WEBVTT Kind: captions Language: en 00:00:00.020 --> 00:00:04.180 align:start position:0% up<00:00:00.710> next<00:00:00.919> we<00:00:01.219> have<00:00:01.250> a<00:00:01.699> panel<00:00:02.179> on<00:00:02.709> EVM<00:00:03.709> which<00:00:04.040> is 00:00:04.180 --> 00:00:04.190 align:start position:0% up next we have a panel on EVM which is 00:00:04.190 --> 00:00:06.579 align:start position:0% up next we have a panel on EVM which is the<00:00:04.310> etherium<00:00:04.670> virtual<00:00:05.000> machine<00:00:05.589> there's 00:00:06.579 --> 00:00:06.589 align:start position:0% the etherium virtual machine there's 00:00:06.589 --> 00:00:09.070 align:start position:0% the etherium virtual machine there's obviously<00:00:07.220> some<00:00:07.430> overlap<00:00:07.790> here<00:00:08.360> with<00:00:08.630> the<00:00:09.050> e 00:00:09.070 --> 00:00:09.080 align:start position:0% obviously some overlap here with the e 00:00:09.080 --> 00:00:11.140 align:start position:0% obviously some overlap here with the e azam<00:00:09.470> topic<00:00:09.830> including<00:00:10.340> those<00:00:10.700> of<00:00:10.850> us<00:00:10.940> on<00:00:11.090> the 00:00:11.140 --> 00:00:11.150 align:start position:0% azam topic including those of us on the 00:00:11.150 --> 00:00:13.570 align:start position:0% azam topic including those of us on the stage<00:00:11.890> unfortunately<00:00:12.890> we<00:00:12.980> had<00:00:13.100> a<00:00:13.130> couple<00:00:13.400> of 00:00:13.570 --> 00:00:13.580 align:start position:0% stage unfortunately we had a couple of 00:00:13.580 --> 00:00:15.550 align:start position:0% stage unfortunately we had a couple of other<00:00:13.730> none<00:00:14.150> II<00:00:14.450> wasn't<00:00:14.720> panelists<00:00:15.320> who<00:00:15.440> were 00:00:15.550 --> 00:00:15.560 align:start position:0% other none II wasn't panelists who were 00:00:15.560 --> 00:00:17.980 align:start position:0% other none II wasn't panelists who were not<00:00:15.710> able<00:00:15.740> to<00:00:16.010> make<00:00:16.550> it<00:00:16.610> but<00:00:17.480> we<00:00:17.540> do<00:00:17.630> have<00:00:17.750> Greg 00:00:17.980 --> 00:00:17.990 align:start position:0% not able to make it but we do have Greg 00:00:17.990 --> 00:00:21.010 align:start position:0% not able to make it but we do have Greg with<00:00:18.290> us<00:00:18.610> thrilled<00:00:19.610> to<00:00:19.790> have<00:00:20.240> him<00:00:20.420> join<00:00:20.750> us<00:00:20.900> for 00:00:21.010 --> 00:00:21.020 align:start position:0% with us thrilled to have him join us for 00:00:21.020 --> 00:00:23.260 align:start position:0% with us thrilled to have him join us for this<00:00:21.110> part<00:00:21.350> and<00:00:22.340> just<00:00:22.490> to<00:00:22.610> be<00:00:22.700> clear<00:00:22.730> this<00:00:23.090> is 00:00:23.260 --> 00:00:23.270 align:start position:0% this part and just to be clear this is 00:00:23.270 --> 00:00:27.100 align:start position:0% this part and just to be clear this is the<00:00:23.750> topic<00:00:23.930> is<00:00:24.170> EVM<00:00:24.770> as<00:00:24.980> I<00:00:25.100> said<00:00:25.310> I<00:00:25.840> mean<00:00:26.840> we<00:00:26.990> may 00:00:27.100 --> 00:00:27.110 align:start position:0% the topic is EVM as I said I mean we may 00:00:27.110 --> 00:00:28.420 align:start position:0% the topic is EVM as I said I mean we may touch<00:00:27.230> upon<00:00:27.380> some<00:00:27.530> some<00:00:27.920> you<00:00:28.010> want<00:00:28.160> some<00:00:28.250> stuff 00:00:28.420 --> 00:00:28.430 align:start position:0% touch upon some some you want some stuff 00:00:28.430 --> 00:00:29.980 align:start position:0% touch upon some some you want some stuff but<00:00:28.520> we'll<00:00:28.610> be<00:00:28.670> focusing<00:00:29.060> more<00:00:29.210> upon<00:00:29.539> the 00:00:29.980 --> 00:00:29.990 align:start position:0% but we'll be focusing more upon the 00:00:29.990 --> 00:00:31.450 align:start position:0% but we'll be focusing more upon the etherium<00:00:30.380> virtual<00:00:30.710> machine<00:00:30.980> what<00:00:31.190> it<00:00:31.280> looks 00:00:31.450 --> 00:00:31.460 align:start position:0% etherium virtual machine what it looks 00:00:31.460 --> 00:00:33.970 align:start position:0% etherium virtual machine what it looks like<00:00:31.580> today<00:00:31.900> the<00:00:32.900> road<00:00:33.050> forward<00:00:33.320> challenges 00:00:33.970 --> 00:00:33.980 align:start position:0% like today the road forward challenges 00:00:33.980 --> 00:00:35.830 align:start position:0% like today the road forward challenges that<00:00:34.100> kind<00:00:34.310> of<00:00:34.340> stuff<00:00:34.579> so<00:00:35.180> cool 00:00:35.830 --> 00:00:35.840 align:start position:0% that kind of stuff so cool 00:00:35.840 --> 00:00:37.600 align:start position:0% that kind of stuff so cool I'll<00:00:36.290> moderate<00:00:36.680> but<00:00:36.829> why<00:00:36.920> don't<00:00:36.980> we<00:00:37.100> kick<00:00:37.520> off 00:00:37.600 --> 00:00:37.610 align:start position:0% I'll moderate but why don't we kick off 00:00:37.610 --> 00:00:38.770 align:start position:0% I'll moderate but why don't we kick off with<00:00:37.670> the<00:00:37.910> introductions<00:00:38.329> Greg<00:00:38.540> do<00:00:38.600> you<00:00:38.630> want 00:00:38.770 --> 00:00:38.780 align:start position:0% with the introductions Greg do you want 00:00:38.780 --> 00:00:39.370 align:start position:0% with the introductions Greg do you want to<00:00:38.870> start 00:00:39.370 --> 00:00:39.380 align:start position:0% to start 00:00:39.380 --> 00:00:43.270 align:start position:0% to start yeah<00:00:40.160> I've<00:00:40.340> I<00:00:40.820> put<00:00:41.630> a<00:00:41.660> lot<00:00:41.899> of<00:00:42.050> work<00:00:42.290> into<00:00:42.620> the 00:00:43.270 --> 00:00:43.280 align:start position:0% yeah I've I put a lot of work into the 00:00:43.280 --> 00:00:49.600 align:start position:0% yeah I've I put a lot of work into the what's<00:00:44.149> now<00:00:44.329> called<00:00:44.600> Aleph<00:00:45.140> is<00:00:45.350> it<00:00:46.960> ADM<00:00:48.610> 1.0 00:00:49.600 --> 00:00:49.610 align:start position:0% what's now called Aleph is it ADM 1.0 00:00:49.610 --> 00:00:54.400 align:start position:0% what's now called Aleph is it ADM 1.0 and<00:00:50.000> put<00:00:50.780> a<00:00:50.809> lot<00:00:51.020> of<00:00:51.170> work<00:00:51.440> into<00:00:53.410> specification 00:00:54.400 --> 00:00:54.410 align:start position:0% and put a lot of work into specification 00:00:54.410 --> 00:00:56.950 align:start position:0% and put a lot of work into specification for<00:00:55.160> making<00:00:55.670> fairly<00:00:55.940> quickly<00:00:56.420> some 00:00:56.950 --> 00:00:56.960 align:start position:0% for making fairly quickly some 00:00:56.960 --> 00:01:01.299 align:start position:0% for making fairly quickly some improvements<00:00:57.850> to<00:00:59.230> get<00:01:00.230> better<00:01:01.010> performance 00:01:01.299 --> 00:01:01.309 align:start position:0% improvements to get better performance 00:01:01.309 --> 00:01:07.870 align:start position:0% improvements to get better performance better<00:01:02.300> formal<00:01:03.290> tractability<00:01:06.189> for<00:01:07.189> the<00:01:07.429> VM 00:01:07.870 --> 00:01:07.880 align:start position:0% better formal tractability for the VM 00:01:07.880 --> 00:01:12.160 align:start position:0% better formal tractability for the VM that<00:01:08.810> could<00:01:09.020> be<00:01:09.170> get<00:01:09.490> begot<00:01:10.689> that<00:01:11.689> we<00:01:11.810> can<00:01:11.959> get 00:01:12.160 --> 00:01:12.170 align:start position:0% that could be get begot that we can get 00:01:12.170 --> 00:01:14.889 align:start position:0% that could be get begot that we can get into<00:01:12.380> place<00:01:12.799> much<00:01:13.189> more<00:01:13.490> quickly<00:01:13.880> than<00:01:14.389> the 00:01:14.889 --> 00:01:14.899 align:start position:0% into place much more quickly than the 00:01:14.899 --> 00:01:18.849 align:start position:0% into place much more quickly than the full<00:01:15.170> US<00:01:15.920> and<00:01:16.219> development<00:01:17.020> those<00:01:18.020> those<00:01:18.560> got 00:01:18.849 --> 00:01:18.859 align:start position:0% full US and development those those got 00:01:18.859 --> 00:01:21.580 align:start position:0% full US and development those those got sort<00:01:19.219> of<00:01:19.340> set<00:01:19.670> aside<00:01:20.090> for<00:01:20.479> the<00:01:20.600> last<00:01:20.840> year<00:01:21.289> I've 00:01:21.580 --> 00:01:21.590 align:start position:0% sort of set aside for the last year I've 00:01:21.590 --> 00:01:24.239 align:start position:0% sort of set aside for the last year I've a<00:01:21.859> month<00:01:22.579> I<00:01:22.819> don't<00:01:22.909> know<00:01:23.179> why<00:01:23.389> but<00:01:23.749> they<00:01:23.929> did 00:01:24.239 --> 00:01:24.249 align:start position:0% a month I don't know why but they did 00:01:24.249 --> 00:01:26.289 align:start position:0% a month I don't know why but they did okay<00:01:25.249> what's<00:01:25.429> that<00:01:25.639> that's<00:01:25.880> a<00:01:26.060> really 00:01:26.289 --> 00:01:26.299 align:start position:0% okay what's that that's a really 00:01:26.299 --> 00:01:27.340 align:start position:0% okay what's that that's a really interesting<00:01:26.509> topic<00:01:26.749> we'll<00:01:27.020> come<00:01:27.139> back<00:01:27.259> to 00:01:27.340 --> 00:01:27.350 align:start position:0% interesting topic we'll come back to 00:01:27.350 --> 00:01:29.109 align:start position:0% interesting topic we'll come back to that<00:01:27.380> just<00:01:27.770> does<00:01:27.889> that<00:01:27.979> come<00:01:28.189> back<00:01:28.399> yeah<00:01:28.759> we'll 00:01:29.109 --> 00:01:29.119 align:start position:0% that just does that come back yeah we'll 00:01:29.119 --> 00:01:30.550 align:start position:0% that just does that come back yeah we'll just<00:01:29.149> do<00:01:29.299> a<00:01:29.329> quick<00:01:29.479> intros<00:01:29.840> and<00:01:30.020> then<00:01:30.109> start 00:01:30.550 --> 00:01:30.560 align:start position:0% just do a quick intros and then start 00:01:30.560 --> 00:01:32.859 align:start position:0% just do a quick intros and then start with<00:01:30.649> that<00:01:30.799> or<00:01:31.249> not<00:01:31.369> we're<00:01:31.969> just<00:01:31.999> doing<00:01:32.329> intro 00:01:32.859 --> 00:01:32.869 align:start position:0% with that or not we're just doing intro 00:01:32.869 --> 00:01:37.029 align:start position:0% with that or not we're just doing intro yeah<00:01:33.109> okay<00:01:33.590> so<00:01:34.069> that's<00:01:34.789> what<00:01:34.999> I<00:01:35.029> did<00:01:35.389> and<00:01:36.039> I'm 00:01:37.029 --> 00:01:37.039 align:start position:0% yeah okay so that's what I did and I'm 00:01:37.039 --> 00:01:39.940 align:start position:0% yeah okay so that's what I did and I'm working<00:01:37.279> on<00:01:37.700> plans<00:01:38.060> to<00:01:38.329> to<00:01:39.109> get<00:01:39.319> that<00:01:39.499> going 00:01:39.940 --> 00:01:39.950 align:start position:0% working on plans to to get that going 00:01:39.950 --> 00:01:42.730 align:start position:0% working on plans to to get that going again<00:01:40.099> quickly<00:01:40.939> and<00:01:41.209> well<00:01:41.929> integrated<00:01:42.590> with 00:01:42.730 --> 00:01:42.740 align:start position:0% again quickly and well integrated with 00:01:42.740 --> 00:01:48.010 align:start position:0% again quickly and well integrated with the<00:01:43.039> EMC<00:01:43.429> work<00:01:44.179> and<00:01:44.539> he<00:01:44.990> was<00:01:45.200> some<00:01:45.529> work<00:01:46.869> so<00:01:47.869> we 00:01:48.010 --> 00:01:48.020 align:start position:0% the EMC work and he was some work so we 00:01:48.020 --> 00:01:50.230 align:start position:0% the EMC work and he was some work so we can<00:01:48.229> sort<00:01:48.409> of<00:01:48.529> front<00:01:48.859> run<00:01:49.099> on<00:01:49.310> that<00:01:49.609> and<00:01:50.029> get 00:01:50.230 --> 00:01:50.240 align:start position:0% can sort of front run on that and get 00:01:50.240 --> 00:01:55.709 align:start position:0% can sort of front run on that and get people<00:01:50.689> get<00:01:51.349> people<00:01:51.709> going<00:01:52.069> and<00:01:53.289> thanks<00:01:54.289> Greg 00:01:55.709 --> 00:01:55.719 align:start position:0% people get people going and thanks Greg 00:01:55.719 --> 00:02:00.909 align:start position:0% people get people going and thanks Greg Hyman<00:01:56.719> Paulo<00:01:56.989> and<00:01:57.429> I<00:01:58.899> working<00:01:59.899> for<00:02:00.289> to<00:02:00.529> you<00:02:00.649> for 00:02:00.909 --> 00:02:00.919 align:start position:0% Hyman Paulo and I working for to you for 00:02:00.919 --> 00:02:03.599 align:start position:0% Hyman Paulo and I working for to you for some<00:02:01.099> time<00:02:01.369> and<00:02:01.700> I<00:02:01.939> was<00:02:02.450> mostly<00:02:02.840> interested<00:02:03.020> in 00:02:03.599 --> 00:02:03.609 align:start position:0% some time and I was mostly interested in 00:02:03.609 --> 00:02:08.800 align:start position:0% some time and I was mostly interested in EVM<00:02:05.109> a<00:02:06.109> long<00:02:06.859> time<00:02:07.159> ago<00:02:07.429> I<00:02:07.459> even<00:02:07.849> created 00:02:08.800 --> 00:02:08.810 align:start position:0% EVM a long time ago I even created 00:02:08.810 --> 00:02:13.690 align:start position:0% EVM a long time ago I even created project<00:02:09.580> to<00:02:11.560> compile<00:02:12.560> a<00:02:12.590> VM<00:02:13.070> code 00:02:13.690 --> 00:02:13.700 align:start position:0% project to compile a VM code 00:02:13.700 --> 00:02:17.080 align:start position:0% project to compile a VM code to<00:02:14.860> machine<00:02:15.860> code<00:02:16.069> some<00:02:16.520> kind<00:02:16.760> of<00:02:16.819> jet 00:02:17.080 --> 00:02:17.090 align:start position:0% to machine code some kind of jet 00:02:17.090 --> 00:02:22.229 align:start position:0% to machine code some kind of jet solution<00:02:17.690> and<00:02:17.989> that<00:02:18.550> also<00:02:19.550> inspired<00:02:20.150> some 00:02:22.229 --> 00:02:22.239 align:start position:0% solution and that also inspired some 00:02:22.239 --> 00:02:25.360 align:start position:0% solution and that also inspired some small<00:02:23.239> but<00:02:23.540> important<00:02:24.140> changes<00:02:24.200> in<00:02:24.680> IBM's 00:02:25.360 --> 00:02:25.370 align:start position:0% small but important changes in IBM's 00:02:25.370 --> 00:02:30.360 align:start position:0% small but important changes in IBM's back<00:02:26.140> before<00:02:27.310> it's<00:02:28.310> even<00:02:28.489> even<00:02:28.849> launched<00:02:29.269> and 00:02:30.360 --> 00:02:30.370 align:start position:0% back before it's even even launched and 00:02:30.370 --> 00:02:36.880 align:start position:0% back before it's even even launched and now<00:02:31.370> I'm<00:02:31.640> trying<00:02:32.390> to<00:02:33.069> bring<00:02:34.069> some<00:02:35.890> cooperation 00:02:36.880 --> 00:02:36.890 align:start position:0% now I'm trying to bring some cooperation 00:02:36.890 --> 00:02:40.530 align:start position:0% now I'm trying to bring some cooperation to<00:02:37.430> to<00:02:38.060> be<00:02:38.599> emulated<00:02:39.019> software<00:02:39.890> by 00:02:40.530 --> 00:02:40.540 align:start position:0% to to be emulated software by 00:02:40.540 --> 00:02:43.869 align:start position:0% to to be emulated software by introducing<00:02:41.540> this<00:02:42.110> Eve<00:02:42.410> EMC<00:02:42.980> product<00:02:43.519> to 00:02:43.869 --> 00:02:43.879 align:start position:0% introducing this Eve EMC product to 00:02:43.879 --> 00:02:49.199 align:start position:0% introducing this Eve EMC product to allow<00:02:45.069> quickly<00:02:46.069> swap<00:02:46.459> VM<00:02:47.180> implementations 00:02:49.199 --> 00:02:49.209 align:start position:0% allow quickly swap VM implementations 00:02:49.209 --> 00:02:52.750 align:start position:0% allow quickly swap VM implementations and<00:02:50.209> I<00:02:50.930> am<00:02:51.140> also<00:02:51.470> cooperating<00:02:52.160> with<00:02:52.400> you 00:02:52.750 --> 00:02:52.760 align:start position:0% and I am also cooperating with you 00:02:52.760 --> 00:03:00.910 align:start position:0% and I am also cooperating with you wasn't<00:02:52.940> team<00:02:56.260> I'm<00:02:57.260> Casey<00:02:57.769> I<00:02:59.650> really<00:03:00.650> got<00:03:00.799> my 00:03:00.910 --> 00:03:00.920 align:start position:0% wasn't team I'm Casey I really got my 00:03:00.920 --> 00:03:03.009 align:start position:0% wasn't team I'm Casey I really got my start<00:03:01.190> as<00:03:01.340> a<00:03:01.400> core<00:03:01.730> developer<00:03:01.819> on<00:03:02.329> a<00:03:02.599> theory 00:03:03.009 --> 00:03:03.019 align:start position:0% start as a core developer on a theory 00:03:03.019 --> 00:03:06.759 align:start position:0% start as a core developer on a theory MJS<00:03:03.440> the<00:03:03.769> JavaScript<00:03:04.959> client<00:03:05.959> well<00:03:06.319> virtual 00:03:06.759 --> 00:03:06.769 align:start position:0% MJS the JavaScript client well virtual 00:03:06.769 --> 00:03:15.400 align:start position:0% MJS the JavaScript client well virtual machine<00:03:08.950> back<00:03:09.950> in<00:03:09.980> 2017<00:03:10.640> or<00:03:11.799> Byzantium<00:03:12.799> and<00:03:14.410> I 00:03:15.400 --> 00:03:15.410 align:start position:0% machine back in 2017 or Byzantium and I 00:03:15.410 --> 00:03:19.059 align:start position:0% machine back in 2017 or Byzantium and I also<00:03:15.940> try<00:03:16.940> to<00:03:17.000> help<00:03:17.180> with<00:03:17.470> security<00:03:18.470> and 00:03:19.059 --> 00:03:19.069 align:start position:0% also try to help with security and 00:03:19.069 --> 00:03:22.270 align:start position:0% also try to help with security and testing<00:03:20.000> fuzz<00:03:20.389> testing<00:03:20.799> finding<00:03:21.799> consensus 00:03:22.270 --> 00:03:22.280 align:start position:0% testing fuzz testing finding consensus 00:03:22.280 --> 00:03:26.110 align:start position:0% testing fuzz testing finding consensus bugs<00:03:22.519> and<00:03:24.250> then<00:03:25.250> I<00:03:25.400> try<00:03:25.549> to<00:03:25.609> help<00:03:25.730> out<00:03:25.970> with 00:03:26.110 --> 00:03:26.120 align:start position:0% bugs and then I try to help out with 00:03:26.120 --> 00:03:29.379 align:start position:0% bugs and then I try to help out with contribute<00:03:26.900> to<00:03:27.459> research<00:03:28.459> on<00:03:28.940> you<00:03:29.299> know 00:03:29.379 --> 00:03:29.389 align:start position:0% contribute to research on you know 00:03:29.389 --> 00:03:35.140 align:start position:0% contribute to research on you know Durham<00:03:30.049> 2.0<00:03:30.760> sharding<00:03:33.069> my<00:03:34.069> name<00:03:34.220> is<00:03:34.310> Alex 00:03:35.140 --> 00:03:35.150 align:start position:0% Durham 2.0 sharding my name is Alex 00:03:35.150 --> 00:03:37.300 align:start position:0% Durham 2.0 sharding my name is Alex I<00:03:35.180> started<00:03:35.810> off<00:03:35.900> 52<00:03:36.230> mgs<00:03:36.590> as<00:03:36.709> well<00:03:36.920> working 00:03:37.300 --> 00:03:37.310 align:start position:0% I started off 52 mgs as well working 00:03:37.310 --> 00:03:39.970 align:start position:0% I started off 52 mgs as well working mostly<00:03:37.639> on<00:03:37.700> the<00:03:37.819> VM<00:03:38.030> in<00:03:38.180> JavaScript<00:03:39.019> but<00:03:39.859> at 00:03:39.970 --> 00:03:39.980 align:start position:0% mostly on the VM in JavaScript but at 00:03:39.980 --> 00:03:41.349 align:start position:0% mostly on the VM in JavaScript but at the<00:03:40.040> same<00:03:40.190> time<00:03:40.519> started<00:03:40.910> to<00:03:40.970> work<00:03:41.120> on 00:03:41.349 --> 00:03:41.359 align:start position:0% the same time started to work on 00:03:41.359 --> 00:03:43.840 align:start position:0% the same time started to work on solidity<00:03:41.920> trying<00:03:42.920> to<00:03:43.010> fix<00:03:43.160> bugs<00:03:43.459> and<00:03:43.730> then 00:03:43.840 --> 00:03:43.850 align:start position:0% solidity trying to fix bugs and then 00:03:43.850 --> 00:03:46.509 align:start position:0% solidity trying to fix bugs and then actually<00:03:44.239> adding<00:03:45.019> features<00:03:45.489> so<00:03:46.489> that 00:03:46.509 --> 00:03:46.519 align:start position:0% actually adding features so that 00:03:46.519 --> 00:03:48.370 align:start position:0% actually adding features so that resulted<00:03:47.030> a<00:03:47.060> lot<00:03:47.180> of<00:03:47.269> DVM<00:03:47.600> works<00:03:47.840> like<00:03:48.109> both<00:03:48.350> of 00:03:48.370 --> 00:03:48.380 align:start position:0% resulted a lot of DVM works like both of 00:03:48.380 --> 00:03:51.460 align:start position:0% resulted a lot of DVM works like both of these<00:03:48.670> and<00:03:49.670> ended<00:03:50.420> up<00:03:50.510> contributing<00:03:50.780> to<00:03:51.170> a<00:03:51.200> VM 00:03:51.460 --> 00:03:51.470 align:start position:0% these and ended up contributing to a VM 00:03:51.470 --> 00:03:53.440 align:start position:0% these and ended up contributing to a VM C<00:03:51.709> and<00:03:52.010> ended<00:03:52.280> up<00:03:52.400> contributing<00:03:52.639> to<00:03:53.000> he<00:03:53.120> wasn't 00:03:53.440 --> 00:03:53.450 align:start position:0% C and ended up contributing to he wasn't 00:03:53.450 --> 00:03:56.199 align:start position:0% C and ended up contributing to he wasn't in<00:03:53.540> the<00:03:53.660> end<00:03:53.810> but<00:03:54.590> I'm<00:03:54.709> still<00:03:54.940> also<00:03:55.940> very 00:03:56.199 --> 00:03:56.209 align:start position:0% in the end but I'm still also very 00:03:56.209 --> 00:03:59.140 align:start position:0% in the end but I'm still also very interested<00:03:56.599> in<00:03:56.690> improving<00:03:57.049> the<00:03:57.319> EVM<00:03:57.650> and<00:03:58.150> so 00:03:59.140 --> 00:03:59.150 align:start position:0% interested in improving the EVM and so 00:03:59.150 --> 00:04:00.520 align:start position:0% interested in improving the EVM and so actually<00:03:59.450> with<00:03:59.569> Pavel<00:03:59.810> we<00:04:00.079> submitted<00:04:00.470> a 00:04:00.520 --> 00:04:00.530 align:start position:0% actually with Pavel we submitted a 00:04:00.530 --> 00:04:02.860 align:start position:0% actually with Pavel we submitted a couple<00:04:00.620> of<00:04:00.799> the<00:04:00.889> IPS<00:04:01.250> and<00:04:01.430> which<00:04:02.269> are<00:04:02.480> accepted 00:04:02.860 --> 00:04:02.870 align:start position:0% couple of the IPS and which are accepted 00:04:02.870 --> 00:04:04.479 align:start position:0% couple of the IPS and which are accepted to<00:04:02.959> constantly<00:04:03.349> Poland<00:04:03.799> Pavel<00:04:04.160> osis 00:04:04.479 --> 00:04:04.489 align:start position:0% to constantly Poland Pavel osis 00:04:04.489 --> 00:04:07.599 align:start position:0% to constantly Poland Pavel osis submitted<00:04:05.299> his<00:04:05.959> only<00:04:06.230> IPs<00:04:06.620> and<00:04:06.950> I<00:04:07.310> was<00:04:07.430> really 00:04:07.599 --> 00:04:07.609 align:start position:0% submitted his only IPs and I was really 00:04:07.609 --> 00:04:09.309 align:start position:0% submitted his only IPs and I was really excited<00:04:07.790> of<00:04:08.239> the<00:04:08.359> IPC 00:04:09.309 --> 00:04:09.319 align:start position:0% excited of the IPC 00:04:09.319 --> 00:04:13.089 align:start position:0% excited of the IPC greg<00:04:09.889> was<00:04:09.919> doing<00:04:10.340> regarding<00:04:11.299> given<00:04:11.630> 1.5<00:04:12.169> but 00:04:13.089 --> 00:04:13.099 align:start position:0% greg was doing regarding given 1.5 but 00:04:13.099 --> 00:04:14.710 align:start position:0% greg was doing regarding given 1.5 but they<00:04:13.220> are<00:04:13.310> much<00:04:13.459> bigger<00:04:13.579> IPS<00:04:14.150> than<00:04:14.329> what<00:04:14.569> we 00:04:14.710 --> 00:04:14.720 align:start position:0% they are much bigger IPS than what we 00:04:14.720 --> 00:04:17.620 align:start position:0% they are much bigger IPS than what we have<00:04:14.840> submitted<00:04:15.049> and<00:04:16.150> so<00:04:17.150> that's<00:04:17.329> that's 00:04:17.620 --> 00:04:17.630 align:start position:0% have submitted and so that's that's 00:04:17.630 --> 00:04:19.870 align:start position:0% have submitted and so that's that's basically<00:04:17.810> about<00:04:18.169> me<00:04:18.400> interested<00:04:19.400> in<00:04:19.489> EVM<00:04:19.760> as 00:04:19.870 --> 00:04:19.880 align:start position:0% basically about me interested in EVM as 00:04:19.880 --> 00:04:23.290 align:start position:0% basically about me interested in EVM as well<00:04:20.060> not<00:04:20.479> just<00:04:20.690> he<00:04:20.780> wasn't<00:04:21.220> cool<00:04:22.220> I'm<00:04:22.460> Lane 00:04:23.290 --> 00:04:23.300 align:start position:0% well not just he wasn't cool I'm Lane 00:04:23.300 --> 00:04:25.540 align:start position:0% well not just he wasn't cool I'm Lane I'm<00:04:23.510> also<00:04:23.900> on<00:04:24.320> he<00:04:24.590> wasn't<00:04:24.770> team<00:04:24.979> that<00:04:25.250> a<00:04:25.280> member 00:04:25.540 --> 00:04:25.550 align:start position:0% I'm also on he wasn't team that a member 00:04:25.550 --> 00:04:26.740 align:start position:0% I'm also on he wasn't team that a member of<00:04:25.610> that<00:04:25.700> team<00:04:25.760> since<00:04:26.150> the<00:04:26.210> beginning<00:04:26.570> of<00:04:26.659> this 00:04:26.740 --> 00:04:26.750 align:start position:0% of that team since the beginning of this 00:04:26.750 --> 00:04:27.550 align:start position:0% of that team since the beginning of this year 00:04:27.550 --> 00:04:27.560 align:start position:0% year 00:04:27.560 --> 00:04:29.200 align:start position:0% year I<00:04:27.590> think<00:04:27.800> my<00:04:27.889> interest<00:04:28.220> in<00:04:28.580> things<00:04:29.090> like 00:04:29.200 --> 00:04:29.210 align:start position:0% I think my interest in things like 00:04:29.210 --> 00:04:31.420 align:start position:0% I think my interest in things like instruction<00:04:30.080> sets<00:04:30.290> and<00:04:30.560> he<00:04:30.770> was<00:04:30.919> a<00:04:30.950> man<00:04:31.160> EVM 00:04:31.420 --> 00:04:31.430 align:start position:0% instruction sets and he was a man EVM 00:04:31.430 --> 00:04:33.550 align:start position:0% instruction sets and he was a man EVM comes<00:04:32.210> from<00:04:32.389> just<00:04:32.510> a<00:04:32.630> deep<00:04:32.810> curiosity<00:04:33.020> of 00:04:33.550 --> 00:04:33.560 align:start position:0% comes from just a deep curiosity of 00:04:33.560 --> 00:04:35.140 align:start position:0% comes from just a deep curiosity of starting<00:04:33.860> at<00:04:33.950> the<00:04:34.010> very<00:04:34.100> bottom<00:04:34.490> of<00:04:34.639> a<00:04:34.850> system 00:04:35.140 --> 00:04:35.150 align:start position:0% starting at the very bottom of a system 00:04:35.150 --> 00:04:36.820 align:start position:0% starting at the very bottom of a system and<00:04:35.360> kind<00:04:35.540> of<00:04:35.570> working<00:04:35.840> my<00:04:35.930> way<00:04:35.960> up<00:04:36.110> there's<00:04:36.560> a 00:04:36.820 --> 00:04:36.830 align:start position:0% and kind of working my way up there's a 00:04:36.830 --> 00:04:38.530 align:start position:0% and kind of working my way up there's a lot<00:04:37.070> of<00:04:37.190> amazing<00:04:37.370> work<00:04:37.669> being<00:04:37.880> done<00:04:37.970> at<00:04:38.330> higher 00:04:38.530 --> 00:04:38.540 align:start position:0% lot of amazing work being done at higher 00:04:38.540 --> 00:04:40.690 align:start position:0% lot of amazing work being done at higher layers<00:04:38.810> layer<00:04:39.080> 2<00:04:39.320> layer<00:04:39.350> 3<00:04:39.590> etc<00:04:39.950> but<00:04:40.430> really 00:04:40.690 --> 00:04:40.700 align:start position:0% layers layer 2 layer 3 etc but really 00:04:40.700 --> 00:04:43.540 align:start position:0% layers layer 2 layer 3 etc but really understanding<00:04:41.710> this<00:04:42.710> virtual<00:04:43.160> machine<00:04:43.190> this 00:04:43.540 --> 00:04:43.550 align:start position:0% understanding this virtual machine this 00:04:43.550 --> 00:04:44.710 align:start position:0% understanding this virtual machine this aetherium<00:04:43.910> machine<00:04:44.180> that<00:04:44.300> we're<00:04:44.419> building 00:04:44.710 --> 00:04:44.720 align:start position:0% aetherium machine that we're building 00:04:44.720 --> 00:04:47.500 align:start position:0% aetherium machine that we're building from<00:04:45.230> from<00:04:45.530> the<00:04:45.650> bottom<00:04:45.889> to<00:04:46.130> start<00:04:46.280> cool<00:04:47.270> so 00:04:47.500 --> 00:04:47.510 align:start position:0% from from the bottom to start cool so 00:04:47.510 --> 00:04:49.570 align:start position:0% from from the bottom to start cool so let<00:04:47.810> me<00:04:47.900> actually<00:04:48.169> I'll<00:04:48.770> come<00:04:48.980> back<00:04:49.070> to<00:04:49.220> EVM 00:04:49.570 --> 00:04:49.580 align:start position:0% let me actually I'll come back to EVM 00:04:49.580 --> 00:04:50.800 align:start position:0% let me actually I'll come back to EVM one-point-five<00:04:50.000> stuff<00:04:50.210> in<00:04:50.300> just<00:04:50.480> a<00:04:50.570> sec<00:04:50.720> I 00:04:50.800 --> 00:04:50.810 align:start position:0% one-point-five stuff in just a sec I 00:04:50.810 --> 00:04:52.659 align:start position:0% one-point-five stuff in just a sec I promise<00:04:51.139> I<00:04:51.290> just<00:04:51.530> want<00:04:51.680> to<00:04:51.770> kick<00:04:51.889> off<00:04:52.010> with<00:04:52.250> an 00:04:52.659 --> 00:04:52.669 align:start position:0% promise I just want to kick off with an 00:04:52.669 --> 00:04:54.070 align:start position:0% promise I just want to kick off with an introductory<00:04:53.120> question<00:04:53.600> which<00:04:53.780> is<00:04:53.900> maybe 00:04:54.070 --> 00:04:54.080 align:start position:0% introductory question which is maybe 00:04:54.080 --> 00:04:55.659 align:start position:0% introductory question which is maybe Alex<00:04:54.380> you<00:04:54.500> could<00:04:54.620> take<00:04:54.740> this<00:04:54.830> one 00:04:55.659 --> 00:04:55.669 align:start position:0% Alex you could take this one 00:04:55.669 --> 00:04:58.150 align:start position:0% Alex you could take this one just<00:04:56.030> what<00:04:56.450> is<00:04:56.540> EVM<00:04:56.870> how<00:04:57.320> did<00:04:57.470> this<00:04:57.560> thing<00:04:57.770> come 00:04:58.150 --> 00:04:58.160 align:start position:0% just what is EVM how did this thing come 00:04:58.160 --> 00:04:59.650 align:start position:0% just what is EVM how did this thing come into<00:04:58.400> existence<00:04:58.790> what<00:04:58.910> is<00:04:59.030> it<00:04:59.090> supposed<00:04:59.330> to<00:04:59.389> be 00:04:59.650 --> 00:04:59.660 align:start position:0% into existence what is it supposed to be 00:04:59.660 --> 00:05:02.700 align:start position:0% into existence what is it supposed to be or<00:05:00.169> do<00:05:00.350> I<00:05:00.880> mean<00:05:01.880> you<00:05:01.910> want<00:05:02.120> to<00:05:02.180> pass<00:05:02.360> in<00:05:02.540> there 00:05:02.700 --> 00:05:02.710 align:start position:0% or do I mean you want to pass in there 00:05:02.710 --> 00:05:09.100 align:start position:0% or do I mean you want to pass in there someone<00:05:03.710> else<00:05:03.770> wanted<00:05:04.130> up<00:05:05.000> to<00:05:05.150> that<00:05:06.669> I<00:05:07.990> mean<00:05:08.990> it 00:05:09.100 --> 00:05:09.110 align:start position:0% someone else wanted up to that I mean it 00:05:09.110 --> 00:05:10.570 align:start position:0% someone else wanted up to that I mean it started<00:05:09.410> from<00:05:09.530> the<00:05:09.710> beginning<00:05:10.100> there's<00:05:10.490> a 00:05:10.570 --> 00:05:10.580 align:start position:0% started from the beginning there's a 00:05:10.580 --> 00:05:12.129 align:start position:0% started from the beginning there's a section<00:05:10.940> of<00:05:11.090> the<00:05:11.210> yellow<00:05:11.479> paper<00:05:11.750> which 00:05:12.129 --> 00:05:12.139 align:start position:0% section of the yellow paper which 00:05:12.139 --> 00:05:17.140 align:start position:0% section of the yellow paper which describes<00:05:12.650> the<00:05:12.830> VM<00:05:13.340> and<00:05:14.889> so<00:05:15.889> it's<00:05:16.160> it's<00:05:16.970> an 00:05:17.140 --> 00:05:17.150 align:start position:0% describes the VM and so it's it's an 00:05:17.150 --> 00:05:19.469 align:start position:0% describes the VM and so it's it's an essential<00:05:17.660> part<00:05:17.930> of<00:05:18.110> even<00:05:18.320> the<00:05:18.560> concept<00:05:19.160> of 00:05:19.469 --> 00:05:19.479 align:start position:0% essential part of even the concept of 00:05:19.479 --> 00:05:22.090 align:start position:0% essential part of even the concept of etherium<00:05:20.479> we<00:05:20.720> have<00:05:20.840> smart<00:05:21.050> contracts<00:05:21.740> and 00:05:22.090 --> 00:05:22.100 align:start position:0% etherium we have smart contracts and 00:05:22.100 --> 00:05:24.010 align:start position:0% etherium we have smart contracts and that<00:05:22.220> what<00:05:22.580> that's<00:05:23.270> what<00:05:23.540> initially 00:05:24.010 --> 00:05:24.020 align:start position:0% that what that's what initially 00:05:24.020 --> 00:05:26.290 align:start position:0% that what that's what initially distinguished<00:05:24.979> etherium<00:05:25.520> from<00:05:25.729> others<00:05:26.060> and 00:05:26.290 --> 00:05:26.300 align:start position:0% distinguished etherium from others and 00:05:26.300 --> 00:05:31.300 align:start position:0% distinguished etherium from others and the<00:05:26.930> VM<00:05:27.290> is<00:05:27.590> is<00:05:27.889> what<00:05:28.190> did<00:05:28.460> it<00:05:28.960> and<00:05:30.040> not<00:05:31.040> to<00:05:31.190> be 00:05:31.300 --> 00:05:31.310 align:start position:0% the VM is is what did it and not to be 00:05:31.310 --> 00:05:34.330 align:start position:0% the VM is is what did it and not to be too<00:05:31.550> nasty<00:05:32.150> but<00:05:32.479> a<00:05:32.630> part<00:05:33.169> of<00:05:33.229> my<00:05:33.410> job<00:05:33.650> is<00:05:33.919> to<00:05:34.130> be 00:05:34.330 --> 00:05:34.340 align:start position:0% too nasty but a part of my job is to be 00:05:34.340 --> 00:05:37.630 align:start position:0% too nasty but a part of my job is to be a<00:05:34.610> nasty<00:05:35.300> old<00:05:35.479> man<00:05:35.570> and<00:05:36.050> yeah<00:05:36.500> Grouch<00:05:37.160> Grouch 00:05:37.630 --> 00:05:37.640 align:start position:0% a nasty old man and yeah Grouch Grouch 00:05:37.640 --> 00:05:39.400 align:start position:0% a nasty old man and yeah Grouch Grouch of<00:05:38.150> people<00:05:38.570> because<00:05:38.780> I've<00:05:38.930> been<00:05:39.080> in<00:05:39.260> the 00:05:39.400 --> 00:05:39.410 align:start position:0% of people because I've been in the 00:05:39.410 --> 00:05:43.240 align:start position:0% of people because I've been in the industry<00:05:39.530> a<00:05:39.890> long<00:05:39.979> time<00:05:40.430> and<00:05:41.380> DVM<00:05:42.380> we<00:05:42.590> have<00:05:42.830> was 00:05:43.240 --> 00:05:43.250 align:start position:0% industry a long time and DVM we have was 00:05:43.250 --> 00:05:45.640 align:start position:0% industry a long time and DVM we have was designed<00:05:43.970> by<00:05:44.180> cryptographers<00:05:45.020> not<00:05:45.380> by 00:05:45.640 --> 00:05:45.650 align:start position:0% designed by cryptographers not by 00:05:45.650 --> 00:05:48.610 align:start position:0% designed by cryptographers not by virtual<00:05:46.640> machine<00:05:46.970> experts<00:05:47.479> so<00:05:48.260> it<00:05:48.410> has 00:05:48.610 --> 00:05:48.620 align:start position:0% virtual machine experts so it has 00:05:48.620 --> 00:05:51.790 align:start position:0% virtual machine experts so it has certain<00:05:49.550> problems<00:05:50.060> which<00:05:50.330> I<00:05:50.750> ran<00:05:50.960> into<00:05:51.440> when<00:05:51.680> I 00:05:51.790 --> 00:05:51.800 align:start position:0% certain problems which I ran into when I 00:05:51.800 --> 00:05:54.010 align:start position:0% certain problems which I ran into when I when<00:05:52.190> I<00:05:52.220> went<00:05:52.550> into<00:05:52.729> it<00:05:52.940> when<00:05:53.390> I<00:05:53.419> got<00:05:53.660> here<00:05:53.990> and 00:05:54.010 --> 00:05:54.020 align:start position:0% when I went into it when I got here and 00:05:54.020 --> 00:05:56.610 align:start position:0% when I went into it when I got here and said<00:05:54.440> this<00:05:55.130> thing<00:05:55.340> needs<00:05:55.610> to<00:05:55.760> be<00:05:55.850> a<00:05:55.970> lot<00:05:56.180> better 00:05:56.610 --> 00:05:56.620 align:start position:0% said this thing needs to be a lot better 00:05:56.620 --> 00:05:59.129 align:start position:0% said this thing needs to be a lot better some<00:05:57.620> of<00:05:57.740> the<00:05:57.830> problems<00:05:58.370> affect<00:05:58.910> performance 00:05:59.129 --> 00:05:59.139 align:start position:0% some of the problems affect performance 00:05:59.139 --> 00:06:02.710 align:start position:0% some of the problems affect performance even<00:06:00.139> worse<00:06:00.650> some<00:06:01.460> of<00:06:01.639> the<00:06:01.760> problems<00:06:02.300> make<00:06:02.539> it 00:06:02.710 --> 00:06:02.720 align:start position:0% even worse some of the problems make it 00:06:02.720 --> 00:06:05.650 align:start position:0% even worse some of the problems make it very<00:06:03.020> difficult<00:06:03.410> to<00:06:03.889> formally<00:06:04.580> analyze<00:06:05.360> the 00:06:05.650 --> 00:06:05.660 align:start position:0% very difficult to formally analyze the 00:06:05.660 --> 00:06:10.570 align:start position:0% very difficult to formally analyze the code<00:06:05.990> and<00:06:08.860> that's<00:06:09.860> something<00:06:10.370> that's 00:06:10.570 --> 00:06:10.580 align:start position:0% code and that's something that's 00:06:10.580 --> 00:06:11.590 align:start position:0% code and that's something that's important<00:06:11.240> to<00:06:11.300> me 00:06:11.590 --> 00:06:11.600 align:start position:0% important to me 00:06:11.600 --> 00:06:14.770 align:start position:0% important to me I<00:06:11.840> sneered<00:06:12.650> at<00:06:12.889> formal<00:06:13.310> and<00:06:13.490> formal<00:06:14.120> analysis 00:06:14.770 --> 00:06:14.780 align:start position:0% I sneered at formal and formal analysis 00:06:14.780 --> 00:06:17.170 align:start position:0% I sneered at formal and formal analysis my<00:06:14.960> whole<00:06:15.169> career<00:06:15.710> because<00:06:16.460> I<00:06:16.610> didn't<00:06:16.940> see 00:06:17.170 --> 00:06:17.180 align:start position:0% my whole career because I didn't see 00:06:17.180 --> 00:06:20.740 align:start position:0% my whole career because I didn't see that<00:06:17.450> taking<00:06:18.880> ten<00:06:19.880> thousand<00:06:20.510> a<00:06:20.600> hundred 00:06:20.740 --> 00:06:20.750 align:start position:0% that taking ten thousand a hundred 00:06:20.750 --> 00:06:24.129 align:start position:0% that taking ten thousand a hundred thousand<00:06:21.410> my<00:06:21.560> program<00:06:22.190> and<00:06:22.550> then<00:06:23.180> writing<00:06:23.539> a 00:06:24.129 --> 00:06:24.139 align:start position:0% thousand my program and then writing a 00:06:24.139 --> 00:06:26.680 align:start position:0% thousand my program and then writing a million<00:06:24.680> line<00:06:24.919> proof<00:06:25.310> was<00:06:26.000> going<00:06:26.360> to<00:06:26.479> help 00:06:26.680 --> 00:06:26.690 align:start position:0% million line proof was going to help 00:06:26.690 --> 00:06:30.879 align:start position:0% million line proof was going to help anything<00:06:27.020> now<00:06:27.979> we're<00:06:28.250> looking<00:06:28.400> at<00:06:29.889> programs 00:06:30.879 --> 00:06:30.889 align:start position:0% anything now we're looking at programs 00:06:30.889 --> 00:06:33.279 align:start position:0% anything now we're looking at programs which<00:06:31.190> are<00:06:31.370> even<00:06:31.760> smaller<00:06:32.120> than<00:06:32.330> what<00:06:32.780> we<00:06:33.080> used 00:06:33.279 --> 00:06:33.289 align:start position:0% which are even smaller than what we used 00:06:33.289 --> 00:06:34.770 align:start position:0% which are even smaller than what we used to<00:06:33.410> write<00:06:33.710> for<00:06:34.010> our 00:06:34.770 --> 00:06:34.780 align:start position:0% to write for our 00:06:34.780 --> 00:06:39.720 align:start position:0% to write for our Apple<00:06:35.139> two's<00:06:37.290> smaller<00:06:38.290> than<00:06:38.680> the<00:06:38.889> 64k 00:06:39.720 --> 00:06:39.730 align:start position:0% Apple two's smaller than the 64k 00:06:39.730 --> 00:06:42.480 align:start position:0% Apple two's smaller than the 64k segments<00:06:40.360> mmm<00:06:40.870> estas<00:06:41.320> that<00:06:41.740> we<00:06:41.860> use<00:06:42.010> staff<00:06:42.280> to 00:06:42.480 --> 00:06:42.490 align:start position:0% segments mmm estas that we use staff to 00:06:42.490 --> 00:06:44.820 align:start position:0% segments mmm estas that we use staff to write<00:06:42.670> in<00:06:43.000> I<00:06:43.240> remember<00:06:43.690> squeezing<00:06:44.410> a 00:06:44.820 --> 00:06:44.830 align:start position:0% write in I remember squeezing a 00:06:44.830 --> 00:06:50.030 align:start position:0% write in I remember squeezing a relational<00:06:45.490> database<00:06:45.700> into<00:06:46.510> a<00:06:46.540> 64<00:06:47.230> K<00:06:47.440> segment 00:06:50.030 --> 00:06:50.040 align:start position:0% relational database into a 64 K segment 00:06:50.040 --> 00:06:53.760 align:start position:0% relational database into a 64 K segment it<00:06:51.040> suddenly<00:06:51.550> starts<00:06:52.030> to<00:06:52.090> make<00:06:52.300> sense<00:06:52.770> when 00:06:53.760 --> 00:06:53.770 align:start position:0% it suddenly starts to make sense when 00:06:53.770 --> 00:06:57.330 align:start position:0% it suddenly starts to make sense when you've<00:06:53.919> got<00:06:54.220> you<00:06:54.970> know<00:06:55.260> an<00:06:56.260> awful<00:06:56.889> lot<00:06:57.310> of 00:06:57.330 --> 00:06:57.340 align:start position:0% you've got you know an awful lot of 00:06:57.340 --> 00:07:03.360 align:start position:0% you've got you know an awful lot of money<00:06:57.669> hanging<00:06:58.660> on<00:06:59.520> 24<00:07:00.520> K<00:07:00.850> of<00:07:01.360> code<00:07:01.780> to<00:07:02.770> spend<00:07:03.100> a 00:07:03.360 --> 00:07:03.370 align:start position:0% money hanging on 24 K of code to spend a 00:07:03.370 --> 00:07:06.060 align:start position:0% money hanging on 24 K of code to spend a lot<00:07:03.700> of<00:07:03.760> money<00:07:04.060> doing<00:07:04.419> anything<00:07:05.080> you<00:07:05.320> can<00:07:05.350> to 00:07:06.060 --> 00:07:06.070 align:start position:0% lot of money doing anything you can to 00:07:06.070 --> 00:07:08.490 align:start position:0% lot of money doing anything you can to prove<00:07:06.280> it<00:07:06.460> right<00:07:06.639> and<00:07:07.030> the<00:07:07.480> current<00:07:07.810> VM<00:07:08.110> makes 00:07:08.490 --> 00:07:08.500 align:start position:0% prove it right and the current VM makes 00:07:08.500 --> 00:07:11.370 align:start position:0% prove it right and the current VM makes that<00:07:08.770> very<00:07:09.070> difficult<00:07:09.450> Lassa<00:07:10.450> makes<00:07:10.960> it<00:07:11.169> a<00:07:11.230> lot 00:07:11.370 --> 00:07:11.380 align:start position:0% that very difficult Lassa makes it a lot 00:07:11.380 --> 00:07:16.110 align:start position:0% that very difficult Lassa makes it a lot easier<00:07:11.580> but<00:07:12.580> when<00:07:12.820> I<00:07:12.850> arrived<00:07:13.650> wasm<00:07:14.650> was<00:07:15.120> not 00:07:16.110 --> 00:07:16.120 align:start position:0% easier but when I arrived wasm was not 00:07:16.120 --> 00:07:20.940 align:start position:0% easier but when I arrived wasm was not yet<00:07:16.419> a<00:07:16.450> thing<00:07:16.780> there<00:07:17.620> was<00:07:18.960> it<00:07:19.960> was<00:07:20.110> agreed<00:07:20.590> I 00:07:20.940 --> 00:07:20.950 align:start position:0% yet a thing there was it was agreed I 00:07:20.950 --> 00:07:23.310 align:start position:0% yet a thing there was it was agreed I don't<00:07:21.669> know<00:07:21.850> exactly<00:07:22.030> where<00:07:22.780> it<00:07:22.930> was<00:07:23.080> in<00:07:23.290> the 00:07:23.310 --> 00:07:23.320 align:start position:0% don't know exactly where it was in the 00:07:23.320 --> 00:07:26.610 align:start position:0% don't know exactly where it was in the realm<00:07:23.590> map<00:07:23.890> but<00:07:24.190> it<00:07:24.340> it<00:07:25.000> was<00:07:25.480> not<00:07:25.780> there<00:07:26.440> was<00:07:26.590> no 00:07:26.610 --> 00:07:26.620 align:start position:0% realm map but it it was not there was no 00:07:26.620 --> 00:07:31.040 align:start position:0% realm map but it it was not there was no spec<00:07:27.100> for<00:07:27.430> it<00:07:27.640> it<00:07:28.300> was<00:07:28.540> finished<00:07:28.810> it<00:07:29.410> was 00:07:31.040 --> 00:07:31.050 align:start position:0% spec for it it was finished it was 00:07:31.050 --> 00:07:34.710 align:start position:0% spec for it it was finished it was minimal<00:07:32.050> minimal<00:07:32.669> Viable<00:07:33.669> Product<00:07:34.180> was<00:07:34.510> not 00:07:34.710 --> 00:07:34.720 align:start position:0% minimal minimal Viable Product was not 00:07:34.720 --> 00:07:37.920 align:start position:0% minimal minimal Viable Product was not even<00:07:34.990> there<00:07:35.229> so<00:07:35.530> I<00:07:36.010> set<00:07:36.669> out<00:07:36.700> to<00:07:37.090> say<00:07:37.330> well<00:07:37.630> I 00:07:37.920 --> 00:07:37.930 align:start position:0% even there so I set out to say well I 00:07:37.930 --> 00:07:39.360 align:start position:0% even there so I set out to say well I don't<00:07:38.290> want<00:07:38.440> to<00:07:38.500> wait<00:07:38.650> that<00:07:38.680> long 00:07:39.360 --> 00:07:39.370 align:start position:0% don't want to wait that long 00:07:39.370 --> 00:07:44.480 align:start position:0% don't want to wait that long and<00:07:40.830> I'm<00:07:41.830> getting<00:07:42.220> back<00:07:42.490> to<00:07:42.940> doing<00:07:43.300> that<00:07:43.479> but 00:07:44.480 --> 00:07:44.490 align:start position:0% and I'm getting back to doing that but 00:07:44.490 --> 00:07:48.120 align:start position:0% and I'm getting back to doing that but that's<00:07:45.490> basically<00:07:45.940> what<00:07:46.540> the<00:07:46.690> EVM<00:07:47.260> is<00:07:47.650> right 00:07:48.120 --> 00:07:48.130 align:start position:0% that's basically what the EVM is right 00:07:48.130 --> 00:07:51.150 align:start position:0% that's basically what the EVM is right now<00:07:48.430> and<00:07:49.000> part<00:07:49.450> of<00:07:49.510> the<00:07:49.660> troubles<00:07:50.160> we're 00:07:51.150 --> 00:07:51.160 align:start position:0% now and part of the troubles we're 00:07:51.160 --> 00:07:54.560 align:start position:0% now and part of the troubles we're running<00:07:51.460> into<00:07:51.700> it<00:07:52.090> and<00:07:52.690> what<00:07:53.110> I<00:07:53.200> joke<00:07:53.560> here's 00:07:54.560 --> 00:07:54.570 align:start position:0% running into it and what I joke here's 00:07:54.570 --> 00:08:00.210 align:start position:0% running into it and what I joke here's the<00:07:55.570> t-shirt<00:07:56.050> from<00:07:57.780> Cancun<00:07:58.780> they<00:07:59.530> day<00:07:59.979> the 00:08:00.210 --> 00:08:00.220 align:start position:0% the t-shirt from Cancun they day the 00:08:00.220 --> 00:08:02.670 align:start position:0% the t-shirt from Cancun they day the dead<00:08:00.490> it's<00:08:01.240> a<00:08:01.360> day<00:08:01.510> after<00:08:01.900> Halloween<00:08:02.050> now 00:08:02.670 --> 00:08:02.680 align:start position:0% dead it's a day after Halloween now 00:08:02.680 --> 00:08:04.920 align:start position:0% dead it's a day after Halloween now there<00:08:03.130> was<00:08:03.220> a<00:08:03.250> accident<00:08:03.760> with<00:08:04.240> laundry<00:08:04.630> bleach 00:08:04.920 --> 00:08:04.930 align:start position:0% there was a accident with laundry bleach 00:08:04.930 --> 00:08:09.420 align:start position:0% there was a accident with laundry bleach so<00:08:05.289> it's<00:08:05.470> been<00:08:05.650> to<00:08:05.800> hell<00:08:05.979> and<00:08:06.010> back<00:08:06.840> and<00:08:08.430> I 00:08:09.420 --> 00:08:09.430 align:start position:0% so it's been to hell and back and I 00:08:09.430 --> 00:08:11.730 align:start position:0% so it's been to hell and back and I never<00:08:09.729> again<00:08:10.210> want<00:08:10.270> to<00:08:10.690> be<00:08:10.900> awakened<00:08:11.530> on<00:08:11.710> a 00:08:11.730 --> 00:08:11.740 align:start position:0% never again want to be awakened on a 00:08:11.740 --> 00:08:15.210 align:start position:0% never again want to be awakened on a Caribbean<00:08:12.220> beach<00:08:12.850> during<00:08:13.330> the<00:08:13.539> vacations<00:08:14.380> to 00:08:15.210 --> 00:08:15.220 align:start position:0% Caribbean beach during the vacations to 00:08:15.220 --> 00:08:17.490 align:start position:0% Caribbean beach during the vacations to discover<00:08:15.700> that<00:08:16.150> you<00:08:16.450> know<00:08:16.510> yet<00:08:17.169> another 00:08:17.490 --> 00:08:17.500 align:start position:0% discover that you know yet another 00:08:17.500 --> 00:08:19.770 align:start position:0% discover that you know yet another million<00:08:18.130> eath<00:08:18.430> is<00:08:18.729> falling<00:08:19.150> down<00:08:19.330> a<00:08:19.360> rat<00:08:19.750> hole 00:08:19.770 --> 00:08:19.780 align:start position:0% million eath is falling down a rat hole 00:08:19.780 --> 00:08:22.500 align:start position:0% million eath is falling down a rat hole because<00:08:20.650> there<00:08:20.890> was<00:08:21.010> a<00:08:21.039> long<00:08:21.310> line<00:08:21.550> bug<00:08:21.940> in 00:08:22.500 --> 00:08:22.510 align:start position:0% because there was a long line bug in 00:08:22.510 --> 00:08:26.550 align:start position:0% because there was a long line bug in your<00:08:22.630> program<00:08:23.080> and<00:08:24.630> so<00:08:25.630> that's<00:08:25.840> my<00:08:26.080> goal<00:08:26.289> right 00:08:26.550 --> 00:08:26.560 align:start position:0% your program and so that's my goal right 00:08:26.560 --> 00:08:32.610 align:start position:0% your program and so that's my goal right now<00:08:26.620> and<00:08:28.229> sees<00:08:29.229> me<00:08:30.960> so<00:08:31.960> I'm<00:08:32.110> just<00:08:32.289> trying<00:08:32.530> to 00:08:32.610 --> 00:08:32.620 align:start position:0% now and sees me so I'm just trying to 00:08:32.620 --> 00:08:35.520 align:start position:0% now and sees me so I'm just trying to get<00:08:33.520> together<00:08:33.700> some<00:08:34.210> people<00:08:34.630> and<00:08:34.960> some<00:08:35.229> money 00:08:35.520 --> 00:08:35.530 align:start position:0% get together some people and some money 00:08:35.530 --> 00:08:39.779 align:start position:0% get together some people and some money to<00:08:36.430> pursue<00:08:36.849> that<00:08:37.180> in<00:08:38.140> parallel<00:08:38.890> and<00:08:39.310> trying<00:08:39.669> to 00:08:39.779 --> 00:08:39.789 align:start position:0% to pursue that in parallel and trying to 00:08:39.789 --> 00:08:41.880 align:start position:0% to pursue that in parallel and trying to get<00:08:39.940> in<00:08:40.120> coordination<00:08:40.659> with<00:08:40.900> the<00:08:41.080> Lassen<00:08:41.620> team 00:08:41.880 --> 00:08:41.890 align:start position:0% get in coordination with the Lassen team 00:08:41.890 --> 00:08:44.900 align:start position:0% get in coordination with the Lassen team so<00:08:42.669> we<00:08:42.820> can<00:08:43.030> get<00:08:43.180> that<00:08:43.450> done<00:08:43.750> more<00:08:44.440> quickly 00:08:44.900 --> 00:08:44.910 align:start position:0% so we can get that done more quickly 00:08:44.910 --> 00:08:47.340 align:start position:0% so we can get that done more quickly onto<00:08:45.910> the<00:08:46.030> main<00:08:46.240> chain 00:08:47.340 --> 00:08:47.350 align:start position:0% onto the main chain 00:08:47.350 --> 00:08:51.300 align:start position:0% onto the main chain and<00:08:48.810> we're<00:08:49.810> going<00:08:50.020> to<00:08:50.080> be<00:08:50.260> able<00:08:50.440> to<00:08:50.650> compile 00:08:51.300 --> 00:08:51.310 align:start position:0% and we're going to be able to compile 00:08:51.310 --> 00:08:55.230 align:start position:0% and we're going to be able to compile that<00:08:51.930> code<00:08:52.930> to<00:08:53.560> Assam<00:08:54.100> code<00:08:54.340> so<00:08:54.730> there's<00:08:54.970> not 00:08:55.230 --> 00:08:55.240 align:start position:0% that code to Assam code so there's not 00:08:55.240 --> 00:08:57.510 align:start position:0% that code to Assam code so there's not going<00:08:55.480> to<00:08:55.570> be<00:08:55.630> any<00:08:55.840> real<00:08:56.110> conflict<00:08:56.650> or<00:08:57.040> trouble 00:08:57.510 --> 00:08:57.520 align:start position:0% going to be any real conflict or trouble 00:08:57.520 --> 00:09:01.680 align:start position:0% going to be any real conflict or trouble for<00:08:58.510> customers<00:08:59.140> as<00:08:59.350> we<00:08:59.590> as<00:08:59.890> we<00:08:59.950> event<00:09:00.730> Eliza<00:09:01.120> I 00:09:01.680 --> 00:09:01.690 align:start position:0% for customers as we as we event Eliza I 00:09:01.690 --> 00:09:04.760 align:start position:0% for customers as we as we event Eliza I sort<00:09:02.320> of<00:09:02.410> see<00:09:02.650> laughs<00:09:02.920> and<00:09:03.220> it's<00:09:03.370> becoming<00:09:03.820> the 00:09:04.760 --> 00:09:04.770 align:start position:0% sort of see laughs and it's becoming the 00:09:04.770 --> 00:09:11.100 align:start position:0% sort of see laughs and it's becoming the assembly<00:09:05.770> language<00:09:06.279> of<00:09:07.080> Ethier<00:09:08.080> i<00:09:09.900> think<00:09:10.900> just 00:09:11.100 --> 00:09:11.110 align:start position:0% assembly language of Ethier i think just 00:09:11.110 --> 00:09:15.960 align:start position:0% assembly language of Ethier i think just half<00:09:11.350> a<00:09:11.589> your<00:09:13.470> interesting<00:09:14.470> line<00:09:14.650> i<00:09:14.910> kind<00:09:15.910> of 00:09:15.960 --> 00:09:15.970 align:start position:0% half a your interesting line i kind of 00:09:15.970 --> 00:09:18.420 align:start position:0% half a your interesting line i kind of felt<00:09:16.150> like<00:09:16.210> that<00:09:16.420> you're<00:09:16.630> saying<00:09:16.870> that<00:09:17.430> was 00:09:18.420 --> 00:09:18.430 align:start position:0% felt like that you're saying that was 00:09:18.430 --> 00:09:21.269 align:start position:0% felt like that you're saying that was him<00:09:18.580> is<00:09:18.670> ready<00:09:18.880> now<00:09:19.060> we<00:09:19.240> don't<00:09:19.420> need<00:09:19.480> a<00:09:19.540> DM<00:09:20.279> but 00:09:21.269 --> 00:09:21.279 align:start position:0% him is ready now we don't need a DM but 00:09:21.279 --> 00:09:23.250 align:start position:0% him is ready now we don't need a DM but then<00:09:21.430> you<00:09:21.580> iterate<00:09:21.940> it<00:09:22.089> on<00:09:22.210> it<00:09:22.330> and<00:09:22.570> i<00:09:22.900> think<00:09:23.200> it 00:09:23.250 --> 00:09:23.260 align:start position:0% then you iterate it on it and i think it 00:09:23.260 --> 00:09:24.960 align:start position:0% then you iterate it on it and i think it was<00:09:23.350> very<00:09:23.380> interesting<00:09:23.830> what<00:09:23.980> you<00:09:24.100> said<00:09:24.310> in 00:09:24.960 --> 00:09:24.970 align:start position:0% was very interesting what you said in 00:09:24.970 --> 00:09:28.829 align:start position:0% was very interesting what you said in general<00:09:25.320> i<00:09:26.820> want<00:09:27.820> to<00:09:27.940> hear<00:09:28.120> a<00:09:28.240> bit<00:09:28.390> more<00:09:28.420> about 00:09:28.829 --> 00:09:28.839 align:start position:0% general i want to hear a bit more about 00:09:28.839 --> 00:09:31.890 align:start position:0% general i want to hear a bit more about that<00:09:28.900> at<00:09:29.710> some<00:09:29.890> point<00:09:30.540> then<00:09:31.540> you<00:09:31.600> just<00:09:31.750> add<00:09:31.839> a 00:09:31.890 --> 00:09:31.900 align:start position:0% that at some point then you just add a 00:09:31.900 --> 00:09:33.780 align:start position:0% that at some point then you just add a tiny<00:09:32.140> bit<00:09:32.290> more<00:09:32.500> color<00:09:32.710> to<00:09:32.800> the<00:09:32.980> introducing 00:09:33.780 --> 00:09:33.790 align:start position:0% tiny bit more color to the introducing 00:09:33.790 --> 00:09:38.160 align:start position:0% tiny bit more color to the introducing EVM<00:09:34.089> idea<00:09:34.600> as<00:09:35.940> you<00:09:36.940> said<00:09:37.120> Greg<00:09:37.390> right<00:09:37.600> EVM<00:09:37.960> is 00:09:38.160 --> 00:09:38.170 align:start position:0% EVM idea as you said Greg right EVM is 00:09:38.170 --> 00:09:40.650 align:start position:0% EVM idea as you said Greg right EVM is sort<00:09:38.710> of<00:09:38.770> the<00:09:39.400> implementation<00:09:40.150> of<00:09:40.270> the<00:09:40.420> yellow 00:09:40.650 --> 00:09:40.660 align:start position:0% sort of the implementation of the yellow 00:09:40.660 --> 00:09:42.030 align:start position:0% sort of the implementation of the yellow paper<00:09:40.870> right<00:09:41.110> it's<00:09:41.230> the<00:09:41.350> state<00:09:41.529> transition 00:09:42.030 --> 00:09:42.040 align:start position:0% paper right it's the state transition 00:09:42.040 --> 00:09:45.600 align:start position:0% paper right it's the state transition machine<00:09:42.880> in<00:09:43.029> the<00:09:43.120> yellow<00:09:43.270> paper<00:09:43.620> and<00:09:44.620> it's<00:09:45.310> a 00:09:45.600 --> 00:09:45.610 align:start position:0% machine in the yellow paper and it's a 00:09:45.610 --> 00:09:47.940 align:start position:0% machine in the yellow paper and it's a really<00:09:46.000> interesting<00:09:46.390> unique<00:09:46.960> really<00:09:47.589> well 00:09:47.940 --> 00:09:47.950 align:start position:0% really interesting unique really well 00:09:47.950 --> 00:09:52.160 align:start position:0% really interesting unique really well designed<00:09:48.240> virtual<00:09:49.240> machine<00:09:49.540> and<00:09:50.350> I'm<00:09:50.470> gonna 00:09:52.160 --> 00:09:52.170 align:start position:0% designed virtual machine and I'm gonna 00:09:52.170 --> 00:09:54.420 align:start position:0% designed virtual machine and I'm gonna hold<00:09:53.170> on<00:09:53.320> hold<00:09:53.589> on<00:09:53.680> wait<00:09:53.860> till<00:09:54.070> I<00:09:54.130> share<00:09:54.339> the 00:09:54.420 --> 00:09:54.430 align:start position:0% hold on hold on wait till I share the 00:09:54.430 --> 00:09:57.270 align:start position:0% hold on hold on wait till I share the second<00:09:54.640> half<00:09:54.760> of<00:09:54.850> my<00:09:54.910> thought<00:09:55.710> it's<00:09:56.710> I'm 00:09:57.270 --> 00:09:57.280 align:start position:0% second half of my thought it's I'm 00:09:57.280 --> 00:09:58.620 align:start position:0% second half of my thought it's I'm paraphrasing<00:09:57.610> and<00:09:58.060> paraphrasing<00:09:58.510> Nick 00:09:58.620 --> 00:09:58.630 align:start position:0% paraphrasing and paraphrasing Nick 00:09:58.630 --> 00:10:01.560 align:start position:0% paraphrasing and paraphrasing Nick Johnson<00:09:58.990> here<00:09:59.260> it's<00:09:59.950> well<00:10:00.220> designed<00:10:00.580> however 00:10:01.560 --> 00:10:01.570 align:start position:0% Johnson here it's well designed however 00:10:01.570 --> 00:10:03.930 align:start position:0% Johnson here it's well designed however it's<00:10:02.080> a<00:10:02.350> theoretical<00:10:02.830> sort<00:10:03.550> of<00:10:03.610> virtual 00:10:03.930 --> 00:10:03.940 align:start position:0% it's a theoretical sort of virtual 00:10:03.940 --> 00:10:04.829 align:start position:0% it's a theoretical sort of virtual machine<00:10:04.210> right<00:10:04.390> so<00:10:04.510> you<00:10:04.570> get<00:10:04.750> these 00:10:04.829 --> 00:10:04.839 align:start position:0% machine right so you get these 00:10:04.839 --> 00:10:06.750 align:start position:0% machine right so you get these interesting<00:10:05.200> things<00:10:05.260> like<00:10:05.589> these<00:10:05.800> 256<00:10:06.580> bit 00:10:06.750 --> 00:10:06.760 align:start position:0% interesting things like these 256 bit 00:10:06.760 --> 00:10:08.610 align:start position:0% interesting things like these 256 bit words<00:10:07.060> so<00:10:07.750> even<00:10:07.930> if<00:10:08.020> you<00:10:08.110> want<00:10:08.260> to<00:10:08.320> do<00:10:08.410> very 00:10:08.610 --> 00:10:08.620 align:start position:0% words so even if you want to do very 00:10:08.620 --> 00:10:11.760 align:start position:0% words so even if you want to do very simple<00:10:09.010> integer<00:10:09.310> math<00:10:09.690> you<00:10:10.690> know<00:10:10.810> you're<00:10:11.260> it's 00:10:11.760 --> 00:10:11.770 align:start position:0% simple integer math you know you're it's 00:10:11.770 --> 00:10:13.110 align:start position:0% simple integer math you know you're it's very<00:10:11.980> inefficient<00:10:12.220> right<00:10:12.580> because<00:10:12.910> you<00:10:13.000> have 00:10:13.110 --> 00:10:13.120 align:start position:0% very inefficient right because you have 00:10:13.120 --> 00:10:15.270 align:start position:0% very inefficient right because you have all<00:10:13.240> these<00:10:13.330> kind<00:10:13.540> of<00:10:13.600> wasted<00:10:13.990> bits<00:10:14.320> and<00:10:15.130> it 00:10:15.270 --> 00:10:15.280 align:start position:0% all these kind of wasted bits and it 00:10:15.280 --> 00:10:17.570 align:start position:0% all these kind of wasted bits and it doesn't<00:10:15.760> resemble<00:10:16.120> anything<00:10:16.570> like<00:10:16.900> an<00:10:16.990> actual 00:10:17.570 --> 00:10:17.580 align:start position:0% doesn't resemble anything like an actual 00:10:17.580 --> 00:10:19.770 align:start position:0% doesn't resemble anything like an actual hardware<00:10:18.580> instruction<00:10:19.000> set<00:10:19.210> whereas<00:10:19.510> in 00:10:19.770 --> 00:10:19.780 align:start position:0% hardware instruction set whereas in 00:10:19.780 --> 00:10:21.120 align:start position:0% hardware instruction set whereas in contrast<00:10:19.930> to<00:10:20.380> something<00:10:20.560> like<00:10:20.800> webassembly 00:10:21.120 --> 00:10:21.130 align:start position:0% contrast to something like webassembly 00:10:21.130 --> 00:10:22.530 align:start position:0% contrast to something like webassembly web<00:10:21.430> assemblies<00:10:21.820> very<00:10:22.030> close<00:10:22.240> to<00:10:22.390> actual 00:10:22.530 --> 00:10:22.540 align:start position:0% web assemblies very close to actual 00:10:22.540 --> 00:10:24.360 align:start position:0% web assemblies very close to actual hardware<00:10:23.050> is<00:10:23.410> that<00:10:23.589> sort<00:10:23.950> of<00:10:23.980> address<00:10:24.220> your 00:10:24.360 --> 00:10:24.370 align:start position:0% hardware is that sort of address your 00:10:24.370 --> 00:10:25.590 align:start position:0% hardware is that sort of address your concern<00:10:24.610> Boris<00:10:24.910> or<00:10:24.970> do<00:10:25.089> you<00:10:25.150> still<00:10:25.300> think<00:10:25.330> it's 00:10:25.590 --> 00:10:25.600 align:start position:0% concern Boris or do you still think it's 00:10:25.600 --> 00:10:39.010 align:start position:0% concern Boris or do you still think it's okay<00:10:25.960> cool<00:10:33.570> exactly<00:10:34.570> okay 00:10:39.010 --> 00:10:39.020 align:start position:0% 00:10:39.020 --> 00:10:43.730 align:start position:0% [Music] 00:10:43.730 --> 00:10:43.740 align:start position:0% 00:10:43.740 --> 00:10:46.230 align:start position:0% okay<00:10:44.740> so<00:10:44.800> just<00:10:45.009> to<00:10:45.069> restate<00:10:45.550> what<00:10:45.759> what<00:10:46.000> Boris 00:10:46.230 --> 00:10:46.240 align:start position:0% okay so just to restate what what Boris 00:10:46.240 --> 00:10:48.780 align:start position:0% okay so just to restate what what Boris said<00:10:46.420> for<00:10:46.930> I<00:10:46.959> guess<00:10:47.170> recording<00:10:47.649> and<00:10:47.800> Internet 00:10:48.780 --> 00:10:48.790 align:start position:0% said for I guess recording and Internet 00:10:48.790 --> 00:10:53.040 align:start position:0% said for I guess recording and Internet people's<00:10:49.230> the<00:10:50.519> EVM<00:10:51.550> is<00:10:51.790> a<00:10:52.360> very<00:10:52.630> well-designed 00:10:53.040 --> 00:10:53.050 align:start position:0% people's the EVM is a very well-designed 00:10:53.050 --> 00:10:55.470 align:start position:0% people's the EVM is a very well-designed VM<00:10:53.500> using<00:10:53.889> technology<00:10:54.370> that<00:10:54.399> sort<00:10:55.180> of<00:10:55.240> comes 00:10:55.470 --> 00:10:55.480 align:start position:0% VM using technology that sort of comes 00:10:55.480 --> 00:10:57.269 align:start position:0% VM using technology that sort of comes from<00:10:55.630> the<00:10:55.750> 1960s<00:10:56.350> and<00:10:56.560> that<00:10:56.709> we<00:10:56.769> could<00:10:56.920> develop 00:10:57.269 --> 00:10:57.279 align:start position:0% from the 1960s and that we could develop 00:10:57.279 --> 00:10:59.309 align:start position:0% from the 1960s and that we could develop a<00:10:57.459> much<00:10:57.579> better<00:10:57.730> VM<00:10:58.180> today<00:10:58.480> using<00:10:58.870> modern 00:10:59.309 --> 00:10:59.319 align:start position:0% a much better VM today using modern 00:10:59.319 --> 00:11:02.519 align:start position:0% a much better VM today using modern technology<00:10:59.769> it<00:11:00.639> also<00:11:00.819> has<00:11:01.240> a<00:11:01.269> very<00:11:01.990> clever 00:11:02.519 --> 00:11:02.529 align:start position:0% technology it also has a very clever 00:11:02.529 --> 00:11:05.100 align:start position:0% technology it also has a very clever feature<00:11:03.449> yeah 00:11:05.100 --> 00:11:05.110 align:start position:0% feature yeah 00:11:05.110 --> 00:11:08.850 align:start position:0% feature yeah called<00:11:05.440> the<00:11:05.620> dynamic<00:11:05.800> jump<00:11:06.569> which<00:11:07.569> back<00:11:07.930> in<00:11:08.290> I 00:11:08.850 --> 00:11:08.860 align:start position:0% called the dynamic jump which back in I 00:11:08.860 --> 00:11:11.850 align:start position:0% called the dynamic jump which back in I think<00:11:09.370> actually<00:11:09.579> 50s<00:11:10.480> Fortran<00:11:11.199> had<00:11:11.470> it<00:11:11.709> was 00:11:11.850 --> 00:11:11.860 align:start position:0% think actually 50s Fortran had it was 00:11:11.860 --> 00:11:15.210 align:start position:0% think actually 50s Fortran had it was called<00:11:12.160> a<00:11:12.310> computed<00:11:13.240> goto<00:11:13.480> in<00:11:14.350> which<00:11:14.800> you<00:11:14.980> can 00:11:15.210 --> 00:11:15.220 align:start position:0% called a computed goto in which you can 00:11:15.220 --> 00:11:17.670 align:start position:0% called a computed goto in which you can do<00:11:15.459> some<00:11:16.089> sort<00:11:16.269> of<00:11:16.420> rithmetic<00:11:16.990> that<00:11:17.470> says 00:11:17.670 --> 00:11:17.680 align:start position:0% do some sort of rithmetic that says 00:11:17.680 --> 00:11:19.620 align:start position:0% do some sort of rithmetic that says where<00:11:17.949> you<00:11:18.130> want<00:11:18.339> to<00:11:18.490> jump<00:11:18.790> and<00:11:19.060> then<00:11:19.120> you<00:11:19.389> jump 00:11:19.620 --> 00:11:19.630 align:start position:0% where you want to jump and then you jump 00:11:19.630 --> 00:11:22.680 align:start position:0% where you want to jump and then you jump why<00:11:20.050> is<00:11:20.110> that<00:11:20.199> a<00:11:20.319> bad<00:11:20.470> thing<00:11:20.730> because<00:11:21.730> when 00:11:22.680 --> 00:11:22.690 align:start position:0% why is that a bad thing because when 00:11:22.690 --> 00:11:24.960 align:start position:0% why is that a bad thing because when you're<00:11:22.870> doing<00:11:23.139> formal<00:11:23.410> analysis<00:11:24.279> you<00:11:24.579> get<00:11:24.790> to 00:11:24.960 --> 00:11:24.970 align:start position:0% you're doing formal analysis you get to 00:11:24.970 --> 00:11:27.449 align:start position:0% you're doing formal analysis you get to that<00:11:25.149> point<00:11:25.449> in<00:11:25.660> the<00:11:25.690> code<00:11:26.110> and<00:11:26.560> you<00:11:27.040> want<00:11:27.279> to 00:11:27.449 --> 00:11:27.459 align:start position:0% that point in the code and you want to 00:11:27.459 --> 00:11:31.350 align:start position:0% that point in the code and you want to say<00:11:28.259> well<00:11:29.259> where's<00:11:29.589> this<00:11:29.860> jump<00:11:30.190> go<00:11:30.459> and<00:11:31.120> the 00:11:31.350 --> 00:11:31.360 align:start position:0% say well where's this jump go and the 00:11:31.360 --> 00:11:34.559 align:start position:0% say well where's this jump go and the answer<00:11:31.750> is<00:11:31.959> it<00:11:32.649> can<00:11:32.920> go<00:11:33.100> anywhere<00:11:34.060> in<00:11:34.269> the 00:11:34.559 --> 00:11:34.569 align:start position:0% answer is it can go anywhere in the 00:11:34.569 --> 00:11:41.309 align:start position:0% answer is it can go anywhere in the program<00:11:35.050> and<00:11:37.319> when<00:11:38.319> I<00:11:38.350> I<00:11:39.899> you<00:11:40.899> know<00:11:40.959> I'd<00:11:41.110> done 00:11:41.309 --> 00:11:41.319 align:start position:0% program and when I I you know I'd done 00:11:41.319 --> 00:11:44.069 align:start position:0% program and when I I you know I'd done one<00:11:41.620> round<00:11:41.920> of<00:11:42.120> optimization<00:11:43.120> I<00:11:43.360> think<00:11:43.630> about 00:11:44.069 --> 00:11:44.079 align:start position:0% one round of optimization I think about 00:11:44.079 --> 00:11:46.230 align:start position:0% one round of optimization I think about doubled<00:11:44.620> the<00:11:44.800> speed<00:11:45.009> of<00:11:45.250> the<00:11:45.370> interpreter<00:11:46.000> and 00:11:46.230 --> 00:11:46.240 align:start position:0% doubled the speed of the interpreter and 00:11:46.240 --> 00:11:48.990 align:start position:0% doubled the speed of the interpreter and then<00:11:46.990> I<00:11:47.019> wanted<00:11:47.560> to<00:11:47.620> do<00:11:47.860> the<00:11:48.040> next<00:11:48.279> round<00:11:48.579> to 00:11:48.990 --> 00:11:49.000 align:start position:0% then I wanted to do the next round to 00:11:49.000 --> 00:11:52.160 align:start position:0% then I wanted to do the next round to apply<00:11:49.329> some<00:11:49.689> techniques<00:11:50.259> that<00:11:50.620> I'd<00:11:51.189> invented 00:11:52.160 --> 00:11:52.170 align:start position:0% apply some techniques that I'd invented 00:11:52.170 --> 00:11:55.350 align:start position:0% apply some techniques that I'd invented in<00:11:53.170> optimizing<00:11:53.740> the<00:11:54.310> interpreter<00:11:55.000> in<00:11:55.329> the 00:11:55.350 --> 00:11:55.360 align:start position:0% in optimizing the interpreter in the 00:11:55.360 --> 00:12:00.150 align:start position:0% in optimizing the interpreter in the Oracle<00:11:56.230> kernel<00:11:56.920> and<00:11:58.199> came<00:11:59.199> around<00:11:59.410> and<00:11:59.980> went 00:12:00.150 --> 00:12:00.160 align:start position:0% Oracle kernel and came around and went 00:12:00.160 --> 00:12:03.059 align:start position:0% Oracle kernel and came around and went uh-oh<00:12:00.610> and<00:12:01.480> I<00:12:01.660> showed<00:12:01.899> it<00:12:02.110> to<00:12:02.139> Christian<00:12:02.829> and 00:12:03.059 --> 00:12:03.069 align:start position:0% uh-oh and I showed it to Christian and 00:12:03.069 --> 00:12:05.429 align:start position:0% uh-oh and I showed it to Christian and he<00:12:03.189> said<00:12:03.490> well<00:12:04.089> of<00:12:04.300> course<00:12:04.329> because<00:12:05.139> of<00:12:05.319> the 00:12:05.429 --> 00:12:05.439 align:start position:0% he said well of course because of the 00:12:05.439 --> 00:12:07.679 align:start position:0% he said well of course because of the damage<00:12:05.800> jump<00:12:06.220> you<00:12:06.459> don't<00:12:06.699> know<00:12:06.910> what<00:12:07.240> level<00:12:07.449> of 00:12:07.679 --> 00:12:07.689 align:start position:0% damage jump you don't know what level of 00:12:07.689 --> 00:12:13.530 align:start position:0% damage jump you don't know what level of the<00:12:07.810> stack<00:12:08.050> you're<00:12:08.350> at<00:12:08.500> I'm<00:12:09.189> going<00:12:10.259> sheep<00:12:12.540> and 00:12:13.530 --> 00:12:13.540 align:start position:0% the stack you're at I'm going sheep and 00:12:13.540 --> 00:12:16.559 align:start position:0% the stack you're at I'm going sheep and stronger<00:12:14.230> words<00:12:14.470> than<00:12:14.589> that<00:12:14.769> and<00:12:15.550> that's<00:12:15.880> then 00:12:16.559 --> 00:12:16.569 align:start position:0% stronger words than that and that's then 00:12:16.569 --> 00:12:19.290 align:start position:0% stronger words than that and that's then I<00:12:16.600> started<00:12:17.139> going<00:12:17.290> okay<00:12:18.160> how<00:12:18.550> do<00:12:18.610> I<00:12:18.759> fix<00:12:19.120> this 00:12:19.290 --> 00:12:19.300 align:start position:0% I started going okay how do I fix this 00:12:19.300 --> 00:12:23.460 align:start position:0% I started going okay how do I fix this and<00:12:20.250> discovered<00:12:21.250> it's<00:12:21.699> like<00:12:22.449> there's<00:12:23.290> no 00:12:23.460 --> 00:12:23.470 align:start position:0% and discovered it's like there's no 00:12:23.470 --> 00:12:27.600 align:start position:0% and discovered it's like there's no basic<00:12:23.949> subroutine<00:12:25.589> you<00:12:26.589> know<00:12:26.680> just<00:12:26.949> a<00:12:27.130> sub 00:12:27.600 --> 00:12:27.610 align:start position:0% basic subroutine you know just a sub 00:12:27.610 --> 00:12:31.170 align:start position:0% basic subroutine you know just a sub instruction<00:12:28.509> and<00:12:29.079> even<00:12:29.470> in<00:12:29.620> the<00:12:29.740> 60s<00:12:30.279> and<00:12:30.699> even 00:12:31.170 --> 00:12:31.180 align:start position:0% instruction and even in the 60s and even 00:12:31.180 --> 00:12:34.230 align:start position:0% instruction and even in the 60s and even in<00:12:31.389> the<00:12:31.660> 50s<00:12:32.110> most<00:12:32.459> computer<00:12:33.459> architectures 00:12:34.230 --> 00:12:34.240 align:start position:0% in the 50s most computer architectures 00:12:34.240 --> 00:12:37.439 align:start position:0% in the 50s most computer architectures had<00:12:34.480> some<00:12:35.170> sort<00:12:35.470> of<00:12:35.529> instruction<00:12:36.250> for<00:12:36.550> for 00:12:37.439 --> 00:12:37.449 align:start position:0% had some sort of instruction for for 00:12:37.449 --> 00:12:41.970 align:start position:0% had some sort of instruction for for making<00:12:37.750> subroutines<00:12:38.410> and<00:12:39.839> the<00:12:40.839> idea<00:12:41.199> was<00:12:41.470> well 00:12:41.970 --> 00:12:41.980 align:start position:0% making subroutines and the idea was well 00:12:41.980 --> 00:12:43.530 align:start position:0% making subroutines and the idea was well you<00:12:42.339> can<00:12:42.519> make<00:12:42.639> those<00:12:42.850> out<00:12:43.029> of<00:12:43.180> the<00:12:43.240> dynamic 00:12:43.530 --> 00:12:43.540 align:start position:0% you can make those out of the dynamic 00:12:43.540 --> 00:12:46.500 align:start position:0% you can make those out of the dynamic jumps<00:12:44.170> and<00:12:44.350> if<00:12:45.130> you<00:12:45.279> ever<00:12:45.399> look<00:12:45.550> at<00:12:46.059> the<00:12:46.120> code 00:12:46.500 --> 00:12:46.510 align:start position:0% jumps and if you ever look at the code 00:12:46.510 --> 00:12:48.510 align:start position:0% jumps and if you ever look at the code this<00:12:46.809> solidity<00:12:47.380> generates 00:12:48.510 --> 00:12:48.520 align:start position:0% this solidity generates 00:12:48.520 --> 00:12:55.200 align:start position:0% this solidity generates for<00:12:48.700> calling<00:12:49.210> a<00:12:49.330> function<00:12:49.950> it's<00:12:52.740> just<00:12:54.210> it's 00:12:55.200 --> 00:12:55.210 align:start position:0% for calling a function it's just it's 00:12:55.210 --> 00:12:56.040 align:start position:0% for calling a function it's just it's pretty<00:12:55.480> ugly 00:12:56.040 --> 00:12:56.050 align:start position:0% pretty ugly 00:12:56.050 --> 00:12:58.950 align:start position:0% pretty ugly so<00:12:56.830> my<00:12:57.250> next<00:12:57.310> sorry<00:12:58.150> I<00:12:58.180> gotta<00:12:58.360> follow<00:12:58.780> up 00:12:58.950 --> 00:12:58.960 align:start position:0% so my next sorry I gotta follow up 00:12:58.960 --> 00:13:02.240 align:start position:0% so my next sorry I gotta follow up question<00:12:59.320> Pablo<00:13:00.060> you<00:13:01.060> said<00:13:01.240> earlier<00:13:01.540> that<00:13:01.600> you 00:13:02.240 --> 00:13:02.250 align:start position:0% question Pablo you said earlier that you 00:13:02.250 --> 00:13:04.620 align:start position:0% question Pablo you said earlier that you suggested<00:13:03.250> some<00:13:03.490> small<00:13:04.000> but<00:13:04.180> important 00:13:04.620 --> 00:13:04.630 align:start position:0% suggested some small but important 00:13:04.630 --> 00:13:09.030 align:start position:0% suggested some small but important changes<00:13:04.990> to<00:13:05.200> the<00:13:05.320> EVM<00:13:06.930> before<00:13:07.930> you<00:13:08.800> know 00:13:09.030 --> 00:13:09.040 align:start position:0% changes to the EVM before you know 00:13:09.040 --> 00:13:13.140 align:start position:0% changes to the EVM before you know Genisys<00:13:09.430> launched<00:13:09.670> in<00:13:10.210> 2015<00:13:11.520> was<00:13:12.520> the<00:13:12.730> dynamic 00:13:13.140 --> 00:13:13.150 align:start position:0% Genisys launched in 2015 was the dynamic 00:13:13.150 --> 00:13:15.810 align:start position:0% Genisys launched in 2015 was the dynamic jump<00:13:13.630> on<00:13:13.840> your<00:13:14.110> radar<00:13:14.470> yeah<00:13:15.250> that's<00:13:15.550> what's 00:13:15.810 --> 00:13:15.820 align:start position:0% jump on your radar yeah that's what's 00:13:15.820 --> 00:13:18.690 align:start position:0% jump on your radar yeah that's what's the<00:13:15.940> problem<00:13:16.360> so<00:13:16.720> even<00:13:17.410> before<00:13:17.560> it<00:13:17.980> was<00:13:18.010> the 00:13:18.690 --> 00:13:18.700 align:start position:0% the problem so even before it was the 00:13:18.700 --> 00:13:22.200 align:start position:0% the problem so even before it was the situation<00:13:19.240> was<00:13:19.450> much<00:13:19.870> worse<00:13:20.230> because<00:13:21.000> now<00:13:22.000> at 00:13:22.200 --> 00:13:22.210 align:start position:0% situation was much worse because now at 00:13:22.210 --> 00:13:25.740 align:start position:0% situation was much worse because now at least<00:13:22.450> you<00:13:22.690> have<00:13:23.940> specified<00:13:24.940> what<00:13:25.510> are 00:13:25.740 --> 00:13:25.750 align:start position:0% least you have specified what are 00:13:25.750 --> 00:13:29.220 align:start position:0% least you have specified what are possible<00:13:27.000> destinations<00:13:28.000> for<00:13:28.210> jump<00:13:28.510> so<00:13:29.170> you 00:13:29.220 --> 00:13:29.230 align:start position:0% possible destinations for jump so you 00:13:29.230 --> 00:13:32.130 align:start position:0% possible destinations for jump so you have<00:13:29.470> special<00:13:29.980> jump<00:13:30.430> this<00:13:30.640> instruction<00:13:31.300> so 00:13:32.130 --> 00:13:32.140 align:start position:0% have special jump this instruction so 00:13:32.140 --> 00:13:34.410 align:start position:0% have special jump this instruction so these<00:13:32.440> are<00:13:32.650> valid<00:13:33.100> places<00:13:33.970> where<00:13:34.150> you<00:13:34.270> can 00:13:34.410 --> 00:13:34.420 align:start position:0% these are valid places where you can 00:13:34.420 --> 00:13:37.560 align:start position:0% these are valid places where you can jump<00:13:34.690> to<00:13:35.220> before<00:13:36.220> that<00:13:36.430> there<00:13:36.670> was<00:13:36.790> no<00:13:37.030> such 00:13:37.560 --> 00:13:37.570 align:start position:0% jump to before that there was no such 00:13:37.570 --> 00:13:40.400 align:start position:0% jump to before that there was no such thing<00:13:37.600> so<00:13:37.900> you<00:13:38.260> can<00:13:38.440> drop<00:13:38.620> anywhere<00:13:39.150> including 00:13:40.400 --> 00:13:40.410 align:start position:0% thing so you can drop anywhere including 00:13:40.410 --> 00:13:44.040 align:start position:0% thing so you can drop anywhere including data<00:13:41.410> from<00:13:41.620> push<00:13:42.100> even<00:13:42.850> so<00:13:43.450> you<00:13:43.510> can<00:13:43.720> execute 00:13:44.040 --> 00:13:44.050 align:start position:0% data from push even so you can execute 00:13:44.050 --> 00:13:49.710 align:start position:0% data from push even so you can execute code<00:13:44.530> in<00:13:45.160> push<00:13:45.490> data<00:13:45.850> and<00:13:46.300> like<00:13:47.190> so<00:13:48.480> before<00:13:49.480> it 00:13:49.710 --> 00:13:49.720 align:start position:0% code in push data and like so before it 00:13:49.720 --> 00:13:54.050 align:start position:0% code in push data and like so before it was<00:13:49.900> impossible<00:13:50.620> to<00:13:51.010> have<00:13:51.550> any<00:13:52.920> other 00:13:54.050 --> 00:13:54.060 align:start position:0% was impossible to have any other 00:13:54.060 --> 00:13:57.360 align:start position:0% was impossible to have any other translation<00:13:55.060> further<00:13:55.900> translation<00:13:56.620> of<00:13:56.740> EVM 00:13:57.360 --> 00:13:57.370 align:start position:0% translation further translation of EVM 00:13:57.370 --> 00:14:01.080 align:start position:0% translation further translation of EVM bytecode<00:13:57.910> so<00:13:58.900> that<00:13:59.140> this<00:13:59.620> like<00:14:00.190> allows<00:14:00.640> some 00:14:01.080 --> 00:14:01.090 align:start position:0% bytecode so that this like allows some 00:14:01.090 --> 00:14:04.800 align:start position:0% bytecode so that this like allows some some<00:14:02.050> way<00:14:02.230> of<00:14:02.440> compiling<00:14:03.280> EVM<00:14:04.150> byte<00:14:04.330> code<00:14:04.600> to 00:14:04.800 --> 00:14:04.810 align:start position:0% some way of compiling EVM byte code to 00:14:04.810 --> 00:14:06.990 align:start position:0% some way of compiling EVM byte code to machine<00:14:04.930> code<00:14:05.320> because<00:14:06.160> on<00:14:06.490> this<00:14:06.820> machine 00:14:06.990 --> 00:14:07.000 align:start position:0% machine code because on this machine 00:14:07.000 --> 00:14:09.090 align:start position:0% machine code because on this machine code<00:14:07.360> level<00:14:07.450> you<00:14:07.840> are<00:14:07.990> not<00:14:08.200> allowed<00:14:08.500> to<00:14:08.530> do<00:14:08.920> I 00:14:09.090 --> 00:14:09.100 align:start position:0% code level you are not allowed to do I 00:14:09.100 --> 00:14:11.970 align:start position:0% code level you are not allowed to do I mean<00:14:09.280> this<00:14:09.610> own<00:14:09.940> way<00:14:10.180> but<00:14:10.620> that<00:14:11.620> would<00:14:11.830> be 00:14:11.970 --> 00:14:11.980 align:start position:0% mean this own way but that would be 00:14:11.980 --> 00:14:13.950 align:start position:0% mean this own way but that would be horrible<00:14:12.160> so<00:14:12.820> yeah<00:14:13.090> that's<00:14:13.360> that<00:14:13.450> was<00:14:13.780> that 00:14:13.950 --> 00:14:13.960 align:start position:0% horrible so yeah that's that was that 00:14:13.960 --> 00:14:17.280 align:start position:0% horrible so yeah that's that was that was<00:14:14.140> the<00:14:14.170> change<00:14:14.530> and<00:14:15.600> destination<00:14:16.600> it<00:14:16.930> kind 00:14:17.280 --> 00:14:17.290 align:start position:0% was the change and destination it kind 00:14:17.290 --> 00:14:20.430 align:start position:0% was the change and destination it kind of<00:14:17.380> like<00:14:17.650> a<00:14:17.980> joint<00:14:18.880> quite<00:14:19.360> late<00:14:19.720> during<00:14:20.140> the 00:14:20.430 --> 00:14:20.440 align:start position:0% of like a joint quite late during the 00:14:20.440 --> 00:14:24.330 align:start position:0% of like a joint quite late during the process<00:14:20.920> and<00:14:21.190> also<00:14:21.880> I<00:14:22.240> didn't<00:14:22.810> know<00:14:22.930> much<00:14:23.140> as<00:14:23.590> I 00:14:24.330 --> 00:14:24.340 align:start position:0% process and also I didn't know much as I 00:14:24.340 --> 00:14:26.910 align:start position:0% process and also I didn't know much as I know<00:14:24.400> now<00:14:24.730> and<00:14:25.150> like<00:14:25.810> didn't<00:14:26.350> have<00:14:26.470> courage<00:14:26.740> to 00:14:26.910 --> 00:14:26.920 align:start position:0% know now and like didn't have courage to 00:14:26.920 --> 00:14:29.820 align:start position:0% know now and like didn't have courage to to<00:14:27.820> change<00:14:28.090> into<00:14:28.390> something<00:14:28.630> like<00:14:28.900> better 00:14:29.820 --> 00:14:29.830 align:start position:0% to change into something like better 00:14:29.830 --> 00:14:34.830 align:start position:0% to change into something like better behaving<00:14:31.020> although<00:14:32.020> we<00:14:32.260> had<00:14:32.500> like<00:14:33.840> JVM 00:14:34.830 --> 00:14:34.840 align:start position:0% behaving although we had like JVM 00:14:34.840 --> 00:14:38.480 align:start position:0% behaving although we had like JVM example<00:14:35.470> when<00:14:35.650> there<00:14:36.340> is<00:14:36.490> like<00:14:36.880> it's<00:14:37.570> fixed 00:14:38.480 --> 00:14:38.490 align:start position:0% example when there is like it's fixed 00:14:38.490 --> 00:14:42.690 align:start position:0% example when there is like it's fixed it's<00:14:39.490> fixed<00:14:39.660> how<00:14:40.660> like<00:14:41.560> what<00:14:41.950> what<00:14:42.310> the<00:14:42.430> stack 00:14:42.690 --> 00:14:42.700 align:start position:0% it's fixed how like what what the stack 00:14:42.700 --> 00:14:44.700 align:start position:0% it's fixed how like what what the stack height<00:14:42.970> can<00:14:43.210> be<00:14:43.390> on<00:14:43.600> when<00:14:44.170> you<00:14:44.290> enter<00:14:44.320> the 00:14:44.700 --> 00:14:44.710 align:start position:0% height can be on when you enter the 00:14:44.710 --> 00:14:48.150 align:start position:0% height can be on when you enter the function<00:14:44.920> what<00:14:45.520> yeah<00:14:46.390> so<00:14:46.600> kind<00:14:46.930> of<00:14:47.050> like<00:14:47.890> yeah 00:14:48.150 --> 00:14:48.160 align:start position:0% function what yeah so kind of like yeah 00:14:48.160 --> 00:14:52.020 align:start position:0% function what yeah so kind of like yeah this<00:14:48.340> is<00:14:48.400> this<00:14:48.760> is<00:14:48.820> missing<00:14:49.560> definitely<00:14:51.030> we're 00:14:52.020 --> 00:14:52.030 align:start position:0% this is this is missing definitely we're 00:14:52.030 --> 00:14:54.240 align:start position:0% this is this is missing definitely we're getting<00:14:52.360> deeply<00:14:52.870> technical<00:14:53.110> here<00:14:53.740> I<00:14:53.920> don't 00:14:54.240 --> 00:14:54.250 align:start position:0% getting deeply technical here I don't 00:14:54.250 --> 00:14:56.910 align:start position:0% getting deeply technical here I don't know<00:14:54.660> some<00:14:55.660> people<00:14:55.870> are<00:14:56.170> probably<00:14:56.380> excited 00:14:56.910 --> 00:14:56.920 align:start position:0% know some people are probably excited 00:14:56.920 --> 00:14:59.310 align:start position:0% know some people are probably excited and<00:14:57.370> some<00:14:57.610> people<00:14:58.000> are<00:14:58.150> just 00:14:59.310 --> 00:14:59.320 align:start position:0% and some people are just 00:14:59.320 --> 00:15:01.230 align:start position:0% and some people are just we<00:15:00.070> have<00:15:00.190> to<00:15:00.310> have<00:15:00.459> at<00:15:00.550> least<00:15:00.639> one<00:15:00.850> nerd<00:15:01.029> in<00:15:01.149> the 00:15:01.230 --> 00:15:01.240 align:start position:0% we have to have at least one nerd in the 00:15:01.240 --> 00:15:03.600 align:start position:0% we have to have at least one nerd in the room<00:15:01.389> yeah<00:15:02.139> we'll<00:15:02.440> save<00:15:02.649> tons<00:15:03.040> of<00:15:03.220> time<00:15:03.279> for 00:15:03.600 --> 00:15:03.610 align:start position:0% room yeah we'll save tons of time for 00:15:03.610 --> 00:15:04.319 align:start position:0% room yeah we'll save tons of time for questions 00:15:04.319 --> 00:15:04.329 align:start position:0% questions 00:15:04.329 --> 00:15:07.470 align:start position:0% questions another<00:15:04.720> problem<00:15:05.440> is<00:15:05.709> that<00:15:06.339> you<00:15:06.670> can<00:15:06.970> you 00:15:07.470 --> 00:15:07.480 align:start position:0% another problem is that you can you 00:15:07.480 --> 00:15:10.079 align:start position:0% another problem is that you can you can't<00:15:07.810> optimize<00:15:08.259> this<00:15:08.740> the<00:15:09.190> compiler<00:15:09.759> can 00:15:10.079 --> 00:15:10.089 align:start position:0% can't optimize this the compiler can 00:15:10.089 --> 00:15:13.560 align:start position:0% can't optimize this the compiler can look<00:15:10.329> and<00:15:10.570> go<00:15:10.779> well<00:15:11.500> yes<00:15:11.889> you're<00:15:12.190> using<00:15:12.570> 256 00:15:13.560 --> 00:15:13.570 align:start position:0% look and go well yes you're using 256 00:15:13.570 --> 00:15:15.540 align:start position:0% look and go well yes you're using 256 bit<00:15:13.779> registers<00:15:14.440> but<00:15:14.949> there's<00:15:15.160> instructions 00:15:15.540 --> 00:15:15.550 align:start position:0% bit registers but there's instructions 00:15:15.550 --> 00:15:19.290 align:start position:0% bit registers but there's instructions like<00:15:16.149> add<00:15:16.480> mod<00:15:16.810> and<00:15:17.380> mall<00:15:17.680> mod<00:15:17.949> so<00:15:18.670> you<00:15:18.730> can<00:15:19.060> say 00:15:19.290 --> 00:15:19.300 align:start position:0% like add mod and mall mod so you can say 00:15:19.300 --> 00:15:22.590 align:start position:0% like add mod and mall mod so you can say that<00:15:19.630> really<00:15:19.839> I'm<00:15:20.170> operating<00:15:20.560> but<00:15:21.130> at<00:15:21.430> 250<00:15:22.149> I'm 00:15:22.590 --> 00:15:22.600 align:start position:0% that really I'm operating but at 250 I'm 00:15:22.600 --> 00:15:25.769 align:start position:0% that really I'm operating but at 250 I'm only<00:15:22.870> using<00:15:23.170> 64<00:15:24.040> of<00:15:24.190> these<00:15:24.339> bits<00:15:24.639> the<00:15:25.389> compiler 00:15:25.769 --> 00:15:25.779 align:start position:0% only using 64 of these bits the compiler 00:15:25.779 --> 00:15:29.490 align:start position:0% only using 64 of these bits the compiler can<00:15:26.139> generate<00:15:26.620> 64-bit<00:15:27.579> code<00:15:27.819> but<00:15:28.300> tough<00:15:29.050> we're 00:15:29.490 --> 00:15:29.500 align:start position:0% can generate 64-bit code but tough we're 00:15:29.500 --> 00:15:31.920 align:start position:0% can generate 64-bit code but tough we're still<00:15:29.680> going<00:15:29.860> to<00:15:29.949> charge<00:15:30.220> you<00:15:30.399> gas<00:15:30.670> as<00:15:31.120> if<00:15:31.750> you 00:15:31.920 --> 00:15:31.930 align:start position:0% still going to charge you gas as if you 00:15:31.930 --> 00:15:34.139 align:start position:0% still going to charge you gas as if you were<00:15:32.079> working<00:15:32.259> with<00:15:32.670> 256<00:15:33.670> bits 00:15:34.139 --> 00:15:34.149 align:start position:0% were working with 256 bits 00:15:34.149 --> 00:15:37.230 align:start position:0% were working with 256 bits I<00:15:34.360> think<00:15:35.259> only<00:15:35.470> in<00:15:35.769> the<00:15:35.889> last<00:15:36.069> month<00:15:36.550> I<00:15:36.819> think<00:15:37.089> I 00:15:37.230 --> 00:15:37.240 align:start position:0% I think only in the last month I think I 00:15:37.240 --> 00:15:39.930 align:start position:0% I think only in the last month I think I figured<00:15:37.480> out<00:15:37.779> a<00:15:37.810> way<00:15:38.050> to<00:15:38.079> fix<00:15:38.500> that<00:15:38.889> looking<00:15:39.759> at 00:15:39.930 --> 00:15:39.940 align:start position:0% figured out a way to fix that looking at 00:15:39.940 --> 00:15:43.290 align:start position:0% figured out a way to fix that looking at the<00:15:40.120> work<00:15:40.860> that's<00:15:41.860> being<00:15:42.069> done<00:15:42.160> on<00:15:42.310> the<00:15:42.610> I<00:15:42.639> le 00:15:43.290 --> 00:15:43.300 align:start position:0% the work that's being done on the I le 00:15:43.300 --> 00:15:46.139 align:start position:0% the work that's being done on the I le virtual<00:15:43.899> machine<00:15:44.459> through<00:15:45.459> procore<00:15:45.819> and 00:15:46.139 --> 00:15:46.149 align:start position:0% virtual machine through procore and 00:15:46.149 --> 00:15:48.329 align:start position:0% virtual machine through procore and other<00:15:46.300> people<00:15:46.810> of<00:15:46.930> runtime<00:15:47.339> verification 00:15:48.329 --> 00:15:48.339 align:start position:0% other people of runtime verification 00:15:48.339 --> 00:15:50.519 align:start position:0% other people of runtime verification I've<00:15:48.670> been<00:15:48.880> working<00:15:49.300> on<00:15:49.509> the<00:15:50.079> lab<00:15:50.230> and<00:15:50.440> that 00:15:50.519 --> 00:15:50.529 align:start position:0% I've been working on the lab and that 00:15:50.529 --> 00:15:52.410 align:start position:0% I've been working on the lab and that time<00:15:50.769> to<00:15:50.949> talk<00:15:51.130> to<00:15:51.370> anyone<00:15:51.730> and<00:15:51.970> write<00:15:52.209> up 00:15:52.410 --> 00:15:52.420 align:start position:0% time to talk to anyone and write up 00:15:52.420 --> 00:15:55.410 align:start position:0% time to talk to anyone and write up right<00:15:52.810> in<00:15:52.959> the<00:15:52.990> IP<00:15:53.259> on<00:15:53.589> that<00:15:53.920> but<00:15:54.639> basically<00:15:54.819> to 00:15:55.410 --> 00:15:55.420 align:start position:0% right in the IP on that but basically to 00:15:55.420 --> 00:15:58.499 align:start position:0% right in the IP on that but basically to charge<00:15:55.720> the<00:15:56.019> gas<00:15:56.259> based<00:15:57.069> on<00:15:57.430> how<00:15:57.880> wide<00:15:58.149> you 00:15:58.499 --> 00:15:58.509 align:start position:0% charge the gas based on how wide you 00:15:58.509 --> 00:16:04.829 align:start position:0% charge the gas based on how wide you actually<00:15:58.990> know<00:16:02.850> what<00:16:03.850> you<00:16:04.029> can<00:16:04.240> tell<00:16:04.420> is<00:16:04.690> the 00:16:04.829 --> 00:16:04.839 align:start position:0% actually know what you can tell is the 00:16:04.839 --> 00:16:07.740 align:start position:0% actually know what you can tell is the maximum<00:16:05.410> with<00:16:05.620> the<00:16:05.829> register<00:16:06.430> you<00:16:06.459> need<00:16:06.750> so 00:16:07.740 --> 00:16:07.750 align:start position:0% maximum with the register you need so 00:16:07.750 --> 00:16:09.720 align:start position:0% maximum with the register you need so there's<00:16:08.319> basically<00:16:08.500> things<00:16:09.220> that<00:16:09.310> can<00:16:09.579> be 00:16:09.720 --> 00:16:09.730 align:start position:0% there's basically things that can be 00:16:09.730 --> 00:16:14.220 align:start position:0% there's basically things that can be fixed<00:16:10.089> and<00:16:10.420> we<00:16:10.630> think<00:16:12.540> Boris<00:16:13.540> who<00:16:13.779> just<00:16:14.050> spoke 00:16:14.220 --> 00:16:14.230 align:start position:0% fixed and we think Boris who just spoke 00:16:14.230 --> 00:16:16.710 align:start position:0% fixed and we think Boris who just spoke up<00:16:14.560> there<00:16:14.980> and<00:16:15.250> I<00:16:15.519> don't<00:16:15.699> know<00:16:15.970> if<00:16:16.240> Brooke<00:16:16.540> is 00:16:16.710 --> 00:16:16.720 align:start position:0% up there and I don't know if Brooke is 00:16:16.720 --> 00:16:19.259 align:start position:0% up there and I don't know if Brooke is still<00:16:17.050> around<00:16:17.350> or<00:16:17.649> not<00:16:17.800> she's<00:16:18.730> she's<00:16:19.120> an 00:16:19.259 --> 00:16:19.269 align:start position:0% still around or not she's she's an 00:16:19.269 --> 00:16:23.370 align:start position:0% still around or not she's she's an amazing<00:16:19.779> formalist<00:16:22.019> she's<00:16:23.019> going<00:16:23.230> to<00:16:23.290> be 00:16:23.370 --> 00:16:23.380 align:start position:0% amazing formalist she's going to be 00:16:23.380 --> 00:16:27.629 align:start position:0% amazing formalist she's going to be humble<00:16:23.829> there<00:16:26.160> before<00:16:27.160> you<00:16:27.220> go<00:16:27.310> any<00:16:27.459> further 00:16:27.629 --> 00:16:27.639 align:start position:0% humble there before you go any further 00:16:27.639 --> 00:16:30.720 align:start position:0% humble there before you go any further I'm<00:16:28.000> wanted<00:16:28.630> to<00:16:28.690> reflect<00:16:28.930> on<00:16:29.199> part<00:16:29.649> mm-hmm 00:16:30.720 --> 00:16:30.730 align:start position:0% I'm wanted to reflect on part mm-hmm 00:16:30.730 --> 00:16:33.300 align:start position:0% I'm wanted to reflect on part mm-hmm you<00:16:31.420> said<00:16:31.660> that<00:16:31.899> maybe<00:16:32.199> specified<00:16:32.889> the<00:16:33.069> actual 00:16:33.300 --> 00:16:33.310 align:start position:0% you said that maybe specified the actual 00:16:33.310 --> 00:16:36.170 align:start position:0% you said that maybe specified the actual width<00:16:33.550> of<00:16:33.850> the<00:16:34.209> data<00:16:34.480> you<00:16:34.690> want<00:16:34.839> to<00:16:34.959> apply<00:16:35.889> the 00:16:36.170 --> 00:16:36.180 align:start position:0% width of the data you want to apply the 00:16:36.180 --> 00:16:38.970 align:start position:0% width of the data you want to apply the computation<00:16:37.180> on<00:16:37.269> and<00:16:37.709> there's<00:16:38.709> just<00:16:38.949> one 00:16:38.970 --> 00:16:38.980 align:start position:0% computation on and there's just one 00:16:38.980 --> 00:16:40.769 align:start position:0% computation on and there's just one thanks<00:16:39.550> to<00:16:39.579> you<00:16:39.790> two<00:16:40.089> worth<00:16:40.329> mentioning<00:16:40.720> here 00:16:40.769 --> 00:16:40.779 align:start position:0% thanks to you two worth mentioning here 00:16:40.779 --> 00:16:43.410 align:start position:0% thanks to you two worth mentioning here and<00:16:41.279> currently<00:16:42.279> the<00:16:42.459> instruction<00:16:42.880> set<00:16:43.120> looks 00:16:43.410 --> 00:16:43.420 align:start position:0% and currently the instruction set looks 00:16:43.420 --> 00:16:46.290 align:start position:0% and currently the instruction set looks like<00:16:43.630> s<00:16:44.490> there's<00:16:45.490> a<00:16:45.550> single<00:16:45.939> instruction 00:16:46.290 --> 00:16:46.300 align:start position:0% like s there's a single instruction 00:16:46.300 --> 00:16:48.240 align:start position:0% like s there's a single instruction which<00:16:46.660> can<00:16:46.930> have<00:16:47.139> an<00:16:47.260> immediate<00:16:47.680> value<00:16:47.860> and 00:16:48.240 --> 00:16:48.250 align:start position:0% which can have an immediate value and 00:16:48.250 --> 00:16:50.340 align:start position:0% which can have an immediate value and that<00:16:48.370> is<00:16:48.519> the<00:16:48.639> push<00:16:48.819> instruction<00:16:49.420> no<00:16:50.199> other 00:16:50.340 --> 00:16:50.350 align:start position:0% that is the push instruction no other 00:16:50.350 --> 00:16:52.079 align:start position:0% that is the push instruction no other instruction<00:16:50.920> cap<00:16:51.189> can<00:16:51.550> have<00:16:51.670> immediate 00:16:52.079 --> 00:16:52.089 align:start position:0% instruction cap can have immediate 00:16:52.089 --> 00:16:54.449 align:start position:0% instruction cap can have immediate values<00:16:52.529> every<00:16:53.529> single<00:16:53.800> other<00:16:53.889> instruction<00:16:54.370> is 00:16:54.449 --> 00:16:54.459 align:start position:0% values every single other instruction is 00:16:54.459 --> 00:16:56.249 align:start position:0% values every single other instruction is just<00:16:54.670> operating<00:16:54.850> on<00:16:55.089> the<00:16:55.209> stack<00:16:55.449> and<00:16:55.689> there 00:16:56.249 --> 00:16:56.259 align:start position:0% just operating on the stack and there 00:16:56.259 --> 00:16:57.929 align:start position:0% just operating on the stack and there were<00:16:56.380> a<00:16:56.410> couple<00:16:56.500> of<00:16:56.800> different<00:16:56.949> proposals<00:16:57.639> to 00:16:57.929 --> 00:16:57.939 align:start position:0% were a couple of different proposals to 00:16:57.939 --> 00:17:00.509 align:start position:0% were a couple of different proposals to augment<00:16:58.720> other<00:16:59.380> instructions<00:17:00.040> to<00:17:00.310> have 00:17:00.509 --> 00:17:00.519 align:start position:0% augment other instructions to have 00:17:00.519 --> 00:17:03.030 align:start position:0% augment other instructions to have immediate<00:17:00.939> values<00:17:01.300> or<00:17:02.170> have<00:17:02.380> like<00:17:02.560> multi<00:17:02.889> byte 00:17:03.030 --> 00:17:03.040 align:start position:0% immediate values or have like multi byte 00:17:03.040 --> 00:17:04.860 align:start position:0% immediate values or have like multi byte codes<00:17:03.339> op<00:17:03.579> codes<00:17:03.910> to<00:17:04.150> encode<00:17:04.419> you<00:17:04.750> know 00:17:04.860 --> 00:17:04.870 align:start position:0% codes op codes to encode you know 00:17:04.870 --> 00:17:07.649 align:start position:0% codes op codes to encode you know different<00:17:05.230> behaviors<00:17:05.970> and<00:17:06.970> there<00:17:07.179> was<00:17:07.299> a<00:17:07.329> big 00:17:07.649 --> 00:17:07.659 align:start position:0% different behaviors and there was a big 00:17:07.659 --> 00:17:10.919 align:start position:0% different behaviors and there was a big resistance<00:17:08.230> to<00:17:08.679> do<00:17:08.770> that<00:17:09.480> and<00:17:10.480> one<00:17:10.659> of<00:17:10.780> the 00:17:10.919 --> 00:17:10.929 align:start position:0% resistance to do that and one of the 00:17:10.929 --> 00:17:12.539 align:start position:0% resistance to do that and one of the reasons<00:17:11.439> people<00:17:11.740> said<00:17:11.980> that<00:17:12.130> it's<00:17:12.339> going<00:17:12.490> to 00:17:12.539 --> 00:17:12.549 align:start position:0% reasons people said that it's going to 00:17:12.549 --> 00:17:13.530 align:start position:0% reasons people said that it's going to make 00:17:13.530 --> 00:17:13.540 align:start position:0% make 00:17:13.540 --> 00:17:16.270 align:start position:0% make the<00:17:14.540> current<00:17:14.990> verification<00:17:15.530> tools<00:17:15.830> have<00:17:16.250> to 00:17:16.270 --> 00:17:16.280 align:start position:0% the current verification tools have to 00:17:16.280 --> 00:17:17.890 align:start position:0% the current verification tools have to be<00:17:16.490> changed<00:17:16.880> and<00:17:16.970> we<00:17:17.030> cannot<00:17:17.270> afford<00:17:17.420> that<00:17:17.660> so 00:17:17.890 --> 00:17:17.900 align:start position:0% be changed and we cannot afford that so 00:17:17.900 --> 00:17:20.110 align:start position:0% be changed and we cannot afford that so there<00:17:18.020> was<00:17:18.110> a<00:17:18.170> real<00:17:18.680> big<00:17:18.890> pushback<00:17:19.130> and<00:17:19.640> what 00:17:20.110 --> 00:17:20.120 align:start position:0% there was a real big pushback and what 00:17:20.120 --> 00:17:23.140 align:start position:0% there was a real big pushback and what you<00:17:20.240> suggest<00:17:20.720> I<00:17:20.870> think<00:17:21.290> I<00:17:22.160> would<00:17:22.730> imagine<00:17:22.940> it 00:17:23.140 --> 00:17:23.150 align:start position:0% you suggest I think I would imagine it 00:17:23.150 --> 00:17:25.210 align:start position:0% you suggest I think I would imagine it to<00:17:23.210> be<00:17:23.300> implemented<00:17:23.780> if<00:17:23.960> say<00:17:24.890> like<00:17:25.070> the 00:17:25.210 --> 00:17:25.220 align:start position:0% to be implemented if say like the 00:17:25.220 --> 00:17:28.510 align:start position:0% to be implemented if say like the additional<00:17:25.790> addition<00:17:26.890> up<00:17:27.890> code<00:17:28.160> would<00:17:28.310> have 00:17:28.510 --> 00:17:28.520 align:start position:0% additional addition up code would have 00:17:28.520 --> 00:17:30.940 align:start position:0% additional addition up code would have an<00:17:28.670> immediate<00:17:28.910> value<00:17:29.410> specifying<00:17:30.410> the<00:17:30.590> bit 00:17:30.940 --> 00:17:30.950 align:start position:0% an immediate value specifying the bit 00:17:30.950 --> 00:17:32.470 align:start position:0% an immediate value specifying the bit its<00:17:31.280> operating<00:17:31.730> on<00:17:31.850> or<00:17:32.030> you<00:17:32.150> would<00:17:32.300> have<00:17:32.330> a 00:17:32.470 --> 00:17:32.480 align:start position:0% its operating on or you would have a 00:17:32.480 --> 00:17:36.340 align:start position:0% its operating on or you would have a multiple<00:17:32.930> byte<00:17:33.140> codes<00:17:33.440> and<00:17:34.130> up<00:17:34.250> code<00:17:35.260> but<00:17:36.260> we 00:17:36.340 --> 00:17:36.350 align:start position:0% multiple byte codes and up code but we 00:17:36.350 --> 00:17:37.750 align:start position:0% multiple byte codes and up code but we have<00:17:36.500> this<00:17:36.620> perspective<00:17:36.920> people<00:17:37.490> don't<00:17:37.610> want 00:17:37.750 --> 00:17:37.760 align:start position:0% have this perspective people don't want 00:17:37.760 --> 00:17:40.900 align:start position:0% have this perspective people don't want to<00:17:37.790> have<00:17:37.960> changes<00:17:38.960> there<00:17:39.200> you<00:17:39.830> can<00:17:40.040> simply<00:17:40.280> you 00:17:40.900 --> 00:17:40.910 align:start position:0% to have changes there you can simply you 00:17:40.910 --> 00:17:43.780 align:start position:0% to have changes there you can simply you can<00:17:41.120> simply<00:17:41.570> call<00:17:41.840> mod<00:17:42.400> after<00:17:43.400> you<00:17:43.490> pulled 00:17:43.780 --> 00:17:43.790 align:start position:0% can simply call mod after you pulled 00:17:43.790 --> 00:17:46.450 align:start position:0% can simply call mod after you pulled that<00:17:43.970> data<00:17:44.260> does<00:17:45.260> you<00:17:45.440> know<00:17:45.590> you<00:17:45.650> only<00:17:45.920> need<00:17:46.220> so 00:17:46.450 --> 00:17:46.460 align:start position:0% that data does you know you only need so 00:17:46.460 --> 00:17:51.700 align:start position:0% that data does you know you only need so many<00:17:46.610> bits<00:17:48.700> and<00:17:49.870> and<00:17:50.870> you<00:17:51.140> want<00:17:51.320> to<00:17:51.380> detect 00:17:51.700 --> 00:17:51.710 align:start position:0% many bits and and you want to detect 00:17:51.710 --> 00:17:54.760 align:start position:0% many bits and and you want to detect patterns<00:17:51.950> and<00:17:52.520> in<00:17:53.120> the<00:17:53.450> VM<00:17:53.690> that<00:17:53.960> there's<00:17:54.620> like 00:17:54.760 --> 00:17:54.770 align:start position:0% patterns and in the VM that there's like 00:17:54.770 --> 00:17:56.440 align:start position:0% patterns and in the VM that there's like a<00:17:54.800> multi<00:17:55.130> four<00:17:55.460> and<00:17:55.700> then<00:17:55.910> there's<00:17:56.210> a 00:17:56.440 --> 00:17:56.450 align:start position:0% a multi four and then there's a 00:17:56.450 --> 00:17:58.450 align:start position:0% a multi four and then there's a calculation<00:17:57.290> then<00:17:57.440> you<00:17:57.590> charge<00:17:57.830> this<00:17:58.010> yeah<00:17:58.340> if 00:17:58.450 --> 00:17:58.460 align:start position:0% calculation then you charge this yeah if 00:17:58.460 --> 00:18:01.120 align:start position:0% calculation then you charge this yeah if if<00:17:59.270> some<00:17:59.480> data<00:17:59.630> came<00:18:00.050> in<00:18:00.320> and<00:18:00.650> then<00:18:00.770> you<00:18:00.920> might 00:18:01.120 --> 00:18:01.130 align:start position:0% if some data came in and then you might 00:18:01.130 --> 00:18:03.070 align:start position:0% if some data came in and then you might you've<00:18:01.610> just<00:18:01.880> fouled<00:18:02.120> away<00:18:02.240> all<00:18:02.540> those<00:18:02.720> bits 00:18:03.070 --> 00:18:03.080 align:start position:0% you've just fouled away all those bits 00:18:03.080 --> 00:18:06.340 align:start position:0% you've just fouled away all those bits and<00:18:03.620> it<00:18:04.520> means<00:18:04.730> a<00:18:05.090> compiler<00:18:05.630> like<00:18:05.840> solidity 00:18:06.340 --> 00:18:06.350 align:start position:0% and it means a compiler like solidity 00:18:06.350 --> 00:18:08.710 align:start position:0% and it means a compiler like solidity will<00:18:06.680> have<00:18:06.890> to<00:18:07.070> generate<00:18:07.610> code<00:18:08.330> to<00:18:08.570> take 00:18:08.710 --> 00:18:08.720 align:start position:0% will have to generate code to take 00:18:08.720 --> 00:18:13.750 align:start position:0% will have to generate code to take advantage<00:18:09.320> of<00:18:09.500> that<00:18:09.740> and<00:18:12.610> solidity<00:18:13.610> is 00:18:13.750 --> 00:18:13.760 align:start position:0% advantage of that and solidity is 00:18:13.760 --> 00:18:15.610 align:start position:0% advantage of that and solidity is actually<00:18:14.180> today<00:18:14.540> generating<00:18:15.230> code<00:18:15.380> like<00:18:15.590> that 00:18:15.610 --> 00:18:15.620 align:start position:0% actually today generating code like that 00:18:15.620 --> 00:18:17.560 align:start position:0% actually today generating code like that if<00:18:16.040> you're<00:18:16.250> using<00:18:16.280> smaller<00:18:16.970> data<00:18:17.270> types 00:18:17.560 --> 00:18:17.570 align:start position:0% if you're using smaller data types 00:18:17.570 --> 00:18:20.380 align:start position:0% if you're using smaller data types mm-hmm<00:18:18.230> but<00:18:18.680> since<00:18:19.280> gas-discharge<00:18:19.670> for<00:18:20.210> even 00:18:20.380 --> 00:18:20.390 align:start position:0% mm-hmm but since gas-discharge for even 00:18:20.390 --> 00:18:21.730 align:start position:0% mm-hmm but since gas-discharge for even the<00:18:20.510> multi<00:18:20.750> distraction<00:18:21.290> it<00:18:21.440> is<00:18:21.590> more 00:18:21.730 --> 00:18:21.740 align:start position:0% the multi distraction it is more 00:18:21.740 --> 00:18:23.530 align:start position:0% the multi distraction it is more expensive<00:18:22.040> but<00:18:22.610> so<00:18:22.970> people<00:18:23.240> don't<00:18:23.360> use<00:18:23.510> it 00:18:23.530 --> 00:18:23.540 align:start position:0% expensive but so people don't use it 00:18:23.540 --> 00:18:26.680 align:start position:0% expensive but so people don't use it right<00:18:24.040> so<00:18:25.040> we<00:18:25.130> have<00:18:25.220> to<00:18:25.340> change<00:18:25.610> the<00:18:25.940> gas<00:18:26.120> model 00:18:26.680 --> 00:18:26.690 align:start position:0% right so we have to change the gas model 00:18:26.690 --> 00:18:29.380 align:start position:0% right so we have to change the gas model so<00:18:27.170> that<00:18:27.200> that<00:18:27.500> actually<00:18:27.850> helps<00:18:28.850> in<00:18:29.120> the<00:18:29.240> way 00:18:29.380 --> 00:18:29.390 align:start position:0% so that that actually helps in the way 00:18:29.390 --> 00:18:34.300 align:start position:0% so that that actually helps in the way that<00:18:29.600> was<00:18:29.750> intended<00:18:30.260> to<00:18:30.290> help<00:18:32.290> so<00:18:33.290> we<00:18:33.710> talked 00:18:34.300 --> 00:18:34.310 align:start position:0% that was intended to help so we talked 00:18:34.310 --> 00:18:36.130 align:start position:0% that was intended to help so we talked about<00:18:34.430> one<00:18:34.850> thing<00:18:35.120> that<00:18:35.180> we<00:18:35.390> kind<00:18:35.630> of<00:18:35.780> have 00:18:36.130 --> 00:18:36.140 align:start position:0% about one thing that we kind of have 00:18:36.140 --> 00:18:38.620 align:start position:0% about one thing that we kind of have consensus<00:18:36.770> that<00:18:37.040> we<00:18:37.310> could<00:18:38.210> or<00:18:38.420> should 00:18:38.620 --> 00:18:38.630 align:start position:0% consensus that we could or should 00:18:38.630 --> 00:18:40.540 align:start position:0% consensus that we could or should and<00:18:38.930> maybe<00:18:39.080> will<00:18:39.290> change<00:18:39.650> which<00:18:39.950> is<00:18:40.100> removing 00:18:40.540 --> 00:18:40.550 align:start position:0% and maybe will change which is removing 00:18:40.550 --> 00:18:42.760 align:start position:0% and maybe will change which is removing dynamic<00:18:40.910> jumps<00:18:41.210> I'm<00:18:41.960> curious<00:18:42.320> what<00:18:42.740> other 00:18:42.760 --> 00:18:42.770 align:start position:0% dynamic jumps I'm curious what other 00:18:42.770 --> 00:18:44.710 align:start position:0% dynamic jumps I'm curious what other things<00:18:43.310> if<00:18:43.520> you<00:18:43.580> could<00:18:43.730> change<00:18:43.970> one<00:18:44.420> thing 00:18:44.710 --> 00:18:44.720 align:start position:0% things if you could change one thing 00:18:44.720 --> 00:18:46.720 align:start position:0% things if you could change one thing besides<00:18:45.470> that<00:18:45.680> any<00:18:46.130> VM<00:18:46.340> what<00:18:46.490> would<00:18:46.580> you 00:18:46.720 --> 00:18:46.730 align:start position:0% besides that any VM what would you 00:18:46.730 --> 00:18:48.310 align:start position:0% besides that any VM what would you change<00:18:47.000> maybe<00:18:47.210> we<00:18:47.360> could<00:18:47.510> just<00:18:47.630> love<00:18:48.050> you<00:18:48.140> guys 00:18:48.310 --> 00:18:48.320 align:start position:0% change maybe we could just love you guys 00:18:48.320 --> 00:18:52.930 align:start position:0% change maybe we could just love you guys all<00:18:48.500> have<00:18:48.650> an<00:18:48.740> answer<00:18:48.980> I<00:18:51.670> guess<00:18:52.670> we<00:18:52.850> have 00:18:52.930 --> 00:18:52.940 align:start position:0% all have an answer I guess we have 00:18:52.940 --> 00:18:55.690 align:start position:0% all have an answer I guess we have overlapping<00:18:53.300> answers<00:18:53.720> the<00:18:54.440> big<00:18:54.560> one<00:18:54.710> is<00:18:54.860> to 00:18:55.690 --> 00:18:55.700 align:start position:0% overlapping answers the big one is to 00:18:55.700 --> 00:18:57.990 align:start position:0% overlapping answers the big one is to remove<00:18:55.940> dynamic<00:18:56.420> gems<00:18:56.660> have<00:18:56.990> cold<00:18:57.320> frames<00:18:57.680> and 00:18:57.990 --> 00:18:58.000 align:start position:0% remove dynamic gems have cold frames and 00:18:58.000 --> 00:19:00.370 align:start position:0% remove dynamic gems have cold frames and this<00:18:59.000> will<00:18:59.210> give<00:18:59.510> a<00:18:59.720> couple<00:18:59.930> of<00:19:00.080> different 00:19:00.370 --> 00:19:00.380 align:start position:0% this will give a couple of different 00:19:00.380 --> 00:19:02.470 align:start position:0% this will give a couple of different benefits<00:19:00.770> a<00:19:00.980> lot<00:19:01.190> of<00:19:01.310> those<00:19:01.490> craig<00:19:02.060> explained 00:19:02.470 --> 00:19:02.480 align:start position:0% benefits a lot of those craig explained 00:19:02.480 --> 00:19:04.480 align:start position:0% benefits a lot of those craig explained but<00:19:03.260> another<00:19:03.470> immediate<00:19:03.830> benefit<00:19:04.310> people 00:19:04.480 --> 00:19:04.490 align:start position:0% but another immediate benefit people 00:19:04.490 --> 00:19:06.460 align:start position:0% but another immediate benefit people actually<00:19:04.820> going<00:19:05.120> to<00:19:05.240> feel<00:19:05.480> as<00:19:05.780> you<00:19:06.320> can 00:19:06.460 --> 00:19:06.470 align:start position:0% actually going to feel as you can 00:19:06.470 --> 00:19:09.310 align:start position:0% actually going to feel as you can address<00:19:06.790> more<00:19:07.790> of<00:19:07.970> the<00:19:08.210> you<00:19:08.660> can<00:19:08.810> address<00:19:08.960> like 00:19:09.310 --> 00:19:09.320 align:start position:0% address more of the you can address like 00:19:09.320 --> 00:19:10.660 align:start position:0% address more of the you can address like different<00:19:09.680> the<00:19:09.830> arguments<00:19:10.400> to<00:19:10.550> the<00:19:10.640> function 00:19:10.660 --> 00:19:10.670 align:start position:0% different the arguments to the function 00:19:10.670 --> 00:19:12.700 align:start position:0% different the arguments to the function much<00:19:11.150> more<00:19:11.330> easily<00:19:11.450> than<00:19:11.630> right<00:19:12.170> now<00:19:12.200> and<00:19:12.590> it 00:19:12.700 --> 00:19:12.710 align:start position:0% much more easily than right now and it 00:19:12.710 --> 00:19:14.770 align:start position:0% much more easily than right now and it also<00:19:12.950> makes<00:19:13.270> compiler<00:19:14.270> code<00:19:14.540> generation 00:19:14.770 --> 00:19:14.780 align:start position:0% also makes compiler code generation 00:19:14.780 --> 00:19:17.290 align:start position:0% also makes compiler code generation phase<00:19:15.050> easier<00:19:15.490> people<00:19:16.490> have<00:19:16.700> a<00:19:16.730> lot<00:19:17.030> of<00:19:17.060> pain 00:19:17.290 --> 00:19:17.300 align:start position:0% phase easier people have a lot of pain 00:19:17.300 --> 00:19:19.240 align:start position:0% phase easier people have a lot of pain with<00:19:17.450> solidity<00:19:17.840> giving<00:19:18.230> this<00:19:18.470> random<00:19:18.980> awkward 00:19:19.240 --> 00:19:19.250 align:start position:0% with solidity giving this random awkward 00:19:19.250 --> 00:19:22.360 align:start position:0% with solidity giving this random awkward error<00:19:19.880> message<00:19:20.240> stack<00:19:20.690> too<00:19:20.870> deep<00:19:21.050> and<00:19:21.290> it<00:19:22.160> is 00:19:22.360 --> 00:19:22.370 align:start position:0% error message stack too deep and it is 00:19:22.370 --> 00:19:24.070 align:start position:0% error message stack too deep and it is giving<00:19:22.670> it<00:19:22.790> in<00:19:22.910> various<00:19:23.510> different<00:19:23.750> ways 00:19:24.070 --> 00:19:24.080 align:start position:0% giving it in various different ways 00:19:24.080 --> 00:19:26.109 align:start position:0% giving it in various different ways where<00:19:24.320> where<00:19:24.710> is<00:19:24.800> different<00:19:25.070> locations 00:19:26.109 --> 00:19:26.119 align:start position:0% where where is different locations 00:19:26.119 --> 00:19:28.449 align:start position:0% where where is different locations and<00:19:26.259> it's<00:19:27.259> just<00:19:27.649> a<00:19:27.709> lot<00:19:27.829> of<00:19:27.859> work<00:19:28.069> to<00:19:28.219> you<00:19:28.309> to 00:19:28.449 --> 00:19:28.459 align:start position:0% and it's just a lot of work to you to 00:19:28.459 --> 00:19:29.799 align:start position:0% and it's just a lot of work to you to work<00:19:28.549> around<00:19:28.699> that<00:19:28.879> with<00:19:29.239> the<00:19:29.449> current<00:19:29.719> EPA 00:19:29.799 --> 00:19:29.809 align:start position:0% work around that with the current EPA 00:19:29.809 --> 00:19:32.349 align:start position:0% work around that with the current EPA model<00:19:30.229> so<00:19:31.099> I<00:19:31.159> think<00:19:31.249> this<00:19:31.429> is<00:19:31.489> the<00:19:31.699> core<00:19:32.119> which 00:19:32.349 --> 00:19:32.359 align:start position:0% model so I think this is the core which 00:19:32.359 --> 00:19:35.379 align:start position:0% model so I think this is the core which which<00:19:33.229> is<00:19:33.439> blocking<00:19:33.799> so<00:19:33.949> many<00:19:34.129> things<00:19:34.369> and<00:19:34.669> so 00:19:35.379 --> 00:19:35.389 align:start position:0% which is blocking so many things and so 00:19:35.389 --> 00:19:37.599 align:start position:0% which is blocking so many things and so that<00:19:35.539> would<00:19:35.629> be<00:19:35.779> my<00:19:35.899> number<00:19:36.199> one<00:19:36.459> case<00:19:37.459> you 00:19:37.599 --> 00:19:37.609 align:start position:0% that would be my number one case you 00:19:37.609 --> 00:19:41.789 align:start position:0% that would be my number one case you have<00:19:37.759> one<00:19:38.799> no<00:19:39.799> I'd<00:19:40.039> rather<00:19:40.219> just<00:19:40.519> switch<00:19:41.329> to 00:19:41.789 --> 00:19:41.799 align:start position:0% have one no I'd rather just switch to 00:19:41.799 --> 00:19:49.449 align:start position:0% have one no I'd rather just switch to assembly<00:19:45.939> for<00:19:46.939> me<00:19:47.119> would<00:19:47.329> be<00:19:47.769> all<00:19:48.769> of<00:19:49.099> this 00:19:49.449 --> 00:19:49.459 align:start position:0% assembly for me would be all of this 00:19:49.459 --> 00:19:53.139 align:start position:0% assembly for me would be all of this let's<00:19:50.239> say<00:19:50.509> soft<00:19:51.019> oils<00:19:51.679> that<00:19:52.039> you<00:19:52.189> can<00:19:52.399> get<00:19:52.819> I 00:19:53.139 --> 00:19:53.149 align:start position:0% let's say soft oils that you can get I 00:19:53.149 --> 00:19:55.209 align:start position:0% let's say soft oils that you can get I mean<00:19:53.509> when<00:19:53.929> you<00:19:54.019> divide<00:19:54.379> by<00:19:54.559> zero<00:19:54.859> if<00:19:55.069> it's 00:19:55.209 --> 00:19:55.219 align:start position:0% mean when you divide by zero if it's 00:19:55.219 --> 00:19:57.179 align:start position:0% mean when you divide by zero if it's zero<00:19:55.489> it<00:19:55.609> doesn't<00:19:55.969> make<00:19:56.239> sense<00:19:56.269> when<00:19:57.019> you 00:19:57.179 --> 00:19:57.189 align:start position:0% zero it doesn't make sense when you 00:19:57.189 --> 00:19:59.859 align:start position:0% zero it doesn't make sense when you access<00:19:58.189> data<00:19:58.219> that<00:19:58.729> doesn't<00:19:59.179> isn't<00:19:59.359> there<00:19:59.719> you 00:19:59.859 --> 00:19:59.869 align:start position:0% access data that doesn't isn't there you 00:19:59.869 --> 00:20:02.949 align:start position:0% access data that doesn't isn't there you get<00:20:00.049> zero<00:20:00.379> and<00:20:00.739> like<00:20:01.159> all<00:20:01.399> of<00:20:01.519> these<00:20:01.699> sorry<00:20:02.449> for 00:20:02.949 --> 00:20:02.959 align:start position:0% get zero and like all of these sorry for 00:20:02.959 --> 00:20:05.649 align:start position:0% get zero and like all of these sorry for first<00:20:03.259> it<00:20:03.439> makes<00:20:03.999> verification<00:20:04.999> harder<00:20:05.389> not 00:20:05.649 --> 00:20:05.659 align:start position:0% first it makes verification harder not 00:20:05.659 --> 00:20:07.989 align:start position:0% first it makes verification harder not not<00:20:05.959> easier<00:20:06.319> although<00:20:06.979> like<00:20:07.369> some<00:20:07.699> people 00:20:07.989 --> 00:20:07.999 align:start position:0% not easier although like some people 00:20:07.999 --> 00:20:10.149 align:start position:0% not easier although like some people said<00:20:08.419> like<00:20:08.689> now<00:20:08.989> it's<00:20:09.169> defined<00:20:09.619> what's<00:20:09.859> going 00:20:10.149 --> 00:20:10.159 align:start position:0% said like now it's defined what's going 00:20:10.159 --> 00:20:12.279 align:start position:0% said like now it's defined what's going to<00:20:10.189> happen<00:20:10.549> but<00:20:10.759> it's<00:20:11.209> mathematically<00:20:12.109> it 00:20:12.279 --> 00:20:12.289 align:start position:0% to happen but it's mathematically it 00:20:12.289 --> 00:20:15.159 align:start position:0% to happen but it's mathematically it doesn't<00:20:12.559> make<00:20:12.709> sense<00:20:12.979> and<00:20:13.839> it's<00:20:14.839> also<00:20:15.019> like 00:20:15.159 --> 00:20:15.169 align:start position:0% doesn't make sense and it's also like 00:20:15.169 --> 00:20:18.279 align:start position:0% doesn't make sense and it's also like very<00:20:15.589> dangerous<00:20:16.309> and<00:20:16.579> we<00:20:16.969> have<00:20:17.299> examples<00:20:18.139> of 00:20:18.279 --> 00:20:18.289 align:start position:0% very dangerous and we have examples of 00:20:18.289 --> 00:20:22.599 align:start position:0% very dangerous and we have examples of this<00:20:19.389> being<00:20:20.389> broken<00:20:20.749> in<00:20:21.049> in<00:20:21.609> deployed 00:20:22.599 --> 00:20:22.609 align:start position:0% this being broken in in deployed 00:20:22.609 --> 00:20:25.869 align:start position:0% this being broken in in deployed production<00:20:23.419> ready<00:20:23.709> smart<00:20:24.709> contracts<00:20:25.279> oh<00:20:25.459> yeah 00:20:25.869 --> 00:20:25.879 align:start position:0% production ready smart contracts oh yeah 00:20:25.879 --> 00:20:28.059 align:start position:0% production ready smart contracts oh yeah that<00:20:26.089> that<00:20:26.389> would<00:20:26.659> be<00:20:26.839> might<00:20:26.989> change<00:20:27.289> so<00:20:28.009> I 00:20:28.059 --> 00:20:28.069 align:start position:0% that that would be might change so I 00:20:28.069 --> 00:20:30.999 align:start position:0% that that would be might change so I would<00:20:28.309> just<00:20:29.199> terminate<00:20:30.199> execution<00:20:30.859> if 00:20:30.999 --> 00:20:31.009 align:start position:0% would just terminate execution if 00:20:31.009 --> 00:20:34.389 align:start position:0% would just terminate execution if something<00:20:31.459> like<00:20:31.579> that<00:20:31.639> happened<00:20:32.239> mm-hmm<00:20:33.399> Greg 00:20:34.389 --> 00:20:34.399 align:start position:0% something like that happened mm-hmm Greg 00:20:34.399 --> 00:20:35.979 align:start position:0% something like that happened mm-hmm Greg up<00:20:34.729> to<00:20:34.879> you<00:20:34.969> and<00:20:35.149> feel<00:20:35.449> free<00:20:35.599> to<00:20:35.629> use<00:20:35.719> this 00:20:35.979 --> 00:20:35.989 align:start position:0% up to you and feel free to use this 00:20:35.989 --> 00:20:38.499 align:start position:0% up to you and feel free to use this opportunity<00:20:36.439> to<00:20:36.679> introduce<00:20:36.829> you<00:20:37.039> yeah<00:20:37.509> and 00:20:38.499 --> 00:20:38.509 align:start position:0% opportunity to introduce you yeah and 00:20:38.509 --> 00:20:40.959 align:start position:0% opportunity to introduce you yeah and I'm<00:20:39.109> with<00:20:39.319> Casey<00:20:39.619> and<00:20:40.159> this<00:20:40.279> part<00:20:40.639> of<00:20:40.759> why<00:20:40.939> I 00:20:40.959 --> 00:20:40.969 align:start position:0% I'm with Casey and this part of why I 00:20:40.969 --> 00:20:43.959 align:start position:0% I'm with Casey and this part of why I asked<00:20:41.509> the<00:20:41.539> question<00:20:41.659> on<00:20:42.259> scheduling<00:20:43.039> um 00:20:43.959 --> 00:20:43.969 align:start position:0% asked the question on scheduling um 00:20:43.969 --> 00:20:46.779 align:start position:0% asked the question on scheduling um because<00:20:44.899> I<00:20:45.079> know<00:20:45.139> that<00:20:46.009> I<00:20:46.099> can<00:20:46.279> much<00:20:46.489> more 00:20:46.779 --> 00:20:46.789 align:start position:0% because I know that I can much more 00:20:46.789 --> 00:20:51.369 align:start position:0% because I know that I can much more rapidly<00:20:47.449> implement<00:20:48.319> a<00:20:48.559> IP<00:20:48.799> 6<00:20:49.279> 1<00:20:49.519> 5<00:20:49.819> and<00:20:50.539> we're 00:20:51.369 --> 00:20:51.379 align:start position:0% rapidly implement a IP 6 1 5 and we're 00:20:51.379 --> 00:20:54.999 align:start position:0% rapidly implement a IP 6 1 5 and we're 26<00:20:51.829> 1<00:20:51.979> 5<00:20:52.299> that's<00:20:53.299> that's<00:20:53.779> that's<00:20:54.319> the<00:20:54.649> proposal 00:20:54.999 --> 00:20:55.009 align:start position:0% 26 1 5 that's that's that's the proposal 00:20:55.009 --> 00:20:58.179 align:start position:0% 26 1 5 that's that's that's the proposal to<00:20:55.579> get<00:20:55.879> rid<00:20:56.089> of<00:20:56.119> dynamic<00:20:56.839> jump<00:20:57.189> introduced 00:20:58.179 --> 00:20:58.189 align:start position:0% to get rid of dynamic jump introduced 00:20:58.189 --> 00:21:01.839 align:start position:0% to get rid of dynamic jump introduced subroutines<00:20:58.909> and<00:20:59.299> a<00:20:59.419> few<00:20:59.659> other<00:20:59.839> opcodes<00:21:00.849> to 00:21:01.839 --> 00:21:01.849 align:start position:0% subroutines and a few other opcodes to 00:21:01.849 --> 00:21:04.149 align:start position:0% subroutines and a few other opcodes to clean<00:21:02.389> that<00:21:02.659> up<00:21:02.689> it<00:21:03.319> would<00:21:03.439> be<00:21:03.559> a<00:21:03.589> separate 00:21:04.149 --> 00:21:04.159 align:start position:0% clean that up it would be a separate 00:21:04.159 --> 00:21:06.279 align:start position:0% clean that up it would be a separate there<00:21:04.969> are<00:21:05.059> separate<00:21:05.389> things<00:21:05.659> you<00:21:05.779> could<00:21:06.079> do 00:21:06.279 --> 00:21:06.289 align:start position:0% there are separate things you could do 00:21:06.289 --> 00:21:09.549 align:start position:0% there are separate things you could do like<00:21:06.529> what<00:21:06.769> Powell<00:21:07.219> mentioned<00:21:08.259> those<00:21:09.259> might 00:21:09.549 --> 00:21:09.559 align:start position:0% like what Powell mentioned those might 00:21:09.559 --> 00:21:11.769 align:start position:0% like what Powell mentioned those might be<00:21:09.589> work<00:21:09.979> you<00:21:10.189> don't<00:21:10.369> want<00:21:10.609> to<00:21:10.759> do<00:21:11.029> there's<00:21:11.689> a 00:21:11.769 --> 00:21:11.779 align:start position:0% be work you don't want to do there's a 00:21:11.779 --> 00:21:15.549 align:start position:0% be work you don't want to do there's a VIP<00:21:12.379> six<00:21:12.979> one<00:21:13.189> six<00:21:13.609> to<00:21:13.879> put<00:21:14.089> in<00:21:14.209> Cindy<00:21:14.839> it's<00:21:15.379> not 00:21:15.549 --> 00:21:15.559 align:start position:0% VIP six one six to put in Cindy it's not 00:21:15.559 --> 00:21:17.649 align:start position:0% VIP six one six to put in Cindy it's not clear<00:21:15.919> if<00:21:16.039> we<00:21:16.189> want<00:21:16.399> to<00:21:16.489> do<00:21:16.669> that<00:21:16.879> or<00:21:17.179> just<00:21:17.209> wait 00:21:17.649 --> 00:21:17.659 align:start position:0% clear if we want to do that or just wait 00:21:17.659 --> 00:21:22.959 align:start position:0% clear if we want to do that or just wait for<00:21:17.869> Azzam<00:21:18.409> but<00:21:19.929> so<00:21:20.929> for<00:21:21.199> me<00:21:21.439> work<00:21:22.369> I'm<00:21:22.609> working 00:21:22.959 --> 00:21:22.969 align:start position:0% for Azzam but so for me work I'm working 00:21:22.969 --> 00:21:25.929 align:start position:0% for Azzam but so for me work I'm working with<00:21:23.149> Boris<00:21:23.539> and<00:21:23.839> and<00:21:24.079> Brook<00:21:24.379> to<00:21:24.619> just<00:21:24.939> raise 00:21:25.929 --> 00:21:25.939 align:start position:0% with Boris and and Brook to just raise 00:21:25.939 --> 00:21:27.789 align:start position:0% with Boris and and Brook to just raise the<00:21:26.239> money<00:21:26.449> and<00:21:26.569> put<00:21:26.899> the<00:21:27.019> plan<00:21:27.259> together<00:21:27.439> to 00:21:27.789 --> 00:21:27.799 align:start position:0% the money and put the plan together to 00:21:27.799 --> 00:21:30.549 align:start position:0% the money and put the plan together to do<00:21:28.129> that<00:21:28.429> just<00:21:29.029> as<00:21:29.239> personal<00:21:29.989> reasons<00:21:30.379> I 00:21:30.549 --> 00:21:30.559 align:start position:0% do that just as personal reasons I 00:21:30.559 --> 00:21:32.949 align:start position:0% do that just as personal reasons I decided<00:21:30.949> I<00:21:31.309> didn't<00:21:31.699> didn't<00:21:32.389> want<00:21:32.569> to<00:21:32.689> do<00:21:32.809> it 00:21:32.949 --> 00:21:32.959 align:start position:0% decided I didn't didn't want to do it 00:21:32.959 --> 00:21:34.809 align:start position:0% decided I didn't didn't want to do it under<00:21:33.109> contract<00:21:33.799> with<00:21:33.919> the<00:21:34.129> foundation 00:21:34.809 --> 00:21:34.819 align:start position:0% under contract with the foundation 00:21:34.819 --> 00:21:37.179 align:start position:0% under contract with the foundation directly<00:21:35.449> down<00:21:36.019> but<00:21:36.349> wanted<00:21:36.649> to<00:21:36.679> have<00:21:36.919> more 00:21:37.179 --> 00:21:37.189 align:start position:0% directly down but wanted to have more 00:21:37.189 --> 00:21:38.870 align:start position:0% directly down but wanted to have more more<00:21:37.579> control<00:21:38.059> over<00:21:38.089> the<00:21:38.509> price 00:21:38.870 --> 00:21:38.880 align:start position:0% more control over the price 00:21:38.880 --> 00:21:41.960 align:start position:0% more control over the price checked<00:21:39.030> myself<00:21:39.860> and<00:21:40.860> this<00:21:40.980> is<00:21:41.040> this<00:21:41.460> is<00:21:41.520> EVM 00:21:41.960 --> 00:21:41.970 align:start position:0% checked myself and this is this is EVM 00:21:41.970 --> 00:21:43.370 align:start position:0% checked myself and this is this is EVM 1.5<00:21:42.510> what<00:21:42.660> you're<00:21:42.750> afraid<00:21:43.050> yeah<00:21:43.230> the 00:21:43.370 --> 00:21:43.380 align:start position:0% 1.5 what you're afraid yeah the 00:21:43.380 --> 00:21:46.160 align:start position:0% 1.5 what you're afraid yeah the collection<00:21:43.830> of<00:21:43.890> these<00:21:44.010> two<00:21:44.340> yeah<00:21:45.060> I<00:21:45.330> guess 00:21:46.160 --> 00:21:46.170 align:start position:0% collection of these two yeah I guess 00:21:46.170 --> 00:21:49.040 align:start position:0% collection of these two yeah I guess Boris<00:21:47.070> is<00:21:47.310> telling<00:21:47.700> me<00:21:47.850> getting<00:21:48.210> out<00:21:48.360> talking 00:21:49.040 --> 00:21:49.050 align:start position:0% Boris is telling me getting out talking 00:21:49.050 --> 00:21:51.770 align:start position:0% Boris is telling me getting out talking to<00:21:49.170> some<00:21:49.380> fair<00:21:50.280> number<00:21:50.520> of<00:21:50.790> other<00:21:50.970> clients<00:21:51.630> are 00:21:51.770 --> 00:21:51.780 align:start position:0% to some fair number of other clients are 00:21:51.780 --> 00:21:53.960 align:start position:0% to some fair number of other clients are going<00:21:51.960> if<00:21:52.320> we<00:21:52.530> can<00:21:52.710> quickly<00:21:52.980> get<00:21:53.340> this<00:21:53.640> stuff 00:21:53.960 --> 00:21:53.970 align:start position:0% going if we can quickly get this stuff 00:21:53.970 --> 00:21:59.360 align:start position:0% going if we can quickly get this stuff we'd<00:21:54.690> really<00:21:55.020> like<00:21:55.260> it<00:21:56.480> Andy<00:21:57.480> BMC<00:21:58.200> means<00:21:58.920> if<00:21:59.220> we 00:21:59.360 --> 00:21:59.370 align:start position:0% we'd really like it Andy BMC means if we 00:21:59.370 --> 00:22:03.920 align:start position:0% we'd really like it Andy BMC means if we wrap<00:21:59.610> it<00:21:59.640> up<00:22:00.030> that<00:22:00.330> way<00:22:01.940> they<00:22:02.940> can<00:22:03.120> get<00:22:03.330> it<00:22:03.480> they 00:22:03.920 --> 00:22:03.930 align:start position:0% wrap it up that way they can get it they 00:22:03.930 --> 00:22:06.440 align:start position:0% wrap it up that way they can get it they can<00:22:04.110> plug<00:22:04.350> it<00:22:04.530> in<00:22:04.680> they<00:22:05.130> can<00:22:05.340> use<00:22:05.520> it<00:22:05.790> mm<00:22:06.270> when 00:22:06.440 --> 00:22:06.450 align:start position:0% can plug it in they can use it mm when 00:22:06.450 --> 00:22:09.020 align:start position:0% can plug it in they can use it mm when wasm<00:22:06.870> is<00:22:06.990> available<00:22:07.590> they<00:22:08.010> can<00:22:08.220> get<00:22:08.400> it<00:22:08.610> they 00:22:09.020 --> 00:22:09.030 align:start position:0% wasm is available they can get it they 00:22:09.030 --> 00:22:13.720 align:start position:0% wasm is available they can get it they can<00:22:09.210> plug<00:22:09.450> it<00:22:09.600> in<00:22:09.750> they<00:22:10.200> can<00:22:10.410> use<00:22:10.590> it<00:22:11.030> and<00:22:12.620> just 00:22:13.720 --> 00:22:13.730 align:start position:0% can plug it in they can use it and just 00:22:13.730 --> 00:22:17.600 align:start position:0% can plug it in they can use it and just try<00:22:14.730> and<00:22:14.970> try<00:22:15.960> and<00:22:16.050> get<00:22:16.380> past<00:22:16.680> this<00:22:16.980> problem 00:22:17.600 --> 00:22:17.610 align:start position:0% try and try and get past this problem 00:22:17.610 --> 00:22:23.150 align:start position:0% try and try and get past this problem yeah<00:22:18.300> much<00:22:18.870> more<00:22:18.900> quickly<00:22:21.530> so<00:22:22.530> there's<00:22:22.680> kind 00:22:23.150 --> 00:22:23.160 align:start position:0% yeah much more quickly so there's kind 00:22:23.160 --> 00:22:24.740 align:start position:0% yeah much more quickly so there's kind of<00:22:23.310> two<00:22:23.370> schools<00:22:23.910> of<00:22:24.030> thought<00:22:24.090> right<00:22:24.600> now 00:22:24.740 --> 00:22:24.750 align:start position:0% of two schools of thought right now 00:22:24.750 --> 00:22:26.960 align:start position:0% of two schools of thought right now about<00:22:25.050> the<00:22:25.260> state<00:22:26.130> execution<00:22:26.610> engine<00:22:26.850> and 00:22:26.960 --> 00:22:26.970 align:start position:0% about the state execution engine and 00:22:26.970 --> 00:22:28.970 align:start position:0% about the state execution engine and ethereal<00:22:27.360> one<00:22:27.570> is<00:22:27.750> we<00:22:28.380> should<00:22:28.530> focus<00:22:28.710> all<00:22:28.950> of 00:22:28.970 --> 00:22:28.980 align:start position:0% ethereal one is we should focus all of 00:22:28.980 --> 00:22:31.430 align:start position:0% ethereal one is we should focus all of our<00:22:29.130> resources<00:22:29.190> on<00:22:29.700> us<00:22:30.180> um<00:22:30.390> and<00:22:30.540> sort<00:22:31.290> of<00:22:31.350> its 00:22:31.430 --> 00:22:31.440 align:start position:0% our resources on us um and sort of its 00:22:31.440 --> 00:22:33.170 align:start position:0% our resources on us um and sort of its Casey<00:22:31.620> alluded<00:22:32.040> to<00:22:32.100> before<00:22:32.220> like<00:22:32.640> that<00:22:32.820> should 00:22:33.170 --> 00:22:33.180 align:start position:0% Casey alluded to before like that should 00:22:33.180 --> 00:22:35.510 align:start position:0% Casey alluded to before like that should be<00:22:33.210> the<00:22:33.630> emphasis<00:22:34.290> right<00:22:34.440> now<00:22:34.620> but<00:22:35.370> there's 00:22:35.510 --> 00:22:35.520 align:start position:0% be the emphasis right now but there's 00:22:35.520 --> 00:22:37.100 align:start position:0% be the emphasis right now but there's clearly<00:22:35.640> another<00:22:36.030> side<00:22:36.270> another<00:22:36.660> way<00:22:36.990> of 00:22:37.100 --> 00:22:37.110 align:start position:0% clearly another side another way of 00:22:37.110 --> 00:22:38.200 align:start position:0% clearly another side another way of looking<00:22:37.230> at<00:22:37.440> this<00:22:37.530> which<00:22:37.590> is<00:22:37.860> that<00:22:38.010> we<00:22:38.130> should 00:22:38.200 --> 00:22:38.210 align:start position:0% looking at this which is that we should 00:22:38.210 --> 00:22:42.080 align:start position:0% looking at this which is that we should not<00:22:39.210> we<00:22:39.450> should<00:22:39.480> not<00:22:39.710> we<00:22:40.710> should<00:22:40.740> not<00:22:41.060> try<00:22:42.060> to 00:22:42.080 --> 00:22:42.090 align:start position:0% not we should not we should not try to 00:22:42.090 --> 00:22:43.730 align:start position:0% not we should not we should not try to deprecated<00:22:42.540> EVM<00:22:42.900> and<00:22:43.110> we<00:22:43.170> should<00:22:43.320> except<00:22:43.590> it's 00:22:43.730 --> 00:22:43.740 align:start position:0% deprecated EVM and we should except it's 00:22:43.740 --> 00:22:44.840 align:start position:0% deprecated EVM and we should except it's gonna<00:22:43.830> be<00:22:43.980> with<00:22:44.130> us<00:22:44.160> for<00:22:44.280> a<00:22:44.460> while<00:22:44.580> and<00:22:44.760> we 00:22:44.840 --> 00:22:44.850 align:start position:0% gonna be with us for a while and we 00:22:44.850 --> 00:22:46.100 align:start position:0% gonna be with us for a while and we should<00:22:45.000> be<00:22:45.060> investing<00:22:45.450> more<00:22:45.630> in<00:22:45.780> it<00:22:45.900> I'm<00:22:46.020> just 00:22:46.100 --> 00:22:46.110 align:start position:0% should be investing more in it I'm just 00:22:46.110 --> 00:22:47.840 align:start position:0% should be investing more in it I'm just wondering<00:22:46.500> Greg<00:22:47.130> maybe<00:22:47.400> you<00:22:47.550> want<00:22:47.700> to<00:22:47.760> make 00:22:47.840 --> 00:22:47.850 align:start position:0% wondering Greg maybe you want to make 00:22:47.850 --> 00:22:50.270 align:start position:0% wondering Greg maybe you want to make the<00:22:47.970> case<00:22:48.120> for<00:22:48.180> why<00:22:48.660> that's<00:22:49.200> worth<00:22:49.530> doing<00:22:49.860> even 00:22:50.270 --> 00:22:50.280 align:start position:0% the case for why that's worth doing even 00:22:50.280 --> 00:22:54.140 align:start position:0% the case for why that's worth doing even in<00:22:50.490> light<00:22:50.700> of<00:22:50.730> you<00:22:50.910> blossom<00:22:51.740> I<00:22:53.150> haven't 00:22:54.140 --> 00:22:54.150 align:start position:0% in light of you blossom I haven't 00:22:54.150 --> 00:22:57.410 align:start position:0% in light of you blossom I haven't counted<00:22:54.330> but<00:22:54.870> how<00:22:55.500> many<00:22:55.560> VM<00:22:56.310> contracts<00:22:57.090> are<00:22:57.330> on 00:22:57.410 --> 00:22:57.420 align:start position:0% counted but how many VM contracts are on 00:22:57.420 --> 00:23:00.200 align:start position:0% counted but how many VM contracts are on the<00:22:57.600> blockchain<00:22:57.840> now<00:22:58.610> what<00:22:59.610> rate<00:22:59.880> is<00:23:00.060> it 00:23:00.200 --> 00:23:00.210 align:start position:0% the blockchain now what rate is it 00:23:00.210 --> 00:23:03.260 align:start position:0% the blockchain now what rate is it growing<00:23:00.660> at<00:23:01.160> is<00:23:02.160> it<00:23:02.370> quadratic<00:23:03.060> or 00:23:03.260 --> 00:23:03.270 align:start position:0% growing at is it quadratic or 00:23:03.270 --> 00:23:07.220 align:start position:0% growing at is it quadratic or exponential<00:23:04.610> if<00:23:05.610> it's<00:23:05.790> exponential<00:23:06.690> however 00:23:07.220 --> 00:23:07.230 align:start position:0% exponential if it's exponential however 00:23:07.230 --> 00:23:10.130 align:start position:0% exponential if it's exponential however long<00:23:07.530> it<00:23:07.770> takes<00:23:08.040> to<00:23:08.160> Yeti<00:23:08.430> wasm<00:23:09.120> out<00:23:09.330> how<00:23:10.080> many 00:23:10.130 --> 00:23:10.140 align:start position:0% long it takes to Yeti wasm out how many 00:23:10.140 --> 00:23:13.640 align:start position:0% long it takes to Yeti wasm out how many more<00:23:10.650> EVM<00:23:11.430> will<00:23:12.120> be<00:23:12.270> out<00:23:12.450> there<00:23:12.750> how<00:23:13.320> many 00:23:13.640 --> 00:23:13.650 align:start position:0% more EVM will be out there how many 00:23:13.650 --> 00:23:17.900 align:start position:0% more EVM will be out there how many existing<00:23:14.070> tools<00:23:14.640> exist<00:23:15.390> for<00:23:16.110> analyze<00:23:16.560> EVM<00:23:17.160> one 00:23:17.900 --> 00:23:17.910 align:start position:0% existing tools exist for analyze EVM one 00:23:17.910 --> 00:23:21.410 align:start position:0% existing tools exist for analyze EVM one code<00:23:18.300> how<00:23:19.020> many<00:23:19.380> new<00:23:20.280> languages<00:23:21.000> are<00:23:21.210> being 00:23:21.410 --> 00:23:21.420 align:start position:0% code how many new languages are being 00:23:21.420 --> 00:23:23.900 align:start position:0% code how many new languages are being created<00:23:22.110> they'll<00:23:22.800> basically<00:23:23.040> there's 00:23:23.900 --> 00:23:23.910 align:start position:0% created they'll basically there's 00:23:23.910 --> 00:23:26.330 align:start position:0% created they'll basically there's already<00:23:24.150> an<00:23:24.570> ecosystem<00:23:25.170> growing<00:23:25.770> up<00:23:25.950> around 00:23:26.330 --> 00:23:26.340 align:start position:0% already an ecosystem growing up around 00:23:26.340 --> 00:23:29.720 align:start position:0% already an ecosystem growing up around that<00:23:27.500> you<00:23:28.500> know<00:23:28.560> so<00:23:28.770> it<00:23:28.860> doesn't<00:23:29.280> help<00:23:29.430> the 00:23:29.720 --> 00:23:29.730 align:start position:0% that you know so it doesn't help the 00:23:29.730 --> 00:23:33.110 align:start position:0% that you know so it doesn't help the community<00:23:30.390> to<00:23:30.660> just<00:23:31.260> say<00:23:31.530> well<00:23:32.340> don't<00:23:32.790> bother 00:23:33.110 --> 00:23:33.120 align:start position:0% community to just say well don't bother 00:23:33.120 --> 00:23:34.820 align:start position:0% community to just say well don't bother because<00:23:33.600> at<00:23:33.990> some<00:23:34.230> point<00:23:34.530> in<00:23:34.680> the<00:23:34.800> future 00:23:34.820 --> 00:23:34.830 align:start position:0% because at some point in the future 00:23:34.830 --> 00:23:46.839 align:start position:0% because at some point in the future we're<00:23:35.400> going<00:23:35.520> to<00:23:35.610> throw<00:23:35.790> that<00:23:36.000> away<00:23:36.230> yeah 00:23:46.839 --> 00:23:46.849 align:start position:0% 00:23:46.849 --> 00:23:51.320 align:start position:0% the<00:23:47.849> Sinclair<00:23:48.570> issue<00:23:48.919> like<00:23:49.919> both<00:23:50.219> awasum<00:23:51.149> and 00:23:51.320 --> 00:23:51.330 align:start position:0% the Sinclair issue like both awasum and 00:23:51.330 --> 00:23:55.849 align:start position:0% the Sinclair issue like both awasum and GBM<00:23:51.779> 1.5<00:23:52.669> I'm<00:23:53.669> curious<00:23:54.259> what<00:23:55.259> are<00:23:55.440> the 00:23:55.849 --> 00:23:55.859 align:start position:0% GBM 1.5 I'm curious what are the 00:23:55.859 --> 00:23:57.889 align:start position:0% GBM 1.5 I'm curious what are the backwards<00:23:56.340> compatibility<00:23:56.909> concerns<00:23:57.570> with 00:23:57.889 --> 00:23:57.899 align:start position:0% backwards compatibility concerns with 00:23:57.899 --> 00:23:59.570 align:start position:0% backwards compatibility concerns with say<00:23:58.200> removing<00:23:58.529> dynamic<00:23:59.039> jumps 00:23:59.570 --> 00:23:59.580 align:start position:0% say removing dynamic jumps 00:23:59.580 --> 00:24:02.930 align:start position:0% say removing dynamic jumps I<00:23:59.609> know<00:24:00.359> I<00:24:00.869> know<00:24:01.139> II<00:24:01.259> was<00:24:01.739> um<00:24:02.249> there<00:24:02.429> there's 00:24:02.930 --> 00:24:02.940 align:start position:0% I know I know II was um there there's 00:24:02.940 --> 00:24:04.700 align:start position:0% I know I know II was um there there's various<00:24:03.269> proposals<00:24:03.599> to<00:24:04.049> add<00:24:04.169> backwards 00:24:04.700 --> 00:24:04.710 align:start position:0% various proposals to add backwards 00:24:04.710 --> 00:24:06.219 align:start position:0% various proposals to add backwards compatibility<00:24:05.190> which<00:24:05.519> might<00:24:05.759> help<00:24:05.909> alleviate 00:24:06.219 --> 00:24:06.229 align:start position:0% compatibility which might help alleviate 00:24:06.229 --> 00:24:11.690 align:start position:0% compatibility which might help alleviate the<00:24:07.229> Sinclair<00:24:08.159> issue<00:24:08.369> that<00:24:08.879> I<00:24:09.379> am<00:24:10.379> Boris<00:24:11.249> Boris 00:24:11.690 --> 00:24:11.700 align:start position:0% the Sinclair issue that I am Boris Boris 00:24:11.700 --> 00:24:15.349 align:start position:0% the Sinclair issue that I am Boris Boris mentioned<00:24:12.210> so<00:24:12.960> I'm<00:24:13.049> curious<00:24:13.399> if<00:24:14.399> you<00:24:14.849> you<00:24:15.210> guys 00:24:15.349 --> 00:24:15.359 align:start position:0% mentioned so I'm curious if you you guys 00:24:15.359 --> 00:24:17.329 align:start position:0% mentioned so I'm curious if you you guys could<00:24:15.629> maybe<00:24:16.080> fill<00:24:16.769> me<00:24:16.919> in<00:24:16.950> on<00:24:17.099> that 00:24:17.329 --> 00:24:17.339 align:start position:0% could maybe fill me in on that 00:24:17.339 --> 00:24:23.209 align:start position:0% could maybe fill me in on that and<00:24:17.519> then<00:24:17.639> we<00:24:17.789> can<00:24:19.070> well<00:24:20.070> fulfill<00:24:20.429> EBA<00:24:21.029> 1.5<00:24:22.219> to 00:24:23.209 --> 00:24:23.219 align:start position:0% and then we can well fulfill EBA 1.5 to 00:24:23.219 --> 00:24:26.659 align:start position:0% and then we can well fulfill EBA 1.5 to a<00:24:23.249> simple<00:24:23.759> idea<00:24:23.909> to<00:24:24.539> some<00:24:25.440> progressing<00:24:26.249> on<00:24:26.519> the 00:24:26.659 --> 00:24:26.669 align:start position:0% a simple idea to some progressing on the 00:24:26.669 --> 00:24:29.180 align:start position:0% a simple idea to some progressing on the deployment<00:24:26.969> time<00:24:27.419> so<00:24:28.259> we<00:24:28.469> don't<00:24:28.859> allow 00:24:29.180 --> 00:24:29.190 align:start position:0% deployment time so we don't allow 00:24:29.190 --> 00:24:32.719 align:start position:0% deployment time so we don't allow dynamic<00:24:30.179> jumps<00:24:30.869> anymore<00:24:31.529> I<00:24:31.830> mean<00:24:32.429> we<00:24:32.580> don't 00:24:32.719 --> 00:24:32.729 align:start position:0% dynamic jumps anymore I mean we don't 00:24:32.729 --> 00:24:35.419 align:start position:0% dynamic jumps anymore I mean we don't allow<00:24:33.059> to<00:24:33.089> deploy<00:24:33.779> let's<00:24:34.200> say<00:24:34.440> evn<00:24:34.859> 1.0 00:24:35.419 --> 00:24:35.429 align:start position:0% allow to deploy let's say evn 1.0 00:24:35.429 --> 00:24:38.959 align:start position:0% allow to deploy let's say evn 1.0 contract<00:24:36.389> at<00:24:36.629> some<00:24:36.869> point<00:24:37.109> but<00:24:37.649> they<00:24:38.489> want<00:24:38.669> our 00:24:38.959 --> 00:24:38.969 align:start position:0% contract at some point but they want our 00:24:38.969 --> 00:24:42.099 align:start position:0% contract at some point but they want our dead<00:24:39.269> they<00:24:39.509> will<00:24:39.629> be<00:24:39.749> there<00:24:39.929> all<00:24:40.799> the<00:24:40.979> time<00:24:41.009> I 00:24:42.099 --> 00:24:42.109 align:start position:0% dead they will be there all the time I 00:24:42.109 --> 00:24:46.129 align:start position:0% dead they will be there all the time I have<00:24:43.109> an<00:24:43.200> addition<00:24:43.589> to<00:24:43.710> this<00:24:44.929> so<00:24:45.929> we<00:24:46.049> have 00:24:46.129 --> 00:24:46.139 align:start position:0% have an addition to this so we have 00:24:46.139 --> 00:24:49.070 align:start position:0% have an addition to this so we have these<00:24:46.259> two<00:24:46.919> translation<00:24:47.549> tools<00:24:48.080> originally 00:24:49.070 --> 00:24:49.080 align:start position:0% these two translation tools originally 00:24:49.080 --> 00:24:51.049 align:start position:0% these two translation tools originally named<00:24:49.440> EVM<00:24:49.769> two<00:24:49.889> wasn't<00:24:50.249> but<00:24:50.489> now<00:24:50.669> we<00:24:50.729> have<00:24:51.029> a 00:24:51.049 --> 00:24:51.059 align:start position:0% named EVM two wasn't but now we have a 00:24:51.059 --> 00:24:54.289 align:start position:0% named EVM two wasn't but now we have a new<00:24:51.389> version<00:24:51.539> called<00:24:51.869> ye<00:24:52.109> VM<00:24:52.669> which<00:24:53.669> compiles 00:24:54.289 --> 00:24:54.299 align:start position:0% new version called ye VM which compiles 00:24:54.299 --> 00:24:56.839 align:start position:0% new version called ye VM which compiles even<00:24:54.659> bite<00:24:54.809> kit<00:24:55.049> was<00:24:55.080> invited<00:24:55.679> good<00:24:55.830> now<00:24:56.549> it<00:24:56.700> is 00:24:56.839 --> 00:24:56.849 align:start position:0% even bite kit was invited good now it is 00:24:56.849 --> 00:24:58.579 align:start position:0% even bite kit was invited good now it is not<00:24:56.999> really<00:24:57.269> optimal<00:24:57.690> because<00:24:58.169> of<00:24:58.349> the<00:24:58.440> very 00:24:58.579 --> 00:24:58.589 align:start position:0% not really optimal because of the very 00:24:58.589 --> 00:25:02.119 align:start position:0% not really optimal because of the very same<00:24:58.799> reason<00:24:59.159> but<00:24:59.909> would<00:25:00.149> would<00:25:00.989> even<00:25:01.229> 1.5<00:25:01.769> we 00:25:02.119 --> 00:25:02.129 align:start position:0% same reason but would would even 1.5 we 00:25:02.129 --> 00:25:03.649 align:start position:0% same reason but would would even 1.5 we implemented<00:25:02.639> then<00:25:02.820> we<00:25:03.029> would<00:25:03.239> have<00:25:03.389> a<00:25:03.419> much 00:25:03.649 --> 00:25:03.659 align:start position:0% implemented then we would have a much 00:25:03.659 --> 00:25:08.930 align:start position:0% implemented then we would have a much more<00:25:04.429> optimized<00:25:05.429> compiler<00:25:06.349> I<00:25:07.820> think<00:25:08.820> there's 00:25:08.930 --> 00:25:08.940 align:start position:0% more optimized compiler I think there's 00:25:08.940 --> 00:25:10.669 align:start position:0% more optimized compiler I think there's like<00:25:09.059> an<00:25:09.210> overlap<00:25:09.509> between<00:25:09.629> these<00:25:09.899> things<00:25:10.200> I'm 00:25:10.669 --> 00:25:10.679 align:start position:0% like an overlap between these things I'm 00:25:10.679 --> 00:25:14.389 align:start position:0% like an overlap between these things I'm not<00:25:10.889> fully<00:25:11.190> personally<00:25:12.349> sold<00:25:13.349> on<00:25:13.499> the<00:25:13.710> six<00:25:14.219> one 00:25:14.389 --> 00:25:14.399 align:start position:0% not fully personally sold on the six one 00:25:14.399 --> 00:25:17.930 align:start position:0% not fully personally sold on the six one six<00:25:14.719> the<00:25:15.719> IP<00:25:15.899> which<00:25:16.259> is<00:25:16.469> the<00:25:16.679> simple<00:25:17.460> editor 00:25:17.930 --> 00:25:17.940 align:start position:0% six the IP which is the simple editor 00:25:17.940 --> 00:25:19.969 align:start position:0% six the IP which is the simple editor but<00:25:18.629> six<00:25:18.899> one<00:25:19.019> five<00:25:19.229> I<00:25:19.289> think<00:25:19.679> it's<00:25:19.859> a 00:25:19.969 --> 00:25:19.979 align:start position:0% but six one five I think it's a 00:25:19.979 --> 00:25:22.129 align:start position:0% but six one five I think it's a low-hanging<00:25:20.249> fruit<00:25:20.639> and<00:25:21.359> if<00:25:21.719> you<00:25:21.809> combine<00:25:22.109> it 00:25:22.129 --> 00:25:22.139 align:start position:0% low-hanging fruit and if you combine it 00:25:22.139 --> 00:25:24.289 align:start position:0% low-hanging fruit and if you combine it together<00:25:22.379> with<00:25:22.769> what<00:25:22.799> Pablo<00:25:23.309> said<00:25:23.639> that<00:25:23.909> okay 00:25:24.289 --> 00:25:24.299 align:start position:0% together with what Pablo said that okay 00:25:24.299 --> 00:25:27.829 align:start position:0% together with what Pablo said that okay we<00:25:24.450> disable<00:25:25.369> the<00:25:26.369> 1.0<00:25:26.789> deployments<00:25:27.419> and<00:25:27.599> it's 00:25:27.829 --> 00:25:27.839 align:start position:0% we disable the 1.0 deployments and it's 00:25:27.839 --> 00:25:29.749 align:start position:0% we disable the 1.0 deployments and it's only<00:25:27.989> just<00:25:28.080> this<00:25:28.440> one<00:25:28.979> point<00:25:29.190> five<00:25:29.369> which<00:25:29.549> is 00:25:29.749 --> 00:25:29.759 align:start position:0% only just this one point five which is 00:25:29.759 --> 00:25:32.149 align:start position:0% only just this one point five which is the<00:25:29.879> six<00:25:30.119> one<00:25:30.330> finds<00:25:30.719> so<00:25:31.169> many<00:25:31.349> numbers<00:25:31.619> anyway 00:25:32.149 --> 00:25:32.159 align:start position:0% the six one finds so many numbers anyway 00:25:32.159 --> 00:25:34.820 align:start position:0% the six one finds so many numbers anyway it's<00:25:32.339> just<00:25:32.729> about<00:25:32.969> the<00:25:33.409> that<00:25:34.409> could<00:25:34.559> be<00:25:34.649> moving 00:25:34.820 --> 00:25:34.830 align:start position:0% it's just about the that could be moving 00:25:34.830 --> 00:25:37.279 align:start position:0% it's just about the that could be moving dynamic<00:25:35.279> jumps<00:25:35.669> jump<00:25:36.089> so<00:25:36.269> if<00:25:36.359> we<00:25:36.509> enable<00:25:37.109> that 00:25:37.279 --> 00:25:37.289 align:start position:0% dynamic jumps jump so if we enable that 00:25:37.289 --> 00:25:39.739 align:start position:0% dynamic jumps jump so if we enable that forcefully<00:25:38.099> and<00:25:38.339> disable<00:25:39.089> deploying<00:25:39.599> hold 00:25:39.739 --> 00:25:39.749 align:start position:0% forcefully and disable deploying hold 00:25:39.749 --> 00:25:43.999 align:start position:0% forcefully and disable deploying hold contracts<00:25:41.690> the<00:25:42.690> solar<00:25:43.320> compiler<00:25:43.739> already 00:25:43.999 --> 00:25:44.009 align:start position:0% contracts the solar compiler already 00:25:44.009 --> 00:25:45.829 align:start position:0% contracts the solar compiler already supports<00:25:44.429> it<00:25:44.580> I<00:25:45.029> think<00:25:45.509> there<00:25:45.629> was<00:25:45.749> an 00:25:45.829 --> 00:25:45.839 align:start position:0% supports it I think there was an 00:25:45.839 --> 00:25:47.810 align:start position:0% supports it I think there was an implementation<00:25:46.379> you<00:25:46.470> made<00:25:46.619> in<00:25:46.739> allit<00:25:47.070> it's 00:25:47.810 --> 00:25:47.820 align:start position:0% implementation you made in allit it's 00:25:47.820 --> 00:25:50.389 align:start position:0% implementation you made in allit it's likely<00:25:48.269> it's<00:25:48.629> a<00:25:48.749> low-hanging<00:25:48.989> fruit<00:25:49.409> which<00:25:50.220> I 00:25:50.389 --> 00:25:50.399 align:start position:0% likely it's a low-hanging fruit which I 00:25:50.399 --> 00:25:51.950 align:start position:0% likely it's a low-hanging fruit which I think<00:25:50.700> could<00:25:50.909> be<00:25:51.089> I<00:25:51.119> mean<00:25:51.269> I<00:25:51.599> would 00:25:51.950 --> 00:25:51.960 align:start position:0% think could be I mean I would 00:25:51.960 --> 00:25:53.950 align:start position:0% think could be I mean I would optimistic<00:25:52.740> to<00:25:53.250> even<00:25:53.430> have<00:25:53.580> it<00:25:53.670> after 00:25:53.950 --> 00:25:53.960 align:start position:0% optimistic to even have it after 00:25:53.960 --> 00:25:56.150 align:start position:0% optimistic to even have it after Constantinople<00:25:54.960> but<00:25:55.140> just<00:25:55.740> right<00:25:55.890> people 00:25:56.150 --> 00:25:56.160 align:start position:0% Constantinople but just right people 00:25:56.160 --> 00:25:57.770 align:start position:0% Constantinople but just right people have<00:25:56.250> to<00:25:56.370> be<00:25:56.460> convinced<00:25:56.880> but<00:25:57.540> it<00:25:57.630> definitely 00:25:57.770 --> 00:25:57.780 align:start position:0% have to be convinced but it definitely 00:25:57.780 --> 00:26:00.560 align:start position:0% have to be convinced but it definitely this<00:25:58.590> single<00:25:58.980> step<00:25:59.220> does<00:26:00.000> help<00:26:00.360> the 00:26:00.560 --> 00:26:00.570 align:start position:0% this single step does help the 00:26:00.570 --> 00:26:02.960 align:start position:0% this single step does help the transition<00:26:01.200> to<00:26:01.530> tui<00:26:01.890> was<00:26:02.130> amiss<00:26:02.400> well<00:26:02.640> if<00:26:02.850> you 00:26:02.960 --> 00:26:02.970 align:start position:0% transition to tui was amiss well if you 00:26:02.970 --> 00:26:04.220 align:start position:0% transition to tui was amiss well if you want<00:26:03.120> to<00:26:03.210> keep<00:26:03.360> backwards<00:26:03.780> compatibility 00:26:04.220 --> 00:26:04.230 align:start position:0% want to keep backwards compatibility 00:26:04.230 --> 00:26:05.510 align:start position:0% want to keep backwards compatibility between<00:26:04.740> that's<00:26:05.040> mean 00:26:05.510 --> 00:26:05.520 align:start position:0% between that's mean 00:26:05.520 --> 00:26:10.280 align:start position:0% between that's mean yeah<00:26:05.970> the<00:26:06.150> code<00:26:06.650> the<00:26:07.650> code<00:26:07.830> is<00:26:08.070> in<00:26:08.660> is<00:26:09.660> in<00:26:09.720> there 00:26:10.280 --> 00:26:10.290 align:start position:0% yeah the code the code is in is in there 00:26:10.290 --> 00:26:12.410 align:start position:0% yeah the code the code is in is in there I<00:26:10.500> think<00:26:10.590> last<00:26:11.130> time<00:26:11.250> I<00:26:11.400> looked<00:26:11.790> you<00:26:11.940> you've 00:26:12.410 --> 00:26:12.420 align:start position:0% I think last time I looked you you've 00:26:12.420 --> 00:26:14.300 align:start position:0% I think last time I looked you you've moved<00:26:12.630> it<00:26:12.900> to<00:26:13.050> the<00:26:13.170> side<00:26:13.440> that<00:26:13.860> it's<00:26:14.070> still 00:26:14.300 --> 00:26:14.310 align:start position:0% moved it to the side that it's still 00:26:14.310 --> 00:26:14.960 align:start position:0% moved it to the side that it's still there 00:26:14.960 --> 00:26:14.970 align:start position:0% there 00:26:14.970 --> 00:26:18.050 align:start position:0% there I<00:26:15.000> think<00:26:15.480> it's<00:26:15.660> not<00:26:15.750> there<00:26:15.930> anymore<00:26:17.060> over 00:26:18.050 --> 00:26:18.060 align:start position:0% I think it's not there anymore over 00:26:18.060 --> 00:26:22.910 align:start position:0% I think it's not there anymore over didn't<00:26:18.900> you<00:26:18.990> have<00:26:19.170> your<00:26:19.200> legacy<00:26:21.590> anyway<00:26:22.590> it's 00:26:22.910 --> 00:26:22.920 align:start position:0% didn't you have your legacy anyway it's 00:26:22.920 --> 00:26:25.040 align:start position:0% didn't you have your legacy anyway it's it's<00:26:23.280> chip<00:26:23.700> it's<00:26:23.970> somewhere<00:26:24.360> down<00:26:24.420> in<00:26:24.600> there 00:26:25.040 --> 00:26:25.050 align:start position:0% it's chip it's somewhere down in there 00:26:25.050 --> 00:26:27.680 align:start position:0% it's chip it's somewhere down in there somewhere<00:26:25.320> they<00:26:26.280> can<00:26:26.460> be<00:26:26.580> pulled<00:26:26.820> back<00:26:27.090> out<00:26:27.330> it 00:26:27.680 --> 00:26:27.690 align:start position:0% somewhere they can be pulled back out it 00:26:27.690 --> 00:26:29.600 align:start position:0% somewhere they can be pulled back out it was<00:26:27.810> implemented<00:26:28.530> some<00:26:28.770> testing<00:26:29.190> needs<00:26:29.370> to<00:26:29.520> be 00:26:29.600 --> 00:26:29.610 align:start position:0% was implemented some testing needs to be 00:26:29.610 --> 00:26:33.740 align:start position:0% was implemented some testing needs to be done<00:26:29.780> yeah<00:26:30.780> but<00:26:31.110> it<00:26:31.230> doesn't<00:26:31.670> yeah<00:26:32.670> I<00:26:32.970> can<00:26:33.570> work 00:26:33.740 --> 00:26:33.750 align:start position:0% done yeah but it doesn't yeah I can work 00:26:33.750 --> 00:26:35.660 align:start position:0% done yeah but it doesn't yeah I can work alone<00:26:34.020> for<00:26:34.290> six<00:26:34.530> months<00:26:34.920> and<00:26:35.190> and<00:26:35.460> have 00:26:35.660 --> 00:26:35.670 align:start position:0% alone for six months and and have 00:26:35.670 --> 00:26:39.110 align:start position:0% alone for six months and and have something<00:26:36.620> then<00:26:37.620> we'll<00:26:37.800> need<00:26:38.460> some<00:26:38.730> more<00:26:38.760> help 00:26:39.110 --> 00:26:39.120 align:start position:0% something then we'll need some more help 00:26:39.120 --> 00:26:42.470 align:start position:0% something then we'll need some more help on<00:26:39.360> some<00:26:39.570> other<00:26:39.750> stuff<00:26:39.980> but<00:26:41.090> it's<00:26:42.090> just<00:26:42.180> not 00:26:42.470 --> 00:26:42.480 align:start position:0% on some other stuff but it's just not 00:26:42.480 --> 00:26:47.210 align:start position:0% on some other stuff but it's just not that<00:26:42.810> hard<00:26:43.140> to<00:26:43.470> get<00:26:44.040> that<00:26:44.280> going<00:26:45.710> in<00:26:46.710> depending 00:26:47.210 --> 00:26:47.220 align:start position:0% that hard to get that going in depending 00:26:47.220 --> 00:26:48.800 align:start position:0% that hard to get that going in depending on<00:26:47.370> scheduling<00:26:47.910> I<00:26:48.060> think<00:26:48.330> it<00:26:48.480> can<00:26:48.630> be<00:26:48.660> done 00:26:48.800 --> 00:26:48.810 align:start position:0% on scheduling I think it can be done 00:26:48.810 --> 00:26:53.530 align:start position:0% on scheduling I think it can be done more<00:26:49.230> quickly<00:26:50.030> than<00:26:51.030> you<00:26:51.210> ask<00:26:51.450> them<00:26:52.040> can<00:26:53.040> be 00:26:53.530 --> 00:26:53.540 align:start position:0% more quickly than you ask them can be 00:26:53.540 --> 00:27:00.350 align:start position:0% more quickly than you ask them can be can<00:26:54.540> be<00:26:54.570> delivered<00:26:57.950> so<00:26:58.950> it<00:26:59.010> was<00:26:59.160> related<00:27:00.150> but 00:27:00.350 --> 00:27:00.360 align:start position:0% can be delivered so it was related but 00:27:00.360 --> 00:27:02.000 align:start position:0% can be delivered so it was related but slightly<00:27:00.510> higher<00:27:00.930> level<00:27:00.960> question<00:27:01.620> why<00:27:01.950> do 00:27:02.000 --> 00:27:02.010 align:start position:0% slightly higher level question why do 00:27:02.010 --> 00:27:04.370 align:start position:0% slightly higher level question why do you<00:27:02.280> guys<00:27:02.460> think<00:27:02.880> EVM<00:27:03.600> has<00:27:03.780> been<00:27:03.960> so<00:27:04.140> slow<00:27:04.200> to 00:27:04.370 --> 00:27:04.380 align:start position:0% you guys think EVM has been so slow to 00:27:04.380 --> 00:27:07.400 align:start position:0% you guys think EVM has been so slow to be<00:27:04.590> evolved<00:27:05.510> as<00:27:06.510> a<00:27:06.570> technical<00:27:07.110> is<00:27:07.290> it 00:27:07.400 --> 00:27:07.410 align:start position:0% be evolved as a technical is it 00:27:07.410 --> 00:27:09.350 align:start position:0% be evolved as a technical is it political<00:27:07.830> is<00:27:07.920> it<00:27:08.010> something<00:27:08.160> else<00:27:08.400> because 00:27:09.350 --> 00:27:09.360 align:start position:0% political is it something else because 00:27:09.360 --> 00:27:17.900 align:start position:0% political is it something else because no<00:27:09.720> resources<00:27:10.290> were<00:27:10.620> put<00:27:10.830> into<00:27:11.070> it<00:27:11.370> I<00:27:16.910> think 00:27:17.900 --> 00:27:17.910 align:start position:0% no resources were put into it I think 00:27:17.910 --> 00:27:20.180 align:start position:0% no resources were put into it I think one<00:27:18.180> of<00:27:18.210> the<00:27:18.390> issues<00:27:18.510> that<00:27:18.750> we<00:27:18.990> have<00:27:19.230> is<00:27:19.680> we 00:27:20.180 --> 00:27:20.190 align:start position:0% one of the issues that we have is we 00:27:20.190 --> 00:27:24.230 align:start position:0% one of the issues that we have is we look<00:27:20.430> at<00:27:20.670> a<00:27:21.530> couple<00:27:22.530> of<00:27:22.680> things<00:27:22.830> I<00:27:23.220> see<00:27:23.760> a<00:27:23.790> split 00:27:24.230 --> 00:27:24.240 align:start position:0% look at a couple of things I see a split 00:27:24.240 --> 00:27:28.910 align:start position:0% look at a couple of things I see a split split<00:27:24.750> between<00:27:26.360> researchers<00:27:27.920> implementers 00:27:28.910 --> 00:27:28.920 align:start position:0% split between researchers implementers 00:27:28.920 --> 00:27:31.730 align:start position:0% split between researchers implementers and<00:27:29.300> people<00:27:30.300> who<00:27:30.480> are<00:27:30.630> attempting<00:27:30.990> to<00:27:31.230> ship 00:27:31.730 --> 00:27:31.740 align:start position:0% and people who are attempting to ship 00:27:31.740 --> 00:27:34.220 align:start position:0% and people who are attempting to ship bug-free<00:27:32.460> production<00:27:33.210> code<00:27:33.450> on<00:27:33.720> top<00:27:33.960> of<00:27:34.110> the 00:27:34.220 --> 00:27:34.230 align:start position:0% bug-free production code on top of the 00:27:34.230 --> 00:27:36.140 align:start position:0% bug-free production code on top of the world<00:27:34.380> computer<00:27:34.890> all<00:27:35.190> of<00:27:35.430> which<00:27:35.850> that<00:27:36.030> are 00:27:36.140 --> 00:27:36.150 align:start position:0% world computer all of which that are 00:27:36.150 --> 00:27:41.540 align:start position:0% world computer all of which that are happening<00:27:36.330> at<00:27:36.630> the<00:27:36.660> same<00:27:37.040> time<00:27:38.570> and<00:27:40.550> again 00:27:41.540 --> 00:27:41.550 align:start position:0% happening at the same time and again 00:27:41.550 --> 00:27:43.820 align:start position:0% happening at the same time and again always<00:27:41.880> a<00:27:42.060> hard<00:27:42.390> call<00:27:43.020> to<00:27:43.290> say<00:27:43.500> when<00:27:43.710> you 00:27:43.820 --> 00:27:43.830 align:start position:0% always a hard call to say when you 00:27:43.830 --> 00:27:45.680 align:start position:0% always a hard call to say when you should<00:27:44.040> ditch<00:27:44.370> old<00:27:44.700> and<00:27:44.970> go<00:27:45.120> to<00:27:45.180> new<00:27:45.420> and 00:27:45.680 --> 00:27:45.690 align:start position:0% should ditch old and go to new and 00:27:45.690 --> 00:27:46.970 align:start position:0% should ditch old and go to new and everything<00:27:45.900> else<00:27:46.110> like<00:27:46.290> that<00:27:46.320> but<00:27:46.710> if<00:27:46.830> the 00:27:46.970 --> 00:27:46.980 align:start position:0% everything else like that but if the 00:27:46.980 --> 00:27:49.640 align:start position:0% everything else like that but if the people<00:27:47.160> who<00:27:47.490> do<00:27:47.640> research<00:27:48.110> never<00:27:49.110> have<00:27:49.380> to<00:27:49.530> do 00:27:49.640 --> 00:27:49.650 align:start position:0% people who do research never have to do 00:27:49.650 --> 00:27:51.860 align:start position:0% people who do research never have to do production<00:27:49.980> implementation<00:27:50.880> it's<00:27:51.480> the<00:27:51.630> same 00:27:51.860 --> 00:27:51.870 align:start position:0% production implementation it's the same 00:27:51.870 --> 00:27:54.350 align:start position:0% production implementation it's the same issue<00:27:52.110> between<00:27:52.550> DevOps<00:27:53.550> and<00:27:53.790> developers<00:27:54.210> if 00:27:54.350 --> 00:27:54.360 align:start position:0% issue between DevOps and developers if 00:27:54.360 --> 00:27:55.520 align:start position:0% issue between DevOps and developers if you<00:27:54.450> never<00:27:54.630> actually<00:27:54.960> mean<00:27:55.110> to<00:27:55.140> have<00:27:55.440> to 00:27:55.520 --> 00:27:55.530 align:start position:0% you never actually mean to have to 00:27:55.530 --> 00:27:58.010 align:start position:0% you never actually mean to have to maintain<00:27:55.680> separate<00:27:56.190> production<00:27:56.370> a<00:27:57.330> research 00:27:58.010 --> 00:27:58.020 align:start position:0% maintain separate production a research 00:27:58.020 --> 00:27:59.930 align:start position:0% maintain separate production a research engine<00:27:58.560> needs<00:27:59.010> to<00:27:59.130> be<00:27:59.220> built<00:27:59.430> differently 00:27:59.930 --> 00:27:59.940 align:start position:0% engine needs to be built differently 00:27:59.940 --> 00:28:02.930 align:start position:0% engine needs to be built differently rather<00:28:00.720> than<00:28:00.960> optimizing<00:28:01.710> for<00:28:02.010> people<00:28:02.820> who 00:28:02.930 --> 00:28:02.940 align:start position:0% rather than optimizing for people who 00:28:02.940 --> 00:28:05.370 align:start position:0% rather than optimizing for people who actually<00:28:03.180> have<00:28:03.540> to<00:28:03.630> ship<00:28:03.810> code<00:28:04.020> in<00:28:04.170> production 00:28:05.370 --> 00:28:05.380 align:start position:0% actually have to ship code in production 00:28:05.380 --> 00:28:07.470 align:start position:0% actually have to ship code in production it<00:28:05.440> feels<00:28:05.800> like<00:28:05.980> there<00:28:06.310> was<00:28:06.430> a<00:28:06.460> large<00:28:06.820> movement 00:28:07.470 --> 00:28:07.480 align:start position:0% it feels like there was a large movement 00:28:07.480 --> 00:28:14.640 align:start position:0% it feels like there was a large movement for<00:28:07.810> whatever<00:28:07.990> reason<00:28:08.640> to<00:28:09.990> new<00:28:10.990> new<00:28:12.630> and<00:28:13.650> we 00:28:14.640 --> 00:28:14.650 align:start position:0% for whatever reason to new new and we 00:28:14.650 --> 00:28:18.420 align:start position:0% for whatever reason to new new and we should<00:28:14.920> not<00:28:15.160> be<00:28:15.400> afraid<00:28:15.670> to<00:28:15.790> keep<00:28:17.190> fixing<00:28:18.190> old 00:28:18.420 --> 00:28:18.430 align:start position:0% should not be afraid to keep fixing old 00:28:18.430 --> 00:28:19.980 align:start position:0% should not be afraid to keep fixing old stuff<00:28:18.760> maybe<00:28:19.030> there<00:28:19.210> was<00:28:19.300> another<00:28:19.330> perception 00:28:19.980 --> 00:28:19.990 align:start position:0% stuff maybe there was another perception 00:28:19.990 --> 00:28:22.860 align:start position:0% stuff maybe there was another perception that<00:28:20.950> fixing<00:28:21.460> a<00:28:21.550> VM<00:28:21.760> was<00:28:21.970> hard<00:28:22.270> but<00:28:22.660> if<00:28:22.780> you 00:28:22.860 --> 00:28:22.870 align:start position:0% that fixing a VM was hard but if you 00:28:22.870 --> 00:28:24.890 align:start position:0% that fixing a VM was hard but if you just<00:28:23.080> bring<00:28:23.380> in<00:28:23.560> people<00:28:23.740> with<00:28:23.980> vm<00:28:24.220> expertise 00:28:24.890 --> 00:28:24.900 align:start position:0% just bring in people with vm expertise 00:28:24.900 --> 00:28:33.000 align:start position:0% just bring in people with vm expertise it's<00:28:25.900> not<00:28:26.050> that<00:28:26.230> hard<00:28:28.530> my<00:28:29.530> opinion<00:28:31.860> we<00:28:32.860> have<00:28:32.890> a 00:28:33.000 --> 00:28:33.010 align:start position:0% it's not that hard my opinion we have a 00:28:33.010 --> 00:28:34.500 align:start position:0% it's not that hard my opinion we have a late<00:28:33.220> addition<00:28:33.460> to<00:28:33.610> the<00:28:33.760> panel<00:28:34.030> everyone 00:28:34.500 --> 00:28:34.510 align:start position:0% late addition to the panel everyone 00:28:34.510 --> 00:28:39.480 align:start position:0% late addition to the panel everyone introduce<00:28:34.630> yourself<00:28:37.650> I'm<00:28:38.650> every<00:28:39.010> Eldon<00:28:39.280> brand 00:28:39.480 --> 00:28:39.490 align:start position:0% introduce yourself I'm every Eldon brand 00:28:39.490 --> 00:28:42.150 align:start position:0% introduce yourself I'm every Eldon brand I've<00:28:39.670> been<00:28:39.850> working<00:28:40.180> on<00:28:41.070> formalization<00:28:42.070> of 00:28:42.150 --> 00:28:42.160 align:start position:0% I've been working on formalization of 00:28:42.160 --> 00:28:44.040 align:start position:0% I've been working on formalization of VMs<00:28:42.490> and<00:28:42.880> stuff<00:28:43.240> I<00:28:43.330> gotta<00:28:43.510> had<00:28:43.690> some<00:28:43.870> meetings 00:28:44.040 --> 00:28:44.050 align:start position:0% VMs and stuff I gotta had some meetings 00:28:44.050 --> 00:28:47.220 align:start position:0% VMs and stuff I gotta had some meetings before<00:28:44.440> this<00:28:44.620> but<00:28:45.060> one<00:28:46.060> thing<00:28:46.420> I've<00:28:46.930> worked<00:28:47.110> on 00:28:47.220 --> 00:28:47.230 align:start position:0% before this but one thing I've worked on 00:28:47.230 --> 00:28:51.330 align:start position:0% before this but one thing I've worked on formalizing<00:28:47.890> is<00:28:47.980> the<00:28:48.100> Waze<00:28:48.280> and<00:28:48.490> VM<00:28:50.040> but<00:28:51.040> not 00:28:51.330 --> 00:28:51.340 align:start position:0% formalizing is the Waze and VM but not 00:28:51.340 --> 00:28:52.110 align:start position:0% formalizing is the Waze and VM but not as<00:28:51.430> much<00:28:51.550> recently 00:28:52.110 --> 00:28:52.120 align:start position:0% as much recently 00:28:52.120 --> 00:28:56.280 align:start position:0% as much recently cuz<00:28:52.870> I've<00:28:53.020> been<00:28:53.170> busy<00:28:53.440> with<00:28:53.530> things<00:28:55.110> but<00:28:56.110> don't 00:28:56.280 --> 00:28:56.290 align:start position:0% cuz I've been busy with things but don't 00:28:56.290 --> 00:28:59.340 align:start position:0% cuz I've been busy with things but don't be<00:28:56.350> shy<00:28:56.530> you<00:28:56.590> what's<00:28:56.800> a<00:28:56.890> big<00:28:57.070> ke<00:28:57.490> VM<00:28:57.850> oh<00:28:58.150> yeah 00:28:59.340 --> 00:28:59.350 align:start position:0% be shy you what's a big ke VM oh yeah 00:28:59.350 --> 00:29:01.560 align:start position:0% be shy you what's a big ke VM oh yeah so<00:28:59.560> one<00:29:00.010> thing<00:29:00.280> one<00:29:00.670> topic<00:29:01.060> can<00:29:01.330> you<00:29:01.390> speak 00:29:01.560 --> 00:29:01.570 align:start position:0% so one thing one topic can you speak 00:29:01.570 --> 00:29:03.270 align:start position:0% so one thing one topic can you speak about<00:29:01.630> I<00:29:01.960> yell<00:29:02.170> eat<00:29:02.320> a<00:29:02.410> tiny<00:29:02.650> a<00:29:02.710> little<00:29:02.740> bit<00:29:02.980> we 00:29:03.270 --> 00:29:03.280 align:start position:0% about I yell eat a tiny a little bit we 00:29:03.280 --> 00:29:04.620 align:start position:0% about I yell eat a tiny a little bit we feel<00:29:03.460> confident<00:29:03.760> to<00:29:03.790> do<00:29:03.880> that<00:29:04.030> one<00:29:04.420> thing<00:29:04.450> that 00:29:04.620 --> 00:29:04.630 align:start position:0% feel confident to do that one thing that 00:29:04.630 --> 00:29:06.060 align:start position:0% feel confident to do that one thing that came<00:29:04.840> up<00:29:04.990> was<00:29:05.110> this<00:29:05.290> other<00:29:05.440> virtual<00:29:05.830> machine 00:29:06.060 --> 00:29:06.070 align:start position:0% came up was this other virtual machine 00:29:06.070 --> 00:29:08.070 align:start position:0% came up was this other virtual machine would<00:29:06.250> you<00:29:06.340> mind<00:29:06.670> taking<00:29:07.000> 60<00:29:07.630> seconds<00:29:07.930> to<00:29:07.990> tell 00:29:08.070 --> 00:29:08.080 align:start position:0% would you mind taking 60 seconds to tell 00:29:08.080 --> 00:29:09.420 align:start position:0% would you mind taking 60 seconds to tell us<00:29:08.110> what<00:29:08.290> that<00:29:08.410> is<00:29:08.470> and<00:29:08.710> how<00:29:08.800> it's<00:29:08.950> similar<00:29:09.220> or 00:29:09.420 --> 00:29:09.430 align:start position:0% us what that is and how it's similar or 00:29:09.430 --> 00:29:13.860 align:start position:0% us what that is and how it's similar or different<00:29:09.550> to<00:29:09.730> the<00:29:10.090> VM<00:29:10.360> it<00:29:10.480> wasn't<00:29:12.090> so<00:29:13.090> y<00:29:13.120> la<00:29:13.630> is 00:29:13.860 --> 00:29:13.870 align:start position:0% different to the VM it wasn't so y la is 00:29:13.870 --> 00:29:17.400 align:start position:0% different to the VM it wasn't so y la is VM<00:29:14.590> that<00:29:14.830> we<00:29:14.920> designed<00:29:15.280> for<00:29:15.840> weaving<00:29:16.840> runtime 00:29:17.400 --> 00:29:17.410 align:start position:0% VM that we designed for weaving runtime 00:29:17.410 --> 00:29:19.740 align:start position:0% VM that we designed for weaving runtime verification<00:29:18.070> designed<00:29:18.400> for<00:29:18.670> the<00:29:19.270> Cardinal 00:29:19.740 --> 00:29:19.750 align:start position:0% verification designed for the Cardinal 00:29:19.750 --> 00:29:25.890 align:start position:0% verification designed for the Cardinal Network<00:29:20.520> and<00:29:22.350> it<00:29:23.910> has<00:29:24.910> a<00:29:24.940> lot<00:29:25.300> of<00:29:25.330> similarities 00:29:25.890 --> 00:29:25.900 align:start position:0% Network and it has a lot of similarities 00:29:25.900 --> 00:29:28.800 align:start position:0% Network and it has a lot of similarities to<00:29:25.930> LLVM<00:29:26.470> we've<00:29:27.130> had<00:29:27.250> some<00:29:27.460> VM<00:29:27.970> experts<00:29:28.540> kind 00:29:28.800 --> 00:29:28.810 align:start position:0% to LLVM we've had some VM experts kind 00:29:28.810 --> 00:29:30.420 align:start position:0% to LLVM we've had some VM experts kind of<00:29:28.870> on<00:29:28.990> our<00:29:29.020> team<00:29:29.260> who<00:29:29.650> helped<00:29:29.980> us<00:29:30.070> design<00:29:30.250> it 00:29:30.420 --> 00:29:30.430 align:start position:0% of on our team who helped us design it 00:29:30.430 --> 00:29:33.510 align:start position:0% of on our team who helped us design it and<00:29:31.210> we<00:29:31.420> mostly<00:29:31.690> tried<00:29:31.930> to<00:29:32.050> avoid<00:29:32.350> building<00:29:33.280> in 00:29:33.510 --> 00:29:33.520 align:start position:0% and we mostly tried to avoid building in 00:29:33.520 --> 00:29:34.890 align:start position:0% and we mostly tried to avoid building in anything<00:29:33.760> that<00:29:33.940> would<00:29:34.120> make<00:29:34.150> verification 00:29:34.890 --> 00:29:34.900 align:start position:0% anything that would make verification 00:29:34.900 --> 00:29:38.100 align:start position:0% anything that would make verification difficult<00:29:35.580> to<00:29:36.580> the<00:29:36.670> VM<00:29:36.940> so<00:29:37.360> things<00:29:37.810> like<00:29:37.930> hem 00:29:38.100 --> 00:29:38.110 align:start position:0% difficult to the VM so things like hem 00:29:38.110 --> 00:29:42.660 align:start position:0% difficult to the VM so things like hem store<00:29:38.380> eight<00:29:38.530> or<00:29:39.900> other<00:29:41.100> issues<00:29:42.100> with<00:29:42.280> the<00:29:42.370> EVM 00:29:42.660 --> 00:29:42.670 align:start position:0% store eight or other issues with the EVM 00:29:42.670 --> 00:29:44.340 align:start position:0% store eight or other issues with the EVM we<00:29:42.820> kind<00:29:43.000> of<00:29:43.090> tried<00:29:43.240> to<00:29:43.270> avoid<00:29:43.540> it's<00:29:44.290> a 00:29:44.340 --> 00:29:44.350 align:start position:0% we kind of tried to avoid it's a 00:29:44.350 --> 00:29:48.150 align:start position:0% we kind of tried to avoid it's a registered<00:29:44.770> based<00:29:45.240> machine<00:29:46.240> so<00:29:47.010> people<00:29:48.010> have 00:29:48.150 --> 00:29:48.160 align:start position:0% registered based machine so people have 00:29:48.160 --> 00:29:50.730 align:start position:0% registered based machine so people have different<00:29:48.460> opinions<00:29:48.520> on<00:29:48.940> that<00:29:49.120> I<00:29:50.050> don't 00:29:50.730 --> 00:29:50.740 align:start position:0% different opinions on that I don't 00:29:50.740 --> 00:29:53.730 align:start position:0% different opinions on that I don't really<00:29:50.860> care<00:29:51.100> either<00:29:51.160> way<00:29:51.370> and<00:29:52.050> it<00:29:53.050> supports 00:29:53.730 --> 00:29:53.740 align:start position:0% really care either way and it supports 00:29:53.740 --> 00:29:56.490 align:start position:0% really care either way and it supports out-of-the-box<00:29:54.430> unbounded<00:29:55.500> integer 00:29:56.490 --> 00:29:56.500 align:start position:0% out-of-the-box unbounded integer 00:29:56.500 --> 00:30:00.450 align:start position:0% out-of-the-box unbounded integer arithmetic<00:29:57.360> so<00:29:58.360> you<00:29:58.420> can<00:29:58.630> just<00:29:58.810> use<00:29:59.800> a<00:29:59.830> proper 00:30:00.450 --> 00:30:00.460 align:start position:0% arithmetic so you can just use a proper 00:30:00.460 --> 00:30:03.000 align:start position:0% arithmetic so you can just use a proper end<00:30:00.640> type<00:30:00.910> in<00:30:01.210> the<00:30:01.420> VM<00:30:01.630> but<00:30:01.900> then<00:30:02.020> we<00:30:02.140> have<00:30:02.320> kind 00:30:03.000 --> 00:30:03.010 align:start position:0% end type in the VM but then we have kind 00:30:03.010 --> 00:30:05.610 align:start position:0% end type in the VM but then we have kind of<00:30:03.040> a<00:30:03.300> more<00:30:04.300> complicated<00:30:04.630> gas<00:30:05.080> model<00:30:05.500> to 00:30:05.610 --> 00:30:05.620 align:start position:0% of a more complicated gas model to 00:30:05.620 --> 00:30:11.340 align:start position:0% of a more complicated gas model to account<00:30:05.860> for<00:30:05.980> that<00:30:09.660> just<00:30:10.660> when<00:30:10.750> I<00:30:10.780> reread<00:30:11.230> the 00:30:11.340 --> 00:30:11.350 align:start position:0% account for that just when I reread the 00:30:11.350 --> 00:30:13.230 align:start position:0% account for that just when I reread the question<00:30:11.380> because<00:30:11.800> we<00:30:11.890> were<00:30:11.980> late<00:30:12.210> the<00:30:13.210> the 00:30:13.230 --> 00:30:13.240 align:start position:0% question because we were late the the 00:30:13.240 --> 00:30:16.260 align:start position:0% question because we were late the the question<00:30:13.870> was<00:30:14.050> why<00:30:14.380> didn<00:30:15.070> t<00:30:15.100> vm<00:30:15.490> improve<00:30:16.030> over 00:30:16.260 --> 00:30:16.270 align:start position:0% question was why didn t vm improve over 00:30:16.270 --> 00:30:17.250 align:start position:0% question was why didn t vm improve over time 00:30:17.250 --> 00:30:17.260 align:start position:0% time 00:30:17.260 --> 00:30:19.530 align:start position:0% time um<00:30:17.440> and<00:30:18.370> Boris<00:30:18.850> explained<00:30:19.180> a<00:30:19.270> couple<00:30:19.480> of 00:30:19.530 --> 00:30:19.540 align:start position:0% um and Boris explained a couple of 00:30:19.540 --> 00:30:22.700 align:start position:0% um and Boris explained a couple of reasons<00:30:19.690> I<00:30:20.110> wanted<00:30:20.590> to<00:30:20.650> add<00:30:20.830> a<00:30:20.860> single<00:30:21.100> reason 00:30:22.700 --> 00:30:22.710 align:start position:0% reasons I wanted to add a single reason 00:30:22.710 --> 00:30:24.900 align:start position:0% reasons I wanted to add a single reason which<00:30:23.710> also<00:30:23.890> Greg<00:30:24.100> mentioned<00:30:24.340> that<00:30:24.580> lack<00:30:24.790> of 00:30:24.900 --> 00:30:24.910 align:start position:0% which also Greg mentioned that lack of 00:30:24.910 --> 00:30:28.100 align:start position:0% which also Greg mentioned that lack of resources<00:30:25.300> and<00:30:25.870> a<00:30:26.320> lot<00:30:26.440> of<00:30:27.160> resources<00:30:27.520> were 00:30:28.100 --> 00:30:28.110 align:start position:0% resources and a lot of resources were 00:30:28.110 --> 00:30:31.230 align:start position:0% resources and a lot of resources were shifted<00:30:29.110> -<00:30:29.230> he<00:30:29.320> was<00:30:29.500> him<00:30:29.710> and<00:30:30.120> there<00:30:31.120> weren't 00:30:31.230 --> 00:30:31.240 align:start position:0% shifted - he was him and there weren't 00:30:31.240 --> 00:30:33.330 align:start position:0% shifted - he was him and there weren't any<00:30:31.420> resources<00:30:31.900> left<00:30:32.020> of<00:30:32.170> IBM<00:30:32.590> and<00:30:32.740> then<00:30:33.280> the 00:30:33.330 --> 00:30:33.340 align:start position:0% any resources left of IBM and then the 00:30:33.340 --> 00:30:36.600 align:start position:0% any resources left of IBM and then the same<00:30:33.550> time<00:30:33.820> the<00:30:34.030> the<00:30:34.810> research<00:30:35.110> team<00:30:35.610> also 00:30:36.600 --> 00:30:36.610 align:start position:0% same time the the research team also 00:30:36.610 --> 00:30:38.160 align:start position:0% same time the the research team also shifted<00:30:37.000> their<00:30:37.120> focus<00:30:37.150> and<00:30:37.720> they<00:30:38.020> weren't 00:30:38.160 --> 00:30:38.170 align:start position:0% shifted their focus and they weren't 00:30:38.170 --> 00:30:39.150 align:start position:0% shifted their focus and they weren't really<00:30:38.290> interested<00:30:38.740> in<00:30:38.830> and<00:30:39.040> getting 00:30:39.150 --> 00:30:39.160 align:start position:0% really interested in and getting 00:30:39.160 --> 00:30:41.280 align:start position:0% really interested in and getting anything<00:30:39.460> done<00:30:39.700> an<00:30:39.820> EVM<00:30:40.150> so<00:30:40.900> there<00:30:41.020> was<00:30:41.110> nobody 00:30:41.280 --> 00:30:41.290 align:start position:0% anything done an EVM so there was nobody 00:30:41.290 --> 00:30:43.920 align:start position:0% anything done an EVM so there was nobody to<00:30:41.740> propose<00:30:42.520> except<00:30:43.060> correct<00:30:43.510> to<00:30:43.660> propose 00:30:43.920 --> 00:30:43.930 align:start position:0% to propose except correct to propose 00:30:43.930 --> 00:30:45.780 align:start position:0% to propose except correct to propose ideas<00:30:44.140> and<00:30:44.560> then<00:30:44.710> there<00:30:44.920> was<00:30:45.010> nobody<00:30:45.160> execute 00:30:45.780 --> 00:30:45.790 align:start position:0% ideas and then there was nobody execute 00:30:45.790 --> 00:30:47.550 align:start position:0% ideas and then there was nobody execute those<00:30:46.450> ideas<00:30:46.780> it's<00:30:47.050> really<00:30:47.230> had<00:30:47.320> to<00:30:47.410> work 00:30:47.550 --> 00:30:47.560 align:start position:0% those ideas it's really had to work 00:30:47.560 --> 00:30:52.080 align:start position:0% those ideas it's really had to work alone<00:30:47.850> on<00:30:48.850> improving<00:30:49.210> the<00:30:49.990> EVM<00:30:50.790> so<00:30:51.790> there's 00:30:52.080 --> 00:30:52.090 align:start position:0% alone on improving the EVM so there's 00:30:52.090 --> 00:30:54.060 align:start position:0% alone on improving the EVM so there's been<00:30:52.270> some<00:30:52.450> conversations<00:30:53.230> even<00:30:53.590> here<00:30:53.860> at<00:30:53.920> Def 00:30:54.060 --> 00:30:54.070 align:start position:0% been some conversations even here at Def 00:30:54.070 --> 00:30:56.280 align:start position:0% been some conversations even here at Def Con<00:30:54.100> the<00:30:54.490> past<00:30:54.700> couple<00:30:54.880> of<00:30:55.000> days<00:30:55.150> that<00:30:55.290> maybe 00:30:56.280 --> 00:30:56.290 align:start position:0% Con the past couple of days that maybe 00:30:56.290 --> 00:30:59.700 align:start position:0% Con the past couple of days that maybe while<00:30:56.530> we<00:30:56.680> wait<00:30:56.860> for<00:30:57.960> Jasper<00:30:58.960> sorry<00:30:59.290> of<00:30:59.380> italic 00:30:59.700 --> 00:30:59.710 align:start position:0% while we wait for Jasper sorry of italic 00:30:59.710 --> 00:31:01.950 align:start position:0% while we wait for Jasper sorry of italic eternity<00:31:00.490> to<00:31:00.970> like<00:31:01.150> become<00:31:01.390> a<00:31:01.420> thing<00:31:01.660> and<00:31:01.840> be 00:31:01.950 --> 00:31:01.960 align:start position:0% eternity to like become a thing and be 00:31:01.960 --> 00:31:03.960 align:start position:0% eternity to like become a thing and be alive<00:31:02.200> but<00:31:02.830> there<00:31:03.160> there<00:31:03.460> is<00:31:03.580> value<00:31:03.790> in 00:31:03.960 --> 00:31:03.970 align:start position:0% alive but there there is value in 00:31:03.970 --> 00:31:06.870 align:start position:0% alive but there there is value in reinvesting<00:31:04.600> in<00:31:04.750> etherium<00:31:05.170> 1.0<00:31:05.620> or<00:31:05.860> 1.5<00:31:06.250> or<00:31:06.670> 30 00:31:06.870 --> 00:31:06.880 align:start position:0% reinvesting in etherium 1.0 or 1.5 or 30 00:31:06.880 --> 00:31:08.010 align:start position:0% reinvesting in etherium 1.0 or 1.5 or 30 in<00:31:06.940> the<00:31:07.000> next<00:31:07.180> generation<00:31:07.480> or<00:31:07.720> whatever<00:31:07.780> you 00:31:08.010 --> 00:31:08.020 align:start position:0% in the next generation or whatever you 00:31:08.020 --> 00:31:09.810 align:start position:0% in the next generation or whatever you want<00:31:08.140> to<00:31:08.170> call<00:31:08.350> it<00:31:08.530> is<00:31:08.680> this<00:31:08.890> could<00:31:09.520> this<00:31:09.640> be 00:31:09.810 --> 00:31:09.820 align:start position:0% want to call it is this could this be 00:31:09.820 --> 00:31:10.830 align:start position:0% want to call it is this could this be part<00:31:10.030> of<00:31:10.120> that<00:31:10.240> conversation 00:31:10.830 --> 00:31:10.840 align:start position:0% part of that conversation 00:31:10.840 --> 00:31:12.660 align:start position:0% part of that conversation improving<00:31:11.350> idiom<00:31:11.620> and<00:31:11.860> if<00:31:11.950> so<00:31:12.130> like<00:31:12.400> what 00:31:12.660 --> 00:31:12.670 align:start position:0% improving idiom and if so like what 00:31:12.670 --> 00:31:17.720 align:start position:0% improving idiom and if so like what would<00:31:12.700> that<00:31:12.790> look<00:31:12.910> like<00:31:13.180> maybe<00:31:13.480> I<00:31:15.000> can<00:31:16.000> add<00:31:16.260> one 00:31:17.720 --> 00:31:17.730 align:start position:0% would that look like maybe I can add one 00:31:17.730 --> 00:31:22.860 align:start position:0% would that look like maybe I can add one one<00:31:18.730> side<00:31:18.940> to<00:31:19.090> that<00:31:19.210> I<00:31:20.050> think<00:31:20.710> we<00:31:21.360> say<00:31:22.360> a<00:31:22.600> Tyrian 00:31:22.860 --> 00:31:22.870 align:start position:0% one side to that I think we say a Tyrian 00:31:22.870 --> 00:31:27.330 align:start position:0% one side to that I think we say a Tyrian 1.5<00:31:23.910> billion<00:31:24.910> plan<00:31:25.270> interim<00:31:26.050> no<00:31:26.380> regrets<00:31:26.770> each 00:31:27.330 --> 00:31:27.340 align:start position:0% 1.5 billion plan interim no regrets each 00:31:27.340 --> 00:31:29.190 align:start position:0% 1.5 billion plan interim no regrets each human<00:31:27.640> ji<00:31:27.940> all<00:31:28.450> these<00:31:28.570> different<00:31:28.840> names<00:31:28.990> refer 00:31:29.190 --> 00:31:29.200 align:start position:0% human ji all these different names refer 00:31:29.200 --> 00:31:32.190 align:start position:0% human ji all these different names refer to<00:31:29.260> the<00:31:29.410> same<00:31:29.530> thing<00:31:29.940> that<00:31:30.940> was<00:31:31.120> there<00:31:31.360> was<00:31:31.450> not 00:31:32.190 --> 00:31:32.200 align:start position:0% to the same thing that was there was not 00:31:32.200 --> 00:31:34.110 align:start position:0% to the same thing that was there was not really<00:31:32.380> about<00:31:32.440> the<00:31:32.560> VM<00:31:32.890> but<00:31:33.460> other<00:31:33.610> parts<00:31:33.880> of 00:31:34.110 --> 00:31:34.120 align:start position:0% really about the VM but other parts of 00:31:34.120 --> 00:31:37.530 align:start position:0% really about the VM but other parts of the<00:31:34.270> network<00:31:35.160> which<00:31:36.160> may<00:31:36.670> just<00:31:36.910> make<00:31:37.000> sense<00:31:37.300> to 00:31:37.530 --> 00:31:37.540 align:start position:0% the network which may just make sense to 00:31:37.540 --> 00:31:39.150 align:start position:0% the network which may just make sense to do<00:31:37.720> them<00:31:37.900> separately<00:31:38.140> because<00:31:38.620> they're<00:31:39.010> not 00:31:39.150 --> 00:31:39.160 align:start position:0% do them separately because they're not 00:31:39.160 --> 00:31:40.740 align:start position:0% do them separately because they're not that<00:31:39.460> interconnected<00:31:40.120> at<00:31:40.240> least<00:31:40.450> at<00:31:40.630> this 00:31:40.740 --> 00:31:40.750 align:start position:0% that interconnected at least at this 00:31:40.750 --> 00:31:42.660 align:start position:0% that interconnected at least at this level<00:31:40.830> at<00:31:41.830> this<00:31:41.950> stage<00:31:42.190> of<00:31:42.340> where<00:31:42.580> the 00:31:42.660 --> 00:31:42.670 align:start position:0% level at this stage of where the 00:31:42.670 --> 00:31:46.410 align:start position:0% level at this stage of where the discussions<00:31:43.240> are<00:31:43.450> it<00:31:44.410> wasn't<00:31:44.740> the<00:31:45.420> DVM 00:31:46.410 --> 00:31:46.420 align:start position:0% discussions are it wasn't the DVM 00:31:46.420 --> 00:31:48.810 align:start position:0% discussions are it wasn't the DVM execution<00:31:47.020> time<00:31:47.230> which<00:31:47.440> was<00:31:48.190> the<00:31:48.220> bound<00:31:48.550> or 00:31:48.810 --> 00:31:48.820 align:start position:0% execution time which was the bound or 00:31:48.820 --> 00:31:50.280 align:start position:0% execution time which was the bound or the<00:31:48.970> reason<00:31:49.330> we<00:31:49.780> need<00:31:49.900> to<00:31:49.990> make<00:31:50.110> those<00:31:50.230> changes 00:31:50.280 --> 00:31:50.290 align:start position:0% the reason we need to make those changes 00:31:50.290 --> 00:31:52.500 align:start position:0% the reason we need to make those changes so<00:31:50.800> I<00:31:51.160> think<00:31:51.280> we<00:31:51.460> can<00:31:51.580> keep<00:31:51.730> them<00:31:51.910> separate<00:31:52.240> and 00:31:52.500 --> 00:31:52.510 align:start position:0% so I think we can keep them separate and 00:31:52.510 --> 00:31:55.350 align:start position:0% so I think we can keep them separate and therefore<00:31:53.080> Greg<00:31:53.530> kicked<00:31:53.890> off<00:31:54.040> with<00:31:54.640> his<00:31:55.000> idiom 00:31:55.350 --> 00:31:55.360 align:start position:0% therefore Greg kicked off with his idiom 00:31:55.360 --> 00:32:00.030 align:start position:0% therefore Greg kicked off with his idiom one<00:31:55.480> five<00:31:55.720> proposal<00:31:58.230> and<00:31:59.230> if<00:31:59.380> you<00:31:59.710> keep<00:31:59.890> them 00:32:00.030 --> 00:32:00.040 align:start position:0% one five proposal and if you keep them 00:32:00.040 --> 00:32:01.110 align:start position:0% one five proposal and if you keep them separate<00:32:00.340> you<00:32:00.460> can<00:32:00.580> also<00:32:00.670> do<00:32:00.850> them<00:32:01.030> in 00:32:01.110 --> 00:32:01.120 align:start position:0% separate you can also do them in 00:32:01.120 --> 00:32:03.240 align:start position:0% separate you can also do them in parallel<00:32:01.510> and<00:32:01.690> maybe<00:32:02.440> get<00:32:02.770> them<00:32:02.950> in<00:32:03.070> more 00:32:03.240 --> 00:32:03.250 align:start position:0% parallel and maybe get them in more 00:32:03.250 --> 00:32:07.080 align:start position:0% parallel and maybe get them in more quickly<00:32:04.530> but<00:32:05.530> that's<00:32:05.710> just<00:32:05.830> my<00:32:06.010> addition<00:32:07.000> to 00:32:07.080 --> 00:32:07.090 align:start position:0% quickly but that's just my addition to 00:32:07.090 --> 00:32:11.010 align:start position:0% quickly but that's just my addition to it<00:32:07.180> maybe<00:32:07.300> Casey<00:32:07.600> you<00:32:07.780> wanna<00:32:08.850> secure<00:32:09.850> I<00:32:10.180> have<00:32:10.990> a 00:32:11.010 --> 00:32:11.020 align:start position:0% it maybe Casey you wanna secure I have a 00:32:11.020 --> 00:32:12.120 align:start position:0% it maybe Casey you wanna secure I have a comment<00:32:11.410> actually<00:32:11.680> about<00:32:11.770> why<00:32:11.950> it's 00:32:12.120 --> 00:32:12.130 align:start position:0% comment actually about why it's 00:32:12.130 --> 00:32:14.880 align:start position:0% comment actually about why it's difficult<00:32:12.550> to<00:32:12.670> update<00:32:13.030> the<00:32:13.990> EVM<00:32:14.440> and<00:32:14.650> I<00:32:14.680> think 00:32:14.880 --> 00:32:14.890 align:start position:0% difficult to update the EVM and I think 00:32:14.890 --> 00:32:17.580 align:start position:0% difficult to update the EVM and I think it's<00:32:15.010> actually<00:32:15.280> just<00:32:15.430> because<00:32:15.730> it's<00:32:16.350> well<00:32:17.350> you 00:32:17.580 --> 00:32:17.590 align:start position:0% it's actually just because it's well you 00:32:17.590 --> 00:32:19.080 align:start position:0% it's actually just because it's well you start<00:32:17.830> with<00:32:17.890> something<00:32:18.280> that's<00:32:18.430> EVM<00:32:18.790> which<00:32:18.970> is 00:32:19.080 --> 00:32:19.090 align:start position:0% start with something that's EVM which is 00:32:19.090 --> 00:32:21.930 align:start position:0% start with something that's EVM which is kind<00:32:19.300> of<00:32:19.360> designed<00:32:19.740> you<00:32:20.740> know<00:32:20.770> ad<00:32:21.220> hoc<00:32:21.700> ish 00:32:21.930 --> 00:32:21.940 align:start position:0% kind of designed you know ad hoc ish 00:32:21.940 --> 00:32:23.850 align:start position:0% kind of designed you know ad hoc ish it's<00:32:22.150> it's<00:32:22.450> it<00:32:22.930> wasn't<00:32:23.320> like<00:32:23.470> someone<00:32:23.770> they 00:32:23.850 --> 00:32:23.860 align:start position:0% it's it's it wasn't like someone they 00:32:23.860 --> 00:32:25.500 align:start position:0% it's it's it wasn't like someone they took<00:32:24.010> some<00:32:24.250> existing<00:32:24.490> VM<00:32:24.910> and<00:32:25.090> then<00:32:25.210> made<00:32:25.480> it 00:32:25.500 --> 00:32:25.510 align:start position:0% took some existing VM and then made it 00:32:25.510 --> 00:32:28.140 align:start position:0% took some existing VM and then made it blockchain<00:32:26.500> capable<00:32:27.400> they<00:32:27.550> you<00:32:27.850> know<00:32:27.970> it<00:32:28.030> was 00:32:28.140 --> 00:32:28.150 align:start position:0% blockchain capable they you know it was 00:32:28.150 --> 00:32:29.830 align:start position:0% blockchain capable they you know it was just<00:32:28.240> designed<00:32:28.540> from<00:32:28.750> the<00:32:28.900> start 00:32:29.830 --> 00:32:29.840 align:start position:0% just designed from the start 00:32:29.840 --> 00:32:31.870 align:start position:0% just designed from the start and<00:32:30.110> then<00:32:30.680> as<00:32:30.830> the<00:32:30.950> hard<00:32:31.130> fork<00:32:31.370> started<00:32:31.730> piling 00:32:31.870 --> 00:32:31.880 align:start position:0% and then as the hard fork started piling 00:32:31.880 --> 00:32:34.180 align:start position:0% and then as the hard fork started piling on<00:32:32.290> logic<00:32:33.290> behind<00:32:33.440> various<00:32:33.800> different<00:32:34.100> parts 00:32:34.180 --> 00:32:34.190 align:start position:0% on logic behind various different parts 00:32:34.190 --> 00:32:36.490 align:start position:0% on logic behind various different parts the<00:32:34.340> VM<00:32:34.550> got<00:32:34.760> more<00:32:34.970> complicated<00:32:35.600> so<00:32:36.260> the 00:32:36.490 --> 00:32:36.500 align:start position:0% the VM got more complicated so the 00:32:36.500 --> 00:32:40.240 align:start position:0% the VM got more complicated so the recent<00:32:37.010> constantinople<00:32:37.850> hard<00:32:38.660> fork<00:32:39.250> the 00:32:40.240 --> 00:32:40.250 align:start position:0% recent constantinople hard fork the 00:32:40.250 --> 00:32:45.070 align:start position:0% recent constantinople hard fork the rules<00:32:40.520> for<00:32:40.880> storage<00:32:41.630> allocation<00:32:42.340> just<00:32:43.340> i<00:32:44.080> mean 00:32:45.070 --> 00:32:45.080 align:start position:0% rules for storage allocation just i mean 00:32:45.080 --> 00:32:47.380 align:start position:0% rules for storage allocation just i mean it<00:32:45.620> like<00:32:45.920> literally<00:32:46.310> tripled<00:32:46.760> it<00:32:46.880> tripled<00:32:47.270> in 00:32:47.380 --> 00:32:47.390 align:start position:0% it like literally tripled it tripled in 00:32:47.390 --> 00:32:49.060 align:start position:0% it like literally tripled it tripled in length<00:32:47.630> how<00:32:47.840> many<00:32:48.050> different<00:32:48.440> cases<00:32:48.590> we<00:32:48.920> have 00:32:49.060 --> 00:32:49.070 align:start position:0% length how many different cases we have 00:32:49.070 --> 00:32:50.140 align:start position:0% length how many different cases we have to<00:32:49.160> handle<00:32:49.490> and<00:32:49.700> it's<00:32:49.820> like<00:32:49.970> different 00:32:50.140 --> 00:32:50.150 align:start position:0% to handle and it's like different 00:32:50.150 --> 00:32:51.640 align:start position:0% to handle and it's like different depending<00:32:50.660> on<00:32:50.690> which<00:32:50.840> pork<00:32:51.170> you're<00:32:51.320> on<00:32:51.440> and 00:32:51.640 --> 00:32:51.650 align:start position:0% depending on which pork you're on and 00:32:51.650 --> 00:32:54.070 align:start position:0% depending on which pork you're on and it's<00:32:51.770> it's<00:32:52.430> a<00:32:52.550> major<00:32:52.730> pain<00:32:53.000> so<00:32:53.210> i<00:32:53.240> think<00:32:53.510> part 00:32:54.070 --> 00:32:54.080 align:start position:0% it's it's a major pain so i think part 00:32:54.080 --> 00:32:55.510 align:start position:0% it's it's a major pain so i think part of<00:32:54.140> the<00:32:54.230> problem<00:32:54.320> with<00:32:54.620> evolving<00:32:54.830> the<00:32:55.040> EBM<00:32:55.400> is 00:32:55.510 --> 00:32:55.520 align:start position:0% of the problem with evolving the EBM is 00:32:55.520 --> 00:32:56.620 align:start position:0% of the problem with evolving the EBM is kind<00:32:55.730> of<00:32:55.790> maintaining<00:32:56.180> backwards 00:32:56.620 --> 00:32:56.630 align:start position:0% kind of maintaining backwards 00:32:56.630 --> 00:32:59.410 align:start position:0% kind of maintaining backwards compatibility<00:32:57.110> so<00:32:57.920> having<00:32:58.160> the<00:32:59.030> ability<00:32:59.060> to 00:32:59.410 --> 00:32:59.420 align:start position:0% compatibility so having the ability to 00:32:59.420 --> 00:33:01.720 align:start position:0% compatibility so having the ability to support<00:32:59.990> the<00:33:00.140> new<00:33:00.260> e<00:33:00.290> vm<00:33:00.620> execution<00:33:01.190> model<00:33:01.520> and 00:33:01.720 --> 00:33:01.730 align:start position:0% support the new e vm execution model and 00:33:01.730 --> 00:33:03.460 align:start position:0% support the new e vm execution model and the<00:33:02.150> old<00:33:02.270> e<00:33:02.390> vm<00:33:02.600> execution<00:33:03.050> model<00:33:03.170> is<00:33:03.320> just 00:33:03.460 --> 00:33:03.470 align:start position:0% the old e vm execution model is just 00:33:03.470 --> 00:33:04.780 align:start position:0% the old e vm execution model is just going<00:33:03.620> to<00:33:03.710> complicate<00:33:04.070> the<00:33:04.280> clients<00:33:04.640> to<00:33:04.700> the 00:33:04.780 --> 00:33:04.790 align:start position:0% going to complicate the clients to the 00:33:04.790 --> 00:33:06.100 align:start position:0% going to complicate the clients to the point<00:33:05.000> where<00:33:05.120> working<00:33:05.360> on<00:33:05.630> them<00:33:05.840> to<00:33:05.960> update 00:33:06.100 --> 00:33:06.110 align:start position:0% point where working on them to update 00:33:06.110 --> 00:33:08.230 align:start position:0% point where working on them to update them<00:33:06.530> for<00:33:06.770> future<00:33:07.490> hard<00:33:07.730> Forks<00:33:07.970> is<00:33:08.060> getting 00:33:08.230 --> 00:33:08.240 align:start position:0% them for future hard Forks is getting 00:33:08.240 --> 00:33:11.380 align:start position:0% them for future hard Forks is getting more<00:33:08.870> difficult<00:33:09.080> over<00:33:09.440> time<00:33:09.710> so<00:33:10.490> i<00:33:10.850> think<00:33:11.030> that 00:33:11.380 --> 00:33:11.390 align:start position:0% more difficult over time so i think that 00:33:11.390 --> 00:33:13.560 align:start position:0% more difficult over time so i think that could<00:33:11.600> be<00:33:11.630> a<00:33:11.750> major<00:33:11.960> barrier<00:33:12.230> as<00:33:12.470> well 00:33:13.560 --> 00:33:13.570 align:start position:0% could be a major barrier as well 00:33:13.570 --> 00:33:15.760 align:start position:0% could be a major barrier as well basically<00:33:14.570> the<00:33:14.840> backwards<00:33:15.350> compatibility 00:33:15.760 --> 00:33:15.770 align:start position:0% basically the backwards compatibility 00:33:15.770 --> 00:33:20.650 align:start position:0% basically the backwards compatibility issue<00:33:16.660> cannot<00:33:17.660> be<00:33:17.810> avoided<00:33:18.080> at<00:33:18.650> all<00:33:19.360> you<00:33:20.360> move 00:33:20.650 --> 00:33:20.660 align:start position:0% issue cannot be avoided at all you move 00:33:20.660 --> 00:33:22.780 align:start position:0% issue cannot be avoided at all you move D<00:33:20.840> you<00:33:20.960> azzam<00:33:21.380> that<00:33:21.560> we<00:33:21.680> still<00:33:21.980> got<00:33:22.190> all<00:33:22.490> these 00:33:22.780 --> 00:33:22.790 align:start position:0% D you azzam that we still got all these 00:33:22.790 --> 00:33:26.590 align:start position:0% D you azzam that we still got all these weird<00:33:23.260> all<00:33:24.260> this<00:33:24.530> weird<00:33:24.800> stuff<00:33:24.950> it<00:33:25.910> gets<00:33:26.300> moved 00:33:26.590 --> 00:33:26.600 align:start position:0% weird all this weird stuff it gets moved 00:33:26.600 --> 00:33:29.230 align:start position:0% weird all this weird stuff it gets moved up<00:33:26.870> to<00:33:27.050> your<00:33:27.170> environment<00:33:27.800> interface<00:33:28.240> and 00:33:29.230 --> 00:33:29.240 align:start position:0% up to your environment interface and 00:33:29.240 --> 00:33:32.290 align:start position:0% up to your environment interface and even<00:33:29.630> with<00:33:29.810> the<00:33:29.930> current<00:33:30.910> even<00:33:31.910> with<00:33:32.030> the<00:33:32.120> old 00:33:32.290 --> 00:33:32.300 align:start position:0% even with the current even with the old 00:33:32.300 --> 00:33:35.110 align:start position:0% even with the current even with the old VM<00:33:32.690> I<00:33:32.720> would<00:33:33.140> love<00:33:33.410> to<00:33:33.860> take<00:33:34.100> a<00:33:34.430> whole<00:33:34.880> lot<00:33:35.090> of 00:33:35.110 --> 00:33:35.120 align:start position:0% VM I would love to take a whole lot of 00:33:35.120 --> 00:33:37.840 align:start position:0% VM I would love to take a whole lot of those<00:33:35.420> op<00:33:35.630> codes<00:33:35.990> it's<00:33:36.290> really<00:33:36.680> art<00:33:36.890> they 00:33:37.840 --> 00:33:37.850 align:start position:0% those op codes it's really art they 00:33:37.850 --> 00:33:39.370 align:start position:0% those op codes it's really art they really<00:33:38.180> have<00:33:38.300> nothing<00:33:38.480> to<00:33:38.720> do<00:33:39.020> with<00:33:39.050> the 00:33:39.370 --> 00:33:39.380 align:start position:0% really have nothing to do with the 00:33:39.380 --> 00:33:42.850 align:start position:0% really have nothing to do with the virtual<00:33:39.770> machine<00:33:40.900> and<00:33:41.900> I<00:33:42.020> could<00:33:42.230> easily<00:33:42.380> as 00:33:42.850 --> 00:33:42.860 align:start position:0% virtual machine and I could easily as 00:33:42.860 --> 00:33:45.820 align:start position:0% virtual machine and I could easily as you<00:33:43.490> have<00:33:43.580> with<00:33:43.790> machine<00:33:44.120> goes<00:33:44.390> say<00:33:44.990> okay 00:33:45.820 --> 00:33:45.830 align:start position:0% you have with machine goes say okay 00:33:45.830 --> 00:33:48.790 align:start position:0% you have with machine goes say okay let's<00:33:46.550> pull<00:33:46.790> all<00:33:46.820> of<00:33:47.150> that<00:33:47.330> out<00:33:47.840> of<00:33:47.900> the<00:33:48.290> VM 00:33:48.790 --> 00:33:48.800 align:start position:0% let's pull all of that out of the VM 00:33:48.800 --> 00:33:51.580 align:start position:0% let's pull all of that out of the VM deprecated<00:33:49.610> it<00:33:49.820> and<00:33:50.050> move<00:33:51.050> it<00:33:51.200> up<00:33:51.350> to<00:33:51.410> the 00:33:51.580 --> 00:33:51.590 align:start position:0% deprecated it and move it up to the 00:33:51.590 --> 00:33:56.620 align:start position:0% deprecated it and move it up to the environment<00:33:52.280> interface<00:33:52.720> you<00:33:53.720> know<00:33:55.090> again<00:33:56.090> the 00:33:56.620 --> 00:33:56.630 align:start position:0% environment interface you know again the 00:33:56.630 --> 00:33:59.080 align:start position:0% environment interface you know again the functionality<00:33:57.350> is<00:33:57.410> there<00:33:57.650> we've<00:33:58.280> got<00:33:58.310> a<00:33:58.490> we've 00:33:59.080 --> 00:33:59.090 align:start position:0% functionality is there we've got a we've 00:33:59.090 --> 00:34:04.360 align:start position:0% functionality is there we've got a we've got<00:33:59.120> a<00:33:59.270> deal<00:33:59.510> with<00:33:59.720> it<00:34:01.330> one<00:34:02.330> note<00:34:02.660> on<00:34:03.280> on<00:34:04.280> the 00:34:04.360 --> 00:34:04.370 align:start position:0% got a deal with it one note on on the 00:34:04.370 --> 00:34:06.010 align:start position:0% got a deal with it one note on on the backwards<00:34:04.640> compatibility<00:34:04.700> and<00:34:05.450> medium 00:34:06.010 --> 00:34:06.020 align:start position:0% backwards compatibility and medium 00:34:06.020 --> 00:34:08.800 align:start position:0% backwards compatibility and medium itself<00:34:06.350> and<00:34:06.740> that<00:34:07.670> promise<00:34:08.300> actually<00:34:08.690> was 00:34:08.800 --> 00:34:08.810 align:start position:0% itself and that promise actually was 00:34:08.810 --> 00:34:11.320 align:start position:0% itself and that promise actually was broken<00:34:09.350> I<00:34:09.530> believe<00:34:10.040> it<00:34:10.370> spurious<00:34:10.820> dragon<00:34:11.180> or 00:34:11.320 --> 00:34:11.330 align:start position:0% broken I believe it spurious dragon or 00:34:11.330 --> 00:34:12.820 align:start position:0% broken I believe it spurious dragon or tendering<00:34:11.840> this<00:34:11.960> or<00:34:12.110> whatever<00:34:12.380> the<00:34:12.500> coding 00:34:12.820 --> 00:34:12.830 align:start position:0% tendering this or whatever the coding 00:34:12.830 --> 00:34:16.990 align:start position:0% tendering this or whatever the coding was<00:34:13.420> back<00:34:14.420> like<00:34:14.600> two<00:34:14.720> years<00:34:14.900> ago<00:34:14.980> where<00:34:16.000> cost 00:34:16.990 --> 00:34:17.000 align:start position:0% was back like two years ago where cost 00:34:17.000 --> 00:34:20.430 align:start position:0% was back like two years ago where cost gaskets<00:34:17.540> were<00:34:17.630> increased<00:34:18.380> and<00:34:18.920> before<00:34:19.730> that<00:34:19.760> I 00:34:20.430 --> 00:34:20.440 align:start position:0% gaskets were increased and before that I 00:34:20.440 --> 00:34:23.110 align:start position:0% gaskets were increased and before that I think<00:34:21.440> it<00:34:21.530> was<00:34:21.800> never<00:34:21.980> explicitly<00:34:22.400> said<00:34:22.940> that 00:34:23.110 --> 00:34:23.120 align:start position:0% think it was never explicitly said that 00:34:23.120 --> 00:34:25.420 align:start position:0% think it was never explicitly said that gas<00:34:23.300> cost<00:34:23.690> cannot<00:34:24.290> be<00:34:24.410> increased<00:34:24.620> but<00:34:25.100> a<00:34:25.130> lot 00:34:25.420 --> 00:34:25.430 align:start position:0% gas cost cannot be increased but a lot 00:34:25.430 --> 00:34:27.400 align:start position:0% gas cost cannot be increased but a lot of<00:34:25.520> contracts<00:34:25.910> assume<00:34:26.180> that<00:34:26.360> and<00:34:26.570> once<00:34:27.290> you 00:34:27.400 --> 00:34:27.410 align:start position:0% of contracts assume that and once you 00:34:27.410 --> 00:34:28.870 align:start position:0% of contracts assume that and once you increase<00:34:27.800> the<00:34:28.010> gas<00:34:28.160> costs<00:34:28.520> so<00:34:28.610> one<00:34:28.730> example 00:34:28.870 --> 00:34:28.880 align:start position:0% increase the gas costs so one example 00:34:28.880 --> 00:34:30.430 align:start position:0% increase the gas costs so one example when<00:34:29.510> a<00:34:29.570> contract<00:34:29.900> makes<00:34:30.050> a<00:34:30.140> call<00:34:30.290> to<00:34:30.380> another 00:34:30.430 --> 00:34:30.440 align:start position:0% when a contract makes a call to another 00:34:30.440 --> 00:34:32.170 align:start position:0% when a contract makes a call to another contract<00:34:31.040> previously<00:34:31.640> they<00:34:31.850> made<00:34:32.000> like<00:34:32.150> a 00:34:32.170 --> 00:34:32.180 align:start position:0% contract previously they made like a 00:34:32.180 --> 00:34:33.550 align:start position:0% contract previously they made like a fixed<00:34:32.510> calculation<00:34:32.990> in<00:34:33.080> the<00:34:33.140> contract<00:34:33.470> in 00:34:33.550 --> 00:34:33.560 align:start position:0% fixed calculation in the contract in 00:34:33.560 --> 00:34:35.350 align:start position:0% fixed calculation in the contract in many<00:34:33.710> cases<00:34:34.130> and<00:34:34.340> once<00:34:34.850> you<00:34:34.970> pumped<00:34:35.210> up<00:34:35.300> the 00:34:35.350 --> 00:34:35.360 align:start position:0% many cases and once you pumped up the 00:34:35.360 --> 00:34:37.600 align:start position:0% many cases and once you pumped up the cost<00:34:35.660> in<00:34:35.960> in<00:34:36.410> some<00:34:36.620> cases<00:34:36.650> they<00:34:37.190> they<00:34:37.580> just 00:34:37.600 --> 00:34:37.610 align:start position:0% cost in in some cases they they just 00:34:37.610 --> 00:34:40.450 align:start position:0% cost in in some cases they they just failed<00:34:38.060> I<00:34:38.270> try<00:34:38.570> them<00:34:38.780> they<00:34:39.020> were<00:34:39.080> done<00:34:39.340> so<00:34:40.340> we 00:34:40.450 --> 00:34:40.460 align:start position:0% failed I try them they were done so we 00:34:40.460 --> 00:34:42.330 align:start position:0% failed I try them they were done so we broke<00:34:40.790> they're<00:34:41.150> backwards<00:34:41.600> compatibility 00:34:42.330 --> 00:34:42.340 align:start position:0% broke they're backwards compatibility 00:34:42.340 --> 00:34:43.930 align:start position:0% broke they're backwards compatibility promise 00:34:43.930 --> 00:34:43.940 align:start position:0% promise 00:34:43.940 --> 00:34:46.329 align:start position:0% promise and<00:34:44.539> but<00:34:44.720> all<00:34:44.809> the<00:34:44.929> proposal<00:34:45.470> since<00:34:45.649> then<00:34:45.889> just 00:34:46.329 --> 00:34:46.339 align:start position:0% and but all the proposal since then just 00:34:46.339 --> 00:34:48.460 align:start position:0% and but all the proposal since then just reduce<00:34:46.700> the<00:34:46.879> costs<00:34:47.270> so<00:34:47.750> like<00:34:47.899> this<00:34:48.020> s<00:34:48.200> toward 00:34:48.460 --> 00:34:48.470 align:start position:0% reduce the costs so like this s toward 00:34:48.470 --> 00:34:50.169 align:start position:0% reduce the costs so like this s toward change<00:34:48.829> you<00:34:49.039> mentioned<00:34:49.549> that<00:34:49.669> reduce<00:34:50.030> the 00:34:50.169 --> 00:34:50.179 align:start position:0% change you mentioned that reduce the 00:34:50.179 --> 00:34:53.379 align:start position:0% change you mentioned that reduce the cost<00:34:50.859> but<00:34:51.859> I<00:34:51.919> think<00:34:52.250> because<00:34:52.460> we<00:34:52.579> broke<00:34:53.210> that 00:34:53.379 --> 00:34:53.389 align:start position:0% cost but I think because we broke that 00:34:53.389 --> 00:34:56.020 align:start position:0% cost but I think because we broke that promise<00:34:53.539> and<00:34:54.020> a<00:34:54.379> lot<00:34:54.829> of<00:34:54.859> the<00:34:55.129> okay<00:34:55.789> the<00:34:55.879> two 00:34:56.020 --> 00:34:56.030 align:start position:0% promise and a lot of the okay the two 00:34:56.030 --> 00:34:58.690 align:start position:0% promise and a lot of the okay the two languages<00:34:56.329> don't<00:34:57.139> they<00:34:58.099> take<00:34:58.339> that<00:34:58.520> into 00:34:58.690 --> 00:34:58.700 align:start position:0% languages don't they take that into 00:34:58.700 --> 00:35:01.150 align:start position:0% languages don't they take that into consideration<00:34:58.760> I<00:34:59.740> think<00:35:00.740> it<00:35:00.920> would<00:35:01.069> be 00:35:01.150 --> 00:35:01.160 align:start position:0% consideration I think it would be 00:35:01.160 --> 00:35:04.089 align:start position:0% consideration I think it would be possible<00:35:01.369> to<00:35:01.789> do<00:35:02.210> like<00:35:02.450> a<00:35:02.480> cleanup<00:35:02.930> of<00:35:03.140> the<00:35:03.770> gas 00:35:04.089 --> 00:35:04.099 align:start position:0% possible to do like a cleanup of the gas 00:35:04.099 --> 00:35:08.200 align:start position:0% possible to do like a cleanup of the gas gas<00:35:04.730> rules<00:35:05.859> in<00:35:06.859> in<00:35:07.579> some<00:35:07.760> cases<00:35:07.940> may 00:35:08.200 --> 00:35:08.210 align:start position:0% gas rules in in some cases may 00:35:08.210 --> 00:35:10.000 align:start position:0% gas rules in in some cases may definitely<00:35:08.809> result<00:35:08.960> in<00:35:09.260> increased<00:35:09.680> costs<00:35:09.980> for 00:35:10.000 --> 00:35:10.010 align:start position:0% definitely result in increased costs for 00:35:10.010 --> 00:35:12.700 align:start position:0% definitely result in increased costs for a<00:35:10.099> given<00:35:10.309> contract<00:35:10.700> or<00:35:10.880> a<00:35:10.910> decreased<00:35:11.359> cost<00:35:11.710> but 00:35:12.700 --> 00:35:12.710 align:start position:0% a given contract or a decreased cost but 00:35:12.710 --> 00:35:15.490 align:start position:0% a given contract or a decreased cost but it<00:35:12.859> shouldn't<00:35:13.190> break<00:35:13.910> contracts<00:35:14.809> entirely 00:35:15.490 --> 00:35:15.500 align:start position:0% it shouldn't break contracts entirely 00:35:15.500 --> 00:35:19.539 align:start position:0% it shouldn't break contracts entirely but<00:35:16.190> it<00:35:16.339> is<00:35:16.579> a<00:35:17.049> say<00:35:18.049> a<00:35:18.079> political<00:35:18.740> question<00:35:19.039> at 00:35:19.539 --> 00:35:19.549 align:start position:0% but it is a say a political question at 00:35:19.549 --> 00:35:22.299 align:start position:0% but it is a say a political question at that<00:35:19.700> point<00:35:19.970> if<00:35:20.240> if<00:35:20.510> a<00:35:20.630> contract<00:35:21.109> is<00:35:21.349> increased 00:35:22.299 --> 00:35:22.309 align:start position:0% that point if if a contract is increased 00:35:22.309 --> 00:35:25.089 align:start position:0% that point if if a contract is increased so<00:35:22.430> much<00:35:22.549> in<00:35:22.849> cost<00:35:23.440> that<00:35:24.440> it<00:35:24.589> kind<00:35:24.770> of<00:35:24.859> breaks 00:35:25.089 --> 00:35:25.099 align:start position:0% so much in cost that it kind of breaks 00:35:25.099 --> 00:35:26.890 align:start position:0% so much in cost that it kind of breaks there<00:35:25.339> the<00:35:25.460> user<00:35:25.609> experience<00:35:25.970> and<00:35:26.599> you<00:35:26.869> know 00:35:26.890 --> 00:35:26.900 align:start position:0% there the user experience and you know 00:35:26.900 --> 00:35:31.539 align:start position:0% there the user experience and you know it's<00:35:27.079> an<00:35:27.170> important<00:35:27.530> country<00:35:30.369> even<00:35:31.369> if<00:35:31.460> we 00:35:31.539 --> 00:35:31.549 align:start position:0% it's an important country even if we 00:35:31.549 --> 00:35:33.309 align:start position:0% it's an important country even if we just<00:35:31.760> ignore<00:35:32.059> the<00:35:32.270> complexity<00:35:32.990> of<00:35:33.020> the<00:35:33.140> gas 00:35:33.309 --> 00:35:33.319 align:start position:0% just ignore the complexity of the gas 00:35:33.319 --> 00:35:36.039 align:start position:0% just ignore the complexity of the gas model<00:35:33.619> which<00:35:33.890> is<00:35:34.359> arguably<00:35:35.359> where<00:35:35.780> a<00:35:35.809> lot<00:35:36.020> of 00:35:36.039 --> 00:35:36.049 align:start position:0% model which is arguably where a lot of 00:35:36.049 --> 00:35:38.049 align:start position:0% model which is arguably where a lot of the<00:35:36.200> complexity<00:35:36.770> in<00:35:36.859> this<00:35:37.339> happens<00:35:37.760> there's 00:35:38.049 --> 00:35:38.059 align:start position:0% the complexity in this happens there's 00:35:38.059 --> 00:35:39.160 align:start position:0% the complexity in this happens there's still<00:35:38.299> complexly<00:35:38.660> if<00:35:38.750> we<00:35:38.839> want<00:35:38.990> to<00:35:39.049> say 00:35:39.160 --> 00:35:39.170 align:start position:0% still complexly if we want to say 00:35:39.170 --> 00:35:40.720 align:start position:0% still complexly if we want to say deprecated<00:35:39.650> old<00:35:39.799> off<00:35:39.950> codes<00:35:40.250> or<00:35:40.430> something 00:35:40.720 --> 00:35:40.730 align:start position:0% deprecated old off codes or something 00:35:40.730 --> 00:35:42.789 align:start position:0% deprecated old off codes or something like<00:35:40.819> that<00:35:40.880> and<00:35:41.329> at<00:35:42.079> that<00:35:42.140> point<00:35:42.470> what<00:35:42.650> do<00:35:42.740> you 00:35:42.789 --> 00:35:42.799 align:start position:0% like that and at that point what do you 00:35:42.799 --> 00:35:45.160 align:start position:0% like that and at that point what do you tell<00:35:43.010> the<00:35:43.190> owners<00:35:43.490> of<00:35:43.520> contracts<00:35:44.059> who<00:35:44.270> you 00:35:45.160 --> 00:35:45.170 align:start position:0% tell the owners of contracts who you 00:35:45.170 --> 00:35:47.410 align:start position:0% tell the owners of contracts who you know<00:35:45.260> use<00:35:45.470> those<00:35:45.680> op<00:35:45.829> codes<00:35:46.130> if<00:35:46.400> you<00:35:46.880> want<00:35:47.329> to 00:35:47.410 --> 00:35:47.420 align:start position:0% know use those op codes if you want to 00:35:47.420 --> 00:35:48.789 align:start position:0% know use those op codes if you want to deprecate<00:35:47.569> it<00:35:47.930> and<00:35:48.020> say<00:35:48.109> you<00:35:48.170> know<00:35:48.410> we<00:35:48.559> want<00:35:48.589> to 00:35:48.789 --> 00:35:48.799 align:start position:0% deprecate it and say you know we want to 00:35:48.799 --> 00:35:50.559 align:start position:0% deprecate it and say you know we want to remove<00:35:49.369> this<00:35:49.609> that<00:35:49.849> we<00:35:49.910> can<00:35:50.029> start<00:35:50.240> to<00:35:50.359> evolve 00:35:50.559 --> 00:35:50.569 align:start position:0% remove this that we can start to evolve 00:35:50.569 --> 00:35:52.240 align:start position:0% remove this that we can start to evolve it<00:35:50.779> to<00:35:50.900> something<00:35:51.109> that's<00:35:51.230> a<00:35:51.410> little<00:35:51.470> saner<00:35:51.890> or 00:35:52.240 --> 00:35:52.250 align:start position:0% it to something that's a little saner or 00:35:52.250 --> 00:35:55.059 align:start position:0% it to something that's a little saner or or<00:35:52.579> a<00:35:52.609> little<00:35:53.029> more<00:35:53.059> modular<00:35:53.630> or<00:35:53.960> is<00:35:54.829> more 00:35:55.059 --> 00:35:55.069 align:start position:0% or a little more modular or is more 00:35:55.069 --> 00:35:57.539 align:start position:0% or a little more modular or is more compatible<00:35:55.849> with<00:35:56.150> other<00:35:56.299> VMs<00:35:56.569> who<00:35:56.930> knows<00:35:57.109> but 00:35:57.539 --> 00:35:57.549 align:start position:0% compatible with other VMs who knows but 00:35:57.549 --> 00:36:00.819 align:start position:0% compatible with other VMs who knows but it<00:35:58.630> there's<00:35:59.630> just<00:35:59.869> there's<00:36:00.349> not<00:36:00.500> something 00:36:00.819 --> 00:36:00.829 align:start position:0% it there's just there's not something 00:36:00.829 --> 00:36:03.670 align:start position:0% it there's just there's not something built<00:36:01.069> into<00:36:01.309> to<00:36:02.299> the<00:36:02.420> system<00:36:02.809> that<00:36:02.990> says<00:36:03.260> you 00:36:03.670 --> 00:36:03.680 align:start position:0% built into to the system that says you 00:36:03.680 --> 00:36:05.319 align:start position:0% built into to the system that says you know<00:36:03.799> we're<00:36:04.190> gonna<00:36:04.339> at<00:36:04.609> some<00:36:04.880> point<00:36:05.119> be<00:36:05.299> able 00:36:05.319 --> 00:36:05.329 align:start position:0% know we're gonna at some point be able 00:36:05.329 --> 00:36:07.450 align:start position:0% know we're gonna at some point be able to<00:36:05.569> say<00:36:05.750> no<00:36:05.779> your<00:36:06.230> contract<00:36:06.710> is<00:36:06.859> no<00:36:07.069> longer 00:36:07.450 --> 00:36:07.460 align:start position:0% to say no your contract is no longer 00:36:07.460 --> 00:36:09.099 align:start position:0% to say no your contract is no longer going<00:36:07.640> to<00:36:07.700> be<00:36:07.760> able<00:36:07.849> to<00:36:08.000> execute<00:36:08.299> on<00:36:08.660> them<00:36:08.839> that 00:36:09.099 --> 00:36:09.109 align:start position:0% going to be able to execute on them that 00:36:09.109 --> 00:36:10.539 align:start position:0% going to be able to execute on them that wasn't<00:36:09.319> what<00:36:09.559> people<00:36:09.589> signed<00:36:10.010> up<00:36:10.130> for<00:36:10.190> when 00:36:10.539 --> 00:36:10.549 align:start position:0% wasn't what people signed up for when 00:36:10.549 --> 00:36:11.950 align:start position:0% wasn't what people signed up for when they<00:36:10.670> signed<00:36:10.880> up<00:36:11.000> for<00:36:11.029> aetherium<00:36:11.450> initially 00:36:11.950 --> 00:36:11.960 align:start position:0% they signed up for aetherium initially 00:36:11.960 --> 00:36:16.779 align:start position:0% they signed up for aetherium initially there's<00:36:13.510> there's<00:36:14.510> this<00:36:14.690> joke<00:36:15.520> that<00:36:16.520> goes 00:36:16.779 --> 00:36:16.789 align:start position:0% there's there's this joke that goes 00:36:16.789 --> 00:36:20.230 align:start position:0% there's there's this joke that goes Intel<00:36:17.720> we<00:36:18.470> put<00:36:18.710> the<00:36:18.829> backwards<00:36:19.430> and<00:36:19.819> backwards 00:36:20.230 --> 00:36:20.240 align:start position:0% Intel we put the backwards and backwards 00:36:20.240 --> 00:36:24.970 align:start position:0% Intel we put the backwards and backwards compatibility<00:36:21.250> and<00:36:23.260> we're<00:36:24.260> stuck<00:36:24.529> with<00:36:24.740> that 00:36:24.970 --> 00:36:24.980 align:start position:0% compatibility and we're stuck with that 00:36:24.980 --> 00:36:27.430 align:start position:0% compatibility and we're stuck with that any<00:36:25.309> contract<00:36:26.089> that<00:36:26.240> works<00:36:26.630> that<00:36:26.990> got<00:36:27.140> put<00:36:27.410> on 00:36:27.430 --> 00:36:27.440 align:start position:0% any contract that works that got put on 00:36:27.440 --> 00:36:30.870 align:start position:0% any contract that works that got put on the<00:36:27.589> chain<00:36:27.980> has<00:36:28.609> to<00:36:28.640> keep<00:36:29.059> working<00:36:29.390> forever 00:36:30.870 --> 00:36:30.880 align:start position:0% the chain has to keep working forever 00:36:30.880 --> 00:36:33.609 align:start position:0% the chain has to keep working forever unless<00:36:31.880> then<00:36:32.180> look<00:36:32.359> well<00:36:32.839> it<00:36:33.109> has<00:36:33.289> to<00:36:33.500> keep 00:36:33.609 --> 00:36:33.619 align:start position:0% unless then look well it has to keep 00:36:33.619 --> 00:36:35.559 align:start position:0% unless then look well it has to keep working<00:36:34.039> forever<00:36:34.220> it<00:36:34.700> has<00:36:34.880> been<00:36:35.240> as<00:36:35.420> an 00:36:35.559 --> 00:36:35.569 align:start position:0% working forever it has been as an 00:36:35.569 --> 00:36:40.930 align:start position:0% working forever it has been as an address<00:36:35.990> they<00:36:36.680> can<00:36:36.710> be<00:36:36.980> called<00:36:39.130> ok<00:36:40.130> can<00:36:40.309> I<00:36:40.400> just 00:36:40.930 --> 00:36:40.940 align:start position:0% address they can be called ok can I just 00:36:40.940 --> 00:36:43.630 align:start position:0% address they can be called ok can I just mention<00:36:41.029> a<00:36:41.299> strange<00:36:41.720> example<00:36:42.020> to<00:36:42.319> this<00:36:42.640> ecole 00:36:43.630 --> 00:36:43.640 align:start position:0% mention a strange example to this ecole 00:36:43.640 --> 00:36:48.609 align:start position:0% mention a strange example to this ecole code<00:36:43.880> of<00:36:44.240> code<00:36:45.190> which<00:36:47.289> which<00:36:48.289> was<00:36:48.470> quickly 00:36:48.609 --> 00:36:48.619 align:start position:0% code of code which which was quickly 00:36:48.619 --> 00:36:50.319 align:start position:0% code of code which which was quickly fixed<00:36:49.039> by<00:36:49.190> introducing<00:36:49.460> a<00:36:49.670> new<00:36:49.789> up<00:36:49.910> code<00:36:50.089> core 00:36:50.319 --> 00:36:50.329 align:start position:0% fixed by introducing a new up code core 00:36:50.329 --> 00:36:52.720 align:start position:0% fixed by introducing a new up code core delegate<00:36:50.630> for<00:36:50.890> just<00:36:51.890> right<00:36:52.069> in<00:36:52.309> two<00:36:52.609> months 00:36:52.720 --> 00:36:52.730 align:start position:0% delegate for just right in two months 00:36:52.730 --> 00:36:55.089 align:start position:0% delegate for just right in two months after<00:36:53.000> launching<00:36:53.450> deuterium<00:36:53.930> because<00:36:54.680> code 00:36:55.089 --> 00:36:55.099 align:start position:0% after launching deuterium because code 00:36:55.099 --> 00:36:56.769 align:start position:0% after launching deuterium because code was<00:36:55.250> supposed<00:36:55.549> to<00:36:55.609> do<00:36:55.760> what<00:36:55.910> delegate<00:36:56.359> call<00:36:56.569> is 00:36:56.769 --> 00:36:56.779 align:start position:0% was supposed to do what delegate call is 00:36:56.779 --> 00:36:57.520 align:start position:0% was supposed to do what delegate call is doing<00:36:57.079> but<00:36:57.230> it<00:36:57.349> was 00:36:57.520 --> 00:36:57.530 align:start position:0% doing but it was 00:36:57.530 --> 00:36:59.290 align:start position:0% doing but it was and<00:36:57.650> you<00:36:58.280> have<00:36:58.400> to<00:36:58.520> still<00:36:58.700> kept<00:36:58.910> it<00:36:59.090> and 00:36:59.290 --> 00:36:59.300 align:start position:0% and you have to still kept it and 00:36:59.300 --> 00:37:02.520 align:start position:0% and you have to still kept it and nothing<00:36:59.780> is<00:36:59.900> using<00:37:00.170> it<00:37:00.790> because<00:37:01.790> it's<00:37:02.060> useless 00:37:02.520 --> 00:37:02.530 align:start position:0% nothing is using it because it's useless 00:37:02.530 --> 00:37:05.830 align:start position:0% nothing is using it because it's useless yet<00:37:03.530> we<00:37:03.770> still<00:37:03.950> have<00:37:04.100> it<00:37:04.190> how<00:37:05.120> can<00:37:05.300> we<00:37:05.450> move<00:37:05.630> it 00:37:05.830 --> 00:37:05.840 align:start position:0% yet we still have it how can we move it 00:37:05.840 --> 00:37:10.660 align:start position:0% yet we still have it how can we move it the<00:37:06.320> best<00:37:06.590> we<00:37:06.800> can<00:37:07.010> do<00:37:07.960> both<00:37:08.960> both<00:37:09.410> the<00:37:09.770> best<00:37:10.430> we 00:37:10.660 --> 00:37:10.670 align:start position:0% the best we can do both both the best we 00:37:10.670 --> 00:37:13.450 align:start position:0% the best we can do both both the best we can<00:37:10.850> do<00:37:11.060> for<00:37:11.360> any<00:37:11.510> VM<00:37:11.960> is<00:37:12.230> when<00:37:12.710> you<00:37:12.830> deprecated 00:37:13.450 --> 00:37:13.460 align:start position:0% can do for any VM is when you deprecated 00:37:13.460 --> 00:37:15.580 align:start position:0% can do for any VM is when you deprecated it<00:37:13.670> is<00:37:14.060> you<00:37:14.840> keep<00:37:15.050> you<00:37:15.200> have<00:37:15.380> to<00:37:15.410> keep 00:37:15.580 --> 00:37:15.590 align:start position:0% it is you keep you have to keep 00:37:15.590 --> 00:37:17.740 align:start position:0% it is you keep you have to keep supporting<00:37:16.340> it<00:37:16.460> null<00:37:16.700> code<00:37:17.060> but<00:37:17.420> if<00:37:17.540> they<00:37:17.690> try 00:37:17.740 --> 00:37:17.750 align:start position:0% supporting it null code but if they try 00:37:17.750 --> 00:37:19.890 align:start position:0% supporting it null code but if they try and<00:37:17.960> put<00:37:18.170> a<00:37:18.380> new<00:37:18.620> contract<00:37:19.220> on<00:37:19.400> the<00:37:19.550> blockchain 00:37:19.890 --> 00:37:19.900 align:start position:0% and put a new contract on the blockchain 00:37:19.900 --> 00:37:23.880 align:start position:0% and put a new contract on the blockchain that<00:37:20.900> uses<00:37:21.410> that<00:37:21.830> uses<00:37:22.040> a<00:37:22.340> deprecated<00:37:23.030> feature 00:37:23.880 --> 00:37:23.890 align:start position:0% that uses that uses a deprecated feature 00:37:23.890 --> 00:37:25.870 align:start position:0% that uses that uses a deprecated feature they<00:37:24.890> can't<00:37:25.160> put<00:37:25.370> it<00:37:25.490> on<00:37:25.550> the<00:37:25.670> blockchain 00:37:25.870 --> 00:37:25.880 align:start position:0% they can't put it on the blockchain 00:37:25.880 --> 00:37:30.340 align:start position:0% they can't put it on the blockchain anymore<00:37:26.630> so<00:37:28.030> yeah<00:37:29.030> deprecating<00:37:29.840> stuff<00:37:30.140> is 00:37:30.340 --> 00:37:30.350 align:start position:0% anymore so yeah deprecating stuff is 00:37:30.350 --> 00:37:33.430 align:start position:0% anymore so yeah deprecating stuff is definitely<00:37:30.950> hard<00:37:31.190> but<00:37:31.910> about<00:37:32.720> Everett's 00:37:33.430 --> 00:37:33.440 align:start position:0% definitely hard but about Everett's 00:37:33.440 --> 00:37:38.230 align:start position:0% definitely hard but about Everett's comment<00:37:33.860> that<00:37:35.770> adding<00:37:36.770> new<00:37:37.190> features<00:37:37.340> or<00:37:37.730> new 00:37:38.230 --> 00:37:38.240 align:start position:0% comment that adding new features or new 00:37:38.240 --> 00:37:39.820 align:start position:0% comment that adding new features or new app<00:37:38.390> pose<00:37:38.630> or<00:37:38.840> changing<00:37:39.200> the<00:37:39.290> way<00:37:39.380> existing 00:37:39.820 --> 00:37:39.830 align:start position:0% app pose or changing the way existing 00:37:39.830 --> 00:37:42.040 align:start position:0% app pose or changing the way existing app<00:37:39.950> codes<00:37:40.220> work<00:37:40.490> increases<00:37:41.360> the<00:37:41.600> complexity 00:37:42.040 --> 00:37:42.050 align:start position:0% app codes work increases the complexity 00:37:42.050 --> 00:37:44.980 align:start position:0% app codes work increases the complexity of<00:37:42.200> the<00:37:42.350> code<00:37:42.530> base<00:37:42.740> because<00:37:43.040> you<00:37:43.250> the<00:37:44.120> code 00:37:44.980 --> 00:37:44.990 align:start position:0% of the code base because you the code 00:37:44.990 --> 00:37:47.290 align:start position:0% of the code base because you the code has<00:37:45.170> to<00:37:45.320> support<00:37:45.650> the<00:37:45.950> you<00:37:46.490> know<00:37:46.610> the<00:37:46.850> old<00:37:47.030> for 00:37:47.290 --> 00:37:47.300 align:start position:0% has to support the you know the old for 00:37:47.300 --> 00:37:49.210 align:start position:0% has to support the you know the old for crawls<00:37:47.600> and<00:37:47.870> then<00:37:47.990> you<00:37:48.290> know<00:37:48.410> next<00:37:48.770> work<00:37:48.980> rules 00:37:49.210 --> 00:37:49.220 align:start position:0% crawls and then you know next work rules 00:37:49.220 --> 00:37:51.280 align:start position:0% crawls and then you know next work rules then<00:37:49.370> the<00:37:49.430> next<00:37:49.670> one<00:37:49.820> and<00:37:50.600> you<00:37:50.660> get<00:37:51.080> all<00:37:51.200> these 00:37:51.280 --> 00:37:51.290 align:start position:0% then the next one and you get all these 00:37:51.290 --> 00:37:56.640 align:start position:0% then the next one and you get all these conditionals<00:37:53.410> all<00:37:54.410> that<00:37:54.770> you<00:37:55.430> can<00:37:55.580> actually 00:37:56.640 --> 00:37:56.650 align:start position:0% conditionals all that you can actually 00:37:56.650 --> 00:38:01.060 align:start position:0% conditionals all that you can actually get<00:37:57.650> rid<00:37:57.800> of<00:37:57.890> that<00:37:58.040> by<00:37:59.350> just<00:38:00.350> only<00:38:00.560> supporting 00:38:01.060 --> 00:38:01.070 align:start position:0% get rid of that by just only supporting 00:38:01.070 --> 00:38:03.820 align:start position:0% get rid of that by just only supporting the<00:38:01.160> new<00:38:01.250> fork<00:38:01.550> rolls<00:38:01.790> and<00:38:02.410> resetting<00:38:03.410> you 00:38:03.820 --> 00:38:03.830 align:start position:0% the new fork rolls and resetting you 00:38:03.830 --> 00:38:05.640 align:start position:0% the new fork rolls and resetting you know<00:38:03.920> essentially<00:38:04.340> like<00:38:04.550> resetting<00:38:04.940> the 00:38:05.640 --> 00:38:05.650 align:start position:0% know essentially like resetting the 00:38:05.650 --> 00:38:09.000 align:start position:0% know essentially like resetting the Genesis<00:38:06.650> block<00:38:06.770> at<00:38:07.130> a<00:38:07.160> more<00:38:07.520> recent<00:38:07.700> snapshot 00:38:09.000 --> 00:38:09.010 align:start position:0% Genesis block at a more recent snapshot 00:38:09.010 --> 00:38:15.340 align:start position:0% Genesis block at a more recent snapshot I'm<00:38:10.010> not<00:38:10.220> sure<00:38:10.430> why<00:38:11.140> so<00:38:12.140> many<00:38:12.290> clients<00:38:12.620> and<00:38:14.350> you 00:38:15.340 --> 00:38:15.350 align:start position:0% I'm not sure why so many clients and you 00:38:15.350 --> 00:38:17.050 align:start position:0% I'm not sure why so many clients and you know<00:38:15.470> users<00:38:16.040> are<00:38:16.220> obsessed<00:38:16.580> with<00:38:16.670> being<00:38:16.970> able 00:38:17.050 --> 00:38:17.060 align:start position:0% know users are obsessed with being able 00:38:17.060 --> 00:38:20.770 align:start position:0% know users are obsessed with being able to<00:38:17.240> process<00:38:17.810> all<00:38:18.230> the<00:38:18.320> way<00:38:18.440> from<00:38:18.740> the<00:38:19.780> Genesis 00:38:20.770 --> 00:38:20.780 align:start position:0% to process all the way from the Genesis 00:38:20.780 --> 00:38:23.170 align:start position:0% to process all the way from the Genesis block<00:38:20.930> and<00:38:21.320> then<00:38:21.920> through<00:38:22.640> all<00:38:22.670> the<00:38:22.940> court 00:38:23.170 --> 00:38:23.180 align:start position:0% block and then through all the court 00:38:23.180 --> 00:38:33.340 align:start position:0% block and then through all the court rules<00:38:23.390> and<00:38:23.630> then<00:38:23.720> currently<00:38:24.590> but<00:38:32.200> what<00:38:33.200> about 00:38:33.340 --> 00:38:33.350 align:start position:0% rules and then currently but what about 00:38:33.350 --> 00:38:34.900 align:start position:0% rules and then currently but what about a<00:38:33.380> contract<00:38:33.860> that<00:38:33.950> has<00:38:34.070> some<00:38:34.220> logic<00:38:34.580> about<00:38:34.790> how 00:38:34.900 --> 00:38:34.910 align:start position:0% a contract that has some logic about how 00:38:34.910 --> 00:38:36.190 align:start position:0% a contract that has some logic about how their<00:38:35.300> funds<00:38:35.510> are<00:38:35.660> supposed<00:38:35.840> to<00:38:35.870> be<00:38:35.960> paid<00:38:36.170> out 00:38:36.190 --> 00:38:36.200 align:start position:0% their funds are supposed to be paid out 00:38:36.200 --> 00:38:37.930 align:start position:0% their funds are supposed to be paid out you<00:38:36.590> reset<00:38:36.950> your<00:38:36.980> Genesis<00:38:37.460> block<00:38:37.610> you 00:38:37.930 --> 00:38:37.940 align:start position:0% you reset your Genesis block you 00:38:37.940 --> 00:38:39.460 align:start position:0% you reset your Genesis block you essentially<00:38:38.210> forget<00:38:38.660> their<00:38:38.870> code<00:38:39.110> structure 00:38:39.460 --> 00:38:39.470 align:start position:0% essentially forget their code structure 00:38:39.470 --> 00:38:41.410 align:start position:0% essentially forget their code structure or<00:38:39.830> something<00:38:40.160> like<00:38:40.250> that<00:38:40.310> and<00:38:40.730> then<00:38:40.880> what 00:38:41.410 --> 00:38:41.420 align:start position:0% or something like that and then what 00:38:41.420 --> 00:38:45.490 align:start position:0% or something like that and then what happens<00:38:41.750> to<00:38:41.900> those<00:38:41.990> funds<00:38:42.200> sitting<00:38:44.470> you<00:38:45.470> know 00:38:45.490 --> 00:38:45.500 align:start position:0% happens to those funds sitting you know 00:38:45.500 --> 00:38:47.230 align:start position:0% happens to those funds sitting you know you<00:38:46.040> start<00:38:46.280> at<00:38:46.340> the<00:38:46.430> snapshot<00:38:46.880> of<00:38:46.910> the<00:38:47.090> current 00:38:47.230 --> 00:38:47.240 align:start position:0% you start at the snapshot of the current 00:38:47.240 --> 00:38:49.270 align:start position:0% you start at the snapshot of the current of<00:38:47.540> a<00:38:47.630> state<00:38:47.900> after<00:38:48.170> the<00:38:48.350> fork<00:38:48.710> right<00:38:48.920> then 00:38:49.270 --> 00:38:49.280 align:start position:0% of a state after the fork right then 00:38:49.280 --> 00:38:51.820 align:start position:0% of a state after the fork right then that<00:38:49.460> client<00:38:49.820> sinks<00:38:50.630> starting<00:38:51.230> from<00:38:51.470> that 00:38:51.820 --> 00:38:51.830 align:start position:0% that client sinks starting from that 00:38:51.830 --> 00:38:54.340 align:start position:0% that client sinks starting from that snapshot<00:38:52.610> and<00:38:52.880> it<00:38:53.480> only<00:38:53.600> has<00:38:53.810> to<00:38:53.960> support<00:38:54.260> the 00:38:54.340 --> 00:38:54.350 align:start position:0% snapshot and it only has to support the 00:38:54.350 --> 00:38:59.680 align:start position:0% snapshot and it only has to support the new<00:38:54.470> fork<00:38:54.740> rules<00:38:57.700> at<00:38:58.700> that<00:38:58.880> point<00:38:59.120> you<00:38:59.210> call<00:38:59.450> in 00:38:59.680 --> 00:38:59.690 align:start position:0% new fork rules at that point you call in 00:38:59.690 --> 00:39:01.240 align:start position:0% new fork rules at that point you call in to<00:38:59.840> a<00:38:59.870> contract<00:39:00.380> that<00:39:00.470> was<00:39:00.590> created<00:39:00.920> before 00:39:01.240 --> 00:39:01.250 align:start position:0% to a contract that was created before 00:39:01.250 --> 00:39:05.080 align:start position:0% to a contract that was created before that<00:39:01.490> on<00:39:01.700> a<00:39:02.420> previous<00:39:02.660> Fork<00:39:03.140> right<00:39:04.010> it's<00:39:04.670> logic 00:39:05.080 --> 00:39:05.090 align:start position:0% that on a previous Fork right it's logic 00:39:05.090 --> 00:39:07.090 align:start position:0% that on a previous Fork right it's logic is<00:39:05.210> broken<00:39:05.600> on<00:39:05.720> the<00:39:05.810> new<00:39:05.930> Fork<00:39:06.230> potentially 00:39:07.090 --> 00:39:07.100 align:start position:0% is broken on the new Fork potentially 00:39:07.100 --> 00:39:09.460 align:start position:0% is broken on the new Fork potentially well<00:39:08.060> so<00:39:08.480> maybe<00:39:08.660> you've<00:39:08.810> locked<00:39:08.990> up<00:39:09.170> someone's 00:39:09.460 --> 00:39:09.470 align:start position:0% well so maybe you've locked up someone's 00:39:09.470 --> 00:39:12.360 align:start position:0% well so maybe you've locked up someone's funds<00:39:09.710> or 00:39:12.360 --> 00:39:12.370 align:start position:0% 00:39:12.370 --> 00:39:14.350 align:start position:0% yeah<00:39:13.370> so<00:39:13.670> I<00:39:13.730> said<00:39:13.910> you<00:39:13.970> can't 00:39:14.350 --> 00:39:14.360 align:start position:0% yeah so I said you can't 00:39:14.360 --> 00:39:17.020 align:start position:0% yeah so I said you can't did<00:39:15.110> you<00:39:15.530> really<00:39:15.890> can't<00:39:16.160> deprecated<00:39:16.610> stuff<00:39:16.820> or 00:39:17.020 --> 00:39:17.030 align:start position:0% did you really can't deprecated stuff or 00:39:17.030 --> 00:39:19.150 align:start position:0% did you really can't deprecated stuff or it's<00:39:17.150> really<00:39:17.270> hard<00:39:17.570> to<00:39:17.720> you<00:39:18.140> can<00:39:18.290> only<00:39:18.410> you 00:39:19.150 --> 00:39:19.160 align:start position:0% it's really hard to you can only you 00:39:19.160 --> 00:39:25.480 align:start position:0% it's really hard to you can only you know<00:39:19.250> change<00:39:19.940> things<00:39:21.280> again<00:39:22.600> the<00:39:24.130> the<00:39:25.130> Intel 00:39:25.480 --> 00:39:25.490 align:start position:0% know change things again the the Intel 00:39:25.490 --> 00:39:27.670 align:start position:0% know change things again the the Intel chip<00:39:25.520> started<00:39:26.300> out<00:39:26.450> as<00:39:26.630> a<00:39:26.660> hand<00:39:26.930> calculator 00:39:27.670 --> 00:39:27.680 align:start position:0% chip started out as a hand calculator 00:39:27.680 --> 00:39:31.780 align:start position:0% chip started out as a hand calculator and<00:39:28.330> that<00:39:29.330> code<00:39:29.570> still<00:39:29.930> runs<00:39:30.260> it<00:39:31.220> doesn't<00:39:31.640> run 00:39:31.780 --> 00:39:31.790 align:start position:0% and that code still runs it doesn't run 00:39:31.790 --> 00:39:34.990 align:start position:0% and that code still runs it doesn't run very<00:39:32.030> well<00:39:32.560> that<00:39:33.560> those<00:39:34.190> op<00:39:34.490> codes<00:39:34.790> have 00:39:34.990 --> 00:39:35.000 align:start position:0% very well that those op codes have 00:39:35.000 --> 00:39:36.910 align:start position:0% very well that those op codes have actually<00:39:35.390> become<00:39:35.570> pretty<00:39:36.020> swell<00:39:36.440> and<00:39:36.770> there's 00:39:36.910 --> 00:39:36.920 align:start position:0% actually become pretty swell and there's 00:39:36.920 --> 00:39:38.760 align:start position:0% actually become pretty swell and there's a<00:39:36.980> good<00:39:37.190> reason<00:39:37.250> not<00:39:37.730> to<00:39:37.790> use<00:39:38.120> them<00:39:38.390> anymore 00:39:38.760 --> 00:39:38.770 align:start position:0% a good reason not to use them anymore 00:39:38.770 --> 00:39:42.190 align:start position:0% a good reason not to use them anymore but<00:39:39.770> that<00:39:40.610> hand<00:39:40.910> calculator<00:39:41.570> is<00:39:41.750> still<00:39:41.990> in 00:39:42.190 --> 00:39:42.200 align:start position:0% but that hand calculator is still in 00:39:42.200 --> 00:39:44.860 align:start position:0% but that hand calculator is still in there<00:39:42.500> and<00:39:42.740> to<00:39:43.430> some<00:39:43.670> extent<00:39:44.180> you<00:39:44.600> know<00:39:44.690> we 00:39:44.860 --> 00:39:44.870 align:start position:0% there and to some extent you know we 00:39:44.870 --> 00:39:47.980 align:start position:0% there and to some extent you know we says<00:39:45.140> you're<00:39:45.320> bitching<00:39:45.740> about<00:39:45.890> it<00:39:46.370> and<00:39:46.990> it's 00:39:47.980 --> 00:39:47.990 align:start position:0% says you're bitching about it and it's 00:39:47.990 --> 00:39:51.880 align:start position:0% says you're bitching about it and it's just<00:39:48.290> tough<00:39:49.160> suck<00:39:49.970> it<00:39:50.150> out<00:39:50.270> I<00:39:50.660> want<00:39:51.620> to 00:39:51.880 --> 00:39:51.890 align:start position:0% just tough suck it out I want to 00:39:51.890 --> 00:39:53.170 align:start position:0% just tough suck it out I want to save<00:39:52.190> some<00:39:52.340> time<00:39:52.370> for<00:39:52.520> ID<00:39:52.730> ask<00:39:52.850> questions 00:39:53.170 --> 00:39:53.180 align:start position:0% save some time for ID ask questions 00:39:53.180 --> 00:39:54.730 align:start position:0% save some time for ID ask questions let's<00:39:53.390> speak<00:39:53.690> maybe<00:39:54.020> ten<00:39:54.230> minutes<00:39:54.470> left<00:39:54.590> with 00:39:54.730 --> 00:39:54.740 align:start position:0% let's speak maybe ten minutes left with 00:39:54.740 --> 00:39:55.840 align:start position:0% let's speak maybe ten minutes left with that<00:39:54.830> let's<00:39:55.070> go<00:39:55.130> ahead<00:39:55.220> and<00:39:55.370> do<00:39:55.430> that<00:39:55.490> anyone 00:39:55.840 --> 00:39:55.850 align:start position:0% that let's go ahead and do that anyone 00:39:55.850 --> 00:40:01.420 align:start position:0% that let's go ahead and do that anyone have<00:39:56.000> a<00:39:56.060> question<00:39:56.390> or<00:39:56.600> comment<00:39:57.820> complaint<00:40:00.430> or 00:40:01.420 --> 00:40:01.430 align:start position:0% have a question or comment complaint or 00:40:01.430 --> 00:40:06.400 align:start position:0% have a question or comment complaint or it's<00:40:01.820> always<00:40:02.180> force<00:40:04.780> so<00:40:05.780> one<00:40:05.960> of<00:40:05.990> the<00:40:06.110> things<00:40:06.290> I 00:40:06.400 --> 00:40:06.410 align:start position:0% it's always force so one of the things I 00:40:06.410 --> 00:40:09.700 align:start position:0% it's always force so one of the things I want<00:40:06.590> us<00:40:06.740> to<00:40:07.040> think<00:40:07.250> about<00:40:07.400> is<00:40:08.500> I'm<00:40:09.500> starting 00:40:09.700 --> 00:40:09.710 align:start position:0% want us to think about is I'm starting 00:40:09.710 --> 00:40:11.230 align:start position:0% want us to think about is I'm starting to<00:40:09.890> think<00:40:09.980> about<00:40:10.280> the<00:40:10.400> different<00:40:10.700> components 00:40:11.230 --> 00:40:11.240 align:start position:0% to think about the different components 00:40:11.240 --> 00:40:14.590 align:start position:0% to think about the different components of<00:40:11.420> what<00:40:12.080> is<00:40:12.200> etherium<00:40:13.210> just<00:40:14.210> as<00:40:14.330> we're<00:40:14.480> maybe 00:40:14.590 --> 00:40:14.600 align:start position:0% of what is etherium just as we're maybe 00:40:14.600 --> 00:40:16.450 align:start position:0% of what is etherium just as we're maybe thinking<00:40:14.930> about<00:40:15.110> what<00:40:15.290> is<00:40:15.410> web<00:40:15.560> 3<00:40:15.890> and<00:40:16.160> how 00:40:16.450 --> 00:40:16.460 align:start position:0% thinking about what is web 3 and how 00:40:16.460 --> 00:40:18.160 align:start position:0% thinking about what is web 3 and how much<00:40:16.610> we're<00:40:16.790> integrating<00:40:17.300> and<00:40:17.540> eeap's<00:40:17.930> and 00:40:18.160 --> 00:40:18.170 align:start position:0% much we're integrating and eeap's and 00:40:18.170 --> 00:40:20.350 align:start position:0% much we're integrating and eeap's and other<00:40:18.260> stuff<00:40:18.500> like<00:40:18.650> that<00:40:18.830> with<00:40:19.160> ipfs<00:40:19.880> and<00:40:20.210> so 00:40:20.350 --> 00:40:20.360 align:start position:0% other stuff like that with ipfs and so 00:40:20.360 --> 00:40:24.220 align:start position:0% other stuff like that with ipfs and so on<00:40:20.860> the<00:40:21.860> EVM<00:40:22.540> goes<00:40:23.540> beyond 00:40:24.220 --> 00:40:24.230 align:start position:0% on the EVM goes beyond 00:40:24.230 --> 00:40:26.590 align:start position:0% on the EVM goes beyond etherium<00:40:24.830> public<00:40:25.130> main<00:40:25.310> net<00:40:25.490> so<00:40:26.240> today 00:40:26.590 --> 00:40:26.600 align:start position:0% etherium public main net so today 00:40:26.600 --> 00:40:29.230 align:start position:0% etherium public main net so today Microsoft<00:40:27.500> released<00:40:27.950> released<00:40:28.310> a<00:40:28.580> new<00:40:28.730> EBM 00:40:29.230 --> 00:40:29.240 align:start position:0% Microsoft released released a new EBM 00:40:29.240 --> 00:40:34.330 align:start position:0% Microsoft released released a new EBM the<00:40:30.140> EE<00:40:30.560> BM<00:40:31.480> written<00:40:32.480> in<00:40:32.600> C<00:40:32.920> without<00:40:33.920> gas 00:40:34.330 --> 00:40:34.340 align:start position:0% the EE BM written in C without gas 00:40:34.340 --> 00:40:37.900 align:start position:0% the EE BM written in C without gas calculations<00:40:35.530> that<00:40:36.530> is<00:40:37.100> designed<00:40:37.580> for 00:40:37.900 --> 00:40:37.910 align:start position:0% calculations that is designed for 00:40:37.910 --> 00:40:40.660 align:start position:0% calculations that is designed for private<00:40:38.330> networks<00:40:38.660> so<00:40:39.500> how<00:40:39.710> much<00:40:39.920> from<00:40:40.520> the 00:40:40.660 --> 00:40:40.670 align:start position:0% private networks so how much from the 00:40:40.670 --> 00:40:44.860 align:start position:0% private networks so how much from the perspective<00:40:41.240> of<00:40:41.450> an<00:40:41.870> EVM<00:40:42.970> specification<00:40:43.970> do 00:40:44.860 --> 00:40:44.870 align:start position:0% perspective of an EVM specification do 00:40:44.870 --> 00:40:49.240 align:start position:0% perspective of an EVM specification do we<00:40:45.020> broaden<00:40:46.480> to<00:40:47.530> support<00:40:48.530> and<00:40:48.710> work<00:40:49.010> with 00:40:49.240 --> 00:40:49.250 align:start position:0% we broaden to support and work with 00:40:49.250 --> 00:40:52.300 align:start position:0% we broaden to support and work with other<00:40:49.970> chains<00:40:50.540> like<00:40:50.960> the<00:40:51.350> way<00:40:51.470> I<00:40:51.500> see<00:40:51.830> it<00:40:51.860> we 00:40:52.300 --> 00:40:52.310 align:start position:0% other chains like the way I see it we 00:40:52.310 --> 00:40:55.050 align:start position:0% other chains like the way I see it we might<00:40:52.460> have<00:40:52.700> a<00:40:52.730> very<00:40:53.000> large<00:40:53.330> EVM<00:40:54.200> community 00:40:55.050 --> 00:40:55.060 align:start position:0% might have a very large EVM community 00:40:55.060 --> 00:40:57.880 align:start position:0% might have a very large EVM community that<00:40:56.060> might<00:40:56.270> want<00:40:56.450> to<00:40:56.570> work<00:40:56.750> together<00:40:56.930> and<00:40:57.350> fix 00:40:57.880 --> 00:40:57.890 align:start position:0% that might want to work together and fix 00:40:57.890 --> 00:41:00.760 align:start position:0% that might want to work together and fix some<00:40:58.100> of<00:40:58.190> the<00:40:58.250> resources<00:40:58.640> issue<00:40:58.940> so<00:40:59.870> just<00:41:00.590> some 00:41:00.760 --> 00:41:00.770 align:start position:0% some of the resources issue so just some 00:41:00.770 --> 00:41:02.590 align:start position:0% some of the resources issue so just some some<00:41:01.190> thoughts<00:41:01.400> that<00:41:01.580> I'd<00:41:02.030> love<00:41:02.240> to<00:41:02.270> hear<00:41:02.480> the 00:41:02.590 --> 00:41:02.600 align:start position:0% some thoughts that I'd love to hear the 00:41:02.600 --> 00:41:09.010 align:start position:0% some thoughts that I'd love to hear the panel's<00:41:02.930> ideas<00:41:03.290> on 00:41:09.010 --> 00:41:09.020 align:start position:0% 00:41:09.020 --> 00:41:11.690 align:start position:0% I'd<00:41:10.020> actually<00:41:10.200> like<00:41:10.560> like<00:41:11.160> to<00:41:11.310> ask<00:41:11.430> you<00:41:11.640> a 00:41:11.690 --> 00:41:11.700 align:start position:0% I'd actually like like to ask you a 00:41:11.700 --> 00:41:15.559 align:start position:0% I'd actually like like to ask you a question<00:41:12.480> because<00:41:12.839> you<00:41:14.060> there's<00:41:15.060> nobody<00:41:15.210> else 00:41:15.559 --> 00:41:15.569 align:start position:0% question because you there's nobody else 00:41:15.569 --> 00:41:20.050 align:start position:0% question because you there's nobody else nobody<00:41:16.020> wants<00:41:16.470> to<00:41:16.500> ask 00:41:20.050 --> 00:41:20.060 align:start position:0% 00:41:20.060 --> 00:41:25.339 align:start position:0% yeah<00:41:22.190> can<00:41:23.190> you<00:41:23.220> clarify<00:41:23.520> a<00:41:24.020> second<00:41:25.020> very<00:41:25.200> can 00:41:25.339 --> 00:41:25.349 align:start position:0% yeah can you clarify a second very can 00:41:25.349 --> 00:41:27.559 align:start position:0% yeah can you clarify a second very can you<00:41:25.440> clarify<00:41:25.650> are<00:41:26.310> you<00:41:26.609> asking<00:41:27.089> specifically 00:41:27.559 --> 00:41:27.569 align:start position:0% you clarify are you asking specifically 00:41:27.569 --> 00:41:30.440 align:start position:0% you clarify are you asking specifically about<00:41:28.220> are<00:41:29.220> we<00:41:29.430> going<00:41:29.640> to<00:41:29.760> support<00:41:30.150> the<00:41:30.300> other 00:41:30.440 --> 00:41:30.450 align:start position:0% about are we going to support the other 00:41:30.450 --> 00:41:38.300 align:start position:0% about are we going to support the other E<00:41:30.869> or<00:41:31.619> I<00:41:32.960> don't<00:41:33.960> know<00:41:35.869> I<00:41:36.890> mean<00:41:37.890> we<00:41:38.130> can 00:41:38.300 --> 00:41:38.310 align:start position:0% E or I don't know I mean we can 00:41:38.310 --> 00:41:39.950 align:start position:0% E or I don't know I mean we can certainly<00:41:38.550> build<00:41:38.849> formal<00:41:39.390> models<00:41:39.690> of<00:41:39.839> those 00:41:39.950 --> 00:41:39.960 align:start position:0% certainly build formal models of those 00:41:39.960 --> 00:41:41.359 align:start position:0% certainly build formal models of those other<00:41:40.170> ones<00:41:40.410> and<00:41:40.589> then<00:41:40.710> we<00:41:40.800> can<00:41:40.920> look<00:41:41.040> at<00:41:41.220> them 00:41:41.359 --> 00:41:41.369 align:start position:0% other ones and then we can look at them 00:41:41.369 --> 00:41:42.770 align:start position:0% other ones and then we can look at them and<00:41:41.490> see<00:41:41.700> ok<00:41:42.060> can<00:41:42.210> we<00:41:42.270> apply<00:41:42.480> those<00:41:42.750> changes 00:41:42.770 --> 00:41:42.780 align:start position:0% and see ok can we apply those changes 00:41:42.780 --> 00:41:49.550 align:start position:0% and see ok can we apply those changes that<00:41:43.319> they<00:41:43.440> make<00:41:43.650> to<00:41:44.089> our<00:41:45.890> EDM<00:41:46.890> as<00:41:47.099> well<00:41:47.280> but<00:41:48.560> ok 00:41:49.550 --> 00:41:49.560 align:start position:0% that they make to our EDM as well but ok 00:41:49.560 --> 00:41:52.040 align:start position:0% that they make to our EDM as well but ok so<00:41:49.619> so<00:41:50.099> maybe<00:41:50.220> this<00:41:50.490> is<00:41:50.670> not<00:41:50.849> relevant<00:41:51.240> and<00:41:51.750> in 00:41:52.040 --> 00:41:52.050 align:start position:0% so so maybe this is not relevant and in 00:41:52.050 --> 00:41:54.770 align:start position:0% so so maybe this is not relevant and in fact<00:41:52.260> various<00:41:53.130> things<00:41:53.369> called<00:41:53.640> EVM<00:41:54.060> are<00:41:54.569> gonna 00:41:54.770 --> 00:41:54.780 align:start position:0% fact various things called EVM are gonna 00:41:54.780 --> 00:41:57.079 align:start position:0% fact various things called EVM are gonna live<00:41:54.990> in<00:41:55.109> their<00:41:55.230> own<00:41:55.349> worlds<00:41:55.859> it<00:41:56.460> just<00:41:56.760> feels 00:41:57.079 --> 00:41:57.089 align:start position:0% live in their own worlds it just feels 00:41:57.089 --> 00:41:58.430 align:start position:0% live in their own worlds it just feels like<00:41:57.300> it<00:41:57.480> might<00:41:57.630> be<00:41:57.780> a<00:41:57.810> way<00:41:57.990> to<00:41:58.020> actually 00:41:58.430 --> 00:41:58.440 align:start position:0% like it might be a way to actually 00:41:58.440 --> 00:42:01.460 align:start position:0% like it might be a way to actually broaden<00:41:58.890> our<00:41:59.040> community<00:41:59.690> and<00:42:00.690> get<00:42:01.079> high 00:42:01.460 --> 00:42:01.470 align:start position:0% broaden our community and get high 00:42:01.470 --> 00:42:03.710 align:start position:0% broaden our community and get high quality<00:42:01.530> code<00:42:02.160> together<00:42:02.339> so<00:42:03.030> she's<00:42:03.420> an<00:42:03.510> idea 00:42:03.710 --> 00:42:03.720 align:start position:0% quality code together so she's an idea 00:42:03.720 --> 00:42:05.450 align:start position:0% quality code together so she's an idea so<00:42:04.140> from<00:42:04.319> my<00:42:04.410> perspective<00:42:04.650> that's<00:42:05.099> one<00:42:05.280> of<00:42:05.369> the 00:42:05.450 --> 00:42:05.460 align:start position:0% so from my perspective that's one of the 00:42:05.460 --> 00:42:07.400 align:start position:0% so from my perspective that's one of the main<00:42:05.609> goals<00:42:05.730> of<00:42:05.880> you<00:42:06.030> was<00:42:06.150> it<00:42:06.180> is<00:42:06.930> that<00:42:07.230> we're 00:42:07.400 --> 00:42:07.410 align:start position:0% main goals of you was it is that we're 00:42:07.410 --> 00:42:08.809 align:start position:0% main goals of you was it is that we're stepping<00:42:07.680> into<00:42:07.950> a<00:42:08.010> much<00:42:08.160> broader<00:42:08.310> community 00:42:08.809 --> 00:42:08.819 align:start position:0% stepping into a much broader community 00:42:08.819 --> 00:42:13.040 align:start position:0% stepping into a much broader community so<00:42:09.270> the<00:42:09.510> other<00:42:09.810> EVMS<00:42:10.530> should<00:42:10.800> all<00:42:11.099> die<00:42:12.020> no<00:42:13.020> I 00:42:13.040 --> 00:42:13.050 align:start position:0% so the other EVMS should all die no I 00:42:13.050 --> 00:42:14.480 align:start position:0% so the other EVMS should all die no I didn't<00:42:13.619> say<00:42:13.680> that<00:42:13.829> but<00:42:13.920> I'm<00:42:14.040> saying<00:42:14.250> if<00:42:14.310> that's 00:42:14.480 --> 00:42:14.490 align:start position:0% didn't say that but I'm saying if that's 00:42:14.490 --> 00:42:15.950 align:start position:0% didn't say that but I'm saying if that's our<00:42:14.579> goal<00:42:14.849> I<00:42:14.880> think<00:42:15.240> that<00:42:15.359> he<00:42:15.450> wasn't<00:42:15.630> largely 00:42:15.950 --> 00:42:15.960 align:start position:0% our goal I think that he wasn't largely 00:42:15.960 --> 00:42:17.329 align:start position:0% our goal I think that he wasn't largely serves<00:42:16.230> that<00:42:16.440> goal<00:42:16.589> that's<00:42:16.859> all<00:42:16.950> I'm<00:42:17.069> saying 00:42:17.329 --> 00:42:17.339 align:start position:0% serves that goal that's all I'm saying 00:42:17.339 --> 00:42:21.740 align:start position:0% serves that goal that's all I'm saying mm-hmm<00:42:17.819> in<00:42:18.780> EVM<00:42:20.240> over<00:42:21.240> the<00:42:21.359> years<00:42:21.540> there<00:42:21.720> have 00:42:21.740 --> 00:42:21.750 align:start position:0% mm-hmm in EVM over the years there have 00:42:21.750 --> 00:42:23.180 align:start position:0% mm-hmm in EVM over the years there have been<00:42:21.869> a<00:42:21.960> couple<00:42:21.990> of<00:42:22.200> other<00:42:22.290> chains<00:42:22.680> using<00:42:22.920> it 00:42:23.180 --> 00:42:23.190 align:start position:0% been a couple of other chains using it 00:42:23.190 --> 00:42:26.390 align:start position:0% been a couple of other chains using it and<00:42:24.140> most<00:42:25.140> of<00:42:25.260> those<00:42:25.380> chains<00:42:25.740> have<00:42:26.040> made 00:42:26.390 --> 00:42:26.400 align:start position:0% and most of those chains have made 00:42:26.400 --> 00:42:30.200 align:start position:0% and most of those chains have made additions<00:42:26.970> to<00:42:27.060> it<00:42:28.400> inform<00:42:29.400> self<00:42:29.640> new<00:42:29.790> up<00:42:29.940> codes 00:42:30.200 --> 00:42:30.210 align:start position:0% additions to it inform self new up codes 00:42:30.210 --> 00:42:32.870 align:start position:0% additions to it inform self new up codes to<00:42:30.810> access<00:42:31.410> data<00:42:31.740> so<00:42:31.980> one<00:42:32.099> example<00:42:32.400> I<00:42:32.579> think<00:42:32.640> is 00:42:32.870 --> 00:42:32.880 align:start position:0% to access data so one example I think is 00:42:32.880 --> 00:42:34.750 align:start position:0% to access data so one example I think is good<00:42:33.060> stuff<00:42:33.329> they<00:42:33.510> had<00:42:33.630> like<00:42:33.869> six<00:42:34.140> sub<00:42:34.290> codes 00:42:34.750 --> 00:42:34.760 align:start position:0% good stuff they had like six sub codes 00:42:34.760 --> 00:42:36.620 align:start position:0% good stuff they had like six sub codes there<00:42:35.760> were<00:42:35.819> a<00:42:35.849> couple<00:42:35.940> of<00:42:36.119> others<00:42:36.300> that<00:42:36.480> kind 00:42:36.620 --> 00:42:36.630 align:start position:0% there were a couple of others that kind 00:42:36.630 --> 00:42:40.460 align:start position:0% there were a couple of others that kind of<00:42:36.660> Cocoon<00:42:36.810> right<00:42:37.319> now<00:42:37.500> but<00:42:38.490> all<00:42:38.609> of<00:42:38.730> these<00:42:39.470> may 00:42:40.460 --> 00:42:40.470 align:start position:0% of Cocoon right now but all of these may 00:42:40.470 --> 00:42:42.190 align:start position:0% of Cocoon right now but all of these may be<00:42:40.500> for<00:42:40.770> the<00:42:40.829> lack<00:42:40.980> of<00:42:41.010> the<00:42:41.130> platform<00:42:41.730> to 00:42:42.190 --> 00:42:42.200 align:start position:0% be for the lack of the platform to 00:42:42.200 --> 00:42:44.930 align:start position:0% be for the lack of the platform to communicate<00:42:43.200> these<00:42:43.290> ideas<00:42:43.440> they<00:42:44.430> are<00:42:44.550> Forks 00:42:44.930 --> 00:42:44.940 align:start position:0% communicate these ideas they are Forks 00:42:44.940 --> 00:42:48.200 align:start position:0% communicate these ideas they are Forks they're<00:42:45.119> not<00:42:45.210> compatible<00:42:45.680> and<00:42:47.089> when<00:42:48.089> they 00:42:48.200 --> 00:42:48.210 align:start position:0% they're not compatible and when they 00:42:48.210 --> 00:42:49.550 align:start position:0% they're not compatible and when they made<00:42:48.359> these<00:42:48.480> changes<00:42:48.869> they<00:42:48.990> also<00:42:49.109> had<00:42:49.380> to 00:42:49.550 --> 00:42:49.560 align:start position:0% made these changes they also had to 00:42:49.560 --> 00:42:51.680 align:start position:0% made these changes they also had to change<00:42:50.250> the<00:42:50.490> language<00:42:50.640> is<00:42:50.910> supporting<00:42:51.329> EVM 00:42:51.680 --> 00:42:51.690 align:start position:0% change the language is supporting EVM 00:42:51.690 --> 00:42:53.480 align:start position:0% change the language is supporting EVM which<00:42:52.230> at<00:42:52.380> a<00:42:52.410> time<00:42:52.680> with<00:42:52.829> religious<00:42:53.130> solidity 00:42:53.480 --> 00:42:53.490 align:start position:0% which at a time with religious solidity 00:42:53.490 --> 00:42:56.540 align:start position:0% which at a time with religious solidity so<00:42:54.119> they<00:42:54.359> for<00:42:54.599> solidity<00:42:55.050> to<00:42:55.619> support<00:42:56.400> those 00:42:56.540 --> 00:42:56.550 align:start position:0% so they for solidity to support those 00:42:56.550 --> 00:42:58.640 align:start position:0% so they for solidity to support those things<00:42:56.839> and<00:42:57.839> I<00:42:57.990> don't<00:42:58.020> really<00:42:58.319> see<00:42:58.530> any 00:42:58.640 --> 00:42:58.650 align:start position:0% things and I don't really see any 00:42:58.650 --> 00:43:00.050 align:start position:0% things and I don't really see any communication<00:42:59.130> between<00:42:59.310> any<00:42:59.579> of<00:42:59.640> these<00:42:59.819> other 00:43:00.050 --> 00:43:00.060 align:start position:0% communication between any of these other 00:43:00.060 --> 00:43:02.329 align:start position:0% communication between any of these other forces<00:43:00.720> their<00:43:00.869> users<00:43:01.170> of<00:43:01.380> EVM<00:43:01.740> at<00:43:01.950> the<00:43:02.040> moment 00:43:02.329 --> 00:43:02.339 align:start position:0% forces their users of EVM at the moment 00:43:02.339 --> 00:43:04.670 align:start position:0% forces their users of EVM at the moment I<00:43:03.030> think<00:43:03.690> we<00:43:03.780> have<00:43:03.869> to<00:43:03.990> overcome<00:43:04.260> that<00:43:04.470> issue 00:43:04.670 --> 00:43:04.680 align:start position:0% I think we have to overcome that issue 00:43:04.680 --> 00:43:06.980 align:start position:0% I think we have to overcome that issue first<00:43:05.010> get<00:43:05.730> like<00:43:05.940> a<00:43:06.180> discussion<00:43:06.569> flowing 00:43:06.980 --> 00:43:06.990 align:start position:0% first get like a discussion flowing 00:43:06.990 --> 00:43:11.120 align:start position:0% first get like a discussion flowing between<00:43:07.140> the<00:43:07.410> different<00:43:07.710> EVM<00:43:08.099> forts<00:43:10.130> between 00:43:11.120 --> 00:43:11.130 align:start position:0% between the different EVM forts between 00:43:11.130 --> 00:43:13.280 align:start position:0% between the different EVM forts between like<00:43:11.550> you<00:43:11.790> know<00:43:12.000> the<00:43:12.089> maenette<00:43:12.420> in<00:43:12.720> front<00:43:12.960> of<00:43:13.109> a 00:43:13.280 --> 00:43:13.290 align:start position:0% like you know the maenette in front of a 00:43:13.290 --> 00:43:15.770 align:start position:0% like you know the maenette in front of a IPS<00:43:13.829> and<00:43:14.160> as<00:43:14.670> well<00:43:14.849> as<00:43:14.970> like<00:43:15.150> the<00:43:15.300> language 00:43:15.770 --> 00:43:15.780 align:start position:0% IPS and as well as like the language 00:43:15.780 --> 00:43:19.069 align:start position:0% IPS and as well as like the language designers<00:43:16.770> compiler<00:43:17.300> others<00:43:18.300> in<00:43:18.630> the<00:43:18.810> theorem 00:43:19.069 --> 00:43:19.079 align:start position:0% designers compiler others in the theorem 00:43:19.079 --> 00:43:21.470 align:start position:0% designers compiler others in the theorem space<00:43:19.369> and<00:43:20.369> once<00:43:20.579> that<00:43:20.790> is<00:43:20.910> solved<00:43:21.210> you<00:43:21.300> can 00:43:21.470 --> 00:43:21.480 align:start position:0% space and once that is solved you can 00:43:21.480 --> 00:43:22.340 align:start position:0% space and once that is solved you can you<00:43:21.750> can<00:43:21.930> then 00:43:22.340 --> 00:43:22.350 align:start position:0% you can then 00:43:22.350 --> 00:43:24.530 align:start position:0% you can then to<00:43:22.440> learn<00:43:22.500> how<00:43:22.680> to<00:43:23.000> you<00:43:24.000> know<00:43:24.030> make<00:43:24.120> bigger 00:43:24.530 --> 00:43:24.540 align:start position:0% to learn how to you know make bigger 00:43:24.540 --> 00:43:26.270 align:start position:0% to learn how to you know make bigger changes<00:43:24.570> and<00:43:25.110> get<00:43:25.350> those<00:43:25.470> changes<00:43:25.860> down<00:43:26.040> to 00:43:26.270 --> 00:43:26.280 align:start position:0% changes and get those changes down to 00:43:26.280 --> 00:43:28.340 align:start position:0% changes and get those changes down to them<00:43:26.430> but<00:43:27.270> we<00:43:27.360> we<00:43:27.690> have<00:43:27.840> those<00:43:28.020> channels 00:43:28.340 --> 00:43:28.350 align:start position:0% them but we we have those channels 00:43:28.350 --> 00:43:32.990 align:start position:0% them but we we have those channels closed<00:43:28.560> for<00:43:28.800> some<00:43:28.950> reason<00:43:31.100> so<00:43:32.100> yeah<00:43:32.460> so<00:43:32.700> for<00:43:32.850> me 00:43:32.990 --> 00:43:33.000 align:start position:0% closed for some reason so yeah so for me 00:43:33.000 --> 00:43:35.690 align:start position:0% closed for some reason so yeah so for me it's<00:43:33.180> it's<00:43:33.540> yeah<00:43:34.260> from<00:43:34.830> my<00:43:35.010> perspective<00:43:35.280> it's 00:43:35.690 --> 00:43:35.700 align:start position:0% it's it's yeah from my perspective it's 00:43:35.700 --> 00:43:37.970 align:start position:0% it's it's yeah from my perspective it's mostly<00:43:36.030> communication<00:43:36.960> easier<00:43:37.260> and<00:43:37.500> it's<00:43:37.770> so 00:43:37.970 --> 00:43:37.980 align:start position:0% mostly communication easier and it's so 00:43:37.980 --> 00:43:40.250 align:start position:0% mostly communication easier and it's so easy<00:43:38.220> to<00:43:38.250> fork<00:43:38.610> and<00:43:38.880> then<00:43:39.030> never<00:43:39.330> go<00:43:39.630> back<00:43:39.840> for 00:43:40.250 --> 00:43:40.260 align:start position:0% easy to fork and then never go back for 00:43:40.260 --> 00:43:42.440 align:start position:0% easy to fork and then never go back for DFC<00:43:40.980> project<00:43:41.400> whatever<00:43:41.640> direction<00:43:42.000> the 00:43:42.440 --> 00:43:42.450 align:start position:0% DFC project whatever direction the 00:43:42.450 --> 00:43:45.410 align:start position:0% DFC project whatever direction the communication<00:43:43.140> should<00:43:43.260> go<00:43:43.530> so<00:43:44.400> like<00:43:44.790> everyone 00:43:45.410 --> 00:43:45.420 align:start position:0% communication should go so like everyone 00:43:45.420 --> 00:43:49.340 align:start position:0% communication should go so like everyone is<00:43:45.720> I<00:43:46.050> think<00:43:46.170> like<00:43:46.350> own<00:43:46.830> a<00:43:47.430> IP<00:43:47.610> repo<00:43:48.480> with<00:43:48.750> VIPs 00:43:49.340 --> 00:43:49.350 align:start position:0% is I think like own a IP repo with VIPs 00:43:49.350 --> 00:43:51.500 align:start position:0% is I think like own a IP repo with VIPs like<00:43:49.650> with<00:43:50.220> different<00:43:50.400> names<00:43:50.790> even<00:43:51.270> cover 00:43:51.500 --> 00:43:51.510 align:start position:0% like with different names even cover 00:43:51.510 --> 00:43:54.080 align:start position:0% like with different names even cover network<00:43:51.960> has<00:43:52.200> what<00:43:52.830> I<00:43:52.860> find<00:43:53.220> out<00:43:53.370> like<00:43:53.640> last 00:43:54.080 --> 00:43:54.090 align:start position:0% network has what I find out like last 00:43:54.090 --> 00:43:57.160 align:start position:0% network has what I find out like last week<00:43:54.390> there's<00:43:54.690> like<00:43:54.960> cover<00:43:55.320> network 00:43:57.160 --> 00:43:57.170 align:start position:0% week there's like cover network 00:43:57.170 --> 00:44:00.680 align:start position:0% week there's like cover network improvement<00:43:58.170> proposals<00:43:58.800> something<00:43:59.370> and<00:43:59.700> so 00:44:00.680 --> 00:44:00.690 align:start position:0% improvement proposals something and so 00:44:00.690 --> 00:44:02.840 align:start position:0% improvement proposals something and so this<00:44:00.900> information<00:44:01.140> is<00:44:01.770> not<00:44:01.890> exchanged<00:44:02.460> this 00:44:02.840 --> 00:44:02.850 align:start position:0% this information is not exchanged this 00:44:02.850 --> 00:44:05.270 align:start position:0% this information is not exchanged this is<00:44:03.060> I<00:44:03.390> don't<00:44:03.750> know<00:44:03.930> how<00:44:04.050> to<00:44:04.110> fix<00:44:04.410> it<00:44:04.620> maybe<00:44:05.040> you 00:44:05.270 --> 00:44:05.280 align:start position:0% is I don't know how to fix it maybe you 00:44:05.280 --> 00:44:08.240 align:start position:0% is I don't know how to fix it maybe you have<00:44:05.460> some<00:44:05.640> ideas<00:44:06.000> but<00:44:06.330> yeah<00:44:06.690> definitely<00:44:07.250> to 00:44:08.240 --> 00:44:08.250 align:start position:0% have some ideas but yeah definitely to 00:44:08.250 --> 00:44:11.570 align:start position:0% have some ideas but yeah definitely to having<00:44:08.610> some<00:44:09.740> some<00:44:10.740> platform<00:44:11.190> to<00:44:11.370> communicate 00:44:11.570 --> 00:44:11.580 align:start position:0% having some some platform to communicate 00:44:11.580 --> 00:44:14.240 align:start position:0% having some some platform to communicate that<00:44:12.230> would<00:44:13.230> be<00:44:13.410> would<00:44:13.560> be<00:44:13.620> great<00:44:13.980> I 00:44:14.240 --> 00:44:14.250 align:start position:0% that would be would be great I 00:44:14.250 --> 00:44:17.270 align:start position:0% that would be would be great I personally<00:44:15.150> hope<00:44:15.330> like<00:44:15.660> we<00:44:15.930> can<00:44:16.110> get<00:44:16.350> a<00:44:16.650> VM<00:44:17.040> see 00:44:17.270 --> 00:44:17.280 align:start position:0% personally hope like we can get a VM see 00:44:17.280 --> 00:44:20.090 align:start position:0% personally hope like we can get a VM see in<00:44:17.460> spotting<00:44:18.210> VM<00:44:18.480> which<00:44:18.750> is<00:44:18.960> by<00:44:19.230> its<00:44:19.860> even 00:44:20.090 --> 00:44:20.100 align:start position:0% in spotting VM which is by its even 00:44:20.100 --> 00:44:23.810 align:start position:0% in spotting VM which is by its even classic<00:44:20.600> I<00:44:21.770> haven't<00:44:22.770> checked<00:44:23.280> the<00:44:23.490> details 00:44:23.810 --> 00:44:23.820 align:start position:0% classic I haven't checked the details 00:44:23.820 --> 00:44:26.360 align:start position:0% classic I haven't checked the details what<00:44:24.090> what<00:44:24.630> changes<00:44:24.660> they<00:44:25.380> have<00:44:25.620> they<00:44:25.950> support 00:44:26.360 --> 00:44:26.370 align:start position:0% what what changes they have they support 00:44:26.370 --> 00:44:29.270 align:start position:0% what what changes they have they support all<00:44:26.460> of<00:44:26.490> that<00:44:26.760> what<00:44:27.120> seems<00:44:27.540> quite<00:44:28.140> close<00:44:28.890> to 00:44:29.270 --> 00:44:29.280 align:start position:0% all of that what seems quite close to 00:44:29.280 --> 00:44:32.840 align:start position:0% all of that what seems quite close to our<00:44:29.670> needs<00:44:30.030> so<00:44:30.900> that<00:44:30.930> we<00:44:31.110> interesting<00:44:31.830> to<00:44:32.010> to 00:44:32.840 --> 00:44:32.850 align:start position:0% our needs so that we interesting to to 00:44:32.850 --> 00:44:37.010 align:start position:0% our needs so that we interesting to to try<00:44:33.090> it<00:44:33.150> on<00:44:33.420> to<00:44:34.140> your<00:44:34.260> network<00:44:35.870> any<00:44:36.870> other 00:44:37.010 --> 00:44:37.020 align:start position:0% try it on to your network any other 00:44:37.020 --> 00:44:46.610 align:start position:0% try it on to your network any other questions<00:44:37.350> yeah<00:44:44.330> I<00:44:45.330> wanted<00:44:45.990> to<00:44:46.110> clarify<00:44:46.350> that 00:44:46.610 --> 00:44:46.620 align:start position:0% questions yeah I wanted to clarify that 00:44:46.620 --> 00:44:50.810 align:start position:0% questions yeah I wanted to clarify that Microsoft<00:44:47.430> IBM<00:44:48.230> implementation<00:44:49.230> is<00:44:49.380> for<00:44:49.820> SGX 00:44:50.810 --> 00:44:50.820 align:start position:0% Microsoft IBM implementation is for SGX 00:44:50.820 --> 00:44:53.240 align:start position:0% Microsoft IBM implementation is for SGX environments<00:44:51.750> so<00:44:51.960> basically<00:44:52.800> the<00:44:53.040> gas 00:44:53.240 --> 00:44:53.250 align:start position:0% environments so basically the gas 00:44:53.250 --> 00:44:55.750 align:start position:0% environments so basically the gas calculation<00:44:53.880> doesn't<00:44:54.180> make<00:44:54.330> sense<00:44:54.600> they're 00:44:55.750 --> 00:44:55.760 align:start position:0% calculation doesn't make sense they're 00:44:55.760 --> 00:44:58.400 align:start position:0% calculation doesn't make sense they're basically<00:44:56.760> they<00:44:56.940> want<00:44:57.180> to<00:44:57.330> you<00:44:57.600> know<00:44:57.750> enabled 00:44:58.400 --> 00:44:58.410 align:start position:0% basically they want to you know enabled 00:44:58.410 --> 00:45:01.070 align:start position:0% basically they want to you know enabled it<00:44:58.560> on<00:44:58.710> the<00:44:58.890> other<00:44:59.150> and<00:45:00.150> you<00:45:00.390> can<00:45:00.420> just<00:45:00.870> you 00:45:01.070 --> 00:45:01.080 align:start position:0% it on the other and you can just you 00:45:01.080 --> 00:45:03.560 align:start position:0% it on the other and you can just you know<00:45:01.140> send<00:45:01.230> code<00:45:01.770> and<00:45:02.010> get<00:45:02.220> the<00:45:02.420> get<00:45:03.420> the 00:45:03.560 --> 00:45:03.570 align:start position:0% know send code and get the get the 00:45:03.570 --> 00:45:07.250 align:start position:0% know send code and get the get the verified<00:45:04.050> computation<00:45:04.790> off<00:45:05.790> train<00:45:06.480> which<00:45:07.080> is 00:45:07.250 --> 00:45:07.260 align:start position:0% verified computation off train which is 00:45:07.260 --> 00:45:08.960 align:start position:0% verified computation off train which is pretty<00:45:07.560> interesting<00:45:07.830> but<00:45:08.190> I<00:45:08.310> guess<00:45:08.520> the<00:45:08.790> gas 00:45:08.960 --> 00:45:08.970 align:start position:0% pretty interesting but I guess the gas 00:45:08.970 --> 00:45:11.650 align:start position:0% pretty interesting but I guess the gas calculation<00:45:09.480> doesn't<00:45:09.780> make<00:45:09.870> sense<00:45:10.140> there 00:45:11.650 --> 00:45:11.660 align:start position:0% calculation doesn't make sense there 00:45:11.660 --> 00:45:19.090 align:start position:0% calculation doesn't make sense there it's<00:45:12.660> negotiation<00:45:16.190> you<00:45:17.190> did<00:45:17.370> the<00:45:17.520> KVM<00:45:18.210> work 00:45:19.090 --> 00:45:19.100 align:start position:0% it's negotiation you did the KVM work 00:45:19.100 --> 00:45:22.610 align:start position:0% it's negotiation you did the KVM work I've<00:45:20.100> had<00:45:20.940> some<00:45:21.180> conversations<00:45:21.390> and<00:45:22.350> work 00:45:22.610 --> 00:45:22.620 align:start position:0% I've had some conversations and work 00:45:22.620 --> 00:45:26.990 align:start position:0% I've had some conversations and work with<00:45:22.950> seed<00:45:23.820> whoever<00:45:24.300> he<00:45:24.570> is 00:45:26.990 --> 00:45:27.000 align:start position:0% 00:45:27.000 --> 00:45:28.970 align:start position:0% there's<00:45:27.359> a<00:45:27.420> man<00:45:27.660> whose<00:45:27.869> jitter<00:45:28.440> tagged<00:45:28.740> his 00:45:28.970 --> 00:45:28.980 align:start position:0% there's a man whose jitter tagged his 00:45:28.980 --> 00:45:31.849 align:start position:0% there's a man whose jitter tagged his seed<00:45:29.250> I<00:45:29.609> don't<00:45:30.210> know<00:45:30.359> who<00:45:30.480> he<00:45:30.599> actually<00:45:30.779> is<00:45:31.049> but 00:45:31.849 --> 00:45:31.859 align:start position:0% seed I don't know who he actually is but 00:45:31.859 --> 00:45:33.950 align:start position:0% seed I don't know who he actually is but we've<00:45:32.039> had<00:45:32.460> a<00:45:32.520> lot<00:45:32.640> of<00:45:32.910> a<00:45:33.480> lot<00:45:33.839> of 00:45:33.950 --> 00:45:33.960 align:start position:0% we've had a lot of a lot of 00:45:33.960 --> 00:45:38.109 align:start position:0% we've had a lot of a lot of communication<00:45:35.119> he's<00:45:36.119> working<00:45:36.690> on<00:45:36.900> a<00:45:37.410> lamb 00:45:38.109 --> 00:45:38.119 align:start position:0% communication he's working on a lamb 00:45:38.119 --> 00:45:42.880 align:start position:0% communication he's working on a lamb formalization<00:45:39.380> forked<00:45:40.380> off<00:45:40.559> of<00:45:40.890> a<00:45:41.339> cheese 00:45:42.880 --> 00:45:42.890 align:start position:0% formalization forked off of a cheese 00:45:42.890 --> 00:45:47.539 align:start position:0% formalization forked off of a cheese formalization<00:45:44.119> and<00:45:45.829> we've<00:45:46.829> talked<00:45:47.130> a<00:45:47.339> bit 00:45:47.539 --> 00:45:47.549 align:start position:0% formalization and we've talked a bit 00:45:47.549 --> 00:45:50.960 align:start position:0% formalization and we've talked a bit about<00:45:47.579> where<00:45:48.270> that<00:45:48.599> the<00:45:48.900> current<00:45:49.789> the<00:45:50.789> current 00:45:50.960 --> 00:45:50.970 align:start position:0% about where that the current the current 00:45:50.970 --> 00:45:53.390 align:start position:0% about where that the current the current EVM<00:45:51.599> gets<00:45:51.960> in<00:45:52.140> the<00:45:52.260> way<00:45:52.440> of<00:45:52.710> that<00:45:52.890> kind<00:45:53.220> of 00:45:53.390 --> 00:45:53.400 align:start position:0% EVM gets in the way of that kind of 00:45:53.400 --> 00:45:57.289 align:start position:0% EVM gets in the way of that kind of thing<00:45:53.760> and<00:45:54.089> how<00:45:54.920> my<00:45:55.920> proposals<00:45:56.670> are<00:45:56.789> intended 00:45:57.289 --> 00:45:57.299 align:start position:0% thing and how my proposals are intended 00:45:57.299 --> 00:46:01.339 align:start position:0% thing and how my proposals are intended to<00:45:57.329> help<00:45:58.400> see<00:45:59.400> this<00:45:59.760> was<00:46:00.180> quite<00:46:00.359> excited<00:46:01.109> and 00:46:01.339 --> 00:46:01.349 align:start position:0% to help see this was quite excited and 00:46:01.349 --> 00:46:03.589 align:start position:0% to help see this was quite excited and contacted<00:46:02.160> me<00:46:02.279> it's<00:46:02.460> like<00:46:02.609> when<00:46:03.089> did<00:46:03.270> these<00:46:03.359> go 00:46:03.589 --> 00:46:03.599 align:start position:0% contacted me it's like when did these go 00:46:03.599 --> 00:46:06.380 align:start position:0% contacted me it's like when did these go in<00:46:03.779> they<00:46:04.049> would<00:46:04.170> help<00:46:04.349> so<00:46:04.589> much<00:46:05.150> but<00:46:06.150> I'm 00:46:06.380 --> 00:46:06.390 align:start position:0% in they would help so much but I'm 00:46:06.390 --> 00:46:08.569 align:start position:0% in they would help so much but I'm running<00:46:06.569> as<00:46:06.960> a<00:46:06.990> formless<00:46:07.559> what<00:46:07.829> your<00:46:08.039> opinion 00:46:08.569 --> 00:46:08.579 align:start position:0% running as a formless what your opinion 00:46:08.579 --> 00:46:11.150 align:start position:0% running as a formless what your opinion is<00:46:08.730> is<00:46:09.059> how<00:46:09.240> much<00:46:09.450> would<00:46:09.750> it<00:46:09.779> help<00:46:10.049> and<00:46:10.740> how<00:46:10.890> bad 00:46:11.150 --> 00:46:11.160 align:start position:0% is is how much would it help and how bad 00:46:11.160 --> 00:46:13.359 align:start position:0% is is how much would it help and how bad is<00:46:11.430> it<00:46:11.460> right<00:46:11.849> now 00:46:13.359 --> 00:46:13.369 align:start position:0% is it right now 00:46:13.369 --> 00:46:15.950 align:start position:0% is it right now well<00:46:14.369> nothing's<00:46:14.760> crashing<00:46:15.240> and<00:46:15.359> burning<00:46:15.480> so<00:46:15.930> I 00:46:15.950 --> 00:46:15.960 align:start position:0% well nothing's crashing and burning so I 00:46:15.960 --> 00:46:19.660 align:start position:0% well nothing's crashing and burning so I think<00:46:16.049> it's<00:46:16.410> not<00:46:16.559> it's<00:46:16.920> not<00:46:17.099> too<00:46:17.309> bad<00:46:17.460> but<00:46:17.869> it 00:46:19.660 --> 00:46:19.670 align:start position:0% think it's not it's not too bad but it 00:46:19.670 --> 00:46:24.740 align:start position:0% think it's not it's not too bad but it it's<00:46:20.670> it's<00:46:21.000> quite<00:46:21.240> a<00:46:21.270> pain<00:46:21.510> to<00:46:21.779> update<00:46:23.630> KB<00:46:24.630> I'm 00:46:24.740 --> 00:46:24.750 align:start position:0% it's it's quite a pain to update KB I'm 00:46:24.750 --> 00:46:26.930 align:start position:0% it's it's quite a pain to update KB I'm especially<00:46:24.990> anything<00:46:25.349> regarding<00:46:25.920> the<00:46:26.130> gas 00:46:26.930 --> 00:46:26.940 align:start position:0% especially anything regarding the gas 00:46:26.940 --> 00:46:29.510 align:start position:0% especially anything regarding the gas calculations<00:46:27.720> because<00:46:28.140> there<00:46:29.010> was<00:46:29.130> I<00:46:29.309> mean 00:46:29.510 --> 00:46:29.520 align:start position:0% calculations because there was I mean 00:46:29.520 --> 00:46:30.710 align:start position:0% calculations because there was I mean you<00:46:29.579> have<00:46:29.700> to<00:46:29.819> do<00:46:29.940> things<00:46:30.180> in<00:46:30.299> a<00:46:30.359> very<00:46:30.510> specific 00:46:30.710 --> 00:46:30.720 align:start position:0% you have to do things in a very specific 00:46:30.720 --> 00:46:32.420 align:start position:0% you have to do things in a very specific order<00:46:31.079> and<00:46:31.260> it's<00:46:31.500> it's<00:46:31.890> kind<00:46:32.099> of<00:46:32.190> annoying 00:46:32.420 --> 00:46:32.430 align:start position:0% order and it's it's kind of annoying 00:46:32.430 --> 00:46:38.569 align:start position:0% order and it's it's kind of annoying that<00:46:32.579> you<00:46:32.730> have<00:46:32.849> to<00:46:32.940> do<00:46:33.029> that<00:46:33.380> I<00:46:37.490> don't<00:46:38.490> know 00:46:38.569 --> 00:46:38.579 align:start position:0% that you have to do that I don't know 00:46:38.579 --> 00:46:40.640 align:start position:0% that you have to do that I don't know like<00:46:38.789> for<00:46:39.329> reference<00:46:39.720> maybe<00:46:39.990> I<00:46:40.079> can<00:46:40.349> say<00:46:40.500> how 00:46:40.640 --> 00:46:40.650 align:start position:0% like for reference maybe I can say how 00:46:40.650 --> 00:46:43.309 align:start position:0% like for reference maybe I can say how long<00:46:40.859> it<00:46:41.039> took<00:46:41.190> to<00:46:41.250> formalize<00:46:41.849> EVM<00:46:42.660> versus<00:46:43.170> how 00:46:43.309 --> 00:46:43.319 align:start position:0% long it took to formalize EVM versus how 00:46:43.319 --> 00:46:45.230 align:start position:0% long it took to formalize EVM versus how long<00:46:43.559> it<00:46:43.950> took<00:46:44.130> to<00:46:44.190> formalize<00:46:44.640> the<00:46:44.819> fragment 00:46:45.230 --> 00:46:45.240 align:start position:0% long it took to formalize the fragment 00:46:45.240 --> 00:46:46.940 align:start position:0% long it took to formalize the fragment of<00:46:45.270> wasum<00:46:45.599> which<00:46:45.720> is<00:46:45.869> most<00:46:46.109> of<00:46:46.230> the<00:46:46.319> execution 00:46:46.940 --> 00:46:46.950 align:start position:0% of wasum which is most of the execution 00:46:46.950 --> 00:46:51.549 align:start position:0% of wasum which is most of the execution but<00:46:47.430> just<00:46:47.670> not<00:46:47.789> the<00:46:48.119> modules<00:46:48.740> an<00:46:49.740> EVM<00:46:50.190> took<00:46:50.520> I 00:46:51.549 --> 00:46:51.559 align:start position:0% but just not the modules an EVM took I 00:46:51.559 --> 00:46:54.559 align:start position:0% but just not the modules an EVM took I want<00:46:52.559> to<00:46:52.680> say<00:46:52.859> I<00:46:53.279> mean<00:46:54.059> depending<00:46:54.299> on<00:46:54.390> how<00:46:54.510> you 00:46:54.559 --> 00:46:54.569 align:start position:0% want to say I mean depending on how you 00:46:54.569 --> 00:46:56.839 align:start position:0% want to say I mean depending on how you count<00:46:54.779> between<00:46:55.200> you<00:46:55.710> know<00:46:55.799> 8<00:46:56.069> and<00:46:56.279> 14<00:46:56.460> months 00:46:56.839 --> 00:46:56.849 align:start position:0% count between you know 8 and 14 months 00:46:56.849 --> 00:46:59.480 align:start position:0% count between you know 8 and 14 months and<00:46:57.240> and<00:46:57.710> wasum<00:46:58.710> was<00:46:58.890> closer<00:46:59.160> to<00:46:59.279> the 00:46:59.480 --> 00:46:59.490 align:start position:0% and and wasum was closer to the 00:46:59.490 --> 00:47:02.260 align:start position:0% and and wasum was closer to the six-month<00:46:59.940> mark<00:47:00.059> maybe<00:47:00.510> so<00:47:00.930> I<00:47:01.200> think<00:47:01.589> that 00:47:02.260 --> 00:47:02.270 align:start position:0% six-month mark maybe so I think that 00:47:02.270 --> 00:47:04.819 align:start position:0% six-month mark maybe so I think that just<00:47:03.270> that<00:47:03.329> alone<00:47:03.480> and<00:47:03.779> the<00:47:04.049> wasum<00:47:04.349> definition 00:47:04.819 --> 00:47:04.829 align:start position:0% just that alone and the wasum definition 00:47:04.829 --> 00:47:06.740 align:start position:0% just that alone and the wasum definition is<00:47:04.920> just<00:47:05.130> shorter<00:47:05.730> and<00:47:05.910> it's<00:47:06.029> cleaner<00:47:06.359> and<00:47:06.690> it 00:47:06.740 --> 00:47:06.750 align:start position:0% is just shorter and it's cleaner and it 00:47:06.750 --> 00:47:09.970 align:start position:0% is just shorter and it's cleaner and it just<00:47:06.900> makes<00:47:07.079> more<00:47:07.260> sense<00:47:07.589> and<00:47:07.829> it<00:47:08.010> it<00:47:08.670> it<00:47:09.569> just 00:47:09.970 --> 00:47:09.980 align:start position:0% just makes more sense and it it it just 00:47:09.980 --> 00:47:15.380 align:start position:0% just makes more sense and it it it just feels<00:47:10.980> more<00:47:11.490> coherent<00:47:13.940> it<00:47:14.940> all<00:47:15.089> kind<00:47:15.329> of 00:47:15.380 --> 00:47:15.390 align:start position:0% feels more coherent it all kind of 00:47:15.390 --> 00:47:17.359 align:start position:0% feels more coherent it all kind of presents<00:47:15.569> itself<00:47:15.990> nicely<00:47:16.529> together<00:47:16.740> instead 00:47:17.359 --> 00:47:17.369 align:start position:0% presents itself nicely together instead 00:47:17.369 --> 00:47:23.680 align:start position:0% presents itself nicely together instead of<00:47:19.760> feeling<00:47:20.760> scatterbrained<00:47:21.569> I<00:47:21.690> don't<00:47:21.839> know 00:47:23.680 --> 00:47:23.690 align:start position:0% of feeling scatterbrained I don't know 00:47:23.690 --> 00:47:27.470 align:start position:0% of feeling scatterbrained I don't know Oh<00:47:25.099> -<00:47:26.099> van<00:47:26.339> dynamic<00:47:26.819> -<00:47:26.940> oh<00:47:27.119> that<00:47:27.329> one 00:47:27.470 --> 00:47:27.480 align:start position:0% Oh - van dynamic - oh that one 00:47:27.480 --> 00:47:29.569 align:start position:0% Oh - van dynamic - oh that one specifically<00:47:27.900> how<00:47:28.319> much<00:47:28.559> does<00:47:28.829> that<00:47:28.859> proposal 00:47:29.569 --> 00:47:29.579 align:start position:0% specifically how much does that proposal 00:47:29.579 --> 00:47:33.170 align:start position:0% specifically how much does that proposal oh<00:47:29.760> my<00:47:30.000> gosh<00:47:30.150> that<00:47:30.420> would<00:47:30.480> help<00:47:30.660> so<00:47:30.809> much<00:47:30.960> oh<00:47:32.180> my 00:47:33.170 --> 00:47:33.180 align:start position:0% oh my gosh that would help so much oh my 00:47:33.180 --> 00:47:34.050 align:start position:0% oh my gosh that would help so much oh my gosh 00:47:34.050 --> 00:47:34.060 align:start position:0% gosh 00:47:34.060 --> 00:47:36.660 align:start position:0% gosh that<00:47:34.780> that<00:47:35.110> is<00:47:35.290> a<00:47:35.320> single<00:47:35.740> like<00:47:35.980> when<00:47:36.190> we<00:47:36.490> made 00:47:36.660 --> 00:47:36.670 align:start position:0% that that is a single like when we made 00:47:36.670 --> 00:47:39.510 align:start position:0% that that is a single like when we made our<00:47:36.700> own<00:47:37.360> like<00:47:37.720> EVM<00:47:38.140> 1.5<00:47:38.800> I<00:47:38.950> called<00:47:39.160> it<00:47:39.310> EDM 00:47:39.510 --> 00:47:39.520 align:start position:0% our own like EVM 1.5 I called it EDM 00:47:39.520 --> 00:47:43.260 align:start position:0% our own like EVM 1.5 I called it EDM prime<00:47:39.850> as<00:47:40.090> a<00:47:40.120> kind<00:47:40.450> of<00:47:40.570> just<00:47:41.380> a<00:47:41.530> toy<00:47:42.100> like<00:47:43.090> how 00:47:43.260 --> 00:47:43.270 align:start position:0% prime as a kind of just a toy like how 00:47:43.270 --> 00:47:45.090 align:start position:0% prime as a kind of just a toy like how would<00:47:43.330> I<00:47:43.480> change<00:47:43.540> the<00:47:43.930> EVM<00:47:44.230> type<00:47:44.470> of<00:47:44.590> thing<00:47:44.770> and 00:47:45.090 --> 00:47:45.100 align:start position:0% would I change the EVM type of thing and 00:47:45.100 --> 00:47:46.500 align:start position:0% would I change the EVM type of thing and that<00:47:45.370> was<00:47:45.460> the<00:47:45.520> very<00:47:45.610> first<00:47:45.730> thing<00:47:46.090> I<00:47:46.180> did<00:47:46.330> was 00:47:46.500 --> 00:47:46.510 align:start position:0% that was the very first thing I did was 00:47:46.510 --> 00:47:48.480 align:start position:0% that was the very first thing I did was it<00:47:46.840> was<00:47:46.960> just<00:47:47.170> okay<00:47:47.410> all<00:47:47.590> jumps<00:47:47.920> are<00:47:48.040> actually 00:47:48.480 --> 00:47:48.490 align:start position:0% it was just okay all jumps are actually 00:47:48.490 --> 00:47:49.830 align:start position:0% it was just okay all jumps are actually labeled<00:47:48.670> and<00:47:49.060> you<00:47:49.120> only<00:47:49.240> can<00:47:49.450> jump<00:47:49.660> to<00:47:49.810> the 00:47:49.830 --> 00:47:49.840 align:start position:0% labeled and you only can jump to the 00:47:49.840 --> 00:47:51.750 align:start position:0% labeled and you only can jump to the jump<00:47:50.410> labels<00:47:50.800> or<00:47:50.950> something<00:47:51.250> like<00:47:51.340> that<00:47:51.580> and 00:47:51.750 --> 00:47:51.760 align:start position:0% jump labels or something like that and 00:47:51.760 --> 00:47:53.580 align:start position:0% jump labels or something like that and then<00:47:51.880> on<00:47:52.270> top<00:47:52.600> of<00:47:52.780> that<00:47:52.840> we<00:47:52.960> put<00:47:53.140> structured 00:47:53.580 --> 00:47:53.590 align:start position:0% then on top of that we put structured 00:47:53.590 --> 00:47:55.410 align:start position:0% then on top of that we put structured control<00:47:53.920> flow<00:47:54.100> like<00:47:54.310> if<00:47:54.490> and<00:47:54.730> wael<00:47:54.940> and<00:47:55.240> stuff 00:47:55.410 --> 00:47:55.420 align:start position:0% control flow like if and wael and stuff 00:47:55.420 --> 00:47:58.650 align:start position:0% control flow like if and wael and stuff like<00:47:55.570> that<00:47:55.720> and<00:47:55.930> and<00:47:56.760> it<00:47:57.760> makes<00:47:58.030> static 00:47:58.650 --> 00:47:58.660 align:start position:0% like that and and it makes static 00:47:58.660 --> 00:48:01.110 align:start position:0% like that and and it makes static analysis<00:47:59.140> tools<00:47:59.350> way<00:47:59.830> more<00:48:00.100> effective<00:48:00.340> like 00:48:01.110 --> 00:48:01.120 align:start position:0% analysis tools way more effective like 00:48:01.120 --> 00:48:03.090 align:start position:0% analysis tools way more effective like like<00:48:01.660> worlds<00:48:02.170> and<00:48:02.290> worlds<00:48:02.530> more<00:48:02.680> effective 00:48:03.090 --> 00:48:03.100 align:start position:0% like worlds and worlds more effective 00:48:03.100 --> 00:48:05.970 align:start position:0% like worlds and worlds more effective and<00:48:03.280> then<00:48:03.370> it<00:48:03.520> makes<00:48:04.410> verification<00:48:05.410> efforts<00:48:05.530> a 00:48:05.970 --> 00:48:05.980 align:start position:0% and then it makes verification efforts a 00:48:05.980 --> 00:48:09.630 align:start position:0% and then it makes verification efforts a lot<00:48:06.430> easier<00:48:06.910> as<00:48:07.060> well<00:48:07.830> dynamic<00:48:08.830> jumps<00:48:09.100> are<00:48:09.280> are 00:48:09.630 --> 00:48:09.640 align:start position:0% lot easier as well dynamic jumps are are 00:48:09.640 --> 00:48:14.870 align:start position:0% lot easier as well dynamic jumps are are terrible<00:48:10.120> like<00:48:10.810> can't<00:48:11.440> we<00:48:11.530> hire<00:48:11.740> you<00:48:12.810> for<00:48:13.810> what 00:48:14.870 --> 00:48:14.880 align:start position:0% terrible like can't we hire you for what 00:48:14.880 --> 00:48:18.090 align:start position:0% terrible like can't we hire you for what we<00:48:15.880> can<00:48:16.030> do<00:48:16.150> what<00:48:16.660> one<00:48:17.440> last<00:48:17.620> questions<00:48:18.010> we 00:48:18.090 --> 00:48:18.100 align:start position:0% we can do what one last questions we 00:48:18.100 --> 00:48:21.330 align:start position:0% we can do what one last questions we have<00:48:18.960> already<00:48:19.960> asked<00:48:20.080> questions<00:48:20.470> can<00:48:21.010> I<00:48:21.040> hit<00:48:21.310> a 00:48:21.330 --> 00:48:21.340 align:start position:0% have already asked questions can I hit a 00:48:21.340 --> 00:48:23.940 align:start position:0% have already asked questions can I hit a question<00:48:21.790> to<00:48:21.880> Gregg<00:48:22.120> oh<00:48:22.360> sure<00:48:22.960> all<00:48:23.830> right 00:48:23.940 --> 00:48:23.950 align:start position:0% question to Gregg oh sure all right 00:48:23.950 --> 00:48:25.800 align:start position:0% question to Gregg oh sure all right never<00:48:24.130> mind<00:48:24.190> sorry<00:48:24.610> audience<00:48:24.850> I'm<00:48:25.540> gonna<00:48:25.690> be 00:48:25.800 --> 00:48:25.810 align:start position:0% never mind sorry audience I'm gonna be 00:48:25.810 --> 00:48:26.190 align:start position:0% never mind sorry audience I'm gonna be quick 00:48:26.190 --> 00:48:26.200 align:start position:0% quick 00:48:26.200 --> 00:48:28.260 align:start position:0% quick Gregg<00:48:26.710> you<00:48:26.920> mentioned<00:48:27.550> that<00:48:27.700> at<00:48:28.090> some<00:48:28.240> point 00:48:28.260 --> 00:48:28.270 align:start position:0% Gregg you mentioned that at some point 00:48:28.270 --> 00:48:33.960 align:start position:0% Gregg you mentioned that at some point that<00:48:30.450> EVM<00:48:31.450> might<00:48:31.660> be<00:48:32.430> the<00:48:33.430> the<00:48:33.700> general 00:48:33.960 --> 00:48:33.970 align:start position:0% that EVM might be the the general 00:48:33.970 --> 00:48:36.420 align:start position:0% that EVM might be the the general description<00:48:34.240> of<00:48:34.660> the<00:48:35.320> contract<00:48:35.830> itself<00:48:36.100> but 00:48:36.420 --> 00:48:36.430 align:start position:0% description of the contract itself but 00:48:36.430 --> 00:48:38.040 align:start position:0% description of the contract itself but it's<00:48:36.550> not<00:48:36.700> the<00:48:36.820> way<00:48:36.910> it<00:48:37.150> is<00:48:37.180> executed<00:48:37.900> it's 00:48:38.040 --> 00:48:38.050 align:start position:0% it's not the way it is executed it's 00:48:38.050 --> 00:48:40.260 align:start position:0% it's not the way it is executed it's just<00:48:38.230> translated<00:48:38.770> to<00:48:38.830> something<00:48:38.980> else<00:48:39.370> maybe 00:48:40.260 --> 00:48:40.270 align:start position:0% just translated to something else maybe 00:48:40.270 --> 00:48:41.820 align:start position:0% just translated to something else maybe I<00:48:40.390> got<00:48:40.690> it<00:48:40.750> wrong<00:48:40.870> but<00:48:41.170> that's<00:48:41.500> what<00:48:41.680> you 00:48:41.820 --> 00:48:41.830 align:start position:0% I got it wrong but that's what you 00:48:41.830 --> 00:48:43.410 align:start position:0% I got it wrong but that's what you mentioned<00:48:42.070> like<00:48:42.370> in<00:48:42.520> the<00:48:42.610> first<00:48:42.820> five<00:48:43.090> minutes 00:48:43.410 --> 00:48:43.420 align:start position:0% mentioned like in the first five minutes 00:48:43.420 --> 00:48:45.030 align:start position:0% mentioned like in the first five minutes that<00:48:43.600> maybe<00:48:43.810> you<00:48:44.020> were<00:48:44.110> translated<00:48:44.620> to<00:48:44.800> you 00:48:45.030 --> 00:48:45.040 align:start position:0% that maybe you were translated to you 00:48:45.040 --> 00:48:48.690 align:start position:0% that maybe you were translated to you Azam<00:48:45.310> at<00:48:45.400> some<00:48:45.550> point<00:48:45.790> instead<00:48:46.240> I'm<00:48:46.360> saying<00:48:47.700> we 00:48:48.690 --> 00:48:48.700 align:start position:0% Azam at some point instead I'm saying we 00:48:48.700 --> 00:48:54.770 align:start position:0% Azam at some point instead I'm saying we can<00:48:48.910> do<00:48:49.090> the<00:48:49.330> work<00:48:49.570> now<00:48:50.280> to<00:48:51.280> get<00:48:51.490> a<00:48:51.520> better<00:48:51.820> EVM 00:48:54.770 --> 00:48:54.780 align:start position:0% can do the work now to get a better EVM 00:48:54.780 --> 00:48:57.890 align:start position:0% can do the work now to get a better EVM ready<00:48:55.780> and<00:48:56.080> going<00:48:56.320> on<00:48:56.830> the<00:48:57.130> main<00:48:57.310> chain 00:48:57.890 --> 00:48:57.900 align:start position:0% ready and going on the main chain 00:48:57.900 --> 00:49:01.340 align:start position:0% ready and going on the main chain because<00:48:58.900> sharding<00:48:59.560> all<00:49:00.160> of<00:49:00.460> thats<00:49:00.730> also 00:49:01.340 --> 00:49:01.350 align:start position:0% because sharding all of thats also 00:49:01.350 --> 00:49:03.840 align:start position:0% because sharding all of thats also somewhere<00:49:02.350> way<00:49:02.560> out<00:49:02.740> in<00:49:02.950> the<00:49:03.040> future<00:49:03.460> we<00:49:03.670> don't 00:49:03.840 --> 00:49:03.850 align:start position:0% somewhere way out in the future we don't 00:49:03.850 --> 00:49:07.650 align:start position:0% somewhere way out in the future we don't know<00:49:04.000> where<00:49:04.210> it<00:49:04.390> is<00:49:04.500> you<00:49:05.500> know<00:49:05.620> and<00:49:05.980> then<00:49:06.880> when 00:49:07.650 --> 00:49:07.660 align:start position:0% know where it is you know and then when 00:49:07.660 --> 00:49:11.090 align:start position:0% know where it is you know and then when Rasim<00:49:08.410> is<00:49:08.650> on<00:49:09.010> the<00:49:09.190> main<00:49:09.430> chain<00:49:09.990> solid 00:49:11.090 --> 00:49:11.100 align:start position:0% Rasim is on the main chain solid 00:49:11.100 --> 00:49:12.510 align:start position:0% Rasim is on the main chain solid formalized 00:49:12.510 --> 00:49:12.520 align:start position:0% formalized 00:49:12.520 --> 00:49:16.770 align:start position:0% formalized ready<00:49:12.760> to<00:49:13.000> go<00:49:13.210> and<00:49:13.980> your<00:49:14.980> compiler<00:49:15.670> to<00:49:16.300> compile 00:49:16.770 --> 00:49:16.780 align:start position:0% ready to go and your compiler to compile 00:49:16.780 --> 00:49:19.770 align:start position:0% ready to go and your compiler to compile from<00:49:17.230> EVM<00:49:17.770> to<00:49:18.400> as<00:49:18.640> and<00:49:18.970> that's<00:49:19.120> ready<00:49:19.300> to<00:49:19.450> go 00:49:19.770 --> 00:49:19.780 align:start position:0% from EVM to as and that's ready to go 00:49:19.780 --> 00:49:24.270 align:start position:0% from EVM to as and that's ready to go there's<00:49:20.710> not<00:49:21.070> any<00:49:21.430> big<00:49:21.760> problem<00:49:22.860> to<00:49:23.860> migrate 00:49:24.270 --> 00:49:24.280 align:start position:0% there's not any big problem to migrate 00:49:24.280 --> 00:49:27.110 align:start position:0% there's not any big problem to migrate code<00:49:24.610> there<00:49:25.420> is<00:49:25.570> no<00:49:25.750> migration<00:49:26.230> that's<00:49:26.740> just 00:49:27.110 --> 00:49:27.120 align:start position:0% code there is no migration that's just 00:49:27.120 --> 00:49:30.000 align:start position:0% code there is no migration that's just that's<00:49:28.120> just<00:49:28.360> the<00:49:29.260> way<00:49:29.440> that<00:49:29.650> it<00:49:29.800> gets 00:49:30.000 --> 00:49:30.010 align:start position:0% that's just the way that it gets 00:49:30.010 --> 00:49:34.200 align:start position:0% that's just the way that it gets executed<00:49:30.810> right<00:49:31.810> no<00:49:32.170> one<00:49:32.760> no<00:49:33.760> one<00:49:33.940> cares 00:49:34.200 --> 00:49:34.210 align:start position:0% executed right no one no one cares 00:49:34.210 --> 00:49:36.450 align:start position:0% executed right no one no one cares whether<00:49:34.930> you<00:49:35.200> compile<00:49:35.590> it<00:49:35.620> to<00:49:35.920> us<00:49:36.070> and<00:49:36.400> then 00:49:36.450 --> 00:49:36.460 align:start position:0% whether you compile it to us and then 00:49:36.460 --> 00:49:38.700 align:start position:0% whether you compile it to us and then then<00:49:36.970> compile<00:49:37.390> the<00:49:37.570> license<00:49:37.990> of<00:49:38.080> machine<00:49:38.410> code 00:49:38.700 --> 00:49:38.710 align:start position:0% then compile the license of machine code 00:49:38.710 --> 00:49:41.430 align:start position:0% then compile the license of machine code or<00:49:39.120> interpreted<00:49:40.120> or<00:49:40.540> compiled<00:49:40.930> what<00:49:41.110> right<00:49:41.290> to 00:49:41.430 --> 00:49:41.440 align:start position:0% or interpreted or compiled what right to 00:49:41.440 --> 00:49:43.530 align:start position:0% or interpreted or compiled what right to machine<00:49:41.800> code<00:49:42.100> that<00:49:42.130> the<00:49:42.670> user<00:49:42.820> doesn't<00:49:43.180> care 00:49:43.530 --> 00:49:43.540 align:start position:0% machine code that the user doesn't care 00:49:43.540 --> 00:49:45.300 align:start position:0% machine code that the user doesn't care about<00:49:43.840> that<00:49:44.020> as<00:49:44.260> long<00:49:44.470> as<00:49:44.620> it<00:49:44.740> gets<00:49:44.890> executed 00:49:45.300 --> 00:49:45.310 align:start position:0% about that as long as it gets executed 00:49:45.310 --> 00:49:47.420 align:start position:0% about that as long as it gets executed correctly 00:49:47.420 --> 00:49:47.430 align:start position:0% correctly 00:49:47.430 --> 00:49:51.510 align:start position:0% correctly but<00:49:48.430> short-term<00:49:49.390> we<00:49:49.690> we<00:49:50.140> want<00:49:50.380> to<00:49:50.500> just<00:49:50.799> get<00:49:51.339> it 00:49:51.510 --> 00:49:51.520 align:start position:0% but short-term we we want to just get it 00:49:51.520 --> 00:49:56.839 align:start position:0% but short-term we we want to just get it working<00:49:51.730> and<00:49:52.660> a<00:49:53.430> little<00:49:54.430> bit<00:49:54.640> longer<00:49:54.910> term 00:49:56.839 --> 00:49:56.849 align:start position:0% working and a little bit longer term 00:49:56.849 --> 00:50:03.839 align:start position:0% working and a little bit longer term whoa<00:49:57.849> excuse<00:49:58.750> me<00:50:01.770> just<00:50:02.770> a<00:50:02.890> little<00:50:02.920> longer<00:50:03.400> term 00:50:03.839 --> 00:50:03.849 align:start position:0% whoa excuse me just a little longer term 00:50:03.849 --> 00:50:07.620 align:start position:0% whoa excuse me just a little longer term we<00:50:04.089> you<00:50:04.510> know<00:50:04.599> we<00:50:04.809> now<00:50:04.960> have<00:50:05.319> a<00:50:05.349> a<00:50:06.630> formerly 00:50:07.620 --> 00:50:07.630 align:start position:0% we you know we now have a a formerly 00:50:07.630 --> 00:50:12.960 align:start position:0% we you know we now have a a formerly verified<00:50:08.260> subset<00:50:08.829> of<00:50:08.859> C<00:50:10.140> we've<00:50:11.140> got<00:50:11.349> I<00:50:11.970> don't 00:50:12.960 --> 00:50:12.970 align:start position:0% verified subset of C we've got I don't 00:50:12.970 --> 00:50:16.950 align:start position:0% verified subset of C we've got I don't know<00:50:13.089> it's<00:50:13.299> a<00:50:13.390> subset<00:50:14.020> or<00:50:14.049> all<00:50:14.380> but<00:50:15.690> LLVM<00:50:16.690> has 00:50:16.950 --> 00:50:16.960 align:start position:0% know it's a subset or all but LLVM has 00:50:16.960 --> 00:50:19.859 align:start position:0% know it's a subset or all but LLVM has been<00:50:17.170> formally<00:50:17.559> verified<00:50:18.089> yeah<00:50:19.089> so<00:50:19.539> we<00:50:19.660> can 00:50:19.859 --> 00:50:19.869 align:start position:0% been formally verified yeah so we can 00:50:19.869 --> 00:50:23.339 align:start position:0% been formally verified yeah so we can have<00:50:20.079> a<00:50:20.109> form<00:50:20.559> of<00:50:20.680> a<00:50:20.829> formally<00:50:21.609> verified<00:50:22.349> EVM 00:50:23.339 --> 00:50:23.349 align:start position:0% have a form of a formally verified EVM 00:50:23.349 --> 00:50:27.390 align:start position:0% have a form of a formally verified EVM 1.5<00:50:25.440> executions<00:50:26.440> of<00:50:26.529> s<00:50:26.650> mutations 00:50:27.390 --> 00:50:27.400 align:start position:0% 1.5 executions of s mutations 00:50:27.400 --> 00:50:29.849 align:start position:0% 1.5 executions of s mutations mm-hmm<00:50:28.150> we<00:50:28.390> have<00:50:28.630> specifications<00:50:28.990> but<00:50:29.589> I 00:50:29.849 --> 00:50:29.859 align:start position:0% mm-hmm we have specifications but I 00:50:29.859 --> 00:50:31.559 align:start position:0% mm-hmm we have specifications but I wouldn't<00:50:30.339> say<00:50:30.490> it's<00:50:30.609> verified<00:50:31.059> it's<00:50:31.270> just<00:50:31.420> a 00:50:31.559 --> 00:50:31.569 align:start position:0% wouldn't say it's verified it's just a 00:50:31.569 --> 00:50:36.349 align:start position:0% wouldn't say it's verified it's just a specification<00:50:31.990> okay<00:50:32.859> so<00:50:33.190> as<00:50:33.460> usual<00:50:33.880> grigory's 00:50:36.349 --> 00:50:36.359 align:start position:0% specification okay so as usual grigory's 00:50:36.359 --> 00:50:38.490 align:start position:0% specification okay so as usual grigory's problem<00:50:37.359> seeing<00:50:37.569> a<00:50:37.690> little<00:50:37.930> bit<00:50:38.109> more<00:50:38.319> than 00:50:38.490 --> 00:50:38.500 align:start position:0% problem seeing a little bit more than 00:50:38.500 --> 00:50:43.500 align:start position:0% problem seeing a little bit more than exists<00:50:39.180> but<00:50:40.180> I<00:50:41.309> want<00:50:42.309> to<00:50:42.369> put<00:50:42.520> in<00:50:42.609> another<00:50:43.000> just 00:50:43.500 --> 00:50:43.510 align:start position:0% exists but I want to put in another just 00:50:43.510 --> 00:50:45.569 align:start position:0% exists but I want to put in another just question<00:50:44.079> and<00:50:44.380> we<00:50:44.950> shouldn't<00:50:45.220> answer<00:50:45.490> it 00:50:45.569 --> 00:50:45.579 align:start position:0% question and we shouldn't answer it 00:50:45.579 --> 00:50:49.309 align:start position:0% question and we shouldn't answer it right<00:50:45.730> now<00:50:45.910> just<00:50:46.150> leave<00:50:46.329> it<00:50:46.420> hanging<00:50:47.490> if<00:50:48.490> we 00:50:49.309 --> 00:50:49.319 align:start position:0% right now just leave it hanging if we 00:50:49.319 --> 00:50:51.569 align:start position:0% right now just leave it hanging if we just<00:50:50.319> culminating<00:50:50.980> all<00:50:51.099> these<00:50:51.220> discussions 00:50:51.569 --> 00:50:51.579 align:start position:0% just culminating all these discussions 00:50:51.579 --> 00:50:53.490 align:start position:0% just culminating all these discussions we<00:50:51.849> had<00:50:51.940> if<00:50:52.059> we<00:50:52.180> keep<00:50:52.390> adding<00:50:52.839> these<00:50:53.079> changes 00:50:53.490 --> 00:50:53.500 align:start position:0% we had if we keep adding these changes 00:50:53.500 --> 00:50:55.319 align:start position:0% we had if we keep adding these changes to<00:50:53.619> EVM<00:50:53.980> yet<00:50:54.369> we<00:50:54.520> have<00:50:54.609> to<00:50:54.789> keep<00:50:54.940> backwards 00:50:55.319 --> 00:50:55.329 align:start position:0% to EVM yet we have to keep backwards 00:50:55.329 --> 00:50:57.150 align:start position:0% to EVM yet we have to keep backwards compatibility<00:50:55.960> you<00:50:56.559> know<00:50:56.680> to<00:50:56.740> a<00:50:56.859> certain 00:50:57.150 --> 00:50:57.160 align:start position:0% compatibility you know to a certain 00:50:57.160 --> 00:50:58.410 align:start position:0% compatibility you know to a certain extent<00:50:57.490> or<00:50:57.640> the<00:50:57.730> different<00:50:58.029> ways<00:50:58.150> to<00:50:58.299> do<00:50:58.390> it 00:50:58.410 --> 00:50:58.420 align:start position:0% extent or the different ways to do it 00:50:58.420 --> 00:51:00.720 align:start position:0% extent or the different ways to do it and<00:50:58.660> then<00:50:59.140> we<00:50:59.319> still<00:50:59.680> plan<00:51:00.130> to<00:51:00.190> switch<00:51:00.490> to 00:51:00.720 --> 00:51:00.730 align:start position:0% and then we still plan to switch to 00:51:00.730 --> 00:51:03.089 align:start position:0% and then we still plan to switch to uoit's<00:51:01.180> them<00:51:01.390> does<00:51:02.200> that<00:51:02.230> leave<00:51:02.559> us<00:51:02.589> with<00:51:02.890> more 00:51:03.089 --> 00:51:03.099 align:start position:0% uoit's them does that leave us with more 00:51:03.099 --> 00:51:05.010 align:start position:0% uoit's them does that leave us with more legacy<00:51:03.549> we<00:51:03.700> have<00:51:03.819> to<00:51:03.940> keep<00:51:04.180> because<00:51:04.869> all<00:51:04.990> of 00:51:05.010 --> 00:51:05.020 align:start position:0% legacy we have to keep because all of 00:51:05.020 --> 00:51:07.620 align:start position:0% legacy we have to keep because all of this<00:51:05.200> stuff<00:51:05.410> is<00:51:05.500> on<00:51:05.529> the<00:51:05.710> main<00:51:05.859> net<00:51:06.069> or<00:51:06.630> you 00:51:07.620 --> 00:51:07.630 align:start position:0% this stuff is on the main net or you 00:51:07.630 --> 00:51:09.329 align:start position:0% this stuff is on the main net or you know<00:51:07.720> it's<00:51:08.020> a<00:51:08.079> better<00:51:08.200> position<00:51:08.470> but<00:51:08.950> I<00:51:08.980> don't 00:51:09.329 --> 00:51:09.339 align:start position:0% know it's a better position but I don't 00:51:09.339 --> 00:51:10.500 align:start position:0% know it's a better position but I don't think<00:51:09.430> we<00:51:09.549> should<00:51:09.579> answer<00:51:09.819> this<00:51:10.029> right<00:51:10.210> now<00:51:10.359> we 00:51:10.500 --> 00:51:10.510 align:start position:0% think we should answer this right now we 00:51:10.510 --> 00:51:13.589 align:start position:0% think we should answer this right now we should<00:51:10.690> just<00:51:10.809> think<00:51:11.020> about<00:51:11.170> this<00:51:12.089> or<00:51:13.089> we<00:51:13.299> did 00:51:13.589 --> 00:51:13.599 align:start position:0% should just think about this or we did 00:51:13.599 --> 00:51:14.730 align:start position:0% should just think about this or we did we<00:51:13.690> have<00:51:13.779> time<00:51:13.930> for<00:51:13.990> one<00:51:14.140> more<00:51:14.230> question<00:51:14.500> from 00:51:14.730 --> 00:51:14.740 align:start position:0% we have time for one more question from 00:51:14.740 --> 00:51:17.160 align:start position:0% we have time for one more question from the<00:51:14.829> audience<00:51:14.920> okay<00:51:15.549> a<00:51:15.910> two<00:51:16.240> second<00:51:16.690> answer<00:51:16.900> is 00:51:17.160 --> 00:51:17.170 align:start position:0% the audience okay a two second answer is 00:51:17.170 --> 00:51:20.069 align:start position:0% the audience okay a two second answer is just<00:51:17.619> as<00:51:17.859> well<00:51:18.339> as<00:51:18.400> against<00:51:18.880> more<00:51:19.119> stable<00:51:19.750> you 00:51:20.069 --> 00:51:20.079 align:start position:0% just as well as against more stable you 00:51:20.079 --> 00:51:25.620 align:start position:0% just as well as against more stable you stop<00:51:21.029> you<00:51:22.029> cap<00:51:22.270> off<00:51:23.069> EVM<00:51:24.069> one<00:51:24.369> and<00:51:24.670> say<00:51:24.940> it's<00:51:25.210> a 00:51:25.620 --> 00:51:25.630 align:start position:0% stop you cap off EVM one and say it's a 00:51:25.630 --> 00:51:27.029 align:start position:0% stop you cap off EVM one and say it's a tail<00:51:26.020> on<00:51:26.049> the<00:51:26.200> main<00:51:26.319> chain<00:51:26.559> and<00:51:26.770> you<00:51:26.829> have<00:51:26.920> to 00:51:27.029 --> 00:51:27.039 align:start position:0% tail on the main chain and you have to 00:51:27.039 --> 00:51:29.670 align:start position:0% tail on the main chain and you have to support<00:51:27.309> it<00:51:27.539> it<00:51:28.539> has<00:51:28.779> to<00:51:28.960> be<00:51:29.079> supported 00:51:29.670 --> 00:51:29.680 align:start position:0% support it it has to be supported 00:51:29.680 --> 00:51:32.160 align:start position:0% support it it has to be supported forever<00:51:30.099> I'm<00:51:30.640> saying<00:51:31.029> it<00:51:31.210> can<00:51:31.359> be<00:51:31.510> supported 00:51:32.160 --> 00:51:32.170 align:start position:0% forever I'm saying it can be supported 00:51:32.170 --> 00:51:34.079 align:start position:0% forever I'm saying it can be supported with<00:51:32.380> the<00:51:32.529> compiler<00:51:33.220> and<00:51:33.400> you<00:51:33.849> stopped 00:51:34.079 --> 00:51:34.089 align:start position:0% with the compiler and you stopped 00:51:34.089 --> 00:51:36.710 align:start position:0% with the compiler and you stopped evolving<00:51:34.480> it<00:51:34.930> so<00:51:35.170> you<00:51:35.260> don't<00:51:35.470> keep<00:51:36.099> creating 00:51:36.710 --> 00:51:36.720 align:start position:0% evolving it so you don't keep creating 00:51:36.720 --> 00:51:40.529 align:start position:0% evolving it so you don't keep creating backwards<00:51:37.720> compel<00:51:38.079> it<00:51:38.260> okay<00:51:39.119> so<00:51:40.119> we've<00:51:40.240> a<00:51:40.299> next 00:51:40.529 --> 00:51:40.539 align:start position:0% backwards compel it okay so we've a next 00:51:40.539 --> 00:51:43.710 align:start position:0% backwards compel it okay so we've a next panel<00:51:40.839> at<00:51:41.140> some<00:51:41.289> point<00:51:42.450> thank<00:51:43.450> you<00:51:43.539> guys<00:51:43.690> very 00:51:43.710 --> 00:51:43.720 align:start position:0% panel at some point thank you guys very 00:51:43.720 --> 00:51:52.800 align:start position:0% panel at some point thank you guys very much<00:51:43.960> thanks<00:51:44.319> for<00:51:44.410> listening 00:51:52.800 --> 00:51:52.810 align:start position:0% 00:51:52.810 --> 00:51:54.870 align:start position:0% you