WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:15.250 align:start position:0% [Music] 00:00:15.250 --> 00:00:15.260 align:start position:0% 00:00:15.260 --> 00:00:17.689 align:start position:0% wants<00:00:16.260> to<00:00:16.320> talk<00:00:16.440> about<00:00:16.619> an<00:00:16.859> EIP<00:00:17.220> just<00:00:17.520> like 00:00:17.689 --> 00:00:17.699 align:start position:0% wants to talk about an EIP just like 00:00:17.699 --> 00:00:19.730 align:start position:0% wants to talk about an EIP just like raise<00:00:17.880> your<00:00:18.060> hand<00:00:18.180> so<00:00:18.420> we<00:00:18.600> can<00:00:18.720> like<00:00:19.020> roughly 00:00:19.730 --> 00:00:19.740 align:start position:0% raise your hand so we can like roughly 00:00:19.740 --> 00:00:22.609 align:start position:0% raise your hand so we can like roughly keep<00:00:19.980> track<00:00:20.160> of<00:00:20.400> time<00:00:20.580> one<00:00:21.119> okay<00:00:21.480> if<00:00:22.260> you're<00:00:22.500> in 00:00:22.609 --> 00:00:22.619 align:start position:0% keep track of time one okay if you're in 00:00:22.619 --> 00:00:23.870 align:start position:0% keep track of time one okay if you're in the<00:00:22.740> back<00:00:22.859> it's<00:00:23.039> not<00:00:23.220> going<00:00:23.340> to<00:00:23.400> happen<00:00:23.520> you 00:00:23.870 --> 00:00:23.880 align:start position:0% the back it's not going to happen you 00:00:23.880 --> 00:00:26.150 align:start position:0% the back it's not going to happen you need<00:00:24.000> to<00:00:24.119> move<00:00:24.240> forward<00:00:24.420> yeah 00:00:26.150 --> 00:00:26.160 align:start position:0% need to move forward yeah 00:00:26.160 --> 00:00:28.070 align:start position:0% need to move forward yeah okay<00:00:26.279> so<00:00:26.699> sorry<00:00:27.000> I<00:00:27.300> I<00:00:27.420> didn't<00:00:27.660> count<00:00:27.900> because 00:00:28.070 --> 00:00:28.080 align:start position:0% okay so sorry I I didn't count because 00:00:28.080 --> 00:00:32.089 align:start position:0% okay so sorry I I didn't count because these<00:00:28.320> guys<00:00:28.439> again<00:00:29.340> again<00:00:30.180> okay<00:00:30.840> one 00:00:32.089 --> 00:00:32.099 align:start position:0% these guys again again okay one 00:00:32.099 --> 00:00:35.630 align:start position:0% these guys again again okay one one<00:00:32.640> and<00:00:32.880> a<00:00:33.059> half<00:00:33.059> two<00:00:33.600> three<00:00:34.079> four<00:00:34.739> five<00:00:35.219> six 00:00:35.630 --> 00:00:35.640 align:start position:0% one and a half two three four five six 00:00:35.640 --> 00:00:38.389 align:start position:0% one and a half two three four five six seven<00:00:36.000> eight<00:00:36.899> nine<00:00:37.260> okay<00:00:37.559> so<00:00:37.980> we<00:00:38.100> get<00:00:38.219> like 00:00:38.389 --> 00:00:38.399 align:start position:0% seven eight nine okay so we get like 00:00:38.399 --> 00:00:40.910 align:start position:0% seven eight nine okay so we get like five<00:00:38.760> minutes<00:00:39.059> each<00:00:39.660> it's<00:00:40.200> hard<00:00:40.379> to<00:00:40.559> like<00:00:40.680> cap 00:00:40.910 --> 00:00:40.920 align:start position:0% five minutes each it's hard to like cap 00:00:40.920 --> 00:00:41.690 align:start position:0% five minutes each it's hard to like cap that 00:00:41.690 --> 00:00:41.700 align:start position:0% that 00:00:41.700 --> 00:00:44.030 align:start position:0% that okay<00:00:42.059> I<00:00:42.360> can<00:00:42.480> like<00:00:42.719> keep<00:00:42.899> the<00:00:43.079> timer<00:00:43.320> yeah<00:00:43.800> you 00:00:44.030 --> 00:00:44.040 align:start position:0% okay I can like keep the timer yeah you 00:00:44.040 --> 00:00:46.369 align:start position:0% okay I can like keep the timer yeah you can<00:00:44.219> roughly<00:00:44.460> keep<00:00:44.640> track<00:00:44.820> of<00:00:45.059> time<00:00:45.200> should<00:00:46.200> we 00:00:46.369 --> 00:00:46.379 align:start position:0% can roughly keep track of time should we 00:00:46.379 --> 00:00:47.330 align:start position:0% can roughly keep track of time should we start 00:00:47.330 --> 00:00:47.340 align:start position:0% start 00:00:47.340 --> 00:00:50.750 align:start position:0% start yeah okay<00:00:48.300> yeah<00:00:49.379> um<00:00:49.379> okay<00:00:50.100> I'll<00:00:50.340> start<00:00:50.520> I'll 00:00:50.750 --> 00:00:50.760 align:start position:0% yeah okay yeah um okay I'll start I'll 00:00:50.760 --> 00:00:53.930 align:start position:0% yeah okay yeah um okay I'll start I'll start<00:00:50.940> on<00:00:51.059> this<00:00:51.180> side 00:00:53.930 --> 00:00:53.940 align:start position:0% 00:00:53.940 --> 00:00:55.790 align:start position:0% okay 00:00:55.790 --> 00:00:55.800 align:start position:0% okay 00:00:55.800 --> 00:00:57.350 align:start position:0% okay hey<00:00:56.219> guys 00:00:57.350 --> 00:00:57.360 align:start position:0% hey guys 00:00:57.360 --> 00:00:59.569 align:start position:0% hey guys um<00:00:57.420> I'm<00:00:57.719> Sarah<00:00:58.079> I'm<00:00:58.680> a<00:00:58.920> smart<00:00:59.100> contract 00:00:59.569 --> 00:00:59.579 align:start position:0% um I'm Sarah I'm a smart contract 00:00:59.579 --> 00:01:02.150 align:start position:0% um I'm Sarah I'm a smart contract engineer<00:01:00.059> at<00:01:00.300> uniswap 00:01:02.150 --> 00:01:02.160 align:start position:0% engineer at uniswap 00:01:02.160 --> 00:01:03.590 align:start position:0% engineer at uniswap um<00:01:02.340> and<00:01:02.640> I'm<00:01:02.760> here 00:01:03.590 --> 00:01:03.600 align:start position:0% um and I'm here 00:01:03.600 --> 00:01:05.990 align:start position:0% um and I'm here I'm<00:01:04.260> Mark<00:01:04.500> and<00:01:04.920> I'm<00:01:05.100> a<00:01:05.280> protocol<00:01:05.519> developer 00:01:05.990 --> 00:01:06.000 align:start position:0% I'm Mark and I'm a protocol developer 00:01:06.000 --> 00:01:08.750 align:start position:0% I'm Mark and I'm a protocol developer from<00:01:06.240> optimism 00:01:08.750 --> 00:01:08.760 align:start position:0% 00:01:08.760 --> 00:01:14.870 align:start position:0% and<00:01:09.960> um<00:01:10.080> so<00:01:10.619> we're<00:01:10.740> gonna 00:01:14.870 --> 00:01:14.880 align:start position:0% 00:01:14.880 --> 00:01:16.850 align:start position:0% we're<00:01:15.360> in<00:01:15.540> we're<00:01:15.780> done<00:01:15.960> should<00:01:16.320> I<00:01:16.500> drop<00:01:16.619> the 00:01:16.850 --> 00:01:16.860 align:start position:0% we're in we're done should I drop the 00:01:16.860 --> 00:01:18.590 align:start position:0% we're in we're done should I drop the mic 00:01:18.590 --> 00:01:18.600 align:start position:0% mic 00:01:18.600 --> 00:01:20.270 align:start position:0% mic um<00:01:18.720> cool<00:01:19.200> so<00:01:19.439> we're<00:01:19.560> gonna<00:01:19.680> kind<00:01:19.860> of<00:01:19.920> tag<00:01:20.100> team 00:01:20.270 --> 00:01:20.280 align:start position:0% um cool so we're gonna kind of tag team 00:01:20.280 --> 00:01:22.370 align:start position:0% um cool so we're gonna kind of tag team this<00:01:20.640> EIP<00:01:21.060> today 00:01:22.370 --> 00:01:22.380 align:start position:0% this EIP today 00:01:22.380 --> 00:01:24.109 align:start position:0% this EIP today um<00:01:22.439> yeah<00:01:22.979> first<00:01:23.220> of<00:01:23.340> all<00:01:23.400> I<00:01:23.520> want<00:01:23.640> to<00:01:23.759> thank<00:01:23.939> you 00:01:24.109 --> 00:01:24.119 align:start position:0% um yeah first of all I want to thank you 00:01:24.119 --> 00:01:25.490 align:start position:0% um yeah first of all I want to thank you guys<00:01:24.240> for<00:01:24.540> hosting<00:01:24.840> the<00:01:24.960> session<00:01:25.140> I<00:01:25.380> think 00:01:25.490 --> 00:01:25.500 align:start position:0% guys for hosting the session I think 00:01:25.500 --> 00:01:27.350 align:start position:0% guys for hosting the session I think it's<00:01:25.680> super<00:01:25.920> important<00:01:26.400> that<00:01:26.820> you<00:01:27.180> know<00:01:27.240> when 00:01:27.350 --> 00:01:27.360 align:start position:0% it's super important that you know when 00:01:27.360 --> 00:01:29.030 align:start position:0% it's super important that you know when we're<00:01:27.540> planning<00:01:27.840> for<00:01:28.080> building<00:01:28.259> open<00:01:28.560> source 00:01:29.030 --> 00:01:29.040 align:start position:0% we're planning for building open source 00:01:29.040 --> 00:01:30.469 align:start position:0% we're planning for building open source software<00:01:29.280> we're<00:01:29.520> really<00:01:29.700> bringing<00:01:30.060> a<00:01:30.240> lot<00:01:30.299> of 00:01:30.469 --> 00:01:30.479 align:start position:0% software we're really bringing a lot of 00:01:30.479 --> 00:01:33.170 align:start position:0% software we're really bringing a lot of diverse<00:01:30.840> perspectives<00:01:31.259> to<00:01:31.619> the<00:01:31.799> table 00:01:33.170 --> 00:01:33.180 align:start position:0% diverse perspectives to the table 00:01:33.180 --> 00:01:35.270 align:start position:0% diverse perspectives to the table um<00:01:33.299> you<00:01:33.659> know<00:01:33.780> I<00:01:33.840> think<00:01:33.960> it's<00:01:34.259> you<00:01:34.799> know<00:01:34.920> a<00:01:35.159> lot 00:01:35.270 --> 00:01:35.280 align:start position:0% um you know I think it's you know a lot 00:01:35.280 --> 00:01:37.130 align:start position:0% um you know I think it's you know a lot of<00:01:35.400> times<00:01:35.579> client<00:01:36.119> devs<00:01:36.479> and<00:01:36.540> core<00:01:36.600> devs<00:01:37.020> were 00:01:37.130 --> 00:01:37.140 align:start position:0% of times client devs and core devs were 00:01:37.140 --> 00:01:38.990 align:start position:0% of times client devs and core devs were you<00:01:37.320> know<00:01:37.439> focused<00:01:37.860> on<00:01:38.040> this<00:01:38.759> really 00:01:38.990 --> 00:01:39.000 align:start position:0% you know focused on this really 00:01:39.000 --> 00:01:41.630 align:start position:0% you know focused on this really long-term<00:01:39.540> vision<00:01:39.840> for<00:01:40.380> ethereum<00:01:40.979> and 00:01:41.630 --> 00:01:41.640 align:start position:0% long-term vision for ethereum and 00:01:41.640 --> 00:01:43.789 align:start position:0% long-term vision for ethereum and unfortunately<00:01:42.240> for<00:01:42.720> application<00:01:43.259> developers 00:01:43.789 --> 00:01:43.799 align:start position:0% unfortunately for application developers 00:01:43.799 --> 00:01:45.830 align:start position:0% unfortunately for application developers that<00:01:44.100> means<00:01:44.400> some<00:01:45.000> of<00:01:45.119> the<00:01:45.180> stuff<00:01:45.360> we<00:01:45.540> want<00:01:45.720> to 00:01:45.830 --> 00:01:45.840 align:start position:0% that means some of the stuff we want to 00:01:45.840 --> 00:01:48.170 align:start position:0% that means some of the stuff we want to see<00:01:45.960> does<00:01:46.619> not<00:01:46.860> get<00:01:47.280> through 00:01:48.170 --> 00:01:48.180 align:start position:0% see does not get through 00:01:48.180 --> 00:01:50.330 align:start position:0% see does not get through um<00:01:48.240> and<00:01:48.420> so<00:01:48.540> hopefully<00:01:48.960> I'm<00:01:49.500> here<00:01:49.740> today<00:01:49.920> to 00:01:50.330 --> 00:01:50.340 align:start position:0% um and so hopefully I'm here today to 00:01:50.340 --> 00:01:53.330 align:start position:0% um and so hopefully I'm here today to convince<00:01:50.820> you<00:01:50.939> that<00:01:51.360> this<00:01:51.720> is<00:01:52.020> worthwhile<00:01:52.619> and 00:01:53.330 --> 00:01:53.340 align:start position:0% convince you that this is worthwhile and 00:01:53.340 --> 00:01:55.550 align:start position:0% convince you that this is worthwhile and actually<00:01:53.820> this<00:01:54.180> EIP<00:01:54.540> really<00:01:54.840> will<00:01:55.079> complement 00:01:55.550 --> 00:01:55.560 align:start position:0% actually this EIP really will complement 00:01:55.560 --> 00:01:59.510 align:start position:0% actually this EIP really will complement the<00:01:56.040> kind<00:01:56.280> of<00:01:56.340> Future<00:01:56.520> Vision<00:01:56.880> for<00:01:57.780> ethereum 00:01:59.510 --> 00:01:59.520 align:start position:0% the kind of Future Vision for ethereum 00:01:59.520 --> 00:02:00.950 align:start position:0% the kind of Future Vision for ethereum um so<00:01:59.700> let<00:01:59.820> me<00:01:59.939> hand<00:02:00.060> this<00:02:00.240> off<00:02:00.360> to<00:02:00.479> Mark<00:02:00.659> to 00:02:00.950 --> 00:02:00.960 align:start position:0% um so let me hand this off to Mark to 00:02:00.960 --> 00:02:03.649 align:start position:0% um so let me hand this off to Mark to give<00:02:01.140> a<00:02:01.320> little<00:02:01.619> a<00:02:01.920> little<00:02:02.100> rundown 00:02:03.649 --> 00:02:03.659 align:start position:0% give a little a little rundown 00:02:03.659 --> 00:02:05.690 align:start position:0% give a little a little rundown okay<00:02:04.140> so<00:02:04.380> we're<00:02:04.560> here<00:02:04.920> today<00:02:05.100> to<00:02:05.399> talk<00:02:05.520> about 00:02:05.690 --> 00:02:05.700 align:start position:0% okay so we're here today to talk about 00:02:05.700 --> 00:02:10.609 align:start position:0% okay so we're here today to talk about EIP<00:02:06.439> 1153<00:02:07.439> which<00:02:07.860> is<00:02:08.039> transient<00:02:08.759> storage<00:02:09.619> and 00:02:10.609 --> 00:02:10.619 align:start position:0% EIP 1153 which is transient storage and 00:02:10.619 --> 00:02:13.130 align:start position:0% EIP 1153 which is transient storage and this<00:02:10.979> EIP<00:02:11.340> adds<00:02:12.120> two<00:02:12.300> new<00:02:12.540> additional<00:02:12.900> op 00:02:13.130 --> 00:02:13.140 align:start position:0% this EIP adds two new additional op 00:02:13.140 --> 00:02:15.530 align:start position:0% this EIP adds two new additional op codes<00:02:13.319> to<00:02:13.620> the<00:02:13.739> evm<00:02:14.160> and<00:02:14.520> this<00:02:14.700> concept<00:02:15.060> of 00:02:15.530 --> 00:02:15.540 align:start position:0% codes to the evm and this concept of 00:02:15.540 --> 00:02:17.690 align:start position:0% codes to the evm and this concept of transient<00:02:16.260> storage<00:02:16.620> which<00:02:17.220> is<00:02:17.340> basically 00:02:17.690 --> 00:02:17.700 align:start position:0% transient storage which is basically 00:02:17.700 --> 00:02:20.390 align:start position:0% transient storage which is basically like<00:02:17.879> a<00:02:18.000> key<00:02:18.180> Value<00:02:18.360> Store<00:02:18.660> per<00:02:19.080> account<00:02:19.400> and 00:02:20.390 --> 00:02:20.400 align:start position:0% like a key Value Store per account and 00:02:20.400 --> 00:02:23.089 align:start position:0% like a key Value Store per account and anytime<00:02:21.000> that<00:02:21.480> you<00:02:22.200> um<00:02:22.260> you<00:02:22.440> know<00:02:22.500> UT<00:02:22.739> store 00:02:23.089 --> 00:02:23.099 align:start position:0% anytime that you um you know UT store 00:02:23.099 --> 00:02:25.910 align:start position:0% anytime that you um you know UT store your<00:02:23.340> t-load<00:02:23.760> which<00:02:23.879> are<00:02:24.060> synonymous<00:02:24.540> to<00:02:24.900> uh<00:02:25.680> s 00:02:25.910 --> 00:02:25.920 align:start position:0% your t-load which are synonymous to uh s 00:02:25.920 --> 00:02:27.530 align:start position:0% your t-load which are synonymous to uh s load<00:02:26.220> and<00:02:26.340> s<00:02:26.459> store<00:02:26.700> but<00:02:27.000> you<00:02:27.120> instead<00:02:27.480> of 00:02:27.530 --> 00:02:27.540 align:start position:0% load and s store but you instead of 00:02:27.540 --> 00:02:29.030 align:start position:0% load and s store but you instead of putting<00:02:27.780> in<00:02:27.959> a<00:02:28.080> state<00:02:28.200> you<00:02:28.500> put<00:02:28.620> it<00:02:28.739> into<00:02:28.860> this 00:02:29.030 --> 00:02:29.040 align:start position:0% putting in a state you put it into this 00:02:29.040 --> 00:02:31.490 align:start position:0% putting in a state you put it into this transient<00:02:29.400> storage<00:02:29.700> map<00:02:30.020> and<00:02:31.020> each<00:02:31.260> one<00:02:31.379> is 00:02:31.490 --> 00:02:31.500 align:start position:0% transient storage map and each one is 00:02:31.500 --> 00:02:33.650 align:start position:0% transient storage map and each one is namespaced<00:02:32.160> by<00:02:32.280> the<00:02:32.459> account<00:02:32.640> and<00:02:33.480> it 00:02:33.650 --> 00:02:33.660 align:start position:0% namespaced by the account and it 00:02:33.660 --> 00:02:36.050 align:start position:0% namespaced by the account and it persists<00:02:34.140> throughout<00:02:34.620> the<00:02:34.860> duration<00:02:35.220> of<00:02:35.700> the 00:02:36.050 --> 00:02:36.060 align:start position:0% persists throughout the duration of the 00:02:36.060 --> 00:02:38.990 align:start position:0% persists throughout the duration of the single<00:02:36.540> transactions<00:02:37.200> execution 00:02:38.990 --> 00:02:39.000 align:start position:0% single transactions execution 00:02:39.000 --> 00:02:41.570 align:start position:0% single transactions execution yeah<00:02:39.480> and<00:02:39.720> so<00:02:39.840> so<00:02:40.080> actually<00:02:40.379> we<00:02:40.860> have<00:02:41.160> this 00:02:41.570 --> 00:02:41.580 align:start position:0% yeah and so so actually we have this 00:02:41.580 --> 00:02:44.030 align:start position:0% yeah and so so actually we have this concept<00:02:42.000> of<00:02:43.200> um<00:02:43.200> you<00:02:43.500> know<00:02:43.560> kind<00:02:43.680> of<00:02:43.800> storage 00:02:44.030 --> 00:02:44.040 align:start position:0% concept of um you know kind of storage 00:02:44.040 --> 00:02:46.790 align:start position:0% concept of um you know kind of storage is<00:02:44.640> used<00:02:45.000> sometimes<00:02:45.599> in<00:02:45.959> a<00:02:46.080> transient<00:02:46.500> way 00:02:46.790 --> 00:02:46.800 align:start position:0% is used sometimes in a transient way 00:02:46.800 --> 00:02:48.949 align:start position:0% is used sometimes in a transient way right<00:02:47.280> now<00:02:47.400> in<00:02:47.519> the<00:02:47.700> evm<00:02:48.120> you<00:02:48.480> can<00:02:48.599> see<00:02:48.780> this 00:02:48.949 --> 00:02:48.959 align:start position:0% right now in the evm you can see this 00:02:48.959 --> 00:02:51.110 align:start position:0% right now in the evm you can see this sometimes<00:02:49.440> with<00:02:49.800> like<00:02:50.040> re-entrancy<00:02:50.760> locks 00:02:51.110 --> 00:02:51.120 align:start position:0% sometimes with like re-entrancy locks 00:02:51.120 --> 00:02:54.170 align:start position:0% sometimes with like re-entrancy locks right<00:02:51.360> so<00:02:51.780> this<00:02:52.319> is<00:02:52.500> when<00:02:52.800> we<00:02:53.220> clear<00:02:53.519> a<00:02:53.819> slot 00:02:54.170 --> 00:02:54.180 align:start position:0% right so this is when we clear a slot 00:02:54.180 --> 00:02:57.110 align:start position:0% right so this is when we clear a slot back<00:02:54.540> to<00:02:54.780> its<00:02:55.200> original<00:02:55.260> value<00:02:55.879> before<00:02:56.879> the 00:02:57.110 --> 00:02:57.120 align:start position:0% back to its original value before the 00:02:57.120 --> 00:02:58.970 align:start position:0% back to its original value before the end<00:02:57.300> of<00:02:57.420> the<00:02:57.540> transaction<00:02:58.080> and<00:02:58.500> then<00:02:58.620> you<00:02:58.800> know 00:02:58.970 --> 00:02:58.980 align:start position:0% end of the transaction and then you know 00:02:58.980 --> 00:03:02.570 align:start position:0% end of the transaction and then you know we're<00:02:59.580> allotted<00:03:00.300> some<00:03:00.480> amount<00:03:00.780> of<00:03:00.900> of<00:03:01.080> refunds 00:03:02.570 --> 00:03:02.580 align:start position:0% we're allotted some amount of of refunds 00:03:02.580 --> 00:03:05.390 align:start position:0% we're allotted some amount of of refunds um<00:03:02.700> and<00:03:03.420> you<00:03:03.840> know<00:03:03.959> to<00:03:04.200> achieve<00:03:04.560> transientness 00:03:05.390 --> 00:03:05.400 align:start position:0% um and you know to achieve transientness 00:03:05.400 --> 00:03:08.330 align:start position:0% um and you know to achieve transientness in<00:03:05.760> this<00:03:05.940> way<00:03:06.120> is<00:03:06.360> actually<00:03:06.599> quite<00:03:06.900> messy 00:03:08.330 --> 00:03:08.340 align:start position:0% in this way is actually quite messy 00:03:08.340 --> 00:03:10.430 align:start position:0% in this way is actually quite messy um<00:03:08.400> from<00:03:09.000> you<00:03:09.300> know<00:03:09.360> the<00:03:09.660> developer<00:03:10.080> point<00:03:10.260> of 00:03:10.430 --> 00:03:10.440 align:start position:0% um from you know the developer point of 00:03:10.440 --> 00:03:11.869 align:start position:0% um from you know the developer point of view 00:03:11.869 --> 00:03:11.879 align:start position:0% view 00:03:11.879 --> 00:03:13.190 align:start position:0% view um<00:03:12.000> you<00:03:12.420> know<00:03:12.480> it's<00:03:12.720> really<00:03:13.019> not 00:03:13.190 --> 00:03:13.200 align:start position:0% um you know it's really not 00:03:13.200 --> 00:03:15.290 align:start position:0% um you know it's really not straightforward<00:03:13.860> you<00:03:14.280> know<00:03:14.400> how<00:03:14.879> the 00:03:15.290 --> 00:03:15.300 align:start position:0% straightforward you know how the 00:03:15.300 --> 00:03:17.270 align:start position:0% straightforward you know how the accounting<00:03:15.720> will<00:03:15.959> work<00:03:16.140> for<00:03:16.379> this 00:03:17.270 --> 00:03:17.280 align:start position:0% accounting will work for this 00:03:17.280 --> 00:03:18.589 align:start position:0% accounting will work for this um<00:03:17.340> especially<00:03:17.640> because<00:03:17.819> refunds<00:03:18.360> are<00:03:18.480> now 00:03:18.589 --> 00:03:18.599 align:start position:0% um especially because refunds are now 00:03:18.599 --> 00:03:19.910 align:start position:0% um especially because refunds are now capped 00:03:19.910 --> 00:03:19.920 align:start position:0% capped 00:03:19.920 --> 00:03:21.290 align:start position:0% capped um<00:03:20.040> and<00:03:20.220> so<00:03:20.340> you<00:03:20.519> know<00:03:20.640> enshrining<00:03:21.180> this 00:03:21.290 --> 00:03:21.300 align:start position:0% um and so you know enshrining this 00:03:21.300 --> 00:03:23.390 align:start position:0% um and so you know enshrining this directly<00:03:21.599> in<00:03:21.780> the<00:03:21.959> evm<00:03:22.319> is<00:03:22.620> is<00:03:22.860> a<00:03:23.099> more<00:03:23.220> direct 00:03:23.390 --> 00:03:23.400 align:start position:0% directly in the evm is is a more direct 00:03:23.400 --> 00:03:27.050 align:start position:0% directly in the evm is is a more direct uh<00:03:24.180> kind<00:03:24.360> of<00:03:24.480> use<00:03:24.659> case<00:03:24.900> to<00:03:25.140> get<00:03:25.260> transientness 00:03:27.050 --> 00:03:27.060 align:start position:0% uh kind of use case to get transientness 00:03:27.060 --> 00:03:28.729 align:start position:0% uh kind of use case to get transientness um<00:03:27.120> you<00:03:27.420> know<00:03:27.480> also<00:03:27.780> developers<00:03:28.319> are<00:03:28.500> kind<00:03:28.680> of 00:03:28.729 --> 00:03:28.739 align:start position:0% um you know also developers are kind of 00:03:28.739 --> 00:03:30.350 align:start position:0% um you know also developers are kind of having<00:03:28.860> to<00:03:29.040> go<00:03:29.220> and<00:03:29.400> do<00:03:29.580> the<00:03:29.700> sort<00:03:29.879> of<00:03:29.940> messy 00:03:30.350 --> 00:03:30.360 align:start position:0% having to go and do the sort of messy 00:03:30.360 --> 00:03:32.030 align:start position:0% having to go and do the sort of messy implementation<00:03:30.900> where<00:03:31.319> you'll<00:03:31.500> see<00:03:31.680> a<00:03:31.860> lot<00:03:31.920> of 00:03:32.030 --> 00:03:32.040 align:start position:0% implementation where you'll see a lot of 00:03:32.040 --> 00:03:34.610 align:start position:0% implementation where you'll see a lot of times<00:03:32.159> like<00:03:32.519> you<00:03:33.120> know<00:03:33.180> one<00:03:33.540> zero<00:03:33.900> one<00:03:34.080> instead 00:03:34.610 --> 00:03:34.620 align:start position:0% times like you know one zero one instead 00:03:34.620 --> 00:03:37.070 align:start position:0% times like you know one zero one instead of<00:03:34.739> clearing<00:03:35.220> to<00:03:35.519> zero<00:03:35.879> we're<00:03:36.060> clearing<00:03:36.540> to 00:03:37.070 --> 00:03:37.080 align:start position:0% of clearing to zero we're clearing to 00:03:37.080 --> 00:03:39.470 align:start position:0% of clearing to zero we're clearing to some<00:03:37.920> dirtied<00:03:38.340> value<00:03:38.640> because<00:03:38.940> as<00:03:39.300> we 00:03:39.470 --> 00:03:39.480 align:start position:0% some dirtied value because as we 00:03:39.480 --> 00:03:41.869 align:start position:0% some dirtied value because as we actually<00:03:39.599> end<00:03:39.840> up<00:03:39.959> getting<00:03:40.459> you<00:03:41.459> know<00:03:41.519> more 00:03:41.869 --> 00:03:41.879 align:start position:0% actually end up getting you know more 00:03:41.879 --> 00:03:43.850 align:start position:0% actually end up getting you know more refunds<00:03:42.480> in<00:03:42.599> that<00:03:42.780> case<00:03:42.959> and<00:03:43.200> so<00:03:43.379> it's<00:03:43.680> really 00:03:43.850 --> 00:03:43.860 align:start position:0% refunds in that case and so it's really 00:03:43.860 --> 00:03:45.949 align:start position:0% refunds in that case and so it's really the<00:03:44.040> sort<00:03:44.280> of<00:03:44.400> patchy<00:03:45.000> way<00:03:45.299> of<00:03:45.540> achieving 00:03:45.949 --> 00:03:45.959 align:start position:0% the sort of patchy way of achieving 00:03:45.959 --> 00:03:48.949 align:start position:0% the sort of patchy way of achieving transientness<00:03:46.620> in<00:03:46.920> the<00:03:47.099> evm<00:03:47.540> and<00:03:48.540> so<00:03:48.659> kind<00:03:48.840> of 00:03:48.949 --> 00:03:48.959 align:start position:0% transientness in the evm and so kind of 00:03:48.959 --> 00:03:51.350 align:start position:0% transientness in the evm and so kind of the<00:03:49.019> way<00:03:49.200> that<00:03:49.500> that<00:03:49.680> we<00:03:50.099> look<00:03:50.340> at<00:03:50.580> this<00:03:50.700> EIP<00:03:51.060> is 00:03:51.350 --> 00:03:51.360 align:start position:0% the way that that we look at this EIP is 00:03:51.360 --> 00:03:53.030 align:start position:0% the way that that we look at this EIP is actually<00:03:51.540> sort<00:03:51.780> of<00:03:51.900> a<00:03:52.019> cleanup<00:03:52.379> it's<00:03:52.739> it's 00:03:53.030 --> 00:03:53.040 align:start position:0% actually sort of a cleanup it's it's 00:03:53.040 --> 00:03:55.610 align:start position:0% actually sort of a cleanup it's it's relieving<00:03:53.640> some<00:03:53.819> of<00:03:53.940> this<00:03:54.060> Tech<00:03:54.299> depth<00:03:54.780> here 00:03:55.610 --> 00:03:55.620 align:start position:0% relieving some of this Tech depth here 00:03:55.620 --> 00:03:57.229 align:start position:0% relieving some of this Tech depth here um<00:03:55.680> because<00:03:55.860> this<00:03:56.159> is<00:03:56.340> a<00:03:56.519> real<00:03:56.640> use<00:03:56.879> case<00:03:57.060> and 00:03:57.229 --> 00:03:57.239 align:start position:0% um because this is a real use case and 00:03:57.239 --> 00:04:00.050 align:start position:0% um because this is a real use case and it<00:03:57.360> is<00:03:57.540> wanted 00:04:00.050 --> 00:04:00.060 align:start position:0% 00:04:00.060 --> 00:04:02.330 align:start position:0% so<00:04:00.599> one<00:04:00.959> really<00:04:01.200> cool<00:04:01.440> side<00:04:01.739> effect<00:04:01.920> of<00:04:02.159> this 00:04:02.330 --> 00:04:02.340 align:start position:0% so one really cool side effect of this 00:04:02.340 --> 00:04:04.009 align:start position:0% so one really cool side effect of this is<00:04:02.879> it<00:04:03.180> actually<00:04:03.299> helps<00:04:03.659> a<00:04:03.780> lot<00:04:03.840> with 00:04:04.009 --> 00:04:04.019 align:start position:0% is it actually helps a lot with 00:04:04.019 --> 00:04:06.470 align:start position:0% is it actually helps a lot with parallelization<00:04:04.739> because 00:04:06.470 --> 00:04:06.480 align:start position:0% parallelization because 00:04:06.480 --> 00:04:07.729 align:start position:0% parallelization because um<00:04:06.540> you<00:04:06.720> know<00:04:06.780> we<00:04:06.900> want<00:04:07.019> we<00:04:07.319> want<00:04:07.379> to<00:04:07.500> scale 00:04:07.729 --> 00:04:07.739 align:start position:0% um you know we want we want to scale 00:04:07.739 --> 00:04:09.410 align:start position:0% um you know we want we want to scale ethereum<00:04:08.220> we<00:04:08.459> want<00:04:08.580> to<00:04:08.760> increase<00:04:09.120> the 00:04:09.410 --> 00:04:09.420 align:start position:0% ethereum we want to increase the 00:04:09.420 --> 00:04:10.789 align:start position:0% ethereum we want to increase the throughput<00:04:09.780> of<00:04:09.959> the<00:04:10.080> system<00:04:10.200> and<00:04:10.500> we<00:04:10.560> can<00:04:10.680> do 00:04:10.789 --> 00:04:10.799 align:start position:0% throughput of the system and we can do 00:04:10.799 --> 00:04:13.429 align:start position:0% throughput of the system and we can do that<00:04:10.980> by<00:04:11.220> paralyzing<00:04:11.819> the<00:04:12.000> evm<00:04:12.420> and<00:04:13.019> right<00:04:13.260> now 00:04:13.429 --> 00:04:13.439 align:start position:0% that by paralyzing the evm and right now 00:04:13.439 --> 00:04:15.890 align:start position:0% that by paralyzing the evm and right now anytime<00:04:14.099> that<00:04:14.459> there<00:04:14.879> is 00:04:15.890 --> 00:04:15.900 align:start position:0% anytime that there is 00:04:15.900 --> 00:04:18.229 align:start position:0% anytime that there is um a<00:04:16.440> lock<00:04:16.620> taken<00:04:17.100> in<00:04:17.280> a<00:04:17.459> contract<00:04:17.760> it<00:04:18.120> is 00:04:18.229 --> 00:04:18.239 align:start position:0% um a lock taken in a contract it is 00:04:18.239 --> 00:04:20.150 align:start position:0% um a lock taken in a contract it is writing<00:04:18.600> the<00:04:18.720> storage<00:04:18.959> and<00:04:19.500> that<00:04:19.680> prevents 00:04:20.150 --> 00:04:20.160 align:start position:0% writing the storage and that prevents 00:04:20.160 --> 00:04:22.550 align:start position:0% writing the storage and that prevents parallelization<00:04:21.000> of<00:04:21.660> that<00:04:21.840> transaction<00:04:22.260> with 00:04:22.550 --> 00:04:22.560 align:start position:0% parallelization of that transaction with 00:04:22.560 --> 00:04:24.469 align:start position:0% parallelization of that transaction with other<00:04:22.800> transactions<00:04:23.460> that<00:04:24.000> are<00:04:24.120> trying<00:04:24.300> to 00:04:24.469 --> 00:04:24.479 align:start position:0% other transactions that are trying to 00:04:24.479 --> 00:04:25.969 align:start position:0% other transactions that are trying to interact<00:04:24.780> with<00:04:24.900> the<00:04:25.080> same<00:04:25.199> contract<00:04:25.500> so<00:04:25.740> if<00:04:25.860> we 00:04:25.969 --> 00:04:25.979 align:start position:0% interact with the same contract so if we 00:04:25.979 --> 00:04:27.590 align:start position:0% interact with the same contract so if we move<00:04:26.160> all<00:04:26.340> these<00:04:26.580> into<00:04:26.820> transient<00:04:27.300> storage 00:04:27.590 --> 00:04:27.600 align:start position:0% move all these into transient storage 00:04:27.600 --> 00:04:29.390 align:start position:0% move all these into transient storage instead<00:04:28.020> then<00:04:28.259> we'll<00:04:28.440> be<00:04:28.560> able<00:04:28.680> to<00:04:28.740> paralyze<00:04:29.220> a 00:04:29.390 --> 00:04:29.400 align:start position:0% instead then we'll be able to paralyze a 00:04:29.400 --> 00:04:31.550 align:start position:0% instead then we'll be able to paralyze a lot<00:04:29.520> more<00:04:29.639> transactions<00:04:30.360> and<00:04:30.960> it's<00:04:31.139> important 00:04:31.550 --> 00:04:31.560 align:start position:0% lot more transactions and it's important 00:04:31.560 --> 00:04:33.890 align:start position:0% lot more transactions and it's important to<00:04:31.860> try<00:04:31.979> to<00:04:32.100> get<00:04:32.280> this<00:04:32.460> change<00:04:32.699> in<00:04:32.940> sooner 00:04:33.890 --> 00:04:33.900 align:start position:0% to try to get this change in sooner 00:04:33.900 --> 00:04:35.450 align:start position:0% to try to get this change in sooner rather<00:04:34.199> than<00:04:34.380> later<00:04:34.620> so<00:04:34.919> we<00:04:35.100> can<00:04:35.220> start 00:04:35.450 --> 00:04:35.460 align:start position:0% rather than later so we can start 00:04:35.460 --> 00:04:38.210 align:start position:0% rather than later so we can start adopting<00:04:36.060> this<00:04:36.300> pattern<00:04:36.660> now<00:04:37.080> and<00:04:37.680> have<00:04:37.979> more 00:04:38.210 --> 00:04:38.220 align:start position:0% adopting this pattern now and have more 00:04:38.220 --> 00:04:40.969 align:start position:0% adopting this pattern now and have more of<00:04:38.400> the<00:04:38.520> network<00:04:38.699> using<00:04:39.419> this<00:04:39.720> kind<00:04:40.080> of<00:04:40.199> way<00:04:40.740> of 00:04:40.969 --> 00:04:40.979 align:start position:0% of the network using this kind of way of 00:04:40.979 --> 00:04:44.749 align:start position:0% of the network using this kind of way of doing<00:04:41.520> locks<00:04:42.060> so<00:04:42.660> we<00:04:42.840> can<00:04:43.080> have<00:04:43.800> more<00:04:44.160> parallel 00:04:44.749 --> 00:04:44.759 align:start position:0% doing locks so we can have more parallel 00:04:44.759 --> 00:04:47.090 align:start position:0% doing locks so we can have more parallel execution<00:04:45.240> in<00:04:45.479> the<00:04:45.600> future 00:04:47.090 --> 00:04:47.100 align:start position:0% execution in the future 00:04:47.100 --> 00:04:49.129 align:start position:0% execution in the future another<00:04:48.000> problem<00:04:48.360> is<00:04:48.660> that<00:04:48.840> it's<00:04:48.960> really 00:04:49.129 --> 00:04:49.139 align:start position:0% another problem is that it's really 00:04:49.139 --> 00:04:52.490 align:start position:0% another problem is that it's really difficult<00:04:49.440> to<00:04:50.160> know<00:04:50.460> how<00:04:51.180> much<00:04:51.360> gas<00:04:51.720> or<00:04:52.080> how 00:04:52.490 --> 00:04:52.500 align:start position:0% difficult to know how much gas or how 00:04:52.500 --> 00:04:53.749 align:start position:0% difficult to know how much gas or how much<00:04:52.620> gas<00:04:52.740> is<00:04:52.919> going<00:04:53.100> to<00:04:53.160> be<00:04:53.220> used<00:04:53.340> when<00:04:53.580> you're 00:04:53.749 --> 00:04:53.759 align:start position:0% much gas is going to be used when you're 00:04:53.759 --> 00:04:55.189 align:start position:0% much gas is going to be used when you're allocating<00:04:54.120> memory<00:04:54.479> because<00:04:54.720> there's<00:04:54.960> this 00:04:55.189 --> 00:04:55.199 align:start position:0% allocating memory because there's this 00:04:55.199 --> 00:04:57.409 align:start position:0% allocating memory because there's this like<00:04:55.380> crazy<00:04:55.860> non-linear<00:04:56.460> function 00:04:57.409 --> 00:04:57.419 align:start position:0% like crazy non-linear function 00:04:57.419 --> 00:04:58.909 align:start position:0% like crazy non-linear function so<00:04:57.840> this<00:04:58.080> makes<00:04:58.259> it<00:04:58.500> much<00:04:58.740> more 00:04:58.909 --> 00:04:58.919 align:start position:0% so this makes it much more 00:04:58.919 --> 00:05:01.430 align:start position:0% so this makes it much more straightforward<00:04:59.520> because<00:05:00.180> every<00:05:00.900> you<00:05:01.380> know 00:05:01.430 --> 00:05:01.440 align:start position:0% straightforward because every you know 00:05:01.440 --> 00:05:04.249 align:start position:0% straightforward because every you know t-store<00:05:01.979> uses<00:05:02.520> the<00:05:02.759> same<00:05:02.880> amount<00:05:03.120> of<00:05:03.300> gas<00:05:03.479> so 00:05:04.249 --> 00:05:04.259 align:start position:0% t-store uses the same amount of gas so 00:05:04.259 --> 00:05:06.170 align:start position:0% t-store uses the same amount of gas so it's<00:05:04.380> easier<00:05:04.740> for<00:05:04.979> a<00:05:05.100> developer<00:05:05.460> to<00:05:05.699> like<00:05:05.880> know 00:05:06.170 --> 00:05:06.180 align:start position:0% it's easier for a developer to like know 00:05:06.180 --> 00:05:08.030 align:start position:0% it's easier for a developer to like know how<00:05:06.479> much<00:05:06.600> gas<00:05:06.900> they're<00:05:07.199> going<00:05:07.440> to<00:05:07.560> be<00:05:07.680> using 00:05:08.030 --> 00:05:08.040 align:start position:0% how much gas they're going to be using 00:05:08.040 --> 00:05:09.290 align:start position:0% how much gas they're going to be using when<00:05:08.460> they're<00:05:08.699> writing<00:05:09.060> their<00:05:09.120> smart 00:05:09.290 --> 00:05:09.300 align:start position:0% when they're writing their smart 00:05:09.300 --> 00:05:11.749 align:start position:0% when they're writing their smart contracts 00:05:11.749 --> 00:05:11.759 align:start position:0% contracts 00:05:11.759 --> 00:05:13.790 align:start position:0% contracts cool<00:05:12.180> and<00:05:12.360> kind<00:05:12.780> of<00:05:12.900> on<00:05:13.020> the<00:05:13.139> on<00:05:13.320> the<00:05:13.500> last<00:05:13.620> note 00:05:13.790 --> 00:05:13.800 align:start position:0% cool and kind of on the on the last note 00:05:13.800 --> 00:05:15.409 align:start position:0% cool and kind of on the on the last note here<00:05:14.160> I<00:05:14.400> just<00:05:14.520> want<00:05:14.639> to<00:05:14.759> re-emphasize<00:05:15.240> that 00:05:15.409 --> 00:05:15.419 align:start position:0% here I just want to re-emphasize that 00:05:15.419 --> 00:05:17.270 align:start position:0% here I just want to re-emphasize that this<00:05:15.660> is<00:05:15.780> not<00:05:16.020> necessarily<00:05:16.440> an<00:05:16.680> addition<00:05:16.979> to 00:05:17.270 --> 00:05:17.280 align:start position:0% this is not necessarily an addition to 00:05:17.280 --> 00:05:18.950 align:start position:0% this is not necessarily an addition to the<00:05:17.400> evm<00:05:17.880> it's<00:05:18.000> it's<00:05:18.180> really<00:05:18.419> we're<00:05:18.660> thinking 00:05:18.950 --> 00:05:18.960 align:start position:0% the evm it's it's really we're thinking 00:05:18.960 --> 00:05:22.010 align:start position:0% the evm it's it's really we're thinking about<00:05:19.080> it<00:05:19.320> as<00:05:19.500> a<00:05:20.040> cleanup<00:05:20.400> a<00:05:20.759> cleaner<00:05:21.300> way<00:05:21.540> of 00:05:22.010 --> 00:05:22.020 align:start position:0% about it as a cleanup a cleaner way of 00:05:22.020 --> 00:05:25.730 align:start position:0% about it as a cleanup a cleaner way of of<00:05:22.259> achieving<00:05:22.860> this<00:05:23.160> use<00:05:23.340> case<00:05:23.580> in<00:05:23.880> the<00:05:24.000> evm<00:05:24.740> I 00:05:25.730 --> 00:05:25.740 align:start position:0% of achieving this use case in the evm I 00:05:25.740 --> 00:05:27.469 align:start position:0% of achieving this use case in the evm I also<00:05:25.979> want<00:05:26.100> to<00:05:26.220> point<00:05:26.699> out<00:05:26.820> this<00:05:27.000> is<00:05:27.120> a<00:05:27.360> really 00:05:27.469 --> 00:05:27.479 align:start position:0% also want to point out this is a really 00:05:27.479 --> 00:05:30.590 align:start position:0% also want to point out this is a really siled<00:05:28.139> change<00:05:28.500> it's<00:05:28.919> two<00:05:29.460> op<00:05:29.699> codes<00:05:30.000> it's 00:05:30.590 --> 00:05:30.600 align:start position:0% siled change it's two op codes it's 00:05:30.600 --> 00:05:32.330 align:start position:0% siled change it's two op codes it's easily<00:05:31.020> testable 00:05:32.330 --> 00:05:32.340 align:start position:0% easily testable 00:05:32.340 --> 00:05:36.290 align:start position:0% easily testable um<00:05:32.479> and<00:05:33.479> uh<00:05:34.500> also<00:05:35.220> benefit<00:05:35.400> it's<00:05:35.759> already<00:05:36.000> been 00:05:36.290 --> 00:05:36.300 align:start position:0% um and uh also benefit it's already been 00:05:36.300 --> 00:05:38.749 align:start position:0% um and uh also benefit it's already been implemented<00:05:36.840> across<00:05:37.320> four<00:05:37.500> clients<00:05:37.979> so 00:05:38.749 --> 00:05:38.759 align:start position:0% implemented across four clients so 00:05:38.759 --> 00:05:41.870 align:start position:0% implemented across four clients so nethermind<00:05:39.419> Bay<00:05:39.780> Zoo<00:05:40.080> ethereum<00:05:41.039> JM<00:05:41.520> or 00:05:41.870 --> 00:05:41.880 align:start position:0% nethermind Bay Zoo ethereum JM or 00:05:41.880 --> 00:05:46.010 align:start position:0% nethermind Bay Zoo ethereum JM or ethereum<00:05:42.300> jmbs<00:05:43.080> and<00:05:43.680> uh<00:05:44.220> also<00:05:45.060> Geth<00:05:45.479> is 00:05:46.010 --> 00:05:46.020 align:start position:0% ethereum jmbs and uh also Geth is 00:05:46.020 --> 00:05:48.050 align:start position:0% ethereum jmbs and uh also Geth is implemented<00:05:46.740> we've<00:05:47.100> also<00:05:47.280> written<00:05:47.580> tests<00:05:47.940> for 00:05:48.050 --> 00:05:48.060 align:start position:0% implemented we've also written tests for 00:05:48.060 --> 00:05:49.790 align:start position:0% implemented we've also written tests for this<00:05:48.180> they<00:05:48.479> all<00:05:48.660> pass 00:05:49.790 --> 00:05:49.800 align:start position:0% this they all pass 00:05:49.800 --> 00:05:51.350 align:start position:0% this they all pass um<00:05:49.860> and<00:05:50.039> so<00:05:50.160> the<00:05:50.280> kind<00:05:50.699> of<00:05:50.820> the<00:05:50.940> final<00:05:51.060> ask 00:05:51.350 --> 00:05:51.360 align:start position:0% um and so the kind of the final ask 00:05:51.360 --> 00:05:52.969 align:start position:0% um and so the kind of the final ask today<00:05:51.660> is<00:05:51.840> to<00:05:52.020> just<00:05:52.199> really<00:05:52.320> get<00:05:52.560> some<00:05:52.800> more 00:05:52.969 --> 00:05:52.979 align:start position:0% today is to just really get some more 00:05:52.979 --> 00:05:55.430 align:start position:0% today is to just really get some more client<00:05:53.520> Dev<00:05:53.759> eyes<00:05:54.060> on<00:05:54.419> these<00:05:54.600> PRS<00:05:55.080> on<00:05:55.320> the 00:05:55.430 --> 00:05:55.440 align:start position:0% client Dev eyes on these PRS on the 00:05:55.440 --> 00:05:57.350 align:start position:0% client Dev eyes on these PRS on the tests<00:05:55.680> we've<00:05:55.919> written<00:05:56.220> and<00:05:56.759> to<00:05:56.940> actually<00:05:57.060> kind 00:05:57.350 --> 00:05:57.360 align:start position:0% tests we've written and to actually kind 00:05:57.360 --> 00:05:59.090 align:start position:0% tests we've written and to actually kind of<00:05:57.479> seriously<00:05:57.840> open<00:05:58.020> this<00:05:58.320> conversation<00:05:58.800> of 00:05:59.090 --> 00:05:59.100 align:start position:0% of seriously open this conversation of 00:05:59.100 --> 00:06:03.469 align:start position:0% of seriously open this conversation of having<00:05:59.280> CFI<00:05:59.940> for<00:06:00.180> 1153<00:06:00.960> in<00:06:01.680> Shanghai 00:06:03.469 --> 00:06:03.479 align:start position:0% having CFI for 1153 in Shanghai 00:06:03.479 --> 00:06:05.990 align:start position:0% having CFI for 1153 in Shanghai um<00:06:03.600> thank<00:06:03.900> you 00:06:05.990 --> 00:06:06.000 align:start position:0% um thank you 00:06:06.000 --> 00:06:08.029 align:start position:0% um thank you I<00:06:06.539> guess<00:06:06.720> just<00:06:07.080> to<00:06:07.199> make<00:06:07.380> sure<00:06:07.440> we<00:06:07.680> have<00:06:07.800> time 00:06:08.029 --> 00:06:08.039 align:start position:0% I guess just to make sure we have time 00:06:08.039 --> 00:06:10.370 align:start position:0% I guess just to make sure we have time like<00:06:08.340> are<00:06:08.940> there<00:06:09.120> like<00:06:09.360> a<00:06:09.539> couple<00:06:09.660> client<00:06:10.080> devs 00:06:10.370 --> 00:06:10.380 align:start position:0% like are there like a couple client devs 00:06:10.380 --> 00:06:11.570 align:start position:0% like are there like a couple client devs with<00:06:10.440> strong<00:06:10.680> opinions<00:06:11.039> about<00:06:11.220> this<00:06:11.400> we 00:06:11.570 --> 00:06:11.580 align:start position:0% with strong opinions about this we 00:06:11.580 --> 00:06:13.670 align:start position:0% with strong opinions about this we probably<00:06:11.820> can't<00:06:12.000> do<00:06:12.180> everyone<00:06:12.360> but<00:06:12.720> uh<00:06:13.320> okay<00:06:13.440> I 00:06:13.670 --> 00:06:13.680 align:start position:0% probably can't do everyone but uh okay I 00:06:13.680 --> 00:06:15.590 align:start position:0% probably can't do everyone but uh okay I know<00:06:13.860> first<00:06:14.100> I<00:06:14.699> have<00:06:14.880> a<00:06:14.940> minute<00:06:15.060> opinion<00:06:15.479> on 00:06:15.590 --> 00:06:15.600 align:start position:0% know first I have a minute opinion on 00:06:15.600 --> 00:06:17.510 align:start position:0% know first I have a minute opinion on this<00:06:15.720> I<00:06:15.960> think<00:06:16.080> it's<00:06:16.259> awesome<00:06:16.560> that<00:06:17.100> people 00:06:17.510 --> 00:06:17.520 align:start position:0% this I think it's awesome that people 00:06:17.520 --> 00:06:19.189 align:start position:0% this I think it's awesome that people from<00:06:17.759> outside<00:06:17.940> the<00:06:18.180> core<00:06:18.300> team<00:06:18.600> are<00:06:18.900> not<00:06:19.020> just 00:06:19.189 --> 00:06:19.199 align:start position:0% from outside the core team are not just 00:06:19.199 --> 00:06:20.990 align:start position:0% from outside the core team are not just riding<00:06:19.680> the<00:06:19.800> spec<00:06:20.039> writing<00:06:20.880> the 00:06:20.990 --> 00:06:21.000 align:start position:0% riding the spec writing the 00:06:21.000 --> 00:06:22.550 align:start position:0% riding the spec writing the implementation<00:06:21.479> but<00:06:21.720> also<00:06:21.960> writing<00:06:22.440> the 00:06:22.550 --> 00:06:22.560 align:start position:0% implementation but also writing the 00:06:22.560 --> 00:06:25.620 align:start position:0% implementation but also writing the tests<00:06:22.979> I<00:06:23.639> mean<00:06:23.819> big<00:06:24.120> round<00:06:24.300> of<00:06:24.479> applause 00:06:25.620 --> 00:06:25.630 align:start position:0% tests I mean big round of applause 00:06:25.630 --> 00:06:27.000 align:start position:0% tests I mean big round of applause [Applause] 00:06:27.000 --> 00:06:27.010 align:start position:0% [Applause] 00:06:27.010 --> 00:06:30.650 align:start position:0% [Applause] [Music] 00:06:30.650 --> 00:06:30.660 align:start position:0% 00:06:30.660 --> 00:06:32.749 align:start position:0% any<00:06:31.020> other<00:06:31.259> comments 00:06:32.749 --> 00:06:32.759 align:start position:0% any other comments 00:06:32.759 --> 00:06:34.850 align:start position:0% any other comments Peter<00:06:33.240> so 00:06:34.850 --> 00:06:34.860 align:start position:0% Peter so 00:06:34.860 --> 00:06:37.550 align:start position:0% Peter so um only<00:06:35.160> know<00:06:35.520> just<00:06:35.940> FYI<00:06:36.660> I<00:06:36.780> do<00:06:37.020> like<00:06:37.139> the<00:06:37.319> EIP 00:06:37.550 --> 00:06:37.560 align:start position:0% um only know just FYI I do like the EIP 00:06:37.560 --> 00:06:38.870 align:start position:0% um only know just FYI I do like the EIP however 00:06:38.870 --> 00:06:38.880 align:start position:0% however 00:06:38.880 --> 00:06:40.610 align:start position:0% however um<00:06:39.000> I<00:06:39.539> kind<00:06:39.660> of<00:06:39.720> have<00:06:39.840> a<00:06:40.020> feeling<00:06:40.139> that<00:06:40.440> the 00:06:40.610 --> 00:06:40.620 align:start position:0% um I kind of have a feeling that the 00:06:40.620 --> 00:06:42.590 align:start position:0% um I kind of have a feeling that the russianizations<00:06:41.400> are<00:06:41.759> not<00:06:41.940> necessarily<00:06:42.360> all 00:06:42.590 --> 00:06:42.600 align:start position:0% russianizations are not necessarily all 00:06:42.600 --> 00:06:44.870 align:start position:0% russianizations are not necessarily all equally<00:06:43.380> valid<00:06:43.800> with<00:06:44.400> the<00:06:44.580> parallel 00:06:44.870 --> 00:06:44.880 align:start position:0% equally valid with the parallel 00:06:44.880 --> 00:06:47.330 align:start position:0% equally valid with the parallel execution<00:06:45.419> I<00:06:46.080> think<00:06:46.139> that's<00:06:46.319> kind<00:06:46.560> of<00:06:46.740> a<00:06:47.039> far 00:06:47.330 --> 00:06:47.340 align:start position:0% execution I think that's kind of a far 00:06:47.340 --> 00:06:50.150 align:start position:0% execution I think that's kind of a far away<00:06:47.520> dream<00:06:47.880> so<00:06:48.240> I<00:06:48.419> I<00:06:48.840> yeah 00:06:50.150 --> 00:06:50.160 align:start position:0% away dream so I I yeah 00:06:50.160 --> 00:06:52.490 align:start position:0% away dream so I I yeah I<00:06:50.639> mean<00:06:50.960> essentially<00:06:51.960> every<00:06:52.139> time<00:06:52.319> you 00:06:52.490 --> 00:06:52.500 align:start position:0% I mean essentially every time you 00:06:52.500 --> 00:06:54.590 align:start position:0% I mean essentially every time you execute<00:06:52.800> a<00:06:52.979> transaction<00:06:53.340> you<00:06:54.240> will<00:06:54.360> touch 00:06:54.590 --> 00:06:54.600 align:start position:0% execute a transaction you will touch 00:06:54.600 --> 00:06:56.090 align:start position:0% execute a transaction you will touch some<00:06:54.900> state<00:06:55.139> so<00:06:55.380> if<00:06:55.500> you<00:06:55.560> touch<00:06:55.740> the<00:06:55.979> same 00:06:56.090 --> 00:06:56.100 align:start position:0% some state so if you touch the same 00:06:56.100 --> 00:06:57.469 align:start position:0% some state so if you touch the same contract<00:06:56.460> you<00:06:56.580> will<00:06:56.759> touch<00:06:56.880> the<00:06:57.120> state<00:06:57.180> some 00:06:57.469 --> 00:06:57.479 align:start position:0% contract you will touch the state some 00:06:57.479 --> 00:06:59.029 align:start position:0% contract you will touch the state some State<00:06:57.660> anyway<00:06:57.840> so<00:06:58.259> that<00:06:58.380> I<00:06:58.620> don't<00:06:58.740> think<00:06:58.860> it 00:06:59.029 --> 00:06:59.039 align:start position:0% State anyway so that I don't think it 00:06:59.039 --> 00:07:02.270 align:start position:0% State anyway so that I don't think it helps<00:06:59.400> there<00:07:00.060> however<00:07:00.720> I<00:07:01.259> I<00:07:01.740> mean<00:07:01.919> personally 00:07:02.270 --> 00:07:02.280 align:start position:0% helps there however I I mean personally 00:07:02.280 --> 00:07:04.670 align:start position:0% helps there however I I mean personally I<00:07:02.400> think<00:07:02.520> it<00:07:02.940> might<00:07:03.120> be<00:07:03.300> nice<00:07:03.539> one<00:07:04.380> thing<00:07:04.560> it 00:07:04.670 --> 00:07:04.680 align:start position:0% I think it might be nice one thing it 00:07:04.680 --> 00:07:07.790 align:start position:0% I think it might be nice one thing it would<00:07:04.919> be 00:07:07.790 --> 00:07:07.800 align:start position:0% 00:07:07.800 --> 00:07:16.450 align:start position:0% yeah<00:07:08.160> let's<00:07:08.520> just<00:07:08.699> keep<00:07:09.000> it<00:07:09.120> at<00:07:09.300> that 00:07:16.450 --> 00:07:16.460 align:start position:0% 00:07:16.460 --> 00:07:19.610 align:start position:0% I<00:07:17.460> I<00:07:17.460> don't<00:07:18.060> really<00:07:18.180> see<00:07:18.479> the<00:07:18.600> point<00:07:18.780> but<00:07:19.199> I'm 00:07:19.610 --> 00:07:19.620 align:start position:0% I I don't really see the point but I'm 00:07:19.620 --> 00:07:22.010 align:start position:0% I I don't really see the point but I'm also<00:07:19.919> not<00:07:20.099> a<00:07:20.340> not<00:07:20.580> a<00:07:20.819> not<00:07:21.120> a<00:07:21.419> contract 00:07:22.010 --> 00:07:22.020 align:start position:0% also not a not a not a contract 00:07:22.020 --> 00:07:23.450 align:start position:0% also not a not a not a contract developer 00:07:23.450 --> 00:07:23.460 align:start position:0% developer 00:07:23.460 --> 00:07:26.029 align:start position:0% developer um<00:07:23.520> it<00:07:24.479> seems<00:07:24.780> to<00:07:24.900> me<00:07:25.080> like<00:07:25.259> a<00:07:25.500> nice<00:07:25.680> to<00:07:25.860> have 00:07:26.029 --> 00:07:26.039 align:start position:0% um it seems to me like a nice to have 00:07:26.039 --> 00:07:29.870 align:start position:0% um it seems to me like a nice to have but<00:07:26.460> nothing<00:07:26.880> that's<00:07:27.720> critical<00:07:28.199> for<00:07:28.919> for<00:07:29.580> us 00:07:29.870 --> 00:07:29.880 align:start position:0% but nothing that's critical for for us 00:07:29.880 --> 00:07:31.550 align:start position:0% but nothing that's critical for for us right<00:07:30.240> now 00:07:31.550 --> 00:07:31.560 align:start position:0% right now 00:07:31.560 --> 00:07:34.490 align:start position:0% right now so<00:07:31.979> I<00:07:32.160> can<00:07:32.280> read<00:07:32.400> about<00:07:32.580> that<00:07:32.880> one<00:07:33.720> of<00:07:33.840> the<00:07:34.080> one 00:07:34.490 --> 00:07:34.500 align:start position:0% so I can read about that one of the one 00:07:34.500 --> 00:07:36.050 align:start position:0% so I can read about that one of the one of<00:07:34.620> the<00:07:34.680> points<00:07:34.979> that<00:07:35.039> I<00:07:35.220> do<00:07:35.280> like<00:07:35.460> about<00:07:35.639> it<00:07:35.880> is 00:07:36.050 --> 00:07:36.060 align:start position:0% of the points that I do like about it is 00:07:36.060 --> 00:07:37.909 align:start position:0% of the points that I do like about it is that<00:07:36.300> with<00:07:36.539> the<00:07:36.780> with<00:07:37.139> these<00:07:37.319> mutexes 00:07:37.909 --> 00:07:37.919 align:start position:0% that with the with these mutexes 00:07:37.919 --> 00:07:40.370 align:start position:0% that with the with these mutexes essentially<00:07:38.460> it<00:07:39.000> touches<00:07:39.360> the<00:07:39.479> state<00:07:39.720> and 00:07:40.370 --> 00:07:40.380 align:start position:0% essentially it touches the state and 00:07:40.380 --> 00:07:42.050 align:start position:0% essentially it touches the state and even<00:07:40.500> if<00:07:40.740> it<00:07:40.860> does<00:07:40.979> nothing<00:07:41.220> just<00:07:41.580> flip<00:07:41.940> some 00:07:42.050 --> 00:07:42.060 align:start position:0% even if it does nothing just flip some 00:07:42.060 --> 00:07:43.790 align:start position:0% even if it does nothing just flip some bits<00:07:42.419> back<00:07:42.539> and<00:07:42.660> forth<00:07:42.960> it<00:07:43.380> still<00:07:43.500> has<00:07:43.680> to 00:07:43.790 --> 00:07:43.800 align:start position:0% bits back and forth it still has to 00:07:43.800 --> 00:07:46.370 align:start position:0% bits back and forth it still has to touch<00:07:43.979> disk<00:07:44.400> and<00:07:44.819> this<00:07:45.000> would<00:07:45.240> allow<00:07:45.539> us<00:07:45.660> to<00:07:46.020> do 00:07:46.370 --> 00:07:46.380 align:start position:0% touch disk and this would allow us to do 00:07:46.380 --> 00:07:48.589 align:start position:0% touch disk and this would allow us to do these<00:07:46.740> things<00:07:46.860> without<00:07:47.099> touching<00:07:47.580> this<00:07:48.180> so 00:07:48.589 --> 00:07:48.599 align:start position:0% these things without touching this so 00:07:48.599 --> 00:07:50.510 align:start position:0% these things without touching this so that's<00:07:48.840> a<00:07:49.080> net<00:07:49.319> benefit<00:07:49.500> for<00:07:49.860> me 00:07:50.510 --> 00:07:50.520 align:start position:0% that's a net benefit for me 00:07:50.520 --> 00:07:54.890 align:start position:0% that's a net benefit for me have<00:07:50.880> you<00:07:51.000> talked<00:07:51.180> to<00:07:51.240> the<00:07:51.360> solidity<00:07:51.780> team<00:07:51.960> yet 00:07:54.890 --> 00:07:54.900 align:start position:0% 00:07:54.900 --> 00:07:58.490 align:start position:0% there<00:07:55.560> is<00:07:55.919> an<00:07:56.220> open<00:07:56.460> draft<00:07:57.120> PR<00:07:57.599> with<00:07:58.319> the 00:07:58.490 --> 00:07:58.500 align:start position:0% there is an open draft PR with the 00:07:58.500 --> 00:08:00.650 align:start position:0% there is an open draft PR with the assembly<00:07:58.860> op<00:07:59.099> code<00:07:59.340> in<00:07:59.759> the<00:07:59.880> solidity<00:08:00.240> repo 00:08:00.650 --> 00:08:00.660 align:start position:0% assembly op code in the solidity repo 00:08:00.660 --> 00:08:01.730 align:start position:0% assembly op code in the solidity repo right<00:08:00.840> now 00:08:01.730 --> 00:08:01.740 align:start position:0% right now 00:08:01.740 --> 00:08:08.150 align:start position:0% right now um<00:08:02.280> yeah 00:08:08.150 --> 00:08:08.160 align:start position:0% 00:08:08.160 --> 00:08:10.189 align:start position:0% I<00:08:08.639> see<00:08:08.880> like<00:08:09.060> it's<00:08:09.180> really<00:08:09.419> parallelization 00:08:10.189 --> 00:08:10.199 align:start position:0% I see like it's really parallelization 00:08:10.199 --> 00:08:12.290 align:start position:0% I see like it's really parallelization that<00:08:10.620> has<00:08:10.860> been<00:08:11.099> quite<00:08:11.460> a<00:08:11.699> lot<00:08:11.819> of<00:08:11.940> work<00:08:12.060> in 00:08:12.290 --> 00:08:12.300 align:start position:0% that has been quite a lot of work in 00:08:12.300 --> 00:08:14.930 align:start position:0% that has been quite a lot of work in analyzing<00:08:12.840> how<00:08:13.139> much<00:08:13.680> the<00:08:13.979> transaction<00:08:14.580> can 00:08:14.930 --> 00:08:14.940 align:start position:0% analyzing how much the transaction can 00:08:14.940 --> 00:08:17.450 align:start position:0% analyzing how much the transaction can be<00:08:15.060> paralyzed<00:08:15.660> and<00:08:15.900> even<00:08:16.560> at<00:08:16.800> flashbots<00:08:17.340> we 00:08:17.450 --> 00:08:17.460 align:start position:0% be paralyzed and even at flashbots we 00:08:17.460 --> 00:08:19.969 align:start position:0% be paralyzed and even at flashbots we were<00:08:17.580> running<00:08:17.759> the<00:08:18.180> analysis<00:08:18.840> of<00:08:19.080> the 00:08:19.969 --> 00:08:19.979 align:start position:0% were running the analysis of the 00:08:19.979 --> 00:08:22.430 align:start position:0% were running the analysis of the of<00:08:20.220> the<00:08:20.460> clashes<00:08:20.879> the<00:08:21.240> bundle<00:08:21.780> clashes<00:08:22.259> the 00:08:22.430 --> 00:08:22.440 align:start position:0% of the clashes the bundle clashes the 00:08:22.440 --> 00:08:25.610 align:start position:0% of the clashes the bundle clashes the transaction<00:08:22.740> clashes<00:08:23.400> so<00:08:23.639> something<00:08:24.539> uh<00:08:25.259> any 00:08:25.610 --> 00:08:25.620 align:start position:0% transaction clashes so something uh any 00:08:25.620 --> 00:08:27.650 align:start position:0% transaction clashes so something uh any improvements<00:08:26.099> in<00:08:26.220> this<00:08:26.460> would<00:08:26.940> would<00:08:27.479> be 00:08:27.650 --> 00:08:27.660 align:start position:0% improvements in this would would be 00:08:27.660 --> 00:08:29.749 align:start position:0% improvements in this would would be quite<00:08:27.840> nice<00:08:28.080> to<00:08:28.379> see<00:08:28.620> there<00:08:29.460> are<00:08:29.639> some 00:08:29.749 --> 00:08:29.759 align:start position:0% quite nice to see there are some 00:08:29.759 --> 00:08:31.969 align:start position:0% quite nice to see there are some Builders<00:08:30.120> there<00:08:30.360> like<00:08:30.960> I've<00:08:31.440> seen<00:08:31.680> actually 00:08:31.969 --> 00:08:31.979 align:start position:0% Builders there like I've seen actually 00:08:31.979 --> 00:08:34.190 align:start position:0% Builders there like I've seen actually the<00:08:32.520> the<00:08:32.640> modifications<00:08:33.240> to<00:08:33.599> get<00:08:33.779> that<00:08:34.020> were 00:08:34.190 --> 00:08:34.200 align:start position:0% the the modifications to get that were 00:08:34.200 --> 00:08:35.930 align:start position:0% the the modifications to get that were introducing<00:08:34.680> parallelization<00:08:35.399> and<00:08:35.820> they 00:08:35.930 --> 00:08:35.940 align:start position:0% introducing parallelization and they 00:08:35.940 --> 00:08:37.550 align:start position:0% introducing parallelization and they were<00:08:36.120> working<00:08:36.300> and<00:08:36.599> I<00:08:36.779> was<00:08:36.959> really<00:08:37.080> surprised 00:08:37.550 --> 00:08:37.560 align:start position:0% were working and I was really surprised 00:08:37.560 --> 00:08:39.529 align:start position:0% were working and I was really surprised like<00:08:37.680> how<00:08:37.919> some<00:08:38.099> developers<00:08:38.520> were<00:08:38.700> able<00:08:38.940> to<00:08:39.180> to 00:08:39.529 --> 00:08:39.539 align:start position:0% like how some developers were able to to 00:08:39.539 --> 00:08:42.290 align:start position:0% like how some developers were able to to do<00:08:39.779> that<00:08:39.959> in<00:08:40.200> their<00:08:40.380> own<00:08:41.000> in<00:08:42.000> their<00:08:42.180> own 00:08:42.290 --> 00:08:42.300 align:start position:0% do that in their own in their own 00:08:42.300 --> 00:08:43.850 align:start position:0% do that in their own in their own implementations<00:08:42.839> just<00:08:43.140> for<00:08:43.320> the<00:08:43.440> simulation 00:08:43.850 --> 00:08:43.860 align:start position:0% implementations just for the simulation 00:08:43.860 --> 00:08:45.370 align:start position:0% implementations just for the simulation efficiency 00:08:45.370 --> 00:08:45.380 align:start position:0% efficiency 00:08:45.380 --> 00:08:48.769 align:start position:0% efficiency uh<00:08:46.380> consider<00:08:47.060> already<00:08:48.060> gains<00:08:48.600> from 00:08:48.769 --> 00:08:48.779 align:start position:0% uh consider already gains from 00:08:48.779 --> 00:08:50.750 align:start position:0% uh consider already gains from paralyzing<00:08:49.380> transactions<00:08:49.980> such<00:08:50.220> as<00:08:50.399> the<00:08:50.580> the 00:08:50.750 --> 00:08:50.760 align:start position:0% paralyzing transactions such as the the 00:08:50.760 --> 00:08:52.550 align:start position:0% paralyzing transactions such as the the implementations<00:08:51.300> are<00:08:51.600> so<00:08:51.899> complex<00:08:52.140> and<00:08:52.320> so 00:08:52.550 --> 00:08:52.560 align:start position:0% implementations are so complex and so 00:08:52.560 --> 00:08:55.490 align:start position:0% implementations are so complex and so specific<00:08:52.920> for<00:08:53.279> for<00:08:53.519> searching<00:08:54.120> uh<00:08:54.899> that<00:08:55.200> they 00:08:55.490 --> 00:08:55.500 align:start position:0% specific for for searching uh that they 00:08:55.500 --> 00:08:58.250 align:start position:0% specific for for searching uh that they are<00:08:55.620> not<00:08:55.740> coming<00:08:55.980> to<00:08:56.399> the<00:08:56.700> journal<00:08:57.480> View 00:08:58.250 --> 00:08:58.260 align:start position:0% are not coming to the journal View 00:08:58.260 --> 00:09:01.370 align:start position:0% are not coming to the journal View uh<00:08:58.920> so<00:08:59.040> it'd<00:08:59.220> be<00:08:59.339> great<00:08:59.519> to<00:08:59.640> see<00:08:59.760> that<00:09:00.080> uh<00:09:01.080> I 00:09:01.370 --> 00:09:01.380 align:start position:0% uh so it'd be great to see that uh I 00:09:01.380 --> 00:09:03.530 align:start position:0% uh so it'd be great to see that uh I think<00:09:01.500> the<00:09:01.680> pitch<00:09:01.980> was<00:09:02.220> really<00:09:02.519> great 00:09:03.530 --> 00:09:03.540 align:start position:0% think the pitch was really great 00:09:03.540 --> 00:09:06.110 align:start position:0% think the pitch was really great so<00:09:04.140> I<00:09:04.620> I<00:09:04.680> was<00:09:04.980> not<00:09:05.160> considering<00:09:05.580> this<00:09:05.880> one 00:09:06.110 --> 00:09:06.120 align:start position:0% so I I was not considering this one 00:09:06.120 --> 00:09:07.910 align:start position:0% so I I was not considering this one because<00:09:06.720> I<00:09:07.080> was<00:09:07.200> always<00:09:07.380> thinking<00:09:07.740> that 00:09:07.910 --> 00:09:07.920 align:start position:0% because I was always thinking that 00:09:07.920 --> 00:09:09.530 align:start position:0% because I was always thinking that anything<00:09:08.160> that<00:09:08.459> was<00:09:08.640> touching<00:09:09.120> the<00:09:09.300> storage 00:09:09.530 --> 00:09:09.540 align:start position:0% anything that was touching the storage 00:09:09.540 --> 00:09:12.710 align:start position:0% anything that was touching the storage was<00:09:10.260> awful<00:09:10.800> amount<00:09:11.100> of<00:09:11.220> testing<00:09:11.760> and<00:09:12.300> huge 00:09:12.710 --> 00:09:12.720 align:start position:0% was awful amount of testing and huge 00:09:12.720 --> 00:09:15.769 align:start position:0% was awful amount of testing and huge risk<00:09:13.019> of<00:09:13.260> of<00:09:13.740> something<00:09:14.100> escaping<00:09:14.820> and<00:09:15.480> and 00:09:15.769 --> 00:09:15.779 align:start position:0% risk of of something escaping and and 00:09:15.779 --> 00:09:18.470 align:start position:0% risk of of something escaping and and some<00:09:16.140> contract<00:09:16.620> breakages<00:09:17.100> so<00:09:17.519> so<00:09:17.700> this<00:09:17.940> is<00:09:18.180> my 00:09:18.470 --> 00:09:18.480 align:start position:0% some contract breakages so so this is my 00:09:18.480 --> 00:09:20.870 align:start position:0% some contract breakages so so this is my biggest<00:09:18.600> worry<00:09:19.500> like<00:09:19.860> we<00:09:20.040> were<00:09:20.160> modifying<00:09:20.700> the 00:09:20.870 --> 00:09:20.880 align:start position:0% biggest worry like we were modifying the 00:09:20.880 --> 00:09:22.870 align:start position:0% biggest worry like we were modifying the cost<00:09:21.060> of<00:09:21.360> storage<00:09:21.600> in<00:09:21.959> the<00:09:22.080> past<00:09:22.200> we're 00:09:22.870 --> 00:09:22.880 align:start position:0% cost of storage in the past we're 00:09:22.880 --> 00:09:26.389 align:start position:0% cost of storage in the past we're modifying<00:09:23.880> the<00:09:23.940> behavior<00:09:24.420> of<00:09:24.720> refunds 00:09:26.389 --> 00:09:26.399 align:start position:0% modifying the behavior of refunds 00:09:26.399 --> 00:09:28.310 align:start position:0% modifying the behavior of refunds um<00:09:26.459> and<00:09:26.880> this<00:09:27.300> one<00:09:27.420> feels<00:09:27.839> a<00:09:27.899> bit<00:09:28.019> like<00:09:28.200> that 00:09:28.310 --> 00:09:28.320 align:start position:0% um and this one feels a bit like that 00:09:28.320 --> 00:09:30.829 align:start position:0% um and this one feels a bit like that like<00:09:28.500> when<00:09:28.740> you<00:09:28.920> say<00:09:29.040> oh<00:09:29.760> it's<00:09:30.060> uh<00:09:30.300> it's<00:09:30.660> a 00:09:30.829 --> 00:09:30.839 align:start position:0% like when you say oh it's uh it's a 00:09:30.839 --> 00:09:34.490 align:start position:0% like when you say oh it's uh it's a known<00:09:31.140> cost<00:09:31.740> but<00:09:32.459> do<00:09:32.880> we<00:09:33.060> do<00:09:33.420> we<00:09:33.600> cup<00:09:33.839> the<00:09:34.200> the 00:09:34.490 --> 00:09:34.500 align:start position:0% known cost but do we do we cup the the 00:09:34.500 --> 00:09:37.490 align:start position:0% known cost but do we do we cup the the storage<00:09:34.800> okay<00:09:35.399> I<00:09:35.640> see<00:09:35.880> yeah<00:09:36.540> refunds<00:09:37.440> are 00:09:37.490 --> 00:09:37.500 align:start position:0% storage okay I see yeah refunds are 00:09:37.500 --> 00:09:38.949 align:start position:0% storage okay I see yeah refunds are capped 00:09:38.949 --> 00:09:38.959 align:start position:0% capped 00:09:38.959 --> 00:09:41.269 align:start position:0% capped nowaday<00:09:39.959> they<00:09:40.260> started<00:09:40.500> transition<00:09:40.920> storage 00:09:41.269 --> 00:09:41.279 align:start position:0% nowaday they started transition storage 00:09:41.279 --> 00:09:43.250 align:start position:0% nowaday they started transition storage because<00:09:41.640> if<00:09:41.880> it's<00:09:42.120> not<00:09:42.240> capped<00:09:42.660> it<00:09:42.779> again<00:09:43.019> it 00:09:43.250 --> 00:09:43.260 align:start position:0% because if it's not capped it again it 00:09:43.260 --> 00:09:45.650 align:start position:0% because if it's not capped it again it should<00:09:43.380> be<00:09:43.560> exponentially<00:09:44.100> growing<00:09:44.580> and<00:09:44.820> it's 00:09:45.650 --> 00:09:45.660 align:start position:0% should be exponentially growing and it's 00:09:45.660 --> 00:09:47.509 align:start position:0% should be exponentially growing and it's it's<00:09:45.720> the<00:09:46.320> same<00:09:46.440> it<00:09:46.740> doesn't<00:09:46.860> exponentially 00:09:47.509 --> 00:09:47.519 align:start position:0% it's the same it doesn't exponentially 00:09:47.519 --> 00:09:50.269 align:start position:0% it's the same it doesn't exponentially grow<00:09:47.760> but<00:09:48.300> we<00:09:48.600> looked<00:09:48.899> at<00:09:49.019> it<00:09:49.200> to<00:09:49.620> see<00:09:49.800> kind<00:09:50.220> of 00:09:50.269 --> 00:09:50.279 align:start position:0% grow but we looked at it to see kind of 00:09:50.279 --> 00:09:52.070 align:start position:0% grow but we looked at it to see kind of you<00:09:50.580> know<00:09:50.640> the<00:09:50.820> upper<00:09:51.120> bound<00:09:51.240> and<00:09:51.660> it<00:09:51.779> seemed 00:09:52.070 --> 00:09:52.080 align:start position:0% you know the upper bound and it seemed 00:09:52.080 --> 00:10:01.190 align:start position:0% you know the upper bound and it seemed like<00:09:52.140> it<00:09:52.320> was<00:09:52.440> safe 00:10:01.190 --> 00:10:01.200 align:start position:0% 00:10:01.200 --> 00:10:04.070 align:start position:0% but<00:10:01.620> it's<00:10:01.800> the<00:10:01.920> same<00:10:02.100> with<00:10:02.279> memory<00:10:02.760> right 00:10:04.070 --> 00:10:04.080 align:start position:0% but it's the same with memory right 00:10:04.080 --> 00:10:06.230 align:start position:0% but it's the same with memory right yeah<00:10:04.140> so<00:10:04.800> with<00:10:05.160> memory<00:10:05.519> we<00:10:05.760> have<00:10:05.940> the 00:10:06.230 --> 00:10:06.240 align:start position:0% yeah so with memory we have the 00:10:06.240 --> 00:10:08.690 align:start position:0% yeah so with memory we have the exponential<00:10:07.200> cost<00:10:07.740> and<00:10:08.040> here<00:10:08.279> we<00:10:08.399> have<00:10:08.580> the 00:10:08.690 --> 00:10:08.700 align:start position:0% exponential cost and here we have the 00:10:08.700 --> 00:10:10.610 align:start position:0% exponential cost and here we have the linear<00:10:09.000> one<00:10:09.180> yeah 00:10:10.610 --> 00:10:10.620 align:start position:0% linear one yeah 00:10:10.620 --> 00:10:13.550 align:start position:0% linear one yeah so<00:10:11.040> I<00:10:11.160> guess<00:10:11.279> just<00:10:11.459> to<00:10:11.580> wrap<00:10:11.760> it<00:10:11.940> up<00:10:12.060> sorry<00:10:12.560> but 00:10:13.550 --> 00:10:13.560 align:start position:0% so I guess just to wrap it up sorry but 00:10:13.560 --> 00:10:15.829 align:start position:0% so I guess just to wrap it up sorry but like<00:10:13.680> is<00:10:13.860> there<00:10:14.100> something<00:10:14.339> that<00:10:14.700> any<00:10:15.240> like<00:10:15.660> we 00:10:15.829 --> 00:10:15.839 align:start position:0% like is there something that any like we 00:10:15.839 --> 00:10:17.570 align:start position:0% like is there something that any like we have<00:10:16.019> tests<00:10:16.380> for<00:10:16.440> this<00:10:16.620> we<00:10:16.800> have 00:10:17.570 --> 00:10:17.580 align:start position:0% have tests for this we have 00:10:17.580 --> 00:10:19.490 align:start position:0% have tests for this we have patience 00:10:19.490 --> 00:10:19.500 align:start position:0% patience 00:10:19.500 --> 00:10:21.290 align:start position:0% patience I<00:10:19.860> guess<00:10:19.980> my<00:10:20.160> question<00:10:20.399> is<00:10:20.580> like<00:10:20.820> from<00:10:21.120> the 00:10:21.290 --> 00:10:21.300 align:start position:0% I guess my question is like from the 00:10:21.300 --> 00:10:22.430 align:start position:0% I guess my question is like from the client<00:10:21.540> teams<00:10:21.779> very<00:10:21.899> quickly<00:10:22.140> is<00:10:22.260> there 00:10:22.430 --> 00:10:22.440 align:start position:0% client teams very quickly is there 00:10:22.440 --> 00:10:23.930 align:start position:0% client teams very quickly is there something<00:10:22.560> like<00:10:22.860> you<00:10:23.160> want<00:10:23.339> to<00:10:23.519> see<00:10:23.640> from<00:10:23.820> here 00:10:23.930 --> 00:10:23.940 align:start position:0% something like you want to see from here 00:10:23.940 --> 00:10:25.430 align:start position:0% something like you want to see from here like<00:10:24.120> a<00:10:24.300> big<00:10:24.360> open<00:10:24.540> question<00:10:24.899> you<00:10:25.140> have<00:10:25.260> about 00:10:25.430 --> 00:10:25.440 align:start position:0% like a big open question you have about 00:10:25.440 --> 00:10:26.750 align:start position:0% like a big open question you have about this<00:10:25.620> Daniel<00:10:25.920> you<00:10:26.160> have<00:10:26.279> the<00:10:26.399> solidity 00:10:26.750 --> 00:10:26.760 align:start position:0% this Daniel you have the solidity 00:10:26.760 --> 00:10:28.970 align:start position:0% this Daniel you have the solidity question<00:10:27.120> but<00:10:27.420> like<00:10:27.660> yeah<00:10:28.320> just<00:10:28.560> to<00:10:28.680> wrap<00:10:28.920> it 00:10:28.970 --> 00:10:28.980 align:start position:0% question but like yeah just to wrap it 00:10:28.980 --> 00:10:30.530 align:start position:0% question but like yeah just to wrap it up<00:10:29.160> anything 00:10:30.530 --> 00:10:30.540 align:start position:0% up anything 00:10:30.540 --> 00:10:32.090 align:start position:0% up anything you<00:10:31.019> wish<00:10:31.140> you<00:10:31.260> would<00:10:31.440> see<00:10:31.620> from<00:10:31.800> this<00:10:31.920> that 00:10:32.090 --> 00:10:32.100 align:start position:0% you wish you would see from this that 00:10:32.100 --> 00:10:34.610 align:start position:0% you wish you would see from this that would<00:10:32.220> help<00:10:32.399> you<00:10:32.580> better<00:10:33.120> understand 00:10:34.610 --> 00:10:34.620 align:start position:0% would help you better understand 00:10:34.620 --> 00:10:37.490 align:start position:0% would help you better understand do<00:10:35.399> you<00:10:35.519> have<00:10:35.700> uh<00:10:36.060> tests<00:10:36.660> or<00:10:36.779> benchmarks<00:10:37.320> for 00:10:37.490 --> 00:10:37.500 align:start position:0% do you have uh tests or benchmarks for 00:10:37.500 --> 00:10:38.449 align:start position:0% do you have uh tests or benchmarks for like 00:10:38.449 --> 00:10:38.459 align:start position:0% like 00:10:38.459 --> 00:10:40.970 align:start position:0% like just<00:10:39.000> writing<00:10:39.360> as<00:10:39.480> much<00:10:39.660> uh<00:10:40.260> to<00:10:40.620> the<00:10:40.800> storage 00:10:40.970 --> 00:10:40.980 align:start position:0% just writing as much uh to the storage 00:10:40.980 --> 00:10:45.530 align:start position:0% just writing as much uh to the storage as<00:10:41.279> possible<00:10:41.700> writing<00:10:42.540> in<00:10:43.019> uh<00:10:43.760> in<00:10:44.760> like<00:10:45.300> small 00:10:45.530 --> 00:10:45.540 align:start position:0% as possible writing in uh in like small 00:10:45.540 --> 00:10:49.009 align:start position:0% as possible writing in uh in like small chunks<00:10:46.019> into<00:10:46.140> it<00:10:46.380> doing<00:10:47.100> uh<00:10:47.700> doing<00:10:48.480> separate 00:10:49.009 --> 00:10:49.019 align:start position:0% chunks into it doing uh doing separate 00:10:49.019 --> 00:10:51.350 align:start position:0% chunks into it doing uh doing separate calls<00:10:49.440> into<00:10:49.860> different 00:10:51.350 --> 00:10:51.360 align:start position:0% calls into different 00:10:51.360 --> 00:10:53.030 align:start position:0% calls into different um<00:10:51.420> different<00:10:51.779> contracts<00:10:52.320> that<00:10:52.560> each<00:10:52.740> write 00:10:53.030 --> 00:10:53.040 align:start position:0% um different contracts that each write 00:10:53.040 --> 00:10:55.490 align:start position:0% um different contracts that each write their<00:10:53.519> own<00:10:53.700> I<00:10:54.660> would<00:10:54.779> really<00:10:54.959> like<00:10:55.200> to<00:10:55.380> see 00:10:55.490 --> 00:10:55.500 align:start position:0% their own I would really like to see 00:10:55.500 --> 00:10:57.170 align:start position:0% their own I would really like to see this 00:10:57.170 --> 00:10:57.180 align:start position:0% this 00:10:57.180 --> 00:10:59.870 align:start position:0% this yeah<00:10:57.959> there's<00:10:58.260> an<00:10:58.500> open<00:10:58.680> PR<00:10:58.980> in<00:10:59.339> the<00:10:59.459> ethereum 00:10:59.870 --> 00:10:59.880 align:start position:0% yeah there's an open PR in the ethereum 00:10:59.880 --> 00:11:02.269 align:start position:0% yeah there's an open PR in the ethereum test<00:11:00.060> repo<00:11:00.600> I<00:11:01.019> think<00:11:01.140> most<00:11:01.680> of<00:11:01.860> those<00:11:01.980> cases 00:11:02.269 --> 00:11:02.279 align:start position:0% test repo I think most of those cases 00:11:02.279 --> 00:11:03.590 align:start position:0% test repo I think most of those cases that<00:11:02.459> you<00:11:02.579> just<00:11:02.700> said<00:11:02.820> are<00:11:03.000> covered<00:11:03.240> I<00:11:03.420> haven't 00:11:03.590 --> 00:11:03.600 align:start position:0% that you just said are covered I haven't 00:11:03.600 --> 00:11:06.230 align:start position:0% that you just said are covered I haven't looked<00:11:04.260> in<00:11:04.560> a<00:11:04.740> bit<00:11:04.800> but<00:11:05.640> um 00:11:06.230 --> 00:11:06.240 align:start position:0% looked in a bit but um 00:11:06.240 --> 00:11:09.350 align:start position:0% looked in a bit but um yes<00:11:06.720> re-entrancy<00:11:07.620> I<00:11:07.920> think<00:11:07.980> is<00:11:08.160> covered 00:11:09.350 --> 00:11:09.360 align:start position:0% yes re-entrancy I think is covered 00:11:09.360 --> 00:11:11.810 align:start position:0% yes re-entrancy I think is covered um<00:11:09.420> I'm<00:11:09.899> happy<00:11:10.260> to<00:11:10.440> share<00:11:10.680> that<00:11:10.920> out<00:11:11.100> with<00:11:11.640> with 00:11:11.810 --> 00:11:11.820 align:start position:0% um I'm happy to share that out with with 00:11:11.820 --> 00:11:13.790 align:start position:0% um I'm happy to share that out with with the<00:11:12.000> wider<00:11:12.360> group<00:11:12.480> but<00:11:12.839> there's<00:11:13.140> extensive 00:11:13.790 --> 00:11:13.800 align:start position:0% the wider group but there's extensive 00:11:13.800 --> 00:11:16.490 align:start position:0% the wider group but there's extensive tests 00:11:16.490 --> 00:11:16.500 align:start position:0% 00:11:16.500 --> 00:11:18.290 align:start position:0% something<00:11:16.920> that<00:11:17.160> I<00:11:17.279> did<00:11:17.399> want<00:11:17.579> to<00:11:17.700> do<00:11:17.820> is<00:11:18.060> use 00:11:18.290 --> 00:11:18.300 align:start position:0% something that I did want to do is use 00:11:18.300 --> 00:11:20.810 align:start position:0% something that I did want to do is use Felix's<00:11:18.899> mem<00:11:19.140> size<00:11:19.380> library<00:11:19.800> and<00:11:20.519> basically 00:11:20.810 --> 00:11:20.820 align:start position:0% Felix's mem size library and basically 00:11:20.820 --> 00:11:22.490 align:start position:0% Felix's mem size library and basically just<00:11:21.000> like<00:11:21.180> look<00:11:21.420> at<00:11:21.540> the<00:11:21.660> gas<00:11:21.839> limit<00:11:22.019> and<00:11:22.320> just 00:11:22.490 --> 00:11:22.500 align:start position:0% just like look at the gas limit and just 00:11:22.500 --> 00:11:24.170 align:start position:0% just like look at the gas limit and just like<00:11:22.620> you<00:11:22.800> know<00:11:22.920> fill<00:11:23.220> in<00:11:23.399> as<00:11:23.579> many<00:11:23.760> things<00:11:23.940> as 00:11:24.170 --> 00:11:24.180 align:start position:0% like you know fill in as many things as 00:11:24.180 --> 00:11:25.790 align:start position:0% like you know fill in as many things as possible<00:11:24.480> that<00:11:25.019> would<00:11:25.140> fit<00:11:25.260> in<00:11:25.380> the<00:11:25.500> gas<00:11:25.620> limit 00:11:25.790 --> 00:11:25.800 align:start position:0% possible that would fit in the gas limit 00:11:25.800 --> 00:11:28.790 align:start position:0% possible that would fit in the gas limit and<00:11:26.040> then<00:11:26.160> like<00:11:26.339> observe<00:11:26.880> the<00:11:27.060> size<00:11:27.620> in<00:11:28.620> the 00:11:28.790 --> 00:11:28.800 align:start position:0% and then like observe the size in the 00:11:28.800 --> 00:11:31.069 align:start position:0% and then like observe the size in the implementation<00:11:29.279> itself 00:11:31.069 --> 00:11:31.079 align:start position:0% implementation itself 00:11:31.079 --> 00:11:33.829 align:start position:0% implementation itself um I<00:11:31.800> have<00:11:31.920> that<00:11:32.220> like<00:11:32.519> on<00:11:32.880> my<00:11:33.120> like<00:11:33.600> computer 00:11:33.829 --> 00:11:33.839 align:start position:0% um I have that like on my like computer 00:11:33.839 --> 00:11:35.690 align:start position:0% um I have that like on my like computer someplace<00:11:34.380> but<00:11:34.740> it's<00:11:34.920> like<00:11:35.160> not<00:11:35.459> really 00:11:35.690 --> 00:11:35.700 align:start position:0% someplace but it's like not really 00:11:35.700 --> 00:11:37.190 align:start position:0% someplace but it's like not really pushed<00:11:36.120> but<00:11:36.420> that<00:11:36.540> is<00:11:36.720> like<00:11:36.839> something<00:11:37.019> that 00:11:37.190 --> 00:11:37.200 align:start position:0% pushed but that is like something that 00:11:37.200 --> 00:11:40.970 align:start position:0% pushed but that is like something that we<00:11:37.320> could<00:11:37.440> add<00:11:37.920> add<00:11:38.640> to<00:11:38.880> make<00:11:39.000> it<00:11:39.120> better 00:11:40.970 --> 00:11:40.980 align:start position:0% we could add add to make it better 00:11:40.980 --> 00:11:43.310 align:start position:0% we could add add to make it better wrap<00:11:41.399> this<00:11:41.579> up<00:11:41.700> to<00:11:41.880> the<00:11:42.000> next<00:11:42.060> one<00:11:42.180> oh<00:11:42.959> one<00:11:43.200> last 00:11:43.310 --> 00:11:43.320 align:start position:0% wrap this up to the next one oh one last 00:11:43.320 --> 00:11:44.870 align:start position:0% wrap this up to the next one oh one last question<00:11:43.560> okay<00:11:43.800> I<00:11:44.100> just<00:11:44.279> had<00:11:44.459> a<00:11:44.579> comment<00:11:44.760> on 00:11:44.870 --> 00:11:44.880 align:start position:0% question okay I just had a comment on 00:11:44.880 --> 00:11:46.490 align:start position:0% question okay I just had a comment on this<00:11:45.060> already<00:11:45.240> depart 00:11:46.490 --> 00:11:46.500 align:start position:0% this already depart 00:11:46.500 --> 00:11:48.470 align:start position:0% this already depart um<00:11:46.560> adding<00:11:46.920> it<00:11:47.040> to<00:11:47.160> the<00:11:47.279> assembly<00:11:47.640> well<00:11:48.120> the<00:11:48.360> pr 00:11:48.470 --> 00:11:48.480 align:start position:0% um adding it to the assembly well the pr 00:11:48.480 --> 00:11:51.530 align:start position:0% um adding it to the assembly well the pr there<00:11:49.140> wasn't<00:11:49.260> a<00:11:49.440> PR<00:11:49.560> we<00:11:49.860> just<00:11:49.980> edited<00:11:50.339> it<00:11:50.459> but 00:11:51.530 --> 00:11:51.540 align:start position:0% there wasn't a PR we just edited it but 00:11:51.540 --> 00:11:53.569 align:start position:0% there wasn't a PR we just edited it but um it's<00:11:52.320> easy<00:11:52.500> to<00:11:52.620> add<00:11:52.740> the<00:11:52.920> op<00:11:53.040> code<00:11:53.220> and<00:11:53.459> you 00:11:53.569 --> 00:11:53.579 align:start position:0% um it's easy to add the op code and you 00:11:53.579 --> 00:11:55.970 align:start position:0% um it's easy to add the op code and you can<00:11:53.640> use<00:11:53.760> it<00:11:53.940> in<00:11:54.060> an<00:11:54.180> inline<00:11:54.540> assembly 00:11:55.970 --> 00:11:55.980 align:start position:0% can use it in an inline assembly 00:11:55.980 --> 00:11:57.710 align:start position:0% can use it in an inline assembly um<00:11:56.040> and<00:11:56.279> if<00:11:56.399> the<00:11:56.579> AIP<00:11:56.820> goes<00:11:57.180> live<00:11:57.300> that's<00:11:57.540> going 00:11:57.710 --> 00:11:57.720 align:start position:0% um and if the AIP goes live that's going 00:11:57.720 --> 00:11:59.750 align:start position:0% um and if the AIP goes live that's going to<00:11:57.779> be<00:11:57.839> added<00:11:58.079> like<00:11:58.260> instantly<00:11:58.680> but<00:11:59.279> adding<00:11:59.640> it 00:11:59.750 --> 00:11:59.760 align:start position:0% to be added like instantly but adding it 00:11:59.760 --> 00:12:01.250 align:start position:0% to be added like instantly but adding it into<00:11:59.940> language<00:12:00.300> is<00:12:00.600> going<00:12:00.720> to<00:12:00.839> take<00:12:00.959> quite<00:12:01.200> a 00:12:01.250 --> 00:12:01.260 align:start position:0% into language is going to take quite a 00:12:01.260 --> 00:12:03.769 align:start position:0% into language is going to take quite a bit<00:12:01.380> because<00:12:01.560> it's<00:12:01.860> a<00:12:02.040> lot<00:12:02.160> of<00:12:02.279> changes 00:12:03.769 --> 00:12:03.779 align:start position:0% bit because it's a lot of changes 00:12:03.779 --> 00:12:05.329 align:start position:0% bit because it's a lot of changes um I<00:12:04.079> don't<00:12:04.200> expect<00:12:04.440> it<00:12:04.800> to<00:12:04.980> to<00:12:05.160> happen 00:12:05.329 --> 00:12:05.339 align:start position:0% um I don't expect it to to happen 00:12:05.339 --> 00:12:07.069 align:start position:0% um I don't expect it to to happen anytime<00:12:05.820> soon 00:12:07.069 --> 00:12:07.079 align:start position:0% anytime soon 00:12:07.079 --> 00:12:08.870 align:start position:0% anytime soon um so<00:12:07.260> if<00:12:07.500> you<00:12:07.620> guys<00:12:07.740> want<00:12:08.279> the<00:12:08.459> help<00:12:08.700> in 00:12:08.870 --> 00:12:08.880 align:start position:0% um so if you guys want the help in 00:12:08.880 --> 00:12:11.389 align:start position:0% um so if you guys want the help in implementing<00:12:09.360> it<00:12:09.540> which<00:12:09.959> may<00:12:10.200> take<00:12:10.440> like<00:12:10.740> 1000 00:12:11.389 --> 00:12:11.399 align:start position:0% implementing it which may take like 1000 00:12:11.399 --> 00:12:13.130 align:start position:0% implementing it which may take like 1000 signs<00:12:11.760> of<00:12:11.880> code 00:12:13.130 --> 00:12:13.140 align:start position:0% signs of code 00:12:13.140 --> 00:12:14.990 align:start position:0% signs of code um<00:12:13.260> that<00:12:13.440> would<00:12:13.560> be<00:12:13.680> welcome 00:12:14.990 --> 00:12:15.000 align:start position:0% um that would be welcome 00:12:15.000 --> 00:12:16.970 align:start position:0% um that would be welcome okay<00:12:15.540> we<00:12:15.839> need<00:12:16.019> to<00:12:16.140> wrap<00:12:16.320> this<00:12:16.440> up<00:12:16.560> I'm<00:12:16.740> sorry 00:12:16.970 --> 00:12:16.980 align:start position:0% okay we need to wrap this up I'm sorry 00:12:16.980 --> 00:12:20.509 align:start position:0% okay we need to wrap this up I'm sorry but<00:12:17.339> uh<00:12:17.880> Igor<00:12:18.360> you're<00:12:18.959> up<00:12:19.140> next 00:12:20.509 --> 00:12:20.519 align:start position:0% but uh Igor you're up next 00:12:20.519 --> 00:12:21.889 align:start position:0% but uh Igor you're up next thank<00:12:21.000> you 00:12:21.889 --> 00:12:21.899 align:start position:0% thank you 00:12:21.899 --> 00:12:24.610 align:start position:0% thank you my<00:12:22.620> name<00:12:22.680> is 00:12:24.610 --> 00:12:24.620 align:start position:0% my name is 00:12:24.620 --> 00:12:28.990 align:start position:0% my name is developer<00:12:25.620> and<00:12:26.160> I'm<00:12:26.459> here<00:12:26.700> to<00:12:27.000> Champion<00:12:27.300> EP 00:12:28.990 --> 00:12:29.000 align:start position:0% developer and I'm here to Champion EP 00:12:29.000 --> 00:12:33.590 align:start position:0% developer and I'm here to Champion EP 5978<00:12:30.000> Untitled<00:12:30.899> guest<00:12:31.440> refund<00:12:31.800> and<00:12:32.040> reverse 00:12:33.590 --> 00:12:33.600 align:start position:0% 5978 Untitled guest refund and reverse 00:12:33.600 --> 00:12:37.269 align:start position:0% 5978 Untitled guest refund and reverse some<00:12:33.959> motivation<00:12:34.380> for<00:12:34.860> this<00:12:35.100> Eep<00:12:35.880> is<00:12:36.480> that 00:12:37.269 --> 00:12:37.279 align:start position:0% some motivation for this Eep is that 00:12:37.279 --> 00:12:41.090 align:start position:0% some motivation for this Eep is that revert<00:12:38.279> of<00:12:38.339> a<00:12:38.459> transaction<00:12:38.820> or<00:12:39.480> any<00:12:39.920> its<00:12:40.920> sub 00:12:41.090 --> 00:12:41.100 align:start position:0% revert of a transaction or any its sub 00:12:41.100 --> 00:12:43.970 align:start position:0% revert of a transaction or any its sub calls<00:12:41.579> drops<00:12:42.060> any<00:12:42.240> state<00:12:42.540> modifications 00:12:43.970 --> 00:12:43.980 align:start position:0% calls drops any state modifications 00:12:43.980 --> 00:12:46.970 align:start position:0% calls drops any state modifications but<00:12:44.820> the<00:12:45.360> user<00:12:45.720> has<00:12:45.899> to<00:12:46.079> pay<00:12:46.260> the<00:12:46.500> full<00:12:46.740> price 00:12:46.970 --> 00:12:46.980 align:start position:0% but the user has to pay the full price 00:12:46.980 --> 00:12:51.050 align:start position:0% but the user has to pay the full price for<00:12:47.459> the<00:12:47.700> state<00:12:47.940> modifications<00:12:48.600> while 00:12:51.050 --> 00:12:51.060 align:start position:0% for the state modifications while 00:12:51.060 --> 00:12:53.889 align:start position:0% for the state modifications while with<00:12:51.779> State<00:12:52.139> modifications<00:12:52.680> are<00:12:53.160> not 00:12:53.889 --> 00:12:53.899 align:start position:0% with State modifications are not 00:12:53.899 --> 00:12:58.449 align:start position:0% with State modifications are not preserved<00:12:54.899> for<00:12:55.320> forever<00:12:55.860> and<00:12:56.820> this<00:12:57.120> has<00:12:57.360> two 00:12:58.449 --> 00:12:58.459 align:start position:0% preserved for forever and this has two 00:12:58.459 --> 00:13:01.670 align:start position:0% preserved for forever and this has two problems<00:12:59.459> with<00:12:59.700> this<00:12:59.940> is<00:13:00.180> that<00:13:00.480> users<00:13:01.139> overpay 00:13:01.670 --> 00:13:01.680 align:start position:0% problems with this is that users overpay 00:13:01.680 --> 00:13:04.610 align:start position:0% problems with this is that users overpay and<00:13:01.980> then<00:13:02.100> it<00:13:02.339> limits<00:13:03.120> some<00:13:03.899> solidity 00:13:04.610 --> 00:13:04.620 align:start position:0% and then it limits some solidity 00:13:04.620 --> 00:13:07.069 align:start position:0% and then it limits some solidity patterns<00:13:05.160> where<00:13:05.339> you<00:13:05.639> may<00:13:05.820> may<00:13:06.480> have<00:13:06.779> a<00:13:06.959> call 00:13:07.069 --> 00:13:07.079 align:start position:0% patterns where you may may have a call 00:13:07.079 --> 00:13:10.910 align:start position:0% patterns where you may may have a call and<00:13:07.440> revert<00:13:07.860> it<00:13:08.060> and<00:13:09.200> it<00:13:10.200> makes<00:13:10.380> it<00:13:10.560> extremely 00:13:10.910 --> 00:13:10.920 align:start position:0% and revert it and it makes it extremely 00:13:10.920 --> 00:13:13.550 align:start position:0% and revert it and it makes it extremely expensive<00:13:11.399> to<00:13:11.700> the<00:13:11.820> point<00:13:12.060> where<00:13:12.560> sometimes 00:13:13.550 --> 00:13:13.560 align:start position:0% expensive to the point where sometimes 00:13:13.560 --> 00:13:16.129 align:start position:0% expensive to the point where sometimes instead<00:13:14.100> of<00:13:14.160> reverting<00:13:14.639> the<00:13:14.820> call<00:13:15.060> you<00:13:15.959> may 00:13:16.129 --> 00:13:16.139 align:start position:0% instead of reverting the call you may 00:13:16.139 --> 00:13:18.889 align:start position:0% instead of reverting the call you may just<00:13:16.320> like<00:13:16.740> transfer<00:13:17.279> easy<00:13:17.459> tokens<00:13:18.060> from<00:13:18.720> one 00:13:18.889 --> 00:13:18.899 align:start position:0% just like transfer easy tokens from one 00:13:18.899 --> 00:13:20.750 align:start position:0% just like transfer easy tokens from one address<00:13:19.139> to<00:13:19.500> another<00:13:19.620> just<00:13:19.980> to<00:13:20.220> like<00:13:20.339> restore 00:13:20.750 --> 00:13:20.760 align:start position:0% address to another just to like restore 00:13:20.760 --> 00:13:24.170 align:start position:0% address to another just to like restore the<00:13:21.000> storage<00:13:21.300> instead<00:13:22.019> of<00:13:22.339> uh<00:13:23.339> paying<00:13:24.060> the 00:13:24.170 --> 00:13:24.180 align:start position:0% the storage instead of uh paying the 00:13:24.180 --> 00:13:27.650 align:start position:0% the storage instead of uh paying the higher<00:13:24.540> gas<00:13:24.720> price<00:13:24.959> of<00:13:25.639> reverting<00:13:26.639> the<00:13:27.480> call 00:13:27.650 --> 00:13:27.660 align:start position:0% higher gas price of reverting the call 00:13:27.660 --> 00:13:29.810 align:start position:0% higher gas price of reverting the call and<00:13:28.139> in<00:13:28.260> my<00:13:28.440> opinion<00:13:28.740> it's<00:13:28.860> an<00:13:29.100> anti-pattern 00:13:29.810 --> 00:13:29.820 align:start position:0% and in my opinion it's an anti-pattern 00:13:29.820 --> 00:13:31.790 align:start position:0% and in my opinion it's an anti-pattern because<00:13:30.000> some<00:13:30.360> side<00:13:30.600> effects<00:13:31.019> can<00:13:31.260> be<00:13:31.440> missed 00:13:31.790 --> 00:13:31.800 align:start position:0% because some side effects can be missed 00:13:31.800 --> 00:13:35.870 align:start position:0% because some side effects can be missed and<00:13:32.700> it<00:13:33.300> may<00:13:33.480> result<00:13:33.660> in<00:13:34.260> a<00:13:34.500> critical<00:13:35.399> hacks 00:13:35.870 --> 00:13:35.880 align:start position:0% and it may result in a critical hacks 00:13:35.880 --> 00:13:37.790 align:start position:0% and it may result in a critical hacks and<00:13:36.120> lots<00:13:36.480> of<00:13:36.540> funds<00:13:36.899> eventually 00:13:37.790 --> 00:13:37.800 align:start position:0% and lots of funds eventually 00:13:37.800 --> 00:13:42.050 align:start position:0% and lots of funds eventually and<00:13:38.399> vcp<00:13:39.000> suggests<00:13:39.540> to<00:13:40.139> reprise<00:13:41.100> the 00:13:42.050 --> 00:13:42.060 align:start position:0% and vcp suggests to reprise the 00:13:42.060 --> 00:13:44.870 align:start position:0% and vcp suggests to reprise the following<00:13:42.360> op<00:13:42.600> codes<00:13:43.019> as<00:13:43.560> a<00:13:43.800> s<00:13:44.220> store<00:13:44.459> create 00:13:44.870 --> 00:13:44.880 align:start position:0% following op codes as a s store create 00:13:44.880 --> 00:13:49.250 align:start position:0% following op codes as a s store create so<00:13:45.660> so<00:13:46.440> distract<00:13:47.360> through<00:13:48.360> the<00:13:48.540> gas<00:13:48.720> refund 00:13:49.250 --> 00:13:49.260 align:start position:0% so so distract through the gas refund 00:13:49.260 --> 00:13:50.930 align:start position:0% so so distract through the gas refund mechanism<00:13:49.740> so<00:13:50.160> they're<00:13:50.339> not<00:13:50.519> going<00:13:50.700> to<00:13:50.820> be 00:13:50.930 --> 00:13:50.940 align:start position:0% mechanism so they're not going to be 00:13:50.940 --> 00:13:53.449 align:start position:0% mechanism so they're not going to be free<00:13:51.180> still<00:13:51.779> gonna<00:13:52.260> pay<00:13:52.560> some<00:13:52.860> price<00:13:53.100> for 00:13:53.449 --> 00:13:53.459 align:start position:0% free still gonna pay some price for 00:13:53.459 --> 00:13:56.690 align:start position:0% free still gonna pay some price for touching<00:13:54.000> uh<00:13:54.899> with<00:13:55.139> addresses<00:13:55.800> or<00:13:56.459> storage 00:13:56.690 --> 00:13:56.700 align:start position:0% touching uh with addresses or storage 00:13:56.700 --> 00:13:59.690 align:start position:0% touching uh with addresses or storage variables<00:13:57.420> but<00:13:58.139> it<00:13:58.320> seems<00:13:58.680> unfair<00:13:58.980> to<00:13:59.279> pay<00:13:59.459> a 00:13:59.690 --> 00:13:59.700 align:start position:0% variables but it seems unfair to pay a 00:13:59.700 --> 00:14:03.350 align:start position:0% variables but it seems unfair to pay a full<00:13:59.880> price<00:14:00.380> vcp<00:14:01.380> is<00:14:01.560> a<00:14:01.860> in<00:14:02.459> a<00:14:02.639> in<00:14:03.000> an<00:14:03.120> early 00:14:03.350 --> 00:14:03.360 align:start position:0% full price vcp is a in a in an early 00:14:03.360 --> 00:14:04.490 align:start position:0% full price vcp is a in a in an early version 00:14:04.490 --> 00:14:04.500 align:start position:0% version 00:14:04.500 --> 00:14:07.190 align:start position:0% version so<00:14:05.100> I<00:14:05.399> just<00:14:05.519> want<00:14:05.700> to<00:14:05.880> spread<00:14:06.360> more<00:14:06.779> awareness 00:14:07.190 --> 00:14:07.200 align:start position:0% so I just want to spread more awareness 00:14:07.200 --> 00:14:10.009 align:start position:0% so I just want to spread more awareness around<00:14:07.500> this<00:14:07.800> problem<00:14:08.120> and<00:14:09.120> hear<00:14:09.480> what<00:14:09.779> kind 00:14:10.009 --> 00:14:10.019 align:start position:0% around this problem and hear what kind 00:14:10.019 --> 00:14:16.250 align:start position:0% around this problem and hear what kind of<00:14:10.139> comments<00:14:10.620> people<00:14:10.980> have<00:14:11.279> thank<00:14:11.700> you 00:14:16.250 --> 00:14:16.260 align:start position:0% 00:14:16.260 --> 00:14:19.730 align:start position:0% uh<00:14:17.040> question<00:14:17.459> uh<00:14:17.940> I'm<00:14:18.420> maybe<00:14:19.260> I<00:14:19.440> missed 00:14:19.730 --> 00:14:19.740 align:start position:0% uh question uh I'm maybe I missed 00:14:19.740 --> 00:14:22.250 align:start position:0% uh question uh I'm maybe I missed something<00:14:19.800> but<00:14:21.120> um<00:14:21.180> is<00:14:21.720> the<00:14:21.839> suggestion 00:14:22.250 --> 00:14:22.260 align:start position:0% something but um is the suggestion 00:14:22.260 --> 00:14:23.810 align:start position:0% something but um is the suggestion essentially<00:14:22.680> to<00:14:22.920> reprice<00:14:23.339> some<00:14:23.579> of<00:14:23.700> the 00:14:23.810 --> 00:14:23.820 align:start position:0% essentially to reprice some of the 00:14:23.820 --> 00:14:33.230 align:start position:0% essentially to reprice some of the storage<00:14:24.000> of<00:14:24.300> codes 00:14:33.230 --> 00:14:33.240 align:start position:0% 00:14:33.240 --> 00:14:38.210 align:start position:0% and<00:14:33.600> let's<00:14:34.260> say<00:14:34.380> sloth<00:14:34.860> is 00:14:38.210 --> 00:14:38.220 align:start position:0% 00:14:38.220 --> 00:14:42.650 align:start position:0% sorry<00:14:38.700> for<00:14:39.139> the<00:14:40.139> clarity<00:14:40.620> so<00:14:40.980> if<00:14:41.279> let's<00:14:41.820> say<00:14:42.060> if 00:14:42.650 --> 00:14:42.660 align:start position:0% sorry for the clarity so if let's say if 00:14:42.660 --> 00:14:44.290 align:start position:0% sorry for the clarity so if let's say if s<00:14:42.899> load<00:14:43.260> operation 00:14:44.290 --> 00:14:44.300 align:start position:0% s load operation 00:14:44.300 --> 00:14:47.269 align:start position:0% s load operation store<00:14:45.300> operation<00:14:45.779> inside<00:14:46.500> the<00:14:46.800> reverted 00:14:47.269 --> 00:14:47.279 align:start position:0% store operation inside the reverted 00:14:47.279 --> 00:14:48.410 align:start position:0% store operation inside the reverted transaction 00:14:48.410 --> 00:14:48.420 align:start position:0% transaction 00:14:48.420 --> 00:14:54.170 align:start position:0% transaction uh<00:14:49.199> costs<00:14:49.760> 22<00:14:51.060> 000<00:14:51.180> and<00:14:51.600> then<00:14:51.899> with<00:14:52.500> some 00:14:54.170 --> 00:14:54.180 align:start position:0% uh costs 22 000 and then with some 00:14:54.180 --> 00:14:57.710 align:start position:0% uh costs 22 000 and then with some we<00:14:55.019> score<00:14:55.320> reverts<00:14:56.040> then<00:14:56.459> the<00:14:57.120> cost<00:14:57.300> of<00:14:57.540> the 00:14:57.710 --> 00:14:57.720 align:start position:0% we score reverts then the cost of the 00:14:57.720 --> 00:14:59.689 align:start position:0% we score reverts then the cost of the separation<00:14:58.079> should<00:14:58.380> be<00:14:58.560> repriced<00:14:59.160> as<00:14:59.459> just 00:14:59.689 --> 00:14:59.699 align:start position:0% separation should be repriced as just 00:14:59.699 --> 00:15:02.150 align:start position:0% separation should be repriced as just like<00:14:59.820> a<00:15:00.060> attaching<00:15:00.660> this<00:15:01.019> load<00:15:01.320> for 00:15:02.150 --> 00:15:02.160 align:start position:0% like a attaching this load for 00:15:02.160 --> 00:15:04.790 align:start position:0% like a attaching this load for a<00:15:02.760> different<00:15:03.120> number<00:15:03.420> so<00:15:03.720> you<00:15:04.019> should<00:15:04.199> not<00:15:04.380> pay 00:15:04.790 --> 00:15:04.800 align:start position:0% a different number so you should not pay 00:15:04.800 --> 00:15:08.269 align:start position:0% a different number so you should not pay twenty<00:15:05.579> two<00:15:05.760> thousand<00:15:06.180> for<00:15:06.600> modifying<00:15:07.380> uh 00:15:08.269 --> 00:15:08.279 align:start position:0% twenty two thousand for modifying uh 00:15:08.279 --> 00:15:10.610 align:start position:0% twenty two thousand for modifying uh storage<00:15:08.519> slot<00:15:09.000> which<00:15:09.300> is<00:15:09.540> not<00:15:09.720> modified<00:15:10.079> at 00:15:10.610 --> 00:15:10.620 align:start position:0% storage slot which is not modified at 00:15:10.620 --> 00:15:12.110 align:start position:0% storage slot which is not modified at the<00:15:10.740> end<00:15:10.860> of<00:15:11.040> transaction 00:15:12.110 --> 00:15:12.120 align:start position:0% the end of transaction 00:15:12.120 --> 00:15:13.850 align:start position:0% the end of transaction and<00:15:12.600> the<00:15:12.720> pricing<00:15:13.079> should<00:15:13.260> happen<00:15:13.500> through 00:15:13.850 --> 00:15:13.860 align:start position:0% and the pricing should happen through 00:15:13.860 --> 00:15:16.329 align:start position:0% and the pricing should happen through the<00:15:14.100> gas<00:15:14.279> refund<00:15:14.760> mechanism 00:15:16.329 --> 00:15:16.339 align:start position:0% the gas refund mechanism 00:15:16.339 --> 00:15:19.970 align:start position:0% the gas refund mechanism uh<00:15:17.339> does<00:15:17.880> it<00:15:18.000> bring<00:15:18.180> any<00:15:18.420> clarity 00:15:19.970 --> 00:15:19.980 align:start position:0% uh does it bring any clarity 00:15:19.980 --> 00:15:25.750 align:start position:0% uh does it bring any clarity foreign 00:15:25.750 --> 00:15:25.760 align:start position:0% 00:15:25.760 --> 00:15:28.189 align:start position:0% idea<00:15:26.760> so<00:15:27.480> um 00:15:28.189 --> 00:15:28.199 align:start position:0% idea so um 00:15:28.199 --> 00:15:29.689 align:start position:0% idea so um it<00:15:28.560> mostly<00:15:28.860> means<00:15:29.100> you<00:15:29.220> would<00:15:29.399> need<00:15:29.579> to 00:15:29.689 --> 00:15:29.699 align:start position:0% it mostly means you would need to 00:15:29.699 --> 00:15:31.850 align:start position:0% it mostly means you would need to remember<00:15:29.820> all<00:15:30.240> of<00:15:30.420> the<00:15:30.540> changes<00:15:30.899> you've<00:15:31.139> done 00:15:31.850 --> 00:15:31.860 align:start position:0% remember all of the changes you've done 00:15:31.860 --> 00:15:34.550 align:start position:0% remember all of the changes you've done and<00:15:32.459> then<00:15:32.639> it's<00:15:33.120> like<00:15:33.360> single<00:15:33.779> point<00:15:33.959> on<00:15:34.320> the 00:15:34.550 --> 00:15:34.560 align:start position:0% and then it's like single point on the 00:15:34.560 --> 00:15:36.110 align:start position:0% and then it's like single point on the reverts<00:15:35.040> goes<00:15:35.279> you<00:15:35.459> would<00:15:35.639> need<00:15:35.760> to<00:15:35.880> go 00:15:36.110 --> 00:15:36.120 align:start position:0% reverts goes you would need to go 00:15:36.120 --> 00:15:38.509 align:start position:0% reverts goes you would need to go through<00:15:36.660> all<00:15:36.959> of<00:15:37.079> the<00:15:37.320> changes<00:15:37.680> and<00:15:37.920> apply<00:15:38.279> a 00:15:38.509 --> 00:15:38.519 align:start position:0% through all of the changes and apply a 00:15:38.519 --> 00:15:40.550 align:start position:0% through all of the changes and apply a compute<00:15:38.940> at<00:15:39.000> least<00:15:39.180> the<00:15:39.420> refund<00:15:39.959> you<00:15:40.260> you<00:15:40.380> get 00:15:40.550 --> 00:15:40.560 align:start position:0% compute at least the refund you you get 00:15:40.560 --> 00:15:43.370 align:start position:0% compute at least the refund you you get from<00:15:40.740> that<00:15:40.920> so<00:15:41.820> like<00:15:42.060> you<00:15:42.420> have<00:15:42.720> like<00:15:43.019> single 00:15:43.370 --> 00:15:43.380 align:start position:0% from that so like you have like single 00:15:43.380 --> 00:15:45.410 align:start position:0% from that so like you have like single operation<00:15:43.800> that<00:15:44.279> it's<00:15:44.940> actually<00:15:45.120> like 00:15:45.410 --> 00:15:45.420 align:start position:0% operation that it's actually like 00:15:45.420 --> 00:15:48.889 align:start position:0% operation that it's actually like unbounded<00:15:46.079> in<00:15:46.380> the<00:15:46.560> complexity<00:15:47.279> internally 00:15:48.889 --> 00:15:48.899 align:start position:0% unbounded in the complexity internally 00:15:48.899 --> 00:15:51.410 align:start position:0% unbounded in the complexity internally and<00:15:49.620> that<00:15:49.980> might<00:15:50.160> be<00:15:50.339> like<00:15:50.519> doable<00:15:50.940> if<00:15:51.300> you 00:15:51.410 --> 00:15:51.420 align:start position:0% and that might be like doable if you 00:15:51.420 --> 00:15:53.750 align:start position:0% and that might be like doable if you have<00:15:51.660> this<00:15:52.019> journal<00:15:52.440> Journal<00:15:53.100> implementation 00:15:53.750 --> 00:15:53.760 align:start position:0% have this journal Journal implementation 00:15:53.760 --> 00:15:56.389 align:start position:0% have this journal Journal implementation of<00:15:54.060> the<00:15:54.180> state<00:15:54.360> because<00:15:54.779> you<00:15:55.199> do<00:15:55.560> also<00:15:56.100> there 00:15:56.389 --> 00:15:56.399 align:start position:0% of the state because you do also there 00:15:56.399 --> 00:15:59.750 align:start position:0% of the state because you do also there like<00:15:56.880> on<00:15:57.420> journal<00:15:57.839> the<00:15:58.019> the<00:15:58.199> changes<00:15:58.680> but<00:15:59.459> if 00:15:59.750 --> 00:15:59.760 align:start position:0% like on journal the the changes but if 00:15:59.760 --> 00:16:01.430 align:start position:0% like on journal the the changes but if someone<00:15:59.940> has<00:16:00.240> different<00:16:00.480> implementation<00:16:01.199> of 00:16:01.430 --> 00:16:01.440 align:start position:0% someone has different implementation of 00:16:01.440 --> 00:16:03.710 align:start position:0% someone has different implementation of that<00:16:01.620> it<00:16:02.579> might<00:16:02.760> be<00:16:02.940> really<00:16:03.060> difficult<00:16:03.420> to 00:16:03.710 --> 00:16:03.720 align:start position:0% that it might be really difficult to 00:16:03.720 --> 00:16:06.949 align:start position:0% that it might be really difficult to implement 00:16:06.949 --> 00:16:06.959 align:start position:0% 00:16:06.959 --> 00:16:10.069 align:start position:0% and<00:16:07.680> just<00:16:07.980> one<00:16:08.100> more<00:16:08.279> comment<00:16:08.639> that<00:16:10.079> um 00:16:10.069 --> 00:16:10.079 align:start position:0% and just one more comment that um 00:16:10.079 --> 00:16:12.069 align:start position:0% and just one more comment that um usually<00:16:10.560> with<00:16:10.920> when 00:16:12.069 --> 00:16:12.079 align:start position:0% usually with when 00:16:12.079 --> 00:16:14.269 align:start position:0% usually with when reverters<00:16:13.079> you<00:16:13.440> can<00:16:13.560> actually<00:16:13.620> have<00:16:13.800> nested 00:16:14.269 --> 00:16:14.279 align:start position:0% reverters you can actually have nested 00:16:14.279 --> 00:16:17.150 align:start position:0% reverters you can actually have nested reverters<00:16:14.760> and<00:16:15.240> you<00:16:15.420> that<00:16:15.839> can<00:16:16.079> end<00:16:16.440> up<00:16:16.620> quite 00:16:17.150 --> 00:16:17.160 align:start position:0% reverters and you that can end up quite 00:16:17.160 --> 00:16:20.090 align:start position:0% reverters and you that can end up quite nasty<00:16:17.699> when<00:16:18.120> you<00:16:18.720> have<00:16:18.839> subcodes<00:16:19.440> that<00:16:19.680> revert 00:16:20.090 --> 00:16:20.100 align:start position:0% nasty when you have subcodes that revert 00:16:20.100 --> 00:16:21.590 align:start position:0% nasty when you have subcodes that revert and<00:16:20.220> the<00:16:20.339> outer<00:16:20.579> code<00:16:20.760> doesn't<00:16:21.000> revert<00:16:21.480> then 00:16:21.590 --> 00:16:21.600 align:start position:0% and the outer code doesn't revert then 00:16:21.600 --> 00:16:24.829 align:start position:0% and the outer code doesn't revert then the<00:16:21.899> outer<00:16:22.560> cool<00:16:22.680> again<00:16:22.920> reverts<00:16:23.519> so 00:16:24.829 --> 00:16:24.839 align:start position:0% the outer cool again reverts so 00:16:24.839 --> 00:16:28.910 align:start position:0% the outer cool again reverts so it's<00:16:25.500> not<00:16:25.800> a<00:16:26.100> very<00:16:26.279> very<00:16:26.519> easy<00:16:26.880> EIP<00:16:27.540> to<00:16:28.139> tackle 00:16:28.910 --> 00:16:28.920 align:start position:0% it's not a very very easy EIP to tackle 00:16:28.920 --> 00:16:31.610 align:start position:0% it's not a very very easy EIP to tackle it<00:16:29.699> might<00:16:29.820> not<00:16:29.940> be<00:16:30.120> too<00:16:30.360> hard<00:16:30.600> but<00:16:30.899> it's<00:16:31.199> I 00:16:31.610 --> 00:16:31.620 align:start position:0% it might not be too hard but it's I 00:16:31.620 --> 00:16:33.290 align:start position:0% it might not be too hard but it's I think<00:16:31.740> the<00:16:31.980> reason<00:16:32.220> about<00:16:32.519> it<00:16:32.760> is<00:16:33.000> not 00:16:33.290 --> 00:16:33.300 align:start position:0% think the reason about it is not 00:16:33.300 --> 00:16:35.930 align:start position:0% think the reason about it is not necessarily<00:16:34.199> easy 00:16:35.930 --> 00:16:35.940 align:start position:0% necessarily easy 00:16:35.940 --> 00:16:39.110 align:start position:0% necessarily easy yeah<00:16:36.420> I<00:16:36.600> think<00:16:36.779> that<00:16:37.019> if<00:16:37.860> if<00:16:37.980> like<00:16:38.399> that<00:16:38.639> is 00:16:39.110 --> 00:16:39.120 align:start position:0% yeah I think that if if like that is 00:16:39.120 --> 00:16:41.870 align:start position:0% yeah I think that if if like that is assuming<00:16:39.779> that<00:16:39.959> we<00:16:40.259> have<00:16:40.500> to<00:16:40.699> keep<00:16:41.699> the 00:16:41.870 --> 00:16:41.880 align:start position:0% assuming that we have to keep the 00:16:41.880 --> 00:16:43.730 align:start position:0% assuming that we have to keep the journal<00:16:42.240> all<00:16:42.420> the<00:16:42.540> time<00:16:42.660> and<00:16:42.899> use<00:16:43.139> it<00:16:43.320> for<00:16:43.500> all 00:16:43.730 --> 00:16:43.740 align:start position:0% journal all the time and use it for all 00:16:43.740 --> 00:16:46.670 align:start position:0% journal all the time and use it for all all<00:16:43.980> the<00:16:44.399> other<00:16:44.459> apartment<00:16:44.899> operations<00:16:45.899> and 00:16:46.670 --> 00:16:46.680 align:start position:0% all the other apartment operations and 00:16:46.680 --> 00:16:47.689 align:start position:0% all the other apartment operations and uh 00:16:47.689 --> 00:16:47.699 align:start position:0% uh 00:16:47.699 --> 00:16:49.970 align:start position:0% uh it<00:16:48.180> kind<00:16:48.360> of<00:16:48.420> this<00:16:48.899> idea<00:16:49.139> fits<00:16:49.560> into<00:16:49.740> that 00:16:49.970 --> 00:16:49.980 align:start position:0% it kind of this idea fits into that 00:16:49.980 --> 00:16:52.910 align:start position:0% it kind of this idea fits into that perfectly<00:16:50.579> I<00:16:51.480> think<00:16:51.720> that<00:16:52.440> might<00:16:52.680> be 00:16:52.910 --> 00:16:52.920 align:start position:0% perfectly I think that might be 00:16:52.920 --> 00:16:55.249 align:start position:0% perfectly I think that might be considered<00:16:53.459> but<00:16:54.060> if<00:16:54.779> there<00:16:54.959> is<00:16:55.079> something 00:16:55.249 --> 00:16:55.259 align:start position:0% considered but if there is something 00:16:55.259 --> 00:16:56.810 align:start position:0% considered but if there is something that<00:16:55.560> you<00:16:55.680> would<00:16:55.800> need<00:16:55.980> to<00:16:56.160> keep<00:16:56.459> different 00:16:56.810 --> 00:16:56.820 align:start position:0% that you would need to keep different 00:16:56.820 --> 00:16:59.210 align:start position:0% that you would need to keep different data<00:16:57.480> structure<00:16:57.839> just<00:16:58.079> for<00:16:58.320> that<00:16:58.560> I<00:16:58.800> think<00:16:58.920> it 00:16:59.210 --> 00:16:59.220 align:start position:0% data structure just for that I think it 00:16:59.220 --> 00:17:01.009 align:start position:0% data structure just for that I think it should<00:16:59.399> be<00:16:59.639> really<00:16:59.820> difficult<00:17:00.240> to<00:17:00.660> have<00:17:00.839> it 00:17:01.009 --> 00:17:01.019 align:start position:0% should be really difficult to have it 00:17:01.019 --> 00:17:03.350 align:start position:0% should be really difficult to have it and<00:17:01.860> I<00:17:01.980> know<00:17:02.160> some<00:17:02.459> of<00:17:02.579> the<00:17:02.759> implementations 00:17:03.350 --> 00:17:03.360 align:start position:0% and I know some of the implementations 00:17:03.360 --> 00:17:05.449 align:start position:0% and I know some of the implementations actually<00:17:03.839> don't<00:17:04.199> use<00:17:04.500> the<00:17:04.860> State<00:17:05.040> Journal 00:17:05.449 --> 00:17:05.459 align:start position:0% actually don't use the State Journal 00:17:05.459 --> 00:17:07.850 align:start position:0% actually don't use the State Journal light<00:17:05.760> I<00:17:06.600> mean<00:17:06.660> that's<00:17:06.959> not<00:17:07.199> something<00:17:07.439> we 00:17:07.850 --> 00:17:07.860 align:start position:0% light I mean that's not something we 00:17:07.860 --> 00:17:11.270 align:start position:0% light I mean that's not something we mandate<00:17:08.400> to<00:17:08.579> to<00:17:09.000> be<00:17:09.240> used 00:17:11.270 --> 00:17:11.280 align:start position:0% mandate to to be used 00:17:11.280 --> 00:17:14.870 align:start position:0% mandate to to be used so<00:17:12.059> you<00:17:12.540> would<00:17:12.720> need<00:17:13.020> like<00:17:13.980> in<00:17:14.160> other<00:17:14.280> words<00:17:14.520> it 00:17:14.870 --> 00:17:14.880 align:start position:0% so you would need like in other words it 00:17:14.880 --> 00:17:17.090 align:start position:0% so you would need like in other words it would<00:17:15.120> be<00:17:15.480> forced<00:17:15.839> to<00:17:16.140> keep<00:17:16.380> something<00:17:16.679> like 00:17:17.090 --> 00:17:17.100 align:start position:0% would be forced to keep something like 00:17:17.100 --> 00:17:20.870 align:start position:0% would be forced to keep something like that<00:17:17.760> anyway<00:17:18.500> although<00:17:19.500> it's<00:17:19.679> not<00:17:19.919> required 00:17:20.870 --> 00:17:20.880 align:start position:0% that anyway although it's not required 00:17:20.880 --> 00:17:25.549 align:start position:0% that anyway although it's not required uh<00:17:21.780> in<00:17:22.140> particular<00:17:22.500> right<00:17:22.740> now 00:17:25.549 --> 00:17:25.559 align:start position:0% 00:17:25.559 --> 00:17:27.350 align:start position:0% you<00:17:26.040> have<00:17:26.160> to<00:17:26.280> keep<00:17:26.400> track<00:17:26.640> of<00:17:26.880> a<00:17:27.000> whole<00:17:27.120> lot<00:17:27.240> of 00:17:27.350 --> 00:17:27.360 align:start position:0% you have to keep track of a whole lot of 00:17:27.360 --> 00:17:29.450 align:start position:0% you have to keep track of a whole lot of information<00:17:27.540> for<00:17:28.439> um 00:17:29.450 --> 00:17:29.460 align:start position:0% information for um 00:17:29.460 --> 00:17:32.390 align:start position:0% information for um for<00:17:30.000> the<00:17:30.299> uh<00:17:31.080> for<00:17:31.380> the<00:17:31.559> refunds<00:17:31.919> anyway<00:17:32.040> for 00:17:32.390 --> 00:17:32.400 align:start position:0% for the uh for the refunds anyway for 00:17:32.400 --> 00:17:33.770 align:start position:0% for the uh for the refunds anyway for the<00:17:32.520> for<00:17:32.700> the<00:17:32.820> storage<00:17:32.940> refunds<00:17:33.419> anyway<00:17:33.540> so 00:17:33.770 --> 00:17:33.780 align:start position:0% the for the storage refunds anyway so 00:17:33.780 --> 00:17:34.669 align:start position:0% the for the storage refunds anyway so it's<00:17:33.960> the<00:17:34.080> same<00:17:34.200> stuff<00:17:34.380> and<00:17:34.559> all 00:17:34.669 --> 00:17:34.679 align:start position:0% it's the same stuff and all 00:17:34.679 --> 00:17:36.529 align:start position:0% it's the same stuff and all implementations<00:17:35.220> I<00:17:35.940> think<00:17:36.120> whether<00:17:36.360> it's 00:17:36.529 --> 00:17:36.539 align:start position:0% implementations I think whether it's 00:17:36.539 --> 00:17:38.029 align:start position:0% implementations I think whether it's journal<00:17:36.840> or<00:17:36.960> cash<00:17:37.140> you<00:17:37.380> have<00:17:37.559> all<00:17:37.679> the<00:17:37.740> info 00:17:38.029 --> 00:17:38.039 align:start position:0% journal or cash you have all the info 00:17:38.039 --> 00:17:39.409 align:start position:0% journal or cash you have all the info you<00:17:38.220> need 00:17:39.409 --> 00:17:39.419 align:start position:0% you need 00:17:39.419 --> 00:17:41.450 align:start position:0% you need um<00:17:39.480> but<00:17:40.080> I'm<00:17:40.260> just<00:17:40.440> still 00:17:41.450 --> 00:17:41.460 align:start position:0% um but I'm just still 00:17:41.460 --> 00:17:43.250 align:start position:0% um but I'm just still traumatized<00:17:42.299> by<00:17:42.419> some<00:17:42.539> of<00:17:42.660> the<00:17:42.720> code<00:17:42.840> I<00:17:43.020> had<00:17:43.140> to 00:17:43.250 --> 00:17:43.260 align:start position:0% traumatized by some of the code I had to 00:17:43.260 --> 00:17:45.049 align:start position:0% traumatized by some of the code I had to write<00:17:43.380> for<00:17:43.860> the<00:17:44.340> um 00:17:45.049 --> 00:17:45.059 align:start position:0% write for the um 00:17:45.059 --> 00:17:47.930 align:start position:0% write for the um for<00:17:45.539> when<00:17:45.720> we<00:17:45.960> were<00:17:46.080> doing<00:17:46.500> the<00:17:46.799> the<00:17:47.039> repricing 00:17:47.930 --> 00:17:47.940 align:start position:0% for when we were doing the the repricing 00:17:47.940 --> 00:17:50.570 align:start position:0% for when we were doing the the repricing of<00:17:48.120> the<00:17:48.660> the<00:17:48.900> 2200 00:17:50.570 --> 00:17:50.580 align:start position:0% of the the 2200 00:17:50.580 --> 00:17:51.770 align:start position:0% of the the 2200 um<00:17:50.640> I<00:17:50.700> can't<00:17:50.820> remember<00:17:50.940> exactly<00:17:51.299> the<00:17:51.480> name<00:17:51.600> of 00:17:51.770 --> 00:17:51.780 align:start position:0% um I can't remember exactly the name of 00:17:51.780 --> 00:17:53.330 align:start position:0% um I can't remember exactly the name of the<00:17:51.900> of<00:17:52.020> it<00:17:52.200> where<00:17:52.559> it<00:17:52.740> was<00:17:52.799> over<00:17:52.919> fitted 00:17:53.330 --> 00:17:53.340 align:start position:0% the of it where it was over fitted 00:17:53.340 --> 00:17:55.010 align:start position:0% the of it where it was over fitted fitted<00:17:53.760> to<00:17:53.820> get<00:17:53.940> and 00:17:55.010 --> 00:17:55.020 align:start position:0% fitted to get and 00:17:55.020 --> 00:17:57.529 align:start position:0% fitted to get and um our<00:17:55.260> code<00:17:55.500> analysis<00:17:56.280> tool<00:17:56.640> freaked<00:17:57.299> out<00:17:57.419> of 00:17:57.529 --> 00:17:57.539 align:start position:0% um our code analysis tool freaked out of 00:17:57.539 --> 00:17:58.970 align:start position:0% um our code analysis tool freaked out of the<00:17:57.600> complexity<00:17:58.020> of<00:17:58.200> the<00:17:58.260> code<00:17:58.380> so<00:17:58.620> I'm<00:17:58.799> kind 00:17:58.970 --> 00:17:58.980 align:start position:0% the complexity of the code so I'm kind 00:17:58.980 --> 00:18:00.409 align:start position:0% the complexity of the code so I'm kind of<00:17:59.100> concerned<00:17:59.400> about<00:17:59.520> that<00:17:59.760> about<00:18:00.120> the 00:18:00.409 --> 00:18:00.419 align:start position:0% of concerned about that about the 00:18:00.419 --> 00:18:02.270 align:start position:0% of concerned about that about the maintainability<00:18:00.900> of<00:18:01.200> some<00:18:01.320> of<00:18:01.500> these<00:18:01.620> I<00:18:02.220> mean 00:18:02.270 --> 00:18:02.280 align:start position:0% maintainability of some of these I mean 00:18:02.280 --> 00:18:03.890 align:start position:0% maintainability of some of these I mean I<00:18:02.400> was<00:18:02.520> implementing<00:18:03.000> the<00:18:03.360> algorithm<00:18:03.720> as 00:18:03.890 --> 00:18:03.900 align:start position:0% I was implementing the algorithm as 00:18:03.900 --> 00:18:05.930 align:start position:0% I was implementing the algorithm as specified<00:18:04.320> and<00:18:04.919> sonar<00:18:05.340> said<00:18:05.520> that's<00:18:05.700> too 00:18:05.930 --> 00:18:05.940 align:start position:0% specified and sonar said that's too 00:18:05.940 --> 00:18:17.870 align:start position:0% specified and sonar said that's too complex<00:18:06.240> you<00:18:06.419> can't<00:18:06.600> do<00:18:06.780> it 00:18:17.870 --> 00:18:17.880 align:start position:0% 00:18:17.880 --> 00:18:19.130 align:start position:0% actually 00:18:19.130 --> 00:18:19.140 align:start position:0% actually 00:18:19.140 --> 00:18:21.529 align:start position:0% actually um it<00:18:19.860> was<00:18:20.100> it<00:18:20.220> was<00:18:20.400> the<00:18:20.520> same<00:18:20.820> uh<00:18:21.240> EIP 00:18:21.529 --> 00:18:21.539 align:start position:0% um it was it was the same uh EIP 00:18:21.539 --> 00:18:23.029 align:start position:0% um it was it was the same uh EIP transient<00:18:22.200> storage 00:18:23.029 --> 00:18:23.039 align:start position:0% transient storage 00:18:23.039 --> 00:18:24.830 align:start position:0% transient storage um so<00:18:23.220> without<00:18:23.460> maybe<00:18:23.760> just<00:18:24.059> Reviving<00:18:24.480> you 00:18:24.830 --> 00:18:24.840 align:start position:0% um so without maybe just Reviving you 00:18:24.840 --> 00:18:25.789 align:start position:0% um so without maybe just Reviving you know<00:18:24.900> everything<00:18:25.020> and<00:18:25.320> reiterating 00:18:25.789 --> 00:18:25.799 align:start position:0% know everything and reiterating 00:18:25.799 --> 00:18:27.529 align:start position:0% know everything and reiterating everything<00:18:26.100> there 00:18:27.529 --> 00:18:27.539 align:start position:0% everything there 00:18:27.539 --> 00:18:29.210 align:start position:0% everything there um it<00:18:27.900> just<00:18:28.080> just<00:18:28.260> kind<00:18:28.559> of<00:18:28.679> adding<00:18:28.860> on<00:18:28.980> a<00:18:29.160> few 00:18:29.210 --> 00:18:29.220 align:start position:0% um it just just kind of adding on a few 00:18:29.220 --> 00:18:30.650 align:start position:0% um it just just kind of adding on a few points<00:18:29.580> one 00:18:30.650 --> 00:18:30.660 align:start position:0% points one 00:18:30.660 --> 00:18:32.690 align:start position:0% points one um<00:18:30.780> you<00:18:31.080> know<00:18:31.140> right<00:18:31.380> now<00:18:31.559> some<00:18:32.220> of<00:18:32.400> the<00:18:32.460> higher 00:18:32.690 --> 00:18:32.700 align:start position:0% um you know right now some of the higher 00:18:32.700 --> 00:18:36.230 align:start position:0% um you know right now some of the higher level<00:18:32.820> oh<00:18:33.179> sorry<00:18:33.600> uh<00:18:34.620> background<00:18:35.039> uh<00:18:35.880> so<00:18:36.059> I'm 00:18:36.230 --> 00:18:36.240 align:start position:0% level oh sorry uh background uh so I'm 00:18:36.240 --> 00:18:37.490 align:start position:0% level oh sorry uh background uh so I'm actually<00:18:36.419> a<00:18:36.660> contributor<00:18:37.020> to<00:18:37.200> the<00:18:37.320> Hof 00:18:37.490 --> 00:18:37.500 align:start position:0% actually a contributor to the Hof 00:18:37.500 --> 00:18:39.110 align:start position:0% actually a contributor to the Hof language<00:18:37.860> which<00:18:38.100> is<00:18:38.220> a<00:18:38.340> low-level<00:18:38.700> uh 00:18:39.110 --> 00:18:39.120 align:start position:0% language which is a low-level uh 00:18:39.120 --> 00:18:41.630 align:start position:0% language which is a low-level uh Assembly<00:18:39.419> Language<00:18:39.660> and<00:18:40.140> then<00:18:40.260> uh<00:18:40.620> formerly 00:18:41.630 --> 00:18:41.640 align:start position:0% Assembly Language and then uh formerly 00:18:41.640 --> 00:18:44.330 align:start position:0% Assembly Language and then uh formerly um<00:18:41.700> I<00:18:42.000> worked<00:18:42.299> with<00:18:42.419> the<00:18:42.720> superfluid<00:18:43.260> protocol 00:18:44.330 --> 00:18:44.340 align:start position:0% um I worked with the superfluid protocol 00:18:44.340 --> 00:18:46.190 align:start position:0% um I worked with the superfluid protocol and<00:18:44.700> so<00:18:45.179> I<00:18:45.299> think<00:18:45.360> I<00:18:45.480> think<00:18:45.660> both<00:18:45.840> of<00:18:45.960> these 00:18:46.190 --> 00:18:46.200 align:start position:0% and so I think I think both of these 00:18:46.200 --> 00:18:49.010 align:start position:0% and so I think I think both of these could<00:18:46.679> benefit<00:18:47.039> from<00:18:47.760> transient<00:18:48.539> storage<00:18:48.780> so 00:18:49.010 --> 00:18:49.020 align:start position:0% could benefit from transient storage so 00:18:49.020 --> 00:18:50.750 align:start position:0% could benefit from transient storage so on<00:18:49.140> the<00:18:49.320> Huff<00:18:49.500> side<00:18:49.740> you<00:18:50.280> know<00:18:50.400> higher<00:18:50.640> level 00:18:50.750 --> 00:18:50.760 align:start position:0% on the Huff side you know higher level 00:18:50.760 --> 00:18:53.690 align:start position:0% on the Huff side you know higher level languages<00:18:51.120> like<00:18:51.419> solidity<00:18:52.080> and<00:18:52.620> Viper<00:18:53.400> you 00:18:53.690 --> 00:18:53.700 align:start position:0% languages like solidity and Viper you 00:18:53.700 --> 00:18:55.070 align:start position:0% languages like solidity and Viper you know<00:18:53.820> they<00:18:53.880> have<00:18:54.059> these<00:18:54.179> re-entrancy<00:18:54.720> locks 00:18:55.070 --> 00:18:55.080 align:start position:0% know they have these re-entrancy locks 00:18:55.080 --> 00:18:56.870 align:start position:0% know they have these re-entrancy locks or<00:18:55.200> modifiers<00:18:55.860> to<00:18:55.980> facilitate<00:18:56.400> re-entrancy 00:18:56.870 --> 00:18:56.880 align:start position:0% or modifiers to facilitate re-entrancy 00:18:56.880 --> 00:18:58.310 align:start position:0% or modifiers to facilitate re-entrancy locks<00:18:57.240> that<00:18:57.360> you<00:18:57.539> know<00:18:57.600> are<00:18:57.720> very<00:18:57.840> well<00:18:58.020> built 00:18:58.310 --> 00:18:58.320 align:start position:0% locks that you know are very well built 00:18:58.320 --> 00:19:00.049 align:start position:0% locks that you know are very well built and<00:18:58.740> it's<00:18:58.860> very<00:18:58.980> easy<00:18:59.160> to<00:18:59.340> build<00:18:59.460> this<00:18:59.640> in<00:18:59.820> a 00:19:00.049 --> 00:19:00.059 align:start position:0% and it's very easy to build this in a 00:19:00.059 --> 00:19:01.730 align:start position:0% and it's very easy to build this in a safe<00:19:00.179> and<00:19:00.299> secure<00:19:00.600> way<00:19:00.780> but<00:19:01.140> when<00:19:01.260> it<00:19:01.380> comes<00:19:01.559> to 00:19:01.730 --> 00:19:01.740 align:start position:0% safe and secure way but when it comes to 00:19:01.740 --> 00:19:03.350 align:start position:0% safe and secure way but when it comes to assembly<00:19:02.160> languages<00:19:02.520> this<00:19:02.820> is<00:19:02.940> actually<00:19:03.120> a 00:19:03.350 --> 00:19:03.360 align:start position:0% assembly languages this is actually a 00:19:03.360 --> 00:19:06.650 align:start position:0% assembly languages this is actually a problem<00:19:03.539> because<00:19:04.080> if<00:19:04.919> you<00:19:05.340> set<00:19:05.880> a<00:19:06.120> lock<00:19:06.299> in 00:19:06.650 --> 00:19:06.660 align:start position:0% problem because if you set a lock in 00:19:06.660 --> 00:19:08.210 align:start position:0% problem because if you set a lock in storage<00:19:06.840> and<00:19:07.080> you<00:19:07.260> don't<00:19:07.380> explicitly<00:19:07.860> free<00:19:08.039> it 00:19:08.210 --> 00:19:08.220 align:start position:0% storage and you don't explicitly free it 00:19:08.220 --> 00:19:09.529 align:start position:0% storage and you don't explicitly free it by<00:19:08.340> the<00:19:08.460> end<00:19:08.580> of<00:19:08.640> the<00:19:08.760> transaction<00:19:09.059> those<00:19:09.419> are 00:19:09.529 --> 00:19:09.539 align:start position:0% by the end of the transaction those are 00:19:09.539 --> 00:19:10.789 align:start position:0% by the end of the transaction those are now<00:19:09.660> bricked<00:19:10.080> which<00:19:10.260> obviously<00:19:10.500> you<00:19:10.620> should 00:19:10.789 --> 00:19:10.799 align:start position:0% now bricked which obviously you should 00:19:10.799 --> 00:19:12.590 align:start position:0% now bricked which obviously you should catch<00:19:11.039> this<00:19:11.160> and<00:19:11.340> unit<00:19:11.640> tests<00:19:12.059> right<00:19:12.240> but<00:19:12.480> it's 00:19:12.590 --> 00:19:12.600 align:start position:0% catch this and unit tests right but it's 00:19:12.600 --> 00:19:16.190 align:start position:0% catch this and unit tests right but it's just<00:19:12.840> it's<00:19:13.380> one<00:19:13.679> more<00:19:13.799> foot<00:19:14.039> gun<00:19:14.280> on<00:19:14.580> the<00:19:14.700> stack 00:19:16.190 --> 00:19:16.200 align:start position:0% just it's one more foot gun on the stack 00:19:16.200 --> 00:19:18.289 align:start position:0% just it's one more foot gun on the stack um sorry<00:19:16.860> to<00:19:17.039> interrupt<00:19:17.400> you<00:19:17.520> I<00:19:17.700> think<00:19:17.940> you 00:19:18.289 --> 00:19:18.299 align:start position:0% um sorry to interrupt you I think you 00:19:18.299 --> 00:19:21.110 align:start position:0% um sorry to interrupt you I think you kind<00:19:18.600> of<00:19:18.780> uh<00:19:19.380> capturing<00:19:20.220> the<00:19:20.400> the<00:19:20.700> governance 00:19:21.110 --> 00:19:21.120 align:start position:0% kind of uh capturing the the governance 00:19:21.120 --> 00:19:23.150 align:start position:0% kind of uh capturing the the governance process<00:19:21.539> right<00:19:21.840> now<00:19:22.020> because<00:19:22.679> we<00:19:22.980> already 00:19:23.150 --> 00:19:23.160 align:start position:0% process right now because we already 00:19:23.160 --> 00:19:25.610 align:start position:0% process right now because we already talked<00:19:23.760> about<00:19:23.820> the<00:19:24.179> CIP<00:19:24.539> and<00:19:24.840> now<00:19:25.020> rehashing 00:19:25.610 --> 00:19:25.620 align:start position:0% talked about the CIP and now rehashing 00:19:25.620 --> 00:19:29.510 align:start position:0% talked about the CIP and now rehashing the<00:19:26.360> discussionist<00:19:27.360> kind<00:19:27.960> of<00:19:28.080> I<00:19:28.919> think<00:19:29.100> not 00:19:29.510 --> 00:19:29.520 align:start position:0% the discussionist kind of I think not 00:19:29.520 --> 00:19:30.409 align:start position:0% the discussionist kind of I think not great 00:19:30.409 --> 00:19:30.419 align:start position:0% great 00:19:30.419 --> 00:19:32.630 align:start position:0% great uh<00:19:31.020> so<00:19:31.260> I<00:19:31.500> would 00:19:32.630 --> 00:19:32.640 align:start position:0% uh so I would 00:19:32.640 --> 00:19:35.990 align:start position:0% uh so I would if<00:19:33.120> the<00:19:33.360> if<00:19:33.900> I<00:19:34.620> would<00:19:35.039> rather<00:19:35.220> move<00:19:35.640> on<00:19:35.820> with 00:19:35.990 --> 00:19:36.000 align:start position:0% if the if I would rather move on with 00:19:36.000 --> 00:19:38.690 align:start position:0% if the if I would rather move on with the<00:19:36.179> next<00:19:36.299> Erp<00:19:36.780> and<00:19:37.140> uh<00:19:37.500> because<00:19:38.039> we<00:19:38.280> discussed 00:19:38.690 --> 00:19:38.700 align:start position:0% the next Erp and uh because we discussed 00:19:38.700 --> 00:19:42.010 align:start position:0% the next Erp and uh because we discussed this<00:19:38.820> one<00:19:38.940> already 00:19:42.010 --> 00:19:42.020 align:start position:0% 00:19:42.020 --> 00:19:44.690 align:start position:0% I<00:19:43.020> do<00:19:43.140> think<00:19:43.260> though<00:19:43.380> it<00:19:43.679> is<00:19:43.799> valuable<00:19:44.280> to<00:19:44.520> know 00:19:44.690 --> 00:19:44.700 align:start position:0% I do think though it is valuable to know 00:19:44.700 --> 00:19:46.810 align:start position:0% I do think though it is valuable to know that<00:19:44.880> like<00:19:45.059> low-level<00:19:45.480> languages<00:19:45.900> and<00:19:46.500> like 00:19:46.810 --> 00:19:46.820 align:start position:0% that like low-level languages and like 00:19:46.820 --> 00:19:49.850 align:start position:0% that like low-level languages and like projects<00:19:47.820> like<00:19:48.000> this<00:19:48.179> uh<00:19:48.900> if<00:19:49.200> you<00:19:49.320> can<00:19:49.500> like 00:19:49.850 --> 00:19:49.860 align:start position:0% projects like this uh if you can like 00:19:49.860 --> 00:19:52.010 align:start position:0% projects like this uh if you can like write<00:19:50.220> it<00:19:50.400> on<00:19:50.520> the<00:19:50.640> eat<00:19:50.820> magicians<00:19:51.419> post<00:19:51.720> or 00:19:52.010 --> 00:19:52.020 align:start position:0% write it on the eat magicians post or 00:19:52.020 --> 00:19:55.909 align:start position:0% write it on the eat magicians post or somewhere 00:19:55.909 --> 00:19:55.919 align:start position:0% 00:19:55.919 --> 00:19:57.710 align:start position:0% yeah<00:19:56.400> yeah<00:19:56.580> we<00:19:56.700> could<00:19:56.820> go<00:19:57.000> we're<00:19:57.360> not<00:19:57.539> going<00:19:57.660> to 00:19:57.710 --> 00:19:57.720 align:start position:0% yeah yeah we could go we're not going to 00:19:57.720 --> 00:19:59.390 align:start position:0% yeah yeah we could go we're not going to be<00:19:57.840> done<00:19:57.960> already<00:19:58.200> though 00:19:59.390 --> 00:19:59.400 align:start position:0% be done already though 00:19:59.400 --> 00:20:01.730 align:start position:0% be done already though yeah<00:19:59.820> sorry<00:20:00.120> so<00:20:00.360> I<00:20:00.720> was<00:20:00.780> gonna<00:20:00.960> say<00:20:01.020> yes<00:20:01.320> we 00:20:01.730 --> 00:20:01.740 align:start position:0% yeah sorry so I was gonna say yes we 00:20:01.740 --> 00:20:03.710 align:start position:0% yeah sorry so I was gonna say yes we probably<00:20:02.039> don't<00:20:02.220> have<00:20:02.340> time<00:20:02.520> to<00:20:02.640> rehash<00:20:03.120> it<00:20:03.299> if 00:20:03.710 --> 00:20:03.720 align:start position:0% probably don't have time to rehash it if 00:20:03.720 --> 00:20:05.630 align:start position:0% probably don't have time to rehash it if but<00:20:04.260> it<00:20:04.500> is<00:20:04.620> valuable<00:20:05.039> I<00:20:05.280> do<00:20:05.400> think<00:20:05.520> like 00:20:05.630 --> 00:20:05.640 align:start position:0% but it is valuable I do think like 00:20:05.640 --> 00:20:07.490 align:start position:0% but it is valuable I do think like putting<00:20:06.059> it<00:20:06.240> in<00:20:06.600> writing<00:20:06.960> on<00:20:07.260> the<00:20:07.380> East 00:20:07.490 --> 00:20:07.500 align:start position:0% putting it in writing on the East 00:20:07.500 --> 00:20:08.990 align:start position:0% putting it in writing on the East magician's<00:20:07.980> post<00:20:08.100> is<00:20:08.340> probably<00:20:08.520> good<00:20:08.820> to 00:20:08.990 --> 00:20:09.000 align:start position:0% magician's post is probably good to 00:20:09.000 --> 00:20:10.130 align:start position:0% magician's post is probably good to document 00:20:10.130 --> 00:20:10.140 align:start position:0% document 00:20:10.140 --> 00:20:13.130 align:start position:0% document um<00:20:10.260> yeah<00:20:10.440> sorry<00:20:10.880> uh<00:20:11.880> also<00:20:12.539> the<00:20:12.720> microphone 00:20:13.130 --> 00:20:13.140 align:start position:0% um yeah sorry uh also the microphone 00:20:13.140 --> 00:20:15.289 align:start position:0% um yeah sorry uh also the microphone don't<00:20:13.380> be<00:20:13.559> scared<00:20:13.919> it's<00:20:14.220> mainly<00:20:14.520> for<00:20:14.580> Direct 00:20:15.289 --> 00:20:15.299 align:start position:0% don't be scared it's mainly for Direct 00:20:15.299 --> 00:20:17.810 align:start position:0% don't be scared it's mainly for Direct ly okay<00:20:15.780> cool<00:20:16.380> cool<00:20:16.440> sorry<00:20:16.799> you<00:20:17.160> had<00:20:17.340> any<00:20:17.520> IP 00:20:17.810 --> 00:20:17.820 align:start position:0% ly okay cool cool sorry you had any IP 00:20:17.820 --> 00:20:19.850 align:start position:0% ly okay cool cool sorry you had any IP as<00:20:18.000> well<00:20:18.120> yes<00:20:18.539> okay 00:20:19.850 --> 00:20:19.860 align:start position:0% as well yes okay 00:20:19.860 --> 00:20:23.330 align:start position:0% as well yes okay um so<00:20:20.100> I'm<00:20:20.280> working<00:20:20.520> on<00:20:20.820> on<00:20:21.120> 5027 00:20:23.330 --> 00:20:23.340 align:start position:0% um so I'm working on on 5027 00:20:23.340 --> 00:20:25.029 align:start position:0% um so I'm working on on 5027 um and<00:20:23.580> also<00:20:23.820> another<00:20:23.940> VIP 00:20:25.029 --> 00:20:25.039 align:start position:0% um and also another VIP 00:20:25.039 --> 00:20:29.029 align:start position:0% um and also another VIP 5478<00:20:26.039> so<00:20:26.760> I<00:20:26.940> just<00:20:27.120> discussed<00:20:27.720> five<00:20:28.140> zeros<00:20:28.500> 27 00:20:29.029 --> 00:20:29.039 align:start position:0% 5478 so I just discussed five zeros 27 00:20:29.039 --> 00:20:31.669 align:start position:0% 5478 so I just discussed five zeros 27 first<00:20:29.340> uh<00:20:30.059> so<00:20:30.240> basically<00:20:30.600> it's<00:20:30.840> uh<00:20:31.200> aims<00:20:31.559> to 00:20:31.669 --> 00:20:31.679 align:start position:0% first uh so basically it's uh aims to 00:20:31.679 --> 00:20:33.770 align:start position:0% first uh so basically it's uh aims to remove<00:20:32.100> the<00:20:32.460> right<00:20:32.940> now<00:20:33.059> the<00:20:33.299> contract<00:20:33.600> limit 00:20:33.770 --> 00:20:33.780 align:start position:0% remove the right now the contract limit 00:20:33.780 --> 00:20:36.529 align:start position:0% remove the right now the contract limit as<00:20:34.080> 24<00:20:34.380> kilobytes<00:20:35.100> uh<00:20:35.940> that<00:20:36.179> it<00:20:36.360> was 00:20:36.529 --> 00:20:36.539 align:start position:0% as 24 kilobytes uh that it was 00:20:36.539 --> 00:20:41.570 align:start position:0% as 24 kilobytes uh that it was introduced<00:20:37.020> in<00:20:37.500> uh<00:20:38.179> EIP<00:20:39.179> 170. 00:20:41.570 --> 00:20:41.580 align:start position:0% introduced in uh EIP 170. 00:20:41.580 --> 00:20:43.730 align:start position:0% introduced in uh EIP 170. um so<00:20:42.059> uh<00:20:42.419> the<00:20:42.660> reason<00:20:42.780> is<00:20:43.080> like<00:20:43.320> I<00:20:43.500> think<00:20:43.620> the 00:20:43.730 --> 00:20:43.740 align:start position:0% um so uh the reason is like I think the 00:20:43.740 --> 00:20:45.350 align:start position:0% um so uh the reason is like I think the motivation<00:20:44.039> is<00:20:44.220> pretty<00:20:44.400> clear<00:20:44.700> that<00:20:45.000> a<00:20:45.179> lot<00:20:45.299> of 00:20:45.350 --> 00:20:45.360 align:start position:0% motivation is pretty clear that a lot of 00:20:45.360 --> 00:20:48.110 align:start position:0% motivation is pretty clear that a lot of people<00:20:45.480> complain<00:20:46.320> regarding<00:20:46.919> 24<00:20:47.400> kilobytes 00:20:48.110 --> 00:20:48.120 align:start position:0% people complain regarding 24 kilobytes 00:20:48.120 --> 00:20:50.990 align:start position:0% people complain regarding 24 kilobytes contract<00:20:48.840> size<00:20:49.080> especially<00:20:49.860> right<00:20:50.640> now<00:20:50.820> the 00:20:50.990 --> 00:20:51.000 align:start position:0% contract size especially right now the 00:20:51.000 --> 00:20:53.270 align:start position:0% contract size especially right now the contract<00:20:51.299> is<00:20:51.720> significantly<00:20:52.620> much<00:20:52.919> more 00:20:53.270 --> 00:20:53.280 align:start position:0% contract is significantly much more 00:20:53.280 --> 00:20:57.370 align:start position:0% contract is significantly much more complicated<00:20:53.760> when<00:20:54.360> EIP<00:20:55.460> 170<00:20:56.460> was<00:20:56.640> introduced 00:20:57.370 --> 00:20:57.380 align:start position:0% complicated when EIP 170 was introduced 00:20:57.380 --> 00:21:02.270 align:start position:0% complicated when EIP 170 was introduced so<00:20:58.380> the<00:20:58.559> major<00:20:58.679> concern<00:20:59.220> of<00:20:59.520> EIP<00:21:00.620> 170<00:21:01.620> is 00:21:02.270 --> 00:21:02.280 align:start position:0% so the major concern of EIP 170 is 00:21:02.280 --> 00:21:04.730 align:start position:0% so the major concern of EIP 170 is basically<00:21:02.640> DDOS<00:21:03.120> attack<00:21:03.419> uh<00:21:04.260> if<00:21:04.500> a<00:21:04.620> large 00:21:04.730 --> 00:21:04.740 align:start position:0% basically DDOS attack uh if a large 00:21:04.740 --> 00:21:07.370 align:start position:0% basically DDOS attack uh if a large counter<00:21:05.160> maybe<00:21:05.340> fix<00:21:05.520> 100<00:21:05.820> kilobytes<00:21:06.539> that<00:21:07.200> was 00:21:07.370 --> 00:21:07.380 align:start position:0% counter maybe fix 100 kilobytes that was 00:21:07.380 --> 00:21:10.250 align:start position:0% counter maybe fix 100 kilobytes that was deployed<00:21:07.919> on<00:21:08.100> the<00:21:08.220> ethereum<00:21:08.640> damn<00:21:08.940> uh<00:21:09.780> if<00:21:10.020> it's 00:21:10.250 --> 00:21:10.260 align:start position:0% deployed on the ethereum damn uh if it's 00:21:10.260 --> 00:21:12.470 align:start position:0% deployed on the ethereum damn uh if it's just<00:21:10.440> charging<00:21:10.919> using<00:21:11.280> a<00:21:11.400> flat<00:21:11.760> fee<00:21:12.000> like<00:21:12.299> for 00:21:12.470 --> 00:21:12.480 align:start position:0% just charging using a flat fee like for 00:21:12.480 --> 00:21:15.770 align:start position:0% just charging using a flat fee like for example<00:21:12.660> right<00:21:12.900> now<00:21:13.020> is<00:21:13.400> 2600<00:21:14.400> then<00:21:15.299> you<00:21:15.600> may 00:21:15.770 --> 00:21:15.780 align:start position:0% example right now is 2600 then you may 00:21:15.780 --> 00:21:18.770 align:start position:0% example right now is 2600 then you may uh<00:21:16.440> specifically<00:21:17.280> significantly<00:21:18.120> under 00:21:18.770 --> 00:21:18.780 align:start position:0% uh specifically significantly under 00:21:18.780 --> 00:21:23.090 align:start position:0% uh specifically significantly under charged<00:21:19.880> so<00:21:20.960> basically<00:21:21.960> the<00:21:22.260> idea<00:21:22.740> is<00:21:22.860> like 00:21:23.090 --> 00:21:23.100 align:start position:0% charged so basically the idea is like 00:21:23.100 --> 00:21:24.590 align:start position:0% charged so basically the idea is like right<00:21:23.280> now<00:21:23.400> the<00:21:23.520> solution<00:21:23.820> basically<00:21:24.240> is<00:21:24.360> that 00:21:24.590 --> 00:21:24.600 align:start position:0% right now the solution basically is that 00:21:24.600 --> 00:21:26.390 align:start position:0% right now the solution basically is that split<00:21:25.020> the<00:21:25.140> contract<00:21:25.500> to<00:21:25.679> multiple<00:21:25.980> contrast 00:21:26.390 --> 00:21:26.400 align:start position:0% split the contract to multiple contrast 00:21:26.400 --> 00:21:28.430 align:start position:0% split the contract to multiple contrast and<00:21:26.700> then<00:21:26.880> I<00:21:27.059> call<00:21:27.179> kind<00:21:27.780> of<00:21:27.960> like<00:21:28.020> chain<00:21:28.200> of 00:21:28.430 --> 00:21:28.440 align:start position:0% and then I call kind of like chain of 00:21:28.440 --> 00:21:30.230 align:start position:0% and then I call kind of like chain of contracts<00:21:29.039> so<00:21:29.460> they<00:21:29.640> can<00:21:29.760> retrieve<00:21:30.120> their 00:21:30.230 --> 00:21:30.240 align:start position:0% contracts so they can retrieve their 00:21:30.240 --> 00:21:33.590 align:start position:0% contracts so they can retrieve their data<00:21:30.659> but<00:21:31.620> it<00:21:32.159> basically<00:21:32.520> make<00:21:33.299> the<00:21:33.480> whole 00:21:33.590 --> 00:21:33.600 align:start position:0% data but it basically make the whole 00:21:33.600 --> 00:21:36.289 align:start position:0% data but it basically make the whole larger<00:21:33.900> much<00:21:34.200> more<00:21:34.440> complicated<00:21:34.880> so<00:21:35.880> the 00:21:36.289 --> 00:21:36.299 align:start position:0% larger much more complicated so the 00:21:36.299 --> 00:21:38.830 align:start position:0% larger much more complicated so the current<00:21:36.480> my<00:21:37.200> idea<00:21:37.559> of<00:21:37.679> solving<00:21:38.159> this<00:21:38.340> EIP 00:21:38.830 --> 00:21:38.840 align:start position:0% current my idea of solving this EIP 00:21:38.840 --> 00:21:42.169 align:start position:0% current my idea of solving this EIP basically<00:21:39.840> the<00:21:40.080> DDOS<00:21:40.559> tag<00:21:40.919> the<00:21:41.820> cup<00:21:41.940> two 00:21:42.169 --> 00:21:42.179 align:start position:0% basically the DDOS tag the cup two 00:21:42.179 --> 00:21:44.390 align:start position:0% basically the DDOS tag the cup two weights<00:21:42.539> one<00:21:42.720> is<00:21:42.840> basically<00:21:43.320> introduced<00:21:43.860> uh 00:21:44.390 --> 00:21:44.400 align:start position:0% weights one is basically introduced uh 00:21:44.400 --> 00:21:46.970 align:start position:0% weights one is basically introduced uh basically<00:21:44.880> a<00:21:45.539> contract<00:21:46.080> called<00:21:46.320> hash<00:21:46.679> versus 00:21:46.970 --> 00:21:46.980 align:start position:0% basically a contract called hash versus 00:21:46.980 --> 00:21:50.750 align:start position:0% basically a contract called hash versus the<00:21:47.460> to<00:21:47.760> the<00:21:48.000> country<00:21:48.240> size<00:21:48.659> so<00:21:49.620> when<00:21:49.919> we<00:21:50.340> call 00:21:50.750 --> 00:21:50.760 align:start position:0% the to the country size so when we call 00:21:50.760 --> 00:21:53.450 align:start position:0% the to the country size so when we call our<00:21:50.940> contract<00:21:51.299> then<00:21:51.840> we<00:21:52.020> immediately<00:21:52.380> to<00:21:53.159> know 00:21:53.450 --> 00:21:53.460 align:start position:0% our contract then we immediately to know 00:21:53.460 --> 00:21:55.549 align:start position:0% our contract then we immediately to know basically<00:21:54.299> the<00:21:54.419> size<00:21:54.600> because<00:21:54.840> size<00:21:55.140> is<00:21:55.380> very 00:21:55.549 --> 00:21:55.559 align:start position:0% basically the size because size is very 00:21:55.559 --> 00:21:58.190 align:start position:0% basically the size because size is very small<00:21:55.860> like<00:21:56.280> four<00:21:56.520> bytes<00:21:56.880> number<00:21:57.120> then<00:21:57.840> we<00:21:58.080> are 00:21:58.190 --> 00:21:58.200 align:start position:0% small like four bytes number then we are 00:21:58.200 --> 00:22:00.890 align:start position:0% small like four bytes number then we are able<00:21:58.380> to<00:21:58.500> pre-charge<00:21:59.159> according<00:22:00.059> to<00:22:00.240> for 00:22:00.890 --> 00:22:00.900 align:start position:0% able to pre-charge according to for 00:22:00.900 --> 00:22:02.750 align:start position:0% able to pre-charge according to for example<00:22:01.140> what<00:22:01.559> the<00:22:01.799> actual<00:22:02.159> size<00:22:02.460> of<00:22:02.640> the 00:22:02.750 --> 00:22:02.760 align:start position:0% example what the actual size of the 00:22:02.760 --> 00:22:05.029 align:start position:0% example what the actual size of the country<00:22:02.880> is<00:22:03.120> like<00:22:03.480> maybe<00:22:03.659> we<00:22:04.140> can<00:22:04.320> just<00:22:04.500> charge 00:22:05.029 --> 00:22:05.039 align:start position:0% country is like maybe we can just charge 00:22:05.039 --> 00:22:07.149 align:start position:0% country is like maybe we can just charge uh<00:22:05.940> charge<00:22:06.240> to 00:22:07.149 --> 00:22:07.159 align:start position:0% uh charge to 00:22:07.159 --> 00:22:11.450 align:start position:0% uh charge to 2614<00:22:08.159> per<00:22:08.760> 24<00:22:09.240> kilobytes<00:22:09.960> so<00:22:10.799> that<00:22:11.039> we<00:22:11.280> are 00:22:11.450 --> 00:22:11.460 align:start position:0% 2614 per 24 kilobytes so that we are 00:22:11.460 --> 00:22:14.029 align:start position:0% 2614 per 24 kilobytes so that we are able<00:22:11.640> to<00:22:11.700> basically<00:22:12.179> have<00:22:12.600> similar 00:22:14.029 --> 00:22:14.039 align:start position:0% able to basically have similar 00:22:14.039 --> 00:22:16.010 align:start position:0% able to basically have similar um right<00:22:14.280> now<00:22:14.400> gas<00:22:14.700> behavior<00:22:15.480> of<00:22:15.720> calling 00:22:16.010 --> 00:22:16.020 align:start position:0% um right now gas behavior of calling 00:22:16.020 --> 00:22:18.289 align:start position:0% um right now gas behavior of calling multiple<00:22:16.380> contracts<00:22:17.220> but<00:22:17.520> just<00:22:17.760> putting<00:22:18.179> it 00:22:18.289 --> 00:22:18.299 align:start position:0% multiple contracts but just putting it 00:22:18.299 --> 00:22:21.110 align:start position:0% multiple contracts but just putting it in<00:22:18.539> a<00:22:18.600> single<00:22:18.840> contract<00:22:19.400> so<00:22:20.400> this<00:22:20.520> is<00:22:20.700> one<00:22:20.820> idea 00:22:21.110 --> 00:22:21.120 align:start position:0% in a single contract so this is one idea 00:22:21.120 --> 00:22:23.930 align:start position:0% in a single contract so this is one idea another<00:22:21.419> idea<00:22:21.840> is<00:22:22.020> we<00:22:22.860> can<00:22:23.039> if<00:22:23.460> the<00:22:23.640> counter 00:22:23.930 --> 00:22:23.940 align:start position:0% another idea is we can if the counter 00:22:23.940 --> 00:22:26.750 align:start position:0% another idea is we can if the counter size<00:22:24.120> is<00:22:24.480> greater<00:22:24.840> than<00:22:24.960> 24<00:22:25.320> kilobytes<00:22:26.039> then 00:22:26.750 --> 00:22:26.760 align:start position:0% size is greater than 24 kilobytes then 00:22:26.760 --> 00:22:29.510 align:start position:0% size is greater than 24 kilobytes then we<00:22:26.940> are<00:22:27.120> able<00:22:27.360> to<00:22:27.480> append<00:22:28.380> a<00:22:28.860> size<00:22:29.159> together 00:22:29.510 --> 00:22:29.520 align:start position:0% we are able to append a size together 00:22:29.520 --> 00:22:33.049 align:start position:0% we are able to append a size together with<00:22:30.059> the<00:22:30.299> current<00:22:30.539> 24<00:22:31.140> kilobytes<00:22:31.919> and<00:22:32.820> then 00:22:33.049 --> 00:22:33.059 align:start position:0% with the current 24 kilobytes and then 00:22:33.059 --> 00:22:35.390 align:start position:0% with the current 24 kilobytes and then tells<00:22:33.780> the<00:22:33.900> what's<00:22:34.140> the<00:22:34.320> actual<00:22:34.679> size<00:22:34.919> it<00:22:35.280> is 00:22:35.390 --> 00:22:35.400 align:start position:0% tells the what's the actual size it is 00:22:35.400 --> 00:22:37.549 align:start position:0% tells the what's the actual size it is and<00:22:36.059> when<00:22:36.299> when<00:22:36.539> the<00:22:36.780> first<00:22:36.900> time<00:22:37.080> it<00:22:37.260> costs 00:22:37.549 --> 00:22:37.559 align:start position:0% and when when the first time it costs 00:22:37.559 --> 00:22:41.990 align:start position:0% and when when the first time it costs its<00:22:37.860> first<00:22:38.039> charge<00:22:38.299> 22<00:22:39.299> 600<00:22:40.140> about<00:22:41.100> the<00:22:41.760> the 00:22:41.990 --> 00:22:42.000 align:start position:0% its first charge 22 600 about the the 00:22:42.000 --> 00:22:44.330 align:start position:0% its first charge 22 600 about the the first<00:22:42.299> 24<00:22:42.780> kilobytes<00:22:43.500> and<00:22:43.919> then<00:22:44.159> the 00:22:44.330 --> 00:22:44.340 align:start position:0% first 24 kilobytes and then the 00:22:44.340 --> 00:22:46.370 align:start position:0% first 24 kilobytes and then the conscious<00:22:44.940> size<00:22:45.120> and<00:22:45.780> then<00:22:45.840> once<00:22:46.080> we<00:22:46.260> know 00:22:46.370 --> 00:22:46.380 align:start position:0% conscious size and then once we know 00:22:46.380 --> 00:22:48.130 align:start position:0% conscious size and then once we know country<00:22:46.620> size<00:22:46.919> then<00:22:47.159> we<00:22:47.340> can<00:22:47.520> further<00:22:47.820> charge 00:22:48.130 --> 00:22:48.140 align:start position:0% country size then we can further charge 00:22:48.140 --> 00:22:50.750 align:start position:0% country size then we can further charge the<00:22:49.140> corresponding<00:22:49.679> the<00:22:49.919> rest<00:22:50.039> of<00:22:50.280> contracts 00:22:50.750 --> 00:22:50.760 align:start position:0% the corresponding the rest of contracts 00:22:50.760 --> 00:22:52.070 align:start position:0% the corresponding the rest of contracts and<00:22:51.000> then<00:22:51.120> put<00:22:51.299> in<00:22:51.480> the<00:22:51.600> memory<00:22:51.780> and<00:22:51.960> then 00:22:52.070 --> 00:22:52.080 align:start position:0% and then put in the memory and then 00:22:52.080 --> 00:22:54.110 align:start position:0% and then put in the memory and then execute<00:22:52.559> so<00:22:53.039> basically<00:22:53.340> this<00:22:53.580> is<00:22:53.640> the<00:22:53.820> basic 00:22:54.110 --> 00:22:54.120 align:start position:0% execute so basically this is the basic 00:22:54.120 --> 00:22:57.470 align:start position:0% execute so basically this is the basic idea<00:22:54.500> uh<00:22:55.500> when<00:22:55.740> it<00:22:56.039> takes<00:22:56.520> a 00:22:57.470 --> 00:22:57.480 align:start position:0% idea uh when it takes a 00:22:57.480 --> 00:23:00.590 align:start position:0% idea uh when it takes a explore<00:22:58.440> the<00:22:58.620> ebm<00:22:59.100> code<00:22:59.340> and<00:22:59.940> also<00:23:00.179> I<00:23:00.299> have<00:23:00.480> a 00:23:00.590 --> 00:23:00.600 align:start position:0% explore the ebm code and also I have a 00:23:00.600 --> 00:23:03.110 align:start position:0% explore the ebm code and also I have a single<00:23:00.960> basic<00:23:01.559> implementation<00:23:02.220> together 00:23:03.110 --> 00:23:03.120 align:start position:0% single basic implementation together 00:23:03.120 --> 00:23:05.990 align:start position:0% single basic implementation together with<00:23:03.480> some<00:23:03.900> concerns<00:23:04.679> of<00:23:04.860> addressing<00:23:05.340> one<00:23:05.700> and 00:23:05.990 --> 00:23:06.000 align:start position:0% with some concerns of addressing one and 00:23:06.000 --> 00:23:09.830 align:start position:0% with some concerns of addressing one and code<00:23:06.320> storage<00:23:07.700> and<00:23:08.700> also<00:23:09.059> be<00:23:09.299> concerned<00:23:09.600> of 00:23:09.830 --> 00:23:09.840 align:start position:0% code storage and also be concerned of 00:23:09.840 --> 00:23:12.169 align:start position:0% code storage and also be concerned of the<00:23:09.960> P2P<00:23:10.440> package<00:23:11.039> size<00:23:11.220> because<00:23:11.580> right<00:23:12.000> now 00:23:12.169 --> 00:23:12.179 align:start position:0% the P2P package size because right now 00:23:12.179 --> 00:23:15.049 align:start position:0% the P2P package size because right now we<00:23:13.140> have<00:23:13.260> a<00:23:13.380> limitation<00:23:13.799> on<00:23:14.039> the<00:23:14.159> P2P<00:23:14.520> packet 00:23:15.049 --> 00:23:15.059 align:start position:0% we have a limitation on the P2P packet 00:23:15.059 --> 00:23:19.029 align:start position:0% we have a limitation on the P2P packet size<00:23:15.260> but<00:23:16.260> with<00:23:16.559> for<00:23:16.980> example<00:23:17.280> 50<00:23:17.700> million<00:23:18.360> gas 00:23:19.029 --> 00:23:19.039 align:start position:0% size but with for example 50 million gas 00:23:19.039 --> 00:23:22.850 align:start position:0% size but with for example 50 million gas block<00:23:20.039> gas<00:23:20.280> limit<00:23:20.880> divided<00:23:21.600> by<00:23:21.780> 200<00:23:22.200> gas<00:23:22.559> price 00:23:22.850 --> 00:23:22.860 align:start position:0% block gas limit divided by 200 gas price 00:23:22.860 --> 00:23:25.730 align:start position:0% block gas limit divided by 200 gas price per<00:23:23.400> byte<00:23:23.820> and<00:23:24.419> so<00:23:24.659> the<00:23:24.780> contract<00:23:25.140> limit<00:23:25.500> size 00:23:25.730 --> 00:23:25.740 align:start position:0% per byte and so the contract limit size 00:23:25.740 --> 00:23:28.010 align:start position:0% per byte and so the contract limit size actually<00:23:26.220> is<00:23:26.460> essentially<00:23:26.880> limited<00:23:27.299> to<00:23:27.360> 250 00:23:28.010 --> 00:23:28.020 align:start position:0% actually is essentially limited to 250 00:23:28.020 --> 00:23:31.669 align:start position:0% actually is essentially limited to 250 50<00:23:28.740> kilobytes<00:23:29.600> so<00:23:30.600> right<00:23:30.780> now<00:23:30.960> that's<00:23:31.200> still 00:23:31.669 --> 00:23:31.679 align:start position:0% 50 kilobytes so right now that's still 00:23:31.679 --> 00:23:34.430 align:start position:0% 50 kilobytes so right now that's still fit<00:23:31.919> into<00:23:32.039> the<00:23:32.280> P2P<00:23:32.700> package<00:23:33.200> so<00:23:34.200> the 00:23:34.430 --> 00:23:34.440 align:start position:0% fit into the P2P package so the 00:23:34.440 --> 00:23:36.289 align:start position:0% fit into the P2P package so the basically<00:23:34.919> there's<00:23:35.159> a<00:23:35.400> couple<00:23:35.580> of<00:23:35.700> concerns 00:23:36.289 --> 00:23:36.299 align:start position:0% basically there's a couple of concerns 00:23:36.299 --> 00:23:38.690 align:start position:0% basically there's a couple of concerns that<00:23:36.539> regarding<00:23:37.080> this<00:23:37.260> if<00:23:37.860> we<00:23:38.039> are<00:23:38.220> able<00:23:38.460> to 00:23:38.690 --> 00:23:38.700 align:start position:0% that regarding this if we are able to 00:23:38.700 --> 00:23:42.950 align:start position:0% that regarding this if we are able to remove<00:23:39.240> this<00:23:39.659> limit<00:23:39.960> yeah<00:23:40.620> happy<00:23:41.100> to 00:23:42.950 --> 00:23:42.960 align:start position:0% remove this limit yeah happy to 00:23:42.960 --> 00:23:47.330 align:start position:0% remove this limit yeah happy to so<00:23:43.799> um<00:23:43.799> there's<00:23:44.039> also<00:23:44.280> EIP<00:23:44.659> 3970<00:23:45.659> not<00:23:45.840> 3978 00:23:47.330 --> 00:23:47.340 align:start position:0% so um there's also EIP 3970 not 3978 00:23:47.340 --> 00:23:49.430 align:start position:0% so um there's also EIP 3970 not 3978 um 3860<00:23:48.059> which<00:23:48.299> is<00:23:48.419> to<00:23:48.600> limit<00:23:48.720> meter<00:23:49.140> and<00:23:49.260> net 00:23:49.430 --> 00:23:49.440 align:start position:0% um 3860 which is to limit meter and net 00:23:49.440 --> 00:23:50.510 align:start position:0% um 3860 which is to limit meter and net code<00:23:49.679> which<00:23:49.919> is<00:23:49.980> like<00:23:50.100> we<00:23:50.280> got<00:23:50.340> two 00:23:50.510 --> 00:23:50.520 align:start position:0% code which is like we got two 00:23:50.520 --> 00:23:52.549 align:start position:0% code which is like we got two conflicting<00:23:50.940> eips 00:23:52.549 --> 00:23:52.559 align:start position:0% conflicting eips 00:23:52.559 --> 00:23:56.090 align:start position:0% conflicting eips um<00:23:52.620> so<00:23:53.460> I'm<00:23:54.360> not<00:23:54.659> opposed<00:23:55.200> to<00:23:55.440> changing<00:23:55.919> the 00:23:56.090 --> 00:23:56.100 align:start position:0% um so I'm not opposed to changing the 00:23:56.100 --> 00:23:57.710 align:start position:0% um so I'm not opposed to changing the limit<00:23:56.280> but<00:23:56.640> completely<00:23:56.940> unlimiting<00:23:57.480> it<00:23:57.539> I 00:23:57.710 --> 00:23:57.720 align:start position:0% limit but completely unlimiting it I 00:23:57.720 --> 00:23:59.029 align:start position:0% limit but completely unlimiting it I think<00:23:57.780> it<00:23:57.900> has<00:23:58.020> issues 00:23:59.029 --> 00:23:59.039 align:start position:0% think it has issues 00:23:59.039 --> 00:24:00.529 align:start position:0% think it has issues um I<00:23:59.580> think<00:23:59.640> it's<00:23:59.760> Martin<00:24:00.000> that<00:24:00.240> has<00:24:00.419> some 00:24:00.529 --> 00:24:00.539 align:start position:0% um I think it's Martin that has some 00:24:00.539 --> 00:24:03.110 align:start position:0% um I think it's Martin that has some really<00:24:00.720> glorious<00:24:01.200> code<00:24:01.559> that<00:24:02.100> shows<00:24:02.940> the 00:24:03.110 --> 00:24:03.120 align:start position:0% really glorious code that shows the 00:24:03.120 --> 00:24:04.310 align:start position:0% really glorious code that shows the performance<00:24:03.419> problems<00:24:03.780> with<00:24:04.020> the<00:24:04.200> current 00:24:04.310 --> 00:24:04.320 align:start position:0% performance problems with the current 00:24:04.320 --> 00:24:07.010 align:start position:0% performance problems with the current jump<00:24:04.620> analysis<00:24:05.220> on<00:24:06.179> on 00:24:07.010 --> 00:24:07.020 align:start position:0% jump analysis on on 00:24:07.020 --> 00:24:10.070 align:start position:0% jump analysis on on um<00:24:07.140> the<00:24:07.740> Legacy<00:24:08.159> formats<00:24:08.940> but<00:24:09.720> another<00:24:09.840> thing 00:24:10.070 --> 00:24:10.080 align:start position:0% um the Legacy formats but another thing 00:24:10.080 --> 00:24:11.570 align:start position:0% um the Legacy formats but another thing to<00:24:10.260> consider<00:24:10.559> is<00:24:10.679> what<00:24:10.860> if<00:24:11.039> we<00:24:11.159> change<00:24:11.340> the 00:24:11.570 --> 00:24:11.580 align:start position:0% to consider is what if we change the 00:24:11.580 --> 00:24:14.450 align:start position:0% to consider is what if we change the code<00:24:11.760> to<00:24:12.299> required<00:24:13.140> to<00:24:13.200> be<00:24:13.380> done<00:24:13.500> in<00:24:13.860> the<00:24:14.100> eof 00:24:14.450 --> 00:24:14.460 align:start position:0% code to required to be done in the eof 00:24:14.460 --> 00:24:17.029 align:start position:0% code to required to be done in the eof and<00:24:15.419> it's<00:24:15.600> the<00:24:15.840> code<00:24:16.020> limit<00:24:16.260> it<00:24:16.559> applies<00:24:16.919> to 00:24:17.029 --> 00:24:17.039 align:start position:0% and it's the code limit it applies to 00:24:17.039 --> 00:24:19.490 align:start position:0% and it's the code limit it applies to and<00:24:17.820> then<00:24:18.120> we<00:24:18.299> could<00:24:18.419> reconsider<00:24:19.020> how<00:24:19.380> much 00:24:19.490 --> 00:24:19.500 align:start position:0% and then we could reconsider how much 00:24:19.500 --> 00:24:21.529 align:start position:0% and then we could reconsider how much data<00:24:19.919> you<00:24:20.039> could<00:24:20.159> bring<00:24:20.340> in<00:24:20.580> that<00:24:21.179> is<00:24:21.360> not 00:24:21.529 --> 00:24:21.539 align:start position:0% data you could bring in that is not 00:24:21.539 --> 00:24:22.490 align:start position:0% data you could bring in that is not subject<00:24:21.840> to<00:24:21.960> this<00:24:22.080> because<00:24:22.200> you're<00:24:22.380> not 00:24:22.490 --> 00:24:22.500 align:start position:0% subject to this because you're not 00:24:22.500 --> 00:24:23.990 align:start position:0% subject to this because you're not supposed<00:24:22.620> to<00:24:22.740> do<00:24:22.980> the<00:24:23.100> jump<00:24:23.220> analysis<00:24:23.700> on<00:24:23.880> the 00:24:23.990 --> 00:24:24.000 align:start position:0% supposed to do the jump analysis on the 00:24:24.000 --> 00:24:25.730 align:start position:0% supposed to do the jump analysis on the data<00:24:24.240> the<00:24:24.539> jump<00:24:24.720> analysis<00:24:25.260> is<00:24:25.380> different<00:24:25.559> in 00:24:25.730 --> 00:24:25.740 align:start position:0% data the jump analysis is different in 00:24:25.740 --> 00:24:28.970 align:start position:0% data the jump analysis is different in eof2<00:24:26.340> there's<00:24:26.940> not<00:24:27.179> the<00:24:27.360> same<00:24:27.480> risks<00:24:27.900> but<00:24:28.799> then 00:24:28.970 --> 00:24:28.980 align:start position:0% eof2 there's not the same risks but then 00:24:28.980 --> 00:24:30.350 align:start position:0% eof2 there's not the same risks but then as<00:24:29.220> you<00:24:29.400> mentioned<00:24:29.580> you<00:24:29.700> get<00:24:29.820> into<00:24:29.940> the<00:24:30.059> issues 00:24:30.350 --> 00:24:30.360 align:start position:0% as you mentioned you get into the issues 00:24:30.360 --> 00:24:32.210 align:start position:0% as you mentioned you get into the issues of<00:24:30.539> how<00:24:31.320> does<00:24:31.440> it<00:24:31.620> impact<00:24:31.860> the<00:24:31.980> storage 00:24:32.210 --> 00:24:32.220 align:start position:0% of how does it impact the storage 00:24:32.220 --> 00:24:34.490 align:start position:0% of how does it impact the storage bringing<00:24:32.760> out<00:24:32.940> you<00:24:33.179> know<00:24:33.320> kilobyte<00:24:34.320> not 00:24:34.490 --> 00:24:34.500 align:start position:0% bringing out you know kilobyte not 00:24:34.500 --> 00:24:37.250 align:start position:0% bringing out you know kilobyte not kilobyte<00:24:34.980> megabyte<00:24:35.520> codes<00:24:36.120> code<00:24:36.720> out<00:24:37.020> of<00:24:37.140> the 00:24:37.250 --> 00:24:37.260 align:start position:0% kilobyte megabyte codes code out of the 00:24:37.260 --> 00:24:38.810 align:start position:0% kilobyte megabyte codes code out of the storage 00:24:38.810 --> 00:24:38.820 align:start position:0% storage 00:24:38.820 --> 00:24:40.250 align:start position:0% storage um and 00:24:40.250 --> 00:24:40.260 align:start position:0% um and 00:24:40.260 --> 00:24:42.770 align:start position:0% um and yeah<00:24:40.860> I<00:24:41.159> I<00:24:41.400> think<00:24:41.580> the<00:24:41.760> unlimiting<00:24:42.299> is<00:24:42.600> going 00:24:42.770 --> 00:24:42.780 align:start position:0% yeah I I think the unlimiting is going 00:24:42.780 --> 00:24:45.409 align:start position:0% yeah I I think the unlimiting is going to<00:24:42.900> be<00:24:42.960> a<00:24:43.200> hard<00:24:43.320> sell<00:24:43.559> I<00:24:43.919> think<00:24:44.179> changing<00:24:45.179> the 00:24:45.409 --> 00:24:45.419 align:start position:0% to be a hard sell I think changing the 00:24:45.419 --> 00:24:46.789 align:start position:0% to be a hard sell I think changing the limit<00:24:45.539> I<00:24:45.840> think<00:24:45.900> is<00:24:46.020> going<00:24:46.260> to<00:24:46.320> be<00:24:46.380> an<00:24:46.500> easier 00:24:46.789 --> 00:24:46.799 align:start position:0% limit I think is going to be an easier 00:24:46.799 --> 00:24:50.630 align:start position:0% limit I think is going to be an easier sell 00:24:50.630 --> 00:24:50.640 align:start position:0% 00:24:50.640 --> 00:24:52.310 align:start position:0% I<00:24:50.880> guess<00:24:51.059> my<00:24:51.299> question<00:24:51.419> is<00:24:51.659> kind<00:24:51.900> of<00:24:51.960> similar 00:24:52.310 --> 00:24:52.320 align:start position:0% I guess my question is kind of similar 00:24:52.320 --> 00:24:53.870 align:start position:0% I guess my question is kind of similar to<00:24:52.440> this<00:24:52.679> that<00:24:52.980> uh 00:24:53.870 --> 00:24:53.880 align:start position:0% to this that uh 00:24:53.880 --> 00:24:56.390 align:start position:0% to this that uh saying<00:24:54.360> that<00:24:54.480> 24K<00:24:55.020> is<00:24:55.200> too<00:24:55.380> small 00:24:56.390 --> 00:24:56.400 align:start position:0% saying that 24K is too small 00:24:56.400 --> 00:24:58.130 align:start position:0% saying that 24K is too small I<00:24:56.820> can<00:24:56.940> definitely<00:24:57.240> accept<00:24:57.480> that<00:24:57.780> I<00:24:58.020> think 00:24:58.130 --> 00:24:58.140 align:start position:0% I can definitely accept that I think 00:24:58.140 --> 00:25:00.350 align:start position:0% I can definitely accept that I think that's<00:24:58.260> a<00:24:58.440> valid<00:24:58.679> concern<00:24:59.039> my<00:24:59.940> question<00:25:00.059> is 00:25:00.350 --> 00:25:00.360 align:start position:0% that's a valid concern my question is 00:25:00.360 --> 00:25:03.470 align:start position:0% that's a valid concern my question is what<00:25:00.720> is<00:25:01.020> reasonable<00:25:01.620> because<00:25:02.159> if<00:25:02.640> uh<00:25:02.880> if<00:25:03.360> you 00:25:03.470 --> 00:25:03.480 align:start position:0% what is reasonable because if uh if you 00:25:03.480 --> 00:25:05.029 align:start position:0% what is reasonable because if uh if you go<00:25:03.600> towards<00:25:03.960> saying<00:25:04.320> that<00:25:04.380> well<00:25:04.559> it<00:25:04.799> should<00:25:04.980> be 00:25:05.029 --> 00:25:05.039 align:start position:0% go towards saying that well it should be 00:25:05.039 --> 00:25:06.830 align:start position:0% go towards saying that well it should be arbitrary<00:25:05.460> large<00:25:05.700> and<00:25:05.880> it<00:25:06.120> will<00:25:06.240> get<00:25:06.419> so 00:25:06.830 --> 00:25:06.840 align:start position:0% arbitrary large and it will get so 00:25:06.840 --> 00:25:08.510 align:start position:0% arbitrary large and it will get so complicated<00:25:07.200> that<00:25:07.500> it<00:25:07.799> definitely<00:25:08.159> won't 00:25:08.510 --> 00:25:08.520 align:start position:0% complicated that it definitely won't 00:25:08.520 --> 00:25:11.210 align:start position:0% complicated that it definitely won't ship<00:25:09.059> but<00:25:09.960> for<00:25:10.140> example<00:25:10.380> saying<00:25:10.799> that<00:25:10.980> well 00:25:11.210 --> 00:25:11.220 align:start position:0% ship but for example saying that well 00:25:11.220 --> 00:25:15.590 align:start position:0% ship but for example saying that well let's<00:25:11.760> raise<00:25:12.000> it<00:25:12.240> from<00:25:12.419> from<00:25:12.659> 24<00:25:13.020> to<00:25:13.559> item<00:25:14.600> 64. 00:25:15.590 --> 00:25:15.600 align:start position:0% let's raise it from from 24 to item 64. 00:25:15.600 --> 00:25:17.690 align:start position:0% let's raise it from from 24 to item 64. that's<00:25:15.960> that<00:25:16.500> thing<00:25:16.740> can<00:25:16.919> be<00:25:17.100> analyzed<00:25:17.520> there 00:25:17.690 --> 00:25:17.700 align:start position:0% that's that thing can be analyzed there 00:25:17.700 --> 00:25:19.669 align:start position:0% that's that thing can be analyzed there we<00:25:17.940> can<00:25:18.059> put<00:25:18.240> the<00:25:18.360> number<00:25:18.539> on<00:25:18.780> it<00:25:18.960> it<00:25:19.500> doesn't 00:25:19.669 --> 00:25:19.679 align:start position:0% we can put the number on it it doesn't 00:25:19.679 --> 00:25:21.110 align:start position:0% we can put the number on it it doesn't mean<00:25:19.860> that<00:25:20.039> it<00:25:20.220> won't<00:25:20.340> require<00:25:20.580> additional 00:25:21.110 --> 00:25:21.120 align:start position:0% mean that it won't require additional 00:25:21.120 --> 00:25:23.930 align:start position:0% mean that it won't require additional changes<00:25:21.480> but<00:25:21.780> it's<00:25:22.080> relatively<00:25:23.039> simple<00:25:23.460> to 00:25:23.930 --> 00:25:23.940 align:start position:0% changes but it's relatively simple to 00:25:23.940 --> 00:25:26.029 align:start position:0% changes but it's relatively simple to understand<00:25:24.059> the<00:25:24.480> implications<00:25:24.960> the<00:25:25.860> moment 00:25:26.029 --> 00:25:26.039 align:start position:0% understand the implications the moment 00:25:26.039 --> 00:25:27.890 align:start position:0% understand the implications the moment you<00:25:26.159> introduce<00:25:26.520> these<00:25:26.880> Dynamic<00:25:27.240> changes<00:25:27.659> I 00:25:27.890 --> 00:25:27.900 align:start position:0% you introduce these Dynamic changes I 00:25:27.900 --> 00:25:30.169 align:start position:0% you introduce these Dynamic changes I think<00:25:28.020> that's<00:25:28.440> that's<00:25:28.919> not<00:25:29.279> really<00:25:29.580> Gonna<00:25:29.820> Fly 00:25:30.169 --> 00:25:30.179 align:start position:0% think that's that's not really Gonna Fly 00:25:30.179 --> 00:25:32.510 align:start position:0% think that's that's not really Gonna Fly it's<00:25:30.480> going<00:25:30.659> to<00:25:30.779> be<00:25:30.900> too<00:25:31.140> complicated<00:25:31.620> in<00:25:32.400> my 00:25:32.510 --> 00:25:32.520 align:start position:0% it's going to be too complicated in my 00:25:32.520 --> 00:25:34.190 align:start position:0% it's going to be too complicated in my opinion 00:25:34.190 --> 00:25:34.200 align:start position:0% opinion 00:25:34.200 --> 00:25:35.450 align:start position:0% opinion um yeah 00:25:35.450 --> 00:25:35.460 align:start position:0% um yeah 00:25:35.460 --> 00:25:38.149 align:start position:0% um yeah um<00:25:35.580> so<00:25:36.059> because<00:25:36.840> I<00:25:37.080> do<00:25:37.200> some<00:25:37.380> experiment<00:25:37.860> and 00:25:38.149 --> 00:25:38.159 align:start position:0% um so because I do some experiment and 00:25:38.159 --> 00:25:41.090 align:start position:0% um so because I do some experiment and and<00:25:38.520> using<00:25:39.480> a<00:25:39.659> code<00:25:39.900> so<00:25:40.140> right<00:25:40.380> now<00:25:40.559> I<00:25:40.860> feel 00:25:41.090 --> 00:25:41.100 align:start position:0% and using a code so right now I feel 00:25:41.100 --> 00:25:43.010 align:start position:0% and using a code so right now I feel like<00:25:41.760> pick<00:25:42.000> some<00:25:42.240> instant<00:25:42.539> synchronization 00:25:43.010 --> 00:25:43.020 align:start position:0% like pick some instant synchronization 00:25:43.020 --> 00:25:45.769 align:start position:0% like pick some instant synchronization and<00:25:43.200> put<00:25:43.320> out<00:25:43.620> some<00:25:43.799> deploying<00:25:44.400> a<00:25:44.580> lot<00:25:44.760> of<00:25:44.880> uh 00:25:45.769 --> 00:25:45.779 align:start position:0% and put out some deploying a lot of uh 00:25:45.779 --> 00:25:47.990 align:start position:0% and put out some deploying a lot of uh like<00:25:46.020> some<00:25:46.320> 200<00:25:46.679> kilobytes<00:25:47.220> of<00:25:47.400> contract<00:25:47.880> on 00:25:47.990 --> 00:25:48.000 align:start position:0% like some 200 kilobytes of contract on 00:25:48.000 --> 00:25:50.330 align:start position:0% like some 200 kilobytes of contract on top<00:25:48.120> there<00:25:48.360> uh<00:25:49.200> it<00:25:49.380> looks<00:25:49.620> like<00:25:49.679> everything<00:25:49.919> is 00:25:50.330 --> 00:25:50.340 align:start position:0% top there uh it looks like everything is 00:25:50.340 --> 00:25:52.789 align:start position:0% top there uh it looks like everything is working<00:25:50.760> fine<00:25:51.000> on<00:25:51.240> my<00:25:51.360> test<00:25:51.480> net 00:25:52.789 --> 00:25:52.799 align:start position:0% working fine on my test net 00:25:52.799 --> 00:25:55.130 align:start position:0% working fine on my test net um so<00:25:53.279> uh<00:25:53.520> has<00:25:53.700> been<00:25:53.880> running<00:25:54.059> for 00:25:55.130 --> 00:25:55.140 align:start position:0% um so uh has been running for 00:25:55.140 --> 00:25:57.169 align:start position:0% um so uh has been running for um more<00:25:55.500> than<00:25:55.559> half<00:25:55.799> years 00:25:57.169 --> 00:25:57.179 align:start position:0% um more than half years 00:25:57.179 --> 00:25:57.769 align:start position:0% um more than half years um 00:25:57.769 --> 00:25:57.779 align:start position:0% um 00:25:57.779 --> 00:25:59.570 align:start position:0% um yeah<00:25:58.320> especially<00:25:58.799> like<00:25:59.039> right<00:25:59.279> now<00:25:59.400> in<00:25:59.520> the 00:25:59.570 --> 00:25:59.580 align:start position:0% yeah especially like right now in the 00:25:59.580 --> 00:26:01.490 align:start position:0% yeah especially like right now in the gas<00:25:59.760> regarding<00:26:00.360> the<00:26:00.480> jump<00:26:00.600> analysis<00:26:01.140> right 00:26:01.490 --> 00:26:01.500 align:start position:0% gas regarding the jump analysis right 00:26:01.500 --> 00:26:03.789 align:start position:0% gas regarding the jump analysis right now<00:26:01.620> the<00:26:01.740> glass<00:26:01.919> metering<00:26:02.520> is<00:26:02.700> charged<00:26:03.240> for 00:26:03.789 --> 00:26:03.799 align:start position:0% now the glass metering is charged for 00:26:03.799 --> 00:26:07.430 align:start position:0% now the glass metering is charged for 2600<00:26:04.799> per<00:26:05.279> 24<00:26:05.700> kilobytes<00:26:06.419> which<00:26:06.900> essentially 00:26:07.430 --> 00:26:07.440 align:start position:0% 2600 per 24 kilobytes which essentially 00:26:07.440 --> 00:26:10.789 align:start position:0% 2600 per 24 kilobytes which essentially I<00:26:07.860> think<00:26:07.980> the<00:26:08.159> same<00:26:08.340> is<00:26:09.000> equivalent<00:26:09.840> to<00:26:09.960> I<00:26:10.679> call 00:26:10.789 --> 00:26:10.799 align:start position:0% I think the same is equivalent to I call 00:26:10.799 --> 00:26:12.529 align:start position:0% I think the same is equivalent to I call this<00:26:10.980> contract<00:26:11.400> and<00:26:11.580> call<00:26:11.700> another<00:26:11.940> one<00:26:12.179> this 00:26:12.529 --> 00:26:12.539 align:start position:0% this contract and call another one this 00:26:12.539 --> 00:26:14.630 align:start position:0% this contract and call another one this Country<00:26:12.779> Corner<00:26:13.200> another<00:26:13.380> one<00:26:13.559> so<00:26:14.279> basically 00:26:14.630 --> 00:26:14.640 align:start position:0% Country Corner another one so basically 00:26:14.640 --> 00:26:16.789 align:start position:0% Country Corner another one so basically I<00:26:14.880> charge<00:26:15.120> this<00:26:15.480> the<00:26:15.779> chain<00:26:15.960> of<00:26:16.260> this<00:26:16.380> calling 00:26:16.789 --> 00:26:16.799 align:start position:0% I charge this the chain of this calling 00:26:16.799 --> 00:26:18.950 align:start position:0% I charge this the chain of this calling to<00:26:16.980> in<00:26:17.100> a<00:26:17.279> single<00:26:17.520> but<00:26:17.700> you<00:26:18.000> see<00:26:18.539> using<00:26:18.840> a 00:26:18.950 --> 00:26:18.960 align:start position:0% to in a single but you see using a 00:26:18.960 --> 00:26:22.370 align:start position:0% to in a single but you see using a single<00:26:19.320> payment<00:26:19.980> so<00:26:20.520> so<00:26:20.820> if<00:26:21.240> we<00:26:21.480> tie<00:26:21.720> this<00:26:22.020> to 00:26:22.370 --> 00:26:22.380 align:start position:0% single payment so so if we tie this to 00:26:22.380 --> 00:26:23.570 align:start position:0% single payment so so if we tie this to eof 00:26:23.570 --> 00:26:23.580 align:start position:0% eof 00:26:23.580 --> 00:26:24.950 align:start position:0% eof um<00:26:23.640> you<00:26:23.760> can<00:26:23.880> have<00:26:24.000> larger<00:26:24.240> contracts<00:26:24.659> if<00:26:24.840> you 00:26:24.950 --> 00:26:24.960 align:start position:0% um you can have larger contracts if you 00:26:24.960 --> 00:26:26.630 align:start position:0% um you can have larger contracts if you do<00:26:25.080> it<00:26:25.140> in<00:26:25.260> an<00:26:25.320> eof<00:26:25.559> container<00:26:26.100> we 00:26:26.630 --> 00:26:26.640 align:start position:0% do it in an eof container we 00:26:26.640 --> 00:26:28.610 align:start position:0% do it in an eof container we simultaneously<00:26:27.419> solve<00:26:27.840> the<00:26:27.960> jump<00:26:28.380> test 00:26:28.610 --> 00:26:28.620 align:start position:0% simultaneously solve the jump test 00:26:28.620 --> 00:26:31.669 align:start position:0% simultaneously solve the jump test analysis<00:26:29.159> problem<00:26:29.539> and<00:26:30.539> uh<00:26:30.900> reasons<00:26:31.500> to 00:26:31.669 --> 00:26:31.679 align:start position:0% analysis problem and uh reasons to 00:26:31.679 --> 00:26:34.789 align:start position:0% analysis problem and uh reasons to motivate<00:26:32.039> people<00:26:32.220> to<00:26:32.400> use<00:26:32.520> eof<00:26:32.940> so<00:26:33.539> I<00:26:34.440> I<00:26:34.620> think 00:26:34.789 --> 00:26:34.799 align:start position:0% motivate people to use eof so I I think 00:26:34.799 --> 00:26:36.110 align:start position:0% motivate people to use eof so I I think there's<00:26:34.980> a<00:26:35.159> lot<00:26:35.220> of<00:26:35.340> things<00:26:35.460> we<00:26:35.700> could<00:26:35.820> combine 00:26:36.110 --> 00:26:36.120 align:start position:0% there's a lot of things we could combine 00:26:36.120 --> 00:26:38.210 align:start position:0% there's a lot of things we could combine and<00:26:36.299> trade<00:26:36.480> some<00:26:36.659> horses<00:26:36.960> to<00:26:37.140> make<00:26:37.260> this<00:26:37.440> work 00:26:38.210 --> 00:26:38.220 align:start position:0% and trade some horses to make this work 00:26:38.220 --> 00:26:41.390 align:start position:0% and trade some horses to make this work I<00:26:38.880> I 00:26:41.390 --> 00:26:41.400 align:start position:0% 00:26:41.400 --> 00:26:43.850 align:start position:0% just<00:26:42.360> in<00:26:42.539> my<00:26:42.720> opponent<00:26:43.020> trivia<00:26:43.200> for<00:26:43.500> why<00:26:43.620> 24 00:26:43.850 --> 00:26:43.860 align:start position:0% just in my opponent trivia for why 24 00:26:43.860 --> 00:26:46.130 align:start position:0% just in my opponent trivia for why 24 kilobytes<00:26:44.340> was<00:26:44.520> chosen<00:26:44.880> as<00:26:45.059> well<00:26:45.179> it<00:26:45.779> was<00:26:45.900> a 00:26:46.130 --> 00:26:46.140 align:start position:0% kilobytes was chosen as well it was a 00:26:46.140 --> 00:26:47.510 align:start position:0% kilobytes was chosen as well it was a convenient<00:26:46.440> representation<00:26:46.980> I<00:26:47.220> think<00:26:47.340> it<00:26:47.400> was 00:26:47.510 --> 00:26:47.520 align:start position:0% convenient representation I think it was 00:26:47.520 --> 00:26:49.310 align:start position:0% convenient representation I think it was two<00:26:47.640> to<00:26:47.820> the<00:26:47.940> six<00:26:48.059> plus<00:26:48.179> two<00:26:48.360> to<00:26:48.480> the<00:26:48.600> seven<00:26:48.720> and 00:26:49.310 --> 00:26:49.320 align:start position:0% two to the six plus two to the seven and 00:26:49.320 --> 00:26:51.110 align:start position:0% two to the six plus two to the seven and at<00:26:49.559> the<00:26:49.679> time<00:26:49.799> of<00:26:49.919> the<00:26:50.039> gas<00:26:50.159> limit<00:26:50.460> it<00:26:50.940> wouldn't 00:26:51.110 --> 00:26:51.120 align:start position:0% at the time of the gas limit it wouldn't 00:26:51.120 --> 00:26:52.789 align:start position:0% at the time of the gas limit it wouldn't have<00:26:51.360> broken<00:26:51.539> any<00:26:51.779> contracts<00:26:52.260> because<00:26:52.440> it<00:26:52.679> was 00:26:52.789 --> 00:26:52.799 align:start position:0% have broken any contracts because it was 00:26:52.799 --> 00:26:55.250 align:start position:0% have broken any contracts because it was impossible<00:26:53.159> to<00:26:53.279> reach<00:26:53.520> that 00:26:55.250 --> 00:26:55.260 align:start position:0% impossible to reach that 00:26:55.260 --> 00:26:58.370 align:start position:0% impossible to reach that so<00:26:55.620> I<00:26:56.279> it's<00:26:56.460> not<00:26:56.700> possible<00:26:57.059> to<00:26:57.299> do<00:26:57.480> this<00:26:57.659> on<00:26:58.020> uh 00:26:58.370 --> 00:26:58.380 align:start position:0% so I it's not possible to do this on uh 00:26:58.380 --> 00:27:01.070 align:start position:0% so I it's not possible to do this on uh on<00:26:59.039> uh<00:26:59.460> mainnet<00:27:00.059> right<00:27:00.240> now<00:27:00.419> and<00:27:00.659> I<00:27:00.779> think<00:27:00.900> it 00:27:01.070 --> 00:27:01.080 align:start position:0% on uh mainnet right now and I think it 00:27:01.080 --> 00:27:02.810 align:start position:0% on uh mainnet right now and I think it think it's<00:27:01.320> also<00:27:01.620> not<00:27:01.799> possible<00:27:02.159> to<00:27:02.640> to 00:27:02.810 --> 00:27:02.820 align:start position:0% think it's also not possible to to 00:27:02.820 --> 00:27:05.390 align:start position:0% think it's also not possible to to increase<00:27:03.419> the<00:27:03.779> code<00:27:03.960> size 00:27:05.390 --> 00:27:05.400 align:start position:0% increase the code size 00:27:05.400 --> 00:27:08.690 align:start position:0% increase the code size uh<00:27:06.000> if<00:27:06.240> you're<00:27:06.360> a<00:27:06.539> client<00:27:06.779> stuff<00:27:07.380> and 00:27:08.690 --> 00:27:08.700 align:start position:0% uh if you're a client stuff and 00:27:08.700 --> 00:27:10.789 align:start position:0% uh if you're a client stuff and you're<00:27:09.419> interested<00:27:09.900> about<00:27:10.140> my<00:27:10.440> reasoning 00:27:10.789 --> 00:27:10.799 align:start position:0% you're interested about my reasoning 00:27:10.799 --> 00:27:13.730 align:start position:0% you're interested about my reasoning come<00:27:11.039> talk<00:27:11.220> to<00:27:11.340> me<00:27:11.520> afterwards 00:27:13.730 --> 00:27:13.740 align:start position:0% come talk to me afterwards 00:27:13.740 --> 00:27:14.690 align:start position:0% come talk to me afterwards um 00:27:14.690 --> 00:27:14.700 align:start position:0% um 00:27:14.700 --> 00:27:18.409 align:start position:0% um what<00:27:15.299> is<00:27:15.419> possible<00:27:15.779> is<00:27:16.080> to<00:27:16.260> do<00:27:16.380> it<00:27:16.500> in<00:27:16.620> UF<00:27:17.120> and<00:27:18.120> I 00:27:18.409 --> 00:27:18.419 align:start position:0% what is possible is to do it in UF and I 00:27:18.419 --> 00:27:19.970 align:start position:0% what is possible is to do it in UF and I think<00:27:18.600> that's<00:27:18.840> what<00:27:19.080> you<00:27:19.200> what<00:27:19.500> you<00:27:19.740> should 00:27:19.970 --> 00:27:19.980 align:start position:0% think that's what you what you should 00:27:19.980 --> 00:27:23.450 align:start position:0% think that's what you what you should strive<00:27:20.700> for<00:27:20.880> uh<00:27:21.600> do<00:27:21.900> it<00:27:22.080> any<00:27:22.320> eof<00:27:22.799> when<00:27:23.100> we<00:27:23.279> have 00:27:23.450 --> 00:27:23.460 align:start position:0% strive for uh do it any eof when we have 00:27:23.460 --> 00:27:25.010 align:start position:0% strive for uh do it any eof when we have the 00:27:25.010 --> 00:27:25.020 align:start position:0% the 00:27:25.020 --> 00:27:27.649 align:start position:0% the the<00:27:25.080> jump<00:27:25.620> test<00:27:25.860> stuff<00:27:26.159> cool<00:27:26.940> I'll<00:27:27.240> get<00:27:27.480> us 00:27:27.649 --> 00:27:27.659 align:start position:0% the jump test stuff cool I'll get us 00:27:27.659 --> 00:27:30.830 align:start position:0% the jump test stuff cool I'll get us commented<00:27:28.620> just<00:27:29.460> a<00:27:29.700> tiny<00:27:30.000> tiny<00:27:30.299> bit<00:27:30.360> of<00:27:30.539> dot 00:27:30.830 --> 00:27:30.840 align:start position:0% commented just a tiny tiny bit of dot 00:27:30.840 --> 00:27:32.810 align:start position:0% commented just a tiny tiny bit of dot comment<00:27:31.020> you<00:27:31.200> mentioned<00:27:31.500> that<00:27:31.740> you<00:27:32.640> had<00:27:32.700> to 00:27:32.810 --> 00:27:32.820 align:start position:0% comment you mentioned that you had to 00:27:32.820 --> 00:27:34.190 align:start position:0% comment you mentioned that you had to test<00:27:33.000> setup<00:27:33.299> and<00:27:33.480> running<00:27:33.600> and<00:27:33.840> it's<00:27:34.020> been 00:27:34.190 --> 00:27:34.200 align:start position:0% test setup and running and it's been 00:27:34.200 --> 00:27:36.649 align:start position:0% test setup and running and it's been running<00:27:34.320> perfectly<00:27:34.880> the<00:27:35.880> with<00:27:36.240> all<00:27:36.419> these 00:27:36.649 --> 00:27:36.659 align:start position:0% running perfectly the with all these 00:27:36.659 --> 00:27:39.169 align:start position:0% running perfectly the with all these changes<00:27:36.960> the<00:27:37.260> catch<00:27:37.620> is<00:27:37.799> it's<00:27:38.159> uh<00:27:38.520> the<00:27:39.059> average 00:27:39.169 --> 00:27:39.179 align:start position:0% changes the catch is it's uh the average 00:27:39.179 --> 00:27:40.730 align:start position:0% changes the catch is it's uh the average case<00:27:39.480> we<00:27:39.720> know<00:27:39.840> that<00:27:40.020> it<00:27:40.140> runs<00:27:40.440> perfectly 00:27:40.730 --> 00:27:40.740 align:start position:0% case we know that it runs perfectly 00:27:40.740 --> 00:27:42.649 align:start position:0% case we know that it runs perfectly because<00:27:41.039> the<00:27:41.580> code<00:27:41.760> is<00:27:41.940> written<00:27:42.240> well<00:27:42.419> the 00:27:42.649 --> 00:27:42.659 align:start position:0% because the code is written well the 00:27:42.659 --> 00:27:44.810 align:start position:0% because the code is written well the problem<00:27:42.840> is<00:27:43.080> how<00:27:43.559> attackable<00:27:44.039> it<00:27:44.279> is<00:27:44.400> and<00:27:44.580> in 00:27:44.810 --> 00:27:44.820 align:start position:0% problem is how attackable it is and in 00:27:44.820 --> 00:27:46.070 align:start position:0% problem is how attackable it is and in your<00:27:44.940> private<00:27:45.240> task<00:27:45.360> that<00:27:45.539> nobody<00:27:45.840> is<00:27:45.960> going 00:27:46.070 --> 00:27:46.080 align:start position:0% your private task that nobody is going 00:27:46.080 --> 00:27:47.930 align:start position:0% your private task that nobody is going to<00:27:46.200> attack<00:27:46.320> it 00:27:47.930 --> 00:27:47.940 align:start position:0% to attack it 00:27:47.940 --> 00:27:50.630 align:start position:0% to attack it cool<00:27:48.600> thank<00:27:49.320> you 00:27:50.630 --> 00:27:50.640 align:start position:0% cool thank you 00:27:50.640 --> 00:27:52.730 align:start position:0% cool thank you um<00:27:50.820> dang<00:27:51.299> crab<00:27:51.659> did<00:27:51.840> you<00:27:51.960> have<00:27:52.020> any<00:27:52.140> IPS<00:27:52.500> do<00:27:52.679> you 00:27:52.730 --> 00:27:52.740 align:start position:0% um dang crab did you have any IPS do you 00:27:52.740 --> 00:27:55.730 align:start position:0% um dang crab did you have any IPS do you want<00:27:52.799> to<00:27:52.860> talk<00:27:52.980> about<00:27:53.039> self-destruct 00:27:55.730 --> 00:27:55.740 align:start position:0% 00:27:55.740 --> 00:27:58.669 align:start position:0% who's<00:27:56.159> the<00:27:56.340> self-destruct<00:27:56.880> guy<00:27:57.179> Proto 00:27:58.669 --> 00:27:58.679 align:start position:0% who's the self-destruct guy Proto 00:27:58.679 --> 00:28:01.850 align:start position:0% who's the self-destruct guy Proto okay<00:27:59.279> uh<00:27:59.820> hello<00:28:00.000> everyone<00:28:00.299> I'm<00:28:00.960> proud<00:28:01.260> of<00:28:01.500> I 00:28:01.850 --> 00:28:01.860 align:start position:0% okay uh hello everyone I'm proud of I 00:28:01.860 --> 00:28:03.649 align:start position:0% okay uh hello everyone I'm proud of I work<00:28:01.980> with<00:28:02.100> Opie<00:28:02.460> lumps 00:28:03.649 --> 00:28:03.659 align:start position:0% work with Opie lumps 00:28:03.659 --> 00:28:04.970 align:start position:0% work with Opie lumps um 00:28:04.970 --> 00:28:04.980 align:start position:0% um 00:28:04.980 --> 00:28:07.610 align:start position:0% um we<00:28:05.340> have<00:28:05.460> this<00:28:05.640> dream<00:28:05.880> of<00:28:06.059> serenity 00:28:07.610 --> 00:28:07.620 align:start position:0% we have this dream of serenity 00:28:07.620 --> 00:28:10.130 align:start position:0% we have this dream of serenity Serenity<00:28:08.340> includes<00:28:08.940> proof<00:28:09.419> of<00:28:09.480> stake<00:28:09.840> and 00:28:10.130 --> 00:28:10.140 align:start position:0% Serenity includes proof of stake and 00:28:10.140 --> 00:28:11.269 align:start position:0% Serenity includes proof of stake and sharding 00:28:11.269 --> 00:28:11.279 align:start position:0% sharding 00:28:11.279 --> 00:28:13.549 align:start position:0% sharding they<00:28:11.640> have<00:28:11.820> achieved<00:28:12.299> proof<00:28:12.600> of<00:28:12.720> Stack<00:28:12.960> I<00:28:13.320> want 00:28:13.549 --> 00:28:13.559 align:start position:0% they have achieved proof of Stack I want 00:28:13.559 --> 00:28:15.950 align:start position:0% they have achieved proof of Stack I want to<00:28:13.679> continue<00:28:13.799> with<00:28:14.100> sharding<00:28:14.580> I'm<00:28:15.299> fully<00:28:15.720> bolt 00:28:15.950 --> 00:28:15.960 align:start position:0% to continue with sharding I'm fully bolt 00:28:15.960 --> 00:28:18.950 align:start position:0% to continue with sharding I'm fully bolt into<00:28:16.140> the<00:28:16.320> ethereum<00:28:16.760> for<00:28:17.760> this<00:28:18.480> combination 00:28:18.950 --> 00:28:18.960 align:start position:0% into the ethereum for this combination 00:28:18.960 --> 00:28:21.950 align:start position:0% into the ethereum for this combination not<00:28:19.799> for<00:28:20.039> one<00:28:20.460> and<00:28:20.640> not<00:28:20.760> the<00:28:20.940> other 00:28:21.950 --> 00:28:21.960 align:start position:0% not for one and not the other 00:28:21.960 --> 00:28:23.210 align:start position:0% not for one and not the other and 00:28:23.210 --> 00:28:23.220 align:start position:0% and 00:28:23.220 --> 00:28:28.310 align:start position:0% and I<00:28:23.880> think<00:28:24.059> right<00:28:25.020> now<00:28:25.200> the<00:28:25.980> process<00:28:26.760> that<00:28:27.600> eaps 00:28:28.310 --> 00:28:28.320 align:start position:0% I think right now the process that eaps 00:28:28.320 --> 00:28:30.590 align:start position:0% I think right now the process that eaps has<00:28:28.620> been<00:28:28.740> like<00:28:28.919> kind<00:28:29.100> of<00:28:29.220> imbalanced<00:28:29.940> with 00:28:30.590 --> 00:28:30.600 align:start position:0% has been like kind of imbalanced with 00:28:30.600 --> 00:28:32.750 align:start position:0% has been like kind of imbalanced with the<00:28:30.840> merge<00:28:31.140> because<00:28:31.440> we<00:28:31.740> have<00:28:31.919> a<00:28:32.159> exclusion 00:28:32.750 --> 00:28:32.760 align:start position:0% the merge because we have a exclusion 00:28:32.760 --> 00:28:35.990 align:start position:0% the merge because we have a exclusion layer<00:28:33.200> consensus<00:28:34.200> layer<00:28:34.440> I<00:28:35.279> think<00:28:35.460> an<00:28:35.700> EIP 00:28:35.990 --> 00:28:36.000 align:start position:0% layer consensus layer I think an EIP 00:28:36.000 --> 00:28:38.930 align:start position:0% layer consensus layer I think an EIP that<00:28:36.659> does<00:28:37.080> both<00:28:37.380> of<00:28:37.559> these<00:28:37.799> and<00:28:38.700> actually 00:28:38.930 --> 00:28:38.940 align:start position:0% that does both of these and actually 00:28:38.940 --> 00:28:41.029 align:start position:0% that does both of these and actually does<00:28:39.299> touch<00:28:39.659> on<00:28:39.960> the<00:28:40.080> testing<00:28:40.500> infrastructure 00:28:41.029 --> 00:28:41.039 align:start position:0% does touch on the testing infrastructure 00:28:41.039 --> 00:28:43.730 align:start position:0% does touch on the testing infrastructure is<00:28:41.760> the<00:28:41.940> thing<00:28:42.059> we<00:28:42.240> need<00:28:42.480> to<00:28:42.659> repair<00:28:42.840> it 00:28:43.730 --> 00:28:43.740 align:start position:0% is the thing we need to repair it 00:28:43.740 --> 00:28:46.190 align:start position:0% is the thing we need to repair it right<00:28:44.220> now<00:28:44.460> the<00:28:44.940> merge<00:28:45.360> was 00:28:46.190 --> 00:28:46.200 align:start position:0% right now the merge was 00:28:46.200 --> 00:28:48.470 align:start position:0% right now the merge was I<00:28:46.679> think<00:28:46.799> still<00:28:47.100> shipped<00:28:47.640> in<00:28:47.700> relative<00:28:48.000> hurry 00:28:48.470 --> 00:28:48.480 align:start position:0% I think still shipped in relative hurry 00:28:48.480 --> 00:28:50.930 align:start position:0% I think still shipped in relative hurry but<00:28:49.140> with<00:28:49.559> scaling<00:28:50.340> we<00:28:50.520> have<00:28:50.640> actual 00:28:50.930 --> 00:28:50.940 align:start position:0% but with scaling we have actual 00:28:50.940 --> 00:28:54.710 align:start position:0% but with scaling we have actual incentives<00:28:51.559> outside<00:28:52.559> of<00:28:53.039> just<00:28:53.460> client<00:28:53.880> teams 00:28:54.710 --> 00:28:54.720 align:start position:0% incentives outside of just client teams 00:28:54.720 --> 00:28:56.390 align:start position:0% incentives outside of just client teams to 00:28:56.390 --> 00:28:56.400 align:start position:0% to 00:28:56.400 --> 00:28:59.029 align:start position:0% to improve<00:28:57.059> this<00:28:57.240> infrastructure<00:28:57.779> to<00:28:58.559> improve 00:28:59.029 --> 00:28:59.039 align:start position:0% improve this infrastructure to improve 00:28:59.039 --> 00:29:01.190 align:start position:0% improve this infrastructure to improve analysis<00:28:59.580> of<00:28:59.760> ethereum<00:29:00.480> to<00:29:00.779> improve 00:29:01.190 --> 00:29:01.200 align:start position:0% analysis of ethereum to improve 00:29:01.200 --> 00:29:04.610 align:start position:0% analysis of ethereum to improve integration<00:29:02.100> testing<00:29:02.640> and<00:29:03.539> so<00:29:03.779> we<00:29:04.380> can<00:29:04.500> get 00:29:04.610 --> 00:29:04.620 align:start position:0% integration testing and so we can get 00:29:04.620 --> 00:29:07.430 align:start position:0% integration testing and so we can get the<00:29:04.740> best<00:29:04.919> of<00:29:05.100> both<00:29:05.220> worlds<00:29:05.760> where<00:29:06.000> we<00:29:06.179> can 00:29:07.430 --> 00:29:07.440 align:start position:0% the best of both worlds where we can 00:29:07.440 --> 00:29:09.110 align:start position:0% the best of both worlds where we can improve<00:29:08.039> ethereum 00:29:09.110 --> 00:29:09.120 align:start position:0% improve ethereum 00:29:09.120 --> 00:29:13.070 align:start position:0% improve ethereum and<00:29:09.600> we<00:29:09.900> can<00:29:10.020> improve<00:29:10.500> the<00:29:11.460> process<00:29:12.299> that<00:29:12.840> we 00:29:13.070 --> 00:29:13.080 align:start position:0% and we can improve the process that we 00:29:13.080 --> 00:29:16.130 align:start position:0% and we can improve the process that we have<00:29:13.500> to<00:29:13.860> accept<00:29:14.039> erps<00:29:14.760> and<00:29:15.539> so<00:29:15.659> that<00:29:15.840> we<00:29:15.960> can 00:29:16.130 --> 00:29:16.140 align:start position:0% have to accept erps and so that we can 00:29:16.140 --> 00:29:17.930 align:start position:0% have to accept erps and so that we can be<00:29:16.380> happy<00:29:16.679> to 00:29:17.930 --> 00:29:17.940 align:start position:0% be happy to 00:29:17.940 --> 00:29:20.990 align:start position:0% be happy to enter<00:29:18.720> future<00:29:19.320> erps<00:29:19.980> without<00:29:20.460> as<00:29:20.820> much 00:29:20.990 --> 00:29:21.000 align:start position:0% enter future erps without as much 00:29:21.000 --> 00:29:22.310 align:start position:0% enter future erps without as much concern<00:29:21.360> because<00:29:21.720> you<00:29:22.020> have<00:29:22.140> to<00:29:22.200> write 00:29:22.310 --> 00:29:22.320 align:start position:0% concern because you have to write 00:29:22.320 --> 00:29:24.230 align:start position:0% concern because you have to write testing<00:29:22.679> in<00:29:22.860> place 00:29:24.230 --> 00:29:24.240 align:start position:0% testing in place 00:29:24.240 --> 00:29:26.870 align:start position:0% testing in place and<00:29:24.899> then<00:29:25.140> outside<00:29:25.740> of<00:29:26.039> testing<00:29:26.460> and<00:29:26.700> the 00:29:26.870 --> 00:29:26.880 align:start position:0% and then outside of testing and the 00:29:26.880 --> 00:29:29.149 align:start position:0% and then outside of testing and the whole<00:29:27.000> process<00:29:27.419> just<00:29:28.320> in<00:29:28.500> case<00:29:28.620> before<00:29:28.860> it 00:29:29.149 --> 00:29:29.159 align:start position:0% whole process just in case before it 00:29:29.159 --> 00:29:30.649 align:start position:0% whole process just in case before it prefer 00:29:30.649 --> 00:29:30.659 align:start position:0% prefer 00:29:30.659 --> 00:29:32.450 align:start position:0% prefer if<00:29:31.140> you're<00:29:31.260> not<00:29:31.440> familiar<00:29:31.740> already<00:29:31.919> before<00:29:32.220> it 00:29:32.450 --> 00:29:32.460 align:start position:0% if you're not familiar already before it 00:29:32.460 --> 00:29:35.029 align:start position:0% if you're not familiar already before it prefer<00:29:32.700> it<00:29:33.059> increases<00:29:33.539> the<00:29:34.200> data<00:29:34.559> for<00:29:34.740> Layer 00:29:35.029 --> 00:29:35.039 align:start position:0% prefer it increases the data for Layer 00:29:35.039 --> 00:29:35.690 align:start position:0% prefer it increases the data for Layer Two 00:29:35.690 --> 00:29:35.700 align:start position:0% Two 00:29:35.700 --> 00:29:37.389 align:start position:0% Two layer<00:29:36.480> 2 00:29:37.389 --> 00:29:37.399 align:start position:0% layer 2 00:29:37.399 --> 00:29:40.070 align:start position:0% layer 2 is<00:29:38.399> meant<00:29:38.760> to<00:29:38.820> be<00:29:38.940> an<00:29:39.120> extension<00:29:39.539> of<00:29:39.659> ethereum 00:29:40.070 --> 00:29:40.080 align:start position:0% is meant to be an extension of ethereum 00:29:40.080 --> 00:29:43.070 align:start position:0% is meant to be an extension of ethereum you<00:29:40.799> could<00:29:40.919> think<00:29:41.159> of<00:29:41.700> the<00:29:42.360> previous<00:29:42.539> charting 00:29:43.070 --> 00:29:43.080 align:start position:0% you could think of the previous charting 00:29:43.080 --> 00:29:45.769 align:start position:0% you could think of the previous charting dream<00:29:43.260> of<00:29:43.440> ethereum<00:29:43.980> as<00:29:44.940> this<00:29:45.240> execution 00:29:45.769 --> 00:29:45.779 align:start position:0% dream of ethereum as this execution 00:29:45.779 --> 00:29:48.169 align:start position:0% dream of ethereum as this execution charting<00:29:46.320> thing<00:29:46.559> where<00:29:47.220> it<00:29:47.399> was<00:29:47.520> all<00:29:48.000> the 00:29:48.169 --> 00:29:48.179 align:start position:0% charting thing where it was all the 00:29:48.179 --> 00:29:51.470 align:start position:0% charting thing where it was all the complexity<00:29:48.539> left<00:29:48.779> on<00:29:49.220> ethereum<00:29:50.220> itself<00:29:50.520> layer 00:29:51.470 --> 00:29:51.480 align:start position:0% complexity left on ethereum itself layer 00:29:51.480 --> 00:29:54.110 align:start position:0% complexity left on ethereum itself layer 2<00:29:51.860> enables<00:29:52.860> this<00:29:53.039> to<00:29:53.220> be<00:29:53.340> more<00:29:53.640> competitive 00:29:54.110 --> 00:29:54.120 align:start position:0% 2 enables this to be more competitive 00:29:54.120 --> 00:29:57.169 align:start position:0% 2 enables this to be more competitive and<00:29:54.720> be<00:29:55.020> split<00:29:55.320> from<00:29:55.500> ethereum<00:29:56.100> where<00:29:56.820> we<00:29:57.059> have 00:29:57.169 --> 00:29:57.179 align:start position:0% and be split from ethereum where we have 00:29:57.179 --> 00:30:00.549 align:start position:0% and be split from ethereum where we have exclusive<00:29:57.659> layer<00:29:57.960> as<00:29:58.080> layer<00:29:58.380> 2<00:29:58.559> and<00:29:59.279> we<00:29:59.460> have 00:30:00.549 --> 00:30:00.559 align:start position:0% exclusive layer as layer 2 and we have 00:30:00.559 --> 00:30:03.710 align:start position:0% exclusive layer as layer 2 and we have the<00:30:01.559> layer<00:30:02.100> bomb<00:30:02.279> just<00:30:02.580> focus<00:30:03.000> on<00:30:03.600> the 00:30:03.710 --> 00:30:03.720 align:start position:0% the layer bomb just focus on the 00:30:03.720 --> 00:30:06.110 align:start position:0% the layer bomb just focus on the securing<00:30:04.200> data<00:30:04.620> fatability<00:30:05.520> and<00:30:05.940> this<00:30:06.059> is 00:30:06.110 --> 00:30:06.120 align:start position:0% securing data fatability and this is 00:30:06.120 --> 00:30:08.690 align:start position:0% securing data fatability and this is what<00:30:06.360> this<00:30:06.480> EIP<00:30:06.720> focuses<00:30:07.320> on<00:30:07.620> and<00:30:08.159> achieves 00:30:08.690 --> 00:30:08.700 align:start position:0% what this EIP focuses on and achieves 00:30:08.700 --> 00:30:11.810 align:start position:0% what this EIP focuses on and achieves and<00:30:09.539> then<00:30:09.659> through<00:30:09.899> this<00:30:10.140> means<00:30:10.620> we<00:30:11.279> can<00:30:11.460> adopt 00:30:11.810 --> 00:30:11.820 align:start position:0% and then through this means we can adopt 00:30:11.820 --> 00:30:14.409 align:start position:0% and then through this means we can adopt a<00:30:11.880> lot<00:30:12.000> more<00:30:12.179> ethereum<00:30:12.779> users<00:30:13.200> onto<00:30:13.919> Layer<00:30:14.220> Two 00:30:14.409 --> 00:30:14.419 align:start position:0% a lot more ethereum users onto Layer Two 00:30:14.419 --> 00:30:17.750 align:start position:0% a lot more ethereum users onto Layer Two and<00:30:15.419> projects<00:30:16.200> like<00:30:16.380> like<00:30:16.860> coinbase<00:30:17.399> or<00:30:17.640> other 00:30:17.750 --> 00:30:17.760 align:start position:0% and projects like like coinbase or other 00:30:17.760 --> 00:30:20.990 align:start position:0% and projects like like coinbase or other like<00:30:18.120> larger<00:30:18.960> ethereum<00:30:19.620> users<00:30:20.039> don't<00:30:20.640> have<00:30:20.880> to 00:30:20.990 --> 00:30:21.000 align:start position:0% like larger ethereum users don't have to 00:30:21.000 --> 00:30:23.210 align:start position:0% like larger ethereum users don't have to look<00:30:21.240> at<00:30:21.659> these<00:30:21.960> ethereum<00:30:22.500> killers<00:30:22.980> in 00:30:23.210 --> 00:30:23.220 align:start position:0% look at these ethereum killers in 00:30:23.220 --> 00:30:26.269 align:start position:0% look at these ethereum killers in quotation<00:30:23.640> marks<00:30:24.539> where<00:30:25.440> they<00:30:25.980> can<00:30:26.100> actually 00:30:26.269 --> 00:30:26.279 align:start position:0% quotation marks where they can actually 00:30:26.279 --> 00:30:30.830 align:start position:0% quotation marks where they can actually host<00:30:26.820> these<00:30:27.179> users<00:30:27.539> at<00:30:28.080> low<00:30:28.260> cost 00:30:30.830 --> 00:30:30.840 align:start position:0% 00:30:30.840 --> 00:30:32.630 align:start position:0% um<00:30:30.899> just<00:30:31.140> because<00:30:31.260> we<00:30:31.620> talked<00:30:31.860> about<00:30:31.980> it<00:30:32.279> a 00:30:32.630 --> 00:30:32.640 align:start position:0% um just because we talked about it a 00:30:32.640 --> 00:30:34.070 align:start position:0% um just because we talked about it a bunch<00:30:32.760> before 00:30:34.070 --> 00:30:34.080 align:start position:0% bunch before 00:30:34.080 --> 00:30:35.450 align:start position:0% bunch before um the<00:30:34.440> client<00:30:34.679> teams<00:30:34.919> have<00:30:35.039> anything<00:30:35.279> else 00:30:35.450 --> 00:30:35.460 align:start position:0% um the client teams have anything else 00:30:35.460 --> 00:30:38.269 align:start position:0% um the client teams have anything else to<00:30:35.640> add<00:30:35.820> or 00:30:38.269 --> 00:30:38.279 align:start position:0% 00:30:38.279 --> 00:30:40.490 align:start position:0% numbers<00:30:38.880> numbers 00:30:40.490 --> 00:30:40.500 align:start position:0% numbers numbers 00:30:40.500 --> 00:30:43.610 align:start position:0% numbers numbers okay<00:30:41.299> you<00:30:42.299> heard<00:30:42.480> it<00:30:42.659> here 00:30:43.610 --> 00:30:43.620 align:start position:0% okay you heard it here 00:30:43.620 --> 00:30:44.930 align:start position:0% okay you heard it here um<00:30:43.679> yeah<00:30:43.860> I<00:30:43.980> just<00:30:44.100> I<00:30:44.279> want<00:30:44.399> to<00:30:44.520> make<00:30:44.580> sure<00:30:44.700> we 00:30:44.930 --> 00:30:44.940 align:start position:0% um yeah I just I want to make sure we 00:30:44.940 --> 00:30:47.149 align:start position:0% um yeah I just I want to make sure we can<00:30:45.059> get<00:30:45.480> to<00:30:45.659> as<00:30:46.020> many<00:30:46.200> people<00:30:46.380> in<00:30:46.620> the<00:30:46.799> next<00:30:46.919> 20 00:30:47.149 --> 00:30:47.159 align:start position:0% can get to as many people in the next 20 00:30:47.159 --> 00:30:49.310 align:start position:0% can get to as many people in the next 20 minutes<00:30:47.399> as<00:30:47.700> possible<00:30:48.000> or<00:30:48.600> thank<00:30:48.899> God<00:30:49.080> we're 00:30:49.310 --> 00:30:49.320 align:start position:0% minutes as possible or thank God we're 00:30:49.320 --> 00:30:50.810 align:start position:0% minutes as possible or thank God we're gonna<00:30:49.440> add<00:30:49.620> something<00:30:49.740> on 00:30:50.810 --> 00:30:50.820 align:start position:0% gonna add something on 00:30:50.820 --> 00:30:52.370 align:start position:0% gonna add something on I<00:30:51.299> think<00:30:51.539> I've<00:30:51.659> already<00:30:51.840> said<00:30:52.080> the<00:30:52.260> main 00:30:52.370 --> 00:30:52.380 align:start position:0% I think I've already said the main 00:30:52.380 --> 00:30:54.049 align:start position:0% I think I've already said the main things<00:30:52.500> I<00:30:52.740> wanted<00:30:52.799> to<00:30:52.980> say<00:30:53.100> but<00:30:53.279> yeah<00:30:53.460> once<00:30:53.880> off 00:30:54.049 --> 00:30:54.059 align:start position:0% things I wanted to say but yeah once off 00:30:54.059 --> 00:30:55.789 align:start position:0% things I wanted to say but yeah once off destruct<00:30:54.419> I<00:30:54.659> think<00:30:54.779> Mario's<00:30:55.320> has<00:30:55.440> the<00:30:55.620> pitch 00:30:55.789 --> 00:30:55.799 align:start position:0% destruct I think Mario's has the pitch 00:30:55.799 --> 00:30:57.669 align:start position:0% destruct I think Mario's has the pitch oh 00:30:57.669 --> 00:30:57.679 align:start position:0% oh 00:30:57.679 --> 00:30:59.870 align:start position:0% oh do<00:30:58.679> you<00:30:58.740> want<00:30:58.799> to<00:30:58.860> do<00:30:58.980> the<00:30:59.039> pitch<00:30:59.220> mares<00:30:59.580> or<00:30:59.760> do 00:30:59.870 --> 00:30:59.880 align:start position:0% do you want to do the pitch mares or do 00:30:59.880 --> 00:31:00.889 align:start position:0% do you want to do the pitch mares or do you<00:31:00.000> want<00:31:00.000> to<00:31:00.120> listen<00:31:00.240> to<00:31:00.419> more<00:31:00.600> of<00:31:00.720> the<00:31:00.840> other 00:31:00.889 --> 00:31:00.899 align:start position:0% you want to listen to more of the other 00:31:00.899 --> 00:31:02.389 align:start position:0% you want to listen to more of the other pitches 00:31:02.389 --> 00:31:02.399 align:start position:0% pitches 00:31:02.399 --> 00:31:05.090 align:start position:0% pitches um<00:31:02.580> we<00:31:02.940> should<00:31:03.120> remove<00:31:03.299> self-destruct 00:31:05.090 --> 00:31:05.100 align:start position:0% um we should remove self-destruct 00:31:05.100 --> 00:31:10.070 align:start position:0% um we should remove self-destruct um<00:31:05.220> yes<00:31:05.640> that's<00:31:06.000> the<00:31:06.179> picture<00:31:06.620> we<00:31:07.620> agree<00:31:07.919> okay 00:31:10.070 --> 00:31:10.080 align:start position:0% um yes that's the picture we agree okay 00:31:10.080 --> 00:31:12.950 align:start position:0% um yes that's the picture we agree okay okay<00:31:10.820> and<00:31:11.820> we<00:31:12.000> need<00:31:12.120> we<00:31:12.539> need<00:31:12.659> to<00:31:12.779> remove 00:31:12.950 --> 00:31:12.960 align:start position:0% okay and we need we need to remove 00:31:12.960 --> 00:31:15.590 align:start position:0% okay and we need we need to remove self-destruct<00:31:13.679> for<00:31:14.159> vertical<00:31:14.940> and<00:31:15.360> history 00:31:15.590 --> 00:31:15.600 align:start position:0% self-destruct for vertical and history 00:31:15.600 --> 00:31:19.730 align:start position:0% self-destruct for vertical and history expiry<00:31:16.320> and<00:31:16.980> uh<00:31:17.820> sorry<00:31:18.299> State<00:31:18.720> expiry<00:31:19.260> and<00:31:19.500> all 00:31:19.730 --> 00:31:19.740 align:start position:0% expiry and uh sorry State expiry and all 00:31:19.740 --> 00:31:21.649 align:start position:0% expiry and uh sorry State expiry and all of<00:31:19.860> these<00:31:20.039> upcoming<00:31:20.460> changes<00:31:20.820> so<00:31:21.120> it<00:31:21.360> needs<00:31:21.600> to 00:31:21.649 --> 00:31:21.659 align:start position:0% of these upcoming changes so it needs to 00:31:21.659 --> 00:31:23.930 align:start position:0% of these upcoming changes so it needs to be<00:31:21.779> done<00:31:21.960> uh<00:31:22.799> the<00:31:22.919> question<00:31:23.100> is<00:31:23.279> do<00:31:23.460> we<00:31:23.640> do<00:31:23.820> we 00:31:23.930 --> 00:31:23.940 align:start position:0% be done uh the question is do we do we 00:31:23.940 --> 00:31:26.570 align:start position:0% be done uh the question is do we do we do<00:31:24.120> it<00:31:24.240> now<00:31:24.600> or<00:31:25.080> do<00:31:25.320> we<00:31:25.500> do<00:31:25.620> it<00:31:25.740> later<00:31:25.919> and<00:31:26.399> I 00:31:26.570 --> 00:31:26.580 align:start position:0% do it now or do we do it later and I 00:31:26.580 --> 00:31:29.450 align:start position:0% do it now or do we do it later and I think<00:31:26.760> it's<00:31:27.480> it's<00:31:27.840> a<00:31:28.080> really<00:31:28.200> small<00:31:28.380> change<00:31:28.740> so 00:31:29.450 --> 00:31:29.460 align:start position:0% think it's it's a really small change so 00:31:29.460 --> 00:31:33.409 align:start position:0% think it's it's a really small change so we<00:31:29.580> should<00:31:29.760> do<00:31:29.880> it<00:31:30.059> now 00:31:33.409 --> 00:31:33.419 align:start position:0% 00:31:33.419 --> 00:31:35.810 align:start position:0% for<00:31:33.720> legacy<00:31:34.320> and<00:31:34.440> dof 00:31:35.810 --> 00:31:35.820 align:start position:0% for legacy and dof 00:31:35.820 --> 00:31:38.389 align:start position:0% for legacy and dof so<00:31:36.299> just<00:31:36.480> to<00:31:36.779> I<00:31:37.140> think<00:31:37.320> this<00:31:37.679> uh<00:31:37.980> if<00:31:38.279> somebody 00:31:38.389 --> 00:31:38.399 align:start position:0% so just to I think this uh if somebody 00:31:38.399 --> 00:31:40.130 align:start position:0% so just to I think this uh if somebody is<00:31:38.640> not<00:31:38.820> really<00:31:38.940> on<00:31:39.120> the<00:31:39.240> page<00:31:39.419> of<00:31:39.600> why<00:31:39.779> we<00:31:39.960> want 00:31:40.130 --> 00:31:40.140 align:start position:0% is not really on the page of why we want 00:31:40.140 --> 00:31:42.310 align:start position:0% is not really on the page of why we want to<00:31:40.200> remove<00:31:40.380> self-destruct<00:31:41.120> essentially 00:31:42.310 --> 00:31:42.320 align:start position:0% to remove self-destruct essentially 00:31:42.320 --> 00:31:45.590 align:start position:0% to remove self-destruct essentially every<00:31:43.320> single<00:31:43.559> op<00:31:43.740> code<00:31:44.039> on<00:31:44.220> the<00:31:44.340> evm<00:31:44.820> is<00:31:45.360> the 00:31:45.590 --> 00:31:45.600 align:start position:0% every single op code on the evm is the 00:31:45.600 --> 00:31:47.870 align:start position:0% every single op code on the evm is the cost<00:31:45.779> is<00:31:46.020> linear<00:31:46.440> or<00:31:46.679> I<00:31:46.860> mean<00:31:47.100> tries<00:31:47.760> to 00:31:47.870 --> 00:31:47.880 align:start position:0% cost is linear or I mean tries to 00:31:47.880 --> 00:31:50.269 align:start position:0% cost is linear or I mean tries to approximate<00:31:48.539> the<00:31:49.080> actual<00:31:49.440> execution<00:31:49.980> that 00:31:50.269 --> 00:31:50.279 align:start position:0% approximate the actual execution that 00:31:50.279 --> 00:31:52.310 align:start position:0% approximate the actual execution that the<00:31:50.580> resources<00:31:51.000> it<00:31:51.179> consumes<00:31:51.659> and 00:31:52.310 --> 00:31:52.320 align:start position:0% the resources it consumes and 00:31:52.320 --> 00:31:54.230 align:start position:0% the resources it consumes and self-destruct<00:31:52.980> is<00:31:53.159> one<00:31:53.399> of<00:31:53.520> those<00:31:53.700> OP<00:31:54.000> codes 00:31:54.230 --> 00:31:54.240 align:start position:0% self-destruct is one of those OP codes 00:31:54.240 --> 00:31:56.149 align:start position:0% self-destruct is one of those OP codes where 00:31:56.149 --> 00:31:56.159 align:start position:0% where 00:31:56.159 --> 00:31:58.190 align:start position:0% where deleting<00:31:57.000> the<00:31:57.240> contract<00:31:57.539> store<00:31:57.720> essentially 00:31:58.190 --> 00:31:58.200 align:start position:0% deleting the contract store essentially 00:31:58.200 --> 00:32:00.289 align:start position:0% deleting the contract store essentially it's<00:31:58.320> a<00:31:58.440> it's<00:31:58.860> a<00:31:58.980> single<00:31:59.159> op<00:31:59.340> code<00:31:59.580> call<00:31:59.880> but<00:32:00.120> it 00:32:00.289 --> 00:32:00.299 align:start position:0% it's a it's a single op code call but it 00:32:00.299 --> 00:32:02.510 align:start position:0% it's a it's a single op code call but it can<00:32:00.600> result<00:32:01.080> in<00:32:01.380> an<00:32:01.559> arbitrarily<00:32:02.279> large 00:32:02.510 --> 00:32:02.520 align:start position:0% can result in an arbitrarily large 00:32:02.520 --> 00:32:05.510 align:start position:0% can result in an arbitrarily large execution<00:32:03.440> and<00:32:04.440> currently<00:32:05.039> the<00:32:05.220> only<00:32:05.340> reason 00:32:05.510 --> 00:32:05.520 align:start position:0% execution and currently the only reason 00:32:05.520 --> 00:32:07.149 align:start position:0% execution and currently the only reason why<00:32:05.760> currently<00:32:06.120> it<00:32:06.299> works<00:32:06.600> is<00:32:06.779> because 00:32:07.149 --> 00:32:07.159 align:start position:0% why currently it works is because 00:32:07.159 --> 00:32:10.010 align:start position:0% why currently it works is because self-destruct<00:32:08.159> assumes<00:32:09.000> that<00:32:09.360> clients 00:32:10.010 --> 00:32:10.020 align:start position:0% self-destruct assumes that clients 00:32:10.020 --> 00:32:12.169 align:start position:0% self-destruct assumes that clients represent<00:32:10.500> the<00:32:10.740> state<00:32:10.980> in<00:32:11.340> a<00:32:11.520> specific<00:32:11.760> way<00:32:12.000> in 00:32:12.169 --> 00:32:12.179 align:start position:0% represent the state in a specific way in 00:32:12.179 --> 00:32:15.409 align:start position:0% represent the state in a specific way in the<00:32:12.299> market<00:32:12.419> Patricia<00:32:13.080> way<00:32:13.260> and<00:32:14.039> if<00:32:14.640> it<00:32:15.179> also 00:32:15.409 --> 00:32:15.419 align:start position:0% the market Patricia way and if it also 00:32:15.419 --> 00:32:16.669 align:start position:0% the market Patricia way and if it also assumes<00:32:15.840> that 00:32:16.669 --> 00:32:16.679 align:start position:0% assumes that 00:32:16.679 --> 00:32:18.710 align:start position:0% assumes that this<00:32:17.159> state<00:32:17.340> does<00:32:17.640> not<00:32:17.760> get<00:32:18.000> deleted<00:32:18.539> from 00:32:18.710 --> 00:32:18.720 align:start position:0% this state does not get deleted from 00:32:18.720 --> 00:32:20.570 align:start position:0% this state does not get deleted from disk<00:32:19.140> it's<00:32:19.260> just<00:32:19.559> a<00:32:19.740> couple<00:32:19.860> of<00:32:20.039> branches<00:32:20.460> of 00:32:20.570 --> 00:32:20.580 align:start position:0% disk it's just a couple of branches of 00:32:20.580 --> 00:32:22.970 align:start position:0% disk it's just a couple of branches of the<00:32:20.640> market<00:32:20.820> Patricia<00:32:21.480> gets<00:32:21.720> updated<00:32:22.020> but<00:32:22.799> the 00:32:22.970 --> 00:32:22.980 align:start position:0% the market Patricia gets updated but the 00:32:22.980 --> 00:32:24.470 align:start position:0% the market Patricia gets updated but the moment<00:32:23.159> you<00:32:23.340> want<00:32:23.460> to<00:32:23.580> do<00:32:23.760> something<00:32:24.000> fancier 00:32:24.470 --> 00:32:24.480 align:start position:0% moment you want to do something fancier 00:32:24.480 --> 00:32:26.750 align:start position:0% moment you want to do something fancier like<00:32:24.779> what<00:32:24.960> Aragon<00:32:25.440> is<00:32:25.559> doing<00:32:25.740> or<00:32:25.980> what<00:32:26.399> gets 00:32:26.750 --> 00:32:26.760 align:start position:0% like what Aragon is doing or what gets 00:32:26.760 --> 00:32:28.190 align:start position:0% like what Aragon is doing or what gets new<00:32:26.880> pruning<00:32:27.240> is<00:32:27.360> doing<00:32:27.539> a<00:32:27.779> sensors 00:32:28.190 --> 00:32:28.200 align:start position:0% new pruning is doing a sensors 00:32:28.200 --> 00:32:31.130 align:start position:0% new pruning is doing a sensors essentially<00:32:28.679> self-destruct<00:32:29.399> will<00:32:29.940> become 00:32:31.130 --> 00:32:31.140 align:start position:0% essentially self-destruct will become 00:32:31.140 --> 00:32:35.210 align:start position:0% essentially self-destruct will become Berlin<00:32:31.980> a<00:32:32.399> completely<00:32:32.820> unbounded<00:32:33.620> opcode<00:32:34.620> and 00:32:35.210 --> 00:32:35.220 align:start position:0% Berlin a completely unbounded opcode and 00:32:35.220 --> 00:32:37.549 align:start position:0% Berlin a completely unbounded opcode and that's<00:32:35.460> it<00:32:35.940> prevents<00:32:36.360> us<00:32:36.539> from 00:32:37.549 --> 00:32:37.559 align:start position:0% that's it prevents us from 00:32:37.559 --> 00:32:39.830 align:start position:0% that's it prevents us from going<00:32:37.980> forward<00:32:38.340> with<00:32:38.820> in<00:32:39.059> the<00:32:39.240> implantations 00:32:39.830 --> 00:32:39.840 align:start position:0% going forward with in the implantations 00:32:39.840 --> 00:32:45.230 align:start position:0% going forward with in the implantations Imagine<00:32:40.740> self-destruct<00:32:41.520> on<00:32:41.760> usdc 00:32:45.230 --> 00:32:45.240 align:start position:0% 00:32:45.240 --> 00:32:47.450 align:start position:0% yeah<00:32:45.840> two 00:32:47.450 --> 00:32:47.460 align:start position:0% yeah two 00:32:47.460 --> 00:32:49.669 align:start position:0% yeah two sorry 00:32:49.669 --> 00:32:49.679 align:start position:0% sorry 00:32:49.679 --> 00:32:53.330 align:start position:0% sorry yeah<00:32:50.059> and<00:32:51.059> and<00:32:51.179> to<00:32:51.539> like<00:32:51.899> make<00:32:52.320> this<00:32:52.559> uh<00:32:52.860> add<00:32:53.159> to 00:32:53.330 --> 00:32:53.340 align:start position:0% yeah and and to like make this uh add to 00:32:53.340 --> 00:32:56.029 align:start position:0% yeah and and to like make this uh add to this<00:32:53.460> like<00:32:53.820> if<00:32:54.480> you<00:32:54.600> want<00:32:54.720> to<00:32:54.840> be<00:32:54.960> stateless<00:32:55.440> it 00:32:56.029 --> 00:32:56.039 align:start position:0% this like if you want to be stateless it 00:32:56.039 --> 00:32:57.889 align:start position:0% this like if you want to be stateless it would<00:32:56.220> be<00:32:56.399> an<00:32:56.640> unbounded<00:32:57.240> number<00:32:57.539> of<00:32:57.720> State 00:32:57.889 --> 00:32:57.899 align:start position:0% would be an unbounded number of State 00:32:57.899 --> 00:32:59.510 align:start position:0% would be an unbounded number of State changes<00:32:58.320> and<00:32:58.559> that<00:32:58.740> completely<00:32:59.159> kills 00:32:59.510 --> 00:32:59.520 align:start position:0% changes and that completely kills 00:32:59.520 --> 00:33:01.130 align:start position:0% changes and that completely kills statelessness 00:33:01.130 --> 00:33:01.140 align:start position:0% statelessness 00:33:01.140 --> 00:33:02.450 align:start position:0% statelessness so<00:33:01.679> yeah 00:33:02.450 --> 00:33:02.460 align:start position:0% so yeah 00:33:02.460 --> 00:33:05.090 align:start position:0% so yeah comment<00:33:03.179> that<00:33:03.419> the<00:33:03.720> currency<00:33:04.559> of<00:33:04.799> this<00:33:04.919> track 00:33:05.090 --> 00:33:05.100 align:start position:0% comment that the currency of this track 00:33:05.100 --> 00:33:07.610 align:start position:0% comment that the currency of this track has<00:33:05.520> a<00:33:05.760> quirk<00:33:06.179> that<00:33:06.419> you<00:33:06.659> can<00:33:06.779> destroy<00:33:07.260> Eve 00:33:07.610 --> 00:33:07.620 align:start position:0% has a quirk that you can destroy Eve 00:33:07.620 --> 00:33:08.510 align:start position:0% has a quirk that you can destroy Eve with<00:33:07.740> that 00:33:08.510 --> 00:33:08.520 align:start position:0% with that 00:33:08.520 --> 00:33:11.090 align:start position:0% with that and<00:33:09.000> the<00:33:09.179> question<00:33:09.360> if<00:33:09.840> if<00:33:10.260> we<00:33:10.799> want<00:33:10.919> to 00:33:11.090 --> 00:33:11.100 align:start position:0% and the question if if we want to 00:33:11.100 --> 00:33:12.769 align:start position:0% and the question if if we want to actually<00:33:11.460> like 00:33:12.769 --> 00:33:12.779 align:start position:0% actually like 00:33:12.779 --> 00:33:15.049 align:start position:0% actually like to<00:33:13.080> make<00:33:13.380> the<00:33:13.559> the<00:33:13.799> scent<00:33:14.039> all<00:33:14.340> work<00:33:14.580> the<00:33:14.940> same 00:33:15.049 --> 00:33:15.059 align:start position:0% to make the the scent all work the same 00:33:15.059 --> 00:33:17.630 align:start position:0% to make the the scent all work the same way<00:33:15.240> or<00:33:15.600> we<00:33:15.779> want<00:33:15.960> to<00:33:16.140> kind<00:33:16.440> of<00:33:16.559> fix<00:33:16.799> it<00:33:17.039> and 00:33:17.630 --> 00:33:17.640 align:start position:0% way or we want to kind of fix it and 00:33:17.640 --> 00:33:21.529 align:start position:0% way or we want to kind of fix it and make<00:33:17.880> it<00:33:18.539> more<00:33:18.980> intuitive<00:33:19.980> I<00:33:20.279> think<00:33:20.460> so<00:33:21.000> I 00:33:21.529 --> 00:33:21.539 align:start position:0% make it more intuitive I think so I 00:33:21.539 --> 00:33:23.210 align:start position:0% make it more intuitive I think so I think<00:33:21.659> it's<00:33:21.899> kind<00:33:22.200> of<00:33:22.380> the<00:33:22.620> the<00:33:22.919> choice 00:33:23.210 --> 00:33:23.220 align:start position:0% think it's kind of the the choice 00:33:23.220 --> 00:33:25.009 align:start position:0% think it's kind of the the choice between<00:33:23.580> like<00:33:24.059> more<00:33:24.419> backwards 00:33:25.009 --> 00:33:25.019 align:start position:0% between like more backwards 00:33:25.019 --> 00:33:27.830 align:start position:0% between like more backwards compatibility<00:33:25.740> between<00:33:26.519> something<00:33:27.000> that<00:33:27.659> is 00:33:27.830 --> 00:33:27.840 align:start position:0% compatibility between something that is 00:33:27.840 --> 00:33:32.090 align:start position:0% compatibility between something that is more<00:33:28.080> obvious<00:33:28.320> how<00:33:28.679> it<00:33:28.799> works 00:33:32.090 --> 00:33:32.100 align:start position:0% 00:33:32.100 --> 00:33:33.289 align:start position:0% oh 00:33:33.289 --> 00:33:33.299 align:start position:0% oh 00:33:33.299 --> 00:33:37.909 align:start position:0% oh so<00:33:33.960> the<00:33:34.200> way<00:33:34.440> I<00:33:34.679> implemented<00:33:35.159> it<00:33:35.399> now<00:33:35.880> it<00:33:37.260> um 00:33:37.909 --> 00:33:37.919 align:start position:0% so the way I implemented it now it um 00:33:37.919 --> 00:33:42.950 align:start position:0% so the way I implemented it now it um just<00:33:38.640> it<00:33:38.880> doesn't<00:33:39.059> destroy<00:33:39.539> it<00:33:39.659> either<00:33:40.159> so<00:33:41.159> it 00:33:42.950 --> 00:33:42.960 align:start position:0% just it doesn't destroy it either so it 00:33:42.960 --> 00:33:45.850 align:start position:0% just it doesn't destroy it either so it and<00:33:43.380> and<00:33:43.440> the<00:33:44.399> idea<00:33:44.519> for<00:33:44.880> everyone<00:33:45.059> the<00:33:45.600> final 00:33:45.850 --> 00:33:45.860 align:start position:0% and and the idea for everyone the final 00:33:45.860 --> 00:33:48.730 align:start position:0% and and the idea for everyone the final implementation<00:33:46.860> right 00:33:48.730 --> 00:33:48.740 align:start position:0% implementation right 00:33:48.740 --> 00:33:51.950 align:start position:0% implementation right the<00:33:49.740> first<00:33:49.860> implementation<00:33:50.460> was<00:33:50.760> okay<00:33:51.179> and<00:33:51.480> uh 00:33:51.950 --> 00:33:51.960 align:start position:0% the first implementation was okay and uh 00:33:51.960 --> 00:33:53.330 align:start position:0% the first implementation was okay and uh for<00:33:52.260> everyone<00:33:52.380> in<00:33:52.620> the<00:33:52.740> room<00:33:52.860> we<00:33:53.039> are<00:33:53.220> not 00:33:53.330 --> 00:33:53.340 align:start position:0% for everyone in the room we are not 00:33:53.340 --> 00:33:55.009 align:start position:0% for everyone in the room we are not trying<00:33:53.640> to<00:33:53.760> remove<00:33:53.940> self-destruct<00:33:54.659> but<00:33:54.899> we're 00:33:55.009 --> 00:33:55.019 align:start position:0% trying to remove self-destruct but we're 00:33:55.019 --> 00:33:57.409 align:start position:0% trying to remove self-destruct but we're changing<00:33:55.440> it<00:33:55.620> uh<00:33:56.279> so<00:33:56.519> that 00:33:57.409 --> 00:33:57.419 align:start position:0% changing it uh so that 00:33:57.419 --> 00:33:59.690 align:start position:0% changing it uh so that um<00:33:57.539> so<00:33:57.899> that<00:33:58.200> the<00:33:58.740> self-destruct<00:33:59.220> will<00:33:59.519> just 00:33:59.690 --> 00:33:59.700 align:start position:0% um so that the self-destruct will just 00:33:59.700 --> 00:34:01.430 align:start position:0% um so that the self-destruct will just send<00:33:59.940> all<00:34:00.120> of<00:34:00.299> The<00:34:00.419> Ether 00:34:01.430 --> 00:34:01.440 align:start position:0% send all of The Ether 00:34:01.440 --> 00:34:03.230 align:start position:0% send all of The Ether um<00:34:01.500> that<00:34:01.740> is<00:34:01.799> in<00:34:01.919> the<00:34:02.100> contract 00:34:03.230 --> 00:34:03.240 align:start position:0% um that is in the contract 00:34:03.240 --> 00:34:05.090 align:start position:0% um that is in the contract and<00:34:03.779> the<00:34:03.960> but<00:34:04.140> the<00:34:04.320> contract<00:34:04.500> itself<00:34:04.860> will 00:34:05.090 --> 00:34:05.100 align:start position:0% and the but the contract itself will 00:34:05.100 --> 00:34:05.870 align:start position:0% and the but the contract itself will stay 00:34:05.870 --> 00:34:05.880 align:start position:0% stay 00:34:05.880 --> 00:34:09.409 align:start position:0% stay and<00:34:06.600> so<00:34:06.899> so<00:34:07.019> it's<00:34:07.620> like<00:34:08.040> it<00:34:08.280> will<00:34:08.639> keep<00:34:08.940> the 00:34:09.409 --> 00:34:09.419 align:start position:0% and so so it's like it will keep the 00:34:09.419 --> 00:34:12.589 align:start position:0% and so so it's like it will keep the current<00:34:10.200> way<00:34:10.500> the<00:34:10.919> only<00:34:11.099> the<00:34:11.460> only<00:34:11.639> thing<00:34:12.000> that 00:34:12.589 --> 00:34:12.599 align:start position:0% current way the only the only thing that 00:34:12.599 --> 00:34:15.530 align:start position:0% current way the only the only thing that is<00:34:12.960> kind<00:34:13.320> of<00:34:13.440> iffy<00:34:13.859> about<00:34:13.980> it<00:34:14.280> is<00:34:15.000> there's<00:34:15.240> some 00:34:15.530 --> 00:34:15.540 align:start position:0% is kind of iffy about it is there's some 00:34:15.540 --> 00:34:17.570 align:start position:0% is kind of iffy about it is there's some pattern<00:34:15.839> where<00:34:16.080> you<00:34:16.260> self-destruct<00:34:16.800> and 00:34:17.570 --> 00:34:17.580 align:start position:0% pattern where you self-destruct and 00:34:17.580 --> 00:34:21.290 align:start position:0% pattern where you self-destruct and create<00:34:17.820> uh<00:34:18.540> to<00:34:18.780> uh<00:34:19.440> uh<00:34:19.919> contract<00:34:20.700> but<00:34:21.119> there 00:34:21.290 --> 00:34:21.300 align:start position:0% create uh to uh uh contract but there 00:34:21.300 --> 00:34:24.409 align:start position:0% create uh to uh uh contract but there have<00:34:21.480> been<00:34:21.659> an<00:34:21.960> analysis<00:34:22.800> about<00:34:23.280> it<00:34:23.580> and<00:34:24.179> it 00:34:24.409 --> 00:34:24.419 align:start position:0% have been an analysis about it and it 00:34:24.419 --> 00:34:27.649 align:start position:0% have been an analysis about it and it doesn't<00:34:24.599> break<00:34:25.139> too<00:34:25.500> much<00:34:25.679> stuff 00:34:27.649 --> 00:34:27.659 align:start position:0% doesn't break too much stuff 00:34:27.659 --> 00:34:29.869 align:start position:0% doesn't break too much stuff and<00:34:28.260> and<00:34:28.320> we<00:34:29.040> and<00:34:29.159> we<00:34:29.339> talk<00:34:29.460> to<00:34:29.580> the<00:34:29.760> people 00:34:29.869 --> 00:34:29.879 align:start position:0% and and we and we talk to the people 00:34:29.879 --> 00:34:33.109 align:start position:0% and and we and we talk to the people that<00:34:30.300> that<00:34:30.839> we<00:34:31.500> would<00:34:31.619> break<00:34:31.859> with<00:34:32.099> it<00:34:32.399> and<00:34:32.879> uh 00:34:33.109 --> 00:34:33.119 align:start position:0% that that we would break with it and uh 00:34:33.119 --> 00:34:35.869 align:start position:0% that that we would break with it and uh they<00:34:33.659> seem<00:34:33.839> to<00:34:34.020> be<00:34:34.679> okay<00:34:34.859> with<00:34:35.099> it<00:34:35.220> how<00:34:35.760> did 00:34:35.869 --> 00:34:35.879 align:start position:0% they seem to be okay with it how did 00:34:35.879 --> 00:34:41.629 align:start position:0% they seem to be okay with it how did gasto<00:34:36.300> can<00:34:36.480> take<00:34:36.599> it 00:34:41.629 --> 00:34:41.639 align:start position:0% 00:34:41.639 --> 00:34:45.470 align:start position:0% um<00:34:41.760> okay<00:34:42.240> uh<00:34:42.899> beside<00:34:43.320> you<00:34:43.500> Proto<00:34:44.280> uh<00:34:45.000> sorry<00:34:45.359> I 00:34:45.470 --> 00:34:45.480 align:start position:0% um okay uh beside you Proto uh sorry I 00:34:45.480 --> 00:34:46.609 align:start position:0% um okay uh beside you Proto uh sorry I don't<00:34:45.540> know<00:34:45.659> your<00:34:45.780> name<00:34:45.899> uh<00:34:46.139> you<00:34:46.379> don't<00:34:46.440> think 00:34:46.609 --> 00:34:46.619 align:start position:0% don't know your name uh you don't think 00:34:46.619 --> 00:34:51.649 align:start position:0% don't know your name uh you don't think that's<00:34:46.919> back<00:34:47.639> yeah<00:34:48.899> um<00:34:48.899> Ronan<00:34:49.619> uh<00:34:50.220> I<00:34:50.700> basically 00:34:51.649 --> 00:34:51.659 align:start position:0% that's back yeah um Ronan uh I basically 00:34:51.659 --> 00:34:55.250 align:start position:0% that's back yeah um Ronan uh I basically build<00:34:52.139> the<00:34:52.440> own<00:34:53.040> chain<00:34:53.280> games<00:34:53.639> uh<00:34:54.540> and 00:34:55.250 --> 00:34:55.260 align:start position:0% build the own chain games uh and 00:34:55.260 --> 00:34:58.310 align:start position:0% build the own chain games uh and basically<00:34:55.919> also<00:34:56.879> other<00:34:57.060> application<00:34:57.540> uh<00:34:58.200> many 00:34:58.310 --> 00:34:58.320 align:start position:0% basically also other application uh many 00:34:58.320 --> 00:35:00.170 align:start position:0% basically also other application uh many things<00:34:58.560> actually<00:34:58.800> but 00:35:00.170 --> 00:35:00.180 align:start position:0% things actually but 00:35:00.180 --> 00:35:02.870 align:start position:0% things actually but um<00:35:00.240> and<00:35:00.839> by<00:35:01.080> that<00:35:01.260> I<00:35:01.440> mean<00:35:01.619> application<00:35:02.580> or 00:35:02.870 --> 00:35:02.880 align:start position:0% um and by that I mean application or 00:35:02.880 --> 00:35:05.890 align:start position:0% um and by that I mean application or games<00:35:03.119> that<00:35:03.599> have<00:35:04.020> a<00:35:04.260> zero<00:35:04.619> back-end<00:35:04.980> and 00:35:05.890 --> 00:35:05.900 align:start position:0% games that have a zero back-end and 00:35:05.900 --> 00:35:10.430 align:start position:0% games that have a zero back-end and where<00:35:06.900> uh<00:35:07.380> the<00:35:07.560> user<00:35:07.920> player<00:35:08.820> uh<00:35:09.720> provide 00:35:10.430 --> 00:35:10.440 align:start position:0% where uh the user player uh provide 00:35:10.440 --> 00:35:12.170 align:start position:0% where uh the user player uh provide their<00:35:10.560> own<00:35:10.740> node<00:35:10.980> through<00:35:11.339> the<00:35:11.579> wallet<00:35:12.000> the 00:35:12.170 --> 00:35:12.180 align:start position:0% their own node through the wallet the 00:35:12.180 --> 00:35:13.069 align:start position:0% their own node through the wallet the truth 00:35:13.069 --> 00:35:13.079 align:start position:0% truth 00:35:13.079 --> 00:35:15.470 align:start position:0% truth and<00:35:13.800> in<00:35:14.040> that<00:35:14.220> context 00:35:15.470 --> 00:35:15.480 align:start position:0% and in that context 00:35:15.480 --> 00:35:16.130 align:start position:0% and in that context um 00:35:16.130 --> 00:35:16.140 align:start position:0% um 00:35:16.140 --> 00:35:18.829 align:start position:0% um I<00:35:16.740> am<00:35:16.920> building<00:35:17.160> an<00:35:17.640> indexer<00:35:18.180> that<00:35:18.420> runs<00:35:18.720> in 00:35:18.829 --> 00:35:18.839 align:start position:0% I am building an indexer that runs in 00:35:18.839 --> 00:35:20.930 align:start position:0% I am building an indexer that runs in the<00:35:19.020> browser 00:35:20.930 --> 00:35:20.940 align:start position:0% the browser 00:35:20.940 --> 00:35:23.510 align:start position:0% the browser um<00:35:21.060> and<00:35:21.060> so<00:35:21.480> you<00:35:21.839> can<00:35:22.020> fetch<00:35:22.320> the<00:35:22.440> logs<00:35:22.800> and<00:35:23.400> it 00:35:23.510 --> 00:35:23.520 align:start position:0% um and so you can fetch the logs and it 00:35:23.520 --> 00:35:25.910 align:start position:0% um and so you can fetch the logs and it will<00:35:23.700> all<00:35:23.880> fine<00:35:24.119> and<00:35:25.020> but<00:35:25.260> some<00:35:25.440> application 00:35:25.910 --> 00:35:25.920 align:start position:0% will all fine and but some application 00:35:25.920 --> 00:35:29.210 align:start position:0% will all fine and but some application of<00:35:26.220> game<00:35:26.400> rely<00:35:26.880> on<00:35:27.060> time<00:35:27.359> information 00:35:29.210 --> 00:35:29.220 align:start position:0% of game rely on time information 00:35:29.220 --> 00:35:30.230 align:start position:0% of game rely on time information and 00:35:30.230 --> 00:35:30.240 align:start position:0% and 00:35:30.240 --> 00:35:34.250 align:start position:0% and most<00:35:31.020> developer<00:35:31.880> assume<00:35:32.880> rightly<00:35:33.480> that<00:35:34.079> the 00:35:34.250 --> 00:35:34.260 align:start position:0% most developer assume rightly that the 00:35:34.260 --> 00:35:36.230 align:start position:0% most developer assume rightly that the timestamp<00:35:34.619> is<00:35:34.800> available<00:35:34.980> and<00:35:35.760> so<00:35:35.940> they<00:35:36.060> don't 00:35:36.230 --> 00:35:36.240 align:start position:0% timestamp is available and so they don't 00:35:36.240 --> 00:35:37.790 align:start position:0% timestamp is available and so they don't need<00:35:36.359> to<00:35:36.480> add<00:35:36.599> the<00:35:36.780> timestamp<00:35:37.200> in<00:35:37.500> the<00:35:37.619> event 00:35:37.790 --> 00:35:37.800 align:start position:0% need to add the timestamp in the event 00:35:37.800 --> 00:35:41.290 align:start position:0% need to add the timestamp in the event that<00:35:38.280> they<00:35:38.460> emit<00:35:39.200> unfortunately<00:35:40.200> the<00:35:40.800> logs 00:35:41.290 --> 00:35:41.300 align:start position:0% that they emit unfortunately the logs 00:35:41.300 --> 00:35:44.530 align:start position:0% that they emit unfortunately the logs don't<00:35:42.300> contain<00:35:42.720> the<00:35:43.500> timestamp<00:35:43.920> information 00:35:44.530 --> 00:35:44.540 align:start position:0% don't contain the timestamp information 00:35:44.540 --> 00:35:46.670 align:start position:0% don't contain the timestamp information and<00:35:45.540> so 00:35:46.670 --> 00:35:46.680 align:start position:0% and so 00:35:46.680 --> 00:35:49.130 align:start position:0% and so in<00:35:47.220> my<00:35:47.280> game<00:35:47.460> for<00:35:47.700> example<00:35:47.940> like<00:35:48.240> 20<00:35:49.020> 000 00:35:49.130 --> 00:35:49.140 align:start position:0% in my game for example like 20 000 00:35:49.140 --> 00:35:51.589 align:start position:0% in my game for example like 20 000 events<00:35:49.800> I<00:35:50.220> can<00:35:50.339> fetch<00:35:50.700> them<00:35:50.880> very<00:35:51.240> quickly 00:35:51.589 --> 00:35:51.599 align:start position:0% events I can fetch them very quickly 00:35:51.599 --> 00:35:54.349 align:start position:0% events I can fetch them very quickly like<00:35:51.900> in<00:35:52.140> five<00:35:52.500> seconds<00:35:52.800> it's<00:35:53.339> all<00:35:53.760> all<00:35:54.119> the 00:35:54.349 --> 00:35:54.359 align:start position:0% like in five seconds it's all all the 00:35:54.359 --> 00:35:58.490 align:start position:0% like in five seconds it's all all the state<00:35:54.540> is<00:35:54.780> synced<00:35:55.200> but<00:35:55.980> if<00:35:56.820> I<00:35:57.000> have<00:35:57.180> to<00:35:57.599> uh<00:35:58.140> add 00:35:58.490 --> 00:35:58.500 align:start position:0% state is synced but if I have to uh add 00:35:58.500 --> 00:36:01.250 align:start position:0% state is synced but if I have to uh add the<00:35:58.740> timestamp<00:35:59.339> then<00:35:59.820> I<00:36:00.000> need<00:36:00.119> to<00:36:00.240> make<00:36:00.480> 20<00:36:01.140> 000 00:36:01.250 --> 00:36:01.260 align:start position:0% the timestamp then I need to make 20 000 00:36:01.260 --> 00:36:05.089 align:start position:0% the timestamp then I need to make 20 000 more<00:36:01.500> requests<00:36:02.240> and<00:36:03.240> account<00:36:04.079> even<00:36:04.440> batch<00:36:04.920> it 00:36:05.089 --> 00:36:05.099 align:start position:0% more requests and account even batch it 00:36:05.099 --> 00:36:07.990 align:start position:0% more requests and account even batch it because<00:36:05.460> uh<00:36:06.260> eip1193<00:36:07.260> which<00:36:07.500> is<00:36:07.619> only 00:36:07.990 --> 00:36:08.000 align:start position:0% because uh eip1193 which is only 00:36:08.000 --> 00:36:11.870 align:start position:0% because uh eip1193 which is only interface<00:36:09.440> I<00:36:10.440> have<00:36:10.560> cannot<00:36:11.400> do<00:36:11.460> that<00:36:11.579> so<00:36:11.700> the 00:36:11.870 --> 00:36:11.880 align:start position:0% interface I have cannot do that so the 00:36:11.880 --> 00:36:13.849 align:start position:0% interface I have cannot do that so the idea<00:36:12.180> is<00:36:12.359> a<00:36:12.599> very<00:36:12.720> simple<00:36:12.900> proposal<00:36:13.440> is<00:36:13.619> simply 00:36:13.849 --> 00:36:13.859 align:start position:0% idea is a very simple proposal is simply 00:36:13.859 --> 00:36:15.650 align:start position:0% idea is a very simple proposal is simply to<00:36:13.980> add<00:36:14.160> the<00:36:14.280> Block<00:36:14.460> timestamp<00:36:15.000> in<00:36:15.240> the<00:36:15.359> logged 00:36:15.650 --> 00:36:15.660 align:start position:0% to add the Block timestamp in the logged 00:36:15.660 --> 00:36:18.349 align:start position:0% to add the Block timestamp in the logged object<00:36:15.960> when<00:36:16.800> you<00:36:16.920> query<00:36:17.220> the<00:36:17.460> logs<00:36:17.760> and 00:36:18.349 --> 00:36:18.359 align:start position:0% object when you query the logs and 00:36:18.359 --> 00:36:19.849 align:start position:0% object when you query the logs and actually<00:36:18.540> someone<00:36:18.839> will<00:36:19.140> say<00:36:19.260> you<00:36:19.560> we<00:36:19.740> could 00:36:19.849 --> 00:36:19.859 align:start position:0% actually someone will say you we could 00:36:19.859 --> 00:36:20.930 align:start position:0% actually someone will say you we could also<00:36:20.040> add<00:36:20.160> the<00:36:20.280> timestamp<00:36:20.640> to<00:36:20.820> the 00:36:20.930 --> 00:36:20.940 align:start position:0% also add the timestamp to the 00:36:20.940 --> 00:36:23.569 align:start position:0% also add the timestamp to the transaction<00:36:21.240> received<00:36:22.020> Etc<00:36:22.280> but<00:36:23.280> basically 00:36:23.569 --> 00:36:23.579 align:start position:0% transaction received Etc but basically 00:36:23.579 --> 00:36:26.630 align:start position:0% transaction received Etc but basically yeah<00:36:23.820> adding<00:36:24.359> the<00:36:24.540> time<00:36:24.780> some<00:36:25.020> information 00:36:26.630 --> 00:36:26.640 align:start position:0% yeah adding the time some information 00:36:26.640 --> 00:36:30.050 align:start position:0% yeah adding the time some information so<00:36:27.359> one<00:36:27.720> of<00:36:27.900> my<00:36:28.200> uh<00:36:28.740> questions<00:36:29.099> here<00:36:29.520> is<00:36:29.760> that 00:36:30.050 --> 00:36:30.060 align:start position:0% so one of my uh questions here is that 00:36:30.060 --> 00:36:32.870 align:start position:0% so one of my uh questions here is that long<00:36:30.839> term<00:36:31.079> the 00:36:32.870 --> 00:36:32.880 align:start position:0% long term the 00:36:32.880 --> 00:36:35.510 align:start position:0% long term the essentially<00:36:33.540> long-term<00:36:34.140> ethereum<00:36:34.560> attempts 00:36:35.510 --> 00:36:35.520 align:start position:0% essentially long-term ethereum attempts 00:36:35.520 --> 00:36:38.329 align:start position:0% essentially long-term ethereum attempts to<00:36:35.760> remove<00:36:36.300> access<00:36:36.720> from<00:36:37.260> old<00:36:37.440> chain<00:36:37.740> segments 00:36:38.329 --> 00:36:38.339 align:start position:0% to remove access from old chain segments 00:36:38.339 --> 00:36:40.970 align:start position:0% to remove access from old chain segments and<00:36:39.300> ideally<00:36:39.720> I<00:36:40.140> would<00:36:40.260> also<00:36:40.619> completely 00:36:40.970 --> 00:36:40.980 align:start position:0% and ideally I would also completely 00:36:40.980 --> 00:36:43.609 align:start position:0% and ideally I would also completely remove<00:36:41.220> access<00:36:41.579> from<00:36:42.180> law<00:36:42.720> accessing<00:36:43.260> logs 00:36:43.609 --> 00:36:43.619 align:start position:0% remove access from law accessing logs 00:36:43.619 --> 00:36:45.950 align:start position:0% remove access from law accessing logs that<00:36:43.800> are<00:36:43.980> older<00:36:44.339> than 00:36:45.950 --> 00:36:45.960 align:start position:0% that are older than 00:36:45.960 --> 00:36:47.810 align:start position:0% that are older than I<00:36:46.500> don't<00:36:46.560> know<00:36:46.680> I<00:36:46.920> would<00:36:47.040> remove<00:36:47.220> I<00:36:47.579> would<00:36:47.700> say 00:36:47.810 --> 00:36:47.820 align:start position:0% I don't know I would remove I would say 00:36:47.820 --> 00:36:49.609 align:start position:0% I don't know I would remove I would say a<00:36:48.000> month<00:36:48.119> three<00:36:48.359> months<00:36:48.660> something<00:36:49.140> fairly 00:36:49.609 --> 00:36:49.619 align:start position:0% a month three months something fairly 00:36:49.619 --> 00:36:50.450 align:start position:0% a month three months something fairly High 00:36:50.450 --> 00:36:50.460 align:start position:0% High 00:36:50.460 --> 00:36:53.050 align:start position:0% High so<00:36:51.000> uh<00:36:51.720> essentially 00:36:53.050 --> 00:36:53.060 align:start position:0% so uh essentially 00:36:53.060 --> 00:36:56.089 align:start position:0% so uh essentially I<00:36:54.060> mean<00:36:54.180> is<00:36:54.780> it<00:36:55.020> already<00:36:55.320> your<00:36:55.619> consensus 00:36:56.089 --> 00:36:56.099 align:start position:0% I mean is it already your consensus 00:36:56.099 --> 00:36:58.730 align:start position:0% I mean is it already your consensus because<00:36:56.520> we<00:36:57.240> talked<00:36:57.420> because<00:36:57.540> I<00:36:58.260> feel<00:36:58.320> we<00:36:58.619> are 00:36:58.730 --> 00:36:58.740 align:start position:0% because we talked because I feel we are 00:36:58.740 --> 00:37:03.910 align:start position:0% because we talked because I feel we are talking<00:36:58.859> now<00:36:59.160> about<00:36:59.339> another<00:36:59.760> thing<00:37:00.240> like 00:37:03.910 --> 00:37:03.920 align:start position:0% 00:37:03.920 --> 00:37:07.310 align:start position:0% so<00:37:04.920> what<00:37:05.220> I<00:37:05.400> was<00:37:05.520> getting<00:37:05.700> at<00:37:05.880> is<00:37:06.180> that<00:37:06.480> uh<00:37:06.780> this 00:37:07.310 --> 00:37:07.320 align:start position:0% so what I was getting at is that uh this 00:37:07.320 --> 00:37:09.230 align:start position:0% so what I was getting at is that uh this is<00:37:07.500> kind<00:37:07.800> of<00:37:07.920> a<00:37:08.040> consensus<00:37:08.460> in<00:37:08.640> ethereum<00:37:09.000> that 00:37:09.230 --> 00:37:09.240 align:start position:0% is kind of a consensus in ethereum that 00:37:09.240 --> 00:37:11.510 align:start position:0% is kind of a consensus in ethereum that the<00:37:09.900> past<00:37:10.440> chain<00:37:10.740> segments<00:37:11.220> needs<00:37:11.400> to<00:37:11.460> be 00:37:11.510 --> 00:37:11.520 align:start position:0% the past chain segments needs to be 00:37:11.520 --> 00:37:12.829 align:start position:0% the past chain segments needs to be pruned<00:37:11.820> otherwise<00:37:12.180> the<00:37:12.420> the<00:37:12.660> network 00:37:12.829 --> 00:37:12.839 align:start position:0% pruned otherwise the the network 00:37:12.839 --> 00:37:16.130 align:start position:0% pruned otherwise the the network implodes<00:37:13.380> and<00:37:14.099> in<00:37:14.339> from<00:37:14.640> that<00:37:14.760> perspective<00:37:15.180> uh 00:37:16.130 --> 00:37:16.140 align:start position:0% implodes and in from that perspective uh 00:37:16.140 --> 00:37:18.230 align:start position:0% implodes and in from that perspective uh the<00:37:16.380> amount<00:37:16.740> of<00:37:16.859> logs<00:37:17.280> you<00:37:17.400> will<00:37:17.579> have<00:37:17.760> to 00:37:18.230 --> 00:37:18.240 align:start position:0% the amount of logs you will have to 00:37:18.240 --> 00:37:21.290 align:start position:0% the amount of logs you will have to access<00:37:18.480> is<00:37:19.140> more<00:37:20.040> limited<00:37:20.520> so<00:37:20.760> it<00:37:20.940> might<00:37:21.119> not 00:37:21.290 --> 00:37:21.300 align:start position:0% access is more limited so it might not 00:37:21.300 --> 00:37:24.290 align:start position:0% access is more limited so it might not be<00:37:21.780> that<00:37:22.440> big<00:37:22.560> of<00:37:22.800> an<00:37:22.980> issue<00:37:23.280> not<00:37:23.640> to<00:37:23.820> I<00:37:24.180> mean 00:37:24.290 --> 00:37:24.300 align:start position:0% be that big of an issue not to I mean 00:37:24.300 --> 00:37:26.750 align:start position:0% be that big of an issue not to I mean you<00:37:24.839> could<00:37:25.020> always<00:37:25.320> retrieve<00:37:26.040> the<00:37:26.099> timestamps 00:37:26.750 --> 00:37:26.760 align:start position:0% you could always retrieve the timestamps 00:37:26.760 --> 00:37:29.150 align:start position:0% you could always retrieve the timestamps if<00:37:27.000> if<00:37:27.359> you<00:37:27.599> have<00:37:27.720> a<00:37:27.900> bounded<00:37:28.440> number<00:37:28.619> of<00:37:28.740> logs 00:37:29.150 --> 00:37:29.160 align:start position:0% if if you have a bounded number of logs 00:37:29.160 --> 00:37:31.730 align:start position:0% if if you have a bounded number of logs you<00:37:29.339> can<00:37:29.520> access<00:37:29.900> don't<00:37:30.900> you<00:37:31.079> think<00:37:31.260> that<00:37:31.500> if 00:37:31.730 --> 00:37:31.740 align:start position:0% you can access don't you think that if 00:37:31.740 --> 00:37:34.490 align:start position:0% you can access don't you think that if we<00:37:31.859> go<00:37:32.040> to<00:37:32.160> that<00:37:32.400> stage<00:37:32.700> uh<00:37:33.420> the<00:37:33.660> the<00:37:33.960> wallet 00:37:34.490 --> 00:37:34.500 align:start position:0% we go to that stage uh the the wallet 00:37:34.500 --> 00:37:37.370 align:start position:0% we go to that stage uh the the wallet interface<00:37:34.920> will<00:37:35.160> also<00:37:35.460> evolve<00:37:35.940> uh<00:37:36.780> with<00:37:37.140> a 00:37:37.370 --> 00:37:37.380 align:start position:0% interface will also evolve uh with a 00:37:37.380 --> 00:37:38.930 align:start position:0% interface will also evolve uh with a different<00:37:37.619> mechanism<00:37:38.220> so<00:37:38.579> that<00:37:38.760> the 00:37:38.930 --> 00:37:38.940 align:start position:0% different mechanism so that the 00:37:38.940 --> 00:37:41.690 align:start position:0% different mechanism so that the application<00:37:39.359> can<00:37:39.720> remain<00:37:40.020> decentralized 00:37:41.690 --> 00:37:41.700 align:start position:0% application can remain decentralized 00:37:41.700 --> 00:37:43.910 align:start position:0% application can remain decentralized or<00:37:42.240> are<00:37:42.420> you<00:37:42.540> giving<00:37:42.720> up<00:37:43.020> on<00:37:43.560> complete 00:37:43.910 --> 00:37:43.920 align:start position:0% or are you giving up on complete 00:37:43.920 --> 00:37:45.650 align:start position:0% or are you giving up on complete decentralization 00:37:45.650 --> 00:37:45.660 align:start position:0% decentralization 00:37:45.660 --> 00:37:48.230 align:start position:0% decentralization from<00:37:46.140> the<00:37:46.320> application<00:37:46.740> point<00:37:46.980> of<00:37:47.160> view<00:37:47.280> I'm<00:37:47.760> I 00:37:48.230 --> 00:37:48.240 align:start position:0% from the application point of view I'm I 00:37:48.240 --> 00:37:50.990 align:start position:0% from the application point of view I'm I don't<00:37:48.660> understand<00:37:48.839> what<00:37:49.260> because<00:37:49.680> like<00:37:50.280> most 00:37:50.990 --> 00:37:51.000 align:start position:0% don't understand what because like most 00:37:51.000 --> 00:37:53.030 align:start position:0% don't understand what because like most applications<00:37:51.480> we<00:37:52.020> kind<00:37:52.200> of<00:37:52.380> as<00:37:52.560> a<00:37:52.740> developer 00:37:53.030 --> 00:37:53.040 align:start position:0% applications we kind of as a developer 00:37:53.040 --> 00:37:55.970 align:start position:0% applications we kind of as a developer we<00:37:53.280> understand<00:37:53.820> that<00:37:54.240> we<00:37:54.720> need<00:37:54.839> to<00:37:55.020> index<00:37:55.440> the 00:37:55.970 --> 00:37:55.980 align:start position:0% we understand that we need to index the 00:37:55.980 --> 00:37:59.030 align:start position:0% we understand that we need to index the data<00:37:56.339> and<00:37:56.700> that's<00:37:56.820> why<00:37:57.000> we<00:37:57.180> use<00:37:57.300> event 00:37:59.030 --> 00:37:59.040 align:start position:0% data and that's why we use event 00:37:59.040 --> 00:38:01.190 align:start position:0% data and that's why we use event um<00:37:59.099> but<00:37:59.460> okay<00:37:59.820> so<00:38:00.119> I<00:38:00.359> think<00:38:00.480> events<00:38:01.079> are 00:38:01.190 --> 00:38:01.200 align:start position:0% um but okay so I think events are 00:38:01.200 --> 00:38:02.990 align:start position:0% um but okay so I think events are completely<00:38:01.500> being<00:38:01.680> misused<00:38:02.339> and<00:38:02.579> they<00:38:02.880> are 00:38:02.990 --> 00:38:03.000 align:start position:0% completely being misused and they are 00:38:03.000 --> 00:38:06.050 align:start position:0% completely being misused and they are used<00:38:03.119> as<00:38:03.240> a<00:38:03.359> database<00:38:03.720> instead<00:38:04.200> of<00:38:04.320> events<00:38:05.400> and 00:38:06.050 --> 00:38:06.060 align:start position:0% used as a database instead of events and 00:38:06.060 --> 00:38:07.970 align:start position:0% used as a database instead of events and uh<00:38:06.300> in<00:38:06.660> my<00:38:06.780> opinion<00:38:07.020> ethereum<00:38:07.440> should<00:38:07.680> use<00:38:07.859> it 00:38:07.970 --> 00:38:07.980 align:start position:0% uh in my opinion ethereum should use it 00:38:07.980 --> 00:38:11.150 align:start position:0% uh in my opinion ethereum should use it as<00:38:08.099> events<00:38:08.520> and<00:38:08.940> should<00:38:09.720> everybody<00:38:10.560> ask<00:38:10.920> you 00:38:11.150 --> 00:38:11.160 align:start position:0% as events and should everybody ask you 00:38:11.160 --> 00:38:13.069 align:start position:0% as events and should everybody ask you the<00:38:11.280> tabs<00:38:11.640> but<00:38:11.820> that's<00:38:11.940> my<00:38:12.119> two<00:38:12.240> cents<00:38:12.480> what<00:38:13.020> do 00:38:13.069 --> 00:38:13.079 align:start position:0% the tabs but that's my two cents what do 00:38:13.079 --> 00:38:15.890 align:start position:0% the tabs but that's my two cents what do you<00:38:13.140> mean<00:38:13.260> by<00:38:13.440> using<00:38:13.859> as<00:38:14.099> event<00:38:14.400> so<00:38:15.060> by<00:38:15.420> event<00:38:15.599> I 00:38:15.890 --> 00:38:15.900 align:start position:0% you mean by using as event so by event I 00:38:15.900 --> 00:38:18.890 align:start position:0% you mean by using as event so by event I mean<00:38:16.079> that<00:38:16.260> that<00:38:16.880> emits<00:38:17.880> something<00:38:18.000> and 00:38:18.890 --> 00:38:18.900 align:start position:0% mean that that emits something and 00:38:18.900 --> 00:38:21.290 align:start position:0% mean that that emits something and anybody<00:38:19.440> interacting<00:38:20.040> with<00:38:20.160> adapt<00:38:20.520> can<00:38:20.760> react 00:38:21.290 --> 00:38:21.300 align:start position:0% anybody interacting with adapt can react 00:38:21.300 --> 00:38:24.349 align:start position:0% anybody interacting with adapt can react to<00:38:21.420> it<00:38:21.599> within<00:38:22.020> a<00:38:22.200> specific<00:38:22.500> time<00:38:23.160> frame<00:38:23.940> but 00:38:24.349 --> 00:38:24.359 align:start position:0% to it within a specific time frame but 00:38:24.359 --> 00:38:26.690 align:start position:0% to it within a specific time frame but not<00:38:24.599> to<00:38:25.020> look<00:38:25.140> up<00:38:25.320> events<00:38:25.800> that<00:38:25.980> happened<00:38:26.220> 10 00:38:26.690 --> 00:38:26.700 align:start position:0% not to look up events that happened 10 00:38:26.700 --> 00:38:28.490 align:start position:0% not to look up events that happened 10 years<00:38:26.940> ago<00:38:27.240> because<00:38:27.480> that's<00:38:27.780> that's<00:38:28.020> not<00:38:28.320> an 00:38:28.490 --> 00:38:28.500 align:start position:0% years ago because that's that's not an 00:38:28.500 --> 00:38:30.530 align:start position:0% years ago because that's that's not an event<00:38:28.680> that's<00:38:29.099> a<00:38:29.280> kind<00:38:29.460> of<00:38:29.579> a<00:38:29.700> database<00:38:30.119> at 00:38:30.530 --> 00:38:30.540 align:start position:0% event that's a kind of a database at 00:38:30.540 --> 00:38:32.630 align:start position:0% event that's a kind of a database at that<00:38:30.660> point<00:38:30.839> yeah<00:38:31.500> I<00:38:31.740> mean<00:38:31.920> I<00:38:32.160> have<00:38:32.400> other 00:38:32.630 --> 00:38:32.640 align:start position:0% that point yeah I mean I have other 00:38:32.640 --> 00:38:34.670 align:start position:0% that point yeah I mean I have other common<00:38:32.940> to<00:38:33.180> make<00:38:33.300> because<00:38:33.780> I<00:38:34.260> think<00:38:34.380> it's<00:38:34.500> a 00:38:34.670 --> 00:38:34.680 align:start position:0% common to make because I think it's a 00:38:34.680 --> 00:38:36.950 align:start position:0% common to make because I think it's a bigger<00:38:34.920> discussion<00:38:35.339> like<00:38:35.760> a<00:38:36.359> lot<00:38:36.480> bigger<00:38:36.780> than 00:38:36.950 --> 00:38:36.960 align:start position:0% bigger discussion like a lot bigger than 00:38:36.960 --> 00:38:39.470 align:start position:0% bigger discussion like a lot bigger than what<00:38:37.260> we<00:38:37.440> have<00:38:37.680> time<00:38:38.040> for<00:38:38.280> now<00:38:38.520> but<00:38:38.880> because 00:38:39.470 --> 00:38:39.480 align:start position:0% what we have time for now but because 00:38:39.480 --> 00:38:43.430 align:start position:0% what we have time for now but because I've<00:38:40.020> we<00:38:40.500> have<00:38:41.160> all<00:38:41.880> applications<00:38:42.420> rely<00:38:43.260> on 00:38:43.430 --> 00:38:43.440 align:start position:0% I've we have all applications rely on 00:38:43.440 --> 00:38:45.410 align:start position:0% I've we have all applications rely on this<00:38:43.680> so<00:38:43.920> the<00:38:44.160> reason<00:38:44.339> why<00:38:44.700> we<00:38:45.000> use<00:38:45.180> the<00:38:45.300> event 00:38:45.410 --> 00:38:45.420 align:start position:0% this so the reason why we use the event 00:38:45.420 --> 00:38:47.630 align:start position:0% this so the reason why we use the event of<00:38:45.660> the<00:38:45.720> database<00:38:46.079> is<00:38:46.320> because<00:38:46.500> I<00:38:47.400> mean<00:38:47.520> the 00:38:47.630 --> 00:38:47.640 align:start position:0% of the database is because I mean the 00:38:47.640 --> 00:38:49.550 align:start position:0% of the database is because I mean the typical<00:38:47.880> example<00:38:48.420> is<00:38:48.599> the<00:38:48.720> NFC<00:38:49.200> if<00:38:49.380> you<00:38:49.500> want 00:38:49.550 --> 00:38:49.560 align:start position:0% typical example is the NFC if you want 00:38:49.560 --> 00:38:52.130 align:start position:0% typical example is the NFC if you want to<00:38:49.619> know<00:38:49.800> the<00:38:49.980> list<00:38:50.160> of<00:38:50.339> the<00:38:50.520> token<00:38:50.820> you<00:38:51.000> own<00:38:51.180> uh 00:38:52.130 --> 00:38:52.140 align:start position:0% to know the list of the token you own uh 00:38:52.140 --> 00:38:55.069 align:start position:0% to know the list of the token you own uh you<00:38:52.680> can<00:38:52.859> add<00:38:53.339> and<00:38:53.820> a<00:38:54.000> lot<00:38:54.060> do<00:38:54.359> that<00:38:54.540> they<00:38:54.839> have 00:38:55.069 --> 00:38:55.079 align:start position:0% you can add and a lot do that they have 00:38:55.079 --> 00:38:58.250 align:start position:0% you can add and a lot do that they have this<00:38:55.800> further<00:38:56.520> called<00:38:56.760> Fetch<00:38:57.480> all<00:38:57.599> you<00:38:58.140> know 00:38:58.250 --> 00:38:58.260 align:start position:0% this further called Fetch all you know 00:38:58.260 --> 00:39:00.230 align:start position:0% this further called Fetch all you know by<00:38:58.440> providing<00:38:58.800> the<00:38:59.040> starting<00:38:59.220> index<00:38:59.700> and<00:39:00.060> the 00:39:00.230 --> 00:39:00.240 align:start position:0% by providing the starting index and the 00:39:00.240 --> 00:39:02.390 align:start position:0% by providing the starting index and the lens<00:39:00.480> at<00:39:01.020> which<00:39:01.200> and<00:39:01.500> and<00:39:01.740> you<00:39:01.920> can<00:39:02.040> do<00:39:02.220> that 00:39:02.390 --> 00:39:02.400 align:start position:0% lens at which and and you can do that 00:39:02.400 --> 00:39:04.069 align:start position:0% lens at which and and you can do that but<00:39:02.640> it<00:39:02.880> adds<00:39:03.300> gas<00:39:03.540> codes<00:39:03.780> to<00:39:04.020> the 00:39:04.069 --> 00:39:04.079 align:start position:0% but it adds gas codes to the 00:39:04.079 --> 00:39:05.810 align:start position:0% but it adds gas codes to the implementation<00:39:04.560> and<00:39:05.040> many 00:39:05.810 --> 00:39:05.820 align:start position:0% implementation and many 00:39:05.820 --> 00:39:07.730 align:start position:0% implementation and many decide<00:39:06.359> actually<00:39:06.540> to<00:39:06.780> not<00:39:06.900> do<00:39:07.079> that<00:39:07.260> and<00:39:07.560> use 00:39:07.730 --> 00:39:07.740 align:start position:0% decide actually to not do that and use 00:39:07.740 --> 00:39:11.089 align:start position:0% decide actually to not do that and use the<00:39:07.980> event<00:39:08.160> and<00:39:08.820> I<00:39:08.940> feel<00:39:09.119> it's<00:39:09.359> it's<00:39:09.839> an<00:39:10.560> I<00:39:10.980> mean 00:39:11.089 --> 00:39:11.099 align:start position:0% the event and I feel it's it's an I mean 00:39:11.099 --> 00:39:13.609 align:start position:0% the event and I feel it's it's an I mean I<00:39:11.280> feel<00:39:11.460> normal<00:39:11.700> to<00:39:12.000> to<00:39:12.180> do<00:39:12.900> that<00:39:13.020> and<00:39:13.260> I<00:39:13.440> feel 00:39:13.609 --> 00:39:13.619 align:start position:0% I feel normal to to do that and I feel 00:39:13.619 --> 00:39:15.230 align:start position:0% I feel normal to to do that and I feel we<00:39:13.859> need<00:39:13.980> to<00:39:14.099> have<00:39:14.220> a<00:39:14.400> discussion<00:39:14.700> about<00:39:14.880> how 00:39:15.230 --> 00:39:15.240 align:start position:0% we need to have a discussion about how 00:39:15.240 --> 00:39:17.030 align:start position:0% we need to have a discussion about how do<00:39:15.420> we<00:39:15.540> will<00:39:15.839> deal<00:39:16.020> with<00:39:16.260> that<00:39:16.440> for 00:39:17.030 --> 00:39:17.040 align:start position:0% do we will deal with that for 00:39:17.040 --> 00:39:18.589 align:start position:0% do we will deal with that for applications<00:39:17.520> that<00:39:17.880> really<00:39:18.000> want<00:39:18.240> to<00:39:18.359> remain 00:39:18.589 --> 00:39:18.599 align:start position:0% applications that really want to remain 00:39:18.599 --> 00:39:20.329 align:start position:0% applications that really want to remain decentralized<00:39:19.260> have<00:39:19.680> you<00:39:19.859> looked<00:39:19.980> at<00:39:20.099> using 00:39:20.329 --> 00:39:20.339 align:start position:0% decentralized have you looked at using 00:39:20.339 --> 00:39:22.609 align:start position:0% decentralized have you looked at using the<00:39:20.460> graphql<00:39:20.940> apis<00:39:21.420> because<00:39:21.900> I<00:39:22.200> think<00:39:22.320> you<00:39:22.500> can 00:39:22.609 --> 00:39:22.619 align:start position:0% the graphql apis because I think you can 00:39:22.619 --> 00:39:24.829 align:start position:0% the graphql apis because I think you can go<00:39:22.859> into<00:39:23.040> a<00:39:23.280> Blog<00:39:23.460> from<00:39:23.700> a<00:39:23.880> log<00:39:24.000> and<00:39:24.540> you<00:39:24.720> can 00:39:24.829 --> 00:39:24.839 align:start position:0% go into a Blog from a log and you can 00:39:24.839 --> 00:39:26.210 align:start position:0% go into a Blog from a log and you can get<00:39:24.960> the<00:39:25.079> timestamp<00:39:25.500> and<00:39:25.680> you<00:39:25.800> can<00:39:25.859> do<00:39:25.980> it<00:39:26.099> in 00:39:26.210 --> 00:39:26.220 align:start position:0% get the timestamp and you can do it in 00:39:26.220 --> 00:39:28.810 align:start position:0% get the timestamp and you can do it in one<00:39:26.400> step<00:39:26.579> your<00:39:27.420> graphql<00:39:27.900> is<00:39:28.079> not<00:39:28.260> part<00:39:28.380> of 00:39:28.810 --> 00:39:28.820 align:start position:0% one step your graphql is not part of 00:39:28.820 --> 00:39:31.430 align:start position:0% one step your graphql is not part of vip1193<00:39:29.820> which<00:39:30.480> is<00:39:30.599> the<00:39:30.780> only<00:39:30.900> thing<00:39:31.079> I<00:39:31.320> have 00:39:31.430 --> 00:39:31.440 align:start position:0% vip1193 which is the only thing I have 00:39:31.440 --> 00:39:34.250 align:start position:0% vip1193 which is the only thing I have access<00:39:31.619> as<00:39:31.980> an<00:39:32.160> application<00:39:32.520> the<00:39:33.420> graphql<00:39:33.960> is 00:39:34.250 --> 00:39:34.260 align:start position:0% access as an application the graphql is 00:39:34.260 --> 00:39:35.810 align:start position:0% access as an application the graphql is there's<00:39:34.440> a<00:39:34.680> standard<00:39:34.859> for<00:39:34.980> the<00:39:35.099> graphql<00:39:35.579> and 00:39:35.810 --> 00:39:35.820 align:start position:0% there's a standard for the graphql and 00:39:35.820 --> 00:39:38.450 align:start position:0% there's a standard for the graphql and it<00:39:36.000> is<00:39:36.119> in<00:39:36.240> the<00:39:36.359> execution<00:39:36.660> apis<00:39:37.200> so 00:39:38.450 --> 00:39:38.460 align:start position:0% it is in the execution apis so 00:39:38.460 --> 00:39:40.130 align:start position:0% it is in the execution apis so um gas<00:39:38.760> and<00:39:38.940> base<00:39:39.119> we<00:39:39.359> both<00:39:39.480> implementing<00:39:40.020> can 00:39:40.130 --> 00:39:40.140 align:start position:0% um gas and base we both implementing can 00:39:40.140 --> 00:39:42.589 align:start position:0% um gas and base we both implementing can expose<00:39:40.440> it<00:39:40.619> but<00:39:40.980> you<00:39:41.280> have<00:39:41.400> I<00:39:42.000> think<00:39:42.240> what<00:39:42.420> is 00:39:42.589 --> 00:39:42.599 align:start position:0% expose it but you have I think what is 00:39:42.599 --> 00:39:44.210 align:start position:0% expose it but you have I think what is important<00:39:42.960> here<00:39:43.079> is<00:39:43.440> that<00:39:43.619> I<00:39:43.920> don't<00:39:44.040> have 00:39:44.210 --> 00:39:44.220 align:start position:0% important here is that I don't have 00:39:44.220 --> 00:39:45.470 align:start position:0% important here is that I don't have access<00:39:44.339> to<00:39:44.640> a<00:39:44.760> node 00:39:45.470 --> 00:39:45.480 align:start position:0% access to a node 00:39:45.480 --> 00:39:47.510 align:start position:0% access to a node the<00:39:46.200> only<00:39:46.380> interface<00:39:46.980> we<00:39:47.220> have<00:39:47.400> for 00:39:47.510 --> 00:39:47.520 align:start position:0% the only interface we have for 00:39:47.520 --> 00:39:50.270 align:start position:0% the only interface we have for application<00:39:47.940> is<00:39:48.180> the<00:39:48.440> ip1193<00:39:49.440> so<00:39:49.859> I<00:39:50.040> I'm 00:39:50.270 --> 00:39:50.280 align:start position:0% application is the ip1193 so I I'm 00:39:50.280 --> 00:39:52.250 align:start position:0% application is the ip1193 so I I'm trying<00:39:50.460> to<00:39:50.640> have<00:39:50.880> actually<00:39:51.000> added<00:39:51.660> a<00:39:51.780> further 00:39:52.250 --> 00:39:52.260 align:start position:0% trying to have actually added a further 00:39:52.260 --> 00:39:54.589 align:start position:0% trying to have actually added a further AIP<00:39:52.619> to<00:39:52.920> solve<00:39:53.160> this<00:39:53.220> using<00:39:53.640> graphql<00:39:54.180> as<00:39:54.420> a 00:39:54.589 --> 00:39:54.599 align:start position:0% AIP to solve this using graphql as a 00:39:54.599 --> 00:39:57.230 align:start position:0% AIP to solve this using graphql as a mechanism<00:39:54.900> by<00:39:55.200> which<00:39:55.320> sorry<00:39:55.560> sorry<00:39:55.859> but<00:39:57.240> um 00:39:57.230 --> 00:39:57.240 align:start position:0% mechanism by which sorry sorry but um 00:39:57.240 --> 00:39:59.810 align:start position:0% mechanism by which sorry sorry but um just<00:39:57.540> because<00:39:57.720> this<00:39:58.020> is<00:39:58.079> not<00:39:58.260> like<00:39:58.560> a<00:39:58.980> core<00:39:59.520> it 00:39:59.810 --> 00:39:59.820 align:start position:0% just because this is not like a core it 00:39:59.820 --> 00:40:00.829 align:start position:0% just because this is not like a core it does<00:40:00.000> touch<00:40:00.119> on<00:40:00.300> the<00:40:00.420> cardboard<00:40:00.660> we're<00:40:00.780> going 00:40:00.829 --> 00:40:00.839 align:start position:0% does touch on the cardboard we're going 00:40:00.839 --> 00:40:02.510 align:start position:0% does touch on the cardboard we're going to<00:40:00.960> have<00:40:01.020> a<00:40:01.140> whole<00:40:01.260> session<00:40:01.440> about<00:40:01.680> erc's<00:40:02.400> on 00:40:02.510 --> 00:40:02.520 align:start position:0% to have a whole session about erc's on 00:40:02.520 --> 00:40:03.829 align:start position:0% to have a whole session about erc's on Friday 00:40:03.829 --> 00:40:03.839 align:start position:0% Friday 00:40:03.839 --> 00:40:05.750 align:start position:0% Friday um it's<00:40:04.079> an<00:40:04.320> infrastructure<00:40:04.740> issue<00:40:05.160> yeah 00:40:05.750 --> 00:40:05.760 align:start position:0% um it's an infrastructure issue yeah 00:40:05.760 --> 00:40:08.870 align:start position:0% um it's an infrastructure issue yeah yeah<00:40:06.359> so<00:40:06.720> I<00:40:06.960> I<00:40:07.200> and<00:40:07.619> I<00:40:08.040> agree<00:40:08.280> with<00:40:08.460> you<00:40:08.640> there's 00:40:08.870 --> 00:40:08.880 align:start position:0% yeah so I I and I agree with you there's 00:40:08.880 --> 00:40:11.690 align:start position:0% yeah so I I and I agree with you there's like<00:40:09.119> a<00:40:09.359> longer<00:40:09.780> discussion<00:40:10.320> about<00:40:10.560> like<00:40:10.980> how 00:40:11.690 --> 00:40:11.700 align:start position:0% like a longer discussion about like how 00:40:11.700 --> 00:40:13.069 align:start position:0% like a longer discussion about like how applications<00:40:12.119> use<00:40:12.359> this<00:40:12.540> stuff<00:40:12.660> but<00:40:12.839> I<00:40:12.960> think 00:40:13.069 --> 00:40:13.079 align:start position:0% applications use this stuff but I think 00:40:13.079 --> 00:40:14.270 align:start position:0% applications use this stuff but I think yeah<00:40:13.200> that's<00:40:13.500> probably<00:40:13.800> a<00:40:13.920> really<00:40:14.040> good<00:40:14.160> one 00:40:14.270 --> 00:40:14.280 align:start position:0% yeah that's probably a really good one 00:40:14.280 --> 00:40:16.130 align:start position:0% yeah that's probably a really good one to<00:40:14.460> discuss<00:40:14.700> on<00:40:14.880> on<00:40:15.060> Friday 00:40:16.130 --> 00:40:16.140 align:start position:0% to discuss on on Friday 00:40:16.140 --> 00:40:18.050 align:start position:0% to discuss on on Friday um<00:40:16.200> yeah<00:40:16.619> thank<00:40:16.980> you 00:40:18.050 --> 00:40:18.060 align:start position:0% um yeah thank you 00:40:18.060 --> 00:40:23.569 align:start position:0% um yeah thank you yeah<00:40:18.720> uh<00:40:19.320> yeah<00:40:19.920> that<00:40:20.520> will<00:40:20.700> be<00:40:20.880> at<00:40:21.720> 1<00:40:22.020> pm<00:40:22.579> I'm 00:40:23.569 --> 00:40:23.579 align:start position:0% yeah uh yeah that will be at 1 pm I'm 00:40:23.579 --> 00:40:25.609 align:start position:0% yeah uh yeah that will be at 1 pm I'm not<00:40:23.820> sure<00:40:24.180> where<00:40:24.540> but<00:40:24.839> in<00:40:25.079> some<00:40:25.320> schedule 00:40:25.609 --> 00:40:25.619 align:start position:0% not sure where but in some schedule 00:40:25.619 --> 00:40:27.530 align:start position:0% not sure where but in some schedule somewhere<00:40:26.160> yeah<00:40:26.400> it's<00:40:26.700> on<00:40:26.880> there's<00:40:27.240> not<00:40:27.359> a<00:40:27.480> lot 00:40:27.530 --> 00:40:27.540 align:start position:0% somewhere yeah it's on there's not a lot 00:40:27.540 --> 00:40:29.329 align:start position:0% somewhere yeah it's on there's not a lot of<00:40:27.599> stuff<00:40:27.720> on<00:40:27.900> the<00:40:27.960> schedule<00:40:28.079> Friday<00:40:28.380> yeah 00:40:29.329 --> 00:40:29.339 align:start position:0% of stuff on the schedule Friday yeah 00:40:29.339 --> 00:40:30.710 align:start position:0% of stuff on the schedule Friday yeah yeah I'm 00:40:30.710 --> 00:40:30.720 align:start position:0% yeah I'm 00:40:30.720 --> 00:40:32.810 align:start position:0% yeah I'm Matt<00:40:31.320> do<00:40:31.619> you<00:40:31.800> have<00:40:31.859> one 00:40:32.810 --> 00:40:32.820 align:start position:0% Matt do you have one 00:40:32.820 --> 00:40:35.870 align:start position:0% Matt do you have one I have<00:40:33.119> an<00:40:33.240> EIP 00:40:35.870 --> 00:40:35.880 align:start position:0% 00:40:35.880 --> 00:40:38.750 align:start position:0% e<00:40:36.140> you<00:40:37.140> get<00:40:37.260> a<00:40:37.440> minute 00:40:38.750 --> 00:40:38.760 align:start position:0% e you get a minute 00:40:38.760 --> 00:40:41.329 align:start position:0% e you get a minute I'll<00:40:39.180> keep<00:40:39.240> it<00:40:39.359> short<00:40:39.480> I'll<00:40:39.660> keep<00:40:39.780> it<00:40:39.900> short 00:40:41.329 --> 00:40:41.339 align:start position:0% I'll keep it short I'll keep it short 00:40:41.339 --> 00:40:43.690 align:start position:0% I'll keep it short I'll keep it short um<00:40:41.460> so<00:40:41.640> my<00:40:41.760> name<00:40:41.880> is<00:40:42.000> Matt<00:40:42.240> I<00:40:42.780> am<00:40:42.900> an<00:40:43.079> author<00:40:43.320> of 00:40:43.690 --> 00:40:43.700 align:start position:0% um so my name is Matt I am an author of 00:40:43.700 --> 00:40:47.810 align:start position:0% um so my name is Matt I am an author of eip374<00:40:44.700> often<00:40:45.480> off<00:40:45.599> call 00:40:47.810 --> 00:40:47.820 align:start position:0% eip374 often off call 00:40:47.820 --> 00:40:49.370 align:start position:0% eip374 often off call more<00:40:48.240> to<00:40:48.359> the<00:40:48.540> mic<00:40:48.660> I<00:40:48.839> thought<00:40:48.960> she<00:40:49.200> was<00:40:49.320> going 00:40:49.370 --> 00:40:49.380 align:start position:0% more to the mic I thought she was going 00:40:49.380 --> 00:40:52.849 align:start position:0% more to the mic I thought she was going to<00:40:49.440> take<00:40:49.560> it<00:40:49.680> away<00:40:49.800> from<00:40:50.040> me 00:40:52.849 --> 00:40:52.859 align:start position:0% 00:40:52.859 --> 00:40:57.170 align:start position:0% you're<00:40:53.700> finished<00:40:53.940> now 00:40:57.170 --> 00:40:57.180 align:start position:0% 00:40:57.180 --> 00:41:00.349 align:start position:0% um<00:40:57.300> yeah<00:40:57.660> so<00:40:57.900> EIP<00:40:58.260> 3074<00:40:59.099> adds<00:40:59.520> to<00:40:59.700> new<00:40:59.940> OP<00:41:00.119> codes 00:41:00.349 --> 00:41:00.359 align:start position:0% um yeah so EIP 3074 adds to new OP codes 00:41:00.359 --> 00:41:02.810 align:start position:0% um yeah so EIP 3074 adds to new OP codes off<00:41:00.660> and<00:41:00.900> off<00:41:01.020> call<00:41:01.320> the<00:41:02.040> motivation<00:41:02.460> of<00:41:02.700> the 00:41:02.810 --> 00:41:02.820 align:start position:0% off and off call the motivation of the 00:41:02.820 --> 00:41:06.109 align:start position:0% off and off call the motivation of the EIP<00:41:03.119> is<00:41:03.720> to<00:41:04.020> improve<00:41:04.619> the<00:41:05.099> user<00:41:05.520> experience<00:41:05.880> of 00:41:06.109 --> 00:41:06.119 align:start position:0% EIP is to improve the user experience of 00:41:06.119 --> 00:41:08.990 align:start position:0% EIP is to improve the user experience of ethereum<00:41:06.599> I<00:41:07.380> think<00:41:07.560> if<00:41:08.040> you're<00:41:08.339> using<00:41:08.579> dapps 00:41:08.990 --> 00:41:09.000 align:start position:0% ethereum I think if you're using dapps 00:41:09.000 --> 00:41:10.670 align:start position:0% ethereum I think if you're using dapps today<00:41:09.119> you're<00:41:09.599> realizing<00:41:10.079> you're<00:41:10.320> signing 00:41:10.670 --> 00:41:10.680 align:start position:0% today you're realizing you're signing 00:41:10.680 --> 00:41:11.810 align:start position:0% today you're realizing you're signing tons<00:41:10.920> and<00:41:11.040> tons<00:41:11.220> of<00:41:11.339> things<00:41:11.460> when<00:41:11.700> you're 00:41:11.810 --> 00:41:11.820 align:start position:0% tons and tons of things when you're 00:41:11.820 --> 00:41:13.430 align:start position:0% tons and tons of things when you're interacting<00:41:12.180> with<00:41:12.300> a<00:41:12.480> single<00:41:12.720> dap<00:41:13.020> and<00:41:13.260> the 00:41:13.430 --> 00:41:13.440 align:start position:0% interacting with a single dap and the 00:41:13.440 --> 00:41:16.370 align:start position:0% interacting with a single dap and the flow<00:41:13.859> that<00:41:14.040> we<00:41:14.160> have<00:41:14.280> is<00:41:14.579> not<00:41:14.880> the<00:41:15.660> best<00:41:15.780> and 00:41:16.370 --> 00:41:16.380 align:start position:0% flow that we have is not the best and 00:41:16.380 --> 00:41:18.410 align:start position:0% flow that we have is not the best and with<00:41:16.800> auth<00:41:17.040> and<00:41:17.160> off<00:41:17.339> call<00:41:17.579> we're<00:41:17.820> providing<00:41:18.180> a 00:41:18.410 --> 00:41:18.420 align:start position:0% with auth and off call we're providing a 00:41:18.420 --> 00:41:20.810 align:start position:0% with auth and off call we're providing a very<00:41:18.540> generic<00:41:19.099> framework<00:41:20.099> for<00:41:20.460> adapt 00:41:20.810 --> 00:41:20.820 align:start position:0% very generic framework for adapt 00:41:20.820 --> 00:41:22.069 align:start position:0% very generic framework for adapt developers<00:41:21.300> to<00:41:21.599> Define<00:41:21.720> like 00:41:22.069 --> 00:41:22.079 align:start position:0% developers to Define like 00:41:22.079 --> 00:41:25.370 align:start position:0% developers to Define like multi-transaction<00:41:22.920> flows<00:41:23.599> in<00:41:24.599> a<00:41:24.720> way<00:41:24.839> that 00:41:25.370 --> 00:41:25.380 align:start position:0% multi-transaction flows in a way that 00:41:25.380 --> 00:41:27.470 align:start position:0% multi-transaction flows in a way that allows<00:41:26.220> users<00:41:26.520> to<00:41:26.700> sign<00:41:26.820> just<00:41:27.119> a<00:41:27.240> single 00:41:27.470 --> 00:41:27.480 align:start position:0% allows users to sign just a single 00:41:27.480 --> 00:41:30.050 align:start position:0% allows users to sign just a single message<00:41:27.660> and<00:41:28.560> they<00:41:28.740> don't<00:41:28.859> need<00:41:29.099> to<00:41:29.400> use<00:41:29.820> any 00:41:30.050 --> 00:41:30.060 align:start position:0% message and they don't need to use any 00:41:30.060 --> 00:41:31.970 align:start position:0% message and they don't need to use any kind<00:41:30.240> of<00:41:30.359> smart<00:41:30.599> contract<00:41:31.020> wallets<00:41:31.440> they<00:41:31.800> get 00:41:31.970 --> 00:41:31.980 align:start position:0% kind of smart contract wallets they get 00:41:31.980 --> 00:41:33.470 align:start position:0% kind of smart contract wallets they get these<00:41:32.220> types<00:41:32.460> of<00:41:32.520> benefits<00:41:32.880> for<00:41:33.000> free<00:41:33.180> without 00:41:33.470 --> 00:41:33.480 align:start position:0% these types of benefits for free without 00:41:33.480 --> 00:41:35.270 align:start position:0% these types of benefits for free without deploying<00:41:34.079> any<00:41:34.200> smart<00:41:34.440> contract<00:41:34.859> wallet 00:41:35.270 --> 00:41:35.280 align:start position:0% deploying any smart contract wallet 00:41:35.280 --> 00:41:37.490 align:start position:0% deploying any smart contract wallet that's<00:41:35.760> one<00:41:36.000> reason<00:41:36.180> another<00:41:36.599> reason<00:41:36.960> that<00:41:37.380> I 00:41:37.490 --> 00:41:37.500 align:start position:0% that's one reason another reason that I 00:41:37.500 --> 00:41:39.650 align:start position:0% that's one reason another reason that I think<00:41:37.619> the<00:41:37.740> EAP<00:41:38.040> 3074<00:41:38.640> is<00:41:38.820> very<00:41:38.940> valuable<00:41:39.300> is 00:41:39.650 --> 00:41:39.660 align:start position:0% think the EAP 3074 is very valuable is 00:41:39.660 --> 00:41:42.170 align:start position:0% think the EAP 3074 is very valuable is it<00:41:39.839> lets<00:41:40.200> all<00:41:40.440> users<00:41:40.800> of<00:41:40.920> eoas<00:41:41.400> sign<00:41:41.760> a<00:41:41.940> message 00:41:42.170 --> 00:41:42.180 align:start position:0% it lets all users of eoas sign a message 00:41:42.180 --> 00:41:44.990 align:start position:0% it lets all users of eoas sign a message to<00:41:42.780> create<00:41:43.380> some<00:41:43.800> sort<00:41:43.980> of<00:41:44.099> social<00:41:44.339> recovery 00:41:44.990 --> 00:41:45.000 align:start position:0% to create some sort of social recovery 00:41:45.000 --> 00:41:47.329 align:start position:0% to create some sort of social recovery mechanism<00:41:45.720> and<00:41:46.500> if<00:41:46.680> they<00:41:46.800> happen<00:41:46.920> to<00:41:47.160> lose 00:41:47.329 --> 00:41:47.339 align:start position:0% mechanism and if they happen to lose 00:41:47.339 --> 00:41:49.790 align:start position:0% mechanism and if they happen to lose their<00:41:47.839> metamask<00:41:48.839> or<00:41:49.020> their<00:41:49.200> Ledger<00:41:49.500> or 00:41:49.790 --> 00:41:49.800 align:start position:0% their metamask or their Ledger or 00:41:49.800 --> 00:41:51.530 align:start position:0% their metamask or their Ledger or whatever<00:41:49.920> wallet<00:41:50.400> that<00:41:50.520> they're<00:41:50.640> using<00:41:51.000> they 00:41:51.530 --> 00:41:51.540 align:start position:0% whatever wallet that they're using they 00:41:51.540 --> 00:41:53.990 align:start position:0% whatever wallet that they're using they can<00:41:51.720> go<00:41:52.020> and<00:41:52.260> recover<00:41:52.619> it<00:41:52.859> with<00:41:53.220> the<00:41:53.700> people 00:41:53.990 --> 00:41:54.000 align:start position:0% can go and recover it with the people 00:41:54.000 --> 00:41:56.329 align:start position:0% can go and recover it with the people that<00:41:54.240> they<00:41:54.420> signed<00:41:54.780> through<00:41:55.140> and<00:41:55.980> the<00:41:56.099> third 00:41:56.329 --> 00:41:56.339 align:start position:0% that they signed through and the third 00:41:56.339 --> 00:41:58.370 align:start position:0% that they signed through and the third thing<00:41:56.700> I<00:41:56.880> think<00:41:57.060> is<00:41:57.180> really<00:41:57.480> interesting<00:41:58.079> with 00:41:58.370 --> 00:41:58.380 align:start position:0% thing I think is really interesting with 00:41:58.380 --> 00:42:00.770 align:start position:0% thing I think is really interesting with 3074<00:41:59.040> and<00:41:59.460> is<00:41:59.700> a<00:41:59.880> testament<00:42:00.119> for<00:42:00.359> like<00:42:00.540> how 00:42:00.770 --> 00:42:00.780 align:start position:0% 3074 and is a testament for like how 00:42:00.780 --> 00:42:03.170 align:start position:0% 3074 and is a testament for like how powerful<00:42:01.140> it<00:42:01.380> is<00:42:01.560> is<00:42:01.800> a<00:42:02.280> proposal<00:42:02.760> that<00:42:03.000> Alex 00:42:03.170 --> 00:42:03.180 align:start position:0% powerful it is is a proposal that Alex 00:42:03.180 --> 00:42:05.329 align:start position:0% powerful it is is a proposal that Alex came<00:42:03.599> up<00:42:03.720> with<00:42:03.900> maybe<00:42:04.740> I<00:42:05.099> don't<00:42:05.160> know<00:42:05.220> maybe 00:42:05.329 --> 00:42:05.339 align:start position:0% came up with maybe I don't know maybe 00:42:05.339 --> 00:42:08.210 align:start position:0% came up with maybe I don't know maybe last<00:42:05.640> year<00:42:05.820> about<00:42:06.119> replacing<00:42:06.839> the<00:42:07.320> wet<00:42:07.619> erc20 00:42:08.210 --> 00:42:08.220 align:start position:0% last year about replacing the wet erc20 00:42:08.220 --> 00:42:11.530 align:start position:0% last year about replacing the wet erc20 token<00:42:08.700> with<00:42:09.480> a<00:42:09.859> contract<00:42:10.859> that<00:42:10.980> uses<00:42:11.280> the 00:42:11.530 --> 00:42:11.540 align:start position:0% token with a contract that uses the 00:42:11.540 --> 00:42:15.230 align:start position:0% token with a contract that uses the ip3074<00:42:12.540> to<00:42:13.520> natively<00:42:14.520> move<00:42:14.760> the<00:42:15.000> ether 00:42:15.230 --> 00:42:15.240 align:start position:0% ip3074 to natively move the ether 00:42:15.240 --> 00:42:16.490 align:start position:0% ip3074 to natively move the ether balances<00:42:15.660> around<00:42:15.839> whenever<00:42:16.320> you're 00:42:16.490 --> 00:42:16.500 align:start position:0% balances around whenever you're 00:42:16.500 --> 00:42:19.190 align:start position:0% balances around whenever you're interacting<00:42:17.040> with<00:42:17.220> the<00:42:17.339> erc20<00:42:17.880> token<00:42:18.420> so 00:42:19.190 --> 00:42:19.200 align:start position:0% interacting with the erc20 token so 00:42:19.200 --> 00:42:21.349 align:start position:0% interacting with the erc20 token so that's<00:42:19.920> the<00:42:20.400> the 00:42:21.349 --> 00:42:21.359 align:start position:0% that's the the 00:42:21.359 --> 00:42:23.990 align:start position:0% that's the the data 00:42:23.990 --> 00:42:24.000 align:start position:0% data 00:42:24.000 --> 00:42:25.609 align:start position:0% data um 00:42:25.609 --> 00:42:25.619 align:start position:0% um 00:42:25.619 --> 00:42:28.250 align:start position:0% um there<00:42:26.280> is<00:42:26.460> some<00:42:26.760> huge<00:42:27.060> user<00:42:27.480> experience<00:42:27.780> risks 00:42:28.250 --> 00:42:28.260 align:start position:0% there is some huge user experience risks 00:42:28.260 --> 00:42:30.050 align:start position:0% there is some huge user experience risks with<00:42:28.440> it<00:42:28.560> is<00:42:28.800> currently<00:42:29.160> done<00:42:29.579> and<00:42:29.940> the 00:42:30.050 --> 00:42:30.060 align:start position:0% with it is currently done and the 00:42:30.060 --> 00:42:32.329 align:start position:0% with it is currently done and the revision<00:42:30.359> took<00:42:30.780> some<00:42:30.960> of<00:42:31.079> the<00:42:31.320> guard<00:42:31.859> rails 00:42:32.329 --> 00:42:32.339 align:start position:0% revision took some of the guard rails 00:42:32.339 --> 00:42:34.250 align:start position:0% revision took some of the guard rails off<00:42:32.460> so 00:42:34.250 --> 00:42:34.260 align:start position:0% off so 00:42:34.260 --> 00:42:36.050 align:start position:0% off so um we<00:42:34.920> don't<00:42:35.040> have<00:42:35.220> enough<00:42:35.400> time<00:42:35.640> to<00:42:35.820> go<00:42:35.940> into 00:42:36.050 --> 00:42:36.060 align:start position:0% um we don't have enough time to go into 00:42:36.060 --> 00:42:38.390 align:start position:0% um we don't have enough time to go into some<00:42:36.359> of<00:42:36.480> those<00:42:36.599> those<00:42:36.960> issues<00:42:37.680> with<00:42:37.920> safety 00:42:38.390 --> 00:42:38.400 align:start position:0% some of those those issues with safety 00:42:38.400 --> 00:42:40.069 align:start position:0% some of those those issues with safety and<00:42:38.940> those<00:42:39.119> are<00:42:39.240> I<00:42:39.420> think<00:42:39.540> my<00:42:39.720> number<00:42:39.900> one 00:42:40.069 --> 00:42:40.079 align:start position:0% and those are I think my number one 00:42:40.079 --> 00:42:42.349 align:start position:0% and those are I think my number one concern<00:42:40.440> on<00:42:40.680> that<00:42:40.859> right<00:42:41.099> now<00:42:41.280> but<00:42:41.940> if<00:42:42.119> we<00:42:42.240> need 00:42:42.349 --> 00:42:42.359 align:start position:0% concern on that right now but if we need 00:42:42.359 --> 00:42:44.210 align:start position:0% concern on that right now but if we need meta<00:42:42.839> transactions<00:42:43.320> let's<00:42:43.500> make<00:42:43.680> a<00:42:43.859> meta 00:42:44.210 --> 00:42:44.220 align:start position:0% meta transactions let's make a meta 00:42:44.220 --> 00:42:47.690 align:start position:0% meta transactions let's make a meta transaction<00:42:44.900> transaction<00:42:45.900> format<00:42:46.440> and<00:42:47.280> some 00:42:47.690 --> 00:42:47.700 align:start position:0% transaction transaction format and some 00:42:47.700 --> 00:42:48.470 align:start position:0% transaction transaction format and some of<00:42:47.820> the<00:42:47.820> other<00:42:47.940> ones<00:42:48.060> you<00:42:48.240> know<00:42:48.359> account 00:42:48.470 --> 00:42:48.480 align:start position:0% of the other ones you know account 00:42:48.480 --> 00:42:50.089 align:start position:0% of the other ones you know account abstraction<00:42:49.079> yeah<00:42:49.500> I<00:42:49.800> think<00:42:49.920> account 00:42:50.089 --> 00:42:50.099 align:start position:0% abstraction yeah I think account 00:42:50.099 --> 00:42:51.290 align:start position:0% abstraction yeah I think account abstract<00:42:50.520> you<00:42:50.700> can<00:42:50.820> solve<00:42:51.000> that<00:42:51.060> and<00:42:51.180> that's 00:42:51.290 --> 00:42:51.300 align:start position:0% abstract you can solve that and that's 00:42:51.300 --> 00:42:53.030 align:start position:0% abstract you can solve that and that's something<00:42:51.420> we<00:42:51.599> know<00:42:51.720> we<00:42:51.839> want<00:42:52.020> to<00:42:52.140> do 00:42:53.030 --> 00:42:53.040 align:start position:0% something we know we want to do 00:42:53.040 --> 00:42:55.670 align:start position:0% something we know we want to do yeah<00:42:53.520> okay<00:42:53.820> so<00:42:54.060> the<00:42:54.420> yeah 00:42:55.670 --> 00:42:55.680 align:start position:0% yeah okay so the yeah 00:42:55.680 --> 00:42:57.290 align:start position:0% yeah okay so the yeah yeah various<00:42:56.280> ones<00:42:56.579> to<00:42:56.700> China<00:42:56.820> man<00:42:57.119> they're 00:42:57.290 --> 00:42:57.300 align:start position:0% yeah various ones to China man they're 00:42:57.300 --> 00:42:58.790 align:start position:0% yeah various ones to China man they're on<00:42:57.420> the<00:42:57.540> same<00:42:57.660> team<00:42:57.839> we<00:42:58.079> have<00:42:58.200> 10<00:42:58.380> minutes<00:42:58.500> left 00:42:58.790 --> 00:42:58.800 align:start position:0% on the same team we have 10 minutes left 00:42:58.800 --> 00:42:59.990 align:start position:0% on the same team we have 10 minutes left sorry<00:42:59.099> no 00:42:59.990 --> 00:43:00.000 align:start position:0% sorry no 00:43:00.000 --> 00:43:02.930 align:start position:0% sorry no um<00:43:00.119> well<00:43:01.040> I<00:43:02.040> will<00:43:02.160> give<00:43:02.280> a<00:43:02.339> shout<00:43:02.460> out<00:43:02.520> there<00:43:02.819> is 00:43:02.930 --> 00:43:02.940 align:start position:0% um well I will give a shout out there is 00:43:02.940 --> 00:43:04.430 align:start position:0% um well I will give a shout out there is an<00:43:03.060> account<00:43:03.180> abstraction<00:43:03.720> panel<00:43:04.140> I<00:43:04.319> think 00:43:04.430 --> 00:43:04.440 align:start position:0% an account abstraction panel I think 00:43:04.440 --> 00:43:07.069 align:start position:0% an account abstraction panel I think Matthew<00:43:04.680> on<00:43:05.099> it<00:43:05.280> uh<00:43:05.760> later<00:43:05.940> this<00:43:06.180> week<00:43:06.359> so<00:43:06.900> if 00:43:07.069 --> 00:43:07.079 align:start position:0% Matthew on it uh later this week so if 00:43:07.079 --> 00:43:08.329 align:start position:0% Matthew on it uh later this week so if you<00:43:07.260> want<00:43:07.380> to<00:43:07.500> go<00:43:07.560> ahead<00:43:07.740> and<00:43:07.859> do<00:43:07.980> a<00:43:08.099> heated 00:43:08.329 --> 00:43:08.339 align:start position:0% you want to go ahead and do a heated 00:43:08.339 --> 00:43:10.370 align:start position:0% you want to go ahead and do a heated debate<00:43:08.700> about<00:43:08.940> the<00:43:09.240> various<00:43:09.599> flavors<00:43:10.020> of 00:43:10.370 --> 00:43:10.380 align:start position:0% debate about the various flavors of 00:43:10.380 --> 00:43:11.870 align:start position:0% debate about the various flavors of account<00:43:10.560> obstruction<00:43:11.099> and<00:43:11.460> fake<00:43:11.700> account 00:43:11.870 --> 00:43:11.880 align:start position:0% account obstruction and fake account 00:43:11.880 --> 00:43:14.630 align:start position:0% account obstruction and fake account obstruction<00:43:12.420> and<00:43:12.780> 3074<00:43:13.500> right<00:43:14.220> um<00:43:14.280> we'll<00:43:14.460> have 00:43:14.630 --> 00:43:14.640 align:start position:0% obstruction and 3074 right um we'll have 00:43:14.640 --> 00:43:16.370 align:start position:0% obstruction and 3074 right um we'll have a<00:43:14.760> whole<00:43:14.880> hour<00:43:15.000> to<00:43:15.180> debate<00:43:15.480> it<00:43:15.599> yeah<00:43:15.780> so<00:43:16.079> yeah 00:43:16.370 --> 00:43:16.380 align:start position:0% a whole hour to debate it yeah so yeah 00:43:16.380 --> 00:43:18.829 align:start position:0% a whole hour to debate it yeah so yeah so<00:43:16.800> that's<00:43:16.920> okay<00:43:17.339> cool<00:43:17.880> can<00:43:18.180> you<00:43:18.300> raise<00:43:18.660> your 00:43:18.829 --> 00:43:18.839 align:start position:0% so that's okay cool can you raise your 00:43:18.839 --> 00:43:22.849 align:start position:0% so that's okay cool can you raise your hand<00:43:18.960> if<00:43:19.140> you<00:43:19.260> still<00:43:19.319> had<00:43:19.500> an<00:43:19.619> EIP<00:43:19.980> uh 00:43:22.849 --> 00:43:22.859 align:start position:0% hand if you still had an EIP uh 00:43:22.859 --> 00:43:26.450 align:start position:0% hand if you still had an EIP uh but<00:43:23.579> Alex<00:43:24.119> you<00:43:24.420> don't<00:43:24.599> have<00:43:24.900> one 00:43:26.450 --> 00:43:26.460 align:start position:0% but Alex you don't have one 00:43:26.460 --> 00:43:28.490 align:start position:0% but Alex you don't have one okay<00:43:27.119> just 00:43:28.490 --> 00:43:28.500 align:start position:0% okay just 00:43:28.500 --> 00:43:32.210 align:start position:0% okay just oh<00:43:28.980> no<00:43:29.099> sorry<00:43:29.339> I<00:43:29.579> mean<00:43:29.900> Alex<00:43:30.900> B 00:43:32.210 --> 00:43:32.220 align:start position:0% oh no sorry I mean Alex B 00:43:32.220 --> 00:43:36.950 align:start position:0% oh no sorry I mean Alex B in<00:43:32.700> front<00:43:32.880> ACC<00:43:33.619> now<00:43:34.619> Okay<00:43:34.920> no<00:43:35.160> Okay<00:43:35.579> cool<00:43:36.180> uh 00:43:36.950 --> 00:43:36.960 align:start position:0% in front ACC now Okay no Okay cool uh 00:43:36.960 --> 00:43:38.890 align:start position:0% in front ACC now Okay no Okay cool uh how<00:43:37.319> about<00:43:37.440> it 00:43:38.890 --> 00:43:38.900 align:start position:0% how about it 00:43:38.900 --> 00:43:43.849 align:start position:0% how about it well<00:43:40.040> do<00:43:41.040> you<00:43:41.099> have<00:43:41.280> it<00:43:41.480> no<00:43:42.480> no<00:43:42.660> uh<00:43:43.500> how<00:43:43.740> about 00:43:43.849 --> 00:43:43.859 align:start position:0% well do you have it no no uh how about 00:43:43.859 --> 00:43:47.270 align:start position:0% well do you have it no no uh how about did<00:43:44.160> you<00:43:44.280> have<00:43:44.400> one 00:43:47.270 --> 00:43:47.280 align:start position:0% 00:43:47.280 --> 00:43:49.550 align:start position:0% okay<00:43:47.640> Daniel<00:43:47.880> do<00:43:48.180> you<00:43:48.300> have<00:43:48.359> a<00:43:48.480> fully<00:43:48.780> IP<00:43:49.079> I 00:43:49.550 --> 00:43:49.560 align:start position:0% okay Daniel do you have a fully IP I 00:43:49.560 --> 00:43:50.930 align:start position:0% okay Daniel do you have a fully IP I have<00:43:49.800> three<00:43:49.980> of<00:43:50.099> them<00:43:50.220> but<00:43:50.400> I<00:43:50.520> only<00:43:50.640> want<00:43:50.819> a 00:43:50.930 --> 00:43:50.940 align:start position:0% have three of them but I only want a 00:43:50.940 --> 00:43:52.490 align:start position:0% have three of them but I only want a quick<00:43:51.060> yay 00:43:52.490 --> 00:43:52.500 align:start position:0% quick yay 00:43:52.500 --> 00:43:55.370 align:start position:0% quick yay okay<00:43:52.920> I<00:43:53.339> also<00:43:53.579> have<00:43:53.700> a<00:43:53.819> quick<00:43:53.940> one<00:43:54.119> for<00:43:54.420> a<00:43:54.599> Yin<00:43:55.079> a 00:43:55.370 --> 00:43:55.380 align:start position:0% okay I also have a quick one for a Yin a 00:43:55.380 --> 00:43:58.609 align:start position:0% okay I also have a quick one for a Yin a okay<00:43:55.920> Dino<00:43:56.460> first<00:43:56.760> and<00:43:57.540> there<00:43:57.780> we<00:43:58.140> finish<00:43:58.319> with 00:43:58.609 --> 00:43:58.619 align:start position:0% okay Dino first and there we finish with 00:43:58.619 --> 00:44:00.770 align:start position:0% okay Dino first and there we finish with Matt<00:43:58.800> so<00:43:59.760> I<00:43:59.880> just<00:44:00.060> I<00:44:00.240> just<00:44:00.359> want<00:44:00.420> to<00:44:00.540> get<00:44:00.660> a 00:44:00.770 --> 00:44:00.780 align:start position:0% Matt so I just I just want to get a 00:44:00.780 --> 00:44:02.510 align:start position:0% Matt so I just I just want to get a temperature<00:44:00.900> check<00:44:01.260> on<00:44:01.560> the<00:44:01.740> three<00:44:01.920> other<00:44:02.099> eof 00:44:02.510 --> 00:44:02.520 align:start position:0% temperature check on the three other eof 00:44:02.520 --> 00:44:05.210 align:start position:0% temperature check on the three other eof ones<00:44:03.060> on<00:44:03.540> eof<00:44:03.900> function<00:44:04.380> static<00:44:04.920> relative 00:44:05.210 --> 00:44:05.220 align:start position:0% ones on eof function static relative 00:44:05.220 --> 00:44:08.150 align:start position:0% ones on eof function static relative jumps<00:44:05.700> and<00:44:05.819> stack<00:44:06.000> validation<00:44:06.599> good<00:44:07.560> idea<00:44:07.800> bad 00:44:08.150 --> 00:44:08.160 align:start position:0% jumps and stack validation good idea bad 00:44:08.160 --> 00:44:09.950 align:start position:0% jumps and stack validation good idea bad idea<00:44:08.280> too<00:44:08.640> complex<00:44:09.000> that's<00:44:09.540> really<00:44:09.660> all<00:44:09.839> I'm 00:44:09.950 --> 00:44:09.960 align:start position:0% idea too complex that's really all I'm 00:44:09.960 --> 00:44:11.870 align:start position:0% idea too complex that's really all I'm looking<00:44:10.140> for 00:44:11.870 --> 00:44:11.880 align:start position:0% looking for 00:44:11.880 --> 00:44:14.270 align:start position:0% looking for okay 00:44:14.270 --> 00:44:14.280 align:start position:0% okay 00:44:14.280 --> 00:44:16.849 align:start position:0% okay okay<00:44:14.480> so<00:44:15.480> the<00:44:15.660> first<00:44:15.720> one<00:44:15.900> is<00:44:16.140> eof<00:44:16.440> functions 00:44:16.849 --> 00:44:16.859 align:start position:0% okay so the first one is eof functions 00:44:16.859 --> 00:44:18.589 align:start position:0% okay so the first one is eof functions where<00:44:17.040> we'd<00:44:17.220> have<00:44:17.339> the<00:44:17.460> call<00:44:17.579> F<00:44:17.880> and<00:44:18.480> we'd 00:44:18.589 --> 00:44:18.599 align:start position:0% where we'd have the call F and we'd 00:44:18.599 --> 00:44:20.809 align:start position:0% where we'd have the call F and we'd split<00:44:18.839> it<00:44:18.960> up<00:44:19.079> in<00:44:19.200> different<00:44:19.380> functions<00:44:19.920> and 00:44:20.809 --> 00:44:20.819 align:start position:0% split it up in different functions and 00:44:20.819 --> 00:44:22.910 align:start position:0% split it up in different functions and have<00:44:21.119> multiple<00:44:21.420> code<00:44:21.540> segments 00:44:22.910 --> 00:44:22.920 align:start position:0% have multiple code segments 00:44:22.920 --> 00:44:28.010 align:start position:0% have multiple code segments good<00:44:23.280> idea<00:44:23.520> bad<00:44:23.760> idea<00:44:24.060> too<00:44:24.240> complex 00:44:28.010 --> 00:44:28.020 align:start position:0% 00:44:28.020 --> 00:44:29.390 align:start position:0% okay 00:44:29.390 --> 00:44:29.400 align:start position:0% okay 00:44:29.400 --> 00:44:31.130 align:start position:0% okay static<00:44:29.880> relative<00:44:30.180> jumps<00:44:30.660> where<00:44:30.780> it's<00:44:31.020> an 00:44:31.130 --> 00:44:31.140 align:start position:0% static relative jumps where it's an 00:44:31.140 --> 00:44:32.750 align:start position:0% static relative jumps where it's an immediate<00:44:31.500> operation<00:44:31.859> you<00:44:32.040> say<00:44:32.220> jump<00:44:32.460> ahead 00:44:32.750 --> 00:44:32.760 align:start position:0% immediate operation you say jump ahead 00:44:32.760 --> 00:44:33.950 align:start position:0% immediate operation you say jump ahead 10. 00:44:33.950 --> 00:44:33.960 align:start position:0% 10. 00:44:33.960 --> 00:44:35.030 align:start position:0% 10. yes 00:44:35.030 --> 00:44:35.040 align:start position:0% yes 00:44:35.040 --> 00:44:39.050 align:start position:0% yes okay<00:44:35.480> and<00:44:36.480> the<00:44:36.900> stack<00:44:37.140> validation<00:44:38.060> which 00:44:39.050 --> 00:44:39.060 align:start position:0% okay and the stack validation which 00:44:39.060 --> 00:44:41.270 align:start position:0% okay and the stack validation which needs<00:44:39.420> the<00:44:39.599> functions<00:44:40.079> where<00:44:40.740> you<00:44:40.980> can<00:44:41.099> say 00:44:41.270 --> 00:44:41.280 align:start position:0% needs the functions where you can say 00:44:41.280 --> 00:44:43.010 align:start position:0% needs the functions where you can say that<00:44:41.640> this<00:44:41.880> function<00:44:42.119> is<00:44:42.359> only<00:44:42.540> going<00:44:42.780> to<00:44:42.839> take 00:44:43.010 --> 00:44:43.020 align:start position:0% that this function is only going to take 00:44:43.020 --> 00:44:46.609 align:start position:0% that this function is only going to take five<00:44:43.859> stack<00:44:44.280> items<00:44:44.760> and<00:44:45.720> if<00:44:45.900> it<00:44:46.020> goes<00:44:46.260> and<00:44:46.440> it's 00:44:46.609 --> 00:44:46.619 align:start position:0% five stack items and if it goes and it's 00:44:46.619 --> 00:44:48.050 align:start position:0% five stack items and if it goes and it's not<00:44:46.800> going<00:44:46.920> to<00:44:46.980> overflow 00:44:48.050 --> 00:44:48.060 align:start position:0% not going to overflow 00:44:48.060 --> 00:44:52.849 align:start position:0% not going to overflow so<00:44:48.540> you<00:44:48.660> could<00:44:48.780> remove<00:44:48.960> the<00:44:49.260> Overflow<00:44:49.619> check 00:44:52.849 --> 00:44:52.859 align:start position:0% 00:44:52.859 --> 00:44:54.710 align:start position:0% my<00:44:53.400> thought<00:44:53.520> on<00:44:53.700> that<00:44:53.819> is<00:44:53.940> it's<00:44:54.119> a<00:44:54.300> bit<00:44:54.420> complex 00:44:54.710 --> 00:44:54.720 align:start position:0% my thought on that is it's a bit complex 00:44:54.720 --> 00:44:57.230 align:start position:0% my thought on that is it's a bit complex to<00:44:54.960> get<00:44:55.079> into<00:44:55.200> Shanghai<00:44:55.680> so<00:44:56.160> that's<00:44:56.640> I<00:44:57.000> want<00:44:57.180> to 00:44:57.230 --> 00:44:57.240 align:start position:0% to get into Shanghai so that's I want to 00:44:57.240 --> 00:45:03.970 align:start position:0% to get into Shanghai so that's I want to see<00:44:57.359> if<00:44:57.540> I'm<00:44:58.020> the<00:44:58.140> only<00:44:58.260> one<00:44:58.380> of<00:44:58.440> that<00:44:58.560> opinion 00:45:03.970 --> 00:45:03.980 align:start position:0% 00:45:03.980 --> 00:45:06.349 align:start position:0% I<00:45:04.980> wasn't<00:45:05.280> saying<00:45:05.640> that<00:45:05.819> the<00:45:06.000> other<00:45:06.060> stuff 00:45:06.349 --> 00:45:06.359 align:start position:0% I wasn't saying that the other stuff 00:45:06.359 --> 00:45:08.510 align:start position:0% I wasn't saying that the other stuff should<00:45:06.540> go<00:45:06.660> into<00:45:07.079> Shanghai<00:45:07.560> I<00:45:07.920> think<00:45:07.980> it's<00:45:08.220> it 00:45:08.510 --> 00:45:08.520 align:start position:0% should go into Shanghai I think it's it 00:45:08.520 --> 00:45:09.950 align:start position:0% should go into Shanghai I think it's it might<00:45:08.700> be<00:45:08.819> a<00:45:08.940> good<00:45:09.000> idea<00:45:09.119> in<00:45:09.359> the<00:45:09.480> future<00:45:09.599> good 00:45:09.950 --> 00:45:09.960 align:start position:0% might be a good idea in the future good 00:45:09.960 --> 00:45:12.250 align:start position:0% might be a good idea in the future good idea<00:45:10.200> just<00:45:10.500> Cancun<00:45:10.980> or<00:45:11.280> later 00:45:12.250 --> 00:45:12.260 align:start position:0% idea just Cancun or later 00:45:12.260 --> 00:45:16.490 align:start position:0% idea just Cancun or later so<00:45:13.260> cool<00:45:13.500> so<00:45:13.920> no<00:45:14.099> one<00:45:14.280> actually<00:45:14.520> proposed<00:45:15.180> uof 00:45:16.490 --> 00:45:16.500 align:start position:0% so cool so no one actually proposed uof 00:45:16.500 --> 00:45:20.390 align:start position:0% so cool so no one actually proposed uof um<00:45:16.619> so<00:45:17.040> I<00:45:17.460> guess<00:45:18.119> the<00:45:18.540> UF<00:45:18.900> is<00:45:19.339> approved<00:45:20.339> for 00:45:20.390 --> 00:45:20.400 align:start position:0% um so I guess the UF is approved for 00:45:20.400 --> 00:45:21.890 align:start position:0% um so I guess the UF is approved for inclusion<00:45:20.819> oh<00:45:21.060> but<00:45:21.240> I<00:45:21.359> just<00:45:21.480> wanted<00:45:21.660> a 00:45:21.890 --> 00:45:21.900 align:start position:0% inclusion oh but I just wanted a 00:45:21.900 --> 00:45:23.150 align:start position:0% inclusion oh but I just wanted a temperature<00:45:22.079> check<00:45:22.380> so<00:45:22.560> let's<00:45:22.680> not<00:45:22.859> discuss 00:45:23.150 --> 00:45:23.160 align:start position:0% temperature check so let's not discuss 00:45:23.160 --> 00:45:24.530 align:start position:0% temperature check so let's not discuss it<00:45:23.280> oh<00:45:23.520> sorry 00:45:24.530 --> 00:45:24.540 align:start position:0% it oh sorry 00:45:24.540 --> 00:45:27.730 align:start position:0% it oh sorry oh<00:45:25.140> yeah<00:45:25.380> these<00:45:25.859> aren't<00:45:25.920> in<00:45:26.160> yet<00:45:26.339> okay<00:45:27.060> okay 00:45:27.730 --> 00:45:27.740 align:start position:0% oh yeah these aren't in yet okay okay 00:45:27.740 --> 00:45:30.770 align:start position:0% oh yeah these aren't in yet okay okay can<00:45:28.740> I<00:45:28.859> like<00:45:29.160> like<00:45:29.460> one<00:45:29.760> comment<00:45:30.180> is<00:45:30.359> like<00:45:30.660> if 00:45:30.770 --> 00:45:30.780 align:start position:0% can I like like one comment is like if 00:45:30.780 --> 00:45:33.410 align:start position:0% can I like like one comment is like if you<00:45:30.960> combine<00:45:31.319> functions<00:45:32.040> and<00:45:32.460> relative<00:45:32.940> jumps 00:45:33.410 --> 00:45:33.420 align:start position:0% you combine functions and relative jumps 00:45:33.420 --> 00:45:36.290 align:start position:0% you combine functions and relative jumps you<00:45:33.599> can<00:45:33.839> get<00:45:34.319> rid<00:45:34.500> of<00:45:34.740> of<00:45:35.160> uh<00:45:35.819> jobless 00:45:36.290 --> 00:45:36.300 align:start position:0% you can get rid of of uh jobless 00:45:36.300 --> 00:45:38.450 align:start position:0% you can get rid of of uh jobless analysis<00:45:36.780> entirely<00:45:37.319> because<00:45:37.800> they<00:45:38.160> kind<00:45:38.339> of 00:45:38.450 --> 00:45:38.460 align:start position:0% analysis entirely because they kind of 00:45:38.460 --> 00:45:40.670 align:start position:0% analysis entirely because they kind of replace<00:45:38.640> that 00:45:40.670 --> 00:45:40.680 align:start position:0% replace that 00:45:40.680 --> 00:45:42.829 align:start position:0% replace that um<00:45:41.060> unless<00:45:42.060> we<00:45:42.180> get<00:45:42.240> rid<00:45:42.359> of<00:45:42.480> the<00:45:42.540> jump<00:45:42.660> code 00:45:42.829 --> 00:45:42.839 align:start position:0% um unless we get rid of the jump code 00:45:42.839 --> 00:45:44.690 align:start position:0% um unless we get rid of the jump code too 00:45:44.690 --> 00:45:44.700 align:start position:0% too 00:45:44.700 --> 00:45:46.069 align:start position:0% too um<00:45:44.819> the<00:45:45.119> jump<00:45:45.240> wood 00:45:46.069 --> 00:45:46.079 align:start position:0% um the jump wood 00:45:46.079 --> 00:45:47.750 align:start position:0% um the jump wood jump<00:45:46.560> and<00:45:46.740> jump<00:45:46.859> I<00:45:47.040> would<00:45:47.220> have<00:45:47.400> to<00:45:47.460> get<00:45:47.579> rid<00:45:47.640> of 00:45:47.750 --> 00:45:47.760 align:start position:0% jump and jump I would have to get rid of 00:45:47.760 --> 00:45:49.609 align:start position:0% jump and jump I would have to get rid of those<00:45:47.819> get<00:45:48.060> rid<00:45:48.180> of<00:45:48.240> jump<00:45:48.359> test<00:45:48.540> analysis<00:45:49.079> yeah 00:45:49.609 --> 00:45:49.619 align:start position:0% those get rid of jump test analysis yeah 00:45:49.619 --> 00:45:51.950 align:start position:0% those get rid of jump test analysis yeah like<00:45:49.920> to<00:45:50.220> remove<00:45:50.280> all<00:45:50.520> of<00:45:50.700> these<00:45:50.940> we<00:45:51.660> can<00:45:51.780> do 00:45:51.950 --> 00:45:51.960 align:start position:0% like to remove all of these we can do 00:45:51.960 --> 00:45:54.349 align:start position:0% like to remove all of these we can do that<00:45:52.079> with<00:45:52.319> these<00:45:52.859> two<00:45:52.980> features<00:45:53.339> but<00:45:53.640> uh<00:45:53.880> like 00:45:54.349 --> 00:45:54.359 align:start position:0% that with these two features but uh like 00:45:54.359 --> 00:45:56.089 align:start position:0% that with these two features but uh like the<00:45:54.660> way<00:45:54.780> we<00:45:55.020> didn't<00:45:55.140> Champion<00:45:55.560> it<00:45:55.920> like 00:45:56.089 --> 00:45:56.099 align:start position:0% the way we didn't Champion it like 00:45:56.099 --> 00:45:59.390 align:start position:0% the way we didn't Champion it like because<00:45:56.520> I<00:45:57.240> think<00:45:57.359> that's<00:45:57.780> not<00:45:58.140> on<00:45:58.500> us<00:45:58.800> to<00:45:59.040> like 00:45:59.390 --> 00:45:59.400 align:start position:0% because I think that's not on us to like 00:45:59.400 --> 00:46:01.910 align:start position:0% because I think that's not on us to like actually<00:45:59.640> say<00:46:00.119> it's<00:46:00.300> great<00:46:00.720> because<00:46:01.140> we<00:46:01.800> need 00:46:01.910 --> 00:46:01.920 align:start position:0% actually say it's great because we need 00:46:01.920 --> 00:46:04.370 align:start position:0% actually say it's great because we need to<00:46:02.040> input<00:46:02.339> from<00:46:02.579> people<00:46:02.940> that<00:46:03.359> say<00:46:03.660> they<00:46:04.200> want 00:46:04.370 --> 00:46:04.380 align:start position:0% to input from people that say they want 00:46:04.380 --> 00:46:05.990 align:start position:0% to input from people that say they want to<00:46:04.500> use<00:46:04.680> that 00:46:05.990 --> 00:46:06.000 align:start position:0% to use that 00:46:06.000 --> 00:46:08.210 align:start position:0% to use that but<00:46:06.540> thanks<00:46:06.839> for<00:46:07.020> mentioning<00:46:07.380> and<00:46:07.800> yeah<00:46:07.920> we 00:46:08.210 --> 00:46:08.220 align:start position:0% but thanks for mentioning and yeah we 00:46:08.220 --> 00:46:12.349 align:start position:0% but thanks for mentioning and yeah we have<00:46:08.339> evm<00:46:08.819> panel<00:46:09.119> on<00:46:09.359> Friday<00:46:09.480> as<00:46:09.839> well 00:46:12.349 --> 00:46:12.359 align:start position:0% 00:46:12.359 --> 00:46:14.630 align:start position:0% I<00:46:12.780> do<00:46:12.839> have<00:46:12.960> another<00:46:13.079> VIP 00:46:14.630 --> 00:46:14.640 align:start position:0% I do have another VIP 00:46:14.640 --> 00:46:16.309 align:start position:0% I do have another VIP I<00:46:15.119> didn't<00:46:15.180> wanted<00:46:15.359> to<00:46:15.540> like<00:46:15.660> talk<00:46:15.780> with<00:46:15.960> the<00:46:16.079> UF 00:46:16.309 --> 00:46:16.319 align:start position:0% I didn't wanted to like talk with the UF 00:46:16.319 --> 00:46:17.809 align:start position:0% I didn't wanted to like talk with the UF because<00:46:16.500> we<00:46:16.740> spent<00:46:16.920> like<00:46:17.160> two<00:46:17.339> hours<00:46:17.460> on<00:46:17.700> like 00:46:17.809 --> 00:46:17.819 align:start position:0% because we spent like two hours on like 00:46:17.819 --> 00:46:19.790 align:start position:0% because we spent like two hours on like protocol<00:46:18.180> Workshop 00:46:19.790 --> 00:46:19.800 align:start position:0% protocol Workshop 00:46:19.800 --> 00:46:21.230 align:start position:0% protocol Workshop um<00:46:19.920> but<00:46:20.220> this<00:46:20.400> app<00:46:20.640> is<00:46:20.819> really<00:46:21.000> cool<00:46:21.119> it's 00:46:21.230 --> 00:46:21.240 align:start position:0% um but this app is really cool it's 00:46:21.240 --> 00:46:24.050 align:start position:0% um but this app is really cool it's called<00:46:21.480> M<00:46:21.660> Copy<00:46:22.079> for<00:46:22.440> memory<00:46:22.740> copying 00:46:24.050 --> 00:46:24.060 align:start position:0% called M Copy for memory copying 00:46:24.060 --> 00:46:25.609 align:start position:0% called M Copy for memory copying it's<00:46:24.359> not<00:46:24.480> marriage<00:46:24.780> yet<00:46:24.900> because<00:46:25.140> of<00:46:25.319> the<00:46:25.380> EIP 00:46:25.609 --> 00:46:25.619 align:start position:0% it's not marriage yet because of the EIP 00:46:25.619 --> 00:46:27.530 align:start position:0% it's not marriage yet because of the EIP process<00:46:26.099> but 00:46:27.530 --> 00:46:27.540 align:start position:0% process but 00:46:27.540 --> 00:46:28.970 align:start position:0% process but um<00:46:27.660> I'm<00:46:27.720> going<00:46:27.900> to<00:46:28.020> summarize<00:46:28.319> it<00:46:28.560> so 00:46:28.970 --> 00:46:28.980 align:start position:0% um I'm going to summarize it so 00:46:28.980 --> 00:46:31.010 align:start position:0% um I'm going to summarize it so basically<00:46:29.339> the<00:46:30.060> only<00:46:30.180> way<00:46:30.359> to<00:46:30.480> copy<00:46:30.720> memory 00:46:31.010 --> 00:46:31.020 align:start position:0% basically the only way to copy memory 00:46:31.020 --> 00:46:33.290 align:start position:0% basically the only way to copy memory right<00:46:31.200> now<00:46:31.380> there<00:46:31.740> are<00:46:31.920> two<00:46:31.980> ways<00:46:32.339> one<00:46:32.819> way<00:46:33.000> is 00:46:33.290 --> 00:46:33.300 align:start position:0% right now there are two ways one way is 00:46:33.300 --> 00:46:35.210 align:start position:0% right now there are two ways one way is to<00:46:33.480> do<00:46:33.599> it<00:46:33.720> at<00:46:33.839> the<00:46:33.960> Loop<00:46:34.260> amp<00:46:34.680> store<00:46:34.800> M<00:46:35.040> low 00:46:35.210 --> 00:46:35.220 align:start position:0% to do it at the Loop amp store M low 00:46:35.220 --> 00:46:36.890 align:start position:0% to do it at the Loop amp store M low damn<00:46:35.400> store<00:46:35.640> and<00:46:36.420> that<00:46:36.540> was<00:46:36.720> really 00:46:36.890 --> 00:46:36.900 align:start position:0% damn store and that was really 00:46:36.900 --> 00:46:38.870 align:start position:0% damn store and that was really recognized<00:46:37.560> in<00:46:37.800> the<00:46:37.980> identity<00:46:38.339> pre-compile 00:46:38.870 --> 00:46:38.880 align:start position:0% recognized in the identity pre-compile 00:46:38.880 --> 00:46:40.849 align:start position:0% recognized in the identity pre-compile was<00:46:39.119> introduced 00:46:40.849 --> 00:46:40.859 align:start position:0% was introduced 00:46:40.859 --> 00:46:42.470 align:start position:0% was introduced um<00:46:40.920> I<00:46:41.099> think<00:46:41.220> the<00:46:41.339> first<00:46:41.520> like<00:46:41.760> few<00:46:42.060> months 00:46:42.470 --> 00:46:42.480 align:start position:0% um I think the first like few months 00:46:42.480 --> 00:46:44.450 align:start position:0% um I think the first like few months after<00:46:43.079> the<00:46:43.500> launch<00:46:43.619> of<00:46:43.800> ethereum<00:46:44.160> that<00:46:44.339> was 00:46:44.450 --> 00:46:44.460 align:start position:0% after the launch of ethereum that was 00:46:44.460 --> 00:46:46.790 align:start position:0% after the launch of ethereum that was used<00:46:44.579> by<00:46:44.760> the<00:46:44.940> solid<00:46:45.300> compiler<00:46:45.780> but<00:46:46.500> then<00:46:46.619> with 00:46:46.790 --> 00:46:46.800 align:start position:0% used by the solid compiler but then with 00:46:46.800 --> 00:46:49.010 align:start position:0% used by the solid compiler but then with the<00:46:46.980> Shanghai<00:46:47.280> attacks<00:46:47.760> it<00:46:47.940> was<00:46:48.060> repriced<00:46:48.720> and 00:46:49.010 --> 00:46:49.020 align:start position:0% the Shanghai attacks it was repriced and 00:46:49.020 --> 00:46:50.990 align:start position:0% the Shanghai attacks it was repriced and the<00:46:49.260> call<00:46:49.319> was<00:46:49.560> becoming<00:46:49.980> too<00:46:50.099> expensive<00:46:50.520> so 00:46:50.990 --> 00:46:51.000 align:start position:0% the call was becoming too expensive so 00:46:51.000 --> 00:46:52.970 align:start position:0% the call was becoming too expensive so nobody<00:46:51.359> used<00:46:51.839> the<00:46:52.020> identity<00:46:52.380> compiler 00:46:52.970 --> 00:46:52.980 align:start position:0% nobody used the identity compiler 00:46:52.980 --> 00:46:55.670 align:start position:0% nobody used the identity compiler anymore<00:46:53.099> it<00:46:53.400> is<00:46:53.520> just<00:46:53.700> there 00:46:55.670 --> 00:46:55.680 align:start position:0% anymore it is just there 00:46:55.680 --> 00:46:57.470 align:start position:0% anymore it is just there I<00:46:55.980> think<00:46:56.099> Viper<00:46:56.579> use<00:46:56.760> it<00:46:56.940> now<00:46:57.060> but<00:46:57.359> it's 00:46:57.470 --> 00:46:57.480 align:start position:0% I think Viper use it now but it's 00:46:57.480 --> 00:46:59.569 align:start position:0% I think Viper use it now but it's already<00:46:57.720> still<00:46:58.079> uses<00:46:58.319> the<00:46:58.440> loop 00:46:59.569 --> 00:46:59.579 align:start position:0% already still uses the loop 00:46:59.579 --> 00:47:02.690 align:start position:0% already still uses the loop um<00:46:59.700> so<00:47:00.300> then<00:47:00.480> the<00:47:00.660> mem<00:47:00.780> copy<00:47:01.200> op<00:47:01.380> code<00:47:01.700> fixes 00:47:02.690 --> 00:47:02.700 align:start position:0% um so then the mem copy op code fixes 00:47:02.700 --> 00:47:04.849 align:start position:0% um so then the mem copy op code fixes all<00:47:02.880> of<00:47:03.000> this 00:47:04.849 --> 00:47:04.859 align:start position:0% all of this 00:47:04.859 --> 00:47:06.710 align:start position:0% all of this and<00:47:05.460> I<00:47:05.760> just<00:47:05.940> I'm<00:47:06.119> trying<00:47:06.300> to<00:47:06.420> read<00:47:06.540> the 00:47:06.710 --> 00:47:06.720 align:start position:0% and I just I'm trying to read the 00:47:06.720 --> 00:47:09.950 align:start position:0% and I just I'm trying to read the numbers<00:47:06.839> so 00:47:09.950 --> 00:47:09.960 align:start position:0% 00:47:09.960 --> 00:47:13.250 align:start position:0% yeah<00:47:10.560> it<00:47:10.680> takes<00:47:10.800> like<00:47:11.040> 800<00:47:11.460> gas<00:47:11.760> to<00:47:12.300> to<00:47:12.900> copy 00:47:13.250 --> 00:47:13.260 align:start position:0% yeah it takes like 800 gas to to copy 00:47:13.260 --> 00:47:17.089 align:start position:0% yeah it takes like 800 gas to to copy 255<00:47:14.480> 256<00:47:15.480> bytes 00:47:17.089 --> 00:47:17.099 align:start position:0% 255 256 bytes 00:47:17.099 --> 00:47:18.470 align:start position:0% 255 256 bytes um 00:47:18.470 --> 00:47:18.480 align:start position:0% um 00:47:18.480 --> 00:47:20.630 align:start position:0% um with<00:47:19.380> the<00:47:19.500> Shanghai<00:47:19.859> course<00:47:20.099> with<00:47:20.339> the<00:47:20.460> recent 00:47:20.630 --> 00:47:20.640 align:start position:0% with the Shanghai course with the recent 00:47:20.640 --> 00:47:24.410 align:start position:0% with the Shanghai course with the recent cost<00:47:20.819> is<00:47:21.000> 160<00:47:21.660> we<00:47:22.140> demo<00:47:22.440> them<00:47:22.680> towards<00:47:23.099> 100 00:47:24.410 --> 00:47:24.420 align:start position:0% cost is 160 we demo them towards 100 00:47:24.420 --> 00:47:27.650 align:start position:0% cost is 160 we demo them towards 100 um and<00:47:24.540> the<00:47:24.660> dip<00:47:24.900> it<00:47:25.079> would<00:47:25.260> be<00:47:25.380> 25<00:47:25.619> by<00:47:26.099> 25<00:47:26.520> gas 00:47:27.650 --> 00:47:27.660 align:start position:0% um and the dip it would be 25 by 25 gas 00:47:27.660 --> 00:47:31.010 align:start position:0% um and the dip it would be 25 by 25 gas we<00:47:28.440> did<00:47:28.619> some<00:47:28.800> analysis 00:47:31.010 --> 00:47:31.020 align:start position:0% we did some analysis 00:47:31.020 --> 00:47:31.970 align:start position:0% we did some analysis um 00:47:31.970 --> 00:47:31.980 align:start position:0% um 00:47:31.980 --> 00:47:33.890 align:start position:0% um I<00:47:32.280> think<00:47:32.339> like<00:47:32.520> 25<00:47:32.700> of<00:47:33.300> all<00:47:33.480> the<00:47:33.660> memory 00:47:33.890 --> 00:47:33.900 align:start position:0% I think like 25 of all the memory 00:47:33.900 --> 00:47:35.390 align:start position:0% I think like 25 of all the memory copying<00:47:34.319> would<00:47:34.560> be 00:47:35.390 --> 00:47:35.400 align:start position:0% copying would be 00:47:35.400 --> 00:47:38.030 align:start position:0% copying would be improved<00:47:36.119> by<00:47:36.240> M<00:47:36.480> Copy 00:47:38.030 --> 00:47:38.040 align:start position:0% improved by M Copy 00:47:38.040 --> 00:47:40.790 align:start position:0% improved by M Copy um<00:47:38.099> and<00:47:38.099> there's<00:47:38.400> actually<00:47:38.640> one<00:47:39.060> feature 00:47:40.790 --> 00:47:40.800 align:start position:0% um and there's actually one feature 00:47:40.800 --> 00:47:43.609 align:start position:0% um and there's actually one feature in<00:47:41.160> the<00:47:41.280> solid<00:47:41.579> compiler<00:47:42.060> which<00:47:42.300> is<00:47:42.480> kinda<00:47:42.960> be 00:47:43.609 --> 00:47:43.619 align:start position:0% in the solid compiler which is kinda be 00:47:43.619 --> 00:47:45.530 align:start position:0% in the solid compiler which is kinda be I<00:47:44.280> mean<00:47:44.339> it's<00:47:44.460> not<00:47:44.579> blocked<00:47:44.940> by<00:47:45.000> this<00:47:45.240> but<00:47:45.420> it's 00:47:45.530 --> 00:47:45.540 align:start position:0% I mean it's not blocked by this but it's 00:47:45.540 --> 00:47:46.910 align:start position:0% I mean it's not blocked by this but it's not<00:47:45.720> implemented 00:47:46.910 --> 00:47:46.920 align:start position:0% not implemented 00:47:46.920 --> 00:47:50.870 align:start position:0% not implemented um slicing<00:47:47.520> of<00:47:47.819> memory<00:47:48.540> arrays<00:47:49.220> and<00:47:50.220> a<00:47:50.700> lot<00:47:50.760> of 00:47:50.870 --> 00:47:50.880 align:start position:0% um slicing of memory arrays and a lot of 00:47:50.880 --> 00:47:53.150 align:start position:0% um slicing of memory arrays and a lot of cases<00:47:51.180> people<00:47:51.480> are<00:47:51.660> doing<00:47:51.839> like<00:47:52.200> forcefully 00:47:53.150 --> 00:47:53.160 align:start position:0% cases people are doing like forcefully 00:47:53.160 --> 00:47:55.730 align:start position:0% cases people are doing like forcefully using<00:47:53.460> call<00:47:53.640> data<00:47:54.060> stuff<00:47:54.260> because<00:47:55.260> that<00:47:55.560> can 00:47:55.730 --> 00:47:55.740 align:start position:0% using call data stuff because that can 00:47:55.740 --> 00:47:57.710 align:start position:0% using call data stuff because that can be<00:47:55.859> sliced<00:47:56.220> in<00:47:56.339> the<00:47:56.520> compiler<00:47:56.940> setting<00:47:57.599> mem 00:47:57.710 --> 00:47:57.720 align:start position:0% be sliced in the compiler setting mem 00:47:57.720 --> 00:48:00.470 align:start position:0% be sliced in the compiler setting mem copy<00:47:58.140> a<00:47:58.260> cheap<00:47:58.440> mem<00:47:58.619> copy<00:47:59.040> would<00:47:59.940> also<00:48:00.180> improve 00:48:00.470 --> 00:48:00.480 align:start position:0% copy a cheap mem copy would also improve 00:48:00.480 --> 00:48:04.550 align:start position:0% copy a cheap mem copy would also improve solidity<00:48:01.079> as<00:48:01.260> a<00:48:01.440> language 00:48:04.550 --> 00:48:04.560 align:start position:0% 00:48:04.560 --> 00:48:10.730 align:start position:0% that's<00:48:05.160> it 00:48:10.730 --> 00:48:10.740 align:start position:0% 00:48:10.740 --> 00:48:14.390 align:start position:0% yes<00:48:11.220> the<00:48:11.460> reason<00:48:11.579> I<00:48:11.760> said<00:48:11.940> I<00:48:12.180> have<00:48:12.420> EIP<00:48:12.839> because 00:48:14.390 --> 00:48:14.400 align:start position:0% yes the reason I said I have EIP because 00:48:14.400 --> 00:48:15.829 align:start position:0% yes the reason I said I have EIP because um it's<00:48:14.940> almost<00:48:15.060> certainly<00:48:15.480> not<00:48:15.599> for 00:48:15.829 --> 00:48:15.839 align:start position:0% um it's almost certainly not for 00:48:15.839 --> 00:48:17.569 align:start position:0% um it's almost certainly not for Shanghai<00:48:16.260> but<00:48:16.680> I<00:48:16.920> don't<00:48:17.040> think<00:48:17.160> it's<00:48:17.400> been 00:48:17.569 --> 00:48:17.579 align:start position:0% Shanghai but I don't think it's been 00:48:17.579 --> 00:48:19.609 align:start position:0% Shanghai but I don't think it's been talked<00:48:17.940> about<00:48:18.000> at<00:48:18.359> all<00:48:18.540> and<00:48:18.900> it's<00:48:19.079> nice<00:48:19.440> to 00:48:19.609 --> 00:48:19.619 align:start position:0% talked about at all and it's nice to 00:48:19.619 --> 00:48:20.690 align:start position:0% talked about at all and it's nice to like 00:48:20.690 --> 00:48:20.700 align:start position:0% like 00:48:20.700 --> 00:48:24.290 align:start position:0% like um<00:48:20.760> get<00:48:21.000> people's<00:48:21.359> brains<00:48:21.780> Brewing<00:48:22.260> on<00:48:22.740> it<00:48:22.920> so 00:48:24.290 --> 00:48:24.300 align:start position:0% um get people's brains Brewing on it so 00:48:24.300 --> 00:48:26.569 align:start position:0% um get people's brains Brewing on it so um<00:48:24.359> first<00:48:25.020> of<00:48:25.140> all<00:48:25.260> the<00:48:25.740> ones<00:48:26.040> based<00:48:26.339> on<00:48:26.400> this 00:48:26.569 --> 00:48:26.579 align:start position:0% um first of all the ones based on this 00:48:26.579 --> 00:48:29.809 align:start position:0% um first of all the ones based on this ERC<00:48:27.060> 457<00:48:27.900> right<00:48:28.200> which<00:48:28.560> is<00:48:28.740> so<00:48:29.280> much<00:48:29.400> the<00:48:29.640> kind 00:48:29.809 --> 00:48:29.819 align:start position:0% ERC 457 right which is so much the kind 00:48:29.819 --> 00:48:31.490 align:start position:0% ERC 457 right which is so much the kind of<00:48:29.940> abstraction<00:48:30.240> that's<00:48:30.960> like<00:48:31.140> a<00:48:31.260> way<00:48:31.380> of 00:48:31.490 --> 00:48:31.500 align:start position:0% of abstraction that's like a way of 00:48:31.500 --> 00:48:32.809 align:start position:0% of abstraction that's like a way of getting<00:48:31.619> a<00:48:31.800> kind<00:48:32.220> of<00:48:32.280> abstraction<00:48:32.579> without 00:48:32.809 --> 00:48:32.819 align:start position:0% getting a kind of abstraction without 00:48:32.819 --> 00:48:34.849 align:start position:0% getting a kind of abstraction without requiring<00:48:33.300> a<00:48:33.420> hard<00:48:33.540> Fork<00:48:33.960> to<00:48:34.319> avoid<00:48:34.560> all<00:48:34.680> those 00:48:34.849 --> 00:48:34.859 align:start position:0% requiring a hard Fork to avoid all those 00:48:34.859 --> 00:48:38.150 align:start position:0% requiring a hard Fork to avoid all those like<00:48:35.160> EIP<00:48:35.880> processed<00:48:36.540> mess 00:48:38.150 --> 00:48:38.160 align:start position:0% like EIP processed mess 00:48:38.160 --> 00:48:38.750 align:start position:0% like EIP processed mess um 00:48:38.750 --> 00:48:38.760 align:start position:0% um 00:48:38.760 --> 00:48:42.710 align:start position:0% um and<00:48:40.140> um<00:48:40.200> this<00:48:40.980> we<00:48:41.220> found<00:48:41.579> that<00:48:41.760> people<00:48:41.940> quite 00:48:42.710 --> 00:48:42.720 align:start position:0% and um this we found that people quite 00:48:42.720 --> 00:48:45.290 align:start position:0% and um this we found that people quite like<00:48:42.960> this<00:48:43.680> approach<00:48:44.040> right<00:48:44.339> because 00:48:45.290 --> 00:48:45.300 align:start position:0% like this approach right because 00:48:45.300 --> 00:48:46.430 align:start position:0% like this approach right because um they<00:48:45.540> can<00:48:45.660> already<00:48:45.780> start<00:48:46.020> using<00:48:46.319> their 00:48:46.430 --> 00:48:46.440 align:start position:0% um they can already start using their 00:48:46.440 --> 00:48:48.890 align:start position:0% um they can already start using their smart<00:48:46.619> contract<00:48:46.920> vaults<00:48:47.339> but<00:48:47.940> we<00:48:48.180> found<00:48:48.480> that 00:48:48.890 --> 00:48:48.900 align:start position:0% smart contract vaults but we found that 00:48:48.900 --> 00:48:51.710 align:start position:0% smart contract vaults but we found that users<00:48:49.500> actually<00:48:49.859> still<00:48:50.819> complain<00:48:51.300> quite<00:48:51.599> a 00:48:51.710 --> 00:48:51.720 align:start position:0% users actually still complain quite a 00:48:51.720 --> 00:48:53.690 align:start position:0% users actually still complain quite a bit<00:48:51.780> about<00:48:52.560> um<00:48:52.619> smart<00:48:52.859> contract<00:48:53.220> worlds 00:48:53.690 --> 00:48:53.700 align:start position:0% bit about um smart contract worlds 00:48:53.700 --> 00:48:55.370 align:start position:0% bit about um smart contract worlds because 00:48:55.370 --> 00:48:55.380 align:start position:0% because 00:48:55.380 --> 00:48:57.050 align:start position:0% because um like<00:48:55.859> they<00:48:56.160> already<00:48:56.280> have<00:48:56.579> their<00:48:56.760> money<00:48:56.880> on 00:48:57.050 --> 00:48:57.060 align:start position:0% um like they already have their money on 00:48:57.060 --> 00:48:59.990 align:start position:0% um like they already have their money on elas<00:48:57.540> and<00:48:58.500> switching<00:48:59.220> all<00:48:59.400> their<00:48:59.579> balances 00:48:59.990 --> 00:49:00.000 align:start position:0% elas and switching all their balances 00:49:00.000 --> 00:49:01.430 align:start position:0% elas and switching all their balances and<00:49:00.180> all<00:49:00.359> their<00:49:00.480> all<00:49:00.660> their<00:49:00.839> nfts<00:49:01.319> and 00:49:01.430 --> 00:49:01.440 align:start position:0% and all their all their nfts and 00:49:01.440 --> 00:49:03.349 align:start position:0% and all their all their nfts and everything<00:49:01.619> is<00:49:02.220> just<00:49:02.520> too<00:49:02.880> much<00:49:03.000> for<00:49:03.180> them 00:49:03.349 --> 00:49:03.359 align:start position:0% everything is just too much for them 00:49:03.359 --> 00:49:06.109 align:start position:0% everything is just too much for them usually<00:49:03.720> so<00:49:04.619> we<00:49:04.980> were<00:49:05.220> thinking<00:49:05.579> quite<00:49:05.940> a<00:49:06.060> bit 00:49:06.109 --> 00:49:06.119 align:start position:0% usually so we were thinking quite a bit 00:49:06.119 --> 00:49:09.230 align:start position:0% usually so we were thinking quite a bit about<00:49:06.300> okay<00:49:06.540> like<00:49:06.839> how<00:49:07.140> can<00:49:07.260> we<00:49:07.880> develop<00:49:08.880> a 00:49:09.230 --> 00:49:09.240 align:start position:0% about okay like how can we develop a 00:49:09.240 --> 00:49:10.609 align:start position:0% about okay like how can we develop a kind<00:49:09.359> of<00:49:09.540> abstraction<00:49:09.780> more<00:49:10.020> how<00:49:10.260> can<00:49:10.440> we 00:49:10.609 --> 00:49:10.619 align:start position:0% kind of abstraction more how can we 00:49:10.619 --> 00:49:13.190 align:start position:0% kind of abstraction more how can we perhaps<00:49:11.220> enshrine<00:49:11.760> it<00:49:11.880> a<00:49:12.000> bit<00:49:12.119> and<00:49:12.720> so<00:49:12.900> some 00:49:13.190 --> 00:49:13.200 align:start position:0% perhaps enshrine it a bit and so some 00:49:13.200 --> 00:49:15.170 align:start position:0% perhaps enshrine it a bit and so some ideas<00:49:13.440> just<00:49:13.980> floating<00:49:14.339> around<00:49:14.579> again<00:49:14.880> there's 00:49:15.170 --> 00:49:15.180 align:start position:0% ideas just floating around again there's 00:49:15.180 --> 00:49:17.569 align:start position:0% ideas just floating around again there's no<00:49:15.359> EIP<00:49:15.720> set<00:49:16.079> and<00:49:16.319> there's<00:49:16.500> no<00:49:16.800> like<00:49:17.040> specific 00:49:17.569 --> 00:49:17.579 align:start position:0% no EIP set and there's no like specific 00:49:17.579 --> 00:49:20.690 align:start position:0% no EIP set and there's no like specific roadmap<00:49:18.300> set<00:49:18.540> but<00:49:19.260> an<00:49:19.500> example<00:49:19.800> is 00:49:20.690 --> 00:49:20.700 align:start position:0% roadmap set but an example is 00:49:20.700 --> 00:49:21.290 align:start position:0% roadmap set but an example is um 00:49:21.290 --> 00:49:21.300 align:start position:0% um 00:49:21.300 --> 00:49:23.930 align:start position:0% um making<00:49:21.900> a<00:49:22.079> new<00:49:22.200> transaction<00:49:22.619> type<00:49:22.940> which 00:49:23.930 --> 00:49:23.940 align:start position:0% making a new transaction type which 00:49:23.940 --> 00:49:27.770 align:start position:0% making a new transaction type which converts<00:49:24.540> an<00:49:24.780> eoa<00:49:25.339> to<00:49:26.339> a<00:49:26.880> Smart<00:49:27.180> contract<00:49:27.540> that 00:49:27.770 --> 00:49:27.780 align:start position:0% converts an eoa to a Smart contract that 00:49:27.780 --> 00:49:30.349 align:start position:0% converts an eoa to a Smart contract that you<00:49:27.900> specify<00:49:28.140> in<00:49:28.319> the<00:49:28.440> data<00:49:28.680> field<00:49:28.800> right<00:49:29.640> and 00:49:30.349 --> 00:49:30.359 align:start position:0% you specify in the data field right and 00:49:30.359 --> 00:49:33.370 align:start position:0% you specify in the data field right and this<00:49:30.839> basically<00:49:31.140> should<00:49:31.560> be<00:49:31.740> quite<00:49:31.980> a<00:49:32.160> simple 00:49:33.370 --> 00:49:33.380 align:start position:0% this basically should be quite a simple 00:49:33.380 --> 00:49:37.309 align:start position:0% this basically should be quite a simple new<00:49:34.380> transaction<00:49:34.740> type<00:49:35.420> there's<00:49:36.420> not<00:49:36.660> really 00:49:37.309 --> 00:49:37.319 align:start position:0% new transaction type there's not really 00:49:37.319 --> 00:49:38.809 align:start position:0% new transaction type there's not really that<00:49:37.680> much<00:49:37.859> complexity<00:49:38.280> as<00:49:38.460> far<00:49:38.579> as<00:49:38.640> I<00:49:38.760> can 00:49:38.809 --> 00:49:38.819 align:start position:0% that much complexity as far as I can 00:49:38.819 --> 00:49:40.250 align:start position:0% that much complexity as far as I can tell<00:49:39.000> but<00:49:39.119> please<00:49:39.300> love<00:49:39.780> to<00:49:39.960> hear<00:49:40.079> some 00:49:40.250 --> 00:49:40.260 align:start position:0% tell but please love to hear some 00:49:40.260 --> 00:49:42.829 align:start position:0% tell but please love to hear some comments<00:49:40.619> some<00:49:41.160> more<00:49:41.400> advanced<00:49:41.880> ones 00:49:42.829 --> 00:49:42.839 align:start position:0% comments some more advanced ones 00:49:42.839 --> 00:49:46.270 align:start position:0% comments some more advanced ones and<00:49:43.319> again<00:49:43.560> just<00:49:43.920> ideation<00:49:44.720> is 00:49:46.270 --> 00:49:46.280 align:start position:0% and again just ideation is 00:49:46.280 --> 00:49:50.829 align:start position:0% and again just ideation is perhaps<00:49:47.280> making<00:49:48.060> an<00:49:48.720> EIP<00:49:49.020> which<00:49:49.380> converts<00:49:50.099> all 00:49:50.829 --> 00:49:50.839 align:start position:0% perhaps making an EIP which converts all 00:49:50.839 --> 00:49:53.890 align:start position:0% perhaps making an EIP which converts all current<00:49:51.839> eoa<00:49:52.380> accounts<00:49:52.980> into<00:49:53.280> a<00:49:53.579> sort<00:49:53.760> of 00:49:53.890 --> 00:49:53.900 align:start position:0% current eoa accounts into a sort of 00:49:53.900 --> 00:49:58.550 align:start position:0% current eoa accounts into a sort of default<00:49:54.900> proxy<00:49:56.099> smart<00:49:56.640> contract<00:49:57.119> World<00:49:57.560> which 00:49:58.550 --> 00:49:58.560 align:start position:0% default proxy smart contract World which 00:49:58.560 --> 00:50:01.550 align:start position:0% default proxy smart contract World which uses<00:49:58.980> the<00:49:59.099> current<00:49:59.220> ecdsa<00:50:00.319> signature<00:50:01.319> scheme 00:50:01.550 --> 00:50:01.560 align:start position:0% uses the current ecdsa signature scheme 00:50:01.560 --> 00:50:03.829 align:start position:0% uses the current ecdsa signature scheme that<00:50:01.680> EO<00:50:01.980> has<00:50:02.160> already<00:50:02.280> used<00:50:02.520> right<00:50:03.359> and 00:50:03.829 --> 00:50:03.839 align:start position:0% that EO has already used right and 00:50:03.839 --> 00:50:06.470 align:start position:0% that EO has already used right and another<00:50:04.140> sort<00:50:04.560> of<00:50:04.680> a<00:50:04.800> more<00:50:04.980> advanced<00:50:05.400> one<00:50:05.640> is 00:50:06.470 --> 00:50:06.480 align:start position:0% another sort of a more advanced one is 00:50:06.480 --> 00:50:09.530 align:start position:0% another sort of a more advanced one is so<00:50:07.319> this<00:50:07.440> ERC<00:50:07.920> 4537<00:50:08.640> it<00:50:08.880> works<00:50:09.180> with<00:50:09.300> a 00:50:09.530 --> 00:50:09.540 align:start position:0% so this ERC 4537 it works with a 00:50:09.540 --> 00:50:10.970 align:start position:0% so this ERC 4537 it works with a so-called<00:50:09.839> entry<00:50:10.140> point<00:50:10.260> smart<00:50:10.560> contract 00:50:10.970 --> 00:50:10.980 align:start position:0% so-called entry point smart contract 00:50:10.980 --> 00:50:14.030 align:start position:0% so-called entry point smart contract which<00:50:11.400> is<00:50:11.579> through<00:50:11.880> which<00:50:12.240> you<00:50:12.900> root<00:50:13.200> all<00:50:13.800> your 00:50:14.030 --> 00:50:14.040 align:start position:0% which is through which you root all your 00:50:14.040 --> 00:50:15.890 align:start position:0% which is through which you root all your user<00:50:14.400> operations<00:50:14.880> to<00:50:15.300> interact<00:50:15.540> with<00:50:15.720> your 00:50:15.890 --> 00:50:15.900 align:start position:0% user operations to interact with your 00:50:15.900 --> 00:50:16.970 align:start position:0% user operations to interact with your wallet 00:50:16.970 --> 00:50:16.980 align:start position:0% wallet 00:50:16.980 --> 00:50:19.309 align:start position:0% wallet and<00:50:17.520> this<00:50:17.940> causes<00:50:18.240> a<00:50:18.359> lot<00:50:18.480> of<00:50:18.599> gas<00:50:18.780> because<00:50:19.079> you 00:50:19.309 --> 00:50:19.319 align:start position:0% and this causes a lot of gas because you 00:50:19.319 --> 00:50:21.410 align:start position:0% and this causes a lot of gas because you do<00:50:19.500> all<00:50:19.920> the<00:50:20.099> signature<00:50:20.520> verification<00:50:21.000> all 00:50:21.410 --> 00:50:21.420 align:start position:0% do all the signature verification all 00:50:21.420 --> 00:50:22.190 align:start position:0% do all the signature verification all the 00:50:22.190 --> 00:50:22.200 align:start position:0% the 00:50:22.200 --> 00:50:25.250 align:start position:0% the um<00:50:22.260> all<00:50:22.560> the<00:50:22.859> stuff<00:50:23.040> on<00:50:23.940> chain<00:50:24.119> using<00:50:24.540> well<00:50:24.780> evm 00:50:25.250 --> 00:50:25.260 align:start position:0% um all the stuff on chain using well evm 00:50:25.260 --> 00:50:27.770 align:start position:0% um all the stuff on chain using well evm up<00:50:25.380> codes<00:50:25.619> right<00:50:25.859> so<00:50:26.280> what<00:50:26.520> if<00:50:26.700> instead<00:50:27.119> you 00:50:27.770 --> 00:50:27.780 align:start position:0% up codes right so what if instead you 00:50:27.780 --> 00:50:30.710 align:start position:0% up codes right so what if instead you made<00:50:28.200> this<00:50:28.440> part<00:50:28.680> of<00:50:28.859> the<00:50:28.980> protocol<00:50:29.339> right<00:50:30.000> in 00:50:30.710 --> 00:50:30.720 align:start position:0% made this part of the protocol right in 00:50:30.720 --> 00:50:32.630 align:start position:0% made this part of the protocol right in um that<00:50:30.900> could<00:50:31.079> be<00:50:31.200> validated<00:50:31.560> outside<00:50:31.800> and 00:50:32.630 --> 00:50:32.640 align:start position:0% um that could be validated outside and 00:50:32.640 --> 00:50:36.410 align:start position:0% um that could be validated outside and so<00:50:32.760> it<00:50:33.000> would<00:50:33.060> save<00:50:33.119> usually<00:50:33.480> lots<00:50:33.720> of<00:50:33.780> gas 00:50:36.410 --> 00:50:36.420 align:start position:0% 00:50:36.420 --> 00:50:41.210 align:start position:0% foreign 00:50:41.210 --> 00:50:41.220 align:start position:0% 00:50:41.220 --> 00:50:42.890 align:start position:0% oh<00:50:41.700> yeah<00:50:41.819> just<00:50:42.060> real<00:50:42.180> quick<00:50:42.359> this<00:50:42.480> isn't<00:50:42.720> on 00:50:42.890 --> 00:50:42.900 align:start position:0% oh yeah just real quick this isn't on 00:50:42.900 --> 00:50:45.290 align:start position:0% oh yeah just real quick this isn't on that<00:50:43.020> but<00:50:43.319> uh<00:50:43.859> it<00:50:44.099> hasn't<00:50:44.400> been<00:50:44.640> suggested<00:50:45.119> for 00:50:45.290 --> 00:50:45.300 align:start position:0% that but uh it hasn't been suggested for 00:50:45.300 --> 00:50:47.329 align:start position:0% that but uh it hasn't been suggested for Shanghai<00:50:45.720> but<00:50:46.020> prior<00:50:46.319> to<00:50:46.440> the<00:50:46.619> merge<00:50:46.859> it<00:50:47.040> had<00:50:47.220> a 00:50:47.329 --> 00:50:47.339 align:start position:0% Shanghai but prior to the merge it had a 00:50:47.339 --> 00:50:49.549 align:start position:0% Shanghai but prior to the merge it had a bit<00:50:47.460> of<00:50:47.579> support<00:50:47.700> uh<00:50:48.480> time<00:50:48.720> aware<00:50:48.960> base<00:50:49.260> fee 00:50:49.549 --> 00:50:49.559 align:start position:0% bit of support uh time aware base fee 00:50:49.559 --> 00:50:51.470 align:start position:0% bit of support uh time aware base fee calculation<00:50:50.220> it<00:50:50.760> would<00:50:50.880> essentially<00:50:51.240> just 00:50:51.470 --> 00:50:51.480 align:start position:0% calculation it would essentially just 00:50:51.480 --> 00:50:53.630 align:start position:0% calculation it would essentially just make<00:50:51.660> 1559<00:50:52.440> quite<00:50:52.680> proof<00:50:53.040> of<00:50:53.099> stake<00:50:53.339> friendly 00:50:53.630 --> 00:50:53.640 align:start position:0% make 1559 quite proof of stake friendly 00:50:53.640 --> 00:50:56.150 align:start position:0% make 1559 quite proof of stake friendly 1559<00:50:54.599> is<00:50:54.839> aware<00:50:55.079> of<00:50:55.200> blocks<00:50:55.619> it's<00:50:55.800> not<00:50:55.980> aware 00:50:56.150 --> 00:50:56.160 align:start position:0% 1559 is aware of blocks it's not aware 00:50:56.160 --> 00:50:58.130 align:start position:0% 1559 is aware of blocks it's not aware of<00:50:56.339> slots<00:50:56.640> you<00:50:57.300> could<00:50:57.359> have<00:50:57.540> say<00:50:57.780> like<00:50:57.960> an 00:50:58.130 --> 00:50:58.140 align:start position:0% of slots you could have say like an 00:50:58.140 --> 00:50:59.809 align:start position:0% of slots you could have say like an empty<00:50:58.380> block<00:50:58.559> with<00:50:58.800> proof<00:50:59.160> of<00:50:59.220> work<00:50:59.400> but<00:50:59.640> now 00:50:59.809 --> 00:50:59.819 align:start position:0% empty block with proof of work but now 00:50:59.819 --> 00:51:01.549 align:start position:0% empty block with proof of work but now you<00:51:00.000> can<00:51:00.059> have<00:51:00.180> missed<00:51:00.660> block<00:51:00.900> proposal<00:51:01.440> so 00:51:01.549 --> 00:51:01.559 align:start position:0% you can have missed block proposal so 00:51:01.559 --> 00:51:02.630 align:start position:0% you can have missed block proposal so here<00:51:01.680> we<00:51:01.859> go 00:51:02.630 --> 00:51:02.640 align:start position:0% here we go 00:51:02.640 --> 00:51:05.750 align:start position:0% here we go I<00:51:03.119> think<00:51:03.240> with<00:51:03.599> a<00:51:03.839> with<00:51:04.079> the<00:51:04.319> amount<00:51:04.619> of<00:51:04.859> missed 00:51:05.750 --> 00:51:05.760 align:start position:0% I think with a with the amount of missed 00:51:05.760 --> 00:51:07.670 align:start position:0% I think with a with the amount of missed slots<00:51:06.000> we<00:51:06.240> see<00:51:06.359> right<00:51:06.660> now<00:51:06.900> I<00:51:07.140> don't<00:51:07.380> think<00:51:07.500> it 00:51:07.670 --> 00:51:07.680 align:start position:0% slots we see right now I don't think it 00:51:07.680 --> 00:51:11.870 align:start position:0% slots we see right now I don't think it makes<00:51:07.859> sense<00:51:08.040> to<00:51:08.280> to<00:51:08.460> do<00:51:08.640> it<00:51:08.819> now<00:51:09.420> uh<00:51:10.579> it's<00:51:11.579> it's 00:51:11.870 --> 00:51:11.880 align:start position:0% makes sense to to do it now uh it's it's 00:51:11.880 --> 00:51:14.329 align:start position:0% makes sense to to do it now uh it's it's like<00:51:12.180> I<00:51:12.599> don't<00:51:12.660> know<00:51:12.720> we're<00:51:12.960> seeing<00:51:13.319> like 00:51:14.329 --> 00:51:14.339 align:start position:0% like I don't know we're seeing like 00:51:14.339 --> 00:51:17.329 align:start position:0% like I don't know we're seeing like point<00:51:15.059> point<00:51:15.200> one<00:51:16.200> percent<00:51:16.440> point<00:51:16.920> zero<00:51:17.220> one 00:51:17.329 --> 00:51:17.339 align:start position:0% point point one percent point zero one 00:51:17.339 --> 00:51:18.829 align:start position:0% point point one percent point zero one percent<00:51:17.579> of<00:51:17.880> missed<00:51:18.359> slots<00:51:18.599> or<00:51:18.720> something 00:51:18.829 --> 00:51:18.839 align:start position:0% percent of missed slots or something 00:51:18.839 --> 00:51:19.849 align:start position:0% percent of missed slots or something like<00:51:19.020> this 00:51:19.849 --> 00:51:19.859 align:start position:0% like this 00:51:19.859 --> 00:51:21.470 align:start position:0% like this it<00:51:20.160> would<00:51:20.339> be<00:51:20.460> a<00:51:20.579> negligible<00:51:21.000> Improvement<00:51:21.359> to 00:51:21.470 --> 00:51:21.480 align:start position:0% it would be a negligible Improvement to 00:51:21.480 --> 00:51:23.510 align:start position:0% it would be a negligible Improvement to ux<00:51:21.780> so<00:51:22.020> yeah<00:51:22.200> just<00:51:22.500> for<00:51:22.740> a<00:51:22.980> cleanup<00:51:23.280> but<00:51:23.400> not 00:51:23.510 --> 00:51:23.520 align:start position:0% ux so yeah just for a cleanup but not 00:51:23.520 --> 00:51:35.750 align:start position:0% ux so yeah just for a cleanup but not necessarily<00:51:24.000> to<00:51:24.420> have 00:51:35.750 --> 00:51:35.760 align:start position:0% 00:51:35.760 --> 00:51:38.450 align:start position:0% so<00:51:36.119> uh<00:51:36.420> with<00:51:36.599> the<00:51:36.720> wallet<00:51:37.079> uh<00:51:37.740> I<00:51:38.220> think<00:51:38.339> there 00:51:38.450 --> 00:51:38.460 align:start position:0% so uh with the wallet uh I think there 00:51:38.460 --> 00:51:40.849 align:start position:0% so uh with the wallet uh I think there was<00:51:38.579> three<00:51:38.880> proposals<00:51:39.599> uh<00:51:40.260> I<00:51:40.440> just<00:51:40.559> wanted<00:51:40.680> to 00:51:40.849 --> 00:51:40.859 align:start position:0% was three proposals uh I just wanted to 00:51:40.859 --> 00:51:43.069 align:start position:0% was three proposals uh I just wanted to mention<00:51:40.980> there<00:51:41.280> was<00:51:41.460> one<00:51:41.640> proposal<00:51:42.180> where<00:51:42.480> uh 00:51:43.069 --> 00:51:43.079 align:start position:0% mention there was one proposal where uh 00:51:43.079 --> 00:51:44.930 align:start position:0% mention there was one proposal where uh you<00:51:43.559> said<00:51:43.740> that<00:51:43.920> we<00:51:44.040> could<00:51:44.220> just<00:51:44.339> Auto<00:51:44.520> convert 00:51:44.930 --> 00:51:44.940 align:start position:0% you said that we could just Auto convert 00:51:44.940 --> 00:51:47.390 align:start position:0% you said that we could just Auto convert everything<00:51:45.380> uh<00:51:46.380> no<00:51:46.559> that's<00:51:46.920> not<00:51:47.099> going<00:51:47.280> to 00:51:47.390 --> 00:51:47.400 align:start position:0% everything uh no that's not going to 00:51:47.400 --> 00:51:49.910 align:start position:0% everything uh no that's not going to happen<00:51:47.520> essentially<00:51:48.480> uh<00:51:49.140> that<00:51:49.680> that's 00:51:49.910 --> 00:51:49.920 align:start position:0% happen essentially uh that that's 00:51:49.920 --> 00:51:52.010 align:start position:0% happen essentially uh that that's already<00:51:50.099> a<00:51:50.400> huge<00:51:50.640> issue<00:51:51.119> for<00:51:51.300> vertical<00:51:51.660> trees 00:51:52.010 --> 00:51:52.020 align:start position:0% already a huge issue for vertical trees 00:51:52.020 --> 00:51:53.569 align:start position:0% already a huge issue for vertical trees where<00:51:52.559> you<00:51:52.740> just<00:51:52.859> want<00:51:52.920> to<00:51:53.040> do<00:51:53.160> an<00:51:53.280> upgrade 00:51:53.569 --> 00:51:53.579 align:start position:0% where you just want to do an upgrade 00:51:53.579 --> 00:51:55.790 align:start position:0% where you just want to do an upgrade where<00:51:53.940> the<00:51:54.359> state<00:51:54.540> just<00:51:54.839> gets<00:51:55.079> flipped<00:51:55.380> over 00:51:55.790 --> 00:51:55.800 align:start position:0% where the state just gets flipped over 00:51:55.800 --> 00:51:59.390 align:start position:0% where the state just gets flipped over and<00:51:55.980> it's<00:51:56.700> a<00:51:56.880> huge<00:51:57.119> linear<00:51:57.540> migration<00:51:58.200> and<00:51:59.099> we 00:51:59.390 --> 00:51:59.400 align:start position:0% and it's a huge linear migration and we 00:51:59.400 --> 00:52:00.650 align:start position:0% and it's a huge linear migration and we have<00:51:59.520> absolutely<00:51:59.819> no<00:52:00.000> idea<00:52:00.240> how<00:52:00.359> we're<00:52:00.480> going 00:52:00.650 --> 00:52:00.660 align:start position:0% have absolutely no idea how we're going 00:52:00.660 --> 00:52:02.809 align:start position:0% have absolutely no idea how we're going to<00:52:00.720> do<00:52:00.839> it<00:52:00.960> for<00:52:01.079> vocal<00:52:01.440> trees<00:52:01.800> so<00:52:02.099> let's<00:52:02.339> not<00:52:02.640> do 00:52:02.809 --> 00:52:02.819 align:start position:0% to do it for vocal trees so let's not do 00:52:02.819 --> 00:52:05.510 align:start position:0% to do it for vocal trees so let's not do it<00:52:03.000> twice<00:52:03.300> but<00:52:04.079> what<00:52:04.319> if<00:52:04.500> it's<00:52:04.619> not<00:52:04.800> actually 00:52:05.510 --> 00:52:05.520 align:start position:0% it twice but what if it's not actually 00:52:05.520 --> 00:52:07.430 align:start position:0% it twice but what if it's not actually touching<00:52:06.119> every<00:52:06.240> account<00:52:06.540> and<00:52:06.839> rather<00:52:07.140> it's 00:52:07.430 --> 00:52:07.440 align:start position:0% touching every account and rather it's 00:52:07.440 --> 00:52:09.890 align:start position:0% touching every account and rather it's there's<00:52:07.740> no<00:52:08.520> code<00:52:08.819> and<00:52:09.359> there's<00:52:09.540> a<00:52:09.720> message 00:52:09.890 --> 00:52:09.900 align:start position:0% there's no code and there's a message 00:52:09.900 --> 00:52:12.170 align:start position:0% there's no code and there's a message signed<00:52:10.380> from<00:52:10.440> that<00:52:10.619> account<00:52:10.880> and<00:52:11.880> it's 00:52:12.170 --> 00:52:12.180 align:start position:0% signed from that account and it's 00:52:12.180 --> 00:52:14.329 align:start position:0% signed from that account and it's treated<00:52:12.480> as<00:52:12.960> a<00:52:13.200> default<00:52:13.440> account<00:52:13.680> and<00:52:13.980> so<00:52:14.160> it 00:52:14.329 --> 00:52:14.339 align:start position:0% treated as a default account and so it 00:52:14.339 --> 00:52:17.390 align:start position:0% treated as a default account and so it falls<00:52:14.460> back<00:52:14.700> to<00:52:14.880> some<00:52:15.059> default<00:52:15.420> code 00:52:17.390 --> 00:52:17.400 align:start position:0% falls back to some default code 00:52:17.400 --> 00:52:21.230 align:start position:0% falls back to some default code um but<00:52:18.000> that<00:52:18.300> would<00:52:18.480> actually<00:52:18.780> break<00:52:19.700> the<00:52:20.700> new 00:52:21.230 --> 00:52:21.240 align:start position:0% um but that would actually break the new 00:52:21.240 --> 00:52:25.010 align:start position:0% um but that would actually break the new semantics<00:52:21.780> that<00:52:21.960> we<00:52:22.140> introduced<00:52:22.559> with 00:52:25.010 --> 00:52:25.020 align:start position:0% 00:52:25.020 --> 00:52:28.490 align:start position:0% right<00:52:25.559> you<00:52:26.339> know<00:52:26.520> which<00:52:26.760> exactly<00:52:27.359> I<00:52:27.780> mean<00:52:27.839> that 00:52:28.490 --> 00:52:28.500 align:start position:0% right you know which exactly I mean that 00:52:28.500 --> 00:52:31.190 align:start position:0% right you know which exactly I mean that no<00:52:28.680> eoa<00:52:29.280> can<00:52:29.579> also<00:52:29.880> have<00:52:30.000> contract<00:52:30.359> code 00:52:31.190 --> 00:52:31.200 align:start position:0% no eoa can also have contract code 00:52:31.200 --> 00:52:33.890 align:start position:0% no eoa can also have contract code but<00:52:31.680> there's<00:52:31.859> no<00:52:32.040> code<00:52:32.280> in<00:52:32.579> the<00:52:32.819> account<00:52:33.119> and 00:52:33.890 --> 00:52:33.900 align:start position:0% but there's no code in the account and 00:52:33.900 --> 00:52:36.049 align:start position:0% but there's no code in the account and so<00:52:34.079> it's<00:52:34.319> already<00:52:34.559> empty 00:52:36.049 --> 00:52:36.059 align:start position:0% so it's already empty 00:52:36.059 --> 00:52:37.490 align:start position:0% so it's already empty and<00:52:36.359> so<00:52:36.480> it<00:52:36.660> would<00:52:36.839> basically<00:52:37.020> be<00:52:37.140> like<00:52:37.319> me 00:52:37.490 --> 00:52:37.500 align:start position:0% and so it would basically be like me 00:52:37.500 --> 00:52:40.910 align:start position:0% and so it would basically be like me sending<00:52:37.980> a<00:52:38.339> transaction<00:52:39.260> and<00:52:40.260> rather<00:52:40.680> than 00:52:40.910 --> 00:52:40.920 align:start position:0% sending a transaction and rather than 00:52:40.920 --> 00:52:42.470 align:start position:0% sending a transaction and rather than executing<00:52:41.700> it<00:52:41.819> the<00:52:41.940> same<00:52:42.000> way<00:52:42.119> that<00:52:42.240> we<00:52:42.359> do 00:52:42.470 --> 00:52:42.480 align:start position:0% executing it the same way that we do 00:52:42.480 --> 00:52:44.030 align:start position:0% executing it the same way that we do today<00:52:42.660> it<00:52:43.140> would<00:52:43.260> realize<00:52:43.619> that<00:52:43.859> the 00:52:44.030 --> 00:52:44.040 align:start position:0% today it would realize that the 00:52:44.040 --> 00:52:46.670 align:start position:0% today it would realize that the recovered<00:52:44.520> address<00:52:44.640> has<00:52:45.059> no<00:52:45.240> code<00:52:45.480> in<00:52:46.200> it<00:52:46.380> and 00:52:46.670 --> 00:52:46.680 align:start position:0% recovered address has no code in it and 00:52:46.680 --> 00:52:48.950 align:start position:0% recovered address has no code in it and so<00:52:46.800> then<00:52:47.040> it<00:52:47.220> would<00:52:47.339> just<00:52:47.520> start<00:52:48.059> executing<00:52:48.720> it 00:52:48.950 --> 00:52:48.960 align:start position:0% so then it would just start executing it 00:52:48.960 --> 00:52:51.290 align:start position:0% so then it would just start executing it in<00:52:49.380> an<00:52:49.500> evm<00:52:49.920> frame<00:52:50.280> with<00:52:50.640> some<00:52:50.880> default 00:52:51.290 --> 00:52:51.300 align:start position:0% in an evm frame with some default 00:52:51.300 --> 00:52:53.450 align:start position:0% in an evm frame with some default account<00:52:51.599> code<00:52:51.960> that<00:52:52.500> implements<00:52:53.099> the<00:52:53.280> same 00:52:53.450 --> 00:52:53.460 align:start position:0% account code that implements the same 00:52:53.460 --> 00:52:57.770 align:start position:0% account code that implements the same concept<00:52:53.940> of<00:52:54.119> the<00:52:54.300> ecdsa<00:52:55.079> account 00:52:57.770 --> 00:52:57.780 align:start position:0% concept of the ecdsa account 00:52:57.780 --> 00:53:00.049 align:start position:0% concept of the ecdsa account okay<00:52:58.140> I<00:52:58.440> couldn't<00:52:58.559> follow<00:52:59.220> so<00:52:59.640> so<00:52:59.700> you 00:53:00.049 --> 00:53:00.059 align:start position:0% okay I couldn't follow so so you 00:53:00.059 --> 00:53:01.790 align:start position:0% okay I couldn't follow so so you wouldn't<00:53:00.240> set<00:53:00.540> the<00:53:00.780> set<00:53:01.140> the<00:53:01.260> contract<00:53:01.559> code 00:53:01.790 --> 00:53:01.800 align:start position:0% wouldn't set the set the contract code 00:53:01.800 --> 00:53:03.410 align:start position:0% wouldn't set the set the contract code you<00:53:02.099> would<00:53:02.280> not<00:53:02.339> set<00:53:02.520> the<00:53:02.640> contract<00:53:02.880> code<00:53:03.059> okay 00:53:03.410 --> 00:53:03.420 align:start position:0% you would not set the contract code okay 00:53:03.420 --> 00:53:09.349 align:start position:0% you would not set the contract code okay it's<00:53:04.020> a<00:53:04.140> fallback 00:53:09.349 --> 00:53:09.359 align:start position:0% 00:53:09.359 --> 00:53:11.390 align:start position:0% okay<00:53:09.780> I<00:53:10.020> think<00:53:10.140> we're<00:53:10.260> going<00:53:10.440> to<00:53:10.500> wrap<00:53:10.740> up<00:53:10.859> uh 00:53:11.390 --> 00:53:11.400 align:start position:0% okay I think we're going to wrap up uh 00:53:11.400 --> 00:53:12.950 align:start position:0% okay I think we're going to wrap up uh it's<00:53:11.579> past<00:53:11.940> six 00:53:12.950 --> 00:53:12.960 align:start position:0% it's past six 00:53:12.960 --> 00:53:14.930 align:start position:0% it's past six um<00:53:13.079> so<00:53:13.319> first<00:53:13.800> of<00:53:13.980> all<00:53:14.040> thanks<00:53:14.339> everyone<00:53:14.520> for 00:53:14.930 --> 00:53:14.940 align:start position:0% um so first of all thanks everyone for 00:53:14.940 --> 00:53:15.829 align:start position:0% um so first of all thanks everyone for coming 00:53:15.829 --> 00:53:15.839 align:start position:0% coming 00:53:15.839 --> 00:53:18.109 align:start position:0% coming um<00:53:15.960> there's<00:53:16.200> more<00:53:16.859> places<00:53:17.160> we<00:53:17.640> can<00:53:17.819> discuss 00:53:18.109 --> 00:53:18.119 align:start position:0% um there's more places we can discuss 00:53:18.119 --> 00:53:20.089 align:start position:0% um there's more places we can discuss all<00:53:18.359> this<00:53:18.540> this<00:53:18.780> week<00:53:18.960> so<00:53:19.319> we<00:53:19.740> mentioned 00:53:20.089 --> 00:53:20.099 align:start position:0% all this this week so we mentioned 00:53:20.099 --> 00:53:22.670 align:start position:0% all this this week so we mentioned there's<00:53:20.339> an<00:53:20.579> evm<00:53:21.059> panel<00:53:21.599> where<00:53:22.079> we<00:53:22.380> can<00:53:22.440> get 00:53:22.670 --> 00:53:22.680 align:start position:0% there's an evm panel where we can get 00:53:22.680 --> 00:53:25.490 align:start position:0% there's an evm panel where we can get into<00:53:22.859> eof<00:53:23.720> 1153<00:53:24.720> all<00:53:25.020> that<00:53:25.140> good<00:53:25.319> stuff 00:53:25.490 --> 00:53:25.500 align:start position:0% into eof 1153 all that good stuff 00:53:25.500 --> 00:53:28.490 align:start position:0% into eof 1153 all that good stuff there's<00:53:26.040> an<00:53:26.280> account<00:53:26.460> abstraction<00:53:27.000> panel<00:53:27.660> uh 00:53:28.490 --> 00:53:28.500 align:start position:0% there's an account abstraction panel uh 00:53:28.500 --> 00:53:30.410 align:start position:0% there's an account abstraction panel uh and<00:53:28.859> we<00:53:29.099> just<00:53:29.220> had<00:53:29.460> some<00:53:29.700> new<00:53:29.880> fresh<00:53:30.119> account 00:53:30.410 --> 00:53:30.420 align:start position:0% and we just had some new fresh account 00:53:30.420 --> 00:53:32.390 align:start position:0% and we just had some new fresh account abstraction<00:53:31.020> content<00:53:31.440> as<00:53:31.619> well<00:53:31.800> and<00:53:32.280> then 00:53:32.390 --> 00:53:32.400 align:start position:0% abstraction content as well and then 00:53:32.400 --> 00:53:35.870 align:start position:0% abstraction content as well and then finally<00:53:32.700> there's<00:53:33.000> an<00:53:33.359> ERC<00:53:34.220> uh<00:53:35.220> kind<00:53:35.460> of<00:53:35.579> Youth 00:53:35.870 --> 00:53:35.880 align:start position:0% finally there's an ERC uh kind of Youth 00:53:35.880 --> 00:53:37.670 align:start position:0% finally there's an ERC uh kind of Youth magician<00:53:36.300> session<00:53:36.540> as<00:53:36.780> well 00:53:37.670 --> 00:53:37.680 align:start position:0% magician session as well 00:53:37.680 --> 00:53:38.809 align:start position:0% magician session as well um<00:53:37.740> throughout<00:53:38.040> the<00:53:38.160> week<00:53:38.280> I<00:53:38.520> don't<00:53:38.640> know<00:53:38.700> when 00:53:38.809 --> 00:53:38.819 align:start position:0% um throughout the week I don't know when 00:53:38.819 --> 00:53:40.609 align:start position:0% um throughout the week I don't know when they<00:53:38.940> are<00:53:39.059> sorry<00:53:39.240> they're<00:53:39.480> all<00:53:39.599> on<00:53:39.720> the<00:53:39.900> agenda 00:53:40.609 --> 00:53:40.619 align:start position:0% they are sorry they're all on the agenda 00:53:40.619 --> 00:53:45.349 align:start position:0% they are sorry they're all on the agenda is<00:53:41.280> on<00:53:41.640> Friday<00:53:41.940> at<00:53:42.540> Workshop<00:53:43.079> room<00:53:43.260> 4<00:53:43.619> at<00:53:43.859> 1<00:53:44.160> pm 00:53:45.349 --> 00:53:45.359 align:start position:0% is on Friday at Workshop room 4 at 1 pm 00:53:45.359 --> 00:53:46.790 align:start position:0% is on Friday at Workshop room 4 at 1 pm you<00:53:45.780> heard<00:53:45.900> it 00:53:46.790 --> 00:53:46.800 align:start position:0% you heard it 00:53:46.800 --> 00:53:49.490 align:start position:0% you heard it um oh<00:53:47.099> product<00:53:47.520> right<00:53:48.000> so<00:53:48.720> Friday<00:53:49.020> there's<00:53:49.380> a 00:53:49.490 --> 00:53:49.500 align:start position:0% um oh product right so Friday there's a 00:53:49.500 --> 00:53:50.870 align:start position:0% um oh product right so Friday there's a session<00:53:49.740> about<00:53:49.980> tank<00:53:50.220> shorting<00:53:50.760> and 00:53:50.870 --> 00:53:50.880 align:start position:0% session about tank shorting and 00:53:50.880 --> 00:53:52.730 align:start position:0% session about tank shorting and prototank<00:53:51.300> shorting<00:53:51.780> if<00:53:52.319> you're<00:53:52.440> interested 00:53:52.730 --> 00:53:52.740 align:start position:0% prototank shorting if you're interested 00:53:52.740 --> 00:53:54.829 align:start position:0% prototank shorting if you're interested to<00:53:52.859> the<00:53:52.980> helpers<00:53:53.280> of<00:53:53.520> the<00:53:53.640> Erp<00:53:54.000> for<00:53:54.240> Edge<00:53:54.480> refer 00:53:54.829 --> 00:53:54.839 align:start position:0% to the helpers of the Erp for Edge refer 00:53:54.839 --> 00:53:57.049 align:start position:0% to the helpers of the Erp for Edge refer just<00:53:55.380> please<00:53:55.619> contact<00:53:55.980> us<00:53:56.280> and<00:53:56.700> we<00:53:56.880> are 00:53:57.049 --> 00:53:57.059 align:start position:0% just please contact us and we are 00:53:57.059 --> 00:53:59.510 align:start position:0% just please contact us and we are hosting<00:53:57.420> co-work<00:53:57.839> sessions 00:53:59.510 --> 00:53:59.520 align:start position:0% hosting co-work sessions 00:53:59.520 --> 00:54:00.890 align:start position:0% hosting co-work sessions yeah cool<00:53:59.940> yeah<00:54:00.240> thank<00:54:00.540> you<00:54:00.660> so<00:54:00.780> much 00:54:00.890 --> 00:54:00.900 align:start position:0% yeah cool yeah thank you so much 00:54:00.900 --> 00:54:01.930 align:start position:0% yeah cool yeah thank you so much everyone<00:54:01.140> for<00:54:01.500> coming 00:54:01.930 --> 00:54:01.940 align:start position:0% everyone for coming 00:54:01.940 --> 00:54:08.039 align:start position:0% everyone for coming [Applause]