WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.709 align:start position:0% [Music] 00:00:09.709 --> 00:00:09.719 align:start position:0% [Music] 00:00:09.719 --> 00:00:12.150 align:start position:0% [Music] I'm<00:00:09.880> Ric<00:00:10.320> from<00:00:10.920> from<00:00:11.080> Ipson<00:00:11.679> research<00:00:11.960> and 00:00:12.150 --> 00:00:12.160 align:start position:0% I'm Ric from from Ipson research and 00:00:12.160 --> 00:00:14.430 align:start position:0% I'm Ric from from Ipson research and development<00:00:12.599> team<00:00:12.840> at<00:00:13.000> etherum<00:00:13.440> foundation 00:00:14.430 --> 00:00:14.440 align:start position:0% development team at etherum foundation 00:00:14.440 --> 00:00:16.630 align:start position:0% development team at etherum foundation and<00:00:14.559> today<00:00:14.879> I<00:00:14.960> want<00:00:15.360> to<00:00:15.519> talk<00:00:15.679> to<00:00:15.719> you<00:00:15.839> about 00:00:16.630 --> 00:00:16.640 align:start position:0% and today I want to talk to you about 00:00:16.640 --> 00:00:19.550 align:start position:0% and today I want to talk to you about some<00:00:17.640> uh<00:00:17.880> some<00:00:18.160> extension<00:00:18.800> we<00:00:19.119> we're<00:00:19.240> going<00:00:19.359> to 00:00:19.550 --> 00:00:19.560 align:start position:0% some uh some extension we we're going to 00:00:19.560 --> 00:00:22.230 align:start position:0% some uh some extension we we're going to add<00:00:20.199> to<00:00:20.480> the<00:00:20.720> to<00:00:20.880> the<00:00:21.000> interium<00:00:21.439> virtual 00:00:22.230 --> 00:00:22.240 align:start position:0% add to the to the interium virtual 00:00:22.240 --> 00:00:25.710 align:start position:0% add to the to the interium virtual machine<00:00:23.240> uh<00:00:23.400> in<00:00:23.519> the<00:00:23.640> near<00:00:24.279> future<00:00:25.279> so<00:00:25.599> the 00:00:25.710 --> 00:00:25.720 align:start position:0% machine uh in the near future so the 00:00:25.720 --> 00:00:27.630 align:start position:0% machine uh in the near future so the idea<00:00:26.039> has<00:00:26.160> a<00:00:26.279> couple<00:00:26.519> of<00:00:26.679> years<00:00:27.039> already<00:00:27.519> and 00:00:27.630 --> 00:00:27.640 align:start position:0% idea has a couple of years already and 00:00:27.640 --> 00:00:30.749 align:start position:0% idea has a couple of years already and it<00:00:27.800> was<00:00:28.199> initiated<00:00:28.840> by<00:00:29.080> some<00:00:29.400> cevs 00:00:30.749 --> 00:00:30.759 align:start position:0% it was initiated by some cevs 00:00:30.759 --> 00:00:34.670 align:start position:0% it was initiated by some cevs to<00:00:31.759> uh<00:00:32.360> to<00:00:32.759> improve<00:00:33.200> the<00:00:33.360> way<00:00:33.680> how<00:00:34.160> the 00:00:34.670 --> 00:00:34.680 align:start position:0% to uh to improve the way how the 00:00:34.680 --> 00:00:37.110 align:start position:0% to uh to improve the way how the cryptography<00:00:35.680> is<00:00:35.920> handled<00:00:36.360> or<00:00:36.520> cryptography 00:00:37.110 --> 00:00:37.120 align:start position:0% cryptography is handled or cryptography 00:00:37.120 --> 00:00:39.389 align:start position:0% cryptography is handled or cryptography related<00:00:37.480> functions<00:00:37.800> are<00:00:38.079> handled<00:00:38.680> on<00:00:38.920> the<00:00:39.239> in 00:00:39.389 --> 00:00:39.399 align:start position:0% related functions are handled on the in 00:00:39.399 --> 00:00:42.549 align:start position:0% related functions are handled on the in the<00:00:39.559> in<00:00:39.640> the<00:00:40.079> evm<00:00:41.079> the<00:00:41.200> main<00:00:41.440> reason<00:00:41.760> was<00:00:41.960> to 00:00:42.549 --> 00:00:42.559 align:start position:0% the in the evm the main reason was to 00:00:42.559 --> 00:00:45.670 align:start position:0% the in the evm the main reason was to avoid<00:00:43.399> adding<00:00:44.000> or<00:00:44.239> limit<00:00:44.760> limit<00:00:45.079> the<00:00:45.239> need<00:00:45.520> to 00:00:45.670 --> 00:00:45.680 align:start position:0% avoid adding or limit limit the need to 00:00:45.680 --> 00:00:48.990 align:start position:0% avoid adding or limit limit the need to adding<00:00:46.039> new 00:00:48.990 --> 00:00:49.000 align:start position:0% 00:00:49.000 --> 00:00:51.229 align:start position:0% promiles<00:00:50.000> yes<00:00:50.160> so<00:00:50.360> but<00:00:50.520> before<00:00:50.719> we<00:00:50.879> get<00:00:51.039> into 00:00:51.229 --> 00:00:51.239 align:start position:0% promiles yes so but before we get into 00:00:51.239 --> 00:00:53.229 align:start position:0% promiles yes so but before we get into the<00:00:51.360> details<00:00:51.800> I<00:00:51.879> would<00:00:52.079> like<00:00:52.280> to<00:00:52.760> make<00:00:53.000> some 00:00:53.229 --> 00:00:53.239 align:start position:0% the details I would like to make some 00:00:53.239 --> 00:00:55.229 align:start position:0% the details I would like to make some simple<00:00:53.600> introduction<00:00:54.160> and<00:00:54.399> explain<00:00:55.120> the 00:00:55.229 --> 00:00:55.239 align:start position:0% simple introduction and explain the 00:00:55.239 --> 00:00:58.069 align:start position:0% simple introduction and explain the reasoning<00:00:55.800> behind<00:00:56.239> evm 00:00:58.069 --> 00:00:58.079 align:start position:0% reasoning behind evm 00:00:58.079 --> 00:01:01.509 align:start position:0% reasoning behind evm Max<00:00:59.079> so<00:00:59.320> what's<00:00:59.519> the<00:00:59.600> evm<00:01:00.079> Max<00:01:00.760> so<00:01:00.960> evm<00:01:01.280> max 00:01:01.509 --> 00:01:01.519 align:start position:0% Max so what's the evm Max so evm max 00:01:01.519 --> 00:01:03.869 align:start position:0% Max so what's the evm Max so evm max translates<00:01:02.039> to<00:01:02.359> EV<00:01:02.760> interium<00:01:03.359> virtual 00:01:03.869 --> 00:01:03.879 align:start position:0% translates to EV interium virtual 00:01:03.879 --> 00:01:07.190 align:start position:0% translates to EV interium virtual machine<00:01:04.879> modular<00:01:05.439> arithmetic<00:01:06.200> extension 00:01:07.190 --> 00:01:07.200 align:start position:0% machine modular arithmetic extension 00:01:07.200 --> 00:01:08.950 align:start position:0% machine modular arithmetic extension it's<00:01:07.320> a<00:01:07.479> set<00:01:07.640> of<00:01:07.759> modular<00:01:08.320> set<00:01:08.479> of<00:01:08.600> the<00:01:08.759> new 00:01:08.950 --> 00:01:08.960 align:start position:0% it's a set of modular set of the new 00:01:08.960 --> 00:01:11.149 align:start position:0% it's a set of modular set of the new modular<00:01:09.400> arithmetic<00:01:09.960> instructions<00:01:10.920> which 00:01:11.149 --> 00:01:11.159 align:start position:0% modular arithmetic instructions which 00:01:11.159 --> 00:01:15.390 align:start position:0% modular arithmetic instructions which support<00:01:12.159> every<00:01:12.600> sized<00:01:13.119> C<00:01:14.119> which<00:01:14.240> is<00:01:14.439> important 00:01:15.390 --> 00:01:15.400 align:start position:0% support every sized C which is important 00:01:15.400 --> 00:01:18.550 align:start position:0% support every sized C which is important old<00:01:16.040> modules<00:01:17.040> at<00:01:17.240> the<00:01:17.400> current<00:01:17.720> spec<00:01:18.360> we 00:01:18.550 --> 00:01:18.560 align:start position:0% old modules at the current spec we 00:01:18.560 --> 00:01:21.789 align:start position:0% old modules at the current spec we Define<00:01:19.520> uh<00:01:19.720> addition<00:01:20.799> subtractions 00:01:21.789 --> 00:01:21.799 align:start position:0% Define uh addition subtractions 00:01:21.799 --> 00:01:24.510 align:start position:0% Define uh addition subtractions subtractions<00:01:22.680> and<00:01:22.920> multiplication<00:01:23.759> we<00:01:24.000> also 00:01:24.510 --> 00:01:24.520 align:start position:0% subtractions and multiplication we also 00:01:24.520 --> 00:01:25.950 align:start position:0% subtractions and multiplication we also consider<00:01:25.000> adding 00:01:25.950 --> 00:01:25.960 align:start position:0% consider adding 00:01:25.960 --> 00:01:28.390 align:start position:0% consider adding exponentiation<00:01:26.960> which<00:01:27.079> is<00:01:27.200> a<00:01:27.360> helpful<00:01:28.079> uh<00:01:28.159> for 00:01:28.390 --> 00:01:28.400 align:start position:0% exponentiation which is a helpful uh for 00:01:28.400 --> 00:01:30.469 align:start position:0% exponentiation which is a helpful uh for calculation<00:01:28.960> some<00:01:29.159> more<00:01:29.400> advanced<00:01:30.360> uh 00:01:30.469 --> 00:01:30.479 align:start position:0% calculation some more advanced uh 00:01:30.479 --> 00:01:32.469 align:start position:0% calculation some more advanced uh modular<00:01:30.880> arithmetic<00:01:31.400> functions<00:01:31.960> like 00:01:32.469 --> 00:01:32.479 align:start position:0% modular arithmetic functions like 00:01:32.479 --> 00:01:35.789 align:start position:0% modular arithmetic functions like modular<00:01:32.920> inversion<00:01:33.520> or<00:01:33.759> square<00:01:34.560> root<00:01:35.560> one 00:01:35.789 --> 00:01:35.799 align:start position:0% modular inversion or square root one 00:01:35.799 --> 00:01:39.109 align:start position:0% modular inversion or square root one every<00:01:36.079> important<00:01:36.560> thing<00:01:37.320> uh<00:01:37.759> uh<00:01:38.320> which<00:01:38.920> should 00:01:39.109 --> 00:01:39.119 align:start position:0% every important thing uh uh which should 00:01:39.119 --> 00:01:42.550 align:start position:0% every important thing uh uh which should be<00:01:39.280> noticed<00:01:39.799> is<00:01:40.240> here<00:01:41.159> is<00:01:41.759> uh<00:01:42.040> that<00:01:42.200> in<00:01:42.360> this 00:01:42.550 --> 00:01:42.560 align:start position:0% be noticed is here is uh that in this 00:01:42.560 --> 00:01:44.469 align:start position:0% be noticed is here is uh that in this proposal<00:01:43.119> that<00:01:43.320> this<00:01:43.479> proposal<00:01:43.920> is<00:01:44.040> built<00:01:44.360> on 00:01:44.469 --> 00:01:44.479 align:start position:0% proposal that this proposal is built on 00:01:44.479 --> 00:01:47.030 align:start position:0% proposal that this proposal is built on the<00:01:44.719> top<00:01:45.040> of<00:01:45.200> the<00:01:45.399> evm<00:01:45.920> object<00:01:46.280> format<00:01:46.759> which 00:01:47.030 --> 00:01:47.040 align:start position:0% the top of the evm object format which 00:01:47.040 --> 00:01:49.749 align:start position:0% the top of the evm object format which we<00:01:47.240> had<00:01:47.600> just<00:01:47.759> a<00:01:47.960> presentation<00:01:48.520> of<00:01:49.399> uh<00:01:49.520> in<00:01:49.640> a 00:01:49.749 --> 00:01:49.759 align:start position:0% we had just a presentation of uh in a 00:01:49.759 --> 00:01:51.270 align:start position:0% we had just a presentation of uh in a minute<00:01:50.119> and<00:01:50.320> also<00:01:50.600> there<00:01:50.719> was<00:01:51.000> one 00:01:51.270 --> 00:01:51.280 align:start position:0% minute and also there was one 00:01:51.280 --> 00:01:55.230 align:start position:0% minute and also there was one presentation<00:01:52.240> made<00:01:52.560> by<00:01:52.759> Dano<00:01:53.759> uh<00:01:54.280> on 00:01:55.230 --> 00:01:55.240 align:start position:0% presentation made by Dano uh on 00:01:55.240 --> 00:02:00.429 align:start position:0% presentation made by Dano uh on Tuesday<00:01:56.240> uh<00:01:56.920> so<00:01:57.920> um<00:01:58.880> yeah<00:01:59.039> so<00:01:59.159> evm<00:01:59.560> max<00:02:00.000> makes<00:02:00.280> a 00:02:00.429 --> 00:02:00.439 align:start position:0% Tuesday uh so um yeah so evm max makes a 00:02:00.439 --> 00:02:04.029 align:start position:0% Tuesday uh so um yeah so evm max makes a usage<00:02:00.759> of<00:02:01.000> e<00:02:01.640> eof<00:02:02.039> immediate<00:02:02.880> arguments<00:02:03.880> and 00:02:04.029 --> 00:02:04.039 align:start position:0% usage of e eof immediate arguments and 00:02:04.039 --> 00:02:05.950 align:start position:0% usage of e eof immediate arguments and the<00:02:04.240> validation<00:02:04.960> of<00:02:05.119> the<00:02:05.240> immediate<00:02:05.680> bite 00:02:05.950 --> 00:02:05.960 align:start position:0% the validation of the immediate bite 00:02:05.960 --> 00:02:09.589 align:start position:0% the validation of the immediate bite code<00:02:06.560> also<00:02:07.560> and<00:02:07.719> it<00:02:07.920> makes<00:02:08.560> uh<00:02:08.759> it<00:02:09.039> possible<00:02:09.399> to 00:02:09.589 --> 00:02:09.599 align:start position:0% code also and it makes uh it possible to 00:02:09.599 --> 00:02:13.670 align:start position:0% code also and it makes uh it possible to validate<00:02:10.080> evm<00:02:10.520> Max<00:02:11.120> code<00:02:12.120> before<00:02:13.120> before<00:02:13.480> the 00:02:13.670 --> 00:02:13.680 align:start position:0% validate evm Max code before before the 00:02:13.680 --> 00:02:15.910 align:start position:0% validate evm Max code before before the deployment<00:02:14.200> of<00:02:14.319> the<00:02:14.440> contract<00:02:14.840> to<00:02:15.040> the<00:02:15.160> to<00:02:15.280> the 00:02:15.910 --> 00:02:15.920 align:start position:0% deployment of the contract to the to the 00:02:15.920 --> 00:02:19.509 align:start position:0% deployment of the contract to the to the chain<00:02:16.959> um<00:02:17.959> but<00:02:18.120> I'm<00:02:18.280> not<00:02:18.480> going<00:02:18.680> to<00:02:18.879> get<00:02:19.080> into 00:02:19.509 --> 00:02:19.519 align:start position:0% chain um but I'm not going to get into 00:02:19.519 --> 00:02:21.350 align:start position:0% chain um but I'm not going to get into details<00:02:19.959> of<00:02:20.200> the<00:02:20.400> of<00:02:20.519> this<00:02:20.720> validation 00:02:21.350 --> 00:02:21.360 align:start position:0% details of the of this validation 00:02:21.360 --> 00:02:23.670 align:start position:0% details of the of this validation because<00:02:21.599> it's<00:02:21.760> not<00:02:22.080> the<00:02:22.440> the<00:02:22.959> the<00:02:23.080> main<00:02:23.400> topic 00:02:23.670 --> 00:02:23.680 align:start position:0% because it's not the the the main topic 00:02:23.680 --> 00:02:27.070 align:start position:0% because it's not the the the main topic of<00:02:23.920> this<00:02:24.440> uh<00:02:24.640> of<00:02:24.879> this<00:02:25.360> uh<00:02:25.879> presentation<00:02:26.879> yeah 00:02:27.070 --> 00:02:27.080 align:start position:0% of this uh of this uh presentation yeah 00:02:27.080 --> 00:02:29.350 align:start position:0% of this uh of this uh presentation yeah but<00:02:27.200> it's<00:02:27.360> worth<00:02:27.680> mentioning<00:02:28.280> that<00:02:28.720> uh<00:02:28.840> eof<00:02:29.280> is 00:02:29.350 --> 00:02:29.360 align:start position:0% but it's worth mentioning that uh eof is 00:02:29.360 --> 00:02:31.949 align:start position:0% but it's worth mentioning that uh eof is a<00:02:29.519> crucial<00:02:30.040> dependency<00:02:30.800> which<00:02:30.959> makes<00:02:31.239> evm<00:02:31.640> Max 00:02:31.949 --> 00:02:31.959 align:start position:0% a crucial dependency which makes evm Max 00:02:31.959 --> 00:02:35.270 align:start position:0% a crucial dependency which makes evm Max easier<00:02:32.840> to<00:02:33.120> implement<00:02:34.080> in<00:02:34.239> an<00:02:34.480> efficient<00:02:34.920> way 00:02:35.270 --> 00:02:35.280 align:start position:0% easier to implement in an efficient way 00:02:35.280 --> 00:02:38.710 align:start position:0% easier to implement in an efficient way it<00:02:35.440> doesn't<00:02:35.720> mean<00:02:35.920> that<00:02:36.160> EV<00:02:36.599> eof<00:02:37.160> is<00:02:38.160> uh<00:02:38.400> is<00:02:38.519> a 00:02:38.710 --> 00:02:38.720 align:start position:0% it doesn't mean that EV eof is uh is a 00:02:38.720 --> 00:02:40.990 align:start position:0% it doesn't mean that EV eof is uh is a dependency<00:02:39.280> which<00:02:39.480> has<00:02:39.640> to<00:02:39.800> be<00:02:40.120> before<00:02:40.640> it 00:02:40.990 --> 00:02:41.000 align:start position:0% dependency which has to be before it 00:02:41.000 --> 00:02:42.830 align:start position:0% dependency which has to be before it just<00:02:41.200> makes<00:02:41.519> the<00:02:41.640> implementation<00:02:42.200> tvx<00:02:42.640> much 00:02:42.830 --> 00:02:42.840 align:start position:0% just makes the implementation tvx much 00:02:42.840 --> 00:02:46.550 align:start position:0% just makes the implementation tvx much easier<00:02:43.159> in<00:02:43.280> an<00:02:43.440> efficient<00:02:44.080> way<00:02:45.080> so<00:02:45.680> but<00:02:46.319> where 00:02:46.550 --> 00:02:46.560 align:start position:0% easier in an efficient way so but where 00:02:46.560 --> 00:02:49.070 align:start position:0% easier in an efficient way so but where exactly<00:02:46.959> evm<00:02:47.360> Max<00:02:47.599> is<00:02:47.760> located<00:02:48.319> in<00:02:48.519> the<00:02:48.840> in<00:02:48.959> the 00:02:49.070 --> 00:02:49.080 align:start position:0% exactly evm Max is located in the in the 00:02:49.080 --> 00:02:53.589 align:start position:0% exactly evm Max is located in the in the crypto<00:02:49.640> graphy<00:02:50.280> related<00:02:51.280> uh<00:02:51.560> evm<00:02:52.239> evm<00:02:52.680> stack 00:02:53.589 --> 00:02:53.599 align:start position:0% crypto graphy related uh evm evm stack 00:02:53.599 --> 00:02:55.430 align:start position:0% crypto graphy related uh evm evm stack so<00:02:53.800> we<00:02:53.959> have<00:02:54.080> a<00:02:54.280> basic<00:02:54.640> operations<00:02:55.239> in<00:02:55.319> the 00:02:55.430 --> 00:02:55.440 align:start position:0% so we have a basic operations in the 00:02:55.440 --> 00:02:57.350 align:start position:0% so we have a basic operations in the modular<00:02:55.840> arithmetic<00:02:56.440> on<00:02:56.599> the<00:02:56.720> on<00:02:56.840> the<00:02:57.000> bottom 00:02:57.350 --> 00:02:57.360 align:start position:0% modular arithmetic on the on the bottom 00:02:57.360 --> 00:02:59.430 align:start position:0% modular arithmetic on the on the bottom level<00:02:58.200> which<00:02:58.319> are<00:02:58.480> used<00:02:58.760> to<00:02:58.879> implement<00:02:59.280> the 00:02:59.430 --> 00:02:59.440 align:start position:0% level which are used to implement the 00:02:59.440 --> 00:03:02.309 align:start position:0% level which are used to implement the second<00:03:00.239> level<00:03:01.239> uh<00:03:01.360> the<00:03:01.480> elliptic<00:03:01.959> curve 00:03:02.309 --> 00:03:02.319 align:start position:0% second level uh the elliptic curve 00:03:02.319 --> 00:03:04.550 align:start position:0% second level uh the elliptic curve cryptography<00:03:03.319> Primitives<00:03:04.000> like<00:03:04.239> Point 00:03:04.550 --> 00:03:04.560 align:start position:0% cryptography Primitives like Point 00:03:04.560 --> 00:03:07.910 align:start position:0% cryptography Primitives like Point addition<00:03:05.840> multiplication<00:03:06.840> and<00:03:07.080> sometime<00:03:07.680> and 00:03:07.910 --> 00:03:07.920 align:start position:0% addition multiplication and sometime and 00:03:07.920 --> 00:03:10.190 align:start position:0% addition multiplication and sometime and and<00:03:08.120> more<00:03:08.360> advanced<00:03:08.840> like<00:03:09.159> piring 00:03:10.190 --> 00:03:10.200 align:start position:0% and more advanced like piring 00:03:10.200 --> 00:03:12.670 align:start position:0% and more advanced like piring verification<00:03:11.200> and<00:03:11.440> these<00:03:11.720> Primitives<00:03:12.480> are 00:03:12.670 --> 00:03:12.680 align:start position:0% verification and these Primitives are 00:03:12.680 --> 00:03:14.670 align:start position:0% verification and these Primitives are used<00:03:13.000> to<00:03:13.200> implement 00:03:14.670 --> 00:03:14.680 align:start position:0% used to implement 00:03:14.680 --> 00:03:17.750 align:start position:0% used to implement ECC<00:03:15.680> uh<00:03:16.360> algorith<00:03:16.959> like<00:03:17.159> signature 00:03:17.750 --> 00:03:17.760 align:start position:0% ECC uh algorith like signature 00:03:17.760 --> 00:03:20.789 align:start position:0% ECC uh algorith like signature verification<00:03:18.760> and<00:03:18.920> ziker<00:03:19.360> related<00:03:19.799> functions 00:03:20.789 --> 00:03:20.799 align:start position:0% verification and ziker related functions 00:03:20.799 --> 00:03:24.589 align:start position:0% verification and ziker related functions but<00:03:21.000> evm<00:03:21.360> Max<00:03:21.640> implements<00:03:22.680> only<00:03:23.680> the<00:03:24.200> bottom 00:03:24.589 --> 00:03:24.599 align:start position:0% but evm Max implements only the bottom 00:03:24.599 --> 00:03:27.710 align:start position:0% but evm Max implements only the bottom one<00:03:25.120> level<00:03:25.560> of<00:03:25.680> on<00:03:25.879> this<00:03:26.080> diagram<00:03:27.080> the<00:03:27.360> Epsilon 00:03:27.710 --> 00:03:27.720 align:start position:0% one level of on this diagram the Epsilon 00:03:27.720 --> 00:03:31.309 align:start position:0% one level of on this diagram the Epsilon team<00:03:28.000> we<00:03:28.519> also<00:03:29.519> uh<00:03:29.879> use<00:03:30.159> evm<00:03:30.519> max<00:03:30.799> to<00:03:30.920> implement 00:03:31.309 --> 00:03:31.319 align:start position:0% team we also uh use evm max to implement 00:03:31.319 --> 00:03:33.390 align:start position:0% team we also uh use evm max to implement the<00:03:31.519> second<00:03:31.879> level<00:03:32.439> to<00:03:32.640> make<00:03:32.840> sure<00:03:33.159> that<00:03:33.280> the 00:03:33.390 --> 00:03:33.400 align:start position:0% the second level to make sure that the 00:03:33.400 --> 00:03:37.390 align:start position:0% the second level to make sure that the set<00:03:33.599> of<00:03:33.760> instruction<00:03:34.239> of<00:03:34.360> evm<00:03:34.760> Max<00:03:35.560> is<00:03:36.400> offer 00:03:37.390 --> 00:03:37.400 align:start position:0% set of instruction of evm Max is offer 00:03:37.400 --> 00:03:40.509 align:start position:0% set of instruction of evm Max is offer the<00:03:37.920> and<00:03:38.080> the<00:03:38.200> API<00:03:38.840> offer<00:03:39.840> uh<00:03:40.120> right 00:03:40.509 --> 00:03:40.519 align:start position:0% the and the API offer uh right 00:03:40.519 --> 00:03:43.789 align:start position:0% the and the API offer uh right abstractions<00:03:41.519> right<00:03:41.760> abstraction<00:03:42.200> and 00:03:43.789 --> 00:03:43.799 align:start position:0% abstractions right abstraction and 00:03:43.799 --> 00:03:47.229 align:start position:0% abstractions right abstraction and efficiency<00:03:44.799> so<00:03:45.599> um 00:03:47.229 --> 00:03:47.239 align:start position:0% efficiency so um 00:03:47.239 --> 00:03:52.030 align:start position:0% efficiency so um sorry<00:03:48.239> too<00:03:49.000> fast<00:03:50.000> what<00:03:50.080> is<00:03:50.280> going<00:03:50.720> on<00:03:51.720> yeah 00:03:52.030 --> 00:03:52.040 align:start position:0% sorry too fast what is going on yeah 00:03:52.040 --> 00:03:55.429 align:start position:0% sorry too fast what is going on yeah okay<00:03:52.599> so<00:03:52.879> we<00:03:53.040> know<00:03:53.599> uh<00:03:54.159> we<00:03:54.319> now<00:03:54.519> know<00:03:54.760> what<00:03:55.040> evm 00:03:55.429 --> 00:03:55.439 align:start position:0% okay so we know uh we now know what evm 00:03:55.439 --> 00:03:56.630 align:start position:0% okay so we know uh we now know what evm Max<00:03:55.680> is<00:03:55.840> in 00:03:56.630 --> 00:03:56.640 align:start position:0% Max is in 00:03:56.640 --> 00:03:58.390 align:start position:0% Max is in general 00:03:58.390 --> 00:03:58.400 align:start position:0% general 00:03:58.400 --> 00:03:59.830 align:start position:0% general um<00:03:59.400> some 00:03:59.830 --> 00:03:59.840 align:start position:0% um some 00:03:59.840 --> 00:04:00.949 align:start position:0% um some [Music] 00:04:00.949 --> 00:04:00.959 align:start position:0% [Music] 00:04:00.959 --> 00:04:02.509 align:start position:0% [Music] so<00:04:01.200> one<00:04:01.319> of<00:04:01.439> the<00:04:01.560> reason<00:04:01.840> I<00:04:01.959> already<00:04:02.200> mentioned 00:04:02.509 --> 00:04:02.519 align:start position:0% so one of the reason I already mentioned 00:04:02.519 --> 00:04:04.589 align:start position:0% so one of the reason I already mentioned at<00:04:02.599> the<00:04:02.680> beginning<00:04:02.959> of<00:04:03.079> the<00:04:03.360> presentation<00:04:04.360> but 00:04:04.589 --> 00:04:04.599 align:start position:0% at the beginning of the presentation but 00:04:04.599 --> 00:04:06.390 align:start position:0% at the beginning of the presentation but there<00:04:04.720> are<00:04:05.239> a<00:04:05.360> couple<00:04:05.640> more<00:04:05.840> reasons<00:04:06.159> I<00:04:06.280> want 00:04:06.390 --> 00:04:06.400 align:start position:0% there are a couple more reasons I want 00:04:06.400 --> 00:04:08.990 align:start position:0% there are a couple more reasons I want to<00:04:06.599> list<00:04:07.519> so<00:04:07.879> in<00:04:08.040> etherian<00:04:08.480> community<00:04:08.920> there 00:04:08.990 --> 00:04:09.000 align:start position:0% to list so in etherian community there 00:04:09.000 --> 00:04:10.830 align:start position:0% to list so in etherian community there is<00:04:09.120> a<00:04:09.239> need<00:04:09.439> to<00:04:09.599> make<00:04:09.799> the<00:04:09.920> implementation<00:04:10.720> of 00:04:10.830 --> 00:04:10.840 align:start position:0% is a need to make the implementation of 00:04:10.840 --> 00:04:14.149 align:start position:0% is a need to make the implementation of the<00:04:11.319> cryptography<00:04:12.319> uh<00:04:12.439> in<00:04:12.599> evm<00:04:13.400> much<00:04:13.640> easier 00:04:14.149 --> 00:04:14.159 align:start position:0% the cryptography uh in evm much easier 00:04:14.159 --> 00:04:15.069 align:start position:0% the cryptography uh in evm much easier and 00:04:15.069 --> 00:04:15.079 align:start position:0% and 00:04:15.079 --> 00:04:16.749 align:start position:0% and efficient 00:04:16.749 --> 00:04:16.759 align:start position:0% efficient 00:04:16.759 --> 00:04:23.230 align:start position:0% efficient get<00:04:17.759> uh<00:04:17.919> me<00:04:18.359> in<00:04:18.600> efficient<00:04:19.600> uh 00:04:23.230 --> 00:04:23.240 align:start position:0% 00:04:23.240 --> 00:04:26.909 align:start position:0% so<00:04:24.240> yeah<00:04:24.720> so<00:04:25.160> with<00:04:25.360> VX<00:04:25.880> we<00:04:26.000> won't<00:04:26.280> need<00:04:26.479> to<00:04:26.680> wait 00:04:26.909 --> 00:04:26.919 align:start position:0% so yeah so with VX we won't need to wait 00:04:26.919 --> 00:04:29.749 align:start position:0% so yeah so with VX we won't need to wait for<00:04:27.120> a<00:04:27.360> specific<00:04:28.040> uh<00:04:28.199> promiles<00:04:28.880> to<00:04:29.039> be<00:04:29.560> okay 00:04:29.749 --> 00:04:29.759 align:start position:0% for a specific uh promiles to be okay 00:04:29.759 --> 00:04:30.710 align:start position:0% for a specific uh promiles to be okay okay<00:04:29.919> thank 00:04:30.710 --> 00:04:30.720 align:start position:0% okay thank 00:04:30.720 --> 00:04:33.830 align:start position:0% okay thank you<00:04:31.720> to<00:04:31.880> be<00:04:32.039> delivered<00:04:32.520> in<00:04:32.680> a<00:04:32.880> in<00:04:32.960> a<00:04:33.120> fork<00:04:33.680> we 00:04:33.830 --> 00:04:33.840 align:start position:0% you to be delivered in a in a fork we 00:04:33.840 --> 00:04:35.590 align:start position:0% you to be delivered in a in a fork we also<00:04:34.080> would<00:04:34.280> like<00:04:34.479> evm<00:04:34.840> Max<00:04:35.039> to<00:04:35.120> be<00:04:35.240> a<00:04:35.360> tool 00:04:35.590 --> 00:04:35.600 align:start position:0% also would like evm Max to be a tool 00:04:35.600 --> 00:04:37.270 align:start position:0% also would like evm Max to be a tool which<00:04:35.759> allows<00:04:36.080> to<00:04:36.320> avoid<00:04:36.720> adding<00:04:37.080> new 00:04:37.270 --> 00:04:37.280 align:start position:0% which allows to avoid adding new 00:04:37.280 --> 00:04:39.950 align:start position:0% which allows to avoid adding new promiles<00:04:38.280> in<00:04:38.400> the<00:04:38.560> future<00:04:39.280> it<00:04:39.400> will<00:04:39.600> make<00:04:39.800> the 00:04:39.950 --> 00:04:39.960 align:start position:0% promiles in the future it will make the 00:04:39.960 --> 00:04:43.590 align:start position:0% promiles in the future it will make the cev's<00:04:40.600> lives<00:04:41.360> much<00:04:41.680> easier<00:04:42.520> because<00:04:42.919> they 00:04:43.590 --> 00:04:43.600 align:start position:0% cev's lives much easier because they 00:04:43.600 --> 00:04:47.189 align:start position:0% cev's lives much easier because they won't<00:04:43.960> need<00:04:44.440> to<00:04:45.280> uh<00:04:45.440> maintain<00:04:46.199> the<00:04:46.880> very 00:04:47.189 --> 00:04:47.199 align:start position:0% won't need to uh maintain the very 00:04:47.199 --> 00:04:49.310 align:start position:0% won't need to uh maintain the very specialized<00:04:47.840> cryptographic<00:04:48.520> libraries<00:04:49.160> in 00:04:49.310 --> 00:04:49.320 align:start position:0% specialized cryptographic libraries in 00:04:49.320 --> 00:04:52.909 align:start position:0% specialized cryptographic libraries in the<00:04:49.919> evm<00:04:50.919> so<00:04:51.479> they<00:04:51.720> they<00:04:51.840> will<00:04:52.039> not<00:04:52.560> have<00:04:52.720> a 00:04:52.909 --> 00:04:52.919 align:start position:0% the evm so they they will not have a 00:04:52.919 --> 00:04:55.350 align:start position:0% the evm so they they will not have a headache<00:04:53.400> like<00:04:54.280> uh<00:04:54.440> what<00:04:54.720> exactly<00:04:55.120> this 00:04:55.350 --> 00:04:55.360 align:start position:0% headache like uh what exactly this 00:04:55.360 --> 00:04:56.909 align:start position:0% headache like uh what exactly this function<00:04:55.639> do<00:04:55.880> I'm<00:04:56.000> not<00:04:56.120> the<00:04:56.280> cryptographer 00:04:56.909 --> 00:04:56.919 align:start position:0% function do I'm not the cryptographer 00:04:56.919 --> 00:04:58.749 align:start position:0% function do I'm not the cryptographer exactly<00:04:57.240> or<00:04:57.360> we<00:04:57.479> don't<00:04:57.680> have<00:04:57.840> a<00:04:58.280> specialized 00:04:58.749 --> 00:04:58.759 align:start position:0% exactly or we don't have a specialized 00:04:58.759 --> 00:05:01.150 align:start position:0% exactly or we don't have a specialized cryptographer<00:04:59.360> in<00:04:59.479> the<00:04:59.720> team<00:05:00.120> so<00:05:00.720> why<00:05:00.880> do<00:05:01.000> we 00:05:01.150 --> 00:05:01.160 align:start position:0% cryptographer in the team so why do we 00:05:01.160 --> 00:05:03.150 align:start position:0% cryptographer in the team so why do we need<00:05:01.360> to<00:05:01.800> to<00:05:02.080> to<00:05:02.240> to<00:05:02.360> maintain<00:05:02.840> this 00:05:03.150 --> 00:05:03.160 align:start position:0% need to to to to maintain this 00:05:03.160 --> 00:05:04.950 align:start position:0% need to to to to maintain this complicated<00:05:03.759> libraries<00:05:04.360> which<00:05:04.479> we<00:05:04.680> take 00:05:04.950 --> 00:05:04.960 align:start position:0% complicated libraries which we take 00:05:04.960 --> 00:05:08.189 align:start position:0% complicated libraries which we take basically<00:05:05.440> very<00:05:05.680> often<00:05:06.360> from<00:05:06.639> some<00:05:07.199> from<00:05:07.919> some 00:05:08.189 --> 00:05:08.199 align:start position:0% basically very often from some from some 00:05:08.199 --> 00:05:11.029 align:start position:0% basically very often from some from some external<00:05:08.680> libraries<00:05:09.280> which<00:05:09.400> are<00:05:09.919> already 00:05:11.029 --> 00:05:11.039 align:start position:0% external libraries which are already 00:05:11.039 --> 00:05:14.230 align:start position:0% external libraries which are already implemented<00:05:12.039> but<00:05:12.720> um<00:05:13.160> so<00:05:13.479> evm<00:05:13.880> max<00:05:14.080> will 00:05:14.230 --> 00:05:14.240 align:start position:0% implemented but um so evm max will 00:05:14.240 --> 00:05:15.710 align:start position:0% implemented but um so evm max will deliver<00:05:14.560> a<00:05:14.720> tool<00:05:14.960> which<00:05:15.080> should<00:05:15.280> make<00:05:15.479> pre 00:05:15.710 --> 00:05:15.720 align:start position:0% deliver a tool which should make pre 00:05:15.720 --> 00:05:18.189 align:start position:0% deliver a tool which should make pre compile<00:05:16.120> specification<00:05:16.919> also<00:05:17.360> possible<00:05:18.000> in 00:05:18.189 --> 00:05:18.199 align:start position:0% compile specification also possible in 00:05:18.199 --> 00:05:21.309 align:start position:0% compile specification also possible in the<00:05:18.400> evm<00:05:18.880> max<00:05:19.199> bu<00:05:19.520> code<00:05:19.880> so<00:05:20.360> we<00:05:20.479> can<00:05:20.680> imagine<00:05:21.120> if 00:05:21.309 --> 00:05:21.319 align:start position:0% the evm max bu code so we can imagine if 00:05:21.319 --> 00:05:23.670 align:start position:0% the evm max bu code so we can imagine if the<00:05:21.560> promiles<00:05:22.360> for<00:05:22.600> some<00:05:22.880> reason<00:05:23.240> will<00:05:23.440> be 00:05:23.670 --> 00:05:23.680 align:start position:0% the promiles for some reason will be 00:05:23.680 --> 00:05:26.390 align:start position:0% the promiles for some reason will be still<00:05:23.919> needed<00:05:24.919> to<00:05:25.240> to<00:05:25.360> be<00:05:25.560> implemented<00:05:26.120> and<00:05:26.240> to 00:05:26.390 --> 00:05:26.400 align:start position:0% still needed to to be implemented and to 00:05:26.400 --> 00:05:29.029 align:start position:0% still needed to to be implemented and to use<00:05:26.800> by<00:05:26.919> the<00:05:27.080> evm<00:05:28.080> we<00:05:28.199> can<00:05:28.400> imagine<00:05:28.759> that<00:05:28.919> the 00:05:29.029 --> 00:05:29.039 align:start position:0% use by the evm we can imagine that the 00:05:29.039 --> 00:05:31.909 align:start position:0% use by the evm we can imagine that the evm<00:05:29.919> bite<00:05:30.199> code<00:05:30.479> we<00:05:30.759> will<00:05:31.080> can<00:05:31.319> define<00:05:31.639> a 00:05:31.909 --> 00:05:31.919 align:start position:0% evm bite code we will can define a 00:05:31.919 --> 00:05:34.390 align:start position:0% evm bite code we will can define a specification<00:05:32.639> of<00:05:32.800> the<00:05:32.919> promiles<00:05:33.759> how<00:05:34.039> they 00:05:34.390 --> 00:05:34.400 align:start position:0% specification of the promiles how they 00:05:34.400 --> 00:05:36.309 align:start position:0% specification of the promiles how they should<00:05:34.639> be<00:05:34.840> implemented 00:05:36.309 --> 00:05:36.319 align:start position:0% should be implemented 00:05:36.319 --> 00:05:39.230 align:start position:0% should be implemented exactly 00:05:39.230 --> 00:05:39.240 align:start position:0% exactly 00:05:39.240 --> 00:05:42.189 align:start position:0% exactly yeah<00:05:40.240> so<00:05:40.600> but<00:05:40.759> let's<00:05:41.000> get<00:05:41.400> little<00:05:41.639> bit<00:05:41.840> deeper 00:05:42.189 --> 00:05:42.199 align:start position:0% yeah so but let's get little bit deeper 00:05:42.199 --> 00:05:45.950 align:start position:0% yeah so but let's get little bit deeper into<00:05:42.520> the<00:05:42.759> evm<00:05:43.160> max<00:05:43.400> instruction<00:05:43.919> details<00:05:44.960> so 00:05:45.950 --> 00:05:45.960 align:start position:0% into the evm max instruction details so 00:05:45.960 --> 00:05:48.270 align:start position:0% into the evm max instruction details so uh<00:05:46.160> we<00:05:46.280> can<00:05:46.440> split<00:05:46.759> it<00:05:46.919> into<00:05:47.160> three<00:05:47.479> different 00:05:48.270 --> 00:05:48.280 align:start position:0% uh we can split it into three different 00:05:48.280 --> 00:05:51.189 align:start position:0% uh we can split it into three different uh<00:05:48.680> three<00:05:48.919> different<00:05:49.280> parts<00:05:49.680> so<00:05:50.560> uh<00:05:50.680> the<00:05:50.840> first 00:05:51.189 --> 00:05:51.199 align:start position:0% uh three different parts so uh the first 00:05:51.199 --> 00:05:55.390 align:start position:0% uh three different parts so uh the first part<00:05:51.560> is<00:05:52.240> uh<00:05:52.520> just<00:05:52.960> uh<00:05:53.720> is<00:05:53.919> responsible<00:05:54.479> for 00:05:55.390 --> 00:05:55.400 align:start position:0% part is uh just uh is responsible for 00:05:55.400 --> 00:05:59.189 align:start position:0% part is uh just uh is responsible for setting<00:05:55.800> up<00:05:56.160> the<00:05:56.840> uh<00:05:57.080> the<00:05:57.319> evm<00:05:57.720> max<00:05:58.199> context 00:05:59.189 --> 00:05:59.199 align:start position:0% setting up the uh the evm max context 00:05:59.199 --> 00:06:01.029 align:start position:0% setting up the uh the evm max context the<00:05:59.360> second<00:05:59.639> second<00:05:59.880> one<00:06:00.240> is<00:06:00.400> just<00:06:00.560> the<00:06:00.720> set<00:06:00.880> of 00:06:01.029 --> 00:06:01.039 align:start position:0% the second second one is just the set of 00:06:01.039 --> 00:06:02.870 align:start position:0% the second second one is just the set of modular<00:06:01.440> arithmetic<00:06:01.919> instruction<00:06:02.479> I<00:06:02.600> already 00:06:02.870 --> 00:06:02.880 align:start position:0% modular arithmetic instruction I already 00:06:02.880 --> 00:06:05.110 align:start position:0% modular arithmetic instruction I already mentioned<00:06:03.520> and<00:06:03.680> the<00:06:03.800> third<00:06:04.120> one<00:06:04.360> is<00:06:04.919> uh 00:06:05.110 --> 00:06:05.120 align:start position:0% mentioned and the third one is uh 00:06:05.120 --> 00:06:08.790 align:start position:0% mentioned and the third one is uh responsible<00:06:05.680> for<00:06:05.919> evm<00:06:06.440> evm<00:06:06.840> Max<00:06:07.160> Contex<00:06:07.520> is 00:06:08.790 --> 00:06:08.800 align:start position:0% responsible for evm evm Max Contex is 00:06:08.800 --> 00:06:11.589 align:start position:0% responsible for evm evm Max Contex is communication<00:06:09.800> so<00:06:10.560> so<00:06:10.800> let's<00:06:11.120> get<00:06:11.319> into 00:06:11.589 --> 00:06:11.599 align:start position:0% communication so so let's get into 00:06:11.599 --> 00:06:13.790 align:start position:0% communication so so let's get into details<00:06:12.000> of<00:06:12.160> these<00:06:12.360> three<00:06:12.880> three<00:06:13.199> three<00:06:13.440> parts 00:06:13.790 --> 00:06:13.800 align:start position:0% details of these three three three parts 00:06:13.800 --> 00:06:16.830 align:start position:0% details of these three three three parts so<00:06:14.039> first<00:06:14.960> uh<00:06:15.080> setup<00:06:15.520> X<00:06:15.720> creates<00:06:16.039> the<00:06:16.160> evm<00:06:16.520> max 00:06:16.830 --> 00:06:16.840 align:start position:0% so first uh setup X creates the evm max 00:06:16.840 --> 00:06:19.230 align:start position:0% so first uh setup X creates the evm max context<00:06:17.680> if<00:06:17.840> it<00:06:17.960> doesn't<00:06:18.319> exist<00:06:18.680> yet<00:06:19.080> which 00:06:19.230 --> 00:06:19.240 align:start position:0% context if it doesn't exist yet which 00:06:19.240 --> 00:06:21.950 align:start position:0% context if it doesn't exist yet which means<00:06:19.720> it<00:06:19.880> initialize<00:06:20.720> modulus<00:06:21.280> values<00:06:21.759> and 00:06:21.950 --> 00:06:21.960 align:start position:0% means it initialize modulus values and 00:06:21.960 --> 00:06:24.749 align:start position:0% means it initialize modulus values and allocates<00:06:22.479> evm<00:06:22.880> max<00:06:23.160> value<00:06:23.599> slots<00:06:24.319> in<00:06:24.479> the 00:06:24.749 --> 00:06:24.759 align:start position:0% allocates evm max value slots in the 00:06:24.759 --> 00:06:28.150 align:start position:0% allocates evm max value slots in the dedicated<00:06:25.319> for<00:06:25.560> evm<00:06:26.000> max<00:06:26.280> memory<00:06:27.000> only<00:06:28.000> these 00:06:28.150 --> 00:06:28.160 align:start position:0% dedicated for evm max memory only these 00:06:28.160 --> 00:06:30.830 align:start position:0% dedicated for evm max memory only these slots<00:06:28.560> can<00:06:28.759> be<00:06:28.960> only<00:06:29.280> access<00:06:29.840> by<00:06:30.039> the<00:06:30.160> evm<00:06:30.560> max 00:06:30.830 --> 00:06:30.840 align:start position:0% slots can be only access by the evm max 00:06:30.840 --> 00:06:33.830 align:start position:0% slots can be only access by the evm max of<00:06:31.039> course<00:06:31.280> of<00:06:31.520> course<00:06:32.520> and<00:06:32.919> also<00:06:33.240> initialize 00:06:33.830 --> 00:06:33.840 align:start position:0% of course of course and also initialize 00:06:33.840 --> 00:06:36.710 align:start position:0% of course of course and also initialize some<00:06:34.160> specific<00:06:35.120> uh<00:06:35.280> constant<00:06:35.840> values<00:06:36.520> like 00:06:36.710 --> 00:06:36.720 align:start position:0% some specific uh constant values like 00:06:36.720 --> 00:06:39.670 align:start position:0% some specific uh constant values like for<00:06:36.880> example<00:06:37.240> air<00:06:37.560> squ<00:06:38.520> which<00:06:38.960> must<00:06:39.280> be<00:06:39.520> which 00:06:39.670 --> 00:06:39.680 align:start position:0% for example air squ which must be which 00:06:39.680 --> 00:06:42.830 align:start position:0% for example air squ which must be which is<00:06:39.840> used<00:06:40.280> for<00:06:41.280> uh<00:06:42.000> which<00:06:42.120> is<00:06:42.240> used<00:06:42.520> by 00:06:42.830 --> 00:06:42.840 align:start position:0% is used for uh which is used by 00:06:42.840 --> 00:06:46.029 align:start position:0% is used for uh which is used by Montgomery<00:06:43.759> Montgomery<00:06:44.639> form<00:06:45.639> in<00:06:45.800> this 00:06:46.029 --> 00:06:46.039 align:start position:0% Montgomery Montgomery form in this 00:06:46.039 --> 00:06:47.990 align:start position:0% Montgomery Montgomery form in this context<00:06:46.759> if<00:06:46.880> the<00:06:47.039> context<00:06:47.400> is<00:06:47.560> already 00:06:47.990 --> 00:06:48.000 align:start position:0% context if the context is already 00:06:48.000 --> 00:06:50.749 align:start position:0% context if the context is already defined<00:06:48.599> so<00:06:49.160> the<00:06:49.280> set<00:06:49.520> upex<00:06:49.960> just<00:06:50.160> only<00:06:50.400> switch 00:06:50.749 --> 00:06:50.759 align:start position:0% defined so the set upex just only switch 00:06:50.759 --> 00:06:53.870 align:start position:0% defined so the set upex just only switch to<00:06:50.960> this<00:06:51.560> to<00:06:51.759> this<00:06:51.960> to<00:06:52.120> this<00:06:52.280> already<00:06:52.560> defined 00:06:53.870 --> 00:06:53.880 align:start position:0% to this to this to this already defined 00:06:53.880 --> 00:06:57.589 align:start position:0% to this to this to this already defined context<00:06:54.880> second<00:06:55.319> part<00:06:55.840> are<00:06:56.240> the<00:06:57.039> arithmetic 00:06:57.589 --> 00:06:57.599 align:start position:0% context second part are the arithmetic 00:06:57.599 --> 00:07:00.350 align:start position:0% context second part are the arithmetic instructions<00:06:58.599> so<00:06:58.879> basically 00:07:00.350 --> 00:07:00.360 align:start position:0% instructions so basically 00:07:00.360 --> 00:07:03.070 align:start position:0% instructions so basically um<00:07:00.879> they<00:07:01.639> uh<00:07:01.960> perform<00:07:02.400> the<00:07:02.520> arithmetic 00:07:03.070 --> 00:07:03.080 align:start position:0% um they uh perform the arithmetic 00:07:03.080 --> 00:07:04.909 align:start position:0% um they uh perform the arithmetic operation<00:07:03.639> according<00:07:03.960> to<00:07:04.160> their<00:07:04.360> names<00:07:04.800> as 00:07:04.909 --> 00:07:04.919 align:start position:0% operation according to their names as 00:07:04.919 --> 00:07:07.589 align:start position:0% operation according to their names as you<00:07:05.000> can<00:07:05.160> see<00:07:05.360> so<00:07:05.599> everybody<00:07:06.080> who<00:07:06.960> uh<00:07:07.080> who<00:07:07.240> know 00:07:07.589 --> 00:07:07.599 align:start position:0% you can see so everybody who uh who know 00:07:07.599 --> 00:07:09.909 align:start position:0% you can see so everybody who uh who know a<00:07:07.680> little<00:07:07.919> bit<00:07:08.199> about<00:07:08.680> the<00:07:09.039> the<00:07:09.280> arithmetic 00:07:09.909 --> 00:07:09.919 align:start position:0% a little bit about the the arithmetic 00:07:09.919 --> 00:07:12.790 align:start position:0% a little bit about the the arithmetic modular<00:07:10.240> arithmetic<00:07:10.759> should<00:07:11.599> uh<00:07:11.720> be<00:07:11.919> able<00:07:12.680> uh 00:07:12.790 --> 00:07:12.800 align:start position:0% modular arithmetic should uh be able uh 00:07:12.800 --> 00:07:15.390 align:start position:0% modular arithmetic should uh be able uh to<00:07:12.919> know<00:07:13.240> what's<00:07:13.599> what<00:07:13.759> they<00:07:14.000> exactly<00:07:14.360> do<00:07:15.240> but 00:07:15.390 --> 00:07:15.400 align:start position:0% to know what's what they exactly do but 00:07:15.400 --> 00:07:17.350 align:start position:0% to know what's what they exactly do but it's<00:07:15.599> worth<00:07:15.840> noticing<00:07:16.440> that<00:07:16.639> they<00:07:16.840> operate 00:07:17.350 --> 00:07:17.360 align:start position:0% it's worth noticing that they operate 00:07:17.360 --> 00:07:20.589 align:start position:0% it's worth noticing that they operate only<00:07:17.759> on<00:07:18.639> uh<00:07:18.960> indexes<00:07:19.560> of<00:07:19.720> the<00:07:19.879> slots<00:07:20.319> in<00:07:20.479> the 00:07:20.589 --> 00:07:20.599 align:start position:0% only on uh indexes of the slots in the 00:07:20.599 --> 00:07:23.670 align:start position:0% only on uh indexes of the slots in the evm<00:07:21.000> max<00:07:21.360> context<00:07:22.360> and<00:07:22.680> the<00:07:22.840> indexes<00:07:23.319> are 00:07:23.670 --> 00:07:23.680 align:start position:0% evm max context and the indexes are 00:07:23.680 --> 00:07:27.749 align:start position:0% evm max context and the indexes are static<00:07:24.440> and<00:07:24.680> can<00:07:24.919> be<00:07:26.240> validated<00:07:27.240> on<00:07:27.479> the 00:07:27.749 --> 00:07:27.759 align:start position:0% static and can be validated on the 00:07:27.759 --> 00:07:30.070 align:start position:0% static and can be validated on the deployment<00:07:28.759> uh<00:07:29.160> uh<00:07:29.520> before<00:07:29.759> before 00:07:30.070 --> 00:07:30.080 align:start position:0% deployment uh uh before before 00:07:30.080 --> 00:07:31.790 align:start position:0% deployment uh uh before before deployment<00:07:30.639> of<00:07:30.759> the<00:07:30.919> contract<00:07:31.240> to<00:07:31.400> the<00:07:31.520> main 00:07:31.790 --> 00:07:31.800 align:start position:0% deployment of the contract to the main 00:07:31.800 --> 00:07:35.189 align:start position:0% deployment of the contract to the main net<00:07:32.599> which<00:07:32.759> allows<00:07:33.120> to<00:07:33.319> validate<00:07:33.960> them<00:07:34.720> us 00:07:35.189 --> 00:07:35.199 align:start position:0% net which allows to validate them us 00:07:35.199 --> 00:07:39.150 align:start position:0% net which allows to validate them us exactly<00:07:35.639> the<00:07:35.840> same<00:07:36.160> way<00:07:36.520> as<00:07:36.800> all<00:07:37.319> the<00:07:38.319> uh<00:07:38.879> all 00:07:39.150 --> 00:07:39.160 align:start position:0% exactly the same way as all the uh all 00:07:39.160 --> 00:07:42.990 align:start position:0% exactly the same way as all the uh all the<00:07:40.120> immediate<00:07:40.599> arguments<00:07:41.440> in<00:07:41.599> the<00:07:41.879> eof<00:07:42.879> uh 00:07:42.990 --> 00:07:43.000 align:start position:0% the immediate arguments in the eof uh 00:07:43.000 --> 00:07:45.869 align:start position:0% the immediate arguments in the eof uh are 00:07:45.869 --> 00:07:45.879 align:start position:0% 00:07:45.879 --> 00:07:48.950 align:start position:0% validated<00:07:46.879> and<00:07:47.039> the<00:07:47.240> last<00:07:47.639> but<00:07:47.840> not<00:07:48.120> least 00:07:48.950 --> 00:07:48.960 align:start position:0% validated and the last but not least 00:07:48.960 --> 00:07:52.110 align:start position:0% validated and the last but not least part<00:07:49.960> uh<00:07:50.319> is<00:07:50.919> there<00:07:51.039> are<00:07:51.639> are<00:07:51.840> two 00:07:52.110 --> 00:07:52.120 align:start position:0% part uh is there are are two 00:07:52.120 --> 00:07:54.390 align:start position:0% part uh is there are are two instructions<00:07:52.759> to<00:07:53.039> upod<00:07:53.759> responsible<00:07:54.199> for 00:07:54.390 --> 00:07:54.400 align:start position:0% instructions to upod responsible for 00:07:54.400 --> 00:07:57.510 align:start position:0% instructions to upod responsible for loading<00:07:54.840> and<00:07:54.960> soring<00:07:55.479> values<00:07:55.840> from<00:07:56.120> and<00:07:56.400> to<00:07:57.360> uh 00:07:57.510 --> 00:07:57.520 align:start position:0% loading and soring values from and to uh 00:07:57.520 --> 00:07:59.950 align:start position:0% loading and soring values from and to uh evm<00:07:57.919> Max<00:07:58.280> context<00:07:58.840> they<00:07:59.000> allow<00:07:59.240> to<00:07:59.520> initialize 00:07:59.950 --> 00:07:59.960 align:start position:0% evm Max context they allow to initialize 00:07:59.960 --> 00:08:04.070 align:start position:0% evm Max context they allow to initialize slots<00:08:00.400> values<00:08:01.360> uh<00:08:01.440> using<00:08:01.800> evm<00:08:02.440> evm<00:08:02.919> memory<00:08:03.720> and 00:08:04.070 --> 00:08:04.080 align:start position:0% slots values uh using evm evm memory and 00:08:04.080 --> 00:08:07.710 align:start position:0% slots values uh using evm evm memory and loads<00:08:05.080> result<00:08:05.639> back<00:08:05.840> to<00:08:06.000> the<00:08:06.120> evm<00:08:06.759> evm<00:08:07.120> memory 00:08:07.710 --> 00:08:07.720 align:start position:0% loads result back to the evm evm memory 00:08:07.720 --> 00:08:10.790 align:start position:0% loads result back to the evm evm memory because<00:08:08.000> we<00:08:08.159> allow<00:08:09.039> only<00:08:09.840> uh<00:08:10.080> we<00:08:10.199> allow<00:08:10.520> any 00:08:10.790 --> 00:08:10.800 align:start position:0% because we allow only uh we allow any 00:08:10.800 --> 00:08:13.149 align:start position:0% because we allow only uh we allow any size<00:08:11.039> of<00:08:11.199> the<00:08:11.319> modulus<00:08:12.039> or<00:08:12.240> C<00:08:12.520> of<00:08:12.680> course<00:08:12.960> but 00:08:13.149 --> 00:08:13.159 align:start position:0% size of the modulus or C of course but 00:08:13.159 --> 00:08:16.270 align:start position:0% size of the modulus or C of course but any<00:08:13.440> size<00:08:14.080> we<00:08:14.240> transfer<00:08:14.759> values<00:08:15.479> from<00:08:15.720> and<00:08:15.960> to 00:08:16.270 --> 00:08:16.280 align:start position:0% any size we transfer values from and to 00:08:16.280 --> 00:08:19.350 align:start position:0% any size we transfer values from and to evm<00:08:16.720> memory<00:08:17.199> instead<00:08:17.639> of<00:08:18.240> uh<00:08:18.400> instead<00:08:18.680> of<00:08:18.800> evm 00:08:19.350 --> 00:08:19.360 align:start position:0% evm memory instead of uh instead of evm 00:08:19.360 --> 00:08:22.710 align:start position:0% evm memory instead of uh instead of evm Stack<00:08:20.360> so<00:08:20.879> this<00:08:21.039> is<00:08:21.319> this<00:08:21.440> is<00:08:21.560> the<00:08:21.759> set<00:08:22.039> of<00:08:22.560> uh 00:08:22.710 --> 00:08:22.720 align:start position:0% Stack so this is this is the set of uh 00:08:22.720 --> 00:08:25.270 align:start position:0% Stack so this is this is the set of uh evm<00:08:23.159> Max<00:08:23.479> instructions<00:08:24.479> and<00:08:24.879> uh<00:08:25.000> but<00:08:25.159> of 00:08:25.270 --> 00:08:25.280 align:start position:0% evm Max instructions and uh but of 00:08:25.280 --> 00:08:27.749 align:start position:0% evm Max instructions and uh but of course<00:08:25.440> it<00:08:25.599> can<00:08:25.720> be<00:08:25.919> extended<00:08:26.800> or<00:08:27.039> changed<00:08:27.599> as 00:08:27.749 --> 00:08:27.759 align:start position:0% course it can be extended or changed as 00:08:27.759 --> 00:08:30.230 align:start position:0% course it can be extended or changed as the<00:08:27.919> proposal<00:08:28.360> is<00:08:28.520> still<00:08:28.720> in<00:08:28.879> the<00:08:29.199> Des<00:08:29.759> stage 00:08:30.230 --> 00:08:30.240 align:start position:0% the proposal is still in the Des stage 00:08:30.240 --> 00:08:36.149 align:start position:0% the proposal is still in the Des stage sorry<00:08:30.520> I<00:08:30.560> need<00:08:30.720> to<00:08:30.919> take<00:08:31.159> a<00:08:31.759> some 00:08:36.149 --> 00:08:36.159 align:start position:0% 00:08:36.159 --> 00:08:40.190 align:start position:0% more<00:08:37.360> yeah<00:08:38.360> so<00:08:38.560> we<00:08:38.719> have<00:08:39.000> a<00:08:39.440> we<00:08:39.599> have<00:08:39.719> a<00:08:39.959> this 00:08:40.190 --> 00:08:40.200 align:start position:0% more yeah so we have a we have a this 00:08:40.200 --> 00:08:43.110 align:start position:0% more yeah so we have a we have a this set<00:08:40.440> of<00:08:40.680> this<00:08:41.320> five<00:08:41.680> instructions<00:08:42.680> which<00:08:42.800> are 00:08:43.110 --> 00:08:43.120 align:start position:0% set of this five instructions which are 00:08:43.120 --> 00:08:48.269 align:start position:0% set of this five instructions which are quite<00:08:44.440> simple<00:08:45.440> uh<00:08:45.920> yeah<00:08:46.399> so<00:08:46.720> as<00:08:46.839> I<00:08:47.000> mentioned<00:08:47.800> U 00:08:48.269 --> 00:08:48.279 align:start position:0% quite simple uh yeah so as I mentioned U 00:08:48.279 --> 00:08:51.430 align:start position:0% quite simple uh yeah so as I mentioned U earlier<00:08:49.120> about<00:08:49.320> the<00:08:49.880> promiles<00:08:50.880> uh<00:08:51.080> they<00:08:51.240> have 00:08:51.430 --> 00:08:51.440 align:start position:0% earlier about the promiles uh they have 00:08:51.440 --> 00:08:54.230 align:start position:0% earlier about the promiles uh they have some<00:08:51.800> downsides<00:08:52.440> I'm<00:08:52.600> going<00:08:52.800> to<00:08:53.519> I'm<00:08:53.680> going<00:08:53.920> to 00:08:54.230 --> 00:08:54.240 align:start position:0% some downsides I'm going to I'm going to 00:08:54.240 --> 00:08:57.509 align:start position:0% some downsides I'm going to I'm going to to<00:08:54.399> to<00:08:54.600> present<00:08:55.160> also<00:08:56.160> uh<00:08:56.360> yeah<00:08:56.959> but<00:08:57.160> let<00:08:57.279> me 00:08:57.509 --> 00:08:57.519 align:start position:0% to to present also uh yeah but let me 00:08:57.519 --> 00:08:59.470 align:start position:0% to to present also uh yeah but let me explain<00:08:57.920> what<00:08:58.120> exactly<00:08:58.600> I<00:08:58.720> have<00:08:58.839> in<00:08:59.000> mind<00:08:59.240> so 00:08:59.470 --> 00:08:59.480 align:start position:0% explain what exactly I have in mind so 00:08:59.480 --> 00:09:00.790 align:start position:0% explain what exactly I have in mind so so<00:09:00.079> at 00:09:00.790 --> 00:09:00.800 align:start position:0% so at 00:09:00.800 --> 00:09:04.190 align:start position:0% so at first<00:09:01.800> um<00:09:02.320> they<00:09:02.440> are<00:09:02.560> all<00:09:02.760> implemented<00:09:03.560> by 00:09:04.190 --> 00:09:04.200 align:start position:0% first um they are all implemented by 00:09:04.200 --> 00:09:07.550 align:start position:0% first um they are all implemented by many<00:09:04.640> different<00:09:05.519> libraries<00:09:06.519> in<00:09:06.959> in<00:09:07.120> different 00:09:07.550 --> 00:09:07.560 align:start position:0% many different libraries in in different 00:09:07.560 --> 00:09:10.430 align:start position:0% many different libraries in in different languages<00:09:08.200> across<00:09:08.880> all<00:09:09.079> the<00:09:09.440> execution 00:09:10.430 --> 00:09:10.440 align:start position:0% languages across all the execution 00:09:10.440 --> 00:09:12.829 align:start position:0% languages across all the execution execution<00:09:10.800> layer<00:09:11.120> clients<00:09:12.079> this<00:09:12.240> means<00:09:12.600> that 00:09:12.829 --> 00:09:12.839 align:start position:0% execution layer clients this means that 00:09:12.839 --> 00:09:14.550 align:start position:0% execution layer clients this means that they<00:09:12.959> are<00:09:13.200> potentially<00:09:13.720> Vector<00:09:14.040> of<00:09:14.240> attacks 00:09:14.550 --> 00:09:14.560 align:start position:0% they are potentially Vector of attacks 00:09:14.560 --> 00:09:17.110 align:start position:0% they are potentially Vector of attacks on<00:09:14.680> the<00:09:14.839> clients<00:09:15.760> and<00:09:15.920> on<00:09:16.079> the<00:09:16.279> consensus<00:09:16.959> of 00:09:17.110 --> 00:09:17.120 align:start position:0% on the clients and on the consensus of 00:09:17.120 --> 00:09:20.430 align:start position:0% on the clients and on the consensus of the<00:09:17.279> chain<00:09:18.040> moreover<00:09:18.880> the<00:09:19.079> IPS<00:09:19.680> proposing<00:09:20.200> new 00:09:20.430 --> 00:09:20.440 align:start position:0% the chain moreover the IPS proposing new 00:09:20.440 --> 00:09:22.790 align:start position:0% the chain moreover the IPS proposing new pre<00:09:20.680> compiles<00:09:21.120> cannot<00:09:21.480> spec<00:09:21.880> out<00:09:22.600> the 00:09:22.790 --> 00:09:22.800 align:start position:0% pre compiles cannot spec out the 00:09:22.800 --> 00:09:25.550 align:start position:0% pre compiles cannot spec out the implementation<00:09:23.560> details<00:09:24.160> details<00:09:25.160> of<00:09:25.360> them 00:09:25.550 --> 00:09:25.560 align:start position:0% implementation details details of them 00:09:25.560 --> 00:09:27.389 align:start position:0% implementation details details of them because<00:09:25.800> the<00:09:25.920> implementations<00:09:26.800> differs 00:09:27.389 --> 00:09:27.399 align:start position:0% because the implementations differs 00:09:27.399 --> 00:09:29.030 align:start position:0% because the implementations differs differ<00:09:27.760> the<00:09:27.839> implementations<00:09:28.519> differ 00:09:29.030 --> 00:09:29.040 align:start position:0% differ the implementations differ 00:09:29.040 --> 00:09:31.230 align:start position:0% differ the implementations differ between<00:09:29.360> between<00:09:29.680> the<00:09:29.839> between<00:09:30.120> the<00:09:30.279> clients 00:09:31.230 --> 00:09:31.240 align:start position:0% between between the between the clients 00:09:31.240 --> 00:09:35.190 align:start position:0% between between the between the clients as<00:09:31.320> a<00:09:31.519> result<00:09:31.920> of<00:09:32.640> this<00:09:33.640> very<00:09:34.040> often<00:09:35.040> uh 00:09:35.190 --> 00:09:35.200 align:start position:0% as a result of this very often uh 00:09:35.200 --> 00:09:37.870 align:start position:0% as a result of this very often uh promise<00:09:35.839> implementation<00:09:36.800> need<00:09:37.079> to<00:09:37.360> do<00:09:37.480> some 00:09:37.870 --> 00:09:37.880 align:start position:0% promise implementation need to do some 00:09:37.880 --> 00:09:40.269 align:start position:0% promise implementation need to do some redundant<00:09:38.880> operations<00:09:39.440> to<00:09:39.640> make<00:09:39.800> sure<00:09:40.120> that 00:09:40.269 --> 00:09:40.279 align:start position:0% redundant operations to make sure that 00:09:40.279 --> 00:09:43.470 align:start position:0% redundant operations to make sure that the<00:09:40.480> result<00:09:41.480> will<00:09:41.680> be<00:09:41.920> exactly<00:09:42.360> the<00:09:42.519> same<00:09:43.160> for 00:09:43.470 --> 00:09:43.480 align:start position:0% the result will be exactly the same for 00:09:43.480 --> 00:09:46.269 align:start position:0% the result will be exactly the same for all<00:09:43.800> possible<00:09:44.640> implementations<00:09:45.640> of<00:09:45.880> the<00:09:46.200> of 00:09:46.269 --> 00:09:46.279 align:start position:0% all possible implementations of the of 00:09:46.279 --> 00:09:48.949 align:start position:0% all possible implementations of the of the<00:09:46.399> promiles<00:09:47.360> so<00:09:47.880> because<00:09:48.320> if<00:09:48.519> the<00:09:48.680> if<00:09:48.800> the 00:09:48.949 --> 00:09:48.959 align:start position:0% the promiles so because if the if the 00:09:48.959 --> 00:09:51.509 align:start position:0% the promiles so because if the if the result<00:09:49.240> will<00:09:49.399> be<00:09:49.600> different<00:09:50.000> we<00:09:50.120> can<00:09:50.279> have<00:09:50.519> a 00:09:51.509 --> 00:09:51.519 align:start position:0% result will be different we can have a 00:09:51.519 --> 00:09:53.470 align:start position:0% result will be different we can have a basically<00:09:51.880> if<00:09:52.000> the<00:09:52.200> result<00:09:52.760> for<00:09:53.000> the<00:09:53.120> same 00:09:53.470 --> 00:09:53.480 align:start position:0% basically if the result for the same 00:09:53.480 --> 00:09:57.069 align:start position:0% basically if the result for the same input<00:09:54.399> will<00:09:54.760> generate<00:09:55.279> different<00:09:55.760> res<00:09:56.160> the 00:09:57.069 --> 00:09:57.079 align:start position:0% input will generate different res the 00:09:57.079 --> 00:09:59.870 align:start position:0% input will generate different res the will<00:09:57.240> be<00:09:57.440> different<00:09:58.360> it<00:09:58.480> means<00:09:58.880> that<00:09:59.200> uh<00:09:59.560> that 00:09:59.870 --> 00:09:59.880 align:start position:0% will be different it means that uh that 00:09:59.880 --> 00:10:02.550 align:start position:0% will be different it means that uh that basically<00:10:00.880> we<00:10:01.399> we<00:10:01.560> we<00:10:01.680> have<00:10:01.800> a<00:10:01.959> consensus 00:10:02.550 --> 00:10:02.560 align:start position:0% basically we we we have a consensus 00:10:02.560 --> 00:10:05.310 align:start position:0% basically we we we have a consensus problem<00:10:03.000> yeah<00:10:03.680> because<00:10:04.000> we<00:10:04.240> we<00:10:04.399> get<00:10:04.920> we<00:10:05.040> get 00:10:05.310 --> 00:10:05.320 align:start position:0% problem yeah because we we get we get 00:10:05.320 --> 00:10:07.550 align:start position:0% problem yeah because we we get we get different<00:10:05.720> results<00:10:06.519> for<00:10:06.720> the<00:10:06.880> same<00:10:07.079> input<00:10:07.440> for 00:10:07.550 --> 00:10:07.560 align:start position:0% different results for the same input for 00:10:07.560 --> 00:10:09.750 align:start position:0% different results for the same input for the<00:10:07.680> same<00:10:07.880> PR<00:10:08.120> compile<00:10:08.720> on<00:10:08.880> a<00:10:09.079> different<00:10:09.519> on<00:10:09.640> a 00:10:09.750 --> 00:10:09.760 align:start position:0% the same PR compile on a different on a 00:10:09.760 --> 00:10:10.990 align:start position:0% the same PR compile on a different on a different 00:10:10.990 --> 00:10:11.000 align:start position:0% different 00:10:11.000 --> 00:10:14.030 align:start position:0% different clients<00:10:12.000> uh<00:10:12.200> and<00:10:12.440> we<00:10:12.600> have<00:10:12.800> even<00:10:13.320> the 00:10:14.030 --> 00:10:14.040 align:start position:0% clients uh and we have even the 00:10:14.040 --> 00:10:16.269 align:start position:0% clients uh and we have even the recently<00:10:15.040> recently<00:10:15.560> very<00:10:15.800> intensive 00:10:16.269 --> 00:10:16.279 align:start position:0% recently recently very intensive 00:10:16.279 --> 00:10:19.030 align:start position:0% recently recently very intensive discussion<00:10:16.839> about<00:10:17.519> uh<00:10:17.760> about<00:10:18.279> exactly<00:10:18.760> this 00:10:19.030 --> 00:10:19.040 align:start position:0% discussion about uh about exactly this 00:10:19.040 --> 00:10:22.190 align:start position:0% discussion about uh about exactly this this<00:10:19.279> problem<00:10:20.160> when<00:10:20.640> when<00:10:21.079> uh<00:10:21.240> finalizing<00:10:22.040> the 00:10:22.190 --> 00:10:22.200 align:start position:0% this problem when when uh finalizing the 00:10:22.200 --> 00:10:24.710 align:start position:0% this problem when when uh finalizing the spec<00:10:22.600> of<00:10:22.800> the<00:10:23.200> of<00:10:23.360> the<00:10:23.440> BLS<00:10:23.880> promiles<00:10:24.480> which<00:10:24.600> is 00:10:24.710 --> 00:10:24.720 align:start position:0% spec of the of the BLS promiles which is 00:10:24.720 --> 00:10:27.550 align:start position:0% spec of the of the BLS promiles which is going<00:10:24.959> to<00:10:25.120> be<00:10:25.720> introduced<00:10:26.399> in<00:10:26.600> the<00:10:27.040> in<00:10:27.240> the<00:10:27.440> in 00:10:27.550 --> 00:10:27.560 align:start position:0% going to be introduced in the in the in 00:10:27.560 --> 00:10:30.750 align:start position:0% going to be introduced in the in the in the<00:10:27.680> upcoming<00:10:28.160> Fork 00:10:30.750 --> 00:10:30.760 align:start position:0% the upcoming Fork 00:10:30.760 --> 00:10:34.990 align:start position:0% the upcoming Fork yeah<00:10:31.200> so<00:10:32.000> um<00:10:32.399> and<00:10:33.040> let<00:10:33.200> me<00:10:34.079> show<00:10:34.399> you<00:10:34.680> one 00:10:34.990 --> 00:10:35.000 align:start position:0% yeah so um and let me show you one 00:10:35.000 --> 00:10:37.870 align:start position:0% yeah so um and let me show you one example<00:10:35.720> very<00:10:35.959> simple<00:10:36.360> example<00:10:37.360> of<00:10:37.480> the<00:10:37.600> pre 00:10:37.870 --> 00:10:37.880 align:start position:0% example very simple example of the pre 00:10:37.880 --> 00:10:41.069 align:start position:0% example very simple example of the pre compile<00:10:38.200> which<00:10:38.399> already<00:10:39.000> exists<00:10:40.000> um<00:10:40.440> it's<00:10:40.720> a 00:10:41.069 --> 00:10:41.079 align:start position:0% compile which already exists um it's a 00:10:41.079 --> 00:10:44.870 align:start position:0% compile which already exists um it's a it's<00:10:41.200> a<00:10:41.360> point<00:10:41.600> addition<00:10:42.000> on<00:10:42.760> bn5<00:10:43.880> 254 00:10:44.870 --> 00:10:44.880 align:start position:0% it's a point addition on bn5 254 00:10:44.880 --> 00:10:48.310 align:start position:0% it's a point addition on bn5 254 elliptic<00:10:45.839> curve<00:10:46.839> and<00:10:47.040> I'm<00:10:47.279> just<00:10:47.560> going<00:10:47.839> to 00:10:48.310 --> 00:10:48.320 align:start position:0% elliptic curve and I'm just going to 00:10:48.320 --> 00:10:50.069 align:start position:0% elliptic curve and I'm just going to present<00:10:48.639> you<00:10:48.800> a<00:10:48.959> simple<00:10:49.320> formula<00:10:49.839> which<00:10:49.959> is 00:10:50.069 --> 00:10:50.079 align:start position:0% present you a simple formula which is 00:10:50.079 --> 00:10:52.069 align:start position:0% present you a simple formula which is used<00:10:50.320> to<00:10:50.440> add<00:10:50.639> two<00:10:50.800> points<00:10:51.000> on<00:10:51.160> Ting<00:10:51.600> curve<00:10:51.880> not 00:10:52.069 --> 00:10:52.079 align:start position:0% used to add two points on Ting curve not 00:10:52.079 --> 00:10:54.870 align:start position:0% used to add two points on Ting curve not going<00:10:52.320> into<00:10:52.560> details<00:10:53.440> because<00:10:53.800> they<00:10:54.399> they 00:10:54.870 --> 00:10:54.880 align:start position:0% going into details because they they 00:10:54.880 --> 00:10:57.069 align:start position:0% going into details because they they they<00:10:55.160> it<00:10:55.279> doesn't<00:10:55.600> matter<00:10:56.240> how<00:10:56.519> they<00:10:56.760> how<00:10:56.920> the 00:10:57.069 --> 00:10:57.079 align:start position:0% they it doesn't matter how they how the 00:10:57.079 --> 00:10:59.430 align:start position:0% they it doesn't matter how they how the addition<00:10:57.360> is<00:10:57.560> defined<00:10:58.399> and<00:10:58.639> why<00:10:58.839> it's<00:10:59.040> this 00:10:59.430 --> 00:10:59.440 align:start position:0% addition is defined and why it's this 00:10:59.440 --> 00:11:02.470 align:start position:0% addition is defined and why it's this way<00:11:00.279> the<00:11:00.399> formula<00:11:00.800> is<00:11:01.040> quite<00:11:01.320> simple<00:11:02.240> we've 00:11:02.470 --> 00:11:02.480 align:start position:0% way the formula is quite simple we've 00:11:02.480 --> 00:11:04.350 align:start position:0% way the formula is quite simple we've got<00:11:02.720> two<00:11:02.920> points<00:11:03.200> on<00:11:03.360> elliptic 00:11:04.350 --> 00:11:04.360 align:start position:0% got two points on elliptic 00:11:04.360 --> 00:11:06.990 align:start position:0% got two points on elliptic curve<00:11:05.360> uh<00:11:05.519> we<00:11:05.680> first<00:11:06.000> check<00:11:06.399> that<00:11:06.560> the<00:11:06.720> x 00:11:06.990 --> 00:11:07.000 align:start position:0% curve uh we first check that the x 00:11:07.000 --> 00:11:09.150 align:start position:0% curve uh we first check that the x coordinates<00:11:07.800> are<00:11:08.040> different<00:11:08.360> of<00:11:08.600> of<00:11:08.760> them<00:11:08.920> are 00:11:09.150 --> 00:11:09.160 align:start position:0% coordinates are different of of them are 00:11:09.160 --> 00:11:11.750 align:start position:0% coordinates are different of of them are different<00:11:09.760> different<00:11:10.680> and<00:11:10.839> if<00:11:11.040> they<00:11:11.200> are<00:11:11.480> not 00:11:11.750 --> 00:11:11.760 align:start position:0% different different and if they are not 00:11:11.760 --> 00:11:13.710 align:start position:0% different different and if they are not we<00:11:11.880> switch<00:11:12.160> to<00:11:12.279> the<00:11:12.480> special<00:11:12.880> case<00:11:13.440> which<00:11:13.600> I'm 00:11:13.710 --> 00:11:13.720 align:start position:0% we switch to the special case which I'm 00:11:13.720 --> 00:11:15.590 align:start position:0% we switch to the special case which I'm not<00:11:13.920> going<00:11:14.160> to<00:11:14.399> present<00:11:14.800> because<00:11:15.040> it's<00:11:15.279> very 00:11:15.590 --> 00:11:15.600 align:start position:0% not going to present because it's very 00:11:15.600 --> 00:11:17.710 align:start position:0% not going to present because it's very similar<00:11:16.040> and<00:11:16.240> doesn't<00:11:16.560> change<00:11:16.920> anything<00:11:17.519> in 00:11:17.710 --> 00:11:17.720 align:start position:0% similar and doesn't change anything in 00:11:17.720 --> 00:11:20.350 align:start position:0% similar and doesn't change anything in what<00:11:17.839> I<00:11:17.959> wanted<00:11:18.240> to<00:11:18.399> focus<00:11:18.680> on<00:11:19.000> here<00:11:19.880> assuming 00:11:20.350 --> 00:11:20.360 align:start position:0% what I wanted to focus on here assuming 00:11:20.360 --> 00:11:22.030 align:start position:0% what I wanted to focus on here assuming that<00:11:20.519> the<00:11:20.720> points<00:11:21.120> have<00:11:21.240> a<00:11:21.440> different<00:11:21.760> x 00:11:22.030 --> 00:11:22.040 align:start position:0% that the points have a different x 00:11:22.040 --> 00:11:24.230 align:start position:0% that the points have a different x coordinates<00:11:23.040> we<00:11:23.279> calculate<00:11:23.680> the<00:11:23.800> slope<00:11:24.120> of 00:11:24.230 --> 00:11:24.240 align:start position:0% coordinates we calculate the slope of 00:11:24.240 --> 00:11:27.230 align:start position:0% coordinates we calculate the slope of the<00:11:24.399> line<00:11:25.240> intersecting<00:11:25.959> these<00:11:26.120> two<00:11:26.320> points 00:11:27.230 --> 00:11:27.240 align:start position:0% the line intersecting these two points 00:11:27.240 --> 00:11:28.910 align:start position:0% the line intersecting these two points and<00:11:27.440> based<00:11:27.680> on<00:11:27.880> this<00:11:28.000> we<00:11:28.160> calculate<00:11:28.560> third 00:11:28.910 --> 00:11:28.920 align:start position:0% and based on this we calculate third 00:11:28.920 --> 00:11:29.990 align:start position:0% and based on this we calculate third point 00:11:29.990 --> 00:11:30.000 align:start position:0% point 00:11:30.000 --> 00:11:32.269 align:start position:0% point where<00:11:30.440> the<00:11:30.600> line<00:11:30.959> intersects<00:11:31.600> the<00:11:32.200> the 00:11:32.269 --> 00:11:32.279 align:start position:0% where the line intersects the the 00:11:32.279 --> 00:11:34.470 align:start position:0% where the line intersects the the elliptic<00:11:32.760> curve<00:11:33.639> the<00:11:33.760> point<00:11:34.040> addition 00:11:34.470 --> 00:11:34.480 align:start position:0% elliptic curve the point addition 00:11:34.480 --> 00:11:37.829 align:start position:0% elliptic curve the point addition definition<00:11:35.160> tells<00:11:36.000> that<00:11:36.320> at<00:11:36.480> the<00:11:36.720> last<00:11:37.000> step 00:11:37.829 --> 00:11:37.839 align:start position:0% definition tells that at the last step 00:11:37.839 --> 00:11:40.949 align:start position:0% definition tells that at the last step we<00:11:38.000> have<00:11:38.160> to<00:11:38.320> negate<00:11:38.800> the<00:11:39.000> y-coordinate<00:11:40.000> value 00:11:40.949 --> 00:11:40.959 align:start position:0% we have to negate the y-coordinate value 00:11:40.959 --> 00:11:42.949 align:start position:0% we have to negate the y-coordinate value to<00:11:41.200> get<00:11:41.399> the<00:11:41.560> final<00:11:41.920> result<00:11:42.560> this<00:11:42.680> is<00:11:42.800> the 00:11:42.949 --> 00:11:42.959 align:start position:0% to get the final result this is the 00:11:42.959 --> 00:11:44.829 align:start position:0% to get the final result this is the definition<00:11:43.480> of<00:11:43.720> of<00:11:43.839> the<00:11:44.000> point<00:11:44.240> addition<00:11:44.600> on 00:11:44.829 --> 00:11:44.839 align:start position:0% definition of of the point addition on 00:11:44.839 --> 00:11:47.430 align:start position:0% definition of of the point addition on the<00:11:45.079> on<00:11:45.200> the<00:11:45.360> elliptic<00:11:45.760> curve<00:11:46.760> uh<00:11:46.880> for<00:11:47.200> this 00:11:47.430 --> 00:11:47.440 align:start position:0% the on the elliptic curve uh for this 00:11:47.440 --> 00:11:50.470 align:start position:0% the on the elliptic curve uh for this exact<00:11:48.120> case<00:11:48.440> when<00:11:48.639> we<00:11:48.800> have<00:11:48.920> a<00:11:49.120> different<00:11:49.920> x 00:11:50.470 --> 00:11:50.480 align:start position:0% exact case when we have a different x 00:11:50.480 --> 00:11:53.949 align:start position:0% exact case when we have a different x coordinates<00:11:51.480> so<00:11:52.160> uh<00:11:52.800> this<00:11:52.959> is<00:11:53.160> simple<00:11:53.440> formula 00:11:53.949 --> 00:11:53.959 align:start position:0% coordinates so uh this is simple formula 00:11:53.959 --> 00:11:57.949 align:start position:0% coordinates so uh this is simple formula very<00:11:54.160> simple<00:11:54.720> formula<00:11:55.720> and<00:11:56.000> formula<00:11:56.760> and<00:11:57.200> uh 00:11:57.949 --> 00:11:57.959 align:start position:0% very simple formula and formula and uh 00:11:57.959 --> 00:11:59.990 align:start position:0% very simple formula and formula and uh let's<00:11:58.240> focus<00:11:58.519> on<00:11:58.720> what<00:11:59.079> and<00:11:59.240> and<00:11:59.480> how<00:11:59.639> many 00:11:59.990 --> 00:12:00.000 align:start position:0% let's focus on what and and how many 00:12:00.000 --> 00:12:03.430 align:start position:0% let's focus on what and and how many operation<00:12:00.519> we<00:12:00.680> have<00:12:00.800> to<00:12:01.360> do<00:12:02.360> uh<00:12:02.519> to<00:12:02.720> calculate 00:12:03.430 --> 00:12:03.440 align:start position:0% operation we have to do uh to calculate 00:12:03.440 --> 00:12:08.030 align:start position:0% operation we have to do uh to calculate this<00:12:04.440> so<00:12:05.240> as<00:12:05.360> we<00:12:05.519> can<00:12:05.639> see<00:12:05.959> we<00:12:06.120> have<00:12:06.399> a<00:12:06.760> like<00:12:07.720> six 00:12:08.030 --> 00:12:08.040 align:start position:0% this so as we can see we have a like six 00:12:08.040 --> 00:12:11.990 align:start position:0% this so as we can see we have a like six abstractions<00:12:09.200> subtractions<00:12:10.200> and<00:12:10.440> two 00:12:11.990 --> 00:12:12.000 align:start position:0% abstractions subtractions and two 00:12:12.000 --> 00:12:13.949 align:start position:0% abstractions subtractions and two multiplications<00:12:13.000> uh<00:12:13.199> which<00:12:13.360> are<00:12:13.560> basically 00:12:13.949 --> 00:12:13.959 align:start position:0% multiplications uh which are basically 00:12:13.959 --> 00:12:16.509 align:start position:0% multiplications uh which are basically the<00:12:14.120> operation<00:12:14.680> which<00:12:14.839> we<00:12:15.000> already<00:12:15.639> have<00:12:16.399> uh 00:12:16.509 --> 00:12:16.519 align:start position:0% the operation which we already have uh 00:12:16.519 --> 00:12:18.870 align:start position:0% the operation which we already have uh in<00:12:16.680> a<00:12:16.880> set<00:12:17.120> of<00:12:17.480> uh<00:12:17.920> of<00:12:18.040> the<00:12:18.199> evm<00:12:18.600> max 00:12:18.870 --> 00:12:18.880 align:start position:0% in a set of uh of the evm max 00:12:18.880 --> 00:12:21.269 align:start position:0% in a set of uh of the evm max instructions<00:12:19.560> but<00:12:20.079> there<00:12:20.240> is<00:12:20.360> a<00:12:20.519> one<00:12:20.880> more 00:12:21.269 --> 00:12:21.279 align:start position:0% instructions but there is a one more 00:12:21.279 --> 00:12:24.150 align:start position:0% instructions but there is a one more additional<00:12:22.120> uh<00:12:22.360> additional<00:12:23.360> operation<00:12:24.040> which 00:12:24.150 --> 00:12:24.160 align:start position:0% additional uh additional operation which 00:12:24.160 --> 00:12:27.910 align:start position:0% additional uh additional operation which is<00:12:24.360> the<00:12:24.920> division<00:12:25.920> and<00:12:26.480> basically<00:12:27.480> uh<00:12:27.680> it's 00:12:27.910 --> 00:12:27.920 align:start position:0% is the division and basically uh it's 00:12:27.920 --> 00:12:31.430 align:start position:0% is the division and basically uh it's it's<00:12:28.160> marked<00:12:28.720> with<00:12:28.920> the<00:12:29.360> with<00:12:29.560> the<00:12:30.040> red<00:12:30.440> color 00:12:31.430 --> 00:12:31.440 align:start position:0% it's marked with the with the red color 00:12:31.440 --> 00:12:33.750 align:start position:0% it's marked with the with the red color so<00:12:31.760> but<00:12:31.959> let's<00:12:32.279> get<00:12:32.519> deeper<00:12:33.279> a<00:12:33.360> little<00:12:33.560> bit 00:12:33.750 --> 00:12:33.760 align:start position:0% so but let's get deeper a little bit 00:12:33.760 --> 00:12:37.750 align:start position:0% so but let's get deeper a little bit deeper<00:12:34.639> um<00:12:35.360> what<00:12:36.279> uh<00:12:36.480> what<00:12:36.639> the<00:12:37.000> how<00:12:37.240> how<00:12:37.360> the 00:12:37.750 --> 00:12:37.760 align:start position:0% deeper um what uh what the how how the 00:12:37.760 --> 00:12:41.189 align:start position:0% deeper um what uh what the how how the division<00:12:38.760> uh<00:12:39.079> can<00:12:39.240> be<00:12:39.440> calculated<00:12:40.079> in<00:12:40.199> modular 00:12:41.189 --> 00:12:41.199 align:start position:0% division uh can be calculated in modular 00:12:41.199 --> 00:12:44.550 align:start position:0% division uh can be calculated in modular arithmetic<00:12:42.199> so<00:12:42.440> as<00:12:42.519> you<00:12:43.040> expected<00:12:44.040> it's<00:12:44.279> very 00:12:44.550 --> 00:12:44.560 align:start position:0% arithmetic so as you expected it's very 00:12:44.560 --> 00:12:47.269 align:start position:0% arithmetic so as you expected it's very expensive<00:12:45.560> and<00:12:45.720> it's<00:12:46.480> uh<00:12:46.839> it's<00:12:47.040> very 00:12:47.269 --> 00:12:47.279 align:start position:0% expensive and it's uh it's very 00:12:47.279 --> 00:12:50.509 align:start position:0% expensive and it's uh it's very expensive<00:12:47.800> and<00:12:48.000> if<00:12:48.160> you<00:12:49.160> uh<00:12:49.480> if<00:12:49.600> you<00:12:49.880> use<00:12:50.240> some 00:12:50.509 --> 00:12:50.519 align:start position:0% expensive and if you uh if you use some 00:12:50.519 --> 00:12:52.910 align:start position:0% expensive and if you uh if you use some well-known<00:12:51.160> method<00:12:51.639> to<00:12:51.920> calculate<00:12:52.720> this 00:12:52.910 --> 00:12:52.920 align:start position:0% well-known method to calculate this 00:12:52.920 --> 00:12:55.790 align:start position:0% well-known method to calculate this using<00:12:53.279> adchain<00:12:53.800> for<00:12:53.920> example<00:12:54.279> T<00:12:55.079> it<00:12:55.240> requires 00:12:55.790 --> 00:12:55.800 align:start position:0% using adchain for example T it requires 00:12:55.800 --> 00:12:58.590 align:start position:0% using adchain for example T it requires about<00:12:56.120> 300<00:12:56.920> multiplications<00:12:57.920> so<00:12:58.160> comparing 00:12:58.590 --> 00:12:58.600 align:start position:0% about 300 multiplications so comparing 00:12:58.600 --> 00:13:00.710 align:start position:0% about 300 multiplications so comparing to<00:12:59.320> six<00:12:59.720> we<00:12:59.880> have<00:13:00.199> uh<00:13:00.320> sorry<00:13:00.560> two 00:13:00.710 --> 00:13:00.720 align:start position:0% to six we have uh sorry two 00:13:00.720 --> 00:13:02.269 align:start position:0% to six we have uh sorry two multiplications<00:13:01.440> we<00:13:01.560> have<00:13:01.720> on<00:13:01.800> the<00:13:01.959> previous 00:13:02.269 --> 00:13:02.279 align:start position:0% multiplications we have on the previous 00:13:02.279 --> 00:13:03.990 align:start position:0% multiplications we have on the previous slides<00:13:02.880> it's 00:13:03.990 --> 00:13:04.000 align:start position:0% slides it's 00:13:04.000 --> 00:13:07.150 align:start position:0% slides it's 300<00:13:05.000> uh<00:13:05.560> to<00:13:05.760> calculate<00:13:06.199> the<00:13:06.360> division<00:13:06.680> in<00:13:06.880> the 00:13:07.150 --> 00:13:07.160 align:start position:0% 300 uh to calculate the division in the 00:13:07.160 --> 00:13:09.230 align:start position:0% 300 uh to calculate the division in the in<00:13:07.279> the<00:13:07.440> arithmetic<00:13:08.279> uh<00:13:08.720> in<00:13:08.800> modular 00:13:09.230 --> 00:13:09.240 align:start position:0% in the arithmetic uh in modular 00:13:09.240 --> 00:13:11.509 align:start position:0% in the arithmetic uh in modular arithmetic<00:13:10.240> but<00:13:10.440> the<00:13:10.600> good<00:13:10.800> thing<00:13:11.040> is<00:13:11.199> that<00:13:11.360> in 00:13:11.509 --> 00:13:11.519 align:start position:0% arithmetic but the good thing is that in 00:13:11.519 --> 00:13:15.670 align:start position:0% arithmetic but the good thing is that in real<00:13:11.800> world<00:13:12.680> we<00:13:12.880> want<00:13:13.120> to<00:13:13.839> uh<00:13:14.199> we<00:13:14.839> want<00:13:15.000> to<00:13:15.279> add 00:13:15.670 --> 00:13:15.680 align:start position:0% real world we want to uh we want to add 00:13:15.680 --> 00:13:17.829 align:start position:0% real world we want to uh we want to add more<00:13:16.079> points<00:13:16.680> to<00:13:16.880> do 00:13:17.829 --> 00:13:17.839 align:start position:0% more points to do 00:13:17.839 --> 00:13:20.629 align:start position:0% more points to do this<00:13:18.839> sorry<00:13:19.279> so<00:13:19.600> but<00:13:19.720> in<00:13:19.880> real<00:13:20.120> world<00:13:20.399> when<00:13:20.519> we 00:13:20.629 --> 00:13:20.639 align:start position:0% this sorry so but in real world when we 00:13:20.639 --> 00:13:23.189 align:start position:0% this sorry so but in real world when we are<00:13:20.800> adding<00:13:21.240> more<00:13:21.560> points<00:13:22.160> so<00:13:22.680> the<00:13:22.800> sequence 00:13:23.189 --> 00:13:23.199 align:start position:0% are adding more points so the sequence 00:13:23.199 --> 00:13:28.590 align:start position:0% are adding more points so the sequence of<00:13:23.680> points<00:13:24.680> uh<00:13:25.199> we<00:13:25.399> will<00:13:25.800> we<00:13:26.600> never<00:13:27.600> uh<00:13:28.160> make<00:13:28.399> a 00:13:28.590 --> 00:13:28.600 align:start position:0% of points uh we will we never uh make a 00:13:28.600 --> 00:13:31.389 align:start position:0% of points uh we will we never uh make a division<00:13:29.199> every<00:13:29.760> every<00:13:30.040> addition<00:13:30.639> we<00:13:30.800> we<00:13:30.920> do 00:13:31.389 --> 00:13:31.399 align:start position:0% division every every addition we we do 00:13:31.399 --> 00:13:35.350 align:start position:0% division every every addition we we do so<00:13:32.120> so<00:13:32.880> like<00:13:33.480> no<00:13:33.920> so<00:13:34.440> every<00:13:34.639> two<00:13:34.880> points<00:13:35.199> we 00:13:35.350 --> 00:13:35.360 align:start position:0% so so like no so every two points we 00:13:35.360 --> 00:13:38.230 align:start position:0% so so like no so every two points we don't<00:13:35.560> do<00:13:35.839> every<00:13:36.079> division<00:13:37.040> uh<00:13:37.600> at<00:13:37.800> at<00:13:37.920> any 00:13:38.230 --> 00:13:38.240 align:start position:0% don't do every division uh at at any 00:13:38.240 --> 00:13:41.629 align:start position:0% don't do every division uh at at any step<00:13:39.240> because<00:13:39.959> it<00:13:40.120> can<00:13:40.360> be<00:13:40.639> it<00:13:40.760> can<00:13:40.880> be<00:13:41.040> done<00:13:41.199> in 00:13:41.629 --> 00:13:41.639 align:start position:0% step because it can be it can be done in 00:13:41.639 --> 00:13:45.069 align:start position:0% step because it can be it can be done in different<00:13:42.040> way<00:13:42.399> which<00:13:42.720> allows<00:13:43.120> to<00:13:43.680> make<00:13:44.680> one 00:13:45.069 --> 00:13:45.079 align:start position:0% different way which allows to make one 00:13:45.079 --> 00:13:48.069 align:start position:0% different way which allows to make one division<00:13:45.480> at<00:13:45.680> most<00:13:46.040> if<00:13:46.279> ever<00:13:46.519> needed<00:13:47.399> if<00:13:47.519> any 00:13:48.069 --> 00:13:48.079 align:start position:0% division at most if ever needed if any 00:13:48.079 --> 00:13:51.590 align:start position:0% division at most if ever needed if any needed<00:13:49.079> so<00:13:50.040> so<00:13:50.320> with<00:13:50.480> VM<00:13:50.920> Max<00:13:51.160> we<00:13:51.279> would<00:13:51.440> be 00:13:51.590 --> 00:13:51.600 align:start position:0% needed so so with VM Max we would be 00:13:51.600 --> 00:13:53.389 align:start position:0% needed so so with VM Max we would be able<00:13:51.880> to<00:13:52.000> implement<00:13:52.440> the<00:13:52.560> points<00:13:52.800> addition<00:13:53.279> in 00:13:53.389 --> 00:13:53.399 align:start position:0% able to implement the points addition in 00:13:53.399 --> 00:13:55.269 align:start position:0% able to implement the points addition in the<00:13:53.600> optimal<00:13:54.040> way<00:13:54.279> without<00:13:54.639> redundant 00:13:55.269 --> 00:13:55.279 align:start position:0% the optimal way without redundant 00:13:55.279 --> 00:13:58.189 align:start position:0% the optimal way without redundant operations<00:13:56.079> and<00:13:56.399> return<00:13:56.639> the<00:13:56.759> results<00:13:57.120> in<00:13:57.399> any 00:13:58.189 --> 00:13:58.199 align:start position:0% operations and return the results in any 00:13:58.199 --> 00:14:02.470 align:start position:0% operations and return the results in any form<00:13:58.800> need<00:13:59.240> did<00:13:59.440> for<00:13:59.600> a<00:13:59.800> specific<00:14:00.399> case<00:14:01.480> so 00:14:02.470 --> 00:14:02.480 align:start position:0% form need did for a specific case so 00:14:02.480 --> 00:14:03.670 align:start position:0% form need did for a specific case so yeah 00:14:03.670 --> 00:14:03.680 align:start position:0% yeah 00:14:03.680 --> 00:14:06.550 align:start position:0% yeah so<00:14:04.680> sorry<00:14:05.279> let's<00:14:05.519> get<00:14:05.800> back<00:14:05.959> to<00:14:06.120> this<00:14:06.279> slide 00:14:06.550 --> 00:14:06.560 align:start position:0% so sorry let's get back to this slide 00:14:06.560 --> 00:14:09.670 align:start position:0% so sorry let's get back to this slide once<00:14:06.759> again<00:14:07.440> so<00:14:07.839> the<00:14:08.120> the<00:14:08.920> the<00:14:09.040> solution<00:14:09.480> is 00:14:09.670 --> 00:14:09.680 align:start position:0% once again so the the the solution is 00:14:09.680 --> 00:14:12.069 align:start position:0% once again so the the the solution is just<00:14:09.880> to<00:14:10.720> one<00:14:10.920> of<00:14:11.160> possible<00:14:11.480> solution<00:14:11.800> is<00:14:11.959> just 00:14:12.069 --> 00:14:12.079 align:start position:0% just to one of possible solution is just 00:14:12.079 --> 00:14:14.590 align:start position:0% just to one of possible solution is just to<00:14:12.240> use<00:14:12.560> in<00:14:12.839> different<00:14:13.399> coordinate<00:14:14.000> system 00:14:14.590 --> 00:14:14.600 align:start position:0% to use in different coordinate system 00:14:14.600 --> 00:14:16.629 align:start position:0% to use in different coordinate system like<00:14:14.759> for<00:14:14.920> example<00:14:15.360> projective<00:14:15.880> for<00:14:16.120> Jacobian 00:14:16.629 --> 00:14:16.639 align:start position:0% like for example projective for Jacobian 00:14:16.639 --> 00:14:19.710 align:start position:0% like for example projective for Jacobian coordinate<00:14:17.240> system<00:14:18.000> but<00:14:18.199> also<00:14:18.519> there<00:14:18.639> are<00:14:19.279> uh 00:14:19.710 --> 00:14:19.720 align:start position:0% coordinate system but also there are uh 00:14:19.720 --> 00:14:23.350 align:start position:0% coordinate system but also there are uh algorithm<00:14:20.639> who<00:14:21.040> which<00:14:21.680> add<00:14:22.440> a<00:14:22.600> sequence<00:14:23.079> of 00:14:23.350 --> 00:14:23.360 align:start position:0% algorithm who which add a sequence of 00:14:23.360 --> 00:14:26.430 align:start position:0% algorithm who which add a sequence of points<00:14:24.360> uh<00:14:24.480> in<00:14:24.680> aine<00:14:25.279> coordinates<00:14:26.120> and<00:14:26.279> you 00:14:26.430 --> 00:14:26.440 align:start position:0% points uh in aine coordinates and you 00:14:26.440 --> 00:14:30.629 align:start position:0% points uh in aine coordinates and you can<00:14:26.839> make<00:14:27.079> a<00:14:27.240> one<00:14:27.600> division<00:14:28.160> in<00:14:28.320> the<00:14:28.440> end 00:14:30.629 --> 00:14:30.639 align:start position:0% can make a one division in the end 00:14:30.639 --> 00:14:32.990 align:start position:0% can make a one division in the end so<00:14:31.360> but<00:14:31.560> what<00:14:31.680> are<00:14:31.839> the<00:14:32.000> benefits<00:14:32.360> of<00:14:32.480> EV<00:14:32.800> Max 00:14:32.990 --> 00:14:33.000 align:start position:0% so but what are the benefits of EV Max 00:14:33.000 --> 00:14:35.189 align:start position:0% so but what are the benefits of EV Max over<00:14:33.279> promiles<00:14:34.120> first<00:14:34.320> of 00:14:35.189 --> 00:14:35.199 align:start position:0% over promiles first of 00:14:35.199 --> 00:14:37.829 align:start position:0% over promiles first of all<00:14:36.199> uh<00:14:36.440> we<00:14:36.600> improve<00:14:37.000> efficiency<00:14:37.480> because<00:14:37.680> of 00:14:37.829 --> 00:14:37.839 align:start position:0% all uh we improve efficiency because of 00:14:37.839 --> 00:14:40.389 align:start position:0% all uh we improve efficiency because of the<00:14:37.920> reason<00:14:38.320> I<00:14:38.440> already<00:14:39.000> mentioned<00:14:40.000> we<00:14:40.160> have 00:14:40.389 --> 00:14:40.399 align:start position:0% the reason I already mentioned we have 00:14:40.399 --> 00:14:43.189 align:start position:0% the reason I already mentioned we have also<00:14:40.680> more<00:14:41.440> flexibility<00:14:42.440> uh<00:14:42.560> because<00:14:42.839> we<00:14:42.959> can 00:14:43.189 --> 00:14:43.199 align:start position:0% also more flexibility uh because we can 00:14:43.199 --> 00:14:45.150 align:start position:0% also more flexibility uh because we can implement<00:14:43.720> the<00:14:43.880> cryptographic<00:14:44.560> algorith 00:14:45.150 --> 00:14:45.160 align:start position:0% implement the cryptographic algorith 00:14:45.160 --> 00:14:47.670 align:start position:0% implement the cryptographic algorith according<00:14:45.440> to<00:14:45.600> the<00:14:45.839> specific<00:14:46.279> needs<00:14:47.199> we<00:14:47.360> also 00:14:47.670 --> 00:14:47.680 align:start position:0% according to the specific needs we also 00:14:47.680 --> 00:14:49.550 align:start position:0% according to the specific needs we also improve<00:14:48.199> security<00:14:48.800> as<00:14:48.920> we<00:14:49.079> mitigate 00:14:49.550 --> 00:14:49.560 align:start position:0% improve security as we mitigate 00:14:49.560 --> 00:14:52.069 align:start position:0% improve security as we mitigate potential<00:14:49.959> consensus<00:14:50.519> risk<00:14:51.360> the<00:14:51.560> complexity 00:14:52.069 --> 00:14:52.079 align:start position:0% potential consensus risk the complexity 00:14:52.079 --> 00:14:54.030 align:start position:0% potential consensus risk the complexity of<00:14:52.199> the<00:14:52.320> precompile<00:14:52.880> implementation<00:14:53.560> details 00:14:54.030 --> 00:14:54.040 align:start position:0% of the precompile implementation details 00:14:54.040 --> 00:14:56.470 align:start position:0% of the precompile implementation details is<00:14:54.160> moved<00:14:54.600> from<00:14:54.839> the<00:14:55.000> evm<00:14:55.639> to<00:14:55.839> the<00:14:55.959> smart 00:14:56.470 --> 00:14:56.480 align:start position:0% is moved from the evm to the smart 00:14:56.480 --> 00:15:00.189 align:start position:0% is moved from the evm to the smart contract<00:14:57.480> and<00:14:57.839> last<00:14:58.079> but<00:14:58.279> not<00:14:58.519> least 00:15:00.189 --> 00:15:00.199 align:start position:0% contract and last but not least 00:15:00.199 --> 00:15:03.269 align:start position:0% contract and last but not least again<00:15:01.199> project<00:15:01.639> can<00:15:01.839> and<00:15:02.040> last<00:15:02.360> but<00:15:02.959> sorry 00:15:03.269 --> 00:15:03.279 align:start position:0% again project can and last but sorry 00:15:03.279 --> 00:15:05.430 align:start position:0% again project can and last but sorry where<00:15:03.440> was<00:15:03.600> it<00:15:04.240> okay<00:15:04.399> and<00:15:04.600> last<00:15:04.800> but<00:15:04.959> not<00:15:05.120> least 00:15:05.430 --> 00:15:05.440 align:start position:0% where was it okay and last but not least 00:15:05.440 --> 00:15:07.389 align:start position:0% where was it okay and last but not least project<00:15:05.720> can<00:15:05.920> deliver<00:15:06.320> functionality<00:15:07.000> they 00:15:07.389 --> 00:15:07.399 align:start position:0% project can deliver functionality they 00:15:07.399 --> 00:15:10.550 align:start position:0% project can deliver functionality they need<00:15:08.399> faster<00:15:08.959> not<00:15:09.240> waiting<00:15:09.680> until<00:15:10.120> the 00:15:10.550 --> 00:15:10.560 align:start position:0% need faster not waiting until the 00:15:10.560 --> 00:15:12.670 align:start position:0% need faster not waiting until the specific<00:15:11.040> promiles<00:15:11.759> will<00:15:11.959> be<00:15:12.160> processed<00:15:12.560> and 00:15:12.670 --> 00:15:12.680 align:start position:0% specific promiles will be processed and 00:15:12.680 --> 00:15:14.509 align:start position:0% specific promiles will be processed and delivered<00:15:13.079> to<00:15:13.199> the 00:15:14.509 --> 00:15:14.519 align:start position:0% delivered to the 00:15:14.519 --> 00:15:17.030 align:start position:0% delivered to the mine<00:15:15.519> so<00:15:15.720> as<00:15:15.839> a<00:15:16.000> summary<00:15:16.399> I<00:15:16.480> would<00:15:16.680> like<00:15:16.839> to 00:15:17.030 --> 00:15:17.040 align:start position:0% mine so as a summary I would like to 00:15:17.040 --> 00:15:19.150 align:start position:0% mine so as a summary I would like to give<00:15:17.160> you<00:15:17.360> an<00:15:17.560> update<00:15:17.920> of<00:15:18.120> what<00:15:18.240> we<00:15:18.399> did<00:15:18.600> till 00:15:19.150 --> 00:15:19.160 align:start position:0% give you an update of what we did till 00:15:19.160 --> 00:15:22.550 align:start position:0% give you an update of what we did till now<00:15:20.160> so<00:15:20.480> we<00:15:20.680> prepared<00:15:21.120> a<00:15:21.240> bunch<00:15:21.480> of<00:15:21.600> aips<00:15:22.399> and 00:15:22.550 --> 00:15:22.560 align:start position:0% now so we prepared a bunch of aips and 00:15:22.560 --> 00:15:25.310 align:start position:0% now so we prepared a bunch of aips and more<00:15:23.040> IPS<00:15:23.320> are<00:15:23.480> in<00:15:23.720> progress<00:15:24.560> we<00:15:24.680> have<00:15:25.120> an 00:15:25.310 --> 00:15:25.320 align:start position:0% more IPS are in progress we have an 00:15:25.320 --> 00:15:27.550 align:start position:0% more IPS are in progress we have an experimental<00:15:26.000> implementation<00:15:26.639> of<00:15:26.920> VM<00:15:27.240> Max 00:15:27.550 --> 00:15:27.560 align:start position:0% experimental implementation of VM Max 00:15:27.560 --> 00:15:30.150 align:start position:0% experimental implementation of VM Max instructions<00:15:28.160> support<00:15:28.560> in<00:15:28.680> the<00:15:29.040> vm1<00:15:29.639> so<00:15:29.880> our 00:15:30.150 --> 00:15:30.160 align:start position:0% instructions support in the vm1 so our 00:15:30.160 --> 00:15:33.629 align:start position:0% instructions support in the vm1 so our project<00:15:30.600> we<00:15:31.600> um<00:15:31.959> we<00:15:32.160> develop<00:15:33.040> from<00:15:33.279> a<00:15:33.399> very 00:15:33.629 --> 00:15:33.639 align:start position:0% project we um we develop from a very 00:15:33.639 --> 00:15:36.350 align:start position:0% project we um we develop from a very long<00:15:34.199> time<00:15:35.199> and<00:15:35.399> on<00:15:35.639> top<00:15:35.839> of<00:15:36.040> this<00:15:36.240> we 00:15:36.350 --> 00:15:36.360 align:start position:0% long time and on top of this we 00:15:36.360 --> 00:15:38.550 align:start position:0% long time and on top of this we implemented<00:15:36.959> a<00:15:37.079> couple<00:15:37.279> of<00:15:37.440> promiles<00:15:38.319> by 00:15:38.550 --> 00:15:38.560 align:start position:0% implemented a couple of promiles by 00:15:38.560 --> 00:15:40.710 align:start position:0% implemented a couple of promiles by generating<00:15:39.160> evm<00:15:39.600> Max<00:15:39.839> bite<00:15:40.160> code<00:15:40.399> and<00:15:40.519> it 00:15:40.710 --> 00:15:40.720 align:start position:0% generating evm Max bite code and it 00:15:40.720 --> 00:15:42.870 align:start position:0% generating evm Max bite code and it appeared<00:15:41.560> that<00:15:41.759> the<00:15:41.880> implementation<00:15:42.680> is 00:15:42.870 --> 00:15:42.880 align:start position:0% appeared that the implementation is 00:15:42.880 --> 00:15:45.030 align:start position:0% appeared that the implementation is faster<00:15:43.279> than<00:15:43.519> implementation<00:15:44.160> in<00:15:44.319> libff 00:15:45.030 --> 00:15:45.040 align:start position:0% faster than implementation in libff 00:15:45.040 --> 00:15:47.189 align:start position:0% faster than implementation in libff which<00:15:45.160> is<00:15:45.319> still<00:15:45.800> being<00:15:46.120> used<00:15:46.480> by<00:15:46.680> some<00:15:46.880> of<00:15:47.040> the 00:15:47.189 --> 00:15:47.199 align:start position:0% which is still being used by some of the 00:15:47.199 --> 00:15:50.949 align:start position:0% which is still being used by some of the execution<00:15:48.160> clients<00:15:49.160> honestly<00:15:49.720> Li<00:15:50.279> is<00:15:50.399> not<00:15:50.800> the 00:15:50.949 --> 00:15:50.959 align:start position:0% execution clients honestly Li is not the 00:15:50.959 --> 00:15:53.230 align:start position:0% execution clients honestly Li is not the the<00:15:51.120> fast<00:15:51.560> the<00:15:51.680> fastest<00:15:52.040> Library<00:15:52.560> available 00:15:53.230 --> 00:15:53.240 align:start position:0% the fast the fastest Library available 00:15:53.240 --> 00:15:55.910 align:start position:0% the fast the fastest Library available but<00:15:53.880> but<00:15:54.319> but<00:15:54.480> it's<00:15:54.639> still<00:15:54.880> used<00:15:55.319> to<00:15:55.720> to 00:15:55.910 --> 00:15:55.920 align:start position:0% but but but it's still used to to 00:15:55.920 --> 00:15:59.030 align:start position:0% but but but it's still used to to implement<00:15:56.480> the<00:15:57.079> existing<00:15:57.480> promis<00:15:58.240> already<00:15:58.639> by 00:15:59.030 --> 00:15:59.040 align:start position:0% implement the existing promis already by 00:15:59.040 --> 00:16:01.389 align:start position:0% implement the existing promis already by some<00:15:59.319> some<00:15:59.519> clients<00:16:00.440> and<00:16:00.680> thanks<00:16:00.920> to<00:16:01.040> Jared 00:16:01.389 --> 00:16:01.399 align:start position:0% some some clients and thanks to Jared 00:16:01.399 --> 00:16:04.110 align:start position:0% some some clients and thanks to Jared from<00:16:01.680> GFF<00:16:02.279> team<00:16:02.639> we<00:16:02.839> also<00:16:03.240> recently<00:16:03.720> prepared 00:16:04.110 --> 00:16:04.120 align:start position:0% from GFF team we also recently prepared 00:16:04.120 --> 00:16:07.350 align:start position:0% from GFF team we also recently prepared a<00:16:04.279> draft<00:16:04.759> of<00:16:05.319> of<00:16:05.440> the<00:16:05.680> specification<00:16:06.639> of<00:16:07.199> the 00:16:07.350 --> 00:16:07.360 align:start position:0% a draft of of the specification of the 00:16:07.360 --> 00:16:10.389 align:start position:0% a draft of of the specification of the vectorized<00:16:08.000> version<00:16:08.319> of<00:16:08.480> evm<00:16:08.880> Max<00:16:09.160> up<00:16:09.399> code 00:16:10.389 --> 00:16:10.399 align:start position:0% vectorized version of evm Max up code 00:16:10.399 --> 00:16:12.870 align:start position:0% vectorized version of evm Max up code which<00:16:10.519> is<00:16:10.720> a<00:16:11.560> direction<00:16:12.079> we<00:16:12.240> wanted<00:16:12.639> to 00:16:12.870 --> 00:16:12.880 align:start position:0% which is a direction we wanted to 00:16:12.880 --> 00:16:14.790 align:start position:0% which is a direction we wanted to investigate<00:16:13.560> in<00:16:13.759> a<00:16:14.000> as<00:16:14.120> a<00:16:14.319> potential 00:16:14.790 --> 00:16:14.800 align:start position:0% investigate in a as a potential 00:16:14.800 --> 00:16:16.749 align:start position:0% investigate in a as a potential Improvement<00:16:15.399> of<00:16:15.600> efficiency<00:16:16.480> of<00:16:16.639> the 00:16:16.749 --> 00:16:16.759 align:start position:0% Improvement of efficiency of the 00:16:16.759 --> 00:16:18.910 align:start position:0% Improvement of efficiency of the implementation<00:16:17.360> of<00:16:17.480> the<00:16:17.639> posidon<00:16:18.560> hash 00:16:18.910 --> 00:16:18.920 align:start position:0% implementation of the posidon hash 00:16:18.920 --> 00:16:21.590 align:start position:0% implementation of the posidon hash function<00:16:19.639> and<00:16:19.839> smaller<00:16:20.199> modulus 00:16:21.590 --> 00:16:21.600 align:start position:0% function and smaller modulus 00:16:21.600 --> 00:16:25.670 align:start position:0% function and smaller modulus setup<00:16:22.600> so<00:16:23.079> what<00:16:23.519> what<00:16:23.839> we<00:16:24.000> plan<00:16:24.279> to<00:16:24.399> do<00:16:24.639> next<00:16:25.560> we 00:16:25.670 --> 00:16:25.680 align:start position:0% setup so what what we plan to do next we 00:16:25.680 --> 00:16:28.590 align:start position:0% setup so what what we plan to do next we need<00:16:26.319> uh<00:16:26.519> more<00:16:26.759> use<00:16:27.120> cases<00:16:27.480> for<00:16:27.680> sure<00:16:28.279> to<00:16:28.440> make 00:16:28.590 --> 00:16:28.600 align:start position:0% need uh more use cases for sure to make 00:16:28.600 --> 00:16:31.069 align:start position:0% need uh more use cases for sure to make sure<00:16:29.079> that<00:16:29.560> uh<00:16:29.839> that<00:16:30.040> the<00:16:30.160> spec<00:16:30.480> is<00:16:30.680> correct 00:16:31.069 --> 00:16:31.079 align:start position:0% sure that uh that the spec is correct 00:16:31.079 --> 00:16:33.790 align:start position:0% sure that uh that the spec is correct and<00:16:31.240> the<00:16:31.360> API<00:16:31.800> is<00:16:32.199> convenient<00:16:33.199> uh<00:16:33.319> we<00:16:33.480> plan 00:16:33.790 --> 00:16:33.800 align:start position:0% and the API is convenient uh we plan 00:16:33.800 --> 00:16:35.509 align:start position:0% and the API is convenient uh we plan also<00:16:34.040> to<00:16:34.199> start<00:16:34.519> supporting<00:16:35.079> different 00:16:35.509 --> 00:16:35.519 align:start position:0% also to start supporting different 00:16:35.519 --> 00:16:38.189 align:start position:0% also to start supporting different models<00:16:36.519> which<00:16:36.920> values<00:16:37.399> which<00:16:37.600> will<00:16:38.040> which 00:16:38.189 --> 00:16:38.199 align:start position:0% models which values which will which 00:16:38.199 --> 00:16:40.949 align:start position:0% models which values which will which will<00:16:38.399> be<00:16:38.560> the<00:16:38.720> power<00:16:39.000> of<00:16:39.160> two<00:16:40.120> some<00:16:40.440> attention 00:16:40.949 --> 00:16:40.959 align:start position:0% will be the power of two some attention 00:16:40.959 --> 00:16:44.629 align:start position:0% will be the power of two some attention also<00:16:41.319> and<00:16:41.560> research<00:16:42.199> on<00:16:42.399> SD<00:16:43.120> s<00:16:43.639> IMD 00:16:44.629 --> 00:16:44.639 align:start position:0% also and research on SD s IMD 00:16:44.639 --> 00:16:47.790 align:start position:0% also and research on SD s IMD instructions<00:16:45.360> is<00:16:45.560> also<00:16:46.199> uh<00:16:46.759> sorry<00:16:47.079> extension 00:16:47.790 --> 00:16:47.800 align:start position:0% instructions is also uh sorry extension 00:16:47.800 --> 00:16:50.269 align:start position:0% instructions is also uh sorry extension it's<00:16:47.959> also<00:16:48.240> required<00:16:48.639> to<00:16:48.920> utilize<00:16:49.920> uh<00:16:50.079> this 00:16:50.269 --> 00:16:50.279 align:start position:0% it's also required to utilize uh this 00:16:50.279 --> 00:16:52.590 align:start position:0% it's also required to utilize uh this extension<00:16:50.800> if<00:16:50.920> it<00:16:51.079> gives<00:16:51.480> measurable<00:16:52.480> uh 00:16:52.590 --> 00:16:52.600 align:start position:0% extension if it gives measurable uh 00:16:52.600 --> 00:16:53.710 align:start position:0% extension if it gives measurable uh measurable 00:16:53.710 --> 00:16:53.720 align:start position:0% measurable 00:16:53.720 --> 00:16:56.949 align:start position:0% measurable benefits<00:16:54.720> uh<00:16:55.000> regarding<00:16:55.480> the<00:16:55.720> tooling<00:16:56.720> uh<00:16:56.800> we 00:16:56.949 --> 00:16:56.959 align:start position:0% benefits uh regarding the tooling uh we 00:16:56.959 --> 00:16:59.509 align:start position:0% benefits uh regarding the tooling uh we work<00:16:57.199> on<00:16:57.399> supporting<00:16:57.880> evm<00:16:58.360> Max<00:16:58.680> in<00:16:59.240> higher 00:16:59.509 --> 00:16:59.519 align:start position:0% work on supporting evm Max in higher 00:16:59.519 --> 00:17:02.670 align:start position:0% work on supporting evm Max in higher level<00:16:59.959> languages<00:17:00.959> like<00:17:01.160> for<00:17:01.319> example<00:17:01.720> youu<00:17:02.319> or 00:17:02.670 --> 00:17:02.680 align:start position:0% level languages like for example youu or 00:17:02.680 --> 00:17:03.510 align:start position:0% level languages like for example youu or or 00:17:03.510 --> 00:17:03.520 align:start position:0% or 00:17:03.520 --> 00:17:06.669 align:start position:0% or half<00:17:04.520> uh<00:17:05.039> we<00:17:05.199> haven't<00:17:05.480> choosed<00:17:05.959> yet<00:17:06.199> which<00:17:06.400> one 00:17:06.669 --> 00:17:06.679 align:start position:0% half uh we haven't choosed yet which one 00:17:06.679 --> 00:17:09.150 align:start position:0% half uh we haven't choosed yet which one but<00:17:06.959> now<00:17:07.160> we<00:17:07.240> are<00:17:07.520> very<00:17:07.760> close<00:17:08.039> to<00:17:08.679> very<00:17:08.880> close 00:17:09.150 --> 00:17:09.160 align:start position:0% but now we are very close to very close 00:17:09.160 --> 00:17:12.750 align:start position:0% but now we are very close to very close to<00:17:09.439> to<00:17:09.640> to<00:17:09.799> start<00:17:10.120> with<00:17:10.520> fuel<00:17:11.520> we<00:17:11.679> plan<00:17:12.039> also<00:17:12.439> to 00:17:12.750 --> 00:17:12.760 align:start position:0% to to to start with fuel we plan also to 00:17:12.760 --> 00:17:14.909 align:start position:0% to to to start with fuel we plan also to research<00:17:13.280> the<00:17:13.439> idea<00:17:13.720> of<00:17:13.839> using<00:17:14.120> KVM<00:17:14.559> Max 00:17:14.909 --> 00:17:14.919 align:start position:0% research the idea of using KVM Max 00:17:14.919 --> 00:17:17.590 align:start position:0% research the idea of using KVM Max biteco<00:17:15.439> as<00:17:15.520> a<00:17:15.679> spec<00:17:16.039> language<00:17:16.959> as<00:17:17.039> I<00:17:17.160> mentioned 00:17:17.590 --> 00:17:17.600 align:start position:0% biteco as a spec language as I mentioned 00:17:17.600 --> 00:17:19.990 align:start position:0% biteco as a spec language as I mentioned already<00:17:18.480> uh<00:17:18.600> for<00:17:18.760> the<00:17:18.919> pre<00:17:19.199> compiles<00:17:19.640> if<00:17:19.799> they 00:17:19.990 --> 00:17:20.000 align:start position:0% already uh for the pre compiles if they 00:17:20.000 --> 00:17:23.390 align:start position:0% already uh for the pre compiles if they still<00:17:20.319> will<00:17:20.679> be<00:17:20.839> needed<00:17:21.240> for<00:17:21.679> any<00:17:22.199> reason<00:17:23.199> uh 00:17:23.390 --> 00:17:23.400 align:start position:0% still will be needed for any reason uh 00:17:23.400 --> 00:17:25.110 align:start position:0% still will be needed for any reason uh it<00:17:23.520> should<00:17:23.799> also<00:17:24.120> result<00:17:24.439> in<00:17:24.559> a<00:17:24.720> tool<00:17:24.919> to 00:17:25.110 --> 00:17:25.120 align:start position:0% it should also result in a tool to 00:17:25.120 --> 00:17:28.110 align:start position:0% it should also result in a tool to transpile<00:17:26.039> this<00:17:26.199> evm<00:17:26.600> Max<00:17:26.919> bite<00:17:27.199> code<00:17:27.880> to 00:17:28.110 --> 00:17:28.120 align:start position:0% transpile this evm Max bite code to 00:17:28.120 --> 00:17:30.549 align:start position:0% transpile this evm Max bite code to higher<00:17:28.400> level<00:17:28.640> Lang<00:17:28.919> language<00:17:29.760> so<00:17:30.080> opposite 00:17:30.549 --> 00:17:30.559 align:start position:0% higher level Lang language so opposite 00:17:30.559 --> 00:17:33.150 align:start position:0% higher level Lang language so opposite basically<00:17:30.960> opposite<00:17:31.440> way<00:17:32.440> uh<00:17:32.679> which<00:17:32.840> can<00:17:33.000> be 00:17:33.150 --> 00:17:33.160 align:start position:0% basically opposite way uh which can be 00:17:33.160 --> 00:17:36.029 align:start position:0% basically opposite way uh which can be used<00:17:33.840> as<00:17:33.960> a<00:17:34.160> pre<00:17:34.440> compile<00:17:35.080> future<00:17:35.480> pre<00:17:35.720> compile 00:17:36.029 --> 00:17:36.039 align:start position:0% used as a pre compile future pre compile 00:17:36.039 --> 00:17:39.590 align:start position:0% used as a pre compile future pre compile implementation<00:17:36.720> by<00:17:36.919> the<00:17:37.039> execution 00:17:39.590 --> 00:17:39.600 align:start position:0% 00:17:39.600 --> 00:17:43.270 align:start position:0% clients<00:17:40.600> yeah<00:17:40.840> so<00:17:41.440> uh<00:17:42.160> so<00:17:42.400> regarding<00:17:42.880> our 00:17:43.270 --> 00:17:43.280 align:start position:0% clients yeah so uh so regarding our 00:17:43.280 --> 00:17:45.590 align:start position:0% clients yeah so uh so regarding our goals<00:17:43.880> for<00:17:44.160> the<00:17:44.400> very<00:17:44.679> new 00:17:45.590 --> 00:17:45.600 align:start position:0% goals for the very new 00:17:45.600 --> 00:17:49.430 align:start position:0% goals for the very new future<00:17:46.600> uh<00:17:47.160> we<00:17:47.360> plan<00:17:48.120> basically<00:17:48.600> the<00:17:48.760> most<00:17:49.280> uh 00:17:49.430 --> 00:17:49.440 align:start position:0% future uh we plan basically the most uh 00:17:49.440 --> 00:17:51.390 align:start position:0% future uh we plan basically the most uh the<00:17:49.559> most<00:17:49.840> important<00:17:50.360> is<00:17:50.520> to<00:17:50.760> finalize<00:17:51.280> the 00:17:51.390 --> 00:17:51.400 align:start position:0% the most important is to finalize the 00:17:51.400 --> 00:18:02.590 align:start position:0% the most important is to finalize the evm<00:17:51.799> max<00:17:52.440> spec<00:17:53.520> then<00:17:54.520> um<00:17:55.480> then<00:17:56.200> uh 00:18:02.590 --> 00:18:02.600 align:start position:0% 00:18:02.600 --> 00:18:06.430 align:start position:0% sorry<00:18:03.600> yeah<00:18:04.000> to<00:18:04.200> finalize<00:18:04.679> the<00:18:04.880> evm<00:18:05.320> max<00:18:05.640> pack 00:18:06.430 --> 00:18:06.440 align:start position:0% sorry yeah to finalize the evm max pack 00:18:06.440 --> 00:18:08.909 align:start position:0% sorry yeah to finalize the evm max pack then<00:18:06.919> uh<00:18:07.159> it<00:18:07.640> when<00:18:07.799> it's<00:18:08.039> implemented<00:18:08.600> it<00:18:08.720> will 00:18:08.909 --> 00:18:08.919 align:start position:0% then uh it when it's implemented it will 00:18:08.919 --> 00:18:12.070 align:start position:0% then uh it when it's implemented it will equip<00:18:09.280> the<00:18:09.640> evm<00:18:10.640> in<00:18:10.799> a<00:18:10.960> cryptographic<00:18:11.679> friend 00:18:12.070 --> 00:18:12.080 align:start position:0% equip the evm in a cryptographic friend 00:18:12.080 --> 00:18:15.110 align:start position:0% equip the evm in a cryptographic friend cryptography<00:18:12.679> friendly<00:18:13.039> tool<00:18:13.520> chain<00:18:14.520> and<00:18:15.000> it 00:18:15.110 --> 00:18:15.120 align:start position:0% cryptography friendly tool chain and it 00:18:15.120 --> 00:18:17.590 align:start position:0% cryptography friendly tool chain and it should<00:18:15.520> minimize<00:18:16.400> the<00:18:16.559> need<00:18:16.799> of<00:18:17.000> adding<00:18:17.360> new 00:18:17.590 --> 00:18:17.600 align:start position:0% should minimize the need of adding new 00:18:17.600 --> 00:18:20.630 align:start position:0% should minimize the need of adding new pre<00:18:17.880> compiles<00:18:18.480> as<00:18:18.600> I<00:18:18.760> mentioned<00:18:19.159> already<00:18:20.159> and 00:18:20.630 --> 00:18:20.640 align:start position:0% pre compiles as I mentioned already and 00:18:20.640 --> 00:18:24.350 align:start position:0% pre compiles as I mentioned already and uh<00:18:21.240> make<00:18:21.520> the<00:18:21.799> evm<00:18:22.799> more<00:18:23.000> Z<00:18:23.480> friendly<00:18:24.080> we<00:18:24.200> want 00:18:24.350 --> 00:18:24.360 align:start position:0% uh make the evm more Z friendly we want 00:18:24.360 --> 00:18:27.230 align:start position:0% uh make the evm more Z friendly we want to<00:18:24.520> be<00:18:25.320> from<00:18:25.520> the<00:18:25.760> very<00:18:26.000> beginning<00:18:26.400> of<00:18:26.559> the<00:18:26.799> evm 00:18:27.230 --> 00:18:27.240 align:start position:0% to be from the very beginning of the evm 00:18:27.240 --> 00:18:30.029 align:start position:0% to be from the very beginning of the evm existence<00:18:27.720> almost<00:18:28.559> and<00:18:28.919> to<00:18:29.080> introduce<00:18:29.720> and<00:18:29.880> we 00:18:30.029 --> 00:18:30.039 align:start position:0% existence almost and to introduce and we 00:18:30.039 --> 00:18:33.789 align:start position:0% existence almost and to introduce and we plan<00:18:30.280> to<00:18:30.480> introduce<00:18:31.080> this<00:18:32.080> ideally<00:18:33.080> after 00:18:33.789 --> 00:18:33.799 align:start position:0% plan to introduce this ideally after 00:18:33.799 --> 00:18:35.870 align:start position:0% plan to introduce this ideally after Fork<00:18:34.240> when<00:18:34.440> the<00:18:34.559> eoff<00:18:35.039> will<00:18:35.200> be<00:18:35.559> will<00:18:35.720> be 00:18:35.870 --> 00:18:35.880 align:start position:0% Fork when the eoff will be will be 00:18:35.880 --> 00:18:39.950 align:start position:0% Fork when the eoff will be will be introduced<00:18:36.480> so<00:18:36.799> hopefully<00:18:37.600> next<00:18:37.880> year<00:18:38.440> or 00:18:39.950 --> 00:18:39.960 align:start position:0% introduced so hopefully next year or 00:18:39.960 --> 00:18:43.149 align:start position:0% introduced so hopefully next year or 2026<00:18:40.960> and<00:18:41.120> if<00:18:41.240> you<00:18:41.360> are<00:18:41.559> interested<00:18:42.120> in<00:18:42.400> the 00:18:43.149 --> 00:18:43.159 align:start position:0% 2026 and if you are interested in the 00:18:43.159 --> 00:18:46.270 align:start position:0% 2026 and if you are interested in the and<00:18:43.600> and<00:18:43.799> have<00:18:44.039> more<00:18:45.039> detailed<00:18:45.600> questions<00:18:46.120> and 00:18:46.270 --> 00:18:46.280 align:start position:0% and and have more detailed questions and 00:18:46.280 --> 00:18:48.750 align:start position:0% and and have more detailed questions and will<00:18:46.360> will<00:18:46.480> not<00:18:46.640> be<00:18:46.799> able<00:18:47.000> to<00:18:47.159> ask<00:18:47.360> it<00:18:47.559> them<00:18:47.760> now 00:18:48.750 --> 00:18:48.760 align:start position:0% will will not be able to ask it them now 00:18:48.760 --> 00:18:52.070 align:start position:0% will will not be able to ask it them now uh<00:18:49.000> this<00:18:49.120> is<00:18:49.360> the<00:18:50.159> list<00:18:50.480> of<00:18:50.679> the<00:18:51.039> people<00:18:51.880> I'm 00:18:52.070 --> 00:18:52.080 align:start position:0% uh this is the list of the people I'm 00:18:52.080 --> 00:18:54.870 align:start position:0% uh this is the list of the people I'm aware<00:18:52.400> of<00:18:53.039> who<00:18:53.200> now<00:18:53.440> work<00:18:53.720> on<00:18:54.120> the<00:18:54.320> on<00:18:54.520> the<00:18:54.760> on 00:18:54.870 --> 00:18:54.880 align:start position:0% aware of who now work on the on the on 00:18:54.880 --> 00:18:57.549 align:start position:0% aware of who now work on the on the on the<00:18:55.000> evm<00:18:55.480> Max<00:18:55.919> and<00:18:56.039> this<00:18:56.159> is<00:18:56.360> ipsilon<00:18:56.799> team<00:18:57.440> I'm 00:18:57.549 --> 00:18:57.559 align:start position:0% the evm Max and this is ipsilon team I'm 00:18:57.559 --> 00:19:02.070 align:start position:0% the evm Max and this is ipsilon team I'm a<00:18:57.720> member<00:18:58.039> of<00:18:59.080> from<00:18:59.360> GF<00:18:59.880> and<00:19:00.159> kef<00:19:00.440> from<00:19:00.679> RG<00:19:01.360> ARG 00:19:02.070 --> 00:19:02.080 align:start position:0% a member of from GF and kef from RG ARG 00:19:02.080 --> 00:19:04.830 align:start position:0% a member of from GF and kef from RG ARG ARG<00:19:02.520> team<00:19:02.799> at 00:19:04.830 --> 00:19:04.840 align:start position:0% ARG team at 00:19:04.840 --> 00:19:08.830 align:start position:0% ARG team at TF<00:19:05.840> yeah<00:19:06.080> so<00:19:07.039> thank<00:19:07.159> you<00:19:07.240> for<00:19:07.400> your<00:19:07.840> attention 00:19:08.830 --> 00:19:08.840 align:start position:0% TF yeah so thank you for your attention 00:19:08.840 --> 00:19:10.870 align:start position:0% TF yeah so thank you for your attention it's<00:19:09.120> time<00:19:09.480> for<00:19:09.720> some<00:19:10.120> question<00:19:10.440> now<00:19:10.640> if<00:19:10.760> you 00:19:10.870 --> 00:19:10.880 align:start position:0% it's time for some question now if you 00:19:10.880 --> 00:19:11.669 align:start position:0% it's time for some question now if you have 00:19:11.669 --> 00:19:11.679 align:start position:0% have 00:19:11.679 --> 00:19:16.789 align:start position:0% have any<00:19:12.679> thank 00:19:16.789 --> 00:19:16.799 align:start position:0% 00:19:16.799 --> 00:19:19.549 align:start position:0% you<00:19:17.799> thanks<00:19:18.120> again<00:19:18.400> for<00:19:18.720> this<00:19:19.320> very 00:19:19.549 --> 00:19:19.559 align:start position:0% you thanks again for this very 00:19:19.559 --> 00:19:22.950 align:start position:0% you thanks again for this very interesting<00:19:20.120> top<00:19:20.760> uh<00:19:21.280> talk<00:19:22.280> uh<00:19:22.400> so<00:19:22.760> let's 00:19:22.950 --> 00:19:22.960 align:start position:0% interesting top uh talk uh so let's 00:19:22.960 --> 00:19:24.990 align:start position:0% interesting top uh talk uh so let's start<00:19:23.200> with<00:19:23.320> our<00:19:23.640> questions<00:19:24.520> the<00:19:24.679> first 00:19:24.990 --> 00:19:25.000 align:start position:0% start with our questions the first 00:19:25.000 --> 00:19:28.750 align:start position:0% start with our questions the first question<00:19:25.720> is<00:19:26.240> um<00:19:27.000> is<00:19:27.120> there<00:19:27.320> a<00:19:27.520> chance<00:19:28.200> that<00:19:28.520> uh 00:19:28.750 --> 00:19:28.760 align:start position:0% question is um is there a chance that uh 00:19:28.760 --> 00:19:31.510 align:start position:0% question is um is there a chance that uh all<00:19:28.960> these<00:19:29.200> extensions<00:19:30.039> and<00:19:30.559> end<00:19:30.799> up<00:19:31.080> being 00:19:31.510 --> 00:19:31.520 align:start position:0% all these extensions and end up being 00:19:31.520 --> 00:19:34.149 align:start position:0% all these extensions and end up being not<00:19:31.919> enough<00:19:32.919> H<00:19:33.120> what<00:19:33.320> about<00:19:33.640> going<00:19:33.880> in<00:19:34.000> the 00:19:34.149 --> 00:19:34.159 align:start position:0% not enough H what about going in the 00:19:34.159 --> 00:19:36.310 align:start position:0% not enough H what about going in the opposite<00:19:34.520> direction<00:19:35.400> and<00:19:35.720> integrate 00:19:36.310 --> 00:19:36.320 align:start position:0% opposite direction and integrate 00:19:36.320 --> 00:19:38.590 align:start position:0% opposite direction and integrate something<00:19:36.880> like<00:19:37.280> wasm<00:19:37.919> and<00:19:38.280> then 00:19:38.590 --> 00:19:38.600 align:start position:0% something like wasm and then 00:19:38.600 --> 00:19:41.990 align:start position:0% something like wasm and then implementing<00:19:39.240> it<00:19:40.120> uh<00:19:40.320> at<00:19:40.480> the<00:19:40.600> contract<00:19:41.039> level 00:19:41.990 --> 00:19:42.000 align:start position:0% implementing it uh at the contract level 00:19:42.000 --> 00:19:44.909 align:start position:0% implementing it uh at the contract level yeah<00:19:42.200> so<00:19:42.720> uh<00:19:43.120> it<00:19:43.320> always<00:19:43.720> can<00:19:43.960> end<00:19:44.200> up<00:19:44.440> with 00:19:44.909 --> 00:19:44.919 align:start position:0% yeah so uh it always can end up with 00:19:44.919 --> 00:19:47.990 align:start position:0% yeah so uh it always can end up with being<00:19:45.280> not<00:19:45.840> enough<00:19:46.280> if<00:19:46.480> there<00:19:46.600> will<00:19:46.760> be<00:19:47.000> some 00:19:47.990 --> 00:19:48.000 align:start position:0% being not enough if there will be some 00:19:48.000 --> 00:19:51.190 align:start position:0% being not enough if there will be some uh<00:19:48.159> some<00:19:48.400> use<00:19:48.760> case<00:19:49.120> which<00:19:49.520> we<00:19:50.280> uh<00:19:50.440> haven't 00:19:51.190 --> 00:19:51.200 align:start position:0% uh some use case which we uh haven't 00:19:51.200 --> 00:19:53.870 align:start position:0% uh some use case which we uh haven't covered<00:19:52.200> uh<00:19:52.440> when<00:19:52.840> when<00:19:53.159> uh<00:19:53.280> when<00:19:53.440> designing 00:19:53.870 --> 00:19:53.880 align:start position:0% covered uh when when uh when designing 00:19:53.880 --> 00:19:54.669 align:start position:0% covered uh when when uh when designing the 00:19:54.669 --> 00:19:54.679 align:start position:0% the 00:19:54.679 --> 00:19:57.870 align:start position:0% the instructions<00:19:55.679> um<00:19:56.320> but<00:19:57.120> uh<00:19:57.360> but<00:19:57.559> yeah<00:19:57.679> so 00:19:57.870 --> 00:19:57.880 align:start position:0% instructions um but uh but yeah so 00:19:57.880 --> 00:19:59.789 align:start position:0% instructions um but uh but yeah so that's<00:19:58.080> why<00:19:58.240> we<00:19:58.720> that's<00:19:58.880> why<00:19:59.000> we<00:19:59.120> trying<00:19:59.400> to<00:19:59.559> do 00:19:59.789 --> 00:19:59.799 align:start position:0% that's why we that's why we trying to do 00:19:59.799 --> 00:20:02.950 align:start position:0% that's why we that's why we trying to do all<00:20:00.039> this<00:20:00.360> all<00:20:00.520> this<00:20:00.679> use<00:20:01.080> cases<00:20:02.080> and<00:20:02.280> also<00:20:02.679> the 00:20:02.950 --> 00:20:02.960 align:start position:0% all this all this use cases and also the 00:20:02.960 --> 00:20:06.549 align:start position:0% all this all this use cases and also the the<00:20:03.080> newest<00:20:03.480> one<00:20:04.000> ideas<00:20:04.559> like<00:20:04.760> Poseidon<00:20:05.559> hash 00:20:06.549 --> 00:20:06.559 align:start position:0% the newest one ideas like Poseidon hash 00:20:06.559 --> 00:20:10.390 align:start position:0% the newest one ideas like Poseidon hash uh<00:20:07.039> like<00:20:07.400> any<00:20:07.640> others<00:20:08.640> and<00:20:08.960> uh<00:20:09.080> regarding 00:20:10.390 --> 00:20:10.400 align:start position:0% uh like any others and uh regarding 00:20:10.400 --> 00:20:13.029 align:start position:0% uh like any others and uh regarding quasm<00:20:11.400> I<00:20:11.520> think<00:20:11.840> I'm<00:20:11.960> not<00:20:12.080> sure<00:20:12.320> I<00:20:12.440> fully 00:20:13.029 --> 00:20:13.039 align:start position:0% quasm I think I'm not sure I fully 00:20:13.039 --> 00:20:16.789 align:start position:0% quasm I think I'm not sure I fully understand<00:20:13.400> but<00:20:14.000> uh<00:20:14.480> but<00:20:14.799> yeah<00:20:15.000> so<00:20:15.320> so<00:20:16.280> the 00:20:16.789 --> 00:20:16.799 align:start position:0% understand but uh but yeah so so the 00:20:16.799 --> 00:20:21.350 align:start position:0% understand but uh but yeah so so the wasm<00:20:17.600> wasm<00:20:18.600> idea<00:20:19.559> to<00:20:19.880> to<00:20:20.480> to<00:20:20.760> to<00:20:20.880> use<00:20:21.080> it<00:20:21.200> to 00:20:21.350 --> 00:20:21.360 align:start position:0% wasm wasm idea to to to to use it to 00:20:21.360 --> 00:20:24.789 align:start position:0% wasm wasm idea to to to to use it to replace<00:20:21.840> evm<00:20:22.360> evm<00:20:23.360> was<00:20:23.840> investigated<00:20:24.520> like<00:20:24.679> a 00:20:24.789 --> 00:20:24.799 align:start position:0% replace evm evm was investigated like a 00:20:24.799 --> 00:20:26.750 align:start position:0% replace evm evm was investigated like a couple<00:20:25.120> years<00:20:25.320> ago<00:20:25.640> by<00:20:25.840> my<00:20:26.159> by<00:20:26.280> my<00:20:26.440> friends 00:20:26.750 --> 00:20:26.760 align:start position:0% couple years ago by my by my friends 00:20:26.760 --> 00:20:29.789 align:start position:0% couple years ago by my by my friends from<00:20:27.000> ipsilon<00:20:27.720> at<00:20:28.440> uh<00:20:28.760> I<00:20:28.840> don't<00:20:29.039> remember<00:20:29.440> now 00:20:29.789 --> 00:20:29.799 align:start position:0% from ipsilon at uh I don't remember now 00:20:29.799 --> 00:20:32.270 align:start position:0% from ipsilon at uh I don't remember now exactly<00:20:30.159> the<00:20:30.280> reasons<00:20:30.720> but<00:20:30.919> it<00:20:31.039> was<00:20:32.000> uh<00:20:32.159> it 00:20:32.270 --> 00:20:32.280 align:start position:0% exactly the reasons but it was uh it 00:20:32.280 --> 00:20:35.430 align:start position:0% exactly the reasons but it was uh it wasn't<00:20:33.039> uh<00:20:33.520> it<00:20:33.640> wasn't<00:20:34.000> finally<00:20:35.000> appeared<00:20:35.320> to 00:20:35.430 --> 00:20:35.440 align:start position:0% wasn't uh it wasn't finally appeared to 00:20:35.440 --> 00:20:38.870 align:start position:0% wasn't uh it wasn't finally appeared to be<00:20:35.600> a<00:20:35.760> good<00:20:36.640> uh<00:20:36.799> to<00:20:36.880> be<00:20:37.039> a<00:20:37.200> good 00:20:38.870 --> 00:20:38.880 align:start position:0% be a good uh to be a good 00:20:38.880 --> 00:20:41.990 align:start position:0% be a good uh to be a good direction<00:20:39.880> okay<00:20:40.120> let's<00:20:40.320> go<00:20:40.480> to<00:20:40.600> the<00:20:40.760> next 00:20:41.990 --> 00:20:42.000 align:start position:0% direction okay let's go to the next 00:20:42.000 --> 00:20:43.830 align:start position:0% direction okay let's go to the next one 00:20:43.830 --> 00:20:43.840 align:start position:0% one 00:20:43.840 --> 00:20:46.350 align:start position:0% one so<00:20:44.840> uh<00:20:45.280> what's<00:20:45.640> and<00:20:45.760> the<00:20:45.880> next<00:20:46.000> one<00:20:46.120> is<00:20:46.240> the 00:20:46.350 --> 00:20:46.360 align:start position:0% so uh what's and the next one is the 00:20:46.360 --> 00:20:49.270 align:start position:0% so uh what's and the next one is the second<00:20:46.559> one<00:20:46.799> so<00:20:47.480> H<00:20:47.640> Eva<00:20:48.159> Max<00:20:48.559> is<00:20:48.880> kind<00:20:49.080> of 00:20:49.270 --> 00:20:49.280 align:start position:0% second one so H Eva Max is kind of 00:20:49.280 --> 00:20:51.870 align:start position:0% second one so H Eva Max is kind of another<00:20:50.039> co-o 00:20:51.870 --> 00:20:51.880 align:start position:0% another co-o 00:20:51.880 --> 00:20:54.070 align:start position:0% another co-o co-processor<00:20:52.880> why<00:20:53.039> not<00:20:53.280> just<00:20:53.559> enable 00:20:54.070 --> 00:20:54.080 align:start position:0% co-processor why not just enable 00:20:54.080 --> 00:20:56.789 align:start position:0% co-processor why not just enable restricted<00:20:54.760> wasm<00:20:55.760> kind<00:20:55.919> of<00:20:56.080> similar<00:20:56.520> question 00:20:56.789 --> 00:20:56.799 align:start position:0% restricted wasm kind of similar question 00:20:56.799 --> 00:20:59.789 align:start position:0% restricted wasm kind of similar question I<00:20:56.960> guess<00:20:57.720> H<00:20:57.919> only<00:20:58.200> on<00:20:58.360> some<00:20:58.640> sign<00:20:59.080> the<00:20:59.480> in 00:20:59.789 --> 00:20:59.799 align:start position:0% I guess H only on some sign the in 00:20:59.799 --> 00:21:03.549 align:start position:0% I guess H only on some sign the in sequence<00:21:00.480> of<00:21:00.720> AD<00:21:01.039> Mo<00:21:01.400> store<00:21:02.320> yeah<00:21:03.120> yeah<00:21:03.280> that's 00:21:03.549 --> 00:21:03.559 align:start position:0% sequence of AD Mo store yeah yeah that's 00:21:03.559 --> 00:21:05.630 align:start position:0% sequence of AD Mo store yeah yeah that's that's<00:21:03.919> that's<00:21:04.080> another<00:21:04.440> so<00:21:04.799> I<00:21:05.159> okay<00:21:05.400> now<00:21:05.520> I 00:21:05.630 --> 00:21:05.640 align:start position:0% that's that's another so I okay now I 00:21:05.640 --> 00:21:08.110 align:start position:0% that's that's another so I okay now I remember<00:21:06.000> one<00:21:06.360> one<00:21:06.760> one<00:21:06.960> one<00:21:07.159> reason<00:21:07.480> why<00:21:07.720> wasm 00:21:08.110 --> 00:21:08.120 align:start position:0% remember one one one one reason why wasm 00:21:08.120 --> 00:21:11.870 align:start position:0% remember one one one one reason why wasm is<00:21:08.400> not<00:21:09.000> uh<00:21:09.919> uh<00:21:10.120> not<00:21:10.559> the<00:21:10.720> best<00:21:10.960> idea<00:21:11.400> here 00:21:11.870 --> 00:21:11.880 align:start position:0% is not uh uh not the best idea here 00:21:11.880 --> 00:21:15.750 align:start position:0% is not uh uh not the best idea here first<00:21:12.080> of<00:21:12.240> all<00:21:13.159> uh<00:21:13.400> wasm<00:21:14.200> as<00:21:14.320> far<00:21:14.559> as<00:21:14.679> I<00:21:14.840> know<00:21:15.600> uh 00:21:15.750 --> 00:21:15.760 align:start position:0% first of all uh wasm as far as I know uh 00:21:15.760 --> 00:21:17.549 align:start position:0% first of all uh wasm as far as I know uh but<00:21:15.880> I<00:21:16.000> can<00:21:16.120> be<00:21:16.320> wrong<00:21:16.559> doesn't<00:21:16.880> operate<00:21:17.320> on 00:21:17.549 --> 00:21:17.559 align:start position:0% but I can be wrong doesn't operate on 00:21:17.559 --> 00:21:20.549 align:start position:0% but I can be wrong doesn't operate on the<00:21:17.760> on<00:21:17.919> the<00:21:18.039> register<00:21:18.480> is<00:21:18.679> bigger<00:21:19.080> than<00:21:19.559> uh<00:21:19.720> 64 00:21:20.549 --> 00:21:20.559 align:start position:0% the on the register is bigger than uh 64 00:21:20.559 --> 00:21:24.990 align:start position:0% the on the register is bigger than uh 64 bits<00:21:21.559> and<00:21:22.080> uh<00:21:22.880> and<00:21:23.279> basically<00:21:23.760> it<00:21:23.960> makes<00:21:24.520> the 00:21:24.990 --> 00:21:25.000 align:start position:0% bits and uh and basically it makes the 00:21:25.000 --> 00:21:27.710 align:start position:0% bits and uh and basically it makes the the<00:21:25.159> implementation<00:21:26.080> of<00:21:26.360> the<00:21:26.880> of<00:21:27.120> the<00:21:27.440> of<00:21:27.600> the 00:21:27.710 --> 00:21:27.720 align:start position:0% the implementation of the of the of the 00:21:27.720 --> 00:21:31.390 align:start position:0% the implementation of the of the of the 220<00:21:28.799> 56<00:21:29.799> uh<00:21:29.960> bits<00:21:30.279> Valu<00:21:30.559> is<00:21:30.799> much<00:21:31.039> more 00:21:31.390 --> 00:21:31.400 align:start position:0% 220 56 uh bits Valu is much more 00:21:31.400 --> 00:21:33.669 align:start position:0% 220 56 uh bits Valu is much more complicated<00:21:32.200> that<00:21:32.360> it<00:21:32.520> can<00:21:32.679> be<00:21:32.880> done<00:21:33.240> now<00:21:33.520> in 00:21:33.669 --> 00:21:33.679 align:start position:0% complicated that it can be done now in 00:21:33.679 --> 00:21:38.870 align:start position:0% complicated that it can be done now in the<00:21:34.039> evm<00:21:35.039> and<00:21:35.559> uh<00:21:36.320> and<00:21:36.640> this<00:21:37.240> also<00:21:38.240> uh<00:21:38.679> this 00:21:38.870 --> 00:21:38.880 align:start position:0% the evm and uh and this also uh this 00:21:38.880 --> 00:21:41.470 align:start position:0% the evm and uh and this also uh this also<00:21:39.200> means<00:21:39.880> that 00:21:41.470 --> 00:21:41.480 align:start position:0% also means that 00:21:41.480 --> 00:21:44.190 align:start position:0% also means that uh<00:21:42.480> yeah<00:21:42.679> so<00:21:42.880> so<00:21:43.120> basically<00:21:43.480> this<00:21:43.640> also<00:21:43.880> means 00:21:44.190 --> 00:21:44.200 align:start position:0% uh yeah so so basically this also means 00:21:44.200 --> 00:21:47.190 align:start position:0% uh yeah so so basically this also means that<00:21:44.679> in<00:21:44.840> the<00:21:44.960> end<00:21:45.559> when<00:21:45.799> we<00:21:46.360> when<00:21:46.640> my<00:21:46.799> friends 00:21:47.190 --> 00:21:47.200 align:start position:0% that in the end when we when my friends 00:21:47.200 --> 00:21:50.630 align:start position:0% that in the end when we when my friends from<00:21:47.760> Team<00:21:48.760> were<00:21:49.039> were<00:21:49.279> trying<00:21:49.679> to<00:21:50.080> to<00:21:50.320> use 00:21:50.630 --> 00:21:50.640 align:start position:0% from Team were were trying to to use 00:21:50.640 --> 00:21:53.750 align:start position:0% from Team were were trying to to use wasm<00:21:51.000> instead<00:21:51.240> of<00:21:51.400> evm<00:21:51.880> it<00:21:52.000> appears<00:21:52.360> to<00:21:52.559> be<00:21:53.400> uh 00:21:53.750 --> 00:21:53.760 align:start position:0% wasm instead of evm it appears to be uh 00:21:53.760 --> 00:21:56.590 align:start position:0% wasm instead of evm it appears to be uh basically<00:21:54.360> less<00:21:54.679> efficient<00:21:55.679> than 00:21:56.590 --> 00:21:56.600 align:start position:0% basically less efficient than 00:21:56.600 --> 00:22:00.789 align:start position:0% basically less efficient than evm<00:21:57.600> great<00:21:58.159> so<00:21:58.919> is<00:21:59.039> it<00:21:59.159> a<00:21:59.440> problem<00:22:00.120> if<00:22:00.559> uh 00:22:00.789 --> 00:22:00.799 align:start position:0% evm great so is it a problem if uh 00:22:00.799 --> 00:22:02.029 align:start position:0% evm great so is it a problem if uh different<00:22:01.080> implementations<00:22:01.720> of<00:22:01.880> a 00:22:02.029 --> 00:22:02.039 align:start position:0% different implementations of a 00:22:02.039 --> 00:22:05.070 align:start position:0% different implementations of a precompile<00:22:02.840> vary<00:22:03.200> in<00:22:03.520> performance<00:22:04.520> if<00:22:04.640> so<00:22:04.960> how 00:22:05.070 --> 00:22:05.080 align:start position:0% precompile vary in performance if so how 00:22:05.080 --> 00:22:08.310 align:start position:0% precompile vary in performance if so how to<00:22:05.240> avoid<00:22:05.559> it<00:22:06.400> so<00:22:06.720> basically<00:22:07.520> when<00:22:07.679> we<00:22:08.000> have 00:22:08.310 --> 00:22:08.320 align:start position:0% to avoid it so basically when we have 00:22:08.320 --> 00:22:11.230 align:start position:0% to avoid it so basically when we have evm<00:22:08.799> Max<00:22:09.480> we<00:22:09.600> will<00:22:09.840> not<00:22:10.200> have<00:22:10.640> hopefully<00:22:11.120> we 00:22:11.230 --> 00:22:11.240 align:start position:0% evm Max we will not have hopefully we 00:22:11.240 --> 00:22:13.870 align:start position:0% evm Max we will not have hopefully we will<00:22:11.400> not<00:22:11.679> have<00:22:12.279> uh<00:22:12.520> new<00:22:12.760> promiles<00:22:13.480> anymore 00:22:13.870 --> 00:22:13.880 align:start position:0% will not have uh new promiles anymore 00:22:13.880 --> 00:22:16.190 align:start position:0% will not have uh new promiles anymore anymore<00:22:14.679> new<00:22:14.880> promile<00:22:15.400> related<00:22:15.720> to<00:22:15.840> elliptic 00:22:16.190 --> 00:22:16.200 align:start position:0% anymore new promile related to elliptic 00:22:16.200 --> 00:22:18.909 align:start position:0% anymore new promile related to elliptic curve<00:22:16.480> cryptography<00:22:17.200> or<00:22:17.960> uh<00:22:18.080> or<00:22:18.279> basically<00:22:18.640> to 00:22:18.909 --> 00:22:18.919 align:start position:0% curve cryptography or uh or basically to 00:22:18.919 --> 00:22:21.630 align:start position:0% curve cryptography or uh or basically to cryptography<00:22:19.919> so<00:22:20.440> we<00:22:20.559> won't<00:22:21.000> have<00:22:21.240> this<00:22:21.480> kind 00:22:21.630 --> 00:22:21.640 align:start position:0% cryptography so we won't have this kind 00:22:21.640 --> 00:22:24.630 align:start position:0% cryptography so we won't have this kind of<00:22:21.760> a<00:22:22.000> problem<00:22:22.919> but<00:22:23.400> there<00:22:23.520> is<00:22:23.679> a<00:22:23.919> problem<00:22:24.279> now 00:22:24.630 --> 00:22:24.640 align:start position:0% of a problem but there is a problem now 00:22:24.640 --> 00:22:27.630 align:start position:0% of a problem but there is a problem now with<00:22:25.080> uh<00:22:25.279> with<00:22:25.520> with<00:22:25.679> the<00:22:25.799> promise<00:22:26.640> already 00:22:27.630 --> 00:22:27.640 align:start position:0% with uh with with the promise already 00:22:27.640 --> 00:22:31.990 align:start position:0% with uh with with the promise already and<00:22:28.200> uh<00:22:28.720> basically<00:22:29.080> it<00:22:29.200> means<00:22:29.960> that<00:22:30.960> uh<00:22:31.440> we 00:22:31.990 --> 00:22:32.000 align:start position:0% and uh basically it means that uh we 00:22:32.000 --> 00:22:33.990 align:start position:0% and uh basically it means that uh we when<00:22:32.279> when<00:22:32.559> when<00:22:32.720> we<00:22:33.000> uh<00:22:33.240> when<00:22:33.400> we<00:22:33.600> designing 00:22:33.990 --> 00:22:34.000 align:start position:0% when when when we uh when we designing 00:22:34.000 --> 00:22:36.110 align:start position:0% when when when we uh when we designing the<00:22:34.159> gas<00:22:34.440> schedule<00:22:34.880> for<00:22:35.120> the<00:22:35.279> precompile<00:22:35.960> we 00:22:36.110 --> 00:22:36.120 align:start position:0% the gas schedule for the precompile we 00:22:36.120 --> 00:22:39.510 align:start position:0% the gas schedule for the precompile we just<00:22:36.240> need<00:22:36.799> to<00:22:37.799> um<00:22:38.080> we<00:22:38.240> just<00:22:38.679> need<00:22:38.880> to<00:22:39.080> make<00:22:39.279> it 00:22:39.510 --> 00:22:39.520 align:start position:0% just need to um we just need to make it 00:22:39.520 --> 00:22:42.110 align:start position:0% just need to um we just need to make it based<00:22:39.919> on<00:22:40.159> the<00:22:40.440> less<00:22:40.760> efficient<00:22:41.559> available 00:22:42.110 --> 00:22:42.120 align:start position:0% based on the less efficient available 00:22:42.120 --> 00:22:44.549 align:start position:0% based on the less efficient available implementation<00:22:43.039> and<00:22:43.400> uh<00:22:43.559> available<00:22:44.000> impation 00:22:44.549 --> 00:22:44.559 align:start position:0% implementation and uh available impation 00:22:44.559 --> 00:22:47.510 align:start position:0% implementation and uh available impation in<00:22:44.679> the<00:22:44.760> client<00:22:45.120> execution<00:22:46.039> uh<00:22:46.159> and<00:22:46.360> the<00:22:46.840> layer 00:22:47.510 --> 00:22:47.520 align:start position:0% in the client execution uh and the layer 00:22:47.520 --> 00:22:48.789 align:start position:0% in the client execution uh and the layer execution 00:22:48.789 --> 00:22:48.799 align:start position:0% execution 00:22:48.799 --> 00:22:52.510 align:start position:0% execution client<00:22:49.799> okay<00:22:50.120> so<00:22:51.120> uh<00:22:51.559> does<00:22:51.880> adding<00:22:52.279> new 00:22:52.510 --> 00:22:52.520 align:start position:0% client okay so uh does adding new 00:22:52.520 --> 00:22:55.310 align:start position:0% client okay so uh does adding new instructions<00:22:53.080> require<00:22:53.480> a<00:22:53.600> hard<00:22:53.919> Fork<00:22:54.760> a<00:22:54.960> new 00:22:55.310 --> 00:22:55.320 align:start position:0% instructions require a hard Fork a new 00:22:55.320 --> 00:22:58.870 align:start position:0% instructions require a hard Fork a new year<00:22:56.120> version<00:22:56.760> or<00:22:57.039> both<00:22:57.880> uh<00:22:58.080> yeah<00:22:58.279> the<00:22:58.600> it<00:22:58.720> will 00:22:58.870 --> 00:22:58.880 align:start position:0% year version or both uh yeah the it will 00:22:58.880 --> 00:23:01.669 align:start position:0% year version or both uh yeah the it will require<00:22:59.279> hard<00:22:59.600> f<00:22:59.880> it<00:23:00.000> will<00:23:00.200> not<00:23:00.520> require<00:23:01.520> uh 00:23:01.669 --> 00:23:01.679 align:start position:0% require hard f it will not require uh 00:23:01.679 --> 00:23:06.590 align:start position:0% require hard f it will not require uh your<00:23:02.120> version<00:23:02.520> bu<00:23:03.080> bump<00:23:04.440> mhm<00:23:05.440> um<00:23:06.240> are<00:23:06.480> you 00:23:06.590 --> 00:23:06.600 align:start position:0% your version bu bump mhm um are you 00:23:06.600 --> 00:23:09.950 align:start position:0% your version bu bump mhm um are you foreseeing<00:23:07.360> any<00:23:07.640> ways<00:23:08.159> for<00:23:08.799> uh<00:23:09.320> anyone<00:23:09.720> to 00:23:09.950 --> 00:23:09.960 align:start position:0% foreseeing any ways for uh anyone to 00:23:09.960 --> 00:23:13.269 align:start position:0% foreseeing any ways for uh anyone to exploit<00:23:10.799> uh<00:23:11.039> these<00:23:11.240> extensions<00:23:11.919> in<00:23:12.080> a<00:23:12.880> non- 00:23:13.269 --> 00:23:13.279 align:start position:0% exploit uh these extensions in a non- 00:23:13.279 --> 00:23:15.149 align:start position:0% exploit uh these extensions in a non- cryptography 00:23:15.149 --> 00:23:15.159 align:start position:0% cryptography 00:23:15.159 --> 00:23:17.909 align:start position:0% cryptography way<00:23:16.159> uh 00:23:17.909 --> 00:23:17.919 align:start position:0% way uh 00:23:17.919 --> 00:23:20.269 align:start position:0% way uh actually<00:23:18.919> I<00:23:19.159> personally<00:23:19.679> hadn't<00:23:20.000> thought 00:23:20.269 --> 00:23:20.279 align:start position:0% actually I personally hadn't thought 00:23:20.279 --> 00:23:23.549 align:start position:0% actually I personally hadn't thought about<00:23:20.520> it<00:23:21.039> but<00:23:21.679> uh<00:23:21.919> but<00:23:22.120> probably 00:23:23.549 --> 00:23:23.559 align:start position:0% about it but uh but probably 00:23:23.559 --> 00:23:27.110 align:start position:0% about it but uh but probably some<00:23:24.559> some<00:23:25.200> guys<00:23:25.480> from<00:23:25.799> ipsilon<00:23:26.520> will<00:23:26.640> be<00:23:26.840> able 00:23:27.110 --> 00:23:27.120 align:start position:0% some some guys from ipsilon will be able 00:23:27.120 --> 00:23:29.870 align:start position:0% some some guys from ipsilon will be able to<00:23:27.559> to<00:23:27.840> to<00:23:27.960> answer<00:23:28.240> this<00:23:28.640> question<00:23:29.360> so<00:23:29.600> we<00:23:29.679> are 00:23:29.870 --> 00:23:29.880 align:start position:0% to to to answer this question so we are 00:23:29.880 --> 00:23:31.990 align:start position:0% to to to answer this question so we are basically<00:23:30.320> here<00:23:30.520> so<00:23:30.880> we<00:23:30.960> can<00:23:31.120> find<00:23:31.360> us<00:23:31.640> sorry 00:23:31.990 --> 00:23:32.000 align:start position:0% basically here so we can find us sorry 00:23:32.000 --> 00:23:34.710 align:start position:0% basically here so we can find us sorry because<00:23:32.320> I<00:23:32.559> I<00:23:33.000> I<00:23:33.080> don't<00:23:33.360> I<00:23:33.440> don't<00:23:33.600> know<00:23:33.840> this 00:23:34.710 --> 00:23:34.720 align:start position:0% because I I I don't I don't know this 00:23:34.720 --> 00:23:37.310 align:start position:0% because I I I don't I don't know this one<00:23:35.720> can<00:23:36.000> extensions<00:23:36.480> like<00:23:36.720> this<00:23:36.880> be<00:23:37.039> added 00:23:37.310 --> 00:23:37.320 align:start position:0% one can extensions like this be added 00:23:37.320 --> 00:23:40.149 align:start position:0% one can extensions like this be added freely<00:23:37.960> or<00:23:38.440> is<00:23:38.559> it<00:23:38.799> bad<00:23:39.039> to<00:23:39.240> have<00:23:39.679> too<00:23:39.880> many 00:23:40.149 --> 00:23:40.159 align:start position:0% freely or is it bad to have too many 00:23:40.159 --> 00:23:42.669 align:start position:0% freely or is it bad to have too many extensions<00:23:41.159> I<00:23:41.360> guess<00:23:41.760> something<00:23:42.159> similar<00:23:42.520> to 00:23:42.669 --> 00:23:42.679 align:start position:0% extensions I guess something similar to 00:23:42.679 --> 00:23:46.590 align:start position:0% extensions I guess something similar to evm<00:23:43.080> Max<00:23:43.480> but<00:23:43.720> for<00:23:43.960> another<00:23:44.919> Target<00:23:45.919> uh 00:23:46.590 --> 00:23:46.600 align:start position:0% evm Max but for another Target uh 00:23:46.600 --> 00:23:48.789 align:start position:0% evm Max but for another Target uh basically<00:23:47.240> if<00:23:47.559> if<00:23:47.720> it<00:23:47.840> will<00:23:48.039> be<00:23:48.200> needed<00:23:48.559> it<00:23:48.679> can 00:23:48.789 --> 00:23:48.799 align:start position:0% basically if if it will be needed it can 00:23:48.799 --> 00:23:51.070 align:start position:0% basically if if it will be needed it can be<00:23:49.000> add<00:23:49.480> but<00:23:49.799> you<00:23:49.919> know<00:23:50.440> the<00:23:50.559> process<00:23:50.960> the 00:23:51.070 --> 00:23:51.080 align:start position:0% be add but you know the process the 00:23:51.080 --> 00:23:53.789 align:start position:0% be add but you know the process the process<00:23:51.360> of<00:23:51.480> adding<00:23:51.799> new<00:23:52.000> extensions<00:23:52.640> is<00:23:52.960> like 00:23:53.789 --> 00:23:53.799 align:start position:0% process of adding new extensions is like 00:23:53.799 --> 00:23:55.510 align:start position:0% process of adding new extensions is like well<00:23:54.080> know<00:23:54.320> and<00:23:54.480> straightforward<00:23:55.240> you<00:23:55.360> need 00:23:55.510 --> 00:23:55.520 align:start position:0% well know and straightforward you need 00:23:55.520 --> 00:23:57.430 align:start position:0% well know and straightforward you need to<00:23:55.720> propose<00:23:56.080> it<00:23:56.279> you<00:23:56.400> need<00:23:56.559> to<00:23:56.760> fight<00:23:57.000> for<00:23:57.279> this 00:23:57.430 --> 00:23:57.440 align:start position:0% to propose it you need to fight for this 00:23:57.440 --> 00:24:00.710 align:start position:0% to propose it you need to fight for this on<00:23:57.840> a<00:23:58.039> ACD<00:23:58.640> calls<00:23:59.039> and<00:23:59.480> uh<00:23:59.840> and<00:24:00.080> maybe<00:24:00.360> finally 00:24:00.710 --> 00:24:00.720 align:start position:0% on a ACD calls and uh and maybe finally 00:24:00.720 --> 00:24:05.070 align:start position:0% on a ACD calls and uh and maybe finally it<00:24:00.799> will<00:24:00.960> be<00:24:01.520> introduced<00:24:02.799> mhm<00:24:03.799> um<00:24:04.200> so<00:24:04.840> if 00:24:05.070 --> 00:24:05.080 align:start position:0% it will be introduced mhm um so if 00:24:05.080 --> 00:24:08.510 align:start position:0% it will be introduced mhm um so if implementing<00:24:05.679> G<00:24:05.960> marks<00:24:06.400> in<00:24:06.880> another<00:24:07.520> language 00:24:08.510 --> 00:24:08.520 align:start position:0% implementing G marks in another language 00:24:08.520 --> 00:24:13.110 align:start position:0% implementing G marks in another language guess<00:24:08.760> not<00:24:09.000> see<00:24:09.440> not<00:24:10.320> uh<00:24:10.840> go<00:24:11.320> or<00:24:11.679> not<00:24:12.320> uh 00:24:13.110 --> 00:24:13.120 align:start position:0% guess not see not uh go or not uh 00:24:13.120 --> 00:24:14.909 align:start position:0% guess not see not uh go or not uh rust 00:24:14.909 --> 00:24:14.919 align:start position:0% rust 00:24:14.919 --> 00:24:17.870 align:start position:0% rust um<00:24:15.919> are<00:24:16.159> there<00:24:16.480> potential<00:24:17.000> performance 00:24:17.870 --> 00:24:17.880 align:start position:0% um are there potential performance 00:24:17.880 --> 00:24:21.149 align:start position:0% um are there potential performance differences 00:24:21.149 --> 00:24:21.159 align:start position:0% 00:24:21.159 --> 00:24:24.830 align:start position:0% then<00:24:22.200> uh<00:24:23.200> yes<00:24:23.520> definitely<00:24:24.080> definitely<00:24:24.480> it<00:24:24.640> can 00:24:24.830 --> 00:24:24.840 align:start position:0% then uh yes definitely definitely it can 00:24:24.840 --> 00:24:26.510 align:start position:0% then uh yes definitely definitely it can be<00:24:25.120> it<00:24:25.240> can<00:24:25.399> be<00:24:25.559> a<00:24:25.760> per<00:24:26.039> performance 00:24:26.510 --> 00:24:26.520 align:start position:0% be it can be a per performance 00:24:26.520 --> 00:24:27.909 align:start position:0% be it can be a per performance differences<00:24:26.960> in<00:24:27.120> the<00:24:27.240> implementation 00:24:27.909 --> 00:24:27.919 align:start position:0% differences in the implementation 00:24:27.919 --> 00:24:31.470 align:start position:0% differences in the implementation between<00:24:28.159> the<00:24:28.720> clients<00:24:29.720> uh<00:24:30.039> like<00:24:30.760> probably<00:24:31.159> for 00:24:31.470 --> 00:24:31.480 align:start position:0% between the clients uh like probably for 00:24:31.480 --> 00:24:33.590 align:start position:0% between the clients uh like probably for every<00:24:31.760> other<00:24:32.240> instructions<00:24:33.240> which<00:24:33.360> are 00:24:33.590 --> 00:24:33.600 align:start position:0% every other instructions which are 00:24:33.600 --> 00:24:35.110 align:start position:0% every other instructions which are implemented<00:24:34.120> in<00:24:34.279> different<00:24:34.600> languages 00:24:35.110 --> 00:24:35.120 align:start position:0% implemented in different languages 00:24:35.120 --> 00:24:38.630 align:start position:0% implemented in different languages across<00:24:35.399> the<00:24:35.559> clients<00:24:36.559> regarding<00:24:37.159> the 00:24:38.630 --> 00:24:38.640 align:start position:0% across the clients regarding the 00:24:38.640 --> 00:24:41.350 align:start position:0% across the clients regarding the yeah<00:24:39.640> yeah<00:24:39.799> so<00:24:40.240> do<00:24:40.399> you<00:24:40.520> want<00:24:40.640> to<00:24:40.799> pick<00:24:41.200> one 00:24:41.350 --> 00:24:41.360 align:start position:0% yeah yeah so do you want to pick one 00:24:41.360 --> 00:24:43.669 align:start position:0% yeah yeah so do you want to pick one more<00:24:41.919> yeah<00:24:42.399> so<00:24:42.640> regarding<00:24:43.120> this<00:24:43.440> this 00:24:43.669 --> 00:24:43.679 align:start position:0% more yeah so regarding this this 00:24:43.679 --> 00:24:46.269 align:start position:0% more yeah so regarding this this question<00:24:44.000> regarding<00:24:44.600> simd<00:24:45.600> uh<00:24:45.760> it's<00:24:46.039> it's<00:24:46.159> a 00:24:46.269 --> 00:24:46.279 align:start position:0% question regarding simd uh it's it's a 00:24:46.279 --> 00:24:48.310 align:start position:0% question regarding simd uh it's it's a new<00:24:46.480> topic<00:24:46.840> we<00:24:47.000> haven't<00:24:47.279> investigated<00:24:47.919> it 00:24:48.310 --> 00:24:48.320 align:start position:0% new topic we haven't investigated it 00:24:48.320 --> 00:24:51.110 align:start position:0% new topic we haven't investigated it very<00:24:48.520> deeply<00:24:48.960> but<00:24:49.240> basically<00:24:49.840> this<00:24:50.120> extension 00:24:51.110 --> 00:24:51.120 align:start position:0% very deeply but basically this extension 00:24:51.120 --> 00:24:53.870 align:start position:0% very deeply but basically this extension we<00:24:51.320> plan<00:24:51.600> to<00:24:51.720> be<00:24:51.880> used<00:24:52.159> only<00:24:52.559> for<00:24:53.240> for<00:24:53.559> smaller 00:24:53.870 --> 00:24:53.880 align:start position:0% we plan to be used only for for smaller 00:24:53.880 --> 00:24:56.149 align:start position:0% we plan to be used only for for smaller modulus<00:24:54.720> like<00:24:55.000> 64 00:24:56.149 --> 00:24:56.159 align:start position:0% modulus like 64 00:24:56.159 --> 00:24:59.310 align:start position:0% modulus like 64 bits<00:24:57.159> which<00:24:57.360> will<00:24:57.679> probably<00:24:58.480> make<00:24:58.799> much<00:24:59.039> more 00:24:59.310 --> 00:24:59.320 align:start position:0% bits which will probably make much more 00:24:59.320 --> 00:25:02.080 align:start position:0% bits which will probably make much more sense<00:24:59.679> here