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.310 align:start position:0% [Music] 00:00:09.310 --> 00:00:09.320 align:start position:0% [Music] 00:00:09.320 --> 00:00:11.070 align:start position:0% [Music] some<00:00:09.400> of<00:00:09.480> the<00:00:09.599> reasons<00:00:09.960> we<00:00:10.400> want<00:00:10.719> we<00:00:10.840> want<00:00:10.960> to 00:00:11.070 --> 00:00:11.080 align:start position:0% some of the reasons we want we want to 00:00:11.080 --> 00:00:14.310 align:start position:0% some of the reasons we want we want to put<00:00:11.280> eof<00:00:11.759> into<00:00:12.040> the<00:00:12.679> into<00:00:13.320> uh 00:00:14.310 --> 00:00:14.320 align:start position:0% put eof into the into uh 00:00:14.320 --> 00:00:17.390 align:start position:0% put eof into the into uh evm<00:00:15.320> so<00:00:15.839> about<00:00:16.119> two<00:00:16.320> years<00:00:16.800> uh<00:00:17.160> in<00:00:17.279> the 00:00:17.390 --> 00:00:17.400 align:start position:0% evm so about two years uh in the 00:00:17.400 --> 00:00:19.150 align:start position:0% evm so about two years uh in the beginning<00:00:17.840> the<00:00:17.960> legend<00:00:18.279> has<00:00:18.480> it<00:00:18.640> that<00:00:18.760> the<00:00:18.880> two 00:00:19.150 --> 00:00:19.160 align:start position:0% beginning the legend has it that the two 00:00:19.160 --> 00:00:20.950 align:start position:0% beginning the legend has it that the two two<00:00:19.279> of<00:00:19.400> the<00:00:19.480> early<00:00:19.680> core<00:00:19.920> developers<00:00:20.760> were 00:00:20.950 --> 00:00:20.960 align:start position:0% two of the early core developers were 00:00:20.960 --> 00:00:22.950 align:start position:0% two of the early core developers were responsible<00:00:21.359> for<00:00:21.480> writing<00:00:21.800> evm<00:00:22.560> and<00:00:22.720> they<00:00:22.840> did 00:00:22.950 --> 00:00:22.960 align:start position:0% responsible for writing evm and they did 00:00:22.960 --> 00:00:25.470 align:start position:0% responsible for writing evm and they did it<00:00:23.119> over<00:00:23.320> the<00:00:23.439> weekend<00:00:24.240> um<00:00:24.439> and<00:00:25.000> it<00:00:25.160> wasn't 00:00:25.470 --> 00:00:25.480 align:start position:0% it over the weekend um and it wasn't 00:00:25.480 --> 00:00:26.990 align:start position:0% it over the weekend um and it wasn't perfect<00:00:25.840> but<00:00:25.960> it<00:00:26.080> was<00:00:26.279> it<00:00:26.359> was<00:00:26.519> really<00:00:26.760> good 00:00:26.990 --> 00:00:27.000 align:start position:0% perfect but it was it was really good 00:00:27.000 --> 00:00:28.349 align:start position:0% perfect but it was it was really good and<00:00:27.119> it<00:00:27.240> got<00:00:27.400> almost<00:00:27.679> everything<00:00:28.039> right<00:00:28.279> I 00:00:28.349 --> 00:00:28.359 align:start position:0% and it got almost everything right I 00:00:28.359 --> 00:00:29.710 align:start position:0% and it got almost everything right I think<00:00:28.480> the<00:00:28.560> only<00:00:28.720> thing<00:00:28.840> that<00:00:28.960> they<00:00:29.080> changed 00:00:29.710 --> 00:00:29.720 align:start position:0% think the only thing that they changed 00:00:29.720 --> 00:00:30.990 align:start position:0% think the only thing that they changed before<00:00:30.000> before<00:00:30.119> it<00:00:30.240> went<00:00:30.439> public<00:00:30.720> was<00:00:30.840> they 00:00:30.990 --> 00:00:31.000 align:start position:0% before before it went public was they 00:00:31.000 --> 00:00:33.110 align:start position:0% before before it went public was they added<00:00:31.800> um<00:00:31.960> one<00:00:32.119> of<00:00:32.200> the<00:00:32.279> C++<00:00:32.880> client 00:00:33.110 --> 00:00:33.120 align:start position:0% added um one of the C++ client 00:00:33.120 --> 00:00:35.430 align:start position:0% added um one of the C++ client developers<00:00:33.559> who's<00:00:33.760> on<00:00:33.920> tpon<00:00:34.520> now<00:00:35.040> asked<00:00:35.320> them 00:00:35.430 --> 00:00:35.440 align:start position:0% developers who's on tpon now asked them 00:00:35.440 --> 00:00:38.310 align:start position:0% developers who's on tpon now asked them to<00:00:35.600> add<00:00:35.800> the<00:00:36.040> jump<00:00:36.320> dust<00:00:37.040> operation<00:00:37.480> in<00:00:37.680> there 00:00:38.310 --> 00:00:38.320 align:start position:0% to add the jump dust operation in there 00:00:38.320 --> 00:00:40.110 align:start position:0% to add the jump dust operation in there for<00:00:38.640> jumps<00:00:39.000> to<00:00:39.280> signal<00:00:39.600> that<00:00:39.800> this<00:00:39.920> is<00:00:40.000> a 00:00:40.110 --> 00:00:40.120 align:start position:0% for jumps to signal that this is a 00:00:40.120 --> 00:00:41.869 align:start position:0% for jumps to signal that this is a correct<00:00:40.399> place<00:00:40.559> to<00:00:40.680> land<00:00:41.320> and<00:00:41.440> they<00:00:41.559> needed 00:00:41.869 --> 00:00:41.879 align:start position:0% correct place to land and they needed 00:00:41.879 --> 00:00:44.470 align:start position:0% correct place to land and they needed that<00:00:42.000> for<00:00:42.280> jit<00:00:42.600> compilation<00:00:43.480> for<00:00:43.680> the<00:00:43.760> llvm 00:00:44.470 --> 00:00:44.480 align:start position:0% that for jit compilation for the llvm 00:00:44.480 --> 00:00:46.150 align:start position:0% that for jit compilation for the llvm and<00:00:44.559> that's<00:00:44.680> an<00:00:44.800> important<00:00:45.160> thing<00:00:45.320> to<00:00:45.760> to<00:00:45.960> keep 00:00:46.150 --> 00:00:46.160 align:start position:0% and that's an important thing to to keep 00:00:46.160 --> 00:00:48.069 align:start position:0% and that's an important thing to to keep in<00:00:46.320> mind<00:00:46.600> is<00:00:46.760> that<00:00:47.000> this<00:00:47.520> is<00:00:47.680> that<00:00:47.800> jit 00:00:48.069 --> 00:00:48.079 align:start position:0% in mind is that this is that jit 00:00:48.079 --> 00:00:49.790 align:start position:0% in mind is that this is that jit compilation<00:00:48.600> is<00:00:48.840> is<00:00:49.199> going<00:00:49.320> to<00:00:49.399> be<00:00:49.480> a<00:00:49.559> running 00:00:49.790 --> 00:00:49.800 align:start position:0% compilation is is going to be a running 00:00:49.800 --> 00:00:50.869 align:start position:0% compilation is is going to be a running theme<00:00:50.039> it's<00:00:50.160> going<00:00:50.280> to<00:00:50.360> come<00:00:50.480> up<00:00:50.640> with<00:00:50.760> with 00:00:50.869 --> 00:00:50.879 align:start position:0% theme it's going to come up with with 00:00:50.879 --> 00:00:53.270 align:start position:0% theme it's going to come up with with the<00:00:51.000> Z<00:00:51.199> kvms<00:00:52.199> so<00:00:52.399> they<00:00:52.520> added<00:00:52.760> that<00:00:52.879> feature 00:00:53.270 --> 00:00:53.280 align:start position:0% the Z kvms so they added that feature 00:00:53.280 --> 00:00:54.549 align:start position:0% the Z kvms so they added that feature and<00:00:53.399> it<00:00:53.480> was<00:00:53.640> good<00:00:53.760> enough<00:00:54.120> it<00:00:54.239> wasn't<00:00:54.440> the 00:00:54.549 --> 00:00:54.559 align:start position:0% and it was good enough it wasn't the 00:00:54.559 --> 00:00:56.110 align:start position:0% and it was good enough it wasn't the thing<00:00:54.719> with<00:00:54.840> the<00:00:54.960> most<00:00:55.199> problems<00:00:55.520> that<00:00:55.680> was 00:00:56.110 --> 00:00:56.120 align:start position:0% thing with the most problems that was 00:00:56.120 --> 00:00:57.510 align:start position:0% thing with the most problems that was you<00:00:56.239> know<00:00:56.440> stuff<00:00:56.719> like<00:00:56.879> you<00:00:56.960> know<00:00:57.120> sinking 00:00:57.510 --> 00:00:57.520 align:start position:0% you know stuff like you know sinking 00:00:57.520 --> 00:00:59.670 align:start position:0% you know stuff like you know sinking nodes<00:00:57.960> and<00:00:58.120> keeping<00:00:58.440> consensus<00:00:59.079> together<00:00:59.519> so 00:00:59.670 --> 00:00:59.680 align:start position:0% nodes and keeping consensus together so 00:00:59.680 --> 00:01:01.830 align:start position:0% nodes and keeping consensus together so they<00:01:00.000> moved<00:01:00.199> on<00:01:00.359> from<00:01:00.559> that<00:01:01.120> so<00:01:01.320> it<00:01:01.480> it<00:01:01.600> worked 00:01:01.830 --> 00:01:01.840 align:start position:0% they moved on from that so it it worked 00:01:01.840 --> 00:01:04.189 align:start position:0% they moved on from that so it it worked but<00:01:01.960> there<00:01:02.039> was<00:01:02.280> still<00:01:03.239> um<00:01:03.399> a<00:01:03.519> few<00:01:03.719> things<00:01:04.040> that 00:01:04.189 --> 00:01:04.199 align:start position:0% but there was still um a few things that 00:01:04.199 --> 00:01:05.550 align:start position:0% but there was still um a few things that that<00:01:04.280> needed<00:01:04.519> to<00:01:04.600> be<00:01:04.720> added<00:01:05.000> early<00:01:05.199> on<00:01:05.360> into 00:01:05.550 --> 00:01:05.560 align:start position:0% that needed to be added early on into 00:01:05.560 --> 00:01:07.710 align:start position:0% that needed to be added early on into the<00:01:05.640> evm<00:01:06.600> call<00:01:06.880> code<00:01:07.080> didn't<00:01:07.280> work<00:01:07.479> like<00:01:07.600> they 00:01:07.710 --> 00:01:07.720 align:start position:0% the evm call code didn't work like they 00:01:07.720 --> 00:01:08.870 align:start position:0% the evm call code didn't work like they thought<00:01:07.880> it<00:01:08.040> would<00:01:08.200> so<00:01:08.320> they<00:01:08.479> replaced<00:01:08.759> it 00:01:08.870 --> 00:01:08.880 align:start position:0% thought it would so they replaced it 00:01:08.880 --> 00:01:10.749 align:start position:0% thought it would so they replaced it with<00:01:09.040> delegate<00:01:09.439> call<00:01:10.200> um<00:01:10.320> there<00:01:10.400> were<00:01:10.560> some 00:01:10.749 --> 00:01:10.759 align:start position:0% with delegate call um there were some 00:01:10.759 --> 00:01:12.270 align:start position:0% with delegate call um there were some performance<00:01:11.200> issues<00:01:11.560> with<00:01:11.680> some<00:01:11.799> of<00:01:11.920> the<00:01:12.000> op 00:01:12.270 --> 00:01:12.280 align:start position:0% performance issues with some of the op 00:01:12.280 --> 00:01:14.030 align:start position:0% performance issues with some of the op codes<00:01:12.759> so<00:01:12.960> they<00:01:13.080> increased<00:01:13.439> the<00:01:13.560> prices<00:01:13.840> on 00:01:14.030 --> 00:01:14.040 align:start position:0% codes so they increased the prices on 00:01:14.040 --> 00:01:17.149 align:start position:0% codes so they increased the prices on some<00:01:14.159> of<00:01:14.280> them<00:01:14.759> appropriately<00:01:15.799> um<00:01:16.799> the<00:01:17.000> there 00:01:17.149 --> 00:01:17.159 align:start position:0% some of them appropriately um the there 00:01:17.159 --> 00:01:19.710 align:start position:0% some of them appropriately um the there is<00:01:17.360> a<00:01:17.560> bit<00:01:17.759> shifting<00:01:18.040> math<00:01:18.400> wasn't<00:01:19.000> uh<00:01:19.439> wasn't 00:01:19.710 --> 00:01:19.720 align:start position:0% is a bit shifting math wasn't uh wasn't 00:01:19.720 --> 00:01:21.670 align:start position:0% is a bit shifting math wasn't uh wasn't exactly<00:01:20.040> what<00:01:20.159> they<00:01:20.320> expected<00:01:20.640> it<00:01:20.759> to<00:01:20.880> be<00:01:21.600> uh 00:01:21.670 --> 00:01:21.680 align:start position:0% exactly what they expected it to be uh 00:01:21.680 --> 00:01:23.590 align:start position:0% exactly what they expected it to be uh so<00:01:21.840> they<00:01:21.920> added<00:01:22.159> some<00:01:22.280> bit<00:01:22.479> shifting<00:01:22.759> code<00:01:23.439> uh 00:01:23.590 --> 00:01:23.600 align:start position:0% so they added some bit shifting code uh 00:01:23.600 --> 00:01:24.910 align:start position:0% so they added some bit shifting code uh and<00:01:23.799> there<00:01:23.960> are<00:01:24.079> some<00:01:24.159> developer<00:01:24.560> experience 00:01:24.910 --> 00:01:24.920 align:start position:0% and there are some developer experience 00:01:24.920 --> 00:01:26.429 align:start position:0% and there are some developer experience requests<00:01:25.320> to<00:01:25.439> put<00:01:25.560> in<00:01:25.680> things<00:01:25.880> like<00:01:26.000> the<00:01:26.079> rever 00:01:26.429 --> 00:01:26.439 align:start position:0% requests to put in things like the rever 00:01:26.439 --> 00:01:28.270 align:start position:0% requests to put in things like the rever op<00:01:26.640> code<00:01:27.200> so<00:01:27.360> you<00:01:27.439> could<00:01:27.640> signal<00:01:28.000> to<00:01:28.159> the 00:01:28.270 --> 00:01:28.280 align:start position:0% op code so you could signal to the 00:01:28.280 --> 00:01:30.510 align:start position:0% op code so you could signal to the system<00:01:28.600> that<00:01:28.799> when<00:01:29.079> when<00:01:29.240> a<00:01:29.439> call<00:01:29.640> fil<00:01:29.920> failed 00:01:30.510 --> 00:01:30.520 align:start position:0% system that when when a call fil failed 00:01:30.520 --> 00:01:32.109 align:start position:0% system that when when a call fil failed in<00:01:30.640> an<00:01:30.799> unexpected<00:01:31.320> way<00:01:31.479> that<00:01:31.600> you<00:01:31.680> could<00:01:31.880> pass 00:01:32.109 --> 00:01:32.119 align:start position:0% in an unexpected way that you could pass 00:01:32.119 --> 00:01:34.149 align:start position:0% in an unexpected way that you could pass data<00:01:32.439> back<00:01:32.720> within<00:01:32.960> the<00:01:33.119> stack<00:01:33.680> and<00:01:33.840> outside 00:01:34.149 --> 00:01:34.159 align:start position:0% data back within the stack and outside 00:01:34.159 --> 00:01:36.190 align:start position:0% data back within the stack and outside of<00:01:34.320> the<00:01:34.479> stack<00:01:35.000> and<00:01:35.159> also<00:01:35.399> some<00:01:35.560> pre-compiled 00:01:36.190 --> 00:01:36.200 align:start position:0% of the stack and also some pre-compiled 00:01:36.200 --> 00:01:37.670 align:start position:0% of the stack and also some pre-compiled for<00:01:36.360> some<00:01:36.640> Advanced<00:01:36.960> cryptography<00:01:37.520> were 00:01:37.670 --> 00:01:37.680 align:start position:0% for some Advanced cryptography were 00:01:37.680 --> 00:01:38.710 align:start position:0% for some Advanced cryptography were added<00:01:37.960> because<00:01:38.200> that's<00:01:38.360> just<00:01:38.520> too 00:01:38.710 --> 00:01:38.720 align:start position:0% added because that's just too 00:01:38.720 --> 00:01:41.590 align:start position:0% added because that's just too inefficient<00:01:39.439> for<00:01:39.600> the<00:01:39.720> evm<00:01:40.079> to 00:01:41.590 --> 00:01:41.600 align:start position:0% inefficient for the evm to 00:01:41.600 --> 00:01:43.630 align:start position:0% inefficient for the evm to execute<00:01:42.600> so<00:01:42.759> one<00:01:42.880> of<00:01:43.000> the<00:01:43.119> first<00:01:43.399> big 00:01:43.630 --> 00:01:43.640 align:start position:0% execute so one of the first big 00:01:43.640 --> 00:01:45.350 align:start position:0% execute so one of the first big proposals<00:01:44.119> to<00:01:44.280> do<00:01:44.479> more<00:01:44.680> than<00:01:44.840> just<00:01:45.040> add<00:01:45.200> one 00:01:45.350 --> 00:01:45.360 align:start position:0% proposals to do more than just add one 00:01:45.360 --> 00:01:47.709 align:start position:0% proposals to do more than just add one or<00:01:45.479> two<00:01:45.600> small<00:01:45.880> things<00:01:46.040> to<00:01:46.159> the<00:01:46.280> evm<00:01:46.960> was<00:01:47.159> EIP 00:01:47.709 --> 00:01:47.719 align:start position:0% or two small things to the evm was EIP 00:01:47.719 --> 00:01:50.870 align:start position:0% or two small things to the evm was EIP 615<00:01:48.640> that's<00:01:48.799> a<00:01:48.960> really<00:01:49.200> low<00:01:49.439> EIP<00:01:49.920> number<00:01:50.759> um 00:01:50.870 --> 00:01:50.880 align:start position:0% 615 that's a really low EIP number um 00:01:50.880 --> 00:01:53.910 align:start position:0% 615 that's a really low EIP number um and<00:01:51.000> it<00:01:51.079> was<00:01:51.360> proposing<00:01:52.360> um<00:01:53.000> the<00:01:53.240> the<00:01:53.399> Top<00:01:53.640> Line 00:01:53.910 --> 00:01:53.920 align:start position:0% and it was proposing um the the Top Line 00:01:53.920 --> 00:01:55.429 align:start position:0% and it was proposing um the the Top Line in<00:01:54.040> the<00:01:54.159> motivation<00:01:54.600> says<00:01:54.840> the<00:01:55.000> design<00:01:55.240> of<00:01:55.320> the 00:01:55.429 --> 00:01:55.439 align:start position:0% in the motivation says the design of the 00:01:55.439 --> 00:01:57.749 align:start position:0% in the motivation says the design of the evm<00:01:55.799> makes<00:01:56.039> near<00:01:56.280> linear<00:01:56.680> time<00:01:57.000> compilation 00:01:57.749 --> 00:01:57.759 align:start position:0% evm makes near linear time compilation 00:01:57.759 --> 00:02:00.109 align:start position:0% evm makes near linear time compilation to<00:01:57.960> machine<00:01:58.280> code<00:01:58.840> difficult<00:01:59.560> um<00:01:59.719> the<00:01:59.920> jump 00:02:00.109 --> 00:02:00.119 align:start position:0% to machine code difficult um the jump 00:02:00.119 --> 00:02:01.510 align:start position:0% to machine code difficult um the jump dust<00:02:00.399> analysis<00:02:00.799> and<00:02:00.920> a<00:02:01.000> few<00:02:01.200> other<00:02:01.360> things 00:02:01.510 --> 00:02:01.520 align:start position:0% dust analysis and a few other things 00:02:01.520 --> 00:02:04.190 align:start position:0% dust analysis and a few other things that<00:02:01.640> were<00:02:01.799> in<00:02:01.960> there<00:02:02.759> um<00:02:03.360> a<00:02:03.479> malicious<00:02:03.920> person 00:02:04.190 --> 00:02:04.200 align:start position:0% that were in there um a malicious person 00:02:04.200 --> 00:02:06.230 align:start position:0% that were in there um a malicious person could<00:02:04.360> write<00:02:04.600> a<00:02:04.719> piece<00:02:04.920> of<00:02:05.039> evm<00:02:05.479> software<00:02:06.119> that 00:02:06.230 --> 00:02:06.240 align:start position:0% could write a piece of evm software that 00:02:06.240 --> 00:02:08.229 align:start position:0% could write a piece of evm software that would<00:02:06.360> take<00:02:06.520> a<00:02:06.719> really<00:02:06.920> long<00:02:07.119> time<00:02:07.280> to<00:02:07.479> compile 00:02:08.229 --> 00:02:08.239 align:start position:0% would take a really long time to compile 00:02:08.239 --> 00:02:09.869 align:start position:0% would take a really long time to compile and<00:02:08.440> provide<00:02:08.840> another<00:02:09.160> form<00:02:09.360> of<00:02:09.520> attack<00:02:09.759> to 00:02:09.869 --> 00:02:09.879 align:start position:0% and provide another form of attack to 00:02:09.879 --> 00:02:12.030 align:start position:0% and provide another form of attack to the<00:02:09.959> evm<00:02:10.399> so<00:02:10.560> that's<00:02:10.800> why<00:02:11.480> uh<00:02:11.599> it<00:02:11.720> wasn't 00:02:12.030 --> 00:02:12.040 align:start position:0% the evm so that's why uh it wasn't 00:02:12.040 --> 00:02:14.790 align:start position:0% the evm so that's why uh it wasn't really<00:02:12.800> you<00:02:12.879> know<00:02:13.040> evm<00:02:13.920> uh<00:02:14.239> Justin<00:02:14.599> Time 00:02:14.790 --> 00:02:14.800 align:start position:0% really you know evm uh Justin Time 00:02:14.800 --> 00:02:16.390 align:start position:0% really you know evm uh Justin Time compilation<00:02:15.239> really<00:02:15.440> hasn't<00:02:15.640> gone<00:02:15.879> too<00:02:16.040> far 00:02:16.390 --> 00:02:16.400 align:start position:0% compilation really hasn't gone too far 00:02:16.400 --> 00:02:19.390 align:start position:0% compilation really hasn't gone too far it's<00:02:16.560> because<00:02:16.760> of<00:02:16.879> issues<00:02:17.200> like<00:02:17.440> that<00:02:18.319> and<00:02:18.680> so 00:02:19.390 --> 00:02:19.400 align:start position:0% it's because of issues like that and so 00:02:19.400 --> 00:02:20.990 align:start position:0% it's because of issues like that and so this<00:02:19.640> was<00:02:19.879> designed<00:02:20.319> to<00:02:20.480> address<00:02:20.760> some<00:02:20.879> of 00:02:20.990 --> 00:02:21.000 align:start position:0% this was designed to address some of 00:02:21.000 --> 00:02:22.589 align:start position:0% this was designed to address some of those<00:02:21.160> issues<00:02:21.840> and<00:02:21.959> the<00:02:22.040> biggest<00:02:22.280> things<00:02:22.440> they 00:02:22.589 --> 00:02:22.599 align:start position:0% those issues and the biggest things they 00:02:22.599 --> 00:02:24.390 align:start position:0% those issues and the biggest things they added<00:02:22.920> was<00:02:23.120> they<00:02:23.319> provided<00:02:23.680> a<00:02:23.879> static<00:02:24.200> jump 00:02:24.390 --> 00:02:24.400 align:start position:0% added was they provided a static jump 00:02:24.400 --> 00:02:26.430 align:start position:0% added was they provided a static jump instead<00:02:24.640> of<00:02:24.720> a<00:02:24.840> relative<00:02:25.280> jump<00:02:25.879> and<00:02:26.000> they<00:02:26.160> also 00:02:26.430 --> 00:02:26.440 align:start position:0% instead of a relative jump and they also 00:02:26.440 --> 00:02:29.550 align:start position:0% instead of a relative jump and they also added<00:02:26.920> um<00:02:27.440> subes<00:02:28.440> and<00:02:28.840> the<00:02:28.959> last<00:02:29.160> three<00:02:29.319> items 00:02:29.550 --> 00:02:29.560 align:start position:0% added um subes and the last three items 00:02:29.560 --> 00:02:30.509 align:start position:0% added um subes and the last three items if<00:02:29.640> you<00:02:29.720> look<00:02:29.920> look<00:02:30.000> at<00:02:30.080> them<00:02:30.160> and<00:02:30.239> squint 00:02:30.509 --> 00:02:30.519 align:start position:0% if you look look at them and squint 00:02:30.519 --> 00:02:31.949 align:start position:0% if you look look at them and squint really<00:02:30.720> hard<00:02:30.879> it<00:02:31.000> looks<00:02:31.200> a<00:02:31.319> lot<00:02:31.519> like<00:02:31.680> what<00:02:31.800> we 00:02:31.949 --> 00:02:31.959 align:start position:0% really hard it looks a lot like what we 00:02:31.959 --> 00:02:34.309 align:start position:0% really hard it looks a lot like what we have<00:02:32.120> designed<00:02:32.440> in<00:02:32.720> eof<00:02:33.720> um<00:02:33.920> they<00:02:34.040> have<00:02:34.160> a 00:02:34.309 --> 00:02:34.319 align:start position:0% have designed in eof um they have a 00:02:34.319 --> 00:02:36.550 align:start position:0% have designed in eof um they have a begin<00:02:34.640> data<00:02:34.920> section<00:02:35.200> to<00:02:35.360> say<00:02:35.920> anything<00:02:36.319> after 00:02:36.550 --> 00:02:36.560 align:start position:0% begin data section to say anything after 00:02:36.560 --> 00:02:39.070 align:start position:0% begin data section to say anything after this<00:02:36.720> op<00:02:36.959> code<00:02:37.160> is<00:02:37.400> data<00:02:38.200> they<00:02:38.360> have<00:02:38.560> an<00:02:38.760> object 00:02:39.070 --> 00:02:39.080 align:start position:0% this op code is data they have an object 00:02:39.080 --> 00:02:41.830 align:start position:0% this op code is data they have an object header<00:02:39.400> that<00:02:39.519> says<00:02:40.159> this<00:02:40.280> is<00:02:40.440> evm<00:02:40.959> code<00:02:41.680> and 00:02:41.830 --> 00:02:41.840 align:start position:0% header that says this is evm code and 00:02:41.840 --> 00:02:43.390 align:start position:0% header that says this is evm code and they<00:02:41.959> have<00:02:42.159> code<00:02:42.400> validation<00:02:42.840> rules<00:02:43.120> that<00:02:43.239> say 00:02:43.390 --> 00:02:43.400 align:start position:0% they have code validation rules that say 00:02:43.400 --> 00:02:45.270 align:start position:0% they have code validation rules that say that<00:02:43.560> everything<00:02:43.879> between<00:02:44.680> the<00:02:44.879> beginning<00:02:45.159> of 00:02:45.270 --> 00:02:45.280 align:start position:0% that everything between the beginning of 00:02:45.280 --> 00:02:47.030 align:start position:0% that everything between the beginning of the<00:02:45.400> header<00:02:46.000> and<00:02:46.120> the<00:02:46.200> beginning<00:02:46.480> of<00:02:46.560> the<00:02:46.680> data 00:02:47.030 --> 00:02:47.040 align:start position:0% the header and the beginning of the data 00:02:47.040 --> 00:02:49.390 align:start position:0% the header and the beginning of the data has<00:02:47.200> to<00:02:47.319> be<00:02:47.560> valid<00:02:47.920> executable<00:02:48.519> code<00:02:49.159> if<00:02:49.280> you 00:02:49.390 --> 00:02:49.400 align:start position:0% has to be valid executable code if you 00:02:49.400 --> 00:02:51.030 align:start position:0% has to be valid executable code if you stand<00:02:49.680> back<00:02:49.800> and<00:02:49.920> squint<00:02:50.239> your<00:02:50.360> eyes<00:02:50.879> that's 00:02:51.030 --> 00:02:51.040 align:start position:0% stand back and squint your eyes that's 00:02:51.040 --> 00:02:53.869 align:start position:0% stand back and squint your eyes that's some<00:02:51.159> of<00:02:51.280> the<00:02:51.440> key<00:02:51.599> features<00:02:51.920> of<00:02:52.120> eof<00:02:53.120> so<00:02:53.560> way 00:02:53.869 --> 00:02:53.879 align:start position:0% some of the key features of eof so way 00:02:53.879 --> 00:02:56.750 align:start position:0% some of the key features of eof so way back<00:02:54.120> in<00:02:54.519> 2017<00:02:55.519> a<00:02:55.640> lot<00:02:55.760> of<00:02:55.879> the<00:02:55.959> needs<00:02:56.200> for<00:02:56.360> eof 00:02:56.750 --> 00:02:56.760 align:start position:0% back in 2017 a lot of the needs for eof 00:02:56.760 --> 00:02:58.830 align:start position:0% back in 2017 a lot of the needs for eof were<00:02:56.959> recognized<00:02:57.560> so<00:02:57.720> the<00:02:58.120> obvious<00:02:58.519> question 00:02:58.830 --> 00:02:58.840 align:start position:0% were recognized so the obvious question 00:02:58.840 --> 00:03:01.309 align:start position:0% were recognized so the obvious question is<00:02:59.519> well<00:03:00.000> why<00:03:00.200> wasn't<00:03:00.519> this<00:03:00.760> done<00:03:01.000> at<00:03:01.159> that 00:03:01.309 --> 00:03:01.319 align:start position:0% is well why wasn't this done at that 00:03:01.319 --> 00:03:02.910 align:start position:0% is well why wasn't this done at that point<00:03:01.480> in<00:03:01.680> time<00:03:01.920> we<00:03:02.080> had<00:03:02.200> all<00:03:02.319> the<00:03:02.519> stuff<00:03:02.720> in 00:03:02.910 --> 00:03:02.920 align:start position:0% point in time we had all the stuff in 00:03:02.920 --> 00:03:04.910 align:start position:0% point in time we had all the stuff in place<00:03:03.480> to<00:03:03.680> get<00:03:03.799> it 00:03:04.910 --> 00:03:04.920 align:start position:0% place to get it 00:03:04.920 --> 00:03:08.750 align:start position:0% place to get it done<00:03:05.920> the<00:03:06.080> reason<00:03:06.519> is<00:03:07.200> ethereum<00:03:07.799> 2.0<00:03:08.319> AKA 00:03:08.750 --> 00:03:08.760 align:start position:0% done the reason is ethereum 2.0 AKA 00:03:08.760 --> 00:03:11.309 align:start position:0% done the reason is ethereum 2.0 AKA Serenity<00:03:09.319> was<00:03:09.480> announced<00:03:10.319> about<00:03:10.959> not<00:03:11.120> too 00:03:11.309 --> 00:03:11.319 align:start position:0% Serenity was announced about not too 00:03:11.319 --> 00:03:13.670 align:start position:0% Serenity was announced about not too long<00:03:11.560> after<00:03:11.799> this<00:03:12.080> this<00:03:12.200> EIP<00:03:12.640> was<00:03:12.760> announced 00:03:13.670 --> 00:03:13.680 align:start position:0% long after this this EIP was announced 00:03:13.680 --> 00:03:15.990 align:start position:0% long after this this EIP was announced and<00:03:13.920> it<00:03:14.480> it<00:03:14.720> pro<00:03:14.959> it<00:03:15.120> was<00:03:15.400> proposing<00:03:15.840> some 00:03:15.990 --> 00:03:16.000 align:start position:0% and it it pro it was proposing some 00:03:16.000 --> 00:03:17.990 align:start position:0% and it it pro it was proposing some major<00:03:16.200> changes<00:03:16.480> to<00:03:16.599> the<00:03:16.720> theorum<00:03:17.080> itself 00:03:17.990 --> 00:03:18.000 align:start position:0% major changes to the theorum itself 00:03:18.000 --> 00:03:19.550 align:start position:0% major changes to the theorum itself among<00:03:18.280> those<00:03:18.519> was<00:03:18.720> switching<00:03:19.040> to<00:03:19.200> proof<00:03:19.400> of 00:03:19.550 --> 00:03:19.560 align:start position:0% among those was switching to proof of 00:03:19.560 --> 00:03:22.149 align:start position:0% among those was switching to proof of stake<00:03:20.480> um<00:03:20.680> and<00:03:20.840> also<00:03:21.360> introducing<00:03:21.879> data 00:03:22.149 --> 00:03:22.159 align:start position:0% stake um and also introducing data 00:03:22.159 --> 00:03:24.789 align:start position:0% stake um and also introducing data sharding<00:03:23.040> and<00:03:23.280> as<00:03:23.440> part<00:03:23.599> of<00:03:23.799> step<00:03:24.040> two<00:03:24.680> uh 00:03:24.789 --> 00:03:24.799 align:start position:0% sharding and as part of step two uh 00:03:24.799 --> 00:03:27.390 align:start position:0% sharding and as part of step two uh introducing<00:03:25.480> ewm<00:03:26.480> as<00:03:26.640> as<00:03:26.760> an<00:03:26.879> alternate<00:03:27.239> form 00:03:27.390 --> 00:03:27.400 align:start position:0% introducing ewm as as an alternate form 00:03:27.400 --> 00:03:30.110 align:start position:0% introducing ewm as as an alternate form of<00:03:27.599> execution<00:03:28.519> and<00:03:28.640> then<00:03:28.840> finally<00:03:29.239> step<00:03:29.879> the 00:03:30.110 --> 00:03:30.120 align:start position:0% of execution and then finally step the 00:03:30.120 --> 00:03:32.149 align:start position:0% of execution and then finally step the phase<00:03:30.360> three<00:03:30.760> step<00:03:31.000> four<00:03:31.519> was<00:03:31.680> a<00:03:31.840> bunch<00:03:32.000> of 00:03:32.149 --> 00:03:32.159 align:start position:0% phase three step four was a bunch of 00:03:32.159 --> 00:03:33.949 align:start position:0% phase three step four was a bunch of other<00:03:32.360> improvements<00:03:33.200> and<00:03:33.360> you'll<00:03:33.519> notice<00:03:33.840> the 00:03:33.949 --> 00:03:33.959 align:start position:0% other improvements and you'll notice the 00:03:33.959 --> 00:03:35.429 align:start position:0% other improvements and you'll notice the further<00:03:34.319> down<00:03:34.480> we<00:03:34.640> go<00:03:34.799> down<00:03:34.959> the<00:03:35.080> list<00:03:35.360> the 00:03:35.429 --> 00:03:35.439 align:start position:0% further down we go down the list the 00:03:35.439 --> 00:03:36.470 align:start position:0% further down we go down the list the more<00:03:35.599> and<00:03:35.680> more<00:03:35.840> it<00:03:35.959> changed<00:03:36.239> from<00:03:36.360> the 00:03:36.470 --> 00:03:36.480 align:start position:0% more and more it changed from the 00:03:36.480 --> 00:03:39.070 align:start position:0% more and more it changed from the original<00:03:36.840> Vision<00:03:37.760> proof<00:03:37.920> of<00:03:38.080> stake<00:03:38.519> shipped 00:03:39.070 --> 00:03:39.080 align:start position:0% original Vision proof of stake shipped 00:03:39.080 --> 00:03:41.869 align:start position:0% original Vision proof of stake shipped pretty<00:03:39.319> much<00:03:39.720> as<00:03:39.920> envisioned<00:03:40.360> in<00:03:40.640> Serenity<00:03:41.640> um 00:03:41.869 --> 00:03:41.879 align:start position:0% pretty much as envisioned in Serenity um 00:03:41.879 --> 00:03:43.630 align:start position:0% pretty much as envisioned in Serenity um the<00:03:42.120> the<00:03:42.239> data<00:03:42.439> sharding<00:03:42.879> became<00:03:43.120> the<00:03:43.239> rollup 00:03:43.630 --> 00:03:43.640 align:start position:0% the the data sharding became the rollup 00:03:43.640 --> 00:03:47.229 align:start position:0% the the data sharding became the rollup Centric<00:03:43.959> road<00:03:44.239> map<00:03:45.159> and<00:03:45.640> the<00:03:45.799> ewm<00:03:46.640> was 00:03:47.229 --> 00:03:47.239 align:start position:0% Centric road map and the ewm was 00:03:47.239 --> 00:03:48.630 align:start position:0% Centric road map and the ewm was eventually<00:03:47.680> abandoned<00:03:48.120> for<00:03:48.239> reasons<00:03:48.519> I'll 00:03:48.630 --> 00:03:48.640 align:start position:0% eventually abandoned for reasons I'll 00:03:48.640 --> 00:03:50.509 align:start position:0% eventually abandoned for reasons I'll get<00:03:48.720> to<00:03:48.840> in<00:03:48.920> the<00:03:49.040> next<00:03:49.200> slide<00:03:49.799> but<00:03:50.000> that<00:03:50.239> last 00:03:50.509 --> 00:03:50.519 align:start position:0% get to in the next slide but that last 00:03:50.519 --> 00:03:52.390 align:start position:0% get to in the next slide but that last Point<00:03:51.239> um<00:03:51.360> they<00:03:51.519> didn't<00:03:51.799> have<00:03:51.959> the<00:03:52.079> idea<00:03:52.280> of 00:03:52.390 --> 00:03:52.400 align:start position:0% Point um they didn't have the idea of 00:03:52.400 --> 00:03:54.589 align:start position:0% Point um they didn't have the idea of oifc<00:03:53.079> built<00:03:53.360> in<00:03:53.560> yet<00:03:53.680> and<00:03:53.799> there's<00:03:53.920> a<00:03:54.200> big<00:03:54.400> push 00:03:54.589 --> 00:03:54.599 align:start position:0% oifc built in yet and there's a big push 00:03:54.599 --> 00:03:57.110 align:start position:0% oifc built in yet and there's a big push to<00:03:54.760> aify<00:03:55.159> the<00:03:55.280> protocol<00:03:55.680> at<00:03:55.840> this 00:03:57.110 --> 00:03:57.120 align:start position:0% to aify the protocol at this 00:03:57.120 --> 00:04:00.710 align:start position:0% to aify the protocol at this point<00:03:58.120> so<00:03:58.360> why<00:03:58.519> was<00:03:58.799> ewam<00:03:59.319> abandoned<00:04:00.079> why<00:04:00.560> they 00:04:00.710 --> 00:04:00.720 align:start position:0% point so why was ewam abandoned why they 00:04:00.720 --> 00:04:02.509 align:start position:0% point so why was ewam abandoned why they put<00:04:00.879> a<00:04:01.079> lot<00:04:01.200> of<00:04:01.319> effort<00:04:01.599> into<00:04:01.799> it<00:04:02.079> Why<00:04:02.239> didn't 00:04:02.509 --> 00:04:02.519 align:start position:0% put a lot of effort into it Why didn't 00:04:02.519 --> 00:04:04.589 align:start position:0% put a lot of effort into it Why didn't it<00:04:02.680> ship<00:04:03.680> um<00:04:04.000> there<00:04:04.079> were<00:04:04.239> a<00:04:04.280> number<00:04:04.480> of 00:04:04.589 --> 00:04:04.599 align:start position:0% it ship um there were a number of 00:04:04.599 --> 00:04:05.789 align:start position:0% it ship um there were a number of reasons<00:04:04.920> and<00:04:05.079> one<00:04:05.200> of<00:04:05.280> them<00:04:05.400> was<00:04:05.560> just<00:04:05.680> the 00:04:05.789 --> 00:04:05.799 align:start position:0% reasons and one of them was just the 00:04:05.799 --> 00:04:07.750 align:start position:0% reasons and one of them was just the complexity<00:04:06.319> around<00:04:06.560> it<00:04:07.200> um<00:04:07.319> we<00:04:07.400> were<00:04:07.519> going<00:04:07.599> to 00:04:07.750 --> 00:04:07.760 align:start position:0% complexity around it um we were going to 00:04:07.760 --> 00:04:10.270 align:start position:0% complexity around it um we were going to have<00:04:07.840> to<00:04:07.959> keep<00:04:08.120> the<00:04:08.200> evm<00:04:08.640> around<00:04:09.360> and<00:04:09.599> ewm 00:04:10.270 --> 00:04:10.280 align:start position:0% have to keep the evm around and ewm 00:04:10.280 --> 00:04:12.830 align:start position:0% have to keep the evm around and ewm around<00:04:11.000> and<00:04:11.439> there<00:04:11.560> was<00:04:11.879> there<00:04:11.959> was<00:04:12.200> proposals 00:04:12.830 --> 00:04:12.840 align:start position:0% around and there was there was proposals 00:04:12.840 --> 00:04:14.470 align:start position:0% around and there was there was proposals and<00:04:13.120> and<00:04:13.280> plans<00:04:13.599> to<00:04:13.760> try<00:04:13.920> and<00:04:14.079> get<00:04:14.280> the 00:04:14.470 --> 00:04:14.480 align:start position:0% and and plans to try and get the 00:04:14.480 --> 00:04:16.870 align:start position:0% and and plans to try and get the shifting<00:04:14.879> between<00:04:15.159> the<00:04:15.239> two<00:04:15.440> versions<00:04:16.440> um<00:04:16.560> to 00:04:16.870 --> 00:04:16.880 align:start position:0% shifting between the two versions um to 00:04:16.880 --> 00:04:20.069 align:start position:0% shifting between the two versions um to to<00:04:17.199> to<00:04:17.400> cross<00:04:17.759> compile<00:04:18.079> evm<00:04:18.440> and<00:04:18.759> ewom<00:04:19.759> um<00:04:19.880> but 00:04:20.069 --> 00:04:20.079 align:start position:0% to to cross compile evm and ewom um but 00:04:20.079 --> 00:04:21.909 align:start position:0% to to cross compile evm and ewom um but also<00:04:20.320> didn't<00:04:20.560> ewom<00:04:21.040> does<00:04:21.160> not<00:04:21.320> natively 00:04:21.909 --> 00:04:21.919 align:start position:0% also didn't ewom does not natively 00:04:21.919 --> 00:04:24.110 align:start position:0% also didn't ewom does not natively support<00:04:22.919> uh<00:04:23.120> the<00:04:23.280> gas<00:04:23.479> into<00:04:23.759> it<00:04:23.880> you<00:04:23.960> would 00:04:24.110 --> 00:04:24.120 align:start position:0% support uh the gas into it you would 00:04:24.120 --> 00:04:25.710 align:start position:0% support uh the gas into it you would have<00:04:24.199> to<00:04:24.320> weave<00:04:24.639> the<00:04:24.840> gas<00:04:25.040> into<00:04:25.280> it<00:04:25.400> and<00:04:25.560> have 00:04:25.710 --> 00:04:25.720 align:start position:0% have to weave the gas into it and have 00:04:25.720 --> 00:04:28.670 align:start position:0% have to weave the gas into it and have validation<00:04:26.240> rules<00:04:26.960> relating<00:04:27.320> to<00:04:27.479> the<00:04:27.680> gas<00:04:28.520> and 00:04:28.670 --> 00:04:28.680 align:start position:0% validation rules relating to the gas and 00:04:28.680 --> 00:04:30.189 align:start position:0% validation rules relating to the gas and there<00:04:28.759> are<00:04:28.960> also<00:04:29.160> issues<00:04:29.479> Rel<00:04:29.720> reled<00:04:29.919> to<00:04:30.000> the 00:04:30.189 --> 00:04:30.199 align:start position:0% there are also issues Rel reled to the 00:04:30.199 --> 00:04:32.909 align:start position:0% there are also issues Rel reled to the 256-bit<00:04:31.199> math<00:04:32.039> and<00:04:32.240> that<00:04:32.400> really<00:04:32.639> is<00:04:32.759> what 00:04:32.909 --> 00:04:32.919 align:start position:0% 256-bit math and that really is what 00:04:32.919 --> 00:04:34.710 align:start position:0% 256-bit math and that really is what caused<00:04:33.199> a<00:04:33.280> lot<00:04:33.360> of<00:04:33.560> performance<00:04:34.080> problems 00:04:34.710 --> 00:04:34.720 align:start position:0% caused a lot of performance problems 00:04:34.720 --> 00:04:36.870 align:start position:0% caused a lot of performance problems they<00:04:35.280> the<00:04:35.479> the<00:04:35.600> ipsilon<00:04:36.000> team<00:04:36.199> went<00:04:36.400> through<00:04:36.759> a 00:04:36.870 --> 00:04:36.880 align:start position:0% they the the ipsilon team went through a 00:04:36.880 --> 00:04:39.029 align:start position:0% they the the ipsilon team went through a summary<00:04:37.199> of<00:04:37.320> the<00:04:37.400> performance<00:04:38.199> of<00:04:38.360> their<00:04:38.479> ewm 00:04:39.029 --> 00:04:39.039 align:start position:0% summary of the performance of their ewm 00:04:39.039 --> 00:04:41.469 align:start position:0% summary of the performance of their ewm prototype<00:04:39.520> in<00:04:39.680> Osaka<00:04:40.639> and<00:04:40.800> you<00:04:40.919> know<00:04:41.120> they<00:04:41.360> had 00:04:41.469 --> 00:04:41.479 align:start position:0% prototype in Osaka and you know they had 00:04:41.479 --> 00:04:43.150 align:start position:0% prototype in Osaka and you know they had a<00:04:41.880> they<00:04:42.039> came<00:04:42.280> public<00:04:42.600> that<00:04:42.720> it<00:04:42.800> wasn't<00:04:43.039> as 00:04:43.150 --> 00:04:43.160 align:start position:0% a they came public that it wasn't as 00:04:43.160 --> 00:04:44.629 align:start position:0% a they came public that it wasn't as performant<00:04:43.560> as<00:04:43.639> they<00:04:43.840> was<00:04:44.080> hoping<00:04:44.360> it<00:04:44.479> was 00:04:44.629 --> 00:04:44.639 align:start position:0% performant as they was hoping it was 00:04:44.639 --> 00:04:46.189 align:start position:0% performant as they was hoping it was going<00:04:44.759> to<00:04:44.880> be<00:04:45.479> um<00:04:45.680> there<00:04:45.759> were<00:04:45.880> some<00:04:45.960> things 00:04:46.189 --> 00:04:46.199 align:start position:0% going to be um there were some things 00:04:46.199 --> 00:04:48.150 align:start position:0% going to be um there were some things can<00:04:46.320> be<00:04:46.400> done<00:04:46.560> to<00:04:46.680> fix<00:04:46.880> it<00:04:47.120> but<00:04:47.320> that<00:04:47.720> it<00:04:47.840> wasn't 00:04:48.150 --> 00:04:48.160 align:start position:0% can be done to fix it but that it wasn't 00:04:48.160 --> 00:04:49.790 align:start position:0% can be done to fix it but that it wasn't going<00:04:48.360> to<00:04:48.680> hit<00:04:48.840> its<00:04:49.000> main<00:04:49.199> goal<00:04:49.440> which<00:04:49.560> was<00:04:49.680> to 00:04:49.790 --> 00:04:49.800 align:start position:0% going to hit its main goal which was to 00:04:49.800 --> 00:04:51.990 align:start position:0% going to hit its main goal which was to be<00:04:49.960> faster<00:04:50.560> than<00:04:50.759> interpreted<00:04:51.280> evm<00:04:51.759> it<00:04:51.840> was 00:04:51.990 --> 00:04:52.000 align:start position:0% be faster than interpreted evm it was 00:04:52.000 --> 00:04:53.790 align:start position:0% be faster than interpreted evm it was kind<00:04:52.120> of<00:04:52.560> kind<00:04:52.680> of<00:04:52.800> a<00:04:52.919> gut<00:04:53.160> punch<00:04:53.400> to<00:04:53.600> to<00:04:53.720> the 00:04:53.790 --> 00:04:53.800 align:start position:0% kind of kind of a gut punch to to the 00:04:53.800 --> 00:04:55.670 align:start position:0% kind of kind of a gut punch to to the Epsilon<00:04:54.160> team<00:04:54.440> but<00:04:54.639> they<00:04:55.080> they<00:04:55.199> did<00:04:55.360> the<00:04:55.520> right 00:04:55.670 --> 00:04:55.680 align:start position:0% Epsilon team but they they did the right 00:04:55.680 --> 00:04:56.950 align:start position:0% Epsilon team but they they did the right thing<00:04:55.800> and<00:04:56.000> they<00:04:56.160> they<00:04:56.280> brought<00:04:56.479> the<00:04:56.600> data<00:04:56.840> out 00:04:56.950 --> 00:04:56.960 align:start position:0% thing and they they brought the data out 00:04:56.960 --> 00:05:01.430 align:start position:0% thing and they they brought the data out and<00:04:57.039> showed<00:04:57.320> what<00:04:57.440> was<00:04:57.560> going<00:04:57.759> on<00:04:57.960> with<00:04:58.080> it 00:05:01.430 --> 00:05:01.440 align:start position:0% 00:05:01.440 --> 00:05:03.150 align:start position:0% so<00:05:02.000> looking<00:05:02.240> at<00:05:02.360> all<00:05:02.520> these<00:05:02.680> things<00:05:02.919> with<00:05:03.039> the 00:05:03.150 --> 00:05:03.160 align:start position:0% so looking at all these things with the 00:05:03.160 --> 00:05:05.430 align:start position:0% so looking at all these things with the evm<00:05:04.160> is<00:05:04.360> probably<00:05:04.880> we<00:05:04.960> should<00:05:05.120> probably<00:05:05.320> look 00:05:05.430 --> 00:05:05.440 align:start position:0% evm is probably we should probably look 00:05:05.440 --> 00:05:08.070 align:start position:0% evm is probably we should probably look and<00:05:05.639> ask<00:05:06.000> before<00:05:06.199> we<00:05:06.320> ask<00:05:06.600> why<00:05:06.840> eof<00:05:07.840> we<00:05:07.919> should 00:05:08.070 --> 00:05:08.080 align:start position:0% and ask before we ask why eof we should 00:05:08.080 --> 00:05:10.070 align:start position:0% and ask before we ask why eof we should ask<00:05:08.360> why<00:05:08.479> not<00:05:08.720> eof<00:05:09.199> couldn't<00:05:09.400> we<00:05:09.560> just<00:05:09.720> do<00:05:09.919> all 00:05:10.070 --> 00:05:10.080 align:start position:0% ask why not eof couldn't we just do all 00:05:10.080 --> 00:05:12.390 align:start position:0% ask why not eof couldn't we just do all these<00:05:10.240> changes<00:05:10.639> without<00:05:10.919> doing<00:05:11.560> a<00:05:11.800> big<00:05:12.080> change 00:05:12.390 --> 00:05:12.400 align:start position:0% these changes without doing a big change 00:05:12.400 --> 00:05:14.710 align:start position:0% these changes without doing a big change to<00:05:12.520> the<00:05:12.639> evm<00:05:13.600> and<00:05:13.759> just<00:05:13.919> do<00:05:14.080> these<00:05:14.240> things<00:05:14.479> peac 00:05:14.710 --> 00:05:14.720 align:start position:0% to the evm and just do these things peac 00:05:14.720 --> 00:05:16.350 align:start position:0% to the evm and just do these things peac meal<00:05:15.320> so<00:05:15.520> this<00:05:15.680> next<00:05:15.840> section<00:05:16.080> we'll<00:05:16.240> talk 00:05:16.350 --> 00:05:16.360 align:start position:0% meal so this next section we'll talk 00:05:16.360 --> 00:05:18.350 align:start position:0% meal so this next section we'll talk about<00:05:16.600> answer<00:05:16.880> that<00:05:17.080> question<00:05:17.280> of<00:05:17.479> why<00:05:17.680> not 00:05:18.350 --> 00:05:18.360 align:start position:0% about answer that question of why not 00:05:18.360 --> 00:05:19.430 align:start position:0% about answer that question of why not why<00:05:18.479> couldn't<00:05:18.680> we<00:05:18.840> just<00:05:19.000> you<00:05:19.080> know<00:05:19.280> just 00:05:19.430 --> 00:05:19.440 align:start position:0% why couldn't we just you know just 00:05:19.440 --> 00:05:21.270 align:start position:0% why couldn't we just you know just introduce<00:05:20.280> uh<00:05:20.400> immediate<00:05:20.800> jumps<00:05:21.120> with 00:05:21.270 --> 00:05:21.280 align:start position:0% introduce uh immediate jumps with 00:05:21.280 --> 00:05:23.150 align:start position:0% introduce uh immediate jumps with immediate<00:05:21.639> codes<00:05:22.440> why<00:05:22.560> couldn't<00:05:22.800> we<00:05:22.919> just<00:05:23.039> do 00:05:23.150 --> 00:05:23.160 align:start position:0% immediate codes why couldn't we just do 00:05:23.160 --> 00:05:25.469 align:start position:0% immediate codes why couldn't we just do SUB<00:05:23.440> routines<00:05:24.360> why<00:05:24.520> couldn't<00:05:24.759> we<00:05:25.039> just 00:05:25.469 --> 00:05:25.479 align:start position:0% SUB routines why couldn't we just 00:05:25.479 --> 00:05:26.909 align:start position:0% SUB routines why couldn't we just enforce<00:05:25.880> code<00:05:26.120> data<00:05:26.360> separation<00:05:26.759> and 00:05:26.909 --> 00:05:26.919 align:start position:0% enforce code data separation and 00:05:26.919 --> 00:05:28.629 align:start position:0% enforce code data separation and validate<00:05:27.280> the<00:05:27.400> code<00:05:27.960> why<00:05:28.080> do<00:05:28.199> we<00:05:28.319> have<00:05:28.400> to<00:05:28.479> do 00:05:28.629 --> 00:05:28.639 align:start position:0% validate the code why do we have to do 00:05:28.639 --> 00:05:30.150 align:start position:0% validate the code why do we have to do this<00:05:28.759> all<00:05:28.919> at<00:05:29.039> once<00:05:29.199> in<00:05:29.319> this<00:05:29.440> big<00:05:29.840> giant 00:05:30.150 --> 00:05:30.160 align:start position:0% this all at once in this big giant 00:05:30.160 --> 00:05:32.189 align:start position:0% this all at once in this big giant change<00:05:30.960> and<00:05:31.120> the<00:05:31.280> problem<00:05:31.600> is<00:05:31.840> all<00:05:32.080> these 00:05:32.189 --> 00:05:32.199 align:start position:0% change and the problem is all these 00:05:32.199 --> 00:05:34.110 align:start position:0% change and the problem is all these features<00:05:32.520> are<00:05:32.720> deeply<00:05:33.000> intertwined<00:05:34.000> you 00:05:34.110 --> 00:05:34.120 align:start position:0% features are deeply intertwined you 00:05:34.120 --> 00:05:35.430 align:start position:0% features are deeply intertwined you really<00:05:34.280> need<00:05:34.400> to<00:05:34.520> do<00:05:34.680> them<00:05:34.840> all<00:05:34.960> at<00:05:35.080> once 00:05:35.430 --> 00:05:35.440 align:start position:0% really need to do them all at once 00:05:35.440 --> 00:05:38.029 align:start position:0% really need to do them all at once because<00:05:36.039> the<00:05:36.199> value<00:05:36.560> comes<00:05:37.080> in<00:05:37.440> all<00:05:37.600> of<00:05:37.759> them 00:05:38.029 --> 00:05:38.039 align:start position:0% because the value comes in all of them 00:05:38.039 --> 00:05:39.510 align:start position:0% because the value comes in all of them together<00:05:38.280> at<00:05:38.400> the<00:05:38.520> same<00:05:38.759> time<00:05:39.000> not<00:05:39.160> on<00:05:39.360> them 00:05:39.510 --> 00:05:39.520 align:start position:0% together at the same time not on them 00:05:39.520 --> 00:05:41.629 align:start position:0% together at the same time not on them individually<00:05:40.160> and<00:05:40.319> doing<00:05:40.520> them<00:05:40.720> individually 00:05:41.629 --> 00:05:41.639 align:start position:0% individually and doing them individually 00:05:41.639 --> 00:05:44.230 align:start position:0% individually and doing them individually actually<00:05:41.919> creates<00:05:42.440> new<00:05:42.960> problems<00:05:43.960> so<00:05:44.120> the 00:05:44.230 --> 00:05:44.240 align:start position:0% actually creates new problems so the 00:05:44.240 --> 00:05:45.670 align:start position:0% actually creates new problems so the first<00:05:44.400> thing<00:05:44.520> we'll<00:05:44.680> talk<00:05:44.840> about<00:05:45.039> is<00:05:45.199> relative 00:05:45.670 --> 00:05:45.680 align:start position:0% first thing we'll talk about is relative 00:05:45.680 --> 00:05:48.230 align:start position:0% first thing we'll talk about is relative jumps<00:05:46.560> and<00:05:46.720> relative<00:05:47.120> jumps<00:05:47.600> um<00:05:47.840> as<00:05:48.080> as<00:05:48.160> I 00:05:48.230 --> 00:05:48.240 align:start position:0% jumps and relative jumps um as as I 00:05:48.240 --> 00:05:50.790 align:start position:0% jumps and relative jumps um as as I mentioned<00:05:48.600> before<00:05:49.560> uh<00:05:49.960> you<00:05:50.080> needed<00:05:50.360> to<00:05:50.520> put 00:05:50.790 --> 00:05:50.800 align:start position:0% mentioned before uh you needed to put 00:05:50.800 --> 00:05:52.950 align:start position:0% mentioned before uh you needed to put the<00:05:50.919> jump<00:05:51.199> Target<00:05:51.600> into<00:05:51.880> the<00:05:52.039> code<00:05:52.639> using 00:05:52.950 --> 00:05:52.960 align:start position:0% the jump Target into the code using 00:05:52.960 --> 00:05:55.189 align:start position:0% the jump Target into the code using something<00:05:53.199> called<00:05:53.360> an<00:05:53.520> immediate<00:05:54.199> argument 00:05:55.189 --> 00:05:55.199 align:start position:0% something called an immediate argument 00:05:55.199 --> 00:05:57.230 align:start position:0% something called an immediate argument um<00:05:55.440> and<00:05:55.639> the<00:05:55.800> push<00:05:56.039> data<00:05:56.479> the<00:05:56.600> push<00:05:56.800> op<00:05:56.960> code<00:05:57.160> is 00:05:57.230 --> 00:05:57.240 align:start position:0% um and the push data the push op code is 00:05:57.240 --> 00:05:58.909 align:start position:0% um and the push data the push op code is an<00:05:57.400> example<00:05:57.840> of<00:05:57.960> things<00:05:58.160> that<00:05:58.319> have<00:05:58.560> the<00:05:58.800> the 00:05:58.909 --> 00:05:58.919 align:start position:0% an example of things that have the the 00:05:58.919 --> 00:06:01.110 align:start position:0% an example of things that have the the immediate<00:05:59.280> argument<00:06:00.120> so<00:06:00.240> if<00:06:00.360> we<00:06:00.479> added<00:06:00.680> a<00:06:00.840> new 00:06:01.110 --> 00:06:01.120 align:start position:0% immediate argument so if we added a new 00:06:01.120 --> 00:06:02.270 align:start position:0% immediate argument so if we added a new one<00:06:01.319> let's<00:06:01.440> say<00:06:01.600> we're<00:06:01.720> going<00:06:01.800> to<00:06:02.039> pretend 00:06:02.270 --> 00:06:02.280 align:start position:0% one let's say we're going to pretend 00:06:02.280 --> 00:06:03.550 align:start position:0% one let's say we're going to pretend we're<00:06:02.400> going<00:06:02.479> to<00:06:02.600> do<00:06:02.720> this<00:06:02.880> e<00:06:03.080> z<00:06:03.319> is<00:06:03.400> going<00:06:03.479> to 00:06:03.550 --> 00:06:03.560 align:start position:0% we're going to do this e z is going to 00:06:03.560 --> 00:06:04.909 align:start position:0% we're going to do this e z is going to be<00:06:03.639> the<00:06:03.720> new<00:06:03.840> R<00:06:04.039> jump<00:06:04.280> instruction<00:06:04.680> and<00:06:04.800> we 00:06:04.909 --> 00:06:04.919 align:start position:0% be the new R jump instruction and we 00:06:04.919 --> 00:06:07.870 align:start position:0% be the new R jump instruction and we have<00:06:05.039> a<00:06:05.479> two<00:06:05.720> bit<00:06:06.360> two<00:06:06.560> byte<00:06:06.840> signed<00:06:07.599> field 00:06:07.870 --> 00:06:07.880 align:start position:0% have a two bit two byte signed field 00:06:07.880 --> 00:06:09.189 align:start position:0% have a two bit two byte signed field that's<00:06:08.000> going<00:06:08.199> tell<00:06:08.440> relative<00:06:08.800> jumps<00:06:09.080> and 00:06:09.189 --> 00:06:09.199 align:start position:0% that's going tell relative jumps and 00:06:09.199 --> 00:06:10.469 align:start position:0% that's going tell relative jumps and you'll<00:06:09.360> see<00:06:09.520> from<00:06:09.680> this<00:06:10.000> that<00:06:10.120> we<00:06:10.280> actually 00:06:10.469 --> 00:06:10.479 align:start position:0% you'll see from this that we actually 00:06:10.479 --> 00:06:13.070 align:start position:0% you'll see from this that we actually you<00:06:10.599> know<00:06:10.800> on<00:06:11.000> average<00:06:11.360> save<00:06:11.639> a<00:06:11.800> bite<00:06:12.560> if<00:06:12.880> if 00:06:13.070 --> 00:06:13.080 align:start position:0% you know on average save a bite if if 00:06:13.080 --> 00:06:15.790 align:start position:0% you know on average save a bite if if the<00:06:13.400> uh<00:06:13.560> if<00:06:13.680> the<00:06:13.800> contract<00:06:14.160> is<00:06:14.280> over<00:06:14.520> 256<00:06:15.360> bit 00:06:15.790 --> 00:06:15.800 align:start position:0% the uh if the contract is over 256 bit 00:06:15.800 --> 00:06:18.790 align:start position:0% the uh if the contract is over 256 bit bytes<00:06:16.280> long<00:06:17.280> the<00:06:17.440> problem<00:06:17.759> comes<00:06:18.520> with 00:06:18.790 --> 00:06:18.800 align:start position:0% bytes long the problem comes with 00:06:18.800 --> 00:06:20.990 align:start position:0% bytes long the problem comes with existing<00:06:19.199> code<00:06:19.520> that<00:06:19.720> may<00:06:20.160> have<00:06:20.360> this<00:06:20.520> op<00:06:20.800> code 00:06:20.990 --> 00:06:21.000 align:start position:0% existing code that may have this op code 00:06:21.000 --> 00:06:22.990 align:start position:0% existing code that may have this op code in<00:06:21.199> place<00:06:21.479> for<00:06:21.599> a<00:06:21.680> number<00:06:21.880> of<00:06:22.039> reasons<00:06:22.840> so 00:06:22.990 --> 00:06:23.000 align:start position:0% in place for a number of reasons so 00:06:23.000 --> 00:06:25.270 align:start position:0% in place for a number of reasons so here's<00:06:23.199> an<00:06:23.360> example<00:06:23.919> up<00:06:24.240> here<00:06:24.440> I<00:06:24.599> have<00:06:24.840> of<00:06:25.039> of<00:06:25.120> a 00:06:25.270 --> 00:06:25.280 align:start position:0% here's an example up here I have of of a 00:06:25.280 --> 00:06:27.430 align:start position:0% here's an example up here I have of of a code<00:06:25.520> that<00:06:25.639> may<00:06:25.880> exist<00:06:26.759> um<00:06:26.880> that<00:06:27.000> has<00:06:27.120> a<00:06:27.240> couple 00:06:27.430 --> 00:06:27.440 align:start position:0% code that may exist um that has a couple 00:06:27.440 --> 00:06:29.230 align:start position:0% code that may exist um that has a couple of<00:06:27.560> push<00:06:27.800> instructions<00:06:28.680> one<00:06:28.800> of<00:06:28.919> those<00:06:29.039> push 00:06:29.230 --> 00:06:29.240 align:start position:0% of push instructions one of those push 00:06:29.240 --> 00:06:30.189 align:start position:0% of push instructions one of those push instruction 00:06:30.189 --> 00:06:30.199 align:start position:0% instruction 00:06:30.199 --> 00:06:32.950 align:start position:0% instruction has<00:06:30.360> the<00:06:30.560> 5B<00:06:31.000> instruction<00:06:31.560> that<00:06:31.680> is<00:06:32.000> the<00:06:32.560> the 00:06:32.950 --> 00:06:32.960 align:start position:0% has the 5B instruction that is the the 00:06:32.960 --> 00:06:35.309 align:start position:0% has the 5B instruction that is the the uh<00:06:33.240> the<00:06:33.360> jump<00:06:33.639> dust<00:06:34.080> Target<00:06:34.800> and<00:06:34.919> then<00:06:35.039> we<00:06:35.160> go 00:06:35.309 --> 00:06:35.319 align:start position:0% uh the jump dust Target and then we go 00:06:35.319 --> 00:06:37.150 align:start position:0% uh the jump dust Target and then we go into<00:06:35.560> some<00:06:35.800> extra<00:06:36.120> data<00:06:36.520> that<00:06:36.639> has<00:06:36.759> a<00:06:36.880> bunch<00:06:37.039> of 00:06:37.150 --> 00:06:37.160 align:start position:0% into some extra data that has a bunch of 00:06:37.160 --> 00:06:39.589 align:start position:0% into some extra data that has a bunch of invalid<00:06:37.560> op<00:06:37.759> codes<00:06:38.240> the<00:06:38.360> ezo<00:06:38.840> op<00:06:39.080> code<00:06:39.280> is<00:06:39.400> not 00:06:39.589 --> 00:06:39.599 align:start position:0% invalid op codes the ezo op code is not 00:06:39.599 --> 00:06:42.350 align:start position:0% invalid op codes the ezo op code is not allocated<00:06:40.440> so<00:06:40.759> the<00:06:40.840> evm<00:06:41.280> doesn't<00:06:41.560> care<00:06:41.800> the<00:06:41.919> 5B 00:06:42.350 --> 00:06:42.360 align:start position:0% allocated so the evm doesn't care the 5B 00:06:42.360 --> 00:06:46.550 align:start position:0% allocated so the evm doesn't care the 5B exists<00:06:42.800> after<00:06:43.000> the<00:06:43.120> EZ<00:06:44.000> FF<00:06:44.479> C9<00:06:45.120> 2A<00:06:46.120> so<00:06:46.280> if<00:06:46.400> we 00:06:46.550 --> 00:06:46.560 align:start position:0% exists after the EZ FF C9 2A so if we 00:06:46.560 --> 00:06:48.790 align:start position:0% exists after the EZ FF C9 2A so if we introduce<00:06:47.000> a<00:06:47.199> new<00:06:47.440> ezero<00:06:48.000> OP<00:06:48.240> code<00:06:48.440> that<00:06:48.560> takes 00:06:48.790 --> 00:06:48.800 align:start position:0% introduce a new ezero OP code that takes 00:06:48.800 --> 00:06:51.110 align:start position:0% introduce a new ezero OP code that takes two<00:06:49.039> immediate<00:06:49.560> bytes<00:06:50.560> without<00:06:50.840> doing 00:06:51.110 --> 00:06:51.120 align:start position:0% two immediate bytes without doing 00:06:51.120 --> 00:06:59.790 align:start position:0% two immediate bytes without doing anything<00:06:51.440> to<00:06:51.680> this<00:06:51.800> other<00:06:52.039> predeployment 00:06:59.790 --> 00:06:59.800 align:start position:0% 00:06:59.800 --> 00:07:02.029 align:start position:0% and<00:06:59.919> hit<00:07:00.039> that<00:07:00.160> jump<00:07:00.400> D<00:07:00.759> is<00:07:00.919> now<00:07:01.080> going<00:07:01.240> to<00:07:01.479> fail 00:07:02.029 --> 00:07:02.039 align:start position:0% and hit that jump D is now going to fail 00:07:02.039 --> 00:07:03.390 align:start position:0% and hit that jump D is now going to fail and<00:07:02.160> you've<00:07:02.360> done<00:07:02.560> nothing<00:07:02.759> to<00:07:02.919> change<00:07:03.160> that 00:07:03.390 --> 00:07:03.400 align:start position:0% and you've done nothing to change that 00:07:03.400 --> 00:07:04.869 align:start position:0% and you've done nothing to change that contract<00:07:03.840> except<00:07:04.080> change<00:07:04.319> the<00:07:04.440> rules<00:07:04.639> of<00:07:04.759> the 00:07:04.869 --> 00:07:04.879 align:start position:0% contract except change the rules of the 00:07:04.879 --> 00:07:07.350 align:start position:0% contract except change the rules of the VM<00:07:05.759> and<00:07:05.879> this<00:07:06.000> is<00:07:06.120> the<00:07:06.240> sort<00:07:06.400> of<00:07:06.599> change<00:07:07.240> in 00:07:07.350 --> 00:07:07.360 align:start position:0% VM and this is the sort of change in 00:07:07.360 --> 00:07:08.869 align:start position:0% VM and this is the sort of change in ethereum<00:07:07.840> that<00:07:07.919> we<00:07:08.039> frown<00:07:08.360> upon<00:07:08.560> and<00:07:08.639> we<00:07:08.720> try 00:07:08.869 --> 00:07:08.879 align:start position:0% ethereum that we frown upon and we try 00:07:08.879 --> 00:07:10.710 align:start position:0% ethereum that we frown upon and we try our<00:07:09.039> best<00:07:09.199> not<00:07:09.319> to<00:07:09.440> do<00:07:09.680> we<00:07:09.800> try<00:07:09.960> not<00:07:10.080> to<00:07:10.199> break 00:07:10.710 --> 00:07:10.720 align:start position:0% our best not to do we try not to break 00:07:10.720 --> 00:07:12.629 align:start position:0% our best not to do we try not to break what<00:07:10.879> has<00:07:11.039> already<00:07:11.240> been<00:07:11.400> out<00:07:11.680> there<00:07:12.199> so<00:07:12.400> to 00:07:12.629 --> 00:07:12.639 align:start position:0% what has already been out there so to 00:07:12.639 --> 00:07:14.670 align:start position:0% what has already been out there so to add<00:07:13.120> immediate<00:07:13.520> op<00:07:13.759> codes<00:07:14.199> would<00:07:14.400> break 00:07:14.670 --> 00:07:14.680 align:start position:0% add immediate op codes would break 00:07:14.680 --> 00:07:17.110 align:start position:0% add immediate op codes would break things<00:07:14.879> that<00:07:15.080> exist 00:07:17.110 --> 00:07:17.120 align:start position:0% things that exist 00:07:17.120 --> 00:07:19.309 align:start position:0% things that exist already<00:07:18.120> and<00:07:18.240> here's<00:07:18.479> another<00:07:18.759> piece<00:07:18.919> of<00:07:19.080> op 00:07:19.309 --> 00:07:19.319 align:start position:0% already and here's another piece of op 00:07:19.319 --> 00:07:21.830 align:start position:0% already and here's another piece of op code<00:07:19.560> that<00:07:19.639> shows<00:07:20.639> um<00:07:21.120> why<00:07:21.280> we<00:07:21.400> really<00:07:21.560> need<00:07:21.720> to 00:07:21.830 --> 00:07:21.840 align:start position:0% code that shows um why we really need to 00:07:21.840 --> 00:07:23.110 align:start position:0% code that shows um why we really need to get<00:07:21.960> rid<00:07:22.080> of<00:07:22.199> relative<00:07:22.479> jumps<00:07:22.800> this<00:07:22.919> is<00:07:23.000> a 00:07:23.110 --> 00:07:23.120 align:start position:0% get rid of relative jumps this is a 00:07:23.120 --> 00:07:24.309 align:start position:0% get rid of relative jumps this is a nightmare<00:07:23.560> code<00:07:23.720> that<00:07:23.800> I<00:07:23.840> learned<00:07:24.080> about<00:07:24.240> a 00:07:24.309 --> 00:07:24.319 align:start position:0% nightmare code that I learned about a 00:07:24.319 --> 00:07:26.270 align:start position:0% nightmare code that I learned about a few<00:07:24.440> weeks<00:07:24.680> ago<00:07:25.479> um<00:07:25.599> you<00:07:25.680> could<00:07:25.840> literally 00:07:26.270 --> 00:07:26.280 align:start position:0% few weeks ago um you could literally 00:07:26.280 --> 00:07:27.869 align:start position:0% few weeks ago um you could literally take<00:07:26.919> that<00:07:27.039> someone<00:07:27.280> actually<00:07:27.440> wanted<00:07:27.680> to 00:07:27.869 --> 00:07:27.879 align:start position:0% take that someone actually wanted to 00:07:27.879 --> 00:07:29.029 align:start position:0% take that someone actually wanted to make<00:07:28.000> sure<00:07:28.120> that<00:07:28.280> they<00:07:28.360> could<00:07:28.520> still<00:07:28.800> kind<00:07:28.919> of 00:07:29.029 --> 00:07:29.039 align:start position:0% make sure that they could still kind of 00:07:29.039 --> 00:07:31.350 align:start position:0% make sure that they could still kind of do<00:07:29.199> any<00:07:29.680> f<00:07:30.160> is<00:07:30.360> you<00:07:30.479> can<00:07:30.720> you<00:07:30.879> can<00:07:31.039> take<00:07:31.199> some 00:07:31.350 --> 00:07:31.360 align:start position:0% do any f is you can you can take some 00:07:31.360 --> 00:07:33.629 align:start position:0% do any f is you can you can take some info<00:07:31.599> from<00:07:31.720> the<00:07:31.840> call<00:07:32.120> data<00:07:32.720> trim<00:07:33.039> it<00:07:33.199> off<00:07:33.479> and 00:07:33.629 --> 00:07:33.639 align:start position:0% info from the call data trim it off and 00:07:33.639 --> 00:07:35.869 align:start position:0% info from the call data trim it off and jump<00:07:33.840> to<00:07:33.960> a<00:07:34.120> specific<00:07:34.520> spot<00:07:34.759> in<00:07:34.919> your<00:07:35.080> code 00:07:35.869 --> 00:07:35.879 align:start position:0% jump to a specific spot in your code 00:07:35.879 --> 00:07:37.270 align:start position:0% jump to a specific spot in your code based<00:07:36.120> on<00:07:36.280> that<00:07:36.400> call<00:07:36.639> data<00:07:36.840> they<00:07:36.919> were<00:07:37.039> using 00:07:37.270 --> 00:07:37.280 align:start position:0% based on that call data they were using 00:07:37.280 --> 00:07:39.869 align:start position:0% based on that call data they were using it<00:07:37.479> as<00:07:37.560> a<00:07:37.680> vector<00:07:38.000> jump<00:07:38.560> instruction<00:07:39.560> but<00:07:39.800> it 00:07:39.869 --> 00:07:39.879 align:start position:0% it as a vector jump instruction but it 00:07:39.879 --> 00:07:41.430 align:start position:0% it as a vector jump instruction but it was<00:07:40.120> just<00:07:40.440> this<00:07:40.560> was<00:07:40.720> just<00:07:40.840> mind-blowing<00:07:41.319> that 00:07:41.430 --> 00:07:41.440 align:start position:0% was just this was just mind-blowing that 00:07:41.440 --> 00:07:42.589 align:start position:0% was just this was just mind-blowing that people<00:07:41.599> were<00:07:41.759> actually<00:07:42.039> I<00:07:42.120> thought<00:07:42.319> this<00:07:42.440> was 00:07:42.589 --> 00:07:42.599 align:start position:0% people were actually I thought this was 00:07:42.599 --> 00:07:43.350 align:start position:0% people were actually I thought this was something<00:07:42.800> that<00:07:42.879> you<00:07:42.960> would<00:07:43.080> do<00:07:43.199> as<00:07:43.280> a 00:07:43.350 --> 00:07:43.360 align:start position:0% something that you would do as a 00:07:43.360 --> 00:07:44.670 align:start position:0% something that you would do as a malicious<00:07:43.800> attack<00:07:44.039> not<00:07:44.199> that<00:07:44.319> something<00:07:44.520> you 00:07:44.670 --> 00:07:44.680 align:start position:0% malicious attack not that something you 00:07:44.680 --> 00:07:46.469 align:start position:0% malicious attack not that something you to<00:07:44.759> find<00:07:44.960> utility<00:07:45.360> in<00:07:45.919> and<00:07:46.039> there<00:07:46.120> are<00:07:46.280> people 00:07:46.469 --> 00:07:46.479 align:start position:0% to find utility in and there are people 00:07:46.479 --> 00:07:47.710 align:start position:0% to find utility in and there are people that<00:07:46.599> like<00:07:46.800> to<00:07:46.919> do<00:07:47.120> things<00:07:47.319> like<00:07:47.479> this<00:07:47.599> in 00:07:47.710 --> 00:07:47.720 align:start position:0% that like to do things like this in 00:07:47.720 --> 00:07:50.110 align:start position:0% that like to do things like this in their<00:07:47.879> code<00:07:48.520> so<00:07:48.720> it's<00:07:49.360> this<00:07:49.479> is<00:07:49.680> why<00:07:49.840> we<00:07:49.960> need 00:07:50.110 --> 00:07:50.120 align:start position:0% their code so it's this is why we need 00:07:50.120 --> 00:07:52.070 align:start position:0% their code so it's this is why we need to<00:07:50.400> provide<00:07:50.680> you<00:07:50.759> know<00:07:51.080> stronger<00:07:51.520> guardrails 00:07:52.070 --> 00:07:52.080 align:start position:0% to provide you know stronger guardrails 00:07:52.080 --> 00:07:54.510 align:start position:0% to provide you know stronger guardrails around<00:07:52.319> some<00:07:52.479> of 00:07:54.510 --> 00:07:54.520 align:start position:0% around some of 00:07:54.520 --> 00:07:56.950 align:start position:0% around some of this<00:07:55.520> um<00:07:55.680> so<00:07:55.879> one<00:07:56.159> thing<00:07:56.360> one<00:07:56.520> approach<00:07:56.840> that 00:07:56.950 --> 00:07:56.960 align:start position:0% this um so one thing one approach that 00:07:56.960 --> 00:07:58.469 align:start position:0% this um so one thing one approach that was<00:07:57.159> tried<00:07:57.479> was<00:07:57.599> to<00:07:57.759> just<00:07:57.919> version<00:07:58.319> the 00:07:58.469 --> 00:07:58.479 align:start position:0% was tried was to just version the 00:07:58.479 --> 00:08:01.869 align:start position:0% was tried was to just version the contracts<00:07:59.560> IP<00:07:59.800> 1702<00:08:00.639> was<00:08:00.879> briefly<00:08:01.280> in<00:08:01.400> Berlin 00:08:01.869 --> 00:08:01.879 align:start position:0% contracts IP 1702 was briefly in Berlin 00:08:01.879 --> 00:08:03.670 align:start position:0% contracts IP 1702 was briefly in Berlin before<00:08:02.080> it<00:08:02.159> was<00:08:02.360> taken<00:08:02.639> out<00:08:03.199> and<00:08:03.280> so<00:08:03.440> we<00:08:03.560> would 00:08:03.670 --> 00:08:03.680 align:start position:0% before it was taken out and so we would 00:08:03.680 --> 00:08:06.550 align:start position:0% before it was taken out and so we would say<00:08:03.919> great<00:08:04.280> you<00:08:04.400> were<00:08:04.520> going<00:08:04.639> to<00:08:04.960> introduce<00:08:05.960> um 00:08:06.550 --> 00:08:06.560 align:start position:0% say great you were going to introduce um 00:08:06.560 --> 00:08:08.749 align:start position:0% say great you were going to introduce um e<00:08:06.840> e0<00:08:07.479> with<00:08:07.599> an<00:08:07.720> immediate<00:08:08.039> data<00:08:08.360> great<00:08:08.639> all 00:08:08.749 --> 00:08:08.759 align:start position:0% e e0 with an immediate data great all 00:08:08.759 --> 00:08:11.469 align:start position:0% e e0 with an immediate data great all new<00:08:09.240> contracts<00:08:10.240> um<00:08:10.440> deployed<00:08:10.919> after<00:08:11.120> Berlin 00:08:11.469 --> 00:08:11.479 align:start position:0% new contracts um deployed after Berlin 00:08:11.479 --> 00:08:13.230 align:start position:0% new contracts um deployed after Berlin and<00:08:11.599> later<00:08:12.199> will<00:08:12.400> have<00:08:12.560> this<00:08:12.680> Rule<00:08:12.919> and<00:08:13.080> all 00:08:13.230 --> 00:08:13.240 align:start position:0% and later will have this Rule and all 00:08:13.240 --> 00:08:14.909 align:start position:0% and later will have this Rule and all contracts<00:08:13.639> defined<00:08:14.039> below<00:08:14.440> won't<00:08:14.680> have<00:08:14.800> the 00:08:14.909 --> 00:08:14.919 align:start position:0% contracts defined below won't have the 00:08:14.919 --> 00:08:16.710 align:start position:0% contracts defined below won't have the ezero<00:08:15.360> op<00:08:15.599> code<00:08:16.000> and<00:08:16.080> we'll<00:08:16.240> just<00:08:16.400> have<00:08:16.520> these 00:08:16.710 --> 00:08:16.720 align:start position:0% ezero op code and we'll just have these 00:08:16.720 --> 00:08:18.189 align:start position:0% ezero op code and we'll just have these versions<00:08:17.080> and<00:08:17.240> every<00:08:17.400> Fork<00:08:17.680> will<00:08:17.800> add<00:08:17.960> a<00:08:18.039> new 00:08:18.189 --> 00:08:18.199 align:start position:0% versions and every Fork will add a new 00:08:18.199 --> 00:08:20.189 align:start position:0% versions and every Fork will add a new version<00:08:19.000> this<00:08:19.120> was<00:08:19.280> ultimately<00:08:19.720> rejected 00:08:20.189 --> 00:08:20.199 align:start position:0% version this was ultimately rejected 00:08:20.199 --> 00:08:21.510 align:start position:0% version this was ultimately rejected because<00:08:20.400> every<00:08:20.560> Fork<00:08:20.879> was<00:08:21.000> going<00:08:21.080> to<00:08:21.199> create<00:08:21.400> a 00:08:21.510 --> 00:08:21.520 align:start position:0% because every Fork was going to create a 00:08:21.520 --> 00:08:23.790 align:start position:0% because every Fork was going to create a new<00:08:21.720> version<00:08:22.440> of<00:08:22.599> evm<00:08:23.039> rules<00:08:23.319> that<00:08:23.440> would<00:08:23.599> grow 00:08:23.790 --> 00:08:23.800 align:start position:0% new version of evm rules that would grow 00:08:23.800 --> 00:08:25.350 align:start position:0% new version of evm rules that would grow and<00:08:23.919> grow<00:08:24.120> and<00:08:24.280> grow<00:08:24.680> sometimes<00:08:24.879> they<00:08:25.039> apply 00:08:25.350 --> 00:08:25.360 align:start position:0% and grow and grow sometimes they apply 00:08:25.360 --> 00:08:26.950 align:start position:0% and grow and grow sometimes they apply and<00:08:25.680> sometimes<00:08:25.879> they<00:08:26.039> don't<00:08:26.639> rather<00:08:26.840> than 00:08:26.950 --> 00:08:26.960 align:start position:0% and sometimes they don't rather than 00:08:26.960 --> 00:08:28.589 align:start position:0% and sometimes they don't rather than having<00:08:27.159> just<00:08:27.319> two<00:08:27.520> sets<00:08:27.720> of<00:08:27.840> rules<00:08:28.360> you<00:08:28.479> would 00:08:28.589 --> 00:08:28.599 align:start position:0% having just two sets of rules you would 00:08:28.599 --> 00:08:30.550 align:start position:0% having just two sets of rules you would have<00:08:28.720> an<00:08:28.879> infinitely<00:08:29.479> growing<00:08:29.720> set<00:08:29.879> of<00:08:30.000> rules 00:08:30.550 --> 00:08:30.560 align:start position:0% have an infinitely growing set of rules 00:08:30.560 --> 00:08:31.710 align:start position:0% have an infinitely growing set of rules which<00:08:30.680> was<00:08:30.840> going<00:08:30.919> to<00:08:31.000> be<00:08:31.199> problematic 00:08:31.710 --> 00:08:31.720 align:start position:0% which was going to be problematic 00:08:31.720 --> 00:08:33.670 align:start position:0% which was going to be problematic complexity<00:08:32.279> wise<00:08:32.800> so<00:08:33.000> that<00:08:33.120> was<00:08:33.240> ultimately 00:08:33.670 --> 00:08:33.680 align:start position:0% complexity wise so that was ultimately 00:08:33.680 --> 00:08:36.350 align:start position:0% complexity wise so that was ultimately taken<00:08:34.000> back<00:08:34.159> out<00:08:34.320> of<00:08:34.479> Berlin<00:08:35.440> um<00:08:35.919> after<00:08:36.080> it<00:08:36.200> was 00:08:36.350 --> 00:08:36.360 align:start position:0% taken back out of Berlin um after it was 00:08:36.360 --> 00:08:39.269 align:start position:0% taken back out of Berlin um after it was initially<00:08:36.680> brought<00:08:36.919> into<00:08:37.680> it<00:08:38.680> um<00:08:39.000> another 00:08:39.269 --> 00:08:39.279 align:start position:0% initially brought into it um another 00:08:39.279 --> 00:08:40.550 align:start position:0% initially brought into it um another thing<00:08:39.440> that<00:08:39.560> was<00:08:39.719> taken<00:08:39.959> out<00:08:40.200> after<00:08:40.360> it<00:08:40.440> was 00:08:40.550 --> 00:08:40.560 align:start position:0% thing that was taken out after it was 00:08:40.560 --> 00:08:43.190 align:start position:0% thing that was taken out after it was putting<00:08:40.839> in<00:08:41.519> was<00:08:41.719> the<00:08:41.880> simple<00:08:42.200> sub<00:08:42.479> routines 00:08:43.190 --> 00:08:43.200 align:start position:0% putting in was the simple sub routines 00:08:43.200 --> 00:08:44.470 align:start position:0% putting in was the simple sub routines and<00:08:43.360> this<00:08:43.519> also<00:08:43.719> underscored<00:08:44.240> another 00:08:44.470 --> 00:08:44.480 align:start position:0% and this also underscored another 00:08:44.480 --> 00:08:45.550 align:start position:0% and this also underscored another problem<00:08:44.640> that<00:08:44.760> we<00:08:44.839> had<00:08:44.920> during<00:08:45.080> the<00:08:45.160> design 00:08:45.550 --> 00:08:45.560 align:start position:0% problem that we had during the design 00:08:45.560 --> 00:08:46.990 align:start position:0% problem that we had during the design process<00:08:45.880> of<00:08:46.000> some<00:08:46.120> of<00:08:46.200> these<00:08:46.360> up<00:08:46.560> codes<00:08:46.760> is<00:08:46.880> we 00:08:46.990 --> 00:08:47.000 align:start position:0% process of some of these up codes is we 00:08:47.000 --> 00:08:49.030 align:start position:0% process of some of these up codes is we didn't<00:08:47.240> always<00:08:47.800> directly<00:08:48.200> interact<00:08:48.680> with<00:08:48.839> the 00:08:49.030 --> 00:08:49.040 align:start position:0% didn't always directly interact with the 00:08:49.040 --> 00:08:50.990 align:start position:0% didn't always directly interact with the compiler<00:08:49.519> developers<00:08:50.519> so<00:08:50.720> this<00:08:50.839> was 00:08:50.990 --> 00:08:51.000 align:start position:0% compiler developers so this was 00:08:51.000 --> 00:08:52.509 align:start position:0% compiler developers so this was implemented<00:08:51.480> by<00:08:51.600> all<00:08:51.720> of<00:08:51.839> the<00:08:51.959> clients<00:08:52.279> it<00:08:52.399> was 00:08:52.509 --> 00:08:52.519 align:start position:0% implemented by all of the clients it was 00:08:52.519 --> 00:08:54.790 align:start position:0% implemented by all of the clients it was ready<00:08:52.680> to<00:08:52.839> go<00:08:53.040> tests<00:08:53.360> were<00:08:53.560> written<00:08:54.320> and<00:08:54.440> then 00:08:54.790 --> 00:08:54.800 align:start position:0% ready to go tests were written and then 00:08:54.800 --> 00:08:55.829 align:start position:0% ready to go tests were written and then a<00:08:54.920> couple<00:08:55.120> of<00:08:55.240> weeks<00:08:55.440> before<00:08:55.600> we<00:08:55.720> were 00:08:55.829 --> 00:08:55.839 align:start position:0% a couple of weeks before we were 00:08:55.839 --> 00:08:57.949 align:start position:0% a couple of weeks before we were scheduling<00:08:56.279> test<00:08:56.560> Nets<00:08:57.160> someone<00:08:57.440> pointed<00:08:57.760> out 00:08:57.949 --> 00:08:57.959 align:start position:0% scheduling test Nets someone pointed out 00:08:57.959 --> 00:08:59.150 align:start position:0% scheduling test Nets someone pointed out that<00:08:58.079> solidity<00:08:58.560> said<00:08:58.760> we're<00:08:58.880> not<00:08:59.000> going<00:08:59.120> to 00:08:59.150 --> 00:08:59.160 align:start position:0% that solidity said we're not going to 00:08:59.160 --> 00:09:01.190 align:start position:0% that solidity said we're not going to use<00:08:59.320> this<00:08:59.440> this<00:08:59.560> op<00:08:59.800> code<00:09:00.360> so<00:09:00.600> solidity<00:09:01.040> is<00:09:01.120> not 00:09:01.190 --> 00:09:01.200 align:start position:0% use this this op code so solidity is not 00:09:01.200 --> 00:09:02.509 align:start position:0% use this this op code so solidity is not going<00:09:01.320> to<00:09:01.519> use<00:09:01.680> it<00:09:01.920> that<00:09:02.040> there<00:09:02.120> was<00:09:02.240> quite<00:09:02.399> a 00:09:02.509 --> 00:09:02.519 align:start position:0% going to use it that there was quite a 00:09:02.519 --> 00:09:03.990 align:start position:0% going to use it that there was quite a discussion<00:09:02.839> on<00:09:02.920> allore<00:09:03.240> devs<00:09:03.480> about<00:09:03.760> why<00:09:03.880> do 00:09:03.990 --> 00:09:04.000 align:start position:0% discussion on allore devs about why do 00:09:04.000 --> 00:09:05.550 align:start position:0% discussion on allore devs about why do we<00:09:04.160> even<00:09:04.360> have<00:09:04.519> this<00:09:04.680> in<00:09:04.880> there<00:09:05.440> and 00:09:05.550 --> 00:09:05.560 align:start position:0% we even have this in there and 00:09:05.560 --> 00:09:07.069 align:start position:0% we even have this in there and ultimately<00:09:05.959> the<00:09:06.120> decision<00:09:06.480> was<00:09:06.640> to<00:09:06.839> take<00:09:06.959> it 00:09:07.069 --> 00:09:07.079 align:start position:0% ultimately the decision was to take it 00:09:07.079 --> 00:09:08.949 align:start position:0% ultimately the decision was to take it out<00:09:07.320> I<00:09:07.399> think<00:09:07.519> it<00:09:07.600> was<00:09:07.680> in<00:09:07.839> Istanbul<00:09:08.720> and<00:09:08.839> this 00:09:08.949 --> 00:09:08.959 align:start position:0% out I think it was in Istanbul and this 00:09:08.959 --> 00:09:10.630 align:start position:0% out I think it was in Istanbul and this was<00:09:09.120> taken<00:09:09.320> out<00:09:09.440> of 00:09:10.630 --> 00:09:10.640 align:start position:0% was taken out of 00:09:10.640 --> 00:09:13.150 align:start position:0% was taken out of Istanbul<00:09:11.640> but<00:09:11.760> we<00:09:11.880> did<00:09:12.040> get<00:09:12.240> one<00:09:12.480> change<00:09:12.800> in 00:09:13.150 --> 00:09:13.160 align:start position:0% Istanbul but we did get one change in 00:09:13.160 --> 00:09:14.790 align:start position:0% Istanbul but we did get one change in before<00:09:13.680> before<00:09:13.880> the<00:09:14.000> merge<00:09:14.360> that<00:09:14.440> is<00:09:14.640> very 00:09:14.790 --> 00:09:14.800 align:start position:0% before before the merge that is very 00:09:14.800 --> 00:09:17.190 align:start position:0% before before the merge that is very important<00:09:15.160> and<00:09:15.279> foundational<00:09:15.800> for<00:09:15.959> E<00:09:16.959> any 00:09:17.190 --> 00:09:17.200 align:start position:0% important and foundational for E any 00:09:17.200 --> 00:09:19.550 align:start position:0% important and foundational for E any contract<00:09:17.600> that<00:09:17.680> begins<00:09:17.959> with<00:09:18.160> ef<00:09:19.160> um<00:09:19.320> cannot 00:09:19.550 --> 00:09:19.560 align:start position:0% contract that begins with ef um cannot 00:09:19.560 --> 00:09:21.389 align:start position:0% contract that begins with ef um cannot be<00:09:19.680> deployed<00:09:20.120> anymore<00:09:20.640> so<00:09:20.800> we<00:09:20.880> can<00:09:21.040> guarantee 00:09:21.389 --> 00:09:21.399 align:start position:0% be deployed anymore so we can guarantee 00:09:21.399 --> 00:09:23.030 align:start position:0% be deployed anymore so we can guarantee you<00:09:21.560> that<00:09:21.640> if<00:09:21.760> the<00:09:21.880> deploy<00:09:22.279> if<00:09:22.399> the<00:09:22.600> con<00:09:22.880> if<00:09:22.959> the 00:09:23.030 --> 00:09:23.040 align:start position:0% you that if the deploy if the con if the 00:09:23.040 --> 00:09:25.230 align:start position:0% you that if the deploy if the con if the code<00:09:23.240> starts<00:09:23.560> with<00:09:23.680> the<00:09:23.760> EF<00:09:24.120> bite<00:09:24.920> um<00:09:25.040> that 00:09:25.230 --> 00:09:25.240 align:start position:0% code starts with the EF bite um that 00:09:25.240 --> 00:09:26.470 align:start position:0% code starts with the EF bite um that certain<00:09:25.480> rules<00:09:25.720> will<00:09:25.839> be<00:09:25.920> able<00:09:26.040> to<00:09:26.160> appli 00:09:26.470 --> 00:09:26.480 align:start position:0% certain rules will be able to appli 00:09:26.480 --> 00:09:30.069 align:start position:0% certain rules will be able to appli within<00:09:26.720> it<00:09:27.360> so<00:09:27.640> so<00:09:27.800> as<00:09:27.959> part<00:09:28.120> of<00:09:28.240> the<00:09:28.480> Berlin<00:09:29.839> uh 00:09:30.069 --> 00:09:30.079 align:start position:0% within it so so as part of the Berlin uh 00:09:30.079 --> 00:09:32.470 align:start position:0% within it so so as part of the Berlin uh hard<00:09:30.360> Fork<00:09:31.079> that<00:09:31.240> was<00:09:31.440> passed<00:09:31.680> in<00:09:31.959> and<00:09:32.200> no<00:09:32.399> the 00:09:32.470 --> 00:09:32.480 align:start position:0% hard Fork that was passed in and no the 00:09:32.480 --> 00:09:34.350 align:start position:0% hard Fork that was passed in and no the London<00:09:32.839> hard<00:09:33.360> one<00:09:33.480> of<00:09:33.600> them<00:09:33.760> before<00:09:33.959> the<00:09:34.040> merch 00:09:34.350 --> 00:09:34.360 align:start position:0% London hard one of them before the merch 00:09:34.360 --> 00:09:35.350 align:start position:0% London hard one of them before the merch is<00:09:34.480> there's<00:09:34.640> so<00:09:34.760> many<00:09:34.920> of<00:09:35.000> them<00:09:35.120> I<00:09:35.240> keep 00:09:35.350 --> 00:09:35.360 align:start position:0% is there's so many of them I keep 00:09:35.360 --> 00:09:39.069 align:start position:0% is there's so many of them I keep forgetting<00:09:36.360> but<00:09:36.920> um<00:09:37.920> it<00:09:38.040> was<00:09:38.560> it<00:09:38.680> was<00:09:38.920> uh 00:09:39.069 --> 00:09:39.079 align:start position:0% forgetting but um it was it was uh 00:09:39.079 --> 00:09:41.310 align:start position:0% forgetting but um it was it was uh enforced<00:09:39.519> so<00:09:39.680> that<00:09:39.800> you<00:09:39.920> could<00:09:40.120> not<00:09:40.800> Implement 00:09:41.310 --> 00:09:41.320 align:start position:0% enforced so that you could not Implement 00:09:41.320 --> 00:09:43.790 align:start position:0% enforced so that you could not Implement code<00:09:42.320> that<00:09:42.480> would<00:09:42.920> uh<00:09:43.079> use<00:09:43.360> this<00:09:43.560> we<00:09:43.680> could 00:09:43.790 --> 00:09:43.800 align:start position:0% code that would uh use this we could 00:09:43.800 --> 00:09:46.150 align:start position:0% code that would uh use this we could preserve<00:09:44.200> space<00:09:44.600> for<00:09:44.839> our<00:09:45.079> for<00:09:45.240> our<00:09:45.480> validated 00:09:46.150 --> 00:09:46.160 align:start position:0% preserve space for our for our validated 00:09:46.160 --> 00:09:48.509 align:start position:0% preserve space for our for our validated contract<00:09:46.720> containers<00:09:47.720> uh<00:09:47.839> there<00:09:48.040> was<00:09:48.240> some 00:09:48.509 --> 00:09:48.519 align:start position:0% contract containers uh there was some 00:09:48.519 --> 00:09:50.350 align:start position:0% contract containers uh there was some some<00:09:49.040> uh<00:09:49.279> emojis<00:09:49.680> that<00:09:49.760> were<00:09:49.880> deployed<00:09:50.240> to 00:09:50.350 --> 00:09:50.360 align:start position:0% some uh emojis that were deployed to 00:09:50.360 --> 00:09:52.590 align:start position:0% some uh emojis that were deployed to kind<00:09:50.480> of<00:09:50.600> cause<00:09:51.240> problems<00:09:52.240> but<00:09:52.360> where<00:09:52.519> this 00:09:52.590 --> 00:09:52.600 align:start position:0% kind of cause problems but where this 00:09:52.600 --> 00:09:54.150 align:start position:0% kind of cause problems but where this brings<00:09:52.839> us<00:09:52.959> up<00:09:53.120> to<00:09:53.360> is<00:09:53.440> this<00:09:53.560> brings<00:09:53.800> us<00:09:53.920> up<00:09:54.040> to 00:09:54.150 --> 00:09:54.160 align:start position:0% brings us up to is this brings us up to 00:09:54.160 --> 00:09:56.230 align:start position:0% brings us up to is this brings us up to the<00:09:54.240> merge<00:09:55.160> and<00:09:55.279> the<00:09:55.360> merge<00:09:55.680> is<00:09:55.839> kind<00:09:55.959> of<00:09:56.079> an 00:09:56.230 --> 00:09:56.240 align:start position:0% the merge and the merge is kind of an 00:09:56.240 --> 00:09:57.870 align:start position:0% the merge and the merge is kind of an important<00:09:56.839> milestone<00:09:57.360> in<00:09:57.480> a<00:09:57.560> lot<00:09:57.680> of<00:09:57.760> these 00:09:57.870 --> 00:09:57.880 align:start position:0% important milestone in a lot of these 00:09:57.880 --> 00:09:59.870 align:start position:0% important milestone in a lot of these evm<00:09:58.200> changes<00:09:58.600> because<00:09:58.720> for<00:09:58.839> a<00:09:59.000> while<00:09:59.519> and<00:09:59.680> all 00:09:59.870 --> 00:09:59.880 align:start position:0% evm changes because for a while and all 00:09:59.880 --> 00:10:02.030 align:start position:0% evm changes because for a while and all cordev<00:10:00.440> to<00:10:00.600> ensure<00:10:01.240> that<00:10:01.360> we<00:10:01.440> were<00:10:01.640> focusing 00:10:02.030 --> 00:10:02.040 align:start position:0% cordev to ensure that we were focusing 00:10:02.040 --> 00:10:03.630 align:start position:0% cordev to ensure that we were focusing on<00:10:02.240> getting<00:10:02.480> proof<00:10:02.720> of<00:10:02.880> stake<00:10:03.200> pushed<00:10:03.480> through 00:10:03.630 --> 00:10:03.640 align:start position:0% on getting proof of stake pushed through 00:10:03.640 --> 00:10:05.430 align:start position:0% on getting proof of stake pushed through on<00:10:03.760> all<00:10:03.880> the<00:10:04.000> clients<00:10:04.920> any<00:10:05.079> and<00:10:05.240> all 00:10:05.430 --> 00:10:05.440 align:start position:0% on all the clients any and all 00:10:05.440 --> 00:10:07.509 align:start position:0% on all the clients any and all consideration<00:10:05.920> of<00:10:06.079> evm<00:10:06.480> changes<00:10:07.000> was<00:10:07.200> was<00:10:07.399> put 00:10:07.509 --> 00:10:07.519 align:start position:0% consideration of evm changes was was put 00:10:07.519 --> 00:10:09.910 align:start position:0% consideration of evm changes was was put on<00:10:07.720> pause<00:10:08.000> until<00:10:08.279> after<00:10:08.480> the<00:10:08.600> merge<00:10:09.519> so<00:10:09.680> during 00:10:09.910 --> 00:10:09.920 align:start position:0% on pause until after the merge so during 00:10:09.920 --> 00:10:11.949 align:start position:0% on pause until after the merge so during this<00:10:10.079> time<00:10:10.279> ipsilon<00:10:10.800> team<00:10:11.480> went<00:10:11.720> and<00:10:11.839> they 00:10:11.949 --> 00:10:11.959 align:start position:0% this time ipsilon team went and they 00:10:11.959 --> 00:10:13.949 align:start position:0% this time ipsilon team went and they were<00:10:12.200> cooking<00:10:12.959> and<00:10:13.120> they<00:10:13.399> they<00:10:13.600> they<00:10:13.760> thought 00:10:13.949 --> 00:10:13.959 align:start position:0% were cooking and they they they thought 00:10:13.959 --> 00:10:15.150 align:start position:0% were cooking and they they they thought about<00:10:14.160> all<00:10:14.279> the<00:10:14.440> things<00:10:14.680> that<00:10:14.800> they<00:10:14.920> learned 00:10:15.150 --> 00:10:15.160 align:start position:0% about all the things that they learned 00:10:15.160 --> 00:10:17.030 align:start position:0% about all the things that they learned from<00:10:15.360> ewam<00:10:16.040> and<00:10:16.240> they<00:10:16.399> came<00:10:16.560> up<00:10:16.720> with<00:10:16.839> this 00:10:17.030 --> 00:10:17.040 align:start position:0% from ewam and they came up with this 00:10:17.040 --> 00:10:19.350 align:start position:0% from ewam and they came up with this plan<00:10:17.279> for<00:10:17.600> for<00:10:17.760> eof<00:10:18.600> and<00:10:18.720> they<00:10:18.880> presented<00:10:19.240> it 00:10:19.350 --> 00:10:19.360 align:start position:0% plan for for eof and they presented it 00:10:19.360 --> 00:10:21.949 align:start position:0% plan for for eof and they presented it at<00:10:19.480> Devcon<00:10:20.240> Bogota<00:10:21.240> and<00:10:21.320> that<00:10:21.440> brings<00:10:21.680> us<00:10:21.800> to 00:10:21.949 --> 00:10:21.959 align:start position:0% at Devcon Bogota and that brings us to 00:10:21.959 --> 00:10:24.509 align:start position:0% at Devcon Bogota and that brings us to talking<00:10:22.240> about<00:10:22.480> little<00:10:22.800> eof<00:10:23.160> and<00:10:23.360> big<00:10:23.560> EF<00:10:24.360> they 00:10:24.509 --> 00:10:24.519 align:start position:0% talking about little eof and big EF they 00:10:24.519 --> 00:10:26.269 align:start position:0% talking about little eof and big EF they had<00:10:24.640> originally<00:10:25.040> designed<00:10:25.399> it<00:10:25.800> in<00:10:25.880> multiple 00:10:26.269 --> 00:10:26.279 align:start position:0% had originally designed it in multiple 00:10:26.279 --> 00:10:28.670 align:start position:0% had originally designed it in multiple pieces<00:10:26.640> and<00:10:27.040> the<00:10:27.279> to<00:10:27.480> present<00:10:27.760> it<00:10:27.880> to<00:10:28.360> to<00:10:28.560> all 00:10:28.670 --> 00:10:28.680 align:start position:0% pieces and the to present it to to all 00:10:28.680 --> 00:10:30.790 align:start position:0% pieces and the to present it to to all the<00:10:28.760> cevs<00:10:29.399> say<00:10:29.880> how<00:10:30.000> much<00:10:30.160> do<00:10:30.279> we<00:10:30.399> want<00:10:30.480> to<00:10:30.640> do 00:10:30.790 --> 00:10:30.800 align:start position:0% the cevs say how much do we want to do 00:10:30.800 --> 00:10:31.910 align:start position:0% the cevs say how much do we want to do do<00:10:30.880> we<00:10:30.959> want<00:10:31.079> to<00:10:31.160> do<00:10:31.279> a<00:10:31.360> little<00:10:31.480> bit<00:10:31.600> of<00:10:31.720> it<00:10:31.839> do 00:10:31.910 --> 00:10:31.920 align:start position:0% do we want to do a little bit of it do 00:10:31.920 --> 00:10:33.110 align:start position:0% do we want to do a little bit of it do we<00:10:32.000> want<00:10:32.079> to<00:10:32.200> do<00:10:32.320> a<00:10:32.399> lot<00:10:32.600> do<00:10:32.680> we<00:10:32.800> want<00:10:32.880> to<00:10:33.000> bring 00:10:33.110 --> 00:10:33.120 align:start position:0% we want to do a lot do we want to bring 00:10:33.120 --> 00:10:35.269 align:start position:0% we want to do a lot do we want to bring in<00:10:33.240> these<00:10:33.399> modules<00:10:34.120> and<00:10:34.240> do<00:10:34.360> it<00:10:34.480> all<00:10:34.760> together 00:10:35.269 --> 00:10:35.279 align:start position:0% in these modules and do it all together 00:10:35.279 --> 00:10:36.790 align:start position:0% in these modules and do it all together so<00:10:35.440> it<00:10:35.480> was<00:10:35.639> kind<00:10:35.760> of<00:10:35.839> a<00:10:36.000> cafeteria<00:10:36.480> approach 00:10:36.790 --> 00:10:36.800 align:start position:0% so it was kind of a cafeteria approach 00:10:36.800 --> 00:10:38.150 align:start position:0% so it was kind of a cafeteria approach how<00:10:36.920> much<00:10:37.040> do<00:10:37.120> we<00:10:37.279> want<00:10:37.360> to<00:10:37.480> break<00:10:37.680> as<00:10:37.839> part<00:10:38.000> of 00:10:38.150 --> 00:10:38.160 align:start position:0% how much do we want to break as part of 00:10:38.160 --> 00:10:40.150 align:start position:0% how much do we want to break as part of this<00:10:38.760> and<00:10:38.839> so<00:10:39.000> they<00:10:39.079> were<00:10:39.279> called<00:10:39.519> little<00:10:39.720> eof 00:10:40.150 --> 00:10:40.160 align:start position:0% this and so they were called little eof 00:10:40.160 --> 00:10:43.750 align:start position:0% this and so they were called little eof and<00:10:40.320> big<00:10:40.880> eoff<00:10:41.880> little<00:10:42.120> eof<00:10:42.600> started<00:10:43.079> with<00:10:43.600> the 00:10:43.750 --> 00:10:43.760 align:start position:0% and big eoff little eof started with the 00:10:43.760 --> 00:10:45.550 align:start position:0% and big eoff little eof started with the evm<00:10:44.200> object<00:10:44.480> format<00:10:44.800> V1<00:10:45.160> this<00:10:45.320> was<00:10:45.440> the 00:10:45.550 --> 00:10:45.560 align:start position:0% evm object format V1 this was the 00:10:45.560 --> 00:10:47.670 align:start position:0% evm object format V1 this was the container<00:10:45.920> format<00:10:46.320> the<00:10:46.480> foundation<00:10:47.440> code 00:10:47.670 --> 00:10:47.680 align:start position:0% container format the foundation code 00:10:47.680 --> 00:10:50.150 align:start position:0% container format the foundation code starts<00:10:48.000> EF<00:10:48.519> 0000001<00:10:49.519> you<00:10:49.639> have<00:10:49.720> a<00:10:49.800> header 00:10:50.150 --> 00:10:50.160 align:start position:0% starts EF 0000001 you have a header 00:10:50.160 --> 00:10:52.389 align:start position:0% starts EF 0000001 you have a header section<00:10:50.800> you<00:10:50.959> have<00:10:51.160> code<00:10:51.560> you<00:10:51.680> have<00:10:51.880> data<00:10:52.200> it's 00:10:52.389 --> 00:10:52.399 align:start position:0% section you have code you have data it's 00:10:52.399 --> 00:10:54.310 align:start position:0% section you have code you have data it's separated<00:10:53.399> one<00:10:53.480> of<00:10:53.600> the<00:10:53.680> neat<00:10:53.880> things<00:10:54.079> about 00:10:54.310 --> 00:10:54.320 align:start position:0% separated one of the neat things about 00:10:54.320 --> 00:10:56.870 align:start position:0% separated one of the neat things about this<00:10:54.440> that's<00:10:54.600> better<00:10:54.839> than<00:10:54.959> EIP<00:10:55.440> 615<00:10:56.440> is<00:10:56.760> you 00:10:56.870 --> 00:10:56.880 align:start position:0% this that's better than EIP 615 is you 00:10:56.880 --> 00:10:58.790 align:start position:0% this that's better than EIP 615 is you know<00:10:57.079> the<00:10:57.240> size<00:10:57.440> of<00:10:57.560> the<00:10:57.720> container<00:10:58.519> so<00:10:58.680> you 00:10:58.790 --> 00:10:58.800 align:start position:0% know the size of the container so you 00:10:58.800 --> 00:11:00.310 align:start position:0% know the size of the container so you know<00:10:58.920> if<00:10:58.959> you<00:10:59.079> get<00:10:59.320> a<00:10:59.399> truncated<00:10:59.920> eof 00:11:00.310 --> 00:11:00.320 align:start position:0% know if you get a truncated eof 00:11:00.320 --> 00:11:01.470 align:start position:0% know if you get a truncated eof container<00:11:00.720> you<00:11:00.839> know<00:11:00.959> you<00:11:01.040> don't<00:11:01.240> have<00:11:01.360> all 00:11:01.470 --> 00:11:01.480 align:start position:0% container you know you don't have all 00:11:01.480 --> 00:11:03.230 align:start position:0% container you know you don't have all the<00:11:01.639> code<00:11:02.079> and<00:11:02.200> you<00:11:02.320> can<00:11:02.480> just<00:11:02.639> reject<00:11:02.959> it<00:11:03.120> so 00:11:03.230 --> 00:11:03.240 align:start position:0% the code and you can just reject it so 00:11:03.240 --> 00:11:04.910 align:start position:0% the code and you can just reject it so you're<00:11:03.399> not<00:11:03.600> accidentally<00:11:04.000> missing<00:11:04.320> code 00:11:04.910 --> 00:11:04.920 align:start position:0% you're not accidentally missing code 00:11:04.920 --> 00:11:06.629 align:start position:0% you're not accidentally missing code that<00:11:05.000> was<00:11:05.160> something<00:11:05.440> that<00:11:05.639> uh<00:11:05.800> 615<00:11:06.360> didn't 00:11:06.629 --> 00:11:06.639 align:start position:0% that was something that uh 615 didn't 00:11:06.639 --> 00:11:08.949 align:start position:0% that was something that uh 615 didn't have<00:11:07.200> ability<00:11:07.519> to<00:11:07.680> say<00:11:08.120> the<00:11:08.279> code<00:11:08.480> ends<00:11:08.800> here 00:11:08.949 --> 00:11:08.959 align:start position:0% have ability to say the code ends here 00:11:08.959 --> 00:11:11.670 align:start position:0% have ability to say the code ends here the<00:11:09.079> data<00:11:09.320> ends<00:11:09.639> here<00:11:09.959> this<00:11:10.079> is<00:11:10.200> the<00:11:10.320> whole 00:11:11.670 --> 00:11:11.680 align:start position:0% the data ends here this is the whole 00:11:11.680 --> 00:11:13.750 align:start position:0% the data ends here this is the whole container<00:11:12.680> um<00:11:12.839> the<00:11:12.959> next<00:11:13.160> feature<00:11:13.440> that<00:11:13.560> was 00:11:13.750 --> 00:11:13.760 align:start position:0% container um the next feature that was 00:11:13.760 --> 00:11:16.150 align:start position:0% container um the next feature that was added<00:11:14.279> was<00:11:14.480> code<00:11:14.800> validation<00:11:15.639> so<00:11:15.800> for<00:11:16.000> that 00:11:16.150 --> 00:11:16.160 align:start position:0% added was code validation so for that 00:11:16.160 --> 00:11:18.230 align:start position:0% added was code validation so for that code<00:11:16.480> section<00:11:17.200> if<00:11:17.360> the<00:11:17.519> op<00:11:17.760> code<00:11:17.959> was<00:11:18.079> not 00:11:18.230 --> 00:11:18.240 align:start position:0% code section if the op code was not 00:11:18.240 --> 00:11:20.350 align:start position:0% code section if the op code was not allocated<00:11:18.760> it<00:11:18.880> couldn't<00:11:19.240> exist<00:11:19.880> and<00:11:20.040> if<00:11:20.120> you 00:11:20.350 --> 00:11:20.360 align:start position:0% allocated it couldn't exist and if you 00:11:20.360 --> 00:11:22.870 align:start position:0% allocated it couldn't exist and if you had<00:11:20.600> a<00:11:20.760> code<00:11:21.000> requiring<00:11:21.399> immediate<00:11:21.880> data<00:11:22.720> all 00:11:22.870 --> 00:11:22.880 align:start position:0% had a code requiring immediate data all 00:11:22.880 --> 00:11:24.310 align:start position:0% had a code requiring immediate data all of<00:11:22.959> the<00:11:23.079> data<00:11:23.320> for<00:11:23.480> that<00:11:23.600> immediate<00:11:24.000> had<00:11:24.120> to<00:11:24.200> be 00:11:24.310 --> 00:11:24.320 align:start position:0% of the data for that immediate had to be 00:11:24.320 --> 00:11:25.629 align:start position:0% of the data for that immediate had to be present<00:11:24.600> in<00:11:24.720> the<00:11:24.839> code<00:11:25.120> or<00:11:25.240> it<00:11:25.320> would<00:11:25.480> be 00:11:25.629 --> 00:11:25.639 align:start position:0% present in the code or it would be 00:11:25.639 --> 00:11:27.310 align:start position:0% present in the code or it would be rejected<00:11:26.440> an<00:11:26.600> important<00:11:26.880> thing<00:11:27.040> about<00:11:27.200> the 00:11:27.310 --> 00:11:27.320 align:start position:0% rejected an important thing about the 00:11:27.320 --> 00:11:29.629 align:start position:0% rejected an important thing about the eof<00:11:27.760> validation<00:11:28.160> container<00:11:28.560> format<00:11:29.320> is<00:11:29.399> if<00:11:29.519> it 00:11:29.629 --> 00:11:29.639 align:start position:0% eof validation container format is if it 00:11:29.639 --> 00:11:31.910 align:start position:0% eof validation container format is if it doesn't<00:11:30.120> parse<00:11:30.839> the<00:11:30.959> code<00:11:31.160> is<00:11:31.519> the<00:11:31.600> entire 00:11:31.910 --> 00:11:31.920 align:start position:0% doesn't parse the code is the entire 00:11:31.920 --> 00:11:33.389 align:start position:0% doesn't parse the code is the entire transaction<00:11:32.360> and<00:11:32.519> the<00:11:32.600> code<00:11:32.800> is<00:11:32.920> rejected<00:11:33.279> the 00:11:33.389 --> 00:11:33.399 align:start position:0% transaction and the code is rejected the 00:11:33.399 --> 00:11:35.430 align:start position:0% transaction and the code is rejected the contract<00:11:33.720> cannot<00:11:33.959> be<00:11:34.079> put<00:11:34.200> on<00:11:34.320> the<00:11:34.440> Chain<00:11:35.200> so 00:11:35.430 --> 00:11:35.440 align:start position:0% contract cannot be put on the Chain so 00:11:35.440 --> 00:11:37.509 align:start position:0% contract cannot be put on the Chain so similarly<00:11:35.920> with<00:11:36.040> code<00:11:36.320> validation<00:11:37.040> if<00:11:37.279> code 00:11:37.509 --> 00:11:37.519 align:start position:0% similarly with code validation if code 00:11:37.519 --> 00:11:39.230 align:start position:0% similarly with code validation if code validation<00:11:37.959> fails<00:11:38.560> the<00:11:38.720> contract<00:11:39.079> is 00:11:39.230 --> 00:11:39.240 align:start position:0% validation fails the contract is 00:11:39.240 --> 00:11:42.190 align:start position:0% validation fails the contract is rejected<00:11:39.639> and<00:11:39.800> can't<00:11:39.959> be<00:11:40.079> placed<00:11:40.320> on<00:11:40.440> the 00:11:42.190 --> 00:11:42.200 align:start position:0% rejected and can't be placed on the 00:11:42.200 --> 00:11:44.550 align:start position:0% rejected and can't be placed on the Chain<00:11:43.200> so<00:11:43.440> after<00:11:43.639> code<00:11:43.959> validation<00:11:44.440> they 00:11:44.550 --> 00:11:44.560 align:start position:0% Chain so after code validation they 00:11:44.560 --> 00:11:46.910 align:start position:0% Chain so after code validation they started<00:11:44.839> to<00:11:45.040> add<00:11:45.399> new<00:11:45.639> OP<00:11:45.959> codes<00:11:46.600> because<00:11:46.800> as 00:11:46.910 --> 00:11:46.920 align:start position:0% started to add new OP codes because as 00:11:46.920 --> 00:11:48.310 align:start position:0% started to add new OP codes because as part<00:11:47.040> of<00:11:47.160> code<00:11:47.360> validation<00:11:47.880> they<00:11:48.000> also<00:11:48.160> went 00:11:48.310 --> 00:11:48.320 align:start position:0% part of code validation they also went 00:11:48.320 --> 00:11:49.670 align:start position:0% part of code validation they also went ahead<00:11:48.519> and<00:11:48.639> banned<00:11:48.920> op<00:11:49.120> codes<00:11:49.360> they<00:11:49.440> banned 00:11:49.670 --> 00:11:49.680 align:start position:0% ahead and banned op codes they banned 00:11:49.680 --> 00:11:51.590 align:start position:0% ahead and banned op codes they banned the<00:11:49.800> old<00:11:50.000> Dynamic<00:11:50.399> jumps<00:11:50.959> and<00:11:51.120> replac<00:11:51.480> them 00:11:51.590 --> 00:11:51.600 align:start position:0% the old Dynamic jumps and replac them 00:11:51.600 --> 00:11:53.350 align:start position:0% the old Dynamic jumps and replac them with<00:11:51.760> relative<00:11:52.160> jumps<00:11:52.800> and<00:11:52.959> again<00:11:53.160> in<00:11:53.279> the 00:11:53.350 --> 00:11:53.360 align:start position:0% with relative jumps and again in the 00:11:53.360 --> 00:11:54.590 align:start position:0% with relative jumps and again in the relative<00:11:53.680> jumps<00:11:53.959> they<00:11:54.079> did<00:11:54.279> one<00:11:54.399> more 00:11:54.590 --> 00:11:54.600 align:start position:0% relative jumps they did one more 00:11:54.600 --> 00:11:56.670 align:start position:0% relative jumps they did one more Improvement<00:11:55.079> above<00:11:55.320> 615<00:11:56.120> and<00:11:56.240> that<00:11:56.360> they<00:11:56.480> made 00:11:56.670 --> 00:11:56.680 align:start position:0% Improvement above 615 and that they made 00:11:56.680 --> 00:11:58.269 align:start position:0% Improvement above 615 and that they made these<00:11:56.880> relative<00:11:57.279> jumps<00:11:57.639> not<00:11:57.760> just<00:11:57.959> static 00:11:58.269 --> 00:11:58.279 align:start position:0% these relative jumps not just static 00:11:58.279 --> 00:12:00.350 align:start position:0% these relative jumps not just static jumps<00:11:58.880> 6<00:11:59.279> 15<00:11:59.519> had<00:11:59.680> static<00:11:59.920> jumps<00:12:00.160> and<00:12:00.240> would 00:12:00.350 --> 00:12:00.360 align:start position:0% jumps 6 15 had static jumps and would 00:12:00.360 --> 00:12:02.269 align:start position:0% jumps 6 15 had static jumps and would list<00:12:00.560> the<00:12:00.680> PC<00:12:00.959> you<00:12:01.040> would<00:12:01.200> jump<00:12:01.399> to<00:12:02.000> but<00:12:02.160> these 00:12:02.269 --> 00:12:02.279 align:start position:0% list the PC you would jump to but these 00:12:02.279 --> 00:12:04.910 align:start position:0% list the PC you would jump to but these are<00:12:02.480> relative<00:12:03.000> giving<00:12:03.320> a<00:12:03.519> a<00:12:03.639> two<00:12:03.920> byte<00:12:04.519> signed 00:12:04.910 --> 00:12:04.920 align:start position:0% are relative giving a a two byte signed 00:12:04.920 --> 00:12:07.190 align:start position:0% are relative giving a a two byte signed integer<00:12:05.240> to<00:12:05.399> say<00:12:05.880> how<00:12:06.000> many<00:12:06.200> oper<00:12:06.760> before 00:12:07.190 --> 00:12:07.200 align:start position:0% integer to say how many oper before 00:12:07.200 --> 00:12:09.030 align:start position:0% integer to say how many oper before after<00:12:07.440> do<00:12:07.560> you<00:12:07.680> move<00:12:07.920> to<00:12:08.440> which<00:12:08.560> is<00:12:08.680> nice<00:12:08.880> for 00:12:09.030 --> 00:12:09.040 align:start position:0% after do you move to which is nice for 00:12:09.040 --> 00:12:10.710 align:start position:0% after do you move to which is nice for compilers<00:12:09.959> because<00:12:10.160> they<00:12:10.279> can<00:12:10.399> lift<00:12:10.600> and 00:12:10.710 --> 00:12:10.720 align:start position:0% compilers because they can lift and 00:12:10.720 --> 00:12:12.750 align:start position:0% compilers because they can lift and shift<00:12:11.320> all<00:12:11.560> the<00:12:11.680> code<00:12:11.880> that<00:12:12.040> they 00:12:12.750 --> 00:12:12.760 align:start position:0% shift all the code that they 00:12:12.760 --> 00:12:15.750 align:start position:0% shift all the code that they need<00:12:13.760> and<00:12:13.920> then<00:12:14.079> we<00:12:14.240> added<00:12:14.800> and<00:12:14.959> then<00:12:15.079> for<00:12:15.279> big 00:12:15.750 --> 00:12:15.760 align:start position:0% need and then we added and then for big 00:12:15.760 --> 00:12:17.470 align:start position:0% need and then we added and then for big we<00:12:15.880> added<00:12:16.120> functions<00:12:16.519> which<00:12:16.639> is<00:12:16.760> the<00:12:16.920> answer 00:12:17.470 --> 00:12:17.480 align:start position:0% we added functions which is the answer 00:12:17.480 --> 00:12:19.949 align:start position:0% we added functions which is the answer to<00:12:17.680> sub<00:12:17.959> routines<00:12:18.880> um<00:12:19.000> it<00:12:19.120> allows<00:12:19.440> us<00:12:19.639> to 00:12:19.949 --> 00:12:19.959 align:start position:0% to sub routines um it allows us to 00:12:19.959 --> 00:12:20.990 align:start position:0% to sub routines um it allows us to basically<00:12:20.399> provide<00:12:20.639> all<00:12:20.760> the<00:12:20.839> same 00:12:20.990 --> 00:12:21.000 align:start position:0% basically provide all the same 00:12:21.000 --> 00:12:22.470 align:start position:0% basically provide all the same functionality<00:12:21.440> with<00:12:21.560> sub<00:12:21.720> routines<00:12:22.320> just 00:12:22.470 --> 00:12:22.480 align:start position:0% functionality with sub routines just 00:12:22.480 --> 00:12:24.389 align:start position:0% functionality with sub routines just with<00:12:22.680> multiple<00:12:23.120> code<00:12:23.399> sections<00:12:24.040> and<00:12:24.160> this<00:12:24.279> is 00:12:24.389 --> 00:12:24.399 align:start position:0% with multiple code sections and this is 00:12:24.399 --> 00:12:25.829 align:start position:0% with multiple code sections and this is something<00:12:24.720> that<00:12:25.040> account<00:12:25.320> abstraction<00:12:25.720> is 00:12:25.829 --> 00:12:25.839 align:start position:0% something that account abstraction is 00:12:25.839 --> 00:12:28.069 align:start position:0% something that account abstraction is looking<00:12:26.040> to<00:12:26.199> use<00:12:26.720> to<00:12:26.959> provide<00:12:27.399> a<00:12:27.600> secondary 00:12:28.069 --> 00:12:28.079 align:start position:0% looking to use to provide a secondary 00:12:28.079 --> 00:12:29.790 align:start position:0% looking to use to provide a secondary entry<00:12:28.399> point<00:12:28.639> in<00:12:29.160> for<00:12:29.320> a<00:12:29.399> lot<00:12:29.519> of<00:12:29.639> their 00:12:29.790 --> 00:12:29.800 align:start position:0% entry point in for a lot of their 00:12:29.800 --> 00:12:31.389 align:start position:0% entry point in for a lot of their functionality<00:12:30.440> so<00:12:30.560> it's<00:12:30.680> a<00:12:30.760> bit<00:12:30.920> Superior<00:12:31.279> to 00:12:31.389 --> 00:12:31.399 align:start position:0% functionality so it's a bit Superior to 00:12:31.399 --> 00:12:33.230 align:start position:0% functionality so it's a bit Superior to subar<00:12:31.720> tees<00:12:31.920> in<00:12:32.040> that 00:12:33.230 --> 00:12:33.240 align:start position:0% subar tees in that 00:12:33.240 --> 00:12:35.670 align:start position:0% subar tees in that regard<00:12:34.240> and<00:12:34.399> finally<00:12:34.720> stack<00:12:35.079> validation<00:12:35.560> this 00:12:35.670 --> 00:12:35.680 align:start position:0% regard and finally stack validation this 00:12:35.680 --> 00:12:37.949 align:start position:0% regard and finally stack validation this is<00:12:35.760> the<00:12:35.920> most<00:12:36.160> complex<00:12:36.639> piece<00:12:36.800> of<00:12:36.920> code<00:12:37.639> um<00:12:37.760> and 00:12:37.949 --> 00:12:37.959 align:start position:0% is the most complex piece of code um and 00:12:37.959 --> 00:12:39.470 align:start position:0% is the most complex piece of code um and specification<00:12:38.680> that<00:12:38.800> is<00:12:38.920> in<00:12:39.040> it<00:12:39.160> and<00:12:39.279> I<00:12:39.399> think 00:12:39.470 --> 00:12:39.480 align:start position:0% specification that is in it and I think 00:12:39.480 --> 00:12:41.350 align:start position:0% specification that is in it and I think it's<00:12:39.639> the<00:12:39.800> most<00:12:40.040> important<00:12:40.440> piece<00:12:40.600> of<00:12:40.760> code 00:12:41.350 --> 00:12:41.360 align:start position:0% it's the most important piece of code 00:12:41.360 --> 00:12:43.949 align:start position:0% it's the most important piece of code that<00:12:41.480> is<00:12:41.600> in<00:12:41.839> big<00:12:42.240> eof<00:12:43.240> what<00:12:43.360> this<00:12:43.519> allows<00:12:43.800> us 00:12:43.949 --> 00:12:43.959 align:start position:0% that is in big eof what this allows us 00:12:43.959 --> 00:12:46.509 align:start position:0% that is in big eof what this allows us to<00:12:44.120> do<00:12:44.839> is<00:12:45.079> if<00:12:45.279> you<00:12:45.399> can<00:12:45.639> evaluate<00:12:46.079> your<00:12:46.240> code 00:12:46.509 --> 00:12:46.519 align:start position:0% to do is if you can evaluate your code 00:12:46.519 --> 00:12:47.670 align:start position:0% to do is if you can evaluate your code and<00:12:46.680> you<00:12:46.760> can<00:12:46.959> pass<00:12:47.160> all<00:12:47.279> the<00:12:47.399> stack 00:12:47.670 --> 00:12:47.680 align:start position:0% and you can pass all the stack 00:12:47.680 --> 00:12:50.110 align:start position:0% and you can pass all the stack validation<00:12:48.160> rules<00:12:48.880> then<00:12:49.040> at<00:12:49.279> runtime<00:12:49.800> for<00:12:50.000> all 00:12:50.110 --> 00:12:50.120 align:start position:0% validation rules then at runtime for all 00:12:50.120 --> 00:12:52.310 align:start position:0% validation rules then at runtime for all of<00:12:50.240> your<00:12:50.360> operands<00:12:51.320> you<00:12:51.440> can<00:12:51.639> just<00:12:51.920> ignore 00:12:52.310 --> 00:12:52.320 align:start position:0% of your operands you can just ignore 00:12:52.320 --> 00:12:54.269 align:start position:0% of your operands you can just ignore stack<00:12:52.680> validation<00:12:53.399> you<00:12:53.519> know<00:12:53.760> that<00:12:53.880> you<00:12:54.000> will 00:12:54.269 --> 00:12:54.279 align:start position:0% stack validation you know that you will 00:12:54.279 --> 00:12:56.230 align:start position:0% stack validation you know that you will have<00:12:54.519> enough<00:12:54.800> operands<00:12:55.279> on<00:12:55.399> the<00:12:55.560> stack<00:12:56.160> and 00:12:56.230 --> 00:12:56.240 align:start position:0% have enough operands on the stack and 00:12:56.240 --> 00:12:58.030 align:start position:0% have enough operands on the stack and you<00:12:56.360> know<00:12:56.519> there<00:12:56.639> will<00:12:56.760> be<00:12:56.880> room<00:12:57.079> on<00:12:57.240> the<00:12:57.440> stack 00:12:58.030 --> 00:12:58.040 align:start position:0% you know there will be room on the stack 00:12:58.040 --> 00:12:59.509 align:start position:0% you know there will be room on the stack and<00:12:58.160> you<00:12:58.240> can<00:12:58.440> remove<00:12:58.760> all<00:12:58.920> the<00:12:59.199> code<00:12:59.360> that<00:12:59.440> you 00:12:59.509 --> 00:12:59.519 align:start position:0% and you can remove all the code that you 00:12:59.519 --> 00:13:00.949 align:start position:0% and you can remove all the code that you were<00:12:59.639> doing<00:12:59.800> to<00:12:59.959> check<00:13:00.120> to<00:13:00.279> say<00:13:00.680> is<00:13:00.800> there 00:13:00.949 --> 00:13:00.959 align:start position:0% were doing to check to say is there 00:13:00.959 --> 00:13:02.230 align:start position:0% were doing to check to say is there enough<00:13:01.120> room<00:13:01.279> in<00:13:01.360> the<00:13:01.519> stack<00:13:01.920> do<00:13:02.040> I<00:13:02.120> have 00:13:02.230 --> 00:13:02.240 align:start position:0% enough room in the stack do I have 00:13:02.240 --> 00:13:03.550 align:start position:0% enough room in the stack do I have enough<00:13:02.399> operands<00:13:02.839> do<00:13:02.920> I<00:13:03.000> have<00:13:03.079> too<00:13:03.240> few 00:13:03.550 --> 00:13:03.560 align:start position:0% enough operands do I have too few 00:13:03.560 --> 00:13:06.030 align:start position:0% enough operands do I have too few operands<00:13:04.560> the<00:13:04.680> downside<00:13:05.120> is<00:13:05.240> it<00:13:05.360> makes<00:13:05.600> you<00:13:05.760> do 00:13:06.030 --> 00:13:06.040 align:start position:0% operands the downside is it makes you do 00:13:06.040 --> 00:13:08.189 align:start position:0% operands the downside is it makes you do good<00:13:06.240> things<00:13:06.480> with<00:13:06.639> code<00:13:07.360> but<00:13:07.600> any<00:13:07.800> modern 00:13:08.189 --> 00:13:08.199 align:start position:0% good things with code but any modern 00:13:08.199 --> 00:13:09.990 align:start position:0% good things with code but any modern compiler<00:13:08.920> is<00:13:09.040> going<00:13:09.160> to<00:13:09.240> spit<00:13:09.480> out<00:13:09.639> code<00:13:09.920> that 00:13:09.990 --> 00:13:10.000 align:start position:0% compiler is going to spit out code that 00:13:10.000 --> 00:13:12.069 align:start position:0% compiler is going to spit out code that is<00:13:10.160> completely<00:13:10.720> compatible<00:13:11.560> with<00:13:11.720> stack 00:13:12.069 --> 00:13:12.079 align:start position:0% is completely compatible with stack 00:13:12.079 --> 00:13:14.189 align:start position:0% is completely compatible with stack validation<00:13:13.040> one<00:13:13.240> minor<00:13:13.600> cave<00:13:13.839> yet<00:13:14.000> for<00:13:14.079> an 00:13:14.189 --> 00:13:14.199 align:start position:0% validation one minor cave yet for an 00:13:14.199 --> 00:13:16.150 align:start position:0% validation one minor cave yet for an optimization<00:13:15.160> we<00:13:15.320> added<00:13:15.560> ranges<00:13:15.959> for 00:13:16.150 --> 00:13:16.160 align:start position:0% optimization we added ranges for 00:13:16.160 --> 00:13:17.910 align:start position:0% optimization we added ranges for validations<00:13:17.079> and<00:13:17.199> this<00:13:17.279> was<00:13:17.440> useful<00:13:17.760> and 00:13:17.910 --> 00:13:17.920 align:start position:0% validations and this was useful and 00:13:17.920 --> 00:13:20.189 align:start position:0% validations and this was useful and requested<00:13:18.320> by<00:13:18.480> solidity<00:13:19.240> so<00:13:19.519> they<00:13:19.680> could<00:13:19.959> you 00:13:20.189 --> 00:13:20.199 align:start position:0% requested by solidity so they could you 00:13:20.199 --> 00:13:21.710 align:start position:0% requested by solidity so they could you have<00:13:20.360> one<00:13:20.600> revert<00:13:21.040> section<00:13:21.399> rather<00:13:21.600> than 00:13:21.710 --> 00:13:21.720 align:start position:0% have one revert section rather than 00:13:21.720 --> 00:13:23.550 align:start position:0% have one revert section rather than having<00:13:21.880> to<00:13:22.040> have<00:13:22.120> a<00:13:22.240> revert<00:13:22.600> section<00:13:23.160> for<00:13:23.320> each 00:13:23.550 --> 00:13:23.560 align:start position:0% having to have a revert section for each 00:13:23.560 --> 00:13:25.069 align:start position:0% having to have a revert section for each stack<00:13:23.880> height<00:13:24.279> so<00:13:24.440> you<00:13:24.519> can<00:13:24.639> come<00:13:24.760> into<00:13:24.959> that 00:13:25.069 --> 00:13:25.079 align:start position:0% stack height so you can come into that 00:13:25.079 --> 00:13:27.629 align:start position:0% stack height so you can come into that reverse<00:13:25.440> section<00:13:25.720> with<00:13:25.839> a<00:13:25.959> range<00:13:26.560> of<00:13:26.720> op<00:13:27.000> codes 00:13:27.629 --> 00:13:27.639 align:start position:0% reverse section with a range of op codes 00:13:27.639 --> 00:13:31.990 align:start position:0% reverse section with a range of op codes and<00:13:27.800> then<00:13:28.279> exit<00:13:28.600> the<00:13:28.720> entire<00:13:29.440> the<00:13:29.560> entire 00:13:31.990 --> 00:13:32.000 align:start position:0% 00:13:32.000 --> 00:13:34.389 align:start position:0% contract<00:13:33.000> so<00:13:33.199> this<00:13:33.320> is<00:13:33.480> a<00:13:33.639> tweet<00:13:33.920> that<00:13:34.040> I<00:13:34.160> came 00:13:34.389 --> 00:13:34.399 align:start position:0% contract so this is a tweet that I came 00:13:34.399 --> 00:13:36.870 align:start position:0% contract so this is a tweet that I came across<00:13:35.120> uh<00:13:35.560> a<00:13:35.680> few<00:13:35.880> weeks<00:13:36.160> ago<00:13:36.519> and<00:13:36.600> this<00:13:36.720> was 00:13:36.870 --> 00:13:36.880 align:start position:0% across uh a few weeks ago and this was 00:13:36.880 --> 00:13:38.430 align:start position:0% across uh a few weeks ago and this was like<00:13:37.079> some<00:13:37.440> something<00:13:37.720> really<00:13:37.959> exciting<00:13:38.279> to 00:13:38.430 --> 00:13:38.440 align:start position:0% like some something really exciting to 00:13:38.440 --> 00:13:42.790 align:start position:0% like some something really exciting to me<00:13:38.959> uh<00:13:39.760> a<00:13:40.279> uh<00:13:41.279> uh<00:13:41.399> someone<00:13:41.720> had<00:13:41.839> a<00:13:42.120> residency<00:13:42.639> as 00:13:42.790 --> 00:13:42.800 align:start position:0% me uh a uh uh someone had a residency as 00:13:42.800 --> 00:13:44.829 align:start position:0% me uh a uh uh someone had a residency as ainc<00:13:43.199> labs<00:13:43.880> and<00:13:44.000> they<00:13:44.120> went<00:13:44.360> through<00:13:44.600> and<00:13:44.720> they 00:13:44.829 --> 00:13:44.839 align:start position:0% ainc labs and they went through and they 00:13:44.839 --> 00:13:48.310 align:start position:0% ainc labs and they went through and they implemented<00:13:45.800> uh<00:13:46.000> eof<00:13:47.000> in<00:13:47.240> in<00:13:47.360> a<00:13:47.680> in<00:13:47.760> a<00:13:47.880> ZK 00:13:48.310 --> 00:13:48.320 align:start position:0% implemented uh eof in in a in a ZK 00:13:48.320 --> 00:13:50.030 align:start position:0% implemented uh eof in in a in a ZK context<00:13:48.839> with<00:13:49.040> the<00:13:49.160> same<00:13:49.360> contracts<00:13:49.760> that<00:13:49.920> way 00:13:50.030 --> 00:13:50.040 align:start position:0% context with the same contracts that way 00:13:50.040 --> 00:13:51.910 align:start position:0% context with the same contracts that way you<00:13:50.120> do<00:13:50.279> with<00:13:50.440> Legacy<00:13:51.320> and<00:13:51.440> they<00:13:51.560> got<00:13:51.680> some 00:13:51.910 --> 00:13:51.920 align:start position:0% you do with Legacy and they got some 00:13:51.920 --> 00:13:54.030 align:start position:0% you do with Legacy and they got some amazing<00:13:52.320> numbers<00:13:53.240> just<00:13:53.399> by<00:13:53.560> implementing 00:13:54.030 --> 00:13:54.040 align:start position:0% amazing numbers just by implementing 00:13:54.040 --> 00:13:56.590 align:start position:0% amazing numbers just by implementing these<00:13:54.279> features<00:13:55.279> um<00:13:55.600> you<00:13:55.759> can<00:13:56.000> get<00:13:56.160> rid<00:13:56.279> of<00:13:56.440> all 00:13:56.590 --> 00:13:56.600 align:start position:0% these features um you can get rid of all 00:13:56.600 --> 00:13:57.949 align:start position:0% these features um you can get rid of all the<00:13:56.759> stack<00:13:57.040> checks<00:13:57.320> and<00:13:57.440> a<00:13:57.519> lot<00:13:57.639> of<00:13:57.720> the<00:13:57.800> other 00:13:57.949 --> 00:13:57.959 align:start position:0% the stack checks and a lot of the other 00:13:57.959 --> 00:13:59.470 align:start position:0% the stack checks and a lot of the other validation<00:13:58.399> checks<00:13:58.680> because<00:13:58.839> you<00:13:59.199> presume 00:13:59.470 --> 00:13:59.480 align:start position:0% validation checks because you presume 00:13:59.480 --> 00:14:01.749 align:start position:0% validation checks because you presume it's<00:13:59.680> valid<00:14:00.360> and<00:14:00.480> it<00:14:00.680> reduced<00:14:01.160> in<00:14:01.279> an<00:14:01.399> improved 00:14:01.749 --> 00:14:01.759 align:start position:0% it's valid and it reduced in an improved 00:14:01.759 --> 00:14:04.389 align:start position:0% it's valid and it reduced in an improved performance<00:14:02.240> by<00:14:02.560> three<00:14:03.000> times<00:14:03.839> so<00:14:04.079> that<00:14:04.199> much 00:14:04.389 --> 00:14:04.399 align:start position:0% performance by three times so that much 00:14:04.399 --> 00:14:05.910 align:start position:0% performance by three times so that much time<00:14:04.519> was<00:14:04.680> spent<00:14:04.880> just<00:14:05.079> validating<00:14:05.560> stack 00:14:05.910 --> 00:14:05.920 align:start position:0% time was spent just validating stack 00:14:05.920 --> 00:14:07.590 align:start position:0% time was spent just validating stack Heights<00:14:06.279> and<00:14:06.440> that<00:14:06.920> that's<00:14:07.120> to<00:14:07.240> me<00:14:07.399> I<00:14:07.440> mean 00:14:07.590 --> 00:14:07.600 align:start position:0% Heights and that that's to me I mean 00:14:07.600 --> 00:14:09.389 align:start position:0% Heights and that that's to me I mean when<00:14:07.720> you<00:14:07.800> ship<00:14:08.000> a<00:14:08.079> 10%<00:14:08.480> Improvement<00:14:09.079> that's 00:14:09.389 --> 00:14:09.399 align:start position:0% when you ship a 10% Improvement that's 00:14:09.399 --> 00:14:10.710 align:start position:0% when you ship a 10% Improvement that's what<00:14:09.519> I'm<00:14:09.680> when<00:14:09.800> I<00:14:09.920> get<00:14:10.040> excited<00:14:10.360> and<00:14:10.440> I<00:14:10.560> start 00:14:10.710 --> 00:14:10.720 align:start position:0% what I'm when I get excited and I start 00:14:10.720 --> 00:14:12.949 align:start position:0% what I'm when I get excited and I start shipping<00:14:11.040> stuff<00:14:11.519> this<00:14:11.600> is<00:14:11.759> like<00:14:11.920> 300%<00:14:12.680> this<00:14:12.800> is 00:14:12.949 --> 00:14:12.959 align:start position:0% shipping stuff this is like 300% this is 00:14:12.959 --> 00:14:15.310 align:start position:0% shipping stuff this is like 300% this is better<00:14:13.160> than<00:14:13.279> I<00:14:13.440> hope<00:14:13.639> for<00:14:14.199> so<00:14:14.360> it's<00:14:14.560> already 00:14:15.310 --> 00:14:15.320 align:start position:0% better than I hope for so it's already 00:14:15.320 --> 00:14:18.470 align:start position:0% better than I hope for so it's already providing<00:14:15.800> real<00:14:16.120> value<00:14:16.399> in<00:14:16.560> ZK<00:14:17.040> context<00:14:18.040> and 00:14:18.470 --> 00:14:18.480 align:start position:0% providing real value in ZK context and 00:14:18.480 --> 00:14:20.790 align:start position:0% providing real value in ZK context and aots<00:14:19.079> they<00:14:19.279> get<00:14:19.600> they<00:14:19.720> get<00:14:20.120> benefit<00:14:20.480> but<00:14:20.639> not 00:14:20.790 --> 00:14:20.800 align:start position:0% aots they get they get benefit but not 00:14:20.800 --> 00:14:23.829 align:start position:0% aots they get they get benefit but not nearly<00:14:21.040> as<00:14:21.160> much<00:14:21.279> as<00:14:21.399> zk's<00:14:21.839> got<00:14:22.079> this<00:14:22.160> is 00:14:23.829 --> 00:14:23.839 align:start position:0% nearly as much as zk's got this is 00:14:23.839 --> 00:14:26.030 align:start position:0% nearly as much as zk's got this is amazing<00:14:24.839> so<00:14:25.000> we<00:14:25.079> were<00:14:25.240> ready<00:14:25.480> to<00:14:25.560> ship<00:14:25.800> this<00:14:25.920> in 00:14:26.030 --> 00:14:26.040 align:start position:0% amazing so we were ready to ship this in 00:14:26.040 --> 00:14:28.310 align:start position:0% amazing so we were ready to ship this in Shanghai<00:14:26.639> except<00:14:26.920> we<00:14:27.040> had<00:14:27.199> one<00:14:27.399> minor<00:14:27.759> issue 00:14:28.310 --> 00:14:28.320 align:start position:0% Shanghai except we had one minor issue 00:14:28.320 --> 00:14:30.790 align:start position:0% Shanghai except we had one minor issue with<00:14:28.440> the<00:14:28.560> solidity<00:14:29.120> Constructor<00:14:30.040> um<00:14:30.240> but<00:14:30.639> but 00:14:30.790 --> 00:14:30.800 align:start position:0% with the solidity Constructor um but but 00:14:30.800 --> 00:14:32.110 align:start position:0% with the solidity Constructor um but but vitalic<00:14:31.320> about<00:14:31.480> a<00:14:31.560> month<00:14:31.800> before<00:14:31.959> our 00:14:32.110 --> 00:14:32.120 align:start position:0% vitalic about a month before our 00:14:32.120 --> 00:14:33.749 align:start position:0% vitalic about a month before our interrupt<00:14:32.560> Dropped<00:14:32.800> a<00:14:32.880> Bomb<00:14:33.120> in<00:14:33.240> that<00:14:33.600> he 00:14:33.749 --> 00:14:33.759 align:start position:0% interrupt Dropped a Bomb in that he 00:14:33.759 --> 00:14:35.790 align:start position:0% interrupt Dropped a Bomb in that he wanted<00:14:33.959> to<00:14:34.079> get<00:14:34.199> rid<00:14:34.320> of<00:14:34.440> code<00:14:34.800> introspection 00:14:35.790 --> 00:14:35.800 align:start position:0% wanted to get rid of code introspection 00:14:35.800 --> 00:14:37.829 align:start position:0% wanted to get rid of code introspection which<00:14:35.920> was<00:14:36.120> another<00:14:36.440> thing<00:14:37.279> um<00:14:37.480> that<00:14:37.600> that<00:14:37.720> was 00:14:37.829 --> 00:14:37.839 align:start position:0% which was another thing um that that was 00:14:37.839 --> 00:14:40.150 align:start position:0% which was another thing um that that was bothering<00:14:38.160> him<00:14:38.279> for<00:14:38.480> Z<00:14:38.680> for<00:14:38.800> zks<00:14:39.360> the<00:14:39.480> ability 00:14:40.150 --> 00:14:40.160 align:start position:0% bothering him for Z for zks the ability 00:14:40.160 --> 00:14:42.310 align:start position:0% bothering him for Z for zks the ability to<00:14:40.399> take<00:14:40.880> memory<00:14:41.240> into<00:14:41.480> code<00:14:41.720> and<00:14:41.880> code<00:14:42.079> into 00:14:42.310 --> 00:14:42.320 align:start position:0% to take memory into code and code into 00:14:42.320 --> 00:14:44.110 align:start position:0% to take memory into code and code into memory<00:14:42.920> caused<00:14:43.240> all<00:14:43.360> sorts<00:14:43.600> of<00:14:43.720> problems<00:14:43.959> with 00:14:44.110 --> 00:14:44.120 align:start position:0% memory caused all sorts of problems with 00:14:44.120 --> 00:14:45.710 align:start position:0% memory caused all sorts of problems with zks<00:14:44.519> and<00:14:44.600> made<00:14:44.759> things<00:14:44.920> really<00:14:45.399> difficult<00:14:45.560> for 00:14:45.710 --> 00:14:45.720 align:start position:0% zks and made things really difficult for 00:14:45.720 --> 00:14:47.310 align:start position:0% zks and made things really difficult for them<00:14:46.079> so<00:14:46.240> we<00:14:46.320> wanted<00:14:46.519> to<00:14:46.639> remove<00:14:46.880> all<00:14:47.000> the<00:14:47.079> code 00:14:47.310 --> 00:14:47.320 align:start position:0% them so we wanted to remove all the code 00:14:47.320 --> 00:14:49.310 align:start position:0% them so we wanted to remove all the code introspection<00:14:48.320> so<00:14:48.600> the<00:14:48.680> interrupt<00:14:49.120> was 00:14:49.310 --> 00:14:49.320 align:start position:0% introspection so the interrupt was 00:14:49.320 --> 00:14:50.550 align:start position:0% introspection so the interrupt was decided<00:14:49.639> that<00:14:49.720> we<00:14:49.800> were<00:14:49.920> going<00:14:50.040> to<00:14:50.199> take<00:14:50.360> it 00:14:50.550 --> 00:14:50.560 align:start position:0% decided that we were going to take it 00:14:50.560 --> 00:14:52.670 align:start position:0% decided that we were going to take it completely<00:14:50.920> out<00:14:51.040> of<00:14:51.120> Shanghai<00:14:52.000> and<00:14:52.199> add<00:14:52.519> new 00:14:52.670 --> 00:14:52.680 align:start position:0% completely out of Shanghai and add new 00:14:52.680 --> 00:14:54.949 align:start position:0% completely out of Shanghai and add new features<00:14:53.120> to<00:14:53.240> remove<00:14:53.480> code<00:14:53.959> introspection 00:14:54.949 --> 00:14:54.959 align:start position:0% features to remove code introspection 00:14:54.959 --> 00:14:56.389 align:start position:0% features to remove code introspection and<00:14:55.120> also<00:14:55.399> everyone<00:14:55.639> said<00:14:55.920> well<00:14:56.120> while<00:14:56.240> we're 00:14:56.389 --> 00:14:56.399 align:start position:0% and also everyone said well while we're 00:14:56.399 --> 00:14:58.110 align:start position:0% and also everyone said well while we're breaking<00:14:56.759> things<00:14:57.279> let's<00:14:57.480> break<00:14:57.800> everything 00:14:58.110 --> 00:14:58.120 align:start position:0% breaking things let's break everything 00:14:58.120 --> 00:15:00.590 align:start position:0% breaking things let's break everything we<00:14:58.279> want<00:14:58.399> to<00:14:58.560> break<00:14:59.079> do<00:14:59.199> it<00:14:59.360> one<00:14:59.600> time<00:15:00.279> do<00:15:00.480> it 00:15:00.590 --> 00:15:00.600 align:start position:0% we want to break do it one time do it 00:15:00.600 --> 00:15:01.829 align:start position:0% we want to break do it one time do it once<00:15:00.720> and<00:15:00.880> for<00:15:01.079> all<00:15:01.360> because<00:15:01.480> we'll<00:15:01.639> never 00:15:01.829 --> 00:15:01.839 align:start position:0% once and for all because we'll never 00:15:01.839 --> 00:15:03.829 align:start position:0% once and for all because we'll never have<00:15:01.920> to<00:15:02.040> do<00:15:02.199> this<00:15:02.360> again<00:15:02.680> right<00:15:03.440> um<00:15:03.680> and 00:15:03.829 --> 00:15:03.839 align:start position:0% have to do this again right um and 00:15:03.839 --> 00:15:05.470 align:start position:0% have to do this again right um and hopefully<00:15:04.480> we'll<00:15:04.639> be<00:15:04.759> able<00:15:04.959> to<00:15:05.160> just<00:15:05.279> get 00:15:05.470 --> 00:15:05.480 align:start position:0% hopefully we'll be able to just get 00:15:05.480 --> 00:15:07.590 align:start position:0% hopefully we'll be able to just get everything<00:15:05.839> that<00:15:06.000> we<00:15:06.160> want<00:15:06.399> broken<00:15:07.320> and<00:15:07.480> get 00:15:07.590 --> 00:15:07.600 align:start position:0% everything that we want broken and get 00:15:07.600 --> 00:15:09.629 align:start position:0% everything that we want broken and get it<00:15:07.759> fixed<00:15:08.240> and<00:15:08.360> do<00:15:08.519> it 00:15:09.629 --> 00:15:09.639 align:start position:0% it fixed and do it 00:15:09.639 --> 00:15:12.189 align:start position:0% it fixed and do it right<00:15:10.639> so<00:15:10.839> that<00:15:10.959> brings<00:15:11.199> us<00:15:11.320> to<00:15:11.440> Mega<00:15:11.759> eof 00:15:12.189 --> 00:15:12.199 align:start position:0% right so that brings us to Mega eof 00:15:12.199 --> 00:15:13.550 align:start position:0% right so that brings us to Mega eof where<00:15:12.320> we<00:15:12.480> break<00:15:12.800> everything<00:15:13.079> that<00:15:13.199> needed<00:15:13.440> to 00:15:13.550 --> 00:15:13.560 align:start position:0% where we break everything that needed to 00:15:13.560 --> 00:15:15.550 align:start position:0% where we break everything that needed to be<00:15:13.680> broken<00:15:14.040> we<00:15:14.199> do<00:15:14.320> it<00:15:14.480> once<00:15:15.160> we<00:15:15.279> try<00:15:15.399> and 00:15:15.550 --> 00:15:15.560 align:start position:0% be broken we do it once we try and 00:15:15.560 --> 00:15:16.550 align:start position:0% be broken we do it once we try and reduce<00:15:15.800> the<00:15:15.880> number<00:15:16.040> of<00:15:16.160> times<00:15:16.320> we're<00:15:16.440> going 00:15:16.550 --> 00:15:16.560 align:start position:0% reduce the number of times we're going 00:15:16.560 --> 00:15:18.509 align:start position:0% reduce the number of times we're going to<00:15:16.639> have<00:15:16.720> to<00:15:16.880> update<00:15:17.480> the<00:15:17.639> base<00:15:17.920> major<00:15:18.240> version 00:15:18.509 --> 00:15:18.519 align:start position:0% to have to update the base major version 00:15:18.519 --> 00:15:21.150 align:start position:0% to have to update the base major version of<00:15:18.800> eof<00:15:19.800> the<00:15:19.920> first<00:15:20.120> thing<00:15:20.240> we<00:15:20.360> started<00:15:20.759> with 00:15:21.150 --> 00:15:21.160 align:start position:0% of eof the first thing we started with 00:15:21.160 --> 00:15:23.350 align:start position:0% of eof the first thing we started with is<00:15:21.880> is<00:15:22.079> contract<00:15:22.480> creation<00:15:22.839> which<00:15:22.920> is<00:15:23.040> a<00:15:23.160> code 00:15:23.350 --> 00:15:23.360 align:start position:0% is is contract creation which is a code 00:15:23.360 --> 00:15:25.470 align:start position:0% is is contract creation which is a code introspection<00:15:24.279> code<00:15:24.560> introspection<00:15:25.120> mostly 00:15:25.470 --> 00:15:25.480 align:start position:0% introspection code introspection mostly 00:15:25.480 --> 00:15:27.710 align:start position:0% introspection code introspection mostly impacts<00:15:25.880> to<00:15:26.040> create<00:15:26.360> op<00:15:26.639> codes<00:15:27.240> and<00:15:27.399> also<00:15:27.560> to 00:15:27.710 --> 00:15:27.720 align:start position:0% impacts to create op codes and also to 00:15:27.720 --> 00:15:30.309 align:start position:0% impacts to create op codes and also to create<00:15:28.000> transaction<00:15:29.000> so<00:15:29.240> the<00:15:29.759> the<00:15:29.920> solution 00:15:30.309 --> 00:15:30.319 align:start position:0% create transaction so the the solution 00:15:30.319 --> 00:15:32.590 align:start position:0% create transaction so the the solution that<00:15:30.440> eof<00:15:30.920> came<00:15:31.079> up<00:15:31.279> with<00:15:32.000> um<00:15:32.199> was<00:15:32.360> that<00:15:32.480> they 00:15:32.590 --> 00:15:32.600 align:start position:0% that eof came up with um was that they 00:15:32.600 --> 00:15:34.470 align:start position:0% that eof came up with um was that they would<00:15:32.839> put<00:15:33.120> the<00:15:33.319> subcontracts<00:15:34.040> in<00:15:34.279> as 00:15:34.470 --> 00:15:34.480 align:start position:0% would put the subcontracts in as 00:15:34.480 --> 00:15:36.309 align:start position:0% would put the subcontracts in as subobjects<00:15:35.000> in<00:15:35.120> the<00:15:35.240> container<00:15:36.040> that<00:15:36.160> would 00:15:36.309 --> 00:15:36.319 align:start position:0% subobjects in the container that would 00:15:36.319 --> 00:15:39.430 align:start position:0% subobjects in the container that would be<00:15:36.639> validated<00:15:37.639> at<00:15:37.839> a<00:15:38.040> contract<00:15:38.440> creation<00:15:38.920> time 00:15:39.430 --> 00:15:39.440 align:start position:0% be validated at a contract creation time 00:15:39.440 --> 00:15:42.030 align:start position:0% be validated at a contract creation time so<00:15:39.639> when<00:15:39.759> you<00:15:39.880> do<00:15:40.040> a<00:15:40.240> create<00:15:41.079> uh<00:15:41.519> a<00:15:41.600> create<00:15:41.839> or<00:15:41.920> a 00:15:42.030 --> 00:15:42.040 align:start position:0% so when you do a create uh a create or a 00:15:42.040 --> 00:15:43.949 align:start position:0% so when you do a create uh a create or a create<00:15:42.240> to<00:15:42.480> type<00:15:42.720> operation<00:15:43.440> you<00:15:43.600> take<00:15:43.800> that 00:15:43.949 --> 00:15:43.959 align:start position:0% create to type operation you take that 00:15:43.959 --> 00:15:45.670 align:start position:0% create to type operation you take that already<00:15:44.279> validated<00:15:44.759> code<00:15:45.079> you<00:15:45.199> deploy<00:15:45.519> it<00:15:45.600> on 00:15:45.670 --> 00:15:45.680 align:start position:0% already validated code you deploy it on 00:15:45.680 --> 00:15:47.990 align:start position:0% already validated code you deploy it on the<00:15:45.800> blockchain<00:15:46.639> validation<00:15:47.120> is<00:15:47.319> done<00:15:47.720> and<00:15:47.839> it 00:15:47.990 --> 00:15:48.000 align:start position:0% the blockchain validation is done and it 00:15:48.000 --> 00:15:49.870 align:start position:0% the blockchain validation is done and it never<00:15:48.240> has<00:15:48.360> to<00:15:48.519> hit<00:15:48.680> the<00:15:48.800> memory<00:15:49.440> so<00:15:49.560> you<00:15:49.639> say<00:15:49.800> I 00:15:49.870 --> 00:15:49.880 align:start position:0% never has to hit the memory so you say I 00:15:49.880 --> 00:15:51.430 align:start position:0% never has to hit the memory so you say I want<00:15:49.959> to<00:15:50.079> deploy<00:15:50.519> that<00:15:50.920> and<00:15:51.000> there's<00:15:51.240> some 00:15:51.430 --> 00:15:51.440 align:start position:0% want to deploy that and there's some 00:15:51.440 --> 00:15:52.509 align:start position:0% want to deploy that and there's some some<00:15:51.600> other<00:15:51.759> things<00:15:51.920> going<00:15:52.120> in<00:15:52.279> there<00:15:52.399> you're 00:15:52.509 --> 00:15:52.519 align:start position:0% some other things going in there you're 00:15:52.519 --> 00:15:54.790 align:start position:0% some other things going in there you're allowed<00:15:52.759> to<00:15:52.959> put<00:15:53.120> extra<00:15:53.440> data<00:15:53.720> into<00:15:54.000> that<00:15:54.600> and 00:15:54.790 --> 00:15:54.800 align:start position:0% allowed to put extra data into that and 00:15:54.800 --> 00:15:56.389 align:start position:0% allowed to put extra data into that and append<00:15:55.160> data<00:15:55.360> onto<00:15:55.600> the<00:15:55.720> existing<00:15:56.040> data<00:15:56.279> and 00:15:56.389 --> 00:15:56.399 align:start position:0% append data onto the existing data and 00:15:56.399 --> 00:15:57.870 align:start position:0% append data onto the existing data and let<00:15:56.519> it<00:15:56.639> grow<00:15:57.160> so<00:15:57.319> you<00:15:57.399> can<00:15:57.519> do<00:15:57.680> your 00:15:57.870 --> 00:15:57.880 align:start position:0% let it grow so you can do your 00:15:57.880 --> 00:15:59.430 align:start position:0% let it grow so you can do your Constructor<00:15:58.399> arguments 00:15:59.430 --> 00:15:59.440 align:start position:0% Constructor arguments 00:15:59.440 --> 00:16:02.389 align:start position:0% Constructor arguments um<00:15:59.600> and<00:15:59.839> do<00:16:00.040> things<00:16:00.360> like<00:16:00.680> like<00:16:01.000> the<00:16:01.519> um<00:16:02.000> Unis 00:16:02.389 --> 00:16:02.399 align:start position:0% um and do things like like the um Unis 00:16:02.399 --> 00:16:04.269 align:start position:0% um and do things like like the um Unis swaps<00:16:02.680> pair<00:16:02.959> contracts<00:16:03.399> wants<00:16:03.600> to<00:16:03.759> have<00:16:03.959> the 00:16:04.269 --> 00:16:04.279 align:start position:0% swaps pair contracts wants to have the 00:16:04.279 --> 00:16:06.509 align:start position:0% swaps pair contracts wants to have the token<00:16:04.639> numbers<00:16:05.440> burnt<00:16:05.759> into<00:16:06.000> the<00:16:06.120> code<00:16:06.360> so 00:16:06.509 --> 00:16:06.519 align:start position:0% token numbers burnt into the code so 00:16:06.519 --> 00:16:09.030 align:start position:0% token numbers burnt into the code so this<00:16:06.600> allows<00:16:06.880> you<00:16:07.000> to<00:16:07.160> do<00:16:07.600> that<00:16:08.600> um<00:16:08.720> the<00:16:08.839> next 00:16:09.030 --> 00:16:09.040 align:start position:0% this allows you to do that um the next 00:16:09.040 --> 00:16:10.509 align:start position:0% this allows you to do that um the next thing<00:16:09.199> was<00:16:09.360> the<00:16:09.519> contract<00:16:10.079> creation 00:16:10.509 --> 00:16:10.519 align:start position:0% thing was the contract creation 00:16:10.519 --> 00:16:11.949 align:start position:0% thing was the contract creation transaction<00:16:11.319> this<00:16:11.480> is<00:16:11.600> a<00:16:11.720> slight 00:16:11.949 --> 00:16:11.959 align:start position:0% transaction this is a slight 00:16:11.959 --> 00:16:13.430 align:start position:0% transaction this is a slight modification<00:16:12.480> of<00:16:12.680> existing<00:16:13.040> contract 00:16:13.430 --> 00:16:13.440 align:start position:0% modification of existing contract 00:16:13.440 --> 00:16:15.550 align:start position:0% modification of existing contract Creation<00:16:14.240> in<00:16:14.399> that<00:16:14.560> if<00:16:14.639> there's<00:16:14.880> any<00:16:15.160> data 00:16:15.550 --> 00:16:15.560 align:start position:0% Creation in that if there's any data 00:16:15.560 --> 00:16:18.670 align:start position:0% Creation in that if there's any data after<00:16:15.920> the<00:16:16.600> um<00:16:16.959> after<00:16:17.319> the<00:16:17.839> eof<00:16:18.279> container 00:16:18.670 --> 00:16:18.680 align:start position:0% after the um after the eof container 00:16:18.680 --> 00:16:20.710 align:start position:0% after the um after the eof container it's<00:16:18.880> passed<00:16:19.120> in<00:16:19.240> as<00:16:19.399> input<00:16:19.759> data<00:16:20.279> so<00:16:20.440> you<00:16:20.560> can 00:16:20.710 --> 00:16:20.720 align:start position:0% it's passed in as input data so you can 00:16:20.720 --> 00:16:22.670 align:start position:0% it's passed in as input data so you can provide<00:16:21.079> Constructor<00:16:21.639> parameters<00:16:22.519> in 00:16:22.670 --> 00:16:22.680 align:start position:0% provide Constructor parameters in 00:16:22.680 --> 00:16:24.550 align:start position:0% provide Constructor parameters in addition<00:16:23.160> to<00:16:23.440> to<00:16:23.639> creating<00:16:24.000> it<00:16:24.160> and<00:16:24.279> through 00:16:24.550 --> 00:16:24.560 align:start position:0% addition to to creating it and through 00:16:24.560 --> 00:16:26.749 align:start position:0% addition to to creating it and through this<00:16:25.079> you<00:16:25.199> can<00:16:25.440> create<00:16:25.839> objects<00:16:26.279> without<00:16:26.680> you 00:16:26.749 --> 00:16:26.759 align:start position:0% this you can create objects without you 00:16:26.759 --> 00:16:28.990 align:start position:0% this you can create objects without you can<00:16:26.880> create<00:16:27.160> contracts<00:16:28.040> without<00:16:28.319> having<00:16:28.519> to 00:16:28.990 --> 00:16:29.000 align:start position:0% can create contracts without having to 00:16:29.000 --> 00:16:31.389 align:start position:0% can create contracts without having to copy<00:16:29.279> any<00:16:29.399> of<00:16:29.519> it<00:16:29.639> to<00:16:29.880> system 00:16:31.389 --> 00:16:31.399 align:start position:0% copy any of it to system 00:16:31.399 --> 00:16:34.069 align:start position:0% copy any of it to system memory<00:16:32.399> another<00:16:32.959> request<00:16:33.360> that<00:16:33.519> came<00:16:33.759> from 00:16:34.069 --> 00:16:34.079 align:start position:0% memory another request that came from 00:16:34.079 --> 00:16:36.670 align:start position:0% memory another request that came from the<00:16:34.360> um<00:16:35.279> that<00:16:35.440> came<00:16:35.720> from<00:16:36.160> that<00:16:36.240> we<00:16:36.360> needed<00:16:36.560> to 00:16:36.670 --> 00:16:36.680 align:start position:0% the um that came from that we needed to 00:16:36.680 --> 00:16:39.629 align:start position:0% the um that came from that we needed to do<00:16:36.839> to<00:16:37.040> to<00:16:37.240> to<00:16:37.440> ensure<00:16:37.920> that<00:16:38.040> we<00:16:38.440> have<00:16:39.440> uh<00:16:39.560> I 00:16:39.629 --> 00:16:39.639 align:start position:0% do to to to ensure that we have uh I 00:16:39.639 --> 00:16:41.590 align:start position:0% do to to to ensure that we have uh I forgot<00:16:39.920> which<00:16:40.040> slide<00:16:40.279> I'm<00:16:40.399> on<00:16:41.120> um<00:16:41.319> but<00:16:41.440> one 00:16:41.590 --> 00:16:41.600 align:start position:0% forgot which slide I'm on um but one 00:16:41.600 --> 00:16:42.790 align:start position:0% forgot which slide I'm on um but one thing<00:16:41.800> we<00:16:41.880> need<00:16:42.000> to<00:16:42.160> add<00:16:42.319> to<00:16:42.440> make<00:16:42.560> sure<00:16:42.680> that 00:16:42.790 --> 00:16:42.800 align:start position:0% thing we need to add to make sure that 00:16:42.800 --> 00:16:44.629 align:start position:0% thing we need to add to make sure that we<00:16:42.920> had<00:16:43.040> code<00:16:43.240> ners<00:16:43.480> inspection<00:16:43.839> fixed<00:16:44.440> was<00:16:44.560> we 00:16:44.629 --> 00:16:44.639 align:start position:0% we had code ners inspection fixed was we 00:16:44.639 --> 00:16:45.829 align:start position:0% we had code ners inspection fixed was we need<00:16:44.800> to<00:16:44.880> be<00:16:44.959> able<00:16:45.120> to<00:16:45.160> get<00:16:45.279> out<00:16:45.440> the<00:16:45.560> data 00:16:45.829 --> 00:16:45.839 align:start position:0% need to be able to get out the data 00:16:45.839 --> 00:16:48.430 align:start position:0% need to be able to get out the data section<00:16:46.240> before<00:16:47.160> the<00:16:47.360> EXT<00:16:47.800> code<00:16:48.079> copied 00:16:48.430 --> 00:16:48.440 align:start position:0% section before the EXT code copied 00:16:48.440 --> 00:16:50.030 align:start position:0% section before the EXT code copied everything<00:16:48.720> in<00:16:48.839> the<00:16:48.959> container<00:16:49.560> so<00:16:49.680> we<00:16:49.800> needed 00:16:50.030 --> 00:16:50.040 align:start position:0% everything in the container so we needed 00:16:50.040 --> 00:16:53.550 align:start position:0% everything in the container so we needed to<00:16:50.199> add<00:16:50.360> new<00:16:50.600> OP<00:16:50.880> codes<00:16:51.720> that<00:16:51.920> would<00:16:52.440> um<00:16:53.440> that 00:16:53.550 --> 00:16:53.560 align:start position:0% to add new OP codes that would um that 00:16:53.560 --> 00:16:55.189 align:start position:0% to add new OP codes that would um that would<00:16:53.759> allow<00:16:53.959> you<00:16:54.079> to<00:16:54.240> access<00:16:54.600> just<00:16:54.759> the<00:16:54.920> data 00:16:55.189 --> 00:16:55.199 align:start position:0% would allow you to access just the data 00:16:55.199 --> 00:16:56.710 align:start position:0% would allow you to access just the data section<00:16:55.519> it's<00:16:55.720> just<00:16:55.839> your<00:16:56.120> data<00:16:56.399> section 00:16:56.710 --> 00:16:56.720 align:start position:0% section it's just your data section 00:16:56.720 --> 00:16:58.309 align:start position:0% section it's just your data section right<00:16:56.800> now<00:16:56.920> so<00:16:57.160> we<00:16:57.279> get<00:16:57.399> some<00:16:57.600> a<00:16:57.680> little<00:16:57.839> bit<00:16:57.959> of 00:16:58.309 --> 00:16:58.319 align:start position:0% right now so we get some a little bit of 00:16:58.319 --> 00:16:59.430 align:start position:0% right now so we get some a little bit of code<00:16:58.560> privac 00:16:59.430 --> 00:16:59.440 align:start position:0% code privac 00:16:59.440 --> 00:17:01.470 align:start position:0% code privac uh<00:16:59.560> benefits<00:17:00.120> there<00:17:00.720> um<00:17:00.839> so<00:17:00.959> you<00:17:01.079> can<00:17:01.319> return 00:17:01.470 --> 00:17:01.480 align:start position:0% uh benefits there um so you can return 00:17:01.480 --> 00:17:03.189 align:start position:0% uh benefits there um so you can return only<00:17:01.680> the<00:17:01.800> data<00:17:02.079> you<00:17:02.240> want<00:17:02.600> so<00:17:02.720> we<00:17:02.800> need<00:17:02.920> to<00:17:03.079> add 00:17:03.189 --> 00:17:03.199 align:start position:0% only the data you want so we need to add 00:17:03.199 --> 00:17:05.710 align:start position:0% only the data you want so we need to add new<00:17:03.360> OP<00:17:03.560> codes<00:17:03.800> for<00:17:04.319> that<00:17:05.319> and<00:17:05.400> then<00:17:05.559> after 00:17:05.710 --> 00:17:05.720 align:start position:0% new OP codes for that and then after 00:17:05.720 --> 00:17:07.029 align:start position:0% new OP codes for that and then after we're<00:17:05.880> done<00:17:06.000> with<00:17:06.120> code<00:17:06.360> introspection<00:17:06.880> the 00:17:07.029 --> 00:17:07.039 align:start position:0% we're done with code introspection the 00:17:07.039 --> 00:17:08.990 align:start position:0% we're done with code introspection the next<00:17:07.240> thing<00:17:07.839> um<00:17:07.959> was<00:17:08.120> to<00:17:08.240> get<00:17:08.319> rid<00:17:08.480> of<00:17:08.640> gas 00:17:08.990 --> 00:17:09.000 align:start position:0% next thing um was to get rid of gas 00:17:09.000 --> 00:17:11.069 align:start position:0% next thing um was to get rid of gas introspection<00:17:10.000> uh<00:17:10.199> gas<00:17:10.400> introspecting<00:17:10.959> and 00:17:11.069 --> 00:17:11.079 align:start position:0% introspection uh gas introspecting and 00:17:11.079 --> 00:17:12.510 align:start position:0% introspection uh gas introspecting and restricting<00:17:11.480> the<00:17:11.559> amount<00:17:11.720> of<00:17:11.880> gas<00:17:12.079> that<00:17:12.199> you 00:17:12.510 --> 00:17:12.520 align:start position:0% restricting the amount of gas that you 00:17:12.520 --> 00:17:14.309 align:start position:0% restricting the amount of gas that you send<00:17:12.760> on<00:17:12.919> to<00:17:13.039> your<00:17:13.160> next<00:17:13.319> layer<00:17:13.559> of<00:17:13.720> contract 00:17:14.309 --> 00:17:14.319 align:start position:0% send on to your next layer of contract 00:17:14.319 --> 00:17:16.350 align:start position:0% send on to your next layer of contract has<00:17:14.520> created<00:17:14.880> some<00:17:15.199> problems<00:17:16.120> uh<00:17:16.199> with 00:17:16.350 --> 00:17:16.360 align:start position:0% has created some problems uh with 00:17:16.360 --> 00:17:17.829 align:start position:0% has created some problems uh with breaking<00:17:16.720> contracts<00:17:17.160> when<00:17:17.240> we<00:17:17.360> increase<00:17:17.720> and 00:17:17.829 --> 00:17:17.839 align:start position:0% breaking contracts when we increase and 00:17:17.839 --> 00:17:19.630 align:start position:0% breaking contracts when we increase and change<00:17:18.079> the<00:17:18.240> gas<00:17:18.480> schedule<00:17:19.120> so<00:17:19.280> if<00:17:19.360> we<00:17:19.480> don't 00:17:19.630 --> 00:17:19.640 align:start position:0% change the gas schedule so if we don't 00:17:19.640 --> 00:17:21.189 align:start position:0% change the gas schedule so if we don't allow<00:17:19.880> you<00:17:20.000> to<00:17:20.120> mess<00:17:20.319> with<00:17:20.480> the<00:17:20.640> gas<00:17:20.880> like<00:17:21.039> that 00:17:21.189 --> 00:17:21.199 align:start position:0% allow you to mess with the gas like that 00:17:21.199 --> 00:17:22.870 align:start position:0% allow you to mess with the gas like that then<00:17:21.319> we're<00:17:21.559> safe<00:17:22.079> changing<00:17:22.480> the<00:17:22.640> gas 00:17:22.870 --> 00:17:22.880 align:start position:0% then we're safe changing the gas 00:17:22.880 --> 00:17:24.189 align:start position:0% then we're safe changing the gas schedule<00:17:23.160> and<00:17:23.240> doing<00:17:23.439> whatever<00:17:23.679> changes<00:17:23.959> are 00:17:24.189 --> 00:17:24.199 align:start position:0% schedule and doing whatever changes are 00:17:24.199 --> 00:17:26.150 align:start position:0% schedule and doing whatever changes are necessary<00:17:25.039> and<00:17:25.160> the<00:17:25.280> solution<00:17:25.679> there<00:17:25.839> is<00:17:26.039> just 00:17:26.150 --> 00:17:26.160 align:start position:0% necessary and the solution there is just 00:17:26.160 --> 00:17:27.870 align:start position:0% necessary and the solution there is just to<00:17:26.280> get<00:17:26.439> new<00:17:26.640> callop<00:17:27.120> codes<00:17:27.400> we<00:17:27.520> introduced 00:17:27.870 --> 00:17:27.880 align:start position:0% to get new callop codes we introduced 00:17:27.880 --> 00:17:30.070 align:start position:0% to get new callop codes we introduced three<00:17:28.039> new<00:17:28.160> callop<00:17:28.559> codes<00:17:29.280> that<00:17:29.440> don't<00:17:29.919> um 00:17:30.070 --> 00:17:30.080 align:start position:0% three new callop codes that don't um 00:17:30.080 --> 00:17:31.470 align:start position:0% three new callop codes that don't um have<00:17:30.240> gas<00:17:30.480> as<00:17:30.600> part<00:17:30.760> of<00:17:30.840> their<00:17:30.919> input 00:17:31.470 --> 00:17:31.480 align:start position:0% have gas as part of their input 00:17:31.480 --> 00:17:34.110 align:start position:0% have gas as part of their input parameters<00:17:32.480> um<00:17:32.799> and<00:17:33.000> also<00:17:33.400> as<00:17:33.520> a<00:17:33.679> nice<00:17:33.919> side 00:17:34.110 --> 00:17:34.120 align:start position:0% parameters um and also as a nice side 00:17:34.120 --> 00:17:36.029 align:start position:0% parameters um and also as a nice side effect<00:17:34.360> we<00:17:34.480> can<00:17:34.640> address<00:17:35.280> a<00:17:35.440> dress<00:17:35.720> Bas 00:17:36.029 --> 00:17:36.039 align:start position:0% effect we can address a dress Bas 00:17:36.039 --> 00:17:37.470 align:start position:0% effect we can address a dress Bas expansion<00:17:36.480> because<00:17:36.679> all<00:17:36.799> the<00:17:36.919> op<00:17:37.120> codes<00:17:37.360> in 00:17:37.470 --> 00:17:37.480 align:start position:0% expansion because all the op codes in 00:17:37.480 --> 00:17:41.350 align:start position:0% expansion because all the op codes in the<00:17:37.559> evm<00:17:38.400> trim<00:17:38.799> all<00:17:39.000> addresses<00:17:39.559> above<00:17:40.400> uh<00:17:41.000> 160 00:17:41.350 --> 00:17:41.360 align:start position:0% the evm trim all addresses above uh 160 00:17:41.360 --> 00:17:43.830 align:start position:0% the evm trim all addresses above uh 160 bytes<00:17:42.160> so<00:17:42.400> these<00:17:42.600> call<00:17:42.880> op<00:17:43.039> codes<00:17:43.320> do<00:17:43.480> not<00:17:43.679> so 00:17:43.830 --> 00:17:43.840 align:start position:0% bytes so these call op codes do not so 00:17:43.840 --> 00:17:45.630 align:start position:0% bytes so these call op codes do not so it's<00:17:44.000> safer<00:17:44.320> address<00:17:44.600> based<00:17:44.880> expansion<00:17:45.520> and 00:17:45.630 --> 00:17:45.640 align:start position:0% it's safer address based expansion and 00:17:45.640 --> 00:17:47.110 align:start position:0% it's safer address based expansion and that<00:17:45.760> only<00:17:45.960> leaves<00:17:46.280> balance<00:17:46.640> is<00:17:46.799> the<00:17:46.880> only 00:17:47.110 --> 00:17:47.120 align:start position:0% that only leaves balance is the only 00:17:47.120 --> 00:17:48.990 align:start position:0% that only leaves balance is the only open<00:17:47.400> op<00:17:47.640> code<00:17:48.120> and<00:17:48.240> that's<00:17:48.360> one<00:17:48.559> op<00:17:48.760> code<00:17:48.919> to 00:17:48.990 --> 00:17:49.000 align:start position:0% open op code and that's one op code to 00:17:49.000 --> 00:17:50.669 align:start position:0% open op code and that's one op code to fix<00:17:49.200> to<00:17:49.320> get<00:17:49.440> full<00:17:49.640> address<00:17:49.960> base<00:17:50.200> expansion 00:17:50.669 --> 00:17:50.679 align:start position:0% fix to get full address base expansion 00:17:50.679 --> 00:17:53.909 align:start position:0% fix to get full address base expansion safety<00:17:51.280> if<00:17:51.400> we<00:17:51.559> decide<00:17:51.840> we<00:17:51.960> want<00:17:52.080> to<00:17:52.240> do<00:17:52.919> that 00:17:53.909 --> 00:17:53.919 align:start position:0% safety if we decide we want to do that 00:17:53.919 --> 00:17:55.830 align:start position:0% safety if we decide we want to do that uh<00:17:54.039> the<00:17:54.160> compiler<00:17:54.559> teams<00:17:54.919> ask<00:17:55.120> for<00:17:55.280> a<00:17:55.360> swap<00:17:55.679> and 00:17:55.830 --> 00:17:55.840 align:start position:0% uh the compiler teams ask for a swap and 00:17:55.840 --> 00:17:57.870 align:start position:0% uh the compiler teams ask for a swap and dup<00:17:56.120> instructions<00:17:57.000> and<00:17:57.120> the<00:17:57.240> Viper<00:17:57.520> team 00:17:57.870 --> 00:17:57.880 align:start position:0% dup instructions and the Viper team 00:17:57.880 --> 00:17:59.230 align:start position:0% dup instructions and the Viper team specifically<00:17:58.320> ask<00:17:58.559> for<00:17:58.640> an<00:17:58.840> exchange 00:17:59.230 --> 00:17:59.240 align:start position:0% specifically ask for an exchange 00:17:59.240 --> 00:18:00.669 align:start position:0% specifically ask for an exchange instruction<00:18:00.000> which<00:18:00.120> is<00:18:00.280> kind<00:18:00.360> of<00:18:00.480> like<00:18:00.559> a 00:18:00.669 --> 00:18:00.679 align:start position:0% instruction which is kind of like a 00:18:00.679 --> 00:18:02.830 align:start position:0% instruction which is kind of like a super<00:18:01.000> swap<00:18:01.600> rather<00:18:01.799> than<00:18:01.919> swapping<00:18:02.400> it<00:18:02.640> at 00:18:02.830 --> 00:18:02.840 align:start position:0% super swap rather than swapping it at 00:18:02.840 --> 00:18:04.190 align:start position:0% super swap rather than swapping it at position<00:18:03.159> one<00:18:03.360> to<00:18:03.520> something<00:18:03.799> deep<00:18:03.960> in<00:18:04.080> the 00:18:04.190 --> 00:18:04.200 align:start position:0% position one to something deep in the 00:18:04.200 --> 00:18:06.470 align:start position:0% position one to something deep in the stack<00:18:04.760> you<00:18:04.960> take<00:18:05.159> something<00:18:05.559> up<00:18:05.679> to<00:18:05.840> 16<00:18:06.200> items 00:18:06.470 --> 00:18:06.480 align:start position:0% stack you take something up to 16 items 00:18:06.480 --> 00:18:08.390 align:start position:0% stack you take something up to 16 items deep<00:18:06.640> in<00:18:06.720> the<00:18:06.840> oper<00:18:07.080> an<00:18:07.320> stack<00:18:07.799> and<00:18:07.880> you<00:18:08.000> swap 00:18:08.390 --> 00:18:08.400 align:start position:0% deep in the oper an stack and you swap 00:18:08.400 --> 00:18:11.590 align:start position:0% deep in the oper an stack and you swap with<00:18:08.559> something<00:18:08.840> else<00:18:09.520> another<00:18:09.919> 16<00:18:10.400> or<00:18:10.600> so<00:18:11.400> uh 00:18:11.590 --> 00:18:11.600 align:start position:0% with something else another 16 or so uh 00:18:11.600 --> 00:18:13.549 align:start position:0% with something else another 16 or so uh spaces<00:18:12.000> deeper<00:18:12.280> in<00:18:12.360> the<00:18:12.440> oper<00:18:12.679> an<00:18:12.919> stack<00:18:13.400> so 00:18:13.549 --> 00:18:13.559 align:start position:0% spaces deeper in the oper an stack so 00:18:13.559 --> 00:18:15.070 align:start position:0% spaces deeper in the oper an stack so you<00:18:13.679> can<00:18:13.799> switch<00:18:14.120> stuff<00:18:14.360> around<00:18:14.600> you<00:18:14.720> can<00:18:14.880> save 00:18:15.070 --> 00:18:15.080 align:start position:0% you can switch stuff around you can save 00:18:15.080 --> 00:18:17.190 align:start position:0% you can switch stuff around you can save two<00:18:15.280> instructions<00:18:16.159> by<00:18:16.280> doing<00:18:16.520> one<00:18:16.760> exchange 00:18:17.190 --> 00:18:17.200 align:start position:0% two instructions by doing one exchange 00:18:17.200 --> 00:18:19.750 align:start position:0% two instructions by doing one exchange instruction<00:18:18.080> it's<00:18:18.280> pretty 00:18:19.750 --> 00:18:19.760 align:start position:0% instruction it's pretty 00:18:19.760 --> 00:18:21.870 align:start position:0% instruction it's pretty neat<00:18:20.760> now<00:18:20.960> this<00:18:21.080> wasn't<00:18:21.360> everything<00:18:21.679> that<00:18:21.760> we 00:18:21.870 --> 00:18:21.880 align:start position:0% neat now this wasn't everything that we 00:18:21.880 --> 00:18:24.029 align:start position:0% neat now this wasn't everything that we wanted<00:18:22.080> to<00:18:22.159> put<00:18:22.280> in<00:18:22.440> eof<00:18:23.200> in<00:18:23.320> order<00:18:23.600> to<00:18:23.880> uh 00:18:24.029 --> 00:18:24.039 align:start position:0% wanted to put in eof in order to uh 00:18:24.039 --> 00:18:26.830 align:start position:0% wanted to put in eof in order to uh reduce<00:18:24.320> it<00:18:24.480> and<00:18:24.600> make<00:18:24.760> it<00:18:24.919> more<00:18:25.799> um<00:18:26.600> more 00:18:26.830 --> 00:18:26.840 align:start position:0% reduce it and make it more um more 00:18:26.840 --> 00:18:28.590 align:start position:0% reduce it and make it more um more testable<00:18:27.400> and<00:18:27.559> reduce<00:18:27.840> the<00:18:27.960> attack<00:18:28.240> surfaces 00:18:28.590 --> 00:18:28.600 align:start position:0% testable and reduce the attack surfaces 00:18:28.600 --> 00:18:30.270 align:start position:0% testable and reduce the attack surfaces and<00:18:28.799> risk<00:18:29.000> surfaces<00:18:29.720> there<00:18:29.799> are<00:18:29.960> about<00:18:30.120> four 00:18:30.270 --> 00:18:30.280 align:start position:0% and risk surfaces there are about four 00:18:30.280 --> 00:18:32.390 align:start position:0% and risk surfaces there are about four features<00:18:30.640> that<00:18:30.760> we<00:18:31.080> we<00:18:31.240> removed<00:18:31.600> from<00:18:31.720> it<00:18:32.280> um 00:18:32.390 --> 00:18:32.400 align:start position:0% features that we we removed from it um 00:18:32.400 --> 00:18:34.430 align:start position:0% features that we we removed from it um TX<00:18:32.760> create<00:18:33.039> is<00:18:33.159> something<00:18:33.520> that<00:18:33.640> we<00:18:33.799> might<00:18:33.960> see 00:18:34.430 --> 00:18:34.440 align:start position:0% TX create is something that we might see 00:18:34.440 --> 00:18:36.830 align:start position:0% TX create is something that we might see return<00:18:35.280> um<00:18:35.440> it's<00:18:35.600> a<00:18:35.760> way<00:18:35.919> to<00:18:36.080> do<00:18:36.360> contract 00:18:36.830 --> 00:18:36.840 align:start position:0% return um it's a way to do contract 00:18:36.840 --> 00:18:38.990 align:start position:0% return um it's a way to do contract Creations<00:18:37.240> through<00:18:37.400> a<00:18:37.640> transaction<00:18:38.640> variable 00:18:38.990 --> 00:18:39.000 align:start position:0% Creations through a transaction variable 00:18:39.000 --> 00:18:40.549 align:start position:0% Creations through a transaction variable length<00:18:39.280> quantities<00:18:39.799> if<00:18:39.919> we<00:18:40.000> want<00:18:40.159> to<00:18:40.280> increase 00:18:40.549 --> 00:18:40.559 align:start position:0% length quantities if we want to increase 00:18:40.559 --> 00:18:43.029 align:start position:0% length quantities if we want to increase the<00:18:40.720> contract<00:18:41.120> sizes<00:18:41.520> above<00:18:41.799> 64k<00:18:42.799> we're 00:18:43.029 --> 00:18:43.039 align:start position:0% the contract sizes above 64k we're 00:18:43.039 --> 00:18:44.310 align:start position:0% the contract sizes above 64k we're probably<00:18:43.240> going<00:18:43.320> to<00:18:43.440> need<00:18:43.600> to<00:18:43.799> do<00:18:44.120> some 00:18:44.310 --> 00:18:44.320 align:start position:0% probably going to need to do some 00:18:44.320 --> 00:18:46.270 align:start position:0% probably going to need to do some changes<00:18:45.039> to<00:18:45.240> the<00:18:45.400> contracts<00:18:45.760> to<00:18:45.880> make<00:18:46.000> sure<00:18:46.159> we 00:18:46.270 --> 00:18:46.280 align:start position:0% changes to the contracts to make sure we 00:18:46.280 --> 00:18:48.630 align:start position:0% changes to the contracts to make sure we can<00:18:46.640> access<00:18:47.000> the<00:18:47.200> areas<00:18:47.960> don't<00:18:48.200> necessarily 00:18:48.630 --> 00:18:48.640 align:start position:0% can access the areas don't necessarily 00:18:48.640 --> 00:18:51.510 align:start position:0% can access the areas don't necessarily need<00:18:48.840> it<00:18:49.080> though<00:18:50.039> um<00:18:51.000> uh<00:18:51.120> there<00:18:51.200> are<00:18:51.360> some 00:18:51.510 --> 00:18:51.520 align:start position:0% need it though um uh there are some 00:18:51.520 --> 00:18:54.630 align:start position:0% need it though um uh there are some issues<00:18:51.919> with<00:18:52.240> ISP<00:18:53.240> with<00:18:53.440> the<00:18:53.679> with<00:18:53.880> the<00:18:54.120> nft 00:18:54.630 --> 00:18:54.640 align:start position:0% issues with ISP with the with the nft 00:18:54.640 --> 00:18:58.870 align:start position:0% issues with ISP with the with the nft erc's<00:18:55.400> and<00:18:55.640> with<00:18:55.840> some<00:18:56.520> some<00:18:56.919> op<00:18:57.520> um<00:18:58.520> some 00:18:58.870 --> 00:18:58.880 align:start position:0% erc's and with some some op um some 00:18:58.880 --> 00:19:00.510 align:start position:0% erc's and with some some op um some erc's<00:18:59.440> that<00:18:59.559> that<00:18:59.679> deal<00:18:59.919> with<00:19:00.080> tokens<00:19:00.400> like 00:19:00.510 --> 00:19:00.520 align:start position:0% erc's that that deal with tokens like 00:19:00.520 --> 00:19:03.430 align:start position:0% erc's that that deal with tokens like erc20<00:19:01.159> style<00:19:01.919> that<00:19:02.080> that<00:19:02.480> require<00:19:02.880> detecting 00:19:03.430 --> 00:19:03.440 align:start position:0% erc20 style that that require detecting 00:19:03.440 --> 00:19:05.230 align:start position:0% erc20 style that that require detecting if<00:19:03.640> a<00:19:03.760> contract<00:19:04.120> is<00:19:04.240> an<00:19:04.360> eoa<00:19:04.760> or<00:19:04.880> not<00:19:05.039> and<00:19:05.120> they 00:19:05.230 --> 00:19:05.240 align:start position:0% if a contract is an eoa or not and they 00:19:05.240 --> 00:19:07.549 align:start position:0% if a contract is an eoa or not and they do<00:19:05.440> that<00:19:05.600> via<00:19:06.200> code<00:19:06.520> size<00:19:07.080> so<00:19:07.200> we're<00:19:07.360> looking 00:19:07.549 --> 00:19:07.559 align:start position:0% do that via code size so we're looking 00:19:07.559 --> 00:19:09.070 align:start position:0% do that via code size so we're looking in<00:19:07.760> ways<00:19:07.960> to<00:19:08.120> address<00:19:08.440> that<00:19:08.600> we'll<00:19:08.799> probably 00:19:09.070 --> 00:19:09.080 align:start position:0% in ways to address that we'll probably 00:19:09.080 --> 00:19:11.110 align:start position:0% in ways to address that we'll probably address<00:19:09.360> that<00:19:09.480> in<00:19:09.640> Osaka<00:19:10.520> I'm<00:19:10.679> optimistic 00:19:11.110 --> 00:19:11.120 align:start position:0% address that in Osaka I'm optimistic 00:19:11.120 --> 00:19:12.909 align:start position:0% address that in Osaka I'm optimistic we'll<00:19:11.280> get<00:19:11.400> that<00:19:11.559> in<00:19:11.760> there<00:19:12.280> and<00:19:12.480> finally 00:19:12.909 --> 00:19:12.919 align:start position:0% we'll get that in there and finally 00:19:12.919 --> 00:19:14.750 align:start position:0% we'll get that in there and finally external<00:19:13.360> data<00:19:13.640> copy<00:19:14.320> um<00:19:14.400> we're<00:19:14.559> going<00:19:14.640> to 00:19:14.750 --> 00:19:14.760 align:start position:0% external data copy um we're going to 00:19:14.760 --> 00:19:17.190 align:start position:0% external data copy um we're going to investigate<00:19:15.200> that<00:19:15.320> and<00:19:15.400> figure<00:19:15.640> out<00:19:15.799> if<00:19:15.880> it's 00:19:17.190 --> 00:19:17.200 align:start position:0% investigate that and figure out if it's 00:19:17.200 --> 00:19:20.029 align:start position:0% investigate that and figure out if it's needed<00:19:18.200> so<00:19:18.440> here's<00:19:18.640> a<00:19:19.080> here's<00:19:19.240> a<00:19:19.440> diagram<00:19:19.880> that 00:19:20.029 --> 00:19:20.039 align:start position:0% needed so here's a here's a diagram that 00:19:20.039 --> 00:19:22.110 align:start position:0% needed so here's a here's a diagram that Dragon<00:19:20.400> put<00:19:20.720> together<00:19:21.400> um<00:19:21.520> that<00:19:21.679> explains<00:19:22.000> the 00:19:22.110 --> 00:19:22.120 align:start position:0% Dragon put together um that explains the 00:19:22.120 --> 00:19:23.789 align:start position:0% Dragon put together um that explains the similarities<00:19:23.039> similarities<00:19:23.559> and 00:19:23.789 --> 00:19:23.799 align:start position:0% similarities similarities and 00:19:23.799 --> 00:19:25.990 align:start position:0% similarities similarities and differences<00:19:24.400> between<00:19:24.679> eof<00:19:25.440> and<00:19:25.559> evm 00:19:25.990 --> 00:19:26.000 align:start position:0% differences between eof and evm 00:19:26.000 --> 00:19:27.950 align:start position:0% differences between eof and evm unvalidated<00:19:26.640> contracts<00:19:27.520> they're<00:19:27.720> more 00:19:27.950 --> 00:19:27.960 align:start position:0% unvalidated contracts they're more 00:19:27.960 --> 00:19:30.549 align:start position:0% unvalidated contracts they're more similar<00:19:28.400> than<00:19:28.799> are<00:19:29.000> different<00:19:29.799> eof<00:19:30.280> just<00:19:30.440> has 00:19:30.549 --> 00:19:30.559 align:start position:0% similar than are different eof just has 00:19:30.559 --> 00:19:31.909 align:start position:0% similar than are different eof just has a<00:19:30.679> container<00:19:31.120> format<00:19:31.440> and<00:19:31.600> different 00:19:31.909 --> 00:19:31.919 align:start position:0% a container format and different 00:19:31.919 --> 00:19:34.029 align:start position:0% a container format and different validation<00:19:32.360> rules<00:19:33.039> and<00:19:33.159> a<00:19:33.280> few<00:19:33.480> different<00:19:33.720> op 00:19:34.029 --> 00:19:34.039 align:start position:0% validation rules and a few different op 00:19:34.039 --> 00:19:36.470 align:start position:0% validation rules and a few different op codes<00:19:34.480> than<00:19:34.640> the<00:19:34.720> evm<00:19:35.280> does<00:19:36.000> and<00:19:36.120> when<00:19:36.240> you<00:19:36.360> go 00:19:36.470 --> 00:19:36.480 align:start position:0% codes than the evm does and when you go 00:19:36.480 --> 00:19:38.270 align:start position:0% codes than the evm does and when you go into<00:19:36.799> executing<00:19:37.240> it<00:19:37.360> it<00:19:37.480> uses<00:19:37.760> the<00:19:37.919> same 00:19:38.270 --> 00:19:38.280 align:start position:0% into executing it it uses the same 00:19:38.280 --> 00:19:40.830 align:start position:0% into executing it it uses the same execution<00:19:38.840> Logic<00:19:39.400> for<00:19:39.600> evm<00:19:40.039> and<00:19:40.159> eof<00:19:40.640> I<00:19:40.720> know 00:19:40.830 --> 00:19:40.840 align:start position:0% execution Logic for evm and eof I know 00:19:40.840 --> 00:19:42.430 align:start position:0% execution Logic for evm and eof I know I've<00:19:40.919> been<00:19:41.039> in<00:19:41.159> all<00:19:41.280> the<00:19:41.360> major<00:19:41.640> clients<00:19:42.280> it 00:19:42.430 --> 00:19:42.440 align:start position:0% I've been in all the major clients it 00:19:42.440 --> 00:19:44.830 align:start position:0% I've been in all the major clients it uses<00:19:42.760> the<00:19:42.919> same<00:19:43.159> Loop<00:19:43.600> so<00:19:43.720> it's<00:19:43.919> pretty 00:19:44.830 --> 00:19:44.840 align:start position:0% uses the same Loop so it's pretty 00:19:44.840 --> 00:19:46.950 align:start position:0% uses the same Loop so it's pretty awesome<00:19:45.840> and<00:19:46.080> I'll<00:19:46.240> just<00:19:46.360> finish<00:19:46.600> on<00:19:46.799> this 00:19:46.950 --> 00:19:46.960 align:start position:0% awesome and I'll just finish on this 00:19:46.960 --> 00:19:49.310 align:start position:0% awesome and I'll just finish on this slide<00:19:47.720> um<00:19:47.840> solidity<00:19:48.360> said<00:19:48.600> that<00:19:48.720> by<00:19:48.840> orders<00:19:49.159> of 00:19:49.310 --> 00:19:49.320 align:start position:0% slide um solidity said that by orders of 00:19:49.320 --> 00:19:51.830 align:start position:0% slide um solidity said that by orders of magnitude<00:19:50.120> the<00:19:50.240> eof<00:19:50.720> design<00:19:51.360> is<00:19:51.559> what<00:19:51.720> they 00:19:51.830 --> 00:19:51.840 align:start position:0% magnitude the eof design is what they 00:19:51.840 --> 00:19:56.510 align:start position:0% magnitude the eof design is what they want<00:19:52.080> for<00:19:52.240> the<00:19:52.360> future<00:19:52.760> of<00:19:52.960> the 00:19:56.510 --> 00:19:56.520 align:start position:0% 00:19:56.520 --> 00:20:01.750 align:start position:0% evm<00:19:57.520> right<00:19:58.080> thanks 00:20:01.750 --> 00:20:01.760 align:start position:0% 00:20:01.760 --> 00:20:03.909 align:start position:0% thank<00:20:01.960> you<00:20:02.159> thank<00:20:02.320> you<00:20:02.520> we<00:20:02.679> have<00:20:03.000> time<00:20:03.320> for<00:20:03.760> a 00:20:03.909 --> 00:20:03.919 align:start position:0% thank you thank you we have time for a 00:20:03.919 --> 00:20:04.950 align:start position:0% thank you thank you we have time for a few 00:20:04.950 --> 00:20:04.960 align:start position:0% few 00:20:04.960 --> 00:20:08.070 align:start position:0% few questions<00:20:05.960> um<00:20:06.440> and<00:20:06.720> again<00:20:06.960> you<00:20:07.080> can<00:20:07.320> vote<00:20:07.840> to 00:20:08.070 --> 00:20:08.080 align:start position:0% questions um and again you can vote to 00:20:08.080 --> 00:20:09.870 align:start position:0% questions um and again you can vote to get<00:20:08.360> the<00:20:08.520> question<00:20:08.880> that<00:20:09.000> you<00:20:09.080> want<00:20:09.360> pushed<00:20:09.679> to 00:20:09.870 --> 00:20:09.880 align:start position:0% get the question that you want pushed to 00:20:09.880 --> 00:20:11.870 align:start position:0% get the question that you want pushed to the<00:20:10.039> top<00:20:10.960> um<00:20:11.120> and<00:20:11.200> so<00:20:11.320> we're<00:20:11.440> going<00:20:11.520> to<00:20:11.640> start 00:20:11.870 --> 00:20:11.880 align:start position:0% the top um and so we're going to start 00:20:11.880 --> 00:20:13.390 align:start position:0% the top um and so we're going to start with<00:20:12.039> what<00:20:12.159> is<00:20:12.280> the<00:20:12.440> motivation<00:20:12.960> for<00:20:13.159> not 00:20:13.390 --> 00:20:13.400 align:start position:0% with what is the motivation for not 00:20:13.400 --> 00:20:15.710 align:start position:0% with what is the motivation for not allowing<00:20:13.840> eof<00:20:14.320> contracts<00:20:14.840> to<00:20:15.000> delegate<00:20:15.400> to 00:20:15.710 --> 00:20:15.720 align:start position:0% allowing eof contracts to delegate to 00:20:15.720 --> 00:20:17.990 align:start position:0% allowing eof contracts to delegate to Legacy<00:20:16.240> code<00:20:17.159> one<00:20:17.280> of<00:20:17.400> the<00:20:17.480> op<00:20:17.679> codes<00:20:17.880> we 00:20:17.990 --> 00:20:18.000 align:start position:0% Legacy code one of the op codes we 00:20:18.000 --> 00:20:19.350 align:start position:0% Legacy code one of the op codes we banned<00:20:18.240> was<00:20:18.400> self-destruct<00:20:19.240> and 00:20:19.350 --> 00:20:19.360 align:start position:0% banned was self-destruct and 00:20:19.360 --> 00:20:21.630 align:start position:0% banned was self-destruct and self-destruct<00:20:20.120> deletes<00:20:20.600> the<00:20:20.760> code<00:20:21.360> and<00:20:21.480> it 00:20:21.630 --> 00:20:21.640 align:start position:0% self-destruct deletes the code and it 00:20:21.640 --> 00:20:23.510 align:start position:0% self-destruct deletes the code and it deletes<00:20:22.000> all<00:20:22.120> of<00:20:22.240> the<00:20:22.360> storage<00:20:22.880> and<00:20:23.000> it<00:20:23.120> moves 00:20:23.510 --> 00:20:23.520 align:start position:0% deletes all of the storage and it moves 00:20:23.520 --> 00:20:25.590 align:start position:0% deletes all of the storage and it moves value<00:20:23.840> over<00:20:24.600> um<00:20:24.720> we<00:20:24.840> wanted<00:20:25.039> to<00:20:25.159> remove<00:20:25.480> the 00:20:25.590 --> 00:20:25.600 align:start position:0% value over um we wanted to remove the 00:20:25.600 --> 00:20:28.149 align:start position:0% value over um we wanted to remove the concept<00:20:25.919> of<00:20:26.039> code<00:20:26.520> disappearing<00:20:27.520> so<00:20:28.039> the 00:20:28.149 --> 00:20:28.159 align:start position:0% concept of code disappearing so the 00:20:28.159 --> 00:20:29.950 align:start position:0% concept of code disappearing so the reason<00:20:28.720> had<00:20:28.840> a<00:20:28.919> band<00:20:29.159> delegate<00:20:29.480> code<00:20:29.720> is<00:20:29.840> you 00:20:29.950 --> 00:20:29.960 align:start position:0% reason had a band delegate code is you 00:20:29.960 --> 00:20:32.390 align:start position:0% reason had a band delegate code is you could<00:20:30.120> delegate<00:20:30.559> call<00:20:31.000> into<00:20:31.760> a<00:20:31.960> legacy 00:20:32.390 --> 00:20:32.400 align:start position:0% could delegate call into a legacy 00:20:32.400 --> 00:20:33.789 align:start position:0% could delegate call into a legacy contract<00:20:32.799> that<00:20:32.919> had<00:20:33.039> a<00:20:33.120> self-destruct 00:20:33.789 --> 00:20:33.799 align:start position:0% contract that had a self-destruct 00:20:33.799 --> 00:20:35.470 align:start position:0% contract that had a self-destruct operation<00:20:34.559> and<00:20:34.679> you<00:20:34.760> could<00:20:34.919> bring<00:20:35.120> the<00:20:35.280> effect 00:20:35.470 --> 00:20:35.480 align:start position:0% operation and you could bring the effect 00:20:35.480 --> 00:20:38.549 align:start position:0% operation and you could bring the effect of<00:20:35.600> a<00:20:35.679> self-destruct<00:20:36.520> into<00:20:36.840> an<00:20:36.960> evm<00:20:37.400> OP<00:20:37.679> code 00:20:38.549 --> 00:20:38.559 align:start position:0% of a self-destruct into an evm OP code 00:20:38.559 --> 00:20:42.070 align:start position:0% of a self-destruct into an evm OP code um<00:20:39.000> and<00:20:39.240> also<00:20:39.799> delegate<00:20:40.240> call<00:20:40.960> on<00:20:41.240> alt<00:20:41.520> VMS<00:20:41.960> has 00:20:42.070 --> 00:20:42.080 align:start position:0% um and also delegate call on alt VMS has 00:20:42.080 --> 00:20:43.350 align:start position:0% um and also delegate call on alt VMS has been<00:20:42.200> an<00:20:42.360> attack<00:20:42.640> Vector<00:20:42.919> for<00:20:43.000> some<00:20:43.120> of<00:20:43.240> their 00:20:43.350 --> 00:20:43.360 align:start position:0% been an attack Vector for some of their 00:20:43.360 --> 00:20:45.270 align:start position:0% been an attack Vector for some of their pre-compiled<00:20:44.240> so<00:20:44.400> it's<00:20:44.640> just<00:20:44.760> solves<00:20:45.120> two 00:20:45.270 --> 00:20:45.280 align:start position:0% pre-compiled so it's just solves two 00:20:45.280 --> 00:20:48.310 align:start position:0% pre-compiled so it's just solves two birds<00:20:45.600> with<00:20:45.720> one<00:20:46.159> stone<00:20:47.159> thank<00:20:47.360> you<00:20:47.960> all<00:20:48.120> right 00:20:48.310 --> 00:20:48.320 align:start position:0% birds with one stone thank you all right 00:20:48.320 --> 00:20:50.549 align:start position:0% birds with one stone thank you all right is<00:20:48.520> eof<00:20:49.080> the<00:20:49.200> new<00:20:49.440> via 00:20:50.549 --> 00:20:50.559 align:start position:0% is eof the new via 00:20:50.559 --> 00:20:52.909 align:start position:0% is eof the new via IR 00:20:52.909 --> 00:20:52.919 align:start position:0% IR 00:20:52.919 --> 00:20:55.270 align:start position:0% IR um<00:20:53.919> it's<00:20:54.120> kind<00:20:54.240> of<00:20:54.320> an<00:20:54.440> inside<00:20:54.799> baseball 00:20:55.270 --> 00:20:55.280 align:start position:0% um it's kind of an inside baseball 00:20:55.280 --> 00:20:56.549 align:start position:0% um it's kind of an inside baseball question 00:20:56.549 --> 00:20:56.559 align:start position:0% question 00:20:56.559 --> 00:20:58.789 align:start position:0% question um<00:20:57.559> I<00:20:57.640> don't<00:20:57.760> know<00:20:57.960> not<00:20:58.120> not<00:20:58.280> really<00:20:58.600> I<00:20:58.679> mean 00:20:58.789 --> 00:20:58.799 align:start position:0% um I don't know not not really I mean 00:20:58.799 --> 00:21:00.350 align:start position:0% um I don't know not not really I mean some<00:20:58.880> people<00:20:59.039> don't<00:20:59.200> like<00:20:59.360> V<00:20:59.880> but<00:21:00.000> what<00:21:00.120> it<00:21:00.240> is 00:21:00.350 --> 00:21:00.360 align:start position:0% some people don't like V but what it is 00:21:00.360 --> 00:21:02.549 align:start position:0% some people don't like V but what it is going<00:21:00.440> to<00:21:00.600> solve<00:21:01.320> the<00:21:01.480> stack<00:21:01.760> to<00:21:01.960> deep<00:21:02.280> problem 00:21:02.549 --> 00:21:02.559 align:start position:0% going to solve the stack to deep problem 00:21:02.559 --> 00:21:03.590 align:start position:0% going to solve the stack to deep problem you're<00:21:02.679> going<00:21:02.760> to<00:21:02.840> be<00:21:02.919> able<00:21:03.039> to<00:21:03.120> use<00:21:03.320> more<00:21:03.440> than 00:21:03.590 --> 00:21:03.600 align:start position:0% you're going to be able to use more than 00:21:03.600 --> 00:21:09.390 align:start position:0% you're going to be able to use more than 16<00:21:04.080> variables<00:21:04.880> so<00:21:05.039> it's<00:21:05.200> better<00:21:05.480> than<00:21:05.600> the<00:21:05.720> new 00:21:09.390 --> 00:21:09.400 align:start position:0% 00:21:09.400 --> 00:21:12.470 align:start position:0% V<00:21:10.400> uh<00:21:10.559> since<00:21:10.919> eof<00:21:11.480> will<00:21:11.640> have<00:21:11.919> performance 00:21:12.470 --> 00:21:12.480 align:start position:0% V uh since eof will have performance 00:21:12.480 --> 00:21:14.549 align:start position:0% V uh since eof will have performance benefit<00:21:12.919> are<00:21:13.080> there<00:21:13.279> plans<00:21:13.559> to<00:21:13.720> decrease<00:21:14.200> gas 00:21:14.549 --> 00:21:14.559 align:start position:0% benefit are there plans to decrease gas 00:21:14.559 --> 00:21:17.230 align:start position:0% benefit are there plans to decrease gas cost<00:21:14.840> when<00:21:15.000> using<00:21:15.640> eof<00:21:16.640> um<00:21:16.799> I<00:21:16.880> think<00:21:17.039> more 00:21:17.230 --> 00:21:17.240 align:start position:0% cost when using eof um I think more 00:21:17.240 --> 00:21:18.909 align:start position:0% cost when using eof um I think more likely<00:21:17.559> we<00:21:17.679> would<00:21:17.840> increase<00:21:18.279> gas<00:21:18.559> cost<00:21:18.760> of 00:21:18.909 --> 00:21:18.919 align:start position:0% likely we would increase gas cost of 00:21:18.919 --> 00:21:21.149 align:start position:0% likely we would increase gas cost of Legacy<00:21:19.360> if<00:21:19.440> we<00:21:19.600> did<00:21:19.799> that<00:21:20.679> um<00:21:20.919> but<00:21:21.039> the 00:21:21.149 --> 00:21:21.159 align:start position:0% Legacy if we did that um but the 00:21:21.159 --> 00:21:22.870 align:start position:0% Legacy if we did that um but the performance<00:21:21.760> benefits<00:21:22.240> from<00:21:22.360> the<00:21:22.559> gas<00:21:22.720> cost 00:21:22.870 --> 00:21:22.880 align:start position:0% performance benefits from the gas cost 00:21:22.880 --> 00:21:24.470 align:start position:0% performance benefits from the gas cost of<00:21:23.000> eof<00:21:23.360> are<00:21:23.520> you<00:21:23.640> just<00:21:23.799> have<00:21:23.919> fewer<00:21:24.240> bite 00:21:24.470 --> 00:21:24.480 align:start position:0% of eof are you just have fewer bite 00:21:24.480 --> 00:21:26.669 align:start position:0% of eof are you just have fewer bite codes<00:21:25.039> you<00:21:25.159> have<00:21:25.320> fewer<00:21:25.640> operations<00:21:26.520> so 00:21:26.669 --> 00:21:26.679 align:start position:0% codes you have fewer operations so 00:21:26.679 --> 00:21:29.110 align:start position:0% codes you have fewer operations so you'll<00:21:26.840> see<00:21:27.480> um<00:21:27.760> we've<00:21:27.960> we've<00:21:28.120> measured<00:21:28.400> this 00:21:29.110 --> 00:21:29.120 align:start position:0% you'll see um we've we've measured this 00:21:29.120 --> 00:21:31.470 align:start position:0% you'll see um we've we've measured this between<00:21:29.520> like<00:21:29.679> 3<00:21:29.880> and<00:21:30.080> 5%<00:21:30.600> just<00:21:30.760> by<00:21:30.880> using<00:21:31.120> eof 00:21:31.470 --> 00:21:31.480 align:start position:0% between like 3 and 5% just by using eof 00:21:31.480 --> 00:21:32.990 align:start position:0% between like 3 and 5% just by using eof in<00:21:31.559> the<00:21:31.679> same<00:21:31.880> contracts<00:21:32.559> so<00:21:32.679> you'll<00:21:32.880> get 00:21:32.990 --> 00:21:33.000 align:start position:0% in the same contracts so you'll get 00:21:33.000 --> 00:21:34.350 align:start position:0% in the same contracts so you'll get savings<00:21:33.440> just<00:21:33.559> by<00:21:33.679> using<00:21:33.919> it<00:21:34.039> without<00:21:34.240> having 00:21:34.350 --> 00:21:34.360 align:start position:0% savings just by using it without having 00:21:34.360 --> 00:21:37.669 align:start position:0% savings just by using it without having to<00:21:34.480> change<00:21:34.760> the<00:21:34.960> schedule<00:21:36.000> amazing<00:21:37.000> how<00:21:37.279> far 00:21:37.669 --> 00:21:37.679 align:start position:0% to change the schedule amazing how far 00:21:37.679 --> 00:21:40.549 align:start position:0% to change the schedule amazing how far is<00:21:37.840> solidity<00:21:38.400> support<00:21:38.799> for<00:21:39.000> eof<00:21:39.919> um<00:21:40.039> so<00:21:40.200> the 00:21:40.549 --> 00:21:40.559 align:start position:0% is solidity support for eof um so the 00:21:40.559 --> 00:21:41.710 align:start position:0% is solidity support for eof um so the one<00:21:40.640> of<00:21:40.679> the<00:21:40.760> engineers<00:21:41.120> from<00:21:41.240> the<00:21:41.320> ipsilon 00:21:41.710 --> 00:21:41.720 align:start position:0% one of the engineers from the ipsilon 00:21:41.720 --> 00:21:44.029 align:start position:0% one of the engineers from the ipsilon team<00:21:42.080> has<00:21:42.320> a<00:21:42.559> prototype<00:21:43.320> that<00:21:43.520> compiles<00:21:43.919> to 00:21:44.029 --> 00:21:44.039 align:start position:0% team has a prototype that compiles to 00:21:44.039 --> 00:21:46.470 align:start position:0% team has a prototype that compiles to the<00:21:44.200> existing<00:21:44.679> format<00:21:45.039> of<00:21:45.159> eof<00:21:45.559> V1<00:21:46.200> and<00:21:46.360> that's 00:21:46.470 --> 00:21:46.480 align:start position:0% the existing format of eof V1 and that's 00:21:46.480 --> 00:21:48.510 align:start position:0% the existing format of eof V1 and that's where<00:21:46.640> we<00:21:46.760> got<00:21:46.960> our<00:21:47.159> numbers<00:21:47.520> for<00:21:47.679> the<00:21:47.799> 3<00:21:47.960> to<00:21:48.080> 5% 00:21:48.510 --> 00:21:48.520 align:start position:0% where we got our numbers for the 3 to 5% 00:21:48.520 --> 00:21:51.269 align:start position:0% where we got our numbers for the 3 to 5% gas<00:21:48.760> savings<00:21:49.559> so<00:21:50.000> um<00:21:50.159> EO<00:21:50.600> solidity<00:21:51.039> is<00:21:51.159> not 00:21:51.269 --> 00:21:51.279 align:start position:0% gas savings so um EO solidity is not 00:21:51.279 --> 00:21:53.710 align:start position:0% gas savings so um EO solidity is not going<00:21:51.400> to<00:21:51.520> ship<00:21:51.760> it<00:21:52.120> until<00:21:52.400> eof<00:21:52.840> ships<00:21:53.440> so<00:21:53.600> it's 00:21:53.710 --> 00:21:53.720 align:start position:0% going to ship it until eof ships so it's 00:21:53.720 --> 00:21:55.029 align:start position:0% going to ship it until eof ships so it's going<00:21:53.840> to<00:21:53.919> stay<00:21:54.080> in<00:21:54.159> a<00:21:54.279> branch<00:21:54.640> until<00:21:54.880> it 00:21:55.029 --> 00:21:55.039 align:start position:0% going to stay in a branch until it 00:21:55.039 --> 00:21:58.789 align:start position:0% going to stay in a branch until it actually<00:21:55.279> is<00:21:55.440> in<00:21:55.840> the<00:21:56.039> test<00:21:56.640> Nets<00:21:57.640> amazing<00:21:58.679> do 00:21:58.789 --> 00:21:58.799 align:start position:0% actually is in the test Nets amazing do 00:21:58.799 --> 00:22:00.870 align:start position:0% actually is in the test Nets amazing do you<00:21:59.000> expect<00:21:59.400> solidity<00:21:59.919> to<00:22:00.159> require<00:22:00.679> a 00:22:00.870 --> 00:22:00.880 align:start position:0% you expect solidity to require a 00:22:00.880 --> 00:22:05.110 align:start position:0% you expect solidity to require a breaking<00:22:01.360> change<00:22:01.919> between<00:22:02.520> 0<00:22:02.799> 8X<00:22:03.480> and<00:22:03.880> 0.9<00:22:04.840> to 00:22:05.110 --> 00:22:05.120 align:start position:0% breaking change between 0 8X and 0.9 to 00:22:05.120 --> 00:22:08.950 align:start position:0% breaking change between 0 8X and 0.9 to add<00:22:05.640> eof<00:22:06.520> support<00:22:07.520> um<00:22:08.200> it<00:22:08.320> wouldn't<00:22:08.600> surprise 00:22:08.950 --> 00:22:08.960 align:start position:0% add eof support um it wouldn't surprise 00:22:08.960 --> 00:22:10.750 align:start position:0% add eof support um it wouldn't surprise me<00:22:09.320> uh<00:22:09.440> that's<00:22:09.559> a<00:22:09.760> decision<00:22:10.039> for<00:22:10.200> solidity<00:22:10.600> to 00:22:10.750 --> 00:22:10.760 align:start position:0% me uh that's a decision for solidity to 00:22:10.760 --> 00:22:12.710 align:start position:0% me uh that's a decision for solidity to make<00:22:11.440> um<00:22:11.559> but<00:22:11.720> that<00:22:11.840> is<00:22:12.039> probably<00:22:12.320> the<00:22:12.480> best 00:22:12.710 --> 00:22:12.720 align:start position:0% make um but that is probably the best 00:22:12.720 --> 00:22:14.590 align:start position:0% make um but that is probably the best way<00:22:12.840> to<00:22:13.000> Signal<00:22:13.880> um<00:22:14.000> that<00:22:14.120> you're<00:22:14.240> going<00:22:14.320> to<00:22:14.400> be 00:22:14.590 --> 00:22:14.600 align:start position:0% way to Signal um that you're going to be 00:22:14.600 --> 00:22:16.909 align:start position:0% way to Signal um that you're going to be using<00:22:15.080> uh<00:22:15.200> eof<00:22:15.600> semantics<00:22:16.360> other<00:22:16.640> things<00:22:16.799> they 00:22:16.909 --> 00:22:16.919 align:start position:0% using uh eof semantics other things they 00:22:16.919 --> 00:22:18.710 align:start position:0% using uh eof semantics other things they might<00:22:17.080> require<00:22:17.520> new<00:22:17.720> pragmas<00:22:18.320> but<00:22:18.440> I<00:22:18.520> think 00:22:18.710 --> 00:22:18.720 align:start position:0% might require new pragmas but I think 00:22:18.720 --> 00:22:20.950 align:start position:0% might require new pragmas but I think that's<00:22:18.919> something<00:22:19.120> for<00:22:19.279> solidity<00:22:19.679> to 00:22:20.950 --> 00:22:20.960 align:start position:0% that's something for solidity to 00:22:20.960 --> 00:22:23.350 align:start position:0% that's something for solidity to answer<00:22:21.960> what<00:22:22.080> was<00:22:22.240> the<00:22:22.360> reason<00:22:22.760> why<00:22:22.880> solidity 00:22:23.350 --> 00:22:23.360 align:start position:0% answer what was the reason why solidity 00:22:23.360 --> 00:22:25.269 align:start position:0% answer what was the reason why solidity didn't<00:22:23.640> use<00:22:23.880> sub<00:22:24.159> routines<00:22:24.559> in<00:22:24.720> that<00:22:24.919> prior 00:22:25.269 --> 00:22:25.279 align:start position:0% didn't use sub routines in that prior 00:22:25.279 --> 00:22:27.430 align:start position:0% didn't use sub routines in that prior iteration<00:22:26.279> and<00:22:26.400> are<00:22:26.640> those<00:22:26.880> concerns 00:22:27.430 --> 00:22:27.440 align:start position:0% iteration and are those concerns 00:22:27.440 --> 00:22:29.750 align:start position:0% iteration and are those concerns mitigated<00:22:27.919> in<00:22:28.080> eof 00:22:29.750 --> 00:22:29.760 align:start position:0% mitigated in eof 00:22:29.760 --> 00:22:31.950 align:start position:0% mitigated in eof um<00:22:30.159> I<00:22:30.320> think<00:22:30.600> it<00:22:30.840> actually<00:22:31.120> cost<00:22:31.360> a<00:22:31.480> few<00:22:31.640> extra 00:22:31.950 --> 00:22:31.960 align:start position:0% um I think it actually cost a few extra 00:22:31.960 --> 00:22:34.470 align:start position:0% um I think it actually cost a few extra bites<00:22:32.919> um<00:22:33.039> the<00:22:33.120> way<00:22:33.279> it<00:22:33.400> was<00:22:33.520> implemented<00:22:34.360> um 00:22:34.470 --> 00:22:34.480 align:start position:0% bites um the way it was implemented um 00:22:34.480 --> 00:22:35.789 align:start position:0% bites um the way it was implemented um it<00:22:34.600> wasn't<00:22:34.799> saving<00:22:35.120> enough<00:22:35.320> bites<00:22:35.559> it<00:22:35.640> was 00:22:35.789 --> 00:22:35.799 align:start position:0% it wasn't saving enough bites it was 00:22:35.799 --> 00:22:37.390 align:start position:0% it wasn't saving enough bites it was actually<00:22:35.960> costing<00:22:36.200> a<00:22:36.279> few<00:22:36.480> more<00:22:36.640> bytes<00:22:37.240> and 00:22:37.390 --> 00:22:37.400 align:start position:0% actually costing a few more bytes and 00:22:37.400 --> 00:22:39.549 align:start position:0% actually costing a few more bytes and with<00:22:37.559> 24K<00:22:38.320> contract<00:22:38.720> size<00:22:39.000> limits<00:22:39.360> every 00:22:39.549 --> 00:22:39.559 align:start position:0% with 24K contract size limits every 00:22:39.559 --> 00:22:41.909 align:start position:0% with 24K contract size limits every bite's<00:22:39.919> precious<00:22:40.600> so<00:22:40.760> I<00:22:40.840> think<00:22:41.039> that<00:22:41.200> was 00:22:41.909 --> 00:22:41.919 align:start position:0% bite's precious so I think that was 00:22:41.919 --> 00:22:45.310 align:start position:0% bite's precious so I think that was their<00:22:42.080> main<00:22:42.320> motivation<00:22:42.720> for<00:22:42.919> rejecting 00:22:45.310 --> 00:22:45.320 align:start position:0% their main motivation for rejecting 00:22:45.320 --> 00:22:48.190 align:start position:0% their main motivation for rejecting it<00:22:46.320> why<00:22:46.480> does<00:22:46.720> eof<00:22:47.240> not<00:22:47.480> suffer<00:22:47.840> from<00:22:48.000> the 00:22:48.190 --> 00:22:48.200 align:start position:0% it why does eof not suffer from the 00:22:48.200 --> 00:22:49.789 align:start position:0% it why does eof not suffer from the complexity<00:22:48.720> of 00:22:49.789 --> 00:22:49.799 align:start position:0% complexity of 00:22:49.799 --> 00:22:53.230 align:start position:0% complexity of versioning<00:22:50.799> um<00:22:51.080> it<00:22:51.279> will<00:22:52.279> uh<00:22:52.600> 5<00:22:52.760> to<00:22:52.880> 10<00:22:53.039> years 00:22:53.230 --> 00:22:53.240 align:start position:0% versioning um it will uh 5 to 10 years 00:22:53.240 --> 00:22:55.110 align:start position:0% versioning um it will uh 5 to 10 years down<00:22:53.400> the<00:22:53.520> road<00:22:54.279> um<00:22:54.440> what<00:22:54.559> we're<00:22:54.720> doing<00:22:55.000> right 00:22:55.110 --> 00:22:55.120 align:start position:0% down the road um what we're doing right 00:22:55.120 --> 00:22:56.430 align:start position:0% down the road um what we're doing right now<00:22:55.240> is<00:22:55.360> what's<00:22:55.559> taking<00:22:55.799> so<00:22:56.000> long<00:22:56.159> is<00:22:56.279> we're 00:22:56.430 --> 00:22:56.440 align:start position:0% now is what's taking so long is we're 00:22:56.440 --> 00:22:58.549 align:start position:0% now is what's taking so long is we're taking<00:22:56.760> every<00:22:57.039> possible<00:22:57.320> breaking<00:22:57.679> change<00:22:58.480> so 00:22:58.549 --> 00:22:58.559 align:start position:0% taking every possible breaking change so 00:22:58.559 --> 00:22:59.870 align:start position:0% taking every possible breaking change so we<00:22:58.640> don't<00:22:58.799> have<00:22:58.880> to<00:22:59.000> do<00:22:59.120> that<00:22:59.279> major<00:22:59.559> breaking 00:22:59.870 --> 00:22:59.880 align:start position:0% we don't have to do that major breaking 00:22:59.880 --> 00:23:01.830 align:start position:0% we don't have to do that major breaking change<00:23:00.159> in<00:23:00.279> the<00:23:00.400> future<00:23:01.200> so<00:23:01.360> what<00:23:01.480> we're<00:23:01.640> left 00:23:01.830 --> 00:23:01.840 align:start position:0% change in the future so what we're left 00:23:01.840 --> 00:23:03.510 align:start position:0% change in the future so what we're left with<00:23:02.000> is<00:23:02.120> we're<00:23:02.240> left<00:23:02.400> with<00:23:02.520> a<00:23:02.640> codebase<00:23:03.360> where 00:23:03.510 --> 00:23:03.520 align:start position:0% with is we're left with a codebase where 00:23:03.520 --> 00:23:05.470 align:start position:0% with is we're left with a codebase where we<00:23:03.600> can<00:23:03.720> add<00:23:03.880> the<00:23:04.000> new<00:23:04.120> features<00:23:04.480> that<00:23:04.600> we<00:23:04.799> have 00:23:05.470 --> 00:23:05.480 align:start position:0% we can add the new features that we have 00:23:05.480 --> 00:23:07.750 align:start position:0% we can add the new features that we have in<00:23:05.720> a<00:23:05.960> compatible<00:23:06.520> way<00:23:07.039> so<00:23:07.200> when<00:23:07.360> we<00:23:07.480> add<00:23:07.640> this 00:23:07.750 --> 00:23:07.760 align:start position:0% in a compatible way so when we add this 00:23:07.760 --> 00:23:09.510 align:start position:0% in a compatible way so when we add this new<00:23:07.919> feature<00:23:08.480> every<00:23:08.799> version<00:23:09.120> of<00:23:09.279> every 00:23:09.510 --> 00:23:09.520 align:start position:0% new feature every version of every 00:23:09.520 --> 00:23:11.070 align:start position:0% new feature every version of every possible<00:23:09.799> eof<00:23:10.200> contract<00:23:10.520> that<00:23:10.679> existed 00:23:11.070 --> 00:23:11.080 align:start position:0% possible eof contract that existed 00:23:11.080 --> 00:23:13.029 align:start position:0% possible eof contract that existed before<00:23:11.760> would<00:23:11.960> still<00:23:12.159> be<00:23:12.320> compatible<00:23:12.760> in<00:23:12.880> a 00:23:13.029 --> 00:23:13.039 align:start position:0% before would still be compatible in a 00:23:13.039 --> 00:23:15.909 align:start position:0% before would still be compatible in a hypothetical<00:23:13.600> eof<00:23:14.000> v11<00:23:14.520> or<00:23:14.679> V12<00:23:15.559> so<00:23:15.720> it's 00:23:15.909 --> 00:23:15.919 align:start position:0% hypothetical eof v11 or V12 so it's 00:23:15.919 --> 00:23:18.669 align:start position:0% hypothetical eof v11 or V12 so it's fully<00:23:16.240> backwards<00:23:16.640> compatible<00:23:17.080> by 00:23:18.669 --> 00:23:18.679 align:start position:0% fully backwards compatible by 00:23:18.679 --> 00:23:20.470 align:start position:0% fully backwards compatible by Design<00:23:19.679> is 00:23:20.470 --> 00:23:20.480 align:start position:0% Design is 00:23:20.480 --> 00:23:24.830 align:start position:0% Design is eof<00:23:21.480> more<00:23:21.840> ZK<00:23:22.440> friendly<00:23:23.440> um<00:23:23.720> yes<00:23:23.919> in<00:23:24.080> two<00:23:24.360> ways 00:23:24.830 --> 00:23:24.840 align:start position:0% eof more ZK friendly um yes in two ways 00:23:24.840 --> 00:23:26.549 align:start position:0% eof more ZK friendly um yes in two ways uh<00:23:24.960> getting<00:23:25.159> rid<00:23:25.279> of<00:23:25.360> the<00:23:25.440> code<00:23:25.640> introspection 00:23:26.549 --> 00:23:26.559 align:start position:0% uh getting rid of the code introspection 00:23:26.559 --> 00:23:27.950 align:start position:0% uh getting rid of the code introspection means<00:23:26.799> they<00:23:26.960> don't<00:23:27.120> have<00:23:27.240> to<00:23:27.360> worry<00:23:27.679> about 00:23:27.950 --> 00:23:27.960 align:start position:0% means they don't have to worry about 00:23:27.960 --> 00:23:29.990 align:start position:0% means they don't have to worry about bite<00:23:28.200> code<00:23:28.600> coming<00:23:28.840> off<00:23:29.000> of<00:23:29.159> the<00:23:29.279> memory<00:23:29.880> and 00:23:29.990 --> 00:23:30.000 align:start position:0% bite code coming off of the memory and 00:23:30.000 --> 00:23:31.990 align:start position:0% bite code coming off of the memory and creating<00:23:30.320> a<00:23:30.440> new<00:23:30.640> contract<00:23:31.480> you<00:23:31.600> can<00:23:31.760> know 00:23:31.990 --> 00:23:32.000 align:start position:0% creating a new contract you can know 00:23:32.000 --> 00:23:33.990 align:start position:0% creating a new contract you can know before<00:23:32.240> you'd<00:23:32.480> write<00:23:32.640> your<00:23:32.760> ZK<00:23:33.240> proof<00:23:33.799> what 00:23:33.990 --> 00:23:34.000 align:start position:0% before you'd write your ZK proof what 00:23:34.000 --> 00:23:35.149 align:start position:0% before you'd write your ZK proof what contracts<00:23:34.400> you're<00:23:34.520> going<00:23:34.600> to<00:23:34.720> have<00:23:34.799> to<00:23:34.919> worry 00:23:35.149 --> 00:23:35.159 align:start position:0% contracts you're going to have to worry 00:23:35.159 --> 00:23:37.590 align:start position:0% contracts you're going to have to worry about<00:23:36.000> and<00:23:36.240> the<00:23:36.480> relative<00:23:36.840> jumps<00:23:37.240> in<00:23:37.400> getting 00:23:37.590 --> 00:23:37.600 align:start position:0% about and the relative jumps in getting 00:23:37.600 --> 00:23:39.549 align:start position:0% about and the relative jumps in getting rid<00:23:37.760> of<00:23:37.880> jump<00:23:38.080> test<00:23:38.360> analysis<00:23:39.080> and<00:23:39.240> being<00:23:39.400> more 00:23:39.549 --> 00:23:39.559 align:start position:0% rid of jump test analysis and being more 00:23:39.559 --> 00:23:40.549 align:start position:0% rid of jump test analysis and being more certain<00:23:39.840> about<00:23:39.960> where<00:23:40.039> your<00:23:40.159> jumps<00:23:40.400> are<00:23:40.480> going 00:23:40.549 --> 00:23:40.559 align:start position:0% certain about where your jumps are going 00:23:40.559 --> 00:23:42.630 align:start position:0% certain about where your jumps are going to<00:23:40.679> land<00:23:41.039> is 00:23:42.630 --> 00:23:42.640 align:start position:0% to land is 00:23:42.640 --> 00:23:45.390 align:start position:0% to land is huge<00:23:43.640> and<00:23:43.760> I<00:23:43.840> think<00:23:44.000> we<00:23:44.120> have<00:23:44.279> time<00:23:44.520> for<00:23:45.080> one 00:23:45.390 --> 00:23:45.400 align:start position:0% huge and I think we have time for one 00:23:45.400 --> 00:23:48.110 align:start position:0% huge and I think we have time for one maybe<00:23:45.640> two<00:23:45.880> more<00:23:46.600> uh<00:23:46.720> will<00:23:46.919> sub<00:23:47.240> routines<00:23:47.960> and 00:23:48.110 --> 00:23:48.120 align:start position:0% maybe two more uh will sub routines and 00:23:48.120 --> 00:23:51.630 align:start position:0% maybe two more uh will sub routines and eof<00:23:48.559> make<00:23:48.760> code<00:23:49.080> size<00:23:49.480> analysis<00:23:50.120> easier<00:23:51.120> um<00:23:51.440> it 00:23:51.630 --> 00:23:51.640 align:start position:0% eof make code size analysis easier um it 00:23:51.640 --> 00:23:53.789 align:start position:0% eof make code size analysis easier um it can<00:23:52.480> uh<00:23:52.679> it<00:23:52.799> depends<00:23:53.039> on<00:23:53.159> what<00:23:53.279> the<00:23:53.360> compilers 00:23:53.789 --> 00:23:53.799 align:start position:0% can uh it depends on what the compilers 00:23:53.799 --> 00:23:55.630 align:start position:0% can uh it depends on what the compilers do<00:23:54.000> with<00:23:54.120> it<00:23:54.799> and<00:23:54.960> if<00:23:55.080> people<00:23:55.279> are<00:23:55.400> trying<00:23:55.559> to 00:23:55.630 --> 00:23:55.640 align:start position:0% do with it and if people are trying to 00:23:55.640 --> 00:23:57.110 align:start position:0% do with it and if people are trying to obate<00:23:56.240> their<00:23:56.320> code<00:23:56.520> it's<00:23:56.679> going<00:23:56.760> to<00:23:56.880> provide 00:23:57.110 --> 00:23:57.120 align:start position:0% obate their code it's going to provide 00:23:57.120 --> 00:23:59.029 align:start position:0% obate their code it's going to provide new<00:23:57.240> creative<00:23:57.559> ways<00:23:57.720> to<00:23:57.840> obate<00:23:58.559> so<00:23:58.760> it's<00:23:58.919> it 00:23:59.029 --> 00:23:59.039 align:start position:0% new creative ways to obate so it's it 00:23:59.039 --> 00:24:00.390 align:start position:0% new creative ways to obate so it's it goes<00:23:59.320> both 00:24:00.390 --> 00:24:00.400 align:start position:0% goes both 00:24:00.400 --> 00:24:02.830 align:start position:0% goes both ways<00:24:01.400> this<00:24:01.520> is<00:24:01.760> this<00:24:01.840> is<00:24:01.960> a<00:24:02.120> good<00:24:02.240> one<00:24:02.559> uh<00:24:02.679> when 00:24:02.830 --> 00:24:02.840 align:start position:0% ways this is this is a good one uh when 00:24:02.840 --> 00:24:04.870 align:start position:0% ways this is this is a good one uh when can<00:24:02.960> we<00:24:03.120> get<00:24:03.240> rid<00:24:03.360> of<00:24:03.480> the<00:24:03.600> evm 00:24:04.870 --> 00:24:04.880 align:start position:0% can we get rid of the evm 00:24:04.880 --> 00:24:09.070 align:start position:0% can we get rid of the evm entirely<00:24:05.880> the<00:24:06.000> evm<00:24:06.440> or<00:24:06.559> the<00:24:06.679> Legacy<00:24:07.240> evm<00:24:08.240> um<00:24:08.880> so 00:24:09.070 --> 00:24:09.080 align:start position:0% entirely the evm or the Legacy evm um so 00:24:09.080 --> 00:24:10.510 align:start position:0% entirely the evm or the Legacy evm um so the<00:24:09.240> problem<00:24:09.440> with<00:24:09.559> the<00:24:09.679> legacy<00:24:10.039> evm<00:24:10.400> is 00:24:10.510 --> 00:24:10.520 align:start position:0% the problem with the legacy evm is 00:24:10.520 --> 00:24:12.070 align:start position:0% the problem with the legacy evm is there's<00:24:10.760> some<00:24:11.000> old<00:24:11.279> contracts<00:24:11.720> that<00:24:11.840> we<00:24:11.919> still 00:24:12.070 --> 00:24:12.080 align:start position:0% there's some old contracts that we still 00:24:12.080 --> 00:24:14.510 align:start position:0% there's some old contracts that we still need<00:24:12.200> to<00:24:12.400> support<00:24:13.320> uh<00:24:13.480> getting<00:24:13.760> rid<00:24:13.960> of<00:24:14.320> uh 00:24:14.510 --> 00:24:14.520 align:start position:0% need to support uh getting rid of uh 00:24:14.520 --> 00:24:16.190 align:start position:0% need to support uh getting rid of uh sunsetting<00:24:15.039> the<00:24:15.200> legacy<00:24:15.520> is<00:24:15.679> something<00:24:15.960> that 00:24:16.190 --> 00:24:16.200 align:start position:0% sunsetting the legacy is something that 00:24:16.200 --> 00:24:18.070 align:start position:0% sunsetting the legacy is something that we<00:24:16.320> have<00:24:16.480> in<00:24:16.640> mind<00:24:17.200> we<00:24:17.320> either<00:24:17.520> need<00:24:17.640> to<00:24:17.960> we 00:24:18.070 --> 00:24:18.080 align:start position:0% we have in mind we either need to we 00:24:18.080 --> 00:24:19.149 align:start position:0% we have in mind we either need to we don't<00:24:18.200> know<00:24:18.360> the<00:24:18.480> answer<00:24:18.640> to<00:24:18.760> it<00:24:18.880> we<00:24:18.960> need<00:24:19.039> to 00:24:19.149 --> 00:24:19.159 align:start position:0% don't know the answer to it we need to 00:24:19.159 --> 00:24:20.310 align:start position:0% don't know the answer to it we need to be<00:24:19.240> able<00:24:19.360> to<00:24:19.440> say<00:24:19.600> we<00:24:19.720> can't<00:24:19.840> do<00:24:19.960> it<00:24:20.039> because<00:24:20.240> of 00:24:20.310 --> 00:24:20.320 align:start position:0% be able to say we can't do it because of 00:24:20.320 --> 00:24:22.390 align:start position:0% be able to say we can't do it because of reasons<00:24:20.600> XYZ<00:24:21.440> or<00:24:21.559> we<00:24:21.640> need<00:24:21.760> to<00:24:21.880> have<00:24:21.960> a<00:24:22.039> plan<00:24:22.240> to 00:24:22.390 --> 00:24:22.400 align:start position:0% reasons XYZ or we need to have a plan to 00:24:22.400 --> 00:24:23.269 align:start position:0% reasons XYZ or we need to have a plan to do<00:24:22.520> it<00:24:22.679> and<00:24:22.760> that's<00:24:22.880> something<00:24:23.080> we're<00:24:23.200> going 00:24:23.269 --> 00:24:23.279 align:start position:0% do it and that's something we're going 00:24:23.279 --> 00:24:24.909 align:start position:0% do it and that's something we're going to<00:24:23.360> be<00:24:23.440> looking<00:24:23.720> to<00:24:23.960> in<00:24:24.120> the<00:24:24.240> next<00:24:24.440> couple 00:24:24.909 --> 00:24:24.919 align:start position:0% to be looking to in the next couple 00:24:24.919 --> 00:24:27.870 align:start position:0% to be looking to in the next couple years<00:24:25.919> amazing<00:24:26.720> um<00:24:26.880> and<00:24:27.039> the<00:24:27.320> last<00:24:27.480> one<00:24:27.640> is<00:24:27.799> a 00:24:27.870 --> 00:24:27.880 align:start position:0% years amazing um and the last one is a 00:24:27.880 --> 00:24:28.990 align:start position:0% years amazing um and the last one is a little<00:24:28.000> bit<00:24:28.080> more<00:24:28.200> of<00:24:28.480> comment<00:24:28.679> than<00:24:28.799> a 00:24:28.990 --> 00:24:29.000 align:start position:0% little bit more of comment than a 00:24:29.000 --> 00:24:31.230 align:start position:0% little bit more of comment than a question<00:24:29.320> so<00:24:29.480> I<00:24:29.559> don't<00:24:29.720> know<00:24:29.880> if<00:24:30.080> there's<00:24:30.960> uh<00:24:31.080> a 00:24:31.230 --> 00:24:31.240 align:start position:0% question so I don't know if there's uh a 00:24:31.240 --> 00:24:33.350 align:start position:0% question so I don't know if there's uh a place<00:24:31.399> you<00:24:31.520> can<00:24:31.679> direct<00:24:32.039> people<00:24:32.440> for<00:24:33.159> uh<00:24:33.240> to 00:24:33.350 --> 00:24:33.360 align:start position:0% place you can direct people for uh to 00:24:33.360 --> 00:24:35.110 align:start position:0% place you can direct people for uh to read<00:24:33.520> the<00:24:33.640> data<00:24:33.840> section<00:24:34.120> of<00:24:34.279> other 00:24:35.110 --> 00:24:35.120 align:start position:0% read the data section of other 00:24:35.120 --> 00:24:37.669 align:start position:0% read the data section of other contracts<00:24:36.120> right<00:24:36.399> so<00:24:37.000> the<00:24:37.120> reason<00:24:37.440> why<00:24:37.559> we 00:24:37.669 --> 00:24:37.679 align:start position:0% contracts right so the reason why we 00:24:37.679 --> 00:24:39.070 align:start position:0% contracts right so the reason why we didn't<00:24:37.880> want<00:24:37.960> to<00:24:38.120> directly<00:24:38.480> do<00:24:38.679> that<00:24:38.840> is<00:24:38.960> we 00:24:39.070 --> 00:24:39.080 align:start position:0% didn't want to directly do that is we 00:24:39.080 --> 00:24:40.470 align:start position:0% didn't want to directly do that is we want<00:24:39.159> to<00:24:39.320> give<00:24:39.520> contracts<00:24:40.000> the<00:24:40.120> option<00:24:40.360> of 00:24:40.470 --> 00:24:40.480 align:start position:0% want to give contracts the option of 00:24:40.480 --> 00:24:42.549 align:start position:0% want to give contracts the option of saying<00:24:41.080> no<00:24:41.240> one<00:24:41.399> can<00:24:41.559> read<00:24:41.760> my<00:24:41.960> data<00:24:42.360> if<00:24:42.480> you 00:24:42.549 --> 00:24:42.559 align:start position:0% saying no one can read my data if you 00:24:42.559 --> 00:24:44.110 align:start position:0% saying no one can read my data if you want<00:24:42.679> to<00:24:42.840> allow<00:24:43.080> someone<00:24:43.279> to<00:24:43.360> read<00:24:43.520> your<00:24:43.679> data 00:24:44.110 --> 00:24:44.120 align:start position:0% want to allow someone to read your data 00:24:44.120 --> 00:24:46.350 align:start position:0% want to allow someone to read your data you<00:24:44.360> expose<00:24:44.640> a<00:24:44.799> function<00:24:45.559> that<00:24:45.720> you<00:24:45.919> then<00:24:46.080> copy 00:24:46.350 --> 00:24:46.360 align:start position:0% you expose a function that you then copy 00:24:46.360 --> 00:24:48.470 align:start position:0% you expose a function that you then copy your<00:24:46.520> data<00:24:46.760> and<00:24:46.880> send<00:24:47.080> it<00:24:47.320> back<00:24:48.080> um<00:24:48.240> but<00:24:48.320> we're 00:24:48.470 --> 00:24:48.480 align:start position:0% your data and send it back um but we're 00:24:48.480 --> 00:24:49.830 align:start position:0% your data and send it back um but we're going<00:24:48.559> to<00:24:48.679> figure<00:24:48.880> out<00:24:49.080> over<00:24:49.240> the<00:24:49.360> next<00:24:49.559> couple 00:24:49.830 --> 00:24:49.840 align:start position:0% going to figure out over the next couple 00:24:49.840 --> 00:24:51.789 align:start position:0% going to figure out over the next couple months<00:24:50.440> if<00:24:50.640> that's<00:24:50.880> going<00:24:50.960> to<00:24:51.120> be<00:24:51.399> sufficient 00:24:51.789 --> 00:24:51.799 align:start position:0% months if that's going to be sufficient 00:24:51.799 --> 00:24:53.310 align:start position:0% months if that's going to be sufficient if<00:24:51.919> there's<00:24:52.080> going<00:24:52.159> to<00:24:52.240> cause<00:24:52.600> problems<00:24:53.159> so 00:24:53.310 --> 00:24:53.320 align:start position:0% if there's going to cause problems so 00:24:53.320 --> 00:24:54.830 align:start position:0% if there's going to cause problems so there<00:24:53.440> is<00:24:53.520> a<00:24:53.679> way<00:24:53.840> out<00:24:54.039> the<00:24:54.159> question<00:24:54.440> is<00:24:54.600> is<00:24:54.720> it 00:24:54.830 --> 00:24:54.840 align:start position:0% there is a way out the question is is it 00:24:54.840 --> 00:24:56.350 align:start position:0% there is a way out the question is is it the<00:24:54.960> right<00:24:55.120> designed<00:24:55.520> choice<00:24:56.080> so<00:24:56.240> I'd 00:24:56.350 --> 00:24:56.360 align:start position:0% the right designed choice so I'd 00:24:56.360 --> 00:24:58.470 align:start position:0% the right designed choice so I'd encourage<00:24:56.799> people<00:24:57.039> who<00:24:57.200> care<00:24:57.399> about<00:24:57.679> this<00:24:58.080> to 00:24:58.470 --> 00:24:58.480 align:start position:0% encourage people who care about this to 00:24:58.480 --> 00:25:00.389 align:start position:0% encourage people who care about this to call<00:24:58.640> into<00:24:58.840> our<00:24:58.960> evm<00:24:59.320> implementor<00:24:59.760> calls<00:25:00.080> and 00:25:00.389 --> 00:25:00.399 align:start position:0% call into our evm implementor calls and 00:25:00.399 --> 00:25:01.870 align:start position:0% call into our evm implementor calls and and<00:25:00.520> let<00:25:00.640> us<00:25:00.799> know<00:25:00.960> why<00:25:01.080> you<00:25:01.200> feel<00:25:01.360> it's 00:25:01.870 --> 00:25:01.880 align:start position:0% and let us know why you feel it's 00:25:01.880 --> 00:25:05.559 align:start position:0% and let us know why you feel it's important<00:25:02.880> thank<00:25:03.039> you<00:25:03.200> so<00:25:03.360> much