WEBVTT Kind: captions Language: en 00:00:00.630 --> 00:00:46.869 align:start position:0% [Music] 00:00:46.869 --> 00:00:46.879 align:start position:0% 00:00:46.879 --> 00:00:51.549 align:start position:0% kind<00:00:47.120> of<00:00:47.640> I<00:00:47.719> mean<00:00:47.879> it's<00:00:48.039> fine<00:00:48.280> but<00:00:48.559> since 00:00:51.549 --> 00:00:51.559 align:start position:0% 00:00:51.559 --> 00:00:54.549 align:start position:0% we<00:00:52.559> okay<00:00:53.480> yeah<00:00:53.680> very<00:00:53.840> good<00:00:54.000> afternoon<00:00:54.320> to<00:00:54.480> all 00:00:54.549 --> 00:00:54.559 align:start position:0% we okay yeah very good afternoon to all 00:00:54.559 --> 00:00:57.110 align:start position:0% we okay yeah very good afternoon to all of<00:00:54.680> you<00:00:54.840> present<00:00:55.199> here<00:00:56.199> so<00:00:56.480> have<00:00:56.800> we<00:00:56.920> have 00:00:57.110 --> 00:00:57.120 align:start position:0% of you present here so have we have 00:00:57.120 --> 00:01:00.029 align:start position:0% of you present here so have we have reached<00:00:57.640> the<00:00:58.000> final<00:00:58.359> day<00:00:58.680> of<00:00:59.079> Devcon<00:00:59.600> we<00:00:59.680> have 00:01:00.029 --> 00:01:00.039 align:start position:0% reached the final day of Devcon we have 00:01:00.039 --> 00:01:03.229 align:start position:0% reached the final day of Devcon we have had<00:01:00.199> like<00:01:00.719> 10<00:01:01.719> different<00:01:02.640> uh<00:01:02.760> talks<00:01:03.079> on 00:01:03.229 --> 00:01:03.239 align:start position:0% had like 10 different uh talks on 00:01:03.239 --> 00:01:06.270 align:start position:0% had like 10 different uh talks on pre-confirmation<00:01:03.720> three<00:01:04.720> full<00:01:05.000> scale<00:01:05.280> events 00:01:06.270 --> 00:01:06.280 align:start position:0% pre-confirmation three full scale events 00:01:06.280 --> 00:01:08.109 align:start position:0% pre-confirmation three full scale events and<00:01:06.600> the<00:01:07.040> only<00:01:07.400> question<00:01:07.680> that<00:01:07.799> I've<00:01:07.960> been 00:01:08.109 --> 00:01:08.119 align:start position:0% and the only question that I've been 00:01:08.119 --> 00:01:10.550 align:start position:0% and the only question that I've been getting<00:01:08.439> is<00:01:08.840> how<00:01:08.960> do<00:01:09.080> you<00:01:09.240> make<00:01:09.479> all<00:01:09.600> of<00:01:09.840> this 00:01:10.550 --> 00:01:10.560 align:start position:0% getting is how do you make all of this 00:01:10.560 --> 00:01:12.789 align:start position:0% getting is how do you make all of this like<00:01:10.840> Fast<00:01:11.200> transaction<00:01:11.680> confirmations<00:01:12.640> yeah 00:01:12.789 --> 00:01:12.799 align:start position:0% like Fast transaction confirmations yeah 00:01:12.799 --> 00:01:15.310 align:start position:0% like Fast transaction confirmations yeah yeah<00:01:12.920> we<00:01:13.080> get<00:01:13.200> it<00:01:13.439> but<00:01:13.840> how<00:01:13.960> do<00:01:14.080> you<00:01:14.240> make<00:01:14.520> this 00:01:15.310 --> 00:01:15.320 align:start position:0% yeah we get it but how do you make this 00:01:15.320 --> 00:01:18.350 align:start position:0% yeah we get it but how do you make this so<00:01:15.520> yeah<00:01:15.680> now<00:01:15.960> on<00:01:16.159> the<00:01:16.360> last<00:01:16.799> day<00:01:17.799> uh<00:01:18.040> welcome 00:01:18.350 --> 00:01:18.360 align:start position:0% so yeah now on the last day uh welcome 00:01:18.360 --> 00:01:20.310 align:start position:0% so yeah now on the last day uh welcome to<00:01:18.520> the<00:01:18.640> workshop<00:01:19.000> on<00:01:19.200> designing<00:01:19.640> an<00:01:19.799> end2end 00:01:20.310 --> 00:01:20.320 align:start position:0% to the workshop on designing an end2end 00:01:20.320 --> 00:01:24.149 align:start position:0% to the workshop on designing an end2end system<00:01:20.640> for<00:01:21.400> based<00:01:21.799> pre-confirmation 00:01:24.149 --> 00:01:24.159 align:start position:0% system for based pre-confirmation 00:01:24.159 --> 00:01:27.550 align:start position:0% system for based pre-confirmation a<00:01:25.159> quick<00:01:25.360> introduction<00:01:25.799> of<00:01:25.920> the<00:01:26.320> speakers<00:01:27.320> uh 00:01:27.550 --> 00:01:27.560 align:start position:0% a quick introduction of the speakers uh 00:01:27.560 --> 00:01:29.910 align:start position:0% a quick introduction of the speakers uh Ahmed<00:01:27.960> go<00:01:28.079> ahead<00:01:28.479> yeah<00:01:28.840> um<00:01:29.119> so<00:01:29.439> my<00:01:29.560> name<00:01:29.720> is 00:01:29.910 --> 00:01:29.920 align:start position:0% Ahmed go ahead yeah um so my name is 00:01:29.920 --> 00:01:32.469 align:start position:0% Ahmed go ahead yeah um so my name is ahed<00:01:30.200> B<00:01:30.880> I<00:01:31.200> work<00:01:31.520> as<00:01:31.680> an<00:01:31.799> ethereum<00:01:32.200> core 00:01:32.469 --> 00:01:32.479 align:start position:0% ahed B I work as an ethereum core 00:01:32.479 --> 00:01:35.149 align:start position:0% ahed B I work as an ethereum core developer<00:01:33.399> normally<00:01:34.240> I'm<00:01:34.399> also<00:01:34.680> the<00:01:34.840> product 00:01:35.149 --> 00:01:35.159 align:start position:0% developer normally I'm also the product 00:01:35.159 --> 00:01:37.510 align:start position:0% developer normally I'm also the product manager<00:01:35.680> of<00:01:35.880> Surge<00:01:36.520> and<00:01:36.720> the<00:01:36.840> technical<00:01:37.240> lead 00:01:37.510 --> 00:01:37.520 align:start position:0% manager of Surge and the technical lead 00:01:37.520 --> 00:01:39.149 align:start position:0% manager of Surge and the technical lead for<00:01:37.720> our<00:01:38.000> pre-confirmation 00:01:39.149 --> 00:01:39.159 align:start position:0% for our pre-confirmation 00:01:39.159 --> 00:01:41.789 align:start position:0% for our pre-confirmation solution<00:01:40.159> and<00:01:40.320> I'm<00:01:40.479> Anu<00:01:41.040> I<00:01:41.200> am<00:01:41.320> working<00:01:41.600> as<00:01:41.680> a 00:01:41.789 --> 00:01:41.799 align:start position:0% solution and I'm Anu I am working as a 00:01:41.799 --> 00:01:44.590 align:start position:0% solution and I'm Anu I am working as a blockchain<00:01:42.119> engineer<00:01:42.560> at<00:01:42.960> nethermind<00:01:43.960> and<00:01:44.479> I 00:01:44.590 --> 00:01:44.600 align:start position:0% blockchain engineer at nethermind and I 00:01:44.600 --> 00:01:46.109 align:start position:0% blockchain engineer at nethermind and I joined<00:01:44.880> this<00:01:45.000> industry<00:01:45.320> like<00:01:45.479> 5<00:01:45.600> years<00:01:45.799> ago 00:01:46.109 --> 00:01:46.119 align:start position:0% joined this industry like 5 years ago 00:01:46.119 --> 00:01:48.910 align:start position:0% joined this industry like 5 years ago mostly<00:01:46.479> focused<00:01:46.880> on<00:01:47.000> dii<00:01:47.840> but<00:01:48.000> for<00:01:48.200> the<00:01:48.360> past<00:01:48.680> 6 00:01:48.910 --> 00:01:48.920 align:start position:0% mostly focused on dii but for the past 6 00:01:48.920 --> 00:01:51.590 align:start position:0% mostly focused on dii but for the past 6 months<00:01:49.880> uh<00:01:50.079> my<00:01:50.640> efforts<00:01:51.000> have<00:01:51.119> been<00:01:51.280> mostly 00:01:51.590 --> 00:01:51.600 align:start position:0% months uh my efforts have been mostly 00:01:51.600 --> 00:01:54.749 align:start position:0% months uh my efforts have been mostly concentrated<00:01:52.200> on<00:01:52.360> Bas<00:01:52.640> precon 00:01:54.749 --> 00:01:54.759 align:start position:0% concentrated on Bas precon 00:01:54.759 --> 00:01:58.190 align:start position:0% concentrated on Bas precon confirmations<00:01:55.759> so<00:01:56.439> today<00:01:56.799> this<00:01:57.079> session<00:01:57.560> is<00:01:58.039> a 00:01:58.190 --> 00:01:58.200 align:start position:0% confirmations so today this session is a 00:01:58.200 --> 00:02:00.350 align:start position:0% confirmations so today this session is a no<00:01:58.439> code<00:01:58.719> session<00:01:59.399> so<00:01:59.600> I<00:01:59.920> won't<00:02:00.079> be<00:02:00.200> like 00:02:00.350 --> 00:02:00.360 align:start position:0% no code session so I won't be like 00:02:00.360 --> 00:02:01.950 align:start position:0% no code session so I won't be like writing<00:02:00.759> a<00:02:00.880> line<00:02:01.079> of<00:02:01.200> code<00:02:01.479> and<00:02:01.560> then<00:02:01.719> asking 00:02:01.950 --> 00:02:01.960 align:start position:0% writing a line of code and then asking 00:02:01.960 --> 00:02:03.670 align:start position:0% writing a line of code and then asking you<00:02:02.079> to<00:02:02.240> copy<00:02:02.479> it<00:02:02.600> and<00:02:02.759> repeat<00:02:03.039> it<00:02:03.200> like<00:02:03.439> 100 00:02:03.670 --> 00:02:03.680 align:start position:0% you to copy it and repeat it like 100 00:02:03.680 --> 00:02:05.789 align:start position:0% you to copy it and repeat it like 100 times<00:02:03.960> over<00:02:04.520> I<00:02:04.600> know<00:02:04.799> most<00:02:04.960> of<00:02:05.079> you<00:02:05.200> will<00:02:05.360> leave 00:02:05.789 --> 00:02:05.799 align:start position:0% times over I know most of you will leave 00:02:05.799 --> 00:02:07.870 align:start position:0% times over I know most of you will leave in<00:02:05.920> like<00:02:06.079> half<00:02:06.240> an<00:02:06.360> hour<00:02:06.560> if<00:02:06.640> I<00:02:06.759> do<00:02:06.960> that<00:02:07.640> so 00:02:07.870 --> 00:02:07.880 align:start position:0% in like half an hour if I do that so 00:02:07.880 --> 00:02:10.270 align:start position:0% in like half an hour if I do that so instead<00:02:08.319> this<00:02:08.440> is<00:02:08.840> a<00:02:09.000> session<00:02:09.520> on<00:02:09.759> design 00:02:10.270 --> 00:02:10.280 align:start position:0% instead this is a session on design 00:02:10.280 --> 00:02:12.869 align:start position:0% instead this is a session on design thinking<00:02:11.280> where<00:02:11.760> we'll<00:02:12.040> build<00:02:12.319> the<00:02:12.480> whole 00:02:12.869 --> 00:02:12.879 align:start position:0% thinking where we'll build the whole 00:02:12.879 --> 00:02:15.589 align:start position:0% thinking where we'll build the whole concept<00:02:13.319> from<00:02:13.520> ground<00:02:13.840> up<00:02:14.480> and<00:02:14.640> share<00:02:15.200> exact 00:02:15.589 --> 00:02:15.599 align:start position:0% concept from ground up and share exact 00:02:15.599 --> 00:02:17.990 align:start position:0% concept from ground up and share exact what<00:02:15.879> exactly<00:02:16.319> we<00:02:16.560> did<00:02:17.120> during<00:02:17.400> our<00:02:17.599> research 00:02:17.990 --> 00:02:18.000 align:start position:0% what exactly we did during our research 00:02:18.000 --> 00:02:19.630 align:start position:0% what exactly we did during our research over<00:02:18.200> the<00:02:18.360> past<00:02:18.680> 6 00:02:19.630 --> 00:02:19.640 align:start position:0% over the past 6 00:02:19.640 --> 00:02:21.710 align:start position:0% over the past 6 months<00:02:20.640> but<00:02:20.800> if<00:02:20.879> you<00:02:21.000> are<00:02:21.200> interested<00:02:21.560> in 00:02:21.710 --> 00:02:21.720 align:start position:0% months but if you are interested in 00:02:21.720 --> 00:02:23.990 align:start position:0% months but if you are interested in looking<00:02:21.920> at<00:02:22.040> the<00:02:22.160> code<00:02:22.640> then<00:02:23.280> I<00:02:23.440> have<00:02:23.560> linked 00:02:23.990 --> 00:02:24.000 align:start position:0% looking at the code then I have linked 00:02:24.000 --> 00:02:27.190 align:start position:0% looking at the code then I have linked it<00:02:24.200> below<00:02:24.519> it's<00:02:25.160> Tao<00:02:25.680> precom<00:02:26.160> AVS<00:02:26.599> repository 00:02:27.190 --> 00:02:27.200 align:start position:0% it below it's Tao precom AVS repository 00:02:27.200 --> 00:02:29.030 align:start position:0% it below it's Tao precom AVS repository which<00:02:27.280> you<00:02:27.400> can<00:02:27.560> find<00:02:27.840> on<00:02:28.000> the<00:02:28.120> neine<00:02:28.680> GitHub 00:02:29.030 --> 00:02:29.040 align:start position:0% which you can find on the neine GitHub 00:02:29.040 --> 00:02:31.430 align:start position:0% which you can find on the neine GitHub page 00:02:31.430 --> 00:02:31.440 align:start position:0% page 00:02:31.440 --> 00:02:33.750 align:start position:0% page so<00:02:31.640> since<00:02:31.800> we<00:02:31.920> want<00:02:32.080> to<00:02:32.239> build<00:02:32.440> it<00:02:32.599> all<00:02:33.000> up<00:02:33.519> from 00:02:33.750 --> 00:02:33.760 align:start position:0% so since we want to build it all up from 00:02:33.760 --> 00:02:36.110 align:start position:0% so since we want to build it all up from ground<00:02:34.120> up<00:02:34.840> we<00:02:34.959> have<00:02:35.080> to<00:02:35.280> start<00:02:35.840> with<00:02:35.959> the 00:02:36.110 --> 00:02:36.120 align:start position:0% ground up we have to start with the 00:02:36.120 --> 00:02:39.070 align:start position:0% ground up we have to start with the foundational<00:02:36.599> knowledge<00:02:37.519> which<00:02:37.640> is<00:02:38.080> rollups 00:02:39.070 --> 00:02:39.080 align:start position:0% foundational knowledge which is rollups 00:02:39.080 --> 00:02:40.830 align:start position:0% foundational knowledge which is rollups because<00:02:39.400> the<00:02:39.560> based<00:02:40.000> in<00:02:40.360> in<00:02:40.519> based 00:02:40.830 --> 00:02:40.840 align:start position:0% because the based in in based 00:02:40.840 --> 00:02:43.190 align:start position:0% because the based in in based reconfirmations<00:02:41.840> comes<00:02:42.080> from<00:02:42.280> based 00:02:43.190 --> 00:02:43.200 align:start position:0% reconfirmations comes from based 00:02:43.200 --> 00:02:45.430 align:start position:0% reconfirmations comes from based rollups<00:02:44.200> just<00:02:44.319> by<00:02:44.440> show<00:02:44.640> of<00:02:44.800> hands<00:02:45.159> how<00:02:45.280> many 00:02:45.430 --> 00:02:45.440 align:start position:0% rollups just by show of hands how many 00:02:45.440 --> 00:02:48.630 align:start position:0% rollups just by show of hands how many of<00:02:45.560> you<00:02:45.680> do<00:02:46.200> understand<00:02:46.400> what<00:02:46.519> a<00:02:46.640> rollup 00:02:48.630 --> 00:02:48.640 align:start position:0% of you do understand what a rollup 00:02:48.640 --> 00:02:52.430 align:start position:0% of you do understand what a rollup is<00:02:49.640> okay<00:02:49.920> pretty<00:02:50.200> much<00:02:50.840> everyone<00:02:51.840> that's 00:02:52.430 --> 00:02:52.440 align:start position:0% is okay pretty much everyone that's 00:02:52.440 --> 00:02:54.990 align:start position:0% is okay pretty much everyone that's great<00:02:53.440> well<00:02:53.599> rollup<00:02:53.959> is<00:02:54.040> a<00:02:54.159> scaling 00:02:54.990 --> 00:02:55.000 align:start position:0% great well rollup is a scaling 00:02:55.000 --> 00:02:56.990 align:start position:0% great well rollup is a scaling solution<00:02:56.000> and<00:02:56.120> why<00:02:56.239> do<00:02:56.319> we<00:02:56.440> need<00:02:56.560> a<00:02:56.640> scaling 00:02:56.990 --> 00:02:57.000 align:start position:0% solution and why do we need a scaling 00:02:57.000 --> 00:02:58.910 align:start position:0% solution and why do we need a scaling solution<00:02:57.920> we<00:02:58.040> need<00:02:58.159> a<00:02:58.280> scaling<00:02:58.560> solution 00:02:58.910 --> 00:02:58.920 align:start position:0% solution we need a scaling solution 00:02:58.920 --> 00:03:01.350 align:start position:0% solution we need a scaling solution because<00:02:59.120> the<00:02:59.239> L1<00:02:59.680> is<00:02:59.879> is<00:03:00.159> really<00:03:00.440> slow<00:03:01.239> the 00:03:01.350 --> 00:03:01.360 align:start position:0% because the L1 is is really slow the 00:03:01.360 --> 00:03:04.270 align:start position:0% because the L1 is is really slow the throughput<00:03:01.760> of<00:03:01.879> L1<00:03:02.319> is<00:03:02.519> not<00:03:02.879> much<00:03:03.879> and<00:03:04.080> why 00:03:04.270 --> 00:03:04.280 align:start position:0% throughput of L1 is not much and why 00:03:04.280 --> 00:03:07.550 align:start position:0% throughput of L1 is not much and why exactly<00:03:04.680> is<00:03:04.840> that<00:03:05.000> the<00:03:05.360> case<00:03:06.360> well<00:03:07.000> in<00:03:07.120> a 00:03:07.550 --> 00:03:07.560 align:start position:0% exactly is that the case well in a 00:03:07.560 --> 00:03:09.869 align:start position:0% exactly is that the case well in a blockchain<00:03:08.560> blocks<00:03:09.080> are<00:03:09.319> basically<00:03:09.680> a 00:03:09.869 --> 00:03:09.879 align:start position:0% blockchain blocks are basically a 00:03:09.879 --> 00:03:12.670 align:start position:0% blockchain blocks are basically a consensus<00:03:10.400> on<00:03:10.560> state<00:03:11.239> transition<00:03:12.239> that's<00:03:12.440> the 00:03:12.670 --> 00:03:12.680 align:start position:0% consensus on state transition that's the 00:03:12.680 --> 00:03:14.229 align:start position:0% consensus on state transition that's the first<00:03:13.040> section<00:03:13.360> of<00:03:13.480> the<00:03:13.560> ethereum<00:03:14.000> white 00:03:14.229 --> 00:03:14.239 align:start position:0% first section of the ethereum white 00:03:14.239 --> 00:03:16.869 align:start position:0% first section of the ethereum white paper<00:03:14.760> you<00:03:14.920> have<00:03:15.120> state<00:03:15.440> a<00:03:16.239> you<00:03:16.400> put<00:03:16.560> a<00:03:16.680> bunch 00:03:16.869 --> 00:03:16.879 align:start position:0% paper you have state a you put a bunch 00:03:16.879 --> 00:03:19.630 align:start position:0% paper you have state a you put a bunch of<00:03:17.040> transactions<00:03:17.799> and<00:03:18.000> apply<00:03:18.319> it<00:03:18.519> to<00:03:18.720> State<00:03:19.040> a 00:03:19.630 --> 00:03:19.640 align:start position:0% of transactions and apply it to State a 00:03:19.640 --> 00:03:21.550 align:start position:0% of transactions and apply it to State a which<00:03:19.760> is<00:03:19.920> like<00:03:20.040> a<00:03:20.239> Delta<00:03:21.040> and<00:03:21.159> you<00:03:21.280> get<00:03:21.400> a 00:03:21.550 --> 00:03:21.560 align:start position:0% which is like a Delta and you get a 00:03:21.560 --> 00:03:22.350 align:start position:0% which is like a Delta and you get a state 00:03:22.350 --> 00:03:22.360 align:start position:0% state 00:03:22.360 --> 00:03:25.470 align:start position:0% state B<00:03:23.360> but<00:03:23.519> now<00:03:23.799> imagine<00:03:24.400> millions<00:03:24.799> of<00:03:24.959> nodes 00:03:25.470 --> 00:03:25.480 align:start position:0% B but now imagine millions of nodes 00:03:25.480 --> 00:03:28.470 align:start position:0% B but now imagine millions of nodes doing<00:03:25.879> this<00:03:26.560> every<00:03:26.840> single<00:03:27.159> Epoch<00:03:28.040> now<00:03:28.280> that's 00:03:28.470 --> 00:03:28.480 align:start position:0% doing this every single Epoch now that's 00:03:28.480 --> 00:03:30.429 align:start position:0% doing this every single Epoch now that's going<00:03:28.560> to<00:03:28.720> make<00:03:28.879> this<00:03:29.040> network<00:03:29.360> really<00:03:29.519> slow 00:03:30.429 --> 00:03:30.439 align:start position:0% going to make this network really slow 00:03:30.439 --> 00:03:32.429 align:start position:0% going to make this network really slow and<00:03:30.640> that's<00:03:30.879> a<00:03:31.040> major 00:03:32.429 --> 00:03:32.439 align:start position:0% and that's a major 00:03:32.439 --> 00:03:34.550 align:start position:0% and that's a major problem<00:03:33.439> so<00:03:33.599> what's<00:03:33.799> the<00:03:33.920> rollup<00:03:34.280> way<00:03:34.439> of 00:03:34.550 --> 00:03:34.560 align:start position:0% problem so what's the rollup way of 00:03:34.560 --> 00:03:37.990 align:start position:0% problem so what's the rollup way of doing<00:03:35.080> it<00:03:36.080> well<00:03:36.799> if<00:03:37.159> processing<00:03:37.760> State 00:03:37.990 --> 00:03:38.000 align:start position:0% doing it well if processing State 00:03:38.000 --> 00:03:40.789 align:start position:0% doing it well if processing State transitions<00:03:38.680> is<00:03:38.959> the<00:03:39.080> biggest<00:03:39.439> issue<00:03:40.319> on<00:03:40.480> the 00:03:40.789 --> 00:03:40.799 align:start position:0% transitions is the biggest issue on the 00:03:40.799 --> 00:03:43.589 align:start position:0% transitions is the biggest issue on the L1<00:03:41.799> what<00:03:41.959> if<00:03:42.200> we<00:03:42.720> process<00:03:43.159> these<00:03:43.360> State 00:03:43.589 --> 00:03:43.599 align:start position:0% L1 what if we process these State 00:03:43.599 --> 00:03:45.750 align:start position:0% L1 what if we process these State transitions<00:03:44.159> off<00:03:44.400> chain<00:03:44.840> or<00:03:45.080> apply<00:03:45.480> these 00:03:45.750 --> 00:03:45.760 align:start position:0% transitions off chain or apply these 00:03:45.760 --> 00:03:48.110 align:start position:0% transitions off chain or apply these Deltas<00:03:46.120> off<00:03:46.400> chain<00:03:47.400> and<00:03:47.519> that's<00:03:47.720> exactly<00:03:48.000> what 00:03:48.110 --> 00:03:48.120 align:start position:0% Deltas off chain and that's exactly what 00:03:48.120 --> 00:03:50.390 align:start position:0% Deltas off chain and that's exactly what a<00:03:48.200> rollup<00:03:48.560> does<00:03:49.360> we<00:03:49.519> have<00:03:49.760> like<00:03:49.879> you<00:03:49.959> can<00:03:50.159> have 00:03:50.390 --> 00:03:50.400 align:start position:0% a rollup does we have like you can have 00:03:50.400 --> 00:03:52.910 align:start position:0% a rollup does we have like you can have a<00:03:50.519> one<00:03:50.760> single<00:03:51.159> rollup<00:03:51.599> node<00:03:52.079> or<00:03:52.200> an<00:03:52.360> L2<00:03:52.680> node 00:03:52.910 --> 00:03:52.920 align:start position:0% a one single rollup node or an L2 node 00:03:52.920 --> 00:03:55.949 align:start position:0% a one single rollup node or an L2 node since<00:03:53.120> it<00:03:53.280> becomes<00:03:53.519> a<00:03:53.640> lay<00:03:53.920> to<00:03:54.680> that<00:03:54.959> applies 00:03:55.949 --> 00:03:55.959 align:start position:0% since it becomes a lay to that applies 00:03:55.959 --> 00:03:58.350 align:start position:0% since it becomes a lay to that applies applies<00:03:56.400> this<00:03:56.560> Delta<00:03:56.959> of<00:03:57.200> chain<00:03:57.879> processes 00:03:58.350 --> 00:03:58.360 align:start position:0% applies this Delta of chain processes 00:03:58.360 --> 00:04:00.990 align:start position:0% applies this Delta of chain processes the<00:03:58.480> state<00:03:58.760> transition<00:04:00.079> and<00:04:00.239> the<00:04:00.360> L1<00:04:00.720> is<00:04:00.879> just 00:04:00.990 --> 00:04:01.000 align:start position:0% the state transition and the L1 is just 00:04:01.000 --> 00:04:04.030 align:start position:0% the state transition and the L1 is just an<00:04:01.400> observer<00:04:02.400> on<00:04:02.560> the<00:04:02.680> L1<00:04:03.200> you<00:04:03.360> have<00:04:03.519> a<00:04:03.640> rollup 00:04:04.030 --> 00:04:04.040 align:start position:0% an observer on the L1 you have a rollup 00:04:04.040 --> 00:04:06.750 align:start position:0% an observer on the L1 you have a rollup inbox<00:04:04.480> contract<00:04:05.400> and<00:04:05.480> you<00:04:05.680> simply<00:04:06.079> push<00:04:06.560> this 00:04:06.750 --> 00:04:06.760 align:start position:0% inbox contract and you simply push this 00:04:06.760 --> 00:04:09.670 align:start position:0% inbox contract and you simply push this state<00:04:07.000> transition<00:04:08.000> and<00:04:08.120> the<00:04:08.319> Delta<00:04:09.280> maybe<00:04:09.560> as 00:04:09.670 --> 00:04:09.680 align:start position:0% state transition and the Delta maybe as 00:04:09.680 --> 00:04:11.830 align:start position:0% state transition and the Delta maybe as a<00:04:09.760> form<00:04:09.920> of<00:04:10.040> a<00:04:10.159> blob<00:04:10.640> or<00:04:10.799> in<00:04:10.920> the<00:04:11.040> call<00:04:11.319> data<00:04:11.720> in 00:04:11.830 --> 00:04:11.840 align:start position:0% a form of a blob or in the call data in 00:04:11.840 --> 00:04:14.350 align:start position:0% a form of a blob or in the call data in the<00:04:11.959> image<00:04:12.200> it's<00:04:12.319> a<00:04:12.560> blob<00:04:13.560> and<00:04:13.680> the<00:04:13.799> L1<00:04:14.159> is<00:04:14.239> just 00:04:14.350 --> 00:04:14.360 align:start position:0% the image it's a blob and the L1 is just 00:04:14.360 --> 00:04:15.110 align:start position:0% the image it's a blob and the L1 is just an 00:04:15.110 --> 00:04:15.120 align:start position:0% an 00:04:15.120 --> 00:04:17.870 align:start position:0% an observer<00:04:16.120> and<00:04:16.440> in<00:04:16.600> the<00:04:16.799> most<00:04:17.160> basic<00:04:17.479> form<00:04:17.759> this 00:04:17.870 --> 00:04:17.880 align:start position:0% observer and in the most basic form this 00:04:17.880 --> 00:04:19.469 align:start position:0% observer and in the most basic form this is<00:04:18.000> what<00:04:18.120> a<00:04:18.199> rollup 00:04:19.469 --> 00:04:19.479 align:start position:0% is what a rollup 00:04:19.479 --> 00:04:24.830 align:start position:0% is what a rollup is<00:04:20.479> but<00:04:20.680> is<00:04:20.840> this<00:04:21.120> enough<00:04:22.120> well<00:04:22.919> no<00:04:23.919> because<00:04:24.720> if 00:04:24.830 --> 00:04:24.840 align:start position:0% is but is this enough well no because if 00:04:24.840 --> 00:04:26.189 align:start position:0% is but is this enough well no because if it's<00:04:25.080> just<00:04:25.280> one<00:04:25.479> note<00:04:25.800> pushing<00:04:26.080> the 00:04:26.189 --> 00:04:26.199 align:start position:0% it's just one note pushing the 00:04:26.199 --> 00:04:28.909 align:start position:0% it's just one note pushing the transition<00:04:26.880> and<00:04:27.080> the<00:04:27.240> Delta<00:04:28.080> how<00:04:28.240> do<00:04:28.360> we<00:04:28.520> know 00:04:28.909 --> 00:04:28.919 align:start position:0% transition and the Delta how do we know 00:04:28.919 --> 00:04:30.390 align:start position:0% transition and the Delta how do we know whether<00:04:29.120> it's<00:04:29.280> actually<00:04:29.479> correct<00:04:29.720> correct<00:04:29.960> or 00:04:30.390 --> 00:04:30.400 align:start position:0% whether it's actually correct correct or 00:04:30.400 --> 00:04:32.870 align:start position:0% whether it's actually correct correct or not<00:04:31.400> and<00:04:31.560> this<00:04:31.680> is<00:04:31.840> where<00:04:32.039> the<00:04:32.199> flavors<00:04:32.680> of<00:04:32.800> the 00:04:32.870 --> 00:04:32.880 align:start position:0% not and this is where the flavors of the 00:04:32.880 --> 00:04:36.310 align:start position:0% not and this is where the flavors of the rollups<00:04:33.320> come<00:04:33.479> in<00:04:33.960> optimistic<00:04:34.520> and<00:04:35.039> ZK<00:04:36.039> in<00:04:36.199> the 00:04:36.310 --> 00:04:36.320 align:start position:0% rollups come in optimistic and ZK in the 00:04:36.320 --> 00:04:38.909 align:start position:0% rollups come in optimistic and ZK in the case<00:04:36.520> of<00:04:36.639> an<00:04:36.800> optimistic<00:04:37.400> rollup<00:04:38.400> well<00:04:38.759> you 00:04:38.909 --> 00:04:38.919 align:start position:0% case of an optimistic rollup well you 00:04:38.919 --> 00:04:41.670 align:start position:0% case of an optimistic rollup well you push<00:04:39.240> the<00:04:39.360> state<00:04:39.680> transition<00:04:40.280> and<00:04:40.440> the<00:04:40.680> Delta 00:04:41.670 --> 00:04:41.680 align:start position:0% push the state transition and the Delta 00:04:41.680 --> 00:04:43.710 align:start position:0% push the state transition and the Delta and<00:04:41.800> then<00:04:41.919> you<00:04:42.080> just<00:04:42.320> wait<00:04:42.800> you<00:04:42.960> just<00:04:43.240> wait<00:04:43.479> for 00:04:43.710 --> 00:04:43.720 align:start position:0% and then you just wait you just wait for 00:04:43.720 --> 00:04:46.310 align:start position:0% and then you just wait you just wait for someone<00:04:44.039> to<00:04:44.240> prove<00:04:44.479> you<00:04:44.960> incorrect<00:04:45.960> if<00:04:46.080> you're 00:04:46.310 --> 00:04:46.320 align:start position:0% someone to prove you incorrect if you're 00:04:46.320 --> 00:04:48.430 align:start position:0% someone to prove you incorrect if you're correct<00:04:46.720> it's<00:04:46.919> it's<00:04:47.080> all<00:04:47.320> good<00:04:47.960> but<00:04:48.120> someone 00:04:48.430 --> 00:04:48.440 align:start position:0% correct it's it's all good but someone 00:04:48.440 --> 00:04:50.310 align:start position:0% correct it's it's all good but someone can<00:04:48.600> just<00:04:48.800> come<00:04:49.039> by<00:04:49.240> and<00:04:49.360> say<00:04:49.639> oh<00:04:49.840> hey<00:04:50.000> it's<00:04:50.160> a 00:04:50.310 --> 00:04:50.320 align:start position:0% can just come by and say oh hey it's a 00:04:50.320 --> 00:04:52.550 align:start position:0% can just come by and say oh hey it's a proof<00:04:50.600> here's<00:04:50.840> a<00:04:51.000> proof<00:04:51.759> this<00:04:51.960> transition 00:04:52.550 --> 00:04:52.560 align:start position:0% proof here's a proof this transition 00:04:52.560 --> 00:04:54.870 align:start position:0% proof here's a proof this transition that<00:04:52.680> you<00:04:52.840> posted<00:04:53.479> is<00:04:53.960> not<00:04:54.280> possible<00:04:54.639> with<00:04:54.759> the 00:04:54.870 --> 00:04:54.880 align:start position:0% that you posted is not possible with the 00:04:54.880 --> 00:04:57.029 align:start position:0% that you posted is not possible with the Delta<00:04:55.199> that<00:04:55.320> you<00:04:55.479> posted<00:04:56.479> and<00:04:56.639> then<00:04:56.759> you<00:04:56.919> kind 00:04:57.029 --> 00:04:57.039 align:start position:0% Delta that you posted and then you kind 00:04:57.039 --> 00:04:59.150 align:start position:0% Delta that you posted and then you kind of<00:04:57.199> get<00:04:57.320> slashed<00:04:57.840> if<00:04:57.960> you<00:04:58.080> have<00:04:58.240> some<00:04:58.360> stake<00:04:58.680> in 00:04:59.150 --> 00:04:59.160 align:start position:0% of get slashed if you have some stake in 00:04:59.160 --> 00:05:01.430 align:start position:0% of get slashed if you have some stake in depends<00:04:59.440> on<00:05:00.000> uh<00:05:00.360> what<00:05:00.560> kind<00:05:00.759> of<00:05:01.039> process<00:05:01.320> the 00:05:01.430 --> 00:05:01.440 align:start position:0% depends on uh what kind of process the 00:05:01.440 --> 00:05:03.029 align:start position:0% depends on uh what kind of process the rollup<00:05:01.759> wants<00:05:01.960> to 00:05:03.029 --> 00:05:03.039 align:start position:0% rollup wants to 00:05:03.039 --> 00:05:05.430 align:start position:0% rollup wants to do<00:05:04.039> and<00:05:04.199> arbitrum<00:05:04.680> is<00:05:04.759> an<00:05:04.880> example<00:05:05.199> of<00:05:05.320> an 00:05:05.430 --> 00:05:05.440 align:start position:0% do and arbitrum is an example of an 00:05:05.440 --> 00:05:06.909 align:start position:0% do and arbitrum is an example of an optimistic<00:05:05.840> rollup<00:05:06.240> I<00:05:06.320> guess<00:05:06.479> most<00:05:06.639> of<00:05:06.759> you 00:05:06.909 --> 00:05:06.919 align:start position:0% optimistic rollup I guess most of you 00:05:06.919 --> 00:05:09.390 align:start position:0% optimistic rollup I guess most of you must<00:05:07.080> have<00:05:07.199> used<00:05:07.880> arbitrum<00:05:08.880> and<00:05:09.000> then<00:05:09.160> we<00:05:09.240> have 00:05:09.390 --> 00:05:09.400 align:start position:0% must have used arbitrum and then we have 00:05:09.400 --> 00:05:12.469 align:start position:0% must have used arbitrum and then we have ZK<00:05:09.759> rollups<00:05:10.639> in<00:05:10.759> the<00:05:10.919> case<00:05:11.080> of<00:05:11.199> ZK<00:05:11.560> rollups 00:05:12.469 --> 00:05:12.479 align:start position:0% ZK rollups in the case of ZK rollups 00:05:12.479 --> 00:05:14.070 align:start position:0% ZK rollups in the case of ZK rollups instead<00:05:12.800> of<00:05:13.039> waiting<00:05:13.320> on<00:05:13.520> for<00:05:13.680> someone<00:05:13.919> to 00:05:14.070 --> 00:05:14.080 align:start position:0% instead of waiting on for someone to 00:05:14.080 --> 00:05:16.390 align:start position:0% instead of waiting on for someone to prove<00:05:14.240> you<00:05:14.520> incorrect<00:05:15.520> the<00:05:15.680> moment<00:05:15.960> you<00:05:16.120> push 00:05:16.390 --> 00:05:16.400 align:start position:0% prove you incorrect the moment you push 00:05:16.400 --> 00:05:18.950 align:start position:0% prove you incorrect the moment you push the<00:05:16.560> transition<00:05:17.120> and<00:05:17.240> the<00:05:17.400> Delta<00:05:18.319> you<00:05:18.520> have<00:05:18.639> to 00:05:18.950 --> 00:05:18.960 align:start position:0% the transition and the Delta you have to 00:05:18.960 --> 00:05:20.629 align:start position:0% the transition and the Delta you have to prove<00:05:19.319> that<00:05:19.520> this<00:05:19.680> is 00:05:20.629 --> 00:05:20.639 align:start position:0% prove that this is 00:05:20.639 --> 00:05:22.950 align:start position:0% prove that this is correct<00:05:21.639> so<00:05:21.840> it's<00:05:22.000> called<00:05:22.160> a<00:05:22.319> validity<00:05:22.720> proof 00:05:22.950 --> 00:05:22.960 align:start position:0% correct so it's called a validity proof 00:05:22.960 --> 00:05:25.510 align:start position:0% correct so it's called a validity proof you're<00:05:23.120> basically<00:05:23.840> proving<00:05:24.199> the<00:05:24.400> validity<00:05:25.120> of 00:05:25.510 --> 00:05:25.520 align:start position:0% you're basically proving the validity of 00:05:25.520 --> 00:05:26.469 align:start position:0% you're basically proving the validity of the 00:05:26.469 --> 00:05:26.479 align:start position:0% the 00:05:26.479 --> 00:05:29.469 align:start position:0% the transition<00:05:27.479> but<00:05:28.120> the<00:05:28.240> point<00:05:28.520> here<00:05:28.720> is<00:05:28.919> that 00:05:29.469 --> 00:05:29.479 align:start position:0% transition but the point here is that 00:05:29.479 --> 00:05:32.870 align:start position:0% transition but the point here is that what<00:05:30.120> whatever<00:05:31.120> time<00:05:31.520> or<00:05:32.240> computational 00:05:32.870 --> 00:05:32.880 align:start position:0% what whatever time or computational 00:05:32.880 --> 00:05:35.469 align:start position:0% what whatever time or computational effort<00:05:33.199> it<00:05:33.400> takes<00:05:34.039> to<00:05:34.400> verify<00:05:34.840> this<00:05:35.000> validity 00:05:35.469 --> 00:05:35.479 align:start position:0% effort it takes to verify this validity 00:05:35.479 --> 00:05:37.350 align:start position:0% effort it takes to verify this validity proof<00:05:35.800> must<00:05:36.039> be<00:05:36.319> less<00:05:36.720> than<00:05:36.919> what<00:05:37.039> it<00:05:37.160> takes 00:05:37.350 --> 00:05:37.360 align:start position:0% proof must be less than what it takes 00:05:37.360 --> 00:05:39.230 align:start position:0% proof must be less than what it takes for<00:05:37.560> the<00:05:37.720> L1<00:05:38.120> itself<00:05:38.440> to<00:05:38.600> process<00:05:38.960> all<00:05:39.080> the 00:05:39.230 --> 00:05:39.240 align:start position:0% for the L1 itself to process all the 00:05:39.240 --> 00:05:41.469 align:start position:0% for the L1 itself to process all the data<00:05:39.759> only<00:05:40.039> then<00:05:40.160> it<00:05:40.360> actually<00:05:40.600> makes<00:05:40.960> sense 00:05:41.469 --> 00:05:41.479 align:start position:0% data only then it actually makes sense 00:05:41.479 --> 00:05:43.790 align:start position:0% data only then it actually makes sense right<00:05:42.479> so<00:05:42.639> these<00:05:42.759> are<00:05:42.880> the<00:05:43.000> two<00:05:43.160> variants<00:05:43.600> for 00:05:43.790 --> 00:05:43.800 align:start position:0% right so these are the two variants for 00:05:43.800 --> 00:05:45.590 align:start position:0% right so these are the two variants for proving<00:05:44.400> whether<00:05:44.600> a<00:05:44.720> transition<00:05:45.160> is<00:05:45.280> correct 00:05:45.590 --> 00:05:45.600 align:start position:0% proving whether a transition is correct 00:05:45.600 --> 00:05:48.189 align:start position:0% proving whether a transition is correct or 00:05:48.189 --> 00:05:48.199 align:start position:0% 00:05:48.199 --> 00:05:50.670 align:start position:0% not<00:05:49.199> once<00:05:49.440> again<00:05:49.639> by<00:05:49.759> sh<00:05:50.080> fans<00:05:50.360> how<00:05:50.440> many<00:05:50.600> of 00:05:50.670 --> 00:05:50.680 align:start position:0% not once again by sh fans how many of 00:05:50.680 --> 00:05:52.309 align:start position:0% not once again by sh fans how many of you<00:05:50.800> have<00:05:50.919> heard<00:05:51.080> of<00:05:51.199> centralized 00:05:52.309 --> 00:05:52.319 align:start position:0% you have heard of centralized 00:05:52.319 --> 00:05:56.790 align:start position:0% you have heard of centralized sequencing<00:05:53.319> okay<00:05:54.000> it's<00:05:54.639> the<00:05:55.639> most<00:05:56.120> cursed 00:05:56.790 --> 00:05:56.800 align:start position:0% sequencing okay it's the most cursed 00:05:56.800 --> 00:06:00.110 align:start position:0% sequencing okay it's the most cursed concept<00:05:57.479> right<00:05:58.080> now<00:05:59.080> and<00:05:59.639> just<00:05:59.759> to<00:05:59.880> give<00:06:00.039> a 00:06:00.110 --> 00:06:00.120 align:start position:0% concept right now and just to give a 00:06:00.120 --> 00:06:01.790 align:start position:0% concept right now and just to give a quick<00:06:00.319> primer<00:06:01.120> when<00:06:01.240> you're<00:06:01.440> making<00:06:01.639> a 00:06:01.790 --> 00:06:01.800 align:start position:0% quick primer when you're making a 00:06:01.800 --> 00:06:03.710 align:start position:0% quick primer when you're making a transaction<00:06:02.240> on<00:06:02.440> arbitrum<00:06:03.319> you're<00:06:03.520> not 00:06:03.710 --> 00:06:03.720 align:start position:0% transaction on arbitrum you're not 00:06:03.720 --> 00:06:05.510 align:start position:0% transaction on arbitrum you're not directly<00:06:04.039> sending<00:06:04.400> the<00:06:04.560> transaction<00:06:05.039> to<00:06:05.319> a 00:06:05.510 --> 00:06:05.520 align:start position:0% directly sending the transaction to a 00:06:05.520 --> 00:06:07.430 align:start position:0% directly sending the transaction to a public<00:06:05.840> mempool<00:06:06.680> like<00:06:06.880> when<00:06:07.000> you're<00:06:07.199> doing 00:06:07.430 --> 00:06:07.440 align:start position:0% public mempool like when you're doing 00:06:07.440 --> 00:06:09.950 align:start position:0% public mempool like when you're doing when<00:06:07.599> you<00:06:07.680> are<00:06:07.840> transacting<00:06:08.319> on<00:06:08.479> ethereum<00:06:08.960> L1 00:06:09.950 --> 00:06:09.960 align:start position:0% when you are transacting on ethereum L1 00:06:09.960 --> 00:06:12.390 align:start position:0% when you are transacting on ethereum L1 instead<00:06:10.639> it's<00:06:10.840> going<00:06:11.039> to<00:06:11.240> an<00:06:11.400> arbitrum 00:06:12.390 --> 00:06:12.400 align:start position:0% instead it's going to an arbitrum 00:06:12.400 --> 00:06:15.189 align:start position:0% instead it's going to an arbitrum sequencer<00:06:13.400> and<00:06:13.520> it's<00:06:13.639> a<00:06:13.800> private<00:06:14.120> server<00:06:15.080> what 00:06:15.189 --> 00:06:15.199 align:start position:0% sequencer and it's a private server what 00:06:15.199 --> 00:06:17.390 align:start position:0% sequencer and it's a private server what the<00:06:15.319> sequencer<00:06:15.880> does<00:06:16.080> is<00:06:16.400> it<00:06:16.599> has<00:06:17.000> complete 00:06:17.390 --> 00:06:17.400 align:start position:0% the sequencer does is it has complete 00:06:17.400 --> 00:06:20.749 align:start position:0% the sequencer does is it has complete control<00:06:17.840> over<00:06:18.360> arranging<00:06:19.039> or<00:06:19.199> ordering<00:06:19.599> the 00:06:20.749 --> 00:06:20.759 align:start position:0% control over arranging or ordering the 00:06:20.759 --> 00:06:23.430 align:start position:0% control over arranging or ordering the transactions<00:06:21.759> and<00:06:22.039> they<00:06:22.199> usually<00:06:22.759> promise 00:06:23.430 --> 00:06:23.440 align:start position:0% transactions and they usually promise 00:06:23.440 --> 00:06:24.790 align:start position:0% transactions and they usually promise that<00:06:23.680> they<00:06:23.759> will<00:06:23.919> arrange<00:06:24.280> the<00:06:24.400> transaction 00:06:24.790 --> 00:06:24.800 align:start position:0% that they will arrange the transaction 00:06:24.800 --> 00:06:26.230 align:start position:0% that they will arrange the transaction in<00:06:24.919> a<00:06:25.039> certain<00:06:25.360> way<00:06:25.639> we<00:06:25.759> don't<00:06:25.919> know<00:06:26.080> whether 00:06:26.230 --> 00:06:26.240 align:start position:0% in a certain way we don't know whether 00:06:26.240 --> 00:06:27.950 align:start position:0% in a certain way we don't know whether they're<00:06:26.400> actually<00:06:26.639> doing<00:06:26.840> it<00:06:26.960> or<00:06:27.120> not<00:06:27.720> but<00:06:27.880> in 00:06:27.950 --> 00:06:27.960 align:start position:0% they're actually doing it or not but in 00:06:27.960 --> 00:06:29.670 align:start position:0% they're actually doing it or not but in the<00:06:28.080> case<00:06:28.240> of<00:06:28.400> arbitrium<00:06:28.960> the<00:06:29.080> promise<00:06:29.360> is 00:06:29.670 --> 00:06:29.680 align:start position:0% the case of arbitrium the promise is 00:06:29.680 --> 00:06:31.390 align:start position:0% the case of arbitrium the promise is that<00:06:29.880> it's<00:06:30.000> a<00:06:30.160> first<00:06:30.440> come<00:06:30.639> first<00:06:30.880> serve<00:06:31.280> if 00:06:31.390 --> 00:06:31.400 align:start position:0% that it's a first come first serve if 00:06:31.400 --> 00:06:33.070 align:start position:0% that it's a first come first serve if your<00:06:31.560> transaction<00:06:32.000> comes<00:06:32.319> before<00:06:32.680> that<00:06:32.840> other 00:06:33.070 --> 00:06:33.080 align:start position:0% your transaction comes before that other 00:06:33.080 --> 00:06:35.029 align:start position:0% your transaction comes before that other person<00:06:33.440> we'll<00:06:33.639> put<00:06:33.800> your<00:06:33.919> transaction<00:06:34.440> first 00:06:35.029 --> 00:06:35.039 align:start position:0% person we'll put your transaction first 00:06:35.039 --> 00:06:37.270 align:start position:0% person we'll put your transaction first in<00:06:35.280> in<00:06:35.400> the<00:06:35.560> block<00:06:36.479> but<00:06:36.639> once<00:06:36.840> again<00:06:37.039> it's<00:06:37.160> a 00:06:37.270 --> 00:06:37.280 align:start position:0% in in the block but once again it's a 00:06:37.280 --> 00:06:38.510 align:start position:0% in in the block but once again it's a promise<00:06:37.680> we<00:06:37.800> don't<00:06:37.919> know<00:06:38.080> whether<00:06:38.319> that's 00:06:38.510 --> 00:06:38.520 align:start position:0% promise we don't know whether that's 00:06:38.520 --> 00:06:42.150 align:start position:0% promise we don't know whether that's actually<00:06:38.800> happening<00:06:39.080> or 00:06:42.150 --> 00:06:42.160 align:start position:0% 00:06:42.160 --> 00:06:44.749 align:start position:0% not<00:06:43.160> so<00:06:43.319> let's<00:06:43.560> get<00:06:43.840> based<00:06:44.240> and<00:06:44.360> talk<00:06:44.560> about 00:06:44.749 --> 00:06:44.759 align:start position:0% not so let's get based and talk about 00:06:44.759 --> 00:06:47.430 align:start position:0% not so let's get based and talk about based<00:06:45.039> rollups<00:06:45.440> and<00:06:45.639> pre 00:06:47.430 --> 00:06:47.440 align:start position:0% based rollups and pre 00:06:47.440 --> 00:06:49.950 align:start position:0% based rollups and pre confirmations<00:06:48.440> well<00:06:48.639> the<00:06:48.840> based<00:06:49.360> part<00:06:49.720> is 00:06:49.950 --> 00:06:49.960 align:start position:0% confirmations well the based part is 00:06:49.960 --> 00:06:51.710 align:start position:0% confirmations well the based part is actually<00:06:50.360> not<00:06:50.639> a<00:06:50.800> different<00:06:51.160> variant<00:06:51.520> of<00:06:51.639> a 00:06:51.710 --> 00:06:51.720 align:start position:0% actually not a different variant of a 00:06:51.720 --> 00:06:53.629 align:start position:0% actually not a different variant of a rollup<00:06:52.120> so<00:06:52.280> it<00:06:52.479> it<00:06:52.560> doesn't<00:06:52.880> stand<00:06:53.160> beside<00:06:53.440> a 00:06:53.629 --> 00:06:53.639 align:start position:0% rollup so it it doesn't stand beside a 00:06:53.639 --> 00:06:56.749 align:start position:0% rollup so it it doesn't stand beside a optimistic<00:06:54.160> or<00:06:54.319> ZK<00:06:54.639> rollup<00:06:55.599> instead<00:06:56.080> based<00:06:56.680> is 00:06:56.749 --> 00:06:56.759 align:start position:0% optimistic or ZK rollup instead based is 00:06:56.759 --> 00:06:58.469 align:start position:0% optimistic or ZK rollup instead based is a<00:06:56.919> form<00:06:57.120> of<00:06:57.280> sequencing<00:06:57.960> just<00:06:58.120> like<00:06:58.240> we<00:06:58.360> have 00:06:58.469 --> 00:06:58.479 align:start position:0% a form of sequencing just like we have 00:06:58.479 --> 00:07:00.869 align:start position:0% a form of sequencing just like we have centralized<00:06:58.879> sequencing<00:06:59.319> we<00:06:59.400> have<00:06:59.919> base 00:07:00.869 --> 00:07:00.879 align:start position:0% centralized sequencing we have base 00:07:00.879 --> 00:07:02.790 align:start position:0% centralized sequencing we have base sequencing<00:07:01.879> and<00:07:02.000> in<00:07:02.080> the<00:07:02.199> case<00:07:02.360> of<00:07:02.479> Base 00:07:02.790 --> 00:07:02.800 align:start position:0% sequencing and in the case of Base 00:07:02.800 --> 00:07:05.909 align:start position:0% sequencing and in the case of Base sequencing<00:07:03.800> the<00:07:04.039> L1<00:07:04.639> proposer<00:07:05.479> is<00:07:05.639> the 00:07:05.909 --> 00:07:05.919 align:start position:0% sequencing the L1 proposer is the 00:07:05.919 --> 00:07:08.589 align:start position:0% sequencing the L1 proposer is the sequencer<00:07:06.919> you<00:07:07.080> don't<00:07:07.360> have<00:07:07.879> a<00:07:08.080> centralized 00:07:08.589 --> 00:07:08.599 align:start position:0% sequencer you don't have a centralized 00:07:08.599 --> 00:07:11.189 align:start position:0% sequencer you don't have a centralized server<00:07:08.919> sequencing<00:07:09.919> the<00:07:10.199> transactions 00:07:11.189 --> 00:07:11.199 align:start position:0% server sequencing the transactions 00:07:11.199 --> 00:07:13.070 align:start position:0% server sequencing the transactions instead<00:07:11.560> it's<00:07:11.759> the<00:07:11.879> L1 00:07:13.070 --> 00:07:13.080 align:start position:0% instead it's the L1 00:07:13.080 --> 00:07:15.550 align:start position:0% instead it's the L1 proposal<00:07:14.080> let's<00:07:14.240> say<00:07:14.400> we<00:07:14.520> have<00:07:14.680> Tao<00:07:15.039> Tao<00:07:15.319> is<00:07:15.400> a 00:07:15.550 --> 00:07:15.560 align:start position:0% proposal let's say we have Tao Tao is a 00:07:15.560 --> 00:07:19.430 align:start position:0% proposal let's say we have Tao Tao is a based<00:07:16.160> rollup<00:07:17.160> and<00:07:17.280> in<00:07:17.400> the<00:07:17.520> case<00:07:17.680> of<00:07:18.280> Tao<00:07:19.280> the 00:07:19.430 --> 00:07:19.440 align:start position:0% based rollup and in the case of Tao the 00:07:19.440 --> 00:07:21.350 align:start position:0% based rollup and in the case of Tao the L1<00:07:19.840> proposal<00:07:20.199> literally<00:07:20.520> runs<00:07:20.840> a<00:07:21.000> tao 00:07:21.350 --> 00:07:21.360 align:start position:0% L1 proposal literally runs a tao 00:07:21.360 --> 00:07:23.270 align:start position:0% L1 proposal literally runs a tao software<00:07:21.759> alongside<00:07:22.240> the<00:07:22.440> usual<00:07:22.840> consensus 00:07:23.270 --> 00:07:23.280 align:start position:0% software alongside the usual consensus 00:07:23.280 --> 00:07:26.110 align:start position:0% software alongside the usual consensus and<00:07:23.479> execution<00:07:24.319> clients<00:07:25.319> and<00:07:25.520> whenever<00:07:25.919> their 00:07:26.110 --> 00:07:26.120 align:start position:0% and execution clients and whenever their 00:07:26.120 --> 00:07:28.550 align:start position:0% and execution clients and whenever their block<00:07:26.400> comes<00:07:26.680> in<00:07:27.199> they<00:07:27.360> literally<00:07:27.840> just<00:07:28.080> put 00:07:28.550 --> 00:07:28.560 align:start position:0% block comes in they literally just put 00:07:28.560 --> 00:07:30.710 align:start position:0% block comes in they literally just put pull<00:07:28.800> the<00:07:28.919> blocks<00:07:29.280> pull<00:07:29.599> the<00:07:29.800> L2<00:07:30.160> transactions 00:07:30.710 --> 00:07:30.720 align:start position:0% pull the blocks pull the L2 transactions 00:07:30.720 --> 00:07:33.830 align:start position:0% pull the blocks pull the L2 transactions from<00:07:31.080> public<00:07:31.360> Tao<00:07:31.680> M<00:07:31.919> Pool<00:07:32.599> they<00:07:32.720> order<00:07:33.080> it<00:07:33.599> in 00:07:33.830 --> 00:07:33.840 align:start position:0% from public Tao M Pool they order it in 00:07:33.840 --> 00:07:37.749 align:start position:0% from public Tao M Pool they order it in their<00:07:34.000> L1<00:07:34.360> block<00:07:34.800> and<00:07:35.000> put<00:07:35.199> it<00:07:36.120> on<00:07:36.240> the<00:07:36.759> network 00:07:37.749 --> 00:07:37.759 align:start position:0% their L1 block and put it on the network 00:07:37.759 --> 00:07:40.469 align:start position:0% their L1 block and put it on the network so<00:07:38.319> yeah<00:07:38.440> you<00:07:38.639> basically<00:07:39.080> are<00:07:39.360> inheriting<00:07:40.360> the 00:07:40.469 --> 00:07:40.479 align:start position:0% so yeah you basically are inheriting the 00:07:40.479 --> 00:07:43.309 align:start position:0% so yeah you basically are inheriting the L1<00:07:40.960> security<00:07:41.800> as<00:07:41.919> well<00:07:42.080> as<00:07:42.240> the<00:07:42.360> L1<00:07:42.720> liveness 00:07:43.309 --> 00:07:43.319 align:start position:0% L1 security as well as the L1 liveness 00:07:43.319 --> 00:07:47.390 align:start position:0% L1 security as well as the L1 liveness because<00:07:43.639> the<00:07:43.759> L1<00:07:44.199> itself<00:07:44.520> is<00:07:44.639> your 00:07:47.390 --> 00:07:47.400 align:start position:0% 00:07:47.400 --> 00:07:49.710 align:start position:0% sequencer<00:07:48.400> so<00:07:48.599> just<00:07:48.720> a<00:07:48.879> quick<00:07:49.120> overview<00:07:49.560> of 00:07:49.710 --> 00:07:49.720 align:start position:0% sequencer so just a quick overview of 00:07:49.720 --> 00:07:52.430 align:start position:0% sequencer so just a quick overview of how<00:07:49.960> Tao<00:07:50.479> actually<00:07:50.840> is<00:07:51.159> arranged<00:07:52.159> well<00:07:52.319> you 00:07:52.430 --> 00:07:52.440 align:start position:0% how Tao actually is arranged well you 00:07:52.440 --> 00:07:54.390 align:start position:0% how Tao actually is arranged well you have<00:07:52.560> the<00:07:52.680> rollups<00:07:53.400> inbox<00:07:53.800> contract<00:07:54.199> that<00:07:54.319> I 00:07:54.390 --> 00:07:54.400 align:start position:0% have the rollups inbox contract that I 00:07:54.400 --> 00:07:56.990 align:start position:0% have the rollups inbox contract that I have<00:07:54.560> been<00:07:54.720> talking<00:07:55.039> about<00:07:56.000> and<00:07:56.240> although<00:07:56.680> Tao 00:07:56.990 --> 00:07:57.000 align:start position:0% have been talking about and although Tao 00:07:57.000 --> 00:07:59.670 align:start position:0% have been talking about and although Tao doesn't<00:07:57.360> really<00:07:57.560> call<00:07:57.720> it<00:07:57.879> rollup<00:07:58.319> inbox<00:07:59.319> uh 00:07:59.670 --> 00:07:59.680 align:start position:0% doesn't really call it rollup inbox uh 00:07:59.680 --> 00:08:01.710 align:start position:0% doesn't really call it rollup inbox uh this<00:07:59.759> is<00:07:59.879> the<00:08:00.039> colloquial<00:08:00.560> term<00:08:01.039> Tao<00:08:01.479> has<00:08:01.599> like 00:08:01.710 --> 00:08:01.720 align:start position:0% this is the colloquial term Tao has like 00:08:01.720 --> 00:08:04.830 align:start position:0% this is the colloquial term Tao has like a<00:08:01.840> bunch<00:08:02.039> of<00:08:02.199> contracts<00:08:02.919> that<00:08:03.919> work<00:08:04.360> together 00:08:04.830 --> 00:08:04.840 align:start position:0% a bunch of contracts that work together 00:08:04.840 --> 00:08:07.430 align:start position:0% a bunch of contracts that work together and<00:08:05.080> they<00:08:05.400> just<00:08:05.599> call<00:08:05.759> it<00:08:05.919> Tao<00:08:06.240> L1 00:08:07.430 --> 00:08:07.440 align:start position:0% and they just call it Tao L1 00:08:07.440 --> 00:08:11.390 align:start position:0% and they just call it Tao L1 contract<00:08:08.440> so<00:08:08.680> that's<00:08:08.960> the<00:08:09.360> L1<00:08:10.240> component<00:08:11.240> now 00:08:11.390 --> 00:08:11.400 align:start position:0% contract so that's the L1 component now 00:08:11.400 --> 00:08:13.309 align:start position:0% contract so that's the L1 component now if<00:08:11.479> you're<00:08:11.639> running<00:08:11.879> an<00:08:12.000> ethereum<00:08:12.360> validator 00:08:13.309 --> 00:08:13.319 align:start position:0% if you're running an ethereum validator 00:08:13.319 --> 00:08:15.550 align:start position:0% if you're running an ethereum validator you<00:08:13.479> usually<00:08:13.800> run<00:08:13.960> an<00:08:14.120> execution<00:08:14.639> client<00:08:15.039> and 00:08:15.550 --> 00:08:15.560 align:start position:0% you usually run an execution client and 00:08:15.560 --> 00:08:18.189 align:start position:0% you usually run an execution client and a<00:08:15.720> consensus<00:08:16.199> client<00:08:16.599> right<00:08:17.479> so<00:08:17.599> in<00:08:17.680> a<00:08:17.840> similar 00:08:18.189 --> 00:08:18.199 align:start position:0% a consensus client right so in a similar 00:08:18.199 --> 00:08:20.029 align:start position:0% a consensus client right so in a similar way<00:08:18.639> if<00:08:18.720> you<00:08:18.840> want<00:08:19.039> to<00:08:19.159> run<00:08:19.400> or<00:08:19.560> be<00:08:19.680> a<00:08:19.800> part<00:08:19.960> of 00:08:20.029 --> 00:08:20.039 align:start position:0% way if you want to run or be a part of 00:08:20.039 --> 00:08:23.629 align:start position:0% way if you want to run or be a part of an<00:08:20.159> L2<00:08:20.560> Network<00:08:21.560> the<00:08:21.720> proposer<00:08:22.199> has<00:08:22.319> to<00:08:22.479> run<00:08:23.479> an 00:08:23.629 --> 00:08:23.639 align:start position:0% an L2 Network the proposer has to run an 00:08:23.639 --> 00:08:26.230 align:start position:0% an L2 Network the proposer has to run an L2<00:08:24.000> execution<00:08:24.479> client<00:08:24.759> or<00:08:24.879> an<00:08:25.000> L2<00:08:25.599> and<00:08:25.759> an<00:08:25.879> L2 00:08:26.230 --> 00:08:26.240 align:start position:0% L2 execution client or an L2 and an L2 00:08:26.240 --> 00:08:29.550 align:start position:0% L2 execution client or an L2 and an L2 consensus<00:08:26.720> client<00:08:27.479> so<00:08:27.680> in<00:08:27.840> this<00:08:28.039> case<00:08:28.680> Tao<00:08:29.159> get 00:08:29.550 --> 00:08:29.560 align:start position:0% consensus client so in this case Tao get 00:08:29.560 --> 00:08:31.790 align:start position:0% consensus client so in this case Tao get is<00:08:29.680> the<00:08:29.840> execution<00:08:30.280> clant<00:08:31.159> which<00:08:31.319> is<00:08:31.639> a 00:08:31.790 --> 00:08:31.800 align:start position:0% is the execution clant which is a 00:08:31.800 --> 00:08:34.110 align:start position:0% is the execution clant which is a modification<00:08:32.440> of<00:08:32.599> the<00:08:32.760> standard<00:08:33.360> go 00:08:34.110 --> 00:08:34.120 align:start position:0% modification of the standard go 00:08:34.120 --> 00:08:36.670 align:start position:0% modification of the standard go ethereum<00:08:35.120> and<00:08:35.320> this<00:08:35.479> is<00:08:35.839> where<00:08:36.080> you<00:08:36.320> have<00:08:36.519> the 00:08:36.670 --> 00:08:36.680 align:start position:0% ethereum and this is where you have the 00:08:36.680 --> 00:08:39.190 align:start position:0% ethereum and this is where you have the mempool<00:08:37.240> you<00:08:37.479> have<00:08:37.800> the<00:08:38.000> actual<00:08:38.320> L2<00:08:38.680> chain<00:08:39.039> all 00:08:39.190 --> 00:08:39.200 align:start position:0% mempool you have the actual L2 chain all 00:08:39.200 --> 00:08:41.670 align:start position:0% mempool you have the actual L2 chain all the<00:08:39.399> blocks<00:08:39.839> are<00:08:40.000> formalized<00:08:40.919> and<00:08:41.039> you<00:08:41.200> also 00:08:41.670 --> 00:08:41.680 align:start position:0% the blocks are formalized and you also 00:08:41.680 --> 00:08:45.030 align:start position:0% the blocks are formalized and you also have<00:08:41.880> the<00:08:42.000> evm<00:08:42.640> on<00:08:42.760> the<00:08:42.880> L2<00:08:43.720> Network<00:08:44.720> and<00:08:44.880> then 00:08:45.030 --> 00:08:45.040 align:start position:0% have the evm on the L2 Network and then 00:08:45.040 --> 00:08:47.310 align:start position:0% have the evm on the L2 Network and then we<00:08:45.160> have<00:08:45.320> the<00:08:45.480> Tao<00:08:45.880> client<00:08:46.320> which<00:08:46.480> has<00:08:46.640> some 00:08:47.310 --> 00:08:47.320 align:start position:0% we have the Tao client which has some 00:08:47.320 --> 00:08:49.190 align:start position:0% we have the Tao client which has some subcomponents<00:08:48.320> and<00:08:48.480> this<00:08:48.600> forms<00:08:48.920> the 00:08:49.190 --> 00:08:49.200 align:start position:0% subcomponents and this forms the 00:08:49.200 --> 00:08:51.470 align:start position:0% subcomponents and this forms the consensus<00:08:50.200> client<00:08:50.760> and<00:08:50.880> it<00:08:51.000> deals<00:08:51.320> with 00:08:51.470 --> 00:08:51.480 align:start position:0% consensus client and it deals with 00:08:51.480 --> 00:08:53.030 align:start position:0% consensus client and it deals with proving<00:08:51.880> the<00:08:52.000> blocks<00:08:52.320> and<00:08:52.480> proposing<00:08:52.920> the 00:08:53.030 --> 00:08:53.040 align:start position:0% proving the blocks and proposing the 00:08:53.040 --> 00:08:56.509 align:start position:0% proving the blocks and proposing the blocks<00:08:53.680> whenever 00:08:56.509 --> 00:08:56.519 align:start position:0% 00:08:56.519 --> 00:08:59.230 align:start position:0% required<00:08:57.519> now<00:08:57.720> today<00:08:58.120> the<00:08:58.279> most<00:08:58.839> important 00:08:59.230 --> 00:08:59.240 align:start position:0% required now today the most important 00:08:59.240 --> 00:09:01.949 align:start position:0% required now today the most important thing<00:08:59.560> for<00:08:59.760> us<00:09:00.120> are<00:09:00.320> block<00:09:00.640> proposals<00:09:01.640> because 00:09:01.949 --> 00:09:01.959 align:start position:0% thing for us are block proposals because 00:09:01.959 --> 00:09:03.350 align:start position:0% thing for us are block proposals because that's<00:09:02.279> where<00:09:02.560> the<00:09:02.680> whole<00:09:02.920> concept<00:09:03.240> of 00:09:03.350 --> 00:09:03.360 align:start position:0% that's where the whole concept of 00:09:03.360 --> 00:09:05.790 align:start position:0% that's where the whole concept of pre-confirmation<00:09:03.839> will<00:09:04.680> be<00:09:04.839> built 00:09:05.790 --> 00:09:05.800 align:start position:0% pre-confirmation will be built 00:09:05.800 --> 00:09:09.030 align:start position:0% pre-confirmation will be built upon<00:09:06.800> so<00:09:06.959> how<00:09:07.079> exactly<00:09:07.680> block<00:09:08.079> proposals<00:09:08.640> work 00:09:09.030 --> 00:09:09.040 align:start position:0% upon so how exactly block proposals work 00:09:09.040 --> 00:09:12.590 align:start position:0% upon so how exactly block proposals work in<00:09:09.240> Tao<00:09:09.680> or<00:09:09.839> in<00:09:09.959> a<00:09:10.120> based<00:09:10.760> rollup<00:09:11.760> so<00:09:12.000> well<00:09:12.480> when 00:09:12.590 --> 00:09:12.600 align:start position:0% in Tao or in a based rollup so well when 00:09:12.600 --> 00:09:14.269 align:start position:0% in Tao or in a based rollup so well when you're<00:09:12.760> making<00:09:12.959> a<00:09:13.079> transaction<00:09:13.519> using<00:09:14.040> any 00:09:14.269 --> 00:09:14.279 align:start position:0% you're making a transaction using any 00:09:14.279 --> 00:09:16.790 align:start position:0% you're making a transaction using any kind<00:09:14.440> of<00:09:14.560> standard<00:09:14.959> wallet<00:09:15.959> it<00:09:16.120> goes<00:09:16.320> to<00:09:16.600> the 00:09:16.790 --> 00:09:16.800 align:start position:0% kind of standard wallet it goes to the 00:09:16.800 --> 00:09:18.910 align:start position:0% kind of standard wallet it goes to the meol<00:09:17.399> or<00:09:17.560> the<00:09:17.720> public<00:09:17.959> me<00:09:18.240> pool<00:09:18.600> which<00:09:18.720> is 00:09:18.910 --> 00:09:18.920 align:start position:0% meol or the public me pool which is 00:09:18.920 --> 00:09:20.350 align:start position:0% meol or the public me pool which is offered<00:09:19.320> by 00:09:20.350 --> 00:09:20.360 align:start position:0% offered by 00:09:20.360 --> 00:09:23.509 align:start position:0% offered by Tao<00:09:21.360> and<00:09:21.680> every<00:09:22.040> few<00:09:22.399> seconds<00:09:22.920> or<00:09:23.120> depending 00:09:23.509 --> 00:09:23.519 align:start position:0% Tao and every few seconds or depending 00:09:23.519 --> 00:09:25.310 align:start position:0% Tao and every few seconds or depending upon<00:09:23.800> what<00:09:23.959> algorithm<00:09:24.519> the<00:09:24.680> proposer<00:09:25.079> is 00:09:25.310 --> 00:09:25.320 align:start position:0% upon what algorithm the proposer is 00:09:25.320 --> 00:09:28.230 align:start position:0% upon what algorithm the proposer is using<00:09:26.320> transactions<00:09:26.959> are<00:09:27.160> feted<00:09:27.680> from<00:09:28.120> the 00:09:28.230 --> 00:09:28.240 align:start position:0% using transactions are feted from the 00:09:28.240 --> 00:09:31.870 align:start position:0% using transactions are feted from the mempool<00:09:29.560> and<00:09:29.760> this<00:09:30.200> transaction<00:09:31.000> batch<00:09:31.440> forms 00:09:31.870 --> 00:09:31.880 align:start position:0% mempool and this transaction batch forms 00:09:31.880 --> 00:09:34.350 align:start position:0% mempool and this transaction batch forms the<00:09:32.040> actual<00:09:32.680> Delta<00:09:33.680> and<00:09:33.800> when<00:09:33.920> you're<00:09:34.079> calling 00:09:34.350 --> 00:09:34.360 align:start position:0% the actual Delta and when you're calling 00:09:34.360 --> 00:09:35.670 align:start position:0% the actual Delta and when you're calling the<00:09:34.480> RO<00:09:34.680> up<00:09:34.800> inbox<00:09:35.160> contract<00:09:35.480> you're 00:09:35.670 --> 00:09:35.680 align:start position:0% the RO up inbox contract you're 00:09:35.680 --> 00:09:37.150 align:start position:0% the RO up inbox contract you're basically<00:09:36.000> calling<00:09:36.279> a<00:09:36.440> function<00:09:36.880> which<00:09:37.000> is 00:09:37.150 --> 00:09:37.160 align:start position:0% basically calling a function which is 00:09:37.160 --> 00:09:38.790 align:start position:0% basically calling a function which is proposed<00:09:37.600> block<00:09:37.920> and<00:09:38.000> you're<00:09:38.200> just<00:09:38.399> passing 00:09:38.790 --> 00:09:38.800 align:start position:0% proposed block and you're just passing 00:09:38.800 --> 00:09:39.949 align:start position:0% proposed block and you're just passing this<00:09:39.079> Delta 00:09:39.949 --> 00:09:39.959 align:start position:0% this Delta 00:09:39.959 --> 00:09:42.269 align:start position:0% this Delta along<00:09:40.959> now<00:09:41.120> you<00:09:41.279> might<00:09:41.440> be<00:09:41.560> wondering<00:09:42.000> well 00:09:42.269 --> 00:09:42.279 align:start position:0% along now you might be wondering well 00:09:42.279 --> 00:09:43.949 align:start position:0% along now you might be wondering well that's<00:09:42.480> the<00:09:42.640> Delta<00:09:42.959> fine<00:09:43.240> where's<00:09:43.440> the 00:09:43.949 --> 00:09:43.959 align:start position:0% that's the Delta fine where's the 00:09:43.959 --> 00:09:46.910 align:start position:0% that's the Delta fine where's the transition<00:09:44.959> so<00:09:45.160> in<00:09:45.440> Tao<00:09:46.000> it's<00:09:46.120> a<00:09:46.279> two-step 00:09:46.910 --> 00:09:46.920 align:start position:0% transition so in Tao it's a two-step 00:09:46.920 --> 00:09:49.870 align:start position:0% transition so in Tao it's a two-step process<00:09:47.920> the<00:09:48.120> Delta<00:09:48.440> is<00:09:48.600> gone<00:09:49.440> and<00:09:49.600> now<00:09:49.760> we 00:09:49.870 --> 00:09:49.880 align:start position:0% process the Delta is gone and now we 00:09:49.880 --> 00:09:52.110 align:start position:0% process the Delta is gone and now we have<00:09:50.040> the<00:09:50.160> Tao<00:09:50.519> prover<00:09:51.000> which<00:09:51.399> comes<00:09:51.640> in<00:09:51.880> later 00:09:52.110 --> 00:09:52.120 align:start position:0% have the Tao prover which comes in later 00:09:52.120 --> 00:09:54.630 align:start position:0% have the Tao prover which comes in later on<00:09:52.680> and<00:09:52.959> just<00:09:53.079> says<00:09:53.680> okay<00:09:53.959> remember<00:09:54.399> that 00:09:54.630 --> 00:09:54.640 align:start position:0% on and just says okay remember that 00:09:54.640 --> 00:09:57.509 align:start position:0% on and just says okay remember that Delta<00:09:55.079> that<00:09:55.279> was<00:09:55.519> pushed<00:09:56.519> uh<00:09:56.760> a<00:09:56.880> few<00:09:57.079> seconds 00:09:57.509 --> 00:09:57.519 align:start position:0% Delta that was pushed uh a few seconds 00:09:57.519 --> 00:09:59.630 align:start position:0% Delta that was pushed uh a few seconds ago<00:09:57.959> or<00:09:58.160> few<00:09:58.320> minutes<00:09:58.640> ago<00:09:58.959> you<00:09:59.079> see<00:09:59.440> this<00:09:59.560> is 00:09:59.630 --> 00:09:59.640 align:start position:0% ago or few minutes ago you see this is 00:09:59.640 --> 00:10:02.949 align:start position:0% ago or few minutes ago you see this is the<00:09:59.800> transition<00:10:00.360> that<00:10:00.560> that<00:10:00.760> Delta<00:10:01.959> causes 00:10:02.949 --> 00:10:02.959 align:start position:0% the transition that that Delta causes 00:10:02.959 --> 00:10:06.750 align:start position:0% the transition that that Delta causes and<00:10:03.440> since<00:10:03.720> Tao<00:10:04.079> is<00:10:04.160> a<00:10:04.240> ZK<00:10:04.519> rollup<00:10:05.240> it<00:10:05.600> pushes<00:10:06.600> a 00:10:06.750 --> 00:10:06.760 align:start position:0% and since Tao is a ZK rollup it pushes a 00:10:06.760 --> 00:10:08.670 align:start position:0% and since Tao is a ZK rollup it pushes a concise<00:10:07.160> proof<00:10:07.519> along<00:10:07.800> with<00:10:07.959> it<00:10:08.160> like<00:10:08.440> okay 00:10:08.670 --> 00:10:08.680 align:start position:0% concise proof along with it like okay 00:10:08.680 --> 00:10:09.949 align:start position:0% concise proof along with it like okay this<00:10:08.760> is<00:10:08.880> the<00:10:09.000> transition<00:10:09.440> and<00:10:09.560> this<00:10:09.640> is<00:10:09.760> the 00:10:09.949 --> 00:10:09.959 align:start position:0% this is the transition and this is the 00:10:09.959 --> 00:10:13.310 align:start position:0% this is the transition and this is the proof<00:10:10.320> that<00:10:10.640> the<00:10:10.800> Delta<00:10:11.160> caused<00:10:11.560> this 00:10:13.310 --> 00:10:13.320 align:start position:0% proof that the Delta caused this 00:10:13.320 --> 00:10:15.790 align:start position:0% proof that the Delta caused this transition<00:10:14.320> now<00:10:14.480> the<00:10:14.600> most<00:10:14.800> important<00:10:15.200> aspect 00:10:15.790 --> 00:10:15.800 align:start position:0% transition now the most important aspect 00:10:15.800 --> 00:10:16.870 align:start position:0% transition now the most important aspect Tao 00:10:16.870 --> 00:10:16.880 align:start position:0% Tao 00:10:16.880 --> 00:10:19.870 align:start position:0% Tao driver<00:10:17.880> so<00:10:18.160> once<00:10:18.640> these<00:10:18.839> L2<00:10:19.279> blocks<00:10:19.519> are<00:10:19.720> put 00:10:19.870 --> 00:10:19.880 align:start position:0% driver so once these L2 blocks are put 00:10:19.880 --> 00:10:22.870 align:start position:0% driver so once these L2 blocks are put on<00:10:20.399> L1<00:10:21.399> there<00:10:21.519> is<00:10:21.640> an<00:10:21.920> block<00:10:22.200> proposed<00:10:22.560> event 00:10:22.870 --> 00:10:22.880 align:start position:0% on L1 there is an block proposed event 00:10:22.880 --> 00:10:24.630 align:start position:0% on L1 there is an block proposed event that<00:10:22.959> is<00:10:23.079> released<00:10:23.560> which<00:10:23.640> shows<00:10:23.920> that<00:10:24.200> hey 00:10:24.630 --> 00:10:24.640 align:start position:0% that is released which shows that hey 00:10:24.640 --> 00:10:27.150 align:start position:0% that is released which shows that hey okay<00:10:24.839> this<00:10:24.959> L2<00:10:25.360> block<00:10:25.760> was<00:10:26.040> put<00:10:26.200> in<00:10:26.360> the<00:10:26.480> L1 00:10:27.150 --> 00:10:27.160 align:start position:0% okay this L2 block was put in the L1 00:10:27.160 --> 00:10:29.310 align:start position:0% okay this L2 block was put in the L1 contract<00:10:28.160> and<00:10:28.320> whenever<00:10:28.760> that<00:10:28.920> block 00:10:29.310 --> 00:10:29.320 align:start position:0% contract and whenever that block 00:10:29.320 --> 00:10:31.990 align:start position:0% contract and whenever that block proposed<00:10:29.720> event<00:10:30.079> is<00:10:30.320> released<00:10:31.320> Tao<00:10:31.680> driver 00:10:31.990 --> 00:10:32.000 align:start position:0% proposed event is released Tao driver 00:10:32.000 --> 00:10:35.030 align:start position:0% proposed event is released Tao driver listens<00:10:32.320> to<00:10:32.519> it<00:10:33.399> and<00:10:33.640> advances<00:10:34.200> the<00:10:34.440> head<00:10:34.680> in 00:10:35.030 --> 00:10:35.040 align:start position:0% listens to it and advances the head in 00:10:35.040 --> 00:10:37.470 align:start position:0% listens to it and advances the head in get<00:10:36.040> advancing<00:10:36.480> the<00:10:36.639> head<00:10:36.839> basically<00:10:37.279> means 00:10:37.470 --> 00:10:37.480 align:start position:0% get advancing the head basically means 00:10:37.480 --> 00:10:39.190 align:start position:0% get advancing the head basically means you're<00:10:37.680> formalizing<00:10:38.279> and<00:10:38.440> putting<00:10:38.680> an<00:10:38.800> L2 00:10:39.190 --> 00:10:39.200 align:start position:0% you're formalizing and putting an L2 00:10:39.200 --> 00:10:43.350 align:start position:0% you're formalizing and putting an L2 block<00:10:39.920> within<00:10:40.920> uh<00:10:41.240> the<00:10:41.360> L2<00:10:42.079> Network<00:10:43.079> and<00:10:43.240> this 00:10:43.350 --> 00:10:43.360 align:start position:0% block within uh the L2 Network and this 00:10:43.360 --> 00:10:44.949 align:start position:0% block within uh the L2 Network and this is<00:10:43.519> when<00:10:43.680> the<00:10:43.800> wallets<00:10:44.240> end<00:10:44.440> up<00:10:44.600> getting<00:10:44.839> the 00:10:44.949 --> 00:10:44.959 align:start position:0% is when the wallets end up getting the 00:10:44.959 --> 00:10:47.030 align:start position:0% is when the wallets end up getting the transaction<00:10:45.440> receipt<00:10:45.839> or<00:10:46.000> the 00:10:47.030 --> 00:10:47.040 align:start position:0% transaction receipt or the 00:10:47.040 --> 00:10:49.069 align:start position:0% transaction receipt or the confirmation<00:10:48.040> so<00:10:48.200> you<00:10:48.279> see<00:10:48.519> the<00:10:48.639> catch<00:10:48.880> here 00:10:49.069 --> 00:10:49.079 align:start position:0% confirmation so you see the catch here 00:10:49.079 --> 00:10:51.550 align:start position:0% confirmation so you see the catch here is<00:10:49.279> that<00:10:50.079> Tao<00:10:50.440> driver<00:10:50.760> only<00:10:51.200> receives<00:10:51.440> the 00:10:51.550 --> 00:10:51.560 align:start position:0% is that Tao driver only receives the 00:10:51.560 --> 00:10:54.069 align:start position:0% is that Tao driver only receives the block<00:10:51.839> proposed<00:10:52.160> event<00:10:52.440> every<00:10:52.639> 12<00:10:53.079> seconds 00:10:54.069 --> 00:10:54.079 align:start position:0% block proposed event every 12 seconds 00:10:54.079 --> 00:10:55.470 align:start position:0% block proposed event every 12 seconds that<00:10:54.200> means<00:10:54.800> when<00:10:54.959> you're<00:10:55.160> making<00:10:55.360> a 00:10:55.470 --> 00:10:55.480 align:start position:0% that means when you're making a 00:10:55.480 --> 00:10:57.590 align:start position:0% that means when you're making a transaction<00:10:55.880> on<00:10:56.040> Tao<00:10:56.720> you<00:10:56.920> get<00:10:57.079> a<00:10:57.240> transaction 00:10:57.590 --> 00:10:57.600 align:start position:0% transaction on Tao you get a transaction 00:10:57.600 --> 00:11:00.389 align:start position:0% transaction on Tao you get a transaction receipt<00:10:57.920> after<00:10:58.120> 12<00:10:58.399> seconds<00:10:58.839> which<00:10:58.959> is<00:10:59.600> huge 00:11:00.389 --> 00:11:00.399 align:start position:0% receipt after 12 seconds which is huge 00:11:00.399 --> 00:11:03.150 align:start position:0% receipt after 12 seconds which is huge that's<00:11:00.680> not<00:11:00.959> ideal<00:11:01.519> for<00:11:02.519> a<00:11:02.600> rollup<00:11:02.959> or<00:11:03.040> a 00:11:03.150 --> 00:11:03.160 align:start position:0% that's not ideal for a rollup or a 00:11:03.160 --> 00:11:05.470 align:start position:0% that's not ideal for a rollup or a scaling 00:11:05.470 --> 00:11:05.480 align:start position:0% scaling 00:11:05.480 --> 00:11:07.629 align:start position:0% scaling solution<00:11:06.480> and<00:11:06.680> that's<00:11:06.880> very<00:11:07.120> evident<00:11:07.519> from 00:11:07.629 --> 00:11:07.639 align:start position:0% solution and that's very evident from 00:11:07.639 --> 00:11:10.550 align:start position:0% solution and that's very evident from the<00:11:07.800> DU<00:11:08.120> analytics<00:11:08.760> graph<00:11:09.160> of<00:11:09.519> Tao's<00:11:10.240> block 00:11:10.550 --> 00:11:10.560 align:start position:0% the DU analytics graph of Tao's block 00:11:10.560 --> 00:11:13.509 align:start position:0% the DU analytics graph of Tao's block times<00:11:11.279> it's<00:11:11.880> average<00:11:12.399> between<00:11:12.720> 12<00:11:13.000> to<00:11:13.160> 24 00:11:13.509 --> 00:11:13.519 align:start position:0% times it's average between 12 to 24 00:11:13.519 --> 00:11:14.870 align:start position:0% times it's average between 12 to 24 seconds<00:11:13.920> which<00:11:14.120> makes<00:11:14.399> sense<00:11:14.680> it's 00:11:14.870 --> 00:11:14.880 align:start position:0% seconds which makes sense it's 00:11:14.880 --> 00:11:17.230 align:start position:0% seconds which makes sense it's inheriting<00:11:15.399> L1<00:11:15.920> block<00:11:16.279> time<00:11:16.760> that's<00:11:17.040> not 00:11:17.230 --> 00:11:17.240 align:start position:0% inheriting L1 block time that's not 00:11:17.240 --> 00:11:18.389 align:start position:0% inheriting L1 block time that's not ideal<00:11:17.600> at 00:11:18.389 --> 00:11:18.399 align:start position:0% ideal at 00:11:18.399 --> 00:11:21.670 align:start position:0% ideal at all<00:11:19.399> so<00:11:19.519> we<00:11:19.639> need<00:11:19.839> pre-confirmation<00:11:20.680> and 00:11:21.670 --> 00:11:21.680 align:start position:0% all so we need pre-confirmation and 00:11:21.680 --> 00:11:24.110 align:start position:0% all so we need pre-confirmation and pre-confirmation<00:11:22.160> is<00:11:22.639> not<00:11:22.839> something<00:11:23.120> new<00:11:24.000> we 00:11:24.110 --> 00:11:24.120 align:start position:0% pre-confirmation is not something new we 00:11:24.120 --> 00:11:25.629 align:start position:0% pre-confirmation is not something new we have<00:11:24.279> already<00:11:24.560> had<00:11:24.680> it<00:11:24.800> on<00:11:24.920> arbitrum<00:11:25.399> for<00:11:25.519> a 00:11:25.629 --> 00:11:25.639 align:start position:0% have already had it on arbitrum for a 00:11:25.639 --> 00:11:29.350 align:start position:0% have already had it on arbitrum for a long<00:11:25.880> while<00:11:26.160> and<00:11:26.959> several<00:11:27.279> other<00:11:27.440> rollups 00:11:29.350 --> 00:11:29.360 align:start position:0% long while and several other rollups 00:11:29.360 --> 00:11:30.790 align:start position:0% long while and several other rollups again<00:11:29.560> show<00:11:29.760> off<00:11:29.920> hands<00:11:30.160> how<00:11:30.279> many<00:11:30.480> of<00:11:30.600> you 00:11:30.790 --> 00:11:30.800 align:start position:0% again show off hands how many of you 00:11:30.800 --> 00:11:33.150 align:start position:0% again show off hands how many of you have<00:11:31.040> transacted<00:11:31.519> on 00:11:33.150 --> 00:11:33.160 align:start position:0% have transacted on 00:11:33.160 --> 00:11:34.990 align:start position:0% have transacted on arbitrium<00:11:34.160> and<00:11:34.279> when<00:11:34.360> you<00:11:34.480> transact<00:11:34.880> on 00:11:34.990 --> 00:11:35.000 align:start position:0% arbitrium and when you transact on 00:11:35.000 --> 00:11:36.550 align:start position:0% arbitrium and when you transact on arbitrium<00:11:35.639> you<00:11:35.839> basically<00:11:36.279> get<00:11:36.440> a 00:11:36.550 --> 00:11:36.560 align:start position:0% arbitrium you basically get a 00:11:36.560 --> 00:11:38.150 align:start position:0% arbitrium you basically get a transaction<00:11:37.000> receipt<00:11:37.399> like<00:11:37.519> in<00:11:37.600> a<00:11:37.760> very<00:11:37.880> small 00:11:38.150 --> 00:11:38.160 align:start position:0% transaction receipt like in a very small 00:11:38.160 --> 00:11:40.269 align:start position:0% transaction receipt like in a very small period<00:11:38.440> of<00:11:38.639> time<00:11:38.920> like<00:11:39.399> half<00:11:39.560> a<00:11:39.720> second<00:11:40.040> 1 00:11:40.269 --> 00:11:40.279 align:start position:0% period of time like half a second 1 00:11:40.279 --> 00:11:43.670 align:start position:0% period of time like half a second 1 second<00:11:41.240> sometimes<00:11:41.440> 2<00:11:42.120> seconds<00:11:43.120> but<00:11:43.279> the<00:11:43.440> point 00:11:43.670 --> 00:11:43.680 align:start position:0% second sometimes 2 seconds but the point 00:11:43.680 --> 00:11:46.590 align:start position:0% second sometimes 2 seconds but the point here<00:11:43.839> is<00:11:44.040> that<00:11:44.519> arbitrum<00:11:45.040> only<00:11:45.480> posts<00:11:46.000> blocks 00:11:46.590 --> 00:11:46.600 align:start position:0% here is that arbitrum only posts blocks 00:11:46.600 --> 00:11:49.310 align:start position:0% here is that arbitrum only posts blocks every<00:11:46.839> 2<00:11:47.040> minutes<00:11:47.399> on<00:11:47.680> L1<00:11:48.680> so<00:11:48.880> how<00:11:49.040> are<00:11:49.160> you 00:11:49.310 --> 00:11:49.320 align:start position:0% every 2 minutes on L1 so how are you 00:11:49.320 --> 00:11:51.030 align:start position:0% every 2 minutes on L1 so how are you getting<00:11:49.680> this<00:11:49.839> transaction<00:11:50.399> receipt 00:11:51.030 --> 00:11:51.040 align:start position:0% getting this transaction receipt 00:11:51.040 --> 00:11:52.710 align:start position:0% getting this transaction receipt immediately<00:11:52.040> it's<00:11:52.240> because<00:11:52.480> that's<00:11:52.600> a 00:11:52.710 --> 00:11:52.720 align:start position:0% immediately it's because that's a 00:11:52.720 --> 00:11:55.069 align:start position:0% immediately it's because that's a pre-confirmation<00:11:53.399> they're<00:11:54.399> giving<00:11:54.680> you<00:11:54.880> a 00:11:55.069 --> 00:11:55.079 align:start position:0% pre-confirmation they're giving you a 00:11:55.079 --> 00:11:57.430 align:start position:0% pre-confirmation they're giving you a promise<00:11:55.480> that<00:11:55.720> hey<00:11:56.000> see<00:11:56.360> this<00:11:56.480> is<00:11:56.600> the<00:11:56.760> receipt 00:11:57.430 --> 00:11:57.440 align:start position:0% promise that hey see this is the receipt 00:11:57.440 --> 00:11:59.269 align:start position:0% promise that hey see this is the receipt and<00:11:57.680> we<00:11:57.800> will<00:11:57.959> be<00:11:58.120> putting<00:11:58.399> this<00:11:58.560> on<00:11:58.680> the<00:11:58.800> L1 00:11:59.269 --> 00:11:59.279 align:start position:0% and we will be putting this on the L1 00:11:59.279 --> 00:12:01.430 align:start position:0% and we will be putting this on the L1 eventually<00:12:00.200> in<00:12:00.360> Tao<00:12:00.720> you<00:12:00.800> have<00:12:00.920> to<00:12:01.079> wait<00:12:01.279> for 00:12:01.430 --> 00:12:01.440 align:start position:0% eventually in Tao you have to wait for 00:12:01.440 --> 00:12:03.389 align:start position:0% eventually in Tao you have to wait for it<00:12:01.560> to<00:12:01.920> put<00:12:02.079> be<00:12:02.240> put<00:12:02.399> on<00:12:02.480> the 00:12:03.389 --> 00:12:03.399 align:start position:0% it to put be put on the 00:12:03.399 --> 00:12:06.629 align:start position:0% it to put be put on the L1<00:12:04.399> but<00:12:04.600> well<00:12:05.480> this<00:12:05.639> gives<00:12:05.920> better<00:12:06.120> ux<00:12:06.480> for 00:12:06.629 --> 00:12:06.639 align:start position:0% L1 but well this gives better ux for 00:12:06.639 --> 00:12:10.790 align:start position:0% L1 but well this gives better ux for arbitrum<00:12:07.079> and<00:12:07.399> bad<00:12:07.639> ux<00:12:08.079> to 00:12:10.790 --> 00:12:10.800 align:start position:0% arbitrum and bad ux to 00:12:10.800 --> 00:12:13.790 align:start position:0% arbitrum and bad ux to Tao<00:12:11.800> now<00:12:12.000> what<00:12:12.160> if<00:12:12.959> we<00:12:13.079> want<00:12:13.279> to<00:12:13.480> put 00:12:13.790 --> 00:12:13.800 align:start position:0% Tao now what if we want to put 00:12:13.800 --> 00:12:17.110 align:start position:0% Tao now what if we want to put pre-confirmation<00:12:14.279> on<00:12:15.440> Tao<00:12:16.440> it's<00:12:16.639> really 00:12:17.110 --> 00:12:17.120 align:start position:0% pre-confirmation on Tao it's really 00:12:17.120 --> 00:12:19.670 align:start position:0% pre-confirmation on Tao it's really tricky<00:12:18.120> because<00:12:18.480> in<00:12:18.600> the<00:12:18.760> case<00:12:18.959> of<00:12:19.160> arbitrum 00:12:19.670 --> 00:12:19.680 align:start position:0% tricky because in the case of arbitrum 00:12:19.680 --> 00:12:21.870 align:start position:0% tricky because in the case of arbitrum we<00:12:19.839> have<00:12:20.320> one<00:12:20.519> server<00:12:20.920> literally<00:12:21.320> one<00:12:21.519> server 00:12:21.870 --> 00:12:21.880 align:start position:0% we have one server literally one server 00:12:21.880 --> 00:12:23.829 align:start position:0% we have one server literally one server in<00:12:22.000> one<00:12:22.160> corner<00:12:22.440> of<00:12:22.600> the<00:12:22.680> world<00:12:23.279> just<00:12:23.440> running 00:12:23.829 --> 00:12:23.839 align:start position:0% in one corner of the world just running 00:12:23.839 --> 00:12:25.790 align:start position:0% in one corner of the world just running except<00:12:24.199> ordering<00:12:24.560> transactions<00:12:25.440> providing 00:12:25.790 --> 00:12:25.800 align:start position:0% except ordering transactions providing 00:12:25.800 --> 00:12:29.350 align:start position:0% except ordering transactions providing pre-<00:12:26.440> confirmations<00:12:27.600> easy<00:12:28.600> in<00:12:28.760> the<00:12:28.880> case<00:12:29.199> of 00:12:29.350 --> 00:12:29.360 align:start position:0% pre- confirmations easy in the case of 00:12:29.360 --> 00:12:32.389 align:start position:0% pre- confirmations easy in the case of based<00:12:30.079> rollups<00:12:31.079> the<00:12:31.199> sequencer<00:12:31.720> is<00:12:31.920> changing 00:12:32.389 --> 00:12:32.399 align:start position:0% based rollups the sequencer is changing 00:12:32.399 --> 00:12:34.389 align:start position:0% based rollups the sequencer is changing every<00:12:32.600> single<00:12:32.920> slot<00:12:33.440> the<00:12:33.600> proposer<00:12:34.000> changes 00:12:34.389 --> 00:12:34.399 align:start position:0% every single slot the proposer changes 00:12:34.399 --> 00:12:37.629 align:start position:0% every single slot the proposer changes every<00:12:34.600> single<00:12:34.880> slot<00:12:35.560> so<00:12:36.199> well<00:12:37.040> the<00:12:37.199> sequencer 00:12:37.629 --> 00:12:37.639 align:start position:0% every single slot so well the sequencer 00:12:37.639 --> 00:12:41.069 align:start position:0% every single slot so well the sequencer changes<00:12:38.000> every<00:12:38.160> single<00:12:38.800> slot<00:12:39.800> and<00:12:40.000> then<00:12:40.839> these 00:12:41.069 --> 00:12:41.079 align:start position:0% changes every single slot and then these 00:12:41.079 --> 00:12:42.629 align:start position:0% changes every single slot and then these days<00:12:41.320> we<00:12:41.440> don't<00:12:41.639> have<00:12:41.760> the<00:12:41.920> proposer<00:12:42.320> building 00:12:42.629 --> 00:12:42.639 align:start position:0% days we don't have the proposer building 00:12:42.639 --> 00:12:44.829 align:start position:0% days we don't have the proposer building the<00:12:42.760> blocks<00:12:43.639> the<00:12:43.760> blocks<00:12:44.040> are<00:12:44.240> actually<00:12:44.480> built 00:12:44.829 --> 00:12:44.839 align:start position:0% the blocks the blocks are actually built 00:12:44.839 --> 00:12:48.430 align:start position:0% the blocks the blocks are actually built via<00:12:45.160> a<00:12:45.320> PBS<00:12:46.079> pipeline<00:12:46.720> like<00:12:47.040> me<00:12:47.480> boost<00:12:48.279> by 00:12:48.430 --> 00:12:48.440 align:start position:0% via a PBS pipeline like me boost by 00:12:48.440 --> 00:12:50.430 align:start position:0% via a PBS pipeline like me boost by flash<00:12:48.800> Bots<00:12:49.440> where<00:12:49.639> Builders<00:12:50.079> build<00:12:50.320> the 00:12:50.430 --> 00:12:50.440 align:start position:0% flash Bots where Builders build the 00:12:50.440 --> 00:12:52.470 align:start position:0% flash Bots where Builders build the blocks<00:12:50.760> for<00:12:51.040> you<00:12:51.639> or<00:12:51.839> for<00:12:52.040> you<00:12:52.199> as<00:12:52.360> the 00:12:52.470 --> 00:12:52.480 align:start position:0% blocks for you or for you as the 00:12:52.480 --> 00:12:54.750 align:start position:0% blocks for you or for you as the proposer<00:12:53.440> and<00:12:53.560> then<00:12:53.760> you<00:12:54.000> just<00:12:54.199> propose<00:12:54.600> the 00:12:54.750 --> 00:12:54.760 align:start position:0% proposer and then you just propose the 00:12:54.760 --> 00:12:56.470 align:start position:0% proposer and then you just propose the block<00:12:55.240> which<00:12:55.680> which<00:12:55.839> whichever<00:12:56.160> Builder 00:12:56.470 --> 00:12:56.480 align:start position:0% block which which whichever Builder 00:12:56.480 --> 00:12:57.790 align:start position:0% block which which whichever Builder gives<00:12:56.639> you<00:12:56.760> the<00:12:56.880> highest<00:12:57.160> bid<00:12:57.360> you<00:12:57.480> just<00:12:57.600> take 00:12:57.790 --> 00:12:57.800 align:start position:0% gives you the highest bid you just take 00:12:57.800 --> 00:12:59.430 align:start position:0% gives you the highest bid you just take their<00:12:57.959> block<00:12:58.199> and<00:12:58.320> propose<00:12:58.639> it<00:12:59.160> you<00:12:59.240> don't 00:12:59.430 --> 00:12:59.440 align:start position:0% their block and propose it you don't 00:12:59.440 --> 00:13:00.870 align:start position:0% their block and propose it you don't even<00:12:59.639> have<00:12:59.760> any<00:12:59.959> control<00:13:00.279> over<00:13:00.480> what's<00:13:00.639> in<00:13:00.760> the 00:13:00.870 --> 00:13:00.880 align:start position:0% even have any control over what's in the 00:13:00.880 --> 00:13:04.110 align:start position:0% even have any control over what's in the block<00:13:01.839> so<00:13:02.079> how<00:13:02.320> exactly<00:13:02.800> will<00:13:02.959> you<00:13:03.800> put<00:13:03.959> in 00:13:04.110 --> 00:13:04.120 align:start position:0% block so how exactly will you put in 00:13:04.120 --> 00:13:05.750 align:start position:0% block so how exactly will you put in base<00:13:04.360> prec<00:13:04.600> confirmations<00:13:05.240> with<00:13:05.440> three 00:13:05.750 --> 00:13:05.760 align:start position:0% base prec confirmations with three 00:13:05.760 --> 00:13:07.350 align:start position:0% base prec confirmations with three layers<00:13:06.240> of 00:13:07.350 --> 00:13:07.360 align:start position:0% layers of 00:13:07.360 --> 00:13:10.150 align:start position:0% layers of complexity<00:13:08.360> well<00:13:08.519> we<00:13:08.639> have<00:13:08.800> done<00:13:08.959> it<00:13:09.880> and 00:13:10.150 --> 00:13:10.160 align:start position:0% complexity well we have done it and 00:13:10.160 --> 00:13:11.990 align:start position:0% complexity well we have done it and let's<00:13:10.360> start<00:13:10.680> with<00:13:10.920> the<00:13:11.079> design 00:13:11.990 --> 00:13:12.000 align:start position:0% let's start with the design 00:13:12.000 --> 00:13:14.030 align:start position:0% let's start with the design principles<00:13:13.000> maybe<00:13:13.399> a<00:13:13.519> quick<00:13:13.680> round<00:13:13.880> of 00:13:14.030 --> 00:13:14.040 align:start position:0% principles maybe a quick round of 00:13:14.040 --> 00:13:17.949 align:start position:0% principles maybe a quick round of questions<00:13:14.399> if<00:13:14.560> anyone<00:13:15.480> has<00:13:15.680> any<00:13:16.079> questions<00:13:17.079> no 00:13:17.949 --> 00:13:17.959 align:start position:0% questions if anyone has any questions no 00:13:17.959 --> 00:13:22.910 align:start position:0% questions if anyone has any questions no okay<00:13:18.880> take<00:13:19.000> it<00:13:19.279> over<00:13:20.279> all<00:13:20.720> right<00:13:21.720> great<00:13:22.079> thank 00:13:22.910 --> 00:13:22.920 align:start position:0% okay take it over all right great thank 00:13:22.920 --> 00:13:25.350 align:start position:0% okay take it over all right great thank you 00:13:25.350 --> 00:13:25.360 align:start position:0% you 00:13:25.360 --> 00:13:28.949 align:start position:0% you um<00:13:26.360> okay<00:13:27.240> so<00:13:27.920> the<00:13:28.079> first<00:13:28.320> thing<00:13:28.480> we<00:13:28.600> wanted<00:13:28.839> to 00:13:28.949 --> 00:13:28.959 align:start position:0% um okay so the first thing we wanted to 00:13:28.959 --> 00:13:32.710 align:start position:0% um okay so the first thing we wanted to do<00:13:29.160> do<00:13:29.959> was<00:13:30.399> we<00:13:30.519> wanted<00:13:30.959> to<00:13:31.880> not<00:13:32.199> introduce 00:13:32.710 --> 00:13:32.720 align:start position:0% do do was we wanted to not introduce 00:13:32.720 --> 00:13:36.150 align:start position:0% do do was we wanted to not introduce centralization<00:13:33.920> again<00:13:34.920> and<00:13:35.680> the<00:13:35.800> way<00:13:35.959> we 00:13:36.150 --> 00:13:36.160 align:start position:0% centralization again and the way we 00:13:36.160 --> 00:13:40.030 align:start position:0% centralization again and the way we wanted<00:13:37.160> the<00:13:37.920> um<00:13:38.199> the<00:13:38.360> idea<00:13:38.720> here<00:13:38.880> is<00:13:39.120> that<00:13:39.920> if 00:13:40.030 --> 00:13:40.040 align:start position:0% wanted the um the idea here is that if 00:13:40.040 --> 00:13:41.590 align:start position:0% wanted the um the idea here is that if we<00:13:40.160> wanted<00:13:40.480> to<00:13:40.680> do<00:13:41.000> to<00:13:41.160> introduce 00:13:41.590 --> 00:13:41.600 align:start position:0% we wanted to do to introduce 00:13:41.600 --> 00:13:43.509 align:start position:0% we wanted to do to introduce centralization<00:13:42.600> we<00:13:42.720> wouldn't<00:13:43.040> have<00:13:43.160> built<00:13:43.399> it 00:13:43.509 --> 00:13:43.519 align:start position:0% centralization we wouldn't have built it 00:13:43.519 --> 00:13:45.990 align:start position:0% centralization we wouldn't have built it as<00:13:43.639> a<00:13:43.720> based<00:13:44.000> rollup<00:13:44.399> in<00:13:44.480> the<00:13:44.600> first<00:13:45.000> place 00:13:45.990 --> 00:13:46.000 align:start position:0% as a based rollup in the first place 00:13:46.000 --> 00:13:48.269 align:start position:0% as a based rollup in the first place then<00:13:47.000> how<00:13:47.120> are<00:13:47.240> we<00:13:47.360> going<00:13:47.480> to<00:13:47.639> solve<00:13:48.000> this 00:13:48.269 --> 00:13:48.279 align:start position:0% then how are we going to solve this 00:13:48.279 --> 00:13:51.110 align:start position:0% then how are we going to solve this complex<00:13:48.760> problem<00:13:49.600> so<00:13:50.040> let<00:13:50.160> me<00:13:50.360> explain<00:13:50.800> how 00:13:51.110 --> 00:13:51.120 align:start position:0% complex problem so let me explain how 00:13:51.120 --> 00:13:56.150 align:start position:0% complex problem so let me explain how gateways<00:13:52.000> work<00:13:53.279> first<00:13:54.360> so<00:13:55.360> gateways<00:13:55.920> are 00:13:56.150 --> 00:13:56.160 align:start position:0% gateways work first so gateways are 00:13:56.160 --> 00:13:59.069 align:start position:0% gateways work first so gateways are basically<00:13:56.759> centralized<00:13:57.639> servers<00:13:58.639> that 00:13:59.069 --> 00:13:59.079 align:start position:0% basically centralized servers that 00:13:59.079 --> 00:14:03.069 align:start position:0% basically centralized servers that expose<00:13:59.360> an<00:13:59.519> RPC<00:14:00.160> for<00:14:00.440> the<00:14:00.600> user<00:14:01.320> to<00:14:01.480> be<00:14:01.720> able<00:14:02.440> to 00:14:03.069 --> 00:14:03.079 align:start position:0% expose an RPC for the user to be able to 00:14:03.079 --> 00:14:05.870 align:start position:0% expose an RPC for the user to be able to provide<00:14:03.399> them<00:14:03.560> the<00:14:03.759> precom<00:14:04.639> they<00:14:05.160> the<00:14:05.800> the 00:14:05.870 --> 00:14:05.880 align:start position:0% provide them the precom they the the 00:14:05.880 --> 00:14:08.509 align:start position:0% provide them the precom they the the user<00:14:06.160> sends<00:14:06.519> the<00:14:06.639> transaction<00:14:07.160> to<00:14:07.279> the<00:14:07.519> RPC 00:14:08.509 --> 00:14:08.519 align:start position:0% user sends the transaction to the RPC 00:14:08.519 --> 00:14:13.269 align:start position:0% user sends the transaction to the RPC and<00:14:08.920> then<00:14:09.920> it<00:14:10.560> selects<00:14:11.320> which<00:14:12.320> uh<00:14:12.680> which<00:14:13.120> uh 00:14:13.269 --> 00:14:13.279 align:start position:0% and then it selects which uh which uh 00:14:13.279 --> 00:14:16.470 align:start position:0% and then it selects which uh which uh transactions<00:14:13.880> wants<00:14:14.120> to<00:14:14.279> precom<00:14:15.199> and<00:14:15.399> then<00:14:16.040> it 00:14:16.470 --> 00:14:16.480 align:start position:0% transactions wants to precom and then it 00:14:16.480 --> 00:14:19.430 align:start position:0% transactions wants to precom and then it it<00:14:16.639> provides<00:14:17.040> it<00:14:17.279> to<00:14:18.279> uh<00:14:18.600> it<00:14:18.759> proposes<00:14:19.279> that 00:14:19.430 --> 00:14:19.440 align:start position:0% it provides it to uh it proposes that 00:14:19.440 --> 00:14:20.790 align:start position:0% it provides it to uh it proposes that block<00:14:19.800> to 00:14:20.790 --> 00:14:20.800 align:start position:0% block to 00:14:20.800 --> 00:14:23.670 align:start position:0% block to L1<00:14:21.800> of<00:14:21.959> course<00:14:22.440> the<00:14:22.720> confirmation<00:14:23.279> receipt 00:14:23.670 --> 00:14:23.680 align:start position:0% L1 of course the confirmation receipt 00:14:23.680 --> 00:14:27.430 align:start position:0% L1 of course the confirmation receipt that<00:14:23.839> goes<00:14:24.000> to<00:14:24.160> the<00:14:24.560> user<00:14:25.560> is<00:14:25.759> given<00:14:26.360> like<00:14:26.680> in<00:14:27.279> a 00:14:27.430 --> 00:14:27.440 align:start position:0% that goes to the user is given like in a 00:14:27.440 --> 00:14:30.350 align:start position:0% that goes to the user is given like in a matter<00:14:27.800> of<00:14:28.040> milliseconds<00:14:29.160> between<00:14:29.680> 100<00:14:30.000> and 00:14:30.350 --> 00:14:30.360 align:start position:0% matter of milliseconds between 100 and 00:14:30.360 --> 00:14:32.870 align:start position:0% matter of milliseconds between 100 and 200<00:14:30.639> milliseconds<00:14:31.440> which<00:14:31.600> is<00:14:31.800> very<00:14:32.079> fast<00:14:32.759> of 00:14:32.870 --> 00:14:32.880 align:start position:0% 200 milliseconds which is very fast of 00:14:32.880 --> 00:14:35.550 align:start position:0% 200 milliseconds which is very fast of course<00:14:33.079> the<00:14:33.240> ux<00:14:33.959> is<00:14:34.120> very<00:14:34.360> cool<00:14:35.079> but<00:14:35.279> the 00:14:35.550 --> 00:14:35.560 align:start position:0% course the ux is very cool but the 00:14:35.560 --> 00:14:39.350 align:start position:0% course the ux is very cool but the compromise<00:14:36.560> is<00:14:37.279> very 00:14:39.350 --> 00:14:39.360 align:start position:0% compromise is very 00:14:39.360 --> 00:14:44.269 align:start position:0% compromise is very high<00:14:40.360> now<00:14:40.720> also<00:14:41.720> like<00:14:42.480> there<00:14:42.600> is<00:14:42.920> a<00:14:43.920> another 00:14:44.269 --> 00:14:44.279 align:start position:0% high now also like there is a another 00:14:44.279 --> 00:14:46.189 align:start position:0% high now also like there is a another concept<00:14:44.720> here<00:14:44.920> in<00:14:45.160> pre-confirmation<00:14:45.600> that<00:14:46.000> is 00:14:46.189 --> 00:14:46.199 align:start position:0% concept here in pre-confirmation that is 00:14:46.199 --> 00:14:48.990 align:start position:0% concept here in pre-confirmation that is important<00:14:46.959> which<00:14:47.120> is<00:14:47.759> not<00:14:48.000> all<00:14:48.240> validator<00:14:48.839> has 00:14:48.990 --> 00:14:49.000 align:start position:0% important which is not all validator has 00:14:49.000 --> 00:14:50.629 align:start position:0% important which is not all validator has signed<00:14:49.279> up<00:14:49.440> to<00:14:49.600> become<00:14:49.880> pre- 00:14:50.629 --> 00:14:50.639 align:start position:0% signed up to become pre- 00:14:50.639 --> 00:14:53.470 align:start position:0% signed up to become pre- confirms<00:14:51.639> and<00:14:51.800> because<00:14:52.040> of<00:14:52.279> this<00:14:53.079> you 00:14:53.470 --> 00:14:53.480 align:start position:0% confirms and because of this you 00:14:53.480 --> 00:14:56.350 align:start position:0% confirms and because of this you sometimes<00:14:53.880> have<00:14:54.480> some<00:14:54.720> validators<00:14:55.360> who<00:14:55.600> have 00:14:56.350 --> 00:14:56.360 align:start position:0% sometimes have some validators who have 00:14:56.360 --> 00:14:58.389 align:start position:0% sometimes have some validators who have uh<00:14:56.480> decided<00:14:56.880> to<00:14:57.079> register<00:14:57.639> as<00:14:57.720> a<00:14:57.839> pre-<00:14:58.079> comfor 00:14:58.389 --> 00:14:58.399 align:start position:0% uh decided to register as a pre- comfor 00:14:58.399 --> 00:15:00.870 align:start position:0% uh decided to register as a pre- comfor and<00:14:58.519> some<00:14:58.720> others<00:14:59.279> that<00:14:59.519> haven't<00:14:59.880> registered 00:15:00.870 --> 00:15:00.880 align:start position:0% and some others that haven't registered 00:15:00.880 --> 00:15:02.470 align:start position:0% and some others that haven't registered so<00:15:01.120> the<00:15:01.320> Gateway<00:15:01.959> can<00:15:02.199> provide 00:15:02.470 --> 00:15:02.480 align:start position:0% so the Gateway can provide 00:15:02.480 --> 00:15:04.990 align:start position:0% so the Gateway can provide pre-confirmation<00:15:02.920> for<00:15:03.360> users<00:15:04.240> and<00:15:04.519> it<00:15:04.639> should 00:15:04.990 --> 00:15:05.000 align:start position:0% pre-confirmation for users and it should 00:15:05.000 --> 00:15:07.069 align:start position:0% pre-confirmation for users and it should it<00:15:05.160> could<00:15:05.480> it<00:15:05.639> not<00:15:05.880> necessarily<00:15:06.360> will<00:15:06.560> push<00:15:06.839> a 00:15:07.069 --> 00:15:07.079 align:start position:0% it could it not necessarily will push a 00:15:07.079 --> 00:15:09.749 align:start position:0% it could it not necessarily will push a block<00:15:07.880> uh<00:15:08.040> a<00:15:08.199> propose<00:15:08.480> a<00:15:08.639> block<00:15:08.880> for<00:15:09.040> the<00:15:09.120> L2<00:15:09.519> on 00:15:09.749 --> 00:15:09.759 align:start position:0% block uh a propose a block for the L2 on 00:15:09.759 --> 00:15:12.710 align:start position:0% block uh a propose a block for the L2 on this<00:15:09.920> slot<00:15:10.680> but<00:15:10.839> it<00:15:11.000> could<00:15:11.480> potentially<00:15:12.480> push 00:15:12.710 --> 00:15:12.720 align:start position:0% this slot but it could potentially push 00:15:12.720 --> 00:15:15.470 align:start position:0% this slot but it could potentially push it<00:15:13.279> here<00:15:14.279> and<00:15:14.399> the<00:15:14.519> way<00:15:14.639> to<00:15:14.759> do<00:15:15.040> this<00:15:15.199> will<00:15:15.320> be 00:15:15.470 --> 00:15:15.480 align:start position:0% it here and the way to do this will be 00:15:15.480 --> 00:15:17.310 align:start position:0% it here and the way to do this will be explained<00:15:15.839> in<00:15:15.920> a<00:15:16.040> later<00:15:16.399> stage<00:15:16.759> when<00:15:16.880> we<00:15:17.040> talk 00:15:17.310 --> 00:15:17.320 align:start position:0% explained in a later stage when we talk 00:15:17.320 --> 00:15:24.230 align:start position:0% explained in a later stage when we talk about<00:15:18.120> um<00:15:18.680> forc<00:15:19.079> inclusion 00:15:24.230 --> 00:15:24.240 align:start position:0% 00:15:24.240 --> 00:15:27.150 align:start position:0% lists<00:15:25.240> all<00:15:25.399> right<00:15:26.240> the<00:15:26.399> other<00:15:26.680> thing<00:15:26.920> that<00:15:27.040> we 00:15:27.150 --> 00:15:27.160 align:start position:0% lists all right the other thing that we 00:15:27.160 --> 00:15:28.990 align:start position:0% lists all right the other thing that we wanted<00:15:27.440> to<00:15:27.639> focus<00:15:27.959> on<00:15:28.240> which<00:15:28.360> was<00:15:28.560> important 00:15:28.990 --> 00:15:29.000 align:start position:0% wanted to focus on which was important 00:15:29.000 --> 00:15:31.990 align:start position:0% wanted to focus on which was important for<00:15:29.199> us<00:15:29.440> is<00:15:29.680> that<00:15:30.160> we<00:15:30.319> wanted<00:15:30.600> to<00:15:30.759> use<00:15:31.120> the<00:15:31.639> the 00:15:31.990 --> 00:15:32.000 align:start position:0% for us is that we wanted to use the the 00:15:32.000 --> 00:15:34.509 align:start position:0% for us is that we wanted to use the the existing<00:15:33.000> transaction<00:15:33.680> structure<00:15:34.319> the 00:15:34.509 --> 00:15:34.519 align:start position:0% existing transaction structure the 00:15:34.519 --> 00:15:36.949 align:start position:0% existing transaction structure the existing<00:15:35.079> wallet<00:15:35.800> we<00:15:35.920> didn't<00:15:36.160> want<00:15:36.279> to<00:15:36.480> invent 00:15:36.949 --> 00:15:36.959 align:start position:0% existing wallet we didn't want to invent 00:15:36.959 --> 00:15:39.790 align:start position:0% existing wallet we didn't want to invent a<00:15:37.319> new<00:15:38.319> um<00:15:38.920> a 00:15:39.790 --> 00:15:39.800 align:start position:0% a new um a 00:15:39.800 --> 00:15:43.389 align:start position:0% a new um a new<00:15:40.800> a<00:15:40.959> new<00:15:41.360> like<00:15:41.800> complexity<00:15:42.519> to<00:15:42.759> the<00:15:43.000> to<00:15:43.160> the 00:15:43.389 --> 00:15:43.399 align:start position:0% new a new like complexity to the to the 00:15:43.399 --> 00:15:46.269 align:start position:0% new a new like complexity to the to the already<00:15:44.399> existing<00:15:45.360> situation<00:15:45.880> when<00:15:46.040> you<00:15:46.120> are 00:15:46.269 --> 00:15:46.279 align:start position:0% already existing situation when you are 00:15:46.279 --> 00:15:48.230 align:start position:0% already existing situation when you are sending<00:15:46.759> transactions<00:15:47.399> through 00:15:48.230 --> 00:15:48.240 align:start position:0% sending transactions through 00:15:48.240 --> 00:15:50.990 align:start position:0% sending transactions through wallets<00:15:49.240> um<00:15:49.440> so<00:15:49.759> some<00:15:50.000> suggestions<00:15:50.639> in<00:15:50.800> the 00:15:50.990 --> 00:15:51.000 align:start position:0% wallets um so some suggestions in the 00:15:51.000 --> 00:15:53.990 align:start position:0% wallets um so some suggestions in the precon<00:15:51.759> space<00:15:52.079> were<00:15:52.399> like<00:15:52.680> oh<00:15:53.319> we<00:15:53.480> should 00:15:53.990 --> 00:15:54.000 align:start position:0% precon space were like oh we should 00:15:54.000 --> 00:15:56.230 align:start position:0% precon space were like oh we should potentially<00:15:54.600> put<00:15:54.920> an<00:15:55.120> inclusion<00:15:55.560> precom<00:15:55.959> fee 00:15:56.230 --> 00:15:56.240 align:start position:0% potentially put an inclusion precom fee 00:15:56.240 --> 00:15:58.749 align:start position:0% potentially put an inclusion precom fee premium<00:15:57.000> so<00:15:57.440> like<00:15:58.160> what<00:15:58.279> are<00:15:58.399> you<00:15:58.560> going<00:15:58.639> to 00:15:58.749 --> 00:15:58.759 align:start position:0% premium so like what are you going to 00:15:58.759 --> 00:16:02.389 align:start position:0% premium so like what are you going to pay<00:15:59.000> P<00:15:59.160> the<00:15:59.279> promer<00:16:00.000> to<00:16:00.399> to<00:16:01.199> to<00:16:01.639> so<00:16:01.880> he<00:16:02.040> can 00:16:02.389 --> 00:16:02.399 align:start position:0% pay P the promer to to to so he can 00:16:02.399 --> 00:16:05.030 align:start position:0% pay P the promer to to to so he can provide<00:16:02.680> you<00:16:02.920> with<00:16:03.120> this<00:16:03.360> fast<00:16:03.720> service<00:16:04.720> or 00:16:05.030 --> 00:16:05.040 align:start position:0% provide you with this fast service or 00:16:05.040 --> 00:16:07.710 align:start position:0% provide you with this fast service or and<00:16:05.480> the<00:16:05.639> base<00:16:05.920> fee<00:16:06.199> per<00:16:06.440> gas<00:16:06.759> for<00:16:07.199> that<00:16:07.560> as 00:16:07.710 --> 00:16:07.720 align:start position:0% and the base fee per gas for that as 00:16:07.720 --> 00:16:11.150 align:start position:0% and the base fee per gas for that as well<00:16:08.600> or<00:16:08.920> for<00:16:09.160> example<00:16:09.680> an<00:16:09.839> execution<00:16:10.319> precom 00:16:11.150 --> 00:16:11.160 align:start position:0% well or for example an execution precom 00:16:11.160 --> 00:16:14.269 align:start position:0% well or for example an execution precom yeah<00:16:11.360> it's<00:16:12.199> it's<00:16:12.399> basically<00:16:13.000> very<00:16:13.240> similar<00:16:14.120> uh 00:16:14.269 --> 00:16:14.279 align:start position:0% yeah it's it's basically very similar uh 00:16:14.279 --> 00:16:16.710 align:start position:0% yeah it's it's basically very similar uh to<00:16:14.639> to<00:16:15.079> each<00:16:15.240> other<00:16:15.560> like<00:16:15.920> they're<00:16:16.120> all<00:16:16.480> like 00:16:16.710 --> 00:16:16.720 align:start position:0% to to each other like they're all like 00:16:16.720 --> 00:16:20.110 align:start position:0% to to each other like they're all like the<00:16:16.959> same<00:16:17.959> so<00:16:18.240> what<00:16:18.360> we<00:16:18.560> decided<00:16:19.040> is<00:16:19.399> no<00:16:19.959> we're 00:16:20.110 --> 00:16:20.120 align:start position:0% the same so what we decided is no we're 00:16:20.120 --> 00:16:21.990 align:start position:0% the same so what we decided is no we're going<00:16:20.240> to<00:16:20.399> choose<00:16:20.680> something<00:16:21.079> that<00:16:21.199> is<00:16:21.440> basic 00:16:21.990 --> 00:16:22.000 align:start position:0% going to choose something that is basic 00:16:22.000 --> 00:16:24.470 align:start position:0% going to choose something that is basic so<00:16:22.160> we're<00:16:22.319> going<00:16:22.440> to<00:16:22.600> choose<00:16:23.000> the<00:16:23.160> same<00:16:23.480> exact 00:16:24.470 --> 00:16:24.480 align:start position:0% so we're going to choose the same exact 00:16:24.480 --> 00:16:27.269 align:start position:0% so we're going to choose the same exact EIP<00:16:25.240> 1559<00:16:25.759> fields<00:16:26.360> which<00:16:26.480> is<00:16:26.720> the<00:16:26.880> priority 00:16:27.269 --> 00:16:27.279 align:start position:0% EIP 1559 fields which is the priority 00:16:27.279 --> 00:16:31.350 align:start position:0% EIP 1559 fields which is the priority fee<00:16:28.160> so<00:16:28.720> the<00:16:28.920> the<00:16:29.000> priority<00:16:29.360> fee<00:16:29.680> pays<00:16:30.040> for<00:16:31.040> the 00:16:31.350 --> 00:16:31.360 align:start position:0% fee so the the priority fee pays for the 00:16:31.360 --> 00:16:35.269 align:start position:0% fee so the the priority fee pays for the pre-confirmation<00:16:32.160> the<00:16:33.440> proposing<00:16:34.440> and<00:16:35.120> the 00:16:35.269 --> 00:16:35.279 align:start position:0% pre-confirmation the proposing and the 00:16:35.279 --> 00:16:38.350 align:start position:0% pre-confirmation the proposing and the approving<00:16:35.839> of<00:16:36.000> that<00:16:36.600> transaction<00:16:37.600> and<00:16:38.199> the 00:16:38.350 --> 00:16:38.360 align:start position:0% approving of that transaction and the 00:16:38.360 --> 00:16:40.870 align:start position:0% approving of that transaction and the user<00:16:38.680> does<00:16:38.839> not<00:16:39.079> have<00:16:39.199> to<00:16:39.360> worry<00:16:39.720> about<00:16:40.519> all<00:16:40.680> of 00:16:40.870 --> 00:16:40.880 align:start position:0% user does not have to worry about all of 00:16:40.880 --> 00:16:45.389 align:start position:0% user does not have to worry about all of these<00:16:41.160> complex<00:16:41.600> things<00:16:42.560> other 00:16:45.389 --> 00:16:45.399 align:start position:0% 00:16:45.399 --> 00:16:47.470 align:start position:0% things 00:16:47.470 --> 00:16:47.480 align:start position:0% things 00:16:47.480 --> 00:16:52.509 align:start position:0% things okay<00:16:48.480> it's<00:16:48.680> not 00:16:52.509 --> 00:16:52.519 align:start position:0% 00:16:52.519 --> 00:16:55.309 align:start position:0% moving 00:16:55.309 --> 00:16:55.319 align:start position:0% moving 00:16:55.319 --> 00:16:58.030 align:start position:0% moving okay<00:16:56.319> all<00:16:56.480> right<00:16:56.759> so<00:16:57.079> I'll<00:16:57.279> start<00:16:57.800> now 00:16:58.030 --> 00:16:58.040 align:start position:0% okay all right so I'll start now 00:16:58.040 --> 00:17:01.069 align:start position:0% okay all right so I'll start now explaining<00:16:58.519> what<00:16:58.680> we<00:16:59.000> we 00:17:01.069 --> 00:17:01.079 align:start position:0% explaining what we we 00:17:01.079 --> 00:17:02.670 align:start position:0% explaining what we we designed 00:17:02.670 --> 00:17:02.680 align:start position:0% designed 00:17:02.680 --> 00:17:08.189 align:start position:0% designed so<00:17:03.680> in<00:17:03.880> Tao<00:17:04.240> like<00:17:04.640> explained<00:17:05.640> we<00:17:05.880> have<00:17:07.000> the<00:17:08.000> in 00:17:08.189 --> 00:17:08.199 align:start position:0% so in Tao like explained we have the in 00:17:08.199 --> 00:17:12.429 align:start position:0% so in Tao like explained we have the in Tao<00:17:08.839> we<00:17:09.000> have<00:17:09.439> that<00:17:10.439> uh<00:17:10.559> Tao<00:17:11.160> client<00:17:12.160> and<00:17:12.280> we 00:17:12.429 --> 00:17:12.439 align:start position:0% Tao we have that uh Tao client and we 00:17:12.439 --> 00:17:14.110 align:start position:0% Tao we have that uh Tao client and we also<00:17:12.720> have<00:17:12.919> Tao 00:17:14.110 --> 00:17:14.120 align:start position:0% also have Tao 00:17:14.120 --> 00:17:17.230 align:start position:0% also have Tao G<00:17:15.120> in<00:17:15.319> Tao<00:17:15.720> also<00:17:15.959> we<00:17:16.160> have<00:17:16.520> before<00:17:16.880> these 00:17:17.230 --> 00:17:17.240 align:start position:0% G in Tao also we have before these 00:17:17.240 --> 00:17:18.669 align:start position:0% G in Tao also we have before these before<00:17:17.480> we<00:17:17.640> come<00:17:17.760> to<00:17:17.959> these<00:17:18.199> we<00:17:18.319> have<00:17:18.480> the 00:17:18.669 --> 00:17:18.679 align:start position:0% before we come to these we have the 00:17:18.679 --> 00:17:22.309 align:start position:0% before we come to these we have the contract<00:17:19.679> that<00:17:20.120> receives<00:17:20.360> the<00:17:20.559> block 00:17:22.309 --> 00:17:22.319 align:start position:0% contract that receives the block 00:17:22.319 --> 00:17:24.470 align:start position:0% contract that receives the block proposals 00:17:24.470 --> 00:17:24.480 align:start position:0% proposals 00:17:24.480 --> 00:17:29.630 align:start position:0% proposals and<00:17:25.480> so<00:17:25.799> so<00:17:26.000> what<00:17:26.160> we<00:17:26.360> did<00:17:27.120> is<00:17:27.959> we<00:17:28.160> added 00:17:29.630 --> 00:17:29.640 align:start position:0% and so so what we did is we added 00:17:29.640 --> 00:17:32.789 align:start position:0% and so so what we did is we added uh<00:17:30.600> something<00:17:30.960> we<00:17:31.120> call<00:17:31.280> a<00:17:31.400> pre-c<00:17:31.679> confing 00:17:32.789 --> 00:17:32.799 align:start position:0% uh something we call a pre-c confing 00:17:32.799 --> 00:17:37.630 align:start position:0% uh something we call a pre-c confing node<00:17:33.799> and<00:17:34.320> that<00:17:34.559> sits<00:17:35.799> between<00:17:36.799> uh<00:17:37.480> the 00:17:37.630 --> 00:17:37.640 align:start position:0% node and that sits between uh the 00:17:37.640 --> 00:17:40.430 align:start position:0% node and that sits between uh the proposal<00:17:38.039> and<00:17:38.200> the<00:17:38.360> contracts<00:17:39.280> and<00:17:39.400> we<00:17:39.600> added 00:17:40.430 --> 00:17:40.440 align:start position:0% proposal and the contracts and we added 00:17:40.440 --> 00:17:42.909 align:start position:0% proposal and the contracts and we added some<00:17:40.919> contracts<00:17:41.919> one<00:17:42.160> contract<00:17:42.600> is<00:17:42.760> the 00:17:42.909 --> 00:17:42.919 align:start position:0% some contracts one contract is the 00:17:42.919 --> 00:17:44.870 align:start position:0% some contracts one contract is the pre-confirmation<00:17:43.360> service<00:17:44.039> contract<00:17:44.640> that 00:17:44.870 --> 00:17:44.880 align:start position:0% pre-confirmation service contract that 00:17:44.880 --> 00:17:47.630 align:start position:0% pre-confirmation service contract that basically<00:17:45.720> receives<00:17:46.600> the<00:17:46.760> blocks<00:17:47.360> that<00:17:47.480> are 00:17:47.630 --> 00:17:47.640 align:start position:0% basically receives the blocks that are 00:17:47.640 --> 00:17:52.950 align:start position:0% basically receives the blocks that are coming<00:17:48.039> from<00:17:48.280> the<00:17:48.840> promer<00:17:49.840> and<00:17:50.400> also<00:17:51.400> um<00:17:52.039> we 00:17:52.950 --> 00:17:52.960 align:start position:0% coming from the promer and also um we 00:17:52.960 --> 00:17:56.710 align:start position:0% coming from the promer and also um we added<00:17:53.440> a<00:17:53.600> restake<00:17:54.360> a<00:17:54.600> reor<00:17:55.240> staking<00:17:55.720> contract 00:17:56.710 --> 00:17:56.720 align:start position:0% added a restake a reor staking contract 00:17:56.720 --> 00:17:59.390 align:start position:0% added a restake a reor staking contract that<00:17:56.880> will<00:17:57.360> basically<00:17:58.360> uh<00:17:58.480> allow 00:17:59.390 --> 00:17:59.400 align:start position:0% that will basically uh allow 00:17:59.400 --> 00:18:02.390 align:start position:0% that will basically uh allow the<00:18:00.039> proposers<00:18:01.039> to 00:18:02.390 --> 00:18:02.400 align:start position:0% the proposers to 00:18:02.400 --> 00:18:05.310 align:start position:0% the proposers to register<00:18:03.400> uh<00:18:03.880> as<00:18:04.000> a 00:18:05.310 --> 00:18:05.320 align:start position:0% register uh as a 00:18:05.320 --> 00:18:08.390 align:start position:0% register uh as a preon<00:18:06.320> and<00:18:06.480> by<00:18:06.679> this<00:18:07.000> these<00:18:07.400> proposers 00:18:08.390 --> 00:18:08.400 align:start position:0% preon and by this these proposers 00:18:08.400 --> 00:18:10.830 align:start position:0% preon and by this these proposers whichever<00:18:08.840> they<00:18:08.960> are<00:18:09.480> any<00:18:09.760> validator<00:18:10.640> can 00:18:10.830 --> 00:18:10.840 align:start position:0% whichever they are any validator can 00:18:10.840 --> 00:18:14.430 align:start position:0% whichever they are any validator can basically<00:18:11.440> just<00:18:11.960> run<00:18:12.960> this<00:18:13.400> set<00:18:13.640> of<00:18:13.880> software 00:18:14.430 --> 00:18:14.440 align:start position:0% basically just run this set of software 00:18:14.440 --> 00:18:17.190 align:start position:0% basically just run this set of software as<00:18:14.559> a<00:18:14.799> site<00:18:15.080> car<00:18:15.440> to<00:18:16.440> uh<00:18:16.640> whatever<00:18:17.000> they're 00:18:17.190 --> 00:18:17.200 align:start position:0% as a site car to uh whatever they're 00:18:17.200 --> 00:18:19.750 align:start position:0% as a site car to uh whatever they're running<00:18:17.520> for<00:18:17.720> the<00:18:17.880> validator<00:18:18.679> so<00:18:19.200> alongside 00:18:19.750 --> 00:18:19.760 align:start position:0% running for the validator so alongside 00:18:19.760 --> 00:18:23.070 align:start position:0% running for the validator so alongside L1<00:18:20.440> you're<00:18:20.679> just<00:18:20.840> running<00:18:21.679> these<00:18:22.000> three<00:18:22.919> uh 00:18:23.070 --> 00:18:23.080 align:start position:0% L1 you're just running these three uh 00:18:23.080 --> 00:18:26.390 align:start position:0% L1 you're just running these three uh basically<00:18:23.960> uh<00:18:24.080> these<00:18:24.320> three<00:18:24.960> um<00:18:25.720> Docker 00:18:26.390 --> 00:18:26.400 align:start position:0% basically uh these three um Docker 00:18:26.400 --> 00:18:29.230 align:start position:0% basically uh these three um Docker Docker<00:18:26.799> Docker<00:18:27.159> images<00:18:27.919> Docker<00:18:28.280> containers 00:18:29.230 --> 00:18:29.240 align:start position:0% Docker Docker images Docker containers 00:18:29.240 --> 00:18:32.789 align:start position:0% Docker Docker images Docker containers and<00:18:29.400> then<00:18:30.120> you<00:18:30.280> are<00:18:30.520> able<00:18:30.880> to<00:18:31.720> precom 00:18:32.789 --> 00:18:32.799 align:start position:0% and then you are able to precom 00:18:32.799 --> 00:18:38.510 align:start position:0% and then you are able to precom transactions<00:18:33.799> when<00:18:33.960> your<00:18:34.120> slot<00:18:34.440> is 00:18:38.510 --> 00:18:38.520 align:start position:0% 00:18:38.520 --> 00:18:41.549 align:start position:0% up<00:18:39.520> so<00:18:39.760> what<00:18:39.960> H<00:18:40.360> how<00:18:40.520> how<00:18:40.679> does<00:18:40.919> this<00:18:41.120> exactly 00:18:41.549 --> 00:18:41.559 align:start position:0% up so what H how how does this exactly 00:18:41.559 --> 00:18:44.909 align:start position:0% up so what H how how does this exactly work<00:18:41.840> so<00:18:42.000> we<00:18:42.120> have<00:18:42.280> a<00:18:42.480> loop<00:18:43.440> that<00:18:43.919> happens 00:18:44.909 --> 00:18:44.919 align:start position:0% work so we have a loop that happens 00:18:44.919 --> 00:18:47.789 align:start position:0% work so we have a loop that happens every<00:18:45.480> 3<00:18:45.799> second<00:18:46.440> when<00:18:46.799> when<00:18:47.240> when<00:18:47.559> when<00:18:47.679> you 00:18:47.789 --> 00:18:47.799 align:start position:0% every 3 second when when when when you 00:18:47.799 --> 00:18:50.310 align:start position:0% every 3 second when when when when you are<00:18:48.000> chosen<00:18:48.480> as<00:18:48.640> the<00:18:48.799> pre-c<00:18:49.039> comer<00:18:49.720> for<00:18:50.039> the 00:18:50.310 --> 00:18:50.320 align:start position:0% are chosen as the pre-c comer for the 00:18:50.320 --> 00:18:52.990 align:start position:0% are chosen as the pre-c comer for the upcoming<00:18:50.760> slot<00:18:51.640> what<00:18:51.840> happens<00:18:52.159> is<00:18:52.360> that<00:18:52.640> you 00:18:52.990 --> 00:18:53.000 align:start position:0% upcoming slot what happens is that you 00:18:53.000 --> 00:18:55.789 align:start position:0% upcoming slot what happens is that you as<00:18:53.120> a<00:18:53.720> pre<00:18:54.039> confing<00:18:54.360> node<00:18:55.080> will<00:18:55.280> Fitch<00:18:55.600> the 00:18:55.789 --> 00:18:55.799 align:start position:0% as a pre confing node will Fitch the 00:18:55.799 --> 00:18:58.149 align:start position:0% as a pre confing node will Fitch the transactions<00:18:56.400> every<00:18:56.640> 3<00:18:56.880> second<00:18:57.320> from<00:18:57.600> the<00:18:57.760> tyo 00:18:58.149 --> 00:18:58.159 align:start position:0% transactions every 3 second from the tyo 00:18:58.159 --> 00:19:00.789 align:start position:0% transactions every 3 second from the tyo proposer<00:18:59.080> which<00:18:59.559> will<00:18:59.840> basically<00:19:00.200> fit<00:19:00.520> them 00:19:00.789 --> 00:19:00.799 align:start position:0% proposer which will basically fit them 00:19:00.799 --> 00:19:02.750 align:start position:0% proposer which will basically fit them from 00:19:02.750 --> 00:19:02.760 align:start position:0% from 00:19:02.760 --> 00:19:05.669 align:start position:0% from Tao<00:19:03.760> the<00:19:03.919> user<00:19:04.400> will<00:19:04.679> have<00:19:04.880> sent<00:19:05.440> this 00:19:05.669 --> 00:19:05.679 align:start position:0% Tao the user will have sent this 00:19:05.679 --> 00:19:08.070 align:start position:0% Tao the user will have sent this transaction<00:19:06.159> to<00:19:06.320> the<00:19:06.440> mle<00:19:07.000> so<00:19:07.159> there<00:19:07.280> is<00:19:07.440> no 00:19:08.070 --> 00:19:08.080 align:start position:0% transaction to the mle so there is no 00:19:08.080 --> 00:19:10.110 align:start position:0% transaction to the mle so there is no centralizing<00:19:09.080> aspect<00:19:09.480> here<00:19:09.720> you<00:19:09.799> don't<00:19:10.000> have 00:19:10.110 --> 00:19:10.120 align:start position:0% centralizing aspect here you don't have 00:19:10.120 --> 00:19:13.870 align:start position:0% centralizing aspect here you don't have to<00:19:10.280> connect<00:19:10.559> to<00:19:10.679> a<00:19:10.880> specific<00:19:11.720> AO<00:19:12.720> to<00:19:12.840> send<00:19:13.080> that 00:19:13.870 --> 00:19:13.880 align:start position:0% to connect to a specific AO to send that 00:19:13.880 --> 00:19:17.230 align:start position:0% to connect to a specific AO to send that transaction<00:19:14.880> and<00:19:15.799> every<00:19:16.039> 3<00:19:16.320> second<00:19:17.080> the 00:19:17.230 --> 00:19:17.240 align:start position:0% transaction and every 3 second the 00:19:17.240 --> 00:19:20.590 align:start position:0% transaction and every 3 second the pre-con<00:19:17.640> fer<00:19:17.919> will<00:19:18.320> sign<00:19:19.320> this<00:19:19.679> trans<00:19:20.200> uh<00:19:20.360> this 00:19:20.590 --> 00:19:20.600 align:start position:0% pre-con fer will sign this trans uh this 00:19:20.600 --> 00:19:22.470 align:start position:0% pre-con fer will sign this trans uh this batch<00:19:21.080> of<00:19:21.320> transactions<00:19:22.000> that<00:19:22.159> it<00:19:22.320> has 00:19:22.470 --> 00:19:22.480 align:start position:0% batch of transactions that it has 00:19:22.480 --> 00:19:25.190 align:start position:0% batch of transactions that it has received<00:19:22.880> from<00:19:23.000> The<00:19:23.120> Tao<00:19:23.559> proposer<00:19:24.559> and<00:19:24.720> then 00:19:25.190 --> 00:19:25.200 align:start position:0% received from The Tao proposer and then 00:19:25.200 --> 00:19:27.470 align:start position:0% received from The Tao proposer and then broadcast<00:19:25.880> it<00:19:26.039> to<00:19:26.240> other<00:19:26.480> pre<00:19:26.720> confers 00:19:27.470 --> 00:19:27.480 align:start position:0% broadcast it to other pre confers 00:19:27.480 --> 00:19:32.870 align:start position:0% broadcast it to other pre confers through<00:19:27.679> P2P 00:19:32.870 --> 00:19:32.880 align:start position:0% 00:19:32.880 --> 00:19:37.350 align:start position:0% oops 00:19:37.350 --> 00:19:37.360 align:start position:0% 00:19:37.360 --> 00:19:43.029 align:start position:0% okay<00:19:38.640> um<00:19:39.640> okay<00:19:39.960> permission<00:19:40.760> okay<00:19:41.360> so<00:19:42.360> here<00:19:42.760> we 00:19:43.029 --> 00:19:43.039 align:start position:0% okay um okay permission okay so here we 00:19:43.039 --> 00:19:45.750 align:start position:0% okay um okay permission okay so here we we<00:19:43.320> we<00:19:43.640> we<00:19:43.840> we<00:19:43.960> look<00:19:44.240> at<00:19:44.799> okay<00:19:44.919> so<00:19:45.200> how<00:19:45.360> do<00:19:45.520> we 00:19:45.750 --> 00:19:45.760 align:start position:0% we we we we look at okay so how do we 00:19:45.760 --> 00:19:48.149 align:start position:0% we we we we look at okay so how do we choose<00:19:46.760> which<00:19:47.039> of<00:19:47.200> the<00:19:47.360> registered<00:19:47.840> prec 00:19:48.149 --> 00:19:48.159 align:start position:0% choose which of the registered prec 00:19:48.159 --> 00:19:52.070 align:start position:0% choose which of the registered prec confers<00:19:49.159> are<00:19:49.360> going<00:19:49.480> to<00:19:49.679> be<00:19:50.080> used<00:19:50.960> or<00:19:51.640> have<00:19:51.840> the 00:19:52.070 --> 00:19:52.080 align:start position:0% confers are going to be used or have the 00:19:52.080 --> 00:19:54.430 align:start position:0% confers are going to be used or have the right<00:19:52.320> to<00:19:52.520> propose<00:19:53.200> these 00:19:54.430 --> 00:19:54.440 align:start position:0% right to propose these 00:19:54.440 --> 00:19:58.230 align:start position:0% right to propose these blocks<00:19:55.440> and<00:19:55.640> this<00:19:55.720> is<00:19:56.000> when<00:19:57.000> we<00:19:57.440> use<00:19:57.880> the<00:19:58.039> look 00:19:58.230 --> 00:19:58.240 align:start position:0% blocks and this is when we use the look 00:19:58.240 --> 00:20:01.310 align:start position:0% blocks and this is when we use the look ahead<00:19:58.960> that<00:19:59.080> is<00:19:59.280> provided<00:19:59.760> by<00:20:00.000> the<00:20:00.440> consensus 00:20:01.310 --> 00:20:01.320 align:start position:0% ahead that is provided by the consensus 00:20:01.320 --> 00:20:07.230 align:start position:0% ahead that is provided by the consensus layer<00:20:02.320> to<00:20:02.520> know<00:20:03.480> which<00:20:04.400> exactly<00:20:05.400> uh<00:20:05.679> is<00:20:06.000> the 00:20:07.230 --> 00:20:07.240 align:start position:0% layer to know which exactly uh is the 00:20:07.240 --> 00:20:10.789 align:start position:0% layer to know which exactly uh is the proposer<00:20:08.240> that<00:20:08.600> has<00:20:09.120> been<00:20:09.520> registered<00:20:10.520> in<00:20:10.679> the 00:20:10.789 --> 00:20:10.799 align:start position:0% proposer that has been registered in the 00:20:10.799 --> 00:20:15.270 align:start position:0% proposer that has been registered in the upcoming<00:20:11.559> 6<00:20:12.200> uh<00:20:12.640> 64<00:20:13.640> uh<00:20:13.760> or<00:20:14.080> like<00:20:14.799> in<00:20:14.960> the<00:20:15.159> in 00:20:15.270 --> 00:20:15.280 align:start position:0% upcoming 6 uh 64 uh or like in the in 00:20:15.280 --> 00:20:18.070 align:start position:0% upcoming 6 uh 64 uh or like in the in this<00:20:15.480> Epoch<00:20:16.039> and<00:20:16.200> in<00:20:16.320> the<00:20:16.480> epoch<00:20:16.960> after<00:20:17.720> so<00:20:17.919> in 00:20:18.070 --> 00:20:18.080 align:start position:0% this Epoch and in the epoch after so in 00:20:18.080 --> 00:20:20.350 align:start position:0% this Epoch and in the epoch after so in consensus<00:20:18.520> layer<00:20:18.799> and<00:20:18.880> Beacon<00:20:19.200> chain<00:20:19.919> you<00:20:20.080> can 00:20:20.350 --> 00:20:20.360 align:start position:0% consensus layer and Beacon chain you can 00:20:20.360 --> 00:20:23.909 align:start position:0% consensus layer and Beacon chain you can query<00:20:20.760> the<00:20:20.880> CL<00:20:21.320> client<00:20:21.840> for<00:20:22.159> the<00:20:22.720> existing<00:20:23.720> uh 00:20:23.909 --> 00:20:23.919 align:start position:0% query the CL client for the existing uh 00:20:23.919 --> 00:20:26.789 align:start position:0% query the CL client for the existing uh Epoch<00:20:24.480> the<00:20:24.600> current<00:20:24.960> Epoch<00:20:25.760> which<00:20:26.320> which 00:20:26.789 --> 00:20:26.799 align:start position:0% Epoch the current Epoch which which 00:20:26.799 --> 00:20:29.149 align:start position:0% Epoch the current Epoch which which which<00:20:27.159> uh<00:20:27.320> which<00:20:27.559> proposer<00:20:28.200> which<00:20:28.640> validators 00:20:29.149 --> 00:20:29.159 align:start position:0% which uh which proposer which validators 00:20:29.159 --> 00:20:31.029 align:start position:0% which uh which proposer which validators have<00:20:29.280> the<00:20:29.400> right<00:20:29.559> to<00:20:29.720> propose<00:20:30.480> and<00:20:30.640> for<00:20:30.880> the 00:20:31.029 --> 00:20:31.039 align:start position:0% have the right to propose and for the 00:20:31.039 --> 00:20:32.029 align:start position:0% have the right to propose and for the upcoming 00:20:32.029 --> 00:20:32.039 align:start position:0% upcoming 00:20:32.039 --> 00:20:35.190 align:start position:0% upcoming Epoch<00:20:33.039> um<00:20:33.320> so<00:20:33.480> it<00:20:33.640> provides<00:20:34.000> you<00:20:34.159> with<00:20:34.280> a<00:20:34.440> list 00:20:35.190 --> 00:20:35.200 align:start position:0% Epoch um so it provides you with a list 00:20:35.200 --> 00:20:39.029 align:start position:0% Epoch um so it provides you with a list 32<00:20:36.200> uh<00:20:36.320> long<00:20:36.720> list<00:20:37.400> of<00:20:38.080> after<00:20:38.320> you<00:20:38.480> specify<00:20:38.919> the 00:20:39.029 --> 00:20:39.039 align:start position:0% 32 uh long list of after you specify the 00:20:39.039 --> 00:20:43.110 align:start position:0% 32 uh long list of after you specify the epoch<00:20:39.480> that<00:20:39.600> you<00:20:39.960> want<00:20:40.960> and<00:20:41.600> so<00:20:41.840> basically<00:20:42.360> the 00:20:43.110 --> 00:20:43.120 align:start position:0% epoch that you want and so basically the 00:20:43.120 --> 00:20:44.950 align:start position:0% epoch that you want and so basically the what<00:20:43.240> we<00:20:43.400> did<00:20:43.640> is<00:20:43.840> that<00:20:44.000> we<00:20:44.120> made<00:20:44.320> the<00:20:44.440> pre 00:20:44.950 --> 00:20:44.960 align:start position:0% what we did is that we made the pre 00:20:44.960 --> 00:20:47.630 align:start position:0% what we did is that we made the pre precon<00:20:45.400> node<00:20:45.960> fix<00:20:46.360> this<00:20:46.520> list<00:20:46.919> from<00:20:47.120> the<00:20:47.240> CL 00:20:47.630 --> 00:20:47.640 align:start position:0% precon node fix this list from the CL 00:20:47.640 --> 00:20:49.630 align:start position:0% precon node fix this list from the CL client<00:20:48.480> and<00:20:48.679> push<00:20:48.919> it<00:20:49.320> to<00:20:49.480> the 00:20:49.630 --> 00:20:49.640 align:start position:0% client and push it to the 00:20:49.640 --> 00:20:51.230 align:start position:0% client and push it to the pre-confirmation 00:20:51.230 --> 00:20:51.240 align:start position:0% pre-confirmation 00:20:51.240 --> 00:20:54.510 align:start position:0% pre-confirmation service<00:20:52.240> and<00:20:52.400> this<00:20:52.640> way<00:20:53.480> we<00:20:53.600> know<00:20:53.880> for<00:20:54.039> example 00:20:54.510 --> 00:20:54.520 align:start position:0% service and this way we know for example 00:20:54.520 --> 00:20:55.950 align:start position:0% service and this way we know for example that<00:20:54.840> since<00:20:55.120> this<00:20:55.280> proposer<00:20:55.679> is<00:20:55.799> not 00:20:55.950 --> 00:20:55.960 align:start position:0% that since this proposer is not 00:20:55.960 --> 00:20:57.310 align:start position:0% that since this proposer is not registered<00:20:56.480> this<00:20:56.600> proposer<00:20:56.960> is<00:20:57.120> not 00:20:57.310 --> 00:20:57.320 align:start position:0% registered this proposer is not 00:20:57.320 --> 00:20:58.750 align:start position:0% registered this proposer is not registered<00:20:58.039> we<00:20:58.159> know<00:20:58.320> that<00:20:58.480> this<00:20:58.640> this 00:20:58.750 --> 00:20:58.760 align:start position:0% registered we know that this this 00:20:58.760 --> 00:21:01.390 align:start position:0% registered we know that this this proposal<00:20:59.080> is<00:20:59.240> registered<00:20:59.720> so<00:21:00.440> then<00:21:00.880> we<00:21:01.039> choose 00:21:01.390 --> 00:21:01.400 align:start position:0% proposal is registered so then we choose 00:21:01.400 --> 00:21:04.590 align:start position:0% proposal is registered so then we choose this<00:21:01.600> proposal<00:21:02.120> to<00:21:03.120> uh<00:21:03.360> be<00:21:03.640> the<00:21:03.799> one<00:21:04.080> who<00:21:04.400> is 00:21:04.590 --> 00:21:04.600 align:start position:0% this proposal to uh be the one who is 00:21:04.600 --> 00:21:10.190 align:start position:0% this proposal to uh be the one who is precc<00:21:04.919> coming<00:21:05.360> those 00:21:10.190 --> 00:21:10.200 align:start position:0% 00:21:10.200 --> 00:21:12.630 align:start position:0% blocks<00:21:11.200> this<00:21:11.360> thing<00:21:11.559> doesn't<00:21:11.960> all<00:21:12.320> always 00:21:12.630 --> 00:21:12.640 align:start position:0% blocks this thing doesn't all always 00:21:12.640 --> 00:21:15.190 align:start position:0% blocks this thing doesn't all always work<00:21:13.120> let's<00:21:13.360> just 00:21:15.190 --> 00:21:15.200 align:start position:0% work let's just 00:21:15.200 --> 00:21:21.590 align:start position:0% work let's just okay<00:21:16.200> um<00:21:17.159> so<00:21:18.159> then<00:21:19.159> there<00:21:19.320> is<00:21:19.960> like<00:21:20.960> with<00:21:21.400> with 00:21:21.590 --> 00:21:21.600 align:start position:0% okay um so then there is like with with 00:21:21.600 --> 00:21:24.590 align:start position:0% okay um so then there is like with with any<00:21:21.919> system<00:21:22.400> you<00:21:22.640> have<00:21:22.760> to<00:21:22.960> have<00:21:23.279> incentive<00:21:24.240> to 00:21:24.590 --> 00:21:24.600 align:start position:0% any system you have to have incentive to 00:21:24.600 --> 00:21:29.430 align:start position:0% any system you have to have incentive to act<00:21:25.919> correctly<00:21:26.919> some<00:21:27.200> systems<00:21:27.640> depend<00:21:28.000> on<00:21:28.880> uh 00:21:29.430 --> 00:21:29.440 align:start position:0% act correctly some systems depend on uh 00:21:29.440 --> 00:21:33.070 align:start position:0% act correctly some systems depend on uh um<00:21:30.159> on<00:21:30.440> only<00:21:31.039> rewarding<00:21:32.039> uh<00:21:32.279> good<00:21:32.520> behavior 00:21:33.070 --> 00:21:33.080 align:start position:0% um on only rewarding uh good behavior 00:21:33.080 --> 00:21:36.470 align:start position:0% um on only rewarding uh good behavior some<00:21:33.279> systems<00:21:34.000> depend<00:21:34.480> on<00:21:35.480> uh<00:21:35.640> punishing<00:21:36.240> bad 00:21:36.470 --> 00:21:36.480 align:start position:0% some systems depend on uh punishing bad 00:21:36.480 --> 00:21:38.710 align:start position:0% some systems depend on uh punishing bad behavior<00:21:37.320> most<00:21:37.600> systems<00:21:38.120> or<00:21:38.320> a<00:21:38.400> lot<00:21:38.559> of 00:21:38.710 --> 00:21:38.720 align:start position:0% behavior most systems or a lot of 00:21:38.720 --> 00:21:42.310 align:start position:0% behavior most systems or a lot of systems<00:21:39.559> depend<00:21:39.919> on<00:21:40.279> doing<00:21:40.760> both<00:21:41.760> so<00:21:41.960> in<00:21:42.120> this 00:21:42.310 --> 00:21:42.320 align:start position:0% systems depend on doing both so in this 00:21:42.320 --> 00:21:43.950 align:start position:0% systems depend on doing both so in this case<00:21:42.760> the<00:21:42.919> preon<00:21:43.480> getes<00:21:43.799> that 00:21:43.950 --> 00:21:43.960 align:start position:0% case the preon getes that 00:21:43.960 --> 00:21:44.909 align:start position:0% case the preon getes that pre-confirmation 00:21:44.909 --> 00:21:44.919 align:start position:0% pre-confirmation 00:21:44.919 --> 00:21:47.549 align:start position:0% pre-confirmation fees<00:21:45.919> and<00:21:46.080> the<00:21:46.240> proposing 00:21:47.549 --> 00:21:47.559 align:start position:0% fees and the proposing 00:21:47.559 --> 00:21:52.510 align:start position:0% fees and the proposing fees<00:21:48.559> in<00:21:48.919> return<00:21:49.640> he<00:21:49.760> needs<00:21:50.120> to<00:21:50.840> precom<00:21:51.840> and 00:21:52.510 --> 00:21:52.520 align:start position:0% fees in return he needs to precom and 00:21:52.520 --> 00:21:54.430 align:start position:0% fees in return he needs to precom and provide<00:21:53.520> good 00:21:54.430 --> 00:21:54.440 align:start position:0% provide good 00:21:54.440 --> 00:21:57.110 align:start position:0% provide good information<00:21:55.440> uh<00:21:55.679> and<00:21:55.960> honor<00:21:56.880> the 00:21:57.110 --> 00:21:57.120 align:start position:0% information uh and honor the 00:21:57.120 --> 00:21:59.710 align:start position:0% information uh and honor the pre-confirmation<00:21:57.559> that<00:21:58.080> he<00:21:58.200> gave<00:21:58.400> to<00:21:58.640> the 00:21:59.710 --> 00:21:59.720 align:start position:0% pre-confirmation that he gave to the 00:21:59.720 --> 00:22:03.830 align:start position:0% pre-confirmation that he gave to the users<00:22:00.720> the<00:22:00.840> way<00:22:01.000> we<00:22:01.120> check<00:22:01.640> that<00:22:02.640> is<00:22:02.880> that<00:22:03.679> in 00:22:03.830 --> 00:22:03.840 align:start position:0% users the way we check that is that in 00:22:03.840 --> 00:22:06.830 align:start position:0% users the way we check that is that in the<00:22:04.279> case<00:22:05.279> the<00:22:05.440> pre-c<00:22:05.679> confer 00:22:06.830 --> 00:22:06.840 align:start position:0% the case the pre-c confer 00:22:06.840 --> 00:22:10.350 align:start position:0% the case the pre-c confer node<00:22:08.120> reveals<00:22:09.120> the<00:22:09.360> signed<00:22:09.880> malicious 00:22:10.350 --> 00:22:10.360 align:start position:0% node reveals the signed malicious 00:22:10.360 --> 00:22:12.950 align:start position:0% node reveals the signed malicious pre-confirmation<00:22:10.799> the<00:22:11.799> way<00:22:12.320> it's<00:22:12.520> done<00:22:12.760> is 00:22:12.950 --> 00:22:12.960 align:start position:0% pre-confirmation the way it's done is 00:22:12.960 --> 00:22:16.630 align:start position:0% pre-confirmation the way it's done is that<00:22:13.840> so<00:22:14.360> let's<00:22:14.640> say<00:22:14.880> I<00:22:15.120> precom<00:22:15.600> a<00:22:15.720> batch<00:22:15.880> of 00:22:16.630 --> 00:22:16.640 align:start position:0% that so let's say I precom a batch of 00:22:16.640 --> 00:22:19.510 align:start position:0% that so let's say I precom a batch of transaction<00:22:17.640> and<00:22:18.360> then<00:22:18.640> I<00:22:18.720> didn't<00:22:19.080> end<00:22:19.279> up 00:22:19.510 --> 00:22:19.520 align:start position:0% transaction and then I didn't end up 00:22:19.520 --> 00:22:22.029 align:start position:0% transaction and then I didn't end up pushing<00:22:19.960> this<00:22:20.159> batch<00:22:20.400> of<00:22:20.559> transactions<00:22:21.400> on 00:22:22.029 --> 00:22:22.039 align:start position:0% pushing this batch of transactions on 00:22:22.039 --> 00:22:24.909 align:start position:0% pushing this batch of transactions on chain<00:22:23.039> but<00:22:23.440> I<00:22:23.559> have<00:22:23.720> already<00:22:24.080> broadcasted 00:22:24.909 --> 00:22:24.919 align:start position:0% chain but I have already broadcasted 00:22:24.919 --> 00:22:26.630 align:start position:0% chain but I have already broadcasted that<00:22:25.120> I<00:22:25.240> have<00:22:25.440> pre-comp<00:22:26.080> this<00:22:26.240> batch<00:22:26.480> of 00:22:26.630 --> 00:22:26.640 align:start position:0% that I have pre-comp this batch of 00:22:26.640 --> 00:22:29.269 align:start position:0% that I have pre-comp this batch of transaction<00:22:27.320> with<00:22:27.520> my<00:22:27.720> signature<00:22:28.960> so<00:22:29.159> what 00:22:29.269 --> 00:22:29.279 align:start position:0% transaction with my signature so what 00:22:29.279 --> 00:22:31.630 align:start position:0% transaction with my signature so what would<00:22:29.520> happen<00:22:29.840> is<00:22:30.440> another<00:22:30.840> promer<00:22:31.440> that<00:22:31.520> was 00:22:31.630 --> 00:22:31.640 align:start position:0% would happen is another promer that was 00:22:31.640 --> 00:22:35.070 align:start position:0% would happen is another promer that was listening<00:22:32.000> on<00:22:32.480> P2P<00:22:33.480> would<00:22:33.799> then<00:22:34.559> pick<00:22:34.840> this 00:22:35.070 --> 00:22:35.080 align:start position:0% listening on P2P would then pick this 00:22:35.080 --> 00:22:37.750 align:start position:0% listening on P2P would then pick this signature<00:22:35.720> with<00:22:36.159> uh<00:22:36.559> with<00:22:36.760> the<00:22:37.080> with<00:22:37.200> the 00:22:37.750 --> 00:22:37.760 align:start position:0% signature with uh with the with the 00:22:37.760 --> 00:22:41.110 align:start position:0% signature with uh with the with the batch<00:22:38.000> of<00:22:38.440> transactions<00:22:39.440> and<00:22:40.200> push<00:22:40.600> that<00:22:40.880> to 00:22:41.110 --> 00:22:41.120 align:start position:0% batch of transactions and push that to 00:22:41.120 --> 00:22:43.470 align:start position:0% batch of transactions and push that to the<00:22:41.320> pre-confirmation<00:22:41.720> service<00:22:42.480> contract 00:22:43.470 --> 00:22:43.480 align:start position:0% the pre-confirmation service contract 00:22:43.480 --> 00:22:45.070 align:start position:0% the pre-confirmation service contract the<00:22:43.600> pre-confirmation<00:22:44.039> service<00:22:44.679> contract 00:22:45.070 --> 00:22:45.080 align:start position:0% the pre-confirmation service contract 00:22:45.080 --> 00:22:48.510 align:start position:0% the pre-confirmation service contract would<00:22:45.320> check<00:22:46.279> if<00:22:46.960> this<00:22:47.400> is<00:22:47.559> a<00:22:47.760> valid<00:22:48.039> signature 00:22:48.510 --> 00:22:48.520 align:start position:0% would check if this is a valid signature 00:22:48.520 --> 00:22:50.909 align:start position:0% would check if this is a valid signature for<00:22:48.720> the<00:22:48.880> pre-c<00:22:49.159> confer<00:22:49.559> of<00:22:49.760> this<00:22:49.919> slot<00:22:50.600> and<00:22:50.760> if 00:22:50.909 --> 00:22:50.919 align:start position:0% for the pre-c confer of this slot and if 00:22:50.919 --> 00:22:51.549 align:start position:0% for the pre-c confer of this slot and if it 00:22:51.549 --> 00:22:51.559 align:start position:0% it 00:22:51.559 --> 00:22:56.310 align:start position:0% it is<00:22:52.559> then<00:22:52.799> it<00:22:52.960> will<00:22:53.840> go<00:22:54.200> and<00:22:55.120> ask<00:22:55.480> the<00:22:55.720> reaking 00:22:56.310 --> 00:22:56.320 align:start position:0% is then it will go and ask the reaking 00:22:56.320 --> 00:23:00.029 align:start position:0% is then it will go and ask the reaking or<00:22:56.480> staking<00:22:56.960> contract<00:22:57.400> to<00:22:57.640> slash<00:22:58.039> the<00:22:58.120> signup 00:23:00.029 --> 00:23:00.039 align:start position:0% or staking contract to slash the signup 00:23:00.039 --> 00:23:03.870 align:start position:0% or staking contract to slash the signup and<00:23:00.200> in<00:23:00.360> this<00:23:00.840> case<00:23:01.840> um<00:23:02.480> yeah<00:23:03.000> the<00:23:03.559> there<00:23:03.679> is 00:23:03.870 --> 00:23:03.880 align:start position:0% and in this case um yeah the there is 00:23:03.880 --> 00:23:06.630 align:start position:0% and in this case um yeah the there is also<00:23:04.159> the<00:23:04.279> slashing<00:23:04.760> for<00:23:05.039> the<00:23:05.360> incorrect<00:23:06.360> uh 00:23:06.630 --> 00:23:06.640 align:start position:0% also the slashing for the incorrect uh 00:23:06.640 --> 00:23:09.590 align:start position:0% also the slashing for the incorrect uh look<00:23:06.840> ahead<00:23:07.760> because<00:23:08.760> you<00:23:09.000> fish<00:23:09.320> the<00:23:09.400> look 00:23:09.590 --> 00:23:09.600 align:start position:0% look ahead because you fish the look 00:23:09.600 --> 00:23:11.710 align:start position:0% look ahead because you fish the look ahead<00:23:09.840> from<00:23:09.960> the<00:23:10.080> CL<00:23:10.600> but<00:23:10.840> how<00:23:11.000> does<00:23:11.200> the<00:23:11.320> El 00:23:11.710 --> 00:23:11.720 align:start position:0% ahead from the CL but how does the El 00:23:11.720 --> 00:23:15.070 align:start position:0% ahead from the CL but how does the El know<00:23:12.360> that<00:23:12.600> this<00:23:13.120> uh<00:23:13.200> look<00:23:13.400> ahead<00:23:13.679> is<00:23:14.080> correct 00:23:15.070 --> 00:23:15.080 align:start position:0% know that this uh look ahead is correct 00:23:15.080 --> 00:23:18.269 align:start position:0% know that this uh look ahead is correct there<00:23:15.240> is<00:23:15.840> you<00:23:15.960> can<00:23:16.360> use<00:23:17.360> um 00:23:18.269 --> 00:23:18.279 align:start position:0% there is you can use um 00:23:18.279 --> 00:23:21.990 align:start position:0% there is you can use um 4788<00:23:19.279> uh<00:23:19.400> EIP<00:23:20.240> uh<00:23:20.440> which<00:23:20.960> uh<00:23:21.480> basically 00:23:21.990 --> 00:23:22.000 align:start position:0% 4788 uh EIP uh which uh basically 00:23:22.000 --> 00:23:26.510 align:start position:0% 4788 uh EIP uh which uh basically provides<00:23:22.360> you<00:23:22.640> with<00:23:22.880> the<00:23:23.520> CL<00:23:24.080> Beacon<00:23:24.799> root<00:23:25.799> um 00:23:26.510 --> 00:23:26.520 align:start position:0% provides you with the CL Beacon root um 00:23:26.520 --> 00:23:28.950 align:start position:0% provides you with the CL Beacon root um and<00:23:26.799> using<00:23:27.200> that<00:23:27.400> you<00:23:27.520> can<00:23:27.720> push<00:23:27.960> a<00:23:28.120> proof 00:23:28.950 --> 00:23:28.960 align:start position:0% and using that you can push a proof 00:23:28.960 --> 00:23:31.950 align:start position:0% and using that you can push a proof if<00:23:29.159> the<00:23:29.320> look<00:23:29.520> ahead<00:23:29.840> is<00:23:30.039> incorrect<00:23:31.039> and<00:23:31.559> the 00:23:31.950 --> 00:23:31.960 align:start position:0% if the look ahead is incorrect and the 00:23:31.960 --> 00:23:33.710 align:start position:0% if the look ahead is incorrect and the prec<00:23:32.240> confer<00:23:32.559> who<00:23:32.679> sent<00:23:32.960> an<00:23:33.120> incorrect<00:23:33.559> look 00:23:33.710 --> 00:23:33.720 align:start position:0% prec confer who sent an incorrect look 00:23:33.720 --> 00:23:38.990 align:start position:0% prec confer who sent an incorrect look ahead<00:23:34.039> would<00:23:34.200> be 00:23:38.990 --> 00:23:39.000 align:start position:0% 00:23:39.000 --> 00:23:43.350 align:start position:0% slashed<00:23:40.000> okay<00:23:40.960> so<00:23:41.440> I<00:23:41.720> before<00:23:41.960> I<00:23:42.080> move<00:23:42.320> on<00:23:42.760> if<00:23:43.159> if 00:23:43.350 --> 00:23:43.360 align:start position:0% slashed okay so I before I move on if if 00:23:43.360 --> 00:23:46.190 align:start position:0% slashed okay so I before I move on if if you<00:23:43.559> guys<00:23:43.720> have<00:23:43.919> any<00:23:44.159> questions<00:23:45.080> it's<00:23:45.960> it's 00:23:46.190 --> 00:23:46.200 align:start position:0% you guys have any questions it's it's 00:23:46.200 --> 00:23:49.350 align:start position:0% you guys have any questions it's it's good<00:23:46.400> to<00:23:47.120> to<00:23:47.320> have<00:23:47.520> them<00:23:47.720> now<00:23:48.200> so<00:23:48.799> yeah<00:23:49.159> please 00:23:49.350 --> 00:23:49.360 align:start position:0% good to to have them now so yeah please 00:23:49.360 --> 00:23:51.950 align:start position:0% good to to have them now so yeah please go<00:23:49.480> ahead<00:23:50.000> I<00:23:50.080> have<00:23:50.200> two<00:23:50.559> questions<00:23:51.559> first<00:23:51.799> one 00:23:51.950 --> 00:23:51.960 align:start position:0% go ahead I have two questions first one 00:23:51.960 --> 00:23:55.630 align:start position:0% go ahead I have two questions first one is<00:23:52.559> based<00:23:52.840> on<00:23:53.400> I'm<00:23:53.520> not<00:23:53.679> familiar<00:23:54.039> with 00:23:55.630 --> 00:23:55.640 align:start position:0% is based on I'm not familiar with 00:23:55.640 --> 00:24:05.830 align:start position:0% is based on I'm not familiar with 478<00:23:56.640> not 00:24:05.830 --> 00:24:05.840 align:start position:0% 00:24:05.840 --> 00:24:09.870 align:start position:0% only<00:24:06.840> yeah<00:24:07.080> so<00:24:07.600> the<00:24:07.720> thing<00:24:07.960> about<00:24:08.559> 4788<00:24:09.559> is 00:24:09.870 --> 00:24:09.880 align:start position:0% only yeah so the thing about 4788 is 00:24:09.880 --> 00:24:12.190 align:start position:0% only yeah so the thing about 4788 is that<00:24:10.640> it<00:24:10.840> provides<00:24:11.240> you<00:24:11.440> with<00:24:11.600> the<00:24:11.799> beacon 00:24:12.190 --> 00:24:12.200 align:start position:0% that it provides you with the beacon 00:24:12.200 --> 00:24:15.029 align:start position:0% that it provides you with the beacon route<00:24:12.720> of<00:24:12.919> the<00:24:13.159> parent<00:24:13.640> block<00:24:14.440> and<00:24:14.600> not<00:24:14.840> the 00:24:15.029 --> 00:24:15.039 align:start position:0% route of the parent block and not the 00:24:15.039 --> 00:24:18.029 align:start position:0% route of the parent block and not the current<00:24:15.559> block<00:24:16.559> and<00:24:16.760> because<00:24:17.000> of<00:24:17.240> this<00:24:17.720> when 00:24:18.029 --> 00:24:18.039 align:start position:0% current block and because of this when 00:24:18.039 --> 00:24:21.390 align:start position:0% current block and because of this when the<00:24:18.200> look<00:24:18.440> ahead<00:24:18.880> is<00:24:19.159> pushed<00:24:20.159> I<00:24:20.320> cannot<00:24:21.200> in 00:24:21.390 --> 00:24:21.400 align:start position:0% the look ahead is pushed I cannot in 00:24:21.400 --> 00:24:25.070 align:start position:0% the look ahead is pushed I cannot in that<00:24:21.640> moment<00:24:22.080> verify<00:24:22.640> its<00:24:23.240> correctness<00:24:24.240> but 00:24:25.070 --> 00:24:25.080 align:start position:0% that moment verify its correctness but 00:24:25.080 --> 00:24:28.870 align:start position:0% that moment verify its correctness but after<00:24:25.399> one<00:24:25.600> single<00:24:26.080> block<00:24:27.080> I<00:24:27.240> can<00:24:28.480> with<00:24:28.720> the 00:24:28.870 --> 00:24:28.880 align:start position:0% after one single block I can with the 00:24:28.880 --> 00:24:31.230 align:start position:0% after one single block I can with the proof<00:24:29.679> using 00:24:31.230 --> 00:24:31.240 align:start position:0% proof using 00:24:31.240 --> 00:24:34.110 align:start position:0% proof using 4788<00:24:32.240> make<00:24:32.480> sure<00:24:32.880> that<00:24:33.240> if<00:24:33.360> it's<00:24:33.520> not<00:24:33.760> correct 00:24:34.110 --> 00:24:34.120 align:start position:0% 4788 make sure that if it's not correct 00:24:34.120 --> 00:24:36.789 align:start position:0% 4788 make sure that if it's not correct that<00:24:34.279> it<00:24:34.399> is<00:24:34.559> not<00:24:35.480> so<00:24:35.760> this<00:24:35.880> is<00:24:36.120> why<00:24:36.360> we<00:24:36.480> opted 00:24:36.789 --> 00:24:36.799 align:start position:0% that it is not so this is why we opted 00:24:36.799 --> 00:24:38.909 align:start position:0% that it is not so this is why we opted for<00:24:37.080> this<00:24:37.720> in<00:24:37.880> the<00:24:38.039> case<00:24:38.279> that<00:24:38.480> it<00:24:38.600> was 00:24:38.909 --> 00:24:38.919 align:start position:0% for this in the case that it was 00:24:38.919 --> 00:24:41.149 align:start position:0% for this in the case that it was possible<00:24:39.399> to<00:24:39.640> verify<00:24:40.520> we<00:24:40.640> would<00:24:40.799> have 00:24:41.149 --> 00:24:41.159 align:start position:0% possible to verify we would have 00:24:41.159 --> 00:24:44.990 align:start position:0% possible to verify we would have potentially<00:24:41.720> opted<00:24:42.600> for<00:24:43.600> um<00:24:44.480> pushing<00:24:44.840> the 00:24:44.990 --> 00:24:45.000 align:start position:0% potentially opted for um pushing the 00:24:45.000 --> 00:24:47.470 align:start position:0% potentially opted for um pushing the proof<00:24:45.520> with<00:24:45.720> the<00:24:45.840> look<00:24:46.039> ahead<00:24:46.960> the<00:24:47.159> problem 00:24:47.470 --> 00:24:47.480 align:start position:0% proof with the look ahead the problem 00:24:47.480 --> 00:24:50.269 align:start position:0% proof with the look ahead the problem with<00:24:47.760> that<00:24:48.200> normally<00:24:48.640> entails<00:24:49.440> that<00:24:50.120> you 00:24:50.269 --> 00:24:50.279 align:start position:0% with that normally entails that you 00:24:50.279 --> 00:24:52.350 align:start position:0% with that normally entails that you would<00:24:50.520> pay<00:24:50.760> more<00:24:51.320> because<00:24:51.600> the<00:24:51.760> proof<00:24:52.000> needs 00:24:52.350 --> 00:24:52.360 align:start position:0% would pay more because the proof needs 00:24:52.360 --> 00:24:53.710 align:start position:0% would pay more because the proof needs to<00:24:52.440> be<00:24:52.559> verified<00:24:53.000> on 00:24:53.710 --> 00:24:53.720 align:start position:0% to be verified on 00:24:53.720 --> 00:24:57.789 align:start position:0% to be verified on chain<00:24:54.720> in<00:24:55.120> every<00:24:55.600> single<00:24:56.320> submission<00:24:57.320> whereas 00:24:57.789 --> 00:24:57.799 align:start position:0% chain in every single submission whereas 00:24:57.799 --> 00:25:00.590 align:start position:0% chain in every single submission whereas if<00:24:57.919> you<00:24:58.039> do<00:24:58.480> it<00:24:58.640> in<00:24:58.760> a<00:24:59.000> fraud<00:24:59.440> prooof<00:24:59.760> manner 00:25:00.590 --> 00:25:00.600 align:start position:0% if you do it in a fraud prooof manner 00:25:00.600 --> 00:25:03.070 align:start position:0% if you do it in a fraud prooof manner only<00:25:00.960> when<00:25:01.200> someone<00:25:01.440> is<00:25:01.640> acting<00:25:02.080> maliciously 00:25:03.070 --> 00:25:03.080 align:start position:0% only when someone is acting maliciously 00:25:03.080 --> 00:25:05.070 align:start position:0% only when someone is acting maliciously that<00:25:03.240> you<00:25:03.360> need<00:25:03.559> to<00:25:03.760> do<00:25:04.039> this<00:25:04.440> so<00:25:04.640> the<00:25:04.799> cost 00:25:05.070 --> 00:25:05.080 align:start position:0% that you need to do this so the cost 00:25:05.080 --> 00:25:07.149 align:start position:0% that you need to do this so the cost drops<00:25:05.679> dramatically<00:25:06.679> and<00:25:06.799> there<00:25:06.919> is 00:25:07.149 --> 00:25:07.159 align:start position:0% drops dramatically and there is 00:25:07.159 --> 00:25:09.630 align:start position:0% drops dramatically and there is precautions<00:25:07.799> to<00:25:08.039> this<00:25:08.360> so<00:25:09.159> whoever<00:25:09.480> is 00:25:09.630 --> 00:25:09.640 align:start position:0% precautions to this so whoever is 00:25:09.640 --> 00:25:11.510 align:start position:0% precautions to this so whoever is submitting<00:25:10.120> the<00:25:10.320> look<00:25:10.520> ahead<00:25:11.120> will<00:25:11.320> get 00:25:11.510 --> 00:25:11.520 align:start position:0% submitting the look ahead will get 00:25:11.520 --> 00:25:14.110 align:start position:0% submitting the look ahead will get rewarded<00:25:12.320> submitting<00:25:12.799> the<00:25:13.120> proof<00:25:13.480> the<00:25:13.760> fraud 00:25:14.110 --> 00:25:14.120 align:start position:0% rewarded submitting the proof the fraud 00:25:14.120 --> 00:25:15.710 align:start position:0% rewarded submitting the proof the fraud proof<00:25:14.399> for<00:25:14.559> the<00:25:14.720> look<00:25:14.880> ahead<00:25:15.360> will<00:25:15.559> get 00:25:15.710 --> 00:25:15.720 align:start position:0% proof for the look ahead will get 00:25:15.720 --> 00:25:19.149 align:start position:0% proof for the look ahead will get rewarded<00:25:16.200> for<00:25:16.520> this<00:25:17.520> uh<00:25:17.799> by<00:25:18.279> uh<00:25:18.399> the<00:25:18.520> slashing 00:25:19.149 --> 00:25:19.159 align:start position:0% rewarded for this uh by uh the slashing 00:25:19.159 --> 00:25:21.549 align:start position:0% rewarded for this uh by uh the slashing of<00:25:19.440> the<00:25:19.919> other 00:25:21.549 --> 00:25:21.559 align:start position:0% of the other 00:25:21.559 --> 00:25:25.070 align:start position:0% of the other promer<00:25:22.559> other<00:25:22.799> questions<00:25:23.640> yeah<00:25:24.080> yeah<00:25:24.640> you<00:25:24.840> go 00:25:25.070 --> 00:25:25.080 align:start position:0% promer other questions yeah yeah you go 00:25:25.080 --> 00:25:28.430 align:start position:0% promer other questions yeah yeah you go back<00:25:25.159> to<00:25:25.320> the<00:25:25.440> slide<00:25:25.919> where<00:25:26.919> was 00:25:28.430 --> 00:25:28.440 align:start position:0% back to the slide where was 00:25:28.440 --> 00:25:31.269 align:start position:0% back to the slide where was com<00:25:28.679> to<00:25:28.840> one<00:25:29.840> okay<00:25:30.240> uh<00:25:30.360> let<00:25:30.480> me<00:25:30.679> try<00:25:30.880> to<00:25:31.039> make 00:25:31.269 --> 00:25:31.279 align:start position:0% com to one okay uh let me try to make 00:25:31.279 --> 00:25:34.430 align:start position:0% com to one okay uh let me try to make this<00:25:31.480> work<00:25:31.919> somehow 00:25:34.430 --> 00:25:34.440 align:start position:0% this work somehow 00:25:34.440 --> 00:25:37.950 align:start position:0% this work somehow okay<00:25:35.440> work<00:25:35.799> please<00:25:36.120> Okay<00:25:36.399> no 00:25:37.950 --> 00:25:37.960 align:start position:0% okay work please Okay no 00:25:37.960 --> 00:25:41.710 align:start position:0% okay work please Okay no Okay<00:25:38.960> yeah<00:25:39.240> over<00:25:39.520> here<00:25:40.200> sure 00:25:41.710 --> 00:25:41.720 align:start position:0% Okay yeah over here sure 00:25:41.720 --> 00:25:44.230 align:start position:0% Okay yeah over here sure um<00:25:42.720> well<00:25:42.840> not<00:25:43.000> this<00:25:43.480> was<00:25:43.640> one<00:25:43.840> where<00:25:44.039> there<00:25:44.120> was 00:25:44.230 --> 00:25:44.240 align:start position:0% um well not this was one where there was 00:25:44.240 --> 00:25:46.110 align:start position:0% um well not this was one where there was a 00:25:46.110 --> 00:25:46.120 align:start position:0% a 00:25:46.120 --> 00:25:49.389 align:start position:0% a SL<00:25:47.120> I<00:25:47.200> was<00:25:47.360> wondering<00:25:48.279> um<00:25:48.480> I<00:25:48.559> mean<00:25:48.960> here<00:25:49.279> this 00:25:49.389 --> 00:25:49.399 align:start position:0% SL I was wondering um I mean here this 00:25:49.399 --> 00:25:51.750 align:start position:0% SL I was wondering um I mean here this one<00:25:49.600> is<00:25:49.760> not<00:25:49.960> opted<00:25:50.240> in<00:25:50.600> and<00:25:50.760> this<00:25:50.880> one<00:25:51.039> is<00:25:51.440> so 00:25:51.750 --> 00:25:51.760 align:start position:0% one is not opted in and this one is so 00:25:51.760 --> 00:25:55.269 align:start position:0% one is not opted in and this one is so for<00:25:52.399> example<00:25:53.399> if<00:25:53.679> I<00:25:54.080> take<00:25:54.520> confirmations<00:25:55.120> from 00:25:55.269 --> 00:25:55.279 align:start position:0% for example if I take confirmations from 00:25:55.279 --> 00:25:58.750 align:start position:0% for example if I take confirmations from someone<00:25:55.640> who<00:25:56.240> SLS 00:25:58.750 --> 00:25:58.760 align:start position:0% someone who SLS 00:25:58.760 --> 00:25:59.830 align:start position:0% someone who SLS reliable 00:25:59.830 --> 00:25:59.840 align:start position:0% reliable 00:25:59.840 --> 00:26:03.950 align:start position:0% reliable St<00:26:00.840> St<00:26:01.279> possi 00:26:03.950 --> 00:26:03.960 align:start position:0% St St possi 00:26:03.960 --> 00:26:08.149 align:start position:0% St St possi that<00:26:04.960> okay<00:26:06.120> so<00:26:07.120> this<00:26:07.240> is<00:26:07.600> probably<00:26:07.960> not 00:26:08.149 --> 00:26:08.159 align:start position:0% that okay so this is probably not 00:26:08.159 --> 00:26:09.669 align:start position:0% that okay so this is probably not mentioned<00:26:08.640> in<00:26:08.880> this 00:26:09.669 --> 00:26:09.679 align:start position:0% mentioned in this 00:26:09.679 --> 00:26:13.350 align:start position:0% mentioned in this presentation<00:26:10.679> which<00:26:10.880> is<00:26:11.640> uh<00:26:11.880> a<00:26:12.120> problem<00:26:12.559> but 00:26:13.350 --> 00:26:13.360 align:start position:0% presentation which is uh a problem but 00:26:13.360 --> 00:26:14.430 align:start position:0% presentation which is uh a problem but hey 00:26:14.430 --> 00:26:14.440 align:start position:0% hey 00:26:14.440 --> 00:26:19.029 align:start position:0% hey sorry<00:26:15.480> um<00:26:16.480> so<00:26:16.720> basically<00:26:17.399> what<00:26:17.720> based<00:26:18.200> rollups 00:26:19.029 --> 00:26:19.039 align:start position:0% sorry um so basically what based rollups 00:26:19.039 --> 00:26:22.389 align:start position:0% sorry um so basically what based rollups depend<00:26:20.039> on<00:26:20.799> giving<00:26:21.120> the<00:26:21.279> user<00:26:21.600> the<00:26:21.760> ability<00:26:22.159> to 00:26:22.389 --> 00:26:22.399 align:start position:0% depend on giving the user the ability to 00:26:22.399 --> 00:26:23.669 align:start position:0% depend on giving the user the ability to always<00:26:22.760> push 00:26:23.669 --> 00:26:23.679 align:start position:0% always push 00:26:23.679 --> 00:26:27.269 align:start position:0% always push transactions<00:26:24.679> on<00:26:24.880> the<00:26:25.039> L1<00:26:26.039> with<00:26:26.520> permission 00:26:27.269 --> 00:26:27.279 align:start position:0% transactions on the L1 with permission 00:26:27.279 --> 00:26:31.269 align:start position:0% transactions on the L1 with permission perm<00:26:27.799> permission<00:26:28.520> LLY<00:26:29.520> okay<00:26:30.360> and<00:26:30.720> that<00:26:30.880> means 00:26:31.269 --> 00:26:31.279 align:start position:0% perm permission LLY okay and that means 00:26:31.279 --> 00:26:33.230 align:start position:0% perm permission LLY okay and that means that<00:26:31.480> there<00:26:31.600> is<00:26:31.840> no<00:26:31.960> one<00:26:32.279> who<00:26:32.520> could<00:26:32.840> prevent 00:26:33.230 --> 00:26:33.240 align:start position:0% that there is no one who could prevent 00:26:33.240 --> 00:26:35.750 align:start position:0% that there is no one who could prevent the<00:26:33.399> user<00:26:34.240> from<00:26:34.480> pushing<00:26:34.799> a<00:26:34.960> transaction<00:26:35.600> that 00:26:35.750 --> 00:26:35.760 align:start position:0% the user from pushing a transaction that 00:26:35.760 --> 00:26:38.190 align:start position:0% the user from pushing a transaction that could<00:26:36.000> invalidate<00:26:37.000> future<00:26:37.480> transactions 00:26:38.190 --> 00:26:38.200 align:start position:0% could invalidate future transactions 00:26:38.200 --> 00:26:39.830 align:start position:0% could invalidate future transactions that<00:26:38.360> have<00:26:38.520> been<00:26:38.880> precom<00:26:39.440> that<00:26:39.559> will<00:26:39.679> be 00:26:39.830 --> 00:26:39.840 align:start position:0% that have been precom that will be 00:26:39.840 --> 00:26:43.430 align:start position:0% that have been precom that will be pushed<00:26:40.120> later<00:26:40.720> that<00:26:40.880> have<00:26:41.039> been<00:26:41.679> pre-comp<00:26:42.679> um 00:26:43.430 --> 00:26:43.440 align:start position:0% pushed later that have been pre-comp um 00:26:43.440 --> 00:26:46.950 align:start position:0% pushed later that have been pre-comp um and<00:26:44.080> this<00:26:44.320> leads<00:26:44.640> to<00:26:45.200> execution<00:26:45.760> precom<00:26:46.760> not 00:26:46.950 --> 00:26:46.960 align:start position:0% and this leads to execution precom not 00:26:46.960 --> 00:26:49.470 align:start position:0% and this leads to execution precom not being<00:26:47.240> able<00:26:47.480> to<00:26:47.600> be<00:26:47.919> provided<00:26:48.919> and<00:26:49.039> the<00:26:49.159> only 00:26:49.470 --> 00:26:49.480 align:start position:0% being able to be provided and the only 00:26:49.480 --> 00:26:52.350 align:start position:0% being able to be provided and the only solution<00:26:49.960> that<00:26:50.120> we<00:26:50.279> have<00:26:50.480> to<00:26:50.720> that<00:26:51.360> is<00:26:51.640> delayed 00:26:52.350 --> 00:26:52.360 align:start position:0% solution that we have to that is delayed 00:26:52.360 --> 00:26:55.789 align:start position:0% solution that we have to that is delayed inbox<00:26:53.360> so<00:26:54.000> pre<00:26:54.279> comers<00:26:54.880> are<00:26:55.080> able<00:26:55.320> to<00:26:55.480> push 00:26:55.789 --> 00:26:55.799 align:start position:0% inbox so pre comers are able to push 00:26:55.799 --> 00:26:57.710 align:start position:0% inbox so pre comers are able to push directly<00:26:56.159> to<00:26:56.320> the<00:26:56.480> Tao<00:26:56.840> smart<00:26:57.159> contract<00:26:57.559> to 00:26:57.710 --> 00:26:57.720 align:start position:0% directly to the Tao smart contract to 00:26:57.720 --> 00:27:00.510 align:start position:0% directly to the Tao smart contract to propose<00:26:58.000> block<00:26:58.240> blocks<00:26:59.120> whereas<00:27:00.120> normal 00:27:00.510 --> 00:27:00.520 align:start position:0% propose block blocks whereas normal 00:27:00.520 --> 00:27:02.510 align:start position:0% propose block blocks whereas normal users<00:27:01.000> who<00:27:01.200> don't<00:27:01.440> want<00:27:01.520> to<00:27:01.679> use<00:27:02.039> the<00:27:02.279> pre-c 00:27:02.510 --> 00:27:02.520 align:start position:0% users who don't want to use the pre-c 00:27:02.520 --> 00:27:04.590 align:start position:0% users who don't want to use the pre-c confing<00:27:02.919> system<00:27:03.320> that<00:27:03.480> is<00:27:03.640> built<00:27:04.159> and<00:27:04.320> want<00:27:04.440> to 00:27:04.590 --> 00:27:04.600 align:start position:0% confing system that is built and want to 00:27:04.600 --> 00:27:06.950 align:start position:0% confing system that is built and want to push<00:27:04.919> directly<00:27:05.480> to<00:27:05.720> avoid<00:27:06.080> potentially 00:27:06.950 --> 00:27:06.960 align:start position:0% push directly to avoid potentially 00:27:06.960 --> 00:27:09.950 align:start position:0% push directly to avoid potentially censorship<00:27:07.960> uh<00:27:08.360> uh<00:27:08.520> by<00:27:08.679> the<00:27:08.840> promer<00:27:09.720> even 00:27:09.950 --> 00:27:09.960 align:start position:0% censorship uh uh by the promer even 00:27:09.960 --> 00:27:11.710 align:start position:0% censorship uh uh by the promer even though<00:27:10.159> this<00:27:10.279> is<00:27:10.360> a<00:27:10.520> decentralized<00:27:11.159> solution 00:27:11.710 --> 00:27:11.720 align:start position:0% though this is a decentralized solution 00:27:11.720 --> 00:27:13.470 align:start position:0% though this is a decentralized solution it<00:27:11.880> could<00:27:12.120> potentially<00:27:12.559> have<00:27:12.760> some<00:27:12.960> type<00:27:13.120> of 00:27:13.470 --> 00:27:13.480 align:start position:0% it could potentially have some type of 00:27:13.480 --> 00:27:15.870 align:start position:0% it could potentially have some type of censorship<00:27:14.480> so<00:27:14.880> if<00:27:15.039> they<00:27:15.240> push<00:27:15.640> their 00:27:15.870 --> 00:27:15.880 align:start position:0% censorship so if they push their 00:27:15.880 --> 00:27:17.789 align:start position:0% censorship so if they push their transaction<00:27:16.360> to<00:27:16.559> this<00:27:16.720> delayed<00:27:17.120> inbox<00:27:17.640> what 00:27:17.789 --> 00:27:17.799 align:start position:0% transaction to this delayed inbox what 00:27:17.799 --> 00:27:19.470 align:start position:0% transaction to this delayed inbox what happens<00:27:18.120> is<00:27:18.279> that<00:27:18.480> we<00:27:18.679> wait<00:27:19.120> for<00:27:19.320> the 00:27:19.470 --> 00:27:19.480 align:start position:0% happens is that we wait for the 00:27:19.480 --> 00:27:22.310 align:start position:0% happens is that we wait for the pre-confirmation<00:27:19.960> to<00:27:20.760> land<00:27:21.760> and<00:27:21.919> then<00:27:22.080> we 00:27:22.310 --> 00:27:22.320 align:start position:0% pre-confirmation to land and then we 00:27:22.320 --> 00:27:25.230 align:start position:0% pre-confirmation to land and then we include<00:27:22.880> those<00:27:23.880> uh<00:27:24.200> transactions<00:27:24.880> that<00:27:25.080> have 00:27:25.230 --> 00:27:25.240 align:start position:0% include those uh transactions that have 00:27:25.240 --> 00:27:27.389 align:start position:0% include those uh transactions that have been<00:27:25.480> pushed<00:27:25.799> by<00:27:25.960> the<00:27:26.080> user<00:27:26.760> so<00:27:26.960> in<00:27:27.159> this 00:27:27.389 --> 00:27:27.399 align:start position:0% been pushed by the user so in this 00:27:27.399 --> 00:27:29.909 align:start position:0% been pushed by the user so in this instance<00:27:28.240> just<00:27:28.360> to<00:27:28.520> be<00:27:28.679> clear<00:27:29.480> uh<00:27:29.679> any 00:27:29.909 --> 00:27:29.919 align:start position:0% instance just to be clear uh any 00:27:29.919 --> 00:27:31.990 align:start position:0% instance just to be clear uh any transactions<00:27:30.520> that<00:27:30.720> come<00:27:31.000> in<00:27:31.200> this 00:27:31.990 --> 00:27:32.000 align:start position:0% transactions that come in this 00:27:32.000 --> 00:27:34.990 align:start position:0% transactions that come in this slot<00:27:33.000> uh<00:27:33.200> will<00:27:33.640> will<00:27:33.840> go<00:27:34.000> to<00:27:34.159> the<00:27:34.360> queue<00:27:34.840> and 00:27:34.990 --> 00:27:35.000 align:start position:0% slot uh will will go to the queue and 00:27:35.000 --> 00:27:37.070 align:start position:0% slot uh will will go to the queue and will<00:27:35.159> not<00:27:35.559> be<00:27:35.840> proposed<00:27:36.399> no<00:27:36.559> it<00:27:36.640> will<00:27:36.799> not<00:27:36.919> be 00:27:37.070 --> 00:27:37.080 align:start position:0% will not be proposed no it will not be 00:27:37.080 --> 00:27:39.389 align:start position:0% will not be proposed no it will not be denied<00:27:37.559> it<00:27:37.640> will<00:27:37.840> go<00:27:37.960> to<00:27:38.120> the<00:27:38.320> Q<00:27:38.679> yeah<00:27:38.840> delayed 00:27:39.389 --> 00:27:39.399 align:start position:0% denied it will go to the Q yeah delayed 00:27:39.399 --> 00:27:41.549 align:start position:0% denied it will go to the Q yeah delayed yes<00:27:39.760> it<00:27:39.880> will<00:27:40.039> be<00:27:40.159> delayed<00:27:40.519> till<00:27:40.799> after<00:27:41.159> the 00:27:41.549 --> 00:27:41.559 align:start position:0% yes it will be delayed till after the 00:27:41.559 --> 00:27:44.029 align:start position:0% yes it will be delayed till after the the<00:27:41.760> pre<00:27:42.000> confer<00:27:42.440> has<00:27:43.200> uh<00:27:43.360> pushed<00:27:43.880> his 00:27:44.029 --> 00:27:44.039 align:start position:0% the pre confer has uh pushed his 00:27:44.039 --> 00:27:45.750 align:start position:0% the pre confer has uh pushed his pre-confirmation<00:27:44.519> and<00:27:45.240> then<00:27:45.360> it<00:27:45.440> will<00:27:45.600> be 00:27:45.750 --> 00:27:45.760 align:start position:0% pre-confirmation and then it will be 00:27:45.760 --> 00:27:48.149 align:start position:0% pre-confirmation and then it will be included<00:27:46.440> what<00:27:46.559> if<00:27:46.760> my<00:27:46.919> preon<00:27:47.600> is<00:27:47.760> dependent 00:27:48.149 --> 00:27:48.159 align:start position:0% included what if my preon is dependent 00:27:48.159 --> 00:27:53.389 align:start position:0% included what if my preon is dependent on<00:27:48.720> one<00:27:48.960> state<00:27:49.279> which<00:27:49.399> is<00:27:49.640> like<00:27:50.120> really<00:27:50.399> nice 00:27:53.389 --> 00:27:53.399 align:start position:0% 00:27:53.399 --> 00:27:54.950 align:start position:0% component 00:27:54.950 --> 00:27:54.960 align:start position:0% component 00:27:54.960 --> 00:27:59.590 align:start position:0% component um<00:27:55.960> yeah<00:27:56.320> no<00:27:57.320> um<00:27:58.279> I<00:27:58.440> could<00:27:58.919> I<00:27:59.039> could<00:27:59.240> expect<00:27:59.480> the 00:27:59.590 --> 00:27:59.600 align:start position:0% um yeah no um I could I could expect the 00:27:59.600 --> 00:28:02.310 align:start position:0% um yeah no um I could I could expect the pre<00:27:59.799> conf<00:28:00.279> with<00:28:00.440> interacting<00:28:00.880> with 00:28:02.310 --> 00:28:02.320 align:start position:0% pre conf with interacting with 00:28:02.320 --> 00:28:05.509 align:start position:0% pre conf with interacting with L1<00:28:03.320> yes<00:28:03.519> so<00:28:03.679> if<00:28:03.880> we<00:28:04.360> engage<00:28:04.919> a<00:28:05.080> composability 00:28:05.509 --> 00:28:05.519 align:start position:0% L1 yes so if we engage a composability 00:28:05.519 --> 00:28:08.950 align:start position:0% L1 yes so if we engage a composability in<00:28:06.360> here<00:28:07.000> then<00:28:07.200> it<00:28:07.440> could<00:28:07.919> yes<00:28:08.240> any<00:28:08.559> state<00:28:08.799> any 00:28:08.950 --> 00:28:08.960 align:start position:0% in here then it could yes any state any 00:28:08.960 --> 00:28:12.070 align:start position:0% in here then it could yes any state any L1<00:28:09.320> State<00:28:09.600> change<00:28:10.080> could<00:28:10.360> potentially<00:28:11.080> affect 00:28:12.070 --> 00:28:12.080 align:start position:0% L1 State change could potentially affect 00:28:12.080 --> 00:28:14.590 align:start position:0% L1 State change could potentially affect uh<00:28:12.279> this<00:28:12.799> uh<00:28:12.919> L2<00:28:13.399> transaction<00:28:14.000> that<00:28:14.240> depends 00:28:14.590 --> 00:28:14.600 align:start position:0% uh this uh L2 transaction that depends 00:28:14.600 --> 00:28:17.710 align:start position:0% uh this uh L2 transaction that depends on<00:28:14.760> it<00:28:15.320> and<00:28:15.480> this<00:28:15.640> is<00:28:16.440> not<00:28:16.760> a<00:28:17.000> problem<00:28:17.399> that<00:28:17.559> the 00:28:17.710 --> 00:28:17.720 align:start position:0% on it and this is not a problem that the 00:28:17.720 --> 00:28:19.110 align:start position:0% on it and this is not a problem that the solution<00:28:18.080> is<00:28:18.200> trying<00:28:18.480> to<00:28:18.640> solve 00:28:19.110 --> 00:28:19.120 align:start position:0% solution is trying to solve 00:28:19.120 --> 00:28:22.310 align:start position:0% solution is trying to solve unfortunately<00:28:20.120> just<00:28:20.279> like<00:28:20.720> an<00:28:21.720> yeah<00:28:21.919> I<00:28:22.000> don't 00:28:22.310 --> 00:28:22.320 align:start position:0% unfortunately just like an yeah I don't 00:28:22.320 --> 00:28:25.789 align:start position:0% unfortunately just like an yeah I don't think<00:28:22.679> I<00:28:22.760> don't<00:28:23.000> think<00:28:23.360> like<00:28:24.039> um<00:28:24.320> as<00:28:24.440> of<00:28:24.799> now 00:28:25.789 --> 00:28:25.799 align:start position:0% think I don't think like um as of now 00:28:25.799 --> 00:28:28.669 align:start position:0% think I don't think like um as of now there<00:28:26.399> is<00:28:27.399> potentially<00:28:27.840> there's<00:28:28.240> some<00:28:28.399> people 00:28:28.669 --> 00:28:28.679 align:start position:0% there is potentially there's some people 00:28:28.679 --> 00:28:31.750 align:start position:0% there is potentially there's some people working<00:28:29.000> on<00:28:29.200> this<00:28:29.480> but<00:28:29.720> I'm<00:28:29.960> not<00:28:30.279> aware<00:28:30.679> of<00:28:31.200> any 00:28:31.750 --> 00:28:31.760 align:start position:0% working on this but I'm not aware of any 00:28:31.760 --> 00:28:33.549 align:start position:0% working on this but I'm not aware of any solution<00:28:32.200> to<00:28:32.440> this<00:28:32.640> particular<00:28:33.120> problem<00:28:33.480> this 00:28:33.549 --> 00:28:33.559 align:start position:0% solution to this particular problem this 00:28:33.559 --> 00:28:35.870 align:start position:0% solution to this particular problem this is<00:28:33.679> a<00:28:33.840> very<00:28:34.039> good<00:28:34.279> question<00:28:34.799> thank<00:28:34.960> you 00:28:35.870 --> 00:28:35.880 align:start position:0% is a very good question thank you 00:28:35.880 --> 00:28:45.029 align:start position:0% is a very good question thank you sir<00:28:36.880> any<00:28:37.200> other<00:28:37.600> questions<00:28:38.240> yeah<00:28:38.480> go 00:28:45.029 --> 00:28:45.039 align:start position:0% 00:28:45.039 --> 00:28:48.310 align:start position:0% ahead<00:28:46.039> yeah<00:28:46.360> so<00:28:47.159> I<00:28:47.360> think<00:28:47.799> this<00:28:47.960> might<00:28:48.159> be 00:28:48.310 --> 00:28:48.320 align:start position:0% ahead yeah so I think this might be 00:28:48.320 --> 00:28:50.070 align:start position:0% ahead yeah so I think this might be talked<00:28:48.640> about<00:28:48.840> in<00:28:48.960> a<00:28:49.080> later<00:28:49.399> stage<00:28:49.679> so<00:28:49.840> I'm<00:28:49.919> not 00:28:50.070 --> 00:28:50.080 align:start position:0% talked about in a later stage so I'm not 00:28:50.080 --> 00:28:52.909 align:start position:0% talked about in a later stage so I'm not going<00:28:50.159> to<00:28:50.320> touch<00:28:50.519> on<00:28:50.640> it<00:28:50.880> more<00:28:51.720> but<00:28:52.240> there<00:28:52.440> is<00:28:52.720> a 00:28:52.909 --> 00:28:52.919 align:start position:0% going to touch on it more but there is a 00:28:52.919 --> 00:28:56.230 align:start position:0% going to touch on it more but there is a way<00:28:53.440> for<00:28:54.279> choosing<00:28:54.679> a<00:28:54.840> random<00:28:55.200> pre-<00:28:55.480> Comer<00:28:56.080> in 00:28:56.230 --> 00:28:56.240 align:start position:0% way for choosing a random pre- Comer in 00:28:56.240 --> 00:28:58.630 align:start position:0% way for choosing a random pre- Comer in the<00:28:56.480> case<00:28:56.760> that<00:28:56.919> there<00:28:57.039> isn't<00:28:57.440> AE<00:28:58.240> Comer 00:28:58.630 --> 00:28:58.640 align:start position:0% the case that there isn't AE Comer 00:28:58.640 --> 00:29:02.509 align:start position:0% the case that there isn't AE Comer available<00:28:59.080> for<00:28:59.279> the<00:28:59.440> next<00:28:59.960> 64<00:29:00.960> uh<00:29:01.159> block 00:29:02.509 --> 00:29:02.519 align:start position:0% available for the next 64 uh block 00:29:02.519 --> 00:29:05.350 align:start position:0% available for the next 64 uh block slot<00:29:03.519> any<00:29:03.720> other 00:29:05.350 --> 00:29:05.360 align:start position:0% slot any other 00:29:05.360 --> 00:29:08.789 align:start position:0% slot any other questions<00:29:06.360> y<00:29:06.600> go<00:29:06.679> ahead<00:29:07.399> um<00:29:07.919> could<00:29:08.080> you<00:29:08.559> touch 00:29:08.789 --> 00:29:08.799 align:start position:0% questions y go ahead um could you touch 00:29:08.799 --> 00:29:12.669 align:start position:0% questions y go ahead um could you touch on<00:29:09.120> more<00:29:09.600> about<00:29:10.480> the<00:29:11.120> so<00:29:11.320> I'm<00:29:11.480> doing<00:29:11.840> PR 00:29:12.669 --> 00:29:12.679 align:start position:0% on more about the so I'm doing PR 00:29:12.679 --> 00:29:15.950 align:start position:0% on more about the so I'm doing PR Gateway<00:29:13.080> as<00:29:13.320> like<00:29:13.519> a<00:29:14.440> a<00:29:14.600> subset<00:29:14.960> of<00:29:15.039> the<00:29:15.200> P<00:29:15.640> lay 00:29:15.950 --> 00:29:15.960 align:start position:0% Gateway as like a a subset of the P lay 00:29:15.960 --> 00:29:19.830 align:start position:0% Gateway as like a a subset of the P lay that's<00:29:16.279> exclusive<00:29:16.760> for<00:29:17.080> pre<00:29:17.720> that's<00:29:17.840> how 00:29:19.830 --> 00:29:19.840 align:start position:0% that's exclusive for pre that's how 00:29:19.840 --> 00:29:22.509 align:start position:0% that's exclusive for pre that's how interact<00:29:20.840> this<00:29:21.480> immediately<00:29:22.080> sounds<00:29:22.279> like<00:29:22.360> a 00:29:22.509 --> 00:29:22.519 align:start position:0% interact this immediately sounds like a 00:29:22.519 --> 00:29:25.389 align:start position:0% interact this immediately sounds like a Loosely<00:29:22.880> coupled<00:29:23.240> system<00:29:23.519> to<00:29:23.720> me<00:29:24.200> off<00:29:24.360> the<00:29:24.559> bat 00:29:25.389 --> 00:29:25.399 align:start position:0% Loosely coupled system to me off the bat 00:29:25.399 --> 00:29:28.149 align:start position:0% Loosely coupled system to me off the bat do<00:29:25.519> you<00:29:25.679> feel<00:29:25.960> like<00:29:26.480> there's 00:29:28.149 --> 00:29:28.159 align:start position:0% do you feel like there's 00:29:28.159 --> 00:29:30.029 align:start position:0% do you feel like there's consensus<00:29:28.679> required<00:29:29.159> here<00:29:29.360> to<00:29:29.600> agree<00:29:29.840> on 00:29:30.029 --> 00:29:30.039 align:start position:0% consensus required here to agree on 00:29:30.039 --> 00:29:32.110 align:start position:0% consensus required here to agree on preon<00:29:30.840> state<00:29:31.159> like<00:29:31.279> what<00:29:31.440> happens<00:29:31.720> if<00:29:31.880> the 00:29:32.110 --> 00:29:32.120 align:start position:0% preon state like what happens if the 00:29:32.120 --> 00:29:34.669 align:start position:0% preon state like what happens if the propos<00:29:32.519> is<00:29:32.640> to<00:29:32.760> pull<00:29:32.960> back<00:29:33.120> to<00:29:33.279> another<00:29:34.279> like 00:29:34.669 --> 00:29:34.679 align:start position:0% propos is to pull back to another like 00:29:34.679 --> 00:29:36.549 align:start position:0% propos is to pull back to another like you<00:29:34.840> unpack<00:29:35.720> the 00:29:36.549 --> 00:29:36.559 align:start position:0% you unpack the 00:29:36.559 --> 00:29:38.389 align:start position:0% you unpack the gate<00:29:37.559> the 00:29:38.389 --> 00:29:38.399 align:start position:0% gate the 00:29:38.399 --> 00:29:41.909 align:start position:0% gate the Gateway<00:29:39.399> okay<00:29:40.039> so<00:29:40.440> the<00:29:40.640> Gateway<00:29:41.320> basically 00:29:41.909 --> 00:29:41.919 align:start position:0% Gateway okay so the Gateway basically 00:29:41.919 --> 00:29:45.549 align:start position:0% Gateway okay so the Gateway basically buys<00:29:42.640> the<00:29:42.880> right<00:29:43.399> from<00:29:43.679> the<00:29:44.279> proposers<00:29:45.279> that 00:29:45.549 --> 00:29:45.559 align:start position:0% buys the right from the proposers that 00:29:45.559 --> 00:29:48.789 align:start position:0% buys the right from the proposers that have<00:29:45.799> registered<00:29:46.480> at<00:29:46.760> P<00:29:47.039> confers<00:29:48.000> to<00:29:48.279> propose 00:29:48.789 --> 00:29:48.799 align:start position:0% have registered at P confers to propose 00:29:48.799 --> 00:29:49.990 align:start position:0% have registered at P confers to propose at<00:29:48.960> a<00:29:49.120> certain 00:29:49.990 --> 00:29:50.000 align:start position:0% at a certain 00:29:50.000 --> 00:29:53.630 align:start position:0% at a certain slot<00:29:51.000> do<00:29:51.120> I<00:29:51.240> even<00:29:51.519> agree<00:29:51.799> on<00:29:52.080> like<00:29:52.720> for 00:29:53.630 --> 00:29:53.640 align:start position:0% slot do I even agree on like for 00:29:53.640 --> 00:29:55.669 align:start position:0% slot do I even agree on like for example<00:29:54.640> us 00:29:55.669 --> 00:29:55.679 align:start position:0% example us 00:29:55.679 --> 00:29:58.950 align:start position:0% example us provide<00:29:56.679> um<00:29:57.159> I<00:29:57.279> don't<00:29:57.519> think<00:29:57.679> so<00:29:58.159> know<00:29:58.559> like 00:29:58.950 --> 00:29:58.960 align:start position:0% provide um I don't think so know like 00:29:58.960 --> 00:30:01.149 align:start position:0% provide um I don't think so know like they<00:29:59.120> can<00:29:59.559> they<00:29:59.679> can<00:29:59.880> have<00:30:00.120> varying<00:30:00.559> tips 00:30:01.149 --> 00:30:01.159 align:start position:0% they can they can have varying tips 00:30:01.159 --> 00:30:04.230 align:start position:0% they can they can have varying tips between<00:30:01.880> one<00:30:02.360> one<00:30:02.720> one<00:30:03.240> one<00:30:03.559> one<00:30:03.720> gateway<00:30:04.080> to 00:30:04.230 --> 00:30:04.240 align:start position:0% between one one one one one gateway to 00:30:04.240 --> 00:30:06.190 align:start position:0% between one one one one one gateway to another<00:30:05.039> the<00:30:05.240> problem<00:30:05.519> is<00:30:05.760> that<00:30:06.039> with 00:30:06.190 --> 00:30:06.200 align:start position:0% another the problem is that with 00:30:06.200 --> 00:30:08.630 align:start position:0% another the problem is that with gateways<00:30:06.600> is<00:30:06.799> that<00:30:07.480> the<00:30:07.679> gate<00:30:07.960> the<00:30:08.080> gateways 00:30:08.630 --> 00:30:08.640 align:start position:0% gateways is that the gate the gateways 00:30:08.640 --> 00:30:10.909 align:start position:0% gateways is that the gate the gateways will<00:30:08.919> have<00:30:09.039> to<00:30:09.279> compete<00:30:10.039> in<00:30:10.279> the<00:30:10.399> beginning<00:30:10.760> we 00:30:10.909 --> 00:30:10.919 align:start position:0% will have to compete in the beginning we 00:30:10.919 --> 00:30:12.470 align:start position:0% will have to compete in the beginning we might<00:30:11.120> have<00:30:11.279> a<00:30:11.399> couple<00:30:11.600> of<00:30:11.760> gateways<00:30:12.240> out 00:30:12.470 --> 00:30:12.480 align:start position:0% might have a couple of gateways out 00:30:12.480 --> 00:30:15.190 align:start position:0% might have a couple of gateways out there<00:30:13.240> the<00:30:13.440> problem<00:30:13.720> with<00:30:13.880> that<00:30:14.159> is<00:30:14.440> that<00:30:15.000> it 00:30:15.190 --> 00:30:15.200 align:start position:0% there the problem with that is that it 00:30:15.200 --> 00:30:17.630 align:start position:0% there the problem with that is that it it<00:30:15.360> normally<00:30:15.960> con<00:30:16.320> people<00:30:16.640> normally<00:30:17.080> end<00:30:17.279> up 00:30:17.630 --> 00:30:17.640 align:start position:0% it normally con people normally end up 00:30:17.640 --> 00:30:19.789 align:start position:0% it normally con people normally end up converging<00:30:18.279> into<00:30:18.600> a<00:30:18.760> couple<00:30:19.000> of<00:30:19.159> gateways 00:30:19.789 --> 00:30:19.799 align:start position:0% converging into a couple of gateways 00:30:19.799 --> 00:30:22.190 align:start position:0% converging into a couple of gateways that<00:30:20.120> then<00:30:20.320> would<00:30:20.559> have<00:30:20.720> a<00:30:20.880> monopoly<00:30:21.679> so<00:30:21.919> like 00:30:22.190 --> 00:30:22.200 align:start position:0% that then would have a monopoly so like 00:30:22.200 --> 00:30:24.710 align:start position:0% that then would have a monopoly so like two<00:30:22.519> or<00:30:22.720> one<00:30:23.039> Gateway<00:30:23.480> that<00:30:23.600> would<00:30:24.120> then<00:30:24.480> be 00:30:24.710 --> 00:30:24.720 align:start position:0% two or one Gateway that would then be 00:30:24.720 --> 00:30:27.430 align:start position:0% two or one Gateway that would then be dominating<00:30:25.720> because<00:30:26.000> the<00:30:26.200> idea<00:30:26.559> here<00:30:26.760> is<00:30:26.960> that 00:30:27.430 --> 00:30:27.440 align:start position:0% dominating because the idea here is that 00:30:27.440 --> 00:30:29.590 align:start position:0% dominating because the idea here is that if<00:30:27.559> a<00:30:27.720> gate<00:30:28.080> way<00:30:28.279> cannot 00:30:29.590 --> 00:30:29.600 align:start position:0% if a gate way cannot 00:30:29.600 --> 00:30:32.710 align:start position:0% if a gate way cannot secure<00:30:30.600> uh<00:30:30.880> uh<00:30:31.120> verif<00:30:31.559> uh<00:30:31.679> validators<00:30:32.320> or 00:30:32.710 --> 00:30:32.720 align:start position:0% secure uh uh verif uh validators or 00:30:32.720 --> 00:30:35.990 align:start position:0% secure uh uh verif uh validators or proposers<00:30:33.720> that<00:30:33.880> are<00:30:34.080> willing<00:30:34.480> to<00:30:34.760> sell<00:30:35.120> it<00:30:35.720> to 00:30:35.990 --> 00:30:36.000 align:start position:0% proposers that are willing to sell it to 00:30:36.000 --> 00:30:39.509 align:start position:0% proposers that are willing to sell it to sell<00:30:36.440> the<00:30:36.600> Gateway<00:30:37.519> their<00:30:38.080> right<00:30:38.559> to<00:30:38.919> propose 00:30:39.509 --> 00:30:39.519 align:start position:0% sell the Gateway their right to propose 00:30:39.519 --> 00:30:42.350 align:start position:0% sell the Gateway their right to propose these<00:30:40.399> uh<00:30:40.519> Tao<00:30:40.960> transactions<00:30:41.559> the<00:30:41.720> Gateway 00:30:42.350 --> 00:30:42.360 align:start position:0% these uh Tao transactions the Gateway 00:30:42.360 --> 00:30:45.110 align:start position:0% these uh Tao transactions the Gateway cannot<00:30:43.360> uh<00:30:43.519> operate<00:30:44.320> would<00:30:44.480> there<00:30:44.600> ever<00:30:44.840> be<00:30:44.960> an 00:30:45.110 --> 00:30:45.120 align:start position:0% cannot uh operate would there ever be an 00:30:45.120 --> 00:30:47.389 align:start position:0% cannot uh operate would there ever be an inst<00:30:45.679> where 00:30:47.389 --> 00:30:47.399 align:start position:0% inst where 00:30:47.399 --> 00:30:50.630 align:start position:0% inst where pre<00:30:48.399> Builds<00:30:48.720> on<00:30:49.000> other<00:30:49.200> pre 00:30:50.630 --> 00:30:50.640 align:start position:0% pre Builds on other pre 00:30:50.640 --> 00:30:55.629 align:start position:0% pre Builds on other pre fromal<00:30:51.640> yeah<00:30:52.279> so<00:30:53.240> consensus<00:30:54.240> um<00:30:54.600> you<00:30:54.799> do<00:30:55.399> and 00:30:55.629 --> 00:30:55.639 align:start position:0% fromal yeah so consensus um you do and 00:30:55.639 --> 00:30:57.549 align:start position:0% fromal yeah so consensus um you do and that's<00:30:55.840> why<00:30:56.000> we<00:30:56.200> have<00:30:56.360> the<00:30:56.480> P2P<00:30:56.960> I'll<00:30:57.159> explain 00:30:57.549 --> 00:30:57.559 align:start position:0% that's why we have the P2P I'll explain 00:30:57.559 --> 00:30:59.870 align:start position:0% that's why we have the P2P I'll explain that<00:30:57.799> and<00:30:58.039> in<00:30:58.960> this 00:30:59.870 --> 00:30:59.880 align:start position:0% that and in this 00:30:59.880 --> 00:31:04.789 align:start position:0% that and in this slide<00:31:00.880> so<00:31:01.679> when<00:31:01.840> we<00:31:02.000> said<00:31:02.639> here<00:31:03.519> sorry<00:31:04.519> this 00:31:04.789 --> 00:31:04.799 align:start position:0% slide so when we said here sorry this 00:31:04.799 --> 00:31:08.070 align:start position:0% slide so when we said here sorry this this<00:31:05.000> thing<00:31:05.240> is<00:31:05.480> not<00:31:05.960> that<00:31:06.960> okay<00:31:07.240> yeah<00:31:07.399> so<00:31:07.720> when 00:31:08.070 --> 00:31:08.080 align:start position:0% this thing is not that okay yeah so when 00:31:08.080 --> 00:31:10.310 align:start position:0% this thing is not that okay yeah so when when<00:31:08.320> we<00:31:08.559> said<00:31:08.919> that<00:31:09.120> the<00:31:09.240> precom<00:31:09.720> node<00:31:10.080> every 00:31:10.310 --> 00:31:10.320 align:start position:0% when we said that the precom node every 00:31:10.320 --> 00:31:13.669 align:start position:0% when we said that the precom node every 3<00:31:10.600> second<00:31:10.960> batches<00:31:11.320> a<00:31:11.919> transaction<00:31:12.919> uh<00:31:13.440> takes 00:31:13.669 --> 00:31:13.679 align:start position:0% 3 second batches a transaction uh takes 00:31:13.679 --> 00:31:15.830 align:start position:0% 3 second batches a transaction uh takes a<00:31:13.760> batch<00:31:14.000> of<00:31:14.200> transaction<00:31:14.720> and<00:31:14.960> signs<00:31:15.320> it<00:31:15.720> and 00:31:15.830 --> 00:31:15.840 align:start position:0% a batch of transaction and signs it and 00:31:15.840 --> 00:31:17.789 align:start position:0% a batch of transaction and signs it and then<00:31:16.000> it<00:31:16.200> broadcasts<00:31:16.880> the<00:31:17.000> sign<00:31:17.320> prec 00:31:17.789 --> 00:31:17.799 align:start position:0% then it broadcasts the sign prec 00:31:17.799 --> 00:31:20.950 align:start position:0% then it broadcasts the sign prec confirmation<00:31:18.799> precon<00:31:19.360> blocks<00:31:19.679> on<00:31:19.840> P2P<00:31:20.840> this 00:31:20.950 --> 00:31:20.960 align:start position:0% confirmation precon blocks on P2P this 00:31:20.960 --> 00:31:23.990 align:start position:0% confirmation precon blocks on P2P this is<00:31:21.240> important<00:31:21.880> because<00:31:22.760> anyone<00:31:23.080> who's 00:31:23.990 --> 00:31:24.000 align:start position:0% is important because anyone who's 00:31:24.000 --> 00:31:28.149 align:start position:0% is important because anyone who's listening<00:31:25.000> can<00:31:25.200> do<00:31:25.960> a<00:31:26.080> bunch<00:31:26.320> of<00:31:26.519> things<00:31:27.480> first 00:31:28.149 --> 00:31:28.159 align:start position:0% listening can do a bunch of things first 00:31:28.159 --> 00:31:32.789 align:start position:0% listening can do a bunch of things first they<00:31:28.279> can<00:31:28.519> advance<00:31:28.960> the<00:31:29.440> head<00:31:30.440> of<00:31:31.440> the<00:31:32.440> uh<00:31:32.600> of 00:31:32.789 --> 00:31:32.799 align:start position:0% they can advance the head of the uh of 00:31:32.799 --> 00:31:36.590 align:start position:0% they can advance the head of the uh of the<00:31:33.320> Tao<00:31:34.320> so<00:31:34.960> people<00:31:35.320> can<00:31:35.639> keep<00:31:35.960> up<00:31:36.200> with<00:31:36.360> these 00:31:36.590 --> 00:31:36.600 align:start position:0% the Tao so people can keep up with these 00:31:36.600 --> 00:31:38.710 align:start position:0% the Tao so people can keep up with these precon<00:31:37.440> prec<00:31:37.639> confirmation<00:31:38.200> you<00:31:38.279> moving<00:31:38.480> to<00:31:38.559> a 00:31:38.710 --> 00:31:38.720 align:start position:0% precon prec confirmation you moving to a 00:31:38.720 --> 00:31:41.029 align:start position:0% precon prec confirmation you moving to a safe<00:31:38.960> head<00:31:39.360> there<00:31:39.919> sorry<00:31:40.320> is<00:31:40.440> it<00:31:40.559> moving<00:31:40.919> just 00:31:41.029 --> 00:31:41.039 align:start position:0% safe head there sorry is it moving just 00:31:41.039 --> 00:31:43.629 align:start position:0% safe head there sorry is it moving just to<00:31:41.200> a<00:31:41.360> safe<00:31:41.639> head<00:31:42.320> it's<00:31:42.519> not<00:31:42.720> a<00:31:42.919> safe<00:31:43.200> head<00:31:43.440> no 00:31:43.629 --> 00:31:43.639 align:start position:0% to a safe head it's not a safe head no 00:31:43.639 --> 00:31:45.509 align:start position:0% to a safe head it's not a safe head no it's<00:31:43.960> it's<00:31:44.120> not<00:31:44.279> even<00:31:44.480> a<00:31:44.639> safe<00:31:44.960> head<00:31:45.159> at<00:31:45.320> this 00:31:45.509 --> 00:31:45.519 align:start position:0% it's it's not even a safe head at this 00:31:45.519 --> 00:31:48.269 align:start position:0% it's it's not even a safe head at this point<00:31:45.840> because<00:31:46.600> it's<00:31:46.840> basically<00:31:47.240> a<00:31:47.480> soft<00:31:47.840> head 00:31:48.269 --> 00:31:48.279 align:start position:0% point because it's basically a soft head 00:31:48.279 --> 00:31:50.789 align:start position:0% point because it's basically a soft head very<00:31:48.519> soft<00:31:48.840> head<00:31:49.159> because<00:31:49.919> as<00:31:50.080> long<00:31:50.440> as<00:31:50.600> long 00:31:50.789 --> 00:31:50.799 align:start position:0% very soft head because as long as long 00:31:50.799 --> 00:31:53.509 align:start position:0% very soft head because as long as long as<00:31:50.919> it<00:31:51.120> hasn't<00:31:51.440> been<00:31:52.080> proposed<00:31:52.480> on<00:31:52.639> L1<00:31:53.320> it's 00:31:53.509 --> 00:31:53.519 align:start position:0% as it hasn't been proposed on L1 it's 00:31:53.519 --> 00:31:55.990 align:start position:0% as it hasn't been proposed on L1 it's not<00:31:53.760> fully<00:31:54.200> safe<00:31:54.679> I<00:31:54.760> mean<00:31:54.960> there<00:31:55.120> is<00:31:55.519> financial 00:31:55.990 --> 00:31:56.000 align:start position:0% not fully safe I mean there is financial 00:31:56.000 --> 00:31:58.750 align:start position:0% not fully safe I mean there is financial precautions<00:31:56.639> to<00:31:57.320> to<00:31:57.559> that<00:31:57.919> proner<00:31:58.360> if<00:31:58.519> he 00:31:58.750 --> 00:31:58.760 align:start position:0% precautions to to that proner if he 00:31:58.760 --> 00:32:01.190 align:start position:0% precautions to to that proner if he doesn't<00:31:59.440> obey<00:31:59.880> or<00:32:00.120> honor<00:32:00.760> these<00:32:00.960> prec 00:32:01.190 --> 00:32:01.200 align:start position:0% doesn't obey or honor these prec 00:32:01.200 --> 00:32:03.029 align:start position:0% doesn't obey or honor these prec confirmations<00:32:01.880> but<00:32:02.039> they<00:32:02.200> can<00:32:02.399> always 00:32:03.029 --> 00:32:03.039 align:start position:0% confirmations but they can always 00:32:03.039 --> 00:32:06.590 align:start position:0% confirmations but they can always software<00:32:03.480> can<00:32:03.639> always<00:32:04.000> fail<00:32:04.880> or<00:32:05.679> um<00:32:05.960> they<00:32:06.440> they 00:32:06.590 --> 00:32:06.600 align:start position:0% software can always fail or um they they 00:32:06.600 --> 00:32:08.629 align:start position:0% software can always fail or um they they could<00:32:06.799> potentially<00:32:07.279> have<00:32:07.480> other<00:32:07.720> incentives 00:32:08.629 --> 00:32:08.639 align:start position:0% could potentially have other incentives 00:32:08.639 --> 00:32:10.590 align:start position:0% could potentially have other incentives so<00:32:08.840> it's<00:32:08.960> a<00:32:09.159> very<00:32:09.320> soft<00:32:09.679> head<00:32:10.000> but<00:32:10.200> at<00:32:10.320> least 00:32:10.590 --> 00:32:10.600 align:start position:0% so it's a very soft head but at least 00:32:10.600 --> 00:32:13.110 align:start position:0% so it's a very soft head but at least you<00:32:10.760> get<00:32:11.440> consistent<00:32:12.000> block<00:32:12.360> times<00:32:12.880> which<00:32:13.000> is 00:32:13.110 --> 00:32:13.120 align:start position:0% you get consistent block times which is 00:32:13.120 --> 00:32:15.509 align:start position:0% you get consistent block times which is a<00:32:13.320> better<00:32:13.519> user<00:32:14.000> experience<00:32:14.679> than<00:32:15.240> what<00:32:15.360> you 00:32:15.509 --> 00:32:15.519 align:start position:0% a better user experience than what you 00:32:15.519 --> 00:32:18.669 align:start position:0% a better user experience than what you get<00:32:15.840> right<00:32:16.000> now<00:32:16.799> um<00:32:16.960> I<00:32:17.039> mean<00:32:17.200> ano<00:32:17.679> said<00:32:18.039> that 00:32:18.669 --> 00:32:18.679 align:start position:0% get right now um I mean ano said that 00:32:18.679 --> 00:32:21.470 align:start position:0% get right now um I mean ano said that transactions<00:32:19.399> normally<00:32:19.840> take<00:32:20.120> 12<00:32:20.519> seconds 00:32:21.470 --> 00:32:21.480 align:start position:0% transactions normally take 12 seconds 00:32:21.480 --> 00:32:23.509 align:start position:0% transactions normally take 12 seconds and<00:32:21.720> on<00:32:21.960> Tao<00:32:22.480> sometimes<00:32:22.720> they<00:32:22.840> take<00:32:23.120> 20 00:32:23.509 --> 00:32:23.519 align:start position:0% and on Tao sometimes they take 20 00:32:23.519 --> 00:32:25.549 align:start position:0% and on Tao sometimes they take 20 seconds<00:32:23.880> so<00:32:24.080> there<00:32:24.200> is<00:32:24.480> some<00:32:24.679> kind<00:32:24.840> of<00:32:25.200> extra 00:32:25.549 --> 00:32:25.559 align:start position:0% seconds so there is some kind of extra 00:32:25.559 --> 00:32:29.230 align:start position:0% seconds so there is some kind of extra delay<00:32:26.080> it's<00:32:26.320> very<00:32:26.519> long<00:32:26.799> time 00:32:29.230 --> 00:32:29.240 align:start position:0% delay it's very long time 00:32:29.240 --> 00:32:31.909 align:start position:0% delay it's very long time um<00:32:30.120> any<00:32:30.360> other<00:32:30.639> questions<00:32:31.120> before<00:32:31.440> moving<00:32:31.679> on 00:32:31.909 --> 00:32:31.919 align:start position:0% um any other questions before moving on 00:32:31.919 --> 00:32:33.149 align:start position:0% um any other questions before moving on sorry<00:32:32.120> I<00:32:32.200> just<00:32:32.279> wanted<00:32:32.480> to<00:32:32.840> understand<00:32:33.000> the 00:32:33.149 --> 00:32:33.159 align:start position:0% sorry I just wanted to understand the 00:32:33.159 --> 00:32:35.389 align:start position:0% sorry I just wanted to understand the consensus<00:32:33.840> at<00:32:33.960> the<00:32:34.080> P2P<00:32:34.519> lay<00:32:34.760> that<00:32:34.840> you<00:32:34.919> were 00:32:35.389 --> 00:32:35.399 align:start position:0% consensus at the P2P lay that you were 00:32:35.399 --> 00:32:36.950 align:start position:0% consensus at the P2P lay that you were describing 00:32:36.950 --> 00:32:36.960 align:start position:0% describing 00:32:36.960 --> 00:32:39.110 align:start position:0% describing um<00:32:37.960> so<00:32:38.240> what<00:32:38.360> what<00:32:38.480> do<00:32:38.519> you<00:32:38.600> mean<00:32:38.919> the 00:32:39.110 --> 00:32:39.120 align:start position:0% um so what what do you mean the 00:32:39.120 --> 00:32:41.909 align:start position:0% um so what what do you mean the consensus<00:32:39.679> so<00:32:40.000> my<00:32:40.120> original<00:32:40.559> question<00:32:41.000> was<00:32:41.760> if 00:32:41.909 --> 00:32:41.919 align:start position:0% consensus so my original question was if 00:32:41.919 --> 00:32:46.310 align:start position:0% consensus so my original question was if you<00:32:42.679> have<00:32:43.679> um<00:32:44.000> pre-confirmation<00:32:44.880> being<00:32:45.880> built 00:32:46.310 --> 00:32:46.320 align:start position:0% you have um pre-confirmation being built 00:32:46.320 --> 00:32:49.710 align:start position:0% you have um pre-confirmation being built upon<00:32:47.320> by<00:32:48.120> sorry<00:32:48.440> new<00:32:48.679> pre-confirmation<00:32:49.159> being 00:32:49.710 --> 00:32:49.720 align:start position:0% upon by sorry new pre-confirmation being 00:32:49.720 --> 00:32:51.389 align:start position:0% upon by sorry new pre-confirmation being built<00:32:50.000> upon<00:32:50.320> the<00:32:50.440> state<00:32:50.720> of<00:32:50.960> previous 00:32:51.389 --> 00:32:51.399 align:start position:0% built upon the state of previous 00:32:51.399 --> 00:32:52.430 align:start position:0% built upon the state of previous pre-confirmation 00:32:52.430 --> 00:32:52.440 align:start position:0% pre-confirmation 00:32:52.440 --> 00:32:54.950 align:start position:0% pre-confirmation mhm<00:32:53.440> how<00:32:53.559> does<00:32:53.760> that<00:32:54.200> like<00:32:54.360> consensus<00:32:54.840> is 00:32:54.950 --> 00:32:54.960 align:start position:0% mhm how does that like consensus is 00:32:54.960 --> 00:32:58.029 align:start position:0% mhm how does that like consensus is needed<00:32:55.279> there<00:32:55.519> for<00:32:55.880> between<00:32:56.880> two<00:32:57.279> different 00:32:58.029 --> 00:32:58.039 align:start position:0% needed there for between two different 00:32:58.039 --> 00:33:01.350 align:start position:0% needed there for between two different so<00:32:58.720> the<00:32:58.919> the<00:32:59.039> pre<00:32:59.320> confer<00:33:00.159> that<00:33:00.360> comes<00:33:00.960> so 00:33:01.350 --> 00:33:01.360 align:start position:0% so the the pre confer that comes so 00:33:01.360 --> 00:33:04.389 align:start position:0% so the the pre confer that comes so let's<00:33:01.639> say<00:33:02.039> that<00:33:02.760> okay<00:33:03.039> let's<00:33:03.480> um<00:33:03.960> let's<00:33:04.159> say 00:33:04.389 --> 00:33:04.399 align:start position:0% let's say that okay let's um let's say 00:33:04.399 --> 00:33:06.830 align:start position:0% let's say that okay let's um let's say that<00:33:04.639> all<00:33:04.760> of<00:33:04.919> these<00:33:05.039> are<00:33:05.200> pre-c<00:33:05.600> confers<00:33:06.600> and 00:33:06.830 --> 00:33:06.840 align:start position:0% that all of these are pre-c confers and 00:33:06.840 --> 00:33:08.430 align:start position:0% that all of these are pre-c confers and this<00:33:06.960> one<00:33:07.120> is<00:33:07.240> a<00:33:07.399> pre-c<00:33:07.600> confer<00:33:07.880> and<00:33:08.120> has<00:33:08.240> been 00:33:08.430 --> 00:33:08.440 align:start position:0% this one is a pre-c confer and has been 00:33:08.440 --> 00:33:11.269 align:start position:0% this one is a pre-c confer and has been pushing<00:33:09.320> um<00:33:09.760> it<00:33:09.919> pushed<00:33:10.320> basically<00:33:10.760> four 00:33:11.269 --> 00:33:11.279 align:start position:0% pushing um it pushed basically four 00:33:11.279 --> 00:33:14.310 align:start position:0% pushing um it pushed basically four blocks<00:33:12.279> it<00:33:12.480> precom<00:33:13.320> first<00:33:13.519> one<00:33:13.880> second<00:33:14.120> one 00:33:14.310 --> 00:33:14.320 align:start position:0% blocks it precom first one second one 00:33:14.320 --> 00:33:16.549 align:start position:0% blocks it precom first one second one third<00:33:14.600> one<00:33:14.799> fourth<00:33:15.120> one<00:33:15.440> and<00:33:15.639> then<00:33:16.320> it 00:33:16.549 --> 00:33:16.559 align:start position:0% third one fourth one and then it 00:33:16.559 --> 00:33:19.549 align:start position:0% third one fourth one and then it basically<00:33:17.159> just<00:33:17.399> went<00:33:17.799> and<00:33:17.960> pushed<00:33:18.200> it<00:33:18.320> to<00:33:18.559> L1 00:33:19.549 --> 00:33:19.559 align:start position:0% basically just went and pushed it to L1 00:33:19.559 --> 00:33:21.830 align:start position:0% basically just went and pushed it to L1 this<00:33:19.720> one<00:33:20.279> would<00:33:20.480> be<00:33:20.639> listening<00:33:21.279> to<00:33:21.519> these 00:33:21.830 --> 00:33:21.840 align:start position:0% this one would be listening to these 00:33:21.840 --> 00:33:22.870 align:start position:0% this one would be listening to these pre-confirmation 00:33:22.870 --> 00:33:22.880 align:start position:0% pre-confirmation 00:33:22.880 --> 00:33:25.629 align:start position:0% pre-confirmation batches<00:33:23.880> on<00:33:24.039> the<00:33:24.200> P2P<00:33:24.880> and<00:33:25.000> would<00:33:25.240> receive 00:33:25.629 --> 00:33:25.639 align:start position:0% batches on the P2P and would receive 00:33:25.639 --> 00:33:27.389 align:start position:0% batches on the P2P and would receive them<00:33:25.960> and<00:33:26.120> it<00:33:26.240> would<00:33:26.519> just<00:33:26.840> wait<00:33:27.080> for<00:33:27.279> a 00:33:27.389 --> 00:33:27.399 align:start position:0% them and it would just wait for a 00:33:27.399 --> 00:33:30.149 align:start position:0% them and it would just wait for a confirm<00:33:28.120> that<00:33:28.279> they<00:33:28.440> have<00:33:28.639> landed<00:33:29.000> on<00:33:29.159> L1<00:33:30.000> and 00:33:30.149 --> 00:33:30.159 align:start position:0% confirm that they have landed on L1 and 00:33:30.159 --> 00:33:35.990 align:start position:0% confirm that they have landed on L1 and then<00:33:30.320> it<00:33:30.480> would<00:33:30.799> start<00:33:31.200> building<00:33:31.639> on<00:33:31.840> top<00:33:32.039> of 00:33:35.990 --> 00:33:36.000 align:start position:0% 00:33:36.000 --> 00:33:38.549 align:start position:0% that<00:33:37.000> would<00:33:37.200> the<00:33:37.360> middle<00:33:37.679> one<00:33:37.919> be<00:33:38.120> accepting 00:33:38.549 --> 00:33:38.559 align:start position:0% that would the middle one be accepting 00:33:38.559 --> 00:33:40.190 align:start position:0% that would the middle one be accepting pre-confirmation<00:33:39.039> before<00:33:39.600> it's<00:33:39.720> been<00:33:39.919> posted 00:33:40.190 --> 00:33:40.200 align:start position:0% pre-confirmation before it's been posted 00:33:40.200 --> 00:33:44.190 align:start position:0% pre-confirmation before it's been posted to<00:33:40.320> L1<00:33:41.440> no<00:33:42.440> no<00:33:42.760> because<00:33:43.440> since<00:33:44.000> its 00:33:44.190 --> 00:33:44.200 align:start position:0% to L1 no no because since its 00:33:44.200 --> 00:33:45.230 align:start position:0% to L1 no no because since its pre-confirmation 00:33:45.230 --> 00:33:45.240 align:start position:0% pre-confirmation 00:33:45.240 --> 00:33:49.870 align:start position:0% pre-confirmation um<00:33:46.240> depends<00:33:46.840> on<00:33:47.840> uh<00:33:48.120> the<00:33:48.519> the<00:33:48.720> state<00:33:49.240> of<00:33:49.639> what 00:33:49.870 --> 00:33:49.880 align:start position:0% um depends on uh the the state of what 00:33:49.880 --> 00:33:53.950 align:start position:0% um depends on uh the the state of what happens<00:33:50.240> in<00:33:50.519> the<00:33:50.720> chain<00:33:51.159> here<00:33:51.880> so<00:33:52.200> it<00:33:52.399> can't<00:33:53.039> do 00:33:53.950 --> 00:33:53.960 align:start position:0% happens in the chain here so it can't do 00:33:53.960 --> 00:33:57.269 align:start position:0% happens in the chain here so it can't do that<00:33:54.960> or<00:33:55.279> it<00:33:55.399> will<00:33:55.600> collect<00:33:56.159> I<00:33:56.240> mean<00:33:56.519> it<00:33:56.720> can 00:33:57.269 --> 00:33:57.279 align:start position:0% that or it will collect I mean it can 00:33:57.279 --> 00:34:00.029 align:start position:0% that or it will collect I mean it can but<00:33:57.440> it<00:33:57.799> to<00:33:57.880> collect<00:33:58.200> a<00:33:58.320> bunch<00:33:58.519> of<00:33:59.039> potentially 00:34:00.029 --> 00:34:00.039 align:start position:0% but it to collect a bunch of potentially 00:34:00.039 --> 00:34:03.149 align:start position:0% but it to collect a bunch of potentially a<00:34:00.159> bunch<00:34:00.399> of<00:34:01.120> um<00:34:01.559> transactions<00:34:02.559> that<00:34:02.760> has<00:34:02.919> been 00:34:03.149 --> 00:34:03.159 align:start position:0% a bunch of um transactions that has been 00:34:03.159 --> 00:34:05.909 align:start position:0% a bunch of um transactions that has been already<00:34:03.519> included<00:34:04.080> for<00:34:04.320> example<00:34:05.080> so<00:34:05.320> it<00:34:05.440> would 00:34:05.909 --> 00:34:05.919 align:start position:0% already included for example so it would 00:34:05.919 --> 00:34:09.149 align:start position:0% already included for example so it would potentially<00:34:06.399> lose<00:34:06.919> that<00:34:07.240> space<00:34:08.240> uh<00:34:08.320> on<00:34:08.480> the<00:34:08.639> L1 00:34:09.149 --> 00:34:09.159 align:start position:0% potentially lose that space uh on the L1 00:34:09.159 --> 00:34:15.750 align:start position:0% potentially lose that space uh on the L1 side<00:34:10.599> and<00:34:11.599> yeah<00:34:12.040> and<00:34:12.399> also<00:34:13.079> if<00:34:13.440> it<00:34:14.200> um<00:34:14.760> it<00:34:15.560> and 00:34:15.750 --> 00:34:15.760 align:start position:0% side and yeah and also if it um it and 00:34:15.760 --> 00:34:17.750 align:start position:0% side and yeah and also if it um it and if<00:34:15.879> it<00:34:16.000> does<00:34:16.240> not<00:34:16.560> if<00:34:16.679> it<00:34:16.800> sees<00:34:17.240> if<00:34:17.359> it<00:34:17.560> for 00:34:17.750 --> 00:34:17.760 align:start position:0% if it does not if it sees if it for 00:34:17.760 --> 00:34:20.550 align:start position:0% if it does not if it sees if it for example<00:34:18.200> precom<00:34:19.200> a<00:34:19.359> bunch<00:34:19.560> of<00:34:19.760> transactions 00:34:20.550 --> 00:34:20.560 align:start position:0% example precom a bunch of transactions 00:34:20.560 --> 00:34:23.389 align:start position:0% example precom a bunch of transactions that<00:34:21.359> uh<00:34:21.560> then<00:34:21.839> already<00:34:22.240> has<00:34:22.399> landed<00:34:23.240> the 00:34:23.389 --> 00:34:23.399 align:start position:0% that uh then already has landed the 00:34:23.399 --> 00:34:25.310 align:start position:0% that uh then already has landed the execution<00:34:23.879> precom<00:34:24.359> is<00:34:24.440> not<00:34:24.599> honored<00:34:25.200> that 00:34:25.310 --> 00:34:25.320 align:start position:0% execution precom is not honored that 00:34:25.320 --> 00:34:26.829 align:start position:0% execution precom is not honored that doesn't<00:34:25.520> mean<00:34:25.720> that<00:34:25.839> it<00:34:25.919> will<00:34:26.079> be<00:34:26.200> slashed<00:34:26.720> it 00:34:26.829 --> 00:34:26.839 align:start position:0% doesn't mean that it will be slashed it 00:34:26.839 --> 00:34:29.149 align:start position:0% doesn't mean that it will be slashed it won't<00:34:27.079> be<00:34:27.159> slashed<00:34:27.520> in<00:34:27.760> the<00:34:27.919> system<00:34:28.919> that 00:34:29.149 --> 00:34:29.159 align:start position:0% won't be slashed in the system that 00:34:29.159 --> 00:34:30.669 align:start position:0% won't be slashed in the system that because<00:34:29.320> the<00:34:29.440> inclusion<00:34:29.800> precom<00:34:30.280> is<00:34:30.399> still 00:34:30.669 --> 00:34:30.679 align:start position:0% because the inclusion precom is still 00:34:30.679 --> 00:34:33.710 align:start position:0% because the inclusion precom is still there<00:34:31.320> but<00:34:31.480> it<00:34:31.599> will<00:34:31.760> lose<00:34:32.200> that<00:34:32.800> uh<00:34:33.320> that<00:34:33.560> and 00:34:33.710 --> 00:34:33.720 align:start position:0% there but it will lose that uh that and 00:34:33.720 --> 00:34:35.270 align:start position:0% there but it will lose that uh that and if<00:34:33.800> it<00:34:33.919> does<00:34:34.079> not<00:34:34.240> include<00:34:34.639> them<00:34:34.919> it<00:34:35.040> will<00:34:35.159> be 00:34:35.270 --> 00:34:35.280 align:start position:0% if it does not include them it will be 00:34:35.280 --> 00:34:38.389 align:start position:0% if it does not include them it will be slashed<00:34:36.240> so<00:34:37.119> in<00:34:37.320> both<00:34:37.599> cases<00:34:37.919> it's<00:34:38.119> kind<00:34:38.280> of 00:34:38.389 --> 00:34:38.399 align:start position:0% slashed so in both cases it's kind of 00:34:38.399 --> 00:34:40.710 align:start position:0% slashed so in both cases it's kind of losing<00:34:38.800> something<00:34:39.240> of<00:34:39.399> course<00:34:39.960> non-inclusion 00:34:40.710 --> 00:34:40.720 align:start position:0% losing something of course non-inclusion 00:34:40.720 --> 00:34:42.869 align:start position:0% losing something of course non-inclusion makes<00:34:40.879> it<00:34:41.079> lose<00:34:41.399> more<00:34:42.000> so<00:34:42.159> it<00:34:42.240> would<00:34:42.480> include 00:34:42.869 --> 00:34:42.879 align:start position:0% makes it lose more so it would include 00:34:42.879 --> 00:34:44.869 align:start position:0% makes it lose more so it would include them<00:34:43.079> even<00:34:43.320> though<00:34:43.520> they're<00:34:43.960> already 00:34:44.869 --> 00:34:44.879 align:start position:0% them even though they're already 00:34:44.879 --> 00:34:46.669 align:start position:0% them even though they're already processed<00:34:45.480> and<00:34:45.639> will<00:34:45.800> be<00:34:45.960> invalid<00:34:46.399> if<00:34:46.520> they're 00:34:46.669 --> 00:34:46.679 align:start position:0% processed and will be invalid if they're 00:34:46.679 --> 00:34:49.149 align:start position:0% processed and will be invalid if they're included<00:34:47.159> again<00:34:47.919> but<00:34:48.280> it<00:34:48.399> won't<00:34:48.760> at<00:34:48.879> least<00:34:49.079> it 00:34:49.149 --> 00:34:49.159 align:start position:0% included again but it won't at least it 00:34:49.159 --> 00:34:50.069 align:start position:0% included again but it won't at least it won't<00:34:49.399> be 00:34:50.069 --> 00:34:50.079 align:start position:0% won't be 00:34:50.079 --> 00:34:52.710 align:start position:0% won't be slashed<00:34:51.079> yeah<00:34:51.240> so<00:34:51.440> this<00:34:51.520> is<00:34:52.000> this<00:34:52.119> is<00:34:52.240> the 00:34:52.710 --> 00:34:52.720 align:start position:0% slashed yeah so this is this is the 00:34:52.720 --> 00:34:55.109 align:start position:0% slashed yeah so this is this is the consensus<00:34:53.720> um<00:34:53.919> I<00:34:54.000> mean<00:34:54.200> this<00:34:54.320> is<00:34:54.440> a<00:34:54.679> problem 00:34:55.109 --> 00:34:55.119 align:start position:0% consensus um I mean this is a problem 00:34:55.119 --> 00:34:57.430 align:start position:0% consensus um I mean this is a problem with<00:34:55.440> also<00:34:55.919> like<00:34:56.159> varying<00:34:56.560> types<00:34:56.760> of<00:34:56.919> precs 00:34:57.430 --> 00:34:57.440 align:start position:0% with also like varying types of precs 00:34:57.440 --> 00:35:01.030 align:start position:0% with also like varying types of precs because<00:34:57.760> because<00:34:58.480> you<00:34:59.000> can<00:34:59.320> always<00:35:00.160> U<00:35:00.839> that 00:35:01.030 --> 00:35:01.040 align:start position:0% because because you can always U that 00:35:01.040 --> 00:35:03.630 align:start position:0% because because you can always U that like<00:35:01.240> if<00:35:01.480> if<00:35:01.920> so<00:35:02.280> in<00:35:02.440> in<00:35:02.599> the<00:35:02.760> system<00:35:03.359> right<00:35:03.480> now 00:35:03.630 --> 00:35:03.640 align:start position:0% like if if so in in the system right now 00:35:03.640 --> 00:35:04.750 align:start position:0% like if if so in in the system right now we're<00:35:03.800> trying<00:35:04.000> to<00:35:04.160> build<00:35:04.400> with<00:35:04.560> prec 00:35:04.750 --> 00:35:04.760 align:start position:0% we're trying to build with prec 00:35:04.760 --> 00:35:07.589 align:start position:0% we're trying to build with prec confirmations<00:35:05.359> is<00:35:05.520> that<00:35:06.079> trying<00:35:06.280> to<00:35:06.520> avoid<00:35:07.440> a 00:35:07.589 --> 00:35:07.599 align:start position:0% confirmations is that trying to avoid a 00:35:07.599 --> 00:35:10.069 align:start position:0% confirmations is that trying to avoid a singular<00:35:08.119> solution<00:35:09.000> to<00:35:09.200> dominate<00:35:09.760> so<00:35:09.960> there 00:35:10.069 --> 00:35:10.079 align:start position:0% singular solution to dominate so there 00:35:10.079 --> 00:35:11.750 align:start position:0% singular solution to dominate so there is<00:35:10.240> multiple<00:35:10.680> Solutions<00:35:11.160> so<00:35:11.400> there<00:35:11.480> is<00:35:11.599> the 00:35:11.750 --> 00:35:11.760 align:start position:0% is multiple Solutions so there is the 00:35:11.760 --> 00:35:13.510 align:start position:0% is multiple Solutions so there is the Gateway<00:35:12.160> there<00:35:12.240> is<00:35:12.400> what<00:35:12.520> we're<00:35:12.680> building<00:35:13.400> and 00:35:13.510 --> 00:35:13.520 align:start position:0% Gateway there is what we're building and 00:35:13.520 --> 00:35:16.990 align:start position:0% Gateway there is what we're building and there<00:35:13.680> is<00:35:14.160> multiple<00:35:14.640> ones<00:35:15.240> so<00:35:15.960> if<00:35:16.160> each<00:35:16.400> one 00:35:16.990 --> 00:35:17.000 align:start position:0% there is multiple ones so if each one 00:35:17.000 --> 00:35:19.310 align:start position:0% there is multiple ones so if each one kind<00:35:17.160> of<00:35:17.400> like<00:35:17.560> needs<00:35:17.760> to<00:35:17.920> build<00:35:18.200> on<00:35:18.520> the<00:35:18.960> one 00:35:19.310 --> 00:35:19.320 align:start position:0% kind of like needs to build on the one 00:35:19.320 --> 00:35:22.470 align:start position:0% kind of like needs to build on the one other<00:35:19.839> the<00:35:20.000> other<00:35:20.240> one<00:35:20.560> it<00:35:20.720> needs<00:35:20.920> to<00:35:21.119> wait<00:35:21.480> for 00:35:22.470 --> 00:35:22.480 align:start position:0% other the other one it needs to wait for 00:35:22.480 --> 00:35:24.870 align:start position:0% other the other one it needs to wait for um<00:35:22.800> the<00:35:22.920> L1<00:35:23.520> the<00:35:23.599> state<00:35:23.839> of<00:35:23.960> L1<00:35:24.280> to<00:35:24.359> be<00:35:24.480> updated 00:35:24.870 --> 00:35:24.880 align:start position:0% um the L1 the state of L1 to be updated 00:35:24.880 --> 00:35:26.790 align:start position:0% um the L1 the state of L1 to be updated to<00:35:25.000> start<00:35:25.200> building<00:35:25.520> on<00:35:25.680> top<00:35:25.839> of<00:35:25.960> it 00:35:26.790 --> 00:35:26.800 align:start position:0% to start building on top of it 00:35:26.800 --> 00:35:29.790 align:start position:0% to start building on top of it additionally<00:35:27.320> to<00:35:27.480> that<00:35:27.800> that<00:35:28.560> um<00:35:29.040> if<00:35:29.200> someone 00:35:29.790 --> 00:35:29.800 align:start position:0% additionally to that that um if someone 00:35:29.800 --> 00:35:31.910 align:start position:0% additionally to that that um if someone if<00:35:29.880> a<00:35:30.040> user<00:35:30.359> pushes<00:35:30.680> a<00:35:30.880> transaction<00:35:31.560> directly 00:35:31.910 --> 00:35:31.920 align:start position:0% if a user pushes a transaction directly 00:35:31.920 --> 00:35:35.230 align:start position:0% if a user pushes a transaction directly to<00:35:32.119> L1<00:35:32.720> without<00:35:33.720> um<00:35:34.560> without<00:35:34.839> pushing<00:35:35.079> it 00:35:35.230 --> 00:35:35.240 align:start position:0% to L1 without um without pushing it 00:35:35.240 --> 00:35:37.750 align:start position:0% to L1 without um without pushing it through<00:35:35.400> a<00:35:35.560> proner<00:35:36.560> then<00:35:36.839> that<00:35:37.079> also<00:35:37.320> changes 00:35:37.750 --> 00:35:37.760 align:start position:0% through a proner then that also changes 00:35:37.760 --> 00:35:39.510 align:start position:0% through a proner then that also changes the<00:35:37.920> state<00:35:38.200> so<00:35:38.359> it<00:35:38.520> doesn't<00:35:38.839> make<00:35:39.040> any<00:35:39.240> sense 00:35:39.510 --> 00:35:39.520 align:start position:0% the state so it doesn't make any sense 00:35:39.520 --> 00:35:41.069 align:start position:0% the state so it doesn't make any sense at<00:35:39.680> all<00:35:40.240> to<00:35:40.440> start<00:35:40.680> building 00:35:41.069 --> 00:35:41.079 align:start position:0% at all to start building 00:35:41.079 --> 00:35:42.870 align:start position:0% at all to start building pre-confirmation<00:35:41.560> before<00:35:42.320> knowing<00:35:42.720> the 00:35:42.870 --> 00:35:42.880 align:start position:0% pre-confirmation before knowing the 00:35:42.880 --> 00:35:49.109 align:start position:0% pre-confirmation before knowing the exact<00:35:43.240> state<00:35:43.800> in<00:35:43.960> the<00:35:44.079> on<00:35:44.240> the<00:35:44.359> L1<00:35:45.240> yeah<00:35:45.440> thank 00:35:49.109 --> 00:35:49.119 align:start position:0% 00:35:49.119 --> 00:35:56.349 align:start position:0% you<00:35:50.359> okay<00:35:51.359> let's<00:35:51.680> hope<00:35:51.920> this<00:35:52.079> marker<00:35:52.560> starts 00:35:56.349 --> 00:35:56.359 align:start position:0% 00:35:56.359 --> 00:35:59.349 align:start position:0% working<00:35:57.359> okay 00:35:59.349 --> 00:35:59.359 align:start position:0% working okay 00:35:59.359 --> 00:36:03.109 align:start position:0% working okay uh<00:36:00.040> yeah<00:36:00.200> so<00:36:00.359> we<00:36:00.520> talked<00:36:00.800> about<00:36:01.079> slashing 00:36:03.109 --> 00:36:03.119 align:start position:0% uh yeah so we talked about slashing 00:36:03.119 --> 00:36:06.190 align:start position:0% uh yeah so we talked about slashing now<00:36:04.119> so<00:36:04.359> as<00:36:04.480> we<00:36:04.599> said<00:36:05.040> the<00:36:05.200> pre-<00:36:05.440> confer<00:36:05.839> needs 00:36:06.190 --> 00:36:06.200 align:start position:0% now so as we said the pre- confer needs 00:36:06.200 --> 00:36:09.109 align:start position:0% now so as we said the pre- confer needs to<00:36:06.400> include<00:36:07.359> and<00:36:07.599> propose<00:36:08.200> these<00:36:08.480> batches<00:36:08.920> of 00:36:09.109 --> 00:36:09.119 align:start position:0% to include and propose these batches of 00:36:09.119 --> 00:36:10.710 align:start position:0% to include and propose these batches of transactions<00:36:09.760> on 00:36:10.710 --> 00:36:10.720 align:start position:0% transactions on 00:36:10.720 --> 00:36:15.470 align:start position:0% transactions on L1<00:36:12.000> but<00:36:13.000> if<00:36:13.200> this<00:36:13.440> validator<00:36:14.440> is<00:36:14.640> selling<00:36:15.240> his 00:36:15.470 --> 00:36:15.480 align:start position:0% L1 but if this validator is selling his 00:36:15.480 --> 00:36:18.589 align:start position:0% L1 but if this validator is selling his right<00:36:15.880> to<00:36:16.040> build<00:36:16.319> the<00:36:16.480> block<00:36:17.240> to<00:36:17.560> a<00:36:18.319> through 00:36:18.589 --> 00:36:18.599 align:start position:0% right to build the block to a through 00:36:18.599 --> 00:36:21.990 align:start position:0% right to build the block to a through PBS<00:36:19.240> to<00:36:19.400> a<00:36:19.839> builder<00:36:20.839> it<00:36:21.040> cannot<00:36:21.480> accomplish 00:36:21.990 --> 00:36:22.000 align:start position:0% PBS to a builder it cannot accomplish 00:36:22.000 --> 00:36:23.990 align:start position:0% PBS to a builder it cannot accomplish that<00:36:22.280> because<00:36:22.560> it<00:36:22.760> has<00:36:22.920> no<00:36:23.160> control<00:36:23.560> over<00:36:23.800> the 00:36:23.990 --> 00:36:24.000 align:start position:0% that because it has no control over the 00:36:24.000 --> 00:36:25.430 align:start position:0% that because it has no control over the content<00:36:24.440> of<00:36:24.599> that 00:36:25.430 --> 00:36:25.440 align:start position:0% content of that 00:36:25.440 --> 00:36:28.230 align:start position:0% content of that block<00:36:26.440> and<00:36:26.560> the<00:36:26.720> solution<00:36:27.040> we<00:36:27.200> found<00:36:27.359> to<00:36:27.680> that 00:36:28.230 --> 00:36:28.240 align:start position:0% block and the solution we found to that 00:36:28.240 --> 00:36:31.790 align:start position:0% block and the solution we found to that is<00:36:28.480> that<00:36:28.839> we<00:36:28.960> would<00:36:29.160> modify<00:36:29.680> the<00:36:29.839> epbs 00:36:31.790 --> 00:36:31.800 align:start position:0% is that we would modify the epbs 00:36:31.800 --> 00:36:37.589 align:start position:0% is that we would modify the epbs pipeline<00:36:32.800> um<00:36:33.520> to<00:36:34.400> accomplish<00:36:35.160> this<00:36:35.760> exact<00:36:36.760> uh 00:36:37.589 --> 00:36:37.599 align:start position:0% pipeline um to accomplish this exact uh 00:36:37.599 --> 00:36:42.790 align:start position:0% pipeline um to accomplish this exact uh uh<00:36:38.920> goal<00:36:39.920> so<00:36:40.839> the<00:36:41.160> the<00:36:41.480> the<00:36:41.599> precom<00:36:42.040> node<00:36:42.520> would 00:36:42.790 --> 00:36:42.800 align:start position:0% uh goal so the the the precom node would 00:36:42.800 --> 00:36:48.069 align:start position:0% uh goal so the the the precom node would go<00:36:43.000> until<00:36:44.079> basically<00:36:45.079> the<00:36:45.960> the<00:36:46.359> Mev<00:36:47.079> poost 00:36:48.069 --> 00:36:48.079 align:start position:0% go until basically the the Mev poost 00:36:48.079 --> 00:36:50.030 align:start position:0% go until basically the the Mev poost that<00:36:48.359> there<00:36:48.480> is<00:36:48.599> a<00:36:48.800> constraint<00:36:49.720> on<00:36:49.920> the 00:36:50.030 --> 00:36:50.040 align:start position:0% that there is a constraint on the 00:36:50.040 --> 00:36:52.430 align:start position:0% that there is a constraint on the Builder<00:36:50.839> and<00:36:51.000> that<00:36:51.160> the<00:36:51.240> builder<00:36:51.680> needs<00:36:51.960> to 00:36:52.430 --> 00:36:52.440 align:start position:0% Builder and that the builder needs to 00:36:52.440 --> 00:36:55.670 align:start position:0% Builder and that the builder needs to include<00:36:53.440> a<00:36:53.560> bunch<00:36:53.800> of<00:36:53.960> L2<00:36:54.440> blocks<00:36:55.319> which<00:36:55.440> are 00:36:55.670 --> 00:36:55.680 align:start position:0% include a bunch of L2 blocks which are 00:36:55.680 --> 00:36:58.309 align:start position:0% include a bunch of L2 blocks which are basically<00:36:56.319> a<00:36:56.480> couple<00:36:56.760> of<00:36:57.079> L1<00:36:57.640> transactions<00:36:58.160> or 00:36:58.309 --> 00:36:58.319 align:start position:0% basically a couple of L1 transactions or 00:36:58.319 --> 00:37:01.030 align:start position:0% basically a couple of L1 transactions or it<00:36:58.440> could<00:36:58.599> be<00:36:58.800> one<00:36:59.040> L1<00:36:59.520> transaction<00:37:00.400> and<00:37:00.599> their 00:37:01.030 --> 00:37:01.040 align:start position:0% it could be one L1 transaction and their 00:37:01.040 --> 00:37:04.309 align:start position:0% it could be one L1 transaction and their blobs<00:37:02.040> and<00:37:02.680> it<00:37:02.839> could<00:37:03.160> in<00:37:03.440> it<00:37:03.520> should<00:37:03.839> include 00:37:04.309 --> 00:37:04.319 align:start position:0% blobs and it could in it should include 00:37:04.319 --> 00:37:08.550 align:start position:0% blobs and it could in it should include them<00:37:05.280> and<00:37:05.480> that's<00:37:05.800> why<00:37:06.079> the<00:37:06.800> uh<00:37:07.760> and<00:37:08.119> and<00:37:08.319> then 00:37:08.550 --> 00:37:08.560 align:start position:0% them and that's why the uh and and then 00:37:08.560 --> 00:37:11.630 align:start position:0% them and that's why the uh and and then the<00:37:08.839> PBS<00:37:09.359> relayer<00:37:09.839> would<00:37:10.240> return<00:37:10.720> with<00:37:11.160> okay 00:37:11.630 --> 00:37:11.640 align:start position:0% the PBS relayer would return with okay 00:37:11.640 --> 00:37:14.470 align:start position:0% the PBS relayer would return with okay yeah<00:37:11.800> I<00:37:11.920> can<00:37:12.040> honor<00:37:12.480> that<00:37:13.280> and<00:37:13.920> and<00:37:14.119> they<00:37:14.240> build 00:37:14.470 --> 00:37:14.480 align:start position:0% yeah I can honor that and and they build 00:37:14.480 --> 00:37:17.030 align:start position:0% yeah I can honor that and and they build a<00:37:14.640> block<00:37:15.440> including<00:37:16.079> these<00:37:16.319> transactions<00:37:16.920> at 00:37:17.030 --> 00:37:17.040 align:start position:0% a block including these transactions at 00:37:17.040 --> 00:37:20.510 align:start position:0% a block including these transactions at the<00:37:17.200> end<00:37:17.960> and<00:37:18.160> we<00:37:18.359> propose<00:37:18.760> the<00:37:18.880> L1<00:37:19.400> block<00:37:20.400> this 00:37:20.510 --> 00:37:20.520 align:start position:0% the end and we propose the L1 block this 00:37:20.520 --> 00:37:22.829 align:start position:0% the end and we propose the L1 block this is<00:37:20.680> the<00:37:20.839> way<00:37:21.119> that<00:37:21.880> um<00:37:22.079> and<00:37:22.280> currently<00:37:22.640> we're 00:37:22.829 --> 00:37:22.839 align:start position:0% is the way that um and currently we're 00:37:22.839 --> 00:37:26.069 align:start position:0% is the way that um and currently we're using<00:37:23.560> um<00:37:24.200> bolt<00:37:24.560> Smith<00:37:24.880> boost<00:37:25.599> because<00:37:25.920> they 00:37:26.069 --> 00:37:26.079 align:start position:0% using um bolt Smith boost because they 00:37:26.079 --> 00:37:27.790 align:start position:0% using um bolt Smith boost because they have<00:37:26.319> that<00:37:26.520> constraint<00:37:27.000> API<00:37:27.560> already 00:37:27.790 --> 00:37:27.800 align:start position:0% have that constraint API already 00:37:27.800 --> 00:37:29.630 align:start position:0% have that constraint API already implemented<00:37:28.319> so<00:37:28.520> we<00:37:29.079> we<00:37:29.160> didn't<00:37:29.359> want<00:37:29.480> to 00:37:29.630 --> 00:37:29.640 align:start position:0% implemented so we we didn't want to 00:37:29.640 --> 00:37:32.270 align:start position:0% implemented so we we didn't want to implement<00:37:30.319> reimplement<00:37:30.920> the<00:37:31.040> wheel<00:37:31.880> but<00:37:32.119> of 00:37:32.270 --> 00:37:32.280 align:start position:0% implement reimplement the wheel but of 00:37:32.280 --> 00:37:35.510 align:start position:0% implement reimplement the wheel but of course<00:37:32.880> there<00:37:33.040> is<00:37:33.319> also<00:37:33.680> commit<00:37:34.040> boost<00:37:35.000> which 00:37:35.510 --> 00:37:35.520 align:start position:0% course there is also commit boost which 00:37:35.520 --> 00:37:38.390 align:start position:0% course there is also commit boost which can<00:37:36.160> have<00:37:36.520> that<00:37:36.920> bolt<00:37:37.280> myth<00:37:37.560> boost<00:37:37.880> module 00:37:38.390 --> 00:37:38.400 align:start position:0% can have that bolt myth boost module 00:37:38.400 --> 00:37:41.349 align:start position:0% can have that bolt myth boost module built<00:37:38.680> on<00:37:38.839> it<00:37:39.760> and<00:37:40.440> you<00:37:40.520> can<00:37:40.720> have<00:37:40.839> it<00:37:41.000> for<00:37:41.160> more 00:37:41.349 --> 00:37:41.359 align:start position:0% built on it and you can have it for more 00:37:41.359 --> 00:37:43.030 align:start position:0% built on it and you can have it for more details<00:37:41.720> on<00:37:41.960> those<00:37:42.200> please<00:37:42.400> search<00:37:42.680> them<00:37:42.839> on 00:37:43.030 --> 00:37:43.040 align:start position:0% details on those please search them on 00:37:43.040 --> 00:37:46.069 align:start position:0% details on those please search them on Google<00:37:43.480> commit<00:37:43.800> boost<00:37:44.359> and<00:37:44.599> bolt<00:37:45.000> M<00:37:45.319> boost 00:37:46.069 --> 00:37:46.079 align:start position:0% Google commit boost and bolt M boost 00:37:46.079 --> 00:37:48.270 align:start position:0% Google commit boost and bolt M boost both<00:37:46.240> of<00:37:46.440> them<00:37:46.760> are<00:37:47.240> they<00:37:47.400> have<00:37:47.680> open<00:37:48.000> source 00:37:48.270 --> 00:37:48.280 align:start position:0% both of them are they have open source 00:37:48.280 --> 00:37:51.670 align:start position:0% both of them are they have open source GitHub<00:37:48.760> repositories<00:37:49.760> that<00:37:49.880> you<00:37:50.040> can<00:37:50.920> um<00:37:51.440> uh 00:37:51.670 --> 00:37:51.680 align:start position:0% GitHub repositories that you can um uh 00:37:51.680 --> 00:37:53.550 align:start position:0% GitHub repositories that you can um uh look<00:37:51.839> at<00:37:52.240> and 00:37:53.550 --> 00:37:53.560 align:start position:0% look at and 00:37:53.560 --> 00:37:56.349 align:start position:0% look at and yeah<00:37:54.560> pre-conference<00:37:55.160> selection<00:37:55.920> I<00:37:56.079> think 00:37:56.349 --> 00:37:56.359 align:start position:0% yeah pre-conference selection I think 00:37:56.359 --> 00:37:58.390 align:start position:0% yeah pre-conference selection I think Anu<00:37:56.720> will<00:37:56.880> take<00:37:57.040> over<00:37:57.280> here 00:37:58.390 --> 00:37:58.400 align:start position:0% Anu will take over here 00:37:58.400 --> 00:38:01.870 align:start position:0% Anu will take over here thank<00:37:58.560> you<00:37:58.720> sir<00:37:59.240> thank<00:37:59.599> you<00:38:00.599> you<00:38:00.720> want<00:38:00.880> the<00:38:01.040> mic 00:38:01.870 --> 00:38:01.880 align:start position:0% thank you sir thank you you want the mic 00:38:01.880 --> 00:38:04.950 align:start position:0% thank you sir thank you you want the mic mic<00:38:02.200> just<00:38:02.400> this<00:38:02.560> one 00:38:04.950 --> 00:38:04.960 align:start position:0% 00:38:04.960 --> 00:38:08.109 align:start position:0% yeah<00:38:05.960> okay<00:38:06.280> so<00:38:06.480> now<00:38:06.680> you<00:38:06.880> have<00:38:07.160> a<00:38:07.359> good<00:38:07.599> idea<00:38:07.920> of 00:38:08.109 --> 00:38:08.119 align:start position:0% yeah okay so now you have a good idea of 00:38:08.119 --> 00:38:10.270 align:start position:0% yeah okay so now you have a good idea of what<00:38:08.319> the<00:38:08.520> overall<00:38:08.960> design<00:38:09.280> looks 00:38:10.270 --> 00:38:10.280 align:start position:0% what the overall design looks 00:38:10.280 --> 00:38:12.589 align:start position:0% what the overall design looks like<00:38:11.280> and<00:38:11.520> let's<00:38:11.680> talk<00:38:11.839> about<00:38:12.000> pre-con<00:38:12.359> fer 00:38:12.589 --> 00:38:12.599 align:start position:0% like and let's talk about pre-con fer 00:38:12.599 --> 00:38:14.990 align:start position:0% like and let's talk about pre-con fer selection<00:38:13.119> because<00:38:13.480> we<00:38:13.839> did<00:38:14.160> speak<00:38:14.480> about<00:38:14.760> how 00:38:14.990 --> 00:38:15.000 align:start position:0% selection because we did speak about how 00:38:15.000 --> 00:38:18.150 align:start position:0% selection because we did speak about how we<00:38:15.119> want<00:38:15.800> the<00:38:16.440> L1<00:38:16.920> proposer<00:38:17.359> to<00:38:17.480> be<00:38:17.680> the<00:38:17.839> only 00:38:18.150 --> 00:38:18.160 align:start position:0% we want the L1 proposer to be the only 00:38:18.160 --> 00:38:20.589 align:start position:0% we want the L1 proposer to be the only one<00:38:18.640> who<00:38:18.800> can<00:38:19.000> precom<00:38:19.560> and<00:38:19.680> then<00:38:19.839> propose<00:38:20.440> the 00:38:20.589 --> 00:38:20.599 align:start position:0% one who can precom and then propose the 00:38:20.599 --> 00:38:23.589 align:start position:0% one who can precom and then propose the L2<00:38:21.000> blocks<00:38:21.319> in<00:38:21.480> a<00:38:21.599> particular<00:38:22.280> slot<00:38:23.280> now<00:38:23.480> this 00:38:23.589 --> 00:38:23.599 align:start position:0% L2 blocks in a particular slot now this 00:38:23.599 --> 00:38:25.190 align:start position:0% L2 blocks in a particular slot now this is<00:38:23.800> actually<00:38:24.040> a<00:38:24.160> very<00:38:24.359> hard<00:38:24.680> problem<00:38:24.960> even 00:38:25.190 --> 00:38:25.200 align:start position:0% is actually a very hard problem even 00:38:25.200 --> 00:38:27.790 align:start position:0% is actually a very hard problem even though<00:38:25.319> it<00:38:25.440> doesn't<00:38:25.720> look<00:38:26.000> like<00:38:26.800> because<00:38:27.599> at 00:38:27.790 --> 00:38:27.800 align:start position:0% though it doesn't look like because at 00:38:27.800 --> 00:38:30.550 align:start position:0% though it doesn't look like because at ethereum<00:38:28.440> we<00:38:28.839> love<00:38:29.359> patching<00:38:29.760> things<00:38:30.040> up<00:38:30.400> and 00:38:30.550 --> 00:38:30.560 align:start position:0% ethereum we love patching things up and 00:38:30.560 --> 00:38:33.309 align:start position:0% ethereum we love patching things up and in<00:38:30.760> the<00:38:31.680> process<00:38:31.960> of<00:38:32.119> patching<00:38:32.480> things<00:38:32.680> up<00:38:33.000> we 00:38:33.309 --> 00:38:33.319 align:start position:0% in the process of patching things up we 00:38:33.319 --> 00:38:34.670 align:start position:0% in the process of patching things up we develop<00:38:33.680> new 00:38:34.670 --> 00:38:34.680 align:start position:0% develop new 00:38:34.680 --> 00:38:39.870 align:start position:0% develop new problems<00:38:35.680> so<00:38:36.400> when<00:38:37.160> eth<00:38:37.440> moved<00:38:37.720> from<00:38:37.920> P<00:38:38.400> to<00:38:38.880> POS 00:38:39.870 --> 00:38:39.880 align:start position:0% problems so when eth moved from P to POS 00:38:39.880 --> 00:38:41.589 align:start position:0% problems so when eth moved from P to POS what<00:38:40.000> happened<00:38:40.359> was<00:38:40.640> we<00:38:40.800> introduced<00:38:41.319> a<00:38:41.440> new 00:38:41.589 --> 00:38:41.599 align:start position:0% what happened was we introduced a new 00:38:41.599 --> 00:38:43.829 align:start position:0% what happened was we introduced a new layer<00:38:41.920> the<00:38:42.079> consensus<00:38:42.599> layer<00:38:43.079> besides<00:38:43.520> the 00:38:43.829 --> 00:38:43.839 align:start position:0% layer the consensus layer besides the 00:38:43.839 --> 00:38:46.390 align:start position:0% layer the consensus layer besides the existing<00:38:44.480> execution<00:38:45.480> so<00:38:45.720> earlier<00:38:46.079> it<00:38:46.200> was 00:38:46.390 --> 00:38:46.400 align:start position:0% existing execution so earlier it was 00:38:46.400 --> 00:38:48.470 align:start position:0% existing execution so earlier it was merged<00:38:46.800> into<00:38:47.040> like<00:38:47.200> one<00:38:47.400> single<00:38:47.760> thing<00:38:48.319> and 00:38:48.470 --> 00:38:48.480 align:start position:0% merged into like one single thing and 00:38:48.480 --> 00:38:50.109 align:start position:0% merged into like one single thing and now<00:38:48.640> we<00:38:48.839> have<00:38:49.119> it's<00:38:49.319> separate<00:38:49.720> we<00:38:49.839> have<00:38:49.960> a 00:38:50.109 --> 00:38:50.119 align:start position:0% now we have it's separate we have a 00:38:50.119 --> 00:38:52.510 align:start position:0% now we have it's separate we have a consensus<00:38:50.640> layer<00:38:51.280> which<00:38:51.480> manages<00:38:51.880> the<00:38:52.040> POS 00:38:52.510 --> 00:38:52.520 align:start position:0% consensus layer which manages the POS 00:38:52.520 --> 00:38:54.630 align:start position:0% consensus layer which manages the POS part<00:38:53.079> and<00:38:53.200> we<00:38:53.359> have<00:38:53.520> the<00:38:53.680> execution<00:38:54.200> layer 00:38:54.630 --> 00:38:54.640 align:start position:0% part and we have the execution layer 00:38:54.640 --> 00:38:56.270 align:start position:0% part and we have the execution layer where<00:38:55.200> which<00:38:55.319> is<00:38:55.480> what<00:38:55.599> we<00:38:55.760> developers 00:38:56.270 --> 00:38:56.280 align:start position:0% where which is what we developers 00:38:56.280 --> 00:38:57.910 align:start position:0% where which is what we developers usually<00:38:56.680> handle<00:38:57.079> when<00:38:57.240> we<00:38:57.440> are<00:38:57.560> develop 00:38:57.910 --> 00:38:57.920 align:start position:0% usually handle when we are develop 00:38:57.920 --> 00:38:59.670 align:start position:0% usually handle when we are develop deploying<00:38:58.319> smart<00:38:58.560> contracts<00:38:58.920> or<00:38:59.119> interacting 00:38:59.670 --> 00:38:59.680 align:start position:0% deploying smart contracts or interacting 00:38:59.680 --> 00:39:02.550 align:start position:0% deploying smart contracts or interacting with<00:38:59.839> ethereum<00:39:00.240> using<00:39:00.480> a<00:39:01.040> wallet<00:39:02.040> the<00:39:02.240> problem 00:39:02.550 --> 00:39:02.560 align:start position:0% with ethereum using a wallet the problem 00:39:02.560 --> 00:39:05.470 align:start position:0% with ethereum using a wallet the problem is<00:39:03.319> the<00:39:03.520> consensus<00:39:04.040> layer<00:39:04.319> is<00:39:04.560> where<00:39:05.240> the 00:39:05.470 --> 00:39:05.480 align:start position:0% is the consensus layer is where the 00:39:05.480 --> 00:39:07.589 align:start position:0% is the consensus layer is where the proposer<00:39:06.200> identity 00:39:07.589 --> 00:39:07.599 align:start position:0% proposer identity 00:39:07.599 --> 00:39:11.510 align:start position:0% proposer identity lives<00:39:08.599> and<00:39:08.920> that<00:39:09.760> has<00:39:09.960> a<00:39:10.119> BLS<00:39:10.680> signature 00:39:11.510 --> 00:39:11.520 align:start position:0% lives and that has a BLS signature 00:39:11.520 --> 00:39:14.069 align:start position:0% lives and that has a BLS signature scheme<00:39:12.520> but<00:39:12.680> the<00:39:12.839> execution<00:39:13.400> layer<00:39:13.720> where<00:39:13.920> all 00:39:14.069 --> 00:39:14.079 align:start position:0% scheme but the execution layer where all 00:39:14.079 --> 00:39:15.950 align:start position:0% scheme but the execution layer where all the<00:39:14.240> inbox<00:39:14.680> contracts<00:39:15.160> are<00:39:15.520> where<00:39:15.680> all<00:39:15.839> the 00:39:15.950 --> 00:39:15.960 align:start position:0% the inbox contracts are where all the 00:39:15.960 --> 00:39:18.670 align:start position:0% the inbox contracts are where all the transactions<00:39:16.480> are<00:39:16.640> made<00:39:17.480> that<00:39:17.640> has<00:39:17.760> an<00:39:17.920> ecdsa 00:39:18.670 --> 00:39:18.680 align:start position:0% transactions are made that has an ecdsa 00:39:18.680 --> 00:39:21.069 align:start position:0% transactions are made that has an ecdsa signature<00:39:19.160> scheme<00:39:20.040> and<00:39:20.240> that's<00:39:20.599> a<00:39:20.800> big 00:39:21.069 --> 00:39:21.079 align:start position:0% signature scheme and that's a big 00:39:21.079 --> 00:39:23.190 align:start position:0% signature scheme and that's a big problem<00:39:21.960> how<00:39:22.119> do<00:39:22.240> we<00:39:22.359> make<00:39:22.520> a<00:39:22.640> connection 00:39:23.190 --> 00:39:23.200 align:start position:0% problem how do we make a connection 00:39:23.200 --> 00:39:24.990 align:start position:0% problem how do we make a connection between<00:39:23.520> both<00:39:23.680> of<00:39:23.880> these<00:39:24.319> there's<00:39:24.560> no<00:39:24.760> way<00:39:24.880> to 00:39:24.990 --> 00:39:25.000 align:start position:0% between both of these there's no way to 00:39:25.000 --> 00:39:28.790 align:start position:0% between both of these there's no way to make<00:39:25.119> a<00:39:25.240> connection 00:39:28.790 --> 00:39:28.800 align:start position:0% 00:39:28.800 --> 00:39:30.510 align:start position:0% so<00:39:29.000> what<00:39:29.119> we<00:39:29.240> need<00:39:29.400> is<00:39:29.560> we<00:39:29.680> need<00:39:29.839> a<00:39:30.000> BLS<00:39:30.359> to 00:39:30.510 --> 00:39:30.520 align:start position:0% so what we need is we need a BLS to 00:39:30.520 --> 00:39:34.349 align:start position:0% so what we need is we need a BLS to ecdsa<00:39:31.119> mapping<00:39:31.920> so<00:39:32.119> let's<00:39:32.319> say<00:39:33.119> I'm<00:39:33.319> an<00:39:33.440> entity 00:39:34.349 --> 00:39:34.359 align:start position:0% ecdsa mapping so let's say I'm an entity 00:39:34.359 --> 00:39:36.910 align:start position:0% ecdsa mapping so let's say I'm an entity I<00:39:34.800> have<00:39:35.000> an<00:39:35.119> ecdsa<00:39:35.800> address<00:39:36.359> and<00:39:36.480> I<00:39:36.560> run<00:39:36.800> a 00:39:36.910 --> 00:39:36.920 align:start position:0% I have an ecdsa address and I run a 00:39:36.920 --> 00:39:38.349 align:start position:0% I have an ecdsa address and I run a thousand<00:39:37.200> validators<00:39:37.800> with<00:39:37.960> thousand 00:39:38.349 --> 00:39:38.359 align:start position:0% thousand validators with thousand 00:39:38.359 --> 00:39:40.109 align:start position:0% thousand validators with thousand different<00:39:38.800> BLS<00:39:39.319> public 00:39:40.109 --> 00:39:40.119 align:start position:0% different BLS public 00:39:40.119 --> 00:39:43.109 align:start position:0% different BLS public keys<00:39:41.119> I<00:39:41.240> need<00:39:41.560> a<00:39:41.800> way<00:39:42.200> that<00:39:42.319> I<00:39:42.440> can<00:39:42.680> prove<00:39:42.960> that 00:39:43.109 --> 00:39:43.119 align:start position:0% keys I need a way that I can prove that 00:39:43.119 --> 00:39:45.270 align:start position:0% keys I need a way that I can prove that I<00:39:43.359> own<00:39:43.640> those<00:39:43.839> thousand<00:39:44.160> validators<00:39:45.079> I<00:39:45.160> can 00:39:45.270 --> 00:39:45.280 align:start position:0% I own those thousand validators I can 00:39:45.280 --> 00:39:46.990 align:start position:0% I own those thousand validators I can show<00:39:45.480> it<00:39:45.560> to<00:39:45.720> the<00:39:45.880> registry<00:39:46.319> contract<00:39:46.720> so<00:39:46.880> we 00:39:46.990 --> 00:39:47.000 align:start position:0% show it to the registry contract so we 00:39:47.000 --> 00:39:48.670 align:start position:0% show it to the registry contract so we have<00:39:47.520> the<00:39:47.640> pre-confirmation<00:39:48.079> service 00:39:48.670 --> 00:39:48.680 align:start position:0% have the pre-confirmation service 00:39:48.680 --> 00:39:50.150 align:start position:0% have the pre-confirmation service contracts<00:39:49.480> actually<00:39:49.760> have<00:39:49.920> three 00:39:50.150 --> 00:39:50.160 align:start position:0% contracts actually have three 00:39:50.160 --> 00:39:51.630 align:start position:0% contracts actually have three subcontracts<00:39:50.880> the<00:39:51.000> pre-confirmation 00:39:51.630 --> 00:39:51.640 align:start position:0% subcontracts the pre-confirmation 00:39:51.640 --> 00:39:53.670 align:start position:0% subcontracts the pre-confirmation registry<00:39:52.640> which<00:39:52.800> we'll<00:39:53.000> be<00:39:53.119> dealing<00:39:53.400> with<00:39:53.520> in 00:39:53.670 --> 00:39:53.680 align:start position:0% registry which we'll be dealing with in 00:39:53.680 --> 00:39:55.589 align:start position:0% registry which we'll be dealing with in this<00:39:53.800> slide<00:39:54.440> and<00:39:54.599> two<00:39:54.800> other<00:39:55.000> contracts<00:39:55.480> that 00:39:55.589 --> 00:39:55.599 align:start position:0% this slide and two other contracts that 00:39:55.599 --> 00:39:58.390 align:start position:0% this slide and two other contracts that we'll<00:39:55.760> be<00:39:55.920> taking<00:39:56.160> up<00:39:56.359> later<00:39:56.599> on 00:39:58.390 --> 00:39:58.400 align:start position:0% we'll be taking up later on 00:39:58.400 --> 00:40:01.230 align:start position:0% we'll be taking up later on so<00:39:58.680> this<00:39:58.880> entity<00:39:59.760> needs<00:40:00.040> to<00:40:00.280> prove<00:40:00.680> that<00:40:00.920> hey<00:40:01.119> I 00:40:01.230 --> 00:40:01.240 align:start position:0% so this entity needs to prove that hey I 00:40:01.240 --> 00:40:03.750 align:start position:0% so this entity needs to prove that hey I own<00:40:01.520> these<00:40:01.720> validators<00:40:02.720> and<00:40:02.920> I<00:40:03.160> actually<00:40:03.560> have 00:40:03.750 --> 00:40:03.760 align:start position:0% own these validators and I actually have 00:40:03.760 --> 00:40:05.910 align:start position:0% own these validators and I actually have the<00:40:03.920> right<00:40:04.079> to<00:40:04.319> propose<00:40:05.040> an<00:40:05.200> L2<00:40:05.560> Block<00:40:05.760> in<00:40:05.839> a 00:40:05.910 --> 00:40:05.920 align:start position:0% the right to propose an L2 Block in a 00:40:05.920 --> 00:40:08.670 align:start position:0% the right to propose an L2 Block in a particular<00:40:06.680> slot<00:40:07.680> and<00:40:07.839> how<00:40:08.040> exactly<00:40:08.359> do<00:40:08.480> you 00:40:08.670 --> 00:40:08.680 align:start position:0% particular slot and how exactly do you 00:40:08.680 --> 00:40:11.430 align:start position:0% particular slot and how exactly do you prove<00:40:09.079> ownership<00:40:09.800> of<00:40:10.079> a<00:40:10.280> key<00:40:10.880> through 00:40:11.430 --> 00:40:11.440 align:start position:0% prove ownership of a key through 00:40:11.440 --> 00:40:14.069 align:start position:0% prove ownership of a key through signatures<00:40:12.520> right<00:40:13.520> so<00:40:13.680> we<00:40:13.800> have<00:40:13.960> this 00:40:14.069 --> 00:40:14.079 align:start position:0% signatures right so we have this 00:40:14.079 --> 00:40:15.990 align:start position:0% signatures right so we have this signature<00:40:14.520> format<00:40:14.960> here<00:40:15.319> which<00:40:15.440> you<00:40:15.520> can<00:40:15.680> see 00:40:15.990 --> 00:40:16.000 align:start position:0% signature format here which you can see 00:40:16.000 --> 00:40:18.309 align:start position:0% signature format here which you can see it<00:40:16.160> basically<00:40:16.640> has<00:40:16.920> the<00:40:17.119> standard<00:40:17.800> thing<00:40:18.040> like 00:40:18.309 --> 00:40:18.319 align:start position:0% it basically has the standard thing like 00:40:18.319 --> 00:40:21.069 align:start position:0% it basically has the standard thing like having<00:40:18.560> a<00:40:18.760> chain<00:40:19.040> ID<00:40:19.560> and<00:40:19.760> then<00:40:20.200> validator<00:40:20.760> op 00:40:21.069 --> 00:40:21.079 align:start position:0% having a chain ID and then validator op 00:40:21.079 --> 00:40:22.630 align:start position:0% having a chain ID and then validator op is<00:40:21.200> basically<00:40:21.640> either<00:40:21.880> zero<00:40:22.079> or<00:40:22.200> one<00:40:22.400> if<00:40:22.480> it's 00:40:22.630 --> 00:40:22.640 align:start position:0% is basically either zero or one if it's 00:40:22.640 --> 00:40:23.950 align:start position:0% is basically either zero or one if it's zero<00:40:22.839> you're<00:40:23.000> removing<00:40:23.280> a<00:40:23.400> validator<00:40:23.839> from 00:40:23.950 --> 00:40:23.960 align:start position:0% zero you're removing a validator from 00:40:23.960 --> 00:40:26.630 align:start position:0% zero you're removing a validator from your<00:40:24.200> list<00:40:24.560> one<00:40:24.760> you're<00:40:25.400> adding<00:40:26.400> and<00:40:26.520> then 00:40:26.630 --> 00:40:26.640 align:start position:0% your list one you're adding and then 00:40:26.640 --> 00:40:28.190 align:start position:0% your list one you're adding and then there<00:40:26.760> is<00:40:26.880> an<00:40:27.000> experim<00:40:27.520> and<00:40:27.720> the<00:40:27.880> actual 00:40:28.190 --> 00:40:28.200 align:start position:0% there is an experim and the actual 00:40:28.200 --> 00:40:31.990 align:start position:0% there is an experim and the actual precon<00:40:28.720> fer<00:40:29.720> so<00:40:30.440> in<00:40:30.680> here<00:40:31.000> the<00:40:31.119> pre-<00:40:31.359> confer<00:40:31.800> in 00:40:31.990 --> 00:40:32.000 align:start position:0% precon fer so in here the pre- confer in 00:40:32.000 --> 00:40:35.750 align:start position:0% precon fer so in here the pre- confer in the<00:40:32.839> signature<00:40:33.839> uh<00:40:34.079> message<00:40:34.839> is<00:40:35.000> the<00:40:35.119> ecdsa 00:40:35.750 --> 00:40:35.760 align:start position:0% the signature uh message is the ecdsa 00:40:35.760 --> 00:40:37.470 align:start position:0% the signature uh message is the ecdsa address<00:40:36.160> that<00:40:36.280> I'm<00:40:36.520> claiming<00:40:37.200> that<00:40:37.319> is 00:40:37.470 --> 00:40:37.480 align:start position:0% address that I'm claiming that is 00:40:37.480 --> 00:40:40.910 align:start position:0% address that I'm claiming that is claiming<00:40:38.319> the<00:40:38.440> ownership<00:40:38.920> of<00:40:39.040> a<00:40:39.160> BLS 00:40:40.910 --> 00:40:40.920 align:start position:0% claiming the ownership of a BLS 00:40:40.920 --> 00:40:44.270 align:start position:0% claiming the ownership of a BLS address<00:40:41.920> so<00:40:42.079> the<00:40:42.200> ecdsa<00:40:42.839> address<00:40:43.319> just<00:40:43.560> pushes 00:40:44.270 --> 00:40:44.280 align:start position:0% address so the ecdsa address just pushes 00:40:44.280 --> 00:40:46.510 align:start position:0% address so the ecdsa address just pushes a<00:40:44.480> signature<00:40:45.440> and<00:40:45.599> the<00:40:45.760> contract<00:40:46.319> just 00:40:46.510 --> 00:40:46.520 align:start position:0% a signature and the contract just 00:40:46.520 --> 00:40:48.390 align:start position:0% a signature and the contract just verifies<00:40:47.200> that<00:40:47.440> yeah<00:40:47.599> it's<00:40:47.760> the<00:40:47.880> signature<00:40:48.240> is 00:40:48.390 --> 00:40:48.400 align:start position:0% verifies that yeah it's the signature is 00:40:48.400 --> 00:40:50.349 align:start position:0% verifies that yeah it's the signature is correct<00:40:48.760> and<00:40:48.920> this<00:40:49.040> BLS<00:40:49.440> public<00:40:49.760> key<00:40:50.119> actually 00:40:50.349 --> 00:40:50.359 align:start position:0% correct and this BLS public key actually 00:40:50.359 --> 00:40:52.950 align:start position:0% correct and this BLS public key actually belongs<00:40:50.680> to<00:40:50.839> this<00:40:50.920> ecdsa<00:40:51.599> key<00:40:52.079> and<00:40:52.319> inserts<00:40:52.760> it 00:40:52.950 --> 00:40:52.960 align:start position:0% belongs to this ecdsa key and inserts it 00:40:52.960 --> 00:40:55.150 align:start position:0% belongs to this ecdsa key and inserts it into<00:40:53.200> a<00:40:53.319> simple 00:40:55.150 --> 00:40:55.160 align:start position:0% into a simple 00:40:55.160 --> 00:40:59.390 align:start position:0% into a simple map<00:40:56.240> now<00:40:57.319> the<00:40:57.440> execution<00:40:57.920> layer<00:40:58.680> has<00:40:59.000> no 00:40:59.390 --> 00:40:59.400 align:start position:0% map now the execution layer has no 00:40:59.400 --> 00:41:01.069 align:start position:0% map now the execution layer has no native<00:41:00.040> way 00:41:01.069 --> 00:41:01.079 align:start position:0% native way 00:41:01.079 --> 00:41:04.349 align:start position:0% native way of<00:41:02.079> verifying<00:41:02.560> BLS<00:41:02.920> signatures<00:41:03.440> right<00:41:03.640> now 00:41:04.349 --> 00:41:04.359 align:start position:0% of verifying BLS signatures right now 00:41:04.359 --> 00:41:06.030 align:start position:0% of verifying BLS signatures right now but<00:41:04.560> very<00:41:04.760> soon<00:41:04.960> in<00:41:05.079> the<00:41:05.280> next<00:41:05.520> upgrade<00:41:05.880> the 00:41:06.030 --> 00:41:06.040 align:start position:0% but very soon in the next upgrade the 00:41:06.040 --> 00:41:08.109 align:start position:0% but very soon in the next upgrade the pectra<00:41:06.359> upgrade<00:41:07.040> a<00:41:07.200> new<00:41:07.400> pre-compile<00:41:08.000> is 00:41:08.109 --> 00:41:08.119 align:start position:0% pectra upgrade a new pre-compile is 00:41:08.119 --> 00:41:11.710 align:start position:0% pectra upgrade a new pre-compile is being<00:41:08.480> added<00:41:09.480> via<00:41:09.800> EIP<00:41:10.400> 2537<00:41:11.400> that's<00:41:11.560> where 00:41:11.710 --> 00:41:11.720 align:start position:0% being added via EIP 2537 that's where 00:41:11.720 --> 00:41:14.670 align:start position:0% being added via EIP 2537 that's where all<00:41:11.839> the<00:41:12.200> discussion<00:41:13.200> uh<00:41:13.560> has<00:41:13.760> happened<00:41:14.480> and 00:41:14.670 --> 00:41:14.680 align:start position:0% all the discussion uh has happened and 00:41:14.680 --> 00:41:16.510 align:start position:0% all the discussion uh has happened and this<00:41:14.839> pre-compile<00:41:15.599> or<00:41:15.760> a<00:41:15.920> set<00:41:16.079> of<00:41:16.240> pre- 00:41:16.510 --> 00:41:16.520 align:start position:0% this pre-compile or a set of pre- 00:41:16.520 --> 00:41:18.750 align:start position:0% this pre-compile or a set of pre- compiles<00:41:17.079> three<00:41:17.319> pre-<00:41:17.560> compiles<00:41:17.960> actually 00:41:18.750 --> 00:41:18.760 align:start position:0% compiles three pre- compiles actually 00:41:18.760 --> 00:41:21.150 align:start position:0% compiles three pre- compiles actually will<00:41:18.960> help<00:41:19.200> us<00:41:19.440> verify<00:41:19.880> BLS 00:41:21.150 --> 00:41:21.160 align:start position:0% will help us verify BLS 00:41:21.160 --> 00:41:23.390 align:start position:0% will help us verify BLS signatures<00:41:22.160> now<00:41:22.319> this<00:41:22.520> is<00:41:22.800> are<00:41:23.040> really 00:41:23.390 --> 00:41:23.400 align:start position:0% signatures now this is are really 00:41:23.400 --> 00:41:25.349 align:start position:0% signatures now this is are really expensive<00:41:24.000> because<00:41:24.319> for<00:41:24.680> verifying<00:41:25.200> one 00:41:25.349 --> 00:41:25.359 align:start position:0% expensive because for verifying one 00:41:25.359 --> 00:41:27.390 align:start position:0% expensive because for verifying one signature<00:41:25.839> we<00:41:25.920> need<00:41:26.079> to<00:41:26.200> spend<00:41:26.480> like<00:41:26.640> three 00:41:27.390 --> 00:41:27.400 align:start position:0% signature we need to spend like three 00:41:27.400 --> 00:41:29.950 align:start position:0% signature we need to spend like three 100K<00:41:27.920> units<00:41:28.200> of<00:41:28.400> gas<00:41:28.680> that's<00:41:28.960> really 00:41:29.950 --> 00:41:29.960 align:start position:0% 100K units of gas that's really 00:41:29.960 --> 00:41:33.150 align:start position:0% 100K units of gas that's really expensive<00:41:30.960> so<00:41:31.200> in<00:41:31.319> our<00:41:31.599> next<00:41:32.240> alter<00:41:32.920> in<00:41:33.000> our 00:41:33.150 --> 00:41:33.160 align:start position:0% expensive so in our next alter in our 00:41:33.160 --> 00:41:35.270 align:start position:0% expensive so in our next alter in our next<00:41:33.319> PC<00:41:33.839> we<00:41:34.160> are<00:41:34.400> actually<00:41:34.680> proposing<00:41:35.040> an 00:41:35.270 --> 00:41:35.280 align:start position:0% next PC we are actually proposing an 00:41:35.280 --> 00:41:37.829 align:start position:0% next PC we are actually proposing an alternative<00:41:35.960> where<00:41:36.800> in<00:41:36.920> the<00:41:37.040> case<00:41:37.200> of<00:41:37.359> BLS 00:41:37.829 --> 00:41:37.839 align:start position:0% alternative where in the case of BLS 00:41:37.839 --> 00:41:40.150 align:start position:0% alternative where in the case of BLS there's<00:41:38.160> a<00:41:38.359> great<00:41:38.640> feature<00:41:39.319> and<00:41:39.440> that's 00:41:40.150 --> 00:41:40.160 align:start position:0% there's a great feature and that's 00:41:40.160 --> 00:41:42.190 align:start position:0% there's a great feature and that's aggregation<00:41:41.160> so<00:41:41.319> if<00:41:41.400> you<00:41:41.520> have<00:41:41.720> thousand 00:41:42.190 --> 00:41:42.200 align:start position:0% aggregation so if you have thousand 00:41:42.200 --> 00:41:44.990 align:start position:0% aggregation so if you have thousand validators<00:41:43.200> what<00:41:43.400> you<00:41:43.480> can<00:41:43.640> do<00:41:43.839> is<00:41:44.440> you<00:41:44.560> can 00:41:44.990 --> 00:41:45.000 align:start position:0% validators what you can do is you can 00:41:45.000 --> 00:41:47.270 align:start position:0% validators what you can do is you can have<00:41:45.200> thousand<00:41:45.560> signatures<00:41:46.000> offchain<00:41:46.880> then 00:41:47.270 --> 00:41:47.280 align:start position:0% have thousand signatures offchain then 00:41:47.280 --> 00:41:49.190 align:start position:0% have thousand signatures offchain then add<00:41:47.560> all<00:41:47.680> of<00:41:47.880> these<00:41:48.119> signatures<00:41:48.640> up<00:41:48.920> it's 00:41:49.190 --> 00:41:49.200 align:start position:0% add all of these signatures up it's 00:41:49.200 --> 00:41:51.829 align:start position:0% add all of these signatures up it's basically<00:41:49.680> elliptic<00:41:50.160> curve<00:41:50.560> addition<00:41:51.560> you 00:41:51.829 --> 00:41:51.839 align:start position:0% basically elliptic curve addition you 00:41:51.839 --> 00:41:54.829 align:start position:0% basically elliptic curve addition you add<00:41:52.119> these<00:41:52.319> signatures<00:41:52.880> up<00:41:53.760> and<00:41:53.960> then<00:41:54.480> on<00:41:54.680> the 00:41:54.829 --> 00:41:54.839 align:start position:0% add these signatures up and then on the 00:41:54.839 --> 00:41:56.710 align:start position:0% add these signatures up and then on the contract<00:41:55.640> you<00:41:55.800> just<00:41:55.920> have<00:41:56.040> to<00:41:56.200> verify<00:41:56.560> one 00:41:56.710 --> 00:41:56.720 align:start position:0% contract you just have to verify one 00:41:56.720 --> 00:41:57.750 align:start position:0% contract you just have to verify one signature 00:41:57.750 --> 00:41:57.760 align:start position:0% signature 00:41:57.760 --> 00:42:01.349 align:start position:0% signature so<00:41:58.040> essentially<00:41:58.599> you<00:41:58.760> can<00:41:59.599> add<00:42:00.599> uh<00:42:01.119> like<00:42:01.240> you 00:42:01.349 --> 00:42:01.359 align:start position:0% so essentially you can add uh like you 00:42:01.359 --> 00:42:04.550 align:start position:0% so essentially you can add uh like you can<00:42:01.720> put<00:42:02.720> thousands<00:42:03.079> of<00:42:03.240> validators<00:42:03.839> in<00:42:04.040> your 00:42:04.550 --> 00:42:04.560 align:start position:0% can put thousands of validators in your 00:42:04.560 --> 00:42:07.790 align:start position:0% can put thousands of validators in your registry<00:42:05.520> via<00:42:05.880> just<00:42:06.079> one<00:42:06.319> signature<00:42:07.079> and<00:42:07.560> just 00:42:07.790 --> 00:42:07.800 align:start position:0% registry via just one signature and just 00:42:07.800 --> 00:42:10.069 align:start position:0% registry via just one signature and just a<00:42:07.920> bit<00:42:08.079> more<00:42:08.280> than<00:42:08.440> 300<00:42:08.880> gigas<00:42:09.800> which<00:42:09.920> is 00:42:10.069 --> 00:42:10.079 align:start position:0% a bit more than 300 gigas which is 00:42:10.079 --> 00:42:11.589 align:start position:0% a bit more than 300 gigas which is amazing<00:42:10.480> and<00:42:10.599> this<00:42:10.720> is<00:42:10.920> what<00:42:11.240> we<00:42:11.359> will 00:42:11.589 --> 00:42:11.599 align:start position:0% amazing and this is what we will 00:42:11.599 --> 00:42:13.270 align:start position:0% amazing and this is what we will potentially<00:42:12.000> be<00:42:12.160> putting<00:42:12.400> in<00:42:12.480> the<00:42:12.640> next 00:42:13.270 --> 00:42:13.280 align:start position:0% potentially be putting in the next 00:42:13.280 --> 00:42:15.950 align:start position:0% potentially be putting in the next version<00:42:14.280> but<00:42:14.440> yeah<00:42:14.640> right<00:42:14.800> now<00:42:15.040> it's<00:42:15.520> one<00:42:15.760> to 00:42:15.950 --> 00:42:15.960 align:start position:0% version but yeah right now it's one to 00:42:15.960 --> 00:42:18.030 align:start position:0% version but yeah right now it's one to one<00:42:16.200> single<00:42:16.560> address<00:42:17.200> single<00:42:17.520> signature 00:42:18.030 --> 00:42:18.040 align:start position:0% one single address single signature 00:42:18.040 --> 00:42:20.270 align:start position:0% one single address single signature every<00:42:18.200> single 00:42:20.270 --> 00:42:20.280 align:start position:0% every single 00:42:20.280 --> 00:42:22.910 align:start position:0% every single time<00:42:21.280> so<00:42:21.440> how<00:42:21.599> is<00:42:21.720> this<00:42:21.880> used<00:42:22.200> to<00:42:22.520> construct 00:42:22.910 --> 00:42:22.920 align:start position:0% time so how is this used to construct 00:42:22.920 --> 00:42:24.589 align:start position:0% time so how is this used to construct the<00:42:23.000> look<00:42:23.160> ahead<00:42:23.520> because<00:42:23.920> the<00:42:24.040> BLS<00:42:24.440> look 00:42:24.589 --> 00:42:24.599 align:start position:0% the look ahead because the BLS look 00:42:24.599 --> 00:42:26.069 align:start position:0% the look ahead because the BLS look ahead<00:42:24.880> is<00:42:25.000> absolutely<00:42:25.440> useless<00:42:25.839> on<00:42:25.960> the 00:42:26.069 --> 00:42:26.079 align:start position:0% ahead is absolutely useless on the 00:42:26.079 --> 00:42:28.109 align:start position:0% ahead is absolutely useless on the consent<00:42:26.480> that's<00:42:26.640> on<00:42:26.720> the<00:42:26.839> consent<00:42:27.440> layer<00:42:28.000> we 00:42:28.109 --> 00:42:28.119 align:start position:0% consent that's on the consent layer we 00:42:28.119 --> 00:42:30.109 align:start position:0% consent that's on the consent layer we need<00:42:28.319> an<00:42:28.520> ecdsa<00:42:29.280> look<00:42:29.480> ahead<00:42:29.800> on<00:42:29.960> the 00:42:30.109 --> 00:42:30.119 align:start position:0% need an ecdsa look ahead on the 00:42:30.119 --> 00:42:32.750 align:start position:0% need an ecdsa look ahead on the execution<00:42:30.640> layer<00:42:31.440> so<00:42:31.880> every<00:42:32.280> every<00:42:32.480> single 00:42:32.750 --> 00:42:32.760 align:start position:0% execution layer so every every single 00:42:32.760 --> 00:42:34.950 align:start position:0% execution layer so every every single time<00:42:32.920> we<00:42:33.040> know<00:42:33.240> that<00:42:33.400> only<00:42:33.720> this<00:42:33.880> ecdsa<00:42:34.680> is 00:42:34.950 --> 00:42:34.960 align:start position:0% time we know that only this ecdsa is 00:42:34.960 --> 00:42:37.190 align:start position:0% time we know that only this ecdsa is supposed<00:42:35.359> to<00:42:35.520> propose<00:42:36.119> no<00:42:36.280> other<00:42:36.480> ecdsa<00:42:37.079> can 00:42:37.190 --> 00:42:37.200 align:start position:0% supposed to propose no other ecdsa can 00:42:37.200 --> 00:42:38.470 align:start position:0% supposed to propose no other ecdsa can propose<00:42:37.480> an<00:42:37.599> L2 00:42:38.470 --> 00:42:38.480 align:start position:0% propose an L2 00:42:38.480 --> 00:42:40.870 align:start position:0% propose an L2 block<00:42:39.480> so<00:42:39.640> in<00:42:39.839> this<00:42:40.040> case<00:42:40.400> it's<00:42:40.559> kind<00:42:40.720> of 00:42:40.870 --> 00:42:40.880 align:start position:0% block so in this case it's kind of 00:42:40.880 --> 00:42:43.829 align:start position:0% block so in this case it's kind of simple<00:42:41.640> the<00:42:41.760> pre-comp<00:42:42.200> node<00:42:42.440> has<00:42:42.559> the<00:42:42.839> logic 00:42:43.829 --> 00:42:43.839 align:start position:0% simple the pre-comp node has the logic 00:42:43.839 --> 00:42:46.950 align:start position:0% simple the pre-comp node has the logic the<00:42:43.960> pre-com<00:42:44.440> node<00:42:44.760> can<00:42:45.319> take<00:42:45.480> a<00:42:45.680> look<00:42:46.079> at<00:42:46.800> the 00:42:46.950 --> 00:42:46.960 align:start position:0% the pre-com node can take a look at the 00:42:46.960 --> 00:42:48.510 align:start position:0% the pre-com node can take a look at the consensus<00:42:47.440> layer<00:42:47.680> because<00:42:47.839> the<00:42:47.920> pre-com<00:42:48.319> node 00:42:48.510 --> 00:42:48.520 align:start position:0% consensus layer because the pre-com node 00:42:48.520 --> 00:42:50.710 align:start position:0% consensus layer because the pre-com node is<00:42:49.400> has<00:42:49.559> the<00:42:49.680> view<00:42:49.880> of<00:42:50.040> both<00:42:50.200> the<00:42:50.319> execution 00:42:50.710 --> 00:42:50.720 align:start position:0% is has the view of both the execution 00:42:50.720 --> 00:42:52.870 align:start position:0% is has the view of both the execution layer<00:42:50.960> and<00:42:51.079> the<00:42:51.240> consensus<00:42:51.680> layer<00:42:52.599> so<00:42:52.760> the 00:42:52.870 --> 00:42:52.880 align:start position:0% layer and the consensus layer so the 00:42:52.880 --> 00:42:55.549 align:start position:0% layer and the consensus layer so the pre-com<00:42:53.319> node<00:42:53.599> pulls<00:42:54.359> all<00:42:54.640> the<00:42:54.920> proposal<00:42:55.400> from 00:42:55.549 --> 00:42:55.559 align:start position:0% pre-com node pulls all the proposal from 00:42:55.559 --> 00:42:59.150 align:start position:0% pre-com node pulls all the proposal from the<00:42:55.680> consensus<00:42:56.160> layer<00:42:56.720> for<00:42:56.960> the<00:42:57.280> next<00:42:58.160> Epoch 00:42:59.150 --> 00:42:59.160 align:start position:0% the consensus layer for the next Epoch 00:42:59.160 --> 00:43:02.270 align:start position:0% the consensus layer for the next Epoch then<00:42:59.319> it<00:42:59.599> fetches<00:43:00.280> the<00:43:00.480> associated<00:43:01.280> ecds<00:43:02.040> key 00:43:02.270 --> 00:43:02.280 align:start position:0% then it fetches the associated ecds key 00:43:02.280 --> 00:43:04.349 align:start position:0% then it fetches the associated ecds key from<00:43:02.920> the<00:43:03.079> pre-confirmation<00:43:03.559> registry 00:43:04.349 --> 00:43:04.359 align:start position:0% from the pre-confirmation registry 00:43:04.359 --> 00:43:07.150 align:start position:0% from the pre-confirmation registry because<00:43:04.720> we<00:43:04.880> have<00:43:05.319> the<00:43:05.480> BLS<00:43:05.880> to<00:43:06.119> ecdsa<00:43:06.720> mapping 00:43:07.150 --> 00:43:07.160 align:start position:0% because we have the BLS to ecdsa mapping 00:43:07.160 --> 00:43:10.109 align:start position:0% because we have the BLS to ecdsa mapping there<00:43:08.040> and<00:43:08.160> it<00:43:08.319> just<00:43:08.559> matches<00:43:08.920> it<00:43:09.240> okay<00:43:09.559> this 00:43:10.109 --> 00:43:10.119 align:start position:0% there and it just matches it okay this 00:43:10.119 --> 00:43:12.670 align:start position:0% there and it just matches it okay this this<00:43:10.319> BLS<00:43:11.119> for<00:43:11.400> for<00:43:11.520> the<00:43:11.640> next<00:43:11.800> slot<00:43:12.520> is 00:43:12.670 --> 00:43:12.680 align:start position:0% this BLS for for the next slot is 00:43:12.680 --> 00:43:14.549 align:start position:0% this BLS for for the next slot is belongs<00:43:12.960> to<00:43:13.160> this<00:43:13.280> ecdsa<00:43:13.960> This<00:43:14.079> one<00:43:14.240> belongs 00:43:14.549 --> 00:43:14.559 align:start position:0% belongs to this ecdsa This one belongs 00:43:14.559 --> 00:43:18.030 align:start position:0% belongs to this ecdsa This one belongs to<00:43:14.760> this<00:43:15.440> and<00:43:15.559> it<00:43:15.760> creates<00:43:16.520> the<00:43:16.680> entire<00:43:17.000> look 00:43:18.030 --> 00:43:18.040 align:start position:0% to this and it creates the entire look 00:43:18.040 --> 00:43:21.750 align:start position:0% to this and it creates the entire look ahead<00:43:19.040> now<00:43:19.200> in<00:43:19.319> our<00:43:19.599> design<00:43:19.960> we<00:43:20.359> have<00:43:21.359> assigned 00:43:21.750 --> 00:43:21.760 align:start position:0% ahead now in our design we have assigned 00:43:21.760 --> 00:43:23.750 align:start position:0% ahead now in our design we have assigned the<00:43:21.920> duty<00:43:22.480> to<00:43:22.720> push<00:43:22.920> the<00:43:23.079> look<00:43:23.280> ahead<00:43:23.559> of 00:43:23.750 --> 00:43:23.760 align:start position:0% the duty to push the look ahead of 00:43:23.760 --> 00:43:25.670 align:start position:0% the duty to push the look ahead of pushing<00:43:24.000> the<00:43:24.119> look<00:43:24.319> ahead<00:43:24.880> to<00:43:25.119> the<00:43:25.319> first 00:43:25.670 --> 00:43:25.680 align:start position:0% pushing the look ahead to the first 00:43:25.680 --> 00:43:28.829 align:start position:0% pushing the look ahead to the first precon<00:43:26.079> fer<00:43:26.559> of<00:43:26.800> every<00:43:27.240> Epoch<00:43:28.079> so<00:43:28.400> the<00:43:28.559> first 00:43:28.829 --> 00:43:28.839 align:start position:0% precon fer of every Epoch so the first 00:43:28.839 --> 00:43:30.870 align:start position:0% precon fer of every Epoch so the first prec<00:43:29.079> confer<00:43:29.440> of<00:43:29.880> current<00:43:30.200> Epoch<00:43:30.559> will<00:43:30.720> be 00:43:30.870 --> 00:43:30.880 align:start position:0% prec confer of current Epoch will be 00:43:30.880 --> 00:43:33.109 align:start position:0% prec confer of current Epoch will be pushing<00:43:31.599> the<00:43:32.000> the<00:43:32.079> look<00:43:32.240> ahead<00:43:32.520> for<00:43:32.680> the<00:43:32.800> next 00:43:33.109 --> 00:43:33.119 align:start position:0% pushing the the look ahead for the next 00:43:33.119 --> 00:43:35.589 align:start position:0% pushing the the look ahead for the next Epoch<00:43:34.119> and<00:43:34.440> they<00:43:34.559> are<00:43:34.680> basically<00:43:35.119> bounded<00:43:35.440> by 00:43:35.589 --> 00:43:35.599 align:start position:0% Epoch and they are basically bounded by 00:43:35.599 --> 00:43:38.750 align:start position:0% Epoch and they are basically bounded by this<00:43:35.720> Duty<00:43:36.040> they<00:43:36.200> must<00:43:36.520> do<00:43:36.720> it<00:43:37.359> if<00:43:37.640> they<00:43:38.079> well 00:43:38.750 --> 00:43:38.760 align:start position:0% this Duty they must do it if they well 00:43:38.760 --> 00:43:40.390 align:start position:0% this Duty they must do it if they well it<00:43:38.960> it<00:43:39.119> kind<00:43:39.280> of<00:43:39.440> there's<00:43:39.640> no<00:43:39.839> option<00:43:40.119> of<00:43:40.240> not 00:43:40.390 --> 00:43:40.400 align:start position:0% it it kind of there's no option of not 00:43:40.400 --> 00:43:42.230 align:start position:0% it it kind of there's no option of not doing<00:43:40.640> it<00:43:40.839> because<00:43:41.079> the<00:43:41.280> contract<00:43:41.800> expects 00:43:42.230 --> 00:43:42.240 align:start position:0% doing it because the contract expects 00:43:42.240 --> 00:43:46.270 align:start position:0% doing it because the contract expects you<00:43:42.640> to<00:43:42.839> provide 00:43:46.270 --> 00:43:46.280 align:start position:0% 00:43:46.280 --> 00:43:48.950 align:start position:0% that<00:43:47.280> and<00:43:47.440> this<00:43:47.559> is<00:43:47.760> what<00:43:47.920> a<00:43:48.119> simple<00:43:48.680> look 00:43:48.950 --> 00:43:48.960 align:start position:0% that and this is what a simple look 00:43:48.960 --> 00:43:51.390 align:start position:0% that and this is what a simple look ahead<00:43:49.599> like<00:43:49.800> like<00:43:50.200> one<00:43:50.359> of<00:43:50.480> the<00:43:50.599> nodes<00:43:51.160> in<00:43:51.280> the 00:43:51.390 --> 00:43:51.400 align:start position:0% ahead like like one of the nodes in the 00:43:51.400 --> 00:43:54.109 align:start position:0% ahead like like one of the nodes in the look<00:43:51.640> ahead<00:43:52.480> array<00:43:52.880> or<00:43:53.119> mapping<00:43:53.480> looks<00:43:53.760> like 00:43:54.109 --> 00:43:54.119 align:start position:0% look ahead array or mapping looks like 00:43:54.119 --> 00:43:56.390 align:start position:0% look ahead array or mapping looks like I'll<00:43:54.359> get<00:43:54.520> to<00:43:54.839> what<00:43:54.960> the<00:43:55.119> look<00:43:55.280> ahead<00:43:56.280> what 00:43:56.390 --> 00:43:56.400 align:start position:0% I'll get to what the look ahead what 00:43:56.400 --> 00:43:58.990 align:start position:0% I'll get to what the look ahead what data<00:43:56.599> structure<00:43:56.880> we<00:43:57.160> actually<00:43:57.680> use<00:43:58.680> but<00:43:58.839> in 00:43:58.990 --> 00:43:59.000 align:start position:0% data structure we actually use but in 00:43:59.000 --> 00:44:00.990 align:start position:0% data structure we actually use but in here<00:43:59.240> the<00:43:59.480> Tim<00:43:59.760> stamp<00:44:00.200> the<00:44:00.319> second<00:44:00.559> field<00:44:00.839> and 00:44:00.990 --> 00:44:01.000 align:start position:0% here the Tim stamp the second field and 00:44:01.000 --> 00:44:02.549 align:start position:0% here the Tim stamp the second field and the<00:44:01.079> fourth<00:44:01.319> field<00:44:01.599> makes<00:44:01.880> sense<00:44:02.200> the<00:44:02.319> time 00:44:02.549 --> 00:44:02.559 align:start position:0% the fourth field makes sense the time 00:44:02.559 --> 00:44:04.829 align:start position:0% the fourth field makes sense the time stamp<00:44:02.839> is<00:44:02.960> the<00:44:03.319> time<00:44:03.559> stamp<00:44:03.800> of<00:44:03.880> the<00:44:04.000> slot<00:44:04.720> and 00:44:04.829 --> 00:44:04.839 align:start position:0% stamp is the time stamp of the slot and 00:44:04.839 --> 00:44:07.510 align:start position:0% stamp is the time stamp of the slot and the<00:44:05.079> proner<00:44:05.559> is<00:44:05.920> whoever<00:44:06.319> is<00:44:06.920> supposed<00:44:07.280> to<00:44:07.359> be 00:44:07.510 --> 00:44:07.520 align:start position:0% the proner is whoever is supposed to be 00:44:07.520 --> 00:44:11.069 align:start position:0% the proner is whoever is supposed to be proning<00:44:08.119> in<00:44:08.240> that<00:44:08.400> slot<00:44:08.720> or<00:44:08.880> proposing<00:44:09.280> an<00:44:09.400> L2 00:44:11.069 --> 00:44:11.079 align:start position:0% proning in that slot or proposing an L2 00:44:11.079 --> 00:44:13.950 align:start position:0% proning in that slot or proposing an L2 block<00:44:12.079> we<00:44:12.240> have<00:44:12.400> another<00:44:12.640> field<00:44:13.200> fall<00:44:13.559> back 00:44:13.950 --> 00:44:13.960 align:start position:0% block we have another field fall back 00:44:13.960 --> 00:44:16.710 align:start position:0% block we have another field fall back and<00:44:14.160> previous<00:44:14.520> timestamp<00:44:15.040> now<00:44:15.160> what<00:44:15.280> are 00:44:16.710 --> 00:44:16.720 align:start position:0% and previous timestamp now what are 00:44:16.720 --> 00:44:19.790 align:start position:0% and previous timestamp now what are these<00:44:17.720> well<00:44:18.359> the<00:44:18.520> previous<00:44:18.920> timestamp<00:44:19.559> is 00:44:19.790 --> 00:44:19.800 align:start position:0% these well the previous timestamp is 00:44:19.800 --> 00:44:22.630 align:start position:0% these well the previous timestamp is just<00:44:20.520> a<00:44:20.680> link<00:44:21.160> to<00:44:21.559> the 00:44:22.630 --> 00:44:22.640 align:start position:0% just a link to the 00:44:22.640 --> 00:44:27.349 align:start position:0% just a link to the last<00:44:23.839> uh<00:44:24.839> look<00:44:25.119> ahead<00:44:25.440> nodes<00:44:26.079> Tim<00:44:26.359> stamp<00:44:27.200> what 00:44:27.349 --> 00:44:27.359 align:start position:0% last uh look ahead nodes Tim stamp what 00:44:27.359 --> 00:44:28.910 align:start position:0% last uh look ahead nodes Tim stamp what this<00:44:27.520> allow<00:44:27.800> us<00:44:27.920> to<00:44:28.040> do 00:44:28.910 --> 00:44:28.920 align:start position:0% this allow us to do 00:44:28.920 --> 00:44:32.670 align:start position:0% this allow us to do is<00:44:30.000> um<00:44:31.000> arrange<00:44:31.520> the<00:44:31.680> look<00:44:31.920> ahead<00:44:32.160> as<00:44:32.280> a<00:44:32.359> link 00:44:32.670 --> 00:44:32.680 align:start position:0% is um arrange the look ahead as a link 00:44:32.680 --> 00:44:34.470 align:start position:0% is um arrange the look ahead as a link list<00:44:32.960> within<00:44:33.240> the<00:44:33.400> contract<00:44:33.880> or<00:44:34.000> sort<00:44:34.280> of<00:44:34.400> a 00:44:34.470 --> 00:44:34.480 align:start position:0% list within the contract or sort of a 00:44:34.480 --> 00:44:37.710 align:start position:0% list within the contract or sort of a link<00:44:34.760> list<00:44:35.520> within<00:44:36.000> the<00:44:36.680> so<00:44:36.960> every<00:44:37.240> look<00:44:37.440> ahead 00:44:37.710 --> 00:44:37.720 align:start position:0% link list within the so every look ahead 00:44:37.720 --> 00:44:40.910 align:start position:0% link list within the so every look ahead structure<00:44:38.480> is<00:44:38.839> an<00:44:39.040> item<00:44:39.240> in<00:44:39.359> a<00:44:39.640> map<00:44:40.640> and<00:44:40.800> the 00:44:40.910 --> 00:44:40.920 align:start position:0% structure is an item in a map and the 00:44:40.920 --> 00:44:43.950 align:start position:0% structure is an item in a map and the previous<00:44:41.240> timestamp<00:44:42.079> just<00:44:43.079> points<00:44:43.440> to<00:44:43.680> one<00:44:43.839> of 00:44:43.950 --> 00:44:43.960 align:start position:0% previous timestamp just points to one of 00:44:43.960 --> 00:44:46.430 align:start position:0% previous timestamp just points to one of the<00:44:44.079> other<00:44:44.760> timestamps<00:44:45.760> what<00:44:45.920> this<00:44:46.040> allows<00:44:46.319> us 00:44:46.430 --> 00:44:46.440 align:start position:0% the other timestamps what this allows us 00:44:46.440 --> 00:44:49.030 align:start position:0% the other timestamps what this allows us to<00:44:46.559> do<00:44:46.760> is<00:44:46.920> have<00:44:47.119> advanced<00:44:47.520> proposals<00:44:48.040> because 00:44:49.030 --> 00:44:49.040 align:start position:0% to do is have advanced proposals because 00:44:49.040 --> 00:44:51.950 align:start position:0% to do is have advanced proposals because not<00:44:49.319> every<00:44:49.640> proposer<00:44:50.079> will<00:44:50.240> be<00:44:50.359> opting<00:44:50.720> in<00:44:51.599> and 00:44:51.950 --> 00:44:51.960 align:start position:0% not every proposer will be opting in and 00:44:51.960 --> 00:44:53.309 align:start position:0% not every proposer will be opting in and also<00:44:52.240> not<00:44:52.440> every<00:44:52.680> proposer<00:44:53.079> will<00:44:53.200> be 00:44:53.309 --> 00:44:53.319 align:start position:0% also not every proposer will be 00:44:53.319 --> 00:44:55.589 align:start position:0% also not every proposer will be registering<00:44:53.839> and<00:44:54.440> exposing<00:44:54.839> an<00:44:55.000> ecdsa 00:44:55.589 --> 00:44:55.599 align:start position:0% registering and exposing an ecdsa 00:44:55.599 --> 00:44:57.150 align:start position:0% registering and exposing an ecdsa address<00:44:55.880> some<00:44:56.000> are<00:44:56.200> just<00:44:56.359> not<00:44:56.520> interested<00:44:57.040> in 00:44:57.150 --> 00:44:57.160 align:start position:0% address some are just not interested in 00:44:57.160 --> 00:44:59.309 align:start position:0% address some are just not interested in preconfig<00:44:57.760> right<00:44:58.480> so<00:44:58.640> in<00:44:58.800> this<00:44:59.000> case<00:44:59.200> we 00:44:59.309 --> 00:44:59.319 align:start position:0% preconfig right so in this case we 00:44:59.319 --> 00:45:01.190 align:start position:0% preconfig right so in this case we cannot<00:44:59.640> just<00:44:59.839> have<00:45:00.000> an<00:45:00.280> entire<00:45:00.640> Epoch<00:45:01.040> be 00:45:01.190 --> 00:45:01.200 align:start position:0% cannot just have an entire Epoch be 00:45:01.200 --> 00:45:03.750 align:start position:0% cannot just have an entire Epoch be empty<00:45:01.559> if<00:45:01.720> there<00:45:01.800> are<00:45:01.920> no<00:45:02.119> pre-con<00:45:02.480> fers<00:45:03.160> or<00:45:03.520> if 00:45:03.750 --> 00:45:03.760 align:start position:0% empty if there are no pre-con fers or if 00:45:03.760 --> 00:45:05.589 align:start position:0% empty if there are no pre-con fers or if there<00:45:03.880> are<00:45:04.040> very<00:45:04.200> few<00:45:04.400> pre-con<00:45:04.720> fers<00:45:05.359> we<00:45:05.480> need 00:45:05.589 --> 00:45:05.599 align:start position:0% there are very few pre-con fers we need 00:45:05.599 --> 00:45:07.309 align:start position:0% there are very few pre-con fers we need to<00:45:05.760> do<00:45:05.920> something<00:45:06.200> in<00:45:06.319> the<00:45:06.400> empty 00:45:07.309 --> 00:45:07.319 align:start position:0% to do something in the empty 00:45:07.319 --> 00:45:09.790 align:start position:0% to do something in the empty slots<00:45:08.319> and<00:45:08.520> what<00:45:08.640> we<00:45:08.760> do<00:45:08.960> is<00:45:09.079> we<00:45:09.240> allow<00:45:09.520> the 00:45:09.790 --> 00:45:09.800 align:start position:0% slots and what we do is we allow the 00:45:09.800 --> 00:45:12.390 align:start position:0% slots and what we do is we allow the next<00:45:10.119> chosen<00:45:10.520> preuner<00:45:11.359> to<00:45:11.559> precom<00:45:12.000> in 00:45:12.390 --> 00:45:12.400 align:start position:0% next chosen preuner to precom in 00:45:12.400 --> 00:45:15.390 align:start position:0% next chosen preuner to precom in advanced<00:45:13.400> and<00:45:13.599> because<00:45:13.839> of<00:45:14.040> this<00:45:14.319> link<00:45:15.119> we<00:45:15.240> can 00:45:15.390 --> 00:45:15.400 align:start position:0% advanced and because of this link we can 00:45:15.400 --> 00:45:17.390 align:start position:0% advanced and because of this link we can do<00:45:15.559> that<00:45:15.720> with<00:45:15.800> a<00:45:15.960> simple<00:45:16.280> check<00:45:16.760> a<00:45:16.960> a<00:45:17.079> simple 00:45:17.390 --> 00:45:17.400 align:start position:0% do that with a simple check a a simple 00:45:17.400 --> 00:45:19.510 align:start position:0% do that with a simple check a a simple if<00:45:17.839> condition<00:45:18.680> that's<00:45:18.880> why<00:45:19.000> in<00:45:19.160> here<00:45:19.280> you<00:45:19.400> can 00:45:19.510 --> 00:45:19.520 align:start position:0% if condition that's why in here you can 00:45:19.520 --> 00:45:23.670 align:start position:0% if condition that's why in here you can see<00:45:20.200> that<00:45:20.720> P2<00:45:21.240> pre-<00:45:21.480> confer<00:45:21.800> 2<00:45:22.480> can<00:45:22.720> precom<00:45:23.559> in 00:45:23.670 --> 00:45:23.680 align:start position:0% see that P2 pre- confer 2 can precom in 00:45:23.680 --> 00:45:27.390 align:start position:0% see that P2 pre- confer 2 can precom in the<00:45:23.839> second<00:45:24.119> and<00:45:24.280> third<00:45:24.559> slot<00:45:25.280> already<00:45:26.280> and<00:45:26.480> P3 00:45:27.390 --> 00:45:27.400 align:start position:0% the second and third slot already and P3 00:45:27.400 --> 00:45:30.630 align:start position:0% the second and third slot already and P3 can<00:45:27.640> precom<00:45:28.520> in<00:45:28.760> three<00:45:28.960> slots<00:45:29.319> in<00:45:29.640> advanced 00:45:30.630 --> 00:45:30.640 align:start position:0% can precom in three slots in advanced 00:45:30.640 --> 00:45:32.150 align:start position:0% can precom in three slots in advanced that<00:45:30.760> is<00:45:30.920> made<00:45:31.160> possible<00:45:31.559> because<00:45:31.760> of<00:45:31.920> this 00:45:32.150 --> 00:45:32.160 align:start position:0% that is made possible because of this 00:45:32.160 --> 00:45:35.510 align:start position:0% that is made possible because of this linkless 00:45:35.510 --> 00:45:35.520 align:start position:0% 00:45:35.520 --> 00:45:38.870 align:start position:0% design<00:45:36.599> finally<00:45:37.599> if<00:45:37.800> we<00:45:38.000> have<00:45:38.200> an<00:45:38.359> Epoch<00:45:38.760> where 00:45:38.870 --> 00:45:38.880 align:start position:0% design finally if we have an Epoch where 00:45:38.880 --> 00:45:40.750 align:start position:0% design finally if we have an Epoch where there<00:45:39.000> are<00:45:39.240> no<00:45:39.480> prec<00:45:39.720> confers<00:45:40.119> at<00:45:40.240> all<00:45:40.640> and 00:45:40.750 --> 00:45:40.760 align:start position:0% there are no prec confers at all and 00:45:40.760 --> 00:45:42.750 align:start position:0% there are no prec confers at all and that's<00:45:41.000> very<00:45:41.200> much<00:45:41.440> possible<00:45:41.800> if<00:45:42.040> no<00:45:42.200> one<00:45:42.559> none 00:45:42.750 --> 00:45:42.760 align:start position:0% that's very much possible if no one none 00:45:42.760 --> 00:45:45.309 align:start position:0% that's very much possible if no one none of<00:45:42.960> the<00:45:43.160> proposers<00:45:43.599> in<00:45:43.839> that<00:45:44.680> uh<00:45:44.800> Epoch<00:45:45.200> has 00:45:45.309 --> 00:45:45.319 align:start position:0% of the proposers in that uh Epoch has 00:45:45.319 --> 00:45:47.230 align:start position:0% of the proposers in that uh Epoch has opted<00:45:45.599> in<00:45:45.880> we<00:45:46.000> don't<00:45:46.240> have<00:45:46.440> anyone<00:45:46.800> as<00:45:46.920> a<00:45:47.000> pre- 00:45:47.230 --> 00:45:47.240 align:start position:0% opted in we don't have anyone as a pre- 00:45:47.240 --> 00:45:49.750 align:start position:0% opted in we don't have anyone as a pre- confirm<00:45:48.119> then<00:45:48.280> we<00:45:48.440> have<00:45:48.559> to<00:45:48.720> select<00:45:49.079> someone 00:45:49.750 --> 00:45:49.760 align:start position:0% confirm then we have to select someone 00:45:49.760 --> 00:45:51.990 align:start position:0% confirm then we have to select someone randomly<00:45:50.760> and<00:45:51.000> that's<00:45:51.160> a<00:45:51.359> very<00:45:51.640> simple 00:45:51.990 --> 00:45:52.000 align:start position:0% randomly and that's a very simple 00:45:52.000 --> 00:45:53.910 align:start position:0% randomly and that's a very simple selection<00:45:52.960> like<00:45:53.119> we<00:45:53.280> need<00:45:53.440> a<00:45:53.520> source<00:45:53.760> of 00:45:53.910 --> 00:45:53.920 align:start position:0% selection like we need a source of 00:45:53.920 --> 00:45:56.270 align:start position:0% selection like we need a source of Randomness<00:45:54.520> and<00:45:54.760> with<00:45:55.240> apply<00:45:55.599> like<00:45:55.839> simp 00:45:56.270 --> 00:45:56.280 align:start position:0% Randomness and with apply like simp 00:45:56.280 --> 00:45:59.109 align:start position:0% Randomness and with apply like simp simple<00:45:56.960> modulus<00:45:57.839> to<00:45:58.200> select<00:45:58.680> one<00:45:58.800> of<00:45:58.960> the 00:45:59.109 --> 00:45:59.119 align:start position:0% simple modulus to select one of the 00:45:59.119 --> 00:46:01.390 align:start position:0% simple modulus to select one of the indices<00:46:00.079> of<00:46:00.319> who<00:46:00.520> is<00:46:00.760> exactly<00:46:01.079> going<00:46:01.200> to<00:46:01.319> be 00:46:01.390 --> 00:46:01.400 align:start position:0% indices of who is exactly going to be 00:46:01.400 --> 00:46:03.750 align:start position:0% indices of who is exactly going to be the<00:46:01.520> proner<00:46:02.040> from<00:46:02.119> the<00:46:02.480> registry<00:46:03.480> and<00:46:03.599> the 00:46:03.750 --> 00:46:03.760 align:start position:0% the proner from the registry and the 00:46:03.760 --> 00:46:05.190 align:start position:0% the proner from the registry and the source<00:46:04.040> of<00:46:04.240> Randomness<00:46:04.720> comes<00:46:04.960> from<00:46:05.119> the 00:46:05.190 --> 00:46:05.200 align:start position:0% source of Randomness comes from the 00:46:05.200 --> 00:46:09.230 align:start position:0% source of Randomness comes from the beacon<00:46:05.480> root<00:46:05.800> contract<00:46:06.800> so<00:46:07.079> we<00:46:08.040> uh<00:46:08.559> as<00:46:08.760> far<00:46:08.960> as 00:46:09.230 --> 00:46:09.240 align:start position:0% beacon root contract so we uh as far as 00:46:09.240 --> 00:46:11.549 align:start position:0% beacon root contract so we uh as far as as<00:46:09.359> far<00:46:09.520> as<00:46:09.599> I<00:46:09.720> remember<00:46:10.119> we<00:46:10.319> basically<00:46:11.200> end<00:46:11.400> up 00:46:11.549 --> 00:46:11.559 align:start position:0% as far as I remember we basically end up 00:46:11.559 --> 00:46:14.870 align:start position:0% as far as I remember we basically end up choosing<00:46:12.559> the<00:46:12.680> beacon<00:46:13.079> route<00:46:13.720> of<00:46:14.079> the<00:46:14.559> first 00:46:14.870 --> 00:46:14.880 align:start position:0% choosing the beacon route of the first 00:46:14.880 --> 00:46:17.150 align:start position:0% choosing the beacon route of the first block<00:46:15.240> in<00:46:15.359> the<00:46:15.559> last<00:46:15.839> Epoch<00:46:16.599> because<00:46:17.000> this 00:46:17.150 --> 00:46:17.160 align:start position:0% block in the last Epoch because this 00:46:17.160 --> 00:46:19.309 align:start position:0% block in the last Epoch because this gives<00:46:17.319> us<00:46:17.480> a<00:46:17.680> pre<00:46:17.880> a<00:46:18.000> deterministic<00:46:18.880> idea<00:46:19.160> of 00:46:19.309 --> 00:46:19.319 align:start position:0% gives us a pre a deterministic idea of 00:46:19.319 --> 00:46:21.390 align:start position:0% gives us a pre a deterministic idea of who's<00:46:19.520> going<00:46:19.640> to<00:46:19.760> be<00:46:19.960> the<00:46:20.079> random<00:46:20.359> preuner<00:46:21.240> in 00:46:21.390 --> 00:46:21.400 align:start position:0% who's going to be the random preuner in 00:46:21.400 --> 00:46:23.710 align:start position:0% who's going to be the random preuner in the<00:46:21.559> next<00:46:21.760> deok<00:46:22.640> so<00:46:22.800> we<00:46:22.920> use<00:46:23.119> that<00:46:23.319> as<00:46:23.400> a<00:46:23.520> source 00:46:23.710 --> 00:46:23.720 align:start position:0% the next deok so we use that as a source 00:46:23.720 --> 00:46:25.870 align:start position:0% the next deok so we use that as a source of<00:46:23.880> Randomness<00:46:24.480> and<00:46:24.599> we<00:46:24.760> just<00:46:24.880> use<00:46:25.200> that<00:46:25.359> to 00:46:25.870 --> 00:46:25.880 align:start position:0% of Randomness and we just use that to 00:46:25.880 --> 00:46:28.109 align:start position:0% of Randomness and we just use that to pick<00:46:26.079> out<00:46:26.200> a<00:46:26.319> pre<00:46:26.520> confir 00:46:28.109 --> 00:46:28.119 align:start position:0% pick out a pre confir 00:46:28.119 --> 00:46:29.790 align:start position:0% pick out a pre confir and<00:46:28.359> this<00:46:28.520> fallback<00:46:28.960> pre-<00:46:29.160> coner<00:46:29.480> has<00:46:29.599> an 00:46:29.790 --> 00:46:29.800 align:start position:0% and this fallback pre- coner has an 00:46:29.800 --> 00:46:32.870 align:start position:0% and this fallback pre- coner has an advantage<00:46:30.359> and<00:46:30.599> that<00:46:30.920> is<00:46:31.559> it<00:46:31.720> can<00:46:32.000> preon<00:46:32.559> in 00:46:32.870 --> 00:46:32.880 align:start position:0% advantage and that is it can preon in 00:46:32.880 --> 00:46:35.069 align:start position:0% advantage and that is it can preon in every<00:46:33.200> single<00:46:33.559> slot<00:46:34.079> of<00:46:34.240> this<00:46:34.400> Epoch<00:46:34.800> because 00:46:35.069 --> 00:46:35.079 align:start position:0% every single slot of this Epoch because 00:46:35.079 --> 00:46:36.870 align:start position:0% every single slot of this Epoch because no<00:46:35.160> one<00:46:35.359> else<00:46:35.599> is<00:46:35.760> there<00:46:35.880> to 00:46:36.870 --> 00:46:36.880 align:start position:0% no one else is there to 00:46:36.880 --> 00:46:50.069 align:start position:0% no one else is there to precom 00:46:50.069 --> 00:46:50.079 align:start position:0% 00:46:50.079 --> 00:46:52.790 align:start position:0% yeah 00:46:52.790 --> 00:46:52.800 align:start position:0% yeah 00:46:52.800 --> 00:46:54.349 align:start position:0% yeah uh 00:46:54.349 --> 00:46:54.359 align:start position:0% uh 00:46:54.359 --> 00:47:00.430 align:start position:0% uh notos<00:46:55.359> you're<00:46:55.520> not<00:46:55.920> to 00:47:00.430 --> 00:47:00.440 align:start position:0% 00:47:00.440 --> 00:47:01.950 align:start position:0% in<00:47:00.640> six 00:47:01.950 --> 00:47:01.960 align:start position:0% in six 00:47:01.960 --> 00:47:04.349 align:start position:0% in six months<00:47:02.960> well<00:47:03.119> but<00:47:03.359> we<00:47:03.480> won't<00:47:03.680> be<00:47:03.800> stopping<00:47:04.160> for 00:47:04.349 --> 00:47:04.359 align:start position:0% months well but we won't be stopping for 00:47:04.359 --> 00:47:06.910 align:start position:0% months well but we won't be stopping for six<00:47:04.599> stopping<00:47:04.960> the<00:47:05.079> system<00:47:05.319> for<00:47:05.480> six<00:47:05.720> months 00:47:06.910 --> 00:47:06.920 align:start position:0% six stopping the system for six months 00:47:06.920 --> 00:47:11.950 align:start position:0% six stopping the system for six months right<00:47:07.920> yeah<00:47:08.520> so<00:47:09.520> I<00:47:09.640> can<00:47:10.319> uh<00:47:10.720> get<00:47:10.960> in<00:47:11.160> here<00:47:11.559> I 00:47:11.950 --> 00:47:11.960 align:start position:0% right yeah so I can uh get in here I 00:47:11.960 --> 00:47:13.990 align:start position:0% right yeah so I can uh get in here I understand<00:47:12.119> the<00:47:12.319> question<00:47:13.079> um<00:47:13.520> so<00:47:13.760> you're 00:47:13.990 --> 00:47:14.000 align:start position:0% understand the question um so you're 00:47:14.000 --> 00:47:16.870 align:start position:0% understand the question um so you're asking<00:47:14.400> is<00:47:15.000> since<00:47:15.480> the<00:47:15.920> pre<00:47:16.200> comfor<00:47:16.559> does<00:47:16.680> not 00:47:16.870 --> 00:47:16.880 align:start position:0% asking is since the pre comfor does not 00:47:16.880 --> 00:47:18.950 align:start position:0% asking is since the pre comfor does not have<00:47:17.040> the<00:47:17.200> right<00:47:17.440> to<00:47:17.760> pre<00:47:18.119> uh<00:47:18.240> to<00:47:18.480> propose<00:47:18.839> a 00:47:18.950 --> 00:47:18.960 align:start position:0% have the right to pre uh to propose a 00:47:18.960 --> 00:47:21.950 align:start position:0% have the right to pre uh to propose a block<00:47:19.400> in<00:47:19.520> the<00:47:19.680> next<00:47:20.000> Epoch<00:47:20.480> for<00:47:20.800> example<00:47:21.800> and 00:47:21.950 --> 00:47:21.960 align:start position:0% block in the next Epoch for example and 00:47:21.960 --> 00:47:25.270 align:start position:0% block in the next Epoch for example and we<00:47:22.079> chose<00:47:22.359> it<00:47:22.640> at<00:47:23.040> random<00:47:24.040> um<00:47:24.240> how<00:47:24.400> will<00:47:24.559> it<00:47:24.760> be 00:47:25.270 --> 00:47:25.280 align:start position:0% we chose it at random um how will it be 00:47:25.280 --> 00:47:28.309 align:start position:0% we chose it at random um how will it be able<00:47:25.559> to<00:47:25.760> honor<00:47:26.160> these<00:47:26.359> preon 00:47:28.309 --> 00:47:28.319 align:start position:0% able to honor these preon 00:47:28.319 --> 00:47:30.829 align:start position:0% able to honor these preon and<00:47:28.839> the<00:47:28.960> answer<00:47:29.240> to<00:47:29.440> this<00:47:29.640> question<00:47:29.960> is<00:47:30.240> that 00:47:30.829 --> 00:47:30.839 align:start position:0% and the answer to this question is that 00:47:30.839 --> 00:47:32.430 align:start position:0% and the answer to this question is that it<00:47:31.040> might<00:47:31.280> not<00:47:31.480> be<00:47:31.640> able<00:47:31.880> to<00:47:32.040> honor<00:47:32.319> the 00:47:32.430 --> 00:47:32.440 align:start position:0% it might not be able to honor the 00:47:32.440 --> 00:47:33.510 align:start position:0% it might not be able to honor the pre-confirmation 00:47:33.510 --> 00:47:33.520 align:start position:0% pre-confirmation 00:47:33.520 --> 00:47:37.230 align:start position:0% pre-confirmation but<00:47:34.520> uh<00:47:35.280> it<00:47:35.520> will<00:47:35.800> not<00:47:36.000> be<00:47:36.160> slashed<00:47:36.760> if<00:47:36.880> it<00:47:37.040> does 00:47:37.230 --> 00:47:37.240 align:start position:0% but uh it will not be slashed if it does 00:47:37.240 --> 00:47:39.030 align:start position:0% but uh it will not be slashed if it does not<00:47:37.400> honor<00:47:37.800> them<00:47:38.079> in<00:47:38.240> this<00:47:38.440> case<00:47:38.680> because<00:47:38.920> it's 00:47:39.030 --> 00:47:39.040 align:start position:0% not honor them in this case because it's 00:47:39.040 --> 00:47:43.109 align:start position:0% not honor them in this case because it's a<00:47:39.240> random<00:47:39.680> picked<00:47:40.000> pre<00:47:40.440> confer<00:47:41.440> and<00:47:42.000> also<00:47:43.000> we 00:47:43.109 --> 00:47:43.119 align:start position:0% a random picked pre confer and also we 00:47:43.119 --> 00:47:44.750 align:start position:0% a random picked pre confer and also we thought<00:47:43.359> about<00:47:43.599> this<00:47:43.800> like<00:47:44.119> okay<00:47:44.359> maybe<00:47:44.599> it 00:47:44.750 --> 00:47:44.760 align:start position:0% thought about this like okay maybe it 00:47:44.760 --> 00:47:46.190 align:start position:0% thought about this like okay maybe it shouldn't<00:47:45.119> be<00:47:45.319> providing<00:47:45.720> pre-confirmation 00:47:46.190 --> 00:47:46.200 align:start position:0% shouldn't be providing pre-confirmation 00:47:46.200 --> 00:47:49.230 align:start position:0% shouldn't be providing pre-confirmation but<00:47:46.680> this<00:47:46.839> would<00:47:47.280> be<00:47:47.480> a<00:47:47.640> very<00:47:47.839> bad<00:47:48.079> ux<00:47:48.800> so<00:47:48.960> we' 00:47:49.230 --> 00:47:49.240 align:start position:0% but this would be a very bad ux so we' 00:47:49.240 --> 00:47:50.549 align:start position:0% but this would be a very bad ux so we' provide<00:47:49.520> the<00:47:49.640> pre-confirmation<00:47:50.040> we<00:47:50.440> would 00:47:50.549 --> 00:47:50.559 align:start position:0% provide the pre-confirmation we would 00:47:50.559 --> 00:47:54.069 align:start position:0% provide the pre-confirmation we would send<00:47:50.760> them<00:47:50.960> in<00:47:51.079> the<00:47:51.200> P2P<00:47:52.160> on<00:47:52.480> on<00:47:52.960> on<00:47:53.520> um<00:47:53.760> on<00:47:53.920> the 00:47:54.069 --> 00:47:54.079 align:start position:0% send them in the P2P on on on um on the 00:47:54.079 --> 00:47:56.510 align:start position:0% send them in the P2P on on on um on the M<00:47:54.400> Pool<00:47:55.280> and<00:47:55.480> potentially<00:47:55.920> someone<00:47:56.160> will<00:47:56.359> pick 00:47:56.510 --> 00:47:56.520 align:start position:0% M Pool and potentially someone will pick 00:47:56.520 --> 00:47:59.190 align:start position:0% M Pool and potentially someone will pick them<00:47:56.640> up<00:47:56.920> and<00:47:57.040> include<00:47:57.440> them<00:47:57.720> if<00:47:58.040> the<00:47:58.760> if<00:47:59.000> the 00:47:59.190 --> 00:47:59.200 align:start position:0% them up and include them if the if the 00:47:59.200 --> 00:48:02.309 align:start position:0% them up and include them if the if the if<00:47:59.440> the<00:47:59.720> if<00:47:59.880> the<00:48:00.000> fee<00:48:00.319> is<00:48:00.720> right<00:48:01.720> um<00:48:01.960> and<00:48:02.119> this 00:48:02.309 --> 00:48:02.319 align:start position:0% if the if the fee is right um and this 00:48:02.319 --> 00:48:04.190 align:start position:0% if the if the fee is right um and this was<00:48:02.559> like<00:48:02.760> the<00:48:03.000> mechanism<00:48:03.520> that<00:48:03.640> we<00:48:03.760> wanted<00:48:04.040> to 00:48:04.190 --> 00:48:04.200 align:start position:0% was like the mechanism that we wanted to 00:48:04.200 --> 00:48:07.790 align:start position:0% was like the mechanism that we wanted to do<00:48:04.839> in<00:48:05.079> the<00:48:05.400> be<00:48:05.760> so<00:48:06.599> um<00:48:06.839> what<00:48:07.040> Tao<00:48:07.359> is<00:48:07.480> doing 00:48:07.790 --> 00:48:07.800 align:start position:0% do in the be so um what Tao is doing 00:48:07.800 --> 00:48:10.390 align:start position:0% do in the be so um what Tao is doing also<00:48:08.079> is<00:48:08.280> that<00:48:08.720> they're<00:48:09.720> they're<00:48:10.040> they're 00:48:10.390 --> 00:48:10.400 align:start position:0% also is that they're they're they're 00:48:10.400 --> 00:48:12.549 align:start position:0% also is that they're they're they're they're<00:48:10.599> using<00:48:11.000> this<00:48:11.119> fullback<00:48:11.720> mechanism<00:48:12.359> to 00:48:12.549 --> 00:48:12.559 align:start position:0% they're using this fullback mechanism to 00:48:12.559 --> 00:48:14.790 align:start position:0% they're using this fullback mechanism to say<00:48:13.040> okay<00:48:13.440> if<00:48:13.559> there<00:48:13.680> is<00:48:13.800> a<00:48:13.920> no<00:48:14.079> a<00:48:14.240> promer 00:48:14.790 --> 00:48:14.800 align:start position:0% say okay if there is a no a promer 00:48:14.800 --> 00:48:17.109 align:start position:0% say okay if there is a no a promer registered<00:48:15.280> in<00:48:15.440> the<00:48:15.559> next<00:48:15.760> Epoch<00:48:16.559> then<00:48:16.800> we<00:48:16.920> are 00:48:17.109 --> 00:48:17.119 align:start position:0% registered in the next Epoch then we are 00:48:17.119 --> 00:48:19.549 align:start position:0% registered in the next Epoch then we are going<00:48:17.240> to<00:48:17.440> propose<00:48:17.920> just<00:48:18.040> to<00:48:18.240> keep<00:48:18.599> the<00:48:19.240> the 00:48:19.549 --> 00:48:19.559 align:start position:0% going to propose just to keep the the 00:48:19.559 --> 00:48:23.030 align:start position:0% going to propose just to keep the the the<00:48:19.720> liveness<00:48:20.319> of<00:48:20.640> the<00:48:20.920> of<00:48:21.079> the<00:48:21.319> chain<00:48:22.319> um<00:48:22.880> and 00:48:23.030 --> 00:48:23.040 align:start position:0% the liveness of the of the chain um and 00:48:23.040 --> 00:48:24.549 align:start position:0% the liveness of the of the chain um and of<00:48:23.160> course<00:48:23.440> this<00:48:23.640> proposal<00:48:24.040> will<00:48:24.200> go<00:48:24.319> to<00:48:24.440> the 00:48:24.549 --> 00:48:24.559 align:start position:0% of course this proposal will go to the 00:48:24.559 --> 00:48:26.390 align:start position:0% of course this proposal will go to the mle<00:48:25.079> and<00:48:25.240> someone<00:48:25.520> will<00:48:25.680> pick<00:48:25.839> it<00:48:25.960> up<00:48:26.160> but<00:48:26.280> if 00:48:26.390 --> 00:48:26.400 align:start position:0% mle and someone will pick it up but if 00:48:26.400 --> 00:48:29.309 align:start position:0% mle and someone will pick it up but if someone<00:48:26.800> intentionally<00:48:27.400> is<00:48:28.040> censoring<00:48:29.040> uh 00:48:29.309 --> 00:48:29.319 align:start position:0% someone intentionally is censoring uh 00:48:29.319 --> 00:48:31.990 align:start position:0% someone intentionally is censoring uh these<00:48:30.000> uh<00:48:30.200> transactions<00:48:31.200> and<00:48:31.400> there<00:48:31.520> is<00:48:31.720> no 00:48:31.990 --> 00:48:32.000 align:start position:0% these uh transactions and there is no 00:48:32.000 --> 00:48:33.589 align:start position:0% these uh transactions and there is no mechanism<00:48:32.520> to<00:48:32.680> force<00:48:32.960> the<00:48:33.079> builders<00:48:33.440> to 00:48:33.589 --> 00:48:33.599 align:start position:0% mechanism to force the builders to 00:48:33.599 --> 00:48:36.349 align:start position:0% mechanism to force the builders to include<00:48:34.000> them<00:48:34.599> then<00:48:35.440> they<00:48:35.559> will<00:48:35.839> potentially 00:48:36.349 --> 00:48:36.359 align:start position:0% include them then they will potentially 00:48:36.359 --> 00:48:39.670 align:start position:0% include them then they will potentially not<00:48:36.640> be<00:48:36.960> embedded<00:48:37.960> uh<00:48:38.079> in<00:48:38.319> time 00:48:39.670 --> 00:48:39.680 align:start position:0% not be embedded uh in time 00:48:39.680 --> 00:48:44.109 align:start position:0% not be embedded uh in time yeah<00:48:40.680> thank<00:48:40.839> you 00:48:44.109 --> 00:48:44.119 align:start position:0% 00:48:44.119 --> 00:48:46.589 align:start position:0% Ed<00:48:45.119> and<00:48:45.280> one<00:48:45.480> thing<00:48:45.640> to<00:48:45.800> not<00:48:46.040> is<00:48:46.240> that 00:48:46.589 --> 00:48:46.599 align:start position:0% Ed and one thing to not is that 00:48:46.599 --> 00:48:48.630 align:start position:0% Ed and one thing to not is that throughout<00:48:47.079> this<00:48:47.680> POC<00:48:48.119> we<00:48:48.240> have<00:48:48.400> never 00:48:48.630 --> 00:48:48.640 align:start position:0% throughout this POC we have never 00:48:48.640 --> 00:48:50.750 align:start position:0% throughout this POC we have never touched<00:48:49.040> the<00:48:49.160> Tao<00:48:49.559> contracts<00:48:50.359> although 00:48:50.750 --> 00:48:50.760 align:start position:0% touched the Tao contracts although 00:48:50.760 --> 00:48:53.430 align:start position:0% touched the Tao contracts although eventually<00:48:51.200> we<00:48:51.400> might<00:48:52.040> to<00:48:52.440> add<00:48:52.640> that<00:48:52.799> delayed 00:48:53.430 --> 00:48:53.440 align:start position:0% eventually we might to add that delayed 00:48:53.440 --> 00:48:56.030 align:start position:0% eventually we might to add that delayed inbox<00:48:54.440> but<00:48:54.599> in<00:48:54.799> here<00:48:55.040> we<00:48:55.160> have<00:48:55.400> tried<00:48:55.680> to<00:48:55.839> not 00:48:56.030 --> 00:48:56.040 align:start position:0% inbox but in here we have tried to not 00:48:56.040 --> 00:48:58.390 align:start position:0% inbox but in here we have tried to not mess<00:48:56.319> around<00:48:56.520> with<00:48:56.760> The<00:48:56.880> Tao<00:48:57.160> contract<00:48:57.760> and 00:48:58.390 --> 00:48:58.400 align:start position:0% mess around with The Tao contract and 00:48:58.400 --> 00:49:01.190 align:start position:0% mess around with The Tao contract and what<00:48:58.680> our<00:48:58.920> task<00:48:59.160> manager<00:48:59.520> does<00:48:59.760> is<00:49:00.160> it<00:49:00.359> simply 00:49:01.190 --> 00:49:01.200 align:start position:0% what our task manager does is it simply 00:49:01.200 --> 00:49:02.710 align:start position:0% what our task manager does is it simply routes<00:49:01.680> the<00:49:01.799> blocks<00:49:02.240> that<00:49:02.359> are<00:49:02.480> being 00:49:02.710 --> 00:49:02.720 align:start position:0% routes the blocks that are being 00:49:02.720 --> 00:49:05.230 align:start position:0% routes the blocks that are being proposed<00:49:03.160> over<00:49:03.359> to<00:49:03.559> Tao<00:49:03.880> contract<00:49:04.839> so<00:49:05.040> because 00:49:05.230 --> 00:49:05.240 align:start position:0% proposed over to Tao contract so because 00:49:05.240 --> 00:49:07.829 align:start position:0% proposed over to Tao contract so because of<00:49:05.480> this<00:49:05.960> the<00:49:06.160> prover<00:49:06.640> architecture<00:49:07.520> doesn't 00:49:07.829 --> 00:49:07.839 align:start position:0% of this the prover architecture doesn't 00:49:07.839 --> 00:49:09.430 align:start position:0% of this the prover architecture doesn't have<00:49:07.960> to<00:49:08.119> change<00:49:08.559> that's<00:49:08.760> the<00:49:08.920> best<00:49:09.160> part 00:49:09.430 --> 00:49:09.440 align:start position:0% have to change that's the best part 00:49:09.440 --> 00:49:11.190 align:start position:0% have to change that's the best part nothing<00:49:09.680> in<00:49:09.799> the<00:49:09.920> prover<00:49:10.240> has<00:49:10.359> to<00:49:10.520> change<00:49:11.079> and 00:49:11.190 --> 00:49:11.200 align:start position:0% nothing in the prover has to change and 00:49:11.200 --> 00:49:12.910 align:start position:0% nothing in the prover has to change and the<00:49:11.319> proposer<00:49:11.799> also<00:49:12.000> needs<00:49:12.319> very<00:49:12.520> minor 00:49:12.910 --> 00:49:12.920 align:start position:0% the proposer also needs very minor 00:49:12.920 --> 00:49:15.030 align:start position:0% the proposer also needs very minor modifications<00:49:13.640> because<00:49:13.960> the<00:49:14.359> original 00:49:15.030 --> 00:49:15.040 align:start position:0% modifications because the original 00:49:15.040 --> 00:49:17.390 align:start position:0% modifications because the original contract<00:49:16.040> original<00:49:16.400> contracts<00:49:16.760> of<00:49:16.920> Tao<00:49:17.240> have 00:49:17.390 --> 00:49:17.400 align:start position:0% contract original contracts of Tao have 00:49:17.400 --> 00:49:20.589 align:start position:0% contract original contracts of Tao have barely<00:49:17.720> been 00:49:20.589 --> 00:49:20.599 align:start position:0% 00:49:20.599 --> 00:49:24.910 align:start position:0% changed<00:49:21.599> go<00:49:21.760> ahead<00:49:22.559> for<00:49:22.680> the<00:49:22.799> next 00:49:24.910 --> 00:49:24.920 align:start position:0% changed go ahead for the next 00:49:24.920 --> 00:49:28.109 align:start position:0% changed go ahead for the next step<00:49:25.920> thank<00:49:26.079> you<00:49:26.480> thank<00:49:26.720> thank 00:49:28.109 --> 00:49:28.119 align:start position:0% step thank you thank thank 00:49:28.119 --> 00:49:31.390 align:start position:0% step thank you thank thank you<00:49:29.119> okay<00:49:29.680> so<00:49:30.280> now<00:49:30.599> we're<00:49:30.839> going<00:49:30.920> to<00:49:31.079> go<00:49:31.280> back 00:49:31.390 --> 00:49:31.400 align:start position:0% you okay so now we're going to go back 00:49:31.400 --> 00:49:33.190 align:start position:0% you okay so now we're going to go back to<00:49:31.559> the<00:49:31.720> pre-confirmation<00:49:32.160> loop<00:49:32.839> that<00:49:33.040> we 00:49:33.190 --> 00:49:33.200 align:start position:0% to the pre-confirmation loop that we 00:49:33.200 --> 00:49:35.829 align:start position:0% to the pre-confirmation loop that we discussed<00:49:33.799> that<00:49:34.119> every<00:49:34.319> 3<00:49:34.599> second<00:49:35.040> we<00:49:35.200> go<00:49:35.400> and 00:49:35.829 --> 00:49:35.839 align:start position:0% discussed that every 3 second we go and 00:49:35.839 --> 00:49:39.349 align:start position:0% discussed that every 3 second we go and um<00:49:36.400> in<00:49:36.599> a<00:49:36.760> bit<00:49:36.920> more 00:49:39.349 --> 00:49:39.359 align:start position:0% 00:49:39.359 --> 00:49:42.069 align:start position:0% details<00:49:40.359> I<00:49:40.520> hope<00:49:40.760> this<00:49:41.000> clicker 00:49:42.069 --> 00:49:42.079 align:start position:0% details I hope this clicker 00:49:42.079 --> 00:49:45.630 align:start position:0% details I hope this clicker works<00:49:43.079> okay<00:49:43.240> I'll<00:49:43.440> just<00:49:43.599> stand<00:49:44.079> here 00:49:45.630 --> 00:49:45.640 align:start position:0% works okay I'll just stand here 00:49:45.640 --> 00:49:48.030 align:start position:0% works okay I'll just stand here um<00:49:46.640> all 00:49:48.030 --> 00:49:48.040 align:start position:0% um all 00:49:48.040 --> 00:49:50.030 align:start position:0% um all right 00:49:50.030 --> 00:49:50.040 align:start position:0% right 00:49:50.040 --> 00:49:54.030 align:start position:0% right so<00:49:51.040> first<00:49:52.040> we<00:49:52.240> start<00:49:52.640> with 00:49:54.030 --> 00:49:54.040 align:start position:0% so first we start with 00:49:54.040 --> 00:49:57.150 align:start position:0% so first we start with the<00:49:55.040> normal<00:49:55.440> event<00:49:55.760> Loop<00:49:56.040> for<00:49:56.240> Tao 00:49:57.150 --> 00:49:57.160 align:start position:0% the normal event Loop for Tao 00:49:57.160 --> 00:49:59.990 align:start position:0% the normal event Loop for Tao so<00:49:57.359> what<00:49:57.520> Tao<00:49:57.880> does<00:49:58.319> is<00:49:58.520> that<00:49:58.760> once<00:49:59.119> every<00:49:59.400> L1 00:49:59.990 --> 00:50:00.000 align:start position:0% so what Tao does is that once every L1 00:50:00.000 --> 00:50:02.750 align:start position:0% so what Tao does is that once every L1 slot<00:50:01.000> it<00:50:01.160> pulls<00:50:01.559> the<00:50:01.799> pending<00:50:02.200> transactions 00:50:02.750 --> 00:50:02.760 align:start position:0% slot it pulls the pending transactions 00:50:02.760 --> 00:50:05.309 align:start position:0% slot it pulls the pending transactions from<00:50:02.960> the<00:50:03.079> men<00:50:03.359> poool<00:50:03.920> Tao<00:50:04.319> proposer<00:50:04.839> goes<00:50:05.079> and 00:50:05.309 --> 00:50:05.319 align:start position:0% from the men poool Tao proposer goes and 00:50:05.319 --> 00:50:08.109 align:start position:0% from the men poool Tao proposer goes and forms<00:50:05.720> the<00:50:05.839> block<00:50:06.280> and<00:50:06.480> then<00:50:07.119> pushes<00:50:07.880> it 00:50:08.109 --> 00:50:08.119 align:start position:0% forms the block and then pushes it 00:50:08.119 --> 00:50:10.829 align:start position:0% forms the block and then pushes it through<00:50:08.319> the<00:50:08.480> blob<00:50:09.280> to<00:50:09.760> the<00:50:09.920> rollup<00:50:10.319> inbox 00:50:10.829 --> 00:50:10.839 align:start position:0% through the blob to the rollup inbox 00:50:10.839 --> 00:50:13.150 align:start position:0% through the blob to the rollup inbox contract<00:50:11.440> through<00:50:11.680> the<00:50:11.920> proposed<00:50:12.280> block 00:50:13.150 --> 00:50:13.160 align:start position:0% contract through the proposed block 00:50:13.160 --> 00:50:18.390 align:start position:0% contract through the proposed block function<00:50:14.160> very<00:50:14.359> simple 00:50:18.390 --> 00:50:18.400 align:start position:0% 00:50:18.400 --> 00:50:20.270 align:start position:0% straightforward<00:50:19.400> what<00:50:19.559> we<00:50:19.760> have<00:50:20.000> with<00:50:20.160> the 00:50:20.270 --> 00:50:20.280 align:start position:0% straightforward what we have with the 00:50:20.280 --> 00:50:23.589 align:start position:0% straightforward what we have with the prec<00:50:20.520> confing<00:50:21.040> solution<00:50:21.880> is<00:50:22.040> the<00:50:22.599> following 00:50:23.589 --> 00:50:23.599 align:start position:0% prec confing solution is the following 00:50:23.599 --> 00:50:25.990 align:start position:0% prec confing solution is the following so<00:50:23.760> we<00:50:23.880> have<00:50:24.000> the<00:50:24.119> pre-com<00:50:24.599> node<00:50:25.480> every<00:50:25.760> 3 00:50:25.990 --> 00:50:26.000 align:start position:0% so we have the pre-com node every 3 00:50:26.000 --> 00:50:28.789 align:start position:0% so we have the pre-com node every 3 second<00:50:26.720> requesting<00:50:27.280> from<00:50:27.440> The<00:50:27.599> Tao<00:50:28.000> proposal 00:50:28.789 --> 00:50:28.799 align:start position:0% second requesting from The Tao proposal 00:50:28.799 --> 00:50:31.190 align:start position:0% second requesting from The Tao proposal a<00:50:28.960> batch<00:50:29.200> of<00:50:29.400> transaction<00:50:30.280> Tao<00:50:30.640> proposer<00:50:31.040> goes 00:50:31.190 --> 00:50:31.200 align:start position:0% a batch of transaction Tao proposer goes 00:50:31.200 --> 00:50:33.150 align:start position:0% a batch of transaction Tao proposer goes and<00:50:31.359> fitches<00:50:31.839> those<00:50:32.040> batch<00:50:32.280> of<00:50:32.440> transactions 00:50:33.150 --> 00:50:33.160 align:start position:0% and fitches those batch of transactions 00:50:33.160 --> 00:50:34.309 align:start position:0% and fitches those batch of transactions from 00:50:34.309 --> 00:50:34.319 align:start position:0% from 00:50:34.319 --> 00:50:38.829 align:start position:0% from Tao<00:50:35.319> and<00:50:35.799> forms<00:50:36.319> a<00:50:36.880> batch<00:50:37.799> gives<00:50:38.160> that<00:50:38.440> batch 00:50:38.829 --> 00:50:38.839 align:start position:0% Tao and forms a batch gives that batch 00:50:38.839 --> 00:50:42.150 align:start position:0% Tao and forms a batch gives that batch to<00:50:39.520> the<00:50:39.720> precom<00:50:40.559> node 00:50:42.150 --> 00:50:42.160 align:start position:0% to the precom node 00:50:42.160 --> 00:50:47.270 align:start position:0% to the precom node and<00:50:43.160> the<00:50:43.319> precom<00:50:43.760> node<00:50:44.079> then<00:50:44.280> goes<00:50:44.839> and<00:50:45.839> then 00:50:47.270 --> 00:50:47.280 align:start position:0% and the precom node then goes and then 00:50:47.280 --> 00:50:51.630 align:start position:0% and the precom node then goes and then um<00:50:48.280> uh<00:50:48.599> pushes<00:50:49.599> this<00:50:49.880> transaction<00:50:50.680> to<00:50:50.839> the<00:50:51.000> P2P 00:50:51.630 --> 00:50:51.640 align:start position:0% um uh pushes this transaction to the P2P 00:50:51.640 --> 00:50:53.630 align:start position:0% um uh pushes this transaction to the P2P like<00:50:51.799> we<00:50:51.920> said<00:50:52.599> the<00:50:52.720> batch<00:50:52.960> of<00:50:53.119> transactions 00:50:53.630 --> 00:50:53.640 align:start position:0% like we said the batch of transactions 00:50:53.640 --> 00:50:57.510 align:start position:0% like we said the batch of transactions to<00:50:53.799> the<00:50:54.200> P2P<00:50:55.200> and<00:50:55.680> of<00:50:55.839> course<00:50:56.480> the<00:50:56.680> this<00:50:57.040> also 00:50:57.510 --> 00:50:57.520 align:start position:0% to the P2P and of course the this also 00:50:57.520 --> 00:51:00.829 align:start position:0% to the P2P and of course the this also only<00:50:57.960> happens<00:50:58.839> after<00:50:59.119> it<00:50:59.319> made<00:50:59.599> sure<00:51:00.440> that<00:51:00.680> it 00:51:00.829 --> 00:51:00.839 align:start position:0% only happens after it made sure that it 00:51:00.839 --> 00:51:04.670 align:start position:0% only happens after it made sure that it is<00:51:01.559> the<00:51:01.839> prec<00:51:02.119> comfort<00:51:02.880> for<00:51:03.200> this<00:51:03.520> specific<00:51:04.520> uh 00:51:04.670 --> 00:51:04.680 align:start position:0% is the prec comfort for this specific uh 00:51:04.680 --> 00:51:06.750 align:start position:0% is the prec comfort for this specific uh for<00:51:04.920> the<00:51:05.079> up<00:51:05.280> for<00:51:05.520> this<00:51:05.680> slot<00:51:06.200> and<00:51:06.359> or<00:51:06.599> an 00:51:06.750 --> 00:51:06.760 align:start position:0% for the up for this slot and or an 00:51:06.760 --> 00:51:09.069 align:start position:0% for the up for this slot and or an upcoming<00:51:07.240> slot<00:51:07.640> that<00:51:07.799> is<00:51:08.000> very 00:51:09.069 --> 00:51:09.079 align:start position:0% upcoming slot that is very 00:51:09.079 --> 00:51:14.270 align:start position:0% upcoming slot that is very near<00:51:10.079> so<00:51:10.319> this<00:51:10.440> is<00:51:10.680> the<00:51:11.040> the<00:51:11.319> new<00:51:11.880> uh 00:51:14.270 --> 00:51:14.280 align:start position:0% 00:51:14.280 --> 00:51:18.030 align:start position:0% loop<00:51:15.280> okay<00:51:15.920> all<00:51:16.079> right<00:51:16.760> so<00:51:17.000> what<00:51:17.119> do<00:51:17.280> we<00:51:17.480> sign 00:51:18.030 --> 00:51:18.040 align:start position:0% loop okay all right so what do we sign 00:51:18.040 --> 00:51:19.589 align:start position:0% loop okay all right so what do we sign when<00:51:18.200> we<00:51:18.440> provide<00:51:18.720> the<00:51:18.839> prec<00:51:19.079> confirmations 00:51:19.589 --> 00:51:19.599 align:start position:0% when we provide the prec confirmations 00:51:19.599 --> 00:51:22.150 align:start position:0% when we provide the prec confirmations through<00:51:19.760> P2P<00:51:20.319> what's<00:51:20.599> the 00:51:22.150 --> 00:51:22.160 align:start position:0% through P2P what's the 00:51:22.160 --> 00:51:25.630 align:start position:0% through P2P what's the signature<00:51:23.480> so<00:51:24.480> the<00:51:24.720> the<00:51:24.839> structure<00:51:25.319> that<00:51:25.480> we 00:51:25.630 --> 00:51:25.640 align:start position:0% signature so the the structure that we 00:51:25.640 --> 00:51:28.630 align:start position:0% signature so the the structure that we use<00:51:25.920> is<00:51:26.599> we<00:51:26.720> use<00:51:26.960> the<00:51:27.079> block<00:51:27.319> ID<00:51:27.960> because<00:51:28.319> we<00:51:28.520> we 00:51:28.630 --> 00:51:28.640 align:start position:0% use is we use the block ID because we we 00:51:28.640 --> 00:51:30.470 align:start position:0% use is we use the block ID because we we need<00:51:28.839> to<00:51:29.119> commit<00:51:29.440> to<00:51:29.599> a<00:51:29.760> specific<00:51:30.160> block 00:51:30.470 --> 00:51:30.480 align:start position:0% need to commit to a specific block 00:51:30.480 --> 00:51:34.109 align:start position:0% need to commit to a specific block height<00:51:31.440> or<00:51:32.359> that<00:51:33.160> uh<00:51:33.319> pre<00:51:33.559> confer<00:51:33.920> could 00:51:34.109 --> 00:51:34.119 align:start position:0% height or that uh pre confer could 00:51:34.119 --> 00:51:36.150 align:start position:0% height or that uh pre confer could potentially<00:51:34.720> sandwich<00:51:35.319> transaction<00:51:35.880> if<00:51:36.000> it 00:51:36.150 --> 00:51:36.160 align:start position:0% potentially sandwich transaction if it 00:51:36.160 --> 00:51:38.190 align:start position:0% potentially sandwich transaction if it wanted<00:51:36.440> to<00:51:37.040> if<00:51:37.160> we<00:51:37.319> don't<00:51:37.599> commit<00:51:37.920> to<00:51:38.040> a 00:51:38.190 --> 00:51:38.200 align:start position:0% wanted to if we don't commit to a 00:51:38.200 --> 00:51:40.190 align:start position:0% wanted to if we don't commit to a specific<00:51:38.640> block<00:51:38.960> height<00:51:39.280> that<00:51:39.440> it<00:51:39.520> needs<00:51:39.799> to 00:51:40.190 --> 00:51:40.200 align:start position:0% specific block height that it needs to 00:51:40.200 --> 00:51:44.670 align:start position:0% specific block height that it needs to to<00:51:40.760> uh<00:51:41.119> to<00:51:41.400> propose<00:51:41.920> this<00:51:42.720> uh<00:51:42.920> batch<00:51:43.400> app<00:51:44.400> also 00:51:44.670 --> 00:51:44.680 align:start position:0% to uh to propose this uh batch app also 00:51:44.680 --> 00:51:47.750 align:start position:0% to uh to propose this uh batch app also the<00:51:44.799> chain<00:51:45.079> ID<00:51:45.640> in<00:51:45.880> case<00:51:46.160> we<00:51:46.280> are<00:51:47.040> we<00:51:47.280> have<00:51:47.559> like 00:51:47.750 --> 00:51:47.760 align:start position:0% the chain ID in case we are we have like 00:51:47.760 --> 00:51:51.109 align:start position:0% the chain ID in case we are we have like multiple<00:51:48.599> uh<00:51:48.799> chains<00:51:49.799> and<00:51:50.119> transaction<00:51:50.760> list 00:51:51.109 --> 00:51:51.119 align:start position:0% multiple uh chains and transaction list 00:51:51.119 --> 00:51:53.390 align:start position:0% multiple uh chains and transaction list hash<00:51:51.799> which<00:51:51.960> is<00:51:52.119> basically<00:51:52.559> just<00:51:52.680> a<00:51:52.880> hash<00:51:53.160> of 00:51:53.390 --> 00:51:53.400 align:start position:0% hash which is basically just a hash of 00:51:53.400 --> 00:51:55.829 align:start position:0% hash which is basically just a hash of the<00:51:53.520> rlp<00:51:53.960> encoded<00:51:54.480> transaction<00:51:55.040> list<00:51:55.599> and<00:51:55.720> I 00:51:55.829 --> 00:51:55.839 align:start position:0% the rlp encoded transaction list and I 00:51:55.839 --> 00:51:58.190 align:start position:0% the rlp encoded transaction list and I see<00:51:56.640> there<00:51:56.760> are<00:51:56.960> some<00:51:57.240> hands<00:51:57.480> for<00:51:57.720> questions 00:51:58.190 --> 00:51:58.200 align:start position:0% see there are some hands for questions 00:51:58.200 --> 00:52:01.069 align:start position:0% see there are some hands for questions yeah<00:51:58.400> go<00:51:58.480> ahead<00:51:58.920> you<00:51:59.160> you<00:51:59.280> have<00:51:59.440> the<00:51:59.880> mic<00:52:00.880> it's 00:52:01.069 --> 00:52:01.079 align:start position:0% yeah go ahead you you have the mic it's 00:52:01.079 --> 00:52:04.750 align:start position:0% yeah go ahead you you have the mic it's fine<00:52:01.240> just<00:52:01.440> raise<00:52:01.880> your<00:52:03.079> seconds<00:52:04.079> yeah<00:52:04.240> so<00:52:04.559> 3 00:52:04.750 --> 00:52:04.760 align:start position:0% fine just raise your seconds yeah so 3 00:52:04.760 --> 00:52:07.390 align:start position:0% fine just raise your seconds yeah so 3 seconds<00:52:05.160> was<00:52:05.400> like<00:52:05.559> a<00:52:05.720> just<00:52:05.880> a<00:52:06.400> conservative 00:52:07.390 --> 00:52:07.400 align:start position:0% seconds was like a just a conservative 00:52:07.400 --> 00:52:09.829 align:start position:0% seconds was like a just a conservative um<00:52:07.839> random<00:52:08.319> number<00:52:08.799> that<00:52:08.960> we<00:52:09.079> chose<00:52:09.480> at<00:52:09.640> this 00:52:09.829 --> 00:52:09.839 align:start position:0% um random number that we chose at this 00:52:09.839 --> 00:52:12.829 align:start position:0% um random number that we chose at this point<00:52:10.119> because<00:52:10.720> we<00:52:10.920> weren't<00:52:11.359> sure<00:52:11.839> how<00:52:12.280> fast 00:52:12.829 --> 00:52:12.839 align:start position:0% point because we weren't sure how fast 00:52:12.839 --> 00:52:15.390 align:start position:0% point because we weren't sure how fast the<00:52:13.160> the<00:52:13.319> system<00:52:13.680> would<00:52:14.160> be<00:52:14.400> the<00:52:14.520> latencies 00:52:15.390 --> 00:52:15.400 align:start position:0% the the system would be the latencies 00:52:15.400 --> 00:52:17.950 align:start position:0% the the system would be the latencies all<00:52:15.520> of<00:52:15.720> that<00:52:16.640> um<00:52:16.880> what<00:52:17.000> we're<00:52:17.200> going<00:52:17.319> to<00:52:17.760> be 00:52:17.950 --> 00:52:17.960 align:start position:0% all of that um what we're going to be 00:52:17.960 --> 00:52:21.309 align:start position:0% all of that um what we're going to be working<00:52:18.359> on<00:52:18.839> later<00:52:19.520> as<00:52:19.680> you<00:52:19.839> we<00:52:19.960> will<00:52:20.160> see<00:52:21.160> and 00:52:21.309 --> 00:52:21.319 align:start position:0% working on later as you we will see and 00:52:21.319 --> 00:52:24.030 align:start position:0% working on later as you we will see and one<00:52:21.440> of<00:52:21.559> the<00:52:21.680> slides<00:52:22.040> is<00:52:22.640> is<00:52:22.880> like<00:52:23.559> getting 00:52:24.030 --> 00:52:24.040 align:start position:0% one of the slides is is like getting 00:52:24.040 --> 00:52:26.150 align:start position:0% one of the slides is is like getting that<00:52:24.200> number<00:52:24.520> lower<00:52:24.920> and<00:52:25.119> seeing<00:52:25.920> how<00:52:26.040> it's 00:52:26.150 --> 00:52:26.160 align:start position:0% that number lower and seeing how it's 00:52:26.160 --> 00:52:28.069 align:start position:0% that number lower and seeing how it's going<00:52:26.280> to<00:52:26.359> be<00:52:26.559> behave<00:52:27.000> and<00:52:27.160> how<00:52:27.319> will<00:52:27.440> it<00:52:27.599> work 00:52:28.069 --> 00:52:28.079 align:start position:0% going to be behave and how will it work 00:52:28.079 --> 00:52:31.950 align:start position:0% going to be behave and how will it work we<00:52:28.160> will<00:52:28.359> talk<00:52:28.559> about<00:52:28.880> that<00:52:29.119> in<00:52:29.400> in<00:52:29.839> in<00:52:30.000> later 00:52:31.950 --> 00:52:31.960 align:start position:0% we will talk about that in in in later 00:52:31.960 --> 00:52:34.190 align:start position:0% we will talk about that in in in later slides 00:52:34.190 --> 00:52:34.200 align:start position:0% slides 00:52:34.200 --> 00:52:38.190 align:start position:0% slides okay<00:52:35.200> so<00:52:35.400> this<00:52:35.680> works<00:52:36.359> here 00:52:38.190 --> 00:52:38.200 align:start position:0% okay so this works here 00:52:38.200 --> 00:52:42.069 align:start position:0% okay so this works here okay<00:52:39.200> yeah<00:52:40.119> so<00:52:41.119> the<00:52:41.680> the<00:52:41.960> the 00:52:42.069 --> 00:52:42.079 align:start position:0% okay yeah so the the the 00:52:42.079 --> 00:52:44.030 align:start position:0% okay yeah so the the the pre-confirmation<00:52:42.599> structure<00:52:43.200> we<00:52:43.319> saw<00:52:43.599> it<00:52:43.880> and 00:52:44.030 --> 00:52:44.040 align:start position:0% pre-confirmation structure we saw it and 00:52:44.040 --> 00:52:45.549 align:start position:0% pre-confirmation structure we saw it and then<00:52:44.359> there<00:52:44.520> is<00:52:44.799> the<00:52:45.040> pre-confirmation 00:52:45.549 --> 00:52:45.559 align:start position:0% then there is the pre-confirmation 00:52:45.559 --> 00:52:48.710 align:start position:0% then there is the pre-confirmation object<00:52:46.359> that<00:52:46.480> is<00:52:46.599> sent<00:52:46.839> on<00:52:47.040> P2P<00:52:47.680> because<00:52:48.559> the 00:52:48.710 --> 00:52:48.720 align:start position:0% object that is sent on P2P because the 00:52:48.720 --> 00:52:51.670 align:start position:0% object that is sent on P2P because the pre-confirmation<00:52:49.480> structure<00:52:50.480> is<00:52:51.200> the<00:52:51.319> one 00:52:51.670 --> 00:52:51.680 align:start position:0% pre-confirmation structure is the one 00:52:51.680 --> 00:52:56.069 align:start position:0% pre-confirmation structure is the one that<00:52:52.119> can<00:52:52.359> be<00:52:52.640> pushed<00:52:53.480> as<00:52:53.599> a<00:52:53.799> proof<00:52:54.520> for<00:52:55.520> uh<00:52:55.960> uh 00:52:56.069 --> 00:52:56.079 align:start position:0% that can be pushed as a proof for uh uh 00:52:56.079 --> 00:53:00.069 align:start position:0% that can be pushed as a proof for uh uh fraud<00:52:56.599> proof<00:52:57.240> but<00:52:57.520> here<00:52:58.200> we<00:52:58.359> need<00:52:58.839> to<00:52:59.839> uh<00:52:59.960> when 00:53:00.069 --> 00:53:00.079 align:start position:0% fraud proof but here we need to uh when 00:53:00.079 --> 00:53:02.990 align:start position:0% fraud proof but here we need to uh when we<00:53:00.200> are<00:53:00.359> pushing<00:53:00.720> the<00:53:00.880> precom<00:53:01.520> batch<00:53:02.280> on<00:53:02.480> P2P 00:53:02.990 --> 00:53:03.000 align:start position:0% we are pushing the precom batch on P2P 00:53:03.000 --> 00:53:05.710 align:start position:0% we are pushing the precom batch on P2P we<00:53:03.119> need<00:53:03.520> more<00:53:03.839> details<00:53:04.799> that<00:53:04.960> one<00:53:05.280> is<00:53:05.440> not 00:53:05.710 --> 00:53:05.720 align:start position:0% we need more details that one is not 00:53:05.720 --> 00:53:08.829 align:start position:0% we need more details that one is not enough<00:53:06.359> so<00:53:06.599> we<00:53:06.799> have<00:53:07.400> the<00:53:07.559> block<00:53:07.920> height<00:53:08.520> and 00:53:08.829 --> 00:53:08.839 align:start position:0% enough so we have the block height and 00:53:08.839 --> 00:53:11.030 align:start position:0% enough so we have the block height and the<00:53:09.000> pending<00:53:09.400> transaction<00:53:09.960> list<00:53:10.400> the<00:53:10.520> whole 00:53:11.030 --> 00:53:11.040 align:start position:0% the pending transaction list the whole 00:53:11.040 --> 00:53:13.069 align:start position:0% the pending transaction list the whole list<00:53:12.040> and 00:53:13.069 --> 00:53:13.079 align:start position:0% list and 00:53:13.079 --> 00:53:17.109 align:start position:0% list and um<00:53:14.079> and<00:53:15.040> the<00:53:15.319> pending<00:53:15.720> transaction<00:53:16.480> bytes<00:53:17.000> I'm 00:53:17.109 --> 00:53:17.119 align:start position:0% um and the pending transaction bytes I'm 00:53:17.119 --> 00:53:19.710 align:start position:0% um and the pending transaction bytes I'm not<00:53:17.359> entirely<00:53:17.720> sure<00:53:18.000> what<00:53:18.200> that<00:53:18.520> is<00:53:18.720> for<00:53:19.559> and 00:53:19.710 --> 00:53:19.720 align:start position:0% not entirely sure what that is for and 00:53:19.720 --> 00:53:24.309 align:start position:0% not entirely sure what that is for and the<00:53:20.119> proof<00:53:21.119> uh<00:53:21.720> uh<00:53:22.359> of<00:53:22.599> the<00:53:22.799> precom 00:53:24.309 --> 00:53:24.319 align:start position:0% the proof uh uh of the precom 00:53:24.319 --> 00:53:26.789 align:start position:0% the proof uh uh of the precom message<00:53:25.319> and<00:53:25.480> this<00:53:25.599> is<00:53:25.799> what<00:53:26.000> ends<00:53:26.240> up<00:53:26.599> being 00:53:26.789 --> 00:53:26.799 align:start position:0% message and this is what ends up being 00:53:26.799 --> 00:53:30.470 align:start position:0% message and this is what ends up being sent<00:53:27.240> exactly<00:53:27.680> in<00:53:27.960> the<00:53:28.359> P2P<00:53:29.359> and<00:53:30.040> the<00:53:30.200> reason 00:53:30.470 --> 00:53:30.480 align:start position:0% sent exactly in the P2P and the reason 00:53:30.480 --> 00:53:32.150 align:start position:0% sent exactly in the P2P and the reason we<00:53:30.599> need<00:53:30.839> the<00:53:31.000> batch<00:53:31.240> of<00:53:31.400> transactions<00:53:31.960> is 00:53:32.150 --> 00:53:32.160 align:start position:0% we need the batch of transactions is 00:53:32.160 --> 00:53:35.230 align:start position:0% we need the batch of transactions is because<00:53:32.480> we<00:53:32.640> need<00:53:33.319> all<00:53:33.559> the<00:53:33.760> other<00:53:34.760> uh<00:53:34.960> pre- 00:53:35.230 --> 00:53:35.240 align:start position:0% because we need all the other uh pre- 00:53:35.240 --> 00:53:37.510 align:start position:0% because we need all the other uh pre- confers<00:53:35.799> or<00:53:36.040> all<00:53:36.200> of<00:53:36.359> the<00:53:36.520> other<00:53:36.960> participants 00:53:37.510 --> 00:53:37.520 align:start position:0% confers or all of the other participants 00:53:37.520 --> 00:53:39.630 align:start position:0% confers or all of the other participants in<00:53:37.680> the<00:53:37.799> network<00:53:38.319> to<00:53:38.440> be<00:53:38.599> able<00:53:38.839> to<00:53:39.040> advance<00:53:39.440> the 00:53:39.630 --> 00:53:39.640 align:start position:0% in the network to be able to advance the 00:53:39.640 --> 00:53:41.230 align:start position:0% in the network to be able to advance the head<00:53:39.880> with<00:53:40.040> this<00:53:40.200> batch<00:53:40.440> of 00:53:41.230 --> 00:53:41.240 align:start position:0% head with this batch of 00:53:41.240 --> 00:53:46.030 align:start position:0% head with this batch of transaction<00:53:42.240> and<00:53:42.960> we<00:53:43.559> also<00:53:44.559> um<00:53:45.319> need<00:53:45.599> them<00:53:45.799> to 00:53:46.030 --> 00:53:46.040 align:start position:0% transaction and we also um need them to 00:53:46.040 --> 00:53:49.349 align:start position:0% transaction and we also um need them to be<00:53:46.359> aware<00:53:46.720> of<00:53:46.960> this<00:53:47.200> so<00:53:47.559> when<00:53:47.839> their<00:53:48.760> role<00:53:49.119> of 00:53:49.349 --> 00:53:49.359 align:start position:0% be aware of this so when their role of 00:53:49.359 --> 00:53:51.630 align:start position:0% be aware of this so when their role of pre-<00:53:49.640> confing<00:53:49.960> comes<00:53:50.200> along<00:53:50.880> they<00:53:51.040> know<00:53:51.359> that 00:53:51.630 --> 00:53:51.640 align:start position:0% pre- confing comes along they know that 00:53:51.640 --> 00:53:52.950 align:start position:0% pre- confing comes along they know that okay<00:53:51.880> these<00:53:52.079> transactions<00:53:52.640> have<00:53:52.799> been 00:53:52.950 --> 00:53:52.960 align:start position:0% okay these transactions have been 00:53:52.960 --> 00:53:54.750 align:start position:0% okay these transactions have been already<00:53:53.240> precom<00:53:53.880> and<00:53:54.040> potentially<00:53:54.440> will<00:53:54.599> be 00:53:54.750 --> 00:53:54.760 align:start position:0% already precom and potentially will be 00:53:54.760 --> 00:53:57.150 align:start position:0% already precom and potentially will be proposed<00:53:55.160> in<00:53:55.280> the<00:53:55.400> next<00:53:56.119> and<00:53:56.280> and<00:53:56.440> in<00:53:56.640> the<00:53:57.040> in 00:53:57.150 --> 00:53:57.160 align:start position:0% proposed in the next and and in the in 00:53:57.160 --> 00:53:59.230 align:start position:0% proposed in the next and and in the in the<00:53:57.319> previous<00:53:57.640> L1<00:53:58.000> block<00:53:58.520> before<00:53:58.760> we<00:53:58.920> start 00:53:59.230 --> 00:53:59.240 align:start position:0% the previous L1 block before we start 00:53:59.240 --> 00:54:02.990 align:start position:0% the previous L1 block before we start pre<00:53:59.480> confing 00:54:02.990 --> 00:54:03.000 align:start position:0% 00:54:03.000 --> 00:54:04.510 align:start position:0% ourselves 00:54:04.510 --> 00:54:04.520 align:start position:0% ourselves 00:54:04.520 --> 00:54:10.549 align:start position:0% ourselves yeah<00:54:05.720> so<00:54:07.000> when<00:54:08.000> um<00:54:08.839> when<00:54:09.000> a<00:54:09.240> pre-com<00:54:09.839> node 00:54:10.549 --> 00:54:10.559 align:start position:0% yeah so when um when a pre-com node 00:54:10.559 --> 00:54:12.589 align:start position:0% yeah so when um when a pre-com node receives<00:54:11.000> the<00:54:11.119> batch<00:54:11.359> of<00:54:11.559> transaction<00:54:12.400> from 00:54:12.589 --> 00:54:12.599 align:start position:0% receives the batch of transaction from 00:54:12.599 --> 00:54:16.470 align:start position:0% receives the batch of transaction from the<00:54:12.720> P2P<00:54:13.480> once<00:54:13.799> it's<00:54:14.119> has<00:54:14.240> been<00:54:14.799> ProMed 00:54:16.470 --> 00:54:16.480 align:start position:0% the P2P once it's has been ProMed 00:54:16.480 --> 00:54:20.150 align:start position:0% the P2P once it's has been ProMed we<00:54:17.480> currently<00:54:18.000> the<00:54:18.160> way<00:54:18.400> it's<00:54:18.839> it<00:54:19.040> it<00:54:19.200> works<00:54:20.040> uh 00:54:20.150 --> 00:54:20.160 align:start position:0% we currently the way it's it it works uh 00:54:20.160 --> 00:54:23.670 align:start position:0% we currently the way it's it it works uh in<00:54:20.400> Tao<00:54:20.760> before<00:54:21.000> the<00:54:21.240> precom<00:54:22.240> is<00:54:22.599> that<00:54:23.280> we<00:54:23.440> get 00:54:23.670 --> 00:54:23.680 align:start position:0% in Tao before the precom is that we get 00:54:23.680 --> 00:54:25.789 align:start position:0% in Tao before the precom is that we get an<00:54:23.920> event<00:54:24.480> which<00:54:24.599> is<00:54:24.720> called<00:54:24.960> block<00:54:25.280> proposed 00:54:25.789 --> 00:54:25.799 align:start position:0% an event which is called block proposed 00:54:25.799 --> 00:54:28.829 align:start position:0% an event which is called block proposed from<00:54:26.000> the<00:54:26.440> one<00:54:27.319> and<00:54:27.559> that<00:54:27.760> goes<00:54:28.240> the<00:54:28.480> Tao 00:54:28.829 --> 00:54:28.839 align:start position:0% from the one and that goes the Tao 00:54:28.839 --> 00:54:30.710 align:start position:0% from the one and that goes the Tao driver<00:54:29.119> is<00:54:29.319> basically<00:54:29.680> subscribed<00:54:30.240> to<00:54:30.440> this 00:54:30.710 --> 00:54:30.720 align:start position:0% driver is basically subscribed to this 00:54:30.720 --> 00:54:34.829 align:start position:0% driver is basically subscribed to this specific<00:54:31.200> event<00:54:31.960> and<00:54:32.240> advances<00:54:32.720> the<00:54:33.000> head<00:54:34.000> uh 00:54:34.829 --> 00:54:34.839 align:start position:0% specific event and advances the head uh 00:54:34.839 --> 00:54:36.990 align:start position:0% specific event and advances the head uh uh<00:54:35.319> once<00:54:35.559> it<00:54:35.960> receives<00:54:36.160> this<00:54:36.359> event<00:54:36.839> which 00:54:36.990 --> 00:54:37.000 align:start position:0% uh once it receives this event which 00:54:37.000 --> 00:54:38.630 align:start position:0% uh once it receives this event which means<00:54:37.440> that<00:54:37.720> the<00:54:37.839> user<00:54:38.160> will<00:54:38.359> get<00:54:38.480> a 00:54:38.630 --> 00:54:38.640 align:start position:0% means that the user will get a 00:54:38.640 --> 00:54:41.950 align:start position:0% means that the user will get a transaction<00:54:39.160> receipt<00:54:39.599> every<00:54:39.920> 12<00:54:40.319> to<00:54:40.799> 24 00:54:41.950 --> 00:54:41.960 align:start position:0% transaction receipt every 12 to 24 00:54:41.960 --> 00:54:46.270 align:start position:0% transaction receipt every 12 to 24 seconds<00:54:42.960> and<00:54:43.160> this<00:54:43.440> is<00:54:44.440> the<00:54:44.599> main<00:54:45.040> point<00:54:46.040> that 00:54:46.270 --> 00:54:46.280 align:start position:0% seconds and this is the main point that 00:54:46.280 --> 00:54:48.470 align:start position:0% seconds and this is the main point that prec<00:54:46.520> confirmation<00:54:47.240> our<00:54:47.480> precon<00:54:48.040> solution<00:54:48.359> is 00:54:48.470 --> 00:54:48.480 align:start position:0% prec confirmation our precon solution is 00:54:48.480 --> 00:54:49.470 align:start position:0% prec confirmation our precon solution is trying<00:54:48.760> to 00:54:49.470 --> 00:54:49.480 align:start position:0% trying to 00:54:49.480 --> 00:54:52.910 align:start position:0% trying to alleviate<00:54:50.480> with<00:54:50.720> this<00:54:50.960> design<00:54:51.720> so<00:54:52.119> now<00:54:52.760> the 00:54:52.910 --> 00:54:52.920 align:start position:0% alleviate with this design so now the 00:54:52.920 --> 00:54:56.750 align:start position:0% alleviate with this design so now the pre-<00:54:53.160> confing<00:54:53.520> node<00:54:54.480> can<00:54:54.960> once<00:54:55.359> it<00:54:55.799> receives 00:54:56.750 --> 00:54:56.760 align:start position:0% pre- confing node can once it receives 00:54:56.760 --> 00:54:58.829 align:start position:0% pre- confing node can once it receives the<00:54:57.359> uh<00:54:57.520> pre-comp<00:54:58.000> message<00:54:58.280> with<00:54:58.400> the<00:54:58.520> pending 00:54:58.829 --> 00:54:58.839 align:start position:0% the uh pre-comp message with the pending 00:54:58.839 --> 00:55:00.950 align:start position:0% the uh pre-comp message with the pending transaction<00:54:59.359> list<00:54:59.960> it<00:55:00.119> can<00:55:00.359> provide<00:55:00.640> it<00:55:00.799> to 00:55:00.950 --> 00:55:00.960 align:start position:0% transaction list it can provide it to 00:55:00.960 --> 00:55:03.950 align:start position:0% transaction list it can provide it to Tao<00:55:01.680> driver<00:55:02.480> and<00:55:02.640> Tao<00:55:02.960> driver<00:55:03.319> can<00:55:03.559> basically 00:55:03.950 --> 00:55:03.960 align:start position:0% Tao driver and Tao driver can basically 00:55:03.960 --> 00:55:07.630 align:start position:0% Tao driver and Tao driver can basically Advance<00:55:04.400> the<00:55:04.599> head<00:55:05.200> of<00:55:05.480> Tao<00:55:06.480> in<00:55:06.720> around<00:55:07.319> 3 00:55:07.630 --> 00:55:07.640 align:start position:0% Advance the head of Tao in around 3 00:55:07.640 --> 00:55:10.589 align:start position:0% Advance the head of Tao in around 3 seconds<00:55:08.240> given<00:55:08.599> that<00:55:08.760> we<00:55:08.920> choose<00:55:09.160> a<00:55:09.319> 3sec<00:55:10.319> uh 00:55:10.589 --> 00:55:10.599 align:start position:0% seconds given that we choose a 3sec uh 00:55:10.599 --> 00:55:20.750 align:start position:0% seconds given that we choose a 3sec uh confirmation<00:55:11.240> Loop<00:55:12.240> um 00:55:20.750 --> 00:55:20.760 align:start position:0% 00:55:20.760 --> 00:55:23.829 align:start position:0% time<00:55:21.760> all<00:55:22.039> right 00:55:23.829 --> 00:55:23.839 align:start position:0% time all right 00:55:23.839 --> 00:55:27.069 align:start position:0% time all right so<00:55:24.839> the<00:55:25.200> the<00:55:25.319> nonpr<00:55:26.039> so<00:55:26.359> there<00:55:26.480> is<00:55:26.640> the<00:55:26.839> precc 00:55:27.069 --> 00:55:27.079 align:start position:0% so the the nonpr so there is the precc 00:55:27.079 --> 00:55:29.430 align:start position:0% so the the nonpr so there is the precc confing<00:55:27.440> node<00:55:27.960> so<00:55:28.280> this<00:55:28.400> is<00:55:28.920> the<00:55:29.079> previous 00:55:29.430 --> 00:55:29.440 align:start position:0% confing node so this is the previous 00:55:29.440 --> 00:55:31.510 align:start position:0% confing node so this is the previous slide<00:55:29.799> was<00:55:30.039> about<00:55:30.599> the<00:55:30.760> pre-c<00:55:31.000> confing<00:55:31.280> node 00:55:31.510 --> 00:55:31.520 align:start position:0% slide was about the pre-c confing node 00:55:31.520 --> 00:55:33.470 align:start position:0% slide was about the pre-c confing node so<00:55:31.680> once<00:55:31.920> it<00:55:32.079> pre-com<00:55:32.599> the<00:55:32.720> transaction<00:55:33.200> list 00:55:33.470 --> 00:55:33.480 align:start position:0% so once it pre-com the transaction list 00:55:33.480 --> 00:55:35.710 align:start position:0% so once it pre-com the transaction list it<00:55:33.599> does<00:55:33.880> this<00:55:34.520> and<00:55:34.640> there<00:55:34.760> is<00:55:35.000> also<00:55:35.319> the<00:55:35.440> non- 00:55:35.710 --> 00:55:35.720 align:start position:0% it does this and there is also the non- 00:55:35.720 --> 00:55:37.549 align:start position:0% it does this and there is also the non- preconfig<00:55:36.200> node<00:55:36.720> receiving<00:55:37.079> this<00:55:37.240> message 00:55:37.549 --> 00:55:37.559 align:start position:0% preconfig node receiving this message 00:55:37.559 --> 00:55:40.029 align:start position:0% preconfig node receiving this message through<00:55:37.799> P2P<00:55:38.760> and<00:55:38.920> then<00:55:39.039> sending<00:55:39.359> it<00:55:39.520> to<00:55:39.680> Tao 00:55:40.029 --> 00:55:40.039 align:start position:0% through P2P and then sending it to Tao 00:55:40.039 --> 00:55:42.270 align:start position:0% through P2P and then sending it to Tao priv<00:55:40.760> driver<00:55:41.119> to<00:55:41.280> advance<00:55:41.559> the<00:55:41.720> head<00:55:41.920> so<00:55:42.079> the 00:55:42.270 --> 00:55:42.280 align:start position:0% priv driver to advance the head so the 00:55:42.280 --> 00:55:44.109 align:start position:0% priv driver to advance the head so the whole<00:55:42.480> network<00:55:42.880> advances<00:55:43.480> together<00:55:43.720> and<00:55:43.920> not 00:55:44.109 --> 00:55:44.119 align:start position:0% whole network advances together and not 00:55:44.119 --> 00:55:54.789 align:start position:0% whole network advances together and not a<00:55:44.280> single<00:55:45.240> uh<00:55:45.400> one<00:55:45.599> of<00:55:45.839> the<00:55:46.240> nodes<00:55:46.760> in<00:55:46.880> the 00:55:54.789 --> 00:55:54.799 align:start position:0% 00:55:54.799 --> 00:55:57.109 align:start position:0% network<00:55:55.799> yep<00:55:56.319> so<00:55:56.440> we<00:55:56.559> already<00:55:56.839> kind<00:55:57.000> of 00:55:57.109 --> 00:55:57.119 align:start position:0% network yep so we already kind of 00:55:57.119 --> 00:56:01.630 align:start position:0% network yep so we already kind of discussed<00:55:57.599> this<00:55:58.119> so<00:55:59.119> um<00:55:59.799> we<00:56:00.079> have<00:56:01.039> two<00:56:01.319> ways 00:56:01.630 --> 00:56:01.640 align:start position:0% discussed this so um we have two ways 00:56:01.640 --> 00:56:02.950 align:start position:0% discussed this so um we have two ways that<00:56:01.799> the<00:56:01.920> pre<00:56:02.160> confer<00:56:02.440> sends<00:56:02.720> his 00:56:02.950 --> 00:56:02.960 align:start position:0% that the pre confer sends his 00:56:02.960 --> 00:56:05.670 align:start position:0% that the pre confer sends his transactions<00:56:03.760> or<00:56:04.119> that<00:56:04.480> the<00:56:04.640> L1<00:56:05.039> transactions 00:56:05.670 --> 00:56:05.680 align:start position:0% transactions or that the L1 transactions 00:56:05.680 --> 00:56:09.230 align:start position:0% transactions or that the L1 transactions that<00:56:05.799> will<00:56:06.039> basically<00:56:06.880> push<00:56:07.280> the<00:56:08.079> uh<00:56:08.200> L2<00:56:09.079> uh 00:56:09.230 --> 00:56:09.240 align:start position:0% that will basically push the uh L2 uh 00:56:09.240 --> 00:56:12.470 align:start position:0% that will basically push the uh L2 uh transaction<00:56:09.799> batches<00:56:10.760> so<00:56:11.079> first<00:56:11.839> we<00:56:11.960> said 00:56:12.470 --> 00:56:12.480 align:start position:0% transaction batches so first we said 00:56:12.480 --> 00:56:16.430 align:start position:0% transaction batches so first we said okay<00:56:13.480> let's<00:56:13.720> say<00:56:14.079> that<00:56:14.680> we<00:56:15.000> have<00:56:16.000> a<00:56:16.160> pre- 00:56:16.430 --> 00:56:16.440 align:start position:0% okay let's say that we have a pre- 00:56:16.440 --> 00:56:19.710 align:start position:0% okay let's say that we have a pre- confer<00:56:16.839> in<00:56:17.319> slot<00:56:17.680> number<00:56:18.119> five<00:56:19.119> and<00:56:19.319> this<00:56:19.480> prec 00:56:19.710 --> 00:56:19.720 align:start position:0% confer in slot number five and this prec 00:56:19.720 --> 00:56:22.470 align:start position:0% confer in slot number five and this prec confer<00:56:20.079> is<00:56:20.319> on<00:56:20.520> duty<00:56:20.839> for<00:56:21.039> slot<00:56:21.400> number<00:56:21.720> 1<00:56:21.960> 2<00:56:22.200> 3 00:56:22.470 --> 00:56:22.480 align:start position:0% confer is on duty for slot number 1 2 3 00:56:22.480 --> 00:56:25.230 align:start position:0% confer is on duty for slot number 1 2 3 4<00:56:22.880> and<00:56:23.160> five<00:56:24.000> that<00:56:24.119> means<00:56:24.480> that<00:56:24.640> they<00:56:24.760> need<00:56:24.920> to 00:56:25.230 --> 00:56:25.240 align:start position:0% 4 and five that means that they need to 00:56:25.240 --> 00:56:27.910 align:start position:0% 4 and five that means that they need to precon<00:56:26.319> a<00:56:26.440> lot<00:56:26.559> of<00:56:26.720> batches<00:56:27.440> on<00:56:27.599> in<00:56:27.760> these 00:56:27.910 --> 00:56:27.920 align:start position:0% precon a lot of batches on in these 00:56:27.920 --> 00:56:29.670 align:start position:0% precon a lot of batches on in these slots<00:56:28.359> and<00:56:28.480> then<00:56:28.640> they<00:56:28.760> can<00:56:28.920> force<00:56:29.319> include 00:56:29.670 --> 00:56:29.680 align:start position:0% slots and then they can force include 00:56:29.680 --> 00:56:31.750 align:start position:0% slots and then they can force include them<00:56:29.880> in<00:56:30.039> slot<00:56:30.400> number<00:56:30.720> five<00:56:31.280> and<00:56:31.440> that's<00:56:31.599> not 00:56:31.750 --> 00:56:31.760 align:start position:0% them in slot number five and that's not 00:56:31.760 --> 00:56:34.870 align:start position:0% them in slot number five and that's not a<00:56:31.960> problem<00:56:32.559> that's<00:56:32.799> easy<00:56:33.039> to<00:56:33.200> do<00:56:33.559> by<00:56:34.280> using<00:56:34.680> the 00:56:34.870 --> 00:56:34.880 align:start position:0% a problem that's easy to do by using the 00:56:34.880 --> 00:56:37.230 align:start position:0% a problem that's easy to do by using the PBS<00:56:35.319> software<00:56:35.720> like<00:56:35.880> we 00:56:37.230 --> 00:56:37.240 align:start position:0% PBS software like we 00:56:37.240 --> 00:56:40.549 align:start position:0% PBS software like we explained<00:56:38.240> um<00:56:38.680> the<00:56:38.880> problem<00:56:39.200> arises<00:56:39.839> if<00:56:40.400> there 00:56:40.549 --> 00:56:40.559 align:start position:0% explained um the problem arises if there 00:56:40.559 --> 00:56:43.510 align:start position:0% explained um the problem arises if there are<00:56:40.920> sparse<00:56:41.920> prec<00:56:42.200> Comforts<00:56:42.640> there<00:56:42.760> isn't<00:56:43.359> a 00:56:43.510 --> 00:56:43.520 align:start position:0% are sparse prec Comforts there isn't a 00:56:43.520 --> 00:56:46.190 align:start position:0% are sparse prec Comforts there isn't a lot<00:56:43.680> of<00:56:43.880> pre<00:56:44.319> Comforts<00:56:45.319> and<00:56:45.640> that<00:56:45.760> would<00:56:45.880> mean 00:56:46.190 --> 00:56:46.200 align:start position:0% lot of pre Comforts and that would mean 00:56:46.200 --> 00:56:47.789 align:start position:0% lot of pre Comforts and that would mean that<00:56:46.440> potentially<00:56:46.880> one<00:56:47.079> pre-<00:56:47.319> Comfort<00:56:47.640> could 00:56:47.789 --> 00:56:47.799 align:start position:0% that potentially one pre- Comfort could 00:56:47.799 --> 00:56:51.950 align:start position:0% that potentially one pre- Comfort could be<00:56:47.960> in<00:56:48.119> slot<00:56:48.520> number<00:56:49.599> 42<00:56:50.599> and<00:56:51.599> he's 00:56:51.950 --> 00:56:51.960 align:start position:0% be in slot number 42 and he's 00:56:51.960 --> 00:56:54.710 align:start position:0% be in slot number 42 and he's responsible<00:56:52.480> for<00:56:52.960> slot<00:56:53.960> uh<00:56:54.079> I<00:56:54.160> don't<00:56:54.319> know 00:56:54.710 --> 00:56:54.720 align:start position:0% responsible for slot uh I don't know 00:56:54.720 --> 00:56:57.670 align:start position:0% responsible for slot uh I don't know five<00:56:55.319> up<00:56:55.559> until<00:56:55.880> 40<00:56:56.359> to<00:56:56.960> and<00:56:57.119> this<00:56:57.240> would<00:56:57.400> mean 00:56:57.670 --> 00:56:57.680 align:start position:0% five up until 40 to and this would mean 00:56:57.680 --> 00:56:59.430 align:start position:0% five up until 40 to and this would mean that<00:56:57.839> he<00:56:57.960> needs<00:56:58.240> to<00:56:58.480> push<00:56:58.799> a<00:56:58.960> lot<00:56:59.160> of 00:56:59.430 --> 00:56:59.440 align:start position:0% that he needs to push a lot of 00:56:59.440 --> 00:57:02.470 align:start position:0% that he needs to push a lot of transactions<00:57:00.200> in<00:57:00.960> in<00:57:01.200> his<00:57:01.359> slot<00:57:01.760> if<00:57:01.880> we<00:57:02.039> follow 00:57:02.470 --> 00:57:02.480 align:start position:0% transactions in in his slot if we follow 00:57:02.480 --> 00:57:06.069 align:start position:0% transactions in in his slot if we follow this<00:57:02.799> model<00:57:03.760> so<00:57:03.960> instead<00:57:04.400> we<00:57:04.520> said<00:57:04.960> okay<00:57:05.799> maybe 00:57:06.069 --> 00:57:06.079 align:start position:0% this model so instead we said okay maybe 00:57:06.079 --> 00:57:08.630 align:start position:0% this model so instead we said okay maybe we<00:57:06.200> should<00:57:06.520> just<00:57:06.839> push<00:57:07.680> all<00:57:07.920> the<00:57:08.079> precom 00:57:08.630 --> 00:57:08.640 align:start position:0% we should just push all the precom 00:57:08.640 --> 00:57:10.910 align:start position:0% we should just push all the precom transactions<00:57:09.440> right<00:57:09.640> away<00:57:09.920> to<00:57:10.079> the 00:57:10.910 --> 00:57:10.920 align:start position:0% transactions right away to the 00:57:10.920 --> 00:57:15.470 align:start position:0% transactions right away to the mol<00:57:11.920> so<00:57:12.480> we<00:57:12.599> get<00:57:12.839> batch<00:57:13.079> a<00:57:13.400> batch<00:57:13.680> B<00:57:14.480> and<00:57:15.160> we 00:57:15.470 --> 00:57:15.480 align:start position:0% mol so we get batch a batch B and we 00:57:15.480 --> 00:57:17.910 align:start position:0% mol so we get batch a batch B and we just<00:57:15.760> push<00:57:16.079> them<00:57:16.359> directly<00:57:16.680> to<00:57:16.839> the<00:57:16.960> men<00:57:17.240> pool 00:57:17.910 --> 00:57:17.920 align:start position:0% just push them directly to the men pool 00:57:17.920 --> 00:57:19.670 align:start position:0% just push them directly to the men pool and<00:57:18.079> at<00:57:18.200> the<00:57:18.319> same<00:57:18.559> time<00:57:18.760> we<00:57:18.920> put<00:57:19.119> them<00:57:19.240> in<00:57:19.400> a 00:57:19.670 --> 00:57:19.680 align:start position:0% and at the same time we put them in a 00:57:19.680 --> 00:57:24.029 align:start position:0% and at the same time we put them in a Que<00:57:20.319> in<00:57:20.480> a<00:57:20.960> cache<00:57:22.079> and<00:57:23.079> the<00:57:23.319> idea<00:57:23.640> of<00:57:23.839> this 00:57:24.029 --> 00:57:24.039 align:start position:0% Que in a cache and the idea of this 00:57:24.039 --> 00:57:27.589 align:start position:0% Que in a cache and the idea of this cache<00:57:24.319> is<00:57:24.559> that<00:57:25.200> once<00:57:25.559> an<00:57:25.760> L1<00:57:26.240> block<00:57:26.799> comes<00:57:27.400> and 00:57:27.589 --> 00:57:27.599 align:start position:0% cache is that once an L1 block comes and 00:57:27.599 --> 00:57:30.710 align:start position:0% cache is that once an L1 block comes and it<00:57:27.920> has<00:57:28.319> those<00:57:29.319> uh<00:57:29.599> batch<00:57:30.000> transaction<00:57:30.599> that 00:57:30.710 --> 00:57:30.720 align:start position:0% it has those uh batch transaction that 00:57:30.720 --> 00:57:33.589 align:start position:0% it has those uh batch transaction that has<00:57:30.880> been<00:57:31.039> pushed<00:57:31.480> here<00:57:32.200> in<00:57:32.400> it<00:57:33.039> then<00:57:33.240> we<00:57:33.359> can 00:57:33.589 --> 00:57:33.599 align:start position:0% has been pushed here in it then we can 00:57:33.599 --> 00:57:35.829 align:start position:0% has been pushed here in it then we can remove<00:57:34.160> this<00:57:34.400> batch<00:57:34.720> from<00:57:35.000> the 00:57:35.829 --> 00:57:35.839 align:start position:0% remove this batch from the 00:57:35.839 --> 00:57:39.630 align:start position:0% remove this batch from the cash<00:57:36.960> if<00:57:37.960> if<00:57:38.200> that<00:57:38.359> doesn't<00:57:38.720> happen<00:57:39.079> then<00:57:39.280> the 00:57:39.630 --> 00:57:39.640 align:start position:0% cash if if that doesn't happen then the 00:57:39.640 --> 00:57:41.870 align:start position:0% cash if if that doesn't happen then the batch<00:57:39.880> of<00:57:40.079> trans<00:57:40.480> if<00:57:40.640> L2<00:57:41.079> transaction<00:57:41.599> stays 00:57:41.870 --> 00:57:41.880 align:start position:0% batch of trans if L2 transaction stays 00:57:41.880 --> 00:57:46.829 align:start position:0% batch of trans if L2 transaction stays in<00:57:42.039> the<00:57:42.359> cash<00:57:43.359> and<00:57:43.720> then<00:57:44.520> once<00:57:44.839> it<00:57:45.079> is<00:57:46.079> yeah<00:57:46.480> and 00:57:46.829 --> 00:57:46.839 align:start position:0% in the cash and then once it is yeah and 00:57:46.839 --> 00:57:49.390 align:start position:0% in the cash and then once it is yeah and so<00:57:47.160> basically<00:57:47.640> if<00:57:47.799> it's<00:57:48.240> if<00:57:48.400> it's<00:57:48.839> U<00:57:49.119> if<00:57:49.200> it's 00:57:49.390 --> 00:57:49.400 align:start position:0% so basically if it's if it's U if it's 00:57:49.400 --> 00:57:52.510 align:start position:0% so basically if it's if it's U if it's included<00:57:50.319> we<00:57:50.520> clear<00:57:51.280> that<00:57:51.520> batch<00:57:51.920> from<00:57:52.240> the 00:57:52.510 --> 00:57:52.520 align:start position:0% included we clear that batch from the 00:57:52.520 --> 00:57:59.349 align:start position:0% included we clear that batch from the from<00:57:52.720> the<00:57:52.920> cache 00:57:59.349 --> 00:57:59.359 align:start position:0% 00:57:59.359 --> 00:58:02.150 align:start position:0% okay<00:58:00.039> so<00:58:00.240> on<00:58:00.440> the<00:58:00.599> proposal 00:58:02.150 --> 00:58:02.160 align:start position:0% okay so on the proposal 00:58:02.160 --> 00:58:06.910 align:start position:0% okay so on the proposal slot<00:58:03.160> we<00:58:03.359> take<00:58:04.200> the<00:58:04.680> ones<00:58:05.039> that<00:58:05.280> hasn't<00:58:05.599> been 00:58:06.910 --> 00:58:06.920 align:start position:0% slot we take the ones that hasn't been 00:58:06.920 --> 00:58:09.589 align:start position:0% slot we take the ones that hasn't been included<00:58:07.920> uh<00:58:08.400> that<00:58:08.559> we<00:58:08.720> pushed<00:58:09.000> to<00:58:09.079> the<00:58:09.200> m<00:58:09.440> pole 00:58:09.589 --> 00:58:09.599 align:start position:0% included uh that we pushed to the m pole 00:58:09.599 --> 00:58:12.470 align:start position:0% included uh that we pushed to the m pole and<00:58:09.760> hasn't<00:58:10.000> been<00:58:10.160> included<00:58:10.720> yet<00:58:11.400> and<00:58:11.680> we<00:58:12.240> make 00:58:12.470 --> 00:58:12.480 align:start position:0% and hasn't been included yet and we make 00:58:12.480 --> 00:58:14.549 align:start position:0% and hasn't been included yet and we make sure<00:58:12.960> that<00:58:13.520> we<00:58:13.720> push<00:58:14.000> them<00:58:14.160> through<00:58:14.359> the 00:58:14.549 --> 00:58:14.559 align:start position:0% sure that we push them through the 00:58:14.559 --> 00:58:17.470 align:start position:0% sure that we push them through the constraints<00:58:15.160> API<00:58:15.720> of<00:58:15.920> Bolt<00:58:16.200> Smith<00:58:16.480> boost<00:58:17.280> to 00:58:17.470 --> 00:58:17.480 align:start position:0% constraints API of Bolt Smith boost to 00:58:17.480 --> 00:58:20.470 align:start position:0% constraints API of Bolt Smith boost to be<00:58:17.839> forc<00:58:18.280> included<00:58:18.839> by<00:58:18.960> the<00:58:19.079> Builder<00:58:20.000> and<00:58:20.240> then 00:58:20.470 --> 00:58:20.480 align:start position:0% be forc included by the Builder and then 00:58:20.480 --> 00:58:23.309 align:start position:0% be forc included by the Builder and then once<00:58:20.720> we<00:58:20.880> receive<00:58:21.200> the<00:58:21.319> L1<00:58:22.039> block<00:58:22.799> we<00:58:22.960> have<00:58:23.160> the 00:58:23.309 --> 00:58:23.319 align:start position:0% once we receive the L1 block we have the 00:58:23.319 --> 00:58:25.589 align:start position:0% once we receive the L1 block we have the guarantee<00:58:23.760> from<00:58:23.960> the<00:58:24.079> relayer<00:58:25.039> that<00:58:25.280> these 00:58:25.589 --> 00:58:25.599 align:start position:0% guarantee from the relayer that these 00:58:25.599 --> 00:58:27.309 align:start position:0% guarantee from the relayer that these transaction 00:58:27.309 --> 00:58:27.319 align:start position:0% transaction 00:58:27.319 --> 00:58:29.829 align:start position:0% transaction uh<00:58:27.839> uh<00:58:28.119> L1<00:58:28.559> transactions<00:58:29.240> that<00:58:29.400> contain<00:58:29.720> the 00:58:29.829 --> 00:58:29.839 align:start position:0% uh uh L1 transactions that contain the 00:58:29.839 --> 00:58:32.549 align:start position:0% uh uh L1 transactions that contain the L2<00:58:30.240> transaction<00:58:30.760> batches<00:58:31.480> are<00:58:31.720> included<00:58:32.319> then 00:58:32.549 --> 00:58:32.559 align:start position:0% L2 transaction batches are included then 00:58:32.559 --> 00:58:41.670 align:start position:0% L2 transaction batches are included then in<00:58:32.839> the<00:58:33.480> uh<00:58:33.599> L1<00:58:34.079> proposed<00:58:34.440> L1 00:58:41.670 --> 00:58:41.680 align:start position:0% 00:58:41.680 --> 00:58:45.349 align:start position:0% block<00:58:42.680> and<00:58:42.880> she<00:58:43.119> will<00:58:43.400> talk<00:58:43.760> about<00:58:44.359> slashing 00:58:45.349 --> 00:58:45.359 align:start position:0% block and she will talk about slashing 00:58:45.359 --> 00:58:51.309 align:start position:0% block and she will talk about slashing and 00:58:51.309 --> 00:58:51.319 align:start position:0% 00:58:51.319 --> 00:58:58.670 align:start position:0% yeah<00:58:52.319> got<00:58:53.000> yeah 00:58:58.670 --> 00:58:58.680 align:start position:0% 00:58:58.680 --> 00:59:01.430 align:start position:0% okay<00:58:59.680> so<00:58:59.880> now<00:59:00.119> comes<00:59:00.440> the<00:59:00.880> pre-confirmation 00:59:01.430 --> 00:59:01.440 align:start position:0% okay so now comes the pre-confirmation 00:59:01.440 --> 00:59:03.270 align:start position:0% okay so now comes the pre-confirmation service<00:59:02.079> manager<00:59:02.599> contract<00:59:03.039> which<00:59:03.160> we 00:59:03.270 --> 00:59:03.280 align:start position:0% service manager contract which we 00:59:03.280 --> 00:59:06.150 align:start position:0% service manager contract which we haven't<00:59:03.520> spoken<00:59:03.839> about<00:59:04.200> yet<00:59:05.200> and<00:59:05.400> this<00:59:05.520> is<00:59:06.000> a 00:59:06.150 --> 00:59:06.160 align:start position:0% haven't spoken about yet and this is a 00:59:06.160 --> 00:59:07.950 align:start position:0% haven't spoken about yet and this is a very<00:59:06.359> interesting<00:59:06.839> contract<00:59:07.319> because<00:59:07.799> what 00:59:07.950 --> 00:59:07.960 align:start position:0% very interesting contract because what 00:59:07.960 --> 00:59:10.349 align:start position:0% very interesting contract because what we<00:59:08.079> have<00:59:08.240> tried<00:59:08.440> to<00:59:08.599> achieve<00:59:08.920> with<00:59:09.079> this<00:59:09.240> PC<00:59:09.839> is 00:59:10.349 --> 00:59:10.359 align:start position:0% we have tried to achieve with this PC is 00:59:10.359 --> 00:59:13.109 align:start position:0% we have tried to achieve with this PC is a<00:59:10.520> really<00:59:10.799> flexible<00:59:11.640> interfacing<00:59:12.640> because<00:59:12.920> we 00:59:13.109 --> 00:59:13.119 align:start position:0% a really flexible interfacing because we 00:59:13.119 --> 00:59:15.190 align:start position:0% a really flexible interfacing because we have<00:59:13.359> a<00:59:13.480> number<00:59:13.760> of<00:59:13.880> reaking<00:59:14.440> solutions<00:59:15.039> right 00:59:15.190 --> 00:59:15.200 align:start position:0% have a number of reaking solutions right 00:59:15.200 --> 00:59:18.029 align:start position:0% have a number of reaking solutions right now<00:59:15.400> out<00:59:15.720> there<00:59:16.359> in<00:59:16.559> the<00:59:16.920> in<00:59:17.039> the<00:59:17.200> market<00:59:17.880> we 00:59:18.029 --> 00:59:18.039 align:start position:0% now out there in the in the market we 00:59:18.039 --> 00:59:20.589 align:start position:0% now out there in the in the market we have<00:59:18.200> ananl<00:59:18.720> we<00:59:18.839> have<00:59:19.000> kak<00:59:19.480> we<00:59:19.880> we<00:59:20.079> might<00:59:20.319> also 00:59:20.589 --> 00:59:20.599 align:start position:0% have ananl we have kak we we might also 00:59:20.599 --> 00:59:22.870 align:start position:0% have ananl we have kak we we might also have<00:59:21.039> our<00:59:21.200> own<00:59:21.400> staking<00:59:21.880> contract<00:59:22.280> later<00:59:22.520> on 00:59:22.870 --> 00:59:22.880 align:start position:0% have our own staking contract later on 00:59:22.880 --> 00:59:25.150 align:start position:0% have our own staking contract later on if<00:59:23.039> a<00:59:23.200> community<00:59:23.640> decides<00:59:23.960> on<00:59:24.119> one<00:59:24.400> which<00:59:25.000> uh 00:59:25.150 --> 00:59:25.160 align:start position:0% if a community decides on one which uh 00:59:25.160 --> 00:59:26.670 align:start position:0% if a community decides on one which uh is<00:59:25.319> actually<00:59:25.599> going<00:59:25.799> on 00:59:26.670 --> 00:59:26.680 align:start position:0% is actually going on 00:59:26.680 --> 00:59:28.029 align:start position:0% is actually going on a<00:59:26.839> discussion<00:59:27.160> is<00:59:27.319> going<00:59:27.480> on<00:59:27.599> on<00:59:27.760> having<00:59:27.960> a 00:59:28.029 --> 00:59:28.039 align:start position:0% a discussion is going on on having a 00:59:28.039 --> 00:59:29.230 align:start position:0% a discussion is going on on having a unified 00:59:29.230 --> 00:59:29.240 align:start position:0% unified 00:59:29.240 --> 00:59:32.230 align:start position:0% unified registry<00:59:30.240> and<00:59:30.760> that<00:59:30.960> calls<00:59:31.240> for<00:59:31.559> having<00:59:32.000> some 00:59:32.230 --> 00:59:32.240 align:start position:0% registry and that calls for having some 00:59:32.240 --> 00:59:34.190 align:start position:0% registry and that calls for having some kind<00:59:32.359> of<00:59:32.480> a<00:59:32.559> middleware<00:59:33.119> contract<00:59:33.720> so<00:59:33.920> that 00:59:34.190 --> 00:59:34.200 align:start position:0% kind of a middleware contract so that 00:59:34.200 --> 00:59:35.870 align:start position:0% kind of a middleware contract so that later<00:59:34.480> on<00:59:34.680> the<00:59:34.799> code<00:59:35.079> logic<00:59:35.400> doesn't<00:59:35.640> have<00:59:35.760> to 00:59:35.870 --> 00:59:35.880 align:start position:0% later on the code logic doesn't have to 00:59:35.880 --> 00:59:38.069 align:start position:0% later on the code logic doesn't have to be<00:59:36.000> changed<00:59:36.760> and<00:59:36.880> the<00:59:37.000> staking<00:59:37.440> is<00:59:37.680> just 00:59:38.069 --> 00:59:38.079 align:start position:0% be changed and the staking is just 00:59:38.079 --> 00:59:40.270 align:start position:0% be changed and the staking is just abstracted<00:59:38.640> away<00:59:38.880> to<00:59:39.039> a<00:59:39.200> different<00:59:39.520> set<00:59:39.960> of 00:59:40.270 --> 00:59:40.280 align:start position:0% abstracted away to a different set of 00:59:40.280 --> 00:59:42.349 align:start position:0% abstracted away to a different set of contracts<00:59:41.280> and<00:59:41.440> that's<00:59:41.640> what<00:59:41.799> we<00:59:42.000> achieve 00:59:42.349 --> 00:59:42.359 align:start position:0% contracts and that's what we achieve 00:59:42.359 --> 00:59:44.549 align:start position:0% contracts and that's what we achieve with<00:59:42.480> the<00:59:42.559> service<00:59:42.880> manager<00:59:43.680> is<00:59:44.039> essentially 00:59:44.549 --> 00:59:44.559 align:start position:0% with the service manager is essentially 00:59:44.559 --> 00:59:46.870 align:start position:0% with the service manager is essentially like<00:59:44.680> a<00:59:44.799> middle<00:59:45.079> wear<00:59:45.760> that<00:59:45.960> ensures<00:59:46.559> that 00:59:46.870 --> 00:59:46.880 align:start position:0% like a middle wear that ensures that 00:59:46.880 --> 00:59:48.950 align:start position:0% like a middle wear that ensures that only<00:59:47.240> those<00:59:47.480> proposers<00:59:47.960> who<00:59:48.119> have<00:59:48.240> a<00:59:48.440> required 00:59:48.950 --> 00:59:48.960 align:start position:0% only those proposers who have a required 00:59:48.960 --> 00:59:52.270 align:start position:0% only those proposers who have a required stake<00:59:49.640> are<00:59:49.920> allowed<00:59:50.319> to<00:59:50.520> precom<00:59:51.079> or<00:59:51.280> propose 00:59:52.270 --> 00:59:52.280 align:start position:0% stake are allowed to precom or propose 00:59:52.280 --> 00:59:53.950 align:start position:0% stake are allowed to precom or propose in<00:59:52.440> in<00:59:52.640> the<00:59:52.880> upcoming<00:59:53.319> blocks<00:59:53.720> in<00:59:53.839> the 00:59:53.950 --> 00:59:53.960 align:start position:0% in in the upcoming blocks in the 00:59:53.960 --> 00:59:57.589 align:start position:0% in in the upcoming blocks in the upcoming<00:59:54.319> slots 00:59:57.589 --> 00:59:57.599 align:start position:0% 00:59:57.599 --> 00:59:59.270 align:start position:0% so<00:59:57.799> what<00:59:57.960> kind<00:59:58.079> of<00:59:58.200> slashings<00:59:58.680> do<00:59:58.799> we<00:59:58.960> have<00:59:59.119> or 00:59:59.270 --> 00:59:59.280 align:start position:0% so what kind of slashings do we have or 00:59:59.280 --> 01:00:02.589 align:start position:0% so what kind of slashings do we have or when<00:59:59.520> exactly<00:59:59.839> do<00:59:59.960> we<01:00:00.200> slash<01:00:01.200> well<01:00:02.119> one<01:00:02.440> one 01:00:02.589 --> 01:00:02.599 align:start position:0% when exactly do we slash well one one 01:00:02.599 --> 01:00:05.029 align:start position:0% when exactly do we slash well one one time<01:00:02.799> do<01:00:02.960> we<01:00:03.119> that<01:00:03.280> we<01:00:03.559> do<01:00:03.760> slashes<01:00:04.520> when<01:00:04.920> the 01:00:05.029 --> 01:00:05.039 align:start position:0% time do we that we do slashes when the 01:00:05.039 --> 01:00:06.950 align:start position:0% time do we that we do slashes when the look<01:00:05.280> ahead<01:00:05.559> being<01:00:05.760> posted<01:00:06.200> is<01:00:06.359> incorrect<01:00:06.839> or 01:00:06.950 --> 01:00:06.960 align:start position:0% look ahead being posted is incorrect or 01:00:06.960 --> 01:00:09.390 align:start position:0% look ahead being posted is incorrect or the<01:00:07.039> look<01:00:07.240> ahead<01:00:07.480> posted<01:00:07.839> is 01:00:09.390 --> 01:00:09.400 align:start position:0% the look ahead posted is 01:00:09.400 --> 01:00:11.750 align:start position:0% the look ahead posted is incorrect<01:00:10.400> a<01:00:10.599> basic<01:00:10.920> version<01:00:11.240> of<01:00:11.400> this<01:00:11.559> is 01:00:11.750 --> 01:00:11.760 align:start position:0% incorrect a basic version of this is 01:00:11.760 --> 01:00:15.630 align:start position:0% incorrect a basic version of this is that<01:00:12.319> when<01:00:12.480> you<01:00:12.920> have<01:00:13.920> uh<01:00:14.200> like<01:00:14.400> let's<01:00:14.599> say<01:00:15.079> for 01:00:15.630 --> 01:00:15.640 align:start position:0% that when you have uh like let's say for 01:00:15.640 --> 01:00:19.109 align:start position:0% that when you have uh like let's say for a<01:00:15.799> validator<01:00:16.359> with<01:00:16.559> BLS<01:00:17.039> key<01:00:17.400> BLS<01:00:17.799> public<01:00:18.079> key 01:00:19.109 --> 01:00:19.119 align:start position:0% a validator with BLS key BLS public key 01:00:19.119 --> 01:00:23.230 align:start position:0% a validator with BLS key BLS public key B5<01:00:20.119> uh<01:00:20.359> in<01:00:20.480> the<01:00:20.680> look<01:00:20.880> ahead<01:00:21.799> mapping<01:00:22.799> uh<01:00:23.000> in<01:00:23.119> in 01:00:23.230 --> 01:00:23.240 align:start position:0% B5 uh in the look ahead mapping uh in in 01:00:23.240 --> 01:00:26.789 align:start position:0% B5 uh in the look ahead mapping uh in in sorry<01:00:23.480> in<01:00:23.559> the<01:00:23.640> BLS<01:00:24.039> mapping<01:00:24.400> you<01:00:24.599> have<01:00:25.280> E4<01:00:26.119> as 01:00:26.789 --> 01:00:26.799 align:start position:0% sorry in the BLS mapping you have E4 as 01:00:26.799 --> 01:00:29.190 align:start position:0% sorry in the BLS mapping you have E4 as the<01:00:27.039> associated<01:00:27.720> individual<01:00:28.359> who<01:00:28.520> owns<01:00:28.960> the 01:00:29.190 --> 01:00:29.200 align:start position:0% the associated individual who owns the 01:00:29.200 --> 01:00:31.710 align:start position:0% the associated individual who owns the B5<01:00:29.680> key<01:00:30.480> but<01:00:30.680> the<01:00:30.839> proposer<01:00:31.240> who<01:00:31.359> pushed<01:00:31.640> the 01:00:31.710 --> 01:00:31.720 align:start position:0% B5 key but the proposer who pushed the 01:00:31.720 --> 01:00:36.069 align:start position:0% B5 key but the proposer who pushed the look<01:00:32.400> ahead<01:00:33.400> placed<01:00:33.960> E2<01:00:34.680> as<01:00:35.160> the<01:00:35.359> associated 01:00:36.069 --> 01:00:36.079 align:start position:0% look ahead placed E2 as the associated 01:00:36.079 --> 01:00:38.990 align:start position:0% look ahead placed E2 as the associated ecdsa<01:00:36.799> key<01:00:37.039> which<01:00:37.160> is<01:00:37.760> factually 01:00:38.990 --> 01:00:39.000 align:start position:0% ecdsa key which is factually 01:00:39.000 --> 01:00:41.069 align:start position:0% ecdsa key which is factually incorrect<01:00:40.000> now<01:00:40.200> this<01:00:40.359> might<01:00:40.520> look<01:00:40.720> like<01:00:40.880> an 01:00:41.069 --> 01:00:41.079 align:start position:0% incorrect now this might look like an 01:00:41.079 --> 01:00:43.589 align:start position:0% incorrect now this might look like an easy<01:00:41.599> way<01:00:41.760> to<01:00:42.039> just<01:00:42.319> compare<01:00:42.839> hey<01:00:43.160> okay<01:00:43.440> both 01:00:43.589 --> 01:00:43.599 align:start position:0% easy way to just compare hey okay both 01:00:43.599 --> 01:00:47.309 align:start position:0% easy way to just compare hey okay both of<01:00:43.799> these<01:00:44.000> are<01:00:44.520> not<01:00:45.160> really<01:00:46.160> equal<01:00:46.559> so<01:00:47.000> why<01:00:47.119> not 01:00:47.309 --> 01:00:47.319 align:start position:0% of these are not really equal so why not 01:00:47.319 --> 01:00:49.309 align:start position:0% of these are not really equal so why not we<01:00:47.440> slash<01:00:48.160> the<01:00:48.359> the<01:00:48.559> person<01:00:48.799> who<01:00:48.920> posted<01:00:49.240> a 01:00:49.309 --> 01:00:49.319 align:start position:0% we slash the the person who posted a 01:00:49.319 --> 01:00:52.430 align:start position:0% we slash the the person who posted a look<01:00:49.480> ahead<01:00:49.799> but<01:00:50.680> it's<01:00:50.880> kind<01:00:51.039> of<01:00:51.240> tricky<01:00:51.960> to 01:00:52.430 --> 01:00:52.440 align:start position:0% look ahead but it's kind of tricky to 01:00:52.440 --> 01:00:56.150 align:start position:0% look ahead but it's kind of tricky to prove<01:00:52.839> this<01:00:53.400> inequality<01:00:54.319> because<01:00:55.200> we<01:00:55.400> have<01:00:55.599> B 01:00:56.150 --> 01:00:56.160 align:start position:0% prove this inequality because we have B 01:00:56.160 --> 01:00:58.870 align:start position:0% prove this inequality because we have B and<01:00:56.280> E4<01:00:56.960> from<01:00:57.319> the<01:00:57.480> pre-confirmation 01:00:58.870 --> 01:00:58.880 align:start position:0% and E4 from the pre-confirmation 01:00:58.880 --> 01:01:02.470 align:start position:0% and E4 from the pre-confirmation registry<01:00:59.880> but<01:01:00.559> in<01:01:00.839> the<01:01:01.039> task<01:01:01.359> manager<01:01:02.359> we 01:01:02.470 --> 01:01:02.480 align:start position:0% registry but in the task manager we 01:01:02.480 --> 01:01:04.950 align:start position:0% registry but in the task manager we don't<01:01:02.760> have<01:01:02.960> access<01:01:03.200> to<01:01:03.359> who<01:01:03.520> exactly<01:01:04.039> was<01:01:04.760> the 01:01:04.950 --> 01:01:04.960 align:start position:0% don't have access to who exactly was the 01:01:04.960 --> 01:01:08.670 align:start position:0% don't have access to who exactly was the BLS<01:01:05.680> the<01:01:05.880> the<01:01:06.680> validator<01:01:07.680> and<01:01:08.000> its<01:01:08.200> Associated 01:01:08.670 --> 01:01:08.680 align:start position:0% BLS the the validator and its Associated 01:01:08.680 --> 01:01:11.190 align:start position:0% BLS the the validator and its Associated BLS<01:01:09.079> key<01:01:09.359> for<01:01:09.520> the<01:01:09.640> current<01:01:09.960> slot<01:01:10.440> or<01:01:10.640> any<01:01:10.839> slot 01:01:11.190 --> 01:01:11.200 align:start position:0% BLS key for the current slot or any slot 01:01:11.200 --> 01:01:13.510 align:start position:0% BLS key for the current slot or any slot that<01:01:11.319> is<01:01:11.440> incorrect<01:01:11.880> we<01:01:12.079> don't<01:01:12.480> have<01:01:13.079> that 01:01:13.510 --> 01:01:13.520 align:start position:0% that is incorrect we don't have that 01:01:13.520 --> 01:01:16.870 align:start position:0% that is incorrect we don't have that information<01:01:14.319> in<01:01:14.839> like<01:01:15.079> s<01:01:15.359> in<01:01:15.440> a<01:01:15.599> simple 01:01:16.870 --> 01:01:16.880 align:start position:0% information in like s in a simple 01:01:16.880 --> 01:01:19.029 align:start position:0% information in like s in a simple way<01:01:17.880> and<01:01:18.039> what<01:01:18.160> we<01:01:18.280> need<01:01:18.440> to<01:01:18.559> do<01:01:18.760> is<01:01:18.880> we 01:01:19.029 --> 01:01:19.039 align:start position:0% way and what we need to do is we 01:01:19.039 --> 01:01:21.910 align:start position:0% way and what we need to do is we basically<01:01:19.400> need<01:01:19.559> to<01:01:20.119> have<01:01:21.119> uh<01:01:21.319> this<01:01:21.480> kind<01:01:21.640> of<01:01:21.760> a 01:01:21.910 --> 01:01:21.920 align:start position:0% basically need to have uh this kind of a 01:01:21.920 --> 01:01:24.230 align:start position:0% basically need to have uh this kind of a match<01:01:22.400> that<01:01:22.640> okay<01:01:22.880> B5<01:01:23.880> from<01:01:24.079> the 01:01:24.230 --> 01:01:24.240 align:start position:0% match that okay B5 from the 01:01:24.240 --> 01:01:26.430 align:start position:0% match that okay B5 from the pre-confirmation<01:01:24.640> registry<01:01:25.520> and<01:01:25.680> B<01:01:26.079> 5<01:01:26.240> in<01:01:26.359> the 01:01:26.430 --> 01:01:26.440 align:start position:0% pre-confirmation registry and B 5 in the 01:01:26.440 --> 01:01:28.910 align:start position:0% pre-confirmation registry and B 5 in the current<01:01:26.720> slot<01:01:27.480> both<01:01:27.680> of<01:01:27.839> them<01:01:28.079> have<01:01:28.359> different 01:01:28.910 --> 01:01:28.920 align:start position:0% current slot both of them have different 01:01:28.920 --> 01:01:31.829 align:start position:0% current slot both of them have different ecdsa<01:01:29.599> keys<01:01:30.480> and<01:01:30.640> then<01:01:30.920> B<01:01:31.079> on<01:01:31.200> the<01:01:31.319> basis<01:01:31.599> of 01:01:31.829 --> 01:01:31.839 align:start position:0% ecdsa keys and then B on the basis of 01:01:31.839 --> 01:01:34.630 align:start position:0% ecdsa keys and then B on the basis of that<01:01:32.200> we<01:01:32.400> slash<01:01:33.000> the<01:01:33.160> pre<01:01:33.680> the<01:01:34.039> poster<01:01:34.440> of<01:01:34.559> the 01:01:34.630 --> 01:01:34.640 align:start position:0% that we slash the pre the poster of the 01:01:34.640 --> 01:01:36.750 align:start position:0% that we slash the pre the poster of the look 01:01:36.750 --> 01:01:36.760 align:start position:0% look 01:01:36.760 --> 01:01:40.029 align:start position:0% look ahead<01:01:37.760> so<01:01:38.000> well<01:01:38.200> there<01:01:38.359> is<01:01:38.559> a<01:01:38.760> way<01:01:38.920> to<01:01:39.119> do<01:01:39.359> that 01:01:40.029 --> 01:01:40.039 align:start position:0% ahead so well there is a way to do that 01:01:40.039 --> 01:01:41.710 align:start position:0% ahead so well there is a way to do that and<01:01:40.359> I<01:01:40.480> kind<01:01:40.640> of<01:01:40.799> have<01:01:40.920> to<01:01:41.079> make<01:01:41.240> a<01:01:41.359> correction 01:01:41.710 --> 01:01:41.720 align:start position:0% and I kind of have to make a correction 01:01:41.720 --> 01:01:45.390 align:start position:0% and I kind of have to make a correction on<01:01:41.960> my<01:01:42.680> previous<01:01:43.680> uh<01:01:43.960> statement<01:01:44.960> that<01:01:45.280> there 01:01:45.390 --> 01:01:45.400 align:start position:0% on my previous uh statement that there 01:01:45.400 --> 01:01:47.109 align:start position:0% on my previous uh statement that there is<01:01:45.599> no<01:01:45.839> connection<01:01:46.240> between<01:01:46.520> the<01:01:46.680> consensus 01:01:47.109 --> 01:01:47.119 align:start position:0% is no connection between the consensus 01:01:47.119 --> 01:01:49.390 align:start position:0% is no connection between the consensus layer<01:01:47.359> and<01:01:47.520> execution<01:01:47.920> layer<01:01:48.520> well<01:01:48.720> there<01:01:48.920> is 01:01:49.390 --> 01:01:49.400 align:start position:0% layer and execution layer well there is 01:01:49.400 --> 01:01:51.230 align:start position:0% layer and execution layer well there is but<01:01:49.760> it's<01:01:50.280> kind<01:01:50.440> of<01:01:50.559> a<01:01:50.720> complicated 01:01:51.230 --> 01:01:51.240 align:start position:0% but it's kind of a complicated 01:01:51.240 --> 01:01:53.069 align:start position:0% but it's kind of a complicated connection<01:01:52.240> and<01:01:52.359> that's<01:01:52.520> through<01:01:52.720> the<01:01:52.799> beacon 01:01:53.069 --> 01:01:53.079 align:start position:0% connection and that's through the beacon 01:01:53.079 --> 01:01:54.630 align:start position:0% connection and that's through the beacon block<01:01:53.319> route<01:01:53.599> which<01:01:53.760> I<01:01:53.839> think<01:01:54.079> Emma<01:01:54.359> touched 01:01:54.630 --> 01:01:54.640 align:start position:0% block route which I think Emma touched 01:01:54.640 --> 01:01:56.589 align:start position:0% block route which I think Emma touched upon<01:01:54.880> briefly 01:01:56.589 --> 01:01:56.599 align:start position:0% upon briefly 01:01:56.599 --> 01:01:58.950 align:start position:0% upon briefly so<01:01:57.119> you<01:01:57.279> see<01:01:57.640> just<01:01:57.799> like<01:01:57.960> the<01:01:58.119> consensus<01:01:58.640> layer 01:01:58.950 --> 01:01:58.960 align:start position:0% so you see just like the consensus layer 01:01:58.960 --> 01:02:01.470 align:start position:0% so you see just like the consensus layer has<01:01:59.240> blocks<01:01:59.960> sorry<01:02:00.319> the<01:02:00.599> execution<01:02:01.000> layer<01:02:01.319> has 01:02:01.470 --> 01:02:01.480 align:start position:0% has blocks sorry the execution layer has 01:02:01.480 --> 01:02:03.510 align:start position:0% has blocks sorry the execution layer has blocks<01:02:01.799> that<01:02:01.960> we<01:02:02.079> deal<01:02:02.359> with<01:02:02.880> the<01:02:03.039> consensus 01:02:03.510 --> 01:02:03.520 align:start position:0% blocks that we deal with the consensus 01:02:03.520 --> 01:02:06.029 align:start position:0% blocks that we deal with the consensus layer<01:02:03.799> also<01:02:04.200> has<01:02:04.440> Beacon<01:02:04.839> blocks<01:02:05.799> because 01:02:06.029 --> 01:02:06.039 align:start position:0% layer also has Beacon blocks because 01:02:06.039 --> 01:02:07.390 align:start position:0% layer also has Beacon blocks because it's<01:02:06.200> the<01:02:06.319> beacon 01:02:07.390 --> 01:02:07.400 align:start position:0% it's the beacon 01:02:07.400 --> 01:02:11.470 align:start position:0% it's the beacon chain<01:02:08.400> and<01:02:08.839> each<01:02:09.079> beacon<01:02:09.440> block<01:02:10.240> has<01:02:10.920> a<01:02:11.079> state 01:02:11.470 --> 01:02:11.480 align:start position:0% chain and each beacon block has a state 01:02:11.480 --> 01:02:13.750 align:start position:0% chain and each beacon block has a state route<01:02:12.480> and<01:02:12.720> if<01:02:12.839> you 01:02:13.750 --> 01:02:13.760 align:start position:0% route and if you 01:02:13.760 --> 01:02:17.750 align:start position:0% route and if you unravel<01:02:14.760> like<01:02:15.039> the<01:02:15.319> entire<01:02:15.720> state<01:02:16.240> tree<01:02:17.240> then 01:02:17.750 --> 01:02:17.760 align:start position:0% unravel like the entire state tree then 01:02:17.760 --> 01:02:19.349 align:start position:0% unravel like the entire state tree then you'll<01:02:18.000> realize<01:02:18.359> that<01:02:18.480> in<01:02:18.599> Beacon<01:02:18.920> State<01:02:19.200> we 01:02:19.349 --> 01:02:19.359 align:start position:0% you'll realize that in Beacon State we 01:02:19.359 --> 01:02:21.430 align:start position:0% you'll realize that in Beacon State we have<01:02:19.640> the<01:02:19.880> validators<01:02:20.400> field<01:02:20.760> which<01:02:20.920> contains 01:02:21.430 --> 01:02:21.440 align:start position:0% have the validators field which contains 01:02:21.440 --> 01:02:23.789 align:start position:0% have the validators field which contains all<01:02:21.640> the<01:02:21.880> validators<01:02:22.880> or<01:02:23.079> the 01:02:23.789 --> 01:02:23.799 align:start position:0% all the validators or the 01:02:23.799 --> 01:02:26.309 align:start position:0% all the validators or the proposers<01:02:24.799> uh<01:02:25.039> and<01:02:25.200> that<01:02:25.319> includes<01:02:25.720> the<01:02:25.960> their 01:02:26.309 --> 01:02:26.319 align:start position:0% proposers uh and that includes the their 01:02:26.319 --> 01:02:30.549 align:start position:0% proposers uh and that includes the their unique<01:02:26.760> index<01:02:27.599> as<01:02:27.720> well<01:02:27.880> as<01:02:28.039> their<01:02:28.240> BLS 01:02:30.549 --> 01:02:30.559 align:start position:0% unique index as well as their BLS 01:02:30.559 --> 01:02:38.069 align:start position:0% unique index as well as their BLS key<01:02:31.960> so<01:02:32.960> what<01:02:33.520> E7<01:02:34.240> 4788<01:02:35.079> proposes<01:02:35.880> is<01:02:36.119> that<01:02:37.079> we 01:02:38.069 --> 01:02:38.079 align:start position:0% key so what E7 4788 proposes is that we 01:02:38.079 --> 01:02:39.630 align:start position:0% key so what E7 4788 proposes is that we get<01:02:38.319> this<01:02:38.480> eventual<01:02:38.839> Merkel<01:02:39.240> route<01:02:39.480> like<01:02:39.599> if 01:02:39.630 --> 01:02:39.640 align:start position:0% get this eventual Merkel route like if 01:02:39.640 --> 01:02:41.950 align:start position:0% get this eventual Merkel route like if we<01:02:39.760> meriz<01:02:40.359> this<01:02:40.559> entire<01:02:40.960> Beacon<01:02:41.359> State<01:02:41.720> and 01:02:41.950 --> 01:02:41.960 align:start position:0% we meriz this entire Beacon State and 01:02:41.960 --> 01:02:43.510 align:start position:0% we meriz this entire Beacon State and then<01:02:42.119> eventually<01:02:42.440> the<01:02:42.559> beacon<01:02:42.880> block<01:02:43.359> we 01:02:43.510 --> 01:02:43.520 align:start position:0% then eventually the beacon block we 01:02:43.520 --> 01:02:46.510 align:start position:0% then eventually the beacon block we eventually<01:02:43.920> get<01:02:44.240> a<01:02:44.400> 132<01:02:45.000> by<01:02:45.240> long<01:02:45.480> Merkel 01:02:46.510 --> 01:02:46.520 align:start position:0% eventually get a 132 by long Merkel 01:02:46.520 --> 01:02:48.990 align:start position:0% eventually get a 132 by long Merkel route<01:02:47.520> and<01:02:47.640> we<01:02:47.799> make<01:02:48.039> this<01:02:48.279> available<01:02:48.760> within 01:02:48.990 --> 01:02:49.000 align:start position:0% route and we make this available within 01:02:49.000 --> 01:02:50.990 align:start position:0% route and we make this available within the<01:02:49.160> execution 01:02:50.990 --> 01:02:51.000 align:start position:0% the execution 01:02:51.000 --> 01:02:53.589 align:start position:0% the execution layer<01:02:52.000> so<01:02:52.279> the<01:02:52.400> thing<01:02:52.599> here<01:02:52.760> is<01:02:53.000> that<01:02:53.440> there's 01:02:53.589 --> 01:02:53.599 align:start position:0% layer so the thing here is that there's 01:02:53.599 --> 01:02:55.829 align:start position:0% layer so the thing here is that there's a<01:02:53.839> problem<01:02:54.359> and<01:02:54.559> that's<01:02:55.000> we<01:02:55.160> only<01:02:55.400> have<01:02:55.559> access 01:02:55.829 --> 01:02:55.839 align:start position:0% a problem and that's we only have access 01:02:55.839 --> 01:02:58.190 align:start position:0% a problem and that's we only have access access<01:02:56.119> to<01:02:56.839> historical<01:02:57.400> Roots<01:02:57.720> we<01:02:57.799> don't<01:02:58.000> have 01:02:58.190 --> 01:02:58.200 align:start position:0% access to historical Roots we don't have 01:02:58.200 --> 01:03:00.710 align:start position:0% access to historical Roots we don't have access<01:02:58.440> to<01:02:58.599> the<01:02:58.720> current<01:02:59.160> slots<01:03:00.160> proposer 01:03:00.710 --> 01:03:00.720 align:start position:0% access to the current slots proposer 01:03:00.720 --> 01:03:03.349 align:start position:0% access to the current slots proposer because<01:03:01.200> well<01:03:02.200> the<01:03:02.319> consensus<01:03:02.799> layer<01:03:03.079> is<01:03:03.240> yet 01:03:03.349 --> 01:03:03.359 align:start position:0% because well the consensus layer is yet 01:03:03.359 --> 01:03:05.150 align:start position:0% because well the consensus layer is yet to<01:03:03.480> create<01:03:03.799> the<01:03:03.920> block<01:03:04.160> so<01:03:04.319> we<01:03:04.440> can't<01:03:04.680> have<01:03:04.880> the 01:03:05.150 --> 01:03:05.160 align:start position:0% to create the block so we can't have the 01:03:05.160 --> 01:03:07.190 align:start position:0% to create the block so we can't have the we<01:03:05.279> can't<01:03:05.480> really<01:03:05.640> know<01:03:05.799> who<01:03:05.960> the<01:03:06.079> proposer 01:03:07.190 --> 01:03:07.200 align:start position:0% we can't really know who the proposer 01:03:07.200 --> 01:03:09.910 align:start position:0% we can't really know who the proposer is<01:03:08.200> so<01:03:08.359> we<01:03:08.480> have<01:03:08.599> to<01:03:08.720> slash<01:03:09.240> or<01:03:09.440> prove<01:03:09.680> that<01:03:09.799> a 01:03:09.910 --> 01:03:09.920 align:start position:0% is so we have to slash or prove that a 01:03:09.920 --> 01:03:12.230 align:start position:0% is so we have to slash or prove that a look<01:03:10.079> ahead<01:03:10.319> is<01:03:10.440> incorrect<01:03:11.240> optimistically 01:03:12.230 --> 01:03:12.240 align:start position:0% look ahead is incorrect optimistically 01:03:12.240 --> 01:03:14.670 align:start position:0% look ahead is incorrect optimistically and<01:03:12.400> the<01:03:12.520> way<01:03:12.680> we<01:03:12.799> do<01:03:13.000> it<01:03:13.279> is<01:03:13.520> we<01:03:13.720> wait<01:03:14.319> until 01:03:14.670 --> 01:03:14.680 align:start position:0% and the way we do it is we wait until 01:03:14.680 --> 01:03:17.190 align:start position:0% and the way we do it is we wait until the<01:03:14.880> incorrect<01:03:15.359> slot<01:03:15.680> has<01:03:15.880> passed<01:03:16.880> and<01:03:17.039> we 01:03:17.190 --> 01:03:17.200 align:start position:0% the incorrect slot has passed and we 01:03:17.200 --> 01:03:19.630 align:start position:0% the incorrect slot has passed and we have<01:03:17.400> the<01:03:17.520> route<01:03:18.200> and<01:03:18.359> once<01:03:18.559> we<01:03:18.720> have<01:03:18.880> the 01:03:19.630 --> 01:03:19.640 align:start position:0% have the route and once we have the 01:03:19.640 --> 01:03:21.870 align:start position:0% have the route and once we have the route<01:03:20.640> we<01:03:20.799> can<01:03:20.960> basically<01:03:21.279> make<01:03:21.400> a<01:03:21.559> static 01:03:21.870 --> 01:03:21.880 align:start position:0% route we can basically make a static 01:03:21.880 --> 01:03:23.029 align:start position:0% route we can basically make a static call<01:03:22.039> to<01:03:22.200> this<01:03:22.359> contract<01:03:22.760> which<01:03:22.839> is<01:03:22.960> the 01:03:23.029 --> 01:03:23.039 align:start position:0% call to this contract which is the 01:03:23.039 --> 01:03:26.029 align:start position:0% call to this contract which is the beacon<01:03:23.319> Roots<01:03:23.960> contract<01:03:24.960> and<01:03:25.279> get<01:03:25.880> that 01:03:26.029 --> 01:03:26.039 align:start position:0% beacon Roots contract and get that 01:03:26.039 --> 01:03:29.190 align:start position:0% beacon Roots contract and get that Beacon<01:03:26.400> route<01:03:27.400> and<01:03:27.559> then<01:03:27.960> just<01:03:28.200> need<01:03:28.400> to<01:03:28.559> send 01:03:29.190 --> 01:03:29.200 align:start position:0% Beacon route and then just need to send 01:03:29.200 --> 01:03:30.349 align:start position:0% Beacon route and then just need to send two 01:03:30.349 --> 01:03:30.359 align:start position:0% two 01:03:30.359 --> 01:03:33.870 align:start position:0% two proves<01:03:31.359> so<01:03:31.599> first<01:03:32.520> the<01:03:32.720> proposer<01:03:33.319> or<01:03:33.480> sorry 01:03:33.870 --> 01:03:33.880 align:start position:0% proves so first the proposer or sorry 01:03:33.880 --> 01:03:36.950 align:start position:0% proves so first the proposer or sorry the<01:03:34.079> Challenger<01:03:35.079> posts<01:03:35.520> the<01:03:35.640> BLS<01:03:36.119> key<01:03:36.640> of 01:03:36.950 --> 01:03:36.960 align:start position:0% the Challenger posts the BLS key of 01:03:36.960 --> 01:03:38.630 align:start position:0% the Challenger posts the BLS key of whoever<01:03:37.400> was<01:03:37.559> supposed<01:03:37.880> to<01:03:37.960> be<01:03:38.119> the<01:03:38.200> validator 01:03:38.630 --> 01:03:38.640 align:start position:0% whoever was supposed to be the validator 01:03:38.640 --> 01:03:41.910 align:start position:0% whoever was supposed to be the validator of<01:03:38.760> that<01:03:38.920> slot<01:03:39.720> as<01:03:39.880> well<01:03:40.079> as<01:03:40.520> their<01:03:40.760> validator 01:03:41.910 --> 01:03:41.920 align:start position:0% of that slot as well as their validator 01:03:41.920 --> 01:03:44.710 align:start position:0% of that slot as well as their validator index<01:03:42.920> and<01:03:43.079> along<01:03:43.359> with<01:03:43.599> this<01:03:43.880> it<01:03:44.000> sends<01:03:44.400> two 01:03:44.710 --> 01:03:44.720 align:start position:0% index and along with this it sends two 01:03:44.720 --> 01:03:48.029 align:start position:0% index and along with this it sends two proofs<01:03:45.720> first<01:03:45.960> is<01:03:46.119> the<01:03:46.319> proof<01:03:47.000> that<01:03:47.680> in<01:03:47.880> this 01:03:48.029 --> 01:03:48.039 align:start position:0% proofs first is the proof that in this 01:03:48.039 --> 01:03:50.630 align:start position:0% proofs first is the proof that in this case<01:03:48.240> if<01:03:48.319> you<01:03:48.440> see<01:03:49.279> we<01:03:49.400> have<01:03:49.520> a<01:03:49.760> proposer<01:03:50.200> index 01:03:50.630 --> 01:03:50.640 align:start position:0% case if you see we have a proposer index 01:03:50.640 --> 01:03:52.710 align:start position:0% case if you see we have a proposer index in<01:03:50.760> the<01:03:50.880> beacon<01:03:51.200> block<01:03:51.960> but<01:03:52.119> in<01:03:52.240> the<01:03:52.359> beacon 01:03:52.710 --> 01:03:52.720 align:start position:0% in the beacon block but in the beacon 01:03:52.720 --> 01:03:54.950 align:start position:0% in the beacon block but in the beacon State<01:03:53.440> well<01:03:53.720> we<01:03:54.079> basically<01:03:54.440> end<01:03:54.599> up<01:03:54.760> having 01:03:54.950 --> 01:03:54.960 align:start position:0% State well we basically end up having 01:03:54.960 --> 01:03:57.789 align:start position:0% State well we basically end up having BLS<01:03:55.359> keys<01:03:55.760> of<01:03:55.880> the<01:03:55.960> validators<01:03:56.839> at<01:03:57.240> respective 01:03:57.789 --> 01:03:57.799 align:start position:0% BLS keys of the validators at respective 01:03:57.799 --> 01:04:00.789 align:start position:0% BLS keys of the validators at respective indices<01:03:58.799> so<01:03:59.000> whilea<01:03:59.279> aoral<01:03:59.799> proof<01:04:00.319> we<01:04:00.480> have<01:04:00.640> to 01:04:00.789 --> 01:04:00.799 align:start position:0% indices so whilea aoral proof we have to 01:04:00.799 --> 01:04:02.630 align:start position:0% indices so whilea aoral proof we have to make<01:04:01.000> this<01:04:01.160> connection<01:04:01.680> that<01:04:01.920> hey<01:04:02.160> this 01:04:02.630 --> 01:04:02.640 align:start position:0% make this connection that hey this 01:04:02.640 --> 01:04:05.670 align:start position:0% make this connection that hey this proposer<01:04:03.119> index<01:04:03.920> actually<01:04:04.279> belongs<01:04:04.799> to<01:04:05.079> this 01:04:05.670 --> 01:04:05.680 align:start position:0% proposer index actually belongs to this 01:04:05.680 --> 01:04:08.750 align:start position:0% proposer index actually belongs to this particular<01:04:06.640> BLS<01:04:07.160> key<01:04:07.520> or<01:04:07.680> BLS<01:04:08.039> public<01:04:08.319> key<01:04:08.599> and 01:04:08.750 --> 01:04:08.760 align:start position:0% particular BLS key or BLS public key and 01:04:08.760 --> 01:04:09.910 align:start position:0% particular BLS key or BLS public key and that's<01:04:08.920> the<01:04:09.119> step 01:04:09.910 --> 01:04:09.920 align:start position:0% that's the step 01:04:09.920 --> 01:04:12.549 align:start position:0% that's the step two<01:04:10.920> and<01:04:11.119> then<01:04:11.359> in<01:04:11.480> the<01:04:11.599> next<01:04:11.960> step<01:04:12.400> the 01:04:12.549 --> 01:04:12.559 align:start position:0% two and then in the next step the 01:04:12.559 --> 01:04:14.029 align:start position:0% two and then in the next step the validator<01:04:13.119> or<01:04:13.400> once<01:04:13.640> again<01:04:13.839> not<01:04:13.960> the 01:04:14.029 --> 01:04:14.039 align:start position:0% validator or once again not the 01:04:14.039 --> 01:04:16.349 align:start position:0% validator or once again not the validator<01:04:14.480> the<01:04:14.559> Challenger<01:04:15.240> needs<01:04:15.520> to<01:04:15.720> prove 01:04:16.349 --> 01:04:16.359 align:start position:0% validator the Challenger needs to prove 01:04:16.359 --> 01:04:18.510 align:start position:0% validator the Challenger needs to prove that<01:04:16.640> this<01:04:16.960> is<01:04:17.119> the<01:04:17.279> proposal<01:04:17.720> index<01:04:18.160> that<01:04:18.279> is 01:04:18.510 --> 01:04:18.520 align:start position:0% that this is the proposal index that is 01:04:18.520 --> 01:04:20.549 align:start position:0% that this is the proposal index that is present<01:04:19.039> in<01:04:19.319> the<01:04:19.440> beacon<01:04:19.839> block<01:04:20.200> as<01:04:20.319> you<01:04:20.400> can 01:04:20.549 --> 01:04:20.559 align:start position:0% present in the beacon block as you can 01:04:20.559 --> 01:04:24.230 align:start position:0% present in the beacon block as you can see<01:04:20.799> here<01:04:21.160> the<01:04:21.359> second<01:04:21.920> field<01:04:22.920> so<01:04:23.599> very<01:04:23.839> simply 01:04:24.230 --> 01:04:24.240 align:start position:0% see here the second field so very simply 01:04:24.240 --> 01:04:26.349 align:start position:0% see here the second field so very simply with<01:04:24.400> two<01:04:24.599> simple<01:04:24.880> Merkel<01:04:25.279> proofs<01:04:26.079> you're 01:04:26.349 --> 01:04:26.359 align:start position:0% with two simple Merkel proofs you're 01:04:26.359 --> 01:04:29.150 align:start position:0% with two simple Merkel proofs you're able<01:04:26.559> to<01:04:26.760> get<01:04:27.000> whoever<01:04:27.440> was<01:04:27.839> the<01:04:27.960> BLS<01:04:28.680> the<01:04:28.839> BLS 01:04:29.150 --> 01:04:29.160 align:start position:0% able to get whoever was the BLS the BLS 01:04:29.160 --> 01:04:30.630 align:start position:0% able to get whoever was the BLS the BLS key<01:04:29.319> of<01:04:29.440> whoever<01:04:29.680> was<01:04:29.839> the<01:04:29.960> validator<01:04:30.440> in<01:04:30.520> the 01:04:30.630 --> 01:04:30.640 align:start position:0% key of whoever was the validator in the 01:04:30.640 --> 01:04:32.789 align:start position:0% key of whoever was the validator in the current<01:04:31.000> slot<01:04:31.520> or<01:04:31.680> the<01:04:31.880> pre<01:04:32.119> the<01:04:32.200> slot<01:04:32.559> that<01:04:32.680> is 01:04:32.789 --> 01:04:32.799 align:start position:0% current slot or the pre the slot that is 01:04:32.799 --> 01:04:34.710 align:start position:0% current slot or the pre the slot that is being 01:04:34.710 --> 01:04:34.720 align:start position:0% being 01:04:34.720 --> 01:04:36.910 align:start position:0% being challenged<01:04:35.720> and<01:04:35.920> well<01:04:36.119> once<01:04:36.279> you<01:04:36.480> get<01:04:36.680> that 01:04:36.910 --> 01:04:36.920 align:start position:0% challenged and well once you get that 01:04:36.920 --> 01:04:38.829 align:start position:0% challenged and well once you get that you<01:04:37.039> can<01:04:37.240> just<01:04:37.400> go<01:04:37.559> ahead<01:04:37.839> and 01:04:38.829 --> 01:04:38.839 align:start position:0% you can just go ahead and 01:04:38.839 --> 01:04:41.150 align:start position:0% you can just go ahead and make<01:04:39.839> check<01:04:40.119> if<01:04:40.279> this<01:04:40.440> inequality<01:04:41.039> is 01:04:41.150 --> 01:04:41.160 align:start position:0% make check if this inequality is 01:04:41.160 --> 01:04:43.109 align:start position:0% make check if this inequality is actually<01:04:41.400> satisfied<01:04:42.000> if<01:04:42.079> it<01:04:42.240> is<01:04:42.720> then<01:04:42.920> well 01:04:43.109 --> 01:04:43.119 align:start position:0% actually satisfied if it is then well 01:04:43.119 --> 01:04:45.029 align:start position:0% actually satisfied if it is then well the<01:04:43.240> look<01:04:43.440> ahead<01:04:43.720> slot<01:04:44.079> is<01:04:44.279> incorrect<01:04:44.839> and<01:04:44.960> you 01:04:45.029 --> 01:04:45.039 align:start position:0% the look ahead slot is incorrect and you 01:04:45.039 --> 01:04:49.829 align:start position:0% the look ahead slot is incorrect and you can<01:04:45.160> slash<01:04:45.520> whoever<01:04:45.880> posted 01:04:49.829 --> 01:04:49.839 align:start position:0% 01:04:49.839 --> 01:04:52.470 align:start position:0% it<01:04:50.839> along<01:04:51.119> with<01:04:51.319> that<01:04:51.520> we<01:04:51.640> have<01:04:51.799> slashing<01:04:52.279> of 01:04:52.470 --> 01:04:52.480 align:start position:0% it along with that we have slashing of 01:04:52.480 --> 01:04:54.510 align:start position:0% it along with that we have slashing of bad<01:04:52.760> prec<01:04:52.960> confirmations<01:04:53.839> which<01:04:54.079> I<01:04:54.200> think<01:04:54.359> was 01:04:54.510 --> 01:04:54.520 align:start position:0% bad prec confirmations which I think was 01:04:54.520 --> 01:04:56.870 align:start position:0% bad prec confirmations which I think was touched<01:04:54.799> upon<01:04:55.000> by<01:04:55.160> ahmmed<01:04:55.960> but<01:04:56.119> in<01:04:56.279> this<01:04:56.440> case 01:04:56.870 --> 01:04:56.880 align:start position:0% touched upon by ahmmed but in this case 01:04:56.880 --> 01:04:58.630 align:start position:0% touched upon by ahmmed but in this case if<01:04:57.000> we<01:04:57.119> want<01:04:57.319> to<01:04:57.520> expand<01:04:57.920> it<01:04:58.160> we<01:04:58.319> have 01:04:58.630 --> 01:04:58.640 align:start position:0% if we want to expand it we have 01:04:58.640 --> 01:05:00.750 align:start position:0% if we want to expand it we have execution<01:04:59.160> pre-<01:04:59.440> comps<01:04:59.960> that<01:05:00.079> could<01:05:00.279> be<01:05:00.480> bad 01:05:00.750 --> 01:05:00.760 align:start position:0% execution pre- comps that could be bad 01:05:00.760 --> 01:05:02.190 align:start position:0% execution pre- comps that could be bad and<01:05:00.920> we<01:05:01.039> could<01:05:01.160> also<01:05:01.359> have<01:05:01.559> bad<01:05:01.760> inclusion 01:05:02.190 --> 01:05:02.200 align:start position:0% and we could also have bad inclusion 01:05:02.200 --> 01:05:04.630 align:start position:0% and we could also have bad inclusion pre-<01:05:02.480> comps<01:05:03.359> in<01:05:03.480> the<01:05:03.680> case<01:05:03.839> of<01:05:04.000> execution 01:05:04.630 --> 01:05:04.640 align:start position:0% pre- comps in the case of execution 01:05:04.640 --> 01:05:08.390 align:start position:0% pre- comps in the case of execution proms<01:05:05.799> well<01:05:06.799> the<01:05:06.960> proposer<01:05:07.480> did<01:05:07.720> push<01:05:08.240> the 01:05:08.390 --> 01:05:08.400 align:start position:0% proms well the proposer did push the 01:05:08.400 --> 01:05:14.230 align:start position:0% proms well the proposer did push the eventual<01:05:08.799> block<01:05:09.440> that<01:05:09.680> he<01:05:09.880> pre-confirmation 01:05:14.230 --> 01:05:14.240 align:start position:0% 01:05:14.240 --> 01:05:15.990 align:start position:0% that<01:05:15.240> was<01:05:15.400> not<01:05:15.720> actually 01:05:15.990 --> 01:05:16.000 align:start position:0% that was not actually 01:05:16.000 --> 01:05:25.829 align:start position:0% that was not actually preconiran-food.com 01:05:25.829 --> 01:05:25.839 align:start position:0% 01:05:25.839 --> 01:05:27.789 align:start position:0% that<01:05:26.000> was<01:05:26.119> on<01:05:26.240> the 01:05:27.789 --> 01:05:27.799 align:start position:0% that was on the 01:05:27.799 --> 01:05:30.150 align:start position:0% that was on the P2P<01:05:28.799> and<01:05:28.960> in<01:05:29.039> the<01:05:29.160> case<01:05:29.319> of<01:05:29.440> inclusion<01:05:29.880> pre 01:05:30.150 --> 01:05:30.160 align:start position:0% P2P and in the case of inclusion pre 01:05:30.160 --> 01:05:32.750 align:start position:0% P2P and in the case of inclusion pre comps<01:05:30.599> that's<01:05:30.839> a<01:05:30.960> bit<01:05:31.119> more<01:05:31.359> simpler<01:05:32.359> we<01:05:32.559> end 01:05:32.750 --> 01:05:32.760 align:start position:0% comps that's a bit more simpler we end 01:05:32.760 --> 01:05:35.029 align:start position:0% comps that's a bit more simpler we end up<01:05:32.960> getting<01:05:33.200> different<01:05:33.520> proposers<01:05:34.200> for<01:05:34.920> the 01:05:35.029 --> 01:05:35.039 align:start position:0% up getting different proposers for the 01:05:35.039 --> 01:05:37.029 align:start position:0% up getting different proposers for the same<01:05:35.279> block<01:05:35.559> ID<01:05:36.240> because<01:05:36.520> it<01:05:36.680> might<01:05:36.880> have 01:05:37.029 --> 01:05:37.039 align:start position:0% same block ID because it might have 01:05:37.039 --> 01:05:55.950 align:start position:0% same block ID because it might have happened<01:05:37.359> that<01:05:37.640> well<01:05:38.119> he<01:05:38.240> pre-confirmation 01:05:55.950 --> 01:05:55.960 align:start position:0% 01:05:55.960 --> 01:06:01.710 align:start position:0% no<01:05:56.960> on<01:05:57.079> the<01:05:57.599> inclusion<01:05:58.599> can<01:05:59.119> happen<01:05:59.480> that<01:06:00.319> I<01:06:00.520> do 01:06:01.710 --> 01:06:01.720 align:start position:0% no on the inclusion can happen that I do 01:06:01.720 --> 01:06:04.910 align:start position:0% no on the inclusion can happen that I do for<01:06:02.720> I<01:06:02.799> don't<01:06:03.559> might<01:06:03.680> turn<01:06:04.119> five<01:06:04.599> away<01:06:04.799> but 01:06:04.910 --> 01:06:04.920 align:start position:0% for I don't might turn five away but 01:06:04.920 --> 01:06:06.829 align:start position:0% for I don't might turn five away but someone<01:06:05.279> incl 01:06:06.829 --> 01:06:06.839 align:start position:0% someone incl 01:06:06.839 --> 01:06:09.750 align:start position:0% someone incl before<01:06:07.839> and<01:06:08.000> then<01:06:08.160> the<01:06:08.279> pre<01:06:09.119> proposer<01:06:09.640> would 01:06:09.750 --> 01:06:09.760 align:start position:0% before and then the pre proposer would 01:06:09.760 --> 01:06:13.349 align:start position:0% before and then the pre proposer would have<01:06:10.599> really<01:06:11.119> is<01:06:11.240> that<01:06:11.559> true<01:06:12.559> yeah<01:06:12.720> so<01:06:13.000> in<01:06:13.160> this 01:06:13.349 --> 01:06:13.359 align:start position:0% have really is that true yeah so in this 01:06:13.359 --> 01:06:16.309 align:start position:0% have really is that true yeah so in this case<01:06:13.720> we<01:06:13.960> actually<01:06:14.960> have<01:06:15.640> uh<01:06:15.960> discovered<01:06:16.200> a 01:06:16.309 --> 01:06:16.319 align:start position:0% case we actually have uh discovered a 01:06:16.319 --> 01:06:18.710 align:start position:0% case we actually have uh discovered a few<01:06:16.559> issues<01:06:17.359> so<01:06:17.760> another<01:06:18.079> variant<01:06:18.400> a<01:06:18.520> more 01:06:18.710 --> 01:06:18.720 align:start position:0% few issues so another variant a more 01:06:18.720 --> 01:06:21.269 align:start position:0% few issues so another variant a more simple<01:06:19.039> variant<01:06:19.359> of<01:06:19.440> your<01:06:19.680> issue<01:06:19.920> would<01:06:20.079> be<01:06:20.559> I 01:06:21.269 --> 01:06:21.279 align:start position:0% simple variant of your issue would be I 01:06:21.279 --> 01:06:24.910 align:start position:0% simple variant of your issue would be I precom<01:06:22.279> and<01:06:22.960> I<01:06:23.079> don't<01:06:23.319> include<01:06:23.680> it<01:06:24.480> but<01:06:24.680> then 01:06:24.910 --> 01:06:24.920 align:start position:0% precom and I don't include it but then 01:06:24.920 --> 01:06:26.589 align:start position:0% precom and I don't include it but then for<01:06:25.119> a<01:06:25.240> long<01:06:25.599> period<01:06:25.960> no<01:06:26.079> one<01:06:26.319> actually 01:06:26.589 --> 01:06:26.599 align:start position:0% for a long period no one actually 01:06:26.599 --> 01:06:30.029 align:start position:0% for a long period no one actually includes<01:06:27.039> any<01:06:27.240> block<01:06:28.119> so<01:06:28.520> what<01:06:28.720> happens<01:06:29.039> is<01:06:29.279> we 01:06:30.029 --> 01:06:30.039 align:start position:0% includes any block so what happens is we 01:06:30.039 --> 01:06:31.549 align:start position:0% includes any block so what happens is we a<01:06:30.160> long<01:06:30.400> time<01:06:30.599> passes<01:06:30.960> and<01:06:31.079> the<01:06:31.200> dispute 01:06:31.549 --> 01:06:31.559 align:start position:0% a long time passes and the dispute 01:06:31.559 --> 01:06:35.349 align:start position:0% a long time passes and the dispute period<01:06:31.880> gets<01:06:32.240> over<01:06:33.240> so<01:06:33.760> even<01:06:34.200> though<01:06:35.200> that 01:06:35.349 --> 01:06:35.359 align:start position:0% period gets over so even though that 01:06:35.359 --> 01:06:37.349 align:start position:0% period gets over so even though that there<01:06:35.480> is<01:06:35.880> no<01:06:36.079> pre-confirmation<01:06:36.559> there<01:06:37.160> is<01:06:37.240> a 01:06:37.349 --> 01:06:37.359 align:start position:0% there is no pre-confirmation there is a 01:06:37.359 --> 01:06:38.630 align:start position:0% there is no pre-confirmation there is a pre-confirmation<01:06:37.799> but<01:06:38.200> there<01:06:38.319> is<01:06:38.440> no 01:06:38.630 --> 01:06:38.640 align:start position:0% pre-confirmation but there is no 01:06:38.640 --> 01:06:40.990 align:start position:0% pre-confirmation but there is no Associated<01:06:39.200> block<01:06:39.720> like<01:06:39.880> the<01:06:39.960> block<01:06:40.240> ID<01:06:40.599> has 01:06:40.990 --> 01:06:41.000 align:start position:0% Associated block like the block ID has 01:06:41.000 --> 01:06:43.470 align:start position:0% Associated block like the block ID has never<01:06:41.279> really<01:06:41.640> progressed<01:06:42.160> on<01:06:42.400> chain<01:06:43.160> and<01:06:43.319> and 01:06:43.470 --> 01:06:43.480 align:start position:0% never really progressed on chain and and 01:06:43.480 --> 01:06:46.789 align:start position:0% never really progressed on chain and and that's<01:06:43.640> an<01:06:43.839> issue<01:06:44.359> but<01:06:44.520> you<01:06:44.680> can't<01:06:45.000> really<01:06:46.000> uh 01:06:46.789 --> 01:06:46.799 align:start position:0% that's an issue but you can't really uh 01:06:46.799 --> 01:06:49.349 align:start position:0% that's an issue but you can't really uh prove<01:06:47.359> the<01:06:47.480> incorrectness<01:06:48.079> of<01:06:48.279> this<01:06:49.039> so<01:06:49.200> we 01:06:49.349 --> 01:06:49.359 align:start position:0% prove the incorrectness of this so we 01:06:49.359 --> 01:06:52.670 align:start position:0% prove the incorrectness of this so we have<01:06:49.559> a<01:06:49.680> way<01:06:49.839> of<01:06:49.960> doing<01:06:50.279> that<01:06:51.119> and<01:06:51.799> uh<01:06:52.000> that<01:06:52.160> is 01:06:52.670 --> 01:06:52.680 align:start position:0% have a way of doing that and uh that is 01:06:52.680 --> 01:06:54.990 align:start position:0% have a way of doing that and uh that is so<01:06:52.880> we<01:06:53.039> might<01:06:53.240> have<01:06:53.359> to<01:06:53.559> go<01:06:53.799> back<01:06:54.039> to<01:06:54.440> so<01:06:54.799> let's 01:06:54.990 --> 01:06:55.000 align:start position:0% so we might have to go back to so let's 01:06:55.000 --> 01:06:56.309 align:start position:0% so we might have to go back to so let's say<01:06:55.200> this<01:06:55.319> is 01:06:56.309 --> 01:06:56.319 align:start position:0% say this is 01:06:56.319 --> 01:07:00.589 align:start position:0% say this is like<01:06:56.680> the<01:06:56.799> slots<01:06:57.640> okay<01:06:58.400> so<01:06:58.960> whenever<01:06:59.960> uh<01:07:00.440> a 01:07:00.589 --> 01:07:00.599 align:start position:0% like the slots okay so whenever uh a 01:07:00.599 --> 01:07:03.190 align:start position:0% like the slots okay so whenever uh a pre-confirmation<01:07:01.079> is<01:07:01.440> being<01:07:01.680> made<01:07:02.680> we<01:07:02.920> also 01:07:03.190 --> 01:07:03.200 align:start position:0% pre-confirmation is being made we also 01:07:03.200 --> 01:07:05.470 align:start position:0% pre-confirmation is being made we also include<01:07:03.880> a<01:07:04.039> look<01:07:04.240> ahead<01:07:04.559> pointer<01:07:05.119> which 01:07:05.470 --> 01:07:05.480 align:start position:0% include a look ahead pointer which 01:07:05.480 --> 01:07:09.150 align:start position:0% include a look ahead pointer which basically<01:07:05.960> points<01:07:06.839> to<01:07:07.839> Which<01:07:08.279> slot<01:07:08.880> in<01:07:09.000> the 01:07:09.150 --> 01:07:09.160 align:start position:0% basically points to Which slot in the 01:07:09.160 --> 01:07:12.349 align:start position:0% basically points to Which slot in the look<01:07:09.400> ahead<01:07:10.039> am<01:07:10.200> I<01:07:10.359> prec<01:07:10.640> coming<01:07:11.000> for<01:07:12.000> so<01:07:12.160> in 01:07:12.349 --> 01:07:12.359 align:start position:0% look ahead am I prec coming for so in 01:07:12.359 --> 01:07:13.630 align:start position:0% look ahead am I prec coming for so in this<01:07:12.520> way<01:07:12.680> what<01:07:12.799> we<01:07:12.920> have<01:07:13.039> to<01:07:13.160> do<01:07:13.319> is<01:07:13.440> we<01:07:13.559> have 01:07:13.630 --> 01:07:13.640 align:start position:0% this way what we have to do is we have 01:07:13.640 --> 01:07:16.549 align:start position:0% this way what we have to do is we have to<01:07:13.760> make<01:07:13.880> a<01:07:14.000> connection<01:07:14.680> between<01:07:15.680> the<01:07:16.400> uh 01:07:16.549 --> 01:07:16.559 align:start position:0% to make a connection between the uh 01:07:16.559 --> 01:07:18.789 align:start position:0% to make a connection between the uh pre-confirmation<01:07:17.079> and<01:07:18.000> the<01:07:18.160> proposed<01:07:18.520> block 01:07:18.789 --> 01:07:18.799 align:start position:0% pre-confirmation and the proposed block 01:07:18.799 --> 01:07:21.549 align:start position:0% pre-confirmation and the proposed block why<01:07:18.920> are<01:07:19.039> the<01:07:19.160> look<01:07:19.520> ahead<01:07:20.520> I<01:07:20.640> think<01:07:21.200> now<01:07:21.440> that 01:07:21.549 --> 01:07:21.559 align:start position:0% why are the look ahead I think now that 01:07:21.559 --> 01:07:23.910 align:start position:0% why are the look ahead I think now that answers<01:07:21.880> your<01:07:22.079> question<01:07:22.480> because<01:07:23.000> if<01:07:23.160> we<01:07:23.480> have 01:07:23.910 --> 01:07:23.920 align:start position:0% answers your question because if we have 01:07:23.920 --> 01:07:26.470 align:start position:0% answers your question because if we have that<01:07:24.079> look<01:07:24.279> Ahad<01:07:24.559> pointer<01:07:25.640> that<01:07:26.079> basically 01:07:26.470 --> 01:07:26.480 align:start position:0% that look Ahad pointer that basically 01:07:26.480 --> 01:07:28.109 align:start position:0% that look Ahad pointer that basically states<01:07:26.920> which<01:07:27.079> look<01:07:27.279> ahead<01:07:27.559> slot<01:07:27.880> have<01:07:28.000> we 01:07:28.109 --> 01:07:28.119 align:start position:0% states which look ahead slot have we 01:07:28.119 --> 01:07:30.349 align:start position:0% states which look ahead slot have we made<01:07:28.319> the<01:07:28.440> pre-confirmation<01:07:28.960> for<01:07:29.960> and<01:07:30.079> if<01:07:30.200> it 01:07:30.349 --> 01:07:30.359 align:start position:0% made the pre-confirmation for and if it 01:07:30.359 --> 01:07:34.109 align:start position:0% made the pre-confirmation for and if it lands<01:07:30.839> on<01:07:31.599> at<01:07:31.720> a<01:07:31.880> different<01:07:32.240> time<01:07:33.000> on<01:07:33.799> uh<01:07:33.920> on 01:07:34.109 --> 01:07:34.119 align:start position:0% lands on at a different time on uh on 01:07:34.119 --> 01:07:34.829 align:start position:0% lands on at a different time on uh on the 01:07:34.829 --> 01:07:34.839 align:start position:0% the 01:07:34.839 --> 01:07:37.470 align:start position:0% the L1<01:07:35.839> we<01:07:35.960> can<01:07:36.160> make<01:07:36.599> the 01:07:37.470 --> 01:07:37.480 align:start position:0% L1 we can make the 01:07:37.480 --> 01:07:39.829 align:start position:0% L1 we can make the inequality<01:07:38.480> okay<01:07:38.760> but<01:07:39.000> but<01:07:39.119> is<01:07:39.240> it<01:07:39.440> possible 01:07:39.829 --> 01:07:39.839 align:start position:0% inequality okay but but is it possible 01:07:39.839 --> 01:07:55.589 align:start position:0% inequality okay but but is it possible that<01:07:40.000> I<01:07:40.440> pre-confirmation 01:07:55.589 --> 01:07:55.599 align:start position:0% 01:07:55.599 --> 01:07:57.269 align:start position:0% prec<01:07:55.799> confirmations<01:07:56.720> I<01:07:56.839> I<01:07:56.880> don't<01:07:57.039> know<01:07:57.160> if 01:07:57.269 --> 01:07:57.279 align:start position:0% prec confirmations I I don't know if 01:07:57.279 --> 01:08:00.109 align:start position:0% prec confirmations I I don't know if that<01:07:57.400> makes<01:07:57.960> sense<01:07:58.960> I<01:07:59.039> mean<01:07:59.520> not<01:07:59.760> really 01:08:00.109 --> 01:08:00.119 align:start position:0% that makes sense I mean not really 01:08:00.119 --> 01:08:01.990 align:start position:0% that makes sense I mean not really because<01:08:00.839> you<01:08:01.000> are<01:08:01.200> prec<01:08:01.680> because<01:08:01.880> the 01:08:01.990 --> 01:08:02.000 align:start position:0% because you are prec because the 01:08:02.000 --> 01:08:03.710 align:start position:0% because you are prec because the proposer<01:08:02.400> is<01:08:02.559> once<01:08:02.799> again<01:08:03.079> the<01:08:03.319> I<01:08:03.400> mean<01:08:03.599> this 01:08:03.710 --> 01:08:03.720 align:start position:0% proposer is once again the I mean this 01:08:03.720 --> 01:08:06.390 align:start position:0% proposer is once again the I mean this is<01:08:03.960> Advanced<01:08:04.680> proposals<01:08:05.680> I<01:08:05.760> mean<01:08:06.000> you<01:08:06.200> just 01:08:06.390 --> 01:08:06.400 align:start position:0% is Advanced proposals I mean you just 01:08:06.400 --> 01:08:07.910 align:start position:0% is Advanced proposals I mean you just put<01:08:06.520> it<01:08:06.720> in<01:08:06.920> you<01:08:07.079> just<01:08:07.279> release<01:08:07.599> it<01:08:07.720> in<01:08:07.799> the 01:08:07.910 --> 01:08:07.920 align:start position:0% put it in you just release it in the 01:08:07.920 --> 01:08:10.230 align:start position:0% put it in you just release it in the public<01:08:08.160> me<01:08:08.440> pool<01:08:09.119> and<01:08:09.440> it<01:08:09.599> might<01:08:09.839> happen<01:08:10.079> that 01:08:10.230 --> 01:08:10.240 align:start position:0% public me pool and it might happen that 01:08:10.240 --> 01:08:13.150 align:start position:0% public me pool and it might happen that the<01:08:10.319> proposer<01:08:10.760> does<01:08:10.960> not<01:08:11.559> included<01:08:12.440> but<01:08:12.640> then 01:08:13.150 --> 01:08:13.160 align:start position:0% the proposer does not included but then 01:08:13.160 --> 01:08:16.630 align:start position:0% the proposer does not included but then your<01:08:13.400> slot<01:08:13.760> will<01:08:13.880> be<01:08:14.039> coming<01:08:14.319> in<01:08:15.200> so<01:08:15.480> if<01:08:15.640> you<01:08:16.400> go 01:08:16.630 --> 01:08:16.640 align:start position:0% your slot will be coming in so if you go 01:08:16.640 --> 01:08:19.309 align:start position:0% your slot will be coming in so if you go back<01:08:16.759> to<01:08:17.000> this<01:08:17.239> slide<01:08:17.679> that 01:08:19.309 --> 01:08:19.319 align:start position:0% back to this slide that 01:08:19.319 --> 01:08:22.309 align:start position:0% back to this slide that Ahmed<01:08:20.319> uh<01:08:20.520> presented<01:08:21.279> in<01:08:21.480> this<01:08:21.679> case<01:08:22.120> when 01:08:22.309 --> 01:08:22.319 align:start position:0% Ahmed uh presented in this case when 01:08:22.319 --> 01:08:25.630 align:start position:0% Ahmed uh presented in this case when your<01:08:22.520> slot<01:08:22.839> comes<01:08:23.440> in<01:08:24.440> you<01:08:24.679> clear<01:08:25.080> all<01:08:25.279> those 01:08:25.630 --> 01:08:25.640 align:start position:0% your slot comes in you clear all those 01:08:25.640 --> 01:08:26.950 align:start position:0% your slot comes in you clear all those pending<01:08:25.960> transactions<01:08:26.440> that<01:08:26.600> have<01:08:26.759> never 01:08:26.950 --> 01:08:26.960 align:start position:0% pending transactions that have never 01:08:26.960 --> 01:08:28.189 align:start position:0% pending transactions that have never been<01:08:27.120> included<01:08:27.520> because<01:08:27.719> the<01:08:27.839> proposer 01:08:28.189 --> 01:08:28.199 align:start position:0% been included because the proposer 01:08:28.199 --> 01:08:30.030 align:start position:0% been included because the proposer didn't<01:08:28.400> want<01:08:28.520> to<01:08:28.640> include<01:08:29.199> but<01:08:29.359> your<01:08:29.560> slot<01:08:29.880> has 01:08:30.030 --> 01:08:30.040 align:start position:0% didn't want to include but your slot has 01:08:30.040 --> 01:08:32.030 align:start position:0% didn't want to include but your slot has now<01:08:30.239> arrived<01:08:31.080> so<01:08:31.279> you<01:08:31.480> pick<01:08:31.719> those 01:08:32.030 --> 01:08:32.040 align:start position:0% now arrived so you pick those 01:08:32.040 --> 01:08:34.189 align:start position:0% now arrived so you pick those transactions<01:08:33.040> and<01:08:33.159> you<01:08:33.319> force<01:08:33.679> includeed 01:08:34.189 --> 01:08:34.199 align:start position:0% transactions and you force includeed 01:08:34.199 --> 01:08:36.590 align:start position:0% transactions and you force includeed whilea<01:08:34.400> the<01:08:34.480> inclusion<01:08:34.920> list<01:08:35.600> through<01:08:35.880> the<01:08:36.239> uh 01:08:36.590 --> 01:08:36.600 align:start position:0% whilea the inclusion list through the uh 01:08:36.600 --> 01:08:39.470 align:start position:0% whilea the inclusion list through the uh PBS<01:08:37.080> pipeline<01:08:37.719> yeah<01:08:38.040> the<01:08:38.600> the<01:08:38.880> other<01:08:39.199> answer 01:08:39.470 --> 01:08:39.480 align:start position:0% PBS pipeline yeah the the other answer 01:08:39.480 --> 01:08:41.709 align:start position:0% PBS pipeline yeah the the other answer to<01:08:39.679> this<01:08:39.880> question<01:08:40.199> is<01:08:40.480> that<01:08:41.000> the<01:08:41.199> previous 01:08:41.709 --> 01:08:41.719 align:start position:0% to this question is that the previous 01:08:41.719 --> 01:08:42.590 align:start position:0% to this question is that the previous pre- 01:08:42.590 --> 01:08:42.600 align:start position:0% pre- 01:08:42.600 --> 01:08:46.510 align:start position:0% pre- Comer<01:08:43.600> um<01:08:44.400> cannot<01:08:45.400> uh<01:08:45.600> like<01:08:46.040> that<01:08:46.400> the 01:08:46.510 --> 01:08:46.520 align:start position:0% Comer um cannot uh like that the 01:08:46.520 --> 01:08:48.510 align:start position:0% Comer um cannot uh like that the previous<01:08:46.839> slot<01:08:47.239> and<01:08:47.600> if<01:08:47.799> if<01:08:47.880> you're<01:08:48.120> talking 01:08:48.510 --> 01:08:48.520 align:start position:0% previous slot and if if you're talking 01:08:48.520 --> 01:08:51.870 align:start position:0% previous slot and if if you're talking about<01:08:49.239> if<01:08:49.480> if<01:08:49.679> this<01:08:49.839> slot<01:08:50.679> is<01:08:50.960> for<01:08:51.239> prec<01:08:51.520> confer 01:08:51.870 --> 01:08:51.880 align:start position:0% about if if this slot is for prec confer 01:08:51.880 --> 01:08:55.669 align:start position:0% about if if this slot is for prec confer 2<01:08:52.319> to<01:08:52.520> precom<01:08:53.040> at<01:08:53.799> the<01:08:54.000> the<01:08:54.159> precom<01:08:54.679> one<01:08:55.080> cannot 01:08:55.669 --> 01:08:55.679 align:start position:0% 2 to precom at the the precom one cannot 01:08:55.679 --> 01:08:58.510 align:start position:0% 2 to precom at the the precom one cannot then<01:08:56.040> go<01:08:56.239> and<01:08:56.440> push<01:08:56.759> transactions<01:08:57.520> there 01:08:58.510 --> 01:08:58.520 align:start position:0% then go and push transactions there 01:08:58.520 --> 01:09:00.950 align:start position:0% then go and push transactions there every<01:08:58.839> slot<01:08:59.679> has<01:08:59.839> an<01:09:00.080> assigned<01:09:00.440> pre-c<01:09:00.640> Comer 01:09:00.950 --> 01:09:00.960 align:start position:0% every slot has an assigned pre-c Comer 01:09:00.960 --> 01:09:03.470 align:start position:0% every slot has an assigned pre-c Comer and<01:09:01.159> only<01:09:01.400> a<01:09:01.600> specific<01:09:01.960> pre-c<01:09:02.199> Comer<01:09:02.560> can<01:09:03.279> uh 01:09:03.470 --> 01:09:03.480 align:start position:0% and only a specific pre-c Comer can uh 01:09:03.480 --> 01:09:06.550 align:start position:0% and only a specific pre-c Comer can uh push<01:09:04.080> transactions<01:09:04.880> or<01:09:05.120> batches<01:09:05.920> in<01:09:06.159> those 01:09:06.550 --> 01:09:06.560 align:start position:0% push transactions or batches in those 01:09:06.560 --> 01:09:09.669 align:start position:0% push transactions or batches in those slots<01:09:07.560> so<01:09:08.000> the<01:09:08.199> contract<01:09:08.640> will<01:09:08.920> just<01:09:09.120> ignore 01:09:09.669 --> 01:09:09.679 align:start position:0% slots so the contract will just ignore 01:09:09.679 --> 01:09:12.110 align:start position:0% slots so the contract will just ignore any<01:09:10.000> batches<01:09:10.920> that<01:09:11.120> arrive<01:09:11.679> from<01:09:11.880> pre- 01:09:12.110 --> 01:09:12.120 align:start position:0% any batches that arrive from pre- 01:09:12.120 --> 01:09:13.829 align:start position:0% any batches that arrive from pre- Comforts<01:09:12.560> that<01:09:12.640> are<01:09:12.799> not<01:09:13.080> assigned<01:09:13.440> to<01:09:13.600> these 01:09:13.829 --> 01:09:13.839 align:start position:0% Comforts that are not assigned to these 01:09:13.839 --> 01:09:16.990 align:start position:0% Comforts that are not assigned to these specific<01:09:14.199> slots<01:09:15.120> okay 01:09:16.990 --> 01:09:17.000 align:start position:0% specific slots okay 01:09:17.000 --> 01:09:21.110 align:start position:0% specific slots okay perfect<01:09:18.000> any<01:09:18.199> more 01:09:21.110 --> 01:09:21.120 align:start position:0% 01:09:21.120 --> 01:09:25.669 align:start position:0% questions<01:09:22.120> no 01:09:25.669 --> 01:09:25.679 align:start position:0% 01:09:25.679 --> 01:09:26.910 align:start position:0% I<01:09:25.799> think<01:09:25.920> we<01:09:26.040> can<01:09:26.159> touch<01:09:26.359> upon<01:09:26.520> the<01:09:26.640> future 01:09:26.910 --> 01:09:26.920 align:start position:0% I think we can touch upon the future 01:09:26.920 --> 01:09:29.950 align:start position:0% I think we can touch upon the future work<01:09:27.199> now 01:09:29.950 --> 01:09:29.960 align:start position:0% 01:09:29.960 --> 01:09:34.950 align:start position:0% yeah<01:09:30.960> um<01:09:31.679> all<01:09:31.880> right<01:09:32.560> so<01:09:33.199> first<01:09:33.839> we<01:09:34.040> start<01:09:34.560> with 01:09:34.950 --> 01:09:34.960 align:start position:0% yeah um all right so first we start with 01:09:34.960 --> 01:09:38.189 align:start position:0% yeah um all right so first we start with soft<01:09:35.319> blocks<01:09:35.799> So<01:09:36.520> currently<01:09:37.520> what<01:09:37.640> we<01:09:37.799> do<01:09:38.040> when 01:09:38.189 --> 01:09:38.199 align:start position:0% soft blocks So currently what we do when 01:09:38.199 --> 01:09:40.709 align:start position:0% soft blocks So currently what we do when we<01:09:38.359> advance<01:09:38.799> the<01:09:38.960> head<01:09:39.359> is<01:09:39.560> that<01:09:40.000> we<01:09:40.199> push<01:09:40.440> a 01:09:40.709 --> 01:09:40.719 align:start position:0% we advance the head is that we push a 01:09:40.719 --> 01:09:45.749 align:start position:0% we advance the head is that we push a whole<01:09:41.000> full<01:09:41.359> block<01:09:42.120> to<01:09:42.880> Tao<01:09:43.880> and<01:09:44.040> in<01:09:44.239> this<01:09:44.759> way 01:09:45.749 --> 01:09:45.759 align:start position:0% whole full block to Tao and in this way 01:09:45.759 --> 01:09:48.110 align:start position:0% whole full block to Tao and in this way what<01:09:45.920> ends<01:09:46.159> up<01:09:46.400> happening<01:09:46.880> is<01:09:47.120> that<01:09:47.719> it<01:09:47.880> goes 01:09:48.110 --> 01:09:48.120 align:start position:0% what ends up happening is that it goes 01:09:48.120 --> 01:09:49.870 align:start position:0% what ends up happening is that it goes and<01:09:48.279> lands<01:09:48.600> in<01:09:48.719> the<01:09:48.839> canonical<01:09:49.359> chain<01:09:49.759> and 01:09:49.870 --> 01:09:49.880 align:start position:0% and lands in the canonical chain and 01:09:49.880 --> 01:09:52.189 align:start position:0% and lands in the canonical chain and this<01:09:50.000> is<01:09:50.159> normal<01:09:51.120> and<01:09:51.279> this<01:09:51.400> is<01:09:51.679> why<01:09:51.960> those 01:09:52.189 --> 01:09:52.199 align:start position:0% this is normal and this is why those 01:09:52.199 --> 01:09:53.990 align:start position:0% this is normal and this is why those transactions<01:09:52.799> are<01:09:53.159> then<01:09:53.319> removed<01:09:53.719> from<01:09:53.880> the 01:09:53.990 --> 01:09:54.000 align:start position:0% transactions are then removed from the 01:09:54.000 --> 01:09:56.470 align:start position:0% transactions are then removed from the mol<01:09:54.560> so<01:09:54.719> when<01:09:54.840> you<01:09:54.960> propose<01:09:55.520> the<01:09:55.640> next<01:09:55.840> block 01:09:56.470 --> 01:09:56.480 align:start position:0% mol so when you propose the next block 01:09:56.480 --> 01:09:58.950 align:start position:0% mol so when you propose the next block they<01:09:56.600> don't<01:09:56.800> get<01:09:56.960> included<01:09:57.520> twice<01:09:58.520> so<01:09:58.719> that's 01:09:58.950 --> 01:09:58.960 align:start position:0% they don't get included twice so that's 01:09:58.960 --> 01:10:02.189 align:start position:0% they don't get included twice so that's one<01:09:59.520> thing<01:10:00.520> um<01:10:01.199> the<01:10:01.440> problem<01:10:01.760> with<01:10:01.960> this 01:10:02.189 --> 01:10:02.199 align:start position:0% one thing um the problem with this 01:10:02.199 --> 01:10:03.310 align:start position:0% one thing um the problem with this approach 01:10:03.310 --> 01:10:03.320 align:start position:0% approach 01:10:03.320 --> 01:10:06.830 align:start position:0% approach is<01:10:04.320> um<01:10:04.880> is<01:10:05.120> that<01:10:05.480> when<01:10:05.719> you<01:10:05.880> we<01:10:06.040> are<01:10:06.280> proposing 01:10:06.830 --> 01:10:06.840 align:start position:0% is um is that when you we are proposing 01:10:06.840 --> 01:10:10.229 align:start position:0% is um is that when you we are proposing these<01:10:07.040> blocks<01:10:07.679> at<01:10:07.800> the<01:10:07.920> end<01:10:08.120> on<01:10:08.480> L1<01:10:09.480> we<01:10:09.640> need<01:10:09.920> to 01:10:10.229 --> 01:10:10.239 align:start position:0% these blocks at the end on L1 we need to 01:10:10.239 --> 01:10:12.709 align:start position:0% these blocks at the end on L1 we need to propose<01:10:10.640> multiple<01:10:11.080> blocks<01:10:11.760> so<01:10:12.000> for<01:10:12.199> example 01:10:12.709 --> 01:10:12.719 align:start position:0% propose multiple blocks so for example 01:10:12.719 --> 01:10:25.310 align:start position:0% propose multiple blocks so for example if<01:10:12.920> I<01:10:13.120> pre-confirmation 01:10:25.310 --> 01:10:25.320 align:start position:0% 01:10:25.320 --> 01:10:27.790 align:start position:0% this<01:10:25.400> is<01:10:25.600> costy<01:10:26.159> proposal<01:10:26.800> and<01:10:27.040> verification 01:10:27.790 --> 01:10:27.800 align:start position:0% this is costy proposal and verification 01:10:27.800 --> 01:10:30.350 align:start position:0% this is costy proposal and verification of<01:10:28.000> these<01:10:28.199> blocks<01:10:28.520> is<01:10:28.719> costy<01:10:29.679> for<01:10:29.880> a<01:10:30.040> block 01:10:30.350 --> 01:10:30.360 align:start position:0% of these blocks is costy for a block 01:10:30.360 --> 01:10:34.510 align:start position:0% of these blocks is costy for a block proposal<01:10:30.880> it<01:10:31.080> cost<01:10:31.400> around<01:10:31.920> 200<01:10:32.480> um<01:10:32.920> 200<01:10:33.600> um 01:10:34.510 --> 01:10:34.520 align:start position:0% proposal it cost around 200 um 200 um 01:10:34.520 --> 01:10:38.350 align:start position:0% proposal it cost around 200 um 200 um 200,000<01:10:35.520> gas<01:10:36.000> Anu<01:10:36.640> right<01:10:36.920> yeah<01:10:37.199> give<01:10:37.360> or<01:10:37.560> take 01:10:38.350 --> 01:10:38.360 align:start position:0% 200,000 gas Anu right yeah give or take 01:10:38.360 --> 01:10:40.270 align:start position:0% 200,000 gas Anu right yeah give or take and<01:10:38.760> um<01:10:39.120> around 01:10:40.270 --> 01:10:40.280 align:start position:0% and um around 01:10:40.280 --> 01:10:42.990 align:start position:0% and um around 400<01:10:41.280> for<01:10:41.480> verifying<01:10:42.000> the<01:10:42.120> ZK<01:10:42.520> proof<01:10:42.760> for<01:10:42.880> a 01:10:42.990 --> 01:10:43.000 align:start position:0% 400 for verifying the ZK proof for a 01:10:43.000 --> 01:10:45.830 align:start position:0% 400 for verifying the ZK proof for a single<01:10:43.320> block<01:10:44.239> give<01:10:44.360> or<01:10:44.560> take<01:10:44.800> as<01:10:44.960> well<01:10:45.679> uh 01:10:45.830 --> 01:10:45.840 align:start position:0% single block give or take as well uh 01:10:45.840 --> 01:10:48.510 align:start position:0% single block give or take as well uh could<01:10:46.000> be<01:10:46.480> a<01:10:46.560> bit<01:10:46.800> more<01:10:47.159> than<01:10:47.360> 400<01:10:47.880> more<01:10:48.159> closer 01:10:48.510 --> 01:10:48.520 align:start position:0% could be a bit more than 400 more closer 01:10:48.520 --> 01:10:52.630 align:start position:0% could be a bit more than 400 more closer to<01:10:48.880> 500<01:10:49.880> so<01:10:50.800> every<01:10:51.080> block<01:10:51.719> that<01:10:51.880> we<01:10:52.000> end<01:10:52.199> up 01:10:52.630 --> 01:10:52.640 align:start position:0% to 500 so every block that we end up 01:10:52.640 --> 01:10:56.470 align:start position:0% to 500 so every block that we end up proposing<01:10:53.640> is<01:10:54.080> is<01:10:54.320> is<01:10:54.520> adding<01:10:55.320> a<01:10:55.400> lot<01:10:55.520> of<01:10:55.719> cost 01:10:56.470 --> 01:10:56.480 align:start position:0% proposing is is is adding a lot of cost 01:10:56.480 --> 01:10:58.790 align:start position:0% proposing is is is adding a lot of cost for<01:10:56.840> proposal<01:10:57.280> and<01:10:57.480> verification<01:10:58.480> so<01:10:58.679> what 01:10:58.790 --> 01:10:58.800 align:start position:0% for proposal and verification so what 01:10:58.800 --> 01:11:02.390 align:start position:0% for proposal and verification so what did<01:10:59.480> we<01:10:59.760> end<01:11:00.040> up<01:11:00.320> with<01:11:00.679> is<01:11:00.920> a<01:11:01.040> solution<01:11:01.600> where 01:11:02.390 --> 01:11:02.400 align:start position:0% did we end up with is a solution where 01:11:02.400 --> 01:11:03.590 align:start position:0% did we end up with is a solution where when<01:11:02.560> you 01:11:03.590 --> 01:11:03.600 align:start position:0% when you 01:11:03.600 --> 01:11:07.790 align:start position:0% when you precom<01:11:04.600> um<01:11:04.840> you're<01:11:05.080> going<01:11:05.199> to<01:11:05.800> add<01:11:06.800> the<01:11:07.120> batch 01:11:07.790 --> 01:11:07.800 align:start position:0% precom um you're going to add the batch 01:11:07.800 --> 01:11:10.310 align:start position:0% precom um you're going to add the batch to<01:11:08.040> taoes<01:11:08.920> push<01:11:09.080> it<01:11:09.360> and<01:11:09.480> then<01:11:09.640> when<01:11:09.760> you<01:11:10.040> push 01:11:10.310 --> 01:11:10.320 align:start position:0% to taoes push it and then when you push 01:11:10.320 --> 01:11:12.750 align:start position:0% to taoes push it and then when you push another<01:11:10.719> batch<01:11:11.640> what<01:11:11.840> it<01:11:11.960> ends<01:11:12.199> up<01:11:12.400> happening 01:11:12.750 --> 01:11:12.760 align:start position:0% another batch what it ends up happening 01:11:12.760 --> 01:11:15.149 align:start position:0% another batch what it ends up happening is<01:11:12.920> that<01:11:13.120> it<01:11:13.280> gets<01:11:13.679> added<01:11:14.360> to<01:11:14.560> the<01:11:14.719> block 01:11:15.149 --> 01:11:15.159 align:start position:0% is that it gets added to the block 01:11:15.159 --> 01:11:18.790 align:start position:0% is that it gets added to the block instead<01:11:15.600> of<01:11:16.239> being<01:11:16.800> so<01:11:17.000> it<01:11:17.199> gets<01:11:17.640> appended<01:11:18.640> in 01:11:18.790 --> 01:11:18.800 align:start position:0% instead of being so it gets appended in 01:11:18.800 --> 01:11:21.189 align:start position:0% instead of being so it gets appended in the<01:11:18.920> block<01:11:19.640> so<01:11:19.840> what<01:11:20.000> happens<01:11:20.360> is<01:11:20.560> that<01:11:20.840> a<01:11:20.960> new 01:11:21.189 --> 01:11:21.199 align:start position:0% the block so what happens is that a new 01:11:21.199 --> 01:11:23.669 align:start position:0% the block so what happens is that a new block<01:11:21.480> is<01:11:21.640> formed<01:11:22.480> with<01:11:22.640> the<01:11:22.840> previous 01:11:23.669 --> 01:11:23.679 align:start position:0% block is formed with the previous 01:11:23.679 --> 01:11:26.030 align:start position:0% block is formed with the previous transactions<01:11:24.400> that<01:11:24.520> are<01:11:24.640> in<01:11:24.800> the<01:11:24.920> block 01:11:26.030 --> 01:11:26.040 align:start position:0% transactions that are in the block 01:11:26.040 --> 01:11:31.070 align:start position:0% transactions that are in the block and<01:11:27.040> um<01:11:27.840> the<01:11:28.400> new<01:11:28.719> transaction<01:11:29.440> batch<01:11:30.440> and<01:11:30.920> the 01:11:31.070 --> 01:11:31.080 align:start position:0% and um the new transaction batch and the 01:11:31.080 --> 01:11:33.590 align:start position:0% and um the new transaction batch and the previous<01:11:31.440> block<01:11:31.679> gets<01:11:31.880> reorg<01:11:32.760> out<01:11:33.199> and<01:11:33.440> then 01:11:33.590 --> 01:11:33.600 align:start position:0% previous block gets reorg out and then 01:11:33.600 --> 01:11:35.189 align:start position:0% previous block gets reorg out and then we<01:11:33.719> include<01:11:34.120> the<01:11:34.239> new 01:11:35.189 --> 01:11:35.199 align:start position:0% we include the new 01:11:35.199 --> 01:11:39.430 align:start position:0% we include the new block<01:11:36.199> and<01:11:36.360> this<01:11:36.560> keeps<01:11:36.920> happening<01:11:38.000> until<01:11:39.000> the 01:11:39.430 --> 01:11:39.440 align:start position:0% block and this keeps happening until the 01:11:39.440 --> 01:11:42.229 align:start position:0% block and this keeps happening until the precom<01:11:39.960> node<01:11:40.360> sends<01:11:41.360> end<01:11:41.639> of<01:11:41.880> end<01:11:42.080> of 01:11:42.229 --> 01:11:42.239 align:start position:0% precom node sends end of end of 01:11:42.239 --> 01:11:43.510 align:start position:0% precom node sends end of end of pre-confirmation 01:11:43.510 --> 01:11:43.520 align:start position:0% pre-confirmation 01:11:43.520 --> 01:11:46.830 align:start position:0% pre-confirmation or<01:11:44.520> uh<01:11:44.800> and<01:11:45.040> then<01:11:45.639> this<01:11:45.960> block<01:11:46.320> becomes<01:11:46.639> a 01:11:46.830 --> 01:11:46.840 align:start position:0% or uh and then this block becomes a 01:11:46.840 --> 01:11:49.510 align:start position:0% or uh and then this block becomes a standard<01:11:47.280> block<01:11:47.960> and<01:11:48.159> gets<01:11:48.360> pushed<01:11:48.639> to<01:11:48.760> L1<01:11:49.400> as 01:11:49.510 --> 01:11:49.520 align:start position:0% standard block and gets pushed to L1 as 01:11:49.520 --> 01:11:53.870 align:start position:0% standard block and gets pushed to L1 as a<01:11:50.280> whole<01:11:50.639> single<01:11:51.719> proposal<01:11:52.719> and<01:11:52.920> this<01:11:53.679> gives 01:11:53.870 --> 01:11:53.880 align:start position:0% a whole single proposal and this gives 01:11:53.880 --> 01:11:55.390 align:start position:0% a whole single proposal and this gives us<01:11:54.080> the<01:11:54.199> cost<01:11:54.480> saving<01:11:54.760> that<01:11:54.880> we're<01:11:55.000> looking 01:11:55.390 --> 01:11:55.400 align:start position:0% us the cost saving that we're looking 01:11:55.400 --> 01:11:57.709 align:start position:0% us the cost saving that we're looking for<01:11:55.719> but<01:11:56.320> it's<01:11:56.480> still<01:11:56.679> not<01:11:56.920> finalized 01:11:57.709 --> 01:11:57.719 align:start position:0% for but it's still not finalized 01:11:57.719 --> 01:11:59.430 align:start position:0% for but it's still not finalized something<01:11:58.120> that<01:11:58.239> we're<01:11:58.440> going<01:11:58.520> to<01:11:59.040> hopefully 01:11:59.430 --> 01:11:59.440 align:start position:0% something that we're going to hopefully 01:11:59.440 --> 01:12:01.430 align:start position:0% something that we're going to hopefully work<01:11:59.639> on<01:11:59.920> the<01:12:00.080> next<01:12:00.280> couple<01:12:00.480> of 01:12:01.430 --> 01:12:01.440 align:start position:0% work on the next couple of 01:12:01.440 --> 01:12:05.470 align:start position:0% work on the next couple of months<01:12:02.440> another<01:12:02.800> thing<01:12:03.280> like<01:12:03.960> uh<01:12:04.760> our<01:12:05.040> friend 01:12:05.470 --> 01:12:05.480 align:start position:0% months another thing like uh our friend 01:12:05.480 --> 01:12:09.229 align:start position:0% months another thing like uh our friend here<01:12:05.840> asked<01:12:06.159> about<01:12:06.480> before<01:12:07.159> is<01:12:07.480> the<01:12:07.679> slot<01:12:08.239> time 01:12:09.229 --> 01:12:09.239 align:start position:0% here asked about before is the slot time 01:12:09.239 --> 01:12:13.189 align:start position:0% here asked about before is the slot time uh<01:12:09.320> for<01:12:09.600> the<01:12:09.719> L2<01:12:10.600> So<01:12:10.880> currently<01:12:11.679> we<01:12:12.040> have<01:12:12.960> a 01:12:13.189 --> 01:12:13.199 align:start position:0% uh for the L2 So currently we have a 01:12:13.199 --> 01:12:16.070 align:start position:0% uh for the L2 So currently we have a constant<01:12:13.679> three<01:12:14.040> block<01:12:14.360> second<01:12:14.719> block<01:12:15.080> time 01:12:16.070 --> 01:12:16.080 align:start position:0% constant three block second block time 01:12:16.080 --> 01:12:18.149 align:start position:0% constant three block second block time and<01:12:16.639> what<01:12:16.760> we're<01:12:17.000> looking<01:12:17.280> for<01:12:17.920> to 01:12:18.149 --> 01:12:18.159 align:start position:0% and what we're looking for to 01:12:18.159 --> 01:12:21.110 align:start position:0% and what we're looking for to accomplishing<01:12:18.920> is<01:12:19.520> one<01:12:19.760> second<01:12:20.040> walk<01:12:20.280> time 01:12:21.110 --> 01:12:21.120 align:start position:0% accomplishing is one second walk time 01:12:21.120 --> 01:12:23.070 align:start position:0% accomplishing is one second walk time and<01:12:21.400> it's<01:12:21.600> not<01:12:21.840> that<01:12:22.080> this<01:12:22.159> is<01:12:22.360> not<01:12:22.679> possible 01:12:23.070 --> 01:12:23.080 align:start position:0% and it's not that this is not possible 01:12:23.080 --> 01:12:26.149 align:start position:0% and it's not that this is not possible currently<01:12:23.560> it<01:12:23.760> just<01:12:23.960> hasn't<01:12:24.239> been<01:12:25.199> tried<01:12:25.600> yet 01:12:26.149 --> 01:12:26.159 align:start position:0% currently it just hasn't been tried yet 01:12:26.159 --> 01:12:27.830 align:start position:0% currently it just hasn't been tried yet and<01:12:26.320> we're<01:12:26.520> not<01:12:26.679> sure<01:12:27.040> what<01:12:27.239> limitations 01:12:27.830 --> 01:12:27.840 align:start position:0% and we're not sure what limitations 01:12:27.840 --> 01:12:31.590 align:start position:0% and we're not sure what limitations we're<01:12:28.000> going<01:12:28.120> to<01:12:28.360> hit<01:12:28.679> with<01:12:28.800> the<01:12:28.920> P2P 01:12:31.590 --> 01:12:31.600 align:start position:0% we're going to hit with the P2P 01:12:31.600 --> 01:12:35.070 align:start position:0% we're going to hit with the P2P Etc<01:12:32.600> yeah<01:12:33.000> and<01:12:33.719> then<01:12:33.960> in<01:12:34.199> the<01:12:34.400> last<01:12:34.639> one<01:12:34.920> I 01:12:35.070 --> 01:12:35.080 align:start position:0% Etc yeah and then in the last one I 01:12:35.080 --> 01:12:37.629 align:start position:0% Etc yeah and then in the last one I think<01:12:35.679> you<01:12:35.800> will<01:12:36.040> talk<01:12:36.280> about<01:12:36.480> it 01:12:37.629 --> 01:12:37.639 align:start position:0% think you will talk about it 01:12:37.639 --> 01:12:39.950 align:start position:0% think you will talk about it yeah<01:12:38.639> so<01:12:38.800> when<01:12:38.920> I<01:12:39.040> was<01:12:39.199> talking<01:12:39.520> about<01:12:39.760> the 01:12:39.950 --> 01:12:39.960 align:start position:0% yeah so when I was talking about the 01:12:39.960 --> 01:12:41.950 align:start position:0% yeah so when I was talking about the pre-confirmation<01:12:40.480> service<01:12:41.480> manager 01:12:41.950 --> 01:12:41.960 align:start position:0% pre-confirmation service manager 01:12:41.960 --> 01:12:43.870 align:start position:0% pre-confirmation service manager contract<01:12:42.679> I<01:12:42.760> said<01:12:43.000> we<01:12:43.080> are<01:12:43.239> trying<01:12:43.440> to<01:12:43.600> make<01:12:43.719> it 01:12:43.870 --> 01:12:43.880 align:start position:0% contract I said we are trying to make it 01:12:43.880 --> 01:12:46.709 align:start position:0% contract I said we are trying to make it like<01:12:44.040> a<01:12:44.120> middleware<01:12:45.120> so<01:12:45.400> that<01:12:45.920> as<01:12:46.120> and<01:12:46.360> when<01:12:46.560> we 01:12:46.709 --> 01:12:46.719 align:start position:0% like a middleware so that as and when we 01:12:46.719 --> 01:12:48.950 align:start position:0% like a middleware so that as and when we want<01:12:46.880> to<01:12:47.280> change<01:12:47.600> the<01:12:47.760> reaking<01:12:48.400> service<01:12:48.760> or 01:12:48.950 --> 01:12:48.960 align:start position:0% want to change the reaking service or 01:12:48.960 --> 01:12:51.709 align:start position:0% want to change the reaking service or the<01:12:49.159> staking<01:12:49.440> service<01:12:50.040> we<01:12:50.960> can<01:12:51.120> just<01:12:51.280> swap<01:12:51.600> it 01:12:51.709 --> 01:12:51.719 align:start position:0% the staking service we can just swap it 01:12:51.719 --> 01:12:56.030 align:start position:0% the staking service we can just swap it out<01:12:52.120> and<01:12:52.600> use<01:12:52.840> a<01:12:53.000> new<01:12:53.320> one<01:12:54.320> and 01:12:56.030 --> 01:12:56.040 align:start position:0% out and use a new one and 01:12:56.040 --> 01:12:57.950 align:start position:0% out and use a new one and in<01:12:56.199> regards<01:12:56.560> to<01:12:56.760> that<01:12:57.199> the<01:12:57.400> community<01:12:57.800> is 01:12:57.950 --> 01:12:57.960 align:start position:0% in regards to that the community is 01:12:57.960 --> 01:12:59.470 align:start position:0% in regards to that the community is planning<01:12:58.280> to<01:12:58.480> launch<01:12:58.800> a<01:12:59.000> universal 01:12:59.470 --> 01:12:59.480 align:start position:0% planning to launch a universal 01:12:59.480 --> 01:13:02.149 align:start position:0% planning to launch a universal pre-confirmation<01:13:00.280> registry<01:13:01.280> so<01:13:01.480> chances<01:13:01.880> are 01:13:02.149 --> 01:13:02.159 align:start position:0% pre-confirmation registry so chances are 01:13:02.159 --> 01:13:03.790 align:start position:0% pre-confirmation registry so chances are there<01:13:02.280> will<01:13:02.400> be<01:13:02.600> many<01:13:02.800> more<01:13:03.040> based<01:13:03.360> rollups 01:13:03.790 --> 01:13:03.800 align:start position:0% there will be many more based rollups 01:13:03.800 --> 01:13:06.629 align:start position:0% there will be many more based rollups down<01:13:03.960> the<01:13:04.120> line<01:13:04.440> not<01:13:04.639> just<01:13:05.159> Tao<01:13:06.159> and<01:13:06.360> when<01:13:06.480> you 01:13:06.629 --> 01:13:06.639 align:start position:0% down the line not just Tao and when you 01:13:06.639 --> 01:13:08.830 align:start position:0% down the line not just Tao and when you have<01:13:06.880> so<01:13:07.040> many<01:13:07.239> based<01:13:07.520> rollups<01:13:08.400> it<01:13:08.520> could<01:13:08.679> be 01:13:08.830 --> 01:13:08.840 align:start position:0% have so many based rollups it could be 01:13:08.840 --> 01:13:11.229 align:start position:0% have so many based rollups it could be the<01:13:09.000> case<01:13:09.280> that<01:13:09.920> one<01:13:10.159> proposer<01:13:10.639> wants<01:13:10.880> to 01:13:11.229 --> 01:13:11.239 align:start position:0% the case that one proposer wants to 01:13:11.239 --> 01:13:13.590 align:start position:0% the case that one proposer wants to propose<01:13:11.760> or<01:13:12.040> pre-comp<01:13:12.520> for<01:13:12.719> multiple<01:13:13.159> based 01:13:13.590 --> 01:13:13.600 align:start position:0% propose or pre-comp for multiple based 01:13:13.600 --> 01:13:16.229 align:start position:0% propose or pre-comp for multiple based rollups<01:13:14.600> but<01:13:15.040> it<01:13:15.199> doesn't<01:13:15.520> really<01:13:15.800> want<01:13:16.000> to 01:13:16.229 --> 01:13:16.239 align:start position:0% rollups but it doesn't really want to 01:13:16.239 --> 01:13:17.990 align:start position:0% rollups but it doesn't really want to register<01:13:16.719> continuously<01:13:17.400> because<01:13:17.679> that<01:13:17.800> will 01:13:17.990 --> 01:13:18.000 align:start position:0% register continuously because that will 01:13:18.000 --> 01:13:20.990 align:start position:0% register continuously because that will cost<01:13:18.239> him<01:13:18.400> a<01:13:18.480> lot<01:13:18.639> of<01:13:18.800> gas<01:13:19.520> and<01:13:19.800> also<01:13:20.560> it<01:13:20.679> won't 01:13:20.990 --> 01:13:21.000 align:start position:0% cost him a lot of gas and also it won't 01:13:21.000 --> 01:13:23.830 align:start position:0% cost him a lot of gas and also it won't be<01:13:21.239> that<01:13:21.400> credibly<01:13:21.840> neutral<01:13:22.639> because<01:13:23.639> might 01:13:23.830 --> 01:13:23.840 align:start position:0% be that credibly neutral because might 01:13:23.840 --> 01:13:25.510 align:start position:0% be that credibly neutral because might be<01:13:24.000> the<01:13:24.120> case<01:13:24.320> that<01:13:24.440> every<01:13:24.600> rollup<01:13:25.120> starts<01:13:25.360> up 01:13:25.510 --> 01:13:25.520 align:start position:0% be the case that every rollup starts up 01:13:25.520 --> 01:13:27.629 align:start position:0% be the case that every rollup starts up its<01:13:25.679> own<01:13:25.920> staking<01:13:26.360> service<01:13:27.120> and<01:13:27.320> and<01:13:27.480> that's 01:13:27.629 --> 01:13:27.639 align:start position:0% its own staking service and and that's 01:13:27.639 --> 01:13:29.629 align:start position:0% its own staking service and and that's not<01:13:27.800> reasonable<01:13:28.400> for<01:13:28.679> the<01:13:29.000> proposer<01:13:29.480> and 01:13:29.629 --> 01:13:29.639 align:start position:0% not reasonable for the proposer and 01:13:29.639 --> 01:13:32.229 align:start position:0% not reasonable for the proposer and that's<01:13:29.760> a<01:13:29.960> waste<01:13:30.239> of<01:13:30.440> eth<01:13:30.800> not<01:13:30.960> a<01:13:31.080> good<01:13:31.239> use<01:13:31.440> of 01:13:32.229 --> 01:13:32.239 align:start position:0% that's a waste of eth not a good use of 01:13:32.239 --> 01:13:34.229 align:start position:0% that's a waste of eth not a good use of collateral<01:13:33.239> so<01:13:33.360> in<01:13:33.520> this<01:13:33.679> case<01:13:33.880> there<01:13:33.960> will<01:13:34.120> be 01:13:34.229 --> 01:13:34.239 align:start position:0% collateral so in this case there will be 01:13:34.239 --> 01:13:36.470 align:start position:0% collateral so in this case there will be a<01:13:34.320> universal<01:13:34.760> pre-confirmation<01:13:35.480> registry 01:13:36.470 --> 01:13:36.480 align:start position:0% a universal pre-confirmation registry 01:13:36.480 --> 01:13:39.270 align:start position:0% a universal pre-confirmation registry where<01:13:37.280> any<01:13:37.520> proposer<01:13:37.920> who<01:13:38.080> wants<01:13:38.320> to<01:13:38.840> become<01:13:39.120> a 01:13:39.270 --> 01:13:39.280 align:start position:0% where any proposer who wants to become a 01:13:39.280 --> 01:13:42.270 align:start position:0% where any proposer who wants to become a pre-<01:13:39.480> confer<01:13:40.239> can<01:13:40.440> go<01:13:40.600> in<01:13:40.800> register<01:13:41.679> the<01:13:41.840> BLS 01:13:42.270 --> 01:13:42.280 align:start position:0% pre- confer can go in register the BLS 01:13:42.280 --> 01:13:46.229 align:start position:0% pre- confer can go in register the BLS mapping<01:13:42.880> instead<01:13:43.239> of<01:13:43.400> being<01:13:43.719> in<01:13:44.360> the<01:13:45.360> protocol 01:13:46.229 --> 01:13:46.239 align:start position:0% mapping instead of being in the protocol 01:13:46.239 --> 01:13:48.550 align:start position:0% mapping instead of being in the protocol owned<01:13:47.239> registry<01:13:47.760> it<01:13:47.840> will<01:13:48.000> be<01:13:48.199> here<01:13:48.320> in<01:13:48.480> the 01:13:48.550 --> 01:13:48.560 align:start position:0% owned registry it will be here in the 01:13:48.560 --> 01:13:51.149 align:start position:0% owned registry it will be here in the Universal<01:13:49.320> pre-confirmation<01:13:50.159> registry 01:13:51.149 --> 01:13:51.159 align:start position:0% Universal pre-confirmation registry 01:13:51.159 --> 01:13:53.189 align:start position:0% Universal pre-confirmation registry along<01:13:51.480> with<01:13:51.679> that<01:13:52.280> so<01:13:52.440> the<01:13:52.560> slashing 01:13:53.189 --> 01:13:53.199 align:start position:0% along with that so the slashing 01:13:53.199 --> 01:13:54.790 align:start position:0% along with that so the slashing condition<01:13:53.480> optin<01:13:53.960> this<01:13:54.080> is<01:13:54.199> a<01:13:54.320> very<01:13:54.480> important 01:13:54.790 --> 01:13:54.800 align:start position:0% condition optin this is a very important 01:13:54.800 --> 01:13:55.550 align:start position:0% condition optin this is a very important aspect 01:13:55.550 --> 01:13:55.560 align:start position:0% aspect 01:13:55.560 --> 01:13:57.950 align:start position:0% aspect ECT<01:13:56.560> so 01:13:57.950 --> 01:13:57.960 align:start position:0% ECT so 01:13:57.960 --> 01:14:01.510 align:start position:0% ECT so the<01:13:58.960> uh<01:13:59.320> rollup<01:13:59.800> protocol<01:14:00.520> like<01:14:00.760> whether 01:14:01.510 --> 01:14:01.520 align:start position:0% the uh rollup protocol like whether 01:14:01.520 --> 01:14:04.110 align:start position:0% the uh rollup protocol like whether whoever<01:14:02.320> makes<01:14:02.639> another<01:14:02.920> base<01:14:03.159> rollup<01:14:03.880> wants 01:14:04.110 --> 01:14:04.120 align:start position:0% whoever makes another base rollup wants 01:14:04.120 --> 01:14:06.070 align:start position:0% whoever makes another base rollup wants to<01:14:04.360> have<01:14:04.600> might<01:14:04.800> want<01:14:05.000> to<01:14:05.159> have<01:14:05.400> their<01:14:05.600> own<01:14:05.880> set 01:14:06.070 --> 01:14:06.080 align:start position:0% to have might want to have their own set 01:14:06.080 --> 01:14:07.590 align:start position:0% to have might want to have their own set of<01:14:06.440> conditions<01:14:06.760> based<01:14:07.040> on<01:14:07.199> which<01:14:07.360> they<01:14:07.480> want 01:14:07.590 --> 01:14:07.600 align:start position:0% of conditions based on which they want 01:14:07.600 --> 01:14:09.830 align:start position:0% of conditions based on which they want to<01:14:07.760> slash<01:14:08.679> so<01:14:08.960> maybe<01:14:09.239> they<01:14:09.360> don't<01:14:09.560> want<01:14:09.679> to 01:14:09.830 --> 01:14:09.840 align:start position:0% to slash so maybe they don't want to 01:14:09.840 --> 01:14:11.910 align:start position:0% to slash so maybe they don't want to slash<01:14:10.400> inclusion<01:14:10.840> proms<01:14:11.400> they<01:14:11.480> want<01:14:11.600> to<01:14:11.760> just 01:14:11.910 --> 01:14:11.920 align:start position:0% slash inclusion proms they want to just 01:14:11.920 --> 01:14:15.270 align:start position:0% slash inclusion proms they want to just slash<01:14:12.440> execution<01:14:13.080> pre-s<01:14:14.080> so<01:14:14.639> they<01:14:14.800> can<01:14:14.960> Define 01:14:15.270 --> 01:14:15.280 align:start position:0% slash execution pre-s so they can Define 01:14:15.280 --> 01:14:17.709 align:start position:0% slash execution pre-s so they can Define their<01:14:15.440> own<01:14:15.639> slashing<01:14:16.280> conditions<01:14:17.199> and<01:14:17.360> then 01:14:17.709 --> 01:14:17.719 align:start position:0% their own slashing conditions and then 01:14:17.719 --> 01:14:20.990 align:start position:0% their own slashing conditions and then only<01:14:18.400> have<01:14:18.760> those<01:14:19.120> proposers<01:14:19.840> who<01:14:20.000> have<01:14:20.639> opted 01:14:20.990 --> 01:14:21.000 align:start position:0% only have those proposers who have opted 01:14:21.000 --> 01:14:23.709 align:start position:0% only have those proposers who have opted into<01:14:21.360> these<01:14:21.639> slashing<01:14:22.320> conditions<01:14:23.040> be<01:14:23.440> prec 01:14:23.709 --> 01:14:23.719 align:start position:0% into these slashing conditions be prec 01:14:23.719 --> 01:14:25.590 align:start position:0% into these slashing conditions be prec confers<01:14:24.280> for<01:14:24.760> their 01:14:25.590 --> 01:14:25.600 align:start position:0% confers for their 01:14:25.600 --> 01:14:28.149 align:start position:0% confers for their roll<01:14:25.880> up<01:14:26.760> so<01:14:26.960> yeah<01:14:27.120> this<01:14:27.239> is<01:14:27.360> still<01:14:27.600> an<01:14:27.719> ongoing 01:14:28.149 --> 01:14:28.159 align:start position:0% roll up so yeah this is still an ongoing 01:14:28.159 --> 01:14:29.669 align:start position:0% roll up so yeah this is still an ongoing discussion<01:14:28.520> in<01:14:28.639> the<01:14:28.760> community<01:14:29.360> and 01:14:29.669 --> 01:14:29.679 align:start position:0% discussion in the community and 01:14:29.679 --> 01:14:31.189 align:start position:0% discussion in the community and eventually<01:14:30.159> there<01:14:30.320> will<01:14:30.520> be<01:14:30.800> we<01:14:30.920> will<01:14:31.080> be 01:14:31.189 --> 01:14:31.199 align:start position:0% eventually there will be we will be 01:14:31.199 --> 01:14:33.430 align:start position:0% eventually there will be we will be specking<01:14:31.560> it<01:14:31.719> all<01:14:31.840> out<01:14:32.080> and<01:14:32.239> releasing<01:14:32.679> it<01:14:32.920> but 01:14:33.430 --> 01:14:33.440 align:start position:0% specking it all out and releasing it but 01:14:33.440 --> 01:14:36.590 align:start position:0% specking it all out and releasing it but yeah<01:14:33.639> that's<01:14:34.320> it's<01:14:34.480> going<01:14:34.600> to<01:14:34.719> be<01:14:34.880> a 01:14:36.590 --> 01:14:36.600 align:start position:0% yeah that's it's going to be a 01:14:36.600 --> 01:14:44.229 align:start position:0% yeah that's it's going to be a while<01:14:37.600> well<01:14:37.920> that's<01:14:38.239> it<01:14:38.760> thank<01:14:38.920> you<01:14:39.080> so 01:14:44.229 --> 01:14:44.239 align:start position:0% 01:14:44.239 --> 01:14:46.629 align:start position:0% much<01:14:45.239> okay<01:14:45.440> there's<01:14:45.600> a<01:14:45.760> question 01:14:46.629 --> 01:14:46.639 align:start position:0% much okay there's a question 01:14:46.639 --> 01:14:49.030 align:start position:0% much okay there's a question here<01:14:47.639> how<01:14:47.760> do<01:14:47.880> you<01:14:48.000> see<01:14:48.280> this<01:14:48.480> integrating 01:14:49.030 --> 01:14:49.040 align:start position:0% here how do you see this integrating 01:14:49.040 --> 01:14:51.470 align:start position:0% here how do you see this integrating into<01:14:49.360> existing<01:14:49.800> kyc<01:14:50.360> systems<01:14:50.719> or<01:14:50.960> rather<01:14:51.280> the 01:14:51.470 --> 01:14:51.480 align:start position:0% into existing kyc systems or rather the 01:14:51.480 --> 01:14:54.550 align:start position:0% into existing kyc systems or rather the path<01:14:51.719> to<01:14:51.960> scale<01:14:52.520> and<01:14:53.520> adoption<01:14:54.040> on<01:14:54.199> the<01:14:54.400> side 01:14:54.550 --> 01:14:54.560 align:start position:0% path to scale and adoption on the side 01:14:54.560 --> 01:14:57.110 align:start position:0% path to scale and adoption on the side of<01:14:54.679> us<01:14:55.000> users<01:14:55.280> and<01:14:55.719> institutions<01:14:56.719> I'm<01:14:56.960> not 01:14:57.110 --> 01:14:57.120 align:start position:0% of us users and institutions I'm not 01:14:57.120 --> 01:14:59.229 align:start position:0% of us users and institutions I'm not sure<01:14:57.520> that's<01:14:57.679> a<01:14:57.920> question<01:14:58.239> for<01:14:58.440> the<01:14:58.600> session 01:14:59.229 --> 01:14:59.239 align:start position:0% sure that's a question for the session 01:14:59.239 --> 01:15:02.149 align:start position:0% sure that's a question for the session yeah 01:15:02.149 --> 01:15:02.159 align:start position:0% 01:15:02.159 --> 01:15:05.350 align:start position:0% yeah<01:15:03.159> all<01:15:03.320> right<01:15:03.560> so<01:15:03.840> any 01:15:05.350 --> 01:15:05.360 align:start position:0% yeah all right so any 01:15:05.360 --> 01:15:09.110 align:start position:0% yeah all right so any questions<01:15:06.480> final<01:15:07.520> how's<01:15:08.520> how<01:15:08.679> how<01:15:08.800> do<01:15:08.920> I 01:15:09.110 --> 01:15:09.120 align:start position:0% questions final how's how how do I 01:15:09.120 --> 01:15:12.950 align:start position:0% questions final how's how how do I evaluate<01:15:09.560> the<01:15:09.719> security<01:15:10.199> of<01:15:10.320> a<01:15:11.120> say<01:15:11.800> I<01:15:12.800> I 01:15:12.950 --> 01:15:12.960 align:start position:0% evaluate the security of a say I I 01:15:12.960 --> 01:15:16.750 align:start position:0% evaluate the security of a say I I probably<01:15:13.239> doesn't<01:15:13.600> care<01:15:14.159> if<01:15:14.280> I<01:15:14.400> send<01:15:14.840> million 01:15:16.750 --> 01:15:16.760 align:start position:0% probably doesn't care if I send million 01:15:16.760 --> 01:15:19.990 align:start position:0% probably doesn't care if I send million I<01:15:17.760> if<01:15:18.120> they 01:15:19.990 --> 01:15:20.000 align:start position:0% I if they 01:15:20.000 --> 01:15:23.590 align:start position:0% I if they say<01:15:21.000> right<01:15:21.639> so<01:15:22.000> what<01:15:22.120> you're<01:15:22.400> asking<01:15:22.840> about<01:15:23.280> is 01:15:23.590 --> 01:15:23.600 align:start position:0% say right so what you're asking about is 01:15:23.600 --> 01:15:26.590 align:start position:0% say right so what you're asking about is the<01:15:23.840> fair<01:15:24.239> exchange<01:15:24.679> problem 01:15:26.590 --> 01:15:26.600 align:start position:0% the fair exchange problem 01:15:26.600 --> 01:15:28.590 align:start position:0% the fair exchange problem and<01:15:27.040> this<01:15:27.159> is<01:15:27.360> something<01:15:27.800> that<01:15:28.000> our<01:15:28.239> research 01:15:28.590 --> 01:15:28.600 align:start position:0% and this is something that our research 01:15:28.600 --> 01:15:30.470 align:start position:0% and this is something that our research team<01:15:28.840> has<01:15:28.960> been<01:15:29.120> looking<01:15:29.440> into<01:15:29.920> for<01:15:30.199> quite 01:15:30.470 --> 01:15:30.480 align:start position:0% team has been looking into for quite 01:15:30.480 --> 01:15:33.669 align:start position:0% team has been looking into for quite some<01:15:30.719> time<01:15:31.040> now<01:15:32.040> um<01:15:32.560> as<01:15:32.679> of<01:15:32.880> now<01:15:33.199> we<01:15:33.320> don't<01:15:33.520> have 01:15:33.669 --> 01:15:33.679 align:start position:0% some time now um as of now we don't have 01:15:33.679 --> 01:15:36.669 align:start position:0% some time now um as of now we don't have a<01:15:33.840> solution<01:15:34.320> for<01:15:34.480> the<01:15:34.600> fair<01:15:34.880> exchange<01:15:35.679> problem 01:15:36.669 --> 01:15:36.679 align:start position:0% a solution for the fair exchange problem 01:15:36.679 --> 01:15:40.750 align:start position:0% a solution for the fair exchange problem um<01:15:37.480> and<01:15:37.679> I<01:15:37.840> think<01:15:38.560> most<01:15:38.880> of<01:15:39.199> the<01:15:39.760> existing<01:15:40.440> or 01:15:40.750 --> 01:15:40.760 align:start position:0% um and I think most of the existing or 01:15:40.760 --> 01:15:42.750 align:start position:0% um and I think most of the existing or proposed<01:15:41.280> Solutions<01:15:41.880> depend<01:15:42.320> on<01:15:42.520> a 01:15:42.750 --> 01:15:42.760 align:start position:0% proposed Solutions depend on a 01:15:42.760 --> 01:15:46.790 align:start position:0% proposed Solutions depend on a reputation<01:15:43.400> system<01:15:43.840> as<01:15:43.960> of<01:15:44.159> now<01:15:45.320> where<01:15:46.320> um<01:15:46.600> if 01:15:46.790 --> 01:15:46.800 align:start position:0% reputation system as of now where um if 01:15:46.800 --> 01:15:49.149 align:start position:0% reputation system as of now where um if the<01:15:47.000> pre-c<01:15:47.280> confer<01:15:47.719> or<01:15:48.400> the<01:15:48.560> Gateway 01:15:49.149 --> 01:15:49.159 align:start position:0% the pre-c confer or the Gateway 01:15:49.159 --> 01:15:51.430 align:start position:0% the pre-c confer or the Gateway providing<01:15:49.560> the<01:15:49.800> pre-confirmation 01:15:51.430 --> 01:15:51.440 align:start position:0% providing the pre-confirmation 01:15:51.440 --> 01:15:55.229 align:start position:0% providing the pre-confirmation um<01:15:52.440> uh<01:15:52.639> is<01:15:52.960> acting<01:15:53.280> maliciously<01:15:54.199> they<01:15:54.400> would 01:15:55.229 --> 01:15:55.239 align:start position:0% um uh is acting maliciously they would 01:15:55.239 --> 01:15:56.950 align:start position:0% um uh is acting maliciously they would this<01:15:55.360> would<01:15:55.639> affect<01:15:55.920> the<01:15:56.120> reputation<01:15:56.639> in<01:15:56.760> a 01:15:56.950 --> 01:15:56.960 align:start position:0% this would affect the reputation in a 01:15:56.960 --> 01:15:59.870 align:start position:0% this would affect the reputation in a bad<01:15:57.239> way<01:15:57.760> and<01:15:57.960> they<01:15:58.120> would<01:15:58.400> potentially<01:15:58.920> be<01:15:59.719> uh 01:15:59.870 --> 01:15:59.880 align:start position:0% bad way and they would potentially be uh 01:15:59.880 --> 01:16:02.470 align:start position:0% bad way and they would potentially be uh cut<01:16:00.199> out<01:16:00.600> of<01:16:00.840> pre<01:16:01.159> confing<01:16:01.520> for<01:16:01.840> the<01:16:02.080> specific 01:16:02.470 --> 01:16:02.480 align:start position:0% cut out of pre confing for the specific 01:16:02.480 --> 01:16:04.870 align:start position:0% cut out of pre confing for the specific protocol<01:16:02.960> they're<01:16:03.159> working<01:16:03.480> on<01:16:04.360> and<01:16:04.679> this 01:16:04.870 --> 01:16:04.880 align:start position:0% protocol they're working on and this 01:16:04.880 --> 01:16:08.070 align:start position:0% protocol they're working on and this would<01:16:05.880> potentially<01:16:06.679> lead<01:16:07.000> them<01:16:07.120> for<01:16:07.360> losses 01:16:08.070 --> 01:16:08.080 align:start position:0% would potentially lead them for losses 01:16:08.080 --> 01:16:11.950 align:start position:0% would potentially lead them for losses so<01:16:08.560> they<01:16:09.040> the<01:16:09.320> reputation<01:16:09.880> B<01:16:10.120> system<01:16:11.000> uh<01:16:11.400> being 01:16:11.950 --> 01:16:11.960 align:start position:0% so they the reputation B system uh being 01:16:11.960 --> 01:16:14.590 align:start position:0% so they the reputation B system uh being proposed<01:16:12.400> for<01:16:12.639> now<01:16:13.360> but<01:16:13.560> we<01:16:13.679> are<01:16:13.880> working<01:16:14.239> on<01:16:14.400> a 01:16:14.590 --> 01:16:14.600 align:start position:0% proposed for now but we are working on a 01:16:14.600 --> 01:16:17.030 align:start position:0% proposed for now but we are working on a non-<01:16:14.960> reputation<01:16:15.480> based<01:16:15.800> system<01:16:16.280> where<01:16:16.840> there 01:16:17.030 --> 01:16:17.040 align:start position:0% non- reputation based system where there 01:16:17.040 --> 01:16:21.430 align:start position:0% non- reputation based system where there is<01:16:17.960> um<01:16:18.520> some<01:16:18.960> oversight<01:16:19.760> over<01:16:20.520> how<01:16:20.920> the<01:16:21.199> pre-c 01:16:21.430 --> 01:16:21.440 align:start position:0% is um some oversight over how the pre-c 01:16:21.440 --> 01:16:24.149 align:start position:0% is um some oversight over how the pre-c comers<01:16:21.840> are<01:16:22.080> acting<01:16:22.719> and<01:16:22.920> if<01:16:23.159> they<01:16:23.320> are 01:16:24.149 --> 01:16:24.159 align:start position:0% comers are acting and if they are 01:16:24.159 --> 01:16:26.910 align:start position:0% comers are acting and if they are actually<01:16:24.960> pre<01:16:25.239> confing<01:16:25.600> in<01:16:25.800> the<01:16:25.960> correct<01:16:26.400> time 01:16:26.910 --> 01:16:26.920 align:start position:0% actually pre confing in the correct time 01:16:26.920 --> 01:16:29.110 align:start position:0% actually pre confing in the correct time providing<01:16:27.360> pre<01:16:27.600> confirmations<01:16:28.400> in<01:16:28.520> a<01:16:28.719> timely 01:16:29.110 --> 01:16:29.120 align:start position:0% providing pre confirmations in a timely 01:16:29.120 --> 01:16:32.830 align:start position:0% providing pre confirmations in a timely manner<01:16:30.000> without<01:16:30.920> like<01:16:31.600> um<01:16:31.880> delaying<01:16:32.560> the 01:16:32.830 --> 01:16:32.840 align:start position:0% manner without like um delaying the 01:16:32.840 --> 01:16:35.030 align:start position:0% manner without like um delaying the pre-confirmation<01:16:33.280> by<01:16:34.040> the<01:16:34.239> you<01:16:34.520> from<01:16:34.760> coming 01:16:35.030 --> 01:16:35.040 align:start position:0% pre-confirmation by the you from coming 01:16:35.040 --> 01:16:39.510 align:start position:0% pre-confirmation by the you from coming from<01:16:35.280> the<01:16:35.440> users<01:16:36.600> or<01:16:37.600> um<01:16:38.000> um<01:16:38.199> like<01:16:38.520> reordering 01:16:39.510 --> 01:16:39.520 align:start position:0% from the users or um um like reordering 01:16:39.520 --> 01:16:43.390 align:start position:0% from the users or um um like reordering transactions<01:16:40.520> uh<01:16:41.120> with<01:16:41.320> this<01:16:41.520> delay<01:16:42.360> to<01:16:42.800> to<01:16:43.159> to 01:16:43.390 --> 01:16:43.400 align:start position:0% transactions uh with this delay to to to 01:16:43.400 --> 01:16:47.270 align:start position:0% transactions uh with this delay to to to just<01:16:43.679> generate<01:16:44.120> more<01:16:44.400> meev<01:16:45.000> or<01:16:45.239> or<01:16:45.560> profit<01:16:45.880> for 01:16:47.270 --> 01:16:47.280 align:start position:0% just generate more meev or or profit for 01:16:47.280 --> 01:16:49.950 align:start position:0% just generate more meev or or profit for themselves<01:16:48.280> there's<01:16:48.480> another<01:16:48.800> question<01:16:49.199> here 01:16:49.950 --> 01:16:49.960 align:start position:0% themselves there's another question here 01:16:49.960 --> 01:16:51.669 align:start position:0% themselves there's another question here what<01:16:50.159> kind<01:16:50.320> of<01:16:50.440> slashing<01:16:51.080> conditions<01:16:51.400> do<01:16:51.520> you 01:16:51.669 --> 01:16:51.679 align:start position:0% what kind of slashing conditions do you 01:16:51.679 --> 01:16:55.310 align:start position:0% what kind of slashing conditions do you see<01:16:52.360> is<01:16:52.480> it<01:16:52.600> a<01:16:52.760> penalty<01:16:53.239> or<01:16:53.480> more<01:16:53.760> tougher 01:16:55.310 --> 01:16:55.320 align:start position:0% see is it a penalty or more tougher 01:16:55.320 --> 01:16:57.590 align:start position:0% see is it a penalty or more tougher so<01:16:55.920> I<01:16:56.040> think<01:16:56.320> right<01:16:56.520> now<01:16:56.719> our<01:16:56.920> slashing 01:16:57.590 --> 01:16:57.600 align:start position:0% so I think right now our slashing 01:16:57.600 --> 01:16:59.750 align:start position:0% so I think right now our slashing condition<01:16:57.880> is<01:16:58.360> very<01:16:58.600> straightforward<01:16:59.400> we 01:16:59.750 --> 01:16:59.760 align:start position:0% condition is very straightforward we 01:16:59.760 --> 01:17:02.510 align:start position:0% condition is very straightforward we just<01:16:59.960> slash<01:17:00.560> the<01:17:00.719> entire<01:17:01.120> stake<01:17:01.600> which<01:17:02.080> is<01:17:02.280> not 01:17:02.510 --> 01:17:02.520 align:start position:0% just slash the entire stake which is not 01:17:02.520 --> 01:17:04.470 align:start position:0% just slash the entire stake which is not ideal<01:17:03.280> and<01:17:03.400> it's<01:17:03.600> definitely<01:17:04.000> not<01:17:04.199> going<01:17:04.360> to 01:17:04.470 --> 01:17:04.480 align:start position:0% ideal and it's definitely not going to 01:17:04.480 --> 01:17:06.910 align:start position:0% ideal and it's definitely not going to be<01:17:04.639> this<01:17:05.000> eventually<01:17:06.000> I<01:17:06.080> think<01:17:06.280> there<01:17:06.360> was<01:17:06.600> one 01:17:06.910 --> 01:17:06.920 align:start position:0% be this eventually I think there was one 01:17:06.920 --> 01:17:08.510 align:start position:0% be this eventually I think there was one there<01:17:07.040> is<01:17:07.239> one<01:17:07.440> proposal<01:17:07.880> by<01:17:08.000> the<01:17:08.120> research 01:17:08.510 --> 01:17:08.520 align:start position:0% there is one proposal by the research 01:17:08.520 --> 01:17:11.750 align:start position:0% there is one proposal by the research team<01:17:09.199> and<01:17:09.400> that's<01:17:09.760> we<01:17:09.960> have<01:17:10.440> let's<01:17:10.639> say<01:17:11.000> slash 01:17:11.750 --> 01:17:11.760 align:start position:0% team and that's we have let's say slash 01:17:11.760 --> 01:17:14.470 align:start position:0% team and that's we have let's say slash tickets<01:17:12.760> so<01:17:13.239> for<01:17:13.639> every<01:17:13.960> pre-confirmation 01:17:14.470 --> 01:17:14.480 align:start position:0% tickets so for every pre-confirmation 01:17:14.480 --> 01:17:17.470 align:start position:0% tickets so for every pre-confirmation that<01:17:14.920> you<01:17:15.080> provide<01:17:15.760> and<01:17:16.120> every<01:17:16.840> validator 01:17:17.470 --> 01:17:17.480 align:start position:0% that you provide and every validator 01:17:17.480 --> 01:17:20.430 align:start position:0% that you provide and every validator that<01:17:17.600> you<01:17:17.880> register<01:17:18.880> you<01:17:19.120> have<01:17:19.600> a<01:17:19.920> a<01:17:20.080> fixed 01:17:20.430 --> 01:17:20.440 align:start position:0% that you register you have a a fixed 01:17:20.440 --> 01:17:22.510 align:start position:0% that you register you have a a fixed amount<01:17:20.679> of<01:17:20.800> stake<01:17:21.719> so<01:17:21.880> for<01:17:22.080> pre-confirmation 01:17:22.510 --> 01:17:22.520 align:start position:0% amount of stake so for pre-confirmation 01:17:22.520 --> 01:17:24.430 align:start position:0% amount of stake so for pre-confirmation let's<01:17:23.080> say<01:17:23.239> you<01:17:23.320> are<01:17:23.440> staking<01:17:23.800> one<01:17:24.000> eth<01:17:24.280> for 01:17:24.430 --> 01:17:24.440 align:start position:0% let's say you are staking one eth for 01:17:24.440 --> 01:17:26.950 align:start position:0% let's say you are staking one eth for every<01:17:24.880> pre<01:17:25.080> confirmation<01:17:25.520> that<01:17:25.639> you<01:17:25.960> provide 01:17:26.950 --> 01:17:26.960 align:start position:0% every pre confirmation that you provide 01:17:26.960 --> 01:17:29.669 align:start position:0% every pre confirmation that you provide and<01:17:27.400> once<01:17:28.000> the<01:17:28.120> pre-confirmation<01:17:28.560> is<01:17:28.920> settled 01:17:29.669 --> 01:17:29.679 align:start position:0% and once the pre-confirmation is settled 01:17:29.679 --> 01:17:32.070 align:start position:0% and once the pre-confirmation is settled you<01:17:29.840> can<01:17:30.120> basically<01:17:30.480> reuse<01:17:30.880> those<01:17:31.080> tickets 01:17:32.070 --> 01:17:32.080 align:start position:0% you can basically reuse those tickets 01:17:32.080 --> 01:17:34.990 align:start position:0% you can basically reuse those tickets but<01:17:32.320> if<01:17:32.480> you<01:17:33.120> mess<01:17:33.360> up<01:17:33.639> that<01:17:34.000> reconfirmation 01:17:34.990 --> 01:17:35.000 align:start position:0% but if you mess up that reconfirmation 01:17:35.000 --> 01:17:37.110 align:start position:0% but if you mess up that reconfirmation only<01:17:35.440> that<01:17:35.600> one<01:17:35.800> e<01:17:36.120> amount<01:17:36.400> will<01:17:36.520> be<01:17:36.639> slashed 01:17:37.110 --> 01:17:37.120 align:start position:0% only that one e amount will be slashed 01:17:37.120 --> 01:17:39.310 align:start position:0% only that one e amount will be slashed and<01:17:37.280> not<01:17:37.440> your<01:17:37.600> entire<01:17:37.960> stake<01:17:38.800> so<01:17:39.000> this<01:17:39.120> is 01:17:39.310 --> 01:17:39.320 align:start position:0% and not your entire stake so this is 01:17:39.320 --> 01:17:41.750 align:start position:0% and not your entire stake so this is open<01:17:39.560> for<01:17:39.840> discussion<01:17:40.480> and<01:17:40.679> one<01:17:40.920> once<01:17:41.159> again<01:17:41.679> I 01:17:41.750 --> 01:17:41.760 align:start position:0% open for discussion and one once again I 01:17:41.760 --> 01:17:43.189 align:start position:0% open for discussion and one once again I think<01:17:41.920> this<01:17:42.040> is<01:17:42.159> a<01:17:42.320> part<01:17:42.560> this<01:17:42.679> will<01:17:42.840> be<01:17:42.960> a<01:17:43.080> part 01:17:43.189 --> 01:17:43.199 align:start position:0% think this is a part this will be a part 01:17:43.199 --> 01:17:45.390 align:start position:0% think this is a part this will be a part of<01:17:43.320> the<01:17:43.440> community-led<01:17:44.080> discussion<01:17:44.840> of<01:17:45.080> how 01:17:45.390 --> 01:17:45.400 align:start position:0% of the community-led discussion of how 01:17:45.400 --> 01:17:48.430 align:start position:0% of the community-led discussion of how seriously<01:17:45.880> we<01:17:46.000> want<01:17:46.159> to<01:17:46.280> slash<01:17:47.159> a<01:17:47.560> a<01:17:48.280> a 01:17:48.430 --> 01:17:48.440 align:start position:0% seriously we want to slash a a a 01:17:48.440 --> 01:17:49.790 align:start position:0% seriously we want to slash a a a malicious<01:17:48.960> prec 01:17:49.790 --> 01:17:49.800 align:start position:0% malicious prec 01:17:49.800 --> 01:17:55.270 align:start position:0% malicious prec confirm<01:17:51.239> uh<01:17:52.400> sorry<01:17:53.400> how<01:17:53.679> do<01:17:53.840> you<01:17:54.080> think<01:17:54.679> uh 01:17:55.270 --> 01:17:55.280 align:start position:0% confirm uh sorry how do you think uh 01:17:55.280 --> 01:17:58.430 align:start position:0% confirm uh sorry how do you think uh distributed<01:17:56.000> validator<01:17:57.000> technology<01:17:57.719> fits 01:17:58.430 --> 01:17:58.440 align:start position:0% distributed validator technology fits 01:17:58.440 --> 01:18:01.950 align:start position:0% distributed validator technology fits into<01:17:58.800> your<01:17:59.360> prec<01:17:59.760> confirmation<01:18:00.840> design<01:18:01.840> do 01:18:01.950 --> 01:18:01.960 align:start position:0% into your prec confirmation design do 01:18:01.960 --> 01:18:04.669 align:start position:0% into your prec confirmation design do you<01:18:02.120> think<01:18:02.320> it<01:18:02.440> could<01:18:02.600> make<01:18:02.800> it<01:18:03.000> much<01:18:03.320> more 01:18:04.669 --> 01:18:04.679 align:start position:0% you think it could make it much more 01:18:04.679 --> 01:18:08.430 align:start position:0% you think it could make it much more secure<01:18:06.080> or<01:18:07.080> have<01:18:07.400> have<01:18:07.520> you<01:18:07.679> guys<01:18:07.840> looked<01:18:08.120> into 01:18:08.430 --> 01:18:08.440 align:start position:0% secure or have have you guys looked into 01:18:08.440 --> 01:18:14.270 align:start position:0% secure or have have you guys looked into that<01:18:09.199> H<01:18:10.520> so<01:18:11.520> in<01:18:12.000> DVT<01:18:13.000> I'm<01:18:13.159> not<01:18:13.400> entirely<01:18:13.880> sure 01:18:14.270 --> 01:18:14.280 align:start position:0% that H so in DVT I'm not entirely sure 01:18:14.280 --> 01:18:17.189 align:start position:0% that H so in DVT I'm not entirely sure about<01:18:15.280> the<01:18:15.440> block<01:18:15.840> proposal<01:18:16.679> and<01:18:16.880> how<01:18:17.040> it 01:18:17.189 --> 01:18:17.199 align:start position:0% about the block proposal and how it 01:18:17.199 --> 01:18:21.590 align:start position:0% about the block proposal and how it works<01:18:17.639> exactly<01:18:18.520> so<01:18:19.199> uh<01:18:20.199> I<01:18:20.400> I<01:18:20.639> know<01:18:21.080> that<01:18:21.320> for 01:18:21.590 --> 01:18:21.600 align:start position:0% works exactly so uh I I know that for 01:18:21.600 --> 01:18:22.470 align:start position:0% works exactly so uh I I know that for the 01:18:22.470 --> 01:18:22.480 align:start position:0% the 01:18:22.480 --> 01:18:25.430 align:start position:0% the attestation<01:18:23.480> uh<01:18:23.639> multiple<01:18:24.600> uh 01:18:25.430 --> 01:18:25.440 align:start position:0% attestation uh multiple uh 01:18:25.440 --> 01:18:28.310 align:start position:0% attestation uh multiple uh like<01:18:25.639> three<01:18:25.880> out<01:18:26.040> of<01:18:26.520> four<01:18:27.520> nodes<01:18:28.000> they<01:18:28.120> need 01:18:28.310 --> 01:18:28.320 align:start position:0% like three out of four nodes they need 01:18:28.320 --> 01:18:31.390 align:start position:0% like three out of four nodes they need to<01:18:28.800> sign<01:18:29.280> basically<01:18:29.719> to<01:18:29.920> get<01:18:30.199> a<01:18:30.600> proper<01:18:30.920> signat 01:18:31.390 --> 01:18:31.400 align:start position:0% to sign basically to get a proper signat 01:18:31.400 --> 01:18:35.709 align:start position:0% to sign basically to get a proper signat a<01:18:31.480> BLS<01:18:32.239> signature<01:18:33.679> and<01:18:34.679> um<01:18:34.960> I<01:18:35.080> think<01:18:35.320> it's<01:18:35.560> kind 01:18:35.709 --> 01:18:35.719 align:start position:0% a BLS signature and um I think it's kind 01:18:35.719 --> 01:18:37.910 align:start position:0% a BLS signature and um I think it's kind of<01:18:35.920> the<01:18:36.040> same<01:18:36.280> for<01:18:36.520> the<01:18:36.760> proposal<01:18:37.320> but<01:18:37.520> I'm<01:18:37.719> not 01:18:37.910 --> 01:18:37.920 align:start position:0% of the same for the proposal but I'm not 01:18:37.920 --> 01:18:39.950 align:start position:0% of the same for the proposal but I'm not sure<01:18:38.320> how<01:18:38.520> they<01:18:38.679> choose<01:18:39.239> which<01:18:39.440> one<01:18:39.639> of<01:18:39.800> the 01:18:39.950 --> 01:18:39.960 align:start position:0% sure how they choose which one of the 01:18:39.960 --> 01:18:41.910 align:start position:0% sure how they choose which one of the nodes<01:18:40.400> is<01:18:40.560> the<01:18:40.679> one<01:18:40.920> who<01:18:41.000> is<01:18:41.239> responsible<01:18:41.719> for 01:18:41.910 --> 01:18:41.920 align:start position:0% nodes is the one who is responsible for 01:18:41.920 --> 01:18:44.870 align:start position:0% nodes is the one who is responsible for forming<01:18:42.400> the<01:18:42.520> block<01:18:43.360> so<01:18:43.600> honestly<01:18:44.080> no<01:18:44.560> uh<01:18:44.679> we 01:18:44.870 --> 01:18:44.880 align:start position:0% forming the block so honestly no uh we 01:18:44.880 --> 01:18:47.910 align:start position:0% forming the block so honestly no uh we have<01:18:45.080> not<01:18:45.320> looked<01:18:45.600> into<01:18:46.320> how<01:18:46.639> D<01:18:47.040> DVT<01:18:47.639> would 01:18:47.910 --> 01:18:47.920 align:start position:0% have not looked into how D DVT would 01:18:47.920 --> 01:18:50.629 align:start position:0% have not looked into how D DVT would interact<01:18:48.600> with<01:18:49.040> with<01:18:49.199> this<01:18:49.400> protocol<01:18:50.199> at<01:18:50.360> this 01:18:50.629 --> 01:18:50.639 align:start position:0% interact with with this protocol at this 01:18:50.639 --> 01:18:54.390 align:start position:0% interact with with this protocol at this moment<01:18:51.639> uh<01:18:51.880> because<01:18:52.560> also<01:18:52.880> DVT<01:18:53.639> does<01:18:53.880> not<01:18:54.080> form 01:18:54.390 --> 01:18:54.400 align:start position:0% moment uh because also DVT does not form 01:18:54.400 --> 01:18:55.270 align:start position:0% moment uh because also DVT does not form a 01:18:55.270 --> 01:18:55.280 align:start position:0% a 01:18:55.280 --> 01:18:58.590 align:start position:0% a significant<01:18:56.280> um<01:18:56.960> like<01:18:57.440> um<01:18:57.679> share<01:18:58.199> in<01:18:58.400> the 01:18:58.590 --> 01:18:58.600 align:start position:0% significant um like um share in the 01:18:58.600 --> 01:19:02.629 align:start position:0% significant um like um share in the market<01:18:58.960> of<01:18:59.199> proposers<01:18:59.840> as<01:18:59.960> of<01:19:00.199> now<01:19:00.920> so<01:19:01.360> it<01:19:01.679> it 01:19:02.629 --> 01:19:02.639 align:start position:0% market of proposers as of now so it it 01:19:02.639 --> 01:19:04.750 align:start position:0% market of proposers as of now so it it it<01:19:03.040> would<01:19:03.280> it<01:19:03.440> might<01:19:03.679> not<01:19:03.880> make<01:19:04.120> sense<01:19:04.360> for<01:19:04.560> us 01:19:04.750 --> 01:19:04.760 align:start position:0% it would it might not make sense for us 01:19:04.760 --> 01:19:07.550 align:start position:0% it would it might not make sense for us to<01:19:04.920> look<01:19:05.120> into<01:19:05.480> it<01:19:05.920> in<01:19:06.080> a<01:19:06.280> serious<01:19:07.120> um<01:19:07.280> in<01:19:07.400> a 01:19:07.550 --> 01:19:07.560 align:start position:0% to look into it in a serious um in a 01:19:07.560 --> 01:19:09.950 align:start position:0% to look into it in a serious um in a serious<01:19:07.920> manner<01:19:08.280> but<01:19:08.639> potentially<01:19:09.639> if<01:19:09.760> it 01:19:09.950 --> 01:19:09.960 align:start position:0% serious manner but potentially if it 01:19:09.960 --> 01:19:13.070 align:start position:0% serious manner but potentially if it becomes<01:19:10.360> more<01:19:10.760> popular<01:19:11.639> then<01:19:11.920> yeah<01:19:12.920> this 01:19:13.070 --> 01:19:13.080 align:start position:0% becomes more popular then yeah this 01:19:13.080 --> 01:19:17.950 align:start position:0% becomes more popular then yeah this would<01:19:13.320> make 01:19:17.950 --> 01:19:17.960 align:start position:0% 01:19:17.960 --> 01:19:21.350 align:start position:0% sense<01:19:18.960> you<01:19:19.080> have<01:19:19.239> any<01:19:19.480> website<01:19:20.000> for<01:19:20.880> networ 01:19:21.350 --> 01:19:21.360 align:start position:0% sense you have any website for networ 01:19:21.360 --> 01:19:25.110 align:start position:0% sense you have any website for networ metri<01:19:22.320> how<01:19:22.480> many<01:19:23.199> subscribed<01:19:23.600> to<01:19:23.800> this<01:19:25.000> kind 01:19:25.110 --> 01:19:25.120 align:start position:0% metri how many subscribed to this kind 01:19:25.120 --> 01:19:28.270 align:start position:0% metri how many subscribed to this kind of<01:19:25.320> stuff<01:19:25.960> are<01:19:26.080> you<01:19:26.199> measuring<01:19:26.679> life<01:19:27.199> or<01:19:28.199> I 01:19:28.270 --> 01:19:28.280 align:start position:0% of stuff are you measuring life or I 01:19:28.280 --> 01:19:29.990 align:start position:0% of stuff are you measuring life or I mean<01:19:28.440> this<01:19:28.560> is<01:19:28.840> not<01:19:29.040> yet<01:19:29.159> on<01:19:29.320> Main<01:19:29.560> net<01:19:29.760> because 01:19:29.990 --> 01:19:30.000 align:start position:0% mean this is not yet on Main net because 01:19:30.000 --> 01:19:31.350 align:start position:0% mean this is not yet on Main net because firstly<01:19:30.360> we<01:19:30.480> don't<01:19:30.679> even<01:19:30.880> have<01:19:31.000> the<01:19:31.120> pre- 01:19:31.350 --> 01:19:31.360 align:start position:0% firstly we don't even have the pre- 01:19:31.360 --> 01:19:33.790 align:start position:0% firstly we don't even have the pre- compiles<01:19:31.880> yet<01:19:32.320> we<01:19:32.440> need<01:19:32.920> to<01:19:33.080> have<01:19:33.199> the<01:19:33.320> prra 01:19:33.790 --> 01:19:33.800 align:start position:0% compiles yet we need to have the prra 01:19:33.800 --> 01:19:36.709 align:start position:0% compiles yet we need to have the prra grade<01:19:34.600> so<01:19:35.120> it's<01:19:35.400> it's<01:19:35.520> running<01:19:35.800> on<01:19:35.960> testnet<01:19:36.480> on 01:19:36.709 --> 01:19:36.719 align:start position:0% grade so it's it's running on testnet on 01:19:36.719 --> 01:19:38.830 align:start position:0% grade so it's it's running on testnet on Helder<01:19:37.280> testnet<01:19:38.280> uh<01:19:38.400> have<01:19:38.520> you<01:19:38.600> heard<01:19:38.760> of 01:19:38.830 --> 01:19:38.840 align:start position:0% Helder testnet uh have you heard of 01:19:38.840 --> 01:19:40.310 align:start position:0% Helder testnet uh have you heard of Helder<01:19:39.080> testet<01:19:39.360> it's<01:19:39.440> a<01:19:39.560> devnet<01:19:40.080> which<01:19:40.199> was 01:19:40.310 --> 01:19:40.320 align:start position:0% Helder testet it's a devnet which was 01:19:40.320 --> 01:19:42.709 align:start position:0% Helder testet it's a devnet which was released<01:19:40.679> during<01:19:40.920> each<01:19:41.120> CC<01:19:41.760> so<01:19:42.040> Tao<01:19:42.360> already 01:19:42.709 --> 01:19:42.719 align:start position:0% released during each CC so Tao already 01:19:42.719 --> 01:19:45.149 align:start position:0% released during each CC so Tao already has<01:19:43.520> uh<01:19:43.719> not<01:19:43.920> the<01:19:44.080> final<01:19:44.360> version<01:19:44.760> but<01:19:44.920> one<01:19:45.040> of 01:19:45.149 --> 01:19:45.159 align:start position:0% has uh not the final version but one of 01:19:45.159 --> 01:19:46.669 align:start position:0% has uh not the final version but one of the<01:19:45.280> intermediate<01:19:45.840> versions<01:19:46.239> running<01:19:46.560> on 01:19:46.669 --> 01:19:46.679 align:start position:0% the intermediate versions running on 01:19:46.679 --> 01:19:48.870 align:start position:0% the intermediate versions running on Helder<01:19:47.040> providing<01:19:47.360> pre<01:19:47.560> confirmations<01:19:48.520> but 01:19:48.870 --> 01:19:48.880 align:start position:0% Helder providing pre confirmations but 01:19:48.880 --> 01:19:50.990 align:start position:0% Helder providing pre confirmations but once<01:19:49.120> again<01:19:49.320> that's<01:19:49.440> a<01:19:49.639> devet<01:19:50.120> so<01:19:50.320> it's<01:19:50.600> only 01:19:50.990 --> 01:19:51.000 align:start position:0% once again that's a devet so it's only 01:19:51.000 --> 01:19:53.470 align:start position:0% once again that's a devet so it's only the<01:19:51.120> validators<01:19:51.639> that<01:19:51.800> Tao<01:19:52.159> is<01:19:52.280> running<01:19:53.280> but 01:19:53.470 --> 01:19:53.480 align:start position:0% the validators that Tao is running but 01:19:53.480 --> 01:19:55.470 align:start position:0% the validators that Tao is running but yeah<01:19:53.719> this<01:19:54.000> this<01:19:54.120> was<01:19:54.280> tested<01:19:54.760> using<01:19:55.000> 300 01:19:55.470 --> 01:19:55.480 align:start position:0% yeah this this was tested using 300 01:19:55.480 --> 01:19:59.189 align:start position:0% yeah this this was tested using 300 validators<01:19:56.480> and<01:19:56.719> it<01:19:56.840> worked<01:19:57.199> great<01:19:58.040> yeah<01:19:58.480> okay 01:19:59.189 --> 01:19:59.199 align:start position:0% validators and it worked great yeah okay 01:19:59.199 --> 01:20:11.229 align:start position:0% validators and it worked great yeah okay thank 01:20:11.229 --> 01:20:11.239 align:start position:0% 01:20:11.239 --> 01:20:15.310 align:start position:0% you 01:20:15.310 --> 01:20:15.320 align:start position:0% 01:20:15.320 --> 01:20:17.590 align:start position:0% might<01:20:16.320> if<01:20:16.440> you<01:20:16.560> can<01:20:16.760> speak<01:20:17.000> to<01:20:17.120> the<01:20:17.280> mic 01:20:17.590 --> 01:20:17.600 align:start position:0% might if you can speak to the mic 01:20:17.600 --> 01:20:19.590 align:start position:0% might if you can speak to the mic because<01:20:18.000> I<01:20:18.199> didn't<01:20:18.520> hear<01:20:19.040> half<01:20:19.199> of<01:20:19.360> what<01:20:19.480> you 01:20:19.590 --> 01:20:19.600 align:start position:0% because I didn't hear half of what you 01:20:19.600 --> 01:20:22.430 align:start position:0% because I didn't hear half of what you said<01:20:19.920> yeah<01:20:20.480> how<01:20:20.719> just<01:20:21.360> how<01:20:21.520> do<01:20:21.639> you<01:20:21.880> decide<01:20:22.280> how 01:20:22.430 --> 01:20:22.440 align:start position:0% said yeah how just how do you decide how 01:20:22.440 --> 01:20:24.709 align:start position:0% said yeah how just how do you decide how much<01:20:22.840> you<01:20:23.120> pay<01:20:23.360> for<01:20:23.520> the<01:20:23.679> pre-conference<01:20:24.320> to 01:20:24.709 --> 01:20:24.719 align:start position:0% much you pay for the pre-conference to 01:20:24.719 --> 01:20:27.709 align:start position:0% much you pay for the pre-conference to post<01:20:25.040> the<01:20:25.480> roll<01:20:25.800> up<01:20:26.120> blocks<01:20:27.120> because<01:20:27.440> there 01:20:27.709 --> 01:20:27.719 align:start position:0% post the roll up blocks because there 01:20:27.719 --> 01:20:30.350 align:start position:0% post the roll up blocks because there might<01:20:27.920> be<01:20:28.159> multiple<01:20:28.639> base<01:20:28.880> rollups<01:20:29.560> and<01:20:29.760> for 01:20:30.350 --> 01:20:30.360 align:start position:0% might be multiple base rollups and for 01:20:30.360 --> 01:20:32.310 align:start position:0% might be multiple base rollups and for the<01:20:30.560> slot<01:20:31.080> and<01:20:31.280> they<01:20:31.400> might<01:20:31.560> be<01:20:31.760> compete<01:20:32.120> for 01:20:32.310 --> 01:20:32.320 align:start position:0% the slot and they might be compete for 01:20:32.320 --> 01:20:36.310 align:start position:0% the slot and they might be compete for this<01:20:32.679> pre<01:20:33.280> same 01:20:36.310 --> 01:20:36.320 align:start position:0% 01:20:36.320 --> 01:20:39.870 align:start position:0% precom<01:20:37.320> so<01:20:37.639> for<01:20:37.880> the<01:20:38.120> payment<01:20:38.800> we 01:20:39.870 --> 01:20:39.880 align:start position:0% precom so for the payment we 01:20:39.880 --> 01:20:43.430 align:start position:0% precom so for the payment we have<01:20:40.880> we<01:20:41.040> have<01:20:41.280> lifted<01:20:41.920> up<01:20:42.120> for<01:20:42.360> the<01:20:42.560> market 01:20:43.430 --> 01:20:43.440 align:start position:0% have we have lifted up for the market 01:20:43.440 --> 01:20:46.510 align:start position:0% have we have lifted up for the market and<01:20:43.719> because<01:20:44.719> we<01:20:45.080> decided<01:20:45.639> that<01:20:45.880> the<01:20:46.080> priority 01:20:46.510 --> 01:20:46.520 align:start position:0% and because we decided that the priority 01:20:46.520 --> 01:20:49.590 align:start position:0% and because we decided that the priority fee<01:20:46.800> will<01:20:46.960> be<01:20:47.520> used<01:20:48.520> then<01:20:49.000> basically<01:20:49.440> the 01:20:49.590 --> 01:20:49.600 align:start position:0% fee will be used then basically the 01:20:49.600 --> 01:20:52.830 align:start position:0% fee will be used then basically the preconference<01:20:50.320> will<01:20:50.560> just<01:20:51.280> not<01:20:51.639> prec<01:20:51.920> confirm 01:20:52.830 --> 01:20:52.840 align:start position:0% preconference will just not prec confirm 01:20:52.840 --> 01:20:55.870 align:start position:0% preconference will just not prec confirm transactions<01:20:53.639> that<01:20:53.760> are<01:20:53.920> not<01:20:54.159> profitable 01:20:55.870 --> 01:20:55.880 align:start position:0% transactions that are not profitable 01:20:55.880 --> 01:21:00.110 align:start position:0% transactions that are not profitable um<01:20:56.639> so<01:20:57.000> any<01:20:57.280> transactions<01:20:58.040> that<01:20:58.560> are<01:20:59.560> do<01:20:59.800> not 01:21:00.110 --> 01:21:00.120 align:start position:0% um so any transactions that are do not 01:21:00.120 --> 01:21:02.390 align:start position:0% um so any transactions that are do not have<01:21:00.320> a<01:21:00.639> high<01:21:00.920> priority<01:21:01.360> fee<01:21:01.760> that<01:21:01.880> is<01:21:02.080> paying 01:21:02.390 --> 01:21:02.400 align:start position:0% have a high priority fee that is paying 01:21:02.400 --> 01:21:11.450 align:start position:0% have a high priority fee that is paying the 01:21:11.450 --> 01:21:11.460 align:start position:0% 01:21:11.460 --> 01:21:23.550 align:start position:0% [Music] 01:21:23.550 --> 01:21:23.560 align:start position:0% 01:21:23.560 --> 01:21:26.110 align:start position:0% pre-conferences<01:21:24.639> blob<01:21:25.280> which<01:21:25.400> is<01:21:25.639> basically 01:21:26.110 --> 01:21:26.120 align:start position:0% pre-conferences blob which is basically 01:21:26.120 --> 01:21:29.229 align:start position:0% pre-conferences blob which is basically now<01:21:26.360> free<01:21:27.040> one<01:21:27.320> way<01:21:27.800> to<01:21:28.040> to<01:21:28.199> get<01:21:28.320> a<01:21:28.480> blob<01:21:28.880> as<01:21:29.000> of 01:21:29.229 --> 01:21:29.239 align:start position:0% now free one way to to get a blob as of 01:21:29.239 --> 01:21:33.110 align:start position:0% now free one way to to get a blob as of now<01:21:30.239> um<01:21:30.920> the<01:21:31.159> the<01:21:31.360> the<01:21:31.440> more<01:21:31.760> I<01:21:31.920> can<01:21:32.120> make<01:21:32.320> money 01:21:33.110 --> 01:21:33.120 align:start position:0% now um the the the more I can make money 01:21:33.120 --> 01:21:35.870 align:start position:0% now um the the the more I can make money so<01:21:33.400> we<01:21:33.560> lift<01:21:33.920> the<01:21:34.120> pricing<01:21:34.840> to<01:21:35.040> the<01:21:35.199> market<01:21:35.520> to 01:21:35.870 --> 01:21:35.880 align:start position:0% so we lift the pricing to the market to 01:21:35.880 --> 01:21:38.590 align:start position:0% so we lift the pricing to the market to decide<01:21:36.880> um<01:21:37.159> there<01:21:37.280> are<01:21:37.520> some<01:21:37.800> research<01:21:38.480> that 01:21:38.590 --> 01:21:38.600 align:start position:0% decide um there are some research that 01:21:38.600 --> 01:21:43.110 align:start position:0% decide um there are some research that is<01:21:38.800> going<01:21:39.080> on<01:21:39.440> in<01:21:39.600> the<01:21:39.800> space<01:21:40.320> by<01:21:41.280> Connor<01:21:42.280> um 01:21:43.110 --> 01:21:43.120 align:start position:0% is going on in the space by Connor um 01:21:43.120 --> 01:21:45.910 align:start position:0% is going on in the space by Connor um and<01:21:43.320> Lynn<01:21:43.880> from<01:21:44.199> nethermind<01:21:45.199> and<01:21:45.440> there's 01:21:45.910 --> 01:21:45.920 align:start position:0% and Lynn from nethermind and there's 01:21:45.920 --> 01:21:48.390 align:start position:0% and Lynn from nethermind and there's another<01:21:46.320> guy<01:21:46.520> I<01:21:46.639> think<01:21:46.880> called<01:21:47.120> Finn<01:21:47.920> Finn 01:21:48.390 --> 01:21:48.400 align:start position:0% another guy I think called Finn Finn 01:21:48.400 --> 01:21:50.229 align:start position:0% another guy I think called Finn Finn yeah<01:21:49.000> uh<01:21:49.120> I<01:21:49.199> don't<01:21:49.320> know<01:21:49.520> their<01:21:49.679> full<01:21:49.880> name<01:21:50.080> so 01:21:50.229 --> 01:21:50.239 align:start position:0% yeah uh I don't know their full name so 01:21:50.239 --> 01:21:52.709 align:start position:0% yeah uh I don't know their full name so I<01:21:50.400> apologize<01:21:50.880> for<01:21:51.120> that<01:21:51.639> about<01:21:51.920> the<01:21:52.080> economics 01:21:52.709 --> 01:21:52.719 align:start position:0% I apologize for that about the economics 01:21:52.719 --> 01:21:55.229 align:start position:0% I apologize for that about the economics of<01:21:52.920> pre-confirmation<01:21:53.440> and<01:21:54.320> the<01:21:54.600> pricing<01:21:55.000> for 01:21:55.229 --> 01:21:55.239 align:start position:0% of pre-confirmation and the pricing for 01:21:55.239 --> 01:21:59.669 align:start position:0% of pre-confirmation and the pricing for pcoms<01:21:56.120> ETC<01:21:57.120> and<01:21:57.639> this<01:21:57.880> work<01:21:58.760> um<01:21:59.159> there<01:21:59.280> is<01:21:59.560> a 01:21:59.669 --> 01:21:59.679 align:start position:0% pcoms ETC and this work um there is a 01:21:59.679 --> 01:22:02.709 align:start position:0% pcoms ETC and this work um there is a lot<01:21:59.840> of<01:22:00.040> talks<01:22:00.440> that<01:22:00.760> Connor<01:22:01.320> Finn<01:22:02.159> and<01:22:02.320> Lynn 01:22:02.709 --> 01:22:02.719 align:start position:0% lot of talks that Connor Finn and Lynn 01:22:02.719 --> 01:22:04.510 align:start position:0% lot of talks that Connor Finn and Lynn has<01:22:02.880> been<01:22:03.080> talking<01:22:03.440> about<01:22:03.719> pre-confirmation 01:22:04.510 --> 01:22:04.520 align:start position:0% has been talking about pre-confirmation 01:22:04.520 --> 01:22:06.790 align:start position:0% has been talking about pre-confirmation um<01:22:05.520> I<01:22:05.679> advise<01:22:06.000> you<01:22:06.080> to<01:22:06.239> go<01:22:06.400> check<01:22:06.639> the 01:22:06.790 --> 01:22:06.800 align:start position:0% um I advise you to go check the 01:22:06.800 --> 01:22:08.950 align:start position:0% um I advise you to go check the recordings<01:22:07.320> for<01:22:07.560> these<01:22:07.760> Talks<01:22:08.520> by<01:22:08.719> these 01:22:08.950 --> 01:22:08.960 align:start position:0% recordings for these Talks by these 01:22:08.960 --> 01:22:11.629 align:start position:0% recordings for these Talks by these people<01:22:09.600> they're<01:22:09.800> BL<01:22:10.440> they're<01:22:11.000> they<01:22:11.159> touch 01:22:11.629 --> 01:22:11.639 align:start position:0% people they're BL they're they touch 01:22:11.639 --> 01:22:15.149 align:start position:0% people they're BL they're they touch exactly<01:22:12.040> on<01:22:12.280> what<01:22:12.400> you<01:22:12.560> asked<01:22:12.840> about<01:22:13.560> thank 01:22:15.149 --> 01:22:15.159 align:start position:0% exactly on what you asked about thank 01:22:15.159 --> 01:22:20.030 align:start position:0% exactly on what you asked about thank you<01:22:16.159> how<01:22:16.440> do<01:22:16.560> you 01:22:20.030 --> 01:22:20.040 align:start position:0% 01:22:20.040 --> 01:22:23.510 align:start position:0% think 01:22:23.510 --> 01:22:23.520 align:start position:0% 01:22:23.520 --> 01:22:26.550 align:start position:0% of<01:22:24.560> do<01:22:24.719> you 01:22:26.550 --> 01:22:26.560 align:start position:0% of do you 01:22:26.560 --> 01:22:30.790 align:start position:0% of do you think<01:22:27.560> it<01:22:28.080> improves<01:22:28.600> it<01:22:29.000> uh<01:22:29.920> is<01:22:30.040> that<01:22:30.239> a<01:22:30.520> reason 01:22:30.790 --> 01:22:30.800 align:start position:0% think it improves it uh is that a reason 01:22:30.800 --> 01:22:32.229 align:start position:0% think it improves it uh is that a reason for 01:22:32.229 --> 01:22:32.239 align:start position:0% for 01:22:32.239 --> 01:22:36.510 align:start position:0% for concern<01:22:33.239> um<01:22:33.760> personally<01:22:34.639> um<01:22:35.360> like<01:22:35.639> meev<01:22:36.320> or 01:22:36.510 --> 01:22:36.520 align:start position:0% concern um personally um like meev or 01:22:36.520 --> 01:22:40.709 align:start position:0% concern um personally um like meev or not<01:22:36.920> me<01:22:37.920> um<01:22:38.440> the<01:22:38.760> the<01:22:38.960> protocol<01:22:39.560> works<01:22:40.120> with 01:22:40.709 --> 01:22:40.719 align:start position:0% not me um the the protocol works with 01:22:40.719 --> 01:22:43.510 align:start position:0% not me um the the protocol works with local<01:22:41.120> built<01:22:41.480> blocks<01:22:42.360> and<01:22:42.600> also<01:22:42.920> works<01:22:43.360> with 01:22:43.510 --> 01:22:43.520 align:start position:0% local built blocks and also works with 01:22:43.520 --> 01:22:47.149 align:start position:0% local built blocks and also works with forced<01:22:43.960> inclusion<01:22:44.760> through<01:22:45.520> PBS<01:22:46.159> pipeline 01:22:47.149 --> 01:22:47.159 align:start position:0% forced inclusion through PBS pipeline 01:22:47.159 --> 01:22:50.310 align:start position:0% forced inclusion through PBS pipeline the<01:22:47.280> only<01:22:47.679> problem<01:22:48.080> here<01:22:48.320> that<01:22:48.520> I<01:22:48.679> see<01:22:49.040> is<01:22:49.360> that 01:22:50.310 --> 01:22:50.320 align:start position:0% the only problem here that I see is that 01:22:50.320 --> 01:22:53.629 align:start position:0% the only problem here that I see is that if<01:22:51.199> relays<01:22:52.199> and<01:22:52.400> Builders<01:22:52.960> decided<01:22:53.480> that 01:22:53.629 --> 01:22:53.639 align:start position:0% if relays and Builders decided that 01:22:53.639 --> 01:22:54.990 align:start position:0% if relays and Builders decided that they're<01:22:53.880> not<01:22:54.159> going<01:22:54.280> to 01:22:54.990 --> 01:22:55.000 align:start position:0% they're not going to 01:22:55.000 --> 01:22:58.189 align:start position:0% they're not going to adopt<01:22:55.960> the<01:22:56.199> constraint<01:22:56.840> API<01:22:57.520> that<01:22:57.719> we<01:22:57.880> talked 01:22:58.189 --> 01:22:58.199 align:start position:0% adopt the constraint API that we talked 01:22:58.199 --> 01:23:01.030 align:start position:0% adopt the constraint API that we talked about<01:22:58.960> because<01:22:59.400> it<01:22:59.639> basically<01:23:00.159> reduces<01:23:00.800> their 01:23:01.030 --> 01:23:01.040 align:start position:0% about because it basically reduces their 01:23:01.040 --> 01:23:03.189 align:start position:0% about because it basically reduces their income<01:23:01.560> because<01:23:01.880> pre-confirmation<01:23:02.360> are<01:23:02.920> not 01:23:03.189 --> 01:23:03.199 align:start position:0% income because pre-confirmation are not 01:23:03.199 --> 01:23:05.070 align:start position:0% income because pre-confirmation are not profitable<01:23:03.760> enough<01:23:04.159> compared<01:23:04.520> to<01:23:04.719> what<01:23:04.880> they 01:23:05.070 --> 01:23:05.080 align:start position:0% profitable enough compared to what they 01:23:05.080 --> 01:23:07.590 align:start position:0% profitable enough compared to what they can<01:23:05.679> include<01:23:06.280> other<01:23:06.520> than<01:23:06.760> these 01:23:07.590 --> 01:23:07.600 align:start position:0% can include other than these 01:23:07.600 --> 01:23:09.830 align:start position:0% can include other than these transactions<01:23:08.600> um<01:23:08.880> then<01:23:09.080> we<01:23:09.239> would<01:23:09.480> have<01:23:09.639> a 01:23:09.830 --> 01:23:09.840 align:start position:0% transactions um then we would have a 01:23:09.840 --> 01:23:13.229 align:start position:0% transactions um then we would have a problem<01:23:10.239> but<01:23:10.400> as<01:23:10.560> of<01:23:10.760> now<01:23:11.199> and<01:23:11.440> as<01:23:11.719> we<01:23:12.719> uh<01:23:12.880> as<01:23:13.040> we 01:23:13.229 --> 01:23:13.239 align:start position:0% problem but as of now and as we uh as we 01:23:13.239 --> 01:23:16.510 align:start position:0% problem but as of now and as we uh as we heard<01:23:13.679> from<01:23:13.920> our<01:23:14.440> partners<01:23:15.440> is<01:23:15.760> that<01:23:16.280> there's 01:23:16.510 --> 01:23:16.520 align:start position:0% heard from our partners is that there's 01:23:16.520 --> 01:23:18.270 align:start position:0% heard from our partners is that there's a<01:23:16.639> lot<01:23:16.800> of<01:23:17.000> talk<01:23:17.400> and<01:23:17.560> the<01:23:17.639> Rel<01:23:17.840> layers<01:23:18.120> and 01:23:18.270 --> 01:23:18.280 align:start position:0% a lot of talk and the Rel layers and 01:23:18.280 --> 01:23:20.030 align:start position:0% a lot of talk and the Rel layers and Builders<01:23:18.719> are<01:23:18.960> agreeing<01:23:19.480> to<01:23:19.679> add<01:23:19.880> the 01:23:20.030 --> 01:23:20.040 align:start position:0% Builders are agreeing to add the 01:23:20.040 --> 01:23:23.790 align:start position:0% Builders are agreeing to add the constraint<01:23:20.880> API<01:23:21.880> um<01:23:22.120> to<01:23:22.360> their<01:23:23.080> pipe<01:23:23.400> to<01:23:23.520> the 01:23:23.790 --> 01:23:23.800 align:start position:0% constraint API um to their pipe to the 01:23:23.800 --> 01:23:26.510 align:start position:0% constraint API um to their pipe to the epbs<01:23:24.520> pipeline<01:23:25.080> so<01:23:25.679> they<01:23:25.840> would<01:23:26.120> be 01:23:26.510 --> 01:23:26.520 align:start position:0% epbs pipeline so they would be 01:23:26.520 --> 01:23:28.629 align:start position:0% epbs pipeline so they would be potentially<01:23:27.520> uh<01:23:28.000> including 01:23:28.629 --> 01:23:28.639 align:start position:0% potentially uh including 01:23:28.639 --> 01:23:29.910 align:start position:0% potentially uh including pre-confirmation 01:23:29.910 --> 01:23:29.920 align:start position:0% pre-confirmation 01:23:29.920 --> 01:23:33.110 align:start position:0% pre-confirmation to<01:23:30.920> add<01:23:31.120> to<01:23:31.360> this<01:23:31.600> we<01:23:32.159> I<01:23:32.280> think<01:23:32.520> we<01:23:32.719> also<01:23:32.960> have 01:23:33.110 --> 01:23:33.120 align:start position:0% to add to this we I think we also have 01:23:33.120 --> 01:23:36.470 align:start position:0% to add to this we I think we also have plans<01:23:33.440> for<01:23:33.639> L2<01:23:34.239> meev<01:23:34.920> extraction<01:23:35.880> so<01:23:36.080> when 01:23:36.470 --> 01:23:36.480 align:start position:0% plans for L2 meev extraction so when 01:23:36.480 --> 01:23:37.950 align:start position:0% plans for L2 meev extraction so when that<01:23:36.600> is<01:23:36.760> added<01:23:37.040> to<01:23:37.239> this<01:23:37.480> I<01:23:37.600> think<01:23:37.840> the 01:23:37.950 --> 01:23:37.960 align:start position:0% that is added to this I think the 01:23:37.960 --> 01:23:41.270 align:start position:0% that is added to this I think the dynamic<01:23:38.360> changes<01:23:38.760> a<01:23:38.920> bit<01:23:39.840> Yeah<01:23:40.120> so<01:23:40.520> basically 01:23:41.270 --> 01:23:41.280 align:start position:0% dynamic changes a bit Yeah so basically 01:23:41.280 --> 01:23:43.830 align:start position:0% dynamic changes a bit Yeah so basically since<01:23:41.600> we<01:23:41.800> have<01:23:42.080> like<01:23:42.400> currently<01:23:42.920> 3C<01:23:43.639> and 01:23:43.830 --> 01:23:43.840 align:start position:0% since we have like currently 3C and 01:23:43.840 --> 01:23:46.629 align:start position:0% since we have like currently 3C and potentially<01:23:44.360> 1<01:23:44.639> second<01:23:45.560> uh<01:23:45.840> uh<01:23:45.960> block<01:23:46.320> times 01:23:46.629 --> 01:23:46.639 align:start position:0% potentially 1 second uh uh block times 01:23:46.639 --> 01:23:50.510 align:start position:0% potentially 1 second uh uh block times for<01:23:46.880> the<01:23:47.000> L2<01:23:48.000> in<01:23:48.199> this<01:23:48.639> one<01:23:48.960> second<01:23:49.560> you<01:23:49.760> can 01:23:50.510 --> 01:23:50.520 align:start position:0% for the L2 in this one second you can 01:23:50.520 --> 01:23:54.110 align:start position:0% for the L2 in this one second you can the<01:23:50.719> the<01:23:50.880> pre-<01:23:51.120> comfor<01:23:51.560> still<01:23:52.120> at<01:23:53.040> at<01:23:53.440> well<01:23:53.880> can 01:23:54.110 --> 01:23:54.120 align:start position:0% the the pre- comfor still at at well can 01:23:54.120 --> 01:23:56.510 align:start position:0% the the pre- comfor still at at well can re<01:23:54.440> order<01:23:54.719> these<01:23:54.920> transaction<01:23:55.880> but<01:23:56.120> we<01:23:56.239> would 01:23:56.510 --> 01:23:56.520 align:start position:0% re order these transaction but we would 01:23:56.520 --> 01:23:59.189 align:start position:0% re order these transaction but we would not<01:23:56.920> expect<01:23:57.400> every<01:23:57.719> prec<01:23:58.040> Comer<01:23:58.800> which<01:23:58.960> is 01:23:59.189 --> 01:23:59.199 align:start position:0% not expect every prec Comer which is 01:23:59.199 --> 01:24:01.590 align:start position:0% not expect every prec Comer which is basically<01:23:59.880> just<01:24:00.080> an<01:24:00.239> L1<01:24:00.679> validator<01:24:01.239> to<01:24:01.400> have 01:24:01.590 --> 01:24:01.600 align:start position:0% basically just an L1 validator to have 01:24:01.600 --> 01:24:05.430 align:start position:0% basically just an L1 validator to have thetic<01:24:02.520> the<01:24:02.679> sophistication<01:24:03.800> needed<01:24:04.800> uh<01:24:05.320> in 01:24:05.430 --> 01:24:05.440 align:start position:0% thetic the sophistication needed uh in 01:24:05.440 --> 01:24:07.709 align:start position:0% thetic the sophistication needed uh in the<01:24:05.639> software<01:24:06.280> and<01:24:06.440> in<01:24:06.600> the<01:24:06.719> hardware<01:24:07.400> to<01:24:07.560> be 01:24:07.709 --> 01:24:07.719 align:start position:0% the software and in the hardware to be 01:24:07.719 --> 01:24:09.950 align:start position:0% the software and in the hardware to be able<01:24:07.920> to<01:24:08.120> support<01:24:08.639> such<01:24:08.880> ordering<01:24:09.520> in<01:24:09.719> one 01:24:09.950 --> 01:24:09.960 align:start position:0% able to support such ordering in one 01:24:09.960 --> 01:24:11.870 align:start position:0% able to support such ordering in one second<01:24:10.880> and<01:24:11.120> I<01:24:11.199> think<01:24:11.400> what's<01:24:11.560> going<01:24:11.679> to 01:24:11.870 --> 01:24:11.880 align:start position:0% second and I think what's going to 01:24:11.880 --> 01:24:14.310 align:start position:0% second and I think what's going to happen<01:24:12.159> is<01:24:12.400> that<01:24:12.600> there<01:24:12.719> will<01:24:12.920> be<01:24:13.120> an<01:24:13.480> a<01:24:13.679> PBS 01:24:14.310 --> 01:24:14.320 align:start position:0% happen is that there will be an a PBS 01:24:14.320 --> 01:24:17.270 align:start position:0% happen is that there will be an a PBS pipeline<01:24:14.800> for<01:24:15.080> L2<01:24:15.560> blocks<01:24:16.480> if<01:24:16.760> this<01:24:17.159> uh 01:24:17.270 --> 01:24:17.280 align:start position:0% pipeline for L2 blocks if this uh 01:24:17.280 --> 01:24:20.110 align:start position:0% pipeline for L2 blocks if this uh protocol<01:24:17.719> gets<01:24:18.159> adoption<01:24:19.159> that<01:24:19.560> will<01:24:19.920> that 01:24:20.110 --> 01:24:20.120 align:start position:0% protocol gets adoption that will that 01:24:20.120 --> 01:24:23.110 align:start position:0% protocol gets adoption that will that tries<01:24:20.400> to<01:24:20.639> extract<01:24:21.159> M<01:24:21.800> from<01:24:22.120> these<01:24:22.280> L2<01:24:22.760> blocks 01:24:23.110 --> 01:24:23.120 align:start position:0% tries to extract M from these L2 blocks 01:24:23.120 --> 01:24:27.310 align:start position:0% tries to extract M from these L2 blocks in<01:24:23.280> this<01:24:23.480> 1<01:24:23.719> second<01:24:24.000> slot 01:24:27.310 --> 01:24:27.320 align:start position:0% 01:24:27.320 --> 01:24:29.910 align:start position:0% sorry<01:24:27.800> last<01:24:28.080> question<01:24:28.920> uh<01:24:29.320> what<01:24:29.480> are<01:24:29.679> the 01:24:29.910 --> 01:24:29.920 align:start position:0% sorry last question uh what are the 01:24:29.920 --> 01:24:33.030 align:start position:0% sorry last question uh what are the latency<01:24:30.840> figures<01:24:31.760> that<01:24:32.000> you<01:24:32.239> guys<01:24:32.560> have 01:24:33.030 --> 01:24:33.040 align:start position:0% latency figures that you guys have 01:24:33.040 --> 01:24:35.950 align:start position:0% latency figures that you guys have regarding<01:24:33.560> like<01:24:33.760> the<01:24:34.199> block<01:24:35.199> transmission 01:24:35.950 --> 01:24:35.960 align:start position:0% regarding like the block transmission 01:24:35.960 --> 01:24:37.950 align:start position:0% regarding like the block transmission from<01:24:36.199> the<01:24:36.400> preconference<01:24:37.120> we<01:24:37.239> don't<01:24:37.520> we<01:24:37.639> don't 01:24:37.950 --> 01:24:37.960 align:start position:0% from the preconference we don't we don't 01:24:37.960 --> 01:24:41.189 align:start position:0% from the preconference we don't we don't have<01:24:38.239> that<01:24:38.600> yet<01:24:38.960> because<01:24:39.679> as<01:24:39.800> of<01:24:40.040> now<01:24:40.560> we<01:24:40.800> have 01:24:41.189 --> 01:24:41.199 align:start position:0% have that yet because as of now we have 01:24:41.199 --> 01:24:44.430 align:start position:0% have that yet because as of now we have only<01:24:41.560> Dev<01:24:41.920> Nets<01:24:42.760> and<01:24:42.960> Dev<01:24:43.239> Nets<01:24:43.480> are<01:24:43.760> basically 01:24:44.430 --> 01:24:44.440 align:start position:0% only Dev Nets and Dev Nets are basically 01:24:44.440 --> 01:24:49.669 align:start position:0% only Dev Nets and Dev Nets are basically just<01:24:45.040> U<01:24:45.880> curtosis<01:24:46.880> uh<01:24:47.280> setup<01:24:48.280> uh<01:24:48.679> instances 01:24:49.669 --> 01:24:49.679 align:start position:0% just U curtosis uh setup uh instances 01:24:49.679 --> 01:24:52.070 align:start position:0% just U curtosis uh setup uh instances that<01:24:49.800> are<01:24:49.960> running<01:24:50.400> on<01:24:50.600> local<01:24:51.000> machines<01:24:52.000> I 01:24:52.070 --> 01:24:52.080 align:start position:0% that are running on local machines I 01:24:52.080 --> 01:24:56.470 align:start position:0% that are running on local machines I mean<01:24:52.280> we<01:24:52.480> have<01:24:52.679> Helder<01:24:53.400> but<01:24:54.800> deployed<01:24:55.760> a 01:24:56.470 --> 01:24:56.480 align:start position:0% mean we have Helder but deployed a 01:24:56.480 --> 01:24:59.149 align:start position:0% mean we have Helder but deployed a hybrid<01:24:56.960> solution<01:24:57.560> between<01:24:58.040> Gateway<01:24:58.480> precom 01:24:59.149 --> 01:24:59.159 align:start position:0% hybrid solution between Gateway precom 01:24:59.159 --> 01:25:02.350 align:start position:0% hybrid solution between Gateway precom and<01:24:59.360> our<01:24:59.679> solution<01:25:00.199> so<01:25:00.400> our<01:25:00.719> smart<01:25:01.360> contracts 01:25:02.350 --> 01:25:02.360 align:start position:0% and our solution so our smart contracts 01:25:02.360 --> 01:25:06.550 align:start position:0% and our solution so our smart contracts but<01:25:02.600> Gateway<01:25:03.119> software<01:25:04.239> basically<01:25:05.239> and<01:25:05.840> um<01:25:06.440> as 01:25:06.550 --> 01:25:06.560 align:start position:0% but Gateway software basically and um as 01:25:06.560 --> 01:25:08.990 align:start position:0% but Gateway software basically and um as of<01:25:06.800> now<01:25:07.159> that<01:25:07.320> that's<01:25:07.600> what<01:25:08.000> no<01:25:08.320> that's<01:25:08.840> that's 01:25:08.990 --> 01:25:09.000 align:start position:0% of now that that's what no that's that's 01:25:09.000 --> 01:25:11.470 align:start position:0% of now that that's what no that's that's deployed<01:25:09.440> in<01:25:09.560> Hilder<01:25:10.159> yeah<01:25:10.600> okay<01:25:10.880> yeah<01:25:11.239> so 01:25:11.470 --> 01:25:11.480 align:start position:0% deployed in Hilder yeah okay yeah so 01:25:11.480 --> 01:25:13.709 align:start position:0% deployed in Hilder yeah okay yeah so that's<01:25:11.679> what<01:25:11.840> deployed<01:25:12.239> in<01:25:12.400> Hilder<01:25:12.840> right<01:25:13.000> now 01:25:13.709 --> 01:25:13.719 align:start position:0% that's what deployed in Hilder right now 01:25:13.719 --> 01:25:16.030 align:start position:0% that's what deployed in Hilder right now so<01:25:14.320> it's<01:25:14.560> not<01:25:14.800> the<01:25:14.960> same<01:25:15.239> and<01:25:15.400> we<01:25:15.520> don't<01:25:15.760> have 01:25:16.030 --> 01:25:16.040 align:start position:0% so it's not the same and we don't have 01:25:16.040 --> 01:25:18.870 align:start position:0% so it's not the same and we don't have that<01:25:16.520> distribution<01:25:17.520> of<01:25:17.960> of<01:25:18.119> site<01:25:18.520> cars 01:25:18.870 --> 01:25:18.880 align:start position:0% that distribution of of site cars 01:25:18.880 --> 01:25:21.669 align:start position:0% that distribution of of site cars running<01:25:19.800> so<01:25:20.080> we<01:25:20.199> can<01:25:20.480> calculate<01:25:21.119> this<01:25:21.480> this 01:25:21.669 --> 01:25:21.679 align:start position:0% running so we can calculate this this 01:25:21.679 --> 01:25:24.310 align:start position:0% running so we can calculate this this latency<01:25:22.679> we<01:25:22.800> can<01:25:23.000> do<01:25:23.199> some<01:25:23.440> simulations<01:25:24.040> po 01:25:24.310 --> 01:25:24.320 align:start position:0% latency we can do some simulations po 01:25:24.320 --> 01:25:27.229 align:start position:0% latency we can do some simulations po potentially<01:25:24.960> but<01:25:25.520> yeah<01:25:25.800> reality<01:25:26.320> always<01:25:27.040> is 01:25:27.229 --> 01:25:27.239 align:start position:0% potentially but yeah reality always is 01:25:27.239 --> 01:25:34.950 align:start position:0% potentially but yeah reality always is is<01:25:27.440> different<01:25:27.800> than 01:25:34.950 --> 01:25:34.960 align:start position:0% 01:25:34.960 --> 01:25:39.510 align:start position:0% simulations<01:25:35.960> do<01:25:36.119> we<01:25:36.280> have<01:25:36.440> more 01:25:39.510 --> 01:25:39.520 align:start position:0% 01:25:39.520 --> 01:25:41.870 align:start position:0% questions<01:25:40.520> think 01:25:41.870 --> 01:25:41.880 align:start position:0% questions think 01:25:41.880 --> 01:25:44.629 align:start position:0% questions think not<01:25:42.880> all<01:25:43.040> right<01:25:43.679> that's<01:25:44.080> thank<01:25:44.199> you<01:25:44.320> everyone 01:25:44.629 --> 01:25:44.639 align:start position:0% not all right that's thank you everyone 01:25:44.639 --> 01:25:49.280 align:start position:0% not all right that's thank you everyone for<01:25:44.880> having<01:25:45.600> for<01:25:45.880> for<01:25:46.119> for<01:25:46.280> attending