WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:10.190 align:start position:0% [Music] 00:00:10.190 --> 00:00:10.200 align:start position:0% [Music] 00:00:10.200 --> 00:00:13.870 align:start position:0% [Music] Carlos<00:00:10.480> Matana<00:00:11.080> work<00:00:11.360> at<00:00:12.200> polygon<00:00:12.799> and<00:00:12.960> today 00:00:13.870 --> 00:00:13.880 align:start position:0% Carlos Matana work at polygon and today 00:00:13.880 --> 00:00:15.829 align:start position:0% Carlos Matana work at polygon and today I<00:00:14.000> will<00:00:14.160> be<00:00:14.440> talking<00:00:14.799> about<00:00:15.040> the<00:00:15.240> top<00:00:15.639> code 00:00:15.829 --> 00:00:15.839 align:start position:0% I will be talking about the top code 00:00:15.839 --> 00:00:19.390 align:start position:0% I will be talking about the top code offenders<00:00:16.480> in<00:00:16.720> the<00:00:17.480> zvm<00:00:18.480> in<00:00:18.600> order<00:00:18.840> to<00:00:19.000> explain 00:00:19.390 --> 00:00:19.400 align:start position:0% offenders in the zvm in order to explain 00:00:19.400 --> 00:00:22.029 align:start position:0% offenders in the zvm in order to explain that<00:00:20.080> basically<00:00:20.519> I<00:00:20.640> will<00:00:20.840> do<00:00:21.560> at<00:00:21.680> the<00:00:21.840> very 00:00:22.029 --> 00:00:22.039 align:start position:0% that basically I will do at the very 00:00:22.039 --> 00:00:24.509 align:start position:0% that basically I will do at the very beginning<00:00:22.439> some<00:00:22.720> introductions<00:00:23.560> about<00:00:23.880> the 00:00:24.509 --> 00:00:24.519 align:start position:0% beginning some introductions about the 00:00:24.519 --> 00:00:26.750 align:start position:0% beginning some introductions about the what<00:00:24.640> are<00:00:24.800> the<00:00:25.000> ZK<00:00:25.400> counters<00:00:26.320> what<00:00:26.439> are<00:00:26.599> the 00:00:26.750 --> 00:00:26.760 align:start position:0% what are the ZK counters what are the 00:00:26.760 --> 00:00:29.669 align:start position:0% what are the ZK counters what are the types<00:00:27.000> of<00:00:27.119> the<00:00:27.240> ZK<00:00:27.560> counters<00:00:28.240> available<00:00:29.240> and 00:00:29.669 --> 00:00:29.679 align:start position:0% types of the ZK counters available and 00:00:29.679 --> 00:00:31.950 align:start position:0% types of the ZK counters available and how<00:00:29.800> many<00:00:30.119> Z<00:00:30.439> counters<00:00:30.920> do<00:00:31.039> we<00:00:31.199> have<00:00:31.439> available 00:00:31.950 --> 00:00:31.960 align:start position:0% how many Z counters do we have available 00:00:31.960 --> 00:00:33.830 align:start position:0% how many Z counters do we have available on<00:00:32.079> the 00:00:33.830 --> 00:00:33.840 align:start position:0% on the 00:00:33.840 --> 00:00:36.430 align:start position:0% on the zbm<00:00:34.840> the<00:00:35.239> second<00:00:35.559> point<00:00:35.840> will<00:00:36.000> be<00:00:36.200> in<00:00:36.320> the 00:00:36.430 --> 00:00:36.440 align:start position:0% zbm the second point will be in the 00:00:36.440 --> 00:00:38.430 align:start position:0% zbm the second point will be in the analysis<00:00:37.000> of<00:00:37.200> the<00:00:37.399> offenders<00:00:38.000> you<00:00:38.120> will<00:00:38.239> see 00:00:38.430 --> 00:00:38.440 align:start position:0% analysis of the offenders you will see 00:00:38.440 --> 00:00:39.590 align:start position:0% analysis of the offenders you will see that<00:00:38.559> there<00:00:38.680> are<00:00:38.840> some<00:00:39.000> straightforward 00:00:39.590 --> 00:00:39.600 align:start position:0% that there are some straightforward 00:00:39.600 --> 00:00:41.790 align:start position:0% that there are some straightforward offenders<00:00:40.039> on<00:00:40.160> the<00:00:40.280> zbm<00:00:41.200> so<00:00:41.399> there<00:00:41.520> is<00:00:41.640> no 00:00:41.790 --> 00:00:41.800 align:start position:0% offenders on the zbm so there is no 00:00:41.800 --> 00:00:43.310 align:start position:0% offenders on the zbm so there is no correlation<00:00:42.239> between<00:00:42.480> the<00:00:42.640> gas<00:00:42.800> consumed<00:00:43.200> on 00:00:43.310 --> 00:00:43.320 align:start position:0% correlation between the gas consumed on 00:00:43.320 --> 00:00:45.430 align:start position:0% correlation between the gas consumed on ethereum<00:00:43.879> and<00:00:44.000> the<00:00:44.120> Z<00:00:44.480> counters<00:00:44.920> consumed<00:00:45.360> on 00:00:45.430 --> 00:00:45.440 align:start position:0% ethereum and the Z counters consumed on 00:00:45.440 --> 00:00:46.069 align:start position:0% ethereum and the Z counters consumed on the 00:00:46.069 --> 00:00:46.079 align:start position:0% the 00:00:46.079 --> 00:00:49.510 align:start position:0% the zvm<00:00:47.079> but<00:00:47.520> I<00:00:47.600> will<00:00:47.960> go<00:00:48.280> more<00:00:48.600> into<00:00:48.879> the<00:00:49.039> details 00:00:49.510 --> 00:00:49.520 align:start position:0% zvm but I will go more into the details 00:00:49.520 --> 00:00:51.990 align:start position:0% zvm but I will go more into the details there<00:00:49.640> are<00:00:50.000> some<00:00:50.719> up<00:00:50.960> codes<00:00:51.199> that<00:00:51.320> are<00:00:51.440> quite 00:00:51.990 --> 00:00:52.000 align:start position:0% there are some up codes that are quite 00:00:52.000 --> 00:00:55.590 align:start position:0% there are some up codes that are quite straightforward<00:00:53.000> but<00:00:53.600> uh<00:00:53.719> when<00:00:54.120> we<00:00:54.600> analyze 00:00:55.590 --> 00:00:55.600 align:start position:0% straightforward but uh when we analyze 00:00:55.600 --> 00:00:57.229 align:start position:0% straightforward but uh when we analyze uh<00:00:55.719> in<00:00:55.879> this<00:00:56.039> case<00:00:56.199> I<00:00:56.320> will<00:00:56.480> analyze<00:00:56.840> a<00:00:56.960> Unis 00:00:57.229 --> 00:00:57.239 align:start position:0% uh in this case I will analyze a Unis 00:00:57.239 --> 00:01:00.750 align:start position:0% uh in this case I will analyze a Unis swap<00:00:57.480> swap<00:00:58.320> uh<00:00:58.480> we<00:00:58.600> will<00:00:58.800> see<00:00:59.399> which<00:00:59.559> is<00:00:59.680> the 00:01:00.750 --> 00:01:00.760 align:start position:0% swap swap uh we will see which is the 00:01:00.760 --> 00:01:05.429 align:start position:0% swap swap uh we will see which is the worst<00:01:01.760> the<00:01:02.000> the<00:01:02.199> worst<00:01:03.199> of<00:01:03.680> codes<00:01:04.680> that<00:01:05.159> uh 00:01:05.429 --> 00:01:05.439 align:start position:0% worst the the worst of codes that uh 00:01:05.439 --> 00:01:07.350 align:start position:0% worst the the worst of codes that uh performs<00:01:05.880> very<00:01:06.080> bad<00:01:06.240> in<00:01:06.360> terms<00:01:06.680> of<00:01:06.920> ratio 00:01:07.350 --> 00:01:07.360 align:start position:0% performs very bad in terms of ratio 00:01:07.360 --> 00:01:09.789 align:start position:0% performs very bad in terms of ratio between<00:01:07.720> gas<00:01:08.159> and<00:01:08.360> GK<00:01:08.759> counters<00:01:09.280> so<00:01:09.439> for<00:01:09.640> that 00:01:09.789 --> 00:01:09.799 align:start position:0% between gas and GK counters so for that 00:01:09.799 --> 00:01:11.910 align:start position:0% between gas and GK counters so for that purpose<00:01:10.119> I<00:01:10.200> will<00:01:10.400> analyze<00:01:10.720> a<00:01:10.799> un<00:01:11.040> swap<00:01:11.240> swap 00:01:11.910 --> 00:01:11.920 align:start position:0% purpose I will analyze a un swap swap 00:01:11.920 --> 00:01:15.550 align:start position:0% purpose I will analyze a un swap swap trace<00:01:12.920> and<00:01:13.600> in<00:01:13.799> in<00:01:14.000> the<00:01:14.479> third<00:01:14.840> point<00:01:15.280> I<00:01:15.360> will 00:01:15.550 --> 00:01:15.560 align:start position:0% trace and in in the third point I will 00:01:15.560 --> 00:01:17.789 align:start position:0% trace and in in the third point I will basically<00:01:16.040> explain<00:01:16.360> it<00:01:16.720> what<00:01:16.840> are<00:01:17.000> the<00:01:17.200> next 00:01:17.789 --> 00:01:17.799 align:start position:0% basically explain it what are the next 00:01:17.799 --> 00:01:23.190 align:start position:0% basically explain it what are the next steps<00:01:18.920> um<00:01:20.079> how<00:01:21.079> I<00:01:21.159> would<00:01:21.360> say<00:01:21.960> the<00:01:22.360> the<00:01:22.880> how<00:01:23.079> we 00:01:23.190 --> 00:01:23.200 align:start position:0% steps um how I would say the the how we 00:01:23.200 --> 00:01:25.990 align:start position:0% steps um how I would say the the how we can<00:01:23.479> optimize<00:01:24.040> those<00:01:24.280> of<00:01:24.520> codes<00:01:25.479> in<00:01:25.600> order<00:01:25.840> to 00:01:25.990 --> 00:01:26.000 align:start position:0% can optimize those of codes in order to 00:01:26.000 --> 00:01:27.749 align:start position:0% can optimize those of codes in order to have<00:01:26.119> a<00:01:26.439> better<00:01:26.759> radio<00:01:27.119> between<00:01:27.360> the<00:01:27.479> gas<00:01:27.640> and 00:01:27.749 --> 00:01:27.759 align:start position:0% have a better radio between the gas and 00:01:27.759 --> 00:01:30.149 align:start position:0% have a better radio between the gas and the<00:01:27.840> S<00:01:28.000> en<00:01:28.119> counters<00:01:28.439> wasted<00:01:29.360> and<00:01:29.520> also<00:01:29.920> I<00:01:30.040> will 00:01:30.149 --> 00:01:30.159 align:start position:0% the S en counters wasted and also I will 00:01:30.159 --> 00:01:33.429 align:start position:0% the S en counters wasted and also I will explain<00:01:30.520> two<00:01:30.759> different<00:01:31.320> approaches<00:01:32.439> um 00:01:33.429 --> 00:01:33.439 align:start position:0% explain two different approaches um 00:01:33.439 --> 00:01:36.190 align:start position:0% explain two different approaches um about<00:01:33.840> how<00:01:34.200> those<00:01:34.640> OP<00:01:34.880> codes<00:01:35.200> could<00:01:35.360> be<00:01:35.560> priced 00:01:36.190 --> 00:01:36.200 align:start position:0% about how those OP codes could be priced 00:01:36.200 --> 00:01:40.310 align:start position:0% about how those OP codes could be priced on<00:01:36.360> the<00:01:36.680> zbm<00:01:37.680> okay<00:01:37.920> so<00:01:38.119> let's 00:01:40.310 --> 00:01:40.320 align:start position:0% on the zbm okay so let's 00:01:40.320 --> 00:01:42.950 align:start position:0% on the zbm okay so let's start<00:01:41.320> what<00:01:41.439> are<00:01:41.560> the<00:01:41.680> zik<00:01:41.960> counters<00:01:42.680> you<00:01:42.799> can 00:01:42.950 --> 00:01:42.960 align:start position:0% start what are the zik counters you can 00:01:42.960 --> 00:01:45.230 align:start position:0% start what are the zik counters you can imagine<00:01:43.560> the<00:01:43.759> zik<00:01:44.119> counters<00:01:44.840> if<00:01:44.960> you<00:01:45.079> can 00:01:45.230 --> 00:01:45.240 align:start position:0% imagine the zik counters if you can 00:01:45.240 --> 00:01:47.429 align:start position:0% imagine the zik counters if you can imagine<00:01:45.640> the<00:01:45.960> gas<00:01:46.280> on<00:01:46.439> ethereum<00:01:46.960> in<00:01:47.079> order<00:01:47.280> to 00:01:47.429 --> 00:01:47.439 align:start position:0% imagine the gas on ethereum in order to 00:01:47.439 --> 00:01:49.230 align:start position:0% imagine the gas on ethereum in order to measure<00:01:47.799> some<00:01:48.159> computational<00:01:48.799> cost 00:01:49.230 --> 00:01:49.240 align:start position:0% measure some computational cost 00:01:49.240 --> 00:01:51.270 align:start position:0% measure some computational cost execution<00:01:49.759> cost<00:01:50.240> you<00:01:50.360> can<00:01:50.520> imagine<00:01:50.840> the<00:01:51.000> zik 00:01:51.270 --> 00:01:51.280 align:start position:0% execution cost you can imagine the zik 00:01:51.280 --> 00:01:52.830 align:start position:0% execution cost you can imagine the zik counters<00:01:51.719> exactly<00:01:52.040> the<00:01:52.119> same<00:01:52.280> as<00:01:52.399> the<00:01:52.520> gas<00:01:52.719> but 00:01:52.830 --> 00:01:52.840 align:start position:0% counters exactly the same as the gas but 00:01:52.840 --> 00:01:56.950 align:start position:0% counters exactly the same as the gas but on<00:01:52.920> the<00:01:53.200> zbm<00:01:54.560> okay<00:01:55.560> basically<00:01:56.000> in<00:01:56.119> the<00:01:56.240> zbm<00:01:56.799> we 00:01:56.950 --> 00:01:56.960 align:start position:0% on the zbm okay basically in the zbm we 00:01:56.960 --> 00:01:59.230 align:start position:0% on the zbm okay basically in the zbm we have<00:01:57.600> in<00:01:57.719> ethereum<00:01:58.159> we<00:01:58.280> have<00:01:58.399> a<00:01:58.680> unit<00:01:59.039> which<00:01:59.159> is 00:01:59.230 --> 00:01:59.240 align:start position:0% have in ethereum we have a unit which is 00:01:59.240 --> 00:02:01.350 align:start position:0% have in ethereum we have a unit which is a<00:01:59.360> block<00:01:59.600> in<00:01:59.680> the<00:01:59.920> zbm<00:02:00.320> we<00:02:00.439> have<00:02:00.600> a<00:02:00.920> unit<00:02:01.200> of 00:02:01.350 --> 00:02:01.360 align:start position:0% a block in the zbm we have a unit of 00:02:01.360 --> 00:02:03.870 align:start position:0% a block in the zbm we have a unit of proving<00:02:01.759> which<00:02:01.880> is<00:02:02.240> a<00:02:02.399> batch<00:02:03.360> so<00:02:03.640> there<00:02:03.759> is 00:02:03.870 --> 00:02:03.880 align:start position:0% proving which is a batch so there is 00:02:03.880 --> 00:02:06.550 align:start position:0% proving which is a batch so there is some<00:02:04.079> relation<00:02:04.439> over<00:02:04.680> there<00:02:05.439> and<00:02:06.159> another 00:02:06.550 --> 00:02:06.560 align:start position:0% some relation over there and another 00:02:06.560 --> 00:02:08.550 align:start position:0% some relation over there and another difference<00:02:06.920> between<00:02:07.159> the<00:02:07.320> theum<00:02:07.600> and<00:02:07.680> the<00:02:07.759> zbm 00:02:08.550 --> 00:02:08.560 align:start position:0% difference between the theum and the zbm 00:02:08.560 --> 00:02:12.150 align:start position:0% difference between the theum and the zbm it's<00:02:08.840> like<00:02:09.360> on<00:02:09.520> ethereum<00:02:10.000> we<00:02:10.200> have<00:02:11.200> one<00:02:11.560> single 00:02:12.150 --> 00:02:12.160 align:start position:0% it's like on ethereum we have one single 00:02:12.160 --> 00:02:15.470 align:start position:0% it's like on ethereum we have one single dimensional<00:02:13.160> um<00:02:14.000> resource<00:02:14.560> which<00:02:14.680> is<00:02:14.800> the<00:02:15.000> gas 00:02:15.470 --> 00:02:15.480 align:start position:0% dimensional um resource which is the gas 00:02:15.480 --> 00:02:17.030 align:start position:0% dimensional um resource which is the gas but<00:02:15.640> on<00:02:15.760> the<00:02:15.920> ZM<00:02:16.360> site<00:02:16.519> we<00:02:16.599> have<00:02:16.720> the<00:02:16.800> Z 00:02:17.030 --> 00:02:17.040 align:start position:0% but on the ZM site we have the Z 00:02:17.040 --> 00:02:19.229 align:start position:0% but on the ZM site we have the Z counters<00:02:17.319> and<00:02:17.440> we<00:02:17.560> have<00:02:18.000> multiple<00:02:18.480> of<00:02:18.640> them 00:02:19.229 --> 00:02:19.239 align:start position:0% counters and we have multiple of them 00:02:19.239 --> 00:02:20.949 align:start position:0% counters and we have multiple of them okay<00:02:19.400> so<00:02:19.599> basically<00:02:20.040> this<00:02:20.519> this<00:02:20.720> table 00:02:20.949 --> 00:02:20.959 align:start position:0% okay so basically this this table 00:02:20.959 --> 00:02:23.229 align:start position:0% okay so basically this this table summarizes<00:02:21.879> what<00:02:22.000> I<00:02:22.120> have<00:02:22.319> just<00:02:22.440> said<00:02:22.680> on<00:02:22.840> eum 00:02:23.229 --> 00:02:23.239 align:start position:0% summarizes what I have just said on eum 00:02:23.239 --> 00:02:24.910 align:start position:0% summarizes what I have just said on eum we<00:02:23.360> have<00:02:23.480> a<00:02:23.560> unit<00:02:23.879> which<00:02:24.000> is<00:02:24.080> a<00:02:24.200> block<00:02:24.440> the<00:02:24.560> ZM 00:02:24.910 --> 00:02:24.920 align:start position:0% we have a unit which is a block the ZM 00:02:24.920 --> 00:02:28.150 align:start position:0% we have a unit which is a block the ZM is<00:02:25.040> a<00:02:25.440> badge<00:02:26.440> the<00:02:26.599> badge<00:02:27.080> consumes<00:02:27.640> some<00:02:27.920> gas 00:02:28.150 --> 00:02:28.160 align:start position:0% is a badge the badge consumes some gas 00:02:28.160 --> 00:02:30.070 align:start position:0% is a badge the badge consumes some gas it<00:02:28.400> has<00:02:28.599> some<00:02:28.800> limitation<00:02:29.239> on<00:02:29.360> the<00:02:29.519> gas<00:02:29.920> and 00:02:30.070 --> 00:02:30.080 align:start position:0% it has some limitation on the gas and 00:02:30.080 --> 00:02:33.589 align:start position:0% it has some limitation on the gas and the<00:02:30.200> gas<00:02:30.440> basically<00:02:30.840> reflects<00:02:31.760> the<00:02:32.760> EXE<00:02:33.319> the 00:02:33.589 --> 00:02:33.599 align:start position:0% the gas basically reflects the EXE the 00:02:33.599 --> 00:02:35.070 align:start position:0% the gas basically reflects the EXE the the<00:02:33.720> computational<00:02:34.319> resources<00:02:34.720> that<00:02:34.840> you<00:02:34.920> are 00:02:35.070 --> 00:02:35.080 align:start position:0% the computational resources that you are 00:02:35.080 --> 00:02:37.390 align:start position:0% the computational resources that you are wasting<00:02:35.360> when<00:02:35.480> you<00:02:35.599> execute<00:02:35.920> an<00:02:36.040> OP<00:02:36.280> code<00:02:37.200> this 00:02:37.390 --> 00:02:37.400 align:start position:0% wasting when you execute an OP code this 00:02:37.400 --> 00:02:40.430 align:start position:0% wasting when you execute an OP code this b<00:02:37.720> a<00:02:37.920> single<00:02:38.239> dimensional<00:02:38.800> gas<00:02:39.560> on<00:02:39.680> the<00:02:39.800> zbm 00:02:40.430 --> 00:02:40.440 align:start position:0% b a single dimensional gas on the zbm 00:02:40.440 --> 00:02:43.550 align:start position:0% b a single dimensional gas on the zbm side<00:02:40.959> we<00:02:41.159> have<00:02:41.879> a<00:02:42.080> batch<00:02:42.560> which<00:02:42.680> is<00:02:42.879> the<00:02:43.319> our 00:02:43.550 --> 00:02:43.560 align:start position:0% side we have a batch which is the our 00:02:43.560 --> 00:02:46.270 align:start position:0% side we have a batch which is the our unit<00:02:43.840> of<00:02:44.000> proving<00:02:44.720> we<00:02:44.879> have<00:02:45.000> the<00:02:45.159> zik<00:02:45.480> counters 00:02:46.270 --> 00:02:46.280 align:start position:0% unit of proving we have the zik counters 00:02:46.280 --> 00:02:49.630 align:start position:0% unit of proving we have the zik counters we<00:02:46.440> have<00:02:46.800> several<00:02:47.319> of<00:02:47.640> them<00:02:47.920> so<00:02:48.120> it's<00:02:48.440> kind<00:02:48.599> of 00:02:49.630 --> 00:02:49.640 align:start position:0% we have several of them so it's kind of 00:02:49.640 --> 00:02:51.869 align:start position:0% we have several of them so it's kind of multi-dimensional<00:02:50.640> and<00:02:50.840> basically<00:02:51.319> they 00:02:51.869 --> 00:02:51.879 align:start position:0% multi-dimensional and basically they 00:02:51.879 --> 00:02:55.550 align:start position:0% multi-dimensional and basically they reflect<00:02:52.879> the<00:02:53.519> the<00:02:53.599> proof<00:02:53.959> computational 00:02:55.550 --> 00:02:55.560 align:start position:0% reflect the the proof computational 00:02:55.560 --> 00:03:00.070 align:start position:0% reflect the the proof computational cost<00:02:56.879> okay<00:02:57.879> well<00:02:58.560> this<00:02:58.680> is<00:02:58.879> basically<00:02:59.680> uh 00:03:00.070 --> 00:03:00.080 align:start position:0% cost okay well this is basically uh 00:03:00.080 --> 00:03:03.550 align:start position:0% cost okay well this is basically uh piece<00:03:00.280> of<00:03:00.519> code<00:03:00.959> this<00:03:01.080> is<00:03:01.560> in<00:03:01.760> Z<00:03:02.360> assembly<00:03:03.360> uh 00:03:03.550 --> 00:03:03.560 align:start position:0% piece of code this is in Z assembly uh 00:03:03.560 --> 00:03:05.589 align:start position:0% piece of code this is in Z assembly uh basically<00:03:04.200> this<00:03:04.319> is<00:03:04.560> the<00:03:04.840> zik<00:03:05.200> ROM<00:03:05.440> we 00:03:05.589 --> 00:03:05.599 align:start position:0% basically this is the zik ROM we 00:03:05.599 --> 00:03:07.869 align:start position:0% basically this is the zik ROM we implement<00:03:06.200> the<00:03:06.440> evm<00:03:06.879> in<00:03:07.040> the<00:03:07.200> Z<00:03:07.480> Assembly 00:03:07.869 --> 00:03:07.879 align:start position:0% implement the evm in the Z Assembly 00:03:07.879 --> 00:03:09.830 align:start position:0% implement the evm in the Z Assembly Language<00:03:08.319> which<00:03:08.440> implements<00:03:09.000> the<00:03:09.159> the<00:03:09.239> evm<00:03:09.599> in 00:03:09.830 --> 00:03:09.840 align:start position:0% Language which implements the the evm in 00:03:09.840 --> 00:03:13.110 align:start position:0% Language which implements the the evm in Z<00:03:10.239> assembly<00:03:11.239> uh<00:03:11.400> language<00:03:11.959> and<00:03:12.120> basically 00:03:13.110 --> 00:03:13.120 align:start position:0% Z assembly uh language and basically 00:03:13.120 --> 00:03:16.630 align:start position:0% Z assembly uh language and basically those<00:03:13.519> are<00:03:14.040> all<00:03:14.560> the<00:03:15.080> ZK<00:03:15.519> counters<00:03:16.120> and<00:03:16.400> all 00:03:16.630 --> 00:03:16.640 align:start position:0% those are all the ZK counters and all 00:03:16.640 --> 00:03:19.830 align:start position:0% those are all the ZK counters and all these<00:03:17.000> values<00:03:18.000> quite<00:03:18.840> difficult<00:03:18.959> to<00:03:19.120> read<00:03:19.280> it 00:03:19.830 --> 00:03:19.840 align:start position:0% these values quite difficult to read it 00:03:19.840 --> 00:03:22.589 align:start position:0% these values quite difficult to read it so<00:03:20.840> in<00:03:20.959> order<00:03:21.200> to<00:03:21.560> understand<00:03:21.680> it<00:03:21.840> better<00:03:22.400> we 00:03:22.589 --> 00:03:22.599 align:start position:0% so in order to understand it better we 00:03:22.599 --> 00:03:24.750 align:start position:0% so in order to understand it better we have<00:03:22.879> as<00:03:23.000> I<00:03:23.120> mentioned<00:03:23.519> in<00:03:23.680> the<00:03:23.920> in<00:03:24.000> the<00:03:24.120> zbm<00:03:24.640> we 00:03:24.750 --> 00:03:24.760 align:start position:0% have as I mentioned in the in the zbm we 00:03:24.760 --> 00:03:27.110 align:start position:0% have as I mentioned in the in the zbm we have<00:03:24.920> a<00:03:25.120> unit<00:03:25.560> which<00:03:25.680> is<00:03:25.920> the<00:03:26.200> the<00:03:26.319> batch<00:03:26.920> and 00:03:27.110 --> 00:03:27.120 align:start position:0% have a unit which is the the batch and 00:03:27.120 --> 00:03:29.429 align:start position:0% have a unit which is the the batch and this<00:03:27.319> batch<00:03:27.680> has<00:03:28.080> several<00:03:28.439> zik<00:03:28.720> counters<00:03:29.319> what 00:03:29.429 --> 00:03:29.439 align:start position:0% this batch has several zik counters what 00:03:29.439 --> 00:03:32.550 align:start position:0% this batch has several zik counters what are<00:03:29.840> those<00:03:30.159> Zig<00:03:30.519> counters<00:03:30.920> basically<00:03:31.280> we<00:03:31.560> have 00:03:32.550 --> 00:03:32.560 align:start position:0% are those Zig counters basically we have 00:03:32.560 --> 00:03:34.350 align:start position:0% are those Zig counters basically we have the<00:03:32.760> steps<00:03:33.280> you<00:03:33.400> can<00:03:33.560> imagine<00:03:33.879> the<00:03:34.000> steps 00:03:34.350 --> 00:03:34.360 align:start position:0% the steps you can imagine the steps 00:03:34.360 --> 00:03:37.869 align:start position:0% the steps you can imagine the steps sometime<00:03:34.920> I<00:03:35.000> have<00:03:35.159> heard<00:03:35.519> about<00:03:36.439> kind<00:03:36.560> of<00:03:36.879> the 00:03:37.869 --> 00:03:37.879 align:start position:0% sometime I have heard about kind of the 00:03:37.879 --> 00:03:39.670 align:start position:0% sometime I have heard about kind of the you<00:03:37.959> can<00:03:38.640> you<00:03:38.720> can<00:03:38.879> change<00:03:39.120> the<00:03:39.239> word<00:03:39.480> and 00:03:39.670 --> 00:03:39.680 align:start position:0% you can you can change the word and 00:03:39.680 --> 00:03:41.350 align:start position:0% you can you can change the word and instead<00:03:39.920> of<00:03:40.040> saying<00:03:40.319> steps<00:03:40.599> you<00:03:40.680> can<00:03:40.799> say<00:03:41.200> kind 00:03:41.350 --> 00:03:41.360 align:start position:0% instead of saying steps you can say kind 00:03:41.360 --> 00:03:42.190 align:start position:0% instead of saying steps you can say kind of 00:03:42.190 --> 00:03:42.200 align:start position:0% of 00:03:42.200 --> 00:03:45.589 align:start position:0% of Cycles<00:03:43.200> H<00:03:43.319> we<00:03:43.519> have<00:03:43.760> the<00:03:44.120> arithmetic<00:03:45.080> State 00:03:45.589 --> 00:03:45.599 align:start position:0% Cycles H we have the arithmetic State 00:03:45.599 --> 00:03:48.509 align:start position:0% Cycles H we have the arithmetic State machine<00:03:46.599> in<00:03:46.680> order<00:03:46.879> to<00:03:47.000> do<00:03:47.519> multiplications 00:03:48.509 --> 00:03:48.519 align:start position:0% machine in order to do multiplications 00:03:48.519 --> 00:03:50.309 align:start position:0% machine in order to do multiplications and<00:03:48.959> well<00:03:49.159> also<00:03:49.360> we<00:03:49.480> use<00:03:49.680> the<00:03:49.840> state<00:03:50.040> machine 00:03:50.309 --> 00:03:50.319 align:start position:0% and well also we use the state machine 00:03:50.319 --> 00:03:53.030 align:start position:0% and well also we use the state machine in<00:03:50.439> order<00:03:50.680> to<00:03:50.840> prove<00:03:51.599> uh<00:03:51.720> divisions<00:03:52.319> by<00:03:52.879> by 00:03:53.030 --> 00:03:53.040 align:start position:0% in order to prove uh divisions by by 00:03:53.040 --> 00:03:55.030 align:start position:0% in order to prove uh divisions by by doing<00:03:53.319> multiplications<00:03:54.319> we<00:03:54.439> have<00:03:54.599> the<00:03:54.720> binary 00:03:55.030 --> 00:03:55.040 align:start position:0% doing multiplications we have the binary 00:03:55.040 --> 00:03:57.670 align:start position:0% doing multiplications we have the binary State<00:03:55.319> machine<00:03:55.599> in<00:03:55.720> order<00:03:55.920> to<00:03:56.079> do<00:03:56.439> additions 00:03:57.670 --> 00:03:57.680 align:start position:0% State machine in order to do additions 00:03:57.680 --> 00:03:59.949 align:start position:0% State machine in order to do additions subtractions<00:03:58.680> and<00:03:58.840> bitwise<00:03:59.319> operations 00:03:59.949 --> 00:03:59.959 align:start position:0% subtractions and bitwise operations 00:03:59.959 --> 00:04:02.830 align:start position:0% subtractions and bitwise operations basically<00:04:00.799> we<00:04:00.959> have<00:04:01.159> the<00:04:01.319> memory<00:04:01.680> align<00:04:02.280> State 00:04:02.830 --> 00:04:02.840 align:start position:0% basically we have the memory align State 00:04:02.840 --> 00:04:05.429 align:start position:0% basically we have the memory align State machine<00:04:03.840> basically<00:04:04.560> uh<00:04:04.680> when<00:04:04.799> you<00:04:04.959> read<00:04:05.239> an 00:04:05.429 --> 00:04:05.439 align:start position:0% machine basically uh when you read an 00:04:05.439 --> 00:04:07.470 align:start position:0% machine basically uh when you read an slot<00:04:05.680> and<00:04:05.760> the<00:04:05.879> CBM<00:04:06.519> two<00:04:06.720> different<00:04:07.000> slots<00:04:07.319> and 00:04:07.470 --> 00:04:07.480 align:start position:0% slot and the CBM two different slots and 00:04:07.480 --> 00:04:09.270 align:start position:0% slot and the CBM two different slots and you<00:04:07.599> want<00:04:07.879> you<00:04:08.000> want<00:04:08.159> to<00:04:08.319> join<00:04:08.560> all<00:04:08.680> the<00:04:08.840> bites 00:04:09.270 --> 00:04:09.280 align:start position:0% you want you want to join all the bites 00:04:09.280 --> 00:04:12.429 align:start position:0% you want you want to join all the bites together<00:04:10.280> uh<00:04:10.400> we<00:04:10.560> use<00:04:10.760> that<00:04:10.959> steam<00:04:11.439> machine 00:04:12.429 --> 00:04:12.439 align:start position:0% together uh we use that steam machine 00:04:12.439 --> 00:04:14.190 align:start position:0% together uh we use that steam machine have<00:04:12.640> the<00:04:12.840> kak<00:04:13.200> Ste<00:04:13.480> machine<00:04:13.879> which<00:04:14.000> is 00:04:14.190 --> 00:04:14.200 align:start position:0% have the kak Ste machine which is 00:04:14.200 --> 00:04:16.749 align:start position:0% have the kak Ste machine which is obvious<00:04:14.640> in<00:04:14.760> order<00:04:14.959> to<00:04:15.079> do<00:04:15.239> kak<00:04:15.600> hashing<00:04:16.600> we 00:04:16.749 --> 00:04:16.759 align:start position:0% obvious in order to do kak hashing we 00:04:16.759 --> 00:04:18.509 align:start position:0% obvious in order to do kak hashing we have<00:04:16.919> the<00:04:17.120> padding<00:04:17.479> poon<00:04:17.919> Ste<00:04:18.120> machine<00:04:18.359> and 00:04:18.509 --> 00:04:18.519 align:start position:0% have the padding poon Ste machine and 00:04:18.519 --> 00:04:21.310 align:start position:0% have the padding poon Ste machine and the<00:04:18.639> poson<00:04:19.359> Machine<00:04:20.359> again<00:04:21.079> quite 00:04:21.310 --> 00:04:21.320 align:start position:0% the poson Machine again quite 00:04:21.320 --> 00:04:23.749 align:start position:0% the poson Machine again quite straightforward<00:04:21.919> to<00:04:22.040> do<00:04:22.479> poson<00:04:22.919> hashing<00:04:23.400> and 00:04:23.749 --> 00:04:23.759 align:start position:0% straightforward to do poson hashing and 00:04:23.759 --> 00:04:26.189 align:start position:0% straightforward to do poson hashing and when<00:04:24.080> we<00:04:24.320> want<00:04:24.560> to<00:04:24.720> do<00:04:24.880> a<00:04:25.000> linear<00:04:25.400> posidon 00:04:26.189 --> 00:04:26.199 align:start position:0% when we want to do a linear posidon 00:04:26.199 --> 00:04:27.909 align:start position:0% when we want to do a linear posidon which<00:04:26.320> is<00:04:26.440> a<00:04:26.600> concatenation<00:04:27.199> of<00:04:27.360> poons<00:04:27.800> in 00:04:27.909 --> 00:04:27.919 align:start position:0% which is a concatenation of poons in 00:04:27.919 --> 00:04:31.110 align:start position:0% which is a concatenation of poons in order<00:04:28.199> to<00:04:28.400> Hash<00:04:29.000> a<00:04:29.160> long<00:04:29.560> r<00:04:29.880> of<00:04:30.039> bite<00:04:30.840> we<00:04:30.960> need 00:04:31.110 --> 00:04:31.120 align:start position:0% order to Hash a long r of bite we need 00:04:31.120 --> 00:04:33.230 align:start position:0% order to Hash a long r of bite we need to<00:04:31.240> use<00:04:31.400> the<00:04:31.560> padding<00:04:31.840> POS<00:04:32.080> on<00:04:32.280> Ste<00:04:32.560> machine 00:04:33.230 --> 00:04:33.240 align:start position:0% to use the padding POS on Ste machine 00:04:33.240 --> 00:04:36.029 align:start position:0% to use the padding POS on Ste machine and<00:04:33.360> the<00:04:33.479> very<00:04:33.720> last<00:04:33.880> one<00:04:34.080> is<00:04:34.360> the<00:04:34.479> Sha<00:04:34.759> 256<00:04:35.720> Ste 00:04:36.029 --> 00:04:36.039 align:start position:0% and the very last one is the Sha 256 Ste 00:04:36.039 --> 00:04:40.430 align:start position:0% and the very last one is the Sha 256 Ste machine<00:04:37.039> which<00:04:37.199> also<00:04:37.400> doing<00:04:38.120> for<00:04:39.120> so<00:04:40.120> it<00:04:40.240> is 00:04:40.430 --> 00:04:40.440 align:start position:0% machine which also doing for so it is 00:04:40.440 --> 00:04:44.390 align:start position:0% machine which also doing for so it is very<00:04:40.639> important<00:04:41.280> to<00:04:41.479> say<00:04:42.320> that<00:04:43.320> each<00:04:44.039> state 00:04:44.390 --> 00:04:44.400 align:start position:0% very important to say that each state 00:04:44.400 --> 00:04:48.029 align:start position:0% very important to say that each state machine<00:04:45.039> has<00:04:45.360> its<00:04:45.680> own<00:04:46.039> capacity<00:04:46.960> so<00:04:47.720> as<00:04:47.840> you 00:04:48.029 --> 00:04:48.039 align:start position:0% machine has its own capacity so as you 00:04:48.039 --> 00:04:52.390 align:start position:0% machine has its own capacity so as you may<00:04:48.199> see<00:04:48.759> on<00:04:49.039> on<00:04:49.199> this<00:04:49.800> slide<00:04:50.800> H<00:04:50.919> we<00:04:51.120> have<00:04:51.840> a<00:04:52.080> lot 00:04:52.390 --> 00:04:52.400 align:start position:0% may see on on this slide H we have a lot 00:04:52.400 --> 00:04:55.150 align:start position:0% may see on on this slide H we have a lot of<00:04:52.680> steps<00:04:53.479> because<00:04:54.479> I<00:04:54.560> would<00:04:54.759> say<00:04:55.000> the 00:04:55.150 --> 00:04:55.160 align:start position:0% of steps because I would say the 00:04:55.160 --> 00:04:57.710 align:start position:0% of steps because I would say the computational<00:04:55.759> cost<00:04:56.039> of<00:04:56.160> for<00:04:56.479> step<00:04:57.080> is<00:04:57.360> quite 00:04:57.710 --> 00:04:57.720 align:start position:0% computational cost of for step is quite 00:04:57.720 --> 00:05:00.950 align:start position:0% computational cost of for step is quite low<00:04:58.120> it's<00:04:58.360> just<00:04:58.639> one<00:04:59.199> I<00:04:59.280> would<00:04:59.440> say<00:05:00.080> one<00:05:00.600> hit 00:05:00.950 --> 00:05:00.960 align:start position:0% low it's just one I would say one hit 00:05:00.960 --> 00:05:03.430 align:start position:0% low it's just one I would say one hit one<00:05:01.199> row<00:05:02.080> when<00:05:02.280> we<00:05:02.440> go<00:05:02.639> through<00:05:02.880> the<00:05:03.080> program 00:05:03.430 --> 00:05:03.440 align:start position:0% one row when we go through the program 00:05:03.440 --> 00:05:06.950 align:start position:0% one row when we go through the program through<00:05:03.639> the<00:05:03.800> GBM<00:05:04.479> R<00:05:05.479> but<00:05:05.639> for<00:05:05.840> example<00:05:06.600> on<00:05:06.800> the 00:05:06.950 --> 00:05:06.960 align:start position:0% through the GBM R but for example on the 00:05:06.960 --> 00:05:10.310 align:start position:0% through the GBM R but for example on the kak<00:05:07.680> you<00:05:07.800> can<00:05:08.000> see<00:05:08.680> that<00:05:09.000> there<00:05:09.120> are<00:05:09.560> way<00:05:09.919> less 00:05:10.310 --> 00:05:10.320 align:start position:0% kak you can see that there are way less 00:05:10.320 --> 00:05:12.710 align:start position:0% kak you can see that there are way less resources<00:05:10.840> over<00:05:11.120> there<00:05:11.680> why<00:05:11.800> is<00:05:11.960> that<00:05:12.360> because 00:05:12.710 --> 00:05:12.720 align:start position:0% resources over there why is that because 00:05:12.720 --> 00:05:15.350 align:start position:0% resources over there why is that because basically<00:05:13.160> it's<00:05:13.479> more<00:05:13.800> complex<00:05:14.320> so<00:05:14.639> it<00:05:14.759> uses 00:05:15.350 --> 00:05:15.360 align:start position:0% basically it's more complex so it uses 00:05:15.360 --> 00:05:19.990 align:start position:0% basically it's more complex so it uses more<00:05:15.720> resources<00:05:16.199> so<00:05:16.400> it<00:05:16.600> has<00:05:17.039> less<00:05:17.360> capacity 00:05:19.990 --> 00:05:20.000 align:start position:0% 00:05:20.000 --> 00:05:21.830 align:start position:0% basically<00:05:21.000> one<00:05:21.160> thing<00:05:21.360> that<00:05:21.479> is<00:05:21.639> very 00:05:21.830 --> 00:05:21.840 align:start position:0% basically one thing that is very 00:05:21.840 --> 00:05:24.629 align:start position:0% basically one thing that is very important<00:05:22.199> also<00:05:22.400> to<00:05:22.520> mention<00:05:22.880> is<00:05:23.080> that<00:05:23.960> none 00:05:24.629 --> 00:05:24.639 align:start position:0% important also to mention is that none 00:05:24.639 --> 00:05:28.110 align:start position:0% important also to mention is that none in<00:05:24.759> a<00:05:25.000> batch<00:05:25.960> we<00:05:26.120> have<00:05:26.400> all<00:05:26.639> those<00:05:26.800> Z<00:05:27.160> resources 00:05:28.110 --> 00:05:28.120 align:start position:0% in a batch we have all those Z resources 00:05:28.120 --> 00:05:31.950 align:start position:0% in a batch we have all those Z resources none<00:05:28.560> of<00:05:28.840> those<00:05:29.160> s<00:05:30.000> Z<00:05:30.440> resources<00:05:31.160> can<00:05:31.360> be 00:05:31.950 --> 00:05:31.960 align:start position:0% none of those s Z resources can be 00:05:31.960 --> 00:05:35.670 align:start position:0% none of those s Z resources can be overflow<00:05:32.960> if<00:05:33.240> any<00:05:33.759> of<00:05:34.080> those<00:05:34.280> Z<00:05:34.639> resources<00:05:35.199> is 00:05:35.670 --> 00:05:35.680 align:start position:0% overflow if any of those Z resources is 00:05:35.680 --> 00:05:38.510 align:start position:0% overflow if any of those Z resources is is<00:05:35.919> overflowed<00:05:36.880> it<00:05:37.000> means<00:05:37.360> that<00:05:37.560> the<00:05:37.720> proof 00:05:38.510 --> 00:05:38.520 align:start position:0% is overflowed it means that the proof 00:05:38.520 --> 00:05:40.270 align:start position:0% is overflowed it means that the proof will<00:05:38.840> not<00:05:39.240> could<00:05:39.440> not<00:05:39.639> be<00:05:39.800> generated 00:05:40.270 --> 00:05:40.280 align:start position:0% will not could not be generated 00:05:40.280 --> 00:05:41.870 align:start position:0% will not could not be generated basically<00:05:40.639> the<00:05:40.759> pro<00:05:41.120> could<00:05:41.280> not<00:05:41.440> generate 00:05:41.870 --> 00:05:41.880 align:start position:0% basically the pro could not generate 00:05:41.880 --> 00:05:43.909 align:start position:0% basically the pro could not generate that<00:05:42.039> proof<00:05:42.440> so<00:05:42.600> we<00:05:42.759> need<00:05:42.919> to<00:05:43.080> be<00:05:43.479> very<00:05:43.680> aware 00:05:43.909 --> 00:05:43.919 align:start position:0% that proof so we need to be very aware 00:05:43.919 --> 00:05:45.230 align:start position:0% that proof so we need to be very aware of 00:05:45.230 --> 00:05:45.240 align:start position:0% of 00:05:45.240 --> 00:05:48.670 align:start position:0% of that<00:05:46.240> okay<00:05:46.479> so<00:05:47.000> let's<00:05:47.199> do<00:05:47.440> some<00:05:47.759> kind<00:05:47.919> of 00:05:48.670 --> 00:05:48.680 align:start position:0% that okay so let's do some kind of 00:05:48.680 --> 00:05:51.670 align:start position:0% that okay so let's do some kind of analysis<00:05:49.680> on<00:05:50.000> the<00:05:50.800> I<00:05:50.880> would<00:05:51.039> say<00:05:51.199> top<00:05:51.440> code 00:05:51.670 --> 00:05:51.680 align:start position:0% analysis on the I would say top code 00:05:51.680 --> 00:05:54.029 align:start position:0% analysis on the I would say top code offenders<00:05:52.120> on<00:05:52.199> the<00:05:52.319> zbm<00:05:53.240> and<00:05:53.440> as<00:05:53.560> I<00:05:53.720> mentioned 00:05:54.029 --> 00:05:54.039 align:start position:0% offenders on the zbm and as I mentioned 00:05:54.039 --> 00:05:57.710 align:start position:0% offenders on the zbm and as I mentioned there<00:05:54.160> are<00:05:55.120> super<00:05:55.639> straightforward<00:05:56.479> op<00:05:56.759> codes 00:05:57.710 --> 00:05:57.720 align:start position:0% there are super straightforward op codes 00:05:57.720 --> 00:06:01.590 align:start position:0% there are super straightforward op codes that<00:05:57.960> consumes<00:05:58.960> ZK<00:05:59.400> count<00:05:59.639> ERS<00:06:00.319> very<00:06:00.680> directly 00:06:01.590 --> 00:06:01.600 align:start position:0% that consumes ZK count ERS very directly 00:06:01.600 --> 00:06:03.950 align:start position:0% that consumes ZK count ERS very directly and<00:06:01.880> clearly<00:06:02.520> there<00:06:02.639> are<00:06:03.120> offenders<00:06:03.600> on<00:06:03.759> the 00:06:03.950 --> 00:06:03.960 align:start position:0% and clearly there are offenders on the 00:06:03.960 --> 00:06:06.870 align:start position:0% and clearly there are offenders on the zbm<00:06:04.960> what<00:06:05.080> I<00:06:05.240> mean<00:06:05.680> when<00:06:05.800> I<00:06:05.960> say<00:06:06.199> offenders<00:06:06.759> it 00:06:06.870 --> 00:06:06.880 align:start position:0% zbm what I mean when I say offenders it 00:06:06.880 --> 00:06:09.790 align:start position:0% zbm what I mean when I say offenders it means<00:06:07.240> that<00:06:07.479> those<00:06:07.680> of<00:06:07.919> codes<00:06:08.479> consumes<00:06:09.199> some 00:06:09.790 --> 00:06:09.800 align:start position:0% means that those of codes consumes some 00:06:09.800 --> 00:06:13.430 align:start position:0% means that those of codes consumes some gas<00:06:10.680> and<00:06:10.880> this<00:06:11.160> gas<00:06:11.680> is<00:06:12.120> basically<00:06:13.120> not 00:06:13.430 --> 00:06:13.440 align:start position:0% gas and this gas is basically not 00:06:13.440 --> 00:06:15.150 align:start position:0% gas and this gas is basically not reflected<00:06:13.919> on<00:06:14.039> the<00:06:14.160> ZK<00:06:14.479> counters<00:06:14.800> that<00:06:15.000> they 00:06:15.150 --> 00:06:15.160 align:start position:0% reflected on the ZK counters that they 00:06:15.160 --> 00:06:17.430 align:start position:0% reflected on the ZK counters that they consume<00:06:15.800> so<00:06:16.039> there<00:06:16.160> is<00:06:16.280> a<00:06:16.400> misalignment<00:06:17.199> over 00:06:17.430 --> 00:06:17.440 align:start position:0% consume so there is a misalignment over 00:06:17.440 --> 00:06:19.790 align:start position:0% consume so there is a misalignment over there<00:06:17.919> the<00:06:18.039> most<00:06:18.280> straightforward<00:06:18.880> one<00:06:19.199> and 00:06:19.790 --> 00:06:19.800 align:start position:0% there the most straightforward one and 00:06:19.800 --> 00:06:22.230 align:start position:0% there the most straightforward one and of<00:06:19.919> course<00:06:20.160> you<00:06:20.360> may<00:06:20.639> heard<00:06:21.000> about<00:06:21.680> in<00:06:22.000> every 00:06:22.230 --> 00:06:22.240 align:start position:0% of course you may heard about in every 00:06:22.240 --> 00:06:26.749 align:start position:0% of course you may heard about in every zvm<00:06:22.880> if<00:06:23.000> you<00:06:23.120> do<00:06:23.520> a<00:06:23.759> loop<00:06:24.120> of<00:06:24.919> kaks<00:06:25.919> then<00:06:26.639> you 00:06:26.749 --> 00:06:26.759 align:start position:0% zvm if you do a loop of kaks then you 00:06:26.759 --> 00:06:29.270 align:start position:0% zvm if you do a loop of kaks then you are<00:06:27.000> wasting<00:06:27.599> a<00:06:27.759> lot<00:06:27.960> of<00:06:28.120> Z<00:06:28.560> resources<00:06:29.000> but<00:06:29.120> you 00:06:29.270 --> 00:06:29.280 align:start position:0% are wasting a lot of Z resources but you 00:06:29.280 --> 00:06:31.110 align:start position:0% are wasting a lot of Z resources but you pay 00:06:31.110 --> 00:06:31.120 align:start position:0% pay 00:06:31.120 --> 00:06:33.749 align:start position:0% pay quite<00:06:31.440> cheap<00:06:31.840> gas<00:06:32.800> so<00:06:33.000> for<00:06:33.160> example<00:06:33.520> the<00:06:33.680> the 00:06:33.749 --> 00:06:33.759 align:start position:0% quite cheap gas so for example the the 00:06:33.759 --> 00:06:35.390 align:start position:0% quite cheap gas so for example the the first<00:06:34.039> code<00:06:34.240> is<00:06:34.319> the<00:06:34.440> Gard<00:06:34.759> the<00:06:34.840> second<00:06:35.160> code 00:06:35.390 --> 00:06:35.400 align:start position:0% first code is the Gard the second code 00:06:35.400 --> 00:06:38.830 align:start position:0% first code is the Gard the second code is<00:06:35.520> the<00:06:35.800> code<00:06:36.120> copy<00:06:36.360> and<00:06:36.560> cod<00:06:36.759> data<00:06:37.400> copy<00:06:38.400> uh<00:06:38.639> in 00:06:38.830 --> 00:06:38.840 align:start position:0% is the code copy and cod data copy uh in 00:06:38.840 --> 00:06:41.150 align:start position:0% is the code copy and cod data copy uh in this<00:06:39.080> case<00:06:39.840> um<00:06:40.120> I<00:06:40.199> would<00:06:40.360> say<00:06:40.520> that<00:06:40.720> all<00:06:40.919> of 00:06:41.150 --> 00:06:41.160 align:start position:0% this case um I would say that all of 00:06:41.160 --> 00:06:47.710 align:start position:0% this case um I would say that all of codes<00:06:42.000> that<00:06:42.280> has<00:06:43.199> some<00:06:43.440> kind<00:06:43.639> of<00:06:44.759> um 00:06:47.710 --> 00:06:47.720 align:start position:0% codes that has some kind of um 00:06:47.720 --> 00:06:51.550 align:start position:0% codes that has some kind of um dynamic<00:06:48.720> dynamic<00:06:49.440> gas<00:06:49.759> pricing<00:06:50.280> given<00:06:51.000> that 00:06:51.550 --> 00:06:51.560 align:start position:0% dynamic dynamic gas pricing given that 00:06:51.560 --> 00:06:53.710 align:start position:0% dynamic dynamic gas pricing given that uh<00:06:51.680> given<00:06:51.919> the<00:06:52.000> memory<00:06:52.319> expansion<00:06:53.280> uh<00:06:53.360> we<00:06:53.560> need 00:06:53.710 --> 00:06:53.720 align:start position:0% uh given the memory expansion uh we need 00:06:53.720 --> 00:06:56.430 align:start position:0% uh given the memory expansion uh we need to<00:06:53.840> do<00:06:54.080> some<00:06:54.319> computations<00:06:54.840> on<00:06:55.000> the<00:06:55.120> zbm<00:06:55.960> that 00:06:56.430 --> 00:06:56.440 align:start position:0% to do some computations on the zbm that 00:06:56.440 --> 00:06:58.029 align:start position:0% to do some computations on the zbm that of<00:06:56.599> course<00:06:56.800> it<00:06:56.960> C<00:06:57.199> some<00:06:57.360> arithmetization 00:06:58.029 --> 00:06:58.039 align:start position:0% of course it C some arithmetization 00:06:58.039 --> 00:07:00.710 align:start position:0% of course it C some arithmetization binary<00:06:59.039> and<00:06:59.240> steps 00:07:00.710 --> 00:07:00.720 align:start position:0% binary and steps 00:07:00.720 --> 00:07:03.430 align:start position:0% binary and steps and<00:07:01.160> also<00:07:01.919> when<00:07:02.120> we<00:07:02.240> do<00:07:02.440> some<00:07:02.680> kind<00:07:02.840> of<00:07:03.160> copy 00:07:03.430 --> 00:07:03.440 align:start position:0% and also when we do some kind of copy 00:07:03.440 --> 00:07:05.510 align:start position:0% and also when we do some kind of copy reation<00:07:03.840> between<00:07:04.240> context<00:07:04.919> one<00:07:05.120> context<00:07:05.400> to 00:07:05.510 --> 00:07:05.520 align:start position:0% reation between context one context to 00:07:05.520 --> 00:07:08.469 align:start position:0% reation between context one context to another<00:07:05.840> context<00:07:06.720> it<00:07:06.879> will<00:07:07.160> basically<00:07:07.639> waste 00:07:08.469 --> 00:07:08.479 align:start position:0% another context it will basically waste 00:07:08.479 --> 00:07:10.390 align:start position:0% another context it will basically waste um<00:07:08.720> a<00:07:08.840> lot<00:07:09.000> of<00:07:09.240> steps<00:07:09.560> as 00:07:10.390 --> 00:07:10.400 align:start position:0% um a lot of steps as 00:07:10.400 --> 00:07:13.909 align:start position:0% um a lot of steps as well<00:07:11.400> the<00:07:11.560> third<00:07:11.840> one<00:07:12.840> also<00:07:13.400> I<00:07:13.479> think<00:07:13.639> it's 00:07:13.909 --> 00:07:13.919 align:start position:0% well the third one also I think it's 00:07:13.919 --> 00:07:16.189 align:start position:0% well the third one also I think it's very<00:07:14.120> clear<00:07:14.440> the<00:07:14.599> example<00:07:15.319> it's<00:07:15.599> the<00:07:15.759> external 00:07:16.189 --> 00:07:16.199 align:start position:0% very clear the example it's the external 00:07:16.199 --> 00:07:19.510 align:start position:0% very clear the example it's the external Cod<00:07:16.599> copy<00:07:16.960> op<00:07:17.400> code<00:07:18.400> in<00:07:18.560> this<00:07:18.759> case<00:07:19.160> we<00:07:19.240> are 00:07:19.510 --> 00:07:19.520 align:start position:0% Cod copy op code in this case we are 00:07:19.520 --> 00:07:21.830 align:start position:0% Cod copy op code in this case we are just<00:07:20.400> I<00:07:20.479> mean<00:07:20.720> this<00:07:20.879> op<00:07:21.080> code<00:07:21.280> basically<00:07:21.599> just 00:07:21.830 --> 00:07:21.840 align:start position:0% just I mean this op code basically just 00:07:21.840 --> 00:07:27.309 align:start position:0% just I mean this op code basically just cop<00:07:22.120> so<00:07:22.960> copy<00:07:23.759> some<00:07:24.680> bytes<00:07:25.560> of<00:07:25.720> a<00:07:26.319> bite<00:07:26.599> code 00:07:27.309 --> 00:07:27.319 align:start position:0% cop so copy some bytes of a bite code 00:07:27.319 --> 00:07:30.029 align:start position:0% cop so copy some bytes of a bite code into<00:07:27.560> a<00:07:27.639> memory<00:07:28.000> region<00:07:28.759> okay<00:07:29.000> that's<00:07:29.199> it 00:07:30.029 --> 00:07:30.039 align:start position:0% into a memory region okay that's it 00:07:30.039 --> 00:07:32.029 align:start position:0% into a memory region okay that's it what<00:07:30.199> you<00:07:30.360> need<00:07:30.479> to<00:07:30.639> do<00:07:30.919> inside<00:07:31.199> the<00:07:31.319> zbm<00:07:31.960> you 00:07:32.029 --> 00:07:32.039 align:start position:0% what you need to do inside the zbm you 00:07:32.039 --> 00:07:34.029 align:start position:0% what you need to do inside the zbm you need<00:07:32.199> to<00:07:32.360> provide<00:07:32.639> the<00:07:32.720> full<00:07:32.960> bite<00:07:33.240> code<00:07:33.919> you 00:07:34.029 --> 00:07:34.039 align:start position:0% need to provide the full bite code you 00:07:34.039 --> 00:07:36.110 align:start position:0% need to provide the full bite code you need<00:07:34.199> to<00:07:34.319> Hash<00:07:34.520> it<00:07:34.639> with<00:07:34.759> the<00:07:34.840> linear<00:07:35.160> poon<00:07:36.000> you 00:07:36.110 --> 00:07:36.120 align:start position:0% need to Hash it with the linear poon you 00:07:36.120 --> 00:07:38.510 align:start position:0% need to Hash it with the linear poon you need<00:07:36.280> to<00:07:36.440> check<00:07:36.720> that<00:07:36.960> that<00:07:37.199> hash<00:07:37.879> matches<00:07:38.360> the 00:07:38.510 --> 00:07:38.520 align:start position:0% need to check that that hash matches the 00:07:38.520 --> 00:07:40.710 align:start position:0% need to check that that hash matches the one<00:07:39.120> that<00:07:39.560> you<00:07:39.680> need<00:07:39.840> to<00:07:39.960> read<00:07:40.199> on<00:07:40.319> the<00:07:40.440> state 00:07:40.710 --> 00:07:40.720 align:start position:0% one that you need to read on the state 00:07:40.720 --> 00:07:43.869 align:start position:0% one that you need to read on the state three<00:07:41.240> so<00:07:41.479> now<00:07:41.759> you<00:07:42.000> know<00:07:42.720> that<00:07:43.000> the<00:07:43.160> full<00:07:43.560> bite 00:07:43.869 --> 00:07:43.879 align:start position:0% three so now you know that the full bite 00:07:43.879 --> 00:07:46.550 align:start position:0% three so now you know that the full bite code<00:07:44.120> is<00:07:44.360> correct<00:07:45.360> and<00:07:45.639> you<00:07:45.759> need<00:07:45.919> to<00:07:46.120> go<00:07:46.400> to 00:07:46.550 --> 00:07:46.560 align:start position:0% code is correct and you need to go to 00:07:46.560 --> 00:07:48.309 align:start position:0% code is correct and you need to go to the<00:07:46.720> exactly<00:07:47.199> bite<00:07:47.479> or<00:07:47.639> number<00:07:47.840> of<00:07:47.960> bites<00:07:48.199> that 00:07:48.309 --> 00:07:48.319 align:start position:0% the exactly bite or number of bites that 00:07:48.319 --> 00:07:50.430 align:start position:0% the exactly bite or number of bites that you<00:07:48.400> want<00:07:48.520> to<00:07:48.680> copy<00:07:48.879> into<00:07:49.080> your<00:07:49.240> memory<00:07:49.560> region 00:07:50.430 --> 00:07:50.440 align:start position:0% you want to copy into your memory region 00:07:50.440 --> 00:07:51.589 align:start position:0% you want to copy into your memory region take<00:07:50.639> that<00:07:50.800> bites<00:07:51.039> and<00:07:51.120> then<00:07:51.240> copy<00:07:51.479> to<00:07:51.520> the 00:07:51.589 --> 00:07:51.599 align:start position:0% take that bites and then copy to the 00:07:51.599 --> 00:07:52.830 align:start position:0% take that bites and then copy to the memory<00:07:51.840> region<00:07:52.080> so<00:07:52.280> there<00:07:52.360> is<00:07:52.479> a<00:07:52.599> lot<00:07:52.720> of 00:07:52.830 --> 00:07:52.840 align:start position:0% memory region so there is a lot of 00:07:52.840 --> 00:07:54.830 align:start position:0% memory region so there is a lot of things<00:07:53.000> to<00:07:53.120> do<00:07:53.240> on<00:07:53.319> the<00:07:53.479> zvm<00:07:54.240> but<00:07:54.400> the<00:07:54.520> cost<00:07:54.720> of 00:07:54.830 --> 00:07:54.840 align:start position:0% things to do on the zvm but the cost of 00:07:54.840 --> 00:07:57.309 align:start position:0% things to do on the zvm but the cost of this<00:07:55.159> code<00:07:55.720> is<00:07:55.879> not<00:07:56.159> that 00:07:57.309 --> 00:07:57.319 align:start position:0% this code is not that 00:07:57.319 --> 00:07:59.990 align:start position:0% this code is not that much<00:07:58.319> and<00:07:58.520> of<00:07:58.680> course<00:07:59.280> uh 00:07:59.990 --> 00:08:00.000 align:start position:0% much and of course uh 00:08:00.000 --> 00:08:02.670 align:start position:0% much and of course uh the<00:08:00.960> clear<00:08:01.280> offenders<00:08:01.759> are<00:08:01.919> the<00:08:02.039> pl<00:08:02.240> compil 00:08:02.670 --> 00:08:02.680 align:start position:0% the clear offenders are the pl compil 00:08:02.680 --> 00:08:05.629 align:start position:0% the clear offenders are the pl compil smart<00:08:03.280> contracts<00:08:04.280> uh<00:08:04.479> you<00:08:04.599> know<00:08:05.240> specific 00:08:05.629 --> 00:08:05.639 align:start position:0% smart contracts uh you know specific 00:08:05.639 --> 00:08:08.270 align:start position:0% smart contracts uh you know specific functions<00:08:06.000> on<00:08:06.159> ethereum<00:08:06.800> like<00:08:07.280> is<00:08:07.680> recover 00:08:08.270 --> 00:08:08.280 align:start position:0% functions on ethereum like is recover 00:08:08.280 --> 00:08:10.830 align:start position:0% functions on ethereum like is recover pings<00:08:09.280> uh<00:08:09.440> modular<00:08:09.840> exponentiation<00:08:10.520> and<00:08:10.680> so 00:08:10.830 --> 00:08:10.840 align:start position:0% pings uh modular exponentiation and so 00:08:10.840 --> 00:08:14.629 align:start position:0% pings uh modular exponentiation and so on<00:08:11.759> and<00:08:12.120> there<00:08:12.240> is<00:08:12.360> a<00:08:12.680> very<00:08:12.960> huge<00:08:13.440> misalignment 00:08:14.629 --> 00:08:14.639 align:start position:0% on and there is a very huge misalignment 00:08:14.639 --> 00:08:16.909 align:start position:0% on and there is a very huge misalignment between<00:08:15.639> the<00:08:15.759> precompiled<00:08:16.360> smart<00:08:16.599> contract 00:08:16.909 --> 00:08:16.919 align:start position:0% between the precompiled smart contract 00:08:16.919 --> 00:08:18.510 align:start position:0% between the precompiled smart contract gas<00:08:17.120> pricing<00:08:17.520> and<00:08:17.680> the<00:08:17.800> ZK<00:08:18.159> counter 00:08:18.510 --> 00:08:18.520 align:start position:0% gas pricing and the ZK counter 00:08:18.520 --> 00:08:21.029 align:start position:0% gas pricing and the ZK counter resourcing<00:08:19.080> consuming<00:08:20.039> the 00:08:21.029 --> 00:08:21.039 align:start position:0% resourcing consuming the 00:08:21.039 --> 00:08:23.749 align:start position:0% resourcing consuming the zbm<00:08:22.039> okay<00:08:22.759> those<00:08:22.919> of<00:08:23.120> course<00:08:23.360> I<00:08:23.479> would<00:08:23.599> say 00:08:23.749 --> 00:08:23.759 align:start position:0% zbm okay those of course I would say 00:08:23.759 --> 00:08:26.070 align:start position:0% zbm okay those of course I would say that<00:08:23.879> are<00:08:24.199> very<00:08:24.840> clear<00:08:25.319> that<00:08:25.800> that<00:08:25.960> are 00:08:26.070 --> 00:08:26.080 align:start position:0% that are very clear that that are 00:08:26.080 --> 00:08:30.550 align:start position:0% that are very clear that that are offenders<00:08:26.680> but<00:08:27.240> I<00:08:27.319> wanted<00:08:28.199> to<00:08:28.599> analyze<00:08:29.199> the 00:08:30.550 --> 00:08:30.560 align:start position:0% offenders but I wanted to analyze the 00:08:30.560 --> 00:08:33.149 align:start position:0% offenders but I wanted to analyze the not<00:08:30.759> the<00:08:30.879> clear<00:08:31.319> codes<00:08:31.680> but<00:08:32.279> the<00:08:32.560> standard<00:08:32.919> of 00:08:33.149 --> 00:08:33.159 align:start position:0% not the clear codes but the standard of 00:08:33.159 --> 00:08:36.430 align:start position:0% not the clear codes but the standard of codes<00:08:33.560> standard<00:08:34.000> transactions<00:08:34.919> on<00:08:35.120> the 00:08:36.430 --> 00:08:36.440 align:start position:0% codes standard transactions on the 00:08:36.440 --> 00:08:41.350 align:start position:0% codes standard transactions on the evm<00:08:37.440> in<00:08:37.640> this<00:08:37.839> case<00:08:38.599> uh<00:08:38.959> basically<00:08:40.159> here<00:08:41.159> this 00:08:41.350 --> 00:08:41.360 align:start position:0% evm in this case uh basically here this 00:08:41.360 --> 00:08:44.550 align:start position:0% evm in this case uh basically here this table<00:08:41.839> well<00:08:42.080> before<00:08:42.320> going<00:08:42.519> to<00:08:42.640> the<00:08:42.839> table<00:08:43.839> um 00:08:44.550 --> 00:08:44.560 align:start position:0% table well before going to the table um 00:08:44.560 --> 00:08:46.910 align:start position:0% table well before going to the table um all<00:08:44.880> these<00:08:45.160> numbers<00:08:45.640> belong<00:08:46.120> I<00:08:46.200> mean<00:08:46.720> there 00:08:46.910 --> 00:08:46.920 align:start position:0% all these numbers belong I mean there 00:08:46.920 --> 00:08:49.550 align:start position:0% all these numbers belong I mean there some<00:08:47.519> assumptions<00:08:48.519> the<00:08:48.680> first<00:08:48.959> assumption<00:08:49.360> is 00:08:49.550 --> 00:08:49.560 align:start position:0% some assumptions the first assumption is 00:08:49.560 --> 00:08:52.870 align:start position:0% some assumptions the first assumption is that<00:08:49.959> here<00:08:50.600> we<00:08:50.720> are<00:08:51.160> I'm<00:08:51.320> showing<00:08:51.800> data<00:08:52.480> of<00:08:52.680> a 00:08:52.870 --> 00:08:52.880 align:start position:0% that here we are I'm showing data of a 00:08:52.880 --> 00:08:55.910 align:start position:0% that here we are I'm showing data of a one<00:08:53.120> batch<00:08:53.560> that<00:08:53.760> has<00:08:54.040> only<00:08:54.480> one<00:08:54.760> block<00:08:55.560> and 00:08:55.910 --> 00:08:55.920 align:start position:0% one batch that has only one block and 00:08:55.920 --> 00:08:57.790 align:start position:0% one batch that has only one block and this<00:08:56.160> block 00:08:57.790 --> 00:08:57.800 align:start position:0% this block 00:08:57.800 --> 00:09:00.230 align:start position:0% this block has<00:08:58.800> and<00:08:59.040> transaction 00:09:00.230 --> 00:09:00.240 align:start position:0% has and transaction 00:09:00.240 --> 00:09:02.230 align:start position:0% has and transaction okay<00:09:00.839> and<00:09:01.000> these<00:09:01.200> transactions<00:09:01.720> are<00:09:01.959> always 00:09:02.230 --> 00:09:02.240 align:start position:0% okay and these transactions are always 00:09:02.240 --> 00:09:04.630 align:start position:0% okay and these transactions are always the<00:09:02.360> same<00:09:02.640> type<00:09:03.120> so<00:09:03.320> you<00:09:03.440> can<00:09:03.600> imagine<00:09:04.200> a<00:09:04.360> block 00:09:04.630 --> 00:09:04.640 align:start position:0% the same type so you can imagine a block 00:09:04.640 --> 00:09:07.509 align:start position:0% the same type so you can imagine a block in<00:09:04.720> the<00:09:04.839> zbm<00:09:05.640> with<00:09:06.360> just<00:09:06.600> ether<00:09:06.959> transfers 00:09:07.509 --> 00:09:07.519 align:start position:0% in the zbm with just ether transfers 00:09:07.519 --> 00:09:09.829 align:start position:0% in the zbm with just ether transfers with<00:09:07.760> just<00:09:08.640> toket<00:09:08.880> transfers<00:09:09.240> and<00:09:09.440> just<00:09:09.640> with 00:09:09.829 --> 00:09:09.839 align:start position:0% with just toket transfers and just with 00:09:09.839 --> 00:09:12.310 align:start position:0% with just toket transfers and just with un<00:09:10.120> swap<00:09:10.360> swaps<00:09:11.360> so<00:09:11.560> let's<00:09:11.760> go<00:09:11.880> for<00:09:12.000> the<00:09:12.120> first 00:09:12.310 --> 00:09:12.320 align:start position:0% un swap swaps so let's go for the first 00:09:12.320 --> 00:09:14.870 align:start position:0% un swap swaps so let's go for the first one<00:09:12.480> the<00:09:12.680> theum<00:09:12.959> transfer<00:09:13.640> we<00:09:13.760> can<00:09:13.959> fill<00:09:14.279> up<00:09:14.720> up 00:09:14.870 --> 00:09:14.880 align:start position:0% one the theum transfer we can fill up up 00:09:14.880 --> 00:09:18.509 align:start position:0% one the theum transfer we can fill up up to<00:09:15.440> 2,000<00:09:16.320> more<00:09:16.440> or<00:09:16.560> less<00:09:17.120> trans<00:09:17.720> a<00:09:17.880> bat<00:09:18.320> and<00:09:18.440> we 00:09:18.509 --> 00:09:18.519 align:start position:0% to 2,000 more or less trans a bat and we 00:09:18.519 --> 00:09:21.670 align:start position:0% to 2,000 more or less trans a bat and we can<00:09:18.640> see<00:09:18.839> that<00:09:19.040> the<00:09:19.360> top<00:09:20.200> GK<00:09:20.760> counter<00:09:21.320> the<00:09:21.440> more 00:09:21.670 --> 00:09:21.680 align:start position:0% can see that the top GK counter the more 00:09:21.680 --> 00:09:23.710 align:start position:0% can see that the top GK counter the more limiting<00:09:22.120> GK<00:09:22.440> counter<00:09:22.800> is<00:09:22.920> the 00:09:23.710 --> 00:09:23.720 align:start position:0% limiting GK counter is the 00:09:23.720 --> 00:09:27.269 align:start position:0% limiting GK counter is the arithmetic<00:09:24.720> why<00:09:25.640> because<00:09:26.360> we<00:09:26.519> are<00:09:26.839> basically 00:09:27.269 --> 00:09:27.279 align:start position:0% arithmetic why because we are basically 00:09:27.279 --> 00:09:29.470 align:start position:0% arithmetic why because we are basically checking<00:09:27.720> the<00:09:27.880> signator<00:09:28.320> inside<00:09:28.560> the<00:09:28.680> C<00:09:29.200> so<00:09:29.399> we 00:09:29.470 --> 00:09:29.480 align:start position:0% checking the signator inside the C so we 00:09:29.480 --> 00:09:31.110 align:start position:0% checking the signator inside the C so we are<00:09:29.560> doing<00:09:29.760> a<00:09:29.880> lot<00:09:30.000> of<00:09:30.120> is<00:09:30.440> recover<00:09:30.800> the 00:09:31.110 --> 00:09:31.120 align:start position:0% are doing a lot of is recover the 00:09:31.120 --> 00:09:34.790 align:start position:0% are doing a lot of is recover the recover<00:09:31.959> uses<00:09:32.440> a<00:09:32.560> lot<00:09:32.760> of<00:09:33.079> arithmetic<00:09:33.880> State 00:09:34.790 --> 00:09:34.800 align:start position:0% recover uses a lot of arithmetic State 00:09:34.800 --> 00:09:37.069 align:start position:0% recover uses a lot of arithmetic State machines<00:09:35.800> if<00:09:35.920> we<00:09:36.040> go<00:09:36.200> to<00:09:36.320> the<00:09:36.480> next<00:09:36.680> two<00:09:36.839> ones 00:09:37.069 --> 00:09:37.079 align:start position:0% machines if we go to the next two ones 00:09:37.079 --> 00:09:40.550 align:start position:0% machines if we go to the next two ones the<00:09:38.079> the<00:09:38.160> Unis<00:09:38.640> swap<00:09:39.519> what<00:09:39.720> we<00:09:39.839> can<00:09:40.000> see<00:09:40.360> is 00:09:40.550 --> 00:09:40.560 align:start position:0% the the Unis swap what we can see is 00:09:40.560 --> 00:09:44.350 align:start position:0% the the Unis swap what we can see is that<00:09:41.440> okay<00:09:41.640> we<00:09:41.760> can<00:09:41.959> fit<00:09:42.800> less<00:09:43.360> transactions 00:09:44.350 --> 00:09:44.360 align:start position:0% that okay we can fit less transactions 00:09:44.360 --> 00:09:46.670 align:start position:0% that okay we can fit less transactions because<00:09:44.640> you<00:09:44.800> have<00:09:45.079> you<00:09:45.200> have<00:09:45.760> some<00:09:46.160> execution 00:09:46.670 --> 00:09:46.680 align:start position:0% because you have you have some execution 00:09:46.680 --> 00:09:47.389 align:start position:0% because you have you have some execution to 00:09:47.389 --> 00:09:47.399 align:start position:0% to 00:09:47.399 --> 00:09:50.790 align:start position:0% to do<00:09:48.399> and<00:09:48.600> we<00:09:48.720> can<00:09:48.880> see<00:09:49.120> that<00:09:49.480> the<00:09:49.839> top<00:09:50.079> of<00:09:50.279> kodik 00:09:50.790 --> 00:09:50.800 align:start position:0% do and we can see that the top of kodik 00:09:50.800 --> 00:09:53.310 align:start position:0% do and we can see that the top of kodik counter<00:09:51.079> offender<00:09:51.640> are<00:09:52.079> basically<00:09:52.600> the 00:09:53.310 --> 00:09:53.320 align:start position:0% counter offender are basically the 00:09:53.320 --> 00:09:56.949 align:start position:0% counter offender are basically the steps<00:09:54.320> either<00:09:55.120> also<00:09:55.440> I<00:09:55.519> mean<00:09:55.760> either<00:09:55.959> in<00:09:56.079> the 00:09:56.949 --> 00:09:56.959 align:start position:0% steps either also I mean either in the 00:09:56.959 --> 00:09:58.949 align:start position:0% steps either also I mean either in the and<00:09:57.079> the<00:09:57.160> Unis<00:09:57.399> swap<00:09:57.640> swap<00:09:58.440> regarding<00:09:58.839> the 00:09:58.949 --> 00:09:58.959 align:start position:0% and the Unis swap swap regarding the 00:09:58.959 --> 00:10:01.990 align:start position:0% and the Unis swap swap regarding the UNIS<00:09:59.640> up<00:09:59.959> it<00:10:00.160> gets<00:10:00.440> even<00:10:00.720> worse<00:10:01.079> I<00:10:01.160> mean<00:10:01.680> you 00:10:01.990 --> 00:10:02.000 align:start position:0% UNIS up it gets even worse I mean you 00:10:02.000 --> 00:10:06.430 align:start position:0% UNIS up it gets even worse I mean you hit<00:10:02.519> the<00:10:02.839> top<00:10:03.839> uh<00:10:04.000> the<00:10:04.160> limit<00:10:04.680> of<00:10:05.200> steps<00:10:06.000> and 00:10:06.430 --> 00:10:06.440 align:start position:0% hit the top uh the limit of steps and 00:10:06.440 --> 00:10:09.630 align:start position:0% hit the top uh the limit of steps and the<00:10:06.560> other<00:10:06.839> state<00:10:07.120> machines<00:10:08.120> remain<00:10:08.519> at<00:10:09.279> he 00:10:09.630 --> 00:10:09.640 align:start position:0% the other state machines remain at he 00:10:09.640 --> 00:10:11.829 align:start position:0% the other state machines remain at he capacity<00:10:10.440> even 00:10:11.829 --> 00:10:11.839 align:start position:0% capacity even 00:10:11.839 --> 00:10:15.190 align:start position:0% capacity even less<00:10:12.839> given<00:10:13.200> those<00:10:13.600> numbers<00:10:14.600> uh<00:10:14.720> we're<00:10:15.000> going 00:10:15.190 --> 00:10:15.200 align:start position:0% less given those numbers uh we're going 00:10:15.200 --> 00:10:18.509 align:start position:0% less given those numbers uh we're going to<00:10:15.560> get<00:10:16.079> into<00:10:16.440> the<00:10:16.600> details<00:10:17.040> of<00:10:18.000> what<00:10:18.160> are<00:10:18.360> the 00:10:18.509 --> 00:10:18.519 align:start position:0% to get into the details of what are the 00:10:18.519 --> 00:10:22.750 align:start position:0% to get into the details of what are the op<00:10:18.800> codes<00:10:19.200> in<00:10:19.360> a<00:10:19.519> Unis<00:10:19.800> swap<00:10:20.040> swap<00:10:20.399> Trace<00:10:21.760> that 00:10:22.750 --> 00:10:22.760 align:start position:0% op codes in a Unis swap swap Trace that 00:10:22.760 --> 00:10:25.190 align:start position:0% op codes in a Unis swap swap Trace that consumes<00:10:23.560> more 00:10:25.190 --> 00:10:25.200 align:start position:0% consumes more 00:10:25.200 --> 00:10:27.949 align:start position:0% consumes more steps<00:10:26.200> okay<00:10:26.360> so<00:10:26.680> yes<00:10:27.160> what<00:10:27.279> are<00:10:27.399> the<00:10:27.519> up<00:10:27.680> codes 00:10:27.949 --> 00:10:27.959 align:start position:0% steps okay so yes what are the up codes 00:10:27.959 --> 00:10:30.509 align:start position:0% steps okay so yes what are the up codes that<00:10:28.200> consume<00:10:28.640> more<00:10:28.880> steps<00:10:29.360> in<00:10:29.480> a<00:10:29.600> Unis<00:10:29.920> swap 00:10:30.509 --> 00:10:30.519 align:start position:0% that consume more steps in a Unis swap 00:10:30.519 --> 00:10:35.350 align:start position:0% that consume more steps in a Unis swap swap<00:10:31.519> so<00:10:32.480> in<00:10:32.640> a<00:10:32.839> Unis<00:10:33.519> if<00:10:34.120> if<00:10:34.240> you<00:10:34.480> analyze<00:10:35.160> a 00:10:35.350 --> 00:10:35.360 align:start position:0% swap so in a Unis if if you analyze a 00:10:35.360 --> 00:10:37.870 align:start position:0% swap so in a Unis if if you analyze a trace<00:10:36.120> of<00:10:36.279> the<00:10:36.440> Unis<00:10:36.760> swap<00:10:37.000> swap<00:10:37.440> uh<00:10:37.519> you<00:10:37.639> will 00:10:37.870 --> 00:10:37.880 align:start position:0% trace of the Unis swap swap uh you will 00:10:37.880 --> 00:10:41.389 align:start position:0% trace of the Unis swap swap uh you will find<00:10:38.320> that<00:10:39.320> um<00:10:39.959> push<00:10:40.200> one<00:10:40.440> push<00:10:40.639> two<00:10:40.839> M<00:10:41.040> store 00:10:41.389 --> 00:10:41.399 align:start position:0% find that um push one push two M store 00:10:41.399 --> 00:10:44.829 align:start position:0% find that um push one push two M store pop<00:10:41.639> and<00:10:41.800> push<00:10:42.120> 20<00:10:42.920> are<00:10:43.160> the<00:10:43.360> most<00:10:44.120> used<00:10:44.639> to 00:10:44.829 --> 00:10:44.839 align:start position:0% pop and push 20 are the most used to 00:10:44.839 --> 00:10:47.190 align:start position:0% pop and push 20 are the most used to coders<00:10:45.320> if<00:10:45.519> you<00:10:45.880> join<00:10:46.399> all<00:10:46.600> the<00:10:46.760> steps 00:10:47.190 --> 00:10:47.200 align:start position:0% coders if you join all the steps 00:10:47.200 --> 00:10:49.710 align:start position:0% coders if you join all the steps consumed<00:10:48.200> by<00:10:48.440> all<00:10:48.639> the<00:10:48.800> appearance<00:10:49.200> of<00:10:49.399> that 00:10:49.710 --> 00:10:49.720 align:start position:0% consumed by all the appearance of that 00:10:49.720 --> 00:10:52.110 align:start position:0% consumed by all the appearance of that op<00:10:49.959> coders<00:10:50.360> on<00:10:50.560> the<00:10:50.720> the<00:10:50.800> book<00:10:51.040> Trace<00:10:51.760> you<00:10:51.880> will 00:10:52.110 --> 00:10:52.120 align:start position:0% op coders on the the book Trace you will 00:10:52.120 --> 00:10:56.230 align:start position:0% op coders on the the book Trace you will find<00:10:52.720> that<00:10:53.720> the<00:10:54.079> push<00:10:54.480> one<00:10:54.920> op<00:10:55.200> code<00:10:55.920> uh<00:10:56.040> will 00:10:56.230 --> 00:10:56.240 align:start position:0% find that the push one op code uh will 00:10:56.240 --> 00:10:59.829 align:start position:0% find that the push one op code uh will weighs<00:10:56.600> around<00:10:57.480> uh<00:10:57.639> 12,000<00:10:58.600> steps 00:10:59.829 --> 00:10:59.839 align:start position:0% weighs around uh 12,000 steps 00:10:59.839 --> 00:11:01.990 align:start position:0% weighs around uh 12,000 steps and<00:11:00.200> it<00:11:00.399> appears<00:11:00.920> in<00:11:01.040> the<00:11:01.160> unisoft<00:11:01.600> sh<00:11:01.880> it 00:11:01.990 --> 00:11:02.000 align:start position:0% and it appears in the unisoft sh it 00:11:02.000 --> 00:11:05.949 align:start position:0% and it appears in the unisoft sh it appears<00:11:02.399> 658<00:11:03.360> times<00:11:04.320> so<00:11:04.760> same<00:11:05.000> for<00:11:05.360> p<00:11:05.560> two<00:11:05.720> M 00:11:05.949 --> 00:11:05.959 align:start position:0% appears 658 times so same for p two M 00:11:05.959 --> 00:11:08.629 align:start position:0% appears 658 times so same for p two M store<00:11:06.240> pop<00:11:06.399> and<00:11:06.519> P<00:11:07.000> so<00:11:07.360> basically<00:11:07.800> this<00:11:08.160> stop 00:11:08.629 --> 00:11:08.639 align:start position:0% store pop and P so basically this stop 00:11:08.639 --> 00:11:10.949 align:start position:0% store pop and P so basically this stop these<00:11:08.880> op<00:11:09.160> codes<00:11:09.800> are<00:11:10.079> the<00:11:10.200> ones<00:11:10.480> that 00:11:10.949 --> 00:11:10.959 align:start position:0% these op codes are the ones that 00:11:10.959 --> 00:11:15.470 align:start position:0% these op codes are the ones that consumes<00:11:11.959> the<00:11:12.160> most<00:11:12.720> steps<00:11:13.360> on<00:11:13.480> the<00:11:13.639> Unis<00:11:14.000> swap 00:11:15.470 --> 00:11:15.480 align:start position:0% consumes the most steps on the Unis swap 00:11:15.480 --> 00:11:19.269 align:start position:0% consumes the most steps on the Unis swap shop<00:11:16.480> but<00:11:16.760> let's<00:11:17.079> go<00:11:17.519> again<00:11:17.880> into<00:11:18.160> the 00:11:19.269 --> 00:11:19.279 align:start position:0% shop but let's go again into the 00:11:19.279 --> 00:11:22.670 align:start position:0% shop but let's go again into the details<00:11:20.279> inside<00:11:20.600> these<00:11:20.760> op<00:11:21.000> codes<00:11:21.760> which<00:11:21.920> are 00:11:22.670 --> 00:11:22.680 align:start position:0% details inside these op codes which are 00:11:22.680 --> 00:11:27.230 align:start position:0% details inside these op codes which are the<00:11:23.680> is<00:11:23.920> the<00:11:24.200> user<00:11:25.200> paying<00:11:26.000> the<00:11:26.240> correct<00:11:26.800> gas 00:11:27.230 --> 00:11:27.240 align:start position:0% the is the user paying the correct gas 00:11:27.240 --> 00:11:30.069 align:start position:0% the is the user paying the correct gas price<00:11:28.160> I<00:11:28.240> mean<00:11:28.880> is<00:11:29.000> the<00:11:29.440> are<00:11:29.560> paying<00:11:29.839> the 00:11:30.069 --> 00:11:30.079 align:start position:0% price I mean is the are paying the 00:11:30.079 --> 00:11:32.910 align:start position:0% price I mean is the are paying the correct<00:11:30.440> gas<00:11:30.760> price<00:11:31.040> in<00:11:31.200> order<00:11:31.760> because<00:11:32.760> the 00:11:32.910 --> 00:11:32.920 align:start position:0% correct gas price in order because the 00:11:32.920 --> 00:11:36.430 align:start position:0% correct gas price in order because the up<00:11:33.160> Cod<00:11:33.360> is<00:11:33.480> consuming<00:11:34.040> 2,000<00:11:35.040> um<00:11:35.440> 12,000 00:11:36.430 --> 00:11:36.440 align:start position:0% up Cod is consuming 2,000 um 12,000 00:11:36.440 --> 00:11:38.790 align:start position:0% up Cod is consuming 2,000 um 12,000 steps<00:11:37.360> so<00:11:37.600> here's<00:11:37.800> the<00:11:37.920> question<00:11:38.240> yes<00:11:38.399> or<00:11:38.560> no 00:11:38.790 --> 00:11:38.800 align:start position:0% steps so here's the question yes or no 00:11:38.800 --> 00:11:41.590 align:start position:0% steps so here's the question yes or no so<00:11:39.000> let's<00:11:39.200> go<00:11:39.360> to<00:11:39.519> analyze<00:11:39.880> a<00:11:40.000> little<00:11:40.360> bit<00:11:41.360> and 00:11:41.590 --> 00:11:41.600 align:start position:0% so let's go to analyze a little bit and 00:11:41.600 --> 00:11:45.150 align:start position:0% so let's go to analyze a little bit and here<00:11:42.320> basically<00:11:43.320> I<00:11:43.639> what<00:11:43.760> I<00:11:43.920> did<00:11:44.200> here<00:11:44.440> is<00:11:44.959> uh 00:11:45.150 --> 00:11:45.160 align:start position:0% here basically I what I did here is uh 00:11:45.160 --> 00:11:48.790 align:start position:0% here basically I what I did here is uh comparing<00:11:46.120> the<00:11:46.360> gas<00:11:46.720> of<00:11:46.959> an<00:11:47.200> not<00:11:47.399> code<00:11:48.079> versus 00:11:48.790 --> 00:11:48.800 align:start position:0% comparing the gas of an not code versus 00:11:48.800 --> 00:11:51.430 align:start position:0% comparing the gas of an not code versus the<00:11:49.279> steps<00:11:49.680> that<00:11:49.839> that<00:11:50.240> code<00:11:50.519> consumed<00:11:51.160> on<00:11:51.320> the 00:11:51.430 --> 00:11:51.440 align:start position:0% the steps that that code consumed on the 00:11:51.440 --> 00:11:54.069 align:start position:0% the steps that that code consumed on the zbm<00:11:52.320> so<00:11:52.600> basically<00:11:53.000> we<00:11:53.160> can<00:11:53.399> get<00:11:53.600> some<00:11:53.800> kind<00:11:53.959> of 00:11:54.069 --> 00:11:54.079 align:start position:0% zbm so basically we can get some kind of 00:11:54.079 --> 00:11:56.470 align:start position:0% zbm so basically we can get some kind of a<00:11:54.279> Rao<00:11:54.720> between<00:11:55.120> gas<00:11:55.560> and 00:11:56.470 --> 00:11:56.480 align:start position:0% a Rao between gas and 00:11:56.480 --> 00:11:59.829 align:start position:0% a Rao between gas and steps<00:11:57.480> here<00:11:57.639> we<00:11:57.760> can<00:11:57.959> say<00:11:58.240> that 00:11:59.829 --> 00:11:59.839 align:start position:0% steps here we can say that 00:11:59.839 --> 00:12:03.829 align:start position:0% steps here we can say that by<00:12:00.040> far<00:12:00.639> the<00:12:00.839> worst<00:12:01.200> up<00:12:01.519> code<00:12:02.120> is<00:12:02.320> the<00:12:02.560> Cod<00:12:02.880> copy 00:12:03.829 --> 00:12:03.839 align:start position:0% by far the worst up code is the Cod copy 00:12:03.839 --> 00:12:08.629 align:start position:0% by far the worst up code is the Cod copy because<00:12:04.399> it<00:12:04.600> cost<00:12:05.000> just<00:12:05.279> 15<00:12:05.959> gas<00:12:07.040> and<00:12:08.040> consumes 00:12:08.629 --> 00:12:08.639 align:start position:0% because it cost just 15 gas and consumes 00:12:08.639 --> 00:12:11.790 align:start position:0% because it cost just 15 gas and consumes 1,000<00:12:09.320> steps<00:12:09.720> so<00:12:09.880> the<00:12:10.000> rtio<00:12:10.800> is<00:12:11.200> I<00:12:11.279> would<00:12:11.480> say 00:12:11.790 --> 00:12:11.800 align:start position:0% 1,000 steps so the rtio is I would say 00:12:11.800 --> 00:12:15.030 align:start position:0% 1,000 steps so the rtio is I would say quite<00:12:12.040> bad<00:12:12.720> the<00:12:12.839> second<00:12:13.160> one<00:12:13.440> is<00:12:13.600> a<00:12:14.079> m<00:12:14.360> store 00:12:15.030 --> 00:12:15.040 align:start position:0% quite bad the second one is a m store 00:12:15.040 --> 00:12:17.030 align:start position:0% quite bad the second one is a m store here<00:12:15.360> I<00:12:15.480> highlight<00:12:15.800> it<00:12:16.040> in<00:12:16.279> in<00:12:16.480> in<00:12:16.639> green 00:12:17.030 --> 00:12:17.040 align:start position:0% here I highlight it in in in green 00:12:17.040 --> 00:12:20.509 align:start position:0% here I highlight it in in in green because<00:12:18.040> it<00:12:18.240> also<00:12:19.000> it's<00:12:19.279> one<00:12:19.480> of<00:12:19.639> the<00:12:19.839> op<00:12:20.120> codes 00:12:20.509 --> 00:12:20.519 align:start position:0% because it also it's one of the op codes 00:12:20.519 --> 00:12:23.590 align:start position:0% because it also it's one of the op codes that<00:12:21.160> has<00:12:21.399> more<00:12:21.760> appearance<00:12:22.480> also<00:12:22.959> on<00:12:23.240> a<00:12:23.360> uni 00:12:23.590 --> 00:12:23.600 align:start position:0% that has more appearance also on a uni 00:12:23.600 --> 00:12:25.629 align:start position:0% that has more appearance also on a uni swap<00:12:23.880> swap 00:12:25.629 --> 00:12:25.639 align:start position:0% swap swap 00:12:25.639 --> 00:12:28.949 align:start position:0% swap swap Trace<00:12:26.639> so<00:12:27.000> clearly<00:12:27.600> if<00:12:27.800> we<00:12:28.000> want<00:12:28.320> to<00:12:28.560> increase 00:12:28.949 --> 00:12:28.959 align:start position:0% Trace so clearly if we want to increase 00:12:28.959 --> 00:12:32.350 align:start position:0% Trace so clearly if we want to increase the<00:12:29.240> efficiency<00:12:29.720> of<00:12:29.880> a<00:12:30.120> v<00:12:30.519> in<00:12:30.639> the<00:12:30.800> zvm<00:12:31.760> clearly 00:12:32.350 --> 00:12:32.360 align:start position:0% the efficiency of a v in the zvm clearly 00:12:32.360 --> 00:12:35.269 align:start position:0% the efficiency of a v in the zvm clearly we<00:12:32.480> need<00:12:32.639> to<00:12:33.360> optimize<00:12:34.000> we<00:12:34.120> need<00:12:34.279> to<00:12:34.639> get 00:12:35.269 --> 00:12:35.279 align:start position:0% we need to optimize we need to get 00:12:35.279 --> 00:12:39.269 align:start position:0% we need to optimize we need to get better<00:12:35.680> ratio<00:12:36.399> in<00:12:36.560> the<00:12:36.720> MS<00:12:37.079> St<00:12:37.440> for<00:12:37.639> example<00:12:38.199> op 00:12:39.269 --> 00:12:39.279 align:start position:0% better ratio in the MS St for example op 00:12:39.279 --> 00:12:41.670 align:start position:0% better ratio in the MS St for example op code<00:12:40.279> third<00:12:40.519> one<00:12:40.639> is<00:12:40.760> the<00:12:40.920> call<00:12:41.120> that<00:12:41.240> the<00:12:41.360> copy 00:12:41.670 --> 00:12:41.680 align:start position:0% code third one is the call that the copy 00:12:41.680 --> 00:12:44.269 align:start position:0% code third one is the call that the copy then<00:12:41.880> push<00:12:42.120> through2<00:12:42.639> and<00:12:42.760> then<00:12:42.959> call<00:12:43.199> that<00:12:43.480> Lo 00:12:44.269 --> 00:12:44.279 align:start position:0% then push through2 and then call that Lo 00:12:44.279 --> 00:12:48.590 align:start position:0% then push through2 and then call that Lo we<00:12:44.480> want<00:12:45.399> to<00:12:46.399> get<00:12:46.760> rid<00:12:47.120> of<00:12:47.480> those<00:12:47.760> top<00:12:48.079> up<00:12:48.320> Cod 00:12:48.590 --> 00:12:48.600 align:start position:0% we want to get rid of those top up Cod 00:12:48.600 --> 00:12:52.230 align:start position:0% we want to get rid of those top up Cod offenders<00:12:49.160> what<00:12:49.320> we<00:12:49.440> should<00:12:49.760> do<00:12:50.279> is<00:12:51.279> repricing 00:12:52.230 --> 00:12:52.240 align:start position:0% offenders what we should do is repricing 00:12:52.240 --> 00:12:55.509 align:start position:0% offenders what we should do is repricing them<00:12:53.240> or<00:12:53.519> optimize<00:12:54.120> them<00:12:54.560> in<00:12:54.680> order<00:12:54.959> to<00:12:55.160> get<00:12:55.360> a 00:12:55.509 --> 00:12:55.519 align:start position:0% them or optimize them in order to get a 00:12:55.519 --> 00:12:57.870 align:start position:0% them or optimize them in order to get a better<00:12:55.760> Rao 00:12:57.870 --> 00:12:57.880 align:start position:0% better Rao 00:12:57.880 --> 00:13:00.310 align:start position:0% better Rao basically<00:12:58.880> on<00:12:59.199> the<00:12:59.320> other 00:13:00.310 --> 00:13:00.320 align:start position:0% basically on the other 00:13:00.320 --> 00:13:03.310 align:start position:0% basically on the other side<00:13:01.320> what<00:13:01.440> are<00:13:01.639> the<00:13:01.800> best<00:13:02.040> of<00:13:02.240> codes<00:13:02.920> what<00:13:03.040> are 00:13:03.310 --> 00:13:03.320 align:start position:0% side what are the best of codes what are 00:13:03.320 --> 00:13:05.949 align:start position:0% side what are the best of codes what are the<00:13:03.519> ones<00:13:03.920> that<00:13:04.320> uh<00:13:04.639> basically<00:13:05.040> the<00:13:05.160> user<00:13:05.480> is 00:13:05.949 --> 00:13:05.959 align:start position:0% the ones that uh basically the user is 00:13:05.959 --> 00:13:09.590 align:start position:0% the ones that uh basically the user is paying<00:13:06.959> um<00:13:07.399> I<00:13:07.480> would<00:13:07.639> say<00:13:08.079> fairly<00:13:09.079> about<00:13:09.440> the 00:13:09.590 --> 00:13:09.600 align:start position:0% paying um I would say fairly about the 00:13:09.600 --> 00:13:11.870 align:start position:0% paying um I would say fairly about the ZK<00:13:09.959> counters<00:13:10.279> that<00:13:10.440> it<00:13:10.600> consumes<00:13:11.000> on<00:13:11.120> the<00:13:11.199> zvm 00:13:11.870 --> 00:13:11.880 align:start position:0% ZK counters that it consumes on the zvm 00:13:11.880 --> 00:13:14.670 align:start position:0% ZK counters that it consumes on the zvm so<00:13:12.120> here<00:13:12.279> we<00:13:12.399> have<00:13:12.560> for<00:13:12.720> example<00:13:13.079> the<00:13:13.959> one<00:13:14.360> jump 00:13:14.670 --> 00:13:14.680 align:start position:0% so here we have for example the one jump 00:13:14.680 --> 00:13:16.750 align:start position:0% so here we have for example the one jump jump<00:13:15.040> conditional<00:13:15.399> stand<00:13:15.760> Cod<00:13:16.000> size<00:13:16.240> or<00:13:16.519> log 00:13:16.750 --> 00:13:16.760 align:start position:0% jump conditional stand Cod size or log 00:13:16.760 --> 00:13:20.350 align:start position:0% jump conditional stand Cod size or log three<00:13:17.760> of<00:13:17.920> course<00:13:18.680> log<00:13:18.920> three<00:13:19.279> s<00:13:19.440> a<00:13:19.639> store<00:13:20.120> and 00:13:20.350 --> 00:13:20.360 align:start position:0% three of course log three s a store and 00:13:20.360 --> 00:13:22.829 align:start position:0% three of course log three s a store and this<00:13:20.560> kind<00:13:20.760> of<00:13:20.959> op<00:13:21.240> codes<00:13:21.959> the<00:13:22.079> ratio<00:13:22.480> is<00:13:22.639> very 00:13:22.829 --> 00:13:22.839 align:start position:0% this kind of op codes the ratio is very 00:13:22.839 --> 00:13:24.550 align:start position:0% this kind of op codes the ratio is very very<00:13:23.040> very<00:13:23.279> very<00:13:23.440> low<00:13:23.880> because<00:13:24.160> basically<00:13:24.480> you 00:13:24.550 --> 00:13:24.560 align:start position:0% very very very low because basically you 00:13:24.560 --> 00:13:26.230 align:start position:0% very very very low because basically you are<00:13:24.720> paying<00:13:24.959> that<00:13:25.079> you<00:13:25.199> are<00:13:25.399> storage<00:13:25.959> some 00:13:26.230 --> 00:13:26.240 align:start position:0% are paying that you are storage some 00:13:26.240 --> 00:13:27.910 align:start position:0% are paying that you are storage some data<00:13:26.480> on<00:13:26.560> the<00:13:26.680> receip<00:13:27.000> 3<00:13:27.240> or<00:13:27.399> on<00:13:27.560> the<00:13:27.680> state 00:13:27.910 --> 00:13:27.920 align:start position:0% data on the receip 3 or on the state 00:13:27.920 --> 00:13:30.910 align:start position:0% data on the receip 3 or on the state three 00:13:30.910 --> 00:13:30.920 align:start position:0% three 00:13:30.920 --> 00:13:36.030 align:start position:0% three okay<00:13:31.160> so<00:13:31.760> now<00:13:32.000> the<00:13:32.160> question<00:13:32.639> is<00:13:33.639> how<00:13:34.440> to<00:13:35.440> di 00:13:36.030 --> 00:13:36.040 align:start position:0% okay so now the question is how to di 00:13:36.040 --> 00:13:39.269 align:start position:0% okay so now the question is how to di those<00:13:36.360> OP<00:13:36.639> coders<00:13:37.639> accordingly 00:13:39.269 --> 00:13:39.279 align:start position:0% those OP coders accordingly 00:13:39.279 --> 00:13:41.790 align:start position:0% those OP coders accordingly to<00:13:40.279> the<00:13:40.480> ZK<00:13:40.880> counters<00:13:41.240> that<00:13:41.440> they<00:13:41.560> are 00:13:41.790 --> 00:13:41.800 align:start position:0% to the ZK counters that they are 00:13:41.800 --> 00:13:45.710 align:start position:0% to the ZK counters that they are consuming<00:13:42.880> basically<00:13:43.880> okay<00:13:44.839> and<00:13:45.279> the<00:13:45.399> most 00:13:45.710 --> 00:13:45.720 align:start position:0% consuming basically okay and the most 00:13:45.720 --> 00:13:47.470 align:start position:0% consuming basically okay and the most straightforward<00:13:46.639> approach<00:13:47.120> which<00:13:47.240> is<00:13:47.360> the 00:13:47.470 --> 00:13:47.480 align:start position:0% straightforward approach which is the 00:13:47.480 --> 00:13:49.629 align:start position:0% straightforward approach which is the one<00:13:47.639> that<00:13:47.760> we<00:13:47.839> are<00:13:47.920> following<00:13:48.440> right<00:13:48.560> now<00:13:49.160> is 00:13:49.629 --> 00:13:49.639 align:start position:0% one that we are following right now is 00:13:49.639 --> 00:13:52.629 align:start position:0% one that we are following right now is an<00:13:49.959> static<00:13:50.560> approach<00:13:51.560> you<00:13:51.680> can<00:13:51.800> see<00:13:52.079> from<00:13:52.519> you 00:13:52.629 --> 00:13:52.639 align:start position:0% an static approach you can see from you 00:13:52.639 --> 00:13:55.829 align:start position:0% an static approach you can see from you can<00:13:52.759> imagine<00:13:53.600> uh<00:13:53.759> the<00:13:53.920> batch<00:13:54.440> as<00:13:54.600> a<00:13:55.279> monolithic 00:13:55.829 --> 00:13:55.839 align:start position:0% can imagine uh the batch as a monolithic 00:13:55.839 --> 00:13:57.910 align:start position:0% can imagine uh the batch as a monolithic batch<00:13:56.759> we<00:13:56.920> have<00:13:57.120> all<00:13:57.279> the<00:13:57.440> resources 00:13:57.910 --> 00:13:57.920 align:start position:0% batch we have all the resources 00:13:57.920 --> 00:14:00.749 align:start position:0% batch we have all the resources available<00:13:58.800> and<00:13:59.199> think<00:13:59.519> that<00:14:00.040> regardless<00:14:00.560> of 00:14:00.749 --> 00:14:00.759 align:start position:0% available and think that regardless of 00:14:00.759 --> 00:14:02.629 align:start position:0% available and think that regardless of the<00:14:00.959> transactions<00:14:01.519> that<00:14:01.680> are<00:14:01.920> executed<00:14:02.440> on 00:14:02.629 --> 00:14:02.639 align:start position:0% the transactions that are executed on 00:14:02.639 --> 00:14:05.710 align:start position:0% the transactions that are executed on that<00:14:02.800> batch<00:14:03.759> that<00:14:03.920> batch<00:14:04.320> has<00:14:04.560> a<00:14:04.800> price<00:14:05.519> that's 00:14:05.710 --> 00:14:05.720 align:start position:0% that batch that batch has a price that's 00:14:05.720 --> 00:14:08.230 align:start position:0% that batch that batch has a price that's it<00:14:06.320> in<00:14:06.480> this<00:14:06.720> case 00:14:08.230 --> 00:14:08.240 align:start position:0% it in this case 00:14:08.240 --> 00:14:12.629 align:start position:0% it in this case 0.01<00:14:09.240> so<00:14:09.680> the<00:14:09.800> sequencer<00:14:10.440> basically<00:14:11.399> pays<00:14:11.880> for 00:14:12.629 --> 00:14:12.639 align:start position:0% 0.01 so the sequencer basically pays for 00:14:12.639 --> 00:14:16.030 align:start position:0% 0.01 so the sequencer basically pays for the<00:14:12.839> batches<00:14:13.519> that<00:14:13.839> it<00:14:14.079> post<00:14:14.519> to<00:14:14.680> layer<00:14:15.040> one 00:14:16.030 --> 00:14:16.040 align:start position:0% the batches that it post to layer one 00:14:16.040 --> 00:14:18.350 align:start position:0% the batches that it post to layer one and<00:14:16.399> the<00:14:16.519> verifier<00:14:17.160> when<00:14:17.320> the<00:14:17.440> verifier 00:14:18.350 --> 00:14:18.360 align:start position:0% and the verifier when the verifier 00:14:18.360 --> 00:14:20.670 align:start position:0% and the verifier when the verifier verifies<00:14:19.360> those<00:14:19.839> uh<00:14:20.000> batches<00:14:20.399> that<00:14:20.519> are 00:14:20.670 --> 00:14:20.680 align:start position:0% verifies those uh batches that are 00:14:20.680 --> 00:14:22.629 align:start position:0% verifies those uh batches that are posted<00:14:20.920> in<00:14:21.000> the<00:14:21.160> ler<00:14:21.399> one<00:14:21.680> it<00:14:21.839> receed<00:14:22.240> the<00:14:22.480> the 00:14:22.629 --> 00:14:22.639 align:start position:0% posted in the ler one it receed the the 00:14:22.639 --> 00:14:26.430 align:start position:0% posted in the ler one it receed the the fees<00:14:23.639> that's<00:14:23.880> it<00:14:24.440> super<00:14:24.720> simple<00:14:25.199> so<00:14:25.399> the<00:14:25.560> user 00:14:26.430 --> 00:14:26.440 align:start position:0% fees that's it super simple so the user 00:14:26.440 --> 00:14:29.629 align:start position:0% fees that's it super simple so the user I<00:14:26.519> would<00:14:26.720> say<00:14:26.880> that<00:14:27.120> the<00:14:27.240> user<00:14:28.120> um<00:14:29.160> does<00:14:29.360> not 00:14:29.629 --> 00:14:29.639 align:start position:0% I would say that the user um does not 00:14:29.639 --> 00:14:32.829 align:start position:0% I would say that the user um does not care<00:14:30.079> about<00:14:30.399> that<00:14:31.000> only<00:14:31.399> the<00:14:31.720> sequencer<00:14:32.639> and 00:14:32.829 --> 00:14:32.839 align:start position:0% care about that only the sequencer and 00:14:32.839 --> 00:14:35.509 align:start position:0% care about that only the sequencer and of<00:14:32.959> course<00:14:33.360> this<00:14:33.639> price<00:14:34.279> is<00:14:34.600> splitted<00:14:35.120> among 00:14:35.509 --> 00:14:35.519 align:start position:0% of course this price is splitted among 00:14:35.519 --> 00:14:39.749 align:start position:0% of course this price is splitted among all<00:14:35.720> the<00:14:35.880> transactions<00:14:36.360> in<00:14:36.480> a<00:14:36.959> b<00:14:38.279> but<00:14:39.279> then<00:14:39.639> we 00:14:39.749 --> 00:14:39.759 align:start position:0% all the transactions in a b but then we 00:14:39.759 --> 00:14:42.150 align:start position:0% all the transactions in a b but then we can<00:14:39.959> use<00:14:40.920> uh<00:14:41.120> the<00:14:41.279> next<00:14:41.480> iteration<00:14:41.920> I<00:14:42.000> would 00:14:42.150 --> 00:14:42.160 align:start position:0% can use uh the next iteration I would 00:14:42.160 --> 00:14:45.030 align:start position:0% can use uh the next iteration I would say<00:14:42.360> we<00:14:42.480> can<00:14:42.600> use<00:14:43.120> kind<00:14:43.279> of<00:14:43.440> a<00:14:43.959> dynamic 00:14:45.030 --> 00:14:45.040 align:start position:0% say we can use kind of a dynamic 00:14:45.040 --> 00:14:47.150 align:start position:0% say we can use kind of a dynamic approach<00:14:46.040> the<00:14:46.160> dynamic<00:14:46.560> approach<00:14:46.839> is<00:14:47.000> very 00:14:47.150 --> 00:14:47.160 align:start position:0% approach the dynamic approach is very 00:14:47.160 --> 00:14:48.910 align:start position:0% approach the dynamic approach is very similar<00:14:47.480> to<00:14:47.639> the<00:14:47.759> gas<00:14:48.000> limit<00:14:48.240> on<00:14:48.360> ethereum<00:14:48.720> so 00:14:48.910 --> 00:14:48.920 align:start position:0% similar to the gas limit on ethereum so 00:14:48.920 --> 00:14:52.150 align:start position:0% similar to the gas limit on ethereum so imagine<00:14:49.279> that<00:14:50.000> we<00:14:50.360> introduce<00:14:51.120> here<00:14:51.720> A<00:14:51.880> New 00:14:52.150 --> 00:14:52.160 align:start position:0% imagine that we introduce here A New 00:14:52.160 --> 00:14:54.430 align:start position:0% imagine that we introduce here A New Concept<00:14:52.600> which<00:14:52.720> is<00:14:52.920> kind<00:14:53.120> of<00:14:53.279> the<00:14:53.440> ZK<00:14:53.880> gas<00:14:54.240> and 00:14:54.430 --> 00:14:54.440 align:start position:0% Concept which is kind of the ZK gas and 00:14:54.440 --> 00:14:58.069 align:start position:0% Concept which is kind of the ZK gas and ZK<00:14:54.839> gas<00:14:55.079> limit<00:14:56.079> so<00:14:56.399> the<00:14:56.519> sequencer<00:14:57.279> does<00:14:57.600> not 00:14:58.069 --> 00:14:58.079 align:start position:0% ZK gas limit so the sequencer does not 00:14:58.079 --> 00:15:01.710 align:start position:0% ZK gas limit so the sequencer does not pay<00:14:58.680> for<00:14:58.880> a<00:14:59.240> full<00:14:59.680> badge<00:15:00.680> but<00:15:00.880> the<00:15:01.040> batch<00:15:01.360> is 00:15:01.710 --> 00:15:01.720 align:start position:0% pay for a full badge but the batch is 00:15:01.720 --> 00:15:05.030 align:start position:0% pay for a full badge but the batch is dynamic<00:15:02.600> so<00:15:02.839> it<00:15:02.959> means<00:15:03.360> that<00:15:04.000> basically<00:15:04.880> the 00:15:05.030 --> 00:15:05.040 align:start position:0% dynamic so it means that basically the 00:15:05.040 --> 00:15:09.430 align:start position:0% dynamic so it means that basically the pr<00:15:05.720> can<00:15:06.240> decide<00:15:07.000> the<00:15:07.160> amount<00:15:07.839> of<00:15:08.839> the<00:15:09.079> state 00:15:09.430 --> 00:15:09.440 align:start position:0% pr can decide the amount of the state 00:15:09.440 --> 00:15:13.110 align:start position:0% pr can decide the amount of the state machines<00:15:10.399> that<00:15:11.240> needs<00:15:11.560> to<00:15:11.759> prove<00:15:12.199> basically 00:15:13.110 --> 00:15:13.120 align:start position:0% machines that needs to prove basically 00:15:13.120 --> 00:15:15.670 align:start position:0% machines that needs to prove basically uh<00:15:13.240> we<00:15:13.360> can<00:15:13.519> achieve<00:15:13.880> that<00:15:14.120> via<00:15:14.480> the<00:15:14.839> the<00:15:15.079> bat 00:15:15.670 --> 00:15:15.680 align:start position:0% uh we can achieve that via the the bat 00:15:15.680 --> 00:15:18.150 align:start position:0% uh we can achieve that via the the bat cops<00:15:16.680> and<00:15:16.880> basically<00:15:17.279> here<00:15:17.440> the<00:15:17.560> sequencer 00:15:18.150 --> 00:15:18.160 align:start position:0% cops and basically here the sequencer 00:15:18.160 --> 00:15:21.430 align:start position:0% cops and basically here the sequencer just<00:15:18.680> sets<00:15:19.440> a<00:15:19.720> z<00:15:20.279> gas<00:15:20.519> limit<00:15:20.920> very<00:15:21.279> very 00:15:21.430 --> 00:15:21.440 align:start position:0% just sets a z gas limit very very 00:15:21.440 --> 00:15:24.230 align:start position:0% just sets a z gas limit very very similar<00:15:21.720> to<00:15:21.839> the<00:15:21.959> gas<00:15:22.199> limit<00:15:22.800> which<00:15:23.040> is<00:15:23.279> the<00:15:23.680> Z 00:15:24.230 --> 00:15:24.240 align:start position:0% similar to the gas limit which is the Z 00:15:24.240 --> 00:15:25.710 align:start position:0% similar to the gas limit which is the Z gas<00:15:24.440> that<00:15:24.560> the<00:15:24.639> sequencer<00:15:25.079> is<00:15:25.199> willing<00:15:25.440> to<00:15:25.600> pay 00:15:25.710 --> 00:15:25.720 align:start position:0% gas that the sequencer is willing to pay 00:15:25.720 --> 00:15:27.949 align:start position:0% gas that the sequencer is willing to pay for<00:15:25.880> a<00:15:25.959> bat<00:15:26.680> and<00:15:26.880> then<00:15:27.120> when<00:15:27.240> the<00:15:27.360> verifier 00:15:27.949 --> 00:15:27.959 align:start position:0% for a bat and then when the verifier 00:15:27.959 --> 00:15:30.829 align:start position:0% for a bat and then when the verifier verifies<00:15:28.360> the<00:15:28.519> proof<00:15:29.040> it's<00:15:29.399> substracting<00:15:30.399> gas 00:15:30.829 --> 00:15:30.839 align:start position:0% verifies the proof it's substracting gas 00:15:30.839 --> 00:15:33.910 align:start position:0% verifies the proof it's substracting gas for<00:15:31.120> the<00:15:31.279> gas<00:15:31.519> limit<00:15:32.319> and<00:15:32.480> if<00:15:32.600> it<00:15:32.720> runs<00:15:33.079> out<00:15:33.759> it 00:15:33.910 --> 00:15:33.920 align:start position:0% for the gas limit and if it runs out it 00:15:33.920 --> 00:15:36.430 align:start position:0% for the gas limit and if it runs out it will<00:15:34.079> be<00:15:34.399> kind<00:15:34.560> of<00:15:34.839> a<00:15:35.199> an<00:15:35.360> out<00:15:35.560> of<00:15:35.720> gas<00:15:36.000> but<00:15:36.240> out 00:15:36.430 --> 00:15:36.440 align:start position:0% will be kind of a an out of gas but out 00:15:36.440 --> 00:15:37.629 align:start position:0% will be kind of a an out of gas but out of<00:15:36.680> gas 00:15:37.629 --> 00:15:37.639 align:start position:0% of gas 00:15:37.639 --> 00:15:42.629 align:start position:0% of gas limit<00:15:38.639> so<00:15:38.880> the<00:15:39.000> batch<00:15:39.240> is<00:15:39.440> kind<00:15:39.600> of<00:15:40.079> uh 00:15:42.629 --> 00:15:42.639 align:start position:0% limit so the batch is kind of uh 00:15:42.639 --> 00:15:47.430 align:start position:0% limit so the batch is kind of uh invalid<00:15:43.639> then<00:15:44.040> the<00:15:44.199> next<00:15:44.519> step<00:15:44.880> is<00:15:45.880> okay<00:15:46.440> let's 00:15:47.430 --> 00:15:47.440 align:start position:0% invalid then the next step is okay let's 00:15:47.440 --> 00:15:49.230 align:start position:0% invalid then the next step is okay let's analyze 00:15:49.230 --> 00:15:49.240 align:start position:0% analyze 00:15:49.240 --> 00:15:51.670 align:start position:0% analyze properly<00:15:50.240> in<00:15:50.440> the<00:15:50.680> in<00:15:50.839> the<00:15:50.959> in<00:15:51.079> the<00:15:51.240> language 00:15:51.670 --> 00:15:51.680 align:start position:0% properly in the in the in the language 00:15:51.680 --> 00:15:55.110 align:start position:0% properly in the in the in the language in<00:15:51.800> the<00:15:52.120> compiler<00:15:53.120> why<00:15:53.519> those<00:15:53.920> OP<00:15:54.279> codes<00:15:54.800> are 00:15:55.110 --> 00:15:55.120 align:start position:0% in the compiler why those OP codes are 00:15:55.120 --> 00:15:58.230 align:start position:0% in the compiler why those OP codes are performing<00:15:55.759> so<00:15:56.160> bad<00:15:57.079> and<00:15:57.360> let's<00:15:57.680> try<00:15:57.959> to 00:15:58.230 --> 00:15:58.240 align:start position:0% performing so bad and let's try to 00:15:58.240 --> 00:16:01.590 align:start position:0% performing so bad and let's try to optimize<00:15:59.240> them<00:15:59.759> let's<00:16:00.079> try 00:16:01.590 --> 00:16:01.600 align:start position:0% optimize them let's try 00:16:01.600 --> 00:16:05.150 align:start position:0% optimize them let's try to<00:16:02.600> let's<00:16:02.839> try<00:16:03.040> to<00:16:03.360> iterate<00:16:04.160> let's<00:16:04.360> try<00:16:04.560> to<00:16:04.759> add 00:16:05.150 --> 00:16:05.160 align:start position:0% to let's try to iterate let's try to add 00:16:05.160 --> 00:16:07.910 align:start position:0% to let's try to iterate let's try to add more<00:16:05.480> instructions<00:16:06.319> in<00:16:06.480> order<00:16:07.079> for<00:16:07.440> those<00:16:07.680> of 00:16:07.910 --> 00:16:07.920 align:start position:0% more instructions in order for those of 00:16:07.920 --> 00:16:10.550 align:start position:0% more instructions in order for those of codes<00:16:08.199> to<00:16:08.360> have<00:16:08.519> a<00:16:08.680> better<00:16:08.959> ratio<00:16:09.880> H<00:16:10.000> let's<00:16:10.240> try 00:16:10.550 --> 00:16:10.560 align:start position:0% codes to have a better ratio H let's try 00:16:10.560 --> 00:16:13.949 align:start position:0% codes to have a better ratio H let's try to<00:16:11.240> improve<00:16:12.240> the<00:16:12.440> constraints<00:16:13.240> the<00:16:13.399> pill<00:16:13.839> in 00:16:13.949 --> 00:16:13.959 align:start position:0% to improve the constraints the pill in 00:16:13.959 --> 00:16:16.350 align:start position:0% to improve the constraints the pill in order<00:16:14.160> for<00:16:14.319> those<00:16:14.519> of<00:16:14.720> c<00:16:15.279> those<00:16:15.680> codes<00:16:16.040> to<00:16:16.199> have 00:16:16.350 --> 00:16:16.360 align:start position:0% order for those of c those codes to have 00:16:16.360 --> 00:16:18.749 align:start position:0% order for those of c those codes to have a<00:16:16.880> better<00:16:17.160> ratio<00:16:17.560> and<00:16:17.720> not<00:16:17.920> to<00:16:18.040> be<00:16:18.199> offended<00:16:18.639> on 00:16:18.749 --> 00:16:18.759 align:start position:0% a better ratio and not to be offended on 00:16:18.759 --> 00:16:19.590 align:start position:0% a better ratio and not to be offended on the 00:16:19.590 --> 00:16:19.600 align:start position:0% the 00:16:19.600 --> 00:16:23.309 align:start position:0% the zbm<00:16:20.600> if<00:16:20.839> you<00:16:21.120> want<00:16:21.360> to<00:16:21.519> know<00:16:21.800> more<00:16:22.360> about<00:16:22.680> that 00:16:23.309 --> 00:16:23.319 align:start position:0% zbm if you want to know more about that 00:16:23.319 --> 00:16:26.389 align:start position:0% zbm if you want to know more about that uh<00:16:23.480> tomorrow<00:16:23.959> we<00:16:24.079> will<00:16:24.279> do<00:16:24.480> a<00:16:25.000> workshop<00:16:26.000> at<00:16:26.160> 3 00:16:26.389 --> 00:16:26.399 align:start position:0% uh tomorrow we will do a workshop at 3 00:16:26.399 --> 00:16:28.990 align:start position:0% uh tomorrow we will do a workshop at 3 P.M<00:16:26.680> on<00:16:26.880> classroom<00:16:27.639> uh<00:16:27.800> C<00:16:28.279> it<00:16:28.440> is<00:16:28.639> called 00:16:28.990 --> 00:16:29.000 align:start position:0% P.M on classroom uh C it is called 00:16:29.000 --> 00:16:33.030 align:start position:0% P.M on classroom uh C it is called optimize<00:16:29.519> zbm<00:16:30.000> thut<00:16:30.680> Series<00:16:31.079> 2<00:16:31.560> we<00:16:31.720> did<00:16:31.920> one<00:16:32.279> on 00:16:33.030 --> 00:16:33.040 align:start position:0% optimize zbm thut Series 2 we did one on 00:16:33.040 --> 00:16:35.790 align:start position:0% optimize zbm thut Series 2 we did one on Brussels<00:16:34.040> uh<00:16:34.199> which<00:16:34.319> one<00:16:34.600> the<00:16:34.800> series<00:16:35.199> one<00:16:35.639> was 00:16:35.790 --> 00:16:35.800 align:start position:0% Brussels uh which one the series one was 00:16:35.800 --> 00:16:38.230 align:start position:0% Brussels uh which one the series one was a<00:16:35.920> lot<00:16:36.040> of<00:16:36.160> people<00:16:36.319> over<00:16:36.560> there<00:16:37.199> so<00:16:37.839> uh<00:16:37.920> we're 00:16:38.230 --> 00:16:38.240 align:start position:0% a lot of people over there so uh we're 00:16:38.240 --> 00:16:42.069 align:start position:0% a lot of people over there so uh we're going<00:16:38.600> to<00:16:39.160> explain<00:16:40.160> um<00:16:41.040> some<00:16:41.279> optimizations 00:16:42.069 --> 00:16:42.079 align:start position:0% going to explain um some optimizations 00:16:42.079 --> 00:16:44.309 align:start position:0% going to explain um some optimizations that<00:16:42.240> we<00:16:42.399> did<00:16:42.839> on<00:16:42.959> the<00:16:43.160> Z<00:16:43.480> assembly<00:16:43.880> side<00:16:44.199> and 00:16:44.309 --> 00:16:44.319 align:start position:0% that we did on the Z assembly side and 00:16:44.319 --> 00:16:47.269 align:start position:0% that we did on the Z assembly side and on<00:16:44.440> the<00:16:44.600> compiler<00:16:45.480> in<00:16:45.639> order<00:16:45.880> to<00:16:46.279> optimize 00:16:47.269 --> 00:16:47.279 align:start position:0% on the compiler in order to optimize 00:16:47.279 --> 00:16:50.030 align:start position:0% on the compiler in order to optimize those<00:16:47.880> uh<00:16:48.079> top<00:16:48.480> up 00:16:50.030 --> 00:16:50.040 align:start position:0% those uh top up 00:16:50.040 --> 00:16:53.710 align:start position:0% those uh top up offenders<00:16:51.040> okay<00:16:51.399> thank 00:16:53.710 --> 00:16:53.720 align:start position:0% 00:16:53.720 --> 00:16:56.829 align:start position:0% you<00:16:54.720> amazing<00:16:55.319> great<00:16:55.560> talk<00:16:55.800> Carlos<00:16:56.160> much 00:16:56.829 --> 00:16:56.839 align:start position:0% you amazing great talk Carlos much 00:16:56.839 --> 00:16:59.430 align:start position:0% you amazing great talk Carlos much gracias<00:16:57.839> all<00:16:58.000> right<00:16:58.360> so<00:16:58.880> remember<00:16:59.120> you<00:16:59.240> can 00:16:59.430 --> 00:16:59.440 align:start position:0% gracias all right so remember you can 00:16:59.440 --> 00:17:01.030 align:start position:0% gracias all right so remember you can post<00:16:59.680> your<00:16:59.839> questions<00:17:00.120> on<00:17:00.240> the<00:17:00.360> QR<00:17:00.680> code<00:17:00.920> we're 00:17:01.030 --> 00:17:01.040 align:start position:0% post your questions on the QR code we're 00:17:01.040 --> 00:17:02.590 align:start position:0% post your questions on the QR code we're going<00:17:01.120> to<00:17:01.240> start<00:17:01.560> to<00:17:01.720> hit<00:17:01.959> the<00:17:02.120> first<00:17:02.319> one<00:17:02.480> the 00:17:02.590 --> 00:17:02.600 align:start position:0% going to start to hit the first one the 00:17:02.600 --> 00:17:05.669 align:start position:0% going to start to hit the first one the top<00:17:03.039> one<00:17:04.039> um<00:17:04.360> what<00:17:04.600> happens<00:17:04.880> if<00:17:05.039> the<00:17:05.160> sequencer 00:17:05.669 --> 00:17:05.679 align:start position:0% top one um what happens if the sequencer 00:17:05.679 --> 00:17:07.870 align:start position:0% top one um what happens if the sequencer has<00:17:05.839> a<00:17:06.000> bug<00:17:06.600> and<00:17:06.720> it<00:17:06.919> creates<00:17:07.240> a<00:17:07.360> batch<00:17:07.720> that 00:17:07.870 --> 00:17:07.880 align:start position:0% has a bug and it creates a batch that 00:17:07.880 --> 00:17:09.750 align:start position:0% has a bug and it creates a batch that overflows<00:17:08.400> the<00:17:08.559> counters<00:17:09.079> and<00:17:09.199> then<00:17:09.400> it<00:17:09.559> gets 00:17:09.750 --> 00:17:09.760 align:start position:0% overflows the counters and then it gets 00:17:09.760 --> 00:17:11.870 align:start position:0% overflows the counters and then it gets committed<00:17:10.280> to 00:17:11.870 --> 00:17:11.880 align:start position:0% committed to 00:17:11.880 --> 00:17:15.270 align:start position:0% committed to ethereum<00:17:12.880> yes<00:17:13.199> inside<00:17:13.720> the<00:17:14.160> good<00:17:14.400> question<00:17:14.839> uh 00:17:15.270 --> 00:17:15.280 align:start position:0% ethereum yes inside the good question uh 00:17:15.280 --> 00:17:17.390 align:start position:0% ethereum yes inside the good question uh inside<00:17:15.640> the<00:17:15.760> ROM<00:17:16.319> it<00:17:16.480> can<00:17:16.679> happen<00:17:16.959> two<00:17:17.160> things 00:17:17.390 --> 00:17:17.400 align:start position:0% inside the ROM it can happen two things 00:17:17.400 --> 00:17:19.870 align:start position:0% inside the ROM it can happen two things so<00:17:17.760> inside<00:17:18.079> the<00:17:18.240> RM<00:17:18.839> if<00:17:18.959> the<00:17:19.079> sequencer<00:17:19.600> has<00:17:19.720> a 00:17:19.870 --> 00:17:19.880 align:start position:0% so inside the RM if the sequencer has a 00:17:19.880 --> 00:17:22.710 align:start position:0% so inside the RM if the sequencer has a bu<00:17:20.199> and<00:17:20.559> commits<00:17:21.280> a<00:17:21.439> badge<00:17:21.880> that<00:17:22.120> overflows 00:17:22.710 --> 00:17:22.720 align:start position:0% bu and commits a badge that overflows 00:17:22.720 --> 00:17:25.390 align:start position:0% bu and commits a badge that overflows the<00:17:23.000> counter<00:17:24.000> uh<00:17:24.120> we<00:17:24.280> have<00:17:24.439> a<00:17:24.640> program<00:17:25.120> as<00:17:25.199> I 00:17:25.390 --> 00:17:25.400 align:start position:0% the counter uh we have a program as I 00:17:25.400 --> 00:17:26.949 align:start position:0% the counter uh we have a program as I mentioned<00:17:25.880> which<00:17:26.000> is<00:17:26.160> the<00:17:26.280> ROM<00:17:26.600> which<00:17:26.720> is<00:17:26.799> an 00:17:26.949 --> 00:17:26.959 align:start position:0% mentioned which is the ROM which is an 00:17:26.959 --> 00:17:29.830 align:start position:0% mentioned which is the ROM which is an evm<00:17:27.319> implementation<00:17:28.160> but<00:17:28.360> inside<00:17:28.600> the<00:17:29.280> the<00:17:29.360> ZM 00:17:29.830 --> 00:17:29.840 align:start position:0% evm implementation but inside the the ZM 00:17:29.840 --> 00:17:33.230 align:start position:0% evm implementation but inside the the ZM PR<00:17:30.400> we<00:17:30.679> control<00:17:31.679> the<00:17:31.840> counters<00:17:32.720> uh<00:17:32.880> that<00:17:33.039> are 00:17:33.230 --> 00:17:33.240 align:start position:0% PR we control the counters uh that are 00:17:33.240 --> 00:17:38.070 align:start position:0% PR we control the counters uh that are wasted<00:17:34.120> if<00:17:34.280> you<00:17:34.600> overflow<00:17:35.600> the<00:17:35.799> counters<00:17:37.080> then 00:17:38.070 --> 00:17:38.080 align:start position:0% wasted if you overflow the counters then 00:17:38.080 --> 00:17:40.270 align:start position:0% wasted if you overflow the counters then the<00:17:38.200> prover<00:17:38.640> can<00:17:39.000> prove<00:17:39.320> the<00:17:39.440> batch<00:17:39.919> but<00:17:40.080> it's 00:17:40.270 --> 00:17:40.280 align:start position:0% the prover can prove the batch but it's 00:17:40.280 --> 00:17:41.789 align:start position:0% the prover can prove the batch but it's an<00:17:40.440> invalid<00:17:40.799> batch<00:17:41.160> when<00:17:41.240> I<00:17:41.320> say<00:17:41.480> invalid 00:17:41.789 --> 00:17:41.799 align:start position:0% an invalid batch when I say invalid 00:17:41.799 --> 00:17:43.430 align:start position:0% an invalid batch when I say invalid batch<00:17:42.039> it<00:17:42.120> means<00:17:42.400> that<00:17:42.559> the<00:17:42.640> Old<00:17:42.919> State<00:17:43.120> Route 00:17:43.430 --> 00:17:43.440 align:start position:0% batch it means that the Old State Route 00:17:43.440 --> 00:17:44.990 align:start position:0% batch it means that the Old State Route is<00:17:43.640> equal<00:17:43.880> to<00:17:44.000> the<00:17:44.120> new<00:17:44.360> State<00:17:44.559> Route<00:17:44.760> so<00:17:44.880> there 00:17:44.990 --> 00:17:45.000 align:start position:0% is equal to the new State Route so there 00:17:45.000 --> 00:17:47.430 align:start position:0% is equal to the new State Route so there is<00:17:45.120> no<00:17:45.360> State<00:17:46.280> transition<00:17:46.799> function<00:17:47.160> over 00:17:47.430 --> 00:17:47.440 align:start position:0% is no State transition function over 00:17:47.440 --> 00:17:50.750 align:start position:0% is no State transition function over there<00:17:48.360> the<00:17:48.480> issue<00:17:48.760> is<00:17:49.039> when<00:17:49.160> you<00:17:49.320> have<00:17:49.480> a<00:17:49.760> bug 00:17:50.750 --> 00:17:50.760 align:start position:0% there the issue is when you have a bug 00:17:50.760 --> 00:17:53.590 align:start position:0% there the issue is when you have a bug the<00:17:50.880> sequencer<00:17:51.480> and<00:17:51.600> in<00:17:51.720> the<00:17:52.160> ROM<00:17:53.160> then<00:17:53.400> you 00:17:53.590 --> 00:17:53.600 align:start position:0% the sequencer and in the ROM then you 00:17:53.600 --> 00:17:55.950 align:start position:0% the sequencer and in the ROM then you end<00:17:53.799> up<00:17:54.000> in<00:17:54.080> a<00:17:54.240> situation<00:17:54.720> when<00:17:54.960> you<00:17:55.280> cannot 00:17:55.950 --> 00:17:55.960 align:start position:0% end up in a situation when you cannot 00:17:55.960 --> 00:17:59.029 align:start position:0% end up in a situation when you cannot prove<00:17:56.760> the<00:17:56.919> watch 00:17:59.029 --> 00:17:59.039 align:start position:0% prove the watch 00:17:59.039 --> 00:18:02.350 align:start position:0% prove the watch amazing<00:17:59.640> thanks<00:18:00.640> um<00:18:01.520> the<00:18:01.640> next<00:18:01.840> one<00:18:01.960> is<00:18:02.200> how 00:18:02.350 --> 00:18:02.360 align:start position:0% amazing thanks um the next one is how 00:18:02.360 --> 00:18:05.350 align:start position:0% amazing thanks um the next one is how much<00:18:02.600> does<00:18:03.039> ef<00:18:04.039> help<00:18:04.360> eliminate<00:18:04.840> or<00:18:05.039> reduce 00:18:05.350 --> 00:18:05.360 align:start position:0% much does ef help eliminate or reduce 00:18:05.360 --> 00:18:08.710 align:start position:0% much does ef help eliminate or reduce the<00:18:05.520> top<00:18:05.799> offender<00:18:06.360> up 00:18:08.710 --> 00:18:08.720 align:start position:0% 00:18:08.720 --> 00:18:10.669 align:start position:0% codes 00:18:10.669 --> 00:18:10.679 align:start position:0% codes 00:18:10.679 --> 00:18:14.590 align:start position:0% codes uh<00:18:11.679> I<00:18:11.799> just<00:18:12.000> read<00:18:12.320> once<00:18:12.880> the 00:18:14.590 --> 00:18:14.600 align:start position:0% uh I just read once the 00:18:14.600 --> 00:18:19.510 align:start position:0% uh I just read once the this<00:18:15.600> uh<00:18:16.600> I<00:18:16.679> mean<00:18:17.600> I<00:18:17.720> would<00:18:17.919> say<00:18:18.159> that<00:18:18.720> uh<00:18:19.360> we 00:18:19.510 --> 00:18:19.520 align:start position:0% this uh I mean I would say that uh we 00:18:19.520 --> 00:18:23.990 align:start position:0% this uh I mean I would say that uh we need<00:18:19.679> to<00:18:20.080> analyze<00:18:21.039> uh<00:18:21.400> deeper<00:18:22.400> um<00:18:23.360> what<00:18:23.679> will 00:18:23.990 --> 00:18:24.000 align:start position:0% need to analyze uh deeper um what will 00:18:24.000 --> 00:18:27.470 align:start position:0% need to analyze uh deeper um what will be<00:18:24.280> the<00:18:25.000> top<00:18:25.480> of<00:18:25.679> offenders<00:18:26.520> given<00:18:26.840> the<00:18:27.080> change 00:18:27.470 --> 00:18:27.480 align:start position:0% be the top of offenders given the change 00:18:27.480 --> 00:18:31.230 align:start position:0% be the top of offenders given the change of<00:18:27.799> the<00:18:27.919> B<00:18:28.200> code<00:18:28.520> and<00:18:28.919> e<00:18:29.440> o<00:18:29.760> f<00:18:30.159> basically<00:18:31.080> it's 00:18:31.230 --> 00:18:31.240 align:start position:0% of the B code and e o f basically it's 00:18:31.240 --> 00:18:33.350 align:start position:0% of the B code and e o f basically it's very<00:18:31.559> difficult<00:18:31.640> to<00:18:31.760> answer<00:18:32.440> yeah<00:18:32.640> yeah<00:18:32.840> no<00:18:33.120> I 00:18:33.350 --> 00:18:33.360 align:start position:0% very difficult to answer yeah yeah no I 00:18:33.360 --> 00:18:35.669 align:start position:0% very difficult to answer yeah yeah no I I<00:18:33.520> agree<00:18:33.960> it's<00:18:34.159> coming<00:18:34.520> but<00:18:34.679> it's<00:18:35.080> yeah<00:18:35.320> it<00:18:35.559> it 00:18:35.669 --> 00:18:35.679 align:start position:0% I agree it's coming but it's yeah it it 00:18:35.679 --> 00:18:39.190 align:start position:0% I agree it's coming but it's yeah it it just<00:18:35.799> requires<00:18:36.120> a<00:18:36.200> lot<00:18:36.360> of<00:18:36.480> work<00:18:36.720> and<00:18:37.320> uh<00:18:38.320> yeah 00:18:39.190 --> 00:18:39.200 align:start position:0% just requires a lot of work and uh yeah 00:18:39.200 --> 00:18:41.909 align:start position:0% just requires a lot of work and uh yeah research<00:18:40.200> do<00:18:40.360> you<00:18:40.559> still<00:18:40.880> need<00:18:41.240> counters<00:18:41.799> if 00:18:41.909 --> 00:18:41.919 align:start position:0% research do you still need counters if 00:18:41.919 --> 00:18:43.950 align:start position:0% research do you still need counters if your<00:18:42.120> proving<00:18:42.480> system<00:18:42.760> supports 00:18:43.950 --> 00:18:43.960 align:start position:0% your proving system supports 00:18:43.960 --> 00:18:46.909 align:start position:0% your proving system supports continuations<00:18:44.960> you<00:18:45.120> need<00:18:45.520> counters<00:18:46.520> but<00:18:46.840> I 00:18:46.909 --> 00:18:46.919 align:start position:0% continuations you need counters but I 00:18:46.919 --> 00:18:49.669 align:start position:0% continuations you need counters but I would<00:18:47.120> say<00:18:47.400> that<00:18:47.799> those<00:18:48.320> counters<00:18:48.960> will<00:18:49.240> not 00:18:49.669 --> 00:18:49.679 align:start position:0% would say that those counters will not 00:18:49.679 --> 00:18:51.669 align:start position:0% would say that those counters will not overflow<00:18:50.400> since<00:18:50.679> you<00:18:50.840> can<00:18:51.120> continue<00:18:51.559> the 00:18:51.669 --> 00:18:51.679 align:start position:0% overflow since you can continue the 00:18:51.679 --> 00:18:54.310 align:start position:0% overflow since you can continue the provent<00:18:52.080> execution<00:18:52.559> into<00:18:52.919> another<00:18:53.280> batch<00:18:53.840> so 00:18:54.310 --> 00:18:54.320 align:start position:0% provent execution into another batch so 00:18:54.320 --> 00:18:57.270 align:start position:0% provent execution into another batch so this<00:18:54.520> will<00:18:54.760> mean<00:18:55.120> that<00:18:55.760> basically<00:18:56.760> any 00:18:57.270 --> 00:18:57.280 align:start position:0% this will mean that basically any 00:18:57.280 --> 00:19:00.590 align:start position:0% this will mean that basically any ethereum<00:18:57.840> transaction<00:18:58.799> will<00:18:58.960> be<00:18:59.600> provable 00:19:00.590 --> 00:19:00.600 align:start position:0% ethereum transaction will be provable 00:19:00.600 --> 00:19:03.750 align:start position:0% ethereum transaction will be provable still<00:19:01.600> if<00:19:01.799> you<00:19:01.919> are<00:19:02.320> just<00:19:02.600> doing<00:19:03.000> a<00:19:03.240> loot<00:19:03.640> a 00:19:03.750 --> 00:19:03.760 align:start position:0% still if you are just doing a loot a 00:19:03.760 --> 00:19:05.710 align:start position:0% still if you are just doing a loot a loop<00:19:04.039> of<00:19:04.240> kicks<00:19:04.840> imagine<00:19:05.320> that<00:19:05.480> you're 00:19:05.710 --> 00:19:05.720 align:start position:0% loop of kicks imagine that you're 00:19:05.720 --> 00:19:08.350 align:start position:0% loop of kicks imagine that you're looking<00:19:06.039> a<00:19:06.400> very<00:19:06.960> large<00:19:07.320> loop<00:19:07.640> of<00:19:07.799> kyats<00:19:08.240> and 00:19:08.350 --> 00:19:08.360 align:start position:0% looking a very large loop of kyats and 00:19:08.360 --> 00:19:11.630 align:start position:0% looking a very large loop of kyats and it<00:19:08.480> consumes<00:19:09.200> seven<00:19:09.559> batches<00:19:10.480> that<00:19:10.679> ethereum 00:19:11.630 --> 00:19:11.640 align:start position:0% it consumes seven batches that ethereum 00:19:11.640 --> 00:19:13.230 align:start position:0% it consumes seven batches that ethereum transaction<00:19:12.240> needs<00:19:12.440> to<00:19:12.640> pay<00:19:12.799> the<00:19:12.919> seven 00:19:13.230 --> 00:19:13.240 align:start position:0% transaction needs to pay the seven 00:19:13.240 --> 00:19:15.430 align:start position:0% transaction needs to pay the seven batches<00:19:14.240> but<00:19:14.440> we<00:19:14.520> need<00:19:14.679> to<00:19:14.799> be<00:19:14.960> aware<00:19:15.200> on<00:19:15.320> the 00:19:15.430 --> 00:19:15.440 align:start position:0% batches but we need to be aware on the 00:19:15.440 --> 00:19:16.909 align:start position:0% batches but we need to be aware on the proving<00:19:15.720> system<00:19:16.000> that<00:19:16.120> it's<00:19:16.320> compute<00:19:16.640> seven 00:19:16.909 --> 00:19:16.919 align:start position:0% proving system that it's compute seven 00:19:16.919 --> 00:19:18.430 align:start position:0% proving system that it's compute seven batches<00:19:17.679> I<00:19:17.760> mean<00:19:17.960> thanks<00:19:18.159> to<00:19:18.280> the 00:19:18.430 --> 00:19:18.440 align:start position:0% batches I mean thanks to the 00:19:18.440 --> 00:19:20.710 align:start position:0% batches I mean thanks to the continuation<00:19:19.120> we<00:19:19.240> will<00:19:19.400> be<00:19:19.520> able<00:19:19.760> to<00:19:19.880> prove<00:19:20.080> it 00:19:20.710 --> 00:19:20.720 align:start position:0% continuation we will be able to prove it 00:19:20.720 --> 00:19:22.070 align:start position:0% continuation we will be able to prove it you<00:19:20.840> need<00:19:20.960> to<00:19:21.080> pay<00:19:21.240> for 00:19:22.070 --> 00:19:22.080 align:start position:0% you need to pay for 00:19:22.080 --> 00:19:26.230 align:start position:0% you need to pay for it<00:19:23.080> yep<00:19:23.400> makes<00:19:23.640> sense<00:19:24.480> so<00:19:25.120> uh<00:19:25.320> next<00:19:25.559> is<00:19:25.919> around 00:19:26.230 --> 00:19:26.240 align:start position:0% it yep makes sense so uh next is around 00:19:26.240 --> 00:19:29.549 align:start position:0% it yep makes sense so uh next is around gas<00:19:26.559> cost<00:19:26.960> would<00:19:27.200> multi-dimensional<00:19:28.000> EAP<00:19:28.720> 50 00:19:29.549 --> 00:19:29.559 align:start position:0% gas cost would multi-dimensional EAP 50 00:19:29.559 --> 00:19:31.510 align:start position:0% gas cost would multi-dimensional EAP 50 1559<00:19:30.559> be 00:19:31.510 --> 00:19:31.520 align:start position:0% 1559 be 00:19:31.520 --> 00:19:37.070 align:start position:0% 1559 be useful<00:19:32.520> I<00:19:32.640> would<00:19:32.880> say<00:19:33.559> I<00:19:33.760> I<00:19:33.919> I<00:19:34.000> was<00:19:34.200> in<00:19:34.720> some<00:19:36.080> um 00:19:37.070 --> 00:19:37.080 align:start position:0% useful I would say I I I was in some um 00:19:37.080 --> 00:19:38.789 align:start position:0% useful I would say I I I was in some um meetings<00:19:37.520> discussing<00:19:38.000> about<00:19:38.400> this 00:19:38.789 --> 00:19:38.799 align:start position:0% meetings discussing about this 00:19:38.799 --> 00:19:42.390 align:start position:0% meetings discussing about this multi-dimensional<00:19:39.600> gas<00:19:40.360> pricing<00:19:41.360> and<00:19:42.240> it 00:19:42.390 --> 00:19:42.400 align:start position:0% multi-dimensional gas pricing and it 00:19:42.400 --> 00:19:44.750 align:start position:0% multi-dimensional gas pricing and it could<00:19:42.559> be<00:19:42.720> done<00:19:43.480> but<00:19:43.799> it's<00:19:44.080> not<00:19:44.320> easy<00:19:44.600> to 00:19:44.750 --> 00:19:44.760 align:start position:0% could be done but it's not easy to 00:19:44.760 --> 00:19:48.590 align:start position:0% could be done but it's not easy to modify<00:19:45.799> the<00:19:46.799> whole<00:19:47.400> I<00:19:47.480> mean<00:19:47.720> adding<00:19:48.200> kind<00:19:48.360> of<00:19:48.480> a 00:19:48.590 --> 00:19:48.600 align:start position:0% modify the whole I mean adding kind of a 00:19:48.600 --> 00:19:50.870 align:start position:0% modify the whole I mean adding kind of a new<00:19:48.799> transactions<00:19:49.400> with<00:19:49.640> new<00:19:49.880> fields<00:19:50.720> in 00:19:50.870 --> 00:19:50.880 align:start position:0% new transactions with new fields in 00:19:50.880 --> 00:19:56.070 align:start position:0% new transactions with new fields in order<00:19:51.280> to<00:19:51.520> sign<00:19:52.559> this<00:19:53.559> gas<00:19:54.559> that<00:19:55.559> uh<00:19:55.679> it<00:19:55.880> does 00:19:56.070 --> 00:19:56.080 align:start position:0% order to sign this gas that uh it does 00:19:56.080 --> 00:19:57.830 align:start position:0% order to sign this gas that uh it does not<00:19:56.320> reflect<00:19:56.760> the<00:19:56.880> computation<00:19:57.440> which<00:19:57.559> is<00:19:57.679> the 00:19:57.830 --> 00:19:57.840 align:start position:0% not reflect the computation which is the 00:19:57.840 --> 00:20:00.430 align:start position:0% not reflect the computation which is the gas<00:19:58.200> but<00:19:58.720> gas<00:19:58.919> layer<00:19:59.200> to<00:19:59.480> or<00:19:59.640> ZK<00:20:00.000> gas<00:20:00.200> whatever 00:20:00.430 --> 00:20:00.440 align:start position:0% gas but gas layer to or ZK gas whatever 00:20:00.440 --> 00:20:02.909 align:start position:0% gas but gas layer to or ZK gas whatever you<00:20:00.559> want<00:20:00.679> to<00:20:00.840> call<00:20:01.000> it<00:20:01.720> that<00:20:02.240> uh<00:20:02.400> basically 00:20:02.909 --> 00:20:02.919 align:start position:0% you want to call it that uh basically 00:20:02.919 --> 00:20:07.950 align:start position:0% you want to call it that uh basically reflects<00:20:03.799> the<00:20:04.880> um<00:20:05.880> ZK<00:20:06.320> counters<00:20:06.799> or<00:20:07.080> proving 00:20:07.950 --> 00:20:07.960 align:start position:0% reflects the um ZK counters or proving 00:20:07.960 --> 00:20:09.710 align:start position:0% reflects the um ZK counters or proving computation<00:20:08.960> uh<00:20:09.080> you<00:20:09.159> need<00:20:09.320> to<00:20:09.440> change 00:20:09.710 --> 00:20:09.720 align:start position:0% computation uh you need to change 00:20:09.720 --> 00:20:13.149 align:start position:0% computation uh you need to change libraries<00:20:10.240> you<00:20:10.360> need<00:20:10.520> to<00:20:10.679> change<00:20:11.640> um<00:20:12.440> uxui 00:20:13.149 --> 00:20:13.159 align:start position:0% libraries you need to change um uxui 00:20:13.159 --> 00:20:16.190 align:start position:0% libraries you need to change um uxui metamask<00:20:13.880> this<00:20:13.960> is<00:20:14.080> not<00:20:14.280> easy<00:20:14.919> a<00:20:15.080> chief<00:20:15.960> a<00:20:16.080> lot 00:20:16.190 --> 00:20:16.200 align:start position:0% metamask this is not easy a chief a lot 00:20:16.200 --> 00:20:19.549 align:start position:0% metamask this is not easy a chief a lot of<00:20:16.360> work<00:20:17.080> a<00:20:17.200> lot<00:20:17.360> of<00:20:17.640> work<00:20:18.640> all<00:20:18.799> right<00:20:19.200> how<00:20:19.360> do 00:20:19.549 --> 00:20:19.559 align:start position:0% of work a lot of work all right how do 00:20:19.559 --> 00:20:21.029 align:start position:0% of work a lot of work all right how do upcodes<00:20:20.000> limit<00:20:20.280> work<00:20:20.520> with<00:20:20.640> Force 00:20:21.029 --> 00:20:21.039 align:start position:0% upcodes limit work with Force 00:20:21.039 --> 00:20:22.990 align:start position:0% upcodes limit work with Force transactions<00:20:21.840> and<00:20:22.120> would<00:20:22.280> it<00:20:22.400> be<00:20:22.679> valid 00:20:22.990 --> 00:20:23.000 align:start position:0% transactions and would it be valid 00:20:23.000 --> 00:20:25.350 align:start position:0% transactions and would it be valid reason<00:20:23.320> to<00:20:23.559> exclude 00:20:25.350 --> 00:20:25.360 align:start position:0% reason to exclude 00:20:25.360 --> 00:20:27.909 align:start position:0% reason to exclude transactions<00:20:26.360> I<00:20:26.440> mean<00:20:26.679> first<00:20:27.159> transaction<00:20:27.799> at 00:20:27.909 --> 00:20:27.919 align:start position:0% transactions I mean first transaction at 00:20:27.919 --> 00:20:29.750 align:start position:0% transactions I mean first transaction at the<00:20:28.000> very<00:20:28.159> beginning<00:20:28.440> is<00:20:28.760> just<00:20:29.000> a<00:20:29.320> regular 00:20:29.750 --> 00:20:29.760 align:start position:0% the very beginning is just a regular 00:20:29.760 --> 00:20:32.870 align:start position:0% the very beginning is just a regular transactions<00:20:30.600> but<00:20:30.919> you<00:20:31.440> just<00:20:31.840> bypass<00:20:32.480> the 00:20:32.870 --> 00:20:32.880 align:start position:0% transactions but you just bypass the 00:20:32.880 --> 00:20:35.310 align:start position:0% transactions but you just bypass the sequencer<00:20:33.880> and<00:20:34.080> it<00:20:34.280> works<00:20:34.640> exactly<00:20:35.000> the<00:20:35.120> same 00:20:35.310 --> 00:20:35.320 align:start position:0% sequencer and it works exactly the same 00:20:35.320 --> 00:20:38.710 align:start position:0% sequencer and it works exactly the same that<00:20:35.480> an<00:20:35.720> standard<00:20:36.280> transaction<00:20:37.280> if<00:20:38.080> a<00:20:38.240> force 00:20:38.710 --> 00:20:38.720 align:start position:0% that an standard transaction if a force 00:20:38.720 --> 00:20:40.070 align:start position:0% that an standard transaction if a force transactions 00:20:40.070 --> 00:20:40.080 align:start position:0% transactions 00:20:40.080 --> 00:20:43.830 align:start position:0% transactions overflows<00:20:41.080> the<00:20:41.240> badge<00:20:41.799> which<00:20:42.000> can<00:20:42.200> be<00:20:43.200> and<00:20:43.720> as 00:20:43.830 --> 00:20:43.840 align:start position:0% overflows the badge which can be and as 00:20:43.840 --> 00:20:45.230 align:start position:0% overflows the badge which can be and as I<00:20:43.960> mentioned<00:20:44.280> before<00:20:44.480> in<00:20:44.640> the<00:20:44.760> first<00:20:44.919> question 00:20:45.230 --> 00:20:45.240 align:start position:0% I mentioned before in the first question 00:20:45.240 --> 00:20:47.870 align:start position:0% I mentioned before in the first question the<00:20:45.360> batch<00:20:45.640> will<00:20:45.760> be<00:20:46.000> invalid<00:20:47.000> and<00:20:47.159> that's<00:20:47.360> it 00:20:47.870 --> 00:20:47.880 align:start position:0% the batch will be invalid and that's it 00:20:47.880 --> 00:20:50.350 align:start position:0% the batch will be invalid and that's it so<00:20:48.080> at<00:20:48.200> the<00:20:48.320> very<00:20:48.520> end<00:20:48.760> you<00:20:48.880> are<00:20:49.200> kind<00:20:49.360> of<00:20:50.120> you 00:20:50.350 --> 00:20:50.360 align:start position:0% so at the very end you are kind of you 00:20:50.360 --> 00:20:52.029 align:start position:0% so at the very end you are kind of you want<00:20:50.559> to<00:20:50.679> force<00:20:51.039> your<00:20:51.240> transactions<00:20:51.760> but<00:20:51.919> you 00:20:52.029 --> 00:20:52.039 align:start position:0% want to force your transactions but you 00:20:52.039 --> 00:20:54.110 align:start position:0% want to force your transactions but you are<00:20:52.280> not<00:20:52.640> achieving<00:20:53.360> to<00:20:53.559> execute<00:20:53.919> your 00:20:54.110 --> 00:20:54.120 align:start position:0% are not achieving to execute your 00:20:54.120 --> 00:20:55.350 align:start position:0% are not achieving to execute your transactions<00:20:54.720> because<00:20:54.919> the<00:20:55.039> batch<00:20:55.240> is 00:20:55.350 --> 00:20:55.360 align:start position:0% transactions because the batch is 00:20:55.360 --> 00:20:58.070 align:start position:0% transactions because the batch is invalid<00:20:56.080> so<00:20:56.600> and<00:20:56.799> every<00:20:57.000> time<00:20:57.280> of<00:20:57.400> course<00:20:57.679> that 00:20:58.070 --> 00:20:58.080 align:start position:0% invalid so and every time of course that 00:20:58.080 --> 00:21:01.990 align:start position:0% invalid so and every time of course that uh<00:20:58.640> a<00:20:58.760> user<00:20:59.120> post<00:21:00.159> um<00:21:01.159> a<00:21:01.280> force<00:21:01.600> transaction 00:21:01.990 --> 00:21:02.000 align:start position:0% uh a user post um a force transaction 00:21:02.000 --> 00:21:03.630 align:start position:0% uh a user post um a force transaction into<00:21:02.240> layer<00:21:02.480> one<00:21:02.720> the<00:21:02.799> user<00:21:03.000> needs<00:21:03.200> to<00:21:03.360> pay<00:21:03.520> for 00:21:03.630 --> 00:21:03.640 align:start position:0% into layer one the user needs to pay for 00:21:03.640 --> 00:21:05.310 align:start position:0% into layer one the user needs to pay for it<00:21:03.799> because<00:21:04.000> you<00:21:04.080> are<00:21:04.240> bypassing<00:21:04.640> the 00:21:05.310 --> 00:21:05.320 align:start position:0% it because you are bypassing the 00:21:05.320 --> 00:21:08.430 align:start position:0% it because you are bypassing the sequence<00:21:06.320> right<00:21:06.640> right<00:21:07.600> uh<00:21:07.760> the<00:21:07.880> next<00:21:08.080> one<00:21:08.240> is 00:21:08.430 --> 00:21:08.440 align:start position:0% sequence right right uh the next one is 00:21:08.440 --> 00:21:10.590 align:start position:0% sequence right right uh the next one is are<00:21:08.600> there<00:21:08.799> any<00:21:09.039> steps<00:21:09.480> that<00:21:09.799> smart<00:21:10.159> contract 00:21:10.590 --> 00:21:10.600 align:start position:0% are there any steps that smart contract 00:21:10.600 --> 00:21:13.230 align:start position:0% are there any steps that smart contract developers<00:21:11.200> can<00:21:11.640> already<00:21:12.000> take<00:21:12.679> now<00:21:13.039> to 00:21:13.230 --> 00:21:13.240 align:start position:0% developers can already take now to 00:21:13.240 --> 00:21:16.190 align:start position:0% developers can already take now to reduce<00:21:13.559> the<00:21:13.679> usage<00:21:14.000> of<00:21:14.159> those<00:21:14.559> offending<00:21:15.039> up 00:21:16.190 --> 00:21:16.200 align:start position:0% reduce the usage of those offending up 00:21:16.200 --> 00:21:19.269 align:start position:0% reduce the usage of those offending up coost<00:21:17.200> I<00:21:17.360> would<00:21:18.000> it's<00:21:18.159> very<00:21:18.600> difficult<00:21:18.840> you 00:21:19.269 --> 00:21:19.279 align:start position:0% coost I would it's very difficult you 00:21:19.279 --> 00:21:21.909 align:start position:0% coost I would it's very difficult you would<00:21:19.600> need<00:21:19.919> to<00:21:20.120> go<00:21:20.400> into<00:21:20.799> a<00:21:21.159> assembly<00:21:21.600> code 00:21:21.909 --> 00:21:21.919 align:start position:0% would need to go into a assembly code 00:21:21.919 --> 00:21:25.990 align:start position:0% would need to go into a assembly code otherwise<00:21:22.320> solid<00:21:22.960> just<00:21:23.200> put<00:21:23.919> the<00:21:24.279> op<00:21:25.000> codes 00:21:25.990 --> 00:21:26.000 align:start position:0% otherwise solid just put the op codes 00:21:26.000 --> 00:21:28.870 align:start position:0% otherwise solid just put the op codes most<00:21:26.360> beneficial<00:21:26.960> for<00:21:27.400> execution<00:21:28.000> not<00:21:28.600> not<00:21:28.760> to 00:21:28.870 --> 00:21:28.880 align:start position:0% most beneficial for execution not not to 00:21:28.880 --> 00:21:32.269 align:start position:0% most beneficial for execution not not to take<00:21:29.039> in<00:21:29.200> account<00:21:29.440> the<00:21:29.559> proving<00:21:29.919> system<00:21:31.200> so<00:21:32.200> I 00:21:32.269 --> 00:21:32.279 align:start position:0% take in account the proving system so I 00:21:32.279 --> 00:21:34.470 align:start position:0% take in account the proving system so I would<00:21:32.400> say<00:21:32.520> it's<00:21:32.640> very<00:21:33.000> difficult<00:21:33.679> yeah<00:21:34.360> I 00:21:34.470 --> 00:21:34.480 align:start position:0% would say it's very difficult yeah I 00:21:34.480 --> 00:21:36.870 align:start position:0% would say it's very difficult yeah I guess<00:21:34.600> it<00:21:34.720> would<00:21:34.919> remind<00:21:35.760> require<00:21:36.159> like<00:21:36.679> yeah 00:21:36.870 --> 00:21:36.880 align:start position:0% guess it would remind require like yeah 00:21:36.880 --> 00:21:38.510 align:start position:0% guess it would remind require like yeah reactor<00:21:37.279> architecting<00:21:37.799> the<00:21:37.919> compilers<00:21:38.360> and 00:21:38.510 --> 00:21:38.520 align:start position:0% reactor architecting the compilers and 00:21:38.520 --> 00:21:40.390 align:start position:0% reactor architecting the compilers and doing<00:21:38.679> a<00:21:38.840> bunch<00:21:39.039> of<00:21:39.200> like<00:21:39.360> changes<00:21:39.840> and<00:21:40.000> then 00:21:40.390 --> 00:21:40.400 align:start position:0% doing a bunch of like changes and then 00:21:40.400 --> 00:21:42.510 align:start position:0% doing a bunch of like changes and then yes<00:21:40.760> again<00:21:41.080> yeah<00:21:41.480> yeah<00:21:42.000> really<00:21:42.240> deep 00:21:42.510 --> 00:21:42.520 align:start position:0% yes again yeah yeah really deep 00:21:42.520 --> 00:21:44.870 align:start position:0% yes again yeah yeah really deep knowledge<00:21:42.840> of<00:21:43.039> that<00:21:43.559> are<00:21:43.760> there<00:21:44.000> any<00:21:44.679> this<00:21:44.760> is 00:21:44.870 --> 00:21:44.880 align:start position:0% knowledge of that are there any this is 00:21:44.880 --> 00:21:46.669 align:start position:0% knowledge of that are there any this is the<00:21:45.039> last<00:21:45.200> one<00:21:45.360> are<00:21:45.480> there<00:21:45.640> any<00:21:45.960> concerns<00:21:46.520> with 00:21:46.669 --> 00:21:46.679 align:start position:0% the last one are there any concerns with 00:21:46.679 --> 00:21:48.990 align:start position:0% the last one are there any concerns with the<00:21:46.840> resulting<00:21:47.279> Divergence<00:21:47.919> with<00:21:48.080> L1<00:21:48.520> fees<00:21:48.880> in 00:21:48.990 --> 00:21:49.000 align:start position:0% the resulting Divergence with L1 fees in 00:21:49.000 --> 00:21:50.669 align:start position:0% the resulting Divergence with L1 fees in terms<00:21:49.240> of<00:21:49.400> user 00:21:50.669 --> 00:21:50.679 align:start position:0% terms of user 00:21:50.679 --> 00:21:53.909 align:start position:0% terms of user experience<00:21:51.679> I<00:21:51.760> mean<00:21:52.000> we<00:21:52.159> are<00:21:52.559> achieving<00:21:53.159> an 00:21:53.909 --> 00:21:53.919 align:start position:0% experience I mean we are achieving an 00:21:53.919 --> 00:21:59.149 align:start position:0% experience I mean we are achieving an stage<00:21:55.240> LLY<00:21:56.240> that<00:21:56.799> uh<00:21:57.240> the<00:21:57.520> difference<00:21:58.600> I<00:21:58.679> mean 00:21:59.149 --> 00:21:59.159 align:start position:0% stage LLY that uh the difference I mean 00:21:59.159 --> 00:22:03.669 align:start position:0% stage LLY that uh the difference I mean these<00:22:00.159> proving<00:22:00.840> cost<00:22:02.080> are<00:22:03.080> every<00:22:03.320> time<00:22:03.520> that 00:22:03.669 --> 00:22:03.679 align:start position:0% these proving cost are every time that 00:22:03.679 --> 00:22:05.149 align:start position:0% these proving cost are every time that are<00:22:03.799> cheaper<00:22:04.120> cheaper<00:22:04.440> cheaper<00:22:04.720> cheaper<00:22:05.000> and 00:22:05.149 --> 00:22:05.159 align:start position:0% are cheaper cheaper cheaper cheaper and 00:22:05.159 --> 00:22:09.830 align:start position:0% are cheaper cheaper cheaper cheaper and cheaper<00:22:05.960> so<00:22:06.960> H<00:22:07.159> I<00:22:07.279> would<00:22:07.600> not<00:22:08.039> expect<00:22:09.039> um<00:22:09.480> a<00:22:09.640> lot 00:22:09.830 --> 00:22:09.840 align:start position:0% cheaper so H I would not expect um a lot 00:22:09.840 --> 00:22:12.669 align:start position:0% cheaper so H I would not expect um a lot of<00:22:10.080> Divergence<00:22:10.640> between<00:22:11.000> layer<00:22:11.320> one<00:22:11.559> fees<00:22:12.400> but 00:22:12.669 --> 00:22:12.679 align:start position:0% of Divergence between layer one fees but 00:22:12.679 --> 00:22:15.430 align:start position:0% of Divergence between layer one fees but still<00:22:12.960> the<00:22:13.080> zbm<00:22:13.760> has<00:22:14.360> some<00:22:14.679> mechanism<00:22:15.320> in 00:22:15.430 --> 00:22:15.440 align:start position:0% still the zbm has some mechanism in 00:22:15.440 --> 00:22:17.470 align:start position:0% still the zbm has some mechanism in order<00:22:15.640> to<00:22:15.840> Port<00:22:16.120> layer<00:22:16.400> one<00:22:16.600> fees<00:22:16.960> into<00:22:17.200> Layer 00:22:17.470 --> 00:22:17.480 align:start position:0% order to Port layer one fees into Layer 00:22:17.480 --> 00:22:20.430 align:start position:0% order to Port layer one fees into Layer Two<00:22:18.159> it's<00:22:18.320> the<00:22:18.480> AAP<00:22:18.919> 1559<00:22:19.640> in<00:22:19.760> the<00:22:19.919> base<00:22:20.120> fees 00:22:20.430 --> 00:22:20.440 align:start position:0% Two it's the AAP 1559 in the base fees 00:22:20.440 --> 00:22:22.710 align:start position:0% Two it's the AAP 1559 in the base fees so<00:22:20.679> it<00:22:20.799> can<00:22:21.039> reflect<00:22:21.880> the<00:22:22.000> DAT<00:22:22.159> availability 00:22:22.710 --> 00:22:22.720 align:start position:0% so it can reflect the DAT availability 00:22:22.720 --> 00:22:25.549 align:start position:0% so it can reflect the DAT availability cost<00:22:22.919> on<00:22:23.080> layer<00:22:23.360> one<00:22:24.120> so<00:22:24.720> yeah<00:22:24.919> this<00:22:25.039> is<00:22:25.159> some 00:22:25.549 --> 00:22:25.559 align:start position:0% cost on layer one so yeah this is some 00:22:25.559 --> 00:22:27.070 align:start position:0% cost on layer one so yeah this is some this<00:22:25.679> is<00:22:25.880> just<00:22:26.039> a<00:22:26.240> technique<00:22:26.640> but<00:22:26.840> there<00:22:26.919> are 00:22:27.070 --> 00:22:27.080 align:start position:0% this is just a technique but there are 00:22:27.080 --> 00:22:28.789 align:start position:0% this is just a technique but there are several<00:22:27.400> ones<00:22:27.960> yeah<00:22:28.159> but<00:22:28.240> I<00:22:28.360> guess<00:22:28.640> like 00:22:28.789 --> 00:22:28.799 align:start position:0% several ones yeah but I guess like 00:22:28.799 --> 00:22:30.750 align:start position:0% several ones yeah but I guess like there's<00:22:29.000> a<00:22:29.120> lot<00:22:29.279> of<00:22:29.640> improvements<00:22:30.400> still<00:22:30.679> in 00:22:30.750 --> 00:22:30.760 align:start position:0% there's a lot of improvements still in 00:22:30.760 --> 00:22:32.590 align:start position:0% there's a lot of improvements still in the<00:22:30.880> backlog<00:22:31.279> to<00:22:31.400> keep<00:22:31.559> improving<00:22:31.919> layer<00:22:32.200> twos 00:22:32.590 --> 00:22:32.600 align:start position:0% the backlog to keep improving layer twos 00:22:32.600 --> 00:22:34.669 align:start position:0% the backlog to keep improving layer twos instead<00:22:32.840> of 00:22:34.669 --> 00:22:34.679 align:start position:0% instead of 00:22:34.679 --> 00:22:37.870 align:start position:0% instead of yeah<00:22:35.679> a<00:22:35.760> lot<00:22:35.880> of<00:22:36.159> work<00:22:37.159> uh<00:22:37.320> and<00:22:37.440> I<00:22:37.520> think<00:22:37.679> with 00:22:37.870 --> 00:22:37.880 align:start position:0% yeah a lot of work uh and I think with 00:22:37.880 --> 00:22:39.909 align:start position:0% yeah a lot of work uh and I think with that<00:22:38.039> we<00:22:38.240> complete<00:22:38.720> all<00:22:38.919> the<00:22:39.120> questions<00:22:39.760> thank 00:22:39.909 --> 00:22:39.919 align:start position:0% that we complete all the questions thank 00:22:39.919 --> 00:22:44.480 align:start position:0% that we complete all the questions thank you<00:22:40.000> so<00:22:40.159> much<00:22:40.400> Carlos<00:22:41.120> it's<00:22:41.240> been<00:22:41.360> a<00:22:41.480> pleasure