WEBVTT Kind: captions Language: en 00:00:18.869 --> 00:00:22.769 align:start position:0% so<00:00:20.099> so<00:00:21.099> the<00:00:21.189> panel<00:00:21.520> is<00:00:21.610> about<00:00:21.700> smart<00:00:22.180> contract 00:00:22.769 --> 00:00:22.779 align:start position:0% so so the panel is about smart contract 00:00:22.779 --> 00:00:26.760 align:start position:0% so so the panel is about smart contract security<00:00:23.669> and<00:00:24.669> one<00:00:25.419> thing<00:00:25.630> that's<00:00:25.840> been 00:00:26.760 --> 00:00:26.770 align:start position:0% security and one thing that's been 00:00:26.770 --> 00:00:30.150 align:start position:0% security and one thing that's been talked<00:00:27.279> about<00:00:27.400> a<00:00:27.550> lot<00:00:27.849> recently<00:00:27.880> is<00:00:29.160> formal 00:00:30.150 --> 00:00:30.160 align:start position:0% talked about a lot recently is formal 00:00:30.160 --> 00:00:34.170 align:start position:0% talked about a lot recently is formal verification<00:00:31.500> so<00:00:32.500> if<00:00:33.460> we<00:00:33.610> start<00:00:33.850> off<00:00:34.000> with 00:00:34.170 --> 00:00:34.180 align:start position:0% verification so if we start off with 00:00:34.180 --> 00:00:36.119 align:start position:0% verification so if we start off with that<00:00:34.300> do<00:00:35.170> you<00:00:35.260> think<00:00:35.470> that<00:00:35.620> formal 00:00:36.119 --> 00:00:36.129 align:start position:0% that do you think that formal 00:00:36.129 --> 00:00:38.970 align:start position:0% that do you think that formal verification<00:00:36.340> is<00:00:37.180> going<00:00:37.600> to<00:00:37.809> be<00:00:37.989> a<00:00:38.350> new<00:00:38.680> tool 00:00:38.970 --> 00:00:38.980 align:start position:0% verification is going to be a new tool 00:00:38.980 --> 00:00:42.060 align:start position:0% verification is going to be a new tool in<00:00:39.370> the<00:00:39.580> like<00:00:39.850> developer<00:00:40.660> tool<00:00:41.080> chain<00:00:41.470> that's 00:00:42.060 --> 00:00:42.070 align:start position:0% in the like developer tool chain that's 00:00:42.070 --> 00:00:44.820 align:start position:0% in the like developer tool chain that's going<00:00:42.339> to<00:00:42.489> be<00:00:43.290> commonly<00:00:44.290> used<00:00:44.559> when 00:00:44.820 --> 00:00:44.830 align:start position:0% going to be commonly used when 00:00:44.830 --> 00:00:47.130 align:start position:0% going to be commonly used when developing<00:00:45.280> smart<00:00:45.519> contracts<00:00:46.210> what's<00:00:46.989> your 00:00:47.130 --> 00:00:47.140 align:start position:0% developing smart contracts what's your 00:00:47.140 --> 00:00:51.479 align:start position:0% developing smart contracts what's your take<00:00:48.989> all<00:00:49.989> right<00:00:50.170> so<00:00:50.470> I<00:00:50.500> worked<00:00:51.070> in<00:00:51.159> formal 00:00:51.479 --> 00:00:51.489 align:start position:0% take all right so I worked in formal 00:00:51.489 --> 00:00:53.310 align:start position:0% take all right so I worked in formal verification<00:00:51.670> for<00:00:52.479> almost<00:00:53.019> four<00:00:53.290> years 00:00:53.310 --> 00:00:53.320 align:start position:0% verification for almost four years 00:00:53.320 --> 00:00:56.250 align:start position:0% verification for almost four years before<00:00:53.799> I<00:00:54.010> joined<00:00:54.460> IC<00:00:54.760> 3<00:00:54.879> at<00:00:55.059> Cornell<00:00:55.390> and<00:00:55.570> I 00:00:56.250 --> 00:00:56.260 align:start position:0% before I joined IC 3 at Cornell and I 00:00:56.260 --> 00:00:58.320 align:start position:0% before I joined IC 3 at Cornell and I think<00:00:56.619> formal<00:00:56.949> verification<00:00:57.100> is<00:00:57.760> really<00:00:58.089> in 00:00:58.320 --> 00:00:58.330 align:start position:0% think formal verification is really in 00:00:58.330 --> 00:01:00.420 align:start position:0% think formal verification is really in the<00:00:58.420> broader<00:00:58.659> community<00:00:59.070> finally<00:01:00.070> getting<00:01:00.339> to 00:01:00.420 --> 00:01:00.430 align:start position:0% the broader community finally getting to 00:01:00.430 --> 00:01:01.500 align:start position:0% the broader community finally getting to that<00:01:00.519> point<00:01:00.760> where<00:01:00.940> it's<00:01:01.150> reaching 00:01:01.500 --> 00:01:01.510 align:start position:0% that point where it's reaching 00:01:01.510 --> 00:01:03.210 align:start position:0% that point where it's reaching acceptance<00:01:02.080> and<00:01:02.320> the<00:01:02.409> tools<00:01:02.650> are<00:01:02.890> reaching 00:01:03.210 --> 00:01:03.220 align:start position:0% acceptance and the tools are reaching 00:01:03.220 --> 00:01:04.829 align:start position:0% acceptance and the tools are reaching the<00:01:03.309> level<00:01:03.610> of<00:01:03.729> maturity<00:01:03.850> that<00:01:04.390> makes<00:01:04.659> them 00:01:04.829 --> 00:01:04.839 align:start position:0% the level of maturity that makes them 00:01:04.839 --> 00:01:07.050 align:start position:0% the level of maturity that makes them actually<00:01:05.229> practical<00:01:05.770> so<00:01:06.700> yeah<00:01:06.880> I<00:01:06.909> think 00:01:07.050 --> 00:01:07.060 align:start position:0% actually practical so yeah I think 00:01:07.060 --> 00:01:08.520 align:start position:0% actually practical so yeah I think formal<00:01:07.450> verification<00:01:07.630> is<00:01:08.110> really<00:01:08.350> going<00:01:08.439> to 00:01:08.520 --> 00:01:08.530 align:start position:0% formal verification is really going to 00:01:08.530 --> 00:01:11.070 align:start position:0% formal verification is really going to be<00:01:08.760> one<00:01:09.760> critical<00:01:10.270> piece<00:01:10.510> of<00:01:10.750> the<00:01:10.960> overall 00:01:11.070 --> 00:01:11.080 align:start position:0% be one critical piece of the overall 00:01:11.080 --> 00:01:13.380 align:start position:0% be one critical piece of the overall security<00:01:11.680> picture<00:01:12.159> yeah<00:01:12.670> like<00:01:12.939> I<00:01:13.060> said<00:01:13.270> in<00:01:13.360> my 00:01:13.380 --> 00:01:13.390 align:start position:0% security picture yeah like I said in my 00:01:13.390 --> 00:01:14.940 align:start position:0% security picture yeah like I said in my talk<00:01:13.540> yesterday<00:01:13.930> it's<00:01:14.260> really<00:01:14.470> not<00:01:14.590> a<00:01:14.650> silver 00:01:14.940 --> 00:01:14.950 align:start position:0% talk yesterday it's really not a silver 00:01:14.950 --> 00:01:17.670 align:start position:0% talk yesterday it's really not a silver bullet<00:01:15.210> but<00:01:16.210> I'm<00:01:16.659> really<00:01:16.930> looking<00:01:17.170> forward<00:01:17.439> to 00:01:17.670 --> 00:01:17.680 align:start position:0% bullet but I'm really looking forward to 00:01:17.680 --> 00:01:19.469 align:start position:0% bullet but I'm really looking forward to using<00:01:17.950> etherium<00:01:18.640> and<00:01:18.909> the<00:01:19.030> smart<00:01:19.299> contract 00:01:19.469 --> 00:01:19.479 align:start position:0% using etherium and the smart contract 00:01:19.479 --> 00:01:22.440 align:start position:0% using etherium and the smart contract space<00:01:20.020> to<00:01:20.289> set<00:01:20.500> the<00:01:20.619> standard<00:01:21.070> for<00:01:21.490> how<00:01:22.030> formal 00:01:22.440 --> 00:01:22.450 align:start position:0% space to set the standard for how formal 00:01:22.450 --> 00:01:23.700 align:start position:0% space to set the standard for how formal verification<00:01:22.600> should<00:01:23.200> be<00:01:23.320> done<00:01:23.469> in<00:01:23.619> the 00:01:23.700 --> 00:01:23.710 align:start position:0% verification should be done in the 00:01:23.710 --> 00:01:25.349 align:start position:0% verification should be done in the broader<00:01:23.920> software<00:01:24.490> development<00:01:24.939> industry 00:01:25.349 --> 00:01:25.359 align:start position:0% broader software development industry 00:01:25.359 --> 00:01:27.179 align:start position:0% broader software development industry and<00:01:25.630> even<00:01:25.869> in<00:01:26.109> the<00:01:26.170> safety-critical<00:01:26.590> domain 00:01:27.179 --> 00:01:27.189 align:start position:0% and even in the safety-critical domain 00:01:27.189 --> 00:01:28.800 align:start position:0% and even in the safety-critical domain so<00:01:27.520> I<00:01:27.549> think<00:01:27.789> we<00:01:27.880> have<00:01:28.000> a<00:01:28.030> big<00:01:28.270> opportunity 00:01:28.800 --> 00:01:28.810 align:start position:0% so I think we have a big opportunity 00:01:28.810 --> 00:01:35.120 align:start position:0% so I think we have a big opportunity here<00:01:29.429> to<00:01:30.429> show<00:01:30.579> people<00:01:30.759> how<00:01:30.969> it's<00:01:31.119> done<00:01:31.270> really 00:01:35.120 --> 00:01:35.130 align:start position:0% 00:01:35.130 --> 00:01:38.249 align:start position:0% so<00:01:36.130> and<00:01:36.399> you<00:01:36.549> think<00:01:36.820> that<00:01:37.030> so<00:01:37.719> it's<00:01:37.869> not<00:01:37.960> only 00:01:38.249 --> 00:01:38.259 align:start position:0% so and you think that so it's not only 00:01:38.259 --> 00:01:41.539 align:start position:0% so and you think that so it's not only going<00:01:38.530> to<00:01:38.679> be<00:01:38.710> for<00:01:39.009> the<00:01:40.049> specialized 00:01:41.539 --> 00:01:41.549 align:start position:0% going to be for the specialized 00:01:41.549 --> 00:01:44.639 align:start position:0% going to be for the specialized contracts<00:01:42.549> but<00:01:42.759> more<00:01:42.969> for<00:01:43.270> in<00:01:43.600> general<00:01:44.020> people 00:01:44.639 --> 00:01:44.649 align:start position:0% contracts but more for in general people 00:01:44.649 --> 00:01:46.859 align:start position:0% contracts but more for in general people are<00:01:44.799> going<00:01:44.950> to<00:01:45.069> do<00:01:45.219> formal<00:01:45.670> verification<00:01:45.869> is 00:01:46.859 --> 00:01:46.869 align:start position:0% are going to do formal verification is 00:01:46.869 --> 00:01:49.230 align:start position:0% are going to do formal verification is that<00:01:47.049> going<00:01:47.259> to<00:01:47.350> be<00:01:47.439> the<00:01:47.729> developers<00:01:48.729> moving 00:01:49.230 --> 00:01:49.240 align:start position:0% that going to be the developers moving 00:01:49.240 --> 00:01:50.429 align:start position:0% that going to be the developers moving over<00:01:49.479> into<00:01:49.749> the<00:01:49.869> form<00:01:50.140> of<00:01:50.259> verification 00:01:50.429 --> 00:01:50.439 align:start position:0% over into the form of verification 00:01:50.439 --> 00:01:53.609 align:start position:0% over into the form of verification domain<00:01:51.039> or<00:01:51.280> are<00:01:51.490> we<00:01:51.640> going<00:01:51.850> to<00:01:52.229> have<00:01:53.229> tools 00:01:53.609 --> 00:01:53.619 align:start position:0% domain or are we going to have tools 00:01:53.619 --> 00:01:56.340 align:start position:0% domain or are we going to have tools which<00:01:53.920> make<00:01:53.950> it's<00:01:54.369> more<00:01:54.909> easy<00:01:55.179> to<00:01:55.569> formal 00:01:56.340 --> 00:01:56.350 align:start position:0% which make it's more easy to formal 00:01:56.350 --> 00:01:59.309 align:start position:0% which make it's more easy to formal verify<00:01:56.770> your<00:01:57.039> your<00:01:57.429> contracts<00:01:58.270> I<00:01:58.689> think<00:01:59.229> we're 00:01:59.309 --> 00:01:59.319 align:start position:0% verify your your contracts I think we're 00:01:59.319 --> 00:02:00.749 align:start position:0% verify your your contracts I think we're gonna<00:01:59.439> have<00:01:59.649> a<00:01:59.679> little<00:01:59.859> bit<00:02:00.039> of<00:02:00.159> both<00:02:00.369> and<00:02:00.670> I 00:02:00.749 --> 00:02:00.759 align:start position:0% gonna have a little bit of both and I 00:02:00.759 --> 00:02:02.399 align:start position:0% gonna have a little bit of both and I think<00:02:00.789> it's<00:02:01.179> up<00:02:01.389> to<00:02:01.509> the<00:02:01.600> users<00:02:01.990> of<00:02:02.259> these 00:02:02.399 --> 00:02:02.409 align:start position:0% think it's up to the users of these 00:02:02.409 --> 00:02:04.529 align:start position:0% think it's up to the users of these contracts<00:02:03.009> to<00:02:03.039> really<00:02:03.369> demand<00:02:03.819> the<00:02:04.119> standard 00:02:04.529 --> 00:02:04.539 align:start position:0% contracts to really demand the standard 00:02:04.539 --> 00:02:05.760 align:start position:0% contracts to really demand the standard and<00:02:04.719> the<00:02:04.780> level<00:02:05.079> of<00:02:05.139> rigor<00:02:05.380> that's 00:02:05.760 --> 00:02:05.770 align:start position:0% and the level of rigor that's 00:02:05.770 --> 00:02:07.050 align:start position:0% and the level of rigor that's appropriate<00:02:06.429> for<00:02:06.609> the<00:02:06.700> amount<00:02:06.909> of<00:02:06.999> money 00:02:07.050 --> 00:02:07.060 align:start position:0% appropriate for the amount of money 00:02:07.060 --> 00:02:09.930 align:start position:0% appropriate for the amount of money that's<00:02:07.389> going<00:02:07.569> into<00:02:07.899> them<00:02:08.050> I<00:02:08.319> think<00:02:08.940> having 00:02:09.930 --> 00:02:09.940 align:start position:0% that's going into them I think having 00:02:09.940 --> 00:02:12.570 align:start position:0% that's going into them I think having low<00:02:10.450> effort<00:02:10.720> automated<00:02:11.500> tools<00:02:11.740> is<00:02:12.069> really<00:02:12.550> a 00:02:12.570 --> 00:02:12.580 align:start position:0% low effort automated tools is really a 00:02:12.580 --> 00:02:14.640 align:start position:0% low effort automated tools is really a great<00:02:12.850> goal<00:02:13.090> and<00:02:13.390> is<00:02:13.690> something<00:02:13.959> that<00:02:14.260> I<00:02:14.290> would 00:02:14.640 --> 00:02:14.650 align:start position:0% great goal and is something that I would 00:02:14.650 --> 00:02:16.410 align:start position:0% great goal and is something that I would personally<00:02:14.890> even<00:02:15.400> like<00:02:15.610> to<00:02:15.730> contribute<00:02:16.120> to<00:02:16.240> in 00:02:16.410 --> 00:02:16.420 align:start position:0% personally even like to contribute to in 00:02:16.420 --> 00:02:18.540 align:start position:0% personally even like to contribute to in this<00:02:16.540> space<00:02:16.810> and<00:02:17.319> I<00:02:17.950> think<00:02:18.010> that<00:02:18.370> will<00:02:18.520> be 00:02:18.540 --> 00:02:18.550 align:start position:0% this space and I think that will be 00:02:18.550 --> 00:02:20.640 align:start position:0% this space and I think that will be great<00:02:18.760> for<00:02:19.090> many<00:02:19.420> many<00:02:19.630> contracts<00:02:20.140> but<00:02:20.470> when 00:02:20.640 --> 00:02:20.650 align:start position:0% great for many many contracts but when 00:02:20.650 --> 00:02:21.840 align:start position:0% great for many many contracts but when you<00:02:20.740> have<00:02:20.890> really<00:02:21.310> really<00:02:21.610> high<00:02:21.790> value 00:02:21.840 --> 00:02:21.850 align:start position:0% you have really really high value 00:02:21.850 --> 00:02:23.640 align:start position:0% you have really really high value contracts<00:02:22.630> I<00:02:22.780> think<00:02:22.960> we<00:02:23.080> will<00:02:23.230> need<00:02:23.350> to<00:02:23.500> have 00:02:23.640 --> 00:02:23.650 align:start position:0% contracts I think we will need to have 00:02:23.650 --> 00:02:25.410 align:start position:0% contracts I think we will need to have some<00:02:23.830> sort<00:02:24.010> of<00:02:24.070> specialized<00:02:24.610> approach<00:02:25.000> where 00:02:25.410 --> 00:02:25.420 align:start position:0% some sort of specialized approach where 00:02:25.420 --> 00:02:28.170 align:start position:0% some sort of specialized approach where we<00:02:26.020> bring<00:02:26.200> in<00:02:26.260> experts<00:02:26.500> and<00:02:26.980> we<00:02:27.040> asked<00:02:27.850> quite 00:02:28.170 --> 00:02:28.180 align:start position:0% we bring in experts and we asked quite 00:02:28.180 --> 00:02:29.759 align:start position:0% we bring in experts and we asked quite about<00:02:28.629> what<00:02:28.810> is<00:02:28.900> this<00:02:29.049> contract<00:02:29.530> actually 00:02:29.759 --> 00:02:29.769 align:start position:0% about what is this contract actually 00:02:29.769 --> 00:02:31.319 align:start position:0% about what is this contract actually doing<00:02:30.280> and<00:02:30.489> how<00:02:30.609> can<00:02:30.760> we<00:02:30.879> make<00:02:31.030> sure<00:02:31.060> it's 00:02:31.319 --> 00:02:31.329 align:start position:0% doing and how can we make sure it's 00:02:31.329 --> 00:02:34.740 align:start position:0% doing and how can we make sure it's doing<00:02:31.480> what<00:02:31.750> we<00:02:31.840> think<00:02:31.959> it's<00:02:32.170> doing<00:02:33.599> so<00:02:34.599> yeah<00:02:34.719> I 00:02:34.740 --> 00:02:34.750 align:start position:0% doing what we think it's doing so yeah I 00:02:34.750 --> 00:02:36.179 align:start position:0% doing what we think it's doing so yeah I think<00:02:35.019> to<00:02:35.290> answer<00:02:35.439> the<00:02:35.620> question<00:02:35.890> it'll<00:02:36.069> be<00:02:36.159> a 00:02:36.179 --> 00:02:36.189 align:start position:0% think to answer the question it'll be a 00:02:36.189 --> 00:02:38.339 align:start position:0% think to answer the question it'll be a combination<00:02:36.730> of<00:02:36.790> both<00:02:36.969> general<00:02:37.629> automatic 00:02:38.339 --> 00:02:38.349 align:start position:0% combination of both general automatic 00:02:38.349 --> 00:02:40.470 align:start position:0% combination of both general automatic and<00:02:38.560> specialized<00:02:39.310> approaches<00:02:39.879> and<00:02:40.209> it<00:02:40.299> really 00:02:40.470 --> 00:02:40.480 align:start position:0% and specialized approaches and it really 00:02:40.480 --> 00:02:42.240 align:start position:0% and specialized approaches and it really depends<00:02:40.900> on<00:02:40.989> how<00:02:41.170> much<00:02:41.290> money<00:02:41.560> your<00:02:41.769> contract 00:02:42.240 --> 00:02:42.250 align:start position:0% depends on how much money your contract 00:02:42.250 --> 00:02:43.949 align:start position:0% depends on how much money your contract is<00:02:42.400> handling<00:02:42.790> and<00:02:43.060> what<00:02:43.209> the<00:02:43.299> attack<00:02:43.540> surface 00:02:43.949 --> 00:02:43.959 align:start position:0% is handling and what the attack surface 00:02:43.959 --> 00:02:48.629 align:start position:0% is handling and what the attack surface is<00:02:44.140> and<00:02:44.560> other<00:02:45.069> factors<00:02:45.730> like<00:02:45.790> that<00:02:47.069> and<00:02:48.069> I 00:02:48.629 --> 00:02:48.639 align:start position:0% is and other factors like that and I 00:02:48.639 --> 00:02:51.089 align:start position:0% is and other factors like that and I would<00:02:48.909> add<00:02:49.060> to<00:02:49.090> that<00:02:49.269> that<00:02:49.719> the<00:02:50.439> tooling<00:02:51.010> is 00:02:51.089 --> 00:02:51.099 align:start position:0% would add to that that the tooling is 00:02:51.099 --> 00:02:52.740 align:start position:0% would add to that that the tooling is going<00:02:51.280> to<00:02:51.340> be<00:02:51.430> a<00:02:51.459> critical<00:02:51.879> component<00:02:52.030> because 00:02:52.740 --> 00:02:52.750 align:start position:0% going to be a critical component because 00:02:52.750 --> 00:02:54.929 align:start position:0% going to be a critical component because a<00:02:53.109> lot<00:02:53.590> of<00:02:53.680> the<00:02:53.739> developers<00:02:54.280> that<00:02:54.340> are<00:02:54.639> coming 00:02:54.929 --> 00:02:54.939 align:start position:0% a lot of the developers that are coming 00:02:54.939 --> 00:02:56.940 align:start position:0% a lot of the developers that are coming in<00:02:55.090> and<00:02:55.299> developing<00:02:55.810> contracts<00:02:56.650> are<00:02:56.799> coming 00:02:56.940 --> 00:02:56.950 align:start position:0% in and developing contracts are coming 00:02:56.950 --> 00:02:58.979 align:start position:0% in and developing contracts are coming from<00:02:57.099> the<00:02:57.280> app<00:02:57.430> development<00:02:58.000> space<00:02:58.389> so<00:02:58.750> if 00:02:58.979 --> 00:02:58.989 align:start position:0% from the app development space so if 00:02:58.989 --> 00:03:00.599 align:start position:0% from the app development space so if you're<00:02:59.109> building<00:02:59.260> web<00:02:59.560> apps<00:02:59.829> or<00:03:00.069> mobile<00:03:00.129> apps 00:03:00.599 --> 00:03:00.609 align:start position:0% you're building web apps or mobile apps 00:03:00.609 --> 00:03:02.159 align:start position:0% you're building web apps or mobile apps you're<00:03:01.150> not<00:03:01.269> used<00:03:01.540> to<00:03:01.689> these<00:03:01.780> kinds<00:03:02.139> of 00:03:02.159 --> 00:03:02.169 align:start position:0% you're not used to these kinds of 00:03:02.169 --> 00:03:05.159 align:start position:0% you're not used to these kinds of requirements<00:03:02.829> and<00:03:03.480> truly<00:03:04.480> smart<00:03:04.720> contract 00:03:05.159 --> 00:03:05.169 align:start position:0% requirements and truly smart contract 00:03:05.169 --> 00:03:07.199 align:start position:0% requirements and truly smart contract development<00:03:05.650> is<00:03:05.980> much<00:03:06.250> more<00:03:06.370> similar<00:03:06.879> to 00:03:07.199 --> 00:03:07.209 align:start position:0% development is much more similar to 00:03:07.209 --> 00:03:09.929 align:start position:0% development is much more similar to writing<00:03:08.079> software<00:03:08.650> to<00:03:09.010> put<00:03:09.280> a<00:03:09.310> shuttle<00:03:09.730> into 00:03:09.929 --> 00:03:09.939 align:start position:0% writing software to put a shuttle into 00:03:09.939 --> 00:03:12.959 align:start position:0% writing software to put a shuttle into space<00:03:10.209> or<00:03:10.510> writing<00:03:11.049> software<00:03:11.230> for<00:03:11.969> safety 00:03:12.959 --> 00:03:12.969 align:start position:0% space or writing software for safety 00:03:12.969 --> 00:03:15.209 align:start position:0% space or writing software for safety medical<00:03:13.450> devices<00:03:13.750> you're<00:03:14.650> writing<00:03:14.859> software 00:03:15.209 --> 00:03:15.219 align:start position:0% medical devices you're writing software 00:03:15.219 --> 00:03:16.470 align:start position:0% medical devices you're writing software that<00:03:15.370> handles<00:03:15.519> millions<00:03:16.090> of<00:03:16.209> dollars 00:03:16.470 --> 00:03:16.480 align:start position:0% that handles millions of dollars 00:03:16.480 --> 00:03:18.539 align:start position:0% that handles millions of dollars potentially<00:03:17.049> so<00:03:17.200> the<00:03:17.409> kinds<00:03:17.769> of<00:03:17.859> security 00:03:18.539 --> 00:03:18.549 align:start position:0% potentially so the kinds of security 00:03:18.549 --> 00:03:19.979 align:start position:0% potentially so the kinds of security requirements<00:03:19.209> are<00:03:19.329> closer<00:03:19.599> to<00:03:19.840> those 00:03:19.979 --> 00:03:19.989 align:start position:0% requirements are closer to those 00:03:19.989 --> 00:03:22.409 align:start position:0% requirements are closer to those applications<00:03:20.200> and<00:03:20.919> a<00:03:21.609> lot<00:03:21.879> of<00:03:21.909> the<00:03:22.180> DAP 00:03:22.409 --> 00:03:22.419 align:start position:0% applications and a lot of the DAP 00:03:22.419 --> 00:03:24.059 align:start position:0% applications and a lot of the DAP developers<00:03:23.049> are<00:03:23.260> not<00:03:23.469> coming<00:03:23.799> from<00:03:23.919> that 00:03:24.059 --> 00:03:24.069 align:start position:0% developers are not coming from that 00:03:24.069 --> 00:03:26.610 align:start position:0% developers are not coming from that space<00:03:24.400> so<00:03:25.120> a<00:03:25.480> combination<00:03:25.780> of<00:03:26.169> tooling<00:03:26.590> that 00:03:26.610 --> 00:03:26.620 align:start position:0% space so a combination of tooling that 00:03:26.620 --> 00:03:29.399 align:start position:0% space so a combination of tooling that automates<00:03:27.189> a<00:03:27.489> lot<00:03:28.120> of<00:03:28.329> the<00:03:28.750> formal 00:03:29.399 --> 00:03:29.409 align:start position:0% automates a lot of the formal 00:03:29.409 --> 00:03:31.530 align:start position:0% automates a lot of the formal verification<00:03:29.560> and<00:03:30.250> then<00:03:30.400> also<00:03:30.819> education 00:03:31.530 --> 00:03:31.540 align:start position:0% verification and then also education 00:03:31.540 --> 00:03:33.839 align:start position:0% verification and then also education just<00:03:31.840> as<00:03:31.930> a<00:03:31.989> process<00:03:32.440> to<00:03:32.650> bring<00:03:33.159> developers<00:03:33.699> up 00:03:33.839 --> 00:03:33.849 align:start position:0% just as a process to bring developers up 00:03:33.849 --> 00:03:35.399 align:start position:0% just as a process to bring developers up to<00:03:33.970> speed<00:03:34.239> with<00:03:34.419> here's<00:03:34.690> the<00:03:34.780> domain<00:03:35.079> we're<00:03:35.260> in 00:03:35.399 --> 00:03:35.409 align:start position:0% to speed with here's the domain we're in 00:03:35.409 --> 00:03:36.990 align:start position:0% to speed with here's the domain we're in and<00:03:35.620> here's<00:03:35.859> really<00:03:36.099> what<00:03:36.280> the<00:03:36.400> requirements 00:03:36.990 --> 00:03:37.000 align:start position:0% and here's really what the requirements 00:03:37.000 --> 00:03:39.589 align:start position:0% and here's really what the requirements are<00:03:37.090> to<00:03:37.900> produce<00:03:38.079> production<00:03:38.530> apps 00:03:39.589 --> 00:03:39.599 align:start position:0% are to produce production apps 00:03:39.599 --> 00:03:41.640 align:start position:0% are to produce production apps yeah<00:03:40.599> and<00:03:40.750> I<00:03:40.810> think<00:03:41.019> a<00:03:41.079> lot<00:03:41.199> of<00:03:41.229> that<00:03:41.409> is<00:03:41.500> gonna 00:03:41.640 --> 00:03:41.650 align:start position:0% yeah and I think a lot of that is gonna 00:03:41.650 --> 00:03:43.080 align:start position:0% yeah and I think a lot of that is gonna come<00:03:41.829> from<00:03:41.859> the<00:03:42.040> user<00:03:42.250> side<00:03:42.519> as<00:03:42.699> well<00:03:42.879> we 00:03:43.080 --> 00:03:43.090 align:start position:0% come from the user side as well we 00:03:43.090 --> 00:03:45.119 align:start position:0% come from the user side as well we really<00:03:43.329> need<00:03:43.449> to<00:03:43.540> educate<00:03:43.659> users<00:03:44.439> and<00:03:44.799> make 00:03:45.119 --> 00:03:45.129 align:start position:0% really need to educate users and make 00:03:45.129 --> 00:03:46.800 align:start position:0% really need to educate users and make them<00:03:45.310> demand<00:03:45.669> the<00:03:45.939> appropriate<00:03:46.479> level<00:03:46.750> of 00:03:46.800 --> 00:03:46.810 align:start position:0% them demand the appropriate level of 00:03:46.810 --> 00:03:48.960 align:start position:0% them demand the appropriate level of rigor<00:03:47.049> for<00:03:47.500> the<00:03:48.280> software<00:03:48.609> that<00:03:48.790> they're 00:03:48.960 --> 00:03:48.970 align:start position:0% rigor for the software that they're 00:03:48.970 --> 00:03:51.030 align:start position:0% rigor for the software that they're using<00:03:49.209> I<00:03:49.569> know<00:03:49.900> people<00:03:50.319> are<00:03:50.530> putting<00:03:50.739> lots<00:03:50.979> of 00:03:51.030 --> 00:03:51.040 align:start position:0% using I know people are putting lots of 00:03:51.040 --> 00:03:52.559 align:start position:0% using I know people are putting lots of money<00:03:51.280> in<00:03:51.430> contracts<00:03:51.879> right<00:03:52.060> now<00:03:52.209> that<00:03:52.389> don't 00:03:52.559 --> 00:03:52.569 align:start position:0% money in contracts right now that don't 00:03:52.569 --> 00:03:54.089 align:start position:0% money in contracts right now that don't even<00:03:52.689> have<00:03:52.810> tests<00:03:53.349> and<00:03:53.590> that's<00:03:53.799> like<00:03:54.069> really 00:03:54.089 --> 00:03:54.099 align:start position:0% even have tests and that's like really 00:03:54.099 --> 00:03:55.890 align:start position:0% even have tests and that's like really the<00:03:54.489> bare<00:03:54.669> minimum<00:03:55.030> in<00:03:55.180> terms<00:03:55.389> of<00:03:55.540> software 00:03:55.890 --> 00:03:55.900 align:start position:0% the bare minimum in terms of software 00:03:55.900 --> 00:03:58.379 align:start position:0% the bare minimum in terms of software engineering<00:03:55.930> so<00:03:56.849> until<00:03:57.849> we<00:03:57.939> educate<00:03:58.359> people 00:03:58.379 --> 00:03:58.389 align:start position:0% engineering so until we educate people 00:03:58.389 --> 00:04:00.749 align:start position:0% engineering so until we educate people to<00:03:58.930> sort<00:03:59.139> of<00:03:59.259> what's<00:03:59.439> possible<00:03:59.979> and<00:04:00.040> what<00:04:00.609> the 00:04:00.749 --> 00:04:00.759 align:start position:0% to sort of what's possible and what the 00:04:00.759 --> 00:04:04.289 align:start position:0% to sort of what's possible and what the tools<00:04:01.229> exists<00:04:02.229> to<00:04:02.439> do<00:04:02.639> I<00:04:03.639> don't<00:04:04.000> think<00:04:04.060> we'll 00:04:04.289 --> 00:04:04.299 align:start position:0% tools exists to do I don't think we'll 00:04:04.299 --> 00:04:05.759 align:start position:0% tools exists to do I don't think we'll see<00:04:04.329> much<00:04:04.479> improvement<00:04:04.780> so<00:04:05.349> there<00:04:05.590> definitely 00:04:05.759 --> 00:04:05.769 align:start position:0% see much improvement so there definitely 00:04:05.769 --> 00:04:07.830 align:start position:0% see much improvement so there definitely needs<00:04:06.099> to<00:04:06.250> be<00:04:06.310> a<00:04:06.430> push<00:04:06.669> on<00:04:06.909> both<00:04:07.120> the<00:04:07.389> developer 00:04:07.830 --> 00:04:07.840 align:start position:0% needs to be a push on both the developer 00:04:07.840 --> 00:04:09.420 align:start position:0% needs to be a push on both the developer and<00:04:08.019> the<00:04:08.139> user<00:04:08.290> side<00:04:08.620> in<00:04:08.949> terms<00:04:09.220> of<00:04:09.340> these 00:04:09.420 --> 00:04:09.430 align:start position:0% and the user side in terms of these 00:04:09.430 --> 00:04:11.610 align:start position:0% and the user side in terms of these tools<00:04:09.729> not<00:04:10.299> just<00:04:10.689> a<00:04:10.780> matter<00:04:10.959> of<00:04:11.049> educating 00:04:11.610 --> 00:04:11.620 align:start position:0% tools not just a matter of educating 00:04:11.620 --> 00:04:13.229 align:start position:0% tools not just a matter of educating users<00:04:11.829> I<00:04:12.250> think<00:04:12.280> the<00:04:12.609> other<00:04:12.759> thing<00:04:13.000> that<00:04:13.030> we 00:04:13.229 --> 00:04:13.239 align:start position:0% users I think the other thing that we 00:04:13.239 --> 00:04:19.999 align:start position:0% users I think the other thing that we can<00:04:13.569> and<00:04:13.780> should<00:04:13.810> be<00:04:13.959> targeting<00:04:14.470> is<00:04:15.930> like<00:04:16.930> one 00:04:19.999 --> 00:04:20.009 align:start position:0% 00:04:20.009 --> 00:04:23.999 align:start position:0% one<00:04:21.009> two<00:04:21.280> three<00:04:21.579> four<00:04:22.409> can<00:04:23.409> reform<00:04:23.770> only<00:04:23.860> the 00:04:23.999 --> 00:04:24.009 align:start position:0% one two three four can reform only the 00:04:24.009 --> 00:04:26.279 align:start position:0% one two three four can reform only the RF<00:04:24.190> I<00:04:24.250> use<00:04:24.400> microphones<00:04:24.909> next<00:04:25.210> time<00:04:25.389> at<00:04:25.930> six 00:04:26.279 --> 00:04:26.289 align:start position:0% RF I use microphones next time at six 00:04:26.289 --> 00:04:30.930 align:start position:0% RF I use microphones next time at six seven<00:04:26.620> eight<00:04:27.870> nine 00:04:30.930 --> 00:04:30.940 align:start position:0% 00:04:30.940 --> 00:04:33.670 align:start position:0% what<00:04:31.940> I<00:04:31.970> was<00:04:32.120> saying<00:04:32.330> is<00:04:32.720> that<00:04:32.750> I<00:04:33.140> think<00:04:33.290> it's 00:04:33.670 --> 00:04:33.680 align:start position:0% what I was saying is that I think it's 00:04:33.680 --> 00:04:35.320 align:start position:0% what I was saying is that I think it's not<00:04:33.830> just<00:04:33.860> the<00:04:34.130> users<00:04:34.610> that<00:04:34.940> we<00:04:35.030> should<00:04:35.240> be 00:04:35.320 --> 00:04:35.330 align:start position:0% not just the users that we should be 00:04:35.330 --> 00:04:37.060 align:start position:0% not just the users that we should be targeting<00:04:35.750> here<00:04:35.960> I<00:04:35.990> think<00:04:36.230> it's<00:04:36.350> also<00:04:36.710> user 00:04:37.060 --> 00:04:37.070 align:start position:0% targeting here I think it's also user 00:04:37.070 --> 00:04:39.550 align:start position:0% targeting here I think it's also user facing<00:04:37.490> intermediaries<00:04:38.180> so<00:04:38.930> like<00:04:39.080> one<00:04:39.320> good 00:04:39.550 --> 00:04:39.560 align:start position:0% facing intermediaries so like one good 00:04:39.560 --> 00:04:40.870 align:start position:0% facing intermediaries so like one good thing<00:04:39.620> from<00:04:39.830> that<00:04:40.130> standpoint<00:04:40.460> that<00:04:40.670> has 00:04:40.870 --> 00:04:40.880 align:start position:0% thing from that standpoint that has 00:04:40.880 --> 00:04:42.310 align:start position:0% thing from that standpoint that has already<00:04:41.030> happened<00:04:41.360> is<00:04:41.690> just<00:04:41.870> the<00:04:41.990> fact<00:04:42.230> that 00:04:42.310 --> 00:04:42.320 align:start position:0% already happened is just the fact that 00:04:42.320 --> 00:04:44.340 align:start position:0% already happened is just the fact that quality<00:04:42.770> Explorer<00:04:43.190> is<00:04:43.310> like<00:04:43.490> either<00:04:43.640> and<00:04:44.000> have 00:04:44.340 --> 00:04:44.350 align:start position:0% quality Explorer is like either and have 00:04:44.350 --> 00:04:47.920 align:start position:0% quality Explorer is like either and have code<00:04:45.350> verification<00:04:45.820> and<00:04:46.820> now<00:04:46.970> check<00:04:47.360> if<00:04:47.690> you 00:04:47.920 --> 00:04:47.930 align:start position:0% code verification and now check if you 00:04:47.930 --> 00:04:49.240 align:start position:0% code verification and now check if you would<00:04:48.080> see<00:04:48.230> a<00:04:48.260> contract<00:04:48.830> saying<00:04:49.070> might<00:04:49.220> be 00:04:49.240 --> 00:04:49.250 align:start position:0% would see a contract saying might be 00:04:49.250 --> 00:04:50.950 align:start position:0% would see a contract saying might be disagreeing<00:04:49.790> interacting<00:04:50.270> with<00:04:50.420> it<00:04:50.630> actually 00:04:50.950 --> 00:04:50.960 align:start position:0% disagreeing interacting with it actually 00:04:50.960 --> 00:04:53.770 align:start position:0% disagreeing interacting with it actually codes<00:04:51.200> it's<00:04:51.950> you<00:04:52.190> can<00:04:52.340> check<00:04:52.670> this<00:04:53.180> source<00:04:53.390> may 00:04:53.770 --> 00:04:53.780 align:start position:0% codes it's you can check this source may 00:04:53.780 --> 00:04:55.420 align:start position:0% codes it's you can check this source may verify<00:04:54.080> the<00:04:54.260> source<00:04:54.470> actually<00:04:54.860> matches<00:04:55.340> the 00:04:55.420 --> 00:04:55.430 align:start position:0% verify the source actually matches the 00:04:55.430 --> 00:04:59.350 align:start position:0% verify the source actually matches the byte<00:04:55.580> code<00:04:57.610> you<00:04:58.610> could<00:04:58.760> see<00:04:58.940> something<00:04:59.180> like 00:04:59.350 --> 00:04:59.360 align:start position:0% byte code you could see something like 00:04:59.360 --> 00:05:01.600 align:start position:0% byte code you could see something like that<00:04:59.450> potentially<00:05:00.110> being<00:05:00.440> expanded<00:05:01.190> quite<00:05:01.580> a 00:05:01.600 --> 00:05:01.610 align:start position:0% that potentially being expanded quite a 00:05:01.610 --> 00:05:03.880 align:start position:0% that potentially being expanded quite a bit<00:05:01.820> you<00:05:02.000> know<00:05:02.060> including<00:05:02.720> you<00:05:03.530> know<00:05:03.620> check 00:05:03.880 --> 00:05:03.890 align:start position:0% bit you know including you know check 00:05:03.890 --> 00:05:05.320 align:start position:0% bit you know including you know check marks<00:05:04.220> for<00:05:04.400> like<00:05:04.520> what<00:05:04.730> kinds<00:05:04.970> of<00:05:05.030> form<00:05:05.240> of 00:05:05.320 --> 00:05:05.330 align:start position:0% marks for like what kinds of form of 00:05:05.330 --> 00:05:07.060 align:start position:0% marks for like what kinds of form of your<00:05:05.450> vacation<00:05:05.750> guarantee<00:05:06.260> is<00:05:06.380> this<00:05:06.530> it's 00:05:07.060 --> 00:05:07.070 align:start position:0% your vacation guarantee is this it's 00:05:07.070 --> 00:05:08.410 align:start position:0% your vacation guarantee is this it's passed<00:05:07.370> are<00:05:07.610> there<00:05:07.730> any<00:05:07.850> tests<00:05:08.210> that<00:05:08.240> it's 00:05:08.410 --> 00:05:08.420 align:start position:0% passed are there any tests that it's 00:05:08.420 --> 00:05:10.800 align:start position:0% passed are there any tests that it's faster<00:05:08.720> we<00:05:08.930> tested<00:05:09.230> it<00:05:09.320> failed<00:05:09.560> and<00:05:09.740> so<00:05:09.890> forth 00:05:10.800 --> 00:05:10.810 align:start position:0% faster we tested it failed and so forth 00:05:10.810 --> 00:05:14.350 align:start position:0% faster we tested it failed and so forth so<00:05:11.810> I<00:05:12.740> know<00:05:13.100> grain<00:05:13.400> you've<00:05:13.670> been<00:05:13.880> developing 00:05:14.350 --> 00:05:14.360 align:start position:0% so I know grain you've been developing 00:05:14.360 --> 00:05:18.670 align:start position:0% so I know grain you've been developing some<00:05:14.570> tooling<00:05:15.080> for<00:05:15.110> solidity<00:05:15.680> and<00:05:17.380> so<00:05:18.380> when 00:05:18.670 --> 00:05:18.680 align:start position:0% some tooling for solidity and so when 00:05:18.680 --> 00:05:19.570 align:start position:0% some tooling for solidity and so when we're<00:05:18.800> talking<00:05:18.890> about<00:05:19.040> tools 00:05:19.570 --> 00:05:19.580 align:start position:0% we're talking about tools 00:05:19.580 --> 00:05:23.140 align:start position:0% we're talking about tools what<00:05:19.760> kind<00:05:20.000> of<00:05:20.120> more<00:05:20.300> tools<00:05:21.280> are<00:05:22.280> needed<00:05:22.670> in 00:05:23.140 --> 00:05:23.150 align:start position:0% what kind of more tools are needed in 00:05:23.150 --> 00:05:28.930 align:start position:0% what kind of more tools are needed in this<00:05:23.300> space<00:05:26.500> well<00:05:27.500> there's<00:05:27.920> a<00:05:28.010> huge<00:05:28.160> range<00:05:28.490> and 00:05:28.930 --> 00:05:28.940 align:start position:0% this space well there's a huge range and 00:05:28.940 --> 00:05:31.780 align:start position:0% this space well there's a huge range and I<00:05:29.930> think<00:05:30.560> it's<00:05:30.680> useful<00:05:30.860> to<00:05:31.040> have<00:05:31.160> both<00:05:31.580> the 00:05:31.780 --> 00:05:31.790 align:start position:0% I think it's useful to have both the 00:05:31.790 --> 00:05:35.290 align:start position:0% I think it's useful to have both the tools<00:05:32.000> that<00:05:32.210> are<00:05:32.600> offering<00:05:33.320> rigorous<00:05:34.300> methods 00:05:35.290 --> 00:05:35.300 align:start position:0% tools that are offering rigorous methods 00:05:35.300 --> 00:05:37.480 align:start position:0% tools that are offering rigorous methods of<00:05:35.390> completeness<00:05:35.750> and<00:05:36.200> the<00:05:36.650> academic<00:05:37.310> work 00:05:37.480 --> 00:05:37.490 align:start position:0% of completeness and the academic work 00:05:37.490 --> 00:05:38.980 align:start position:0% of completeness and the academic work and<00:05:37.640> the<00:05:37.700> research<00:05:37.880> is<00:05:38.240> really<00:05:38.450> essential<00:05:38.870> to 00:05:38.980 --> 00:05:38.990 align:start position:0% and the research is really essential to 00:05:38.990 --> 00:05:41.080 align:start position:0% and the research is really essential to that<00:05:39.140> but<00:05:40.100> you<00:05:40.130> can<00:05:40.310> get<00:05:40.430> a<00:05:40.460> lot<00:05:40.610> of<00:05:40.700> value<00:05:41.060> out 00:05:41.080 --> 00:05:41.090 align:start position:0% that but you can get a lot of value out 00:05:41.090 --> 00:05:43.690 align:start position:0% that but you can get a lot of value out of<00:05:41.330> heuristics<00:05:41.930> as<00:05:42.110> well<00:05:42.320> and<00:05:42.710> you<00:05:43.670> know 00:05:43.690 --> 00:05:43.700 align:start position:0% of heuristics as well and you know 00:05:43.700 --> 00:05:45.700 align:start position:0% of heuristics as well and you know things<00:05:44.060> that<00:05:44.210> are<00:05:44.390> rather<00:05:44.630> obvious<00:05:45.170> now<00:05:45.350> like 00:05:45.700 --> 00:05:45.710 align:start position:0% things that are rather obvious now like 00:05:45.710 --> 00:05:48.280 align:start position:0% things that are rather obvious now like the<00:05:45.980> reentry<00:05:46.460> attack<00:05:46.730> on<00:05:46.940> the<00:05:47.030> Dow<00:05:47.210> maybe<00:05:48.140> the 00:05:48.280 --> 00:05:48.290 align:start position:0% the reentry attack on the Dow maybe the 00:05:48.290 --> 00:05:49.720 align:start position:0% the reentry attack on the Dow maybe the particulars<00:05:48.770> of<00:05:48.830> it<00:05:49.070> weren't<00:05:49.310> obvious<00:05:49.610> the 00:05:49.720 --> 00:05:49.730 align:start position:0% particulars of it weren't obvious the 00:05:49.730 --> 00:05:52.510 align:start position:0% particulars of it weren't obvious the spot<00:05:50.000> but<00:05:50.240> the<00:05:50.720> particular<00:05:51.410> attack<00:05:51.770> of<00:05:52.040> having 00:05:52.510 --> 00:05:52.520 align:start position:0% spot but the particular attack of having 00:05:52.520 --> 00:05:54.970 align:start position:0% spot but the particular attack of having a<00:05:52.580> recursive<00:05:53.060> call<00:05:53.320> from<00:05:54.320> an<00:05:54.410> external<00:05:54.680> call 00:05:54.970 --> 00:05:54.980 align:start position:0% a recursive call from an external call 00:05:54.980 --> 00:05:57.160 align:start position:0% a recursive call from an external call is<00:05:55.220> quite<00:05:55.730> easy<00:05:55.940> to<00:05:56.030> spot<00:05:56.330> and<00:05:56.600> so<00:05:56.720> it<00:05:56.840> doesn't 00:05:57.160 --> 00:05:57.170 align:start position:0% is quite easy to spot and so it doesn't 00:05:57.170 --> 00:06:00.190 align:start position:0% is quite easy to spot and so it doesn't take<00:05:57.410> a<00:05:58.280> very<00:05:58.910> heavy-duty<00:05:59.450> approach<00:05:59.990> to<00:06:00.140> be 00:06:00.190 --> 00:06:00.200 align:start position:0% take a very heavy-duty approach to be 00:06:00.200 --> 00:06:03.340 align:start position:0% take a very heavy-duty approach to be able<00:06:00.230> to<00:06:00.410> detect<00:06:01.040> those<00:06:01.370> things<00:06:01.670> so<00:06:02.510> the 00:06:03.340 --> 00:06:03.350 align:start position:0% able to detect those things so the 00:06:03.350 --> 00:06:04.720 align:start position:0% able to detect those things so the tooling<00:06:03.650> can<00:06:03.770> range<00:06:04.040> from<00:06:04.160> the<00:06:04.400> more<00:06:04.550> rigorous 00:06:04.720 --> 00:06:04.730 align:start position:0% tooling can range from the more rigorous 00:06:04.730 --> 00:06:09.700 align:start position:0% tooling can range from the more rigorous to<00:06:05.740> just<00:06:06.740> some<00:06:07.160> simple<00:06:07.810> sorts<00:06:08.810> of<00:06:08.960> analyses 00:06:09.700 --> 00:06:09.710 align:start position:0% to just some simple sorts of analyses 00:06:09.710 --> 00:06:12.250 align:start position:0% to just some simple sorts of analyses static<00:06:10.220> analysis<00:06:10.730> is<00:06:10.910> a<00:06:10.940> great<00:06:11.210> tool<00:06:11.990> to<00:06:12.020> be 00:06:12.250 --> 00:06:12.260 align:start position:0% static analysis is a great tool to be 00:06:12.260 --> 00:06:14.830 align:start position:0% static analysis is a great tool to be able<00:06:12.410> to<00:06:12.560> just<00:06:12.830> detect<00:06:13.360> things<00:06:14.360> that<00:06:14.630> are 00:06:14.830 --> 00:06:14.840 align:start position:0% able to just detect things that are 00:06:14.840 --> 00:06:18.430 align:start position:0% able to just detect things that are potential<00:06:15.770> areas<00:06:16.220> of<00:06:16.370> risk<00:06:16.960> so<00:06:17.960> I<00:06:18.020> think<00:06:18.110> that 00:06:18.430 --> 00:06:18.440 align:start position:0% potential areas of risk so I think that 00:06:18.440 --> 00:06:20.980 align:start position:0% potential areas of risk so I think that can<00:06:18.830> go<00:06:18.980> a<00:06:19.010> long<00:06:19.220> way<00:06:19.400> towards<00:06:19.990> providing 00:06:20.980 --> 00:06:20.990 align:start position:0% can go a long way towards providing 00:06:20.990 --> 00:06:23.140 align:start position:0% can go a long way towards providing people<00:06:21.320> more<00:06:21.470> visibility<00:06:22.130> into<00:06:22.460> contracts 00:06:23.140 --> 00:06:23.150 align:start position:0% people more visibility into contracts 00:06:23.150 --> 00:06:25.750 align:start position:0% people more visibility into contracts and<00:06:23.990> if<00:06:24.290> you<00:06:24.410> know<00:06:24.620> that<00:06:24.890> you're<00:06:25.040> looking<00:06:25.460> for 00:06:25.750 --> 00:06:25.760 align:start position:0% and if you know that you're looking for 00:06:25.760 --> 00:06:29.290 align:start position:0% and if you know that you're looking for risks<00:06:26.750> then<00:06:27.290> we<00:06:28.100> can<00:06:28.280> devise<00:06:28.580> tools<00:06:28.970> that 00:06:29.290 --> 00:06:29.300 align:start position:0% risks then we can devise tools that 00:06:29.300 --> 00:06:31.810 align:start position:0% risks then we can devise tools that highlight<00:06:29.870> that<00:06:30.050> and<00:06:30.400> expose<00:06:31.400> where<00:06:31.610> the 00:06:31.810 --> 00:06:31.820 align:start position:0% highlight that and expose where the 00:06:31.820 --> 00:06:33.820 align:start position:0% highlight that and expose where the potential<00:06:32.330> areas<00:06:32.570> are<00:06:32.960> and<00:06:33.230> that<00:06:33.590> can<00:06:33.710> be<00:06:33.800> a 00:06:33.820 --> 00:06:33.830 align:start position:0% potential areas are and that can be a 00:06:33.830 --> 00:06:36.100 align:start position:0% potential areas are and that can be a low<00:06:34.130> that<00:06:34.760> can<00:06:34.850> be<00:06:34.970> low<00:06:35.150> investment<00:06:35.450> you<00:06:35.990> know 00:06:36.100 --> 00:06:36.110 align:start position:0% low that can be low investment you know 00:06:36.110 --> 00:06:37.810 align:start position:0% low that can be low investment you know you<00:06:36.170> don't<00:06:36.410> have<00:06:36.590> to<00:06:36.770> do<00:06:36.890> a<00:06:36.920> full<00:06:37.280> security 00:06:37.810 --> 00:06:37.820 align:start position:0% you don't have to do a full security 00:06:37.820 --> 00:06:38.780 align:start position:0% you don't have to do a full security audit 00:06:38.780 --> 00:06:38.790 align:start position:0% audit 00:06:38.790 --> 00:06:41.180 align:start position:0% audit first<00:06:39.600> as<00:06:39.930> a<00:06:39.960> first<00:06:40.260> step<00:06:40.500> you'll<00:06:40.920> want<00:06:41.070> to<00:06:41.130> do 00:06:41.180 --> 00:06:41.190 align:start position:0% first as a first step you'll want to do 00:06:41.190 --> 00:06:43.370 align:start position:0% first as a first step you'll want to do it<00:06:41.310> later<00:06:41.430> but<00:06:41.700> as<00:06:41.940> a<00:06:42.240> first<00:06:42.570> step<00:06:42.750> if<00:06:43.020> you<00:06:43.230> can 00:06:43.370 --> 00:06:43.380 align:start position:0% it later but as a first step if you can 00:06:43.380 --> 00:06:45.470 align:start position:0% it later but as a first step if you can run<00:06:43.530> some<00:06:43.710> tools<00:06:43.950> that<00:06:44.220> provide<00:06:44.480> some 00:06:45.470 --> 00:06:45.480 align:start position:0% run some tools that provide some 00:06:45.480 --> 00:06:47.300 align:start position:0% run some tools that provide some indications<00:06:46.050> of<00:06:46.140> where<00:06:46.290> to<00:06:46.410> look<00:06:46.620> for 00:06:47.300 --> 00:06:47.310 align:start position:0% indications of where to look for 00:06:47.310 --> 00:06:49.310 align:start position:0% indications of where to look for security<00:06:48.180> vulnerabilities<00:06:48.210> that<00:06:48.810> offers<00:06:49.290> a 00:06:49.310 --> 00:06:49.320 align:start position:0% security vulnerabilities that offers a 00:06:49.320 --> 00:06:52.220 align:start position:0% security vulnerabilities that offers a lot<00:06:49.410> of<00:06:49.560> value<00:06:49.740> for<00:06:49.950> low-cost<00:06:50.910> and<00:06:51.690> and<00:06:52.110> I 00:06:52.220 --> 00:06:52.230 align:start position:0% lot of value for low-cost and and I 00:06:52.230 --> 00:06:53.240 align:start position:0% lot of value for low-cost and and I think<00:06:52.440> that<00:06:52.590> stuff<00:06:52.830> should<00:06:52.980> be<00:06:53.040> in<00:06:53.160> the 00:06:53.240 --> 00:06:53.250 align:start position:0% think that stuff should be in the 00:06:53.250 --> 00:06:54.950 align:start position:0% think that stuff should be in the compiler<00:06:53.700> like<00:06:53.940> in<00:06:54.150> most<00:06:54.420> high-level 00:06:54.950 --> 00:06:54.960 align:start position:0% compiler like in most high-level 00:06:54.960 --> 00:06:56.870 align:start position:0% compiler like in most high-level languages<00:06:55.650> you<00:06:55.800> have<00:06:55.830> that<00:06:56.220> kind<00:06:56.430> of<00:06:56.520> basic 00:06:56.870 --> 00:06:56.880 align:start position:0% languages you have that kind of basic 00:06:56.880 --> 00:06:58.490 align:start position:0% languages you have that kind of basic static<00:06:57.090> analysis<00:06:57.660> already<00:06:58.050> built<00:06:58.230> into<00:06:58.380> the 00:06:58.490 --> 00:06:58.500 align:start position:0% static analysis already built into the 00:06:58.500 --> 00:07:00.290 align:start position:0% static analysis already built into the compiler<00:06:58.980> and<00:06:59.160> there's<00:06:59.700> no<00:06:59.880> reason<00:07:00.210> we 00:07:00.290 --> 00:07:00.300 align:start position:0% compiler and there's no reason we 00:07:00.300 --> 00:07:02.570 align:start position:0% compiler and there's no reason we shouldn't<00:07:00.510> be<00:07:00.630> doing<00:07:00.750> the<00:07:00.960> same<00:07:01.140> here<00:07:01.590> the 00:07:02.570 --> 00:07:02.580 align:start position:0% shouldn't be doing the same here the 00:07:02.580 --> 00:07:05.030 align:start position:0% shouldn't be doing the same here the only<00:07:02.880> caution<00:07:03.360> that<00:07:03.570> I<00:07:03.690> would<00:07:03.870> have<00:07:04.050> is<00:07:04.290> being 00:07:05.030 --> 00:07:05.040 align:start position:0% only caution that I would have is being 00:07:05.040 --> 00:07:07.340 align:start position:0% only caution that I would have is being careful<00:07:05.460> not<00:07:05.640> to<00:07:05.910> just<00:07:06.090> run<00:07:06.390> sort<00:07:06.750> of<00:07:06.840> all<00:07:07.140> the 00:07:07.340 --> 00:07:07.350 align:start position:0% careful not to just run sort of all the 00:07:07.350 --> 00:07:09.170 align:start position:0% careful not to just run sort of all the low<00:07:07.500> effort<00:07:07.680> tools<00:07:08.040> and<00:07:08.370> then<00:07:08.520> call<00:07:08.820> it<00:07:09.030> a 00:07:09.170 --> 00:07:09.180 align:start position:0% low effort tools and then call it a 00:07:09.180 --> 00:07:11.000 align:start position:0% low effort tools and then call it a solve<00:07:09.690> problem<00:07:10.200> and<00:07:10.350> put<00:07:10.470> a<00:07:10.530> bunch<00:07:10.710> of<00:07:10.800> money 00:07:11.000 --> 00:07:11.010 align:start position:0% solve problem and put a bunch of money 00:07:11.010 --> 00:07:12.920 align:start position:0% solve problem and put a bunch of money in<00:07:11.070> the<00:07:11.220> contract<00:07:11.670> because<00:07:11.970> that's<00:07:12.600> something 00:07:12.920 --> 00:07:12.930 align:start position:0% in the contract because that's something 00:07:12.930 --> 00:07:15.380 align:start position:0% in the contract because that's something that<00:07:13.050> happens<00:07:13.200> inside<00:07:14.010> of<00:07:14.280> the<00:07:14.550> corporate 00:07:15.380 --> 00:07:15.390 align:start position:0% that happens inside of the corporate 00:07:15.390 --> 00:07:16.460 align:start position:0% that happens inside of the corporate space<00:07:15.570> and<00:07:15.840> even<00:07:16.080> in<00:07:16.200> high<00:07:16.320> assurance 00:07:16.460 --> 00:07:16.470 align:start position:0% space and even in high assurance 00:07:16.470 --> 00:07:18.140 align:start position:0% space and even in high assurance software<00:07:17.070> all<00:07:17.160> the<00:07:17.280> time<00:07:17.490> where<00:07:17.700> people<00:07:17.730> will 00:07:18.140 --> 00:07:18.150 align:start position:0% software all the time where people will 00:07:18.150 --> 00:07:20.120 align:start position:0% software all the time where people will run<00:07:18.300> a<00:07:18.360> few<00:07:18.600> tools<00:07:18.780> and<00:07:19.230> then<00:07:19.770> assume<00:07:20.100> that 00:07:20.120 --> 00:07:20.130 align:start position:0% run a few tools and then assume that 00:07:20.130 --> 00:07:21.740 align:start position:0% run a few tools and then assume that they<00:07:20.460> have<00:07:20.490> assurance<00:07:21.150> that<00:07:21.330> really<00:07:21.630> isn't 00:07:21.740 --> 00:07:21.750 align:start position:0% they have assurance that really isn't 00:07:21.750 --> 00:07:26.720 align:start position:0% they have assurance that really isn't there<00:07:22.110> so<00:07:24.650> so<00:07:25.650> when<00:07:25.800> we<00:07:25.890> talk<00:07:26.040> about<00:07:26.070> smart 00:07:26.720 --> 00:07:26.730 align:start position:0% there so so when we talk about smart 00:07:26.730 --> 00:07:28.670 align:start position:0% there so so when we talk about smart contract<00:07:27.270> security<00:07:27.780> often<00:07:28.200> you<00:07:28.290> talk<00:07:28.530> about 00:07:28.670 --> 00:07:28.680 align:start position:0% contract security often you talk about 00:07:28.680 --> 00:07:31.850 align:start position:0% contract security often you talk about only<00:07:29.160> from<00:07:29.340> the<00:07:29.490> developer<00:07:30.060> perspective<00:07:30.860> but 00:07:31.850 --> 00:07:31.860 align:start position:0% only from the developer perspective but 00:07:31.860 --> 00:07:33.170 align:start position:0% only from the developer perspective but and<00:07:32.040> is<00:07:32.160> easy<00:07:32.310> to<00:07:32.430> forget<00:07:32.610> that<00:07:32.670> there's<00:07:33.000> also 00:07:33.170 --> 00:07:33.180 align:start position:0% and is easy to forget that there's also 00:07:33.180 --> 00:07:36.590 align:start position:0% and is easy to forget that there's also a<00:07:33.330> user<00:07:33.540> perspective<00:07:33.780> so<00:07:34.820> what<00:07:35.820> what<00:07:36.090> how<00:07:36.420> can 00:07:36.590 --> 00:07:36.600 align:start position:0% a user perspective so what what how can 00:07:36.600 --> 00:07:39.590 align:start position:0% a user perspective so what what how can we<00:07:36.660> make<00:07:36.840> it<00:07:36.870> more<00:07:37.380> secure<00:07:38.280> for<00:07:38.880> end-users<00:07:39.150> to 00:07:39.590 --> 00:07:39.600 align:start position:0% we make it more secure for end-users to 00:07:39.600 --> 00:07:42.890 align:start position:0% we make it more secure for end-users to interact<00:07:40.200> with<00:07:40.350> contracts<00:07:41.390> which<00:07:42.390> may<00:07:42.600> or<00:07:42.780> may 00:07:42.890 --> 00:07:42.900 align:start position:0% interact with contracts which may or may 00:07:42.900 --> 00:07:49.540 align:start position:0% interact with contracts which may or may not<00:07:42.930> be<00:07:43.410> hostile<00:07:44.010> or<00:07:44.220> backdoored<00:07:44.790> or<00:07:45.560> flawed<00:07:46.560> I 00:07:49.540 --> 00:07:49.550 align:start position:0% 00:07:49.550 --> 00:07:53.300 align:start position:0% think<00:07:51.080> like<00:07:52.080> there's<00:07:52.440> always<00:07:52.800> going<00:07:53.190> to<00:07:53.250> be 00:07:53.300 --> 00:07:53.310 align:start position:0% think like there's always going to be 00:07:53.310 --> 00:07:56.360 align:start position:0% think like there's always going to be like<00:07:53.760> a<00:07:54.110> little<00:07:55.110> puzzle<00:07:55.260> so<00:07:55.680> like<00:07:55.860> earlier<00:07:56.220> on 00:07:56.360 --> 00:07:56.370 align:start position:0% like a little puzzle so like earlier on 00:07:56.370 --> 00:07:59.150 align:start position:0% like a little puzzle so like earlier on I<00:07:56.400> mean<00:07:56.640> I<00:07:56.850> mentioned<00:07:57.600> black<00:07:57.720> explorers<00:07:58.350> one 00:07:59.150 --> 00:07:59.160 align:start position:0% I mean I mentioned black explorers one 00:07:59.160 --> 00:08:01.700 align:start position:0% I mean I mentioned black explorers one other<00:07:59.400> possibility<00:08:00.180> is<00:08:00.210> that<00:08:00.530> figure<00:08:01.530> out 00:08:01.700 --> 00:08:01.710 align:start position:0% other possibility is that figure out 00:08:01.710 --> 00:08:04.310 align:start position:0% other possibility is that figure out some<00:08:02.070> kind<00:08:02.310> of<00:08:02.370> what<00:08:03.030> kind<00:08:03.270> of<00:08:03.510> walls<00:08:03.900> or<00:08:04.140> what 00:08:04.310 --> 00:08:04.320 align:start position:0% some kind of what kind of walls or what 00:08:04.320 --> 00:08:05.720 align:start position:0% some kind of what kind of walls or what kind<00:08:04.500> of<00:08:04.560> things<00:08:04.800> should<00:08:05.010> be<00:08:05.130> integrated<00:08:05.340> into 00:08:05.720 --> 00:08:05.730 align:start position:0% kind of things should be integrated into 00:08:05.730 --> 00:08:08.510 align:start position:0% kind of things should be integrated into something<00:08:06.120> like<00:08:06.210> a<00:08:06.270> mist<00:08:06.570> um<00:08:07.410> then<00:08:08.070> of<00:08:08.310> course 00:08:08.510 --> 00:08:08.520 align:start position:0% something like a mist um then of course 00:08:08.520 --> 00:08:09.980 align:start position:0% something like a mist um then of course there's<00:08:08.700> a<00:08:08.790> question<00:08:09.120> of<00:08:09.210> exactly<00:08:09.570> what<00:08:09.750> kinds 00:08:09.980 --> 00:08:09.990 align:start position:0% there's a question of exactly what kinds 00:08:09.990 --> 00:08:12.170 align:start position:0% there's a question of exactly what kinds of<00:08:10.050> things<00:08:10.230> do<00:08:10.350> you<00:08:10.440> get<00:08:10.560> integrated<00:08:11.130> so<00:08:11.460> but 00:08:12.170 --> 00:08:12.180 align:start position:0% of things do you get integrated so but 00:08:12.180 --> 00:08:14.240 align:start position:0% of things do you get integrated so but if<00:08:12.480> it's<00:08:12.750> formal<00:08:13.260> verification<00:08:13.440> checkers 00:08:14.240 --> 00:08:14.250 align:start position:0% if it's formal verification checkers 00:08:14.250 --> 00:08:15.800 align:start position:0% if it's formal verification checkers then<00:08:14.460> like<00:08:14.700> one<00:08:14.880> question<00:08:15.030> is<00:08:15.360> what<00:08:15.570> exactly 00:08:15.800 --> 00:08:15.810 align:start position:0% then like one question is what exactly 00:08:15.810 --> 00:08:17.960 align:start position:0% then like one question is what exactly if<00:08:16.200> you<00:08:16.260> are<00:08:16.380> flying<00:08:16.590> because<00:08:17.340> it's<00:08:17.610> easy<00:08:17.790> to 00:08:17.960 --> 00:08:17.970 align:start position:0% if you are flying because it's easy to 00:08:17.970 --> 00:08:20.270 align:start position:0% if you are flying because it's easy to write<00:08:18.090> a<00:08:18.150> contracts<00:08:18.660> where<00:08:18.930> what<00:08:19.410> if<00:08:19.770> you're<00:08:20.250> a 00:08:20.270 --> 00:08:20.280 align:start position:0% write a contracts where what if you're a 00:08:20.280 --> 00:08:21.500 align:start position:0% write a contracts where what if you're a malicious<00:08:20.670> developer<00:08:21.120> or<00:08:21.180> you<00:08:21.270> write<00:08:21.420> the 00:08:21.500 --> 00:08:21.510 align:start position:0% malicious developer or you write the 00:08:21.510 --> 00:08:23.480 align:start position:0% malicious developer or you write the contracts<00:08:21.960> and<00:08:22.110> you<00:08:22.230> also<00:08:22.530> just<00:08:22.740> like<00:08:23.190> write<00:08:23.460> a 00:08:23.480 --> 00:08:23.490 align:start position:0% contracts and you also just like write a 00:08:23.490 --> 00:08:25.100 align:start position:0% contracts and you also just like write a bunch<00:08:23.730> of<00:08:23.850> weird<00:08:24.120> why<00:08:24.270> three<00:08:24.570> statements<00:08:24.990> and 00:08:25.100 --> 00:08:25.110 align:start position:0% bunch of weird why three statements and 00:08:25.110 --> 00:08:26.660 align:start position:0% bunch of weird why three statements and it<00:08:25.170> looks<00:08:25.350> impressive<00:08:25.740> and<00:08:25.980> looks<00:08:26.130> secure<00:08:26.430> but 00:08:26.660 --> 00:08:26.670 align:start position:0% it looks impressive and looks secure but 00:08:26.670 --> 00:08:28.070 align:start position:0% it looks impressive and looks secure but in<00:08:26.760> reality<00:08:26.910> the<00:08:27.270> why<00:08:27.360> three<00:08:27.570> statements<00:08:27.990> are 00:08:28.070 --> 00:08:28.080 align:start position:0% in reality the why three statements are 00:08:28.080 --> 00:08:30.050 align:start position:0% in reality the why three statements are like<00:08:28.200> missing<00:08:28.560> something<00:08:28.890> that's<00:08:29.100> actually<00:08:29.550> a 00:08:30.050 --> 00:08:30.060 align:start position:0% like missing something that's actually a 00:08:30.060 --> 00:08:30.560 align:start position:0% like missing something that's actually a backdoor 00:08:30.560 --> 00:08:30.570 align:start position:0% backdoor 00:08:30.570 --> 00:08:34.219 align:start position:0% backdoor so<00:08:31.490> there's<00:08:32.490> but<00:08:33.120> that's<00:08:33.360> part<00:08:33.720> of<00:08:33.810> it<00:08:33.960> but<00:08:34.110> the 00:08:34.219 --> 00:08:34.229 align:start position:0% so there's but that's part of it but the 00:08:34.229 --> 00:08:36.980 align:start position:0% so there's but that's part of it but the the<00:08:34.680> other<00:08:34.860> part<00:08:35.160> is<00:08:35.340> even<00:08:36.330> just<00:08:36.360> things<00:08:36.870> like 00:08:36.980 --> 00:08:36.990 align:start position:0% the other part is even just things like 00:08:36.990 --> 00:08:38.600 align:start position:0% the other part is even just things like security<00:08:37.530> auditing<00:08:37.919> and<00:08:38.040> even<00:08:38.250> saying<00:08:38.490> you 00:08:38.600 --> 00:08:38.610 align:start position:0% security auditing and even saying you 00:08:38.610 --> 00:08:40.370 align:start position:0% security auditing and even saying you know<00:08:38.700> I<00:08:38.729> mean<00:08:38.940> this<00:08:39.120> particular<00:08:39.330> contract<00:08:40.020> has 00:08:40.370 --> 00:08:40.380 align:start position:0% know I mean this particular contract has 00:08:40.380 --> 00:08:43.159 align:start position:0% know I mean this particular contract has been<00:08:40.580> audited<00:08:41.580> by<00:08:41.610> like<00:08:42.000> these<00:08:42.690> particular 00:08:43.159 --> 00:08:43.169 align:start position:0% been audited by like these particular 00:08:43.169 --> 00:08:44.810 align:start position:0% been audited by like these particular people<00:08:43.560> this<00:08:43.650> particular<00:08:44.070> contract<00:08:44.340> matches 00:08:44.810 --> 00:08:44.820 align:start position:0% people this particular contract matches 00:08:44.820 --> 00:08:47.000 align:start position:0% people this particular contract matches some<00:08:44.940> particular<00:08:45.330> time 00:08:47.000 --> 00:08:47.010 align:start position:0% some particular time 00:08:47.010 --> 00:08:49.200 align:start position:0% some particular time yeah<00:08:48.010> I<00:08:48.040> think<00:08:48.370> this<00:08:48.670> is<00:08:48.880> this<00:08:49.150> is 00:08:49.200 --> 00:08:49.210 align:start position:0% yeah I think this is this is 00:08:49.210 --> 00:08:51.180 align:start position:0% yeah I think this is this is fundamentally<00:08:49.930> a<00:08:49.960> UX<00:08:50.350> problem<00:08:50.770> and<00:08:50.950> we<00:08:51.010> should 00:08:51.180 --> 00:08:51.190 align:start position:0% fundamentally a UX problem and we should 00:08:51.190 --> 00:08:52.560 align:start position:0% fundamentally a UX problem and we should take<00:08:51.520> inspiration<00:08:51.820> from<00:08:52.090> the<00:08:52.390> work<00:08:52.540> that's 00:08:52.560 --> 00:08:52.570 align:start position:0% take inspiration from the work that's 00:08:52.570 --> 00:08:54.330 align:start position:0% take inspiration from the work that's been<00:08:52.930> done<00:08:52.990> in<00:08:53.140> browsers<00:08:53.680> there's<00:08:53.980> been<00:08:54.130> a<00:08:54.160> lot 00:08:54.330 --> 00:08:54.340 align:start position:0% been done in browsers there's been a lot 00:08:54.340 --> 00:08:56.340 align:start position:0% been done in browsers there's been a lot of<00:08:54.370> work<00:08:54.610> about<00:08:54.850> how<00:08:55.240> to<00:08:55.300> securely<00:08:56.050> browse 00:08:56.340 --> 00:08:56.350 align:start position:0% of work about how to securely browse 00:08:56.350 --> 00:08:57.510 align:start position:0% of work about how to securely browse websites<00:08:56.620> and<00:08:57.130> there<00:08:57.250> are<00:08:57.310> a<00:08:57.340> lot<00:08:57.400> of 00:08:57.510 --> 00:08:57.520 align:start position:0% websites and there are a lot of 00:08:57.520 --> 00:09:00.270 align:start position:0% websites and there are a lot of parallels<00:08:57.880> between<00:08:58.150> that<00:08:58.600> indie<00:08:58.900> apps<00:08:59.160> well<00:09:00.160> I 00:09:00.270 --> 00:09:00.280 align:start position:0% parallels between that indie apps well I 00:09:00.280 --> 00:09:01.680 align:start position:0% parallels between that indie apps well I think<00:09:00.340> are<00:09:00.670> the<00:09:00.760> security<00:09:01.180> model<00:09:01.330> that<00:09:01.600> we 00:09:01.680 --> 00:09:01.690 align:start position:0% think are the security model that we 00:09:01.690 --> 00:09:03.630 align:start position:0% think are the security model that we have<00:09:01.840> here<00:09:01.870> that<00:09:02.650> we're<00:09:02.800> trying<00:09:03.010> to<00:09:03.190> achieve 00:09:03.630 --> 00:09:03.640 align:start position:0% have here that we're trying to achieve 00:09:03.640 --> 00:09:05.580 align:start position:0% have here that we're trying to achieve is<00:09:03.850> definitely<00:09:04.300> a<00:09:04.330> bit<00:09:04.540> stricter<00:09:04.990> as<00:09:05.290> we're 00:09:05.580 --> 00:09:05.590 align:start position:0% is definitely a bit stricter as we're 00:09:05.590 --> 00:09:09.120 align:start position:0% is definitely a bit stricter as we're saying<00:09:05.800> that<00:09:06.040> it's<00:09:06.580> the<00:09:07.210> job<00:09:07.540> of<00:09:07.930> mystic<00:09:08.710> even 00:09:09.120 --> 00:09:09.130 align:start position:0% saying that it's the job of mystic even 00:09:09.130 --> 00:09:12.720 align:start position:0% saying that it's the job of mystic even to<00:09:09.310> protect<00:09:09.760> the<00:09:09.940> user<00:09:10.260> from<00:09:11.260> number<00:09:12.040> one<00:09:12.220> bad 00:09:12.720 --> 00:09:12.730 align:start position:0% to protect the user from number one bad 00:09:12.730 --> 00:09:15.810 align:start position:0% to protect the user from number one bad contracts<00:09:13.300> number<00:09:14.020> two<00:09:14.290> bad<00:09:14.920> interfaces<00:09:15.700> to 00:09:15.810 --> 00:09:15.820 align:start position:0% contracts number two bad interfaces to 00:09:15.820 --> 00:09:17.190 align:start position:0% contracts number two bad interfaces to good<00:09:15.970> contracts<00:09:16.390> we<00:09:16.570> don't<00:09:16.720> even<00:09:16.930> trust<00:09:17.080> the 00:09:17.190 --> 00:09:17.200 align:start position:0% good contracts we don't even trust the 00:09:17.200 --> 00:09:18.630 align:start position:0% good contracts we don't even trust the source<00:09:17.320> or<00:09:17.530> the<00:09:17.560> JavaScript<00:09:18.130> this<00:09:18.310> is<00:09:18.430> Sarah 00:09:18.630 --> 00:09:18.640 align:start position:0% source or the JavaScript this is Sarah 00:09:18.640 --> 00:09:22.170 align:start position:0% source or the JavaScript this is Sarah Lee<00:09:18.790> and<00:09:20.280> and<00:09:21.280> then<00:09:21.610> you<00:09:21.760> know<00:09:21.790> if<00:09:21.940> you<00:09:22.030> have 00:09:22.170 --> 00:09:22.180 align:start position:0% Lee and and then you know if you have 00:09:22.180 --> 00:09:24.120 align:start position:0% Lee and and then you know if you have good<00:09:22.390> contracts<00:09:22.930> and<00:09:23.230> you<00:09:23.260> know<00:09:23.860> you<00:09:23.980> have 00:09:24.120 --> 00:09:24.130 align:start position:0% good contracts and you know you have 00:09:24.130 --> 00:09:25.680 align:start position:0% good contracts and you know you have good<00:09:24.280> JavaScript<00:09:24.850> on<00:09:25.000> top<00:09:25.210> of<00:09:25.360> that<00:09:25.480> there's 00:09:25.680 --> 00:09:25.690 align:start position:0% good JavaScript on top of that there's 00:09:25.690 --> 00:09:27.360 align:start position:0% good JavaScript on top of that there's also<00:09:25.780> built-in<00:09:26.230> user<00:09:26.440> access<00:09:26.860> control<00:09:26.890> which 00:09:27.360 --> 00:09:27.370 align:start position:0% also built-in user access control which 00:09:27.370 --> 00:09:28.920 align:start position:0% also built-in user access control which is<00:09:27.550> you<00:09:28.000> know<00:09:28.090> something<00:09:28.360> that<00:09:28.480> we<00:09:28.630> can<00:09:28.780> have<00:09:28.900> a 00:09:28.920 --> 00:09:28.930 align:start position:0% is you know something that we can have a 00:09:28.930 --> 00:09:32.580 align:start position:0% is you know something that we can have a catalan<00:09:29.380> all<00:09:29.560> by<00:09:29.890> itself<00:09:30.220> so<00:09:31.200> if<00:09:32.200> you<00:09:32.320> make<00:09:32.470> the 00:09:32.580 --> 00:09:32.590 align:start position:0% catalan all by itself so if you make the 00:09:32.590 --> 00:09:35.580 align:start position:0% catalan all by itself so if you make the comparison<00:09:33.220> to<00:09:33.430> to<00:09:33.850> for<00:09:34.150> example<00:09:34.210> the<00:09:34.600> web<00:09:35.170> and 00:09:35.580 --> 00:09:35.590 align:start position:0% comparison to to for example the web and 00:09:35.590 --> 00:09:37.260 align:start position:0% comparison to to for example the web and just<00:09:35.800> browse<00:09:36.160> the<00:09:36.460> internet<00:09:36.790> with<00:09:36.940> with 00:09:37.260 --> 00:09:37.270 align:start position:0% just browse the internet with with 00:09:37.270 --> 00:09:40.230 align:start position:0% just browse the internet with with google<00:09:37.780> chrome<00:09:38.020> you<00:09:38.290> have<00:09:39.280> their<00:09:39.850> blacklist 00:09:40.230 --> 00:09:40.240 align:start position:0% google chrome you have their blacklist 00:09:40.240 --> 00:09:42.510 align:start position:0% google chrome you have their blacklist approach<00:09:40.840> where<00:09:41.290> they<00:09:41.440> tried<00:09:42.160> to<00:09:42.190> access 00:09:42.510 --> 00:09:42.520 align:start position:0% approach where they tried to access 00:09:42.520 --> 00:09:44.430 align:start position:0% approach where they tried to access something<00:09:42.880> which<00:09:43.150> is<00:09:43.300> known<00:09:43.570> bad<00:09:43.900> and<00:09:44.230> they 00:09:44.430 --> 00:09:44.440 align:start position:0% something which is known bad and they 00:09:44.440 --> 00:09:48.150 align:start position:0% something which is known bad and they alert<00:09:44.680> you<00:09:45.000> so<00:09:46.000> do<00:09:46.960> you<00:09:47.050> see<00:09:47.320> that<00:09:47.350> as<00:09:47.800> a 00:09:48.150 --> 00:09:48.160 align:start position:0% alert you so do you see that as a 00:09:48.160 --> 00:09:51.390 align:start position:0% alert you so do you see that as a possible<00:09:48.790> way<00:09:48.940> forward<00:09:49.360> or<00:09:49.630> more<00:09:50.470> reputation 00:09:51.390 --> 00:09:51.400 align:start position:0% possible way forward or more reputation 00:09:51.400 --> 00:09:54.930 align:start position:0% possible way forward or more reputation about<00:09:51.930> reputation<00:09:52.930> systems<00:09:53.710> for<00:09:54.010> known<00:09:54.520> good 00:09:54.930 --> 00:09:54.940 align:start position:0% about reputation systems for known good 00:09:54.940 --> 00:09:58.710 align:start position:0% about reputation systems for known good contracts<00:09:55.660> financial<00:09:56.200> services<00:09:56.590> you<00:09:57.630> know<00:09:58.630> as 00:09:58.710 --> 00:09:58.720 align:start position:0% contracts financial services you know as 00:09:58.720 --> 00:10:01.080 align:start position:0% contracts financial services you know as far<00:09:58.900> as<00:09:58.960> reputation<00:09:59.680> systems<00:10:00.070> go<00:10:00.250> reputation 00:10:01.080 --> 00:10:01.090 align:start position:0% far as reputation systems go reputation 00:10:01.090 --> 00:10:02.820 align:start position:0% far as reputation systems go reputation systems<00:10:01.420> go<00:10:01.570> like<00:10:01.780> the<00:10:01.900> two<00:10:02.080> are<00:10:02.320> sort<00:10:02.560> of<00:10:02.620> flow 00:10:02.820 --> 00:10:02.830 align:start position:0% systems go like the two are sort of flow 00:10:02.830 --> 00:10:04.440 align:start position:0% systems go like the two are sort of flow into<00:10:03.070> each<00:10:03.190> other<00:10:03.400> like<00:10:03.580> a<00:10:03.700> blacklist<00:10:04.240> as<00:10:04.420> a 00:10:04.440 --> 00:10:04.450 align:start position:0% into each other like a blacklist as a 00:10:04.450 --> 00:10:06.060 align:start position:0% into each other like a blacklist as a reputation<00:10:04.720> system<00:10:05.230> with<00:10:05.530> a<00:10:05.560> default<00:10:05.950> this 00:10:06.060 --> 00:10:06.070 align:start position:0% reputation system with a default this 00:10:06.070 --> 00:10:07.500 align:start position:0% reputation system with a default this euro<00:10:06.310> and<00:10:06.520> can<00:10:06.610> go<00:10:06.760> negative<00:10:06.940> and<00:10:07.240> the<00:10:07.360> other 00:10:07.500 --> 00:10:07.510 align:start position:0% euro and can go negative and the other 00:10:07.510 --> 00:10:08.940 align:start position:0% euro and can go negative and the other one<00:10:07.690> is<00:10:07.810> where<00:10:07.930> the<00:10:08.020> default<00:10:08.320> is<00:10:08.440> euro<00:10:08.680> one<00:10:08.830> can 00:10:08.940 --> 00:10:08.950 align:start position:0% one is where the default is euro one can 00:10:08.950 --> 00:10:12.480 align:start position:0% one is where the default is euro one can go<00:10:09.130> positive<00:10:09.640> and<00:10:10.360> I<00:10:10.630> think<00:10:11.020> both<00:10:11.980> approaches 00:10:12.480 --> 00:10:12.490 align:start position:0% go positive and I think both approaches 00:10:12.490 --> 00:10:16.680 align:start position:0% go positive and I think both approaches have<00:10:12.670> their<00:10:12.820> merits<00:10:13.030> so<00:10:13.930> for<00:10:15.150> example<00:10:16.150> I<00:10:16.210> think 00:10:16.680 --> 00:10:16.690 align:start position:0% have their merits so for example I think 00:10:16.690 --> 00:10:18.810 align:start position:0% have their merits so for example I think there<00:10:16.840> are<00:10:17.020> there<00:10:17.680> are<00:10:17.740> some<00:10:18.130> kinds<00:10:18.520> of<00:10:18.640> white 00:10:18.810 --> 00:10:18.820 align:start position:0% there are there are some kinds of white 00:10:18.820 --> 00:10:21.360 align:start position:0% there are there are some kinds of white whitelisted<00:10:19.630> that<00:10:20.170> do<00:10:20.260> you<00:10:20.320> make<00:10:20.470> sense<00:10:20.740> so 00:10:21.360 --> 00:10:21.370 align:start position:0% whitelisted that do you make sense so 00:10:21.370 --> 00:10:24.180 align:start position:0% whitelisted that do you make sense so for<00:10:21.550> example<00:10:22.120> if<00:10:22.300> you<00:10:22.600> are<00:10:22.890> accessing<00:10:23.890> some 00:10:24.180 --> 00:10:24.190 align:start position:0% for example if you are accessing some 00:10:24.190 --> 00:10:25.740 align:start position:0% for example if you are accessing some particular<00:10:24.550> application<00:10:25.120> and<00:10:25.330> then<00:10:25.720> the 00:10:25.740 --> 00:10:25.750 align:start position:0% particular application and then the 00:10:25.750 --> 00:10:27.330 align:start position:0% particular application and then the application<00:10:25.840> all<00:10:26.590> of<00:10:26.680> a<00:10:26.740> sudden<00:10:27.010> decides 00:10:27.330 --> 00:10:27.340 align:start position:0% application all of a sudden decides 00:10:27.340 --> 00:10:30.660 align:start position:0% application all of a sudden decides stoical<00:10:28.140> force<00:10:29.140> your<00:10:29.500> accounts<00:10:29.920> to<00:10:30.040> call<00:10:30.310> to 00:10:30.660 --> 00:10:30.670 align:start position:0% stoical force your accounts to call to 00:10:30.670 --> 00:10:32.190 align:start position:0% stoical force your accounts to call to do<00:10:30.820> a<00:10:30.850> call<00:10:31.210> to<00:10:31.540> some<00:10:31.780> people<00:10:32.020> you<00:10:32.110> look 00:10:32.190 --> 00:10:32.200 align:start position:0% do a call to some people you look 00:10:32.200 --> 00:10:33.510 align:start position:0% do a call to some people you look unknown<00:10:32.470> address<00:10:32.890> with<00:10:33.040> a<00:10:33.070> large<00:10:33.250> amount<00:10:33.490> of 00:10:33.510 --> 00:10:33.520 align:start position:0% unknown address with a large amount of 00:10:33.520 --> 00:10:34.890 align:start position:0% unknown address with a large amount of gas<00:10:33.670> and<00:10:33.880> a<00:10:33.940> large<00:10:34.090> amount<00:10:34.300> of<00:10:34.330> data<00:10:34.510> you<00:10:34.750> might 00:10:34.890 --> 00:10:34.900 align:start position:0% gas and a large amount of data you might 00:10:34.900 --> 00:10:37.350 align:start position:0% gas and a large amount of data you might want<00:10:35.080> to<00:10:35.140> make<00:10:35.710> sure<00:10:35.950> that<00:10:36.160> be<00:10:36.760> concerned<00:10:37.210> that 00:10:37.350 --> 00:10:37.360 align:start position:0% want to make sure that be concerned that 00:10:37.360 --> 00:10:38.730 align:start position:0% want to make sure that be concerned that maybe<00:10:37.660> that<00:10:37.900> call<00:10:38.140> is<00:10:38.320> like<00:10:38.500> actually 00:10:38.730 --> 00:10:38.740 align:start position:0% maybe that call is like actually 00:10:38.740 --> 00:10:40.470 align:start position:0% maybe that call is like actually stealing<00:10:39.280> all<00:10:39.550> of<00:10:39.610> your<00:10:39.730> maker<00:10:39.910> coins<00:10:40.270> or 00:10:40.470 --> 00:10:40.480 align:start position:0% stealing all of your maker coins or 00:10:40.480 --> 00:10:42.900 align:start position:0% stealing all of your maker coins or something<00:10:40.780> similar<00:10:40.990> and<00:10:41.290> so<00:10:41.860> I<00:10:41.890> an<00:10:42.550> approach 00:10:42.900 --> 00:10:42.910 align:start position:0% something similar and so I an approach 00:10:42.910 --> 00:10:44.880 align:start position:0% something similar and so I an approach that<00:10:42.940> explicitly<00:10:43.810> asks<00:10:44.350> for<00:10:44.470> your<00:10:44.560> permission 00:10:44.880 --> 00:10:44.890 align:start position:0% that explicitly asks for your permission 00:10:44.890 --> 00:10:46.470 align:start position:0% that explicitly asks for your permission if<00:10:45.100> it's<00:10:45.220> outside<00:10:45.520> of<00:10:45.670> some<00:10:45.820> way<00:10:45.970> whitelist 00:10:46.470 --> 00:10:46.480 align:start position:0% if it's outside of some way whitelist 00:10:46.480 --> 00:10:47.820 align:start position:0% if it's outside of some way whitelist might<00:10:46.660> be<00:10:46.780> a<00:10:46.810> good<00:10:46.990> way<00:10:47.110> of<00:10:47.140> mitigating<00:10:47.320> that 00:10:47.820 --> 00:10:47.830 align:start position:0% might be a good way of mitigating that 00:10:47.830 --> 00:10:49.710 align:start position:0% might be a good way of mitigating that me<00:10:48.550> and<00:10:48.670> well<00:10:48.790> if<00:10:48.970> there<00:10:49.120> is<00:10:49.150> some<00:10:49.510> like<00:10:49.690> a 00:10:49.710 --> 00:10:49.720 align:start position:0% me and well if there is some like a 00:10:49.720 --> 00:10:51.660 align:start position:0% me and well if there is some like a known<00:10:49.930> black<00:10:50.230> quest<00:10:50.530> then<00:10:50.830> that's<00:10:51.430> something 00:10:51.660 --> 00:10:51.670 align:start position:0% known black quest then that's something 00:10:51.670 --> 00:10:54.300 align:start position:0% known black quest then that's something I<00:10:51.970> am<00:10:52.090> you<00:10:52.780> could<00:10:52.930> provide<00:10:53.590> like<00:10:53.890> you've<00:10:54.040> even 00:10:54.300 --> 00:10:54.310 align:start position:0% I am you could provide like you've even 00:10:54.310 --> 00:10:56.980 align:start position:0% I am you could provide like you've even stronger<00:10:54.700> warnings<00:10:55.150> about<00:10:55.270> so<00:10:56.170> it's 00:10:56.980 --> 00:10:56.990 align:start position:0% stronger warnings about so it's 00:10:56.990 --> 00:10:59.949 align:start position:0% stronger warnings about so it's it<00:10:57.709> depends<00:10:58.310> on<00:10:58.540> what<00:10:59.540> it<00:10:59.630> is<00:10:59.660> that<00:10:59.870> you're 00:10:59.949 --> 00:10:59.959 align:start position:0% it depends on what it is that you're 00:10:59.959 --> 00:11:01.780 align:start position:0% it depends on what it is that you're blocking<00:11:00.410> and<00:11:00.560> it<00:11:00.620> also<00:11:00.770> depends<00:11:01.310> on<00:11:01.399> sort<00:11:01.700> of 00:11:01.780 --> 00:11:01.790 align:start position:0% blocking and it also depends on sort of 00:11:01.790 --> 00:11:03.340 align:start position:0% blocking and it also depends on sort of what<00:11:02.000> the<00:11:02.120> consequences<00:11:02.420> are<00:11:02.899> of<00:11:03.110> you<00:11:03.230> know 00:11:03.340 --> 00:11:03.350 align:start position:0% what the consequences are of you know 00:11:03.350 --> 00:11:04.810 align:start position:0% what the consequences are of you know something<00:11:03.680> being<00:11:03.950> outside<00:11:04.310> of<00:11:04.370> the<00:11:04.520> whitelist 00:11:04.810 --> 00:11:04.820 align:start position:0% something being outside of the whitelist 00:11:04.820 --> 00:11:07.960 align:start position:0% something being outside of the whitelist or<00:11:05.000> inside<00:11:05.270> the<00:11:05.300> blacklist<00:11:05.810> and<00:11:06.490> I<00:11:07.490> do<00:11:07.610> think 00:11:07.960 --> 00:11:07.970 align:start position:0% or inside the blacklist and I do think 00:11:07.970 --> 00:11:10.720 align:start position:0% or inside the blacklist and I do think that<00:11:08.209> the<00:11:08.750> web<00:11:09.080> access<00:11:10.070> control<00:11:10.430> on<00:11:10.520> the<00:11:10.610> web 00:11:10.720 --> 00:11:10.730 align:start position:0% that the web access control on the web 00:11:10.730 --> 00:11:13.000 align:start position:0% that the web access control on the web is<00:11:10.880> a<00:11:10.910> good<00:11:11.209> good<00:11:12.170> comparison<00:11:12.529> from<00:11:12.800> a<00:11:12.860> UI 00:11:13.000 --> 00:11:13.010 align:start position:0% is a good good comparison from a UI 00:11:13.010 --> 00:11:16.180 align:start position:0% is a good good comparison from a UI perspective<00:11:13.760> and<00:11:14.440> the<00:11:15.440> industry's<00:11:15.890> had<00:11:16.070> to 00:11:16.180 --> 00:11:16.190 align:start position:0% perspective and the industry's had to 00:11:16.190 --> 00:11:17.769 align:start position:0% perspective and the industry's had to deal<00:11:16.399> with<00:11:16.430> how<00:11:17.029> do<00:11:17.089> you<00:11:17.209> communicate<00:11:17.390> to 00:11:17.769 --> 00:11:17.779 align:start position:0% deal with how do you communicate to 00:11:17.779 --> 00:11:19.630 align:start position:0% deal with how do you communicate to users<00:11:18.260> that<00:11:18.410> this<00:11:18.560> is<00:11:18.709> a<00:11:18.740> risk<00:11:19.010> but<00:11:19.610> a 00:11:19.630 --> 00:11:19.640 align:start position:0% users that this is a risk but a 00:11:19.640 --> 00:11:21.400 align:start position:0% users that this is a risk but a particular<00:11:20.120> type<00:11:20.330> of<00:11:20.360> risk<00:11:20.690> so<00:11:20.959> the<00:11:21.050> same<00:11:21.230> way 00:11:21.400 --> 00:11:21.410 align:start position:0% particular type of risk so the same way 00:11:21.410 --> 00:11:22.840 align:start position:0% particular type of risk so the same way that<00:11:21.589> you<00:11:21.709> would<00:11:21.800> download<00:11:22.010> an<00:11:22.310> app<00:11:22.490> and<00:11:22.760> they 00:11:22.840 --> 00:11:22.850 align:start position:0% that you would download an app and they 00:11:22.850 --> 00:11:25.750 align:start position:0% that you would download an app and they would<00:11:22.970> ask<00:11:23.089> permission<00:11:23.420> to<00:11:23.839> use<00:11:23.930> a<00:11:23.990> camera<00:11:24.760> you 00:11:25.750 --> 00:11:25.760 align:start position:0% would ask permission to use a camera you 00:11:25.760 --> 00:11:28.090 align:start position:0% would ask permission to use a camera you know<00:11:25.850> if<00:11:26.000> you<00:11:26.120> flood<00:11:27.110> the<00:11:27.230> user<00:11:27.410> with<00:11:27.740> too<00:11:27.950> many 00:11:28.090 --> 00:11:28.100 align:start position:0% know if you flood the user with too many 00:11:28.100 --> 00:11:30.280 align:start position:0% know if you flood the user with too many of<00:11:28.250> those<00:11:28.339> warnings<00:11:28.820> you<00:11:29.060> just<00:11:29.570> entrain<00:11:30.110> them 00:11:30.280 --> 00:11:30.290 align:start position:0% of those warnings you just entrain them 00:11:30.290 --> 00:11:34.150 align:start position:0% of those warnings you just entrain them to<00:11:30.440> click<00:11:30.620> ok<00:11:31.060> and<00:11:32.350> but<00:11:33.350> if<00:11:33.470> you<00:11:33.560> don't<00:11:33.830> provide 00:11:34.150 --> 00:11:34.160 align:start position:0% to click ok and but if you don't provide 00:11:34.160 --> 00:11:37.780 align:start position:0% to click ok and but if you don't provide the<00:11:34.730> correct<00:11:35.000> access<00:11:35.209> control<00:11:35.839> for<00:11:36.459> the<00:11:37.459> for 00:11:37.780 --> 00:11:37.790 align:start position:0% the correct access control for the for 00:11:37.790 --> 00:11:39.449 align:start position:0% the correct access control for the for the<00:11:37.850> correct<00:11:38.089> types<00:11:38.300> of<00:11:38.420> operations<00:11:38.959> then 00:11:39.449 --> 00:11:39.459 align:start position:0% the correct types of operations then 00:11:39.459 --> 00:11:42.850 align:start position:0% the correct types of operations then then<00:11:40.459> the<00:11:41.060> security<00:11:41.330> is<00:11:41.600> worse<00:11:41.779> so<00:11:42.020> I<00:11:42.260> think<00:11:42.649> we 00:11:42.850 --> 00:11:42.860 align:start position:0% then the security is worse so I think we 00:11:42.860 --> 00:11:44.470 align:start position:0% then the security is worse so I think we do<00:11:43.040> at<00:11:43.220> least<00:11:43.370> from<00:11:43.459> a<00:11:43.580> UI<00:11:43.700> perspective<00:11:44.330> we 00:11:44.470 --> 00:11:44.480 align:start position:0% do at least from a UI perspective we 00:11:44.480 --> 00:11:46.420 align:start position:0% do at least from a UI perspective we have<00:11:44.690> a<00:11:44.990> kind<00:11:45.380> of<00:11:45.440> comparison<00:11:45.980> and<00:11:46.130> like<00:11:46.250> how 00:11:46.420 --> 00:11:46.430 align:start position:0% have a kind of comparison and like how 00:11:46.430 --> 00:11:48.550 align:start position:0% have a kind of comparison and like how do<00:11:46.490> you<00:11:46.670> create<00:11:47.420> something<00:11:47.870> for<00:11:48.170> the<00:11:48.320> user 00:11:48.550 --> 00:11:48.560 align:start position:0% do you create something for the user 00:11:48.560 --> 00:11:52.690 align:start position:0% do you create something for the user that<00:11:48.950> is<00:11:49.279> both<00:11:49.820> simple<00:11:50.089> and<00:11:51.339> provides<00:11:52.339> those 00:11:52.690 --> 00:11:52.700 align:start position:0% that is both simple and provides those 00:11:52.700 --> 00:11:55.210 align:start position:0% that is both simple and provides those the<00:11:53.209> the<00:11:53.570> robust<00:11:53.959> robust<00:11:54.470> security<00:11:54.920> measures 00:11:55.210 --> 00:11:55.220 align:start position:0% the the robust robust security measures 00:11:55.220 --> 00:11:56.829 align:start position:0% the the robust robust security measures against<00:11:55.640> things<00:11:55.760> like<00:11:55.910> sending<00:11:56.510> lots<00:11:56.660> of 00:11:56.829 --> 00:11:56.839 align:start position:0% against things like sending lots of 00:11:56.839 --> 00:11:59.620 align:start position:0% against things like sending lots of ether<00:11:57.410> or<00:11:57.560> whatever<00:11:58.209> there's<00:11:59.209> also<00:11:59.420> an 00:11:59.620 --> 00:11:59.630 align:start position:0% ether or whatever there's also an 00:11:59.630 --> 00:12:01.900 align:start position:0% ether or whatever there's also an opportunity<00:11:59.839> for<00:12:00.410> some<00:12:00.620> of<00:12:00.770> the<00:12:00.920> existing 00:12:01.900 --> 00:12:01.910 align:start position:0% opportunity for some of the existing 00:12:01.910 --> 00:12:03.970 align:start position:0% opportunity for some of the existing early<00:12:02.270> adapt<00:12:02.870> development<00:12:03.380> companies<00:12:03.740> in<00:12:03.890> the 00:12:03.970 --> 00:12:03.980 align:start position:0% early adapt development companies in the 00:12:03.980 --> 00:12:06.040 align:start position:0% early adapt development companies in the space<00:12:04.100> to<00:12:04.430> set<00:12:04.579> a<00:12:04.610> standard<00:12:05.089> so<00:12:05.720> what<00:12:05.870> one 00:12:06.040 --> 00:12:06.050 align:start position:0% space to set a standard so what one 00:12:06.050 --> 00:12:07.900 align:start position:0% space to set a standard so what one thing<00:12:06.260> that<00:12:06.380> we<00:12:06.500> don't<00:12:06.740> want<00:12:06.950> for<00:12:07.040> example<00:12:07.190> is 00:12:07.900 --> 00:12:07.910 align:start position:0% thing that we don't want for example is 00:12:07.910 --> 00:12:10.090 align:start position:0% thing that we don't want for example is a<00:12:08.240> situation<00:12:08.779> where<00:12:09.440> it's<00:12:09.620> just<00:12:09.770> like<00:12:09.890> an 00:12:10.090 --> 00:12:10.100 align:start position:0% a situation where it's just like an 00:12:10.100 --> 00:12:11.889 align:start position:0% a situation where it's just like an accepted<00:12:10.550> defaults<00:12:11.029> to<00:12:11.180> like<00:12:11.300> ask<00:12:11.540> for<00:12:11.750> every 00:12:11.889 --> 00:12:11.899 align:start position:0% accepted defaults to like ask for every 00:12:11.899 --> 00:12:13.930 align:start position:0% accepted defaults to like ask for every single<00:12:12.110> permission<00:12:12.560> Under<00:12:12.740> the<00:12:12.770> Sun<00:12:13.040> is<00:12:13.459> what 00:12:13.930 --> 00:12:13.940 align:start position:0% single permission Under the Sun is what 00:12:13.940 --> 00:12:15.610 align:start position:0% single permission Under the Sun is what to<00:12:14.029> do<00:12:14.180> that<00:12:14.360> then<00:12:14.540> you<00:12:14.570> just<00:12:14.690> work<00:12:14.990> with<00:12:15.020> the 00:12:15.610 --> 00:12:15.620 align:start position:0% to do that then you just work with the 00:12:15.620 --> 00:12:18.400 align:start position:0% to do that then you just work with the value<00:12:15.890> of<00:12:15.980> this<00:12:16.100> is<00:12:16.220> the<00:12:16.339> place<00:12:16.970> but<00:12:17.300> if<00:12:18.050> on<00:12:18.320> the 00:12:18.400 --> 00:12:18.410 align:start position:0% value of this is the place but if on the 00:12:18.410 --> 00:12:19.449 align:start position:0% value of this is the place but if on the other<00:12:18.529> hand<00:12:18.620> you<00:12:19.010> know<00:12:19.130> a<00:12:19.190> lot<00:12:19.430> of 00:12:19.449 --> 00:12:19.459 align:start position:0% other hand you know a lot of 00:12:19.459 --> 00:12:21.699 align:start position:0% other hand you know a lot of applications<00:12:20.180> are<00:12:20.420> designed<00:12:20.870> in<00:12:21.230> such<00:12:21.260> a<00:12:21.470> way 00:12:21.699 --> 00:12:21.709 align:start position:0% applications are designed in such a way 00:12:21.709 --> 00:12:24.100 align:start position:0% applications are designed in such a way that<00:12:21.740> they<00:12:22.040> use<00:12:22.220> flow<00:12:23.180> nicely<00:12:23.450> with<00:12:23.839> the<00:12:23.959> act 00:12:24.100 --> 00:12:24.110 align:start position:0% that they use flow nicely with the act 00:12:24.110 --> 00:12:26.650 align:start position:0% that they use flow nicely with the act with<00:12:24.440> the<00:12:25.399> security<00:12:25.880> and<00:12:26.000> access<00:12:26.120> control 00:12:26.650 --> 00:12:26.660 align:start position:0% with the security and access control 00:12:26.660 --> 00:12:29.010 align:start position:0% with the security and access control that<00:12:26.690> exists<00:12:27.290> then<00:12:27.560> something<00:12:28.459> that<00:12:28.579> doesn't 00:12:29.010 --> 00:12:29.020 align:start position:0% that exists then something that doesn't 00:12:29.020 --> 00:12:31.540 align:start position:0% that exists then something that doesn't sort<00:12:30.020> of<00:12:30.140> fit<00:12:30.589> those<00:12:30.770> patterns<00:12:31.160> would<00:12:31.370> be 00:12:31.540 --> 00:12:31.550 align:start position:0% sort of fit those patterns would be 00:12:31.550 --> 00:12:33.670 align:start position:0% sort of fit those patterns would be would<00:12:31.940> actually<00:12:32.270> get<00:12:32.990> looked<00:12:33.230> at<00:12:33.380> much<00:12:33.529> more 00:12:33.670 --> 00:12:33.680 align:start position:0% would actually get looked at much more 00:12:33.680 --> 00:12:41.150 align:start position:0% would actually get looked at much more suspicious<00:12:34.130> to<00:12:34.220> me<00:12:34.279> which<00:12:34.430> is<00:12:34.459> what<00:12:34.670> we<00:12:34.760> will 00:12:41.150 --> 00:12:41.160 align:start position:0% 00:12:41.160 --> 00:12:44.310 align:start position:0% I'm<00:12:42.160> gonna<00:12:42.370> ask<00:12:42.550> a<00:12:42.730> direct<00:12:43.360> question<00:12:43.630> so<00:12:44.050> in 00:12:44.310 --> 00:12:44.320 align:start position:0% I'm gonna ask a direct question so in 00:12:44.320 --> 00:12:47.580 align:start position:0% I'm gonna ask a direct question so in the<00:12:44.620> as<00:12:45.100> of<00:12:46.030> today<00:12:46.390> with<00:12:46.690> the<00:12:46.810> languages<00:12:47.290> we 00:12:47.580 --> 00:12:47.590 align:start position:0% the as of today with the languages we 00:12:47.590 --> 00:12:49.800 align:start position:0% the as of today with the languages we have<00:12:47.800> if<00:12:48.610> you<00:12:48.700> want<00:12:48.970> to<00:12:49.060> ride<00:12:49.240> secure 00:12:49.800 --> 00:12:49.810 align:start position:0% have if you want to ride secure 00:12:49.810 --> 00:12:53.520 align:start position:0% have if you want to ride secure contracts<00:12:50.410> is<00:12:50.860> it<00:12:51.490> possible<00:12:51.940> to<00:12:52.390> develop<00:12:53.230> a 00:12:53.520 --> 00:12:53.530 align:start position:0% contracts is it possible to develop a 00:12:53.530 --> 00:12:57.360 align:start position:0% contracts is it possible to develop a secure<00:12:53.860> contract<00:12:54.400> without<00:12:55.150> knowing<00:12:56.370> pretty 00:12:57.360 --> 00:12:57.370 align:start position:0% secure contract without knowing pretty 00:12:57.370 --> 00:13:00.170 align:start position:0% secure contract without knowing pretty much<00:12:57.580> in<00:12:57.790> depth<00:12:58.120> how<00:12:58.510> the<00:12:58.870> VM<00:12:59.290> works 00:13:00.170 --> 00:13:00.180 align:start position:0% much in depth how the VM works 00:13:00.180 --> 00:13:04.340 align:start position:0% much in depth how the VM works underneath<00:13:01.180> the<00:13:01.810> language<00:13:02.140> level<00:13:02.350> the<00:13:03.160> quirks 00:13:04.340 --> 00:13:04.350 align:start position:0% underneath the language level the quirks 00:13:04.350 --> 00:13:07.170 align:start position:0% underneath the language level the quirks nothing<00:13:05.350> of<00:13:05.500> any<00:13:05.650> complexity<00:13:06.190> I'd<00:13:06.460> say<00:13:06.730> I<00:13:06.940> mean 00:13:07.170 --> 00:13:07.180 align:start position:0% nothing of any complexity I'd say I mean 00:13:07.180 --> 00:13:08.580 align:start position:0% nothing of any complexity I'd say I mean if<00:13:07.270> you<00:13:07.360> have<00:13:07.510> something<00:13:07.750> very<00:13:07.990> simple<00:13:08.440> that's 00:13:08.580 --> 00:13:08.590 align:start position:0% if you have something very simple that's 00:13:08.590 --> 00:13:10.200 align:start position:0% if you have something very simple that's following<00:13:08.980> an<00:13:09.070> established<00:13:09.520> pattern<00:13:09.700> sure 00:13:10.200 --> 00:13:10.210 align:start position:0% following an established pattern sure 00:13:10.210 --> 00:13:12.540 align:start position:0% following an established pattern sure but<00:13:11.020> if<00:13:11.140> you're<00:13:11.290> going<00:13:11.530> into<00:13:11.860> some<00:13:12.070> new<00:13:12.250> space 00:13:12.540 --> 00:13:12.550 align:start position:0% but if you're going into some new space 00:13:12.550 --> 00:13:14.340 align:start position:0% but if you're going into some new space then<00:13:13.030> yeah<00:13:13.300> you<00:13:13.360> should<00:13:13.660> understand<00:13:14.110> how<00:13:14.230> the 00:13:14.340 --> 00:13:14.350 align:start position:0% then yeah you should understand how the 00:13:14.350 --> 00:13:16.380 align:start position:0% then yeah you should understand how the internals<00:13:14.890> affect<00:13:15.190> your<00:13:15.370> contract<00:13:15.940> or<00:13:16.150> have 00:13:16.380 --> 00:13:16.390 align:start position:0% internals affect your contract or have 00:13:16.390 --> 00:13:18.420 align:start position:0% internals affect your contract or have someone<00:13:16.720> look<00:13:16.870> at<00:13:16.960> it<00:13:17.020> because<00:13:17.230> you<00:13:17.710> know 00:13:18.420 --> 00:13:18.430 align:start position:0% someone look at it because you know 00:13:18.430 --> 00:13:20.520 align:start position:0% someone look at it because you know ideally<00:13:18.820> I<00:13:19.030> think<00:13:19.420> we'd<00:13:19.690> wants<00:13:20.020> to<00:13:20.110> reach<00:13:20.290> them 00:13:20.520 --> 00:13:20.530 align:start position:0% ideally I think we'd wants to reach them 00:13:20.530 --> 00:13:22.080 align:start position:0% ideally I think we'd wants to reach them reach<00:13:20.710> the<00:13:20.920> stage<00:13:21.190> where<00:13:21.250> like<00:13:21.580> the<00:13:21.700> language 00:13:22.080 --> 00:13:22.090 align:start position:0% reach the stage where like the language 00:13:22.090 --> 00:13:25.920 align:start position:0% reach the stage where like the language is<00:13:22.210> intuitive<00:13:22.750> and<00:13:22.780> like<00:13:23.370> the<00:13:24.750> limitations<00:13:25.750> in 00:13:25.920 --> 00:13:25.930 align:start position:0% is intuitive and like the limitations in 00:13:25.930 --> 00:13:29.040 align:start position:0% is intuitive and like the limitations in the<00:13:26.020> VM<00:13:26.260> layer<00:13:26.470> don't<00:13:26.830> really<00:13:27.130> yeah<00:13:27.430> look<00:13:28.390> it 00:13:29.040 --> 00:13:29.050 align:start position:0% the VM layer don't really yeah look it 00:13:29.050 --> 00:13:30.600 align:start position:0% the VM layer don't really yeah look it cause<00:13:29.290> any<00:13:29.470> quirks<00:13:29.950> that<00:13:30.070> are<00:13:30.280> sort<00:13:30.550> of 00:13:30.600 --> 00:13:30.610 align:start position:0% cause any quirks that are sort of 00:13:30.610 --> 00:13:33.360 align:start position:0% cause any quirks that are sort of unexpected<00:13:31.300> that<00:13:31.840> don't<00:13:32.050> appear<00:13:32.440> at<00:13:32.950> this<00:13:33.190> at 00:13:33.360 --> 00:13:33.370 align:start position:0% unexpected that don't appear at this at 00:13:33.370 --> 00:13:35.280 align:start position:0% unexpected that don't appear at this at the<00:13:33.610> solidity<00:13:33.970> level<00:13:34.330> itself<00:13:34.660> but<00:13:35.140> at<00:13:35.230> the 00:13:35.280 --> 00:13:35.290 align:start position:0% the solidity level itself but at the 00:13:35.290 --> 00:13:37.080 align:start position:0% the solidity level itself but at the same<00:13:35.470> time<00:13:35.680> we're<00:13:35.860> not<00:13:35.890> quite<00:13:36.190> there<00:13:36.400> yet<00:13:36.460> so 00:13:37.080 --> 00:13:37.090 align:start position:0% same time we're not quite there yet so 00:13:37.090 --> 00:13:39.330 align:start position:0% same time we're not quite there yet so look<00:13:37.450> we<00:13:37.600> have<00:13:37.870> thing<00:13:38.200> you<00:13:38.980> know<00:13:39.070> we<00:13:39.160> have 00:13:39.330 --> 00:13:39.340 align:start position:0% look we have thing you know we have 00:13:39.340 --> 00:13:41.220 align:start position:0% look we have thing you know we have things<00:13:39.520> to<00:13:39.670> worry<00:13:39.910> about<00:13:39.970> like<00:13:40.180> gasps<00:13:40.690> we<00:13:41.050> have 00:13:41.220 --> 00:13:41.230 align:start position:0% things to worry about like gasps we have 00:13:41.230 --> 00:13:42.960 align:start position:0% things to worry about like gasps we have caustic<00:13:41.710> limits<00:13:42.130> that<00:13:42.430> we<00:13:42.520> have<00:13:42.700> we<00:13:42.850> have 00:13:42.960 --> 00:13:42.970 align:start position:0% caustic limits that we have we have 00:13:42.970 --> 00:13:46.140 align:start position:0% caustic limits that we have we have stack<00:13:43.270> limits<00:13:43.690> so<00:13:44.550> there<00:13:45.550> are<00:13:45.670> a<00:13:45.700> couple<00:13:45.820> of 00:13:46.140 --> 00:13:46.150 align:start position:0% stack limits so there are a couple of 00:13:46.150 --> 00:13:48.030 align:start position:0% stack limits so there are a couple of ways<00:13:46.270> of<00:13:46.390> attacking<00:13:46.690> the<00:13:46.900> problem<00:13:47.290> so<00:13:47.800> one<00:13:48.010> of 00:13:48.030 --> 00:13:48.040 align:start position:0% ways of attacking the problem so one of 00:13:48.040 --> 00:13:49.890 align:start position:0% ways of attacking the problem so one of them<00:13:48.310> is<00:13:48.340> modifying<00:13:49.060> the<00:13:49.180> protocol<00:13:49.600> to<00:13:49.630> try 00:13:49.890 --> 00:13:49.900 align:start position:0% them is modifying the protocol to try 00:13:49.900 --> 00:13:51.720 align:start position:0% them is modifying the protocol to try and<00:13:49.990> reduce<00:13:50.170> the<00:13:50.350> number<00:13:50.440> of<00:13:50.650> those<00:13:50.740> limits<00:13:51.130> so 00:13:51.720 --> 00:13:51.730 align:start position:0% and reduce the number of those limits so 00:13:51.730 --> 00:13:53.700 align:start position:0% and reduce the number of those limits so like<00:13:51.970> I<00:13:52.120> have<00:13:52.330> an<00:13:52.450> EIP<00:13:53.020> out<00:13:53.290> there<00:13:53.500> that 00:13:53.700 --> 00:13:53.710 align:start position:0% like I have an EIP out there that 00:13:53.710 --> 00:13:55.020 align:start position:0% like I have an EIP out there that basically<00:13:53.800> gets<00:13:54.370> rid<00:13:54.550> of<00:13:54.610> the<00:13:54.730> call<00:13:54.910> stack 00:13:55.020 --> 00:13:55.030 align:start position:0% basically gets rid of the call stack 00:13:55.030 --> 00:13:56.850 align:start position:0% basically gets rid of the call stack limited<00:13:55.600> basically<00:13:55.990> replaces<00:13:56.470> it<00:13:56.590> was<00:13:56.710> like<00:13:56.830> a 00:13:56.850 --> 00:13:56.860 align:start position:0% limited basically replaces it was like a 00:13:56.860 --> 00:13:59.160 align:start position:0% limited basically replaces it was like a gas<00:13:57.100> based<00:13:57.400> limitation<00:13:58.000> scheme<00:13:58.270> another 00:13:59.160 --> 00:13:59.170 align:start position:0% gas based limitation scheme another 00:13:59.170 --> 00:14:01.530 align:start position:0% gas based limitation scheme another thing<00:13:59.470> is<00:13:59.680> to<00:13:59.970> basically<00:14:00.970> just<00:14:01.150> like<00:14:01.270> to<00:14:01.390> put 00:14:01.530 --> 00:14:01.540 align:start position:0% thing is to basically just like to put 00:14:01.540 --> 00:14:02.880 align:start position:0% thing is to basically just like to put more<00:14:01.750> checks<00:14:02.080> into<00:14:02.320> the<00:14:02.410> development 00:14:02.880 --> 00:14:02.890 align:start position:0% more checks into the development 00:14:02.890 --> 00:14:05.070 align:start position:0% more checks into the development environment<00:14:02.980> so<00:14:03.940> if<00:14:04.210> for<00:14:04.420> example<00:14:04.480> you<00:14:04.900> have 00:14:05.070 --> 00:14:05.080 align:start position:0% environment so if for example you have 00:14:05.080 --> 00:14:07.290 align:start position:0% environment so if for example you have code<00:14:05.350> where<00:14:05.620> you<00:14:05.860> can't<00:14:06.190> like<00:14:06.910> let's<00:14:07.150> say 00:14:07.290 --> 00:14:07.300 align:start position:0% code where you can't like let's say 00:14:07.300 --> 00:14:09.060 align:start position:0% code where you can't like let's say formally<00:14:07.720> verified<00:14:07.750> that<00:14:08.350> they<00:14:08.440> consume<00:14:08.890> is 00:14:09.060 --> 00:14:09.070 align:start position:0% formally verified that they consume is 00:14:09.070 --> 00:14:10.470 align:start position:0% formally verified that they consume is like<00:14:09.220> less<00:14:09.460> than<00:14:09.490> I've<00:14:09.790> seen<00:14:09.970> a<00:14:10.000> safe<00:14:10.360> amount 00:14:10.470 --> 00:14:10.480 align:start position:0% like less than I've seen a safe amount 00:14:10.480 --> 00:14:11.760 align:start position:0% like less than I've seen a safe amount of<00:14:10.690> gas<00:14:10.870> and<00:14:11.080> that's<00:14:11.230> something<00:14:11.500> that<00:14:11.650> should 00:14:11.760 --> 00:14:11.770 align:start position:0% of gas and that's something that should 00:14:11.770 --> 00:14:13.890 align:start position:0% of gas and that's something that should be<00:14:11.830> more<00:14:12.310> closely<00:14:12.580> and<00:14:13.270> look<00:14:13.420> those<00:14:13.780> are 00:14:13.890 --> 00:14:13.900 align:start position:0% be more closely and look those are 00:14:13.900 --> 00:14:15.600 align:start position:0% be more closely and look those are things<00:14:14.200> where<00:14:14.410> we<00:14:14.560> can't<00:14:14.800> have<00:14:14.950> a<00:14:14.980> tool<00:14:15.220> where 00:14:15.600 --> 00:14:15.610 align:start position:0% things where we can't have a tool where 00:14:15.610 --> 00:14:17.880 align:start position:0% things where we can't have a tool where we<00:14:15.640> can't<00:14:15.910> have<00:14:16.060> supposed<00:14:16.300> to<00:14:16.420> highlight<00:14:16.890> so 00:14:17.880 --> 00:14:17.890 align:start position:0% we can't have supposed to highlight so 00:14:17.890 --> 00:14:20.550 align:start position:0% we can't have supposed to highlight so I'm<00:14:18.160> gonna<00:14:18.310> draw<00:14:18.700> on<00:14:18.760> an<00:14:18.940> analogy<00:14:19.930> to<00:14:20.110> safety 00:14:20.550 --> 00:14:20.560 align:start position:0% I'm gonna draw on an analogy to safety 00:14:20.560 --> 00:14:21.930 align:start position:0% I'm gonna draw on an analogy to safety critical<00:14:20.680> systems<00:14:21.040> here<00:14:21.490> where<00:14:21.670> if<00:14:21.790> you 00:14:21.930 --> 00:14:21.940 align:start position:0% critical systems here where if you 00:14:21.940 --> 00:14:22.980 align:start position:0% critical systems here where if you really<00:14:22.240> want<00:14:22.390> to<00:14:22.480> build<00:14:22.600> something<00:14:22.840> that's 00:14:22.980 --> 00:14:22.990 align:start position:0% really want to build something that's 00:14:22.990 --> 00:14:24.690 align:start position:0% really want to build something that's going<00:14:23.380> in<00:14:23.470> a<00:14:23.530> spacecraft<00:14:24.070> or<00:14:24.250> something<00:14:24.580> like 00:14:24.690 --> 00:14:24.700 align:start position:0% going in a spacecraft or something like 00:14:24.700 --> 00:14:26.460 align:start position:0% going in a spacecraft or something like that<00:14:24.760> you<00:14:25.480> still<00:14:25.690> have<00:14:25.870> to<00:14:25.990> consider<00:14:26.140> the 00:14:26.460 --> 00:14:26.470 align:start position:0% that you still have to consider the 00:14:26.470 --> 00:14:27.570 align:start position:0% that you still have to consider the hardware<00:14:26.830> and<00:14:26.950> you<00:14:27.010> still<00:14:27.220> have<00:14:27.340> to<00:14:27.370> consider 00:14:27.570 --> 00:14:27.580 align:start position:0% hardware and you still have to consider 00:14:27.580 --> 00:14:29.850 align:start position:0% hardware and you still have to consider the<00:14:28.150> assembly<00:14:28.930> representation<00:14:29.650> and<00:14:29.770> you 00:14:29.850 --> 00:14:29.860 align:start position:0% the assembly representation and you 00:14:29.860 --> 00:14:31.770 align:start position:0% the assembly representation and you really<00:14:30.160> have<00:14:30.370> to<00:14:30.580> consider<00:14:30.910> at<00:14:31.360> least<00:14:31.450> the 00:14:31.770 --> 00:14:31.780 align:start position:0% really have to consider at least the 00:14:31.780 --> 00:14:33.860 align:start position:0% really have to consider at least the whole<00:14:31.900> stack<00:14:32.230> so<00:14:32.680> I<00:14:32.980> don't<00:14:33.160> think<00:14:33.340> you'll<00:14:33.460> I 00:14:33.860 --> 00:14:33.870 align:start position:0% whole stack so I don't think you'll I 00:14:33.870 --> 00:14:36.720 align:start position:0% whole stack so I don't think you'll I think<00:14:34.870> maybe<00:14:35.290> eventually<00:14:35.590> once<00:14:36.160> we<00:14:36.340> really 00:14:36.720 --> 00:14:36.730 align:start position:0% think maybe eventually once we really 00:14:36.730 --> 00:14:38.070 align:start position:0% think maybe eventually once we really develop<00:14:37.060> these<00:14:37.180> tools<00:14:37.390> you'll<00:14:37.630> be<00:14:37.750> able<00:14:37.840> to 00:14:38.070 --> 00:14:38.080 align:start position:0% develop these tools you'll be able to 00:14:38.080 --> 00:14:40.050 align:start position:0% develop these tools you'll be able to have<00:14:38.530> some<00:14:38.980> sort<00:14:39.220> of<00:14:39.280> ignorance<00:14:39.940> and 00:14:40.050 --> 00:14:40.060 align:start position:0% have some sort of ignorance and 00:14:40.060 --> 00:14:41.940 align:start position:0% have some sort of ignorance and abstraction<00:14:40.600> of<00:14:40.660> those<00:14:40.810> lower<00:14:41.050> levels<00:14:41.410> but<00:14:41.710> I 00:14:41.940 --> 00:14:41.950 align:start position:0% abstraction of those lower levels but I 00:14:41.950 --> 00:14:45.360 align:start position:0% abstraction of those lower levels but I think<00:14:42.520> it's<00:14:42.640> gonna<00:14:42.730> be<00:14:42.910> years<00:14:43.210> personally<00:14:44.370> do 00:14:45.360 --> 00:14:45.370 align:start position:0% think it's gonna be years personally do 00:14:45.370 --> 00:14:47.430 align:start position:0% think it's gonna be years personally do you<00:14:45.460> think<00:14:45.670> that<00:14:45.850> the<00:14:46.270> development<00:14:47.080> of<00:14:47.200> new 00:14:47.430 --> 00:14:47.440 align:start position:0% you think that the development of new 00:14:47.440 --> 00:14:50.190 align:start position:0% you think that the development of new domain-specific<00:14:48.340> languages<00:14:49.270> for<00:14:49.690> certain 00:14:50.190 --> 00:14:50.200 align:start position:0% domain-specific languages for certain 00:14:50.200 --> 00:14:50.840 align:start position:0% domain-specific languages for certain types<00:14:50.380> of 00:14:50.840 --> 00:14:50.850 align:start position:0% types of 00:14:50.850 --> 00:14:54.409 align:start position:0% types of or<00:14:51.089> contracts<00:14:51.720> in<00:14:51.809> general<00:14:52.199> would<00:14:53.069> aid<00:14:53.369> do<00:14:54.329> you 00:14:54.409 --> 00:14:54.419 align:start position:0% or contracts in general would aid do you 00:14:54.419 --> 00:14:56.059 align:start position:0% or contracts in general would aid do you think<00:14:54.569> that's<00:14:54.749> coming<00:14:55.289> that<00:14:55.679> we're<00:14:55.859> having 00:14:56.059 --> 00:14:56.069 align:start position:0% think that's coming that we're having 00:14:56.069 --> 00:14:58.069 align:start position:0% think that's coming that we're having more<00:14:56.189> languages<00:14:56.699> because<00:14:57.479> earlier<00:14:57.839> we<00:14:57.989> had 00:14:58.069 --> 00:14:58.079 align:start position:0% more languages because earlier we had 00:14:58.079 --> 00:15:00.199 align:start position:0% more languages because earlier we had there<00:14:58.499> was<00:14:58.589> development<00:14:58.799> both<00:14:59.579> in<00:14:59.759> solidity 00:15:00.199 --> 00:15:00.209 align:start position:0% there was development both in solidity 00:15:00.209 --> 00:15:02.900 align:start position:0% there was development both in solidity and<00:15:00.299> serpent<00:15:00.839> and<00:15:01.019> for<00:15:01.410> that<00:15:01.470> part<00:15:01.799> LLL<00:15:02.189> now<00:15:02.850> it 00:15:02.900 --> 00:15:02.910 align:start position:0% and serpent and for that part LLL now it 00:15:02.910 --> 00:15:05.239 align:start position:0% and serpent and for that part LLL now it seems<00:15:03.209> that<00:15:03.299> solidity<00:15:03.869> is<00:15:04.019> the<00:15:04.379> leading<00:15:05.009> the 00:15:05.239 --> 00:15:05.249 align:start position:0% seems that solidity is the leading the 00:15:05.249 --> 00:15:09.019 align:start position:0% seems that solidity is the leading the race<00:15:05.429> and<00:15:06.410> is<00:15:07.410> almost<00:15:07.739> the<00:15:07.979> canonical 00:15:09.019 --> 00:15:09.029 align:start position:0% race and is almost the canonical 00:15:09.029 --> 00:15:11.719 align:start position:0% race and is almost the canonical contract<00:15:09.660> development<00:15:10.049> language<00:15:10.579> will<00:15:11.579> there 00:15:11.719 --> 00:15:11.729 align:start position:0% contract development language will there 00:15:11.729 --> 00:15:14.749 align:start position:0% contract development language will there be<00:15:11.879> more<00:15:12.529> well<00:15:13.529> I<00:15:13.979> can<00:15:14.279> speak<00:15:14.399> from<00:15:14.669> my 00:15:14.749 --> 00:15:14.759 align:start position:0% be more well I can speak from my 00:15:14.759 --> 00:15:16.759 align:start position:0% be more well I can speak from my perspective<00:15:15.059> that<00:15:15.479> I<00:15:15.509> I<00:15:15.899> hope<00:15:16.379> there<00:15:16.619> will<00:15:16.709> be 00:15:16.759 --> 00:15:16.769 align:start position:0% perspective that I I hope there will be 00:15:16.769 --> 00:15:19.519 align:start position:0% perspective that I I hope there will be more<00:15:17.039> because<00:15:17.369> the<00:15:17.729> language<00:15:18.269> a<00:15:18.569> language 00:15:19.519 --> 00:15:19.529 align:start position:0% more because the language a language 00:15:19.529 --> 00:15:21.169 align:start position:0% more because the language a language like<00:15:19.679> solidity<00:15:20.069> that's<00:15:20.729> fairly<00:15:20.939> high-level 00:15:21.169 --> 00:15:21.179 align:start position:0% like solidity that's fairly high-level 00:15:21.179 --> 00:15:23.509 align:start position:0% like solidity that's fairly high-level is<00:15:21.660> our<00:15:21.989> main<00:15:22.229> abstraction<00:15:22.859> layer<00:15:23.009> over<00:15:23.489> the 00:15:23.509 --> 00:15:23.519 align:start position:0% is our main abstraction layer over the 00:15:23.519 --> 00:15:28.340 align:start position:0% is our main abstraction layer over the EVM<00:15:24.119> so<00:15:24.629> as<00:15:24.839> developers<00:15:26.749> we<00:15:27.749> spend<00:15:28.019> more<00:15:28.169> time 00:15:28.340 --> 00:15:28.350 align:start position:0% EVM so as developers we spend more time 00:15:28.350 --> 00:15:31.039 align:start position:0% EVM so as developers we spend more time writing<00:15:28.859> smart<00:15:29.279> contracts<00:15:29.729> in<00:15:29.910> that<00:15:30.359> that 00:15:31.039 --> 00:15:31.049 align:start position:0% writing smart contracts in that that 00:15:31.049 --> 00:15:33.739 align:start position:0% writing smart contracts in that that abstraction<00:15:31.470> layer<00:15:31.799> and<00:15:32.100> so<00:15:32.449> to<00:15:33.449> the<00:15:33.539> extent 00:15:33.739 --> 00:15:33.749 align:start position:0% abstraction layer and so to the extent 00:15:33.749 --> 00:15:35.389 align:start position:0% abstraction layer and so to the extent that<00:15:33.929> the<00:15:34.109> abstraction<00:15:34.619> later<00:15:34.829> layer 00:15:35.389 --> 00:15:35.399 align:start position:0% that the abstraction later layer 00:15:35.399 --> 00:15:38.119 align:start position:0% that the abstraction later layer supports<00:15:35.970> good<00:15:36.269> security<00:15:36.899> practices<00:15:37.470> that's 00:15:38.119 --> 00:15:38.129 align:start position:0% supports good security practices that's 00:15:38.129 --> 00:15:39.499 align:start position:0% supports good security practices that's going<00:15:38.399> to<00:15:38.459> help<00:15:38.639> the<00:15:38.729> whole<00:15:38.850> community<00:15:38.879> right 00:15:39.499 --> 00:15:39.509 align:start position:0% going to help the whole community right 00:15:39.509 --> 00:15:43.039 align:start position:0% going to help the whole community right more<00:15:39.720> secure<00:15:40.019> contracts<00:15:40.499> and<00:15:41.299> right<00:15:42.299> now<00:15:42.629> I 00:15:43.039 --> 00:15:43.049 align:start position:0% more secure contracts and right now I 00:15:43.049 --> 00:15:45.349 align:start position:0% more secure contracts and right now I think<00:15:43.169> that<00:15:43.439> the<00:15:44.160> the<00:15:44.639> convergence<00:15:45.209> on 00:15:45.349 --> 00:15:45.359 align:start position:0% think that the the convergence on 00:15:45.359 --> 00:15:47.329 align:start position:0% think that the the convergence on solidity<00:15:45.749> is<00:15:45.839> helpful<00:15:46.410> to<00:15:46.439> create<00:15:46.769> stability 00:15:47.329 --> 00:15:47.339 align:start position:0% solidity is helpful to create stability 00:15:47.339 --> 00:15:48.979 align:start position:0% solidity is helpful to create stability in<00:15:47.399> the<00:15:47.489> community<00:15:47.910> but<00:15:48.359> we<00:15:48.479> really<00:15:48.839> do<00:15:48.959> need 00:15:48.979 --> 00:15:48.989 align:start position:0% in the community but we really do need 00:15:48.989 --> 00:15:51.289 align:start position:0% in the community but we really do need other<00:15:49.350> languages<00:15:49.949> and<00:15:50.160> other<00:15:50.309> abstraction 00:15:51.289 --> 00:15:51.299 align:start position:0% other languages and other abstraction 00:15:51.299 --> 00:15:54.079 align:start position:0% other languages and other abstraction layers<00:15:51.829> not<00:15:52.829> to<00:15:53.009> necessarily<00:15:53.399> find<00:15:53.729> the 00:15:54.079 --> 00:15:54.089 align:start position:0% layers not to necessarily find the 00:15:54.089 --> 00:15:58.129 align:start position:0% layers not to necessarily find the ultimate<00:15:54.749> one<00:15:55.019> but<00:15:55.379> too<00:15:56.179> similar<00:15:57.179> to<00:15:57.329> the<00:15:57.539> to 00:15:58.129 --> 00:15:58.139 align:start position:0% ultimate one but too similar to the to 00:15:58.139 --> 00:16:00.169 align:start position:0% ultimate one but too similar to the to the<00:15:58.259> web<00:15:58.409> community<00:15:58.679> to<00:15:59.429> have<00:15:59.939> more 00:16:00.169 --> 00:16:00.179 align:start position:0% the web community to have more 00:16:00.179 --> 00:16:01.879 align:start position:0% the web community to have more experimentation<00:16:00.779> and<00:16:01.109> have<00:16:01.199> the<00:16:01.289> ecosystem 00:16:01.879 --> 00:16:01.889 align:start position:0% experimentation and have the ecosystem 00:16:01.889 --> 00:16:03.710 align:start position:0% experimentation and have the ecosystem naturally<00:16:02.369> evolved<00:16:02.789> these<00:16:03.329> different 00:16:03.710 --> 00:16:03.720 align:start position:0% naturally evolved these different 00:16:03.720 --> 00:16:06.559 align:start position:0% naturally evolved these different abstraction<00:16:04.199> layers<00:16:04.429> so<00:16:05.429> yeah<00:16:05.699> I<00:16:05.909> personally 00:16:06.559 --> 00:16:06.569 align:start position:0% abstraction layers so yeah I personally 00:16:06.569 --> 00:16:08.869 align:start position:0% abstraction layers so yeah I personally I<00:16:06.600> would<00:16:06.779> love<00:16:06.929> to<00:16:07.079> see<00:16:07.259> other<00:16:07.799> languages<00:16:08.549> and 00:16:08.869 --> 00:16:08.879 align:start position:0% I would love to see other languages and 00:16:08.879 --> 00:16:12.259 align:start position:0% I would love to see other languages and you<00:16:09.869> know<00:16:09.989> the<00:16:10.199> EVM<00:16:10.829> C<00:16:11.100> and<00:16:11.369> JIT<00:16:11.639> work<00:16:11.879> that<00:16:12.149> we 00:16:12.259 --> 00:16:12.269 align:start position:0% you know the EVM C and JIT work that we 00:16:12.269 --> 00:16:13.849 align:start position:0% you know the EVM C and JIT work that we heard<00:16:12.419> about<00:16:12.479> yesterday<00:16:12.779> is<00:16:13.139> really<00:16:13.379> exciting 00:16:13.849 --> 00:16:13.859 align:start position:0% heard about yesterday is really exciting 00:16:13.859 --> 00:16:15.679 align:start position:0% heard about yesterday is really exciting in<00:16:13.949> order<00:16:14.129> to<00:16:14.220> open<00:16:14.549> up<00:16:14.669> that<00:16:14.939> the<00:16:15.419> the 00:16:15.679 --> 00:16:15.689 align:start position:0% in order to open up that the the 00:16:15.689 --> 00:16:18.019 align:start position:0% in order to open up that the the platform<00:16:16.220> so<00:16:17.220> I'm<00:16:17.309> gonna<00:16:17.429> play<00:16:17.639> a<00:16:17.669> little<00:16:17.819> bit 00:16:18.019 --> 00:16:18.029 align:start position:0% platform so I'm gonna play a little bit 00:16:18.029 --> 00:16:19.639 align:start position:0% platform so I'm gonna play a little bit of<00:16:18.149> devil's<00:16:18.509> advocate<00:16:18.929> on<00:16:19.049> this<00:16:19.289> I<00:16:19.409> don't 00:16:19.639 --> 00:16:19.649 align:start position:0% of devil's advocate on this I don't 00:16:19.649 --> 00:16:21.139 align:start position:0% of devil's advocate on this I don't think<00:16:19.709> good<00:16:20.009> languages<00:16:20.489> can<00:16:20.669> solve<00:16:20.909> bad 00:16:21.139 --> 00:16:21.149 align:start position:0% think good languages can solve bad 00:16:21.149 --> 00:16:23.479 align:start position:0% think good languages can solve bad programmers<00:16:21.809> and<00:16:22.139> I<00:16:22.379> think<00:16:22.619> that<00:16:22.829> as<00:16:23.009> long<00:16:23.279> as 00:16:23.479 --> 00:16:23.489 align:start position:0% programmers and I think that as long as 00:16:23.489 --> 00:16:25.579 align:start position:0% programmers and I think that as long as you're<00:16:23.759> having<00:16:24.509> a<00:16:24.569> turing-complete<00:16:24.869> language 00:16:25.579 --> 00:16:25.589 align:start position:0% you're having a turing-complete language 00:16:25.589 --> 00:16:27.229 align:start position:0% you're having a turing-complete language that<00:16:25.829> has<00:16:25.979> expressiveness<00:16:26.609> you're<00:16:26.879> gonna<00:16:27.029> run 00:16:27.229 --> 00:16:27.239 align:start position:0% that has expressiveness you're gonna run 00:16:27.239 --> 00:16:28.939 align:start position:0% that has expressiveness you're gonna run into<00:16:27.269> problems<00:16:27.929> of<00:16:28.169> some<00:16:28.350> sort<00:16:28.649> with<00:16:28.859> the 00:16:28.939 --> 00:16:28.949 align:start position:0% into problems of some sort with the 00:16:28.949 --> 00:16:32.869 align:start position:0% into problems of some sort with the language<00:16:29.509> and<00:16:30.509> I<00:16:31.019> do<00:16:31.159> think<00:16:32.159> that<00:16:32.339> having<00:16:32.579> a 00:16:32.869 --> 00:16:32.879 align:start position:0% language and I do think that having a 00:16:32.879 --> 00:16:35.090 align:start position:0% language and I do think that having a small<00:16:33.239> number<00:16:33.509> of<00:16:33.659> diverse<00:16:34.229> languages<00:16:34.889> is 00:16:35.090 --> 00:16:35.100 align:start position:0% small number of diverse languages is 00:16:35.100 --> 00:16:36.769 align:start position:0% small number of diverse languages is better<00:16:35.369> than<00:16:35.579> having<00:16:35.909> a<00:16:35.999> very<00:16:36.029> large<00:16:36.389> number 00:16:36.769 --> 00:16:36.779 align:start position:0% better than having a very large number 00:16:36.779 --> 00:16:38.299 align:start position:0% better than having a very large number of<00:16:36.809> languages<00:16:37.169> because<00:16:37.649> then<00:16:37.829> you<00:16:37.919> have<00:16:37.949> more 00:16:38.299 --> 00:16:38.309 align:start position:0% of languages because then you have more 00:16:38.309 --> 00:16:39.349 align:start position:0% of languages because then you have more people<00:16:38.489> in<00:16:38.639> the<00:16:38.759> community<00:16:39.119> who<00:16:39.239> can 00:16:39.349 --> 00:16:39.359 align:start position:0% people in the community who can 00:16:39.359 --> 00:16:41.299 align:start position:0% people in the community who can understand<00:16:39.959> the<00:16:40.259> language<00:16:40.350> really<00:16:40.739> well<00:16:41.009> and 00:16:41.299 --> 00:16:41.309 align:start position:0% understand the language really well and 00:16:41.309 --> 00:16:44.659 align:start position:0% understand the language really well and sort<00:16:41.519> of<00:16:41.609> audit<00:16:41.970> your<00:16:42.029> code<00:16:42.299> so<00:16:42.979> for<00:16:43.979> the<00:16:44.549> web 00:16:44.659 --> 00:16:44.669 align:start position:0% sort of audit your code so for the web 00:16:44.669 --> 00:16:46.609 align:start position:0% sort of audit your code so for the web it's<00:16:44.909> a<00:16:44.999> great<00:16:45.179> example<00:16:45.299> you<00:16:46.229> mostly<00:16:46.529> see 00:16:46.609 --> 00:16:46.619 align:start position:0% it's a great example you mostly see 00:16:46.619 --> 00:16:48.349 align:start position:0% it's a great example you mostly see JavaScript<00:16:47.309> really<00:16:47.519> in<00:16:47.699> practice<00:16:47.879> for 00:16:48.349 --> 00:16:48.359 align:start position:0% JavaScript really in practice for 00:16:48.359 --> 00:16:51.259 align:start position:0% JavaScript really in practice for client-side<00:16:48.749> computation<00:16:49.589> and<00:16:50.149> even<00:16:51.149> though 00:16:51.259 --> 00:16:51.269 align:start position:0% client-side computation and even though 00:16:51.269 --> 00:16:53.419 align:start position:0% client-side computation and even though it's<00:16:51.419> not<00:16:51.539> the<00:16:51.720> greatest<00:16:51.899> language<00:16:52.409> people<00:16:53.279> do 00:16:53.419 --> 00:16:53.429 align:start position:0% it's not the greatest language people do 00:16:53.429 --> 00:16:54.499 align:start position:0% it's not the greatest language people do understand<00:16:53.879> it<00:16:54.029> and<00:16:54.149> they<00:16:54.209> sort<00:16:54.389> of 00:16:54.499 --> 00:16:54.509 align:start position:0% understand it and they sort of 00:16:54.509 --> 00:16:56.269 align:start position:0% understand it and they sort of understand<00:16:54.959> the<00:16:55.079> common<00:16:55.289> anti<00:16:55.679> patterns<00:16:56.069> and 00:16:56.269 --> 00:16:56.279 align:start position:0% understand the common anti patterns and 00:16:56.279 --> 00:16:57.919 align:start position:0% understand the common anti patterns and that<00:16:56.369> helps<00:16:56.729> them<00:16:56.909> write<00:16:57.059> secure<00:16:57.389> code<00:16:57.449> in 00:16:57.919 --> 00:16:57.929 align:start position:0% that helps them write secure code in 00:16:57.929 --> 00:17:01.159 align:start position:0% that helps them write secure code in many<00:16:58.169> cases<00:16:59.269> to<00:17:00.269> use<00:17:00.389> your<00:17:00.600> own<00:17:00.720> example 00:17:01.159 --> 00:17:01.169 align:start position:0% many cases to use your own example 00:17:01.169 --> 00:17:03.319 align:start position:0% many cases to use your own example however<00:17:01.350> the<00:17:02.249> transpilers 00:17:03.319 --> 00:17:03.329 align:start position:0% however the transpilers 00:17:03.329 --> 00:17:04.699 align:start position:0% however the transpilers that<00:17:03.449> have<00:17:03.540> taken<00:17:03.720> off<00:17:03.959> in<00:17:04.110> the<00:17:04.169> last<00:17:04.350> five<00:17:04.559> to 00:17:04.699 --> 00:17:04.709 align:start position:0% that have taken off in the last five to 00:17:04.709 --> 00:17:05.899 align:start position:0% that have taken off in the last five to ten<00:17:04.890> years<00:17:05.069> in<00:17:05.189> the<00:17:05.279> JavaScript<00:17:05.760> community 00:17:05.899 --> 00:17:05.909 align:start position:0% ten years in the JavaScript community 00:17:05.909 --> 00:17:08.539 align:start position:0% ten years in the JavaScript community have<00:17:06.269> allowed<00:17:06.569> the<00:17:06.809> community<00:17:07.230> to<00:17:07.709> test<00:17:08.010> es6 00:17:08.539 --> 00:17:08.549 align:start position:0% have allowed the community to test es6 00:17:08.549 --> 00:17:10.850 align:start position:0% have allowed the community to test es6 es<00:17:08.939> seven<00:17:09.240> features<00:17:09.569> before<00:17:10.350> they're<00:17:10.529> part<00:17:10.740> of 00:17:10.850 --> 00:17:10.860 align:start position:0% es seven features before they're part of 00:17:10.860 --> 00:17:15.279 align:start position:0% es seven features before they're part of the<00:17:11.309> core<00:17:11.579> so<00:17:12.029> that's<00:17:12.480> like<00:17:12.689> this<00:17:13.260> bottom<00:17:13.799> up 00:17:15.279 --> 00:17:15.289 align:start position:0% the core so that's like this bottom up 00:17:15.289 --> 00:17:17.449 align:start position:0% the core so that's like this bottom up contribution<00:17:16.289> to<00:17:16.649> the<00:17:16.829> language<00:17:17.159> and 00:17:17.449 --> 00:17:17.459 align:start position:0% contribution to the language and 00:17:17.459 --> 00:17:20.360 align:start position:0% contribution to the language and evolution<00:17:18.360> so<00:17:18.539> it's<00:17:18.659> not<00:17:18.779> just<00:17:18.890> the<00:17:19.890> tc39 00:17:20.360 --> 00:17:20.370 align:start position:0% evolution so it's not just the tc39 00:17:20.370 --> 00:17:22.759 align:start position:0% evolution so it's not just the tc39 committee<00:17:20.399> that<00:17:21.269> is<00:17:21.480> bringing<00:17:22.289> the<00:17:22.500> language 00:17:22.759 --> 00:17:22.769 align:start position:0% committee that is bringing the language 00:17:22.769 --> 00:17:24.110 align:start position:0% committee that is bringing the language changes<00:17:23.130> from<00:17:23.250> the<00:17:23.399> top<00:17:23.579> down 00:17:24.110 --> 00:17:24.120 align:start position:0% changes from the top down 00:17:24.120 --> 00:17:26.149 align:start position:0% changes from the top down they're<00:17:24.480> certainly<00:17:24.750> helping<00:17:25.679> to<00:17:25.799> add<00:17:25.919> them<00:17:26.130> to 00:17:26.149 --> 00:17:26.159 align:start position:0% they're certainly helping to add them to 00:17:26.159 --> 00:17:28.130 align:start position:0% they're certainly helping to add them to the<00:17:26.399> language<00:17:26.789> but<00:17:27.209> there's<00:17:27.360> this<00:17:27.510> bottom-up 00:17:28.130 --> 00:17:28.140 align:start position:0% the language but there's this bottom-up 00:17:28.140 --> 00:17:30.740 align:start position:0% the language but there's this bottom-up effort<00:17:29.010> from<00:17:29.279> community<00:17:30.210> members<00:17:30.539> and 00:17:30.740 --> 00:17:30.750 align:start position:0% effort from community members and 00:17:30.750 --> 00:17:32.840 align:start position:0% effort from community members and transpilers<00:17:31.320> and<00:17:31.529> so<00:17:31.590> it<00:17:31.740> just<00:17:32.190> helps<00:17:32.309> inform 00:17:32.840 --> 00:17:32.850 align:start position:0% transpilers and so it just helps inform 00:17:32.850 --> 00:17:34.909 align:start position:0% transpilers and so it just helps inform it<00:17:32.970> from<00:17:33.149> both<00:17:33.299> sides<00:17:33.570> so<00:17:33.929> I<00:17:34.289> would<00:17:34.559> agree<00:17:34.740> with 00:17:34.909 --> 00:17:34.919 align:start position:0% it from both sides so I would agree with 00:17:34.919 --> 00:17:37.820 align:start position:0% it from both sides so I would agree with you<00:17:35.039> that<00:17:35.070> I'm<00:17:36.000> having<00:17:36.480> the<00:17:37.019> kind<00:17:37.470> of<00:17:37.559> core 00:17:37.820 --> 00:17:37.830 align:start position:0% you that I'm having the kind of core 00:17:37.830 --> 00:17:41.509 align:start position:0% you that I'm having the kind of core language<00:17:38.100> offerings<00:17:38.760> and<00:17:40.399> having<00:17:41.399> people 00:17:41.509 --> 00:17:41.519 align:start position:0% language offerings and having people 00:17:41.519 --> 00:17:43.879 align:start position:0% language offerings and having people develop<00:17:42.120> expertise<00:17:42.630> in<00:17:42.809> that<00:17:42.840> language<00:17:43.380> is<00:17:43.559> is 00:17:43.879 --> 00:17:43.889 align:start position:0% develop expertise in that language is is 00:17:43.889 --> 00:17:46.700 align:start position:0% develop expertise in that language is is the<00:17:44.190> primary<00:17:44.429> concern<00:17:44.789> but<00:17:45.480> then<00:17:45.720> if<00:17:46.110> you<00:17:46.260> take 00:17:46.700 --> 00:17:46.710 align:start position:0% the primary concern but then if you take 00:17:46.710 --> 00:17:48.289 align:start position:0% the primary concern but then if you take a<00:17:46.769> step<00:17:46.980> back<00:17:47.159> and<00:17:47.309> look<00:17:47.460> at<00:17:47.549> the<00:17:47.639> ecosystem<00:17:48.210> as 00:17:48.289 --> 00:17:48.299 align:start position:0% a step back and look at the ecosystem as 00:17:48.299 --> 00:17:49.669 align:start position:0% a step back and look at the ecosystem as a<00:17:48.330> whole<00:17:48.419> and<00:17:48.870> the<00:17:48.929> evolution<00:17:49.440> of<00:17:49.529> the 00:17:49.669 --> 00:17:49.679 align:start position:0% a whole and the evolution of the 00:17:49.679 --> 00:17:51.350 align:start position:0% a whole and the evolution of the patterns<00:17:50.039> and<00:17:50.220> abstractions<00:17:50.760> and<00:17:50.909> languages 00:17:51.350 --> 00:17:51.360 align:start position:0% patterns and abstractions and languages 00:17:51.360 --> 00:17:54.110 align:start position:0% patterns and abstractions and languages they're<00:17:51.690> available<00:17:52.130> having<00:17:53.130> multiple 00:17:54.110 --> 00:17:54.120 align:start position:0% they're available having multiple 00:17:54.120 --> 00:17:57.440 align:start position:0% they're available having multiple sources<00:17:54.510> of<00:17:54.919> experimentation<00:17:55.919> and<00:17:56.450> evolution 00:17:57.440 --> 00:17:57.450 align:start position:0% sources of experimentation and evolution 00:17:57.450 --> 00:18:04.250 align:start position:0% sources of experimentation and evolution I<00:17:57.570> think<00:17:57.750> really<00:17:57.929> helps<00:17:59.240> totally<00:18:00.240> agree<00:18:03.260> all 00:18:04.250 --> 00:18:04.260 align:start position:0% I think really helps totally agree all 00:18:04.260 --> 00:18:06.620 align:start position:0% I think really helps totally agree all right<00:18:04.440> the<00:18:04.590> topic<00:18:04.860> one<00:18:05.070> last<00:18:05.309> question<00:18:05.570> do<00:18:06.570> you 00:18:06.620 --> 00:18:06.630 align:start position:0% right the topic one last question do you 00:18:06.630 --> 00:18:09.740 align:start position:0% right the topic one last question do you think<00:18:06.840> there<00:18:06.960> are<00:18:06.990> any<00:18:07.110> particular<00:18:08.750> features 00:18:09.740 --> 00:18:09.750 align:start position:0% think there are any particular features 00:18:09.750 --> 00:18:13.580 align:start position:0% think there are any particular features of<00:18:09.779> the<00:18:10.049> EVM<00:18:10.500> or<00:18:10.830> new<00:18:11.370> uploads<00:18:11.909> or<00:18:12.559> changes<00:18:13.559> to 00:18:13.580 --> 00:18:13.590 align:start position:0% of the EVM or new uploads or changes to 00:18:13.590 --> 00:18:16.310 align:start position:0% of the EVM or new uploads or changes to the<00:18:13.799> EVM<00:18:14.549> which<00:18:14.850> could<00:18:15.059> be<00:18:15.149> made<00:18:15.360> which<00:18:16.019> could 00:18:16.310 --> 00:18:16.320 align:start position:0% the EVM which could be made which could 00:18:16.320 --> 00:18:21.950 align:start position:0% the EVM which could be made which could improve<00:18:16.710> the<00:18:17.159> security<00:18:18.019> in<00:18:19.019> contracts<00:18:20.960> one 00:18:21.950 --> 00:18:21.960 align:start position:0% improve the security in contracts one 00:18:21.960 --> 00:18:23.480 align:start position:0% improve the security in contracts one thing<00:18:22.169> that<00:18:22.289> I<00:18:22.350> really<00:18:22.740> don't<00:18:22.919> like<00:18:23.070> about<00:18:23.130> the 00:18:23.480 --> 00:18:23.490 align:start position:0% thing that I really don't like about the 00:18:23.490 --> 00:18:25.370 align:start position:0% thing that I really don't like about the EVM<00:18:23.850> is<00:18:24.120> the<00:18:24.299> lack<00:18:24.480> of<00:18:24.510> distinction<00:18:25.200> between 00:18:25.370 --> 00:18:25.380 align:start position:0% EVM is the lack of distinction between 00:18:25.380 --> 00:18:28.909 align:start position:0% EVM is the lack of distinction between calling<00:18:26.340> a<00:18:26.519> function<00:18:26.730> sending<00:18:27.480> money<00:18:27.919> and 00:18:28.909 --> 00:18:28.919 align:start position:0% calling a function sending money and 00:18:28.919 --> 00:18:30.620 align:start position:0% calling a function sending money and sending<00:18:29.490> a<00:18:29.580> message<00:18:29.610> I<00:18:30.210> think<00:18:30.480> there<00:18:30.600> should 00:18:30.620 --> 00:18:30.630 align:start position:0% sending a message I think there should 00:18:30.630 --> 00:18:32.930 align:start position:0% sending a message I think there should be<00:18:30.960> some<00:18:31.289> ways<00:18:31.470> to<00:18:31.710> access<00:18:31.860> more<00:18:32.370> restrictive 00:18:32.930 --> 00:18:32.940 align:start position:0% be some ways to access more restrictive 00:18:32.940 --> 00:18:34.879 align:start position:0% be some ways to access more restrictive subsets<00:18:33.450> of<00:18:33.659> this<00:18:33.899> functionality<00:18:34.350> where 00:18:34.879 --> 00:18:34.889 align:start position:0% subsets of this functionality where 00:18:34.889 --> 00:18:36.610 align:start position:0% subsets of this functionality where maybe<00:18:35.100> you<00:18:35.279> only<00:18:35.460> want<00:18:35.610> to<00:18:35.820> send<00:18:36.000> money<00:18:36.149> and 00:18:36.610 --> 00:18:36.620 align:start position:0% maybe you only want to send money and 00:18:36.620 --> 00:18:38.960 align:start position:0% maybe you only want to send money and allow<00:18:37.620> other<00:18:38.130> contracts<00:18:38.700> that<00:18:38.850> you're 00:18:38.960 --> 00:18:38.970 align:start position:0% allow other contracts that you're 00:18:38.970 --> 00:18:41.029 align:start position:0% allow other contracts that you're sending<00:18:39.240> money<00:18:39.360> to<00:18:39.630> to<00:18:39.929> perform<00:18:40.230> only<00:18:40.590> limited 00:18:41.029 --> 00:18:41.039 align:start position:0% sending money to to perform only limited 00:18:41.039 --> 00:18:44.539 align:start position:0% sending money to to perform only limited operations<00:18:41.690> otherwise<00:18:42.690> fail<00:18:43.049> so<00:18:43.950> I<00:18:44.309> think 00:18:44.539 --> 00:18:44.549 align:start position:0% operations otherwise fail so I think 00:18:44.549 --> 00:18:47.000 align:start position:0% operations otherwise fail so I think maybe<00:18:44.820> that<00:18:44.970> that<00:18:45.620> architectural<00:18:46.620> concern 00:18:47.000 --> 00:18:47.010 align:start position:0% maybe that that architectural concern 00:18:47.010 --> 00:18:49.190 align:start position:0% maybe that that architectural concern could<00:18:47.399> use<00:18:47.580> some<00:18:47.760> work<00:18:47.940> but<00:18:48.269> in<00:18:48.480> general<00:18:48.899> I<00:18:49.139> I 00:18:49.190 --> 00:18:49.200 align:start position:0% could use some work but in general I I 00:18:49.200 --> 00:18:51.350 align:start position:0% could use some work but in general I I don't<00:18:49.710> think<00:18:49.919> so<00:18:50.070> I<00:18:50.100> think<00:18:50.250> there's<00:18:51.090> a<00:18:51.179> lot 00:18:51.350 --> 00:18:51.360 align:start position:0% don't think so I think there's a lot 00:18:51.360 --> 00:18:52.610 align:start position:0% don't think so I think there's a lot more<00:18:51.389> work<00:18:51.750> to<00:18:51.960> be<00:18:51.990> done<00:18:52.110> at<00:18:52.350> the<00:18:52.440> higher 00:18:52.610 --> 00:18:52.620 align:start position:0% more work to be done at the higher 00:18:52.620 --> 00:18:55.730 align:start position:0% more work to be done at the higher levels<00:18:53.100> than<00:18:53.309> at<00:18:53.490> the<00:18:53.580> EVM<00:18:53.909> right<00:18:54.240> now<00:18:54.389> I<00:18:54.740> have 00:18:55.730 --> 00:18:55.740 align:start position:0% levels than at the EVM right now I have 00:18:55.740 --> 00:18:57.649 align:start position:0% levels than at the EVM right now I have a<00:18:55.769> few<00:18:56.010> specific<00:18:56.460> proposals<00:18:57.000> or<00:18:57.210> like<00:18:57.330> one<00:18:57.539> of 00:18:57.649 --> 00:18:57.659 align:start position:0% a few specific proposals or like one of 00:18:57.659 --> 00:19:00.110 align:start position:0% a few specific proposals or like one of them<00:18:57.840> is<00:18:57.870> look<00:18:58.139> as<00:18:58.380> as<00:18:59.100> I<00:18:59.309> mentioned<00:18:59.669> replacing 00:19:00.110 --> 00:19:00.120 align:start position:0% them is look as as I mentioned replacing 00:19:00.120 --> 00:19:02.210 align:start position:0% them is look as as I mentioned replacing the<00:19:00.269> cost<00:19:00.450> the<00:19:00.690> cost<00:19:00.870> at<00:19:01.139> replacing<00:19:01.740> the<00:19:02.039> cost 00:19:02.210 --> 00:19:02.220 align:start position:0% the cost the cost at replacing the cost 00:19:02.220 --> 00:19:04.570 align:start position:0% the cost the cost at replacing the cost element<00:19:02.760> was<00:19:02.850> with<00:19:03.179> gas<00:19:03.389> one<00:19:03.779> of<00:19:03.809> them<00:19:04.080> is<00:19:04.230> the 00:19:04.570 --> 00:19:04.580 align:start position:0% element was with gas one of them is the 00:19:04.580 --> 00:19:07.669 align:start position:0% element was with gas one of them is the call<00:19:05.580> static<00:19:06.000> proposal<00:19:06.600> where<00:19:06.779> he<00:19:06.840> can<00:19:07.049> make<00:19:07.649> a 00:19:07.669 --> 00:19:07.679 align:start position:0% call static proposal where he can make a 00:19:07.679 --> 00:19:10.669 align:start position:0% call static proposal where he can make a call<00:19:08.070> so<00:19:08.399> that<00:19:08.580> which<00:19:08.730> can<00:19:09.000> record<00:19:09.840> as<00:19:10.350> much<00:19:10.500> as 00:19:10.669 --> 00:19:10.679 align:start position:0% call so that which can record as much as 00:19:10.679 --> 00:19:11.510 align:start position:0% call so that which can record as much as it<00:19:10.799> needs<00:19:10.830> to<00:19:11.100> Anam 00:19:11.510 --> 00:19:11.520 align:start position:0% it needs to Anam 00:19:11.520 --> 00:19:13.610 align:start position:0% it needs to Anam any<00:19:11.760> state<00:19:12.000> changes<00:19:12.480> and<00:19:12.660> a<00:19:12.720> few<00:19:12.840> others<00:19:13.110> and 00:19:13.610 --> 00:19:13.620 align:start position:0% any state changes and a few others and 00:19:13.620 --> 00:19:15.680 align:start position:0% any state changes and a few others and you<00:19:14.400> know<00:19:14.520> I<00:19:14.550> think<00:19:14.730> we<00:19:15.150> can<00:19:15.330> meet<00:19:15.480> good 00:19:15.680 --> 00:19:15.690 align:start position:0% you know I think we can meet good 00:19:15.690 --> 00:19:18.350 align:start position:0% you know I think we can meet good building<00:19:16.080> blocks<00:19:16.380> Ike<00:19:16.740> and<00:19:17.210> there<00:19:18.210> are 00:19:18.350 --> 00:19:18.360 align:start position:0% building blocks Ike and there are 00:19:18.360 --> 00:19:19.880 align:start position:0% building blocks Ike and there are different<00:19:19.080> creative<00:19:19.380> ways<00:19:19.410> of<00:19:19.680> high-level 00:19:19.880 --> 00:19:19.890 align:start position:0% different creative ways of high-level 00:19:19.890 --> 00:19:25.100 align:start position:0% different creative ways of high-level languages<00:19:20.520> vary<00:19:21.140> but<00:19:22.700> in<00:19:23.700> general<00:19:24.420> like<00:19:24.690> the 00:19:25.100 --> 00:19:25.110 align:start position:0% languages vary but in general like the 00:19:25.110 --> 00:19:26.840 align:start position:0% languages vary but in general like the impression<00:19:25.620> I've<00:19:25.740> gotten<00:19:26.070> is<00:19:26.220> that<00:19:26.400> it's<00:19:26.550> much 00:19:26.840 --> 00:19:26.850 align:start position:0% impression I've gotten is that it's much 00:19:26.850 --> 00:19:28.940 align:start position:0% impression I've gotten is that it's much more<00:19:26.880> about<00:19:27.300> these<00:19:27.660> sort<00:19:27.930> of<00:19:27.990> incremental 00:19:28.940 --> 00:19:28.950 align:start position:0% more about these sort of incremental 00:19:28.950 --> 00:19:35.480 align:start position:0% more about these sort of incremental additions<00:19:29.400> than<00:19:31.340> redesigns<00:19:34.040> all<00:19:35.040> right<00:19:35.220> I 00:19:35.480 --> 00:19:35.490 align:start position:0% additions than redesigns all right I 00:19:35.490 --> 00:19:37.490 align:start position:0% additions than redesigns all right I think<00:19:36.270> we're<00:19:36.510> running<00:19:36.780> out<00:19:36.870> of<00:19:36.900> time<00:19:37.020> is<00:19:37.470> that 00:19:37.490 --> 00:19:37.500 align:start position:0% think we're running out of time is that 00:19:37.500 --> 00:19:43.190 align:start position:0% think we're running out of time is that right<00:19:37.740> thing<00:19:38.010> yeah<00:19:39.020> so<00:19:40.340> thank<00:19:41.340> you<00:19:41.430> guys<00:19:42.200> thank 00:19:43.190 --> 00:19:43.200 align:start position:0% right thing yeah so thank you guys thank 00:19:43.200 --> 00:19:45.320 align:start position:0% right thing yeah so thank you guys thank you