WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:20.450 align:start position:0% [Music] 00:00:20.450 --> 00:00:20.460 align:start position:0% 00:00:20.460 --> 00:00:23.970 align:start position:0% hello<00:00:21.460> everyone<00:00:22.050> my<00:00:23.050> name<00:00:23.169> is<00:00:23.230> Jack<00:00:23.619> Peterson 00:00:23.970 --> 00:00:23.980 align:start position:0% hello everyone my name is Jack Peterson 00:00:23.980 --> 00:00:28.079 align:start position:0% hello everyone my name is Jack Peterson I'm<00:00:24.460> the<00:00:24.849> lead<00:00:25.119> developer<00:00:25.689> of<00:00:26.189> auger<00:00:27.189> but<00:00:27.909> I'm 00:00:28.079 --> 00:00:28.089 align:start position:0% I'm the lead developer of auger but I'm 00:00:28.089 --> 00:00:30.239 align:start position:0% I'm the lead developer of auger but I'm actually<00:00:28.269> not<00:00:28.710> really<00:00:29.710> going<00:00:29.829> to<00:00:29.919> be<00:00:30.009> talking 00:00:30.239 --> 00:00:30.249 align:start position:0% actually not really going to be talking 00:00:30.249 --> 00:00:34.770 align:start position:0% actually not really going to be talking about<00:00:30.809> auger<00:00:31.809> today<00:00:33.390> instead<00:00:34.390> I'm<00:00:34.540> gonna<00:00:34.660> be 00:00:34.770 --> 00:00:34.780 align:start position:0% about auger today instead I'm gonna be 00:00:34.780 --> 00:00:37.710 align:start position:0% about auger today instead I'm gonna be talking<00:00:35.110> about<00:00:36.150> the<00:00:37.150> sort<00:00:37.540> of<00:00:37.570> the<00:00:37.690> general 00:00:37.710 --> 00:00:37.720 align:start position:0% talking about the sort of the general 00:00:37.720 --> 00:00:41.240 align:start position:0% talking about the sort of the general state<00:00:38.380> of<00:00:38.560> tooling<00:00:39.070> in<00:00:39.580> etherium<00:00:40.390> zico<00:00:40.660> system 00:00:41.240 --> 00:00:41.250 align:start position:0% state of tooling in etherium zico system 00:00:41.250 --> 00:00:45.860 align:start position:0% state of tooling in etherium zico system and<00:00:43.380> point<00:00:44.380> out<00:00:44.470> some<00:00:44.680> things<00:00:44.710> that<00:00:44.950> I<00:00:45.070> think 00:00:45.860 --> 00:00:45.870 align:start position:0% and point out some things that I think 00:00:45.870 --> 00:00:51.560 align:start position:0% and point out some things that I think could<00:00:47.370> use<00:00:48.370> some<00:00:48.580> improvement 00:00:51.560 --> 00:00:51.570 align:start position:0% 00:00:51.570 --> 00:00:54.810 align:start position:0% you<00:00:52.570> know<00:00:52.690> auger<00:00:53.020> has<00:00:53.230> been<00:00:53.500> in<00:00:54.040> development 00:00:54.810 --> 00:00:54.820 align:start position:0% you know auger has been in development 00:00:54.820 --> 00:00:59.540 align:start position:0% you know auger has been in development at<00:00:55.240> this<00:00:55.390> point<00:00:55.660> for<00:00:56.790> almost<00:00:57.790> three<00:00:58.060> years<00:00:58.090> and 00:00:59.540 --> 00:00:59.550 align:start position:0% at this point for almost three years and 00:00:59.550 --> 00:01:02.550 align:start position:0% at this point for almost three years and that<00:01:00.550> that's<00:01:00.790> a<00:01:01.030> so<00:01:01.810> long<00:01:02.050> as<00:01:02.260> a<00:01:02.320> long 00:01:02.550 --> 00:01:02.560 align:start position:0% that that's a so long as a long 00:01:02.560 --> 00:01:05.280 align:start position:0% that that's a so long as a long development<00:01:02.800> cycle<00:01:03.329> it's<00:01:04.329> certainly<00:01:05.019> longer 00:01:05.280 --> 00:01:05.290 align:start position:0% development cycle it's certainly longer 00:01:05.290 --> 00:01:09.270 align:start position:0% development cycle it's certainly longer than<00:01:06.329> any<00:01:07.329> of<00:01:07.420> the<00:01:07.630> team<00:01:07.869> who<00:01:08.289> were<00:01:08.499> you<00:01:09.219> know 00:01:09.270 --> 00:01:09.280 align:start position:0% than any of the team who were you know 00:01:09.280 --> 00:01:12.800 align:start position:0% than any of the team who were you know came<00:01:09.520> from<00:01:09.670> backgrounds<00:01:10.210> of<00:01:10.920> web<00:01:11.920> development 00:01:12.800 --> 00:01:12.810 align:start position:0% came from backgrounds of web development 00:01:12.810 --> 00:01:14.849 align:start position:0% came from backgrounds of web development application<00:01:13.810> development<00:01:14.170> scientific 00:01:14.849 --> 00:01:14.859 align:start position:0% application development scientific 00:01:14.859 --> 00:01:18.179 align:start position:0% application development scientific development<00:01:15.369> expected<00:01:15.999> based<00:01:16.329> on<00:01:16.600> their<00:01:17.189> past 00:01:18.179 --> 00:01:18.189 align:start position:0% development expected based on their past 00:01:18.189 --> 00:01:22.469 align:start position:0% development expected based on their past experiences<00:01:18.939> and<00:01:19.539> I<00:01:20.049> think<00:01:21.270> one<00:01:22.270> of<00:01:22.299> the 00:01:22.469 --> 00:01:22.479 align:start position:0% experiences and I think one of the 00:01:22.479 --> 00:01:27.510 align:start position:0% experiences and I think one of the reasons<00:01:22.810> for<00:01:22.869> this<00:01:23.170> is<00:01:23.819> that<00:01:26.159> we<00:01:27.159> all<00:01:27.189> came 00:01:27.510 --> 00:01:27.520 align:start position:0% reasons for this is that we all came 00:01:27.520 --> 00:01:30.539 align:start position:0% reasons for this is that we all came from<00:01:27.899> environments<00:01:28.899> where<00:01:29.439> you<00:01:30.369> know<00:01:30.459> that 00:01:30.539 --> 00:01:30.549 align:start position:0% from environments where you know that 00:01:30.549 --> 00:01:33.510 align:start position:0% from environments where you know that had<00:01:30.670> been<00:01:30.819> established<00:01:31.389> for<00:01:31.569> a<00:01:31.659> while<00:01:31.810> and<00:01:32.520> in 00:01:33.510 --> 00:01:33.520 align:start position:0% had been established for a while and in 00:01:33.520 --> 00:01:34.859 align:start position:0% had been established for a while and in an<00:01:33.639> established<00:01:34.090> development<00:01:34.509> environment 00:01:34.859 --> 00:01:34.869 align:start position:0% an established development environment 00:01:34.869 --> 00:01:36.959 align:start position:0% an established development environment there<00:01:34.990> are<00:01:35.020> certain<00:01:35.319> tools<00:01:35.560> that<00:01:35.829> you<00:01:36.819> just 00:01:36.959 --> 00:01:36.969 align:start position:0% there are certain tools that you just 00:01:36.969 --> 00:01:38.219 align:start position:0% there are certain tools that you just sort<00:01:37.149> of<00:01:37.209> take<00:01:37.389> for<00:01:37.569> granted<00:01:37.630> as<00:01:38.020> being 00:01:38.219 --> 00:01:38.229 align:start position:0% sort of take for granted as being 00:01:38.229 --> 00:01:40.649 align:start position:0% sort of take for granted as being available<00:01:39.090> whereas<00:01:40.090> in<00:01:40.209> a<00:01:40.240> very<00:01:40.450> young 00:01:40.649 --> 00:01:40.659 align:start position:0% available whereas in a very young 00:01:40.659 --> 00:01:42.389 align:start position:0% available whereas in a very young ecosystem<00:01:41.350> like<00:01:41.530> youth<00:01:41.679> areum's<00:01:42.039> they<00:01:42.219> might 00:01:42.389 --> 00:01:42.399 align:start position:0% ecosystem like youth areum's they might 00:01:42.399 --> 00:01:49.830 align:start position:0% ecosystem like youth areum's they might not<00:01:42.549> be<00:01:47.789> it's<00:01:48.789> over<00:01:48.939> the<00:01:49.119> past 00:01:49.830 --> 00:01:49.840 align:start position:0% not be it's over the past 00:01:49.840 --> 00:01:53.340 align:start position:0% not be it's over the past I<00:01:50.009> don't<00:01:51.009> know<00:01:51.069> six<00:01:51.340> months<00:01:51.689> I've<00:01:52.689> spent<00:01:53.289> a 00:01:53.340 --> 00:01:53.350 align:start position:0% I don't know six months I've spent a 00:01:53.350 --> 00:01:57.059 align:start position:0% I don't know six months I've spent a fair<00:01:53.499> amount<00:01:53.560> of<00:01:53.740> time<00:01:54.009> talking<00:01:54.909> to<00:01:56.069> DAP 00:01:57.059 --> 00:01:57.069 align:start position:0% fair amount of time talking to DAP 00:01:57.069 --> 00:02:00.649 align:start position:0% fair amount of time talking to DAP developers<00:01:57.639> on<00:01:57.999> different<00:01:58.659> projects<00:01:59.079> about 00:02:00.649 --> 00:02:00.659 align:start position:0% developers on different projects about 00:02:00.659 --> 00:02:04.980 align:start position:0% developers on different projects about whether<00:02:01.659> they<00:02:03.389> you<00:02:04.389> know<00:02:04.479> what<00:02:04.810> their 00:02:04.980 --> 00:02:04.990 align:start position:0% whether they you know what their 00:02:04.990 --> 00:02:07.529 align:start position:0% whether they you know what their thoughts<00:02:05.200> are<00:02:05.469> on<00:02:05.969> the<00:02:06.969> tooling<00:02:07.329> in<00:02:07.420> the 00:02:07.529 --> 00:02:07.539 align:start position:0% thoughts are on the tooling in the 00:02:07.539 --> 00:02:09.410 align:start position:0% thoughts are on the tooling in the ecosystem<00:02:08.110> and<00:02:08.259> whether<00:02:08.500> or<00:02:08.619> not<00:02:08.679> they<00:02:08.950> are 00:02:09.410 --> 00:02:09.420 align:start position:0% ecosystem and whether or not they are 00:02:09.420 --> 00:02:14.300 align:start position:0% ecosystem and whether or not they are ahead<00:02:10.420> of<00:02:10.509> schedule<00:02:10.600> or<00:02:11.080> behind<00:02:11.470> schedule 00:02:14.300 --> 00:02:14.310 align:start position:0% 00:02:14.310 --> 00:02:16.980 align:start position:0% well<00:02:15.310> I<00:02:15.370> guess<00:02:15.550> you're<00:02:16.300> a<00:02:16.330> lot<00:02:16.599> of<00:02:16.690> you<00:02:16.810> are 00:02:16.980 --> 00:02:16.990 align:start position:0% well I guess you're a lot of you are 00:02:16.990 --> 00:02:18.540 align:start position:0% well I guess you're a lot of you are deaf<00:02:17.260> developers<00:02:17.709> yourselves<00:02:18.190> so<00:02:18.280> I<00:02:18.340> don't 00:02:18.540 --> 00:02:18.550 align:start position:0% deaf developers yourselves so I don't 00:02:18.550 --> 00:02:21.150 align:start position:0% deaf developers yourselves so I don't have<00:02:18.640> to<00:02:18.760> tell<00:02:18.940> you<00:02:19.030> this<00:02:19.180> but<00:02:19.660> the<00:02:20.650> most 00:02:21.150 --> 00:02:21.160 align:start position:0% have to tell you this but the most 00:02:21.160 --> 00:02:23.040 align:start position:0% have to tell you this but the most common<00:02:21.550> answer<00:02:21.670> was<00:02:21.940> definitely<00:02:22.420> Wow 00:02:23.040 --> 00:02:23.050 align:start position:0% common answer was definitely Wow 00:02:23.050 --> 00:02:24.809 align:start position:0% common answer was definitely Wow everything<00:02:23.590> is<00:02:23.709> taking<00:02:24.099> a<00:02:24.190> lot<00:02:24.340> longer<00:02:24.550> than 00:02:24.809 --> 00:02:24.819 align:start position:0% everything is taking a lot longer than 00:02:24.819 --> 00:02:29.430 align:start position:0% everything is taking a lot longer than we<00:02:24.940> expected<00:02:25.950> and<00:02:26.950> I<00:02:27.900> think<00:02:28.900> the<00:02:29.050> reason<00:02:29.410> for 00:02:29.430 --> 00:02:29.440 align:start position:0% we expected and I think the reason for 00:02:29.440 --> 00:02:34.170 align:start position:0% we expected and I think the reason for that<00:02:29.590> is<00:02:29.860> basically<00:02:30.310> just<00:02:30.700> that<00:02:33.090> there's<00:02:34.090> a 00:02:34.170 --> 00:02:34.180 align:start position:0% that is basically just that there's a 00:02:34.180 --> 00:02:37.530 align:start position:0% that is basically just that there's a there's<00:02:34.600> a<00:02:34.660> lack<00:02:34.900> of<00:02:35.880> good<00:02:36.880> consistent 00:02:37.530 --> 00:02:37.540 align:start position:0% there's a lack of good consistent 00:02:37.540 --> 00:02:39.059 align:start position:0% there's a lack of good consistent tooling<00:02:37.900> in<00:02:38.020> this<00:02:38.170> space<00:02:38.440> you<00:02:38.800> know<00:02:38.890> I<00:02:38.920> think 00:02:39.059 --> 00:02:39.069 align:start position:0% tooling in this space you know I think 00:02:39.069 --> 00:02:43.320 align:start position:0% tooling in this space you know I think of<00:02:39.340> tooling<00:02:40.180> as<00:02:41.640> being<00:02:42.640> so<00:02:42.790> important<00:02:43.239> because 00:02:43.320 --> 00:02:43.330 align:start position:0% of tooling as being so important because 00:02:43.330 --> 00:02:46.309 align:start position:0% of tooling as being so important because it's<00:02:43.720> a<00:02:43.810> force<00:02:44.050> multiplier<00:02:44.610> right<00:02:45.610> if<00:02:45.730> I<00:02:45.819> have 00:02:46.309 --> 00:02:46.319 align:start position:0% it's a force multiplier right if I have 00:02:46.319 --> 00:02:49.500 align:start position:0% it's a force multiplier right if I have an<00:02:47.319> ecosystem<00:02:47.800> of<00:02:48.250> thousand<00:02:48.760> developers<00:02:49.209> and 00:02:49.500 --> 00:02:49.510 align:start position:0% an ecosystem of thousand developers and 00:02:49.510 --> 00:02:52.140 align:start position:0% an ecosystem of thousand developers and those<00:02:50.230> thousand<00:02:50.620> developers<00:02:51.040> don't<00:02:51.370> have<00:02:51.640> I 00:02:52.140 --> 00:02:52.150 align:start position:0% those thousand developers don't have I 00:02:52.150 --> 00:02:54.949 align:start position:0% those thousand developers don't have I don't<00:02:52.720> know<00:02:52.810> a<00:02:52.870> debugger<00:02:53.459> all<00:02:54.459> right<00:02:54.549> and<00:02:54.640> then 00:02:54.949 --> 00:02:54.959 align:start position:0% don't know a debugger all right and then 00:02:54.959 --> 00:02:57.539 align:start position:0% don't know a debugger all right and then you<00:02:55.959> sit<00:02:56.620> down<00:02:56.769> you<00:02:56.920> write<00:02:57.040> one<00:02:57.220> you<00:02:57.310> give<00:02:57.430> it 00:02:57.539 --> 00:02:57.549 align:start position:0% you sit down you write one you give it 00:02:57.549 --> 00:03:00.050 align:start position:0% you sit down you write one you give it to<00:02:57.640> them<00:02:57.760> that<00:02:58.450> makes<00:02:58.660> every<00:02:59.620> one<00:02:59.769> of<00:02:59.799> them 00:03:00.050 --> 00:03:00.060 align:start position:0% to them that makes every one of them 00:03:00.060 --> 00:03:02.970 align:start position:0% to them that makes every one of them more<00:03:01.060> efficient<00:03:01.569> right<00:03:01.750> so<00:03:02.709> it<00:03:02.830> has<00:03:02.950> a 00:03:02.970 --> 00:03:02.980 align:start position:0% more efficient right so it has a 00:03:02.980 --> 00:03:05.330 align:start position:0% more efficient right so it has a multiplicative<00:03:03.790> not<00:03:04.030> an<00:03:04.150> additive<00:03:04.450> effect 00:03:05.330 --> 00:03:05.340 align:start position:0% multiplicative not an additive effect 00:03:05.340 --> 00:03:09.390 align:start position:0% multiplicative not an additive effect and<00:03:06.340> I<00:03:07.060> think<00:03:07.090> that<00:03:07.480> the<00:03:07.930> main<00:03:08.080> thing<00:03:08.110> that<00:03:08.860> we 00:03:09.390 --> 00:03:09.400 align:start position:0% and I think that the main thing that we 00:03:09.400 --> 00:03:11.759 align:start position:0% and I think that the main thing that we need<00:03:09.549> in<00:03:09.700> this<00:03:09.790> ecosystem<00:03:10.090> is<00:03:10.510> just<00:03:10.810> is<00:03:11.500> just 00:03:11.759 --> 00:03:11.769 align:start position:0% need in this ecosystem is just is just 00:03:11.769 --> 00:03:17.819 align:start position:0% need in this ecosystem is just is just better<00:03:11.950> tools<00:03:12.310> I<00:03:16.080> think<00:03:17.080> it's<00:03:17.290> worth<00:03:17.410> taking<00:03:17.650> a 00:03:17.819 --> 00:03:17.829 align:start position:0% better tools I think it's worth taking a 00:03:17.829 --> 00:03:21.990 align:start position:0% better tools I think it's worth taking a step<00:03:17.859> back<00:03:18.250> in<00:03:18.280> and<00:03:19.079> examining<00:03:20.640> well<00:03:21.640> why 00:03:21.990 --> 00:03:22.000 align:start position:0% step back in and examining well why 00:03:22.000 --> 00:03:24.060 align:start position:0% step back in and examining well why might<00:03:22.239> there<00:03:22.720> not<00:03:22.870> be<00:03:23.140> good<00:03:23.350> tooling<00:03:23.799> in<00:03:23.920> this 00:03:24.060 --> 00:03:24.070 align:start position:0% might there not be good tooling in this 00:03:24.070 --> 00:03:27.030 align:start position:0% might there not be good tooling in this space<00:03:25.140> and<00:03:26.140> now<00:03:26.260> part<00:03:26.500> of<00:03:26.530> it<00:03:26.620> is<00:03:26.769> just<00:03:26.799> that 00:03:27.030 --> 00:03:27.040 align:start position:0% space and now part of it is just that 00:03:27.040 --> 00:03:30.240 align:start position:0% space and now part of it is just that this<00:03:27.250> is<00:03:27.370> a<00:03:27.400> young<00:03:27.670> space<00:03:28.170> all<00:03:29.170> right<00:03:29.320> so<00:03:29.590> you 00:03:30.240 --> 00:03:30.250 align:start position:0% this is a young space all right so you 00:03:30.250 --> 00:03:32.880 align:start position:0% this is a young space all right so you wouldn't<00:03:30.459> expect<00:03:30.790> it<00:03:30.970> to<00:03:31.180> have<00:03:31.680> you<00:03:32.680> know<00:03:32.769> the 00:03:32.880 --> 00:03:32.890 align:start position:0% wouldn't expect it to have you know the 00:03:32.890 --> 00:03:35.069 align:start position:0% wouldn't expect it to have you know the maturity<00:03:33.370> of<00:03:33.450> desktop<00:03:34.450> application 00:03:35.069 --> 00:03:35.079 align:start position:0% maturity of desktop application 00:03:35.079 --> 00:03:38.430 align:start position:0% maturity of desktop application development<00:03:35.440> tools<00:03:35.590> for<00:03:36.070> example<00:03:37.109> but<00:03:38.109> I<00:03:38.170> also 00:03:38.430 --> 00:03:38.440 align:start position:0% development tools for example but I also 00:03:38.440 --> 00:03:41.310 align:start position:0% development tools for example but I also think<00:03:38.709> that<00:03:38.910> there<00:03:39.910> is<00:03:40.090> sort<00:03:40.690> of<00:03:40.780> a<00:03:40.870> structural 00:03:41.310 --> 00:03:41.320 align:start position:0% think that there is sort of a structural 00:03:41.320 --> 00:03:43.650 align:start position:0% think that there is sort of a structural problem<00:03:41.560> in<00:03:41.890> that<00:03:42.010> there's<00:03:42.329> currently<00:03:43.329> a<00:03:43.420> lack 00:03:43.650 --> 00:03:43.660 align:start position:0% problem in that there's currently a lack 00:03:43.660 --> 00:03:46.229 align:start position:0% problem in that there's currently a lack of<00:03:43.690> incentives<00:03:44.620> to<00:03:45.010> build<00:03:45.190> good<00:03:45.340> tools<00:03:45.579> right 00:03:46.229 --> 00:03:46.239 align:start position:0% of incentives to build good tools right 00:03:46.239 --> 00:03:49.800 align:start position:0% of incentives to build good tools right there's<00:03:46.510> the<00:03:47.640> allure<00:03:48.640> of<00:03:48.670> the<00:03:49.150> doing<00:03:49.690> the 00:03:49.800 --> 00:03:49.810 align:start position:0% there's the allure of the doing the 00:03:49.810 --> 00:03:53.340 align:start position:0% there's the allure of the doing the token<00:03:50.140> sale<00:03:50.350> right<00:03:50.859> and<00:03:51.070> the<00:03:51.160> thing<00:03:51.340> is<00:03:52.350> having 00:03:53.340 --> 00:03:53.350 align:start position:0% token sale right and the thing is having 00:03:53.350 --> 00:03:58.110 align:start position:0% token sale right and the thing is having done<00:03:54.340> a<00:03:54.370> token<00:03:54.790> sale<00:03:56.160> after<00:03:57.160> you<00:03:57.640> do<00:03:57.760> a<00:03:57.790> token 00:03:58.110 --> 00:03:58.120 align:start position:0% done a token sale after you do a token 00:03:58.120 --> 00:04:00.420 align:start position:0% done a token sale after you do a token sale<00:03:58.299> you<00:03:58.510> are<00:03:58.720> committed<00:03:59.500> to<00:03:59.709> delivering<00:04:00.130> on 00:04:00.420 --> 00:04:00.430 align:start position:0% sale you are committed to delivering on 00:04:00.430 --> 00:04:03.000 align:start position:0% sale you are committed to delivering on a<00:04:00.489> particular<00:04:01.420> application<00:04:01.680> right<00:04:02.680> so<00:04:02.950> you 00:04:03.000 --> 00:04:03.010 align:start position:0% a particular application right so you 00:04:03.010 --> 00:04:07.020 align:start position:0% a particular application right so you move<00:04:03.430> at<00:04:03.640> breakneck<00:04:04.269> speed<00:04:04.750> towards<00:04:05.850> MVP<00:04:06.850> for 00:04:07.020 --> 00:04:07.030 align:start position:0% move at breakneck speed towards MVP for 00:04:07.030 --> 00:04:09.750 align:start position:0% move at breakneck speed towards MVP for your<00:04:07.180> application<00:04:07.750> and<00:04:07.930> I<00:04:07.989> think<00:04:08.230> that<00:04:08.440> a<00:04:08.760> lot 00:04:09.750 --> 00:04:09.760 align:start position:0% your application and I think that a lot 00:04:09.760 --> 00:04:11.520 align:start position:0% your application and I think that a lot of<00:04:09.790> the<00:04:10.030> best<00:04:10.209> minds<00:04:10.630> in<00:04:10.840> this<00:04:10.989> space<00:04:11.260> are 00:04:11.520 --> 00:04:11.530 align:start position:0% of the best minds in this space are 00:04:11.530 --> 00:04:18.990 align:start position:0% of the best minds in this space are doing<00:04:11.920> exactly<00:04:12.790> that<00:04:14.130> and<00:04:15.130> I<00:04:15.670> think<00:04:15.940> that<00:04:18.000> if 00:04:18.990 --> 00:04:19.000 align:start position:0% doing exactly that and I think that if 00:04:19.000 --> 00:04:20.279 align:start position:0% doing exactly that and I think that if you<00:04:19.150> stop<00:04:19.329> and<00:04:19.479> think<00:04:19.600> about<00:04:19.690> how<00:04:19.930> tooling 00:04:20.279 --> 00:04:20.289 align:start position:0% you stop and think about how tooling 00:04:20.289 --> 00:04:22.670 align:start position:0% you stop and think about how tooling does<00:04:20.500> have<00:04:20.709> a<00:04:20.739> multiplicative<00:04:21.400> effect 00:04:22.670 --> 00:04:22.680 align:start position:0% does have a multiplicative effect 00:04:22.680 --> 00:04:25.070 align:start position:0% does have a multiplicative effect that<00:04:23.280> we<00:04:23.490> are<00:04:23.699> all<00:04:23.910> ironically<00:04:24.660> actually 00:04:25.070 --> 00:04:25.080 align:start position:0% that we are all ironically actually 00:04:25.080 --> 00:04:28.700 align:start position:0% that we are all ironically actually moving<00:04:25.410> slower<00:04:25.710> than<00:04:25.830> if<00:04:26.250> we<00:04:27.120> stopped<00:04:27.710> and 00:04:28.700 --> 00:04:28.710 align:start position:0% moving slower than if we stopped and 00:04:28.710 --> 00:04:31.969 align:start position:0% moving slower than if we stopped and took<00:04:28.889> a<00:04:28.979> deep<00:04:29.130> breath<00:04:29.340> and<00:04:29.610> all<00:04:30.979> communicated 00:04:31.969 --> 00:04:31.979 align:start position:0% took a deep breath and all communicated 00:04:31.979 --> 00:04:34.310 align:start position:0% took a deep breath and all communicated really<00:04:32.699> well<00:04:32.850> with<00:04:33.000> each<00:04:33.120> other<00:04:33.240> about<00:04:33.750> what 00:04:34.310 --> 00:04:34.320 align:start position:0% really well with each other about what 00:04:34.320 --> 00:04:38.090 align:start position:0% really well with each other about what tools<00:04:35.039> we<00:04:36.030> could<00:04:36.240> share<00:04:36.509> between<00:04:37.100> different 00:04:38.090 --> 00:04:38.100 align:start position:0% tools we could share between different 00:04:38.100 --> 00:04:45.350 align:start position:0% tools we could share between different projects<00:04:40.940> and<00:04:43.370> so<00:04:44.370> to<00:04:44.430> try<00:04:44.669> and<00:04:44.820> address<00:04:45.000> the 00:04:45.350 --> 00:04:45.360 align:start position:0% projects and so to try and address the 00:04:45.360 --> 00:04:48.740 align:start position:0% projects and so to try and address the issue<00:04:45.660> of<00:04:45.930> lack<00:04:46.320> of<00:04:46.500> incentives<00:04:47.330> I'd<00:04:48.330> like<00:04:48.600> to 00:04:48.740 --> 00:04:48.750 align:start position:0% issue of lack of incentives I'd like to 00:04:48.750 --> 00:04:51.950 align:start position:0% issue of lack of incentives I'd like to propose<00:04:48.900> sort<00:04:49.380> of<00:04:49.470> a<00:04:50.300> call<00:04:51.300> to<00:04:51.449> arms<00:04:51.630> if<00:04:51.930> you 00:04:51.950 --> 00:04:51.960 align:start position:0% propose sort of a call to arms if you 00:04:51.960 --> 00:04:56.060 align:start position:0% propose sort of a call to arms if you will<00:04:52.169> I<00:04:52.610> think<00:04:53.610> that<00:04:54.139> DAP<00:04:55.139> teams<00:04:55.470> especially 00:04:56.060 --> 00:04:56.070 align:start position:0% will I think that DAP teams especially 00:04:56.070 --> 00:04:59.029 align:start position:0% will I think that DAP teams especially those<00:04:56.490> of<00:04:56.639> us<00:04:56.729> that<00:04:56.759> have<00:04:57.180> done<00:04:57.870> token<00:04:58.830> sales 00:04:59.029 --> 00:04:59.039 align:start position:0% those of us that have done token sales 00:04:59.039 --> 00:05:02.120 align:start position:0% those of us that have done token sales and<00:04:59.580> we<00:04:59.940> have<00:05:00.090> some<00:05:00.300> resources<00:05:00.780> and<00:05:01.169> we<00:05:01.620> have<00:05:01.830> a 00:05:02.120 --> 00:05:02.130 align:start position:0% and we have some resources and we have a 00:05:02.130 --> 00:05:05.540 align:start position:0% and we have some resources and we have a dire<00:05:03.090> need<00:05:03.120> for<00:05:03.419> better<00:05:03.750> tools<00:05:04.110> I<00:05:04.440> think<00:05:05.370> we 00:05:05.540 --> 00:05:05.550 align:start position:0% dire need for better tools I think we 00:05:05.550 --> 00:05:09.379 align:start position:0% dire need for better tools I think we should<00:05:05.849> create<00:05:06.650> bounties<00:05:07.970> for<00:05:08.970> the<00:05:09.090> tooling 00:05:09.379 --> 00:05:09.389 align:start position:0% should create bounties for the tooling 00:05:09.389 --> 00:05:19.730 align:start position:0% should create bounties for the tooling that<00:05:09.419> we<00:05:09.660> need<00:05:17.810> or<00:05:18.810> we<00:05:18.840> could<00:05:19.080> just<00:05:19.110> commission 00:05:19.730 --> 00:05:19.740 align:start position:0% that we need or we could just commission 00:05:19.740 --> 00:05:22.430 align:start position:0% that we need or we could just commission the<00:05:20.729> tools<00:05:20.970> but<00:05:21.270> bounties<00:05:21.780> and<00:05:21.810> prizes<00:05:22.139> are 00:05:22.430 --> 00:05:22.440 align:start position:0% the tools but bounties and prizes are 00:05:22.440 --> 00:05:24.950 align:start position:0% the tools but bounties and prizes are sort<00:05:22.650> of<00:05:22.710> more<00:05:22.830> fun<00:05:23.099> so<00:05:23.669> I'm<00:05:24.599> gonna<00:05:24.720> go<00:05:24.840> with 00:05:24.950 --> 00:05:24.960 align:start position:0% sort of more fun so I'm gonna go with 00:05:24.960 --> 00:05:35.300 align:start position:0% sort of more fun so I'm gonna go with that<00:05:29.630> okay<00:05:30.630> so<00:05:30.659> I<00:05:32.570> had<00:05:33.570> I<00:05:33.870> have<00:05:34.020> had<00:05:34.409> a<00:05:34.440> bunch<00:05:35.220> of 00:05:35.300 --> 00:05:35.310 align:start position:0% that okay so I had I have had a bunch of 00:05:35.310 --> 00:05:37.760 align:start position:0% that okay so I had I have had a bunch of long<00:05:35.490> conversations<00:05:35.669> with<00:05:36.210> my<00:05:36.840> smart 00:05:37.760 --> 00:05:37.770 align:start position:0% long conversations with my smart 00:05:37.770 --> 00:05:39.500 align:start position:0% long conversations with my smart contract<00:05:38.130> with<00:05:38.460> augur<00:05:38.639> smart<00:05:39.030> contract 00:05:39.500 --> 00:05:39.510 align:start position:0% contract with augur smart contract 00:05:39.510 --> 00:05:41.659 align:start position:0% contract with augur smart contract development<00:05:39.960> team<00:05:40.110> sort<00:05:41.070> of<00:05:41.159> what<00:05:41.310> what<00:05:41.550> is 00:05:41.659 --> 00:05:41.669 align:start position:0% development team sort of what what is 00:05:41.669 --> 00:05:43.700 align:start position:0% development team sort of what what is their<00:05:41.849> wish<00:05:42.060> list<00:05:42.389> as<00:05:42.750> far<00:05:42.870> as<00:05:43.229> tooling<00:05:43.680> that 00:05:43.700 --> 00:05:43.710 align:start position:0% their wish list as far as tooling that 00:05:43.710 --> 00:05:46.520 align:start position:0% their wish list as far as tooling that could<00:05:43.949> be<00:05:44.070> improved<00:05:44.630> and<00:05:45.630> it's<00:05:46.110> mostly<00:05:46.409> not 00:05:46.520 --> 00:05:46.530 align:start position:0% could be improved and it's mostly not 00:05:46.530 --> 00:05:49.399 align:start position:0% could be improved and it's mostly not things<00:05:46.830> that<00:05:46.949> are<00:05:47.130> well<00:05:47.820> X<00:05:48.780> is<00:05:49.110> just 00:05:49.399 --> 00:05:49.409 align:start position:0% things that are well X is just 00:05:49.409 --> 00:05:51.370 align:start position:0% things that are well X is just completely<00:05:49.830> missing<00:05:50.340> from<00:05:50.370> this<00:05:50.820> ecosystem 00:05:51.370 --> 00:05:51.380 align:start position:0% completely missing from this ecosystem 00:05:51.380 --> 00:05:54.230 align:start position:0% completely missing from this ecosystem rather<00:05:52.380> it's<00:05:52.740> you<00:05:53.190> know<00:05:53.370> something<00:05:54.210> that 00:05:54.230 --> 00:05:54.240 align:start position:0% rather it's you know something that 00:05:54.240 --> 00:05:56.689 align:start position:0% rather it's you know something that exists<00:05:54.720> but<00:05:54.930> maybe<00:05:55.080> doesn't<00:05:55.470> work<00:05:55.620> as<00:05:55.889> well<00:05:56.400> as 00:05:56.689 --> 00:05:56.699 align:start position:0% exists but maybe doesn't work as well as 00:05:56.699 --> 00:05:58.909 align:start position:0% exists but maybe doesn't work as well as we<00:05:57.509> would<00:05:57.599> like<00:05:57.780> it<00:05:57.930> to<00:05:57.960> or<00:05:58.229> it<00:05:58.470> just<00:05:58.620> doesn't 00:05:58.909 --> 00:05:58.919 align:start position:0% we would like it to or it just doesn't 00:05:58.919 --> 00:06:01.490 align:start position:0% we would like it to or it just doesn't work<00:05:59.039> quite<00:05:59.340> as<00:05:59.639> we<00:05:59.849> would<00:06:00.000> like<00:06:00.150> it<00:06:00.300> to<00:06:00.500> so 00:06:01.490 --> 00:06:01.500 align:start position:0% work quite as we would like it to so 00:06:01.500 --> 00:06:03.830 align:start position:0% work quite as we would like it to so this<00:06:01.620> is<00:06:01.800> this<00:06:02.099> is<00:06:02.280> my<00:06:02.520> wish<00:06:02.729> list<00:06:02.970> sort<00:06:03.750> of 00:06:03.830 --> 00:06:03.840 align:start position:0% this is this is my wish list sort of 00:06:03.840 --> 00:06:06.050 align:start position:0% this is this is my wish list sort of trimmed<00:06:04.080> down<00:06:04.169> the<00:06:05.130> suggestions<00:06:05.699> that<00:06:05.759> I<00:06:05.880> got 00:06:06.050 --> 00:06:06.060 align:start position:0% trimmed down the suggestions that I got 00:06:06.060 --> 00:06:07.670 align:start position:0% trimmed down the suggestions that I got for<00:06:06.150> my<00:06:06.210> engineers<00:06:06.690> and<00:06:06.990> this<00:06:07.320> seemed<00:06:07.560> to<00:06:07.650> be 00:06:07.670 --> 00:06:07.680 align:start position:0% for my engineers and this seemed to be 00:06:07.680 --> 00:06:11.629 align:start position:0% for my engineers and this seemed to be the<00:06:07.770> consensus<00:06:08.370> list<00:06:09.830> and<00:06:10.830> I'm<00:06:11.190> gonna<00:06:11.490> go 00:06:11.629 --> 00:06:11.639 align:start position:0% the consensus list and I'm gonna go 00:06:11.639 --> 00:06:15.140 align:start position:0% the consensus list and I'm gonna go through<00:06:11.820> each<00:06:11.909> one<00:06:12.000> of<00:06:12.210> these<00:06:12.300> in<00:06:13.759> some<00:06:14.759> detail 00:06:15.140 --> 00:06:15.150 align:start position:0% through each one of these in some detail 00:06:15.150 --> 00:06:18.890 align:start position:0% through each one of these in some detail and<00:06:16.280> I<00:06:17.280> guess<00:06:17.820> there's<00:06:18.000> there's<00:06:18.599> two<00:06:18.659> things 00:06:18.890 --> 00:06:18.900 align:start position:0% and I guess there's there's two things 00:06:18.900 --> 00:06:20.149 align:start position:0% and I guess there's there's two things that<00:06:19.020> I<00:06:19.349> would<00:06:19.500> like<00:06:19.620> people<00:06:19.740> to<00:06:19.979> take<00:06:20.099> away 00:06:20.149 --> 00:06:20.159 align:start position:0% that I would like people to take away 00:06:20.159 --> 00:06:24.170 align:start position:0% that I would like people to take away from<00:06:20.400> this<00:06:20.669> first<00:06:21.539> is<00:06:21.810> that<00:06:21.990> if<00:06:22.289> you<00:06:22.860> are<00:06:23.180> Andy 00:06:24.170 --> 00:06:24.180 align:start position:0% from this first is that if you are Andy 00:06:24.180 --> 00:06:25.580 align:start position:0% from this first is that if you are Andy theorem<00:06:24.479> developer<00:06:24.870> which<00:06:25.020> I<00:06:25.199> know<00:06:25.259> I<00:06:25.530> know 00:06:25.580 --> 00:06:25.590 align:start position:0% theorem developer which I know I know 00:06:25.590 --> 00:06:31.010 align:start position:0% theorem developer which I know I know many<00:06:26.039> of<00:06:26.190> you<00:06:26.280> are<00:06:26.780> then<00:06:28.340> please<00:06:29.340> chip<00:06:29.639> in<00:06:30.020> this 00:06:31.010 --> 00:06:31.020 align:start position:0% many of you are then please chip in this 00:06:31.020 --> 00:06:34.940 align:start position:0% many of you are then please chip in this is<00:06:31.729> you<00:06:32.729> know<00:06:32.820> this<00:06:32.969> is<00:06:33.150> me<00:06:33.599> saying<00:06:33.870> that<00:06:34.229> augur 00:06:34.940 --> 00:06:34.950 align:start position:0% is you know this is me saying that augur 00:06:34.950 --> 00:06:36.170 align:start position:0% is you know this is me saying that augur could<00:06:35.130> really<00:06:35.310> use<00:06:35.550> your<00:06:35.909> help 00:06:36.170 --> 00:06:36.180 align:start position:0% could really use your help 00:06:36.180 --> 00:06:39.050 align:start position:0% could really use your help and<00:06:36.510> I<00:06:37.110> guess<00:06:37.710> in<00:06:37.890> the<00:06:38.040> spirit<00:06:38.490> in<00:06:38.820> the<00:06:38.940> spirit 00:06:39.050 --> 00:06:39.060 align:start position:0% and I guess in the spirit in the spirit 00:06:39.060 --> 00:06:40.970 align:start position:0% and I guess in the spirit in the spirit of<00:06:39.300> auger<00:06:39.540> putting<00:06:40.110> putting<00:06:40.470> our<00:06:40.680> money<00:06:40.770> where 00:06:40.970 --> 00:06:40.980 align:start position:0% of auger putting putting our money where 00:06:40.980 --> 00:06:46.790 align:start position:0% of auger putting putting our money where our<00:06:41.010> mouth<00:06:41.220> is<00:06:41.840> and<00:06:43.310> if<00:06:44.310> you<00:06:45.210> are<00:06:45.390> a<00:06:45.740> you<00:06:46.740> know 00:06:46.790 --> 00:06:46.800 align:start position:0% our mouth is and if you are a you know 00:06:46.800 --> 00:06:50.810 align:start position:0% our mouth is and if you are a you know if<00:06:46.980> you're<00:06:47.370> adapt<00:06:47.670> development<00:06:48.240> team<00:06:48.740> and<00:06:49.820> by 00:06:50.810 --> 00:06:50.820 align:start position:0% if you're adapt development team and by 00:06:50.820 --> 00:06:53.180 align:start position:0% if you're adapt development team and by which<00:06:51.060> list<00:06:51.360> doesn't<00:06:51.840> match<00:06:51.960> yours<00:06:52.290> and<00:06:52.800> I 00:06:53.180 --> 00:06:53.190 align:start position:0% which list doesn't match yours and I 00:06:53.190 --> 00:06:54.680 align:start position:0% which list doesn't match yours and I mean<00:06:53.340> it<00:06:53.430> probably<00:06:53.460> doesn't<00:06:53.970> right 00:06:54.680 --> 00:06:54.690 align:start position:0% mean it probably doesn't right 00:06:54.690 --> 00:06:56.720 align:start position:0% mean it probably doesn't right everybody's<00:06:55.380> not<00:06:55.560> gonna<00:06:55.710> have<00:06:55.890> the<00:06:56.430> exact 00:06:56.720 --> 00:06:56.730 align:start position:0% everybody's not gonna have the exact 00:06:56.730 --> 00:07:00.650 align:start position:0% everybody's not gonna have the exact same<00:06:56.760> needs<00:06:57.260> then<00:06:58.260> I<00:06:58.970> would<00:06:59.970> say<00:07:00.120> you<00:07:00.630> should 00:07:00.650 --> 00:07:00.660 align:start position:0% same needs then I would say you should 00:07:00.660 --> 00:07:03.230 align:start position:0% same needs then I would say you should create<00:07:01.110> your<00:07:01.170> own<00:07:01.320> bounties<00:07:01.740> or<00:07:02.670> Commission 00:07:03.230 --> 00:07:03.240 align:start position:0% create your own bounties or Commission 00:07:03.240 --> 00:07:04.880 align:start position:0% create your own bounties or Commission your<00:07:03.390> own<00:07:03.510> tools<00:07:03.810> and<00:07:04.230> I'll<00:07:04.410> tell<00:07:04.590> you<00:07:04.650> what<00:07:04.770> if 00:07:04.880 --> 00:07:04.890 align:start position:0% your own tools and I'll tell you what if 00:07:04.890 --> 00:07:06.290 align:start position:0% your own tools and I'll tell you what if you<00:07:05.070> don't<00:07:05.250> if<00:07:05.580> you<00:07:05.880> don't<00:07:06.000> want<00:07:06.150> to<00:07:06.210> go 00:07:06.290 --> 00:07:06.300 align:start position:0% you don't if you don't want to go 00:07:06.300 --> 00:07:09.080 align:start position:0% you don't if you don't want to go through<00:07:06.420> the<00:07:06.540> hassle<00:07:06.690> of<00:07:07.460> you<00:07:08.460> know<00:07:08.550> let 00:07:09.080 --> 00:07:09.090 align:start position:0% through the hassle of you know let 00:07:09.090 --> 00:07:11.240 align:start position:0% through the hassle of you know let people<00:07:09.270> know<00:07:09.420> that<00:07:09.570> you're<00:07:09.990> you<00:07:10.830> you're<00:07:11.130> doing 00:07:11.240 --> 00:07:11.250 align:start position:0% people know that you're you you're doing 00:07:11.250 --> 00:07:15.020 align:start position:0% people know that you're you you're doing a<00:07:11.490> bounty<00:07:12.230> and<00:07:13.230> you<00:07:13.500> want<00:07:13.680> to<00:07:13.770> just<00:07:13.920> make<00:07:14.910> it 00:07:15.020 --> 00:07:15.030 align:start position:0% a bounty and you want to just make it 00:07:15.030 --> 00:07:17.090 align:start position:0% a bounty and you want to just make it available<00:07:15.210> you<00:07:15.510> can<00:07:15.660> put<00:07:15.810> it<00:07:15.930> on<00:07:16.100> augers 00:07:17.090 --> 00:07:17.100 align:start position:0% available you can put it on augers 00:07:17.100 --> 00:07:19.670 align:start position:0% available you can put it on augers website<00:07:17.910> we're<00:07:18.780> gonna<00:07:18.870> have<00:07:19.050> all<00:07:19.230> Garnett 00:07:19.670 --> 00:07:19.680 align:start position:0% website we're gonna have all Garnett 00:07:19.680 --> 00:07:21.920 align:start position:0% website we're gonna have all Garnett slash<00:07:19.890> bounties<00:07:20.370> is<00:07:20.640> where<00:07:21.480> it's<00:07:21.660> gonna<00:07:21.750> be 00:07:21.920 --> 00:07:21.930 align:start position:0% slash bounties is where it's gonna be 00:07:21.930 --> 00:07:23.600 align:start position:0% slash bounties is where it's gonna be listed<00:07:22.290> you<00:07:22.440> know<00:07:22.530> just<00:07:22.740> send<00:07:23.310> me<00:07:23.430> an<00:07:23.520> email 00:07:23.600 --> 00:07:23.610 align:start position:0% listed you know just send me an email 00:07:23.610 --> 00:07:26.720 align:start position:0% listed you know just send me an email jacket<00:07:24.450> auger<00:07:24.660> dotnet<00:07:25.050> and<00:07:25.290> I'm<00:07:26.190> happy<00:07:26.490> to<00:07:26.520> put 00:07:26.720 --> 00:07:26.730 align:start position:0% jacket auger dotnet and I'm happy to put 00:07:26.730 --> 00:07:28.430 align:start position:0% jacket auger dotnet and I'm happy to put up<00:07:26.850> third-party<00:07:27.630> bounties<00:07:27.960> as<00:07:28.110> well<00:07:28.260> as<00:07:28.350> the 00:07:28.430 --> 00:07:28.440 align:start position:0% up third-party bounties as well as the 00:07:28.440 --> 00:07:33.260 align:start position:0% up third-party bounties as well as the ones<00:07:28.590> we<00:07:28.740> want<00:07:31.610> so<00:07:32.610> now<00:07:32.730> let<00:07:32.850> me<00:07:32.880> let<00:07:33.090> me<00:07:33.120> go 00:07:33.260 --> 00:07:33.270 align:start position:0% ones we want so now let me let me go 00:07:33.270 --> 00:07:35.860 align:start position:0% ones we want so now let me let me go through<00:07:33.450> my<00:07:33.720> particular<00:07:34.560> wishlist<00:07:35.040> in<00:07:35.280> detail 00:07:35.860 --> 00:07:35.870 align:start position:0% through my particular wishlist in detail 00:07:35.870 --> 00:07:45.260 align:start position:0% through my particular wishlist in detail well<00:07:37.640> 10<00:07:38.640> minutes<00:07:38.670> Wow<00:07:39.000> anyways<00:07:41.120> so<00:07:44.270> feedback 00:07:45.260 --> 00:07:45.270 align:start position:0% well 10 minutes Wow anyways so feedback 00:07:45.270 --> 00:07:47.960 align:start position:0% well 10 minutes Wow anyways so feedback I<00:07:45.540> got<00:07:45.660> from<00:07:46.220> our<00:07:47.220> smart<00:07:47.610> contract 00:07:47.960 --> 00:07:47.970 align:start position:0% I got from our smart contract 00:07:47.970 --> 00:07:49.610 align:start position:0% I got from our smart contract development<00:07:48.390> team<00:07:48.510> as<00:07:48.750> well<00:07:48.930> as<00:07:49.110> a<00:07:49.290> number<00:07:49.470> of 00:07:49.610 --> 00:07:49.620 align:start position:0% development team as well as a number of 00:07:49.620 --> 00:07:52.250 align:start position:0% development team as well as a number of other<00:07:49.980> people<00:07:50.250> in<00:07:51.240> the<00:07:51.660> space<00:07:51.870> is<00:07:52.080> that<00:07:52.200> the 00:07:52.250 --> 00:07:52.260 align:start position:0% other people in the space is that the 00:07:52.260 --> 00:07:53.930 align:start position:0% other people in the space is that the number<00:07:52.830> one<00:07:53.100> thing<00:07:53.340> that's<00:07:53.490> really<00:07:53.820> missing 00:07:53.930 --> 00:07:53.940 align:start position:0% number one thing that's really missing 00:07:53.940 --> 00:07:59.360 align:start position:0% number one thing that's really missing is<00:07:54.450> a<00:07:55.140> debugger<00:07:56.100> like<00:07:57.030> a<00:07:57.060> good<00:07:57.600> debugger<00:07:58.370> the 00:07:59.360 --> 00:07:59.370 align:start position:0% is a debugger like a good debugger the 00:07:59.370 --> 00:08:01.850 align:start position:0% is a debugger like a good debugger the kinds<00:07:59.640> that<00:08:00.030> we<00:08:00.090> knew<00:08:00.300> in<00:08:00.480> our<00:08:00.750> past<00:08:01.350> lives<00:08:01.530> as 00:08:01.850 --> 00:08:01.860 align:start position:0% kinds that we knew in our past lives as 00:08:01.860 --> 00:08:03.890 align:start position:0% kinds that we knew in our past lives as other<00:08:02.070> other<00:08:02.820> sorts<00:08:03.270> of<00:08:03.330> application 00:08:03.890 --> 00:08:03.900 align:start position:0% other other sorts of application 00:08:03.900 --> 00:08:08.360 align:start position:0% other other sorts of application developers<00:08:06.680> you<00:08:07.680> know<00:08:07.710> there's<00:08:07.980> there's<00:08:08.220> all 00:08:08.360 --> 00:08:08.370 align:start position:0% developers you know there's there's all 00:08:08.370 --> 00:08:12.770 align:start position:0% developers you know there's there's all kinds<00:08:08.730> of<00:08:10.640> well<00:08:11.640> there's<00:08:12.120> a<00:08:12.150> roomful 00:08:12.770 --> 00:08:12.780 align:start position:0% kinds of well there's a roomful 00:08:12.780 --> 00:08:16.310 align:start position:0% kinds of well there's a roomful developers<00:08:13.290> right<00:08:13.500> so<00:08:14.030> tell<00:08:15.030> me<00:08:15.150> if<00:08:15.240> this<00:08:15.360> if 00:08:16.310 --> 00:08:16.320 align:start position:0% developers right so tell me if this if 00:08:16.320 --> 00:08:17.570 align:start position:0% developers right so tell me if this if any<00:08:16.470> of<00:08:16.560> you<00:08:16.620> have<00:08:16.770> been<00:08:16.890> through<00:08:16.950> this<00:08:17.160> sort 00:08:17.570 --> 00:08:17.580 align:start position:0% any of you have been through this sort 00:08:17.580 --> 00:08:21.410 align:start position:0% any of you have been through this sort of<00:08:17.760> debugging<00:08:18.570> cycle<00:08:18.990> where<00:08:19.850> you<00:08:20.850> are<00:08:21.120> trying 00:08:21.410 --> 00:08:21.420 align:start position:0% of debugging cycle where you are trying 00:08:21.420 --> 00:08:23.960 align:start position:0% of debugging cycle where you are trying to<00:08:21.630> execute<00:08:22.320> a<00:08:22.500> sent<00:08:22.710> transaction<00:08:23.370> and<00:08:23.610> it 00:08:23.960 --> 00:08:23.970 align:start position:0% to execute a sent transaction and it 00:08:23.970 --> 00:08:26.000 align:start position:0% to execute a sent transaction and it fails<00:08:24.210> for<00:08:25.200> what<00:08:25.350> you've<00:08:25.440> a<00:08:25.530> bug<00:08:25.740> in<00:08:25.860> your<00:08:25.890> code 00:08:26.000 --> 00:08:26.010 align:start position:0% fails for what you've a bug in your code 00:08:26.010 --> 00:08:28.700 align:start position:0% fails for what you've a bug in your code you<00:08:26.970> ran<00:08:27.090> out<00:08:27.120> of<00:08:27.270> gas<00:08:27.480> whatever<00:08:28.020> transaction 00:08:28.700 --> 00:08:28.710 align:start position:0% you ran out of gas whatever transaction 00:08:28.710 --> 00:08:32.120 align:start position:0% you ran out of gas whatever transaction failed<00:08:30.260> but<00:08:31.260> you<00:08:31.380> don't<00:08:31.530> actually<00:08:31.710> know 00:08:32.120 --> 00:08:32.130 align:start position:0% failed but you don't actually know 00:08:32.130 --> 00:08:32.690 align:start position:0% failed but you don't actually know anything 00:08:32.690 --> 00:08:32.700 align:start position:0% anything 00:08:32.700 --> 00:08:34.360 align:start position:0% anything other<00:08:32.880> than<00:08:33.210> that<00:08:33.270> your<00:08:33.570> transaction<00:08:34.140> failed 00:08:34.360 --> 00:08:34.370 align:start position:0% other than that your transaction failed 00:08:34.370 --> 00:08:38.120 align:start position:0% other than that your transaction failed right<00:08:35.370> you<00:08:36.030> can't<00:08:36.330> if<00:08:36.540> you<00:08:37.410> have<00:08:37.500> you<00:08:37.590> tried<00:08:37.890> to 00:08:38.120 --> 00:08:38.130 align:start position:0% right you can't if you have you tried to 00:08:38.130 --> 00:08:40.220 align:start position:0% right you can't if you have you tried to omit<00:08:38.970> some<00:08:39.210> logs<00:08:39.450> as<00:08:39.870> part<00:08:40.080> of<00:08:40.140> your 00:08:40.220 --> 00:08:40.230 align:start position:0% omit some logs as part of your 00:08:40.230 --> 00:08:41.540 align:start position:0% omit some logs as part of your transaction<00:08:40.860> well<00:08:41.010> they<00:08:41.100> didn't<00:08:41.280> get<00:08:41.340> emitted 00:08:41.540 --> 00:08:41.550 align:start position:0% transaction well they didn't get emitted 00:08:41.550 --> 00:08:44.750 align:start position:0% transaction well they didn't get emitted because<00:08:41.760> your<00:08:42.000> transaction<00:08:42.480> failed<00:08:43.760> you 00:08:44.750 --> 00:08:44.760 align:start position:0% because your transaction failed you 00:08:44.760 --> 00:08:47.420 align:start position:0% because your transaction failed you can't<00:08:45.030> just<00:08:45.840> set<00:08:46.170> a<00:08:46.200> breakpoint<00:08:46.530> in<00:08:46.980> your 00:08:47.420 --> 00:08:47.430 align:start position:0% can't just set a breakpoint in your 00:08:47.430 --> 00:08:49.160 align:start position:0% can't just set a breakpoint in your solidity<00:08:47.850> code<00:08:48.150> and<00:08:48.390> then<00:08:48.480> drop<00:08:48.810> into<00:08:49.020> the 00:08:49.160 --> 00:08:49.170 align:start position:0% solidity code and then drop into the 00:08:49.170 --> 00:08:49.910 align:start position:0% solidity code and then drop into the environment<00:08:49.380> and 00:08:49.910 --> 00:08:49.920 align:start position:0% environment and 00:08:49.920 --> 00:08:53.179 align:start position:0% environment and look<00:08:50.160> at<00:08:50.249> the<00:08:50.339> variables<00:08:51.019> because<00:08:52.019> well<00:08:52.949> you 00:08:53.179 --> 00:08:53.189 align:start position:0% look at the variables because well you 00:08:53.189 --> 00:08:56.179 align:start position:0% look at the variables because well you don't<00:08:53.309> have<00:08:53.399> a<00:08:53.429> property<00:08:53.790> bugger<00:08:54.059> and<00:08:54.920> so<00:08:55.920> what 00:08:56.179 --> 00:08:56.189 align:start position:0% don't have a property bugger and so what 00:08:56.189 --> 00:08:58.160 align:start position:0% don't have a property bugger and so what you<00:08:56.309> end<00:08:56.459> up<00:08:56.489> doing<00:08:56.549> is<00:08:56.970> you<00:08:57.329> comment<00:08:58.049> out 00:08:58.160 --> 00:08:58.170 align:start position:0% you end up doing is you comment out 00:08:58.170 --> 00:09:01.609 align:start position:0% you end up doing is you comment out chunks<00:08:59.160> of<00:08:59.309> code<00:08:59.689> you<00:09:00.689> recompile<00:09:01.259> you<00:09:01.439> run 00:09:01.609 --> 00:09:01.619 align:start position:0% chunks of code you recompile you run 00:09:01.619 --> 00:09:04.970 align:start position:0% chunks of code you recompile you run your<00:09:01.769> test<00:09:01.949> again<00:09:02.279> and<00:09:03.230> see<00:09:04.230> if<00:09:04.319> it<00:09:04.410> passes<00:09:04.589> you 00:09:04.970 --> 00:09:04.980 align:start position:0% your test again and see if it passes you 00:09:04.980 --> 00:09:06.799 align:start position:0% your test again and see if it passes you do<00:09:05.639> that<00:09:05.819> over<00:09:05.999> and<00:09:06.089> over<00:09:06.269> again<00:09:06.359> until<00:09:06.600> you 00:09:06.799 --> 00:09:06.809 align:start position:0% do that over and over again until you 00:09:06.809 --> 00:09:12.970 align:start position:0% do that over and over again until you get<00:09:07.290> you<00:09:07.499> get<00:09:07.619> a<00:09:07.679> transaction<00:09:08.279> not<00:09:08.699> failing 00:09:12.970 --> 00:09:12.980 align:start position:0% 00:09:12.980 --> 00:09:16.099 align:start position:0% this<00:09:13.980> makes<00:09:14.369> writing<00:09:14.699> contract<00:09:15.509> code<00:09:15.779> take 00:09:16.099 --> 00:09:16.109 align:start position:0% this makes writing contract code take 00:09:16.109 --> 00:09:18.109 align:start position:0% this makes writing contract code take forever<00:09:16.470> if<00:09:17.129> this<00:09:17.429> is<00:09:17.579> your<00:09:17.699> development 00:09:18.109 --> 00:09:18.119 align:start position:0% forever if this is your development 00:09:18.119 --> 00:09:20.359 align:start position:0% forever if this is your development cycle<00:09:18.299> now<00:09:19.049> there's<00:09:19.499> various<00:09:19.739> things<00:09:19.829> that<00:09:20.069> we 00:09:20.359 --> 00:09:20.369 align:start position:0% cycle now there's various things that we 00:09:20.369 --> 00:09:23.720 align:start position:0% cycle now there's various things that we do<00:09:20.790> in<00:09:21.239> house<00:09:21.749> to<00:09:22.139> make<00:09:22.290> this<00:09:22.859> not<00:09:23.129> literally 00:09:23.720 --> 00:09:23.730 align:start position:0% do in house to make this not literally 00:09:23.730 --> 00:09:25.519 align:start position:0% do in house to make this not literally our<00:09:23.850> development<00:09:24.329> cycle<00:09:24.660> it's<00:09:24.839> not<00:09:25.049> it's<00:09:25.410> not 00:09:25.519 --> 00:09:25.529 align:start position:0% our development cycle it's not it's not 00:09:25.529 --> 00:09:29.479 align:start position:0% our development cycle it's not it's not quite<00:09:25.889> quite<00:09:26.759> this<00:09:26.970> raw<00:09:27.889> but<00:09:28.889> this<00:09:29.040> is<00:09:29.220> sort<00:09:29.429> of 00:09:29.479 --> 00:09:29.489 align:start position:0% quite quite this raw but this is sort of 00:09:29.489 --> 00:09:32.030 align:start position:0% quite quite this raw but this is sort of the<00:09:29.730> this<00:09:30.480> is<00:09:30.660> sort<00:09:30.809> of<00:09:30.839> the<00:09:31.019> naive<00:09:31.379> cycle<00:09:31.799> now 00:09:32.030 --> 00:09:32.040 align:start position:0% the this is sort of the naive cycle now 00:09:32.040 --> 00:09:33.949 align:start position:0% the this is sort of the naive cycle now a<00:09:32.309> lot<00:09:32.850> of<00:09:32.879> you're<00:09:32.999> probably<00:09:33.149> thinking<00:09:33.329> well 00:09:33.949 --> 00:09:33.959 align:start position:0% a lot of you're probably thinking well 00:09:33.959 --> 00:09:35.929 align:start position:0% a lot of you're probably thinking well there<00:09:34.290> is<00:09:34.410> a<00:09:34.439> debugger<00:09:34.889> out<00:09:35.129> there<00:09:35.339> right 00:09:35.929 --> 00:09:35.939 align:start position:0% there is a debugger out there right 00:09:35.939 --> 00:09:43.609 align:start position:0% there is a debugger out there right remix<00:09:36.569> and<00:09:38.600> remix<00:09:39.600> is<00:09:39.749> cool<00:09:40.249> but<00:09:42.470> it's<00:09:43.470> also 00:09:43.609 --> 00:09:43.619 align:start position:0% remix and remix is cool but it's also 00:09:43.619 --> 00:09:52.749 align:start position:0% remix and remix is cool but it's also it's<00:09:44.220> a<00:09:44.339> full<00:09:44.899> browser-based<00:09:46.220> IDE<00:09:47.220> and<00:09:50.359> it's 00:09:52.749 --> 00:09:52.759 align:start position:0% it's a full browser-based IDE and it's 00:09:52.759 --> 00:09:55.400 align:start position:0% it's a full browser-based IDE and it's so<00:09:53.759> one<00:09:54.119> it's<00:09:54.299> it's<00:09:54.509> awkward<00:09:54.869> for<00:09:55.079> large 00:09:55.400 --> 00:09:55.410 align:start position:0% so one it's it's awkward for large 00:09:55.410 --> 00:09:56.900 align:start position:0% so one it's it's awkward for large projects<00:09:55.980> to<00:09:56.069> use<00:09:56.160> it's<00:09:56.339> awkward<00:09:56.639> to<00:09:56.730> load 00:09:56.900 --> 00:09:56.910 align:start position:0% projects to use it's awkward to load 00:09:56.910 --> 00:09:59.720 align:start position:0% projects to use it's awkward to load lots<00:09:57.149> of<00:09:57.269> contracts<00:09:57.749> into<00:09:57.959> it<00:09:58.429> get<00:09:59.429> all<00:09:59.549> the 00:09:59.720 --> 00:09:59.730 align:start position:0% lots of contracts into it get all the 00:09:59.730 --> 00:10:01.460 align:start position:0% lots of contracts into it get all the relative<00:10:00.239> paths<00:10:00.509> and<00:10:00.779> stuff<00:10:01.019> to<00:10:01.169> resolve 00:10:01.460 --> 00:10:01.470 align:start position:0% relative paths and stuff to resolve 00:10:01.470 --> 00:10:04.519 align:start position:0% relative paths and stuff to resolve correctly<00:10:02.720> but<00:10:03.720> the<00:10:03.809> big<00:10:03.989> I<00:10:04.110> think<00:10:04.290> the<00:10:04.350> bigger 00:10:04.519 --> 00:10:04.529 align:start position:0% correctly but the big I think the bigger 00:10:04.529 --> 00:10:07.220 align:start position:0% correctly but the big I think the bigger issue<00:10:04.619> with<00:10:05.009> it<00:10:05.129> by<00:10:05.249> far<00:10:05.489> is<00:10:05.639> that<00:10:05.929> you<00:10:06.929> can't 00:10:07.220 --> 00:10:07.230 align:start position:0% issue with it by far is that you can't 00:10:07.230 --> 00:10:09.530 align:start position:0% issue with it by far is that you can't really<00:10:07.559> integrate<00:10:08.189> it<00:10:08.339> with<00:10:08.699> other<00:10:08.730> tools<00:10:08.999> or 00:10:09.530 --> 00:10:09.540 align:start position:0% really integrate it with other tools or 00:10:09.540 --> 00:10:12.049 align:start position:0% really integrate it with other tools or at<00:10:10.019> least<00:10:10.139> I<00:10:10.470> don't<00:10:11.160> know<00:10:11.279> how<00:10:11.429> to<00:10:11.519> do<00:10:11.669> it<00:10:11.819> and 00:10:12.049 --> 00:10:12.059 align:start position:0% at least I don't know how to do it and 00:10:12.059 --> 00:10:14.449 align:start position:0% at least I don't know how to do it and by<00:10:12.899> smart<00:10:13.410> contract<00:10:13.799> dev<00:10:13.919> team<00:10:14.129> doesn't<00:10:14.309> know 00:10:14.449 --> 00:10:14.459 align:start position:0% by smart contract dev team doesn't know 00:10:14.459 --> 00:10:19.100 align:start position:0% by smart contract dev team doesn't know how<00:10:14.549> to<00:10:14.579> do<00:10:14.790> it<00:10:16.459> for<00:10:17.459> example<00:10:17.669> like<00:10:17.959> augur<00:10:18.959> has 00:10:19.100 --> 00:10:19.110 align:start position:0% how to do it for example like augur has 00:10:19.110 --> 00:10:21.289 align:start position:0% how to do it for example like augur has a<00:10:19.139> pretty<00:10:19.410> extensive<00:10:19.709> test<00:10:20.069> suite<00:10:20.279> as<00:10:20.850> you 00:10:21.289 --> 00:10:21.299 align:start position:0% a pretty extensive test suite as you 00:10:21.299 --> 00:10:23.539 align:start position:0% a pretty extensive test suite as you might<00:10:21.449> imagine<00:10:21.540> we<00:10:21.869> have<00:10:22.549> including 00:10:23.539 --> 00:10:23.549 align:start position:0% might imagine we have including 00:10:23.549 --> 00:10:26.869 align:start position:0% might imagine we have including libraries<00:10:23.970> and<00:10:24.149> stuff<00:10:24.209> we<00:10:24.419> have<00:10:24.799> 75<00:10:25.799> or<00:10:26.639> 76 00:10:26.869 --> 00:10:26.879 align:start position:0% libraries and stuff we have 75 or 76 00:10:26.879 --> 00:10:29.689 align:start position:0% libraries and stuff we have 75 or 76 smart<00:10:27.569> contracts<00:10:28.019> make<00:10:28.470> up<00:10:28.619> augur<00:10:29.189> in<00:10:29.369> total 00:10:29.689 --> 00:10:29.699 align:start position:0% smart contracts make up augur in total 00:10:29.699 --> 00:10:31.789 align:start position:0% smart contracts make up augur in total and<00:10:30.389> so<00:10:30.509> we<00:10:30.629> have<00:10:30.720> a<00:10:30.779> lot<00:10:30.899> of<00:10:30.929> tests<00:10:31.290> associated 00:10:31.789 --> 00:10:31.799 align:start position:0% and so we have a lot of tests associated 00:10:31.799 --> 00:10:33.199 align:start position:0% and so we have a lot of tests associated with<00:10:31.919> that<00:10:32.100> we<00:10:32.189> have<00:10:32.279> unit<00:10:32.610> tests<00:10:32.910> written 00:10:33.199 --> 00:10:33.209 align:start position:0% with that we have unit tests written 00:10:33.209 --> 00:10:37.819 align:start position:0% with that we have unit tests written using<00:10:33.809> pi<00:10:34.589> theorem<00:10:34.860> tester<00:10:35.399> and<00:10:36.709> we<00:10:37.709> have 00:10:37.819 --> 00:10:37.829 align:start position:0% using pi theorem tester and we have 00:10:37.829 --> 00:10:40.220 align:start position:0% using pi theorem tester and we have integration<00:10:38.429> tests<00:10:38.819> which<00:10:39.749> are<00:10:39.929> written 00:10:40.220 --> 00:10:40.230 align:start position:0% integration tests which are written 00:10:40.230 --> 00:10:43.879 align:start position:0% integration tests which are written using<00:10:41.480> well<00:10:42.480> they're<00:10:42.660> written<00:10:42.869> in<00:10:43.019> JavaScript 00:10:43.879 --> 00:10:43.889 align:start position:0% using well they're written in JavaScript 00:10:43.889 --> 00:10:48.199 align:start position:0% using well they're written in JavaScript using<00:10:44.100> the<00:10:44.850> eath<00:10:45.119> KS<00:10:45.480> library<00:10:45.899> I<00:10:47.119> think<00:10:48.119> the 00:10:48.199 --> 00:10:48.209 align:start position:0% using the eath KS library I think the 00:10:48.209 --> 00:10:49.249 align:start position:0% using the eath KS library I think the author<00:10:48.329> of<00:10:48.509> that<00:10:48.660> library<00:10:48.929> is<00:10:48.959> actually 00:10:49.249 --> 00:10:49.259 align:start position:0% author of that library is actually 00:10:49.259 --> 00:10:54.019 align:start position:0% author of that library is actually talking<00:10:49.470> right<00:10:49.679> after<00:10:49.980> me<00:10:50.779> and<00:10:51.779> I<00:10:52.910> mean<00:10:53.910> what 00:10:54.019 --> 00:10:54.029 align:start position:0% talking right after me and I mean what 00:10:54.029 --> 00:10:55.849 align:start position:0% talking right after me and I mean what what<00:10:54.509> the<00:10:54.660> cycle<00:10:54.989> we<00:10:55.049> would<00:10:55.199> really<00:10:55.350> want<00:10:55.619> is 00:10:55.849 --> 00:10:55.859 align:start position:0% what the cycle we would really want is 00:10:55.859 --> 00:11:00.409 align:start position:0% what the cycle we would really want is to<00:10:58.039> be<00:10:59.039> able<00:10:59.129> to<00:10:59.249> say<00:10:59.579> set<00:10:59.819> a<00:10:59.850> breakpoint<00:11:00.089> in 00:11:00.409 --> 00:11:00.419 align:start position:0% to be able to say set a breakpoint in 00:11:00.419 --> 00:11:01.730 align:start position:0% to be able to say set a breakpoint in solidity 00:11:01.730 --> 00:11:01.740 align:start position:0% solidity 00:11:01.740 --> 00:11:05.060 align:start position:0% solidity and<00:11:01.970> then<00:11:02.970> run<00:11:03.330> our<00:11:03.450> test<00:11:03.660> suite<00:11:03.860> right<00:11:04.860> that 00:11:05.060 --> 00:11:05.070 align:start position:0% and then run our test suite right that 00:11:05.070 --> 00:11:06.560 align:start position:0% and then run our test suite right that that's<00:11:05.280> basically<00:11:05.790> what<00:11:06.030> we're<00:11:06.150> developing 00:11:06.560 --> 00:11:06.570 align:start position:0% that's basically what we're developing 00:11:06.570 --> 00:11:11.150 align:start position:0% that's basically what we're developing against<00:11:07.310> and<00:11:08.480> you<00:11:09.480> know<00:11:09.540> have<00:11:09.750> it<00:11:09.800> break<00:11:10.800> and 00:11:11.150 --> 00:11:11.160 align:start position:0% against and you know have it break and 00:11:11.160 --> 00:11:13.160 align:start position:0% against and you know have it break and then<00:11:11.280> drop<00:11:11.610> us<00:11:11.790> into<00:11:11.970> a<00:11:12.120> context<00:11:12.870> where<00:11:12.960> we<00:11:13.020> can 00:11:13.160 --> 00:11:13.170 align:start position:0% then drop us into a context where we can 00:11:13.170 --> 00:11:14.990 align:start position:0% then drop us into a context where we can see<00:11:13.350> what<00:11:13.500> went<00:11:13.650> wrong<00:11:13.800> when<00:11:14.550> something<00:11:14.850> goes 00:11:14.990 --> 00:11:15.000 align:start position:0% see what went wrong when something goes 00:11:15.000 --> 00:11:19.460 align:start position:0% see what went wrong when something goes wrong<00:11:16.790> and<00:11:17.790> as<00:11:18.600> far<00:11:18.750> as<00:11:18.840> I<00:11:18.900> can<00:11:18.960> tell<00:11:19.140> there's 00:11:19.460 --> 00:11:19.470 align:start position:0% wrong and as far as I can tell there's 00:11:19.470 --> 00:11:21.080 align:start position:0% wrong and as far as I can tell there's not<00:11:19.650> there's<00:11:19.860> not<00:11:19.980> really<00:11:20.250> a<00:11:20.400> way<00:11:20.490> to<00:11:20.640> do<00:11:20.940> this 00:11:21.080 --> 00:11:21.090 align:start position:0% not there's not really a way to do this 00:11:21.090 --> 00:11:24.920 align:start position:0% not there's not really a way to do this with<00:11:21.360> remix<00:11:22.140> because<00:11:22.530> it's<00:11:23.090> it's<00:11:24.090> it's<00:11:24.360> a<00:11:24.540> it's 00:11:24.920 --> 00:11:24.930 align:start position:0% with remix because it's it's it's a it's 00:11:24.930 --> 00:11:28.040 align:start position:0% with remix because it's it's it's a it's a<00:11:25.020> full<00:11:25.290> solution<00:11:25.770> it's<00:11:26.550> a<00:11:26.670> standalone<00:11:27.120> web 00:11:28.040 --> 00:11:28.050 align:start position:0% a full solution it's a standalone web 00:11:28.050 --> 00:11:31.250 align:start position:0% a full solution it's a standalone web application<00:11:28.770> and<00:11:29.360> so<00:11:30.360> remix<00:11:30.690> is<00:11:30.810> cool<00:11:30.990> but<00:11:31.140> it 00:11:31.250 --> 00:11:31.260 align:start position:0% application and so remix is cool but it 00:11:31.260 --> 00:11:33.970 align:start position:0% application and so remix is cool but it would<00:11:31.410> be<00:11:31.560> so<00:11:32.250> much<00:11:32.430> cooler<00:11:32.790> if<00:11:32.910> it<00:11:33.270> was<00:11:33.510> a 00:11:33.970 --> 00:11:33.980 align:start position:0% would be so much cooler if it was a 00:11:33.980 --> 00:11:39.200 align:start position:0% would be so much cooler if it was a library<00:11:36.710> and<00:11:37.710> so<00:11:38.310> this<00:11:38.430> is<00:11:38.550> the<00:11:38.670> first<00:11:38.850> bounty 00:11:39.200 --> 00:11:39.210 align:start position:0% library and so this is the first bounty 00:11:39.210 --> 00:11:41.630 align:start position:0% library and so this is the first bounty I<00:11:39.240> want<00:11:39.420> to<00:11:39.480> propose<00:11:39.890> what<00:11:40.890> I<00:11:40.920> want<00:11:41.250> what<00:11:41.580> I 00:11:41.630 --> 00:11:41.640 align:start position:0% I want to propose what I want what I 00:11:41.640 --> 00:11:43.610 align:start position:0% I want to propose what I want what I want<00:11:41.880> I<00:11:42.060> should<00:11:42.090> say<00:11:42.360> what<00:11:42.540> my<00:11:42.660> team<00:11:42.990> wants<00:11:43.410> is 00:11:43.610 --> 00:11:43.620 align:start position:0% want I should say what my team wants is 00:11:43.620 --> 00:11:45.770 align:start position:0% want I should say what my team wants is a<00:11:43.980> portable<00:11:44.730> debugger<00:11:45.120> and<00:11:45.270> they<00:11:45.450> want<00:11:45.660> this 00:11:45.770 --> 00:11:45.780 align:start position:0% a portable debugger and they want this 00:11:45.780 --> 00:11:51.470 align:start position:0% a portable debugger and they want this more<00:11:46.020> than<00:11:46.080> anything<00:11:46.470> else<00:11:47.660> and<00:11:49.190> the<00:11:50.190> the<00:11:50.520> most 00:11:51.470 --> 00:11:51.480 align:start position:0% more than anything else and the the most 00:11:51.480 --> 00:11:52.970 align:start position:0% more than anything else and the the most important<00:11:51.900> requirement<00:11:52.350> is<00:11:52.410> that<00:11:52.500> it<00:11:52.650> must<00:11:52.800> be 00:11:52.970 --> 00:11:52.980 align:start position:0% important requirement is that it must be 00:11:52.980 --> 00:11:56.480 align:start position:0% important requirement is that it must be a<00:11:53.100> library<00:11:53.730> slash<00:11:54.300> module<00:11:54.810> so<00:11:55.680> that<00:11:55.890> it<00:11:56.220> can<00:11:56.400> be 00:11:56.480 --> 00:11:56.490 align:start position:0% a library slash module so that it can be 00:11:56.490 --> 00:11:58.040 align:start position:0% a library slash module so that it can be integrated<00:11:57.060> with<00:11:57.180> our<00:11:57.300> existing<00:11:57.720> tooling 00:11:58.040 --> 00:11:58.050 align:start position:0% integrated with our existing tooling 00:11:58.050 --> 00:11:59.450 align:start position:0% integrated with our existing tooling that<00:11:58.080> means<00:11:58.350> integrated<00:11:58.800> with<00:11:58.920> our<00:11:59.070> existing 00:11:59.450 --> 00:11:59.460 align:start position:0% that means integrated with our existing 00:11:59.460 --> 00:12:02.540 align:start position:0% that means integrated with our existing IDs<00:11:59.780> all<00:12:00.780> right<00:12:00.900> like<00:12:01.110> for<00:12:01.350> example<00:12:02.040> if<00:12:02.430> you 00:12:02.540 --> 00:12:02.550 align:start position:0% IDs all right like for example if you 00:12:02.550 --> 00:12:04.910 align:start position:0% IDs all right like for example if you use<00:12:02.760> a<00:12:02.790> vs<00:12:03.390> code<00:12:03.720> you<00:12:03.900> want<00:12:04.110> the<00:12:04.230> debugger<00:12:04.770> to 00:12:04.910 --> 00:12:04.920 align:start position:0% use a vs code you want the debugger to 00:12:04.920 --> 00:12:08.000 align:start position:0% use a vs code you want the debugger to be<00:12:05.010> integrated<00:12:05.820> with<00:12:05.970> vs<00:12:06.270> code<00:12:06.740> you<00:12:07.740> want<00:12:07.860> it 00:12:08.000 --> 00:12:08.010 align:start position:0% be integrated with vs code you want it 00:12:08.010 --> 00:12:10.640 align:start position:0% be integrated with vs code you want it to<00:12:08.100> be<00:12:08.250> integrated<00:12:09.060> with<00:12:09.090> your<00:12:09.240> existing<00:12:09.650> test 00:12:10.640 --> 00:12:10.650 align:start position:0% to be integrated with your existing test 00:12:10.650 --> 00:12:12.560 align:start position:0% to be integrated with your existing test suite<00:12:10.950> with<00:12:11.400> your<00:12:11.520> existing<00:12:11.730> build<00:12:12.150> system 00:12:12.560 --> 00:12:12.570 align:start position:0% suite with your existing build system 00:12:12.570 --> 00:12:17.560 align:start position:0% suite with your existing build system with<00:12:12.750> your<00:12:12.900> existing<00:12:13.170> deploy<00:12:14.040> system<00:12:15.890> and 00:12:17.560 --> 00:12:17.570 align:start position:0% with your existing deploy system and 00:12:17.570 --> 00:12:20.900 align:start position:0% with your existing deploy system and this<00:12:18.570> probably<00:12:19.080> is<00:12:19.560> obvious<00:12:20.460> but<00:12:20.580> the<00:12:20.700> key 00:12:20.900 --> 00:12:20.910 align:start position:0% this probably is obvious but the key 00:12:20.910 --> 00:12:23.210 align:start position:0% this probably is obvious but the key feature<00:12:21.120> is<00:12:21.770> breakpoints<00:12:22.770> they're<00:12:23.040> one<00:12:23.190> of 00:12:23.210 --> 00:12:23.220 align:start position:0% feature is breakpoints they're one of 00:12:23.220 --> 00:12:24.590 align:start position:0% feature is breakpoints they're one of those<00:12:23.340> things<00:12:23.550> that<00:12:23.670> you<00:12:23.790> do<00:12:23.940> not<00:12:24.090> realize<00:12:24.570> how 00:12:24.590 --> 00:12:24.600 align:start position:0% those things that you do not realize how 00:12:24.600 --> 00:12:28.070 align:start position:0% those things that you do not realize how much<00:12:25.050> you<00:12:25.710> miss<00:12:25.890> breakpoints<00:12:26.930> until<00:12:27.930> you're 00:12:28.070 --> 00:12:28.080 align:start position:0% much you miss breakpoints until you're 00:12:28.080 --> 00:12:29.270 align:start position:0% much you miss breakpoints until you're in<00:12:28.170> a<00:12:28.230> development<00:12:28.590> environment<00:12:28.740> where<00:12:29.160> you 00:12:29.270 --> 00:12:29.280 align:start position:0% in a development environment where you 00:12:29.280 --> 00:12:35.450 align:start position:0% in a development environment where you don't<00:12:29.520> have<00:12:29.640> great<00:12:29.880> points<00:12:32.870> and<00:12:34.310> so<00:12:35.310> we're 00:12:35.450 --> 00:12:35.460 align:start position:0% don't have great points and so we're 00:12:35.460 --> 00:12:38.180 align:start position:0% don't have great points and so we're gonna<00:12:35.550> put<00:12:36.210> up<00:12:36.330> details<00:12:36.900> for<00:12:37.320> this<00:12:37.530> bounty<00:12:37.950> and 00:12:38.180 --> 00:12:38.190 align:start position:0% gonna put up details for this bounty and 00:12:38.190 --> 00:12:40.790 align:start position:0% gonna put up details for this bounty and the<00:12:38.640> others<00:12:38.850> I'm<00:12:39.000> proposing<00:12:39.480> at<00:12:39.660> augur<00:12:40.440> dotnet 00:12:40.790 --> 00:12:40.800 align:start position:0% the others I'm proposing at augur dotnet 00:12:40.800 --> 00:12:41.840 align:start position:0% the others I'm proposing at augur dotnet slash<00:12:41.070> bounties<00:12:41.460> there's<00:12:41.640> just<00:12:41.760> a 00:12:41.840 --> 00:12:41.850 align:start position:0% slash bounties there's just a 00:12:41.850 --> 00:12:44.240 align:start position:0% slash bounties there's just a placeholder<00:12:42.060> page<00:12:42.540> there<00:12:42.780> now<00:12:43.100> the<00:12:44.100> details 00:12:44.240 --> 00:12:44.250 align:start position:0% placeholder page there now the details 00:12:44.250 --> 00:12:45.530 align:start position:0% placeholder page there now the details will<00:12:44.550> be<00:12:44.580> available<00:12:44.730> sometime<00:12:45.240> over<00:12:45.390> the<00:12:45.450> next 00:12:45.530 --> 00:12:45.540 align:start position:0% will be available sometime over the next 00:12:45.540 --> 00:12:49.010 align:start position:0% will be available sometime over the next few<00:12:45.810> days<00:12:45.960> and<00:12:46.260> so<00:12:47.160> if<00:12:47.450> once<00:12:48.450> we<00:12:48.600> have<00:12:48.720> that<00:12:48.870> up 00:12:49.010 --> 00:12:49.020 align:start position:0% few days and so if once we have that up 00:12:49.020 --> 00:12:51.020 align:start position:0% few days and so if once we have that up and<00:12:49.170> you<00:12:49.320> can<00:12:49.440> look<00:12:49.560> at<00:12:49.710> proper<00:12:50.580> specs<00:12:50.850> for 00:12:51.020 --> 00:12:51.030 align:start position:0% and you can look at proper specs for 00:12:51.030 --> 00:12:54.440 align:start position:0% and you can look at proper specs for this<00:12:51.150> thing<00:12:51.390> if<00:12:51.720> you<00:12:52.260> build<00:12:52.470> it<00:12:52.730> you<00:12:53.730> get<00:12:53.880> 2,000 00:12:54.440 --> 00:12:54.450 align:start position:0% this thing if you build it you get 2,000 00:12:54.450 --> 00:13:03.900 align:start position:0% this thing if you build it you get 2,000 rep<00:12:56.120> that's<00:12:57.120> the<00:12:57.240> first<00:12:57.450> bounty 00:13:03.900 --> 00:13:03.910 align:start position:0% 00:13:03.910 --> 00:13:07.440 align:start position:0% this<00:13:04.910> is<00:13:05.060> the<00:13:05.120> second<00:13:05.450> point<00:13:05.600> and<00:13:05.779> this<00:13:06.110> is 00:13:07.440 --> 00:13:07.450 align:start position:0% this is the second point and this is 00:13:07.450 --> 00:13:10.060 align:start position:0% this is the second point and this is that<00:13:08.450> this<00:13:08.630> may<00:13:08.779> be<00:13:08.810> a<00:13:08.990> look<00:13:09.440> this<00:13:09.620> is<00:13:09.680> a<00:13:09.800> little 00:13:10.060 --> 00:13:10.070 align:start position:0% that this may be a look this is a little 00:13:10.070 --> 00:13:12.579 align:start position:0% that this may be a look this is a little controversial<00:13:10.750> very<00:13:11.750> often<00:13:12.110> I<00:13:12.170> find<00:13:12.350> when<00:13:12.560> I 00:13:12.579 --> 00:13:12.589 align:start position:0% controversial very often I find when I 00:13:12.589 --> 00:13:13.930 align:start position:0% controversial very often I find when I bring<00:13:12.860> this<00:13:12.980> up<00:13:13.130> especially<00:13:13.580> among<00:13:13.730> younger 00:13:13.930 --> 00:13:13.940 align:start position:0% bring this up especially among younger 00:13:13.940 --> 00:13:16.660 align:start position:0% bring this up especially among younger developers<00:13:14.770> I'm<00:13:15.770> met<00:13:16.010> with<00:13:16.160> something<00:13:16.490> less 00:13:16.660 --> 00:13:16.670 align:start position:0% developers I'm met with something less 00:13:16.670 --> 00:13:20.400 align:start position:0% developers I'm met with something less than<00:13:16.700> a<00:13:16.940> chorus<00:13:17.450> of<00:13:17.540> agreement<00:13:19.060> but 00:13:20.400 --> 00:13:20.410 align:start position:0% than a chorus of agreement but 00:13:20.410 --> 00:13:22.449 align:start position:0% than a chorus of agreement but nevertheless<00:13:21.410> I<00:13:21.649> think<00:13:21.680> it's<00:13:21.920> an<00:13:22.010> important 00:13:22.449 --> 00:13:22.459 align:start position:0% nevertheless I think it's an important 00:13:22.459 --> 00:13:27.850 align:start position:0% nevertheless I think it's an important point<00:13:23.320> especially<00:13:24.320> for<00:13:26.110> code<00:13:27.110> written<00:13:27.350> in<00:13:27.680> a 00:13:27.850 --> 00:13:27.860 align:start position:0% point especially for code written in a 00:13:27.860 --> 00:13:29.410 align:start position:0% point especially for code written in a smart<00:13:28.160> contract<00:13:28.310> environment<00:13:29.120> which<00:13:29.240> is<00:13:29.390> very 00:13:29.410 --> 00:13:29.420 align:start position:0% smart contract environment which is very 00:13:29.420 --> 00:13:31.960 align:start position:0% smart contract environment which is very unforgiving<00:13:30.410> and<00:13:30.920> where<00:13:31.370> if<00:13:31.520> you 00:13:31.960 --> 00:13:31.970 align:start position:0% unforgiving and where if you 00:13:31.970 --> 00:13:34.720 align:start position:0% unforgiving and where if you you<00:13:32.690> can't<00:13:32.959> reasonably<00:13:33.620> expect<00:13:34.220> to<00:13:34.370> launch 00:13:34.720 --> 00:13:34.730 align:start position:0% you can't reasonably expect to launch 00:13:34.730 --> 00:13:40.449 align:start position:0% you can't reasonably expect to launch with<00:13:35.120> bugs<00:13:35.480> and<00:13:35.980> recover<00:13:38.709> so<00:13:39.709> I<00:13:39.740> one<00:13:40.250> thing<00:13:40.370> I 00:13:40.449 --> 00:13:40.459 align:start position:0% with bugs and recover so I one thing I 00:13:40.459 --> 00:13:42.130 align:start position:0% with bugs and recover so I one thing I think<00:13:40.640> it<00:13:40.730> makes<00:13:40.850> sense<00:13:40.970> to<00:13:41.209> do<00:13:41.330> is<00:13:41.480> step<00:13:42.020> back 00:13:42.130 --> 00:13:42.140 align:start position:0% think it makes sense to do is step back 00:13:42.140 --> 00:13:44.079 align:start position:0% think it makes sense to do is step back and<00:13:42.320> say<00:13:42.440> like<00:13:42.560> what<00:13:42.950> other<00:13:43.100> software<00:13:43.790> is 00:13:44.079 --> 00:13:44.089 align:start position:0% and say like what other software is 00:13:44.089 --> 00:13:47.860 align:start position:0% and say like what other software is written<00:13:45.080> in<00:13:45.290> environments<00:13:45.920> like<00:13:45.950> this<00:13:46.870> and 00:13:47.860 --> 00:13:47.870 align:start position:0% written in environments like this and 00:13:47.870 --> 00:13:50.740 align:start position:0% written in environments like this and and<00:13:48.760> good<00:13:49.760> examples<00:13:50.180> are<00:13:50.330> things<00:13:50.480> that<00:13:50.600> are 00:13:50.740 --> 00:13:50.750 align:start position:0% and good examples are things that are 00:13:50.750 --> 00:13:52.510 align:start position:0% and good examples are things that are called<00:13:50.930> safety<00:13:51.290> critical<00:13:51.620> software<00:13:52.010> right<00:13:52.399> so 00:13:52.510 --> 00:13:52.520 align:start position:0% called safety critical software right so 00:13:52.520 --> 00:13:57.460 align:start position:0% called safety critical software right so these<00:13:53.029> are<00:13:53.180> things<00:13:53.390> like<00:13:55.779> the<00:13:56.779> software<00:13:57.260> that 00:13:57.460 --> 00:13:57.470 align:start position:0% these are things like the software that 00:13:57.470 --> 00:14:01.150 align:start position:0% these are things like the software that monitors<00:13:58.310> nuclear<00:13:59.029> reactors<00:13:59.589> the<00:14:00.589> software 00:14:01.150 --> 00:14:01.160 align:start position:0% monitors nuclear reactors the software 00:14:01.160 --> 00:14:04.150 align:start position:0% monitors nuclear reactors the software like<00:14:01.850> the<00:14:02.000> firmware<00:14:02.270> insighting<00:14:03.160> anti-lock 00:14:04.150 --> 00:14:04.160 align:start position:0% like the firmware insighting anti-lock 00:14:04.160 --> 00:14:08.130 align:start position:0% like the firmware insighting anti-lock brake<00:14:04.430> controllers<00:14:05.980> pacemaker<00:14:06.980> firmware 00:14:08.130 --> 00:14:08.140 align:start position:0% brake controllers pacemaker firmware 00:14:08.140 --> 00:14:12.250 align:start position:0% brake controllers pacemaker firmware stuff<00:14:09.140> like<00:14:09.320> that<00:14:09.500> the<00:14:09.709> stuff<00:14:10.190> that<00:14:11.110> if<00:14:12.110> it 00:14:12.250 --> 00:14:12.260 align:start position:0% stuff like that the stuff that if it 00:14:12.260 --> 00:14:15.329 align:start position:0% stuff like that the stuff that if it fails<00:14:12.560> the<00:14:13.310> consequences<00:14:14.209> are<00:14:14.420> catastrophic 00:14:15.329 --> 00:14:15.339 align:start position:0% fails the consequences are catastrophic 00:14:15.339 --> 00:14:18.430 align:start position:0% fails the consequences are catastrophic you<00:14:16.339> know<00:14:16.430> your<00:14:16.610> brakes<00:14:16.850> fail<00:14:17.350> there's<00:14:18.350> a 00:14:18.430 --> 00:14:18.440 align:start position:0% you know your brakes fail there's a 00:14:18.440 --> 00:14:20.860 align:start position:0% you know your brakes fail there's a nuclear<00:14:18.800> meltdown<00:14:19.010> right<00:14:19.490> so<00:14:20.060> no<00:14:20.360> but<00:14:20.510> people 00:14:20.860 --> 00:14:20.870 align:start position:0% nuclear meltdown right so no but people 00:14:20.870 --> 00:14:22.600 align:start position:0% nuclear meltdown right so no but people do<00:14:21.080> write<00:14:21.320> software<00:14:21.800> in<00:14:21.950> these<00:14:22.070> environments 00:14:22.600 --> 00:14:22.610 align:start position:0% do write software in these environments 00:14:22.610 --> 00:14:25.960 align:start position:0% do write software in these environments right<00:14:23.029> and<00:14:23.240> in<00:14:24.140> many<00:14:24.350> cases<00:14:24.760> they<00:14:25.760> write 00:14:25.960 --> 00:14:25.970 align:start position:0% right and in many cases they write 00:14:25.970 --> 00:14:29.350 align:start position:0% right and in many cases they write software<00:14:26.180> and<00:14:26.630> it<00:14:26.779> works<00:14:27.080> consistently<00:14:28.360> for 00:14:29.350 --> 00:14:29.360 align:start position:0% software and it works consistently for 00:14:29.360 --> 00:14:35.380 align:start position:0% software and it works consistently for 30<00:14:29.600> years<00:14:30.670> and<00:14:33.610> if<00:14:34.610> you<00:14:34.670> look<00:14:34.970> at<00:14:35.120> if<00:14:35.270> you 00:14:35.380 --> 00:14:35.390 align:start position:0% 30 years and if you look at if you 00:14:35.390 --> 00:14:37.600 align:start position:0% 30 years and if you look at if you compare<00:14:35.690> that<00:14:35.720> to<00:14:35.870> that<00:14:36.830> sort<00:14:37.100> of<00:14:37.190> move<00:14:37.370> fast 00:14:37.600 --> 00:14:37.610 align:start position:0% compare that to that sort of move fast 00:14:37.610 --> 00:14:40.120 align:start position:0% compare that to that sort of move fast and<00:14:37.790> break<00:14:37.970> things<00:14:38.029> mentality<00:14:38.839> of<00:14:38.950> modern<00:14:39.950> web 00:14:40.120 --> 00:14:40.130 align:start position:0% and break things mentality of modern web 00:14:40.130 --> 00:14:44.350 align:start position:0% and break things mentality of modern web development<00:14:42.490> Mille<00:14:43.490> to<00:14:43.520> write<00:14:43.820> stuff<00:14:44.089> that's 00:14:44.350 --> 00:14:44.360 align:start position:0% development Mille to write stuff that's 00:14:44.360 --> 00:14:45.670 align:start position:0% development Mille to write stuff that's that<00:14:44.570> reliable<00:14:45.020> right<00:14:45.230> you're<00:14:45.350> gonna<00:14:45.440> write 00:14:45.670 --> 00:14:45.680 align:start position:0% that reliable right you're gonna write 00:14:45.680 --> 00:14:47.500 align:start position:0% that reliable right you're gonna write something<00:14:45.950> and<00:14:46.400> not<00:14:46.700> only<00:14:46.880> is<00:14:47.089> it<00:14:47.209> not<00:14:47.390> gonna 00:14:47.500 --> 00:14:47.510 align:start position:0% something and not only is it not gonna 00:14:47.510 --> 00:14:49.900 align:start position:0% something and not only is it not gonna have<00:14:47.720> bugs<00:14:47.959> it's<00:14:48.290> gonna<00:14:48.589> it's<00:14:49.190> gonna<00:14:49.339> work 00:14:49.900 --> 00:14:49.910 align:start position:0% have bugs it's gonna it's gonna work 00:14:49.910 --> 00:14:52.870 align:start position:0% have bugs it's gonna it's gonna work bug<00:14:50.300> free<00:14:50.630> for<00:14:51.140> 30<00:14:51.350> years<00:14:51.680> in<00:14:52.040> an<00:14:52.459> environment 00:14:52.870 --> 00:14:52.880 align:start position:0% bug free for 30 years in an environment 00:14:52.880 --> 00:14:53.980 align:start position:0% bug free for 30 years in an environment where<00:14:53.060> if<00:14:53.180> it<00:14:53.360> fails<00:14:53.570> there<00:14:53.810> will<00:14:53.900> be<00:14:53.930> a 00:14:53.980 --> 00:14:53.990 align:start position:0% where if it fails there will be a 00:14:53.990 --> 00:14:56.680 align:start position:0% where if it fails there will be a nuclear<00:14:54.320> meltdown<00:14:55.240> it's<00:14:56.240> a<00:14:56.300> pretty<00:14:56.480> reliable 00:14:56.680 --> 00:14:56.690 align:start position:0% nuclear meltdown it's a pretty reliable 00:14:56.690 --> 00:15:00.639 align:start position:0% nuclear meltdown it's a pretty reliable code<00:14:57.260> and<00:14:58.810> it's<00:14:59.810> so<00:15:00.110> I<00:15:00.170> think<00:15:00.350> it's<00:15:00.470> really 00:15:00.639 --> 00:15:00.649 align:start position:0% code and it's so I think it's really 00:15:00.649 --> 00:15:02.199 align:start position:0% code and it's so I think it's really worth<00:15:00.829> asking<00:15:01.040> how<00:15:01.550> do<00:15:01.610> people<00:15:02.000> actually 00:15:02.199 --> 00:15:02.209 align:start position:0% worth asking how do people actually 00:15:02.209 --> 00:15:05.579 align:start position:0% worth asking how do people actually write<00:15:02.690> code<00:15:02.750> for<00:15:03.170> environments<00:15:04.070> like<00:15:04.160> that 00:15:05.579 --> 00:15:05.589 align:start position:0% write code for environments like that 00:15:05.589 --> 00:15:10.960 align:start position:0% write code for environments like that well<00:15:06.589> so<00:15:07.300> my<00:15:08.300> co-founder<00:15:08.630> Joey<00:15:09.520> spent<00:15:10.520> a<00:15:10.670> bunch 00:15:10.960 --> 00:15:10.970 align:start position:0% well so my co-founder Joey spent a bunch 00:15:10.970 --> 00:15:12.910 align:start position:0% well so my co-founder Joey spent a bunch of<00:15:11.089> time<00:15:11.150> over<00:15:11.540> the<00:15:11.630> past<00:15:11.870> year<00:15:12.170> really 00:15:12.910 --> 00:15:12.920 align:start position:0% of time over the past year really 00:15:12.920 --> 00:15:14.980 align:start position:0% of time over the past year really searching<00:15:13.310> this<00:15:13.510> he<00:15:14.510> looked<00:15:14.690> up<00:15:14.839> the 00:15:14.980 --> 00:15:14.990 align:start position:0% searching this he looked up the 00:15:14.990 --> 00:15:17.920 align:start position:0% searching this he looked up the standards<00:15:15.769> that<00:15:16.100> are<00:15:16.850> used<00:15:17.000> to<00:15:17.389> write<00:15:17.570> code<00:15:17.899> in 00:15:17.920 --> 00:15:17.930 align:start position:0% standards that are used to write code in 00:15:17.930 --> 00:15:19.629 align:start position:0% standards that are used to write code in these<00:15:18.170> kinds<00:15:18.440> of<00:15:18.470> environments<00:15:19.010> and<00:15:19.250> there's 00:15:19.629 --> 00:15:19.639 align:start position:0% these kinds of environments and there's 00:15:19.639 --> 00:15:22.210 align:start position:0% these kinds of environments and there's actually<00:15:19.910> several<00:15:20.120> of<00:15:20.269> them<00:15:20.860> misra<00:15:21.860> is<00:15:22.040> the 00:15:22.210 --> 00:15:22.220 align:start position:0% actually several of them misra is the 00:15:22.220 --> 00:15:24.400 align:start position:0% actually several of them misra is the one<00:15:22.399> used<00:15:22.550> as<00:15:22.820> a<00:15:23.240> C<00:15:23.540> coding<00:15:23.839> standard<00:15:24.170> used<00:15:24.290> by 00:15:24.400 --> 00:15:24.410 align:start position:0% one used as a C coding standard used by 00:15:24.410 --> 00:15:29.920 align:start position:0% one used as a C coding standard used by the<00:15:24.470> automotive<00:15:24.920> industry<00:15:27.250> NASA<00:15:28.250> and<00:15:28.550> JPL<00:15:28.930> Jet 00:15:29.920 --> 00:15:29.930 align:start position:0% the automotive industry NASA and JPL Jet 00:15:29.930 --> 00:15:31.210 align:start position:0% the automotive industry NASA and JPL Jet Propulsion<00:15:29.959> Laboratory<00:15:30.440> they<00:15:30.860> have<00:15:30.980> their 00:15:31.210 --> 00:15:31.220 align:start position:0% Propulsion Laboratory they have their 00:15:31.220 --> 00:15:34.060 align:start position:0% Propulsion Laboratory they have their their<00:15:31.579> own<00:15:31.760> coding<00:15:32.510> standard<00:15:33.070> there's 00:15:34.060 --> 00:15:34.070 align:start position:0% their own coding standard there's 00:15:34.070 --> 00:15:35.740 align:start position:0% their own coding standard there's another<00:15:34.279> there's<00:15:35.060> like<00:15:35.180> a<00:15:35.209> restrictive 00:15:35.740 --> 00:15:35.750 align:start position:0% another there's like a restrictive 00:15:35.750 --> 00:15:38.110 align:start position:0% another there's like a restrictive subset<00:15:36.230> of<00:15:36.440> the<00:15:36.769> ADA<00:15:36.920> language<00:15:37.370> called<00:15:37.670> spark 00:15:38.110 --> 00:15:38.120 align:start position:0% subset of the ADA language called spark 00:15:38.120 --> 00:15:39.519 align:start position:0% subset of the ADA language called spark that's<00:15:38.480> also<00:15:38.750> used<00:15:38.899> in<00:15:39.050> these<00:15:39.170> kinds<00:15:39.470> of 00:15:39.519 --> 00:15:39.529 align:start position:0% that's also used in these kinds of 00:15:39.529 --> 00:15:41.949 align:start position:0% that's also used in these kinds of environments<00:15:40.089> and<00:15:41.089> there's<00:15:41.630> a<00:15:41.690> lot<00:15:41.839> of 00:15:41.949 --> 00:15:41.959 align:start position:0% environments and there's a lot of 00:15:41.959 --> 00:15:44.819 align:start position:0% environments and there's a lot of commonalities<00:15:42.560> between<00:15:42.680> these<00:15:43.579> different 00:15:44.819 --> 00:15:44.829 align:start position:0% commonalities between these different 00:15:44.829 --> 00:15:48.129 align:start position:0% commonalities between these different these<00:15:45.829> different<00:15:46.269> safety<00:15:47.269> critical<00:15:47.449> coding 00:15:48.129 --> 00:15:48.139 align:start position:0% these different safety critical coding 00:15:48.139 --> 00:15:50.410 align:start position:0% these different safety critical coding standards<00:15:48.529> one<00:15:49.040> is<00:15:49.160> that<00:15:49.310> they<00:15:49.639> always<00:15:50.029> use<00:15:50.240> a 00:15:50.410 --> 00:15:50.420 align:start position:0% standards one is that they always use a 00:15:50.420 --> 00:15:54.639 align:start position:0% standards one is that they always use a restricted<00:15:51.350> subset<00:15:51.920> of<00:15:52.510> a<00:15:53.510> language<00:15:53.899> I<00:15:54.199> mean 00:15:54.639 --> 00:15:54.649 align:start position:0% restricted subset of a language I mean 00:15:54.649 --> 00:15:56.350 align:start position:0% restricted subset of a language I mean you<00:15:54.920> take<00:15:55.070> some<00:15:55.519> mysteries<00:15:55.820> of<00:15:55.940> C<00:15:56.060> coding 00:15:56.350 --> 00:15:56.360 align:start position:0% you take some mysteries of C coding 00:15:56.360 --> 00:15:57.430 align:start position:0% you take some mysteries of C coding standard<00:15:56.660> now<00:15:56.750> sees<00:15:56.959> a<00:15:56.990> pretty<00:15:57.230> small 00:15:57.430 --> 00:15:57.440 align:start position:0% standard now sees a pretty small 00:15:57.440 --> 00:16:00.720 align:start position:0% standard now sees a pretty small language<00:15:57.769> to<00:15:57.889> begin<00:15:58.100> with<00:15:58.510> it's<00:15:59.510> not<00:15:59.630> like 00:16:00.720 --> 00:16:00.730 align:start position:0% language to begin with it's not like 00:16:00.730 --> 00:16:03.430 align:start position:0% language to begin with it's not like well<00:16:01.730> it's<00:16:01.820> not<00:16:01.880> like<00:16:02.029> say<00:16:02.209> C++<00:16:02.779> which<00:16:03.019> is<00:16:03.139> just 00:16:03.430 --> 00:16:03.440 align:start position:0% well it's not like say C++ which is just 00:16:03.440 --> 00:16:06.280 align:start position:0% well it's not like say C++ which is just all<00:16:04.399> kinds<00:16:04.699> of<00:16:04.760> features<00:16:04.910> this<00:16:05.870> is<00:16:06.019> a<00:16:06.050> fairly 00:16:06.280 --> 00:16:06.290 align:start position:0% all kinds of features this is a fairly 00:16:06.290 --> 00:16:08.439 align:start position:0% all kinds of features this is a fairly small<00:16:06.470> language<00:16:07.130> but<00:16:07.339> mr.<00:16:07.699> C<00:16:07.880> is<00:16:08.029> actually<00:16:08.209> a 00:16:08.439 --> 00:16:08.449 align:start position:0% small language but mr. C is actually a 00:16:08.449 --> 00:16:13.120 align:start position:0% small language but mr. C is actually a subset<00:16:08.990> of<00:16:09.199> C<00:16:09.769> and<00:16:11.380> it's<00:16:12.380> a<00:16:12.500> subset<00:16:12.860> it<00:16:13.010> has 00:16:13.120 --> 00:16:13.130 align:start position:0% subset of C and it's a subset it has 00:16:13.130 --> 00:16:16.360 align:start position:0% subset of C and it's a subset it has fewer<00:16:13.459> features<00:16:14.019> it's<00:16:15.019> designed<00:16:15.410> to<00:16:15.529> be<00:16:15.800> less 00:16:16.360 --> 00:16:16.370 align:start position:0% fewer features it's designed to be less 00:16:16.370 --> 00:16:20.130 align:start position:0% fewer features it's designed to be less abstract<00:16:17.000> and<00:16:17.800> it's<00:16:18.800> designed<00:16:19.160> to<00:16:19.220> just<00:16:19.550> be 00:16:20.130 --> 00:16:20.140 align:start position:0% abstract and it's designed to just be 00:16:20.140 --> 00:16:24.250 align:start position:0% abstract and it's designed to just be safer<00:16:21.140> by<00:16:21.320> sort<00:16:21.560> of<00:16:21.620> just<00:16:21.890> being<00:16:22.070> simpler<00:16:23.260> and 00:16:24.250 --> 00:16:24.260 align:start position:0% safer by sort of just being simpler and 00:16:24.260 --> 00:16:26.560 align:start position:0% safer by sort of just being simpler and really<00:16:24.560> if<00:16:24.649> you<00:16:24.740> could<00:16:24.860> encapsulate<00:16:25.339> the<00:16:26.240> the 00:16:26.560 --> 00:16:26.570 align:start position:0% really if you could encapsulate the the 00:16:26.570 --> 00:16:29.769 align:start position:0% really if you could encapsulate the the goal<00:16:26.779> is<00:16:27.730> just<00:16:28.730> catch<00:16:28.940> as<00:16:29.060> many<00:16:29.240> bugs<00:16:29.510> as<00:16:29.690> you 00:16:29.769 --> 00:16:29.779 align:start position:0% goal is just catch as many bugs as you 00:16:29.779 --> 00:16:38.079 align:start position:0% goal is just catch as many bugs as you can<00:16:29.990> with<00:16:30.199> static<00:16:30.860> analysis<00:16:36.550> so<00:16:37.550> bounty 00:16:38.079 --> 00:16:38.089 align:start position:0% can with static analysis so bounty 00:16:38.089 --> 00:16:41.199 align:start position:0% can with static analysis so bounty number<00:16:38.300> two<00:16:38.449> is<00:16:39.279> what<00:16:40.279> I'm<00:16:40.399> calling<00:16:40.579> super 00:16:41.199 --> 00:16:41.209 align:start position:0% number two is what I'm calling super 00:16:41.209 --> 00:16:45.000 align:start position:0% number two is what I'm calling super simple<00:16:41.600> solidity<00:16:42.940> so<00:16:43.940> this<00:16:44.060> is<00:16:44.180> sort<00:16:44.329> of<00:16:44.390> like 00:16:45.000 --> 00:16:45.010 align:start position:0% simple solidity so this is sort of like 00:16:45.010 --> 00:16:51.370 align:start position:0% simple solidity so this is sort of like mr.<00:16:46.010> Mishra<00:16:46.640> for<00:16:46.850> solidity<00:16:47.269> and<00:16:48.010> I<00:16:50.380> would 00:16:51.370 --> 00:16:51.380 align:start position:0% mr. Mishra for solidity and I would 00:16:51.380 --> 00:16:53.319 align:start position:0% mr. Mishra for solidity and I would really<00:16:51.529> like<00:16:51.740> to<00:16:51.920> see<00:16:52.100> a<00:16:52.130> basically<00:16:53.120> just<00:16:53.209> a 00:16:53.319 --> 00:16:53.329 align:start position:0% really like to see a basically just a 00:16:53.329 --> 00:16:56.800 align:start position:0% really like to see a basically just a pragma<00:16:53.839> for<00:16:54.079> a<00:16:54.110> solidity<00:16:54.560> and<00:16:55.630> this<00:16:56.630> would 00:16:56.800 --> 00:16:56.810 align:start position:0% pragma for a solidity and this would 00:16:56.810 --> 00:16:59.620 align:start position:0% pragma for a solidity and this would just<00:16:56.930> be<00:16:57.019> a<00:16:57.140> safe<00:16:57.620> simple<00:16:58.399> very<00:16:58.850> restricted 00:16:59.620 --> 00:16:59.630 align:start position:0% just be a safe simple very restricted 00:16:59.630 --> 00:17:02.139 align:start position:0% just be a safe simple very restricted subset<00:17:00.140> of<00:17:00.290> solidity<00:17:01.279> so<00:17:01.519> here<00:17:01.910> are<00:17:02.000> some 00:17:02.139 --> 00:17:02.149 align:start position:0% subset of solidity so here are some 00:17:02.149 --> 00:17:05.189 align:start position:0% subset of solidity so here are some examples<00:17:02.600> right<00:17:03.170> and<00:17:03.410> this<00:17:04.370> may<00:17:05.120> seem 00:17:05.189 --> 00:17:05.199 align:start position:0% examples right and this may seem 00:17:05.199 --> 00:17:07.929 align:start position:0% examples right and this may seem absurdly<00:17:06.199> restrictive<00:17:06.949> depending<00:17:07.699> on<00:17:07.790> what 00:17:07.929 --> 00:17:07.939 align:start position:0% absurdly restrictive depending on what 00:17:07.939 --> 00:17:10.120 align:start position:0% absurdly restrictive depending on what kind<00:17:08.179> of<00:17:08.240> programming<00:17:08.660> you're<00:17:08.929> used<00:17:09.110> to<00:17:09.230> but 00:17:10.120 --> 00:17:10.130 align:start position:0% kind of programming you're used to but 00:17:10.130 --> 00:17:14.829 align:start position:0% kind of programming you're used to but these<00:17:11.559> these<00:17:12.559> restrictions<00:17:13.100> are<00:17:13.579> the<00:17:14.510> kinds 00:17:14.829 --> 00:17:14.839 align:start position:0% these these restrictions are the kinds 00:17:14.839 --> 00:17:16.059 align:start position:0% these these restrictions are the kinds of<00:17:14.929> things<00:17:15.110> that<00:17:15.169> you<00:17:15.380> find<00:17:15.530> in<00:17:15.709> the<00:17:15.770> mistress 00:17:16.059 --> 00:17:16.069 align:start position:0% of things that you find in the mistress 00:17:16.069 --> 00:17:19.270 align:start position:0% of things that you find in the mistress standard<00:17:16.429> for<00:17:16.790> example<00:17:17.150> no<00:17:17.809> inheritance<00:17:18.280> no 00:17:19.270 --> 00:17:19.280 align:start position:0% standard for example no inheritance no 00:17:19.280 --> 00:17:23.069 align:start position:0% standard for example no inheritance no recursion<00:17:19.660> no<00:17:20.660> implicit<00:17:21.020> types<00:17:21.380> right<00:17:21.650> no<00:17:21.860> var 00:17:23.069 --> 00:17:23.079 align:start position:0% recursion no implicit types right no var 00:17:23.079 --> 00:17:25.490 align:start position:0% recursion no implicit types right no var no<00:17:24.079> function<00:17:24.409> overloading 00:17:25.490 --> 00:17:25.500 align:start position:0% no function overloading 00:17:25.500 --> 00:17:27.409 align:start position:0% no function overloading and<00:17:26.069> we've<00:17:26.309> got<00:17:26.429> a<00:17:26.459> whole<00:17:26.579> I'm<00:17:26.760> not<00:17:27.120> gonna<00:17:27.240> list 00:17:27.409 --> 00:17:27.419 align:start position:0% and we've got a whole I'm not gonna list 00:17:27.419 --> 00:17:28.429 align:start position:0% and we've got a whole I'm not gonna list them<00:17:27.569> all<00:17:27.630> here<00:17:27.780> but<00:17:27.839> we<00:17:27.959> have<00:17:28.049> a<00:17:28.079> whole<00:17:28.230> list 00:17:28.429 --> 00:17:28.439 align:start position:0% them all here but we have a whole list 00:17:28.439 --> 00:17:32.899 align:start position:0% them all here but we have a whole list of<00:17:28.710> things<00:17:29.240> that<00:17:31.190> we<00:17:32.190> would<00:17:32.309> like<00:17:32.400> to<00:17:32.460> see 00:17:32.899 --> 00:17:32.909 align:start position:0% of things that we would like to see 00:17:32.909 --> 00:17:35.149 align:start position:0% of things that we would like to see excluded<00:17:33.539> from<00:17:33.720> this<00:17:34.200> sort<00:17:34.440> of<00:17:34.500> very<00:17:34.710> simple 00:17:35.149 --> 00:17:35.159 align:start position:0% excluded from this sort of very simple 00:17:35.159 --> 00:17:39.080 align:start position:0% excluded from this sort of very simple solidity<00:17:35.850> subset<00:17:36.390> and<00:17:37.520> so<00:17:38.520> if<00:17:38.640> you<00:17:38.730> create 00:17:39.080 --> 00:17:39.090 align:start position:0% solidity subset and so if you create 00:17:39.090 --> 00:17:42.560 align:start position:0% solidity subset and so if you create this<00:17:39.330> pragma<00:17:40.429> you<00:17:41.429> get<00:17:41.669> one<00:17:42.120> thousand<00:17:42.510> two 00:17:42.560 --> 00:17:42.570 align:start position:0% this pragma you get one thousand two 00:17:42.570 --> 00:17:46.549 align:start position:0% this pragma you get one thousand two hundred<00:17:42.630> fifty<00:17:42.990> rep<00:17:43.350> I<00:17:45.169> need<00:17:46.169> to<00:17:46.260> move<00:17:46.409> this 00:17:46.549 --> 00:17:46.559 align:start position:0% hundred fifty rep I need to move this 00:17:46.559 --> 00:17:47.840 align:start position:0% hundred fifty rep I need to move this along<00:17:46.770> cuz<00:17:47.039> it<00:17:47.130> looks<00:17:47.250> like<00:17:47.400> I'm<00:17:47.520> running<00:17:47.610> out 00:17:47.840 --> 00:17:47.850 align:start position:0% along cuz it looks like I'm running out 00:17:47.850 --> 00:17:55.700 align:start position:0% along cuz it looks like I'm running out of<00:17:47.880> time<00:17:50.240> okay<00:17:53.360> so<00:17:54.360> to<00:17:55.260> go<00:17:55.380> through<00:17:55.530> the<00:17:55.590> rest 00:17:55.700 --> 00:17:55.710 align:start position:0% of time okay so to go through the rest 00:17:55.710 --> 00:17:58.850 align:start position:0% of time okay so to go through the rest of<00:17:55.890> this<00:17:55.980> quickly<00:17:56.250> the<00:17:57.440> anybody<00:17:58.440> ever<00:17:58.650> seen 00:17:58.850 --> 00:17:58.860 align:start position:0% of this quickly the anybody ever seen 00:17:58.860 --> 00:18:01.299 align:start position:0% of this quickly the anybody ever seen this<00:17:59.010> exception<00:17:59.610> exception<00:18:00.240> stack<00:18:00.570> to<00:18:00.809> deep 00:18:01.299 --> 00:18:01.309 align:start position:0% this exception exception stack to deep 00:18:01.309 --> 00:18:04.159 align:start position:0% this exception exception stack to deep solidity<00:18:02.309> has<00:18:02.580> this<00:18:02.760> has<00:18:03.210> a<00:18:03.240> quirk<00:18:03.900> where 00:18:04.159 --> 00:18:04.169 align:start position:0% solidity has this has a quirk where 00:18:04.169 --> 00:18:06.770 align:start position:0% solidity has this has a quirk where local<00:18:05.159> variables<00:18:05.580> and<00:18:05.669> parameters<00:18:05.850> they<00:18:06.659> go 00:18:06.770 --> 00:18:06.780 align:start position:0% local variables and parameters they go 00:18:06.780 --> 00:18:09.640 align:start position:0% local variables and parameters they go on<00:18:06.929> the<00:18:07.020> stack<00:18:07.289> and<00:18:07.740> the<00:18:08.280> stack<00:18:08.309> can<00:18:08.820> only<00:18:09.000> be<00:18:09.240> a 00:18:09.640 --> 00:18:09.650 align:start position:0% on the stack and the stack can only be a 00:18:09.650 --> 00:18:11.899 align:start position:0% on the stack and the stack can only be a certain<00:18:10.650> depth<00:18:10.890> sort<00:18:11.280> of<00:18:11.370> depending<00:18:11.730> what's 00:18:11.899 --> 00:18:11.909 align:start position:0% certain depth sort of depending what's 00:18:11.909 --> 00:18:14.060 align:start position:0% certain depth sort of depending what's on<00:18:12.059> it<00:18:12.210> so<00:18:12.510> we<00:18:13.049> have<00:18:13.140> between<00:18:13.409> 8<00:18:13.710> and<00:18:13.919> 16 00:18:14.060 --> 00:18:14.070 align:start position:0% on it so we have between 8 and 16 00:18:14.070 --> 00:18:18.080 align:start position:0% on it so we have between 8 and 16 variables<00:18:14.820> something<00:18:15.360> like<00:18:15.480> that<00:18:16.909> one<00:18:17.909> kind 00:18:18.080 --> 00:18:18.090 align:start position:0% variables something like that one kind 00:18:18.090 --> 00:18:20.240 align:start position:0% variables something like that one kind of<00:18:18.150> one<00:18:18.440> one<00:18:19.440> thing<00:18:19.559> that's<00:18:19.710> a<00:18:19.770> little<00:18:19.980> awkward 00:18:20.240 --> 00:18:20.250 align:start position:0% of one one thing that's a little awkward 00:18:20.250 --> 00:18:22.310 align:start position:0% of one one thing that's a little awkward about<00:18:20.340> it<00:18:20.580> is<00:18:20.700> anytime<00:18:21.510> you<00:18:21.690> allocate<00:18:22.200> a<00:18:22.230> new 00:18:22.310 --> 00:18:22.320 align:start position:0% about it is anytime you allocate a new 00:18:22.320 --> 00:18:24.860 align:start position:0% about it is anytime you allocate a new variable<00:18:22.770> in<00:18:22.860> solidity<00:18:23.280> it<00:18:23.490> puts<00:18:24.270> a<00:18:24.360> very<00:18:24.510> puts 00:18:24.860 --> 00:18:24.870 align:start position:0% variable in solidity it puts a very puts 00:18:24.870 --> 00:18:27.409 align:start position:0% variable in solidity it puts a very puts it<00:18:24.929> on<00:18:25.020> the<00:18:25.140> stack<00:18:25.380> but<00:18:25.830> there<00:18:26.330> there's<00:18:27.330> an 00:18:27.409 --> 00:18:27.419 align:start position:0% it on the stack but there there's an 00:18:27.419 --> 00:18:29.180 align:start position:0% it on the stack but there there's an actually<00:18:27.690> way<00:18:27.780> to<00:18:27.840> pop<00:18:28.080> it<00:18:28.200> off<00:18:28.350> the<00:18:28.530> stack<00:18:28.799> at 00:18:29.180 --> 00:18:29.190 align:start position:0% actually way to pop it off the stack at 00:18:29.190 --> 00:18:30.490 align:start position:0% actually way to pop it off the stack at least<00:18:29.370> not<00:18:29.549> without<00:18:29.640> was<00:18:30.030> not<00:18:30.360> without 00:18:30.490 --> 00:18:30.500 align:start position:0% least not without was not without 00:18:30.500 --> 00:18:36.110 align:start position:0% least not without was not without digging<00:18:31.500> down<00:18:31.740> into<00:18:31.909> assembly<00:18:34.490> serpent<00:18:35.490> which 00:18:36.110 --> 00:18:36.120 align:start position:0% digging down into assembly serpent which 00:18:36.120 --> 00:18:39.799 align:start position:0% digging down into assembly serpent which I<00:18:36.450> missed<00:18:37.289> terribly<00:18:38.150> sermon<00:18:39.150> had<00:18:39.299> both<00:18:39.510> stack 00:18:39.799 --> 00:18:39.809 align:start position:0% I missed terribly sermon had both stack 00:18:39.809 --> 00:18:41.990 align:start position:0% I missed terribly sermon had both stack and<00:18:40.020> memory<00:18:40.320> variables<00:18:40.710> and<00:18:41.490> you<00:18:41.580> could<00:18:41.700> pop 00:18:41.990 --> 00:18:42.000 align:start position:0% and memory variables and you could pop 00:18:42.000 --> 00:18:43.190 align:start position:0% and memory variables and you could pop variables<00:18:42.419> off<00:18:42.539> the<00:18:42.630> stack<00:18:42.809> if<00:18:42.960> you<00:18:43.020> needed 00:18:43.190 --> 00:18:43.200 align:start position:0% variables off the stack if you needed 00:18:43.200 --> 00:18:44.529 align:start position:0% variables off the stack if you needed which<00:18:43.350> seems<00:18:43.559> like<00:18:44.010> a<00:18:44.039> pretty<00:18:44.159> reasonable 00:18:44.529 --> 00:18:44.539 align:start position:0% which seems like a pretty reasonable 00:18:44.539 --> 00:18:47.419 align:start position:0% which seems like a pretty reasonable system<00:18:45.539> to<00:18:45.659> me<00:18:45.780> right<00:18:46.409> nothing<00:18:47.070> on<00:18:47.159> the<00:18:47.220> stack 00:18:47.419 --> 00:18:47.429 align:start position:0% system to me right nothing on the stack 00:18:47.429 --> 00:18:50.450 align:start position:0% system to me right nothing on the stack uses<00:18:48.150> the<00:18:48.240> whiff<00:18:48.419> keyword<00:18:48.890> to<00:18:49.890> put<00:18:50.130> something 00:18:50.450 --> 00:18:50.460 align:start position:0% uses the whiff keyword to put something 00:18:50.460 --> 00:18:52.940 align:start position:0% uses the whiff keyword to put something on<00:18:50.700> the<00:18:50.970> stack<00:18:51.179> and<00:18:51.510> then<00:18:52.470> when<00:18:52.559> you<00:18:52.650> axe<00:18:52.799> it 00:18:52.940 --> 00:18:52.950 align:start position:0% on the stack and then when you axe it 00:18:52.950 --> 00:19:00.380 align:start position:0% on the stack and then when you axe it there's<00:18:53.130> nothing<00:18:53.340> on<00:18:53.429> the<00:18:53.490> stack<00:18:53.669> again<00:18:59.390> so 00:19:00.380 --> 00:19:00.390 align:start position:0% there's nothing on the stack again so 00:19:00.390 --> 00:19:03.320 align:start position:0% there's nothing on the stack again so body<00:19:00.570> number<00:19:00.780> three<00:19:01.020> is<00:19:01.200> a<00:19:01.789> stack<00:19:02.789> popper 00:19:03.320 --> 00:19:03.330 align:start position:0% body number three is a stack popper 00:19:03.330 --> 00:19:06.409 align:start position:0% body number three is a stack popper feature<00:19:03.570> four<00:19:03.900> solidity<00:19:04.320> I<00:19:05.000> so<00:19:06.000> this<00:19:06.120> is<00:19:06.240> just 00:19:06.409 --> 00:19:06.419 align:start position:0% feature four solidity I so this is just 00:19:06.419 --> 00:19:07.970 align:start position:0% feature four solidity I so this is just a<00:19:06.510> way<00:19:06.659> of<00:19:06.840> removing<00:19:07.110> local<00:19:07.500> variables<00:19:07.890> from 00:19:07.970 --> 00:19:07.980 align:start position:0% a way of removing local variables from 00:19:07.980 --> 00:19:09.580 align:start position:0% a way of removing local variables from the<00:19:08.070> stack<00:19:08.340> without<00:19:08.730> digging<00:19:09.059> down<00:19:09.330> into 00:19:09.580 --> 00:19:09.590 align:start position:0% the stack without digging down into 00:19:09.590 --> 00:19:12.590 align:start position:0% the stack without digging down into assembly<00:19:11.000> doesn't<00:19:12.000> act<00:19:12.120> doesn't<00:19:12.360> even<00:19:12.480> have 00:19:12.590 --> 00:19:12.600 align:start position:0% assembly doesn't act doesn't even have 00:19:12.600 --> 00:19:13.940 align:start position:0% assembly doesn't act doesn't even have to<00:19:12.659> work<00:19:12.809> for<00:19:13.020> function<00:19:13.409> parameters<00:19:13.830> just 00:19:13.940 --> 00:19:13.950 align:start position:0% to work for function parameters just 00:19:13.950 --> 00:19:17.120 align:start position:0% to work for function parameters just talking<00:19:14.640> about<00:19:14.730> local<00:19:14.970> variables<00:19:15.419> here<00:19:16.130> yeah 00:19:17.120 --> 00:19:17.130 align:start position:0% talking about local variables here yeah 00:19:17.130 --> 00:19:18.470 align:start position:0% talking about local variables here yeah you<00:19:17.190> can<00:19:17.460> sort<00:19:17.760> of<00:19:17.820> accomplish<00:19:18.210> the<00:19:18.330> same 00:19:18.470 --> 00:19:18.480 align:start position:0% you can sort of accomplish the same 00:19:18.480 --> 00:19:20.870 align:start position:0% you can sort of accomplish the same thing<00:19:18.690> with<00:19:18.840> function<00:19:19.200> calls<00:19:19.610> but<00:19:20.610> it<00:19:20.789> would 00:19:20.870 --> 00:19:20.880 align:start position:0% thing with function calls but it would 00:19:20.880 --> 00:19:22.220 align:start position:0% thing with function calls but it would also<00:19:21.000> be<00:19:21.210> really<00:19:21.330> nice<00:19:21.600> to<00:19:21.750> be<00:19:21.809> able<00:19:21.870> to<00:19:22.020> clear 00:19:22.220 --> 00:19:22.230 align:start position:0% also be really nice to be able to clear 00:19:22.230 --> 00:19:26.029 align:start position:0% also be really nice to be able to clear off<00:19:22.350> the<00:19:22.470> stack<00:19:24.440> the<00:19:25.440> solidity<00:19:25.770> devs 00:19:26.029 --> 00:19:26.039 align:start position:0% off the stack the solidity devs 00:19:26.039 --> 00:19:28.159 align:start position:0% off the stack the solidity devs themselves<00:19:26.700> claim<00:19:26.909> this<00:19:27.150> christian<00:19:27.630> alex<00:19:28.049> so 00:19:28.159 --> 00:19:28.169 align:start position:0% themselves claim this christian alex so 00:19:28.169 --> 00:19:32.480 align:start position:0% themselves claim this christian alex so you<00:19:28.230> guys<00:19:28.380> in<00:19:28.559> here<00:19:29.630> or<00:19:30.630> really<00:19:31.590> anyone<00:19:31.919> but 00:19:32.480 --> 00:19:32.490 align:start position:0% you guys in here or really anyone but 00:19:32.490 --> 00:19:33.770 align:start position:0% you guys in here or really anyone but it's<00:19:32.610> open<00:19:32.820> anyone<00:19:33.120> who<00:19:33.210> wants<00:19:33.419> to<00:19:33.480> submit<00:19:33.659> a 00:19:33.770 --> 00:19:33.780 align:start position:0% it's open anyone who wants to submit a 00:19:33.780 --> 00:19:35.299 align:start position:0% it's open anyone who wants to submit a PR<00:19:34.049> as<00:19:34.169> long<00:19:34.260> as<00:19:34.350> your<00:19:34.470> PRI<00:19:34.710> is<00:19:34.799> accepted<00:19:35.250> you 00:19:35.299 --> 00:19:35.309 align:start position:0% PR as long as your PRI is accepted you 00:19:35.309 --> 00:19:44.180 align:start position:0% PR as long as your PRI is accepted you get<00:19:35.429> a<00:19:35.460> thousand<00:19:35.789> wrap 00:19:44.180 --> 00:19:44.190 align:start position:0% 00:19:44.190 --> 00:19:46.760 align:start position:0% currently<00:19:45.190> there's<00:19:45.520> actually<00:19:45.789> not<00:19:45.909> a<00:19:46.120> way<00:19:46.360> to 00:19:46.760 --> 00:19:46.770 align:start position:0% currently there's actually not a way to 00:19:46.770 --> 00:19:49.649 align:start position:0% currently there's actually not a way to get<00:19:47.770> return<00:19:48.100> values<00:19:48.460> if<00:19:49.029> you<00:19:49.090> do<00:19:49.299> a<00:19:49.330> send 00:19:49.649 --> 00:19:49.659 align:start position:0% get return values if you do a send 00:19:49.659 --> 00:19:52.789 align:start position:0% get return values if you do a send transaction<00:19:50.230> to<00:19:50.409> any<00:19:51.130> theory<00:19:51.340> of<00:19:51.399> node<00:19:51.610> which 00:19:52.789 --> 00:19:52.799 align:start position:0% transaction to any theory of node which 00:19:52.799 --> 00:19:55.139 align:start position:0% transaction to any theory of node which actually<00:19:53.799> surprises<00:19:54.309> a<00:19:54.340> lot<00:19:54.399> of<00:19:54.549> people<00:19:54.880> at 00:19:55.139 --> 00:19:55.149 align:start position:0% actually surprises a lot of people at 00:19:55.149 --> 00:19:57.930 align:start position:0% actually surprises a lot of people at first<00:19:55.500> but<00:19:56.500> if<00:19:56.860> you<00:19:56.980> do<00:19:57.159> a<00:19:57.190> send<00:19:57.460> transaction 00:19:57.930 --> 00:19:57.940 align:start position:0% first but if you do a send transaction 00:19:57.940 --> 00:19:59.250 align:start position:0% first but if you do a send transaction you<00:19:58.000> actually<00:19:58.270> just<00:19:58.419> get<00:19:58.539> back<00:19:58.690> a<00:19:58.720> transaction 00:19:59.250 --> 00:19:59.260 align:start position:0% you actually just get back a transaction 00:19:59.260 --> 00:20:01.590 align:start position:0% you actually just get back a transaction hash<00:19:59.440> you<00:19:59.649> do<00:19:59.799> not<00:19:59.980> get<00:20:00.220> back<00:20:00.399> and<00:20:00.880> at<00:20:01.360> the 00:20:01.590 --> 00:20:01.600 align:start position:0% hash you do not get back and at the 00:20:01.600 --> 00:20:03.750 align:start position:0% hash you do not get back and at the actual<00:20:01.840> return<00:20:02.049> value<00:20:02.470> and<00:20:02.679> in<00:20:03.130> fact<00:20:03.370> that 00:20:03.750 --> 00:20:03.760 align:start position:0% actual return value and in fact that 00:20:03.760 --> 00:20:06.510 align:start position:0% actual return value and in fact that return<00:20:04.090> value<00:20:04.120> is<00:20:04.480> not<00:20:05.110> accessible<00:20:05.770> anywhere 00:20:06.510 --> 00:20:06.520 align:start position:0% return value is not accessible anywhere 00:20:06.520 --> 00:20:13.049 align:start position:0% return value is not accessible anywhere at<00:20:06.940> all<00:20:07.799> now<00:20:09.029> if<00:20:10.029> your<00:20:10.419> return<00:20:10.630> value<00:20:11.580> isn't<00:20:12.580> it 00:20:13.049 --> 00:20:13.059 align:start position:0% at all now if your return value isn't it 00:20:13.059 --> 00:20:16.289 align:start position:0% at all now if your return value isn't it doesn't<00:20:13.179> have<00:20:13.360> any<00:20:13.480> dependence<00:20:13.960> on<00:20:14.080> State<00:20:15.299> if 00:20:16.289 --> 00:20:16.299 align:start position:0% doesn't have any dependence on State if 00:20:16.299 --> 00:20:17.909 align:start position:0% doesn't have any dependence on State if it's<00:20:16.480> just<00:20:16.720> based<00:20:16.899> on<00:20:17.080> the<00:20:17.230> input<00:20:17.529> data<00:20:17.649> then 00:20:17.909 --> 00:20:17.919 align:start position:0% it's just based on the input data then 00:20:17.919 --> 00:20:19.950 align:start position:0% it's just based on the input data then you<00:20:18.039> can<00:20:18.070> rerun<00:20:18.669> the<00:20:18.850> same<00:20:19.059> input<00:20:19.419> data<00:20:19.630> as<00:20:19.899> a 00:20:19.950 --> 00:20:19.960 align:start position:0% you can rerun the same input data as a 00:20:19.960 --> 00:20:22.620 align:start position:0% you can rerun the same input data as a call<00:20:20.740> and<00:20:21.190> that<00:20:21.850> will<00:20:21.970> give<00:20:22.120> you<00:20:22.240> the<00:20:22.360> return 00:20:22.620 --> 00:20:22.630 align:start position:0% call and that will give you the return 00:20:22.630 --> 00:20:31.100 align:start position:0% call and that will give you the return value<00:20:22.929> okay<00:20:25.529> but<00:20:26.529> if<00:20:26.950> you<00:20:29.520> on<00:20:30.520> the<00:20:30.580> timestamp 00:20:31.100 --> 00:20:31.110 align:start position:0% value okay but if you on the timestamp 00:20:31.110 --> 00:20:34.470 align:start position:0% value okay but if you on the timestamp then<00:20:32.220> there's<00:20:33.220> actually<00:20:33.429> no<00:20:33.850> way<00:20:34.000> to<00:20:34.059> get<00:20:34.330> it 00:20:34.470 --> 00:20:34.480 align:start position:0% then there's actually no way to get it 00:20:34.480 --> 00:20:38.399 align:start position:0% then there's actually no way to get it now<00:20:35.200> it's<00:20:36.159> computable<00:20:36.700> by<00:20:36.820> the<00:20:36.880> caller<00:20:37.409> using 00:20:38.399 --> 00:20:38.409 align:start position:0% now it's computable by the caller using 00:20:38.409 --> 00:20:40.500 align:start position:0% now it's computable by the caller using commands<00:20:39.130> -<00:20:39.610> nice<00:20:39.760> library<00:20:40.000> but<00:20:40.299> this<00:20:40.390> is 00:20:40.500 --> 00:20:40.510 align:start position:0% commands - nice library but this is 00:20:40.510 --> 00:20:42.120 align:start position:0% commands - nice library but this is somewhat<00:20:40.809> heavyweight<00:20:41.230> it's<00:20:41.440> inconvenient 00:20:42.120 --> 00:20:42.130 align:start position:0% somewhat heavyweight it's inconvenient 00:20:42.130 --> 00:20:43.830 align:start position:0% somewhat heavyweight it's inconvenient I<00:20:42.250> think<00:20:43.000> the<00:20:43.090> etherium<00:20:43.510> I<00:20:43.600> think<00:20:43.720> it'd<00:20:43.779> be 00:20:43.830 --> 00:20:43.840 align:start position:0% I think the etherium I think it'd be 00:20:43.840 --> 00:20:45.360 align:start position:0% I think the etherium I think it'd be really<00:20:43.990> great<00:20:44.200> if<00:20:44.350> the<00:20:44.470> etherium<00:20:44.860> notes<00:20:45.070> just 00:20:45.360 --> 00:20:45.370 align:start position:0% really great if the etherium notes just 00:20:45.370 --> 00:20:54.570 align:start position:0% really great if the etherium notes just would<00:20:46.120> provide<00:20:46.480> the<00:20:46.720> return<00:20:47.289> value<00:20:53.100> and<00:20:54.100> so 00:20:54.570 --> 00:20:54.580 align:start position:0% would provide the return value and so 00:20:54.580 --> 00:20:56.250 align:start position:0% would provide the return value and so this<00:20:54.970> is<00:20:55.120> the<00:20:55.270> fourth<00:20:55.570> and<00:20:55.720> final<00:20:55.809> bounty<00:20:56.200> I 00:20:56.250 --> 00:20:56.260 align:start position:0% this is the fourth and final bounty I 00:20:56.260 --> 00:20:59.669 align:start position:0% this is the fourth and final bounty I want<00:20:56.409> to<00:20:56.470> propose<00:20:56.740> is<00:20:58.200> it's<00:20:59.200> a<00:20:59.260> lot<00:20:59.380> of<00:20:59.409> text 00:20:59.669 --> 00:20:59.679 align:start position:0% want to propose is it's a lot of text 00:20:59.679 --> 00:21:04.230 align:start position:0% want to propose is it's a lot of text isn't<00:20:59.980> it<00:21:00.270> it's<00:21:01.270> just<00:21:01.419> that<00:21:01.539> I<00:21:01.870> would<00:21:02.380> like<00:21:03.240> any 00:21:04.230 --> 00:21:04.240 align:start position:0% isn't it it's just that I would like any 00:21:04.240 --> 00:21:05.639 align:start position:0% isn't it it's just that I would like any theory<00:21:04.539> imply<00:21:04.779> any<00:21:04.960> of<00:21:05.080> the<00:21:05.169> theorem<00:21:05.440> playing 00:21:05.639 --> 00:21:05.649 align:start position:0% theory imply any of the theorem playing 00:21:05.649 --> 00:21:09.990 align:start position:0% theory imply any of the theorem playing guess<00:21:05.980> parity<00:21:06.960> to<00:21:07.960> supply<00:21:08.710> users<00:21:09.429> with<00:21:09.700> a 00:21:09.990 --> 00:21:10.000 align:start position:0% guess parity to supply users with a 00:21:10.000 --> 00:21:11.940 align:start position:0% guess parity to supply users with a return<00:21:10.390> value<00:21:10.570> and<00:21:11.140> you<00:21:11.500> can<00:21:11.620> do<00:21:11.710> this<00:21:11.830> using 00:21:11.940 --> 00:21:11.950 align:start position:0% return value and you can do this using 00:21:11.950 --> 00:21:13.740 align:start position:0% return value and you can do this using really<00:21:12.340> any<00:21:12.460> mechanism<00:21:12.970> you<00:21:13.029> like<00:21:13.210> there<00:21:13.630> was 00:21:13.740 --> 00:21:13.750 align:start position:0% really any mechanism you like there was 00:21:13.750 --> 00:21:16.529 align:start position:0% really any mechanism you like there was an<00:21:13.870> EIP<00:21:14.110> recently<00:21:14.919> that's<00:21:15.149> proposed<00:21:16.149> putting 00:21:16.529 --> 00:21:16.539 align:start position:0% an EIP recently that's proposed putting 00:21:16.539 --> 00:21:19.560 align:start position:0% an EIP recently that's proposed putting it<00:21:16.659> in<00:21:17.190> transaction<00:21:18.190> receipts<00:21:18.549> for<00:21:19.270> various 00:21:19.560 --> 00:21:19.570 align:start position:0% it in transaction receipts for various 00:21:19.570 --> 00:21:21.299 align:start position:0% it in transaction receipts for various reasons<00:21:19.899> that<00:21:20.140> didn't<00:21:20.830> go<00:21:20.919> through<00:21:21.130> but 00:21:21.299 --> 00:21:21.309 align:start position:0% reasons that didn't go through but 00:21:21.309 --> 00:21:22.620 align:start position:0% reasons that didn't go through but there's<00:21:21.610> other<00:21:21.850> ways<00:21:22.000> of<00:21:22.149> doing<00:21:22.210> it<00:21:22.450> that<00:21:22.539> I 00:21:22.620 --> 00:21:22.630 align:start position:0% there's other ways of doing it that I 00:21:22.630 --> 00:21:24.360 align:start position:0% there's other ways of doing it that I think<00:21:22.809> would<00:21:22.870> work<00:21:23.020> perfectly<00:21:23.470> well<00:21:23.649> you 00:21:24.360 --> 00:21:24.370 align:start position:0% think would work perfectly well you 00:21:24.370 --> 00:21:25.590 align:start position:0% think would work perfectly well you don't<00:21:24.460> have<00:21:24.610> to<00:21:24.700> store<00:21:24.970> anything<00:21:25.179> you<00:21:25.450> could 00:21:25.590 --> 00:21:25.600 align:start position:0% don't have to store anything you could 00:21:25.600 --> 00:21:28.649 align:start position:0% don't have to store anything you could just<00:21:25.779> make<00:21:26.620> it<00:21:26.649> available<00:21:27.539> via<00:21:28.539> a 00:21:28.649 --> 00:21:28.659 align:start position:0% just make it available via a 00:21:28.659 --> 00:21:30.659 align:start position:0% just make it available via a subscription<00:21:29.289> you<00:21:29.830> know<00:21:30.100> so<00:21:30.279> when<00:21:30.549> the 00:21:30.659 --> 00:21:30.669 align:start position:0% subscription you know so when the 00:21:30.669 --> 00:21:34.769 align:start position:0% subscription you know so when the transaction<00:21:31.240> is<00:21:31.360> sealed<00:21:31.980> the<00:21:33.480> then<00:21:34.480> the 00:21:34.769 --> 00:21:34.779 align:start position:0% transaction is sealed the then the 00:21:34.779 --> 00:21:36.539 align:start position:0% transaction is sealed the then the theorem<00:21:35.049> node<00:21:35.260> uses<00:21:35.559> its<00:21:35.710> existing<00:21:36.100> pub/sub 00:21:36.539 --> 00:21:36.549 align:start position:0% theorem node uses its existing pub/sub 00:21:36.549 --> 00:21:38.039 align:start position:0% theorem node uses its existing pub/sub system<00:21:36.940> to<00:21:37.210> send<00:21:37.539> out<00:21:37.659> a<00:21:37.690> push<00:21:37.899> notification 00:21:38.039 --> 00:21:38.049 align:start position:0% system to send out a push notification 00:21:38.049 --> 00:21:39.810 align:start position:0% system to send out a push notification to<00:21:38.590> the<00:21:38.679> client<00:21:39.010> saying<00:21:39.220> hey<00:21:39.520> here's<00:21:39.730> the 00:21:39.810 --> 00:21:39.820 align:start position:0% to the client saying hey here's the 00:21:39.820 --> 00:21:41.700 align:start position:0% to the client saying hey here's the return<00:21:40.059> value<00:21:40.360> but<00:21:40.779> really<00:21:41.140> can<00:21:41.620> be 00:21:41.700 --> 00:21:41.710 align:start position:0% return value but really can be 00:21:41.710 --> 00:21:44.039 align:start position:0% return value but really can be implemented<00:21:42.419> any<00:21:43.419> way<00:21:43.600> you<00:21:43.659> want 00:21:44.039 --> 00:21:44.049 align:start position:0% implemented any way you want 00:21:44.049 --> 00:21:46.080 align:start position:0% implemented any way you want it's<00:21:44.230> claimable<00:21:44.559> by<00:21:44.830> either<00:21:45.130> the<00:21:45.399> theory<00:21:46.000> of 00:21:46.080 --> 00:21:46.090 align:start position:0% it's claimable by either the theory of 00:21:46.090 --> 00:21:47.789 align:start position:0% it's claimable by either the theory of no<00:21:46.240> development<00:21:46.720> teams<00:21:46.899> over<00:21:47.139> again<00:21:47.380> by<00:21:47.529> third 00:21:47.789 --> 00:21:47.799 align:start position:0% no development teams over again by third 00:21:47.799 --> 00:21:53.000 align:start position:0% no development teams over again by third party<00:21:48.100> submitting<00:21:48.940> a<00:21:49.000> PR 00:21:53.000 --> 00:21:53.010 align:start position:0% 00:21:53.010 --> 00:21:56.160 align:start position:0% okay<00:21:54.010> and<00:21:54.160> the<00:21:54.570> bounty<00:21:55.570> all<00:21:55.810> the<00:21:55.900> bounty<00:21:56.140> of 00:21:56.160 --> 00:21:56.170 align:start position:0% okay and the bounty all the bounty of 00:21:56.170 --> 00:21:58.740 align:start position:0% okay and the bounty all the bounty of utils<00:21:56.470> will<00:21:56.680> be<00:21:56.830> posted<00:21:57.640> over<00:21:57.790> the<00:21:57.850> next<00:21:58.030> few 00:21:58.740 --> 00:21:58.750 align:start position:0% utils will be posted over the next few 00:21:58.750 --> 00:22:11.230 align:start position:0% utils will be posted over the next few days<00:21:58.930> at<00:21:59.170> augur<00:21:59.470> net<00:21:59.830> slash<00:22:00.700> bounties 00:22:11.230 --> 00:22:11.240 align:start position:0% 00:22:11.240 --> 00:22:18.819 align:start position:0% [Music]