WEBVTT Kind: captions Language: en 00:00:04.610 --> 00:00:07.090 align:start position:0% what<00:00:05.360> this<00:00:05.510> is<00:00:05.810> is<00:00:06.110> a<00:00:06.200> community<00:00:06.860> discussion 00:00:07.090 --> 00:00:07.100 align:start position:0% what this is is a community discussion 00:00:07.100 --> 00:00:11.110 align:start position:0% what this is is a community discussion and<00:00:07.700> we<00:00:07.970> have<00:00:08.180> people<00:00:08.600> who<00:00:08.750> are<00:00:08.780> core<00:00:09.110> devs<00:00:10.120> we 00:00:11.110 --> 00:00:11.120 align:start position:0% and we have people who are core devs we 00:00:11.120 --> 00:00:13.990 align:start position:0% and we have people who are core devs we have<00:00:11.270> cat<00:00:11.510> herders<00:00:11.900> here<00:00:12.469> we<00:00:13.400> have<00:00:13.520> all<00:00:13.700> kinds 00:00:13.990 --> 00:00:14.000 align:start position:0% have cat herders here we have all kinds 00:00:14.000 --> 00:00:15.280 align:start position:0% have cat herders here we have all kinds of<00:00:14.030> people<00:00:14.210> or<00:00:14.750> from<00:00:14.960> different 00:00:15.280 --> 00:00:15.290 align:start position:0% of people or from different 00:00:15.290 --> 00:00:16.690 align:start position:0% of people or from different organizations<00:00:15.590> to<00:00:16.010> bring<00:00:16.220> different<00:00:16.340> skills 00:00:16.690 --> 00:00:16.700 align:start position:0% organizations to bring different skills 00:00:16.700 --> 00:00:18.519 align:start position:0% organizations to bring different skills to<00:00:17.150> this<00:00:17.270> and<00:00:17.570> what<00:00:18.110> we're<00:00:18.200> going<00:00:18.290> to<00:00:18.349> talk 00:00:18.519 --> 00:00:18.529 align:start position:0% to this and what we're going to talk 00:00:18.529 --> 00:00:22.179 align:start position:0% to this and what we're going to talk about<00:00:18.590> is<00:00:18.920> theorem<00:00:19.340> 1x<00:00:19.990> and<00:00:20.990> so<00:00:21.529> this<00:00:21.950> is<00:00:22.070> an 00:00:22.179 --> 00:00:22.189 align:start position:0% about is theorem 1x and so this is an 00:00:22.189 --> 00:00:24.069 align:start position:0% about is theorem 1x and so this is an open<00:00:22.310> format<00:00:22.849> this<00:00:23.000> is<00:00:23.150> a<00:00:23.180> fishbowl<00:00:23.630> format 00:00:24.069 --> 00:00:24.079 align:start position:0% open format this is a fishbowl format 00:00:24.079 --> 00:00:26.019 align:start position:0% open format this is a fishbowl format and<00:00:24.320> so<00:00:24.770> what<00:00:24.919> that<00:00:24.950> means<00:00:25.099> is<00:00:25.550> people<00:00:25.880> from 00:00:26.019 --> 00:00:26.029 align:start position:0% and so what that means is people from 00:00:26.029 --> 00:00:27.670 align:start position:0% and so what that means is people from the<00:00:26.119> audience<00:00:26.390> can<00:00:26.540> join<00:00:26.810> us<00:00:27.020> in<00:00:27.230> the<00:00:27.290> week<00:00:27.439> we 00:00:27.670 --> 00:00:27.680 align:start position:0% the audience can join us in the week we 00:00:27.680 --> 00:00:29.530 align:start position:0% the audience can join us in the week we have<00:00:27.829> these<00:00:27.980> -<00:00:28.279> this<00:00:28.579> chair<00:00:28.880> right<00:00:29.090> here<00:00:29.419> in 00:00:29.530 --> 00:00:29.540 align:start position:0% have these - this chair right here in 00:00:29.540 --> 00:00:31.060 align:start position:0% have these - this chair right here in this<00:00:29.660> chair<00:00:29.869> right<00:00:29.930> there<00:00:30.560> we're<00:00:30.710> gonna<00:00:30.829> try 00:00:31.060 --> 00:00:31.070 align:start position:0% this chair right there we're gonna try 00:00:31.070 --> 00:00:33.340 align:start position:0% this chair right there we're gonna try to<00:00:31.099> keep<00:00:31.340> open<00:00:31.790> so<00:00:32.480> if<00:00:32.599> you<00:00:32.720> come<00:00:32.930> to<00:00:33.050> the<00:00:33.140> front 00:00:33.340 --> 00:00:33.350 align:start position:0% to keep open so if you come to the front 00:00:33.350 --> 00:00:34.360 align:start position:0% to keep open so if you come to the front there's<00:00:33.530> someone<00:00:33.739> there<00:00:33.829> you<00:00:33.920> can<00:00:34.070> kick<00:00:34.250> them 00:00:34.360 --> 00:00:34.370 align:start position:0% there's someone there you can kick them 00:00:34.370 --> 00:00:38.229 align:start position:0% there's someone there you can kick them out<00:00:34.489> if<00:00:35.270> you<00:00:35.450> would<00:00:35.570> like<00:00:35.720> to<00:00:35.750> to<00:00:36.410> join<00:00:37.180> but<00:00:38.180> I 00:00:38.229 --> 00:00:38.239 align:start position:0% out if you would like to to join but I 00:00:38.239 --> 00:00:40.180 align:start position:0% out if you would like to to join but I expect<00:00:38.660> this<00:00:38.750> to<00:00:38.930> fill<00:00:39.140> in<00:00:39.320> more<00:00:39.530> as<00:00:39.829> more<00:00:40.100> and 00:00:40.180 --> 00:00:40.190 align:start position:0% expect this to fill in more as more and 00:00:40.190 --> 00:00:41.860 align:start position:0% expect this to fill in more as more and more<00:00:40.219> people<00:00:40.430> want<00:00:40.699> to<00:00:40.760> participate<00:00:41.239> if<00:00:41.780> you 00:00:41.860 --> 00:00:41.870 align:start position:0% more people want to participate if you 00:00:41.870 --> 00:00:43.450 align:start position:0% more people want to participate if you want<00:00:42.019> to<00:00:42.109> keep<00:00:42.289> participating<00:00:43.070> you<00:00:43.160> can<00:00:43.309> move 00:00:43.450 --> 00:00:43.460 align:start position:0% want to keep participating you can move 00:00:43.460 --> 00:00:44.979 align:start position:0% want to keep participating you can move into<00:00:43.609> one<00:00:43.820> of<00:00:43.910> these<00:00:44.000> chairs<00:00:44.300> and<00:00:44.570> just<00:00:44.600> stay 00:00:44.979 --> 00:00:44.989 align:start position:0% into one of these chairs and just stay 00:00:44.989 --> 00:00:47.169 align:start position:0% into one of these chairs and just stay maybe<00:00:45.980> you<00:00:46.129> won't<00:00:46.250> get<00:00:46.429> kicked<00:00:46.640> out<00:00:46.789> but<00:00:47.090> I 00:00:47.169 --> 00:00:47.179 align:start position:0% maybe you won't get kicked out but I 00:00:47.179 --> 00:00:48.750 align:start position:0% maybe you won't get kicked out but I think<00:00:47.359> anyone<00:00:47.660> could<00:00:47.840> be<00:00:47.960> kicked<00:00:48.170> out<00:00:48.350> so 00:00:48.750 --> 00:00:48.760 align:start position:0% think anyone could be kicked out so 00:00:48.760 --> 00:00:52.569 align:start position:0% think anyone could be kicked out so sorry<00:00:50.469> but<00:00:51.469> yeah<00:00:51.679> just<00:00:51.949> keep<00:00:52.129> in<00:00:52.219> mind<00:00:52.250> you're 00:00:52.569 --> 00:00:52.579 align:start position:0% sorry but yeah just keep in mind you're 00:00:52.579 --> 00:00:54.910 align:start position:0% sorry but yeah just keep in mind you're you're<00:00:52.969> free<00:00:53.449> to<00:00:53.780> participate<00:00:53.989> so<00:00:54.649> we're 00:00:54.910 --> 00:00:54.920 align:start position:0% you're free to participate so we're 00:00:54.920 --> 00:00:57.880 align:start position:0% you're free to participate so we're gonna<00:00:55.010> have<00:00:55.339> I<00:00:56.239> guess<00:00:56.960> we'll<00:00:57.140> try<00:00:57.320> to<00:00:57.379> keep<00:00:57.769> a 00:00:57.880 --> 00:00:57.890 align:start position:0% gonna have I guess we'll try to keep a 00:00:57.890 --> 00:01:00.009 align:start position:0% gonna have I guess we'll try to keep a mic<00:00:58.100> mic<00:00:58.370> over<00:00:58.850> here<00:00:58.999> if<00:00:59.539> anyone<00:00:59.629> wants<00:00:59.989> to 00:01:00.009 --> 00:01:00.019 align:start position:0% mic mic over here if anyone wants to 00:01:00.019 --> 00:01:02.290 align:start position:0% mic mic over here if anyone wants to come<00:01:00.079> and<00:01:00.440> we'll<00:01:00.559> put<00:01:00.679> a<00:01:00.710> mic<00:01:00.890> right<00:01:00.920> here<00:01:01.370> and 00:01:02.290 --> 00:01:02.300 align:start position:0% come and we'll put a mic right here and 00:01:02.300 --> 00:01:05.140 align:start position:0% come and we'll put a mic right here and so<00:01:02.510> I<00:01:02.539> guess<00:01:02.989> we'll<00:01:03.170> get<00:01:03.260> started<00:01:03.320> the<00:01:04.159> key<00:01:04.430> the 00:01:05.140 --> 00:01:05.150 align:start position:0% so I guess we'll get started the key the 00:01:05.150 --> 00:01:06.820 align:start position:0% so I guess we'll get started the key the key<00:01:05.360> to<00:01:05.510> this<00:01:05.630> is<00:01:05.900> where<00:01:06.200> we're<00:01:06.440> gonna<00:01:06.500> start 00:01:06.820 --> 00:01:06.830 align:start position:0% key to this is where we're gonna start 00:01:06.830 --> 00:01:08.380 align:start position:0% key to this is where we're gonna start with<00:01:07.010> what<00:01:07.220> what<00:01:07.610> does<00:01:07.760> the<00:01:07.880> community<00:01:08.090> want 00:01:08.380 --> 00:01:08.390 align:start position:0% with what what does the community want 00:01:08.390 --> 00:01:10.540 align:start position:0% with what what does the community want to<00:01:08.600> talk<00:01:08.750> about<00:01:08.930> what<00:01:09.650> -<00:01:09.800> developers<00:01:10.280> want<00:01:10.490> to 00:01:10.540 --> 00:01:10.550 align:start position:0% to talk about what - developers want to 00:01:10.550 --> 00:01:12.100 align:start position:0% to talk about what - developers want to talk<00:01:10.700> about<00:01:10.820> what<00:01:11.030> core<00:01:11.330> developers<00:01:11.840> want<00:01:12.050> to 00:01:12.100 --> 00:01:12.110 align:start position:0% talk about what core developers want to 00:01:12.110 --> 00:01:14.920 align:start position:0% talk about what core developers want to talk<00:01:12.260> about<00:01:12.610> and<00:01:13.610> then<00:01:13.940> I'll<00:01:14.090> I<00:01:14.300> can<00:01:14.420> just<00:01:14.750> pass 00:01:14.920 --> 00:01:14.930 align:start position:0% talk about and then I'll I can just pass 00:01:14.930 --> 00:01:17.140 align:start position:0% talk about and then I'll I can just pass the<00:01:14.960> microphone<00:01:15.260> on<00:01:15.770> to<00:01:16.010> you<00:01:16.160> all<00:01:16.670> and<00:01:17.000> then 00:01:17.140 --> 00:01:17.150 align:start position:0% the microphone on to you all and then 00:01:17.150 --> 00:01:19.330 align:start position:0% the microphone on to you all and then maybe<00:01:17.690> you<00:01:17.870> guys<00:01:18.050> can<00:01:18.350> get<00:01:18.500> started<00:01:18.530> with<00:01:19.220> the 00:01:19.330 --> 00:01:19.340 align:start position:0% maybe you guys can get started with the 00:01:19.340 --> 00:01:20.740 align:start position:0% maybe you guys can get started with the conversation 00:01:20.740 --> 00:01:20.750 align:start position:0% conversation 00:01:20.750 --> 00:01:22.720 align:start position:0% conversation sounds<00:01:21.230> great<00:01:21.410> should<00:01:21.590> we<00:01:21.650> do<00:01:21.770> intros<00:01:22.190> with 00:01:22.720 --> 00:01:22.730 align:start position:0% sounds great should we do intros with 00:01:22.730 --> 00:01:24.130 align:start position:0% sounds great should we do intros with some<00:01:22.970> of<00:01:23.060> the<00:01:23.120> people<00:01:23.390> up<00:01:23.480> here<00:01:23.510> who<00:01:23.720> are<00:01:23.900> core 00:01:24.130 --> 00:01:24.140 align:start position:0% some of the people up here who are core 00:01:24.140 --> 00:01:25.390 align:start position:0% some of the people up here who are core devs<00:01:24.350> and<00:01:24.590> stuff<00:01:24.770> just<00:01:24.950> so<00:01:25.100> people<00:01:25.250> are 00:01:25.390 --> 00:01:25.400 align:start position:0% devs and stuff just so people are 00:01:25.400 --> 00:01:26.860 align:start position:0% devs and stuff just so people are familiar<00:01:25.520> well<00:01:26.300> everyone<00:01:26.570> in<00:01:26.630> the<00:01:26.690> circle 00:01:26.860 --> 00:01:26.870 align:start position:0% familiar well everyone in the circle 00:01:26.870 --> 00:01:29.110 align:start position:0% familiar well everyone in the circle gets<00:01:27.110> an<00:01:27.290> intro<00:01:27.590> so<00:01:27.800> perfect<00:01:28.520> yes<00:01:28.730> if<00:01:28.910> you're 00:01:29.110 --> 00:01:29.120 align:start position:0% gets an intro so perfect yes if you're 00:01:29.120 --> 00:01:31.030 align:start position:0% gets an intro so perfect yes if you're gonna<00:01:29.210> sit<00:01:29.450> in<00:01:29.570> a<00:01:29.630> circle<00:01:29.960> then<00:01:30.170> introduce 00:01:31.030 --> 00:01:31.040 align:start position:0% gonna sit in a circle then introduce 00:01:31.040 --> 00:01:34.750 align:start position:0% gonna sit in a circle then introduce yourself<00:01:31.400> yes<00:01:31.790> okay<00:01:33.190> so<00:01:34.190> let's<00:01:34.400> kick<00:01:34.550> it<00:01:34.610> off 00:01:34.750 --> 00:01:34.760 align:start position:0% yourself yes okay so let's kick it off 00:01:34.760 --> 00:01:36.730 align:start position:0% yourself yes okay so let's kick it off I'm<00:01:35.030> Jamie<00:01:35.300> Pitts<00:01:35.630> I've<00:01:36.260> worked<00:01:36.500> with 00:01:36.730 --> 00:01:36.740 align:start position:0% I'm Jamie Pitts I've worked with 00:01:36.740 --> 00:01:38.650 align:start position:0% I'm Jamie Pitts I've worked with magicians<00:01:37.190> I'm<00:01:37.580> also<00:01:38.000> work<00:01:38.150> at<00:01:38.270> the<00:01:38.360> etherium 00:01:38.650 --> 00:01:38.660 align:start position:0% magicians I'm also work at the etherium 00:01:38.660 --> 00:01:42.610 align:start position:0% magicians I'm also work at the etherium foundation<00:01:39.700> that's<00:01:40.700> a<00:01:40.880> net<00:01:41.060> back<00:01:41.450> there<00:01:41.660> once 00:01:42.610 --> 00:01:42.620 align:start position:0% foundation that's a net back there once 00:01:42.620 --> 00:01:45.700 align:start position:0% foundation that's a net back there once you<00:01:42.740> introduce<00:01:42.860> yourself<00:01:43.690> hi<00:01:44.690> guys<00:01:44.930> I'm<00:01:45.350> in<00:01:45.590> it 00:01:45.700 --> 00:01:45.710 align:start position:0% you introduce yourself hi guys I'm in it 00:01:45.710 --> 00:01:47.770 align:start position:0% you introduce yourself hi guys I'm in it and<00:01:45.980> I'm<00:01:46.220> working<00:01:46.670> with<00:01:46.820> it<00:01:46.970> here<00:01:47.150> magicians 00:01:47.770 --> 00:01:47.780 align:start position:0% and I'm working with it here magicians 00:01:47.780 --> 00:01:50.110 align:start position:0% and I'm working with it here magicians and<00:01:48.260> I'm<00:01:48.530> helping<00:01:48.950> out<00:01:49.040> with<00:01:49.220> operations<00:01:49.880> and 00:01:50.110 --> 00:01:50.120 align:start position:0% and I'm helping out with operations and 00:01:50.120 --> 00:01:52.690 align:start position:0% and I'm helping out with operations and organizing<00:01:50.750> events<00:01:51.020> and<00:01:51.740> making<00:01:52.280> sure<00:01:52.490> that 00:01:52.690 --> 00:01:52.700 align:start position:0% organizing events and making sure that 00:01:52.700 --> 00:01:54.550 align:start position:0% organizing events and making sure that all<00:01:52.910> those<00:01:53.090> people<00:01:53.630> and<00:01:53.900> all<00:01:54.080> those<00:01:54.320> the 00:01:54.550 --> 00:01:54.560 align:start position:0% all those people and all those the 00:01:54.560 --> 00:01:58.270 align:start position:0% all those people and all those the important<00:01:55.220> discussions<00:01:55.760> will<00:01:56.030> happen<00:01:57.100> cool 00:01:58.270 --> 00:01:58.280 align:start position:0% important discussions will happen cool 00:01:58.280 --> 00:02:00.280 align:start position:0% important discussions will happen cool so<00:01:58.460> we'll<00:01:59.390> leave<00:01:59.510> to<00:01:59.690> you<00:01:59.750> Hudson<00:01:59.870> you<00:02:00.140> wanna 00:02:00.280 --> 00:02:00.290 align:start position:0% so we'll leave to you Hudson you wanna 00:02:00.290 --> 00:02:03.610 align:start position:0% so we'll leave to you Hudson you wanna introduce<00:02:00.730> so<00:02:01.730> my<00:02:02.450> name<00:02:02.600> is<00:02:02.630> Alexia<00:02:03.260> Hoonah 00:02:03.610 --> 00:02:03.620 align:start position:0% introduce so my name is Alexia Hoonah 00:02:03.620 --> 00:02:05.920 align:start position:0% introduce so my name is Alexia Hoonah I'm<00:02:03.800> I've<00:02:04.580> been<00:02:04.760> working<00:02:05.120> on<00:02:05.240> your<00:02:05.570> biggest 00:02:05.920 --> 00:02:05.930 align:start position:0% I'm I've been working on your biggest 00:02:05.930 --> 00:02:08.020 align:start position:0% I'm I've been working on your biggest client<00:02:06.170> which<00:02:06.590> is<00:02:06.620> derivative<00:02:07.220> of<00:02:07.370> Kosir<00:02:07.880> IAM 00:02:08.020 --> 00:02:08.030 align:start position:0% client which is derivative of Kosir IAM 00:02:08.030 --> 00:02:11.290 align:start position:0% client which is derivative of Kosir IAM and<00:02:08.660> also<00:02:09.019> the<00:02:09.410> last<00:02:09.679> this<00:02:10.429> year<00:02:10.489> i've<00:02:11.120> also 00:02:11.290 --> 00:02:11.300 align:start position:0% and also the last this year i've also 00:02:11.300 --> 00:02:13.720 align:start position:0% and also the last this year i've also been<00:02:11.480> involved<00:02:11.870> into<00:02:12.400> research<00:02:13.400> in 00:02:13.720 --> 00:02:13.730 align:start position:0% been involved into research in 00:02:13.730 --> 00:02:15.520 align:start position:0% been involved into research in development<00:02:14.510> of 00:02:15.520 --> 00:02:15.530 align:start position:0% development of 00:02:15.530 --> 00:02:18.220 align:start position:0% development of into<00:02:15.950> state<00:02:16.250> rent<00:02:16.610> and<00:02:16.880> stateless<00:02:17.480> clients<00:02:17.990> so 00:02:18.220 --> 00:02:18.230 align:start position:0% into state rent and stateless clients so 00:02:18.230 --> 00:02:20.140 align:start position:0% into state rent and stateless clients so which<00:02:18.500> I'm<00:02:18.710> all<00:02:19.220> these<00:02:19.550> things<00:02:19.760> I'm<00:02:19.910> still 00:02:20.140 --> 00:02:20.150 align:start position:0% which I'm all these things I'm still 00:02:20.150 --> 00:02:28.150 align:start position:0% which I'm all these things I'm still doing<00:02:23.020> hey<00:02:24.020> I'm<00:02:24.530> Hudson<00:02:24.950> Jamison<00:02:25.520> I<00:02:26.830> work<00:02:27.830> with 00:02:28.150 --> 00:02:28.160 align:start position:0% doing hey I'm Hudson Jamison I work with 00:02:28.160 --> 00:02:29.680 align:start position:0% doing hey I'm Hudson Jamison I work with the<00:02:28.280> etherium<00:02:28.700> Foundation<00:02:29.330> and<00:02:29.480> with<00:02:29.570> the 00:02:29.680 --> 00:02:29.690 align:start position:0% the etherium Foundation and with the 00:02:29.690 --> 00:02:33.880 align:start position:0% the etherium Foundation and with the etherium<00:02:30.110> cat<00:02:30.290> herders<00:02:30.680> I<00:02:31.480> also<00:02:32.620> am<00:02:33.620> one<00:02:33.860> of 00:02:33.880 --> 00:02:33.890 align:start position:0% etherium cat herders I also am one of 00:02:33.890 --> 00:02:36.160 align:start position:0% etherium cat herders I also am one of the<00:02:34.040> organizers<00:02:34.070> of<00:02:34.730> the<00:02:34.970> bi-weekly<00:02:35.480> core 00:02:36.160 --> 00:02:36.170 align:start position:0% the organizers of the bi-weekly core 00:02:36.170 --> 00:02:37.540 align:start position:0% the organizers of the bi-weekly core developer<00:02:36.590> meetings<00:02:36.920> along<00:02:37.160> with<00:02:37.340> a<00:02:37.370> few 00:02:37.540 --> 00:02:37.550 align:start position:0% developer meetings along with a few 00:02:37.550 --> 00:02:40.480 align:start position:0% developer meetings along with a few other<00:02:37.700> people<00:02:37.760> who<00:02:38.120> we<00:02:38.990> all<00:02:39.110> help<00:02:39.350> out 00:02:40.480 --> 00:02:40.490 align:start position:0% other people who we all help out 00:02:40.490 --> 00:02:44.530 align:start position:0% other people who we all help out I'm<00:02:41.060> not<00:02:41.330> accord<00:02:41.780> EV<00:02:42.190> but<00:02:43.190> I<00:02:43.459> try<00:02:44.060> to<00:02:44.120> keep<00:02:44.330> up 00:02:44.530 --> 00:02:44.540 align:start position:0% I'm not accord EV but I try to keep up 00:02:44.540 --> 00:02:45.820 align:start position:0% I'm not accord EV but I try to keep up with<00:02:44.660> the<00:02:44.810> text<00:02:45.260> so<00:02:45.350> that<00:02:45.470> I<00:02:45.500> can<00:02:45.680> facilitate 00:02:45.820 --> 00:02:45.830 align:start position:0% with the text so that I can facilitate 00:02:45.830 --> 00:02:48.490 align:start position:0% with the text so that I can facilitate the<00:02:46.220> meetings<00:02:46.610> accurately<00:02:47.300> I've<00:02:48.110> been<00:02:48.260> doing 00:02:48.490 --> 00:02:48.500 align:start position:0% the meetings accurately I've been doing 00:02:48.500 --> 00:02:51.280 align:start position:0% the meetings accurately I've been doing that<00:02:48.620> for<00:02:48.830> the<00:02:48.860> past<00:02:48.920> three<00:02:49.550> years<00:02:49.580> roughly<00:02:50.300> so 00:02:51.280 --> 00:02:51.290 align:start position:0% that for the past three years roughly so 00:02:51.290 --> 00:02:52.840 align:start position:0% that for the past three years roughly so I<00:02:51.320> know<00:02:51.410> a<00:02:51.470> lot<00:02:51.620> about<00:02:51.800> the<00:02:51.920> process 00:02:52.840 --> 00:02:52.850 align:start position:0% I know a lot about the process 00:02:52.850 --> 00:02:55.420 align:start position:0% I know a lot about the process he's<00:02:53.570> the<00:02:53.900> hard<00:02:54.080> fork<00:02:54.320> decisions<00:02:54.860> things<00:02:55.130> like 00:02:55.420 --> 00:02:55.430 align:start position:0% he's the hard fork decisions things like 00:02:55.430 --> 00:02:57.130 align:start position:0% he's the hard fork decisions things like that<00:02:55.670> so<00:02:56.330> that's<00:02:56.450> how<00:02:56.630> I<00:02:56.660> feel<00:02:56.840> like<00:02:56.870> I<00:02:57.080> will 00:02:57.130 --> 00:02:57.140 align:start position:0% that so that's how I feel like I will 00:02:57.140 --> 00:02:59.410 align:start position:0% that so that's how I feel like I will contribute<00:02:57.650> today<00:02:58.190> I<00:02:58.459> also<00:02:58.940> have<00:02:59.120> a<00:02:59.180> talk 00:02:59.410 --> 00:02:59.420 align:start position:0% contribute today I also have a talk 00:02:59.420 --> 00:03:01.240 align:start position:0% contribute today I also have a talk tomorrow<00:02:59.690> on<00:03:00.170> the<00:03:00.260> main<00:03:00.290> stage<00:03:00.470> right<00:03:01.100> after 00:03:01.240 --> 00:03:01.250 align:start position:0% tomorrow on the main stage right after 00:03:01.250 --> 00:03:03.729 align:start position:0% tomorrow on the main stage right after Vitalik<00:03:01.970> I<00:03:02.120> think<00:03:02.300> it's<00:03:02.420> a<00:03:02.510> ten<00:03:02.780> on<00:03:03.020> eighth<00:03:03.500> one 00:03:03.729 --> 00:03:03.739 align:start position:0% Vitalik I think it's a ten on eighth one 00:03:03.739 --> 00:03:06.400 align:start position:0% Vitalik I think it's a ten on eighth one X<00:03:03.950> so<00:03:04.760> if<00:03:05.030> you<00:03:05.150> want<00:03:05.300> to<00:03:05.390> see<00:03:05.540> a<00:03:05.570> more<00:03:05.780> formal 00:03:06.400 --> 00:03:06.410 align:start position:0% X so if you want to see a more formal 00:03:06.410 --> 00:03:08.110 align:start position:0% X so if you want to see a more formal presentation<00:03:07.130> that<00:03:07.250> I<00:03:07.280> have<00:03:07.400> slides<00:03:07.640> for<00:03:08.030> and 00:03:08.110 --> 00:03:08.120 align:start position:0% presentation that I have slides for and 00:03:08.120 --> 00:03:09.550 align:start position:0% presentation that I have slides for and stuff<00:03:08.390> feel<00:03:08.600> free<00:03:08.630> to<00:03:08.810> come<00:03:09.020> to<00:03:09.110> that<00:03:09.230> tomorrow 00:03:09.550 --> 00:03:09.560 align:start position:0% stuff feel free to come to that tomorrow 00:03:09.560 --> 00:03:14.500 align:start position:0% stuff feel free to come to that tomorrow that's<00:03:10.130> the<00:03:10.280> end<00:03:10.400> of<00:03:10.459> my<00:03:10.550> showing<00:03:12.760> hey<00:03:13.760> I'm<00:03:14.330> Tim 00:03:14.500 --> 00:03:14.510 align:start position:0% that's the end of my showing hey I'm Tim 00:03:14.510 --> 00:03:17.020 align:start position:0% that's the end of my showing hey I'm Tim bake<00:03:14.690> Oh<00:03:14.870> I<00:03:15.050> work<00:03:15.560> with<00:03:16.070> the<00:03:16.160> Pegasus<00:03:16.550> team<00:03:16.760> on 00:03:17.020 --> 00:03:17.030 align:start position:0% bake Oh I work with the Pegasus team on 00:03:17.030 --> 00:03:18.370 align:start position:0% bake Oh I work with the Pegasus team on the<00:03:17.480> hyper<00:03:17.840> that<00:03:18.050> year 00:03:18.370 --> 00:03:18.380 align:start position:0% the hyper that year 00:03:18.380 --> 00:03:21.130 align:start position:0% the hyper that year hyper<00:03:18.920> ledger<00:03:19.250> basement<00:03:19.700> client<00:03:20.080> I'm<00:03:21.080> a 00:03:21.130 --> 00:03:21.140 align:start position:0% hyper ledger basement client I'm a 00:03:21.140 --> 00:03:22.750 align:start position:0% hyper ledger basement client I'm a product<00:03:21.410> manager<00:03:21.500> not<00:03:21.980> a<00:03:22.010> core<00:03:22.190> dev<00:03:22.340> but<00:03:22.610> I<00:03:22.670> do 00:03:22.750 --> 00:03:22.760 align:start position:0% product manager not a core dev but I do 00:03:22.760 --> 00:03:24.370 align:start position:0% product manager not a core dev but I do attend<00:03:23.090> the<00:03:23.209> calls<00:03:23.390> to<00:03:23.750> try<00:03:23.870> wrap<00:03:24.080> my<00:03:24.230> head 00:03:24.370 --> 00:03:24.380 align:start position:0% attend the calls to try wrap my head 00:03:24.380 --> 00:03:26.890 align:start position:0% attend the calls to try wrap my head around<00:03:24.410> the<00:03:24.830> process<00:03:25.040> and<00:03:25.580> the<00:03:25.670> eeap's<00:03:25.900> and 00:03:26.890 --> 00:03:26.900 align:start position:0% around the process and the eeap's and 00:03:26.900 --> 00:03:29.729 align:start position:0% around the process and the eeap's and I'm<00:03:27.019> also<00:03:27.140> part<00:03:27.410> of<00:03:27.470> the<00:03:27.709> cat<00:03:27.890> herders 00:03:29.729 --> 00:03:29.739 align:start position:0% I'm also part of the cat herders 00:03:29.739 --> 00:03:34.000 align:start position:0% I'm also part of the cat herders I'm<00:03:30.739> Rai<00:03:31.610> also<00:03:32.269> at<00:03:32.600> Pegasus<00:03:33.200> working<00:03:33.709> on 00:03:34.000 --> 00:03:34.010 align:start position:0% I'm Rai also at Pegasus working on 00:03:34.010 --> 00:03:42.400 align:start position:0% I'm Rai also at Pegasus working on hydrology<00:03:34.549> Basu<00:03:35.080> yeah<00:03:39.880> hi<00:03:40.880> I'm<00:03:41.269> Martin<00:03:42.019> swanda 00:03:42.400 --> 00:03:42.410 align:start position:0% hydrology Basu yeah hi I'm Martin swanda 00:03:42.410 --> 00:03:44.320 align:start position:0% hydrology Basu yeah hi I'm Martin swanda and<00:03:42.620> I<00:03:42.709> work<00:03:42.890> for<00:03:43.130> the<00:03:43.190> ethereum<00:03:43.820> foundation 00:03:44.320 --> 00:03:44.330 align:start position:0% and I work for the ethereum foundation 00:03:44.330 --> 00:03:47.680 align:start position:0% and I work for the ethereum foundation with<00:03:45.519> security<00:03:46.519> issues<00:03:46.790> aetherium 00:03:47.680 --> 00:03:47.690 align:start position:0% with security issues aetherium 00:03:47.690 --> 00:03:50.170 align:start position:0% with security issues aetherium infrastructure<00:03:48.260> may<00:03:48.500> not<00:03:48.680> and<00:03:49.040> also<00:03:49.549> I'm<00:03:49.970> one 00:03:50.170 --> 00:03:50.180 align:start position:0% infrastructure may not and also I'm one 00:03:50.180 --> 00:03:54.759 align:start position:0% infrastructure may not and also I'm one of<00:03:50.299> the<00:03:50.390> coders<00:03:50.780> on<00:03:51.410> go<00:03:51.769> with<00:03:51.920> areum<00:03:53.260> hey<00:03:54.290> so 00:03:54.759 --> 00:03:54.769 align:start position:0% of the coders on go with areum hey so 00:03:54.769 --> 00:03:57.039 align:start position:0% of the coders on go with areum hey so I'm<00:03:55.130> Peter<00:03:55.370> and<00:03:55.730> I'm<00:03:56.209> currently<00:03:56.540> the<00:03:56.840> lead 00:03:57.039 --> 00:03:57.049 align:start position:0% I'm Peter and I'm currently the lead 00:03:57.049 --> 00:04:03.220 align:start position:0% I'm Peter and I'm currently the lead deaf<00:03:57.290> of<00:03:57.500> Goethe<00:03:57.920> reom<00:03:58.280> that's<00:03:58.700> about<00:03:59.060> it<00:04:02.230> I'm 00:04:03.220 --> 00:04:03.230 align:start position:0% deaf of Goethe reom that's about it I'm 00:04:03.230 --> 00:04:05.770 align:start position:0% deaf of Goethe reom that's about it I'm Vitalik<00:04:04.130> I<00:04:04.250> advised<00:04:04.489> a<00:04:04.670> couple<00:04:04.910> ICO<00:04:05.209> projects 00:04:05.770 --> 00:04:05.780 align:start position:0% Vitalik I advised a couple ICO projects 00:04:05.780 --> 00:04:14.809 align:start position:0% Vitalik I advised a couple ICO projects it<00:04:05.930> before<00:04:06.560> never 00:04:14.809 --> 00:04:14.819 align:start position:0% 00:04:14.819 --> 00:04:18.210 align:start position:0% hello<00:04:16.440> technically<00:04:17.440> I'm<00:04:17.530> not<00:04:17.560> the<00:04:17.859> part<00:04:18.070> of 00:04:18.210 --> 00:04:18.220 align:start position:0% hello technically I'm not the part of 00:04:18.220 --> 00:04:20.580 align:start position:0% hello technically I'm not the part of the<00:04:18.370> core<00:04:18.609> team<00:04:18.639> but<00:04:19.600> I've<00:04:19.750> since<00:04:20.079> I'm<00:04:20.260> sitting 00:04:20.580 --> 00:04:20.590 align:start position:0% the core team but I've since I'm sitting 00:04:20.590 --> 00:04:25.350 align:start position:0% the core team but I've since I'm sitting here<00:04:20.859> I'm<00:04:21.280> doing<00:04:21.850> the<00:04:23.430> notes<00:04:24.430> and<00:04:24.760> the<00:04:24.880> clients 00:04:25.350 --> 00:04:25.360 align:start position:0% here I'm doing the notes and the clients 00:04:25.360 --> 00:04:27.480 align:start position:0% here I'm doing the notes and the clients with<00:04:25.600> the<00:04:25.750> nation-state<00:04:26.460> cryptography<00:04:27.460> for 00:04:27.480 --> 00:04:27.490 align:start position:0% with the nation-state cryptography for 00:04:27.490 --> 00:04:30.150 align:start position:0% with the nation-state cryptography for the<00:04:28.290> Russian<00:04:29.290> central<00:04:29.650> bank 00:04:30.150 --> 00:04:30.160 align:start position:0% the Russian central bank 00:04:30.160 --> 00:04:35.520 align:start position:0% the Russian central bank I<00:04:32.070> guess<00:04:33.070> my<00:04:33.639> name<00:04:33.790> is<00:04:33.970> Cody<00:04:34.330> born<00:04:34.690> I'm<00:04:35.410> a 00:04:35.520 --> 00:04:35.530 align:start position:0% I guess my name is Cody born I'm a 00:04:35.530 --> 00:04:37.770 align:start position:0% I guess my name is Cody born I'm a developer<00:04:36.130> on<00:04:36.340> the<00:04:36.370> adjure<00:04:37.030> blockchain<00:04:37.570> team 00:04:37.770 --> 00:04:37.780 align:start position:0% developer on the adjure blockchain team 00:04:37.780 --> 00:04:42.480 align:start position:0% developer on the adjure blockchain team at<00:04:38.410> Microsoft<00:04:39.780> hi<00:04:40.780> I'm<00:04:41.139> Lucas<00:04:41.530> I'm<00:04:41.830> just<00:04:42.340> a 00:04:42.480 --> 00:04:42.490 align:start position:0% at Microsoft hi I'm Lucas I'm just a 00:04:42.490 --> 00:04:45.180 align:start position:0% at Microsoft hi I'm Lucas I'm just a random<00:04:42.990> software<00:04:43.990> developer<00:04:44.530> who<00:04:44.740> worked<00:04:44.979> on 00:04:45.180 --> 00:04:45.190 align:start position:0% random software developer who worked on 00:04:45.190 --> 00:04:48.000 align:start position:0% random software developer who worked on depths<00:04:45.580> and<00:04:45.790> I'm<00:04:46.000> the<00:04:46.720> humbled<00:04:47.290> sitting<00:04:47.860> at 00:04:48.000 --> 00:04:48.010 align:start position:0% depths and I'm the humbled sitting at 00:04:48.010 --> 00:05:00.270 align:start position:0% depths and I'm the humbled sitting at his<00:04:48.130> magic<00:04:48.610> round<00:04:48.850> here<00:04:57.930> okay<00:04:58.930> so<00:04:59.160> what<00:05:00.160> do<00:05:00.220> you 00:05:00.270 --> 00:05:00.280 align:start position:0% his magic round here okay so what do you 00:05:00.280 --> 00:05:02.610 align:start position:0% his magic round here okay so what do you guys<00:05:00.370> want<00:05:00.550> to<00:05:00.639> talk<00:05:00.729> about<00:05:01.169> what<00:05:02.169> do<00:05:02.229> you<00:05:02.410> all 00:05:02.610 --> 00:05:02.620 align:start position:0% guys want to talk about what do you all 00:05:02.620 --> 00:05:04.650 align:start position:0% guys want to talk about what do you all want<00:05:02.650> to<00:05:02.889> talk<00:05:03.070> about<00:05:03.220> if<00:05:03.820> if<00:05:04.240> there's<00:05:04.450> anybody 00:05:04.650 --> 00:05:04.660 align:start position:0% want to talk about if if there's anybody 00:05:04.660 --> 00:05:06.840 align:start position:0% want to talk about if if there's anybody who<00:05:04.930> has<00:05:05.110> a<00:05:05.139> topic<00:05:05.710> that<00:05:05.919> relates<00:05:06.280> to<00:05:06.550> theory 00:05:06.840 --> 00:05:06.850 align:start position:0% who has a topic that relates to theory 00:05:06.850 --> 00:05:07.790 align:start position:0% who has a topic that relates to theory m1x 00:05:07.790 --> 00:05:07.800 align:start position:0% m1x 00:05:07.800 --> 00:05:11.010 align:start position:0% m1x please<00:05:08.800> come<00:05:09.010> forward<00:05:09.190> with<00:05:09.370> it<00:05:09.490> is<00:05:10.210> do<00:05:10.930> we 00:05:11.010 --> 00:05:11.020 align:start position:0% please come forward with it is do we 00:05:11.020 --> 00:05:13.650 align:start position:0% please come forward with it is do we have<00:05:11.139> something<00:05:11.320> okay<00:05:11.800> come<00:05:12.130> on<00:05:12.220> down<00:05:12.460> come<00:05:12.760> on 00:05:13.650 --> 00:05:13.660 align:start position:0% have something okay come on down come on 00:05:13.660 --> 00:05:17.190 align:start position:0% have something okay come on down come on down<00:05:13.720> I<00:05:14.460> also<00:05:15.460> have<00:05:15.760> a<00:05:15.789> topic<00:05:16.180> okay<00:05:16.630> so<00:05:17.140> you 00:05:17.190 --> 00:05:17.200 align:start position:0% down I also have a topic okay so you 00:05:17.200 --> 00:05:20.460 align:start position:0% down I also have a topic okay so you first<00:05:17.560> I'm<00:05:17.890> worried<00:05:18.400> about<00:05:18.520> the<00:05:19.470> scalability 00:05:20.460 --> 00:05:20.470 align:start position:0% first I'm worried about the scalability 00:05:20.470 --> 00:05:24.600 align:start position:0% first I'm worried about the scalability of<00:05:20.500> a<00:05:20.919> theorem<00:05:21.250> one<00:05:21.490> so<00:05:21.880> and<00:05:23.039> we<00:05:24.039> can't<00:05:24.370> even 00:05:24.600 --> 00:05:24.610 align:start position:0% of a theorem one so and we can't even 00:05:24.610 --> 00:05:29.460 align:start position:0% of a theorem one so and we can't even reprise<00:05:25.479> up<00:05:25.930> codes<00:05:27.810> without<00:05:28.810> breaking 00:05:29.460 --> 00:05:29.470 align:start position:0% reprise up codes without breaking 00:05:29.470 --> 00:05:31.200 align:start position:0% reprise up codes without breaking anything<00:05:29.710> I<00:05:30.070> mean<00:05:30.460> we<00:05:30.669> had<00:05:30.789> this<00:05:30.940> discussion 00:05:31.200 --> 00:05:31.210 align:start position:0% anything I mean we had this discussion 00:05:31.210 --> 00:05:35.430 align:start position:0% anything I mean we had this discussion with<00:05:31.600> the<00:05:31.919> 1283<00:05:32.919> I<00:05:33.190> think<00:05:33.550> it<00:05:33.640> was<00:05:33.990> the<00:05:34.990> problem 00:05:35.430 --> 00:05:35.440 align:start position:0% with the 1283 I think it was the problem 00:05:35.440 --> 00:05:37.740 align:start position:0% with the 1283 I think it was the problem and<00:05:35.620> now<00:05:36.280> we<00:05:36.340> have<00:05:36.640> the<00:05:36.820> same<00:05:37.030> problem<00:05:37.450> again 00:05:37.740 --> 00:05:37.750 align:start position:0% and now we have the same problem again 00:05:37.750 --> 00:05:42.750 align:start position:0% and now we have the same problem again with<00:05:38.580> 1884<00:05:39.660> so<00:05:40.660> as<00:05:41.140> a<00:05:41.470> developer<00:05:42.160> I<00:05:42.190> would<00:05:42.370> be 00:05:42.750 --> 00:05:42.760 align:start position:0% with 1884 so as a developer I would be 00:05:42.760 --> 00:05:44.600 align:start position:0% with 1884 so as a developer I would be really<00:05:43.120> interested<00:05:43.690> in<00:05:43.900> seeing<00:05:44.260> some 00:05:44.600 --> 00:05:44.610 align:start position:0% really interested in seeing some 00:05:44.610 --> 00:05:49.469 align:start position:0% really interested in seeing some invariants<00:05:45.610> that<00:05:46.440> I<00:05:47.440> can<00:05:48.160> work<00:05:48.370> with<00:05:48.430> so<00:05:49.210> that 00:05:49.469 --> 00:05:49.479 align:start position:0% invariants that I can work with so that 00:05:49.479 --> 00:05:51.900 align:start position:0% invariants that I can work with so that my<00:05:49.780> code<00:05:50.200> that<00:05:50.470> I<00:05:50.500> write<00:05:50.830> and<00:05:50.890> deploy<00:05:51.490> Andre 00:05:51.900 --> 00:05:51.910 align:start position:0% my code that I write and deploy Andre 00:05:51.910 --> 00:05:54.510 align:start position:0% my code that I write and deploy Andre Ethier<00:05:52.030> maenette<00:05:52.950> doesn't<00:05:53.950> break<00:05:54.160> in<00:05:54.430> the 00:05:54.510 --> 00:05:54.520 align:start position:0% Ethier maenette doesn't break in the 00:05:54.520 --> 00:05:58.230 align:start position:0% Ethier maenette doesn't break in the future<00:05:55.380> and<00:05:56.380> I<00:05:56.830> mean<00:05:57.070> in<00:05:57.220> the<00:05:57.700> case<00:05:57.729> of<00:05:58.090> the 00:05:58.230 --> 00:05:58.240 align:start position:0% future and I mean in the case of the 00:05:58.240 --> 00:05:59.840 align:start position:0% future and I mean in the case of the 1283 00:05:59.840 --> 00:05:59.850 align:start position:0% 1283 00:05:59.850 --> 00:06:03.870 align:start position:0% 1283 the<00:06:00.850> developers<00:06:01.630> weren't<00:06:02.250> following<00:06:03.250> best 00:06:03.870 --> 00:06:03.880 align:start position:0% the developers weren't following best 00:06:03.880 --> 00:06:08.219 align:start position:0% the developers weren't following best practices<00:06:04.080> but<00:06:05.080> now<00:06:05.289> in<00:06:05.530> this<00:06:05.970> 1884<00:06:06.970> case<00:06:07.270> yeah 00:06:08.219 --> 00:06:08.229 align:start position:0% practices but now in this 1884 case yeah 00:06:08.229 --> 00:06:11.040 align:start position:0% practices but now in this 1884 case yeah people<00:06:08.950> wrote<00:06:09.220> code<00:06:09.580> they<00:06:10.240> followed<00:06:10.690> every 00:06:11.040 --> 00:06:11.050 align:start position:0% people wrote code they followed every 00:06:11.050 --> 00:06:14.550 align:start position:0% people wrote code they followed every guideline<00:06:11.470> that<00:06:11.830> was<00:06:12.550> there<00:06:12.820> and<00:06:13.120> now<00:06:13.560> the 00:06:14.550 --> 00:06:14.560 align:start position:0% guideline that was there and now the 00:06:14.560 --> 00:06:17.339 align:start position:0% guideline that was there and now the code<00:06:14.770> breaks<00:06:15.450> so<00:06:16.450> yeah<00:06:16.600> I<00:06:16.630> can<00:06:16.990> kind<00:06:17.169> of<00:06:17.200> give<00:06:17.320> a 00:06:17.339 --> 00:06:17.349 align:start position:0% code breaks so yeah I can kind of give a 00:06:17.349 --> 00:06:19.380 align:start position:0% code breaks so yeah I can kind of give a quick<00:06:17.590> intro<00:06:17.919> to<00:06:17.950> this<00:06:18.190> before<00:06:18.430> we<00:06:18.849> have<00:06:19.120> some 00:06:19.380 --> 00:06:19.390 align:start position:0% quick intro to this before we have some 00:06:19.390 --> 00:06:20.310 align:start position:0% quick intro to this before we have some comment<00:06:19.780> from<00:06:19.900> some<00:06:20.080> of<00:06:20.169> the<00:06:20.229> other 00:06:20.310 --> 00:06:20.320 align:start position:0% comment from some of the other 00:06:20.320 --> 00:06:21.060 align:start position:0% comment from some of the other developers 00:06:21.060 --> 00:06:21.070 align:start position:0% developers 00:06:21.070 --> 00:06:24.900 align:start position:0% developers but<00:06:21.190> we<00:06:21.820> had<00:06:22.000> an<00:06:22.120> EIP<00:06:22.330> and<00:06:22.840> basically<00:06:23.620> in<00:06:24.610> order 00:06:24.900 --> 00:06:24.910 align:start position:0% but we had an EIP and basically in order 00:06:24.910 --> 00:06:28.170 align:start position:0% but we had an EIP and basically in order to<00:06:25.090> make<00:06:25.960> it<00:06:26.170> the<00:06:26.470> blockchain<00:06:26.890> a<00:06:27.160> bit<00:06:27.400> safer<00:06:27.940> to 00:06:28.170 --> 00:06:28.180 align:start position:0% to make it the blockchain a bit safer to 00:06:28.180 --> 00:06:29.940 align:start position:0% to make it the blockchain a bit safer to prevent<00:06:28.510> from<00:06:28.750> and<00:06:29.080> please<00:06:29.440> correct<00:06:29.830> me 00:06:29.940 --> 00:06:29.950 align:start position:0% prevent from and please correct me 00:06:29.950 --> 00:06:32.160 align:start position:0% prevent from and please correct me because<00:06:30.010> I'm<00:06:30.190> gonna<00:06:30.310> butcher<00:06:30.580> this<00:06:30.880> from<00:06:31.480> like 00:06:32.160 --> 00:06:32.170 align:start position:0% because I'm gonna butcher this from like 00:06:32.170 --> 00:06:35.940 align:start position:0% because I'm gonna butcher this from like DDoS<00:06:32.680> attacks<00:06:33.010> we<00:06:34.080> repriced<00:06:35.080> an<00:06:35.260> opcode<00:06:35.440> and 00:06:35.940 --> 00:06:35.950 align:start position:0% DDoS attacks we repriced an opcode and 00:06:35.950 --> 00:06:38.070 align:start position:0% DDoS attacks we repriced an opcode and in<00:06:36.280> repricing<00:06:36.760> that<00:06:37.060> opcode<00:06:37.600> if<00:06:37.810> you<00:06:37.900> have<00:06:38.050> a 00:06:38.070 --> 00:06:38.080 align:start position:0% in repricing that opcode if you have a 00:06:38.080 --> 00:06:39.960 align:start position:0% in repricing that opcode if you have a smart<00:06:38.440> contract<00:06:38.650> that<00:06:39.190> relies<00:06:39.580> on<00:06:39.610> that 00:06:39.960 --> 00:06:39.970 align:start position:0% smart contract that relies on that 00:06:39.970 --> 00:06:42.300 align:start position:0% smart contract that relies on that opcode<00:06:40.480> being<00:06:40.750> a<00:06:40.900> certain<00:06:41.200> price<00:06:41.500> that 00:06:42.300 --> 00:06:42.310 align:start position:0% opcode being a certain price that 00:06:42.310 --> 00:06:45.360 align:start position:0% opcode being a certain price that contract<00:06:42.910> may<00:06:43.180> break<00:06:43.530> there<00:06:44.530> was<00:06:44.680> a<00:06:44.920> bunch<00:06:45.250> of 00:06:45.360 --> 00:06:45.370 align:start position:0% contract may break there was a bunch of 00:06:45.370 --> 00:06:47.220 align:start position:0% contract may break there was a bunch of contracts<00:06:45.940> that<00:06:46.060> have<00:06:46.120> upgradability<00:06:47.020> I 00:06:47.220 --> 00:06:47.230 align:start position:0% contracts that have upgradability I 00:06:47.230 --> 00:06:49.260 align:start position:0% contracts that have upgradability I believe<00:06:47.620> Aragon<00:06:48.040> was<00:06:48.070> one<00:06:48.370> of<00:06:48.460> them<00:06:48.550> and<00:06:48.730> those 00:06:49.260 --> 00:06:49.270 align:start position:0% believe Aragon was one of them and those 00:06:49.270 --> 00:06:51.390 align:start position:0% believe Aragon was one of them and those are<00:06:50.020> gonna<00:06:50.230> be<00:06:50.410> able<00:06:50.500> to<00:06:50.620> be<00:06:50.770> upgraded<00:06:51.310> but 00:06:51.390 --> 00:06:51.400 align:start position:0% are gonna be able to be upgraded but 00:06:51.400 --> 00:06:53.130 align:start position:0% are gonna be able to be upgraded but it's<00:06:51.520> a<00:06:51.580> little<00:06:51.790> bit<00:06:51.880> annoying<00:06:52.180> there's<00:06:52.870> other 00:06:53.130 --> 00:06:53.140 align:start position:0% it's a little bit annoying there's other 00:06:53.140 --> 00:06:55.200 align:start position:0% it's a little bit annoying there's other contracts<00:06:53.740> that<00:06:53.980> may<00:06:54.310> have<00:06:54.610> the<00:06:54.640> effect<00:06:55.060> of 00:06:55.200 --> 00:06:55.210 align:start position:0% contracts that may have the effect of 00:06:55.210 --> 00:06:57.300 align:start position:0% contracts that may have the effect of having<00:06:55.330> funds<00:06:55.750> locked<00:06:56.080> in<00:06:56.290> them<00:06:56.470> that's<00:06:57.220> a 00:06:57.300 --> 00:06:57.310 align:start position:0% having funds locked in them that's a 00:06:57.310 --> 00:06:58.950 align:start position:0% having funds locked in them that's a little<00:06:57.460> bit<00:06:57.610> scary<00:06:57.730> of<00:06:58.060> a<00:06:58.120> term<00:06:58.390> so<00:06:58.690> what<00:06:58.840> we 00:06:58.950 --> 00:06:58.960 align:start position:0% little bit scary of a term so what we 00:06:58.960 --> 00:07:00.990 align:start position:0% little bit scary of a term so what we did<00:06:59.140> is<00:06:59.380> in<00:06:59.680> order<00:06:59.950> to<00:07:00.160> prevent<00:07:00.700> this<00:07:00.940> from 00:07:00.990 --> 00:07:01.000 align:start position:0% did is in order to prevent this from 00:07:01.000 --> 00:07:02.850 align:start position:0% did is in order to prevent this from being<00:07:01.450> another<00:07:01.780> scenario<00:07:02.350> where<00:07:02.560> it's<00:07:02.680> like 00:07:02.850 --> 00:07:02.860 align:start position:0% being another scenario where it's like 00:07:02.860 --> 00:07:04.860 align:start position:0% being another scenario where it's like we<00:07:03.460> can't<00:07:03.730> get<00:07:03.850> our<00:07:03.940> funds<00:07:04.210> out<00:07:04.450> things<00:07:04.750> like 00:07:04.860 --> 00:07:04.870 align:start position:0% we can't get our funds out things like 00:07:04.870 --> 00:07:07.140 align:start position:0% we can't get our funds out things like that<00:07:05.230> what<00:07:05.590> we<00:07:05.680> determined<00:07:06.250> was<00:07:06.430> if<00:07:06.940> people 00:07:07.140 --> 00:07:07.150 align:start position:0% that what we determined was if people 00:07:07.150 --> 00:07:09.090 align:start position:0% that what we determined was if people come<00:07:07.540> to<00:07:07.750> us<00:07:07.900> after<00:07:08.110> we<00:07:08.350> implement<00:07:08.740> the<00:07:08.800> CIP 00:07:09.090 --> 00:07:09.100 align:start position:0% come to us after we implement the CIP 00:07:09.100 --> 00:07:12.870 align:start position:0% come to us after we implement the CIP and<00:07:09.550> they<00:07:10.450> say<00:07:10.750> something<00:07:11.410> like<00:07:11.560> hey<00:07:12.370> this<00:07:12.700> is 00:07:12.870 --> 00:07:12.880 align:start position:0% and they say something like hey this is 00:07:12.880 --> 00:07:15.120 align:start position:0% and they say something like hey this is you<00:07:13.240> know<00:07:13.360> messing<00:07:13.720> my<00:07:13.990> contract<00:07:14.620> up<00:07:14.800> we're 00:07:15.120 --> 00:07:15.130 align:start position:0% you know messing my contract up we're 00:07:15.130 --> 00:07:16.980 align:start position:0% you know messing my contract up we're going<00:07:15.280> to<00:07:15.430> research<00:07:16.150> and<00:07:16.330> come<00:07:16.510> up<00:07:16.720> with<00:07:16.960> a 00:07:16.980 --> 00:07:16.990 align:start position:0% going to research and come up with a 00:07:16.990 --> 00:07:19.470 align:start position:0% going to research and come up with a solution<00:07:17.500> to<00:07:17.890> work<00:07:18.070> around<00:07:18.250> so<00:07:19.000> that<00:07:19.120> they<00:07:19.210> can 00:07:19.470 --> 00:07:19.480 align:start position:0% solution to work around so that they can 00:07:19.480 --> 00:07:21.510 align:start position:0% solution to work around so that they can have<00:07:20.050> their<00:07:20.200> contracts<00:07:20.710> work<00:07:20.950> again<00:07:21.310> and 00:07:21.510 --> 00:07:21.520 align:start position:0% have their contracts work again and 00:07:21.520 --> 00:07:23.340 align:start position:0% have their contracts work again and those<00:07:21.760> limited<00:07:22.180> amount<00:07:22.390> of<00:07:22.450> cases<00:07:22.990> do<00:07:23.140> I<00:07:23.170> get 00:07:23.340 --> 00:07:23.350 align:start position:0% those limited amount of cases do I get 00:07:23.350 --> 00:07:25.650 align:start position:0% those limited amount of cases do I get that<00:07:23.530> I'm<00:07:23.770> almost<00:07:23.920> right<00:07:24.310> okay<00:07:24.610> yeah<00:07:25.360> Martin 00:07:25.650 --> 00:07:25.660 align:start position:0% that I'm almost right okay yeah Martin 00:07:25.660 --> 00:07:27.120 align:start position:0% that I'm almost right okay yeah Martin can<00:07:25.870> also<00:07:25.990> comment<00:07:26.350> a<00:07:26.530> little<00:07:26.680> bit<00:07:26.800> more<00:07:27.010> on 00:07:27.120 --> 00:07:27.130 align:start position:0% can also comment a little bit more on 00:07:27.130 --> 00:07:29.310 align:start position:0% can also comment a little bit more on that 00:07:29.310 --> 00:07:29.320 align:start position:0% 00:07:29.320 --> 00:07:32.820 align:start position:0% yeah<00:07:30.190> and<00:07:30.490> you<00:07:30.880> brought<00:07:31.060> up<00:07:31.270> two<00:07:31.510> cases<00:07:31.960> 1283 00:07:32.820 --> 00:07:32.830 align:start position:0% yeah and you brought up two cases 1283 00:07:32.830 --> 00:07:36.210 align:start position:0% yeah and you brought up two cases 1283 and<00:07:33.250> 1884<00:07:34.000> and<00:07:34.450> they're<00:07:34.720> kind<00:07:35.560> of<00:07:35.650> different 00:07:36.210 --> 00:07:36.220 align:start position:0% and 1884 and they're kind of different 00:07:36.220 --> 00:07:40.650 align:start position:0% and 1884 and they're kind of different because<00:07:36.970> 1283<00:07:37.780> was<00:07:38.500> made<00:07:38.920> to<00:07:39.730> improve<00:07:40.210> the 00:07:40.650 --> 00:07:40.660 align:start position:0% because 1283 was made to improve the 00:07:40.660 --> 00:07:43.650 align:start position:0% because 1283 was made to improve the life<00:07:40.810> of<00:07:41.110> deaf<00:07:41.740> developers<00:07:42.480> making<00:07:43.480> it 00:07:43.650 --> 00:07:43.660 align:start position:0% life of deaf developers making it 00:07:43.660 --> 00:07:51.420 align:start position:0% life of deaf developers making it cheaper<00:07:46.590> whereas<00:07:48.420> 1884<00:07:49.710> has<00:07:50.710> been<00:07:50.980> added<00:07:51.280> as 00:07:51.420 --> 00:07:51.430 align:start position:0% cheaper whereas 1884 has been added as 00:07:51.430 --> 00:07:53.780 align:start position:0% cheaper whereas 1884 has been added as basically<00:07:51.970> a<00:07:52.060> security<00:07:52.540> precaution<00:07:53.110> because 00:07:53.780 --> 00:07:53.790 align:start position:0% basically a security precaution because 00:07:53.790 --> 00:07:58.620 align:start position:0% basically a security precaution because to<00:07:54.790> rebalance<00:07:55.410> the<00:07:56.410> opcodes<00:07:56.860> and<00:07:57.270> the<00:07:58.270> former 00:07:58.620 --> 00:07:58.630 align:start position:0% to rebalance the opcodes and the former 00:07:58.630 --> 00:08:01.140 align:start position:0% to rebalance the opcodes and the former one<00:07:58.810> we<00:07:59.050> skip<00:07:59.110> that<00:07:59.680> so<00:08:00.460> it's<00:08:00.670> not<00:08:00.820> to<00:08:00.940> break 00:08:01.140 --> 00:08:01.150 align:start position:0% one we skip that so it's not to break 00:08:01.150 --> 00:08:05.460 align:start position:0% one we skip that so it's not to break stuff<00:08:02.730> it's<00:08:03.730> being<00:08:04.060> implemented<00:08:04.750> now<00:08:05.110> again 00:08:05.460 --> 00:08:05.470 align:start position:0% stuff it's being implemented now again 00:08:05.470 --> 00:08:09.840 align:start position:0% stuff it's being implemented now again in<00:08:05.680> the<00:08:05.710> form<00:08:06.010> of<00:08:06.130> e<00:08:06.330> 2200<00:08:07.530> but<00:08:08.530> with<00:08:08.800> a<00:08:09.010> minor 00:08:09.840 --> 00:08:09.850 align:start position:0% in the form of e 2200 but with a minor 00:08:09.850 --> 00:08:12.230 align:start position:0% in the form of e 2200 but with a minor modification<00:08:10.330> so<00:08:11.290> that<00:08:11.470> it<00:08:11.620> won't<00:08:11.770> start 00:08:12.230 --> 00:08:12.240 align:start position:0% modification so that it won't start 00:08:12.240 --> 00:08:15.120 align:start position:0% modification so that it won't start introducing<00:08:13.240> new<00:08:13.710> vulnerabilities<00:08:14.710> into 00:08:15.120 --> 00:08:15.130 align:start position:0% introducing new vulnerabilities into 00:08:15.130 --> 00:08:20.820 align:start position:0% introducing new vulnerabilities into contract<00:08:16.080> and<00:08:17.080> in<00:08:17.500> general<00:08:18.070> the<00:08:18.640> idea<00:08:19.830> that 00:08:20.820 --> 00:08:20.830 align:start position:0% contract and in general the idea that 00:08:20.830 --> 00:08:22.770 align:start position:0% contract and in general the idea that has<00:08:21.070> been<00:08:21.220> floating<00:08:21.610> around<00:08:21.670> a<00:08:21.970> lot<00:08:22.150> is<00:08:22.570> that 00:08:22.770 --> 00:08:22.780 align:start position:0% has been floating around a lot is that 00:08:22.780 --> 00:08:25.440 align:start position:0% has been floating around a lot is that if<00:08:22.900> we<00:08:23.050> do<00:08:23.290> changes<00:08:24.040> to<00:08:24.190> the<00:08:24.310> EVM<00:08:24.670> we<00:08:25.120> will<00:08:25.330> also 00:08:25.440 --> 00:08:25.450 align:start position:0% if we do changes to the EVM we will also 00:08:25.450 --> 00:08:28.530 align:start position:0% if we do changes to the EVM we will also do<00:08:25.720> versioning<00:08:26.290> so<00:08:26.980> that<00:08:27.220> these<00:08:28.030> new<00:08:28.300> features 00:08:28.530 --> 00:08:28.540 align:start position:0% do versioning so that these new features 00:08:28.540 --> 00:08:34.290 align:start position:0% do versioning so that these new features will<00:08:29.080> be<00:08:29.110> opted<00:08:29.919> in<00:08:30.570> however<00:08:31.570> it<00:08:32.500> really<00:08:33.010> makes 00:08:34.290 --> 00:08:34.300 align:start position:0% will be opted in however it really makes 00:08:34.300 --> 00:08:37.380 align:start position:0% will be opted in however it really makes really<00:08:34.539> kind<00:08:34.810> of<00:08:34.959> makes<00:08:35.860> no<00:08:36.039> sense<00:08:36.459> to<00:08:37.120> have 00:08:37.380 --> 00:08:37.390 align:start position:0% really kind of makes no sense to have 00:08:37.390 --> 00:08:41.279 align:start position:0% really kind of makes no sense to have opt-in<00:08:38.190> features<00:08:39.330> for<00:08:40.330> security<00:08:40.870> features 00:08:41.279 --> 00:08:41.289 align:start position:0% opt-in features for security features 00:08:41.289 --> 00:08:44.300 align:start position:0% opt-in features for security features where<00:08:41.860> we<00:08:42.039> want<00:08:42.250> to<00:08:42.370> protect<00:08:43.120> the<00:08:43.209> base<00:08:43.390> layer 00:08:44.300 --> 00:08:44.310 align:start position:0% where we want to protect the base layer 00:08:44.310 --> 00:08:48.210 align:start position:0% where we want to protect the base layer so<00:08:45.310> thus<00:08:45.670> we're<00:08:45.910> all<00:08:46.060> out<00:08:46.209> 1884<00:08:46.990> and<00:08:47.890> the<00:08:48.010> thing 00:08:48.210 --> 00:08:48.220 align:start position:0% so thus we're all out 1884 and the thing 00:08:48.220 --> 00:08:49.980 align:start position:0% so thus we're all out 1884 and the thing is<00:08:48.339> this<00:08:48.519> will<00:08:48.730> affect<00:08:49.060> a<00:08:49.209> lot<00:08:49.330> of<00:08:49.360> contracts 00:08:49.980 --> 00:08:49.990 align:start position:0% is this will affect a lot of contracts 00:08:49.990 --> 00:08:53.610 align:start position:0% is this will affect a lot of contracts but<00:08:50.560> in<00:08:51.040> the<00:08:51.550> large<00:08:52.029> majority<00:08:52.480> of<00:08:52.660> cases<00:08:52.720> it 00:08:53.610 --> 00:08:53.620 align:start position:0% but in the large majority of cases it 00:08:53.620 --> 00:08:57.840 align:start position:0% but in the large majority of cases it will<00:08:54.279> only<00:08:54.839> mind<00:08:55.839> affect<00:08:56.560> them<00:08:56.800> a<00:08:57.040> little<00:08:57.700> bit 00:08:57.840 --> 00:08:57.850 align:start position:0% will only mind affect them a little bit 00:08:57.850 --> 00:09:01.530 align:start position:0% will only mind affect them a little bit like<00:08:58.540> most<00:08:59.170> use<00:08:59.620> cases<00:08:59.950> that<00:09:00.430> are<00:09:01.060> affected 00:09:01.530 --> 00:09:01.540 align:start position:0% like most use cases that are affected 00:09:01.540 --> 00:09:03.889 align:start position:0% like most use cases that are affected can<00:09:01.810> be<00:09:01.959> solved<00:09:02.410> by<00:09:02.470> adding<00:09:02.740> a<00:09:02.950> bit<00:09:03.070> more<00:09:03.130> gas 00:09:03.889 --> 00:09:03.899 align:start position:0% can be solved by adding a bit more gas 00:09:03.899 --> 00:09:09.690 align:start position:0% can be solved by adding a bit more gas at<00:09:04.899> the<00:09:05.019> beginning<00:09:05.700> and<00:09:07.170> I<00:09:08.430> think<00:09:09.430> that<00:09:09.579> would 00:09:09.690 --> 00:09:09.700 align:start position:0% at the beginning and I think that would 00:09:09.700 --> 00:09:12.120 align:start position:0% at the beginning and I think that would cover<00:09:09.880> like<00:09:10.120> 95%<00:09:10.899> of<00:09:11.410> all<00:09:11.500> the<00:09:11.560> cases<00:09:11.950> where 00:09:12.120 --> 00:09:12.130 align:start position:0% cover like 95% of all the cases where 00:09:12.130 --> 00:09:14.610 align:start position:0% cover like 95% of all the cases where it's<00:09:12.360> going<00:09:13.360> to<00:09:13.390> be<00:09:13.480> affected<00:09:13.899> but<00:09:14.290> then<00:09:14.470> there 00:09:14.610 --> 00:09:14.620 align:start position:0% it's going to be affected but then there 00:09:14.620 --> 00:09:17.400 align:start position:0% it's going to be affected but then there are<00:09:14.709> some<00:09:15.040> particular<00:09:15.850> use<00:09:16.329> particular<00:09:17.050> flows 00:09:17.400 --> 00:09:17.410 align:start position:0% are some particular use particular flows 00:09:17.410 --> 00:09:21.150 align:start position:0% are some particular use particular flows where<00:09:18.279> it's<00:09:18.399> already<00:09:18.779> encoded<00:09:19.779> that<00:09:20.140> it's<00:09:20.560> an 00:09:21.150 --> 00:09:21.160 align:start position:0% where it's already encoded that it's an 00:09:21.160 --> 00:09:23.639 align:start position:0% where it's already encoded that it's an automated<00:09:21.640> transfer<00:09:22.480> into<00:09:23.050> something<00:09:23.500> else 00:09:23.639 --> 00:09:23.649 align:start position:0% automated transfer into something else 00:09:23.649 --> 00:09:28.980 align:start position:0% automated transfer into something else and<00:09:23.980> that<00:09:24.899> flow<00:09:25.899> between<00:09:26.170> two<00:09:26.790> contracts<00:09:27.990> can 00:09:28.980 --> 00:09:28.990 align:start position:0% and that flow between two contracts can 00:09:28.990 --> 00:09:31.350 align:start position:0% and that flow between two contracts can thus<00:09:29.170> be<00:09:29.200> broken<00:09:30.010> in<00:09:30.310> a<00:09:30.700> way<00:09:30.730> that<00:09:31.060> is<00:09:31.180> not 00:09:31.350 --> 00:09:31.360 align:start position:0% thus be broken in a way that is not 00:09:31.360 --> 00:09:36.620 align:start position:0% thus be broken in a way that is not fixable<00:09:32.430> and<00:09:33.600> I<00:09:34.600> mean<00:09:34.870> not<00:09:35.079> fixable<00:09:35.620> by<00:09:36.430> the 00:09:36.620 --> 00:09:36.630 align:start position:0% fixable and I mean not fixable by the 00:09:36.630 --> 00:09:39.449 align:start position:0% fixable and I mean not fixable by the initiator<00:09:37.630> of<00:09:37.810> the<00:09:38.110> of<00:09:38.290> the<00:09:38.410> transfer<00:09:38.800> or<00:09:38.980> the 00:09:39.449 --> 00:09:39.459 align:start position:0% initiator of the of the transfer or the 00:09:39.459 --> 00:09:44.370 align:start position:0% initiator of the of the transfer or the operation<00:09:40.000> and<00:09:41.970> so<00:09:42.970> that<00:09:43.240> much<00:09:43.480> has<00:09:43.930> been<00:09:44.170> you 00:09:44.370 --> 00:09:44.380 align:start position:0% operation and so that much has been you 00:09:44.380 --> 00:09:46.290 align:start position:0% operation and so that much has been you know<00:09:44.440> we<00:09:44.800> know<00:09:44.950> that<00:09:44.980> this<00:09:45.399> might<00:09:45.970> break 00:09:46.290 --> 00:09:46.300 align:start position:0% know we know that this might break 00:09:46.300 --> 00:09:49.260 align:start position:0% know we know that this might break things<00:09:46.570> the<00:09:47.290> question<00:09:47.770> is<00:09:47.920> how<00:09:48.310> hard<00:09:48.790> will<00:09:49.089> it 00:09:49.260 --> 00:09:49.270 align:start position:0% things the question is how hard will it 00:09:49.270 --> 00:09:52.440 align:start position:0% things the question is how hard will it break<00:09:49.510> and<00:09:49.959> and<00:09:50.829> how<00:09:51.130> much<00:09:51.370> pain<00:09:51.790> will<00:09:52.300> it 00:09:52.440 --> 00:09:52.450 align:start position:0% break and and how much pain will it 00:09:52.450 --> 00:09:57.440 align:start position:0% break and and how much pain will it bring<00:09:53.610> because<00:09:54.610> I<00:09:54.820> think<00:09:55.360> that<00:09:55.720> in<00:09:55.899> many<00:09:56.079> cases 00:09:57.440 --> 00:09:57.450 align:start position:0% bring because I think that in many cases 00:09:57.450 --> 00:09:59.790 align:start position:0% bring because I think that in many cases contracts<00:09:58.450> are<00:09:58.570> actually<00:09:58.959> upgradeable<00:09:59.560> and 00:09:59.790 --> 00:09:59.800 align:start position:0% contracts are actually upgradeable and 00:09:59.800 --> 00:10:01.740 align:start position:0% contracts are actually upgradeable and if<00:10:00.339> you<00:10:00.459> have<00:10:00.610> a<00:10:00.640> set<00:10:00.850> of<00:10:00.880> contracts<00:10:01.540> which 00:10:01.740 --> 00:10:01.750 align:start position:0% if you have a set of contracts which 00:10:01.750 --> 00:10:03.480 align:start position:0% if you have a set of contracts which suffer<00:10:02.230> from<00:10:02.350> this<00:10:02.589> you<00:10:03.160> can<00:10:03.339> actually 00:10:03.480 --> 00:10:03.490 align:start position:0% suffer from this you can actually 00:10:03.490 --> 00:10:07.319 align:start position:0% suffer from this you can actually redeploy<00:10:04.209> it<00:10:04.420> and<00:10:04.720> fix<00:10:05.350> it<00:10:05.500> that<00:10:05.560> way<00:10:06.329> which 00:10:07.319 --> 00:10:07.329 align:start position:0% redeploy it and fix it that way which 00:10:07.329 --> 00:10:10.410 align:start position:0% redeploy it and fix it that way which further<00:10:08.320> brings<00:10:08.709> down<00:10:09.040> the<00:10:09.459> number<00:10:09.820> of<00:10:09.940> actual 00:10:10.410 --> 00:10:10.420 align:start position:0% further brings down the number of actual 00:10:10.420 --> 00:10:14.100 align:start position:0% further brings down the number of actual broken<00:10:10.660> flows<00:10:11.110> and<00:10:11.829> if<00:10:12.040> there<00:10:12.480> if<00:10:13.480> it<00:10:13.750> can<00:10:13.990> be 00:10:14.100 --> 00:10:14.110 align:start position:0% broken flows and if there if it can be 00:10:14.110 --> 00:10:15.960 align:start position:0% broken flows and if there if it can be evidenced<00:10:14.680> later<00:10:14.890> on<00:10:15.100> that<00:10:15.430> hey<00:10:15.640> we<00:10:15.820> have 00:10:15.960 --> 00:10:15.970 align:start position:0% evidenced later on that hey we have 00:10:15.970 --> 00:10:18.510 align:start position:0% evidenced later on that hey we have actually<00:10:16.390> these<00:10:17.110> particular<00:10:17.890> instances 00:10:18.510 --> 00:10:18.520 align:start position:0% actually these particular instances 00:10:18.520 --> 00:10:22.769 align:start position:0% actually these particular instances which<00:10:19.360> are<00:10:19.740> broken<00:10:20.740> cannot<00:10:21.550> be<00:10:21.760> upgraded<00:10:21.910> and 00:10:22.769 --> 00:10:22.779 align:start position:0% which are broken cannot be upgraded and 00:10:22.779 --> 00:10:26.370 align:start position:0% which are broken cannot be upgraded and cannot<00:10:23.770> be<00:10:23.920> salvaged<00:10:24.430> in<00:10:24.610> any<00:10:24.820> way<00:10:25.110> then<00:10:26.110> we 00:10:26.370 --> 00:10:26.380 align:start position:0% cannot be salvaged in any way then we 00:10:26.380 --> 00:10:28.470 align:start position:0% cannot be salvaged in any way then we can<00:10:26.560> look<00:10:26.709> at<00:10:26.860> okay<00:10:27.100> so<00:10:27.130> what<00:10:27.490> fixes<00:10:28.120> are 00:10:28.470 --> 00:10:28.480 align:start position:0% can look at okay so what fixes are 00:10:28.480 --> 00:10:31.019 align:start position:0% can look at okay so what fixes are needed<00:10:28.870> to<00:10:29.410> solve<00:10:29.680> these<00:10:29.980> instances<00:10:30.760> and 00:10:31.019 --> 00:10:31.029 align:start position:0% needed to solve these instances and 00:10:31.029 --> 00:10:36.720 align:start position:0% needed to solve these instances and there<00:10:31.420> are<00:10:31.540> a<00:10:31.600> couple<00:10:31.930> of<00:10:32.339> ways<00:10:34.740> that<00:10:35.740> may<00:10:36.130> help 00:10:36.720 --> 00:10:36.730 align:start position:0% there are a couple of ways that may help 00:10:36.730 --> 00:10:39.269 align:start position:0% there are a couple of ways that may help in<00:10:37.089> most<00:10:37.630> of<00:10:37.810> them<00:10:37.930> I<00:10:37.959> think<00:10:38.320> in<00:10:38.680> for<00:10:38.920> example 00:10:39.269 --> 00:10:39.279 align:start position:0% in most of them I think in for example 00:10:39.279 --> 00:10:42.480 align:start position:0% in most of them I think in for example if<00:10:39.370> we<00:10:39.550> lower<00:10:39.790> the<00:10:40.000> cost<00:10:40.240> of<00:10:40.480> a<00:10:40.630> location<00:10:41.490> that 00:10:42.480 --> 00:10:42.490 align:start position:0% if we lower the cost of a location that 00:10:42.490 --> 00:10:45.360 align:start position:0% if we lower the cost of a location that will<00:10:42.699> solve<00:10:42.940> a<00:10:43.060> lot<00:10:43.180> of<00:10:43.209> the<00:10:43.449> issues<00:10:44.250> but<00:10:45.250> it 00:10:45.360 --> 00:10:45.370 align:start position:0% will solve a lot of the issues but it 00:10:45.370 --> 00:10:47.860 align:start position:0% will solve a lot of the issues but it remains<00:10:45.760> to<00:10:45.880> be<00:10:45.940> seen<00:10:46.029> exactly<00:10:46.740> what 00:10:47.860 --> 00:10:47.870 align:start position:0% remains to be seen exactly what 00:10:47.870 --> 00:10:50.910 align:start position:0% remains to be seen exactly what kind<00:10:48.200> of<00:10:48.290> patches<00:10:48.830> will<00:10:49.279> be<00:10:49.460> needed<00:10:49.790> for<00:10:50.600> the 00:10:50.910 --> 00:10:50.920 align:start position:0% kind of patches will be needed for the 00:10:50.920 --> 00:10:54.220 align:start position:0% kind of patches will be needed for the yeah<00:10:51.920> to<00:10:52.190> get<00:10:52.339> the<00:10:52.430> maximum<00:10:52.940> coverage<00:10:53.300> or<00:10:53.990> the 00:10:54.220 --> 00:10:54.230 align:start position:0% yeah to get the maximum coverage or the 00:10:54.230 --> 00:10:56.829 align:start position:0% yeah to get the maximum coverage or the rescuing<00:10:54.680> or<00:10:54.920> what<00:10:55.490> you<00:10:55.550> want<00:10:55.700> to<00:10:55.760> call<00:10:55.880> so 00:10:56.829 --> 00:10:56.839 align:start position:0% rescuing or what you want to call so 00:10:56.839 --> 00:10:58.480 align:start position:0% rescuing or what you want to call so maybe<00:10:57.110> just<00:10:57.470> a<00:10:57.620> step<00:10:57.830> back<00:10:58.040> I<00:10:58.190> thought<00:10:58.370> it 00:10:58.480 --> 00:10:58.490 align:start position:0% maybe just a step back I thought it 00:10:58.490 --> 00:10:59.740 align:start position:0% maybe just a step back I thought it might<00:10:58.640> be<00:10:58.670> useful<00:10:58.910> to<00:10:59.120> just<00:10:59.210> offer<00:10:59.510> an 00:10:59.740 --> 00:10:59.750 align:start position:0% might be useful to just offer an 00:10:59.750 --> 00:11:02.860 align:start position:0% might be useful to just offer an introduction<00:11:00.350> as<00:11:00.620> to<00:11:00.650> like<00:11:01.130> the<00:11:01.820> specific<00:11:02.450> and 00:11:02.860 --> 00:11:02.870 align:start position:0% introduction as to like the specific and 00:11:02.870 --> 00:11:05.290 align:start position:0% introduction as to like the specific and if<00:11:03.080> gas<00:11:03.440> cost<00:11:03.770> increase<00:11:04.670> in<00:11:04.880> some<00:11:05.089> of<00:11:05.210> the 00:11:05.290 --> 00:11:05.300 align:start position:0% if gas cost increase in some of the 00:11:05.300 --> 00:11:09.370 align:start position:0% if gas cost increase in some of the security<00:11:05.510> background<00:11:05.870> around<00:11:06.260> it<00:11:06.670> so<00:11:08.110> it's<00:11:09.110> a 00:11:09.370 --> 00:11:09.380 align:start position:0% security background around it so it's a 00:11:09.380 --> 00:11:12.310 align:start position:0% security background around it so it's a kind<00:11:09.589> of<00:11:09.710> general<00:11:10.339> fact<00:11:10.760> in<00:11:11.180> a<00:11:11.480> theory<00:11:11.900> so<00:11:12.170> in 00:11:12.310 --> 00:11:12.320 align:start position:0% kind of general fact in a theory so in 00:11:12.320 --> 00:11:13.750 align:start position:0% kind of general fact in a theory so in aetherium<00:11:12.740> we<00:11:12.860> have<00:11:12.980> different<00:11:13.310> kinds<00:11:13.550> of<00:11:13.610> op 00:11:13.750 --> 00:11:13.760 align:start position:0% aetherium we have different kinds of op 00:11:13.760 --> 00:11:15.040 align:start position:0% aetherium we have different kinds of op codes<00:11:14.000> we<00:11:14.210> have<00:11:14.240> op<00:11:14.540> codes<00:11:14.810> that<00:11:14.930> do 00:11:15.040 --> 00:11:15.050 align:start position:0% codes we have op codes that do 00:11:15.050 --> 00:11:18.700 align:start position:0% codes we have op codes that do computation<00:11:15.800> add<00:11:16.070> divide<00:11:16.970> subtract<00:11:17.710> elliptic 00:11:18.700 --> 00:11:18.710 align:start position:0% computation add divide subtract elliptic 00:11:18.710 --> 00:11:21.820 align:start position:0% computation add divide subtract elliptic curve<00:11:18.890> pairing<00:11:19.400> and<00:11:19.760> so<00:11:19.880> forth<00:11:20.180> we<00:11:20.360> have<00:11:20.830> and 00:11:21.820 --> 00:11:21.830 align:start position:0% curve pairing and so forth we have and 00:11:21.830 --> 00:11:24.700 align:start position:0% curve pairing and so forth we have and we<00:11:22.370> have<00:11:22.550> data<00:11:22.820> and<00:11:23.210> we<00:11:23.870> have<00:11:23.900> op<00:11:24.230> codes<00:11:24.470> that 00:11:24.700 --> 00:11:24.710 align:start position:0% we have data and we have op codes that 00:11:24.710 --> 00:11:26.740 align:start position:0% we have data and we have op codes that do<00:11:24.920> disk<00:11:25.190> i/o<00:11:25.400> so<00:11:25.760> basically<00:11:26.089> op<00:11:26.330> codes<00:11:26.630> that 00:11:26.740 --> 00:11:26.750 align:start position:0% do disk i/o so basically op codes that 00:11:26.750 --> 00:11:28.690 align:start position:0% do disk i/o so basically op codes that read<00:11:26.960> from<00:11:27.200> read<00:11:27.529> from<00:11:27.740> contract<00:11:28.190> balances 00:11:28.690 --> 00:11:28.700 align:start position:0% read from read from contract balances 00:11:28.700 --> 00:11:31.269 align:start position:0% read from read from contract balances read<00:11:28.910> from<00:11:29.029> contract<00:11:29.510> state<00:11:29.839> so<00:11:30.529> read<00:11:30.890> things 00:11:31.269 --> 00:11:31.279 align:start position:0% read from contract state so read things 00:11:31.279 --> 00:11:34.180 align:start position:0% read from contract state so read things that<00:11:31.490> require<00:11:32.060> basically<00:11:33.020> accessing<00:11:33.950> the 00:11:34.180 --> 00:11:34.190 align:start position:0% that require basically accessing the 00:11:34.190 --> 00:11:37.360 align:start position:0% that require basically accessing the disk<00:11:34.460> and<00:11:34.760> it's<00:11:35.000> been<00:11:35.270> a<00:11:35.680> general<00:11:36.680> fact<00:11:37.040> of 00:11:37.360 --> 00:11:37.370 align:start position:0% disk and it's been a general fact of 00:11:37.370 --> 00:11:38.980 align:start position:0% disk and it's been a general fact of etherium<00:11:37.880> pretty<00:11:38.210> much<00:11:38.420> since<00:11:38.690> the<00:11:38.870> beginning 00:11:38.980 --> 00:11:38.990 align:start position:0% etherium pretty much since the beginning 00:11:38.990 --> 00:11:42.460 align:start position:0% etherium pretty much since the beginning that<00:11:39.740> the<00:11:40.460> gas<00:11:40.820> costs<00:11:41.480> that<00:11:41.690> we<00:11:41.839> set<00:11:42.140> for<00:11:42.380> those 00:11:42.460 --> 00:11:42.470 align:start position:0% that the gas costs that we set for those 00:11:42.470 --> 00:11:44.530 align:start position:0% that the gas costs that we set for those out<00:11:42.740> codes<00:11:43.130> are<00:11:43.279> for<00:11:43.520> multiple<00:11:43.880> reasons<00:11:44.029> far 00:11:44.530 --> 00:11:44.540 align:start position:0% out codes are for multiple reasons far 00:11:44.540 --> 00:11:46.780 align:start position:0% out codes are for multiple reasons far lower<00:11:44.810> than<00:11:45.080> they<00:11:45.200> should<00:11:45.380> be<00:11:45.529> so<00:11:46.520> one<00:11:46.760> of 00:11:46.780 --> 00:11:46.790 align:start position:0% lower than they should be so one of 00:11:46.790 --> 00:11:49.690 align:start position:0% lower than they should be so one of those<00:11:47.000> reasons<00:11:47.270> is<00:11:47.720> that<00:11:47.779> the<00:11:48.620> operative<00:11:49.339> to 00:11:49.690 --> 00:11:49.700 align:start position:0% those reasons is that the operative to 00:11:49.700 --> 00:11:51.040 align:start position:0% those reasons is that the operative to there<00:11:49.850> gas<00:11:50.060> cost<00:11:50.360> the<00:11:50.540> op<00:11:50.630> codes<00:11:50.900> actually 00:11:51.040 --> 00:11:51.050 align:start position:0% there gas cost the op codes actually 00:11:51.050 --> 00:11:52.449 align:start position:0% there gas cost the op codes actually take<00:11:51.440> a<00:11:51.470> fairly<00:11:51.740> long<00:11:52.070> time<00:11:52.100> to<00:11:52.310> process 00:11:52.449 --> 00:11:52.459 align:start position:0% take a fairly long time to process 00:11:52.459 --> 00:11:55.570 align:start position:0% take a fairly long time to process because<00:11:53.620> accessing<00:11:54.620> disk<00:11:54.860> is<00:11:55.100> pretty 00:11:55.570 --> 00:11:55.580 align:start position:0% because accessing disk is pretty 00:11:55.580 --> 00:11:58.990 align:start position:0% because accessing disk is pretty expensive<00:11:55.820> and<00:11:56.240> takes<00:11:56.390> a<00:11:56.540> long<00:11:56.720> time<00:11:56.750> and<00:11:58.000> so 00:11:58.990 --> 00:11:59.000 align:start position:0% expensive and takes a long time and so 00:11:59.000 --> 00:12:00.970 align:start position:0% expensive and takes a long time and so for<00:11:59.209> example<00:11:59.779> there<00:11:59.959> was<00:12:00.080> this<00:12:00.230> recent<00:12:00.709> paper 00:12:00.970 --> 00:12:00.980 align:start position:0% for example there was this recent paper 00:12:00.980 --> 00:12:03.610 align:start position:0% for example there was this recent paper that<00:12:01.430> suggest<00:12:02.050> suggested<00:12:03.050> that<00:12:03.230> like<00:12:03.440> on 00:12:03.610 --> 00:12:03.620 align:start position:0% that suggest suggested that like on 00:12:03.620 --> 00:12:05.140 align:start position:0% that suggest suggested that like on their<00:12:03.770> own<00:12:03.860> hardware<00:12:04.190> a<00:12:04.370> worst-case<00:12:04.790> dos 00:12:05.140 --> 00:12:05.150 align:start position:0% their own hardware a worst-case dos 00:12:05.150 --> 00:12:07.060 align:start position:0% their own hardware a worst-case dos block<00:12:05.510> would<00:12:05.750> take<00:12:05.930> like<00:12:06.170> up<00:12:06.320> to<00:12:06.440> 80<00:12:06.589> seconds 00:12:07.060 --> 00:12:07.070 align:start position:0% block would take like up to 80 seconds 00:12:07.070 --> 00:12:10.180 align:start position:0% block would take like up to 80 seconds to<00:12:07.160> process<00:12:07.310> and<00:12:08.830> making<00:12:09.830> a<00:12:09.890> worst-case 00:12:10.180 --> 00:12:10.190 align:start position:0% to process and making a worst-case 00:12:10.190 --> 00:12:11.650 align:start position:0% to process and making a worst-case tosspot<00:12:10.610> is<00:12:10.910> hard<00:12:11.120> because<00:12:11.270> you<00:12:11.420> have<00:12:11.540> to 00:12:11.650 --> 00:12:11.660 align:start position:0% tosspot is hard because you have to 00:12:11.660 --> 00:12:13.329 align:start position:0% tosspot is hard because you have to outbid<00:12:11.810> like<00:12:12.200> whatever<00:12:12.500> all<00:12:12.650> the<00:12:12.800> other<00:12:12.920> users 00:12:13.329 --> 00:12:13.339 align:start position:0% outbid like whatever all the other users 00:12:13.339 --> 00:12:16.440 align:start position:0% outbid like whatever all the other users but<00:12:13.640> there's<00:12:13.850> like<00:12:14.300> it's<00:12:14.620> security<00:12:15.620> is<00:12:15.860> still 00:12:16.440 --> 00:12:16.450 align:start position:0% but there's like it's security is still 00:12:16.450 --> 00:12:18.780 align:start position:0% but there's like it's security is still lower<00:12:17.450> than<00:12:17.750> we<00:12:17.839> would<00:12:17.870> want<00:12:18.140> it<00:12:18.290> to<00:12:18.320> be 00:12:18.780 --> 00:12:18.790 align:start position:0% lower than we would want it to be 00:12:18.790 --> 00:12:22.390 align:start position:0% lower than we would want it to be especially<00:12:19.790> given<00:12:20.330> the<00:12:20.990> people's<00:12:21.529> people's 00:12:22.390 --> 00:12:22.400 align:start position:0% especially given the people's people's 00:12:22.400 --> 00:12:24.130 align:start position:0% especially given the people's people's desire<00:12:22.760> for<00:12:23.089> more<00:12:23.270> scalability<00:12:23.930> in<00:12:24.020> the 00:12:24.130 --> 00:12:24.140 align:start position:0% desire for more scalability in the 00:12:24.140 --> 00:12:27.220 align:start position:0% desire for more scalability in the medium<00:12:24.440> term<00:12:24.620> and<00:12:24.920> so<00:12:25.490> from<00:12:26.480> a<00:12:26.600> security<00:12:26.959> point 00:12:27.220 --> 00:12:27.230 align:start position:0% medium term and so from a security point 00:12:27.230 --> 00:12:28.810 align:start position:0% medium term and so from a security point of<00:12:27.350> view<00:12:27.410> it's<00:12:27.709> like<00:12:27.890> pretty<00:12:28.100> much<00:12:28.190> required 00:12:28.810 --> 00:12:28.820 align:start position:0% of view it's like pretty much required 00:12:28.820 --> 00:12:33.040 align:start position:0% of view it's like pretty much required to<00:12:29.470> increase<00:12:30.470> the<00:12:30.920> gas<00:12:31.100> costs<00:12:31.700> of<00:12:32.050> checking 00:12:33.040 --> 00:12:33.050 align:start position:0% to increase the gas costs of checking 00:12:33.050 --> 00:12:35.320 align:start position:0% to increase the gas costs of checking contract<00:12:33.560> balances<00:12:34.100> reading<00:12:34.550> contract<00:12:35.029> code 00:12:35.320 --> 00:12:35.330 align:start position:0% contract balances reading contract code 00:12:35.330 --> 00:12:38.680 align:start position:0% contract balances reading contract code you<00:12:35.660> agreed<00:12:36.170> in<00:12:36.290> contract<00:12:36.740> storage<00:12:37.160> and<00:12:37.690> my 00:12:38.680 --> 00:12:38.690 align:start position:0% you agreed in contract storage and my 00:12:38.690 --> 00:12:40.510 align:start position:0% you agreed in contract storage and my own<00:12:38.839> personal<00:12:39.320> opinion<00:12:39.740> is<00:12:39.890> that<00:12:39.920> the<00:12:40.190> IP<00:12:40.370> is 00:12:40.510 --> 00:12:40.520 align:start position:0% own personal opinion is that the IP is 00:12:40.520 --> 00:12:41.949 align:start position:0% own personal opinion is that the IP is that<00:12:40.730> we<00:12:40.790> have<00:12:41.000> don't<00:12:41.240> go<00:12:41.390> nearly<00:12:41.600> far<00:12:41.779> enough 00:12:41.949 --> 00:12:41.959 align:start position:0% that we have don't go nearly far enough 00:12:41.959 --> 00:12:44.829 align:start position:0% that we have don't go nearly far enough but<00:12:42.620> the<00:12:42.830> problem<00:12:43.190> is<00:12:43.310> that<00:12:43.370> the<00:12:43.790> like<00:12:44.660> this 00:12:44.829 --> 00:12:44.839 align:start position:0% but the problem is that the like this 00:12:44.839 --> 00:12:46.920 align:start position:0% but the problem is that the like this requires<00:12:45.170> increasing<00:12:45.709> some<00:12:45.860> gas<00:12:46.070> costs<00:12:46.610> and 00:12:46.920 --> 00:12:46.930 align:start position:0% requires increasing some gas costs and 00:12:46.930 --> 00:12:50.949 align:start position:0% requires increasing some gas costs and this<00:12:48.130> basically<00:12:49.130> breaks<00:12:49.640> some<00:12:50.120> contracts 00:12:50.949 --> 00:12:50.959 align:start position:0% this basically breaks some contracts 00:12:50.959 --> 00:12:53.980 align:start position:0% this basically breaks some contracts that<00:12:51.279> relied<00:12:52.279> I'd<00:12:53.240> only<00:12:53.390> assumption<00:12:53.779> that 00:12:53.980 --> 00:12:53.990 align:start position:0% that relied I'd only assumption that 00:12:53.990 --> 00:12:55.600 align:start position:0% that relied I'd only assumption that there<00:12:54.380> is<00:12:54.470> a<00:12:54.500> fixed<00:12:54.800> amount<00:12:54.890> of<00:12:55.100> gas<00:12:55.250> within 00:12:55.600 --> 00:12:55.610 align:start position:0% there is a fixed amount of gas within 00:12:55.610 --> 00:12:58.210 align:start position:0% there is a fixed amount of gas within which<00:12:55.790> they<00:12:56.000> could<00:12:56.209> do<00:12:56.390> some<00:12:56.600> things 00:12:58.210 --> 00:12:58.220 align:start position:0% which they could do some things 00:12:58.220 --> 00:13:02.180 align:start position:0% which they could do some things so<00:12:59.220> I<00:12:59.790> think<00:13:00.630> I've<00:13:00.930> written<00:13:01.320> this<00:13:01.710> opinion 00:13:02.180 --> 00:13:02.190 align:start position:0% so I think I've written this opinion 00:13:02.190 --> 00:13:04.190 align:start position:0% so I think I've written this opinion somewhere<00:13:02.550> but<00:13:02.730> from<00:13:03.330> my<00:13:03.420> point<00:13:03.690> of<00:13:03.810> view<00:13:03.870> the 00:13:04.190 --> 00:13:04.200 align:start position:0% somewhere but from my point of view the 00:13:04.200 --> 00:13:07.520 align:start position:0% somewhere but from my point of view the the<00:13:04.830> reason<00:13:05.310> why<00:13:05.490> the<00:13:06.060> creases<00:13:06.690> of<00:13:06.720> the<00:13:06.900> gas 00:13:07.520 --> 00:13:07.530 align:start position:0% the reason why the creases of the gas 00:13:07.530 --> 00:13:10.790 align:start position:0% the reason why the creases of the gas ghost<00:13:08.220> breaking<00:13:09.030> things<00:13:09.240> is<00:13:09.720> because<00:13:10.470> the<00:13:10.590> gas 00:13:10.790 --> 00:13:10.800 align:start position:0% ghost breaking things is because the gas 00:13:10.800 --> 00:13:14.180 align:start position:0% ghost breaking things is because the gas is<00:13:11.130> used<00:13:11.490> in<00:13:11.760> two<00:13:11.970> different<00:13:12.270> functions<00:13:13.190> so 00:13:14.180 --> 00:13:14.190 align:start position:0% is used in two different functions so 00:13:14.190 --> 00:13:16.340 align:start position:0% is used in two different functions so first<00:13:14.490> function<00:13:14.700> of<00:13:15.030> the<00:13:15.120> gas<00:13:15.300> is<00:13:15.630> what 00:13:16.340 --> 00:13:16.350 align:start position:0% first function of the gas is what 00:13:16.350 --> 00:13:18.940 align:start position:0% first function of the gas is what metallic<00:13:17.040> was<00:13:17.160> talking<00:13:17.490> about<00:13:17.550> is<00:13:18.330> to 00:13:18.940 --> 00:13:18.950 align:start position:0% metallic was talking about is to 00:13:18.950 --> 00:13:23.600 align:start position:0% metallic was talking about is to basically<00:13:19.950> measure<00:13:20.640> the<00:13:21.890> the<00:13:22.890> impact<00:13:23.310> on<00:13:23.520> the 00:13:23.600 --> 00:13:23.610 align:start position:0% basically measure the the impact on the 00:13:23.610 --> 00:13:25.400 align:start position:0% basically measure the the impact on the system<00:13:23.790> the<00:13:24.120> performance<00:13:24.600> impact<00:13:24.900> and<00:13:25.140> charge 00:13:25.400 --> 00:13:25.410 align:start position:0% system the performance impact and charge 00:13:25.410 --> 00:13:27.680 align:start position:0% system the performance impact and charge people<00:13:25.680> for<00:13:25.890> the<00:13:26.700> same<00:13:26.940> transaction<00:13:27.270> to 00:13:27.680 --> 00:13:27.690 align:start position:0% people for the same transaction to 00:13:27.690 --> 00:13:30.620 align:start position:0% people for the same transaction to compensate<00:13:28.290> for<00:13:28.530> that<00:13:28.590> and<00:13:29.330> discourage<00:13:30.330> the 00:13:30.620 --> 00:13:30.630 align:start position:0% compensate for that and discourage the 00:13:30.630 --> 00:13:33.530 align:start position:0% compensate for that and discourage the abuse<00:13:31.470> of<00:13:31.680> the<00:13:31.740> system<00:13:31.880> but<00:13:32.880> there's<00:13:33.030> a<00:13:33.150> second 00:13:33.530 --> 00:13:33.540 align:start position:0% abuse of the system but there's a second 00:13:33.540 --> 00:13:37.940 align:start position:0% abuse of the system but there's a second function<00:13:33.930> which<00:13:34.110> also<00:13:34.320> gas<00:13:35.030> gas<00:13:36.060> plays<00:13:37.050> which 00:13:37.940 --> 00:13:37.950 align:start position:0% function which also gas gas plays which 00:13:37.950 --> 00:13:40.250 align:start position:0% function which also gas gas plays which is<00:13:38.160> the<00:13:38.370> restriction<00:13:39.060> of<00:13:39.390> the<00:13:39.420> things<00:13:40.050> like 00:13:40.250 --> 00:13:40.260 align:start position:0% is the restriction of the things like 00:13:40.260 --> 00:13:44.720 align:start position:0% is the restriction of the things like recursion<00:13:40.920> and<00:13:41.810> Kobach's<00:13:42.810> and<00:13:43.200> that<00:13:43.950> that 00:13:44.720 --> 00:13:44.730 align:start position:0% recursion and Kobach's and that that 00:13:44.730 --> 00:13:47.930 align:start position:0% recursion and Kobach's and that that second<00:13:45.570> function<00:13:46.080> has<00:13:46.890> been<00:13:47.490> on<00:13:47.610> the<00:13:47.730> rise 00:13:47.930 --> 00:13:47.940 align:start position:0% second function has been on the rise 00:13:47.940 --> 00:13:51.440 align:start position:0% second function has been on the rise since<00:13:48.380> 2016<00:13:49.380> when<00:13:49.710> the<00:13:50.580> especially 00:13:51.440 --> 00:13:51.450 align:start position:0% since 2016 when the especially 00:13:51.450 --> 00:13:54.860 align:start position:0% since 2016 when the especially especially<00:13:51.780> after<00:13:52.260> the<00:13:52.650> re-entrance<00:13:53.870> e3 00:13:54.860 --> 00:13:54.870 align:start position:0% especially after the re-entrance e3 00:13:54.870 --> 00:13:56.930 align:start position:0% especially after the re-entrance e3 instance<00:13:55.170> ii<00:13:55.260> problems<00:13:55.680> have<00:13:55.950> been<00:13:56.100> kind<00:13:56.820> of 00:13:56.930 --> 00:13:56.940 align:start position:0% instance ii problems have been kind of 00:13:56.940 --> 00:13:58.370 align:start position:0% instance ii problems have been kind of brought<00:13:57.240> into<00:13:57.570> light<00:13:57.750> and<00:13:57.780> people<00:13:58.290> were 00:13:58.370 --> 00:13:58.380 align:start position:0% brought into light and people were 00:13:58.380 --> 00:14:00.500 align:start position:0% brought into light and people were trying<00:13:58.590> to<00:13:58.800> use<00:13:58.980> the<00:13:59.280> second<00:14:00.030> function<00:14:00.210> the 00:14:00.500 --> 00:14:00.510 align:start position:0% trying to use the second function the 00:14:00.510 --> 00:14:03.830 align:start position:0% trying to use the second function the gas<00:14:00.690> much<00:14:00.990> more<00:14:01.380> to<00:14:02.310> so<00:14:03.090> they<00:14:03.210> would<00:14:03.390> allocate 00:14:03.830 --> 00:14:03.840 align:start position:0% gas much more to so they would allocate 00:14:03.840 --> 00:14:05.840 align:start position:0% gas much more to so they would allocate a<00:14:04.140> very<00:14:04.350> limited<00:14:04.590> amount<00:14:04.920> of<00:14:05.250> gas<00:14:05.400> for<00:14:05.640> a<00:14:05.700> lot 00:14:05.840 --> 00:14:05.850 align:start position:0% a very limited amount of gas for a lot 00:14:05.850 --> 00:14:07.820 align:start position:0% a very limited amount of gas for a lot of<00:14:05.970> operations<00:14:06.510> to<00:14:06.750> make<00:14:07.290> sure<00:14:07.530> that<00:14:07.710> the 00:14:07.820 --> 00:14:07.830 align:start position:0% of operations to make sure that the 00:14:07.830 --> 00:14:09.920 align:start position:0% of operations to make sure that the recursion<00:14:08.130> doesn't<00:14:08.610> go<00:14:08.700> deep<00:14:09.000> or<00:14:09.240> the 00:14:09.920 --> 00:14:09.930 align:start position:0% recursion doesn't go deep or the 00:14:09.930 --> 00:14:13.280 align:start position:0% recursion doesn't go deep or the callbacks<00:14:10.380> can't<00:14:10.680> do<00:14:10.890> things<00:14:11.640> but<00:14:12.630> we<00:14:12.840> now<00:14:12.990> see 00:14:13.280 --> 00:14:13.290 align:start position:0% callbacks can't do things but we now see 00:14:13.290 --> 00:14:15.230 align:start position:0% callbacks can't do things but we now see that<00:14:13.500> these<00:14:13.650> two<00:14:14.010> functions<00:14:14.430> are<00:14:14.610> becoming<00:14:15.000> at 00:14:15.230 --> 00:14:15.240 align:start position:0% that these two functions are becoming at 00:14:15.240 --> 00:14:17.000 align:start position:0% that these two functions are becoming at odds<00:14:15.450> with<00:14:15.570> each<00:14:15.720> other 00:14:17.000 --> 00:14:17.010 align:start position:0% odds with each other 00:14:17.010 --> 00:14:19.580 align:start position:0% odds with each other while<00:14:17.430> you<00:14:18.090> know<00:14:18.180> improving<00:14:18.660> one<00:14:18.960> we<00:14:19.200> actually 00:14:19.580 --> 00:14:19.590 align:start position:0% while you know improving one we actually 00:14:19.590 --> 00:14:21.860 align:start position:0% while you know improving one we actually hurt<00:14:19.950> in<00:14:20.130> the<00:14:20.280> other<00:14:20.430> and<00:14:20.730> from<00:14:21.360> my<00:14:21.480> point<00:14:21.690> of 00:14:21.860 --> 00:14:21.870 align:start position:0% hurt in the other and from my point of 00:14:21.870 --> 00:14:24.620 align:start position:0% hurt in the other and from my point of view<00:14:21.930> the<00:14:22.170> it<00:14:22.830> is<00:14:23.340> becoming<00:14:23.790> worrying<00:14:24.450> because 00:14:24.620 --> 00:14:24.630 align:start position:0% view the it is becoming worrying because 00:14:24.630 --> 00:14:27.320 align:start position:0% view the it is becoming worrying because that<00:14:24.990> that<00:14:25.500> tells<00:14:25.740> me<00:14:25.950> that<00:14:25.980> in<00:14:26.430> the<00:14:26.580> future<00:14:26.910> we 00:14:27.320 --> 00:14:27.330 align:start position:0% that that tells me that in the future we 00:14:27.330 --> 00:14:28.850 align:start position:0% that that tells me that in the future we need<00:14:27.450> to<00:14:27.510> do<00:14:27.780> more<00:14:28.080> of<00:14:28.110> those<00:14:28.380> things 00:14:28.850 --> 00:14:28.860 align:start position:0% need to do more of those things 00:14:28.860 --> 00:14:31.670 align:start position:0% need to do more of those things in<00:14:29.090> just<00:14:30.090> in<00:14:30.240> the<00:14:30.330> gas<00:14:30.510> Coast<00:14:30.810> and<00:14:30.960> we<00:14:31.350> have<00:14:31.530> to 00:14:31.670 --> 00:14:31.680 align:start position:0% in just in the gas Coast and we have to 00:14:31.680 --> 00:14:33.620 align:start position:0% in just in the gas Coast and we have to assume<00:14:31.950> that<00:14:32.130> we<00:14:32.310> should<00:14:33.030> be<00:14:33.180> doing<00:14:33.390> it<00:14:33.480> all 00:14:33.620 --> 00:14:33.630 align:start position:0% assume that we should be doing it all 00:14:33.630 --> 00:14:35.540 align:start position:0% assume that we should be doing it all the<00:14:33.750> time<00:14:33.780> anyway<00:14:34.380> because<00:14:35.010> the<00:14:35.280> hardware 00:14:35.540 --> 00:14:35.550 align:start position:0% the time anyway because the hardware 00:14:35.550 --> 00:14:38.480 align:start position:0% the time anyway because the hardware changes<00:14:36.150> everything<00:14:36.420> changes<00:14:36.680> we<00:14:37.680> have<00:14:38.070> to<00:14:38.220> do 00:14:38.480 --> 00:14:38.490 align:start position:0% changes everything changes we have to do 00:14:38.490 --> 00:14:40.370 align:start position:0% changes everything changes we have to do the<00:14:38.670> way<00:14:38.790> out<00:14:39.000> of<00:14:39.030> it<00:14:39.360> is<00:14:39.390> to<00:14:39.690> split<00:14:40.110> those<00:14:40.320> two 00:14:40.370 --> 00:14:40.380 align:start position:0% the way out of it is to split those two 00:14:40.380 --> 00:14:42.470 align:start position:0% the way out of it is to split those two functions<00:14:40.980> and<00:14:41.160> then<00:14:41.370> decouple<00:14:41.850> them<00:14:42.180> from 00:14:42.470 --> 00:14:42.480 align:start position:0% functions and then decouple them from 00:14:42.480 --> 00:14:44.090 align:start position:0% functions and then decouple them from each<00:14:42.600> other<00:14:42.720> and<00:14:43.140> that<00:14:43.680> does<00:14:43.920> bring 00:14:44.090 --> 00:14:44.100 align:start position:0% each other and that does bring 00:14:44.100 --> 00:14:46.100 align:start position:0% each other and that does bring complexity<00:14:44.940> because<00:14:45.330> we<00:14:45.480> essentially<00:14:45.840> will 00:14:46.100 --> 00:14:46.110 align:start position:0% complexity because we essentially will 00:14:46.110 --> 00:14:48.800 align:start position:0% complexity because we essentially will have<00:14:46.230> two<00:14:46.620> gases<00:14:47.070> now<00:14:47.280> to<00:14:47.880> gas<00:14:48.090> counters<00:14:48.630> one 00:14:48.800 --> 00:14:48.810 align:start position:0% have two gases now to gas counters one 00:14:48.810 --> 00:14:50.930 align:start position:0% have two gases now to gas counters one for<00:14:49.020> the<00:14:49.170> one<00:14:49.680> first<00:14:50.010> function<00:14:50.460> one<00:14:50.640> for<00:14:50.880> the 00:14:50.930 --> 00:14:50.940 align:start position:0% for the one first function one for the 00:14:50.940 --> 00:14:52.910 align:start position:0% for the one first function one for the second<00:14:51.270> function<00:14:51.450> and<00:14:51.840> then<00:14:52.380> you<00:14:52.590> need<00:14:52.770> to 00:14:52.910 --> 00:14:52.920 align:start position:0% second function and then you need to 00:14:52.920 --> 00:14:54.770 align:start position:0% second function and then you need to decide<00:14:53.040> what<00:14:53.460> is<00:14:53.610> the<00:14:53.640> gas<00:14:53.880> limit<00:14:54.270> and<00:14:54.480> is<00:14:54.630> it 00:14:54.770 --> 00:14:54.780 align:start position:0% decide what is the gas limit and is it 00:14:54.780 --> 00:14:56.870 align:start position:0% decide what is the gas limit and is it the<00:14:55.080> gas<00:14:55.230> limit<00:14:55.620> for<00:14:55.860> the<00:14:55.920> first<00:14:56.160> one<00:14:56.430> or<00:14:56.640> is<00:14:56.760> it 00:14:56.870 --> 00:14:56.880 align:start position:0% the gas limit for the first one or is it 00:14:56.880 --> 00:14:58.880 align:start position:0% the gas limit for the first one or is it the<00:14:56.970> gas<00:14:57.120> limit<00:14:57.330> for<00:14:57.600> the<00:14:57.690> second<00:14:58.050> one<00:14:58.200> but<00:14:58.830> I 00:14:58.880 --> 00:14:58.890 align:start position:0% the gas limit for the second one but I 00:14:58.890 --> 00:15:01.310 align:start position:0% the gas limit for the second one but I think<00:14:59.100> it's<00:14:59.250> solvable<00:14:59.670> and<00:15:00.270> more<00:15:00.870> importantly 00:15:01.310 --> 00:15:01.320 align:start position:0% think it's solvable and more importantly 00:15:01.320 --> 00:15:03.530 align:start position:0% think it's solvable and more importantly if<00:15:01.530> you<00:15:01.560> decouple<00:15:01.950> this<00:15:02.280> then<00:15:02.580> you<00:15:02.760> are<00:15:02.790> kind 00:15:03.530 --> 00:15:03.540 align:start position:0% if you decouple this then you are kind 00:15:03.540 --> 00:15:08.180 align:start position:0% if you decouple this then you are kind of<00:15:03.630> a<00:15:03.750> bit<00:15:03.900> more<00:15:04.230> future-proof<00:15:06.800> so<00:15:07.800> coming 00:15:08.180 --> 00:15:08.190 align:start position:0% of a bit more future-proof so coming 00:15:08.190 --> 00:15:10.340 align:start position:0% of a bit more future-proof so coming back<00:15:08.220> to<00:15:08.490> your<00:15:08.610> original<00:15:08.700> question<00:15:09.200> which<00:15:10.200> was 00:15:10.340 --> 00:15:10.350 align:start position:0% back to your original question which was 00:15:10.350 --> 00:15:10.560 align:start position:0% back to your original question which was a 00:15:10.560 --> 00:15:10.570 align:start position:0% a 00:15:10.570 --> 00:15:12.240 align:start position:0% a like<00:15:10.720> invariances<00:15:11.290> an<00:15:11.440> app<00:15:11.560> developer<00:15:12.010> like 00:15:12.240 --> 00:15:12.250 align:start position:0% like invariances an app developer like 00:15:12.250 --> 00:15:13.620 align:start position:0% like invariances an app developer like obviously<00:15:12.580> we<00:15:12.730> need<00:15:12.850> to<00:15:12.970> change<00:15:13.090> the<00:15:13.270> gas<00:15:13.390> cost 00:15:13.620 --> 00:15:13.630 align:start position:0% obviously we need to change the gas cost 00:15:13.630 --> 00:15:15.540 align:start position:0% obviously we need to change the gas cost sometimes<00:15:14.020> because<00:15:14.380> security<00:15:14.860> and<00:15:15.250> a<00:15:15.430> whole 00:15:15.540 --> 00:15:15.550 align:start position:0% sometimes because security and a whole 00:15:15.550 --> 00:15:17.520 align:start position:0% sometimes because security and a whole bunch<00:15:15.730> of<00:15:15.820> reasons<00:15:16.000> and<00:15:16.900> some<00:15:17.200> of<00:15:17.290> which<00:15:17.380> we 00:15:17.520 --> 00:15:17.530 align:start position:0% bunch of reasons and some of which we 00:15:17.530 --> 00:15:20.190 align:start position:0% bunch of reasons and some of which we don't<00:15:17.620> know<00:15:17.770> today<00:15:18.270> so<00:15:19.270> I<00:15:19.300> I<00:15:19.720> guess<00:15:19.960> it's<00:15:20.140> a 00:15:20.190 --> 00:15:20.200 align:start position:0% don't know today so I I guess it's a 00:15:20.200 --> 00:15:22.230 align:start position:0% don't know today so I I guess it's a question<00:15:20.230> for<00:15:20.590> people<00:15:20.710> up<00:15:20.890> here<00:15:21.190> are<00:15:21.970> there 00:15:22.230 --> 00:15:22.240 align:start position:0% question for people up here are there 00:15:22.240 --> 00:15:24.810 align:start position:0% question for people up here are there like<00:15:22.480> actual<00:15:22.960> invariants<00:15:23.860> that<00:15:23.920> you<00:15:24.220> can<00:15:24.430> give 00:15:24.810 --> 00:15:24.820 align:start position:0% like actual invariants that you can give 00:15:24.820 --> 00:15:26.580 align:start position:0% like actual invariants that you can give the<00:15:25.090> DAP<00:15:25.300> developers<00:15:25.870> building<00:15:26.410> and 00:15:26.580 --> 00:15:26.590 align:start position:0% the DAP developers building and 00:15:26.590 --> 00:15:30.240 align:start position:0% the DAP developers building and aetherium<00:15:26.980> or<00:15:27.250> is<00:15:28.090> the<00:15:28.690> sort<00:15:29.140> of<00:15:29.260> hard<00:15:29.560> answer 00:15:30.240 --> 00:15:30.250 align:start position:0% aetherium or is the sort of hard answer 00:15:30.250 --> 00:15:31.650 align:start position:0% aetherium or is the sort of hard answer you<00:15:30.370> know<00:15:30.490> things<00:15:30.820> will<00:15:31.000> change<00:15:31.030> they<00:15:31.510> will 00:15:31.650 --> 00:15:31.660 align:start position:0% you know things will change they will 00:15:31.660 --> 00:15:34.050 align:start position:0% you know things will change they will break<00:15:31.870> and<00:15:32.290> we'll<00:15:32.860> try<00:15:33.100> our<00:15:33.310> best<00:15:33.460> you<00:15:33.880> know<00:15:34.000> to 00:15:34.050 --> 00:15:34.060 align:start position:0% break and we'll try our best you know to 00:15:34.060 --> 00:15:35.880 align:start position:0% break and we'll try our best you know to make<00:15:34.480> that<00:15:34.690> the<00:15:34.870> least<00:15:35.110> inconvenient<00:15:35.830> as 00:15:35.880 --> 00:15:35.890 align:start position:0% make that the least inconvenient as 00:15:35.890 --> 00:15:37.920 align:start position:0% make that the least inconvenient as possible<00:15:36.280> but<00:15:36.670> it's<00:15:36.820> kind<00:15:36.970> of<00:15:37.030> unrealistic<00:15:37.570> if 00:15:37.920 --> 00:15:37.930 align:start position:0% possible but it's kind of unrealistic if 00:15:37.930 --> 00:15:39.480 align:start position:0% possible but it's kind of unrealistic if you're<00:15:38.050> building<00:15:38.140> an<00:15:38.470> app<00:15:38.590> to<00:15:38.830> assume<00:15:39.100> you 00:15:39.480 --> 00:15:39.490 align:start position:0% you're building an app to assume you 00:15:39.490 --> 00:15:41.340 align:start position:0% you're building an app to assume you know<00:15:39.610> there's<00:15:39.880> any<00:15:40.030> invariants<00:15:40.600> I<00:15:40.780> think<00:15:41.290> the 00:15:41.340 --> 00:15:41.350 align:start position:0% know there's any invariants I think the 00:15:41.350 --> 00:15:42.720 align:start position:0% know there's any invariants I think the truth<00:15:41.530> is<00:15:41.650> like<00:15:41.920> somewhere<00:15:42.190> in<00:15:42.250> between<00:15:42.340> but 00:15:42.720 --> 00:15:42.730 align:start position:0% truth is like somewhere in between but 00:15:42.730 --> 00:15:44.330 align:start position:0% truth is like somewhere in between but I'm<00:15:42.910> curious<00:15:43.120> what<00:15:43.480> people<00:15:43.510> think<00:15:43.900> about<00:15:43.990> that 00:15:44.330 --> 00:15:44.340 align:start position:0% I'm curious what people think about that 00:15:44.340 --> 00:15:48.060 align:start position:0% I'm curious what people think about that yeah<00:15:45.340> I<00:15:45.370> I<00:15:45.490> think<00:15:46.060> that<00:15:46.750> the<00:15:47.290> app<00:15:47.380> developers 00:15:48.060 --> 00:15:48.070 align:start position:0% yeah I I think that the app developers 00:15:48.070 --> 00:15:51.210 align:start position:0% yeah I I think that the app developers should<00:15:48.400> have<00:15:48.640> the<00:15:48.790> mindset<00:15:49.210> that<00:15:49.810> things<00:15:50.560> may 00:15:51.210 --> 00:15:51.220 align:start position:0% should have the mindset that things may 00:15:51.220 --> 00:15:54.390 align:start position:0% should have the mindset that things may change<00:15:52.080> there<00:15:53.080> are<00:15:53.200> no<00:15:53.410> way<00:15:53.560> variants<00:15:54.160> and 00:15:54.390 --> 00:15:54.400 align:start position:0% change there are no way variants and 00:15:54.400 --> 00:15:59.960 align:start position:0% change there are no way variants and they<00:15:55.240> should<00:15:55.710> build<00:15:56.710> their<00:15:57.420> systems<00:15:58.420> or 00:15:59.960 --> 00:15:59.970 align:start position:0% they should build their systems or 00:15:59.970 --> 00:16:02.730 align:start position:0% they should build their systems or deployments<00:16:00.970> in<00:16:01.630> ways<00:16:01.870> that<00:16:02.320> they<00:16:02.500> can<00:16:02.560> be 00:16:02.730 --> 00:16:02.740 align:start position:0% deployments in ways that they can be 00:16:02.740 --> 00:16:05.460 align:start position:0% deployments in ways that they can be upgraded<00:16:03.900> because<00:16:04.900> it's<00:16:05.050> still<00:16:05.290> developing 00:16:05.460 --> 00:16:05.470 align:start position:0% upgraded because it's still developing 00:16:05.470 --> 00:16:07.530 align:start position:0% upgraded because it's still developing the<00:16:06.040> EVM<00:16:06.340> is<00:16:06.430> still<00:16:06.610> developing<00:16:07.000> that's<00:16:07.360> my 00:16:07.530 --> 00:16:07.540 align:start position:0% the EVM is still developing that's my 00:16:07.540 --> 00:16:14.130 align:start position:0% the EVM is still developing that's my point<00:16:08.410> of<00:16:08.560> view<00:16:10.530> just<00:16:11.530> after<00:16:11.890> that<00:16:12.070> I<00:16:12.600> think<00:16:13.600> of 00:16:14.130 --> 00:16:14.140 align:start position:0% point of view just after that I think of 00:16:14.140 --> 00:16:15.660 align:start position:0% point of view just after that I think of for<00:16:14.620> example<00:16:14.680> now<00:16:14.980> the<00:16:15.040> important<00:16:15.520> thing<00:16:15.640> that 00:16:15.660 --> 00:16:15.670 align:start position:0% for example now the important thing that 00:16:15.670 --> 00:16:18.480 align:start position:0% for example now the important thing that that<00:16:15.910> developers<00:16:16.390> should<00:16:16.420> always<00:16:16.990> keep<00:16:17.320> if<00:16:18.310> in 00:16:18.480 --> 00:16:18.490 align:start position:0% that developers should always keep if in 00:16:18.490 --> 00:16:20.400 align:start position:0% that developers should always keep if in front<00:16:18.700> of<00:16:18.820> them<00:16:18.970> is<00:16:19.180> that<00:16:19.360> every<00:16:19.600> time<00:16:19.780> you<00:16:19.990> you 00:16:20.400 --> 00:16:20.410 align:start position:0% front of them is that every time you you 00:16:20.410 --> 00:16:22.170 align:start position:0% front of them is that every time you you find<00:16:20.650> a<00:16:20.740> neat<00:16:20.920> little<00:16:21.070> trick<00:16:21.400> that<00:16:21.700> hey<00:16:21.910> I<00:16:21.940> can 00:16:22.170 --> 00:16:22.180 align:start position:0% find a neat little trick that hey I can 00:16:22.180 --> 00:16:25.350 align:start position:0% find a neat little trick that hey I can store<00:16:22.720> this<00:16:22.930> data<00:16:22.990> in<00:16:23.890> a<00:16:24.010> in<00:16:24.520> a<00:16:24.610> more<00:16:24.820> optimal 00:16:25.350 --> 00:16:25.360 align:start position:0% store this data in a in a more optimal 00:16:25.360 --> 00:16:27.960 align:start position:0% store this data in a in a more optimal way<00:16:25.600> or<00:16:25.840> sorry<00:16:26.200> in<00:16:26.350> a<00:16:26.650> way<00:16:26.830> that<00:16:27.070> kind<00:16:27.670> of<00:16:27.760> is<00:16:27.940> a 00:16:27.960 --> 00:16:27.970 align:start position:0% way or sorry in a way that kind of is a 00:16:27.970 --> 00:16:30.090 align:start position:0% way or sorry in a way that kind of is a bit<00:16:28.210> cheaper<00:16:28.720> than<00:16:28.930> storing<00:16:29.410> it<00:16:29.590> the<00:16:29.740> other 00:16:30.090 --> 00:16:30.100 align:start position:0% bit cheaper than storing it the other 00:16:30.100 --> 00:16:33.090 align:start position:0% bit cheaper than storing it the other way<00:16:30.280> around<00:16:30.400> our<00:16:31.270> goal<00:16:31.720> as<00:16:32.050> maintenance<00:16:32.920> of<00:16:33.010> a 00:16:33.090 --> 00:16:33.100 align:start position:0% way around our goal as maintenance of a 00:16:33.100 --> 00:16:34.740 align:start position:0% way around our goal as maintenance of a theorem<00:16:33.460> is<00:16:33.610> to<00:16:33.850> make<00:16:34.000> sure<00:16:34.030> that<00:16:34.270> everything 00:16:34.740 --> 00:16:34.750 align:start position:0% theorem is to make sure that everything 00:16:34.750 --> 00:16:36.690 align:start position:0% theorem is to make sure that everything is<00:16:34.810> priced<00:16:35.080> correctly<00:16:35.320> which<00:16:36.250> kind<00:16:36.460> of<00:16:36.520> means 00:16:36.690 --> 00:16:36.700 align:start position:0% is priced correctly which kind of means 00:16:36.700 --> 00:16:41.510 align:start position:0% is priced correctly which kind of means that<00:16:36.940> storing<00:16:37.630> data<00:16:37.870> should<00:16:38.430> cost<00:16:39.430> the<00:16:40.150> actual 00:16:41.510 --> 00:16:41.520 align:start position:0% that storing data should cost the actual 00:16:41.520 --> 00:16:44.580 align:start position:0% that storing data should cost the actual resource<00:16:42.520> so<00:16:43.210> if<00:16:43.420> you<00:16:43.510> figure<00:16:43.690> out<00:16:43.840> a<00:16:43.960> cheaper 00:16:44.580 --> 00:16:44.590 align:start position:0% resource so if you figure out a cheaper 00:16:44.590 --> 00:16:46.620 align:start position:0% resource so if you figure out a cheaper way<00:16:44.740> to<00:16:44.770> store<00:16:45.220> it<00:16:45.370> then<00:16:46.000> there<00:16:46.300> is<00:16:46.390> a<00:16:46.420> high 00:16:46.620 --> 00:16:46.630 align:start position:0% way to store it then there is a high 00:16:46.630 --> 00:16:49.170 align:start position:0% way to store it then there is a high chance<00:16:46.660> that<00:16:47.200> if<00:16:47.470> it<00:16:48.160> picks<00:16:48.370> up<00:16:48.490> steam<00:16:48.790> then<00:16:49.090> it 00:16:49.170 --> 00:16:49.180 align:start position:0% chance that if it picks up steam then it 00:16:49.180 --> 00:16:51.990 align:start position:0% chance that if it picks up steam then it will<00:16:49.360> get<00:16:49.510> patched<00:16:49.810> simply<00:16:50.620> because<00:16:50.950> it's<00:16:51.760> out 00:16:51.990 --> 00:16:52.000 align:start position:0% will get patched simply because it's out 00:16:52.000 --> 00:16:54.060 align:start position:0% will get patched simply because it's out of<00:16:52.030> its<00:16:52.390> not<00:16:52.630> balanced<00:16:53.290> correctly<00:16:53.470> so<00:16:53.920> our 00:16:54.060 --> 00:16:54.070 align:start position:0% of its not balanced correctly so our 00:16:54.070 --> 00:16:57.450 align:start position:0% of its not balanced correctly so our goal<00:16:54.310> is<00:16:54.460> always<00:16:54.610> to<00:16:55.110> balance<00:16:56.110> there<00:16:56.320> is<00:16:56.460> the 00:16:57.450 --> 00:16:57.460 align:start position:0% goal is always to balance there is the 00:16:57.460 --> 00:16:58.770 align:start position:0% goal is always to balance there is the of<00:16:57.610> course<00:16:57.820> of<00:16:58.030> the<00:16:58.090> resources<00:16:58.570> actually 00:16:58.770 --> 00:16:58.780 align:start position:0% of course of the resources actually 00:16:58.780 --> 00:17:00.810 align:start position:0% of course of the resources actually being<00:16:59.170> used<00:16:59.410> and<00:16:59.710> yes<00:16:59.980> sometimes<00:17:00.460> that<00:17:00.640> means 00:17:00.810 --> 00:17:00.820 align:start position:0% being used and yes sometimes that means 00:17:00.820 --> 00:17:02.670 align:start position:0% being used and yes sometimes that means making<00:17:01.270> it<00:17:01.450> them<00:17:01.750> cheaper<00:17:02.080> and<00:17:02.170> sometimes<00:17:02.560> it 00:17:02.670 --> 00:17:02.680 align:start position:0% making it them cheaper and sometimes it 00:17:02.680 --> 00:17:04.890 align:start position:0% making it them cheaper and sometimes it means<00:17:02.890> making<00:17:03.160> them<00:17:03.370> more<00:17:03.490> expensive<00:17:03.820> but<00:17:04.689> all 00:17:04.890 --> 00:17:04.900 align:start position:0% means making them more expensive but all 00:17:04.900 --> 00:17:07.980 align:start position:0% means making them more expensive but all the<00:17:05.079> loopholes<00:17:05.880> will<00:17:06.880> eventually<00:17:07.570> be<00:17:07.689> filled 00:17:07.980 --> 00:17:07.990 align:start position:0% the loopholes will eventually be filled 00:17:07.990 --> 00:17:13.740 align:start position:0% the loopholes will eventually be filled so<00:17:08.829> I<00:17:09.660> think<00:17:10.660> that's<00:17:10.930> a<00:17:11.020> good<00:17:11.140> invariant<00:17:12.689> can<00:17:13.689> I 00:17:13.740 --> 00:17:13.750 align:start position:0% so I think that's a good invariant can I 00:17:13.750 --> 00:17:16.290 align:start position:0% so I think that's a good invariant can I ask<00:17:13.839> a<00:17:13.990> question<00:17:14.520> unrelated<00:17:15.520> can<00:17:15.760> we<00:17:15.850> warm 00:17:16.290 --> 00:17:16.300 align:start position:0% ask a question unrelated can we warm 00:17:16.300 --> 00:17:20.970 align:start position:0% ask a question unrelated can we warm from<00:17:17.370> great<00:17:18.370> hi<00:17:19.089> I'm<00:17:19.240> Mary<00:17:19.689> Emma<00:17:19.839> from<00:17:20.079> maker 00:17:20.970 --> 00:17:20.980 align:start position:0% from great hi I'm Mary Emma from maker 00:17:20.980 --> 00:17:23.250 align:start position:0% from great hi I'm Mary Emma from maker and<00:17:21.070> I'd<00:17:21.490> like<00:17:21.640> to<00:17:21.700> discuss<00:17:22.260> programmatic 00:17:23.250 --> 00:17:23.260 align:start position:0% and I'd like to discuss programmatic 00:17:23.260 --> 00:17:30.600 align:start position:0% and I'd like to discuss programmatic proof-of-work<00:17:25.530> because<00:17:28.440> because<00:17:29.440> I<00:17:29.590> feel<00:17:29.830> I 00:17:30.600 --> 00:17:30.610 align:start position:0% proof-of-work because because I feel I 00:17:30.610 --> 00:17:34.830 align:start position:0% proof-of-work because because I feel I I<00:17:30.880> feel<00:17:31.300> like<00:17:31.450> there's<00:17:32.110> a<00:17:32.200> big<00:17:32.620> device<00:17:33.840> core 00:17:34.830 --> 00:17:34.840 align:start position:0% I feel like there's a big device core 00:17:34.840 --> 00:17:39.060 align:start position:0% I feel like there's a big device core devs<00:17:35.110> and<00:17:35.640> community<00:17:36.640> in<00:17:36.700> general<00:17:36.880> and<00:17:38.070> like 00:17:39.060 --> 00:17:39.070 align:start position:0% devs and community in general and like 00:17:39.070 --> 00:17:41.670 align:start position:0% devs and community in general and like I've<00:17:39.310> seen<00:17:39.610> a<00:17:39.640> lot<00:17:39.910> of<00:17:39.990> prominent<00:17:40.990> members<00:17:41.350> of 00:17:41.670 --> 00:17:41.680 align:start position:0% I've seen a lot of prominent members of 00:17:41.680 --> 00:17:44.730 align:start position:0% I've seen a lot of prominent members of different<00:17:42.010> projects<00:17:42.610> and<00:17:42.790> apps<00:17:43.440> that<00:17:44.440> feel 00:17:44.730 --> 00:17:44.740 align:start position:0% different projects and apps that feel 00:17:44.740 --> 00:17:47.310 align:start position:0% different projects and apps that feel strongly<00:17:45.160> against<00:17:45.700> it<00:17:45.820> and<00:17:46.090> many<00:17:46.990> quarters 00:17:47.310 --> 00:17:47.320 align:start position:0% strongly against it and many quarters 00:17:47.320 --> 00:17:49.770 align:start position:0% strongly against it and many quarters apps<00:17:47.470> that<00:17:47.680> feel<00:17:48.130> strongly<00:17:48.460> for<00:17:48.550> it<00:17:48.910> then<00:17:49.120> they 00:17:49.770 --> 00:17:49.780 align:start position:0% apps that feel strongly for it then they 00:17:49.780 --> 00:17:51.930 align:start position:0% apps that feel strongly for it then they were<00:17:49.870> way<00:17:50.050> around<00:17:50.320> and<00:17:50.560> I<00:17:51.010> don't<00:17:51.640> think<00:17:51.790> we've 00:17:51.930 --> 00:17:51.940 align:start position:0% were way around and I don't think we've 00:17:51.940 --> 00:17:54.600 align:start position:0% were way around and I don't think we've ever<00:17:52.180> been<00:17:52.480> closer<00:17:52.750> to<00:17:53.140> a<00:17:53.280> potential<00:17:54.280> heart 00:17:54.600 --> 00:17:54.610 align:start position:0% ever been closer to a potential heart 00:17:54.610 --> 00:17:55.020 align:start position:0% ever been closer to a potential heart Fork 00:17:55.020 --> 00:17:55.030 align:start position:0% Fork 00:17:55.030 --> 00:17:58.800 align:start position:0% Fork since<00:17:55.720> 2016<00:17:56.560> so<00:17:57.130> I<00:17:57.490> would<00:17:58.210> like<00:17:58.330> to<00:17:58.390> see<00:17:58.690> what 00:17:58.800 --> 00:17:58.810 align:start position:0% since 2016 so I would like to see what 00:17:58.810 --> 00:18:03.030 align:start position:0% since 2016 so I would like to see what you<00:17:58.930> think<00:17:59.140> about<00:17:59.260> it<00:17:59.530> I<00:18:00.330> think<00:18:01.330> prog<00:18:01.600> POW<00:18:02.040> is 00:18:03.030 --> 00:18:03.040 align:start position:0% you think about it I think prog POW is 00:18:03.040 --> 00:18:05.430 align:start position:0% you think about it I think prog POW is really<00:18:03.400> important<00:18:04.090> as<00:18:04.330> an<00:18:04.900> issue<00:18:05.050> that<00:18:05.320> we 00:18:05.430 --> 00:18:05.440 align:start position:0% really important as an issue that we 00:18:05.440 --> 00:18:08.670 align:start position:0% really important as an issue that we need<00:18:05.560> to<00:18:05.650> decide<00:18:06.900> not<00:18:07.900> important<00:18:08.320> in<00:18:08.410> itself 00:18:08.670 --> 00:18:08.680 align:start position:0% need to decide not important in itself 00:18:08.680 --> 00:18:10.620 align:start position:0% need to decide not important in itself necessarily<00:18:09.400> I<00:18:09.430> am<00:18:09.640> NOT<00:18:09.820> taking<00:18:10.000> a<00:18:10.210> position 00:18:10.620 --> 00:18:10.630 align:start position:0% necessarily I am NOT taking a position 00:18:10.630 --> 00:18:13.410 align:start position:0% necessarily I am NOT taking a position but<00:18:11.350> I'll<00:18:12.130> say<00:18:12.430> that<00:18:12.730> because<00:18:13.060> of<00:18:13.300> the 00:18:13.410 --> 00:18:13.420 align:start position:0% but I'll say that because of the 00:18:13.420 --> 00:18:16.170 align:start position:0% but I'll say that because of the politics<00:18:14.020> around<00:18:14.230> it<00:18:14.680> it<00:18:15.310> makes<00:18:15.850> it<00:18:16.030> really 00:18:16.170 --> 00:18:16.180 align:start position:0% politics around it it makes it really 00:18:16.180 --> 00:18:18.620 align:start position:0% politics around it it makes it really challenging<00:18:16.900> because<00:18:17.020> on<00:18:17.290> one<00:18:17.500> side<00:18:17.800> you<00:18:18.070> have 00:18:18.620 --> 00:18:18.630 align:start position:0% challenging because on one side you have 00:18:18.630 --> 00:18:21.420 align:start position:0% challenging because on one side you have you<00:18:19.630> know<00:18:19.720> the<00:18:19.870> people<00:18:20.200> like<00:18:20.590> ASIC 00:18:21.420 --> 00:18:21.430 align:start position:0% you know the people like ASIC 00:18:21.430 --> 00:18:23.400 align:start position:0% you know the people like ASIC manufacturers<00:18:22.210> and<00:18:22.540> users<00:18:22.570> and<00:18:23.260> some 00:18:23.400 --> 00:18:23.410 align:start position:0% manufacturers and users and some 00:18:23.410 --> 00:18:25.830 align:start position:0% manufacturers and users and some investors<00:18:23.860> and<00:18:24.040> stuff<00:18:24.250> like<00:18:24.400> that<00:18:24.670> who<00:18:25.210> say<00:18:25.420> we 00:18:25.830 --> 00:18:25.840 align:start position:0% investors and stuff like that who say we 00:18:25.840 --> 00:18:27.240 align:start position:0% investors and stuff like that who say we don't<00:18:25.990> need<00:18:26.230> it<00:18:26.410> the<00:18:26.560> threat<00:18:26.800> isn't<00:18:26.980> big 00:18:27.240 --> 00:18:27.250 align:start position:0% don't need it the threat isn't big 00:18:27.250 --> 00:18:30.210 align:start position:0% don't need it the threat isn't big enough<00:18:27.370> or<00:18:28.110> you<00:18:29.110> know<00:18:29.230> the<00:18:29.530> people<00:18:29.830> who<00:18:29.860> made 00:18:30.210 --> 00:18:30.220 align:start position:0% enough or you know the people who made 00:18:30.220 --> 00:18:32.550 align:start position:0% enough or you know the people who made it<00:18:30.430> are<00:18:30.520> unknown<00:18:31.060> and<00:18:31.450> that's<00:18:31.600> scary<00:18:32.080> and 00:18:32.550 --> 00:18:32.560 align:start position:0% it are unknown and that's scary and 00:18:32.560 --> 00:18:35.010 align:start position:0% it are unknown and that's scary and things<00:18:32.980> like<00:18:33.160> that<00:18:33.660> and<00:18:34.660> then<00:18:34.780> on<00:18:34.870> the<00:18:34.990> other 00:18:35.010 --> 00:18:35.020 align:start position:0% things like that and then on the other 00:18:35.020 --> 00:18:37.260 align:start position:0% things like that and then on the other side<00:18:35.170> you<00:18:35.650> have<00:18:36.130> the<00:18:36.160> GPU<00:18:36.670> miners<00:18:37.060> and<00:18:37.180> the 00:18:37.260 --> 00:18:37.270 align:start position:0% side you have the GPU miners and the 00:18:37.270 --> 00:18:38.910 align:start position:0% side you have the GPU miners and the mining<00:18:37.600> pool<00:18:37.780> saying<00:18:38.080> we<00:18:38.320> need<00:18:38.590> this 00:18:38.910 --> 00:18:38.920 align:start position:0% mining pool saying we need this 00:18:38.920 --> 00:18:41.280 align:start position:0% mining pool saying we need this otherwise<00:18:39.880> we're<00:18:40.570> gonna<00:18:40.630> go<00:18:40.840> under<00:18:41.020> and 00:18:41.280 --> 00:18:41.290 align:start position:0% otherwise we're gonna go under and 00:18:41.290 --> 00:18:43.980 align:start position:0% otherwise we're gonna go under and you're<00:18:41.770> going<00:18:42.610> against<00:18:43.060> the<00:18:43.210> promise<00:18:43.720> that 00:18:43.980 --> 00:18:43.990 align:start position:0% you're going against the promise that 00:18:43.990 --> 00:18:46.080 align:start position:0% you're going against the promise that you<00:18:44.410> made<00:18:44.440> in<00:18:44.740> the<00:18:44.830> white<00:18:45.010> paper<00:18:45.280> according<00:18:45.970> to 00:18:46.080 --> 00:18:46.090 align:start position:0% you made in the white paper according to 00:18:46.090 --> 00:18:49.860 align:start position:0% you made in the white paper according to them<00:18:46.270> that<00:18:46.860> that<00:18:48.030> there<00:18:49.030> would<00:18:49.420> not<00:18:49.630> be<00:18:49.690> a 00:18:49.860 --> 00:18:49.870 align:start position:0% them that that there would not be a 00:18:49.870 --> 00:18:53.250 align:start position:0% them that that there would not be a sakra<00:18:50.380> xizt<00:18:50.590> insanity<00:18:51.430> reom<00:18:51.640> so<00:18:52.510> and<00:18:53.020> then 00:18:53.250 --> 00:18:53.260 align:start position:0% sakra xizt insanity reom so and then 00:18:53.260 --> 00:18:56.340 align:start position:0% sakra xizt insanity reom so and then there's<00:18:53.470> many<00:18:53.920> many<00:18:54.160> other<00:18:55.230> arguments<00:18:56.230> I'm 00:18:56.340 --> 00:18:56.350 align:start position:0% there's many many other arguments I'm 00:18:56.350 --> 00:18:58.890 align:start position:0% there's many many other arguments I'm actually<00:18:56.710> post<00:18:57.550> Devcon<00:18:58.060> going<00:18:58.480> to<00:18:58.690> make<00:18:58.870> a 00:18:58.890 --> 00:18:58.900 align:start position:0% actually post Devcon going to make a 00:18:58.900 --> 00:19:01.590 align:start position:0% actually post Devcon going to make a large<00:18:59.380> blog<00:18:59.830> post<00:19:00.160> reddit<00:19:00.520> post<00:19:00.730> etc<00:19:01.330> with 00:19:01.590 --> 00:19:01.600 align:start position:0% large blog post reddit post etc with 00:19:01.600 --> 00:19:02.730 align:start position:0% large blog post reddit post etc with everybody's<00:19:02.080> arguments<00:19:02.650> and 00:19:02.730 --> 00:19:02.740 align:start position:0% everybody's arguments and 00:19:02.740 --> 00:19:04.950 align:start position:0% everybody's arguments and counter-arguments<00:19:03.370> so<00:19:04.240> the<00:19:04.420> community<00:19:04.930> can 00:19:04.950 --> 00:19:04.960 align:start position:0% counter-arguments so the community can 00:19:04.960 --> 00:19:07.560 align:start position:0% counter-arguments so the community can get<00:19:05.110> a<00:19:05.170> better<00:19:05.350> idea<00:19:05.560> of<00:19:05.920> where<00:19:06.790> everybody 00:19:07.560 --> 00:19:07.570 align:start position:0% get a better idea of where everybody 00:19:07.570 --> 00:19:10.740 align:start position:0% get a better idea of where everybody stands<00:19:07.990> on<00:19:08.230> that<00:19:08.410> from<00:19:08.650> each<00:19:08.740> side<00:19:09.630> that's<00:19:10.630> on 00:19:10.740 --> 00:19:10.750 align:start position:0% stands on that from each side that's on 00:19:10.750 --> 00:19:13.650 align:start position:0% stands on that from each side that's on my<00:19:10.900> to-do<00:19:11.200> list<00:19:11.230> and<00:19:11.710> it's<00:19:12.700> nearing<00:19:13.300> the<00:19:13.390> front 00:19:13.650 --> 00:19:13.660 align:start position:0% my to-do list and it's nearing the front 00:19:13.660 --> 00:19:16.440 align:start position:0% my to-do list and it's nearing the front of<00:19:13.780> it<00:19:13.930> so<00:19:14.380> that'll<00:19:15.370> happen<00:19:15.640> hopefully<00:19:15.970> before 00:19:16.440 --> 00:19:16.450 align:start position:0% of it so that'll happen hopefully before 00:19:16.450 --> 00:19:20.100 align:start position:0% of it so that'll happen hopefully before November<00:19:17.370> and<00:19:18.370> other<00:19:19.060> than<00:19:19.270> that<00:19:19.390> I<00:19:19.540> do<00:19:19.780> want 00:19:20.100 --> 00:19:20.110 align:start position:0% November and other than that I do want 00:19:20.110 --> 00:19:21.870 align:start position:0% November and other than that I do want to<00:19:20.140> kind<00:19:20.290> of<00:19:20.410> hear<00:19:20.680> the<00:19:20.830> perspective<00:19:21.340> of<00:19:21.490> some 00:19:21.870 --> 00:19:21.880 align:start position:0% to kind of hear the perspective of some 00:19:21.880 --> 00:19:23.190 align:start position:0% to kind of hear the perspective of some of<00:19:21.970> the<00:19:22.030> core<00:19:22.240> devs<00:19:22.480> because<00:19:22.750> there<00:19:22.900> you're 00:19:23.190 --> 00:19:23.200 align:start position:0% of the core devs because there you're 00:19:23.200 --> 00:19:25.160 align:start position:0% of the core devs because there you're right<00:19:23.380> there<00:19:23.590> are<00:19:23.620> core<00:19:24.040> devs<00:19:24.250> who<00:19:24.520> are 00:19:25.160 --> 00:19:25.170 align:start position:0% right there are core devs who are 00:19:25.170 --> 00:19:27.210 align:start position:0% right there are core devs who are supporting<00:19:26.170> prog<00:19:26.440> pal 00:19:27.210 --> 00:19:27.220 align:start position:0% supporting prog pal 00:19:27.220 --> 00:19:28.680 align:start position:0% supporting prog pal from<00:19:27.520> their<00:19:27.670> perspective<00:19:27.790> whether<00:19:28.480> its 00:19:28.680 --> 00:19:28.690 align:start position:0% from their perspective whether its 00:19:28.690 --> 00:19:31.290 align:start position:0% from their perspective whether its technical<00:19:29.110> political<00:19:29.620> or<00:19:29.740> both<00:19:29.950> and<00:19:30.300> that's 00:19:31.290 --> 00:19:31.300 align:start position:0% technical political or both and that's 00:19:31.300 --> 00:19:34.470 align:start position:0% technical political or both and that's another<00:19:31.540> divide<00:19:31.930> that's<00:19:32.170> very<00:19:33.360> that's<00:19:34.360> very 00:19:34.470 --> 00:19:34.480 align:start position:0% another divide that's very that's very 00:19:34.480 --> 00:19:36.270 align:start position:0% another divide that's very that's very naturally<00:19:35.290> occurring<00:19:35.740> is<00:19:35.860> you<00:19:36.010> have<00:19:36.130> this 00:19:36.270 --> 00:19:36.280 align:start position:0% naturally occurring is you have this 00:19:36.280 --> 00:19:37.920 align:start position:0% naturally occurring is you have this technical<00:19:36.760> perspective<00:19:37.030> where<00:19:37.450> we<00:19:37.480> had<00:19:37.690> two 00:19:37.920 --> 00:19:37.930 align:start position:0% technical perspective where we had two 00:19:37.930 --> 00:19:39.390 align:start position:0% technical perspective where we had two audits<00:19:38.320> done<00:19:38.410> a<00:19:38.590> hardware<00:19:39.220> and<00:19:39.340> a<00:19:39.370> software 00:19:39.390 --> 00:19:39.400 align:start position:0% audits done a hardware and a software 00:19:39.400 --> 00:19:41.970 align:start position:0% audits done a hardware and a software audit<00:19:40.090> that<00:19:40.570> basically<00:19:40.990> cleared<00:19:41.440> prog<00:19:41.680> Pao<00:19:41.950> is 00:19:41.970 --> 00:19:41.980 align:start position:0% audit that basically cleared prog Pao is 00:19:41.980 --> 00:19:43.800 align:start position:0% audit that basically cleared prog Pao is something<00:19:42.520> that<00:19:42.640> wasn't<00:19:42.820> super<00:19:43.240> fishy<00:19:43.480> and 00:19:43.800 --> 00:19:43.810 align:start position:0% something that wasn't super fishy and 00:19:43.810 --> 00:19:47.040 align:start position:0% something that wasn't super fishy and then<00:19:44.470> you<00:19:44.650> have<00:19:44.860> and<00:19:45.820> then<00:19:45.850> you<00:19:46.600> so<00:19:46.870> you<00:19:46.960> have 00:19:47.040 --> 00:19:47.050 align:start position:0% then you have and then you so you have 00:19:47.050 --> 00:19:48.420 align:start position:0% then you have and then you so you have the<00:19:47.140> technical<00:19:47.380> perspective<00:19:47.620> of<00:19:47.920> it's<00:19:48.160> good 00:19:48.420 --> 00:19:48.430 align:start position:0% the technical perspective of it's good 00:19:48.430 --> 00:19:50.370 align:start position:0% the technical perspective of it's good we've<00:19:48.730> implemented<00:19:49.180> it<00:19:49.390> it'll<00:19:49.600> take<00:19:49.780> two<00:19:50.050> to 00:19:50.370 --> 00:19:50.380 align:start position:0% we've implemented it it'll take two to 00:19:50.380 --> 00:19:51.660 align:start position:0% we've implemented it it'll take two to four<00:19:50.620> weeks<00:19:50.650> for<00:19:50.920> the<00:19:51.100> other<00:19:51.220> clients<00:19:51.640> to 00:19:51.660 --> 00:19:51.670 align:start position:0% four weeks for the other clients to 00:19:51.670 --> 00:19:52.950 align:start position:0% four weeks for the other clients to implement<00:19:52.060> it<00:19:52.120> we're<00:19:52.240> good<00:19:52.390> to<00:19:52.510> go<00:19:52.540> and<00:19:52.660> then 00:19:52.950 --> 00:19:52.960 align:start position:0% implement it we're good to go and then 00:19:52.960 --> 00:19:55.830 align:start position:0% implement it we're good to go and then the<00:19:53.050> political<00:19:53.530> one<00:19:53.950> where<00:19:54.130> it's<00:19:54.250> like<00:19:54.840> you 00:19:55.830 --> 00:19:55.840 align:start position:0% the political one where it's like you 00:19:55.840 --> 00:19:59.030 align:start position:0% the political one where it's like you know<00:19:55.960> I<00:19:56.230> hate<00:19:56.740> Christie<00:19:57.220> Christie's<00:19:57.820> bad 00:19:59.030 --> 00:19:59.040 align:start position:0% know I hate Christie Christie's bad 00:19:59.040 --> 00:20:02.430 align:start position:0% know I hate Christie Christie's bad Christie<00:20:00.040> lied<00:20:00.250> all<00:20:00.910> this<00:20:01.090> other<00:20:01.240> stuff<00:20:01.440> with 00:20:02.430 --> 00:20:02.440 align:start position:0% Christie lied all this other stuff with 00:20:02.440 --> 00:20:05.430 align:start position:0% Christie lied all this other stuff with coarse<00:20:02.680> scientific<00:20:03.400> and<00:20:03.840> the<00:20:04.840> people<00:20:05.230> who<00:20:05.350> are 00:20:05.430 --> 00:20:05.440 align:start position:0% coarse scientific and the people who are 00:20:05.440 --> 00:20:07.200 align:start position:0% coarse scientific and the people who are anonymously<00:20:05.980> developing<00:20:06.550> it<00:20:06.670> so<00:20:06.910> a<00:20:06.940> long 00:20:07.200 --> 00:20:07.210 align:start position:0% anonymously developing it so a long 00:20:07.210 --> 00:20:09.780 align:start position:0% anonymously developing it so a long story<00:20:07.510> short<00:20:07.870> a<00:20:08.410> lot<00:20:08.860> of<00:20:09.010> politics<00:20:09.460> involved 00:20:09.780 --> 00:20:09.790 align:start position:0% story short a lot of politics involved 00:20:09.790 --> 00:20:11.670 align:start position:0% story short a lot of politics involved there's<00:20:10.300> technical<00:20:10.810> versus<00:20:11.110> non<00:20:11.290> technical 00:20:11.670 --> 00:20:11.680 align:start position:0% there's technical versus non technical 00:20:11.680 --> 00:20:14.010 align:start position:0% there's technical versus non technical arguments<00:20:12.430> and<00:20:12.640> there<00:20:13.150> is<00:20:13.300> a<00:20:13.330> division<00:20:13.690> that 00:20:14.010 --> 00:20:14.020 align:start position:0% arguments and there is a division that 00:20:14.020 --> 00:20:16.110 align:start position:0% arguments and there is a division that needs<00:20:14.230> to<00:20:14.380> be<00:20:14.530> figured<00:20:15.220> out<00:20:15.430> in<00:20:15.670> a<00:20:15.790> rough 00:20:16.110 --> 00:20:16.120 align:start position:0% needs to be figured out in a rough 00:20:16.120 --> 00:20:24.060 align:start position:0% needs to be figured out in a rough consensus<00:20:16.690> style<00:20:16.960> way<00:20:20.790> yeah<00:20:21.790> I<00:20:22.030> am<00:20:23.070> personally 00:20:24.060 --> 00:20:24.070 align:start position:0% consensus style way yeah I am personally 00:20:24.070 --> 00:20:26.220 align:start position:0% consensus style way yeah I am personally I<00:20:24.100> kind<00:20:24.640> of<00:20:24.760> cooled<00:20:25.060> down<00:20:25.240> quite<00:20:25.600> a<00:20:25.630> lot<00:20:25.960> on 00:20:26.220 --> 00:20:26.230 align:start position:0% I kind of cooled down quite a lot on 00:20:26.230 --> 00:20:29.100 align:start position:0% I kind of cooled down quite a lot on this<00:20:26.590> particular<00:20:27.130> issue<00:20:27.490> or<00:20:27.850> last<00:20:28.330> few<00:20:28.840> months 00:20:29.100 --> 00:20:29.110 align:start position:0% this particular issue or last few months 00:20:29.110 --> 00:20:32.640 align:start position:0% this particular issue or last few months I<00:20:29.320> did<00:20:30.190> see<00:20:30.400> a<00:20:30.430> lot<00:20:30.610> of<00:20:30.870> you<00:20:31.870> know<00:20:31.900> discussions 00:20:32.640 --> 00:20:32.650 align:start position:0% I did see a lot of you know discussions 00:20:32.650 --> 00:20:35.400 align:start position:0% I did see a lot of you know discussions a<00:20:32.830> lot<00:20:32.950> of<00:20:33.100> people<00:20:33.480> getting<00:20:34.480> I<00:20:34.840> hope<00:20:35.200> they're 00:20:35.400 --> 00:20:35.410 align:start position:0% a lot of people getting I hope they're 00:20:35.410 --> 00:20:37.860 align:start position:0% a lot of people getting I hope they're getting<00:20:35.650> more<00:20:35.800> informed<00:20:36.280> about<00:20:36.370> this<00:20:36.790> so<00:20:37.600> and 00:20:37.860 --> 00:20:37.870 align:start position:0% getting more informed about this so and 00:20:37.870 --> 00:20:39.630 align:start position:0% getting more informed about this so and I<00:20:37.990> really<00:20:38.020> welcome<00:20:38.620> the<00:20:38.890> audits<00:20:39.370> that 00:20:39.630 --> 00:20:39.640 align:start position:0% I really welcome the audits that 00:20:39.640 --> 00:20:41.600 align:start position:0% I really welcome the audits that happened<00:20:40.030> I<00:20:40.210> read<00:20:40.720> through<00:20:40.990> the<00:20:41.140> audit<00:20:41.380> report 00:20:41.600 --> 00:20:41.610 align:start position:0% happened I read through the audit report 00:20:41.610 --> 00:20:46.440 align:start position:0% happened I read through the audit report yeah<00:20:42.610> I<00:20:42.640> mean<00:20:42.880> I<00:20:43.500> I<00:20:44.500> sort<00:20:45.220> of<00:20:45.310> had<00:20:45.730> my<00:20:45.940> opinions 00:20:46.440 --> 00:20:46.450 align:start position:0% yeah I mean I I sort of had my opinions 00:20:46.450 --> 00:20:48.960 align:start position:0% yeah I mean I I sort of had my opinions I<00:20:46.660> put<00:20:47.140> them<00:20:47.350> out<00:20:47.440> there<00:20:47.500> and<00:20:47.950> I'm<00:20:48.220> happy<00:20:48.940> that 00:20:48.960 --> 00:20:48.970 align:start position:0% I put them out there and I'm happy that 00:20:48.970 --> 00:20:52.530 align:start position:0% I put them out there and I'm happy that you<00:20:49.750> know<00:20:49.780> people<00:20:50.230> were<00:20:50.650> listening<00:20:51.130> and<00:20:51.730> there 00:20:52.530 --> 00:20:52.540 align:start position:0% you know people were listening and there 00:20:52.540 --> 00:20:55.020 align:start position:0% you know people were listening and there was<00:20:52.720> a<00:20:52.750> discussion<00:20:53.320> going<00:20:53.680> on<00:20:53.920> and<00:20:54.610> at<00:20:54.910> the 00:20:55.020 --> 00:20:55.030 align:start position:0% was a discussion going on and at the 00:20:55.030 --> 00:20:57.510 align:start position:0% was a discussion going on and at the mall<00:20:55.150> at<00:20:55.330> this<00:20:55.510> moment<00:20:55.690> I'm<00:20:56.050> you<00:20:56.830> know<00:20:56.950> I'll<00:20:57.310> be 00:20:57.510 --> 00:20:57.520 align:start position:0% mall at this moment I'm you know I'll be 00:20:57.520 --> 00:21:00.480 align:start position:0% mall at this moment I'm you know I'll be okay<00:20:57.550> if<00:20:58.090> it<00:20:58.240> gets<00:20:58.480> implemented<00:20:59.280> rolled<00:21:00.280> out 00:21:00.480 --> 00:21:00.490 align:start position:0% okay if it gets implemented rolled out 00:21:00.490 --> 00:21:03.840 align:start position:0% okay if it gets implemented rolled out and<00:21:01.000> I'm<00:21:01.360> gonna<00:21:01.540> be<00:21:01.720> okay<00:21:01.750> if<00:21:02.110> it<00:21:02.260> doesn't<00:21:02.850> so 00:21:03.840 --> 00:21:03.850 align:start position:0% and I'm gonna be okay if it doesn't so 00:21:03.850 --> 00:21:07.190 align:start position:0% and I'm gonna be okay if it doesn't so I'm<00:21:04.150> not<00:21:04.330> really<00:21:04.840> going<00:21:05.200> to<00:21:05.290> worry<00:21:05.920> about<00:21:06.070> this 00:21:07.190 --> 00:21:07.200 align:start position:0% I'm not really going to worry about this 00:21:07.200 --> 00:21:11.310 align:start position:0% I'm not really going to worry about this so<00:21:08.520> if<00:21:09.520> I'm<00:21:09.760> basically<00:21:10.510> something<00:21:10.930> that<00:21:11.110> I've 00:21:11.310 --> 00:21:11.320 align:start position:0% so if I'm basically something that I've 00:21:11.320 --> 00:21:13.200 align:start position:0% so if I'm basically something that I've said<00:21:11.590> before<00:21:11.740> if<00:21:12.190> I<00:21:12.340> turned<00:21:12.610> out<00:21:12.760> to<00:21:12.790> be<00:21:13.030> wrong 00:21:13.200 --> 00:21:13.210 align:start position:0% said before if I turned out to be wrong 00:21:13.210 --> 00:21:17.460 align:start position:0% said before if I turned out to be wrong that<00:21:13.600> that's<00:21:13.960> fine<00:21:14.230> you<00:21:14.470> know<00:21:15.720> yeah<00:21:16.720> just<00:21:16.930> kind 00:21:17.460 --> 00:21:17.470 align:start position:0% that that's fine you know yeah just kind 00:21:17.470 --> 00:21:19.770 align:start position:0% that that's fine you know yeah just kind of<00:21:17.560> moved<00:21:17.770> on<00:21:17.920> so<00:21:18.610> I<00:21:18.640> think<00:21:18.910> it's<00:21:19.180> made<00:21:19.450> a<00:21:19.480> good 00:21:19.770 --> 00:21:19.780 align:start position:0% of moved on so I think it's made a good 00:21:19.780 --> 00:21:28.370 align:start position:0% of moved on so I think it's made a good progress<00:21:20.020> recently 00:21:28.370 --> 00:21:28.380 align:start position:0% 00:21:28.380 --> 00:21:31.890 align:start position:0% yes<00:21:29.380> I'm<00:21:29.620> one<00:21:30.370> of<00:21:30.490> the<00:21:30.640> core<00:21:31.210> developers<00:21:31.660> or 00:21:31.890 --> 00:21:31.900 align:start position:0% yes I'm one of the core developers or 00:21:31.900 --> 00:21:35.640 align:start position:0% yes I'm one of the core developers or pro<00:21:32.500> rock<00:21:32.920> pal<00:21:33.210> and<00:21:34.210> I've<00:21:34.330> written<00:21:34.510> down<00:21:35.080> my 00:21:35.640 --> 00:21:35.650 align:start position:0% pro rock pal and I've written down my 00:21:35.650 --> 00:21:39.000 align:start position:0% pro rock pal and I've written down my reasons<00:21:36.040> why<00:21:36.190> I<00:21:36.220> believe<00:21:36.790> rock<00:21:37.150> pop<00:21:37.740> is<00:21:38.740> the 00:21:39.000 --> 00:21:39.010 align:start position:0% reasons why I believe rock pop is the 00:21:39.010 --> 00:21:43.410 align:start position:0% reasons why I believe rock pop is the right<00:21:39.310> way<00:21:39.550> forward<00:21:41.400> the<00:21:42.400> way<00:21:42.520> I<00:21:42.550> see<00:21:42.910> it<00:21:42.940> I 00:21:43.410 --> 00:21:43.420 align:start position:0% right way forward the way I see it I 00:21:43.420 --> 00:21:47.310 align:start position:0% right way forward the way I see it I think<00:21:44.380> there's<00:21:44.560> very<00:21:44.980> loud<00:21:45.750> what<00:21:46.750> I<00:21:46.780> perceive 00:21:47.310 --> 00:21:47.320 align:start position:0% think there's very loud what I perceive 00:21:47.320 --> 00:21:51.570 align:start position:0% think there's very loud what I perceive is<00:21:47.470> a<00:21:47.500> very<00:21:47.860> loud<00:21:48.070> minority<00:21:48.760> who<00:21:49.830> is<00:21:50.830> extremely 00:21:51.570 --> 00:21:51.580 align:start position:0% is a very loud minority who is extremely 00:21:51.580 --> 00:21:54.240 align:start position:0% is a very loud minority who is extremely loud<00:21:51.760> and<00:21:52.090> spreading<00:21:52.720> a<00:21:52.750> lot<00:21:52.840> of<00:21:52.990> fear<00:21:53.230> and<00:21:54.010> I 00:21:54.240 --> 00:21:54.250 align:start position:0% loud and spreading a lot of fear and I 00:21:54.250 --> 00:21:56.660 align:start position:0% loud and spreading a lot of fear and I started<00:21:54.640> in<00:21:54.820> doubt<00:21:55.030> about<00:21:55.270> it 00:21:56.660 --> 00:21:56.670 align:start position:0% started in doubt about it 00:21:56.670 --> 00:22:02.190 align:start position:0% started in doubt about it and<00:21:57.670> in<00:21:58.330> my<00:21:58.950> view<00:21:59.950> there<00:22:00.700> has<00:22:00.970> been<00:22:01.330> signaling 00:22:02.190 --> 00:22:02.200 align:start position:0% and in my view there has been signaling 00:22:02.200 --> 00:22:05.610 align:start position:0% and in my view there has been signaling taken<00:22:02.770> from<00:22:03.460> the<00:22:03.610> community<00:22:04.320> there<00:22:05.320> has<00:22:05.350> been 00:22:05.610 --> 00:22:05.620 align:start position:0% taken from the community there has been 00:22:05.620 --> 00:22:07.620 align:start position:0% taken from the community there has been coined<00:22:05.830> about<00:22:06.130> there's<00:22:06.490> been<00:22:06.670> mining<00:22:07.090> votes 00:22:07.620 --> 00:22:07.630 align:start position:0% coined about there's been mining votes 00:22:07.630 --> 00:22:12.630 align:start position:0% coined about there's been mining votes and<00:22:07.960> etc<00:22:08.170> etc<00:22:08.760> so<00:22:09.760> I<00:22:09.790> feel<00:22:10.240> it<00:22:10.690> has<00:22:11.020> been<00:22:11.640> kind 00:22:12.630 --> 00:22:12.640 align:start position:0% and etc etc so I feel it has been kind 00:22:12.640 --> 00:22:19.080 align:start position:0% and etc etc so I feel it has been kind of<00:22:14.700> there<00:22:15.700> has<00:22:15.820> been<00:22:16.270> shown<00:22:16.690> a<00:22:17.640> great<00:22:18.640> support 00:22:19.080 --> 00:22:19.090 align:start position:0% of there has been shown a great support 00:22:19.090 --> 00:22:23.730 align:start position:0% of there has been shown a great support in<00:22:19.210> the<00:22:19.330> community<00:22:21.420> and<00:22:22.420> I<00:22:22.900> don't<00:22:22.960> think<00:22:23.380> this 00:22:23.730 --> 00:22:23.740 align:start position:0% in the community and I don't think this 00:22:23.740 --> 00:22:26.040 align:start position:0% in the community and I don't think this situation<00:22:24.310> has<00:22:24.430> changed<00:22:24.460> from<00:22:25.390> six<00:22:25.960> months 00:22:26.040 --> 00:22:26.050 align:start position:0% situation has changed from six months 00:22:26.050 --> 00:22:28.070 align:start position:0% situation has changed from six months ago 00:22:28.070 --> 00:22:28.080 align:start position:0% ago 00:22:28.080 --> 00:22:31.080 align:start position:0% ago except<00:22:29.080> that<00:22:29.170> at<00:22:29.920> this<00:22:30.220> point<00:22:30.490> in<00:22:30.640> time<00:22:30.820> there 00:22:31.080 --> 00:22:31.090 align:start position:0% except that at this point in time there 00:22:31.090 --> 00:22:34.800 align:start position:0% except that at this point in time there has<00:22:31.180> been<00:22:31.210> a<00:22:31.390> lot<00:22:31.570> more<00:22:32.730> yeah<00:22:33.730> a<00:22:34.030> lot<00:22:34.600> more 00:22:34.800 --> 00:22:34.810 align:start position:0% has been a lot more yeah a lot more 00:22:34.810 --> 00:22:37.470 align:start position:0% has been a lot more yeah a lot more churn<00:22:35.350> from<00:22:35.680> the<00:22:35.770> political<00:22:36.030> side<00:22:37.030> and<00:22:37.330> then 00:22:37.470 --> 00:22:37.480 align:start position:0% churn from the political side and then 00:22:37.480 --> 00:22:44.970 align:start position:0% churn from the political side and then the<00:22:38.910> fun<00:22:39.930> side<00:22:42.270> yeah<00:22:43.270> and<00:22:43.540> I<00:22:43.950> from<00:22:44.950> the 00:22:44.970 --> 00:22:44.980 align:start position:0% the fun side yeah and I from the 00:22:44.980 --> 00:22:47.700 align:start position:0% the fun side yeah and I from the political<00:22:45.310> side<00:22:45.760> I<00:22:46.060> would<00:22:46.150> say<00:22:46.540> that<00:22:46.840> one<00:22:47.170> area 00:22:47.700 --> 00:22:47.710 align:start position:0% political side I would say that one area 00:22:47.710 --> 00:22:50.610 align:start position:0% political side I would say that one area that<00:22:47.770> myself<00:22:48.670> that<00:22:49.510> I<00:22:49.570> fault<00:22:49.810> myself<00:22:49.990> on<00:22:50.440> and 00:22:50.610 --> 00:22:50.620 align:start position:0% that myself that I fault myself on and 00:22:50.620 --> 00:22:52.470 align:start position:0% that myself that I fault myself on and others<00:22:50.860> is<00:22:51.190> there<00:22:52.090> wasn't<00:22:52.240> enough 00:22:52.470 --> 00:22:52.480 align:start position:0% others is there wasn't enough 00:22:52.480 --> 00:22:54.210 align:start position:0% others is there wasn't enough communication<00:22:52.840> people<00:22:53.410> like<00:22:53.650> to<00:22:53.800> be<00:22:53.920> heard 00:22:54.210 --> 00:22:54.220 align:start position:0% communication people like to be heard 00:22:54.220 --> 00:22:56.490 align:start position:0% communication people like to be heard and<00:22:54.400> this<00:22:55.150> kind<00:22:55.420> of<00:22:55.450> got<00:22:55.630> sprung<00:22:55.930> on<00:22:56.110> people 00:22:56.490 --> 00:22:56.500 align:start position:0% and this kind of got sprung on people 00:22:56.500 --> 00:22:59.040 align:start position:0% and this kind of got sprung on people some<00:22:56.920> people<00:22:57.250> because<00:22:57.610> you<00:22:58.420> know<00:22:58.540> who's<00:22:58.870> gonna 00:22:59.040 --> 00:22:59.050 align:start position:0% some people because you know who's gonna 00:22:59.050 --> 00:23:00.690 align:start position:0% some people because you know who's gonna read<00:22:59.320> a<00:22:59.350> transcript<00:23:00.010> of<00:23:00.070> the<00:23:00.190> most<00:23:00.400> boring 00:23:00.690 --> 00:23:00.700 align:start position:0% read a transcript of the most boring 00:23:00.700 --> 00:23:03.660 align:start position:0% read a transcript of the most boring core<00:23:01.060> dev<00:23:01.270> meetings<00:23:01.720> every<00:23:02.050> other<00:23:02.170> week<00:23:02.670> I 00:23:03.660 --> 00:23:03.670 align:start position:0% core dev meetings every other week I 00:23:03.670 --> 00:23:05.100 align:start position:0% core dev meetings every other week I mean<00:23:04.000> it's<00:23:04.150> not<00:23:04.240> boring<00:23:04.510> to<00:23:04.600> everybody<00:23:04.960> but 00:23:05.100 --> 00:23:05.110 align:start position:0% mean it's not boring to everybody but 00:23:05.110 --> 00:23:06.720 align:start position:0% mean it's not boring to everybody but like<00:23:05.290> there's<00:23:05.500> a<00:23:05.590> lot<00:23:05.770> of<00:23:05.920> you<00:23:06.130> know<00:23:06.160> just<00:23:06.550> very 00:23:06.720 --> 00:23:06.730 align:start position:0% like there's a lot of you know just very 00:23:06.730 --> 00:23:08.730 align:start position:0% like there's a lot of you know just very deep<00:23:07.030> technical<00:23:07.360> topics<00:23:07.960> and<00:23:08.140> the<00:23:08.410> average 00:23:08.730 --> 00:23:08.740 align:start position:0% deep technical topics and the average 00:23:08.740 --> 00:23:11.010 align:start position:0% deep technical topics and the average person<00:23:09.130> isn't<00:23:09.280> gonna<00:23:09.430> you<00:23:09.850> know<00:23:09.970> realize<00:23:10.780> that 00:23:11.010 --> 00:23:11.020 align:start position:0% person isn't gonna you know realize that 00:23:11.020 --> 00:23:13.260 align:start position:0% person isn't gonna you know realize that so<00:23:11.200> got<00:23:12.010> sprung<00:23:12.280> on<00:23:12.460> a<00:23:12.490> lot<00:23:12.670> of<00:23:12.700> people<00:23:13.090> and 00:23:13.260 --> 00:23:13.270 align:start position:0% so got sprung on a lot of people and 00:23:13.270 --> 00:23:15.930 align:start position:0% so got sprung on a lot of people and that<00:23:13.720> was<00:23:14.050> a<00:23:14.110> communication<00:23:14.770> error<00:23:15.040> and<00:23:15.220> so 00:23:15.930 --> 00:23:15.940 align:start position:0% that was a communication error and so 00:23:15.940 --> 00:23:18.690 align:start position:0% that was a communication error and so because<00:23:16.390> of<00:23:16.540> that<00:23:16.570> now<00:23:17.070> people<00:23:18.070> are<00:23:18.190> upset 00:23:18.690 --> 00:23:18.700 align:start position:0% because of that now people are upset 00:23:18.700 --> 00:23:20.160 align:start position:0% because of that now people are upset because<00:23:18.880> they<00:23:19.270> felt<00:23:19.540> like<00:23:19.750> they're<00:23:19.960> not<00:23:20.110> being 00:23:20.160 --> 00:23:20.170 align:start position:0% because they felt like they're not being 00:23:20.170 --> 00:23:21.930 align:start position:0% because they felt like they're not being heard<00:23:20.410> now<00:23:20.740> they<00:23:21.040> weren't<00:23:21.310> being<00:23:21.430> heard<00:23:21.520> then 00:23:21.930 --> 00:23:21.940 align:start position:0% heard now they weren't being heard then 00:23:21.940 --> 00:23:23.610 align:start position:0% heard now they weren't being heard then when<00:23:22.180> they<00:23:22.330> felt<00:23:22.630> like<00:23:22.780> they<00:23:22.990> didn't<00:23:23.470> like 00:23:23.610 --> 00:23:23.620 align:start position:0% when they felt like they didn't like 00:23:23.620 --> 00:23:24.960 align:start position:0% when they felt like they didn't like Prague<00:23:23.890> town<00:23:24.100> they<00:23:24.280> thought<00:23:24.490> it<00:23:24.610> was<00:23:24.700> dead 00:23:24.960 --> 00:23:24.970 align:start position:0% Prague town they thought it was dead 00:23:24.970 --> 00:23:26.880 align:start position:0% Prague town they thought it was dead because<00:23:25.330> it<00:23:25.390> wasn't<00:23:25.780> getting<00:23:25.960> implemented<00:23:26.680> as 00:23:26.880 --> 00:23:26.890 align:start position:0% because it wasn't getting implemented as 00:23:26.890 --> 00:23:28.950 align:start position:0% because it wasn't getting implemented as quickly<00:23:27.190> cuz<00:23:27.550> this<00:23:27.640> has<00:23:27.790> been<00:23:27.970> on<00:23:28.240> the<00:23:28.810> radar 00:23:28.950 --> 00:23:28.960 align:start position:0% quickly cuz this has been on the radar 00:23:28.960 --> 00:23:31.920 align:start position:0% quickly cuz this has been on the radar for<00:23:29.170> how<00:23:29.890> many<00:23:30.120> since<00:23:31.120> last<00:23:31.420> don't<00:23:31.780> know 00:23:31.920 --> 00:23:31.930 align:start position:0% for how many since last don't know 00:23:31.930 --> 00:23:34.050 align:start position:0% for how many since last don't know before<00:23:32.080> last<00:23:32.440> DEFCON<00:23:32.920> so<00:23:33.160> since<00:23:33.430> March<00:23:33.820> of 00:23:34.050 --> 00:23:34.060 align:start position:0% before last DEFCON so since March of 00:23:34.060 --> 00:23:37.170 align:start position:0% before last DEFCON so since March of 2018<00:23:35.010> Prague<00:23:36.010> POW<00:23:36.250> has<00:23:36.400> been<00:23:36.580> starting<00:23:37.000> to<00:23:37.090> be 00:23:37.170 --> 00:23:37.180 align:start position:0% 2018 Prague POW has been starting to be 00:23:37.180 --> 00:23:37.980 align:start position:0% 2018 Prague POW has been starting to be implemented<00:23:37.570> talk 00:23:37.980 --> 00:23:37.990 align:start position:0% implemented talk 00:23:37.990 --> 00:23:40.160 align:start position:0% implemented talk about<00:23:38.170> etcetera<00:23:38.679> so<00:23:38.950> it's<00:23:39.070> been<00:23:39.250> a<00:23:39.309> long<00:23:39.460> time 00:23:40.160 --> 00:23:40.170 align:start position:0% about etcetera so it's been a long time 00:23:40.170 --> 00:23:43.020 align:start position:0% about etcetera so it's been a long time so<00:23:41.170> I<00:23:41.200> think<00:23:41.530> if<00:23:41.890> we<00:23:41.980> can<00:23:42.190> have<00:23:42.580> people<00:23:42.910> be 00:23:43.020 --> 00:23:43.030 align:start position:0% so I think if we can have people be 00:23:43.030 --> 00:23:45.630 align:start position:0% so I think if we can have people be heard<00:23:43.270> that's<00:23:43.510> going<00:23:43.809> to<00:23:44.160> heal<00:23:45.160> a<00:23:45.190> lot<00:23:45.400> of<00:23:45.550> the 00:23:45.630 --> 00:23:45.640 align:start position:0% heard that's going to heal a lot of the 00:23:45.640 --> 00:23:47.430 align:start position:0% heard that's going to heal a lot of the wounds<00:23:46.059> and<00:23:46.300> start<00:23:46.690> to<00:23:46.780> get<00:23:46.870> us<00:23:46.990> more<00:23:47.140> toward<00:23:47.410> a 00:23:47.430 --> 00:23:47.440 align:start position:0% wounds and start to get us more toward a 00:23:47.440 --> 00:23:49.410 align:start position:0% wounds and start to get us more toward a rough<00:23:47.590> consensus<00:23:48.220> and<00:23:48.460> I<00:23:48.970> welcome<00:23:49.210> people 00:23:49.410 --> 00:23:49.420 align:start position:0% rough consensus and I welcome people 00:23:49.420 --> 00:23:50.940 align:start position:0% rough consensus and I welcome people from<00:23:49.690> the<00:23:49.809> audience<00:23:50.200> if<00:23:50.350> you<00:23:50.380> have<00:23:50.530> an<00:23:50.620> opinion 00:23:50.940 --> 00:23:50.950 align:start position:0% from the audience if you have an opinion 00:23:50.950 --> 00:23:52.320 align:start position:0% from the audience if you have an opinion on<00:23:51.070> this<00:23:51.220> you<00:23:51.370> can<00:23:51.490> go<00:23:51.580> sit<00:23:51.790> in<00:23:51.910> this<00:23:52.000> chair<00:23:52.059> and 00:23:52.320 --> 00:23:52.330 align:start position:0% on this you can go sit in this chair and 00:23:52.330 --> 00:23:55.260 align:start position:0% on this you can go sit in this chair and like<00:23:52.950> you<00:23:53.950> know<00:23:54.070> give<00:23:54.490> your<00:23:54.640> opinion<00:23:55.090> or 00:23:55.260 --> 00:23:55.270 align:start position:0% like you know give your opinion or 00:23:55.270 --> 00:23:58.260 align:start position:0% like you know give your opinion or whatnot<00:23:55.710> and<00:23:56.710> otherwise<00:23:57.250> anyone<00:23:57.820> else<00:23:58.000> we<00:23:58.150> can 00:23:58.260 --> 00:23:58.270 align:start position:0% whatnot and otherwise anyone else we can 00:23:58.270 --> 00:24:02.640 align:start position:0% whatnot and otherwise anyone else we can go<00:23:58.360> to<00:23:58.450> another<00:23:58.540> topic<00:24:01.230> one<00:24:02.230> thing<00:24:02.440> that<00:24:02.559> I'd 00:24:02.640 --> 00:24:02.650 align:start position:0% go to another topic one thing that I'd 00:24:02.650 --> 00:24:05.549 align:start position:0% go to another topic one thing that I'd like<00:24:02.830> to<00:24:02.890> point<00:24:03.070> out<00:24:03.190> is<00:24:03.400> um<00:24:03.610> intro<00:24:04.320> my<00:24:05.320> name<00:24:05.350> is 00:24:05.549 --> 00:24:05.559 align:start position:0% like to point out is um intro my name is 00:24:05.559 --> 00:24:07.020 align:start position:0% like to point out is um intro my name is Dan<00:24:05.710> affarin<00:24:06.160> I'm<00:24:06.280> picking<00:24:06.580> my<00:24:06.670> son<00:24:06.850> up<00:24:06.940> from 00:24:07.020 --> 00:24:07.030 align:start position:0% Dan affarin I'm picking my son up from 00:24:07.030 --> 00:24:11.580 align:start position:0% Dan affarin I'm picking my son up from school<00:24:09.809> one<00:24:10.809> of<00:24:10.900> things<00:24:11.020> that<00:24:11.080> have<00:24:11.230> noticed 00:24:11.580 --> 00:24:11.590 align:start position:0% school one of things that have noticed 00:24:11.590 --> 00:24:12.990 align:start position:0% school one of things that have noticed within<00:24:11.770> the<00:24:11.920> past<00:24:12.100> six<00:24:12.280> to<00:24:12.490> eight<00:24:12.610> months<00:24:12.880> with 00:24:12.990 --> 00:24:13.000 align:start position:0% within the past six to eight months with 00:24:13.000 --> 00:24:15.330 align:start position:0% within the past six to eight months with this<00:24:13.120> is<00:24:13.870> there's<00:24:14.110> been<00:24:14.290> a<00:24:14.320> notable<00:24:14.620> drop<00:24:15.130> in 00:24:15.330 --> 00:24:15.340 align:start position:0% this is there's been a notable drop in 00:24:15.340 --> 00:24:17.370 align:start position:0% this is there's been a notable drop in civility<00:24:15.850> in<00:24:16.179> the<00:24:16.510> arguments<00:24:16.960> relating<00:24:17.320> to 00:24:17.370 --> 00:24:17.380 align:start position:0% civility in the arguments relating to 00:24:17.380 --> 00:24:19.530 align:start position:0% civility in the arguments relating to prog<00:24:17.559> pal<00:24:17.800> and<00:24:18.760> the<00:24:18.910> problem<00:24:19.150> with<00:24:19.240> this<00:24:19.330> drop 00:24:19.530 --> 00:24:19.540 align:start position:0% prog pal and the problem with this drop 00:24:19.540 --> 00:24:21.240 align:start position:0% prog pal and the problem with this drop in<00:24:19.660> civility<00:24:20.080> is<00:24:20.260> people<00:24:20.620> start<00:24:20.980> closing 00:24:21.240 --> 00:24:21.250 align:start position:0% in civility is people start closing 00:24:21.250 --> 00:24:23.640 align:start position:0% in civility is people start closing their<00:24:21.370> ears<00:24:21.750> and<00:24:22.750> there<00:24:22.900> are<00:24:23.020> principled 00:24:23.640 --> 00:24:23.650 align:start position:0% their ears and there are principled 00:24:23.650 --> 00:24:25.650 align:start position:0% their ears and there are principled people<00:24:24.010> with<00:24:24.130> real<00:24:24.429> solid<00:24:24.880> objections<00:24:25.330> to<00:24:25.510> it 00:24:25.650 --> 00:24:25.660 align:start position:0% people with real solid objections to it 00:24:25.660 --> 00:24:28.230 align:start position:0% people with real solid objections to it who<00:24:26.290> get<00:24:26.559> lumped<00:24:27.280> together<00:24:27.370> with<00:24:27.970> some<00:24:28.179> of 00:24:28.230 --> 00:24:28.240 align:start position:0% who get lumped together with some of 00:24:28.240 --> 00:24:30.000 align:start position:0% who get lumped together with some of these<00:24:28.300> people<00:24:28.510> spouting<00:24:28.900> these<00:24:29.200> crazy<00:24:29.679> things 00:24:30.000 --> 00:24:30.010 align:start position:0% these people spouting these crazy things 00:24:30.010 --> 00:24:32.669 align:start position:0% these people spouting these crazy things and<00:24:30.420> that's<00:24:31.420> doing<00:24:31.720> a<00:24:31.870> disservice<00:24:32.080> to<00:24:32.260> the 00:24:32.669 --> 00:24:32.679 align:start position:0% and that's doing a disservice to the 00:24:32.679 --> 00:24:34.980 align:start position:0% and that's doing a disservice to the dialogue<00:24:33.070> to<00:24:33.700> be<00:24:33.820> uncivil<00:24:34.330> and<00:24:34.510> to<00:24:34.660> be<00:24:34.750> rude 00:24:34.980 --> 00:24:34.990 align:start position:0% dialogue to be uncivil and to be rude 00:24:34.990 --> 00:24:37.830 align:start position:0% dialogue to be uncivil and to be rude and<00:24:35.260> to<00:24:35.410> be<00:24:35.530> crude<00:24:35.770> to<00:24:35.920> everyone<00:24:36.340> and<00:24:36.550> to<00:24:37.300> send 00:24:37.830 --> 00:24:37.840 align:start position:0% and to be crude to everyone and to send 00:24:37.840 --> 00:24:39.299 align:start position:0% and to be crude to everyone and to send all<00:24:37.990> sorts<00:24:38.260> of<00:24:38.320> weird<00:24:38.530> veiled<00:24:38.860> threats<00:24:39.190> to 00:24:39.299 --> 00:24:39.309 align:start position:0% all sorts of weird veiled threats to 00:24:39.309 --> 00:24:47.390 align:start position:0% all sorts of weird veiled threats to people<00:24:39.610> that's<00:24:40.150> just<00:24:40.270> not<00:24:40.540> cool<00:24:42.480> yeah<00:24:43.480> I<00:24:43.510> agree 00:24:47.390 --> 00:24:47.400 align:start position:0% 00:24:47.400 --> 00:24:49.620 align:start position:0% yeah<00:24:48.400> I<00:24:48.429> think<00:24:48.580> I<00:24:48.790> want<00:24:48.970> to<00:24:49.030> want<00:24:49.330> to<00:24:49.360> echo 00:24:49.620 --> 00:24:49.630 align:start position:0% yeah I think I want to want to echo 00:24:49.630 --> 00:24:52.169 align:start position:0% yeah I think I want to want to echo Dinos<00:24:49.900> statement<00:24:50.559> I'm<00:24:50.950> Adrian<00:24:51.309> Sutton 00:24:52.169 --> 00:24:52.179 align:start position:0% Dinos statement I'm Adrian Sutton 00:24:52.179 --> 00:24:56.130 align:start position:0% Dinos statement I'm Adrian Sutton work<00:24:53.050> on<00:24:53.200> Basu<00:24:53.530> I<00:24:54.240> think<00:24:55.240> one<00:24:55.780> of<00:24:55.809> the<00:24:55.929> things 00:24:56.130 --> 00:24:56.140 align:start position:0% work on Basu I think one of the things 00:24:56.140 --> 00:24:58.200 align:start position:0% work on Basu I think one of the things that's<00:24:56.290> very<00:24:56.410> dangerous<00:24:57.070> in<00:24:57.309> this<00:24:57.520> for<00:24:58.059> the 00:24:58.200 --> 00:24:58.210 align:start position:0% that's very dangerous in this for the 00:24:58.210 --> 00:25:00.000 align:start position:0% that's very dangerous in this for the whole<00:24:58.360> etherion<00:24:58.900> community<00:24:59.350> is<00:24:59.559> that<00:24:59.800> if<00:24:59.890> we 00:25:00.000 --> 00:25:00.010 align:start position:0% whole etherion community is that if we 00:25:00.010 --> 00:25:03.080 align:start position:0% whole etherion community is that if we set<00:25:00.220> a<00:25:00.250> precedent<00:25:00.880> where<00:25:01.750> you<00:25:02.260> can<00:25:02.559> shoot<00:25:02.860> down 00:25:03.080 --> 00:25:03.090 align:start position:0% set a precedent where you can shoot down 00:25:03.090 --> 00:25:07.830 align:start position:0% set a precedent where you can shoot down something<00:25:04.090> by<00:25:05.400> attacking<00:25:06.400> someone<00:25:07.360> proposing 00:25:07.830 --> 00:25:07.840 align:start position:0% something by attacking someone proposing 00:25:07.840 --> 00:25:09.570 align:start position:0% something by attacking someone proposing it<00:25:07.929> personally<00:25:08.410> then<00:25:08.950> we're<00:25:09.040> gonna<00:25:09.130> see<00:25:09.340> a<00:25:09.370> lot 00:25:09.570 --> 00:25:09.580 align:start position:0% it personally then we're gonna see a lot 00:25:09.580 --> 00:25:12.030 align:start position:0% it personally then we're gonna see a lot more<00:25:09.640> of<00:25:09.910> that<00:25:09.940> in<00:25:10.150> the<00:25:10.210> future<00:25:10.360> so<00:25:11.200> I'm<00:25:11.559> really 00:25:12.030 --> 00:25:12.040 align:start position:0% more of that in the future so I'm really 00:25:12.040 --> 00:25:15.780 align:start position:0% more of that in the future so I'm really keen<00:25:12.309> to<00:25:12.340> hear<00:25:12.900> technical<00:25:13.900> concerns<00:25:14.520> and<00:25:15.520> that 00:25:15.780 --> 00:25:15.790 align:start position:0% keen to hear technical concerns and that 00:25:15.790 --> 00:25:17.520 align:start position:0% keen to hear technical concerns and that that<00:25:16.179> includes<00:25:16.450> some<00:25:16.600> politics<00:25:17.020> of<00:25:17.200> do<00:25:17.410> we 00:25:17.520 --> 00:25:17.530 align:start position:0% that includes some politics of do we 00:25:17.530 --> 00:25:19.290 align:start position:0% that includes some politics of do we actually<00:25:17.679> want<00:25:18.040> to<00:25:18.130> be<00:25:18.340> a<00:25:18.490> Sikh<00:25:18.790> friendly<00:25:19.090> is 00:25:19.290 --> 00:25:19.300 align:start position:0% actually want to be a Sikh friendly is 00:25:19.300 --> 00:25:21.660 align:start position:0% actually want to be a Sikh friendly is that<00:25:19.690> that<00:25:20.320> direction<00:25:20.590> we<00:25:20.770> want<00:25:20.920> to<00:25:20.950> go<00:25:21.010> those 00:25:21.660 --> 00:25:21.670 align:start position:0% that that direction we want to go those 00:25:21.670 --> 00:25:23.640 align:start position:0% that that direction we want to go those arguments<00:25:22.059> I'm<00:25:22.420> all<00:25:22.809> for<00:25:23.020> I<00:25:23.080> really<00:25:23.350> want<00:25:23.590> to 00:25:23.640 --> 00:25:23.650 align:start position:0% arguments I'm all for I really want to 00:25:23.650 --> 00:25:26.640 align:start position:0% arguments I'm all for I really want to hear<00:25:23.830> but<00:25:24.010> when<00:25:24.190> we<00:25:24.309> start<00:25:24.640> diving<00:25:25.120> into<00:25:25.650> this 00:25:26.640 --> 00:25:26.650 align:start position:0% hear but when we start diving into this 00:25:26.650 --> 00:25:28.590 align:start position:0% hear but when we start diving into this person<00:25:27.220> was<00:25:27.340> associated<00:25:27.730> with<00:25:27.910> that<00:25:28.210> or 00:25:28.590 --> 00:25:28.600 align:start position:0% person was associated with that or 00:25:28.600 --> 00:25:31.410 align:start position:0% person was associated with that or they're<00:25:29.080> corrupt<00:25:29.530> or<00:25:29.860> their<00:25:30.100> and<00:25:31.059> not 00:25:31.410 --> 00:25:31.420 align:start position:0% they're corrupt or their and not 00:25:31.420 --> 00:25:33.299 align:start position:0% they're corrupt or their and not actually<00:25:31.840> being<00:25:31.990> able<00:25:32.110> to<00:25:32.260> point<00:25:32.470> to<00:25:32.710> this<00:25:33.250> is 00:25:33.299 --> 00:25:33.309 align:start position:0% actually being able to point to this is 00:25:33.309 --> 00:25:36.210 align:start position:0% actually being able to point to this is what<00:25:33.700> they're<00:25:33.880> trying<00:25:34.030> to<00:25:34.240> do<00:25:34.450> so<00:25:34.980> if<00:25:35.980> you've 00:25:36.210 --> 00:25:36.220 align:start position:0% what they're trying to do so if you've 00:25:36.220 --> 00:25:37.500 align:start position:0% what they're trying to do so if you've got<00:25:36.370> a<00:25:36.400> problem<00:25:36.550> with<00:25:36.670> Proctor<00:25:36.970> and<00:25:37.240> you<00:25:37.300> think 00:25:37.500 --> 00:25:37.510 align:start position:0% got a problem with Proctor and you think 00:25:37.510 --> 00:25:39.840 align:start position:0% got a problem with Proctor and you think it's<00:25:37.660> all<00:25:37.750> great<00:25:37.900> scam<00:25:38.260> then<00:25:38.920> great<00:25:39.550> let's 00:25:39.840 --> 00:25:39.850 align:start position:0% it's all great scam then great let's 00:25:39.850 --> 00:25:42.240 align:start position:0% it's all great scam then great let's hear<00:25:40.059> exactly<00:25:40.450> what<00:25:40.630> the<00:25:40.870> scam<00:25:41.110> is<00:25:41.290> not<00:25:41.530> just<00:25:42.010> a 00:25:42.240 --> 00:25:42.250 align:start position:0% hear exactly what the scam is not just a 00:25:42.250 --> 00:25:44.370 align:start position:0% hear exactly what the scam is not just a vague<00:25:42.850> thing<00:25:43.300> where<00:25:43.480> we're<00:25:43.630> we're<00:25:43.929> slandering 00:25:44.370 --> 00:25:44.380 align:start position:0% vague thing where we're we're slandering 00:25:44.380 --> 00:25:47.159 align:start position:0% vague thing where we're we're slandering personalities<00:25:45.010> because<00:25:45.370> that<00:25:45.580> leads<00:25:45.850> to<00:25:46.210> more 00:25:47.159 --> 00:25:47.169 align:start position:0% personalities because that leads to more 00:25:47.169 --> 00:25:49.879 align:start position:0% personalities because that leads to more and<00:25:47.230> more<00:25:47.760> attacking<00:25:48.760> people 00:25:49.879 --> 00:25:49.889 align:start position:0% and more attacking people 00:25:49.889 --> 00:25:52.090 align:start position:0% and more attacking people which<00:25:50.369> makes<00:25:50.580> it<00:25:50.730> incredibly<00:25:50.850> difficult<00:25:51.389> for 00:25:52.090 --> 00:25:52.100 align:start position:0% which makes it incredibly difficult for 00:25:52.100 --> 00:25:54.499 align:start position:0% which makes it incredibly difficult for people<00:25:53.100> to<00:25:53.309> stand<00:25:53.460> up<00:25:53.639> and<00:25:53.789> make<00:25:53.970> proposals 00:25:54.499 --> 00:25:54.509 align:start position:0% people to stand up and make proposals 00:25:54.509 --> 00:25:56.119 align:start position:0% people to stand up and make proposals and<00:25:54.659> be<00:25:54.749> involved<00:25:55.080> in<00:25:55.169> the<00:25:55.230> community<00:25:55.619> we've 00:25:56.119 --> 00:25:56.129 align:start position:0% and be involved in the community we've 00:25:56.129 --> 00:25:57.529 align:start position:0% and be involved in the community we've lost<00:25:56.429> people<00:25:56.669> in<00:25:56.879> the<00:25:56.970> community<00:25:57.330> who<00:25:57.450> would 00:25:57.529 --> 00:25:57.539 align:start position:0% lost people in the community who would 00:25:57.539 --> 00:25:59.570 align:start position:0% lost people in the community who would diluent<00:25:57.899> great<00:25:58.350> work<00:25:58.590> because<00:25:59.220> they've<00:25:59.429> been 00:25:59.570 --> 00:25:59.580 align:start position:0% diluent great work because they've been 00:25:59.580 --> 00:26:01.609 align:start position:0% diluent great work because they've been attacked<00:25:59.909> personally<00:26:00.119> in<00:26:00.539> the<00:26:00.629> past<00:26:00.840> we<00:26:01.499> don't 00:26:01.609 --> 00:26:01.619 align:start position:0% attacked personally in the past we don't 00:26:01.619 --> 00:26:02.570 align:start position:0% attacked personally in the past we don't want<00:26:01.799> to<00:26:01.860> see<00:26:01.919> that<00:26:02.070> happening<00:26:02.369> in<00:26:02.489> the<00:26:02.519> future 00:26:02.570 --> 00:26:02.580 align:start position:0% want to see that happening in the future 00:26:02.580 --> 00:26:11.180 align:start position:0% want to see that happening in the future just<00:26:08.840> to<00:26:09.840> add<00:26:09.929> my<00:26:10.139> two<00:26:10.200> cents<00:26:10.649> this<00:26:10.950> whole 00:26:11.180 --> 00:26:11.190 align:start position:0% just to add my two cents this whole 00:26:11.190 --> 00:26:14.629 align:start position:0% just to add my two cents this whole proper<00:26:11.669> vs.<00:26:12.059> Edie<00:26:12.299> Hodge<00:26:12.450> discussion<00:26:13.049> I<00:26:13.739> think 00:26:14.629 --> 00:26:14.639 align:start position:0% proper vs. Edie Hodge discussion I think 00:26:14.639 --> 00:26:19.279 align:start position:0% proper vs. Edie Hodge discussion I think one<00:26:15.090> of<00:26:15.119> the<00:26:16.220> so<00:26:17.389> currently<00:26:18.389> my<00:26:18.539> feeling<00:26:19.139> is 00:26:19.279 --> 00:26:19.289 align:start position:0% one of the so currently my feeling is 00:26:19.289 --> 00:26:21.919 align:start position:0% one of the so currently my feeling is that<00:26:19.320> the<00:26:19.889> whole<00:26:20.340> discussion<00:26:20.669> boils<00:26:21.090> around<00:26:21.419> a 00:26:21.919 --> 00:26:21.929 align:start position:0% that the whole discussion boils around a 00:26:21.929 --> 00:26:23.989 align:start position:0% that the whole discussion boils around a sick<00:26:22.799> whether<00:26:23.009> we<00:26:23.159> want<00:26:23.340> to<00:26:23.460> be<00:26:23.519> a<00:26:23.580> secure 00:26:23.989 --> 00:26:23.999 align:start position:0% sick whether we want to be a secure 00:26:23.999 --> 00:26:25.729 align:start position:0% sick whether we want to be a secure distant<00:26:24.389> or<00:26:24.570> not<00:26:24.779> and<00:26:25.200> I<00:26:25.320> think<00:26:25.499> this<00:26:25.619> is 00:26:25.729 --> 00:26:25.739 align:start position:0% distant or not and I think this is 00:26:25.739 --> 00:26:27.289 align:start position:0% distant or not and I think this is something<00:26:25.950> that<00:26:26.190> kind<00:26:26.369> of<00:26:26.519> just<00:26:26.820> is<00:26:26.940> tearing 00:26:27.289 --> 00:26:27.299 align:start position:0% something that kind of just is tearing 00:26:27.299 --> 00:26:30.440 align:start position:0% something that kind of just is tearing the<00:26:27.389> whole<00:26:27.480> community<00:26:27.929> apart<00:26:28.289> and<00:26:28.499> I<00:26:29.309> from<00:26:30.299> my 00:26:30.440 --> 00:26:30.450 align:start position:0% the whole community apart and I from my 00:26:30.450 --> 00:26:32.590 align:start position:0% the whole community apart and I from my personal<00:26:30.899> perspective<00:26:31.019> I<00:26:31.470> don't<00:26:31.679> really<00:26:31.889> see 00:26:32.590 --> 00:26:32.600 align:start position:0% personal perspective I don't really see 00:26:32.600 --> 00:26:36.080 align:start position:0% personal perspective I don't really see what's<00:26:33.600> the<00:26:33.779> whole<00:26:33.929> point<00:26:34.259> of<00:26:34.759> office<00:26:35.759> so 00:26:36.080 --> 00:26:36.090 align:start position:0% what's the whole point of office so 00:26:36.090 --> 00:26:38.749 align:start position:0% what's the whole point of office so currently<00:26:36.480> we<00:26:37.200> have<00:26:37.230> a<00:26:37.379> few<00:26:37.619> big<00:26:38.159> mining<00:26:38.519> pools 00:26:38.749 --> 00:26:38.759 align:start position:0% currently we have a few big mining pools 00:26:38.759 --> 00:26:41.779 align:start position:0% currently we have a few big mining pools now<00:26:38.940> if<00:26:39.210> we<00:26:39.899> have<00:26:40.049> an<00:26:40.200> ASIC<00:26:40.559> friendly<00:26:40.919> mining 00:26:41.779 --> 00:26:41.789 align:start position:0% now if we have an ASIC friendly mining 00:26:41.789 --> 00:26:43.700 align:start position:0% now if we have an ASIC friendly mining algorithm<00:26:42.299> then<00:26:42.509> probably<00:26:43.169> we<00:26:43.379> will<00:26:43.499> have 00:26:43.700 --> 00:26:43.710 align:start position:0% algorithm then probably we will have 00:26:43.710 --> 00:26:45.470 align:start position:0% algorithm then probably we will have some<00:26:43.980> manufacturers<00:26:44.669> that<00:26:44.879> make<00:26:45.059> a<00:26:45.090> killing 00:26:45.470 --> 00:26:45.480 align:start position:0% some manufacturers that make a killing 00:26:45.480 --> 00:26:47.810 align:start position:0% some manufacturers that make a killing out<00:26:45.600> of<00:26:45.779> it<00:26:45.960> and<00:26:46.169> some<00:26:46.470> mining<00:26:46.799> pools<00:26:47.070> now<00:26:47.639> if 00:26:47.810 --> 00:26:47.820 align:start position:0% out of it and some mining pools now if 00:26:47.820 --> 00:26:50.090 align:start position:0% out of it and some mining pools now if we<00:26:47.940> have<00:26:48.090> an<00:26:48.299> ASIC<00:26:48.769> resistant<00:26:49.769> mining 00:26:50.090 --> 00:26:50.100 align:start position:0% we have an ASIC resistant mining 00:26:50.100 --> 00:26:51.680 align:start position:0% we have an ASIC resistant mining algorithm<00:26:50.609> probably<00:26:51.059> there<00:26:51.239> will<00:26:51.330> be<00:26:51.389> some 00:26:51.680 --> 00:26:51.690 align:start position:0% algorithm probably there will be some 00:26:51.690 --> 00:26:53.029 align:start position:0% algorithm probably there will be some different<00:26:52.019> mining<00:26:52.289> pools<00:26:52.529> and<00:26:52.710> different 00:26:53.029 --> 00:26:53.039 align:start position:0% different mining pools and different 00:26:53.039 --> 00:26:55.340 align:start position:0% different mining pools and different hardware<00:26:53.970> vendors<00:26:54.299> making<00:26:54.690> a<00:26:54.779> killing<00:26:54.960> out<00:26:55.200> of 00:26:55.340 --> 00:26:55.350 align:start position:0% hardware vendors making a killing out of 00:26:55.350 --> 00:26:58.369 align:start position:0% hardware vendors making a killing out of it<00:26:55.499> but<00:26:56.039> essentially<00:26:56.989> from<00:26:57.989> my<00:26:58.109> perspective 00:26:58.369 --> 00:26:58.379 align:start position:0% it but essentially from my perspective 00:26:58.379 --> 00:27:00.169 align:start position:0% it but essentially from my perspective currently<00:26:59.039> we're<00:26:59.190> just<00:26:59.429> trying<00:26:59.700> to<00:26:59.759> decide 00:27:00.169 --> 00:27:00.179 align:start position:0% currently we're just trying to decide 00:27:00.179 --> 00:27:02.450 align:start position:0% currently we're just trying to decide who<00:27:00.690> we<00:27:00.899> want<00:27:01.109> to<00:27:01.259> give<00:27:01.409> our<00:27:01.559> money<00:27:01.769> to<00:27:01.919> for 00:27:02.450 --> 00:27:02.460 align:start position:0% who we want to give our money to for 00:27:02.460 --> 00:27:06.139 align:start position:0% who we want to give our money to for mining<00:27:02.789> or<00:27:02.999> for<00:27:03.980> creating<00:27:04.980> that<00:27:05.100> hardware<00:27:05.580> now 00:27:06.139 --> 00:27:06.149 align:start position:0% mining or for creating that hardware now 00:27:06.149 --> 00:27:08.859 align:start position:0% mining or for creating that hardware now if<00:27:06.480> on<00:27:07.200> the<00:27:07.379> other<00:27:07.470> hand<00:27:07.590> we<00:27:08.070> can<00:27:08.309> actually 00:27:08.859 --> 00:27:08.869 align:start position:0% if on the other hand we can actually 00:27:08.869 --> 00:27:11.690 align:start position:0% if on the other hand we can actually technically<00:27:09.869> say<00:27:10.139> that<00:27:10.379> one<00:27:11.159> of<00:27:11.309> them<00:27:11.519> is 00:27:11.690 --> 00:27:11.700 align:start position:0% technically say that one of them is 00:27:11.700 --> 00:27:14.090 align:start position:0% technically say that one of them is dangerous<00:27:12.330> or<00:27:12.840> one<00:27:12.989> of<00:27:13.139> them<00:27:13.379> or<00:27:13.769> we<00:27:13.950> can 00:27:14.090 --> 00:27:14.100 align:start position:0% dangerous or one of them or we can 00:27:14.100 --> 00:27:16.580 align:start position:0% dangerous or one of them or we can somehow<00:27:14.399> prove<00:27:14.759> that<00:27:14.970> yes<00:27:15.269> et<00:27:15.629> hash<00:27:15.840> is<00:27:16.529> a 00:27:16.580 --> 00:27:16.590 align:start position:0% somehow prove that yes et hash is a 00:27:16.590 --> 00:27:18.710 align:start position:0% somehow prove that yes et hash is a security<00:27:17.340> issue<00:27:17.369> and<00:27:17.879> we<00:27:18.239> can<00:27:18.450> prove<00:27:18.659> that 00:27:18.710 --> 00:27:18.720 align:start position:0% security issue and we can prove that 00:27:18.720 --> 00:27:20.899 align:start position:0% security issue and we can prove that publicly<00:27:19.320> then<00:27:19.859> all<00:27:20.009> of<00:27:20.039> a<00:27:20.220> sudden<00:27:20.249> probably 00:27:20.899 --> 00:27:20.909 align:start position:0% publicly then all of a sudden probably 00:27:20.909 --> 00:27:22.609 align:start position:0% publicly then all of a sudden probably the<00:27:21.029> entire<00:27:21.090> community<00:27:21.509> would<00:27:21.929> shift<00:27:22.169> towards 00:27:22.609 --> 00:27:22.619 align:start position:0% the entire community would shift towards 00:27:22.619 --> 00:27:24.859 align:start position:0% the entire community would shift towards the<00:27:22.710> other<00:27:22.859> one<00:27:23.070> so<00:27:23.549> if<00:27:23.730> as<00:27:23.909> long<00:27:24.239> so<00:27:24.720> if 00:27:24.859 --> 00:27:24.869 align:start position:0% the other one so if as long so if 00:27:24.869 --> 00:27:27.049 align:start position:0% the other one so if as long so if there's<00:27:25.139> a<00:27:25.350> threat<00:27:25.799> to<00:27:26.070> the<00:27:26.159> network<00:27:26.519> I<00:27:26.730> think 00:27:27.049 --> 00:27:27.059 align:start position:0% there's a threat to the network I think 00:27:27.059 --> 00:27:28.970 align:start position:0% there's a threat to the network I think then<00:27:27.239> the<00:27:27.269> whole<00:27:27.570> discussion<00:27:28.019> is<00:27:28.230> decided<00:27:28.769> and 00:27:28.970 --> 00:27:28.980 align:start position:0% then the whole discussion is decided and 00:27:28.980 --> 00:27:31.129 align:start position:0% then the whole discussion is decided and if<00:27:29.519> there's<00:27:29.730> no<00:27:29.940> threat<00:27:30.239> to<00:27:30.269> the<00:27:30.450> network<00:27:30.840> then 00:27:31.129 --> 00:27:31.139 align:start position:0% if there's no threat to the network then 00:27:31.139 --> 00:27:33.619 align:start position:0% if there's no threat to the network then it's<00:27:31.499> it's<00:27:32.190> kind<00:27:32.609> of<00:27:32.669> just<00:27:33.330> a<00:27:33.480> heated 00:27:33.619 --> 00:27:33.629 align:start position:0% it's it's kind of just a heated 00:27:33.629 --> 00:27:35.810 align:start position:0% it's it's kind of just a heated political<00:27:33.929> thing<00:27:34.499> of<00:27:34.679> who<00:27:35.009> gets<00:27:35.249> to<00:27:35.429> make<00:27:35.549> more 00:27:35.810 --> 00:27:35.820 align:start position:0% political thing of who gets to make more 00:27:35.820 --> 00:27:38.210 align:start position:0% political thing of who gets to make more money<00:27:35.999> out<00:27:36.210> of<00:27:36.239> it<00:27:36.480> and<00:27:36.749> that's<00:27:37.169> not<00:27:37.529> going<00:27:38.009> too 00:27:38.210 --> 00:27:38.220 align:start position:0% money out of it and that's not going too 00:27:38.220 --> 00:27:42.160 align:start position:0% money out of it and that's not going too far<00:27:38.429> too<00:27:39.119> fast 00:27:42.160 --> 00:27:42.170 align:start position:0% 00:27:42.170 --> 00:27:48.820 align:start position:0% I<00:27:46.600> do<00:27:47.600> we<00:27:47.750> have<00:27:47.840> a<00:27:47.870> next<00:27:47.990> topic<00:27:48.470> or<00:27:48.590> somebody 00:27:48.820 --> 00:27:48.830 align:start position:0% I do we have a next topic or somebody 00:27:48.830 --> 00:27:50.110 align:start position:0% I do we have a next topic or somebody wants<00:27:49.040> to<00:27:49.100> discuss<00:27:49.430> something<00:27:49.640> yeah<00:27:49.820> come<00:27:50.060> on 00:27:50.110 --> 00:27:50.120 align:start position:0% wants to discuss something yeah come on 00:27:50.120 --> 00:27:52.090 align:start position:0% wants to discuss something yeah come on up<00:27:50.300> you<00:27:50.540> can<00:27:51.170> come<00:27:51.320> on<00:27:51.440> up<00:27:51.470> before<00:27:51.830> we're<00:27:51.980> done 00:27:52.090 --> 00:27:52.100 align:start position:0% up you can come on up before we're done 00:27:52.100 --> 00:27:53.590 align:start position:0% up you can come on up before we're done talking<00:27:52.460> about<00:27:52.610> the<00:27:52.730> next<00:27:52.940> topic<00:27:53.120> by<00:27:53.360> the<00:27:53.420> way 00:27:53.590 --> 00:27:53.600 align:start position:0% talking about the next topic by the way 00:27:53.600 --> 00:27:55.150 align:start position:0% talking about the next topic by the way and<00:27:53.750> just<00:27:53.870> grab<00:27:54.050> a<00:27:54.080> mic<00:27:54.320> so<00:27:54.530> we<00:27:54.560> know<00:27:54.800> the<00:27:54.980> next 00:27:55.150 --> 00:27:55.160 align:start position:0% and just grab a mic so we know the next 00:27:55.160 --> 00:27:58.260 align:start position:0% and just grab a mic so we know the next one's<00:27:55.370> ready<00:27:55.580> all<00:27:56.360> right<00:27:56.510> hey<00:27:56.810> I'm<00:27:57.380> Fernando 00:27:58.260 --> 00:27:58.270 align:start position:0% one's ready all right hey I'm Fernando 00:27:58.270 --> 00:28:00.640 align:start position:0% one's ready all right hey I'm Fernando what's<00:27:59.270> the<00:27:59.360> deal<00:27:59.510> what<00:27:59.720> state<00:28:00.080> rent<00:28:00.320> where 00:28:00.640 --> 00:28:00.650 align:start position:0% what's the deal what state rent where 00:28:00.650 --> 00:28:02.220 align:start position:0% what's the deal what state rent where are<00:28:00.710> we<00:28:00.800> at<00:28:00.920> with<00:28:01.040> that 00:28:02.220 --> 00:28:02.230 align:start position:0% are we at with that 00:28:02.230 --> 00:28:04.990 align:start position:0% are we at with that it's<00:28:03.230> council 00:28:04.990 --> 00:28:05.000 align:start position:0% it's council 00:28:05.000 --> 00:28:08.170 align:start position:0% it's council no<00:28:05.990> actually<00:28:06.410> it's<00:28:06.620> more<00:28:06.860> the<00:28:07.730> question<00:28:07.880> is 00:28:08.170 --> 00:28:08.180 align:start position:0% no actually it's more the question is 00:28:08.180 --> 00:28:10.360 align:start position:0% no actually it's more the question is the<00:28:08.660> answer<00:28:08.870> is<00:28:08.960> more<00:28:09.140> complicated<00:28:09.950> than<00:28:10.340> that 00:28:10.360 --> 00:28:10.370 align:start position:0% the answer is more complicated than that 00:28:10.370 --> 00:28:13.030 align:start position:0% the answer is more complicated than that so<00:28:11.180> our<00:28:11.210> current<00:28:11.660> effort<00:28:12.140> is<00:28:12.350> to<00:28:12.620> prototype 00:28:13.030 --> 00:28:13.040 align:start position:0% so our current effort is to prototype 00:28:13.040 --> 00:28:15.910 align:start position:0% so our current effort is to prototype and<00:28:13.490> specify<00:28:14.480> so<00:28:14.900> that's<00:28:15.080> my<00:28:15.320> main<00:28:15.560> effort 00:28:15.910 --> 00:28:15.920 align:start position:0% and specify so that's my main effort 00:28:15.920 --> 00:28:19.180 align:start position:0% and specify so that's my main effort effort<00:28:16.400> in<00:28:16.640> my<00:28:17.210> little<00:28:17.630> team<00:28:17.900> team<00:28:18.440> so<00:28:19.130> to 00:28:19.180 --> 00:28:19.190 align:start position:0% effort in my little team team so to 00:28:19.190 --> 00:28:21.940 align:start position:0% effort in my little team team so to prototype<00:28:19.940> and<00:28:20.090> specify<00:28:20.630> the<00:28:20.960> the<00:28:21.680> first 00:28:21.940 --> 00:28:21.950 align:start position:0% prototype and specify the the first 00:28:21.950 --> 00:28:24.700 align:start position:0% prototype and specify the the first viable<00:28:22.420> version<00:28:23.420> of<00:28:23.570> the<00:28:23.780> state<00:28:24.020> status 00:28:24.700 --> 00:28:24.710 align:start position:0% viable version of the state status 00:28:24.710 --> 00:28:33.370 align:start position:0% viable version of the state status clients<00:28:25.600> what's<00:28:26.600> this<00:28:26.810> oh<00:28:27.850> yeah<00:28:28.880> and<00:28:31.330> so<00:28:32.380> so 00:28:33.370 --> 00:28:33.380 align:start position:0% clients what's this oh yeah and so so 00:28:33.380 --> 00:28:35.680 align:start position:0% clients what's this oh yeah and so so you<00:28:33.440> might<00:28:33.890> be<00:28:33.920> the<00:28:34.160> the<00:28:34.820> the<00:28:35.180> good<00:28:35.330> thing<00:28:35.540> to 00:28:35.680 --> 00:28:35.690 align:start position:0% you might be the the the good thing to 00:28:35.690 --> 00:28:37.660 align:start position:0% you might be the the the good thing to put<00:28:35.870> out<00:28:35.900> there<00:28:36.290> is<00:28:36.410> a<00:28:36.440> date<00:28:36.740> of<00:28:36.890> data<00:28:37.310> from<00:28:37.520> the 00:28:37.660 --> 00:28:37.670 align:start position:0% put out there is a date of data from the 00:28:37.670 --> 00:28:41.680 align:start position:0% put out there is a date of data from the status<00:28:38.000> client<00:28:38.390> prototype<00:28:39.940> if<00:28:40.940> that<00:28:41.390> would<00:28:41.660> be 00:28:41.680 --> 00:28:41.690 align:start position:0% status client prototype if that would be 00:28:41.690 --> 00:28:46.360 align:start position:0% status client prototype if that would be their<00:28:41.960> proposed<00:28:42.320> to<00:28:44.770> Leah<00:28:45.770> did<00:28:46.010> that<00:28:46.160> one 00:28:46.360 --> 00:28:46.370 align:start position:0% their proposed to Leah did that one 00:28:46.370 --> 00:28:48.490 align:start position:0% their proposed to Leah did that one that's<00:28:46.760> probably<00:28:46.970> the<00:28:47.360> like<00:28:47.630> the<00:28:47.840> closest<00:28:48.290> one 00:28:48.490 --> 00:28:48.500 align:start position:0% that's probably the like the closest one 00:28:48.500 --> 00:28:50.230 align:start position:0% that's probably the like the closest one you<00:28:48.620> could<00:28:48.830> if<00:28:49.190> you<00:28:49.340> scroll<00:28:49.610> down<00:28:49.670> to<00:28:49.850> the 00:28:50.230 --> 00:28:50.240 align:start position:0% you could if you scroll down to the 00:28:50.240 --> 00:28:51.970 align:start position:0% you could if you scroll down to the there 00:28:51.970 --> 00:28:51.980 align:start position:0% there 00:28:51.980 --> 00:28:54.540 align:start position:0% there it<00:28:52.340> describes<00:28:52.880> a<00:28:53.000> slightly<00:28:53.420> the<00:28:53.570> idea<00:28:53.960> of<00:28:54.230> it 00:28:54.540 --> 00:28:54.550 align:start position:0% it describes a slightly the idea of it 00:28:54.550 --> 00:28:57.670 align:start position:0% it describes a slightly the idea of it go<00:28:55.550> down<00:28:55.760> a<00:28:55.820> little<00:28:56.030> bit<00:28:56.300> it's<00:28:56.900> very<00:28:57.110> old<00:28:57.320> post 00:28:57.670 --> 00:28:57.680 align:start position:0% go down a little bit it's very old post 00:28:57.680 --> 00:28:59.560 align:start position:0% go down a little bit it's very old post but<00:28:57.890> it's<00:28:58.010> still<00:28:58.220> relevant<00:28:58.490> and<00:28:58.790> it<00:28:59.060> describes 00:28:59.560 --> 00:28:59.570 align:start position:0% but it's still relevant and it describes 00:28:59.570 --> 00:29:02.680 align:start position:0% but it's still relevant and it describes what<00:28:59.690> we<00:28:59.990> kind<00:29:00.260> of<00:29:00.380> want<00:29:00.590> to<00:29:00.650> do<00:29:00.860> and<00:29:01.100> the<00:29:02.000> yeah 00:29:02.680 --> 00:29:02.690 align:start position:0% what we kind of want to do and the yeah 00:29:02.690 --> 00:29:07.090 align:start position:0% what we kind of want to do and the yeah further<00:29:03.530> down<00:29:03.740> to<00:29:03.950> the<00:29:04.070> graph<00:29:04.310> to<00:29:05.030> the<00:29:06.100> next 00:29:07.090 --> 00:29:07.100 align:start position:0% further down to the graph to the next 00:29:07.100 --> 00:29:08.530 align:start position:0% further down to the graph to the next one 00:29:08.530 --> 00:29:08.540 align:start position:0% one 00:29:08.540 --> 00:29:11.800 align:start position:0% one breakdown<00:29:09.350> yeah<00:29:09.590> a<00:29:09.620> further<00:29:09.950> one<00:29:10.600> further<00:29:11.600> it 00:29:11.800 --> 00:29:11.810 align:start position:0% breakdown yeah a further one further it 00:29:11.810 --> 00:29:17.080 align:start position:0% breakdown yeah a further one further it further<00:29:12.430> okay<00:29:13.430> that<00:29:13.610> one<00:29:14.920> so<00:29:15.920> yeah<00:29:16.730> so<00:29:16.940> the 00:29:17.080 --> 00:29:17.090 align:start position:0% further okay that one so yeah so the 00:29:17.090 --> 00:29:22.150 align:start position:0% further okay that one so yeah so the this<00:29:17.690> is<00:29:17.750> the<00:29:19.450> I've<00:29:20.450> done<00:29:20.660> some<00:29:20.870> more<00:29:21.160> analysis 00:29:22.150 --> 00:29:22.160 align:start position:0% this is the I've done some more analysis 00:29:22.160 --> 00:29:24.250 align:start position:0% this is the I've done some more analysis on<00:29:22.250> this<00:29:22.340> but<00:29:22.820> basically<00:29:22.940> there<00:29:23.480> are<00:29:23.720> what 00:29:24.250 --> 00:29:24.260 align:start position:0% on this but basically there are what 00:29:24.260 --> 00:29:26.560 align:start position:0% on this but basically there are what we're<00:29:24.440> trying<00:29:24.620> to<00:29:24.770> do<00:29:24.920> is<00:29:25.070> that<00:29:25.280> we<00:29:26.240> kind<00:29:26.390> of 00:29:26.560 --> 00:29:26.570 align:start position:0% we're trying to do is that we kind of 00:29:26.570 --> 00:29:29.380 align:start position:0% we're trying to do is that we kind of try<00:29:26.720> to<00:29:26.780> circumvent<00:29:27.050> rent<00:29:27.770> a<00:29:28.040> bit<00:29:28.460> because<00:29:29.060> as 00:29:29.380 --> 00:29:29.390 align:start position:0% try to circumvent rent a bit because as 00:29:29.390 --> 00:29:31.690 align:start position:0% try to circumvent rent a bit because as I<00:29:29.540> said<00:29:29.600> in<00:29:29.960> April<00:29:30.080> in<00:29:30.560> our<00:29:30.770> meeting<00:29:31.280> in<00:29:31.370> Berlin 00:29:31.690 --> 00:29:31.700 align:start position:0% I said in April in our meeting in Berlin 00:29:31.700 --> 00:29:34.810 align:start position:0% I said in April in our meeting in Berlin after<00:29:32.230> research<00:29:33.230> in<00:29:33.590> researching<00:29:34.340> rent<00:29:34.550> for<00:29:34.760> a 00:29:34.810 --> 00:29:34.820 align:start position:0% after research in researching rent for a 00:29:34.820 --> 00:29:37.270 align:start position:0% after research in researching rent for a bit<00:29:35.090> for<00:29:35.630> a<00:29:35.690> few<00:29:36.170> months<00:29:36.470> I've<00:29:36.650> realized<00:29:37.130> that 00:29:37.270 --> 00:29:37.280 align:start position:0% bit for a few months I've realized that 00:29:37.280 --> 00:29:39.850 align:start position:0% bit for a few months I've realized that it<00:29:37.550> is<00:29:37.700> possible<00:29:38.180> to<00:29:38.210> do<00:29:38.420> it<00:29:38.570> technically<00:29:38.990> but 00:29:39.850 --> 00:29:39.860 align:start position:0% it is possible to do it technically but 00:29:39.860 --> 00:29:41.950 align:start position:0% it is possible to do it technically but it<00:29:39.920> would<00:29:40.310> be<00:29:40.430> very<00:29:40.550> expensive<00:29:41.180> project<00:29:41.420> to 00:29:41.950 --> 00:29:41.960 align:start position:0% it would be very expensive project to 00:29:41.960 --> 00:29:46.870 align:start position:0% it would be very expensive project to roll<00:29:42.230> out<00:29:44.740> practically<00:29:45.740> and<00:29:45.950> the<00:29:46.430> reason<00:29:46.730> why 00:29:46.870 --> 00:29:46.880 align:start position:0% roll out practically and the reason why 00:29:46.880 --> 00:29:48.490 align:start position:0% roll out practically and the reason why it<00:29:46.940> would<00:29:47.150> be<00:29:47.270> very<00:29:47.390> expensive<00:29:47.690> to<00:29:48.050> roll<00:29:48.350> out 00:29:48.490 --> 00:29:48.500 align:start position:0% it would be very expensive to roll out 00:29:48.500 --> 00:29:51.460 align:start position:0% it would be very expensive to roll out right<00:29:48.710> now<00:29:48.890> is<00:29:49.160> the<00:29:49.570> is<00:29:50.570> the<00:29:50.900> cost<00:29:51.320> of 00:29:51.460 --> 00:29:51.470 align:start position:0% right now is the is the cost of 00:29:51.470 --> 00:29:53.150 align:start position:0% right now is the is the cost of ecosystem<00:29:52.070> research<00:29:52.370> which 00:29:53.150 --> 00:29:53.160 align:start position:0% ecosystem research which 00:29:53.160 --> 00:29:56.270 align:start position:0% ecosystem research which had<00:29:53.640> to<00:29:53.790> be<00:29:53.940> done<00:29:54.180> because<00:29:55.050> the<00:29:55.440> the<00:29:56.070> state 00:29:56.270 --> 00:29:56.280 align:start position:0% had to be done because the the state 00:29:56.280 --> 00:29:59.480 align:start position:0% had to be done because the the state rent<00:29:56.760> wherever<00:29:57.180> however<00:29:57.870> you<00:29:58.320> implemented<00:29:59.040> it 00:29:59.480 --> 00:29:59.490 align:start position:0% rent wherever however you implemented it 00:29:59.490 --> 00:30:01.910 align:start position:0% rent wherever however you implemented it will<00:29:59.880> change<00:30:00.210> the<00:30:00.420> programming<00:30:00.900> paradigm<00:30:01.380> in 00:30:01.910 --> 00:30:01.920 align:start position:0% will change the programming paradigm in 00:30:01.920 --> 00:30:03.950 align:start position:0% will change the programming paradigm in the<00:30:02.160> way<00:30:02.310> that<00:30:02.610> at<00:30:03.060> least<00:30:03.240> in<00:30:03.360> a<00:30:03.510> way<00:30:03.540> I<00:30:03.630> thought 00:30:03.950 --> 00:30:03.960 align:start position:0% the way that at least in a way I thought 00:30:03.960 --> 00:30:06.050 align:start position:0% the way that at least in a way I thought about<00:30:04.020> it<00:30:04.410> because<00:30:04.680> other<00:30:05.130> proposals<00:30:05.820> where 00:30:06.050 --> 00:30:06.060 align:start position:0% about it because other proposals where 00:30:06.060 --> 00:30:08.870 align:start position:0% about it because other proposals where you<00:30:06.270> have<00:30:06.540> a<00:30:06.570> kind<00:30:07.170> of<00:30:07.260> attenuated<00:30:08.010> cost<00:30:08.700> of 00:30:08.870 --> 00:30:08.880 align:start position:0% you have a kind of attenuated cost of 00:30:08.880 --> 00:30:10.580 align:start position:0% you have a kind of attenuated cost of the<00:30:08.970> storage<00:30:09.360> which<00:30:09.780> I<00:30:09.900> don't<00:30:10.080> call<00:30:10.320> story 00:30:10.580 --> 00:30:10.590 align:start position:0% the storage which I don't call story 00:30:10.590 --> 00:30:12.500 align:start position:0% the storage which I don't call story Brent<00:30:10.860> it's<00:30:11.100> a<00:30:11.220> state<00:30:11.850> rent<00:30:12.060> because<00:30:12.270> it 00:30:12.500 --> 00:30:12.510 align:start position:0% Brent it's a state rent because it 00:30:12.510 --> 00:30:14.930 align:start position:0% Brent it's a state rent because it doesn't<00:30:12.870> actually<00:30:13.020> remove<00:30:13.650> things<00:30:14.520> from<00:30:14.700> the 00:30:14.930 --> 00:30:14.940 align:start position:0% doesn't actually remove things from the 00:30:14.940 --> 00:30:19.370 align:start position:0% doesn't actually remove things from the storage<00:30:15.210> so<00:30:16.400> so<00:30:17.400> any<00:30:17.640> any<00:30:18.000> proposals<00:30:18.900> in<00:30:19.140> any 00:30:19.370 --> 00:30:19.380 align:start position:0% storage so so any any proposals in any 00:30:19.380 --> 00:30:21.380 align:start position:0% storage so so any any proposals in any shape<00:30:19.890> or<00:30:20.010> form<00:30:20.070> which<00:30:20.550> will<00:30:20.760> start<00:30:21.030> removing 00:30:21.380 --> 00:30:21.390 align:start position:0% shape or form which will start removing 00:30:21.390 --> 00:30:24.590 align:start position:0% shape or form which will start removing things<00:30:21.690> from<00:30:22.050> the<00:30:22.260> state<00:30:22.500> at<00:30:23.250> a<00:30:23.310> certain<00:30:23.850> after 00:30:24.590 --> 00:30:24.600 align:start position:0% things from the state at a certain after 00:30:24.600 --> 00:30:26.720 align:start position:0% things from the state at a certain after the<00:30:24.750> state<00:30:25.020> rent<00:30:25.350> is<00:30:25.500> not<00:30:25.530> paid<00:30:25.730> will 00:30:26.720 --> 00:30:26.730 align:start position:0% the state rent is not paid will 00:30:26.730 --> 00:30:29.480 align:start position:0% the state rent is not paid will inevitably<00:30:27.570> change<00:30:28.230> the<00:30:28.950> program<00:30:29.370> in 00:30:29.480 --> 00:30:29.490 align:start position:0% inevitably change the program in 00:30:29.490 --> 00:30:31.520 align:start position:0% inevitably change the program in paradigm<00:30:29.970> and<00:30:30.510> some<00:30:30.870> of<00:30:31.020> the<00:30:31.110> things<00:30:31.320> will 00:30:31.520 --> 00:30:31.530 align:start position:0% paradigm and some of the things will 00:30:31.530 --> 00:30:34.310 align:start position:0% paradigm and some of the things will become<00:30:31.890> quite<00:30:32.520> a<00:30:32.610> connect<00:30:33.060> unexpected<00:30:33.780> for 00:30:34.310 --> 00:30:34.320 align:start position:0% become quite a connect unexpected for 00:30:34.320 --> 00:30:37.490 align:start position:0% become quite a connect unexpected for example<00:30:34.800> give<00:30:35.250> you<00:30:35.310> example<00:30:35.790> now<00:30:35.940> I<00:30:36.440> have<00:30:37.440> a 00:30:37.490 --> 00:30:37.500 align:start position:0% example give you example now I have a 00:30:37.500 --> 00:30:41.030 align:start position:0% example give you example now I have a smart<00:30:37.800> contract<00:30:38.010> and<00:30:38.970> solidity<00:30:39.420> and<00:30:39.750> it<00:30:40.650> has<00:30:40.800> a 00:30:41.030 --> 00:30:41.040 align:start position:0% smart contract and solidity and it has a 00:30:41.040 --> 00:30:44.870 align:start position:0% smart contract and solidity and it has a variable<00:30:42.000> fill<00:30:42.960> variable<00:30:43.470> net<00:30:43.620> and<00:30:43.880> you 00:30:44.870 --> 00:30:44.880 align:start position:0% variable fill variable net and you 00:30:44.880 --> 00:30:46.880 align:start position:0% variable fill variable net and you initialize<00:30:45.600> it<00:30:45.780> in<00:30:45.900> constructor<00:30:46.560> and<00:30:46.740> that 00:30:46.880 --> 00:30:46.890 align:start position:0% initialize it in constructor and that 00:30:46.890 --> 00:30:48.470 align:start position:0% initialize it in constructor and that variable<00:30:47.310> essentially<00:30:47.880> like<00:30:48.030> let's<00:30:48.360> say 00:30:48.470 --> 00:30:48.480 align:start position:0% variable essentially like let's say 00:30:48.480 --> 00:30:50.750 align:start position:0% variable essentially like let's say pointer<00:30:48.990> to<00:30:49.170> another<00:30:49.200> contract<00:30:49.890> you 00:30:50.750 --> 00:30:50.760 align:start position:0% pointer to another contract you 00:30:50.760 --> 00:30:52.520 align:start position:0% pointer to another contract you initialize<00:30:51.180> it<00:30:51.300> in<00:30:51.390> contract<00:30:51.900> and<00:30:52.050> it's<00:30:52.290> an<00:30:52.410> on 00:30:52.520 --> 00:30:52.530 align:start position:0% initialize it in contract and it's an on 00:30:52.530 --> 00:30:54.830 align:start position:0% initialize it in contract and it's an on now<00:30:52.740> it's<00:30:53.400> reference<00:30:54.030> to<00:30:54.210> another<00:30:54.330> contract 00:30:54.830 --> 00:30:54.840 align:start position:0% now it's reference to another contract 00:30:54.840 --> 00:30:56.570 align:start position:0% now it's reference to another contract and<00:30:55.020> you<00:30:55.110> can<00:30:55.320> happily<00:30:55.680> use<00:30:55.980> it<00:30:56.130> within<00:30:56.340> the 00:30:56.570 --> 00:30:56.580 align:start position:0% and you can happily use it within the 00:30:56.580 --> 00:30:58.880 align:start position:0% and you can happily use it within the contract<00:30:56.880> anytime<00:30:57.420> and<00:30:57.690> you<00:30:58.230> assume<00:30:58.590> that<00:30:58.620> it 00:30:58.880 --> 00:30:58.890 align:start position:0% contract anytime and you assume that it 00:30:58.890 --> 00:31:01.960 align:start position:0% contract anytime and you assume that it will<00:30:59.070> never<00:30:59.280> go<00:30:59.640> -<00:30:59.810> it<00:31:00.810> will<00:31:01.140> never<00:31:01.290> disappear 00:31:01.960 --> 00:31:01.970 align:start position:0% will never go - it will never disappear 00:31:01.970 --> 00:31:04.340 align:start position:0% will never go - it will never disappear so<00:31:02.970> you<00:31:03.030> don't<00:31:03.240> have<00:31:03.360> to<00:31:03.510> check<00:31:03.780> in<00:31:04.020> every 00:31:04.340 --> 00:31:04.350 align:start position:0% so you don't have to check in every 00:31:04.350 --> 00:31:05.900 align:start position:0% so you don't have to check in every function<00:31:04.920> of<00:31:05.010> the<00:31:05.100> contract<00:31:05.520> that<00:31:05.580> that 00:31:05.900 --> 00:31:05.910 align:start position:0% function of the contract that that 00:31:05.910 --> 00:31:08.360 align:start position:0% function of the contract that that pointer<00:31:06.360> is<00:31:06.390> still<00:31:06.720> valid<00:31:06.990> that<00:31:07.440> the<00:31:07.680> contract 00:31:08.360 --> 00:31:08.370 align:start position:0% pointer is still valid that the contract 00:31:08.370 --> 00:31:09.770 align:start position:0% pointer is still valid that the contract that<00:31:08.400> you<00:31:08.610> point<00:31:08.880> you<00:31:09.030> know<00:31:09.120> is<00:31:09.300> still<00:31:09.510> there 00:31:09.770 --> 00:31:09.780 align:start position:0% that you point you know is still there 00:31:09.780 --> 00:31:11.690 align:start position:0% that you point you know is still there because<00:31:10.290> you're<00:31:10.620> assumed<00:31:10.920> that<00:31:11.070> okay<00:31:11.400> I've 00:31:11.690 --> 00:31:11.700 align:start position:0% because you're assumed that okay I've 00:31:11.700 --> 00:31:14.030 align:start position:0% because you're assumed that okay I've initialized<00:31:11.970> in<00:31:12.330> constructor<00:31:13.140> it<00:31:13.680> will<00:31:13.890> not 00:31:14.030 --> 00:31:14.040 align:start position:0% initialized in constructor it will not 00:31:14.040 --> 00:31:17.260 align:start position:0% initialized in constructor it will not go<00:31:14.250> away<00:31:14.340> it's<00:31:14.820> like<00:31:14.940> in<00:31:15.320> kind<00:31:16.320> of<00:31:16.380> Const 00:31:17.260 --> 00:31:17.270 align:start position:0% go away it's like in kind of Const 00:31:17.270 --> 00:31:20.540 align:start position:0% go away it's like in kind of Const constant<00:31:18.270> variable<00:31:18.690> in<00:31:18.780> C++<00:31:19.440> right<00:31:19.800> it<00:31:20.340> will 00:31:20.540 --> 00:31:20.550 align:start position:0% constant variable in C++ right it will 00:31:20.550 --> 00:31:22.340 align:start position:0% constant variable in C++ right it will be<00:31:20.610> there<00:31:20.940> it's<00:31:21.210> once<00:31:21.480> you've<00:31:21.690> initialized<00:31:21.960> it 00:31:22.340 --> 00:31:22.350 align:start position:0% be there it's once you've initialized it 00:31:22.350 --> 00:31:25.160 align:start position:0% be there it's once you've initialized it it<00:31:22.470> never<00:31:22.680> changes<00:31:23.190> but<00:31:24.000> then<00:31:24.210> with<00:31:24.930> the<00:31:24.990> state 00:31:25.160 --> 00:31:25.170 align:start position:0% it never changes but then with the state 00:31:25.170 --> 00:31:26.930 align:start position:0% it never changes but then with the state rent<00:31:25.440> you<00:31:25.620> might<00:31:25.800> see<00:31:26.130> that<00:31:26.280> this<00:31:26.490> thing<00:31:26.550> can 00:31:26.930 --> 00:31:26.940 align:start position:0% rent you might see that this thing can 00:31:26.940 --> 00:31:30.320 align:start position:0% rent you might see that this thing can just<00:31:26.970> go<00:31:27.600> under<00:31:28.020> you<00:31:28.590> know<00:31:28.710> it<00:31:29.340> will<00:31:29.580> go<00:31:30.000> under 00:31:30.320 --> 00:31:30.330 align:start position:0% just go under you know it will go under 00:31:30.330 --> 00:31:32.930 align:start position:0% just go under you know it will go under the<00:31:30.420> pointer<00:31:30.960> so<00:31:31.200> the<00:31:31.440> this<00:31:31.760> contract<00:31:32.760> will 00:31:32.930 --> 00:31:32.940 align:start position:0% the pointer so the this contract will 00:31:32.940 --> 00:31:34.210 align:start position:0% the pointer so the this contract will disappear<00:31:33.390> and<00:31:33.510> then<00:31:33.630> your<00:31:33.750> pointer<00:31:34.170> will 00:31:34.210 --> 00:31:34.220 align:start position:0% disappear and then your pointer will 00:31:34.220 --> 00:31:36.200 align:start position:0% disappear and then your pointer will will<00:31:35.220> point<00:31:35.430> to<00:31:35.580> something<00:31:35.760> that<00:31:35.910> doesn't 00:31:36.200 --> 00:31:36.210 align:start position:0% will point to something that doesn't 00:31:36.210 --> 00:31:38.960 align:start position:0% will point to something that doesn't exist<00:31:36.540> anymore<00:31:36.780> so<00:31:37.080> that<00:31:37.620> sort<00:31:38.070> of<00:31:38.130> lots<00:31:38.880> of 00:31:38.960 --> 00:31:38.970 align:start position:0% exist anymore so that sort of lots of 00:31:38.970 --> 00:31:40.700 align:start position:0% exist anymore so that sort of lots of these<00:31:39.090> things<00:31:39.360> have<00:31:39.570> to<00:31:39.600> be<00:31:39.750> changed<00:31:40.350> in<00:31:40.560> terms 00:31:40.700 --> 00:31:40.710 align:start position:0% these things have to be changed in terms 00:31:40.710 --> 00:31:45.140 align:start position:0% these things have to be changed in terms of<00:31:40.950> the<00:31:41.070> paradigm<00:31:42.920> so<00:31:43.920> and<00:31:44.310> obviously<00:31:44.910> there 00:31:45.140 --> 00:31:45.150 align:start position:0% of the paradigm so and obviously there 00:31:45.150 --> 00:31:46.430 align:start position:0% of the paradigm so and obviously there would<00:31:45.300> be<00:31:45.330> some<00:31:45.570> contracts<00:31:46.020> that<00:31:46.110> would<00:31:46.290> be 00:31:46.430 --> 00:31:46.440 align:start position:0% would be some contracts that would be 00:31:46.440 --> 00:31:49.190 align:start position:0% would be some contracts that would be suspected<00:31:47.310> susceptible<00:31:47.940> to<00:31:47.970> some<00:31:48.870> Griffin 00:31:49.190 --> 00:31:49.200 align:start position:0% suspected susceptible to some Griffin 00:31:49.200 --> 00:31:51.200 align:start position:0% suspected susceptible to some Griffin attacks<00:31:49.500> that<00:31:50.160> need<00:31:50.430> to<00:31:50.580> be<00:31:50.700> needed<00:31:51.090> to<00:31:51.120> be 00:31:51.200 --> 00:31:51.210 align:start position:0% attacks that need to be needed to be 00:31:51.210 --> 00:31:53.990 align:start position:0% attacks that need to be needed to be researched<00:31:51.690> as<00:31:51.960> well<00:31:52.140> and<00:31:52.380> obviously<00:31:53.000> the 00:31:53.990 --> 00:31:54.000 align:start position:0% researched as well and obviously the 00:31:54.000 --> 00:31:56.210 align:start position:0% researched as well and obviously the number<00:31:54.780> amount<00:31:55.050> of<00:31:55.230> resources<00:31:55.680> that<00:31:55.830> I 00:31:56.210 --> 00:31:56.220 align:start position:0% number amount of resources that I 00:31:56.220 --> 00:31:58.130 align:start position:0% number amount of resources that I thought<00:31:56.580> would<00:31:56.760> be<00:31:56.910> required<00:31:57.270> for<00:31:57.330> that<00:31:57.630> so<00:31:57.930> if 00:31:58.130 --> 00:31:58.140 align:start position:0% thought would be required for that so if 00:31:58.140 --> 00:31:59.780 align:start position:0% thought would be required for that so if we<00:31:58.290> really<00:31:58.500> wanted<00:31:58.830> to<00:31:58.950> roll<00:31:59.100> it<00:31:59.250> out<00:31:59.370> would<00:31:59.640> be 00:31:59.780 --> 00:31:59.790 align:start position:0% we really wanted to roll it out would be 00:31:59.790 --> 00:32:02.390 align:start position:0% we really wanted to roll it out would be you<00:32:00.360> know<00:32:00.480> something<00:32:00.840> that<00:32:00.870> I<00:32:01.140> cannot<00:32:01.710> afford 00:32:02.390 --> 00:32:02.400 align:start position:0% you know something that I cannot afford 00:32:02.400 --> 00:32:04.970 align:start position:0% you know something that I cannot afford or<00:32:03.000> maybe<00:32:03.810> I'm<00:32:03.990> not<00:32:04.170> sure<00:32:04.230> if<00:32:04.620> if<00:32:04.740> they<00:32:04.860> are 00:32:04.970 --> 00:32:04.980 align:start position:0% or maybe I'm not sure if if they are 00:32:04.980 --> 00:32:05.730 align:start position:0% or maybe I'm not sure if if they are foundation 00:32:05.730 --> 00:32:05.740 align:start position:0% foundation 00:32:05.740 --> 00:32:07.380 align:start position:0% foundation would<00:32:06.460> be<00:32:06.610> able<00:32:06.670> to<00:32:06.910> afford<00:32:07.120> that<00:32:07.240> or 00:32:07.380 --> 00:32:07.390 align:start position:0% would be able to afford that or 00:32:07.390 --> 00:32:10.710 align:start position:0% would be able to afford that or something<00:32:07.960> like<00:32:08.170> that<00:32:08.320> so<00:32:08.830> that's<00:32:09.160> why<00:32:09.720> we 00:32:10.710 --> 00:32:10.720 align:start position:0% something like that so that's why we 00:32:10.720 --> 00:32:13.260 align:start position:0% something like that so that's why we started<00:32:11.050> to<00:32:11.170> do<00:32:11.320> more<00:32:12.100> emphasis<00:32:12.670> on<00:32:12.790> status 00:32:13.260 --> 00:32:13.270 align:start position:0% started to do more emphasis on status 00:32:13.270 --> 00:32:15.840 align:start position:0% started to do more emphasis on status clients<00:32:13.660> which<00:32:13.900> might<00:32:14.200> actually<00:32:14.850> if 00:32:15.840 --> 00:32:15.850 align:start position:0% clients which might actually if 00:32:15.850 --> 00:32:21.030 align:start position:0% clients which might actually if implemented<00:32:16.890> correctly<00:32:17.890> and<00:32:18.520> if<00:32:18.760> if<00:32:19.300> my<00:32:20.040> sort 00:32:21.030 --> 00:32:21.040 align:start position:0% implemented correctly and if if my sort 00:32:21.040 --> 00:32:23.700 align:start position:0% implemented correctly and if if my sort of<00:32:21.100> intuition<00:32:22.090> is<00:32:22.300> correct<00:32:22.470> it<00:32:23.470> might 00:32:23.700 --> 00:32:23.710 align:start position:0% of intuition is correct it might 00:32:23.710 --> 00:32:28.190 align:start position:0% of intuition is correct it might actually<00:32:23.890> give<00:32:24.280> us<00:32:24.400> enough<00:32:24.820> runway<00:32:25.890> before<00:32:26.910> we 00:32:28.190 --> 00:32:28.200 align:start position:0% actually give us enough runway before we 00:32:28.200 --> 00:32:30.870 align:start position:0% actually give us enough runway before we and<00:32:29.200> then<00:32:29.380> I've<00:32:29.590> got<00:32:29.800> another<00:32:30.040> proposal<00:32:30.490> but 00:32:30.870 --> 00:32:30.880 align:start position:0% and then I've got another proposal but 00:32:30.880 --> 00:32:32.790 align:start position:0% and then I've got another proposal but which<00:32:31.060> I<00:32:31.210> haven't<00:32:31.600> published<00:32:31.780> yet<00:32:32.140> that 00:32:32.790 --> 00:32:32.800 align:start position:0% which I haven't published yet that 00:32:32.800 --> 00:32:34.950 align:start position:0% which I haven't published yet that actually<00:32:33.520> introduces<00:32:34.000> state<00:32:34.210> rent<00:32:34.450> after<00:32:34.870> the 00:32:34.950 --> 00:32:34.960 align:start position:0% actually introduces state rent after the 00:32:34.960 --> 00:32:37.200 align:start position:0% actually introduces state rent after the stateless<00:32:35.320> clients<00:32:35.790> but<00:32:36.790> in<00:32:36.940> a<00:32:37.090> slightly 00:32:37.200 --> 00:32:37.210 align:start position:0% stateless clients but in a slightly 00:32:37.210 --> 00:32:39.780 align:start position:0% stateless clients but in a slightly different<00:32:38.050> in<00:32:38.470> more<00:32:38.770> surprising<00:32:39.310> way<00:32:39.460> but<00:32:39.760> I 00:32:39.780 --> 00:32:39.790 align:start position:0% different in more surprising way but I 00:32:39.790 --> 00:32:46.920 align:start position:0% different in more surprising way but I don't<00:32:39.910> think<00:32:40.180> I<00:32:40.360> have<00:32:40.510> time<00:32:40.720> to<00:32:40.780> explain<00:32:41.530> it<00:32:45.930> so 00:32:46.920 --> 00:32:46.930 align:start position:0% don't think I have time to explain it so 00:32:46.930 --> 00:32:49.080 align:start position:0% don't think I have time to explain it so there<00:32:47.320> basically<00:32:47.440> it's<00:32:47.860> postponed<00:32:48.430> at<00:32:48.940> the 00:32:49.080 --> 00:32:49.090 align:start position:0% there basically it's postponed at the 00:32:49.090 --> 00:32:51.330 align:start position:0% there basically it's postponed at the moment<00:32:49.390> until<00:32:49.840> we<00:32:50.230> do<00:32:50.380> the<00:32:50.590> stateless<00:32:50.920> clients 00:32:51.330 --> 00:32:51.340 align:start position:0% moment until we do the stateless clients 00:32:51.340 --> 00:32:54.750 align:start position:0% moment until we do the stateless clients okay<00:32:51.910> so<00:32:52.980> stateless<00:32:53.980> clients<00:32:54.340> are<00:32:54.490> the<00:32:54.610> way<00:32:54.700> to 00:32:54.750 --> 00:32:54.760 align:start position:0% okay so stateless clients are the way to 00:32:54.760 --> 00:32:56.970 align:start position:0% okay so stateless clients are the way to go<00:32:54.970> until<00:32:55.240> a<00:32:55.780> few<00:32:56.260> point<00:32:56.500> oh<00:32:56.620> that's<00:32:56.830> what's 00:32:56.970 --> 00:32:56.980 align:start position:0% go until a few point oh that's what's 00:32:56.980 --> 00:32:59.490 align:start position:0% go until a few point oh that's what's gonna<00:32:57.100> hold<00:32:57.280> so<00:32:57.520> hopefully<00:32:58.360> because<00:32:59.170> I<00:32:59.200> don't 00:32:59.490 --> 00:32:59.500 align:start position:0% gonna hold so hopefully because I don't 00:32:59.500 --> 00:33:02.010 align:start position:0% gonna hold so hopefully because I don't know<00:32:59.650> because<00:33:00.010> the<00:33:00.540> obviously<00:33:01.540> the<00:33:01.660> future<00:33:01.960> is 00:33:02.010 --> 00:33:02.020 align:start position:0% know because the obviously the future is 00:33:02.020 --> 00:33:05.730 align:start position:0% know because the obviously the future is hard<00:33:02.260> to<00:33:02.350> predict<00:33:02.740> this<00:33:02.920> is<00:33:02.980> our<00:33:03.340> current<00:33:04.740> this 00:33:05.730 --> 00:33:05.740 align:start position:0% hard to predict this is our current this 00:33:05.740 --> 00:33:07.320 align:start position:0% hard to predict this is our current this Alec<00:33:05.950> wants<00:33:06.070> to<00:33:06.280> say<00:33:06.430> something<00:33:06.730> yeah<00:33:07.030> so<00:33:07.300> I 00:33:07.320 --> 00:33:07.330 align:start position:0% Alec wants to say something yeah so I 00:33:07.330 --> 00:33:09.510 align:start position:0% Alec wants to say something yeah so I know<00:33:07.600> like<00:33:08.170> another<00:33:08.530> reason<00:33:08.950> why<00:33:09.130> it's<00:33:09.340> good 00:33:09.510 --> 00:33:09.520 align:start position:0% know like another reason why it's good 00:33:09.520 --> 00:33:12.090 align:start position:0% know like another reason why it's good to<00:33:09.670> go<00:33:09.790> this<00:33:09.970> way<00:33:10.150> is<00:33:10.300> because<00:33:10.510> the<00:33:10.930> like<00:33:11.740> the 00:33:12.090 --> 00:33:12.100 align:start position:0% to go this way is because the like the 00:33:12.100 --> 00:33:14.070 align:start position:0% to go this way is because the like the ease<00:33:12.280> by<00:33:12.550> far<00:33:12.850> the<00:33:13.000> easiest<00:33:13.150> way<00:33:13.720> it's<00:33:13.900> our 00:33:14.070 --> 00:33:14.080 align:start position:0% ease by far the easiest way it's our 00:33:14.080 --> 00:33:17.190 align:start position:0% ease by far the easiest way it's our kind<00:33:14.230> of<00:33:14.910> merge<00:33:15.910> ease<00:33:16.180> one<00:33:16.420> into<00:33:16.780> it<00:33:16.900> the<00:33:16.990> REM 00:33:17.190 --> 00:33:17.200 align:start position:0% kind of merge ease one into it the REM 00:33:17.200 --> 00:33:19.950 align:start position:0% kind of merge ease one into it the REM 2.0<00:33:17.710> is<00:33:18.010> to<00:33:18.310> basically<00:33:18.540> turn<00:33:19.540> it<00:33:19.720> into<00:33:19.870> a 00:33:19.950 --> 00:33:19.960 align:start position:0% 2.0 is to basically turn it into a 00:33:19.960 --> 00:33:21.600 align:start position:0% 2.0 is to basically turn it into a stingless<00:33:20.380> client<00:33:20.740> by<00:33:20.830> default<00:33:21.250> because 00:33:21.600 --> 00:33:21.610 align:start position:0% stingless client by default because 00:33:21.610 --> 00:33:24.390 align:start position:0% stingless client by default because that's<00:33:21.820> just<00:33:22.030> the<00:33:22.630> way<00:33:22.780> that<00:33:22.960> state<00:33:23.320> is<00:33:23.620> inside 00:33:24.390 --> 00:33:24.400 align:start position:0% that's just the way that state is inside 00:33:24.400 --> 00:33:26.370 align:start position:0% that's just the way that state is inside of<00:33:24.550> each<00:33:24.640> key<00:33:24.820> works<00:33:25.060> so<00:33:25.690> what<00:33:25.780> actually<00:33:25.960> kind 00:33:26.370 --> 00:33:26.380 align:start position:0% of each key works so what actually kind 00:33:26.380 --> 00:33:28.290 align:start position:0% of each key works so what actually kind of<00:33:26.440> makes<00:33:26.650> the<00:33:26.890> the<00:33:27.430> roadmap<00:33:27.790> stoic<00:33:28.090> fit 00:33:28.290 --> 00:33:28.300 align:start position:0% of makes the the roadmap stoic fit 00:33:28.300 --> 00:33:31.800 align:start position:0% of makes the the roadmap stoic fit together<00:33:28.600> very<00:33:28.690> smoothly<00:33:30.450> so<00:33:31.450> the<00:33:31.600> downside 00:33:31.800 --> 00:33:31.810 align:start position:0% together very smoothly so the downside 00:33:31.810 --> 00:33:34.290 align:start position:0% together very smoothly so the downside of<00:33:32.110> the<00:33:32.350> state<00:33:32.560> is<00:33:32.680> Cline<00:33:33.060> related<00:33:34.060> to<00:33:34.210> the 00:33:34.290 --> 00:33:34.300 align:start position:0% of the state is Cline related to the 00:33:34.300 --> 00:33:36.270 align:start position:0% of the state is Cline related to the state<00:33:34.510> rent<00:33:34.720> is<00:33:34.930> that<00:33:35.110> there<00:33:35.620> will<00:33:35.800> have<00:33:36.010> to<00:33:36.070> be 00:33:36.270 --> 00:33:36.280 align:start position:0% state rent is that there will have to be 00:33:36.280 --> 00:33:38.640 align:start position:0% state rent is that there will have to be no<00:33:36.760> the<00:33:36.970> network<00:33:37.360> that<00:33:37.570> still<00:33:38.230> hold<00:33:38.530> the 00:33:38.640 --> 00:33:38.650 align:start position:0% no the network that still hold the 00:33:38.650 --> 00:33:42.420 align:start position:0% no the network that still hold the entire<00:33:38.890> state<00:33:39.220> but<00:33:40.090> the<00:33:41.020> this<00:33:41.980> requirement 00:33:42.420 --> 00:33:42.430 align:start position:0% entire state but the this requirement 00:33:42.430 --> 00:33:47.190 align:start position:0% entire state but the this requirement will<00:33:42.850> not<00:33:43.090> will<00:33:43.840> not<00:33:43.870> be<00:33:44.460> for<00:33:45.460> every<00:33:46.200> basically 00:33:47.190 --> 00:33:47.200 align:start position:0% will not will not be for every basically 00:33:47.200 --> 00:33:49.500 align:start position:0% will not will not be for every basically phone<00:33:47.350> out<00:33:47.530> so<00:33:47.560> they<00:33:48.400> will<00:33:48.640> be<00:33:48.790> still<00:33:49.060> somebody 00:33:49.500 --> 00:33:49.510 align:start position:0% phone out so they will be still somebody 00:33:49.510 --> 00:33:52.170 align:start position:0% phone out so they will be still somebody has<00:33:49.720> to<00:33:49.900> have<00:33:50.050> all<00:33:50.320> the<00:33:50.440> entire<00:33:50.680> state<00:33:50.980> but<00:33:51.940> we 00:33:52.170 --> 00:33:52.180 align:start position:0% has to have all the entire state but we 00:33:52.180 --> 00:33:55.440 align:start position:0% has to have all the entire state but we hope<00:33:52.390> that<00:33:52.690> this<00:33:52.960> is<00:33:53.640> you<00:33:54.640> know<00:33:54.760> as<00:33:55.030> long<00:33:55.390> as 00:33:55.440 --> 00:33:55.450 align:start position:0% hope that this is you know as long as 00:33:55.450 --> 00:33:57.480 align:start position:0% hope that this is you know as long as not<00:33:55.750> everybody<00:33:56.200> needs<00:33:56.350> to<00:33:56.560> do<00:33:56.680> that<00:33:56.920> it<00:33:57.250> will 00:33:57.480 --> 00:33:57.490 align:start position:0% not everybody needs to do that it will 00:33:57.490 --> 00:33:58.370 align:start position:0% not everybody needs to do that it will be<00:33:57.640> better 00:33:58.370 --> 00:33:58.380 align:start position:0% be better 00:33:58.380 --> 00:34:01.560 align:start position:0% be better so<00:33:59.380> one<00:33:59.830> kind<00:34:00.220> of<00:34:00.340> hard<00:34:01.210> thing<00:34:01.540> about 00:34:01.560 --> 00:34:01.570 align:start position:0% so one kind of hard thing about 00:34:01.570 --> 00:34:03.450 align:start position:0% so one kind of hard thing about stateless<00:34:02.290> clients<00:34:02.830> that<00:34:02.980> I<00:34:03.010> think<00:34:03.310> it's 00:34:03.450 --> 00:34:03.460 align:start position:0% stateless clients that I think it's 00:34:03.460 --> 00:34:05.340 align:start position:0% stateless clients that I think it's important<00:34:04.030> to<00:34:04.180> be<00:34:04.300> very<00:34:04.330> transparent<00:34:05.050> and 00:34:05.340 --> 00:34:05.350 align:start position:0% important to be very transparent and 00:34:05.350 --> 00:34:08.490 align:start position:0% important to be very transparent and clear<00:34:05.500> about<00:34:05.800> is<00:34:06.130> that<00:34:06.330> meet<00:34:07.330> the<00:34:07.840> making 00:34:08.490 --> 00:34:08.500 align:start position:0% clear about is that meet the making 00:34:08.500 --> 00:34:11.070 align:start position:0% clear about is that meet the making stateless<00:34:09.040> clients<00:34:09.580> work<00:34:09.940> well<00:34:10.330> ultimately 00:34:11.070 --> 00:34:11.080 align:start position:0% stateless clients work well ultimately 00:34:11.080 --> 00:34:13.920 align:start position:0% stateless clients work well ultimately will<00:34:12.010> require<00:34:12.520> the<00:34:12.880> basically<00:34:13.540> the<00:34:13.720> same 00:34:13.920 --> 00:34:13.930 align:start position:0% will require the basically the same 00:34:13.930 --> 00:34:16.320 align:start position:0% will require the basically the same kinds<00:34:14.380> of<00:34:14.530> kind<00:34:14.980> of<00:34:15.040> gas<00:34:15.250> cost<00:34:15.490> sacrifices 00:34:16.320 --> 00:34:16.330 align:start position:0% kinds of kind of gas cost sacrifices 00:34:16.330 --> 00:34:17.520 align:start position:0% kinds of kind of gas cost sacrifices that<00:34:16.360> we<00:34:16.630> talk<00:34:16.810> that<00:34:17.230> we 00:34:17.520 --> 00:34:17.530 align:start position:0% that we talk that we 00:34:17.530 --> 00:34:19.980 align:start position:0% that we talk that we but<00:34:17.830> in<00:34:17.919> the<00:34:17.980> first<00:34:18.100> question<00:34:18.730> but<00:34:18.990> probably 00:34:19.980 --> 00:34:19.990 align:start position:0% but in the first question but probably 00:34:19.990 --> 00:34:22.860 align:start position:0% but in the first question but probably to<00:34:20.230> an<00:34:20.620> to<00:34:21.250> an<00:34:21.400> even<00:34:21.640> greater<00:34:21.820> scale<00:34:22.210> right<00:34:22.630> so 00:34:22.860 --> 00:34:22.870 align:start position:0% to an to an even greater scale right so 00:34:22.870 --> 00:34:26.940 align:start position:0% to an to an even greater scale right so for<00:34:23.110> example<00:34:23.710> the<00:34:24.700> witness<00:34:25.360> size<00:34:26.050> so<00:34:26.500> the<00:34:26.650> size 00:34:26.940 --> 00:34:26.950 align:start position:0% for example the witness size so the size 00:34:26.950 --> 00:34:29.100 align:start position:0% for example the witness size so the size of<00:34:27.400> like<00:34:27.730> extra<00:34:28.150> Merkel<00:34:28.450> data<00:34:28.690> that<00:34:28.929> you<00:34:29.020> would 00:34:29.100 --> 00:34:29.110 align:start position:0% of like extra Merkel data that you would 00:34:29.110 --> 00:34:32.850 align:start position:0% of like extra Merkel data that you would needs<00:34:29.320> to<00:34:29.530> pass<00:34:29.770> for<00:34:30.669> to<00:34:31.050> verify<00:34:32.050> a<00:34:32.320> worst<00:34:32.679> case 00:34:32.850 --> 00:34:32.860 align:start position:0% needs to pass for to verify a worst case 00:34:32.860 --> 00:34:34.740 align:start position:0% needs to pass for to verify a worst case block<00:34:33.429> right<00:34:33.669> now<00:34:33.880> is<00:34:34.210> about<00:34:34.480> three<00:34:34.690> hundred 00:34:34.740 --> 00:34:34.750 align:start position:0% block right now is about three hundred 00:34:34.750 --> 00:34:36.899 align:start position:0% block right now is about three hundred and<00:34:35.050> thirty<00:34:35.440> megabytes<00:34:36.010> and<00:34:36.250> that's 00:34:36.899 --> 00:34:36.909 align:start position:0% and thirty megabytes and that's 00:34:36.909 --> 00:34:39.090 align:start position:0% and thirty megabytes and that's basically<00:34:37.330> because<00:34:37.570> you<00:34:38.140> have<00:34:38.620> contracts 00:34:39.090 --> 00:34:39.100 align:start position:0% basically because you have contracts 00:34:39.100 --> 00:34:40.800 align:start position:0% basically because you have contracts calling<00:34:39.460> that<00:34:39.610> seven<00:34:39.880> hundred<00:34:39.909> gasps<00:34:40.360> twenty 00:34:40.800 --> 00:34:40.810 align:start position:0% calling that seven hundred gasps twenty 00:34:40.810 --> 00:34:42.780 align:start position:0% calling that seven hundred gasps twenty four<00:34:41.020> thousand<00:34:41.470> gasps<00:34:41.650> for<00:34:41.919> a<00:34:41.950> contract<00:34:42.520> and 00:34:42.780 --> 00:34:42.790 align:start position:0% four thousand gasps for a contract and 00:34:42.790 --> 00:34:44.010 align:start position:0% four thousand gasps for a contract and then<00:34:42.880> add<00:34:43.060> four<00:34:43.300> thousand<00:34:43.630> bytes<00:34:43.750> for<00:34:43.990> a 00:34:44.010 --> 00:34:44.020 align:start position:0% then add four thousand bytes for a 00:34:44.020 --> 00:34:46.860 align:start position:0% then add four thousand bytes for a witness<00:34:44.320> twenty<00:34:44.620> eight<00:34:44.740> thousand<00:34:45.190> x<00:34:45.870> fourteen 00:34:46.860 --> 00:34:46.870 align:start position:0% witness twenty eight thousand x fourteen 00:34:46.870 --> 00:34:48.659 align:start position:0% witness twenty eight thousand x fourteen hundred<00:34:47.320> and<00:34:47.620> like<00:34:47.800> you've<00:34:47.950> got<00:34:48.070> you've<00:34:48.640> got 00:34:48.659 --> 00:34:48.669 align:start position:0% hundred and like you've got you've got 00:34:48.669 --> 00:34:50.130 align:start position:0% hundred and like you've got you've got your<00:34:48.880> hundreds<00:34:49.179> of<00:34:49.300> megabytes<00:34:49.570> right<00:34:49.929> there 00:34:50.130 --> 00:34:50.140 align:start position:0% your hundreds of megabytes right there 00:34:50.140 --> 00:34:53.190 align:start position:0% your hundreds of megabytes right there so<00:34:50.950> and<00:34:51.490> then<00:34:52.210> there's<00:34:52.510> kind<00:34:52.780> of<00:34:52.840> smaller 00:34:53.190 --> 00:34:53.200 align:start position:0% so and then there's kind of smaller 00:34:53.200 --> 00:34:55.200 align:start position:0% so and then there's kind of smaller versions<00:34:53.770> of<00:34:53.950> this<00:34:54.130> attack<00:34:54.550> with<00:34:54.820> things<00:34:55.030> like 00:34:55.200 --> 00:34:55.210 align:start position:0% versions of this attack with things like 00:34:55.210 --> 00:34:57.300 align:start position:0% versions of this attack with things like the<00:34:55.390> balance<00:34:55.720> off<00:34:55.900> code<00:34:56.110> SSO<00:34:56.770> load<00:34:56.919> and<00:34:57.100> all<00:34:57.190> of 00:34:57.300 --> 00:34:57.310 align:start position:0% the balance off code SSO load and all of 00:34:57.310 --> 00:35:00.270 align:start position:0% the balance off code SSO load and all of those<00:34:57.430> things<00:34:57.790> so<00:34:58.510> I<00:34:58.990> think<00:34:59.530> we<00:35:00.010> will 00:35:00.270 --> 00:35:00.280 align:start position:0% those things so I think we will 00:35:00.280 --> 00:35:02.760 align:start position:0% those things so I think we will ultimately<00:35:00.640> need<00:35:01.390> to<00:35:01.630> have<00:35:01.780> changes<00:35:02.320> that<00:35:02.530> say 00:35:02.760 --> 00:35:02.770 align:start position:0% ultimately need to have changes that say 00:35:02.770 --> 00:35:04.890 align:start position:0% ultimately need to have changes that say like<00:35:03.010> one<00:35:03.310> the<00:35:04.000> gasps<00:35:04.180> cost<00:35:04.510> for<00:35:04.780> these 00:35:04.890 --> 00:35:04.900 align:start position:0% like one the gasps cost for these 00:35:04.900 --> 00:35:07.410 align:start position:0% like one the gasps cost for these storage<00:35:05.200> accessing<00:35:05.830> of<00:35:05.950> course<00:35:06.270> opcodes<00:35:07.270> go<00:35:07.390> a 00:35:07.410 --> 00:35:07.420 align:start position:0% storage accessing of course opcodes go a 00:35:07.420 --> 00:35:11.640 align:start position:0% storage accessing of course opcodes go a lot<00:35:07.570> more<00:35:08.010> to<00:35:09.010> is<00:35:09.880> that<00:35:10.360> the<00:35:10.540> gas<00:35:10.870> cost<00:35:11.290> for 00:35:11.640 --> 00:35:11.650 align:start position:0% lot more to is that the gas cost for 00:35:11.650 --> 00:35:14.190 align:start position:0% lot more to is that the gas cost for accessing<00:35:12.480> contracts<00:35:13.480> that<00:35:13.660> have<00:35:13.720> a<00:35:13.870> large 00:35:14.190 --> 00:35:14.200 align:start position:0% accessing contracts that have a large 00:35:14.200 --> 00:35:16.050 align:start position:0% accessing contracts that have a large storage<00:35:14.590> like<00:35:15.070> what<00:35:15.250> needs<00:35:15.430> to<00:35:15.490> go<00:35:15.670> up<00:35:15.790> even 00:35:16.050 --> 00:35:16.060 align:start position:0% storage like what needs to go up even 00:35:16.060 --> 00:35:18.750 align:start position:0% storage like what needs to go up even further<00:35:16.240> right<00:35:16.570> so<00:35:16.780> for<00:35:16.960> example<00:35:17.530> charge<00:35:18.250> one 00:35:18.750 --> 00:35:18.760 align:start position:0% further right so for example charge one 00:35:18.760 --> 00:35:20.670 align:start position:0% further right so for example charge one gasp<00:35:19.000> provide<00:35:19.510> of<00:35:19.690> provide<00:35:20.110> of<00:35:20.260> code<00:35:20.470> that<00:35:20.500> you 00:35:20.670 --> 00:35:20.680 align:start position:0% gasp provide of provide of code that you 00:35:20.680 --> 00:35:22.920 align:start position:0% gasp provide of provide of code that you read<00:35:20.950> and<00:35:21.580> if<00:35:21.730> we<00:35:21.880> want<00:35:22.060> to<00:35:22.150> make<00:35:22.330> this<00:35:22.480> nicer 00:35:22.920 --> 00:35:22.930 align:start position:0% read and if we want to make this nicer 00:35:22.930 --> 00:35:24.930 align:start position:0% read and if we want to make this nicer one<00:35:23.200> thing<00:35:23.500> we<00:35:23.620> could<00:35:23.830> do<00:35:24.010> for<00:35:24.220> example<00:35:24.250> is<00:35:24.820> we 00:35:24.930 --> 00:35:24.940 align:start position:0% one thing we could do for example is we 00:35:24.940 --> 00:35:26.310 align:start position:0% one thing we could do for example is we could<00:35:25.120> waive<00:35:25.360> the<00:35:25.570> extra<00:35:25.900> fee<00:35:26.080> if<00:35:26.200> the 00:35:26.310 --> 00:35:26.320 align:start position:0% could waive the extra fee if the 00:35:26.320 --> 00:35:28.440 align:start position:0% could waive the extra fee if the contract<00:35:26.770> was<00:35:26.950> accessed<00:35:27.400> say<00:35:28.060> within<00:35:28.360> the 00:35:28.440 --> 00:35:28.450 align:start position:0% contract was accessed say within the 00:35:28.450 --> 00:35:30.510 align:start position:0% contract was accessed say within the last<00:35:28.630> ten<00:35:28.840> thousand<00:35:29.230> blocks<00:35:29.410> and<00:35:29.710> that<00:35:30.340> would 00:35:30.510 --> 00:35:30.520 align:start position:0% last ten thousand blocks and that would 00:35:30.520 --> 00:35:33.180 align:start position:0% last ten thousand blocks and that would reflect<00:35:30.850> the<00:35:31.360> kind<00:35:31.690> of<00:35:31.810> the<00:35:32.320> actual<00:35:32.710> load<00:35:32.980> of 00:35:33.180 --> 00:35:33.190 align:start position:0% reflect the kind of the actual load of 00:35:33.190 --> 00:35:34.830 align:start position:0% reflect the kind of the actual load of kind<00:35:33.370> of<00:35:33.460> quote<00:35:33.670> almost<00:35:33.910> stateless<00:35:34.450> clients 00:35:34.830 --> 00:35:34.840 align:start position:0% kind of quote almost stateless clients 00:35:34.840 --> 00:35:36.060 align:start position:0% kind of quote almost stateless clients that<00:35:34.990> keep<00:35:35.110> stayed<00:35:35.350> around<00:35:35.470> for<00:35:35.800> a<00:35:35.830> little<00:35:35.920> bit 00:35:36.060 --> 00:35:36.070 align:start position:0% that keep stayed around for a little bit 00:35:36.070 --> 00:35:40.590 align:start position:0% that keep stayed around for a little bit of<00:35:36.310> time<00:35:36.520> so<00:35:37.620> like<00:35:38.620> those<00:35:39.400> kinds<00:35:39.880> of<00:35:40.000> like<00:35:40.210> that 00:35:40.590 --> 00:35:40.600 align:start position:0% of time so like those kinds of like that 00:35:40.600 --> 00:35:42.990 align:start position:0% of time so like those kinds of like that kind<00:35:40.930> of<00:35:40.990> rebalancing<00:35:41.800> would<00:35:42.460> need<00:35:42.730> to<00:35:42.880> be 00:35:42.990 --> 00:35:43.000 align:start position:0% kind of rebalancing would need to be 00:35:43.000 --> 00:35:44.730 align:start position:0% kind of rebalancing would need to be thought<00:35:43.240> thought<00:35:43.870> about<00:35:44.080> as<00:35:44.230> well<00:35:44.410> so 00:35:44.730 --> 00:35:44.740 align:start position:0% thought thought about as well so 00:35:44.740 --> 00:35:46.860 align:start position:0% thought thought about as well so basically<00:35:44.860> kind<00:35:45.430> of<00:35:45.580> for<00:35:46.240> multiple<00:35:46.720> reasons 00:35:46.860 --> 00:35:46.870 align:start position:0% basically kind of for multiple reasons 00:35:46.870 --> 00:35:49.890 align:start position:0% basically kind of for multiple reasons like<00:35:47.700> developers<00:35:48.700> should<00:35:49.030> expect<00:35:49.480> that<00:35:49.660> kind 00:35:49.890 --> 00:35:49.900 align:start position:0% like developers should expect that kind 00:35:49.900 --> 00:35:52.740 align:start position:0% like developers should expect that kind of<00:35:50.080> IO<00:35:50.530> is<00:35:51.010> likely<00:35:51.280> to<00:35:51.610> storage<00:35:52.390> reading 00:35:52.740 --> 00:35:52.750 align:start position:0% of IO is likely to storage reading 00:35:52.750 --> 00:35:54.570 align:start position:0% of IO is likely to storage reading account<00:35:53.290> reading<00:35:53.650> cross<00:35:53.860> contract<00:35:54.310> calling 00:35:54.570 --> 00:35:54.580 align:start position:0% account reading cross contract calling 00:35:54.580 --> 00:35:55.890 align:start position:0% account reading cross contract calling is<00:35:54.670> likely<00:35:54.880> to<00:35:55.060> get<00:35:55.180> more<00:35:55.360> expensive<00:35:55.810> relative 00:35:55.890 --> 00:35:55.900 align:start position:0% is likely to get more expensive relative 00:35:55.900 --> 00:35:59.760 align:start position:0% is likely to get more expensive relative to<00:35:56.230> other<00:35:56.350> things<00:35:57.900> just<00:35:58.900> to<00:35:58.990> pause<00:35:59.170> this<00:35:59.380> topic 00:35:59.760 --> 00:35:59.770 align:start position:0% to other things just to pause this topic 00:35:59.770 --> 00:36:00.810 align:start position:0% to other things just to pause this topic for<00:35:59.920> a<00:35:59.950> second<00:36:00.280> I<00:36:00.310> wanted<00:36:00.550> to<00:36:00.610> introduce 00:36:00.810 --> 00:36:00.820 align:start position:0% for a second I wanted to introduce 00:36:00.820 --> 00:36:03.930 align:start position:0% for a second I wanted to introduce somebody<00:36:01.210> just<00:36:01.480> got<00:36:01.660> here<00:36:02.010> Felix<00:36:03.010> Felix<00:36:03.700> take 00:36:03.930 --> 00:36:03.940 align:start position:0% somebody just got here Felix Felix take 00:36:03.940 --> 00:36:04.830 align:start position:0% somebody just got here Felix Felix take the<00:36:04.030> mic<00:36:04.210> and<00:36:04.330> just<00:36:04.390> give<00:36:04.570> a<00:36:04.600> quick 00:36:04.830 --> 00:36:04.840 align:start position:0% the mic and just give a quick 00:36:04.840 --> 00:36:06.060 align:start position:0% the mic and just give a quick introduction<00:36:05.200> he<00:36:05.470> works<00:36:05.620> on<00:36:05.740> some<00:36:05.920> of<00:36:06.010> the 00:36:06.060 --> 00:36:06.070 align:start position:0% introduction he works on some of the 00:36:06.070 --> 00:36:09.240 align:start position:0% introduction he works on some of the networking<00:36:06.490> stack<00:36:06.910> yeah<00:36:07.900> I'm<00:36:08.290> Felix<00:36:08.620> I<00:36:08.800> work 00:36:09.240 --> 00:36:09.250 align:start position:0% networking stack yeah I'm Felix I work 00:36:09.250 --> 00:36:12.930 align:start position:0% networking stack yeah I'm Felix I work on<00:36:09.430> guest<00:36:09.640> on<00:36:09.880> on<00:36:10.420> the<00:36:10.660> networking<00:36:11.140> uh<00:36:11.980> I<00:36:12.340> just 00:36:12.930 --> 00:36:12.940 align:start position:0% on guest on on the networking uh I just 00:36:12.940 --> 00:36:14.850 align:start position:0% on guest on on the networking uh I just got<00:36:13.150> here<00:36:13.300> from<00:36:13.360> another<00:36:13.840> a<00:36:14.020> I<00:36:14.050> missed<00:36:14.710> the 00:36:14.850 --> 00:36:14.860 align:start position:0% got here from another a I missed the 00:36:14.860 --> 00:36:17.970 align:start position:0% got here from another a I missed the beginning<00:36:15.220> so<00:36:15.400> I<00:36:15.430> don't<00:36:15.700> really<00:36:15.880> know<00:36:16.980> what 00:36:17.970 --> 00:36:17.980 align:start position:0% beginning so I don't really know what 00:36:17.980 --> 00:36:19.320 align:start position:0% beginning so I don't really know what you<00:36:18.100> guys<00:36:18.220> talking<00:36:18.550> about<00:36:18.580> what<00:36:18.700> I<00:36:18.880> hear<00:36:19.180> it's 00:36:19.320 --> 00:36:19.330 align:start position:0% you guys talking about what I hear it's 00:36:19.330 --> 00:36:20.970 align:start position:0% you guys talking about what I hear it's mostly<00:36:19.600> been<00:36:19.840> about<00:36:19.870> stateless<00:36:20.440> fans<00:36:20.680> which 00:36:20.970 --> 00:36:20.980 align:start position:0% mostly been about stateless fans which 00:36:20.980 --> 00:36:23.310 align:start position:0% mostly been about stateless fans which is<00:36:21.130> actually<00:36:21.640> which<00:36:21.820> add<00:36:22.150> also<00:36:22.930> huge 00:36:23.310 --> 00:36:23.320 align:start position:0% is actually which add also huge 00:36:23.320 --> 00:36:25.590 align:start position:0% is actually which add also huge challenges<00:36:23.860> on<00:36:24.070> the<00:36:24.280> on<00:36:24.790> the<00:36:25.120> networking<00:36:25.450> side 00:36:25.590 --> 00:36:25.600 align:start position:0% challenges on the on the networking side 00:36:25.600 --> 00:36:28.800 align:start position:0% challenges on the on the networking side so<00:36:26.020> I<00:36:26.080> feel<00:36:26.350> like<00:36:26.380> the<00:36:27.450> status<00:36:28.450> lines<00:36:28.660> is 00:36:28.800 --> 00:36:28.810 align:start position:0% so I feel like the status lines is 00:36:28.810 --> 00:36:31.260 align:start position:0% so I feel like the status lines is basically<00:36:29.170> just<00:36:29.560> this<00:36:29.980> unsolved<00:36:30.580> is<00:36:30.760> like 00:36:31.260 --> 00:36:31.270 align:start position:0% basically just this unsolved is like 00:36:31.270 --> 00:36:33.120 align:start position:0% basically just this unsolved is like any<00:36:31.630> other<00:36:32.260> problem<00:36:32.619> there<00:36:32.860> has<00:36:32.980> been 00:36:33.120 --> 00:36:33.130 align:start position:0% any other problem there has been 00:36:33.130 --> 00:36:34.859 align:start position:0% any other problem there has been progress<00:36:33.430> but<00:36:33.700> it's<00:36:34.090> not<00:36:34.270> really<00:36:34.630> something 00:36:34.859 --> 00:36:34.869 align:start position:0% progress but it's not really something 00:36:34.869 --> 00:36:37.830 align:start position:0% progress but it's not really something that<00:36:35.230> we<00:36:35.740> can<00:36:35.920> honestly<00:36:36.070> say<00:36:36.460> like<00:36:36.760> it's<00:36:36.970> easy 00:36:37.830 --> 00:36:37.840 align:start position:0% that we can honestly say like it's easy 00:36:37.840 --> 00:36:40.680 align:start position:0% that we can honestly say like it's easy to<00:36:38.050> pull<00:36:38.470> off<00:36:38.500> like<00:36:39.430> yeah<00:36:40.000> I<00:36:40.030> would<00:36:40.270> I<00:36:40.480> would 00:36:40.680 --> 00:36:40.690 align:start position:0% to pull off like yeah I would I would 00:36:40.690 --> 00:36:42.480 align:start position:0% to pull off like yeah I would I would use<00:36:40.869> the<00:36:41.020> same<00:36:41.200> analogy<00:36:41.440> as<00:36:41.770> for<00:36:42.040> quantum 00:36:42.480 --> 00:36:42.490 align:start position:0% use the same analogy as for quantum 00:36:42.490 --> 00:36:45.900 align:start position:0% use the same analogy as for quantum computers<00:36:42.910> I've<00:36:43.240> heard<00:36:43.570> like<00:36:44.050> to<00:36:44.410> as<00:36:45.070> I've 00:36:45.900 --> 00:36:45.910 align:start position:0% computers I've heard like to as I've 00:36:45.910 --> 00:36:48.390 align:start position:0% computers I've heard like to as I've heard<00:36:46.240> about<00:36:46.360> two<00:36:46.690> years<00:36:46.869> ago<00:36:47.020> that<00:36:47.500> in<00:36:47.800> terms 00:36:48.390 --> 00:36:48.400 align:start position:0% heard about two years ago that in terms 00:36:48.400 --> 00:36:51.600 align:start position:0% heard about two years ago that in terms of<00:36:48.580> quantum<00:36:49.030> computers<00:36:49.510> all<00:36:50.200> the<00:36:50.530> all<00:36:51.369> the 00:36:51.600 --> 00:36:51.610 align:start position:0% of quantum computers all the all the 00:36:51.610 --> 00:36:53.460 align:start position:0% of quantum computers all the all the fundamental<00:36:52.210> challenges<00:36:52.660> have<00:36:52.869> been<00:36:53.050> solved 00:36:53.460 --> 00:36:53.470 align:start position:0% fundamental challenges have been solved 00:36:53.470 --> 00:36:55.740 align:start position:0% fundamental challenges have been solved now<00:36:53.830> it's<00:36:54.070> the<00:36:54.250> matter<00:36:54.460> of<00:36:54.610> engineering<00:36:55.300> to 00:36:55.740 --> 00:36:55.750 align:start position:0% now it's the matter of engineering to 00:36:55.750 --> 00:36:59.460 align:start position:0% now it's the matter of engineering to get<00:36:55.869> to<00:36:56.080> build<00:36:56.290> one<00:36:56.530> I<00:36:57.600> mean<00:36:58.600> it's<00:36:58.810> it's<00:36:59.170> so 00:36:59.460 --> 00:36:59.470 align:start position:0% get to build one I mean it's it's so 00:36:59.470 --> 00:37:03.150 align:start position:0% get to build one I mean it's it's so there<00:37:00.340> is<00:37:00.460> no<00:37:00.700> real<00:37:01.240> kind<00:37:01.990> of<00:37:02.080> super<00:37:02.740> complex 00:37:03.150 --> 00:37:03.160 align:start position:0% there is no real kind of super complex 00:37:03.160 --> 00:37:05.490 align:start position:0% there is no real kind of super complex stuff<00:37:03.550> in<00:37:03.850> stateless<00:37:04.300> Minds<00:37:04.570> that<00:37:04.840> the<00:37:05.140> idea 00:37:05.490 --> 00:37:05.500 align:start position:0% stuff in stateless Minds that the idea 00:37:05.500 --> 00:37:07.500 align:start position:0% stuff in stateless Minds that the idea is<00:37:05.560> super<00:37:05.740> simple<00:37:06.040> you<00:37:06.430> can<00:37:06.820> yes<00:37:07.119> there<00:37:07.360> would 00:37:07.500 --> 00:37:07.510 align:start position:0% is super simple you can yes there would 00:37:07.510 --> 00:37:08.850 align:start position:0% is super simple you can yes there would be<00:37:07.540> more<00:37:07.900> you<00:37:08.470> know 00:37:08.850 --> 00:37:08.860 align:start position:0% be more you know 00:37:08.860 --> 00:37:10.800 align:start position:0% be more you know shuffling<00:37:09.670> that<00:37:09.880> data<00:37:10.210> around<00:37:10.450> the<00:37:10.630> network 00:37:10.800 --> 00:37:10.810 align:start position:0% shuffling that data around the network 00:37:10.810 --> 00:37:13.230 align:start position:0% shuffling that data around the network there<00:37:11.500> would<00:37:11.650> be<00:37:11.680> some<00:37:11.920> issues<00:37:12.250> with<00:37:12.400> that<00:37:12.490> but 00:37:13.230 --> 00:37:13.240 align:start position:0% there would be some issues with that but 00:37:13.240 --> 00:37:16.880 align:start position:0% there would be some issues with that but I<00:37:13.480> don't<00:37:13.750> see<00:37:13.990> them<00:37:14.290> as<00:37:14.350> being<00:37:14.770> fundamental 00:37:16.880 --> 00:37:16.890 align:start position:0% I don't see them as being fundamental 00:37:16.890 --> 00:37:21.720 align:start position:0% I don't see them as being fundamental can<00:37:17.890> I<00:37:18.040> interrupt<00:37:19.170> so<00:37:20.170> I<00:37:20.470> I<00:37:20.980> think<00:37:21.490> there<00:37:21.700> are 00:37:21.720 --> 00:37:21.730 align:start position:0% can I interrupt so I I think there are 00:37:21.730 --> 00:37:23.670 align:start position:0% can I interrupt so I I think there are really<00:37:22.270> fundamental<00:37:22.600> issues<00:37:23.200> there<00:37:23.380> so<00:37:23.560> the 00:37:23.670 --> 00:37:23.680 align:start position:0% really fundamental issues there so the 00:37:23.680 --> 00:37:25.920 align:start position:0% really fundamental issues there so the problem<00:37:24.010> is<00:37:24.100> that<00:37:24.280> the<00:37:24.880> moment<00:37:25.240> so<00:37:25.600> currently 00:37:25.920 --> 00:37:25.930 align:start position:0% problem is that the moment so currently 00:37:25.930 --> 00:37:27.480 align:start position:0% problem is that the moment so currently transactions<00:37:26.650> are<00:37:26.740> really<00:37:26.950> tiny 00:37:27.480 --> 00:37:27.490 align:start position:0% transactions are really tiny 00:37:27.490 --> 00:37:29.370 align:start position:0% transactions are really tiny the<00:37:27.850> moment<00:37:28.210> you<00:37:28.390> start<00:37:28.720> entering<00:37:28.960> into 00:37:29.370 --> 00:37:29.380 align:start position:0% the moment you start entering into 00:37:29.380 --> 00:37:31.470 align:start position:0% the moment you start entering into territories<00:37:29.980> of<00:37:30.100> megabytes<00:37:30.400> and<00:37:30.910> we're<00:37:31.360> not 00:37:31.470 --> 00:37:31.480 align:start position:0% territories of megabytes and we're not 00:37:31.480 --> 00:37:32.880 align:start position:0% territories of megabytes and we're not talking<00:37:31.810> about<00:37:31.900> hundreds<00:37:32.290> of<00:37:32.350> megabytes<00:37:32.619> as 00:37:32.880 --> 00:37:32.890 align:start position:0% talking about hundreds of megabytes as 00:37:32.890 --> 00:37:35.130 align:start position:0% talking about hundreds of megabytes as megabytes<00:37:33.369> the<00:37:34.210> whole<00:37:34.330> networking<00:37:34.780> layer 00:37:35.130 --> 00:37:35.140 align:start position:0% megabytes the whole networking layer 00:37:35.140 --> 00:37:37.590 align:start position:0% megabytes the whole networking layer needs<00:37:35.410> to<00:37:35.590> be<00:37:35.710> gutted<00:37:36.100> out<00:37:36.220> and<00:37:36.600> retrofitted 00:37:37.590 --> 00:37:37.600 align:start position:0% needs to be gutted out and retrofitted 00:37:37.600 --> 00:37:39.500 align:start position:0% needs to be gutted out and retrofitted so<00:37:37.720> you<00:37:37.810> cannot<00:37:38.080> own<00:37:38.320> you<00:37:38.710> can<00:37:38.890> chunk<00:37:39.130> up 00:37:39.500 --> 00:37:39.510 align:start position:0% so you cannot own you can chunk up 00:37:39.510 --> 00:37:42.180 align:start position:0% so you cannot own you can chunk up messages<00:37:40.510> into<00:37:40.720> smaller<00:37:41.080> pieces<00:37:41.320> that's<00:37:41.890> a 00:37:42.180 --> 00:37:42.190 align:start position:0% messages into smaller pieces that's a 00:37:42.190 --> 00:37:45.420 align:start position:0% messages into smaller pieces that's a lot<00:37:42.790> of<00:37:42.970> engineering<00:37:43.270> effort<00:37:44.430> research 00:37:45.420 --> 00:37:45.430 align:start position:0% lot of engineering effort research 00:37:45.430 --> 00:37:49.980 align:start position:0% lot of engineering effort research effort<00:37:46.710> let<00:37:47.710> me<00:37:47.770> just<00:37:47.950> finish<00:37:48.190> however<00:37:48.990> even 00:37:49.980 --> 00:37:49.990 align:start position:0% effort let me just finish however even 00:37:49.990 --> 00:37:51.810 align:start position:0% effort let me just finish however even if<00:37:50.109> that<00:37:50.470> is<00:37:50.650> soft<00:37:50.950> and<00:37:51.190> the<00:37:51.250> network<00:37:51.609> data 00:37:51.810 --> 00:37:51.820 align:start position:0% if that is soft and the network data 00:37:51.820 --> 00:37:55.740 align:start position:0% if that is soft and the network data shuffling<00:37:52.300> is<00:37:52.420> soft<00:37:52.690> then<00:37:53.410> if<00:37:53.800> you<00:37:54.420> so<00:37:55.420> all<00:37:55.630> of 00:37:55.740 --> 00:37:55.750 align:start position:0% shuffling is soft then if you so all of 00:37:55.750 --> 00:37:57.240 align:start position:0% shuffling is soft then if you so all of a<00:37:55.810> sudden<00:37:56.050> you<00:37:56.140> also<00:37:56.410> need<00:37:56.680> to<00:37:56.710> store<00:37:57.100> these 00:37:57.240 --> 00:37:57.250 align:start position:0% a sudden you also need to store these 00:37:57.250 --> 00:37:59.810 align:start position:0% a sudden you also need to store these witnesses<00:37:57.820> beside<00:37:58.750> the<00:37:58.900> transaction<00:37:59.500> so<00:37:59.710> you 00:37:59.810 --> 00:37:59.820 align:start position:0% witnesses beside the transaction so you 00:37:59.820 --> 00:38:03.060 align:start position:0% witnesses beside the transaction so you implode<00:38:00.820> or<00:38:01.060> explode<00:38:01.150> sorry<00:38:01.840> the<00:38:02.470> the<00:38:02.890> data 00:38:03.060 --> 00:38:03.070 align:start position:0% implode or explode sorry the the data 00:38:03.070 --> 00:38:05.099 align:start position:0% implode or explode sorry the the data usage<00:38:03.369> of<00:38:03.700> the<00:38:03.850> immutable<00:38:04.119> side<00:38:04.630> of<00:38:04.750> the<00:38:04.900> chain 00:38:05.099 --> 00:38:05.109 align:start position:0% usage of the immutable side of the chain 00:38:05.109 --> 00:38:07.260 align:start position:0% usage of the immutable side of the chain and<00:38:05.350> we<00:38:05.859> can<00:38:06.010> say<00:38:06.220> that<00:38:06.400> yeah<00:38:06.550> but<00:38:07.030> that's 00:38:07.260 --> 00:38:07.270 align:start position:0% and we can say that yeah but that's 00:38:07.270 --> 00:38:09.000 align:start position:0% and we can say that yeah but that's cheap<00:38:07.570> to<00:38:07.750> store<00:38:07.990> we<00:38:08.109> can<00:38:08.260> put<00:38:08.380> it<00:38:08.470> on<00:38:08.590> an<00:38:08.680> HDD 00:38:09.000 --> 00:38:09.010 align:start position:0% cheap to store we can put it on an HDD 00:38:09.010 --> 00:38:11.609 align:start position:0% cheap to store we can put it on an HDD sure<00:38:09.430> but<00:38:09.670> we're<00:38:10.180> already<00:38:10.390> at<00:38:10.630> 100<00:38:11.170> gigabytes 00:38:11.609 --> 00:38:11.619 align:start position:0% sure but we're already at 100 gigabytes 00:38:11.619 --> 00:38:14.970 align:start position:0% sure but we're already at 100 gigabytes 150<00:38:12.369> gigs<00:38:12.550> of<00:38:13.020> tiny<00:38:14.020> transactions<00:38:14.830> now 00:38:14.970 --> 00:38:14.980 align:start position:0% 150 gigs of tiny transactions now 00:38:14.980 --> 00:38:16.290 align:start position:0% 150 gigs of tiny transactions now imagine<00:38:15.490> that<00:38:15.520> all<00:38:15.760> of<00:38:15.880> a<00:38:15.910> sudden<00:38:16.180> every 00:38:16.290 --> 00:38:16.300 align:start position:0% imagine that all of a sudden every 00:38:16.300 --> 00:38:18.030 align:start position:0% imagine that all of a sudden every transaction<00:38:16.660> will<00:38:16.900> be<00:38:16.990> twice<00:38:17.200> or<00:38:17.530> not<00:38:17.859> twice 00:38:18.030 --> 00:38:18.040 align:start position:0% transaction will be twice or not twice 00:38:18.040 --> 00:38:19.890 align:start position:0% transaction will be twice or not twice ten<00:38:18.310> times<00:38:18.550> the<00:38:18.700> size<00:38:18.910> and<00:38:19.270> maybe<00:38:19.450> instead<00:38:19.780> of 00:38:19.890 --> 00:38:19.900 align:start position:0% ten times the size and maybe instead of 00:38:19.900 --> 00:38:21.510 align:start position:0% ten times the size and maybe instead of one<00:38:20.170> hundred<00:38:20.260> fifty<00:38:20.590> gigs<00:38:20.950> would<00:38:21.130> we<00:38:21.400> would 00:38:21.510 --> 00:38:21.520 align:start position:0% one hundred fifty gigs would we would 00:38:21.520 --> 00:38:25.260 align:start position:0% one hundred fifty gigs would we would have<00:38:21.700> two<00:38:21.850> terabytes<00:38:22.359> of<00:38:22.570> immutable<00:38:23.470> chain 00:38:25.260 --> 00:38:25.270 align:start position:0% have two terabytes of immutable chain 00:38:25.270 --> 00:38:27.780 align:start position:0% have two terabytes of immutable chain basically<00:38:25.810> is<00:38:26.080> the<00:38:26.260> information<00:38:26.800> to<00:38:27.490> give<00:38:27.670> us 00:38:27.780 --> 00:38:27.790 align:start position:0% basically is the information to give us 00:38:27.790 --> 00:38:31.800 align:start position:0% basically is the information to give us they<00:38:27.940> was<00:38:28.120> playing<00:38:28.390> for<00:38:28.570> syncing<00:38:28.990> data<00:38:30.810> yes 00:38:31.800 --> 00:38:31.810 align:start position:0% they was playing for syncing data yes 00:38:31.810 --> 00:38:34.080 align:start position:0% they was playing for syncing data yes I'm<00:38:32.680> saying<00:38:32.890> like<00:38:33.100> that<00:38:33.370> basic<00:38:33.760> like<00:38:33.940> an 00:38:34.080 --> 00:38:34.090 align:start position:0% I'm saying like that basic like an 00:38:34.090 --> 00:38:36.600 align:start position:0% I'm saying like that basic like an archive<00:38:34.480> no<00:38:34.720> it<00:38:34.840> basically<00:38:35.230> is<00:38:35.560> the<00:38:36.190> note<00:38:36.400> the 00:38:36.600 --> 00:38:36.610 align:start position:0% archive no it basically is the note the 00:38:36.610 --> 00:38:38.730 align:start position:0% archive no it basically is the note the the<00:38:36.640> the<00:38:37.090> no<00:38:37.240> type<00:38:37.570> that<00:38:37.810> has<00:38:37.960> like<00:38:38.290> all<00:38:38.500> of<00:38:38.620> the 00:38:38.730 --> 00:38:38.740 align:start position:0% the the no type that has like all of the 00:38:38.740 --> 00:38:40.200 align:start position:0% the the no type that has like all of the data<00:38:38.950> was<00:38:39.160> the<00:38:39.310> ability<00:38:39.610> to<00:38:39.640> produce<00:38:39.850> it<00:38:40.120> on 00:38:40.200 --> 00:38:40.210 align:start position:0% data was the ability to produce it on 00:38:40.210 --> 00:38:42.830 align:start position:0% data was the ability to produce it on demand<00:38:40.390> for<00:38:40.690> any<00:38:40.780> transaction<00:38:41.460> yeah<00:38:42.460> but<00:38:42.640> my 00:38:42.830 --> 00:38:42.840 align:start position:0% demand for any transaction yeah but my 00:38:42.840 --> 00:38:45.240 align:start position:0% demand for any transaction yeah but my essentially<00:38:43.840> without<00:38:44.260> an<00:38:44.440> archive<00:38:44.800> node<00:38:45.010> you 00:38:45.240 --> 00:38:45.250 align:start position:0% essentially without an archive node you 00:38:45.250 --> 00:38:47.340 align:start position:0% essentially without an archive node you would<00:38:45.400> not<00:38:45.550> so<00:38:46.000> you<00:38:46.390> either<00:38:46.630> need<00:38:46.780> the<00:38:46.990> archive 00:38:47.340 --> 00:38:47.350 align:start position:0% would not so you either need the archive 00:38:47.350 --> 00:38:49.410 align:start position:0% would not so you either need the archive code<00:38:47.530> or<00:38:47.770> you<00:38:47.950> need<00:38:48.130> the<00:38:48.430> chain<00:38:48.790> of<00:38:48.910> witnesses 00:38:49.410 --> 00:38:49.420 align:start position:0% code or you need the chain of witnesses 00:38:49.420 --> 00:38:51.870 align:start position:0% code or you need the chain of witnesses so<00:38:50.380> one<00:38:50.560> thing<00:38:50.740> we<00:38:50.860> can<00:38:50.980> agree<00:38:51.130> on<00:38:51.310> with<00:38:51.550> status 00:38:51.870 --> 00:38:51.880 align:start position:0% so one thing we can agree on with status 00:38:51.880 --> 00:38:54.720 align:start position:0% so one thing we can agree on with status clients<00:38:52.180> is<00:38:52.300> that<00:38:52.510> basically<00:38:52.840> it<00:38:53.160> it<00:38:54.160> changes 00:38:54.720 --> 00:38:54.730 align:start position:0% clients is that basically it it changes 00:38:54.730 --> 00:38:56.960 align:start position:0% clients is that basically it it changes the<00:38:55.090> user<00:38:55.330> experience<00:38:55.630> a<00:38:55.930> lot<00:38:56.110> where 00:38:56.960 --> 00:38:56.970 align:start position:0% the user experience a lot where 00:38:56.970 --> 00:39:00.360 align:start position:0% the user experience a lot where previously<00:38:58.470> handing<00:38:59.470> the<00:38:59.560> state<00:38:59.800> was<00:39:00.040> kind<00:39:00.280> of 00:39:00.360 --> 00:39:00.370 align:start position:0% previously handing the state was kind of 00:39:00.370 --> 00:39:01.980 align:start position:0% previously handing the state was kind of if<00:39:00.610> areum's<00:39:00.970> problem<00:39:01.420> with<00:39:01.660> stateless 00:39:01.980 --> 00:39:01.990 align:start position:0% if areum's problem with stateless 00:39:01.990 --> 00:39:04.590 align:start position:0% if areum's problem with stateless clients<00:39:02.410> it's<00:39:02.560> a<00:39:02.710> user<00:39:03.010> problem<00:39:03.460> no<00:39:04.150> no<00:39:04.390> that's 00:39:04.590 --> 00:39:04.600 align:start position:0% clients it's a user problem no no that's 00:39:04.600 --> 00:39:06.480 align:start position:0% clients it's a user problem no no that's not<00:39:04.780> true<00:39:05.080> because<00:39:05.290> I<00:39:05.770> think<00:39:06.160> you<00:39:06.280> might<00:39:06.460> be 00:39:06.480 --> 00:39:06.490 align:start position:0% not true because I think you might be 00:39:06.490 --> 00:39:09.060 align:start position:0% not true because I think you might be confusing<00:39:06.640> it<00:39:07.390> with<00:39:07.420> what<00:39:08.350> I<00:39:08.380> call<00:39:08.620> status 00:39:09.060 --> 00:39:09.070 align:start position:0% confusing it with what I call status 00:39:09.070 --> 00:39:13.020 align:start position:0% confusing it with what I call status contracts<00:39:10.140> so<00:39:11.140> they<00:39:11.320> they're<00:39:11.890> so<00:39:12.280> stateless 00:39:13.020 --> 00:39:13.030 align:start position:0% contracts so they they're so stateless 00:39:13.030 --> 00:39:15.690 align:start position:0% contracts so they they're so stateless contracts<00:39:13.690> is<00:39:13.810> the<00:39:14.200> the<00:39:14.560> idea<00:39:14.890> it's<00:39:15.550> actually 00:39:15.690 --> 00:39:15.700 align:start position:0% contracts is the the idea it's actually 00:39:15.700 --> 00:39:20.070 align:start position:0% contracts is the the idea it's actually the<00:39:16.380> it's<00:39:17.380> a<00:39:17.500> design<00:39:17.800> pattern<00:39:18.390> where<00:39:19.390> we're<00:39:19.870> by 00:39:20.070 --> 00:39:20.080 align:start position:0% the it's a design pattern where we're by 00:39:20.080 --> 00:39:23.640 align:start position:0% the it's a design pattern where we're by your<00:39:20.410> start<00:39:21.930> instead<00:39:22.930> of<00:39:23.050> storing<00:39:23.470> your<00:39:23.500> data 00:39:23.640 --> 00:39:23.650 align:start position:0% your start instead of storing your data 00:39:23.650 --> 00:39:26.160 align:start position:0% your start instead of storing your data inside<00:39:24.280> the<00:39:24.310> contract<00:39:24.850> storage<00:39:25.240> you<00:39:25.810> store 00:39:26.160 --> 00:39:26.170 align:start position:0% inside the contract storage you store 00:39:26.170 --> 00:39:28.140 align:start position:0% inside the contract storage you store some<00:39:26.410> sort<00:39:26.620> of<00:39:26.650> miracle<00:39:26.890> route<00:39:27.250> and<00:39:27.520> then<00:39:28.030> you 00:39:28.140 --> 00:39:28.150 align:start position:0% some sort of miracle route and then you 00:39:28.150 --> 00:39:30.990 align:start position:0% some sort of miracle route and then you start<00:39:28.450> passing<00:39:28.690> the<00:39:29.140> they<00:39:29.920> like<00:39:30.430> you<00:39:30.580> pretend 00:39:30.990 --> 00:39:31.000 align:start position:0% start passing the they like you pretend 00:39:31.000 --> 00:39:32.550 align:start position:0% start passing the they like you pretend that<00:39:31.120> they're<00:39:31.420> the<00:39:31.630> data<00:39:31.840> somewhere<00:39:32.260> of 00:39:32.550 --> 00:39:32.560 align:start position:0% that they're the data somewhere of 00:39:32.560 --> 00:39:33.090 align:start position:0% that they're the data somewhere of change 00:39:33.090 --> 00:39:33.100 align:start position:0% change 00:39:33.100 --> 00:39:34.710 align:start position:0% change well<00:39:33.460> you<00:39:33.670> don't<00:39:33.790> pretend<00:39:34.180> that<00:39:34.300> there<00:39:34.480> is<00:39:34.570> of 00:39:34.710 --> 00:39:34.720 align:start position:0% well you don't pretend that there is of 00:39:34.720 --> 00:39:36.990 align:start position:0% well you don't pretend that there is of chain<00:39:34.960> but<00:39:35.500> whenever<00:39:35.770> your<00:39:36.190> do<00:39:36.610> something 00:39:36.990 --> 00:39:37.000 align:start position:0% chain but whenever your do something 00:39:37.000 --> 00:39:38.430 align:start position:0% chain but whenever your do something with<00:39:37.150> the<00:39:37.240> data<00:39:37.270> you<00:39:37.570> start<00:39:37.900> providing<00:39:38.170> the 00:39:38.430 --> 00:39:38.440 align:start position:0% with the data you start providing the 00:39:38.440 --> 00:39:39.870 align:start position:0% with the data you start providing the miracle<00:39:38.770> proofs<00:39:39.010> and<00:39:39.220> these<00:39:39.370> proofs<00:39:39.700> are 00:39:39.870 --> 00:39:39.880 align:start position:0% miracle proofs and these proofs are 00:39:39.880 --> 00:39:41.370 align:start position:0% miracle proofs and these proofs are actually<00:39:40.180> inside<00:39:40.480> the<00:39:40.540> transaction<00:39:41.170> and<00:39:41.350> that 00:39:41.370 --> 00:39:41.380 align:start position:0% actually inside the transaction and that 00:39:41.380 --> 00:39:43.530 align:start position:0% actually inside the transaction and that it<00:39:41.980> increases<00:39:42.310> the<00:39:42.460> size<00:39:42.730> of<00:39:42.910> transaction<00:39:43.390> and 00:39:43.530 --> 00:39:43.540 align:start position:0% it increases the size of transaction and 00:39:43.540 --> 00:39:46.080 align:start position:0% it increases the size of transaction and so<00:39:43.690> on<00:39:43.840> the<00:39:44.320> status<00:39:44.680> client<00:39:45.010> actually<00:39:45.190> remove 00:39:46.080 --> 00:39:46.090 align:start position:0% so on the status client actually remove 00:39:46.090 --> 00:39:48.570 align:start position:0% so on the status client actually remove it's<00:39:46.360> not<00:39:46.570> like<00:39:46.780> that<00:39:46.960> it<00:39:47.230> moves<00:39:47.560> the<00:39:47.890> the 00:39:48.570 --> 00:39:48.580 align:start position:0% it's not like that it moves the the 00:39:48.580 --> 00:39:51.450 align:start position:0% it's not like that it moves the the burden<00:39:49.000> into<00:39:49.360> the<00:39:49.480> actual<00:39:49.930> layer<00:39:50.320> in<00:39:50.830> the 00:39:51.450 --> 00:39:51.460 align:start position:0% burden into the actual layer in the 00:39:51.460 --> 00:39:54.120 align:start position:0% burden into the actual layer in the protocol<00:39:51.910> layer<00:39:52.120> it's<00:39:52.420> it's<00:39:52.780> not<00:39:52.990> the<00:39:53.320> the<00:39:53.890> job 00:39:54.120 --> 00:39:54.130 align:start position:0% protocol layer it's it's not the the job 00:39:54.130 --> 00:39:56.160 align:start position:0% protocol layer it's it's not the the job of<00:39:54.340> the<00:39:54.580> smart<00:39:55.030> contract<00:39:55.210> developer<00:39:55.870> will<00:39:56.020> not 00:39:56.160 --> 00:39:56.170 align:start position:0% of the smart contract developer will not 00:39:56.170 --> 00:39:58.050 align:start position:0% of the smart contract developer will not change<00:39:56.470> and<00:39:56.800> the<00:39:57.310> user<00:39:57.520> will<00:39:57.760> have<00:39:57.940> the 00:39:58.050 --> 00:39:58.060 align:start position:0% change and the user will have the 00:39:58.060 --> 00:39:59.910 align:start position:0% change and the user will have the exactly<00:39:58.450> the<00:39:58.570> same<00:39:58.630> experience<00:39:59.380> apart<00:39:59.740> from 00:39:59.910 --> 00:39:59.920 align:start position:0% exactly the same experience apart from 00:39:59.920 --> 00:40:02.490 align:start position:0% exactly the same experience apart from paying<00:40:00.400> more<00:40:00.730> for<00:40:00.760> the<00:40:01.060> state<00:40:01.270> access<00:40:01.690> so<00:40:02.230> as 00:40:02.490 --> 00:40:02.500 align:start position:0% paying more for the state access so as 00:40:02.500 --> 00:40:05.880 align:start position:0% paying more for the state access so as Vitalik<00:40:02.950> mentioned<00:40:03.370> the<00:40:04.270> call<00:40:04.780> up<00:40:05.380> codes<00:40:05.710> will 00:40:05.880 --> 00:40:05.890 align:start position:0% Vitalik mentioned the call up codes will 00:40:05.890 --> 00:40:07.230 align:start position:0% Vitalik mentioned the call up codes will be<00:40:05.920> more<00:40:06.160> expensive<00:40:06.460> because<00:40:06.760> you<00:40:07.000> have<00:40:07.120> to 00:40:07.230 --> 00:40:07.240 align:start position:0% be more expensive because you have to 00:40:07.240 --> 00:40:10.950 align:start position:0% be more expensive because you have to load<00:40:07.420> the<00:40:07.570> code<00:40:07.810> the<00:40:08.560> S<00:40:09.220> store<00:40:09.610> as<00:40:09.910> loads<00:40:10.480> and<00:40:10.840> s 00:40:10.950 --> 00:40:10.960 align:start position:0% load the code the S store as loads and s 00:40:10.960 --> 00:40:13.080 align:start position:0% load the code the S store as loads and s stores<00:40:11.320> will<00:40:11.500> be<00:40:11.530> more<00:40:11.830> expensive<00:40:12.130> balanced 00:40:13.080 --> 00:40:13.090 align:start position:0% stores will be more expensive balanced 00:40:13.090 --> 00:40:14.340 align:start position:0% stores will be more expensive balanced the<00:40:13.300> reading<00:40:13.570> will<00:40:13.750> be<00:40:13.780> more<00:40:14.080> expensive 00:40:14.340 --> 00:40:14.350 align:start position:0% the reading will be more expensive 00:40:14.350 --> 00:40:16.170 align:start position:0% the reading will be more expensive anything<00:40:14.920> that<00:40:15.100> touches<00:40:15.250> the<00:40:15.550> state<00:40:15.790> will<00:40:16.030> be 00:40:16.170 --> 00:40:16.180 align:start position:0% anything that touches the state will be 00:40:16.180 --> 00:40:18.480 align:start position:0% anything that touches the state will be more<00:40:16.390> expensive<00:40:16.750> to<00:40:17.440> pay<00:40:17.680> for<00:40:17.950> the<00:40:18.010> witnesses 00:40:18.480 --> 00:40:18.490 align:start position:0% more expensive to pay for the witnesses 00:40:18.490 --> 00:40:21.110 align:start position:0% more expensive to pay for the witnesses transaction<00:40:19.450> format<00:40:19.930> will<00:40:20.110> not<00:40:20.260> change 00:40:21.110 --> 00:40:21.120 align:start position:0% transaction format will not change 00:40:21.120 --> 00:40:24.270 align:start position:0% transaction format will not change essentially<00:40:22.120> in<00:40:22.350> there<00:40:23.350> will<00:40:23.470> be<00:40:23.500> more<00:40:23.920> that 00:40:24.270 --> 00:40:24.280 align:start position:0% essentially in there will be more that 00:40:24.280 --> 00:40:26.250 align:start position:0% essentially in there will be more that data<00:40:24.550> shuffling<00:40:25.030> around<00:40:25.150> network<00:40:25.660> but<00:40:25.870> not<00:40:25.900> as 00:40:26.250 --> 00:40:26.260 align:start position:0% data shuffling around network but not as 00:40:26.260 --> 00:40:28.940 align:start position:0% data shuffling around network but not as transactions<00:40:26.920> as<00:40:27.100> the<00:40:27.370> as<00:40:27.610> the<00:40:27.880> basically 00:40:28.940 --> 00:40:28.950 align:start position:0% transactions as the as the basically 00:40:28.950 --> 00:40:31.740 align:start position:0% transactions as the as the basically part<00:40:29.950> of<00:40:30.010> witnesses<00:40:30.730> and<00:40:30.940> of<00:40:31.330> course<00:40:31.570> the 00:40:31.740 --> 00:40:31.750 align:start position:0% part of witnesses and of course the 00:40:31.750 --> 00:40:34.650 align:start position:0% part of witnesses and of course the witnesses<00:40:32.260> we<00:40:32.410> will<00:40:32.790> chop<00:40:33.790> them<00:40:33.970> up<00:40:34.120> in<00:40:34.330> part 00:40:34.650 --> 00:40:34.660 align:start position:0% witnesses we will chop them up in part 00:40:34.660 --> 00:40:37.840 align:start position:0% witnesses we will chop them up in part so<00:40:35.080> you<00:40:35.140> don't<00:40:35.380> have<00:40:35.560> to<00:40:35.770> like<00:40:36.370> to<00:40:36.880> ensure<00:40:37.180> the 00:40:37.840 --> 00:40:37.850 align:start position:0% so you don't have to like to ensure the 00:40:37.850 --> 00:40:40.870 align:start position:0% so you don't have to like to ensure the the<00:40:37.940> better<00:40:38.150> propagation<00:40:38.930> so<00:40:39.320> that<00:40:39.560> is<00:40:39.680> also<00:40:39.890> a 00:40:40.870 --> 00:40:40.880 align:start position:0% the better propagation so that is also a 00:40:40.880 --> 00:40:44.350 align:start position:0% the better propagation so that is also a kind<00:40:41.540> of<00:40:41.720> pretty<00:40:42.080> solvable<00:40:42.500> problem<00:40:43.210> but<00:40:44.210> yeah 00:40:44.350 --> 00:40:44.360 align:start position:0% kind of pretty solvable problem but yeah 00:40:44.360 --> 00:40:46.180 align:start position:0% kind of pretty solvable problem but yeah it's<00:40:44.510> not<00:40:45.010> okay 00:40:46.180 --> 00:40:46.190 align:start position:0% it's not okay 00:40:46.190 --> 00:40:48.880 align:start position:0% it's not okay also<00:40:47.030> in<00:40:47.210> that<00:40:47.270> case<00:40:47.570> that<00:40:47.780> that's<00:40:48.260> like<00:40:48.440> it's 00:40:48.880 --> 00:40:48.890 align:start position:0% also in that case that that's like it's 00:40:48.890 --> 00:40:51.490 align:start position:0% also in that case that that's like it's like<00:40:49.700> halfway<00:40:49.940> solution<00:40:50.600> basically<00:40:50.930> like<00:40:51.320> you 00:40:51.490 --> 00:40:51.500 align:start position:0% like halfway solution basically like you 00:40:51.500 --> 00:40:53.380 align:start position:0% like halfway solution basically like you do<00:40:51.680> still<00:40:51.980> want<00:40:52.130> to<00:40:52.250> have<00:40:52.490> state<00:40:52.790> it's<00:40:53.300> not 00:40:53.380 --> 00:40:53.390 align:start position:0% do still want to have state it's not 00:40:53.390 --> 00:40:55.720 align:start position:0% do still want to have state it's not like<00:40:53.720> status<00:40:54.470> and<00:40:54.800> you<00:40:54.920> know<00:40:55.040> like<00:40:55.250> a<00:40:55.400> theorem 00:40:55.720 --> 00:40:55.730 align:start position:0% like status and you know like a theorem 00:40:55.730 --> 00:40:57.190 align:start position:0% like status and you know like a theorem itself<00:40:55.970> doesn't<00:40:56.210> have<00:40:56.420> any<00:40:56.600> state<00:40:56.810> it's<00:40:56.990> more 00:40:57.190 --> 00:40:57.200 align:start position:0% itself doesn't have any state it's more 00:40:57.200 --> 00:40:59.470 align:start position:0% itself doesn't have any state it's more about<00:40:57.410> so<00:40:58.040> I<00:40:58.070> would<00:40:58.340> say<00:40:58.550> this<00:40:58.700> is<00:40:58.910> the<00:40:59.120> the 00:40:59.470 --> 00:40:59.480 align:start position:0% about so I would say this is the the 00:40:59.480 --> 00:41:01.030 align:start position:0% about so I would say this is the the stateless<00:40:59.840> client<00:41:00.200> is<00:41:00.290> basically<00:41:00.620> approach 00:41:01.030 --> 00:41:01.040 align:start position:0% stateless client is basically approach 00:41:01.040 --> 00:41:04.780 align:start position:0% stateless client is basically approach of<00:41:01.280> of<00:41:02.230> instead<00:41:03.230> of<00:41:03.350> asking<00:41:03.830> every<00:41:04.190> all<00:41:04.730> the 00:41:04.780 --> 00:41:04.790 align:start position:0% of of instead of asking every all the 00:41:04.790 --> 00:41:07.180 align:start position:0% of of instead of asking every all the app<00:41:05.210> developers<00:41:05.750> to<00:41:05.900> follow<00:41:06.140> design<00:41:06.590> certain 00:41:07.180 --> 00:41:07.190 align:start position:0% app developers to follow design certain 00:41:07.190 --> 00:41:09.220 align:start position:0% app developers to follow design certain design<00:41:07.460> pattern<00:41:07.880> you<00:41:08.450> just<00:41:08.660> basically<00:41:08.780> solve 00:41:09.220 --> 00:41:09.230 align:start position:0% design pattern you just basically solve 00:41:09.230 --> 00:41:13.120 align:start position:0% design pattern you just basically solve it<00:41:09.380> for<00:41:09.560> them<00:41:09.770> in<00:41:09.980> a<00:41:10.480> generic<00:41:11.480> way<00:41:11.740> so<00:41:12.740> if<00:41:13.070> you 00:41:13.120 --> 00:41:13.130 align:start position:0% it for them in a generic way so if you 00:41:13.130 --> 00:41:15.520 align:start position:0% it for them in a generic way so if you have<00:41:13.550> a<00:41:13.580> status<00:41:14.270> client<00:41:14.630> instead<00:41:15.110> of<00:41:15.260> telling 00:41:15.520 --> 00:41:15.530 align:start position:0% have a status client instead of telling 00:41:15.530 --> 00:41:17.410 align:start position:0% have a status client instead of telling everybody<00:41:15.620> poom<00:41:16.160> to<00:41:16.520> put<00:41:16.700> merkel<00:41:17.090> root<00:41:17.210> in<00:41:17.330> the 00:41:17.410 --> 00:41:17.420 align:start position:0% everybody poom to put merkel root in the 00:41:17.420 --> 00:41:19.480 align:start position:0% everybody poom to put merkel root in the contract<00:41:17.870> you<00:41:18.050> just<00:41:18.470> tell<00:41:18.650> them<00:41:18.830> just<00:41:18.980> do 00:41:19.480 --> 00:41:19.490 align:start position:0% contract you just tell them just do 00:41:19.490 --> 00:41:21.460 align:start position:0% contract you just tell them just do whatever<00:41:19.670> you<00:41:19.880> did<00:41:20.150> before<00:41:20.330> and<00:41:20.750> we're<00:41:21.380> just 00:41:21.460 --> 00:41:21.470 align:start position:0% whatever you did before and we're just 00:41:21.470 --> 00:41:22.900 align:start position:0% whatever you did before and we're just gonna<00:41:21.620> take<00:41:22.040> care<00:41:22.250> of<00:41:22.400> that<00:41:22.520> you're<00:41:22.730> just 00:41:22.900 --> 00:41:22.910 align:start position:0% gonna take care of that you're just 00:41:22.910 --> 00:41:24.820 align:start position:0% gonna take care of that you're just gonna<00:41:23.000> pay<00:41:23.240> for<00:41:23.300> it<00:41:23.570> a<00:41:23.630> bit<00:41:23.780> more<00:41:23.990> but<00:41:24.560> the 00:41:24.820 --> 00:41:24.830 align:start position:0% gonna pay for it a bit more but the 00:41:24.830 --> 00:41:26.440 align:start position:0% gonna pay for it a bit more but the whole<00:41:25.040> technicalities<00:41:25.820> will<00:41:25.970> be<00:41:26.090> taken<00:41:26.420> care 00:41:26.440 --> 00:41:26.450 align:start position:0% whole technicalities will be taken care 00:41:26.450 --> 00:41:26.770 align:start position:0% whole technicalities will be taken care of 00:41:26.770 --> 00:41:26.780 align:start position:0% of 00:41:26.780 --> 00:41:29.560 align:start position:0% of so<00:41:27.470> we<00:41:27.920> have<00:41:28.130> we<00:41:28.310> have<00:41:28.340> the<00:41:28.670> working<00:41:29.450> group 00:41:29.560 --> 00:41:29.570 align:start position:0% so we have we have the working group 00:41:29.570 --> 00:41:30.850 align:start position:0% so we have we have the working group session<00:41:29.960> scheduled<00:41:30.440> for<00:41:30.650> later<00:41:30.770> this 00:41:30.850 --> 00:41:30.860 align:start position:0% session scheduled for later this 00:41:30.860 --> 00:41:33.310 align:start position:0% session scheduled for later this afternoon<00:41:31.070> and<00:41:31.640> about<00:41:31.850> like<00:41:32.120> 15<00:41:32.870> minutes<00:41:33.170> left 00:41:33.310 --> 00:41:33.320 align:start position:0% afternoon and about like 15 minutes left 00:41:33.320 --> 00:41:35.470 align:start position:0% afternoon and about like 15 minutes left for<00:41:33.530> this<00:41:33.710> session<00:41:33.920> so<00:41:34.910> maybe<00:41:35.180> it<00:41:35.300> makes<00:41:35.420> sense 00:41:35.470 --> 00:41:35.480 align:start position:0% for this session so maybe it makes sense 00:41:35.480 --> 00:41:37.480 align:start position:0% for this session so maybe it makes sense to<00:41:35.720> just<00:41:35.960> like<00:41:36.080> have<00:41:36.230> a<00:41:36.260> stateless<00:41:36.710> client 00:41:37.480 --> 00:41:37.490 align:start position:0% to just like have a stateless client 00:41:37.490 --> 00:41:39.490 align:start position:0% to just like have a stateless client discussion<00:41:38.480> this<00:41:38.750> afternoon<00:41:38.900> because<00:41:39.410> I<00:41:39.440> know 00:41:39.490 --> 00:41:39.500 align:start position:0% discussion this afternoon because I know 00:41:39.500 --> 00:41:40.330 align:start position:0% discussion this afternoon because I know there's<00:41:39.710> a<00:41:39.740> whole<00:41:39.860> bunch<00:41:40.040> of<00:41:40.100> new<00:41:40.220> people 00:41:40.330 --> 00:41:40.340 align:start position:0% there's a whole bunch of new people 00:41:40.340 --> 00:41:43.540 align:start position:0% there's a whole bunch of new people sitting<00:41:40.790> there<00:41:40.850> what<00:41:41.270> time<00:41:41.510> is<00:41:41.660> it<00:41:42.160> 3:30<00:41:43.160> to 00:41:43.540 --> 00:41:43.550 align:start position:0% sitting there what time is it 3:30 to 00:41:43.550 --> 00:41:45.160 align:start position:0% sitting there what time is it 3:30 to the<00:41:43.670> end<00:41:43.820> of<00:41:44.000> the<00:41:44.570> day<00:41:44.720> I<00:41:44.750> don't<00:41:44.960> know<00:41:45.020> what 00:41:45.160 --> 00:41:45.170 align:start position:0% the end of the day I don't know what 00:41:45.170 --> 00:41:47.800 align:start position:0% the end of the day I don't know what that<00:41:45.290> is<00:41:45.530> they<00:41:45.980> have<00:41:46.190> this<00:41:46.340> room<00:41:46.520> here<00:41:46.790> to<00:41:47.330> just 00:41:47.800 --> 00:41:47.810 align:start position:0% that is they have this room here to just 00:41:47.810 --> 00:41:50.650 align:start position:0% that is they have this room here to just discuss<00:41:48.140> working<00:41:48.470> groups<00:41:49.060> jason<00:41:50.060> carver<00:41:50.390> also 00:41:50.650 --> 00:41:50.660 align:start position:0% discuss working groups jason carver also 00:41:50.660 --> 00:41:54.540 align:start position:0% discuss working groups jason carver also join<00:41:50.900> give<00:41:51.560> a<00:41:51.590> quick<00:41:51.800> intro<00:41:52.130> with<00:41:52.280> Felix's<00:41:52.700> mic 00:41:54.540 --> 00:41:54.550 align:start position:0% join give a quick intro with Felix's mic 00:41:54.550 --> 00:41:58.210 align:start position:0% join give a quick intro with Felix's mic hi<00:41:55.660> Jason<00:41:56.660> Carver<00:41:57.170> working<00:41:57.530> on<00:41:57.590> the<00:41:57.770> Trinity 00:41:58.210 --> 00:41:58.220 align:start position:0% hi Jason Carver working on the Trinity 00:41:58.220 --> 00:42:00.820 align:start position:0% hi Jason Carver working on the Trinity clients<00:41:59.150> that's<00:41:59.390> an<00:41:59.690> all<00:41:59.990> Python<00:42:00.380> client<00:42:00.560> I 00:42:00.820 --> 00:42:00.830 align:start position:0% clients that's an all Python client I 00:42:00.830 --> 00:42:02.290 align:start position:0% clients that's an all Python client I came<00:42:01.280> here<00:42:01.370> to<00:42:01.550> talk<00:42:01.730> about<00:42:01.790> stateless 00:42:02.290 --> 00:42:02.300 align:start position:0% came here to talk about stateless 00:42:02.300 --> 00:42:03.610 align:start position:0% came here to talk about stateless clients<00:42:02.600> so<00:42:02.690> I<00:42:02.720> guess<00:42:02.930> I'll<00:42:03.110> save<00:42:03.440> that<00:42:03.470> for 00:42:03.610 --> 00:42:03.620 align:start position:0% clients so I guess I'll save that for 00:42:03.620 --> 00:42:05.620 align:start position:0% clients so I guess I'll save that for him<00:42:03.890> I<00:42:04.070> mean<00:42:05.030> we<00:42:05.150> keep<00:42:05.330> talking<00:42:05.450> about 00:42:05.620 --> 00:42:05.630 align:start position:0% him I mean we keep talking about 00:42:05.630 --> 00:42:08.770 align:start position:0% him I mean we keep talking about stateless<00:42:06.110> clients<00:42:06.530> but<00:42:06.880> yeah<00:42:07.880> yeah<00:42:08.480> does 00:42:08.770 --> 00:42:08.780 align:start position:0% stateless clients but yeah yeah does 00:42:08.780 --> 00:42:17.700 align:start position:0% stateless clients but yeah yeah does anyone<00:42:09.020> have<00:42:09.200> anything<00:42:09.410> else<00:42:09.680> they<00:42:10.370> owe 00:42:17.700 --> 00:42:17.710 align:start position:0% 00:42:17.710 --> 00:42:21.609 align:start position:0% hello<00:42:18.710> hello<00:42:18.920> could<00:42:19.520> you<00:42:19.700> talk<00:42:19.910> about<00:42:19.940> VIP<00:42:20.839> one 00:42:21.609 --> 00:42:21.619 align:start position:0% hello hello could you talk about VIP one 00:42:21.619 --> 00:42:23.940 align:start position:0% hello hello could you talk about VIP one five<00:42:21.890> five<00:42:22.099> nine<00:42:22.160> which<00:42:22.640> is<00:42:22.670> the<00:42:23.150> idea<00:42:23.480> of 00:42:23.940 --> 00:42:23.950 align:start position:0% five five nine which is the idea of 00:42:23.950 --> 00:42:27.460 align:start position:0% five five nine which is the idea of having<00:42:24.950> the<00:42:25.250> gas<00:42:26.180> priced<00:42:26.569> at<00:42:26.930> the<00:42:26.990> protocol 00:42:27.460 --> 00:42:27.470 align:start position:0% having the gas priced at the protocol 00:42:27.470 --> 00:42:28.990 align:start position:0% having the gas priced at the protocol level<00:42:27.500> and<00:42:27.950> it's<00:42:28.069> burned<00:42:28.339> instead<00:42:28.640> of<00:42:28.789> given 00:42:28.990 --> 00:42:29.000 align:start position:0% level and it's burned instead of given 00:42:29.000 --> 00:42:30.640 align:start position:0% level and it's burned instead of given two<00:42:29.059> -<00:42:29.359> yeah<00:42:29.960> sure 00:42:30.640 --> 00:42:30.650 align:start position:0% two - yeah sure 00:42:30.650 --> 00:42:33.579 align:start position:0% two - yeah sure so<00:42:31.039> the<00:42:32.000> basic<00:42:32.420> kind<00:42:32.690> of<00:42:32.779> description<00:42:33.380> of<00:42:33.500> the 00:42:33.579 --> 00:42:33.589 align:start position:0% so the basic kind of description of the 00:42:33.589 --> 00:42:38.890 align:start position:0% so the basic kind of description of the proposal<00:42:34.279> rate<00:42:34.670> is<00:42:35.029> that<00:42:35.599> we<00:42:36.940> basically<00:42:37.940> add<00:42:38.359> a 00:42:38.890 --> 00:42:38.900 align:start position:0% proposal rate is that we basically add a 00:42:38.900 --> 00:42:41.170 align:start position:0% proposal rate is that we basically add a kind<00:42:39.529> of<00:42:39.619> negative<00:42:39.920> components<00:42:40.819> to<00:42:40.910> the<00:42:41.000> block 00:42:41.170 --> 00:42:41.180 align:start position:0% kind of negative components to the block 00:42:41.180 --> 00:42:43.720 align:start position:0% kind of negative components to the block reward<00:42:41.359> so<00:42:41.809> that<00:42:41.990> basically<00:42:42.140> says<00:42:42.740> that<00:42:43.010> we 00:42:43.720 --> 00:42:43.730 align:start position:0% reward so that basically says that we 00:42:43.730 --> 00:42:46.240 align:start position:0% reward so that basically says that we have<00:42:43.880> some<00:42:44.210> in<00:42:44.390> protocol<00:42:44.869> fear<00:42:45.170> and<00:42:45.680> incident 00:42:46.240 --> 00:42:46.250 align:start position:0% have some in protocol fear and incident 00:42:46.250 --> 00:42:48.309 align:start position:0% have some in protocol fear and incident you<00:42:46.670> within<00:42:47.180> the<00:42:47.299> context<00:42:47.779> of<00:42:47.869> any<00:42:47.960> particular 00:42:48.309 --> 00:42:48.319 align:start position:0% you within the context of any particular 00:42:48.319 --> 00:42:50.109 align:start position:0% you within the context of any particular block<00:42:48.770> you<00:42:48.950> can<00:42:49.099> think<00:42:49.279> of<00:42:49.339> it<00:42:49.460> as<00:42:49.549> a<00:42:49.609> constant 00:42:50.109 --> 00:42:50.119 align:start position:0% block you can think of it as a constant 00:42:50.119 --> 00:42:51.490 align:start position:0% block you can think of it as a constant but<00:42:50.270> the<00:42:50.329> constant<00:42:50.720> adjusts<00:42:51.109> up<00:42:51.200> and<00:42:51.380> down 00:42:51.490 --> 00:42:51.500 align:start position:0% but the constant adjusts up and down 00:42:51.500 --> 00:42:54.789 align:start position:0% but the constant adjusts up and down over<00:42:51.680> time<00:42:52.010> and<00:42:52.819> it's<00:42:53.329> basically<00:42:53.809> the<00:42:54.529> minor 00:42:54.789 --> 00:42:54.799 align:start position:0% over time and it's basically the minor 00:42:54.799 --> 00:42:57.549 align:start position:0% over time and it's basically the minor of<00:42:54.950> a<00:42:55.160> block<00:42:55.430> has<00:42:55.849> to<00:42:55.880> pay<00:42:56.270> some<00:42:56.599> amounts<00:42:57.079> or 00:42:57.549 --> 00:42:57.559 align:start position:0% of a block has to pay some amounts or 00:42:57.559 --> 00:42:58.990 align:start position:0% of a block has to pay some amounts or alternatively<00:42:58.190> the<00:42:58.400> block<00:42:58.579> reward<00:42:58.880> is 00:42:58.990 --> 00:42:59.000 align:start position:0% alternatively the block reward is 00:42:59.000 --> 00:43:01.359 align:start position:0% alternatively the block reward is reduced<00:42:59.299> by<00:42:59.450> that<00:42:59.630> amount<00:42:59.690> which<00:43:00.260> is<00:43:00.289> equal<00:43:01.160> to 00:43:01.359 --> 00:43:01.369 align:start position:0% reduced by that amount which is equal to 00:43:01.369 --> 00:43:03.819 align:start position:0% reduced by that amount which is equal to that<00:43:01.579> fee<00:43:01.880> multiplied<00:43:02.510> by<00:43:02.779> the<00:43:03.500> number<00:43:03.650> of 00:43:03.819 --> 00:43:03.829 align:start position:0% that fee multiplied by the number of 00:43:03.829 --> 00:43:07.690 align:start position:0% that fee multiplied by the number of gwei<00:43:04.220> of<00:43:04.400> gas<00:43:04.609> used<00:43:04.910> and<00:43:05.799> this<00:43:06.799> obviously<00:43:07.130> if 00:43:07.690 --> 00:43:07.700 align:start position:0% gwei of gas used and this obviously if 00:43:07.700 --> 00:43:09.609 align:start position:0% gwei of gas used and this obviously if this<00:43:08.000> kind<00:43:08.240> of<00:43:08.390> like<00:43:08.480> whatever<00:43:09.170> this<00:43:09.349> burn 00:43:09.609 --> 00:43:09.619 align:start position:0% this kind of like whatever this burn 00:43:09.619 --> 00:43:11.559 align:start position:0% this kind of like whatever this burn feels<00:43:10.069> like<00:43:10.369> it'll<00:43:10.549> push<00:43:10.849> up<00:43:11.089> the<00:43:11.299> minimum 00:43:11.559 --> 00:43:11.569 align:start position:0% feels like it'll push up the minimum 00:43:11.569 --> 00:43:13.630 align:start position:0% feels like it'll push up the minimum wave<00:43:11.990> or<00:43:12.380> the<00:43:12.410> minimum<00:43:12.829> gas<00:43:13.069> price<00:43:13.369> that<00:43:13.549> the 00:43:13.630 --> 00:43:13.640 align:start position:0% wave or the minimum gas price that the 00:43:13.640 --> 00:43:15.339 align:start position:0% wave or the minimum gas price that the miner<00:43:13.819> is<00:43:14.029> willing<00:43:14.270> to<00:43:14.299> accept<00:43:14.510> by<00:43:14.990> roughly 00:43:15.339 --> 00:43:15.349 align:start position:0% miner is willing to accept by roughly 00:43:15.349 --> 00:43:17.620 align:start position:0% miner is willing to accept by roughly the<00:43:15.440> same<00:43:15.589> amount<00:43:15.650> right<00:43:16.490> so<00:43:17.089> like<00:43:17.210> if<00:43:17.329> the<00:43:17.480> fee 00:43:17.620 --> 00:43:17.630 align:start position:0% the same amount right so like if the fee 00:43:17.630 --> 00:43:19.329 align:start position:0% the same amount right so like if the fee goes<00:43:17.779> up<00:43:18.020> to<00:43:18.140> ten<00:43:18.349> quid<00:43:18.589> then<00:43:18.770> the<00:43:18.859> miners<00:43:19.130> not 00:43:19.329 --> 00:43:19.339 align:start position:0% goes up to ten quid then the miners not 00:43:19.339 --> 00:43:21.130 align:start position:0% goes up to ten quid then the miners not gonna<00:43:19.460> accept<00:43:19.849> transactions<00:43:20.599> that<00:43:20.779> are<00:43:20.839> less 00:43:21.130 --> 00:43:21.140 align:start position:0% gonna accept transactions that are less 00:43:21.140 --> 00:43:22.420 align:start position:0% gonna accept transactions that are less than<00:43:21.319> 10<00:43:21.500> way<00:43:21.650> because<00:43:21.950> they're<00:43:22.069> not<00:43:22.190> even 00:43:22.420 --> 00:43:22.430 align:start position:0% than 10 way because they're not even 00:43:22.430 --> 00:43:25.000 align:start position:0% than 10 way because they're not even going<00:43:22.520> to<00:43:22.579> be<00:43:22.700> not<00:43:23.359> profitable<00:43:23.869> anymore<00:43:24.049> and 00:43:25.000 --> 00:43:25.010 align:start position:0% going to be not profitable anymore and 00:43:25.010 --> 00:43:27.579 align:start position:0% going to be not profitable anymore and the<00:43:25.819> idea<00:43:26.180> would<00:43:26.420> be<00:43:26.480> that<00:43:26.630> we<00:43:27.079> would<00:43:27.319> say 00:43:27.579 --> 00:43:27.589 align:start position:0% the idea would be that we would say 00:43:27.589 --> 00:43:30.099 align:start position:0% the idea would be that we would say increase<00:43:28.430> the<00:43:28.640> gas<00:43:28.819> limit<00:43:29.150> limit<00:43:29.690> of<00:43:29.779> a<00:43:29.839> block 00:43:30.099 --> 00:43:30.109 align:start position:0% increase the gas limit limit of a block 00:43:30.109 --> 00:43:32.049 align:start position:0% increase the gas limit limit of a block from<00:43:30.289> say<00:43:30.529> 10<00:43:30.770> million<00:43:31.160> to<00:43:31.369> maybe<00:43:31.520> 20<00:43:31.880> million 00:43:32.049 --> 00:43:32.059 align:start position:0% from say 10 million to maybe 20 million 00:43:32.059 --> 00:43:35.079 align:start position:0% from say 10 million to maybe 20 million or<00:43:32.329> more<00:43:32.480> but<00:43:33.020> then<00:43:33.349> we<00:43:33.980> would<00:43:34.190> have<00:43:34.220> this<00:43:34.700> fee 00:43:35.079 --> 00:43:35.089 align:start position:0% or more but then we would have this fee 00:43:35.089 --> 00:43:36.910 align:start position:0% or more but then we would have this fee be<00:43:35.390> adjusted<00:43:35.960> according<00:43:36.349> to<00:43:36.380> an<00:43:36.589> automatic 00:43:36.910 --> 00:43:36.920 align:start position:0% be adjusted according to an automatic 00:43:36.920 --> 00:43:41.039 align:start position:0% be adjusted according to an automatic algorithm<00:43:37.700> that<00:43:37.849> basically<00:43:38.020> in<00:43:39.020> targets<00:43:39.680> the 00:43:41.039 --> 00:43:41.049 align:start position:0% algorithm that basically in targets the 00:43:41.049 --> 00:43:44.260 align:start position:0% algorithm that basically in targets the use<00:43:42.049> average<00:43:42.289> usage<00:43:43.010> of<00:43:43.220> gas<00:43:43.549> and<00:43:43.789> a<00:43:43.819> block<00:43:44.059> to 00:43:44.260 --> 00:43:44.270 align:start position:0% use average usage of gas and a block to 00:43:44.270 --> 00:43:46.720 align:start position:0% use average usage of gas and a block to be<00:43:44.390> to<00:43:44.809> be<00:43:44.960> at<00:43:45.079> the<00:43:45.230> ten<00:43:45.410> million<00:43:45.589> level<00:43:46.039> so<00:43:46.520> if 00:43:46.720 --> 00:43:46.730 align:start position:0% be to be at the ten million level so if 00:43:46.730 --> 00:43:48.490 align:start position:0% be to be at the ten million level so if a<00:43:46.880> block<00:43:47.119> sometimes<00:43:47.510> blocks<00:43:48.109> will<00:43:48.230> be<00:43:48.319> bigger 00:43:48.490 --> 00:43:48.500 align:start position:0% a block sometimes blocks will be bigger 00:43:48.500 --> 00:43:49.740 align:start position:0% a block sometimes blocks will be bigger sometimes<00:43:48.980> walk<00:43:49.160> is<00:43:49.309> always<00:43:49.460> smaller 00:43:49.740 --> 00:43:49.750 align:start position:0% sometimes walk is always smaller 00:43:49.750 --> 00:43:51.760 align:start position:0% sometimes walk is always smaller whenever<00:43:50.750> blocks<00:43:51.049> are<00:43:51.230> bigger<00:43:51.410> the<00:43:51.619> fee<00:43:51.740> goes 00:43:51.760 --> 00:43:51.770 align:start position:0% whenever blocks are bigger the fee goes 00:43:51.770 --> 00:43:53.349 align:start position:0% whenever blocks are bigger the fee goes up<00:43:52.099> whenever<00:43:52.309> blocks<00:43:52.670> were<00:43:52.789> smaller<00:43:53.029> the<00:43:53.240> fee 00:43:53.349 --> 00:43:53.359 align:start position:0% up whenever blocks were smaller the fee 00:43:53.359 --> 00:43:55.690 align:start position:0% up whenever blocks were smaller the fee goes<00:43:53.510> down<00:43:53.779> and<00:43:54.079> so<00:43:54.200> at<00:43:54.470> equilibrium<00:43:54.700> like 00:43:55.690 --> 00:43:55.700 align:start position:0% goes down and so at equilibrium like 00:43:55.700 --> 00:43:59.200 align:start position:0% goes down and so at equilibrium like there's<00:43:55.970> some<00:43:56.299> kind<00:43:56.660> of<00:43:56.829> mandatory<00:43:57.829> fee<00:43:58.309> that 00:43:59.200 --> 00:43:59.210 align:start position:0% there's some kind of mandatory fee that 00:43:59.210 --> 00:44:01.480 align:start position:0% there's some kind of mandatory fee that gets<00:43:59.480> that<00:44:00.020> kind<00:44:00.230> of<00:44:00.349> gets<00:44:00.559> burns<00:44:00.980> and<00:44:01.160> miners 00:44:01.480 --> 00:44:01.490 align:start position:0% gets that kind of gets burns and miners 00:44:01.490 --> 00:44:05.339 align:start position:0% gets that kind of gets burns and miners are<00:44:01.730> going<00:44:02.029> to<00:44:02.180> accept<00:44:02.480> below<00:44:02.839> it<00:44:03.049> but<00:44:03.680> the<00:44:04.579> end 00:44:05.339 --> 00:44:05.349 align:start position:0% are going to accept below it but the end 00:44:05.349 --> 00:44:08.049 align:start position:0% are going to accept below it but the end like<00:44:06.349> blocks<00:44:06.710> are<00:44:06.950> an<00:44:07.069> on<00:44:07.250> average<00:44:07.609> gonna<00:44:07.849> be<00:44:08.029> a 00:44:08.049 --> 00:44:08.059 align:start position:0% like blocks are an on average gonna be a 00:44:08.059 --> 00:44:10.359 align:start position:0% like blocks are an on average gonna be a half<00:44:08.839> full<00:44:09.140> or<00:44:09.170> one-third<00:44:09.650> fo<00:44:09.890> instead<00:44:10.279> of 00:44:10.359 --> 00:44:10.369 align:start position:0% half full or one-third fo instead of 00:44:10.369 --> 00:44:13.240 align:start position:0% half full or one-third fo instead of being<00:44:10.579> completely<00:44:10.940> fall<00:44:11.210> the<00:44:11.869> reason<00:44:12.440> why<00:44:12.890> we 00:44:13.240 --> 00:44:13.250 align:start position:0% being completely fall the reason why we 00:44:13.250 --> 00:44:15.010 align:start position:0% being completely fall the reason why we wants<00:44:13.579> to<00:44:13.700> do<00:44:13.880> this<00:44:14.059> and<00:44:14.450> there's<00:44:14.630> actually<00:44:14.990> a 00:44:15.010 --> 00:44:15.020 align:start position:0% wants to do this and there's actually a 00:44:15.020 --> 00:44:17.529 align:start position:0% wants to do this and there's actually a few<00:44:15.200> different<00:44:15.380> reasons<00:44:15.789> one<00:44:16.789> of<00:44:16.970> them<00:44:17.210> is 00:44:17.529 --> 00:44:17.539 align:start position:0% few different reasons one of them is 00:44:17.539 --> 00:44:20.920 align:start position:0% few different reasons one of them is that<00:44:18.730> but<00:44:19.730> the<00:44:19.819> most<00:44:19.940> fundamental<00:44:20.210> one<00:44:20.690> is 00:44:20.920 --> 00:44:20.930 align:start position:0% that but the most fundamental one is 00:44:20.930 --> 00:44:23.230 align:start position:0% that but the most fundamental one is that<00:44:21.109> currently<00:44:21.559> fee<00:44:21.890> markets<00:44:22.339> work<00:44:22.670> really 00:44:23.230 --> 00:44:23.240 align:start position:0% that currently fee markets work really 00:44:23.240 --> 00:44:26.910 align:start position:0% that currently fee markets work really horribly<00:44:23.450> so<00:44:24.260> one<00:44:25.160> example<00:44:25.580> of<00:44:26.330> this<00:44:26.540> is<00:44:26.840> that 00:44:26.910 --> 00:44:26.920 align:start position:0% horribly so one example of this is that 00:44:26.920 --> 00:44:30.340 align:start position:0% horribly so one example of this is that like<00:44:27.920> on<00:44:28.160> average<00:44:28.610> people<00:44:28.910> tends<00:44:29.330> to<00:44:29.630> overpay 00:44:30.340 --> 00:44:30.350 align:start position:0% like on average people tends to overpay 00:44:30.350 --> 00:44:32.500 align:start position:0% like on average people tends to overpay by<00:44:30.619> a<00:44:30.650> factor<00:44:31.220> of<00:44:31.250> somewhere<00:44:31.790> between<00:44:31.850> three 00:44:32.500 --> 00:44:32.510 align:start position:0% by a factor of somewhere between three 00:44:32.510 --> 00:44:34.270 align:start position:0% by a factor of somewhere between three and<00:44:32.540> three<00:44:33.080> and<00:44:33.110> five<00:44:33.410> or<00:44:33.650> higher<00:44:33.800> than<00:44:34.040> five 00:44:34.270 --> 00:44:34.280 align:start position:0% and three and five or higher than five 00:44:34.280 --> 00:44:36.700 align:start position:0% and three and five or higher than five for<00:44:34.670> our<00:44:34.730> transactions<00:44:35.360> and<00:44:36.080> like<00:44:36.380> you<00:44:36.530> see 00:44:36.700 --> 00:44:36.710 align:start position:0% for our transactions and like you see 00:44:36.710 --> 00:44:38.410 align:start position:0% for our transactions and like you see people<00:44:36.860> talking<00:44:37.310> about<00:44:37.430> a<00:44:37.550> trade-off<00:44:37.970> of<00:44:38.030> like 00:44:38.410 --> 00:44:38.420 align:start position:0% people talking about a trade-off of like 00:44:38.420 --> 00:44:40.450 align:start position:0% people talking about a trade-off of like you<00:44:38.510> either<00:44:38.690> pay<00:44:38.990> five<00:44:39.230> times<00:44:39.500> more<00:44:39.800> and<00:44:40.130> you 00:44:40.450 --> 00:44:40.460 align:start position:0% you either pay five times more and you 00:44:40.460 --> 00:44:42.580 align:start position:0% you either pay five times more and you get<00:44:40.610> included<00:44:40.850> right<00:44:41.210> now<00:44:41.420> or<00:44:41.840> you<00:44:42.080> pay<00:44:42.320> like 00:44:42.580 --> 00:44:42.590 align:start position:0% get included right now or you pay like 00:44:42.590 --> 00:44:44.859 align:start position:0% get included right now or you pay like two<00:44:42.830> took<00:44:43.040> the<00:44:43.610> minimum<00:44:44.060> and<00:44:44.210> you<00:44:44.270> wait<00:44:44.570> maybe 00:44:44.859 --> 00:44:44.869 align:start position:0% two took the minimum and you wait maybe 00:44:44.869 --> 00:44:47.320 align:start position:0% two took the minimum and you wait maybe a<00:44:44.960> minute<00:44:45.170> and<00:44:45.350> maybe<00:44:45.560> ten<00:44:45.800> minutes<00:44:46.160> but<00:44:46.490> like 00:44:47.320 --> 00:44:47.330 align:start position:0% a minute and maybe ten minutes but like 00:44:47.330 --> 00:44:49.210 align:start position:0% a minute and maybe ten minutes but like in<00:44:47.540> reality<00:44:47.750> that<00:44:48.290> waiting<00:44:48.830> is<00:44:48.980> like 00:44:49.210 --> 00:44:49.220 align:start position:0% in reality that waiting is like 00:44:49.220 --> 00:44:50.920 align:start position:0% in reality that waiting is like completely<00:44:49.700> socially<00:44:49.880> unproductive<00:44:50.750> right 00:44:50.920 --> 00:44:50.930 align:start position:0% completely socially unproductive right 00:44:50.930 --> 00:44:52.540 align:start position:0% completely socially unproductive right because<00:44:51.200> it's<00:44:51.380> the<00:44:51.500> same<00:44:51.710> load<00:44:51.980> to<00:44:52.160> the<00:44:52.280> chain 00:44:52.540 --> 00:44:52.550 align:start position:0% because it's the same load to the chain 00:44:52.550 --> 00:44:54.190 align:start position:0% because it's the same load to the chain well<00:44:52.820> no<00:44:53.000> matter<00:44:53.180> if<00:44:53.420> it<00:44:53.510> happens<00:44:53.810> now<00:44:53.960> or<00:44:54.110> if 00:44:54.190 --> 00:44:54.200 align:start position:0% well no matter if it happens now or if 00:44:54.200 --> 00:44:56.560 align:start position:0% well no matter if it happens now or if it<00:44:54.290> happens<00:44:54.410> ten<00:44:54.740> minutes<00:44:55.040> from<00:44:55.130> now<00:44:55.220> and<00:44:55.700> and 00:44:56.560 --> 00:44:56.570 align:start position:0% it happens ten minutes from now and and 00:44:56.570 --> 00:44:59.410 align:start position:0% it happens ten minutes from now and and also<00:44:56.750> just<00:44:57.369> it<00:44:58.369> adds<00:44:58.580> a<00:44:58.790> lot<00:44:58.940> of<00:44:59.000> wallet 00:44:59.410 --> 00:44:59.420 align:start position:0% also just it adds a lot of wallet 00:44:59.420 --> 00:45:01.030 align:start position:0% also just it adds a lot of wallet complexity<00:45:00.110> that<00:45:00.290> people<00:45:00.590> have<00:45:00.740> to<00:45:00.890> like 00:45:01.030 --> 00:45:01.040 align:start position:0% complexity that people have to like 00:45:01.040 --> 00:45:02.530 align:start position:0% complexity that people have to like think<00:45:01.310> about<00:45:01.400> oh<00:45:01.670> is<00:45:01.820> this<00:45:01.970> gonna<00:45:02.119> be<00:45:02.270> a<00:45:02.300> solo 00:45:02.530 --> 00:45:02.540 align:start position:0% think about oh is this gonna be a solo 00:45:02.540 --> 00:45:03.880 align:start position:0% think about oh is this gonna be a solo transaction<00:45:03.110> is<00:45:03.230> this<00:45:03.320> gonna<00:45:03.470> be<00:45:03.560> a<00:45:03.650> fast 00:45:03.880 --> 00:45:03.890 align:start position:0% transaction is this gonna be a fast 00:45:03.890 --> 00:45:06.910 align:start position:0% transaction is this gonna be a fast transaction<00:45:04.580> so<00:45:05.350> EAP<00:45:06.350> one<00:45:06.500> five<00:45:06.710> five<00:45:06.890> nine 00:45:06.910 --> 00:45:06.920 align:start position:0% transaction so EAP one five five nine 00:45:06.920 --> 00:45:09.640 align:start position:0% transaction so EAP one five five nine fixes<00:45:07.580> it<00:45:07.730> by<00:45:07.880> making<00:45:08.090> the<00:45:08.840> calculations<00:45:09.560> you 00:45:09.640 --> 00:45:09.650 align:start position:0% fixes it by making the calculations you 00:45:09.650 --> 00:45:11.470 align:start position:0% fixes it by making the calculations you will<00:45:09.710> minor<00:45:09.980> much<00:45:10.310> some<00:45:10.550> much<00:45:10.880> simpler<00:45:11.300> the 00:45:11.470 --> 00:45:11.480 align:start position:0% will minor much some much simpler the 00:45:11.480 --> 00:45:14.080 align:start position:0% will minor much some much simpler the calculation<00:45:12.080> basically<00:45:12.290> as<00:45:12.800> if<00:45:13.460> there<00:45:13.910> is<00:45:14.060> a 00:45:14.080 --> 00:45:14.090 align:start position:0% calculation basically as if there is a 00:45:14.090 --> 00:45:16.510 align:start position:0% calculation basically as if there is a transaction<00:45:14.840> that<00:45:14.990> pays<00:45:15.530> the<00:45:15.830> burn<00:45:16.040> like 00:45:16.510 --> 00:45:16.520 align:start position:0% transaction that pays the burn like 00:45:16.520 --> 00:45:18.880 align:start position:0% transaction that pays the burn like whatever<00:45:16.910> the<00:45:17.090> burn<00:45:17.240> fee<00:45:17.510> is<00:45:17.690> plus<00:45:18.410> whatever 00:45:18.880 --> 00:45:18.890 align:start position:0% whatever the burn fee is plus whatever 00:45:18.890 --> 00:45:21.670 align:start position:0% whatever the burn fee is plus whatever amount<00:45:19.310> and<00:45:19.700> it<00:45:19.820> overcomes<00:45:20.390> the<00:45:21.050> extra<00:45:21.500> risk 00:45:21.670 --> 00:45:21.680 align:start position:0% amount and it overcomes the extra risk 00:45:21.680 --> 00:45:23.650 align:start position:0% amount and it overcomes the extra risk that<00:45:21.980> my<00:45:22.100> block<00:45:22.340> will<00:45:22.490> be<00:45:22.580> an<00:45:22.670> uncle<00:45:22.820> and<00:45:23.240> that 00:45:23.650 --> 00:45:23.660 align:start position:0% that my block will be an uncle and that 00:45:23.660 --> 00:45:25.450 align:start position:0% that my block will be an uncle and that value<00:45:24.020> has<00:45:24.140> been<00:45:24.290> estimated<00:45:24.440> to<00:45:24.920> be<00:45:25.040> about<00:45:25.130> one 00:45:25.450 --> 00:45:25.460 align:start position:0% value has been estimated to be about one 00:45:25.460 --> 00:45:28.660 align:start position:0% value has been estimated to be about one guei<00:45:25.730> that'll<00:45:26.300> accept<00:45:26.630> it<00:45:26.840> and<00:45:27.020> so<00:45:27.670> clients 00:45:28.660 --> 00:45:28.670 align:start position:0% guei that'll accept it and so clients 00:45:28.670 --> 00:45:31.420 align:start position:0% guei that'll accept it and so clients would<00:45:28.850> just<00:45:29.090> like<00:45:29.300> pay<00:45:29.540> like<00:45:30.350> calculate<00:45:31.190> the 00:45:31.420 --> 00:45:31.430 align:start position:0% would just like pay like calculate the 00:45:31.430 --> 00:45:32.740 align:start position:0% would just like pay like calculate the fee<00:45:31.580> that<00:45:31.700> they<00:45:31.820> pay<00:45:32.030> based<00:45:32.270> on<00:45:32.420> a<00:45:32.480> simple 00:45:32.740 --> 00:45:32.750 align:start position:0% fee that they pay based on a simple 00:45:32.750 --> 00:45:36.280 align:start position:0% fee that they pay based on a simple formula<00:45:33.109> and<00:45:33.670> it'll<00:45:34.720> reliably<00:45:35.720> get<00:45:35.990> into<00:45:36.200> the 00:45:36.280 --> 00:45:36.290 align:start position:0% formula and it'll reliably get into the 00:45:36.290 --> 00:45:38.770 align:start position:0% formula and it'll reliably get into the chain<00:45:36.560> and<00:45:36.890> so<00:45:37.369> users<00:45:37.850> will<00:45:38.090> be<00:45:38.119> able<00:45:38.330> to<00:45:38.600> get 00:45:38.770 --> 00:45:38.780 align:start position:0% chain and so users will be able to get 00:45:38.780 --> 00:45:40.359 align:start position:0% chain and so users will be able to get like<00:45:38.990> pretty<00:45:39.230> reliable<00:45:39.740> next<00:45:40.130> block 00:45:40.359 --> 00:45:40.369 align:start position:0% like pretty reliable next block 00:45:40.369 --> 00:45:42.010 align:start position:0% like pretty reliable next block inclusion<00:45:40.880> of<00:45:41.000> any<00:45:41.150> of<00:45:41.270> their<00:45:41.420> transactions 00:45:42.010 --> 00:45:42.020 align:start position:0% inclusion of any of their transactions 00:45:42.020 --> 00:45:44.260 align:start position:0% inclusion of any of their transactions even<00:45:42.619> if<00:45:42.950> there<00:45:43.100> are<00:45:43.250> odd<00:45:43.430> short-term<00:45:43.880> spikes 00:45:44.260 --> 00:45:44.270 align:start position:0% even if there are odd short-term spikes 00:45:44.270 --> 00:45:46.390 align:start position:0% even if there are odd short-term spikes and<00:45:44.510> there's<00:45:44.690> like<00:45:44.990> suddenly<00:45:45.410> two<00:45:45.980> times<00:45:46.220> more 00:45:46.390 --> 00:45:46.400 align:start position:0% and there's like suddenly two times more 00:45:46.400 --> 00:45:47.800 align:start position:0% and there's like suddenly two times more usage<00:45:46.760> in<00:45:46.850> this<00:45:46.940> minute<00:45:47.240> and<00:45:47.390> electrodes<00:45:47.750> I 00:45:47.800 --> 00:45:47.810 align:start position:0% usage in this minute and electrodes I 00:45:47.810 --> 00:45:49.599 align:start position:0% usage in this minute and electrodes I was<00:45:47.930> watching<00:45:48.230> usage<00:45:48.710> the<00:45:48.859> next<00:45:49.070> minute<00:45:49.400> so 00:45:49.599 --> 00:45:49.609 align:start position:0% was watching usage the next minute so 00:45:49.609 --> 00:45:53.290 align:start position:0% was watching usage the next minute so it's<00:45:50.140> intended<00:45:51.140> as<00:45:51.470> a<00:45:51.680> kind<00:45:51.920> of<00:45:52.040> fee<00:45:52.880> market 00:45:53.290 --> 00:45:53.300 align:start position:0% it's intended as a kind of fee market 00:45:53.300 --> 00:45:56.020 align:start position:0% it's intended as a kind of fee market simplification<00:45:54.290> and<00:45:54.590> a<00:45:55.340> user<00:45:55.760> experience 00:45:56.020 --> 00:45:56.030 align:start position:0% simplification and a user experience 00:45:56.030 --> 00:45:59.320 align:start position:0% simplification and a user experience increase<00:45:56.930> because<00:45:57.440> like<00:45:57.800> users<00:45:58.190> just<00:45:58.850> won't 00:45:59.320 --> 00:45:59.330 align:start position:0% increase because like users just won't 00:45:59.330 --> 00:46:02.410 align:start position:0% increase because like users just won't happen<00:45:59.570> won't<00:45:59.869> have<00:46:00.080> to<00:46:00.230> wait<00:46:00.410> anymore<00:46:01.420> what 00:46:02.410 --> 00:46:02.420 align:start position:0% happen won't have to wait anymore what 00:46:02.420 --> 00:46:05.800 align:start position:0% happen won't have to wait anymore what does<00:46:02.510> that<00:46:02.570> do<00:46:02.869> for<00:46:03.609> users<00:46:04.609> who<00:46:04.640> are<00:46:05.000> willing 00:46:05.800 --> 00:46:05.810 align:start position:0% does that do for users who are willing 00:46:05.810 --> 00:46:07.960 align:start position:0% does that do for users who are willing to<00:46:06.170> let<00:46:06.680> a<00:46:06.710> transaction<00:46:07.310> happen<00:46:07.550> sometime 00:46:07.960 --> 00:46:07.970 align:start position:0% to let a transaction happen sometime 00:46:07.970 --> 00:46:09.670 align:start position:0% to let a transaction happen sometime over<00:46:08.210> the<00:46:08.300> next<00:46:08.510> day<00:46:08.750> they're<00:46:09.410> very 00:46:09.670 --> 00:46:09.680 align:start position:0% over the next day they're very 00:46:09.680 --> 00:46:11.980 align:start position:0% over the next day they're very price-sensitive<00:46:09.890> saying<00:46:10.580> yeah<00:46:11.210> so<00:46:11.480> users 00:46:11.980 --> 00:46:11.990 align:start position:0% price-sensitive saying yeah so users 00:46:11.990 --> 00:46:15.310 align:start position:0% price-sensitive saying yeah so users will<00:46:12.020> be<00:46:12.650> able<00:46:13.369> to<00:46:13.820> still<00:46:14.300> like<00:46:14.600> basically<00:46:15.109> say 00:46:15.310 --> 00:46:15.320 align:start position:0% will be able to still like basically say 00:46:15.320 --> 00:46:17.440 align:start position:0% will be able to still like basically say I<00:46:15.590> want<00:46:16.190> to<00:46:16.280> pay<00:46:16.430> a<00:46:16.460> transaction<00:46:16.730> I'm<00:46:17.300> gonna 00:46:17.440 --> 00:46:17.450 align:start position:0% I want to pay a transaction I'm gonna 00:46:17.450 --> 00:46:19.890 align:start position:0% I want to pay a transaction I'm gonna pay<00:46:17.690> a<00:46:17.720> gas<00:46:18.080> price<00:46:18.470> which<00:46:18.740> is<00:46:18.920> lower<00:46:19.190> than<00:46:19.340> the 00:46:19.890 --> 00:46:19.900 align:start position:0% pay a gas price which is lower than the 00:46:19.900 --> 00:46:22.840 align:start position:0% pay a gas price which is lower than the let's<00:46:20.900> say<00:46:21.020> for<00:46:21.200> example<00:46:21.230> I<00:46:21.890> as<00:46:22.340> a<00:46:22.369> transaction 00:46:22.840 --> 00:46:22.850 align:start position:0% let's say for example I as a transaction 00:46:22.850 --> 00:46:25.270 align:start position:0% let's say for example I as a transaction sender<00:46:23.480> see<00:46:23.840> that<00:46:24.200> the<00:46:24.590> current<00:46:24.800> fee<00:46:25.070> that's 00:46:25.270 --> 00:46:25.280 align:start position:0% sender see that the current fee that's 00:46:25.280 --> 00:46:26.830 align:start position:0% sender see that the current fee that's being<00:46:25.550> burned<00:46:25.820> is<00:46:26.060> like<00:46:26.240> pushed<00:46:26.510> all<00:46:26.720> the<00:46:26.750> way 00:46:26.830 --> 00:46:26.840 align:start position:0% being burned is like pushed all the way 00:46:26.840 --> 00:46:29.620 align:start position:0% being burned is like pushed all the way up<00:46:27.080> to<00:46:27.230> 23<00:46:27.710> way<00:46:27.950> because<00:46:28.550> like<00:46:28.940> I<00:46:29.090> know<00:46:29.300> fair 00:46:29.620 --> 00:46:29.630 align:start position:0% up to 23 way because like I know fair 00:46:29.630 --> 00:46:31.530 align:start position:0% up to 23 way because like I know fair one<00:46:29.810> is<00:46:29.930> doing<00:46:30.080> stupid<00:46:30.380> stuff 00:46:31.530 --> 00:46:31.540 align:start position:0% one is doing stupid stuff 00:46:31.540 --> 00:46:34.620 align:start position:0% one is doing stupid stuff and<00:46:31.660> I<00:46:32.200> as<00:46:33.070> a<00:46:33.220> user<00:46:33.370> know<00:46:33.850> that<00:46:34.180> fair<00:46:34.390> ones 00:46:34.620 --> 00:46:34.630 align:start position:0% and I as a user know that fair ones 00:46:34.630 --> 00:46:36.450 align:start position:0% and I as a user know that fair ones doing<00:46:34.870> stupid<00:46:35.080> stuff<00:46:35.230> is<00:46:35.530> exceptional<00:46:36.160> and 00:46:36.450 --> 00:46:36.460 align:start position:0% doing stupid stuff is exceptional and 00:46:36.460 --> 00:46:38.400 align:start position:0% doing stupid stuff is exceptional and four<00:46:36.760> hours<00:46:37.030> from<00:46:37.210> now<00:46:37.390> chances<00:46:37.750> are<00:46:37.990> fair<00:46:38.230> one 00:46:38.400 --> 00:46:38.410 align:start position:0% four hours from now chances are fair one 00:46:38.410 --> 00:46:40.620 align:start position:0% four hours from now chances are fair one will<00:46:38.500> stop<00:46:38.740> doing<00:46:38.890> stupid<00:46:39.190> stuff<00:46:39.370> so<00:46:40.090> I<00:46:40.120> as<00:46:40.600> a 00:46:40.620 --> 00:46:40.630 align:start position:0% will stop doing stupid stuff so I as a 00:46:40.630 --> 00:46:43.290 align:start position:0% will stop doing stupid stuff so I as a user<00:46:40.840> totally<00:46:41.500> can<00:46:41.800> send<00:46:42.520> a<00:46:42.580> transaction<00:46:42.970> with 00:46:43.290 --> 00:46:43.300 align:start position:0% user totally can send a transaction with 00:46:43.300 --> 00:46:45.240 align:start position:0% user totally can send a transaction with a<00:46:43.330> gas<00:46:43.540> price<00:46:43.870> of<00:46:44.050> say<00:46:44.230> nine<00:46:44.500> gwei<00:46:44.800> instead<00:46:45.160> of 00:46:45.240 --> 00:46:45.250 align:start position:0% a gas price of say nine gwei instead of 00:46:45.250 --> 00:46:47.520 align:start position:0% a gas price of say nine gwei instead of twenty<00:46:45.490> three<00:46:45.760> and<00:46:46.120> whenever<00:46:46.870> fair<00:46:47.320> wind 00:46:47.520 --> 00:46:47.530 align:start position:0% twenty three and whenever fair wind 00:46:47.530 --> 00:46:49.080 align:start position:0% twenty three and whenever fair wind stops<00:46:47.770> doing<00:46:47.980> stupid<00:46:48.250> stuff<00:46:48.640> to<00:46:48.670> get<00:46:48.910> the 00:46:49.080 --> 00:46:49.090 align:start position:0% stops doing stupid stuff to get the 00:46:49.090 --> 00:46:50.850 align:start position:0% stops doing stupid stuff to get the burns<00:46:49.360> gas<00:46:49.630> price<00:46:49.870> we<00:46:50.050> collaborate<00:46:50.500> down<00:46:50.680> to 00:46:50.850 --> 00:46:50.860 align:start position:0% burns gas price we collaborate down to 00:46:50.860 --> 00:46:52.350 align:start position:0% burns gas price we collaborate down to below<00:46:51.040> nine<00:46:51.280> image<00:46:51.640> production<00:46:51.940> will<00:46:52.210> get 00:46:52.350 --> 00:46:52.360 align:start position:0% below nine image production will get 00:46:52.360 --> 00:46:54.930 align:start position:0% below nine image production will get included<00:46:52.780> so<00:46:53.290> that's<00:46:53.530> like<00:46:53.860> totally<00:46:54.580> fine<00:46:54.760> an 00:46:54.930 --> 00:46:54.940 align:start position:0% included so that's like totally fine an 00:46:54.940 --> 00:46:57.780 align:start position:0% included so that's like totally fine an intended<00:46:55.300> behavior<00:46:55.600> that<00:46:55.750> you<00:46:55.840> can<00:46:56.020> do<00:46:56.760> so<00:46:57.760> I 00:46:57.780 --> 00:46:57.790 align:start position:0% intended behavior that you can do so I 00:46:57.790 --> 00:47:00.150 align:start position:0% intended behavior that you can do so I want<00:46:58.030> to<00:46:58.060> comment<00:46:58.300> in<00:46:58.540> this<00:46:58.690> that<00:46:58.930> we<00:46:59.770> a<00:46:59.800> lot<00:47:00.100> of 00:47:00.150 --> 00:47:00.160 align:start position:0% want to comment in this that we a lot of 00:47:00.160 --> 00:47:02.670 align:start position:0% want to comment in this that we a lot of times<00:47:00.280> we're<00:47:00.760> thinking<00:47:01.060> about<00:47:01.180> like<00:47:01.960> the<00:47:02.380> one 00:47:02.670 --> 00:47:02.680 align:start position:0% times we're thinking about like the one 00:47:02.680 --> 00:47:05.340 align:start position:0% times we're thinking about like the one user<00:47:02.920> sending<00:47:03.490> one<00:47:03.640> transaction<00:47:04.170> which<00:47:05.170> is 00:47:05.340 --> 00:47:05.350 align:start position:0% user sending one transaction which is 00:47:05.350 --> 00:47:07.980 align:start position:0% user sending one transaction which is okay<00:47:05.680> you<00:47:05.740> know<00:47:06.070> you<00:47:06.130> can<00:47:06.490> wait<00:47:06.970> or<00:47:07.390> you<00:47:07.570> can<00:47:07.810> do 00:47:07.980 --> 00:47:07.990 align:start position:0% okay you know you can wait or you can do 00:47:07.990 --> 00:47:10.590 align:start position:0% okay you know you can wait or you can do it<00:47:08.050> within<00:47:08.380> like<00:47:08.830> you<00:47:09.100> pay<00:47:09.310> a<00:47:09.340> bit<00:47:09.490> more<00:47:09.600> but 00:47:10.590 --> 00:47:10.600 align:start position:0% it within like you pay a bit more but 00:47:10.600 --> 00:47:12.210 align:start position:0% it within like you pay a bit more but the<00:47:10.840> real<00:47:10.990> problem<00:47:11.410> is<00:47:11.560> that<00:47:11.590> for<00:47:11.890> the<00:47:12.040> people 00:47:12.210 --> 00:47:12.220 align:start position:0% the real problem is that for the people 00:47:12.220 --> 00:47:14.610 align:start position:0% the real problem is that for the people or<00:47:12.610> for<00:47:12.640> organization<00:47:13.540> who<00:47:13.750> actually<00:47:13.930> depend 00:47:14.610 --> 00:47:14.620 align:start position:0% or for organization who actually depend 00:47:14.620 --> 00:47:16.710 align:start position:0% or for organization who actually depend on<00:47:14.830> sending<00:47:15.340> tons<00:47:15.550> of<00:47:15.760> transactions<00:47:16.330> all<00:47:16.540> the 00:47:16.710 --> 00:47:16.720 align:start position:0% on sending tons of transactions all the 00:47:16.720 --> 00:47:19.560 align:start position:0% on sending tons of transactions all the time<00:47:16.960> and<00:47:17.260> for<00:47:17.340> those<00:47:18.340> people<00:47:18.760> it's<00:47:18.910> crucial 00:47:19.560 --> 00:47:19.570 align:start position:0% time and for those people it's crucial 00:47:19.570 --> 00:47:22.050 align:start position:0% time and for those people it's crucial that<00:47:19.810> the<00:47:20.560> things<00:47:20.980> work<00:47:21.280> well<00:47:21.550> because<00:47:21.940> they 00:47:22.050 --> 00:47:22.060 align:start position:0% that the things work well because they 00:47:22.060 --> 00:47:23.610 align:start position:0% that the things work well because they can't<00:47:22.270> just<00:47:22.540> say<00:47:22.660> what<00:47:23.110> we're<00:47:23.260> gonna<00:47:23.350> close 00:47:23.610 --> 00:47:23.620 align:start position:0% can't just say what we're gonna close 00:47:23.620 --> 00:47:25.230 align:start position:0% can't just say what we're gonna close our<00:47:23.800> exchange<00:47:24.130> for<00:47:24.280> four<00:47:24.460> days<00:47:24.640> until<00:47:24.850> this 00:47:25.230 --> 00:47:25.240 align:start position:0% our exchange for four days until this 00:47:25.240 --> 00:47:36.630 align:start position:0% our exchange for four days until this whole<00:47:25.480> things<00:47:25.750> blow<00:47:26.020> over<00:47:26.200> right<00:47:26.350> or<00:47:35.430> we<00:47:36.430> stop 00:47:36.630 --> 00:47:36.640 align:start position:0% whole things blow over right or we stop 00:47:36.640 --> 00:47:39.120 align:start position:0% whole things blow over right or we stop sometime<00:47:36.970> under<00:47:37.540> topics<00:47:37.720> ten<00:47:38.710> minutes<00:47:38.950> any 00:47:39.120 --> 00:47:39.130 align:start position:0% sometime under topics ten minutes any 00:47:39.130 --> 00:47:44.610 align:start position:0% sometime under topics ten minutes any topics<00:47:39.640> yeah<00:47:42.210> Bri<00:47:43.210> I<00:47:43.360> wants<00:47:43.690> to<00:47:43.840> bring<00:47:44.230> up<00:47:44.440> this 00:47:44.610 --> 00:47:44.620 align:start position:0% topics yeah Bri I wants to bring up this 00:47:44.620 --> 00:47:48.750 align:start position:0% topics yeah Bri I wants to bring up this idea<00:47:44.860> that<00:47:45.610> in<00:47:45.880> order<00:47:46.240> to<00:47:46.620> reduce<00:47:47.760> storage 00:47:48.750 --> 00:47:48.760 align:start position:0% idea that in order to reduce storage 00:47:48.760 --> 00:47:52.670 align:start position:0% idea that in order to reduce storage requirements<00:47:49.600> on<00:47:49.750> nodes<00:47:50.050> we<00:47:50.560> like<00:47:50.800> actually 00:47:52.670 --> 00:47:52.680 align:start position:0% requirements on nodes we like actually 00:47:52.680 --> 00:47:55.290 align:start position:0% requirements on nodes we like actually make<00:47:53.680> more<00:47:53.920> progress<00:47:54.220> on<00:47:54.610> implementing<00:47:55.090> a 00:47:55.290 --> 00:47:55.300 align:start position:0% make more progress on implementing a 00:47:55.300 --> 00:47:57.420 align:start position:0% make more progress on implementing a mechanism<00:47:55.720> where<00:47:56.020> we<00:47:56.140> only<00:47:56.320> require<00:47:56.740> nodes<00:47:57.160> to 00:47:57.420 --> 00:47:57.430 align:start position:0% mechanism where we only require nodes to 00:47:57.430 --> 00:47:59.250 align:start position:0% mechanism where we only require nodes to store<00:47:57.700> say<00:47:57.940> the<00:47:58.090> last<00:47:58.270> year<00:47:58.570> of<00:47:58.690> history<00:47:58.870> and 00:47:59.250 --> 00:47:59.260 align:start position:0% store say the last year of history and 00:47:59.260 --> 00:48:00.630 align:start position:0% store say the last year of history and for<00:47:59.440> anything<00:47:59.590> older<00:47:59.950> than<00:47:59.980> one<00:48:00.280> year<00:48:00.520> we 00:48:00.630 --> 00:48:00.640 align:start position:0% for anything older than one year we 00:48:00.640 --> 00:48:02.040 align:start position:0% for anything older than one year we figure<00:48:00.910> out<00:48:01.030> some<00:48:01.330> way<00:48:01.480> we're<00:48:01.690> note<00:48:01.840> where 00:48:02.040 --> 00:48:02.050 align:start position:0% figure out some way we're note where 00:48:02.050 --> 00:48:04.080 align:start position:0% figure out some way we're note where each<00:48:02.230> individual<00:48:02.770> node<00:48:02.980> only<00:48:03.520> needs<00:48:03.760> to<00:48:03.880> store 00:48:04.080 --> 00:48:04.090 align:start position:0% each individual node only needs to store 00:48:04.090 --> 00:48:06.780 align:start position:0% each individual node only needs to store part<00:48:04.360> of<00:48:04.450> that<00:48:04.600> so<00:48:05.260> that<00:48:05.590> we<00:48:06.250> basically 00:48:06.780 --> 00:48:06.790 align:start position:0% part of that so that we basically 00:48:06.790 --> 00:48:09.240 align:start position:0% part of that so that we basically instead<00:48:07.480> of<00:48:07.540> node<00:48:08.140> storage<00:48:08.560> being<00:48:08.770> 200 00:48:09.240 --> 00:48:09.250 align:start position:0% instead of node storage being 200 00:48:09.250 --> 00:48:10.740 align:start position:0% instead of node storage being 200 gigabytes<00:48:09.640> that<00:48:09.820> can<00:48:09.940> just<00:48:10.150> be<00:48:10.270> like<00:48:10.300> state 00:48:10.740 --> 00:48:10.750 align:start position:0% gigabytes that can just be like state 00:48:10.750 --> 00:48:18.990 align:start position:0% gigabytes that can just be like state plus<00:48:11.080> 10<00:48:11.380> attended<00:48:12.190> 20<00:48:17.460> when<00:48:18.460> you<00:48:18.550> when<00:48:18.910> you 00:48:18.990 --> 00:48:19.000 align:start position:0% plus 10 attended 20 when you when you 00:48:19.000 --> 00:48:21.210 align:start position:0% plus 10 attended 20 when you when you say<00:48:19.090> splitting<00:48:19.480> it<00:48:19.570> you<00:48:19.630> don't<00:48:19.810> mean<00:48:19.960> like<00:48:20.220> go 00:48:21.210 --> 00:48:21.220 align:start position:0% say splitting it you don't mean like go 00:48:21.220 --> 00:48:30.980 align:start position:0% say splitting it you don't mean like go to<00:48:21.280> Peter<00:48:24.540> sounds<00:48:25.540> like<00:48:25.630> sharding<00:48:26.140> kinda 00:48:30.980 --> 00:48:30.990 align:start position:0% 00:48:30.990 --> 00:48:33.950 align:start position:0% is<00:48:31.990> it<00:48:32.140> sharding<00:48:32.560> or<00:48:32.680> cheney 00:48:33.950 --> 00:48:33.960 align:start position:0% is it sharding or cheney 00:48:33.960 --> 00:48:37.080 align:start position:0% is it sharding or cheney yeah<00:48:34.960> so<00:48:35.200> I<00:48:35.230> guess<00:48:35.410> this<00:48:35.830> kind<00:48:36.130> of<00:48:36.280> was<00:48:36.520> one<00:48:37.000> of 00:48:37.080 --> 00:48:37.090 align:start position:0% yeah so I guess this kind of was one of 00:48:37.090 --> 00:48:39.270 align:start position:0% yeah so I guess this kind of was one of my<00:48:37.240> proposals<00:48:37.450> from<00:48:38.140> way<00:48:38.410> back<00:48:38.620> in<00:48:38.680> I<00:48:39.070> think 00:48:39.270 --> 00:48:39.280 align:start position:0% my proposals from way back in I think 00:48:39.280 --> 00:48:41.070 align:start position:0% my proposals from way back in I think last<00:48:39.550> year<00:48:39.760> or<00:48:40.150> this<00:48:40.300> year<00:48:40.360> journey<00:48:40.690> or<00:48:40.870> last 00:48:41.070 --> 00:48:41.080 align:start position:0% last year or this year journey or last 00:48:41.080 --> 00:48:43.460 align:start position:0% last year or this year journey or last year<00:48:41.200> January<00:48:41.620> so<00:48:42.070> the<00:48:42.220> idea<00:48:42.460> was<00:48:42.700> that 00:48:43.460 --> 00:48:43.470 align:start position:0% year January so the idea was that 00:48:43.470 --> 00:48:47.400 align:start position:0% year January so the idea was that currently<00:48:44.470> a<00:48:44.980> lot<00:48:45.910> of<00:48:46.060> the<00:48:46.240> ether<00:48:46.600> ohms<00:48:46.750> chain 00:48:47.400 --> 00:48:47.410 align:start position:0% currently a lot of the ether ohms chain 00:48:47.410 --> 00:48:49.500 align:start position:0% currently a lot of the ether ohms chain data<00:48:47.650> about<00:48:48.010> one<00:48:48.220> another<00:48:48.490> 50<00:48:48.880> gigs<00:48:49.090> give<00:48:49.390> or 00:48:49.500 --> 00:48:49.510 align:start position:0% data about one another 50 gigs give or 00:48:49.510 --> 00:48:52.470 align:start position:0% data about one another 50 gigs give or take<00:48:49.690> is<00:48:49.960> just<00:48:50.440> immutable<00:48:50.830> past<00:48:51.370> chain<00:48:51.940> for 00:48:52.470 --> 00:48:52.480 align:start position:0% take is just immutable past chain for 00:48:52.480 --> 00:48:54.300 align:start position:0% take is just immutable past chain for example<00:48:52.510> past<00:48:53.020> transactions<00:48:53.650> past<00:48:53.950> blocks 00:48:54.300 --> 00:48:54.310 align:start position:0% example past transactions past blocks 00:48:54.310 --> 00:48:57.720 align:start position:0% example past transactions past blocks past<00:48:54.640> receipts<00:48:55.120> and<00:48:56.010> many<00:48:57.010> people<00:48:57.460> don't 00:48:57.720 --> 00:48:57.730 align:start position:0% past receipts and many people don't 00:48:57.730 --> 00:49:00.000 align:start position:0% past receipts and many people don't really<00:48:58.000> need<00:48:58.300> this<00:48:58.510> I<00:48:58.720> mean<00:48:58.870> yes<00:48:59.410> it's<00:48:59.770> nice 00:49:00.000 --> 00:49:00.010 align:start position:0% really need this I mean yes it's nice 00:49:00.010 --> 00:49:01.560 align:start position:0% really need this I mean yes it's nice that<00:49:00.070> you<00:49:00.370> can<00:49:00.400> dig<00:49:00.730> up<00:49:00.850> your<00:49:00.910> transaction 00:49:01.560 --> 00:49:01.570 align:start position:0% that you can dig up your transaction 00:49:01.570 --> 00:49:02.850 align:start position:0% that you can dig up your transaction that<00:49:01.690> you<00:49:01.810> did<00:49:01.990> five<00:49:02.260> years<00:49:02.290> ago 00:49:02.850 --> 00:49:02.860 align:start position:0% that you did five years ago 00:49:02.860 --> 00:49:05.370 align:start position:0% that you did five years ago but<00:49:03.610> do<00:49:03.820> you<00:49:03.940> realistically<00:49:04.330> want<00:49:04.930> to<00:49:05.110> do<00:49:05.230> it 00:49:05.370 --> 00:49:05.380 align:start position:0% but do you realistically want to do it 00:49:05.380 --> 00:49:08.640 align:start position:0% but do you realistically want to do it now<00:49:06.280> if<00:49:06.580> you<00:49:06.850> don't<00:49:07.120> want<00:49:07.390> to<00:49:07.510> do<00:49:07.630> it<00:49:07.750> and<00:49:07.960> okay 00:49:08.640 --> 00:49:08.650 align:start position:0% now if you don't want to do it and okay 00:49:08.650 --> 00:49:09.960 align:start position:0% now if you don't want to do it and okay that's<00:49:08.920> that<00:49:09.280> might<00:49:09.490> be<00:49:09.640> an<00:49:09.730> interesting 00:49:09.960 --> 00:49:09.970 align:start position:0% that's that might be an interesting 00:49:09.970 --> 00:49:11.760 align:start position:0% that's that might be an interesting thing<00:49:10.210> for<00:49:10.900> you<00:49:11.020> to<00:49:11.200> want<00:49:11.350> to<00:49:11.440> dig<00:49:11.590> up<00:49:11.740> your 00:49:11.760 --> 00:49:11.770 align:start position:0% thing for you to want to dig up your 00:49:11.770 --> 00:49:13.500 align:start position:0% thing for you to want to dig up your transaction<00:49:12.430> from<00:49:12.520> five<00:49:12.820> years<00:49:13.030> ago<00:49:13.330> I 00:49:13.500 --> 00:49:13.510 align:start position:0% transaction from five years ago I 00:49:13.510 --> 00:49:15.090 align:start position:0% transaction from five years ago I definitely<00:49:14.260> don't<00:49:14.380> want<00:49:14.620> to<00:49:14.680> pick<00:49:14.860> up<00:49:14.920> your 00:49:15.090 --> 00:49:15.100 align:start position:0% definitely don't want to pick up your 00:49:15.100 --> 00:49:17.370 align:start position:0% definitely don't want to pick up your transaction<00:49:15.610> for<00:49:15.730> five<00:49:15.970> years<00:49:16.210> ago<00:49:16.450> so 00:49:17.370 --> 00:49:17.380 align:start position:0% transaction for five years ago so 00:49:17.380 --> 00:49:19.290 align:start position:0% transaction for five years ago so essentially<00:49:17.860> it's<00:49:17.980> just<00:49:18.040> we're<00:49:18.760> wasting<00:49:19.240> a 00:49:19.290 --> 00:49:19.300 align:start position:0% essentially it's just we're wasting a 00:49:19.300 --> 00:49:21.510 align:start position:0% essentially it's just we're wasting a lot<00:49:19.390> of<00:49:19.450> space<00:49:19.810> for<00:49:19.840> a<00:49:20.020> lot<00:49:20.110> of<00:49:20.200> people<00:49:20.680> that 00:49:21.510 --> 00:49:21.520 align:start position:0% lot of space for a lot of people that 00:49:21.520 --> 00:49:23.840 align:start position:0% lot of space for a lot of people that and<00:49:21.940> it<00:49:22.150> doesn't<00:49:22.450> really<00:49:22.540> give<00:49:22.780> a<00:49:22.810> anything 00:49:23.840 --> 00:49:23.850 align:start position:0% and it doesn't really give a anything 00:49:23.850 --> 00:49:27.120 align:start position:0% and it doesn't really give a anything back<00:49:24.850> and<00:49:25.150> then<00:49:25.600> the<00:49:25.780> the<00:49:26.080> idea<00:49:26.440> was<00:49:26.680> that<00:49:26.710> can 00:49:27.120 --> 00:49:27.130 align:start position:0% back and then the the idea was that can 00:49:27.130 --> 00:49:30.090 align:start position:0% back and then the the idea was that can we<00:49:27.250> somehow<00:49:27.660> say<00:49:28.660> that<00:49:28.840> okay<00:49:29.170> we're<00:49:29.800> going<00:49:30.010> to 00:49:30.090 --> 00:49:30.100 align:start position:0% we somehow say that okay we're going to 00:49:30.100 --> 00:49:33.390 align:start position:0% we somehow say that okay we're going to maintain<00:49:30.460> the<00:49:30.700> last<00:49:31.140> some<00:49:32.140> time<00:49:32.770> frame<00:49:33.190> maybe 00:49:33.390 --> 00:49:33.400 align:start position:0% maintain the last some time frame maybe 00:49:33.400 --> 00:49:35.070 align:start position:0% maintain the last some time frame maybe a<00:49:33.550> year<00:49:33.940> and<00:49:34.090> maintain<00:49:34.510> everything<00:49:34.900> on<00:49:35.020> all 00:49:35.070 --> 00:49:35.080 align:start position:0% a year and maintain everything on all 00:49:35.080 --> 00:49:36.990 align:start position:0% a year and maintain everything on all who<00:49:35.350> knows<00:49:35.560> but<00:49:36.010> everything<00:49:36.460> that's<00:49:36.640> older 00:49:36.990 --> 00:49:37.000 align:start position:0% who knows but everything that's older 00:49:37.000 --> 00:49:39.810 align:start position:0% who knows but everything that's older than<00:49:37.210> one<00:49:37.990> year<00:49:38.260> let's<00:49:38.470> try<00:49:38.920> to<00:49:38.980> put<00:49:39.400> it<00:49:39.550> stash 00:49:39.810 --> 00:49:39.820 align:start position:0% than one year let's try to put it stash 00:49:39.820 --> 00:49:41.430 align:start position:0% than one year let's try to put it stash it<00:49:39.970> somewhere<00:49:40.300> else<00:49:40.600> and<00:49:40.960> make<00:49:41.200> it<00:49:41.320> available 00:49:41.430 --> 00:49:41.440 align:start position:0% it somewhere else and make it available 00:49:41.440 --> 00:49:44.820 align:start position:0% it somewhere else and make it available and<00:49:42.390> generally<00:49:43.390> I<00:49:43.420> think<00:49:43.600> most<00:49:44.230> of<00:49:44.440> this<00:49:44.590> is 00:49:44.820 --> 00:49:44.830 align:start position:0% and generally I think most of this is 00:49:44.830 --> 00:49:47.580 align:start position:0% and generally I think most of this is doable<00:49:45.190> so<00:49:45.970> it<00:49:46.120> it<00:49:46.570> is<00:49:46.780> not<00:49:46.960> even<00:49:47.260> a<00:49:47.350> hard 00:49:47.580 --> 00:49:47.590 align:start position:0% doable so it it is not even a hard 00:49:47.590 --> 00:49:50.270 align:start position:0% doable so it it is not even a hard problem<00:49:47.890> to<00:49:48.190> solve<00:49:48.430> the<00:49:49.150> tricky<00:49:49.510> parts<00:49:49.900> come 00:49:50.270 --> 00:49:50.280 align:start position:0% problem to solve the tricky parts come 00:49:50.280 --> 00:49:52.530 align:start position:0% problem to solve the tricky parts come start<00:49:51.280> to<00:49:51.370> appear<00:49:51.610> with<00:49:51.820> for<00:49:51.970> example<00:49:52.060> logs 00:49:52.530 --> 00:49:52.540 align:start position:0% start to appear with for example logs 00:49:52.540 --> 00:49:55.980 align:start position:0% start to appear with for example logs because<00:49:53.230> they<00:49:53.530> are<00:49:53.970> so<00:49:54.970> contracts<00:49:55.780> for 00:49:55.980 --> 00:49:55.990 align:start position:0% because they are so contracts for 00:49:55.990 --> 00:49:58.260 align:start position:0% because they are so contracts for contracts<00:49:56.410> use<00:49:56.620> logs<00:49:56.920> as<00:49:57.310> a<00:49:57.700> cheap<00:49:58.000> data 00:49:58.260 --> 00:49:58.270 align:start position:0% contracts use logs as a cheap data 00:49:58.270 --> 00:50:00.660 align:start position:0% contracts use logs as a cheap data storage<00:49:58.750> and<00:49:58.960> then<00:49:59.710> they<00:49:59.950> just<00:50:00.310> the<00:50:00.490> Deb 00:50:00.660 --> 00:50:00.670 align:start position:0% storage and then they just the Deb 00:50:00.670 --> 00:50:03.030 align:start position:0% storage and then they just the Deb filters<00:50:01.210> for<00:50:01.420> the<00:50:01.480> logs<00:50:01.780> and<00:50:02.140> the<00:50:02.590> issue<00:50:02.740> is 00:50:03.030 --> 00:50:03.040 align:start position:0% filters for the logs and the issue is 00:50:03.040 --> 00:50:04.740 align:start position:0% filters for the logs and the issue is that<00:50:03.070> logs<00:50:03.550> weren't<00:50:04.000> really<00:50:04.210> designed<00:50:04.360> for 00:50:04.740 --> 00:50:04.750 align:start position:0% that logs weren't really designed for 00:50:04.750 --> 00:50:07.110 align:start position:0% that logs weren't really designed for this<00:50:05.110> but<00:50:05.680> it<00:50:06.160> wasn't<00:50:06.490> really<00:50:06.670> explicitly 00:50:07.110 --> 00:50:07.120 align:start position:0% this but it wasn't really explicitly 00:50:07.120 --> 00:50:08.820 align:start position:0% this but it wasn't really explicitly said<00:50:07.450> nor<00:50:07.660> limited<00:50:08.170> that<00:50:08.320> this<00:50:08.560> is<00:50:08.680> not 00:50:08.820 --> 00:50:08.830 align:start position:0% said nor limited that this is not 00:50:08.830 --> 00:50:10.890 align:start position:0% said nor limited that this is not intended<00:50:09.190> use<00:50:09.490> case<00:50:09.730> the<00:50:10.240> Internet<00:50:10.570> use<00:50:10.690> case 00:50:10.890 --> 00:50:10.900 align:start position:0% intended use case the Internet use case 00:50:10.900 --> 00:50:14.670 align:start position:0% intended use case the Internet use case of<00:50:11.050> logs<00:50:11.320> was<00:50:11.590> to<00:50:11.970> raise<00:50:12.970> events<00:50:13.570> so<00:50:14.110> your 00:50:14.670 --> 00:50:14.680 align:start position:0% of logs was to raise events so your 00:50:14.680 --> 00:50:16.800 align:start position:0% of logs was to raise events so your smart<00:50:14.950> contract<00:50:15.280> does<00:50:15.430> something<00:50:15.940> it<00:50:16.450> raises 00:50:16.800 --> 00:50:16.810 align:start position:0% smart contract does something it raises 00:50:16.810 --> 00:50:19.380 align:start position:0% smart contract does something it raises a<00:50:16.840> few<00:50:17.080> events<00:50:17.500> and<00:50:17.650> then<00:50:17.800> you<00:50:18.430> react<00:50:18.880> to<00:50:19.210> those 00:50:19.380 --> 00:50:19.390 align:start position:0% a few events and then you react to those 00:50:19.390 --> 00:50:21.150 align:start position:0% a few events and then you react to those events<00:50:19.750> and<00:50:19.930> yes<00:50:20.230> it's<00:50:20.440> nice<00:50:20.590> that<00:50:20.650> you<00:50:20.980> don't 00:50:21.150 --> 00:50:21.160 align:start position:0% events and yes it's nice that you don't 00:50:21.160 --> 00:50:23.340 align:start position:0% events and yes it's nice that you don't have<00:50:21.280> to<00:50:21.400> react<00:50:21.700> immediately<00:50:21.970> you<00:50:22.780> can<00:50:23.020> react 00:50:23.340 --> 00:50:23.350 align:start position:0% have to react immediately you can react 00:50:23.350 --> 00:50:25.680 align:start position:0% have to react immediately you can react a<00:50:23.710> day<00:50:24.010> later<00:50:24.250> a<00:50:24.430> week<00:50:24.760> later<00:50:24.970> a<00:50:25.120> month<00:50:25.420> later 00:50:25.680 --> 00:50:25.690 align:start position:0% a day later a week later a month later 00:50:25.690 --> 00:50:28.050 align:start position:0% a day later a week later a month later and<00:50:26.050> that's<00:50:26.230> perfectly<00:50:26.620> fine<00:50:26.860> the<00:50:27.520> problem<00:50:27.670> is 00:50:28.050 --> 00:50:28.060 align:start position:0% and that's perfectly fine the problem is 00:50:28.060 --> 00:50:29.820 align:start position:0% and that's perfectly fine the problem is that<00:50:28.300> for<00:50:28.420> example<00:50:28.480> there<00:50:28.900> are<00:50:28.930> Deb's<00:50:29.380> kind<00:50:29.770> of 00:50:29.820 --> 00:50:29.830 align:start position:0% that for example there are Deb's kind of 00:50:29.830 --> 00:50:31.890 align:start position:0% that for example there are Deb's kind of like<00:50:30.010> the<00:50:30.130> Akasha<00:50:30.430> social<00:50:30.910> network<00:50:31.270> which 00:50:31.890 --> 00:50:31.900 align:start position:0% like the Akasha social network which 00:50:31.900 --> 00:50:34.410 align:start position:0% like the Akasha social network which uses<00:50:32.470> logs<00:50:32.800> to<00:50:33.070> store<00:50:33.340> the<00:50:33.490> post<00:50:33.730> themselves 00:50:34.410 --> 00:50:34.420 align:start position:0% uses logs to store the post themselves 00:50:34.420 --> 00:50:36.600 align:start position:0% uses logs to store the post themselves which<00:50:34.780> means<00:50:35.050> that<00:50:35.260> when<00:50:35.440> you<00:50:35.560> want<00:50:35.800> to<00:50:36.280> list 00:50:36.600 --> 00:50:36.610 align:start position:0% which means that when you want to list 00:50:36.610 --> 00:50:38.250 align:start position:0% which means that when you want to list the<00:50:36.880> post<00:50:37.120> that<00:50:37.420> you've<00:50:37.600> written<00:50:37.780> or<00:50:38.110> your 00:50:38.250 --> 00:50:38.260 align:start position:0% the post that you've written or your 00:50:38.260 --> 00:50:40.520 align:start position:0% the post that you've written or your feed<00:50:38.560> they<00:50:39.070> will<00:50:39.280> actually<00:50:39.430> scan<00:50:40.180> the<00:50:40.330> in 00:50:40.520 --> 00:50:40.530 align:start position:0% feed they will actually scan the in 00:50:40.530 --> 00:50:43.640 align:start position:0% feed they will actually scan the in a<00:50:40.560> blockchain<00:50:41.010> for<00:50:41.700> data<00:50:42.150> and<00:50:42.720> these<00:50:43.320> are<00:50:43.530> the 00:50:43.640 --> 00:50:43.650 align:start position:0% a blockchain for data and these are the 00:50:43.650 --> 00:50:46.100 align:start position:0% a blockchain for data and these are the use<00:50:43.800> cases<00:50:43.920> that<00:50:44.480> that<00:50:45.480> gets<00:50:45.720> really<00:50:45.900> really 00:50:46.100 --> 00:50:46.110 align:start position:0% use cases that that gets really really 00:50:46.110 --> 00:50:47.840 align:start position:0% use cases that that gets really really broken<00:50:46.500> because<00:50:46.950> all<00:50:47.070> of<00:50:47.100> a<00:50:47.280> sudden<00:50:47.580> you<00:50:47.670> have 00:50:47.840 --> 00:50:47.850 align:start position:0% broken because all of a sudden you have 00:50:47.850 --> 00:50:50.870 align:start position:0% broken because all of a sudden you have a<00:50:47.880> node<00:50:48.180> that<00:50:48.530> wants<00:50:49.530> to<00:50:49.560> access<00:50:49.860> all<00:50:50.370> the<00:50:50.640> time 00:50:50.870 --> 00:50:50.880 align:start position:0% a node that wants to access all the time 00:50:50.880 --> 00:50:52.940 align:start position:0% a node that wants to access all the time the<00:50:51.300> history<00:50:51.720> going<00:50:51.900> back<00:50:52.050> to<00:50:52.380> the<00:50:52.470> past<00:50:52.680> five 00:50:52.940 --> 00:50:52.950 align:start position:0% the history going back to the past five 00:50:52.950 --> 00:50:55.010 align:start position:0% the history going back to the past five years<00:50:52.980> and<00:50:53.400> this<00:50:54.090> is<00:50:54.240> their<00:50:54.570> really<00:50:54.810> the 00:50:55.010 --> 00:50:55.020 align:start position:0% years and this is their really the 00:50:55.020 --> 00:50:57.920 align:start position:0% years and this is their really the challenge<00:50:55.410> that<00:50:55.500> that<00:50:56.180> needs<00:50:57.180> to<00:50:57.300> be<00:50:57.420> solved 00:50:57.920 --> 00:50:57.930 align:start position:0% challenge that that needs to be solved 00:50:57.930 --> 00:51:01.160 align:start position:0% challenge that that needs to be solved on<00:50:57.990> the<00:50:58.680> upside<00:50:58.830> however<00:50:59.720> the<00:51:00.720> nice<00:51:00.960> thing 00:51:01.160 --> 00:51:01.170 align:start position:0% on the upside however the nice thing 00:51:01.170 --> 00:51:03.800 align:start position:0% on the upside however the nice thing about<00:51:01.260> this<00:51:01.590> chain<00:51:02.190> Pass<00:51:02.760> chain<00:51:03.150> data<00:51:03.330> is<00:51:03.630> that 00:51:03.800 --> 00:51:03.810 align:start position:0% about this chain Pass chain data is that 00:51:03.810 --> 00:51:06.830 align:start position:0% about this chain Pass chain data is that it's<00:51:04.050> immutable<00:51:04.640> which<00:51:05.640> does<00:51:05.910> mean<00:51:06.210> that<00:51:06.270> I 00:51:06.830 --> 00:51:06.840 align:start position:0% it's immutable which does mean that I 00:51:06.840 --> 00:51:08.300 align:start position:0% it's immutable which does mean that I mean<00:51:07.140> immutable<00:51:07.650> in<00:51:07.770> theory<00:51:08.100> is<00:51:08.190> not 00:51:08.300 --> 00:51:08.310 align:start position:0% mean immutable in theory is not 00:51:08.310 --> 00:51:10.220 align:start position:0% mean immutable in theory is not immutable<00:51:08.910> but<00:51:09.060> in<00:51:09.240> practice<00:51:09.690> do<00:51:09.840> the<00:51:10.020> proof 00:51:10.220 --> 00:51:10.230 align:start position:0% immutable but in practice do the proof 00:51:10.230 --> 00:51:12.590 align:start position:0% immutable but in practice do the proof of<00:51:10.350> work<00:51:10.590> you<00:51:11.040> won't<00:51:11.280> have<00:51:11.460> a<00:51:11.520> real<00:51:11.790> that's<00:51:12.150> a 00:51:12.590 --> 00:51:12.600 align:start position:0% of work you won't have a real that's a 00:51:12.600 --> 00:51:15.110 align:start position:0% of work you won't have a real that's a million<00:51:12.930> block<00:51:13.140> deep<00:51:13.380> and<00:51:13.760> this<00:51:14.760> kind<00:51:15.060> of 00:51:15.110 --> 00:51:15.120 align:start position:0% million block deep and this kind of 00:51:15.120 --> 00:51:17.750 align:start position:0% million block deep and this kind of means<00:51:15.360> that<00:51:15.540> you<00:51:16.260> can<00:51:16.530> move<00:51:16.770> this<00:51:17.070> data<00:51:17.310> on<00:51:17.580> to 00:51:17.750 --> 00:51:17.760 align:start position:0% means that you can move this data on to 00:51:17.760 --> 00:51:20.900 align:start position:0% means that you can move this data on to an<00:51:17.850> HDD<00:51:18.210> so<00:51:19.050> you<00:51:19.110> can<00:51:19.440> actually<00:51:19.740> make<00:51:20.220> store<00:51:20.760> it 00:51:20.900 --> 00:51:20.910 align:start position:0% an HDD so you can actually make store it 00:51:20.910 --> 00:51:24.020 align:start position:0% an HDD so you can actually make store it relatively<00:51:21.630> cheaply<00:51:22.160> however<00:51:23.160> I<00:51:23.250> do<00:51:23.430> I<00:51:23.730> still 00:51:24.020 --> 00:51:24.030 align:start position:0% relatively cheaply however I do I still 00:51:24.030 --> 00:51:26.740 align:start position:0% relatively cheaply however I do I still say<00:51:24.210> that<00:51:24.240> if<00:51:24.720> we<00:51:25.050> want<00:51:25.230> to<00:51:25.320> enter<00:51:25.500> these 00:51:26.740 --> 00:51:26.750 align:start position:0% say that if we want to enter these 00:51:26.750 --> 00:51:31.190 align:start position:0% say that if we want to enter these stateless<00:51:27.750> clients<00:51:28.260> territory<00:51:28.830> then<00:51:30.080> well<00:51:31.080> if 00:51:31.190 --> 00:51:31.200 align:start position:0% stateless clients territory then well if 00:51:31.200 --> 00:51:32.720 align:start position:0% stateless clients territory then well if the<00:51:31.350> blocks<00:51:31.560> all<00:51:31.740> of<00:51:31.860> a<00:51:31.920> sudden<00:51:32.190> becomes<00:51:32.520> a 00:51:32.720 --> 00:51:32.730 align:start position:0% the blocks all of a sudden becomes a 00:51:32.730 --> 00:51:35.060 align:start position:0% the blocks all of a sudden becomes a hundred<00:51:33.030> times<00:51:33.180> larger<00:51:33.540> than<00:51:34.020> we<00:51:34.890> need<00:51:35.040> to 00:51:35.060 --> 00:51:35.070 align:start position:0% hundred times larger than we need to 00:51:35.070 --> 00:51:37.040 align:start position:0% hundred times larger than we need to solve<00:51:35.370> this<00:51:35.550> because<00:51:35.730> even<00:51:36.150> on<00:51:36.420> an<00:51:36.540> HDD<00:51:36.840> you 00:51:37.040 --> 00:51:37.050 align:start position:0% solve this because even on an HDD you 00:51:37.050 --> 00:51:39.860 align:start position:0% solve this because even on an HDD you don't<00:51:37.260> want<00:51:37.470> to<00:51:37.590> put<00:51:37.770> 100<00:51:38.220> times<00:51:38.430> more<00:51:38.550> data<00:51:38.910> so 00:51:39.860 --> 00:51:39.870 align:start position:0% don't want to put 100 times more data so 00:51:39.870 --> 00:51:42.760 align:start position:0% don't want to put 100 times more data so it's<00:51:39.990> an<00:51:40.080> interesting<00:51:40.320> problem<00:51:41.040> definitely 00:51:42.760 --> 00:51:42.770 align:start position:0% it's an interesting problem definitely 00:51:42.770 --> 00:51:45.740 align:start position:0% it's an interesting problem definitely so<00:51:43.820> something<00:51:44.820> interacting<00:51:45.270> with<00:51:45.390> the<00:51:45.510> next 00:51:45.740 --> 00:51:45.750 align:start position:0% so something interacting with the next 00:51:45.750 --> 00:51:48.410 align:start position:0% so something interacting with the next section<00:51:46.080> of<00:51:46.260> topics<00:51:46.710> how<00:51:47.490> does<00:51:47.700> the<00:51:47.850> finality 00:51:48.410 --> 00:51:48.420 align:start position:0% section of topics how does the finality 00:51:48.420 --> 00:51:50.450 align:start position:0% section of topics how does the finality gadget<00:51:48.810> figure<00:51:49.020> in<00:51:49.140> with<00:51:49.290> a<00:51:49.350> chain<00:51:49.530> data<00:51:49.740> do<00:51:50.400> we 00:51:50.450 --> 00:51:50.460 align:start position:0% gadget figure in with a chain data do we 00:51:50.460 --> 00:51:52.340 align:start position:0% gadget figure in with a chain data do we need<00:51:50.700> to<00:51:50.790> keep<00:51:51.000> historical<00:51:51.600> data<00:51:51.780> being<00:51:52.170> on 00:51:52.340 --> 00:51:52.350 align:start position:0% need to keep historical data being on 00:51:52.350 --> 00:51:54.920 align:start position:0% need to keep historical data being on the<00:51:52.470> horizon<00:51:52.890> of<00:51:53.040> the<00:51:53.250> agreed-upon<00:51:54.060> finality 00:51:54.920 --> 00:51:54.930 align:start position:0% the horizon of the agreed-upon finality 00:51:54.930 --> 00:51:57.140 align:start position:0% the horizon of the agreed-upon finality and<00:51:55.140> how<00:51:55.530> far<00:51:55.860> you<00:51:56.400> know<00:51:56.490> how<00:51:56.700> important<00:51:57.060> is 00:51:57.140 --> 00:51:57.150 align:start position:0% and how far you know how important is 00:51:57.150 --> 00:52:00.350 align:start position:0% and how far you know how important is that<00:51:58.340> finality<00:51:59.340> gadget<00:51:59.820> you<00:51:59.910> mean<00:52:00.030> like<00:52:00.210> that 00:52:00.350 --> 00:52:00.360 align:start position:0% that finality gadget you mean like that 00:52:00.360 --> 00:52:03.110 align:start position:0% that finality gadget you mean like that used<00:52:00.510> to<00:52:00.630> finality<00:52:00.930> I<00:52:01.050> should<00:52:01.290> get<00:52:01.530> one<00:52:02.120> and 00:52:03.110 --> 00:52:03.120 align:start position:0% used to finality I should get one and 00:52:03.120 --> 00:52:05.570 align:start position:0% used to finality I should get one and for<00:52:03.630> consensus<00:52:04.320> purposes<00:52:04.860> you<00:52:05.040> definitely 00:52:05.570 --> 00:52:05.580 align:start position:0% for consensus purposes you definitely 00:52:05.580 --> 00:52:07.700 align:start position:0% for consensus purposes you definitely don't<00:52:05.940> need<00:52:06.180> to<00:52:06.480> keep<00:52:06.690> any<00:52:06.870> history<00:52:07.290> older 00:52:07.700 --> 00:52:07.710 align:start position:0% don't need to keep any history older 00:52:07.710 --> 00:52:11.990 align:start position:0% don't need to keep any history older than<00:52:07.920> about<00:52:08.160> eight<00:52:08.370> months<00:52:09.530> but<00:52:10.530> and<00:52:11.070> like<00:52:11.760> one 00:52:11.990 --> 00:52:12.000 align:start position:0% than about eight months but and like one 00:52:12.000 --> 00:52:13.760 align:start position:0% than about eight months but and like one year<00:52:12.270> was<00:52:12.450> the<00:52:12.570> period<00:52:12.930> that<00:52:13.020> I<00:52:13.080> had<00:52:13.230> suggested 00:52:13.760 --> 00:52:13.770 align:start position:0% year was the period that I had suggested 00:52:13.770 --> 00:52:15.950 align:start position:0% year was the period that I had suggested we<00:52:13.890> make<00:52:14.010> kind<00:52:14.280> of<00:52:14.370> mandatory<00:52:14.640> doubled<00:52:15.270> so 00:52:15.950 --> 00:52:15.960 align:start position:0% we make kind of mandatory doubled so 00:52:15.960 --> 00:52:19.490 align:start position:0% we make kind of mandatory doubled so sorry<00:52:16.830> so<00:52:17.070> so<00:52:17.640> the<00:52:17.760> one<00:52:17.910> proposal<00:52:18.480> and<00:52:19.140> that<00:52:19.170> ia 00:52:19.490 --> 00:52:19.500 align:start position:0% sorry so so the one proposal and that ia 00:52:19.500 --> 00:52:22.130 align:start position:0% sorry so so the one proposal and that ia that<00:52:20.310> I<00:52:20.370> have<00:52:20.700> for<00:52:21.000> solving<00:52:21.450> this<00:52:21.660> receipt 00:52:22.130 --> 00:52:22.140 align:start position:0% that I have for solving this receipt 00:52:22.140 --> 00:52:25.040 align:start position:0% that I have for solving this receipt issue<00:52:22.350> is<00:52:22.860> that<00:52:23.120> it's<00:52:24.120> actually<00:52:24.300> a<00:52:24.570> very<00:52:24.780> nice 00:52:25.040 --> 00:52:25.050 align:start position:0% issue is that it's actually a very nice 00:52:25.050 --> 00:52:26.600 align:start position:0% issue is that it's actually a very nice problem<00:52:25.560> to<00:52:25.710> just<00:52:25.740> solve<00:52:26.100> with<00:52:26.250> a<00:52:26.280> group<00:52:26.490> to 00:52:26.600 --> 00:52:26.610 align:start position:0% problem to just solve with a group to 00:52:26.610 --> 00:52:28.790 align:start position:0% problem to just solve with a group to economic<00:52:27.060> light<00:52:27.210> quite<00:52:27.450> market<00:52:27.930> right<00:52:28.290> like<00:52:28.560> I 00:52:28.790 --> 00:52:28.800 align:start position:0% economic light quite market right like I 00:52:28.800 --> 00:52:31.220 align:start position:0% economic light quite market right like I want<00:52:29.490> to<00:52:29.640> keep<00:52:29.790> a<00:52:29.970> list<00:52:30.180> of<00:52:30.360> all<00:52:30.510> risks<00:52:30.750> of<00:52:30.930> all 00:52:31.220 --> 00:52:31.230 align:start position:0% want to keep a list of all risks of all 00:52:31.230 --> 00:52:33.920 align:start position:0% want to keep a list of all risks of all the<00:52:31.410> transactions<00:52:32.100> that<00:52:33.090> satisfy<00:52:33.630> some 00:52:33.920 --> 00:52:33.930 align:start position:0% the transactions that satisfy some 00:52:33.930 --> 00:52:36.620 align:start position:0% the transactions that satisfy some particular<00:52:34.170> bloom<00:52:34.650> filter<00:52:35.010> I<00:52:35.280> asked<00:52:35.760> you<00:52:36.090> you 00:52:36.620 --> 00:52:36.630 align:start position:0% particular bloom filter I asked you you 00:52:36.630 --> 00:52:38.360 align:start position:0% particular bloom filter I asked you you give<00:52:36.870> me<00:52:37.050> a<00:52:37.080> complete<00:52:37.500> list<00:52:37.740> and<00:52:38.010> you<00:52:38.100> sign 00:52:38.360 --> 00:52:38.370 align:start position:0% give me a complete list and you sign 00:52:38.370 --> 00:52:42.080 align:start position:0% give me a complete list and you sign that<00:52:38.610> list<00:52:38.880> and<00:52:39.270> if<00:52:40.230> it's<00:52:41.190> or<00:52:41.370> if<00:52:41.580> someone<00:52:41.970> else 00:52:42.080 --> 00:52:42.090 align:start position:0% that list and if it's or if someone else 00:52:42.090 --> 00:52:43.790 align:start position:0% that list and if it's or if someone else disagrees<00:52:42.660> they<00:52:42.900> can<00:52:43.050> make<00:52:43.200> a<00:52:43.230> miracle<00:52:43.470> proof 00:52:43.790 --> 00:52:43.800 align:start position:0% disagrees they can make a miracle proof 00:52:43.800 --> 00:52:45.410 align:start position:0% disagrees they can make a miracle proof and<00:52:44.010> they<00:52:44.100> can<00:52:44.280> like<00:52:44.490> so<00:52:44.640> and<00:52:44.940> they<00:52:45.030> can<00:52:45.180> slash 00:52:45.410 --> 00:52:45.420 align:start position:0% and they can like so and they can slash 00:52:45.420 --> 00:52:50.300 align:start position:0% and they can like so and they can slash your<00:52:45.570> deposit<00:52:46.080> so<00:52:47.180> like<00:52:48.180> basic<00:52:48.750> turning<00:52:49.310> like 00:52:50.300 --> 00:52:50.310 align:start position:0% your deposit so like basic turning like 00:52:50.310 --> 00:52:52.530 align:start position:0% your deposit so like basic turning like making<00:52:50.760> something<00:52:51.120> like<00:52:51.450> that 00:52:52.530 --> 00:52:52.540 align:start position:0% making something like that 00:52:52.540 --> 00:52:54.120 align:start position:0% making something like that the<00:52:52.660> other<00:52:52.990> benefit<00:52:53.380> of<00:52:53.470> that<00:52:53.500> approach<00:52:53.920> is 00:52:54.120 --> 00:52:54.130 align:start position:0% the other benefit of that approach is 00:52:54.130 --> 00:52:55.680 align:start position:0% the other benefit of that approach is that<00:52:54.160> instead<00:52:54.550> of<00:52:54.670> requiring<00:52:54.970> like<00:52:55.390> you<00:52:55.570> to 00:52:55.680 --> 00:52:55.690 align:start position:0% that instead of requiring like you to 00:52:55.690 --> 00:52:57.240 align:start position:0% that instead of requiring like you to scan<00:52:55.930> a<00:52:55.960> bunch<00:52:56.230> of<00:52:56.320> headers<00:52:56.560> walk<00:52:56.830> away<00:52:57.100> it's 00:52:57.240 --> 00:52:57.250 align:start position:0% scan a bunch of headers walk away it's 00:52:57.250 --> 00:52:59.370 align:start position:0% scan a bunch of headers walk away it's basically<00:52:57.700> a<00:52:58.120> few<00:52:58.630> rounds<00:52:58.990> of<00:52:59.050> network 00:52:59.370 --> 00:52:59.380 align:start position:0% basically a few rounds of network 00:52:59.380 --> 00:53:02.010 align:start position:0% basically a few rounds of network messaging<00:52:59.950> so<00:53:00.490> could<00:53:01.030> be<00:53:01.150> also<00:53:01.330> interesting 00:53:02.010 --> 00:53:02.020 align:start position:0% messaging so could be also interesting 00:53:02.020 --> 00:53:03.540 align:start position:0% messaging so could be also interesting to<00:53:02.050> look<00:53:02.290> into<00:53:02.500> prototyping<00:53:03.040> in<00:53:03.190> the<00:53:03.280> medium 00:53:03.540 --> 00:53:03.550 align:start position:0% to look into prototyping in the medium 00:53:03.550 --> 00:53:07.140 align:start position:0% to look into prototyping in the medium term<00:53:04.440> so<00:53:05.440> maybe<00:53:05.740> one<00:53:06.370> thing<00:53:06.640> we<00:53:06.820> could<00:53:07.000> do 00:53:07.140 --> 00:53:07.150 align:start position:0% term so maybe one thing we could do 00:53:07.150 --> 00:53:08.580 align:start position:0% term so maybe one thing we could do because<00:53:07.360> there's<00:53:07.750> so<00:53:07.900> many<00:53:08.020> people<00:53:08.440> in<00:53:08.500> the 00:53:08.580 --> 00:53:08.590 align:start position:0% because there's so many people in the 00:53:08.590 --> 00:53:11.280 align:start position:0% because there's so many people in the room<00:53:08.770> we're<00:53:09.400> just<00:53:09.670> like<00:53:09.850> us<00:53:10.060> like<00:53:10.420> a<00:53:10.780> lot<00:53:11.170> of 00:53:11.280 --> 00:53:11.290 align:start position:0% room we're just like us like a lot of 00:53:11.290 --> 00:53:12.960 align:start position:0% room we're just like us like a lot of you<00:53:11.380> guys<00:53:11.500> are<00:53:11.560> deaf<00:53:11.890> developers<00:53:12.400> like<00:53:12.610> who 00:53:12.960 --> 00:53:12.970 align:start position:0% you guys are deaf developers like who 00:53:12.970 --> 00:53:18.990 align:start position:0% you guys are deaf developers like who here<00:53:13.510> needs<00:53:13.930> access<00:53:14.770> to<00:53:16.200> logs<00:53:17.200> from<00:53:18.000> beyond 00:53:18.990 --> 00:53:19.000 align:start position:0% here needs access to logs from beyond 00:53:19.000 --> 00:53:21.840 align:start position:0% here needs access to logs from beyond like<00:53:19.410> you<00:53:20.410> know<00:53:20.560> last<00:53:20.950> three<00:53:21.220> months<00:53:21.550> or 00:53:21.840 --> 00:53:21.850 align:start position:0% like you know last three months or 00:53:21.850 --> 00:53:23.940 align:start position:0% like you know last three months or something<00:53:21.970> like<00:53:22.330> who's<00:53:22.960> Depp's<00:53:23.320> actually<00:53:23.770> use 00:53:23.940 --> 00:53:23.950 align:start position:0% something like who's Depp's actually use 00:53:23.950 --> 00:53:26.820 align:start position:0% something like who's Depp's actually use this<00:53:24.160> stuff<00:53:24.780> you<00:53:25.780> can<00:53:25.960> just<00:53:26.140> maybe<00:53:26.380> raise<00:53:26.650> your 00:53:26.820 --> 00:53:26.830 align:start position:0% this stuff you can just maybe raise your 00:53:26.830 --> 00:53:28.770 align:start position:0% this stuff you can just maybe raise your hand<00:53:27.040> if<00:53:27.280> you<00:53:27.430> need<00:53:27.640> access<00:53:27.970> to<00:53:28.300> all<00:53:28.660> the 00:53:28.770 --> 00:53:28.780 align:start position:0% hand if you need access to all the 00:53:28.780 --> 00:53:31.290 align:start position:0% hand if you need access to all the historical<00:53:29.260> stuff<00:53:29.470> I<00:53:29.710> see<00:53:30.220> about<00:53:30.400> 15<00:53:31.000> hands 00:53:31.290 --> 00:53:31.300 align:start position:0% historical stuff I see about 15 hands 00:53:31.300 --> 00:53:33.900 align:start position:0% historical stuff I see about 15 hands yeah<00:53:31.690> so<00:53:32.530> what<00:53:32.680> about<00:53:32.770> transactions<00:53:33.550> who 00:53:33.900 --> 00:53:33.910 align:start position:0% yeah so what about transactions who 00:53:33.910 --> 00:53:36.270 align:start position:0% yeah so what about transactions who snaps<00:53:34.330> use<00:53:34.750> transactions<00:53:35.470> could<00:53:35.770> we<00:53:35.890> also<00:53:36.010> get 00:53:36.270 --> 00:53:36.280 align:start position:0% snaps use transactions could we also get 00:53:36.280 --> 00:53:37.980 align:start position:0% snaps use transactions could we also get some<00:53:36.430> information<00:53:36.970> on<00:53:37.030> why<00:53:37.270> those<00:53:37.570> locks<00:53:37.810> I 00:53:37.980 --> 00:53:37.990 align:start position:0% some information on why those locks I 00:53:37.990 --> 00:53:40.560 align:start position:0% some information on why those locks I don't<00:53:38.170> know<00:53:38.260> maybe<00:53:38.590> because<00:53:39.030> it's<00:53:40.030> cheaper 00:53:40.560 --> 00:53:40.570 align:start position:0% don't know maybe because it's cheaper 00:53:40.570 --> 00:53:43.290 align:start position:0% don't know maybe because it's cheaper yeah<00:53:41.380> but<00:53:42.250> that<00:53:42.610> would<00:53:42.730> actually<00:53:43.030> be<00:53:43.120> a<00:53:43.150> really 00:53:43.290 --> 00:53:43.300 align:start position:0% yeah but that would actually be a really 00:53:43.300 --> 00:53:44.760 align:start position:0% yeah but that would actually be a really interesting<00:53:43.600> question<00:53:43.900> like<00:53:44.260> to<00:53:44.410> a<00:53:44.440> lot<00:53:44.620> of 00:53:44.760 --> 00:53:44.770 align:start position:0% interesting question like to a lot of 00:53:44.770 --> 00:53:46.500 align:start position:0% interesting question like to a lot of client<00:53:45.010> developers<00:53:45.430> like<00:53:45.640> which<00:53:45.850> taps<00:53:46.180> are 00:53:46.500 --> 00:53:46.510 align:start position:0% client developers like which taps are 00:53:46.510 --> 00:53:48.390 align:start position:0% client developers like which taps are like<00:53:46.690> heavy<00:53:47.050> on<00:53:47.200> like<00:53:47.410> actually<00:53:47.830> accessing 00:53:48.390 --> 00:53:48.400 align:start position:0% like heavy on like actually accessing 00:53:48.400 --> 00:53:51.500 align:start position:0% like heavy on like actually accessing transactions<00:53:49.270> like<00:53:49.780> transaction<00:53:50.590> by<00:53:50.890> hashed 00:53:51.500 --> 00:53:51.510 align:start position:0% transactions like transaction by hashed 00:53:51.510 --> 00:53:54.180 align:start position:0% transactions like transaction by hashed transaction<00:53:52.510> by<00:53:52.690> book<00:53:52.930> and<00:53:53.110> index<00:53:53.470> who<00:53:53.770> uses 00:53:54.180 --> 00:53:54.190 align:start position:0% transaction by book and index who uses 00:53:54.190 --> 00:53:57.690 align:start position:0% transaction by book and index who uses those<00:53:55.080> that's<00:53:56.080> really<00:53:56.440> dumb<00:53:56.860> developer<00:53:57.520> is 00:53:57.690 --> 00:53:57.700 align:start position:0% those that's really dumb developer is 00:53:57.700 --> 00:54:00.360 align:start position:0% those that's really dumb developer is there<00:53:58.000> and<00:53:58.180> wants<00:53:58.480> to<00:53:58.510> talk<00:53:58.840> about<00:53:58.870> it<00:53:59.370> please 00:54:00.360 --> 00:54:00.370 align:start position:0% there and wants to talk about it please 00:54:00.370 --> 00:54:01.110 align:start position:0% there and wants to talk about it please come<00:54:00.700> over 00:54:01.110 --> 00:54:01.120 align:start position:0% come over 00:54:01.120 --> 00:54:04.260 align:start position:0% come over instead<00:54:01.690> this<00:54:02.320> circle<00:54:02.860> because<00:54:03.190> this<00:54:03.520> those 00:54:04.260 --> 00:54:04.270 align:start position:0% instead this circle because this those 00:54:04.270 --> 00:54:06.930 align:start position:0% instead this circle because this those mics<00:54:04.570> has<00:54:04.870> a<00:54:04.900> cable<00:54:05.440> so<00:54:05.860> we<00:54:06.130> just<00:54:06.340> come<00:54:06.610> free<00:54:06.790> so 00:54:06.930 --> 00:54:06.940 align:start position:0% mics has a cable so we just come free so 00:54:06.940 --> 00:54:08.670 align:start position:0% mics has a cable so we just come free so just<00:54:07.120> for<00:54:07.240> the<00:54:07.360> record<00:54:07.450> I<00:54:07.720> saw<00:54:07.930> two<00:54:08.140> hands<00:54:08.560> for 00:54:08.670 --> 00:54:08.680 align:start position:0% just for the record I saw two hands for 00:54:08.680 --> 00:54:14.120 align:start position:0% just for the record I saw two hands for the<00:54:08.800> transactions<00:54:10.110> three<00:54:11.110> okay<00:54:12.480> well<00:54:13.480> cool 00:54:14.120 --> 00:54:14.130 align:start position:0% the transactions three okay well cool 00:54:14.130 --> 00:54:16.860 align:start position:0% the transactions three okay well cool okay<00:54:15.130> so<00:54:15.370> not<00:54:15.820> a<00:54:15.850> lot<00:54:16.090> of<00:54:16.210> people<00:54:16.510> you<00:54:16.660> actually 00:54:16.860 --> 00:54:16.870 align:start position:0% okay so not a lot of people you actually 00:54:16.870 --> 00:54:19.170 align:start position:0% okay so not a lot of people you actually use<00:54:17.590> a<00:54:17.620> facility<00:54:18.280> that<00:54:18.310> like<00:54:18.550> access<00:54:18.940> past 00:54:19.170 --> 00:54:19.180 align:start position:0% use a facility that like access past 00:54:19.180 --> 00:54:21.630 align:start position:0% use a facility that like access past transactions<00:54:19.780> is<00:54:19.960> what<00:54:20.110> I<00:54:20.140> mean<00:54:20.320> getting<00:54:20.640> so 00:54:21.630 --> 00:54:21.640 align:start position:0% transactions is what I mean getting so 00:54:21.640 --> 00:54:23.880 align:start position:0% transactions is what I mean getting so from<00:54:21.850> this<00:54:22.000> room<00:54:22.240> from<00:54:22.690> this<00:54:22.870> room<00:54:23.080> it<00:54:23.350> is<00:54:23.500> not 00:54:23.880 --> 00:54:23.890 align:start position:0% from this room from this room it is not 00:54:23.890 --> 00:54:26.190 align:start position:0% from this room from this room it is not me<00:54:24.820> like<00:54:24.940> not<00:54:25.030> representative<00:54:25.660> just<00:54:26.110> to 00:54:26.190 --> 00:54:26.200 align:start position:0% me like not representative just to 00:54:26.200 --> 00:54:27.960 align:start position:0% me like not representative just to expand<00:54:26.560> the<00:54:26.770> reason<00:54:27.100> why<00:54:27.220> Felix<00:54:27.640> was<00:54:27.790> asked 00:54:27.960 --> 00:54:27.970 align:start position:0% expand the reason why Felix was asked 00:54:27.970 --> 00:54:30.210 align:start position:0% expand the reason why Felix was asked actually<00:54:28.300> asking<00:54:28.840> this<00:54:28.930> question<00:54:29.380> so<00:54:29.650> we've 00:54:30.210 --> 00:54:30.220 align:start position:0% actually asking this question so we've 00:54:30.220 --> 00:54:31.740 align:start position:0% actually asking this question so we've been<00:54:30.400> sitting<00:54:30.700> on<00:54:30.790> a<00:54:30.850> new<00:54:31.150> feature<00:54:31.480> for 00:54:31.740 --> 00:54:31.750 align:start position:0% been sitting on a new feature for 00:54:31.750 --> 00:54:35.760 align:start position:0% been sitting on a new feature for example<00:54:32.170> in<00:54:32.260> gas<00:54:32.500> that<00:54:34.020> so<00:54:35.020> currently<00:54:35.350> all 00:54:35.760 --> 00:54:35.770 align:start position:0% example in gas that so currently all 00:54:35.770 --> 00:54:37.200 align:start position:0% example in gas that so currently all fool<00:54:36.220> knows<00:54:36.400> all<00:54:36.580> the<00:54:36.640> theorem<00:54:36.910> who<00:54:37.030> knows 00:54:37.200 --> 00:54:37.210 align:start position:0% fool knows all the theorem who knows 00:54:37.210 --> 00:54:39.270 align:start position:0% fool knows all the theorem who knows maintain<00:54:37.690> an<00:54:37.870> index<00:54:38.260> the<00:54:38.470> transaction<00:54:38.980> index 00:54:39.270 --> 00:54:39.280 align:start position:0% maintain an index the transaction index 00:54:39.280 --> 00:54:41.010 align:start position:0% maintain an index the transaction index that's<00:54:39.460> simply<00:54:39.850> saying<00:54:40.060> that<00:54:40.330> this 00:54:41.010 --> 00:54:41.020 align:start position:0% that's simply saying that this 00:54:41.020 --> 00:54:43.530 align:start position:0% that's simply saying that this transaction<00:54:41.440> hash<00:54:41.860> is<00:54:42.220> located<00:54:43.210> in<00:54:43.330> that 00:54:43.530 --> 00:54:43.540 align:start position:0% transaction hash is located in that 00:54:43.540 --> 00:54:45.450 align:start position:0% transaction hash is located in that block<00:54:43.900> so<00:54:44.140> essentially<00:54:44.680> just<00:54:44.710> the<00:54:45.040> hash<00:54:45.220> to 00:54:45.450 --> 00:54:45.460 align:start position:0% block so essentially just the hash to 00:54:45.460 --> 00:54:48.750 align:start position:0% block so essentially just the hash to block<00:54:45.700> number<00:54:46.030> mapping<00:54:46.420> and<00:54:46.630> it<00:54:47.530> seems<00:54:47.830> like<00:54:48.730> a 00:54:48.750 --> 00:54:48.760 align:start position:0% block number mapping and it seems like a 00:54:48.760 --> 00:54:51.930 align:start position:0% block number mapping and it seems like a stupid<00:54:49.180> cheap<00:54:49.870> thing<00:54:50.370> except<00:54:51.370> when<00:54:51.580> we<00:54:51.700> count 00:54:51.930 --> 00:54:51.940 align:start position:0% stupid cheap thing except when we count 00:54:51.940 --> 00:54:53.130 align:start position:0% stupid cheap thing except when we count that<00:54:52.060> they<00:54:52.180> are<00:54:52.300> five<00:54:52.630> hundred<00:54:52.960> million 00:54:53.130 --> 00:54:53.140 align:start position:0% that they are five hundred million 00:54:53.140 --> 00:54:54.780 align:start position:0% that they are five hundred million transactions<00:54:53.830> it<00:54:53.950> turns<00:54:54.160> out<00:54:54.370> that<00:54:54.550> that's 00:54:54.780 --> 00:54:54.790 align:start position:0% transactions it turns out that that's 00:54:54.790 --> 00:54:57.030 align:start position:0% transactions it turns out that that's 200<00:54:55.180> gigabytes<00:54:55.600> of<00:54:55.720> the<00:54:55.870> sorry<00:54:56.170> 20<00:54:56.680> gigabytes 00:54:57.030 --> 00:54:57.040 align:start position:0% 200 gigabytes of the sorry 20 gigabytes 00:54:57.040 --> 00:54:59.850 align:start position:0% 200 gigabytes of the sorry 20 gigabytes of<00:54:57.190> data<00:54:57.360> so<00:54:58.360> essentially<00:54:58.840> every<00:54:59.140> fu--<00:54:59.650> know 00:54:59.850 --> 00:54:59.860 align:start position:0% of data so essentially every fu-- know 00:54:59.860 --> 00:55:02.070 align:start position:0% of data so essentially every fu-- know this<00:55:00.010> is<00:55:00.160> storing<00:55:00.970> 20<00:55:01.300> gigabytes<00:55:01.630> of<00:55:01.870> data 00:55:02.070 --> 00:55:02.080 align:start position:0% this is storing 20 gigabytes of data 00:55:02.080 --> 00:55:05.180 align:start position:0% this is storing 20 gigabytes of data just<00:55:02.650> to<00:55:02.770> be<00:55:03.010> able<00:55:03.310> to<00:55:03.490> say<00:55:03.940> in<00:55:04.360> which<00:55:04.570> blocks 00:55:05.180 --> 00:55:05.190 align:start position:0% just to be able to say in which blocks 00:55:05.190 --> 00:55:07.880 align:start position:0% just to be able to say in which blocks and<00:55:05.369> transaction<00:55:05.880> is<00:55:06.030> and<00:55:06.720> if<00:55:07.050> full<00:55:07.440> of<00:55:07.470> don't 00:55:07.880 --> 00:55:07.890 align:start position:0% and transaction is and if full of don't 00:55:07.890 --> 00:55:09.710 align:start position:0% and transaction is and if full of don't need<00:55:08.069> it<00:55:08.220> then<00:55:08.400> we<00:55:08.550> can<00:55:08.760> immediately<00:55:08.880> wipe<00:55:09.480> out 00:55:09.710 --> 00:55:09.720 align:start position:0% need it then we can immediately wipe out 00:55:09.720 --> 00:55:12.050 align:start position:0% need it then we can immediately wipe out 20<00:55:10.230> gigs<00:55:10.470> of<00:55:10.680> data<00:55:10.859> that<00:55:11.310> can<00:55:12.030> be 00:55:12.050 --> 00:55:12.060 align:start position:0% 20 gigs of data that can be 00:55:12.060 --> 00:55:14.089 align:start position:0% 20 gigs of data that can be reconstructed<00:55:12.540> at<00:55:13.020> any<00:55:13.170> point<00:55:13.440> in<00:55:13.619> time<00:55:13.650> and 00:55:14.089 --> 00:55:14.099 align:start position:0% reconstructed at any point in time and 00:55:14.099 --> 00:55:17.359 align:start position:0% reconstructed at any point in time and that's<00:55:14.730> the<00:55:15.270> reason<00:55:16.230> Felix's<00:55:16.980> question<00:55:17.280> was 00:55:17.359 --> 00:55:17.369 align:start position:0% that's the reason Felix's question was 00:55:17.369 --> 00:55:18.800 align:start position:0% that's the reason Felix's question was really<00:55:17.579> really<00:55:17.849> good<00:55:18.000> because<00:55:18.150> we<00:55:18.480> always 00:55:18.800 --> 00:55:18.810 align:start position:0% really really good because we always 00:55:18.810 --> 00:55:20.990 align:start position:0% really really good because we always wondered<00:55:19.260> is<00:55:19.500> anyone<00:55:19.920> actually<00:55:20.099> using<00:55:20.670> it<00:55:20.819> or 00:55:20.990 --> 00:55:21.000 align:start position:0% wondered is anyone actually using it or 00:55:21.000 --> 00:55:22.760 align:start position:0% wondered is anyone actually using it or can<00:55:21.180> we<00:55:21.359> wipe<00:55:21.540> it<00:55:21.750> should<00:55:21.990> it<00:55:22.109> be<00:55:22.200> the<00:55:22.349> default 00:55:22.760 --> 00:55:22.770 align:start position:0% can we wipe it should it be the default 00:55:22.770 --> 00:55:24.950 align:start position:0% can we wipe it should it be the default or<00:55:22.950> should<00:55:23.099> it<00:55:23.190> not<00:55:23.310> be<00:55:23.369> default<00:55:24.030> so<00:55:24.810> it's 00:55:24.950 --> 00:55:24.960 align:start position:0% or should it not be default so it's 00:55:24.960 --> 00:55:26.599 align:start position:0% or should it not be default so it's actually<00:55:25.319> really<00:55:25.500> reassuring<00:55:26.160> to<00:55:26.339> see<00:55:26.369> that 00:55:26.599 --> 00:55:26.609 align:start position:0% actually really reassuring to see that 00:55:26.609 --> 00:55:31.280 align:start position:0% actually really reassuring to see that people<00:55:26.760> don't<00:55:27.089> need<00:55:27.420> it<00:55:29.900> yeah<00:55:30.900> come<00:55:31.079> to<00:55:31.200> the 00:55:31.280 --> 00:55:31.290 align:start position:0% people don't need it yeah come to the 00:55:31.290 --> 00:55:36.829 align:start position:0% people don't need it yeah come to the mic<00:55:31.410> right<00:55:31.440> there<00:55:34.910> yeah<00:55:35.910> so<00:55:36.089> I<00:55:36.119> work<00:55:36.690> at 00:55:36.829 --> 00:55:36.839 align:start position:0% mic right there yeah so I work at 00:55:36.839 --> 00:55:38.930 align:start position:0% mic right there yeah so I work at synthetics<00:55:37.560> and<00:55:37.829> so<00:55:38.010> we<00:55:38.160> obviously<00:55:38.369> have 00:55:38.930 --> 00:55:38.940 align:start position:0% synthetics and so we obviously have 00:55:38.940 --> 00:55:40.760 align:start position:0% synthetics and so we obviously have what's<00:55:39.510> like<00:55:39.720> a<00:55:39.750> Dex<00:55:40.079> a<00:55:40.290> bit<00:55:40.410> like<00:55:40.530> your<00:55:40.680> new 00:55:40.760 --> 00:55:40.770 align:start position:0% what's like a Dex a bit like your new 00:55:40.770 --> 00:55:43.309 align:start position:0% what's like a Dex a bit like your new Swami<00:55:41.250> introduce<00:55:41.849> yourself<00:55:42.390> oh<00:55:42.450> hello<00:55:42.839> my 00:55:43.309 --> 00:55:43.319 align:start position:0% Swami introduce yourself oh hello my 00:55:43.319 --> 00:55:46.819 align:start position:0% Swami introduce yourself oh hello my name<00:55:43.470> is<00:55:43.500> Justin<00:55:43.859> Moses<00:55:44.790> and<00:55:45.000> I'm<00:55:45.960> the<00:55:46.170> CTO<00:55:46.440> at 00:55:46.819 --> 00:55:46.829 align:start position:0% name is Justin Moses and I'm the CTO at 00:55:46.829 --> 00:55:49.700 align:start position:0% name is Justin Moses and I'm the CTO at synthetics<00:55:47.460> for<00:55:47.730> a<00:55:47.760> defy<00:55:48.270> app<00:55:48.480> and<00:55:49.470> we<00:55:49.560> do 00:55:49.700 --> 00:55:49.710 align:start position:0% synthetics for a defy app and we do 00:55:49.710 --> 00:55:51.559 align:start position:0% synthetics for a defy app and we do indeed<00:55:50.010> need<00:55:50.040> to<00:55:50.339> know<00:55:50.460> the<00:55:50.790> transactions<00:55:51.420> our 00:55:51.559 --> 00:55:51.569 align:start position:0% indeed need to know the transactions our 00:55:51.569 --> 00:55:53.870 align:start position:0% indeed need to know the transactions our users<00:55:51.810> of<00:55:51.930> ahead<00:55:52.920> of<00:55:53.069> time<00:55:53.400> and<00:55:53.609> adapts 00:55:53.870 --> 00:55:53.880 align:start position:0% users of ahead of time and adapts 00:55:53.880 --> 00:55:55.010 align:start position:0% users of ahead of time and adapts however<00:55:54.240> we<00:55:54.390> have<00:55:54.510> been<00:55:54.540> using<00:55:54.750> something 00:55:55.010 --> 00:55:55.020 align:start position:0% however we have been using something 00:55:55.020 --> 00:55:56.599 align:start position:0% however we have been using something like<00:55:55.319> the<00:55:55.470> graph<00:55:55.650> and<00:55:55.950> that's<00:55:56.130> actually<00:55:56.310> being 00:55:56.599 --> 00:55:56.609 align:start position:0% like the graph and that's actually being 00:55:56.609 --> 00:55:59.030 align:start position:0% like the graph and that's actually being successful<00:55:57.510> so<00:55:57.540> we're<00:55:58.500> happy<00:55:58.619> to<00:55:58.859> use 00:55:59.030 --> 00:55:59.040 align:start position:0% successful so we're happy to use 00:55:59.040 --> 00:56:00.530 align:start position:0% successful so we're happy to use decentralized<00:55:59.670> services<00:56:00.030> like<00:56:00.180> that<00:56:00.210> that 00:56:00.530 --> 00:56:00.540 align:start position:0% decentralized services like that that 00:56:00.540 --> 00:56:02.960 align:start position:0% decentralized services like that that can<00:56:00.630> track<00:56:00.869> all<00:56:00.900> our<00:56:01.140> transactions<00:56:01.970> instead 00:56:02.960 --> 00:56:02.970 align:start position:0% can track all our transactions instead 00:56:02.970 --> 00:56:05.630 align:start position:0% can track all our transactions instead of<00:56:03.060> having<00:56:03.210> to<00:56:03.390> do<00:56:03.510> like<00:56:03.900> yeah<00:56:04.349> point<00:56:05.280> go<00:56:05.460> back 00:56:05.630 --> 00:56:05.640 align:start position:0% of having to do like yeah point go back 00:56:05.640 --> 00:56:08.089 align:start position:0% of having to do like yeah point go back and<00:56:05.849> look<00:56:05.970> at<00:56:06.089> individual<00:56:06.900> one<00:56:07.020> so<00:56:07.800> I<00:56:07.859> guess 00:56:08.089 --> 00:56:08.099 align:start position:0% and look at individual one so I guess 00:56:08.099 --> 00:56:09.770 align:start position:0% and look at individual one so I guess what<00:56:08.250> I'm<00:56:08.369> hearing<00:56:08.700> is<00:56:08.819> that<00:56:09.000> actually<00:56:09.510> all 00:56:09.770 --> 00:56:09.780 align:start position:0% what I'm hearing is that actually all 00:56:09.780 --> 00:56:11.329 align:start position:0% what I'm hearing is that actually all the<00:56:09.900> people<00:56:10.170> who<00:56:10.319> might<00:56:10.560> actually<00:56:10.890> want 00:56:11.329 --> 00:56:11.339 align:start position:0% the people who might actually want 00:56:11.339 --> 00:56:13.160 align:start position:0% the people who might actually want access<00:56:11.670> to<00:56:11.849> transactions<00:56:12.510> will<00:56:12.630> totally<00:56:13.050> be 00:56:13.160 --> 00:56:13.170 align:start position:0% access to transactions will totally be 00:56:13.170 --> 00:56:15.230 align:start position:0% access to transactions will totally be fine<00:56:13.440> -<00:56:13.619> like<00:56:13.800> externalizing<00:56:14.700> that<00:56:14.849> to<00:56:15.030> some 00:56:15.230 --> 00:56:15.240 align:start position:0% fine - like externalizing that to some 00:56:15.240 --> 00:56:17.930 align:start position:0% fine - like externalizing that to some service<00:56:15.480> provider<00:56:15.930> because<00:56:16.500> it<00:56:16.800> is<00:56:17.010> it's<00:56:17.819> not 00:56:17.930 --> 00:56:17.940 align:start position:0% service provider because it is it's not 00:56:17.940 --> 00:56:20.450 align:start position:0% service provider because it is it's not really<00:56:18.119> something<00:56:18.560> anyone<00:56:19.560> like<00:56:19.950> a<00:56:20.190> lot<00:56:20.430> of 00:56:20.450 --> 00:56:20.460 align:start position:0% really something anyone like a lot of 00:56:20.460 --> 00:56:22.069 align:start position:0% really something anyone like a lot of people<00:56:20.670> expect<00:56:21.150> from<00:56:21.210> the<00:56:21.420> node<00:56:21.569> to<00:56:21.780> like<00:56:21.930> do 00:56:22.069 --> 00:56:22.079 align:start position:0% people expect from the node to like do 00:56:22.079 --> 00:56:23.990 align:start position:0% people expect from the node to like do for<00:56:22.319> them<00:56:22.440> to<00:56:22.740> like<00:56:22.890> get<00:56:23.130> the<00:56:23.280> transaction<00:56:23.609> I 00:56:23.990 --> 00:56:24.000 align:start position:0% for them to like get the transaction I 00:56:24.000 --> 00:56:25.520 align:start position:0% for them to like get the transaction I think<00:56:24.240> a<00:56:24.270> cost<00:56:24.540> you<00:56:24.690> would<00:56:24.780> have<00:56:24.930> like<00:56:25.109> rewrite 00:56:25.520 --> 00:56:25.530 align:start position:0% think a cost you would have like rewrite 00:56:25.530 --> 00:56:28.640 align:start position:0% think a cost you would have like rewrite their<00:56:25.740> stuff<00:56:26.069> but<00:56:26.430> I<00:56:26.640> mean<00:56:27.109> know<00:56:28.109> that's<00:56:28.380> what 00:56:28.640 --> 00:56:28.650 align:start position:0% their stuff but I mean know that's what 00:56:28.650 --> 00:56:33.770 align:start position:0% their stuff but I mean know that's what I<00:56:28.800> thought<00:56:28.920> they<00:56:29.010> were<00:56:29.130> log<00:56:29.339> heavy<00:56:32.780> crypto 00:56:33.770 --> 00:56:33.780 align:start position:0% I thought they were log heavy crypto 00:56:33.780 --> 00:56:36.140 align:start position:0% I thought they were log heavy crypto economic<00:56:34.290> light<00:56:34.530> client<00:56:35.010> implemented<00:56:35.819> then 00:56:36.140 --> 00:56:36.150 align:start position:0% economic light client implemented then 00:56:36.150 --> 00:56:38.780 align:start position:0% economic light client implemented then they<00:56:36.300> could<00:56:36.569> just<00:56:36.900> like<00:56:37.170> replace<00:56:38.160> one<00:56:38.490> two<00:56:38.640> to 00:56:38.780 --> 00:56:38.790 align:start position:0% they could just like replace one two to 00:56:38.790 --> 00:56:40.700 align:start position:0% they could just like replace one two to one<00:56:39.089> the<00:56:39.119> two<00:56:39.420> lines<00:56:39.660> of<00:56:39.869> code<00:56:40.109> and<00:56:40.470> it<00:56:40.589> would 00:56:40.700 --> 00:56:40.710 align:start position:0% one the two lines of code and it would 00:56:40.710 --> 00:56:42.200 align:start position:0% one the two lines of code and it would just<00:56:40.859> work<00:56:40.950> as<00:56:41.220> is<00:56:41.430> and<00:56:41.730> it<00:56:41.940> would<00:56:42.030> probably 00:56:42.200 --> 00:56:42.210 align:start position:0% just work as is and it would probably 00:56:42.210 --> 00:56:43.930 align:start position:0% just work as is and it would probably work<00:56:42.450> even<00:56:42.750> faster<00:56:42.930> than<00:56:43.290> today 00:56:43.930 --> 00:56:43.940 align:start position:0% work even faster than today 00:56:43.940 --> 00:56:47.270 align:start position:0% work even faster than today but<00:56:44.940> I<00:56:45.060> was<00:56:45.450> just<00:56:45.630> Paulo<00:56:45.990> question<00:56:46.440> for<00:56:46.560> you<00:56:46.650> on 00:56:47.270 --> 00:56:47.280 align:start position:0% but I was just Paulo question for you on 00:56:47.280 --> 00:56:49.490 align:start position:0% but I was just Paulo question for you on the<00:56:47.369> deef<00:56:47.550> i<00:56:47.730> thing<00:56:48.000> we<00:56:48.569> look<00:56:48.780> up<00:56:48.869> transactions 00:56:49.490 --> 00:56:49.500 align:start position:0% the deef i thing we look up transactions 00:56:49.500 --> 00:56:53.120 align:start position:0% the deef i thing we look up transactions don't<00:56:50.400> is<00:56:51.390> that<00:56:51.690> ancient<00:56:52.020> transactions<00:56:52.859> or<00:56:53.040> is 00:56:53.120 --> 00:56:53.130 align:start position:0% don't is that ancient transactions or is 00:56:53.130 --> 00:56:55.069 align:start position:0% don't is that ancient transactions or is the<00:56:53.220> transactions<00:56:53.790> for<00:56:53.970> the<00:56:54.030> last<00:56:54.180> week<00:56:54.450> month 00:56:55.069 --> 00:56:55.079 align:start position:0% the transactions for the last week month 00:56:55.079 --> 00:56:56.930 align:start position:0% the transactions for the last week month will<00:56:55.650> have<00:56:55.770> all<00:56:56.040> of<00:56:56.190> them<00:56:56.310> so<00:56:56.490> over<00:56:56.670> time<00:56:56.790> so 00:56:56.930 --> 00:56:56.940 align:start position:0% will have all of them so over time so 00:56:56.940 --> 00:56:58.579 align:start position:0% will have all of them so over time so we're<00:56:57.060> gonna<00:56:57.180> go<00:56:57.300> back<00:56:57.450> to<00:56:57.630> look<00:56:57.839> at<00:56:57.960> even<00:56:58.319> you 00:56:58.579 --> 00:56:58.589 align:start position:0% we're gonna go back to look at even you 00:56:58.589 --> 00:57:04.069 align:start position:0% we're gonna go back to look at even you know<00:56:58.680> years<00:56:59.010> worth<00:57:01.010> interesting<00:57:02.540> I<00:57:03.540> want<00:57:03.930> to 00:57:04.069 --> 00:57:04.079 align:start position:0% know years worth interesting I want to 00:57:04.079 --> 00:57:05.180 align:start position:0% know years worth interesting I want to throw<00:57:04.200> this<00:57:04.319> out<00:57:04.440> there<00:57:04.650> real<00:57:04.800> quick<00:57:04.980> we're 00:57:05.180 --> 00:57:05.190 align:start position:0% throw this out there real quick we're 00:57:05.190 --> 00:57:07.370 align:start position:0% throw this out there real quick we're about<00:57:05.579> out<00:57:05.640> of<00:57:05.849> time<00:57:06.000> right<00:57:06.690> what's<00:57:07.079> it<00:57:07.230> worth 00:57:07.370 --> 00:57:07.380 align:start position:0% about out of time right what's it worth 00:57:07.380 --> 00:57:10.910 align:start position:0% about out of time right what's it worth three<00:57:07.740> minutes<00:57:08.040> yes<00:57:08.280> yeah<00:57:08.819> so<00:57:09.109> I<00:57:10.109> personally 00:57:10.910 --> 00:57:10.920 align:start position:0% three minutes yes yeah so I personally 00:57:10.920 --> 00:57:13.370 align:start position:0% three minutes yes yeah so I personally think<00:57:11.160> eath<00:57:11.640> 1x<00:57:12.089> eath<00:57:12.359> 1.0<00:57:12.990> is<00:57:13.140> getting 00:57:13.370 --> 00:57:13.380 align:start position:0% think eath 1x eath 1.0 is getting 00:57:13.380 --> 00:57:15.839 align:start position:0% think eath 1x eath 1.0 is getting stronger<00:57:13.770> there<00:57:14.339> was<00:57:14.520> a<00:57:14.550> period<00:57:14.940> of<00:57:15.210> kind<00:57:15.569> of 00:57:15.839 --> 00:57:15.849 align:start position:0% stronger there was a period of kind of 00:57:15.849 --> 00:57:18.630 align:start position:0% stronger there was a period of kind of you<00:57:16.630> know<00:57:16.749> eath<00:57:16.930> 2.0<00:57:17.529> is<00:57:17.589> the<00:57:17.829> the<00:57:18.130> new<00:57:18.279> stuff 00:57:18.630 --> 00:57:18.640 align:start position:0% you know eath 2.0 is the the new stuff 00:57:18.640 --> 00:57:21.660 align:start position:0% you know eath 2.0 is the the new stuff and<00:57:19.150> it's<00:57:19.269> sexier<00:57:19.930> and<00:57:20.229> stuff<00:57:20.470> like<00:57:20.680> that<00:57:20.950> but 00:57:21.660 --> 00:57:21.670 align:start position:0% and it's sexier and stuff like that but 00:57:21.670 --> 00:57:25.170 align:start position:0% and it's sexier and stuff like that but uh<00:57:21.729> now<00:57:22.720> it's<00:57:23.200> like<00:57:23.470> the<00:57:24.130> theorem<00:57:24.579> foundation 00:57:25.170 --> 00:57:25.180 align:start position:0% uh now it's like the theorem foundation 00:57:25.180 --> 00:57:27.599 align:start position:0% uh now it's like the theorem foundation has<00:57:25.749> dedicated<00:57:25.989> at<00:57:26.559> least<00:57:26.950> eight<00:57:27.220> million 00:57:27.599 --> 00:57:27.609 align:start position:0% has dedicated at least eight million 00:57:27.609 --> 00:57:31.589 align:start position:0% has dedicated at least eight million dollars<00:57:28.029> to<00:57:28.450> eath<00:57:28.749> 1.0<00:57:29.499> and<00:57:29.859> 1x<00:57:30.599> research 00:57:31.589 --> 00:57:31.599 align:start position:0% dollars to eath 1.0 and 1x research 00:57:31.599 --> 00:57:34.589 align:start position:0% dollars to eath 1.0 and 1x research development<00:57:32.170> etc<00:57:32.259> and<00:57:32.979> that<00:57:33.700> is<00:57:33.880> being<00:57:34.180> spun 00:57:34.589 --> 00:57:34.599 align:start position:0% development etc and that is being spun 00:57:34.599 --> 00:57:36.569 align:start position:0% development etc and that is being spun up<00:57:34.779> they<00:57:34.989> did<00:57:35.109> that<00:57:35.200> back<00:57:35.380> in<00:57:35.410> May<00:57:35.769> to<00:57:36.369> do<00:57:36.489> it 00:57:36.569 --> 00:57:36.579 align:start position:0% up they did that back in May to do it 00:57:36.579 --> 00:57:38.099 align:start position:0% up they did that back in May to do it for<00:57:36.729> the<00:57:36.789> next<00:57:36.910> year<00:57:37.089> and<00:57:37.479> there<00:57:37.690> are<00:57:37.809> teams 00:57:38.099 --> 00:57:38.109 align:start position:0% for the next year and there are teams 00:57:38.109 --> 00:57:40.079 align:start position:0% for the next year and there are teams being<00:57:38.410> spun<00:57:38.739> up<00:57:38.890> as<00:57:39.039> we<00:57:39.190> speak<00:57:39.369> coordinators 00:57:40.079 --> 00:57:40.089 align:start position:0% being spun up as we speak coordinators 00:57:40.089 --> 00:57:42.569 align:start position:0% being spun up as we speak coordinators being<00:57:40.329> spun<00:57:40.599> up<00:57:40.779> as<00:57:40.930> we<00:57:41.049> speak<00:57:41.380> so<00:57:42.130> there's<00:57:42.489> a 00:57:42.569 --> 00:57:42.579 align:start position:0% being spun up as we speak so there's a 00:57:42.579 --> 00:57:44.430 align:start position:0% being spun up as we speak so there's a lot<00:57:43.150> of<00:57:43.269> good<00:57:43.390> stuff<00:57:43.599> happening<00:57:43.809> as<00:57:44.229> some<00:57:44.349> of 00:57:44.430 --> 00:57:44.440 align:start position:0% lot of good stuff happening as some of 00:57:44.440 --> 00:57:45.779 align:start position:0% lot of good stuff happening as some of it's<00:57:44.559> happening<00:57:44.680> in<00:57:44.950> the<00:57:45.009> background<00:57:45.489> a<00:57:45.640> lot 00:57:45.779 --> 00:57:45.789 align:start position:0% it's happening in the background a lot 00:57:45.789 --> 00:57:46.950 align:start position:0% it's happening in the background a lot of<00:57:45.880> it<00:57:45.999> you're<00:57:46.089> gonna<00:57:46.150> see<00:57:46.420> in<00:57:46.509> the<00:57:46.539> forefront 00:57:46.950 --> 00:57:46.960 align:start position:0% of it you're gonna see in the forefront 00:57:46.960 --> 00:57:51.630 align:start position:0% of it you're gonna see in the forefront real<00:57:47.319> soon<00:57:48.119> you've<00:57:49.119> won<00:57:49.359> forever<00:57:49.829> yeah<00:57:50.859> wait 00:57:51.630 --> 00:57:51.640 align:start position:0% real soon you've won forever yeah wait 00:57:51.640 --> 00:57:53.069 align:start position:0% real soon you've won forever yeah wait but<00:57:51.940> is<00:57:52.029> it<00:57:52.150> really<00:57:52.329> gonna<00:57:52.420> be<00:57:52.569> forever<00:57:52.749> that's 00:57:53.069 --> 00:57:53.079 align:start position:0% but is it really gonna be forever that's 00:57:53.079 --> 00:57:54.960 align:start position:0% but is it really gonna be forever that's actually<00:57:53.440> the<00:57:53.589> next<00:57:53.890> topic<00:57:54.220> eath<00:57:54.579> one-day 00:57:54.960 --> 00:57:54.970 align:start position:0% actually the next topic eath one-day 00:57:54.970 --> 00:58:00.479 align:start position:0% actually the next topic eath one-day into<00:57:55.599> transition<00:57:58.380> just<00:57:59.380> one<00:57:59.799> last<00:58:00.009> one<00:58:00.339> last 00:58:00.479 --> 00:58:00.489 align:start position:0% into transition just one last one last 00:58:00.489 --> 00:58:03.329 align:start position:0% into transition just one last one last bit<00:58:00.789> about<00:58:00.970> that<00:58:01.180> I<00:58:01.509> mean<00:58:01.960> oh<00:58:02.140> he's<00:58:02.710> gone<00:58:02.890> but 00:58:03.329 --> 00:58:03.339 align:start position:0% bit about that I mean oh he's gone but 00:58:03.339 --> 00:58:05.219 align:start position:0% bit about that I mean oh he's gone but the<00:58:03.460> guy<00:58:03.579> was<00:58:03.729> just<00:58:03.759> standing<00:58:04.150> there<00:58:04.210> had<00:58:05.079> like 00:58:05.219 --> 00:58:05.229 align:start position:0% the guy was just standing there had like 00:58:05.229 --> 00:58:10.890 align:start position:0% the guy was just standing there had like some<00:58:05.410> pretty<00:58:08.729> but<00:58:09.729> just<00:58:09.880> like<00:58:10.029> in<00:58:10.239> general<00:58:10.450> I 00:58:10.890 --> 00:58:10.900 align:start position:0% some pretty but just like in general I 00:58:10.900 --> 00:58:12.839 align:start position:0% some pretty but just like in general I think<00:58:11.140> like<00:58:11.349> that<00:58:11.859> developers<00:58:12.430> if<00:58:12.579> you<00:58:12.700> have 00:58:12.839 --> 00:58:12.849 align:start position:0% think like that developers if you have 00:58:12.849 --> 00:58:15.359 align:start position:0% think like that developers if you have like<00:58:13.029> these<00:58:13.210> peculiar<00:58:13.779> use<00:58:14.170> cases<00:58:14.440> trying<00:58:15.099> I 00:58:15.359 --> 00:58:15.369 align:start position:0% like these peculiar use cases trying I 00:58:15.369 --> 00:58:17.160 align:start position:0% like these peculiar use cases trying I don't<00:58:15.549> know<00:58:15.609> like<00:58:16.239> on<00:58:16.390> eat<00:58:16.569> magicians<00:58:17.049> or 00:58:17.160 --> 00:58:17.170 align:start position:0% don't know like on eat magicians or 00:58:17.170 --> 00:58:18.630 align:start position:0% don't know like on eat magicians or somewhere<00:58:17.470> like<00:58:17.499> that<00:58:17.619> they<00:58:18.249> try<00:58:18.460> and<00:58:18.519> like 00:58:18.630 --> 00:58:18.640 align:start position:0% somewhere like that they try and like 00:58:18.640 --> 00:58:20.759 align:start position:0% somewhere like that they try and like explain<00:58:19.089> like<00:58:19.720> answer<00:58:20.019> those<00:58:20.170> questions<00:58:20.529> and 00:58:20.759 --> 00:58:20.769 align:start position:0% explain like answer those questions and 00:58:20.769 --> 00:58:22.499 align:start position:0% explain like answer those questions and like<00:58:20.890> oh<00:58:21.130> are<00:58:21.609> DAP<00:58:21.789> is<00:58:21.969> like<00:58:22.119> kind<00:58:22.329> of<00:58:22.359> weird 00:58:22.499 --> 00:58:22.509 align:start position:0% like oh are DAP is like kind of weird 00:58:22.509 --> 00:58:24.839 align:start position:0% like oh are DAP is like kind of weird because<00:58:22.749> it<00:58:23.019> uses<00:58:23.200> logs<00:58:23.859> in<00:58:24.069> this<00:58:24.190> way<00:58:24.400> and<00:58:24.700> and 00:58:24.839 --> 00:58:24.849 align:start position:0% because it uses logs in this way and and 00:58:24.849 --> 00:58:26.819 align:start position:0% because it uses logs in this way and and we'd<00:58:25.299> like<00:58:25.479> the<00:58:25.630> note<00:58:25.809> to<00:58:26.019> do<00:58:26.170> that<00:58:26.319> or<00:58:26.559> not<00:58:26.589> do 00:58:26.819 --> 00:58:26.829 align:start position:0% we'd like the note to do that or not do 00:58:26.829 --> 00:58:28.469 align:start position:0% we'd like the note to do that or not do that<00:58:26.979> like<00:58:27.609> if<00:58:27.819> they<00:58:27.969> were<00:58:28.029> like<00:58:28.269> eath 00:58:28.469 --> 00:58:28.479 align:start position:0% that like if they were like eath 00:58:28.479 --> 00:58:30.390 align:start position:0% that like if they were like eath magician<00:58:28.960> supposed<00:58:29.440> you<00:58:29.979> know<00:58:30.009> kind<00:58:30.339> of 00:58:30.390 --> 00:58:30.400 align:start position:0% magician supposed you know kind of 00:58:30.400 --> 00:58:32.279 align:start position:0% magician supposed you know kind of either<00:58:30.999> complaining<00:58:31.660> you're<00:58:31.809> requesting 00:58:32.279 --> 00:58:32.289 align:start position:0% either complaining you're requesting 00:58:32.289 --> 00:58:33.900 align:start position:0% either complaining you're requesting features<00:58:32.619> I<00:58:32.859> think<00:58:33.160> that<00:58:33.400> would<00:58:33.489> be<00:58:33.579> pretty 00:58:33.900 --> 00:58:33.910 align:start position:0% features I think that would be pretty 00:58:33.910 --> 00:58:35.999 align:start position:0% features I think that would be pretty useful<00:58:33.999> I<00:58:34.390> mean<00:58:34.569> like<00:58:34.719> one<00:58:35.619> five<00:58:35.829> of<00:58:35.979> nine 00:58:35.999 --> 00:58:36.009 align:start position:0% useful I mean like one five of nine 00:58:36.009 --> 00:58:37.589 align:start position:0% useful I mean like one five of nine right<00:58:36.489> was<00:58:36.670> like<00:58:36.880> one<00:58:37.029> I<00:58:37.059> was<00:58:37.269> very<00:58:37.420> interested 00:58:37.589 --> 00:58:37.599 align:start position:0% right was like one I was very interested 00:58:37.599 --> 00:58:39.299 align:start position:0% right was like one I was very interested in<00:58:37.869> already<00:58:38.049> right<00:58:38.289> and<00:58:38.469> it's<00:58:38.589> imagine<00:58:39.069> a<00:58:39.160> lot 00:58:39.299 --> 00:58:39.309 align:start position:0% in already right and it's imagine a lot 00:58:39.309 --> 00:58:40.950 align:start position:0% in already right and it's imagine a lot of<00:58:39.339> DOC<00:58:39.519> development<00:58:40.119> care<00:58:40.329> a<00:58:40.359> lot<00:58:40.569> about<00:58:40.630> that 00:58:40.950 --> 00:58:40.960 align:start position:0% of DOC development care a lot about that 00:58:40.960 --> 00:58:43.380 align:start position:0% of DOC development care a lot about that because<00:58:41.049> gasses<00:58:41.640> you<00:58:42.640> know<00:58:42.700> lifeblood<00:58:43.269> and 00:58:43.380 --> 00:58:43.390 align:start position:0% because gasses you know lifeblood and 00:58:43.390 --> 00:58:45.299 align:start position:0% because gasses you know lifeblood and having<00:58:43.809> the<00:58:43.900> form<00:58:44.650> to<00:58:44.769> be<00:58:44.799> able<00:58:44.890> to<00:58:44.979> talk<00:58:45.069> about 00:58:45.299 --> 00:58:45.309 align:start position:0% having the form to be able to talk about 00:58:45.309 --> 00:58:46.859 align:start position:0% having the form to be able to talk about that<00:58:45.460> because<00:58:45.579> don't<00:58:46.239> really<00:58:46.509> want<00:58:46.660> to<00:58:46.690> jump 00:58:46.859 --> 00:58:46.869 align:start position:0% that because don't really want to jump 00:58:46.869 --> 00:58:48.239 align:start position:0% that because don't really want to jump in<00:58:47.019> on<00:58:47.109> AI<00:58:47.289> pay<00:58:47.589> unless<00:58:47.769> I<00:58:47.950> have<00:58:48.039> something 00:58:48.239 --> 00:58:48.249 align:start position:0% in on AI pay unless I have something 00:58:48.249 --> 00:58:50.459 align:start position:0% in on AI pay unless I have something yeah<00:58:48.910> you<00:58:49.150> know<00:58:49.210> meaningful<00:58:49.599> to<00:58:49.690> say<00:58:49.869> I<00:58:50.079> think 00:58:50.459 --> 00:58:50.469 align:start position:0% yeah you know meaningful to say I think 00:58:50.469 --> 00:58:52.019 align:start position:0% yeah you know meaningful to say I think so<00:58:50.589> I<00:58:50.619> feel<00:58:50.799> like<00:58:50.829> youth<00:58:51.279> magicians<00:58:51.729> it's<00:58:51.880> kind 00:58:52.019 --> 00:58:52.029 align:start position:0% so I feel like youth magicians it's kind 00:58:52.029 --> 00:58:54.329 align:start position:0% so I feel like youth magicians it's kind of<00:58:52.150> more<00:58:52.329> general<00:58:52.749> less<00:58:53.019> formal<00:58:53.769> forum<00:58:54.160> where 00:58:54.329 --> 00:58:54.339 align:start position:0% of more general less formal forum where 00:58:54.339 --> 00:58:56.400 align:start position:0% of more general less formal forum where you<00:58:54.430> can<00:58:54.460> just<00:58:54.759> kind<00:58:54.940> of<00:58:55.029> write<00:58:55.569> a<00:58:55.599> post<00:58:56.200> and 00:58:56.400 --> 00:58:56.410 align:start position:0% you can just kind of write a post and 00:58:56.410 --> 00:59:05.300 align:start position:0% you can just kind of write a post and people<00:58:56.650> will<00:58:56.769> see<00:58:56.890> it<00:58:56.979> yeah 00:59:05.300 --> 00:59:05.310 align:start position:0% 00:59:05.310 --> 00:59:07.370 align:start position:0% you