WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.110 align:start position:0% [Music] 00:00:09.110 --> 00:00:09.120 align:start position:0% [Music] 00:00:09.120 --> 00:00:09.749 align:start position:0% [Music] the 00:00:09.749 --> 00:00:09.759 align:start position:0% the 00:00:09.759 --> 00:00:12.870 align:start position:0% the introduction<00:00:10.759> yeah<00:00:11.559> uh<00:00:12.040> in<00:00:12.200> this<00:00:12.400> talk<00:00:12.799> I 00:00:12.870 --> 00:00:12.880 align:start position:0% introduction yeah uh in this talk I 00:00:12.880 --> 00:00:14.990 align:start position:0% introduction yeah uh in this talk I would<00:00:13.080> like<00:00:13.280> to<00:00:13.480> talk<00:00:13.759> about<00:00:14.080> endgame<00:00:14.799> the 00:00:14.990 --> 00:00:15.000 align:start position:0% would like to talk about endgame the 00:00:15.000 --> 00:00:18.910 align:start position:0% would like to talk about endgame the last<00:00:15.280> step<00:00:15.839> of<00:00:16.720> uh<00:00:16.920> Aran<00:00:17.480> project<00:00:18.359> it<00:00:18.520> started 00:00:18.910 --> 00:00:18.920 align:start position:0% last step of uh Aran project it started 00:00:18.920 --> 00:00:21.790 align:start position:0% last step of uh Aran project it started few<00:00:19.119> years<00:00:19.359> ago<00:00:20.160> and<00:00:20.439> I<00:00:20.560> think<00:00:20.880> I<00:00:21.039> found<00:00:21.439> the 00:00:21.790 --> 00:00:21.800 align:start position:0% few years ago and I think I found the 00:00:21.800 --> 00:00:25.550 align:start position:0% few years ago and I think I found the solution<00:00:22.279> that's<00:00:22.480> going<00:00:22.680> to<00:00:23.039> last<00:00:23.640> for<00:00:23.800> a 00:00:25.550 --> 00:00:25.560 align:start position:0% solution that's going to last for a 00:00:25.560 --> 00:00:29.509 align:start position:0% solution that's going to last for a while<00:00:26.560> uh<00:00:26.840> before<00:00:27.240> that<00:00:28.240> let's<00:00:28.640> talk<00:00:29.080> about 00:00:29.509 --> 00:00:29.519 align:start position:0% while uh before that let's talk about 00:00:29.519 --> 00:00:31.550 align:start position:0% while uh before that let's talk about history 00:00:31.550 --> 00:00:31.560 align:start position:0% history 00:00:31.560 --> 00:00:33.830 align:start position:0% history uh<00:00:31.720> and<00:00:31.960> basic<00:00:32.360> evolution<00:00:32.719> of<00:00:32.840> the<00:00:33.040> project<00:00:33.399> it 00:00:33.830 --> 00:00:33.840 align:start position:0% uh and basic evolution of the project it 00:00:33.840 --> 00:00:37.229 align:start position:0% uh and basic evolution of the project it started<00:00:34.840> in 00:00:37.229 --> 00:00:37.239 align:start position:0% started in 00:00:37.239 --> 00:00:40.590 align:start position:0% started in 2021<00:00:38.239> I<00:00:38.360> took<00:00:38.520> a<00:00:38.640> break<00:00:38.879> for<00:00:39.120> the<00:00:39.320> work<00:00:40.320> I 00:00:40.590 --> 00:00:40.600 align:start position:0% 2021 I took a break for the work I 00:00:40.600 --> 00:00:43.670 align:start position:0% 2021 I took a break for the work I basically<00:00:41.360> go<00:00:41.800> went<00:00:42.120> to<00:00:42.280> the<00:00:42.399> seaside<00:00:43.280> relaxed 00:00:43.670 --> 00:00:43.680 align:start position:0% basically go went to the seaside relaxed 00:00:43.680 --> 00:00:46.750 align:start position:0% basically go went to the seaside relaxed a<00:00:43.760> little<00:00:44.000> bit<00:00:44.520> and<00:00:44.719> after<00:00:45.000> I<00:00:45.200> came<00:00:45.520> back 00:00:46.750 --> 00:00:46.760 align:start position:0% a little bit and after I came back 00:00:46.760 --> 00:00:50.549 align:start position:0% a little bit and after I came back I<00:00:47.760> uh<00:00:47.960> I<00:00:48.160> did<00:00:49.120> basically<00:00:49.760> want<00:00:50.000> to<00:00:50.120> do<00:00:50.280> some 00:00:50.549 --> 00:00:50.559 align:start position:0% I uh I did basically want to do some 00:00:50.559 --> 00:00:52.549 align:start position:0% I uh I did basically want to do some project<00:00:51.000> that's<00:00:51.280> related<00:00:51.600> to<00:00:51.760> infrastructure 00:00:52.549 --> 00:00:52.559 align:start position:0% project that's related to infrastructure 00:00:52.559 --> 00:00:54.830 align:start position:0% project that's related to infrastructure wanted<00:00:52.800> to<00:00:52.920> build<00:00:53.160> something<00:00:53.399> that<00:00:53.559> use<00:00:54.000> evm 00:00:54.830 --> 00:00:54.840 align:start position:0% wanted to build something that use evm 00:00:54.840 --> 00:00:56.549 align:start position:0% wanted to build something that use evm and<00:00:54.920> I<00:00:55.039> started<00:00:55.320> researching<00:00:55.960> what's 00:00:56.549 --> 00:00:56.559 align:start position:0% and I started researching what's 00:00:56.559 --> 00:01:00.069 align:start position:0% and I started researching what's basically<00:00:57.520> on<00:00:57.840> the<00:00:58.399> market<00:00:59.399> and<00:00:59.559> it<00:00:59.640> was<00:00:59.800> like 00:01:00.069 --> 00:01:00.079 align:start position:0% basically on the market and it was like 00:01:00.079 --> 00:01:03.869 align:start position:0% basically on the market and it was like treatings<00:01:01.039> open<00:01:01.359> ethereum<00:01:02.280> was<00:01:03.160> the<00:01:03.480> client 00:01:03.869 --> 00:01:03.879 align:start position:0% treatings open ethereum was the client 00:01:03.879 --> 00:01:06.830 align:start position:0% treatings open ethereum was the client that<00:01:04.000> I<00:01:04.119> worked<00:01:04.400> on<00:01:04.960> before<00:01:05.960> and<00:01:06.159> it<00:01:06.240> was<00:01:06.439> GP 00:01:06.830 --> 00:01:06.840 align:start position:0% that I worked on before and it was GP 00:01:06.840 --> 00:01:09.510 align:start position:0% that I worked on before and it was GP license<00:01:07.159> so<00:01:07.320> it<00:01:07.400> was<00:01:07.520> not<00:01:07.920> suitable<00:01:08.920> uh<00:01:09.119> EV 00:01:09.510 --> 00:01:09.520 align:start position:0% license so it was not suitable uh EV 00:01:09.520 --> 00:01:13.030 align:start position:0% license so it was not suitable uh EV modm<00:01:09.920> was<00:01:10.119> the<00:01:10.240> new<00:01:10.640> one<00:01:11.640> it<00:01:11.920> has<00:01:12.159> some<00:01:12.880> it's 00:01:13.030 --> 00:01:13.040 align:start position:0% modm was the new one it has some it's 00:01:13.040 --> 00:01:15.550 align:start position:0% modm was the new one it has some it's built<00:01:13.360> by<00:01:13.720> ex<00:01:14.000> colleague<00:01:14.680> it<00:01:14.880> has<00:01:15.040> some 00:01:15.550 --> 00:01:15.560 align:start position:0% built by ex colleague it has some 00:01:15.560 --> 00:01:18.910 align:start position:0% built by ex colleague it has some experimental<00:01:16.560> and<00:01:17.119> exotic<00:01:17.640> crust<00:01:18.520> night 00:01:18.910 --> 00:01:18.920 align:start position:0% experimental and exotic crust night 00:01:18.920 --> 00:01:21.190 align:start position:0% experimental and exotic crust night features<00:01:19.840> and<00:01:19.960> it<00:01:20.119> was<00:01:20.360> like<00:01:20.680> just 00:01:21.190 --> 00:01:21.200 align:start position:0% features and it was like just 00:01:21.200 --> 00:01:23.749 align:start position:0% features and it was like just interpreter<00:01:22.200> so<00:01:22.479> that<00:01:22.680> sense<00:01:23.079> it<00:01:23.200> was<00:01:23.400> not 00:01:23.749 --> 00:01:23.759 align:start position:0% interpreter so that sense it was not 00:01:23.759 --> 00:01:26.990 align:start position:0% interpreter so that sense it was not enough<00:01:24.040> for<00:01:24.200> me<00:01:25.200> SP<00:01:25.720> VM<00:01:26.320> I<00:01:26.400> was<00:01:26.680> most 00:01:26.990 --> 00:01:27.000 align:start position:0% enough for me SP VM I was most 00:01:27.000 --> 00:01:30.149 align:start position:0% enough for me SP VM I was most interested<00:01:27.400> in<00:01:27.560> it<00:01:28.520> and 00:01:30.149 --> 00:01:30.159 align:start position:0% interested in it and 00:01:30.159 --> 00:01:33.230 align:start position:0% interested in it and it<00:01:30.280> was<00:01:30.439> old<00:01:30.720> the<00:01:30.960> project<00:01:31.560> old<00:01:31.799> the<00:01:32.079> evm<00:01:33.079> but 00:01:33.230 --> 00:01:33.240 align:start position:0% it was old the project old the evm but 00:01:33.240 --> 00:01:35.429 align:start position:0% it was old the project old the evm but it<00:01:33.360> was<00:01:33.479> not<00:01:33.680> that<00:01:33.880> maintain<00:01:34.720> uh<00:01:34.840> it<00:01:34.920> was<00:01:35.159> hard 00:01:35.429 --> 00:01:35.439 align:start position:0% it was not that maintain uh it was hard 00:01:35.439 --> 00:01:37.429 align:start position:0% it was not that maintain uh it was hard to<00:01:35.640> use<00:01:35.840> it<00:01:36.240> and<00:01:36.399> if<00:01:36.479> you<00:01:36.600> want<00:01:36.799> to<00:01:36.960> do 00:01:37.429 --> 00:01:37.439 align:start position:0% to use it and if you want to do 00:01:37.439 --> 00:01:40.749 align:start position:0% to use it and if you want to do inspection<00:01:38.439> tracing<00:01:39.360> you<00:01:39.520> need<00:01:39.720> to<00:01:40.000> basically 00:01:40.749 --> 00:01:40.759 align:start position:0% inspection tracing you need to basically 00:01:40.759 --> 00:01:44.270 align:start position:0% inspection tracing you need to basically build<00:01:41.040> it<00:01:41.360> in<00:01:41.640> some<00:01:42.399> different<00:01:43.040> way<00:01:44.040> and 00:01:44.270 --> 00:01:44.280 align:start position:0% build it in some different way and 00:01:44.280 --> 00:01:46.510 align:start position:0% build it in some different way and that's<00:01:44.560> very<00:01:44.840> hard<00:01:45.040> to 00:01:46.510 --> 00:01:46.520 align:start position:0% that's very hard to 00:01:46.520 --> 00:01:51.469 align:start position:0% that's very hard to use<00:01:47.680> so<00:01:48.680> after<00:01:49.280> making<00:01:49.880> PR<00:01:50.320> to<00:01:50.479> the<00:01:50.640> sputnic<00:01:51.200> to 00:01:51.469 --> 00:01:51.479 align:start position:0% use so after making PR to the sputnic to 00:01:51.479 --> 00:01:55.429 align:start position:0% use so after making PR to the sputnic to add<00:01:51.799> some<00:01:52.439> generics<00:01:53.159> on<00:01:53.439> the<00:01:53.680> instruction 00:01:55.429 --> 00:01:55.439 align:start position:0% add some generics on the instruction 00:01:55.439 --> 00:01:59.149 align:start position:0% add some generics on the instruction set<00:01:56.439> uh<00:01:56.799> basically<00:01:57.439> after<00:01:57.759> two<00:01:58.039> weeks<00:01:58.399> of<00:01:58.840> no 00:01:59.149 --> 00:01:59.159 align:start position:0% set uh basically after two weeks of no 00:01:59.159 --> 00:02:02.469 align:start position:0% set uh basically after two weeks of no response<00:01:59.920> nothing<00:02:00.880> and<00:02:01.439> seeing<00:02:01.840> the<00:02:02.039> project 00:02:02.469 --> 00:02:02.479 align:start position:0% response nothing and seeing the project 00:02:02.479 --> 00:02:06.350 align:start position:0% response nothing and seeing the project not<00:02:03.000> moving<00:02:03.399> anywhere<00:02:04.360> I<00:02:04.479> closed<00:02:04.840> that<00:02:05.039> PR<00:02:05.799> and 00:02:06.350 --> 00:02:06.360 align:start position:0% not moving anywhere I closed that PR and 00:02:06.360 --> 00:02:09.790 align:start position:0% not moving anywhere I closed that PR and made<00:02:06.640> my<00:02:06.759> own<00:02:07.079> rvm<00:02:07.960> in<00:02:08.039> the<00:02:08.200> month<00:02:08.520> I<00:02:08.679> had<00:02:08.959> some 00:02:09.790 --> 00:02:09.800 align:start position:0% made my own rvm in the month I had some 00:02:09.800 --> 00:02:14.030 align:start position:0% made my own rvm in the month I had some initial<00:02:10.800> initial<00:02:11.720> code<00:02:12.160> that<00:02:12.360> can<00:02:12.560> be<00:02:12.720> run<00:02:13.640> is 00:02:14.030 --> 00:02:14.040 align:start position:0% initial initial code that can be run is 00:02:14.040 --> 00:02:16.509 align:start position:0% initial initial code that can be run is PR<00:02:14.400> if<00:02:14.519> you<00:02:14.640> want<00:02:14.800> to<00:02:14.920> look<00:02:15.080> at 00:02:16.509 --> 00:02:16.519 align:start position:0% PR if you want to look at 00:02:16.519 --> 00:02:20.309 align:start position:0% PR if you want to look at that<00:02:17.519> by<00:02:17.680> the<00:02:17.800> end<00:02:17.959> of<00:02:18.599> 2021<00:02:19.599> I<00:02:19.760> supported<00:02:20.200> the 00:02:20.309 --> 00:02:20.319 align:start position:0% that by the end of 2021 I supported the 00:02:20.319 --> 00:02:23.470 align:start position:0% that by the end of 2021 I supported the latest<00:02:20.840> Forks<00:02:21.840> uh<00:02:22.000> state<00:02:22.440> for<00:02:22.800> test<00:02:23.160> state 00:02:23.470 --> 00:02:23.480 align:start position:0% latest Forks uh state for test state 00:02:23.480 --> 00:02:26.509 align:start position:0% latest Forks uh state for test state test<00:02:23.720> for<00:02:24.160> passing<00:02:25.160> it<00:02:25.319> supported<00:02:25.760> to<00:02:25.959> pre 00:02:26.509 --> 00:02:26.519 align:start position:0% test for passing it supported to pre 00:02:26.519 --> 00:02:28.869 align:start position:0% test for passing it supported to pre compil<00:02:27.519> and<00:02:27.800> the<00:02:27.920> most<00:02:28.120> important<00:02:28.480> interface 00:02:28.869 --> 00:02:28.879 align:start position:0% compil and the most important interface 00:02:28.879 --> 00:02:31.470 align:start position:0% compil and the most important interface was<00:02:29.040> simple<00:02:30.239> I<00:02:30.360> wanted<00:02:30.680> to<00:02:30.920> have<00:02:31.160> for<00:02:31.360> my 00:02:31.470 --> 00:02:31.480 align:start position:0% was simple I wanted to have for my 00:02:31.480 --> 00:02:33.470 align:start position:0% was simple I wanted to have for my experience<00:02:31.959> open<00:02:32.200> ethereum<00:02:32.800> I<00:02:32.920> want<00:02:33.160> to<00:02:33.319> have 00:02:33.470 --> 00:02:33.480 align:start position:0% experience open ethereum I want to have 00:02:33.480 --> 00:02:36.270 align:start position:0% experience open ethereum I want to have evm<00:02:34.080> where<00:02:34.239> you<00:02:34.360> set<00:02:34.680> all<00:02:34.840> the<00:02:35.080> data<00:02:35.599> and<00:02:35.840> say 00:02:36.270 --> 00:02:36.280 align:start position:0% evm where you set all the data and say 00:02:36.280 --> 00:02:38.670 align:start position:0% evm where you set all the data and say transact<00:02:37.120> and<00:02:37.280> then<00:02:37.560> basically<00:02:38.040> it<00:02:38.280> gives<00:02:38.480> you 00:02:38.670 --> 00:02:38.680 align:start position:0% transact and then basically it gives you 00:02:38.680 --> 00:02:40.030 align:start position:0% transact and then basically it gives you the<00:02:38.800> output<00:02:39.120> of<00:02:39.280> that 00:02:40.030 --> 00:02:40.040 align:start position:0% the output of that 00:02:40.040 --> 00:02:44.149 align:start position:0% the output of that execution<00:02:41.040> the<00:02:41.200> database<00:02:41.680> trait<00:02:42.360> was<00:02:43.159> the 00:02:44.149 --> 00:02:44.159 align:start position:0% execution the database trait was the 00:02:44.159 --> 00:02:46.110 align:start position:0% execution the database trait was the obstruction<00:02:44.920> that<00:02:45.120> allows<00:02:45.480> you<00:02:45.640> run<00:02:45.959> time 00:02:46.110 --> 00:02:46.120 align:start position:0% obstruction that allows you run time 00:02:46.120 --> 00:02:49.350 align:start position:0% obstruction that allows you run time fetching<00:02:46.560> of<00:02:46.879> account<00:02:47.599> storage<00:02:48.599> environment 00:02:49.350 --> 00:02:49.360 align:start position:0% fetching of account storage environment 00:02:49.360 --> 00:02:51.149 align:start position:0% fetching of account storage environment was<00:02:49.599> the<00:02:49.760> way<00:02:50.040> how<00:02:50.159> you<00:02:50.319> set<00:02:50.640> transaction 00:02:51.149 --> 00:02:51.159 align:start position:0% was the way how you set transaction 00:02:51.159 --> 00:02:53.910 align:start position:0% was the way how you set transaction block<00:02:52.000> configuration<00:02:52.680> everything<00:02:53.000> around<00:02:53.280> it 00:02:53.910 --> 00:02:53.920 align:start position:0% block configuration everything around it 00:02:53.920 --> 00:02:57.750 align:start position:0% block configuration everything around it and<00:02:54.239> inspector<00:02:55.239> was<00:02:55.640> the<00:02:56.599> good<00:02:56.920> abstraction 00:02:57.750 --> 00:02:57.760 align:start position:0% and inspector was the good abstraction 00:02:57.760 --> 00:02:59.910 align:start position:0% and inspector was the good abstraction very<00:02:58.000> powerful<00:02:58.480> one<00:02:58.760> that<00:02:58.920> allows<00:02:59.280> you<00:02:59.519> run 00:02:59.910 --> 00:02:59.920 align:start position:0% very powerful one that allows you run 00:02:59.920 --> 00:03:03.070 align:start position:0% very powerful one that allows you run time<00:03:00.120> inspection<00:03:00.720> of<00:03:01.040> the<00:03:01.680> your<00:03:01.959> evm<00:03:02.680> when<00:03:02.879> you 00:03:03.070 --> 00:03:03.080 align:start position:0% time inspection of the your evm when you 00:03:03.080 --> 00:03:05.270 align:start position:0% time inspection of the your evm when you it<00:03:03.480> it's 00:03:05.270 --> 00:03:05.280 align:start position:0% it it's 00:03:05.280 --> 00:03:09.309 align:start position:0% it it's run<00:03:06.280> get<00:03:06.560> it's<00:03:07.239> this<00:03:07.560> PR<00:03:08.239> it<00:03:08.360> was<00:03:08.599> optimized 00:03:09.309 --> 00:03:09.319 align:start position:0% run get it's this PR it was optimized 00:03:09.319 --> 00:03:12.070 align:start position:0% run get it's this PR it was optimized few<00:03:09.599> times<00:03:09.920> but<00:03:10.080> this<00:03:10.319> PR<00:03:10.680> was<00:03:10.920> most<00:03:11.200> impactful 00:03:12.070 --> 00:03:12.080 align:start position:0% few times but this PR was most impactful 00:03:12.080 --> 00:03:15.550 align:start position:0% few times but this PR was most impactful it<00:03:12.560> basically<00:03:13.200> forx<00:03:14.120> the<00:03:14.360> the 00:03:15.550 --> 00:03:15.560 align:start position:0% it basically forx the the 00:03:15.560 --> 00:03:18.390 align:start position:0% it basically forx the the performance<00:03:16.560> uh<00:03:16.680> it<00:03:16.799> was<00:03:16.959> no<00:03:17.200> STD<00:03:17.720> from<00:03:17.879> the 00:03:18.390 --> 00:03:18.400 align:start position:0% performance uh it was no STD from the 00:03:18.400 --> 00:03:23.750 align:start position:0% performance uh it was no STD from the start<00:03:19.400> uh<00:03:20.400> IDE<00:03:20.879> idea<00:03:21.319> was<00:03:21.519> to<00:03:21.720> use<00:03:22.000> it<00:03:22.280> in 00:03:23.750 --> 00:03:23.760 align:start position:0% start uh IDE idea was to use it in 00:03:23.760 --> 00:03:28.149 align:start position:0% start uh IDE idea was to use it in JavaScript<00:03:24.760> or<00:03:25.319> vas<00:03:26.120> it<00:03:26.200> was<00:03:26.440> M<00:03:26.760> MIT<00:03:27.200> license 00:03:28.149 --> 00:03:28.159 align:start position:0% JavaScript or vas it was M MIT license 00:03:28.159 --> 00:03:30.789 align:start position:0% JavaScript or vas it was M MIT license and<00:03:28.560> by<00:03:29.200> that<00:03:29.439> year<00:03:29.920> basically<00:03:30.319> jumped<00:03:30.640> to 00:03:30.789 --> 00:03:30.799 align:start position:0% and by that year basically jumped to 00:03:30.799 --> 00:03:34.509 align:start position:0% and by that year basically jumped to another<00:03:31.159> project<00:03:31.519> and<00:03:31.720> rvm<00:03:32.239> became<00:03:32.480> my 00:03:34.509 --> 00:03:34.519 align:start position:0% another project and rvm became my 00:03:34.519 --> 00:03:38.990 align:start position:0% another project and rvm became my hobby<00:03:35.519> first<00:03:35.879> adopters<00:03:36.720> came<00:03:37.360> next<00:03:37.879> year<00:03:38.879> uh 00:03:38.990 --> 00:03:39.000 align:start position:0% hobby first adopters came next year uh 00:03:39.000 --> 00:03:41.789 align:start position:0% hobby first adopters came next year uh fundry<00:03:39.560> was<00:03:39.720> the<00:03:39.840> biggest<00:03:40.159> one<00:03:40.519> at<00:03:40.720> the<00:03:40.840> first 00:03:41.789 --> 00:03:41.799 align:start position:0% fundry was the biggest one at the first 00:03:41.799 --> 00:03:45.429 align:start position:0% fundry was the biggest one at the first one<00:03:42.799> uh<00:03:43.120> the<00:03:43.280> way<00:03:43.560> how<00:03:43.799> I<00:03:43.920> met<00:03:44.200> giio<00:03:44.920> was<00:03:45.200> he 00:03:45.429 --> 00:03:45.439 align:start position:0% one uh the way how I met giio was he 00:03:45.439 --> 00:03:48.390 align:start position:0% one uh the way how I met giio was he tweeted<00:03:46.040> if<00:03:46.239> there<00:03:46.360> is<00:03:46.640> any<00:03:47.159> EVMS<00:03:47.799> out<00:03:48.040> there 00:03:48.390 --> 00:03:48.400 align:start position:0% tweeted if there is any EVMS out there 00:03:48.400 --> 00:03:51.030 align:start position:0% tweeted if there is any EVMS out there and<00:03:48.560> I<00:03:48.799> responded<00:03:49.360> on<00:03:49.519> the<00:03:49.680> Tweet<00:03:50.200> hey<00:03:50.480> freshly 00:03:51.030 --> 00:03:51.040 align:start position:0% and I responded on the Tweet hey freshly 00:03:51.040 --> 00:03:53.350 align:start position:0% and I responded on the Tweet hey freshly back<00:03:51.280> if<00:03:51.360> you're<00:03:51.599> interested<00:03:52.560> and<00:03:52.720> he<00:03:52.879> was<00:03:53.200> in 00:03:53.350 --> 00:03:53.360 align:start position:0% back if you're interested and he was in 00:03:53.360 --> 00:03:56.910 align:start position:0% back if you're interested and he was in the<00:03:53.480> minutes<00:03:53.879> my<00:03:54.120> DMs<00:03:54.920> that's<00:03:55.599> georgeos<00:03:56.599> he's 00:03:56.910 --> 00:03:56.920 align:start position:0% the minutes my DMs that's georgeos he's 00:03:56.920 --> 00:03:59.949 align:start position:0% the minutes my DMs that's georgeos he's basically<00:03:57.400> amazing<00:03:57.799> in<00:03:57.959> that<00:03:58.280> sense 00:03:59.949 --> 00:03:59.959 align:start position:0% basically amazing in that sense 00:03:59.959 --> 00:04:02.190 align:start position:0% basically amazing in that sense uh<00:04:00.159> they<00:04:00.360> started<00:04:00.799> integrated<00:04:01.360> a<00:04:01.480> few<00:04:01.720> months 00:04:02.190 --> 00:04:02.200 align:start position:0% uh they started integrated a few months 00:04:02.200 --> 00:04:04.869 align:start position:0% uh they started integrated a few months I<00:04:02.319> think<00:04:02.799> the<00:04:02.920> Oliver<00:04:03.560> did<00:04:03.799> the<00:04:03.959> first 00:04:04.869 --> 00:04:04.879 align:start position:0% I think the Oliver did the first 00:04:04.879 --> 00:04:07.110 align:start position:0% I think the Oliver did the first integration<00:04:05.879> uh<00:04:06.200> five<00:04:06.480> months<00:04:06.760> after<00:04:07.000> the 00:04:07.110 --> 00:04:07.120 align:start position:0% integration uh five months after the 00:04:07.120 --> 00:04:09.589 align:start position:0% integration uh five months after the start<00:04:07.400> that<00:04:07.560> was<00:04:07.799> like<00:04:08.040> March 00:04:09.589 --> 00:04:09.599 align:start position:0% start that was like March 00:04:09.599 --> 00:04:12.270 align:start position:0% start that was like March 2022<00:04:10.599> uh<00:04:10.799> hardhead<00:04:11.360> started<00:04:11.760> integrating<00:04:12.120> the 00:04:12.270 --> 00:04:12.280 align:start position:0% 2022 uh hardhead started integrating the 00:04:12.280 --> 00:04:16.069 align:start position:0% 2022 uh hardhead started integrating the r<00:04:12.599> backand<00:04:13.480> they<00:04:14.000> published<00:04:14.400> the<00:04:15.159> this<00:04:15.319> year 00:04:16.069 --> 00:04:16.079 align:start position:0% r backand they published the this year 00:04:16.079 --> 00:04:18.670 align:start position:0% r backand they published the this year Builder<00:04:16.479> sures<00:04:16.959> was<00:04:17.280> one<00:04:17.479> of<00:04:17.600> the<00:04:17.799> big<00:04:18.519> uh 00:04:18.670 --> 00:04:18.680 align:start position:0% Builder sures was one of the big uh 00:04:18.680 --> 00:04:23.189 align:start position:0% Builder sures was one of the big uh users<00:04:19.600> of<00:04:19.880> the<00:04:20.359> CL<00:04:20.759> of<00:04:20.959> the<00:04:21.639> library<00:04:22.639> and<00:04:23.000> they 00:04:23.189 --> 00:04:23.199 align:start position:0% users of the CL of the library and they 00:04:23.199 --> 00:04:25.469 align:start position:0% users of the CL of the library and they would<00:04:23.560> the<00:04:23.759> first<00:04:24.120> one<00:04:24.479> they<00:04:24.639> sync<00:04:25.160> from<00:04:25.320> the 00:04:25.469 --> 00:04:25.479 align:start position:0% would the first one they sync from the 00:04:25.479 --> 00:04:28.990 align:start position:0% would the first one they sync from the Genesis<00:04:26.000> to<00:04:26.240> the<00:04:26.680> tip<00:04:27.040> of<00:04:27.280> the<00:04:27.639> main<00:04:27.960> net<00:04:28.880> and 00:04:28.990 --> 00:04:29.000 align:start position:0% Genesis to the tip of the main net and 00:04:29.000 --> 00:04:30.510 align:start position:0% Genesis to the tip of the main net and it<00:04:29.080> was<00:04:29.240> very<00:04:29.360> nice<00:04:29.560> to<00:04:29.720> to<00:04:29.800> hear<00:04:30.120> hey<00:04:30.320> we<00:04:30.440> are 00:04:30.510 --> 00:04:30.520 align:start position:0% it was very nice to to hear hey we are 00:04:30.520 --> 00:04:32.950 align:start position:0% it was very nice to to hear hey we are thinking<00:04:30.919> everything<00:04:31.199> is 00:04:32.950 --> 00:04:32.960 align:start position:0% thinking everything is 00:04:32.960 --> 00:04:36.070 align:start position:0% thinking everything is fine<00:04:33.960> by<00:04:34.120> the<00:04:34.199> end<00:04:34.400> of<00:04:34.520> 2022<00:04:35.320> all<00:04:35.520> Forks<00:04:35.919> was 00:04:36.070 --> 00:04:36.080 align:start position:0% fine by the end of 2022 all Forks was 00:04:36.080 --> 00:04:38.510 align:start position:0% fine by the end of 2022 all Forks was supported<00:04:36.680> optimization<00:04:37.280> was<00:04:37.440> done<00:04:37.880> our<00:04:38.160> RV 00:04:38.510 --> 00:04:38.520 align:start position:0% supported optimization was done our RV 00:04:38.520 --> 00:04:41.270 align:start position:0% supported optimization was done our RV MGS<00:04:39.160> was<00:04:39.720> supported<00:04:40.240> but<00:04:40.440> removed<00:04:40.919> by<00:04:41.039> the<00:04:41.120> end 00:04:41.270 --> 00:04:41.280 align:start position:0% MGS was supported but removed by the end 00:04:41.280 --> 00:04:43.629 align:start position:0% MGS was supported but removed by the end of<00:04:41.400> the<00:04:41.520> year<00:04:41.800> there<00:04:41.919> is<00:04:42.080> no<00:04:42.320> traction<00:04:43.320> a<00:04:43.440> few 00:04:43.629 --> 00:04:43.639 align:start position:0% of the year there is no traction a few 00:04:43.639 --> 00:04:45.510 align:start position:0% of the year there is no traction a few more<00:04:43.800> optimization<00:04:44.320> was<00:04:44.520> done<00:04:45.120> and<00:04:45.280> most 00:04:45.510 --> 00:04:45.520 align:start position:0% more optimization was done and most 00:04:45.520 --> 00:04:48.909 align:start position:0% more optimization was done and most importantly<00:04:46.160> R<00:04:46.720> the<00:04:46.919> client<00:04:47.759> started<00:04:48.320> to<00:04:48.680> be 00:04:48.909 --> 00:04:48.919 align:start position:0% importantly R the client started to be 00:04:48.919 --> 00:04:51.990 align:start position:0% importantly R the client started to be made<00:04:49.320> October<00:04:49.960> 2022<00:04:50.960> at<00:04:51.240> that<00:04:51.440> point<00:04:51.639> of<00:04:51.800> time 00:04:51.990 --> 00:04:52.000 align:start position:0% made October 2022 at that point of time 00:04:52.000 --> 00:04:54.469 align:start position:0% made October 2022 at that point of time I<00:04:52.120> join<00:04:52.440> Paradigm<00:04:52.880> to<00:04:53.000> work<00:04:53.199> on<00:04:53.320> the<00:04:53.479> client<00:04:54.320> I 00:04:54.469 --> 00:04:54.479 align:start position:0% I join Paradigm to work on the client I 00:04:54.479 --> 00:04:57.629 align:start position:0% I join Paradigm to work on the client I think<00:04:54.720> I<00:04:54.919> had<00:04:55.199> H<00:04:55.960> from<00:04:56.320> the<00:04:56.600> my<00:04:56.840> open<00:04:57.160> etherium 00:04:57.629 --> 00:04:57.639 align:start position:0% think I had H from the my open etherium 00:04:57.639 --> 00:04:59.990 align:start position:0% think I had H from the my open etherium times 00:04:59.990 --> 00:05:00.000 align:start position:0% times 00:05:00.000 --> 00:05:03.350 align:start position:0% times second<00:05:00.400> year<00:05:00.919> and<00:05:01.120> R<00:05:01.720> are<00:05:02.039> mostly<00:05:02.840> basically 00:05:03.350 --> 00:05:03.360 align:start position:0% second year and R are mostly basically 00:05:03.360 --> 00:05:06.110 align:start position:0% second year and R are mostly basically focused<00:05:03.960> on<00:05:04.520> the<00:05:04.720> client 00:05:06.110 --> 00:05:06.120 align:start position:0% focused on the client 00:05:06.120 --> 00:05:09.189 align:start position:0% focused on the client implementation<00:05:07.120> uh<00:05:07.520> we<00:05:07.720> needed<00:05:08.039> to<00:05:08.919> make 00:05:09.189 --> 00:05:09.199 align:start position:0% implementation uh we needed to make 00:05:09.199 --> 00:05:12.070 align:start position:0% implementation uh we needed to make something<00:05:09.600> stable<00:05:10.600> and<00:05:10.960> we<00:05:11.240> did<00:05:11.479> it<00:05:11.759> very 00:05:12.070 --> 00:05:12.080 align:start position:0% something stable and we did it very 00:05:12.080 --> 00:05:15.029 align:start position:0% something stable and we did it very fastly<00:05:12.639> team<00:05:12.880> was<00:05:13.120> amazing<00:05:14.039> I<00:05:14.240> plan<00:05:14.560> to<00:05:14.680> stay 00:05:15.029 --> 00:05:15.039 align:start position:0% fastly team was amazing I plan to stay 00:05:15.039 --> 00:05:17.270 align:start position:0% fastly team was amazing I plan to stay there<00:05:15.360> just<00:05:15.520> for<00:05:15.600> a<00:05:15.720> few<00:05:15.919> months<00:05:16.479> but<00:05:17.080> I'm 00:05:17.270 --> 00:05:17.280 align:start position:0% there just for a few months but I'm 00:05:17.280 --> 00:05:19.950 align:start position:0% there just for a few months but I'm still<00:05:17.600> there<00:05:18.199> now<00:05:18.440> in<00:05:18.600> inaka<00:05:19.440> but<00:05:19.639> did<00:05:19.800> the 00:05:19.950 --> 00:05:19.960 align:start position:0% still there now in inaka but did the 00:05:19.960 --> 00:05:21.070 align:start position:0% still there now in inaka but did the very<00:05:20.160> same 00:05:21.070 --> 00:05:21.080 align:start position:0% very same 00:05:21.080 --> 00:05:24.590 align:start position:0% very same team<00:05:22.080> shanka<00:05:22.479> and<00:05:22.600> kakum<00:05:22.919> were<00:05:23.120> added<00:05:23.960> and 00:05:24.590 --> 00:05:24.600 align:start position:0% team shanka and kakum were added and 00:05:24.600 --> 00:05:30.870 align:start position:0% team shanka and kakum were added and time<00:05:24.919> moved<00:05:25.560> on<00:05:26.560> this<00:05:27.000> year<00:05:28.000> R<00:05:28.440> 01<00:05:29.160> was<00:05:29.360> relased 00:05:30.870 --> 00:05:30.880 align:start position:0% time moved on this year R 01 was relased 00:05:30.880 --> 00:05:33.550 align:start position:0% time moved on this year R 01 was relased big<00:05:31.199> stability<00:05:32.000> Improvement<00:05:33.000> U<00:05:33.240> it<00:05:33.360> was 00:05:33.550 --> 00:05:33.560 align:start position:0% big stability Improvement U it was 00:05:33.560 --> 00:05:37.830 align:start position:0% big stability Improvement U it was audited<00:05:34.560> it<00:05:34.759> was<00:05:35.800> the<00:05:36.800> the<00:05:36.960> people<00:05:37.280> like<00:05:37.479> it 00:05:37.830 --> 00:05:37.840 align:start position:0% audited it was the the people like it 00:05:37.840 --> 00:05:40.790 align:start position:0% audited it was the the people like it people<00:05:38.160> wanted<00:05:38.479> to<00:05:38.600> use<00:05:38.800> it<00:05:39.560> it<00:05:39.759> was<00:05:40.160> it<00:05:40.440> is 00:05:40.790 --> 00:05:40.800 align:start position:0% people wanted to use it it was it is 00:05:40.800 --> 00:05:44.230 align:start position:0% people wanted to use it it was it is amazing<00:05:41.800> RM<00:05:42.560> on<00:05:42.720> its<00:05:42.880> own<00:05:43.160> hit<00:05:43.520> it<00:05:43.880> own 00:05:44.230 --> 00:05:44.240 align:start position:0% amazing RM on its own hit it own 00:05:44.240 --> 00:05:46.870 align:start position:0% amazing RM on its own hit it own Milestone<00:05:44.840> it<00:05:45.000> got<00:05:45.440> audited<00:05:46.440> uh<00:05:46.560> it<00:05:46.680> was 00:05:46.870 --> 00:05:46.880 align:start position:0% Milestone it got audited uh it was 00:05:46.880 --> 00:05:49.469 align:start position:0% Milestone it got audited uh it was Community<00:05:47.240> Driven<00:05:47.680> by<00:05:47.840> the<00:05:47.919> six<00:05:48.280> company<00:05:49.280> and 00:05:49.469 --> 00:05:49.479 align:start position:0% Community Driven by the six company and 00:05:49.479 --> 00:05:52.270 align:start position:0% Community Driven by the six company and it's<00:05:49.680> B<00:05:50.000> guy<00:05:50.199> gido<00:05:51.120> basically<00:05:51.680> the<00:05:51.880> guy<00:05:52.120> that 00:05:52.270 --> 00:05:52.280 align:start position:0% it's B guy gido basically the guy that 00:05:52.280 --> 00:05:55.670 align:start position:0% it's B guy gido basically the guy that finds<00:05:52.639> a<00:05:52.800> lot<00:05:53.000> of<00:05:53.240> evm<00:05:54.039> bugs<00:05:55.039> uh<00:05:55.199> there's<00:05:55.440> blog 00:05:55.670 --> 00:05:55.680 align:start position:0% finds a lot of evm bugs uh there's blog 00:05:55.680 --> 00:05:57.670 align:start position:0% finds a lot of evm bugs uh there's blog post<00:05:55.880> if<00:05:56.000> you<00:05:56.039> want<00:05:56.199> to<00:05:56.319> hear<00:05:56.639> more<00:05:57.400> uh<00:05:57.479> you 00:05:57.670 --> 00:05:57.680 align:start position:0% post if you want to hear more uh you 00:05:57.680 --> 00:05:59.870 align:start position:0% post if you want to hear more uh you have<00:05:57.880> got<00:05:58.039> supported<00:05:58.960> and<00:05:59.199> start<00:05:59.479> of<00:05:59.639> of<00:05:59.759> the 00:05:59.870 --> 00:05:59.880 align:start position:0% have got supported and start of of the 00:05:59.880 --> 00:06:04.350 align:start position:0% have got supported and start of of the year<00:06:00.600> uh<00:06:00.800> Z<00:06:01.080> KVM<00:06:01.840> become<00:06:02.280> a 00:06:04.350 --> 00:06:04.360 align:start position:0% year uh Z KVM become a 00:06:04.360 --> 00:06:08.550 align:start position:0% year uh Z KVM become a thing<00:06:05.360> this<00:06:05.600> year<00:06:06.319> I<00:06:06.680> could<00:06:07.000> claim<00:06:08.000> I<00:06:08.120> feel 00:06:08.550 --> 00:06:08.560 align:start position:0% thing this year I could claim I feel 00:06:08.560 --> 00:06:11.830 align:start position:0% thing this year I could claim I feel that's<00:06:08.759> okay<00:06:09.080> to<00:06:09.199> claim<00:06:09.599> that<00:06:10.560> the<00:06:10.759> rvm<00:06:11.319> become 00:06:11.830 --> 00:06:11.840 align:start position:0% that's okay to claim that the rvm become 00:06:11.840 --> 00:06:14.270 align:start position:0% that's okay to claim that the rvm become the<00:06:12.160> became<00:06:12.680> the<00:06:12.800> most<00:06:13.120> popular<00:06:13.440> evm<00:06:13.919> Library 00:06:14.270 --> 00:06:14.280 align:start position:0% the became the most popular evm Library 00:06:14.280 --> 00:06:17.550 align:start position:0% the became the most popular evm Library out<00:06:14.520> there<00:06:15.280> and<00:06:15.440> it's<00:06:16.319> become<00:06:16.840> the<00:06:17.080> critical 00:06:17.550 --> 00:06:17.560 align:start position:0% out there and it's become the critical 00:06:17.560 --> 00:06:20.469 align:start position:0% out there and it's become the critical component<00:06:18.199> of<00:06:18.520> etherum<00:06:19.160> ecosystem<00:06:20.160> there<00:06:20.280> is 00:06:20.469 --> 00:06:20.479 align:start position:0% component of etherum ecosystem there is 00:06:20.479 --> 00:06:23.390 align:start position:0% component of etherum ecosystem there is few<00:06:20.800> types<00:06:21.319> of<00:06:21.560> the<00:06:21.759> rvm<00:06:22.280> users<00:06:22.880> that<00:06:23.080> I<00:06:23.240> can 00:06:23.390 --> 00:06:23.400 align:start position:0% few types of the rvm users that I can 00:06:23.400 --> 00:06:26.430 align:start position:0% few types of the rvm users that I can see<00:06:24.160> they're<00:06:24.440> basically<00:06:24.919> clients<00:06:25.280> and<00:06:25.479> chain 00:06:26.430 --> 00:06:26.440 align:start position:0% see they're basically clients and chain 00:06:26.440 --> 00:06:30.110 align:start position:0% see they're basically clients and chain R<00:06:27.160> first<00:06:28.160> hel<00:06:28.919> like<00:06:29.080> client 00:06:30.110 --> 00:06:30.120 align:start position:0% R first hel like client 00:06:30.120 --> 00:06:33.909 align:start position:0% R first hel like client SC<00:06:31.120> uh<00:06:31.720> as<00:06:32.000> the<00:06:32.400> execution<00:06:33.000> clients<00:06:33.520> there<00:06:33.639> is 00:06:33.909 --> 00:06:33.919 align:start position:0% SC uh as the execution clients there is 00:06:33.919 --> 00:06:36.710 align:start position:0% SC uh as the execution clients there is different<00:06:34.240> chains<00:06:34.759> Optimus<00:06:35.240> scroll<00:06:36.199> binance 00:06:36.710 --> 00:06:36.720 align:start position:0% different chains Optimus scroll binance 00:06:36.720 --> 00:06:39.830 align:start position:0% different chains Optimus scroll binance polygon<00:06:37.280> they<00:06:37.560> all<00:06:37.960> all<00:06:38.199> interested<00:06:38.639> to<00:06:38.919> have 00:06:39.830 --> 00:06:39.840 align:start position:0% polygon they all all interested to have 00:06:39.840 --> 00:06:43.670 align:start position:0% polygon they all all interested to have uh<00:06:40.400> RM<00:06:41.400> in<00:06:41.560> their<00:06:41.880> code<00:06:42.440> or<00:06:42.720> basically<00:06:43.319> in<00:06:43.479> this 00:06:43.670 --> 00:06:43.680 align:start position:0% uh RM in their code or basically in this 00:06:43.680 --> 00:06:47.909 align:start position:0% uh RM in their code or basically in this sense<00:06:44.080> R<00:06:44.880> and<00:06:45.880> in<00:06:46.080> that<00:06:46.240> connection<00:06:46.800> rvm<00:06:47.800> the 00:06:47.909 --> 00:06:47.919 align:start position:0% sense R and in that connection rvm the 00:06:47.919 --> 00:06:50.469 align:start position:0% sense R and in that connection rvm the tooling<00:06:48.440> both<00:06:48.680> The<00:06:48.800> Foundry<00:06:49.400> hardhead<00:06:50.120> are 00:06:50.469 --> 00:06:50.479 align:start position:0% tooling both The Foundry hardhead are 00:06:50.479 --> 00:06:53.990 align:start position:0% tooling both The Foundry hardhead are basically<00:06:50.840> using<00:06:51.479> RM<00:06:52.479> Builder<00:06:52.880> searches<00:06:53.880> uh 00:06:53.990 --> 00:06:54.000 align:start position:0% basically using RM Builder searches uh 00:06:54.000 --> 00:06:55.909 align:start position:0% basically using RM Builder searches uh they're<00:06:54.160> a<00:06:54.240> little<00:06:54.440> bit<00:06:54.680> private<00:06:55.280> but<00:06:55.599> always 00:06:55.909 --> 00:06:55.919 align:start position:0% they're a little bit private but always 00:06:55.919 --> 00:07:00.749 align:start position:0% they're a little bit private but always in<00:06:56.120> my<00:06:56.720> DMs<00:06:57.639> are<00:06:57.960> the<00:06:58.080> big<00:06:58.319> users<00:06:58.680> of<00:06:58.840> it<00:06:59.759> and<00:06:59.960> Z 00:07:00.749 --> 00:07:00.759 align:start position:0% in my DMs are the big users of it and Z 00:07:00.759 --> 00:07:05.390 align:start position:0% in my DMs are the big users of it and Z KVM<00:07:01.759> uh<00:07:02.039> basically<00:07:02.800> it<00:07:03.039> became<00:07:03.919> the<00:07:04.400> standard 00:07:05.390 --> 00:07:05.400 align:start position:0% KVM uh basically it became the standard 00:07:05.400 --> 00:07:07.749 align:start position:0% KVM uh basically it became the standard Library<00:07:05.879> that's<00:07:06.080> used<00:07:06.319> in<00:07:06.479> that<00:07:06.639> field<00:07:07.639> there 00:07:07.749 --> 00:07:07.759 align:start position:0% Library that's used in that field there 00:07:07.759 --> 00:07:12.110 align:start position:0% Library that's used in that field there is<00:07:07.960> even<00:07:08.599> a<00:07:08.960> grant<00:07:09.440> by<00:07:09.879> EF<00:07:10.800> uh<00:07:10.919> Foundation<00:07:11.639> that 00:07:12.110 --> 00:07:12.120 align:start position:0% is even a grant by EF uh Foundation that 00:07:12.120 --> 00:07:15.430 align:start position:0% is even a grant by EF uh Foundation that basically<00:07:13.120> uh<00:07:13.319> targets<00:07:13.840> RM<00:07:14.680> formal 00:07:15.430 --> 00:07:15.440 align:start position:0% basically uh targets RM formal 00:07:15.440 --> 00:07:17.869 align:start position:0% basically uh targets RM formal verification<00:07:16.440> with<00:07:16.639> the<00:07:16.759> usage<00:07:17.120> of<00:07:17.360> the<00:07:17.520> risk 00:07:17.869 --> 00:07:17.879 align:start position:0% verification with the usage of the risk 00:07:17.879 --> 00:07:19.350 align:start position:0% verification with the usage of the risk 5<00:07:18.280> and<00:07:18.479> Z 00:07:19.350 --> 00:07:19.360 align:start position:0% 5 and Z 00:07:19.360 --> 00:07:22.309 align:start position:0% 5 and Z kvms<00:07:20.360> this<00:07:20.560> all<00:07:20.879> affected<00:07:21.560> the<00:07:21.720> future<00:07:22.120> of 00:07:22.309 --> 00:07:22.319 align:start position:0% kvms this all affected the future of 00:07:22.319 --> 00:07:24.909 align:start position:0% kvms this all affected the future of Aran<00:07:22.919> how<00:07:23.160> I<00:07:23.319> look<00:07:23.479> at 00:07:24.909 --> 00:07:24.919 align:start position:0% Aran how I look at 00:07:24.919 --> 00:07:28.150 align:start position:0% Aran how I look at it<00:07:25.919> so<00:07:26.479> the 00:07:28.150 --> 00:07:28.160 align:start position:0% it so the 00:07:28.160 --> 00:07:31.189 align:start position:0% it so the problems<00:07:29.160> first<00:07:29.639> problem<00:07:30.160> how<00:07:30.360> to<00:07:30.520> do<00:07:30.759> AIP 00:07:31.189 --> 00:07:31.199 align:start position:0% problems first problem how to do AIP 00:07:31.199 --> 00:07:33.869 align:start position:0% problems first problem how to do AIP testing<00:07:31.919> how<00:07:32.080> to<00:07:32.280> do<00:07:32.599> how<00:07:32.759> to<00:07:32.960> allow<00:07:33.440> AIP 00:07:33.869 --> 00:07:33.879 align:start position:0% testing how to do how to allow AIP 00:07:33.879 --> 00:07:36.189 align:start position:0% testing how to do how to allow AIP Champions<00:07:34.479> to<00:07:34.759> come<00:07:34.960> to<00:07:35.160> the<00:07:35.319> code<00:07:35.599> base 00:07:36.189 --> 00:07:36.199 align:start position:0% Champions to come to the code base 00:07:36.199 --> 00:07:38.309 align:start position:0% Champions to come to the code base improve<00:07:36.680> their<00:07:36.919> thing<00:07:37.319> implemented<00:07:37.919> tested 00:07:38.309 --> 00:07:38.319 align:start position:0% improve their thing implemented tested 00:07:38.319 --> 00:07:42.469 align:start position:0% improve their thing implemented tested in<00:07:38.440> The<00:07:38.599> Foundry<00:07:39.039> if<00:07:39.520> needed<00:07:40.520> and 00:07:42.469 --> 00:07:42.479 align:start position:0% in The Foundry if needed and 00:07:42.479 --> 00:07:46.110 align:start position:0% in The Foundry if needed and basically<00:07:43.479> do<00:07:43.960> their<00:07:44.159> own<00:07:44.479> thing<00:07:45.240> and<00:07:45.639> do 00:07:46.110 --> 00:07:46.120 align:start position:0% basically do their own thing and do 00:07:46.120 --> 00:07:48.909 align:start position:0% basically do their own thing and do their<00:07:46.479> basically<00:07:46.840> on<00:07:47.000> their<00:07:47.159> own<00:07:47.720> time<00:07:48.720> the 00:07:48.909 --> 00:07:48.919 align:start position:0% their basically on their own time the 00:07:48.919 --> 00:07:51.230 align:start position:0% their basically on their own time the one<00:07:49.120> of<00:07:49.280> the<00:07:49.400> example<00:07:49.800> is<00:07:50.000> trans<00:07:50.520> storage<00:07:51.159> I 00:07:51.230 --> 00:07:51.240 align:start position:0% one of the example is trans storage I 00:07:51.240 --> 00:07:53.710 align:start position:0% one of the example is trans storage I want<00:07:51.440> to<00:07:51.599> just<00:07:51.879> moved<00:07:52.159> on<00:07:52.319> that<00:07:52.560> pad<00:07:53.319> uh<00:07:53.560> in 00:07:53.710 --> 00:07:53.720 align:start position:0% want to just moved on that pad uh in 00:07:53.720 --> 00:07:56.110 align:start position:0% want to just moved on that pad uh in July<00:07:54.000> 24<00:07:54.479> I<00:07:54.599> got<00:07:54.800> issue<00:07:55.080> in<00:07:55.240> GitHub<00:07:55.840> hey<00:07:56.000> can 00:07:56.110 --> 00:07:56.120 align:start position:0% July 24 I got issue in GitHub hey can 00:07:56.120 --> 00:07:59.510 align:start position:0% July 24 I got issue in GitHub hey can you<00:07:56.240> implement<00:07:56.879> that<00:07:57.879> that<00:07:58.039> was<00:07:58.319> one<00:07:58.479> of<00:07:58.639> the<00:07:58.919> a 00:07:59.510 --> 00:07:59.520 align:start position:0% you implement that that was one of the a 00:07:59.520 --> 00:08:01.670 align:start position:0% you implement that that was one of the a iions<00:07:59.879> that<00:08:00.039> wanted<00:08:00.400> this<00:08:00.639> included<00:08:01.000> in<00:08:01.120> Aran 00:08:01.670 --> 00:08:01.680 align:start position:0% iions that wanted this included in Aran 00:08:01.680 --> 00:08:03.589 align:start position:0% iions that wanted this included in Aran for<00:08:01.960> him<00:08:02.120> to<00:08:02.280> test<00:08:02.520> it<00:08:02.639> in<00:08:02.759> The 00:08:03.589 --> 00:08:03.599 align:start position:0% for him to test it in The 00:08:03.599 --> 00:08:06.390 align:start position:0% for him to test it in The Foundry<00:08:04.599> y<00:08:04.840> it<00:08:04.960> was<00:08:05.159> not<00:08:05.360> included<00:08:05.840> in<00:08:06.000> the<00:08:06.159> any 00:08:06.390 --> 00:08:06.400 align:start position:0% Foundry y it was not included in the any 00:08:06.400 --> 00:08:08.629 align:start position:0% Foundry y it was not included in the any hard<00:08:06.639> Fork<00:08:07.000> there<00:08:07.120> is<00:08:07.280> no<00:08:07.560> even<00:08:07.840> notion<00:08:08.319> for<00:08:08.479> it 00:08:08.629 --> 00:08:08.639 align:start position:0% hard Fork there is no even notion for it 00:08:08.639 --> 00:08:12.749 align:start position:0% hard Fork there is no even notion for it to<00:08:08.759> be<00:08:09.240> included<00:08:10.240> so<00:08:10.599> that<00:08:10.800> was<00:08:11.280> mostly<00:08:11.759> it<00:08:12.560> few 00:08:12.749 --> 00:08:12.759 align:start position:0% to be included so that was mostly it few 00:08:12.759 --> 00:08:13.749 align:start position:0% to be included so that was mostly it few months 00:08:13.749 --> 00:08:13.759 align:start position:0% months 00:08:13.759 --> 00:08:18.869 align:start position:0% months after<00:08:14.759> uh<00:08:14.960> a<00:08:15.400> got<00:08:16.000> CFI<00:08:17.000> so<00:08:17.840> it<00:08:18.240> potentially<00:08:18.759> can 00:08:18.869 --> 00:08:18.879 align:start position:0% after uh a got CFI so it potentially can 00:08:18.879 --> 00:08:21.270 align:start position:0% after uh a got CFI so it potentially can be<00:08:18.960> included<00:08:19.240> in<00:08:19.400> shangai<00:08:20.400> but<00:08:20.599> either<00:08:20.919> way 00:08:21.270 --> 00:08:21.280 align:start position:0% be included in shangai but either way 00:08:21.280 --> 00:08:23.270 align:start position:0% be included in shangai but either way there<00:08:21.360> is<00:08:21.520> not<00:08:21.759> like<00:08:22.080> strong 00:08:23.270 --> 00:08:23.280 align:start position:0% there is not like strong 00:08:23.280 --> 00:08:26.149 align:start position:0% there is not like strong guarantee<00:08:24.280> shangai<00:08:24.960> happened<00:08:25.599> yep<00:08:25.879> he<00:08:26.000> was 00:08:26.149 --> 00:08:26.159 align:start position:0% guarantee shangai happened yep he was 00:08:26.159 --> 00:08:27.149 align:start position:0% guarantee shangai happened yep he was not 00:08:27.149 --> 00:08:27.159 align:start position:0% not 00:08:27.159 --> 00:08:30.110 align:start position:0% not inside<00:08:28.159> next<00:08:28.560> har<00:08:28.919> Fork 00:08:30.110 --> 00:08:30.120 align:start position:0% inside next har Fork 00:08:30.120 --> 00:08:34.550 align:start position:0% inside next har Fork Cancun<00:08:31.120> July<00:08:32.080> PR<00:08:32.519> was<00:08:32.680> made<00:08:33.000> for<00:08:33.279> that<00:08:33.560> AIP 00:08:34.550 --> 00:08:34.560 align:start position:0% Cancun July PR was made for that AIP 00:08:34.560 --> 00:08:37.670 align:start position:0% Cancun July PR was made for that AIP August<00:08:35.000> it<00:08:35.120> was<00:08:35.279> merged<00:08:35.800> in<00:08:36.000> March<00:08:36.760> the<00:08:37.200> AIP 00:08:37.670 --> 00:08:37.680 align:start position:0% August it was merged in March the AIP 00:08:37.680 --> 00:08:40.750 align:start position:0% August it was merged in March the AIP landed<00:08:38.080> on<00:08:38.640> minute<00:08:39.640> approximately<00:08:40.399> four 00:08:40.750 --> 00:08:40.760 align:start position:0% landed on minute approximately four 00:08:40.760 --> 00:08:43.509 align:start position:0% landed on minute approximately four months<00:08:41.200> before<00:08:41.599> that<00:08:41.919> a<00:08:42.640> should<00:08:42.959> be<00:08:43.159> made 00:08:43.509 --> 00:08:43.519 align:start position:0% months before that a should be made 00:08:43.519 --> 00:08:45.670 align:start position:0% months before that a should be made inside<00:08:43.919> the<00:08:44.120> clients<00:08:44.640> for<00:08:44.839> the<00:08:45.000> testing<00:08:45.519> for 00:08:45.670 --> 00:08:45.680 align:start position:0% inside the clients for the testing for 00:08:45.680 --> 00:08:48.750 align:start position:0% inside the clients for the testing for the<00:08:45.800> dam<00:08:46.080> Nets<00:08:46.560> and<00:08:46.880> for<00:08:47.240> test<00:08:47.560> Nets<00:08:47.920> at<00:08:48.040> the 00:08:48.750 --> 00:08:48.760 align:start position:0% the dam Nets and for test Nets at the 00:08:48.760 --> 00:08:51.790 align:start position:0% the dam Nets and for test Nets at the end<00:08:49.760> another<00:08:50.120> example<00:08:50.519> was 00:08:51.790 --> 00:08:51.800 align:start position:0% end another example was 00:08:51.800 --> 00:08:54.550 align:start position:0% end another example was 3074<00:08:52.800> and<00:08:52.959> I<00:08:53.080> want<00:08:53.240> to<00:08:53.360> say<00:08:53.720> all<00:08:53.959> the<00:08:54.160> requests 00:08:54.550 --> 00:08:54.560 align:start position:0% 3074 and I want to say all the requests 00:08:54.560 --> 00:08:56.710 align:start position:0% 3074 and I want to say all the requests that<00:08:54.760> Champions<00:08:55.279> made<00:08:55.560> were<00:08:55.760> reasonable<00:08:56.560> it 00:08:56.710 --> 00:08:56.720 align:start position:0% that Champions made were reasonable it 00:08:56.720 --> 00:08:59.710 align:start position:0% that Champions made were reasonable it is<00:08:57.000> from<00:08:57.240> their<00:08:57.519> point<00:08:57.720> of<00:08:58.279> view<00:08:59.279> but<00:08:59.440> but<00:08:59.600> the 00:08:59.710 --> 00:08:59.720 align:start position:0% is from their point of view but but the 00:08:59.720 --> 00:09:01.750 align:start position:0% is from their point of view but but the question<00:09:00.000> that<00:09:00.120> I<00:09:00.279> had<00:09:00.480> is<00:09:00.720> like<00:09:01.399> should<00:09:01.600> I 00:09:01.750 --> 00:09:01.760 align:start position:0% question that I had is like should I 00:09:01.760 --> 00:09:03.590 align:start position:0% question that I had is like should I have<00:09:01.920> started<00:09:02.320> working<00:09:02.600> on<00:09:02.760> I<00:09:03.160> right<00:09:03.320> away 00:09:03.590 --> 00:09:03.600 align:start position:0% have started working on I right away 00:09:03.600 --> 00:09:05.509 align:start position:0% have started working on I right away when<00:09:03.760> the<00:09:03.880> first<00:09:04.200> request<00:09:04.600> come<00:09:05.279> it's<00:09:05.440> a 00:09:05.509 --> 00:09:05.519 align:start position:0% when the first request come it's a 00:09:05.519 --> 00:09:06.750 align:start position:0% when the first request come it's a little<00:09:05.720> bit<00:09:05.880> silly<00:09:06.240> because<00:09:06.480> I<00:09:06.560> have 00:09:06.750 --> 00:09:06.760 align:start position:0% little bit silly because I have 00:09:06.760 --> 00:09:09.069 align:start position:0% little bit silly because I have different<00:09:07.000> priorities<00:09:07.560> I<00:09:07.680> cannot<00:09:08.000> do 00:09:09.069 --> 00:09:09.079 align:start position:0% different priorities I cannot do 00:09:09.079 --> 00:09:12.670 align:start position:0% different priorities I cannot do everything<00:09:10.079> should<00:09:10.399> I<00:09:10.839> just<00:09:11.079> merge<00:09:11.519> PR<00:09:12.480> when 00:09:12.670 --> 00:09:12.680 align:start position:0% everything should I just merge PR when 00:09:12.680 --> 00:09:15.790 align:start position:0% everything should I just merge PR when it<00:09:12.839> was<00:09:13.360> made<00:09:14.360> the<00:09:14.720> question<00:09:15.120> with<00:09:15.279> that<00:09:15.560> is 00:09:15.790 --> 00:09:15.800 align:start position:0% it was made the question with that is 00:09:15.800 --> 00:09:17.630 align:start position:0% it was made the question with that is who<00:09:15.959> is<00:09:16.079> going<00:09:16.240> to<00:09:16.360> do<00:09:16.519> maintenance<00:09:17.320> who<00:09:17.480> is 00:09:17.630 --> 00:09:17.640 align:start position:0% who is going to do maintenance who is 00:09:17.640 --> 00:09:21.069 align:start position:0% who is going to do maintenance who is going<00:09:17.839> to<00:09:18.040> remove<00:09:18.360> it<00:09:18.680> if<00:09:18.959> the<00:09:19.560> AIP<00:09:20.240> was<00:09:20.440> not 00:09:21.069 --> 00:09:21.079 align:start position:0% going to remove it if the AIP was not 00:09:21.079 --> 00:09:24.710 align:start position:0% going to remove it if the AIP was not included<00:09:22.079> do<00:09:22.240> I<00:09:22.399> do<00:09:22.519> it<00:09:22.640> for<00:09:22.880> every<00:09:23.519> iip<00:09:24.519> that 00:09:24.710 --> 00:09:24.720 align:start position:0% included do I do it for every iip that 00:09:24.720 --> 00:09:27.470 align:start position:0% included do I do it for every iip that would<00:09:24.920> be<00:09:25.360> a<00:09:25.560> lot<00:09:25.800> of<00:09:26.040> unnecessary 00:09:27.470 --> 00:09:27.480 align:start position:0% would be a lot of unnecessary 00:09:27.480 --> 00:09:30.470 align:start position:0% would be a lot of unnecessary code<00:09:28.480> and<00:09:28.920> in<00:09:29.040> the<00:09:29.160> end<00:09:29.480> who<00:09:29.600> is<00:09:30.040> going<00:09:30.279> to 00:09:30.470 --> 00:09:30.480 align:start position:0% code and in the end who is going to 00:09:30.480 --> 00:09:32.590 align:start position:0% code and in the end who is going to maintain<00:09:30.959> all<00:09:31.120> of 00:09:32.590 --> 00:09:32.600 align:start position:0% maintain all of 00:09:32.600 --> 00:09:35.750 align:start position:0% maintain all of that<00:09:33.600> second<00:09:34.120> problem<00:09:35.120> with<00:09:35.320> the 00:09:35.750 --> 00:09:35.760 align:start position:0% that second problem with the 00:09:35.760 --> 00:09:37.590 align:start position:0% that second problem with the maintainance 00:09:37.590 --> 00:09:37.600 align:start position:0% maintainance 00:09:37.600 --> 00:09:42.230 align:start position:0% maintainance is<00:09:38.600> uh<00:09:38.760> how<00:09:39.000> to<00:09:39.240> add<00:09:40.240> testing<00:09:41.200> Dev<00:09:42.040> uh 00:09:42.230 --> 00:09:42.240 align:start position:0% is uh how to add testing Dev uh 00:09:42.240 --> 00:09:44.990 align:start position:0% is uh how to add testing Dev uh experimental<00:09:42.880> features<00:09:43.880> one<00:09:44.040> of<00:09:44.279> those<00:09:44.680> I 00:09:44.990 --> 00:09:45.000 align:start position:0% experimental features one of those I 00:09:45.000 --> 00:09:47.949 align:start position:0% experimental features one of those I always<00:09:45.360> try<00:09:45.560> to<00:09:45.800> facilitate<00:09:46.600> and<00:09:46.800> enable<00:09:47.680> a 00:09:47.949 --> 00:09:47.959 align:start position:0% always try to facilitate and enable a 00:09:47.959 --> 00:09:49.990 align:start position:0% always try to facilitate and enable a big<00:09:48.240> project<00:09:48.600> that<00:09:48.760> depend<00:09:49.079> of<00:09:49.240> our<00:09:49.399> evm<00:09:49.839> to 00:09:49.990 --> 00:09:50.000 align:start position:0% big project that depend of our evm to 00:09:50.000 --> 00:09:53.150 align:start position:0% big project that depend of our evm to give<00:09:50.120> it<00:09:50.399> support<00:09:50.920> to<00:09:51.120> give<00:09:51.399> a<00:09:52.000> to<00:09:52.560> to<00:09:52.720> make 00:09:53.150 --> 00:09:53.160 align:start position:0% give it support to give a to to make 00:09:53.160 --> 00:09:55.990 align:start position:0% give it support to give a to to make Tech<00:09:53.440> functionality<00:09:54.240> happen<00:09:55.240> sometimes<00:09:55.720> that 00:09:55.990 --> 00:09:56.000 align:start position:0% Tech functionality happen sometimes that 00:09:56.000 --> 00:09:59.870 align:start position:0% Tech functionality happen sometimes that there's<00:09:56.680> like<00:09:57.279> features<00:09:58.279> U<00:09:58.480> rust<00:09:58.920> features 00:09:59.870 --> 00:09:59.880 align:start position:0% there's like features U rust features 00:09:59.880 --> 00:10:03.350 align:start position:0% there's like features U rust features that<00:10:00.240> basically<00:10:01.000> enable<00:10:01.519> those<00:10:01.920> things<00:10:02.920> as 00:10:03.350 --> 00:10:03.360 align:start position:0% that basically enable those things as 00:10:03.360 --> 00:10:06.190 align:start position:0% that basically enable those things as configuration<00:10:04.360> but<00:10:04.880> sometimes<00:10:05.360> if<00:10:05.720> this<00:10:05.880> is 00:10:06.190 --> 00:10:06.200 align:start position:0% configuration but sometimes if this is 00:10:06.200 --> 00:10:10.750 align:start position:0% configuration but sometimes if this is only<00:10:06.600> the<00:10:06.959> evm<00:10:07.640> project<00:10:08.600> simple<00:10:09.000> evm<00:10:09.680> project 00:10:10.750 --> 00:10:10.760 align:start position:0% only the evm project simple evm project 00:10:10.760 --> 00:10:14.269 align:start position:0% only the evm project simple evm project RMC<00:10:11.760> r55<00:10:12.640> integration<00:10:13.200> that<00:10:13.720> require 00:10:14.269 --> 00:10:14.279 align:start position:0% RMC r55 integration that require 00:10:14.279 --> 00:10:16.230 align:start position:0% RMC r55 integration that require different<00:10:14.680> execution<00:10:15.279> environment<00:10:15.920> would 00:10:16.230 --> 00:10:16.240 align:start position:0% different execution environment would 00:10:16.240 --> 00:10:17.269 align:start position:0% different execution environment would not<00:10:16.480> be 00:10:17.269 --> 00:10:17.279 align:start position:0% not be 00:10:17.279 --> 00:10:20.550 align:start position:0% not be possible<00:10:18.279> and<00:10:18.480> problem<00:10:18.880> three<00:10:19.640> is<00:10:20.120> chain 00:10:20.550 --> 00:10:20.560 align:start position:0% possible and problem three is chain 00:10:20.560 --> 00:10:23.110 align:start position:0% possible and problem three is chain support<00:10:21.560> most<00:10:21.800> of<00:10:22.120> chains<00:10:22.480> have<00:10:22.680> small 00:10:23.110 --> 00:10:23.120 align:start position:0% support most of chains have small 00:10:23.120 --> 00:10:26.350 align:start position:0% support most of chains have small difference<00:10:24.120> and<00:10:24.279> they're<00:10:24.560> not<00:10:24.920> like<00:10:25.720> uh<00:10:26.160> they 00:10:26.350 --> 00:10:26.360 align:start position:0% difference and they're not like uh they 00:10:26.360 --> 00:10:30.310 align:start position:0% difference and they're not like uh they don't<00:10:26.720> want<00:10:27.279> to<00:10:27.680> move<00:10:28.000> away<00:10:28.360> from<00:10:28.600> evm<00:10:29.320> a<00:10:29.440> lot 00:10:30.310 --> 00:10:30.320 align:start position:0% don't want to move away from evm a lot 00:10:30.320 --> 00:10:33.150 align:start position:0% don't want to move away from evm a lot they're<00:10:30.560> most<00:10:30.839> like<00:10:31.079> new<00:10:31.320> Chains<00:10:31.760> speec<00:10:32.440> hards 00:10:33.150 --> 00:10:33.160 align:start position:0% they're most like new Chains speec hards 00:10:33.160 --> 00:10:37.069 align:start position:0% they're most like new Chains speec hards new<00:10:33.480> transaction<00:10:34.120> types<00:10:34.959> maybe<00:10:35.760> few 00:10:37.069 --> 00:10:37.079 align:start position:0% new transaction types maybe few 00:10:37.079 --> 00:10:39.829 align:start position:0% new transaction types maybe few aips<00:10:38.079> but<00:10:38.240> in<00:10:38.360> general<00:10:38.720> they're<00:10:39.040> like<00:10:39.240> small 00:10:39.829 --> 00:10:39.839 align:start position:0% aips but in general they're like small 00:10:39.839 --> 00:10:43.030 align:start position:0% aips but in general they're like small difference<00:10:40.360> from<00:10:40.560> the<00:10:40.760> main<00:10:41.040> net<00:10:42.040> main<00:10:42.320> net 00:10:43.030 --> 00:10:43.040 align:start position:0% difference from the main net main net 00:10:43.040 --> 00:10:45.629 align:start position:0% difference from the main net main net evm<00:10:44.040> only<00:10:44.320> way<00:10:44.480> to<00:10:44.639> do<00:10:44.839> that<00:10:45.040> previously<00:10:45.560> it 00:10:45.629 --> 00:10:45.639 align:start position:0% evm only way to do that previously it 00:10:45.639 --> 00:10:48.750 align:start position:0% evm only way to do that previously it was<00:10:45.800> like<00:10:46.040> Fork<00:10:46.399> the<00:10:46.560> project<00:10:47.519> and<00:10:47.880> that 00:10:48.750 --> 00:10:48.760 align:start position:0% was like Fork the project and that 00:10:48.760 --> 00:10:51.670 align:start position:0% was like Fork the project and that brings<00:10:49.240> the<00:10:49.440> maintainance<00:10:50.040> issue<00:10:50.560> and<00:10:51.079> burden 00:10:51.670 --> 00:10:51.680 align:start position:0% brings the maintainance issue and burden 00:10:51.680 --> 00:10:53.910 align:start position:0% brings the maintainance issue and burden of<00:10:52.000> maintaining<00:10:52.800> to 00:10:53.910 --> 00:10:53.920 align:start position:0% of maintaining to 00:10:53.920 --> 00:10:58.870 align:start position:0% of maintaining to basically<00:10:55.399> repos<00:10:56.399> so<00:10:57.279> solution<00:10:57.680> for<00:10:57.920> all<00:10:58.240> that 00:10:58.870 --> 00:10:58.880 align:start position:0% basically repos so solution for all that 00:10:58.880 --> 00:11:02.269 align:start position:0% basically repos so solution for all that is<00:10:59.320> to<00:10:59.440> make<00:10:59.800> evm<00:11:00.360> framework<00:11:01.360> I<00:11:01.519> think<00:11:01.880> that's 00:11:02.269 --> 00:11:02.279 align:start position:0% is to make evm framework I think that's 00:11:02.279 --> 00:11:04.750 align:start position:0% is to make evm framework I think that's the<00:11:02.560> the<00:11:02.720> last<00:11:03.000> stage<00:11:03.320> of<00:11:03.480> our<00:11:03.760> evm<00:11:04.200> and<00:11:04.480> it's 00:11:04.750 --> 00:11:04.760 align:start position:0% the the last stage of our evm and it's 00:11:04.760 --> 00:11:05.750 align:start position:0% the the last stage of our evm and it's end 00:11:05.750 --> 00:11:05.760 align:start position:0% end 00:11:05.760 --> 00:11:08.949 align:start position:0% end game<00:11:06.760> what<00:11:06.880> do<00:11:06.959> you<00:11:07.079> mean<00:11:07.320> by<00:11:07.519> that<00:11:08.440> uh<00:11:08.639> let's 00:11:08.949 --> 00:11:08.959 align:start position:0% game what do you mean by that uh let's 00:11:08.959 --> 00:11:10.949 align:start position:0% game what do you mean by that uh let's make<00:11:09.360> the<00:11:09.519> code 00:11:10.949 --> 00:11:10.959 align:start position:0% make the code 00:11:10.959 --> 00:11:13.870 align:start position:0% make the code extensible<00:11:11.959> chain<00:11:12.480> can<00:11:12.680> use<00:11:13.040> RM<00:11:13.639> as<00:11:13.720> the 00:11:13.870 --> 00:11:13.880 align:start position:0% extensible chain can use RM as the 00:11:13.880 --> 00:11:16.230 align:start position:0% extensible chain can use RM as the library<00:11:14.600> override<00:11:15.120> the<00:11:15.279> functionality<00:11:16.079> that 00:11:16.230 --> 00:11:16.240 align:start position:0% library override the functionality that 00:11:16.240 --> 00:11:18.629 align:start position:0% library override the functionality that they<00:11:16.399> need<00:11:17.160> uh<00:11:17.360> add<00:11:17.639> NE<00:11:17.920> transaction<00:11:18.519> that 00:11:18.629 --> 00:11:18.639 align:start position:0% they need uh add NE transaction that 00:11:18.639 --> 00:11:21.949 align:start position:0% they need uh add NE transaction that they<00:11:18.800> need<00:11:19.680> and<00:11:19.959> just<00:11:20.160> uses<00:11:20.600> the<00:11:20.760> library<00:11:21.720> that 00:11:21.949 --> 00:11:21.959 align:start position:0% they need and just uses the library that 00:11:21.959 --> 00:11:24.750 align:start position:0% they need and just uses the library that makes<00:11:22.320> the<00:11:22.560> core<00:11:22.920> of<00:11:23.120> the<00:11:23.360> library<00:11:24.160> same 00:11:24.750 --> 00:11:24.760 align:start position:0% makes the core of the library same 00:11:24.760 --> 00:11:27.389 align:start position:0% makes the core of the library same across<00:11:25.120> all<00:11:25.320> the<00:11:25.639> chains<00:11:26.639> implementing<00:11:27.200> new 00:11:27.389 --> 00:11:27.399 align:start position:0% across all the chains implementing new 00:11:27.399 --> 00:11:29.949 align:start position:0% across all the chains implementing new aips<00:11:28.000> that<00:11:28.120> are<00:11:28.279> on<00:11:28.440> the<00:11:28.600> main<00:11:28.839> net<00:11:29.519> become 00:11:29.949 --> 00:11:29.959 align:start position:0% aips that are on the main net become 00:11:29.959 --> 00:11:32.710 align:start position:0% aips that are on the main net become easier<00:11:30.959> and<00:11:31.399> uh<00:11:31.600> all<00:11:31.800> the<00:11:31.920> chains<00:11:32.320> can<00:11:32.519> just 00:11:32.710 --> 00:11:32.720 align:start position:0% easier and uh all the chains can just 00:11:32.720 --> 00:11:34.190 align:start position:0% easier and uh all the chains can just reuse<00:11:33.120> the 00:11:34.190 --> 00:11:34.200 align:start position:0% reuse the 00:11:34.200 --> 00:11:38.110 align:start position:0% reuse the code<00:11:35.200> uh<00:11:35.360> tooling<00:11:35.800> can<00:11:36.000> create<00:11:36.639> their<00:11:36.880> own<00:11:37.800> Uh 00:11:38.110 --> 00:11:38.120 align:start position:0% code uh tooling can create their own Uh 00:11:38.120 --> 00:11:40.829 align:start position:0% code uh tooling can create their own Uh custom<00:11:38.720> way<00:11:39.000> to<00:11:39.200> inspect<00:11:39.880> maybe<00:11:40.440> they<00:11:40.600> need 00:11:40.829 --> 00:11:40.839 align:start position:0% custom way to inspect maybe they need 00:11:40.839 --> 00:11:43.710 align:start position:0% custom way to inspect maybe they need more<00:11:41.040> performance<00:11:41.560> way<00:11:42.560> maybe<00:11:42.839> they<00:11:43.000> need 00:11:43.710 --> 00:11:43.720 align:start position:0% more performance way maybe they need 00:11:43.720 --> 00:11:47.550 align:start position:0% more performance way maybe they need rvnc<00:11:44.680> needed<00:11:45.360> new<00:11:45.720> execution<00:11:46.440> environment<00:11:47.440> uh 00:11:47.550 --> 00:11:47.560 align:start position:0% rvnc needed new execution environment uh 00:11:47.560 --> 00:11:51.190 align:start position:0% rvnc needed new execution environment uh new<00:11:47.760> AP<00:11:48.200> can<00:11:48.320> be<00:11:48.480> implemented<00:11:49.160> and<00:11:49.360> tested 00:11:51.190 --> 00:11:51.200 align:start position:0% new AP can be implemented and tested 00:11:51.200 --> 00:11:54.389 align:start position:0% new AP can be implemented and tested separately<00:11:52.200> uh<00:11:52.720> and<00:11:53.279> for<00:11:53.440> example<00:11:54.040> this<00:11:54.160> is 00:11:54.389 --> 00:11:54.399 align:start position:0% separately uh and for example this is 00:11:54.399 --> 00:11:57.030 align:start position:0% separately uh and for example this is the<00:11:54.600> first<00:11:54.880> look<00:11:55.279> how<00:11:55.760> how 00:11:57.030 --> 00:11:57.040 align:start position:0% the first look how how 00:11:57.040 --> 00:12:00.030 align:start position:0% the first look how how basically<00:11:58.040> I<00:11:58.399> I'm<00:11:58.519> not<00:11:58.920> coming<00:11:59.399> to<00:11:59.519> the<00:11:59.639> code<00:11:59.920> a 00:12:00.030 --> 00:12:00.040 align:start position:0% basically I I'm not coming to the code a 00:12:00.040 --> 00:12:02.430 align:start position:0% basically I I'm not coming to the code a little<00:12:00.240> bit<00:12:00.600> but<00:12:01.000> yeah<00:12:01.240> the<00:12:01.399> main<00:12:01.920> inspector 00:12:02.430 --> 00:12:02.440 align:start position:0% little bit but yeah the main inspector 00:12:02.440 --> 00:12:04.790 align:start position:0% little bit but yeah the main inspector main<00:12:02.920> optimis<00:12:03.519> inspector<00:12:03.920> Optimus<00:12:04.519> you<00:12:04.600> will 00:12:04.790 --> 00:12:04.800 align:start position:0% main optimis inspector Optimus you will 00:12:04.800 --> 00:12:07.509 align:start position:0% main optimis inspector Optimus you will have<00:12:05.040> different<00:12:05.360> types<00:12:05.720> for<00:12:05.880> your<00:12:06.519> different 00:12:07.509 --> 00:12:07.519 align:start position:0% have different types for your different 00:12:07.519 --> 00:12:09.430 align:start position:0% have different types for your different evm<00:12:08.079> that<00:12:08.200> you 00:12:09.430 --> 00:12:09.440 align:start position:0% evm that you 00:12:09.440 --> 00:12:13.990 align:start position:0% evm that you need<00:12:10.440> idea<00:12:10.920> came<00:12:11.920> uh<00:12:12.519> initial<00:12:12.959> idea<00:12:13.480> came<00:12:13.760> few 00:12:13.990 --> 00:12:14.000 align:start position:0% need idea came uh initial idea came few 00:12:14.000 --> 00:12:17.069 align:start position:0% need idea came uh initial idea came few years<00:12:14.199> ago<00:12:14.800> I<00:12:14.920> looked<00:12:15.199> at<00:12:15.399> TV<00:12:15.720> and<00:12:15.920> bom<00:12:16.800> and 00:12:17.069 --> 00:12:17.079 align:start position:0% years ago I looked at TV and bom and 00:12:17.079 --> 00:12:21.069 align:start position:0% years ago I looked at TV and bom and they<00:12:17.279> had<00:12:17.560> like<00:12:17.800> array<00:12:18.279> of<00:12:19.000> functions<00:12:20.000> and<00:12:20.680> um 00:12:21.069 --> 00:12:21.079 align:start position:0% they had like array of functions and um 00:12:21.079 --> 00:12:24.550 align:start position:0% they had like array of functions and um array<00:12:21.399> of<00:12:21.639> functions<00:12:22.639> that<00:12:23.320> was<00:12:23.560> different<00:12:24.079> by 00:12:24.550 --> 00:12:24.560 align:start position:0% array of functions that was different by 00:12:24.560 --> 00:12:28.150 align:start position:0% array of functions that was different by Fork<00:12:25.560> so<00:12:26.240> my<00:12:26.399> first<00:12:26.680> idea<00:12:27.000> was<00:12:27.279> hey<00:12:27.560> can<00:12:27.720> we 00:12:28.150 --> 00:12:28.160 align:start position:0% Fork so my first idea was hey can we 00:12:28.160 --> 00:12:30.550 align:start position:0% Fork so my first idea was hey can we introduce<00:12:28.639> customers<00:12:29.160> struction<00:12:29.920> and<00:12:30.199> make 00:12:30.550 --> 00:12:30.560 align:start position:0% introduce customers struction and make 00:12:30.560 --> 00:12:35.110 align:start position:0% introduce customers struction and make it<00:12:31.519> like<00:12:32.519> allow<00:12:33.000> user<00:12:33.440> to<00:12:33.760> reimplement<00:12:34.560> or<00:12:34.839> add 00:12:35.110 --> 00:12:35.120 align:start position:0% it like allow user to reimplement or add 00:12:35.120 --> 00:12:37.750 align:start position:0% it like allow user to reimplement or add their<00:12:35.279> own<00:12:35.600> custom<00:12:35.959> instruction<00:12:36.959> that<00:12:37.320> idea 00:12:37.750 --> 00:12:37.760 align:start position:0% their own custom instruction that idea 00:12:37.760 --> 00:12:40.949 align:start position:0% their own custom instruction that idea expanded<00:12:38.760> so<00:12:39.000> it's<00:12:39.199> not<00:12:39.519> just<00:12:39.800> on<00:12:40.079> instruction 00:12:40.949 --> 00:12:40.959 align:start position:0% expanded so it's not just on instruction 00:12:40.959 --> 00:12:42.710 align:start position:0% expanded so it's not just on instruction but<00:12:41.199> on<00:12:41.560> full 00:12:42.710 --> 00:12:42.720 align:start position:0% but on full 00:12:42.720 --> 00:12:46.110 align:start position:0% but on full logic<00:12:43.720> and<00:12:44.000> that<00:12:44.279> full<00:12:44.639> logic<00:12:45.320> function 00:12:46.110 --> 00:12:46.120 align:start position:0% logic and that full logic function 00:12:46.120 --> 00:12:50.150 align:start position:0% logic and that full logic function overriding<00:12:47.120> was<00:12:47.360> the<00:12:47.560> Handler<00:12:48.279> from<00:12:48.639> the<00:12:49.040> last 00:12:50.150 --> 00:12:50.160 align:start position:0% overriding was the Handler from the last 00:12:50.160 --> 00:12:53.509 align:start position:0% overriding was the Handler from the last year<00:12:51.160> uh<00:12:51.399> I<00:12:51.519> think<00:12:51.680> it<00:12:51.839> was<00:12:52.079> very<00:12:52.360> great<00:12:52.680> idea 00:12:53.509 --> 00:12:53.519 align:start position:0% year uh I think it was very great idea 00:12:53.519 --> 00:12:56.110 align:start position:0% year uh I think it was very great idea but<00:12:53.800> implementation<00:12:54.600> wise<00:12:54.880> it<00:12:55.000> was<00:12:55.199> like<00:12:55.519> box 00:12:56.110 --> 00:12:56.120 align:start position:0% but implementation wise it was like box 00:12:56.120 --> 00:12:59.790 align:start position:0% but implementation wise it was like box or<00:12:57.120> pointer<00:12:57.519> or<00:12:57.720> function<00:12:58.240> that<00:12:58.399> was<00:12:58.639> not<00:12:59.399> uh 00:12:59.790 --> 00:12:59.800 align:start position:0% or pointer or function that was not uh 00:12:59.800 --> 00:13:02.949 align:start position:0% or pointer or function that was not uh the<00:13:00.000> greatest<00:13:00.519> and<00:13:00.800> more<00:13:01.040> flexible 00:13:02.949 --> 00:13:02.959 align:start position:0% the greatest and more flexible 00:13:02.959 --> 00:13:06.470 align:start position:0% the greatest and more flexible ve<00:13:03.959> uh<00:13:04.600> I<00:13:04.720> like<00:13:05.079> the<00:13:05.240> insights<00:13:05.800> that<00:13:05.959> I<00:13:06.120> got 00:13:06.470 --> 00:13:06.480 align:start position:0% ve uh I like the insights that I got 00:13:06.480 --> 00:13:09.110 align:start position:0% ve uh I like the insights that I got while<00:13:06.720> Implement<00:13:07.240> that<00:13:08.160> and<00:13:08.399> the<00:13:08.600> EV 00:13:09.110 --> 00:13:09.120 align:start position:0% while Implement that and the EV 00:13:09.120 --> 00:13:12.389 align:start position:0% while Implement that and the EV framework<00:13:10.120> uh<00:13:10.279> it<00:13:10.480> Ru<00:13:10.880> two<00:13:11.079> things<00:13:11.600> it<00:13:11.839> ruce 00:13:12.389 --> 00:13:12.399 align:start position:0% framework uh it Ru two things it ruce 00:13:12.399 --> 00:13:14.790 align:start position:0% framework uh it Ru two things it ruce the<00:13:12.600> generics<00:13:13.079> on<00:13:13.240> the<00:13:13.440> data<00:13:14.000> on<00:13:14.279> transaction 00:13:14.790 --> 00:13:14.800 align:start position:0% the generics on the data on transaction 00:13:14.800 --> 00:13:18.110 align:start position:0% the generics on the data on transaction block<00:13:15.160> config<00:13:16.000> and<00:13:16.120> it<00:13:16.320> reduce<00:13:17.199> it<00:13:17.399> revor<00:13:17.959> the 00:13:18.110 --> 00:13:18.120 align:start position:0% block config and it reduce it revor the 00:13:18.120 --> 00:13:22.150 align:start position:0% block config and it reduce it revor the Handler<00:13:18.800> in<00:13:19.120> more<00:13:19.519> trait<00:13:20.079> like<00:13:20.800> way<00:13:21.680> so<00:13:21.920> it's 00:13:22.150 --> 00:13:22.160 align:start position:0% Handler in more trait like way so it's 00:13:22.160 --> 00:13:25.110 align:start position:0% Handler in more trait like way so it's more<00:13:22.399> easier<00:13:22.760> to 00:13:25.110 --> 00:13:25.120 align:start position:0% 00:13:25.120 --> 00:13:29.790 align:start position:0% use<00:13:26.120> few<00:13:26.880> examples<00:13:27.519> of<00:13:27.800> that<00:13:28.279> is<00:13:28.519> basically 00:13:29.790 --> 00:13:29.800 align:start position:0% use few examples of that is basically 00:13:29.800 --> 00:13:33.829 align:start position:0% use few examples of that is basically how<00:13:30.800> how<00:13:31.519> our<00:13:31.800> basic<00:13:32.199> of<00:13:32.399> the<00:13:32.560> optimism<00:13:33.560> that 00:13:33.829 --> 00:13:33.839 align:start position:0% how how our basic of the optimism that 00:13:33.839 --> 00:13:37.310 align:start position:0% how how our basic of the optimism that was<00:13:34.079> the<00:13:34.320> first<00:13:35.079> uh<00:13:35.320> few<00:13:36.160> that<00:13:36.320> was<00:13:36.639> first 00:13:37.310 --> 00:13:37.320 align:start position:0% was the first uh few that was first 00:13:37.320 --> 00:13:39.829 align:start position:0% was the first uh few that was first chain<00:13:37.680> that<00:13:37.839> was<00:13:38.000> included<00:13:38.360> in<00:13:38.440> RBM<00:13:39.199> in<00:13:39.399> sense 00:13:39.829 --> 00:13:39.839 align:start position:0% chain that was included in RBM in sense 00:13:39.839 --> 00:13:42.870 align:start position:0% chain that was included in RBM in sense of<00:13:40.120> the<00:13:40.399> it<00:13:40.519> was<00:13:40.760> included<00:13:41.199> as<00:13:41.320> the<00:13:41.720> feature<00:13:42.720> it 00:13:42.870 --> 00:13:42.880 align:start position:0% of the it was included as the feature it 00:13:42.880 --> 00:13:46.189 align:start position:0% of the it was included as the feature it was<00:13:43.160> very<00:13:43.880> like<00:13:44.279> in<00:13:44.920> intrusive<00:13:45.920> with<00:13:46.079> the 00:13:46.189 --> 00:13:46.199 align:start position:0% was very like in intrusive with the 00:13:46.199 --> 00:13:49.670 align:start position:0% was very like in intrusive with the handlers<00:13:46.800> it<00:13:47.040> be<00:13:47.360> I<00:13:47.760> tried<00:13:48.639> I<00:13:48.920> succeed<00:13:49.320> to 00:13:49.670 --> 00:13:49.680 align:start position:0% handlers it be I tried I succeed to 00:13:49.680 --> 00:13:51.310 align:start position:0% handlers it be I tried I succeed to extract<00:13:50.079> some<00:13:50.279> functionality<00:13:50.680> to<00:13:50.800> the 00:13:51.310 --> 00:13:51.320 align:start position:0% extract some functionality to the 00:13:51.320 --> 00:13:55.870 align:start position:0% extract some functionality to the handlers<00:13:52.320> but<00:13:52.920> with<00:13:53.480> EV<00:13:54.040> framework<00:13:55.040> uh<00:13:55.480> that 00:13:55.870 --> 00:13:55.880 align:start position:0% handlers but with EV framework uh that 00:13:55.880 --> 00:13:58.629 align:start position:0% handlers but with EV framework uh that become<00:13:56.240> even<00:13:56.519> easier<00:13:57.519> currently<00:13:58.040> it<00:13:58.240> stands 00:13:58.629 --> 00:13:58.639 align:start position:0% become even easier currently it stands 00:13:58.639 --> 00:14:01.269 align:start position:0% become even easier currently it stands it's<00:13:59.120> con<00:13:59.279> crate<00:13:59.839> I<00:14:00.000> still<00:14:00.399> have<00:14:00.639> work<00:14:00.880> to<00:14:01.079> do 00:14:01.269 --> 00:14:01.279 align:start position:0% it's con crate I still have work to do 00:14:01.279 --> 00:14:05.710 align:start position:0% it's con crate I still have work to do on<00:14:01.480> EV<00:14:02.240> frameworking<00:14:03.240> but<00:14:03.720> it<00:14:04.560> become 00:14:05.710 --> 00:14:05.720 align:start position:0% on EV frameworking but it become 00:14:05.720 --> 00:14:08.509 align:start position:0% on EV frameworking but it become possibility<00:14:06.720> under<00:14:07.320> uh<00:14:07.519> another<00:14:07.920> chain<00:14:08.240> is 00:14:08.509 --> 00:14:08.519 align:start position:0% possibility under uh another chain is 00:14:08.519 --> 00:14:10.389 align:start position:0% possibility under uh another chain is call<00:14:08.920> that<00:14:09.079> did<00:14:09.279> the<00:14:09.480> similar<00:14:09.920> thing<00:14:10.120> on<00:14:10.279> their 00:14:10.389 --> 00:14:10.399 align:start position:0% call that did the similar thing on their 00:14:10.399 --> 00:14:11.110 align:start position:0% call that did the similar thing on their own 00:14:11.110 --> 00:14:11.120 align:start position:0% own 00:14:11.120 --> 00:14:14.629 align:start position:0% own repo<00:14:12.120> just<00:14:12.440> imagine<00:14:13.040> like<00:14:13.480> every<00:14:13.800> evm<00:14:14.240> chain 00:14:14.629 --> 00:14:14.639 align:start position:0% repo just imagine like every evm chain 00:14:14.639 --> 00:14:17.470 align:start position:0% repo just imagine like every evm chain doing<00:14:15.079> their<00:14:15.240> own<00:14:15.839> crates<00:14:16.720> and<00:14:17.040> having 00:14:17.470 --> 00:14:17.480 align:start position:0% doing their own crates and having 00:14:17.480 --> 00:14:20.949 align:start position:0% doing their own crates and having Foundry<00:14:18.199> r<00:14:18.639> or<00:14:18.959> all<00:14:19.160> the<00:14:19.320> tooling<00:14:20.160> support 00:14:20.949 --> 00:14:20.959 align:start position:0% Foundry r or all the tooling support 00:14:20.959 --> 00:14:24.350 align:start position:0% Foundry r or all the tooling support those<00:14:21.680> ex<00:14:22.240> variants<00:14:22.880> of 00:14:24.350 --> 00:14:24.360 align:start position:0% those ex variants of 00:14:24.360 --> 00:14:28.069 align:start position:0% those ex variants of RM<00:14:25.360> and<00:14:25.639> all<00:14:25.920> be<00:14:26.120> tested<00:14:26.680> all<00:14:26.920> be<00:14:27.079> done<00:14:27.680> in 00:14:28.069 --> 00:14:28.079 align:start position:0% RM and all be tested all be done in 00:14:28.079 --> 00:14:29.710 align:start position:0% RM and all be tested all be done in basically 00:14:29.710 --> 00:14:29.720 align:start position:0% basically 00:14:29.720 --> 00:14:34.870 align:start position:0% basically it<00:14:29.959> eases<00:14:30.639> the<00:14:30.920> integration<00:14:31.800> with<00:14:32.120> all<00:14:32.440> the 00:14:34.870 --> 00:14:34.880 align:start position:0% 00:14:34.880 --> 00:14:36.590 align:start position:0% stack<00:14:35.880> the 00:14:36.590 --> 00:14:36.600 align:start position:0% stack the 00:14:36.600 --> 00:14:39.749 align:start position:0% stack the split<00:14:37.600> uh<00:14:38.000> that<00:14:38.199> was<00:14:38.880> inside<00:14:39.279> that<00:14:39.399> the<00:14:39.560> head 00:14:39.749 --> 00:14:39.759 align:start position:0% split uh that was inside that the head 00:14:39.759 --> 00:14:41.150 align:start position:0% split uh that was inside that the head with<00:14:39.880> the<00:14:40.000> Handler<00:14:40.360> is<00:14:40.519> there<00:14:40.639> is<00:14:40.800> split 00:14:41.150 --> 00:14:41.160 align:start position:0% with the Handler is there is split 00:14:41.160 --> 00:14:43.710 align:start position:0% with the Handler is there is split between<00:14:41.440> the<00:14:41.639> data<00:14:42.480> that<00:14:42.600> is<00:14:42.759> currently 00:14:43.710 --> 00:14:43.720 align:start position:0% between the data that is currently 00:14:43.720 --> 00:14:46.910 align:start position:0% between the data that is currently context<00:14:44.720> and<00:14:45.079> the<00:14:45.320> Handler<00:14:46.320> that<00:14:46.480> is<00:14:46.720> the 00:14:46.910 --> 00:14:46.920 align:start position:0% context and the Handler that is the 00:14:46.920 --> 00:14:49.990 align:start position:0% context and the Handler that is the logic<00:14:47.399> part<00:14:47.639> of<00:14:48.079> RM<00:14:49.079> context<00:14:49.560> contain 00:14:49.990 --> 00:14:50.000 align:start position:0% logic part of RM context contain 00:14:50.000 --> 00:14:52.430 align:start position:0% logic part of RM context contain transaction<00:14:50.639> block<00:14:51.240> usual<00:14:51.720> things<00:14:52.240> it 00:14:52.430 --> 00:14:52.440 align:start position:0% transaction block usual things it 00:14:52.440 --> 00:14:54.670 align:start position:0% transaction block usual things it contains<00:14:52.959> journaling<00:14:53.560> state<00:14:54.079> that<00:14:54.320> allows 00:14:54.670 --> 00:14:54.680 align:start position:0% contains journaling state that allows 00:14:54.680 --> 00:14:56.990 align:start position:0% contains journaling state that allows you<00:14:54.839> to<00:14:55.040> revert<00:14:55.600> things<00:14:56.120> when<00:14:56.320> the<00:14:56.480> revert 00:14:56.990 --> 00:14:57.000 align:start position:0% you to revert things when the revert 00:14:57.000 --> 00:15:00.710 align:start position:0% you to revert things when the revert happen<00:14:57.320> in<00:14:57.480> the<00:14:57.880> calls<00:14:58.880> and<00:14:59.120> and<00:14:59.480> it<00:15:00.120> contains 00:15:00.710 --> 00:15:00.720 align:start position:0% happen in the calls and and it contains 00:15:00.720 --> 00:15:03.710 align:start position:0% happen in the calls and and it contains database<00:15:01.399> that<00:15:01.600> fetch<00:15:01.920> the<00:15:02.040> runtime<00:15:02.600> data<00:15:03.600> uh 00:15:03.710 --> 00:15:03.720 align:start position:0% database that fetch the runtime data uh 00:15:03.720 --> 00:15:06.030 align:start position:0% database that fetch the runtime data uh trans<00:15:04.240> stor<00:15:04.639> and<00:15:04.800> Waring<00:15:05.120> of<00:15:05.399> account<00:15:05.680> is<00:15:05.839> all 00:15:06.030 --> 00:15:06.040 align:start position:0% trans stor and Waring of account is all 00:15:06.040 --> 00:15:09.230 align:start position:0% trans stor and Waring of account is all done<00:15:06.240> in<00:15:06.800> journaling<00:15:07.800> uh<00:15:08.079> Handler<00:15:08.759> on<00:15:09.000> other 00:15:09.230 --> 00:15:09.240 align:start position:0% done in journaling uh Handler on other 00:15:09.240 --> 00:15:10.749 align:start position:0% done in journaling uh Handler on other hand<00:15:09.519> he<00:15:09.639> has<00:15:09.839> four 00:15:10.749 --> 00:15:10.759 align:start position:0% hand he has four 00:15:10.759 --> 00:15:14.269 align:start position:0% hand he has four parts<00:15:11.759> uh<00:15:11.959> validator<00:15:12.600> that<00:15:12.839> validates<00:15:13.800> the 00:15:14.269 --> 00:15:14.279 align:start position:0% parts uh validator that validates the 00:15:14.279 --> 00:15:16.550 align:start position:0% parts uh validator that validates the interaction<00:15:14.880> between<00:15:15.399> block<00:15:15.920> transaction 00:15:16.550 --> 00:15:16.560 align:start position:0% interaction between block transaction 00:15:16.560 --> 00:15:19.870 align:start position:0% interaction between block transaction and<00:15:16.800> config<00:15:17.560> config<00:15:18.240> can<00:15:18.600> config<00:15:19.279> can<00:15:19.600> have 00:15:19.870 --> 00:15:19.880 align:start position:0% and config config can config can have 00:15:19.880 --> 00:15:22.069 align:start position:0% and config config can config can have chain<00:15:20.199> ID<00:15:20.560> that<00:15:20.720> needs<00:15:20.920> to<00:15:21.040> be<00:15:21.199> checked<00:15:21.759> with 00:15:22.069 --> 00:15:22.079 align:start position:0% chain ID that needs to be checked with 00:15:22.079 --> 00:15:25.150 align:start position:0% chain ID that needs to be checked with the<00:15:22.320> transaction<00:15:22.880> chain<00:15:23.199> ID<00:15:23.920> for<00:15:24.160> example 00:15:25.150 --> 00:15:25.160 align:start position:0% the transaction chain ID for example 00:15:25.160 --> 00:15:28.309 align:start position:0% the transaction chain ID for example prevalidation<00:15:26.040> do<00:15:26.399> some<00:15:26.839> warming<00:15:27.639> do<00:15:27.959> some 00:15:28.309 --> 00:15:28.319 align:start position:0% prevalidation do some warming do some 00:15:28.319 --> 00:15:32.350 align:start position:0% prevalidation do some warming do some deduct<00:15:28.759> the<00:15:29.040> call<00:15:29.480> balance<00:15:30.160> dop 00:15:32.350 --> 00:15:32.360 align:start position:0% deduct the call balance dop 00:15:32.360 --> 00:15:33.870 align:start position:0% deduct the call balance dop 7702 00:15:33.870 --> 00:15:33.880 align:start position:0% 7702 00:15:33.880 --> 00:15:35.790 align:start position:0% 7702 um<00:15:34.880> yeah 00:15:35.790 --> 00:15:35.800 align:start position:0% um yeah 00:15:35.800 --> 00:15:39.710 align:start position:0% um yeah it<00:15:36.800> it<00:15:37.319> yeah<00:15:37.560> change<00:15:38.079> delegate<00:15:38.680> quote<00:15:39.079> to<00:15:39.319> the 00:15:39.710 --> 00:15:39.720 align:start position:0% it it yeah change delegate quote to the 00:15:39.720 --> 00:15:44.350 align:start position:0% it it yeah change delegate quote to the state<00:15:41.120> execution<00:15:42.120> uh<00:15:42.319> is<00:15:42.720> little<00:15:42.959> bit<00:15:43.360> complex 00:15:44.350 --> 00:15:44.360 align:start position:0% state execution uh is little bit complex 00:15:44.360 --> 00:15:47.509 align:start position:0% state execution uh is little bit complex it<00:15:44.600> has<00:15:44.959> two<00:15:45.120> main<00:15:45.360> Loops<00:15:46.079> the<00:15:46.279> frame<00:15:47.120> is<00:15:47.319> the 00:15:47.509 --> 00:15:47.519 align:start position:0% it has two main Loops the frame is the 00:15:47.519 --> 00:15:51.790 align:start position:0% it has two main Loops the frame is the loop<00:15:47.920> around<00:15:48.720> the<00:15:49.720> around<00:15:50.160> the<00:15:50.480> calls<00:15:51.480> and 00:15:51.790 --> 00:15:51.800 align:start position:0% loop around the around the calls and 00:15:51.800 --> 00:15:55.150 align:start position:0% loop around the around the calls and interpreter<00:15:52.680> is<00:15:53.040> loop<00:15:53.639> around<00:15:54.160> the<00:15:54.440> bite<00:15:54.720> code 00:15:55.150 --> 00:15:55.160 align:start position:0% interpreter is loop around the bite code 00:15:55.160 --> 00:15:57.269 align:start position:0% interpreter is loop around the bite code basic 00:15:57.269 --> 00:15:57.279 align:start position:0% basic 00:15:57.279 --> 00:16:00.870 align:start position:0% basic instructions<00:15:58.279> and<00:15:59.079> in<00:15:59.319> the<00:15:59.440> end<00:15:59.800> we<00:16:00.040> have<00:16:00.560> post 00:16:00.870 --> 00:16:00.880 align:start position:0% instructions and in the end we have post 00:16:00.880 --> 00:16:03.829 align:start position:0% instructions and in the end we have post execution<00:16:01.560> that<00:16:01.720> does<00:16:02.160> refund<00:16:02.800> of<00:16:03.000> not<00:16:03.319> spend 00:16:03.829 --> 00:16:03.839 align:start position:0% execution that does refund of not spend 00:16:03.839 --> 00:16:07.910 align:start position:0% execution that does refund of not spend gas<00:16:04.399> it<00:16:04.959> reimburse<00:16:05.680> the<00:16:06.199> color<00:16:07.199> it<00:16:07.519> basically 00:16:07.910 --> 00:16:07.920 align:start position:0% gas it reimburse the color it basically 00:16:07.920 --> 00:16:10.749 align:start position:0% gas it reimburse the color it basically RS<00:16:08.360> the<00:16:08.480> beneficiary<00:16:09.319> and<00:16:09.519> creates<00:16:10.120> the<00:16:10.560> the 00:16:10.749 --> 00:16:10.759 align:start position:0% RS the beneficiary and creates the the 00:16:10.759 --> 00:16:14.629 align:start position:0% RS the beneficiary and creates the the outcome<00:16:11.720> of<00:16:12.120> the 00:16:14.629 --> 00:16:14.639 align:start position:0% 00:16:14.639 --> 00:16:18.629 align:start position:0% execution<00:16:15.639> in<00:16:16.199> code<00:16:17.199> as<00:16:17.360> you<00:16:17.519> see<00:16:17.880> context<00:16:18.440> has 00:16:18.629 --> 00:16:18.639 align:start position:0% execution in code as you see context has 00:16:18.639 --> 00:16:19.790 align:start position:0% execution in code as you see context has a<00:16:18.800> lot<00:16:18.959> of 00:16:19.790 --> 00:16:19.800 align:start position:0% a lot of 00:16:19.800 --> 00:16:23.990 align:start position:0% a lot of generics<00:16:21.079> and<00:16:22.079> it<00:16:22.560> allows<00:16:23.079> you<00:16:23.319> basically<00:16:23.720> to 00:16:23.990 --> 00:16:24.000 align:start position:0% generics and it allows you basically to 00:16:24.000 --> 00:16:26.509 align:start position:0% generics and it allows you basically to have<00:16:24.199> it<00:16:24.519> generalized<00:16:25.480> there<00:16:25.600> is<00:16:25.759> some<00:16:26.000> to-do 00:16:26.509 --> 00:16:26.519 align:start position:0% have it generalized there is some to-do 00:16:26.519 --> 00:16:29.309 align:start position:0% have it generalized there is some to-do too<00:16:27.319> spec<00:16:27.680> needs<00:16:27.920> to<00:16:28.040> be<00:16:28.240> made<00:16:28.560> inside<00:16:29.040> side 00:16:29.309 --> 00:16:29.319 align:start position:0% too spec needs to be made inside side 00:16:29.319 --> 00:16:31.230 align:start position:0% too spec needs to be made inside side moved<00:16:29.759> ins<00:16:30.000> side<00:16:30.240> configuration<00:16:30.920> but<00:16:31.079> in 00:16:31.230 --> 00:16:31.240 align:start position:0% moved ins side configuration but in 00:16:31.240 --> 00:16:34.749 align:start position:0% moved ins side configuration but in general<00:16:32.160> this<00:16:32.319> is<00:16:32.839> the<00:16:33.440> the<00:16:33.639> first<00:16:34.000> view<00:16:34.440> of 00:16:34.749 --> 00:16:34.759 align:start position:0% general this is the the first view of 00:16:34.759 --> 00:16:39.230 align:start position:0% general this is the the first view of the<00:16:35.319> of<00:16:35.480> the<00:16:35.920> new<00:16:36.199> context<00:16:36.680> in<00:16:36.959> evm 00:16:39.230 --> 00:16:39.240 align:start position:0% the of the new context in evm 00:16:39.240 --> 00:16:42.910 align:start position:0% the of the new context in evm framework<00:16:40.240> validation<00:16:41.000> wire<00:16:42.000> one<00:16:42.440> of<00:16:42.720> the 00:16:42.910 --> 00:16:42.920 align:start position:0% framework validation wire one of the 00:16:42.920 --> 00:16:45.670 align:start position:0% framework validation wire one of the four<00:16:43.279> stages<00:16:43.800> in<00:16:43.920> the<00:16:44.040> Handler<00:16:44.720> has<00:16:45.279> basically 00:16:45.670 --> 00:16:45.680 align:start position:0% four stages in the Handler has basically 00:16:45.680 --> 00:16:48.430 align:start position:0% four stages in the Handler has basically self<00:16:46.079> contain<00:16:46.560> it<00:16:46.800> contains<00:16:47.800> associate<00:16:48.240> types 00:16:48.430 --> 00:16:48.440 align:start position:0% self contain it contains associate types 00:16:48.440 --> 00:16:50.389 align:start position:0% self contain it contains associate types of<00:16:48.600> the<00:16:48.720> context<00:16:49.160> and<00:16:49.360> arrow<00:16:49.720> a<00:16:49.839> few<00:16:50.079> factor 00:16:50.389 --> 00:16:50.399 align:start position:0% of the context and arrow a few factor 00:16:50.399 --> 00:16:53.509 align:start position:0% of the context and arrow a few factor that<00:16:50.519> needs<00:16:50.720> to<00:16:50.800> be<00:16:51.399> called<00:16:52.399> uh<00:16:52.519> other<00:16:53.079> Handler 00:16:53.509 --> 00:16:53.519 align:start position:0% that needs to be called uh other Handler 00:16:53.519 --> 00:16:56.189 align:start position:0% that needs to be called uh other Handler types<00:16:53.839> are<00:16:54.040> in<00:16:54.199> similar<00:16:54.639> fashion<00:16:55.040> made<00:16:55.959> and 00:16:56.189 --> 00:16:56.199 align:start position:0% types are in similar fashion made and 00:16:56.199 --> 00:16:59.470 align:start position:0% types are in similar fashion made and you<00:16:56.519> can<00:16:56.880> have<00:16:57.279> ethereum<00:16:58.160> validation 00:16:59.470 --> 00:16:59.480 align:start position:0% you can have ethereum validation 00:16:59.480 --> 00:17:04.870 align:start position:0% you can have ethereum validation that<00:16:59.839> basically<00:17:00.839> does<00:17:01.720> the<00:17:02.160> the<00:17:02.399> AUM<00:17:03.000> specific 00:17:04.870 --> 00:17:04.880 align:start position:0% that basically does the the AUM specific 00:17:04.880 --> 00:17:07.990 align:start position:0% that basically does the the AUM specific implementation<00:17:05.880> many<00:17:06.240> evm<00:17:06.760> became<00:17:07.480> become 00:17:07.990 --> 00:17:08.000 align:start position:0% implementation many evm became become 00:17:08.000 --> 00:17:11.069 align:start position:0% implementation many evm became become just<00:17:08.240> the<00:17:08.520> context<00:17:09.120> and<00:17:09.280> the 00:17:11.069 --> 00:17:11.079 align:start position:0% just the context and the 00:17:11.079 --> 00:17:14.669 align:start position:0% just the context and the Handler<00:17:12.079> and<00:17:12.480> to<00:17:12.720> create<00:17:13.079> your<00:17:13.319> own<00:17:13.679> evm<00:17:14.559> this 00:17:14.669 --> 00:17:14.679 align:start position:0% Handler and to create your own evm this 00:17:14.679 --> 00:17:17.669 align:start position:0% Handler and to create your own evm this is<00:17:15.079> example<00:17:15.480> of<00:17:15.679> manm<00:17:16.559> it's<00:17:16.760> still<00:17:17.160> pending 00:17:17.669 --> 00:17:17.679 align:start position:0% is example of manm it's still pending 00:17:17.679 --> 00:17:20.150 align:start position:0% is example of manm it's still pending and<00:17:18.039> it's<00:17:18.240> probably<00:17:18.520> going<00:17:18.679> to<00:17:18.799> be<00:17:19.000> changed<00:17:19.959> in 00:17:20.150 --> 00:17:20.160 align:start position:0% and it's probably going to be changed in 00:17:20.160 --> 00:17:24.150 align:start position:0% and it's probably going to be changed in small<00:17:20.520> or<00:17:20.679> maybe<00:17:21.280> medium<00:17:22.160> way<00:17:23.160> uh<00:17:23.400> you 00:17:24.150 --> 00:17:24.160 align:start position:0% small or maybe medium way uh you 00:17:24.160 --> 00:17:27.750 align:start position:0% small or maybe medium way uh you basically<00:17:25.120> specify<00:17:25.760> everything<00:17:26.160> you<00:17:26.760> need 00:17:27.750 --> 00:17:27.760 align:start position:0% basically specify everything you need 00:17:27.760 --> 00:17:29.590 align:start position:0% basically specify everything you need for<00:17:27.959> example<00:17:28.319> you<00:17:28.480> have<00:17:28.640> your<00:17:28.960> context<00:17:29.400> with 00:17:29.590 --> 00:17:29.600 align:start position:0% for example you have your context with 00:17:29.600 --> 00:17:32.750 align:start position:0% for example you have your context with some<00:17:29.960> predefined<00:17:30.600> data<00:17:31.320> theaction<00:17:32.000> and<00:17:32.559> for 00:17:32.750 --> 00:17:32.760 align:start position:0% some predefined data theaction and for 00:17:32.760 --> 00:17:35.110 align:start position:0% some predefined data theaction and for example<00:17:33.160> are<00:17:33.400> the<00:17:33.559> structure<00:17:34.039> inside<00:17:34.440> RM<00:17:35.000> but 00:17:35.110 --> 00:17:35.120 align:start position:0% example are the structure inside RM but 00:17:35.120 --> 00:17:36.950 align:start position:0% example are the structure inside RM but you<00:17:35.200> can<00:17:35.400> add<00:17:35.640> your<00:17:35.880> transaction<00:17:36.360> initation 00:17:36.950 --> 00:17:36.960 align:start position:0% you can add your transaction initation 00:17:36.960 --> 00:17:40.190 align:start position:0% you can add your transaction initation on<00:17:37.120> it<00:17:38.120> and<00:17:38.280> you<00:17:38.440> have<00:17:38.679> specified<00:17:39.240> the<00:17:39.559> Handler 00:17:40.190 --> 00:17:40.200 align:start position:0% on it and you have specified the Handler 00:17:40.200 --> 00:17:43.870 align:start position:0% on it and you have specified the Handler that<00:17:40.480> has<00:17:41.200> their<00:17:41.400> own<00:17:42.360> uh 00:17:43.870 --> 00:17:43.880 align:start position:0% that has their own uh 00:17:43.880 --> 00:17:46.070 align:start position:0% that has their own uh functionality 00:17:46.070 --> 00:17:46.080 align:start position:0% functionality 00:17:46.080 --> 00:17:50.310 align:start position:0% functionality execution<00:17:47.080> uh<00:17:47.280> eum<00:17:48.360> executor<00:17:49.360> has<00:17:49.640> few<00:17:49.880> field 00:17:50.310 --> 00:17:50.320 align:start position:0% execution uh eum executor has few field 00:17:50.320 --> 00:17:52.909 align:start position:0% execution uh eum executor has few field that<00:17:50.440> are<00:17:50.600> maybe 00:17:52.909 --> 00:17:52.919 align:start position:0% that are maybe 00:17:52.919 --> 00:17:55.630 align:start position:0% that are maybe um<00:17:53.919> they're<00:17:54.360> interesting<00:17:54.799> to<00:17:55.080> people<00:17:55.440> they 00:17:55.630 --> 00:17:55.640 align:start position:0% um they're interesting to people they 00:17:55.640 --> 00:17:57.950 align:start position:0% um they're interesting to people they have<00:17:56.280> pre-compile<00:17:57.080> provider<00:17:57.760> and 00:17:57.950 --> 00:17:57.960 align:start position:0% have pre-compile provider and 00:17:57.960 --> 00:17:59.950 align:start position:0% have pre-compile provider and instruction<00:17:58.400> provider<00:17:59.240> where<00:17:59.400> you<00:17:59.520> can 00:17:59.950 --> 00:17:59.960 align:start position:0% instruction provider where you can 00:17:59.960 --> 00:18:02.590 align:start position:0% instruction provider where you can generate<00:18:00.480> your<00:18:00.919> basic<00:18:01.360> list<00:18:01.559> of<00:18:01.760> precompilers 00:18:02.590 --> 00:18:02.600 align:start position:0% generate your basic list of precompilers 00:18:02.600 --> 00:18:03.789 align:start position:0% generate your basic list of precompilers and<00:18:02.720> there<00:18:02.840> is<00:18:03.000> trade<00:18:03.320> that<00:18:03.440> you<00:18:03.520> need<00:18:03.679> to 00:18:03.789 --> 00:18:03.799 align:start position:0% and there is trade that you need to 00:18:03.799 --> 00:18:07.070 align:start position:0% and there is trade that you need to implement<00:18:04.159> for<00:18:04.360> this<00:18:04.520> to 00:18:07.070 --> 00:18:07.080 align:start position:0% 00:18:07.080 --> 00:18:10.390 align:start position:0% happen<00:18:08.080> uh<00:18:08.200> on<00:18:08.400> other<00:18:08.679> hand<00:18:09.200> this<00:18:09.320> is<00:18:09.960> example 00:18:10.390 --> 00:18:10.400 align:start position:0% happen uh on other hand this is example 00:18:10.400 --> 00:18:13.510 align:start position:0% happen uh on other hand this is example of<00:18:10.840> Inspector<00:18:11.760> main<00:18:12.120> evm<00:18:12.840> is<00:18:13.039> still<00:18:13.240> working 00:18:13.510 --> 00:18:13.520 align:start position:0% of Inspector main evm is still working 00:18:13.520 --> 00:18:16.310 align:start position:0% of Inspector main evm is still working in<00:18:13.679> progress<00:18:14.200> but<00:18:14.440> idea<00:18:14.799> is<00:18:15.039> you<00:18:15.159> will<00:18:15.679> do<00:18:16.039> your 00:18:16.310 --> 00:18:16.320 align:start position:0% in progress but idea is you will do your 00:18:16.320 --> 00:18:18.990 align:start position:0% in progress but idea is you will do your create<00:18:16.559> you<00:18:16.760> create<00:18:17.080> your<00:18:17.280> own<00:18:18.240> uh<00:18:18.440> in 00:18:18.990 --> 00:18:19.000 align:start position:0% create you create your own uh in 00:18:19.000 --> 00:18:21.669 align:start position:0% create you create your own uh in inspector<00:18:19.960> types<00:18:20.880> where<00:18:21.039> that<00:18:21.240> Implement 00:18:21.669 --> 00:18:21.679 align:start position:0% inspector types where that Implement 00:18:21.679 --> 00:18:24.149 align:start position:0% inspector types where that Implement those<00:18:21.960> traits<00:18:22.960> and<00:18:23.080> you<00:18:23.200> can<00:18:23.400> just<00:18:23.640> override 00:18:24.149 --> 00:18:24.159 align:start position:0% those traits and you can just override 00:18:24.159 --> 00:18:27.430 align:start position:0% those traits and you can just override it<00:18:24.760> in<00:18:24.880> the<00:18:25.039> end<00:18:25.360> this<00:18:25.760> inspector<00:18:26.240> main<00:18:26.760> uses 00:18:27.430 --> 00:18:27.440 align:start position:0% it in the end this inspector main uses 00:18:27.440 --> 00:18:32.510 align:start position:0% it in the end this inspector main uses the<00:18:28.440> D<00:18:28.919> B<00:18:29.360> and<00:18:29.799> inspector 00:18:32.510 --> 00:18:32.520 align:start position:0% the D B and inspector 00:18:32.520 --> 00:18:35.830 align:start position:0% the D B and inspector genics<00:18:33.520> and<00:18:34.039> this<00:18:34.159> is<00:18:34.480> how<00:18:34.799> you<00:18:34.960> use<00:18:35.200> it<00:18:35.600> there 00:18:35.830 --> 00:18:35.840 align:start position:0% genics and this is how you use it there 00:18:35.840 --> 00:18:38.669 align:start position:0% genics and this is how you use it there probably<00:18:36.200> going<00:18:36.360> to<00:18:36.520> be<00:18:37.080> some<00:18:38.080> helper 00:18:38.669 --> 00:18:38.679 align:start position:0% probably going to be some helper 00:18:38.679 --> 00:18:43.789 align:start position:0% probably going to be some helper function<00:18:39.200> that<00:18:39.440> is<00:18:40.440> allow<00:18:41.039> a<00:18:41.120> little<00:18:41.400> bit<00:18:41.640> more 00:18:43.789 --> 00:18:43.799 align:start position:0% function that is allow a little bit more 00:18:43.799 --> 00:18:48.390 align:start position:0% function that is allow a little bit more um<00:18:44.799> flexibility<00:18:45.760> and<00:18:46.440> utility<00:18:47.440> but<00:18:47.919> I<00:18:48.039> want<00:18:48.280> to 00:18:48.390 --> 00:18:48.400 align:start position:0% um flexibility and utility but I want to 00:18:48.400 --> 00:18:50.470 align:start position:0% um flexibility and utility but I want to show<00:18:48.600> you<00:18:48.799> just<00:18:49.159> example<00:18:49.799> how<00:18:50.080> this<00:18:50.280> could 00:18:50.470 --> 00:18:50.480 align:start position:0% show you just example how this could 00:18:50.480 --> 00:18:52.630 align:start position:0% show you just example how this could look<00:18:51.320> it's 00:18:52.630 --> 00:18:52.640 align:start position:0% look it's 00:18:52.640 --> 00:18:57.830 align:start position:0% look it's um<00:18:54.080> yeah<00:18:55.080> in<00:18:55.240> the<00:18:55.520> end<00:18:56.520> um<00:18:56.799> I<00:18:57.000> assume<00:18:57.360> a<00:18:57.480> lot<00:18:57.640> of 00:18:57.830 --> 00:18:57.840 align:start position:0% um yeah in the end um I assume a lot of 00:18:57.840 --> 00:19:00.029 align:start position:0% um yeah in the end um I assume a lot of users<00:18:58.240> are<00:18:58.360> going<00:18:58.520> to<00:18:58.880> come<00:18:59.400> and<00:18:59.600> Implement 00:19:00.029 --> 00:19:00.039 align:start position:0% users are going to come and Implement 00:19:00.039 --> 00:19:02.350 align:start position:0% users are going to come and Implement their<00:19:00.200> own<00:19:00.400> evm<00:19:01.159> or<00:19:01.440> their<00:19:01.600> own<00:19:01.880> like 00:19:02.350 --> 00:19:02.360 align:start position:0% their own evm or their own like 00:19:02.360 --> 00:19:07.630 align:start position:0% their own evm or their own like extensions<00:19:03.360> and<00:19:03.600> just<00:19:03.880> use<00:19:04.240> our<00:19:04.480> evm<00:19:04.960> in<00:19:05.280> that 00:19:07.630 --> 00:19:07.640 align:start position:0% extensions and just use our evm in that 00:19:07.640 --> 00:19:12.430 align:start position:0% extensions and just use our evm in that form<00:19:09.080> uh<00:19:10.080> I<00:19:10.200> think<00:19:10.440> that's<00:19:10.640> it<00:19:11.600> uh<00:19:12.120> thank<00:19:12.280> you 00:19:12.430 --> 00:19:12.440 align:start position:0% form uh I think that's it uh thank you 00:19:12.440 --> 00:19:15.909 align:start position:0% form uh I think that's it uh thank you very<00:19:12.600> much<00:19:12.760> for<00:19:12.960> having<00:19:13.679> me 00:19:15.909 --> 00:19:15.919 align:start position:0% very much for having me 00:19:15.919 --> 00:19:19.520 align:start position:0% very much for having me and<00:19:16.919> that's 00:19:19.520 --> 00:19:19.530 align:start position:0% 00:19:19.530 --> 00:19:23.510 align:start position:0% [Music] 00:19:23.510 --> 00:19:23.520 align:start position:0% 00:19:23.520 --> 00:19:26.789 align:start position:0% it<00:19:24.520> thank<00:19:24.679> you<00:19:24.840> Dragon<00:19:25.559> it's<00:19:26.000> really<00:19:26.360> amazing 00:19:26.789 --> 00:19:26.799 align:start position:0% it thank you Dragon it's really amazing 00:19:26.799 --> 00:19:29.029 align:start position:0% it thank you Dragon it's really amazing what<00:19:26.960> you<00:19:27.080> have<00:19:27.240> the<00:19:27.480> man<00:19:27.720> us<00:19:27.880> to<00:19:28.039> do<00:19:28.559> and<00:19:28.880> all 00:19:29.029 --> 00:19:29.039 align:start position:0% what you have the man us to do and all 00:19:29.039 --> 00:19:33.270 align:start position:0% what you have the man us to do and all those<00:19:29.240> years<00:19:29.799> with<00:19:30.440> RM<00:19:31.440> so<00:19:32.280> let's<00:19:32.559> start<00:19:32.919> with 00:19:33.270 --> 00:19:33.280 align:start position:0% those years with RM so let's start with 00:19:33.280 --> 00:19:35.990 align:start position:0% those years with RM so let's start with our<00:19:34.039> questions<00:19:35.039> uh<00:19:35.200> the<00:19:35.320> first<00:19:35.600> question<00:19:35.840> is 00:19:35.990 --> 00:19:36.000 align:start position:0% our questions uh the first question is 00:19:36.000 --> 00:19:39.110 align:start position:0% our questions uh the first question is about<00:19:36.360> testing<00:19:36.880> so<00:19:37.159> do<00:19:37.280> you<00:19:37.480> use<00:19:38.200> any<00:19:38.480> kind<00:19:38.799> of 00:19:39.110 --> 00:19:39.120 align:start position:0% about testing so do you use any kind of 00:19:39.120 --> 00:19:40.909 align:start position:0% about testing so do you use any kind of equivalent<00:19:39.720> testing<00:19:40.200> or<00:19:40.520> basically 00:19:40.909 --> 00:19:40.919 align:start position:0% equivalent testing or basically 00:19:40.919 --> 00:19:44.390 align:start position:0% equivalent testing or basically differential<00:19:41.640> testing<00:19:42.640> uh<00:19:42.840> as<00:19:43.080> part<00:19:43.360> of<00:19:43.960> of<00:19:44.280> uh 00:19:44.390 --> 00:19:44.400 align:start position:0% differential testing uh as part of of uh 00:19:44.400 --> 00:19:48.710 align:start position:0% differential testing uh as part of of uh your<00:19:44.760> C<00:19:45.760> uh<00:19:46.000> yeah<00:19:46.240> on<00:19:46.480> every<00:19:47.000> PR<00:19:48.000> state<00:19:48.360> test 00:19:48.710 --> 00:19:48.720 align:start position:0% your C uh yeah on every PR state test 00:19:48.720 --> 00:19:50.750 align:start position:0% your C uh yeah on every PR state test around<00:19:49.240> basically<00:19:49.799> state<00:19:50.080> test<00:19:50.320> made<00:19:50.520> by 00:19:50.750 --> 00:19:50.760 align:start position:0% around basically state test made by 00:19:50.760 --> 00:19:53.310 align:start position:0% around basically state test made by Teran<00:19:51.039> Foundation<00:19:51.919> the<00:19:52.080> testing<00:19:52.440> team<00:19:53.120> and 00:19:53.310 --> 00:19:53.320 align:start position:0% Teran Foundation the testing team and 00:19:53.320 --> 00:19:56.310 align:start position:0% Teran Foundation the testing team and it's<00:19:53.600> like<00:19:53.960> good<00:19:54.919> first<00:19:55.240> line<00:19:55.480> of<00:19:55.640> the<00:19:55.840> fence 00:19:56.310 --> 00:19:56.320 align:start position:0% it's like good first line of the fence 00:19:56.320 --> 00:19:58.190 align:start position:0% it's like good first line of the fence if<00:19:56.520> everything<00:19:56.880> is<00:19:57.120> okay<00:19:57.360> if<00:19:57.600> everything 00:19:58.190 --> 00:19:58.200 align:start position:0% if everything is okay if everything 00:19:58.200 --> 00:20:01.310 align:start position:0% if everything is okay if everything works<00:19:59.080> other<00:19:59.360> than<00:19:59.559> that<00:19:59.760> there<00:19:59.880> is<00:20:00.720> fuzzing 00:20:01.310 --> 00:20:01.320 align:start position:0% works other than that there is fuzzing 00:20:01.320 --> 00:20:04.390 align:start position:0% works other than that there is fuzzing team<00:20:02.200> fuzzing<00:20:03.200> project<00:20:03.679> that<00:20:03.799> are<00:20:03.919> run<00:20:04.120> in<00:20:04.240> the 00:20:04.390 --> 00:20:04.400 align:start position:0% team fuzzing project that are run in the 00:20:04.400 --> 00:20:07.070 align:start position:0% team fuzzing project that are run in the backgrounds<00:20:05.080> by<00:20:05.520> materium<00:20:05.919> Foundation<00:20:06.559> by<00:20:06.960> I 00:20:07.070 --> 00:20:07.080 align:start position:0% backgrounds by materium Foundation by I 00:20:07.080 --> 00:20:10.310 align:start position:0% backgrounds by materium Foundation by I think<00:20:07.240> Martin<00:20:07.640> has<00:20:07.880> it<00:20:08.120> from<00:20:08.480> go<00:20:08.679> evm<00:20:09.080> lab<00:20:10.080> from 00:20:10.310 --> 00:20:10.320 align:start position:0% think Martin has it from go evm lab from 00:20:10.320 --> 00:20:13.270 align:start position:0% think Martin has it from go evm lab from go<00:20:10.520> etherum<00:20:10.960> but<00:20:11.120> go<00:20:11.559> lab<00:20:11.799> I<00:20:11.919> think<00:20:12.080> is<00:20:12.320> project 00:20:13.270 --> 00:20:13.280 align:start position:0% go etherum but go lab I think is project 00:20:13.280 --> 00:20:14.590 align:start position:0% go etherum but go lab I think is project but<00:20:13.559> yeah 00:20:14.590 --> 00:20:14.600 align:start position:0% but yeah 00:20:14.600 --> 00:20:18.430 align:start position:0% but yeah it's<00:20:15.600> there<00:20:15.720> are<00:20:15.919> few<00:20:16.400> stages<00:20:16.960> of<00:20:17.240> the<00:20:17.480> testing 00:20:18.430 --> 00:20:18.440 align:start position:0% it's there are few stages of the testing 00:20:18.440 --> 00:20:22.310 align:start position:0% it's there are few stages of the testing done<00:20:19.440> and<00:20:19.760> this<00:20:19.880> is<00:20:20.520> based<00:20:20.840> on<00:20:21.360> every<00:20:21.640> new<00:20:21.919> PR 00:20:22.310 --> 00:20:22.320 align:start position:0% done and this is based on every new PR 00:20:22.320 --> 00:20:25.350 align:start position:0% done and this is based on every new PR or<00:20:23.200> yeah<00:20:23.640> uh<00:20:24.000> for<00:20:24.240> fuzzing<00:20:24.640> is<00:20:24.760> done<00:20:24.960> in<00:20:25.080> the 00:20:25.350 --> 00:20:25.360 align:start position:0% or yeah uh for fuzzing is done in the 00:20:25.360 --> 00:20:27.990 align:start position:0% or yeah uh for fuzzing is done in the background<00:20:26.360> it's<00:20:26.480> not<00:20:26.640> on<00:20:26.760> every<00:20:27.039> PR<00:20:27.640> but<00:20:27.880> the 00:20:27.990 --> 00:20:28.000 align:start position:0% background it's not on every PR but the 00:20:28.000 --> 00:20:29.230 align:start position:0% background it's not on every PR but the state<00:20:28.360> test 00:20:29.230 --> 00:20:29.240 align:start position:0% state test 00:20:29.240 --> 00:20:32.190 align:start position:0% state test running<00:20:29.600> it<00:20:29.840> in<00:20:30.080> the<00:20:30.320> on<00:20:30.520> theb<00:20:31.440> web<00:20:31.679> assembly 00:20:32.190 --> 00:20:32.200 align:start position:0% running it in the on theb web assembly 00:20:32.200 --> 00:20:37.990 align:start position:0% running it in the on theb web assembly some<00:20:32.559> specific<00:20:33.679> rust<00:20:35.159> Target<00:20:36.159> uh<00:20:36.360> running<00:20:36.960> on 00:20:37.990 --> 00:20:38.000 align:start position:0% some specific rust Target uh running on 00:20:38.000 --> 00:20:41.870 align:start position:0% some specific rust Target uh running on uh<00:20:39.280> different<00:20:40.280> targets<00:20:40.799> basic<00:20:41.120> allows<00:20:41.400> you<00:20:41.520> to 00:20:41.870 --> 00:20:41.880 align:start position:0% uh different targets basic allows you to 00:20:41.880 --> 00:20:45.070 align:start position:0% uh different targets basic allows you to test<00:20:42.200> all<00:20:42.480> the<00:20:42.760> those<00:20:43.000> things<00:20:43.559> mhm<00:20:44.360> so<00:20:44.840> are 00:20:45.070 --> 00:20:45.080 align:start position:0% test all the those things mhm so are 00:20:45.080 --> 00:20:48.270 align:start position:0% test all the those things mhm so are there<00:20:45.600> any<00:20:46.080> early<00:20:46.760> architectural<00:20:47.600> decisions 00:20:48.270 --> 00:20:48.280 align:start position:0% there any early architectural decisions 00:20:48.280 --> 00:20:50.870 align:start position:0% there any early architectural decisions that<00:20:48.640> uh<00:20:48.799> you<00:20:48.960> have 00:20:50.870 --> 00:20:50.880 align:start position:0% that uh you have 00:20:50.880 --> 00:20:53.190 align:start position:0% that uh you have regret 00:20:53.190 --> 00:20:53.200 align:start position:0% regret 00:20:53.200 --> 00:20:57.950 align:start position:0% regret uh<00:20:54.200> yeah<00:20:55.039> um<00:20:56.039> I<00:20:56.159> think<00:20:56.400> I<00:20:56.559> didn't<00:20:56.960> understood 00:20:57.950 --> 00:20:57.960 align:start position:0% uh yeah um I think I didn't understood 00:20:57.960 --> 00:21:00.230 align:start position:0% uh yeah um I think I didn't understood how<00:20:58.360> the<00:20:58.799> calls<00:20:59.280> and<00:20:59.480> everything<00:20:59.799> around<00:21:00.039> that 00:21:00.230 --> 00:21:00.240 align:start position:0% how the calls and everything around that 00:21:00.240 --> 00:21:02.590 align:start position:0% how the calls and everything around that works<00:21:01.240> I<00:21:01.360> still<00:21:01.640> struggle<00:21:02.120> with<00:21:02.280> that<00:21:02.520> I 00:21:02.590 --> 00:21:02.600 align:start position:0% works I still struggle with that I 00:21:02.600 --> 00:21:05.350 align:start position:0% works I still struggle with that I didn't<00:21:02.919> find<00:21:03.159> a<00:21:03.360> good<00:21:03.520> fit<00:21:03.840> on<00:21:04.039> top<00:21:04.240> of<00:21:04.400> it<00:21:05.200> the 00:21:05.350 --> 00:21:05.360 align:start position:0% didn't find a good fit on top of it the 00:21:05.360 --> 00:21:08.870 align:start position:0% didn't find a good fit on top of it the frame<00:21:05.880> and<00:21:06.080> how<00:21:06.320> the<00:21:06.600> frame<00:21:07.320> basically<00:21:08.080> works 00:21:08.870 --> 00:21:08.880 align:start position:0% frame and how the frame basically works 00:21:08.880 --> 00:21:12.110 align:start position:0% frame and how the frame basically works with<00:21:09.240> other<00:21:09.600> frames<00:21:10.559> it<00:21:10.679> seems<00:21:11.080> it's<00:21:11.360> nice<00:21:11.799> but 00:21:12.110 --> 00:21:12.120 align:start position:0% with other frames it seems it's nice but 00:21:12.120 --> 00:21:14.310 align:start position:0% with other frames it seems it's nice but still<00:21:12.480> need<00:21:12.720> to<00:21:12.880> land<00:21:13.240> on<00:21:13.880> the<00:21:14.080> good 00:21:14.310 --> 00:21:14.320 align:start position:0% still need to land on the good 00:21:14.320 --> 00:21:17.950 align:start position:0% still need to land on the good abstructure<00:21:14.840> on<00:21:15.000> top<00:21:15.159> of<00:21:15.760> it<00:21:16.760> uh<00:21:17.159> initially 00:21:17.950 --> 00:21:17.960 align:start position:0% abstructure on top of it uh initially 00:21:17.960 --> 00:21:21.669 align:start position:0% abstructure on top of it uh initially the<00:21:18.440> the<00:21:18.679> calling<00:21:19.200> a<00:21:19.360> sub<00:21:19.679> calling<00:21:20.159> was<00:21:20.840> behind 00:21:21.669 --> 00:21:21.679 align:start position:0% the the calling a sub calling was behind 00:21:21.679 --> 00:21:24.870 align:start position:0% the the calling a sub calling was behind the<00:21:22.039> basically<00:21:22.840> you<00:21:23.120> call<00:21:23.600> your<00:21:24.000> sub<00:21:24.360> call<00:21:24.679> and 00:21:24.870 --> 00:21:24.880 align:start position:0% the basically you call your sub call and 00:21:24.880 --> 00:21:28.149 align:start position:0% the basically you call your sub call and stack<00:21:25.480> became<00:21:25.960> the<00:21:26.200> problem<00:21:27.159> so<00:21:27.679> I<00:21:27.760> needed<00:21:28.039> to 00:21:28.149 --> 00:21:28.159 align:start position:0% stack became the problem so I needed to 00:21:28.159 --> 00:21:32.990 align:start position:0% stack became the problem so I needed to move<00:21:28.600> all<00:21:28.880> that<00:21:29.200> to<00:21:29.919> the<00:21:30.400> the<00:21:30.799> loop<00:21:31.720> so<00:21:32.640> yeah 00:21:32.990 --> 00:21:33.000 align:start position:0% move all that to the the loop so yeah 00:21:33.000 --> 00:21:35.630 align:start position:0% move all that to the the loop so yeah there<00:21:33.120> are<00:21:33.279> few<00:21:33.760> of<00:21:33.960> those 00:21:35.630 --> 00:21:35.640 align:start position:0% there are few of those 00:21:35.640 --> 00:21:38.789 align:start position:0% there are few of those things<00:21:36.640> the<00:21:36.840> next<00:21:37.120> question<00:21:37.919> is<00:21:38.279> uh<00:21:38.480> if<00:21:38.640> there 00:21:38.789 --> 00:21:38.799 align:start position:0% things the next question is uh if there 00:21:38.799 --> 00:21:42.789 align:start position:0% things the next question is uh if there are<00:21:39.200> any<00:21:39.440> plans<00:21:39.880> to<00:21:40.320> natively<00:21:41.000> support<00:21:41.799> ZK<00:21:42.240> VMS 00:21:42.789 --> 00:21:42.799 align:start position:0% are any plans to natively support ZK VMS 00:21:42.799 --> 00:21:46.390 align:start position:0% are any plans to natively support ZK VMS like<00:21:43.320> sp1<00:21:44.279> because<00:21:44.799> currently<00:21:45.799> uh<00:21:45.919> you<00:21:46.080> need 00:21:46.390 --> 00:21:46.400 align:start position:0% like sp1 because currently uh you need 00:21:46.400 --> 00:21:49.830 align:start position:0% like sp1 because currently uh you need to<00:21:46.600> do<00:21:46.919> some<00:21:47.480> uh<00:21:47.679> hockey<00:21:48.279> patches<00:21:48.799> to<00:21:49.480> be<00:21:49.640> able 00:21:49.830 --> 00:21:49.840 align:start position:0% to do some uh hockey patches to be able 00:21:49.840 --> 00:21:52.789 align:start position:0% to do some uh hockey patches to be able to<00:21:50.000> run<00:21:50.240> them<00:21:51.039> uh<00:21:51.200> we<00:21:51.320> should<00:21:51.520> talk<00:21:51.720> with<00:21:51.880> them 00:21:52.789 --> 00:21:52.799 align:start position:0% to run them uh we should talk with them 00:21:52.799 --> 00:21:56.870 align:start position:0% to run them uh we should talk with them basically<00:21:53.799> AV<00:21:54.200> framework<00:21:54.720> is<00:21:55.200> a<00:21:55.960> idea<00:21:56.559> that 00:21:56.870 --> 00:21:56.880 align:start position:0% basically AV framework is a idea that 00:21:56.880 --> 00:21:59.669 align:start position:0% basically AV framework is a idea that basically<00:21:57.520> would<00:21:57.720> allow<00:21:58.600> support 00:21:59.669 --> 00:21:59.679 align:start position:0% basically would allow support 00:21:59.679 --> 00:22:02.470 align:start position:0% basically would allow support this<00:22:00.799> great 00:22:02.470 --> 00:22:02.480 align:start position:0% this great 00:22:02.480 --> 00:22:06.269 align:start position:0% this great um<00:22:03.480> another<00:22:03.960> question<00:22:04.640> again<00:22:04.880> related<00:22:05.279> to<00:22:05.480> zvm 00:22:06.269 --> 00:22:06.279 align:start position:0% um another question again related to zvm 00:22:06.279 --> 00:22:10.669 align:start position:0% um another question again related to zvm so<00:22:07.080> RM<00:22:07.799> is<00:22:07.960> now<00:22:08.159> used<00:22:08.440> on<00:22:08.679> both<00:22:09.120> CPUs<00:22:10.000> and<00:22:10.320> ZK 00:22:10.669 --> 00:22:10.679 align:start position:0% so RM is now used on both CPUs and ZK 00:22:10.679 --> 00:22:13.590 align:start position:0% so RM is now used on both CPUs and ZK VMS<00:22:11.559> and<00:22:11.919> uh<00:22:12.080> these<00:22:12.240> two<00:22:12.480> environments<00:22:13.120> have 00:22:13.590 --> 00:22:13.600 align:start position:0% VMS and uh these two environments have 00:22:13.600 --> 00:22:17.230 align:start position:0% VMS and uh these two environments have very<00:22:13.919> different<00:22:14.600> performance<00:22:15.640> profiles<00:22:16.640> uh 00:22:17.230 --> 00:22:17.240 align:start position:0% very different performance profiles uh 00:22:17.240 --> 00:22:19.669 align:start position:0% very different performance profiles uh how<00:22:17.440> can<00:22:17.600> you<00:22:17.799> optimize<00:22:18.320> for<00:22:18.679> the<00:22:18.840> one<00:22:19.320> or<00:22:19.520> the 00:22:19.669 --> 00:22:19.679 align:start position:0% how can you optimize for the one or the 00:22:19.679 --> 00:22:22.830 align:start position:0% how can you optimize for the one or the other<00:22:20.080> or<00:22:20.440> both<00:22:21.360> in<00:22:21.520> general<00:22:22.080> everything<00:22:22.559> is 00:22:22.830 --> 00:22:22.840 align:start position:0% other or both in general everything is 00:22:22.840 --> 00:22:25.190 align:start position:0% other or both in general everything is Ras<00:22:23.200> compiler<00:22:23.679> so<00:22:23.840> it<00:22:24.440> what<00:22:24.640> compiles 00:22:25.190 --> 00:22:25.200 align:start position:0% Ras compiler so it what compiles 00:22:25.200 --> 00:22:26.909 align:start position:0% Ras compiler so it what compiles optimization<00:22:25.720> of<00:22:25.880> D<00:22:26.159> basically<00:22:26.480> on<00:22:26.640> Ras 00:22:26.909 --> 00:22:26.919 align:start position:0% optimization of D basically on Ras 00:22:26.919 --> 00:22:29.350 align:start position:0% optimization of D basically on Ras compilers<00:22:27.360> so<00:22:27.559> the<00:22:27.720> target<00:22:28.039> is<00:22:28.200> different<00:22:28.919> zkv 00:22:29.350 --> 00:22:29.360 align:start position:0% compilers so the target is different zkv 00:22:29.360 --> 00:22:32.470 align:start position:0% compilers so the target is different zkv mcus<00:22:29.880> risk<00:22:30.200> 5<00:22:31.120> while<00:22:31.320> the<00:22:31.440> CPUs<00:22:31.919> has<00:22:32.200> different 00:22:32.470 --> 00:22:32.480 align:start position:0% mcus risk 5 while the CPUs has different 00:22:32.480 --> 00:22:34.029 align:start position:0% mcus risk 5 while the CPUs has different instruction<00:22:32.919> set<00:22:33.240> that<00:22:33.360> are<00:22:33.480> May<00:22:33.720> more 00:22:34.029 --> 00:22:34.039 align:start position:0% instruction set that are May more 00:22:34.039 --> 00:22:36.789 align:start position:0% instruction set that are May more performant<00:22:35.039> in<00:22:35.200> general<00:22:35.520> I<00:22:35.640> didn't<00:22:36.360> I<00:22:36.520> didn't 00:22:36.789 --> 00:22:36.799 align:start position:0% performant in general I didn't I didn't 00:22:36.799 --> 00:22:39.149 align:start position:0% performant in general I didn't I didn't do<00:22:36.960> the<00:22:37.120> testing<00:22:37.559> on<00:22:37.880> on<00:22:38.039> top<00:22:38.200> of<00:22:38.360> it<00:22:38.720> so<00:22:39.000> that 00:22:39.149 --> 00:22:39.159 align:start position:0% do the testing on on top of it so that 00:22:39.159 --> 00:22:42.310 align:start position:0% do the testing on on top of it so that would<00:22:39.320> be<00:22:39.559> like<00:22:40.080> good<00:22:40.320> way<00:22:40.520> to<00:22:40.799> check<00:22:41.200> those<00:22:42.200> I 00:22:42.310 --> 00:22:42.320 align:start position:0% would be like good way to check those I 00:22:42.320 --> 00:22:44.390 align:start position:0% would be like good way to check those I guess<00:22:42.480> a<00:22:42.640> followup<00:22:43.200> here<00:22:43.400> is<00:22:43.600> and<00:22:44.039> probably 00:22:44.390 --> 00:22:44.400 align:start position:0% guess a followup here is and probably 00:22:44.400 --> 00:22:46.590 align:start position:0% guess a followup here is and probably you<00:22:44.559> haven't<00:22:44.880> check<00:22:45.799> yourself<00:22:46.240> and<00:22:46.440> that's 00:22:46.590 --> 00:22:46.600 align:start position:0% you haven't check yourself and that's 00:22:46.600 --> 00:22:49.669 align:start position:0% you haven't check yourself and that's more<00:22:46.880> about<00:22:47.240> the<00:22:47.360> zvm<00:22:48.120> but<00:22:48.760> have<00:22:49.200> have<00:22:49.360> you<00:22:49.480> any 00:22:49.669 --> 00:22:49.679 align:start position:0% more about the zvm but have have you any 00:22:49.679 --> 00:22:52.990 align:start position:0% more about the zvm but have have you any intuitions<00:22:50.600> that<00:22:51.240> some<00:22:51.840> uh<00:22:52.279> llvm 00:22:52.990 --> 00:22:53.000 align:start position:0% intuitions that some uh llvm 00:22:53.000 --> 00:22:56.789 align:start position:0% intuitions that some uh llvm optimizations<00:22:53.840> might<00:22:54.120> be<00:22:54.440> better<00:22:54.799> for<00:22:55.159> zvm<00:22:56.120> or 00:22:56.789 --> 00:22:56.799 align:start position:0% optimizations might be better for zvm or 00:22:56.799 --> 00:22:58.669 align:start position:0% optimizations might be better for zvm or may<00:22:57.000> be<00:22:57.240> better<00:22:57.480> to<00:22:57.679> not<00:22:57.880> use<00:22:58.039> some<00:22:58.200> optim 00:22:58.669 --> 00:22:58.679 align:start position:0% may be better to not use some optim 00:22:58.679 --> 00:23:00.669 align:start position:0% may be better to not use some optim iations<00:22:59.440> um<00:22:59.679> compiler<00:23:00.039> optimization 00:23:00.669 --> 00:23:00.679 align:start position:0% iations um compiler optimization 00:23:00.679 --> 00:23:02.870 align:start position:0% iations um compiler optimization basically<00:23:01.320> I'm<00:23:01.480> not<00:23:01.640> sure<00:23:02.080> I<00:23:02.200> didn't<00:23:02.440> look<00:23:02.600> at 00:23:02.870 --> 00:23:02.880 align:start position:0% basically I'm not sure I didn't look at 00:23:02.880 --> 00:23:08.310 align:start position:0% basically I'm not sure I didn't look at it<00:23:04.039> great<00:23:05.039> uh<00:23:05.320> so<00:23:06.279> what<00:23:06.480> is<00:23:06.640> missing<00:23:07.240> in<00:23:07.760> our 00:23:08.310 --> 00:23:08.320 align:start position:0% it great uh so what is missing in our 00:23:08.320 --> 00:23:13.830 align:start position:0% it great uh so what is missing in our evm<00:23:08.880> to<00:23:09.039> be<00:23:09.360> more<00:23:09.640> performant<00:23:10.279> than<00:23:11.039> AVM<00:23:11.760> 1<00:23:12.840> uh 00:23:13.830 --> 00:23:13.840 align:start position:0% evm to be more performant than AVM 1 uh 00:23:13.840 --> 00:23:17.630 align:start position:0% evm to be more performant than AVM 1 uh I<00:23:14.159> have<00:23:14.480> some<00:23:14.880> task<00:23:15.279> in<00:23:15.520> my<00:23:16.320> backlog<00:23:17.320> uh<00:23:17.480> they 00:23:17.630 --> 00:23:17.640 align:start position:0% I have some task in my backlog uh they 00:23:17.640 --> 00:23:19.269 align:start position:0% I have some task in my backlog uh they require<00:23:18.000> basically<00:23:18.400> testing<00:23:18.799> every<00:23:18.960> change 00:23:19.269 --> 00:23:19.279 align:start position:0% require basically testing every change 00:23:19.279 --> 00:23:20.669 align:start position:0% require basically testing every change that<00:23:19.480> happen<00:23:19.760> on<00:23:19.919> the<00:23:20.039> performance<00:23:20.480> side 00:23:20.669 --> 00:23:20.679 align:start position:0% that happen on the performance side 00:23:20.679 --> 00:23:23.190 align:start position:0% that happen on the performance side needs<00:23:20.880> to<00:23:21.000> be<00:23:21.200> tested<00:23:21.720> measured<00:23:22.200> then<00:23:22.960> well 00:23:23.190 --> 00:23:23.200 align:start position:0% needs to be tested measured then well 00:23:23.200 --> 00:23:25.470 align:start position:0% needs to be tested measured then well validated<00:23:23.799> that<00:23:24.120> that<00:23:24.760> assumption<00:23:25.240> that<00:23:25.360> I 00:23:25.470 --> 00:23:25.480 align:start position:0% validated that that assumption that I 00:23:25.480 --> 00:23:28.710 align:start position:0% validated that that assumption that I made<00:23:25.720> are<00:23:25.960> correct<00:23:26.960> so<00:23:27.400> I<00:23:27.520> need<00:23:27.760> to<00:23:27.919> look<00:23:28.120> at 00:23:28.710 --> 00:23:28.720 align:start position:0% made are correct so I need to look at 00:23:28.720 --> 00:23:30.710 align:start position:0% made are correct so I need to look at call<00:23:28.919> optimization<00:23:29.640> to<00:23:29.799> check<00:23:30.000> it<00:23:30.240> I<00:23:30.360> need<00:23:30.520> to 00:23:30.710 --> 00:23:30.720 align:start position:0% call optimization to check it I need to 00:23:30.720 --> 00:23:33.590 align:start position:0% call optimization to check it I need to look<00:23:30.960> at<00:23:31.600> the<00:23:31.840> stack<00:23:32.320> verification<00:23:33.039> if<00:23:33.240> this 00:23:33.590 --> 00:23:33.600 align:start position:0% look at the stack verification if this 00:23:33.600 --> 00:23:36.230 align:start position:0% look at the stack verification if this extracted<00:23:34.400> from<00:23:34.720> the<00:23:35.000> instruction<00:23:35.640> to<00:23:35.919> before 00:23:36.230 --> 00:23:36.240 align:start position:0% extracted from the instruction to before 00:23:36.240 --> 00:23:38.510 align:start position:0% extracted from the instruction to before instruction<00:23:36.679> to<00:23:36.799> the<00:23:36.880> main<00:23:37.120> Loop<00:23:37.760> if<00:23:38.000> this<00:23:38.320> is 00:23:38.510 --> 00:23:38.520 align:start position:0% instruction to the main Loop if this is 00:23:38.520 --> 00:23:40.510 align:start position:0% instruction to the main Loop if this is going<00:23:38.760> to<00:23:39.080> affect<00:23:39.640> the 00:23:40.510 --> 00:23:40.520 align:start position:0% going to affect the 00:23:40.520 --> 00:23:44.190 align:start position:0% going to affect the performance<00:23:41.720> MH<00:23:42.720> uh<00:23:43.039> is<00:23:43.159> it<00:23:43.360> easy<00:23:43.640> to<00:23:43.799> add<00:23:44.000> a 00:23:44.190 --> 00:23:44.200 align:start position:0% performance MH uh is it easy to add a 00:23:44.200 --> 00:23:47.350 align:start position:0% performance MH uh is it easy to add a new<00:23:44.960> new<00:23:45.320> promiles<00:23:46.200> yeah<00:23:46.600> it<00:23:46.720> was<00:23:46.960> one<00:23:47.080> of<00:23:47.240> the 00:23:47.350 --> 00:23:47.360 align:start position:0% new new promiles yeah it was one of the 00:23:47.360 --> 00:23:50.430 align:start position:0% new new promiles yeah it was one of the use<00:23:47.720> cases<00:23:48.000> that<00:23:48.200> to<00:23:48.559> say<00:23:48.720> used<00:23:49.000> a<00:23:49.159> lot<00:23:50.080> and<00:23:50.320> it 00:23:50.430 --> 00:23:50.440 align:start position:0% use cases that to say used a lot and it 00:23:50.440 --> 00:23:52.909 align:start position:0% use cases that to say used a lot and it was<00:23:50.960> very<00:23:51.200> easy<00:23:51.480> it's<00:23:51.679> one<00:23:51.880> of<00:23:52.080> the<00:23:52.600> biggest 00:23:52.909 --> 00:23:52.919 align:start position:0% was very easy it's one of the biggest 00:23:52.919 --> 00:23:56.230 align:start position:0% was very easy it's one of the biggest use<00:23:53.240> cases<00:23:53.679> of<00:23:54.679> um<00:23:55.080> how<00:23:55.279> you<00:23:55.400> can<00:23:55.640> extend 00:23:56.230 --> 00:23:56.240 align:start position:0% use cases of um how you can extend 00:23:56.240 --> 00:23:59.630 align:start position:0% use cases of um how you can extend easiest<00:23:56.799> and<00:23:57.159> biggest<00:23:58.000> way<00:23:58.240> to<00:23:58.480> extend 00:23:59.630 --> 00:23:59.640 align:start position:0% easiest and biggest way to extend 00:23:59.640 --> 00:24:03.230 align:start position:0% easiest and biggest way to extend AR<00:24:00.640> what<00:24:01.120> uh<00:24:01.480> the<00:24:01.640> most<00:24:01.919> interesting<00:24:02.480> use<00:24:02.840> case 00:24:03.230 --> 00:24:03.240 align:start position:0% AR what uh the most interesting use case 00:24:03.240 --> 00:24:06.750 align:start position:0% AR what uh the most interesting use case that<00:24:03.600> you<00:24:03.720> have<00:24:03.880> seen<00:24:04.080> so 00:24:06.750 --> 00:24:06.760 align:start position:0% 00:24:06.760 --> 00:24:08.470 align:start position:0% far 00:24:08.470 --> 00:24:08.480 align:start position:0% far 00:24:08.480 --> 00:24:13.630 align:start position:0% far um<00:24:09.480> Z<00:24:09.760> kvms<00:24:10.520> was<00:24:11.279> really<00:24:11.840> really<00:24:12.640> unexpected 00:24:13.630 --> 00:24:13.640 align:start position:0% um Z kvms was really really unexpected 00:24:13.640 --> 00:24:15.870 align:start position:0% um Z kvms was really really unexpected to<00:24:13.799> be<00:24:13.960> honest<00:24:14.240> it<00:24:14.440> just<00:24:14.640> landed<00:24:15.240> it<00:24:15.360> was<00:24:15.559> like 00:24:15.870 --> 00:24:15.880 align:start position:0% to be honest it just landed it was like 00:24:15.880 --> 00:24:17.510 align:start position:0% to be honest it just landed it was like Hey<00:24:16.039> it<00:24:16.159> can<00:24:16.279> be<00:24:16.400> used<00:24:16.640> in<00:24:16.760> that<00:24:16.960> way<00:24:17.159> I<00:24:17.240> didn't 00:24:17.510 --> 00:24:17.520 align:start position:0% Hey it can be used in that way I didn't 00:24:17.520 --> 00:24:21.269 align:start position:0% Hey it can be used in that way I didn't expect<00:24:17.840> that<00:24:18.520> I<00:24:18.840> made<00:24:19.120> it<00:24:19.320> nod<00:24:20.039> to<00:24:20.200> use<00:24:20.360> it<00:24:20.520> in 00:24:21.269 --> 00:24:21.279 align:start position:0% expect that I made it nod to use it in 00:24:21.279 --> 00:24:23.750 align:start position:0% expect that I made it nod to use it in maybe<00:24:21.640> front<00:24:21.960> ends<00:24:22.520> so<00:24:22.799> that<00:24:23.120> JavaScript<00:24:23.679> can 00:24:23.750 --> 00:24:23.760 align:start position:0% maybe front ends so that JavaScript can 00:24:23.760 --> 00:24:25.830 align:start position:0% maybe front ends so that JavaScript can be<00:24:23.880> implemented<00:24:24.240> on<00:24:24.400> top<00:24:24.559> of<00:24:24.720> it<00:24:25.320> maybe<00:24:25.600> it<00:24:25.720> can 00:24:25.830 --> 00:24:25.840 align:start position:0% be implemented on top of it maybe it can 00:24:25.840 --> 00:24:29.269 align:start position:0% be implemented on top of it maybe it can be<00:24:25.960> used<00:24:26.200> in<00:24:26.440> vasm<00:24:27.200> as<00:24:27.480> the<00:24:28.120> like 00:24:29.269 --> 00:24:29.279 align:start position:0% be used in vasm as the like 00:24:29.279 --> 00:24:33.750 align:start position:0% be used in vasm as the like some<00:24:29.600> project<00:24:30.000> that<00:24:30.240> do<00:24:30.919> that<00:24:31.640> b<00:24:32.640> but<00:24:32.880> zvm<00:24:33.559> was 00:24:33.750 --> 00:24:33.760 align:start position:0% some project that do that b but zvm was 00:24:33.760 --> 00:24:36.950 align:start position:0% some project that do that b but zvm was like<00:24:34.039> unexpected<00:24:34.919> surprise<00:24:35.919> and<00:24:36.120> was<00:24:36.559> amazing 00:24:36.950 --> 00:24:36.960 align:start position:0% like unexpected surprise and was amazing 00:24:36.960 --> 00:24:37.630 align:start position:0% like unexpected surprise and was amazing in 00:24:37.630 --> 00:24:37.640 align:start position:0% in 00:24:37.640 --> 00:24:40.269 align:start position:0% in general<00:24:38.640> like<00:24:38.919> thank<00:24:39.159> again<00:24:39.399> our<00:24:39.600> speaker 00:24:40.269 --> 00:24:40.279 align:start position:0% general like thank again our speaker 00:24:40.279 --> 00:24:43.190 align:start position:0% general like thank again our speaker Dragon<00:24:40.799> for<00:24:41.480> the<00:24:41.640> excellent<00:24:42.200> presentation 00:24:43.190 --> 00:24:43.200 align:start position:0% Dragon for the excellent presentation 00:24:43.200 --> 00:24:46.360 align:start position:0% Dragon for the excellent presentation thank<00:24:43.360> you