WEBVTT Kind: captions Language: en 00:00:00.190 --> 00:00:17.500 align:start position:0% [Music] 00:00:17.500 --> 00:00:17.510 align:start position:0% 00:00:17.510 --> 00:00:22.269 align:start position:0% so<00:00:18.510> I'm<00:00:18.930> Greg<00:00:19.410> Colvin<00:00:20.010> I<00:00:20.220> work<00:00:20.700> mainly<00:00:21.000> on<00:00:21.450> the 00:00:22.269 --> 00:00:22.279 align:start position:0% so I'm Greg Colvin I work mainly on the 00:00:22.279 --> 00:00:28.370 align:start position:0% so I'm Greg Colvin I work mainly on the c++<00:00:23.279> evm<00:00:24.470> louder<00:00:25.470> I<00:00:26.369> work<00:00:26.790> mainly<00:00:27.029> on<00:00:27.419> the<00:00:27.540> c++ 00:00:28.370 --> 00:00:28.380 align:start position:0% c++ evm louder I work mainly on the c++ 00:00:28.380 --> 00:00:31.100 align:start position:0% c++ evm louder I work mainly on the c++ d<00:00:28.410> BM<00:00:28.890> this<00:00:29.580> is<00:00:29.730> my<00:00:29.910> friend<00:00:30.210> Martin<00:00:30.779> if<00:00:30.960> you 00:00:31.100 --> 00:00:31.110 align:start position:0% d BM this is my friend Martin if you 00:00:31.110 --> 00:00:32.950 align:start position:0% d BM this is my friend Martin if you want<00:00:31.290> to<00:00:31.380> introduce<00:00:31.590> yourself 00:00:32.950 --> 00:00:32.960 align:start position:0% want to introduce yourself 00:00:32.960 --> 00:00:36.100 align:start position:0% want to introduce yourself hi<00:00:33.960> I'm<00:00:34.140> Martin<00:00:34.350> busy<00:00:34.710> i'm<00:00:35.370> working<00:00:35.760> on 00:00:36.100 --> 00:00:36.110 align:start position:0% hi I'm Martin busy i'm working on 00:00:36.110 --> 00:00:40.240 align:start position:0% hi I'm Martin busy i'm working on prototyping<00:00:37.110> he<00:00:37.710> was<00:00:37.920> on<00:00:38.070> and<00:00:38.250> i<00:00:39.059> also<00:00:39.239> work<00:00:39.570> on 00:00:40.240 --> 00:00:40.250 align:start position:0% prototyping he was on and i also work on 00:00:40.250 --> 00:00:46.240 align:start position:0% prototyping he was on and i also work on the<00:00:41.250> new<00:00:41.489> MJS<00:00:42.059> and 00:00:46.240 --> 00:00:46.250 align:start position:0% 00:00:46.250 --> 00:00:50.770 align:start position:0% new<00:00:47.250> hi<00:00:47.490> I'm<00:00:48.030> pavo<00:00:48.360> and<00:00:48.720> I'm<00:00:49.560> working<00:00:50.130> on<00:00:50.400> small 00:00:50.770 --> 00:00:50.780 align:start position:0% new hi I'm pavo and I'm working on small 00:00:50.780 --> 00:00:55.610 align:start position:0% new hi I'm pavo and I'm working on small sub<00:00:51.780> project<00:00:52.320> called<00:00:52.650> a<00:00:52.950> vm<00:00:53.610> it's<00:00:54.420> a<00:00:54.660> kind 00:00:55.610 --> 00:00:55.620 align:start position:0% sub project called a vm it's a kind 00:00:55.620 --> 00:00:57.970 align:start position:0% sub project called a vm it's a kind of<00:00:55.770> just-in-time<00:00:56.370> compiler<00:00:57.090> does 00:00:57.970 --> 00:00:57.980 align:start position:0% of just-in-time compiler does 00:00:57.980 --> 00:01:01.490 align:start position:0% of just-in-time compiler does translates<00:00:58.980> a<00:00:59.400> vm<00:00:59.940> byte<00:01:00.180> code<00:01:00.510> into<00:01:01.140> machine 00:01:01.490 --> 00:01:01.500 align:start position:0% translates a vm byte code into machine 00:01:01.500 --> 00:01:05.319 align:start position:0% translates a vm byte code into machine code<00:01:02.130> using<00:01:03.000> llvm<00:01:03.930> project 00:01:05.319 --> 00:01:05.329 align:start position:0% code using llvm project 00:01:05.329 --> 00:01:08.090 align:start position:0% code using llvm project hey<00:01:06.329> I'm<00:01:06.600> Christina<00:01:07.049> like<00:01:07.170> listener<00:01:07.439> I'm<00:01:07.740> the 00:01:08.090 --> 00:01:08.100 align:start position:0% hey I'm Christina like listener I'm the 00:01:08.100 --> 00:01:09.289 align:start position:0% hey I'm Christina like listener I'm the team<00:01:08.369> leader<00:01:08.399> of<00:01:08.610> the<00:01:08.729> c++<00:01:09.180> implementation 00:01:09.289 --> 00:01:09.299 align:start position:0% team leader of the c++ implementation 00:01:09.299 --> 00:01:11.230 align:start position:0% team leader of the c++ implementation that<00:01:09.840> I'm<00:01:10.110> also 00:01:11.230 --> 00:01:11.240 align:start position:0% that I'm also 00:01:11.240 --> 00:01:13.940 align:start position:0% that I'm also working<00:01:12.240> on<00:01:12.420> solidity<00:01:12.869> which<00:01:13.229> is<00:01:13.470> basically 00:01:13.940 --> 00:01:13.950 align:start position:0% working on solidity which is basically 00:01:13.950 --> 00:01:17.240 align:start position:0% working on solidity which is basically the<00:01:14.100> main<00:01:14.570> user<00:01:15.570> of<00:01:16.049> the<00:01:16.380> etherium<00:01:16.920> virtual 00:01:17.240 --> 00:01:17.250 align:start position:0% the main user of the etherium virtual 00:01:17.250 --> 00:01:18.399 align:start position:0% the main user of the etherium virtual machine 00:01:18.399 --> 00:01:18.409 align:start position:0% machine 00:01:18.409 --> 00:01:21.559 align:start position:0% machine hello<00:01:19.409> my<00:01:20.100> name<00:01:20.249> is<00:01:20.280> Alex<00:01:20.639> Greig<00:01:20.850> sassy<00:01:21.270> and<00:01:21.479> I 00:01:21.559 --> 00:01:21.569 align:start position:0% hello my name is Alex Greig sassy and I 00:01:21.569 --> 00:01:24.919 align:start position:0% hello my name is Alex Greig sassy and I work<00:01:21.810> with<00:01:22.020> Martin<00:01:22.469> on<00:01:22.679> he<00:01:23.069> wasn't<00:01:23.509> as<00:01:24.509> well<00:01:24.810> as 00:01:24.919 --> 00:01:24.929 align:start position:0% work with Martin on he wasn't as well as 00:01:24.929 --> 00:01:26.989 align:start position:0% work with Martin on he wasn't as well as with<00:01:25.079> Christian<00:01:25.499> on<00:01:25.679> solidity<00:01:26.219> and<00:01:26.460> I'm 00:01:26.989 --> 00:01:26.999 align:start position:0% with Christian on solidity and I'm 00:01:26.999 --> 00:01:28.879 align:start position:0% with Christian on solidity and I'm really<00:01:27.240> interested<00:01:27.450> to<00:01:27.719> improve<00:01:28.139> both<00:01:28.409> even 00:01:28.879 --> 00:01:28.889 align:start position:0% really interested to improve both even 00:01:28.889 --> 00:01:31.429 align:start position:0% really interested to improve both even one<00:01:29.159> and<00:01:29.429> the<00:01:30.389> replacement<00:01:30.659> of<00:01:30.990> it<00:01:31.170> called<00:01:31.350> he 00:01:31.429 --> 00:01:31.439 align:start position:0% one and the replacement of it called he 00:01:31.439 --> 00:01:33.340 align:start position:0% one and the replacement of it called he wasn't 00:01:33.340 --> 00:01:33.350 align:start position:0% wasn't 00:01:33.350 --> 00:01:38.139 align:start position:0% wasn't so<00:01:34.819> what<00:01:35.819> I<00:01:35.850> wanted<00:01:36.329> to<00:01:36.389> do<00:01:36.780> this<00:01:37.020> morning<00:01:37.439> is 00:01:38.139 --> 00:01:38.149 align:start position:0% so what I wanted to do this morning is 00:01:38.149 --> 00:01:41.859 align:start position:0% so what I wanted to do this morning is everybody<00:01:39.149> got<00:01:39.450> working<00:01:40.020> so<00:01:40.709> fast 00:01:41.859 --> 00:01:41.869 align:start position:0% everybody got working so fast 00:01:41.869 --> 00:01:44.449 align:start position:0% everybody got working so fast approaching<00:01:42.869> the<00:01:42.990> conference<00:01:43.649> getting 00:01:44.449 --> 00:01:44.459 align:start position:0% approaching the conference getting 00:01:44.459 --> 00:01:46.999 align:start position:0% approaching the conference getting things<00:01:44.729> done<00:01:45.060> to<00:01:45.329> talk<00:01:45.539> about<00:01:45.779> that<00:01:46.649> I<00:01:46.799> could 00:01:46.999 --> 00:01:47.009 align:start position:0% things done to talk about that I could 00:01:47.009 --> 00:01:49.219 align:start position:0% things done to talk about that I could no<00:01:47.189> longer<00:01:47.429> keep<00:01:47.819> track<00:01:48.179> of<00:01:48.209> anything<00:01:48.659> but<00:01:49.049> my 00:01:49.219 --> 00:01:49.229 align:start position:0% no longer keep track of anything but my 00:01:49.229 --> 00:01:52.730 align:start position:0% no longer keep track of anything but my own<00:01:49.439> work<00:01:49.770> so<00:01:50.609> I<00:01:50.639> would<00:01:50.969> sort<00:01:51.209> of<00:01:51.389> like<00:01:51.600> to<00:01:51.959> just 00:01:52.730 --> 00:01:52.740 align:start position:0% own work so I would sort of like to just 00:01:52.740 --> 00:01:54.919 align:start position:0% own work so I would sort of like to just hear<00:01:53.009> from<00:01:53.069> people<00:01:53.490> what<00:01:54.450> they've<00:01:54.689> been<00:01:54.869> doing 00:01:54.919 --> 00:01:54.929 align:start position:0% hear from people what they've been doing 00:01:54.929 --> 00:01:57.969 align:start position:0% hear from people what they've been doing the<00:01:55.289> last<00:01:55.439> few<00:01:56.009> months<00:01:56.219> and<00:01:56.909> what<00:01:57.389> direction 00:01:57.969 --> 00:01:57.979 align:start position:0% the last few months and what direction 00:01:57.979 --> 00:02:00.969 align:start position:0% the last few months and what direction what<00:01:58.979> direction<00:01:59.189> they<00:01:59.729> intend<00:02:00.380> have<00:02:00.619> to<00:02:00.799> be 00:02:00.969 --> 00:02:00.979 align:start position:0% what direction they intend have to be 00:02:00.979 --> 00:02:05.310 align:start position:0% what direction they intend have to be heading<00:02:01.369> in<00:02:01.549> um<00:02:02.770> shall<00:02:03.770> we<00:02:03.799> start<00:02:04.189> with<00:02:04.430> Martin 00:02:05.310 --> 00:02:05.320 align:start position:0% heading in um shall we start with Martin 00:02:05.320 --> 00:02:08.350 align:start position:0% heading in um shall we start with Martin here<00:02:06.320> so<00:02:06.710> the<00:02:06.920> last<00:02:07.070> couple<00:02:07.340> months<00:02:07.579> I've<00:02:07.969> been 00:02:08.350 --> 00:02:08.360 align:start position:0% here so the last couple months I've been 00:02:08.360 --> 00:02:10.660 align:start position:0% here so the last couple months I've been working<00:02:08.720> on<00:02:08.810> something<00:02:09.050> called<00:02:09.410> EVM<00:02:09.979> tourism 00:02:10.660 --> 00:02:10.670 align:start position:0% working on something called EVM tourism 00:02:10.670 --> 00:02:14.890 align:start position:0% working on something called EVM tourism which<00:02:11.560> takes<00:02:12.560> EVM<00:02:13.130> code<00:02:13.489> in<00:02:13.880> trance<00:02:14.269> compiles 00:02:14.890 --> 00:02:14.900 align:start position:0% which takes EVM code in trance compiles 00:02:14.900 --> 00:02:18.250 align:start position:0% which takes EVM code in trance compiles it<00:02:15.170> to<00:02:15.349> web<00:02:15.620> assembly<00:02:16.599> and<00:02:17.599> we<00:02:18.050> are<00:02:18.110> now 00:02:18.250 --> 00:02:18.260 align:start position:0% it to web assembly and we are now 00:02:18.260 --> 00:02:20.500 align:start position:0% it to web assembly and we are now passing<00:02:18.560> all<00:02:19.040> the<00:02:19.250> virtual<00:02:19.610> machine<00:02:19.700> tests 00:02:20.500 --> 00:02:20.510 align:start position:0% passing all the virtual machine tests 00:02:20.510 --> 00:02:23.620 align:start position:0% passing all the virtual machine tests and<00:02:20.870> the<00:02:21.080> official<00:02:21.380> test<00:02:21.650> repository<00:02:22.510> we<00:02:23.510> also 00:02:23.620 --> 00:02:23.630 align:start position:0% and the official test repository we also 00:02:23.630 --> 00:02:25.120 align:start position:0% and the official test repository we also have<00:02:23.720> online<00:02:23.989> demo<00:02:24.560> if<00:02:24.680> you<00:02:24.769> want<00:02:24.920> to<00:02:24.980> check<00:02:25.069> it 00:02:25.120 --> 00:02:25.130 align:start position:0% have online demo if you want to check it 00:02:25.130 --> 00:02:27.059 align:start position:0% have online demo if you want to check it out<00:02:25.370> know 00:02:27.059 --> 00:02:27.069 align:start position:0% out know 00:02:27.069 --> 00:02:31.449 align:start position:0% out know what<00:02:28.069> is<00:02:28.250> a<00:02:28.280> transpiler<00:02:29.269> oh<00:02:30.069> ok<00:02:31.069> it's<00:02:31.340> good 00:02:31.449 --> 00:02:31.459 align:start position:0% what is a transpiler oh ok it's good 00:02:31.459 --> 00:02:33.449 align:start position:0% what is a transpiler oh ok it's good quick<00:02:31.610> so<00:02:31.940> we<00:02:32.390> have<00:02:32.510> two<00:02:32.660> types<00:02:32.870> of<00:02:32.989> bytecode 00:02:33.449 --> 00:02:33.459 align:start position:0% quick so we have two types of bytecode 00:02:33.459 --> 00:02:36.550 align:start position:0% quick so we have two types of bytecode start<00:02:34.459> out<00:02:34.580> with<00:02:34.989> atheneum<00:02:35.989> virtual<00:02:36.290> machine 00:02:36.550 --> 00:02:36.560 align:start position:0% start out with atheneum virtual machine 00:02:36.560 --> 00:02:40.780 align:start position:0% start out with atheneum virtual machine by<00:02:36.739> code<00:02:37.010> and<00:02:37.459> we<00:02:38.269> want<00:02:38.540> to<00:02:38.950> transform<00:02:39.950> it<00:02:40.549> to 00:02:40.780 --> 00:02:40.790 align:start position:0% by code and we want to transform it to 00:02:40.790 --> 00:02:43.539 align:start position:0% by code and we want to transform it to you<00:02:41.180> a<00:02:41.209> new<00:02:41.840> type<00:02:42.049> of<00:02:42.080> bytecode<00:02:42.590> web<00:02:42.950> assembly 00:02:43.539 --> 00:02:43.549 align:start position:0% you a new type of bytecode web assembly 00:02:43.549 --> 00:02:47.170 align:start position:0% you a new type of bytecode web assembly so<00:02:44.200> the<00:02:45.200> chance<00:02:45.470> compiler<00:02:46.370> you<00:02:46.519> can<00:02:46.670> think<00:02:46.880> in 00:02:47.170 --> 00:02:47.180 align:start position:0% so the chance compiler you can think in 00:02:47.180 --> 00:02:50.380 align:start position:0% so the chance compiler you can think in math<00:02:47.450> terms<00:02:47.630> as<00:02:47.989> a<00:02:48.019> function<00:02:48.560> that<00:02:48.769> map's<00:02:49.430> this 00:02:50.380 --> 00:02:50.390 align:start position:0% math terms as a function that map's this 00:02:50.390 --> 00:02:54.759 align:start position:0% math terms as a function that map's this one<00:02:50.599> input<00:02:50.780> BBM<00:02:51.590> to<00:02:52.280> a<00:02:52.310> new<00:02:52.989> output<00:02:53.989> what 00:02:54.759 --> 00:02:54.769 align:start position:0% one input BBM to a new output what 00:02:54.769 --> 00:02:57.059 align:start position:0% one input BBM to a new output what assembly<00:02:55.420> and 00:02:57.059 --> 00:02:57.069 align:start position:0% assembly and 00:02:57.069 --> 00:02:59.670 align:start position:0% assembly and why<00:02:58.069> web<00:02:58.370> assembly 00:02:59.670 --> 00:02:59.680 align:start position:0% why web assembly 00:02:59.680 --> 00:03:03.400 align:start position:0% why web assembly the<00:03:00.680> interesting<00:03:01.280> problem<00:03:01.730> ok<00:03:02.599> so<00:03:02.660> web 00:03:03.400 --> 00:03:03.410 align:start position:0% the interesting problem ok so web 00:03:03.410 --> 00:03:05.039 align:start position:0% the interesting problem ok so web assembly<00:03:03.980> is<00:03:04.220> a 00:03:05.039 --> 00:03:05.049 align:start position:0% assembly is a 00:03:05.049 --> 00:03:09.520 align:start position:0% assembly is a new<00:03:06.250> binary<00:03:07.250> format<00:03:08.030> that's<00:03:08.390> targeted<00:03:09.079> that's 00:03:09.520 --> 00:03:09.530 align:start position:0% new binary format that's targeted that's 00:03:09.530 --> 00:03:13.000 align:start position:0% new binary format that's targeted that's designed<00:03:10.220> and<00:03:10.430> me<00:03:10.519> targeted<00:03:11.060> for<00:03:11.530> the<00:03:12.530> web<00:03:12.709> the 00:03:13.000 --> 00:03:13.010 align:start position:0% designed and me targeted for the web the 00:03:13.010 --> 00:03:13.949 align:start position:0% designed and me targeted for the web the web<00:03:13.040> browser 00:03:13.949 --> 00:03:13.959 align:start position:0% web browser 00:03:13.959 --> 00:03:17.289 align:start position:0% web browser and<00:03:14.959> the<00:03:15.319> interesting<00:03:15.950> properties<00:03:16.579> that<00:03:17.090> has 00:03:17.289 --> 00:03:17.299 align:start position:0% and the interesting properties that has 00:03:17.299 --> 00:03:20.670 align:start position:0% and the interesting properties that has no<00:03:17.630> ever<00:03:17.780> interested<00:03:18.170> in<00:03:18.889> it<00:03:19.190> is 00:03:20.670 --> 00:03:20.680 align:start position:0% no ever interested in it is 00:03:20.680 --> 00:03:23.259 align:start position:0% no ever interested in it is it's<00:03:21.680> very<00:03:21.739> fast<00:03:22.190> and<00:03:22.370> efficient<00:03:22.790> it's 00:03:23.259 --> 00:03:23.269 align:start position:0% it's very fast and efficient it's 00:03:23.269 --> 00:03:26.580 align:start position:0% it's very fast and efficient it's portable<00:03:23.930> it's<00:03:24.489> sighs 00:03:26.580 --> 00:03:26.590 align:start position:0% portable it's sighs 00:03:26.590 --> 00:03:30.550 align:start position:0% portable it's sighs sighs<00:03:27.730> efficiency<00:03:28.730> so<00:03:29.000> it's<00:03:29.299> easy<00:03:30.139> to<00:03:30.170> press 00:03:30.550 --> 00:03:30.560 align:start position:0% sighs efficiency so it's easy to press 00:03:30.560 --> 00:03:34.410 align:start position:0% sighs efficiency so it's easy to press easy<00:03:31.359> to<00:03:32.359> load<00:03:32.540> and 00:03:34.410 --> 00:03:34.420 align:start position:0% easy to load and 00:03:34.420 --> 00:03:38.069 align:start position:0% easy to load and it<00:03:35.420> also<00:03:35.569> has<00:03:35.720> most<00:03:36.410> importantly<00:03:36.829> built<00:03:37.519> in 00:03:38.069 --> 00:03:38.079 align:start position:0% it also has most importantly built in 00:03:38.079 --> 00:03:40.360 align:start position:0% it also has most importantly built in it's<00:03:39.079> designed<00:03:39.500> to<00:03:39.560> run<00:03:39.739> the<00:03:39.920> website 00:03:40.360 --> 00:03:40.370 align:start position:0% it's designed to run the website 00:03:40.370 --> 00:03:42.250 align:start position:0% it's designed to run the website designed<00:03:41.060> to<00:03:41.209> run<00:03:41.359> in<00:03:41.540> untrusted 00:03:42.250 --> 00:03:42.260 align:start position:0% designed to run in untrusted 00:03:42.260 --> 00:03:46.539 align:start position:0% designed to run in untrusted environments<00:03:43.060> and<00:03:44.560> that<00:03:45.560> mask<00:03:45.739> so<00:03:45.950> closely<00:03:46.220> to 00:03:46.539 --> 00:03:46.549 align:start position:0% environments and that mask so closely to 00:03:46.549 --> 00:03:51.730 align:start position:0% environments and that mask so closely to what<00:03:46.579> we're<00:03:46.850> doing<00:03:47.180> so<00:03:47.810> yeah 00:03:51.730 --> 00:03:51.740 align:start position:0% 00:03:51.740 --> 00:03:53.800 align:start position:0% good<00:03:52.740> x 00:03:53.800 --> 00:03:53.810 align:start position:0% good x 00:03:53.810 --> 00:03:56.830 align:start position:0% good x okay<00:03:54.810> I<00:03:54.990> can<00:03:55.230> be<00:03:55.320> next 00:03:56.830 --> 00:03:56.840 align:start position:0% okay I can be next 00:03:56.840 --> 00:03:58.660 align:start position:0% okay I can be next so 00:03:58.660 --> 00:03:58.670 align:start position:0% so 00:03:58.670 --> 00:04:01.330 align:start position:0% so the<00:03:59.670> evm<00:04:00.000> jet<00:04:00.270> had 00:04:01.330 --> 00:04:01.340 align:start position:0% the evm jet had 00:04:01.340 --> 00:04:04.580 align:start position:0% the evm jet had Assyrian<00:04:02.540> the<00:04:03.540> virtual<00:04:04.440> machine 00:04:04.580 --> 00:04:04.590 align:start position:0% Assyrian the virtual machine 00:04:04.590 --> 00:04:07.550 align:start position:0% Assyrian the virtual machine implementation<00:04:05.520> I'm<00:04:05.730> carrying<00:04:06.240> off<00:04:06.560> it's 00:04:07.550 --> 00:04:07.560 align:start position:0% implementation I'm carrying off it's 00:04:07.560 --> 00:04:10.940 align:start position:0% implementation I'm carrying off it's fully<00:04:08.100> compliant<00:04:08.670> with<00:04:08.940> the<00:04:09.180> vm<00:04:09.780> from<00:04:10.110> from 00:04:10.940 --> 00:04:10.950 align:start position:0% fully compliant with the vm from from 00:04:10.950 --> 00:04:14.110 align:start position:0% fully compliant with the vm from from the<00:04:11.100> land<00:04:11.280> of<00:04:11.750> the<00:04:12.750> cereal 00:04:14.110 --> 00:04:14.120 align:start position:0% the land of the cereal 00:04:14.120 --> 00:04:17.240 align:start position:0% the land of the cereal but<00:04:15.120> the<00:04:15.390> problem<00:04:15.840> I<00:04:16.049> was<00:04:16.320> trying<00:04:16.680> to<00:04:16.799> solve 00:04:17.240 --> 00:04:17.250 align:start position:0% but the problem I was trying to solve 00:04:17.250 --> 00:04:21.830 align:start position:0% but the problem I was trying to solve from<00:04:18.260> about<00:04:19.260> couple<00:04:20.040> of<00:04:20.100> miles<00:04:20.400> is<00:04:20.780> how<00:04:21.780> to 00:04:21.830 --> 00:04:21.840 align:start position:0% from about couple of miles is how to 00:04:21.840 --> 00:04:23.590 align:start position:0% from about couple of miles is how to bring<00:04:22.770> this 00:04:23.590 --> 00:04:23.600 align:start position:0% bring this 00:04:23.600 --> 00:04:27.890 align:start position:0% bring this implementation<00:04:24.600> to<00:04:25.169> other<00:04:25.770> clients<00:04:26.370> so<00:04:27.150> what 00:04:27.890 --> 00:04:27.900 align:start position:0% implementation to other clients so what 00:04:27.900 --> 00:04:31.030 align:start position:0% implementation to other clients so what I<00:04:27.930> was<00:04:28.290> working<00:04:28.560> on<00:04:28.910> is<00:04:29.910> a 00:04:31.030 --> 00:04:31.040 align:start position:0% I was working on is a 00:04:31.040 --> 00:04:36.490 align:start position:0% I was working on is a new<00:04:32.300> CC<00:04:33.300> c<00:04:33.780> language<00:04:33.960> interface<00:04:34.770> for 00:04:36.490 --> 00:04:36.500 align:start position:0% new CC c language interface for 00:04:36.500 --> 00:04:40.700 align:start position:0% new CC c language interface for film<00:04:37.500> virtual<00:04:38.430> machine<00:04:38.760> in<00:04:38.910> general<00:04:39.530> what<00:04:40.530> we 00:04:40.700 --> 00:04:40.710 align:start position:0% film virtual machine in general what we 00:04:40.710 --> 00:04:43.300 align:start position:0% film virtual machine in general what we call<00:04:41.010> EV<00:04:41.790> MC<00:04:42.270> and 00:04:43.300 --> 00:04:43.310 align:start position:0% call EV MC and 00:04:43.310 --> 00:04:46.510 align:start position:0% call EV MC and it's<00:04:44.310> like 00:04:46.510 --> 00:04:46.520 align:start position:0% it's like 00:04:46.520 --> 00:04:50.080 align:start position:0% it's like quite<00:04:47.660> quite<00:04:48.660> simple 00:04:50.080 --> 00:04:50.090 align:start position:0% quite quite simple 00:04:50.090 --> 00:04:54.650 align:start position:0% quite quite simple interface<00:04:51.090> then<00:04:51.840> you<00:04:52.440> can<00:04:52.710> pack<00:04:53.100> your<00:04:53.660> vm 00:04:54.650 --> 00:04:54.660 align:start position:0% interface then you can pack your vm 00:04:54.660 --> 00:04:58.130 align:start position:0% interface then you can pack your vm implementation<00:04:55.530> with<00:04:55.800> and<00:04:56.270> bring<00:04:57.270> it<00:04:57.450> to<00:04:57.479> two 00:04:58.130 --> 00:04:58.140 align:start position:0% implementation with and bring it to two 00:04:58.140 --> 00:05:01.670 align:start position:0% implementation with and bring it to two other<00:04:58.290> other<00:04:59.130> other<00:04:59.930> projects<00:05:00.930> that<00:05:01.140> might<00:05:01.500> be 00:05:01.670 --> 00:05:01.680 align:start position:0% other other other projects that might be 00:05:01.680 --> 00:05:04.060 align:start position:0% other other other projects that might be interested<00:05:02.220> in<00:05:02.340> so 00:05:04.060 --> 00:05:04.070 align:start position:0% interested in so 00:05:04.070 --> 00:05:07.100 align:start position:0% interested in so just<00:05:05.070> before<00:05:05.310> the<00:05:05.610> conference<00:05:05.970> i<00:05:06.300> was<00:05:06.479> able<00:05:06.810> to 00:05:07.100 --> 00:05:07.110 align:start position:0% just before the conference i was able to 00:05:07.110 --> 00:05:10.670 align:start position:0% just before the conference i was able to plug<00:05:07.530> a<00:05:07.860> vm<00:05:08.220> g<00:05:08.250> to<00:05:08.700> Python<00:05:09.090> client<00:05:09.330> it's<00:05:10.200> still 00:05:10.670 --> 00:05:10.680 align:start position:0% plug a vm g to Python client it's still 00:05:10.680 --> 00:05:13.550 align:start position:0% plug a vm g to Python client it's still syncing<00:05:11.280> the<00:05:11.490> blockchain<00:05:11.790> but<00:05:12.330> I<00:05:12.360> hope<00:05:12.840> it<00:05:13.050> can 00:05:13.550 --> 00:05:13.560 align:start position:0% syncing the blockchain but I hope it can 00:05:13.560 --> 00:05:17.080 align:start position:0% syncing the blockchain but I hope it can finish<00:05:13.970> during<00:05:14.970> this<00:05:15.120> conference<00:05:15.570> and 00:05:17.080 --> 00:05:17.090 align:start position:0% finish during this conference and 00:05:17.090 --> 00:05:21.070 align:start position:0% finish during this conference and yeah<00:05:18.090> so<00:05:18.419> it's<00:05:18.890> I'm<00:05:19.890> not<00:05:20.250> focusing<00:05:20.880> on 00:05:21.070 --> 00:05:21.080 align:start position:0% yeah so it's I'm not focusing on 00:05:21.080 --> 00:05:24.080 align:start position:0% yeah so it's I'm not focusing on optimizing<00:05:22.080> the<00:05:22.590> the<00:05:22.860> execution<00:05:23.130> time<00:05:23.729> but 00:05:24.080 --> 00:05:24.090 align:start position:0% optimizing the the execution time but 00:05:24.090 --> 00:05:28.280 align:start position:0% optimizing the the execution time but mostly<00:05:24.510> to<00:05:25.160> bring<00:05:26.160> in<00:05:26.400> my<00:05:27.270> project<00:05:27.570> to<00:05:28.140> other 00:05:28.280 --> 00:05:28.290 align:start position:0% mostly to bring in my project to other 00:05:28.290 --> 00:05:29.500 align:start position:0% mostly to bring in my project to other products 00:05:29.500 --> 00:05:29.510 align:start position:0% products 00:05:29.510 --> 00:05:32.620 align:start position:0% products so<00:05:30.510> so<00:05:31.020> we<00:05:31.140> now<00:05:31.350> have<00:05:31.620> a<00:05:31.650> plug-and-play 00:05:32.620 --> 00:05:32.630 align:start position:0% so so we now have a plug-and-play 00:05:32.630 --> 00:05:36.700 align:start position:0% so so we now have a plug-and-play interface<00:05:33.650> for<00:05:34.650> both<00:05:34.860> the<00:05:35.100> c++ 00:05:36.700 --> 00:05:36.710 align:start position:0% interface for both the c++ 00:05:36.710 --> 00:05:38.500 align:start position:0% interface for both the c++ execution<00:05:37.710> engine 00:05:38.500 --> 00:05:38.510 align:start position:0% execution engine 00:05:38.510 --> 00:05:41.980 align:start position:0% execution engine and<00:05:38.660> the<00:05:39.050> Python<00:05:40.090> execution<00:05:41.090> engine<00:05:41.330> yeah 00:05:41.980 --> 00:05:41.990 align:start position:0% and the Python execution engine yeah 00:05:41.990 --> 00:05:45.130 align:start position:0% and the Python execution engine yeah that's<00:05:42.230> right<00:05:42.410> so<00:05:42.770> so<00:05:43.400> the<00:05:43.930> disciplines<00:05:44.930> blast 00:05:45.130 --> 00:05:45.140 align:start position:0% that's right so so the disciplines blast 00:05:45.140 --> 00:05:48.220 align:start position:0% that's right so so the disciplines blast client<00:05:45.620> and<00:05:45.890> Python<00:05:46.490> client<00:05:46.730> I<00:05:47.210> able<00:05:47.930> to<00:05:47.990> use 00:05:48.220 --> 00:05:48.230 align:start position:0% client and Python client I able to use 00:05:48.230 --> 00:05:51.460 align:start position:0% client and Python client I able to use the<00:05:48.410> same<00:05:48.650> interface<00:05:49.130> for<00:05:49.490> a<00:05:49.730> vm<00:05:49.970> g<00:05:50.000> to<00:05:50.540> be 00:05:51.460 --> 00:05:51.470 align:start position:0% the same interface for a vm g to be 00:05:51.470 --> 00:05:54.180 align:start position:0% the same interface for a vm g to be operational<00:05:52.190> on<00:05:52.370> the<00:05:52.550> on<00:05:52.820> the<00:05:52.880> blockchain 00:05:54.180 --> 00:05:54.190 align:start position:0% operational on the on the blockchain 00:05:54.190 --> 00:05:57.300 align:start position:0% operational on the on the blockchain so<00:05:55.190> it's<00:05:55.460> still<00:05:55.700> experimental<00:05:56.030> but 00:05:57.300 --> 00:05:57.310 align:start position:0% so it's still experimental but 00:05:57.310 --> 00:06:02.340 align:start position:0% so it's still experimental but very<00:05:58.310> promising<00:05:59.050> that's<00:06:00.050> really<00:06:00.380> cool 00:06:02.340 --> 00:06:02.350 align:start position:0% very promising that's really cool 00:06:02.350 --> 00:06:05.050 align:start position:0% very promising that's really cool so<00:06:03.350> that's<00:06:03.530> that<00:06:04.070> basically<00:06:04.670> the<00:06:04.730> idea<00:06:04.760> is<00:06:05.030> to 00:06:05.050 --> 00:06:05.060 align:start position:0% so that's that basically the idea is to 00:06:05.060 --> 00:06:08.890 align:start position:0% so that's that basically the idea is to have<00:06:05.240> a<00:06:05.920> common<00:06:06.920> interface<00:06:07.160> between<00:06:07.610> the<00:06:07.900> the 00:06:08.890 --> 00:06:08.900 align:start position:0% have a common interface between the the 00:06:08.900 --> 00:06:10.990 align:start position:0% have a common interface between the the client<00:06:09.320> and<00:06:09.440> the<00:06:09.560> virtual<00:06:09.860> machine<00:06:09.950> and<00:06:10.400> in 00:06:10.990 --> 00:06:11.000 align:start position:0% client and the virtual machine and in 00:06:11.000 --> 00:06:12.910 align:start position:0% client and the virtual machine and in the<00:06:11.090> end<00:06:11.120> be<00:06:11.420> able<00:06:11.750> to<00:06:11.900> swap<00:06:12.530> different 00:06:12.910 --> 00:06:12.920 align:start position:0% the end be able to swap different 00:06:12.920 --> 00:06:14.410 align:start position:0% the end be able to swap different virtual<00:06:13.070> machines<00:06:13.550> and<00:06:13.790> we're<00:06:13.940> also<00:06:14.030> planning 00:06:14.410 --> 00:06:14.420 align:start position:0% virtual machines and we're also planning 00:06:14.420 --> 00:06:15.990 align:start position:0% virtual machines and we're also planning to 00:06:15.990 --> 00:06:16.000 align:start position:0% to 00:06:16.000 --> 00:06:19.300 align:start position:0% to to<00:06:17.000> refactor<00:06:17.360> the<00:06:17.630> C++<00:06:18.320> interpreter<00:06:18.890> to<00:06:19.160> use 00:06:19.300 --> 00:06:19.310 align:start position:0% to refactor the C++ interpreter to use 00:06:19.310 --> 00:06:21.220 align:start position:0% to refactor the C++ interpreter to use exactly<00:06:19.640> the<00:06:19.820> same<00:06:20.060> interface<00:06:20.480> so<00:06:20.930> you<00:06:20.990> could 00:06:21.220 --> 00:06:21.230 align:start position:0% exactly the same interface so you could 00:06:21.230 --> 00:06:22.920 align:start position:0% exactly the same interface so you could seamlessly<00:06:21.770> swap<00:06:22.220> between 00:06:22.920 --> 00:06:22.930 align:start position:0% seamlessly swap between 00:06:22.930 --> 00:06:24.940 align:start position:0% seamlessly swap between just-in-time<00:06:23.930> compiler<00:06:24.440> and<00:06:24.680> the 00:06:24.940 --> 00:06:24.950 align:start position:0% just-in-time compiler and the 00:06:24.950 --> 00:06:26.500 align:start position:0% just-in-time compiler and the interpreter<00:06:25.550> and<00:06:25.730> you<00:06:25.910> can<00:06:26.060> use<00:06:26.300> the 00:06:26.500 --> 00:06:26.510 align:start position:0% interpreter and you can use the 00:06:26.510 --> 00:06:28.600 align:start position:0% interpreter and you can use the interpreter<00:06:26.960> with<00:06:27.110> all<00:06:27.610> client 00:06:28.600 --> 00:06:28.610 align:start position:0% interpreter with all client 00:06:28.610 --> 00:06:29.980 align:start position:0% interpreter with all client implementations<00:06:29.210> that<00:06:29.300> support<00:06:29.840> that 00:06:29.980 --> 00:06:29.990 align:start position:0% implementations that support that 00:06:29.990 --> 00:06:32.910 align:start position:0% implementations that support that interface 00:06:32.910 --> 00:06:32.920 align:start position:0% 00:06:32.920 --> 00:06:37.570 align:start position:0% very<00:06:33.920> nice<00:06:34.220> very<00:06:34.880> nice 00:06:37.570 --> 00:06:37.580 align:start position:0% 00:06:37.580 --> 00:06:39.850 align:start position:0% like<00:06:38.270> this 00:06:39.850 --> 00:06:39.860 align:start position:0% like this 00:06:39.860 --> 00:06:45.570 align:start position:0% like this [Applause] 00:06:45.570 --> 00:06:45.580 align:start position:0% [Applause] 00:06:45.580 --> 00:06:48.480 align:start position:0% [Applause] rock<00:06:46.580> and<00:06:46.939> roll 00:06:48.480 --> 00:06:48.490 align:start position:0% rock and roll 00:06:48.490 --> 00:06:51.939 align:start position:0% rock and roll that<00:06:49.490> will<00:06:49.669> be<00:06:49.819> at<00:06:49.939> the<00:06:50.090> party<00:06:50.360> later<00:06:50.780> I<00:06:51.229> have 00:06:51.939 --> 00:06:51.949 align:start position:0% that will be at the party later I have 00:06:51.949 --> 00:06:54.070 align:start position:0% that will be at the party later I have to<00:06:52.099> go<00:06:52.219> buy<00:06:52.430> a<00:06:52.460> guitar<00:06:52.759> if<00:06:53.360> anybody<00:06:53.750> knows<00:06:54.050> a 00:06:54.070 --> 00:06:54.080 align:start position:0% to go buy a guitar if anybody knows a 00:06:54.080 --> 00:06:57.929 align:start position:0% to go buy a guitar if anybody knows a good<00:06:54.439> place 00:06:57.929 --> 00:06:57.939 align:start position:0% 00:06:57.939 --> 00:07:00.510 align:start position:0% what<00:06:58.939> else<00:06:59.180> here 00:07:00.510 --> 00:07:00.520 align:start position:0% what else here 00:07:00.520 --> 00:07:04.260 align:start position:0% what else here Alec<00:07:01.520> enemy<00:07:02.409> all<00:07:03.409> right 00:07:04.260 --> 00:07:04.270 align:start position:0% Alec enemy all right 00:07:04.270 --> 00:07:06.999 align:start position:0% Alec enemy all right yeah<00:07:05.270> you<00:07:05.360> will<00:07:05.599> you<00:07:06.259> will<00:07:06.379> learn<00:07:06.530> about<00:07:06.710> you 00:07:06.999 --> 00:07:07.009 align:start position:0% yeah you will you will learn about you 00:07:07.009 --> 00:07:09.309 align:start position:0% yeah you will you will learn about you awesome<00:07:07.219> later<00:07:08.180> on<00:07:08.479> it<00:07:08.870> will<00:07:09.080> be<00:07:09.139> the<00:07:09.289> first 00:07:09.309 --> 00:07:09.319 align:start position:0% awesome later on it will be the first 00:07:09.319 --> 00:07:11.740 align:start position:0% awesome later on it will be the first presentation<00:07:09.860> today<00:07:10.280> after<00:07:10.699> lunch<00:07:10.940> and<00:07:11.180> I 00:07:11.740 --> 00:07:11.750 align:start position:0% presentation today after lunch and I 00:07:11.750 --> 00:07:13.779 align:start position:0% presentation today after lunch and I invite<00:07:12.080> everyone<00:07:12.409> to<00:07:12.560> listen<00:07:13.159> to<00:07:13.490> it<00:07:13.580> because 00:07:13.779 --> 00:07:13.789 align:start position:0% invite everyone to listen to it because 00:07:13.789 --> 00:07:16.540 align:start position:0% invite everyone to listen to it because if<00:07:13.909> you'll<00:07:14.060> be<00:07:14.210> very<00:07:14.449> interesting<00:07:15.099> but<00:07:16.099> i<00:07:16.250> can 00:07:16.540 --> 00:07:16.550 align:start position:0% if you'll be very interesting but i can 00:07:16.550 --> 00:07:18.730 align:start position:0% if you'll be very interesting but i can tell<00:07:16.759> you<00:07:16.789> up<00:07:17.060> front<00:07:17.090> a<00:07:17.449> few<00:07:17.629> details<00:07:18.020> which 00:07:18.730 --> 00:07:18.740 align:start position:0% tell you up front a few details which 00:07:18.740 --> 00:07:20.369 align:start position:0% tell you up front a few details which connects<00:07:19.190> to<00:07:19.280> this<00:07:19.370> panel 00:07:20.369 --> 00:07:20.379 align:start position:0% connects to this panel 00:07:20.379 --> 00:07:22.959 align:start position:0% connects to this panel that<00:07:21.379> mostly<00:07:21.650> we<00:07:21.830> have<00:07:22.009> been<00:07:22.190> working<00:07:22.550> on<00:07:22.729> and 00:07:22.959 --> 00:07:22.969 align:start position:0% that mostly we have been working on and 00:07:22.969 --> 00:07:25.570 align:start position:0% that mostly we have been working on and two<00:07:23.750> different<00:07:23.840> things<00:07:24.229> first<00:07:25.009> of<00:07:25.159> all<00:07:25.340> as 00:07:25.570 --> 00:07:25.580 align:start position:0% two different things first of all as 00:07:25.580 --> 00:07:27.909 align:start position:0% two different things first of all as Martinez<00:07:26.090> mentioned<00:07:26.599> and<00:07:26.840> was<00:07:27.590> him<00:07:27.770> is<00:07:27.889> a 00:07:27.909 --> 00:07:27.919 align:start position:0% Martinez mentioned and was him is a 00:07:27.919 --> 00:07:31.119 align:start position:0% Martinez mentioned and was him is a different<00:07:28.280> bytecode<00:07:28.759> so<00:07:29.479> we<00:07:30.169> need<00:07:30.379> multiple 00:07:31.119 --> 00:07:31.129 align:start position:0% different bytecode so we need multiple 00:07:31.129 --> 00:07:33.550 align:start position:0% different bytecode so we need multiple languages<00:07:31.550> to<00:07:31.849> compile<00:07:32.810> code<00:07:33.169> to<00:07:33.440> this 00:07:33.550 --> 00:07:33.560 align:start position:0% languages to compile code to this 00:07:33.560 --> 00:07:35.350 align:start position:0% languages to compile code to this bytecode<00:07:33.800> because<00:07:34.400> you<00:07:34.490> don't<00:07:34.699> want<00:07:34.789> to<00:07:35.150> write 00:07:35.350 --> 00:07:35.360 align:start position:0% bytecode because you don't want to write 00:07:35.360 --> 00:07:38.619 align:start position:0% bytecode because you don't want to write byte<00:07:35.629> code<00:07:35.870> by<00:07:36.139> hand<00:07:36.439> and<00:07:37.189> secondly<00:07:38.090> you<00:07:38.599> want 00:07:38.619 --> 00:07:38.629 align:start position:0% byte code by hand and secondly you want 00:07:38.629 --> 00:07:41.790 align:start position:0% byte code by hand and secondly you want to<00:07:39.199> run<00:07:39.949> this<00:07:40.129> bite<00:07:40.340> good<00:07:40.580> on<00:07:40.639> something<00:07:41.240> and 00:07:41.790 --> 00:07:41.800 align:start position:0% to run this bite good on something and 00:07:41.800 --> 00:07:44.110 align:start position:0% to run this bite good on something and on<00:07:42.800> the<00:07:42.979> language<00:07:43.129> side<00:07:43.550> we<00:07:43.789> have<00:07:43.819> been 00:07:44.110 --> 00:07:44.120 align:start position:0% on the language side we have been 00:07:44.120 --> 00:07:47.019 align:start position:0% on the language side we have been working<00:07:44.719> on<00:07:45.139> getting<00:07:45.469> C<00:07:46.009> and<00:07:46.250> solidity<00:07:46.729> ready 00:07:47.019 --> 00:07:47.029 align:start position:0% working on getting C and solidity ready 00:07:47.029 --> 00:07:49.600 align:start position:0% working on getting C and solidity ready and<00:07:47.300> we<00:07:48.020> have<00:07:48.169> written<00:07:48.409> a<00:07:48.740> lot<00:07:48.889> of<00:07:49.039> contracts 00:07:49.600 --> 00:07:49.610 align:start position:0% and we have written a lot of contracts 00:07:49.610 --> 00:07:51.730 align:start position:0% and we have written a lot of contracts in<00:07:49.759> these<00:07:49.969> languages<00:07:50.300> all<00:07:50.539> ready<00:07:50.719> for<00:07:51.139> wasn't 00:07:51.730 --> 00:07:51.740 align:start position:0% in these languages all ready for wasn't 00:07:51.740 --> 00:07:55.809 align:start position:0% in these languages all ready for wasn't and<00:07:52.240> on<00:07:53.240> the<00:07:53.629> vm<00:07:54.080> side<00:07:54.349> actually<00:07:54.710> be<00:07:55.580> really 00:07:55.809 --> 00:07:55.819 align:start position:0% and on the vm side actually be really 00:07:55.819 --> 00:07:59.170 align:start position:0% and on the vm side actually be really grateful<00:07:56.449> to<00:07:56.629> have<00:07:57.469> all<00:07:57.529> and<00:07:57.889> his<00:07:58.639> work<00:07:58.819> on<00:07:58.969> EV 00:07:59.170 --> 00:07:59.180 align:start position:0% grateful to have all and his work on EV 00:07:59.180 --> 00:08:02.379 align:start position:0% grateful to have all and his work on EV MC<00:07:59.650> because<00:08:00.650> we<00:08:00.770> have<00:08:00.889> implemented<00:08:01.190> vm<00:08:01.699> on<00:08:01.909> EV 00:08:02.379 --> 00:08:02.389 align:start position:0% MC because we have implemented vm on EV 00:08:02.389 --> 00:08:05.800 align:start position:0% MC because we have implemented vm on EV MC<00:08:02.839> and<00:08:03.139> that<00:08:03.469> means<00:08:03.770> he<00:08:04.639> wasn't<00:08:04.940> can<00:08:05.330> be<00:08:05.509> used 00:08:05.800 --> 00:08:05.810 align:start position:0% MC and that means he wasn't can be used 00:08:05.810 --> 00:08:09.040 align:start position:0% MC and that means he wasn't can be used with<00:08:06.099> syllabus<00:08:07.099> athyrium<00:08:07.669> without<00:08:08.449> any<00:08:08.779> major 00:08:09.040 --> 00:08:09.050 align:start position:0% with syllabus athyrium without any major 00:08:09.050 --> 00:08:12.269 align:start position:0% with syllabus athyrium without any major changes<00:08:09.699> Thank<00:08:10.699> You<00:08:10.849> papa 00:08:12.269 --> 00:08:12.279 align:start position:0% changes Thank You papa 00:08:12.279 --> 00:08:15.189 align:start position:0% changes Thank You papa why<00:08:13.279> would<00:08:13.580> you<00:08:13.610> want<00:08:14.029> to<00:08:14.150> write<00:08:14.479> contracts 00:08:15.189 --> 00:08:15.199 align:start position:0% why would you want to write contracts 00:08:15.199 --> 00:08:16.890 align:start position:0% why would you want to write contracts and<00:08:15.560> see 00:08:16.890 --> 00:08:16.900 align:start position:0% and see 00:08:16.900 --> 00:08:19.420 align:start position:0% and see you<00:08:17.900> don't<00:08:18.080> really<00:08:18.229> want<00:08:18.440> to<00:08:18.469> write<00:08:18.770> contracts 00:08:19.420 --> 00:08:19.430 align:start position:0% you don't really want to write contracts 00:08:19.430 --> 00:08:22.629 align:start position:0% you don't really want to write contracts as<00:08:19.759> an<00:08:20.060> end<00:08:20.210> user<00:08:20.300> in<00:08:20.690> C<00:08:20.960> but<00:08:21.860> there<00:08:22.580> are 00:08:22.629 --> 00:08:22.639 align:start position:0% as an end user in C but there are 00:08:22.639 --> 00:08:24.430 align:start position:0% as an end user in C but there are certain<00:08:23.000> contracts<00:08:23.569> which<00:08:23.719> probably<00:08:24.199> makes 00:08:24.430 --> 00:08:24.440 align:start position:0% certain contracts which probably makes 00:08:24.440 --> 00:08:27.850 align:start position:0% certain contracts which probably makes sense<00:08:24.529> to<00:08:24.949> be<00:08:25.039> written<00:08:25.219> in<00:08:25.430> C<00:08:25.699> and<00:08:25.909> I<00:08:26.870> don't<00:08:27.800> you 00:08:27.850 --> 00:08:27.860 align:start position:0% sense to be written in C and I don't you 00:08:27.860 --> 00:08:29.740 align:start position:0% sense to be written in C and I don't you want<00:08:28.039> to<00:08:28.129> go<00:08:28.250> into<00:08:28.400> a<00:08:28.520> lot<00:08:28.759> of<00:08:28.819> detail<00:08:29.270> you<00:08:29.599> will 00:08:29.740 --> 00:08:29.750 align:start position:0% want to go into a lot of detail you will 00:08:29.750 --> 00:08:31.450 align:start position:0% want to go into a lot of detail you will see<00:08:29.930> a<00:08:29.960> bit<00:08:30.199> more<00:08:30.229> in<00:08:30.529> the<00:08:30.620> presentation<00:08:31.099> and 00:08:31.450 --> 00:08:31.460 align:start position:0% see a bit more in the presentation and 00:08:31.460 --> 00:08:34.540 align:start position:0% see a bit more in the presentation and but<00:08:32.390> just<00:08:32.959> think<00:08:33.440> about<00:08:33.560> the<00:08:33.769> precompiler<00:08:34.310> you 00:08:34.540 --> 00:08:34.550 align:start position:0% but just think about the precompiler you 00:08:34.550 --> 00:08:37.449 align:start position:0% but just think about the precompiler you already<00:08:34.849> have<00:08:35.060> and<00:08:35.300> the<00:08:36.140> for<00:08:36.349> pecan<00:08:36.680> pies<00:08:36.890> like 00:08:37.449 --> 00:08:37.459 align:start position:0% already have and the for pecan pies like 00:08:37.459 --> 00:08:41.790 align:start position:0% already have and the for pecan pies like sha-256<00:08:38.419> ripe<00:08:39.019> em<00:08:39.199> 360<00:08:40.159> and<00:08:40.430> easy<00:08:40.940> recovery 00:08:41.790 --> 00:08:41.800 align:start position:0% sha-256 ripe em 360 and easy recovery 00:08:41.800 --> 00:08:44.920 align:start position:0% sha-256 ripe em 360 and easy recovery you<00:08:42.800> want<00:08:43.070> this<00:08:43.250> to<00:08:43.490> be<00:08:43.610> written<00:08:43.880> in<00:08:44.300> a<00:08:44.449> highly 00:08:44.920 --> 00:08:44.930 align:start position:0% you want this to be written in a highly 00:08:44.930 --> 00:08:47.079 align:start position:0% you want this to be written in a highly efficient<00:08:45.410> way<00:08:45.620> and<00:08:45.850> those<00:08:46.850> should<00:08:47.060> be 00:08:47.079 --> 00:08:47.089 align:start position:0% efficient way and those should be 00:08:47.089 --> 00:08:49.240 align:start position:0% efficient way and those should be included<00:08:47.569> by<00:08:47.690> all<00:08:47.870> the<00:08:47.990> VMS<00:08:48.110> and<00:08:48.529> you<00:08:49.040> don't 00:08:49.240 --> 00:08:49.250 align:start position:0% included by all the VMS and you don't 00:08:49.250 --> 00:08:51.220 align:start position:0% included by all the VMS and you don't really<00:08:49.399> want<00:08:49.640> to<00:08:49.880> f<00:08:49.940> them<00:08:50.210> as<00:08:50.600> a<00:08:50.660> pre-compiled 00:08:51.220 --> 00:08:51.230 align:start position:0% really want to f them as a pre-compiled 00:08:51.230 --> 00:08:53.470 align:start position:0% really want to f them as a pre-compiled anymore<00:08:51.710> in<00:08:51.950> the<00:08:52.370> future<00:08:52.580> so<00:08:53.300> those<00:08:53.450> are 00:08:53.470 --> 00:08:53.480 align:start position:0% anymore in the future so those are 00:08:53.480 --> 00:08:55.510 align:start position:0% anymore in the future so those are written<00:08:54.020> in<00:08:54.110> C<00:08:54.350> right<00:08:54.620> now<00:08:54.830> and<00:08:55.040> they<00:08:55.490> are 00:08:55.510 --> 00:08:55.520 align:start position:0% written in C right now and they are 00:08:55.520 --> 00:08:57.850 align:start position:0% written in C right now and they are limited<00:08:56.060> set<00:08:56.300> off<00:08:56.420> of<00:08:56.600> code<00:08:57.200> which<00:08:57.470> you<00:08:57.500> can 00:08:57.850 --> 00:08:57.860 align:start position:0% limited set off of code which you can 00:08:57.860 --> 00:09:00.550 align:start position:0% limited set off of code which you can much<00:08:58.010> easily<00:08:58.390> verify<00:08:59.390> I<00:08:59.660> wouldn't<00:09:00.290> advise 00:09:00.550 --> 00:09:00.560 align:start position:0% much easily verify I wouldn't advise 00:09:00.560 --> 00:09:03.370 align:start position:0% much easily verify I wouldn't advise anyone<00:09:00.860> to<00:09:00.980> write<00:09:01.660> like<00:09:02.660> a<00:09:02.690> really<00:09:03.020> complex 00:09:03.370 --> 00:09:03.380 align:start position:0% anyone to write like a really complex 00:09:03.380 --> 00:09:05.770 align:start position:0% anyone to write like a really complex contract<00:09:03.980> and<00:09:04.160> see<00:09:04.400> unless<00:09:05.300> they<00:09:05.450> know<00:09:05.600> what 00:09:05.770 --> 00:09:05.780 align:start position:0% contract and see unless they know what 00:09:05.780 --> 00:09:06.630 align:start position:0% contract and see unless they know what they're<00:09:05.930> doing 00:09:06.630 --> 00:09:06.640 align:start position:0% they're doing 00:09:06.640 --> 00:09:10.290 align:start position:0% they're doing solidity<00:09:07.640> is<00:09:07.790> hard<00:09:08.150> enough<00:09:08.330> it<00:09:08.810> turns<00:09:08.990> out 00:09:10.290 --> 00:09:10.300 align:start position:0% solidity is hard enough it turns out 00:09:10.300 --> 00:09:12.820 align:start position:0% solidity is hard enough it turns out yeah<00:09:11.300> I<00:09:11.510> mean<00:09:11.660> the<00:09:12.110> thing<00:09:12.260> is<00:09:12.290> also<00:09:12.500> that<00:09:12.710> that 00:09:12.820 --> 00:09:12.830 align:start position:0% yeah I mean the thing is also that that 00:09:12.830 --> 00:09:15.700 align:start position:0% yeah I mean the thing is also that that a<00:09:13.010> lot<00:09:13.250> of<00:09:13.430> code<00:09:13.910> already<00:09:14.480> exists<00:09:15.410> in<00:09:15.530> see 00:09:15.700 --> 00:09:15.710 align:start position:0% a lot of code already exists in see 00:09:15.710 --> 00:09:18.970 align:start position:0% a lot of code already exists in see especially<00:09:15.920> cryptographic<00:09:16.610> libraries<00:09:17.980> they 00:09:18.970 --> 00:09:18.980 align:start position:0% especially cryptographic libraries they 00:09:18.980 --> 00:09:21.040 align:start position:0% especially cryptographic libraries they already<00:09:19.250> in<00:09:19.700> see<00:09:20.000> they<00:09:20.210> have<00:09:20.420> been<00:09:20.630> tested 00:09:21.040 --> 00:09:21.050 align:start position:0% already in see they have been tested 00:09:21.050 --> 00:09:22.900 align:start position:0% already in see they have been tested they<00:09:21.230> are<00:09:21.350> working<00:09:21.560> and<00:09:21.980> if<00:09:22.250> we<00:09:22.340> can<00:09:22.460> just<00:09:22.490> take 00:09:22.900 --> 00:09:22.910 align:start position:0% they are working and if we can just take 00:09:22.910 --> 00:09:24.390 align:start position:0% they are working and if we can just take them<00:09:23.120> without<00:09:23.330> modification<00:09:24.050> that's<00:09:24.170> great 00:09:24.390 --> 00:09:24.400 align:start position:0% them without modification that's great 00:09:24.400 --> 00:09:28.030 align:start position:0% them without modification that's great the<00:09:25.400> advance<00:09:25.670> of<00:09:25.880> crypto<00:09:26.330> code<00:09:26.630> is<00:09:26.930> written<00:09:27.710> in 00:09:28.030 --> 00:09:28.040 align:start position:0% the advance of crypto code is written in 00:09:28.040 --> 00:09:32.580 align:start position:0% the advance of crypto code is written in C<00:09:28.340> and<00:09:28.370> well<00:09:29.260> long<00:09:30.260> since<00:09:30.650> well<00:09:30.890> tested 00:09:32.580 --> 00:09:32.590 align:start position:0% C and well long since well tested 00:09:32.590 --> 00:09:34.830 align:start position:0% C and well long since well tested that's<00:09:33.590> the<00:09:33.770> Assumption 00:09:34.830 --> 00:09:34.840 align:start position:0% that's the Assumption 00:09:34.840 --> 00:09:36.910 align:start position:0% that's the Assumption fits<00:09:35.840> the<00:09:36.050> assumption<00:09:36.470> that<00:09:36.500> they<00:09:36.710> well 00:09:36.910 --> 00:09:36.920 align:start position:0% fits the assumption that they well 00:09:36.920 --> 00:09:38.280 align:start position:0% fits the assumption that they well tested 00:09:38.280 --> 00:09:38.290 align:start position:0% tested 00:09:38.290 --> 00:09:40.650 align:start position:0% tested [Laughter] 00:09:40.650 --> 00:09:40.660 align:start position:0% [Laughter] 00:09:40.660 --> 00:09:45.420 align:start position:0% [Laughter] it's<00:09:41.660> not<00:09:41.840> always<00:09:42.140> a<00:09:42.410> good<00:09:42.650> assumption 00:09:45.420 --> 00:09:45.430 align:start position:0% 00:09:45.430 --> 00:09:49.090 align:start position:0% when<00:09:46.430> when<00:09:46.940> people<00:09:47.360> complain<00:09:47.810> about<00:09:48.320> solidity 00:09:49.090 --> 00:09:49.100 align:start position:0% when when people complain about solidity 00:09:49.100 --> 00:09:52.030 align:start position:0% when when people complain about solidity being<00:09:49.490> too<00:09:49.760> hard<00:09:50.060> though<00:09:50.420> I<00:09:50.480> I<00:09:50.960> point<00:09:51.830> out<00:09:51.980> that 00:09:52.030 --> 00:09:52.040 align:start position:0% being too hard though I I point out that 00:09:52.040 --> 00:09:54.580 align:start position:0% being too hard though I I point out that most<00:09:52.580> of<00:09:52.880> the<00:09:53.000> world's<00:09:53.450> most<00:09:53.780> reliable 00:09:54.580 --> 00:09:54.590 align:start position:0% most of the world's most reliable 00:09:54.590 --> 00:10:00.210 align:start position:0% most of the world's most reliable software<00:09:54.890> has<00:09:55.670> been<00:09:55.910> engineered<00:09:56.210> in<00:09:56.630> see 00:10:00.210 --> 00:10:00.220 align:start position:0% 00:10:00.220 --> 00:10:03.990 align:start position:0% most<00:10:01.220> of<00:10:01.400> your<00:10:01.550> paychecks<00:10:02.180> probably<00:10:02.930> are 00:10:03.990 --> 00:10:04.000 align:start position:0% most of your paychecks probably are 00:10:04.000 --> 00:10:06.880 align:start position:0% most of your paychecks probably are come<00:10:05.000> out<00:10:05.180> of<00:10:05.300> an<00:10:05.420> oracle<00:10:05.930> system<00:10:06.470> which<00:10:06.680> was 00:10:06.880 --> 00:10:06.890 align:start position:0% come out of an oracle system which was 00:10:06.890 --> 00:10:08.340 align:start position:0% come out of an oracle system which was written<00:10:07.100> in<00:10:07.370> C 00:10:08.340 --> 00:10:08.350 align:start position:0% written in C 00:10:08.350 --> 00:10:11.380 align:start position:0% written in C so<00:10:09.350> that<00:10:09.590> it<00:10:09.710> in<00:10:10.100> the<00:10:10.310> end<00:10:10.490> it<00:10:10.700> comes<00:10:10.880> down<00:10:11.060> to 00:10:11.380 --> 00:10:11.390 align:start position:0% so that it in the end it comes down to 00:10:11.390 --> 00:10:12.970 align:start position:0% so that it in the end it comes down to engineering<00:10:11.660> discipline<00:10:12.590> more<00:10:12.800> than 00:10:12.970 --> 00:10:12.980 align:start position:0% engineering discipline more than 00:10:12.980 --> 00:10:17.070 align:start position:0% engineering discipline more than anything 00:10:17.070 --> 00:10:17.080 align:start position:0% 00:10:17.080 --> 00:10:21.780 align:start position:0% so<00:10:18.080> I<00:10:18.470> really<00:10:19.250> think<00:10:19.490> the 00:10:21.780 --> 00:10:21.790 align:start position:0% so I really think the 00:10:21.790 --> 00:10:23.310 align:start position:0% so I really think the GVMC 00:10:23.310 --> 00:10:23.320 align:start position:0% GVMC 00:10:23.320 --> 00:10:26.470 align:start position:0% GVMC interfaces<00:10:24.320> is<00:10:24.830> really<00:10:25.370> a<00:10:25.400> powerful<00:10:25.670> idea 00:10:26.470 --> 00:10:26.480 align:start position:0% interfaces is really a powerful idea 00:10:26.480 --> 00:10:28.780 align:start position:0% interfaces is really a powerful idea that's<00:10:26.840> going<00:10:27.110> to<00:10:27.230> help<00:10:27.350> us<00:10:27.620> quite<00:10:27.980> a<00:10:28.010> lot<00:10:28.400> in 00:10:28.780 --> 00:10:28.790 align:start position:0% that's going to help us quite a lot in 00:10:28.790 --> 00:10:32.980 align:start position:0% that's going to help us quite a lot in pulling<00:10:29.780> together<00:10:30.110> the<00:10:30.860> different<00:10:31.640> work<00:10:32.150> they 00:10:32.980 --> 00:10:32.990 align:start position:0% pulling together the different work they 00:10:32.990 --> 00:10:33.930 align:start position:0% pulling together the different work they are 00:10:33.930 --> 00:10:33.940 align:start position:0% are 00:10:33.940 --> 00:10:36.370 align:start position:0% are providing<00:10:34.940> the<00:10:35.090> diversity<00:10:35.840> we've<00:10:36.050> talked 00:10:36.370 --> 00:10:36.380 align:start position:0% providing the diversity we've talked 00:10:36.380 --> 00:10:37.200 align:start position:0% providing the diversity we've talked about 00:10:37.200 --> 00:10:37.210 align:start position:0% about 00:10:37.210 --> 00:10:39.240 align:start position:0% about without 00:10:39.240 --> 00:10:39.250 align:start position:0% without 00:10:39.250 --> 00:10:42.940 align:start position:0% without ball<00:10:40.250> speak<00:10:40.640> up<00:10:40.850> Fred<00:10:41.090> without<00:10:42.080> vulcanizing 00:10:42.940 --> 00:10:42.950 align:start position:0% ball speak up Fred without vulcanizing 00:10:42.950 --> 00:10:46.500 align:start position:0% ball speak up Fred without vulcanizing the<00:10:43.370> work<00:10:43.910> we<00:10:44.090> can<00:10:44.270> have<00:10:44.450> a<00:10:44.480> diverse<00:10:45.020> number<00:10:45.160> of 00:10:46.500 --> 00:10:46.510 align:start position:0% the work we can have a diverse number of 00:10:46.510 --> 00:10:49.720 align:start position:0% the work we can have a diverse number of implementations<00:10:47.510> of<00:10:47.690> etherium<00:10:48.440> without<00:10:49.430> them 00:10:49.720 --> 00:10:49.730 align:start position:0% implementations of etherium without them 00:10:49.730 --> 00:10:52.930 align:start position:0% implementations of etherium without them being<00:10:49.940> in<00:10:50.540> separate<00:10:51.380> silos<00:10:51.710> that<00:10:52.010> can't<00:10:52.670> run 00:10:52.930 --> 00:10:52.940 align:start position:0% being in separate silos that can't run 00:10:52.940 --> 00:10:56.640 align:start position:0% being in separate silos that can't run together<00:10:53.180> they<00:10:53.780> can't<00:10:54.050> talk<00:10:54.290> to<00:10:54.500> each<00:10:54.650> other 00:10:56.640 --> 00:10:56.650 align:start position:0% together they can't talk to each other 00:10:56.650 --> 00:11:00.010 align:start position:0% together they can't talk to each other so<00:10:57.650> I<00:10:57.710> think<00:10:57.890> you<00:10:58.250> can<00:10:58.460> even<00:10:59.300> do<00:10:59.540> more<00:10:59.750> about 00:11:00.010 --> 00:11:00.020 align:start position:0% so I think you can even do more about 00:11:00.020 --> 00:11:02.590 align:start position:0% so I think you can even do more about that<00:11:00.230> like<00:11:00.700> having<00:11:01.700> multiple 00:11:02.590 --> 00:11:02.600 align:start position:0% that like having multiple 00:11:02.600 --> 00:11:05.560 align:start position:0% that like having multiple implementations<00:11:02.930> of<00:11:03.650> vm<00:11:04.160> itself<00:11:04.700> you<00:11:05.360> can 00:11:05.560 --> 00:11:05.570 align:start position:0% implementations of vm itself you can 00:11:05.570 --> 00:11:08.280 align:start position:0% implementations of vm itself you can build<00:11:05.780> a<00:11:06.640> quite 00:11:08.280 --> 00:11:08.290 align:start position:0% build a quite 00:11:08.290 --> 00:11:11.680 align:start position:0% build a quite complex<00:11:09.290> structure<00:11:09.800> of<00:11:10.190> that<00:11:10.250> I<00:11:10.760> mean<00:11:11.270> you<00:11:11.450> can 00:11:11.680 --> 00:11:11.690 align:start position:0% complex structure of that I mean you can 00:11:11.690 --> 00:11:15.430 align:start position:0% complex structure of that I mean you can decide<00:11:12.560> up<00:11:12.860> front<00:11:13.250> which<00:11:14.320> implementation<00:11:15.320> you 00:11:15.430 --> 00:11:15.440 align:start position:0% decide up front which implementation you 00:11:15.440 --> 00:11:19.270 align:start position:0% decide up front which implementation you want<00:11:15.650> to<00:11:16.300> use<00:11:17.300> for<00:11:17.750> this<00:11:17.960> particular<00:11:18.620> code<00:11:18.920> or 00:11:19.270 --> 00:11:19.280 align:start position:0% want to use for this particular code or 00:11:19.280 --> 00:11:22.120 align:start position:0% want to use for this particular code or just<00:11:20.090> select<00:11:20.780> the<00:11:20.840> randomly<00:11:21.380> to<00:11:21.800> avoid<00:11:22.100> any 00:11:22.120 --> 00:11:22.130 align:start position:0% just select the randomly to avoid any 00:11:22.130 --> 00:11:24.390 align:start position:0% just select the randomly to avoid any any<00:11:22.820> crashes 00:11:24.390 --> 00:11:24.400 align:start position:0% any crashes 00:11:24.400 --> 00:11:26.310 align:start position:0% any crashes how's<00:11:25.400> that 00:11:26.310 --> 00:11:26.320 align:start position:0% how's that 00:11:26.320 --> 00:11:30.190 align:start position:0% how's that you<00:11:27.320> can<00:11:27.530> implement<00:11:27.680> like<00:11:28.400> some<00:11:29.210> kind<00:11:29.450> of<00:11:29.630> vm 00:11:30.190 --> 00:11:30.200 align:start position:0% you can implement like some kind of vm 00:11:30.200 --> 00:11:33.250 align:start position:0% you can implement like some kind of vm that<00:11:30.560> actually<00:11:31.600> composites<00:11:32.600> other<00:11:32.840> vm<00:11:33.230> and 00:11:33.250 --> 00:11:33.260 align:start position:0% that actually composites other vm and 00:11:33.260 --> 00:11:35.640 align:start position:0% that actually composites other vm and behind<00:11:34.250> it 00:11:35.640 --> 00:11:35.650 align:start position:0% behind it 00:11:35.650 --> 00:11:39.790 align:start position:0% behind it so<00:11:36.650> is<00:11:37.340> it<00:11:37.550> going<00:11:37.970> to<00:11:38.060> be<00:11:38.180> part<00:11:38.570> of<00:11:38.780> the<00:11:39.140> vmc 00:11:39.790 --> 00:11:39.800 align:start position:0% so is it going to be part of the vmc 00:11:39.800 --> 00:11:43.720 align:start position:0% so is it going to be part of the vmc interface<00:11:40.520> or<00:11:41.030> the<00:11:41.780> higher<00:11:42.080> level<00:11:42.920> that<00:11:43.670> you 00:11:43.720 --> 00:11:43.730 align:start position:0% interface or the higher level that you 00:11:43.730 --> 00:11:45.910 align:start position:0% interface or the higher level that you do<00:11:44.090> things<00:11:44.450> like<00:11:44.780> start<00:11:45.260> out<00:11:45.500> with<00:11:45.740> an 00:11:45.910 --> 00:11:45.920 align:start position:0% do things like start out with an 00:11:45.920 --> 00:11:47.830 align:start position:0% do things like start out with an interpreter<00:11:46.640> no<00:11:46.880> you<00:11:46.940> can<00:11:47.270> use<00:11:47.420> the<00:11:47.600> same 00:11:47.830 --> 00:11:47.840 align:start position:0% interpreter no you can use the same 00:11:47.840 --> 00:11:50.410 align:start position:0% interpreter no you can use the same interface<00:11:48.320> for<00:11:48.710> higher<00:11:49.040> level<00:11:49.520> like<00:11:49.820> you<00:11:50.210> can 00:11:50.410 --> 00:11:50.420 align:start position:0% interface for higher level like you can 00:11:50.420 --> 00:11:51.780 align:start position:0% interface for higher level like you can write<00:11:51.080> a 00:11:51.780 --> 00:11:51.790 align:start position:0% write a 00:11:51.790 --> 00:11:57.120 align:start position:0% write a vm<00:11:52.790> that<00:11:53.360> compose<00:11:54.110> other<00:11:54.470> VMS<00:11:54.890> but<00:11:55.550> still<00:11:55.970> X 00:11:57.120 --> 00:11:57.130 align:start position:0% vm that compose other VMS but still X 00:11:57.130 --> 00:12:01.950 align:start position:0% vm that compose other VMS but still X exports<00:11:58.130> the<00:11:58.310> same<00:11:58.580> interface<00:11:59.120> vmc<00:12:00.400> no<00:12:01.400> I<00:12:01.430> mean 00:12:01.950 --> 00:12:01.960 align:start position:0% exports the same interface vmc no I mean 00:12:01.960 --> 00:12:05.020 align:start position:0% exports the same interface vmc no I mean by<00:12:02.960> typically<00:12:03.620> you<00:12:03.860> start<00:12:04.250> out<00:12:04.460> running<00:12:04.940> an 00:12:05.020 --> 00:12:05.030 align:start position:0% by typically you start out running an 00:12:05.030 --> 00:12:08.800 align:start position:0% by typically you start out running an interpreter<00:12:05.810> you<00:12:06.410> notice<00:12:06.830> the<00:12:07.040> hot<00:12:07.250> spots<00:12:07.810> you 00:12:08.800 --> 00:12:08.810 align:start position:0% interpreter you notice the hot spots you 00:12:08.810 --> 00:12:11.740 align:start position:0% interpreter you notice the hot spots you had<00:12:09.050> pad<00:12:09.350> you<00:12:09.770> hand<00:12:10.040> those<00:12:10.310> up<00:12:10.640> to<00:12:10.940> a<00:12:10.970> jit<00:12:11.420> for 00:12:11.740 --> 00:12:11.750 align:start position:0% had pad you hand those up to a jit for 00:12:11.750 --> 00:12:13.890 align:start position:0% had pad you hand those up to a jit for faster<00:12:12.230> execution 00:12:13.890 --> 00:12:13.900 align:start position:0% faster execution 00:12:13.900 --> 00:12:17.290 align:start position:0% faster execution you<00:12:14.900> may<00:12:15.170> do<00:12:15.530> the<00:12:15.580> compilation<00:12:16.580> on<00:12:16.730> a<00:12:16.760> separate 00:12:17.290 --> 00:12:17.300 align:start position:0% you may do the compilation on a separate 00:12:17.300 --> 00:12:19.140 align:start position:0% you may do the compilation on a separate thread<00:12:17.570> because<00:12:18.020> it<00:12:18.230> could<00:12:18.410> take<00:12:18.590> a<00:12:18.650> while 00:12:19.140 --> 00:12:19.150 align:start position:0% thread because it could take a while 00:12:19.150 --> 00:12:22.300 align:start position:0% thread because it could take a while yeah<00:12:20.150> it's<00:12:20.600> that<00:12:20.690> part<00:12:21.200> of<00:12:21.350> the<00:12:21.470> interface<00:12:21.920> or 00:12:22.300 --> 00:12:22.310 align:start position:0% yeah it's that part of the interface or 00:12:22.310 --> 00:12:25.199 align:start position:0% yeah it's that part of the interface or will<00:12:22.490> that<00:12:22.640> be<00:12:23.110> a<00:12:23.140> lot<00:12:23.760> it's<00:12:24.760> all<00:12:24.970> possible 00:12:25.199 --> 00:12:25.209 align:start position:0% will that be a lot it's all possible 00:12:25.209 --> 00:12:28.519 align:start position:0% will that be a lot it's all possible with<00:12:25.690> with<00:12:26.079> this<00:12:26.320> vmc<00:12:27.220> interface 00:12:28.519 --> 00:12:28.529 align:start position:0% with with this vmc interface 00:12:28.529 --> 00:12:32.540 align:start position:0% with with this vmc interface okay 00:12:32.540 --> 00:12:32.550 align:start position:0% 00:12:32.550 --> 00:12:35.670 align:start position:0% so<00:12:33.550> basically<00:12:33.880> the<00:12:34.420> interface<00:12:34.959> only<00:12:35.290> defines 00:12:35.670 --> 00:12:35.680 align:start position:0% so basically the interface only defines 00:12:35.680 --> 00:12:39.240 align:start position:0% so basically the interface only defines the<00:12:36.430> entry<00:12:36.670> points<00:12:37.120> and<00:12:37.300> the<00:12:37.959> way<00:12:38.140> the<00:12:38.709> VMS<00:12:39.070> can 00:12:39.240 --> 00:12:39.250 align:start position:0% the entry points and the way the VMS can 00:12:39.250 --> 00:12:41.150 align:start position:0% the entry points and the way the VMS can ask<00:12:39.370> for<00:12:39.490> data<00:12:39.820> from<00:12:40.120> the<00:12:40.240> block<00:12:40.420> chain<00:12:40.450> and 00:12:41.150 --> 00:12:41.160 align:start position:0% ask for data from the block chain and 00:12:41.160 --> 00:12:43.500 align:start position:0% ask for data from the block chain and that's<00:12:42.160> very<00:12:42.310> generic<00:12:42.850> and<00:12:43.060> it<00:12:43.149> only<00:12:43.269> gives 00:12:43.500 --> 00:12:43.510 align:start position:0% that's very generic and it only gives 00:12:43.510 --> 00:12:45.060 align:start position:0% that's very generic and it only gives you<00:12:43.660> the<00:12:43.750> bare<00:12:43.899> minimum<00:12:44.170> you<00:12:44.350> need<00:12:44.500> and 00:12:45.060 --> 00:12:45.070 align:start position:0% you the bare minimum you need and 00:12:45.070 --> 00:12:47.420 align:start position:0% you the bare minimum you need and because<00:12:45.970> of<00:12:46.000> that<00:12:46.120> you<00:12:46.300> can<00:12:46.570> compose<00:12:47.050> and 00:12:47.420 --> 00:12:47.430 align:start position:0% because of that you can compose and 00:12:47.430 --> 00:12:50.400 align:start position:0% because of that you can compose and multiple<00:12:48.430> levels<00:12:48.730> if<00:12:48.850> you<00:12:49.000> wanted<00:12:49.390> so<00:12:50.290> the 00:12:50.400 --> 00:12:50.410 align:start position:0% multiple levels if you wanted so the 00:12:50.410 --> 00:12:54.769 align:start position:0% multiple levels if you wanted so the composition<00:12:51.310> would<00:12:51.490> be<00:12:51.700> at<00:12:52.089> another<00:12:52.480> level<00:12:52.810> if 00:12:54.769 --> 00:12:54.779 align:start position:0% composition would be at another level if 00:12:54.779 --> 00:12:58.050 align:start position:0% composition would be at another level if we<00:12:55.779> wanted<00:12:56.230> to<00:12:56.350> we<00:12:56.529> could<00:12:56.800> abstract<00:12:57.519> that<00:12:57.760> but 00:12:58.050 --> 00:12:58.060 align:start position:0% we wanted to we could abstract that but 00:12:58.060 --> 00:13:00.090 align:start position:0% we wanted to we could abstract that but we<00:12:58.180> haven't<00:12:58.390> yet<00:12:58.720> now<00:12:59.440> it<00:12:59.589> works<00:12:59.800> on<00:12:59.980> the<00:13:00.070> same 00:13:00.090 --> 00:13:00.100 align:start position:0% we haven't yet now it works on the same 00:13:00.100 --> 00:13:03.690 align:start position:0% we haven't yet now it works on the same I<00:13:00.959> works<00:13:01.959> on<00:13:02.110> the<00:13:02.170> same<00:13:02.230> level<00:13:02.350> as<00:13:03.310> basically 00:13:03.690 --> 00:13:03.700 align:start position:0% I works on the same level as basically 00:13:03.700 --> 00:13:05.610 align:start position:0% I works on the same level as basically you<00:13:03.790> just<00:13:03.850> get<00:13:04.120> in<00:13:04.269> the<00:13:04.510> the<00:13:04.779> contract<00:13:05.529> to 00:13:05.610 --> 00:13:05.620 align:start position:0% you just get in the the contract to 00:13:05.620 --> 00:13:08.550 align:start position:0% you just get in the the contract to execute<00:13:06.130> and<00:13:06.570> then<00:13:07.570> you<00:13:07.839> can<00:13:08.019> initially<00:13:08.290> run 00:13:08.550 --> 00:13:08.560 align:start position:0% execute and then you can initially run 00:13:08.560 --> 00:13:10.319 align:start position:0% execute and then you can initially run it<00:13:08.709> as<00:13:08.829> an<00:13:08.950> interpreter<00:13:09.339> if<00:13:09.640> you<00:13:09.760> wanted<00:13:10.120> and 00:13:10.319 --> 00:13:10.329 align:start position:0% it as an interpreter if you wanted and 00:13:10.329 --> 00:13:14.420 align:start position:0% it as an interpreter if you wanted and you<00:13:10.360> can<00:13:11.140> change<00:13:11.350> it<00:13:11.470> over<00:13:11.560> right<00:13:12.399> all<00:13:12.910> right 00:13:14.420 --> 00:13:14.430 align:start position:0% you can change it over right all right 00:13:14.430 --> 00:13:17.610 align:start position:0% you can change it over right all right so<00:13:15.430> what's<00:13:15.700> the<00:13:16.000> what's<00:13:16.420> the<00:13:16.540> timing<00:13:16.959> on<00:13:17.320> this 00:13:17.610 --> 00:13:17.620 align:start position:0% so what's the what's the timing on this 00:13:17.620 --> 00:13:20.970 align:start position:0% so what's the what's the timing on this I'm<00:13:18.310> always<00:13:18.579> asking<00:13:19.329> that's<00:13:19.750> always<00:13:20.170> fuzzy 00:13:20.970 --> 00:13:20.980 align:start position:0% I'm always asking that's always fuzzy 00:13:20.980 --> 00:13:25.069 align:start position:0% I'm always asking that's always fuzzy and<00:13:21.190> changing<00:13:21.870> yeah<00:13:22.870> so<00:13:23.500> for<00:13:23.890> web<00:13:24.519> assembly 00:13:25.069 --> 00:13:25.079 align:start position:0% and changing yeah so for web assembly 00:13:25.079 --> 00:13:28.310 align:start position:0% and changing yeah so for web assembly pacifically<00:13:26.079> it<00:13:26.709> depends<00:13:27.339> on<00:13:27.490> the<00:13:27.550> wc3 00:13:28.310 --> 00:13:28.320 align:start position:0% pacifically it depends on the wc3 00:13:28.320 --> 00:13:32.009 align:start position:0% pacifically it depends on the wc3 working<00:13:29.320> group<00:13:29.529> but<00:13:30.060> as<00:13:31.060> it<00:13:31.329> stands<00:13:31.510> now<00:13:31.630> it's 00:13:32.009 --> 00:13:32.019 align:start position:0% working group but as it stands now it's 00:13:32.019 --> 00:13:34.110 align:start position:0% working group but as it stands now it's implemented<00:13:32.589> in<00:13:32.800> all<00:13:32.980> the<00:13:33.100> major<00:13:33.220> browsers 00:13:34.110 --> 00:13:34.120 align:start position:0% implemented in all the major browsers 00:13:34.120 --> 00:13:36.290 align:start position:0% implemented in all the major browsers and<00:13:34.630> it's<00:13:34.839> on<00:13:34.990> the 00:13:36.290 --> 00:13:36.300 align:start position:0% and it's on the 00:13:36.300 --> 00:13:39.590 align:start position:0% and it's on the twelfth<00:13:37.589> refreshing 00:13:39.590 --> 00:13:39.600 align:start position:0% twelfth refreshing 00:13:39.600 --> 00:13:41.819 align:start position:0% twelfth refreshing prototype<00:13:40.600> so<00:13:40.959> I<00:13:41.199> think<00:13:41.320> it's<00:13:41.529> getting<00:13:41.649> pretty 00:13:41.819 --> 00:13:41.829 align:start position:0% prototype so I think it's getting pretty 00:13:41.829 --> 00:13:45.259 align:start position:0% prototype so I think it's getting pretty close<00:13:42.070> I<00:13:42.370> would<00:13:42.490> expect<00:13:42.760> it<00:13:42.970> in<00:13:43.320> 2017 00:13:45.259 --> 00:13:45.269 align:start position:0% close I would expect it in 2017 00:13:45.269 --> 00:13:49.079 align:start position:0% close I would expect it in 2017 to<00:13:46.269> finalize<00:13:46.660> the<00:13:47.019> spec<00:13:47.370> after<00:13:48.370> that<00:13:48.550> then<00:13:48.910> we 00:13:49.079 --> 00:13:49.089 align:start position:0% to finalize the spec after that then we 00:13:49.089 --> 00:13:53.000 align:start position:0% to finalize the spec after that then we can<00:13:49.120> move<00:13:49.390> on<00:13:49.660> to<00:13:50.610> finalizing<00:13:51.610> our<00:13:51.730> eat 00:13:53.000 --> 00:13:53.010 align:start position:0% can move on to finalizing our eat 00:13:53.010 --> 00:13:56.819 align:start position:0% can move on to finalizing our eat as<00:13:54.010> we<00:13:54.220> stand<00:13:54.459> with<00:13:54.790> a<00:13:54.850> prototype<00:13:55.420> we<00:13:56.260> we<00:13:56.649> have 00:13:56.819 --> 00:13:56.829 align:start position:0% as we stand with a prototype we we have 00:13:56.829 --> 00:13:59.990 align:start position:0% as we stand with a prototype we we have most<00:13:57.490> the<00:13:57.640> major<00:13:57.790> components<00:13:58.510> implemented 00:13:59.990 --> 00:14:00.000 align:start position:0% most the major components implemented 00:14:00.000 --> 00:14:01.949 align:start position:0% most the major components implemented next<00:14:01.000> big<00:14:01.180> thing<00:14:01.360> we're<00:14:01.449> going<00:14:01.540> to<00:14:01.600> be<00:14:01.779> pushing 00:14:01.949 --> 00:14:01.959 align:start position:0% next big thing we're going to be pushing 00:14:01.959 --> 00:14:04.590 align:start position:0% next big thing we're going to be pushing out<00:14:02.170> as<00:14:02.290> a<00:14:02.350> test<00:14:02.560> Network<00:14:02.970> once<00:14:03.970> again<00:14:04.089> brought 00:14:04.590 --> 00:14:04.600 align:start position:0% out as a test Network once again brought 00:14:04.600 --> 00:14:09.900 align:start position:0% out as a test Network once again brought to<00:14:04.810> to<00:14:05.620> us<00:14:05.769> by<00:14:06.360> facilitated<00:14:07.360> by<00:14:07.390> a<00:14:07.829> PMC<00:14:08.910> since 00:14:09.900 --> 00:14:09.910 align:start position:0% to to us by facilitated by a PMC since 00:14:09.910 --> 00:14:12.630 align:start position:0% to to us by facilitated by a PMC since we<00:14:10.060> can<00:14:10.209> just<00:14:10.449> drop<00:14:11.050> the<00:14:11.290> wazoo<00:14:11.500> the<00:14:12.160> woz<00:14:12.370> some 00:14:12.630 --> 00:14:12.640 align:start position:0% we can just drop the wazoo the woz some 00:14:12.640 --> 00:14:15.420 align:start position:0% we can just drop the wazoo the woz some chitter<00:14:13.449> interpreter<00:14:14.230> into<00:14:14.680> all<00:14:15.130> the<00:14:15.310> other 00:14:15.420 --> 00:14:15.430 align:start position:0% chitter interpreter into all the other 00:14:15.430 --> 00:14:19.470 align:start position:0% chitter interpreter into all the other clients<00:14:16.170> yeah<00:14:17.170> so<00:14:17.620> that's<00:14:17.769> pretty<00:14:17.949> cool<00:14:18.480> it's 00:14:19.470 --> 00:14:19.480 align:start position:0% clients yeah so that's pretty cool it's 00:14:19.480 --> 00:14:20.449 align:start position:0% clients yeah so that's pretty cool it's great<00:14:19.660> fun 00:14:20.449 --> 00:14:20.459 align:start position:0% great fun 00:14:20.459 --> 00:14:23.580 align:start position:0% great fun if<00:14:21.459> we<00:14:21.579> used<00:14:21.820> up<00:14:22.000> our<00:14:22.120> 20<00:14:22.420> minutes<00:14:22.750> yet 00:14:23.580 --> 00:14:23.590 align:start position:0% if we used up our 20 minutes yet 00:14:23.590 --> 00:14:27.610 align:start position:0% if we used up our 20 minutes yet you<00:14:24.590> have<00:14:24.860> six<00:14:25.610> minutes<00:14:25.760> left<00:14:26.390> six<00:14:27.350> whole 00:14:27.610 --> 00:14:27.620 align:start position:0% you have six minutes left six whole 00:14:27.620 --> 00:14:29.830 align:start position:0% you have six minutes left six whole minutes<00:14:27.800> and<00:14:28.520> I<00:14:28.580> have<00:14:28.700> a<00:14:28.730> question<00:14:28.880> um<00:14:29.450> I 00:14:29.830 --> 00:14:29.840 align:start position:0% minutes and I have a question um I 00:14:29.840 --> 00:14:31.720 align:start position:0% minutes and I have a question um I cannot<00:14:30.230> see<00:14:30.560> anything<00:14:30.590> but<00:14:31.400> the<00:14:31.580> most 00:14:31.720 --> 00:14:31.730 align:start position:0% cannot see anything but the most 00:14:31.730 --> 00:14:34.420 align:start position:0% cannot see anything but the most blinding<00:14:32.540> white<00:14:32.990> lights<00:14:33.410> I've<00:14:33.800> ever<00:14:33.980> seen<00:14:34.250> in 00:14:34.420 --> 00:14:34.430 align:start position:0% blinding white lights I've ever seen in 00:14:34.430 --> 00:14:36.450 align:start position:0% blinding white lights I've ever seen in my<00:14:34.460> life 00:14:36.450 --> 00:14:36.460 align:start position:0% my life 00:14:36.460 --> 00:14:38.530 align:start position:0% my life did<00:14:37.460> you<00:14:37.610> want<00:14:37.790> to<00:14:37.910> let<00:14:38.030> you<00:14:38.210> know<00:14:38.240> about 00:14:38.530 --> 00:14:38.540 align:start position:0% did you want to let you know about 00:14:38.540 --> 00:14:43.270 align:start position:0% did you want to let you know about security<00:14:39.530> Christian<00:14:40.060> so<00:14:41.060> the<00:14:41.980> the<00:14:42.980> original 00:14:43.270 --> 00:14:43.280 align:start position:0% security Christian so the the original 00:14:43.280 --> 00:14:46.140 align:start position:0% security Christian so the the original EVM<00:14:43.610> was<00:14:43.910> designed<00:14:44.540> from<00:14:44.660> the<00:14:44.810> ground<00:14:44.840> up<00:14:45.140> to 00:14:46.140 --> 00:14:46.150 align:start position:0% EVM was designed from the ground up to 00:14:46.150 --> 00:14:49.240 align:start position:0% EVM was designed from the ground up to have<00:14:47.150> fixed<00:14:48.020> bounds<00:14:48.620> on<00:14:48.770> resource 00:14:49.240 --> 00:14:49.250 align:start position:0% have fixed bounds on resource 00:14:49.250 --> 00:14:52.000 align:start position:0% have fixed bounds on resource consumption<00:14:49.640> and<00:14:50.200> these<00:14:51.200> bounds<00:14:51.860> should 00:14:52.000 --> 00:14:52.010 align:start position:0% consumption and these bounds should 00:14:52.010 --> 00:14:54.670 align:start position:0% consumption and these bounds should coincide<00:14:52.250> with<00:14:52.460> the<00:14:52.610> gas<00:14:52.790> usage<00:14:53.500> what<00:14:54.500> do<00:14:54.620> we 00:14:54.670 --> 00:14:54.680 align:start position:0% coincide with the gas usage what do we 00:14:54.680 --> 00:14:56.830 align:start position:0% coincide with the gas usage what do we know<00:14:54.740> about<00:14:55.150> existing<00:14:56.150> he<00:14:56.420> wasn't 00:14:56.830 --> 00:14:56.840 align:start position:0% know about existing he wasn't 00:14:56.840 --> 00:14:59.410 align:start position:0% know about existing he wasn't implementations<00:14:57.530> in<00:14:57.860> that<00:14:57.980> regard<00:14:58.340> okay<00:14:59.270> Oh 00:14:59.410 --> 00:14:59.420 align:start position:0% implementations in that regard okay Oh 00:14:59.420 --> 00:15:02.200 align:start position:0% implementations in that regard okay Oh so<00:15:00.200> regarding<00:15:00.890> security<00:15:01.100> in<00:15:01.700> the<00:15:02.030> virtual 00:15:02.200 --> 00:15:02.210 align:start position:0% so regarding security in the virtual 00:15:02.210 --> 00:15:04.210 align:start position:0% so regarding security in the virtual machine<00:15:02.510> I<00:15:03.020> think<00:15:03.350> like<00:15:03.560> the<00:15:03.890> number<00:15:04.190> one 00:15:04.210 --> 00:15:04.220 align:start position:0% machine I think like the number one 00:15:04.220 --> 00:15:06.730 align:start position:0% machine I think like the number one biggest<00:15:04.760> security<00:15:05.300> issue<00:15:05.630> though<00:15:06.020> is<00:15:06.260> the 00:15:06.730 --> 00:15:06.740 align:start position:0% biggest security issue though is the 00:15:06.740 --> 00:15:09.670 align:start position:0% biggest security issue though is the trusted<00:15:07.160> computing<00:15:07.520> base<00:15:07.910> and<00:15:08.680> that's 00:15:09.670 --> 00:15:09.680 align:start position:0% trusted computing base and that's 00:15:09.680 --> 00:15:11.560 align:start position:0% trusted computing base and that's continually<00:15:10.310> expanding<00:15:11.030> with<00:15:11.210> every 00:15:11.560 --> 00:15:11.570 align:start position:0% continually expanding with every 00:15:11.570 --> 00:15:15.570 align:start position:0% continually expanding with every precompiled<00:15:12.530> that<00:15:12.710> we<00:15:13.040> add<00:15:13.480> so<00:15:14.480> the<00:15:14.990> point<00:15:15.020> of 00:15:15.570 --> 00:15:15.580 align:start position:0% precompiled that we add so the point of 00:15:15.580 --> 00:15:18.490 align:start position:0% precompiled that we add so the point of web<00:15:16.580> assembly<00:15:17.120> from<00:15:17.450> a<00:15:17.600> security<00:15:17.990> perspective 00:15:18.490 --> 00:15:18.500 align:start position:0% web assembly from a security perspective 00:15:18.500 --> 00:15:21.790 align:start position:0% web assembly from a security perspective and<00:15:19.250> it<00:15:19.550> is<00:15:19.700> when<00:15:19.910> Katie's<00:15:20.330> perspective<00:15:21.050> is<00:15:21.410> to 00:15:21.790 --> 00:15:21.800 align:start position:0% and it is when Katie's perspective is to 00:15:21.800 --> 00:15:24.190 align:start position:0% and it is when Katie's perspective is to minimize<00:15:22.280> the<00:15:23.000> overall<00:15:23.060> trusted<00:15:23.870> computing 00:15:24.190 --> 00:15:24.200 align:start position:0% minimize the overall trusted computing 00:15:24.200 --> 00:15:25.320 align:start position:0% minimize the overall trusted computing base 00:15:25.320 --> 00:15:25.330 align:start position:0% base 00:15:25.330 --> 00:15:28.390 align:start position:0% base now<00:15:26.330> security<00:15:27.230> from<00:15:27.620> the<00:15:28.070> metering 00:15:28.390 --> 00:15:28.400 align:start position:0% now security from the metering 00:15:28.400 --> 00:15:32.350 align:start position:0% now security from the metering perspective<00:15:29.180> is<00:15:29.390> done<00:15:30.080> by<00:15:30.380> VM<00:15:31.130> tourism<00:15:31.820> or 00:15:32.350 --> 00:15:32.360 align:start position:0% perspective is done by VM tourism or 00:15:32.360 --> 00:15:36.130 align:start position:0% perspective is done by VM tourism or sorry<00:15:32.980> it's<00:15:33.980> done<00:15:34.250> by<00:15:34.400> metering<00:15:34.880> injection<00:15:35.480> so 00:15:36.130 --> 00:15:36.140 align:start position:0% sorry it's done by metering injection so 00:15:36.140 --> 00:15:39.010 align:start position:0% sorry it's done by metering injection so we<00:15:36.770> can<00:15:36.950> do<00:15:37.130> static<00:15:37.700> analysis<00:15:38.210> on<00:15:38.390> the<00:15:38.540> code<00:15:38.750> to 00:15:39.010 --> 00:15:39.020 align:start position:0% we can do static analysis on the code to 00:15:39.020 --> 00:15:43.000 align:start position:0% we can do static analysis on the code to find<00:15:39.400> it's<00:15:40.400> very<00:15:40.550> well<00:15:41.000> delineated<00:15:41.390> in<00:15:42.050> web 00:15:43.000 --> 00:15:43.010 align:start position:0% find it's very well delineated in web 00:15:43.010 --> 00:15:46.060 align:start position:0% find it's very well delineated in web assembly<00:15:43.490> flow<00:15:44.450> control<00:15:44.840> so<00:15:45.260> it's<00:15:45.470> easy<00:15:45.680> to<00:15:45.920> do 00:15:46.060 --> 00:15:46.070 align:start position:0% assembly flow control so it's easy to do 00:15:46.070 --> 00:15:48.490 align:start position:0% assembly flow control so it's easy to do static<00:15:46.490> analysis<00:15:46.730> on<00:15:47.330> the<00:15:47.420> flow<00:15:47.600> control<00:15:48.140> and 00:15:48.490 --> 00:15:48.500 align:start position:0% static analysis on the flow control and 00:15:48.500 --> 00:15:50.590 align:start position:0% static analysis on the flow control and inject<00:15:48.860> metering<00:15:49.340> statements<00:15:49.970> at<00:15:50.450> the 00:15:50.590 --> 00:15:50.600 align:start position:0% inject metering statements at the 00:15:50.600 --> 00:15:52.810 align:start position:0% inject metering statements at the beginning<00:15:51.020> of<00:15:51.350> each<00:15:51.530> branch<00:15:51.860> possible<00:15:52.640> branch 00:15:52.810 --> 00:15:52.820 align:start position:0% beginning of each branch possible branch 00:15:52.820 --> 00:15:55.900 align:start position:0% beginning of each branch possible branch condition<00:15:53.300> that<00:15:53.690> will<00:15:53.840> meet<00:15:54.020> her<00:15:54.140> in<00:15:54.700> the<00:15:55.700> same 00:15:55.900 --> 00:15:55.910 align:start position:0% condition that will meet her in the same 00:15:55.910 --> 00:15:59.880 align:start position:0% condition that will meet her in the same applies<00:15:56.300> to<00:15:56.570> memory<00:15:56.900> usage<00:15:57.170> so<00:15:58.100> it<00:15:58.550> provides<00:15:58.880> a 00:15:59.880 --> 00:15:59.890 align:start position:0% applies to memory usage so it provides a 00:15:59.890 --> 00:16:02.520 align:start position:0% applies to memory usage so it provides a so<00:16:00.890> the<00:16:01.400> the 00:16:02.520 --> 00:16:02.530 align:start position:0% so the the 00:16:02.530 --> 00:16:06.910 align:start position:0% so the the gas<00:16:03.530> model<00:16:03.980> and<00:16:04.220> the<00:16:05.030> memory<00:16:05.390> model<00:16:05.690> as<00:16:06.320> far<00:16:06.770> as 00:16:06.910 --> 00:16:06.920 align:start position:0% gas model and the memory model as far as 00:16:06.920 --> 00:16:08.470 align:start position:0% gas model and the memory model as far as metering<00:16:07.280> is<00:16:07.640> going<00:16:07.910> to<00:16:08.000> work<00:16:08.120> the<00:16:08.240> same<00:16:08.420> way 00:16:08.470 --> 00:16:08.480 align:start position:0% metering is going to work the same way 00:16:08.480 --> 00:16:12.370 align:start position:0% metering is going to work the same way with<00:16:09.470> at<00:16:09.680> a<00:16:09.710> benefit<00:16:10.280> that<00:16:10.970> it's<00:16:11.420> decoupled 00:16:12.370 --> 00:16:12.380 align:start position:0% with at a benefit that it's decoupled 00:16:12.380 --> 00:16:15.090 align:start position:0% with at a benefit that it's decoupled from<00:16:12.710> the<00:16:13.100> evm 00:16:15.090 --> 00:16:15.100 align:start position:0% from the evm 00:16:15.100 --> 00:16:18.730 align:start position:0% from the evm by<00:16:16.100> default<00:16:16.490> so<00:16:17.030> it's<00:16:17.210> not<00:16:17.360> we<00:16:18.320> have<00:16:18.470> a<00:16:18.500> nice 00:16:18.730 --> 00:16:18.740 align:start position:0% by default so it's not we have a nice 00:16:18.740 --> 00:16:20.540 align:start position:0% by default so it's not we have a nice separation<00:16:19.400> of<00:16:19.640> concerns 00:16:20.540 --> 00:16:20.550 align:start position:0% separation of concerns 00:16:20.550 --> 00:16:24.019 align:start position:0% separation of concerns and<00:16:21.470> I<00:16:22.470> think<00:16:22.800> that<00:16:23.070> also<00:16:23.220> provides<00:16:23.519> extra 00:16:24.019 --> 00:16:24.029 align:start position:0% and I think that also provides extra 00:16:24.029 --> 00:16:25.670 align:start position:0% and I think that also provides extra security<00:16:24.330> because<00:16:24.959> we<00:16:25.260> can<00:16:25.410> think<00:16:25.589> about 00:16:25.670 --> 00:16:25.680 align:start position:0% security because we can think about 00:16:25.680 --> 00:16:28.310 align:start position:0% security because we can think about these<00:16:26.010> two<00:16:26.190> components<00:16:26.600> separately<00:16:27.600> now<00:16:27.930> we 00:16:28.310 --> 00:16:28.320 align:start position:0% these two components separately now we 00:16:28.320 --> 00:16:30.170 align:start position:0% these two components separately now we can<00:16:28.500> think<00:16:28.680> about<00:16:28.769> okay<00:16:29.130> here<00:16:29.610> is<00:16:29.820> our 00:16:30.170 --> 00:16:30.180 align:start position:0% can think about okay here is our 00:16:30.180 --> 00:16:33.170 align:start position:0% can think about okay here is our metering<00:16:31.110> injection<00:16:31.649> algorithm<00:16:32.070> right<00:16:32.399> we 00:16:33.170 --> 00:16:33.180 align:start position:0% metering injection algorithm right we 00:16:33.180 --> 00:16:35.480 align:start position:0% metering injection algorithm right we can<00:16:33.269> examine<00:16:33.450> that<00:16:33.750> and<00:16:34.410> then<00:16:34.920> we<00:16:35.040> have<00:16:35.220> a 00:16:35.480 --> 00:16:35.490 align:start position:0% can examine that and then we have a 00:16:35.490 --> 00:16:37.340 align:start position:0% can examine that and then we have a separate<00:16:35.940> team<00:16:36.060> or<00:16:36.360> separate<00:16:36.630> module<00:16:37.050> all 00:16:37.340 --> 00:16:37.350 align:start position:0% separate team or separate module all 00:16:37.350 --> 00:16:39.620 align:start position:0% separate team or separate module all together<00:16:37.620> examining<00:16:38.519> and<00:16:38.880> looking<00:16:39.149> at<00:16:39.300> our 00:16:39.620 --> 00:16:39.630 align:start position:0% together examining and looking at our 00:16:39.630 --> 00:16:41.360 align:start position:0% together examining and looking at our trusted<00:16:39.959> computing<00:16:40.260> base<00:16:40.589> which<00:16:40.980> would<00:16:41.190> be 00:16:41.360 --> 00:16:41.370 align:start position:0% trusted computing base which would be 00:16:41.370 --> 00:16:45.009 align:start position:0% trusted computing base which would be the<00:16:41.760> awesome<00:16:42.570> TN<00:16:42.839> so<00:16:43.740> two<00:16:44.250> bolts<00:16:44.579> there 00:16:45.009 --> 00:16:45.019 align:start position:0% the awesome TN so two bolts there 00:16:45.019 --> 00:16:47.000 align:start position:0% the awesome TN so two bolts there minimizing<00:16:46.019> the<00:16:46.140> trusted<00:16:46.470> computing<00:16:46.709> base 00:16:47.000 --> 00:16:47.010 align:start position:0% minimizing the trusted computing base 00:16:47.010 --> 00:16:49.509 align:start position:0% minimizing the trusted computing base that<00:16:47.220> I<00:16:47.279> think<00:16:47.490> is<00:16:47.640> the<00:16:47.910> biggest 00:16:49.509 --> 00:16:49.519 align:start position:0% that I think is the biggest 00:16:49.519 --> 00:16:52.040 align:start position:0% that I think is the biggest lowest<00:16:50.519> hanging<00:16:50.670> fruit<00:16:50.850> most<00:16:51.600> bang<00:16:51.779> for<00:16:51.870> the 00:16:52.040 --> 00:16:52.050 align:start position:0% lowest hanging fruit most bang for the 00:16:52.050 --> 00:16:54.350 align:start position:0% lowest hanging fruit most bang for the buck<00:16:52.079> right<00:16:52.709> as<00:16:53.070> far<00:16:53.250> as<00:16:53.430> increasing<00:16:54.000> security 00:16:54.350 --> 00:16:54.360 align:start position:0% buck right as far as increasing security 00:16:54.360 --> 00:16:56.230 align:start position:0% buck right as far as increasing security in<00:16:54.720> our<00:16:54.810> network 00:16:56.230 --> 00:16:56.240 align:start position:0% in our network 00:16:56.240 --> 00:17:00.530 align:start position:0% in our network but<00:16:57.240> do<00:16:57.660> we<00:16:57.750> know<00:16:57.990> whether<00:16:58.320> the<00:16:58.980> I<00:16:59.250> mean<00:16:59.399> so<00:16:59.730> for 00:17:00.530 --> 00:17:00.540 align:start position:0% but do we know whether the I mean so for 00:17:00.540 --> 00:17:03.010 align:start position:0% but do we know whether the I mean so for example<00:17:00.600> memory<00:17:01.170> will<00:17:01.410> probably<00:17:01.890> be<00:17:02.160> paid 00:17:03.010 --> 00:17:03.020 align:start position:0% example memory will probably be paid 00:17:03.020 --> 00:17:06.819 align:start position:0% example memory will probably be paid with<00:17:04.020> regard<00:17:04.350> to<00:17:04.410> the<00:17:04.800> the<00:17:05.429> memory<00:17:05.730> of<00:17:05.790> the 00:17:06.819 --> 00:17:06.829 align:start position:0% with regard to the the memory of the 00:17:06.829 --> 00:17:08.720 align:start position:0% with regard to the the memory of the virtual<00:17:07.829> memory<00:17:08.010> of<00:17:08.250> the<00:17:08.339> virtual<00:17:08.640> machine 00:17:08.720 --> 00:17:08.730 align:start position:0% virtual memory of the virtual machine 00:17:08.730 --> 00:17:11.120 align:start position:0% virtual memory of the virtual machine and<00:17:09.030> not<00:17:09.240> with<00:17:09.900> regards<00:17:10.290> to<00:17:10.319> the<00:17:10.589> memory<00:17:11.069> of 00:17:11.120 --> 00:17:11.130 align:start position:0% and not with regards to the memory of 00:17:11.130 --> 00:17:13.040 align:start position:0% and not with regards to the memory of the<00:17:11.339> actual<00:17:11.850> physical<00:17:12.209> implementation<00:17:12.449> I 00:17:13.040 --> 00:17:13.050 align:start position:0% the actual physical implementation I 00:17:13.050 --> 00:17:15.110 align:start position:0% the actual physical implementation I mean<00:17:13.800> it's<00:17:13.949> easy<00:17:14.220> for<00:17:14.459> memory<00:17:14.699> because<00:17:14.970> it 00:17:15.110 --> 00:17:15.120 align:start position:0% mean it's easy for memory because it 00:17:15.120 --> 00:17:17.390 align:start position:0% mean it's easy for memory because it probably<00:17:15.780> won't<00:17:16.170> scale<00:17:16.530> quadratically<00:17:17.040> but 00:17:17.390 --> 00:17:17.400 align:start position:0% probably won't scale quadratically but 00:17:17.400 --> 00:17:18.890 align:start position:0% probably won't scale quadratically but there<00:17:17.699> could<00:17:17.970> be<00:17:18.030> some<00:17:18.329> other<00:17:18.420> edge<00:17:18.630> cases 00:17:18.890 --> 00:17:18.900 align:start position:0% there could be some other edge cases 00:17:18.900 --> 00:17:20.199 align:start position:0% there could be some other edge cases that 00:17:20.199 --> 00:17:20.209 align:start position:0% that 00:17:20.209 --> 00:17:24.079 align:start position:0% that yeah<00:17:21.350> could<00:17:22.350> hurt<00:17:22.500> us<00:17:22.620> at<00:17:22.770> some<00:17:22.920> point<00:17:23.160> so<00:17:23.579> yeah 00:17:24.079 --> 00:17:24.089 align:start position:0% yeah could hurt us at some point so yeah 00:17:24.089 --> 00:17:26.419 align:start position:0% yeah could hurt us at some point so yeah the<00:17:24.240> memory<00:17:24.540> is<00:17:24.689> very<00:17:24.900> explicitly<00:17:25.709> allocated 00:17:26.419 --> 00:17:26.429 align:start position:0% the memory is very explicitly allocated 00:17:26.429 --> 00:17:29.330 align:start position:0% the memory is very explicitly allocated with<00:17:26.610> web<00:17:26.790> assembly<00:17:27.300> you<00:17:28.290> use<00:17:28.620> expand<00:17:29.100> memory 00:17:29.330 --> 00:17:29.340 align:start position:0% with web assembly you use expand memory 00:17:29.340 --> 00:17:32.419 align:start position:0% with web assembly you use expand memory and<00:17:29.730> there's<00:17:30.210> initial<00:17:30.890> memory<00:17:31.890> allocations 00:17:32.419 --> 00:17:32.429 align:start position:0% and there's initial memory allocations 00:17:32.429 --> 00:17:34.370 align:start position:0% and there's initial memory allocations that<00:17:32.550> the<00:17:32.669> program<00:17:33.030> declares<00:17:33.510> up<00:17:33.750> front<00:17:34.020> in 00:17:34.370 --> 00:17:34.380 align:start position:0% that the program declares up front in 00:17:34.380 --> 00:17:36.140 align:start position:0% that the program declares up front in the<00:17:34.710> binary<00:17:34.890> format<00:17:35.400> okay<00:17:35.700> we're<00:17:35.940> starting 00:17:36.140 --> 00:17:36.150 align:start position:0% the binary format okay we're starting 00:17:36.150 --> 00:17:38.000 align:start position:0% the binary format okay we're starting with<00:17:36.540> this<00:17:36.750> amount<00:17:36.990> of<00:17:37.080> memory<00:17:37.260> here's<00:17:37.860> what 00:17:38.000 --> 00:17:38.010 align:start position:0% with this amount of memory here's what 00:17:38.010 --> 00:17:40.870 align:start position:0% with this amount of memory here's what we're<00:17:38.160> going<00:17:38.280> to<00:17:38.400> have<00:17:38.550> in<00:17:38.669> memory<00:17:39.050> so 00:17:40.870 --> 00:17:40.880 align:start position:0% we're going to have in memory so 00:17:40.880 --> 00:17:43.340 align:start position:0% we're going to have in memory so it's<00:17:41.880> actually<00:17:42.150> kind<00:17:42.300> of<00:17:42.360> like<00:17:42.480> a<00:17:42.510> elf<00:17:42.900> format 00:17:43.340 --> 00:17:43.350 align:start position:0% it's actually kind of like a elf format 00:17:43.350 --> 00:17:46.130 align:start position:0% it's actually kind of like a elf format if<00:17:43.470> you're<00:17:43.650> familiar<00:17:43.919> about<00:17:44.640> how<00:17:44.940> you<00:17:45.840> know<00:17:45.929> l 00:17:46.130 --> 00:17:46.140 align:start position:0% if you're familiar about how you know l 00:17:46.140 --> 00:17:49.610 align:start position:0% if you're familiar about how you know l format<00:17:46.530> initializes<00:17:47.429> programs<00:17:48.380> and<00:17:49.380> then 00:17:49.610 --> 00:17:49.620 align:start position:0% format initializes programs and then 00:17:49.620 --> 00:17:51.860 align:start position:0% format initializes programs and then whenever<00:17:50.340> you<00:17:50.610> need<00:17:50.820> more<00:17:51.090> memory<00:17:51.300> there's 00:17:51.860 --> 00:17:51.870 align:start position:0% whenever you need more memory there's 00:17:51.870 --> 00:17:55.730 align:start position:0% whenever you need more memory there's not<00:17:52.200> good<00:17:52.520> expand<00:17:53.520> memory<00:17:53.760> so<00:17:54.720> it's<00:17:55.440> very 00:17:55.730 --> 00:17:55.740 align:start position:0% not good expand memory so it's very 00:17:55.740 --> 00:17:57.919 align:start position:0% not good expand memory so it's very clear<00:17:56.100> where<00:17:56.370> all<00:17:56.550> the<00:17:57.210> memory<00:17:57.480> expansions 00:17:57.919 --> 00:17:57.929 align:start position:0% clear where all the memory expansions 00:17:57.929 --> 00:18:00.440 align:start position:0% clear where all the memory expansions can<00:17:58.440> happen<00:17:58.679> and<00:17:58.880> yeah<00:17:59.880> that's<00:18:00.150> what<00:18:00.330> we 00:18:00.440 --> 00:18:00.450 align:start position:0% can happen and yeah that's what we 00:18:00.450 --> 00:18:02.620 align:start position:0% can happen and yeah that's what we injector<00:18:01.290> me<00:18:01.440> drink 00:18:02.620 --> 00:18:02.630 align:start position:0% injector me drink 00:18:02.630 --> 00:18:06.500 align:start position:0% injector me drink just<00:18:03.630> like<00:18:03.809> finesse<00:18:04.620> break<00:18:05.040> up<00:18:05.309> code<00:18:05.640> okay 00:18:06.500 --> 00:18:06.510 align:start position:0% just like finesse break up code okay 00:18:06.510 --> 00:18:10.100 align:start position:0% just like finesse break up code okay like<00:18:07.140> the<00:18:07.290> S<00:18:07.440> break<00:18:07.830> in<00:18:08.100> all<00:18:08.250> UNIX<00:18:08.900> I'm<00:18:09.900> not 00:18:10.100 --> 00:18:10.110 align:start position:0% like the S break in all UNIX I'm not 00:18:10.110 --> 00:18:12.409 align:start position:0% like the S break in all UNIX I'm not familiar<00:18:10.260> with<00:18:10.590> that<00:18:10.620> yeah<00:18:11.400> II<00:18:11.429> have<00:18:12.150> to<00:18:12.270> tell 00:18:12.409 --> 00:18:12.419 align:start position:0% familiar with that yeah II have to tell 00:18:12.419 --> 00:18:14.740 align:start position:0% familiar with that yeah II have to tell me<00:18:12.540> about<00:18:12.600> that<00:18:12.780> it<00:18:13.020> is<00:18:13.260> similar<00:18:13.470> to<00:18:13.740> it<00:18:13.830> ok 00:18:14.740 --> 00:18:14.750 align:start position:0% me about that it is similar to it ok 00:18:14.750 --> 00:18:20.200 align:start position:0% me about that it is similar to it ok guess<00:18:15.750> BRK<00:18:16.940> yeah<00:18:17.710> just<00:18:18.710> a<00:18:18.800> quick<00:18:18.950> note<00:18:19.160> on<00:18:19.220> on 00:18:20.200 --> 00:18:20.210 align:start position:0% guess BRK yeah just a quick note on on 00:18:20.210 --> 00:18:23.830 align:start position:0% guess BRK yeah just a quick note on on the<00:18:20.390> metering<00:18:20.630> part<00:18:20.960> and<00:18:22.150> so<00:18:23.150> it's<00:18:23.510> entirely 00:18:23.830 --> 00:18:23.840 align:start position:0% the metering part and so it's entirely 00:18:23.840 --> 00:18:26.680 align:start position:0% the metering part and so it's entirely decoupled<00:18:24.380> from<00:18:24.410> the<00:18:24.650> execution<00:18:25.190> time<00:18:25.430> and<00:18:25.690> we 00:18:26.680 --> 00:18:26.690 align:start position:0% decoupled from the execution time and we 00:18:26.690 --> 00:18:28.810 align:start position:0% decoupled from the execution time and we have<00:18:26.900> the<00:18:27.020> input<00:18:27.200> byte<00:18:27.710> code<00:18:27.980> which<00:18:28.490> doesn't 00:18:28.810 --> 00:18:28.820 align:start position:0% have the input byte code which doesn't 00:18:28.820 --> 00:18:31.150 align:start position:0% have the input byte code which doesn't have<00:18:28.970> metering<00:18:29.390> because<00:18:30.110> we<00:18:30.230> don't<00:18:30.440> trust<00:18:30.710> the 00:18:31.150 --> 00:18:31.160 align:start position:0% have metering because we don't trust the 00:18:31.160 --> 00:18:33.520 align:start position:0% have metering because we don't trust the input<00:18:31.400> compilers<00:18:31.910> so<00:18:32.090> anyone<00:18:32.360> who<00:18:32.600> compiles 00:18:33.520 --> 00:18:33.530 align:start position:0% input compilers so anyone who compiles 00:18:33.530 --> 00:18:35.290 align:start position:0% input compilers so anyone who compiles it<00:18:33.680> wasn't<00:18:34.040> we<00:18:34.550> don't<00:18:34.760> really<00:18:34.850> want<00:18:35.060> to<00:18:35.120> trust 00:18:35.290 --> 00:18:35.300 align:start position:0% it wasn't we don't really want to trust 00:18:35.300 --> 00:18:37.300 align:start position:0% it wasn't we don't really want to trust them<00:18:35.510> to<00:18:35.540> include<00:18:36.440> metering<00:18:36.830> in<00:18:36.950> a<00:18:37.010> correct 00:18:37.300 --> 00:18:37.310 align:start position:0% them to include metering in a correct 00:18:37.310 --> 00:18:40.810 align:start position:0% them to include metering in a correct way<00:18:37.400> and<00:18:37.960> so<00:18:38.960> when<00:18:39.080> it<00:18:39.200> gets<00:18:39.380> to<00:18:39.530> the<00:18:39.820> execution 00:18:40.810 --> 00:18:40.820 align:start position:0% way and so when it gets to the execution 00:18:40.820 --> 00:18:43.450 align:start position:0% way and so when it gets to the execution time<00:18:41.030> we<00:18:41.900> will<00:18:42.080> inject<00:18:42.650> these<00:18:43.010> metering 00:18:43.450 --> 00:18:43.460 align:start position:0% time we will inject these metering 00:18:43.460 --> 00:18:45.520 align:start position:0% time we will inject these metering statements<00:18:44.030> into<00:18:44.510> the<00:18:44.690> right<00:18:44.870> places<00:18:45.200> in<00:18:45.440> the 00:18:45.520 --> 00:18:45.530 align:start position:0% statements into the right places in the 00:18:45.530 --> 00:18:48.700 align:start position:0% statements into the right places in the bytecode<00:18:45.680> and<00:18:46.570> during<00:18:47.570> runtime<00:18:47.810> there's<00:18:48.530> no 00:18:48.700 --> 00:18:48.710 align:start position:0% bytecode and during runtime there's no 00:18:48.710 --> 00:18:51.220 align:start position:0% bytecode and during runtime there's no need<00:18:48.890> to<00:18:48.920> do<00:18:49.340> anything<00:18:49.640> special<00:18:49.960> all<00:18:50.960> those 00:18:51.220 --> 00:18:51.230 align:start position:0% need to do anything special all those 00:18:51.230 --> 00:18:53.290 align:start position:0% need to do anything special all those metering<00:18:51.590> statements<00:18:52.100> are<00:18:52.460> just<00:18:52.730> calls<00:18:53.000> to<00:18:53.270> a 00:18:53.290 --> 00:18:53.300 align:start position:0% metering statements are just calls to a 00:18:53.300 --> 00:18:55.900 align:start position:0% metering statements are just calls to a specific<00:18:53.660> function<00:18:54.050> and<00:18:54.470> so<00:18:55.430> this<00:18:55.640> kinda 00:18:55.900 --> 00:18:55.910 align:start position:0% specific function and so this kinda 00:18:55.910 --> 00:18:59.400 align:start position:0% specific function and so this kinda works<00:18:56.090> like<00:18:56.360> how<00:18:56.720> and<00:18:57.080> it<00:18:58.040> jet<00:18:58.310> works<00:18:58.580> and 00:18:59.400 --> 00:18:59.410 align:start position:0% works like how and it jet works and 00:18:59.410 --> 00:19:03.490 align:start position:0% works like how and it jet works and like<00:19:00.410> de<00:19:00.560> la<00:19:00.620> vm<00:19:00.950> jet<00:19:01.160> we<00:19:01.340> have<00:19:01.520> four<00:19:02.330> EVM<00:19:02.630> but 00:19:03.490 --> 00:19:03.500 align:start position:0% like de la vm jet we have four EVM but 00:19:03.500 --> 00:19:05.800 align:start position:0% like de la vm jet we have four EVM but we<00:19:03.620> do<00:19:03.740> this<00:19:03.980> upfront<00:19:04.220> before<00:19:04.760> execution<00:19:05.360> so 00:19:05.800 --> 00:19:05.810 align:start position:0% we do this upfront before execution so 00:19:05.810 --> 00:19:08.920 align:start position:0% we do this upfront before execution so it<00:19:05.930> should<00:19:06.110> be<00:19:06.140> much<00:19:06.560> faster<00:19:06.970> and<00:19:07.970> another 00:19:08.920 --> 00:19:08.930 align:start position:0% it should be much faster and another 00:19:08.930 --> 00:19:11.020 align:start position:0% it should be much faster and another interesting<00:19:09.050> point<00:19:09.620> great<00:19:10.220> so<00:19:10.790> you<00:19:10.850> were 00:19:11.020 --> 00:19:11.030 align:start position:0% interesting point great so you were 00:19:11.030 --> 00:19:12.580 align:start position:0% interesting point great so you were thinking<00:19:11.060> about<00:19:11.600> like<00:19:11.780> doing<00:19:12.170> the<00:19:12.290> metering 00:19:12.580 --> 00:19:12.590 align:start position:0% thinking about like doing the metering 00:19:12.590 --> 00:19:15.370 align:start position:0% thinking about like doing the metering in<00:19:12.770> another<00:19:13.070> thread<00:19:13.400> correct<00:19:14.060> great<00:19:14.780> yeah<00:19:15.350> I 00:19:15.370 --> 00:19:15.380 align:start position:0% in another thread correct great yeah I 00:19:15.380 --> 00:19:18.430 align:start position:0% in another thread correct great yeah I don't<00:19:15.620> think<00:19:15.770> that's<00:19:16.100> going<00:19:16.250> to<00:19:16.310> work<00:19:16.900> so<00:19:17.900> will 00:19:18.430 --> 00:19:18.440 align:start position:0% don't think that's going to work so will 00:19:18.440 --> 00:19:19.900 align:start position:0% don't think that's going to work so will it<00:19:18.590> work<00:19:18.800> but<00:19:19.100> I<00:19:19.190> don't<00:19:19.250> think<00:19:19.490> it's<00:19:19.670> going<00:19:19.820> to 00:19:19.900 --> 00:19:19.910 align:start position:0% it work but I don't think it's going to 00:19:19.910 --> 00:19:22.980 align:start position:0% it work but I don't think it's going to be<00:19:20.000> any<00:19:20.180> faster<00:19:20.780> now<00:19:20.930> ok 00:19:22.980 --> 00:19:22.990 align:start position:0% be any faster now ok 00:19:22.990 --> 00:19:26.070 align:start position:0% be any faster now ok and<00:19:23.990> that<00:19:24.650> is 00:19:26.070 --> 00:19:26.080 align:start position:0% and that is 00:19:26.080 --> 00:19:29.380 align:start position:0% and that is it<00:19:27.080> would<00:19:27.380> save<00:19:27.800> time<00:19:28.280> on<00:19:28.700> the<00:19:28.850> very<00:19:29.090> most 00:19:29.380 --> 00:19:29.390 align:start position:0% it would save time on the very most 00:19:29.390 --> 00:19:33.010 align:start position:0% it would save time on the very most expensive<00:19:30.140> instructions<00:19:31.240> which<00:19:32.240> cost<00:19:32.540> enough 00:19:33.010 --> 00:19:33.020 align:start position:0% expensive instructions which cost enough 00:19:33.020 --> 00:19:35.650 align:start position:0% expensive instructions which cost enough that<00:19:33.230> it's<00:19:33.380> not<00:19:33.560> worth<00:19:33.800> saving<00:19:34.070> time<00:19:34.490> and<00:19:34.760> on 00:19:35.650 --> 00:19:35.660 align:start position:0% that it's not worth saving time and on 00:19:35.660 --> 00:19:38.140 align:start position:0% that it's not worth saving time and on long<00:19:35.960> runs<00:19:36.320> of<00:19:36.740> just<00:19:37.070> doing<00:19:37.310> addition<00:19:38.000> and 00:19:38.140 --> 00:19:38.150 align:start position:0% long runs of just doing addition and 00:19:38.150 --> 00:19:41.050 align:start position:0% long runs of just doing addition and multiplication<00:19:38.230> and<00:19:39.230> arithmetic<00:19:39.850> you're<00:19:40.850> not 00:19:41.050 --> 00:19:41.060 align:start position:0% multiplication and arithmetic you're not 00:19:41.060 --> 00:19:43.050 align:start position:0% multiplication and arithmetic you're not going<00:19:41.360> to<00:19:41.450> save<00:19:41.690> enough<00:19:42.080> to<00:19:42.260> bother 00:19:43.050 --> 00:19:43.060 align:start position:0% going to save enough to bother 00:19:43.060 --> 00:19:45.190 align:start position:0% going to save enough to bother especially<00:19:44.060> if<00:19:44.180> you're<00:19:44.390> going<00:19:44.630> to<00:19:44.750> push<00:19:44.990> all 00:19:45.190 --> 00:19:45.200 align:start position:0% especially if you're going to push all 00:19:45.200 --> 00:19:49.200 align:start position:0% especially if you're going to push all of<00:19:45.230> that<00:19:45.590> to<00:19:45.830> the<00:19:45.980> end<00:19:46.160> of<00:19:46.370> the<00:19:46.460> basic<00:19:46.880> block 00:19:49.200 --> 00:19:49.210 align:start position:0% 00:19:49.210 --> 00:19:52.630 align:start position:0% but<00:19:50.210> like<00:19:50.510> doing<00:19:50.810> a<00:19:50.930> call<00:19:51.230> cost<00:19:51.770> enough<00:19:52.310> that's 00:19:52.630 --> 00:19:52.640 align:start position:0% but like doing a call cost enough that's 00:19:52.640 --> 00:19:54.540 align:start position:0% but like doing a call cost enough that's saving<00:19:52.880> a<00:19:53.150> bit<00:19:53.330> of<00:19:53.480> time 00:19:54.540 --> 00:19:54.550 align:start position:0% saving a bit of time 00:19:54.550 --> 00:20:00.540 align:start position:0% saving a bit of time doing<00:19:55.550> the<00:19:55.760> need<00:19:55.970> ring<00:19:56.240> on<00:19:56.420> the<00:19:56.600> call 00:20:00.540 --> 00:20:00.550 align:start position:0% 00:20:00.550 --> 00:20:04.210 align:start position:0% I<00:20:01.550> was<00:20:01.790> just<00:20:01.880> going<00:20:02.420> to<00:20:02.480> say<00:20:02.630> like<00:20:02.920> we<00:20:03.920> sorta 00:20:04.210 --> 00:20:04.220 align:start position:0% I was just going to say like we sorta 00:20:04.220 --> 00:20:05.680 align:start position:0% I was just going to say like we sorta can<00:20:04.370> do<00:20:04.490> that<00:20:04.640> now<00:20:04.790> it's<00:20:05.300> a<00:20:05.390> little<00:20:05.540> bit 00:20:05.680 --> 00:20:05.690 align:start position:0% can do that now it's a little bit 00:20:05.690 --> 00:20:08.610 align:start position:0% can do that now it's a little bit hackneyed<00:20:06.560> but<00:20:06.590> we<00:20:06.860> sort<00:20:07.070> of<00:20:07.160> get<00:20:07.460> get<00:20:07.910> the 00:20:08.610 --> 00:20:08.620 align:start position:0% hackneyed but we sort of get get the 00:20:08.620 --> 00:20:11.530 align:start position:0% hackneyed but we sort of get get the separation<00:20:09.620> concerns<00:20:10.010> to<00:20:10.160> free<00:20:10.400> because<00:20:11.060> like 00:20:11.530 --> 00:20:11.540 align:start position:0% separation concerns to free because like 00:20:11.540 --> 00:20:13.720 align:start position:0% separation concerns to free because like whenever<00:20:12.440> we<00:20:12.620> call<00:20:12.890> out<00:20:12.980> to<00:20:13.100> the<00:20:13.190> interface<00:20:13.400> to 00:20:13.720 --> 00:20:13.730 align:start position:0% whenever we call out to the interface to 00:20:13.730 --> 00:20:15.580 align:start position:0% whenever we call out to the interface to do<00:20:13.850> the<00:20:13.940> metering<00:20:14.210> that's<00:20:14.990> going<00:20:15.440> to<00:20:15.500> be 00:20:15.580 --> 00:20:15.590 align:start position:0% do the metering that's going to be 00:20:15.590 --> 00:20:18.090 align:start position:0% do the metering that's going to be possibly<00:20:16.190> running<00:20:16.400> on<00:20:16.580> a<00:20:16.610> separate<00:20:16.880> thread<00:20:17.000> so 00:20:18.090 --> 00:20:18.100 align:start position:0% possibly running on a separate thread so 00:20:18.100 --> 00:20:20.710 align:start position:0% possibly running on a separate thread so but<00:20:19.100> I<00:20:19.310> don't<00:20:19.490> know<00:20:19.700> how<00:20:20.330> much<00:20:20.480> that's 00:20:20.710 --> 00:20:20.720 align:start position:0% but I don't know how much that's 00:20:20.720 --> 00:20:22.380 align:start position:0% but I don't know how much that's improving<00:20:21.080> our<00:20:21.290> performance<00:20:21.770> either<00:20:21.920> so 00:20:22.380 --> 00:20:22.390 align:start position:0% improving our performance either so 00:20:22.390 --> 00:20:24.840 align:start position:0% improving our performance either so ouchy<00:20:23.390> for<00:20:23.600> your<00:20:23.720> stretch 00:20:24.840 --> 00:20:24.850 align:start position:0% ouchy for your stretch 00:20:24.850 --> 00:20:26.860 align:start position:0% ouchy for your stretch right<00:20:25.850> now<00:20:26.000> we're<00:20:26.180> using<00:20:26.330> the<00:20:26.570> eight<00:20:26.690> to 00:20:26.860 --> 00:20:26.870 align:start position:0% right now we're using the eight to 00:20:26.870 --> 00:20:29.730 align:start position:0% right now we're using the eight to prototype<00:20:27.440> so<00:20:27.950> we<00:20:28.070> get<00:20:28.280> 8<00:20:28.550> threads<00:20:28.880> by<00:20:29.180> default 00:20:29.730 --> 00:20:29.740 align:start position:0% prototype so we get 8 threads by default 00:20:29.740 --> 00:20:33.760 align:start position:0% prototype so we get 8 threads by default and<00:20:30.740> they're<00:20:31.390> allocated<00:20:32.390> when<00:20:32.570> it<00:20:32.720> starts<00:20:33.650> up 00:20:33.760 --> 00:20:33.770 align:start position:0% and they're allocated when it starts up 00:20:33.770 --> 00:20:35.650 align:start position:0% and they're allocated when it starts up so<00:20:34.340> they're<00:20:34.670> fairly<00:20:34.850> cheap<00:20:35.150> very<00:20:35.390> cheap 00:20:35.650 --> 00:20:35.660 align:start position:0% so they're fairly cheap very cheap 00:20:35.660 --> 00:20:38.070 align:start position:0% so they're fairly cheap very cheap actually<00:20:36.350> thanks<00:20:37.310> guy 00:20:38.070 --> 00:20:38.080 align:start position:0% actually thanks guy 00:20:38.080 --> 00:20:41.620 align:start position:0% actually thanks guy thank<00:20:39.080> you<00:20:39.230> very<00:20:39.260> much<00:20:39.940> thank<00:20:40.940> you<00:20:41.060> all<00:20:41.330> thank 00:20:41.620 --> 00:20:41.630 align:start position:0% thank you very much thank you all thank 00:20:41.630 --> 00:20:43.490 align:start position:0% thank you very much thank you all thank you<00:20:41.930> very<00:20:42.140> much<00:20:42.380> thank<00:20:43.070> you 00:20:43.490 --> 00:20:43.500 align:start position:0% you very much thank you 00:20:43.500 --> 00:20:43.970 align:start position:0% you very much thank you [Applause] 00:20:43.970 --> 00:20:43.980 align:start position:0% [Applause] 00:20:43.980 --> 00:20:52.150 align:start position:0% [Applause] [Music]