WEBVTT Kind: captions Language: en 00:00:04.800 --> 00:00:07.950 align:start position:0% Aloha<00:00:05.800> I'm<00:00:06.160> Danno<00:00:06.520> Ferran<00:00:06.880> and<00:00:07.090> I'm<00:00:07.690> Tim 00:00:07.950 --> 00:00:07.960 align:start position:0% Aloha I'm Danno Ferran and I'm Tim 00:00:07.960 --> 00:00:09.540 align:start position:0% Aloha I'm Danno Ferran and I'm Tim product<00:00:08.559> manager<00:00:08.800> at<00:00:08.889> Pegasus 00:00:09.540 --> 00:00:09.550 align:start position:0% product manager at Pegasus 00:00:09.550 --> 00:00:13.049 align:start position:0% product manager at Pegasus I<00:00:09.690> am<00:00:10.690> a<00:00:10.870> network<00:00:11.230> protocol<00:00:11.590> engineer<00:00:12.010> and<00:00:12.219> our 00:00:13.049 --> 00:00:13.059 align:start position:0% I am a network protocol engineer and our 00:00:13.059 --> 00:00:15.210 align:start position:0% I am a network protocol engineer and our talk<00:00:13.300> today<00:00:13.450> is<00:00:13.570> to<00:00:14.170> propose<00:00:14.500> and<00:00:14.830> talk<00:00:14.950> about 00:00:15.210 --> 00:00:15.220 align:start position:0% talk today is to propose and talk about 00:00:15.220 --> 00:00:17.970 align:start position:0% talk today is to propose and talk about a<00:00:15.250> proposed<00:00:16.140> cadence<00:00:17.140> for<00:00:17.290> network<00:00:17.590> upgrades 00:00:17.970 --> 00:00:17.980 align:start position:0% a proposed cadence for network upgrades 00:00:17.980 --> 00:00:19.740 align:start position:0% a proposed cadence for network upgrades which<00:00:18.130> you<00:00:18.220> might<00:00:18.310> also<00:00:18.490> call<00:00:18.820> hard<00:00:19.180> Forks<00:00:19.540> and 00:00:19.740 --> 00:00:19.750 align:start position:0% which you might also call hard Forks and 00:00:19.750 --> 00:00:21.690 align:start position:0% which you might also call hard Forks and changing<00:00:20.710> it<00:00:20.770> from<00:00:20.829> the<00:00:20.980> old<00:00:21.130> model<00:00:21.340> which<00:00:21.579> is 00:00:21.690 --> 00:00:21.700 align:start position:0% changing it from the old model which is 00:00:21.700 --> 00:00:22.769 align:start position:0% changing it from the old model which is kind<00:00:21.880> of<00:00:21.910> like<00:00:22.029> buying<00:00:22.210> a<00:00:22.360> plane<00:00:22.570> ticket 00:00:22.769 --> 00:00:22.779 align:start position:0% kind of like buying a plane ticket 00:00:22.779 --> 00:00:25.200 align:start position:0% kind of like buying a plane ticket everyone<00:00:23.290> gets<00:00:23.500> on<00:00:23.650> the<00:00:23.739> same<00:00:23.890> plane<00:00:24.220> you<00:00:24.880> pick 00:00:25.200 --> 00:00:25.210 align:start position:0% everyone gets on the same plane you pick 00:00:25.210 --> 00:00:27.179 align:start position:0% everyone gets on the same plane you pick seats<00:00:25.570> you<00:00:25.930> do<00:00:26.079> a<00:00:26.110> months<00:00:26.619> and<00:00:26.860> years<00:00:27.070> in 00:00:27.179 --> 00:00:27.189 align:start position:0% seats you do a months and years in 00:00:27.189 --> 00:00:29.670 align:start position:0% seats you do a months and years in advance<00:00:27.310> and<00:00:27.939> things<00:00:28.660> don't<00:00:28.869> change<00:00:28.989> it<00:00:29.410> flies 00:00:29.670 --> 00:00:29.680 align:start position:0% advance and things don't change it flies 00:00:29.680 --> 00:00:31.229 align:start position:0% advance and things don't change it flies out<00:00:29.890> or<00:00:29.919> it<00:00:30.099> doesn't<00:00:30.310> and<00:00:30.880> instead<00:00:31.149> of 00:00:31.229 --> 00:00:31.239 align:start position:0% out or it doesn't and instead of 00:00:31.239 --> 00:00:33.150 align:start position:0% out or it doesn't and instead of replacing<00:00:31.509> with<00:00:31.779> a<00:00:31.810> train<00:00:32.050> model<00:00:32.410> where<00:00:32.619> you 00:00:33.150 --> 00:00:33.160 align:start position:0% replacing with a train model where you 00:00:33.160 --> 00:00:34.530 align:start position:0% replacing with a train model where you show<00:00:33.280> up<00:00:33.399> at<00:00:33.460> the<00:00:33.489> train<00:00:33.730> platform<00:00:33.760> and 00:00:34.530 --> 00:00:34.540 align:start position:0% show up at the train platform and 00:00:34.540 --> 00:00:36.510 align:start position:0% show up at the train platform and whoever's<00:00:35.320> there<00:00:35.470> is<00:00:35.649> leaves<00:00:36.010> and<00:00:36.250> whoever's 00:00:36.510 --> 00:00:36.520 align:start position:0% whoever's there is leaves and whoever's 00:00:36.520 --> 00:00:39.150 align:start position:0% whoever's there is leaves and whoever's there<00:00:36.640> doesn't<00:00:37.110> but<00:00:38.110> first<00:00:38.350> let's<00:00:38.830> start<00:00:38.920> with 00:00:39.150 --> 00:00:39.160 align:start position:0% there doesn't but first let's start with 00:00:39.160 --> 00:00:41.130 align:start position:0% there doesn't but first let's start with a<00:00:39.190> little<00:00:39.310> bit<00:00:39.460> of<00:00:39.490> history<00:00:39.940> what<00:00:40.660> did<00:00:40.840> network 00:00:41.130 --> 00:00:41.140 align:start position:0% a little bit of history what did network 00:00:41.140 --> 00:00:43.380 align:start position:0% a little bit of history what did network upgrades<00:00:41.470> look<00:00:41.650> like<00:00:41.800> before<00:00:42.190> this<00:00:42.430> it<00:00:43.240> was<00:00:43.360> a 00:00:43.380 --> 00:00:43.390 align:start position:0% upgrades look like before this it was a 00:00:43.390 --> 00:00:45.240 align:start position:0% upgrades look like before this it was a lot<00:00:43.570> like<00:00:43.690> a<00:00:43.750> family<00:00:44.170> vacation<00:00:44.290> frontier 00:00:45.240 --> 00:00:45.250 align:start position:0% lot like a family vacation frontier 00:00:45.250 --> 00:00:47.580 align:start position:0% lot like a family vacation frontier homestead<00:00:45.700> Byzantium<00:00:46.300> constant<00:00:46.720> Opel<00:00:46.990> mom 00:00:47.580 --> 00:00:47.590 align:start position:0% homestead Byzantium constant Opel mom 00:00:47.590 --> 00:00:48.780 align:start position:0% homestead Byzantium constant Opel mom and<00:00:47.770> dad<00:00:47.920> would<00:00:48.070> tell<00:00:48.310> us<00:00:48.400> where<00:00:48.610> we're<00:00:48.760> going 00:00:48.780 --> 00:00:48.790 align:start position:0% and dad would tell us where we're going 00:00:48.790 --> 00:00:51.420 align:start position:0% and dad would tell us where we're going we'd<00:00:49.330> pack<00:00:49.690> the<00:00:49.870> car<00:00:50.080> you<00:00:50.770> sneak<00:00:51.130> in<00:00:51.310> your 00:00:51.420 --> 00:00:51.430 align:start position:0% we'd pack the car you sneak in your 00:00:51.430 --> 00:00:53.550 align:start position:0% we'd pack the car you sneak in your favorite<00:00:51.820> toy<00:00:52.060> we<00:00:52.780> drive<00:00:53.140> and<00:00:53.350> drive<00:00:53.500> and 00:00:53.550 --> 00:00:53.560 align:start position:0% favorite toy we drive and drive and 00:00:53.560 --> 00:00:55.170 align:start position:0% favorite toy we drive and drive and drive<00:00:53.890> we'd<00:00:54.160> get<00:00:54.340> there<00:00:54.490> eventually<00:00:54.730> and<00:00:55.120> it 00:00:55.170 --> 00:00:55.180 align:start position:0% drive we'd get there eventually and it 00:00:55.180 --> 00:00:56.610 align:start position:0% drive we'd get there eventually and it would<00:00:55.270> all<00:00:55.420> be<00:00:55.450> happiness<00:00:55.960> in<00:00:56.110> sunshine<00:00:56.470> in 00:00:56.610 --> 00:00:56.620 align:start position:0% would all be happiness in sunshine in 00:00:56.620 --> 00:01:00.390 align:start position:0% would all be happiness in sunshine in the<00:00:56.710> end<00:00:57.870> except<00:00:58.870> when<00:00:58.990> it<00:00:59.079> wasn't<00:00:59.280> there<00:01:00.280> were 00:01:00.390 --> 00:01:00.400 align:start position:0% the end except when it wasn't there were 00:01:00.400 --> 00:01:01.920 align:start position:0% the end except when it wasn't there were a<00:01:00.430> few<00:01:00.610> network<00:01:00.880> upgrades<00:01:01.270> that<00:01:01.540> were<00:01:01.630> a 00:01:01.920 --> 00:01:01.930 align:start position:0% a few network upgrades that were a 00:01:01.930 --> 00:01:03.600 align:start position:0% a few network upgrades that were a little<00:01:02.079> more<00:01:02.260> emergency<00:01:03.190> all-hands-on-deck 00:01:03.600 --> 00:01:03.610 align:start position:0% little more emergency all-hands-on-deck 00:01:03.610 --> 00:01:06.030 align:start position:0% little more emergency all-hands-on-deck type<00:01:04.180> situations<00:01:04.780> the<00:01:05.470> first<00:01:05.500> two<00:01:05.860> were<00:01:05.950> the 00:01:06.030 --> 00:01:06.040 align:start position:0% type situations the first two were the 00:01:06.040 --> 00:01:07.950 align:start position:0% type situations the first two were the Shanghai<00:01:06.430> attack<00:01:06.759> and<00:01:07.329> the<00:01:07.450> second<00:01:07.750> one<00:01:07.840> was 00:01:07.950 --> 00:01:07.960 align:start position:0% Shanghai attack and the second one was 00:01:07.960 --> 00:01:09.090 align:start position:0% Shanghai attack and the second one was then<00:01:08.140> there<00:01:08.259> was<00:01:08.350> a<00:01:08.380> security<00:01:08.770> flaw 00:01:09.090 --> 00:01:09.100 align:start position:0% then there was a security flaw 00:01:09.100 --> 00:01:10.980 align:start position:0% then there was a security flaw discovered<00:01:09.579> as<00:01:09.670> part<00:01:09.850> of<00:01:09.880> Constantinople<00:01:10.780> in 00:01:10.980 --> 00:01:10.990 align:start position:0% discovered as part of Constantinople in 00:01:10.990 --> 00:01:13.319 align:start position:0% discovered as part of Constantinople in those<00:01:11.560> situations<00:01:12.159> we<00:01:12.310> all<00:01:12.429> came<00:01:12.579> together<00:01:12.819> we 00:01:13.319 --> 00:01:13.329 align:start position:0% those situations we all came together we 00:01:13.329 --> 00:01:15.090 align:start position:0% those situations we all came together we all<00:01:13.479> got<00:01:13.659> the<00:01:13.749> network<00:01:14.020> upgrade<00:01:14.319> out<00:01:14.469> in<00:01:14.679> a 00:01:15.090 --> 00:01:15.100 align:start position:0% all got the network upgrade out in a 00:01:15.100 --> 00:01:17.760 align:start position:0% all got the network upgrade out in a timely<00:01:15.520> and<00:01:15.549> fast<00:01:15.969> fashion<00:01:16.299> laser<00:01:17.200> focused<00:01:17.679> on 00:01:17.760 --> 00:01:17.770 align:start position:0% timely and fast fashion laser focused on 00:01:17.770 --> 00:01:19.980 align:start position:0% timely and fast fashion laser focused on what<00:01:17.920> the<00:01:18.009> problems<00:01:18.340> were<00:01:18.840> so<00:01:19.840> where<00:01:19.929> does 00:01:19.980 --> 00:01:19.990 align:start position:0% what the problems were so where does 00:01:19.990 --> 00:01:22.889 align:start position:0% what the problems were so where does that<00:01:20.049> put<00:01:20.170> us<00:01:20.350> today<00:01:21.450> so<00:01:22.450> the<00:01:22.569> beginning<00:01:22.689> of 00:01:22.889 --> 00:01:22.899 align:start position:0% that put us today so the beginning of 00:01:22.899 --> 00:01:24.480 align:start position:0% that put us today so the beginning of the<00:01:23.020> year<00:01:23.109> we<00:01:23.289> proposed<00:01:23.619> a<00:01:23.649> plan<00:01:23.889> for<00:01:24.159> instant 00:01:24.480 --> 00:01:24.490 align:start position:0% the year we proposed a plan for instant 00:01:24.490 --> 00:01:26.340 align:start position:0% the year we proposed a plan for instant Bowl<00:01:24.670> where<00:01:25.329> we<00:01:25.420> would<00:01:25.569> take<00:01:25.780> everything<00:01:26.229> from 00:01:26.340 --> 00:01:26.350 align:start position:0% Bowl where we would take everything from 00:01:26.350 --> 00:01:28.139 align:start position:0% Bowl where we would take everything from the<00:01:26.469> beginning<00:01:26.770> and<00:01:27.399> we'd<00:01:27.579> have 00:01:28.139 --> 00:01:28.149 align:start position:0% the beginning and we'd have 00:01:28.149 --> 00:01:29.609 align:start position:0% the beginning and we'd have landmarks<00:01:28.659> along<00:01:28.780> the<00:01:28.960> way<00:01:29.079> that<00:01:29.259> we<00:01:29.350> would<00:01:29.499> do 00:01:29.609 --> 00:01:29.619 align:start position:0% landmarks along the way that we would do 00:01:29.619 --> 00:01:31.139 align:start position:0% landmarks along the way that we would do things<00:01:29.859> like<00:01:29.979> have<00:01:30.159> the<00:01:30.340> IQs<00:01:30.729> ready<00:01:30.909> and<00:01:31.060> all 00:01:31.139 --> 00:01:31.149 align:start position:0% things like have the IQs ready and all 00:01:31.149 --> 00:01:32.429 align:start position:0% things like have the IQs ready and all that<00:01:31.270> other<00:01:31.389> stuff<00:01:31.479> go<00:01:31.899> from<00:01:32.079> step<00:01:32.289> to<00:01:32.409> step 00:01:32.429 --> 00:01:32.439 align:start position:0% that other stuff go from step to step 00:01:32.439 --> 00:01:34.469 align:start position:0% that other stuff go from step to step down<00:01:32.649> the<00:01:33.009> waterfall<00:01:33.490> and<00:01:33.850> it<00:01:34.090> was<00:01:34.240> gonna<00:01:34.329> be 00:01:34.469 --> 00:01:34.479 align:start position:0% down the waterfall and it was gonna be 00:01:34.479 --> 00:01:36.059 align:start position:0% down the waterfall and it was gonna be rainbows<00:01:34.929> in<00:01:35.079> the<00:01:35.139> sunshine<00:01:35.560> it<00:01:35.709> was<00:01:35.829> gonna<00:01:35.920> be 00:01:36.059 --> 00:01:36.069 align:start position:0% rainbows in the sunshine it was gonna be 00:01:36.069 --> 00:01:37.020 align:start position:0% rainbows in the sunshine it was gonna be awesomeness 00:01:37.020 --> 00:01:37.030 align:start position:0% awesomeness 00:01:37.030 --> 00:01:39.719 align:start position:0% awesomeness right<00:01:37.329> yeah<00:01:38.289> well<00:01:38.859> like<00:01:39.039> everyone<00:01:39.429> in<00:01:39.609> this 00:01:39.719 --> 00:01:39.729 align:start position:0% right yeah well like everyone in this 00:01:39.729 --> 00:01:41.520 align:start position:0% right yeah well like everyone in this room<00:01:39.909> probably<00:01:40.030> knows<00:01:40.359> Waterfall<00:01:41.139> doesn't 00:01:41.520 --> 00:01:41.530 align:start position:0% room probably knows Waterfall doesn't 00:01:41.530 --> 00:01:43.590 align:start position:0% room probably knows Waterfall doesn't work<00:01:41.679> for<00:01:41.829> software<00:01:42.100> development<00:01:42.509> but<00:01:43.509> we 00:01:43.590 --> 00:01:43.600 align:start position:0% work for software development but we 00:01:43.600 --> 00:01:45.569 align:start position:0% work for software development but we tried<00:01:43.810> it<00:01:43.929> anyway<00:01:44.049> for<00:01:44.409> a<00:01:44.439> spam<00:01:44.679> bowl<00:01:44.889> and<00:01:45.069> so 00:01:45.569 --> 00:01:45.579 align:start position:0% tried it anyway for a spam bowl and so 00:01:45.579 --> 00:01:47.429 align:start position:0% tried it anyway for a spam bowl and so at<00:01:45.909> the<00:01:46.119> beginning<00:01:46.240> of<00:01:46.539> the<00:01:46.630> years<00:01:46.899> we<00:01:47.170> set 00:01:47.429 --> 00:01:47.439 align:start position:0% at the beginning of the years we set 00:01:47.439 --> 00:01:49.349 align:start position:0% at the beginning of the years we set ourselves<00:01:47.560> a<00:01:47.889> bunch<00:01:48.069> of<00:01:48.159> deadlines<00:01:48.520> we<00:01:49.240> would 00:01:49.349 --> 00:01:49.359 align:start position:0% ourselves a bunch of deadlines we would 00:01:49.359 --> 00:01:51.239 align:start position:0% ourselves a bunch of deadlines we would have<00:01:49.539> a<00:01:49.569> kickoff<00:01:49.929> in<00:01:50.109> January<00:01:50.529> give<00:01:51.130> ourselves 00:01:51.239 --> 00:01:51.249 align:start position:0% have a kickoff in January give ourselves 00:01:51.249 --> 00:01:52.889 align:start position:0% have a kickoff in January give ourselves a<00:01:51.639> good<00:01:51.850> amount<00:01:51.999> of<00:01:52.119> time<00:01:52.299> to<00:01:52.509> review<00:01:52.749> all<00:01:52.869> the 00:01:52.889 --> 00:01:52.899 align:start position:0% a good amount of time to review all the 00:01:52.899 --> 00:01:54.690 align:start position:0% a good amount of time to review all the eeap's<00:01:53.170> so<00:01:53.560> that<00:01:53.740> around<00:01:53.950> mid-may<00:01:54.369> we<00:01:54.579> could 00:01:54.690 --> 00:01:54.700 align:start position:0% eeap's so that around mid-may we could 00:01:54.700 --> 00:01:55.679 align:start position:0% eeap's so that around mid-may we could have<00:01:54.850> a<00:01:54.880> final<00:01:55.329> list 00:01:55.679 --> 00:01:55.689 align:start position:0% have a final list 00:01:55.689 --> 00:01:57.449 align:start position:0% have a final list this<00:01:56.109> would<00:01:56.259> give<00:01:56.409> us<00:01:56.560> two<00:01:56.799> months<00:01:57.100> to<00:01:57.219> work<00:01:57.340> on 00:01:57.449 --> 00:01:57.459 align:start position:0% this would give us two months to work on 00:01:57.459 --> 00:01:59.190 align:start position:0% this would give us two months to work on client<00:01:57.850> implementations<00:01:58.569> which<00:01:58.929> brought<00:01:59.170> us 00:01:59.190 --> 00:01:59.200 align:start position:0% client implementations which brought us 00:01:59.200 --> 00:02:01.349 align:start position:0% client implementations which brought us to<00:01:59.319> mid-july<00:01:59.709> this<00:02:00.549> way<00:02:00.729> we<00:02:00.909> could<00:02:01.060> deploy<00:02:01.299> a 00:02:01.349 --> 00:02:01.359 align:start position:0% to mid-july this way we could deploy a 00:02:01.359 --> 00:02:02.760 align:start position:0% to mid-july this way we could deploy a test<00:02:01.630> nuts<00:02:01.929> around<00:02:02.049> mid-august 00:02:02.760 --> 00:02:02.770 align:start position:0% test nuts around mid-august 00:02:02.770 --> 00:02:04.889 align:start position:0% test nuts around mid-august and<00:02:02.859> finally<00:02:03.579> have<00:02:03.789> her<00:02:03.880> upgrade<00:02:04.270> go<00:02:04.420> live<00:02:04.630> on 00:02:04.889 --> 00:02:04.899 align:start position:0% and finally have her upgrade go live on 00:02:04.899 --> 00:02:07.289 align:start position:0% and finally have her upgrade go live on main<00:02:05.170> net<00:02:05.380> by<00:02:05.920> mid<00:02:06.130> October<00:02:06.159> which<00:02:07.029> was 00:02:07.289 --> 00:02:07.299 align:start position:0% main net by mid October which was 00:02:07.299 --> 00:02:09.300 align:start position:0% main net by mid October which was supposed<00:02:07.659> to<00:02:07.749> be<00:02:07.899> two<00:02:08.140> weeks<00:02:08.259> before<00:02:08.530> DEFCON 00:02:09.300 --> 00:02:09.310 align:start position:0% supposed to be two weeks before DEFCON 00:02:09.310 --> 00:02:11.550 align:start position:0% supposed to be two weeks before DEFCON we're<00:02:09.610> forking<00:02:09.940> next<00:02:10.149> week<00:02:10.270> no<00:02:10.780> we're<00:02:10.959> not<00:02:11.020> and 00:02:11.550 --> 00:02:11.560 align:start position:0% we're forking next week no we're not and 00:02:11.560 --> 00:02:14.730 align:start position:0% we're forking next week no we're not and so<00:02:12.220> how<00:02:12.580> many<00:02:12.640> of<00:02:13.210> you<00:02:13.450> have<00:02:13.540> these<00:02:14.380> deadlines 00:02:14.730 --> 00:02:14.740 align:start position:0% so how many of you have these deadlines 00:02:14.740 --> 00:02:17.580 align:start position:0% so how many of you have these deadlines we<00:02:14.920> actually<00:02:15.190> it<00:02:15.510> we<00:02:16.510> hit<00:02:16.750> the<00:02:16.870> first<00:02:17.020> one<00:02:17.170> the 00:02:17.580 --> 00:02:17.590 align:start position:0% we actually it we hit the first one the 00:02:17.590 --> 00:02:18.500 align:start position:0% we actually it we hit the first one the kickoff 00:02:18.500 --> 00:02:18.510 align:start position:0% kickoff 00:02:18.510 --> 00:02:20.899 align:start position:0% kickoff and<00:02:18.799> obviously<00:02:19.799> a<00:02:20.069> lot<00:02:20.280> of<00:02:20.400> things<00:02:20.640> went<00:02:20.819> wrong 00:02:20.899 --> 00:02:20.909 align:start position:0% and obviously a lot of things went wrong 00:02:20.909 --> 00:02:23.630 align:start position:0% and obviously a lot of things went wrong here<00:02:21.360> and<00:02:21.569> one<00:02:22.409> of<00:02:22.530> the<00:02:22.650> more<00:02:23.370> interesting 00:02:23.630 --> 00:02:23.640 align:start position:0% here and one of the more interesting 00:02:23.640 --> 00:02:25.580 align:start position:0% here and one of the more interesting ones<00:02:24.000> is<00:02:24.269> that<00:02:24.299> the<00:02:24.659> theorem<00:02:24.870> community<00:02:25.409> had 00:02:25.580 --> 00:02:25.590 align:start position:0% ones is that the theorem community had 00:02:25.590 --> 00:02:27.199 align:start position:0% ones is that the theorem community had grown<00:02:25.860> a<00:02:25.890> lot<00:02:26.099> since<00:02:26.370> the<00:02:26.519> previous<00:02:26.730> upgrade 00:02:27.199 --> 00:02:27.209 align:start position:0% grown a lot since the previous upgrade 00:02:27.209 --> 00:02:29.390 align:start position:0% grown a lot since the previous upgrade so<00:02:27.870> when<00:02:28.019> it<00:02:28.140> came<00:02:28.260> time<00:02:28.319> to<00:02:28.709> review<00:02:29.040> the<00:02:29.189> eats 00:02:29.390 --> 00:02:29.400 align:start position:0% so when it came time to review the eats 00:02:29.400 --> 00:02:31.550 align:start position:0% so when it came time to review the eats instead<00:02:30.090> of<00:02:30.209> having<00:02:30.360> only<00:02:30.659> a<00:02:30.810> handful<00:02:31.379> to 00:02:31.550 --> 00:02:31.560 align:start position:0% instead of having only a handful to 00:02:31.560 --> 00:02:33.770 align:start position:0% instead of having only a handful to review<00:02:31.980> there<00:02:32.400> were<00:02:32.489> so<00:02:32.730> many<00:02:32.939> that<00:02:33.420> I<00:02:33.480> wasn't 00:02:33.770 --> 00:02:33.780 align:start position:0% review there were so many that I wasn't 00:02:33.780 --> 00:02:35.330 align:start position:0% review there were so many that I wasn't able<00:02:33.870> to<00:02:34.079> fit<00:02:34.260> them<00:02:34.349> on<00:02:34.500> this<00:02:34.620> live<00:02:34.860> using<00:02:35.159> the 00:02:35.330 --> 00:02:35.340 align:start position:0% able to fit them on this live using the 00:02:35.340 --> 00:02:37.729 align:start position:0% able to fit them on this live using the font<00:02:35.549> they<00:02:35.670> gave<00:02:35.819> us<00:02:36.000> and<00:02:36.269> so<00:02:37.170> this<00:02:37.349> means<00:02:37.590> that 00:02:37.729 --> 00:02:37.739 align:start position:0% font they gave us and so this means that 00:02:37.739 --> 00:02:40.069 align:start position:0% font they gave us and so this means that around<00:02:38.459> mid-may<00:02:38.849> when<00:02:39.390> we<00:02:39.569> should<00:02:39.780> have<00:02:39.810> had<00:02:40.019> a 00:02:40.069 --> 00:02:40.079 align:start position:0% around mid-may when we should have had a 00:02:40.079 --> 00:02:42.410 align:start position:0% around mid-may when we should have had a finalists<00:02:40.680> of<00:02:40.799> Eve's<00:02:41.129> for<00:02:41.310> the<00:02:41.400> upgrade<00:02:41.790> we're 00:02:42.410 --> 00:02:42.420 align:start position:0% finalists of Eve's for the upgrade we're 00:02:42.420 --> 00:02:43.729 align:start position:0% finalists of Eve's for the upgrade we're still<00:02:42.599> trying<00:02:42.810> to<00:02:42.870> wrap<00:02:43.049> her<00:02:43.230> head<00:02:43.260> around<00:02:43.440> all 00:02:43.729 --> 00:02:43.739 align:start position:0% still trying to wrap her head around all 00:02:43.739 --> 00:02:45.259 align:start position:0% still trying to wrap her head around all of<00:02:43.890> these<00:02:44.040> they<00:02:44.640> were<00:02:44.700> in<00:02:44.849> completely 00:02:45.259 --> 00:02:45.269 align:start position:0% of these they were in completely 00:02:45.269 --> 00:02:47.000 align:start position:0% of these they were in completely different<00:02:45.420> stages<00:02:46.109> some<00:02:46.319> of<00:02:46.409> them<00:02:46.560> were<00:02:46.709> early 00:02:47.000 --> 00:02:47.010 align:start position:0% different stages some of them were early 00:02:47.010 --> 00:02:48.679 align:start position:0% different stages some of them were early drafts<00:02:47.489> while<00:02:47.609> others<00:02:47.879> had<00:02:48.090> working<00:02:48.329> test 00:02:48.679 --> 00:02:48.689 align:start position:0% drafts while others had working test 00:02:48.689 --> 00:02:50.360 align:start position:0% drafts while others had working test nuts<00:02:48.900> and<00:02:49.170> there<00:02:49.470> were<00:02:49.530> dependencies<00:02:50.129> across 00:02:50.360 --> 00:02:50.370 align:start position:0% nuts and there were dependencies across 00:02:50.370 --> 00:02:53.270 align:start position:0% nuts and there were dependencies across all<00:02:50.609> of<00:02:50.790> them<00:02:50.940> so<00:02:51.900> this<00:02:52.019> was<00:02:52.140> not<00:02:52.290> ideal<00:02:52.470> and<00:02:52.859> we 00:02:53.270 --> 00:02:53.280 align:start position:0% all of them so this was not ideal and we 00:02:53.280 --> 00:02:55.729 align:start position:0% all of them so this was not ideal and we obviously<00:02:53.430> missed<00:02:53.909> that<00:02:54.090> deadline<00:02:54.379> so<00:02:55.379> we 00:02:55.729 --> 00:02:55.739 align:start position:0% obviously missed that deadline so we 00:02:55.739 --> 00:02:57.710 align:start position:0% obviously missed that deadline so we actually<00:02:56.069> got<00:02:56.190> her<00:02:56.310> and<00:02:56.549> her<00:02:56.819> final<00:02:57.480> list<00:02:57.629> of 00:02:57.710 --> 00:02:57.720 align:start position:0% actually got her and her final list of 00:02:57.720 --> 00:02:59.479 align:start position:0% actually got her and her final list of eeap's<00:02:57.989> for<00:02:58.230> Istanbul<00:02:58.650> around<00:02:59.129> mid-july 00:02:59.479 --> 00:02:59.489 align:start position:0% eeap's for Istanbul around mid-july 00:02:59.489 --> 00:03:02.270 align:start position:0% eeap's for Istanbul around mid-july which<00:03:00.150> is<00:03:00.329> when<00:03:00.480> we<00:03:00.510> should<00:03:00.780> have<00:03:00.870> been<00:03:01.280> having 00:03:02.270 --> 00:03:02.280 align:start position:0% which is when we should have been having 00:03:02.280 --> 00:03:04.879 align:start position:0% which is when we should have been having the<00:03:02.489> clients<00:03:02.819> implementation<00:03:03.450> done<00:03:03.889> this 00:03:04.879 --> 00:03:04.889 align:start position:0% the clients implementation done this 00:03:04.889 --> 00:03:06.410 align:start position:0% the clients implementation done this pushed<00:03:05.159> back<00:03:05.310> the<00:03:05.340> clients<00:03:05.790> implementation 00:03:06.410 --> 00:03:06.420 align:start position:0% pushed back the clients implementation 00:03:06.420 --> 00:03:09.199 align:start position:0% pushed back the clients implementation to<00:03:07.019> the<00:03:07.049> end<00:03:07.409> of<00:03:07.530> this<00:03:07.620> summer<00:03:07.849> around<00:03:08.849> August 00:03:09.199 --> 00:03:09.209 align:start position:0% to the end of this summer around August 00:03:09.209 --> 00:03:10.430 align:start position:0% to the end of this summer around August which<00:03:09.540> is<00:03:09.690> when<00:03:09.810> we<00:03:09.840> should<00:03:09.959> have<00:03:10.109> gone<00:03:10.200> live 00:03:10.430 --> 00:03:10.440 align:start position:0% which is when we should have gone live 00:03:10.440 --> 00:03:12.080 align:start position:0% which is when we should have gone live on<00:03:10.590> the<00:03:10.680> test<00:03:10.889> nets<00:03:11.099> and<00:03:11.310> it<00:03:11.700> pushed<00:03:11.879> back<00:03:12.060> the 00:03:12.080 --> 00:03:12.090 align:start position:0% on the test nets and it pushed back the 00:03:12.090 --> 00:03:14.330 align:start position:0% on the test nets and it pushed back the test<00:03:12.389> net<00:03:12.569> upgrades<00:03:12.930> to<00:03:13.139> October<00:03:13.739> which<00:03:14.190> is 00:03:14.330 --> 00:03:14.340 align:start position:0% test net upgrades to October which is 00:03:14.340 --> 00:03:15.319 align:start position:0% test net upgrades to October which is when<00:03:14.459> we<00:03:14.489> should<00:03:14.609> have<00:03:14.730> had<00:03:14.879> a<00:03:14.940> Romanian 00:03:15.319 --> 00:03:15.329 align:start position:0% when we should have had a Romanian 00:03:15.329 --> 00:03:17.479 align:start position:0% when we should have had a Romanian upgrade<00:03:15.659> at<00:03:16.349> this<00:03:16.560> point<00:03:16.799> the<00:03:16.920> minute<00:03:17.190> upgrade 00:03:17.479 --> 00:03:17.489 align:start position:0% upgrade at this point the minute upgrade 00:03:17.489 --> 00:03:18.770 align:start position:0% upgrade at this point the minute upgrade will<00:03:17.639> probably<00:03:17.909> be<00:03:18.000> at<00:03:18.120> the<00:03:18.269> end<00:03:18.359> of<00:03:18.450> the<00:03:18.569> year 00:03:18.770 --> 00:03:18.780 align:start position:0% will probably be at the end of the year 00:03:18.780 --> 00:03:22.280 align:start position:0% will probably be at the end of the year or<00:03:19.019> early<00:03:19.170> 2020<00:03:19.829> and<00:03:20.389> so<00:03:21.389> as<00:03:21.629> this<00:03:22.139> was 00:03:22.280 --> 00:03:22.290 align:start position:0% or early 2020 and so as this was 00:03:22.290 --> 00:03:24.439 align:start position:0% or early 2020 and so as this was happening<00:03:22.739> a<00:03:23.010> lot<00:03:23.340> of<00:03:23.430> people<00:03:23.669> realized<00:03:24.090> it 00:03:24.439 --> 00:03:24.449 align:start position:0% happening a lot of people realized it 00:03:24.449 --> 00:03:27.110 align:start position:0% happening a lot of people realized it was<00:03:24.660> not<00:03:24.810> going<00:03:25.169> super<00:03:25.410> well<00:03:25.440> and<00:03:26.030> there<00:03:27.030> were 00:03:27.110 --> 00:03:27.120 align:start position:0% was not going super well and there were 00:03:27.120 --> 00:03:28.909 align:start position:0% was not going super well and there were suggestions<00:03:27.510> made<00:03:27.959> around<00:03:28.290> how<00:03:28.470> we<00:03:28.530> can<00:03:28.769> make 00:03:28.909 --> 00:03:28.919 align:start position:0% suggestions made around how we can make 00:03:28.919 --> 00:03:31.789 align:start position:0% suggestions made around how we can make Berlin<00:03:29.310> the<00:03:29.849> next<00:03:30.120> upgrade<00:03:30.299> go<00:03:31.019> much<00:03:31.319> smoother 00:03:31.789 --> 00:03:31.799 align:start position:0% Berlin the next upgrade go much smoother 00:03:31.799 --> 00:03:34.039 align:start position:0% Berlin the next upgrade go much smoother than<00:03:31.829> Istanbul<00:03:32.430> so<00:03:33.359> will<00:03:33.540> not<00:03:33.690> walk<00:03:33.900> you 00:03:34.039 --> 00:03:34.049 align:start position:0% than Istanbul so will not walk you 00:03:34.049 --> 00:03:35.360 align:start position:0% than Istanbul so will not walk you through<00:03:34.319> some<00:03:34.500> of<00:03:34.530> these<00:03:34.709> ideas<00:03:34.769> that<00:03:35.280> the 00:03:35.360 --> 00:03:35.370 align:start position:0% through some of these ideas that the 00:03:35.370 --> 00:03:37.159 align:start position:0% through some of these ideas that the community<00:03:35.819> you've<00:03:35.970> brought<00:03:36.180> forward<00:03:36.449> and<00:03:36.690> try 00:03:37.159 --> 00:03:37.169 align:start position:0% community you've brought forward and try 00:03:37.169 --> 00:03:38.780 align:start position:0% community you've brought forward and try to<00:03:37.230> bundle<00:03:37.500> them<00:03:37.709> together<00:03:37.889> into<00:03:38.340> what<00:03:38.609> we've 00:03:38.780 --> 00:03:38.790 align:start position:0% to bundle them together into what we've 00:03:38.790 --> 00:03:43.460 align:start position:0% to bundle them together into what we've called<00:03:39.030> the<00:03:39.209> train<00:03:39.419> station<00:03:39.780> model<00:03:42.260> the<00:03:43.260> first 00:03:43.460 --> 00:03:43.470 align:start position:0% called the train station model the first 00:03:43.470 --> 00:03:44.900 align:start position:0% called the train station model the first person<00:03:43.829> to<00:03:43.859> notice<00:03:44.129> how<00:03:44.280> poorly<00:03:44.549> things<00:03:44.790> were 00:03:44.900 --> 00:03:44.910 align:start position:0% person to notice how poorly things were 00:03:44.910 --> 00:03:46.729 align:start position:0% person to notice how poorly things were going<00:03:45.150> was<00:03:45.269> Alexia<00:03:45.660> coup<00:03:45.870> nob<00:03:46.079> the<00:03:46.500> brains 00:03:46.729 --> 00:03:46.739 align:start position:0% going was Alexia coup nob the brains 00:03:46.739 --> 00:03:48.740 align:start position:0% going was Alexia coup nob the brains behind<00:03:46.919> state<00:03:47.400> rent<00:03:47.669> and<00:03:47.849> stateless<00:03:48.239> clients 00:03:48.740 --> 00:03:48.750 align:start position:0% behind state rent and stateless clients 00:03:48.750 --> 00:03:50.890 align:start position:0% behind state rent and stateless clients and<00:03:48.930> he<00:03:49.379> posted<00:03:49.680> a<00:03:49.769> blog<00:03:49.980> post<00:03:50.280> or<00:03:50.400> outline 00:03:50.890 --> 00:03:50.900 align:start position:0% and he posted a blog post or outline 00:03:50.900 --> 00:03:52.939 align:start position:0% and he posted a blog post or outline basically<00:03:51.900> where<00:03:52.199> things<00:03:52.440> were<00:03:52.560> at<00:03:52.709> where 00:03:52.939 --> 00:03:52.949 align:start position:0% basically where things were at where 00:03:52.949 --> 00:03:54.409 align:start position:0% basically where things were at where things<00:03:53.190> could<00:03:53.430> be<00:03:53.609> and<00:03:53.849> where<00:03:54.000> they<00:03:54.120> should<00:03:54.299> go 00:03:54.409 --> 00:03:54.419 align:start position:0% things could be and where they should go 00:03:54.419 --> 00:03:56.780 align:start position:0% things could be and where they should go on<00:03:54.660> the<00:03:55.349> first<00:03:55.530> picture<00:03:55.739> outlines<00:03:56.280> what<00:03:56.669> was 00:03:56.780 --> 00:03:56.790 align:start position:0% on the first picture outlines what was 00:03:56.790 --> 00:03:58.069 align:start position:0% on the first picture outlines what was going<00:03:57.030> on<00:03:57.180> with<00:03:57.329> the<00:03:57.419> first<00:03:57.629> set<00:03:57.840> of<00:03:57.930> network 00:03:58.069 --> 00:03:58.079 align:start position:0% going on with the first set of network 00:03:58.079 --> 00:04:00.500 align:start position:0% going on with the first set of network upgrades<00:03:58.620> there<00:03:59.519> was<00:03:59.609> a<00:03:59.639> everyone<00:04:00.239> would<00:04:00.359> come 00:04:00.500 --> 00:04:00.510 align:start position:0% upgrades there was a everyone would come 00:04:00.510 --> 00:04:02.059 align:start position:0% upgrades there was a everyone would come together<00:04:00.629> they<00:04:01.019> would<00:04:01.109> write<00:04:01.349> their<00:04:01.620> their 00:04:02.059 --> 00:04:02.069 align:start position:0% together they would write their their 00:04:02.069 --> 00:04:03.920 align:start position:0% together they would write their their tests<00:04:02.579> but<00:04:02.730> there<00:04:02.849> was<00:04:03.000> one<00:04:03.239> special<00:04:03.659> client 00:04:03.920 --> 00:04:03.930 align:start position:0% tests but there was one special client 00:04:03.930 --> 00:04:05.930 align:start position:0% tests but there was one special client that<00:04:04.019> had<00:04:04.139> special<00:04:04.290> privileges<00:04:04.889> a<00:04:05.129> left<00:04:05.819> the 00:04:05.930 --> 00:04:05.940 align:start position:0% that had special privileges a left the 00:04:05.940 --> 00:04:08.420 align:start position:0% that had special privileges a left the C++<00:04:06.569> client<00:04:06.959> was<00:04:07.440> the<00:04:07.590> one<00:04:07.769> client<00:04:08.069> that<00:04:08.220> could 00:04:08.420 --> 00:04:08.430 align:start position:0% C++ client was the one client that could 00:04:08.430 --> 00:04:10.280 align:start position:0% C++ client was the one client that could actually<00:04:08.549> produce<00:04:09.030> the<00:04:09.599> reference<00:04:09.930> tests 00:04:10.280 --> 00:04:10.290 align:start position:0% actually produce the reference tests 00:04:10.290 --> 00:04:11.899 align:start position:0% actually produce the reference tests that<00:04:10.709> were<00:04:10.859> needed<00:04:11.129> by<00:04:11.220> all<00:04:11.459> of<00:04:11.609> the<00:04:11.730> other 00:04:11.899 --> 00:04:11.909 align:start position:0% that were needed by all of the other 00:04:11.909 --> 00:04:13.849 align:start position:0% that were needed by all of the other clients<00:04:12.480> to<00:04:12.659> verify<00:04:13.319> that<00:04:13.470> all<00:04:13.650> of<00:04:13.739> their 00:04:13.849 --> 00:04:13.859 align:start position:0% clients to verify that all of their 00:04:13.859 --> 00:04:16.069 align:start position:0% clients to verify that all of their consensus<00:04:14.370> critical<00:04:14.790> code<00:04:14.970> was<00:04:15.209> correct<00:04:15.659> it 00:04:16.069 --> 00:04:16.079 align:start position:0% consensus critical code was correct it 00:04:16.079 --> 00:04:18.110 align:start position:0% consensus critical code was correct it was<00:04:16.169> going<00:04:16.380> to<00:04:16.440> function<00:04:16.769> properly<00:04:16.889> so<00:04:17.820> before 00:04:18.110 --> 00:04:18.120 align:start position:0% was going to function properly so before 00:04:18.120 --> 00:04:19.819 align:start position:0% was going to function properly so before anything<00:04:18.389> could<00:04:18.659> progress<00:04:19.049> out<00:04:19.320> left<00:04:19.650> had<00:04:19.769> to 00:04:19.819 --> 00:04:19.829 align:start position:0% anything could progress out left had to 00:04:19.829 --> 00:04:21.680 align:start position:0% anything could progress out left had to have<00:04:19.979> all<00:04:20.159> of<00:04:20.190> their<00:04:20.400> stuff<00:04:20.430> written<00:04:20.909> in<00:04:21.209> the 00:04:21.680 --> 00:04:21.690 align:start position:0% have all of their stuff written in the 00:04:21.690 --> 00:04:23.270 align:start position:0% have all of their stuff written in the tests<00:04:21.930> written<00:04:22.199> and<00:04:22.530> then<00:04:22.860> they<00:04:22.949> had<00:04:23.099> to<00:04:23.190> go 00:04:23.270 --> 00:04:23.280 align:start position:0% tests written and then they had to go 00:04:23.280 --> 00:04:24.620 align:start position:0% tests written and then they had to go work<00:04:23.430> with<00:04:23.639> the<00:04:23.729> other<00:04:23.880> clients<00:04:24.360> and<00:04:24.510> work 00:04:24.620 --> 00:04:24.630 align:start position:0% work with the other clients and work 00:04:24.630 --> 00:04:26.959 align:start position:0% work with the other clients and work back<00:04:24.840> and<00:04:25.050> forth<00:04:25.110> they<00:04:25.800> created<00:04:26.280> a<00:04:26.430> gating 00:04:26.959 --> 00:04:26.969 align:start position:0% back and forth they created a gating 00:04:26.969 --> 00:04:28.850 align:start position:0% back and forth they created a gating function<00:04:27.479> this<00:04:28.050> is<00:04:28.200> why<00:04:28.320> a<00:04:28.349> lot<00:04:28.500> of<00:04:28.680> the 00:04:28.850 --> 00:04:28.860 align:start position:0% function this is why a lot of the 00:04:28.860 --> 00:04:30.500 align:start position:0% function this is why a lot of the network<00:04:29.460> upgrades<00:04:29.789> moved<00:04:30.000> in<00:04:30.120> lockstep 00:04:30.500 --> 00:04:30.510 align:start position:0% network upgrades moved in lockstep 00:04:30.510 --> 00:04:31.740 align:start position:0% network upgrades moved in lockstep before<00:04:30.870> because<00:04:31.169> there<00:04:31.289> was<00:04:31.409> one 00:04:31.740 --> 00:04:31.750 align:start position:0% before because there was one 00:04:31.750 --> 00:04:34.770 align:start position:0% before because there was one tasks<00:04:32.650> that<00:04:32.830> had<00:04:33.010> to<00:04:33.100> be<00:04:33.220> accomplished<00:04:34.000> so 00:04:34.770 --> 00:04:34.780 align:start position:0% tasks that had to be accomplished so 00:04:34.780 --> 00:04:36.570 align:start position:0% tasks that had to be accomplished so what<00:04:35.260> Alexei<00:04:35.590> proposed<00:04:35.980> is<00:04:36.220> instead<00:04:36.520> of 00:04:36.570 --> 00:04:36.580 align:start position:0% what Alexei proposed is instead of 00:04:36.580 --> 00:04:39.270 align:start position:0% what Alexei proposed is instead of focusing<00:04:36.760> on<00:04:37.300> as<00:04:37.630> a<00:04:37.990> group<00:04:38.350> and<00:04:38.560> having<00:04:39.130> one 00:04:39.270 --> 00:04:39.280 align:start position:0% focusing on as a group and having one 00:04:39.280 --> 00:04:40.980 align:start position:0% focusing on as a group and having one client<00:04:39.490> and<00:04:39.730> doing<00:04:39.940> everything<00:04:40.150> at<00:04:40.330> once<00:04:40.540> that 00:04:40.980 --> 00:04:40.990 align:start position:0% client and doing everything at once that 00:04:40.990 --> 00:04:43.470 align:start position:0% client and doing everything at once that we<00:04:41.080> split<00:04:41.350> these<00:04:41.470> these<00:04:41.890> upgrades<00:04:42.550> the 00:04:43.470 --> 00:04:43.480 align:start position:0% we split these these upgrades the 00:04:43.480 --> 00:04:45.510 align:start position:0% we split these these upgrades the details<00:04:43.990> into<00:04:44.380> various<00:04:44.710> working<00:04:45.070> group<00:04:45.250> so<00:04:45.400> to 00:04:45.510 --> 00:04:45.520 align:start position:0% details into various working group so to 00:04:45.520 --> 00:04:47.580 align:start position:0% details into various working group so to have<00:04:45.670> various<00:04:46.110> areas<00:04:47.110> of<00:04:47.260> concern<00:04:47.560> and 00:04:47.580 --> 00:04:47.590 align:start position:0% have various areas of concern and 00:04:47.590 --> 00:04:48.750 align:start position:0% have various areas of concern and interest<00:04:47.890> that<00:04:48.220> they<00:04:48.310> would<00:04:48.460> recommend 00:04:48.750 --> 00:04:48.760 align:start position:0% interest that they would recommend 00:04:48.760 --> 00:04:51.060 align:start position:0% interest that they would recommend proposals<00:04:49.330> in<00:04:49.480> in<00:04:50.290> these<00:04:50.470> network<00:04:50.830> groups 00:04:51.060 --> 00:04:51.070 align:start position:0% proposals in in these network groups 00:04:51.070 --> 00:04:53.280 align:start position:0% proposals in in these network groups they<00:04:51.640> would<00:04:51.910> produce<00:04:52.570> reference 00:04:53.280 --> 00:04:53.290 align:start position:0% they would produce reference 00:04:53.290 --> 00:04:54.600 align:start position:0% they would produce reference implementations<00:04:53.980> for<00:04:54.130> what<00:04:54.280> they<00:04:54.370> thought 00:04:54.600 --> 00:04:54.610 align:start position:0% implementations for what they thought 00:04:54.610 --> 00:04:56.670 align:start position:0% implementations for what they thought needed<00:04:54.760> to<00:04:54.970> be<00:04:55.150> changed<00:04:55.440> now<00:04:56.440> what<00:04:56.590> he 00:04:56.670 --> 00:04:56.680 align:start position:0% needed to be changed now what he 00:04:56.680 --> 00:04:58.500 align:start position:0% needed to be changed now what he proposes<00:04:57.100> a<00:04:57.310> very<00:04:57.550> important<00:04:58.120> thing<00:04:58.270> for<00:04:58.300> the 00:04:58.500 --> 00:04:58.510 align:start position:0% proposes a very important thing for the 00:04:58.510 --> 00:05:00.240 align:start position:0% proposes a very important thing for the reference<00:04:58.720> implementations<00:04:59.440> it<00:04:59.950> was<00:05:00.100> going 00:05:00.240 --> 00:05:00.250 align:start position:0% reference implementations it was going 00:05:00.250 --> 00:05:02.040 align:start position:0% reference implementations it was going to<00:05:00.310> use<00:05:00.460> a<00:05:00.490> new<00:05:00.730> tool<00:05:00.760> written<00:05:01.270> by<00:05:01.390> Dmitry<00:05:01.870> from 00:05:02.040 --> 00:05:02.050 align:start position:0% to use a new tool written by Dmitry from 00:05:02.050 --> 00:05:04.020 align:start position:0% to use a new tool written by Dmitry from the<00:05:02.170> etherium<00:05:02.500> testing<00:05:02.860> team<00:05:03.040> called<00:05:03.640> retest 00:05:04.020 --> 00:05:04.030 align:start position:0% the etherium testing team called retest 00:05:04.030 --> 00:05:06.360 align:start position:0% the etherium testing team called retest F<00:05:04.240> what<00:05:04.870> Dmitry<00:05:05.290> did<00:05:05.410> is<00:05:05.620> he<00:05:05.740> when<00:05:05.890> he<00:05:06.010> got<00:05:06.160> all 00:05:06.360 --> 00:05:06.370 align:start position:0% F what Dmitry did is he when he got all 00:05:06.370 --> 00:05:08.400 align:start position:0% F what Dmitry did is he when he got all of<00:05:06.490> the<00:05:06.580> testing<00:05:06.970> code<00:05:07.150> that<00:05:07.690> I<00:05:07.720> left<00:05:07.990> needed 00:05:08.400 --> 00:05:08.410 align:start position:0% of the testing code that I left needed 00:05:08.410 --> 00:05:10.410 align:start position:0% of the testing code that I left needed to<00:05:08.830> produce<00:05:08.980> these<00:05:09.280> reference<00:05:09.610> tests<00:05:10.000> and<00:05:10.360> he 00:05:10.410 --> 00:05:10.420 align:start position:0% to produce these reference tests and he 00:05:10.420 --> 00:05:13.290 align:start position:0% to produce these reference tests and he took<00:05:10.630> out<00:05:10.780> the<00:05:10.900> need<00:05:11.080> to<00:05:11.230> have<00:05:11.730> to<00:05:12.730> have<00:05:12.910> a<00:05:13.090> left 00:05:13.290 --> 00:05:13.300 align:start position:0% took out the need to have to have a left 00:05:13.300 --> 00:05:15.360 align:start position:0% took out the need to have to have a left run<00:05:13.570> these<00:05:13.750> so<00:05:14.440> you<00:05:14.470> can<00:05:14.560> create<00:05:14.980> a<00:05:15.070> reference 00:05:15.360 --> 00:05:15.370 align:start position:0% run these so you can create a reference 00:05:15.370 --> 00:05:17.550 align:start position:0% run these so you can create a reference test<00:05:15.760> from<00:05:16.270> any<00:05:16.420> client<00:05:16.900> that<00:05:16.990> implements<00:05:17.470> the 00:05:17.550 --> 00:05:17.560 align:start position:0% test from any client that implements the 00:05:17.560 --> 00:05:21.300 align:start position:0% test from any client that implements the api's<00:05:18.010> that<00:05:18.790> retest<00:05:19.510> death<00:05:19.750> uses<00:05:20.470> death<00:05:21.160> has 00:05:21.300 --> 00:05:21.310 align:start position:0% api's that retest death uses death has 00:05:21.310 --> 00:05:22.920 align:start position:0% api's that retest death uses death has implemented<00:05:21.640> them<00:05:22.000> basically<00:05:22.810> was 00:05:22.920 --> 00:05:22.930 align:start position:0% implemented them basically was 00:05:22.930 --> 00:05:25.530 align:start position:0% implemented them basically was implemented<00:05:23.410> them<00:05:23.560> and<00:05:23.770> obviously<00:05:24.580> Alice's 00:05:25.530 --> 00:05:25.540 align:start position:0% implemented them and obviously Alice's 00:05:25.540 --> 00:05:27.810 align:start position:0% implemented them and obviously Alice's implements<00:05:26.080> of<00:05:26.169> them<00:05:26.290> so<00:05:26.980> from<00:05:27.250> these<00:05:27.430> you<00:05:27.640> can 00:05:27.810 --> 00:05:27.820 align:start position:0% implements of them so from these you can 00:05:27.820 --> 00:05:29.760 align:start position:0% implements of them so from these you can create<00:05:27.940> your<00:05:28.150> iips<00:05:28.630> and<00:05:28.930> you<00:05:28.990> can<00:05:29.169> target<00:05:29.410> any 00:05:29.760 --> 00:05:29.770 align:start position:0% create your iips and you can target any 00:05:29.770 --> 00:05:31.770 align:start position:0% create your iips and you can target any of<00:05:30.040> those<00:05:30.190> three<00:05:30.460> platforms<00:05:30.760> right<00:05:31.090> now<00:05:31.270> to 00:05:31.770 --> 00:05:31.780 align:start position:0% of those three platforms right now to 00:05:31.780 --> 00:05:34.470 align:start position:0% of those three platforms right now to generate<00:05:31.960> your<00:05:32.290> reference<00:05:32.710> tests<00:05:33.150> to<00:05:34.150> create 00:05:34.470 --> 00:05:34.480 align:start position:0% generate your reference tests to create 00:05:34.480 --> 00:05:36.450 align:start position:0% generate your reference tests to create an<00:05:34.570> EIP<00:05:34.810> to<00:05:35.110> test<00:05:35.350> so<00:05:35.530> we<00:05:35.620> are<00:05:35.740> not<00:05:35.860> tied<00:05:36.220> to 00:05:36.450 --> 00:05:36.460 align:start position:0% an EIP to test so we are not tied to 00:05:36.460 --> 00:05:38.280 align:start position:0% an EIP to test so we are not tied to just<00:05:36.669> one<00:05:36.940> implementation<00:05:37.720> and<00:05:37.900> one 00:05:38.280 --> 00:05:38.290 align:start position:0% just one implementation and one 00:05:38.290 --> 00:05:40.140 align:start position:0% just one implementation and one implementer<00:05:38.830> to<00:05:39.400> produce<00:05:39.610> the<00:05:39.850> reference 00:05:40.140 --> 00:05:40.150 align:start position:0% implementer to produce the reference 00:05:40.150 --> 00:05:44.130 align:start position:0% implementer to produce the reference tests<00:05:40.450> anymore<00:05:42.330> the<00:05:43.330> second<00:05:43.660> idea<00:05:43.720> that<00:05:43.990> came 00:05:44.130 --> 00:05:44.140 align:start position:0% tests anymore the second idea that came 00:05:44.140 --> 00:05:46.500 align:start position:0% tests anymore the second idea that came up<00:05:44.290> as<00:05:44.440> a<00:05:44.470> need<00:05:44.680> for<00:05:44.830> EIP<00:05:45.130> champions<00:05:45.730> on<00:05:46.240> this 00:05:46.500 --> 00:05:46.510 align:start position:0% up as a need for EIP champions on this 00:05:46.510 --> 00:05:48.630 align:start position:0% up as a need for EIP champions on this is<00:05:46.630> a<00:05:46.660> picture<00:05:46.930> of<00:05:47.050> tweets<00:05:47.710> from<00:05:48.040> the<00:05:48.220> berlin 00:05:48.630 --> 00:05:48.640 align:start position:0% is a picture of tweets from the berlin 00:05:48.640 --> 00:05:51.000 align:start position:0% is a picture of tweets from the berlin all-court<00:05:49.060> devs<00:05:49.270> meeting<00:05:49.690> and<00:05:49.860> from<00:05:50.860> there 00:05:51.000 --> 00:05:51.010 align:start position:0% all-court devs meeting and from there 00:05:51.010 --> 00:05:54.450 align:start position:0% all-court devs meeting and from there alyx<00:05:52.260> different<00:05:53.260> different<00:05:53.620> alexei<00:05:54.040> but<00:05:54.160> alex 00:05:54.450 --> 00:05:54.460 align:start position:0% alyx different different alexei but alex 00:05:54.460 --> 00:05:56.760 align:start position:0% alyx different different alexei but alex proposed<00:05:54.820> that<00:05:55.300> each<00:05:55.360> AIP<00:05:55.870> needs<00:05:56.200> a<00:05:56.320> champion 00:05:56.760 --> 00:05:56.770 align:start position:0% proposed that each AIP needs a champion 00:05:56.770 --> 00:05:59.610 align:start position:0% proposed that each AIP needs a champion and<00:05:56.860> boris<00:05:57.160> echoed<00:05:57.490> it<00:05:57.580> said<00:05:57.790> yes<00:05:58.030> the<00:05:58.930> IPS 00:05:59.610 --> 00:05:59.620 align:start position:0% and boris echoed it said yes the IPS 00:05:59.620 --> 00:06:01.409 align:start position:0% and boris echoed it said yes the IPS need<00:05:59.830> a<00:06:00.010> human<00:06:00.400> being<00:06:00.610> that<00:06:00.880> we<00:06:01.030> can<00:06:01.210> go<00:06:01.360> to 00:06:01.409 --> 00:06:01.419 align:start position:0% need a human being that we can go to 00:06:01.419 --> 00:06:03.990 align:start position:0% need a human being that we can go to then<00:06:02.169> we<00:06:02.260> can<00:06:02.440> talk<00:06:02.650> to<00:06:02.860> and<00:06:03.040> say<00:06:03.220> hey<00:06:03.400> what<00:06:03.880> is 00:06:03.990 --> 00:06:04.000 align:start position:0% then we can talk to and say hey what is 00:06:04.000 --> 00:06:06.480 align:start position:0% then we can talk to and say hey what is the<00:06:04.120> status<00:06:04.390> of<00:06:04.479> api<00:06:04.720> p1<00:06:05.680> human<00:06:06.040> that<00:06:06.130> you<00:06:06.280> call 00:06:06.480 --> 00:06:06.490 align:start position:0% the status of api p1 human that you call 00:06:06.490 --> 00:06:08.390 align:start position:0% the status of api p1 human that you call into<00:06:06.729> the<00:06:06.880> alcor<00:06:07.210> devs<00:06:07.390> call<00:06:07.600> and<00:06:07.780> say<00:06:07.930> hey 00:06:08.390 --> 00:06:08.400 align:start position:0% into the alcor devs call and say hey 00:06:08.400 --> 00:06:11.219 align:start position:0% into the alcor devs call and say hey state<00:06:09.400> rent<00:06:09.640> is<00:06:09.820> going<00:06:10.150> more<00:06:10.300> into<00:06:10.510> stateless 00:06:11.219 --> 00:06:11.229 align:start position:0% state rent is going more into stateless 00:06:11.229 --> 00:06:12.630 align:start position:0% state rent is going more into stateless clients<00:06:11.650> right<00:06:11.770> now<00:06:11.800> so<00:06:12.100> you<00:06:12.160> won't<00:06:12.310> be<00:06:12.400> seeing 00:06:12.630 --> 00:06:12.640 align:start position:0% clients right now so you won't be seeing 00:06:12.640 --> 00:06:14.659 align:start position:0% clients right now so you won't be seeing this<00:06:12.760> for<00:06:12.940> a<00:06:13.030> while<00:06:13.150> it<00:06:13.450> needs<00:06:13.900> one<00:06:14.110> human<00:06:14.500> who 00:06:14.659 --> 00:06:14.669 align:start position:0% this for a while it needs one human who 00:06:14.669 --> 00:06:17.130 align:start position:0% this for a while it needs one human who coordinates<00:06:15.669> so<00:06:16.210> when<00:06:16.300> we<00:06:16.390> say<00:06:16.600> hey<00:06:16.810> we<00:06:16.840> need 00:06:17.130 --> 00:06:17.140 align:start position:0% coordinates so when we say hey we need 00:06:17.140 --> 00:06:20.430 align:start position:0% coordinates so when we say hey we need more<00:06:17.350> tests<00:06:17.770> for<00:06:17.890> a<00:06:17.979> IP<00:06:18.870> 2200<00:06:19.870> that<00:06:20.229> we<00:06:20.290> can 00:06:20.430 --> 00:06:20.440 align:start position:0% more tests for a IP 2200 that we can 00:06:20.440 --> 00:06:21.750 align:start position:0% more tests for a IP 2200 that we can talk<00:06:20.620> to<00:06:20.740> that<00:06:20.770> person<00:06:20.890> that<00:06:21.280> can<00:06:21.340> go<00:06:21.520> back<00:06:21.669> to 00:06:21.750 --> 00:06:21.760 align:start position:0% talk to that person that can go back to 00:06:21.760 --> 00:06:23.159 align:start position:0% talk to that person that can go back to the<00:06:21.850> developers<00:06:22.240> and<00:06:22.479> they<00:06:22.600> can<00:06:22.750> create<00:06:22.930> those 00:06:23.159 --> 00:06:23.169 align:start position:0% the developers and they can create those 00:06:23.169 --> 00:06:25.500 align:start position:0% the developers and they can create those new<00:06:23.350> tests<00:06:23.800> it<00:06:24.370> is<00:06:24.490> not<00:06:24.669> just<00:06:24.910> one<00:06:25.060> person<00:06:25.419> do 00:06:25.500 --> 00:06:25.510 align:start position:0% new tests it is not just one person do 00:06:25.510 --> 00:06:27.510 align:start position:0% new tests it is not just one person do all<00:06:25.660> those<00:06:25.780> things<00:06:25.990> but<00:06:26.560> if<00:06:26.680> the<00:06:26.800> IP<00:06:27.010> is<00:06:27.250> small 00:06:27.510 --> 00:06:27.520 align:start position:0% all those things but if the IP is small 00:06:27.520 --> 00:06:28.830 align:start position:0% all those things but if the IP is small enough<00:06:27.640> where<00:06:27.940> the<00:06:28.000> person<00:06:28.270> is<00:06:28.300> dedicated 00:06:28.830 --> 00:06:28.840 align:start position:0% enough where the person is dedicated 00:06:28.840 --> 00:06:30.150 align:start position:0% enough where the person is dedicated enough<00:06:29.080> it<00:06:29.320> could<00:06:29.770> be<00:06:29.919> the<00:06:30.010> person 00:06:30.150 --> 00:06:30.160 align:start position:0% enough it could be the person 00:06:30.160 --> 00:06:32.159 align:start position:0% enough it could be the person implementing<00:06:30.729> it<00:06:30.820> but<00:06:31.390> it<00:06:31.510> is<00:06:31.600> one<00:06:31.750> person<00:06:32.080> who 00:06:32.159 --> 00:06:32.169 align:start position:0% implementing it but it is one person who 00:06:32.169 --> 00:06:33.630 align:start position:0% implementing it but it is one person who coordinates<00:06:32.320> and<00:06:32.860> is<00:06:32.919> accountable<00:06:33.130> and 00:06:33.630 --> 00:06:33.640 align:start position:0% coordinates and is accountable and 00:06:33.640 --> 00:06:35.969 align:start position:0% coordinates and is accountable and champions<00:06:34.570> the<00:06:34.690> EIP<00:06:34.900> through<00:06:35.380> the<00:06:35.500> process 00:06:35.969 --> 00:06:35.979 align:start position:0% champions the EIP through the process 00:06:35.979 --> 00:06:40.090 align:start position:0% champions the EIP through the process taking<00:06:36.580> it<00:06:36.820> through<00:06:37.000> the<00:06:37.090> steps<00:06:37.330> as<00:06:37.510> available 00:06:40.090 --> 00:06:40.100 align:start position:0% 00:06:40.100 --> 00:06:42.160 align:start position:0% and<00:06:40.220> another<00:06:41.030> big<00:06:41.240> idea<00:06:41.390> that<00:06:41.570> was<00:06:41.750> introduced 00:06:42.160 --> 00:06:42.170 align:start position:0% and another big idea that was introduced 00:06:42.170 --> 00:06:44.410 align:start position:0% and another big idea that was introduced this<00:06:42.290> year<00:06:42.350> is<00:06:42.770> the<00:06:42.950> concept<00:06:43.400> of<00:06:43.520> a<00:06:43.730> IP<00:06:43.910> centric 00:06:44.410 --> 00:06:44.420 align:start position:0% this year is the concept of a IP centric 00:06:44.420 --> 00:06:46.420 align:start position:0% this year is the concept of a IP centric 4<00:06:44.630> key<00:06:44.780> this<00:06:45.230> was<00:06:45.410> brought<00:06:45.590> forward<00:06:45.830> by<00:06:46.040> Martin 00:06:46.420 --> 00:06:46.430 align:start position:0% 4 key this was brought forward by Martin 00:06:46.430 --> 00:06:48.160 align:start position:0% 4 key this was brought forward by Martin and<00:06:46.520> the<00:06:46.640> theorem<00:06:46.910> foundation<00:06:47.420> and<00:06:47.690> the 00:06:48.160 --> 00:06:48.170 align:start position:0% and the theorem foundation and the 00:06:48.170 --> 00:06:50.080 align:start position:0% and the theorem foundation and the general<00:06:48.530> idea<00:06:48.830> is<00:06:48.920> that<00:06:49.280> instead<00:06:49.610> of<00:06:49.880> having 00:06:50.080 --> 00:06:50.090 align:start position:0% general idea is that instead of having 00:06:50.090 --> 00:06:52.000 align:start position:0% general idea is that instead of having all<00:06:50.360> our<00:06:50.570> apes<00:06:50.750> move<00:06:51.110> to<00:06:51.320> the<00:06:51.440> various<00:06:51.740> stages 00:06:52.000 --> 00:06:52.010 align:start position:0% all our apes move to the various stages 00:06:52.010 --> 00:06:55.390 align:start position:0% all our apes move to the various stages of<00:06:52.190> the<00:06:52.400> upgrade<00:06:52.730> in<00:06:52.970> a<00:06:53.270> at<00:06:53.930> the<00:06:54.050> same<00:06:54.230> time<00:06:54.740> you 00:06:55.390 --> 00:06:55.400 align:start position:0% of the upgrade in a at the same time you 00:06:55.400 --> 00:06:57.640 align:start position:0% of the upgrade in a at the same time you have<00:06:55.550> each<00:06:55.820> a<00:06:56.090> progress<00:06:56.570> independently<00:06:57.380> and 00:06:57.640 --> 00:06:57.650 align:start position:0% have each a progress independently and 00:06:57.650 --> 00:06:59.140 align:start position:0% have each a progress independently and you<00:06:57.770> only<00:06:57.950> schedule<00:06:58.400> them<00:06:58.550> for<00:06:58.670> an<00:06:58.730> upgrade 00:06:59.140 --> 00:06:59.150 align:start position:0% you only schedule them for an upgrade 00:06:59.150 --> 00:07:00.430 align:start position:0% you only schedule them for an upgrade when<00:06:59.450> they<00:06:59.570> get<00:06:59.690> to<00:06:59.840> a<00:06:59.870> point<00:07:00.080> where<00:07:00.320> they're 00:07:00.430 --> 00:07:00.440 align:start position:0% when they get to a point where they're 00:07:00.440 --> 00:07:03.610 align:start position:0% when they get to a point where they're ready<00:07:00.620> to<00:07:00.710> do<00:07:00.920> so<00:07:01.160> so<00:07:02.030> using<00:07:02.840> this<00:07:02.960> model<00:07:03.350> if 00:07:03.610 --> 00:07:03.620 align:start position:0% ready to do so so using this model if 00:07:03.620 --> 00:07:05.350 align:start position:0% ready to do so so using this model if you<00:07:03.680> wanted<00:07:04.010> to<00:07:04.070> get<00:07:04.190> an<00:07:04.310> e<00:07:04.460> plive<00:07:04.790> on<00:07:04.970> main<00:07:05.150> net 00:07:05.350 --> 00:07:05.360 align:start position:0% you wanted to get an e plive on main net 00:07:05.360 --> 00:07:07.000 align:start position:0% you wanted to get an e plive on main net the<00:07:05.780> way<00:07:05.900> you<00:07:05.960> would<00:07:06.170> go<00:07:06.320> about<00:07:06.500> it<00:07:06.680> is<00:07:06.830> this 00:07:07.000 --> 00:07:07.010 align:start position:0% the way you would go about it is this 00:07:07.010 --> 00:07:08.890 align:start position:0% the way you would go about it is this you<00:07:07.610> start<00:07:07.850> you<00:07:08.120> first<00:07:08.390> start<00:07:08.570> by<00:07:08.690> writing 00:07:08.890 --> 00:07:08.900 align:start position:0% you start you first start by writing 00:07:08.900 --> 00:07:11.170 align:start position:0% you start you first start by writing your<00:07:09.080> EEP<00:07:09.290> and<00:07:09.500> then<00:07:10.070> you'll<00:07:10.400> go<00:07:10.580> on<00:07:10.790> all<00:07:10.970> core 00:07:11.170 --> 00:07:11.180 align:start position:0% your EEP and then you'll go on all core 00:07:11.180 --> 00:07:12.790 align:start position:0% your EEP and then you'll go on all core devs<00:07:11.390> to<00:07:11.660> get<00:07:11.810> what<00:07:12.020> is<00:07:12.140> called<00:07:12.290> an<00:07:12.560> initial 00:07:12.790 --> 00:07:12.800 align:start position:0% devs to get what is called an initial 00:07:12.800 --> 00:07:14.950 align:start position:0% devs to get what is called an initial acceptance<00:07:13.310> this<00:07:14.300> means<00:07:14.540> that<00:07:14.690> the<00:07:14.810> core 00:07:14.950 --> 00:07:14.960 align:start position:0% acceptance this means that the core 00:07:14.960 --> 00:07:16.270 align:start position:0% acceptance this means that the core developers<00:07:15.410> are<00:07:15.680> generally<00:07:16.100> positive 00:07:16.270 --> 00:07:16.280 align:start position:0% developers are generally positive 00:07:16.280 --> 00:07:18.250 align:start position:0% developers are generally positive towards<00:07:16.820> your<00:07:16.940> idea<00:07:17.270> and<00:07:17.510> that<00:07:17.570> assuming 00:07:18.250 --> 00:07:18.260 align:start position:0% towards your idea and that assuming 00:07:18.260 --> 00:07:19.660 align:start position:0% towards your idea and that assuming everything<00:07:18.620> goes<00:07:18.800> well<00:07:18.950> on<00:07:19.010> the<00:07:19.220> next<00:07:19.460> steps 00:07:19.660 --> 00:07:19.670 align:start position:0% everything goes well on the next steps 00:07:19.670 --> 00:07:22.270 align:start position:0% everything goes well on the next steps it<00:07:19.970> except<00:07:20.300> a<00:07:20.390> PR<00:07:20.720> for<00:07:21.050> a<00:07:21.590> well-written 00:07:22.270 --> 00:07:22.280 align:start position:0% it except a PR for a well-written 00:07:22.280 --> 00:07:23.710 align:start position:0% it except a PR for a well-written implementation<00:07:23.030> of<00:07:23.120> your<00:07:23.240> EEP<00:07:23.360> in<00:07:23.540> their 00:07:23.710 --> 00:07:23.720 align:start position:0% implementation of your EEP in their 00:07:23.720 --> 00:07:25.570 align:start position:0% implementation of your EEP in their client<00:07:24.110> and<00:07:24.290> this<00:07:25.010> can<00:07:25.160> be<00:07:25.280> a<00:07:25.310> really<00:07:25.490> useful 00:07:25.570 --> 00:07:25.580 align:start position:0% client and this can be a really useful 00:07:25.580 --> 00:07:27.820 align:start position:0% client and this can be a really useful signaling<00:07:26.300> mechanism<00:07:26.810> for<00:07:27.140> organizations 00:07:27.820 --> 00:07:27.830 align:start position:0% signaling mechanism for organizations 00:07:27.830 --> 00:07:29.470 align:start position:0% signaling mechanism for organizations that<00:07:28.010> fund<00:07:28.250> some<00:07:28.520> of<00:07:28.550> the<00:07:28.730> teams<00:07:28.970> working<00:07:29.270> on 00:07:29.470 --> 00:07:29.480 align:start position:0% that fund some of the teams working on 00:07:29.480 --> 00:07:31.390 align:start position:0% that fund some of the teams working on these<00:07:29.600> eats<00:07:30.050> organiz<00:07:30.950> I<00:07:31.010> see<00:07:31.070> organizations 00:07:31.390 --> 00:07:31.400 align:start position:0% these eats organiz I see organizations 00:07:31.400 --> 00:07:33.790 align:start position:0% these eats organiz I see organizations like<00:07:32.210> the<00:07:32.330> EF<00:07:32.510> like<00:07:32.960> Malik<00:07:33.290> Dow<00:07:33.440> or<00:07:33.680> like 00:07:33.790 --> 00:07:33.800 align:start position:0% like the EF like Malik Dow or like 00:07:33.800 --> 00:07:35.590 align:start position:0% like the EF like Malik Dow or like consensus<00:07:34.310> can<00:07:34.790> use<00:07:35.000> this<00:07:35.150> initially 00:07:35.590 --> 00:07:35.600 align:start position:0% consensus can use this initially 00:07:35.600 --> 00:07:37.120 align:start position:0% consensus can use this initially acceptance<00:07:36.050> status<00:07:36.380> to<00:07:36.650> note<00:07:36.800> that<00:07:36.830> their 00:07:37.120 --> 00:07:37.130 align:start position:0% acceptance status to note that their 00:07:37.130 --> 00:07:38.710 align:start position:0% acceptance status to note that their funding<00:07:37.430> in<00:07:37.580> efforts<00:07:37.910> that<00:07:38.150> has<00:07:38.300> a<00:07:38.330> fairly 00:07:38.710 --> 00:07:38.720 align:start position:0% funding in efforts that has a fairly 00:07:38.720 --> 00:07:41.040 align:start position:0% funding in efforts that has a fairly high<00:07:38.750> likelihood<00:07:39.140> of<00:07:39.560> making<00:07:39.980> it<00:07:40.250> on<00:07:40.310> main<00:07:40.520> net 00:07:41.040 --> 00:07:41.050 align:start position:0% high likelihood of making it on main net 00:07:41.050 --> 00:07:43.780 align:start position:0% high likelihood of making it on main net so<00:07:42.050> once<00:07:42.230> you<00:07:42.350> have<00:07:42.470> this<00:07:42.650> initial<00:07:43.490> acceptance 00:07:43.780 --> 00:07:43.790 align:start position:0% so once you have this initial acceptance 00:07:43.790 --> 00:07:46.000 align:start position:0% so once you have this initial acceptance stamp<00:07:44.180> you<00:07:44.750> go<00:07:45.020> and<00:07:45.290> work<00:07:45.470> on<00:07:45.590> your<00:07:45.710> reference 00:07:46.000 --> 00:07:46.010 align:start position:0% stamp you go and work on your reference 00:07:46.010 --> 00:07:47.530 align:start position:0% stamp you go and work on your reference implementation<00:07:46.640> this<00:07:47.000> just<00:07:47.360> means 00:07:47.530 --> 00:07:47.540 align:start position:0% implementation this just means 00:07:47.540 --> 00:07:48.910 align:start position:0% implementation this just means implementing<00:07:48.080> your<00:07:48.170> EEP<00:07:48.320> against<00:07:48.590> one<00:07:48.740> of<00:07:48.830> the 00:07:48.910 --> 00:07:48.920 align:start position:0% implementing your EEP against one of the 00:07:48.920 --> 00:07:51.190 align:start position:0% implementing your EEP against one of the major<00:07:49.100> clients<00:07:49.610> and<00:07:49.790> then<00:07:50.300> generate<00:07:51.080> your 00:07:51.190 --> 00:07:51.200 align:start position:0% major clients and then generate your 00:07:51.200 --> 00:07:53.010 align:start position:0% major clients and then generate your reference<00:07:51.950> tests<00:07:52.280> using<00:07:52.460> region<00:07:52.790> instead 00:07:53.010 --> 00:07:53.020 align:start position:0% reference tests using region instead 00:07:53.020 --> 00:07:55.000 align:start position:0% reference tests using region instead this<00:07:54.020> would<00:07:54.170> kick<00:07:54.320> off<00:07:54.440> a<00:07:54.500> security 00:07:55.000 --> 00:07:55.010 align:start position:0% this would kick off a security 00:07:55.010 --> 00:07:56.920 align:start position:0% this would kick off a security evaluation<00:07:55.160> period<00:07:55.730> of<00:07:55.970> your<00:07:56.090> EEP<00:07:56.300> where<00:07:56.810> you 00:07:56.920 --> 00:07:56.930 align:start position:0% evaluation period of your EEP where you 00:07:56.930 --> 00:07:58.600 align:start position:0% evaluation period of your EEP where you want<00:07:57.170> to<00:07:57.290> reach<00:07:57.440> out<00:07:57.620> to<00:07:57.770> people<00:07:57.890> in<00:07:58.160> aetherium 00:07:58.600 --> 00:07:58.610 align:start position:0% want to reach out to people in aetherium 00:07:58.610 --> 00:07:59.980 align:start position:0% want to reach out to people in aetherium who<00:07:58.850> are<00:07:58.910> familiar<00:07:59.300> with<00:07:59.420> the<00:07:59.570> bits<00:07:59.750> of<00:07:59.900> the 00:07:59.980 --> 00:07:59.990 align:start position:0% who are familiar with the bits of the 00:07:59.990 --> 00:08:01.600 align:start position:0% who are familiar with the bits of the system<00:08:00.320> you're<00:08:00.410> changing<00:08:00.890> so<00:08:01.250> that<00:08:01.280> they<00:08:01.460> can 00:08:01.600 --> 00:08:01.610 align:start position:0% system you're changing so that they can 00:08:01.610 --> 00:08:03.580 align:start position:0% system you're changing so that they can poke<00:08:01.820> at<00:08:01.970> your<00:08:02.120> eek<00:08:02.240> as<00:08:02.420> you're<00:08:03.140> going<00:08:03.320> through 00:08:03.580 --> 00:08:03.590 align:start position:0% poke at your eek as you're going through 00:08:03.590 --> 00:08:04.990 align:start position:0% poke at your eek as you're going through all<00:08:03.680> of<00:08:03.710> this<00:08:03.950> you<00:08:04.280> want<00:08:04.460> to<00:08:04.550> feed<00:08:04.730> everything 00:08:04.990 --> 00:08:05.000 align:start position:0% all of this you want to feed everything 00:08:05.000 --> 00:08:06.310 align:start position:0% all of this you want to feed everything you<00:08:05.210> learned<00:08:05.420> back<00:08:05.690> into<00:08:05.990> your<00:08:06.140> each 00:08:06.310 --> 00:08:06.320 align:start position:0% you learned back into your each 00:08:06.320 --> 00:08:08.530 align:start position:0% you learned back into your each specification<00:08:06.710> and<00:08:07.370> specifically<00:08:08.210> under<00:08:08.420> the 00:08:08.530 --> 00:08:08.540 align:start position:0% specification and specifically under the 00:08:08.540 --> 00:08:11.470 align:start position:0% specification and specifically under the security<00:08:08.930> consideration<00:08:09.620> section<00:08:10.480> once 00:08:11.470 --> 00:08:11.480 align:start position:0% security consideration section once 00:08:11.480 --> 00:08:12.970 align:start position:0% security consideration section once you've<00:08:11.600> done<00:08:11.750> all<00:08:11.810> that<00:08:11.990> so<00:08:12.470> you've<00:08:12.650> got<00:08:12.860> in 00:08:12.970 --> 00:08:12.980 align:start position:0% you've done all that so you've got in 00:08:12.980 --> 00:08:14.380 align:start position:0% you've done all that so you've got in your<00:08:13.070> initial<00:08:13.250> acceptance<00:08:13.670> your<00:08:14.060> reference 00:08:14.380 --> 00:08:14.390 align:start position:0% your initial acceptance your reference 00:08:14.390 --> 00:08:16.540 align:start position:0% your initial acceptance your reference implementation<00:08:15.080> and<00:08:15.380> your<00:08:15.470> testing<00:08:15.890> you<00:08:16.340> want 00:08:16.540 --> 00:08:16.550 align:start position:0% implementation and your testing you want 00:08:16.550 --> 00:08:18.220 align:start position:0% implementation and your testing you want to<00:08:16.640> go<00:08:16.760> back<00:08:17.000> on<00:08:17.210> our<00:08:17.390> core<00:08:17.570> devs<00:08:17.780> to<00:08:17.960> get<00:08:18.080> your 00:08:18.220 --> 00:08:18.230 align:start position:0% to go back on our core devs to get your 00:08:18.230 --> 00:08:21.070 align:start position:0% to go back on our core devs to get your eat<00:08:18.410> move<00:08:18.680> to<00:08:18.950> accepted<00:08:19.430> at<00:08:20.300> that<00:08:20.510> point<00:08:20.780> all 00:08:21.070 --> 00:08:21.080 align:start position:0% eat move to accepted at that point all 00:08:21.080 --> 00:08:22.240 align:start position:0% eat move to accepted at that point all the<00:08:21.230> other<00:08:21.380> maintenance<00:08:21.620> lions<00:08:22.100> will 00:08:22.240 --> 00:08:22.250 align:start position:0% the other maintenance lions will 00:08:22.250 --> 00:08:23.380 align:start position:0% the other maintenance lions will implement<00:08:22.550> it<00:08:22.760> and<00:08:23.000> then<00:08:23.150> they'll<00:08:23.270> be 00:08:23.380 --> 00:08:23.390 align:start position:0% implement it and then they'll be 00:08:23.390 --> 00:08:25.420 align:start position:0% implement it and then they'll be scheduled<00:08:23.750> for<00:08:23.810> a<00:08:23.930> test<00:08:24.080> net<00:08:24.260> upgrade<00:08:24.620> once 00:08:25.420 --> 00:08:25.430 align:start position:0% scheduled for a test net upgrade once 00:08:25.430 --> 00:08:26.920 align:start position:0% scheduled for a test net upgrade once that<00:08:25.610> upgrade<00:08:25.970> goes<00:08:26.150> live<00:08:26.420> assuming 00:08:26.920 --> 00:08:26.930 align:start position:0% that upgrade goes live assuming 00:08:26.930 --> 00:08:28.720 align:start position:0% that upgrade goes live assuming everything<00:08:27.050> is<00:08:27.410> fine<00:08:27.950> then<00:08:28.460> it'll<00:08:28.670> be 00:08:28.720 --> 00:08:28.730 align:start position:0% everything is fine then it'll be 00:08:28.730 --> 00:08:30.130 align:start position:0% everything is fine then it'll be scheduled<00:08:29.090> for<00:08:29.210> main<00:08:29.360> net<00:08:29.540> and<00:08:29.750> will<00:08:30.050> be 00:08:30.130 --> 00:08:30.140 align:start position:0% scheduled for main net and will be 00:08:30.140 --> 00:08:32.760 align:start position:0% scheduled for main net and will be deployed<00:08:30.470> on<00:08:30.650> the<00:08:30.920> maximum<00:08:31.610> net<00:08:31.760> upgrade<00:08:32.090> and 00:08:32.760 --> 00:08:32.770 align:start position:0% deployed on the maximum net upgrade and 00:08:32.770 --> 00:08:35.110 align:start position:0% deployed on the maximum net upgrade and James<00:08:33.770> Hancock<00:08:34.160> put<00:08:34.370> together<00:08:34.490> a<00:08:34.700> really<00:08:34.970> good 00:08:35.110 --> 00:08:35.120 align:start position:0% James Hancock put together a really good 00:08:35.120 --> 00:08:38.020 align:start position:0% James Hancock put together a really good diagram<00:08:35.570> to<00:08:35.780> explain<00:08:35.810> this<00:08:36.169> process<00:08:36.430> so<00:08:37.430> you 00:08:38.020 --> 00:08:38.030 align:start position:0% diagram to explain this process so you 00:08:38.030 --> 00:08:39.670 align:start position:0% diagram to explain this process so you see<00:08:38.210> it<00:08:38.300> step<00:08:38.479> 0<00:08:38.840> you<00:08:38.900> start<00:08:39.260> off<00:08:39.349> with<00:08:39.530> your 00:08:39.670 --> 00:08:39.680 align:start position:0% see it step 0 you start off with your 00:08:39.680 --> 00:08:41.770 align:start position:0% see it step 0 you start off with your draft<00:08:39.950> of<00:08:40.130> an<00:08:40.220> deep<00:08:40.340> and<00:08:41.180> they're<00:08:41.419> the<00:08:41.630> only 00:08:41.770 --> 00:08:41.780 align:start position:0% draft of an deep and they're the only 00:08:41.780 --> 00:08:43.570 align:start position:0% draft of an deep and they're the only Gaming<00:08:42.200> function<00:08:42.560> is<00:08:42.800> you<00:08:43.130> need<00:08:43.280> to<00:08:43.310> get<00:08:43.460> it 00:08:43.570 --> 00:08:43.580 align:start position:0% Gaming function is you need to get it 00:08:43.580 --> 00:08:45.760 align:start position:0% Gaming function is you need to get it approved<00:08:43.820> by<00:08:43.940> EIP<00:08:44.330> editors<00:08:44.900> this<00:08:45.380> just<00:08:45.590> means 00:08:45.760 --> 00:08:45.770 align:start position:0% approved by EIP editors this just means 00:08:45.770 --> 00:08:47.590 align:start position:0% approved by EIP editors this just means your<00:08:45.920> EEP<00:08:46.100> meets<00:08:46.460> the<00:08:46.640> basic<00:08:46.970> templates 00:08:47.590 --> 00:08:47.600 align:start position:0% your EEP meets the basic templates 00:08:47.600 --> 00:08:49.840 align:start position:0% your EEP meets the basic templates requirements<00:08:48.350> from<00:08:49.100> there<00:08:49.340> you<00:08:49.460> get<00:08:49.580> a<00:08:49.640> green 00:08:49.840 --> 00:08:49.850 align:start position:0% requirements from there you get a green 00:08:49.850 --> 00:08:51.610 align:start position:0% requirements from there you get a green light<00:08:50.060> from<00:08:50.210> all<00:08:50.390> core<00:08:50.540> devs<00:08:50.780> or<00:08:51.050> an<00:08:51.200> initial 00:08:51.610 --> 00:08:51.620 align:start position:0% light from all core devs or an initial 00:08:51.620 --> 00:08:53.050 align:start position:0% light from all core devs or an initial acceptance<00:08:51.920> which<00:08:52.550> means<00:08:52.790> that<00:08:52.940> they're 00:08:53.050 --> 00:08:53.060 align:start position:0% acceptance which means that they're 00:08:53.060 --> 00:08:53.470 align:start position:0% acceptance which means that they're generally 00:08:53.470 --> 00:08:53.480 align:start position:0% generally 00:08:53.480 --> 00:08:55.150 align:start position:0% generally positive<00:08:53.839> towards<00:08:54.079> your<00:08:54.199> idea<00:08:54.560> and<00:08:54.829> that<00:08:54.920> did 00:08:55.150 --> 00:08:55.160 align:start position:0% positive towards your idea and that did 00:08:55.160 --> 00:08:56.829 align:start position:0% positive towards your idea and that did accept<00:08:55.459> a<00:08:55.550> good<00:08:55.670> PR<00:08:56.000> from<00:08:56.120> it<00:08:56.300> in<00:08:56.480> their 00:08:56.829 --> 00:08:56.839 align:start position:0% accept a good PR from it in their 00:08:56.839 --> 00:08:58.540 align:start position:0% accept a good PR from it in their codebase<00:08:57.230> you<00:08:57.829> start<00:08:58.040> working<00:08:58.370> on<00:08:58.430> your 00:08:58.540 --> 00:08:58.550 align:start position:0% codebase you start working on your 00:08:58.550 --> 00:09:00.550 align:start position:0% codebase you start working on your implementation<00:08:59.240> and<00:08:59.540> then<00:08:59.870> you<00:09:00.230> own<00:09:00.380> the 00:09:00.550 --> 00:09:00.560 align:start position:0% implementation and then you own the 00:09:00.560 --> 00:09:02.470 align:start position:0% implementation and then you own the testing<00:09:00.920> for<00:09:01.130> it<00:09:01.220> so<00:09:01.790> not<00:09:01.910> only<00:09:02.060> are<00:09:02.449> you 00:09:02.470 --> 00:09:02.480 align:start position:0% testing for it so not only are you 00:09:02.480 --> 00:09:04.960 align:start position:0% testing for it so not only are you generating<00:09:03.230> the<00:09:03.350> reference<00:09:03.680> tests<00:09:04.040> and 00:09:04.960 --> 00:09:04.970 align:start position:0% generating the reference tests and 00:09:04.970 --> 00:09:06.879 align:start position:0% generating the reference tests and trying<00:09:05.600> to<00:09:05.690> test<00:09:05.899> both<00:09:06.079> the<00:09:06.110> happy<00:09:06.500> path<00:09:06.680> as 00:09:06.879 --> 00:09:06.889 align:start position:0% trying to test both the happy path as 00:09:06.889 --> 00:09:08.980 align:start position:0% trying to test both the happy path as well<00:09:07.010> as<00:09:07.100> the<00:09:07.220> quirks<00:09:07.490> and<00:09:07.730> edge<00:09:08.389> cases<00:09:08.720> very 00:09:08.980 --> 00:09:08.990 align:start position:0% well as the quirks and edge cases very 00:09:08.990 --> 00:09:11.860 align:start position:0% well as the quirks and edge cases very specific<00:09:09.440> eats<00:09:10.029> but<00:09:11.029> you<00:09:11.209> also<00:09:11.420> want<00:09:11.690> to<00:09:11.750> get 00:09:11.860 --> 00:09:11.870 align:start position:0% specific eats but you also want to get 00:09:11.870 --> 00:09:13.629 align:start position:0% specific eats but you also want to get in<00:09:11.990> touch<00:09:12.170> with<00:09:12.199> the<00:09:12.529> EF<00:09:12.829> testing<00:09:13.220> team<00:09:13.430> and 00:09:13.629 --> 00:09:13.639 align:start position:0% in touch with the EF testing team and 00:09:13.639 --> 00:09:15.280 align:start position:0% in touch with the EF testing team and other<00:09:13.730> people<00:09:14.089> who<00:09:14.269> are<00:09:14.389> more<00:09:14.779> knowledgeable 00:09:15.280 --> 00:09:15.290 align:start position:0% other people who are more knowledgeable 00:09:15.290 --> 00:09:16.840 align:start position:0% other people who are more knowledgeable about<00:09:15.350> what<00:09:15.620> you're<00:09:15.769> changing<00:09:16.160> to<00:09:16.310> make<00:09:16.699> sure 00:09:16.840 --> 00:09:16.850 align:start position:0% about what you're changing to make sure 00:09:16.850 --> 00:09:18.370 align:start position:0% about what you're changing to make sure that<00:09:17.029> all<00:09:17.300> of<00:09:17.329> the<00:09:17.570> important<00:09:17.990> security 00:09:18.370 --> 00:09:18.380 align:start position:0% that all of the important security 00:09:18.380 --> 00:09:19.930 align:start position:0% that all of the important security considerations<00:09:19.010> get<00:09:19.250> fed<00:09:19.459> back<00:09:19.639> into<00:09:19.670> the 00:09:19.930 --> 00:09:19.940 align:start position:0% considerations get fed back into the 00:09:19.940 --> 00:09:22.240 align:start position:0% considerations get fed back into the spec<00:09:20.440> once<00:09:21.440> you've<00:09:21.560> done<00:09:21.680> all<00:09:21.740> that<00:09:21.860> you<00:09:22.130> go 00:09:22.240 --> 00:09:22.250 align:start position:0% spec once you've done all that you go 00:09:22.250 --> 00:09:23.949 align:start position:0% spec once you've done all that you go back<00:09:22.430> on<00:09:22.550> all<00:09:22.670> core<00:09:22.880> devs<00:09:23.089> get<00:09:23.360> your<00:09:23.540> eat<00:09:23.720> move 00:09:23.949 --> 00:09:23.959 align:start position:0% back on all core devs get your eat move 00:09:23.959 --> 00:09:25.840 align:start position:0% back on all core devs get your eat move to<00:09:24.110> accept<00:09:24.380> it<00:09:24.620> and<00:09:24.889> it'll<00:09:25.130> be<00:09:25.250> scheduled<00:09:25.670> for 00:09:25.840 --> 00:09:25.850 align:start position:0% to accept it and it'll be scheduled for 00:09:25.850 --> 00:09:27.879 align:start position:0% to accept it and it'll be scheduled for the<00:09:25.910> next<00:09:26.000> upgrade<00:09:26.540> at<00:09:26.779> that<00:09:27.380> point<00:09:27.649> it'll 00:09:27.879 --> 00:09:27.889 align:start position:0% the next upgrade at that point it'll 00:09:27.889 --> 00:09:29.379 align:start position:0% the next upgrade at that point it'll move<00:09:28.100> into<00:09:28.279> last<00:09:28.519> call<00:09:28.760> and<00:09:29.029> we'll<00:09:29.269> keep 00:09:29.379 --> 00:09:29.389 align:start position:0% move into last call and we'll keep 00:09:29.389 --> 00:09:30.939 align:start position:0% move into last call and we'll keep running<00:09:29.570> the<00:09:29.810> reference<00:09:30.170> test<00:09:30.380> against<00:09:30.709> it 00:09:30.939 --> 00:09:30.949 align:start position:0% running the reference test against it 00:09:30.949 --> 00:09:32.710 align:start position:0% running the reference test against it all<00:09:31.190> the<00:09:31.399> way<00:09:31.490> up<00:09:31.610> to<00:09:31.730> the<00:09:31.850> test<00:09:32.029> nut<00:09:32.240> block 00:09:32.710 --> 00:09:32.720 align:start position:0% all the way up to the test nut block 00:09:32.720 --> 00:09:34.269 align:start position:0% all the way up to the test nut block if<00:09:32.870> it<00:09:33.139> goes<00:09:33.260> live<00:09:33.470> on<00:09:33.620> the<00:09:33.740> test<00:09:33.949> nets<00:09:34.160> and 00:09:34.269 --> 00:09:34.279 align:start position:0% if it goes live on the test nets and 00:09:34.279 --> 00:09:35.740 align:start position:0% if it goes live on the test nets and everything<00:09:34.639> is<00:09:34.760> fine<00:09:34.940> then<00:09:35.420> it'll<00:09:35.660> be 00:09:35.740 --> 00:09:35.750 align:start position:0% everything is fine then it'll be 00:09:35.750 --> 00:09:37.600 align:start position:0% everything is fine then it'll be scheduled<00:09:36.050> for<00:09:36.199> main<00:09:36.350> net<00:09:36.560> and<00:09:36.800> finally<00:09:37.310> your 00:09:37.600 --> 00:09:37.610 align:start position:0% scheduled for main net and finally your 00:09:37.610 --> 00:09:41.949 align:start position:0% scheduled for main net and finally your equal<00:09:37.940> relies<00:09:38.209> on<00:09:38.389> main<00:09:38.720> net<00:09:40.630> finally<00:09:41.630> as<00:09:41.720> Tim 00:09:41.949 --> 00:09:41.959 align:start position:0% equal relies on main net finally as Tim 00:09:41.959 --> 00:09:43.629 align:start position:0% equal relies on main net finally as Tim mentioned<00:09:41.990> the<00:09:42.649> etherium<00:09:43.160> community<00:09:43.550> is 00:09:43.629 --> 00:09:43.639 align:start position:0% mentioned the etherium community is 00:09:43.639 --> 00:09:45.430 align:start position:0% mentioned the etherium community is growing<00:09:44.000> there's<00:09:44.570> more<00:09:44.779> people<00:09:44.990> that<00:09:45.139> we<00:09:45.290> need 00:09:45.430 --> 00:09:45.440 align:start position:0% growing there's more people that we need 00:09:45.440 --> 00:09:47.259 align:start position:0% growing there's more people that we need to<00:09:45.529> take<00:09:45.649> considerations<00:09:46.430> into<00:09:46.670> rather<00:09:47.000> than 00:09:47.259 --> 00:09:47.269 align:start position:0% to take considerations into rather than 00:09:47.269 --> 00:09:49.180 align:start position:0% to take considerations into rather than just<00:09:47.449> the<00:09:47.510> developers<00:09:48.050> and<00:09:48.230> the<00:09:48.290> researchers 00:09:49.180 --> 00:09:49.190 align:start position:0% just the developers and the researchers 00:09:49.190 --> 00:09:50.829 align:start position:0% just the developers and the researchers who<00:09:49.310> are<00:09:49.370> creating<00:09:49.670> these<00:09:49.790> items<00:09:50.120> we<00:09:50.690> have 00:09:50.829 --> 00:09:50.839 align:start position:0% who are creating these items we have 00:09:50.839 --> 00:09:53.920 align:start position:0% who are creating these items we have people<00:09:51.139> running<00:09:52.120> exchanges<00:09:53.120> that<00:09:53.600> people 00:09:53.920 --> 00:09:53.930 align:start position:0% people running exchanges that people 00:09:53.930 --> 00:09:55.120 align:start position:0% people running exchanges that people running<00:09:54.139> their<00:09:54.199> own<00:09:54.260> personal<00:09:54.709> Nords<00:09:54.980> for 00:09:55.120 --> 00:09:55.130 align:start position:0% running their own personal Nords for 00:09:55.130 --> 00:09:57.490 align:start position:0% running their own personal Nords for corporate<00:09:55.430> for<00:09:55.610> personal<00:09:56.449> information<00:09:56.570> we 00:09:57.490 --> 00:09:57.500 align:start position:0% corporate for personal information we 00:09:57.500 --> 00:09:59.259 align:start position:0% corporate for personal information we have<00:09:57.620> corporations<00:09:58.160> running<00:09:58.339> nodes<00:09:58.579> and<00:09:59.149> we 00:09:59.259 --> 00:09:59.269 align:start position:0% have corporations running nodes and we 00:09:59.269 --> 00:10:00.699 align:start position:0% have corporations running nodes and we have<00:09:59.449> service<00:09:59.839> providers<00:10:00.290> such<00:10:00.440> as<00:10:00.500> in 00:10:00.699 --> 00:10:00.709 align:start position:0% have service providers such as in 00:10:00.709 --> 00:10:02.500 align:start position:0% have service providers such as in Ferrara<00:10:01.069> that<00:10:01.519> run<00:10:01.730> these<00:10:01.819> aetherium<00:10:02.329> nodes 00:10:02.500 --> 00:10:02.510 align:start position:0% Ferrara that run these aetherium nodes 00:10:02.510 --> 00:10:03.939 align:start position:0% Ferrara that run these aetherium nodes and<00:10:03.260> when<00:10:03.410> you<00:10:03.500> know<00:10:03.589> take<00:10:03.740> into 00:10:03.939 --> 00:10:03.949 align:start position:0% and when you know take into 00:10:03.949 --> 00:10:06.639 align:start position:0% and when you know take into consideration<00:10:04.610> that<00:10:04.850> they<00:10:05.269> need<00:10:05.480> some<00:10:05.839> some 00:10:06.639 --> 00:10:06.649 align:start position:0% consideration that they need some some 00:10:06.649 --> 00:10:08.439 align:start position:0% consideration that they need some some standard<00:10:07.130> amount<00:10:07.430> of<00:10:07.610> time<00:10:07.880> to<00:10:08.209> react<00:10:08.420> to 00:10:08.439 --> 00:10:08.449 align:start position:0% standard amount of time to react to 00:10:08.449 --> 00:10:10.449 align:start position:0% standard amount of time to react to these<00:10:08.720> node<00:10:08.959> upgrades<00:10:09.350> so<00:10:09.980> a<00:10:10.010> few<00:10:10.190> months<00:10:10.370> ago 00:10:10.449 --> 00:10:10.459 align:start position:0% these node upgrades so a few months ago 00:10:10.459 --> 00:10:14.470 align:start position:0% these node upgrades so a few months ago I<00:10:10.550> proposed<00:10:11.000> a<00:10:11.269> IP<00:10:11.440> 1872<00:10:12.550> and<00:10:13.550> set<00:10:14.029> of<00:10:14.149> upgrade 00:10:14.470 --> 00:10:14.480 align:start position:0% I proposed a IP 1872 and set of upgrade 00:10:14.480 --> 00:10:18.220 align:start position:0% I proposed a IP 1872 and set of upgrade windows<00:10:14.660> to<00:10:16.000> tell<00:10:17.000> us<00:10:17.120> when<00:10:17.329> we<00:10:17.360> should<00:10:17.660> do<00:10:18.199> our 00:10:18.220 --> 00:10:18.230 align:start position:0% windows to tell us when we should do our 00:10:18.230 --> 00:10:19.600 align:start position:0% windows to tell us when we should do our network<00:10:18.589> upgrades<00:10:18.980> rather<00:10:19.220> than<00:10:19.430> just 00:10:19.600 --> 00:10:19.610 align:start position:0% network upgrades rather than just 00:10:19.610 --> 00:10:21.400 align:start position:0% network upgrades rather than just picking<00:10:19.819> a<00:10:20.000> date<00:10:20.180> random<00:10:20.630> date<00:10:20.779> when<00:10:21.290> we're 00:10:21.400 --> 00:10:21.410 align:start position:0% picking a date random date when we're 00:10:21.410 --> 00:10:23.050 align:start position:0% picking a date random date when we're ready<00:10:21.560> to<00:10:21.680> fork<00:10:21.949> so<00:10:22.670> there<00:10:22.790> were<00:10:22.850> several 00:10:23.050 --> 00:10:23.060 align:start position:0% ready to fork so there were several 00:10:23.060 --> 00:10:24.519 align:start position:0% ready to fork so there were several recommendations<00:10:23.389> in<00:10:23.899> there<00:10:23.990> some<00:10:24.260> of<00:10:24.319> these<00:10:24.410> I 00:10:24.519 --> 00:10:24.529 align:start position:0% recommendations in there some of these I 00:10:24.529 --> 00:10:26.439 align:start position:0% recommendations in there some of these I feel<00:10:24.680> stronger<00:10:25.160> about<00:10:25.250> than<00:10:25.550> others<00:10:25.760> the 00:10:26.439 --> 00:10:26.449 align:start position:0% feel stronger about than others the 00:10:26.449 --> 00:10:27.819 align:start position:0% feel stronger about than others the first<00:10:26.690> recommendation<00:10:26.899> that<00:10:27.440> I<00:10:27.529> feel<00:10:27.709> the 00:10:27.819 --> 00:10:27.829 align:start position:0% first recommendation that I feel the 00:10:27.829 --> 00:10:29.439 align:start position:0% first recommendation that I feel the most<00:10:27.949> strongest<00:10:28.220> about<00:10:28.579> is<00:10:28.970> that<00:10:29.180> we<00:10:29.269> should 00:10:29.439 --> 00:10:29.449 align:start position:0% most strongest about is that we should 00:10:29.449 --> 00:10:31.449 align:start position:0% most strongest about is that we should fork<00:10:29.690> on<00:10:29.839> the<00:10:29.899> third<00:10:30.319> Wednesday<00:10:30.589> of<00:10:30.829> a<00:10:31.220> month 00:10:31.449 --> 00:10:31.459 align:start position:0% fork on the third Wednesday of a month 00:10:31.459 --> 00:10:33.460 align:start position:0% fork on the third Wednesday of a month kind<00:10:32.360> of<00:10:32.420> like<00:10:32.510> how<00:10:32.660> Microsoft<00:10:32.990> has<00:10:33.350> their 00:10:33.460 --> 00:10:33.470 align:start position:0% kind of like how Microsoft has their 00:10:33.470 --> 00:10:34.750 align:start position:0% kind of like how Microsoft has their Patch<00:10:33.649> Tuesday<00:10:33.680> where<00:10:34.279> their<00:10:34.370> security 00:10:34.750 --> 00:10:34.760 align:start position:0% Patch Tuesday where their security 00:10:34.760 --> 00:10:36.579 align:start position:0% Patch Tuesday where their security patches<00:10:34.940> will<00:10:35.720> come<00:10:35.870> out<00:10:35.990> on<00:10:36.110> a<00:10:36.139> second 00:10:36.579 --> 00:10:36.589 align:start position:0% patches will come out on a second 00:10:36.589 --> 00:10:37.509 align:start position:0% patches will come out on a second Tuesday<00:10:36.860> of<00:10:36.889> the<00:10:36.980> month<00:10:37.010> unless<00:10:37.279> it's 00:10:37.509 --> 00:10:37.519 align:start position:0% Tuesday of the month unless it's 00:10:37.519 --> 00:10:39.460 align:start position:0% Tuesday of the month unless it's emergency<00:10:37.850> patch<00:10:38.120> that<00:10:38.930> way<00:10:39.019> so<00:10:39.199> submit 00:10:39.460 --> 00:10:39.470 align:start position:0% emergency patch that way so submit 00:10:39.470 --> 00:10:41.230 align:start position:0% emergency patch that way so submit administrators<00:10:40.040> know<00:10:40.310> that<00:10:40.880> they<00:10:40.970> should<00:10:41.149> not 00:10:41.230 --> 00:10:41.240 align:start position:0% administrators know that they should not 00:10:41.240 --> 00:10:43.210 align:start position:0% administrators know that they should not take<00:10:41.420> vacations<00:10:42.050> during<00:10:42.260> the<00:10:42.470> second<00:10:42.860> week<00:10:43.040> of 00:10:43.210 --> 00:10:43.220 align:start position:0% take vacations during the second week of 00:10:43.220 --> 00:10:44.980 align:start position:0% take vacations during the second week of a<00:10:43.370> month<00:10:43.579> because<00:10:44.000> that's<00:10:44.300> when<00:10:44.480> a<00:10:44.510> lot<00:10:44.779> of<00:10:44.839> the 00:10:44.980 --> 00:10:44.990 align:start position:0% a month because that's when a lot of the 00:10:44.990 --> 00:10:46.720 align:start position:0% a month because that's when a lot of the work<00:10:45.139> is<00:10:45.260> going<00:10:45.440> to<00:10:45.529> come<00:10:45.649> around<00:10:45.740> to<00:10:46.100> testing 00:10:46.720 --> 00:10:46.730 align:start position:0% work is going to come around to testing 00:10:46.730 --> 00:10:48.519 align:start position:0% work is going to come around to testing and<00:10:46.850> upgrade<00:10:47.089> in<00:10:47.209> the<00:10:47.240> clients 00:10:48.519 --> 00:10:48.529 align:start position:0% and upgrade in the clients 00:10:48.529 --> 00:10:50.319 align:start position:0% and upgrade in the clients similarly<00:10:49.100> note<00:10:49.459> operators<00:10:49.970> would<00:10:50.120> know<00:10:50.300> that 00:10:50.319 --> 00:10:50.329 align:start position:0% similarly note operators would know that 00:10:50.329 --> 00:10:52.059 align:start position:0% similarly note operators would know that the<00:10:50.600> third<00:10:50.839> week<00:10:50.990> of<00:10:51.079> a<00:10:51.170> month<00:10:51.380> is<00:10:51.829> probably 00:10:52.059 --> 00:10:52.069 align:start position:0% the third week of a month is probably 00:10:52.069 --> 00:10:53.710 align:start position:0% the third week of a month is probably not<00:10:52.430> the<00:10:52.579> best<00:10:52.610> time<00:10:52.910> to<00:10:52.940> take<00:10:53.209> vacation 00:10:53.710 --> 00:10:53.720 align:start position:0% not the best time to take vacation 00:10:53.720 --> 00:10:55.240 align:start position:0% not the best time to take vacation because<00:10:53.959> that's<00:10:54.139> when<00:10:54.380> a<00:10:54.589> network<00:10:54.889> upgrade 00:10:55.240 --> 00:10:55.250 align:start position:0% because that's when a network upgrade 00:10:55.250 --> 00:10:57.819 align:start position:0% because that's when a network upgrade could<00:10:55.490> occur<00:10:55.760> now<00:10:56.660> these<00:10:56.870> could<00:10:57.139> occur<00:10:57.410> in<00:10:57.649> any 00:10:57.819 --> 00:10:57.829 align:start position:0% could occur now these could occur in any 00:10:57.829 --> 00:10:59.590 align:start position:0% could occur now these could occur in any of<00:10:58.010> the<00:10:58.100> twelve<00:10:58.339> months<00:10:58.639> but<00:10:59.149> the<00:10:59.269> second 00:10:59.590 --> 00:10:59.600 align:start position:0% of the twelve months but the second 00:10:59.600 --> 00:11:01.150 align:start position:0% of the twelve months but the second thing<00:10:59.690> that<00:10:59.839> I<00:10:59.870> recommend<00:11:00.139> this<00:11:00.740> is<00:11:00.889> more<00:11:01.069> of<00:11:01.130> a 00:11:01.150 --> 00:11:01.160 align:start position:0% thing that I recommend this is more of a 00:11:01.160 --> 00:11:02.980 align:start position:0% thing that I recommend this is more of a recommendation<00:11:01.790> is<00:11:01.939> that<00:11:02.269> we<00:11:02.510> put<00:11:02.720> four 00:11:02.980 --> 00:11:02.990 align:start position:0% recommendation is that we put four 00:11:02.990 --> 00:11:04.449 align:start position:0% recommendation is that we put four specific<00:11:03.230> months<00:11:03.649> that<00:11:03.769> we<00:11:03.860> prefer<00:11:04.040> to<00:11:04.220> launch 00:11:04.449 --> 00:11:04.459 align:start position:0% specific months that we prefer to launch 00:11:04.459 --> 00:11:05.079 align:start position:0% specific months that we prefer to launch main<00:11:04.699> nets 00:11:05.079 --> 00:11:05.089 align:start position:0% main nets 00:11:05.089 --> 00:11:07.079 align:start position:0% main nets main<00:11:05.839> an<00:11:05.990> upgrades<00:11:06.350> those<00:11:06.769> will<00:11:06.920> be 00:11:07.079 --> 00:11:07.089 align:start position:0% main an upgrades those will be 00:11:07.089 --> 00:11:09.749 align:start position:0% main an upgrades those will be January<00:11:07.480> April<00:11:07.720> July<00:11:07.990> in<00:11:08.350> October<00:11:08.800> those<00:11:09.579> are 00:11:09.749 --> 00:11:09.759 align:start position:0% January April July in October those are 00:11:09.759 --> 00:11:11.489 align:start position:0% January April July in October those are three<00:11:09.879> months<00:11:09.999> apart<00:11:10.360> and<00:11:11.199> those<00:11:11.319> who<00:11:11.410> have 00:11:11.489 --> 00:11:11.499 align:start position:0% three months apart and those who have 00:11:11.499 --> 00:11:13.650 align:start position:0% three months apart and those who have the<00:11:11.589> advantage<00:11:11.980> of<00:11:12.100> missing<00:11:12.399> a<00:11:12.490> lot<00:11:12.670> of<00:11:12.850> US<00:11:13.509> and 00:11:13.650 --> 00:11:13.660 align:start position:0% the advantage of missing a lot of US and 00:11:13.660 --> 00:11:15.030 align:start position:0% the advantage of missing a lot of US and European<00:11:13.990> centric<00:11:14.439> conflicts<00:11:14.920> around 00:11:15.030 --> 00:11:15.040 align:start position:0% European centric conflicts around 00:11:15.040 --> 00:11:18.420 align:start position:0% European centric conflicts around vacations<00:11:15.670> and<00:11:15.939> holidays<00:11:16.499> so<00:11:17.499> that<00:11:17.769> the 00:11:18.420 --> 00:11:18.430 align:start position:0% vacations and holidays so that the 00:11:18.430 --> 00:11:20.579 align:start position:0% vacations and holidays so that the operators<00:11:19.029> in<00:11:19.059> those<00:11:19.329> areas 00:11:20.579 --> 00:11:20.589 align:start position:0% operators in those areas 00:11:20.589 --> 00:11:23.989 align:start position:0% operators in those areas won't<00:11:20.920> feel<00:11:21.279> any<00:11:21.490> conflicts<00:11:21.939> with<00:11:21.970> those 00:11:23.989 --> 00:11:23.999 align:start position:0% won't feel any conflicts with those 00:11:23.999 --> 00:11:26.489 align:start position:0% won't feel any conflicts with those however<00:11:24.999> sometimes<00:11:25.749> it<00:11:26.079> comes<00:11:26.230> it's 00:11:26.489 --> 00:11:26.499 align:start position:0% however sometimes it comes it's 00:11:26.499 --> 00:11:28.379 align:start position:0% however sometimes it comes it's necessary<00:11:27.009> to<00:11:27.189> delay<00:11:27.430> a<00:11:27.459> network<00:11:27.879> upgrade<00:11:28.240> has 00:11:28.379 --> 00:11:28.389 align:start position:0% necessary to delay a network upgrade has 00:11:28.389 --> 00:11:30.389 align:start position:0% necessary to delay a network upgrade has happened<00:11:28.660> with<00:11:28.749> Constantinople<00:11:29.110> in<00:11:29.800> those 00:11:30.389 --> 00:11:30.399 align:start position:0% happened with Constantinople in those 00:11:30.399 --> 00:11:32.879 align:start position:0% happened with Constantinople in those cases<00:11:30.670> the<00:11:31.059> delays<00:11:31.329> would<00:11:31.509> go<00:11:31.629> out<00:11:31.779> in<00:11:32.050> month 00:11:32.879 --> 00:11:32.889 align:start position:0% cases the delays would go out in month 00:11:32.889 --> 00:11:34.739 align:start position:0% cases the delays would go out in month increments<00:11:33.430> if<00:11:33.550> we<00:11:33.639> have<00:11:33.759> to<00:11:33.879> delay<00:11:34.149> it<00:11:34.300> we 00:11:34.739 --> 00:11:34.749 align:start position:0% increments if we have to delay it we 00:11:34.749 --> 00:11:36.540 align:start position:0% increments if we have to delay it we pick<00:11:34.930> a<00:11:34.990> new<00:11:35.230> third<00:11:35.740> month<00:11:36.009> the<00:11:36.370> third 00:11:36.540 --> 00:11:36.550 align:start position:0% pick a new third month the third 00:11:36.550 --> 00:11:37.889 align:start position:0% pick a new third month the third Wednesday<00:11:36.879> of<00:11:36.910> the<00:11:37.089> month<00:11:37.120> probably<00:11:37.689> the<00:11:37.809> next 00:11:37.889 --> 00:11:37.899 align:start position:0% Wednesday of the month probably the next 00:11:37.899 --> 00:11:40.889 align:start position:0% Wednesday of the month probably the next month<00:11:38.199> to<00:11:38.740> shift<00:11:38.949> it<00:11:39.100> out<00:11:39.189> a<00:11:39.220> month<00:11:39.519> and<00:11:40.209> the 00:11:40.889 --> 00:11:40.899 align:start position:0% month to shift it out a month and the 00:11:40.899 --> 00:11:42.389 align:start position:0% month to shift it out a month and the aim<00:11:41.019> here<00:11:41.290> for<00:11:41.470> this<00:11:41.529> is<00:11:41.740> to<00:11:41.860> do<00:11:41.949> these<00:11:42.069> network 00:11:42.389 --> 00:11:42.399 align:start position:0% aim here for this is to do these network 00:11:42.399 --> 00:11:45.119 align:start position:0% aim here for this is to do these network upgrades<00:11:42.790> twice<00:11:43.269> a<00:11:43.449> year<00:11:43.720> we<00:11:44.410> would<00:11:44.559> do<00:11:44.740> one<00:11:44.980> in 00:11:45.119 --> 00:11:45.129 align:start position:0% upgrades twice a year we would do one in 00:11:45.129 --> 00:11:47.100 align:start position:0% upgrades twice a year we would do one in January<00:11:45.579> and<00:11:45.730> one<00:11:45.910> and<00:11:46.089> not<00:11:46.149> July<00:11:46.449> or<00:11:46.870> one<00:11:47.019> in 00:11:47.100 --> 00:11:47.110 align:start position:0% January and one and not July or one in 00:11:47.110 --> 00:11:49.019 align:start position:0% January and one and not July or one in April<00:11:47.470> and<00:11:47.559> one<00:11:47.680> or<00:11:47.800> October<00:11:48.249> so<00:11:48.790> once<00:11:48.939> you 00:11:49.019 --> 00:11:49.029 align:start position:0% April and one or October so once you 00:11:49.029 --> 00:11:50.699 align:start position:0% April and one or October so once you schedule<00:11:49.389> one<00:11:49.569> you<00:11:49.749> would<00:11:49.870> do<00:11:49.990> one<00:11:50.170> six<00:11:50.439> months 00:11:50.699 --> 00:11:50.709 align:start position:0% schedule one you would do one six months 00:11:50.709 --> 00:11:53.249 align:start position:0% schedule one you would do one six months later<00:11:50.920> I<00:11:51.660> mean<00:11:52.660> of<00:11:52.749> course<00:11:52.809> in<00:11:53.139> this 00:11:53.249 --> 00:11:53.259 align:start position:0% later I mean of course in this 00:11:53.259 --> 00:11:53.939 align:start position:0% later I mean of course in this recommendation 00:11:53.939 --> 00:11:53.949 align:start position:0% recommendation 00:11:53.949 --> 00:11:56.280 align:start position:0% recommendation you<00:11:54.550> could<00:11:54.730> always<00:11:54.910> fight<00:11:55.300> fires<00:11:55.629> whenever 00:11:56.280 --> 00:11:56.290 align:start position:0% you could always fight fires whenever 00:11:56.290 --> 00:11:57.900 align:start position:0% you could always fight fires whenever and<00:11:56.589> wherever<00:11:56.889> they<00:11:57.100> happen<00:11:57.550> if<00:11:57.670> we<00:11:57.759> have 00:11:57.900 --> 00:11:57.910 align:start position:0% and wherever they happen if we have 00:11:57.910 --> 00:11:59.819 align:start position:0% and wherever they happen if we have another<00:11:58.120> situation<00:11:58.660> like<00:11:58.779> Constantinople<00:11:59.680> or 00:11:59.819 --> 00:11:59.829 align:start position:0% another situation like Constantinople or 00:11:59.829 --> 00:12:02.429 align:start position:0% another situation like Constantinople or the<00:12:00.399> Shanghai<00:12:00.790> attacks<00:12:01.149> we<00:12:01.389> can<00:12:01.600> upgrade<00:12:02.110> it 00:12:02.429 --> 00:12:02.439 align:start position:0% the Shanghai attacks we can upgrade it 00:12:02.439 --> 00:12:04.139 align:start position:0% the Shanghai attacks we can upgrade it on<00:12:02.709> very<00:12:02.949> short<00:12:03.220> notice<00:12:03.249> or<00:12:03.730> we<00:12:03.879> couldn't 00:12:04.139 --> 00:12:04.149 align:start position:0% on very short notice or we couldn't 00:12:04.149 --> 00:12:05.639 align:start position:0% on very short notice or we couldn't cancel<00:12:04.569> a<00:12:04.660> fork<00:12:04.899> and<00:12:05.019> move<00:12:05.139> it<00:12:05.259> out<00:12:05.350> on<00:12:05.470> very 00:12:05.639 --> 00:12:05.649 align:start position:0% cancel a fork and move it out on very 00:12:05.649 --> 00:12:07.199 align:start position:0% cancel a fork and move it out on very short<00:12:05.889> notice<00:12:05.949> if<00:12:06.610> there's<00:12:06.850> an<00:12:06.999> emergency 00:12:07.199 --> 00:12:07.209 align:start position:0% short notice if there's an emergency 00:12:07.209 --> 00:12:09.480 align:start position:0% short notice if there's an emergency those<00:12:08.110> recommendations<00:12:08.470> do<00:12:08.889> not<00:12:09.040> constrain 00:12:09.480 --> 00:12:09.490 align:start position:0% those recommendations do not constrain 00:12:09.490 --> 00:12:11.519 align:start position:0% those recommendations do not constrain us<00:12:09.519> on<00:12:09.759> acting<00:12:10.120> on<00:12:10.209> those<00:12:10.329> emergencies<00:12:10.839> but<00:12:11.439> if 00:12:11.519 --> 00:12:11.529 align:start position:0% us on acting on those emergencies but if 00:12:11.529 --> 00:12:13.559 align:start position:0% us on acting on those emergencies but if it's<00:12:11.649> not<00:12:11.829> an<00:12:12.009> emergency<00:12:12.129> the<00:12:13.089> discipline 00:12:13.559 --> 00:12:13.569 align:start position:0% it's not an emergency the discipline 00:12:13.569 --> 00:12:14.669 align:start position:0% it's not an emergency the discipline that<00:12:13.660> comes<00:12:13.809> with<00:12:14.019> the<00:12:14.079> time<00:12:14.290> frame<00:12:14.470> like<00:12:14.620> this 00:12:14.669 --> 00:12:14.679 align:start position:0% that comes with the time frame like this 00:12:14.679 --> 00:12:16.949 align:start position:0% that comes with the time frame like this will<00:12:15.339> be<00:12:15.429> appreciated<00:12:15.730> by<00:12:16.540> the<00:12:16.600> people<00:12:16.779> who 00:12:16.949 --> 00:12:16.959 align:start position:0% will be appreciated by the people who 00:12:16.959 --> 00:12:19.379 align:start position:0% will be appreciated by the people who have<00:12:17.079> to<00:12:17.170> operate<00:12:17.529> the<00:12:18.129> etherium<00:12:18.579> nodes<00:12:18.790> that 00:12:19.379 --> 00:12:19.389 align:start position:0% have to operate the etherium nodes that 00:12:19.389 --> 00:12:22.259 align:start position:0% have to operate the etherium nodes that all<00:12:19.720> of<00:12:19.929> our<00:12:19.990> networks<00:12:20.350> depend<00:12:20.679> on<00:12:21.120> so<00:12:22.120> it's 00:12:22.259 --> 00:12:22.269 align:start position:0% all of our networks depend on so it's 00:12:22.269 --> 00:12:23.819 align:start position:0% all of our networks depend on so it's synthesis<00:12:22.660> from<00:12:22.839> all<00:12:22.929> of<00:12:23.079> these<00:12:23.199> four 00:12:23.819 --> 00:12:23.829 align:start position:0% synthesis from all of these four 00:12:23.829 --> 00:12:26.009 align:start position:0% synthesis from all of these four recommendations<00:12:24.639> we<00:12:25.329> get<00:12:25.540> to<00:12:25.689> the<00:12:25.809> Train 00:12:26.009 --> 00:12:26.019 align:start position:0% recommendations we get to the Train 00:12:26.019 --> 00:12:27.960 align:start position:0% recommendations we get to the Train model<00:12:26.379> so<00:12:26.559> rather<00:12:26.709> than<00:12:26.949> a<00:12:27.009> model<00:12:27.370> where<00:12:27.819> we're 00:12:27.960 --> 00:12:27.970 align:start position:0% model so rather than a model where we're 00:12:27.970 --> 00:12:30.329 align:start position:0% model so rather than a model where we're all<00:12:27.999> flying<00:12:28.420> on<00:12:28.689> an<00:12:28.779> airplane<00:12:29.110> and<00:12:29.439> we're<00:12:30.069> land 00:12:30.329 --> 00:12:30.339 align:start position:0% all flying on an airplane and we're land 00:12:30.339 --> 00:12:32.160 align:start position:0% all flying on an airplane and we're land we're<00:12:30.759> going<00:12:31.269> for<00:12:31.420> a<00:12:31.480> specific<00:12:31.660> flight<00:12:32.050> at<00:12:32.139> a 00:12:32.160 --> 00:12:32.170 align:start position:0% we're going for a specific flight at a 00:12:32.170 --> 00:12:33.989 align:start position:0% we're going for a specific flight at a specific<00:12:32.379> time<00:12:32.800> instead<00:12:33.579> it's<00:12:33.730> like<00:12:33.790> we're 00:12:33.989 --> 00:12:33.999 align:start position:0% specific time instead it's like we're 00:12:33.999 --> 00:12:35.400 align:start position:0% specific time instead it's like we're going<00:12:34.120> to<00:12:34.240> a<00:12:34.329> train<00:12:34.629> station<00:12:35.079> and<00:12:35.199> as<00:12:35.319> the 00:12:35.400 --> 00:12:35.410 align:start position:0% going to a train station and as the 00:12:35.410 --> 00:12:39.389 align:start position:0% going to a train station and as the trains<00:12:35.679> come<00:12:35.920> and<00:12:36.040> go<00:12:36.209> you<00:12:37.209> come<00:12:37.749> and<00:12:37.839> go<00:12:38.399> yeah 00:12:39.389 --> 00:12:39.399 align:start position:0% trains come and go you come and go yeah 00:12:39.399 --> 00:12:41.369 align:start position:0% trains come and go you come and go yeah and<00:12:39.670> there's<00:12:39.970> four<00:12:40.120> main<00:12:40.269> ideas<00:12:40.629> here<00:12:40.899> so<00:12:41.259> the 00:12:41.369 --> 00:12:41.379 align:start position:0% and there's four main ideas here so the 00:12:41.379 --> 00:12:42.840 align:start position:0% and there's four main ideas here so the first<00:12:41.649> is<00:12:41.889> that<00:12:42.069> the<00:12:42.249> each<00:12:42.399> should<00:12:42.639> progress 00:12:42.840 --> 00:12:42.850 align:start position:0% first is that the each should progress 00:12:42.850 --> 00:12:45.269 align:start position:0% first is that the each should progress independently<00:12:43.809> like<00:12:44.319> we<00:12:44.470> said<00:12:44.620> before<00:12:44.649> you 00:12:45.269 --> 00:12:45.279 align:start position:0% independently like we said before you 00:12:45.279 --> 00:12:46.799 align:start position:0% independently like we said before you don't<00:12:45.459> want<00:12:45.579> to<00:12:45.670> have<00:12:45.819> all<00:12:46.059> the<00:12:46.179> eeap's<00:12:46.360> moving 00:12:46.799 --> 00:12:46.809 align:start position:0% don't want to have all the eeap's moving 00:12:46.809 --> 00:12:48.780 align:start position:0% don't want to have all the eeap's moving in<00:12:46.899> lockstep<00:12:47.230> towards<00:12:47.769> towards<00:12:48.220> the<00:12:48.399> various 00:12:48.780 --> 00:12:48.790 align:start position:0% in lockstep towards towards the various 00:12:48.790 --> 00:12:51.809 align:start position:0% in lockstep towards towards the various stages<00:12:49.449> of<00:12:49.600> the<00:12:49.779> process<00:12:49.959> instead<00:12:50.410> every<00:12:51.399> epin 00:12:51.809 --> 00:12:51.819 align:start position:0% stages of the process instead every epin 00:12:51.819 --> 00:12:53.249 align:start position:0% stages of the process instead every epin working<00:12:52.120> group<00:12:52.300> moved<00:12:52.600> at<00:12:52.749> their<00:12:52.870> own<00:12:53.019> pace 00:12:53.249 --> 00:12:53.259 align:start position:0% working group moved at their own pace 00:12:53.259 --> 00:12:55.379 align:start position:0% working group moved at their own pace and<00:12:53.559> whenever<00:12:54.009> it's<00:12:54.519> something<00:12:54.850> is<00:12:54.999> ready<00:12:55.209> to 00:12:55.379 --> 00:12:55.389 align:start position:0% and whenever it's something is ready to 00:12:55.389 --> 00:12:57.629 align:start position:0% and whenever it's something is ready to ship<00:12:55.629> only<00:12:55.929> then<00:12:56.559> do<00:12:56.769> you<00:12:56.800> schedule<00:12:57.100> it<00:12:57.399> for<00:12:57.429> an 00:12:57.629 --> 00:12:57.639 align:start position:0% ship only then do you schedule it for an 00:12:57.639 --> 00:13:00.030 align:start position:0% ship only then do you schedule it for an actual<00:12:57.819> upgrade<00:12:58.410> the<00:12:59.410> second<00:12:59.740> point<00:12:59.860> is<00:13:00.009> that 00:13:00.030 --> 00:13:00.040 align:start position:0% actual upgrade the second point is that 00:13:00.040 --> 00:13:02.730 align:start position:0% actual upgrade the second point is that EAPs<00:13:00.610> have<00:13:00.879> a<00:13:00.910> champion<00:13:01.449> a<00:13:01.540> human<00:13:01.839> being<00:13:02.050> who 00:13:02.730 --> 00:13:02.740 align:start position:0% EAPs have a champion a human being who 00:13:02.740 --> 00:13:04.559 align:start position:0% EAPs have a champion a human being who the<00:13:02.860> all<00:13:02.980> core<00:13:03.160> devs<00:13:03.370> can<00:13:03.610> contact<00:13:03.970> to<00:13:04.120> say<00:13:04.360> hey 00:13:04.559 --> 00:13:04.569 align:start position:0% the all core devs can contact to say hey 00:13:04.569 --> 00:13:05.939 align:start position:0% the all core devs can contact to say hey is<00:13:04.779> this<00:13:04.899> EIP<00:13:05.230> ready<00:13:05.529> for<00:13:05.679> this<00:13:05.769> network 00:13:05.939 --> 00:13:05.949 align:start position:0% is this EIP ready for this network 00:13:05.949 --> 00:13:07.619 align:start position:0% is this EIP ready for this network upgrade<00:13:06.429> should<00:13:06.639> we<00:13:07.029> move<00:13:07.179> it<00:13:07.269> to<00:13:07.300> the<00:13:07.420> next 00:13:07.619 --> 00:13:07.629 align:start position:0% upgrade should we move it to the next 00:13:07.629 --> 00:13:09.569 align:start position:0% upgrade should we move it to the next one<00:13:07.809> it's<00:13:07.959> a<00:13:08.019> single<00:13:08.319> point<00:13:08.470> of<00:13:08.529> contact<00:13:08.589> who 00:13:09.569 --> 00:13:09.579 align:start position:0% one it's a single point of contact who 00:13:09.579 --> 00:13:11.489 align:start position:0% one it's a single point of contact who can<00:13:09.699> answer<00:13:09.850> these<00:13:10.120> questions<00:13:10.540> and<00:13:10.720> help<00:13:11.230> move 00:13:11.489 --> 00:13:11.499 align:start position:0% can answer these questions and help move 00:13:11.499 --> 00:13:13.489 align:start position:0% can answer these questions and help move the<00:13:11.709> EIP<00:13:11.949> through<00:13:12.309> the<00:13:12.370> process<00:13:12.819> maybe 00:13:13.489 --> 00:13:13.499 align:start position:0% the EIP through the process maybe 00:13:13.499 --> 00:13:15.869 align:start position:0% the EIP through the process maybe motivate<00:13:14.499> the<00:13:14.620> team<00:13:14.860> to<00:13:15.100> make<00:13:15.220> deadlines<00:13:15.670> and 00:13:15.869 --> 00:13:15.879 align:start position:0% motivate the team to make deadlines and 00:13:15.879 --> 00:13:17.369 align:start position:0% motivate the team to make deadlines and maybe<00:13:16.000> just<00:13:16.240> let<00:13:16.389> all<00:13:16.569> core<00:13:16.779> devs<00:13:16.959> know<00:13:17.110> that 00:13:17.369 --> 00:13:17.379 align:start position:0% maybe just let all core devs know that 00:13:17.379 --> 00:13:19.049 align:start position:0% maybe just let all core devs know that we<00:13:17.829> found<00:13:17.860> an<00:13:18.129> issue<00:13:18.279> and<00:13:18.639> we're<00:13:18.790> not<00:13:18.910> going<00:13:19.029> to 00:13:19.049 --> 00:13:19.059 align:start position:0% we found an issue and we're not going to 00:13:19.059 --> 00:13:20.120 align:start position:0% we found an issue and we're not going to make<00:13:19.179> this<00:13:19.329> network<00:13:19.540> up 00:13:20.120 --> 00:13:20.130 align:start position:0% make this network up 00:13:20.130 --> 00:13:22.939 align:start position:0% make this network up and<00:13:20.480> the<00:13:21.480> third<00:13:21.690> idea<00:13:21.839> is<00:13:22.230> that<00:13:22.440> whatever<00:13:22.800> is 00:13:22.939 --> 00:13:22.949 align:start position:0% and the third idea is that whatever is 00:13:22.949 --> 00:13:25.370 align:start position:0% and the third idea is that whatever is done<00:13:23.160> is<00:13:23.430> whatever<00:13:23.610> shift<00:13:24.120> is<00:13:24.930> whatever 00:13:25.370 --> 00:13:25.380 align:start position:0% done is whatever shift is whatever 00:13:25.380 --> 00:13:27.980 align:start position:0% done is whatever shift is whatever shifts<00:13:25.860> sorry<00:13:26.130> so<00:13:27.060> this<00:13:27.269> way<00:13:27.389> an<00:13:27.660> upgrade 00:13:27.980 --> 00:13:27.990 align:start position:0% shifts sorry so this way an upgrade 00:13:27.990 --> 00:13:29.749 align:start position:0% shifts sorry so this way an upgrade consists<00:13:28.470> of<00:13:28.589> basically<00:13:28.800> the<00:13:29.160> eats<00:13:29.370> that<00:13:29.670> are 00:13:29.749 --> 00:13:29.759 align:start position:0% consists of basically the eats that are 00:13:29.759 --> 00:13:31.280 align:start position:0% consists of basically the eats that are in<00:13:29.910> a<00:13:30.000> spot<00:13:30.300> where<00:13:30.329> they're<00:13:30.660> ready<00:13:30.810> to<00:13:30.899> go<00:13:31.079> live 00:13:31.280 --> 00:13:31.290 align:start position:0% in a spot where they're ready to go live 00:13:31.290 --> 00:13:33.350 align:start position:0% in a spot where they're ready to go live anything<00:13:32.279> that's<00:13:32.430> still<00:13:32.639> in<00:13:32.759> progress<00:13:32.940> gets 00:13:33.350 --> 00:13:33.360 align:start position:0% anything that's still in progress gets 00:13:33.360 --> 00:13:35.329 align:start position:0% anything that's still in progress gets moved<00:13:33.600> to<00:13:33.660> the<00:13:33.750> next<00:13:34.050> upgrade<00:13:34.230> like<00:13:34.949> we<00:13:35.100> said 00:13:35.329 --> 00:13:35.339 align:start position:0% moved to the next upgrade like we said 00:13:35.339 --> 00:13:37.430 align:start position:0% moved to the next upgrade like we said if<00:13:35.579> there's<00:13:35.880> any<00:13:36.000> last-minute<00:13:36.480> issue<00:13:36.810> then 00:13:37.430 --> 00:13:37.440 align:start position:0% if there's any last-minute issue then 00:13:37.440 --> 00:13:39.650 align:start position:0% if there's any last-minute issue then you<00:13:37.470> can<00:13:37.829> obviously<00:13:38.160> kick<00:13:38.490> that<00:13:38.639> eat<00:13:38.759> out<00:13:38.910> kick 00:13:39.650 --> 00:13:39.660 align:start position:0% you can obviously kick that eat out kick 00:13:39.660 --> 00:13:41.449 align:start position:0% you can obviously kick that eat out kick that<00:13:39.690> EEP<00:13:40.139> out<00:13:40.319> to<00:13:40.680> the<00:13:40.709> next<00:13:40.949> train<00:13:41.190> as<00:13:41.310> well 00:13:41.449 --> 00:13:41.459 align:start position:0% that EEP out to the next train as well 00:13:41.459 --> 00:13:43.730 align:start position:0% that EEP out to the next train as well and<00:13:42.420> the<00:13:42.600> final<00:13:42.899> recommendation<00:13:43.470> is<00:13:43.560> that<00:13:43.589> we 00:13:43.730 --> 00:13:43.740 align:start position:0% and the final recommendation is that we 00:13:43.740 --> 00:13:45.350 align:start position:0% and the final recommendation is that we move<00:13:43.889> to<00:13:44.009> semi-annual<00:13:44.699> network<00:13:45.000> upgrades 00:13:45.350 --> 00:13:45.360 align:start position:0% move to semi-annual network upgrades 00:13:45.360 --> 00:13:47.329 align:start position:0% move to semi-annual network upgrades rather<00:13:45.930> than<00:13:46.199> the<00:13:46.259> annual<00:13:46.649> or<00:13:46.800> less<00:13:46.980> upgrades 00:13:47.329 --> 00:13:47.339 align:start position:0% rather than the annual or less upgrades 00:13:47.339 --> 00:13:49.129 align:start position:0% rather than the annual or less upgrades that<00:13:47.430> we've<00:13:47.550> doing<00:13:47.730> in<00:13:47.910> the<00:13:47.970> past<00:13:48.180> one<00:13:48.990> of<00:13:49.019> the 00:13:49.129 --> 00:13:49.139 align:start position:0% that we've doing in the past one of the 00:13:49.139 --> 00:13:50.569 align:start position:0% that we've doing in the past one of the big<00:13:49.470> advantages<00:13:49.589> that<00:13:49.980> we<00:13:50.069> get<00:13:50.220> out<00:13:50.339> of<00:13:50.370> this 00:13:50.569 --> 00:13:50.579 align:start position:0% big advantages that we get out of this 00:13:50.579 --> 00:13:52.460 align:start position:0% big advantages that we get out of this is<00:13:51.060> that<00:13:51.209> when<00:13:51.300> we<00:13:51.360> tell<00:13:51.569> an<00:13:51.690> EIP<00:13:51.959> that<00:13:52.319> you're 00:13:52.460 --> 00:13:52.470 align:start position:0% is that when we tell an EIP that you're 00:13:52.470 --> 00:13:54.319 align:start position:0% is that when we tell an EIP that you're not<00:13:52.620> ready<00:13:52.860> for<00:13:53.009> this<00:13:53.100> network<00:13:53.459> upgrade<00:13:53.850> the 00:13:54.319 --> 00:13:54.329 align:start position:0% not ready for this network upgrade the 00:13:54.329 --> 00:13:55.970 align:start position:0% not ready for this network upgrade the next<00:13:54.600> upgrade<00:13:54.899> is<00:13:55.050> only<00:13:55.199> six<00:13:55.500> months<00:13:55.740> down<00:13:55.860> the 00:13:55.970 --> 00:13:55.980 align:start position:0% next upgrade is only six months down the 00:13:55.980 --> 00:13:58.220 align:start position:0% next upgrade is only six months down the road<00:13:56.069> rather<00:13:56.819> than<00:13:57.089> a<00:13:57.180> year<00:13:57.420> or<00:13:57.600> more<00:13:57.839> down<00:13:58.079> the 00:13:58.220 --> 00:13:58.230 align:start position:0% road rather than a year or more down the 00:13:58.230 --> 00:14:00.530 align:start position:0% road rather than a year or more down the road<00:13:58.410> so<00:13:59.009> they<00:13:59.130> know<00:13:59.310> that<00:13:59.519> they're<00:13:59.730> there<00:14:00.329> the 00:14:00.530 --> 00:14:00.540 align:start position:0% road so they know that they're there the 00:14:00.540 --> 00:14:02.059 align:start position:0% road so they know that they're there the work<00:14:00.720> that<00:14:00.870> they<00:14:00.959> put<00:14:00.990> into<00:14:01.259> will<00:14:01.649> still<00:14:01.860> show 00:14:02.059 --> 00:14:02.069 align:start position:0% work that they put into will still show 00:14:02.069 --> 00:14:04.129 align:start position:0% work that they put into will still show up<00:14:02.250> in<00:14:02.399> a<00:14:02.459> reasonable<00:14:02.850> timeframe<00:14:03.060> rather<00:14:03.930> than 00:14:04.129 --> 00:14:04.139 align:start position:0% up in a reasonable timeframe rather than 00:14:04.139 --> 00:14:05.689 align:start position:0% up in a reasonable timeframe rather than some<00:14:04.380> unknown<00:14:04.769> timeframe<00:14:05.220> in<00:14:05.339> the<00:14:05.430> future 00:14:05.689 --> 00:14:05.699 align:start position:0% some unknown timeframe in the future 00:14:05.699 --> 00:14:07.579 align:start position:0% some unknown timeframe in the future you'll<00:14:06.269> reduce<00:14:06.540> a<00:14:06.660> lot<00:14:06.810> of<00:14:06.870> the<00:14:06.959> anxiety<00:14:07.470> when 00:14:07.579 --> 00:14:07.589 align:start position:0% you'll reduce a lot of the anxiety when 00:14:07.589 --> 00:14:09.379 align:start position:0% you'll reduce a lot of the anxiety when it<00:14:07.680> comes<00:14:07.860> to<00:14:07.949> scheduling<00:14:08.220> and<00:14:08.670> moving<00:14:09.209> stuff 00:14:09.379 --> 00:14:09.389 align:start position:0% it comes to scheduling and moving stuff 00:14:09.389 --> 00:14:11.389 align:start position:0% it comes to scheduling and moving stuff in<00:14:09.630> and<00:14:09.810> out<00:14:09.870> of<00:14:09.990> a<00:14:10.050> network<00:14:10.319> upgrade<00:14:10.680> and<00:14:11.190> from 00:14:11.389 --> 00:14:11.399 align:start position:0% in and out of a network upgrade and from 00:14:11.399 --> 00:14:12.470 align:start position:0% in and out of a network upgrade and from this<00:14:11.550> we<00:14:11.699> can<00:14:11.850> make<00:14:11.940> sure<00:14:12.000> that<00:14:12.180> what<00:14:12.329> goes 00:14:12.470 --> 00:14:12.480 align:start position:0% this we can make sure that what goes 00:14:12.480 --> 00:14:14.449 align:start position:0% this we can make sure that what goes into<00:14:12.720> the<00:14:12.930> network<00:14:13.079> upgrade<00:14:13.560> is<00:14:13.740> the<00:14:14.130> good 00:14:14.449 --> 00:14:14.459 align:start position:0% into the network upgrade is the good 00:14:14.459 --> 00:14:18.949 align:start position:0% into the network upgrade is the good stuff<00:14:16.040> and<00:14:17.040> like<00:14:17.610> we<00:14:17.730> said<00:14:17.880> earlier<00:14:17.940> we<00:14:18.750> didn't 00:14:18.949 --> 00:14:18.959 align:start position:0% stuff and like we said earlier we didn't 00:14:18.959 --> 00:14:20.449 align:start position:0% stuff and like we said earlier we didn't come<00:14:19.079> up<00:14:19.170> with<00:14:19.319> all<00:14:19.440> of<00:14:19.470> these<00:14:19.680> ideas<00:14:20.040> the 00:14:20.449 --> 00:14:20.459 align:start position:0% come up with all of these ideas the 00:14:20.459 --> 00:14:22.220 align:start position:0% come up with all of these ideas the community<00:14:21.029> mostly<00:14:21.360> did<00:14:21.509> so<00:14:21.870> we<00:14:21.959> wanted<00:14:22.139> to 00:14:22.220 --> 00:14:22.230 align:start position:0% community mostly did so we wanted to 00:14:22.230 --> 00:14:24.350 align:start position:0% community mostly did so we wanted to make<00:14:22.410> sure<00:14:22.440> we<00:14:22.740> linked<00:14:22.980> back<00:14:23.160> to<00:14:23.190> them<00:14:23.459> so 00:14:24.350 --> 00:14:24.360 align:start position:0% make sure we linked back to them so 00:14:24.360 --> 00:14:25.970 align:start position:0% make sure we linked back to them so anyone<00:14:24.660> who's<00:14:24.839> interested<00:14:25.260> can<00:14:25.290> go<00:14:25.589> and<00:14:25.769> dig 00:14:25.970 --> 00:14:25.980 align:start position:0% anyone who's interested can go and dig 00:14:25.980 --> 00:14:27.710 align:start position:0% anyone who's interested can go and dig it<00:14:26.130> a<00:14:26.279> bit<00:14:26.490> deeper<00:14:26.760> to<00:14:26.790> the<00:14:27.029> original<00:14:27.449> sources 00:14:27.710 --> 00:14:27.720 align:start position:0% it a bit deeper to the original sources 00:14:27.720 --> 00:14:30.110 align:start position:0% it a bit deeper to the original sources yeah<00:14:28.440> if<00:14:28.649> you<00:14:28.740> google<00:14:29.100> alexia<00:14:29.550> to<00:14:29.699> knob<00:14:29.880> that's 00:14:30.110 --> 00:14:30.120 align:start position:0% yeah if you google alexia to knob that's 00:14:30.120 --> 00:14:33.439 align:start position:0% yeah if you google alexia to knob that's the<00:14:30.269> article<00:14:30.660> that<00:14:30.750> you'll<00:14:30.899> find<00:14:32.060> and<00:14:33.060> so<00:14:33.300> yeah 00:14:33.439 --> 00:14:33.449 align:start position:0% the article that you'll find and so yeah 00:14:33.449 --> 00:14:35.569 align:start position:0% the article that you'll find and so yeah that's<00:14:33.930> what<00:14:34.050> we<00:14:34.139> had<00:14:34.290> thank<00:14:35.190> you<00:14:35.279> all<00:14:35.399> for 00:14:35.569 --> 00:14:35.579 align:start position:0% that's what we had thank you all for 00:14:35.579 --> 00:14:36.860 align:start position:0% that's what we had thank you all for listening<00:14:35.639> and<00:14:36.180> we<00:14:36.329> have<00:14:36.449> a<00:14:36.480> couple<00:14:36.690> minutes 00:14:36.860 --> 00:14:36.870 align:start position:0% listening and we have a couple minutes 00:14:36.870 --> 00:14:45.079 align:start position:0% listening and we have a couple minutes for<00:14:37.050> questions<00:14:37.440> if<00:14:37.680> anyone<00:14:38.010> has<00:14:38.130> any<00:14:44.089> hey 00:14:45.079 --> 00:14:45.089 align:start position:0% for questions if anyone has any hey 00:14:45.089 --> 00:14:47.120 align:start position:0% for questions if anyone has any hey thanks<00:14:45.360> for<00:14:45.420> the<00:14:45.540> thanks<00:14:45.930> for<00:14:46.050> the<00:14:46.170> talk<00:14:46.350> I<00:14:46.829> was 00:14:47.120 --> 00:14:47.130 align:start position:0% thanks for the thanks for the talk I was 00:14:47.130 --> 00:14:49.250 align:start position:0% thanks for the thanks for the talk I was just<00:14:47.250> curious<00:14:47.399> what's<00:14:47.910> required<00:14:48.240> to<00:14:49.170> get 00:14:49.250 --> 00:14:49.260 align:start position:0% just curious what's required to get 00:14:49.260 --> 00:14:51.110 align:start position:0% just curious what's required to get miners<00:14:49.709> on<00:14:49.889> board<00:14:50.100> at<00:14:50.220> this<00:14:50.339> like<00:14:50.730> plan<00:14:51.000> of 00:14:51.110 --> 00:14:51.120 align:start position:0% miners on board at this like plan of 00:14:51.120 --> 00:14:53.840 align:start position:0% miners on board at this like plan of doing<00:14:51.649> regular<00:14:52.649> hard<00:14:52.860> Forks<00:14:53.160> for<00:14:53.490> upgrades 00:14:53.840 --> 00:14:53.850 align:start position:0% doing regular hard Forks for upgrades 00:14:53.850 --> 00:14:55.550 align:start position:0% doing regular hard Forks for upgrades and<00:14:54.149> are<00:14:54.600> there<00:14:54.750> any<00:14:54.779> like<00:14:54.990> difficulty 00:14:55.550 --> 00:14:55.560 align:start position:0% and are there any like difficulty 00:14:55.560 --> 00:14:56.780 align:start position:0% and are there any like difficulty adjustments<00:14:56.040> that<00:14:56.160> are<00:14:56.250> happening<00:14:56.399> with<00:14:56.670> each 00:14:56.780 --> 00:14:56.790 align:start position:0% adjustments that are happening with each 00:14:56.790 --> 00:15:00.889 align:start position:0% adjustments that are happening with each of<00:14:56.940> those<00:14:57.500> hard<00:14:58.500> Forks<00:14:58.740> yeah<00:14:59.699> on<00:14:59.970> board<00:15:00.180> miners 00:15:00.889 --> 00:15:00.899 align:start position:0% of those hard Forks yeah on board miners 00:15:00.899 --> 00:15:03.470 align:start position:0% of those hard Forks yeah on board miners and<00:15:01.199> miners<00:15:01.740> I<00:15:02.089> don't<00:15:03.089> think<00:15:03.329> you<00:15:03.389> would 00:15:03.470 --> 00:15:03.480 align:start position:0% and miners I don't think you would 00:15:03.480 --> 00:15:06.769 align:start position:0% and miners I don't think you would change<00:15:03.689> anything<00:15:03.810> for<00:15:04.139> miners<00:15:04.439> so<00:15:05.540> the<00:15:06.540> only 00:15:06.769 --> 00:15:06.779 align:start position:0% change anything for miners so the only 00:15:06.779 --> 00:15:08.780 align:start position:0% change anything for miners so the only obviously<00:15:07.439> like<00:15:07.620> the<00:15:07.889> the<00:15:08.069> difficulty<00:15:08.490> bomb 00:15:08.780 --> 00:15:08.790 align:start position:0% obviously like the the difficulty bomb 00:15:08.790 --> 00:15:10.280 align:start position:0% obviously like the the difficulty bomb is<00:15:09.029> one<00:15:09.389> thing<00:15:09.510> that<00:15:09.660> comes<00:15:09.779> up<00:15:09.959> and<00:15:10.139> that's 00:15:10.280 --> 00:15:10.290 align:start position:0% is one thing that comes up and that's 00:15:10.290 --> 00:15:13.490 align:start position:0% is one thing that comes up and that's usually<00:15:10.470> solved<00:15:10.920> through<00:15:11.040> an<00:15:11.130> e<00:15:11.279> p--<00:15:11.689> so<00:15:12.689> if<00:15:12.959> we 00:15:13.490 --> 00:15:13.500 align:start position:0% usually solved through an e p-- so if we 00:15:13.500 --> 00:15:15.259 align:start position:0% usually solved through an e p-- so if we want<00:15:13.740> if<00:15:14.010> we<00:15:14.069> want<00:15:14.339> to<00:15:14.430> delay<00:15:14.639> the<00:15:14.699> difficulty 00:15:15.259 --> 00:15:15.269 align:start position:0% want if we want to delay the difficulty 00:15:15.269 --> 00:15:16.939 align:start position:0% want if we want to delay the difficulty bombed<00:15:15.449> again<00:15:15.750> we<00:15:15.959> simply<00:15:16.290> choose<00:15:16.529> whatever 00:15:16.939 --> 00:15:16.949 align:start position:0% bombed again we simply choose whatever 00:15:16.949 --> 00:15:19.850 align:start position:0% bombed again we simply choose whatever upgrade<00:15:17.550> we<00:15:17.730> want<00:15:18.120> to<00:15:18.209> do<00:15:18.300> that<00:15:18.420> in<00:15:18.600> and<00:15:18.860> and 00:15:19.850 --> 00:15:19.860 align:start position:0% upgrade we want to do that in and and 00:15:19.860 --> 00:15:22.280 align:start position:0% upgrade we want to do that in and and and<00:15:20.250> and<00:15:20.639> add<00:15:20.910> that<00:15:21.089> to<00:15:21.240> that<00:15:21.269> upgrade<00:15:21.689> so<00:15:22.110> the 00:15:22.280 --> 00:15:22.290 align:start position:0% and and add that to that upgrade so the 00:15:22.290 --> 00:15:23.540 align:start position:0% and and add that to that upgrade so the idea<00:15:22.500> then<00:15:22.680> that<00:15:22.709> the<00:15:22.889> difficulty<00:15:23.339> bombs 00:15:23.540 --> 00:15:23.550 align:start position:0% idea then that the difficulty bombs 00:15:23.550 --> 00:15:26.030 align:start position:0% idea then that the difficulty bombs would<00:15:23.759> be<00:15:23.870> changed<00:15:24.870> to<00:15:25.139> line<00:15:25.620> up<00:15:25.769> with<00:15:25.800> this 00:15:26.030 --> 00:15:26.040 align:start position:0% would be changed to line up with this 00:15:26.040 --> 00:15:28.340 align:start position:0% would be changed to line up with this schedule<00:15:26.610> that<00:15:26.850> you're<00:15:26.939> proposing<00:15:27.260> to<00:15:28.260> be 00:15:28.340 --> 00:15:28.350 align:start position:0% schedule that you're proposing to be 00:15:28.350 --> 00:15:30.679 align:start position:0% schedule that you're proposing to be determined<00:15:28.800> in<00:15:29.670> historically<00:15:30.209> for<00:15:30.420> the<00:15:30.480> past 00:15:30.679 --> 00:15:30.689 align:start position:0% determined in historically for the past 00:15:30.689 --> 00:15:32.110 align:start position:0% determined in historically for the past two<00:15:30.839> upgrades<00:15:31.019> it<00:15:31.380> has<00:15:31.500> picked<00:15:31.829> it 00:15:32.110 --> 00:15:32.120 align:start position:0% two upgrades it has picked it 00:15:32.120 --> 00:15:34.329 align:start position:0% two upgrades it has picked it one<00:15:32.270> fork<00:15:32.570> but<00:15:33.260> my<00:15:33.560> understanding<00:15:33.740> was<00:15:34.220> that 00:15:34.329 --> 00:15:34.339 align:start position:0% one fork but my understanding was that 00:15:34.339 --> 00:15:35.320 align:start position:0% one fork but my understanding was that they<00:15:34.430> were<00:15:34.520> trying<00:15:34.730> to<00:15:34.790> kick<00:15:34.970> it<00:15:35.089> out<00:15:35.180> more 00:15:35.320 --> 00:15:35.330 align:start position:0% they were trying to kick it out more 00:15:35.330 --> 00:15:37.030 align:start position:0% they were trying to kick it out more than<00:15:35.480> one<00:15:35.660> pork<00:15:35.930> it's<00:15:36.110> just<00:15:36.350> we've<00:15:36.890> had 00:15:37.030 --> 00:15:37.040 align:start position:0% than one pork it's just we've had 00:15:37.040 --> 00:15:38.290 align:start position:0% than one pork it's just we've had difficulties<00:15:37.670> getting<00:15:37.820> these<00:15:38.029> network 00:15:38.290 --> 00:15:38.300 align:start position:0% difficulties getting these network 00:15:38.300 --> 00:15:43.600 align:start position:0% difficulties getting these network upgrades<00:15:38.630> out<00:15:38.860> thank<00:15:39.860> you<00:15:42.160> and<00:15:43.160> one<00:15:43.460> of<00:15:43.490> the 00:15:43.600 --> 00:15:43.610 align:start position:0% upgrades out thank you and one of the 00:15:43.610 --> 00:15:45.670 align:start position:0% upgrades out thank you and one of the other<00:15:43.730> reasons<00:15:44.150> for<00:15:44.540> proposing<00:15:45.170> the<00:15:45.320> regular 00:15:45.670 --> 00:15:45.680 align:start position:0% other reasons for proposing the regular 00:15:45.680 --> 00:15:47.410 align:start position:0% other reasons for proposing the regular time<00:15:45.920> frame<00:15:46.220> is<00:15:46.370> so<00:15:46.460> the<00:15:46.670> miners<00:15:46.820> know<00:15:47.150> hey 00:15:47.410 --> 00:15:47.420 align:start position:0% time frame is so the miners know hey 00:15:47.420 --> 00:15:49.300 align:start position:0% time frame is so the miners know hey third<00:15:48.110> Wednesday<00:15:48.529> of<00:15:48.560> a<00:15:48.680> month<00:15:48.830> is<00:15:48.920> coming<00:15:49.190> up 00:15:49.300 --> 00:15:49.310 align:start position:0% third Wednesday of a month is coming up 00:15:49.310 --> 00:15:50.680 align:start position:0% third Wednesday of a month is coming up we<00:15:49.430> should<00:15:49.490> check<00:15:49.760> aetherium<00:15:50.150> are<00:15:50.240> reporting 00:15:50.680 --> 00:15:50.690 align:start position:0% we should check aetherium are reporting 00:15:50.690 --> 00:15:52.750 align:start position:0% we should check aetherium are reporting are<00:15:50.779> we<00:15:50.870> not<00:15:51.190> so<00:15:52.190> the<00:15:52.250> miners<00:15:52.430> are<00:15:52.610> another 00:15:52.750 --> 00:15:52.760 align:start position:0% are we not so the miners are another 00:15:52.760 --> 00:15:54.250 align:start position:0% are we not so the miners are another important<00:15:53.210> remember<00:15:53.660> this<00:15:53.779> community<00:15:54.200> that 00:15:54.250 --> 00:15:54.260 align:start position:0% important remember this community that 00:15:54.260 --> 00:15:58.600 align:start position:0% important remember this community that we<00:15:54.320> need<00:15:54.410> to<00:15:54.589> take<00:15:54.770> into<00:15:55.010> consideration<00:15:57.610> any 00:15:58.600 --> 00:15:58.610 align:start position:0% we need to take into consideration any 00:15:58.610 --> 00:16:01.630 align:start position:0% we need to take into consideration any other<00:15:58.790> questions<00:15:59.120> okay 00:16:01.630 --> 00:16:01.640 align:start position:0% 00:16:01.640 --> 00:16:12.650 align:start position:0% back<00:16:01.910> to<00:16:02.000> everybody 00:16:12.650 --> 00:16:12.660 align:start position:0% 00:16:12.660 --> 00:16:14.720 align:start position:0% you