WEBVTT Kind: captions Language: en 00:00:01.010 --> 00:00:12.430 align:start position:0% [Music] 00:00:12.430 --> 00:00:12.440 align:start position:0% 00:00:12.440 --> 00:00:14.910 align:start position:0% hello<00:00:13.440> thanks<00:00:13.639> a<00:00:13.759> lot<00:00:13.920> for<00:00:14.120> coming<00:00:14.599> I'm<00:00:14.719> very 00:00:14.910 --> 00:00:14.920 align:start position:0% hello thanks a lot for coming I'm very 00:00:14.920 --> 00:00:16.950 align:start position:0% hello thanks a lot for coming I'm very happy<00:00:15.120> to<00:00:15.240> see<00:00:15.599> so<00:00:15.759> many<00:00:16.000> of<00:00:16.119> you<00:00:16.400> here<00:00:16.640> tonight 00:00:16.950 --> 00:00:16.960 align:start position:0% happy to see so many of you here tonight 00:00:16.960 --> 00:00:19.269 align:start position:0% happy to see so many of you here tonight I<00:00:17.080> know<00:00:17.199> it's<00:00:17.320> been<00:00:17.439> a<00:00:17.560> long<00:00:17.840> day<00:00:18.400> and<00:00:19.000> this<00:00:19.160> is 00:00:19.269 --> 00:00:19.279 align:start position:0% I know it's been a long day and this is 00:00:19.279 --> 00:00:21.470 align:start position:0% I know it's been a long day and this is the<00:00:19.520> last<00:00:19.760> two<00:00:20.039> talks<00:00:20.400> so<00:00:20.640> thanks<00:00:20.840> for<00:00:21.119> staying 00:00:21.470 --> 00:00:21.480 align:start position:0% the last two talks so thanks for staying 00:00:21.480 --> 00:00:24.189 align:start position:0% the last two talks so thanks for staying here<00:00:22.240> so<00:00:22.600> my<00:00:22.720> name<00:00:22.880> is<00:00:23.039> Peter<00:00:23.560> I'm<00:00:23.680> a<00:00:23.840> pral 00:00:24.189 --> 00:00:24.199 align:start position:0% here so my name is Peter I'm a pral 00:00:24.199 --> 00:00:25.750 align:start position:0% here so my name is Peter I'm a pral engineer<00:00:24.560> at<00:00:24.720> scroll<00:00:25.119> and<00:00:25.240> today<00:00:25.439> I<00:00:25.519> want<00:00:25.640> to 00:00:25.750 --> 00:00:25.760 align:start position:0% engineer at scroll and today I want to 00:00:25.760 --> 00:00:27.390 align:start position:0% engineer at scroll and today I want to tell<00:00:25.880> you<00:00:26.039> about<00:00:26.560> a<00:00:26.720> recent<00:00:27.039> rollup 00:00:27.390 --> 00:00:27.400 align:start position:0% tell you about a recent rollup 00:00:27.400 --> 00:00:29.669 align:start position:0% tell you about a recent rollup Improvement<00:00:27.920> proposal<00:00:28.560> that<00:00:28.640> is<00:00:28.800> called<00:00:29.000> l1s 00:00:29.669 --> 00:00:29.679 align:start position:0% Improvement proposal that is called l1s 00:00:29.679 --> 00:00:31.509 align:start position:0% Improvement proposal that is called l1s load 00:00:31.509 --> 00:00:31.519 align:start position:0% load 00:00:31.519 --> 00:00:32.910 align:start position:0% load so<00:00:31.679> let's<00:00:31.880> start<00:00:32.119> by<00:00:32.279> talking<00:00:32.480> about<00:00:32.719> what<00:00:32.800> is 00:00:32.910 --> 00:00:32.920 align:start position:0% so let's start by talking about what is 00:00:32.920 --> 00:00:34.030 align:start position:0% so let's start by talking about what is A1<00:00:33.280> s 00:00:34.030 --> 00:00:34.040 align:start position:0% A1 s 00:00:34.040 --> 00:00:36.549 align:start position:0% A1 s load<00:00:35.040> essentially<00:00:35.600> A1<00:00:35.960> s<00:00:36.160> load<00:00:36.360> is<00:00:36.440> a 00:00:36.549 --> 00:00:36.559 align:start position:0% load essentially A1 s load is a 00:00:36.559 --> 00:00:39.030 align:start position:0% load essentially A1 s load is a pre-compile<00:00:37.399> that<00:00:37.640> is<00:00:37.800> deployed<00:00:38.200> on<00:00:38.280> l2s<00:00:38.879> like 00:00:39.030 --> 00:00:39.040 align:start position:0% pre-compile that is deployed on l2s like 00:00:39.040 --> 00:00:41.709 align:start position:0% pre-compile that is deployed on l2s like scroll<00:00:39.640> and<00:00:39.800> other<00:00:39.960> l2s<00:00:40.920> that<00:00:41.079> you<00:00:41.239> as<00:00:41.320> a<00:00:41.480> de 00:00:41.709 --> 00:00:41.719 align:start position:0% scroll and other l2s that you as a de 00:00:41.719 --> 00:00:44.229 align:start position:0% scroll and other l2s that you as a de developer<00:00:42.320> who<00:00:42.480> deploys<00:00:42.840> your<00:00:43.000> dep<00:00:43.239> on<00:00:43.320> L2<00:00:44.120> can 00:00:44.229 --> 00:00:44.239 align:start position:0% developer who deploys your dep on L2 can 00:00:44.239 --> 00:00:46.990 align:start position:0% developer who deploys your dep on L2 can use<00:00:44.440> to<00:00:44.559> read<00:00:44.840> State<00:00:45.120> directory<00:00:45.600> from 00:00:46.990 --> 00:00:47.000 align:start position:0% use to read State directory from 00:00:47.000 --> 00:00:50.150 align:start position:0% use to read State directory from L1<00:00:48.000> so<00:00:48.800> if<00:00:48.960> there's<00:00:49.160> any<00:00:49.360> solidity<00:00:49.840> devs 00:00:50.150 --> 00:00:50.160 align:start position:0% L1 so if there's any solidity devs 00:00:50.160 --> 00:00:52.990 align:start position:0% L1 so if there's any solidity devs around<00:00:50.480> here<00:00:50.719> this<00:00:50.840> is<00:00:51.000> how<00:00:51.120> it<00:00:51.239> looks<00:00:52.160> so<00:00:52.879> this 00:00:52.990 --> 00:00:53.000 align:start position:0% around here this is how it looks so this 00:00:53.000 --> 00:00:54.389 align:start position:0% around here this is how it looks so this is<00:00:53.160> the<00:00:53.280> contract<00:00:53.640> that<00:00:53.719> you<00:00:53.800> would<00:00:54.000> Deploy<00:00:54.280> on 00:00:54.389 --> 00:00:54.399 align:start position:0% is the contract that you would Deploy on 00:00:54.399 --> 00:00:56.910 align:start position:0% is the contract that you would Deploy on L2<00:00:55.320> it's<00:00:55.520> very<00:00:55.719> simple<00:00:56.239> you<00:00:56.320> can<00:00:56.520> just<00:00:56.719> take 00:00:56.910 --> 00:00:56.920 align:start position:0% L2 it's very simple you can just take 00:00:56.920 --> 00:00:59.029 align:start position:0% L2 it's very simple you can just take the<00:00:57.079> L1<00:00:57.559> contract<00:00:57.960> address<00:00:58.320> you<00:00:58.440> can<00:00:58.719> provide 00:00:59.029 --> 00:00:59.039 align:start position:0% the L1 contract address you can provide 00:00:59.039 --> 00:01:02.270 align:start position:0% the L1 contract address you can provide one<00:00:59.320> two<00:00:59.600> or<00:00:59.719> up<00:01:00.039> to<00:01:00.239> five<00:01:00.559> storage<00:01:01.160> Keys<00:01:02.000> you 00:01:02.270 --> 00:01:02.280 align:start position:0% one two or up to five storage Keys you 00:01:02.280 --> 00:01:04.710 align:start position:0% one two or up to five storage Keys you encode<00:01:02.680> it<00:01:03.039> and<00:01:03.160> then<00:01:03.280> call<00:01:03.519> this<00:01:03.720> precompile 00:01:04.710 --> 00:01:04.720 align:start position:0% encode it and then call this precompile 00:01:04.720 --> 00:01:06.510 align:start position:0% encode it and then call this precompile and<00:01:04.879> then<00:01:05.360> at<00:01:05.479> the<00:01:05.600> end<00:01:05.760> you<00:01:05.880> get<00:01:06.040> the<00:01:06.159> result 00:01:06.510 --> 00:01:06.520 align:start position:0% and then at the end you get the result 00:01:06.520 --> 00:01:08.270 align:start position:0% and then at the end you get the result back<00:01:06.680> that<00:01:06.799> you<00:01:06.920> can<00:01:07.040> decode<00:01:07.400> and<00:01:07.600> use<00:01:08.000> in<00:01:08.119> your 00:01:08.270 --> 00:01:08.280 align:start position:0% back that you can decode and use in your 00:01:08.280 --> 00:01:09.310 align:start position:0% back that you can decode and use in your application 00:01:09.310 --> 00:01:09.320 align:start position:0% application 00:01:09.320 --> 00:01:11.710 align:start position:0% application logic<00:01:10.320> uh<00:01:10.560> what<00:01:10.720> happens<00:01:11.000> under<00:01:11.240> the<00:01:11.360> hood<00:01:11.640> is 00:01:11.710 --> 00:01:11.720 align:start position:0% logic uh what happens under the hood is 00:01:11.720 --> 00:01:14.070 align:start position:0% logic uh what happens under the hood is that<00:01:11.880> the<00:01:11.960> sequencer<00:01:12.479> fetches<00:01:13.240> this<00:01:13.439> data<00:01:13.840> for 00:01:14.070 --> 00:01:14.080 align:start position:0% that the sequencer fetches this data for 00:01:14.080 --> 00:01:16.749 align:start position:0% that the sequencer fetches this data for you<00:01:14.479> through<00:01:14.720> adjacent<00:01:15.119> RPC 00:01:16.749 --> 00:01:16.759 align:start position:0% you through adjacent RPC 00:01:16.759 --> 00:01:19.710 align:start position:0% you through adjacent RPC request<00:01:17.759> or<00:01:18.000> it<00:01:18.119> can<00:01:18.320> even<00:01:18.560> look<00:01:19.200> uh<00:01:19.320> as<00:01:19.439> simple 00:01:19.710 --> 00:01:19.720 align:start position:0% request or it can even look uh as simple 00:01:19.720 --> 00:01:21.190 align:start position:0% request or it can even look uh as simple as<00:01:19.880> this<00:01:20.079> if<00:01:20.320> if<00:01:20.400> you<00:01:20.520> provide<00:01:20.799> some<00:01:20.960> higher 00:01:21.190 --> 00:01:21.200 align:start position:0% as this if if you provide some higher 00:01:21.200 --> 00:01:23.190 align:start position:0% as this if if you provide some higher level<00:01:21.840> libraries<00:01:22.320> you<00:01:22.560> you<00:01:22.640> know<00:01:22.799> just<00:01:22.960> call 00:01:23.190 --> 00:01:23.200 align:start position:0% level libraries you you know just call 00:01:23.200 --> 00:01:26.510 align:start position:0% level libraries you you know just call the<00:01:23.320> ls<00:01:23.720> load<00:01:24.520> uh<00:01:24.640> read<00:01:24.880> onsite<00:01:25.320> intent<00:01:26.320> there 00:01:26.510 --> 00:01:26.520 align:start position:0% the ls load uh read onsite intent there 00:01:26.520 --> 00:01:30.590 align:start position:0% the ls load uh read onsite intent there you<00:01:26.600> can<00:01:26.759> use<00:01:26.920> the<00:01:27.079> data<00:01:27.320> in<00:01:27.439> your<00:01:27.600> L2<00:01:28.000> contract 00:01:30.590 --> 00:01:30.600 align:start position:0% you can use the data in your L2 contract 00:01:30.600 --> 00:01:33.069 align:start position:0% you can use the data in your L2 contract now<00:01:30.840> today<00:01:31.840> today<00:01:32.119> at<00:01:32.280> the<00:01:32.399> venue<00:01:32.680> I<00:01:32.799> passed 00:01:33.069 --> 00:01:33.079 align:start position:0% now today today at the venue I passed 00:01:33.079 --> 00:01:34.510 align:start position:0% now today today at the venue I passed this<00:01:33.200> door<00:01:33.399> and<00:01:33.479> I<00:01:33.600> like<00:01:33.759> this<00:01:33.920> kind<00:01:34.040> of<00:01:34.159> as<00:01:34.280> a 00:01:34.510 --> 00:01:34.520 align:start position:0% this door and I like this kind of as a 00:01:34.520 --> 00:01:37.069 align:start position:0% this door and I like this kind of as a metaphor<00:01:35.520> uh<00:01:35.600> so<00:01:35.799> Alan<00:01:36.079> EST<00:01:36.399> is<00:01:36.640> essentially 00:01:37.069 --> 00:01:37.079 align:start position:0% metaphor uh so Alan EST is essentially 00:01:37.079 --> 00:01:39.270 align:start position:0% metaphor uh so Alan EST is essentially about<00:01:37.360> keeping<00:01:37.640> the<00:01:37.759> door<00:01:38.040> to<00:01:38.200> storage<00:01:38.600> open 00:01:39.270 --> 00:01:39.280 align:start position:0% about keeping the door to storage open 00:01:39.280 --> 00:01:42.310 align:start position:0% about keeping the door to storage open to<00:01:39.439> your<00:01:39.600> L2 00:01:42.310 --> 00:01:42.320 align:start position:0% to your L2 00:01:42.320 --> 00:01:45.190 align:start position:0% to your L2 dep<00:01:43.320> before<00:01:43.560> we<00:01:43.680> go<00:01:43.840> into<00:01:44.040> the<00:01:44.200> implementation 00:01:45.190 --> 00:01:45.200 align:start position:0% dep before we go into the implementation 00:01:45.200 --> 00:01:46.950 align:start position:0% dep before we go into the implementation uh<00:01:45.320> let<00:01:45.479> me<00:01:45.759> highlight<00:01:46.119> some<00:01:46.240> use<00:01:46.520> cases<00:01:46.799> that 00:01:46.950 --> 00:01:46.960 align:start position:0% uh let me highlight some use cases that 00:01:46.960 --> 00:01:48.630 align:start position:0% uh let me highlight some use cases that we've<00:01:47.479> discovered<00:01:48.159> because<00:01:48.360> we've<00:01:48.520> been 00:01:48.630 --> 00:01:48.640 align:start position:0% we've discovered because we've been 00:01:48.640 --> 00:01:50.109 align:start position:0% we've discovered because we've been running<00:01:48.920> this<00:01:49.079> through<00:01:49.320> some<00:01:49.520> hackathons<00:01:50.000> in 00:01:50.109 --> 00:01:50.119 align:start position:0% running this through some hackathons in 00:01:50.119 --> 00:01:52.069 align:start position:0% running this through some hackathons in the<00:01:50.240> last<00:01:50.360> few<00:01:50.600> months<00:01:51.600> uh<00:01:51.719> one<00:01:51.840> of<00:01:51.960> my 00:01:52.069 --> 00:01:52.079 align:start position:0% the last few months uh one of my 00:01:52.079 --> 00:01:54.230 align:start position:0% the last few months uh one of my favorites<00:01:52.479> is<00:01:52.680> this<00:01:53.000> uh<00:01:53.119> cross<00:01:53.399> layer<00:01:53.680> tornado 00:01:54.230 --> 00:01:54.240 align:start position:0% favorites is this uh cross layer tornado 00:01:54.240 --> 00:01:56.429 align:start position:0% favorites is this uh cross layer tornado cach<00:01:54.600> imagine<00:01:54.960> that<00:01:55.079> you<00:01:55.240> can<00:01:55.880> deposit<00:01:56.240> some 00:01:56.429 --> 00:01:56.439 align:start position:0% cach imagine that you can deposit some 00:01:56.439 --> 00:01:59.149 align:start position:0% cach imagine that you can deposit some tokens<00:01:56.759> into<00:01:56.960> the<00:01:57.079> shielded<00:01:57.759> set<00:01:58.439> on<00:01:58.600> L1<00:01:59.079> and 00:01:59.149 --> 00:01:59.159 align:start position:0% tokens into the shielded set on L1 and 00:01:59.159 --> 00:02:01.990 align:start position:0% tokens into the shielded set on L1 and then<00:01:59.280> you<00:01:59.360> can<00:01:59.479> withdraw<00:02:00.119> L2<00:02:01.119> uh<00:02:01.360> very<00:02:01.560> simless 00:02:01.990 --> 00:02:02.000 align:start position:0% then you can withdraw L2 uh very simless 00:02:02.000 --> 00:02:02.870 align:start position:0% then you can withdraw L2 uh very simless user 00:02:02.870 --> 00:02:02.880 align:start position:0% user 00:02:02.880 --> 00:02:05.350 align:start position:0% user experience<00:02:03.880> or<00:02:04.119> imagine<00:02:04.520> that<00:02:04.640> you<00:02:05.000> deploy 00:02:05.350 --> 00:02:05.360 align:start position:0% experience or imagine that you deploy 00:02:05.360 --> 00:02:07.749 align:start position:0% experience or imagine that you deploy your<00:02:05.560> D<00:02:05.759> on<00:02:05.880> an<00:02:06.000> L2<00:02:06.439> that<00:02:06.560> doesn't<00:02:06.799> have<00:02:06.960> enss 00:02:07.749 --> 00:02:07.759 align:start position:0% your D on an L2 that doesn't have enss 00:02:07.759 --> 00:02:10.790 align:start position:0% your D on an L2 that doesn't have enss in<00:02:08.000> this<00:02:08.160> case<00:02:08.560> you<00:02:08.720> could<00:02:09.000> just<00:02:09.440> uh<00:02:09.599> use<00:02:09.879> i1<00:02:10.520> to 00:02:10.790 --> 00:02:10.800 align:start position:0% in this case you could just uh use i1 to 00:02:10.800 --> 00:02:14.390 align:start position:0% in this case you could just uh use i1 to directly<00:02:11.160> look<00:02:11.440> up<00:02:11.840> uh<00:02:12.000> names<00:02:12.400> from<00:02:12.599> the 00:02:14.390 --> 00:02:14.400 align:start position:0% directly look up uh names from the 00:02:14.400 --> 00:02:17.790 align:start position:0% directly look up uh names from the i1s<00:02:15.400> another<00:02:15.720> example<00:02:16.200> is<00:02:16.400> defi<00:02:17.319> so<00:02:17.480> you<00:02:17.599> could 00:02:17.790 --> 00:02:17.800 align:start position:0% i1s another example is defi so you could 00:02:17.800 --> 00:02:19.830 align:start position:0% i1s another example is defi so you could create<00:02:18.480> uh<00:02:18.599> a<00:02:18.720> defi<00:02:19.120> dep<00:02:19.480> where<00:02:19.640> you<00:02:19.720> can 00:02:19.830 --> 00:02:19.840 align:start position:0% create uh a defi dep where you can 00:02:19.840 --> 00:02:22.630 align:start position:0% create uh a defi dep where you can borrow<00:02:20.120> on<00:02:20.519> L2<00:02:21.519> d<00:02:21.800> by<00:02:21.959> directly<00:02:22.319> using 00:02:22.630 --> 00:02:22.640 align:start position:0% borrow on L2 d by directly using 00:02:22.640 --> 00:02:24.550 align:start position:0% borrow on L2 d by directly using collateral<00:02:23.080> on<00:02:23.160> L1<00:02:23.599> without<00:02:24.000> bridging<00:02:24.360> this 00:02:24.550 --> 00:02:24.560 align:start position:0% collateral on L1 without bridging this 00:02:24.560 --> 00:02:25.830 align:start position:0% collateral on L1 without bridging this from<00:02:24.680> L1<00:02:25.000> to 00:02:25.830 --> 00:02:25.840 align:start position:0% from L1 to 00:02:25.840 --> 00:02:28.350 align:start position:0% from L1 to L2<00:02:26.840> and<00:02:27.000> for<00:02:27.239> account<00:02:27.519> obstruction<00:02:27.920> wallets 00:02:28.350 --> 00:02:28.360 align:start position:0% L2 and for account obstruction wallets 00:02:28.360 --> 00:02:30.550 align:start position:0% L2 and for account obstruction wallets you<00:02:29.120> might<00:02:29.280> have<00:02:29.400> heard<00:02:29.599> about<00:02:29.920> key<00:02:30.120> stores 00:02:30.550 --> 00:02:30.560 align:start position:0% you might have heard about key stores 00:02:30.560 --> 00:02:32.190 align:start position:0% you might have heard about key stores the<00:02:30.680> idea<00:02:30.920> is<00:02:31.080> that<00:02:31.440> you<00:02:31.599> manage<00:02:31.879> all<00:02:32.040> your 00:02:32.190 --> 00:02:32.200 align:start position:0% the idea is that you manage all your 00:02:32.200 --> 00:02:34.229 align:start position:0% the idea is that you manage all your keys<00:02:32.400> on<00:02:32.560> one<00:02:32.680> chain<00:02:32.959> let's<00:02:33.120> say<00:02:33.239> on<00:02:33.360> i1<00:02:34.120> and 00:02:34.229 --> 00:02:34.239 align:start position:0% keys on one chain let's say on i1 and 00:02:34.239 --> 00:02:35.670 align:start position:0% keys on one chain let's say on i1 and when<00:02:34.360> you<00:02:34.480> update<00:02:34.800> your<00:02:34.920> keys<00:02:35.239> you<00:02:35.360> add<00:02:35.519> or 00:02:35.670 --> 00:02:35.680 align:start position:0% when you update your keys you add or 00:02:35.680 --> 00:02:38.190 align:start position:0% when you update your keys you add or delete<00:02:35.920> a<00:02:36.080> key<00:02:37.000> uh<00:02:37.319> this<00:02:37.519> update<00:02:37.920> is 00:02:38.190 --> 00:02:38.200 align:start position:0% delete a key uh this update is 00:02:38.200 --> 00:02:40.070 align:start position:0% delete a key uh this update is automatically<00:02:38.800> propagated<00:02:39.319> to<00:02:39.519> all<00:02:39.879> your 00:02:40.070 --> 00:02:40.080 align:start position:0% automatically propagated to all your 00:02:40.080 --> 00:02:41.830 align:start position:0% automatically propagated to all your Wallets<00:02:40.360> on<00:02:40.480> all<00:02:40.599> the 00:02:41.830 --> 00:02:41.840 align:start position:0% Wallets on all the 00:02:41.840 --> 00:02:44.750 align:start position:0% Wallets on all the chains<00:02:42.840> so<00:02:43.040> this<00:02:43.239> last<00:02:43.640> example<00:02:44.080> would<00:02:44.519> look 00:02:44.750 --> 00:02:44.760 align:start position:0% chains so this last example would look 00:02:44.760 --> 00:02:47.229 align:start position:0% chains so this last example would look like<00:02:44.959> this<00:02:45.800> uh<00:02:46.120> in<00:02:46.239> the<00:02:46.360> L1<00:02:46.720> contract<00:02:47.120> you 00:02:47.229 --> 00:02:47.239 align:start position:0% like this uh in the L1 contract you 00:02:47.239 --> 00:02:48.710 align:start position:0% like this uh in the L1 contract you would<00:02:47.440> most<00:02:47.640> likely<00:02:47.959> have<00:02:48.239> some<00:02:48.400> kind<00:02:48.519> of<00:02:48.599> a 00:02:48.710 --> 00:02:48.720 align:start position:0% would most likely have some kind of a 00:02:48.720 --> 00:02:50.229 align:start position:0% would most likely have some kind of a mapping<00:02:49.120> where<00:02:49.239> you<00:02:49.400> store<00:02:49.680> the<00:02:49.800> authorized 00:02:50.229 --> 00:02:50.239 align:start position:0% mapping where you store the authorized 00:02:50.239 --> 00:02:53.149 align:start position:0% mapping where you store the authorized signers<00:02:51.239> and<00:02:51.360> on<00:02:51.519> L2<00:02:52.200> it's<00:02:52.400> very<00:02:52.599> simple<00:02:52.920> you 00:02:53.149 --> 00:02:53.159 align:start position:0% signers and on L2 it's very simple you 00:02:53.159 --> 00:02:54.910 align:start position:0% signers and on L2 it's very simple you just<00:02:53.680> calculate<00:02:54.200> the<00:02:54.280> storage<00:02:54.560> slot<00:02:54.840> that 00:02:54.910 --> 00:02:54.920 align:start position:0% just calculate the storage slot that 00:02:54.920 --> 00:02:56.470 align:start position:0% just calculate the storage slot that you're<00:02:55.120> interested<00:02:55.480> in<00:02:56.000> and<00:02:56.080> then<00:02:56.200> you<00:02:56.319> can 00:02:56.470 --> 00:02:56.480 align:start position:0% you're interested in and then you can 00:02:56.480 --> 00:02:59.030 align:start position:0% you're interested in and then you can call<00:02:57.000> l1s<00:02:57.480> load<00:02:57.640> read<00:02:57.879> bull<00:02:58.440> the<00:02:58.560> sequencer 00:02:59.030 --> 00:02:59.040 align:start position:0% call l1s load read bull the sequencer 00:02:59.040 --> 00:03:01.190 align:start position:0% call l1s load read bull the sequencer fet<00:02:59.360> is<00:02:59.440> the<00:02:59.519> data<00:02:59.879> for<00:03:00.000> you<00:03:00.159> and<00:03:00.319> you<00:03:00.480> can 00:03:01.190 --> 00:03:01.200 align:start position:0% fet is the data for you and you can 00:03:01.200 --> 00:03:02.949 align:start position:0% fet is the data for you and you can decide<00:03:01.599> in<00:03:01.720> your<00:03:01.879> L2<00:03:02.200> wallet<00:03:02.560> whether<00:03:02.800> this 00:03:02.949 --> 00:03:02.959 align:start position:0% decide in your L2 wallet whether this 00:03:02.959 --> 00:03:06.270 align:start position:0% decide in your L2 wallet whether this signer<00:03:03.280> is<00:03:03.440> authorized<00:03:03.959> or<00:03:04.120> not<00:03:04.799> so<00:03:05.599> a<00:03:06.080> Lo 00:03:06.270 --> 00:03:06.280 align:start position:0% signer is authorized or not so a Lo 00:03:06.280 --> 00:03:08.670 align:start position:0% signer is authorized or not so a Lo makes<00:03:06.519> this<00:03:06.760> very<00:03:06.959> easy<00:03:07.159> to<00:03:07.360> implement<00:03:08.319> and 00:03:08.670 --> 00:03:08.680 align:start position:0% makes this very easy to implement and 00:03:08.680 --> 00:03:11.550 align:start position:0% makes this very easy to implement and also<00:03:08.920> very<00:03:09.080> easy<00:03:09.280> to<00:03:09.440> use<00:03:09.640> as<00:03:09.760> a<00:03:09.959> as<00:03:10.040> a 00:03:11.550 --> 00:03:11.560 align:start position:0% also very easy to use as a as a 00:03:11.560 --> 00:03:14.309 align:start position:0% also very easy to use as a as a developer<00:03:12.560> uh<00:03:12.720> now<00:03:12.920> that<00:03:13.000> you<00:03:13.120> have<00:03:13.280> a<00:03:13.760> general 00:03:14.309 --> 00:03:14.319 align:start position:0% developer uh now that you have a general 00:03:14.319 --> 00:03:15.670 align:start position:0% developer uh now that you have a general understanding<00:03:14.519> of<00:03:14.640> what<00:03:14.760> is<00:03:14.879> a<00:03:15.319> load<00:03:15.519> and<00:03:15.599> what 00:03:15.670 --> 00:03:15.680 align:start position:0% understanding of what is a load and what 00:03:15.680 --> 00:03:17.550 align:start position:0% understanding of what is a load and what are<00:03:15.799> some<00:03:15.920> use<00:03:16.159> cases<00:03:16.440> let<00:03:16.560> me<00:03:16.680> talk<00:03:16.920> about<00:03:17.400> why 00:03:17.550 --> 00:03:17.560 align:start position:0% are some use cases let me talk about why 00:03:17.560 --> 00:03:19.030 align:start position:0% are some use cases let me talk about why do<00:03:17.680> I<00:03:17.799> think<00:03:18.080> we<00:03:18.280> need<00:03:18.400> to<00:03:18.599> provide<00:03:18.840> this<00:03:18.959> in 00:03:19.030 --> 00:03:19.040 align:start position:0% do I think we need to provide this in 00:03:19.040 --> 00:03:22.350 align:start position:0% do I think we need to provide this in the<00:03:19.159> sequencer<00:03:20.319> level<00:03:21.319> and<00:03:21.760> the<00:03:21.879> way<00:03:22.000> I<00:03:22.159> think 00:03:22.350 --> 00:03:22.360 align:start position:0% the sequencer level and the way I think 00:03:22.360 --> 00:03:25.509 align:start position:0% the sequencer level and the way I think about<00:03:22.599> this<00:03:22.760> is<00:03:22.920> that<00:03:23.200> this<00:03:23.319> is<00:03:23.640> uh<00:03:24.200> uh<00:03:25.080> service 00:03:25.509 --> 00:03:25.519 align:start position:0% about this is that this is uh uh service 00:03:25.519 --> 00:03:26.750 align:start position:0% about this is that this is uh uh service that<00:03:25.640> the<00:03:25.720> sequencer<00:03:26.239> provides<00:03:26.519> to<00:03:26.640> you 00:03:26.750 --> 00:03:26.760 align:start position:0% that the sequencer provides to you 00:03:26.760 --> 00:03:29.309 align:start position:0% that the sequencer provides to you basically<00:03:27.080> MPT<00:03:27.519> proofs<00:03:27.879> as<00:03:28.000> a<00:03:28.159> service<00:03:29.159> uh 00:03:29.309 --> 00:03:29.319 align:start position:0% basically MPT proofs as a service uh 00:03:29.319 --> 00:03:31.030 align:start position:0% basically MPT proofs as a service uh because<00:03:29.519> this<00:03:29.599> is<00:03:29.840> all<00:03:30.000> doable<00:03:30.439> already 00:03:31.030 --> 00:03:31.040 align:start position:0% because this is all doable already 00:03:31.040 --> 00:03:33.149 align:start position:0% because this is all doable already without<00:03:31.400> relying<00:03:31.760> on<00:03:31.879> this<00:03:32.040> pre-compile<00:03:33.040> but 00:03:33.149 --> 00:03:33.159 align:start position:0% without relying on this pre-compile but 00:03:33.159 --> 00:03:35.949 align:start position:0% without relying on this pre-compile but it's<00:03:33.400> very<00:03:34.239> complex<00:03:34.680> as<00:03:34.760> a<00:03:34.920> developer<00:03:35.760> first 00:03:35.949 --> 00:03:35.959 align:start position:0% it's very complex as a developer first 00:03:35.959 --> 00:03:37.550 align:start position:0% it's very complex as a developer first of<00:03:36.080> all<00:03:36.239> relaying<00:03:36.959> the<00:03:37.120> state<00:03:37.360> root 00:03:37.550 --> 00:03:37.560 align:start position:0% of all relaying the state root 00:03:37.560 --> 00:03:39.229 align:start position:0% of all relaying the state root information<00:03:38.040> from<00:03:38.200> L1<00:03:38.519> to<00:03:38.640> L2<00:03:38.920> in<00:03:38.959> a<00:03:39.080> very 00:03:39.229 --> 00:03:39.239 align:start position:0% information from L1 to L2 in a very 00:03:39.239 --> 00:03:42.789 align:start position:0% information from L1 to L2 in a very fiable<00:03:39.680> way<00:03:40.439> is<00:03:40.879> very<00:03:41.120> complex<00:03:42.080> and<00:03:42.239> then<00:03:42.599> for 00:03:42.789 --> 00:03:42.799 align:start position:0% fiable way is very complex and then for 00:03:42.799 --> 00:03:44.949 align:start position:0% fiable way is very complex and then for any<00:03:42.959> interaction<00:03:43.360> on<00:03:43.480> L2<00:03:44.000> providing<00:03:44.360> this<00:03:44.480> MPT 00:03:44.949 --> 00:03:44.959 align:start position:0% any interaction on L2 providing this MPT 00:03:44.959 --> 00:03:47.070 align:start position:0% any interaction on L2 providing this MPT proof<00:03:45.480> is<00:03:45.760> costly<00:03:46.120> and<00:03:46.239> also<00:03:46.560> complex<00:03:46.879> to 00:03:47.070 --> 00:03:47.080 align:start position:0% proof is costly and also complex to 00:03:47.080 --> 00:03:49.710 align:start position:0% proof is costly and also complex to develop<00:03:48.040> so<00:03:48.680> let's<00:03:48.879> just<00:03:49.000> do<00:03:49.159> the<00:03:49.280> sequencer 00:03:49.710 --> 00:03:49.720 align:start position:0% develop so let's just do the sequencer 00:03:49.720 --> 00:03:51.670 align:start position:0% develop so let's just do the sequencer and<00:03:49.840> the<00:03:49.920> pro<00:03:50.200> do<00:03:50.360> the<00:03:50.439> heavy<00:03:50.680> lifting<00:03:51.319> so<00:03:51.480> that 00:03:51.670 --> 00:03:51.680 align:start position:0% and the pro do the heavy lifting so that 00:03:51.680 --> 00:03:54.429 align:start position:0% and the pro do the heavy lifting so that you<00:03:51.879> as<00:03:52.000> the<00:03:52.159> da<00:03:52.439> developer<00:03:52.920> can<00:03:53.120> focus<00:03:53.920> on<00:03:54.280> the 00:03:54.429 --> 00:03:54.439 align:start position:0% you as the da developer can focus on the 00:03:54.439 --> 00:03:58.350 align:start position:0% you as the da developer can focus on the cool<00:03:54.680> application<00:03:55.159> logic<00:03:55.439> that<00:03:55.519> you<00:03:55.640> want<00:03:55.720> to 00:03:58.350 --> 00:03:58.360 align:start position:0% 00:03:58.360 --> 00:04:01.149 align:start position:0% develop<00:03:59.360> there<00:03:59.480> have<00:03:59.959> some<00:04:00.120> serious<00:04:01.040> there 00:04:01.149 --> 00:04:01.159 align:start position:0% develop there have some serious there 00:04:01.159 --> 00:04:02.949 align:start position:0% develop there have some serious there have<00:04:01.319> been<00:04:01.480> some<00:04:01.840> alternative<00:04:02.400> proposals<00:04:02.799> to 00:04:02.949 --> 00:04:02.959 align:start position:0% have been some alternative proposals to 00:04:02.959 --> 00:04:05.390 align:start position:0% have been some alternative proposals to Alan<00:04:03.200> asot<00:04:03.599> in<00:04:03.680> the<00:04:03.879> past<00:04:04.040> few<00:04:04.239> years<00:04:05.040> uh<00:04:05.159> two 00:04:05.390 --> 00:04:05.400 align:start position:0% Alan asot in the past few years uh two 00:04:05.400 --> 00:04:07.390 align:start position:0% Alan asot in the past few years uh two that<00:04:05.560> we<00:04:05.680> know<00:04:05.840> of<00:04:06.000> our<00:04:06.239> L1<00:04:06.599> call<00:04:06.879> and<00:04:07.120> remote 00:04:07.390 --> 00:04:07.400 align:start position:0% that we know of our L1 call and remote 00:04:07.400 --> 00:04:09.630 align:start position:0% that we know of our L1 call and remote static<00:04:07.799> call<00:04:08.640> and<00:04:08.799> these<00:04:08.920> are<00:04:09.040> more<00:04:09.239> powerful 00:04:09.630 --> 00:04:09.640 align:start position:0% static call and these are more powerful 00:04:09.640 --> 00:04:11.630 align:start position:0% static call and these are more powerful in<00:04:09.760> a<00:04:09.920> way<00:04:10.319> so<00:04:10.640> from<00:04:10.760> your<00:04:10.959> out<00:04:11.159> to<00:04:11.280> contract 00:04:11.630 --> 00:04:11.640 align:start position:0% in a way so from your out to contract 00:04:11.640 --> 00:04:13.710 align:start position:0% in a way so from your out to contract you<00:04:11.720> can<00:04:11.920> directly<00:04:12.640> call<00:04:12.879> A<00:04:13.000> View<00:04:13.280> function<00:04:13.560> on 00:04:13.710 --> 00:04:13.720 align:start position:0% you can directly call A View function on 00:04:13.720 --> 00:04:17.749 align:start position:0% you can directly call A View function on L1<00:04:14.480> basically<00:04:15.000> execute<00:04:15.760> uh<00:04:15.920> a<00:04:16.000> full<00:04:16.359> evm<00:04:17.359> uh 00:04:17.749 --> 00:04:17.759 align:start position:0% L1 basically execute uh a full evm uh 00:04:17.759 --> 00:04:20.310 align:start position:0% L1 basically execute uh a full evm uh function<00:04:18.759> but<00:04:18.959> these<00:04:19.079> are<00:04:19.560> in<00:04:19.680> our<00:04:19.919> experience 00:04:20.310 --> 00:04:20.320 align:start position:0% function but these are in our experience 00:04:20.320 --> 00:04:22.950 align:start position:0% function but these are in our experience not<00:04:20.560> very<00:04:21.199> friendly<00:04:21.560> to<00:04:21.720> zare<00:04:22.160> lab<00:04:22.400> so<00:04:22.759> uh<00:04:22.840> the 00:04:22.950 --> 00:04:22.960 align:start position:0% not very friendly to zare lab so uh the 00:04:22.960 --> 00:04:25.350 align:start position:0% not very friendly to zare lab so uh the proving<00:04:23.280> is<00:04:23.440> costly<00:04:24.280> and<00:04:24.440> also<00:04:24.759> for<00:04:24.919> instance 00:04:25.350 --> 00:04:25.360 align:start position:0% proving is costly and also for instance 00:04:25.360 --> 00:04:27.350 align:start position:0% proving is costly and also for instance Scrolls<00:04:26.120> execution<00:04:26.639> environment<00:04:27.080> for<00:04:27.240> which 00:04:27.350 --> 00:04:27.360 align:start position:0% Scrolls execution environment for which 00:04:27.360 --> 00:04:29.390 align:start position:0% Scrolls execution environment for which we<00:04:27.479> have<00:04:27.560> aover<00:04:28.479> is<00:04:28.639> slightly<00:04:28.960> different<00:04:29.199> from 00:04:29.390 --> 00:04:29.400 align:start position:0% we have aover is slightly different from 00:04:29.400 --> 00:04:32.029 align:start position:0% we have aover is slightly different from L1<00:04:30.080> so<00:04:30.280> if<00:04:30.520> within<00:04:30.880> that<00:04:31.199> prover<00:04:31.759> you<00:04:31.840> would 00:04:32.029 --> 00:04:32.039 align:start position:0% L1 so if within that prover you would 00:04:32.039 --> 00:04:33.749 align:start position:0% L1 so if within that prover you would need<00:04:32.199> to<00:04:32.520> implement<00:04:32.960> another<00:04:33.280> execution 00:04:33.749 --> 00:04:33.759 align:start position:0% need to implement another execution 00:04:33.759 --> 00:04:35.909 align:start position:0% need to implement another execution environment<00:04:34.440> for<00:04:34.639> ethereum<00:04:35.039> calls<00:04:35.639> and<00:04:35.800> that 00:04:35.909 --> 00:04:35.919 align:start position:0% environment for ethereum calls and that 00:04:35.919 --> 00:04:39.510 align:start position:0% environment for ethereum calls and that makes<00:04:36.199> this<00:04:36.440> very<00:04:37.000> hard<00:04:37.520> to<00:04:37.960> develop<00:04:38.280> on 00:04:39.510 --> 00:04:39.520 align:start position:0% makes this very hard to develop on 00:04:39.520 --> 00:04:42.990 align:start position:0% makes this very hard to develop on zaps<00:04:40.520> on<00:04:40.639> the<00:04:40.759> other<00:04:41.000> hand<00:04:41.520> A1<00:04:41.840> asot<00:04:42.280> has<00:04:42.479> the 00:04:42.990 --> 00:04:43.000 align:start position:0% zaps on the other hand A1 asot has the 00:04:43.000 --> 00:04:45.950 align:start position:0% zaps on the other hand A1 asot has the the<00:04:43.759> issue<00:04:44.199> that<00:04:44.960> you<00:04:45.120> know<00:04:45.360> if<00:04:45.479> you<00:04:45.680> interact 00:04:45.950 --> 00:04:45.960 align:start position:0% the issue that you know if you interact 00:04:45.960 --> 00:04:47.189 align:start position:0% the issue that you know if you interact with<00:04:46.039> a<00:04:46.120> contract<00:04:46.440> and<00:04:46.560> it's<00:04:46.680> upgraded<00:04:47.080> and 00:04:47.189 --> 00:04:47.199 align:start position:0% with a contract and it's upgraded and 00:04:47.199 --> 00:04:48.990 align:start position:0% with a contract and it's upgraded and the<00:04:47.280> storage<00:04:47.560> slots<00:04:47.880> change<00:04:48.520> that<00:04:48.680> might<00:04:48.800> be<00:04:48.919> a 00:04:48.990 --> 00:04:49.000 align:start position:0% the storage slots change that might be a 00:04:49.000 --> 00:04:50.990 align:start position:0% the storage slots change that might be a challenge<00:04:49.400> or<00:04:49.560> that<00:04:49.680> might<00:04:49.840> be<00:04:49.960> an<00:04:50.080> issue<00:04:50.800> so 00:04:50.990 --> 00:04:51.000 align:start position:0% challenge or that might be an issue so 00:04:51.000 --> 00:04:52.150 align:start position:0% challenge or that might be an issue so this<00:04:51.080> is<00:04:51.199> something<00:04:51.440> you<00:04:51.560> need<00:04:51.680> to<00:04:51.840> consider 00:04:52.150 --> 00:04:52.160 align:start position:0% this is something you need to consider 00:04:52.160 --> 00:04:54.270 align:start position:0% this is something you need to consider as<00:04:52.240> a<00:04:52.360> developer<00:04:52.880> in<00:04:53.039> that<00:04:53.360> regard<00:04:53.720> A1<00:04:54.039> call 00:04:54.270 --> 00:04:54.280 align:start position:0% as a developer in that regard A1 call 00:04:54.280 --> 00:04:56.950 align:start position:0% as a developer in that regard A1 call would<00:04:54.400> be<00:04:54.520> more 00:04:56.950 --> 00:04:56.960 align:start position:0% 00:04:56.960 --> 00:04:59.390 align:start position:0% powerful<00:04:57.960> all<00:04:58.120> right<00:04:58.520> now<00:04:58.759> let's<00:04:59.039> let<00:04:59.120> me<00:04:59.240> show 00:04:59.390 --> 00:04:59.400 align:start position:0% powerful all right now let's let me show 00:04:59.400 --> 00:05:01.870 align:start position:0% powerful all right now let's let me show you<00:04:59.840> this<00:04:59.919> is<00:05:00.080> implemented<00:05:00.840> in<00:05:01.240> in<00:05:01.440> our 00:05:01.870 --> 00:05:01.880 align:start position:0% you this is implemented in in our 00:05:01.880 --> 00:05:03.469 align:start position:0% you this is implemented in in our reference<00:05:02.280> implementation<00:05:02.840> in<00:05:02.919> the 00:05:03.469 --> 00:05:03.479 align:start position:0% reference implementation in the 00:05:03.479 --> 00:05:05.990 align:start position:0% reference implementation in the sequencer<00:05:04.479> there<00:05:04.560> are<00:05:04.720> two<00:05:05.000> prerequisites 00:05:05.990 --> 00:05:06.000 align:start position:0% sequencer there are two prerequisites 00:05:06.000 --> 00:05:07.790 align:start position:0% sequencer there are two prerequisites before<00:05:06.199> we<00:05:06.320> jump<00:05:06.520> into<00:05:06.680> the<00:05:06.800> implementation 00:05:07.790 --> 00:05:07.800 align:start position:0% before we jump into the implementation 00:05:07.800 --> 00:05:09.629 align:start position:0% before we jump into the implementation the<00:05:07.880> first<00:05:08.080> prerequisite<00:05:08.639> is<00:05:09.080> what<00:05:09.199> I<00:05:09.360> call 00:05:09.629 --> 00:05:09.639 align:start position:0% the first prerequisite is what I call 00:05:09.639 --> 00:05:12.189 align:start position:0% the first prerequisite is what I call trustless<00:05:10.199> block<00:05:10.560> hash<00:05:10.759> relay<00:05:11.520> so<00:05:11.680> the<00:05:11.759> L2 00:05:12.189 --> 00:05:12.199 align:start position:0% trustless block hash relay so the L2 00:05:12.199 --> 00:05:14.670 align:start position:0% trustless block hash relay so the L2 Network<00:05:13.120> scroll<00:05:13.520> in<00:05:13.680> this<00:05:13.880> example<00:05:14.320> needs<00:05:14.560> to 00:05:14.670 --> 00:05:14.680 align:start position:0% Network scroll in this example needs to 00:05:14.680 --> 00:05:17.710 align:start position:0% Network scroll in this example needs to have<00:05:14.800> a<00:05:14.919> notion<00:05:15.840> of<00:05:16.840> uh<00:05:17.039> what<00:05:17.199> is<00:05:17.280> the<00:05:17.440> latest 00:05:17.710 --> 00:05:17.720 align:start position:0% have a notion of uh what is the latest 00:05:17.720 --> 00:05:19.590 align:start position:0% have a notion of uh what is the latest L1<00:05:18.080> block<00:05:18.639> basically<00:05:18.960> it<00:05:19.039> needs<00:05:19.199> to<00:05:19.319> have<00:05:19.440> a 00:05:19.590 --> 00:05:19.600 align:start position:0% L1 block basically it needs to have a 00:05:19.600 --> 00:05:22.150 align:start position:0% L1 block basically it needs to have a view<00:05:19.919> of<00:05:20.080> the<00:05:20.199> L1<00:05:20.639> chain<00:05:21.280> including<00:05:21.759> the<00:05:21.880> state 00:05:22.150 --> 00:05:22.160 align:start position:0% view of the L1 chain including the state 00:05:22.160 --> 00:05:24.270 align:start position:0% view of the L1 chain including the state rout<00:05:22.800> because<00:05:23.000> you<00:05:23.120> need<00:05:23.280> the<00:05:23.360> state<00:05:23.560> roots<00:05:23.919> to 00:05:24.270 --> 00:05:24.280 align:start position:0% rout because you need the state roots to 00:05:24.280 --> 00:05:27.029 align:start position:0% rout because you need the state roots to to<00:05:24.440> verify<00:05:24.840> these<00:05:25.280> proofs<00:05:26.280> uh<00:05:26.440> some<00:05:26.639> rollups 00:05:27.029 --> 00:05:27.039 align:start position:0% to verify these proofs uh some rollups 00:05:27.039 --> 00:05:30.670 align:start position:0% to verify these proofs uh some rollups already<00:05:27.319> support<00:05:27.800> this<00:05:28.800> uh<00:05:29.280> the<00:05:29.400> way<00:05:29.840> Works<00:05:30.600> uh 00:05:30.670 --> 00:05:30.680 align:start position:0% already support this uh the way Works uh 00:05:30.680 --> 00:05:32.270 align:start position:0% already support this uh the way Works uh in<00:05:30.800> our<00:05:31.000> system<00:05:31.560> although<00:05:31.840> it's<00:05:31.919> not<00:05:32.039> launch 00:05:32.270 --> 00:05:32.280 align:start position:0% in our system although it's not launch 00:05:32.280 --> 00:05:33.749 align:start position:0% in our system although it's not launch domain<00:05:32.600> at<00:05:32.759> yet<00:05:32.960> is<00:05:33.160> the<00:05:33.240> sequencer 00:05:33.749 --> 00:05:33.759 align:start position:0% domain at yet is the sequencer 00:05:33.759 --> 00:05:35.909 align:start position:0% domain at yet is the sequencer optimistically<00:05:34.319> relays<00:05:35.039> blocks<00:05:35.319> from<00:05:35.479> L1<00:05:35.800> to 00:05:35.909 --> 00:05:35.919 align:start position:0% optimistically relays blocks from L1 to 00:05:35.919 --> 00:05:38.390 align:start position:0% optimistically relays blocks from L1 to L2<00:05:36.840> we<00:05:37.039> verified<00:05:37.440> that<00:05:37.600> these<00:05:37.800> indeed<00:05:38.039> form<00:05:38.280> a 00:05:38.390 --> 00:05:38.400 align:start position:0% L2 we verified that these indeed form a 00:05:38.400 --> 00:05:40.550 align:start position:0% L2 we verified that these indeed form a chain<00:05:38.639> of<00:05:38.840> blocks<00:05:39.840> and<00:05:40.039> then<00:05:40.280> when<00:05:40.400> we 00:05:40.550 --> 00:05:40.560 align:start position:0% chain of blocks and then when we 00:05:40.560 --> 00:05:43.309 align:start position:0% chain of blocks and then when we finalize<00:05:41.120> this<00:05:41.400> back<00:05:41.520> on<00:05:41.960> ethereum<00:05:42.960> uh<00:05:43.160> we 00:05:43.309 --> 00:05:43.319 align:start position:0% finalize this back on ethereum uh we 00:05:43.319 --> 00:05:44.790 align:start position:0% finalize this back on ethereum uh we check<00:05:43.639> that<00:05:43.800> the<00:05:43.880> sequencer<00:05:44.400> relate<00:05:44.680> the 00:05:44.790 --> 00:05:44.800 align:start position:0% check that the sequencer relate the 00:05:44.800 --> 00:05:46.309 align:start position:0% check that the sequencer relate the correct<00:05:45.080> data<00:05:45.319> so<00:05:45.440> if<00:05:45.560> the<00:05:45.680> sequencer<00:05:46.120> tries 00:05:46.309 --> 00:05:46.319 align:start position:0% correct data so if the sequencer tries 00:05:46.319 --> 00:05:48.029 align:start position:0% correct data so if the sequencer tries to<00:05:46.440> cheat<00:05:47.039> then<00:05:47.160> it<00:05:47.280> will<00:05:47.400> be<00:05:47.560> unable<00:05:47.919> to 00:05:48.029 --> 00:05:48.039 align:start position:0% to cheat then it will be unable to 00:05:48.039 --> 00:05:50.150 align:start position:0% to cheat then it will be unable to finalize<00:05:48.520> this<00:05:48.639> on<00:05:48.840> Al<00:05:49.039> one<00:05:49.759> so<00:05:49.919> this<00:05:50.039> is 00:05:50.150 --> 00:05:50.160 align:start position:0% finalize this on Al one so this is 00:05:50.160 --> 00:05:52.150 align:start position:0% finalize this on Al one so this is doable<00:05:50.600> but<00:05:50.759> this<00:05:50.840> is<00:05:50.960> one<00:05:51.080> of<00:05:51.160> the 00:05:52.150 --> 00:05:52.160 align:start position:0% doable but this is one of the 00:05:52.160 --> 00:05:54.270 align:start position:0% doable but this is one of the prerequisites<00:05:53.160> the<00:05:53.280> other<00:05:53.440> prerequisite<00:05:54.120> is 00:05:54.270 --> 00:05:54.280 align:start position:0% prerequisites the other prerequisite is 00:05:54.280 --> 00:05:57.189 align:start position:0% prerequisites the other prerequisite is that<00:05:55.199> any<00:05:55.440> L2<00:05:55.800> node<00:05:56.039> including<00:05:56.520> non<00:05:56.759> sequencer 00:05:57.189 --> 00:05:57.199 align:start position:0% that any L2 node including non sequencer 00:05:57.199 --> 00:05:58.830 align:start position:0% that any L2 node including non sequencer noes<00:05:57.400> so<00:05:57.560> Fuller<00:05:57.880> nodes<00:05:58.160> must<00:05:58.360> connect<00:05:58.639> to<00:05:58.759> an 00:05:58.830 --> 00:05:58.840 align:start position:0% noes so Fuller nodes must connect to an 00:05:58.840 --> 00:06:00.990 align:start position:0% noes so Fuller nodes must connect to an L1<00:05:59.160> node<00:05:59.759> because<00:06:00.000> as<00:06:00.120> I<00:06:00.240> mentioned<00:06:00.639> this 00:06:00.990 --> 00:06:01.000 align:start position:0% L1 node because as I mentioned this 00:06:01.000 --> 00:06:03.350 align:start position:0% L1 node because as I mentioned this precom<00:06:01.560> call<00:06:01.759> is<00:06:01.880> translated<00:06:02.319> into<00:06:02.560> an<00:06:02.680> RPC 00:06:03.350 --> 00:06:03.360 align:start position:0% precom call is translated into an RPC 00:06:03.360 --> 00:06:07.350 align:start position:0% precom call is translated into an RPC query<00:06:04.360> So<00:06:05.240> currently<00:06:05.800> not<00:06:06.039> all<00:06:06.360> rollups 00:06:07.350 --> 00:06:07.360 align:start position:0% query So currently not all rollups 00:06:07.360 --> 00:06:09.350 align:start position:0% query So currently not all rollups inforce<00:06:07.880> this<00:06:08.599> uh<00:06:08.720> you<00:06:08.800> might<00:06:09.000> just<00:06:09.120> follow 00:06:09.350 --> 00:06:09.360 align:start position:0% inforce this uh you might just follow 00:06:09.360 --> 00:06:10.950 align:start position:0% inforce this uh you might just follow the<00:06:09.440> unsafe<00:06:09.840> chain<00:06:10.280> from<00:06:10.440> the<00:06:10.599> peer-to-peer 00:06:10.950 --> 00:06:10.960 align:start position:0% the unsafe chain from the peer-to-peer 00:06:10.960 --> 00:06:13.150 align:start position:0% the unsafe chain from the peer-to-peer layer<00:06:11.400> from<00:06:11.520> the<00:06:11.639> sequencer<00:06:12.599> but<00:06:12.759> if<00:06:12.880> you<00:06:13.039> want 00:06:13.150 --> 00:06:13.160 align:start position:0% layer from the sequencer but if you want 00:06:13.160 --> 00:06:15.070 align:start position:0% layer from the sequencer but if you want to<00:06:13.319> support<00:06:13.680> l1s<00:06:14.160> load<00:06:14.360> then<00:06:14.479> all<00:06:14.599> nodes<00:06:14.919> need 00:06:15.070 --> 00:06:15.080 align:start position:0% to support l1s load then all nodes need 00:06:15.080 --> 00:06:16.990 align:start position:0% to support l1s load then all nodes need to<00:06:15.240> connect<00:06:15.599> to<00:06:15.800> an<00:06:15.919> i<00:06:16.039> one 00:06:16.990 --> 00:06:17.000 align:start position:0% to connect to an i one 00:06:17.000 --> 00:06:19.230 align:start position:0% to connect to an i one Noe<00:06:18.000> given<00:06:18.240> these<00:06:18.440> prerequisites<00:06:19.000> it's 00:06:19.230 --> 00:06:19.240 align:start position:0% Noe given these prerequisites it's 00:06:19.240 --> 00:06:21.670 align:start position:0% Noe given these prerequisites it's actually<00:06:20.240> quite<00:06:20.440> simple<00:06:20.919> the<00:06:21.080> execution<00:06:21.560> part 00:06:21.670 --> 00:06:21.680 align:start position:0% actually quite simple the execution part 00:06:21.680 --> 00:06:23.749 align:start position:0% actually quite simple the execution part of<00:06:21.800> the<00:06:21.880> pre-combine<00:06:22.360> is<00:06:22.479> quite<00:06:22.680> simple<00:06:23.479> uh<00:06:23.639> I 00:06:23.749 --> 00:06:23.759 align:start position:0% of the pre-combine is quite simple uh I 00:06:23.759 --> 00:06:25.350 align:start position:0% of the pre-combine is quite simple uh I copied<00:06:24.039> the<00:06:24.160> example<00:06:24.479> from<00:06:24.599> our<00:06:24.800> go<00:06:24.960> ethereum 00:06:25.350 --> 00:06:25.360 align:start position:0% copied the example from our go ethereum 00:06:25.360 --> 00:06:27.950 align:start position:0% copied the example from our go ethereum Fork<00:06:26.080> so<00:06:26.240> you<00:06:26.360> would<00:06:26.560> just<00:06:26.680> need<00:06:26.840> to<00:06:27.599> extend 00:06:27.950 --> 00:06:27.960 align:start position:0% Fork so you would just need to extend 00:06:27.960 --> 00:06:29.749 align:start position:0% Fork so you would just need to extend your<00:06:28.160> evm<00:06:28.560> implementation<00:06:29.080> to<00:06:29.240> add<00:06:29.360> a<00:06:29.440> new 00:06:29.749 --> 00:06:29.759 align:start position:0% your evm implementation to add a new 00:06:29.759 --> 00:06:32.029 align:start position:0% your evm implementation to add a new pre-compile<00:06:30.759> and<00:06:30.880> what<00:06:31.000> it<00:06:31.120> does<00:06:31.360> is<00:06:31.720> first<00:06:31.919> of 00:06:32.029 --> 00:06:32.039 align:start position:0% pre-compile and what it does is first of 00:06:32.039 --> 00:06:34.629 align:start position:0% pre-compile and what it does is first of all<00:06:32.160> it<00:06:32.319> needs<00:06:33.199> it<00:06:33.280> needs<00:06:33.479> to<00:06:33.599> read<00:06:33.840> the<00:06:33.960> latest 00:06:34.629 --> 00:06:34.639 align:start position:0% all it needs it needs to read the latest 00:06:34.639 --> 00:06:37.189 align:start position:0% all it needs it needs to read the latest layer<00:06:34.960> one<00:06:35.160> block<00:06:35.599> that<00:06:35.720> we<00:06:35.880> know<00:06:36.080> of<00:06:36.919> in<00:06:37.039> our 00:06:37.189 --> 00:06:37.199 align:start position:0% layer one block that we know of in our 00:06:37.199 --> 00:06:38.670 align:start position:0% layer one block that we know of in our case<00:06:37.400> this<00:06:37.479> is<00:06:37.599> stored<00:06:37.880> in<00:06:38.000> States<00:06:38.400> but<00:06:38.520> this 00:06:38.670 --> 00:06:38.680 align:start position:0% case this is stored in States but this 00:06:38.680 --> 00:06:40.830 align:start position:0% case this is stored in States but this might<00:06:38.800> be<00:06:38.919> implemented<00:06:39.360> in<00:06:39.479> other<00:06:39.680> ways<00:06:40.680> then 00:06:40.830 --> 00:06:40.840 align:start position:0% might be implemented in other ways then 00:06:40.840 --> 00:06:42.670 align:start position:0% might be implemented in other ways then it<00:06:40.960> needs<00:06:41.199> to<00:06:41.599> parse<00:06:42.000> the<00:06:42.120> inputs<00:06:42.479> that<00:06:42.599> the 00:06:42.670 --> 00:06:42.680 align:start position:0% it needs to parse the inputs that the 00:06:42.680 --> 00:06:45.350 align:start position:0% it needs to parse the inputs that the developer<00:06:43.400> provided<00:06:44.400> uh<00:06:44.599> execute<00:06:45.000> a<00:06:45.160> batch 00:06:45.350 --> 00:06:45.360 align:start position:0% developer provided uh execute a batch 00:06:45.360 --> 00:06:48.110 align:start position:0% developer provided uh execute a batch RPC<00:06:46.000> call<00:06:46.639> so<00:06:47.000> even<00:06:47.199> if<00:06:47.319> you<00:06:47.479> read<00:06:47.919> five 00:06:48.110 --> 00:06:48.120 align:start position:0% RPC call so even if you read five 00:06:48.120 --> 00:06:49.790 align:start position:0% RPC call so even if you read five storage<00:06:48.479> slots<00:06:48.800> the<00:06:48.919> latency<00:06:49.360> is<00:06:49.479> the<00:06:49.560> same 00:06:49.790 --> 00:06:49.800 align:start position:0% storage slots the latency is the same 00:06:49.800 --> 00:06:51.830 align:start position:0% storage slots the latency is the same because<00:06:49.960> we<00:06:50.080> can<00:06:50.240> batch<00:06:50.560> these<00:06:50.759> queries<00:06:51.680> and 00:06:51.830 --> 00:06:51.840 align:start position:0% because we can batch these queries and 00:06:51.840 --> 00:06:53.909 align:start position:0% because we can batch these queries and then<00:06:52.120> resume<00:06:52.680> execution<00:06:53.120> and<00:06:53.360> return<00:06:53.599> control 00:06:53.909 --> 00:06:53.919 align:start position:0% then resume execution and return control 00:06:53.919 --> 00:06:55.869 align:start position:0% then resume execution and return control to<00:06:54.039> the<00:06:54.160> evm 00:06:55.869 --> 00:06:55.879 align:start position:0% to the evm 00:06:55.879 --> 00:06:58.230 align:start position:0% to the evm execution<00:06:56.879> so<00:06:57.080> that<00:06:57.199> was<00:06:57.360> the<00:06:57.479> execution<00:06:58.039> and 00:06:58.230 --> 00:06:58.240 align:start position:0% execution so that was the execution and 00:06:58.240 --> 00:07:00.589 align:start position:0% execution so that was the execution and on<00:06:58.360> the<00:06:58.479> verification<00:06:59.080> side<00:06:59.280> as<00:06:59.639> mentioned<00:07:00.440> we 00:07:00.589 --> 00:07:00.599 align:start position:0% on the verification side as mentioned we 00:07:00.599 --> 00:07:03.430 align:start position:0% on the verification side as mentioned we need<00:07:00.720> to<00:07:00.919> verify<00:07:01.919> uh<00:07:02.039> the<00:07:02.160> block<00:07:02.440> hash<00:07:02.680> relay 00:07:03.430 --> 00:07:03.440 align:start position:0% need to verify uh the block hash relay 00:07:03.440 --> 00:07:05.469 align:start position:0% need to verify uh the block hash relay so<00:07:03.680> verify<00:07:04.160> the<00:07:04.280> L1<00:07:04.560> header<00:07:04.800> chain<00:07:05.039> and<00:07:05.160> verify 00:07:05.469 --> 00:07:05.479 align:start position:0% so verify the L1 header chain and verify 00:07:05.479 --> 00:07:07.830 align:start position:0% so verify the L1 header chain and verify that<00:07:05.639> the<00:07:06.000> sequencer<00:07:06.879> relay<00:07:07.319> the<00:07:07.400> correct 00:07:07.830 --> 00:07:07.840 align:start position:0% that the sequencer relay the correct 00:07:07.840 --> 00:07:10.029 align:start position:0% that the sequencer relay the correct information<00:07:08.840> and<00:07:09.039> then<00:07:09.520> as<00:07:09.680> part<00:07:09.840> of<00:07:09.960> the 00:07:10.029 --> 00:07:10.039 align:start position:0% information and then as part of the 00:07:10.039 --> 00:07:11.990 align:start position:0% information and then as part of the proving<00:07:10.440> process<00:07:10.680> the<00:07:10.800> sequencer<00:07:11.319> also 00:07:11.990 --> 00:07:12.000 align:start position:0% proving process the sequencer also 00:07:12.000 --> 00:07:14.589 align:start position:0% proving process the sequencer also fetches<00:07:12.440> these<00:07:12.599> MPT<00:07:13.120> proofs<00:07:14.120> uh<00:07:14.199> so<00:07:14.319> that<00:07:14.479> you 00:07:14.589 --> 00:07:14.599 align:start position:0% fetches these MPT proofs uh so that you 00:07:14.599 --> 00:07:16.510 align:start position:0% fetches these MPT proofs uh so that you as<00:07:14.720> the<00:07:14.840> developer<00:07:15.199> don't<00:07:15.360> need<00:07:15.560> to<00:07:15.680> do<00:07:15.840> that 00:07:16.510 --> 00:07:16.520 align:start position:0% as the developer don't need to do that 00:07:16.520 --> 00:07:18.230 align:start position:0% as the developer don't need to do that and<00:07:16.720> inside<00:07:17.080> approver<00:07:17.520> we<00:07:17.599> need<00:07:17.720> to<00:07:17.879> verify 00:07:18.230 --> 00:07:18.240 align:start position:0% and inside approver we need to verify 00:07:18.240 --> 00:07:20.589 align:start position:0% and inside approver we need to verify all<00:07:18.400> these<00:07:18.599> lay<00:07:18.879> one<00:07:19.000> MPT<00:07:19.479> proofs<00:07:20.280> and<00:07:20.479> make 00:07:20.589 --> 00:07:20.599 align:start position:0% all these lay one MPT proofs and make 00:07:20.599 --> 00:07:23.550 align:start position:0% all these lay one MPT proofs and make sure<00:07:20.840> that<00:07:21.160> these<00:07:21.319> were<00:07:21.520> all 00:07:23.550 --> 00:07:23.560 align:start position:0% sure that these were all 00:07:23.560 --> 00:07:26.550 align:start position:0% sure that these were all correct<00:07:24.560> now<00:07:25.319> we<00:07:25.479> have<00:07:25.800> this<00:07:26.120> rollup 00:07:26.550 --> 00:07:26.560 align:start position:0% correct now we have this rollup 00:07:26.560 --> 00:07:28.029 align:start position:0% correct now we have this rollup Improvement<00:07:27.039> proposal<00:07:27.440> but<00:07:27.560> this<00:07:27.680> is<00:07:27.759> still<00:07:27.919> a 00:07:28.029 --> 00:07:28.039 align:start position:0% Improvement proposal but this is still a 00:07:28.039 --> 00:07:29.270 align:start position:0% Improvement proposal but this is still a draft<00:07:28.360> and<00:07:28.440> there<00:07:28.520> are<00:07:28.759> still<00:07:28.919> some<00:07:29.080> open 00:07:29.270 --> 00:07:29.280 align:start position:0% draft and there are still some open 00:07:29.280 --> 00:07:30.110 align:start position:0% draft and there are still some open questions 00:07:30.110 --> 00:07:30.120 align:start position:0% questions 00:07:30.120 --> 00:07:31.430 align:start position:0% questions and<00:07:30.199> the<00:07:30.319> main<00:07:30.520> goal<00:07:30.720> of<00:07:30.840> this<00:07:31.000> talk<00:07:31.199> is<00:07:31.280> to 00:07:31.430 --> 00:07:31.440 align:start position:0% and the main goal of this talk is to 00:07:31.440 --> 00:07:33.230 align:start position:0% and the main goal of this talk is to involve<00:07:31.759> more<00:07:31.960> people<00:07:32.240> so<00:07:32.400> if<00:07:32.479> you're<00:07:32.680> a 00:07:33.230 --> 00:07:33.240 align:start position:0% involve more people so if you're a 00:07:33.240 --> 00:07:34.550 align:start position:0% involve more people so if you're a developer<00:07:33.680> who<00:07:33.840> might<00:07:33.960> be<00:07:34.120> interested<00:07:34.440> in 00:07:34.550 --> 00:07:34.560 align:start position:0% developer who might be interested in 00:07:34.560 --> 00:07:36.909 align:start position:0% developer who might be interested in using<00:07:34.879> this<00:07:35.479> then<00:07:35.639> we<00:07:35.800> love<00:07:35.919> to<00:07:36.080> hear<00:07:36.280> for<00:07:36.720> hear 00:07:36.909 --> 00:07:36.919 align:start position:0% using this then we love to hear for hear 00:07:36.919 --> 00:07:39.629 align:start position:0% using this then we love to hear for hear from<00:07:37.120> you<00:07:37.639> see<00:07:37.919> what<00:07:38.039> you<00:07:38.199> need<00:07:38.960> uh<00:07:39.160> and<00:07:39.360> if<00:07:39.520> you 00:07:39.629 --> 00:07:39.639 align:start position:0% from you see what you need uh and if you 00:07:39.639 --> 00:07:42.830 align:start position:0% from you see what you need uh and if you are<00:07:40.080> an<00:07:40.240> L2<00:07:40.680> protocol<00:07:41.440> maintainer<00:07:42.440> you<00:07:42.560> know 00:07:42.830 --> 00:07:42.840 align:start position:0% are an L2 protocol maintainer you know 00:07:42.840 --> 00:07:44.270 align:start position:0% are an L2 protocol maintainer you know you're<00:07:43.000> maintaining<00:07:43.400> a<00:07:43.479> sequencer<00:07:43.960> note<00:07:44.159> then 00:07:44.270 --> 00:07:44.280 align:start position:0% you're maintaining a sequencer note then 00:07:44.280 --> 00:07:46.149 align:start position:0% you're maintaining a sequencer note then you're<00:07:44.479> interested<00:07:44.800> in<00:07:45.280> adopting<00:07:45.800> this<00:07:46.000> then 00:07:46.149 --> 00:07:46.159 align:start position:0% you're interested in adopting this then 00:07:46.159 --> 00:07:48.309 align:start position:0% you're interested in adopting this then we'd<00:07:46.400> also<00:07:46.599> love<00:07:46.800> to<00:07:46.919> hear<00:07:47.120> from<00:07:47.280> you<00:07:47.800> to<00:07:48.080> share 00:07:48.309 --> 00:07:48.319 align:start position:0% we'd also love to hear from you to share 00:07:48.319 --> 00:07:49.230 align:start position:0% we'd also love to hear from you to share your 00:07:49.230 --> 00:07:49.240 align:start position:0% your 00:07:49.240 --> 00:07:51.749 align:start position:0% your input<00:07:50.240> so<00:07:50.360> I<00:07:50.440> want<00:07:50.560> to<00:07:50.680> highlight<00:07:51.000> three<00:07:51.159> open 00:07:51.749 --> 00:07:51.759 align:start position:0% input so I want to highlight three open 00:07:51.759 --> 00:07:54.350 align:start position:0% input so I want to highlight three open questions<00:07:52.759> uh<00:07:52.879> one<00:07:53.080> open<00:07:53.319> question<00:07:53.759> that<00:07:54.039> we 00:07:54.350 --> 00:07:54.360 align:start position:0% questions uh one open question that we 00:07:54.360 --> 00:07:56.510 align:start position:0% questions uh one open question that we received<00:07:54.520> from<00:07:54.680> devs<00:07:55.000> actually<00:07:55.240> is<00:07:55.440> that<00:07:55.759> like 00:07:56.510 --> 00:07:56.520 align:start position:0% received from devs actually is that like 00:07:56.520 --> 00:07:58.990 align:start position:0% received from devs actually is that like do<00:07:56.680> we<00:07:56.800> want<00:07:56.919> to<00:07:57.080> allow<00:07:57.520> L2<00:07:58.319> applications<00:07:58.840> to 00:07:58.990 --> 00:07:59.000 align:start position:0% do we want to allow L2 applications to 00:07:59.000 --> 00:08:01.309 align:start position:0% do we want to allow L2 applications to read<00:07:59.720> A1<00:08:00.039> State<00:08:00.240> at<00:08:00.400> arbitrary<00:08:00.840> height<00:08:01.039> so<00:08:01.159> not 00:08:01.309 --> 00:08:01.319 align:start position:0% read A1 State at arbitrary height so not 00:08:01.319 --> 00:08:02.990 align:start position:0% read A1 State at arbitrary height so not just<00:08:01.440> the<00:08:01.560> latest<00:08:01.879> A1<00:08:02.240> height<00:08:02.639> but<00:08:02.759> maybe 00:08:02.990 --> 00:08:03.000 align:start position:0% just the latest A1 height but maybe 00:08:03.000 --> 00:08:05.270 align:start position:0% just the latest A1 height but maybe older<00:08:03.440> State<00:08:04.440> definitely<00:08:04.879> for<00:08:05.039> some 00:08:05.270 --> 00:08:05.280 align:start position:0% older State definitely for some 00:08:05.280 --> 00:08:06.909 align:start position:0% older State definitely for some applications<00:08:05.879> this<00:08:06.000> is 00:08:06.909 --> 00:08:06.919 align:start position:0% applications this is 00:08:06.919 --> 00:08:09.550 align:start position:0% applications this is required<00:08:07.919> but<00:08:08.199> this<00:08:08.400> also<00:08:09.199> has<00:08:09.360> some 00:08:09.550 --> 00:08:09.560 align:start position:0% required but this also has some 00:08:09.560 --> 00:08:11.189 align:start position:0% required but this also has some drawbacks<00:08:10.039> for<00:08:10.159> instance<00:08:10.560> if<00:08:10.680> you<00:08:10.879> allow 00:08:11.189 --> 00:08:11.199 align:start position:0% drawbacks for instance if you allow 00:08:11.199 --> 00:08:13.670 align:start position:0% drawbacks for instance if you allow reading<00:08:11.599> Old<00:08:11.919> State<00:08:12.840> then<00:08:13.039> the<00:08:13.159> nodes<00:08:13.479> must 00:08:13.670 --> 00:08:13.680 align:start position:0% reading Old State then the nodes must 00:08:13.680 --> 00:08:15.950 align:start position:0% reading Old State then the nodes must connect<00:08:14.000> to<00:08:14.159> an<00:08:14.319> archive<00:08:14.840> at<00:08:15.080> one<00:08:15.240> note<00:08:15.840> and 00:08:15.950 --> 00:08:15.960 align:start position:0% connect to an archive at one note and 00:08:15.960 --> 00:08:18.189 align:start position:0% connect to an archive at one note and for<00:08:16.159> some<00:08:16.360> L1<00:08:16.759> nodes<00:08:17.240> like<00:08:17.440> WTH<00:08:17.800> I<00:08:17.879> believe 00:08:18.189 --> 00:08:18.199 align:start position:0% for some L1 nodes like WTH I believe 00:08:18.199 --> 00:08:19.869 align:start position:0% for some L1 nodes like WTH I believe this<00:08:18.319> is<00:08:18.759> not<00:08:18.919> even<00:08:19.240> possible<00:08:19.599> because<00:08:19.759> it 00:08:19.869 --> 00:08:19.879 align:start position:0% this is not even possible because it 00:08:19.879 --> 00:08:25.670 align:start position:0% this is not even possible because it cannot<00:08:20.159> serve<00:08:20.720> historical<00:08:21.720> uh<00:08:21.879> G<00:08:22.199> proof 00:08:25.670 --> 00:08:25.680 align:start position:0% 00:08:25.680 --> 00:08:28.309 align:start position:0% requests<00:08:26.680> another<00:08:27.039> question<00:08:27.360> is<00:08:27.879> how<00:08:28.080> do<00:08:28.199> you 00:08:28.309 --> 00:08:28.319 align:start position:0% requests another question is how do you 00:08:28.319 --> 00:08:30.710 align:start position:0% requests another question is how do you deal<00:08:28.599> with<00:08:29.039> RPC<00:08:29.720> errors<00:08:30.000> and<00:08:30.159> latency<00:08:30.639> when 00:08:30.710 --> 00:08:30.720 align:start position:0% deal with RPC errors and latency when 00:08:30.720 --> 00:08:33.110 align:start position:0% deal with RPC errors and latency when you<00:08:30.919> execute<00:08:31.800> uh<00:08:32.000> these<00:08:32.200> calls<00:08:32.440> to<00:08:32.560> the<00:08:32.640> L1<00:08:32.919> SL 00:08:33.110 --> 00:08:33.120 align:start position:0% you execute uh these calls to the L1 SL 00:08:33.120 --> 00:08:35.190 align:start position:0% you execute uh these calls to the L1 SL load<00:08:33.279> pre-compile<00:08:34.200> latency<00:08:34.839> is<00:08:34.919> a<00:08:35.039> big 00:08:35.190 --> 00:08:35.200 align:start position:0% load pre-compile latency is a big 00:08:35.200 --> 00:08:37.630 align:start position:0% load pre-compile latency is a big question<00:08:35.440> mark<00:08:35.680> to<00:08:35.800> me<00:08:36.039> because<00:08:36.800> if<00:08:36.959> there's<00:08:37.159> a 00:08:37.630 --> 00:08:37.640 align:start position:0% question mark to me because if there's a 00:08:37.640 --> 00:08:39.430 align:start position:0% question mark to me because if there's a latency<00:08:38.080> between<00:08:38.320> the<00:08:38.399> L2<00:08:38.760> node<00:08:39.000> and<00:08:39.080> the<00:08:39.159> L1 00:08:39.430 --> 00:08:39.440 align:start position:0% latency between the L2 node and the L1 00:08:39.440 --> 00:08:42.350 align:start position:0% latency between the L2 node and the L1 node<00:08:39.959> you<00:08:40.039> know<00:08:40.200> the<00:08:40.320> RPC<00:08:40.800> query<00:08:41.640> that<00:08:41.839> might 00:08:42.350 --> 00:08:42.360 align:start position:0% node you know the RPC query that might 00:08:42.360 --> 00:08:43.750 align:start position:0% node you know the RPC query that might affect<00:08:42.680> the<00:08:42.800> throughput<00:08:43.200> of<00:08:43.279> the<00:08:43.399> system<00:08:43.680> that 00:08:43.750 --> 00:08:43.760 align:start position:0% affect the throughput of the system that 00:08:43.760 --> 00:08:45.829 align:start position:0% affect the throughput of the system that might<00:08:43.919> slow<00:08:44.159> your<00:08:44.279> system<00:08:44.600> down<00:08:45.279> so<00:08:45.560> you<00:08:45.680> need 00:08:45.829 --> 00:08:45.839 align:start position:0% might slow your system down so you need 00:08:45.839 --> 00:08:47.550 align:start position:0% might slow your system down so you need to<00:08:46.360> consider<00:08:46.760> that<00:08:46.880> when<00:08:47.000> you<00:08:47.120> price<00:08:47.440> this 00:08:47.550 --> 00:08:47.560 align:start position:0% to consider that when you price this 00:08:47.560 --> 00:08:49.509 align:start position:0% to consider that when you price this pre-compile<00:08:48.560> and<00:08:48.720> if<00:08:48.800> you<00:08:49.040> encounter<00:08:49.399> an 00:08:49.509 --> 00:08:49.519 align:start position:0% pre-compile and if you encounter an 00:08:49.519 --> 00:08:51.710 align:start position:0% pre-compile and if you encounter an error<00:08:49.800> you<00:08:49.920> need<00:08:50.040> to<00:08:50.240> decide<00:08:50.839> do<00:08:51.000> I<00:08:51.160> retry<00:08:51.600> or 00:08:51.710 --> 00:08:51.720 align:start position:0% error you need to decide do I retry or 00:08:51.720 --> 00:08:54.269 align:start position:0% error you need to decide do I retry or do<00:08:51.839> I<00:08:52.040> drop<00:08:52.320> this 00:08:54.269 --> 00:08:54.279 align:start position:0% do I drop this 00:08:54.279 --> 00:08:56.509 align:start position:0% do I drop this transaction<00:08:55.279> and<00:08:55.399> finally<00:08:55.760> defining<00:08:56.160> the<00:08:56.320> gas 00:08:56.509 --> 00:08:56.519 align:start position:0% transaction and finally defining the gas 00:08:56.519 --> 00:08:58.670 align:start position:0% transaction and finally defining the gas cost<00:08:56.720> is<00:08:56.880> also<00:08:57.120> tricky<00:08:57.680> so<00:08:57.959> in<00:08:58.079> our<00:08:58.320> proposal 00:08:58.670 --> 00:08:58.680 align:start position:0% cost is also tricky so in our proposal 00:08:58.680 --> 00:09:00.870 align:start position:0% cost is also tricky so in our proposal we<00:08:58.800> have<00:08:58.880> a<00:08:59.000> very<00:08:59.160> simple<00:08:59.600> pricing<00:08:59.920> mechanism 00:09:00.870 --> 00:09:00.880 align:start position:0% we have a very simple pricing mechanism 00:09:00.880 --> 00:09:02.670 align:start position:0% we have a very simple pricing mechanism basically<00:09:01.200> a<00:09:01.360> fixed<00:09:01.680> cost<00:09:01.880> per<00:09:02.079> pre-c<00:09:02.320> compi 00:09:02.670 --> 00:09:02.680 align:start position:0% basically a fixed cost per pre-c compi 00:09:02.680 --> 00:09:05.710 align:start position:0% basically a fixed cost per pre-c compi call<00:09:02.880> and<00:09:03.079> variable<00:09:03.920> cost<00:09:04.920> um<00:09:05.160> or<00:09:05.440> another 00:09:05.710 --> 00:09:05.720 align:start position:0% call and variable cost um or another 00:09:05.720 --> 00:09:08.110 align:start position:0% call and variable cost um or another fixed<00:09:06.079> cost<00:09:06.640> per<00:09:07.040> the<00:09:07.399> number<00:09:07.600> of<00:09:07.680> slots<00:09:08.040> that 00:09:08.110 --> 00:09:08.120 align:start position:0% fixed cost per the number of slots that 00:09:08.120 --> 00:09:11.230 align:start position:0% fixed cost per the number of slots that you're<00:09:08.760> quarrying<00:09:09.760> but<00:09:10.160> this<00:09:10.279> is<00:09:10.399> not<00:09:10.560> all<00:09:11.040> you 00:09:11.230 --> 00:09:11.240 align:start position:0% you're quarrying but this is not all you 00:09:11.240 --> 00:09:13.630 align:start position:0% you're quarrying but this is not all you also<00:09:11.440> have<00:09:11.560> to<00:09:11.760> pay<00:09:12.160> for<00:09:12.920> producing<00:09:13.480> and 00:09:13.630 --> 00:09:13.640 align:start position:0% also have to pay for producing and 00:09:13.640 --> 00:09:16.590 align:start position:0% also have to pay for producing and verifying<00:09:14.040> these<00:09:14.200> MPT<00:09:14.959> proofs<00:09:15.959> uh<00:09:16.120> that<00:09:16.279> is 00:09:16.590 --> 00:09:16.600 align:start position:0% verifying these MPT proofs uh that is 00:09:16.600 --> 00:09:17.990 align:start position:0% verifying these MPT proofs uh that is probably<00:09:16.839> you<00:09:16.959> can<00:09:17.079> do<00:09:17.200> some<00:09:17.360> benchmarking<00:09:17.839> to 00:09:17.990 --> 00:09:18.000 align:start position:0% probably you can do some benchmarking to 00:09:18.000 --> 00:09:20.630 align:start position:0% probably you can do some benchmarking to price<00:09:18.399> that<00:09:19.399> and<00:09:19.800> what's<00:09:20.000> kind<00:09:20.079> of<00:09:20.200> tricky<00:09:20.519> is 00:09:20.630 --> 00:09:20.640 align:start position:0% price that and what's kind of tricky is 00:09:20.640 --> 00:09:22.949 align:start position:0% price that and what's kind of tricky is to<00:09:21.160> price<00:09:21.480> this<00:09:21.640> RPC<00:09:22.079> latency<00:09:22.600> like<00:09:22.720> what<00:09:22.839> is 00:09:22.949 --> 00:09:22.959 align:start position:0% to price this RPC latency like what is 00:09:22.959 --> 00:09:25.590 align:start position:0% to price this RPC latency like what is the<00:09:23.120> cost<00:09:23.839> of<00:09:24.079> doing<00:09:24.360> this<00:09:24.680> RPC<00:09:25.160> query<00:09:25.440> on<00:09:25.519> the 00:09:25.590 --> 00:09:25.600 align:start position:0% the cost of doing this RPC query on the 00:09:25.600 --> 00:09:27.630 align:start position:0% the cost of doing this RPC query on the sequencer<00:09:26.440> as<00:09:26.560> opposed<00:09:26.839> to<00:09:26.959> processing<00:09:27.399> other 00:09:27.630 --> 00:09:27.640 align:start position:0% sequencer as opposed to processing other 00:09:27.640 --> 00:09:30.910 align:start position:0% sequencer as opposed to processing other transactions 00:09:30.910 --> 00:09:30.920 align:start position:0% 00:09:30.920 --> 00:09:33.870 align:start position:0% so<00:09:31.200> we<00:09:31.640> still<00:09:31.959> have<00:09:32.200> some<00:09:32.440> way<00:09:32.640> to<00:09:32.839> go<00:09:33.320> this<00:09:33.440> rip 00:09:33.870 --> 00:09:33.880 align:start position:0% so we still have some way to go this rip 00:09:33.880 --> 00:09:37.350 align:start position:0% so we still have some way to go this rip was<00:09:34.040> proposed<00:09:34.399> in<00:09:34.560> June<00:09:35.560> and<00:09:36.360> uh<00:09:37.000> it's<00:09:37.160> now 00:09:37.350 --> 00:09:37.360 align:start position:0% was proposed in June and uh it's now 00:09:37.360 --> 00:09:38.790 align:start position:0% was proposed in June and uh it's now gaining<00:09:37.600> some<00:09:37.760> traction<00:09:38.160> we've<00:09:38.320> been 00:09:38.790 --> 00:09:38.800 align:start position:0% gaining some traction we've been 00:09:38.800 --> 00:09:40.750 align:start position:0% gaining some traction we've been exploring<00:09:39.200> some<00:09:39.320> use<00:09:39.640> cases<00:09:40.320> but<00:09:40.440> the<00:09:40.560> next 00:09:40.750 --> 00:09:40.760 align:start position:0% exploring some use cases but the next 00:09:40.760 --> 00:09:43.590 align:start position:0% exploring some use cases but the next step<00:09:40.959> would<00:09:41.079> be<00:09:41.200> to<00:09:41.560> involve<00:09:41.920> more<00:09:42.640> uh<00:09:42.880> L2<00:09:43.320> dep 00:09:43.590 --> 00:09:43.600 align:start position:0% step would be to involve more uh L2 dep 00:09:43.600 --> 00:09:46.509 align:start position:0% step would be to involve more uh L2 dep developers<00:09:44.160> and<00:09:44.519> L2<00:09:44.920> protol<00:09:45.360> teams<00:09:46.000> so<00:09:46.320> as<00:09:46.399> I 00:09:46.509 --> 00:09:46.519 align:start position:0% developers and L2 protol teams so as I 00:09:46.519 --> 00:09:48.910 align:start position:0% developers and L2 protol teams so as I mentioned<00:09:46.839> we'd<00:09:47.079> love<00:09:47.200> to<00:09:47.320> hear<00:09:47.760> from<00:09:47.920> you<00:09:48.800> uh 00:09:48.910 --> 00:09:48.920 align:start position:0% mentioned we'd love to hear from you uh 00:09:48.920 --> 00:09:50.870 align:start position:0% mentioned we'd love to hear from you uh just<00:09:49.120> recently<00:09:49.519> we<00:09:49.640> set<00:09:49.800> up<00:09:49.959> a<00:09:50.120> working<00:09:50.480> group 00:09:50.870 --> 00:09:50.880 align:start position:0% just recently we set up a working group 00:09:50.880 --> 00:09:52.910 align:start position:0% just recently we set up a working group telegram<00:09:51.320> channel<00:09:52.079> so<00:09:52.360> if<00:09:52.440> you're<00:09:52.600> interested 00:09:52.910 --> 00:09:52.920 align:start position:0% telegram channel so if you're interested 00:09:52.920 --> 00:09:54.949 align:start position:0% telegram channel so if you're interested in<00:09:53.000> joining<00:09:53.360> the<00:09:53.480> discussion<00:09:54.399> feel<00:09:54.600> free<00:09:54.800> to 00:09:54.949 --> 00:09:54.959 align:start position:0% in joining the discussion feel free to 00:09:54.959 --> 00:09:57.030 align:start position:0% in joining the discussion feel free to join<00:09:55.399> if<00:09:55.519> you<00:09:55.839> cannot<00:09:56.120> join<00:09:56.320> for<00:09:56.519> some<00:09:56.680> reason 00:09:57.030 --> 00:09:57.040 align:start position:0% join if you cannot join for some reason 00:09:57.040 --> 00:09:58.829 align:start position:0% join if you cannot join for some reason then<00:09:57.200> feel<00:09:57.399> free<00:09:57.560> to<00:09:57.720> message<00:09:58.000> me<00:09:58.120> on<00:09:58.279> Twitter 00:09:58.829 --> 00:09:58.839 align:start position:0% then feel free to message me on Twitter 00:09:58.839 --> 00:09:59.829 align:start position:0% then feel free to message me on Twitter and<00:09:58.959> I<00:09:59.079> add<00:09:59.200> you 00:09:59.829 --> 00:09:59.839 align:start position:0% and I add you 00:09:59.839 --> 00:10:01.870 align:start position:0% and I add you and<00:09:59.959> I<00:10:00.120> really<00:10:00.320> hope<00:10:00.640> that<00:10:01.200> we<00:10:01.399> get<00:10:01.560> support 00:10:01.870 --> 00:10:01.880 align:start position:0% and I really hope that we get support 00:10:01.880 --> 00:10:04.269 align:start position:0% and I really hope that we get support from<00:10:02.079> at<00:10:02.200> least<00:10:02.480> one<00:10:02.680> other<00:10:02.920> L2<00:10:03.320> team<00:10:03.959> and<00:10:04.120> that 00:10:04.269 --> 00:10:04.279 align:start position:0% from at least one other L2 team and that 00:10:04.279 --> 00:10:06.069 align:start position:0% from at least one other L2 team and that we<00:10:04.399> can<00:10:04.640> ship<00:10:05.000> this<00:10:05.160> feature<00:10:05.480> on<00:10:05.680> at<00:10:05.800> least<00:10:05.959> two 00:10:06.069 --> 00:10:06.079 align:start position:0% we can ship this feature on at least two 00:10:06.079 --> 00:10:08.350 align:start position:0% we can ship this feature on at least two l2s<00:10:06.600> maybe<00:10:06.800> in 00:10:08.350 --> 00:10:08.360 align:start position:0% l2s maybe in 00:10:08.360 --> 00:10:10.509 align:start position:0% l2s maybe in 2025<00:10:09.360> and<00:10:09.519> in<00:10:09.640> this<00:10:09.800> presentation<00:10:10.240> I<00:10:10.360> also 00:10:10.509 --> 00:10:10.519 align:start position:0% 2025 and in this presentation I also 00:10:10.519 --> 00:10:12.069 align:start position:0% 2025 and in this presentation I also have<00:10:10.680> some<00:10:10.839> resources<00:10:11.440> both<00:10:11.880> uh<00:10:11.959> the 00:10:12.069 --> 00:10:12.079 align:start position:0% have some resources both uh the 00:10:12.079 --> 00:10:14.069 align:start position:0% have some resources both uh the reference<00:10:12.720> implementation<00:10:13.720> The<00:10:13.839> eth 00:10:14.069 --> 00:10:14.079 align:start position:0% reference implementation The eth 00:10:14.079 --> 00:10:17.630 align:start position:0% reference implementation The eth Magicians<00:10:14.519> link<00:10:15.399> and<00:10:15.560> we<00:10:15.720> also<00:10:16.000> have<00:10:16.240> some<00:10:17.000> uh 00:10:17.630 --> 00:10:17.640 align:start position:0% Magicians link and we also have some uh 00:10:17.640 --> 00:10:20.350 align:start position:0% Magicians link and we also have some uh resources<00:10:18.120> for<00:10:18.320> devs<00:10:18.959> uh<00:10:19.079> devnet<00:10:20.000> and<00:10:20.160> some 00:10:20.350 --> 00:10:20.360 align:start position:0% resources for devs uh devnet and some 00:10:20.360 --> 00:10:22.470 align:start position:0% resources for devs uh devnet and some example<00:10:20.800> codes<00:10:21.240> that<00:10:21.360> you<00:10:21.480> can<00:10:21.640> use<00:10:21.839> to<00:10:22.360> get 00:10:22.470 --> 00:10:22.480 align:start position:0% example codes that you can use to get 00:10:22.480 --> 00:10:23.910 align:start position:0% example codes that you can use to get some 00:10:23.910 --> 00:10:23.920 align:start position:0% some 00:10:23.920 --> 00:10:25.870 align:start position:0% some inspiration<00:10:24.920> that's<00:10:25.079> all<00:10:25.200> I<00:10:25.320> have<00:10:25.480> for<00:10:25.640> today 00:10:25.870 --> 00:10:25.880 align:start position:0% inspiration that's all I have for today 00:10:25.880 --> 00:10:27.110 align:start position:0% inspiration that's all I have for today and<00:10:26.040> I'm<00:10:26.160> looking<00:10:26.360> forward<00:10:26.680> to<00:10:26.920> your 00:10:27.110 --> 00:10:27.120 align:start position:0% and I'm looking forward to your 00:10:27.120 --> 00:10:31.190 align:start position:0% and I'm looking forward to your questions<00:10:27.839> thank<00:10:28.000> you 00:10:31.190 --> 00:10:31.200 align:start position:0% 00:10:31.200 --> 00:10:33.550 align:start position:0% thank<00:10:31.360> you<00:10:31.519> Peter<00:10:32.120> we<00:10:32.320> have<00:10:32.440> a<00:10:32.560> few<00:10:32.839> questions 00:10:33.550 --> 00:10:33.560 align:start position:0% thank you Peter we have a few questions 00:10:33.560 --> 00:10:36.750 align:start position:0% thank you Peter we have a few questions so<00:10:34.320> first<00:10:34.640> question<00:10:34.920> is<00:10:35.440> what<00:10:35.639> happens<00:10:36.079> when<00:10:36.480> I 00:10:36.750 --> 00:10:36.760 align:start position:0% so first question is what happens when I 00:10:36.760 --> 00:10:40.350 align:start position:0% so first question is what happens when I load<00:10:37.160> a<00:10:37.360> state<00:10:37.639> from<00:10:37.839> L1<00:10:38.360> but<00:10:38.519> then<00:10:38.680> L1 00:10:40.350 --> 00:10:40.360 align:start position:0% load a state from L1 but then L1 00:10:40.360 --> 00:10:42.509 align:start position:0% load a state from L1 but then L1 reorgs<00:10:41.360> yeah<00:10:41.519> that's<00:10:41.639> a<00:10:41.800> good<00:10:42.000> question<00:10:42.320> so 00:10:42.509 --> 00:10:42.519 align:start position:0% reorgs yeah that's a good question so 00:10:42.519 --> 00:10:44.790 align:start position:0% reorgs yeah that's a good question so the<00:10:42.680> question<00:10:42.959> is<00:10:43.639> uh<00:10:43.800> when<00:10:43.959> does<00:10:44.160> the 00:10:44.790 --> 00:10:44.800 align:start position:0% the question is uh when does the 00:10:44.800 --> 00:10:47.670 align:start position:0% the question is uh when does the sequencer<00:10:45.800> relay<00:10:46.480> this<00:10:46.680> if<00:10:46.800> the<00:10:46.959> sequencer<00:10:47.440> is 00:10:47.670 --> 00:10:47.680 align:start position:0% sequencer relay this if the sequencer is 00:10:47.680 --> 00:10:50.150 align:start position:0% sequencer relay this if the sequencer is conservative<00:10:48.240> and<00:10:48.360> it<00:10:48.480> weighs<00:10:48.800> for<00:10:49.279> L1<00:10:49.720> to 00:10:50.150 --> 00:10:50.160 align:start position:0% conservative and it weighs for L1 to 00:10:50.160 --> 00:10:53.509 align:start position:0% conservative and it weighs for L1 to finalize<00:10:51.160> then<00:10:51.560> this<00:10:51.680> won't<00:10:52.000> happen<00:10:53.000> but<00:10:53.360> then 00:10:53.509 --> 00:10:53.519 align:start position:0% finalize then this won't happen but then 00:10:53.519 --> 00:10:54.829 align:start position:0% finalize then this won't happen but then the<00:10:53.600> user<00:10:53.880> experience<00:10:54.200> is<00:10:54.320> not<00:10:54.480> very<00:10:54.639> good 00:10:54.829 --> 00:10:54.839 align:start position:0% the user experience is not very good 00:10:54.839 --> 00:10:57.389 align:start position:0% the user experience is not very good because<00:10:55.040> the<00:10:55.120> latency<00:10:55.639> is<00:10:56.200> uh<00:10:56.519> 12<00:10:56.880> to<00:10:57.079> 15 00:10:57.389 --> 00:10:57.399 align:start position:0% because the latency is uh 12 to 15 00:10:57.399 --> 00:11:00.310 align:start position:0% because the latency is uh 12 to 15 minutes<00:10:58.200> if<00:10:58.320> the<00:10:58.440> sequencer<00:10:59.680> uh<00:10:59.800> relays<00:11:00.200> it 00:11:00.310 --> 00:11:00.320 align:start position:0% minutes if the sequencer uh relays it 00:11:00.320 --> 00:11:02.350 align:start position:0% minutes if the sequencer uh relays it earlier<00:11:00.760> maybe<00:11:00.959> after<00:11:01.160> a<00:11:01.240> couple<00:11:01.440> of<00:11:01.560> minutes 00:11:02.350 --> 00:11:02.360 align:start position:0% earlier maybe after a couple of minutes 00:11:02.360 --> 00:11:05.870 align:start position:0% earlier maybe after a couple of minutes then<00:11:02.839> us<00:11:03.079> ASD<00:11:03.360> L2<00:11:03.800> need<00:11:03.959> to<00:11:04.399> be<00:11:04.639> reorg<00:11:05.040> aware<00:11:05.760> so 00:11:05.870 --> 00:11:05.880 align:start position:0% then us ASD L2 need to be reorg aware so 00:11:05.880 --> 00:11:07.150 align:start position:0% then us ASD L2 need to be reorg aware so you<00:11:06.000> need<00:11:06.120> to<00:11:06.240> detect<00:11:06.519> reorgs<00:11:06.880> and<00:11:06.959> you<00:11:07.040> need 00:11:07.150 --> 00:11:07.160 align:start position:0% you need to detect reorgs and you need 00:11:07.160 --> 00:11:09.790 align:start position:0% you need to detect reorgs and you need to<00:11:07.560> reor<00:11:08.079> along<00:11:08.920> uh<00:11:09.040> with<00:11:09.200> the<00:11:09.480> one<00:11:09.600> most 00:11:09.790 --> 00:11:09.800 align:start position:0% to reor along uh with the one most 00:11:09.800 --> 00:11:11.590 align:start position:0% to reor along uh with the one most likely<00:11:10.480> but<00:11:10.639> I<00:11:10.760> think<00:11:11.000> this<00:11:11.079> is<00:11:11.240> the<00:11:11.360> same 00:11:11.590 --> 00:11:11.600 align:start position:0% likely but I think this is the same 00:11:11.600 --> 00:11:14.389 align:start position:0% likely but I think this is the same problem<00:11:11.880> that<00:11:12.000> l2s<00:11:12.480> have<00:11:12.720> with<00:11:13.200> uh<00:11:13.399> deposits 00:11:14.389 --> 00:11:14.399 align:start position:0% problem that l2s have with uh deposits 00:11:14.399 --> 00:11:16.910 align:start position:0% problem that l2s have with uh deposits so<00:11:15.040> any<00:11:15.360> information<00:11:15.880> that<00:11:16.160> relate<00:11:16.519> from<00:11:16.639> L1 00:11:16.910 --> 00:11:16.920 align:start position:0% so any information that relate from L1 00:11:16.920 --> 00:11:19.269 align:start position:0% so any information that relate from L1 to<00:11:17.040> L2<00:11:17.399> be<00:11:17.519> it<00:11:17.639> L1<00:11:17.920> s<00:11:18.120> load<00:11:18.360> or<00:11:18.880> deposit 00:11:19.269 --> 00:11:19.279 align:start position:0% to L2 be it L1 s load or deposit 00:11:19.279 --> 00:11:21.629 align:start position:0% to L2 be it L1 s load or deposit transactions<00:11:19.839> have<00:11:20.000> the<00:11:20.079> same 00:11:21.629 --> 00:11:21.639 align:start position:0% transactions have the same 00:11:21.639 --> 00:11:25.069 align:start position:0% transactions have the same issue<00:11:22.639> okay<00:11:23.440> NE<00:11:23.760> next<00:11:24.079> question<00:11:24.440> is<00:11:24.800> what<00:11:24.920> is 00:11:25.069 --> 00:11:25.079 align:start position:0% issue okay NE next question is what is 00:11:25.079 --> 00:11:27.509 align:start position:0% issue okay NE next question is what is the<00:11:25.240> latency<00:11:25.760> of<00:11:25.959> data<00:11:26.279> relay<00:11:26.720> from<00:11:27.040> ethereum 00:11:27.509 --> 00:11:27.519 align:start position:0% the latency of data relay from ethereum 00:11:27.519 --> 00:11:30.269 align:start position:0% the latency of data relay from ethereum to<00:11:27.920> L2 00:11:30.269 --> 00:11:30.279 align:start position:0% to L2 00:11:30.279 --> 00:11:33.110 align:start position:0% to L2 yeah<00:11:30.399> so<00:11:30.639> that's<00:11:31.560> essentially<00:11:32.560> it<00:11:32.720> boyss<00:11:33.000> down 00:11:33.110 --> 00:11:33.120 align:start position:0% yeah so that's essentially it boyss down 00:11:33.120 --> 00:11:34.710 align:start position:0% yeah so that's essentially it boyss down to<00:11:33.240> the<00:11:33.320> same<00:11:33.560> question<00:11:33.959> like<00:11:34.200> if<00:11:34.279> you<00:11:34.399> want<00:11:34.519> to 00:11:34.710 --> 00:11:34.720 align:start position:0% to the same question like if you want to 00:11:34.720 --> 00:11:36.030 align:start position:0% to the same question like if you want to be<00:11:34.920> conservative<00:11:35.480> just<00:11:35.639> wait<00:11:35.800> for 00:11:36.030 --> 00:11:36.040 align:start position:0% be conservative just wait for 00:11:36.040 --> 00:11:38.629 align:start position:0% be conservative just wait for finalization<00:11:37.040> if<00:11:37.200> not<00:11:37.399> you<00:11:37.519> need<00:11:37.680> to<00:11:38.160> reor 00:11:38.629 --> 00:11:38.639 align:start position:0% finalization if not you need to reor 00:11:38.639 --> 00:11:43.030 align:start position:0% finalization if not you need to reor along<00:11:38.880> with<00:11:39.680> L1<00:11:40.959> um<00:11:41.959> in<00:11:42.160> reality<00:11:42.519> it's<00:11:42.680> not 00:11:43.030 --> 00:11:43.040 align:start position:0% along with L1 um in reality it's not 00:11:43.040 --> 00:11:46.310 align:start position:0% along with L1 um in reality it's not terrible<00:11:44.040> because<00:11:45.040> I<00:11:45.160> think<00:11:45.399> L1<00:11:45.800> hasn't<00:11:46.079> had<00:11:46.200> a 00:11:46.310 --> 00:11:46.320 align:start position:0% terrible because I think L1 hasn't had a 00:11:46.320 --> 00:11:49.069 align:start position:0% terrible because I think L1 hasn't had a reor<00:11:46.680> deeper<00:11:47.000> than<00:11:47.160> seven<00:11:47.600> slots<00:11:48.320> or<00:11:48.519> is 00:11:49.069 --> 00:11:49.079 align:start position:0% reor deeper than seven slots or is 00:11:49.079 --> 00:11:51.750 align:start position:0% reor deeper than seven slots or is extremely<00:11:49.519> unlikely<00:11:50.519> so<00:11:51.200> as<00:11:51.320> long<00:11:51.519> as<00:11:51.639> you 00:11:51.750 --> 00:11:51.760 align:start position:0% extremely unlikely so as long as you 00:11:51.760 --> 00:11:53.629 align:start position:0% extremely unlikely so as long as you have<00:11:51.880> a<00:11:52.040> mechanism<00:11:52.560> to<00:11:52.839> reor<00:11:53.279> if<00:11:53.399> there's<00:11:53.519> a 00:11:53.629 --> 00:11:53.639 align:start position:0% have a mechanism to reor if there's a 00:11:53.639 --> 00:11:55.430 align:start position:0% have a mechanism to reor if there's a deeper<00:11:53.880> RoR<00:11:54.320> then<00:11:54.760> this<00:11:54.880> won't<00:11:55.160> really<00:11:55.320> be 00:11:55.430 --> 00:11:55.440 align:start position:0% deeper RoR then this won't really be 00:11:55.440 --> 00:11:57.790 align:start position:0% deeper RoR then this won't really be triggered<00:11:55.839> in<00:11:56.040> most<00:11:56.519> scenarios<00:11:57.519> but<00:11:57.639> there's 00:11:57.790 --> 00:11:57.800 align:start position:0% triggered in most scenarios but there's 00:11:57.800 --> 00:11:59.230 align:start position:0% triggered in most scenarios but there's still<00:11:58.000> the<00:11:58.079> issue<00:11:58.320> on<00:11:58.600> one<00:11:58.680> of<00:11:58.800> the<00:11:58.920> Ina 00:11:59.230 --> 00:11:59.240 align:start position:0% still the issue on one of the Ina 00:11:59.240 --> 00:12:01.590 align:start position:0% still the issue on one of the Ina activity<00:11:59.560> leak<00:11:59.880> what<00:12:00.000> if<00:12:00.680> L1<00:12:01.320> doesn't 00:12:01.590 --> 00:12:01.600 align:start position:0% activity leak what if L1 doesn't 00:12:01.600 --> 00:12:03.670 align:start position:0% activity leak what if L1 doesn't finalize<00:12:02.000> for<00:12:02.079> a<00:12:02.200> long<00:12:02.360> time<00:12:02.880> in<00:12:03.000> this<00:12:03.160> case 00:12:03.670 --> 00:12:03.680 align:start position:0% finalize for a long time in this case 00:12:03.680 --> 00:12:05.670 align:start position:0% finalize for a long time in this case definitely<00:12:04.680> being<00:12:04.880> more<00:12:05.040> aggressive<00:12:05.399> and<00:12:05.519> not 00:12:05.670 --> 00:12:05.680 align:start position:0% definitely being more aggressive and not 00:12:05.680 --> 00:12:07.030 align:start position:0% definitely being more aggressive and not waiting<00:12:05.920> for<00:12:06.079> finalization<00:12:06.720> would<00:12:06.839> be<00:12:06.920> the 00:12:07.030 --> 00:12:07.040 align:start position:0% waiting for finalization would be the 00:12:07.040 --> 00:12:08.470 align:start position:0% waiting for finalization would be the way<00:12:07.200> to<00:12:07.320> go<00:12:07.519> otherwise<00:12:07.839> user<00:12:08.120> experience 00:12:08.470 --> 00:12:08.480 align:start position:0% way to go otherwise user experience 00:12:08.480 --> 00:12:10.110 align:start position:0% way to go otherwise user experience would 00:12:10.110 --> 00:12:10.120 align:start position:0% would 00:12:10.120 --> 00:12:13.829 align:start position:0% would suffer<00:12:11.120> okay<00:12:12.040> next<00:12:12.440> question<00:12:13.000> is<00:12:13.440> why<00:12:13.560> is<00:12:13.680> it 00:12:13.829 --> 00:12:13.839 align:start position:0% suffer okay next question is why is it 00:12:13.839 --> 00:12:15.949 align:start position:0% suffer okay next question is why is it only<00:12:14.120> limited<00:12:14.480> to<00:12:14.680> five 00:12:15.949 --> 00:12:15.959 align:start position:0% only limited to five 00:12:15.959 --> 00:12:18.030 align:start position:0% only limited to five Keys<00:12:16.959> yeah<00:12:17.120> that's<00:12:17.240> a<00:12:17.360> good<00:12:17.519> question<00:12:17.800> do<00:12:17.920> you 00:12:18.030 --> 00:12:18.040 align:start position:0% Keys yeah that's a good question do you 00:12:18.040 --> 00:12:21.069 align:start position:0% Keys yeah that's a good question do you need<00:12:18.320> more<00:12:18.480> than<00:12:18.680> five<00:12:19.360> keys<00:12:20.360> if<00:12:20.600> yes<00:12:20.880> then 00:12:21.069 --> 00:12:21.079 align:start position:0% need more than five keys if yes then 00:12:21.079 --> 00:12:23.550 align:start position:0% need more than five keys if yes then please<00:12:21.279> let<00:12:21.440> us<00:12:21.639> know<00:12:22.399> five<00:12:22.920> is<00:12:23.199> was<00:12:23.320> just<00:12:23.440> an 00:12:23.550 --> 00:12:23.560 align:start position:0% please let us know five is was just an 00:12:23.560 --> 00:12:25.150 align:start position:0% please let us know five is was just an arbitrary<00:12:24.000> number<00:12:24.320> we<00:12:24.440> didn't<00:12:24.600> want<00:12:24.720> to<00:12:25.040> make 00:12:25.150 --> 00:12:25.160 align:start position:0% arbitrary number we didn't want to make 00:12:25.160 --> 00:12:28.110 align:start position:0% arbitrary number we didn't want to make it<00:12:25.639> unbounded<00:12:26.639> uh<00:12:26.720> for<00:12:26.959> most<00:12:27.399> application<00:12:27.839> use 00:12:28.110 --> 00:12:28.120 align:start position:0% it unbounded uh for most application use 00:12:28.120 --> 00:12:29.870 align:start position:0% it unbounded uh for most application use cases<00:12:28.360> that<00:12:28.519> we<00:12:28.800> explor 00:12:29.870 --> 00:12:29.880 align:start position:0% cases that we explor 00:12:29.880 --> 00:12:31.870 align:start position:0% cases that we explor five<00:12:30.120> or<00:12:30.320> less<00:12:30.600> was<00:12:30.920> enough<00:12:31.320> but<00:12:31.519> if<00:12:31.600> you<00:12:31.760> think 00:12:31.870 --> 00:12:31.880 align:start position:0% five or less was enough but if you think 00:12:31.880 --> 00:12:33.670 align:start position:0% five or less was enough but if you think it's<00:12:32.040> not<00:12:32.240> enough<00:12:32.560> then<00:12:33.160> uh<00:12:33.279> this<00:12:33.360> is<00:12:33.480> still 00:12:33.670 --> 00:12:33.680 align:start position:0% it's not enough then uh this is still 00:12:33.680 --> 00:12:36.350 align:start position:0% it's not enough then uh this is still draft<00:12:34.040> so<00:12:34.279> we<00:12:34.360> can<00:12:34.519> still<00:12:34.720> change 00:12:36.350 --> 00:12:36.360 align:start position:0% draft so we can still change 00:12:36.360 --> 00:12:41.230 align:start position:0% draft so we can still change it<00:12:37.600> okay<00:12:38.600> uh<00:12:39.279> which<00:12:39.560> state<00:12:40.320> or<00:12:40.600> block<00:12:41.000> does 00:12:41.230 --> 00:12:41.240 align:start position:0% it okay uh which state or block does 00:12:41.240 --> 00:12:43.829 align:start position:0% it okay uh which state or block does this<00:12:41.440> op<00:12:41.760> code<00:12:41.920> load<00:12:42.199> form<00:12:43.000> uh<00:12:43.199> is<00:12:43.320> it<00:12:43.600> the 00:12:43.829 --> 00:12:43.839 align:start position:0% this op code load form uh is it the 00:12:43.839 --> 00:12:45.430 align:start position:0% this op code load form uh is it the latest<00:12:44.279> ethereum 00:12:45.430 --> 00:12:45.440 align:start position:0% latest ethereum 00:12:45.440 --> 00:12:47.990 align:start position:0% latest ethereum block<00:12:46.440> it<00:12:46.560> is<00:12:46.720> the<00:12:46.880> latest<00:12:47.240> ethereum<00:12:47.639> block 00:12:47.990 --> 00:12:48.000 align:start position:0% block it is the latest ethereum block 00:12:48.000 --> 00:12:51.829 align:start position:0% block it is the latest ethereum block that<00:12:48.240> this<00:12:48.399> L2<00:12:49.040> blockchain<00:12:49.480> knows<00:12:49.760> of<00:12:50.760> so<00:12:51.560> um 00:12:51.829 --> 00:12:51.839 align:start position:0% that this L2 blockchain knows of so um 00:12:51.839 --> 00:12:54.110 align:start position:0% that this L2 blockchain knows of so um there<00:12:51.959> needs<00:12:52.160> to<00:12:52.320> be<00:12:52.800> on<00:12:52.920> this<00:12:53.079> L2<00:12:53.440> Network<00:12:53.959> it 00:12:54.110 --> 00:12:54.120 align:start position:0% there needs to be on this L2 Network it 00:12:54.120 --> 00:12:55.949 align:start position:0% there needs to be on this L2 Network it has<00:12:54.279> multiple<00:12:54.639> notes<00:12:55.079> sequencer<00:12:55.560> and<00:12:55.680> follow 00:12:55.949 --> 00:12:55.959 align:start position:0% has multiple notes sequencer and follow 00:12:55.959 --> 00:12:57.910 align:start position:0% has multiple notes sequencer and follow notes<00:12:56.519> they<00:12:56.639> need<00:12:56.760> to<00:12:56.880> have<00:12:57.000> a<00:12:57.120> consensus 00:12:57.910 --> 00:12:57.920 align:start position:0% notes they need to have a consensus 00:12:57.920 --> 00:12:59.629 align:start position:0% notes they need to have a consensus about<00:12:58.160> what<00:12:58.240> is<00:12:58.399> the<00:12:58.560> latest<00:12:58.880> l<00:12:59.199> one<00:12:59.399> block 00:12:59.629 --> 00:12:59.639 align:start position:0% about what is the latest l one block 00:12:59.639 --> 00:13:03.750 align:start position:0% about what is the latest l one block that<00:12:59.839> they<00:13:00.240> see<00:13:01.560> otherwise<00:13:02.560> uh<00:13:02.760> execution<00:13:03.560> to 00:13:03.750 --> 00:13:03.760 align:start position:0% that they see otherwise uh execution to 00:13:03.760 --> 00:13:06.269 align:start position:0% that they see otherwise uh execution to cuse<00:13:04.040> to<00:13:04.160> this<00:13:04.320> pre<00:13:04.560> compile<00:13:04.839> would<00:13:05.279> diverge 00:13:06.269 --> 00:13:06.279 align:start position:0% cuse to this pre compile would diverge 00:13:06.279 --> 00:13:07.430 align:start position:0% cuse to this pre compile would diverge but<00:13:06.440> this<00:13:06.560> could<00:13:06.680> be<00:13:06.839> implemented<00:13:07.320> in 00:13:07.430 --> 00:13:07.440 align:start position:0% but this could be implemented in 00:13:07.440 --> 00:13:09.110 align:start position:0% but this could be implemented in different<00:13:07.720> ways<00:13:07.920> I<00:13:08.040> mentioned<00:13:08.360> this<00:13:08.519> as<00:13:09.000> uh 00:13:09.110 --> 00:13:09.120 align:start position:0% different ways I mentioned this as uh 00:13:09.120 --> 00:13:11.269 align:start position:0% different ways I mentioned this as uh one<00:13:09.279> of<00:13:09.360> the<00:13:09.680> prerequisites<00:13:10.680> and<00:13:10.839> I<00:13:10.920> would<00:13:11.079> say 00:13:11.269 --> 00:13:11.279 align:start position:0% one of the prerequisites and I would say 00:13:11.279 --> 00:13:13.949 align:start position:0% one of the prerequisites and I would say this<00:13:11.360> is<00:13:11.519> not<00:13:11.680> in<00:13:11.839> the<00:13:12.120> scope<00:13:13.120> uh<00:13:13.240> of<00:13:13.399> this<00:13:13.519> Rip 00:13:13.949 --> 00:13:13.959 align:start position:0% this is not in the scope uh of this Rip 00:13:13.959 --> 00:13:15.269 align:start position:0% this is not in the scope uh of this Rip but<00:13:14.079> it's<00:13:14.199> a<00:13:14.320> prerequisite<00:13:14.880> that<00:13:15.000> could<00:13:15.160> be 00:13:15.269 --> 00:13:15.279 align:start position:0% but it's a prerequisite that could be 00:13:15.279 --> 00:13:16.470 align:start position:0% but it's a prerequisite that could be implemented<00:13:15.720> in<00:13:15.880> different<00:13:16.120> ways<00:13:16.320> for 00:13:16.470 --> 00:13:16.480 align:start position:0% implemented in different ways for 00:13:16.480 --> 00:13:17.949 align:start position:0% implemented in different ways for different 00:13:17.949 --> 00:13:17.959 align:start position:0% different 00:13:17.959 --> 00:13:21.870 align:start position:0% different rollups<00:13:19.360> okay<00:13:20.360> uh<00:13:20.880> what<00:13:21.040> happens<00:13:21.440> if<00:13:21.600> there<00:13:21.760> is 00:13:21.870 --> 00:13:21.880 align:start position:0% rollups okay uh what happens if there is 00:13:21.880 --> 00:13:24.670 align:start position:0% rollups okay uh what happens if there is a<00:13:22.040> small<00:13:22.320> reorg<00:13:22.920> for<00:13:23.279> the<00:13:23.519> specific<00:13:23.959> L1<00:13:24.399> node 00:13:24.670 --> 00:13:24.680 align:start position:0% a small reorg for the specific L1 node 00:13:24.680 --> 00:13:27.790 align:start position:0% a small reorg for the specific L1 node at<00:13:24.839> the<00:13:25.000> tip<00:13:25.720> then<00:13:26.079> the<00:13:26.320> L2<00:13:26.760> sequencer<00:13:27.360> would 00:13:27.790 --> 00:13:27.800 align:start position:0% at the tip then the L2 sequencer would 00:13:27.800 --> 00:13:30.430 align:start position:0% at the tip then the L2 sequencer would process<00:13:28.160> incorrect<00:13:28.600> data<00:13:28.920> to<00:13:29.120> to<00:13:29.199> the<00:13:29.320> L2<00:13:30.320> how 00:13:30.430 --> 00:13:30.440 align:start position:0% process incorrect data to to the L2 how 00:13:30.440 --> 00:13:32.710 align:start position:0% process incorrect data to to the L2 how would<00:13:30.760> execution<00:13:31.279> continue<00:13:31.760> on<00:13:31.920> the 00:13:32.710 --> 00:13:32.720 align:start position:0% would execution continue on the 00:13:32.720 --> 00:13:35.189 align:start position:0% would execution continue on the L2<00:13:33.720> yeah<00:13:33.880> same<00:13:34.120> question<00:13:34.399> as<00:13:34.600> before<00:13:34.920> so<00:13:35.079> you 00:13:35.189 --> 00:13:35.199 align:start position:0% L2 yeah same question as before so you 00:13:35.199 --> 00:13:37.550 align:start position:0% L2 yeah same question as before so you would<00:13:35.360> need<00:13:35.560> to<00:13:36.360> most<00:13:36.600> likely<00:13:36.839> reor<00:13:37.320> along 00:13:37.550 --> 00:13:37.560 align:start position:0% would need to most likely reor along 00:13:37.560 --> 00:13:38.750 align:start position:0% would need to most likely reor along with<00:13:37.680> that 00:13:38.750 --> 00:13:38.760 align:start position:0% with that 00:13:38.760 --> 00:13:41.829 align:start position:0% with that one<00:13:39.760> okay<00:13:40.519> how<00:13:40.639> do<00:13:40.760> you<00:13:40.920> configure<00:13:41.399> switching 00:13:41.829 --> 00:13:41.839 align:start position:0% one okay how do you configure switching 00:13:41.839 --> 00:13:45.350 align:start position:0% one okay how do you configure switching the<00:13:42.000> RPC<00:13:42.560> node<00:13:42.839> on<00:13:43.000> a<00:13:43.199> live<00:13:43.560> e 00:13:45.350 --> 00:13:45.360 align:start position:0% the RPC node on a live e 00:13:45.360 --> 00:13:47.750 align:start position:0% the RPC node on a live e sequencer<00:13:46.360> how<00:13:46.519> do<00:13:46.600> you<00:13:46.720> configure 00:13:47.750 --> 00:13:47.760 align:start position:0% sequencer how do you configure 00:13:47.760 --> 00:13:51.269 align:start position:0% sequencer how do you configure switching<00:13:48.760> well<00:13:48.920> I<00:13:49.440> mean<00:13:50.440> you<00:13:50.560> can<00:13:50.720> get<00:13:50.880> fancy 00:13:51.269 --> 00:13:51.279 align:start position:0% switching well I mean you can get fancy 00:13:51.279 --> 00:13:52.949 align:start position:0% switching well I mean you can get fancy I<00:13:51.320> mean<00:13:51.440> the<00:13:51.560> easiest<00:13:52.000> solution<00:13:52.320> is<00:13:52.600> to<00:13:52.759> just 00:13:52.949 --> 00:13:52.959 align:start position:0% I mean the easiest solution is to just 00:13:52.959 --> 00:13:55.030 align:start position:0% I mean the easiest solution is to just compare<00:13:53.639> connect<00:13:53.920> to<00:13:54.079> one<00:13:54.240> node<00:13:54.560> but 00:13:55.030 --> 00:13:55.040 align:start position:0% compare connect to one node but 00:13:55.040 --> 00:13:56.470 align:start position:0% compare connect to one node but obviously<00:13:55.399> that's<00:13:55.560> not<00:13:55.759> robust<00:13:56.160> what<00:13:56.240> if<00:13:56.360> the 00:13:56.470 --> 00:13:56.480 align:start position:0% obviously that's not robust what if the 00:13:56.480 --> 00:13:58.749 align:start position:0% obviously that's not robust what if the node<00:13:56.680> is<00:13:56.839> down<00:13:57.639> so<00:13:58.000> ideally<00:13:58.320> you<00:13:58.399> would<00:13:58.560> set<00:13:58.680> up 00:13:58.749 --> 00:13:58.759 align:start position:0% node is down so ideally you would set up 00:13:58.759 --> 00:14:02.910 align:start position:0% node is down so ideally you would set up multip<00:13:59.519> L1<00:13:59.839> RPC<00:14:00.360> nodes<00:14:01.360> U<00:14:02.000> ideally<00:14:02.480> multiple 00:14:02.910 --> 00:14:02.920 align:start position:0% multip L1 RPC nodes U ideally multiple 00:14:02.920 --> 00:14:05.030 align:start position:0% multip L1 RPC nodes U ideally multiple types<00:14:03.120> of<00:14:03.240> L1<00:14:03.600> clients<00:14:04.320> and<00:14:04.440> then<00:14:04.560> have<00:14:04.680> a<00:14:04.759> load 00:14:05.030 --> 00:14:05.040 align:start position:0% types of L1 clients and then have a load 00:14:05.040 --> 00:14:07.310 align:start position:0% types of L1 clients and then have a load balancer<00:14:05.920> and<00:14:06.079> then<00:14:06.240> you<00:14:06.360> can<00:14:06.560> dynamically 00:14:07.310 --> 00:14:07.320 align:start position:0% balancer and then you can dynamically 00:14:07.320 --> 00:14:11.350 align:start position:0% balancer and then you can dynamically switch<00:14:07.639> off<00:14:07.920> and<00:14:08.160> add<00:14:08.759> nodes<00:14:09.759> uh<00:14:10.360> that's 00:14:11.350 --> 00:14:11.360 align:start position:0% switch off and add nodes uh that's 00:14:11.360 --> 00:14:13.030 align:start position:0% switch off and add nodes uh that's robust<00:14:11.720> for<00:14:11.839> the<00:14:11.920> sequencer<00:14:12.399> and<00:14:12.519> for<00:14:12.680> L2 00:14:13.030 --> 00:14:13.040 align:start position:0% robust for the sequencer and for L2 00:14:13.040 --> 00:14:15.069 align:start position:0% robust for the sequencer and for L2 nodes<00:14:13.600> probably<00:14:13.959> it's<00:14:14.199> enough<00:14:14.399> to<00:14:14.600> just<00:14:14.920> uh 00:14:15.069 --> 00:14:15.079 align:start position:0% nodes probably it's enough to just uh 00:14:15.079 --> 00:14:16.870 align:start position:0% nodes probably it's enough to just uh run<00:14:15.240> a<00:14:15.399> sing<00:14:15.600> Single<00:14:15.880> a<00:14:16.079> one 00:14:16.870 --> 00:14:16.880 align:start position:0% run a sing Single a one 00:14:16.880 --> 00:14:20.590 align:start position:0% run a sing Single a one Noe<00:14:17.880> okay<00:14:18.800> um<00:14:19.240> is<00:14:19.360> this<00:14:19.560> the<00:14:19.680> same<00:14:19.959> as<00:14:20.120> the 00:14:20.590 --> 00:14:20.600 align:start position:0% Noe okay um is this the same as the 00:14:20.600 --> 00:14:22.310 align:start position:0% Noe okay um is this the same as the previous<00:14:21.000> questions<00:14:21.440> or<00:14:21.600> is<00:14:21.720> this<00:14:21.920> separate 00:14:22.310 --> 00:14:22.320 align:start position:0% previous questions or is this separate 00:14:22.320 --> 00:14:24.590 align:start position:0% previous questions or is this separate question<00:14:22.759> when<00:14:22.959> I<00:14:23.160> load<00:14:23.519> L1<00:14:23.920> stage<00:14:24.279> should<00:14:24.440> I 00:14:24.590 --> 00:14:24.600 align:start position:0% question when I load L1 stage should I 00:14:24.600 --> 00:14:26.829 align:start position:0% question when I load L1 stage should I specify<00:14:25.000> L1<00:14:25.480> block<00:14:25.720> number<00:14:26.240> it's<00:14:26.360> a<00:14:26.480> different 00:14:26.829 --> 00:14:26.839 align:start position:0% specify L1 block number it's a different 00:14:26.839 --> 00:14:29.430 align:start position:0% specify L1 block number it's a different question<00:14:27.720> in<00:14:27.880> the<00:14:28.040> current<00:14:28.759> version<00:14:29.240> of<00:14:29.320> the 00:14:29.430 --> 00:14:29.440 align:start position:0% question in the current version of the 00:14:29.440 --> 00:14:32.389 align:start position:0% question in the current version of the spec<00:14:29.720> you<00:14:29.880> cannot<00:14:30.199> specify<00:14:30.560> an<00:14:30.680> A1<00:14:31.279> number<00:14:32.279> in 00:14:32.389 --> 00:14:32.399 align:start position:0% spec you cannot specify an A1 number in 00:14:32.399 --> 00:14:34.430 align:start position:0% spec you cannot specify an A1 number in a<00:14:32.560> previous<00:14:32.880> version<00:14:33.199> you<00:14:33.399> could<00:14:33.959> so<00:14:34.240> as<00:14:34.320> I 00:14:34.430 --> 00:14:34.440 align:start position:0% a previous version you could so as I 00:14:34.440 --> 00:14:35.629 align:start position:0% a previous version you could so as I mentioned<00:14:34.759> this<00:14:34.839> is<00:14:34.959> one<00:14:35.079> of<00:14:35.199> the<00:14:35.279> open 00:14:35.629 --> 00:14:35.639 align:start position:0% mentioned this is one of the open 00:14:35.639 --> 00:14:38.069 align:start position:0% mentioned this is one of the open questions<00:14:36.639> and<00:14:37.079> I<00:14:37.199> guess<00:14:37.320> we<00:14:37.639> need<00:14:37.759> to<00:14:37.880> learn 00:14:38.069 --> 00:14:38.079 align:start position:0% questions and I guess we need to learn 00:14:38.079 --> 00:14:40.350 align:start position:0% questions and I guess we need to learn more<00:14:38.320> for<00:14:38.600> from<00:14:38.839> developers<00:14:39.360> to<00:14:39.839> decide<00:14:40.160> which 00:14:40.350 --> 00:14:40.360 align:start position:0% more for from developers to decide which 00:14:40.360 --> 00:14:41.710 align:start position:0% more for from developers to decide which way<00:14:40.519> to 00:14:41.710 --> 00:14:41.720 align:start position:0% way to 00:14:41.720 --> 00:14:46.310 align:start position:0% way to go<00:14:42.720> okay<00:14:43.279> uh<00:14:43.440> when<00:14:43.680> will<00:14:44.279> will<00:14:44.519> when<00:14:44.720> will<00:14:45.199> s<00:14:45.720> L1 00:14:46.310 --> 00:14:46.320 align:start position:0% go okay uh when will will when will s L1 00:14:46.320 --> 00:14:50.749 align:start position:0% go okay uh when will will when will s L1 s<00:14:46.600> load<00:14:47.000> be<00:14:47.199> available<00:14:47.600> on<00:14:48.160> mainnet<00:14:49.560> soon<00:14:50.560> I 00:14:50.749 --> 00:14:50.759 align:start position:0% s load be available on mainnet soon I 00:14:50.759 --> 00:14:53.230 align:start position:0% s load be available on mainnet soon I hope<00:14:51.279> so<00:14:51.800> but<00:14:52.199> this<00:14:52.320> is<00:14:52.440> not<00:14:52.600> very<00:14:52.759> useful<00:14:53.120> if 00:14:53.230 --> 00:14:53.240 align:start position:0% hope so but this is not very useful if 00:14:53.240 --> 00:14:55.509 align:start position:0% hope so but this is not very useful if only<00:14:53.399> one<00:14:53.519> rollup<00:14:53.880> ships<00:14:54.160> it<00:14:54.399> so<00:14:55.000> I<00:14:55.160> hope<00:14:55.399> at 00:14:55.509 --> 00:14:55.519 align:start position:0% only one rollup ships it so I hope at 00:14:55.519 --> 00:14:58.590 align:start position:0% only one rollup ships it so I hope at least<00:14:55.720> two<00:14:56.160> rollups<00:14:56.839> can<00:14:56.959> ship<00:14:57.199> it<00:14:57.399> next<00:14:57.639> year 00:14:58.590 --> 00:14:58.600 align:start position:0% least two rollups can ship it next year 00:14:58.600 --> 00:15:00.550 align:start position:0% least two rollups can ship it next year somebody<00:14:58.880> want<00:14:59.040> wants<00:14:59.199> to<00:14:59.279> know<00:14:59.480> what<00:14:59.600> is 00:15:00.550 --> 00:15:00.560 align:start position:0% somebody want wants to know what is 00:15:00.560 --> 00:15:03.310 align:start position:0% somebody want wants to know what is RP<00:15:01.560> so<00:15:01.720> rip<00:15:02.120> stands<00:15:02.320> for<00:15:02.480> rollup<00:15:02.839> Improvement 00:15:03.310 --> 00:15:03.320 align:start position:0% RP so rip stands for rollup Improvement 00:15:03.320 --> 00:15:05.269 align:start position:0% RP so rip stands for rollup Improvement proposal<00:15:04.079> this<00:15:04.199> is<00:15:04.360> similar<00:15:04.639> to<00:15:04.759> the<00:15:04.880> EIP 00:15:05.269 --> 00:15:05.279 align:start position:0% proposal this is similar to the EIP 00:15:05.279 --> 00:15:07.470 align:start position:0% proposal this is similar to the EIP process<00:15:05.560> that<00:15:05.680> is<00:15:05.800> for<00:15:05.959> L1<00:15:06.720> and<00:15:06.880> we<00:15:07.079> have<00:15:07.199> a 00:15:07.470 --> 00:15:07.480 align:start position:0% process that is for L1 and we have a 00:15:07.480 --> 00:15:09.590 align:start position:0% process that is for L1 and we have a less<00:15:07.759> binding<00:15:08.639> kind<00:15:08.759> of<00:15:08.920> collaborative 00:15:09.590 --> 00:15:09.600 align:start position:0% less binding kind of collaborative 00:15:09.600 --> 00:15:12.749 align:start position:0% less binding kind of collaborative process<00:15:09.920> for<00:15:10.120> L2<00:15:10.680> that<00:15:10.759> is<00:15:10.880> called<00:15:11.519> RP<00:15:12.519> oh 00:15:12.749 --> 00:15:12.759 align:start position:0% process for L2 that is called RP oh 00:15:12.759 --> 00:15:15.870 align:start position:0% process for L2 that is called RP oh times<00:15:13.079> up<00:15:13.800> um<00:15:14.279> thank<00:15:14.480> you<00:15:14.759> and<00:15:15.079> if<00:15:15.279> anybody<00:15:15.680> has 00:15:15.870 --> 00:15:15.880 align:start position:0% times up um thank you and if anybody has 00:15:15.880 --> 00:15:19.590 align:start position:0% times up um thank you and if anybody has any<00:15:16.040> more<00:15:16.399> questions<00:15:17.399> uh<00:15:17.839> please<00:15:18.639> find<00:15:18.920> him<00:15:19.440> uh 00:15:19.590 --> 00:15:19.600 align:start position:0% any more questions uh please find him uh 00:15:19.600 --> 00:15:23.639 align:start position:0% any more questions uh please find him uh by<00:15:19.759> the<00:15:19.920> stage<00:15:20.440> thank<00:15:20.600> you<00:15:20.880> thank<00:15:21.040> you