WEBVTT Kind: captions Language: en 00:00:04.610 --> 00:00:08.200 align:start position:0% all<00:00:05.299> right<00:00:05.480> a<00:00:05.509> theory<00:00:05.960> m1x<00:00:06.790> let's<00:00:07.790> talk<00:00:08.029> about 00:00:08.200 --> 00:00:08.210 align:start position:0% all right a theory m1x let's talk about 00:00:08.210 --> 00:00:10.270 align:start position:0% all right a theory m1x let's talk about it<00:00:08.510> for<00:00:09.410> you<00:00:09.500> those<00:00:09.620> of<00:00:09.650> you<00:00:09.830> who<00:00:09.980> don't<00:00:10.129> know 00:00:10.270 --> 00:00:10.280 align:start position:0% it for you those of you who don't know 00:00:10.280 --> 00:00:11.460 align:start position:0% it for you those of you who don't know just<00:00:10.580> a<00:00:10.639> quick<00:00:10.820> intro 00:00:11.460 --> 00:00:11.470 align:start position:0% just a quick intro 00:00:11.470 --> 00:00:13.500 align:start position:0% just a quick intro at<00:00:11.830> the<00:00:11.920> etherium<00:00:12.400> foundation<00:00:13.030> I<00:00:13.120> worked<00:00:13.330> at<00:00:13.450> a 00:00:13.500 --> 00:00:13.510 align:start position:0% at the etherium foundation I worked at a 00:00:13.510 --> 00:00:16.440 align:start position:0% at the etherium foundation I worked at a bank<00:00:13.540> for<00:00:13.960> a<00:00:13.990> few<00:00:14.320> years<00:00:14.740> I<00:00:15.640> have<00:00:15.970> a<00:00:16.000> wife<00:00:16.240> and 00:00:16.440 --> 00:00:16.450 align:start position:0% bank for a few years I have a wife and 00:00:16.450 --> 00:00:18.590 align:start position:0% bank for a few years I have a wife and three<00:00:16.510> cats<00:00:16.900> and<00:00:17.350> I<00:00:17.440> mainly<00:00:17.740> work<00:00:18.070> on 00:00:18.590 --> 00:00:18.600 align:start position:0% three cats and I mainly work on 00:00:18.600 --> 00:00:21.720 align:start position:0% three cats and I mainly work on community<00:00:19.600> security<00:00:20.320> and<00:00:20.500> DevOps<00:00:20.950> at<00:00:21.550> the 00:00:21.720 --> 00:00:21.730 align:start position:0% community security and DevOps at the 00:00:21.730 --> 00:00:24.000 align:start position:0% community security and DevOps at the etherium<00:00:22.180> foundation<00:00:22.840> so<00:00:23.110> if<00:00:23.410> you<00:00:23.680> see<00:00:23.860> me 00:00:24.000 --> 00:00:24.010 align:start position:0% etherium foundation so if you see me 00:00:24.010 --> 00:00:30.060 align:start position:0% etherium foundation so if you see me around<00:00:24.279> please<00:00:24.610> say<00:00:24.880> hi<00:00:25.090> I'm<00:00:25.450> friendly<00:00:28.740> so<00:00:29.740> the 00:00:30.060 --> 00:00:30.070 align:start position:0% around please say hi I'm friendly so the 00:00:30.070 --> 00:00:31.530 align:start position:0% around please say hi I'm friendly so the thing<00:00:30.250> I<00:00:30.310> want<00:00:30.340> you<00:00:30.579> to<00:00:30.640> take<00:00:30.849> away<00:00:31.119> from<00:00:31.180> this 00:00:31.530 --> 00:00:31.540 align:start position:0% thing I want you to take away from this 00:00:31.540 --> 00:00:33.530 align:start position:0% thing I want you to take away from this is<00:00:31.779> that<00:00:31.810> eath<00:00:32.200> 1x<00:00:32.710> represents 00:00:33.530 --> 00:00:33.540 align:start position:0% is that eath 1x represents 00:00:33.540 --> 00:00:36.420 align:start position:0% is that eath 1x represents sustainability<00:00:34.650> that<00:00:35.650> is<00:00:35.800> a<00:00:35.829> really<00:00:36.160> cheesy 00:00:36.420 --> 00:00:36.430 align:start position:0% sustainability that is a really cheesy 00:00:36.430 --> 00:00:38.940 align:start position:0% sustainability that is a really cheesy hashtag<00:00:37.090> that<00:00:37.420> we<00:00:37.630> came<00:00:37.840> up<00:00:37.900> with<00:00:38.079> at<00:00:38.530> one<00:00:38.829> of 00:00:38.940 --> 00:00:38.950 align:start position:0% hashtag that we came up with at one of 00:00:38.950 --> 00:00:41.729 align:start position:0% hashtag that we came up with at one of the<00:00:39.100> 1x<00:00:39.579> meetings<00:00:40.030> and<00:00:40.329> I<00:00:41.050> really<00:00:41.380> like<00:00:41.560> it 00:00:41.729 --> 00:00:41.739 align:start position:0% the 1x meetings and I really like it 00:00:41.739 --> 00:00:44.550 align:start position:0% the 1x meetings and I really like it because<00:00:41.860> it<00:00:42.220> describes<00:00:42.520> how<00:00:43.200> we're<00:00:44.200> trying<00:00:44.470> to 00:00:44.550 --> 00:00:44.560 align:start position:0% because it describes how we're trying to 00:00:44.560 --> 00:00:47.430 align:start position:0% because it describes how we're trying to keep<00:00:44.710> the<00:00:44.890> chain<00:00:45.130> together<00:00:45.370> and<00:00:46.290> how<00:00:47.290> we're 00:00:47.430 --> 00:00:47.440 align:start position:0% keep the chain together and how we're 00:00:47.440 --> 00:00:49.950 align:start position:0% keep the chain together and how we're trying<00:00:47.470> to<00:00:47.800> make<00:00:47.980> aetherium<00:00:48.400> 1.0<00:00:49.090> last<00:00:49.390> for<00:00:49.750> as 00:00:49.950 --> 00:00:49.960 align:start position:0% trying to make aetherium 1.0 last for as 00:00:49.960 --> 00:00:52.800 align:start position:0% trying to make aetherium 1.0 last for as long<00:00:50.200> as<00:00:50.260> necessary<00:00:51.100> and<00:00:51.510> keep<00:00:52.510> the<00:00:52.630> network 00:00:52.800 --> 00:00:52.810 align:start position:0% long as necessary and keep the network 00:00:52.810 --> 00:00:54.660 align:start position:0% long as necessary and keep the network running<00:00:53.380> and<00:00:53.620> efficient<00:00:54.160> for<00:00:54.280> everybody 00:00:54.660 --> 00:00:54.670 align:start position:0% running and efficient for everybody 00:00:54.670 --> 00:01:00.150 align:start position:0% running and efficient for everybody using<00:00:55.090> it<00:00:55.210> Oh<00:00:57.630> before<00:00:58.630> I<00:00:58.780> start<00:00:59.110> this<00:00:59.320> there's 00:01:00.150 --> 00:01:00.160 align:start position:0% using it Oh before I start this there's 00:01:00.160 --> 00:01:02.310 align:start position:0% using it Oh before I start this there's gonna<00:01:00.340> be<00:01:00.520> a<00:01:00.550> time<00:01:01.060> for<00:01:01.270> Q&A<00:01:01.540> at<00:01:01.840> the<00:01:01.900> end<00:01:01.990> so 00:01:02.310 --> 00:01:02.320 align:start position:0% gonna be a time for Q&A at the end so 00:01:02.320 --> 00:01:03.840 align:start position:0% gonna be a time for Q&A at the end so please<00:01:02.350> get<00:01:02.740> your<00:01:02.860> questions<00:01:02.920> ready<00:01:03.430> we'll 00:01:03.840 --> 00:01:03.850 align:start position:0% please get your questions ready we'll 00:01:03.850 --> 00:01:06.539 align:start position:0% please get your questions ready we'll have<00:01:04.000> mics<00:01:04.299> at<00:01:04.509> the<00:01:04.600> audience<00:01:05.220> probably<00:01:06.220> just 00:01:06.539 --> 00:01:06.549 align:start position:0% have mics at the audience probably just 00:01:06.549 --> 00:01:08.340 align:start position:0% have mics at the audience probably just in<00:01:06.670> the<00:01:06.790> aisles<00:01:07.119> I<00:01:07.240> believe<00:01:07.659> so<00:01:07.960> when<00:01:08.229> that 00:01:08.340 --> 00:01:08.350 align:start position:0% in the aisles I believe so when that 00:01:08.350 --> 00:01:11.069 align:start position:0% in the aisles I believe so when that happens<00:01:08.799> I<00:01:09.310> will<00:01:09.729> let<00:01:09.880> you<00:01:10.000> all<00:01:10.150> know<00:01:10.180> oh<00:01:10.600> it's 00:01:11.069 --> 00:01:11.079 align:start position:0% happens I will let you all know oh it's 00:01:11.079 --> 00:01:12.420 align:start position:0% happens I will let you all know oh it's actually<00:01:11.200> gonna<00:01:11.439> be<00:01:11.590> at<00:01:11.680> the<00:01:11.770> front<00:01:12.009> so<00:01:12.220> line 00:01:12.420 --> 00:01:12.430 align:start position:0% actually gonna be at the front so line 00:01:12.430 --> 00:01:13.859 align:start position:0% actually gonna be at the front so line up<00:01:12.610> at<00:01:12.729> the<00:01:12.820> front<00:01:13.000> when<00:01:13.210> you<00:01:13.299> have<00:01:13.420> questions 00:01:13.859 --> 00:01:13.869 align:start position:0% up at the front when you have questions 00:01:13.869 --> 00:01:19.050 align:start position:0% up at the front when you have questions once<00:01:14.079> my<00:01:14.229> presentations<00:01:14.920> over<00:01:16.920> and<00:01:17.920> Wow<00:01:18.760> that 00:01:19.050 --> 00:01:19.060 align:start position:0% once my presentations over and Wow that 00:01:19.060 --> 00:01:22.080 align:start position:0% once my presentations over and Wow that caught<00:01:19.240> that<00:01:19.420> code<00:01:19.770> here's<00:01:20.770> the<00:01:20.920> beginning<00:01:21.090> we 00:01:22.080 --> 00:01:22.090 align:start position:0% caught that code here's the beginning we 00:01:22.090 --> 00:01:24.000 align:start position:0% caught that code here's the beginning we had<00:01:22.270> ad<00:01:22.480> hoc<00:01:22.810> meetings<00:01:23.200> in<00:01:23.380> Prague<00:01:23.620> during 00:01:24.000 --> 00:01:24.010 align:start position:0% had ad hoc meetings in Prague during 00:01:24.010 --> 00:01:27.210 align:start position:0% had ad hoc meetings in Prague during DEFCON<00:01:24.490> 4<00:01:24.900> there<00:01:25.900> was<00:01:25.990> about<00:01:26.200> 25<00:01:26.710> people<00:01:27.010> there 00:01:27.210 --> 00:01:27.220 align:start position:0% DEFCON 4 there was about 25 people there 00:01:27.220 --> 00:01:28.800 align:start position:0% DEFCON 4 there was about 25 people there you<00:01:27.430> could<00:01:27.760> see<00:01:27.940> some<00:01:28.180> of<00:01:28.210> them<00:01:28.360> in<00:01:28.390> that<00:01:28.540> image 00:01:28.800 --> 00:01:28.810 align:start position:0% you could see some of them in that image 00:01:28.810 --> 00:01:30.870 align:start position:0% you could see some of them in that image and<00:01:29.290> we<00:01:29.890> talked<00:01:30.130> about<00:01:30.280> how<00:01:30.640> to<00:01:30.700> achieve 00:01:30.870 --> 00:01:30.880 align:start position:0% and we talked about how to achieve 00:01:30.880 --> 00:01:33.300 align:start position:0% and we talked about how to achieve sustainability<00:01:31.810> we<00:01:32.140> were<00:01:32.260> saying<00:01:32.530> you<00:01:32.830> know 00:01:33.300 --> 00:01:33.310 align:start position:0% sustainability we were saying you know 00:01:33.310 --> 00:01:36.000 align:start position:0% sustainability we were saying you know there's<00:01:33.790> a<00:01:34.000> lot<00:01:34.240> of<00:01:34.270> state<00:01:34.600> bloat<00:01:35.010> there's 00:01:36.000 --> 00:01:36.010 align:start position:0% there's a lot of state bloat there's 00:01:36.010 --> 00:01:38.130 align:start position:0% there's a lot of state bloat there's things<00:01:36.340> going<00:01:36.460> on<00:01:36.880> that<00:01:36.940> are<00:01:37.360> gonna<00:01:37.510> like 00:01:38.130 --> 00:01:38.140 align:start position:0% things going on that are gonna like 00:01:38.140 --> 00:01:41.280 align:start position:0% things going on that are gonna like fundamentally<00:01:38.950> change<00:01:39.340> aetherium<00:01:40.210> when<00:01:40.690> 2.0 00:01:41.280 --> 00:01:41.290 align:start position:0% fundamentally change aetherium when 2.0 00:01:41.290 --> 00:01:43.050 align:start position:0% fundamentally change aetherium when 2.0 comes<00:01:41.560> around<00:01:41.890> how<00:01:42.070> can<00:01:42.280> we<00:01:42.370> best<00:01:42.549> prepare<00:01:43.030> for 00:01:43.050 --> 00:01:43.060 align:start position:0% comes around how can we best prepare for 00:01:43.060 --> 00:01:45.870 align:start position:0% comes around how can we best prepare for those<00:01:43.330> in<00:01:43.510> 1.0<00:01:44.170> while<00:01:45.100> keeping<00:01:45.430> the<00:01:45.520> network 00:01:45.870 --> 00:01:45.880 align:start position:0% those in 1.0 while keeping the network 00:01:45.880 --> 00:01:49.200 align:start position:0% those in 1.0 while keeping the network very<00:01:46.330> very<00:01:46.690> active<00:01:47.140> and<00:01:47.710> are<00:01:48.490> not<00:01:48.729> active<00:01:49.090> but 00:01:49.200 --> 00:01:49.210 align:start position:0% very very active and are not active but 00:01:49.210 --> 00:01:52.770 align:start position:0% very very active and are not active but very<00:01:49.890> efficient<00:01:50.890> very<00:01:51.540> optimizable<00:01:52.540> for 00:01:52.770 --> 00:01:52.780 align:start position:0% very efficient very optimizable for 00:01:52.780 --> 00:01:58.109 align:start position:0% very efficient very optimizable for people<00:01:52.990> to<00:01:53.080> use<00:01:55.830> so<00:01:56.830> from<00:01:57.549> that<00:01:57.700> meeting<00:01:57.940> in 00:01:58.109 --> 00:01:58.119 align:start position:0% people to use so from that meeting in 00:01:58.119 --> 00:02:00.120 align:start position:0% people to use so from that meeting in Prague<00:01:58.390> we<00:01:58.630> came<00:01:58.869> with<00:01:59.020> four<00:01:59.350> working<00:01:59.860> groups 00:02:00.120 --> 00:02:00.130 align:start position:0% Prague we came with four working groups 00:02:00.130 --> 00:02:03.270 align:start position:0% Prague we came with four working groups the<00:02:00.610> simulation<00:02:01.240> working<00:02:01.659> group<00:02:01.979> state<00:02:02.979> rent 00:02:03.270 --> 00:02:03.280 align:start position:0% the simulation working group state rent 00:02:03.280 --> 00:02:05.160 align:start position:0% the simulation working group state rent working<00:02:03.640> group<00:02:03.880> the<00:02:04.060> chain<00:02:04.299> pruning<00:02:04.750> working 00:02:05.160 --> 00:02:05.170 align:start position:0% working group the chain pruning working 00:02:05.170 --> 00:02:07.699 align:start position:0% working group the chain pruning working group<00:02:05.350> and<00:02:05.560> the<00:02:05.619> ewaz<00:02:05.950> and<00:02:06.220> working<00:02:06.549> group<00:02:06.790> so 00:02:07.699 --> 00:02:07.709 align:start position:0% group and the ewaz and working group so 00:02:07.709 --> 00:02:10.440 align:start position:0% group and the ewaz and working group so simulation<00:02:08.709> working<00:02:09.099> group<00:02:09.369> was<00:02:09.789> put 00:02:10.440 --> 00:02:10.450 align:start position:0% simulation working group was put 00:02:10.450 --> 00:02:13.110 align:start position:0% simulation working group was put together<00:02:10.599> to<00:02:10.989> understand<00:02:11.500> how<00:02:11.769> can<00:02:12.129> we<00:02:12.370> look 00:02:13.110 --> 00:02:13.120 align:start position:0% together to understand how can we look 00:02:13.120 --> 00:02:14.089 align:start position:0% together to understand how can we look at 00:02:14.089 --> 00:02:14.099 align:start position:0% at 00:02:14.099 --> 00:02:16.339 align:start position:0% at how<00:02:14.730> much<00:02:14.909> state<00:02:15.420> bloat<00:02:15.689> is<00:02:15.840> affecting 00:02:16.339 --> 00:02:16.349 align:start position:0% how much state bloat is affecting 00:02:16.349 --> 00:02:20.030 align:start position:0% how much state bloat is affecting aetherium<00:02:17.450> what<00:02:18.450> can<00:02:18.599> we<00:02:18.719> do<00:02:18.930> about<00:02:19.379> like 00:02:20.030 --> 00:02:20.040 align:start position:0% aetherium what can we do about like 00:02:20.040 --> 00:02:22.099 align:start position:0% aetherium what can we do about like coming<00:02:20.430> up<00:02:20.519> with<00:02:20.549> graphs<00:02:20.939> figures<00:02:21.420> numbers<00:02:21.930> to 00:02:22.099 --> 00:02:22.109 align:start position:0% coming up with graphs figures numbers to 00:02:22.109 --> 00:02:24.349 align:start position:0% coming up with graphs figures numbers to make<00:02:22.260> it<00:02:22.379> help<00:02:22.590> us<00:02:22.709> understand<00:02:23.250> more<00:02:23.370> the 00:02:24.349 --> 00:02:24.359 align:start position:0% make it help us understand more the 00:02:24.359 --> 00:02:26.119 align:start position:0% make it help us understand more the state<00:02:24.599> rent<00:02:24.989> working<00:02:25.379> group<00:02:25.620> which<00:02:25.829> has<00:02:25.980> now 00:02:26.119 --> 00:02:26.129 align:start position:0% state rent working group which has now 00:02:26.129 --> 00:02:28.130 align:start position:0% state rent working group which has now turned<00:02:26.189> into<00:02:26.609> the<00:02:27.090> state<00:02:27.299> be<00:02:27.540> working<00:02:27.959> group 00:02:28.130 --> 00:02:28.140 align:start position:0% turned into the state be working group 00:02:28.140 --> 00:02:31.099 align:start position:0% turned into the state be working group which<00:02:28.319> has<00:02:28.439> now<00:02:28.590> turned<00:02:28.650> into<00:02:29.099> the<00:02:30.109> like 00:02:31.099 --> 00:02:31.109 align:start position:0% which has now turned into the like 00:02:31.109 --> 00:02:33.020 align:start position:0% which has now turned into the like another<00:02:31.530> whole<00:02:31.859> working<00:02:32.400> group<00:02:32.579> kind<00:02:32.819> of<00:02:32.939> a 00:02:33.020 --> 00:02:33.030 align:start position:0% another whole working group kind of a 00:02:33.030 --> 00:02:35.390 align:start position:0% another whole working group kind of a thing<00:02:33.239> is<00:02:33.840> about<00:02:34.500> addressing<00:02:35.010> the<00:02:35.220> growing 00:02:35.390 --> 00:02:35.400 align:start position:0% thing is about addressing the growing 00:02:35.400 --> 00:02:38.869 align:start position:0% thing is about addressing the growing state<00:02:35.959> maybe<00:02:36.959> advance<00:02:37.560> snapshot<00:02:38.280> sinking<00:02:38.760> and 00:02:38.869 --> 00:02:38.879 align:start position:0% state maybe advance snapshot sinking and 00:02:38.879 --> 00:02:40.580 align:start position:0% state maybe advance snapshot sinking and stateless<00:02:39.209> clients<00:02:39.750> are<00:02:39.870> also<00:02:40.109> explored 00:02:40.580 --> 00:02:40.590 align:start position:0% stateless clients are also explored 00:02:40.590 --> 00:02:43.369 align:start position:0% stateless clients are also explored later<00:02:40.889> on<00:02:41.540> there's<00:02:42.540> just<00:02:42.599> a<00:02:42.810> ton<00:02:42.989> of<00:02:43.049> stuff 00:02:43.369 --> 00:02:43.379 align:start position:0% later on there's just a ton of stuff 00:02:43.379 --> 00:02:46.429 align:start position:0% later on there's just a ton of stuff like<00:02:44.219> eath<00:02:44.849> 2.0<00:02:45.569> Danny's<00:02:46.109> going<00:02:46.230> to<00:02:46.319> talk 00:02:46.429 --> 00:02:46.439 align:start position:0% like eath 2.0 Danny's going to talk 00:02:46.439 --> 00:02:48.920 align:start position:0% like eath 2.0 Danny's going to talk about<00:02:46.590> this<00:02:46.799> after<00:02:47.099> me<00:02:47.250> but<00:02:47.400> if<00:02:47.579> 2.0<00:02:48.269> is<00:02:48.480> gonna 00:02:48.920 --> 00:02:48.930 align:start position:0% about this after me but if 2.0 is gonna 00:02:48.930 --> 00:02:50.929 align:start position:0% about this after me but if 2.0 is gonna have<00:02:49.079> a<00:02:49.109> lot<00:02:49.319> of<00:02:49.349> changes<00:02:50.040> and<00:02:50.069> figuring<00:02:50.790> out 00:02:50.929 --> 00:02:50.939 align:start position:0% have a lot of changes and figuring out 00:02:50.939 --> 00:02:53.539 align:start position:0% have a lot of changes and figuring out how<00:02:51.209> to<00:02:51.239> store<00:02:51.659> information<00:02:51.870> in<00:02:52.560> a<00:02:52.680> way<00:02:52.709> where 00:02:53.539 --> 00:02:53.549 align:start position:0% how to store information in a way where 00:02:53.549 --> 00:02:55.640 align:start position:0% how to store information in a way where it's<00:02:54.389> not<00:02:54.480> going<00:02:54.689> to<00:02:54.750> blow<00:02:54.959> up<00:02:55.109> people's<00:02:55.439> hard 00:02:55.640 --> 00:02:55.650 align:start position:0% it's not going to blow up people's hard 00:02:55.650 --> 00:02:57.589 align:start position:0% it's not going to blow up people's hard drives<00:02:56.010> so<00:02:56.280> can<00:02:56.879> we<00:02:56.970> address<00:02:57.180> some<00:02:57.299> of<00:02:57.450> those 00:02:57.589 --> 00:02:57.599 align:start position:0% drives so can we address some of those 00:02:57.599 --> 00:03:00.229 align:start position:0% drives so can we address some of those problems<00:02:57.659> now<00:02:58.349> that<00:02:58.739> I<00:02:58.769> mean<00:02:59.010> the<00:02:59.609> fact<00:02:59.970> is 00:03:00.229 --> 00:03:00.239 align:start position:0% problems now that I mean the fact is 00:03:00.239 --> 00:03:02.690 align:start position:0% problems now that I mean the fact is people<00:03:01.139> are<00:03:01.230> just<00:03:01.409> storing<00:03:01.859> this<00:03:02.010> data<00:03:02.069> for 00:03:02.690 --> 00:03:02.700 align:start position:0% people are just storing this data for 00:03:02.700 --> 00:03:04.640 align:start position:0% people are just storing this data for free<00:03:02.909> and<00:03:03.239> it's<00:03:03.359> you<00:03:03.900> know<00:03:04.019> a<00:03:04.049> difficult<00:03:04.409> thing 00:03:04.640 --> 00:03:04.650 align:start position:0% free and it's you know a difficult thing 00:03:04.650 --> 00:03:06.530 align:start position:0% free and it's you know a difficult thing to<00:03:04.980> incentivize<00:03:05.519> and<00:03:05.760> figure<00:03:06.000> out<00:03:06.060> what<00:03:06.269> to<00:03:06.389> do 00:03:06.530 --> 00:03:06.540 align:start position:0% to incentivize and figure out what to do 00:03:06.540 --> 00:03:08.780 align:start position:0% to incentivize and figure out what to do with<00:03:06.769> you<00:03:07.769> can't<00:03:08.010> even<00:03:08.159> run<00:03:08.370> in<00:03:08.489> aetherium 00:03:08.780 --> 00:03:08.790 align:start position:0% with you can't even run in aetherium 00:03:08.790 --> 00:03:11.420 align:start position:0% with you can't even run in aetherium client<00:03:09.329> on<00:03:09.480> a<00:03:09.680> regular<00:03:10.680> hard<00:03:10.980> disk<00:03:11.220> drive 00:03:11.420 --> 00:03:11.430 align:start position:0% client on a regular hard disk drive 00:03:11.430 --> 00:03:12.860 align:start position:0% client on a regular hard disk drive anymore<00:03:11.790> it<00:03:11.879> has<00:03:11.909> to<00:03:12.120> be<00:03:12.209> on<00:03:12.299> a<00:03:12.329> solid-state 00:03:12.860 --> 00:03:12.870 align:start position:0% anymore it has to be on a solid-state 00:03:12.870 --> 00:03:14.929 align:start position:0% anymore it has to be on a solid-state drive<00:03:12.900> because<00:03:13.379> of<00:03:13.560> the<00:03:13.680> disk<00:03:13.980> IO<00:03:14.189> reads<00:03:14.609> or 00:03:14.929 --> 00:03:14.939 align:start position:0% drive because of the disk IO reads or 00:03:14.939 --> 00:03:18.409 align:start position:0% drive because of the disk IO reads or the<00:03:15.209> disk<00:03:15.389> IO<00:03:15.859> so<00:03:16.859> that's<00:03:17.790> that<00:03:17.970> working<00:03:18.389> group 00:03:18.409 --> 00:03:18.419 align:start position:0% the disk IO so that's that working group 00:03:18.419 --> 00:03:21.589 align:start position:0% the disk IO so that's that working group we<00:03:18.720> have<00:03:18.840> chain<00:03:19.139> pruning<00:03:20.030> can<00:03:21.030> we<00:03:21.180> archive 00:03:21.589 --> 00:03:21.599 align:start position:0% we have chain pruning can we archive 00:03:21.599 --> 00:03:24.589 align:start position:0% we have chain pruning can we archive blocks<00:03:21.959> can<00:03:22.319> we<00:03:22.409> archive<00:03:22.769> logs<00:03:23.329> how<00:03:24.329> many<00:03:24.479> of 00:03:24.589 --> 00:03:24.599 align:start position:0% blocks can we archive logs how many of 00:03:24.599 --> 00:03:28.580 align:start position:0% blocks can we archive logs how many of you<00:03:24.690> here<00:03:24.900> adapt<00:03:25.229> developers<00:03:27.199> keep<00:03:28.199> your<00:03:28.379> hand 00:03:28.580 --> 00:03:28.590 align:start position:0% you here adapt developers keep your hand 00:03:28.590 --> 00:03:33.199 align:start position:0% you here adapt developers keep your hand up<00:03:28.799> if<00:03:29.129> you<00:03:29.400> use<00:03:29.699> logs<00:03:30.090> in<00:03:30.419> your<00:03:30.540> DAP<00:03:32.090> keep<00:03:33.090> your 00:03:33.199 --> 00:03:33.209 align:start position:0% up if you use logs in your DAP keep your 00:03:33.209 --> 00:03:34.909 align:start position:0% up if you use logs in your DAP keep your hand<00:03:33.419> up<00:03:33.599> if<00:03:33.780> you're<00:03:33.930> a<00:03:33.959> cheater<00:03:34.379> and<00:03:34.769> you're 00:03:34.909 --> 00:03:34.919 align:start position:0% hand up if you're a cheater and you're 00:03:34.919 --> 00:03:36.860 align:start position:0% hand up if you're a cheater and you're using<00:03:35.159> logs<00:03:35.579> because<00:03:36.269> there<00:03:36.449> are<00:03:36.540> cheaper 00:03:36.860 --> 00:03:36.870 align:start position:0% using logs because there are cheaper 00:03:36.870 --> 00:03:40.250 align:start position:0% using logs because there are cheaper storage<00:03:37.349> than<00:03:37.560> on<00:03:37.650> chain<00:03:37.949> storage<00:03:38.569> okay<00:03:39.569> yes 00:03:40.250 --> 00:03:40.260 align:start position:0% storage than on chain storage okay yes 00:03:40.260 --> 00:03:41.809 align:start position:0% storage than on chain storage okay yes that's<00:03:40.560> exactly<00:03:40.799> why<00:03:41.310> we<00:03:41.489> might<00:03:41.669> need<00:03:41.760> to 00:03:41.809 --> 00:03:41.819 align:start position:0% that's exactly why we might need to 00:03:41.819 --> 00:03:43.780 align:start position:0% that's exactly why we might need to archive<00:03:42.030> logs<00:03:42.510> it<00:03:42.690> was<00:03:42.780> never<00:03:42.959> really<00:03:43.199> like 00:03:43.780 --> 00:03:43.790 align:start position:0% archive logs it was never really like 00:03:43.790 --> 00:03:46.460 align:start position:0% archive logs it was never really like explicitly<00:03:44.790> said<00:03:45.150> if<00:03:45.510> we're<00:03:45.959> going<00:03:45.989> to<00:03:46.229> have 00:03:46.460 --> 00:03:46.470 align:start position:0% explicitly said if we're going to have 00:03:46.470 --> 00:03:48.259 align:start position:0% explicitly said if we're going to have logs<00:03:46.829> last<00:03:47.099> forever<00:03:47.519> they're<00:03:47.729> supposed<00:03:48.030> to<00:03:48.120> be 00:03:48.259 --> 00:03:48.269 align:start position:0% logs last forever they're supposed to be 00:03:48.269 --> 00:03:51.020 align:start position:0% logs last forever they're supposed to be for<00:03:48.449> error<00:03:48.690> messages<00:03:49.260> and<00:03:49.430> for<00:03:50.430> just<00:03:50.669> you<00:03:50.940> know 00:03:51.020 --> 00:03:51.030 align:start position:0% for error messages and for just you know 00:03:51.030 --> 00:03:52.580 align:start position:0% for error messages and for just you know tracking<00:03:51.359> certain<00:03:51.810> things<00:03:52.049> but<00:03:52.260> now<00:03:52.409> that 00:03:52.580 --> 00:03:52.590 align:start position:0% tracking certain things but now that 00:03:52.590 --> 00:03:54.589 align:start position:0% tracking certain things but now that they're<00:03:52.979> a<00:03:53.010> cheaper<00:03:53.370> way<00:03:53.519> of<00:03:53.639> storage<00:03:54.060> that's 00:03:54.589 --> 00:03:54.599 align:start position:0% they're a cheaper way of storage that's 00:03:54.599 --> 00:03:56.809 align:start position:0% they're a cheaper way of storage that's unbalancing<00:03:55.530> things<00:03:55.769> a<00:03:55.949> lot<00:03:56.159> and<00:03:56.489> it's 00:03:56.809 --> 00:03:56.819 align:start position:0% unbalancing things a lot and it's 00:03:56.819 --> 00:03:58.399 align:start position:0% unbalancing things a lot and it's causing<00:03:57.269> some<00:03:57.419> state<00:03:57.689> bloat<00:03:57.959> so<00:03:58.169> can<00:03:58.319> we 00:03:58.399 --> 00:03:58.409 align:start position:0% causing some state bloat so can we 00:03:58.409 --> 00:04:01.009 align:start position:0% causing some state bloat so can we archive<00:03:58.859> those<00:03:59.069> can<00:03:59.370> we<00:03:59.459> maybe<00:03:59.609> make<00:03:59.879> it<00:04:00.090> so 00:04:01.009 --> 00:04:01.019 align:start position:0% archive those can we maybe make it so 00:04:01.019 --> 00:04:02.869 align:start position:0% archive those can we maybe make it so that<00:04:01.049> you<00:04:01.409> have<00:04:01.799> to<00:04:02.010> fetch<00:04:02.340> them<00:04:02.609> from<00:04:02.790> an 00:04:02.869 --> 00:04:02.879 align:start position:0% that you have to fetch them from an 00:04:02.879 --> 00:04:05.420 align:start position:0% that you have to fetch them from an external<00:04:03.299> source<00:04:03.859> what<00:04:04.859> we're<00:04:05.069> looking<00:04:05.310> into 00:04:05.420 --> 00:04:05.430 align:start position:0% external source what we're looking into 00:04:05.430 --> 00:04:07.580 align:start position:0% external source what we're looking into things<00:04:05.699> like<00:04:05.879> that<00:04:06.209> and<00:04:06.479> then<00:04:06.989> there<00:04:07.379> was<00:04:07.470> the 00:04:07.580 --> 00:04:07.590 align:start position:0% things like that and then there was the 00:04:07.590 --> 00:04:09.379 align:start position:0% things like that and then there was the awasum<00:04:08.129> Working<00:04:08.459> Group<00:04:08.609> that<00:04:08.879> determines 00:04:09.379 --> 00:04:09.389 align:start position:0% awasum Working Group that determines 00:04:09.389 --> 00:04:12.710 align:start position:0% awasum Working Group that determines what<00:04:10.199> for<00:04:10.379> me<00:04:10.500> was<00:04:10.709> going<00:04:11.069> into<00:04:11.250> 1x<00:04:11.669> and<00:04:11.879> 2.0<00:04:12.449> a 00:04:12.710 --> 00:04:12.720 align:start position:0% what for me was going into 1x and 2.0 a 00:04:12.720 --> 00:04:15.170 align:start position:0% what for me was going into 1x and 2.0 a lot<00:04:13.290> of<00:04:13.409> he<00:04:13.530> was<00:04:13.709> and<00:04:13.949> workshops<00:04:14.699> and<00:04:15.000> talks 00:04:15.170 --> 00:04:15.180 align:start position:0% lot of he was and workshops and talks 00:04:15.180 --> 00:04:17.330 align:start position:0% lot of he was and workshops and talks are<00:04:15.629> around<00:04:15.989> Def<00:04:16.199> Con<00:04:16.440> so<00:04:16.470> feel<00:04:16.859> free<00:04:16.889> to<00:04:17.070> jump 00:04:17.330 --> 00:04:17.340 align:start position:0% are around Def Con so feel free to jump 00:04:17.340 --> 00:04:22.009 align:start position:0% are around Def Con so feel free to jump into<00:04:17.489> those<00:04:17.699> for<00:04:17.970> more<00:04:18.120> information<00:04:20.239> so<00:04:21.239> at 00:04:22.009 --> 00:04:22.019 align:start position:0% into those for more information so at 00:04:22.019 --> 00:04:24.649 align:start position:0% into those for more information so at the<00:04:22.469> time<00:04:22.740> of<00:04:23.099> Prague<00:04:23.669> but<00:04:24.000> basically<00:04:24.389> between 00:04:24.649 --> 00:04:24.659 align:start position:0% the time of Prague but basically between 00:04:24.659 --> 00:04:28.050 align:start position:0% the time of Prague but basically between late<00:04:25.440> last<00:04:25.710> year<00:04:25.919> early<00:04:26.340> this<00:04:26.520> year 00:04:28.050 --> 00:04:28.060 align:start position:0% late last year early this year 00:04:28.060 --> 00:04:30.480 align:start position:0% late last year early this year meant<00:04:28.690> a<00:04:28.870> renewed<00:04:29.260> effort<00:04:29.710> to<00:04:29.890> invest<00:04:30.250> in<00:04:30.400> the 00:04:30.480 --> 00:04:30.490 align:start position:0% meant a renewed effort to invest in the 00:04:30.490 --> 00:04:33.240 align:start position:0% meant a renewed effort to invest in the existing<00:04:31.000> eath<00:04:31.270> 1.0<00:04:31.930> network<00:04:32.350> to<00:04:32.830> ensure<00:04:33.130> it 00:04:33.240 --> 00:04:33.250 align:start position:0% existing eath 1.0 network to ensure it 00:04:33.250 --> 00:04:35.940 align:start position:0% existing eath 1.0 network to ensure it can<00:04:33.400> survive<00:04:33.910> and<00:04:34.240> thrive<00:04:34.390> indefinitely<00:04:35.200> so 00:04:35.940 --> 00:04:35.950 align:start position:0% can survive and thrive indefinitely so 00:04:35.950 --> 00:04:37.350 align:start position:0% can survive and thrive indefinitely so that's<00:04:36.130> what<00:04:36.280> I<00:04:36.310> alerted<00:04:36.640> to<00:04:36.790> earlier<00:04:37.210> that's 00:04:37.350 --> 00:04:37.360 align:start position:0% that's what I alerted to earlier that's 00:04:37.360 --> 00:04:39.660 align:start position:0% that's what I alerted to earlier that's the<00:04:37.540> first<00:04:37.780> version<00:04:38.710> of<00:04:38.830> what<00:04:39.040> sustainability 00:04:39.660 --> 00:04:39.670 align:start position:0% the first version of what sustainability 00:04:39.670 --> 00:04:44.360 align:start position:0% the first version of what sustainability is<00:04:39.880> I'm<00:04:40.540> gonna<00:04:40.690> get<00:04:40.870> to<00:04:40.960> the<00:04:41.080> second<00:04:41.500> one<00:04:41.680> later 00:04:44.360 --> 00:04:44.370 align:start position:0% 00:04:44.370 --> 00:04:48.690 align:start position:0% so<00:04:45.390> if<00:04:46.390> 2.0<00:04:47.200> is<00:04:47.470> sexy<00:04:47.980> right<00:04:48.130> now<00:04:48.190> it's<00:04:48.520> like 00:04:48.690 --> 00:04:48.700 align:start position:0% so if 2.0 is sexy right now it's like 00:04:48.700 --> 00:04:50.430 align:start position:0% so if 2.0 is sexy right now it's like the<00:04:48.850> new<00:04:49.000> hot<00:04:49.270> thing<00:04:49.300> everyone<00:04:49.930> wants<00:04:49.960> to<00:04:50.230> work 00:04:50.430 --> 00:04:50.440 align:start position:0% the new hot thing everyone wants to work 00:04:50.440 --> 00:04:52.920 align:start position:0% the new hot thing everyone wants to work on<00:04:50.650> it<00:04:50.890> but<00:04:51.400> we<00:04:51.520> still<00:04:51.700> have<00:04:51.850> this<00:04:51.970> 1.0<00:04:52.630> chain 00:04:52.920 --> 00:04:52.930 align:start position:0% on it but we still have this 1.0 chain 00:04:52.930 --> 00:04:56.460 align:start position:0% on it but we still have this 1.0 chain and<00:04:53.230> up<00:04:54.160> until<00:04:54.400> you<00:04:55.270> know<00:04:55.300> last<00:04:56.170> year<00:04:56.350> in 00:04:56.460 --> 00:04:56.470 align:start position:0% and up until you know last year in 00:04:56.470 --> 00:04:58.470 align:start position:0% and up until you know last year in Prague<00:04:56.740> there<00:04:57.040> was<00:04:57.160> some<00:04:57.340> kind<00:04:57.670> of<00:04:57.850> discomfort 00:04:58.470 --> 00:04:58.480 align:start position:0% Prague there was some kind of discomfort 00:04:58.480 --> 00:05:01.050 align:start position:0% Prague there was some kind of discomfort and<00:04:58.810> some<00:04:59.110> like<00:04:59.430> things<00:05:00.430> that<00:05:00.640> we<00:05:00.730> really<00:05:00.940> need 00:05:01.050 --> 00:05:01.060 align:start position:0% and some like things that we really need 00:05:01.060 --> 00:05:02.690 align:start position:0% and some like things that we really need to<00:05:01.090> address<00:05:01.330> about<00:05:01.840> the<00:05:01.990> fact<00:05:02.200> that 00:05:02.690 --> 00:05:02.700 align:start position:0% to address about the fact that 00:05:02.700 --> 00:05:05.040 align:start position:0% to address about the fact that developers<00:05:03.700> were<00:05:03.820> dropping<00:05:04.120> off<00:05:04.360> doing<00:05:04.750> stuff 00:05:05.040 --> 00:05:05.050 align:start position:0% developers were dropping off doing stuff 00:05:05.050 --> 00:05:08.040 align:start position:0% developers were dropping off doing stuff with<00:05:05.290> 1.0<00:05:05.950> to<00:05:06.010> do<00:05:06.160> stuff<00:05:06.400> on<00:05:06.520> 2.0<00:05:07.150> and<00:05:07.420> we<00:05:07.930> need 00:05:08.040 --> 00:05:08.050 align:start position:0% with 1.0 to do stuff on 2.0 and we need 00:05:08.050 --> 00:05:09.960 align:start position:0% with 1.0 to do stuff on 2.0 and we need to<00:05:08.140> make<00:05:08.290> it<00:05:08.440> so<00:05:08.620> that<00:05:08.650> 1.0<00:05:09.430> is<00:05:09.700> still 00:05:09.960 --> 00:05:09.970 align:start position:0% to make it so that 1.0 is still 00:05:09.970 --> 00:05:12.690 align:start position:0% to make it so that 1.0 is still sustainable<00:05:10.660> and<00:05:10.840> 1.0<00:05:11.470> is<00:05:11.830> still<00:05:12.190> fun<00:05:12.400> to<00:05:12.550> work 00:05:12.690 --> 00:05:12.700 align:start position:0% sustainable and 1.0 is still fun to work 00:05:12.700 --> 00:05:15.990 align:start position:0% sustainable and 1.0 is still fun to work with<00:05:12.760> and<00:05:13.180> has<00:05:13.720> goals<00:05:14.140> and<00:05:14.530> like<00:05:15.100> a<00:05:15.310> know<00:05:15.700> its 00:05:15.990 --> 00:05:16.000 align:start position:0% with and has goals and like a know its 00:05:16.000 --> 00:05:18.720 align:start position:0% with and has goals and like a know its own<00:05:16.210> driven<00:05:16.690> architecture<00:05:17.470> just<00:05:18.040> like<00:05:18.160> 2.0 00:05:18.720 --> 00:05:18.730 align:start position:0% own driven architecture just like 2.0 00:05:18.730 --> 00:05:23.850 align:start position:0% own driven architecture just like 2.0 has<00:05:18.940> so<00:05:20.250> not<00:05:21.250> that<00:05:21.430> we<00:05:21.520> don't<00:05:21.700> like<00:05:21.940> 2.0<00:05:22.540> but<00:05:23.230> it 00:05:23.850 --> 00:05:23.860 align:start position:0% has so not that we don't like 2.0 but it 00:05:23.860 --> 00:05:25.740 align:start position:0% has so not that we don't like 2.0 but it is<00:05:24.040> let<00:05:24.280> you<00:05:24.370> know<00:05:24.400> the<00:05:24.670> sexier<00:05:25.120> younger 00:05:25.740 --> 00:05:25.750 align:start position:0% is let you know the sexier younger 00:05:25.750 --> 00:05:28.680 align:start position:0% is let you know the sexier younger brother<00:05:25.990> of<00:05:26.080> eath<00:05:26.770> 1.0<00:05:27.460> and<00:05:27.730> we<00:05:28.330> need<00:05:28.480> to<00:05:28.540> make 00:05:28.680 --> 00:05:28.690 align:start position:0% brother of eath 1.0 and we need to make 00:05:28.690 --> 00:05:31.080 align:start position:0% brother of eath 1.0 and we need to make sure<00:05:28.720> that<00:05:29.140> 1.0<00:05:29.980> and<00:05:30.100> one<00:05:30.250> point<00:05:30.520> X<00:05:30.670> stays<00:05:30.910> in 00:05:31.080 --> 00:05:31.090 align:start position:0% sure that 1.0 and one point X stays in 00:05:31.090 --> 00:05:36.570 align:start position:0% sure that 1.0 and one point X stays in the<00:05:31.180> forefront<00:05:31.600> until<00:05:32.050> we<00:05:32.169> can<00:05:32.320> get<00:05:32.470> to<00:05:32.500> 2.0<00:05:35.580> ok 00:05:36.570 --> 00:05:36.580 align:start position:0% the forefront until we can get to 2.0 ok 00:05:36.580 --> 00:05:38.159 align:start position:0% the forefront until we can get to 2.0 ok so<00:05:36.640> this<00:05:36.940> was<00:05:37.180> kind<00:05:37.450> of<00:05:37.600> I<00:05:37.690> don't<00:05:37.750> know<00:05:37.870> if<00:05:37.960> how 00:05:38.159 --> 00:05:38.169 align:start position:0% so this was kind of I don't know if how 00:05:38.169 --> 00:05:39.930 align:start position:0% so this was kind of I don't know if how many<00:05:38.320> of<00:05:38.380> y'all<00:05:38.530> remember<00:05:38.710> this<00:05:38.940> controversy 00:05:39.930 --> 00:05:39.940 align:start position:0% many of y'all remember this controversy 00:05:39.940 --> 00:05:42.210 align:start position:0% many of y'all remember this controversy from<00:05:40.090> last<00:05:40.390> year<00:05:40.690> but<00:05:40.870> like<00:05:41.470> the<00:05:41.980> Prague 00:05:42.210 --> 00:05:42.220 align:start position:0% from last year but like the Prague 00:05:42.220 --> 00:05:43.560 align:start position:0% from last year but like the Prague meetings<00:05:42.669> that<00:05:42.730> I<00:05:42.820> talked<00:05:43.060> about<00:05:43.180> the<00:05:43.419> ad-hoc 00:05:43.560 --> 00:05:43.570 align:start position:0% meetings that I talked about the ad-hoc 00:05:43.570 --> 00:05:46.290 align:start position:0% meetings that I talked about the ad-hoc ones<00:05:44.050> with<00:05:44.230> 20<00:05:44.590> to<00:05:44.680> 25<00:05:45.070> people<00:05:45.340> a<00:05:45.730> lot<00:05:46.270> of 00:05:46.290 --> 00:05:46.300 align:start position:0% ones with 20 to 25 people a lot of 00:05:46.300 --> 00:05:48.000 align:start position:0% ones with 20 to 25 people a lot of people<00:05:46.480> said<00:05:46.810> those<00:05:46.990> were<00:05:47.140> secret<00:05:47.620> meetings 00:05:48.000 --> 00:05:48.010 align:start position:0% people said those were secret meetings 00:05:48.010 --> 00:05:50.670 align:start position:0% people said those were secret meetings and<00:05:48.310> the<00:05:48.790> reason<00:05:49.090> for<00:05:49.240> that<00:05:49.300> was<00:05:49.660> we<00:05:50.320> did<00:05:50.500> have 00:05:50.670 --> 00:05:50.680 align:start position:0% and the reason for that was we did have 00:05:50.680 --> 00:05:53.790 align:start position:0% and the reason for that was we did have this<00:05:50.830> note<00:05:51.130> sheet<00:05:51.400> passed<00:05:51.669> around<00:05:52.650> during<00:05:53.650> it 00:05:53.790 --> 00:05:53.800 align:start position:0% this note sheet passed around during it 00:05:53.800 --> 00:05:56.640 align:start position:0% this note sheet passed around during it that<00:05:54.250> I<00:05:54.460> think<00:05:54.750> someone<00:05:55.750> from<00:05:55.810> consensus<00:05:56.410> took 00:05:56.640 --> 00:05:56.650 align:start position:0% that I think someone from consensus took 00:05:56.650 --> 00:06:01.760 align:start position:0% that I think someone from consensus took and<00:05:57.840> they<00:05:58.840> basically<00:05:59.200> took<00:05:59.530> notes<00:05:59.860> down<00:06:00.160> and 00:06:01.760 --> 00:06:01.770 align:start position:0% and they basically took notes down and 00:06:01.770 --> 00:06:04.800 align:start position:0% and they basically took notes down and they<00:06:02.770> were<00:06:02.830> released<00:06:03.550> later<00:06:03.970> or<00:06:04.570> they<00:06:04.750> were 00:06:04.800 --> 00:06:04.810 align:start position:0% they were released later or they were 00:06:04.810 --> 00:06:06.360 align:start position:0% they were released later or they were going<00:06:05.080> to<00:06:05.140> be<00:06:05.230> released<00:06:05.530> later<00:06:05.620> but<00:06:06.100> they<00:06:06.220> got 00:06:06.360 --> 00:06:06.370 align:start position:0% going to be released later but they got 00:06:06.370 --> 00:06:10.920 align:start position:0% going to be released later but they got like<00:06:06.700> leaked<00:06:07.150> early<00:06:07.660> because<00:06:09.210> some<00:06:10.210> one<00:06:10.840> of 00:06:10.920 --> 00:06:10.930 align:start position:0% like leaked early because some one of 00:06:10.930 --> 00:06:12.330 align:start position:0% like leaked early because some one of the<00:06:11.050> core<00:06:11.260> developers<00:06:11.710> thought<00:06:11.980> that<00:06:12.190> people 00:06:12.330 --> 00:06:12.340 align:start position:0% the core developers thought that people 00:06:12.340 --> 00:06:13.740 align:start position:0% the core developers thought that people should<00:06:12.610> know<00:06:12.730> about<00:06:12.850> the<00:06:13.090> notes<00:06:13.270> before<00:06:13.660> we 00:06:13.740 --> 00:06:13.750 align:start position:0% should know about the notes before we 00:06:13.750 --> 00:06:15.390 align:start position:0% should know about the notes before we were<00:06:13.870> ready<00:06:14.080> so<00:06:14.470> we<00:06:14.650> were<00:06:14.740> talking<00:06:15.100> about<00:06:15.190> one 00:06:15.390 --> 00:06:15.400 align:start position:0% were ready so we were talking about one 00:06:15.400 --> 00:06:17.700 align:start position:0% were ready so we were talking about one X<00:06:15.580> in<00:06:15.760> Prague<00:06:16.030> it<00:06:16.540> was<00:06:16.690> like<00:06:16.840> 20<00:06:17.200> people<00:06:17.380> in<00:06:17.620> a 00:06:17.700 --> 00:06:17.710 align:start position:0% X in Prague it was like 20 people in a 00:06:17.710 --> 00:06:19.320 align:start position:0% X in Prague it was like 20 people in a room<00:06:17.740> there<00:06:18.190> were<00:06:18.280> other<00:06:18.460> ad<00:06:18.700> hoc<00:06:18.940> meetings 00:06:19.320 --> 00:06:19.330 align:start position:0% room there were other ad hoc meetings 00:06:19.330 --> 00:06:20.940 align:start position:0% room there were other ad hoc meetings all<00:06:19.480> over<00:06:19.750> the<00:06:19.870> place<00:06:20.080> and<00:06:20.350> so<00:06:20.770> people 00:06:20.940 --> 00:06:20.950 align:start position:0% all over the place and so people 00:06:20.950 --> 00:06:23.880 align:start position:0% all over the place and so people interpreted<00:06:21.700> this<00:06:21.880> as<00:06:22.120> oh<00:06:22.750> these<00:06:23.530> people<00:06:23.740> are 00:06:23.880 --> 00:06:23.890 align:start position:0% interpreted this as oh these people are 00:06:23.890 --> 00:06:25.230 align:start position:0% interpreted this as oh these people are coming<00:06:24.040> together<00:06:24.310> to<00:06:24.640> figure<00:06:24.790> out<00:06:24.940> what's 00:06:25.230 --> 00:06:25.240 align:start position:0% coming together to figure out what's 00:06:25.240 --> 00:06:26.909 align:start position:0% coming together to figure out what's happening<00:06:25.300> to<00:06:25.780> aetherium<00:06:26.350> without<00:06:26.590> anyone 00:06:26.909 --> 00:06:26.919 align:start position:0% happening to aetherium without anyone 00:06:26.919 --> 00:06:28.950 align:start position:0% happening to aetherium without anyone else's<00:06:27.220> input<00:06:27.610> this<00:06:28.060> isn't<00:06:28.390> like<00:06:28.540> the<00:06:28.570> core 00:06:28.950 --> 00:06:28.960 align:start position:0% else's input this isn't like the core 00:06:28.960 --> 00:06:30.570 align:start position:0% else's input this isn't like the core developer<00:06:29.440> meetings<00:06:29.800> where<00:06:30.040> it's<00:06:30.190> all<00:06:30.310> open 00:06:30.570 --> 00:06:30.580 align:start position:0% developer meetings where it's all open 00:06:30.580 --> 00:06:33.630 align:start position:0% developer meetings where it's all open and<00:06:30.910> out<00:06:31.000> there<00:06:31.210> and<00:06:31.360> streaming<00:06:32.040> so<00:06:33.040> we<00:06:33.400> did<00:06:33.550> an 00:06:33.630 --> 00:06:33.640 align:start position:0% and out there and streaming so we did an 00:06:33.640 --> 00:06:36.870 align:start position:0% and out there and streaming so we did an experiment<00:06:34.770> because<00:06:35.770> of<00:06:35.919> the<00:06:36.039> 1x<00:06:36.400> initiative 00:06:36.870 --> 00:06:36.880 align:start position:0% experiment because of the 1x initiative 00:06:36.880 --> 00:06:39.120 align:start position:0% experiment because of the 1x initiative starting<00:06:37.390> we<00:06:37.960> wanted<00:06:38.229> developers<00:06:38.680> to<00:06:38.830> be<00:06:38.919> able 00:06:39.120 --> 00:06:39.130 align:start position:0% starting we wanted developers to be able 00:06:39.130 --> 00:06:40.020 align:start position:0% starting we wanted developers to be able to<00:06:39.190> speak<00:06:39.460> hand 00:06:40.020 --> 00:06:40.030 align:start position:0% to speak hand 00:06:40.030 --> 00:06:42.360 align:start position:0% to speak hand without<00:06:40.450> fear<00:06:40.750> of<00:06:40.810> media<00:06:41.160> misinterpretation 00:06:42.360 --> 00:06:42.370 align:start position:0% without fear of media misinterpretation 00:06:42.370 --> 00:06:44.760 align:start position:0% without fear of media misinterpretation sorry<00:06:42.880> Li<00:06:43.180> sorry<00:06:43.630> Kim<00:06:43.960> with<00:06:44.140> Coyne<00:06:44.350> desk<00:06:44.620> I 00:06:44.760 --> 00:06:44.770 align:start position:0% sorry Li sorry Kim with Coyne desk I 00:06:44.770 --> 00:06:46.260 align:start position:0% sorry Li sorry Kim with Coyne desk I know<00:06:44.890> you're<00:06:45.040> out<00:06:45.190> there 00:06:46.260 --> 00:06:46.270 align:start position:0% know you're out there 00:06:46.270 --> 00:06:48.420 align:start position:0% know you're out there but<00:06:46.600> yeah<00:06:46.780> without<00:06:46.990> fear<00:06:47.410> of<00:06:47.560> media<00:06:47.980> interpret 00:06:48.420 --> 00:06:48.430 align:start position:0% but yeah without fear of media interpret 00:06:48.430 --> 00:06:50.490 align:start position:0% but yeah without fear of media interpret interpretations<00:06:49.300> so<00:06:49.630> we<00:06:49.840> had<00:06:50.020> an<00:06:50.110> eighth<00:06:50.260> one 00:06:50.490 --> 00:06:50.500 align:start position:0% interpretations so we had an eighth one 00:06:50.500 --> 00:06:52.830 align:start position:0% interpretations so we had an eighth one x-coordinate<00:06:51.130> meeting<00:06:51.520> on<00:06:51.670> the<00:06:52.270> 30th<00:06:52.420> of<00:06:52.720> the 00:06:52.830 --> 00:06:52.840 align:start position:0% x-coordinate meeting on the 30th of the 00:06:52.840 --> 00:06:54.720 align:start position:0% x-coordinate meeting on the 30th of the November<00:06:53.290> of<00:06:53.410> last<00:06:53.440> year 00:06:54.720 --> 00:06:54.730 align:start position:0% November of last year 00:06:54.730 --> 00:06:57.120 align:start position:0% November of last year to<00:06:55.060> solidify<00:06:55.330> plans<00:06:55.900> for<00:06:56.230> workshops<00:06:56.740> and 00:06:57.120 --> 00:06:57.130 align:start position:0% to solidify plans for workshops and 00:06:57.130 --> 00:06:58.650 align:start position:0% to solidify plans for workshops and things<00:06:57.400> like<00:06:57.550> that<00:06:57.610> but<00:06:57.970> we<00:06:58.090> use<00:06:58.240> Chatham 00:06:58.650 --> 00:06:58.660 align:start position:0% things like that but we use Chatham 00:06:58.660 --> 00:07:00.680 align:start position:0% things like that but we use Chatham House<00:06:58.810> Rules<00:06:59.200> and<00:06:59.800> what<00:06:59.950> that<00:07:00.100> means<00:07:00.280> is 00:07:00.680 --> 00:07:00.690 align:start position:0% House Rules and what that means is 00:07:00.690 --> 00:07:03.180 align:start position:0% House Rules and what that means is everybody<00:07:01.690> attends<00:07:02.170> the<00:07:02.320> meeting<00:07:02.680> and<00:07:02.890> you 00:07:03.180 --> 00:07:03.190 align:start position:0% everybody attends the meeting and you 00:07:03.190 --> 00:07:05.190 align:start position:0% everybody attends the meeting and you take<00:07:03.430> notes<00:07:03.730> but<00:07:03.970> you<00:07:04.000> don't<00:07:04.270> attribute<00:07:04.720> those 00:07:05.190 --> 00:07:05.200 align:start position:0% take notes but you don't attribute those 00:07:05.200 --> 00:07:07.530 align:start position:0% take notes but you don't attribute those notes<00:07:05.500> to<00:07:05.680> anyone<00:07:06.070> in<00:07:06.160> particular<00:07:06.420> what<00:07:07.420> you 00:07:07.530 --> 00:07:07.540 align:start position:0% notes to anyone in particular what you 00:07:07.540 --> 00:07:09.480 align:start position:0% notes to anyone in particular what you do<00:07:07.750> is<00:07:07.930> you<00:07:08.110> just<00:07:08.140> write<00:07:08.620> the<00:07:08.650> notes<00:07:08.950> down<00:07:09.070> and 00:07:09.480 --> 00:07:09.490 align:start position:0% do is you just write the notes down and 00:07:09.490 --> 00:07:11.070 align:start position:0% do is you just write the notes down and no<00:07:09.670> one<00:07:09.820> everyone<00:07:10.180> can<00:07:10.450> talk<00:07:10.660> about<00:07:10.930> what 00:07:11.070 --> 00:07:11.080 align:start position:0% no one everyone can talk about what 00:07:11.080 --> 00:07:12.330 align:start position:0% no one everyone can talk about what happened<00:07:11.410> at<00:07:11.470> the<00:07:11.560> meeting<00:07:11.710> but<00:07:11.980> they<00:07:12.100> can't 00:07:12.330 --> 00:07:12.340 align:start position:0% happened at the meeting but they can't 00:07:12.340 --> 00:07:15.180 align:start position:0% happened at the meeting but they can't mention<00:07:12.580> names<00:07:13.020> so<00:07:14.020> we<00:07:14.320> decided<00:07:14.650> to<00:07:14.770> just<00:07:14.920> try 00:07:15.180 --> 00:07:15.190 align:start position:0% mention names so we decided to just try 00:07:15.190 --> 00:07:17.160 align:start position:0% mention names so we decided to just try that<00:07:15.370> we<00:07:15.580> didn't<00:07:15.850> record<00:07:16.210> or<00:07:16.480> stream<00:07:16.990> the 00:07:17.160 --> 00:07:17.170 align:start position:0% that we didn't record or stream the 00:07:17.170 --> 00:07:19.170 align:start position:0% that we didn't record or stream the meeting<00:07:17.530> and<00:07:17.680> the<00:07:18.310> community<00:07:18.730> pushed<00:07:18.940> back<00:07:19.150> on 00:07:19.170 --> 00:07:19.180 align:start position:0% meeting and the community pushed back on 00:07:19.180 --> 00:07:21.920 align:start position:0% meeting and the community pushed back on that<00:07:19.600> so<00:07:20.020> we<00:07:20.260> decided<00:07:20.590> to<00:07:20.770> not<00:07:20.920> do<00:07:21.100> that<00:07:21.220> again 00:07:21.920 --> 00:07:21.930 align:start position:0% that so we decided to not do that again 00:07:21.930 --> 00:07:25.050 align:start position:0% that so we decided to not do that again so<00:07:22.930> that's<00:07:23.140> kind<00:07:23.530> of<00:07:23.560> the<00:07:23.680> end<00:07:23.800> of<00:07:23.920> that<00:07:24.130> but<00:07:24.610> it 00:07:25.050 --> 00:07:25.060 align:start position:0% so that's kind of the end of that but it 00:07:25.060 --> 00:07:26.790 align:start position:0% so that's kind of the end of that but it was<00:07:25.210> really<00:07:25.480> interesting<00:07:25.780> to<00:07:26.020> me<00:07:26.200> and<00:07:26.350> I<00:07:26.410> put 00:07:26.790 --> 00:07:26.800 align:start position:0% was really interesting to me and I put 00:07:26.800 --> 00:07:28.580 align:start position:0% was really interesting to me and I put it<00:07:26.860> with<00:07:27.040> us<00:07:27.160> in<00:07:27.310> the<00:07:27.490> presentation<00:07:28.210> because 00:07:28.580 --> 00:07:28.590 align:start position:0% it with us in the presentation because 00:07:28.590 --> 00:07:31.710 align:start position:0% it with us in the presentation because this<00:07:29.590> kind<00:07:29.890> of<00:07:30.040> jump-started<00:07:30.940> a<00:07:31.150> lot<00:07:31.540> of 00:07:31.710 --> 00:07:31.720 align:start position:0% this kind of jump-started a lot of 00:07:31.720 --> 00:07:34.800 align:start position:0% this kind of jump-started a lot of enthusiasm<00:07:31.920> for<00:07:32.920> you<00:07:33.430> know<00:07:33.520> transparency<00:07:34.510> and 00:07:34.800 --> 00:07:34.810 align:start position:0% enthusiasm for you know transparency and 00:07:34.810 --> 00:07:36.540 align:start position:0% enthusiasm for you know transparency and really<00:07:35.050> showed<00:07:35.320> that<00:07:35.350> like<00:07:35.890> showed<00:07:36.220> us<00:07:36.370> what 00:07:36.540 --> 00:07:36.550 align:start position:0% really showed that like showed us what 00:07:36.550 --> 00:07:38.310 align:start position:0% really showed that like showed us what the<00:07:36.670> community<00:07:37.090> values<00:07:37.570> within<00:07:37.840> aetherium 00:07:38.310 --> 00:07:38.320 align:start position:0% the community values within aetherium 00:07:38.320 --> 00:07:41.690 align:start position:0% the community values within aetherium and<00:07:38.680> I<00:07:39.310> thought<00:07:39.520> that<00:07:39.700> was<00:07:39.820> really<00:07:40.000> important 00:07:41.690 --> 00:07:41.700 align:start position:0% and I thought that was really important 00:07:41.700 --> 00:07:45.120 align:start position:0% and I thought that was really important we<00:07:42.700> had<00:07:42.910> a<00:07:43.210> 1<00:07:43.450> X<00:07:43.630> meeting<00:07:43.990> at<00:07:44.110> Stanford<00:07:44.710> that 00:07:45.120 --> 00:07:45.130 align:start position:0% we had a 1 X meeting at Stanford that 00:07:45.130 --> 00:07:48.630 align:start position:0% we had a 1 X meeting at Stanford that was<00:07:45.310> streamed<00:07:46.030> and<00:07:46.180> recorded<00:07:46.680> in<00:07:47.680> January<00:07:48.280> and 00:07:48.630 --> 00:07:48.640 align:start position:0% was streamed and recorded in January and 00:07:48.640 --> 00:07:52.350 align:start position:0% was streamed and recorded in January and that<00:07:49.390> one<00:07:49.630> had<00:07:50.350> a<00:07:50.380> lot<00:07:50.590> to<00:07:50.620> do<00:07:50.860> with<00:07:51.090> Alexi<00:07:52.090> kind 00:07:52.350 --> 00:07:52.360 align:start position:0% that one had a lot to do with Alexi kind 00:07:52.360 --> 00:07:54.030 align:start position:0% that one had a lot to do with Alexi kind of<00:07:52.450> running<00:07:52.750> the<00:07:52.930> meetings<00:07:53.320> and<00:07:53.650> doing<00:07:53.980> a 00:07:54.030 --> 00:07:54.040 align:start position:0% of running the meetings and doing a 00:07:54.040 --> 00:07:55.350 align:start position:0% of running the meetings and doing a really<00:07:54.070> good<00:07:54.370> job<00:07:54.430> of<00:07:54.700> getting<00:07:54.880> us<00:07:55.150> all 00:07:55.350 --> 00:07:55.360 align:start position:0% really good job of getting us all 00:07:55.360 --> 00:07:58.050 align:start position:0% really good job of getting us all organized<00:07:55.930> and<00:07:56.490> talking<00:07:57.490> about<00:07:57.670> the<00:07:57.820> things 00:07:58.050 --> 00:07:58.060 align:start position:0% organized and talking about the things 00:07:58.060 --> 00:08:01.110 align:start position:0% organized and talking about the things we<00:07:58.240> needed<00:07:58.420> to<00:07:58.600> do<00:07:58.750> in<00:07:58.960> 1.0<00:07:59.590> to<00:08:00.120> achieve 00:08:01.110 --> 00:08:01.120 align:start position:0% we needed to do in 1.0 to achieve 00:08:01.120 --> 00:08:04.830 align:start position:0% we needed to do in 1.0 to achieve sustainability<00:08:01.840> and<00:08:02.290> on<00:08:02.530> chain<00:08:03.720> pruning<00:08:04.720> and 00:08:04.830 --> 00:08:04.840 align:start position:0% sustainability and on chain pruning and 00:08:04.840 --> 00:08:07.950 align:start position:0% sustainability and on chain pruning and stuff<00:08:05.050> like<00:08:05.170> that<00:08:05.910> Berlin<00:08:06.910> I<00:08:07.420> didn't<00:08:07.780> get<00:08:07.870> to 00:08:07.950 --> 00:08:07.960 align:start position:0% stuff like that Berlin I didn't get to 00:08:07.960 --> 00:08:09.930 align:start position:0% stuff like that Berlin I didn't get to go<00:08:08.050> to<00:08:08.110> that<00:08:08.290> one<00:08:08.500> it<00:08:08.770> sucked<00:08:09.220> because<00:08:09.550> I 00:08:09.930 --> 00:08:09.940 align:start position:0% go to that one it sucked because I 00:08:09.940 --> 00:08:11.850 align:start position:0% go to that one it sucked because I didn't<00:08:10.150> get<00:08:10.240> to<00:08:10.330> go<00:08:10.450> but<00:08:10.840> in<00:08:11.260> April<00:08:11.440> we<00:08:11.740> had 00:08:11.850 --> 00:08:11.860 align:start position:0% didn't get to go but in April we had 00:08:11.860 --> 00:08:14.130 align:start position:0% didn't get to go but in April we had another<00:08:12.130> meeting<00:08:12.370> that<00:08:12.970> was<00:08:13.540> also<00:08:13.840> streaming 00:08:14.130 --> 00:08:14.140 align:start position:0% another meeting that was also streaming 00:08:14.140 --> 00:08:15.630 align:start position:0% another meeting that was also streaming reported<00:08:14.620> you<00:08:14.680> can<00:08:14.830> find<00:08:15.040> all<00:08:15.280> this<00:08:15.430> on 00:08:15.630 --> 00:08:15.640 align:start position:0% reported you can find all this on 00:08:15.640 --> 00:08:17.190 align:start position:0% reported you can find all this on youtube<00:08:16.090> it's<00:08:16.360> hours<00:08:16.720> of<00:08:16.870> really<00:08:17.080> good 00:08:17.190 --> 00:08:17.200 align:start position:0% youtube it's hours of really good 00:08:17.200 --> 00:08:19.470 align:start position:0% youtube it's hours of really good content<00:08:17.440> on<00:08:17.950> one<00:08:18.280> point<00:08:18.550> oh<00:08:18.670> and<00:08:18.880> one<00:08:19.000> point<00:08:19.270> X 00:08:19.470 --> 00:08:19.480 align:start position:0% content on one point oh and one point X 00:08:19.480 --> 00:08:22.740 align:start position:0% content on one point oh and one point X and<00:08:19.980> a<00:08:20.980> lot<00:08:21.430> of<00:08:21.460> different<00:08:21.760> stuff<00:08:22.270> came<00:08:22.510> away 00:08:22.740 --> 00:08:22.750 align:start position:0% and a lot of different stuff came away 00:08:22.750 --> 00:08:24.740 align:start position:0% and a lot of different stuff came away from<00:08:22.810> that<00:08:22.990> including<00:08:23.530> more<00:08:23.710> working<00:08:24.100> groups 00:08:24.740 --> 00:08:24.750 align:start position:0% from that including more working groups 00:08:24.750 --> 00:08:27.540 align:start position:0% from that including more working groups we<00:08:25.750> had<00:08:25.960> EVM<00:08:26.410> evolution<00:08:27.070> which<00:08:27.520> is 00:08:27.540 --> 00:08:27.550 align:start position:0% we had EVM evolution which is 00:08:27.550 --> 00:08:29.670 align:start position:0% we had EVM evolution which is improvements<00:08:28.240> to<00:08:28.390> the<00:08:28.510> current<00:08:28.990> EVM<00:08:29.350> around 00:08:29.670 --> 00:08:29.680 align:start position:0% improvements to the current EVM around 00:08:29.680 --> 00:08:31.920 align:start position:0% improvements to the current EVM around speed<00:08:30.070> safety<00:08:30.370> and<00:08:30.640> and<00:08:30.730> operability<00:08:31.060> that 00:08:31.920 --> 00:08:31.930 align:start position:0% speed safety and and operability that 00:08:31.930 --> 00:08:33.960 align:start position:0% speed safety and and operability that ones<00:08:32.200> currently<00:08:32.740> not<00:08:32.950> doing<00:08:32.980> anything<00:08:33.580> right 00:08:33.960 --> 00:08:33.970 align:start position:0% ones currently not doing anything right 00:08:33.970 --> 00:08:36.750 align:start position:0% ones currently not doing anything right now<00:08:34.500> that<00:08:35.500> one<00:08:35.680> got<00:08:35.860> some<00:08:36.100> feedback<00:08:36.520> from 00:08:36.750 --> 00:08:36.760 align:start position:0% now that one got some feedback from 00:08:36.760 --> 00:08:38.220 align:start position:0% now that one got some feedback from different<00:08:36.910> developers<00:08:37.570> that<00:08:37.840> they<00:08:37.900> didn't 00:08:38.220 --> 00:08:38.230 align:start position:0% different developers that they didn't 00:08:38.230 --> 00:08:39.990 align:start position:0% different developers that they didn't really<00:08:38.350> want<00:08:38.440> it<00:08:38.650> to<00:08:38.710> be<00:08:38.890> put<00:08:39.100> in<00:08:39.250> so<00:08:39.880> that 00:08:39.990 --> 00:08:40.000 align:start position:0% really want it to be put in so that 00:08:40.000 --> 00:08:41.520 align:start position:0% really want it to be put in so that working<00:08:40.420> group<00:08:40.450> is<00:08:40.750> no<00:08:40.960> longer<00:08:41.260> in<00:08:41.440> existence 00:08:41.520 --> 00:08:41.530 align:start position:0% working group is no longer in existence 00:08:41.530 --> 00:08:44.220 align:start position:0% working group is no longer in existence as<00:08:42.040> far<00:08:42.070> as<00:08:42.370> I<00:08:42.490> know<00:08:42.550> there's<00:08:43.540> the<00:08:43.750> testing<00:08:44.110> and 00:08:44.220 --> 00:08:44.230 align:start position:0% as far as I know there's the testing and 00:08:44.230 --> 00:08:46.020 align:start position:0% as far as I know there's the testing and infrastructure<00:08:44.830> team<00:08:45.100> they're<00:08:45.580> kind<00:08:45.850> of<00:08:45.940> have 00:08:46.020 --> 00:08:46.030 align:start position:0% infrastructure team they're kind of have 00:08:46.030 --> 00:08:47.610 align:start position:0% infrastructure team they're kind of have a<00:08:46.060> working<00:08:46.480> group<00:08:46.630> where<00:08:47.020> there 00:08:47.610 --> 00:08:47.620 align:start position:0% a working group where there 00:08:47.620 --> 00:08:49.920 align:start position:0% a working group where there you<00:08:47.770> build<00:08:48.160> these<00:08:48.279> tools<00:08:48.640> these<00:08:49.150> cross<00:08:49.450> client 00:08:49.920 --> 00:08:49.930 align:start position:0% you build these tools these cross client 00:08:49.930 --> 00:08:51.840 align:start position:0% you build these tools these cross client testing<00:08:50.320> tools<00:08:50.589> and<00:08:50.950> other<00:08:51.339> things<00:08:51.700> for 00:08:51.840 --> 00:08:51.850 align:start position:0% testing tools and other things for 00:08:51.850 --> 00:08:53.460 align:start position:0% testing tools and other things for compatibility 00:08:53.460 --> 00:08:53.470 align:start position:0% compatibility 00:08:53.470 --> 00:08:55.950 align:start position:0% compatibility there's<00:08:53.770> the<00:08:53.920> finality<00:08:54.279> gadget<00:08:55.089> which<00:08:55.779> is 00:08:55.950 --> 00:08:55.960 align:start position:0% there's the finality gadget which is 00:08:55.960 --> 00:08:58.290 align:start position:0% there's the finality gadget which is using<00:08:56.260> the<00:08:56.350> 2.0<00:08:56.980> beacon<00:08:57.400> chain<00:08:57.700> to<00:08:57.910> finalize 00:08:58.290 --> 00:08:58.300 align:start position:0% using the 2.0 beacon chain to finalize 00:08:58.300 --> 00:09:00.510 align:start position:0% using the 2.0 beacon chain to finalize eath<00:08:58.570> 1.0<00:08:59.230> blocks<00:08:59.560> which<00:08:59.890> is<00:09:00.040> a<00:09:00.070> really<00:09:00.430> really 00:09:00.510 --> 00:09:00.520 align:start position:0% eath 1.0 blocks which is a really really 00:09:00.520 --> 00:09:02.940 align:start position:0% eath 1.0 blocks which is a really really cool<00:09:00.670> idea<00:09:00.990> that<00:09:01.990> one's<00:09:02.230> actually<00:09:02.380> about<00:09:02.800> to 00:09:02.940 --> 00:09:02.950 align:start position:0% cool idea that one's actually about to 00:09:02.950 --> 00:09:05.850 align:start position:0% cool idea that one's actually about to spin<00:09:03.220> up<00:09:03.339> a<00:09:03.430> lot<00:09:03.660> more<00:09:04.660> that's<00:09:05.260> gonna<00:09:05.380> be<00:09:05.620> a<00:09:05.650> lot 00:09:05.850 --> 00:09:05.860 align:start position:0% spin up a lot more that's gonna be a lot 00:09:05.860 --> 00:09:07.920 align:start position:0% spin up a lot more that's gonna be a lot more<00:09:06.010> news<00:09:06.279> from<00:09:06.550> that<00:09:06.580> coming<00:09:07.029> soon<00:09:07.270> from 00:09:07.920 --> 00:09:07.930 align:start position:0% more news from that coming soon from 00:09:07.930 --> 00:09:09.390 align:start position:0% more news from that coming soon from what<00:09:08.050> I've<00:09:08.170> heard 00:09:09.390 --> 00:09:09.400 align:start position:0% what I've heard 00:09:09.400 --> 00:09:12.930 align:start position:0% what I've heard eeew<00:09:09.900> 1559<00:09:10.900> the<00:09:11.080> fee<00:09:11.230> market<00:09:11.620> change<00:09:11.950> that<00:09:12.790> one 00:09:12.930 --> 00:09:12.940 align:start position:0% eeew 1559 the fee market change that one 00:09:12.940 --> 00:09:15.060 align:start position:0% eeew 1559 the fee market change that one if<00:09:13.089> you've<00:09:13.210> seen<00:09:13.450> Eric<00:09:13.960> Connor<00:09:14.230> Eco<00:09:14.830> gnar 00:09:15.060 --> 00:09:15.070 align:start position:0% if you've seen Eric Connor Eco gnar 00:09:15.070 --> 00:09:17.730 align:start position:0% if you've seen Eric Connor Eco gnar orbit<00:09:15.730> Alec<00:09:16.000> deuteron<00:09:16.450> talking<00:09:17.290> about<00:09:17.500> that 00:09:17.730 --> 00:09:17.740 align:start position:0% orbit Alec deuteron talking about that 00:09:17.740 --> 00:09:19.500 align:start position:0% orbit Alec deuteron talking about that that's<00:09:18.010> making<00:09:18.520> transaction<00:09:19.150> fees<00:09:19.300> more 00:09:19.500 --> 00:09:19.510 align:start position:0% that's making transaction fees more 00:09:19.510 --> 00:09:21.840 align:start position:0% that's making transaction fees more stable<00:09:20.020> and<00:09:20.140> predictable<00:09:20.470> by<00:09:21.339> splitting<00:09:21.730> the 00:09:21.840 --> 00:09:21.850 align:start position:0% stable and predictable by splitting the 00:09:21.850 --> 00:09:24.000 align:start position:0% stable and predictable by splitting the transaction<00:09:22.540> fee<00:09:22.779> into<00:09:23.170> two<00:09:23.380> different<00:09:23.800> types 00:09:24.000 --> 00:09:24.010 align:start position:0% transaction fee into two different types 00:09:24.010 --> 00:09:26.070 align:start position:0% transaction fee into two different types of<00:09:24.220> fees<00:09:24.400> one<00:09:24.760> of<00:09:24.850> them<00:09:24.940> is<00:09:25.060> burned<00:09:25.360> on<00:09:25.630> chain 00:09:26.070 --> 00:09:26.080 align:start position:0% of fees one of them is burned on chain 00:09:26.080 --> 00:09:30.829 align:start position:0% of fees one of them is burned on chain and<00:09:26.980> the<00:09:27.130> other<00:09:27.279> one<00:09:27.490> is<00:09:27.760> the<00:09:28.089> predictable<00:09:28.690> fee 00:09:30.829 --> 00:09:30.839 align:start position:0% and the other one is the predictable fee 00:09:30.839 --> 00:09:34.350 align:start position:0% and the other one is the predictable fee so<00:09:31.839> after<00:09:32.529> all<00:09:32.830> these<00:09:33.190> meetings<00:09:33.490> it's<00:09:34.029> been 00:09:34.350 --> 00:09:34.360 align:start position:0% so after all these meetings it's been 00:09:34.360 --> 00:09:36.960 align:start position:0% so after all these meetings it's been about<00:09:34.779> a<00:09:34.839> year<00:09:34.960> since<00:09:35.500> Prague<00:09:35.890> where<00:09:36.730> are<00:09:36.850> we 00:09:36.960 --> 00:09:36.970 align:start position:0% about a year since Prague where are we 00:09:36.970 --> 00:09:38.880 align:start position:0% about a year since Prague where are we at<00:09:37.120> with<00:09:37.360> sustainability<00:09:38.110> what<00:09:38.529> it<00:09:38.650> what<00:09:38.770> is 00:09:38.880 --> 00:09:38.890 align:start position:0% at with sustainability what it what is 00:09:38.890 --> 00:09:39.660 align:start position:0% at with sustainability what it what is it<00:09:39.010> now 00:09:39.660 --> 00:09:39.670 align:start position:0% it now 00:09:39.670 --> 00:09:42.120 align:start position:0% it now and<00:09:39.760> I'd<00:09:40.750> argue<00:09:40.810> that<00:09:41.200> it's<00:09:41.500> about<00:09:41.830> improving 00:09:42.120 --> 00:09:42.130 align:start position:0% and I'd argue that it's about improving 00:09:42.130 --> 00:09:44.550 align:start position:0% and I'd argue that it's about improving processes<00:09:42.790> and<00:09:43.029> making<00:09:43.330> protocol<00:09:43.810> changes<00:09:44.350> to 00:09:44.550 --> 00:09:44.560 align:start position:0% processes and making protocol changes to 00:09:44.560 --> 00:09:45.990 align:start position:0% processes and making protocol changes to ensure<00:09:44.710> the<00:09:45.010> sustainability<00:09:45.190> of<00:09:45.760> the 00:09:45.990 --> 00:09:46.000 align:start position:0% ensure the sustainability of the 00:09:46.000 --> 00:09:47.880 align:start position:0% ensure the sustainability of the etherium<00:09:46.420> 1.0<00:09:46.900> blockchain<00:09:47.440> and<00:09:47.560> what<00:09:47.650> I<00:09:47.680> mean 00:09:47.880 --> 00:09:47.890 align:start position:0% etherium 1.0 blockchain and what I mean 00:09:47.890 --> 00:09:51.320 align:start position:0% etherium 1.0 blockchain and what I mean by<00:09:47.950> that<00:09:48.100> is<00:09:48.460> unlike<00:09:49.420> the<00:09:49.570> version<00:09:49.930> 1 00:09:51.320 --> 00:09:51.330 align:start position:0% by that is unlike the version 1 00:09:51.330 --> 00:09:54.000 align:start position:0% by that is unlike the version 1 sustainability<00:09:52.330> where<00:09:52.990> it<00:09:53.290> was<00:09:53.380> just<00:09:53.410> about 00:09:54.000 --> 00:09:54.010 align:start position:0% sustainability where it was just about 00:09:54.010 --> 00:09:56.100 align:start position:0% sustainability where it was just about you<00:09:54.400> know<00:09:54.430> let's<00:09:55.209> keep<00:09:55.390> the<00:09:55.570> chain<00:09:55.779> alive 00:09:56.100 --> 00:09:56.110 align:start position:0% you know let's keep the chain alive 00:09:56.110 --> 00:10:00.630 align:start position:0% you know let's keep the chain alive let's<00:09:56.620> you<00:09:56.890> know<00:09:57.270> do<00:09:58.270> some<00:09:58.510> stuff<00:09:58.779> with<00:09:59.640> the 00:10:00.630 --> 00:10:00.640 align:start position:0% let's you know do some stuff with the 00:10:00.640 --> 00:10:03.000 align:start position:0% let's you know do some stuff with the reducing<00:10:01.270> state<00:10:01.510> bloat<00:10:01.900> and<00:10:02.260> rent<00:10:02.650> and<00:10:02.920> all 00:10:03.000 --> 00:10:03.010 align:start position:0% reducing state bloat and rent and all 00:10:03.010 --> 00:10:06.840 align:start position:0% reducing state bloat and rent and all this<00:10:03.130> other<00:10:03.310> stuff<00:10:03.720> now<00:10:04.720> we<00:10:05.709> are<00:10:06.190> looking<00:10:06.550> at 00:10:06.840 --> 00:10:06.850 align:start position:0% this other stuff now we are looking at 00:10:06.850 --> 00:10:08.910 align:start position:0% this other stuff now we are looking at improving<00:10:07.360> processes<00:10:07.930> making<00:10:08.320> protocol 00:10:08.910 --> 00:10:08.920 align:start position:0% improving processes making protocol 00:10:08.920 --> 00:10:10.650 align:start position:0% improving processes making protocol changes<00:10:09.339> making<00:10:09.520> things<00:10:09.820> more<00:10:09.970> energetic<00:10:10.420> and 00:10:10.650 --> 00:10:10.660 align:start position:0% changes making things more energetic and 00:10:10.660 --> 00:10:13.710 align:start position:0% changes making things more energetic and exciting<00:10:11.200> in<00:10:11.290> the<00:10:11.380> 1.0<00:10:11.920> chain<00:10:12.250> and<00:10:12.520> I've<00:10:13.450> been 00:10:13.710 --> 00:10:13.720 align:start position:0% exciting in the 1.0 chain and I've been 00:10:13.720 --> 00:10:15.180 align:start position:0% exciting in the 1.0 chain and I've been seeing<00:10:13.930> a<00:10:14.050> lot<00:10:14.140> more<00:10:14.200> participation<00:10:15.040> because 00:10:15.180 --> 00:10:15.190 align:start position:0% seeing a lot more participation because 00:10:15.190 --> 00:10:17.280 align:start position:0% seeing a lot more participation because of<00:10:15.430> that<00:10:15.550> I<00:10:15.790> think<00:10:15.820> that<00:10:16.360> people<00:10:16.839> are<00:10:17.020> getting 00:10:17.280 --> 00:10:17.290 align:start position:0% of that I think that people are getting 00:10:17.290 --> 00:10:18.750 align:start position:0% of that I think that people are getting really<00:10:17.529> excited<00:10:18.040> about<00:10:18.130> what<00:10:18.400> we<00:10:18.490> can<00:10:18.520> do 00:10:18.750 --> 00:10:18.760 align:start position:0% really excited about what we can do 00:10:18.760 --> 00:10:22.530 align:start position:0% really excited about what we can do today<00:10:18.970> on<00:10:19.300> aetherium<00:10:19.690> and<00:10:20.880> without<00:10:21.880> having<00:10:22.420> to 00:10:22.530 --> 00:10:22.540 align:start position:0% today on aetherium and without having to 00:10:22.540 --> 00:10:27.150 align:start position:0% today on aetherium and without having to exactly<00:10:23.080> know<00:10:23.230> what<00:10:23.380> the<00:10:23.500> future<00:10:23.800> brings<00:10:26.160> this 00:10:27.150 --> 00:10:27.160 align:start position:0% exactly know what the future brings this 00:10:27.160 --> 00:10:29.790 align:start position:0% exactly know what the future brings this is<00:10:27.339> an<00:10:27.430> example<00:10:28.000> of<00:10:28.240> the<00:10:28.570> current<00:10:28.720> AIP<00:10:29.140> process 00:10:29.790 --> 00:10:29.800 align:start position:0% is an example of the current AIP process 00:10:29.800 --> 00:10:31.800 align:start position:0% is an example of the current AIP process though<00:10:29.980> so<00:10:30.310> this<00:10:30.430> is<00:10:30.550> like<00:10:30.700> my<00:10:30.940> favorite<00:10:31.270> or 00:10:31.800 --> 00:10:31.810 align:start position:0% though so this is like my favorite or 00:10:31.810 --> 00:10:35.340 align:start position:0% though so this is like my favorite or one<00:10:32.380> of<00:10:32.470> my<00:10:32.529> favorite<00:10:34.080> improvements<00:10:35.080> right 00:10:35.340 --> 00:10:35.350 align:start position:0% one of my favorite improvements right 00:10:35.350 --> 00:10:38.100 align:start position:0% one of my favorite improvements right now<00:10:35.560> which<00:10:36.040> one<00:10:36.390> yeah<00:10:37.420> a<00:10:37.540> theory<00:10:37.839> in<00:10:37.900> the<00:10:37.959> IP 00:10:38.100 --> 00:10:38.110 align:start position:0% now which one yeah a theory in the IP 00:10:38.110 --> 00:10:40.079 align:start position:0% now which one yeah a theory in the IP process<00:10:38.680> so<00:10:38.860> I'm<00:10:39.040> an<00:10:39.190> e<00:10:39.279> IP<00:10:39.430> editor<00:10:39.880> I'm 00:10:40.079 --> 00:10:40.089 align:start position:0% process so I'm an e IP editor I'm 00:10:40.089 --> 00:10:43.920 align:start position:0% process so I'm an e IP editor I'm involved<00:10:40.360> in<00:10:40.600> that<00:10:40.779> and<00:10:41.820> right<00:10:42.820> now<00:10:43.029> it's<00:10:43.360> kind 00:10:43.920 --> 00:10:43.930 align:start position:0% involved in that and right now it's kind 00:10:43.930 --> 00:10:46.560 align:start position:0% involved in that and right now it's kind of<00:10:44.050> hard<00:10:44.290> to<00:10:44.380> jump<00:10:44.740> into<00:10:44.920> the<00:10:45.459> EIP<00:10:45.850> one<00:10:46.270> is<00:10:46.420> our 00:10:46.560 --> 00:10:46.570 align:start position:0% of hard to jump into the EIP one is our 00:10:46.570 --> 00:10:49.500 align:start position:0% of hard to jump into the EIP one is our technical<00:10:47.170> standard<00:10:47.709> for<00:10:48.339> how<00:10:48.910> to<00:10:48.970> submit<00:10:49.300> a 00:10:49.500 --> 00:10:49.510 align:start position:0% technical standard for how to submit a 00:10:49.510 --> 00:10:51.690 align:start position:0% technical standard for how to submit a change<00:10:49.720> to<00:10:50.290> the<00:10:50.410> etherion<00:10:50.830> protocol<00:10:51.339> or<00:10:51.670> a 00:10:51.690 --> 00:10:51.700 align:start position:0% change to the etherion protocol or a 00:10:51.700 --> 00:10:54.180 align:start position:0% change to the etherion protocol or a community<00:10:52.209> standard<00:10:52.720> and<00:10:52.870> it's<00:10:53.500> really<00:10:53.860> hard 00:10:54.180 --> 00:10:54.190 align:start position:0% community standard and it's really hard 00:10:54.190 --> 00:10:55.549 align:start position:0% community standard and it's really hard to 00:10:55.549 --> 00:10:55.559 align:start position:0% to 00:10:55.559 --> 00:10:57.659 align:start position:0% to Digest<00:10:56.559> right<00:10:56.829> now<00:10:56.979> it's<00:10:57.159> kind<00:10:57.399> of<00:10:57.459> long 00:10:57.659 --> 00:10:57.669 align:start position:0% Digest right now it's kind of long 00:10:57.669 --> 00:10:59.939 align:start position:0% Digest right now it's kind of long there's<00:10:58.509> all<00:10:58.689> these<00:10:58.809> different<00:10:58.869> IPS<00:10:59.589> you<00:10:59.769> have 00:10:59.939 --> 00:10:59.949 align:start position:0% there's all these different IPS you have 00:10:59.949 --> 00:11:01.739 align:start position:0% there's all these different IPS you have to<00:11:00.039> format<00:11:00.399> them<00:11:00.579> a<00:11:00.639> certain<00:11:00.969> way<00:11:01.149> and<00:11:01.419> we<00:11:01.629> want 00:11:01.739 --> 00:11:01.749 align:start position:0% to format them a certain way and we want 00:11:01.749 --> 00:11:04.369 align:start position:0% to format them a certain way and we want to<00:11:01.869> make<00:11:01.989> that<00:11:02.139> a<00:11:02.169> little<00:11:02.409> bit<00:11:02.529> easier<00:11:03.069> so 00:11:04.369 --> 00:11:04.379 align:start position:0% to make that a little bit easier so 00:11:04.379 --> 00:11:07.229 align:start position:0% to make that a little bit easier so right<00:11:05.379> now<00:11:05.619> we<00:11:06.069> have<00:11:06.239> work-in-progress 00:11:07.229 --> 00:11:07.239 align:start position:0% right now we have work-in-progress 00:11:07.239 --> 00:11:10.199 align:start position:0% right now we have work-in-progress draftee<00:11:07.989> IP<00:11:08.139> accepted<00:11:08.859> e<00:11:08.919> IP<00:11:09.099> main<00:11:09.969> mint 00:11:10.199 --> 00:11:10.209 align:start position:0% draftee IP accepted e IP main mint 00:11:10.209 --> 00:11:12.209 align:start position:0% draftee IP accepted e IP main mint client<00:11:10.569> implementation<00:11:11.229> network<00:11:11.649> update<00:11:12.039> and 00:11:12.209 --> 00:11:12.219 align:start position:0% client implementation network update and 00:11:12.219 --> 00:11:13.679 align:start position:0% client implementation network update and then<00:11:12.309> the<00:11:12.429> miners<00:11:12.789> mind<00:11:12.999> the<00:11:13.089> new<00:11:13.209> blocks<00:11:13.449> and 00:11:13.679 --> 00:11:13.689 align:start position:0% then the miners mind the new blocks and 00:11:13.689 --> 00:11:16.469 align:start position:0% then the miners mind the new blocks and then<00:11:13.779> we're<00:11:13.899> at<00:11:13.989> consensus<00:11:14.589> and<00:11:15.209> what<00:11:16.209> we<00:11:16.329> do 00:11:16.469 --> 00:11:16.479 align:start position:0% then we're at consensus and what we do 00:11:16.479 --> 00:11:17.999 align:start position:0% then we're at consensus and what we do is<00:11:16.629> we<00:11:16.749> take<00:11:16.959> these<00:11:17.199> e<00:11:17.229> IPS 00:11:17.999 --> 00:11:18.009 align:start position:0% is we take these e IPS 00:11:18.009 --> 00:11:20.009 align:start position:0% is we take these e IPS and<00:11:18.129> we<00:11:18.369> stuff<00:11:18.759> them<00:11:18.879> into<00:11:19.059> these<00:11:19.239> hard<00:11:19.569> Forks 00:11:20.009 --> 00:11:20.019 align:start position:0% and we stuff them into these hard Forks 00:11:20.019 --> 00:11:23.009 align:start position:0% and we stuff them into these hard Forks and<00:11:20.309> they're<00:11:21.309> on<00:11:21.549> a<00:11:21.609> certain<00:11:22.359> date<00:11:22.599> and<00:11:22.749> time 00:11:23.009 --> 00:11:23.019 align:start position:0% and they're on a certain date and time 00:11:23.019 --> 00:11:26.129 align:start position:0% and they're on a certain date and time and<00:11:23.849> we<00:11:24.849> do<00:11:24.939> that<00:11:25.089> my<00:11:25.179> block<00:11:25.419> number<00:11:25.839> and 00:11:26.129 --> 00:11:26.139 align:start position:0% and we do that my block number and 00:11:26.139 --> 00:11:28.469 align:start position:0% and we do that my block number and that's<00:11:26.889> not<00:11:27.279> really<00:11:27.609> efficient<00:11:28.089> because<00:11:28.359> it 00:11:28.469 --> 00:11:28.479 align:start position:0% that's not really efficient because it 00:11:28.479 --> 00:11:29.429 align:start position:0% that's not really efficient because it makes<00:11:28.659> us<00:11:28.809> rush 00:11:29.429 --> 00:11:29.439 align:start position:0% makes us rush 00:11:29.439 --> 00:11:31.919 align:start position:0% makes us rush we<00:11:29.529> don't<00:11:29.679> have<00:11:29.829> test<00:11:30.099> cases<00:11:30.219> up<00:11:30.699> yet<00:11:30.909> we<00:11:31.179> have 00:11:31.919 --> 00:11:31.929 align:start position:0% we don't have test cases up yet we have 00:11:31.929 --> 00:11:33.419 align:start position:0% we don't have test cases up yet we have to<00:11:32.079> pressure<00:11:32.319> everybody<00:11:32.799> to<00:11:32.979> work<00:11:33.159> really 00:11:33.419 --> 00:11:33.429 align:start position:0% to pressure everybody to work really 00:11:33.429 --> 00:11:35.759 align:start position:0% to pressure everybody to work really hard<00:11:33.519> and<00:11:33.909> really<00:11:33.999> fast<00:11:34.119> at<00:11:34.779> this<00:11:35.319> you<00:11:35.649> know 00:11:35.759 --> 00:11:35.769 align:start position:0% hard and really fast at this you know 00:11:35.769 --> 00:11:39.299 align:start position:0% hard and really fast at this you know normal<00:11:36.579> this<00:11:36.789> original<00:11:37.539> model<00:11:37.989> of<00:11:38.259> how<00:11:38.979> we<00:11:39.039> do 00:11:39.299 --> 00:11:39.309 align:start position:0% normal this original model of how we do 00:11:39.309 --> 00:11:42.659 align:start position:0% normal this original model of how we do things<00:11:39.549> today<00:11:40.079> instead<00:11:41.079> we<00:11:41.469> want<00:11:41.649> an<00:11:41.739> e<00:11:41.859> IP<00:11:42.009> VIP 00:11:42.659 --> 00:11:42.669 align:start position:0% things today instead we want an e IP VIP 00:11:42.669 --> 00:11:45.479 align:start position:0% things today instead we want an e IP VIP focused<00:11:43.419> network<00:11:43.839> upgrade<00:11:44.289> model<00:11:44.739> where<00:11:45.279> we 00:11:45.479 --> 00:11:45.489 align:start position:0% focused network upgrade model where we 00:11:45.489 --> 00:11:48.389 align:start position:0% focused network upgrade model where we have<00:11:45.729> our<00:11:46.119> draft<00:11:46.959> and<00:11:47.379> then<00:11:47.649> we<00:11:47.829> have<00:11:48.159> the<00:11:48.279> all 00:11:48.389 --> 00:11:48.399 align:start position:0% have our draft and then we have the all 00:11:48.399 --> 00:11:50.459 align:start position:0% have our draft and then we have the all core<00:11:48.669> devs<00:11:48.849> green<00:11:49.179> light<00:11:49.359> these<00:11:49.569> Cori<00:11:49.929> IPS 00:11:50.459 --> 00:11:50.469 align:start position:0% core devs green light these Cori IPS 00:11:50.469 --> 00:11:52.109 align:start position:0% core devs green light these Cori IPS from<00:11:51.189> there<00:11:51.429> we<00:11:51.639> get<00:11:51.789> into<00:11:52.029> the 00:11:52.109 --> 00:11:52.119 align:start position:0% from there we get into the 00:11:52.119 --> 00:11:55.079 align:start position:0% from there we get into the implementations<00:11:53.309> from<00:11:54.309> there<00:11:54.639> we<00:11:54.789> get<00:11:54.909> into 00:11:55.079 --> 00:11:55.089 align:start position:0% implementations from there we get into 00:11:55.089 --> 00:11:56.909 align:start position:0% implementations from there we get into testing<00:11:55.569> and<00:11:55.779> then<00:11:55.899> it's<00:11:56.049> only<00:11:56.259> accepted 00:11:56.909 --> 00:11:56.919 align:start position:0% testing and then it's only accepted 00:11:56.919 --> 00:11:58.199 align:start position:0% testing and then it's only accepted after<00:11:57.069> the<00:11:57.309> test<00:11:57.579> cases<00:11:57.879> and<00:11:58.119> the 00:11:58.199 --> 00:11:58.209 align:start position:0% after the test cases and the 00:11:58.209 --> 00:12:00.569 align:start position:0% after the test cases and the implementations<00:11:59.049> are<00:11:59.289> finished<00:12:00.219> or<00:12:00.399> near 00:12:00.569 --> 00:12:00.579 align:start position:0% implementations are finished or near 00:12:00.579 --> 00:12:02.939 align:start position:0% implementations are finished or near finished<00:12:00.999> and<00:12:01.299> what<00:12:02.109> that's<00:12:02.259> gonna<00:12:02.409> help<00:12:02.679> is 00:12:02.939 --> 00:12:02.949 align:start position:0% finished and what that's gonna help is 00:12:02.949 --> 00:12:05.009 align:start position:0% finished and what that's gonna help is instead<00:12:03.399> of<00:12:03.459> us<00:12:03.639> deciding<00:12:04.149> early<00:12:04.539> on<00:12:04.689> like 00:12:05.009 --> 00:12:05.019 align:start position:0% instead of us deciding early on like 00:12:05.019 --> 00:12:08.819 align:start position:0% instead of us deciding early on like okay<00:12:05.379> we're<00:12:05.529> gonna<00:12:05.619> put<00:12:05.889> the<00:12:06.369> IP<00:12:06.639> 1<00:12:07.599> 2<00:12:07.869> &<00:12:08.049> 3<00:12:08.079> into 00:12:08.819 --> 00:12:08.829 align:start position:0% okay we're gonna put the IP 1 2 & 3 into 00:12:08.829 --> 00:12:10.409 align:start position:0% okay we're gonna put the IP 1 2 & 3 into this<00:12:08.949> hard<00:12:09.249> fork<00:12:09.549> on<00:12:09.669> this<00:12:09.849> date<00:12:10.119> so<00:12:10.329> we're 00:12:10.409 --> 00:12:10.419 align:start position:0% this hard fork on this date so we're 00:12:10.419 --> 00:12:11.579 align:start position:0% this hard fork on this date so we're gonna<00:12:10.539> have<00:12:10.719> to<00:12:10.839> rush<00:12:11.049> to<00:12:11.079> the<00:12:11.289> finish<00:12:11.559> line 00:12:11.579 --> 00:12:11.589 align:start position:0% gonna have to rush to the finish line 00:12:11.589 --> 00:12:14.159 align:start position:0% gonna have to rush to the finish line now<00:12:12.549> we<00:12:12.609> just<00:12:12.999> do<00:12:13.149> a<00:12:13.179> hard<00:12:13.449> fork<00:12:13.719> when<00:12:13.839> the<00:12:13.899> EIP 00:12:14.159 --> 00:12:14.169 align:start position:0% now we just do a hard fork when the EIP 00:12:14.169 --> 00:12:16.469 align:start position:0% now we just do a hard fork when the EIP is<00:12:14.379> done<00:12:14.679> and<00:12:14.979> if<00:12:15.639> there<00:12:15.789> happens<00:12:16.119> to<00:12:16.239> be<00:12:16.329> more 00:12:16.469 --> 00:12:16.479 align:start position:0% is done and if there happens to be more 00:12:16.479 --> 00:12:18.419 align:start position:0% is done and if there happens to be more than<00:12:16.539> one<00:12:16.779> AIP<00:12:17.079> done<00:12:17.439> at<00:12:17.559> the<00:12:17.649> same<00:12:17.829> time<00:12:18.129> or 00:12:18.419 --> 00:12:18.429 align:start position:0% than one AIP done at the same time or 00:12:18.429 --> 00:12:19.739 align:start position:0% than one AIP done at the same time or there's<00:12:18.579> like<00:12:18.759> really<00:12:19.059> ones<00:12:19.359> that<00:12:19.509> are<00:12:19.599> really 00:12:19.739 --> 00:12:19.749 align:start position:0% there's like really ones that are really 00:12:19.749 --> 00:12:22.439 align:start position:0% there's like really ones that are really close<00:12:20.049> together<00:12:20.259> that's<00:12:21.069> great 00:12:22.439 --> 00:12:22.449 align:start position:0% close together that's great 00:12:22.449 --> 00:12:24.359 align:start position:0% close together that's great some<00:12:22.809> of<00:12:22.899> the<00:12:22.959> challenges<00:12:23.229> behind<00:12:23.949> this<00:12:24.099> are 00:12:24.359 --> 00:12:24.369 align:start position:0% some of the challenges behind this are 00:12:24.369 --> 00:12:27.119 align:start position:0% some of the challenges behind this are gonna<00:12:24.489> be<00:12:24.699> letting<00:12:25.419> clients<00:12:26.409> exchanges 00:12:27.119 --> 00:12:27.129 align:start position:0% gonna be letting clients exchanges 00:12:27.129 --> 00:12:29.249 align:start position:0% gonna be letting clients exchanges people<00:12:27.579> like<00:12:27.819> infrastructure<00:12:28.689> projects<00:12:29.229> like 00:12:29.249 --> 00:12:29.259 align:start position:0% people like infrastructure projects like 00:12:29.259 --> 00:12:33.179 align:start position:0% people like infrastructure projects like in<00:12:29.499> fira<00:12:29.889> and<00:12:30.309> cloud<00:12:30.849> pod<00:12:31.719> front<00:12:32.019> know<00:12:32.289> when 00:12:33.179 --> 00:12:33.189 align:start position:0% in fira and cloud pod front know when 00:12:33.189 --> 00:12:34.679 align:start position:0% in fira and cloud pod front know when these<00:12:33.369> hard<00:12:33.609> Forks<00:12:33.879> are<00:12:33.999> happening<00:12:34.419> so<00:12:34.569> we're 00:12:34.679 --> 00:12:34.689 align:start position:0% these hard Forks are happening so we're 00:12:34.689 --> 00:12:36.449 align:start position:0% these hard Forks are happening so we're gonna<00:12:34.779> have<00:12:35.019> to<00:12:35.169> bump<00:12:35.319> up<00:12:35.529> our<00:12:35.679> communications 00:12:36.449 --> 00:12:36.459 align:start position:0% gonna have to bump up our communications 00:12:36.459 --> 00:12:39.479 align:start position:0% gonna have to bump up our communications we're<00:12:36.639> gonna<00:12:36.729> have<00:12:36.939> to<00:12:37.089> ramp<00:12:37.869> up<00:12:38.079> and<00:12:38.979> assign 00:12:39.479 --> 00:12:39.489 align:start position:0% we're gonna have to ramp up and assign 00:12:39.489 --> 00:12:42.539 align:start position:0% we're gonna have to ramp up and assign people<00:12:39.789> to<00:12:40.269> know<00:12:41.039> when<00:12:42.039> these<00:12:42.159> things<00:12:42.219> are 00:12:42.539 --> 00:12:42.549 align:start position:0% people to know when these things are 00:12:42.549 --> 00:12:44.699 align:start position:0% people to know when these things are happening<00:12:43.029> and<00:12:43.179> that's<00:12:43.779> actually<00:12:44.079> a<00:12:44.259> job<00:12:44.499> that 00:12:44.699 --> 00:12:44.709 align:start position:0% happening and that's actually a job that 00:12:44.709 --> 00:12:46.589 align:start position:0% happening and that's actually a job that the<00:12:44.799> etherium<00:12:45.219> cat<00:12:45.459> herders<00:12:45.939> which<00:12:46.149> I'm<00:12:46.449> also 00:12:46.589 --> 00:12:46.599 align:start position:0% the etherium cat herders which I'm also 00:12:46.599 --> 00:12:49.019 align:start position:0% the etherium cat herders which I'm also a<00:12:46.749> part<00:12:47.049> of<00:12:47.229> is<00:12:48.039> going<00:12:48.279> to<00:12:48.339> hopefully<00:12:48.609> have<00:12:48.999> a 00:12:49.019 --> 00:12:49.029 align:start position:0% a part of is going to hopefully have a 00:12:49.029 --> 00:12:54.629 align:start position:0% a part of is going to hopefully have a really<00:12:49.419> big<00:12:49.899> job<00:12:50.199> in<00:12:50.349> accomplishing<00:12:53.639> here's 00:12:54.629 --> 00:12:54.639 align:start position:0% really big job in accomplishing here's 00:12:54.639 --> 00:12:56.759 align:start position:0% really big job in accomplishing here's another<00:12:54.939> really<00:12:55.179> cool<00:12:55.569> change<00:12:56.109> this<00:12:56.409> one<00:12:56.619> is<00:12:56.739> a 00:12:56.759 --> 00:12:56.769 align:start position:0% another really cool change this one is a 00:12:56.769 --> 00:13:01.229 align:start position:0% another really cool change this one is a graph<00:12:57.189> from<00:12:57.219> Alexia<00:12:57.849> Kuna<00:12:58.239> and<00:12:59.609> this<00:13:00.609> is<00:13:00.819> how 00:13:01.229 --> 00:13:01.239 align:start position:0% graph from Alexia Kuna and this is how 00:13:01.239 --> 00:13:02.660 align:start position:0% graph from Alexia Kuna and this is how whoops 00:13:02.660 --> 00:13:02.670 align:start position:0% whoops 00:13:02.670 --> 00:13:05.990 align:start position:0% whoops this<00:13:02.880> is<00:13:03.090> how<00:13:04.100> things<00:13:05.100> want<00:13:05.460> to<00:13:05.610> work<00:13:05.760> in<00:13:05.910> the 00:13:05.990 --> 00:13:06.000 align:start position:0% this is how things want to work in the 00:13:06.000 --> 00:13:06.590 align:start position:0% this is how things want to work in the future 00:13:06.590 --> 00:13:06.600 align:start position:0% future 00:13:06.600 --> 00:13:08.990 align:start position:0% future metallic<00:13:07.530> or<00:13:07.740> people<00:13:08.160> on<00:13:08.280> the<00:13:08.430> internet<00:13:08.760> or 00:13:08.990 --> 00:13:09.000 align:start position:0% metallic or people on the internet or 00:13:09.000 --> 00:13:11.570 align:start position:0% metallic or people on the internet or other<00:13:09.060> core<00:13:09.600> developers<00:13:10.140> have<00:13:10.800> an<00:13:10.920> idea<00:13:11.280> and 00:13:11.570 --> 00:13:11.580 align:start position:0% other core developers have an idea and 00:13:11.580 --> 00:13:13.310 align:start position:0% other core developers have an idea and they're<00:13:11.940> smiling<00:13:12.270> and<00:13:12.570> they<00:13:12.690> like<00:13:12.900> I<00:13:13.080> really 00:13:13.310 --> 00:13:13.320 align:start position:0% they're smiling and they like I really 00:13:13.320 --> 00:13:16.610 align:start position:0% they're smiling and they like I really like<00:13:13.530> this<00:13:13.710> idea<00:13:13.920> so<00:13:14.430> they're<00:13:15.270> going<00:13:15.510> to<00:13:15.750> put 00:13:16.610 --> 00:13:16.620 align:start position:0% like this idea so they're going to put 00:13:16.620 --> 00:13:18.200 align:start position:0% like this idea so they're going to put an<00:13:16.710> improvement<00:13:17.070> proposal<00:13:17.640> out<00:13:17.790> there<00:13:17.820> maybe 00:13:18.200 --> 00:13:18.210 align:start position:0% an improvement proposal out there maybe 00:13:18.210 --> 00:13:20.030 align:start position:0% an improvement proposal out there maybe on<00:13:18.420> a<00:13:18.450> theory<00:13:18.780> of<00:13:18.930> magicians<00:13:19.380> form<00:13:19.710> but<00:13:19.920> it's 00:13:20.030 --> 00:13:20.040 align:start position:0% on a theory of magicians form but it's 00:13:20.040 --> 00:13:22.730 align:start position:0% on a theory of magicians form but it's not<00:13:20.220> formal<00:13:20.580> yet<00:13:20.910> then<00:13:21.840> there's<00:13:22.170> a<00:13:22.230> working 00:13:22.730 --> 00:13:22.740 align:start position:0% not formal yet then there's a working 00:13:22.740 --> 00:13:25.040 align:start position:0% not formal yet then there's a working group<00:13:22.890> formed<00:13:23.640> around<00:13:23.880> each<00:13:24.030> proposal<00:13:24.570> and 00:13:25.040 --> 00:13:25.050 align:start position:0% group formed around each proposal and 00:13:25.050 --> 00:13:27.230 align:start position:0% group formed around each proposal and research<00:13:25.380> project<00:13:26.010> and<00:13:26.250> then<00:13:26.820> others<00:13:27.120> can 00:13:27.230 --> 00:13:27.240 align:start position:0% research project and then others can 00:13:27.240 --> 00:13:29.390 align:start position:0% research project and then others can optionally<00:13:27.990> participate<00:13:28.920> there<00:13:29.220> can<00:13:29.370> be 00:13:29.390 --> 00:13:29.400 align:start position:0% optionally participate there can be 00:13:29.400 --> 00:13:30.740 align:start position:0% optionally participate there can be client<00:13:29.850> implementations<00:13:30.540> other 00:13:30.740 --> 00:13:30.750 align:start position:0% client implementations other 00:13:30.750 --> 00:13:33.440 align:start position:0% client implementations other improvements<00:13:31.530> but<00:13:32.340> it's<00:13:32.610> not<00:13:32.850> like<00:13:33.180> we're 00:13:33.440 --> 00:13:33.450 align:start position:0% improvements but it's not like we're 00:13:33.450 --> 00:13:35.870 align:start position:0% improvements but it's not like we're having<00:13:34.050> every<00:13:34.710> core<00:13:35.100> developer<00:13:35.580> look<00:13:35.760> at 00:13:35.870 --> 00:13:35.880 align:start position:0% having every core developer look at 00:13:35.880 --> 00:13:36.890 align:start position:0% having every core developer look at every<00:13:36.270> EIP 00:13:36.890 --> 00:13:36.900 align:start position:0% every EIP 00:13:36.900 --> 00:13:38.690 align:start position:0% every EIP we<00:13:37.410> have<00:13:37.530> these<00:13:37.680> working<00:13:38.130> groups<00:13:38.160> of<00:13:38.520> people 00:13:38.690 --> 00:13:38.700 align:start position:0% we have these working groups of people 00:13:38.700 --> 00:13:40.100 align:start position:0% we have these working groups of people who<00:13:38.940> are<00:13:39.030> interested<00:13:39.330> and<00:13:39.750> they<00:13:39.900> present 00:13:40.100 --> 00:13:40.110 align:start position:0% who are interested and they present 00:13:40.110 --> 00:13:42.620 align:start position:0% who are interested and they present their<00:13:40.440> case<00:13:40.650> and<00:13:40.950> they<00:13:41.070> do<00:13:41.130> the<00:13:41.910> research<00:13:42.420> and 00:13:42.620 --> 00:13:42.630 align:start position:0% their case and they do the research and 00:13:42.630 --> 00:13:46.340 align:start position:0% their case and they do the research and the<00:13:42.690> simulations<00:13:43.440> and<00:13:43.740> the<00:13:44.120> testing<00:13:45.350> cases 00:13:46.340 --> 00:13:46.350 align:start position:0% the simulations and the testing cases 00:13:46.350 --> 00:13:48.920 align:start position:0% the simulations and the testing cases and<00:13:46.650> the<00:13:47.420> implementations<00:13:48.420> and<00:13:48.630> work<00:13:48.750> with 00:13:48.920 --> 00:13:48.930 align:start position:0% and the implementations and work with 00:13:48.930 --> 00:13:52.010 align:start position:0% and the implementations and work with the<00:13:49.020> team<00:13:49.050> and<00:13:49.760> this<00:13:50.760> is<00:13:50.910> a<00:13:50.940> lot<00:13:51.240> better<00:13:51.630> than 00:13:52.010 --> 00:13:52.020 align:start position:0% the team and this is a lot better than 00:13:52.020 --> 00:13:54.770 align:start position:0% the team and this is a lot better than how<00:13:52.620> we've<00:13:52.800> had<00:13:52.950> it<00:13:53.070> before<00:13:53.100> where<00:13:53.790> the<00:13:54.600> core 00:13:54.770 --> 00:13:54.780 align:start position:0% how we've had it before where the core 00:13:54.780 --> 00:13:57.290 align:start position:0% how we've had it before where the core devs<00:13:54.990> have<00:13:55.140> to<00:13:55.260> look<00:13:55.380> at<00:13:55.500> every<00:13:55.770> IP<00:13:56.070> I<00:13:56.490> want<00:13:57.240> to 00:13:57.290 --> 00:13:57.300 align:start position:0% devs have to look at every IP I want to 00:13:57.300 --> 00:13:59.180 align:start position:0% devs have to look at every IP I want to make<00:13:57.420> a<00:13:57.450> note<00:13:57.660> here<00:13:57.990> that<00:13:58.020> these<00:13:58.710> improvements 00:13:59.180 --> 00:13:59.190 align:start position:0% make a note here that these improvements 00:13:59.190 --> 00:14:00.740 align:start position:0% make a note here that these improvements that<00:13:59.430> I'm<00:13:59.550> talking<00:13:59.940> about<00:14:00.150> aren't<00:14:00.450> done<00:14:00.720> yet 00:14:00.740 --> 00:14:00.750 align:start position:0% that I'm talking about aren't done yet 00:14:00.750 --> 00:14:02.870 align:start position:0% that I'm talking about aren't done yet it's<00:14:01.140> a<00:14:01.230> work<00:14:01.410> in<00:14:01.560> progress<00:14:01.830> and<00:14:02.310> we<00:14:02.370> aren't 00:14:02.870 --> 00:14:02.880 align:start position:0% it's a work in progress and we aren't 00:14:02.880 --> 00:14:05.060 align:start position:0% it's a work in progress and we aren't even<00:14:03.000> at<00:14:03.180> consensus<00:14:03.840> as<00:14:03.990> this<00:14:04.320> that<00:14:04.740> this<00:14:04.920> is 00:14:05.060 --> 00:14:05.070 align:start position:0% even at consensus as this that this is 00:14:05.070 --> 00:14:07.520 align:start position:0% even at consensus as this that this is how<00:14:05.190> it's<00:14:05.370> going<00:14:05.460> to<00:14:05.550> be<00:14:05.780> we<00:14:06.780> kind<00:14:07.110> of<00:14:07.200> have<00:14:07.470> to 00:14:07.520 --> 00:14:07.530 align:start position:0% how it's going to be we kind of have to 00:14:07.530 --> 00:14:09.200 align:start position:0% how it's going to be we kind of have to come<00:14:07.770> to<00:14:07.860> rough<00:14:08.040> consensus<00:14:08.580> about<00:14:08.700> this<00:14:09.030> but 00:14:09.200 --> 00:14:09.210 align:start position:0% come to rough consensus about this but 00:14:09.210 --> 00:14:10.550 align:start position:0% come to rough consensus about this but this<00:14:09.300> is<00:14:09.450> definitely<00:14:09.720> what<00:14:09.930> I'll<00:14:10.050> be<00:14:10.200> pushing 00:14:10.550 --> 00:14:10.560 align:start position:0% this is definitely what I'll be pushing 00:14:10.560 --> 00:14:13.880 align:start position:0% this is definitely what I'll be pushing for<00:14:10.830> as<00:14:11.820> we<00:14:12.180> go<00:14:12.390> forward<00:14:12.750> into<00:14:13.020> this<00:14:13.260> new<00:14:13.590> era 00:14:13.880 --> 00:14:13.890 align:start position:0% for as we go forward into this new era 00:14:13.890 --> 00:14:17.600 align:start position:0% for as we go forward into this new era of<00:14:14.070> eath<00:14:14.340> 1x<00:14:15.800> so<00:14:16.800> how<00:14:16.950> is<00:14:17.010> this<00:14:17.160> all<00:14:17.340> gonna<00:14:17.430> get 00:14:17.600 --> 00:14:17.610 align:start position:0% of eath 1x so how is this all gonna get 00:14:17.610 --> 00:14:19.100 align:start position:0% of eath 1x so how is this all gonna get funded<00:14:18.090> we<00:14:18.270> all<00:14:18.390> know<00:14:18.570> that<00:14:18.840> there's<00:14:18.990> all 00:14:19.100 --> 00:14:19.110 align:start position:0% funded we all know that there's all 00:14:19.110 --> 00:14:22.520 align:start position:0% funded we all know that there's all these<00:14:19.230> grant<00:14:19.560> programs<00:14:19.650> out<00:14:20.310> there<00:14:20.520> for<00:14:20.550> e<00:14:21.530> 2.0 00:14:22.520 --> 00:14:22.530 align:start position:0% these grant programs out there for e 2.0 00:14:22.530 --> 00:14:25.340 align:start position:0% these grant programs out there for e 2.0 and<00:14:22.920> different<00:14:23.310> tooling<00:14:23.700> projects<00:14:24.360> the 00:14:25.340 --> 00:14:25.350 align:start position:0% and different tooling projects the 00:14:25.350 --> 00:14:27.470 align:start position:0% and different tooling projects the etherium<00:14:25.770> foundation<00:14:26.370> earmarked<00:14:26.910> 8<00:14:27.060> million 00:14:27.470 --> 00:14:27.480 align:start position:0% etherium foundation earmarked 8 million 00:14:27.480 --> 00:14:30.140 align:start position:0% etherium foundation earmarked 8 million dollars<00:14:27.900> back<00:14:28.170> in<00:14:28.380> May<00:14:28.650> for<00:14:29.550> the<00:14:29.610> next<00:14:29.850> year<00:14:30.060> of 00:14:30.140 --> 00:14:30.150 align:start position:0% dollars back in May for the next year of 00:14:30.150 --> 00:14:32.990 align:start position:0% dollars back in May for the next year of eath<00:14:30.330> 1.0<00:14:30.960> and<00:14:31.110> one<00:14:31.260> point<00:14:31.590> X<00:14:31.800> research<00:14:32.790> that 00:14:32.990 --> 00:14:33.000 align:start position:0% eath 1.0 and one point X research that 00:14:33.000 --> 00:14:36.320 align:start position:0% eath 1.0 and one point X research that was<00:14:33.120> announced<00:14:33.480> at<00:14:33.660> ether<00:14:34.050> real<00:14:34.200> and<00:14:35.330> we're 00:14:36.320 --> 00:14:36.330 align:start position:0% was announced at ether real and we're 00:14:36.330 --> 00:14:38.510 align:start position:0% was announced at ether real and we're working<00:14:36.660> to<00:14:36.750> bring<00:14:36.930> full-time<00:14:37.500> eath<00:14:37.800> 1x<00:14:38.220> teams 00:14:38.510 --> 00:14:38.520 align:start position:0% working to bring full-time eath 1x teams 00:14:38.520 --> 00:14:40.460 align:start position:0% working to bring full-time eath 1x teams and<00:14:38.730> coordinators<00:14:39.270> together<00:14:39.630> that's<00:14:39.930> also<00:14:40.440> a 00:14:40.460 --> 00:14:40.470 align:start position:0% and coordinators together that's also a 00:14:40.470 --> 00:14:41.870 align:start position:0% and coordinators together that's also a work<00:14:40.680> in<00:14:40.830> progress<00:14:41.040> that<00:14:41.250> you'll<00:14:41.460> be<00:14:41.580> hearing 00:14:41.870 --> 00:14:41.880 align:start position:0% work in progress that you'll be hearing 00:14:41.880 --> 00:14:44.150 align:start position:0% work in progress that you'll be hearing more<00:14:42.030> about<00:14:42.090> in<00:14:42.420> 2020 00:14:44.150 --> 00:14:44.160 align:start position:0% more about in 2020 00:14:44.160 --> 00:14:47.120 align:start position:0% more about in 2020 so<00:14:44.730> yay<00:14:45.060> we<00:14:45.300> got<00:14:45.420> funding<00:14:45.960> we<00:14:46.380> have<00:14:46.500> excitement 00:14:47.120 --> 00:14:47.130 align:start position:0% so yay we got funding we have excitement 00:14:47.130 --> 00:14:49.310 align:start position:0% so yay we got funding we have excitement we<00:14:47.280> have<00:14:47.400> everything<00:14:47.760> we<00:14:48.120> need<00:14:48.150> to<00:14:48.990> really 00:14:49.310 --> 00:14:49.320 align:start position:0% we have everything we need to really 00:14:49.320 --> 00:14:51.890 align:start position:0% we have everything we need to really bring<00:14:49.620> the<00:14:49.950> eath<00:14:50.070> 1.0<00:14:50.640> chain<00:14:50.970> into<00:14:51.480> its<00:14:51.630> next 00:14:51.890 --> 00:14:51.900 align:start position:0% bring the eath 1.0 chain into its next 00:14:51.900 --> 00:14:56.500 align:start position:0% bring the eath 1.0 chain into its next evolution<00:14:52.590> before<00:14:52.890> we<00:14:53.010> hit<00:14:53.130> 2.0 00:14:56.500 --> 00:14:56.510 align:start position:0% 00:14:56.510 --> 00:15:00.110 align:start position:0% [Music] 00:15:00.110 --> 00:15:00.120 align:start position:0% [Music] 00:15:00.120 --> 00:15:03.570 align:start position:0% so<00:15:01.120> if<00:15:01.240> you<00:15:01.330> want<00:15:01.540> to<00:15:01.600> know<00:15:01.720> more<00:15:02.580> google 00:15:03.570 --> 00:15:03.580 align:start position:0% so if you want to know more google 00:15:03.580 --> 00:15:06.150 align:start position:0% so if you want to know more google Alexia<00:15:04.210> two<00:15:04.420> knobs<00:15:04.600> medium<00:15:05.140> his<00:15:05.560> blog<00:15:05.860> has<00:15:06.130> a 00:15:06.150 --> 00:15:06.160 align:start position:0% Alexia two knobs medium his blog has a 00:15:06.160 --> 00:15:08.400 align:start position:0% Alexia two knobs medium his blog has a ton<00:15:06.460> of<00:15:06.490> good<00:15:06.670> post<00:15:06.940> on<00:15:07.180> that<00:15:07.420> there's<00:15:08.230> an 00:15:08.400 --> 00:15:08.410 align:start position:0% ton of good post on that there's an 00:15:08.410 --> 00:15:11.750 align:start position:0% ton of good post on that there's an aetherium<00:15:08.860> wiki<00:15:09.190> page<00:15:09.630> that<00:15:10.630> has<00:15:10.840> the<00:15:10.870> eath<00:15:11.230> 1x 00:15:11.750 --> 00:15:11.760 align:start position:0% aetherium wiki page that has the eath 1x 00:15:11.760 --> 00:15:14.970 align:start position:0% aetherium wiki page that has the eath 1x history<00:15:12.760> on<00:15:12.910> it<00:15:13.060> it<00:15:13.180> talks<00:15:13.420> about<00:15:13.630> the<00:15:14.230> Berlin 00:15:14.970 --> 00:15:14.980 align:start position:0% history on it it talks about the Berlin 00:15:14.980 --> 00:15:17.160 align:start position:0% history on it it talks about the Berlin meeting<00:15:15.460> and<00:15:15.700> the<00:15:16.000> Stanford<00:15:16.300> meeting<00:15:16.930> and<00:15:17.080> it 00:15:17.160 --> 00:15:17.170 align:start position:0% meeting and the Stanford meeting and it 00:15:17.170 --> 00:15:20.130 align:start position:0% meeting and the Stanford meeting and it says<00:15:17.440> links<00:15:17.830> to<00:15:17.950> the<00:15:18.040> YouTube<00:15:18.370> pages<00:15:19.140> also 00:15:20.130 --> 00:15:20.140 align:start position:0% says links to the YouTube pages also 00:15:20.140 --> 00:15:22.260 align:start position:0% says links to the YouTube pages also check<00:15:20.410> out<00:15:20.560> the<00:15:20.740> PM<00:15:21.220> repo<00:15:21.610> on<00:15:21.790> aetherium 00:15:22.260 --> 00:15:22.270 align:start position:0% check out the PM repo on aetherium 00:15:22.270 --> 00:15:24.480 align:start position:0% check out the PM repo on aetherium github<00:15:22.780> that's<00:15:23.770> the<00:15:23.950> one<00:15:24.100> where<00:15:24.280> we<00:15:24.370> have<00:15:24.460> the 00:15:24.480 --> 00:15:24.490 align:start position:0% github that's the one where we have the 00:15:24.490 --> 00:15:26.340 align:start position:0% github that's the one where we have the bi-weekly<00:15:24.760> core<00:15:25.360> developer<00:15:25.840> meetings<00:15:26.170> that 00:15:26.340 --> 00:15:26.350 align:start position:0% bi-weekly core developer meetings that 00:15:26.350 --> 00:15:28.200 align:start position:0% bi-weekly core developer meetings that myself<00:15:26.530> and<00:15:26.920> a<00:15:26.980> few<00:15:27.190> others<00:15:27.400> help<00:15:27.700> coordinate 00:15:28.200 --> 00:15:28.210 align:start position:0% myself and a few others help coordinate 00:15:28.210 --> 00:15:30.900 align:start position:0% myself and a few others help coordinate and<00:15:28.360> run<00:15:28.570> for<00:15:29.440> every<00:15:29.680> core<00:15:29.920> developer<00:15:30.370> meeting 00:15:30.900 --> 00:15:30.910 align:start position:0% and run for every core developer meeting 00:15:30.910 --> 00:15:32.280 align:start position:0% and run for every core developer meeting that<00:15:31.030> happens<00:15:31.330> every<00:15:31.540> two<00:15:31.750> weeks<00:15:31.960> we<00:15:32.170> have<00:15:32.260> a 00:15:32.280 --> 00:15:32.290 align:start position:0% that happens every two weeks we have a 00:15:32.290 --> 00:15:35.040 align:start position:0% that happens every two weeks we have a full<00:15:32.560> transcript<00:15:33.310> of<00:15:33.400> notes<00:15:33.810> that's<00:15:34.810> in<00:15:34.960> the 00:15:35.040 --> 00:15:35.050 align:start position:0% full transcript of notes that's in the 00:15:35.050 --> 00:15:37.620 align:start position:0% full transcript of notes that's in the PM<00:15:35.350> repo<00:15:35.800> and<00:15:35.860> you<00:15:36.040> can<00:15:36.190> go<00:15:36.340> back<00:15:36.550> three<00:15:37.270> years 00:15:37.620 --> 00:15:37.630 align:start position:0% PM repo and you can go back three years 00:15:37.630 --> 00:15:39.660 align:start position:0% PM repo and you can go back three years and<00:15:37.870> see<00:15:38.050> notes<00:15:38.290> for<00:15:38.560> every<00:15:38.860> meeting<00:15:39.100> also 00:15:39.660 --> 00:15:39.670 align:start position:0% and see notes for every meeting also 00:15:39.670 --> 00:15:42.330 align:start position:0% and see notes for every meeting also YouTube<00:15:40.420> streams<00:15:40.840> and<00:15:41.170> live<00:15:41.410> recordings<00:15:42.040> of 00:15:42.330 --> 00:15:42.340 align:start position:0% YouTube streams and live recordings of 00:15:42.340 --> 00:15:45.360 align:start position:0% YouTube streams and live recordings of almost<00:15:42.910> every<00:15:43.210> meeting<00:15:44.010> contact<00:15:45.010> me<00:15:45.160> if<00:15:45.250> you 00:15:45.360 --> 00:15:45.370 align:start position:0% almost every meeting contact me if you 00:15:45.370 --> 00:15:46.890 align:start position:0% almost every meeting contact me if you want<00:15:45.520> to<00:15:45.610> help<00:15:45.790> if<00:15:45.970> you're<00:15:46.150> like<00:15:46.420> a<00:15:46.450> low-level 00:15:46.890 --> 00:15:46.900 align:start position:0% want to help if you're like a low-level 00:15:46.900 --> 00:15:50.250 align:start position:0% want to help if you're like a low-level developer<00:15:47.580> this<00:15:48.580> stuff<00:15:48.790> is<00:15:48.940> more<00:15:49.120> like<00:15:49.510> not 00:15:50.250 --> 00:15:50.260 align:start position:0% developer this stuff is more like not 00:15:50.260 --> 00:15:51.930 align:start position:0% developer this stuff is more like not for<00:15:50.440> people<00:15:50.650> who<00:15:50.740> build<00:15:50.950> apps<00:15:51.130> necessarily 00:15:51.930 --> 00:15:51.940 align:start position:0% for people who build apps necessarily 00:15:51.940 --> 00:15:53.610 align:start position:0% for people who build apps necessarily except<00:15:52.330> to<00:15:52.420> get<00:15:52.540> their<00:15:52.690> input<00:15:52.870> this<00:15:53.320> is<00:15:53.440> more 00:15:53.610 --> 00:15:53.620 align:start position:0% except to get their input this is more 00:15:53.620 --> 00:15:55.920 align:start position:0% except to get their input this is more for<00:15:53.800> like<00:15:54.010> low-level<00:15:54.850> client<00:15:55.240> developers<00:15:55.690> and 00:15:55.920 --> 00:15:55.930 align:start position:0% for like low-level client developers and 00:15:55.930 --> 00:15:57.000 align:start position:0% for like low-level client developers and people<00:15:56.200> looking<00:15:56.410> at<00:15:56.530> working<00:15:56.710> on<00:15:56.920> the 00:15:57.000 --> 00:15:57.010 align:start position:0% people looking at working on the 00:15:57.010 --> 00:15:59.010 align:start position:0% people looking at working on the protocol<00:15:57.460> or<00:15:57.580> the<00:15:57.640> networking<00:15:58.060> layer<00:15:58.210> but<00:15:58.690> if 00:15:59.010 --> 00:15:59.020 align:start position:0% protocol or the networking layer but if 00:15:59.020 --> 00:16:00.450 align:start position:0% protocol or the networking layer but if you're<00:15:59.230> interested<00:15:59.530> in<00:15:59.860> that<00:15:59.890> and<00:16:00.160> don't<00:16:00.340> know 00:16:00.450 --> 00:16:00.460 align:start position:0% you're interested in that and don't know 00:16:00.460 --> 00:16:02.640 align:start position:0% you're interested in that and don't know where<00:16:00.610> to<00:16:00.700> start<00:16:00.970> please<00:16:01.720> reach<00:16:02.080> out<00:16:02.290> to<00:16:02.350> me<00:16:02.530> I 00:16:02.640 --> 00:16:02.650 align:start position:0% where to start please reach out to me I 00:16:02.650 --> 00:16:04.190 align:start position:0% where to start please reach out to me I can<00:16:02.890> connect<00:16:03.220> you<00:16:03.280> with<00:16:03.430> the<00:16:03.520> right<00:16:03.640> people 00:16:04.190 --> 00:16:04.200 align:start position:0% can connect you with the right people 00:16:04.200 --> 00:16:06.690 align:start position:0% can connect you with the right people and<00:16:05.200> I'm<00:16:05.380> not<00:16:05.590> like<00:16:05.860> an<00:16:06.040> angry<00:16:06.370> frustrated 00:16:06.690 --> 00:16:06.700 align:start position:0% and I'm not like an angry frustrated 00:16:06.700 --> 00:16:12.780 align:start position:0% and I'm not like an angry frustrated person<00:16:07.420> I'm<00:16:07.630> happy<00:16:07.960> happy<00:16:08.770> to<00:16:08.860> help<00:16:11.790> alright 00:16:12.780 --> 00:16:12.790 align:start position:0% person I'm happy happy to help alright 00:16:12.790 --> 00:16:15.480 align:start position:0% person I'm happy happy to help alright so<00:16:13.660> everyone<00:16:14.140> thank<00:16:14.620> you<00:16:14.710> so<00:16:14.890> much<00:16:15.070> start<00:16:15.370> to 00:16:15.480 --> 00:16:15.490 align:start position:0% so everyone thank you so much start to 00:16:15.490 --> 00:16:17.310 align:start position:0% so everyone thank you so much start to come<00:16:15.670> up<00:16:15.700> to<00:16:15.940> the<00:16:16.060> front<00:16:16.330> for<00:16:16.540> questions<00:16:17.080> the 00:16:17.310 --> 00:16:17.320 align:start position:0% come up to the front for questions the 00:16:17.320 --> 00:16:21.030 align:start position:0% come up to the front for questions the microphones<00:16:18.040> over<00:16:18.340> there<00:16:18.550> and<00:16:19.410> yeah<00:16:20.440> anybody 00:16:21.030 --> 00:16:21.040 align:start position:0% microphones over there and yeah anybody 00:16:21.040 --> 00:16:24.660 align:start position:0% microphones over there and yeah anybody got<00:16:21.160> questions<00:16:22.980> if<00:16:23.980> not<00:16:24.220> I<00:16:24.280> could<00:16:24.400> talk<00:16:24.640> about 00:16:24.660 --> 00:16:24.670 align:start position:0% got questions if not I could talk about 00:16:24.670 --> 00:16:27.390 align:start position:0% got questions if not I could talk about my<00:16:24.880> table<00:16:25.330> top<00:16:25.510> RPG<00:16:25.720> podcast<00:16:26.680> but<00:16:26.980> that's<00:16:27.190> like 00:16:27.390 --> 00:16:27.400 align:start position:0% my table top RPG podcast but that's like 00:16:27.400 --> 00:16:29.310 align:start position:0% my table top RPG podcast but that's like very<00:16:27.540> unrelated<00:16:28.540> so<00:16:28.780> I<00:16:28.810> don't<00:16:29.050> know<00:16:29.110> how<00:16:29.260> many 00:16:29.310 --> 00:16:29.320 align:start position:0% very unrelated so I don't know how many 00:16:29.320 --> 00:16:31.200 align:start position:0% very unrelated so I don't know how many people<00:16:29.680> are<00:16:29.740> gonna<00:16:29.830> enjoy<00:16:30.190> that<00:16:30.220> Oh<00:16:30.550> some<00:16:31.060> keep 00:16:31.200 --> 00:16:31.210 align:start position:0% people are gonna enjoy that Oh some keep 00:16:31.210 --> 00:16:33.660 align:start position:0% people are gonna enjoy that Oh some keep some<00:16:31.390> fans<00:16:31.950> hey<00:16:32.950> what's<00:16:33.160> up<00:16:33.280> introduce 00:16:33.660 --> 00:16:33.670 align:start position:0% some fans hey what's up introduce 00:16:33.670 --> 00:16:35.400 align:start position:0% some fans hey what's up introduce yourself<00:16:33.700> and<00:16:34.270> then<00:16:34.360> pose<00:16:34.570> your<00:16:34.720> question<00:16:35.080> hi 00:16:35.400 --> 00:16:35.410 align:start position:0% yourself and then pose your question hi 00:16:35.410 --> 00:16:37.020 align:start position:0% yourself and then pose your question hi I'm<00:16:35.620> sorry<00:16:35.890> I'm<00:16:36.070> wondering<00:16:36.730> what's<00:16:36.940> the 00:16:37.020 --> 00:16:37.030 align:start position:0% I'm sorry I'm wondering what's the 00:16:37.030 --> 00:16:39.300 align:start position:0% I'm sorry I'm wondering what's the soonest<00:16:37.630> that<00:16:37.780> yeah<00:16:38.380> if<00:16:38.440> you<00:16:38.530> wanted<00:16:38.800> five 00:16:39.300 --> 00:16:39.310 align:start position:0% soonest that yeah if you wanted five 00:16:39.310 --> 00:16:42.960 align:start position:0% soonest that yeah if you wanted five five<00:16:39.490> nine<00:16:39.570> might<00:16:40.570> be<00:16:41.560> implemented<00:16:42.100> awesome 00:16:42.960 --> 00:16:42.970 align:start position:0% five nine might be implemented awesome 00:16:42.970 --> 00:16:45.630 align:start position:0% five nine might be implemented awesome the<00:16:43.150> IP<00:16:43.330> five<00:16:43.750> five<00:16:44.020> nine<00:16:44.440> one<00:16:44.860> five<00:16:45.370> five<00:16:45.610> nine 00:16:45.630 --> 00:16:45.640 align:start position:0% the IP five five nine one five five nine 00:16:45.640 --> 00:16:48.000 align:start position:0% the IP five five nine one five five nine that<00:16:46.300> was<00:16:46.570> on<00:16:46.990> this<00:16:47.170> one<00:16:47.350> the<00:16:47.470> fee<00:16:47.650> market 00:16:48.000 --> 00:16:48.010 align:start position:0% that was on this one the fee market 00:16:48.010 --> 00:16:50.640 align:start position:0% that was on this one the fee market change<00:16:48.900> that's<00:16:49.900> a<00:16:50.080> good<00:16:50.230> question<00:16:50.620> for 00:16:50.640 --> 00:16:50.650 align:start position:0% change that's a good question for 00:16:50.650 --> 00:16:54.060 align:start position:0% change that's a good question for vitalik<00:16:51.460> and<00:16:51.610> Eric<00:16:52.060> I'm<00:16:52.270> thinking<00:16:52.780> 2020<00:16:53.530> they 00:16:54.060 --> 00:16:54.070 align:start position:0% vitalik and Eric I'm thinking 2020 they 00:16:54.070 --> 00:16:56.160 align:start position:0% vitalik and Eric I'm thinking 2020 they can<00:16:54.310> definitely<00:16:54.820> go<00:16:55.000> in<00:16:55.210> we<00:16:55.720> still<00:16:55.900> have<00:16:56.050> to 00:16:56.160 --> 00:16:56.170 align:start position:0% can definitely go in we still have to 00:16:56.170 --> 00:16:57.690 align:start position:0% can definitely go in we still have to come<00:16:56.320> to<00:16:56.410> consensus<00:16:56.980> around<00:16:57.280> it<00:16:57.430> but<00:16:57.520> I<00:16:57.580> have 00:16:57.690 --> 00:16:57.700 align:start position:0% come to consensus around it but I have 00:16:57.700 --> 00:17:00.930 align:start position:0% come to consensus around it but I have not<00:16:57.850> seen<00:16:57.910> much<00:16:58.360> opposition<00:16:58.750> personally<00:16:59.940> for 00:17:00.930 --> 00:17:00.940 align:start position:0% not seen much opposition personally for 00:17:00.940 --> 00:17:02.670 align:start position:0% not seen much opposition personally for it<00:17:01.120> I<00:17:01.360> think<00:17:01.870> it's<00:17:01.960> a<00:17:02.020> really<00:17:02.230> important 00:17:02.670 --> 00:17:02.680 align:start position:0% it I think it's a really important 00:17:02.680 --> 00:17:05.060 align:start position:0% it I think it's a really important change<00:17:02.950> that<00:17:03.040> a<00:17:03.190> lot<00:17:03.400> of<00:17:03.430> people<00:17:03.790> are<00:17:03.910> very 00:17:05.060 --> 00:17:05.070 align:start position:0% change that a lot of people are very 00:17:05.070 --> 00:17:06.590 align:start position:0% change that a lot of people are very you<00:17:05.130> know<00:17:05.250> like<00:17:05.880> they<00:17:06.030> really<00:17:06.210> like<00:17:06.420> the<00:17:06.570> idea 00:17:06.590 --> 00:17:06.600 align:start position:0% you know like they really like the idea 00:17:06.600 --> 00:17:08.780 align:start position:0% you know like they really like the idea of<00:17:06.930> that<00:17:07.080> it<00:17:07.650> will<00:17:07.860> change<00:17:07.920> the<00:17:08.520> user 00:17:08.780 --> 00:17:08.790 align:start position:0% of that it will change the user 00:17:08.790 --> 00:17:10.670 align:start position:0% of that it will change the user experience<00:17:09.240> a<00:17:09.570> little<00:17:09.660> bit<00:17:09.780> and<00:17:10.140> the 00:17:10.670 --> 00:17:10.680 align:start position:0% experience a little bit and the 00:17:10.680 --> 00:17:12.200 align:start position:0% experience a little bit and the experience<00:17:11.280> for<00:17:11.460> Daffy<00:17:11.670> Debs 00:17:12.200 --> 00:17:12.210 align:start position:0% experience for Daffy Debs 00:17:12.210 --> 00:17:13.490 align:start position:0% experience for Daffy Debs so<00:17:12.660> that<00:17:12.810> is<00:17:12.930> something<00:17:13.140> to<00:17:13.260> take<00:17:13.470> into 00:17:13.490 --> 00:17:13.500 align:start position:0% so that is something to take into 00:17:13.500 --> 00:17:16.640 align:start position:0% so that is something to take into consideration<00:17:14.030> but<00:17:15.030> otherwise<00:17:15.450> I<00:17:15.930> think<00:17:16.080> that 00:17:16.640 --> 00:17:16.650 align:start position:0% consideration but otherwise I think that 00:17:16.650 --> 00:17:26.340 align:start position:0% consideration but otherwise I think that that's<00:17:16.920> a<00:17:17.100> really<00:17:17.250> good<00:17:17.460> idea 00:17:26.340 --> 00:17:26.350 align:start position:0% 00:17:26.350 --> 00:17:28.410 align:start position:0% you