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:10.350 align:start position:0% [Music] 00:00:10.350 --> 00:00:10.360 align:start position:0% [Music] 00:00:10.360 --> 00:00:12.350 align:start position:0% [Music] uh<00:00:10.559> hello<00:00:10.800> everyone<00:00:11.120> my<00:00:11.240> name<00:00:11.360> is<00:00:11.519> Alex<00:00:11.960> I<00:00:12.080> work 00:00:12.350 --> 00:00:12.360 align:start position:0% uh hello everyone my name is Alex I work 00:00:12.360 --> 00:00:14.470 align:start position:0% uh hello everyone my name is Alex I work on<00:00:12.599> account<00:00:12.880> obstruction<00:00:13.480> and<00:00:13.639> today<00:00:14.000> I<00:00:14.080> will 00:00:14.470 --> 00:00:14.480 align:start position:0% on account obstruction and today I will 00:00:14.480 --> 00:00:16.590 align:start position:0% on account obstruction and today I will follow<00:00:14.839> you<00:00:15.120> stock<00:00:15.320> with<00:00:15.440> a<00:00:15.559> deep<00:00:15.759> dive<00:00:16.119> into 00:00:16.590 --> 00:00:16.600 align:start position:0% follow you stock with a deep dive into 00:00:16.600 --> 00:00:18.550 align:start position:0% follow you stock with a deep dive into the<00:00:16.720> future<00:00:17.039> of<00:00:17.160> native<00:00:17.520> account<00:00:17.840> obstruction 00:00:18.550 --> 00:00:18.560 align:start position:0% the future of native account obstruction 00:00:18.560 --> 00:00:20.830 align:start position:0% the future of native account obstruction and<00:00:18.720> our<00:00:18.920> plans<00:00:19.160> for<00:00:19.320> it<00:00:19.960> so<00:00:20.240> for<00:00:20.439> the<00:00:20.560> purpose 00:00:20.830 --> 00:00:20.840 align:start position:0% and our plans for it so for the purpose 00:00:20.840 --> 00:00:22.390 align:start position:0% and our plans for it so for the purpose of<00:00:20.960> this<00:00:21.080> talk<00:00:21.279> I<00:00:21.400> suggest<00:00:21.680> like<00:00:21.840> we<00:00:21.920> all<00:00:22.080> agree 00:00:22.390 --> 00:00:22.400 align:start position:0% of this talk I suggest like we all agree 00:00:22.400 --> 00:00:24.150 align:start position:0% of this talk I suggest like we all agree that<00:00:22.519> we<00:00:22.720> want<00:00:22.960> native<00:00:23.279> account<00:00:23.560> obstruction 00:00:24.150 --> 00:00:24.160 align:start position:0% that we want native account obstruction 00:00:24.160 --> 00:00:25.750 align:start position:0% that we want native account obstruction the<00:00:24.320> way<00:00:24.560> to<00:00:24.720> for<00:00:24.920> C<00:00:25.119> obstruction<00:00:25.519> is<00:00:25.640> to 00:00:25.750 --> 00:00:25.760 align:start position:0% the way to for C obstruction is to 00:00:25.760 --> 00:00:28.029 align:start position:0% the way to for C obstruction is to enshrine<00:00:26.160> it<00:00:26.279> in<00:00:26.439> layer<00:00:26.720> tools<00:00:27.039> and<00:00:27.199> the<00:00:27.880> uh 00:00:28.029 --> 00:00:28.039 align:start position:0% enshrine it in layer tools and the uh 00:00:28.039 --> 00:00:30.269 align:start position:0% enshrine it in layer tools and the uh main<00:00:28.359> net<00:00:29.039> and<00:00:29.320> we<00:00:29.439> need<00:00:29.560> to<00:00:29.679> answer<00:00:30.039> the 00:00:30.269 --> 00:00:30.279 align:start position:0% main net and we need to answer the 00:00:30.279 --> 00:00:32.830 align:start position:0% main net and we need to answer the following<00:00:30.759> questions<00:00:31.199> before<00:00:31.480> we<00:00:31.800> go<00:00:32.000> into<00:00:32.200> it 00:00:32.830 --> 00:00:32.840 align:start position:0% following questions before we go into it 00:00:32.840 --> 00:00:35.310 align:start position:0% following questions before we go into it uh<00:00:33.160> first<00:00:33.399> we<00:00:33.559> need<00:00:33.680> to<00:00:33.800> know<00:00:34.120> which<00:00:34.399> part<00:00:34.840> of 00:00:35.310 --> 00:00:35.320 align:start position:0% uh first we need to know which part of 00:00:35.320 --> 00:00:37.069 align:start position:0% uh first we need to know which part of native<00:00:35.640> account<00:00:35.879> obstruction<00:00:36.520> is<00:00:36.680> already 00:00:37.069 --> 00:00:37.079 align:start position:0% native account obstruction is already 00:00:37.079 --> 00:00:39.630 align:start position:0% native account obstruction is already happening<00:00:37.399> in<00:00:37.520> the<00:00:37.680> next<00:00:37.960> ethereum<00:00:38.320> hard<00:00:38.640> Fork 00:00:39.630 --> 00:00:39.640 align:start position:0% happening in the next ethereum hard Fork 00:00:39.640 --> 00:00:41.869 align:start position:0% happening in the next ethereum hard Fork uh<00:00:39.920> we<00:00:40.039> need<00:00:40.160> to<00:00:40.320> see<00:00:40.760> why<00:00:41.039> it<00:00:41.239> is<00:00:41.399> not<00:00:41.600> enough 00:00:41.869 --> 00:00:41.879 align:start position:0% uh we need to see why it is not enough 00:00:41.879 --> 00:00:43.190 align:start position:0% uh we need to see why it is not enough and<00:00:42.079> what<00:00:42.200> is<00:00:42.320> still<00:00:42.480> missing<00:00:42.840> for<00:00:43.000> us<00:00:43.079> to 00:00:43.190 --> 00:00:43.200 align:start position:0% and what is still missing for us to 00:00:43.200 --> 00:00:45.670 align:start position:0% and what is still missing for us to achieve<00:00:43.440> the<00:00:43.640> account<00:00:43.920> obstruction<00:00:44.680> endgame 00:00:45.670 --> 00:00:45.680 align:start position:0% achieve the account obstruction endgame 00:00:45.680 --> 00:00:47.510 align:start position:0% achieve the account obstruction endgame uh<00:00:45.960> I<00:00:46.039> want<00:00:46.160> to<00:00:46.280> explain<00:00:46.640> how<00:00:46.800> we<00:00:47.039> plan<00:00:47.320> to 00:00:47.510 --> 00:00:47.520 align:start position:0% uh I want to explain how we plan to 00:00:47.520 --> 00:00:52.150 align:start position:0% uh I want to explain how we plan to achieve<00:00:47.800> it<00:00:48.719> uh<00:00:49.160> and<00:00:49.920> also<00:00:50.199> Explain<00:00:50.600> how<00:00:51.160> other 00:00:52.150 --> 00:00:52.160 align:start position:0% achieve it uh and also Explain how other 00:00:52.160 --> 00:00:54.549 align:start position:0% achieve it uh and also Explain how other companies<00:00:52.719> and<00:00:52.920> teams<00:00:53.239> can<00:00:53.960> participate<00:00:54.440> in 00:00:54.549 --> 00:00:54.559 align:start position:0% companies and teams can participate in 00:00:54.559 --> 00:00:57.029 align:start position:0% companies and teams can participate in this<00:00:54.719> effort<00:00:55.559> and<00:00:56.039> honestly<00:00:56.480> look<00:00:56.680> at<00:00:56.840> the 00:00:57.029 --> 00:00:57.039 align:start position:0% this effort and honestly look at the 00:00:57.039 --> 00:00:58.830 align:start position:0% this effort and honestly look at the possible<00:00:57.359> alternatives<00:00:58.199> to<00:00:58.320> doing<00:00:58.600> what<00:00:58.760> we 00:00:58.830 --> 00:00:58.840 align:start position:0% possible alternatives to doing what we 00:00:58.840 --> 00:01:03.110 align:start position:0% possible alternatives to doing what we are<00:00:59.000> proposing<00:01:00.120> so<00:01:01.000> uh<00:01:01.840> uh<00:01:02.000> and<00:01:02.280> a<00:01:02.440> quick<00:01:02.640> recap 00:01:03.110 --> 00:01:03.120 align:start position:0% are proposing so uh uh and a quick recap 00:01:03.120 --> 00:01:04.109 align:start position:0% are proposing so uh uh and a quick recap of<00:01:03.280> where<00:01:03.399> we<00:01:03.519> stand<00:01:03.719> with<00:01:03.879> account 00:01:04.109 --> 00:01:04.119 align:start position:0% of where we stand with account 00:01:04.119 --> 00:01:05.630 align:start position:0% of where we stand with account obstruction<00:01:04.600> right<00:01:04.720> now<00:01:04.879> if<00:01:05.000> somebody<00:01:05.320> was 00:01:05.630 --> 00:01:05.640 align:start position:0% obstruction right now if somebody was 00:01:05.640 --> 00:01:07.550 align:start position:0% obstruction right now if somebody was not<00:01:05.880> involved<00:01:06.240> into<00:01:06.400> it<00:01:06.799> so<00:01:07.159> the<00:01:07.320> first 00:01:07.550 --> 00:01:07.560 align:start position:0% not involved into it so the first 00:01:07.560 --> 00:01:09.830 align:start position:0% not involved into it so the first account<00:01:07.840> obstruction<00:01:08.240> proposal<00:01:08.720> ERC<00:01:09.080> 4337<00:01:09.720> is 00:01:09.830 --> 00:01:09.840 align:start position:0% account obstruction proposal ERC 4337 is 00:01:09.840 --> 00:01:12.070 align:start position:0% account obstruction proposal ERC 4337 is soled<00:01:10.040> the<00:01:10.119> account<00:01:10.520> obstruction<00:01:11.520> uh<00:01:11.680> without 00:01:12.070 --> 00:01:12.080 align:start position:0% soled the account obstruction uh without 00:01:12.080 --> 00:01:15.469 align:start position:0% soled the account obstruction uh without making<00:01:12.720> consensus<00:01:13.200> changes<00:01:13.680> on<00:01:14.439> eum<00:01:14.880> protocol 00:01:15.469 --> 00:01:15.479 align:start position:0% making consensus changes on eum protocol 00:01:15.479 --> 00:01:19.350 align:start position:0% making consensus changes on eum protocol it<00:01:15.840> uh<00:01:16.320> allowed<00:01:16.680> us<00:01:17.159> with<00:01:17.520> purely<00:01:18.040> out<00:01:18.360> of 00:01:19.350 --> 00:01:19.360 align:start position:0% it uh allowed us with purely out of 00:01:19.360 --> 00:01:22.350 align:start position:0% it uh allowed us with purely out of consensus<00:01:20.079> to<00:01:20.880> uh<00:01:21.119> provide<00:01:21.960> a<00:01:22.119> count 00:01:22.350 --> 00:01:22.360 align:start position:0% consensus to uh provide a count 00:01:22.360 --> 00:01:24.350 align:start position:0% consensus to uh provide a count obstruction<00:01:22.720> solution<00:01:23.119> and<00:01:23.240> it<00:01:23.360> did<00:01:23.560> solve<00:01:24.159> a 00:01:24.350 --> 00:01:24.360 align:start position:0% obstruction solution and it did solve a 00:01:24.360 --> 00:01:27.109 align:start position:0% obstruction solution and it did solve a vast<00:01:24.600> majority<00:01:25.040> of<00:01:25.360> cases<00:01:26.360> and<00:01:26.680> it<00:01:26.840> has<00:01:26.960> been 00:01:27.109 --> 00:01:27.119 align:start position:0% vast majority of cases and it has been 00:01:27.119 --> 00:01:29.109 align:start position:0% vast majority of cases and it has been released<00:01:27.439> more<00:01:27.560> than<00:01:27.680> a<00:01:27.799> year<00:01:27.960> ago<00:01:28.280> the<00:01:28.439> main 00:01:29.109 --> 00:01:29.119 align:start position:0% released more than a year ago the main 00:01:29.119 --> 00:01:31.830 align:start position:0% released more than a year ago the main and<00:01:29.479> uh<00:01:29.640> the<00:01:30.200> has<00:01:30.640> have<00:01:30.759> been<00:01:30.880> launched<00:01:31.520> so 00:01:31.830 --> 00:01:31.840 align:start position:0% and uh the has have been launched so 00:01:31.840 --> 00:01:34.230 align:start position:0% and uh the has have been launched so it's<00:01:31.960> no<00:01:32.119> longer<00:01:32.360> a<00:01:32.479> new<00:01:32.759> project<00:01:33.280> it<00:01:33.880> has<00:01:34.040> been 00:01:34.230 --> 00:01:34.240 align:start position:0% it's no longer a new project it has been 00:01:34.240 --> 00:01:36.469 align:start position:0% it's no longer a new project it has been used<00:01:34.600> for<00:01:35.320> a<00:01:35.439> year<00:01:35.640> by<00:01:35.799> a<00:01:35.880> very<00:01:36.040> serious 00:01:36.469 --> 00:01:36.479 align:start position:0% used for a year by a very serious 00:01:36.479 --> 00:01:39.789 align:start position:0% used for a year by a very serious project<00:01:37.479> uh<00:01:37.600> EAP<00:01:37.960> 772<00:01:38.920> is<00:01:39.000> a<00:01:39.159> very<00:01:39.360> important 00:01:39.789 --> 00:01:39.799 align:start position:0% project uh EAP 772 is a very important 00:01:39.799 --> 00:01:41.789 align:start position:0% project uh EAP 772 is a very important proposal<00:01:40.280> because<00:01:40.560> it's<00:01:40.680> the<00:01:40.840> first<00:01:41.079> time<00:01:41.600> uh 00:01:41.789 --> 00:01:41.799 align:start position:0% proposal because it's the first time uh 00:01:41.799 --> 00:01:43.469 align:start position:0% proposal because it's the first time uh mainnet<00:01:42.320> is<00:01:42.479> getting<00:01:42.960> some<00:01:43.240> account 00:01:43.469 --> 00:01:43.479 align:start position:0% mainnet is getting some account 00:01:43.479 --> 00:01:46.230 align:start position:0% mainnet is getting some account obstruction<00:01:43.880> features<00:01:44.880> uh<00:01:45.040> this<00:01:45.240> EAP<00:01:45.560> allows 00:01:46.230 --> 00:01:46.240 align:start position:0% obstruction features uh this EAP allows 00:01:46.240 --> 00:01:48.069 align:start position:0% obstruction features uh this EAP allows uh<00:01:46.360> as<00:01:46.439> you<00:01:46.560> know<00:01:46.719> EOS<00:01:47.079> to<00:01:47.399> like<00:01:47.520> role<00:01:47.799> play<00:01:47.960> for 00:01:48.069 --> 00:01:48.079 align:start position:0% uh as you know EOS to like role play for 00:01:48.079 --> 00:01:49.950 align:start position:0% uh as you know EOS to like role play for a<00:01:48.200> time<00:01:48.399> as<00:01:48.520> smart<00:01:48.840> accounts<00:01:49.600> and<00:01:49.759> this 00:01:49.950 --> 00:01:49.960 align:start position:0% a time as smart accounts and this 00:01:49.960 --> 00:01:52.230 align:start position:0% a time as smart accounts and this scheduled<00:01:50.360> for<00:01:50.520> the<00:01:50.640> next<00:01:50.799> hard<00:01:51.079> work<00:01:51.960> uh<00:01:52.079> you 00:01:52.230 --> 00:01:52.240 align:start position:0% scheduled for the next hard work uh you 00:01:52.240 --> 00:01:54.830 align:start position:0% scheduled for the next hard work uh you have<00:01:52.360> mentioned<00:01:52.680> RP<00:01:53.159> 7560<00:01:54.159> this<00:01:54.399> is<00:01:54.560> our 00:01:54.830 --> 00:01:54.840 align:start position:0% have mentioned RP 7560 this is our 00:01:54.840 --> 00:01:57.029 align:start position:0% have mentioned RP 7560 this is our proposal<00:01:55.240> to<00:01:55.560> enshrine<00:01:56.240> the<00:01:56.360> design<00:01:56.600> of<00:01:56.719> ERC 00:01:57.029 --> 00:01:57.039 align:start position:0% proposal to enshrine the design of ERC 00:01:57.039 --> 00:02:01.429 align:start position:0% proposal to enshrine the design of ERC 4337<00:01:57.799> as<00:01:58.119> part<00:01:58.759> of<00:01:58.960> Layer<00:01:59.320> Two<00:01:59.560> con<00:01:59.920> ensus<00:02:00.600> uh 00:02:01.429 --> 00:02:01.439 align:start position:0% 4337 as part of Layer Two con ensus uh 00:02:01.439 --> 00:02:03.830 align:start position:0% 4337 as part of Layer Two con ensus uh and<00:02:01.960> it<00:02:02.280> has<00:02:02.399> been<00:02:02.600> implemented<00:02:03.280> and<00:02:03.479> there<00:02:03.680> is 00:02:03.830 --> 00:02:03.840 align:start position:0% and it has been implemented and there is 00:02:03.840 --> 00:02:07.469 align:start position:0% and it has been implemented and there is a<00:02:04.479> devet<00:02:05.039> ready<00:02:05.880> implementation<00:02:06.880> and<00:02:07.200> now<00:02:07.360> we 00:02:07.469 --> 00:02:07.479 align:start position:0% a devet ready implementation and now we 00:02:07.479 --> 00:02:09.830 align:start position:0% a devet ready implementation and now we are<00:02:07.600> also<00:02:08.080> proposing<00:02:08.759> EAP 00:02:09.830 --> 00:02:09.840 align:start position:0% are also proposing EAP 00:02:09.840 --> 00:02:13.949 align:start position:0% are also proposing EAP 7701<00:02:10.840> this<00:02:11.319> is<00:02:11.560> somewhat<00:02:11.920> similar<00:02:12.239> to<00:02:12.959> 7560 00:02:13.949 --> 00:02:13.959 align:start position:0% 7701 this is somewhat similar to 7560 00:02:13.959 --> 00:02:16.229 align:start position:0% 7701 this is somewhat similar to 7560 but<00:02:14.239> it<00:02:14.360> is<00:02:14.640> trying<00:02:14.920> to<00:02:15.040> be<00:02:15.200> less<00:02:15.440> opinionated 00:02:16.229 --> 00:02:16.239 align:start position:0% but it is trying to be less opinionated 00:02:16.239 --> 00:02:21.390 align:start position:0% but it is trying to be less opinionated using<00:02:17.239> uh<00:02:17.599> Le<00:02:17.800> less<00:02:18.040> of<00:02:18.519> uh<00:02:19.319> uh<00:02:20.319> uh<00:02:21.239> the 00:02:21.390 --> 00:02:21.400 align:start position:0% using uh Le less of uh uh uh the 00:02:21.400 --> 00:02:24.670 align:start position:0% using uh Le less of uh uh uh the protocol<00:02:21.840> Parts<00:02:22.640> uh<00:02:23.000> and<00:02:23.480> it<00:02:23.680> targets<00:02:24.519> uh 00:02:24.670 --> 00:02:24.680 align:start position:0% protocol Parts uh and it targets uh 00:02:24.680 --> 00:02:27.550 align:start position:0% protocol Parts uh and it targets uh etherum<00:02:25.080> layer<00:02:25.360> one<00:02:25.959> and<00:02:26.080> it<00:02:26.239> relies<00:02:26.560> on<00:02:26.840> eof 00:02:27.550 --> 00:02:27.560 align:start position:0% etherum layer one and it relies on eof 00:02:27.560 --> 00:02:29.910 align:start position:0% etherum layer one and it relies on eof to<00:02:27.720> do<00:02:27.840> so<00:02:28.080> it's<00:02:28.239> in<00:02:28.440> early<00:02:28.720> draft<00:02:29.040> stage<00:02:29.680> and 00:02:29.910 --> 00:02:29.920 align:start position:0% to do so it's in early draft stage and 00:02:29.920 --> 00:02:31.229 align:start position:0% to do so it's in early draft stage and and<00:02:30.000> we<00:02:30.160> request<00:02:30.480> everybody<00:02:30.800> to<00:02:30.959> provide 00:02:31.229 --> 00:02:31.239 align:start position:0% and we request everybody to provide 00:02:31.239 --> 00:02:34.190 align:start position:0% and we request everybody to provide their<00:02:31.400> feedback<00:02:31.760> on<00:02:32.080> it<00:02:33.080> uh<00:02:33.280> so<00:02:33.680> a<00:02:33.760> little<00:02:33.959> bit 00:02:34.190 --> 00:02:34.200 align:start position:0% their feedback on it uh so a little bit 00:02:34.200 --> 00:02:38.110 align:start position:0% their feedback on it uh so a little bit like<00:02:34.360> more<00:02:34.519> on<00:02:35.040> 7702<00:02:36.040> uh<00:02:36.560> this<00:02:37.080> is<00:02:37.519> how<00:02:37.720> the 00:02:38.110 --> 00:02:38.120 align:start position:0% like more on 7702 uh this is how the 00:02:38.120 --> 00:02:40.990 align:start position:0% like more on 7702 uh this is how the account<00:02:38.840> looks<00:02:39.239> for<00:02:39.920> once<00:02:40.120> you<00:02:40.280> update<00:02:40.680> it 00:02:40.990 --> 00:02:41.000 align:start position:0% account looks for once you update it 00:02:41.000 --> 00:02:42.990 align:start position:0% account looks for once you update it with<00:02:41.879> uh 00:02:42.990 --> 00:02:43.000 align:start position:0% with uh 00:02:43.000 --> 00:02:46.309 align:start position:0% with uh 772<00:02:44.000> so<00:02:44.200> you<00:02:44.560> still<00:02:44.879> have<00:02:45.040> the<00:02:45.280> private<00:02:45.640> key 00:02:46.309 --> 00:02:46.319 align:start position:0% 772 so you still have the private key 00:02:46.319 --> 00:02:48.670 align:start position:0% 772 so you still have the private key but<00:02:46.480> you<00:02:46.720> also<00:02:47.000> have<00:02:47.200> Smart<00:02:47.599> contract<00:02:48.040> code<00:02:48.519> so 00:02:48.670 --> 00:02:48.680 align:start position:0% but you also have Smart contract code so 00:02:48.680 --> 00:02:50.670 align:start position:0% but you also have Smart contract code so it<00:02:48.760> changes<00:02:49.080> the<00:02:49.200> behavior<00:02:49.519> of<00:02:49.640> current<00:02:49.959> EOS 00:02:50.670 --> 00:02:50.680 align:start position:0% it changes the behavior of current EOS 00:02:50.680 --> 00:02:53.390 align:start position:0% it changes the behavior of current EOS allows<00:02:50.959> them<00:02:51.080> to<00:02:51.280> have<00:02:51.480> code<00:02:51.840> as<00:02:52.120> well<00:02:53.120> and 00:02:53.390 --> 00:02:53.400 align:start position:0% allows them to have code as well and 00:02:53.400 --> 00:02:55.270 align:start position:0% allows them to have code as well and this<00:02:53.560> solv<00:02:53.959> fully<00:02:54.239> solves<00:02:54.560> the<00:02:54.760> execution 00:02:55.270 --> 00:02:55.280 align:start position:0% this solv fully solves the execution 00:02:55.280 --> 00:02:57.430 align:start position:0% this solv fully solves the execution part<00:02:55.480> of<00:02:55.680> account<00:02:55.959> obstruction<00:02:56.720> your<00:02:57.080> account 00:02:57.430 --> 00:02:57.440 align:start position:0% part of account obstruction your account 00:02:57.440 --> 00:02:59.350 align:start position:0% part of account obstruction your account can<00:02:57.599> do<00:02:58.000> multiple<00:02:58.440> operations<00:02:58.800> in<00:02:58.959> the<00:02:59.080> same 00:02:59.350 --> 00:02:59.360 align:start position:0% can do multiple operations in the same 00:02:59.360 --> 00:03:02.750 align:start position:0% can do multiple operations in the same time<00:03:00.080> doing<00:03:00.360> T<00:03:00.720> whatever<00:03:01.400> uh<00:03:01.640> it<00:03:01.760> is<00:03:02.319> it<00:03:02.480> does 00:03:02.750 --> 00:03:02.760 align:start position:0% time doing T whatever uh it is it does 00:03:02.760 --> 00:03:05.830 align:start position:0% time doing T whatever uh it is it does not<00:03:03.360> however<00:03:03.599> solve<00:03:03.959> the<00:03:04.200> security<00:03:04.920> part<00:03:05.640> of 00:03:05.830 --> 00:03:05.840 align:start position:0% not however solve the security part of 00:03:05.840 --> 00:03:08.110 align:start position:0% not however solve the security part of account<00:03:06.159> obstruction<00:03:06.879> because<00:03:07.560> you<00:03:07.879> still 00:03:08.110 --> 00:03:08.120 align:start position:0% account obstruction because you still 00:03:08.120 --> 00:03:09.750 align:start position:0% account obstruction because you still have<00:03:08.239> a<00:03:08.400> private<00:03:08.720> key<00:03:08.879> you<00:03:08.959> still<00:03:09.159> have<00:03:09.280> an<00:03:09.400> EA 00:03:09.750 --> 00:03:09.760 align:start position:0% have a private key you still have an EA 00:03:09.760 --> 00:03:10.990 align:start position:0% have a private key you still have an EA you<00:03:09.879> still<00:03:10.040> have<00:03:10.159> 12<00:03:10.400> words<00:03:10.680> that<00:03:10.799> can 00:03:10.990 --> 00:03:11.000 align:start position:0% you still have 12 words that can 00:03:11.000 --> 00:03:13.509 align:start position:0% you still have 12 words that can override<00:03:11.480> your<00:03:11.640> smart<00:03:11.920> contract<00:03:12.280> wallet<00:03:13.239> and 00:03:13.509 --> 00:03:13.519 align:start position:0% override your smart contract wallet and 00:03:13.519 --> 00:03:16.110 align:start position:0% override your smart contract wallet and there<00:03:13.920> also<00:03:14.159> needs<00:03:14.400> to<00:03:14.519> be<00:03:14.760> another<00:03:15.159> EA<00:03:15.920> that 00:03:16.110 --> 00:03:16.120 align:start position:0% there also needs to be another EA that 00:03:16.120 --> 00:03:19.030 align:start position:0% there also needs to be another EA that creates<00:03:16.480> a<00:03:16.720> transaction<00:03:17.720> to<00:03:17.959> use<00:03:18.239> your 00:03:19.030 --> 00:03:19.040 align:start position:0% creates a transaction to use your 00:03:19.040 --> 00:03:21.509 align:start position:0% creates a transaction to use your authorization<00:03:20.040> uh<00:03:20.239> the<00:03:20.400> upside<00:03:20.879> of<00:03:21.080> this<00:03:21.360> is 00:03:21.509 --> 00:03:21.519 align:start position:0% authorization uh the upside of this is 00:03:21.519 --> 00:03:24.990 align:start position:0% authorization uh the upside of this is that<00:03:21.760> it<00:03:21.920> works<00:03:22.360> great<00:03:22.720> with<00:03:22.920> ERC<00:03:23.680> 4337<00:03:24.680> and 00:03:24.990 --> 00:03:25.000 align:start position:0% that it works great with ERC 4337 and 00:03:25.000 --> 00:03:26.789 align:start position:0% that it works great with ERC 4337 and such<00:03:25.200> accounts<00:03:25.519> can<00:03:25.640> be<00:03:25.879> part<00:03:26.200> of<00:03:26.480> account 00:03:26.789 --> 00:03:26.799 align:start position:0% such accounts can be part of account 00:03:26.799 --> 00:03:28.350 align:start position:0% such accounts can be part of account obstruction<00:03:27.239> ecosystem<00:03:27.720> and<00:03:27.879> get<00:03:28.120> gas 00:03:28.350 --> 00:03:28.360 align:start position:0% obstruction ecosystem and get gas 00:03:28.360 --> 00:03:32.350 align:start position:0% obstruction ecosystem and get gas obstruction<00:03:29.000> and<00:03:30.000> many<00:03:30.239> other<00:03:30.680> features<00:03:31.680> so 00:03:32.350 --> 00:03:32.360 align:start position:0% obstruction and many other features so 00:03:32.360 --> 00:03:33.990 align:start position:0% obstruction and many other features so one<00:03:32.599> question<00:03:32.840> you<00:03:32.959> can<00:03:33.080> ask<00:03:33.280> is<00:03:33.439> like<00:03:33.760> great 00:03:33.990 --> 00:03:34.000 align:start position:0% one question you can ask is like great 00:03:34.000 --> 00:03:35.710 align:start position:0% one question you can ask is like great so<00:03:34.319> next<00:03:34.519> we'll<00:03:34.760> just<00:03:34.920> wait<00:03:35.080> for<00:03:35.239> the<00:03:35.400> rest<00:03:35.560> of 00:03:35.710 --> 00:03:35.720 align:start position:0% so next we'll just wait for the rest of 00:03:35.720 --> 00:03:38.070 align:start position:0% so next we'll just wait for the rest of account<00:03:36.120> obstruction<00:03:36.640> to<00:03:36.799> be<00:03:36.959> enshrined<00:03:37.599> in 00:03:38.070 --> 00:03:38.080 align:start position:0% account obstruction to be enshrined in 00:03:38.080 --> 00:03:41.750 align:start position:0% account obstruction to be enshrined in uh<00:03:38.799> uh<00:03:38.959> e<00:03:39.360> main<00:03:39.560> it<00:03:40.080> well<00:03:40.640> if<00:03:40.760> you<00:03:40.879> look<00:03:41.000> at<00:03:41.159> the 00:03:41.750 --> 00:03:41.760 align:start position:0% uh uh e main it well if you look at the 00:03:41.760 --> 00:03:44.110 align:start position:0% uh uh e main it well if you look at the uh<00:03:41.879> specs<00:03:42.239> for<00:03:42.439> the<00:03:42.560> next<00:03:42.799> three<00:03:43.040> hard<00:03:43.319> Forks 00:03:44.110 --> 00:03:44.120 align:start position:0% uh specs for the next three hard Forks 00:03:44.120 --> 00:03:45.830 align:start position:0% uh specs for the next three hard Forks this<00:03:44.280> is<00:03:44.400> the<00:03:44.560> list<00:03:44.799> of<00:03:44.959> eaps<00:03:45.439> that<00:03:45.560> are 00:03:45.830 --> 00:03:45.840 align:start position:0% this is the list of eaps that are 00:03:45.840 --> 00:03:47.990 align:start position:0% this is the list of eaps that are considered<00:03:46.280> or<00:03:46.439> scheduled<00:03:46.840> for<00:03:47.040> inclusion<00:03:47.840> in 00:03:47.990 --> 00:03:48.000 align:start position:0% considered or scheduled for inclusion in 00:03:48.000 --> 00:03:50.390 align:start position:0% considered or scheduled for inclusion in the<00:03:48.200> next<00:03:48.599> uh<00:03:48.680> three<00:03:49.000> hard<00:03:49.280> fors<00:03:49.879> like<00:03:50.200> this<00:03:50.319> is 00:03:50.390 --> 00:03:50.400 align:start position:0% the next uh three hard fors like this is 00:03:50.400 --> 00:03:53.309 align:start position:0% the next uh three hard fors like this is a<00:03:50.560> long<00:03:50.799> list<00:03:51.319> like<00:03:51.920> these<00:03:52.120> changes<00:03:52.560> will<00:03:52.799> take 00:03:53.309 --> 00:03:53.319 align:start position:0% a long list like these changes will take 00:03:53.319 --> 00:03:57.429 align:start position:0% a long list like these changes will take quite<00:03:53.519> a<00:03:53.640> lot<00:03:53.840> of<00:03:54.319> time<00:03:55.319> and<00:03:55.560> so<00:03:56.040> if<00:03:56.159> we<00:03:56.319> were<00:03:57.040> to 00:03:57.429 --> 00:03:57.439 align:start position:0% quite a lot of time and so if we were to 00:03:57.439 --> 00:03:59.429 align:start position:0% quite a lot of time and so if we were to just<00:03:57.799> wait<00:03:58.079> out<00:03:58.400> for<00:03:58.599> to<00:03:58.720> introduce<00:03:59.120> a<00:03:59.239> account 00:03:59.429 --> 00:03:59.439 align:start position:0% just wait out for to introduce a account 00:03:59.439 --> 00:04:01.830 align:start position:0% just wait out for to introduce a account substra<00:03:59.799> C<00:04:00.799> on<00:04:01.000> layer 00:04:01.830 --> 00:04:01.840 align:start position:0% substra C on layer 00:04:01.840 --> 00:04:05.509 align:start position:0% substra C on layer one<00:04:02.840> this<00:04:03.000> could<00:04:03.239> take<00:04:03.799> very<00:04:04.040> long<00:04:04.280> time<00:04:04.840> and 00:04:05.509 --> 00:04:05.519 align:start position:0% one this could take very long time and 00:04:05.519 --> 00:04:08.750 align:start position:0% one this could take very long time and also<00:04:05.959> it<00:04:06.879> it's<00:04:07.040> a<00:04:07.239> high<00:04:07.439> bar<00:04:07.760> to<00:04:07.959> clear<00:04:08.599> in 00:04:08.750 --> 00:04:08.760 align:start position:0% also it it's a high bar to clear in 00:04:08.760 --> 00:04:11.990 align:start position:0% also it it's a high bar to clear in terms<00:04:09.280> of<00:04:09.720> uh<00:04:10.000> production<00:04:10.519> tested<00:04:11.200> uh 00:04:11.990 --> 00:04:12.000 align:start position:0% terms of uh production tested uh 00:04:12.000 --> 00:04:15.309 align:start position:0% terms of uh production tested uh specifications<00:04:13.000> uh<00:04:13.720> fully<00:04:14.120> spec<00:04:14.439> road<00:04:14.720> map 00:04:15.309 --> 00:04:15.319 align:start position:0% specifications uh fully spec road map 00:04:15.319 --> 00:04:18.349 align:start position:0% specifications uh fully spec road map and<00:04:16.000> it<00:04:16.120> requires<00:04:16.479> an<00:04:16.759> unanimous<00:04:17.359> consense 00:04:18.349 --> 00:04:18.359 align:start position:0% and it requires an unanimous consense 00:04:18.359 --> 00:04:21.189 align:start position:0% and it requires an unanimous consense among<00:04:18.840> uh<00:04:19.000> core<00:04:19.239> ethereum<00:04:19.880> developers<00:04:20.880> uh<00:04:21.040> to 00:04:21.189 --> 00:04:21.199 align:start position:0% among uh core ethereum developers uh to 00:04:21.199 --> 00:04:24.230 align:start position:0% among uh core ethereum developers uh to do<00:04:21.359> such<00:04:21.519> a<00:04:21.919> feature<00:04:22.919> uh<00:04:23.120> it<00:04:23.280> doesn't<00:04:23.880> mean 00:04:24.230 --> 00:04:24.240 align:start position:0% do such a feature uh it doesn't mean 00:04:24.240 --> 00:04:26.070 align:start position:0% do such a feature uh it doesn't mean that<00:04:24.440> we<00:04:24.560> will<00:04:24.840> just<00:04:25.280> wait<00:04:25.520> for<00:04:25.720> these<00:04:25.919> things 00:04:26.070 --> 00:04:26.080 align:start position:0% that we will just wait for these things 00:04:26.080 --> 00:04:28.749 align:start position:0% that we will just wait for these things to<00:04:26.280> happen<00:04:26.840> we<00:04:26.960> have<00:04:27.199> a<00:04:27.320> lot<00:04:27.520> of<00:04:27.919> uh<00:04:28.360> activity 00:04:28.749 --> 00:04:28.759 align:start position:0% to happen we have a lot of uh activity 00:04:28.759 --> 00:04:31.070 align:start position:0% to happen we have a lot of uh activity we<00:04:28.840> can<00:04:29.039> do<00:04:29.320> on<00:04:29.720> layer<00:04:29.960> tools<00:04:30.479> who<00:04:30.600> are<00:04:30.800> eager 00:04:31.070 --> 00:04:31.080 align:start position:0% we can do on layer tools who are eager 00:04:31.080 --> 00:04:32.670 align:start position:0% we can do on layer tools who are eager to<00:04:31.240> innovate<00:04:31.639> with<00:04:31.840> account<00:04:32.160> obstruction 00:04:32.670 --> 00:04:32.680 align:start position:0% to innovate with account obstruction 00:04:32.680 --> 00:04:36.189 align:start position:0% to innovate with account obstruction right<00:04:33.240> now<00:04:34.240> uh<00:04:34.600> another<00:04:35.160> like<00:04:35.479> alternative<00:04:36.000> is 00:04:36.189 --> 00:04:36.199 align:start position:0% right now uh another like alternative is 00:04:36.199 --> 00:04:40.550 align:start position:0% right now uh another like alternative is just<00:04:36.360> to<00:04:37.120> keep<00:04:37.320> using<00:04:37.759> ERC<00:04:38.400> 4337<00:04:39.400> like<00:04:39.560> forever 00:04:40.550 --> 00:04:40.560 align:start position:0% just to keep using ERC 4337 like forever 00:04:40.560 --> 00:04:44.430 align:start position:0% just to keep using ERC 4337 like forever so<00:04:41.120> can<00:04:41.320> we<00:04:41.919> keep<00:04:42.160> using<00:04:42.479> it<00:04:42.960> well<00:04:43.360> kind<00:04:43.560> of<00:04:44.080> yes 00:04:44.430 --> 00:04:44.440 align:start position:0% so can we keep using it well kind of yes 00:04:44.440 --> 00:04:48.629 align:start position:0% so can we keep using it well kind of yes it's<00:04:45.160> good<00:04:45.639> enough<00:04:46.639> in<00:04:46.919> many<00:04:47.240> cases<00:04:48.000> but<00:04:48.280> it's 00:04:48.629 --> 00:04:48.639 align:start position:0% it's good enough in many cases but it's 00:04:48.639 --> 00:04:50.790 align:start position:0% it's good enough in many cases but it's very<00:04:48.880> much<00:04:49.160> not<00:04:49.440> perfect<00:04:49.960> like<00:04:50.120> the<00:04:50.479> main 00:04:50.790 --> 00:04:50.800 align:start position:0% very much not perfect like the main 00:04:50.800 --> 00:04:54.230 align:start position:0% very much not perfect like the main downside<00:04:51.240> is<00:04:51.360> it<00:04:51.600> still<00:04:52.000> relies<00:04:52.440> on<00:04:52.960> EAS<00:04:53.960> uh<00:04:54.039> to 00:04:54.230 --> 00:04:54.240 align:start position:0% downside is it still relies on EAS uh to 00:04:54.240 --> 00:04:56.110 align:start position:0% downside is it still relies on EAS uh to act<00:04:54.440> as<00:04:54.560> bundlers<00:04:55.360> so<00:04:55.520> you<00:04:55.639> have<00:04:55.720> an<00:04:55.880> account 00:04:56.110 --> 00:04:56.120 align:start position:0% act as bundlers so you have an account 00:04:56.120 --> 00:04:57.310 align:start position:0% act as bundlers so you have an account abstraction<00:04:56.440> solution<00:04:56.680> but<00:04:56.800> you<00:04:56.919> still<00:04:57.120> need 00:04:57.310 --> 00:04:57.320 align:start position:0% abstraction solution but you still need 00:04:57.320 --> 00:05:00.629 align:start position:0% abstraction solution but you still need EAS<00:04:57.720> for<00:04:57.919> that<00:04:58.800> uh<00:04:59.120> we<00:04:59.280> also<00:04:59.720> create<00:05:00.039> a<00:05:00.199> lot<00:05:00.360> of 00:05:00.629 --> 00:05:00.639 align:start position:0% EAS for that uh we also create a lot of 00:05:00.639 --> 00:05:03.390 align:start position:0% EAS for that uh we also create a lot of complexity<00:05:01.600> by<00:05:01.759> implementing<00:05:02.320> a<00:05:02.440> lot<00:05:02.600> of<00:05:03.120> like 00:05:03.390 --> 00:05:03.400 align:start position:0% complexity by implementing a lot of like 00:05:03.400 --> 00:05:06.110 align:start position:0% complexity by implementing a lot of like parallel<00:05:03.840> technical<00:05:04.240> Stacks<00:05:04.720> parallel<00:05:05.120> mles 00:05:06.110 --> 00:05:06.120 align:start position:0% parallel technical Stacks parallel mles 00:05:06.120 --> 00:05:08.710 align:start position:0% parallel technical Stacks parallel mles uh<00:05:06.560> parall<00:05:06.880> bundlers<00:05:07.560> and<00:05:07.960> modifications<00:05:08.560> to 00:05:08.710 --> 00:05:08.720 align:start position:0% uh parall bundlers and modifications to 00:05:08.720 --> 00:05:12.710 align:start position:0% uh parall bundlers and modifications to the<00:05:09.160> node<00:05:10.360> uh<00:05:11.360> and<00:05:11.680> as<00:05:11.880> layer<00:05:12.160> tws<00:05:12.440> want<00:05:12.600> to 00:05:12.710 --> 00:05:12.720 align:start position:0% the node uh and as layer tws want to 00:05:12.720 --> 00:05:14.150 align:start position:0% the node uh and as layer tws want to innovate<00:05:13.120> they<00:05:13.240> start<00:05:13.479> implementing<00:05:13.960> their 00:05:14.150 --> 00:05:14.160 align:start position:0% innovate they start implementing their 00:05:14.160 --> 00:05:15.950 align:start position:0% innovate they start implementing their own<00:05:14.880> uh<00:05:15.000> Native<00:05:15.320> account<00:05:15.560> obstruction 00:05:15.950 --> 00:05:15.960 align:start position:0% own uh Native account obstruction 00:05:15.960 --> 00:05:18.309 align:start position:0% own uh Native account obstruction Solutions<00:05:16.360> there<00:05:16.479> are<00:05:17.080> chains<00:05:17.400> who<00:05:17.520> did<00:05:17.720> that 00:05:18.309 --> 00:05:18.319 align:start position:0% Solutions there are chains who did that 00:05:18.319 --> 00:05:20.150 align:start position:0% Solutions there are chains who did that and<00:05:18.520> it<00:05:18.639> is<00:05:18.880> it<00:05:19.000> is<00:05:19.080> a<00:05:19.240> problem<00:05:19.520> because<00:05:20.039> then 00:05:20.150 --> 00:05:20.160 align:start position:0% and it is it is a problem because then 00:05:20.160 --> 00:05:23.110 align:start position:0% and it is it is a problem because then it<00:05:20.479> breaks<00:05:20.759> the<00:05:21.280> compatibility<00:05:22.280> and<00:05:22.840> also 00:05:23.110 --> 00:05:23.120 align:start position:0% it breaks the compatibility and also 00:05:23.120 --> 00:05:25.510 align:start position:0% it breaks the compatibility and also there<00:05:23.240> are<00:05:23.400> still<00:05:24.160> uh<00:05:24.280> new<00:05:24.520> EAP<00:05:25.039> that 00:05:25.510 --> 00:05:25.520 align:start position:0% there are still uh new EAP that 00:05:25.520 --> 00:05:28.350 align:start position:0% there are still uh new EAP that introduce<00:05:26.000> new<00:05:26.160> features<00:05:26.639> to<00:05:27.160> ethereum<00:05:28.160> one 00:05:28.350 --> 00:05:28.360 align:start position:0% introduce new features to ethereum one 00:05:28.360 --> 00:05:30.309 align:start position:0% introduce new features to ethereum one big<00:05:28.560> example<00:05:28.880> is<00:05:29.000> inclusion<00:05:29.400> list<00:05:30.080> uh<00:05:30.199> you 00:05:30.309 --> 00:05:30.319 align:start position:0% big example is inclusion list uh you 00:05:30.319 --> 00:05:33.390 align:start position:0% big example is inclusion list uh you have<00:05:30.440> mentioned<00:05:30.919> fossil<00:05:31.919> uh<00:05:32.160> and<00:05:32.400> this<00:05:32.600> eaps 00:05:33.390 --> 00:05:33.400 align:start position:0% have mentioned fossil uh and this eaps 00:05:33.400 --> 00:05:35.629 align:start position:0% have mentioned fossil uh and this eaps like<00:05:34.000> don't<00:05:34.360> benefit<00:05:34.880> account<00:05:35.199> obstruction 00:05:35.629 --> 00:05:35.639 align:start position:0% like don't benefit account obstruction 00:05:35.639 --> 00:05:36.790 align:start position:0% like don't benefit account obstruction users<00:05:35.960> in<00:05:36.080> the 00:05:36.790 --> 00:05:36.800 align:start position:0% users in the 00:05:36.800 --> 00:05:42.670 align:start position:0% users in the account<00:05:38.160> W<00:05:39.280> uh<00:05:40.280> so<00:05:40.960> uh<00:05:41.120> let's<00:05:41.440> zoom<00:05:41.840> into<00:05:42.400> a 00:05:42.670 --> 00:05:42.680 align:start position:0% account W uh so uh let's zoom into a 00:05:42.680 --> 00:05:45.909 align:start position:0% account W uh so uh let's zoom into a flow<00:05:43.199> of<00:05:43.360> a<00:05:43.560> single<00:05:44.120> uh<00:05:44.240> user<00:05:44.639> operation<00:05:45.600> in 00:05:45.909 --> 00:05:45.919 align:start position:0% flow of a single uh user operation in 00:05:45.919 --> 00:05:49.029 align:start position:0% flow of a single uh user operation in ERC<00:05:46.400> 437<00:05:47.160> so<00:05:47.600> what<00:05:47.759> happens<00:05:48.080> is<00:05:48.199> the<00:05:48.360> user 00:05:49.029 --> 00:05:49.039 align:start position:0% ERC 437 so what happens is the user 00:05:49.039 --> 00:05:51.350 align:start position:0% ERC 437 so what happens is the user signs<00:05:49.400> and<00:05:49.600> creates<00:05:49.960> a<00:05:50.080> user<00:05:50.400> operation<00:05:51.240> and 00:05:51.350 --> 00:05:51.360 align:start position:0% signs and creates a user operation and 00:05:51.360 --> 00:05:53.430 align:start position:0% signs and creates a user operation and the<00:05:51.479> user<00:05:51.759> has<00:05:51.919> to<00:05:52.160> provide<00:05:52.479> it<00:05:52.680> to<00:05:52.840> a<00:05:53.000> bundler 00:05:53.430 --> 00:05:53.440 align:start position:0% the user has to provide it to a bundler 00:05:53.440 --> 00:05:55.749 align:start position:0% the user has to provide it to a bundler server<00:05:54.160> the<00:05:54.319> bundler<00:05:54.720> server<00:05:55.000> then<00:05:55.199> collects 00:05:55.749 --> 00:05:55.759 align:start position:0% server the bundler server then collects 00:05:55.759 --> 00:05:59.670 align:start position:0% server the bundler server then collects and<00:05:56.120> other<00:05:56.400> user<00:05:57.000> operations<00:05:58.000> and<00:05:58.759> uh<00:05:59.240> bundles 00:05:59.670 --> 00:05:59.680 align:start position:0% and other user operations and uh bundles 00:05:59.680 --> 00:06:02.870 align:start position:0% and other user operations and uh bundles them<00:05:59.919> together<00:06:00.240> and<00:06:00.560> provides<00:06:01.360> uh<00:06:01.520> it<00:06:01.680> as<00:06:01.800> a 00:06:02.870 --> 00:06:02.880 align:start position:0% them together and provides uh it as a 00:06:02.880 --> 00:06:05.430 align:start position:0% them together and provides uh it as a transaction<00:06:03.880> uh<00:06:04.000> to<00:06:04.199> the<00:06:04.400> blog<00:06:04.639> Builder<00:06:05.319> and 00:06:05.430 --> 00:06:05.440 align:start position:0% transaction uh to the blog Builder and 00:06:05.440 --> 00:06:08.469 align:start position:0% transaction uh to the blog Builder and it<00:06:05.600> has<00:06:05.759> to<00:06:05.880> use<00:06:06.199> this<00:06:06.560> uh<00:06:06.919> conditional<00:06:07.599> API 00:06:08.469 --> 00:06:08.479 align:start position:0% it has to use this uh conditional API 00:06:08.479 --> 00:06:10.749 align:start position:0% it has to use this uh conditional API meaning<00:06:08.840> that<00:06:09.000> it<00:06:09.160> performs<00:06:09.599> the<00:06:09.759> validation 00:06:10.749 --> 00:06:10.759 align:start position:0% meaning that it performs the validation 00:06:10.759 --> 00:06:12.830 align:start position:0% meaning that it performs the validation and<00:06:11.160> he<00:06:11.319> provides<00:06:11.599> a<00:06:11.919> condition<00:06:12.400> for<00:06:12.639> this 00:06:12.830 --> 00:06:12.840 align:start position:0% and he provides a condition for this 00:06:12.840 --> 00:06:15.230 align:start position:0% and he provides a condition for this transaction<00:06:13.520> uh<00:06:13.639> to<00:06:13.759> be<00:06:14.120> valid<00:06:14.759> and<00:06:14.880> then<00:06:15.080> the 00:06:15.230 --> 00:06:15.240 align:start position:0% transaction uh to be valid and then the 00:06:15.240 --> 00:06:18.070 align:start position:0% transaction uh to be valid and then the blog<00:06:15.479> Builder<00:06:15.840> can<00:06:16.080> include<00:06:16.520> this<00:06:16.800> as<00:06:17.280> a<00:06:17.800> as<00:06:17.919> a 00:06:18.070 --> 00:06:18.080 align:start position:0% blog Builder can include this as a as a 00:06:18.080 --> 00:06:21.070 align:start position:0% blog Builder can include this as a as a call<00:06:18.560> uh<00:06:18.840> onchain<00:06:19.840> with<00:06:20.120> RP 00:06:21.070 --> 00:06:21.080 align:start position:0% call uh onchain with RP 00:06:21.080 --> 00:06:23.469 align:start position:0% call uh onchain with RP 7560<00:06:22.080> uh<00:06:22.199> we<00:06:22.319> make<00:06:22.560> all<00:06:22.800> this<00:06:23.080> super 00:06:23.469 --> 00:06:23.479 align:start position:0% 7560 uh we make all this super 00:06:23.479 --> 00:06:25.070 align:start position:0% 7560 uh we make all this super structures<00:06:23.919> that<00:06:24.039> we<00:06:24.199> had<00:06:24.360> with<00:06:24.479> the<00:06:24.639> bundler 00:06:25.070 --> 00:06:25.080 align:start position:0% structures that we had with the bundler 00:06:25.080 --> 00:06:26.909 align:start position:0% structures that we had with the bundler and<00:06:25.400> conditional<00:06:25.680> API<00:06:26.080> and<00:06:26.240> entry<00:06:26.639> point 00:06:26.909 --> 00:06:26.919 align:start position:0% and conditional API and entry point 00:06:26.919 --> 00:06:29.710 align:start position:0% and conditional API and entry point contract<00:06:27.800> uh<00:06:28.039> part<00:06:28.280> of<00:06:28.479> consensus<00:06:29.039> protocol 00:06:29.710 --> 00:06:29.720 align:start position:0% contract uh part of consensus protocol 00:06:29.720 --> 00:06:31.909 align:start position:0% contract uh part of consensus protocol so<00:06:29.919> it<00:06:30.479> very<00:06:30.639> much<00:06:30.840> simplifies<00:06:31.319> and<00:06:31.479> flattens 00:06:31.909 --> 00:06:31.919 align:start position:0% so it very much simplifies and flattens 00:06:31.919 --> 00:06:34.749 align:start position:0% so it very much simplifies and flattens out<00:06:32.160> the<00:06:32.479> complexity<00:06:33.479> and<00:06:33.639> for<00:06:33.800> the<00:06:33.960> user<00:06:34.440> they 00:06:34.749 --> 00:06:34.759 align:start position:0% out the complexity and for the user they 00:06:34.759 --> 00:06:37.070 align:start position:0% out the complexity and for the user they uh<00:06:34.880> sign<00:06:35.599> transaction<00:06:36.240> and<00:06:36.400> they<00:06:36.560> broadcast 00:06:37.070 --> 00:06:37.080 align:start position:0% uh sign transaction and they broadcast 00:06:37.080 --> 00:06:40.070 align:start position:0% uh sign transaction and they broadcast it<00:06:37.240> to<00:06:37.360> the<00:06:37.639> mol<00:06:38.639> and<00:06:39.080> the<00:06:39.360> protocol<00:06:39.800> takes 00:06:40.070 --> 00:06:40.080 align:start position:0% it to the mol and the protocol takes 00:06:40.080 --> 00:06:43.510 align:start position:0% it to the mol and the protocol takes care<00:06:40.440> of<00:06:40.560> the<00:06:40.800> rest<00:06:41.800> uh<00:06:41.919> and<00:06:42.599> the<00:06:42.759> complexity 00:06:43.510 --> 00:06:43.520 align:start position:0% care of the rest uh and the complexity 00:06:43.520 --> 00:06:45.950 align:start position:0% care of the rest uh and the complexity becomes<00:06:43.919> part<00:06:44.240> of<00:06:44.680> the<00:06:44.840> protocol<00:06:45.319> but<00:06:45.720> again 00:06:45.950 --> 00:06:45.960 align:start position:0% becomes part of the protocol but again 00:06:45.960 --> 00:06:47.390 align:start position:0% becomes part of the protocol but again it's<00:06:46.319> uh 00:06:47.390 --> 00:06:47.400 align:start position:0% it's uh 00:06:47.400 --> 00:06:52.110 align:start position:0% it's uh simplified<00:06:48.400> uh<00:06:49.319> so<00:06:50.319> how<00:06:50.479> it<00:06:50.639> works<00:06:51.120> is<00:06:51.360> that 00:06:52.110 --> 00:06:52.120 align:start position:0% simplified uh so how it works is that 00:06:52.120 --> 00:06:53.830 align:start position:0% simplified uh so how it works is that already<00:06:52.479> now<00:06:52.759> like<00:06:52.919> all<00:06:53.120> transactions<00:06:53.680> that 00:06:53.830 --> 00:06:53.840 align:start position:0% already now like all transactions that 00:06:53.840 --> 00:06:56.270 align:start position:0% already now like all transactions that we<00:06:54.240> uh<00:06:54.319> broadcast<00:06:54.880> to<00:06:55.039> meole<00:06:55.599> and<00:06:55.759> include<00:06:56.120> on 00:06:56.270 --> 00:06:56.280 align:start position:0% we uh broadcast to meole and include on 00:06:56.280 --> 00:06:59.029 align:start position:0% we uh broadcast to meole and include on chain<00:06:56.759> they<00:06:56.960> have<00:06:57.280> a<00:06:57.520> validation<00:06:58.080> code<00:06:58.879> this 00:06:59.029 --> 00:06:59.039 align:start position:0% chain they have a validation code this 00:06:59.039 --> 00:07:01.830 align:start position:0% chain they have a validation code this code<00:06:59.199> is<00:06:59.319> not<00:06:59.680> solidity<00:07:00.120> evm<00:07:00.520> code<00:07:01.039> it's<00:07:01.199> a<00:07:01.720> you 00:07:01.830 --> 00:07:01.840 align:start position:0% code is not solidity evm code it's a you 00:07:01.840 --> 00:07:04.629 align:start position:0% code is not solidity evm code it's a you probably<00:07:02.160> go<00:07:02.479> code<00:07:02.840> that<00:07:03.440> uh<00:07:04.039> blog<00:07:04.240> Builder 00:07:04.629 --> 00:07:04.639 align:start position:0% probably go code that uh blog Builder 00:07:04.639 --> 00:07:07.909 align:start position:0% probably go code that uh blog Builder have<00:07:05.479> uh<00:07:05.759> we<00:07:05.960> validate<00:07:06.520> signatures<00:07:07.199> nones 00:07:07.909 --> 00:07:07.919 align:start position:0% have uh we validate signatures nones 00:07:07.919 --> 00:07:11.029 align:start position:0% have uh we validate signatures nones balances<00:07:08.520> G<00:07:08.800> limits<00:07:09.520> uh<00:07:09.639> base<00:07:09.919> fees<00:07:10.720> and<00:07:10.879> these 00:07:11.029 --> 00:07:11.039 align:start position:0% balances G limits uh base fees and these 00:07:11.039 --> 00:07:13.869 align:start position:0% balances G limits uh base fees and these checks<00:07:11.280> are<00:07:11.479> done<00:07:12.199> uh<00:07:12.319> in<00:07:12.599> go<00:07:12.960> as<00:07:13.440> part<00:07:13.599> of 00:07:13.869 --> 00:07:13.879 align:start position:0% checks are done uh in go as part of 00:07:13.879 --> 00:07:15.950 align:start position:0% checks are done uh in go as part of consensus<00:07:14.599> and<00:07:14.720> then<00:07:14.879> the<00:07:15.000> execution<00:07:15.560> is<00:07:15.720> done 00:07:15.950 --> 00:07:15.960 align:start position:0% consensus and then the execution is done 00:07:15.960 --> 00:07:19.670 align:start position:0% consensus and then the execution is done on<00:07:16.120> the<00:07:16.280> evm<00:07:17.280> uh<00:07:17.440> with<00:07:18.080> 7560<00:07:19.080> we<00:07:19.240> split<00:07:19.520> the 00:07:19.670 --> 00:07:19.680 align:start position:0% on the evm uh with 7560 we split the 00:07:19.680 --> 00:07:21.710 align:start position:0% on the evm uh with 7560 we split the transaction<00:07:20.120> into<00:07:20.360> two<00:07:20.560> parts<00:07:21.360> and<00:07:21.560> the 00:07:21.710 --> 00:07:21.720 align:start position:0% transaction into two parts and the 00:07:21.720 --> 00:07:24.950 align:start position:0% transaction into two parts and the validation<00:07:22.280> part<00:07:22.560> is<00:07:22.800> also<00:07:23.120> solidity<00:07:23.840> code<00:07:24.840> uh 00:07:24.950 --> 00:07:24.960 align:start position:0% validation part is also solidity code uh 00:07:24.960 --> 00:07:28.670 align:start position:0% validation part is also solidity code uh that<00:07:25.160> also<00:07:25.440> runs<00:07:25.759> on<00:07:26.319> chain<00:07:27.319> and<00:07:28.120> uh<00:07:28.280> but<00:07:28.479> it's 00:07:28.670 --> 00:07:28.680 align:start position:0% that also runs on chain and uh but it's 00:07:28.680 --> 00:07:30.950 align:start position:0% that also runs on chain and uh but it's it's<00:07:28.840> still<00:07:29.080> a<00:07:29.160> single<00:07:29.840> uh<00:07:30.120> transaction<00:07:30.840> that 00:07:30.950 --> 00:07:30.960 align:start position:0% it's still a single uh transaction that 00:07:30.960 --> 00:07:32.469 align:start position:0% it's still a single uh transaction that is<00:07:31.080> split<00:07:31.360> into<00:07:31.680> validation<00:07:32.080> part<00:07:32.280> and 00:07:32.469 --> 00:07:32.479 align:start position:0% is split into validation part and 00:07:32.479 --> 00:07:34.350 align:start position:0% is split into validation part and execution<00:07:32.919> part<00:07:33.199> and<00:07:33.520> error<00:07:33.800> in<00:07:34.000> validation 00:07:34.350 --> 00:07:34.360 align:start position:0% execution part and error in validation 00:07:34.360 --> 00:07:36.110 align:start position:0% execution part and error in validation part<00:07:34.560> means<00:07:34.720> that<00:07:34.879> transaction<00:07:35.280> is<00:07:35.639> not<00:07:35.840> valid 00:07:36.110 --> 00:07:36.120 align:start position:0% part means that transaction is not valid 00:07:36.120 --> 00:07:37.950 align:start position:0% part means that transaction is not valid it's<00:07:36.240> not<00:07:36.400> included<00:07:36.759> onchain<00:07:37.120> and<00:07:37.280> reverted 00:07:37.950 --> 00:07:37.960 align:start position:0% it's not included onchain and reverted 00:07:37.960 --> 00:07:41.189 align:start position:0% it's not included onchain and reverted it<00:07:38.120> just<00:07:38.319> cannot<00:07:38.720> be<00:07:39.000> included<00:07:40.000> uh<00:07:40.080> in<00:07:40.199> a 00:07:41.189 --> 00:07:41.199 align:start position:0% it just cannot be included uh in a 00:07:41.199 --> 00:07:45.749 align:start position:0% it just cannot be included uh in a block<00:07:42.199> uh<00:07:42.800> so<00:07:43.800> if<00:07:43.960> you're<00:07:44.199> familiar<00:07:44.560> withc<00:07:45.000> 437 00:07:45.749 --> 00:07:45.759 align:start position:0% block uh so if you're familiar withc 437 00:07:45.759 --> 00:07:49.230 align:start position:0% block uh so if you're familiar withc 437 the<00:07:45.919> most<00:07:46.319> complex<00:07:47.319> possibly<00:07:48.039> uh<00:07:48.240> path<00:07:48.560> for 00:07:49.230 --> 00:07:49.240 align:start position:0% the most complex possibly uh path for 00:07:49.240 --> 00:07:51.950 align:start position:0% the most complex possibly uh path for transaction<00:07:49.720> to<00:07:49.879> take<00:07:50.599> is<00:07:50.759> to<00:07:51.159> have<00:07:51.560> gas 00:07:51.950 --> 00:07:51.960 align:start position:0% transaction to take is to have gas 00:07:51.960 --> 00:07:55.629 align:start position:0% transaction to take is to have gas sponsoring<00:07:52.960> and<00:07:53.440> uh<00:07:54.000> to<00:07:54.319> deploy<00:07:54.680> a<00:07:54.840> contract<00:07:55.479> a 00:07:55.629 --> 00:07:55.639 align:start position:0% sponsoring and uh to deploy a contract a 00:07:55.639 --> 00:07:57.749 align:start position:0% sponsoring and uh to deploy a contract a smart<00:07:55.919> contract<00:07:56.720> as<00:07:57.000> part<00:07:57.199> of<00:07:57.319> the<00:07:57.479> first 00:07:57.749 --> 00:07:57.759 align:start position:0% smart contract as part of the first 00:07:57.759 --> 00:08:00.270 align:start position:0% smart contract as part of the first transaction<00:07:58.159> interaction<00:07:58.879> so<00:07:59.120> these<00:07:59.240> are<00:07:59.720> all 00:08:00.270 --> 00:08:00.280 align:start position:0% transaction interaction so these are all 00:08:00.280 --> 00:08:03.230 align:start position:0% transaction interaction so these are all execution<00:08:00.840> pathes<00:08:01.400> in<00:08:01.680> account<00:08:02.240> obstruction 00:08:03.230 --> 00:08:03.240 align:start position:0% execution pathes in account obstruction 00:08:03.240 --> 00:08:05.710 align:start position:0% execution pathes in account obstruction and<00:08:03.680> this<00:08:03.800> is<00:08:03.960> what<00:08:04.120> it<00:08:04.240> looks<00:08:04.479> like<00:08:04.639> in 00:08:05.710 --> 00:08:05.720 align:start position:0% and this is what it looks like in 00:08:05.720 --> 00:08:08.670 align:start position:0% and this is what it looks like in 7560<00:08:06.720> uh<00:08:06.879> meaning<00:08:07.280> that<00:08:07.919> uh<00:08:08.080> for<00:08:08.360> a 00:08:08.670 --> 00:08:08.680 align:start position:0% 7560 uh meaning that uh for a 00:08:08.680 --> 00:08:11.029 align:start position:0% 7560 uh meaning that uh for a transaction<00:08:09.280> type<00:08:09.800> we<00:08:09.960> add<00:08:10.120> a<00:08:10.280> number<00:08:10.479> of 00:08:11.029 --> 00:08:11.039 align:start position:0% transaction type we add a number of 00:08:11.039 --> 00:08:14.189 align:start position:0% transaction type we add a number of fields<00:08:12.039> uh<00:08:12.400> and<00:08:13.000> what<00:08:13.159> what<00:08:13.319> happens<00:08:13.919> during 00:08:14.189 --> 00:08:14.199 align:start position:0% fields uh and what what happens during 00:08:14.199 --> 00:08:17.469 align:start position:0% fields uh and what what happens during this<00:08:14.360> transaction<00:08:14.759> flow<00:08:15.159> is<00:08:16.120> uh<00:08:16.960> First<00:08:17.240> Step 00:08:17.469 --> 00:08:17.479 align:start position:0% this transaction flow is uh First Step 00:08:17.479 --> 00:08:19.670 align:start position:0% this transaction flow is uh First Step user<00:08:17.720> creates<00:08:18.000> a<00:08:18.159> transaction<00:08:18.919> sends<00:08:19.199> it<00:08:19.520> to 00:08:19.670 --> 00:08:19.680 align:start position:0% user creates a transaction sends it to 00:08:19.680 --> 00:08:22.070 align:start position:0% user creates a transaction sends it to the<00:08:19.800> blog<00:08:20.120> Builder<00:08:21.120> as<00:08:21.360> part<00:08:21.520> of<00:08:21.639> a 00:08:22.070 --> 00:08:22.080 align:start position:0% the blog Builder as part of a 00:08:22.080 --> 00:08:24.950 align:start position:0% the blog Builder as part of a transaction<00:08:23.080> uh<00:08:23.599> it's<00:08:24.000> uh<00:08:24.400> smart<00:08:24.639> contract 00:08:24.950 --> 00:08:24.960 align:start position:0% transaction uh it's uh smart contract 00:08:24.960 --> 00:08:28.469 align:start position:0% transaction uh it's uh smart contract gets<00:08:25.560> deployed<00:08:26.560> uh<00:08:26.800> pay<00:08:27.080> Master<00:08:27.560> gets<00:08:28.120> queried 00:08:28.469 --> 00:08:28.479 align:start position:0% gets deployed uh pay Master gets queried 00:08:28.479 --> 00:08:30.510 align:start position:0% gets deployed uh pay Master gets queried if<00:08:28.599> it<00:08:28.800> agrees<00:08:29.120> to<00:08:29.240> pay<00:08:29.759> G<00:08:30.039> for<00:08:30.240> this 00:08:30.510 --> 00:08:30.520 align:start position:0% if it agrees to pay G for this 00:08:30.520 --> 00:08:33.029 align:start position:0% if it agrees to pay G for this transaction<00:08:31.520> then<00:08:31.720> the<00:08:31.919> account<00:08:32.320> is<00:08:32.800> uh 00:08:33.029 --> 00:08:33.039 align:start position:0% transaction then the account is uh 00:08:33.039 --> 00:08:35.070 align:start position:0% transaction then the account is uh quered<00:08:33.440> to<00:08:33.599> see<00:08:33.959> if<00:08:34.320> it<00:08:34.599> accept<00:08:34.959> this 00:08:35.070 --> 00:08:35.080 align:start position:0% quered to see if it accept this 00:08:35.080 --> 00:08:36.790 align:start position:0% quered to see if it accept this transaction<00:08:35.479> is<00:08:35.640> valid<00:08:35.919> check<00:08:36.120> the<00:08:36.279> signature 00:08:36.790 --> 00:08:36.800 align:start position:0% transaction is valid check the signature 00:08:36.800 --> 00:08:38.909 align:start position:0% transaction is valid check the signature and<00:08:36.919> not<00:08:37.560> and<00:08:37.719> everything<00:08:38.640> then<00:08:38.800> the 00:08:38.909 --> 00:08:38.919 align:start position:0% and not and everything then the 00:08:38.919 --> 00:08:40.670 align:start position:0% and not and everything then the transaction<00:08:39.320> gets<00:08:39.560> actually<00:08:40.000> executed<00:08:40.519> and 00:08:40.670 --> 00:08:40.680 align:start position:0% transaction gets actually executed and 00:08:40.680 --> 00:08:43.909 align:start position:0% transaction gets actually executed and reaches<00:08:41.000> the<00:08:41.200> Target<00:08:41.919> contract<00:08:42.919> and<00:08:43.479> uh<00:08:43.680> if 00:08:43.909 --> 00:08:43.919 align:start position:0% reaches the Target contract and uh if 00:08:43.919 --> 00:08:46.790 align:start position:0% reaches the Target contract and uh if pay<00:08:44.120> Master<00:08:44.360> wanted<00:08:44.640> to<00:08:45.120> it<00:08:45.240> gets<00:08:45.600> also<00:08:46.200> notify 00:08:46.790 --> 00:08:46.800 align:start position:0% pay Master wanted to it gets also notify 00:08:46.800 --> 00:08:50.389 align:start position:0% pay Master wanted to it gets also notify that<00:08:47.080> pay<00:08:47.600> transaction<00:08:48.040> execution<00:08:49.000> uh<00:08:49.160> has 00:08:50.389 --> 00:08:50.399 align:start position:0% that pay transaction execution uh has 00:08:50.399 --> 00:08:54.310 align:start position:0% that pay transaction execution uh has finished<00:08:51.399> uh<00:08:52.120> however<00:08:52.880> uh<00:08:53.279> what<00:08:53.839> need<00:08:54.080> to<00:08:54.200> be 00:08:54.310 --> 00:08:54.320 align:start position:0% finished uh however uh what need to be 00:08:54.320 --> 00:08:58.829 align:start position:0% finished uh however uh what need to be said<00:08:54.880> RP<00:08:55.600> 7560<00:08:56.600> is<00:08:56.880> not<00:08:57.279> meant<00:08:57.640> to<00:08:57.839> be<00:08:58.000> included 00:08:58.829 --> 00:08:58.839 align:start position:0% said RP 7560 is not meant to be included 00:08:58.839 --> 00:09:01.870 align:start position:0% said RP 7560 is not meant to be included and<00:08:59.040> layer<00:08:59.440> to<00:08:59.680> in<00:08:59.800> its<00:08:59.959> current<00:09:00.399> form<00:09:01.399> and 00:09:01.870 --> 00:09:01.880 align:start position:0% and layer to in its current form and 00:09:01.880 --> 00:09:04.870 align:start position:0% and layer to in its current form and like<00:09:02.200> the<00:09:02.360> RP<00:09:02.839> process<00:09:03.200> itself<00:09:03.680> was<00:09:03.880> started 00:09:04.870 --> 00:09:04.880 align:start position:0% like the RP process itself was started 00:09:04.880 --> 00:09:06.389 align:start position:0% like the RP process itself was started for 00:09:06.389 --> 00:09:06.399 align:start position:0% for 00:09:06.399 --> 00:09:09.269 align:start position:0% for uh<00:09:07.399> features<00:09:08.000> that<00:09:08.320> are<00:09:08.600> common<00:09:08.920> between 00:09:09.269 --> 00:09:09.279 align:start position:0% uh features that are common between 00:09:09.279 --> 00:09:11.630 align:start position:0% uh features that are common between various<00:09:09.760> layer<00:09:10.079> twos<00:09:10.720> but<00:09:10.920> not<00:09:11.160> necessarily 00:09:11.630 --> 00:09:11.640 align:start position:0% various layer twos but not necessarily 00:09:11.640 --> 00:09:15.190 align:start position:0% various layer twos but not necessarily Target<00:09:12.000> layer<00:09:12.440> one<00:09:13.440> uh<00:09:14.079> the<00:09:14.399> it<00:09:14.640> provides<00:09:14.959> us<00:09:15.079> a 00:09:15.190 --> 00:09:15.200 align:start position:0% Target layer one uh the it provides us a 00:09:15.200 --> 00:09:17.910 align:start position:0% Target layer one uh the it provides us a lot<00:09:15.320> of<00:09:15.800> uh<00:09:16.040> uh<00:09:16.480> flexibility<00:09:17.480> uh<00:09:17.600> because<00:09:17.800> we 00:09:17.910 --> 00:09:17.920 align:start position:0% lot of uh uh flexibility uh because we 00:09:17.920 --> 00:09:20.430 align:start position:0% lot of uh uh flexibility uh because we don't<00:09:18.120> need<00:09:18.760> unanimous<00:09:19.399> agreement<00:09:19.880> of<00:09:20.160> all 00:09:20.430 --> 00:09:20.440 align:start position:0% don't need unanimous agreement of all 00:09:20.440 --> 00:09:22.829 align:start position:0% don't need unanimous agreement of all core<00:09:20.880> developers<00:09:21.880> uh<00:09:22.000> it's<00:09:22.160> an<00:09:22.360> opt-in 00:09:22.829 --> 00:09:22.839 align:start position:0% core developers uh it's an opt-in 00:09:22.839 --> 00:09:25.870 align:start position:0% core developers uh it's an opt-in process<00:09:23.160> where<00:09:23.839> rollups<00:09:24.399> can<00:09:24.839> decide<00:09:25.519> to<00:09:25.680> pick 00:09:25.870 --> 00:09:25.880 align:start position:0% process where rollups can decide to pick 00:09:25.880 --> 00:09:28.069 align:start position:0% process where rollups can decide to pick up<00:09:26.000> features<00:09:26.360> and<00:09:26.519> implement<00:09:26.839> it<00:09:26.959> on<00:09:27.120> the<00:09:27.920> uh 00:09:28.069 --> 00:09:28.079 align:start position:0% up features and implement it on the uh 00:09:28.079 --> 00:09:31.470 align:start position:0% up features and implement it on the uh networks<00:09:29.079> and<00:09:29.680> uh<00:09:30.000> uh<00:09:30.320> it's<00:09:30.680> very<00:09:30.920> feasible 00:09:31.470 --> 00:09:31.480 align:start position:0% networks and uh uh it's very feasible 00:09:31.480 --> 00:09:34.389 align:start position:0% networks and uh uh it's very feasible and<00:09:31.760> like<00:09:32.200> logical<00:09:32.640> for<00:09:32.959> some<00:09:33.200> RPS<00:09:33.720> who<00:09:33.920> get 00:09:34.389 --> 00:09:34.399 align:start position:0% and like logical for some RPS who get 00:09:34.399 --> 00:09:40.069 align:start position:0% and like logical for some RPS who get adopted<00:09:34.880> to<00:09:35.399> evolve<00:09:36.279> into<00:09:36.880> eaps<00:09:37.880> so<00:09:38.640> uh<00:09:39.640> what 00:09:40.069 --> 00:09:40.079 align:start position:0% adopted to evolve into eaps so uh what 00:09:40.079 --> 00:09:44.829 align:start position:0% adopted to evolve into eaps so uh what prevents<00:09:41.360> 7560<00:09:42.360> approach<00:09:43.040> to<00:09:43.800> being<00:09:44.399> part<00:09:44.640> of 00:09:44.829 --> 00:09:44.839 align:start position:0% prevents 7560 approach to being part of 00:09:44.839 --> 00:09:48.230 align:start position:0% prevents 7560 approach to being part of the<00:09:45.360> main<00:09:45.560> net<00:09:45.839> EAP<00:09:46.839> well<00:09:47.440> a<00:09:47.560> huge<00:09:47.760> part<00:09:47.920> of<00:09:48.040> it 00:09:48.230 --> 00:09:48.240 align:start position:0% the main net EAP well a huge part of it 00:09:48.240 --> 00:09:52.110 align:start position:0% the main net EAP well a huge part of it it<00:09:49.000> uh<00:09:49.640> defines<00:09:50.399> validation<00:09:51.399> as<00:09:51.600> solidity 00:09:52.110 --> 00:09:52.120 align:start position:0% it uh defines validation as solidity 00:09:52.120 --> 00:09:54.150 align:start position:0% it uh defines validation as solidity methods<00:09:52.560> like<00:09:52.760> we<00:09:53.000> Define<00:09:53.440> solidity<00:09:53.880> method 00:09:54.150 --> 00:09:54.160 align:start position:0% methods like we Define solidity method 00:09:54.160 --> 00:09:56.310 align:start position:0% methods like we Define solidity method that<00:09:54.360> say<00:09:54.680> and<00:09:54.800> we<00:09:54.920> say<00:09:55.120> that<00:09:55.440> this<00:09:55.720> method<00:09:56.160> has 00:09:56.310 --> 00:09:56.320 align:start position:0% that say and we say that this method has 00:09:56.320 --> 00:09:58.069 align:start position:0% that say and we say that this method has to<00:09:56.839> return<00:09:57.040> correctly<00:09:57.440> then<00:09:57.560> the<00:09:57.720> transaction 00:09:58.069 --> 00:09:58.079 align:start position:0% to return correctly then the transaction 00:09:58.079 --> 00:10:00.710 align:start position:0% to return correctly then the transaction is<00:09:58.240> valid<00:09:59.120> it<00:09:59.399> this<00:09:59.519> a<00:09:59.600> little<00:09:59.920> problematic 00:10:00.710 --> 00:10:00.720 align:start position:0% is valid it this a little problematic 00:10:00.720 --> 00:10:03.389 align:start position:0% is valid it this a little problematic because<00:10:01.040> evm<00:10:01.600> is<00:10:01.880> supposed<00:10:02.480> to<00:10:02.640> be<00:10:02.959> language 00:10:03.389 --> 00:10:03.399 align:start position:0% because evm is supposed to be language 00:10:03.399 --> 00:10:06.110 align:start position:0% because evm is supposed to be language agnostic<00:10:04.360> and<00:10:04.600> methods<00:10:04.959> are<00:10:05.160> just<00:10:05.560> part<00:10:05.760> of 00:10:06.110 --> 00:10:06.120 align:start position:0% agnostic and methods are just part of 00:10:06.120 --> 00:10:08.310 align:start position:0% agnostic and methods are just part of solidity<00:10:06.600> programming<00:10:06.959> language<00:10:07.880> it's<00:10:08.120> not 00:10:08.310 --> 00:10:08.320 align:start position:0% solidity programming language it's not 00:10:08.320 --> 00:10:10.310 align:start position:0% solidity programming language it's not such<00:10:08.480> a<00:10:08.600> big<00:10:08.720> deal<00:10:08.880> for<00:10:09.040> layer<00:10:09.279> tws<00:10:09.680> because 00:10:10.310 --> 00:10:10.320 align:start position:0% such a big deal for layer tws because 00:10:10.320 --> 00:10:12.389 align:start position:0% such a big deal for layer tws because almost<00:10:10.600> all<00:10:10.760> of<00:10:10.920> them<00:10:11.200> already<00:10:11.839> have<00:10:12.160> some 00:10:12.389 --> 00:10:12.399 align:start position:0% almost all of them already have some 00:10:12.399 --> 00:10:15.110 align:start position:0% almost all of them already have some kind<00:10:12.560> of<00:10:13.000> pre-compiled<00:10:14.000> that<00:10:14.160> are<00:10:14.760> defined 00:10:15.110 --> 00:10:15.120 align:start position:0% kind of pre-compiled that are defined 00:10:15.120 --> 00:10:18.350 align:start position:0% kind of pre-compiled that are defined fully<00:10:15.480> in<00:10:15.600> solidity<00:10:16.240> and<00:10:16.560> they<00:10:16.800> already<00:10:17.120> do<00:10:17.360> it 00:10:18.350 --> 00:10:18.360 align:start position:0% fully in solidity and they already do it 00:10:18.360 --> 00:10:22.110 align:start position:0% fully in solidity and they already do it uh<00:10:18.560> another<00:10:19.000> thing<00:10:19.360> is<00:10:19.640> that<00:10:20.079> eof<00:10:20.959> ethereum<00:10:21.920> uh 00:10:22.110 --> 00:10:22.120 align:start position:0% uh another thing is that eof ethereum uh 00:10:22.120 --> 00:10:24.230 align:start position:0% uh another thing is that eof ethereum uh evm<00:10:22.480> object<00:10:22.720> format<00:10:23.360> introduces<00:10:24.040> the 00:10:24.230 --> 00:10:24.240 align:start position:0% evm object format introduces the 00:10:24.240 --> 00:10:27.389 align:start position:0% evm object format introduces the deployment<00:10:24.760> time<00:10:25.120> code<00:10:25.720> validation<00:10:26.720> and 00:10:27.389 --> 00:10:27.399 align:start position:0% deployment time code validation and 00:10:27.399 --> 00:10:28.829 align:start position:0% deployment time code validation and account<00:10:27.640> obstruction<00:10:28.160> could<00:10:28.480> greatly 00:10:28.829 --> 00:10:28.839 align:start position:0% account obstruction could greatly 00:10:28.839 --> 00:10:31.590 align:start position:0% account obstruction could greatly benefit<00:10:29.360> from<00:10:29.519> code<00:10:30.000> validation<00:10:31.000> however 00:10:31.590 --> 00:10:31.600 align:start position:0% benefit from code validation however 00:10:31.600 --> 00:10:35.030 align:start position:0% benefit from code validation however without<00:10:32.600> uh<00:10:32.760> EF<00:10:33.640> definitions<00:10:34.640> we<00:10:34.760> would<00:10:34.920> not 00:10:35.030 --> 00:10:35.040 align:start position:0% without uh EF definitions we would not 00:10:35.040 --> 00:10:37.350 align:start position:0% without uh EF definitions we would not be<00:10:35.160> able<00:10:35.399> to<00:10:35.519> do<00:10:35.680> it<00:10:36.040> uh<00:10:36.160> with<00:10:36.440> the<00:10:36.839> um<00:10:37.000> method 00:10:37.350 --> 00:10:37.360 align:start position:0% be able to do it uh with the um method 00:10:37.360 --> 00:10:39.710 align:start position:0% be able to do it uh with the um method selectors<00:10:38.360> and<00:10:38.920> it<00:10:39.079> it<00:10:39.200> can<00:10:39.279> be<00:10:39.399> a<00:10:39.519> problem 00:10:39.710 --> 00:10:39.720 align:start position:0% selectors and it it can be a problem 00:10:39.720 --> 00:10:42.389 align:start position:0% selectors and it it can be a problem that<00:10:39.920> your<00:10:40.399> validation<00:10:40.959> code<00:10:41.519> is<00:10:41.880> a<00:10:42.079> part<00:10:42.279> of 00:10:42.389 --> 00:10:42.399 align:start position:0% that your validation code is a part of 00:10:42.399 --> 00:10:43.710 align:start position:0% that your validation code is a part of your<00:10:42.560> contract<00:10:42.880> that<00:10:43.040> can<00:10:43.160> be<00:10:43.279> called<00:10:43.560> by 00:10:43.710 --> 00:10:43.720 align:start position:0% your contract that can be called by 00:10:43.720 --> 00:10:45.870 align:start position:0% your contract that can be called by other<00:10:43.959> contracts<00:10:44.760> in<00:10:45.079> some<00:10:45.360> scenarios<00:10:45.760> that 00:10:45.870 --> 00:10:45.880 align:start position:0% other contracts in some scenarios that 00:10:45.880 --> 00:10:47.710 align:start position:0% other contracts in some scenarios that can<00:10:46.040> lead<00:10:46.240> to 00:10:47.710 --> 00:10:47.720 align:start position:0% can lead to 00:10:47.720 --> 00:10:51.790 align:start position:0% can lead to vulnerabilities<00:10:48.720> so<00:10:48.920> a<00:10:49.079> reminder<00:10:49.639> in<00:10:50.200> UF<00:10:51.200> uh 00:10:51.790 --> 00:10:51.800 align:start position:0% vulnerabilities so a reminder in UF uh 00:10:51.800 --> 00:10:55.269 align:start position:0% vulnerabilities so a reminder in UF uh the<00:10:52.079> contract<00:10:52.720> is<00:10:53.639> being<00:10:53.920> split<00:10:54.399> into<00:10:54.839> parts 00:10:55.269 --> 00:10:55.279 align:start position:0% the contract is being split into parts 00:10:55.279 --> 00:10:58.430 align:start position:0% the contract is being split into parts so<00:10:55.560> Legacy<00:10:56.560> uh<00:10:56.839> contract<00:10:57.279> they<00:10:57.440> have<00:10:57.800> the<00:10:58.000> blob 00:10:58.430 --> 00:10:58.440 align:start position:0% so Legacy uh contract they have the blob 00:10:58.440 --> 00:11:01.110 align:start position:0% so Legacy uh contract they have the blob that<00:10:58.680> includes<00:10:59.040> all<00:10:59.399> the<00:10:59.600> code<00:10:59.880> and<00:11:00.160> data<00:11:00.680> of 00:11:01.110 --> 00:11:01.120 align:start position:0% that includes all the code and data of 00:11:01.120 --> 00:11:04.710 align:start position:0% that includes all the code and data of uh<00:11:01.680> your<00:11:02.000> contract<00:11:02.680> with<00:11:02.880> eof<00:11:03.480> the<00:11:04.320> contracts 00:11:04.710 --> 00:11:04.720 align:start position:0% uh your contract with eof the contracts 00:11:04.720 --> 00:11:06.990 align:start position:0% uh your contract with eof the contracts are<00:11:04.880> split<00:11:05.519> into<00:11:05.880> the<00:11:06.120> header<00:11:06.560> the<00:11:06.760> code 00:11:06.990 --> 00:11:07.000 align:start position:0% are split into the header the code 00:11:07.000 --> 00:11:09.509 align:start position:0% are split into the header the code section<00:11:07.440> and<00:11:07.720> data<00:11:08.040> section<00:11:09.040> what<00:11:09.200> we<00:11:09.360> are 00:11:09.509 --> 00:11:09.519 align:start position:0% section and data section what we are 00:11:09.519 --> 00:11:12.670 align:start position:0% section and data section what we are suggesting<00:11:10.000> with<00:11:10.200> the<00:11:10.360> EAP<00:11:10.839> 7701<00:11:11.839> is<00:11:12.040> to<00:11:12.440> also 00:11:12.670 --> 00:11:12.680 align:start position:0% suggesting with the EAP 7701 is to also 00:11:12.680 --> 00:11:16.509 align:start position:0% suggesting with the EAP 7701 is to also split<00:11:13.040> the<00:11:13.160> code<00:11:13.440> section<00:11:14.240> into<00:11:15.240> uh<00:11:16.240> into 00:11:16.509 --> 00:11:16.519 align:start position:0% split the code section into uh into 00:11:16.519 --> 00:11:18.670 align:start position:0% split the code section into uh into parts<00:11:16.760> that<00:11:16.959> have<00:11:17.440> roles<00:11:17.800> assigned<00:11:18.120> to<00:11:18.279> them 00:11:18.670 --> 00:11:18.680 align:start position:0% parts that have roles assigned to them 00:11:18.680 --> 00:11:21.629 align:start position:0% parts that have roles assigned to them so<00:11:18.920> the<00:11:19.160> contract<00:11:19.680> would<00:11:20.040> have<00:11:20.760> an<00:11:21.079> EF 00:11:21.629 --> 00:11:21.639 align:start position:0% so the contract would have an EF 00:11:21.639 --> 00:11:24.310 align:start position:0% so the contract would have an EF validation<00:11:22.160> code<00:11:22.600> execution<00:11:23.200> code<00:11:23.760> any<00:11:24.000> other 00:11:24.310 --> 00:11:24.320 align:start position:0% validation code execution code any other 00:11:24.320 --> 00:11:29.470 align:start position:0% validation code execution code any other code<00:11:25.320> and<00:11:25.959> uh<00:11:26.399> uh<00:11:27.000> we<00:11:27.160> can<00:11:27.519> verify<00:11:28.000> the<00:11:28.200> code<00:11:28.800> of 00:11:29.470 --> 00:11:29.480 align:start position:0% code and uh uh we can verify the code of 00:11:29.480 --> 00:11:32.870 align:start position:0% code and uh uh we can verify the code of the<00:11:29.760> validation<00:11:30.440> section<00:11:31.440> uh<00:11:31.680> before<00:11:32.600> uh 00:11:32.870 --> 00:11:32.880 align:start position:0% the validation section uh before uh 00:11:32.880 --> 00:11:37.590 align:start position:0% the validation section uh before uh deploying<00:11:33.320> such<00:11:33.519> contracts<00:11:34.480> and<00:11:35.480> U<00:11:36.480> we<00:11:36.959> like 00:11:37.590 --> 00:11:37.600 align:start position:0% deploying such contracts and U we like 00:11:37.600 --> 00:11:39.430 align:start position:0% deploying such contracts and U we like uh<00:11:38.120> this<00:11:38.320> code<00:11:38.519> doesn't<00:11:38.800> have<00:11:38.920> to<00:11:39.040> be 00:11:39.430 --> 00:11:39.440 align:start position:0% uh this code doesn't have to be 00:11:39.440 --> 00:11:42.269 align:start position:0% uh this code doesn't have to be observable<00:11:40.440> on<00:11:40.720> chain<00:11:41.079> from<00:11:41.279> within<00:11:41.600> EF<00:11:42.120> but 00:11:42.269 --> 00:11:42.279 align:start position:0% observable on chain from within EF but 00:11:42.279 --> 00:11:45.069 align:start position:0% observable on chain from within EF but it<00:11:42.399> is<00:11:42.639> still<00:11:43.000> executed<00:11:43.720> as<00:11:43.959> part<00:11:44.639> of<00:11:44.959> uh 00:11:45.069 --> 00:11:45.079 align:start position:0% it is still executed as part of uh 00:11:45.079 --> 00:11:46.230 align:start position:0% it is still executed as part of uh transaction 00:11:46.230 --> 00:11:46.240 align:start position:0% transaction 00:11:46.240 --> 00:11:48.750 align:start position:0% transaction validation<00:11:47.240> uh<00:11:47.519> so<00:11:47.760> if<00:11:47.839> we<00:11:48.000> look<00:11:48.200> again<00:11:48.399> on<00:11:48.600> all 00:11:48.750 --> 00:11:48.760 align:start position:0% validation uh so if we look again on all 00:11:48.760 --> 00:11:50.550 align:start position:0% validation uh so if we look again on all the<00:11:48.839> flow<00:11:49.160> the<00:11:49.279> flow<00:11:49.680> remains<00:11:50.000> exactly<00:11:50.399> the 00:11:50.550 --> 00:11:50.560 align:start position:0% the flow the flow remains exactly the 00:11:50.560 --> 00:11:54.110 align:start position:0% the flow the flow remains exactly the same<00:11:51.399> just<00:11:51.639> instead<00:11:52.120> of<00:11:52.639> uh<00:11:52.800> calling<00:11:53.320> specific 00:11:54.110 --> 00:11:54.120 align:start position:0% same just instead of uh calling specific 00:11:54.120 --> 00:11:58.230 align:start position:0% same just instead of uh calling specific functions<00:11:55.120> uh<00:11:55.519> the<00:11:55.800> evm<00:11:56.360> executes<00:11:57.240> a<00:11:57.600> certain 00:11:58.230 --> 00:11:58.240 align:start position:0% functions uh the evm executes a certain 00:11:58.240 --> 00:12:01.030 align:start position:0% functions uh the evm executes a certain uh<00:11:58.360> predefined<00:11:58.880> section<00:11:59.680> of<00:11:59.920> your<00:12:00.160> eof 00:12:01.030 --> 00:12:01.040 align:start position:0% uh predefined section of your eof 00:12:01.040 --> 00:12:04.670 align:start position:0% uh predefined section of your eof contracts<00:12:02.040> and<00:12:02.760> uh<00:12:03.399> this<00:12:03.639> allows<00:12:03.959> us<00:12:04.079> to<00:12:04.440> like 00:12:04.670 --> 00:12:04.680 align:start position:0% contracts and uh this allows us to like 00:12:04.680 --> 00:12:06.389 align:start position:0% contracts and uh this allows us to like get<00:12:04.839> away<00:12:05.040> from<00:12:05.240> this<00:12:05.720> magic<00:12:06.120> method 00:12:06.389 --> 00:12:06.399 align:start position:0% get away from this magic method 00:12:06.399 --> 00:12:11.629 align:start position:0% get away from this magic method selectors<00:12:07.320> into<00:12:07.760> a<00:12:08.120> more<00:12:08.680> U<00:12:08.880> minut<00:12:09.639> uh<00:12:10.480> level 00:12:11.629 --> 00:12:11.639 align:start position:0% selectors into a more U minut uh level 00:12:11.639 --> 00:12:14.629 align:start position:0% selectors into a more U minut uh level solution<00:12:12.639> so<00:12:13.199> now<00:12:13.760> uh<00:12:13.959> it's<00:12:14.120> time<00:12:14.279> to<00:12:14.440> talk 00:12:14.629 --> 00:12:14.639 align:start position:0% solution so now uh it's time to talk 00:12:14.639 --> 00:12:16.430 align:start position:0% solution so now uh it's time to talk about<00:12:15.000> challenges<00:12:15.440> of<00:12:15.600> account<00:12:15.880> obstruction 00:12:16.430 --> 00:12:16.440 align:start position:0% about challenges of account obstruction 00:12:16.440 --> 00:12:17.790 align:start position:0% about challenges of account obstruction like<00:12:16.760> people<00:12:17.000> have<00:12:17.120> been<00:12:17.279> talking<00:12:17.519> about<00:12:17.680> it 00:12:17.790 --> 00:12:17.800 align:start position:0% like people have been talking about it 00:12:17.800 --> 00:12:20.790 align:start position:0% like people have been talking about it for<00:12:18.040> 10<00:12:18.279> years<00:12:18.600> it's<00:12:18.839> still<00:12:19.160> not<00:12:19.440> on<00:12:19.800> mainnet 00:12:20.790 --> 00:12:20.800 align:start position:0% for 10 years it's still not on mainnet 00:12:20.800 --> 00:12:22.389 align:start position:0% for 10 years it's still not on mainnet uh<00:12:20.959> this<00:12:21.040> is<00:12:21.199> because<00:12:21.399> it's<00:12:21.600> actually<00:12:21.959> hard<00:12:22.279> if 00:12:22.389 --> 00:12:22.399 align:start position:0% uh this is because it's actually hard if 00:12:22.399 --> 00:12:24.509 align:start position:0% uh this is because it's actually hard if you<00:12:22.600> see<00:12:22.839> somebody<00:12:23.279> talking<00:12:23.639> about 00:12:24.509 --> 00:12:24.519 align:start position:0% you see somebody talking about 00:12:24.519 --> 00:12:26.509 align:start position:0% you see somebody talking about validation<00:12:25.079> scope<00:12:25.440> on<00:12:25.839> account<00:12:26.079> substraction 00:12:26.509 --> 00:12:26.519 align:start position:0% validation scope on account substraction 00:12:26.519 --> 00:12:28.949 align:start position:0% validation scope on account substraction you<00:12:26.680> immediately<00:12:27.120> think<00:12:27.320> about<00:12:27.600> this<00:12:27.959> picture 00:12:28.949 --> 00:12:28.959 align:start position:0% you immediately think about this picture 00:12:28.959 --> 00:12:32.509 align:start position:0% you immediately think about this picture uh<00:12:29.440> and<00:12:30.120> the<00:12:30.240> main<00:12:30.519> problems<00:12:30.920> for<00:12:31.160> that<00:12:31.720> what 00:12:32.509 --> 00:12:32.519 align:start position:0% uh and the main problems for that what 00:12:32.519 --> 00:12:34.189 align:start position:0% uh and the main problems for that what account<00:12:32.800> obstruction<00:12:33.160> creates<00:12:33.480> is<00:12:33.600> the<00:12:33.760> cross 00:12:34.189 --> 00:12:34.199 align:start position:0% account obstruction creates is the cross 00:12:34.199 --> 00:12:36.750 align:start position:0% account obstruction creates is the cross dependencies<00:12:35.199> between<00:12:35.519> transaction<00:12:36.199> and 00:12:36.750 --> 00:12:36.760 align:start position:0% dependencies between transaction and 00:12:36.760 --> 00:12:40.750 align:start position:0% dependencies between transaction and validations<00:12:37.760> and<00:12:38.519> the<00:12:38.839> the<00:12:39.079> complexity 00:12:40.750 --> 00:12:40.760 align:start position:0% validations and the the complexity 00:12:40.760 --> 00:12:44.150 align:start position:0% validations and the the complexity it<00:12:41.760> you<00:12:41.920> you<00:12:42.040> get<00:12:42.480> in<00:12:43.079> building<00:12:43.560> blocks 00:12:44.150 --> 00:12:44.160 align:start position:0% it you you get in building blocks 00:12:44.160 --> 00:12:46.189 align:start position:0% it you you get in building blocks efficiently<00:12:45.160> and<00:12:45.360> maintaining<00:12:46.000> a 00:12:46.189 --> 00:12:46.199 align:start position:0% efficiently and maintaining a 00:12:46.199 --> 00:12:48.430 align:start position:0% efficiently and maintaining a decentralized<00:12:46.839> peer-to-peer<00:12:47.240> M<00:12:47.639> Pool 00:12:48.430 --> 00:12:48.440 align:start position:0% decentralized peer-to-peer M Pool 00:12:48.440 --> 00:12:51.629 align:start position:0% decentralized peer-to-peer M Pool efficiently<00:12:49.440> uh<00:12:49.600> so<00:12:50.160> let<00:12:50.279> me<00:12:50.480> try<00:12:50.720> to<00:12:51.360> uh 00:12:51.629 --> 00:12:51.639 align:start position:0% efficiently uh so let me try to uh 00:12:51.639 --> 00:12:54.949 align:start position:0% efficiently uh so let me try to uh explain<00:12:52.000> these<00:12:52.720> problems<00:12:53.720> uh<00:12:54.040> so<00:12:54.360> the<00:12:54.680> cross 00:12:54.949 --> 00:12:54.959 align:start position:0% explain these problems uh so the cross 00:12:54.959 --> 00:12:56.750 align:start position:0% explain these problems uh so the cross transactional<00:12:55.519> dependencies<00:12:56.279> look<00:12:56.560> like 00:12:56.750 --> 00:12:56.760 align:start position:0% transactional dependencies look like 00:12:56.760 --> 00:12:59.389 align:start position:0% transactional dependencies look like that<00:12:57.399> uh<00:12:57.480> you<00:12:57.639> have<00:12:57.839> transaction<00:12:58.320> four<00:12:58.959> if 00:12:59.389 --> 00:12:59.399 align:start position:0% that uh you have transaction four if 00:12:59.399 --> 00:13:01.990 align:start position:0% that uh you have transaction four if modifies<00:12:59.880> the<00:13:00.079> state<00:13:01.079> and<00:13:01.480> it<00:13:01.600> makes<00:13:01.800> the 00:13:01.990 --> 00:13:02.000 align:start position:0% modifies the state and it makes the 00:13:02.000 --> 00:13:04.550 align:start position:0% modifies the state and it makes the transaction<00:13:02.519> five<00:13:02.959> invalid<00:13:03.480> so<00:13:03.920> when<00:13:04.120> you 00:13:04.550 --> 00:13:04.560 align:start position:0% transaction five invalid so when you 00:13:04.560 --> 00:13:05.990 align:start position:0% transaction five invalid so when you receive<00:13:04.920> the<00:13:05.079> transaction<00:13:05.519> five 00:13:05.990 --> 00:13:06.000 align:start position:0% receive the transaction five 00:13:06.000 --> 00:13:08.990 align:start position:0% receive the transaction five individually<00:13:07.000> it<00:13:07.199> seemed<00:13:07.519> valid<00:13:07.800> to<00:13:08.000> you 00:13:08.990 --> 00:13:09.000 align:start position:0% individually it seemed valid to you 00:13:09.000 --> 00:13:14.509 align:start position:0% individually it seemed valid to you because<00:13:09.760> X<00:13:10.279> was<00:13:11.000> a<00:13:11.320> was<00:13:11.760> uh<00:13:12.240> uh<00:13:13.040> equal<00:13:13.320> to<00:13:13.760> zero 00:13:14.509 --> 00:13:14.519 align:start position:0% because X was a was uh uh equal to zero 00:13:14.519 --> 00:13:16.990 align:start position:0% because X was a was uh uh equal to zero but<00:13:14.800> now<00:13:15.600> you<00:13:15.839> started<00:13:16.240> building<00:13:16.519> a<00:13:16.680> block<00:13:16.880> you 00:13:16.990 --> 00:13:17.000 align:start position:0% but now you started building a block you 00:13:17.000 --> 00:13:20.230 align:start position:0% but now you started building a block you include<00:13:17.320> transaction<00:13:17.720> four<00:13:18.120> first<00:13:18.959> and<00:13:19.399> now<00:13:19.920> a 00:13:20.230 --> 00:13:20.240 align:start position:0% include transaction four first and now a 00:13:20.240 --> 00:13:22.430 align:start position:0% include transaction four first and now a equals<00:13:20.600> 1<00:13:20.880> and<00:13:21.040> it's<00:13:21.320> not<00:13:21.519> a<00:13:21.680> valid 00:13:22.430 --> 00:13:22.440 align:start position:0% equals 1 and it's not a valid 00:13:22.440 --> 00:13:25.829 align:start position:0% equals 1 and it's not a valid transaction<00:13:23.440> uh<00:13:24.079> and<00:13:24.279> in<00:13:24.440> order<00:13:24.760> to<00:13:25.560> work 00:13:25.829 --> 00:13:25.839 align:start position:0% transaction uh and in order to work 00:13:25.839 --> 00:13:28.389 align:start position:0% transaction uh and in order to work around<00:13:26.160> this<00:13:26.360> issue<00:13:26.800> in<00:13:27.040> in<00:13:27.199> general<00:13:28.040> we<00:13:28.240> we 00:13:28.389 --> 00:13:28.399 align:start position:0% around this issue in in general we we 00:13:28.399 --> 00:13:31.269 align:start position:0% around this issue in in general we we just<00:13:28.639> have<00:13:28.839> to<00:13:29.120> to<00:13:29.399> split<00:13:29.760> the<00:13:30.360> uh<00:13:30.680> transaction 00:13:31.269 --> 00:13:31.279 align:start position:0% just have to to split the uh transaction 00:13:31.279 --> 00:13:34.430 align:start position:0% just have to to split the uh transaction into<00:13:31.560> two<00:13:31.760> parts<00:13:32.760> and<00:13:33.120> have<00:13:33.279> the<00:13:33.480> validations 00:13:34.430 --> 00:13:34.440 align:start position:0% into two parts and have the validations 00:13:34.440 --> 00:13:37.750 align:start position:0% into two parts and have the validations run<00:13:35.160> separately<00:13:35.680> from<00:13:36.079> executions<00:13:37.079> in<00:13:37.240> their 00:13:37.750 --> 00:13:37.760 align:start position:0% run separately from executions in their 00:13:37.760 --> 00:13:41.949 align:start position:0% run separately from executions in their separate<00:13:38.399> place<00:13:38.880> in<00:13:39.720> in<00:13:39.839> the<00:13:40.040> book<00:13:41.040> so<00:13:41.680> these 00:13:41.949 --> 00:13:41.959 align:start position:0% separate place in in the book so these 00:13:41.959 --> 00:13:44.069 align:start position:0% separate place in in the book so these are<00:13:42.240> still<00:13:42.639> three<00:13:43.079> account<00:13:43.360> abstraction 00:13:44.069 --> 00:13:44.079 align:start position:0% are still three account abstraction 00:13:44.079 --> 00:13:46.590 align:start position:0% are still three account abstraction transactions<00:13:45.079> but<00:13:45.240> their<00:13:45.440> validation<00:13:46.040> parts 00:13:46.590 --> 00:13:46.600 align:start position:0% transactions but their validation parts 00:13:46.600 --> 00:13:48.910 align:start position:0% transactions but their validation parts are<00:13:47.160> separated<00:13:47.720> from<00:13:47.880> them<00:13:48.079> and<00:13:48.199> they<00:13:48.360> run 00:13:48.910 --> 00:13:48.920 align:start position:0% are separated from them and they run 00:13:48.920 --> 00:13:52.269 align:start position:0% are separated from them and they run before<00:13:49.920> any<00:13:50.199> execution<00:13:50.680> code<00:13:50.959> starts 00:13:52.269 --> 00:13:52.279 align:start position:0% before any execution code starts 00:13:52.279 --> 00:13:55.110 align:start position:0% before any execution code starts running<00:13:53.279> now<00:13:53.639> you<00:13:53.800> may<00:13:54.000> ask<00:13:54.240> but<00:13:54.560> what<00:13:54.680> if 00:13:55.110 --> 00:13:55.120 align:start position:0% running now you may ask but what if 00:13:55.120 --> 00:13:57.629 align:start position:0% running now you may ask but what if validations<00:13:56.120> invalidate<00:13:56.759> each<00:13:56.920> other<00:13:57.480> what 00:13:57.629 --> 00:13:57.639 align:start position:0% validations invalidate each other what 00:13:57.639 --> 00:14:00.389 align:start position:0% validations invalidate each other what if<00:13:57.800> the<00:13:58.000> validation<00:13:58.519> code<00:13:59.320> changes<00:13:59.920> the<00:14:00.079> state 00:14:00.389 --> 00:14:00.399 align:start position:0% if the validation code changes the state 00:14:00.399 --> 00:14:04.269 align:start position:0% if the validation code changes the state that<00:14:00.639> another<00:14:01.040> validation<00:14:02.199> uses<00:14:03.199> and<00:14:03.959> in 00:14:04.269 --> 00:14:04.279 align:start position:0% that another validation uses and in 00:14:04.279 --> 00:14:06.230 align:start position:0% that another validation uses and in general<00:14:04.759> it<00:14:04.959> would<00:14:05.160> be<00:14:05.399> possible<00:14:06.000> and<00:14:06.120> in 00:14:06.230 --> 00:14:06.240 align:start position:0% general it would be possible and in 00:14:06.240 --> 00:14:08.350 align:start position:0% general it would be possible and in order<00:14:06.519> to<00:14:06.680> prevent<00:14:07.000> that<00:14:07.480> we<00:14:07.639> need<00:14:07.800> to<00:14:07.959> send 00:14:08.350 --> 00:14:08.360 align:start position:0% order to prevent that we need to send 00:14:08.360 --> 00:14:10.629 align:start position:0% order to prevent that we need to send box<00:14:08.720> the<00:14:08.880> validation<00:14:09.440> code<00:14:10.000> to<00:14:10.240> prevent<00:14:10.519> it 00:14:10.629 --> 00:14:10.639 align:start position:0% box the validation code to prevent it 00:14:10.639 --> 00:14:12.230 align:start position:0% box the validation code to prevent it from<00:14:10.839> doing<00:14:11.160> certain<00:14:11.480> things<00:14:11.720> that<00:14:11.880> it<00:14:12.000> should 00:14:12.230 --> 00:14:12.240 align:start position:0% from doing certain things that it should 00:14:12.240 --> 00:14:14.829 align:start position:0% from doing certain things that it should not<00:14:12.399> be<00:14:12.560> allowed<00:14:12.880> to<00:14:13.040> do<00:14:13.920> so<00:14:14.279> what<00:14:14.399> are<00:14:14.600> those 00:14:14.829 --> 00:14:14.839 align:start position:0% not be allowed to do so what are those 00:14:14.839 --> 00:14:18.870 align:start position:0% not be allowed to do so what are those things<00:14:15.720> uh<00:14:15.880> it's<00:14:16.360> accessing<00:14:17.240> other<00:14:17.759> people's 00:14:18.870 --> 00:14:18.880 align:start position:0% things uh it's accessing other people's 00:14:18.880 --> 00:14:22.670 align:start position:0% things uh it's accessing other people's storage<00:14:19.880> and<00:14:20.639> accessing<00:14:21.639> environment<00:14:22.399> of 00:14:22.670 --> 00:14:22.680 align:start position:0% storage and accessing environment of 00:14:22.680 --> 00:14:25.150 align:start position:0% storage and accessing environment of codes<00:14:23.279> so<00:14:23.560> environment<00:14:24.000> op<00:14:24.199> codes<00:14:24.399> are<00:14:24.720> block 00:14:25.150 --> 00:14:25.160 align:start position:0% codes so environment op codes are block 00:14:25.160 --> 00:14:28.030 align:start position:0% codes so environment op codes are block number<00:14:25.800> time<00:14:26.079> stamp<00:14:26.680> base<00:14:27.000> fee<00:14:27.639> everything 00:14:28.030 --> 00:14:28.040 align:start position:0% number time stamp base fee everything 00:14:28.040 --> 00:14:31.430 align:start position:0% number time stamp base fee everything that<00:14:28.320> may<00:14:28.519> change<00:14:29.360> from<00:14:29.680> validation<00:14:30.480> and<00:14:30.920> uh 00:14:31.430 --> 00:14:31.440 align:start position:0% that may change from validation and uh 00:14:31.440 --> 00:14:35.310 align:start position:0% that may change from validation and uh execution<00:14:32.120> or<00:14:32.560> between<00:14:33.279> uh<00:14:33.639> phases<00:14:34.639> and<00:14:35.000> other 00:14:35.310 --> 00:14:35.320 align:start position:0% execution or between uh phases and other 00:14:35.320 --> 00:14:37.670 align:start position:0% execution or between uh phases and other people's<00:14:35.720> code<00:14:36.079> is<00:14:36.720> a<00:14:36.880> code<00:14:37.199> in<00:14:37.360> other 00:14:37.670 --> 00:14:37.680 align:start position:0% people's code is a code in other 00:14:37.680 --> 00:14:41.749 align:start position:0% people's code is a code in other contracts<00:14:38.440> unless<00:14:39.160> it<00:14:39.360> is<00:14:39.920> in<00:14:40.079> a<00:14:40.240> mapping<00:14:41.240> uh 00:14:41.749 --> 00:14:41.759 align:start position:0% contracts unless it is in a mapping uh 00:14:41.759 --> 00:14:44.870 align:start position:0% contracts unless it is in a mapping uh mapped<00:14:42.160> to<00:14:42.399> your<00:14:42.839> address<00:14:43.839> and<00:14:44.079> on<00:14:44.279> layer<00:14:44.560> twos 00:14:44.870 --> 00:14:44.880 align:start position:0% mapped to your address and on layer twos 00:14:44.880 --> 00:14:47.310 align:start position:0% mapped to your address and on layer twos it's<00:14:45.199> also<00:14:45.600> any<00:14:45.880> stateful<00:14:46.360> pre-compiled<00:14:47.079> so 00:14:47.310 --> 00:14:47.320 align:start position:0% it's also any stateful pre-compiled so 00:14:47.320 --> 00:14:51.110 align:start position:0% it's also any stateful pre-compiled so this<00:14:48.160> uh<00:14:48.480> doing<00:14:48.800> this<00:14:48.959> is<00:14:49.519> illegal<00:14:50.519> all<00:14:50.800> other 00:14:51.110 --> 00:14:51.120 align:start position:0% this uh doing this is illegal all other 00:14:51.120 --> 00:14:54.670 align:start position:0% this uh doing this is illegal all other things<00:14:51.440> are<00:14:52.000> allowed<00:14:52.720> uh<00:14:53.600> in<00:14:53.800> validation<00:14:54.560> and 00:14:54.670 --> 00:14:54.680 align:start position:0% things are allowed uh in validation and 00:14:54.680 --> 00:14:56.550 align:start position:0% things are allowed uh in validation and it<00:14:54.800> allows<00:14:55.079> us<00:14:55.199> to<00:14:55.320> do<00:14:55.800> many<00:14:56.079> great<00:14:56.279> things<00:14:56.480> you 00:14:56.550 --> 00:14:56.560 align:start position:0% it allows us to do many great things you 00:14:56.560 --> 00:14:58.710 align:start position:0% it allows us to do many great things you can<00:14:56.720> use<00:14:57.000> tokens<00:14:57.399> you<00:14:57.519> can<00:14:57.639> transfer<00:14:58.079> tokens 00:14:58.710 --> 00:14:58.720 align:start position:0% can use tokens you can transfer tokens 00:14:58.720 --> 00:15:01.389 align:start position:0% can use tokens you can transfer tokens you<00:14:58.839> can<00:14:59.079> can<00:14:59.680> uh<00:14:59.839> do<00:15:00.079> all<00:15:00.199> of<00:15:00.399> that<00:15:00.920> uh<00:15:01.040> in 00:15:01.389 --> 00:15:01.399 align:start position:0% you can can uh do all of that uh in 00:15:01.399 --> 00:15:02.949 align:start position:0% you can can uh do all of that uh in validation 00:15:02.949 --> 00:15:02.959 align:start position:0% validation 00:15:02.959 --> 00:15:06.189 align:start position:0% validation functions<00:15:03.959> uh<00:15:04.399> like<00:15:04.839> there<00:15:04.959> are<00:15:05.360> other<00:15:05.800> small 00:15:06.189 --> 00:15:06.199 align:start position:0% functions uh like there are other small 00:15:06.199 --> 00:15:09.189 align:start position:0% functions uh like there are other small complexities<00:15:07.199> uh<00:15:07.480> like<00:15:08.199> one<00:15:08.440> example<00:15:08.880> is<00:15:09.120> you 00:15:09.189 --> 00:15:09.199 align:start position:0% complexities uh like one example is you 00:15:09.199 --> 00:15:12.590 align:start position:0% complexities uh like one example is you don't<00:15:09.399> need<00:15:09.519> to<00:15:10.199> invalidate<00:15:11.199> a<00:15:11.600> transaction 00:15:12.590 --> 00:15:12.600 align:start position:0% don't need to invalidate a transaction 00:15:12.600 --> 00:15:14.710 align:start position:0% don't need to invalidate a transaction to<00:15:12.800> make<00:15:12.920> it<00:15:13.120> hard<00:15:13.440> to<00:15:13.680> for<00:15:13.839> a<00:15:13.920> block<00:15:14.160> Builder 00:15:14.710 --> 00:15:14.720 align:start position:0% to make it hard to for a block Builder 00:15:14.720 --> 00:15:16.230 align:start position:0% to make it hard to for a block Builder to<00:15:15.000> build<00:15:15.360> a<00:15:15.480> block<00:15:15.759> with<00:15:15.880> a<00:15:16.000> account 00:15:16.230 --> 00:15:16.240 align:start position:0% to build a block with a account 00:15:16.240 --> 00:15:19.430 align:start position:0% to build a block with a account obstruction<00:15:17.040> like<00:15:17.560> one<00:15:17.800> good<00:15:18.000> example<00:15:18.519> is<00:15:19.279> uh 00:15:19.430 --> 00:15:19.440 align:start position:0% obstruction like one good example is uh 00:15:19.440 --> 00:15:21.670 align:start position:0% obstruction like one good example is uh unused<00:15:19.959> gas<00:15:20.240> and<00:15:20.480> using<00:15:20.920> unused<00:15:21.320> gas<00:15:21.519> as<00:15:21.600> a 00:15:21.670 --> 00:15:21.680 align:start position:0% unused gas and using unused gas as a 00:15:21.680 --> 00:15:23.509 align:start position:0% unused gas and using unused gas as a vector<00:15:22.160> for<00:15:22.320> example<00:15:22.720> you're<00:15:23.079> building<00:15:23.360> a 00:15:23.509 --> 00:15:23.519 align:start position:0% vector for example you're building a 00:15:23.519 --> 00:15:25.470 align:start position:0% vector for example you're building a block<00:15:24.120> you<00:15:24.279> include<00:15:24.680> five<00:15:24.880> transaction<00:15:25.360> you 00:15:25.470 --> 00:15:25.480 align:start position:0% block you include five transaction you 00:15:25.480 --> 00:15:27.110 align:start position:0% block you include five transaction you see<00:15:25.680> that<00:15:25.839> you<00:15:26.000> still<00:15:26.240> have<00:15:26.600> a<00:15:26.800> lot<00:15:26.920> of 00:15:27.110 --> 00:15:27.120 align:start position:0% see that you still have a lot of 00:15:27.120 --> 00:15:30.030 align:start position:0% see that you still have a lot of available<00:15:27.600> space<00:15:28.519> because<00:15:29.079> action<00:15:29.279> for 00:15:30.030 --> 00:15:30.040 align:start position:0% available space because action for 00:15:30.040 --> 00:15:31.710 align:start position:0% available space because action for requested<00:15:30.600> 10<00:15:30.800> million<00:15:31.160> gas<00:15:31.319> limit<00:15:31.560> but 00:15:31.710 --> 00:15:31.720 align:start position:0% requested 10 million gas limit but 00:15:31.720 --> 00:15:34.069 align:start position:0% requested 10 million gas limit but didn't<00:15:32.000> use<00:15:32.199> it<00:15:32.720> so<00:15:32.959> you<00:15:33.160> start<00:15:33.720> adding 00:15:34.069 --> 00:15:34.079 align:start position:0% didn't use it so you start adding 00:15:34.079 --> 00:15:36.030 align:start position:0% didn't use it so you start adding another<00:15:34.399> transaction<00:15:34.800> to<00:15:34.920> your<00:15:35.079> block<00:15:35.880> and 00:15:36.030 --> 00:15:36.040 align:start position:0% another transaction to your block and 00:15:36.040 --> 00:15:38.790 align:start position:0% another transaction to your block and what<00:15:36.199> happens<00:15:36.560> is<00:15:37.399> transaction<00:15:37.839> four<00:15:38.240> saw<00:15:38.560> a 00:15:38.790 --> 00:15:38.800 align:start position:0% what happens is transaction four saw a 00:15:38.800 --> 00:15:41.550 align:start position:0% what happens is transaction four saw a change<00:15:39.199> in<00:15:39.360> the<00:15:39.720> state<00:15:40.720> and<00:15:40.880> started<00:15:41.279> using 00:15:41.550 --> 00:15:41.560 align:start position:0% change in the state and started using 00:15:41.560 --> 00:15:44.590 align:start position:0% change in the state and started using more<00:15:41.880> gas<00:15:42.319> and<00:15:42.519> now<00:15:43.079> you<00:15:43.279> are<00:15:43.720> like<00:15:44.279> you<00:15:44.440> have 00:15:44.590 --> 00:15:44.600 align:start position:0% more gas and now you are like you have 00:15:44.600 --> 00:15:46.670 align:start position:0% more gas and now you are like you have it<00:15:45.240> recursive<00:15:45.720> like<00:15:45.800> chicken<00:15:46.160> neck<00:15:46.399> problem 00:15:46.670 --> 00:15:46.680 align:start position:0% it recursive like chicken neck problem 00:15:46.680 --> 00:15:49.230 align:start position:0% it recursive like chicken neck problem because<00:15:47.079> now<00:15:47.600> the<00:15:47.800> transaction<00:15:48.600> six<00:15:48.959> doesn't 00:15:49.230 --> 00:15:49.240 align:start position:0% because now the transaction six doesn't 00:15:49.240 --> 00:15:50.710 align:start position:0% because now the transaction six doesn't fit<00:15:49.480> your<00:15:49.639> block<00:15:49.880> and<00:15:49.959> you<00:15:50.079> need<00:15:50.199> to<00:15:50.360> exclude 00:15:50.710 --> 00:15:50.720 align:start position:0% fit your block and you need to exclude 00:15:50.720 --> 00:15:54.350 align:start position:0% fit your block and you need to exclude it<00:15:51.000> and<00:15:51.120> you<00:15:51.240> can<00:15:51.440> get<00:15:51.720> it<00:15:52.440> to<00:15:53.440> um<00:15:53.880> to<00:15:54.040> square 00:15:54.350 --> 00:15:54.360 align:start position:0% it and you can get it to um to square 00:15:54.360 --> 00:15:57.230 align:start position:0% it and you can get it to um to square one<00:15:55.000> like<00:15:55.240> we<00:15:55.480> do<00:15:55.720> solve<00:15:56.000> it<00:15:56.160> by<00:15:56.399> introducing 00:15:57.230 --> 00:15:57.240 align:start position:0% one like we do solve it by introducing 00:15:57.240 --> 00:15:59.509 align:start position:0% one like we do solve it by introducing gas<00:15:57.560> charge<00:15:58.120> on<00:15:58.279> a<00:15:58.480> used<00:15:58.720> gas 00:15:59.509 --> 00:15:59.519 align:start position:0% gas charge on a used gas 00:15:59.519 --> 00:16:01.470 align:start position:0% gas charge on a used gas but<00:15:59.959> I'm<00:16:00.120> just<00:16:00.319> saying<00:16:00.519> using<00:16:00.759> it<00:16:00.920> to<00:16:01.040> showcase 00:16:01.470 --> 00:16:01.480 align:start position:0% but I'm just saying using it to showcase 00:16:01.480 --> 00:16:03.949 align:start position:0% but I'm just saying using it to showcase the<00:16:01.680> kind<00:16:01.839> of<00:16:02.079> problems<00:16:02.480> we<00:16:02.600> need<00:16:02.759> to<00:16:02.920> solve<00:16:03.839> uh 00:16:03.949 --> 00:16:03.959 align:start position:0% the kind of problems we need to solve uh 00:16:03.959 --> 00:16:06.389 align:start position:0% the kind of problems we need to solve uh when<00:16:04.240> implementing<00:16:04.839> account<00:16:05.240> obstruction 00:16:06.389 --> 00:16:06.399 align:start position:0% when implementing account obstruction 00:16:06.399 --> 00:16:08.949 align:start position:0% when implementing account obstruction natively<00:16:07.399> uh<00:16:07.920> and<00:16:08.199> another<00:16:08.519> thing<00:16:08.800> is 00:16:08.949 --> 00:16:08.959 align:start position:0% natively uh and another thing is 00:16:08.959 --> 00:16:13.069 align:start position:0% natively uh and another thing is maintaining<00:16:09.639> an<00:16:10.040> efficient<00:16:11.000> uh<00:16:11.319> mle<00:16:12.319> uh<00:16:12.440> to<00:16:12.839> to 00:16:13.069 --> 00:16:13.079 align:start position:0% maintaining an efficient uh mle uh to to 00:16:13.079 --> 00:16:14.670 align:start position:0% maintaining an efficient uh mle uh to to receive<00:16:13.440> a<00:16:13.600> huge<00:16:13.839> number<00:16:14.079> of<00:16:14.199> transactions 00:16:14.670 --> 00:16:14.680 align:start position:0% receive a huge number of transactions 00:16:14.680 --> 00:16:16.990 align:start position:0% receive a huge number of transactions simultaneously<00:16:15.560> and<00:16:15.800> validate<00:16:16.240> them<00:16:16.880> you 00:16:16.990 --> 00:16:17.000 align:start position:0% simultaneously and validate them you 00:16:17.000 --> 00:16:19.389 align:start position:0% simultaneously and validate them you need<00:16:17.279> to<00:16:17.720> to<00:16:17.920> parallelize<00:16:18.519> their<00:16:18.720> validation 00:16:19.389 --> 00:16:19.399 align:start position:0% need to to parallelize their validation 00:16:19.399 --> 00:16:21.389 align:start position:0% need to to parallelize their validation so<00:16:19.600> assuming<00:16:20.040> like<00:16:20.279> here's<00:16:20.480> a<00:16:20.560> block<00:16:20.759> Builder 00:16:21.389 --> 00:16:21.399 align:start position:0% so assuming like here's a block Builder 00:16:21.399 --> 00:16:24.030 align:start position:0% so assuming like here's a block Builder it<00:16:21.600> has<00:16:22.040> six<00:16:22.519> uh<00:16:22.639> CPU<00:16:23.079> course<00:16:23.639> and<00:16:23.759> it's 00:16:24.030 --> 00:16:24.040 align:start position:0% it has six uh CPU course and it's 00:16:24.040 --> 00:16:26.030 align:start position:0% it has six uh CPU course and it's performing<00:16:24.560> validation<00:16:25.000> of<00:16:25.199> six<00:16:25.920> uh 00:16:26.030 --> 00:16:26.040 align:start position:0% performing validation of six uh 00:16:26.040 --> 00:16:28.629 align:start position:0% performing validation of six uh transactions<00:16:26.600> in<00:16:26.800> in<00:16:27.000> parallel<00:16:27.959> so<00:16:28.199> it<00:16:28.360> runs 00:16:28.629 --> 00:16:28.639 align:start position:0% transactions in in parallel so it runs 00:16:28.639 --> 00:16:31.990 align:start position:0% transactions in in parallel so it runs them<00:16:29.160> uh<00:16:29.639> uh<00:16:30.600> individually<00:16:31.480> meaning<00:16:31.839> they 00:16:31.990 --> 00:16:32.000 align:start position:0% them uh uh individually meaning they 00:16:32.000 --> 00:16:35.030 align:start position:0% them uh uh individually meaning they don't<00:16:32.360> access<00:16:32.720> each<00:16:32.880> other<00:16:33.399> state<00:16:34.399> and<00:16:34.759> if<00:16:34.880> it 00:16:35.030 --> 00:16:35.040 align:start position:0% don't access each other state and if it 00:16:35.040 --> 00:16:36.990 align:start position:0% don't access each other state and if it finds<00:16:35.279> a<00:16:35.440> transaction<00:16:35.880> that<00:16:36.040> is<00:16:36.199> not<00:16:36.480> valid 00:16:36.990 --> 00:16:37.000 align:start position:0% finds a transaction that is not valid 00:16:37.000 --> 00:16:39.550 align:start position:0% finds a transaction that is not valid individually<00:16:38.000> it<00:16:38.160> gets<00:16:38.440> included<00:16:39.040> from<00:16:39.440> uh 00:16:39.550 --> 00:16:39.560 align:start position:0% individually it gets included from uh 00:16:39.560 --> 00:16:42.030 align:start position:0% individually it gets included from uh blog<00:16:39.800> building<00:16:40.720> and<00:16:40.880> the<00:16:41.040> next<00:16:41.279> step<00:16:41.639> for<00:16:41.880> the 00:16:42.030 --> 00:16:42.040 align:start position:0% blog building and the next step for the 00:16:42.040 --> 00:16:44.110 align:start position:0% blog building and the next step for the blog<00:16:42.279> Builder<00:16:42.920> is<00:16:43.120> to<00:16:43.480> validate<00:16:43.880> all 00:16:44.110 --> 00:16:44.120 align:start position:0% blog Builder is to validate all 00:16:44.120 --> 00:16:46.910 align:start position:0% blog Builder is to validate all transactions<00:16:44.720> that<00:16:45.519> uh<00:16:46.199> that<00:16:46.480> remain<00:16:46.800> that 00:16:46.910 --> 00:16:46.920 align:start position:0% transactions that uh that remain that 00:16:46.920 --> 00:16:50.110 align:start position:0% transactions that uh that remain that are<00:16:47.160> remaining<00:16:47.560> in<00:16:47.839> a<00:16:48.079> in<00:16:48.199> a<00:16:48.319> smamp<00:16:48.639> pole<00:16:49.440> and 00:16:50.110 --> 00:16:50.120 align:start position:0% are remaining in a in a smamp pole and 00:16:50.120 --> 00:16:54.710 align:start position:0% are remaining in a in a smamp pole and build<00:16:50.560> an<00:16:51.199> valid<00:16:51.639> block<00:16:52.639> if<00:16:53.399> uh<00:16:53.839> we<00:16:54.000> were<00:16:54.319> not 00:16:54.710 --> 00:16:54.720 align:start position:0% build an valid block if uh we were not 00:16:54.720 --> 00:16:59.910 align:start position:0% build an valid block if uh we were not able<00:16:55.079> to<00:16:55.880> uh<00:16:56.240> separate<00:16:57.240> uh<00:16:57.519> the<00:16:57.800> scope<00:16:58.560> of<00:16:59.240> uh 00:16:59.910 --> 00:16:59.920 align:start position:0% able to uh separate uh the scope of uh 00:16:59.920 --> 00:17:01.430 align:start position:0% able to uh separate uh the scope of uh validation<00:17:00.399> code<00:17:00.759> in<00:17:00.920> one<00:17:01.079> of<00:17:01.240> these 00:17:01.430 --> 00:17:01.440 align:start position:0% validation code in one of these 00:17:01.440 --> 00:17:03.389 align:start position:0% validation code in one of these Transaction<00:17:02.279> what<00:17:02.440> could<00:17:02.639> happen<00:17:03.040> is<00:17:03.279> we 00:17:03.389 --> 00:17:03.399 align:start position:0% Transaction what could happen is we 00:17:03.399 --> 00:17:05.829 align:start position:0% Transaction what could happen is we could<00:17:03.639> have<00:17:03.880> a<00:17:04.280> mass<00:17:04.559> inv<00:17:04.760> validation<00:17:05.160> event 00:17:05.829 --> 00:17:05.839 align:start position:0% could have a mass inv validation event 00:17:05.839 --> 00:17:09.110 align:start position:0% could have a mass inv validation event when<00:17:06.160> one<00:17:06.839> transaction<00:17:07.839> uh<00:17:08.280> changes<00:17:08.799> some 00:17:09.110 --> 00:17:09.120 align:start position:0% when one transaction uh changes some 00:17:09.120 --> 00:17:12.230 align:start position:0% when one transaction uh changes some State<00:17:09.839> and<00:17:10.199> makes<00:17:10.679> all<00:17:11.199> other<00:17:11.520> transactions 00:17:12.230 --> 00:17:12.240 align:start position:0% State and makes all other transactions 00:17:12.240 --> 00:17:15.510 align:start position:0% State and makes all other transactions in<00:17:12.439> your<00:17:12.679> block<00:17:13.439> invalid<00:17:14.439> and<00:17:14.720> uh<00:17:15.039> it<00:17:15.199> provides 00:17:15.510 --> 00:17:15.520 align:start position:0% in your block invalid and uh it provides 00:17:15.520 --> 00:17:19.870 align:start position:0% in your block invalid and uh it provides a<00:17:15.760> huge<00:17:16.760> d<00:17:17.240> uh<00:17:17.400> DS<00:17:17.880> Vector<00:17:18.640> for<00:17:19.319> mol 00:17:19.870 --> 00:17:19.880 align:start position:0% a huge d uh DS Vector for mol 00:17:19.880 --> 00:17:21.990 align:start position:0% a huge d uh DS Vector for mol participants<00:17:20.400> and<00:17:20.559> blog<00:17:20.799> Builders<00:17:21.760> because 00:17:21.990 --> 00:17:22.000 align:start position:0% participants and blog Builders because 00:17:22.000 --> 00:17:24.110 align:start position:0% participants and blog Builders because we<00:17:22.120> don't<00:17:22.240> want<00:17:22.400> them<00:17:22.799> propagating<00:17:23.799> uh<00:17:23.919> in 00:17:24.110 --> 00:17:24.120 align:start position:0% we don't want them propagating uh in 00:17:24.120 --> 00:17:25.350 align:start position:0% we don't want them propagating uh in valid 00:17:25.350 --> 00:17:25.360 align:start position:0% valid 00:17:25.360 --> 00:17:28.909 align:start position:0% valid blocks<00:17:26.360> uh<00:17:26.679> now<00:17:27.160> uh<00:17:27.280> developers<00:17:28.079> who<00:17:28.319> are 00:17:28.909 --> 00:17:28.919 align:start position:0% blocks uh now uh developers who are 00:17:28.919 --> 00:17:30.390 align:start position:0% blocks uh now uh developers who are interested<00:17:29.320> especially<00:17:29.720> if<00:17:29.799> you're<00:17:30.039> working 00:17:30.390 --> 00:17:30.400 align:start position:0% interested especially if you're working 00:17:30.400 --> 00:17:32.750 align:start position:0% interested especially if you're working on<00:17:30.559> layer<00:17:30.799> twos<00:17:31.360> what<00:17:31.480> can<00:17:31.640> you<00:17:31.840> do<00:17:32.200> to<00:17:32.559> make 00:17:32.750 --> 00:17:32.760 align:start position:0% on layer twos what can you do to make 00:17:32.760 --> 00:17:35.070 align:start position:0% on layer twos what can you do to make Native<00:17:33.080> account<00:17:33.360> obstruction<00:17:33.840> happen<00:17:34.720> first 00:17:35.070 --> 00:17:35.080 align:start position:0% Native account obstruction happen first 00:17:35.080 --> 00:17:37.390 align:start position:0% Native account obstruction happen first like<00:17:35.280> do<00:17:35.480> get<00:17:35.600> in<00:17:35.760> touch<00:17:36.000> with<00:17:36.160> us<00:17:36.559> on<00:17:36.960> any<00:17:37.160> of 00:17:37.390 --> 00:17:37.400 align:start position:0% like do get in touch with us on any of 00:17:37.400 --> 00:17:40.390 align:start position:0% like do get in touch with us on any of our<00:17:37.960> uh<00:17:38.080> channels<00:17:38.480> Discord<00:17:38.919> Telegram<00:17:39.919> and 00:17:40.390 --> 00:17:40.400 align:start position:0% our uh channels Discord Telegram and 00:17:40.400 --> 00:17:41.909 align:start position:0% our uh channels Discord Telegram and let's<00:17:40.679> talk<00:17:40.919> about<00:17:41.200> Native<00:17:41.559> account 00:17:41.909 --> 00:17:41.919 align:start position:0% let's talk about Native account 00:17:41.919 --> 00:17:44.470 align:start position:0% let's talk about Native account abstraction<00:17:42.919> uh<00:17:43.120> do<00:17:43.400> just<00:17:43.679> read<00:17:44.080> and<00:17:44.280> get 00:17:44.470 --> 00:17:44.480 align:start position:0% abstraction uh do just read and get 00:17:44.480 --> 00:17:48.230 align:start position:0% abstraction uh do just read and get familiar<00:17:45.080> with<00:17:45.799> either<00:17:46.360> both<00:17:46.679> RP<00:17:47.200> 7560<00:17:48.039> and 00:17:48.230 --> 00:17:48.240 align:start position:0% familiar with either both RP 7560 and 00:17:48.240 --> 00:17:49.470 align:start position:0% familiar with either both RP 7560 and EAP 00:17:49.470 --> 00:17:49.480 align:start position:0% EAP 00:17:49.480 --> 00:17:52.750 align:start position:0% EAP 7701<00:17:50.480> uh<00:17:50.600> we're<00:17:50.799> looking<00:17:51.039> for<00:17:51.280> feedback<00:17:51.679> on<00:17:51.799> it 00:17:52.750 --> 00:17:52.760 align:start position:0% 7701 uh we're looking for feedback on it 00:17:52.760 --> 00:17:56.909 align:start position:0% 7701 uh we're looking for feedback on it um<00:17:53.760> and<00:17:54.600> you<00:17:54.720> can<00:17:54.919> also<00:17:55.320> go<00:17:56.320> dive<00:17:56.520> into<00:17:56.760> the 00:17:56.909 --> 00:17:56.919 align:start position:0% um and you can also go dive into the 00:17:56.919 --> 00:17:59.190 align:start position:0% um and you can also go dive into the code<00:17:57.840> uh<00:17:58.000> this<00:17:58.080> is<00:17:58.200> the<00:17:58.320> link<00:17:58.520> to<00:17:58.840> our 00:17:59.190 --> 00:17:59.200 align:start position:0% code uh this is the link to our 00:17:59.200 --> 00:18:02.510 align:start position:0% code uh this is the link to our reference<00:17:59.840> implementation<00:18:00.840> of<00:18:01.159> RP 00:18:02.510 --> 00:18:02.520 align:start position:0% reference implementation of RP 00:18:02.520 --> 00:18:05.710 align:start position:0% reference implementation of RP 7560<00:18:03.520> uh<00:18:03.720> there<00:18:03.840> is<00:18:04.039> also<00:18:04.360> a<00:18:04.640> roll<00:18:04.960> call<00:18:05.200> event 00:18:05.710 --> 00:18:05.720 align:start position:0% 7560 uh there is also a roll call event 00:18:05.720 --> 00:18:08.750 align:start position:0% 7560 uh there is also a roll call event for<00:18:06.200> the<00:18:06.320> RP<00:18:07.000> process<00:18:08.000> I<00:18:08.280> guess<00:18:08.480> everybody 00:18:08.750 --> 00:18:08.760 align:start position:0% for the RP process I guess everybody 00:18:08.760 --> 00:18:12.230 align:start position:0% for the RP process I guess everybody knows<00:18:08.960> it<00:18:09.120> just<00:18:09.559> join<00:18:09.799> it<00:18:10.039> add<00:18:10.360> RP<00:18:10.919> 7560<00:18:11.919> to<00:18:12.080> the 00:18:12.230 --> 00:18:12.240 align:start position:0% knows it just join it add RP 7560 to the 00:18:12.240 --> 00:18:14.430 align:start position:0% knows it just join it add RP 7560 to the agenda<00:18:12.960> and<00:18:13.159> discuss<00:18:13.480> it<00:18:13.640> with<00:18:13.880> other<00:18:14.080> layers 00:18:14.430 --> 00:18:14.440 align:start position:0% agenda and discuss it with other layers 00:18:14.440 --> 00:18:17.350 align:start position:0% agenda and discuss it with other layers too<00:18:15.120> and<00:18:15.400> let's<00:18:15.840> uh<00:18:16.000> let's<00:18:16.159> start<00:18:16.360> building<00:18:16.720> it 00:18:17.350 --> 00:18:17.360 align:start position:0% too and let's uh let's start building it 00:18:17.360 --> 00:18:20.669 align:start position:0% too and let's uh let's start building it so<00:18:17.679> here<00:18:17.840> are<00:18:18.200> our<00:18:18.600> websites<00:18:19.480> and<00:18:19.960> uh<00:18:20.159> that's 00:18:20.669 --> 00:18:20.679 align:start position:0% so here are our websites and uh that's 00:18:20.679 --> 00:18:22.549 align:start position:0% so here are our websites and uh that's uh<00:18:20.840> that's<00:18:21.000> it 00:18:22.549 --> 00:18:22.559 align:start position:0% uh that's it 00:18:22.559 --> 00:18:26.029 align:start position:0% uh that's it for<00:18:23.559> thank 00:18:26.029 --> 00:18:26.039 align:start position:0% 00:18:26.039 --> 00:18:29.270 align:start position:0% you<00:18:27.039> thank<00:18:27.760> thank<00:18:27.960> you<00:18:28.080> so<00:18:28.320> much 00:18:29.270 --> 00:18:29.280 align:start position:0% you thank thank you so much 00:18:29.280 --> 00:18:31.950 align:start position:0% you thank thank you so much Alex<00:18:30.280> let<00:18:30.440> me<00:18:30.600> start<00:18:30.880> with<00:18:31.159> questions<00:18:31.760> the 00:18:31.950 --> 00:18:31.960 align:start position:0% Alex let me start with questions the 00:18:31.960 --> 00:18:36.590 align:start position:0% Alex let me start with questions the first<00:18:32.240> one<00:18:32.679> is<00:18:33.679> if<00:18:34.240> 4337<00:18:35.240> bundles<00:18:36.039> bundlers 00:18:36.590 --> 00:18:36.600 align:start position:0% first one is if 4337 bundles bundlers 00:18:36.600 --> 00:18:39.029 align:start position:0% first one is if 4337 bundles bundlers don't<00:18:37.480> yet<00:18:37.720> support<00:18:38.159> the<00:18:38.360> aggregation 00:18:39.029 --> 00:18:39.039 align:start position:0% don't yet support the aggregation 00:18:39.039 --> 00:18:42.070 align:start position:0% don't yet support the aggregation portion<00:18:39.520> of<00:18:39.720> the<00:18:39.960> spec<00:18:40.799> how<00:18:41.039> can<00:18:41.240> we<00:18:41.520> read<00:18:41.919> how 00:18:42.070 --> 00:18:42.080 align:start position:0% portion of the spec how can we read how 00:18:42.080 --> 00:18:44.190 align:start position:0% portion of the spec how can we read how can<00:18:42.280> we<00:18:42.520> be<00:18:42.720> ready<00:18:43.080> to<00:18:43.280> make<00:18:43.440> it<00:18:43.679> part<00:18:43.880> of<00:18:44.000> the 00:18:44.190 --> 00:18:44.200 align:start position:0% can we be ready to make it part of the 00:18:44.200 --> 00:18:47.590 align:start position:0% can we be ready to make it part of the protocol<00:18:45.200> yeah<00:18:45.480> so<00:18:46.120> uh<00:18:46.320> aggregation<00:18:47.120> is<00:18:47.400> a 00:18:47.590 --> 00:18:47.600 align:start position:0% protocol yeah so uh aggregation is a 00:18:47.600 --> 00:18:50.350 align:start position:0% protocol yeah so uh aggregation is a part<00:18:47.799> of<00:18:48.039> 4337<00:18:49.039> it<00:18:49.240> will<00:18:49.480> be<00:18:49.720> part<00:18:49.880> of<00:18:50.039> native 00:18:50.350 --> 00:18:50.360 align:start position:0% part of 4337 it will be part of native 00:18:50.360 --> 00:18:52.750 align:start position:0% part of 4337 it will be part of native account<00:18:50.679> obstruction<00:18:51.640> uh<00:18:52.080> eventually<00:18:52.600> we 00:18:52.750 --> 00:18:52.760 align:start position:0% account obstruction uh eventually we 00:18:52.760 --> 00:18:55.390 align:start position:0% account obstruction uh eventually we have<00:18:52.919> a<00:18:53.039> draft<00:18:53.480> EAP<00:18:53.880> for<00:18:54.080> that<00:18:54.799> uh<00:18:55.039> however 00:18:55.390 --> 00:18:55.400 align:start position:0% have a draft EAP for that uh however 00:18:55.400 --> 00:18:57.270 align:start position:0% have a draft EAP for that uh however it's<00:18:55.520> a<00:18:55.679> complex<00:18:56.240> Topic<00:18:56.520> in<00:18:56.679> itself<00:18:57.080> the 00:18:57.270 --> 00:18:57.280 align:start position:0% it's a complex Topic in itself the 00:18:57.280 --> 00:19:00.470 align:start position:0% it's a complex Topic in itself the aggregated<00:18:57.799> signatures<00:18:58.320> are<00:18:58.840> complex<00:18:59.480> and 00:19:00.470 --> 00:19:00.480 align:start position:0% aggregated signatures are complex and 00:19:00.480 --> 00:19:02.470 align:start position:0% aggregated signatures are complex and there<00:19:00.679> has<00:19:00.799> been<00:19:01.360> little<00:19:01.720> adoption<00:19:02.159> of 00:19:02.470 --> 00:19:02.480 align:start position:0% there has been little adoption of 00:19:02.480 --> 00:19:05.870 align:start position:0% there has been little adoption of aggregation<00:19:03.120> yet<00:19:04.000> uh<00:19:05.000> it<00:19:05.280> does<00:19:05.559> provide 00:19:05.870 --> 00:19:05.880 align:start position:0% aggregation yet uh it does provide 00:19:05.880 --> 00:19:07.870 align:start position:0% aggregation yet uh it does provide additional<00:19:06.280> challenges<00:19:07.159> in<00:19:07.280> the<00:19:07.400> context<00:19:07.720> of 00:19:07.870 --> 00:19:07.880 align:start position:0% additional challenges in the context of 00:19:07.880 --> 00:19:10.590 align:start position:0% additional challenges in the context of native<00:19:08.240> account<00:19:08.799> obstruction<00:19:09.799> uh<00:19:10.000> but<00:19:10.320> I 00:19:10.590 --> 00:19:10.600 align:start position:0% native account obstruction uh but I 00:19:10.600 --> 00:19:12.310 align:start position:0% native account obstruction uh but I think<00:19:10.799> we<00:19:10.880> will<00:19:11.039> overcome<00:19:11.440> them<00:19:11.600> and<00:19:11.799> again 00:19:12.310 --> 00:19:12.320 align:start position:0% think we will overcome them and again 00:19:12.320 --> 00:19:13.750 align:start position:0% think we will overcome them and again our<00:19:12.559> approach<00:19:12.840> is<00:19:12.960> to<00:19:13.120> make<00:19:13.280> all<00:19:13.440> these 00:19:13.750 --> 00:19:13.760 align:start position:0% our approach is to make all these 00:19:13.760 --> 00:19:16.510 align:start position:0% our approach is to make all these changes<00:19:14.360> very<00:19:14.600> very<00:19:14.840> modular<00:19:15.600> we<00:19:15.720> don't<00:19:16.360> want 00:19:16.510 --> 00:19:16.520 align:start position:0% changes very very modular we don't want 00:19:16.520 --> 00:19:19.029 align:start position:0% changes very very modular we don't want to<00:19:16.679> make<00:19:16.919> one<00:19:17.240> Mega<00:19:18.159> account<00:19:18.520> obstruction 00:19:19.029 --> 00:19:19.039 align:start position:0% to make one Mega account obstruction 00:19:19.039 --> 00:19:21.630 align:start position:0% to make one Mega account obstruction spec<00:19:19.600> and<00:19:19.760> implement<00:19:20.159> it<00:19:20.320> in<00:19:20.480> one<00:19:20.679> fork<00:19:21.520> we 00:19:21.630 --> 00:19:21.640 align:start position:0% spec and implement it in one fork we 00:19:21.640 --> 00:19:24.310 align:start position:0% spec and implement it in one fork we want<00:19:21.799> to<00:19:21.960> make<00:19:22.280> like<00:19:22.440> basically<00:19:22.919> as<00:19:23.120> many<00:19:23.679> eaps 00:19:24.310 --> 00:19:24.320 align:start position:0% want to make like basically as many eaps 00:19:24.320 --> 00:19:27.789 align:start position:0% want to make like basically as many eaps as<00:19:24.840> possible<00:19:25.840> uh<00:19:26.080> reasonably<00:19:27.080> uh<00:19:27.400> so<00:19:27.640> that 00:19:27.789 --> 00:19:27.799 align:start position:0% as possible uh reasonably uh so that 00:19:27.799 --> 00:19:30.750 align:start position:0% as possible uh reasonably uh so that chains<00:19:28.240> can<00:19:29.120> uh<00:19:29.320> adopt<00:19:29.799> them<00:19:30.039> meaningfully 00:19:30.750 --> 00:19:30.760 align:start position:0% chains can uh adopt them meaningfully 00:19:30.760 --> 00:19:35.789 align:start position:0% chains can uh adopt them meaningfully but<00:19:31.159> uh<00:19:31.640> uh<00:19:31.960> one<00:19:32.240> by<00:19:32.720> one<00:19:33.720> uh 00:19:35.789 --> 00:19:35.799 align:start position:0% but uh uh one by one uh 00:19:35.799 --> 00:19:38.350 align:start position:0% but uh uh one by one uh okay<00:19:36.799> next<00:19:37.039> one<00:19:37.240> how<00:19:37.440> critical<00:19:37.919> and<00:19:38.120> how 00:19:38.350 --> 00:19:38.360 align:start position:0% okay next one how critical and how 00:19:38.360 --> 00:19:39.750 align:start position:0% okay next one how critical and how centralized 00:19:39.750 --> 00:19:39.760 align:start position:0% centralized 00:19:39.760 --> 00:19:42.909 align:start position:0% centralized is<00:19:40.760> are<00:19:40.919> the<00:19:41.120> bundled<00:19:41.799> like<00:19:42.039> is<00:19:42.280> is<00:19:42.480> Bund<00:19:42.799> is 00:19:42.909 --> 00:19:42.919 align:start position:0% is are the bundled like is is Bund is 00:19:42.919 --> 00:19:46.390 align:start position:0% is are the bundled like is is Bund is the<00:19:43.320> bundled<00:19:44.320> okay<00:19:44.919> can<00:19:45.039> I 00:19:46.390 --> 00:19:46.400 align:start position:0% the bundled okay can I 00:19:46.400 --> 00:19:49.830 align:start position:0% the bundled okay can I see<00:19:47.400> how<00:19:48.200> sorry<00:19:48.600> how<00:19:48.840> critical<00:19:49.400> and<00:19:49.600> how 00:19:49.830 --> 00:19:49.840 align:start position:0% see how sorry how critical and how 00:19:49.840 --> 00:19:51.789 align:start position:0% see how sorry how critical and how centralized<00:19:50.559> is<00:19:50.720> the<00:19:50.919> bundle<00:19:51.440> yeah<00:19:51.559> I<00:19:51.640> guess 00:19:51.789 --> 00:19:51.799 align:start position:0% centralized is the bundle yeah I guess 00:19:51.799 --> 00:19:55.590 align:start position:0% centralized is the bundle yeah I guess the<00:19:52.000> bundler<00:19:52.640> uh<00:19:53.159> so<00:19:53.360> in<00:19:53.520> ERC<00:19:53.919> 467<00:19:54.679> bundler<00:19:55.120> is 00:19:55.590 --> 00:19:55.600 align:start position:0% the bundler uh so in ERC 467 bundler is 00:19:55.600 --> 00:19:58.870 align:start position:0% the bundler uh so in ERC 467 bundler is critical<00:19:56.600> not<00:19:57.000> very<00:19:57.280> centralized<00:19:58.200> if<00:19:58.360> you<00:19:58.720> use 00:19:58.870 --> 00:19:58.880 align:start position:0% critical not very centralized if you use 00:19:58.880 --> 00:20:00.310 align:start position:0% critical not very centralized if you use it<00:19:59.000> correctly<00:19:59.400> so<00:19:59.559> if<00:19:59.640> you're<00:19:59.840> using<00:20:00.080> it<00:20:00.200> with 00:20:00.310 --> 00:20:00.320 align:start position:0% it correctly so if you're using it with 00:20:00.320 --> 00:20:05.470 align:start position:0% it correctly so if you're using it with a<00:20:00.400> M<00:20:00.880> Pool<00:20:02.159> uh<00:20:03.159> that<00:20:03.480> is<00:20:03.720> not<00:20:04.280> uh<00:20:04.520> like<00:20:05.120> you<00:20:05.280> you 00:20:05.470 --> 00:20:05.480 align:start position:0% a M Pool uh that is not uh like you you 00:20:05.480 --> 00:20:08.470 align:start position:0% a M Pool uh that is not uh like you you don't<00:20:05.679> depend<00:20:05.919> on<00:20:06.080> any<00:20:06.280> centralized<00:20:07.480> bundler 00:20:08.470 --> 00:20:08.480 align:start position:0% don't depend on any centralized bundler 00:20:08.480 --> 00:20:10.470 align:start position:0% don't depend on any centralized bundler uh<00:20:08.679> with<00:20:09.480> uh 00:20:10.470 --> 00:20:10.480 align:start position:0% uh with uh 00:20:10.480 --> 00:20:13.310 align:start position:0% uh with uh 7560<00:20:11.480> um<00:20:11.679> the<00:20:11.840> RO<00:20:12.039> of<00:20:12.120> the<00:20:12.240> bundler<00:20:12.640> changes<00:20:13.120> it 00:20:13.310 --> 00:20:13.320 align:start position:0% 7560 um the RO of the bundler changes it 00:20:13.320 --> 00:20:16.110 align:start position:0% 7560 um the RO of the bundler changes it becomes<00:20:13.880> more<00:20:14.320> of<00:20:14.679> an<00:20:14.880> assistant<00:20:15.400> to<00:20:15.880> to<00:20:16.000> the 00:20:16.110 --> 00:20:16.120 align:start position:0% becomes more of an assistant to to the 00:20:16.120 --> 00:20:18.669 align:start position:0% becomes more of an assistant to to the block<00:20:16.520> Builder<00:20:17.520> and<00:20:17.720> then<00:20:17.960> it's<00:20:18.400> as 00:20:18.669 --> 00:20:18.679 align:start position:0% block Builder and then it's as 00:20:18.679 --> 00:20:20.750 align:start position:0% block Builder and then it's as decentralized<00:20:19.440> in<00:20:19.600> the<00:20:19.720> underlying<00:20:20.240> Network 00:20:20.750 --> 00:20:20.760 align:start position:0% decentralized in the underlying Network 00:20:20.760 --> 00:20:24.510 align:start position:0% decentralized in the underlying Network there<00:20:20.880> is<00:20:21.080> no<00:20:22.000> added<00:20:22.679> centralization<00:20:23.520> Vector 00:20:24.510 --> 00:20:24.520 align:start position:0% there is no added centralization Vector 00:20:24.520 --> 00:20:27.950 align:start position:0% there is no added centralization Vector uh<00:20:24.760> on<00:20:24.919> on<00:20:25.000> the<00:20:25.159> bunders<00:20:26.440> uh<00:20:27.440> does<00:20:27.600> that<00:20:27.760> make 00:20:27.950 --> 00:20:27.960 align:start position:0% uh on on the bunders uh does that make 00:20:27.960 --> 00:20:31.510 align:start position:0% uh on on the bunders uh does that make sense<00:20:28.400> uh<00:20:28.520> yeah<00:20:28.919> okay<00:20:29.200> thank<00:20:29.919> you<00:20:30.919> next<00:20:31.120> one<00:20:31.360> we 00:20:31.510 --> 00:20:31.520 align:start position:0% sense uh yeah okay thank you next one we 00:20:31.520 --> 00:20:36.070 align:start position:0% sense uh yeah okay thank you next one we have<00:20:32.159> 4337<00:20:33.360> 756 00:20:36.070 --> 00:20:36.080 align:start position:0% have 4337 756 00:20:36.080 --> 00:20:39.350 align:start position:0% have 4337 756 07702<00:20:37.080> can<00:20:37.240> you<00:20:38.039> can<00:20:38.200> you<00:20:38.400> describe<00:20:38.960> how<00:20:39.200> they 00:20:39.350 --> 00:20:39.360 align:start position:0% 07702 can you can you describe how they 00:20:39.360 --> 00:20:41.750 align:start position:0% 07702 can you can you describe how they all<00:20:39.600> play<00:20:39.960> nicely<00:20:40.400> with<00:20:40.600> each<00:20:40.799> other<00:20:41.400> and<00:20:41.559> how 00:20:41.750 --> 00:20:41.760 align:start position:0% all play nicely with each other and how 00:20:41.760 --> 00:20:44.070 align:start position:0% all play nicely with each other and how can<00:20:41.919> we<00:20:42.120> avoid<00:20:42.520> once<00:20:42.880> again<00:20:43.280> fragmentation 00:20:44.070 --> 00:20:44.080 align:start position:0% can we avoid once again fragmentation 00:20:44.080 --> 00:20:47.149 align:start position:0% can we avoid once again fragmentation the<00:20:44.320> space<00:20:45.120> in<00:20:45.320> this<00:20:45.559> case<00:20:45.799> with<00:20:46.039> regard<00:20:46.320> to<00:20:46.559> AA 00:20:47.149 --> 00:20:47.159 align:start position:0% the space in this case with regard to AA 00:20:47.159 --> 00:20:50.190 align:start position:0% the space in this case with regard to AA account<00:20:47.559> abstraction<00:20:48.159> Solutions<00:20:49.159> um<00:20:50.000> right 00:20:50.190 --> 00:20:50.200 align:start position:0% account abstraction Solutions um right 00:20:50.200 --> 00:20:53.750 align:start position:0% account abstraction Solutions um right so<00:20:50.600> 7702<00:20:51.600> does<00:20:51.760> not<00:20:51.919> pose<00:20:52.280> any<00:20:52.760> fragmentation 00:20:53.750 --> 00:20:53.760 align:start position:0% so 7702 does not pose any fragmentation 00:20:53.760 --> 00:20:55.909 align:start position:0% so 7702 does not pose any fragmentation uh<00:20:53.960> challenges<00:20:54.559> whatsoever<00:20:55.039> because<00:20:55.600> this<00:20:55.720> is 00:20:55.909 --> 00:20:55.919 align:start position:0% uh challenges whatsoever because this is 00:20:55.919 --> 00:20:58.909 align:start position:0% uh challenges whatsoever because this is just<00:20:56.080> a<00:20:56.280> new<00:20:56.559> feature<00:20:57.039> of<00:20:57.679> of<00:20:57.799> the<00:20:57.919> evm<00:20:58.640> and<00:20:58.760> I 00:20:58.909 --> 00:20:58.919 align:start position:0% just a new feature of of the evm and I 00:20:58.919 --> 00:21:01.070 align:start position:0% just a new feature of of the evm and I assume<00:20:59.159> it<00:20:59.280> will<00:20:59.480> get<00:20:59.679> supported<00:21:00.320> like<00:21:00.760> pretty 00:21:01.070 --> 00:21:01.080 align:start position:0% assume it will get supported like pretty 00:21:01.080 --> 00:21:05.190 align:start position:0% assume it will get supported like pretty widely<00:21:01.840> and<00:21:02.679> it's<00:21:03.240> also<00:21:04.240> like<00:21:04.720> it's<00:21:04.840> an 00:21:05.190 --> 00:21:05.200 align:start position:0% widely and it's also like it's an 00:21:05.200 --> 00:21:08.270 align:start position:0% widely and it's also like it's an addition<00:21:05.679> to<00:21:06.360> uh<00:21:06.559> account<00:21:06.960> obstruction<00:21:07.960> road 00:21:08.270 --> 00:21:08.280 align:start position:0% addition to uh account obstruction road 00:21:08.280 --> 00:21:12.350 align:start position:0% addition to uh account obstruction road map<00:21:08.720> with<00:21:08.919> 4367<00:21:09.720> and<00:21:10.159> 7560<00:21:11.159> we<00:21:11.320> keep<00:21:11.600> the<00:21:11.880> flow 00:21:12.350 --> 00:21:12.360 align:start position:0% map with 4367 and 7560 we keep the flow 00:21:12.360 --> 00:21:15.909 align:start position:0% map with 4367 and 7560 we keep the flow the<00:21:12.520> user<00:21:12.760> flow<00:21:13.559> uh<00:21:13.960> so<00:21:14.240> similar<00:21:14.760> that<00:21:15.039> it<00:21:15.640> it 00:21:15.909 --> 00:21:15.919 align:start position:0% the user flow uh so similar that it it 00:21:15.919 --> 00:21:18.750 align:start position:0% the user flow uh so similar that it it can<00:21:16.520> have<00:21:16.799> very<00:21:17.039> minimal<00:21:17.880> traction<00:21:18.440> uh<00:21:18.600> like 00:21:18.750 --> 00:21:18.760 align:start position:0% can have very minimal traction uh like 00:21:18.760 --> 00:21:21.029 align:start position:0% can have very minimal traction uh like friction<00:21:19.559> in<00:21:19.760> terms<00:21:20.159> of<00:21:20.320> fragmentation 00:21:21.029 --> 00:21:21.039 align:start position:0% friction in terms of fragmentation 00:21:21.039 --> 00:21:22.710 align:start position:0% friction in terms of fragmentation because<00:21:21.600> if<00:21:21.720> you<00:21:21.840> have<00:21:22.000> two<00:21:22.200> accounts<00:21:22.559> and 00:21:22.710 --> 00:21:22.720 align:start position:0% because if you have two accounts and 00:21:22.720 --> 00:21:25.710 align:start position:0% because if you have two accounts and their<00:21:23.320> differences<00:21:23.799> are<00:21:24.000> so<00:21:24.559> minimal<00:21:25.559> I 00:21:25.710 --> 00:21:25.720 align:start position:0% their differences are so minimal I 00:21:25.720 --> 00:21:28.149 align:start position:0% their differences are so minimal I assume<00:21:26.159> just<00:21:26.400> most<00:21:27.000> wallets<00:21:27.440> would<00:21:27.720> support 00:21:28.149 --> 00:21:28.159 align:start position:0% assume just most wallets would support 00:21:28.159 --> 00:21:31.029 align:start position:0% assume just most wallets would support both<00:21:28.880> and<00:21:29.159> both<00:21:29.320> of<00:21:29.480> them<00:21:29.720> will<00:21:30.400> coexist 00:21:31.029 --> 00:21:31.039 align:start position:0% both and both of them will coexist 00:21:31.039 --> 00:21:34.549 align:start position:0% both and both of them will coexist peacefully<00:21:32.039> for<00:21:32.240> a<00:21:32.400> period<00:21:33.120> between<00:21:34.120> uh<00:21:34.279> now 00:21:34.549 --> 00:21:34.559 align:start position:0% peacefully for a period between uh now 00:21:34.559 --> 00:21:38.070 align:start position:0% peacefully for a period between uh now and<00:21:34.760> when<00:21:35.440> uh<00:21:35.840> 7701<00:21:36.840> is<00:21:37.080> implemented<00:21:37.600> on<00:21:37.760> Main 00:21:38.070 --> 00:21:38.080 align:start position:0% and when uh 7701 is implemented on Main 00:21:38.080 --> 00:21:40.990 align:start position:0% and when uh 7701 is implemented on Main net<00:21:39.080> and<00:21:39.600> and<00:21:39.720> so<00:21:39.960> like<00:21:40.320> they<00:21:40.400> are<00:21:40.559> all<00:21:40.720> still 00:21:40.990 --> 00:21:41.000 align:start position:0% net and and so like they are all still 00:21:41.000 --> 00:21:42.909 align:start position:0% net and and so like they are all still part<00:21:41.200> of<00:21:41.320> the<00:21:41.480> same<00:21:41.720> ecosystem<00:21:42.360> so<00:21:42.520> it's<00:21:42.720> not 00:21:42.909 --> 00:21:42.919 align:start position:0% part of the same ecosystem so it's not 00:21:42.919 --> 00:21:45.470 align:start position:0% part of the same ecosystem so it's not fragmented<00:21:43.520> it's<00:21:43.720> just<00:21:44.679> different<00:21:44.919> flavors 00:21:45.470 --> 00:21:45.480 align:start position:0% fragmented it's just different flavors 00:21:45.480 --> 00:21:48.269 align:start position:0% fragmented it's just different flavors of<00:21:45.960> uh<00:21:46.120> of<00:21:46.279> the<00:21:46.440> same<00:21:47.120> uh<00:21:47.360> same<00:21:47.640> thing<00:21:48.159> that 00:21:48.269 --> 00:21:48.279 align:start position:0% of uh of the same uh same thing that 00:21:48.279 --> 00:21:50.390 align:start position:0% of uh of the same uh same thing that makes 00:21:50.390 --> 00:21:50.400 align:start position:0% makes 00:21:50.400 --> 00:21:52.870 align:start position:0% makes sense<00:21:51.400> what's<00:21:51.600> your<00:21:51.799> recommended<00:21:52.320> drou<00:21:52.679> map 00:21:52.870 --> 00:21:52.880 align:start position:0% sense what's your recommended drou map 00:21:52.880 --> 00:21:54.990 align:start position:0% sense what's your recommended drou map for<00:21:53.080> metamask<00:21:53.640> to<00:21:53.840> achieve<00:21:54.200> the<00:21:54.320> end<00:21:54.600> goal<00:21:54.840> of 00:21:54.990 --> 00:21:55.000 align:start position:0% for metamask to achieve the end goal of 00:21:55.000 --> 00:21:56.110 align:start position:0% for metamask to achieve the end goal of account 00:21:56.110 --> 00:21:56.120 align:start position:0% account 00:21:56.120 --> 00:21:58.630 align:start position:0% account obstruction<00:21:57.120> yeah<00:21:57.279> so<00:21:57.559> metamask<00:21:58.080> and<00:21:58.240> other 00:21:58.630 --> 00:21:58.640 align:start position:0% obstruction yeah so metamask and other 00:21:58.640 --> 00:22:01.750 align:start position:0% obstruction yeah so metamask and other wallets<00:21:59.360> uh<00:21:59.760> EA<00:22:00.159> wallets<00:22:00.880> they<00:22:01.000> would<00:22:01.200> be<00:22:01.600> like 00:22:01.750 --> 00:22:01.760 align:start position:0% wallets uh EA wallets they would be like 00:22:01.760 --> 00:22:03.669 align:start position:0% wallets uh EA wallets they would be like it<00:22:01.880> would<00:22:02.000> be<00:22:02.159> great<00:22:02.559> if<00:22:02.880> they<00:22:03.159> started 00:22:03.669 --> 00:22:03.679 align:start position:0% it would be great if they started 00:22:03.679 --> 00:22:06.269 align:start position:0% it would be great if they started looking<00:22:04.039> into<00:22:05.039> account<00:22:05.400> abstraction<00:22:05.919> like 00:22:06.269 --> 00:22:06.279 align:start position:0% looking into account abstraction like 00:22:06.279 --> 00:22:10.590 align:start position:0% looking into account abstraction like they<00:22:06.400> can<00:22:06.679> start<00:22:07.080> with<00:22:07.799> uh<00:22:08.960> 7702<00:22:09.960> with<00:22:10.320> getting 00:22:10.590 --> 00:22:10.600 align:start position:0% they can start with uh 7702 with getting 00:22:10.600 --> 00:22:13.590 align:start position:0% they can start with uh 7702 with getting all<00:22:10.919> users<00:22:11.320> to<00:22:12.039> also<00:22:12.440> include<00:22:12.919> some<00:22:13.240> kind<00:22:13.400> of 00:22:13.590 --> 00:22:13.600 align:start position:0% all users to also include some kind of 00:22:13.600 --> 00:22:16.909 align:start position:0% all users to also include some kind of code<00:22:14.520> uh<00:22:14.880> in<00:22:15.039> their<00:22:15.360> EAS<00:22:16.080> it<00:22:16.200> can<00:22:16.360> be<00:22:16.520> like<00:22:16.679> very 00:22:16.909 --> 00:22:16.919 align:start position:0% code uh in their EAS it can be like very 00:22:16.919 --> 00:22:19.710 align:start position:0% code uh in their EAS it can be like very simple<00:22:17.320> like<00:22:17.480> recovery<00:22:18.000> or<00:22:18.240> gas<00:22:18.720> sponsoring 00:22:19.710 --> 00:22:19.720 align:start position:0% simple like recovery or gas sponsoring 00:22:19.720 --> 00:22:23.190 align:start position:0% simple like recovery or gas sponsoring and<00:22:19.919> everything<00:22:20.520> but<00:22:21.520> crucially<00:22:21.960> it<00:22:22.120> will<00:22:22.840> uh 00:22:23.190 --> 00:22:23.200 align:start position:0% and everything but crucially it will uh 00:22:23.200 --> 00:22:26.510 align:start position:0% and everything but crucially it will uh to<00:22:23.480> get<00:22:23.600> a<00:22:23.919> production<00:22:24.400> experience<00:22:24.919> of<00:22:25.480> having 00:22:26.510 --> 00:22:26.520 align:start position:0% to get a production experience of having 00:22:26.520 --> 00:22:28.950 align:start position:0% to get a production experience of having uh<00:22:27.520> and<00:22:27.640> managing<00:22:28.039> a<00:22:28.120> fleet<00:22:28.559> of<00:22:28.679> smart 00:22:28.950 --> 00:22:28.960 align:start position:0% uh and managing a fleet of smart 00:22:28.960 --> 00:22:31.029 align:start position:0% uh and managing a fleet of smart contract<00:22:29.320> wallets<00:22:29.679> because<00:22:29.919> up<00:22:30.080> until<00:22:30.400> now 00:22:31.029 --> 00:22:31.039 align:start position:0% contract wallets because up until now 00:22:31.039 --> 00:22:32.470 align:start position:0% contract wallets because up until now like<00:22:31.240> most<00:22:31.440> wallets<00:22:31.799> have<00:22:32.039> only<00:22:32.320> been 00:22:32.470 --> 00:22:32.480 align:start position:0% like most wallets have only been 00:22:32.480 --> 00:22:35.350 align:start position:0% like most wallets have only been managing<00:22:32.960> like<00:22:33.080> the<00:22:33.640> private<00:22:34.000> Keys<00:22:34.360> part<00:22:35.120> and 00:22:35.350 --> 00:22:35.360 align:start position:0% managing like the private Keys part and 00:22:35.360 --> 00:22:38.190 align:start position:0% managing like the private Keys part and did<00:22:35.559> not<00:22:35.760> look<00:22:35.960> at<00:22:36.080> users<00:22:36.520> wallets<00:22:37.159> as<00:22:37.720> smart 00:22:38.190 --> 00:22:38.200 align:start position:0% did not look at users wallets as smart 00:22:38.200 --> 00:22:41.630 align:start position:0% did not look at users wallets as smart contracts<00:22:39.200> and<00:22:39.679> uh<00:22:40.640> after<00:22:40.960> that<00:22:41.159> like<00:22:41.520> there 00:22:41.630 --> 00:22:41.640 align:start position:0% contracts and uh after that like there 00:22:41.640 --> 00:22:45.310 align:start position:0% contracts and uh after that like there is<00:22:42.159> no<00:22:42.440> reason<00:22:42.919> the<00:22:43.360> for<00:22:43.520> metamask<00:22:44.039> not<00:22:44.200> to<00:22:44.640> use 00:22:45.310 --> 00:22:45.320 align:start position:0% is no reason the for metamask not to use 00:22:45.320 --> 00:22:48.710 align:start position:0% is no reason the for metamask not to use ERC<00:22:45.720> 4337<00:22:46.559> wallets<00:22:47.360> uh<00:22:47.640> for<00:22:47.880> people<00:22:48.200> who<00:22:48.559> who 00:22:48.710 --> 00:22:48.720 align:start position:0% ERC 4337 wallets uh for people who who 00:22:48.720 --> 00:22:51.710 align:start position:0% ERC 4337 wallets uh for people who who are<00:22:48.840> starting<00:22:49.240> now<00:22:50.159> like<00:22:51.159> you<00:22:51.279> you<00:22:51.440> probably 00:22:51.710 --> 00:22:51.720 align:start position:0% are starting now like you you probably 00:22:51.720 --> 00:22:55.430 align:start position:0% are starting now like you you probably don't<00:22:51.960> need<00:22:52.159> to<00:22:53.120> steer<00:22:53.559> them<00:22:53.760> into<00:22:54.080> using<00:22:54.440> 7702 00:22:55.430 --> 00:22:55.440 align:start position:0% don't need to steer them into using 7702 00:22:55.440 --> 00:22:58.149 align:start position:0% don't need to steer them into using 7702 if<00:22:55.600> they<00:22:55.880> are<00:22:56.159> newcomers<00:22:56.960> you<00:22:57.080> can<00:22:57.279> just<00:22:58.000> get 00:22:58.149 --> 00:22:58.159 align:start position:0% if they are newcomers you can just get 00:22:58.159 --> 00:23:01.070 align:start position:0% if they are newcomers you can just get them<00:22:58.520> to<00:22:58.760> deploy<00:22:59.279> an<00:22:59.880> upgradable<00:23:00.480> proxy<00:23:00.799> smart 00:23:01.070 --> 00:23:01.080 align:start position:0% them to deploy an upgradable proxy smart 00:23:01.080 --> 00:23:04.510 align:start position:0% them to deploy an upgradable proxy smart contract<00:23:01.600> wallet<00:23:02.600> and<00:23:03.039> uh<00:23:03.400> as<00:23:03.520> long<00:23:04.279> as<00:23:04.400> long 00:23:04.510 --> 00:23:04.520 align:start position:0% contract wallet and uh as long as long 00:23:04.520 --> 00:23:06.630 align:start position:0% contract wallet and uh as long as long as<00:23:04.600> it's<00:23:04.720> an<00:23:04.840> upgradable<00:23:05.320> proxy<00:23:06.000> they<00:23:06.159> can 00:23:06.630 --> 00:23:06.640 align:start position:0% as it's an upgradable proxy they can 00:23:06.640 --> 00:23:08.590 align:start position:0% as it's an upgradable proxy they can evolve<00:23:07.159> together<00:23:07.440> with<00:23:07.799> uh<00:23:08.279> account 00:23:08.590 --> 00:23:08.600 align:start position:0% evolve together with uh account 00:23:08.600 --> 00:23:11.870 align:start position:0% evolve together with uh account obstruction<00:23:09.480> like<00:23:09.840> versioning<00:23:10.440> and<00:23:10.799> uh<00:23:11.720> and 00:23:11.870 --> 00:23:11.880 align:start position:0% obstruction like versioning and uh and 00:23:11.880 --> 00:23:14.630 align:start position:0% obstruction like versioning and uh and all<00:23:12.080> that<00:23:12.799> uh 00:23:14.630 --> 00:23:14.640 align:start position:0% all that uh 00:23:14.640 --> 00:23:18.430 align:start position:0% all that uh right<00:23:15.640> what<00:23:16.200> do<00:23:16.320> you<00:23:16.440> mean<00:23:16.720> by<00:23:16.880> other<00:23:17.360> code<00:23:18.240> in 00:23:18.430 --> 00:23:18.440 align:start position:0% right what do you mean by other code in 00:23:18.440 --> 00:23:21.070 align:start position:0% right what do you mean by other code in Brackets<00:23:19.080> section<00:23:19.520> at 00:23:21.070 --> 00:23:21.080 align:start position:0% Brackets section at 00:23:21.080 --> 00:23:24.190 align:start position:0% Brackets section at 7701<00:23:22.080> yeah<00:23:22.360> uh<00:23:22.559> this<00:23:22.679> is<00:23:22.880> referring<00:23:23.360> to<00:23:23.960> this 00:23:24.190 --> 00:23:24.200 align:start position:0% 7701 yeah uh this is referring to this 00:23:24.200 --> 00:23:27.110 align:start position:0% 7701 yeah uh this is referring to this slide<00:23:24.559> I<00:23:24.720> I<00:23:24.840> can<00:23:25.000> I<00:23:25.080> don't<00:23:25.240> have<00:23:25.400> slides<00:23:25.840> uh<00:23:26.120> so 00:23:27.110 --> 00:23:27.120 align:start position:0% slide I I can I don't have slides uh so 00:23:27.120 --> 00:23:30.310 align:start position:0% slide I I can I don't have slides uh so uh<00:23:27.400> you<00:23:27.520> can<00:23:27.760> have<00:23:28.559> and<00:23:29.120> any<00:23:29.400> number<00:23:29.679> of<00:23:29.919> code 00:23:30.310 --> 00:23:30.320 align:start position:0% uh you can have and any number of code 00:23:30.320 --> 00:23:34.630 align:start position:0% uh you can have and any number of code sections<00:23:31.240> in<00:23:31.520> an<00:23:31.679> eof<00:23:32.640> account<00:23:33.640> uh<00:23:33.919> so<00:23:34.360> any 00:23:34.630 --> 00:23:34.640 align:start position:0% sections in an eof account uh so any 00:23:34.640 --> 00:23:37.390 align:start position:0% sections in an eof account uh so any code<00:23:34.919> that<00:23:35.080> does<00:23:35.240> not<00:23:35.559> have<00:23:35.919> a<00:23:36.480> role<00:23:37.080> assigned 00:23:37.390 --> 00:23:37.400 align:start position:0% code that does not have a role assigned 00:23:37.400 --> 00:23:40.230 align:start position:0% code that does not have a role assigned to<00:23:37.559> it<00:23:37.840> as<00:23:38.120> we<00:23:38.360> described<00:23:38.840> it<00:23:39.360> is<00:23:39.600> just<00:23:40.039> an 00:23:40.230 --> 00:23:40.240 align:start position:0% to it as we described it is just an 00:23:40.240 --> 00:23:43.350 align:start position:0% to it as we described it is just an external<00:23:40.679> code<00:23:40.960> so<00:23:41.120> it<00:23:41.279> can<00:23:41.440> be<00:23:41.600> called<00:23:42.360> by 00:23:43.350 --> 00:23:43.360 align:start position:0% external code so it can be called by 00:23:43.360 --> 00:23:46.029 align:start position:0% external code so it can be called by like<00:23:43.799> some<00:23:44.240> other<00:23:44.600> contracts<00:23:45.120> or<00:23:45.760> other 00:23:46.029 --> 00:23:46.039 align:start position:0% like some other contracts or other 00:23:46.039 --> 00:23:49.110 align:start position:0% like some other contracts or other addresses<00:23:46.520> can<00:23:46.679> just<00:23:47.120> call<00:23:47.440> into<00:23:47.760> this<00:23:48.120> code 00:23:49.110 --> 00:23:49.120 align:start position:0% addresses can just call into this code 00:23:49.120 --> 00:23:51.390 align:start position:0% addresses can just call into this code and<00:23:49.279> if<00:23:49.400> the<00:23:49.600> code<00:23:49.919> is<00:23:50.200> assigned<00:23:50.600> a<00:23:50.760> role<00:23:51.279> you 00:23:51.390 --> 00:23:51.400 align:start position:0% and if the code is assigned a role you 00:23:51.400 --> 00:23:54.350 align:start position:0% and if the code is assigned a role you cannot<00:23:51.799> call<00:23:52.120> into<00:23:52.559> this<00:23:52.760> code<00:23:53.520> it<00:23:53.720> has<00:23:53.840> to<00:23:54.039> be 00:23:54.350 --> 00:23:54.360 align:start position:0% cannot call into this code it has to be 00:23:54.360 --> 00:23:59.230 align:start position:0% cannot call into this code it has to be executed<00:23:55.000> as<00:23:55.279> part<00:23:56.200> of<00:23:56.880> a<00:23:57.880> EAP<00:23:58.480> 7701 00:23:59.230 --> 00:23:59.240 align:start position:0% executed as part of a EAP 7701 00:23:59.240 --> 00:24:01.909 align:start position:0% executed as part of a EAP 7701 transaction<00:24:00.240> right<00:24:00.480> it's<00:24:00.840> uh<00:24:01.240> so<00:24:01.559> this<00:24:01.679> is<00:24:01.760> the 00:24:01.909 --> 00:24:01.919 align:start position:0% transaction right it's uh so this is the 00:24:01.919 --> 00:24:04.430 align:start position:0% transaction right it's uh so this is the difference<00:24:02.200> between<00:24:02.520> like<00:24:02.880> other<00:24:03.240> code<00:24:03.880> and 00:24:04.430 --> 00:24:04.440 align:start position:0% difference between like other code and 00:24:04.440 --> 00:24:07.789 align:start position:0% difference between like other code and code<00:24:04.720> with<00:24:04.880> an<00:24:05.400> assigned<00:24:06.400> purpose<00:24:07.400> in<00:24:07.559> terms 00:24:07.789 --> 00:24:07.799 align:start position:0% code with an assigned purpose in terms 00:24:07.799 --> 00:24:09.549 align:start position:0% code with an assigned purpose in terms of<00:24:07.960> account 00:24:09.549 --> 00:24:09.559 align:start position:0% of account 00:24:09.559 --> 00:24:11.990 align:start position:0% of account obstruction<00:24:10.559> now<00:24:10.880> the<00:24:11.039> last 00:24:11.990 --> 00:24:12.000 align:start position:0% obstruction now the last 00:24:12.000 --> 00:24:14.549 align:start position:0% obstruction now the last question<00:24:13.000> what's<00:24:13.240> the<00:24:13.440> point<00:24:13.720> of<00:24:13.919> separating 00:24:14.549 --> 00:24:14.559 align:start position:0% question what's the point of separating 00:24:14.559 --> 00:24:16.669 align:start position:0% question what's the point of separating validation<00:24:15.120> and<00:24:15.400> execution<00:24:15.919> in<00:24:16.080> ethereum's 00:24:16.669 --> 00:24:16.679 align:start position:0% validation and execution in ethereum's 00:24:16.679 --> 00:24:18.990 align:start position:0% validation and execution in ethereum's account<00:24:17.000> obstruction<00:24:17.960> if<00:24:18.240> conflicts<00:24:18.760> can 00:24:18.990 --> 00:24:19.000 align:start position:0% account obstruction if conflicts can 00:24:19.000 --> 00:24:22.110 align:start position:0% account obstruction if conflicts can still<00:24:19.400> arise<00:24:19.919> during<00:24:20.520> execution<00:24:21.520> even<00:24:21.799> after 00:24:22.110 --> 00:24:22.120 align:start position:0% still arise during execution even after 00:24:22.120 --> 00:24:24.870 align:start position:0% still arise during execution even after validation<00:24:22.760> under<00:24:23.159> restricted<00:24:23.720> rules<00:24:24.480> yeah 00:24:24.870 --> 00:24:24.880 align:start position:0% validation under restricted rules yeah 00:24:24.880 --> 00:24:28.070 align:start position:0% validation under restricted rules yeah great<00:24:25.200> question<00:24:25.600> like<00:24:26.360> uh<00:24:26.640> the<00:24:26.880> problem<00:24:27.240> is<00:24:27.919> if 00:24:28.070 --> 00:24:28.080 align:start position:0% great question like uh the problem is if 00:24:28.080 --> 00:24:30.669 align:start position:0% great question like uh the problem is if the<00:24:28.559> execution<00:24:29.360> conflicts<00:24:30.159> uh<00:24:30.320> with<00:24:30.480> each 00:24:30.669 --> 00:24:30.679 align:start position:0% the execution conflicts uh with each 00:24:30.679 --> 00:24:34.110 align:start position:0% the execution conflicts uh with each other<00:24:31.440> you<00:24:31.600> can<00:24:32.200> get<00:24:33.000> a<00:24:33.159> state<00:24:33.399> you<00:24:33.520> didn't 00:24:34.110 --> 00:24:34.120 align:start position:0% other you can get a state you didn't 00:24:34.120 --> 00:24:35.909 align:start position:0% other you can get a state you didn't initially<00:24:34.600> want<00:24:34.880> for<00:24:35.000> example<00:24:35.279> you<00:24:35.360> can<00:24:35.600> get<00:24:35.720> a 00:24:35.909 --> 00:24:35.919 align:start position:0% initially want for example you can get a 00:24:35.919 --> 00:24:37.630 align:start position:0% initially want for example you can get a transaction<00:24:36.360> to<00:24:36.520> revert<00:24:37.320> but<00:24:37.480> the 00:24:37.630 --> 00:24:37.640 align:start position:0% transaction to revert but the 00:24:37.640 --> 00:24:40.269 align:start position:0% transaction to revert but the transaction<00:24:38.120> is<00:24:38.279> still<00:24:38.760> valid<00:24:39.760> and<00:24:40.000> another 00:24:40.269 --> 00:24:40.279 align:start position:0% transaction is still valid and another 00:24:40.279 --> 00:24:43.110 align:start position:0% transaction is still valid and another thing<00:24:40.440> is<00:24:40.679> execution<00:24:41.480> is<00:24:42.039> not<00:24:42.360> limited<00:24:42.919> not 00:24:43.110 --> 00:24:43.120 align:start position:0% thing is execution is not limited not 00:24:43.120 --> 00:24:45.710 align:start position:0% thing is execution is not limited not sendbox<00:24:43.600> it<00:24:43.919> can<00:24:44.080> be<00:24:44.399> a<00:24:44.559> 20<00:24:44.840> million<00:24:45.200> G 00:24:45.710 --> 00:24:45.720 align:start position:0% sendbox it can be a 20 million G 00:24:45.720 --> 00:24:47.950 align:start position:0% sendbox it can be a 20 million G operation<00:24:46.720> and<00:24:46.919> it<00:24:47.080> can<00:24:47.320> write<00:24:47.640> all<00:24:47.840> the 00:24:47.950 --> 00:24:47.960 align:start position:0% operation and it can write all the 00:24:47.960 --> 00:24:50.669 align:start position:0% operation and it can write all the storage<00:24:48.320> in<00:24:48.440> the<00:24:48.559> world<00:24:49.480> uh<00:24:49.640> validation<00:24:50.279> is 00:24:50.669 --> 00:24:50.679 align:start position:0% storage in the world uh validation is 00:24:50.679 --> 00:24:53.830 align:start position:0% storage in the world uh validation is limited<00:24:51.279> and<00:24:51.520> sandboxed<00:24:52.440> so<00:24:52.600> we<00:24:52.760> extract<00:24:53.679> all 00:24:53.830 --> 00:24:53.840 align:start position:0% limited and sandboxed so we extract all 00:24:53.840 --> 00:24:55.710 align:start position:0% limited and sandboxed so we extract all the<00:24:54.039> validations<00:24:54.760> because<00:24:55.039> we<00:24:55.200> assume<00:24:55.600> they 00:24:55.710 --> 00:24:55.720 align:start position:0% the validations because we assume they 00:24:55.720 --> 00:24:58.710 align:start position:0% the validations because we assume they are<00:24:56.399> small<00:24:56.919> functions<00:24:57.559> relatively<00:24:58.200> like<00:24:58.640> I 00:24:58.710 --> 00:24:58.720 align:start position:0% are small functions relatively like I 00:24:58.720 --> 00:25:00.909 align:start position:0% are small functions relatively like I don't<00:24:58.880> want<00:24:59.000> to<00:24:59.120> say<00:24:59.360> pure<00:24:59.919> but<00:25:00.360> clean 00:25:00.909 --> 00:25:00.919 align:start position:0% don't want to say pure but clean 00:25:00.919 --> 00:25:04.070 align:start position:0% don't want to say pure but clean functions<00:25:01.799> that<00:25:01.960> only<00:25:02.279> access<00:25:02.760> accounts<00:25:03.240> own 00:25:04.070 --> 00:25:04.080 align:start position:0% functions that only access accounts own 00:25:04.080 --> 00:25:09.389 align:start position:0% functions that only access accounts own storage<00:25:05.240> and<00:25:06.240> if<00:25:06.760> they<00:25:07.080> were<00:25:07.440> to<00:25:08.240> collide<00:25:09.240> that 00:25:09.389 --> 00:25:09.399 align:start position:0% storage and if they were to collide that 00:25:09.399 --> 00:25:11.909 align:start position:0% storage and if they were to collide that would<00:25:10.080> make<00:25:10.640> block<00:25:11.039> invalid<00:25:11.520> the<00:25:11.640> difference 00:25:11.909 --> 00:25:11.919 align:start position:0% would make block invalid the difference 00:25:11.919 --> 00:25:14.070 align:start position:0% would make block invalid the difference between<00:25:12.159> the<00:25:12.760> H<00:25:13.039> reverted<00:25:13.559> transaction<00:25:13.919> in 00:25:14.070 --> 00:25:14.080 align:start position:0% between the H reverted transaction in 00:25:14.080 --> 00:25:15.350 align:start position:0% between the H reverted transaction in block<00:25:14.360> and<00:25:14.480> invalid<00:25:14.880> block<00:25:15.080> is<00:25:15.200> the 00:25:15.350 --> 00:25:15.360 align:start position:0% block and invalid block is the 00:25:15.360 --> 00:25:17.470 align:start position:0% block and invalid block is the difference<00:25:15.720> between<00:25:16.440> a<00:25:16.640> block<00:25:16.880> Builder<00:25:17.200> being 00:25:17.470 --> 00:25:17.480 align:start position:0% difference between a block Builder being 00:25:17.480 --> 00:25:20.950 align:start position:0% difference between a block Builder being dosed<00:25:18.480> and<00:25:18.720> somebody<00:25:19.120> having<00:25:19.360> to<00:25:20.279> redo<00:25:20.720> his 00:25:20.950 --> 00:25:20.960 align:start position:0% dosed and somebody having to redo his 00:25:20.960 --> 00:25:23.840 align:start position:0% dosed and somebody having to redo his action