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:16.390 align:start position:0% [Music] 00:00:16.390 --> 00:00:16.400 align:start position:0% 00:00:16.400 --> 00:00:19.310 align:start position:0% execution<00:00:17.400> layer<00:00:17.820> specifications<00:00:18.420> and<00:00:19.140> we're 00:00:19.310 --> 00:00:19.320 align:start position:0% execution layer specifications and we're 00:00:19.320 --> 00:00:21.170 align:start position:0% execution layer specifications and we're working<00:00:19.500> on<00:00:19.740> the<00:00:19.920> future<00:00:20.100> of<00:00:20.580> how<00:00:20.880> do<00:00:21.060> you 00:00:21.170 --> 00:00:21.180 align:start position:0% working on the future of how do you 00:00:21.180 --> 00:00:22.609 align:start position:0% working on the future of how do you specify<00:00:21.539> the<00:00:21.660> execution<00:00:22.020> there<00:00:22.199> so<00:00:22.380> we've 00:00:22.609 --> 00:00:22.619 align:start position:0% specify the execution there so we've 00:00:22.619 --> 00:00:24.410 align:start position:0% specify the execution there so we've just<00:00:22.740> heard<00:00:22.980> about<00:00:23.160> how<00:00:23.460> the<00:00:23.640> consensus<00:00:24.060> layer 00:00:24.410 --> 00:00:24.420 align:start position:0% just heard about how the consensus layer 00:00:24.420 --> 00:00:27.529 align:start position:0% just heard about how the consensus layer do<00:00:24.660> their<00:00:25.619> specifications<00:00:26.279> in<00:00:26.580> Python 00:00:27.529 --> 00:00:27.539 align:start position:0% do their specifications in Python 00:00:27.539 --> 00:00:29.029 align:start position:0% do their specifications in Python if<00:00:27.960> you<00:00:28.019> think<00:00:28.199> what<00:00:28.320> I'm<00:00:28.500> talking<00:00:28.680> about<00:00:28.859> is 00:00:29.029 --> 00:00:29.039 align:start position:0% if you think what I'm talking about is 00:00:29.039 --> 00:00:30.170 align:start position:0% if you think what I'm talking about is similar<00:00:29.340> it's<00:00:29.519> because<00:00:29.640> that's<00:00:29.820> where<00:00:29.939> we<00:00:30.060> got 00:00:30.170 --> 00:00:30.180 align:start position:0% similar it's because that's where we got 00:00:30.180 --> 00:00:32.870 align:start position:0% similar it's because that's where we got the<00:00:30.300> idea<00:00:30.539> from<00:00:30.800> before<00:00:31.800> I<00:00:32.099> begin<00:00:32.279> I<00:00:32.700> want<00:00:32.820> to 00:00:32.870 --> 00:00:32.880 align:start position:0% the idea from before I begin I want to 00:00:32.880 --> 00:00:34.010 align:start position:0% the idea from before I begin I want to talk<00:00:33.000> about<00:00:33.059> what<00:00:33.239> I<00:00:33.360> mean<00:00:33.480> by<00:00:33.600> the<00:00:33.719> execution 00:00:34.010 --> 00:00:34.020 align:start position:0% talk about what I mean by the execution 00:00:34.020 --> 00:00:36.470 align:start position:0% talk about what I mean by the execution layer<00:00:34.800> we're<00:00:35.340> only<00:00:35.520> here<00:00:35.700> interested<00:00:36.180> in<00:00:36.239> the 00:00:36.470 --> 00:00:36.480 align:start position:0% layer we're only here interested in the 00:00:36.480 --> 00:00:38.630 align:start position:0% layer we're only here interested in the state's<00:00:36.780> transition<00:00:37.079> function<00:00:37.500> so<00:00:38.399> you<00:00:38.520> have 00:00:38.630 --> 00:00:38.640 align:start position:0% state's transition function so you have 00:00:38.640 --> 00:00:39.889 align:start position:0% state's transition function so you have like<00:00:38.760> a<00:00:38.880> long<00:00:39.000> chain<00:00:39.180> of<00:00:39.360> blocks<00:00:39.600> you<00:00:39.780> have 00:00:39.889 --> 00:00:39.899 align:start position:0% like a long chain of blocks you have 00:00:39.899 --> 00:00:43.010 align:start position:0% like a long chain of blocks you have some<00:00:40.079> State<00:00:40.320> you<00:00:41.040> add<00:00:41.219> in<00:00:41.399> some<00:00:41.640> new<00:00:41.760> state<00:00:42.020> and 00:00:43.010 --> 00:00:43.020 align:start position:0% some State you add in some new state and 00:00:43.020 --> 00:00:44.389 align:start position:0% some State you add in some new state and the<00:00:43.140> question<00:00:43.320> is<00:00:43.500> firstly<00:00:43.920> is<00:00:44.100> that<00:00:44.280> block 00:00:44.389 --> 00:00:44.399 align:start position:0% the question is firstly is that block 00:00:44.399 --> 00:00:46.910 align:start position:0% the question is firstly is that block valid<00:00:44.879> are<00:00:45.300> you<00:00:45.480> allowed<00:00:45.960> to<00:00:46.440> add<00:00:46.559> it<00:00:46.680> to<00:00:46.800> the 00:00:46.910 --> 00:00:46.920 align:start position:0% valid are you allowed to add it to the 00:00:46.920 --> 00:00:49.910 align:start position:0% valid are you allowed to add it to the state<00:00:47.120> and<00:00:48.120> secondly<00:00:48.480> what<00:00:49.320> is<00:00:49.440> the<00:00:49.559> new<00:00:49.680> state 00:00:49.910 --> 00:00:49.920 align:start position:0% state and secondly what is the new state 00:00:49.920 --> 00:00:52.010 align:start position:0% state and secondly what is the new state afterwards<00:00:50.460> we<00:00:51.239> don't<00:00:51.360> care<00:00:51.539> about<00:00:51.719> anything 00:00:52.010 --> 00:00:52.020 align:start position:0% afterwards we don't care about anything 00:00:52.020 --> 00:00:54.410 align:start position:0% afterwards we don't care about anything else<00:00:52.379> we<00:00:53.039> don't<00:00:53.100> care<00:00:53.280> about<00:00:53.399> networking<00:00:54.000> we 00:00:54.410 --> 00:00:54.420 align:start position:0% else we don't care about networking we 00:00:54.420 --> 00:00:56.689 align:start position:0% else we don't care about networking we don't<00:00:54.600> care<00:00:54.719> how<00:00:54.899> we<00:00:55.020> input<00:00:55.320> reorgs<00:00:55.980> we<00:00:56.579> only 00:00:56.689 --> 00:00:56.699 align:start position:0% don't care how we input reorgs we only 00:00:56.699 --> 00:00:58.189 align:start position:0% don't care how we input reorgs we only care<00:00:56.940> about<00:00:57.059> what<00:00:57.360> is<00:00:57.480> the<00:00:57.660> state<00:00:57.840> transition 00:00:58.189 --> 00:00:58.199 align:start position:0% care about what is the state transition 00:00:58.199 --> 00:00:59.630 align:start position:0% care about what is the state transition function 00:00:59.630 --> 00:00:59.640 align:start position:0% function 00:00:59.640 --> 00:01:01.970 align:start position:0% function So<00:01:00.420> currently<00:01:00.780> let's<00:01:00.960> suppose<00:01:01.379> you're<00:01:01.559> like 00:01:01.970 --> 00:01:01.980 align:start position:0% So currently let's suppose you're like 00:01:01.980 --> 00:01:04.189 align:start position:0% So currently let's suppose you're like someone<00:01:02.219> you<00:01:02.579> want<00:01:02.820> to<00:01:02.940> know<00:01:03.059> about<00:01:03.359> the<00:01:04.080> state 00:01:04.189 --> 00:01:04.199 align:start position:0% someone you want to know about the state 00:01:04.199 --> 00:01:05.870 align:start position:0% someone you want to know about the state transition<00:01:04.619> function<00:01:04.920> the<00:01:05.100> Executioner<00:01:05.640> how 00:01:05.870 --> 00:01:05.880 align:start position:0% transition function the Executioner how 00:01:05.880 --> 00:01:07.550 align:start position:0% transition function the Executioner how it<00:01:06.000> works<00:01:06.299> where<00:01:07.020> would<00:01:07.140> you<00:01:07.260> go<00:01:07.380> for 00:01:07.550 --> 00:01:07.560 align:start position:0% it works where would you go for 00:01:07.560 --> 00:01:09.530 align:start position:0% it works where would you go for information<00:01:07.820> well<00:01:08.820> the<00:01:09.000> first<00:01:09.119> place<00:01:09.299> you 00:01:09.530 --> 00:01:09.540 align:start position:0% information well the first place you 00:01:09.540 --> 00:01:11.330 align:start position:0% information well the first place you could<00:01:09.659> go<00:01:09.900> is<00:01:10.140> the<00:01:10.380> yellow<00:01:10.560> paper<00:01:10.799> where<00:01:11.159> I 00:01:11.330 --> 00:01:11.340 align:start position:0% could go is the yellow paper where I 00:01:11.340 --> 00:01:13.730 align:start position:0% could go is the yellow paper where I have<00:01:11.460> the<00:01:11.760> yellow<00:01:12.000> paper<00:01:12.360> here<00:01:13.080> this<00:01:13.380> is<00:01:13.500> a 00:01:13.730 --> 00:01:13.740 align:start position:0% have the yellow paper here this is a 00:01:13.740 --> 00:01:16.550 align:start position:0% have the yellow paper here this is a lovely<00:01:14.220> extract<00:01:14.700> that<00:01:15.000> explains<00:01:16.080> um<00:01:16.080> what<00:01:16.439> the 00:01:16.550 --> 00:01:16.560 align:start position:0% lovely extract that explains um what the 00:01:16.560 --> 00:01:19.730 align:start position:0% lovely extract that explains um what the hell<00:01:16.680> of<00:01:16.799> a<00:01:16.920> validity<00:01:17.220> conditions<00:01:17.700> are<00:01:18.060> and 00:01:19.730 --> 00:01:19.740 align:start position:0% hell of a validity conditions are and 00:01:19.740 --> 00:01:22.310 align:start position:0% hell of a validity conditions are and some<00:01:20.220> people<00:01:20.460> think<00:01:20.700> this<00:01:20.820> is<00:01:20.939> readable 00:01:22.310 --> 00:01:22.320 align:start position:0% some people think this is readable 00:01:22.320 --> 00:01:23.330 align:start position:0% some people think this is readable um 00:01:23.330 --> 00:01:23.340 align:start position:0% um 00:01:23.340 --> 00:01:25.429 align:start position:0% um they<00:01:23.880> are<00:01:24.000> in<00:01:24.119> the<00:01:24.240> minority<00:01:24.659> if<00:01:25.259> you're 00:01:25.429 --> 00:01:25.439 align:start position:0% they are in the minority if you're 00:01:25.439 --> 00:01:29.330 align:start position:0% they are in the minority if you're curious<00:01:25.799> about<00:01:26.100> the<00:01:26.460> like<00:01:26.840> weird<00:01:27.840> mountains 00:01:29.330 --> 00:01:29.340 align:start position:0% curious about the like weird mountains 00:01:29.340 --> 00:01:30.469 align:start position:0% curious about the like weird mountains um<00:01:29.400> they're<00:01:29.580> not<00:01:29.759> mountains<00:01:30.240> that's<00:01:30.360> how 00:01:30.469 --> 00:01:30.479 align:start position:0% um they're not mountains that's how 00:01:30.479 --> 00:01:32.749 align:start position:0% um they're not mountains that's how mathematicians<00:01:31.020> write<00:01:31.259> down 00:01:32.749 --> 00:01:32.759 align:start position:0% mathematicians write down 00:01:32.759 --> 00:01:34.190 align:start position:0% mathematicians write down um<00:01:32.880> the<00:01:33.060> other<00:01:33.240> problem<00:01:33.420> with<00:01:33.600> the<00:01:33.840> yellow 00:01:34.190 --> 00:01:34.200 align:start position:0% um the other problem with the yellow 00:01:34.200 --> 00:01:35.569 align:start position:0% um the other problem with the yellow paper<00:01:34.500> is<00:01:34.740> that<00:01:34.920> it's<00:01:35.040> actually<00:01:35.159> really<00:01:35.400> out 00:01:35.569 --> 00:01:35.579 align:start position:0% paper is that it's actually really out 00:01:35.579 --> 00:01:38.510 align:start position:0% paper is that it's actually really out of<00:01:35.759> date<00:01:36.479> um<00:01:36.540> this<00:01:36.780> is<00:01:36.900> the<00:01:37.079> Berlin<00:01:37.439> version 00:01:38.510 --> 00:01:38.520 align:start position:0% of date um this is the Berlin version 00:01:38.520 --> 00:01:40.010 align:start position:0% of date um this is the Berlin version the<00:01:38.820> reason<00:01:39.000> it's<00:01:39.180> the<00:01:39.299> Berlin<00:01:39.600> version<00:01:39.840> is 00:01:40.010 --> 00:01:40.020 align:start position:0% the reason it's the Berlin version is 00:01:40.020 --> 00:01:43.010 align:start position:0% the reason it's the Berlin version is because<00:01:40.140> no<00:01:40.320> one's<00:01:40.560> implemented<00:01:40.920> London<00:01:41.220> yet 00:01:43.010 --> 00:01:43.020 align:start position:0% because no one's implemented London yet 00:01:43.020 --> 00:01:45.530 align:start position:0% because no one's implemented London yet um<00:01:43.140> secondly<00:01:43.560> you<00:01:43.740> can<00:01:43.799> look<00:01:43.979> at<00:01:44.100> eips<00:01:44.579> eips 00:01:45.530 --> 00:01:45.540 align:start position:0% um secondly you can look at eips eips 00:01:45.540 --> 00:01:50.030 align:start position:0% um secondly you can look at eips eips are<00:01:46.140> individual<00:01:46.860> slices<00:01:47.700> of<00:01:48.659> like<00:01:49.500> changes 00:01:50.030 --> 00:01:50.040 align:start position:0% are individual slices of like changes 00:01:50.040 --> 00:01:51.889 align:start position:0% are individual slices of like changes they're<00:01:50.340> specific<00:01:50.820> change<00:01:51.119> proposals<00:01:51.840> and 00:01:51.889 --> 00:01:51.899 align:start position:0% they're specific change proposals and 00:01:51.899 --> 00:01:53.450 align:start position:0% they're specific change proposals and they're<00:01:52.079> like<00:01:52.259> you<00:01:52.920> can<00:01:53.040> look<00:01:53.159> at<00:01:53.280> them<00:01:53.340> and 00:01:53.450 --> 00:01:53.460 align:start position:0% they're like you can look at them and 00:01:53.460 --> 00:01:54.889 align:start position:0% they're like you can look at them and see<00:01:53.640> the<00:01:53.700> history<00:01:53.820> but<00:01:54.119> they're<00:01:54.360> they're<00:01:54.659> not 00:01:54.889 --> 00:01:54.899 align:start position:0% see the history but they're they're not 00:01:54.899 --> 00:01:55.969 align:start position:0% see the history but they're they're not you<00:01:55.079> don't<00:01:55.140> they<00:01:55.380> don't<00:01:55.500> tell<00:01:55.619> you<00:01:55.740> about<00:01:55.799> the 00:01:55.969 --> 00:01:55.979 align:start position:0% you don't they don't tell you about the 00:01:55.979 --> 00:01:57.310 align:start position:0% you don't they don't tell you about the relationship<00:01:56.340> they<00:01:56.520> only<00:01:56.640> tell<00:01:56.880> you<00:01:56.939> about 00:01:57.310 --> 00:01:57.320 align:start position:0% relationship they only tell you about 00:01:57.320 --> 00:02:00.109 align:start position:0% relationship they only tell you about individual<00:01:58.320> changes<00:01:58.740> in<00:01:58.920> isolation<00:01:59.340> so<00:01:59.939> if 00:02:00.109 --> 00:02:00.119 align:start position:0% individual changes in isolation so if 00:02:00.119 --> 00:02:02.450 align:start position:0% individual changes in isolation so if you<00:02:00.360> like<00:02:01.140> for<00:02:01.380> example<00:02:01.619> if<00:02:01.860> you<00:02:01.979> re<00:02:02.100> you<00:02:02.399> can 00:02:02.450 --> 00:02:02.460 align:start position:0% you like for example if you re you can 00:02:02.460 --> 00:02:03.649 align:start position:0% you like for example if you re you can read<00:02:02.579> heaps<00:02:02.939> where<00:02:03.060> it's<00:02:03.180> like<00:02:03.299> well<00:02:03.479> this 00:02:03.649 --> 00:02:03.659 align:start position:0% read heaps where it's like well this 00:02:03.659 --> 00:02:04.969 align:start position:0% read heaps where it's like well this thing<00:02:03.720> says<00:02:04.020> this<00:02:04.140> and<00:02:04.320> this<00:02:04.500> thing<00:02:04.619> says<00:02:04.860> this 00:02:04.969 --> 00:02:04.979 align:start position:0% thing says this and this thing says this 00:02:04.979 --> 00:02:06.950 align:start position:0% thing says this and this thing says this but<00:02:05.159> how<00:02:05.340> do<00:02:05.460> those<00:02:05.640> two<00:02:05.759> things<00:02:05.939> interact<00:02:06.420> and 00:02:06.950 --> 00:02:06.960 align:start position:0% but how do those two things interact and 00:02:06.960 --> 00:02:09.169 align:start position:0% but how do those two things interact and you<00:02:07.079> just<00:02:07.200> can't<00:02:07.380> get<00:02:07.560> that<00:02:07.619> from<00:02:07.799> the<00:02:07.860> IVs 00:02:09.169 --> 00:02:09.179 align:start position:0% you just can't get that from the IVs 00:02:09.179 --> 00:02:10.309 align:start position:0% you just can't get that from the IVs um at<00:02:09.360> that<00:02:09.479> point<00:02:09.660> you<00:02:09.840> can<00:02:09.959> then<00:02:10.020> go<00:02:10.140> again 00:02:10.309 --> 00:02:10.319 align:start position:0% um at that point you can then go again 00:02:10.319 --> 00:02:12.050 align:start position:0% um at that point you can then go again when<00:02:10.560> I<00:02:10.619> look<00:02:10.679> at<00:02:10.800> the<00:02:10.920> test<00:02:11.039> suite<00:02:11.400> and<00:02:11.879> the 00:02:12.050 --> 00:02:12.060 align:start position:0% when I look at the test suite and the 00:02:12.060 --> 00:02:14.570 align:start position:0% when I look at the test suite and the test<00:02:12.239> Suite<00:02:12.540> is<00:02:12.660> great<00:02:12.840> it<00:02:13.260> is<00:02:13.379> full<00:02:13.560> of<00:02:13.800> loads 00:02:14.570 --> 00:02:14.580 align:start position:0% test Suite is great it is full of loads 00:02:14.580 --> 00:02:16.490 align:start position:0% test Suite is great it is full of loads and<00:02:14.700> loads<00:02:14.940> of<00:02:15.060> tests<00:02:15.360> but<00:02:15.720> ultimately<00:02:16.080> it's 00:02:16.490 --> 00:02:16.500 align:start position:0% and loads of tests but ultimately it's 00:02:16.500 --> 00:02:17.990 align:start position:0% and loads of tests but ultimately it's just<00:02:16.739> a<00:02:16.920> pile<00:02:17.160> of<00:02:17.340> tests<00:02:17.640> it's<00:02:17.819> not 00:02:17.990 --> 00:02:18.000 align:start position:0% just a pile of tests it's not 00:02:18.000 --> 00:02:20.150 align:start position:0% just a pile of tests it's not particularly<00:02:18.300> well<00:02:18.420> organized<00:02:19.020> and<00:02:19.920> if<00:02:20.040> you 00:02:20.150 --> 00:02:20.160 align:start position:0% particularly well organized and if you 00:02:20.160 --> 00:02:21.710 align:start position:0% particularly well organized and if you want<00:02:20.340> to<00:02:20.459> find<00:02:20.580> some<00:02:20.819> Behavior<00:02:21.300> like<00:02:21.540> maybe 00:02:21.710 --> 00:02:21.720 align:start position:0% want to find some Behavior like maybe 00:02:21.720 --> 00:02:23.330 align:start position:0% want to find some Behavior like maybe you<00:02:22.020> can<00:02:22.140> find<00:02:22.319> somewhere<00:02:22.680> in<00:02:22.860> the<00:02:22.920> test<00:02:23.040> Suite 00:02:23.330 --> 00:02:23.340 align:start position:0% you can find somewhere in the test Suite 00:02:23.340 --> 00:02:24.650 align:start position:0% you can find somewhere in the test Suite where<00:02:23.459> that<00:02:23.640> behavior<00:02:23.940> is<00:02:24.060> tested<00:02:24.360> but<00:02:24.540> it's 00:02:24.650 --> 00:02:24.660 align:start position:0% where that behavior is tested but it's 00:02:24.660 --> 00:02:27.290 align:start position:0% where that behavior is tested but it's not<00:02:24.920> specifying<00:02:25.920> anything 00:02:27.290 --> 00:02:27.300 align:start position:0% not specifying anything 00:02:27.300 --> 00:02:28.670 align:start position:0% not specifying anything and<00:02:27.660> then<00:02:27.840> you<00:02:27.959> can<00:02:28.080> just<00:02:28.200> give<00:02:28.260> up<00:02:28.440> and<00:02:28.560> look 00:02:28.670 --> 00:02:28.680 align:start position:0% and then you can just give up and look 00:02:28.680 --> 00:02:30.890 align:start position:0% and then you can just give up and look at<00:02:28.800> the<00:02:28.800> gas<00:02:28.980> source<00:02:29.340> code 00:02:30.890 --> 00:02:30.900 align:start position:0% at the gas source code 00:02:30.900 --> 00:02:32.990 align:start position:0% at the gas source code um<00:02:31.020> I<00:02:31.260> fundamentally<00:02:31.860> if<00:02:32.040> you've<00:02:32.220> like<00:02:32.459> got<00:02:32.819> to 00:02:32.990 --> 00:02:33.000 align:start position:0% um I fundamentally if you've like got to 00:02:33.000 --> 00:02:34.250 align:start position:0% um I fundamentally if you've like got to the<00:02:33.180> point<00:02:33.360> where<00:02:33.720> you're<00:02:33.840> reading<00:02:34.200> the 00:02:34.250 --> 00:02:34.260 align:start position:0% the point where you're reading the 00:02:34.260 --> 00:02:35.809 align:start position:0% the point where you're reading the having<00:02:34.500> to<00:02:34.680> read<00:02:34.800> the<00:02:34.980> client<00:02:35.099> source<00:02:35.520> code<00:02:35.640> to 00:02:35.809 --> 00:02:35.819 align:start position:0% having to read the client source code to 00:02:35.819 --> 00:02:37.250 align:start position:0% having to read the client source code to work<00:02:35.940> out<00:02:36.060> how<00:02:36.239> the<00:02:36.300> execution<00:02:36.599> layer<00:02:36.959> works 00:02:37.250 --> 00:02:37.260 align:start position:0% work out how the execution layer works 00:02:37.260 --> 00:02:39.350 align:start position:0% work out how the execution layer works we<00:02:37.379> have<00:02:37.560> failed<00:02:37.860> at<00:02:37.980> specifying<00:02:38.520> it<00:02:38.640> these 00:02:39.350 --> 00:02:39.360 align:start position:0% we have failed at specifying it these 00:02:39.360 --> 00:02:41.809 align:start position:0% we have failed at specifying it these clients<00:02:39.780> they<00:02:40.020> are<00:02:40.200> big<00:02:40.440> like<00:02:41.220> complicated 00:02:41.809 --> 00:02:41.819 align:start position:0% clients they are big like complicated 00:02:41.819 --> 00:02:45.830 align:start position:0% clients they are big like complicated high<00:02:42.599> performance<00:02:43.519> pieces<00:02:44.519> of<00:02:44.640> code<00:02:44.940> they're 00:02:45.830 --> 00:02:45.840 align:start position:0% high performance pieces of code they're 00:02:45.840 --> 00:02:48.290 align:start position:0% high performance pieces of code they're not<00:02:46.140> like<00:02:46.560> designed<00:02:46.980> for<00:02:47.099> the<00:02:47.280> reader 00:02:48.290 --> 00:02:48.300 align:start position:0% not like designed for the reader 00:02:48.300 --> 00:02:49.790 align:start position:0% not like designed for the reader the<00:02:48.599> other<00:02:48.720> thing<00:02:48.900> about<00:02:49.019> specifications<00:02:49.620> is 00:02:49.790 --> 00:02:49.800 align:start position:0% the other thing about specifications is 00:02:49.800 --> 00:02:51.229 align:start position:0% the other thing about specifications is they<00:02:49.980> need<00:02:50.160> to<00:02:50.220> be<00:02:50.340> passed<00:02:50.580> the<00:02:50.700> standards 00:02:51.229 --> 00:02:51.239 align:start position:0% they need to be passed the standards 00:02:51.239 --> 00:02:53.449 align:start position:0% they need to be passed the standards process<00:02:51.540> you<00:02:52.379> can't<00:02:52.560> just<00:02:52.739> like<00:02:52.920> fail<00:02:53.160> we're 00:02:53.449 --> 00:02:53.459 align:start position:0% process you can't just like fail we're 00:02:53.459 --> 00:02:54.530 align:start position:0% process you can't just like fail we're going<00:02:53.580> to<00:02:53.640> implement<00:02:53.940> all<00:02:54.120> this<00:02:54.300> stuff<00:02:54.420> and 00:02:54.530 --> 00:02:54.540 align:start position:0% going to implement all this stuff and 00:02:54.540 --> 00:02:55.250 align:start position:0% going to implement all this stuff and then<00:02:54.599> we're<00:02:54.720> going<00:02:54.840> to<00:02:54.840> update<00:02:55.140> the 00:02:55.250 --> 00:02:55.260 align:start position:0% then we're going to update the 00:02:55.260 --> 00:02:56.930 align:start position:0% then we're going to update the specifications<00:02:55.680> later<00:02:55.980> this<00:02:56.580> is<00:02:56.640> the<00:02:56.819> big 00:02:56.930 --> 00:02:56.940 align:start position:0% specifications later this is the big 00:02:56.940 --> 00:02:59.869 align:start position:0% specifications later this is the big problem<00:02:57.319> with<00:02:58.319> the<00:02:58.739> yellow<00:02:58.920> paper<00:02:59.160> is<00:02:59.700> that 00:02:59.869 --> 00:02:59.879 align:start position:0% problem with the yellow paper is that 00:02:59.879 --> 00:03:01.790 align:start position:0% problem with the yellow paper is that it's<00:03:00.060> not<00:03:00.239> part<00:03:00.420> of<00:03:00.599> it<00:03:00.720> no<00:03:00.900> one<00:03:01.080> like<00:03:01.260> proposes 00:03:01.790 --> 00:03:01.800 align:start position:0% it's not part of it no one like proposes 00:03:01.800 --> 00:03:03.470 align:start position:0% it's not part of it no one like proposes A<00:03:01.980> Change<00:03:02.160> by<00:03:02.459> saying<00:03:02.700> this<00:03:02.879> is<00:03:03.060> how<00:03:03.239> I<00:03:03.360> would 00:03:03.470 --> 00:03:03.480 align:start position:0% A Change by saying this is how I would 00:03:03.480 --> 00:03:04.910 align:start position:0% A Change by saying this is how I would change<00:03:03.660> the<00:03:03.900> yellow<00:03:04.019> paper 00:03:04.910 --> 00:03:04.920 align:start position:0% change the yellow paper 00:03:04.920 --> 00:03:06.770 align:start position:0% change the yellow paper so<00:03:05.400> the<00:03:05.580> yellow<00:03:05.700> paper<00:03:06.000> just<00:03:06.239> gets<00:03:06.480> updated 00:03:06.770 --> 00:03:06.780 align:start position:0% so the yellow paper just gets updated 00:03:06.780 --> 00:03:09.910 align:start position:0% so the yellow paper just gets updated later<00:03:07.560> on<00:03:07.800> as<00:03:08.400> an<00:03:08.580> after<00:03:08.760> foot 00:03:09.910 --> 00:03:09.920 align:start position:0% later on as an after foot 00:03:09.920 --> 00:03:12.530 align:start position:0% later on as an after foot the<00:03:10.920> other<00:03:11.040> problem<00:03:11.280> is<00:03:12.060> that<00:03:12.239> the<00:03:12.420> other 00:03:12.530 --> 00:03:12.540 align:start position:0% the other problem is that the other 00:03:12.540 --> 00:03:14.270 align:start position:0% the other problem is that the other paper<00:03:12.720> is<00:03:13.019> just<00:03:13.200> like<00:03:13.500> a<00:03:13.620> documentation<00:03:14.159> it's 00:03:14.270 --> 00:03:14.280 align:start position:0% paper is just like a documentation it's 00:03:14.280 --> 00:03:16.369 align:start position:0% paper is just like a documentation it's not<00:03:14.400> executable<00:03:15.120> you<00:03:15.420> can't<00:03:15.540> test<00:03:15.840> whether<00:03:16.080> it 00:03:16.369 --> 00:03:16.379 align:start position:0% not executable you can't test whether it 00:03:16.379 --> 00:03:17.330 align:start position:0% not executable you can't test whether it works 00:03:17.330 --> 00:03:17.340 align:start position:0% works 00:03:17.340 --> 00:03:18.890 align:start position:0% works um<00:03:17.400> at<00:03:17.580> least<00:03:17.700> close<00:03:17.879> to<00:03:18.060> eops<00:03:18.540> as<00:03:18.599> well<00:03:18.720> so 00:03:18.890 --> 00:03:18.900 align:start position:0% um at least close to eops as well so 00:03:18.900 --> 00:03:22.850 align:start position:0% um at least close to eops as well so this<00:03:19.739> here<00:03:19.920> is<00:03:20.580> a<00:03:20.940> sample<00:03:21.300> from<00:03:21.900> the<00:03:22.080> EIP<00:03:22.379> that 00:03:22.850 --> 00:03:22.860 align:start position:0% this here is a sample from the EIP that 00:03:22.860 --> 00:03:25.809 align:start position:0% this here is a sample from the EIP that changes<00:03:23.340> how<00:03:23.819> the<00:03:24.300> cost<00:03:24.540> of<00:03:24.959> the<00:03:25.200> mod<00:03:25.440> x 00:03:25.809 --> 00:03:25.819 align:start position:0% changes how the cost of the mod x 00:03:25.819 --> 00:03:28.910 align:start position:0% changes how the cost of the mod x pre-compile<00:03:26.819> works<00:03:27.780> it<00:03:28.140> was<00:03:28.260> proposed<00:03:28.680> it<00:03:28.800> was 00:03:28.910 --> 00:03:28.920 align:start position:0% pre-compile works it was proposed it was 00:03:28.920 --> 00:03:30.410 align:start position:0% pre-compile works it was proposed it was accepted<00:03:29.340> and<00:03:29.640> you're<00:03:29.819> like<00:03:29.940> this<00:03:30.120> is<00:03:30.239> nice 00:03:30.410 --> 00:03:30.420 align:start position:0% accepted and you're like this is nice 00:03:30.420 --> 00:03:32.210 align:start position:0% accepted and you're like this is nice there's<00:03:30.659> a<00:03:30.840> nice<00:03:30.959> piece<00:03:31.200> of<00:03:31.319> easily<00:03:31.739> readable 00:03:32.210 --> 00:03:32.220 align:start position:0% there's a nice piece of easily readable 00:03:32.220 --> 00:03:35.030 align:start position:0% there's a nice piece of easily readable python<00:03:32.700> that<00:03:32.940> says<00:03:33.180> exactly<00:03:33.480> what<00:03:33.599> it<00:03:33.720> does 00:03:35.030 --> 00:03:35.040 align:start position:0% python that says exactly what it does 00:03:35.040 --> 00:03:37.190 align:start position:0% python that says exactly what it does problem<00:03:35.459> this<00:03:35.700> is<00:03:35.760> this<00:03:35.940> python<00:03:36.300> is<00:03:36.420> wrong 00:03:37.190 --> 00:03:37.200 align:start position:0% problem this is this python is wrong 00:03:37.200 --> 00:03:40.070 align:start position:0% problem this is this python is wrong now<00:03:37.680> no<00:03:37.860> one<00:03:37.980> has<00:03:38.099> ever<00:03:38.280> executed<00:03:38.760> this<00:03:38.879> python 00:03:40.070 --> 00:03:40.080 align:start position:0% now no one has ever executed this python 00:03:40.080 --> 00:03:41.390 align:start position:0% now no one has ever executed this python because<00:03:40.379> if<00:03:40.560> they<00:03:40.739> had<00:03:40.920> they<00:03:41.159> would<00:03:41.220> discover 00:03:41.390 --> 00:03:41.400 align:start position:0% because if they had they would discover 00:03:41.400 --> 00:03:44.330 align:start position:0% because if they had they would discover that<00:03:41.640> it<00:03:41.819> doesn't<00:03:41.879> really<00:03:42.000> make<00:03:42.239> any<00:03:42.360> sense 00:03:44.330 --> 00:03:44.340 align:start position:0% that it doesn't really make any sense 00:03:44.340 --> 00:03:46.850 align:start position:0% that it doesn't really make any sense um<00:03:44.459> and<00:03:45.060> I<00:03:45.360> mean<00:03:45.540> as<00:03:45.659> Donald<00:03:45.900> crew<00:03:46.319> said<00:03:46.379> Beware 00:03:46.850 --> 00:03:46.860 align:start position:0% um and I mean as Donald crew said Beware 00:03:46.860 --> 00:03:48.530 align:start position:0% um and I mean as Donald crew said Beware bugs<00:03:47.159> in<00:03:47.280> the<00:03:47.400> above<00:03:47.640> code<00:03:47.819> I<00:03:48.120> have<00:03:48.299> only 00:03:48.530 --> 00:03:48.540 align:start position:0% bugs in the above code I have only 00:03:48.540 --> 00:03:50.030 align:start position:0% bugs in the above code I have only proved<00:03:49.019> it<00:03:49.140> correct 00:03:50.030 --> 00:03:50.040 align:start position:0% proved it correct 00:03:50.040 --> 00:03:51.890 align:start position:0% proved it correct I<00:03:50.280> haven't<00:03:50.459> executed<00:03:51.120> it 00:03:51.890 --> 00:03:51.900 align:start position:0% I haven't executed it 00:03:51.900 --> 00:03:54.530 align:start position:0% I haven't executed it so<00:03:52.140> you<00:03:52.379> need<00:03:52.440> a<00:03:52.620> this<00:03:52.860> is<00:03:53.040> our<00:03:53.159> approach 00:03:54.530 --> 00:03:54.540 align:start position:0% so you need a this is our approach 00:03:54.540 --> 00:03:56.869 align:start position:0% so you need a this is our approach um<00:03:54.599> we<00:03:54.959> want<00:03:55.200> to<00:03:55.379> start<00:03:55.739> with<00:03:56.220> like<00:03:56.400> a<00:03:56.640> code 00:03:56.869 --> 00:03:56.879 align:start position:0% um we want to start with like a code 00:03:56.879 --> 00:03:59.509 align:start position:0% um we want to start with like a code first<00:03:57.360> approach<00:03:57.900> to<00:03:58.019> specifications 00:03:59.509 --> 00:03:59.519 align:start position:0% first approach to specifications 00:03:59.519 --> 00:04:01.309 align:start position:0% first approach to specifications um<00:03:59.580> we<00:03:59.879> take<00:04:00.060> like<00:04:00.239> Python<00:04:00.900> and<00:04:01.080> we're<00:04:01.260> not 00:04:01.309 --> 00:04:01.319 align:start position:0% um we take like Python and we're not 00:04:01.319 --> 00:04:02.809 align:start position:0% um we take like Python and we're not just<00:04:01.440> writing<00:04:01.739> any<00:04:01.860> old<00:04:01.980> python<00:04:02.400> we're<00:04:02.580> like 00:04:02.809 --> 00:04:02.819 align:start position:0% just writing any old python we're like 00:04:02.819 --> 00:04:04.610 align:start position:0% just writing any old python we're like trying<00:04:03.299> to<00:04:03.480> create<00:04:03.659> the<00:04:03.840> python<00:04:04.200> that<00:04:04.379> if<00:04:04.500> you 00:04:04.610 --> 00:04:04.620 align:start position:0% trying to create the python that if you 00:04:04.620 --> 00:04:06.229 align:start position:0% trying to create the python that if you open<00:04:04.739> like<00:04:05.040> some<00:04:05.280> programming<00:04:05.760> book<00:04:05.940> and 00:04:06.229 --> 00:04:06.239 align:start position:0% open like some programming book and 00:04:06.239 --> 00:04:08.390 align:start position:0% open like some programming book and someone<00:04:06.420> had<00:04:06.659> an<00:04:06.840> example<00:04:07.200> algorithm 00:04:08.390 --> 00:04:08.400 align:start position:0% someone had an example algorithm 00:04:08.400 --> 00:04:10.670 align:start position:0% someone had an example algorithm that<00:04:08.940> python<00:04:09.420> so<00:04:09.480> we<00:04:09.599> don't<00:04:09.720> use<00:04:09.840> classes<00:04:10.379> it's 00:04:10.670 --> 00:04:10.680 align:start position:0% that python so we don't use classes it's 00:04:10.680 --> 00:04:13.670 align:start position:0% that python so we don't use classes it's just<00:04:10.920> methods<00:04:11.640> and<00:04:12.200> effectively<00:04:13.200> structs 00:04:13.670 --> 00:04:13.680 align:start position:0% just methods and effectively structs 00:04:13.680 --> 00:04:15.589 align:start position:0% just methods and effectively structs this<00:04:14.340> is<00:04:14.459> like<00:04:14.640> the<00:04:14.760> common<00:04:15.000> language<00:04:15.299> that 00:04:15.589 --> 00:04:15.599 align:start position:0% this is like the common language that 00:04:15.599 --> 00:04:17.750 align:start position:0% this is like the common language that all<00:04:15.840> programmers<00:04:16.260> speak<00:04:16.440> this 00:04:17.750 --> 00:04:17.760 align:start position:0% all programmers speak this 00:04:17.760 --> 00:04:19.129 align:start position:0% all programmers speak this um<00:04:17.820> you<00:04:18.120> know<00:04:18.239> anyone<00:04:18.540> who's<00:04:18.720> done<00:04:18.959> any 00:04:19.129 --> 00:04:19.139 align:start position:0% um you know anyone who's done any 00:04:19.139 --> 00:04:20.330 align:start position:0% um you know anyone who's done any programming<00:04:19.500> will<00:04:19.680> immediately<00:04:20.040> know<00:04:20.220> what 00:04:20.330 --> 00:04:20.340 align:start position:0% programming will immediately know what 00:04:20.340 --> 00:04:21.530 align:start position:0% programming will immediately know what this<00:04:20.459> is<00:04:20.579> you<00:04:20.820> don't<00:04:20.940> need<00:04:21.120> to<00:04:21.359> like 00:04:21.530 --> 00:04:21.540 align:start position:0% this is you don't need to like 00:04:21.540 --> 00:04:23.150 align:start position:0% this is you don't need to like understand<00:04:21.959> fewer<00:04:22.500> mathematics<00:04:22.740> like<00:04:22.919> you<00:04:23.040> do 00:04:23.150 --> 00:04:23.160 align:start position:0% understand fewer mathematics like you do 00:04:23.160 --> 00:04:24.409 align:start position:0% understand fewer mathematics like you do with<00:04:23.220> the<00:04:23.280> yellow<00:04:23.400> paper 00:04:24.409 --> 00:04:24.419 align:start position:0% with the yellow paper 00:04:24.419 --> 00:04:27.469 align:start position:0% with the yellow paper and<00:04:24.840> crucially<00:04:25.440> it<00:04:26.040> can<00:04:26.160> be<00:04:26.280> executed<00:04:26.759> we<00:04:27.300> can 00:04:27.469 --> 00:04:27.479 align:start position:0% and crucially it can be executed we can 00:04:27.479 --> 00:04:29.270 align:start position:0% and crucially it can be executed we can test<00:04:27.660> it<00:04:27.840> if<00:04:28.380> you<00:04:28.500> want<00:04:28.620> to<00:04:28.740> know<00:04:28.860> what<00:04:29.100> the 00:04:29.270 --> 00:04:29.280 align:start position:0% test it if you want to know what the 00:04:29.280 --> 00:04:31.969 align:start position:0% test it if you want to know what the python<00:04:29.880> python<00:04:30.720> does<00:04:30.900> you<00:04:31.259> can<00:04:31.380> run<00:04:31.500> it<00:04:31.680> if<00:04:31.860> you 00:04:31.969 --> 00:04:31.979 align:start position:0% python python does you can run it if you 00:04:31.979 --> 00:04:33.230 align:start position:0% python python does you can run it if you want<00:04:32.100> to<00:04:32.160> compare<00:04:32.460> it<00:04:32.580> to<00:04:32.699> a<00:04:32.820> client<00:04:33.000> you<00:04:33.120> can 00:04:33.230 --> 00:04:33.240 align:start position:0% want to compare it to a client you can 00:04:33.240 --> 00:04:34.670 align:start position:0% want to compare it to a client you can run<00:04:33.419> this<00:04:33.600> you<00:04:33.720> can<00:04:33.840> run<00:04:33.960> the<00:04:34.139> client<00:04:34.259> do<00:04:34.500> they 00:04:34.670 --> 00:04:34.680 align:start position:0% run this you can run the client do they 00:04:34.680 --> 00:04:35.930 align:start position:0% run this you can run the client do they do<00:04:34.800> the<00:04:34.919> same<00:04:35.100> thing 00:04:35.930 --> 00:04:35.940 align:start position:0% do the same thing 00:04:35.940 --> 00:04:37.969 align:start position:0% do the same thing we're<00:04:36.780> purely<00:04:37.259> here<00:04:37.500> interested<00:04:37.919> in 00:04:37.969 --> 00:04:37.979 align:start position:0% we're purely here interested in 00:04:37.979 --> 00:04:39.710 align:start position:0% we're purely here interested in readability<00:04:38.400> we<00:04:39.300> don't<00:04:39.419> care<00:04:39.540> about 00:04:39.710 --> 00:04:39.720 align:start position:0% readability we don't care about 00:04:39.720 --> 00:04:43.730 align:start position:0% readability we don't care about performance<00:04:40.699> it's<00:04:41.699> extremely<00:04:42.240> slow<00:04:42.560> it<00:04:43.560> can 00:04:43.730 --> 00:04:43.740 align:start position:0% performance it's extremely slow it can 00:04:43.740 --> 00:04:46.070 align:start position:0% performance it's extremely slow it can think<00:04:43.979> mainnet<00:04:44.580> I<00:04:45.419> think<00:04:45.540> it<00:04:45.660> takes<00:04:45.900> about 00:04:46.070 --> 00:04:46.080 align:start position:0% think mainnet I think it takes about 00:04:46.080 --> 00:04:47.990 align:start position:0% think mainnet I think it takes about probably<00:04:46.740> getting<00:04:47.040> about<00:04:47.340> six<00:04:47.580> to<00:04:47.759> nine 00:04:47.990 --> 00:04:48.000 align:start position:0% probably getting about six to nine 00:04:48.000 --> 00:04:49.430 align:start position:0% probably getting about six to nine months<00:04:48.300> if<00:04:48.479> you<00:04:48.600> want<00:04:48.720> to<00:04:48.780> start<00:04:48.960> from<00:04:49.139> Genesis 00:04:49.430 --> 00:04:49.440 align:start position:0% months if you want to start from Genesis 00:04:49.440 --> 00:04:51.110 align:start position:0% months if you want to start from Genesis and<00:04:49.620> get<00:04:49.740> to<00:04:49.860> the<00:04:49.919> head<00:04:50.040> of<00:04:50.160> the<00:04:50.280> chain 00:04:51.110 --> 00:04:51.120 align:start position:0% and get to the head of the chain 00:04:51.120 --> 00:04:53.150 align:start position:0% and get to the head of the chain it's<00:04:51.479> not<00:04:51.720> a<00:04:51.840> viable<00:04:52.139> client 00:04:53.150 --> 00:04:53.160 align:start position:0% it's not a viable client 00:04:53.160 --> 00:04:55.730 align:start position:0% it's not a viable client we<00:04:54.000> also<00:04:54.180> make<00:04:54.300> some<00:04:54.479> very<00:04:54.720> weird<00:04:55.139> like<00:04:55.500> design 00:04:55.730 --> 00:04:55.740 align:start position:0% we also make some very weird like design 00:04:55.740 --> 00:04:59.390 align:start position:0% we also make some very weird like design choices<00:04:56.479> we<00:04:57.479> look<00:04:57.900> at<00:04:58.080> hard<00:04:58.800> Forks<00:04:59.280> in 00:04:59.390 --> 00:04:59.400 align:start position:0% choices we look at hard Forks in 00:04:59.400 --> 00:05:01.430 align:start position:0% choices we look at hard Forks in isolation<00:04:59.820> so<00:05:00.060> if<00:05:00.240> you<00:05:00.419> have<00:05:00.600> various<00:05:01.080> if<00:05:01.259> you 00:05:01.430 --> 00:05:01.440 align:start position:0% isolation so if you have various if you 00:05:01.440 --> 00:05:04.550 align:start position:0% isolation so if you have various if you go<00:05:01.560> you'll<00:05:01.860> see<00:05:01.979> it's<00:05:02.220> ethereum<00:05:03.120> slash<00:05:03.960> uh 00:05:04.550 --> 00:05:04.560 align:start position:0% go you'll see it's ethereum slash uh 00:05:04.560 --> 00:05:07.070 align:start position:0% go you'll see it's ethereum slash uh theorem<00:05:05.400> slash<00:05:06.000> Frontier<00:05:06.479> and<00:05:06.780> slash 00:05:07.070 --> 00:05:07.080 align:start position:0% theorem slash Frontier and slash 00:05:07.080 --> 00:05:08.450 align:start position:0% theorem slash Frontier and slash Homestead<00:05:07.560> and<00:05:07.680> each<00:05:07.800> of<00:05:07.919> those<00:05:08.040> is<00:05:08.220> an 00:05:08.450 --> 00:05:08.460 align:start position:0% Homestead and each of those is an 00:05:08.460 --> 00:05:11.090 align:start position:0% Homestead and each of those is an independent<00:05:09.000> implementation<00:05:09.620> of<00:05:10.620> those<00:05:10.860> hard 00:05:11.090 --> 00:05:11.100 align:start position:0% independent implementation of those hard 00:05:11.100 --> 00:05:12.290 align:start position:0% independent implementation of those hard Forks 00:05:12.290 --> 00:05:12.300 align:start position:0% Forks 00:05:12.300 --> 00:05:14.390 align:start position:0% Forks so<00:05:12.840> this<00:05:13.080> is<00:05:13.259> like<00:05:13.440> terrible<00:05:13.860> for<00:05:14.100> like<00:05:14.220> code 00:05:14.390 --> 00:05:14.400 align:start position:0% so this is like terrible for like code 00:05:14.400 --> 00:05:16.010 align:start position:0% so this is like terrible for like code duplication<00:05:15.000> like<00:05:15.180> literally<00:05:15.479> every<00:05:15.720> time<00:05:15.900> we 00:05:16.010 --> 00:05:16.020 align:start position:0% duplication like literally every time we 00:05:16.020 --> 00:05:17.390 align:start position:0% duplication like literally every time we include<00:05:16.320> a<00:05:16.500> new<00:05:16.620> hard<00:05:16.740> Fork<00:05:17.040> there's<00:05:17.160> like 00:05:17.390 --> 00:05:17.400 align:start position:0% include a new hard Fork there's like 00:05:17.400 --> 00:05:20.150 align:start position:0% include a new hard Fork there's like this<00:05:17.580> massive<00:05:18.000> coffee<00:05:18.240> of<00:05:18.600> like<00:05:19.100> thousands<00:05:20.100> of 00:05:20.150 --> 00:05:20.160 align:start position:0% this massive coffee of like thousands of 00:05:20.160 --> 00:05:21.350 align:start position:0% this massive coffee of like thousands of lines<00:05:20.460> of<00:05:20.639> code 00:05:21.350 --> 00:05:21.360 align:start position:0% lines of code 00:05:21.360 --> 00:05:23.210 align:start position:0% lines of code uh<00:05:21.960> but<00:05:22.139> it's<00:05:22.259> great<00:05:22.440> if<00:05:22.620> you're<00:05:22.740> like<00:05:22.979> a 00:05:23.210 --> 00:05:23.220 align:start position:0% uh but it's great if you're like a 00:05:23.220 --> 00:05:25.249 align:start position:0% uh but it's great if you're like a reader<00:05:23.580> you<00:05:24.120> want<00:05:24.240> to<00:05:24.360> read<00:05:24.479> it 00:05:25.249 --> 00:05:25.259 align:start position:0% reader you want to read it 00:05:25.259 --> 00:05:28.430 align:start position:0% reader you want to read it you<00:05:25.740> know<00:05:25.860> you<00:05:26.100> can<00:05:26.220> see<00:05:26.460> like<00:05:27.000> how<00:05:27.440> Homestead 00:05:28.430 --> 00:05:28.440 align:start position:0% you know you can see like how Homestead 00:05:28.440 --> 00:05:30.050 align:start position:0% you know you can see like how Homestead works<00:05:28.740> completely<00:05:29.160> in<00:05:29.280> isolation<00:05:29.699> you<00:05:29.940> don't 00:05:30.050 --> 00:05:30.060 align:start position:0% works completely in isolation you don't 00:05:30.060 --> 00:05:31.189 align:start position:0% works completely in isolation you don't have<00:05:30.180> to<00:05:30.300> have<00:05:30.479> to<00:05:30.660> think<00:05:30.780> about<00:05:30.900> how<00:05:31.139> it 00:05:31.189 --> 00:05:31.199 align:start position:0% have to have to think about how it 00:05:31.199 --> 00:05:33.230 align:start position:0% have to have to think about how it relates<00:05:31.500> to<00:05:31.740> other<00:05:32.160> things<00:05:32.400> whereas<00:05:33.000> if<00:05:33.120> you 00:05:33.230 --> 00:05:33.240 align:start position:0% relates to other things whereas if you 00:05:33.240 --> 00:05:34.909 align:start position:0% relates to other things whereas if you read<00:05:33.419> a<00:05:33.600> real<00:05:33.660> client<00:05:33.960> it's<00:05:34.199> just<00:05:34.440> a<00:05:34.560> pie<00:05:34.680> of 00:05:34.909 --> 00:05:34.919 align:start position:0% read a real client it's just a pie of 00:05:34.919 --> 00:05:36.770 align:start position:0% read a real client it's just a pie of like<00:05:35.039> if<00:05:35.580> we're<00:05:35.759> later<00:05:36.000> than<00:05:36.240> spiritious 00:05:36.770 --> 00:05:36.780 align:start position:0% like if we're later than spiritious 00:05:36.780 --> 00:05:38.390 align:start position:0% like if we're later than spiritious Dragon<00:05:37.020> do<00:05:37.320> this<00:05:37.500> thing<00:05:37.620> otherwise<00:05:37.979> do<00:05:38.220> this 00:05:38.390 --> 00:05:38.400 align:start position:0% Dragon do this thing otherwise do this 00:05:38.400 --> 00:05:40.430 align:start position:0% Dragon do this thing otherwise do this thing<00:05:39.060> um<00:05:39.180> if<00:05:39.360> you<00:05:39.479> do<00:05:39.600> want<00:05:39.780> to<00:05:39.900> see<00:05:40.020> look<00:05:40.320> at 00:05:40.430 --> 00:05:40.440 align:start position:0% thing um if you do want to see look at 00:05:40.440 --> 00:05:41.689 align:start position:0% thing um if you do want to see look at the<00:05:40.560> comparison<00:05:40.919> so<00:05:41.100> we're<00:05:41.340> developing 00:05:41.689 --> 00:05:41.699 align:start position:0% the comparison so we're developing 00:05:41.699 --> 00:05:44.029 align:start position:0% the comparison so we're developing specialist<00:05:42.240> diff<00:05:42.600> tools<00:05:43.080> and<00:05:43.620> those<00:05:43.800> diff 00:05:44.029 --> 00:05:44.039 align:start position:0% specialist diff tools and those diff 00:05:44.039 --> 00:05:45.230 align:start position:0% specialist diff tools and those diff tools 00:05:45.230 --> 00:05:45.240 align:start position:0% tools 00:05:45.240 --> 00:05:46.790 align:start position:0% tools um<00:05:45.300> allow<00:05:45.600> you<00:05:45.660> to<00:05:45.780> compare<00:05:46.080> like<00:05:46.380> this<00:05:46.620> is 00:05:46.790 --> 00:05:46.800 align:start position:0% um allow you to compare like this is 00:05:46.800 --> 00:05:48.050 align:start position:0% um allow you to compare like this is exactly<00:05:47.100> what<00:05:47.280> happened<00:05:47.460> this<00:05:47.759> is<00:05:47.880> the 00:05:48.050 --> 00:05:48.060 align:start position:0% exactly what happened this is the 00:05:48.060 --> 00:05:50.749 align:start position:0% exactly what happened this is the specification<00:05:48.600> for<00:05:49.220> Frontier<00:05:50.220> this<00:05:50.460> is<00:05:50.580> the 00:05:50.749 --> 00:05:50.759 align:start position:0% specification for Frontier this is the 00:05:50.759 --> 00:05:52.430 align:start position:0% specification for Frontier this is the specification<00:05:51.360> for<00:05:51.660> Homestead<00:05:52.139> this<00:05:52.380> is 00:05:52.430 --> 00:05:52.440 align:start position:0% specification for Homestead this is 00:05:52.440 --> 00:05:55.550 align:start position:0% specification for Homestead this is what's<00:05:52.740> changed<00:05:53.280> exactly<00:05:54.180> line<00:05:54.660> by<00:05:54.900> line<00:05:55.139> in 00:05:55.550 --> 00:05:55.560 align:start position:0% what's changed exactly line by line in 00:05:55.560 --> 00:05:57.590 align:start position:0% what's changed exactly line by line in code<00:05:55.860> that<00:05:56.340> we<00:05:56.460> have<00:05:56.639> tested 00:05:57.590 --> 00:05:57.600 align:start position:0% code that we have tested 00:05:57.600 --> 00:05:59.029 align:start position:0% code that we have tested um<00:05:57.660> so<00:05:57.840> here's<00:05:58.080> a<00:05:58.139> sample 00:05:59.029 --> 00:05:59.039 align:start position:0% um so here's a sample 00:05:59.039 --> 00:06:01.670 align:start position:0% um so here's a sample this<00:05:59.520> is<00:05:59.639> the<00:05:59.820> S<00:05:59.940> load<00:06:00.300> opcode<00:06:00.720> to<00:06:01.380> give<00:06:01.500> you 00:06:01.670 --> 00:06:01.680 align:start position:0% this is the S load opcode to give you 00:06:01.680 --> 00:06:03.290 align:start position:0% this is the S load opcode to give you like<00:06:01.800> a<00:06:01.979> feel 00:06:03.290 --> 00:06:03.300 align:start position:0% like a feel 00:06:03.300 --> 00:06:04.550 align:start position:0% like a feel um<00:06:03.360> a<00:06:03.600> number<00:06:03.720> of<00:06:03.840> things<00:06:03.960> here<00:06:04.080> first<00:06:04.259> you<00:06:04.440> can 00:06:04.550 --> 00:06:04.560 align:start position:0% um a number of things here first you can 00:06:04.560 --> 00:06:05.990 align:start position:0% um a number of things here first you can immediately<00:06:04.800> see<00:06:04.979> we've<00:06:05.460> really<00:06:05.580> tried<00:06:05.940> to 00:06:05.990 --> 00:06:06.000 align:start position:0% immediately see we've really tried to 00:06:06.000 --> 00:06:08.090 align:start position:0% immediately see we've really tried to make<00:06:06.120> it<00:06:06.300> as<00:06:06.360> readable<00:06:06.780> as<00:06:06.900> possible<00:06:07.199> we've 00:06:08.090 --> 00:06:08.100 align:start position:0% make it as readable as possible we've 00:06:08.100 --> 00:06:09.529 align:start position:0% make it as readable as possible we've also<00:06:08.280> divided<00:06:08.639> that<00:06:08.820> up<00:06:08.940> into<00:06:09.120> these<00:06:09.360> like 00:06:09.529 --> 00:06:09.539 align:start position:0% also divided that up into these like 00:06:09.539 --> 00:06:10.909 align:start position:0% also divided that up into these like individual<00:06:09.960> sections<00:06:10.320> which<00:06:10.440> we've<00:06:10.680> given 00:06:10.909 --> 00:06:10.919 align:start position:0% individual sections which we've given 00:06:10.919 --> 00:06:12.170 align:start position:0% individual sections which we've given headers 00:06:12.170 --> 00:06:12.180 align:start position:0% headers 00:06:12.180 --> 00:06:13.730 align:start position:0% headers um<00:06:12.240> this<00:06:12.539> actually<00:06:12.720> like<00:06:13.020> matters<00:06:13.440> there<00:06:13.620> are 00:06:13.730 --> 00:06:13.740 align:start position:0% um this actually like matters there are 00:06:13.740 --> 00:06:15.469 align:start position:0% um this actually like matters there are a<00:06:13.860> number<00:06:13.979> of<00:06:14.100> quite<00:06:14.340> subtle<00:06:14.699> semantics<00:06:15.240> that 00:06:15.469 --> 00:06:15.479 align:start position:0% a number of quite subtle semantics that 00:06:15.479 --> 00:06:17.810 align:start position:0% a number of quite subtle semantics that the<00:06:15.660> evm<00:06:16.139> has<00:06:16.320> that<00:06:16.979> relates<00:06:17.220> from<00:06:17.460> the<00:06:17.639> fact 00:06:17.810 --> 00:06:17.820 align:start position:0% the evm has that relates from the fact 00:06:17.820 --> 00:06:19.270 align:start position:0% the evm has that relates from the fact that<00:06:18.060> gas 00:06:19.270 --> 00:06:19.280 align:start position:0% that gas 00:06:19.280 --> 00:06:21.230 align:start position:0% that gas calculations<00:06:20.280> are<00:06:20.580> done<00:06:20.759> before<00:06:20.940> any 00:06:21.230 --> 00:06:21.240 align:start position:0% calculations are done before any 00:06:21.240 --> 00:06:23.629 align:start position:0% calculations are done before any computation<00:06:21.720> is<00:06:21.900> done<00:06:22.080> and<00:06:22.979> you<00:06:23.220> can<00:06:23.280> get<00:06:23.460> very 00:06:23.629 --> 00:06:23.639 align:start position:0% computation is done and you can get very 00:06:23.639 --> 00:06:25.490 align:start position:0% computation is done and you can get very confused<00:06:24.120> about<00:06:24.300> some<00:06:24.600> of<00:06:24.720> the<00:06:24.780> subtleties<00:06:25.259> of 00:06:25.490 --> 00:06:25.500 align:start position:0% confused about some of the subtleties of 00:06:25.500 --> 00:06:27.110 align:start position:0% confused about some of the subtleties of particularly<00:06:25.919> the<00:06:26.100> cool<00:06:26.220> lock<00:06:26.460> codes<00:06:26.699> if<00:06:27.000> you 00:06:27.110 --> 00:06:27.120 align:start position:0% particularly the cool lock codes if you 00:06:27.120 --> 00:06:28.610 align:start position:0% particularly the cool lock codes if you don't<00:06:27.240> realize<00:06:27.600> this 00:06:28.610 --> 00:06:28.620 align:start position:0% don't realize this 00:06:28.620 --> 00:06:30.590 align:start position:0% don't realize this um<00:06:28.680> now<00:06:29.100> I<00:06:29.220> want<00:06:29.340> to<00:06:29.460> move<00:06:29.580> on<00:06:29.759> to<00:06:29.880> like<00:06:30.060> now<00:06:30.419> we 00:06:30.590 --> 00:06:30.600 align:start position:0% um now I want to move on to like now we 00:06:30.600 --> 00:06:32.270 align:start position:0% um now I want to move on to like now we have<00:06:30.780> these<00:06:31.020> things<00:06:31.139> how<00:06:31.500> can<00:06:31.680> that<00:06:31.860> like 00:06:32.270 --> 00:06:32.280 align:start position:0% have these things how can that like 00:06:32.280 --> 00:06:34.189 align:start position:0% have these things how can that like affect<00:06:32.940> the<00:06:33.060> development<00:06:33.479> process<00:06:33.780> how<00:06:34.080> does 00:06:34.189 --> 00:06:34.199 align:start position:0% affect the development process how does 00:06:34.199 --> 00:06:35.390 align:start position:0% affect the development process how does having<00:06:34.380> these<00:06:34.680> specifications<00:06:35.039> make 00:06:35.390 --> 00:06:35.400 align:start position:0% having these specifications make 00:06:35.400 --> 00:06:37.730 align:start position:0% having these specifications make improving<00:06:36.000> and<00:06:36.539> building<00:06:36.720> on<00:06:36.960> the<00:06:37.080> evm<00:06:37.440> better 00:06:37.730 --> 00:06:37.740 align:start position:0% improving and building on the evm better 00:06:37.740 --> 00:06:39.590 align:start position:0% improving and building on the evm better and<00:06:38.460> I<00:06:38.639> think<00:06:38.759> it's<00:06:38.880> helpful<00:06:39.180> here<00:06:39.300> to<00:06:39.479> think 00:06:39.590 --> 00:06:39.600 align:start position:0% and I think it's helpful here to think 00:06:39.600 --> 00:06:41.870 align:start position:0% and I think it's helpful here to think about<00:06:39.720> two<00:06:40.139> signs<00:06:40.500> of<00:06:40.620> development<00:06:40.979> process 00:06:41.870 --> 00:06:41.880 align:start position:0% about two signs of development process 00:06:41.880 --> 00:06:44.090 align:start position:0% about two signs of development process on<00:06:42.479> one<00:06:42.660> hand<00:06:42.780> you<00:06:43.319> have<00:06:43.440> like<00:06:43.620> your<00:06:43.800> r<00:06:43.979> d 00:06:44.090 --> 00:06:44.100 align:start position:0% on one hand you have like your r d 00:06:44.100 --> 00:06:46.309 align:start position:0% on one hand you have like your r d people<00:06:44.400> think<00:06:44.699> of<00:06:44.880> italic<00:06:45.539> and<00:06:45.960> then<00:06:46.139> on<00:06:46.259> the 00:06:46.309 --> 00:06:46.319 align:start position:0% people think of italic and then on the 00:06:46.319 --> 00:06:47.990 align:start position:0% people think of italic and then on the other<00:06:46.380> hand<00:06:46.500> you<00:06:46.680> have<00:06:46.860> implementers<00:06:47.940> um 00:06:47.990 --> 00:06:48.000 align:start position:0% other hand you have implementers um 00:06:48.000 --> 00:06:51.230 align:start position:0% other hand you have implementers um Peter<00:06:48.960> who's<00:06:49.139> the<00:06:49.500> gef<00:06:49.860> team<00:06:50.039> lead 00:06:51.230 --> 00:06:51.240 align:start position:0% Peter who's the gef team lead 00:06:51.240 --> 00:06:52.850 align:start position:0% Peter who's the gef team lead um<00:06:51.300> the<00:06:51.539> r<00:06:51.660> d<00:06:51.780> people 00:06:52.850 --> 00:06:52.860 align:start position:0% um the r d people 00:06:52.860 --> 00:06:54.590 align:start position:0% um the r d people um<00:06:52.919> they're<00:06:53.220> doing<00:06:53.460> research 00:06:54.590 --> 00:06:54.600 align:start position:0% um they're doing research 00:06:54.600 --> 00:06:56.450 align:start position:0% um they're doing research um they<00:06:54.960> want<00:06:55.080> to<00:06:55.380> throw<00:06:55.680> together<00:06:55.979> some 00:06:56.450 --> 00:06:56.460 align:start position:0% um they want to throw together some 00:06:56.460 --> 00:06:57.710 align:start position:0% um they want to throw together some simple<00:06:56.699> python<00:06:57.180> they<00:06:57.360> don't<00:06:57.479> really<00:06:57.539> care 00:06:57.710 --> 00:06:57.720 align:start position:0% simple python they don't really care 00:06:57.720 --> 00:06:58.850 align:start position:0% simple python they don't really care about<00:06:57.840> performance<00:06:58.319> they<00:06:58.500> just<00:06:58.620> want<00:06:58.740> to 00:06:58.850 --> 00:06:58.860 align:start position:0% about performance they just want to 00:06:58.860 --> 00:07:00.529 align:start position:0% about performance they just want to write<00:06:59.039> it<00:06:59.220> test<00:06:59.460> it<00:06:59.639> and<00:06:59.759> think<00:06:59.880> is<00:07:00.060> this<00:07:00.240> a<00:07:00.360> way 00:07:00.529 --> 00:07:00.539 align:start position:0% write it test it and think is this a way 00:07:00.539 --> 00:07:02.090 align:start position:0% write it test it and think is this a way we<00:07:00.720> should<00:07:00.960> do<00:07:01.139> this<00:07:01.319> thing 00:07:02.090 --> 00:07:02.100 align:start position:0% we should do this thing 00:07:02.100 --> 00:07:04.010 align:start position:0% we should do this thing on<00:07:02.819> the<00:07:02.940> other<00:07:03.060> hand<00:07:03.240> you<00:07:03.780> have<00:07:03.840> the 00:07:04.010 --> 00:07:04.020 align:start position:0% on the other hand you have the 00:07:04.020 --> 00:07:06.110 align:start position:0% on the other hand you have the implementers<00:07:04.620> who<00:07:05.280> are<00:07:05.400> trying<00:07:05.580> to<00:07:05.759> write<00:07:05.880> her 00:07:06.110 --> 00:07:06.120 align:start position:0% implementers who are trying to write her 00:07:06.120 --> 00:07:08.150 align:start position:0% implementers who are trying to write her robust<00:07:06.419> production-ready<00:07:07.080> system<00:07:07.680> they<00:07:07.979> want 00:07:08.150 --> 00:07:08.160 align:start position:0% robust production-ready system they want 00:07:08.160 --> 00:07:09.650 align:start position:0% robust production-ready system they want to<00:07:08.280> know<00:07:08.400> every<00:07:08.580> single<00:07:08.819> subtle<00:07:09.180> detail<00:07:09.479> of 00:07:09.650 --> 00:07:09.660 align:start position:0% to know every single subtle detail of 00:07:09.660 --> 00:07:11.570 align:start position:0% to know every single subtle detail of every<00:07:09.840> single<00:07:10.139> thing<00:07:10.319> that<00:07:11.100> has<00:07:11.280> to<00:07:11.400> happen 00:07:11.570 --> 00:07:11.580 align:start position:0% every single thing that has to happen 00:07:11.580 --> 00:07:13.610 align:start position:0% every single thing that has to happen because<00:07:11.759> if<00:07:12.000> they<00:07:12.120> get<00:07:12.240> it<00:07:12.360> wrong<00:07:12.539> that's<00:07:13.380> a 00:07:13.610 --> 00:07:13.620 align:start position:0% because if they get it wrong that's a 00:07:13.620 --> 00:07:15.770 align:start position:0% because if they get it wrong that's a major<00:07:13.740> security<00:07:14.039> instance<00:07:14.639> and<00:07:15.300> also<00:07:15.600> they 00:07:15.770 --> 00:07:15.780 align:start position:0% major security instance and also they 00:07:15.780 --> 00:07:16.909 align:start position:0% major security instance and also they have<00:07:15.900> to<00:07:16.020> like<00:07:16.139> spend<00:07:16.500> all<00:07:16.620> their<00:07:16.740> time 00:07:16.909 --> 00:07:16.919 align:start position:0% have to like spend all their time 00:07:16.919 --> 00:07:18.770 align:start position:0% have to like spend all their time thinking<00:07:17.220> about<00:07:17.280> the<00:07:17.580> subtleties<00:07:18.060> of<00:07:18.240> like<00:07:18.419> DB 00:07:18.770 --> 00:07:18.780 align:start position:0% thinking about the subtleties of like DB 00:07:18.780 --> 00:07:21.110 align:start position:0% thinking about the subtleties of like DB disk<00:07:19.139> performance<00:07:19.440> which<00:07:19.740> is<00:07:19.919> a<00:07:20.220> endless<00:07:20.880> bug 00:07:21.110 --> 00:07:21.120 align:start position:0% disk performance which is a endless bug 00:07:21.120 --> 00:07:23.270 align:start position:0% disk performance which is a endless bug there<00:07:21.360> for<00:07:21.599> anyone<00:07:21.900> who<00:07:22.080> has<00:07:22.199> worked<00:07:22.620> on<00:07:22.800> the 00:07:23.270 --> 00:07:23.280 align:start position:0% there for anyone who has worked on the 00:07:23.280 --> 00:07:24.890 align:start position:0% there for anyone who has worked on the execution<00:07:23.639> there 00:07:24.890 --> 00:07:24.900 align:start position:0% execution there 00:07:24.900 --> 00:07:27.170 align:start position:0% execution there um<00:07:24.960> and<00:07:25.380> Eels<00:07:25.740> provides<00:07:26.400> a<00:07:26.580> common<00:07:26.699> framework 00:07:27.170 --> 00:07:27.180 align:start position:0% um and Eels provides a common framework 00:07:27.180 --> 00:07:29.210 align:start position:0% um and Eels provides a common framework it<00:07:27.479> allows<00:07:27.840> these<00:07:28.139> two<00:07:28.259> sides<00:07:28.620> to<00:07:28.800> talk<00:07:28.979> to 00:07:29.210 --> 00:07:29.220 align:start position:0% it allows these two sides to talk to 00:07:29.220 --> 00:07:32.029 align:start position:0% it allows these two sides to talk to each<00:07:29.340> other<00:07:29.520> it's<00:07:29.940> a<00:07:30.120> Common<00:07:30.300> Language<00:07:30.860> your<00:07:31.860> r 00:07:32.029 --> 00:07:32.039 align:start position:0% each other it's a Common Language your r 00:07:32.039 --> 00:07:34.309 align:start position:0% each other it's a Common Language your r d<00:07:32.160> people<00:07:32.400> they<00:07:32.699> can<00:07:32.880> write<00:07:33.180> that<00:07:33.780> Python<00:07:34.199> and 00:07:34.309 --> 00:07:34.319 align:start position:0% d people they can write that Python and 00:07:34.319 --> 00:07:35.870 align:start position:0% d people they can write that Python and this<00:07:34.740> is<00:07:34.800> what<00:07:34.919> is<00:07:35.099> already<00:07:35.280> when<00:07:35.699> they're 00:07:35.870 --> 00:07:35.880 align:start position:0% this is what is already when they're 00:07:35.880 --> 00:07:37.070 align:start position:0% this is what is already when they're doing<00:07:36.000> their<00:07:36.180> research<00:07:36.479> they<00:07:36.660> write<00:07:36.900> little 00:07:37.070 --> 00:07:37.080 align:start position:0% doing their research they write little 00:07:37.080 --> 00:07:38.629 align:start position:0% doing their research they write little python<00:07:37.560> models<00:07:37.860> well<00:07:37.979> now<00:07:38.160> you<00:07:38.280> have<00:07:38.460> these 00:07:38.629 --> 00:07:38.639 align:start position:0% python models well now you have these 00:07:38.639 --> 00:07:40.189 align:start position:0% python models well now you have these specs<00:07:39.060> if<00:07:39.539> you've<00:07:39.720> written<00:07:39.960> that<00:07:40.080> little 00:07:40.189 --> 00:07:40.199 align:start position:0% specs if you've written that little 00:07:40.199 --> 00:07:42.890 align:start position:0% specs if you've written that little python<00:07:40.680> model<00:07:40.860> you<00:07:41.639> can<00:07:41.759> like<00:07:42.419> stick<00:07:42.599> it<00:07:42.780> in 00:07:42.890 --> 00:07:42.900 align:start position:0% python model you can like stick it in 00:07:42.900 --> 00:07:44.629 align:start position:0% python model you can like stick it in eels<00:07:43.199> you<00:07:43.380> can<00:07:43.500> implement<00:07:43.740> it<00:07:43.919> eels<00:07:44.220> it's<00:07:44.400> not 00:07:44.629 --> 00:07:44.639 align:start position:0% eels you can implement it eels it's not 00:07:44.639 --> 00:07:47.990 align:start position:0% eels you can implement it eels it's not much<00:07:44.759> more<00:07:45.000> work<00:07:45.240> and<00:07:45.660> already<00:07:45.900> you<00:07:46.680> have<00:07:47.039> like 00:07:47.990 --> 00:07:48.000 align:start position:0% much more work and already you have like 00:07:48.000 --> 00:07:49.610 align:start position:0% much more work and already you have like you<00:07:48.660> have<00:07:48.780> something<00:07:49.020> that<00:07:49.259> you<00:07:49.380> can<00:07:49.500> then 00:07:49.610 --> 00:07:49.620 align:start position:0% you have something that you can then 00:07:49.620 --> 00:07:51.770 align:start position:0% you have something that you can then show<00:07:49.919> to<00:07:50.099> the<00:07:50.220> implementers<00:07:50.759> this<00:07:51.419> leads<00:07:51.660> to 00:07:51.770 --> 00:07:51.780 align:start position:0% show to the implementers this leads to 00:07:51.780 --> 00:07:53.570 align:start position:0% show to the implementers this leads to this<00:07:52.020> sort<00:07:52.139> of<00:07:52.259> development<00:07:52.620> process<00:07:52.979> you 00:07:53.570 --> 00:07:53.580 align:start position:0% this sort of development process you 00:07:53.580 --> 00:07:55.309 align:start position:0% this sort of development process you have<00:07:53.759> your<00:07:53.880> r<00:07:54.000> d<00:07:54.180> people<00:07:54.479> they<00:07:54.720> develop<00:07:55.080> their 00:07:55.309 --> 00:07:55.319 align:start position:0% have your r d people they develop their 00:07:55.319 --> 00:07:59.210 align:start position:0% have your r d people they develop their idea<00:07:55.620> they<00:07:56.039> prototype<00:07:56.520> it<00:07:56.699> in<00:07:56.880> eels<00:07:57.620> you<00:07:58.620> then 00:07:59.210 --> 00:07:59.220 align:start position:0% idea they prototype it in eels you then 00:07:59.220 --> 00:08:02.150 align:start position:0% idea they prototype it in eels you then give<00:07:59.699> it<00:07:59.940> to<00:08:00.060> us<00:08:00.599> at<00:08:00.900> the<00:08:01.020> eels<00:08:01.199> team<00:08:01.380> and<00:08:01.560> we<00:08:01.740> as 00:08:02.150 --> 00:08:02.160 align:start position:0% give it to us at the eels team and we as 00:08:02.160 --> 00:08:04.909 align:start position:0% give it to us at the eels team and we as of<00:08:02.580> like<00:08:02.759> the<00:08:02.880> governance<00:08:03.300> process<00:08:03.919> integrate 00:08:04.909 --> 00:08:04.919 align:start position:0% of like the governance process integrate 00:08:04.919 --> 00:08:07.309 align:start position:0% of like the governance process integrate all<00:08:05.639> of<00:08:05.759> those<00:08:05.940> things<00:08:06.120> together<00:08:06.419> we<00:08:06.960> make<00:08:07.139> a 00:08:07.309 --> 00:08:07.319 align:start position:0% all of those things together we make a 00:08:07.319 --> 00:08:09.409 align:start position:0% all of those things together we make a hard<00:08:07.440> Fork<00:08:07.860> exactly<00:08:08.639> what<00:08:08.819> goes<00:08:09.060> in<00:08:09.120> obviously 00:08:09.409 --> 00:08:09.419 align:start position:0% hard Fork exactly what goes in obviously 00:08:09.419 --> 00:08:11.390 align:start position:0% hard Fork exactly what goes in obviously is<00:08:09.599> like<00:08:09.900> a<00:08:10.080> theme<00:08:10.440> for<00:08:10.560> all<00:08:10.740> quartet<00:08:11.039> it's<00:08:11.280> not 00:08:11.390 --> 00:08:11.400 align:start position:0% is like a theme for all quartet it's not 00:08:11.400 --> 00:08:13.249 align:start position:0% is like a theme for all quartet it's not like<00:08:11.460> we're<00:08:11.639> taking<00:08:11.819> all<00:08:12.000> the<00:08:12.120> power<00:08:12.240> here<00:08:12.900> and 00:08:13.249 --> 00:08:13.259 align:start position:0% like we're taking all the power here and 00:08:13.259 --> 00:08:14.930 align:start position:0% like we're taking all the power here and quickly<00:08:13.740> once<00:08:14.039> you've<00:08:14.099> done<00:08:14.280> that<00:08:14.460> there's<00:08:14.819> a 00:08:14.930 --> 00:08:14.940 align:start position:0% quickly once you've done that there's a 00:08:14.940 --> 00:08:16.010 align:start position:0% quickly once you've done that there's a whole<00:08:15.060> bunch<00:08:15.180> of<00:08:15.300> things<00:08:15.419> you<00:08:15.599> can<00:08:15.660> do<00:08:15.780> because 00:08:16.010 --> 00:08:16.020 align:start position:0% whole bunch of things you can do because 00:08:16.020 --> 00:08:17.749 align:start position:0% whole bunch of things you can do because you<00:08:16.199> have<00:08:16.319> an<00:08:16.440> executable<00:08:16.860> spec 00:08:17.749 --> 00:08:17.759 align:start position:0% you have an executable spec 00:08:17.759 --> 00:08:20.629 align:start position:0% you have an executable spec we<00:08:18.180> are<00:08:18.419> executable<00:08:19.020> spec<00:08:19.259> will<00:08:20.039> be<00:08:20.220> able<00:08:20.460> to 00:08:20.629 --> 00:08:20.639 align:start position:0% we are executable spec will be able to 00:08:20.639 --> 00:08:23.809 align:start position:0% we are executable spec will be able to fill<00:08:21.599> all<00:08:22.020> the<00:08:22.199> test<00:08:22.319> sectors<00:08:22.680> it<00:08:23.520> might<00:08:23.639> even 00:08:23.809 --> 00:08:23.819 align:start position:0% fill all the test sectors it might even 00:08:23.819 --> 00:08:26.210 align:start position:0% fill all the test sectors it might even be<00:08:24.060> able<00:08:24.300> to<00:08:24.419> like<00:08:24.780> run<00:08:25.080> its<00:08:25.440> own<00:08:25.500> very 00:08:26.210 --> 00:08:26.220 align:start position:0% be able to like run its own very 00:08:26.220 --> 00:08:28.309 align:start position:0% be able to like run its own very miniature<00:08:26.819> like<00:08:27.120> two<00:08:27.479> million<00:08:27.840> gas<00:08:27.960> a<00:08:28.199> block 00:08:28.309 --> 00:08:28.319 align:start position:0% miniature like two million gas a block 00:08:28.319 --> 00:08:30.710 align:start position:0% miniature like two million gas a block test<00:08:28.680> net<00:08:28.919> and<00:08:29.819> that<00:08:30.000> means<00:08:30.240> that<00:08:30.360> you<00:08:30.539> can 00:08:30.710 --> 00:08:30.720 align:start position:0% test net and that means that you can 00:08:30.720 --> 00:08:33.170 align:start position:0% test net and that means that you can have<00:08:30.840> tests<00:08:31.379> and<00:08:31.919> for<00:08:32.219> size<00:08:32.459> specs<00:08:32.820> before 00:08:33.170 --> 00:08:33.180 align:start position:0% have tests and for size specs before 00:08:33.180 --> 00:08:35.269 align:start position:0% have tests and for size specs before you've<00:08:33.479> even<00:08:33.599> written<00:08:34.020> a<00:08:34.140> line<00:08:34.260> of<00:08:34.440> code<00:08:34.680> in 00:08:35.269 --> 00:08:35.279 align:start position:0% you've even written a line of code in 00:08:35.279 --> 00:08:36.589 align:start position:0% you've even written a line of code in your<00:08:35.399> production<00:08:35.700> class 00:08:36.589 --> 00:08:36.599 align:start position:0% your production class 00:08:36.599 --> 00:08:39.170 align:start position:0% your production class this<00:08:37.200> like<00:08:37.440> frees<00:08:37.800> up<00:08:38.339> um<00:08:38.339> production<00:08:38.700> clients 00:08:39.170 --> 00:08:39.180 align:start position:0% this like frees up um production clients 00:08:39.180 --> 00:08:41.570 align:start position:0% this like frees up um production clients to<00:08:39.599> not<00:08:39.719> have<00:08:39.899> to<00:08:40.080> be<00:08:40.260> also<00:08:40.919> the<00:08:41.279> r<00:08:41.399> d 00:08:41.570 --> 00:08:41.580 align:start position:0% to not have to be also the r d 00:08:41.580 --> 00:08:43.490 align:start position:0% to not have to be also the r d playground<00:08:42.060> that<00:08:42.719> they<00:08:42.899> cut<00:08:43.020> that<00:08:43.200> they 00:08:43.490 --> 00:08:43.500 align:start position:0% playground that they cut that they 00:08:43.500 --> 00:08:45.650 align:start position:0% playground that they cut that they sometimes<00:08:43.919> are<00:08:44.099> it<00:08:44.820> is<00:08:45.000> not<00:08:45.180> like<00:08:45.360> a<00:08:45.540> perfect 00:08:45.650 --> 00:08:45.660 align:start position:0% sometimes are it is not like a perfect 00:08:45.660 --> 00:08:47.030 align:start position:0% sometimes are it is not like a perfect thing<00:08:45.899> like<00:08:46.260> often<00:08:46.560> you<00:08:46.620> have<00:08:46.740> to<00:08:46.800> go<00:08:46.920> and 00:08:47.030 --> 00:08:47.040 align:start position:0% thing like often you have to go and 00:08:47.040 --> 00:08:48.710 align:start position:0% thing like often you have to go and Implement<00:08:47.279> models<00:08:47.700> in<00:08:48.060> production<00:08:48.360> clients 00:08:48.710 --> 00:08:48.720 align:start position:0% Implement models in production clients 00:08:48.720 --> 00:08:50.509 align:start position:0% Implement models in production clients to<00:08:48.839> deal<00:08:48.959> with<00:08:49.140> performance<00:08:49.560> issues<00:08:49.980> there 00:08:50.509 --> 00:08:50.519 align:start position:0% to deal with performance issues there 00:08:50.519 --> 00:08:52.090 align:start position:0% to deal with performance issues there are<00:08:50.640> networking<00:08:51.000> issues<00:08:51.240> we<00:08:51.420> don't<00:08:51.540> deal<00:08:51.720> with 00:08:52.090 --> 00:08:52.100 align:start position:0% are networking issues we don't deal with 00:08:52.100 --> 00:08:54.590 align:start position:0% are networking issues we don't deal with but<00:08:53.100> currently<00:08:53.459> like<00:08:53.760> anyone<00:08:54.120> who<00:08:54.300> wants<00:08:54.540> to 00:08:54.590 --> 00:08:54.600 align:start position:0% but currently like anyone who wants to 00:08:54.600 --> 00:08:56.269 align:start position:0% but currently like anyone who wants to propose<00:08:54.899> any<00:08:55.080> like<00:08:55.320> significant<00:08:55.800> change<00:08:56.040> they 00:08:56.269 --> 00:08:56.279 align:start position:0% propose any like significant change they 00:08:56.279 --> 00:08:58.790 align:start position:0% propose any like significant change they have<00:08:56.459> they<00:08:56.640> like<00:08:56.880> implemented<00:08:57.480> in<00:08:57.660> geaf<00:08:58.320> or 00:08:58.790 --> 00:08:58.800 align:start position:0% have they like implemented in geaf or 00:08:58.800 --> 00:09:00.050 align:start position:0% have they like implemented in geaf or wherever 00:09:00.050 --> 00:09:00.060 align:start position:0% wherever 00:09:00.060 --> 00:09:01.370 align:start position:0% wherever um<00:09:00.180> whereas<00:09:00.540> now<00:09:00.660> you<00:09:00.779> have<00:09:00.899> this<00:09:01.080> playground 00:09:01.370 --> 00:09:01.380 align:start position:0% um whereas now you have this playground 00:09:01.380 --> 00:09:02.930 align:start position:0% um whereas now you have this playground to<00:09:01.740> do<00:09:02.040> it<00:09:02.160> in 00:09:02.930 --> 00:09:02.940 align:start position:0% to do it in 00:09:02.940 --> 00:09:04.670 align:start position:0% to do it in and<00:09:03.480> critically<00:09:03.779> this<00:09:04.019> is<00:09:04.080> like<00:09:04.260> a<00:09:04.440> sort<00:09:04.620> of 00:09:04.670 --> 00:09:04.680 align:start position:0% and critically this is like a sort of 00:09:04.680 --> 00:09:07.250 align:start position:0% and critically this is like a sort of paralyzation<00:09:05.220> stage<00:09:05.640> because<00:09:06.540> like 00:09:07.250 --> 00:09:07.260 align:start position:0% paralyzation stage because like 00:09:07.260 --> 00:09:09.829 align:start position:0% paralyzation stage because like currently<00:09:07.740> you<00:09:08.399> know<00:09:08.519> you<00:09:09.060> currently<00:09:09.660> you 00:09:09.829 --> 00:09:09.839 align:start position:0% currently you know you currently you 00:09:09.839 --> 00:09:11.930 align:start position:0% currently you know you currently you have<00:09:09.959> this<00:09:10.200> like<00:09:10.380> situation<00:09:11.279> where<00:09:11.580> like<00:09:11.760> the 00:09:11.930 --> 00:09:11.940 align:start position:0% have this like situation where like the 00:09:11.940 --> 00:09:13.670 align:start position:0% have this like situation where like the instrumentals<00:09:12.420> and<00:09:12.540> the<00:09:12.600> r<00:09:12.720> d<00:09:12.839> people<00:09:13.140> like 00:09:13.670 --> 00:09:13.680 align:start position:0% instrumentals and the r d people like 00:09:13.680 --> 00:09:15.290 align:start position:0% instrumentals and the r d people like get<00:09:13.920> have<00:09:14.160> to<00:09:14.339> like<00:09:14.459> interact<00:09:14.820> much<00:09:15.120> more 00:09:15.290 --> 00:09:15.300 align:start position:0% get have to like interact much more 00:09:15.300 --> 00:09:17.210 align:start position:0% get have to like interact much more tightly<00:09:15.600> if<00:09:16.380> you<00:09:16.440> have<00:09:16.620> this<00:09:16.800> like<00:09:16.920> eels 00:09:17.210 --> 00:09:17.220 align:start position:0% tightly if you have this like eels 00:09:17.220 --> 00:09:18.829 align:start position:0% tightly if you have this like eels process<00:09:17.580> you<00:09:17.820> can<00:09:18.000> like<00:09:18.120> separate<00:09:18.540> that<00:09:18.660> out 00:09:18.829 --> 00:09:18.839 align:start position:0% process you can like separate that out 00:09:18.839 --> 00:09:20.630 align:start position:0% process you can like separate that out and<00:09:19.080> do<00:09:19.200> these<00:09:19.380> in<00:09:19.560> parallel<00:09:19.920> so<00:09:20.160> that<00:09:20.339> you<00:09:20.519> can 00:09:20.630 --> 00:09:20.640 align:start position:0% and do these in parallel so that you can 00:09:20.640 --> 00:09:22.850 align:start position:0% and do these in parallel so that you can like<00:09:21.180> have<00:09:21.480> the<00:09:21.720> implementers<00:09:22.200> finishing<00:09:22.680> up 00:09:22.850 --> 00:09:22.860 align:start position:0% like have the implementers finishing up 00:09:22.860 --> 00:09:25.009 align:start position:0% like have the implementers finishing up one<00:09:23.040> hard<00:09:23.399> Fork<00:09:23.880> while<00:09:24.300> eels<00:09:24.720> are<00:09:24.899> like 00:09:25.009 --> 00:09:25.019 align:start position:0% one hard Fork while eels are like 00:09:25.019 --> 00:09:26.449 align:start position:0% one hard Fork while eels are like getting<00:09:25.200> ready<00:09:25.440> to<00:09:25.620> prepare<00:09:25.920> the<00:09:26.100> next<00:09:26.220> hard 00:09:26.449 --> 00:09:26.459 align:start position:0% getting ready to prepare the next hard 00:09:26.459 --> 00:09:28.370 align:start position:0% getting ready to prepare the next hard Fork<00:09:26.940> whereas<00:09:27.720> if<00:09:27.839> you're<00:09:27.959> like<00:09:28.140> busy 00:09:28.370 --> 00:09:28.380 align:start position:0% Fork whereas if you're like busy 00:09:28.380 --> 00:09:29.570 align:start position:0% Fork whereas if you're like busy modeling<00:09:28.740> things<00:09:28.860> in<00:09:29.040> gef<00:09:29.339> and<00:09:29.459> the 00:09:29.570 --> 00:09:29.580 align:start position:0% modeling things in gef and the 00:09:29.580 --> 00:09:31.370 align:start position:0% modeling things in gef and the implementers<00:09:30.000> are<00:09:30.240> also<00:09:30.480> tied<00:09:31.019> into<00:09:31.200> doing 00:09:31.370 --> 00:09:31.380 align:start position:0% implementers are also tied into doing 00:09:31.380 --> 00:09:33.230 align:start position:0% implementers are also tied into doing the<00:09:31.620> r<00:09:31.740> d<00:09:31.920> you<00:09:32.459> just<00:09:32.580> don't<00:09:32.700> get<00:09:32.880> the<00:09:33.060> same 00:09:33.230 --> 00:09:33.240 align:start position:0% the r d you just don't get the same 00:09:33.240 --> 00:09:36.530 align:start position:0% the r d you just don't get the same parallel<00:09:33.899> efficiency<00:09:34.640> I<00:09:35.640> just<00:09:35.820> now<00:09:36.060> talk<00:09:36.240> a 00:09:36.530 --> 00:09:36.540 align:start position:0% parallel efficiency I just now talk a 00:09:36.540 --> 00:09:38.810 align:start position:0% parallel efficiency I just now talk a bit<00:09:36.660> about<00:09:36.779> where<00:09:37.560> we're<00:09:37.680> at<00:09:37.860> we<00:09:38.760> have 00:09:38.810 --> 00:09:38.820 align:start position:0% bit about where we're at we have 00:09:38.820 --> 00:09:42.050 align:start position:0% bit about where we're at we have implemented<00:09:39.300> all<00:09:39.660> the<00:09:39.779> hard<00:09:39.899> folks<00:09:40.800> um<00:09:40.860> uh<00:09:41.700> the 00:09:42.050 --> 00:09:42.060 align:start position:0% implemented all the hard folks um uh the 00:09:42.060 --> 00:09:44.750 align:start position:0% implemented all the hard folks um uh the merge<00:09:42.420> is<00:09:42.480> still<00:09:42.660> a<00:09:42.839> PR<00:09:42.959> but<00:09:43.920> we're<00:09:44.519> nearly 00:09:44.750 --> 00:09:44.760 align:start position:0% merge is still a PR but we're nearly 00:09:44.760 --> 00:09:46.250 align:start position:0% merge is still a PR but we're nearly there 00:09:46.250 --> 00:09:46.260 align:start position:0% there 00:09:46.260 --> 00:09:47.750 align:start position:0% there um<00:09:46.320> we're<00:09:46.860> going<00:09:46.980> to<00:09:47.100> need<00:09:47.160> to<00:09:47.220> do<00:09:47.339> a<00:09:47.459> bunch<00:09:47.640> of 00:09:47.750 --> 00:09:47.760 align:start position:0% um we're going to need to do a bunch of 00:09:47.760 --> 00:09:48.650 align:start position:0% um we're going to need to do a bunch of like 00:09:48.650 --> 00:09:48.660 align:start position:0% like 00:09:48.660 --> 00:09:50.810 align:start position:0% like um<00:09:48.720> refactoring 00:09:50.810 --> 00:09:50.820 align:start position:0% um refactoring 00:09:50.820 --> 00:09:53.930 align:start position:0% um refactoring um<00:09:50.880> and<00:09:51.600> then<00:09:51.660> we<00:09:51.899> need<00:09:52.140> to<00:09:52.740> freeze<00:09:53.640> the<00:09:53.700> code 00:09:53.930 --> 00:09:53.940 align:start position:0% um and then we need to freeze the code 00:09:53.940 --> 00:09:55.370 align:start position:0% um and then we need to freeze the code because<00:09:54.420> we're<00:09:54.660> asking<00:09:54.899> people<00:09:55.080> to<00:09:55.260> like 00:09:55.370 --> 00:09:55.380 align:start position:0% because we're asking people to like 00:09:55.380 --> 00:09:56.690 align:start position:0% because we're asking people to like build<00:09:55.560> it<00:09:55.740> we're<00:09:55.920> saying<00:09:56.100> if<00:09:56.279> you<00:09:56.399> want<00:09:56.580> to 00:09:56.690 --> 00:09:56.700 align:start position:0% build it we're saying if you want to 00:09:56.700 --> 00:10:00.350 align:start position:0% build it we're saying if you want to take<00:09:57.360> an<00:09:57.540> EIP<00:09:57.980> and<00:09:58.980> you<00:09:59.160> want<00:09:59.339> to<00:09:59.519> build<00:09:59.940> on<00:10:00.240> top 00:10:00.350 --> 00:10:00.360 align:start position:0% take an EIP and you want to build on top 00:10:00.360 --> 00:10:03.410 align:start position:0% take an EIP and you want to build on top of<00:10:00.480> that<00:10:00.720> change<00:10:01.560> it<00:10:01.740> you<00:10:01.920> have<00:10:02.459> to<00:10:02.580> take 00:10:03.410 --> 00:10:03.420 align:start position:0% of that change it you have to take 00:10:03.420 --> 00:10:06.889 align:start position:0% of that change it you have to take our<00:10:04.260> latest<00:10:04.560> Fork<00:10:05.160> copy<00:10:05.940> it<00:10:06.120> Implement<00:10:06.660> your 00:10:06.889 --> 00:10:06.899 align:start position:0% our latest Fork copy it Implement your 00:10:06.899 --> 00:10:08.449 align:start position:0% our latest Fork copy it Implement your own<00:10:07.019> changes<00:10:07.380> and<00:10:07.560> we<00:10:07.680> can't<00:10:07.800> ask<00:10:08.040> people<00:10:08.220> to 00:10:08.449 --> 00:10:08.459 align:start position:0% own changes and we can't ask people to 00:10:08.459 --> 00:10:10.310 align:start position:0% own changes and we can't ask people to do<00:10:08.640> that<00:10:08.820> sort<00:10:09.000> of<00:10:09.180> thing<00:10:09.300> until<00:10:09.720> we've<00:10:10.080> freeze 00:10:10.310 --> 00:10:10.320 align:start position:0% do that sort of thing until we've freeze 00:10:10.320 --> 00:10:11.389 align:start position:0% do that sort of thing until we've freeze the<00:10:10.440> code<00:10:10.560> and<00:10:10.740> said<00:10:10.860> we're<00:10:11.100> not<00:10:11.220> going<00:10:11.279> to 00:10:11.389 --> 00:10:11.399 align:start position:0% the code and said we're not going to 00:10:11.399 --> 00:10:12.710 align:start position:0% the code and said we're not going to like<00:10:11.519> refactor<00:10:12.000> it<00:10:12.060> under<00:10:12.240> you<00:10:12.420> and<00:10:12.480> we're<00:10:12.600> not 00:10:12.710 --> 00:10:12.720 align:start position:0% like refactor it under you and we're not 00:10:12.720 --> 00:10:14.090 align:start position:0% like refactor it under you and we're not quite<00:10:12.839> there<00:10:12.959> yet<00:10:13.140> once<00:10:13.680> we've<00:10:13.860> done<00:10:13.980> that 00:10:14.090 --> 00:10:14.100 align:start position:0% quite there yet once we've done that 00:10:14.100 --> 00:10:16.009 align:start position:0% quite there yet once we've done that we're<00:10:14.279> playing<00:10:14.459> like<00:10:14.820> Shadow<00:10:15.300> the<00:10:15.660> current 00:10:16.009 --> 00:10:16.019 align:start position:0% we're playing like Shadow the current 00:10:16.019 --> 00:10:17.630 align:start position:0% we're playing like Shadow the current governance<00:10:16.560> process<00:10:16.860> for<00:10:17.040> Shanghai<00:10:17.399> so 00:10:17.630 --> 00:10:17.640 align:start position:0% governance process for Shanghai so 00:10:17.640 --> 00:10:19.550 align:start position:0% governance process for Shanghai so Shanghai<00:10:18.060> is<00:10:18.660> going<00:10:18.839> to<00:10:19.019> go<00:10:19.200> through<00:10:19.380> in 00:10:19.550 --> 00:10:19.560 align:start position:0% Shanghai is going to go through in 00:10:19.560 --> 00:10:21.290 align:start position:0% Shanghai is going to go through in exactly<00:10:20.040> the<00:10:20.160> way<00:10:20.279> that<00:10:20.459> all<00:10:20.700> previous<00:10:20.880> like 00:10:21.290 --> 00:10:21.300 align:start position:0% exactly the way that all previous like 00:10:21.300 --> 00:10:22.730 align:start position:0% exactly the way that all previous like hard<00:10:21.540> Forks<00:10:21.959> have<00:10:22.019> gone<00:10:22.140> through<00:10:22.320> but<00:10:22.560> we're 00:10:22.730 --> 00:10:22.740 align:start position:0% hard Forks have gone through but we're 00:10:22.740 --> 00:10:25.070 align:start position:0% hard Forks have gone through but we're going<00:10:22.980> to<00:10:23.100> also<00:10:23.519> be<00:10:23.820> working<00:10:24.600> with<00:10:24.839> a<00:10:25.019> whole 00:10:25.070 --> 00:10:25.080 align:start position:0% going to also be working with a whole 00:10:25.080 --> 00:10:26.530 align:start position:0% going to also be working with a whole bunch<00:10:25.200> of<00:10:25.320> people<00:10:25.500> to<00:10:25.800> try<00:10:25.920> and<00:10:26.040> Implement 00:10:26.530 --> 00:10:26.540 align:start position:0% bunch of people to try and Implement 00:10:26.540 --> 00:10:30.290 align:start position:0% bunch of people to try and Implement those<00:10:27.540> changes<00:10:28.140> changes<00:10:28.860> as<00:10:29.220> eels<00:10:29.640> proposals 00:10:30.290 --> 00:10:30.300 align:start position:0% those changes changes as eels proposals 00:10:30.300 --> 00:10:32.210 align:start position:0% those changes changes as eels proposals and<00:10:30.959> then<00:10:31.080> we're<00:10:31.260> going<00:10:31.380> to<00:10:31.500> like<00:10:31.680> see<00:10:31.920> how<00:10:32.100> the 00:10:32.210 --> 00:10:32.220 align:start position:0% and then we're going to like see how the 00:10:32.220 --> 00:10:33.829 align:start position:0% and then we're going to like see how the government's<00:10:32.519> process<00:10:32.820> works<00:10:33.240> and<00:10:33.720> then 00:10:33.829 --> 00:10:33.839 align:start position:0% government's process works and then 00:10:33.839 --> 00:10:35.150 align:start position:0% government's process works and then hopefully<00:10:34.140> we<00:10:34.320> can<00:10:34.440> like<00:10:34.560> improve<00:10:34.920> on<00:10:35.040> that 00:10:35.150 --> 00:10:35.160 align:start position:0% hopefully we can like improve on that 00:10:35.160 --> 00:10:37.550 align:start position:0% hopefully we can like improve on that and<00:10:35.339> talk<00:10:35.519> about<00:10:35.700> moving<00:10:36.540> away<00:10:36.720> from<00:10:37.140> some<00:10:37.440> of 00:10:37.550 --> 00:10:37.560 align:start position:0% and talk about moving away from some of 00:10:37.560 --> 00:10:39.650 align:start position:0% and talk about moving away from some of these<00:10:37.800> Legacy<00:10:38.399> approaches<00:10:38.940> to<00:10:39.180> specifying 00:10:39.650 --> 00:10:39.660 align:start position:0% these Legacy approaches to specifying 00:10:39.660 --> 00:10:41.870 align:start position:0% these Legacy approaches to specifying execution<00:10:40.080> there<00:10:40.320> finally<00:10:40.860> there's<00:10:41.640> the 00:10:41.870 --> 00:10:41.880 align:start position:0% execution there finally there's the 00:10:41.880 --> 00:10:44.810 align:start position:0% execution there finally there's the question<00:10:42.000> of<00:10:42.300> how<00:10:43.019> you<00:10:43.140> can<00:10:43.260> help<00:10:43.579> first<00:10:44.579> if 00:10:44.810 --> 00:10:44.820 align:start position:0% question of how you can help first if 00:10:44.820 --> 00:10:46.069 align:start position:0% question of how you can help first if you<00:10:44.940> actually<00:10:45.060> need<00:10:45.240> your<00:10:45.300> help<00:10:45.420> yet<00:10:45.600> we're 00:10:46.069 --> 00:10:46.079 align:start position:0% you actually need your help yet we're 00:10:46.079 --> 00:10:47.449 align:start position:0% you actually need your help yet we're still 00:10:47.449 --> 00:10:47.459 align:start position:0% still 00:10:47.459 --> 00:10:49.550 align:start position:0% still um uh<00:10:48.060> code<00:10:48.180> we're<00:10:48.420> still<00:10:48.660> coding<00:10:48.959> we<00:10:49.320> need<00:10:49.440> to 00:10:49.550 --> 00:10:49.560 align:start position:0% um uh code we're still coding we need to 00:10:49.560 --> 00:10:53.210 align:start position:0% um uh code we're still coding we need to finish<00:10:49.680> that<00:10:50.300> once<00:10:51.300> we've<00:10:51.480> done<00:10:51.660> that<00:10:52.100> we<00:10:53.100> ask 00:10:53.210 --> 00:10:53.220 align:start position:0% finish that once we've done that we ask 00:10:53.220 --> 00:10:57.530 align:start position:0% finish that once we've done that we ask you<00:10:53.399> to<00:10:53.579> like<00:10:53.760> Implement<00:10:54.600> your<00:10:55.140> favorite<00:10:55.440> EIP 00:10:57.530 --> 00:10:57.540 align:start position:0% you to like Implement your favorite EIP 00:10:57.540 --> 00:10:59.329 align:start position:0% you to like Implement your favorite EIP um and<00:10:57.959> like<00:10:58.019> give<00:10:58.260> us<00:10:58.440> feedback<00:10:58.740> like<00:10:58.920> how 00:10:59.329 --> 00:10:59.339 align:start position:0% um and like give us feedback like how 00:10:59.339 --> 00:11:00.650 align:start position:0% um and like give us feedback like how was<00:10:59.459> it<00:10:59.640> because<00:10:59.820> we<00:11:00.060> didn't<00:11:00.120> want<00:11:00.300> this<00:11:00.420> to<00:11:00.540> be 00:11:00.650 --> 00:11:00.660 align:start position:0% was it because we didn't want this to be 00:11:00.660 --> 00:11:02.690 align:start position:0% was it because we didn't want this to be a<00:11:00.720> world<00:11:00.839> where<00:11:01.200> we<00:11:01.620> as<00:11:01.800> like<00:11:01.980> the<00:11:02.160> eels<00:11:02.459> team 00:11:02.690 --> 00:11:02.700 align:start position:0% a world where we as like the eels team 00:11:02.700 --> 00:11:05.210 align:start position:0% a world where we as like the eels team can<00:11:03.360> like<00:11:03.600> develop<00:11:04.200> what<00:11:04.440> we<00:11:04.620> want<00:11:04.740> develop 00:11:05.210 --> 00:11:05.220 align:start position:0% can like develop what we want develop 00:11:05.220 --> 00:11:06.769 align:start position:0% can like develop what we want develop things<00:11:05.459> and<00:11:05.700> we<00:11:05.820> can<00:11:05.880> propose<00:11:06.120> changes<00:11:06.480> but<00:11:06.660> no 00:11:06.769 --> 00:11:06.779 align:start position:0% things and we can propose changes but no 00:11:06.779 --> 00:11:08.030 align:start position:0% things and we can propose changes but no one<00:11:06.899> else<00:11:06.959> understands<00:11:07.440> it<00:11:07.560> I<00:11:07.680> don't<00:11:07.800> want<00:11:07.920> to 00:11:08.030 --> 00:11:08.040 align:start position:0% one else understands it I don't want to 00:11:08.040 --> 00:11:08.870 align:start position:0% one else understands it I don't want to be<00:11:08.160> in<00:11:08.279> the<00:11:08.399> situation<00:11:08.579> that<00:11:08.820> you're 00:11:08.870 --> 00:11:08.880 align:start position:0% be in the situation that you're 00:11:08.880 --> 00:11:10.850 align:start position:0% be in the situation that you're currently<00:11:09.180> with<00:11:09.300> DNA<00:11:09.660> people<00:11:09.839> actually<00:11:10.260> only 00:11:10.850 --> 00:11:10.860 align:start position:0% currently with DNA people actually only 00:11:10.860 --> 00:11:12.590 align:start position:0% currently with DNA people actually only a<00:11:11.100> really<00:11:11.279> quite<00:11:11.579> small<00:11:11.760> minority<00:11:12.240> of<00:11:12.420> people 00:11:12.590 --> 00:11:12.600 align:start position:0% a really quite small minority of people 00:11:12.600 --> 00:11:15.050 align:start position:0% a really quite small minority of people know<00:11:13.320> how<00:11:13.680> to<00:11:13.800> write<00:11:13.980> Tech 00:11:15.050 --> 00:11:15.060 align:start position:0% know how to write Tech 00:11:15.060 --> 00:11:17.150 align:start position:0% know how to write Tech um<00:11:15.120> and<00:11:15.300> how<00:11:15.480> to<00:11:15.600> change<00:11:15.779> the<00:11:15.959> Euro<00:11:16.320> paper<00:11:16.440> so<00:11:17.100> I 00:11:17.150 --> 00:11:17.160 align:start position:0% um and how to change the Euro paper so I 00:11:17.160 --> 00:11:18.410 align:start position:0% um and how to change the Euro paper so I want<00:11:17.339> this<00:11:17.399> to<00:11:17.519> be<00:11:17.640> like<00:11:17.760> an<00:11:17.880> open<00:11:18.060> process 00:11:18.410 --> 00:11:18.420 align:start position:0% want this to be like an open process 00:11:18.420 --> 00:11:19.670 align:start position:0% want this to be like an open process where<00:11:18.660> anyone<00:11:18.959> who's<00:11:19.079> like<00:11:19.200> oh<00:11:19.320> I<00:11:19.500> want<00:11:19.620> to 00:11:19.670 --> 00:11:19.680 align:start position:0% where anyone who's like oh I want to 00:11:19.680 --> 00:11:21.889 align:start position:0% where anyone who's like oh I want to propose<00:11:20.040> something<00:11:20.220> to<00:11:20.940> just<00:11:21.180> clone<00:11:21.720> that 00:11:21.889 --> 00:11:21.899 align:start position:0% propose something to just clone that 00:11:21.899 --> 00:11:25.030 align:start position:0% propose something to just clone that repository<00:11:22.440> run<00:11:22.980> the<00:11:23.220> new<00:11:23.339> fork<00:11:23.760> tool<00:11:24.120> and 00:11:25.030 --> 00:11:25.040 align:start position:0% repository run the new fork tool and 00:11:25.040 --> 00:11:27.769 align:start position:0% repository run the new fork tool and Implement<00:11:26.040> their<00:11:26.519> change<00:11:26.760> and<00:11:27.180> like<00:11:27.300> produce 00:11:27.769 --> 00:11:27.779 align:start position:0% Implement their change and like produce 00:11:27.779 --> 00:11:29.509 align:start position:0% Implement their change and like produce a<00:11:27.959> proposal<00:11:28.380> without<00:11:28.560> being<00:11:28.860> burdened<00:11:29.339> by 00:11:29.509 --> 00:11:29.519 align:start position:0% a proposal without being burdened by 00:11:29.519 --> 00:11:31.550 align:start position:0% a proposal without being burdened by having<00:11:29.700> to<00:11:29.820> think<00:11:29.940> about<00:11:30.120> like<00:11:30.420> how<00:11:30.839> the<00:11:30.959> FDB 00:11:31.550 --> 00:11:31.560 align:start position:0% having to think about like how the FDB 00:11:31.560 --> 00:11:32.750 align:start position:0% having to think about like how the FDB works<00:11:31.860> or<00:11:31.980> whatever<00:11:32.100> or<00:11:32.339> whatever<00:11:32.579> else 00:11:32.750 --> 00:11:32.760 align:start position:0% works or whatever or whatever else 00:11:32.760 --> 00:11:35.269 align:start position:0% works or whatever or whatever else they're<00:11:32.940> going<00:11:33.060> to<00:11:33.120> do<00:11:33.180> they're<00:11:33.300> modeling 00:11:35.269 --> 00:11:35.279 align:start position:0% they're going to do they're modeling 00:11:35.279 --> 00:11:36.889 align:start position:0% they're going to do they're modeling um yeah 00:11:36.889 --> 00:11:36.899 align:start position:0% um yeah 00:11:36.899 --> 00:11:38.509 align:start position:0% um yeah um<00:11:37.019> that's<00:11:37.200> the<00:11:37.380> end<00:11:37.500> of<00:11:37.620> my<00:11:37.740> talk 00:11:38.509 --> 00:11:38.519 align:start position:0% um that's the end of my talk 00:11:38.519 --> 00:11:41.210 align:start position:0% um that's the end of my talk um<00:11:38.640> we<00:11:39.060> are<00:11:39.240> have<00:11:39.660> plenty<00:11:40.019> of<00:11:40.079> time<00:11:40.260> so<00:11:40.620> do 00:11:41.210 --> 00:11:41.220 align:start position:0% um we are have plenty of time so do 00:11:41.220 --> 00:11:43.130 align:start position:0% um we are have plenty of time so do people<00:11:41.399> have<00:11:41.579> any<00:11:41.640> questions 00:11:43.130 --> 00:11:43.140 align:start position:0% people have any questions 00:11:43.140 --> 00:11:46.190 align:start position:0% people have any questions State<00:11:43.560> growth<00:11:44.100> so<00:11:44.940> if<00:11:45.240> I<00:11:45.420> make<00:11:45.540> a<00:11:45.720> commit<00:11:46.019> to 00:11:46.190 --> 00:11:46.200 align:start position:0% State growth so if I make a commit to 00:11:46.200 --> 00:11:47.810 align:start position:0% State growth so if I make a commit to the<00:11:46.320> execution<00:11:46.740> spec<00:11:47.100> and<00:11:47.339> I<00:11:47.459> want<00:11:47.579> to<00:11:47.640> see<00:11:47.700> how 00:11:47.810 --> 00:11:47.820 align:start position:0% the execution spec and I want to see how 00:11:47.820 --> 00:11:50.269 align:start position:0% the execution spec and I want to see how that<00:11:47.940> influences<00:11:48.360> State<00:11:48.660> growth<00:11:49.019> over<00:11:49.140> time 00:11:50.269 --> 00:11:50.279 align:start position:0% that influences State growth over time 00:11:50.279 --> 00:11:51.829 align:start position:0% that influences State growth over time and<00:11:50.579> like<00:11:50.700> the<00:11:50.880> capability<00:11:51.180> to<00:11:51.420> run<00:11:51.540> a<00:11:51.660> node 00:11:51.829 --> 00:11:51.839 align:start position:0% and like the capability to run a node 00:11:51.839 --> 00:11:53.569 align:start position:0% and like the capability to run a node and<00:11:52.019> things<00:11:52.200> like<00:11:52.380> that<00:11:52.560> have<00:11:53.100> those<00:11:53.279> sort<00:11:53.459> of 00:11:53.569 --> 00:11:53.579 align:start position:0% and things like that have those sort of 00:11:53.579 --> 00:11:55.310 align:start position:0% and things like that have those sort of things<00:11:53.700> those<00:11:54.120> mutations<00:11:54.600> been<00:11:55.019> thought 00:11:55.310 --> 00:11:55.320 align:start position:0% things those mutations been thought 00:11:55.320 --> 00:11:59.569 align:start position:0% things those mutations been thought about<00:11:55.700> from<00:11:56.700> a<00:11:57.060> uh<00:11:57.600> you<00:11:57.899> know 00:11:59.569 --> 00:11:59.579 align:start position:0% about from a uh you know 00:11:59.579 --> 00:12:02.030 align:start position:0% about from a uh you know metrics<00:12:00.420> Gathering<00:12:00.839> level 00:12:02.030 --> 00:12:02.040 align:start position:0% metrics Gathering level 00:12:02.040 --> 00:12:03.170 align:start position:0% metrics Gathering level um I<00:12:02.279> mean<00:12:02.399> this<00:12:02.519> is<00:12:02.640> a<00:12:02.760> thing<00:12:02.880> that<00:12:03.000> like 00:12:03.170 --> 00:12:03.180 align:start position:0% um I mean this is a thing that like 00:12:03.180 --> 00:12:04.970 align:start position:0% um I mean this is a thing that like people<00:12:03.480> who<00:12:03.720> implement<00:12:04.019> this<00:12:04.260> like<00:12:04.500> think 00:12:04.970 --> 00:12:04.980 align:start position:0% people who implement this like think 00:12:04.980 --> 00:12:07.250 align:start position:0% people who implement this like think about<00:12:05.160> this<00:12:05.459> all<00:12:05.700> the<00:12:05.820> time 00:12:07.250 --> 00:12:07.260 align:start position:0% about this all the time 00:12:07.260 --> 00:12:10.310 align:start position:0% about this all the time um<00:12:07.320> like<00:12:07.980> I<00:12:08.880> mean<00:12:09.000> yes<00:12:09.540> because<00:12:09.779> we<00:12:09.959> hold<00:12:10.140> the 00:12:10.310 --> 00:12:10.320 align:start position:0% um like I mean yes because we hold the 00:12:10.320 --> 00:12:12.470 align:start position:0% um like I mean yes because we hold the whole<00:12:10.380> state<00:12:10.560> you<00:12:10.740> can<00:12:10.920> like<00:12:11.160> model<00:12:11.940> that<00:12:12.300> sort 00:12:12.470 --> 00:12:12.480 align:start position:0% whole state you can like model that sort 00:12:12.480 --> 00:12:14.329 align:start position:0% whole state you can like model that sort of<00:12:12.540> thing<00:12:12.720> I<00:12:12.959> think<00:12:13.140> a<00:12:13.320> lot<00:12:13.500> of<00:12:13.620> that<00:12:13.740> is<00:12:14.040> mostly 00:12:14.329 --> 00:12:14.339 align:start position:0% of thing I think a lot of that is mostly 00:12:14.339 --> 00:12:16.970 align:start position:0% of thing I think a lot of that is mostly about<00:12:14.519> gas<00:12:14.940> pricing<00:12:15.360> and<00:12:15.540> gas<00:12:15.660> accounting<00:12:16.200> and 00:12:16.970 --> 00:12:16.980 align:start position:0% about gas pricing and gas accounting and 00:12:16.980 --> 00:12:18.410 align:start position:0% about gas pricing and gas accounting and like<00:12:17.220> there<00:12:17.459> are<00:12:17.579> advantages<00:12:17.880> here<00:12:18.120> so<00:12:18.240> for 00:12:18.410 --> 00:12:18.420 align:start position:0% like there are advantages here so for 00:12:18.420 --> 00:12:20.690 align:start position:0% like there are advantages here so for example<00:12:18.600> there<00:12:18.779> was<00:12:18.959> a<00:12:19.079> proposal<00:12:19.500> about<00:12:20.459> how 00:12:20.690 --> 00:12:20.700 align:start position:0% example there was a proposal about how 00:12:20.700 --> 00:12:22.130 align:start position:0% example there was a proposal about how withdrawals<00:12:21.240> worked<00:12:21.540> because<00:12:21.779> I<00:12:21.959> have<00:12:22.019> the 00:12:22.130 --> 00:12:22.140 align:start position:0% withdrawals worked because I have the 00:12:22.140 --> 00:12:23.870 align:start position:0% withdrawals worked because I have the execution<00:12:22.440> specs<00:12:22.860> I<00:12:23.040> could<00:12:23.160> like<00:12:23.279> look<00:12:23.519> up<00:12:23.640> the 00:12:23.870 --> 00:12:23.880 align:start position:0% execution specs I could like look up the 00:12:23.880 --> 00:12:25.310 align:start position:0% execution specs I could like look up the table<00:12:24.000> of<00:12:24.180> gas<00:12:24.360> prices<00:12:24.540> in<00:12:24.839> the<00:12:24.959> execution<00:12:25.140> so 00:12:25.310 --> 00:12:25.320 align:start position:0% table of gas prices in the execution so 00:12:25.320 --> 00:12:26.449 align:start position:0% table of gas prices in the execution so I<00:12:25.440> can<00:12:25.500> say<00:12:25.620> well<00:12:25.800> this<00:12:25.920> is<00:12:26.040> how<00:12:26.160> much<00:12:26.279> this 00:12:26.449 --> 00:12:26.459 align:start position:0% I can say well this is how much this 00:12:26.459 --> 00:12:28.670 align:start position:0% I can say well this is how much this sort<00:12:26.579> of<00:12:26.700> thing<00:12:26.760> should<00:12:26.940> cost<00:12:27.120> and<00:12:28.019> like<00:12:28.260> yeah 00:12:28.670 --> 00:12:28.680 align:start position:0% sort of thing should cost and like yeah 00:12:28.680 --> 00:12:30.170 align:start position:0% sort of thing should cost and like yeah but<00:12:28.920> I<00:12:29.040> don't<00:12:29.160> I<00:12:29.279> don't<00:12:29.459> think<00:12:29.579> our<00:12:29.760> tool<00:12:30.120> is 00:12:30.170 --> 00:12:30.180 align:start position:0% but I don't I don't think our tool is 00:12:30.180 --> 00:12:31.430 align:start position:0% but I don't I don't think our tool is like<00:12:30.360> particularly<00:12:30.779> useful<00:12:31.079> for<00:12:31.260> like 00:12:31.430 --> 00:12:31.440 align:start position:0% like particularly useful for like 00:12:31.440 --> 00:12:33.350 align:start position:0% like particularly useful for like modeling<00:12:32.160> State<00:12:32.339> growth<00:12:32.700> particularly<00:12:33.120> you 00:12:33.350 --> 00:12:33.360 align:start position:0% modeling State growth particularly you 00:12:33.360 --> 00:12:34.730 align:start position:0% modeling State growth particularly you just<00:12:33.480> need<00:12:33.660> to<00:12:33.779> understand<00:12:33.959> like<00:12:34.440> What 00:12:34.730 --> 00:12:34.740 align:start position:0% just need to understand like What 00:12:34.740 --> 00:12:36.410 align:start position:0% just need to understand like What patients<00:12:35.220> can<00:12:35.339> cause<00:12:35.519> State<00:12:35.700> growth<00:12:36.120> and<00:12:36.240> how 00:12:36.410 --> 00:12:36.420 align:start position:0% patients can cause State growth and how 00:12:36.420 --> 00:12:38.329 align:start position:0% patients can cause State growth and how much<00:12:36.480> gas<00:12:36.720> those<00:12:36.959> could<00:12:37.140> those<00:12:37.440> cost 00:12:38.329 --> 00:12:38.339 align:start position:0% much gas those could those cost 00:12:38.339 --> 00:12:40.430 align:start position:0% much gas those could those cost how<00:12:38.880> is<00:12:39.060> this<00:12:39.180> going<00:12:39.360> to<00:12:39.480> interact<00:12:39.779> with<00:12:40.140> the 00:12:40.430 --> 00:12:40.440 align:start position:0% how is this going to interact with the 00:12:40.440 --> 00:12:44.090 align:start position:0% how is this going to interact with the reference<00:12:40.980> tests<00:12:41.640> that<00:12:42.360> the<00:12:42.959> eels<00:12:43.560> there's<00:12:43.920> a 00:12:44.090 --> 00:12:44.100 align:start position:0% reference tests that the eels there's a 00:12:44.100 --> 00:12:47.030 align:start position:0% reference tests that the eels there's a lot<00:12:44.220> of<00:12:44.399> crazy<00:12:44.880> edge<00:12:45.240> cases<00:12:45.779> in<00:12:46.680> reference 00:12:47.030 --> 00:12:47.040 align:start position:0% lot of crazy edge cases in reference 00:12:47.040 --> 00:12:50.870 align:start position:0% lot of crazy edge cases in reference tests<00:12:47.959> such<00:12:48.959> as<00:12:49.160> integer<00:12:50.160> boundaries<00:12:50.579> and 00:12:50.870 --> 00:12:50.880 align:start position:0% tests such as integer boundaries and 00:12:50.880 --> 00:12:53.150 align:start position:0% tests such as integer boundaries and other<00:12:51.120> strange<00:12:51.959> things 00:12:53.150 --> 00:12:53.160 align:start position:0% other strange things 00:12:53.160 --> 00:12:56.090 align:start position:0% other strange things oh<00:12:53.760> yeah<00:12:54.000> I<00:12:54.180> mean<00:12:54.360> I<00:12:54.600> I've<00:12:55.079> had<00:12:55.380> a<00:12:55.560> lot<00:12:55.740> of<00:12:55.860> fun 00:12:56.090 --> 00:12:56.100 align:start position:0% oh yeah I mean I I've had a lot of fun 00:12:56.100 --> 00:12:57.769 align:start position:0% oh yeah I mean I I've had a lot of fun with<00:12:56.339> crazy<00:12:56.519> edge<00:12:56.820> cases<00:12:57.120> I<00:12:57.300> should<00:12:57.420> do<00:12:57.540> a<00:12:57.660> talk 00:12:57.769 --> 00:12:57.779 align:start position:0% with crazy edge cases I should do a talk 00:12:57.779 --> 00:12:59.509 align:start position:0% with crazy edge cases I should do a talk on<00:12:57.959> Crazy<00:12:58.079> Edge<00:12:58.320> cases<00:12:58.680> once<00:12:59.040> they<00:12:59.220> at<00:12:59.339> some 00:12:59.509 --> 00:12:59.519 align:start position:0% on Crazy Edge cases once they at some 00:12:59.519 --> 00:13:02.030 align:start position:0% on Crazy Edge cases once they at some point<00:12:59.639> they<00:12:59.880> are<00:13:00.000> amazing<00:13:00.720> I<00:13:01.079> mean<00:13:01.200> firstly<00:13:01.560> we 00:13:02.030 --> 00:13:02.040 align:start position:0% point they are amazing I mean firstly we 00:13:02.040 --> 00:13:04.250 align:start position:0% point they are amazing I mean firstly we run<00:13:02.220> all<00:13:02.700> of<00:13:02.820> the<00:13:02.940> reference<00:13:03.240> tests<00:13:03.600> so<00:13:04.019> if<00:13:04.139> you 00:13:04.250 --> 00:13:04.260 align:start position:0% run all of the reference tests so if you 00:13:04.260 --> 00:13:07.610 align:start position:0% run all of the reference tests so if you go<00:13:04.440> in<00:13:04.620> our<00:13:04.800> test<00:13:05.040> Suite<00:13:05.459> you<00:13:05.700> type<00:13:05.880> talks<00:13:06.620> the 00:13:07.610 --> 00:13:07.620 align:start position:0% go in our test Suite you type talks the 00:13:07.620 --> 00:13:08.750 align:start position:0% go in our test Suite you type talks the automatic 00:13:08.750 --> 00:13:08.760 align:start position:0% automatic 00:13:08.760 --> 00:13:11.569 align:start position:0% automatic um<00:13:08.880> like<00:13:09.360> test<00:13:09.839> Suite<00:13:10.200> will<00:13:10.560> run<00:13:10.800> all<00:13:11.339> of<00:13:11.519> the 00:13:11.569 --> 00:13:11.579 align:start position:0% um like test Suite will run all of the 00:13:11.579 --> 00:13:13.730 align:start position:0% um like test Suite will run all of the reference<00:13:11.940> tests<00:13:12.360> and<00:13:12.779> So<00:13:12.899> currently<00:13:13.260> we<00:13:13.560> pass 00:13:13.730 --> 00:13:13.740 align:start position:0% reference tests and So currently we pass 00:13:13.740 --> 00:13:16.190 align:start position:0% reference tests and So currently we pass every<00:13:14.220> single<00:13:14.459> one<00:13:14.639> of<00:13:14.760> them<00:13:14.880> and<00:13:15.660> I<00:13:15.779> have<00:13:16.019> like 00:13:16.190 --> 00:13:16.200 align:start position:0% every single one of them and I have like 00:13:16.200 --> 00:13:17.569 align:start position:0% every single one of them and I have like learned<00:13:16.560> an<00:13:16.680> awful<00:13:16.920> lot<00:13:17.040> about<00:13:17.279> the<00:13:17.459> crazy 00:13:17.569 --> 00:13:17.579 align:start position:0% learned an awful lot about the crazy 00:13:17.579 --> 00:13:19.910 align:start position:0% learned an awful lot about the crazy edge<00:13:17.820> cases<00:13:18.180> of<00:13:18.360> the<00:13:18.540> VM<00:13:18.959> we<00:13:19.500> actually<00:13:19.620> hope<00:13:19.800> to 00:13:19.910 --> 00:13:19.920 align:start position:0% edge cases of the VM we actually hope to 00:13:19.920 --> 00:13:22.009 align:start position:0% edge cases of the VM we actually hope to confirm<00:13:20.339> that<00:13:20.459> you<00:13:20.700> know<00:13:20.820> we<00:13:21.000> want<00:13:21.180> to<00:13:21.420> be<00:13:21.600> the 00:13:22.009 --> 00:13:22.019 align:start position:0% confirm that you know we want to be the 00:13:22.019 --> 00:13:23.990 align:start position:0% confirm that you know we want to be the mechanical<00:13:22.380> builder<00:13:22.920> of<00:13:23.100> the<00:13:23.579> um<00:13:23.579> execution 00:13:23.990 --> 00:13:24.000 align:start position:0% mechanical builder of the um execution 00:13:24.000 --> 00:13:25.670 align:start position:0% mechanical builder of the um execution test<00:13:24.240> So<00:13:24.540> currently<00:13:24.959> for<00:13:25.200> those<00:13:25.440> who<00:13:25.560> are<00:13:25.620> not 00:13:25.670 --> 00:13:25.680 align:start position:0% test So currently for those who are not 00:13:25.680 --> 00:13:28.790 align:start position:0% test So currently for those who are not familiar<00:13:26.040> we<00:13:26.220> have<00:13:26.399> test<00:13:27.120> fillers 00:13:28.790 --> 00:13:28.800 align:start position:0% familiar we have test fillers 00:13:28.800 --> 00:13:31.009 align:start position:0% familiar we have test fillers um which<00:13:29.220> are<00:13:29.399> like<00:13:29.579> they're<00:13:30.480> not<00:13:30.600> like<00:13:30.839> a 00:13:31.009 --> 00:13:31.019 align:start position:0% um which are like they're not like a 00:13:31.019 --> 00:13:32.509 align:start position:0% um which are like they're not like a complete<00:13:31.320> test<00:13:31.380> they<00:13:31.680> say<00:13:31.800> here<00:13:32.040> is<00:13:32.160> what<00:13:32.399> the 00:13:32.509 --> 00:13:32.519 align:start position:0% complete test they say here is what the 00:13:32.519 --> 00:13:34.190 align:start position:0% complete test they say here is what the pre-state's<00:13:33.060> like<00:13:33.240> here<00:13:33.839> are<00:13:34.019> some 00:13:34.190 --> 00:13:34.200 align:start position:0% pre-state's like here are some 00:13:34.200 --> 00:13:35.449 align:start position:0% pre-state's like here are some assertions<00:13:34.680> about<00:13:34.860> what<00:13:35.040> it<00:13:35.160> should<00:13:35.279> be<00:13:35.339> like 00:13:35.449 --> 00:13:35.459 align:start position:0% assertions about what it should be like 00:13:35.459 --> 00:13:36.590 align:start position:0% assertions about what it should be like per<00:13:35.639> state 00:13:36.590 --> 00:13:36.600 align:start position:0% per state 00:13:36.600 --> 00:13:39.410 align:start position:0% per state then<00:13:37.139> you<00:13:37.680> run<00:13:37.860> you<00:13:38.279> take<00:13:38.519> a<00:13:38.639> client<00:13:39.240> um<00:13:39.300> it's 00:13:39.410 --> 00:13:39.420 align:start position:0% then you run you take a client um it's 00:13:39.420 --> 00:13:41.930 align:start position:0% then you run you take a client um it's usually<00:13:39.779> gef<00:13:40.200> and<00:13:40.860> you<00:13:40.980> run<00:13:41.220> a<00:13:41.579> filling 00:13:41.930 --> 00:13:41.940 align:start position:0% usually gef and you run a filling 00:13:41.940 --> 00:13:44.930 align:start position:0% usually gef and you run a filling process<00:13:42.300> that<00:13:42.540> gives<00:13:42.899> you<00:13:43.019> a<00:13:43.200> completed 00:13:44.930 --> 00:13:44.940 align:start position:0% process that gives you a completed 00:13:44.940 --> 00:13:47.329 align:start position:0% process that gives you a completed um<00:13:45.060> reference<00:13:45.600> test 00:13:47.329 --> 00:13:47.339 align:start position:0% um reference test 00:13:47.339 --> 00:13:49.610 align:start position:0% um reference test um<00:13:47.459> that<00:13:47.820> reference<00:13:48.139> reference<00:13:49.139> test<00:13:49.320> and<00:13:49.500> it 00:13:49.610 --> 00:13:49.620 align:start position:0% um that reference reference test and it 00:13:49.620 --> 00:13:50.750 align:start position:0% um that reference reference test and it tells<00:13:49.800> you<00:13:49.860> what<00:13:49.980> the<00:13:50.100> state<00:13:50.220> bridge<00:13:50.399> is<00:13:50.579> it 00:13:50.750 --> 00:13:50.760 align:start position:0% tells you what the state bridge is it 00:13:50.760 --> 00:13:52.009 align:start position:0% tells you what the state bridge is it tells<00:13:50.940> you<00:13:51.000> basically<00:13:51.360> exactly<00:13:51.720> what<00:13:51.839> the 00:13:52.009 --> 00:13:52.019 align:start position:0% tells you basically exactly what the 00:13:52.019 --> 00:13:53.210 align:start position:0% tells you basically exactly what the block<00:13:52.139> should<00:13:52.440> be<00:13:52.560> after<00:13:52.740> you<00:13:52.980> can<00:13:53.100> perform 00:13:53.210 --> 00:13:53.220 align:start position:0% block should be after you can perform 00:13:53.220 --> 00:13:54.769 align:start position:0% block should be after you can perform this<00:13:53.459> execution 00:13:54.769 --> 00:13:54.779 align:start position:0% this execution 00:13:54.779 --> 00:13:56.269 align:start position:0% this execution um we<00:13:55.019> will<00:13:55.139> think<00:13:55.320> that<00:13:55.500> we<00:13:55.800> should<00:13:55.920> be<00:13:56.100> like 00:13:56.269 --> 00:13:56.279 align:start position:0% um we will think that we should be like 00:13:56.279 --> 00:13:58.610 align:start position:0% um we will think that we should be like the<00:13:56.459> chemical<00:13:56.760> filler<00:13:57.240> of<00:13:57.360> those<00:13:57.480> tests<00:13:57.959> we 00:13:58.610 --> 00:13:58.620 align:start position:0% the chemical filler of those tests we 00:13:58.620 --> 00:14:01.069 align:start position:0% the chemical filler of those tests we can<00:13:58.740> fill<00:13:58.980> them<00:13:59.220> before<00:13:59.820> the<00:14:00.660> execution 00:14:01.069 --> 00:14:01.079 align:start position:0% can fill them before the execution 00:14:01.079 --> 00:14:04.670 align:start position:0% can fill them before the execution clients<00:14:01.500> had<00:14:01.680> even<00:14:01.860> implemented<00:14:02.579> those<00:14:02.760> tests 00:14:04.670 --> 00:14:04.680 align:start position:0% clients had even implemented those tests 00:14:04.680 --> 00:14:07.550 align:start position:0% clients had even implemented those tests um<00:14:04.740> and<00:14:05.220> then<00:14:05.339> we<00:14:05.639> can<00:14:05.820> if<00:14:06.600> you<00:14:06.720> want<00:14:06.959> to<00:14:07.139> and 00:14:07.550 --> 00:14:07.560 align:start position:0% um and then we can if you want to and 00:14:07.560 --> 00:14:08.930 align:start position:0% um and then we can if you want to and that<00:14:07.680> means<00:14:07.920> that<00:14:07.980> clients<00:14:08.339> can<00:14:08.459> like<00:14:08.579> use<00:14:08.760> the 00:14:08.930 --> 00:14:08.940 align:start position:0% that means that clients can like use the 00:14:08.940 --> 00:14:10.190 align:start position:0% that means that clients can like use the test<00:14:09.060> to<00:14:09.300> build<00:14:09.420> their<00:14:09.600> clients<00:14:09.839> whereas 00:14:10.190 --> 00:14:10.200 align:start position:0% test to build their clients whereas 00:14:10.200 --> 00:14:11.569 align:start position:0% test to build their clients whereas currently<00:14:10.440> until<00:14:10.800> you've<00:14:11.160> implemented 00:14:11.569 --> 00:14:11.579 align:start position:0% currently until you've implemented 00:14:11.579 --> 00:14:12.949 align:start position:0% currently until you've implemented something<00:14:11.760> you<00:14:12.240> can't<00:14:12.360> fill<00:14:12.540> the<00:14:12.660> reference 00:14:12.949 --> 00:14:12.959 align:start position:0% something you can't fill the reference 00:14:12.959 --> 00:14:14.690 align:start position:0% something you can't fill the reference tests<00:14:13.680> and<00:14:13.980> you<00:14:14.040> have<00:14:14.279> to<00:14:14.339> invent<00:14:14.579> a 00:14:14.690 --> 00:14:14.700 align:start position:0% tests and you have to invent a 00:14:14.700 --> 00:14:16.129 align:start position:0% tests and you have to invent a production<00:14:15.000> client 00:14:16.129 --> 00:14:16.139 align:start position:0% production client 00:14:16.139 --> 00:14:17.569 align:start position:0% production client um<00:14:16.260> there<00:14:16.560> is<00:14:16.680> also<00:14:16.920> and<00:14:17.100> I<00:14:17.279> haven't<00:14:17.399> thought 00:14:17.569 --> 00:14:17.579 align:start position:0% um there is also and I haven't thought 00:14:17.579 --> 00:14:20.269 align:start position:0% um there is also and I haven't thought about<00:14:17.700> in<00:14:18.060> great<00:14:18.240> detail<00:14:18.600> the<00:14:19.500> question<00:14:19.800> of 00:14:20.269 --> 00:14:20.279 align:start position:0% about in great detail the question of 00:14:20.279 --> 00:14:23.690 align:start position:0% about in great detail the question of whether<00:14:20.639> we<00:14:21.000> should<00:14:21.180> use<00:14:21.560> the<00:14:22.560> whether<00:14:23.339> we<00:14:23.519> can 00:14:23.690 --> 00:14:23.700 align:start position:0% whether we should use the whether we can 00:14:23.700 --> 00:14:26.930 align:start position:0% whether we should use the whether we can like<00:14:23.940> analyze<00:14:24.720> the<00:14:25.019> structure<00:14:25.500> of<00:14:26.459> the 00:14:26.930 --> 00:14:26.940 align:start position:0% like analyze the structure of the 00:14:26.940 --> 00:14:29.930 align:start position:0% like analyze the structure of the alleles<00:14:27.500> to<00:14:28.500> like<00:14:28.860> generate<00:14:29.339> new<00:14:29.579> reference 00:14:29.930 --> 00:14:29.940 align:start position:0% alleles to like generate new reference 00:14:29.940 --> 00:14:32.090 align:start position:0% alleles to like generate new reference tests<00:14:30.360> and<00:14:30.839> basically<00:14:31.200> do<00:14:31.440> some<00:14:31.620> sort<00:14:31.800> of<00:14:31.920> path 00:14:32.090 --> 00:14:32.100 align:start position:0% tests and basically do some sort of path 00:14:32.100 --> 00:14:33.410 align:start position:0% tests and basically do some sort of path analysis<00:14:32.700> and<00:14:32.820> say<00:14:33.000> well<00:14:33.120> these<00:14:33.240> are<00:14:33.360> the 00:14:33.410 --> 00:14:33.420 align:start position:0% analysis and say well these are the 00:14:33.420 --> 00:14:35.690 align:start position:0% analysis and say well these are the possible<00:14:33.660> parts<00:14:33.959> of<00:14:34.260> this<00:14:34.620> sort<00:14:35.160> of<00:14:35.279> code<00:14:35.459> base 00:14:35.690 --> 00:14:35.700 align:start position:0% possible parts of this sort of code base 00:14:35.700 --> 00:14:37.910 align:start position:0% possible parts of this sort of code base can<00:14:36.300> we<00:14:36.420> follow<00:14:36.660> every<00:14:37.019> possible<00:14:37.380> path<00:14:37.680> and 00:14:37.910 --> 00:14:37.920 align:start position:0% can we follow every possible path and 00:14:37.920 --> 00:14:39.170 align:start position:0% can we follow every possible path and make<00:14:38.040> sure<00:14:38.160> there's<00:14:38.339> a<00:14:38.579> reference<00:14:38.820> test<00:14:39.000> that 00:14:39.170 --> 00:14:39.180 align:start position:0% make sure there's a reference test that 00:14:39.180 --> 00:14:40.730 align:start position:0% make sure there's a reference test that follows<00:14:39.480> every<00:14:39.720> possible<00:14:40.079> path<00:14:40.320> but<00:14:40.620> that's 00:14:40.730 --> 00:14:40.740 align:start position:0% follows every possible path but that's 00:14:40.740 --> 00:14:44.509 align:start position:0% follows every possible path but that's like<00:14:40.980> r<00:14:41.639> d<00:14:41.820> that<00:14:42.120> we<00:14:42.300> like<00:14:42.480> haven't<00:14:43.199> done<00:14:43.500> yet 00:14:44.509 --> 00:14:44.519 align:start position:0% like r d that we like haven't done yet 00:14:44.519 --> 00:14:47.629 align:start position:0% like r d that we like haven't done yet you<00:14:45.300> mentioned<00:14:45.660> you<00:14:46.139> implemented 00:14:47.629 --> 00:14:47.639 align:start position:0% you mentioned you implemented 00:14:47.639 --> 00:14:50.329 align:start position:0% you mentioned you implemented no<00:14:48.120> you<00:14:48.420> care<00:14:48.899> only<00:14:49.199> about<00:14:49.440> State<00:14:49.860> transition 00:14:50.329 --> 00:14:50.339 align:start position:0% no you care only about State transition 00:14:50.339 --> 00:14:53.629 align:start position:0% no you care only about State transition function<00:14:51.139> and<00:14:52.139> that<00:14:52.620> means<00:14:52.860> you<00:14:53.040> implemented 00:14:53.629 --> 00:14:53.639 align:start position:0% function and that means you implemented 00:14:53.639 --> 00:14:56.750 align:start position:0% function and that means you implemented your<00:14:54.060> own<00:14:54.240> evm<00:14:54.839> and<00:14:55.500> you<00:14:55.800> can<00:14:56.040> fill<00:14:56.279> the<00:14:56.519> test 00:14:56.750 --> 00:14:56.760 align:start position:0% your own evm and you can fill the test 00:14:56.760 --> 00:14:58.430 align:start position:0% your own evm and you can fill the test and<00:14:57.480> and 00:14:58.430 --> 00:14:58.440 align:start position:0% and and 00:14:58.440 --> 00:15:02.569 align:start position:0% and and you<00:14:59.279> provide<00:14:59.699> the<00:15:00.060> post<00:15:00.660> State<00:15:01.079> hash<00:15:01.579> yeah 00:15:02.569 --> 00:15:02.579 align:start position:0% you provide the post State hash yeah 00:15:02.579 --> 00:15:05.810 align:start position:0% you provide the post State hash yeah like<00:15:02.959> if<00:15:03.959> you<00:15:04.079> have<00:15:04.199> a<00:15:04.380> chain<00:15:04.680> and<00:15:05.339> you<00:15:05.459> want<00:15:05.639> if 00:15:05.810 --> 00:15:05.820 align:start position:0% like if you have a chain and you want if 00:15:05.820 --> 00:15:08.150 align:start position:0% like if you have a chain and you want if you<00:15:05.940> have<00:15:06.060> a<00:15:06.240> chain<00:15:06.480> and<00:15:07.440> you<00:15:07.680> want<00:15:07.800> and<00:15:08.040> you 00:15:08.150 --> 00:15:08.160 align:start position:0% you have a chain and you want and you 00:15:08.160 --> 00:15:10.670 align:start position:0% you have a chain and you want and you have<00:15:08.579> a<00:15:08.639> block<00:15:08.760> and<00:15:09.060> your<00:15:09.180> proposal<00:15:09.660> is<00:15:09.839> to<00:15:10.019> add 00:15:10.670 --> 00:15:10.680 align:start position:0% have a block and your proposal is to add 00:15:10.680 --> 00:15:12.590 align:start position:0% have a block and your proposal is to add that<00:15:11.100> block<00:15:11.339> to<00:15:11.579> the<00:15:11.699> end<00:15:11.820> of<00:15:11.940> that<00:15:12.120> chain<00:15:12.300> and 00:15:12.590 --> 00:15:12.600 align:start position:0% that block to the end of that chain and 00:15:12.600 --> 00:15:15.350 align:start position:0% that block to the end of that chain and update<00:15:12.959> the<00:15:13.139> state<00:15:13.320> we<00:15:14.220> can<00:15:14.399> tell<00:15:14.639> you<00:15:14.760> we<00:15:15.120> our 00:15:15.350 --> 00:15:15.360 align:start position:0% update the state we can tell you we our 00:15:15.360 --> 00:15:17.569 align:start position:0% update the state we can tell you we our tests<00:15:15.720> specify<00:15:16.139> exact<00:15:16.500> our<00:15:16.860> thing<00:15:17.160> specifies 00:15:17.569 --> 00:15:17.579 align:start position:0% tests specify exact our thing specifies 00:15:17.579 --> 00:15:19.129 align:start position:0% tests specify exact our thing specifies exactly 00:15:19.129 --> 00:15:19.139 align:start position:0% exactly 00:15:19.139 --> 00:15:21.050 align:start position:0% exactly um whether<00:15:19.920> that<00:15:20.100> block<00:15:20.220> is<00:15:20.459> valid<00:15:20.699> are<00:15:20.940> you 00:15:21.050 --> 00:15:21.060 align:start position:0% um whether that block is valid are you 00:15:21.060 --> 00:15:22.610 align:start position:0% um whether that block is valid are you allowed<00:15:21.300> to<00:15:21.360> do<00:15:21.540> that<00:15:21.600> because<00:15:21.779> blocks 00:15:22.610 --> 00:15:22.620 align:start position:0% allowed to do that because blocks 00:15:22.620 --> 00:15:23.810 align:start position:0% allowed to do that because blocks something<00:15:22.680> to<00:15:22.860> take<00:15:22.980> advantage<00:15:23.279> tend<00:15:23.639> to<00:15:23.699> be 00:15:23.810 --> 00:15:23.820 align:start position:0% something to take advantage tend to be 00:15:23.820 --> 00:15:25.550 align:start position:0% something to take advantage tend to be invalid<00:15:24.779> um<00:15:24.839> in<00:15:25.019> that<00:15:25.079> case<00:15:25.199> you're<00:15:25.320> just<00:15:25.440> not 00:15:25.550 --> 00:15:25.560 align:start position:0% invalid um in that case you're just not 00:15:25.560 --> 00:15:26.870 align:start position:0% invalid um in that case you're just not allowed<00:15:25.800> to<00:15:25.860> do<00:15:25.920> it<00:15:26.040> and<00:15:26.160> if<00:15:26.279> it<00:15:26.399> is<00:15:26.459> valid<00:15:26.760> it 00:15:26.870 --> 00:15:26.880 align:start position:0% allowed to do it and if it is valid it 00:15:26.880 --> 00:15:29.810 align:start position:0% allowed to do it and if it is valid it tells<00:15:27.180> you<00:15:27.300> what<00:15:27.839> the<00:15:28.019> state<00:15:28.260> changes<00:15:28.920> are<00:15:29.160> and 00:15:29.810 --> 00:15:29.820 align:start position:0% tells you what the state changes are and 00:15:29.820 --> 00:15:31.310 align:start position:0% tells you what the state changes are and then<00:15:29.940> you<00:15:30.060> can<00:15:30.180> do<00:15:30.300> the<00:15:30.480> next<00:15:30.600> thing<00:15:30.779> we<00:15:31.199> don't 00:15:31.310 --> 00:15:31.320 align:start position:0% then you can do the next thing we don't 00:15:31.320 --> 00:15:32.449 align:start position:0% then you can do the next thing we don't do<00:15:31.500> anything<00:15:31.620> else<00:15:31.800> that's<00:15:32.040> the<00:15:32.279> only 00:15:32.449 --> 00:15:32.459 align:start position:0% do anything else that's the only 00:15:32.459 --> 00:15:34.610 align:start position:0% do anything else that's the only question<00:15:32.699> we<00:15:33.000> answer 00:15:34.610 --> 00:15:34.620 align:start position:0% question we answer 00:15:34.620 --> 00:15:37.850 align:start position:0% question we answer um<00:15:34.680> so<00:15:35.040> this<00:15:35.279> is<00:15:35.399> obviously<00:15:35.940> uh<00:15:36.899> inspired<00:15:37.560> by 00:15:37.850 --> 00:15:37.860 align:start position:0% um so this is obviously uh inspired by 00:15:37.860 --> 00:15:40.850 align:start position:0% um so this is obviously uh inspired by the<00:15:38.160> consensus<00:15:38.639> specs<00:15:39.120> or<00:15:39.720> the<00:15:39.899> pi<00:15:40.139> spec<00:15:40.380> are 00:15:40.850 --> 00:15:40.860 align:start position:0% the consensus specs or the pi spec are 00:15:40.860 --> 00:15:42.769 align:start position:0% the consensus specs or the pi spec are there<00:15:41.040> any<00:15:41.220> particular<00:15:41.779> architecture 00:15:42.769 --> 00:15:42.779 align:start position:0% there any particular architecture 00:15:42.779 --> 00:15:46.009 align:start position:0% there any particular architecture changes<00:15:43.320> or<00:15:43.620> learnings<00:15:44.100> you've<00:15:44.760> gotten<00:15:45.420> from 00:15:46.009 --> 00:15:46.019 align:start position:0% changes or learnings you've gotten from 00:15:46.019 --> 00:15:48.290 align:start position:0% changes or learnings you've gotten from the<00:15:46.440> pi<00:15:46.680> specs<00:15:47.160> oh<00:15:47.519> yeah<00:15:47.639> that's<00:15:47.880> a<00:15:48.000> really 00:15:48.290 --> 00:15:48.300 align:start position:0% the pi specs oh yeah that's a really 00:15:48.300 --> 00:15:50.090 align:start position:0% the pi specs oh yeah that's a really good<00:15:48.420> question<00:15:48.600> okay<00:15:49.019> so<00:15:49.440> there's<00:15:49.860> a<00:15:49.980> couple 00:15:50.090 --> 00:15:50.100 align:start position:0% good question okay so there's a couple 00:15:50.100 --> 00:15:51.650 align:start position:0% good question okay so there's a couple of<00:15:50.220> different<00:15:50.399> tiers<00:15:50.880> here 00:15:51.650 --> 00:15:51.660 align:start position:0% of different tiers here 00:15:51.660 --> 00:15:53.269 align:start position:0% of different tiers here um the<00:15:52.019> first<00:15:52.139> one 00:15:53.269 --> 00:15:53.279 align:start position:0% um the first one 00:15:53.279 --> 00:15:55.490 align:start position:0% um the first one um<00:15:53.399> is<00:15:53.760> that<00:15:54.120> the 00:15:55.490 --> 00:15:55.500 align:start position:0% um is that the 00:15:55.500 --> 00:15:58.009 align:start position:0% um is that the um<00:15:55.560> Pi<00:15:56.160> spec<00:15:56.459> is<00:15:57.300> you<00:15:57.540> connected<00:15:57.899> to<00:15:57.959> this 00:15:58.009 --> 00:15:58.019 align:start position:0% um Pi spec is you connected to this 00:15:58.019 --> 00:16:01.910 align:start position:0% um Pi spec is you connected to this price<00:15:58.139> spec<00:15:58.380> is<00:15:59.220> a<00:16:00.060> document 00:16:01.910 --> 00:16:01.920 align:start position:0% price spec is a document 00:16:01.920 --> 00:16:04.250 align:start position:0% price spec is a document um<00:16:01.980> that<00:16:02.579> can<00:16:02.820> be<00:16:03.060> it<00:16:03.360> is<00:16:03.600> a<00:16:04.019> bunch<00:16:04.139> of 00:16:04.250 --> 00:16:04.260 align:start position:0% um that can be it is a bunch of 00:16:04.260 --> 00:16:06.350 align:start position:0% um that can be it is a bunch of documentation<00:16:04.740> that<00:16:05.100> can<00:16:05.279> be<00:16:05.639> compiled<00:16:06.240> to 00:16:06.350 --> 00:16:06.360 align:start position:0% documentation that can be compiled to 00:16:06.360 --> 00:16:09.350 align:start position:0% documentation that can be compiled to code<00:16:06.680> so<00:16:07.680> if<00:16:07.800> you<00:16:07.920> look<00:16:08.040> at<00:16:08.279> the<00:16:08.579> pi<00:16:08.940> spec<00:16:09.120> it's 00:16:09.350 --> 00:16:09.360 align:start position:0% code so if you look at the pi spec it's 00:16:09.360 --> 00:16:10.850 align:start position:0% code so if you look at the pi spec it's a<00:16:09.540> bunch<00:16:09.600> of<00:16:09.660> MD<00:16:09.959> files<00:16:10.260> with<00:16:10.380> some<00:16:10.500> code<00:16:10.680> in 00:16:10.850 --> 00:16:10.860 align:start position:0% a bunch of MD files with some code in 00:16:10.860 --> 00:16:12.290 align:start position:0% a bunch of MD files with some code in then<00:16:11.040> there's<00:16:11.220> a<00:16:11.399> compilation<00:16:11.760> process<00:16:12.120> that 00:16:12.290 --> 00:16:12.300 align:start position:0% then there's a compilation process that 00:16:12.300 --> 00:16:16.610 align:start position:0% then there's a compilation process that spits<00:16:12.660> out<00:16:12.720> code<00:16:13.339> we<00:16:14.339> are<00:16:14.519> a<00:16:14.699> bunch<00:16:14.880> of<00:16:15.000> code 00:16:16.610 --> 00:16:16.620 align:start position:0% spits out code we are a bunch of code 00:16:16.620 --> 00:16:18.350 align:start position:0% spits out code we are a bunch of code um<00:16:16.740> that<00:16:17.160> is 00:16:18.350 --> 00:16:18.360 align:start position:0% um that is 00:16:18.360 --> 00:16:19.910 align:start position:0% um that is um<00:16:18.480> we<00:16:18.779> can<00:16:18.899> then<00:16:19.019> you<00:16:19.199> can<00:16:19.320> then<00:16:19.440> compile 00:16:19.910 --> 00:16:19.920 align:start position:0% um we can then you can then compile 00:16:19.920 --> 00:16:21.889 align:start position:0% um we can then you can then compile using<00:16:20.279> standard<00:16:20.699> documentation<00:16:21.180> tools<00:16:21.540> to 00:16:21.889 --> 00:16:21.899 align:start position:0% using standard documentation tools to 00:16:21.899 --> 00:16:23.870 align:start position:0% using standard documentation tools to documentation 00:16:23.870 --> 00:16:23.880 align:start position:0% documentation 00:16:23.880 --> 00:16:26.269 align:start position:0% documentation um the<00:16:24.720> second<00:16:24.779> big<00:16:25.079> change<00:16:25.320> if<00:16:25.620> the<00:16:25.860> pi<00:16:26.100> spec 00:16:26.269 --> 00:16:26.279 align:start position:0% um the second big change if the pi spec 00:16:26.279 --> 00:16:27.710 align:start position:0% um the second big change if the pi spec does<00:16:26.579> this<00:16:26.760> like<00:16:26.940> incremental<00:16:27.480> building 00:16:27.710 --> 00:16:27.720 align:start position:0% does this like incremental building 00:16:27.720 --> 00:16:30.110 align:start position:0% does this like incremental building stage<00:16:28.199> where 00:16:30.110 --> 00:16:30.120 align:start position:0% stage where 00:16:30.120 --> 00:16:32.269 align:start position:0% stage where um<00:16:30.180> in<00:16:30.660> the<00:16:30.779> price<00:16:30.899> spec<00:16:31.199> you<00:16:31.380> have<00:16:31.500> phase<00:16:31.860> zero 00:16:32.269 --> 00:16:32.279 align:start position:0% um in the price spec you have phase zero 00:16:32.279 --> 00:16:34.129 align:start position:0% um in the price spec you have phase zero and<00:16:32.699> then<00:16:32.820> you<00:16:32.940> have<00:16:33.120> outer<00:16:33.420> and<00:16:33.540> the<00:16:33.600> out<00:16:33.720> her 00:16:34.129 --> 00:16:34.139 align:start position:0% and then you have outer and the out her 00:16:34.139 --> 00:16:36.230 align:start position:0% and then you have outer and the out her documentation<00:16:34.680> just<00:16:35.040> adds<00:16:35.459> a<00:16:35.639> few<00:16:35.760> changes<00:16:36.120> to 00:16:36.230 --> 00:16:36.240 align:start position:0% documentation just adds a few changes to 00:16:36.240 --> 00:16:38.509 align:start position:0% documentation just adds a few changes to the<00:16:36.360> face<00:16:36.480> hero<00:16:36.899> whereas<00:16:37.680> what<00:16:37.860> we<00:16:37.980> did<00:16:38.160> was<00:16:38.339> we 00:16:38.509 --> 00:16:38.519 align:start position:0% the face hero whereas what we did was we 00:16:38.519 --> 00:16:41.930 align:start position:0% the face hero whereas what we did was we copied<00:16:39.000> we<00:16:39.360> copy<00:16:39.720> the<00:16:39.959> entire<00:16:40.320> thing<00:16:40.940> and 00:16:41.930 --> 00:16:41.940 align:start position:0% copied we copy the entire thing and 00:16:41.940 --> 00:16:43.970 align:start position:0% copied we copy the entire thing and create<00:16:42.420> a<00:16:42.720> new<00:16:42.899> version<00:16:43.199> that<00:16:43.620> contains 00:16:43.970 --> 00:16:43.980 align:start position:0% create a new version that contains 00:16:43.980 --> 00:16:45.710 align:start position:0% create a new version that contains everything<00:16:44.160> which<00:16:44.880> means<00:16:45.180> because<00:16:45.420> otherwise 00:16:45.710 --> 00:16:45.720 align:start position:0% everything which means because otherwise 00:16:45.720 --> 00:16:47.090 align:start position:0% everything which means because otherwise what<00:16:45.959> would<00:16:46.079> happen<00:16:46.259> is<00:16:46.500> if<00:16:46.620> you<00:16:46.740> wanted<00:16:46.860> to 00:16:47.090 --> 00:16:47.100 align:start position:0% what would happen is if you wanted to 00:16:47.100 --> 00:16:48.410 align:start position:0% what would happen is if you wanted to know<00:16:47.279> how 00:16:48.410 --> 00:16:48.420 align:start position:0% know how 00:16:48.420 --> 00:16:50.810 align:start position:0% know how um<00:16:48.480> the<00:16:48.899> merge<00:16:49.199> worked<00:16:49.620> in<00:16:50.160> Paris<00:16:50.399> Works<00:16:50.639> you'd 00:16:50.810 --> 00:16:50.820 align:start position:0% um the merge worked in Paris Works you'd 00:16:50.820 --> 00:16:52.189 align:start position:0% um the merge worked in Paris Works you'd have<00:16:50.940> to<00:16:51.000> read<00:16:51.120> Paris<00:16:51.540> which<00:16:51.720> would<00:16:51.779> say<00:16:51.959> these 00:16:52.189 --> 00:16:52.199 align:start position:0% have to read Paris which would say these 00:16:52.199 --> 00:16:55.069 align:start position:0% have to read Paris which would say these are<00:16:52.320> the<00:16:52.380> changes<00:16:52.980> versus<00:16:53.160> London<00:16:53.959> and<00:16:54.959> then 00:16:55.069 --> 00:16:55.079 align:start position:0% are the changes versus London and then 00:16:55.079 --> 00:16:56.389 align:start position:0% are the changes versus London and then London<00:16:55.620> would<00:16:55.740> say<00:16:55.920> well<00:16:56.040> these<00:16:56.220> are<00:16:56.279> the 00:16:56.389 --> 00:16:56.399 align:start position:0% London would say well these are the 00:16:56.399 --> 00:16:58.129 align:start position:0% London would say well these are the changes<00:16:56.639> versus<00:16:56.820> Berlin<00:16:57.300> then<00:16:57.540> Berlin<00:16:57.899> would 00:16:58.129 --> 00:16:58.139 align:start position:0% changes versus Berlin then Berlin would 00:16:58.139 --> 00:16:59.210 align:start position:0% changes versus Berlin then Berlin would say<00:16:58.259> well<00:16:58.380> these<00:16:58.560> are<00:16:58.680> the<00:16:58.740> changes<00:16:58.980> versus 00:16:59.210 --> 00:16:59.220 align:start position:0% say well these are the changes versus 00:16:59.220 --> 00:17:00.949 align:start position:0% say well these are the changes versus istanbula<00:17:00.000> it'll<00:17:00.180> just<00:17:00.300> keep<00:17:00.420> going<00:17:00.600> on<00:17:00.779> and 00:17:00.949 --> 00:17:00.959 align:start position:0% istanbula it'll just keep going on and 00:17:00.959 --> 00:17:02.990 align:start position:0% istanbula it'll just keep going on and on<00:17:01.139> and<00:17:01.860> so<00:17:02.100> we<00:17:02.339> don't<00:17:02.519> think<00:17:02.699> that's<00:17:02.820> a 00:17:02.990 --> 00:17:03.000 align:start position:0% on and so we don't think that's a 00:17:03.000 --> 00:17:04.130 align:start position:0% on and so we don't think that's a particularly<00:17:03.240> good<00:17:03.420> way<00:17:03.540> especially<00:17:03.959> because 00:17:04.130 --> 00:17:04.140 align:start position:0% particularly good way especially because 00:17:04.140 --> 00:17:05.990 align:start position:0% particularly good way especially because a<00:17:04.380> lot<00:17:04.500> of<00:17:04.679> the<00:17:04.860> historical<00:17:05.459> details<00:17:05.939> are 00:17:05.990 --> 00:17:06.000 align:start position:0% a lot of the historical details are 00:17:06.000 --> 00:17:07.549 align:start position:0% a lot of the historical details are really<00:17:06.179> quite<00:17:06.360> Legacy<00:17:06.839> and<00:17:06.959> not<00:17:07.140> things<00:17:07.380> that 00:17:07.549 --> 00:17:07.559 align:start position:0% really quite Legacy and not things that 00:17:07.559 --> 00:17:08.929 align:start position:0% really quite Legacy and not things that people<00:17:08.040> need<00:17:08.280> to<00:17:08.400> be<00:17:08.459> concerned<00:17:08.819> with 00:17:08.929 --> 00:17:08.939 align:start position:0% people need to be concerned with 00:17:08.939 --> 00:17:10.909 align:start position:0% people need to be concerned with nowadays<00:17:09.419> because<00:17:09.600> they've<00:17:09.959> been<00:17:10.140> changed 00:17:10.909 --> 00:17:10.919 align:start position:0% nowadays because they've been changed 00:17:10.919 --> 00:17:15.110 align:start position:0% nowadays because they've been changed out<00:17:11.299> and<00:17:12.299> so<00:17:12.660> we<00:17:13.260> just<00:17:14.220> like<00:17:14.400> do<00:17:14.579> isolate 00:17:15.110 --> 00:17:15.120 align:start position:0% out and so we just like do isolate 00:17:15.120 --> 00:17:16.370 align:start position:0% out and so we just like do isolate they're<00:17:15.240> completely<00:17:15.540> isolated<00:17:15.900> files<00:17:16.260> this 00:17:16.370 --> 00:17:16.380 align:start position:0% they're completely isolated files this 00:17:16.380 --> 00:17:17.809 align:start position:0% they're completely isolated files this cause<00:17:16.559> like<00:17:16.860> a<00:17:17.280> whole<00:17:17.339> bunch<00:17:17.459> of<00:17:17.579> code 00:17:17.809 --> 00:17:17.819 align:start position:0% cause like a whole bunch of code 00:17:17.819 --> 00:17:20.929 align:start position:0% cause like a whole bunch of code duplication<00:17:18.360> issues<00:17:18.780> and<00:17:19.740> complexity<00:17:20.339> but<00:17:20.819> it 00:17:20.929 --> 00:17:20.939 align:start position:0% duplication issues and complexity but it 00:17:20.939 --> 00:17:24.289 align:start position:0% duplication issues and complexity but it does<00:17:21.059> mean<00:17:21.299> it's<00:17:21.540> like<00:17:21.780> really<00:17:22.939> simple<00:17:23.939> you 00:17:24.289 --> 00:17:24.299 align:start position:0% does mean it's like really simple you 00:17:24.299 --> 00:17:26.630 align:start position:0% does mean it's like really simple you can<00:17:24.419> read<00:17:24.660> a<00:17:25.199> particular<00:17:25.500> Fork<00:17:26.100> completely<00:17:26.459> in 00:17:26.630 --> 00:17:26.640 align:start position:0% can read a particular Fork completely in 00:17:26.640 --> 00:17:28.669 align:start position:0% can read a particular Fork completely in isolation<00:17:26.939> from<00:17:27.240> any<00:17:27.360> other<00:17:27.540> Fork<00:17:27.900> whereas<00:17:28.500> if 00:17:28.669 --> 00:17:28.679 align:start position:0% isolation from any other Fork whereas if 00:17:28.679 --> 00:17:30.230 align:start position:0% isolation from any other Fork whereas if you<00:17:28.799> can't<00:17:29.280> do<00:17:29.460> that<00:17:29.520> with<00:17:29.700> the<00:17:29.820> consensus 00:17:30.230 --> 00:17:30.240 align:start position:0% you can't do that with the consensus 00:17:30.240 --> 00:17:33.470 align:start position:0% you can't do that with the consensus face<00:17:30.480> I<00:17:31.140> was<00:17:31.320> wondering<00:17:31.860> for<00:17:32.520> the<00:17:32.700> executables 00:17:33.470 --> 00:17:33.480 align:start position:0% face I was wondering for the executables 00:17:33.480 --> 00:17:36.350 align:start position:0% face I was wondering for the executables back<00:17:33.679> how<00:17:34.679> do<00:17:34.799> you<00:17:34.919> think<00:17:35.100> it<00:17:35.700> might<00:17:36.000> change 00:17:36.350 --> 00:17:36.360 align:start position:0% back how do you think it might change 00:17:36.360 --> 00:17:39.409 align:start position:0% back how do you think it might change and<00:17:36.780> improve<00:17:37.200> like<00:17:37.500> the<00:17:37.679> eeip<00:17:38.160> process<00:17:38.760> of 00:17:39.409 --> 00:17:39.419 align:start position:0% and improve like the eeip process of 00:17:39.419 --> 00:17:41.810 align:start position:0% and improve like the eeip process of ethereum<00:17:40.020> there<00:17:40.559> was<00:17:40.679> lots<00:17:41.100> of<00:17:41.160> conversation 00:17:41.810 --> 00:17:41.820 align:start position:0% ethereum there was lots of conversation 00:17:41.820 --> 00:17:43.909 align:start position:0% ethereum there was lots of conversation in<00:17:42.419> terms<00:17:42.660> of<00:17:42.780> governance<00:17:43.260> of<00:17:43.500> how<00:17:43.740> when 00:17:43.909 --> 00:17:43.919 align:start position:0% in terms of governance of how when 00:17:43.919 --> 00:17:46.370 align:start position:0% in terms of governance of how when you're<00:17:44.100> proposing<00:17:44.580> an<00:17:44.820> EIP<00:17:45.179> maybe<00:17:46.020> this 00:17:46.370 --> 00:17:46.380 align:start position:0% you're proposing an EIP maybe this 00:17:46.380 --> 00:17:48.230 align:start position:0% you're proposing an EIP maybe this should<00:17:46.559> be<00:17:46.679> like<00:17:46.919> a<00:17:47.160> requirement<00:17:47.640> to<00:17:48.000> kind<00:17:48.179> of 00:17:48.230 --> 00:17:48.240 align:start position:0% should be like a requirement to kind of 00:17:48.240 --> 00:17:50.930 align:start position:0% should be like a requirement to kind of speed<00:17:48.419> up<00:17:48.720> the<00:17:49.020> testing<00:17:49.440> process<00:17:49.919> but<00:17:50.700> would 00:17:50.930 --> 00:17:50.940 align:start position:0% speed up the testing process but would 00:17:50.940 --> 00:17:52.789 align:start position:0% speed up the testing process but would love<00:17:51.299> to<00:17:51.480> hear<00:17:51.660> your<00:17:51.900> thoughts<00:17:52.260> on<00:17:52.380> how<00:17:52.679> it 00:17:52.789 --> 00:17:52.799 align:start position:0% love to hear your thoughts on how it 00:17:52.799 --> 00:17:54.890 align:start position:0% love to hear your thoughts on how it could<00:17:52.980> be<00:17:53.160> integrated<00:17:53.700> and<00:17:54.120> what<00:17:54.299> parts<00:17:54.480> of<00:17:54.720> it 00:17:54.890 --> 00:17:54.900 align:start position:0% could be integrated and what parts of it 00:17:54.900 --> 00:17:58.850 align:start position:0% could be integrated and what parts of it it<00:17:55.080> could<00:17:55.260> improve<00:17:56.120> to<00:17:57.120> change<00:17:57.539> that<00:17:58.020> that<00:17:58.260> EIP 00:17:58.850 --> 00:17:58.860 align:start position:0% it could improve to change that that EIP 00:17:58.860 --> 00:18:01.490 align:start position:0% it could improve to change that that EIP flow<00:17:59.580> so<00:18:00.240> on<00:18:00.539> the<00:18:00.720> one<00:18:00.840> so<00:18:01.080> there<00:18:01.260> are<00:18:01.380> some 00:18:01.490 --> 00:18:01.500 align:start position:0% flow so on the one so there are some 00:18:01.500 --> 00:18:04.130 align:start position:0% flow so on the one so there are some people<00:18:02.059> who<00:18:03.059> think<00:18:03.240> that<00:18:03.480> we<00:18:03.600> should<00:18:03.720> get<00:18:03.960> rid 00:18:04.130 --> 00:18:04.140 align:start position:0% people who think that we should get rid 00:18:04.140 --> 00:18:07.850 align:start position:0% people who think that we should get rid of<00:18:04.320> the<00:18:04.380> EIP<00:18:04.679> process<00:18:05.299> for<00:18:06.299> the<00:18:07.020> execution 00:18:07.850 --> 00:18:07.860 align:start position:0% of the EIP process for the execution 00:18:07.860 --> 00:18:10.190 align:start position:0% of the EIP process for the execution layer<00:18:08.220> we<00:18:08.460> should<00:18:08.580> have<00:18:08.760> bullish<00:18:09.179> erp's<00:18:10.080> the 00:18:10.190 --> 00:18:10.200 align:start position:0% layer we should have bullish erp's the 00:18:10.200 --> 00:18:11.810 align:start position:0% layer we should have bullish erp's the execution<00:18:10.500> layer<00:18:10.860> instead<00:18:11.280> you<00:18:11.460> should<00:18:11.640> have 00:18:11.810 --> 00:18:11.820 align:start position:0% execution layer instead you should have 00:18:11.820 --> 00:18:14.450 align:start position:0% execution layer instead you should have whatever<00:18:12.320> eels<00:18:13.320> proposals<00:18:13.919> are<00:18:13.980> coordination 00:18:14.450 --> 00:18:14.460 align:start position:0% whatever eels proposals are coordination 00:18:14.460 --> 00:18:15.770 align:start position:0% whatever eels proposals are coordination just<00:18:14.640> if<00:18:14.880> you<00:18:14.940> want<00:18:15.059> to<00:18:15.120> change<00:18:15.240> the<00:18:15.419> execution 00:18:15.770 --> 00:18:15.780 align:start position:0% just if you want to change the execution 00:18:15.780 --> 00:18:17.690 align:start position:0% just if you want to change the execution layer<00:18:16.140> you<00:18:16.500> write<00:18:16.620> an<00:18:16.799> eel's<00:18:17.160> proposal<00:18:17.460> you 00:18:17.690 --> 00:18:17.700 align:start position:0% layer you write an eel's proposal you 00:18:17.700 --> 00:18:19.010 align:start position:0% layer you write an eel's proposal you might<00:18:17.820> write<00:18:17.940> a<00:18:18.059> small<00:18:18.240> amount<00:18:18.419> of<00:18:18.539> ancillary 00:18:19.010 --> 00:18:19.020 align:start position:0% might write a small amount of ancillary 00:18:19.020 --> 00:18:20.450 align:start position:0% might write a small amount of ancillary documentation<00:18:19.500> but<00:18:19.679> both<00:18:19.860> you<00:18:20.039> just<00:18:20.220> request 00:18:20.450 --> 00:18:20.460 align:start position:0% documentation but both you just request 00:18:20.460 --> 00:18:22.850 align:start position:0% documentation but both you just request PR<00:18:20.760> there<00:18:21.539> are<00:18:21.660> other<00:18:21.780> people<00:18:22.020> who<00:18:22.500> think<00:18:22.620> that 00:18:22.850 --> 00:18:22.860 align:start position:0% PR there are other people who think that 00:18:22.860 --> 00:18:25.310 align:start position:0% PR there are other people who think that we<00:18:23.039> should<00:18:23.160> do<00:18:23.340> a<00:18:23.580> like<00:18:23.700> hybrid<00:18:24.120> process<00:18:24.539> where 00:18:25.310 --> 00:18:25.320 align:start position:0% we should do a like hybrid process where 00:18:25.320 --> 00:18:29.750 align:start position:0% we should do a like hybrid process where there<00:18:25.559> is<00:18:25.740> a<00:18:26.580> EIP<00:18:27.360> and<00:18:28.080> the<00:18:28.140> EIP<00:18:28.440> comes<00:18:29.220> with<00:18:29.400> as 00:18:29.750 --> 00:18:29.760 align:start position:0% there is a EIP and the EIP comes with as 00:18:29.760 --> 00:18:32.510 align:start position:0% there is a EIP and the EIP comes with as like<00:18:29.940> a<00:18:30.120> mandatory<00:18:30.600> component<00:18:31.140> a<00:18:31.919> yields 00:18:32.510 --> 00:18:32.520 align:start position:0% like a mandatory component a yields 00:18:32.520 --> 00:18:33.950 align:start position:0% like a mandatory component a yields change 00:18:33.950 --> 00:18:33.960 align:start position:0% change 00:18:33.960 --> 00:18:35.690 align:start position:0% change um<00:18:34.260> I<00:18:34.799> actually<00:18:35.039> don't<00:18:35.220> have<00:18:35.340> particularly 00:18:35.690 --> 00:18:35.700 align:start position:0% um I actually don't have particularly 00:18:35.700 --> 00:18:36.890 align:start position:0% um I actually don't have particularly strong<00:18:35.820> opinion<00:18:36.120> of<00:18:36.240> this<00:18:36.360> I<00:18:36.539> can<00:18:36.660> see<00:18:36.720> the 00:18:36.890 --> 00:18:36.900 align:start position:0% strong opinion of this I can see the 00:18:36.900 --> 00:18:39.409 align:start position:0% strong opinion of this I can see the argument<00:18:37.200> for<00:18:37.380> both<00:18:37.620> sides 00:18:39.409 --> 00:18:39.419 align:start position:0% argument for both sides 00:18:39.419 --> 00:18:42.110 align:start position:0% argument for both sides um<00:18:39.539> yeah<00:18:39.960> but<00:18:40.799> there's<00:18:41.400> lots<00:18:41.700> of<00:18:41.760> thoughts<00:18:42.059> on 00:18:42.110 --> 00:18:42.120 align:start position:0% um yeah but there's lots of thoughts on 00:18:42.120 --> 00:18:44.690 align:start position:0% um yeah but there's lots of thoughts on this<00:18:42.240> I<00:18:42.840> generally<00:18:43.620> take<00:18:43.860> the<00:18:44.039> attitude<00:18:44.400> that 00:18:44.690 --> 00:18:44.700 align:start position:0% this I generally take the attitude that 00:18:44.700 --> 00:18:46.430 align:start position:0% this I generally take the attitude that I'm<00:18:44.880> going<00:18:45.059> to<00:18:45.179> wait<00:18:45.299> until<00:18:45.539> like<00:18:45.960> we've 00:18:46.430 --> 00:18:46.440 align:start position:0% I'm going to wait until like we've 00:18:46.440 --> 00:18:47.810 align:start position:0% I'm going to wait until like we've started<00:18:46.740> using<00:18:47.039> this<00:18:47.100> and<00:18:47.280> people<00:18:47.460> have<00:18:47.640> like 00:18:47.810 --> 00:18:47.820 align:start position:0% started using this and people have like 00:18:47.820 --> 00:18:49.310 align:start position:0% started using this and people have like seen<00:18:48.000> it<00:18:48.179> in<00:18:48.299> production<00:18:48.660> and<00:18:48.900> then<00:18:49.020> they<00:18:49.200> can 00:18:49.310 --> 00:18:49.320 align:start position:0% seen it in production and then they can 00:18:49.320 --> 00:18:50.330 align:start position:0% seen it in production and then they can start<00:18:49.500> talking<00:18:49.679> about<00:18:49.860> what<00:18:50.100> they<00:18:50.220> actually 00:18:50.330 --> 00:18:50.340 align:start position:0% start talking about what they actually 00:18:50.340 --> 00:18:52.820 align:start position:0% start talking about what they actually want<00:18:50.520> to<00:18:50.640> do