WEBVTT Kind: captions Language: en 00:00:00.149 --> 00:00:02.240 align:start position:0% hi<00:00:00.599> I'm<00:00:00.780> a<00:00:00.810> hugger<00:00:01.110> I'm<00:00:01.439> team<00:00:01.860> lead<00:00:02.010> for<00:00:02.159> the 00:00:02.240 --> 00:00:02.250 align:start position:0% hi I'm a hugger I'm team lead for the 00:00:02.250 --> 00:00:04.400 align:start position:0% hi I'm a hugger I'm team lead for the UCS<00:00:02.730> team<00:00:02.970> which<00:00:03.360> actually<00:00:03.780> is<00:00:03.840> a<00:00:03.929> JavaScript 00:00:04.400 --> 00:00:04.410 align:start position:0% UCS team which actually is a JavaScript 00:00:04.410 --> 00:00:05.900 align:start position:0% UCS team which actually is a JavaScript team<00:00:04.560> was<00:00:04.710> in<00:00:04.830> the<00:00:04.859> serum<00:00:05.220> foundation<00:00:05.339> and 00:00:05.900 --> 00:00:05.910 align:start position:0% team was in the serum foundation and 00:00:05.910 --> 00:00:07.970 align:start position:0% team was in the serum foundation and I'll<00:00:06.810> give<00:00:06.990> you<00:00:07.109> a<00:00:07.170> short<00:00:07.379> introduction<00:00:07.710> to 00:00:07.970 --> 00:00:07.980 align:start position:0% I'll give you a short introduction to 00:00:07.980 --> 00:00:09.620 align:start position:0% I'll give you a short introduction to what<00:00:08.610> we<00:00:08.760> have<00:00:08.880> to<00:00:09.000> what<00:00:09.090> we're<00:00:09.269> doing<00:00:09.300> and 00:00:09.620 --> 00:00:09.630 align:start position:0% what we have to what we're doing and 00:00:09.630 --> 00:00:11.270 align:start position:0% what we have to what we're doing and then<00:00:10.170> the<00:00:10.349> other<00:00:10.469> team<00:00:10.769> members<00:00:11.070> will 00:00:11.270 --> 00:00:11.280 align:start position:0% then the other team members will 00:00:11.280 --> 00:00:13.520 align:start position:0% then the other team members will introduce<00:00:11.969> some<00:00:12.389> some<00:00:12.900> parts<00:00:13.139> of<00:00:13.230> the<00:00:13.349> roadmap 00:00:13.520 --> 00:00:13.530 align:start position:0% introduce some some parts of the roadmap 00:00:13.530 --> 00:00:16.580 align:start position:0% introduce some some parts of the roadmap for<00:00:13.950> for<00:00:14.340> 2019<00:00:14.759> as<00:00:15.269> what's<00:00:16.080> the<00:00:16.139> serious 00:00:16.580 --> 00:00:16.590 align:start position:0% for for 2019 as what's the serious 00:00:16.590 --> 00:00:18.620 align:start position:0% for for 2019 as what's the serious assume<00:00:16.800> jaysis<00:00:17.130> maybe<00:00:17.390> this<00:00:18.390> github 00:00:18.620 --> 00:00:18.630 align:start position:0% assume jaysis maybe this github 00:00:18.630 --> 00:00:20.900 align:start position:0% assume jaysis maybe this github organization<00:00:18.840> that<00:00:19.410> get<00:00:19.980> up<00:00:20.070> accomplish<00:00:20.670> is 00:00:20.900 --> 00:00:20.910 align:start position:0% organization that get up accomplish is 00:00:20.910 --> 00:00:23.240 align:start position:0% organization that get up accomplish is serious<00:00:21.750> and<00:00:21.900> what<00:00:22.230> Lane<00:00:22.439> said<00:00:22.650> we<00:00:22.800> we<00:00:23.039> mainly 00:00:23.240 --> 00:00:23.250 align:start position:0% serious and what Lane said we we mainly 00:00:23.250 --> 00:00:24.859 align:start position:0% serious and what Lane said we we mainly do<00:00:23.430> base<00:00:23.609> level<00:00:23.939> infrastructure<00:00:24.390> components 00:00:24.859 --> 00:00:24.869 align:start position:0% do base level infrastructure components 00:00:24.869 --> 00:00:26.269 align:start position:0% do base level infrastructure components in<00:00:24.930> JavaScript<00:00:25.380> so<00:00:25.439> this<00:00:26.010> is<00:00:26.130> an 00:00:26.269 --> 00:00:26.279 align:start position:0% in JavaScript so this is an 00:00:26.279 --> 00:00:27.620 align:start position:0% in JavaScript so this is an implementation<00:00:26.519> of<00:00:26.910> the<00:00:26.970> virtual<00:00:27.330> machine 00:00:27.620 --> 00:00:27.630 align:start position:0% implementation of the virtual machine 00:00:27.630 --> 00:00:29.870 align:start position:0% implementation of the virtual machine deftly<00:00:28.529> 2<00:00:28.680> p.m.<00:00:28.890> limitation<00:00:29.429> miracle<00:00:29.760> tree 00:00:29.870 --> 00:00:29.880 align:start position:0% deftly 2 p.m. limitation miracle tree 00:00:29.880 --> 00:00:31.640 align:start position:0% deftly 2 p.m. limitation miracle tree implementation<00:00:30.000> and<00:00:30.570> so<00:00:30.689> on<00:00:30.840> and<00:00:31.050> we've 00:00:31.640 --> 00:00:31.650 align:start position:0% implementation and so on and we've 00:00:31.650 --> 00:00:33.610 align:start position:0% implementation and so on and we've roughly<00:00:32.309> have<00:00:32.430> got<00:00:32.640> 20<00:00:32.969> active<00:00:33.180> minute 00:00:33.610 --> 00:00:33.620 align:start position:0% roughly have got 20 active minute 00:00:33.620 --> 00:00:35.840 align:start position:0% roughly have got 20 active minute repositories<00:00:34.620> there<00:00:34.800> so<00:00:35.010> lots<00:00:35.250> of<00:00:35.340> work<00:00:35.550> and 00:00:35.840 --> 00:00:35.850 align:start position:0% repositories there so lots of work and 00:00:35.850 --> 00:00:37.549 align:start position:0% repositories there so lots of work and mostly<00:00:36.570> it's<00:00:36.750> done<00:00:36.870> by<00:00:37.020> the<00:00:37.079> serum<00:00:37.380> foundation 00:00:37.549 --> 00:00:37.559 align:start position:0% mostly it's done by the serum foundation 00:00:37.559 --> 00:00:40.430 align:start position:0% mostly it's done by the serum foundation there<00:00:38.040> are<00:00:38.129> some<00:00:38.280> other<00:00:38.840> minute<00:00:39.840> repositories 00:00:40.430 --> 00:00:40.440 align:start position:0% there are some other minute repositories 00:00:40.440 --> 00:00:42.860 align:start position:0% there are some other minute repositories from<00:00:40.590> other<00:00:40.739> people<00:00:41.600> just<00:00:42.600> as<00:00:42.750> an 00:00:42.860 --> 00:00:42.870 align:start position:0% from other people just as an 00:00:42.870 --> 00:00:44.270 align:start position:0% from other people just as an introduction<00:00:43.140> we<00:00:43.410> do<00:00:43.500> monthly<00:00:43.680> ecosystem 00:00:44.270 --> 00:00:44.280 align:start position:0% introduction we do monthly ecosystem 00:00:44.280 --> 00:00:47.479 align:start position:0% introduction we do monthly ecosystem updates<00:00:44.610> on<00:00:44.850> reddit<00:00:45.149> since<00:00:46.140> some<00:00:46.320> time<00:00:46.559> so<00:00:47.340> if 00:00:47.479 --> 00:00:47.489 align:start position:0% updates on reddit since some time so if 00:00:47.489 --> 00:00:49.010 align:start position:0% updates on reddit since some time so if you<00:00:47.579> want<00:00:47.760> to<00:00:47.820> stay<00:00:48.059> up<00:00:48.210> to<00:00:48.329> date<00:00:48.360> what<00:00:48.629> we<00:00:48.750> what 00:00:49.010 --> 00:00:49.020 align:start position:0% you want to stay up to date what we what 00:00:49.020 --> 00:00:50.090 align:start position:0% you want to stay up to date what we what we<00:00:49.050> are<00:00:49.170> up<00:00:49.320> to<00:00:49.440> what<00:00:49.500> we're<00:00:49.680> doing<00:00:49.710> at<00:00:50.010> the 00:00:50.090 --> 00:00:50.100 align:start position:0% we are up to what we're doing at the 00:00:50.100 --> 00:00:51.799 align:start position:0% we are up to what we're doing at the moment<00:00:50.129> go<00:00:51.059> and<00:00:51.180> read<00:00:51.300> it<00:00:51.329> and<00:00:51.539> have<00:00:51.629> a<00:00:51.660> look 00:00:51.799 --> 00:00:51.809 align:start position:0% moment go and read it and have a look 00:00:51.809 --> 00:00:54.830 align:start position:0% moment go and read it and have a look out<00:00:51.960> there<00:00:52.230> what's<00:00:53.070> going<00:00:53.340> on<00:00:53.489> I<00:00:53.670> just<00:00:54.539> provide 00:00:54.830 --> 00:00:54.840 align:start position:0% out there what's going on I just provide 00:00:54.840 --> 00:00:57.200 align:start position:0% out there what's going on I just provide in<00:00:54.989> repository<00:00:55.620> organization<00:00:56.460> so<00:00:56.910> if<00:00:57.059> you've 00:00:57.200 --> 00:00:57.210 align:start position:0% in repository organization so if you've 00:00:57.210 --> 00:00:59.510 align:start position:0% in repository organization so if you've got<00:00:57.420> for<00:00:57.750> general<00:00:58.559> project<00:00:58.800> management<00:00:59.399> stuff 00:00:59.510 --> 00:00:59.520 align:start position:0% got for general project management stuff 00:00:59.520 --> 00:01:01.790 align:start position:0% got for general project management stuff so<00:00:59.850> if<00:00:59.969> you<00:01:00.059> want<00:01:00.210> to<00:01:00.320> suggest<00:01:01.320> something 00:01:01.790 --> 00:01:01.800 align:start position:0% so if you want to suggest something 00:01:01.800 --> 00:01:04.219 align:start position:0% so if you want to suggest something which<00:01:02.100> we<00:01:02.430> could<00:01:02.969> do<00:01:03.059> better<00:01:03.270> on<00:01:03.390> new<00:01:03.719> projects 00:01:04.219 --> 00:01:04.229 align:start position:0% which we could do better on new projects 00:01:04.229 --> 00:01:06.440 align:start position:0% which we could do better on new projects we<00:01:04.739> should<00:01:04.920> do<00:01:05.070> you<00:01:05.309> can<00:01:05.580> go<00:01:05.820> there<00:01:06.060> and<00:01:06.240> just 00:01:06.440 --> 00:01:06.450 align:start position:0% we should do you can go there and just 00:01:06.450 --> 00:01:07.609 align:start position:0% we should do you can go there and just file<00:01:06.630> an<00:01:06.750> issue<00:01:06.869> there<00:01:07.170> and<00:01:07.350> then<00:01:07.470> we<00:01:07.590> can 00:01:07.609 --> 00:01:07.619 align:start position:0% file an issue there and then we can 00:01:07.619 --> 00:01:09.380 align:start position:0% file an issue there and then we can start<00:01:08.010> a<00:01:08.070> discussion<00:01:08.159> there<00:01:08.549> and<00:01:09.000> we've<00:01:09.360> got 00:01:09.380 --> 00:01:09.390 align:start position:0% start a discussion there and we've got 00:01:09.390 --> 00:01:11.300 align:start position:0% start a discussion there and we've got all<00:01:09.630> mandatory<00:01:09.840> jitter<00:01:10.260> channel<00:01:10.590> at<00:01:10.680> a<00:01:10.710> cerium 00:01:11.300 --> 00:01:11.310 align:start position:0% all mandatory jitter channel at a cerium 00:01:11.310 --> 00:01:13.250 align:start position:0% all mandatory jitter channel at a cerium slash<00:01:11.580> assumed<00:01:12.030> raise<00:01:12.150> and<00:01:12.570> you<00:01:12.960> can<00:01:13.110> go<00:01:13.229> there 00:01:13.250 --> 00:01:13.260 align:start position:0% slash assumed raise and you can go there 00:01:13.260 --> 00:01:15.050 align:start position:0% slash assumed raise and you can go there for<00:01:13.590> tech<00:01:13.740> related<00:01:14.100> questions<00:01:14.460> or<00:01:14.640> forgetting 00:01:15.050 --> 00:01:15.060 align:start position:0% for tech related questions or forgetting 00:01:15.060 --> 00:01:18.219 align:start position:0% for tech related questions or forgetting contacted<00:01:15.659> in<00:01:15.840> first<00:01:16.200> first<00:01:16.799> place<00:01:17.009> as<00:01:17.189> well 00:01:18.219 --> 00:01:18.229 align:start position:0% contacted in first first place as well 00:01:18.229 --> 00:01:20.300 align:start position:0% contacted in first first place as well so<00:01:19.229> what<00:01:19.409> are<00:01:19.500> the<00:01:19.560> characteristics<00:01:20.130> of<00:01:20.250> our 00:01:20.300 --> 00:01:20.310 align:start position:0% so what are the characteristics of our 00:01:20.310 --> 00:01:21.649 align:start position:0% so what are the characteristics of our libraries<00:01:20.700> we<00:01:20.850> initially<00:01:21.240> developed<00:01:21.570> from 00:01:21.649 --> 00:01:21.659 align:start position:0% libraries we initially developed from 00:01:21.659 --> 00:01:23.749 align:start position:0% libraries we initially developed from nodejs<00:01:22.020> and<00:01:22.380> then<00:01:22.590> we<00:01:22.740> distribute<00:01:23.189> many<00:01:23.640> of 00:01:23.749 --> 00:01:23.759 align:start position:0% nodejs and then we distribute many of 00:01:23.759 --> 00:01:25.910 align:start position:0% nodejs and then we distribute many of our<00:01:23.880> libraries<00:01:24.240> as<00:01:24.390> well<00:01:24.420> as<00:01:24.570> is<00:01:25.439> five<00:01:25.680> modules 00:01:25.910 --> 00:01:25.920 align:start position:0% our libraries as well as is five modules 00:01:25.920 --> 00:01:28.429 align:start position:0% our libraries as well as is five modules for<00:01:26.310> the<00:01:26.340> browser<00:01:26.580> so<00:01:27.150> for<00:01:27.390> example<00:01:27.689> the<00:01:27.780> VM<00:01:28.200> is 00:01:28.429 --> 00:01:28.439 align:start position:0% for the browser so for example the VM is 00:01:28.439 --> 00:01:31.249 align:start position:0% for the browser so for example the VM is a<00:01:28.470> browser<00:01:29.159> first<00:01:29.460> library<00:01:30.090> and<00:01:30.360> it's<00:01:31.110> also 00:01:31.249 --> 00:01:31.259 align:start position:0% a browser first library and it's also 00:01:31.259 --> 00:01:34.640 align:start position:0% a browser first library and it's also actually<00:01:31.670> run<00:01:32.670> in<00:01:32.880> in<00:01:33.060> various<00:01:33.360> tools<00:01:33.659> like 00:01:34.640 --> 00:01:34.650 align:start position:0% actually run in in various tools like 00:01:34.650 --> 00:01:37.910 align:start position:0% actually run in in various tools like remix<00:01:35.040> or<00:01:35.220> meta<00:01:35.400> mask<00:01:35.700> or<00:01:36.509> truffle<00:01:36.930> as<00:01:37.439> many 00:01:37.910 --> 00:01:37.920 align:start position:0% remix or meta mask or truffle as many 00:01:37.920 --> 00:01:40.670 align:start position:0% remix or meta mask or truffle as many development<00:01:38.490> tools<00:01:38.869> our<00:01:39.869> libraries<00:01:40.259> are 00:01:40.670 --> 00:01:40.680 align:start position:0% development tools our libraries are 00:01:40.680 --> 00:01:42.770 align:start position:0% development tools our libraries are high-quality<00:01:41.040> libraries<00:01:41.700> we've<00:01:41.880> got<00:01:42.420> unity 00:01:42.770 --> 00:01:42.780 align:start position:0% high-quality libraries we've got unity 00:01:42.780 --> 00:01:44.389 align:start position:0% high-quality libraries we've got unity tests<00:01:43.110> you<00:01:43.320> know<00:01:43.380> unit<00:01:43.890> tests<00:01:44.070> for<00:01:44.250> all<00:01:44.280> the 00:01:44.389 --> 00:01:44.399 align:start position:0% tests you know unit tests for all the 00:01:44.399 --> 00:01:46.460 align:start position:0% tests you know unit tests for all the libraries<00:01:44.790> all<00:01:45.000> our<00:01:45.210> CI<00:01:45.390> integrated<00:01:46.020> and<00:01:46.350> we 00:01:46.460 --> 00:01:46.470 align:start position:0% libraries all our CI integrated and we 00:01:46.470 --> 00:01:49.100 align:start position:0% libraries all our CI integrated and we have<00:01:46.560> two<00:01:46.680> test<00:01:46.890> coverage<00:01:47.189> above<00:01:48.180> 90%<00:01:48.540> in<00:01:48.930> most 00:01:49.100 --> 00:01:49.110 align:start position:0% have two test coverage above 90% in most 00:01:49.110 --> 00:01:51.770 align:start position:0% have two test coverage above 90% in most cases<00:01:49.320> and<00:01:49.649> this<00:01:50.340> actually<00:01:50.700> is<00:01:50.820> really<00:01:51.509> needed 00:01:51.770 --> 00:01:51.780 align:start position:0% cases and this actually is really needed 00:01:51.780 --> 00:01:53.660 align:start position:0% cases and this actually is really needed because<00:01:51.869> yeah<00:01:52.439> like<00:01:52.770> like<00:01:53.009> I<00:01:53.040> said<00:01:53.280> the 00:01:53.660 --> 00:01:53.670 align:start position:0% because yeah like like I said the 00:01:53.670 --> 00:01:55.280 align:start position:0% because yeah like like I said the libraries<00:01:54.030> are<00:01:54.210> very<00:01:54.630> much<00:01:54.990> used<00:01:55.200> in 00:01:55.280 --> 00:01:55.290 align:start position:0% libraries are very much used in 00:01:55.290 --> 00:01:58.039 align:start position:0% libraries are very much used in production<00:01:55.560> and<00:01:56.040> also<00:01:56.700> in<00:01:57.049> security 00:01:58.039 --> 00:01:58.049 align:start position:0% production and also in security 00:01:58.049 --> 00:02:00.859 align:start position:0% production and also in security sensitive<00:01:58.350> contexts<00:01:59.009> and<00:01:59.240> we<00:02:00.240> do<00:02:00.420> like<00:02:00.600> behind 00:02:00.859 --> 00:02:00.869 align:start position:0% sensitive contexts and we do like behind 00:02:00.869 --> 00:02:02.719 align:start position:0% sensitive contexts and we do like behind a<00:02:01.049> bit<00:02:01.229> on<00:02:01.439> on<00:02:01.770> modernization<00:02:02.280> of<00:02:02.579> our 00:02:02.719 --> 00:02:02.729 align:start position:0% a bit on on modernization of our 00:02:02.729 --> 00:02:04.660 align:start position:0% a bit on on modernization of our libraries<00:02:03.060> we<00:02:03.270> are<00:02:03.390> very<00:02:03.689> much<00:02:03.840> aware<00:02:03.960> of<00:02:04.079> set 00:02:04.660 --> 00:02:04.670 align:start position:0% libraries we are very much aware of set 00:02:04.670 --> 00:02:07.340 align:start position:0% libraries we are very much aware of set like<00:02:05.670> using<00:02:06.360> modern<00:02:06.780> JavaScript<00:02:06.960> features 00:02:07.340 --> 00:02:07.350 align:start position:0% like using modern JavaScript features 00:02:07.350 --> 00:02:08.990 align:start position:0% like using modern JavaScript features like<00:02:07.710> promises<00:02:07.979> and<00:02:08.429> would<00:02:08.520> be<00:02:08.640> a<00:02:08.670> very<00:02:08.729> much 00:02:08.990 --> 00:02:09.000 align:start position:0% like promises and would be a very much 00:02:09.000 --> 00:02:11.449 align:start position:0% like promises and would be a very much callback<00:02:09.420> based<00:02:09.629> so<00:02:09.929> and<00:02:10.830> in<00:02:11.129> your<00:02:11.250> six 00:02:11.449 --> 00:02:11.459 align:start position:0% callback based so and in your six 00:02:11.459 --> 00:02:12.550 align:start position:0% callback based so and in your six classes<00:02:11.970> and<00:02:12.120> stuff<00:02:12.270> like 00:02:12.550 --> 00:02:12.560 align:start position:0% classes and stuff like 00:02:12.560 --> 00:02:13.839 align:start position:0% classes and stuff like but<00:02:12.800> we<00:02:12.920> have<00:02:13.130> this<00:02:13.220> on<00:02:13.370> the<00:02:13.430> plate<00:02:13.610> as<00:02:13.730> well 00:02:13.839 --> 00:02:13.849 align:start position:0% but we have this on the plate as well 00:02:13.849 --> 00:02:15.370 align:start position:0% but we have this on the plate as well and<00:02:14.060> we<00:02:14.150> will<00:02:14.239> do<00:02:14.480> updates<00:02:14.810> on<00:02:14.930> that<00:02:15.050> as<00:02:15.230> well 00:02:15.370 --> 00:02:15.380 align:start position:0% and we will do updates on that as well 00:02:15.380 --> 00:02:17.199 align:start position:0% and we will do updates on that as well and<00:02:15.620> another<00:02:16.160> part<00:02:16.640> is<00:02:16.790> typescript 00:02:17.199 --> 00:02:17.209 align:start position:0% and another part is typescript 00:02:17.209 --> 00:02:19.300 align:start position:0% and another part is typescript integration<00:02:17.720> where<00:02:17.900> Alex<00:02:18.290> will<00:02:18.470> we'll<00:02:18.739> talk 00:02:19.300 --> 00:02:19.310 align:start position:0% integration where Alex will we'll talk 00:02:19.310 --> 00:02:23.800 align:start position:0% integration where Alex will we'll talk about<00:02:19.430> more<00:02:20.390> later<00:02:21.970> actually<00:02:22.970> many<00:02:23.239> of<00:02:23.450> the 00:02:23.800 --> 00:02:23.810 align:start position:0% about more later actually many of the 00:02:23.810 --> 00:02:25.390 align:start position:0% about more later actually many of the work<00:02:23.959> being<00:02:24.470> done<00:02:24.560> is<00:02:24.800> actually<00:02:24.980> coming<00:02:25.370> from 00:02:25.390 --> 00:02:25.400 align:start position:0% work being done is actually coming from 00:02:25.400 --> 00:02:27.010 align:start position:0% work being done is actually coming from a<00:02:25.610> community<00:02:26.030> and<00:02:26.239> we<00:02:26.630> are<00:02:26.660> highly 00:02:27.010 --> 00:02:27.020 align:start position:0% a community and we are highly 00:02:27.020 --> 00:02:29.470 align:start position:0% a community and we are highly community-driven<00:02:27.620> projects<00:02:28.130> and<00:02:28.340> I'm<00:02:29.239> always 00:02:29.470 --> 00:02:29.480 align:start position:0% community-driven projects and I'm always 00:02:29.480 --> 00:02:33.009 align:start position:0% community-driven projects and I'm always very<00:02:29.750> much<00:02:30.319> amazed<00:02:31.099> that<00:02:31.569> every<00:02:32.569> now<00:02:32.750> and<00:02:32.900> then 00:02:33.009 --> 00:02:33.019 align:start position:0% very much amazed that every now and then 00:02:33.019 --> 00:02:35.589 align:start position:0% very much amazed that every now and then some<00:02:33.470> super<00:02:33.920> high<00:02:34.069> quality<00:02:34.300> pull<00:02:35.300> request 00:02:35.589 --> 00:02:35.599 align:start position:0% some super high quality pull request 00:02:35.599 --> 00:02:37.330 align:start position:0% some super high quality pull request comes<00:02:35.780> in<00:02:35.959> like<00:02:36.140> implementing<00:02:36.769> Merkle<00:02:37.099> trees 00:02:37.330 --> 00:02:37.340 align:start position:0% comes in like implementing Merkle trees 00:02:37.340 --> 00:02:40.390 align:start position:0% comes in like implementing Merkle trees or<00:02:37.700> doing<00:02:38.630> a<00:02:38.690> super<00:02:38.989> high<00:02:39.110> quality<00:02:39.140> new<00:02:39.980> client 00:02:40.390 --> 00:02:40.400 align:start position:0% or doing a super high quality new client 00:02:40.400 --> 00:02:42.850 align:start position:0% or doing a super high quality new client RPC<00:02:40.790> server<00:02:41.060> and<00:02:41.569> this<00:02:41.900> is<00:02:42.290> just<00:02:42.560> coming<00:02:42.800> out 00:02:42.850 --> 00:02:42.860 align:start position:0% RPC server and this is just coming out 00:02:42.860 --> 00:02:46.180 align:start position:0% RPC server and this is just coming out from<00:02:43.040> from<00:02:43.489> nowhere<00:02:43.959> and<00:02:44.959> I<00:02:45.170> actually<00:02:45.769> want<00:02:46.130> to 00:02:46.180 --> 00:02:46.190 align:start position:0% from from nowhere and I actually want to 00:02:46.190 --> 00:02:47.920 align:start position:0% from from nowhere and I actually want to take<00:02:46.370> the<00:02:46.489> stage<00:02:46.700> and<00:02:46.880> say<00:02:47.269> thank<00:02:47.540> you<00:02:47.630> to<00:02:47.900> all 00:02:47.920 --> 00:02:47.930 align:start position:0% take the stage and say thank you to all 00:02:47.930 --> 00:02:49.479 align:start position:0% take the stage and say thank you to all you<00:02:48.230> guys<00:02:48.260> who<00:02:48.650> contributed<00:02:49.250> to<00:02:49.370> our 00:02:49.479 --> 00:02:49.489 align:start position:0% you guys who contributed to our 00:02:49.489 --> 00:02:57.640 align:start position:0% you guys who contributed to our libraries<00:02:49.850> and<00:02:51.040> thank<00:02:52.040> you<00:02:55.840> and<00:02:56.840> I've<00:02:57.380> got 00:02:57.640 --> 00:02:57.650 align:start position:0% libraries and thank you and I've got 00:02:57.650 --> 00:02:58.809 align:start position:0% libraries and thank you and I've got very<00:02:57.890> much<00:02:58.010> this<00:02:58.160> on<00:02:58.310> the<00:02:58.400> plate<00:02:58.580> that<00:02:58.610> we 00:02:58.809 --> 00:02:58.819 align:start position:0% very much this on the plate that we 00:02:58.819 --> 00:03:01.900 align:start position:0% very much this on the plate that we should<00:02:58.970> more<00:02:59.390> emphasis<00:02:59.870> on<00:03:00.019> this<00:03:00.140> or<00:03:00.860> that<00:03:01.790> we 00:03:01.900 --> 00:03:01.910 align:start position:0% should more emphasis on this or that we 00:03:01.910 --> 00:03:03.880 align:start position:0% should more emphasis on this or that we should<00:03:02.030> emphasis<00:03:02.390> on<00:03:02.510> this<00:03:02.660> even<00:03:03.019> more<00:03:03.200> we<00:03:03.620> do 00:03:03.880 --> 00:03:03.890 align:start position:0% should emphasis on this even more we do 00:03:03.890 --> 00:03:05.410 align:start position:0% should emphasis on this even more we do get<00:03:04.040> it<00:03:04.160> getting<00:03:04.459> better<00:03:04.610> and<00:03:04.730> review<00:03:05.120> times 00:03:05.410 --> 00:03:05.420 align:start position:0% get it getting better and review times 00:03:05.420 --> 00:03:07.990 align:start position:0% get it getting better and review times we<00:03:05.750> are<00:03:05.780> not<00:03:05.959> there<00:03:06.530> where<00:03:06.830> we<00:03:06.980> want<00:03:07.370> to<00:03:07.489> be<00:03:07.610> but 00:03:07.990 --> 00:03:08.000 align:start position:0% we are not there where we want to be but 00:03:08.000 --> 00:03:09.190 align:start position:0% we are not there where we want to be but I<00:03:08.209> have<00:03:08.299> this<00:03:08.420> very<00:03:08.569> much<00:03:08.750> on<00:03:08.840> the<00:03:08.900> plate<00:03:08.989> that 00:03:09.190 --> 00:03:09.200 align:start position:0% I have this very much on the plate that 00:03:09.200 --> 00:03:11.440 align:start position:0% I have this very much on the plate that we<00:03:09.319> won't<00:03:09.709> even<00:03:09.830> prove<00:03:10.099> there<00:03:10.340> I<00:03:10.549> just 00:03:11.440 --> 00:03:11.450 align:start position:0% we won't even prove there I just 00:03:11.450 --> 00:03:12.940 align:start position:0% we won't even prove there I just introduced<00:03:11.810> in<00:03:11.900> labeling<00:03:12.319> system<00:03:12.650> as<00:03:12.769> well 00:03:12.940 --> 00:03:12.950 align:start position:0% introduced in labeling system as well 00:03:12.950 --> 00:03:14.530 align:start position:0% introduced in labeling system as well and<00:03:13.250> we've<00:03:13.459> got<00:03:13.670> a<00:03:13.700> new<00:03:13.970> corporation<00:03:14.450> with 00:03:14.530 --> 00:03:14.540 align:start position:0% and we've got a new corporation with 00:03:14.540 --> 00:03:17.349 align:start position:0% and we've got a new corporation with good<00:03:14.690> coin<00:03:14.870> so<00:03:15.500> many<00:03:16.069> ways<00:03:16.370> to<00:03:16.760> contribute<00:03:17.090> to 00:03:17.349 --> 00:03:17.359 align:start position:0% good coin so many ways to contribute to 00:03:17.359 --> 00:03:20.080 align:start position:0% good coin so many ways to contribute to our<00:03:17.390> libraries<00:03:17.840> and<00:03:17.870> and<00:03:18.410> also<00:03:18.890> talk<00:03:19.280> to<00:03:19.310> us<00:03:19.579> at 00:03:20.080 --> 00:03:20.090 align:start position:0% our libraries and and also talk to us at 00:03:20.090 --> 00:03:22.509 align:start position:0% our libraries and and also talk to us at Def<00:03:20.299> Con<00:03:20.470> just<00:03:21.470> remember<00:03:21.769> our<00:03:21.799> faces<00:03:22.100> and<00:03:22.370> very 00:03:22.509 --> 00:03:22.519 align:start position:0% Def Con just remember our faces and very 00:03:22.519 --> 00:03:24.520 align:start position:0% Def Con just remember our faces and very happy<00:03:22.880> if<00:03:23.030> if<00:03:23.269> we<00:03:23.420> get<00:03:23.570> an<00:03:23.660> exchange<00:03:24.140> later 00:03:24.520 --> 00:03:24.530 align:start position:0% happy if if we get an exchange later 00:03:24.530 --> 00:03:26.380 align:start position:0% happy if if we get an exchange later about<00:03:24.799> what<00:03:25.430> we<00:03:25.549> can<00:03:25.700> do<00:03:25.820> and<00:03:25.940> what<00:03:26.060> we<00:03:26.150> can<00:03:26.299> do 00:03:26.380 --> 00:03:26.390 align:start position:0% about what we can do and what we can do 00:03:26.390 --> 00:03:30.309 align:start position:0% about what we can do and what we can do better<00:03:26.540> actually<00:03:27.940> um<00:03:28.940> these<00:03:29.540> are<00:03:29.600> some<00:03:29.780> of<00:03:30.230> our 00:03:30.309 --> 00:03:30.319 align:start position:0% better actually um these are some of our 00:03:30.319 --> 00:03:31.630 align:start position:0% better actually um these are some of our libraries<00:03:30.680> I<00:03:30.739> don't<00:03:31.069> want<00:03:31.220> to<00:03:31.280> dig<00:03:31.400> in<00:03:31.519> there 00:03:31.630 --> 00:03:31.640 align:start position:0% libraries I don't want to dig in there 00:03:31.640 --> 00:03:35.020 align:start position:0% libraries I don't want to dig in there too<00:03:32.090> deep<00:03:32.359> the<00:03:32.630> virtual<00:03:33.590> machine<00:03:34.030> transaction 00:03:35.020 --> 00:03:35.030 align:start position:0% too deep the virtual machine transaction 00:03:35.030 --> 00:03:36.789 align:start position:0% too deep the virtual machine transaction library<00:03:35.390> miracle<00:03:35.690> patricia<00:03:35.989> tree<00:03:36.230> various 00:03:36.789 --> 00:03:36.799 align:start position:0% library miracle patricia tree various 00:03:36.799 --> 00:03:38.920 align:start position:0% library miracle patricia tree various utility<00:03:37.310> libraries<00:03:37.790> and<00:03:38.120> an<00:03:38.359> implementation 00:03:38.920 --> 00:03:38.930 align:start position:0% utility libraries and an implementation 00:03:38.930 --> 00:03:41.770 align:start position:0% utility libraries and an implementation of<00:03:39.380> base<00:03:39.590> level<00:03:40.269> protocols<00:03:41.269> like<00:03:41.420> the<00:03:41.569> ROP 00:03:41.770 --> 00:03:41.780 align:start position:0% of base level protocols like the ROP 00:03:41.780 --> 00:03:44.530 align:start position:0% of base level protocols like the ROP library<00:03:42.319> for<00:03:42.500> example<00:03:42.889> and<00:03:43.069> many<00:03:43.790> others<00:03:44.120> just 00:03:44.530 --> 00:03:44.540 align:start position:0% library for example and many others just 00:03:44.540 --> 00:03:46.059 align:start position:0% library for example and many others just to<00:03:44.600> give<00:03:44.720> you<00:03:44.810> a<00:03:44.840> short<00:03:45.049> overview<00:03:45.230> but<00:03:45.829> you<00:03:45.920> can 00:03:46.059 --> 00:03:46.069 align:start position:0% to give you a short overview but you can 00:03:46.069 --> 00:03:48.430 align:start position:0% to give you a short overview but you can look<00:03:46.220> at<00:03:46.370> the<00:03:46.459> organization<00:03:47.440> getup 00:03:48.430 --> 00:03:48.440 align:start position:0% look at the organization getup 00:03:48.440 --> 00:03:50.080 align:start position:0% look at the organization getup organization<00:03:49.010> for<00:03:49.250> for<00:03:49.670> a<00:03:49.700> better<00:03:49.850> overview 00:03:50.080 --> 00:03:50.090 align:start position:0% organization for for a better overview 00:03:50.090 --> 00:03:52.750 align:start position:0% organization for for a better overview on<00:03:50.420> that<00:03:50.630> and<00:03:51.170> there<00:03:52.069> was<00:03:52.190> already<00:03:52.340> my 00:03:52.750 --> 00:03:52.760 align:start position:0% on that and there was already my 00:03:52.760 --> 00:03:54.099 align:start position:0% on that and there was already my introduction<00:03:53.239> we<00:03:53.359> have<00:03:53.450> many<00:03:53.630> speakers<00:03:53.989> today 00:03:54.099 --> 00:03:54.109 align:start position:0% introduction we have many speakers today 00:03:54.109 --> 00:03:56.590 align:start position:0% introduction we have many speakers today and<00:03:54.680> next<00:03:54.829> is<00:03:55.010> Jared<00:03:55.370> who<00:03:55.940> will<00:03:56.060> give<00:03:56.239> you<00:03:56.389> some 00:03:56.590 --> 00:03:56.600 align:start position:0% and next is Jared who will give you some 00:03:56.600 --> 00:04:00.990 align:start position:0% and next is Jared who will give you some update<00:03:56.959> on<00:03:57.139> the<00:03:57.260> virtual<00:03:57.560> machine<00:03:57.829> thank<00:03:58.549> you 00:04:00.990 --> 00:04:01.000 align:start position:0% 00:04:01.000 --> 00:04:05.979 align:start position:0% so<00:04:02.000> hi<00:04:02.299> I'm<00:04:02.989> Jared<00:04:03.560> wah<00:04:03.739> singer<00:04:04.100> I<00:04:04.790> have<00:04:05.750> done 00:04:05.979 --> 00:04:05.989 align:start position:0% so hi I'm Jared wah singer I have done 00:04:05.989 --> 00:04:08.170 align:start position:0% so hi I'm Jared wah singer I have done quite<00:04:06.260> a<00:04:06.290> bit<00:04:06.350> of<00:04:06.470> work<00:04:06.680> on<00:04:06.889> the<00:04:07.430> etherium<00:04:07.880> Jas 00:04:08.170 --> 00:04:08.180 align:start position:0% quite a bit of work on the etherium Jas 00:04:08.180 --> 00:04:10.150 align:start position:0% quite a bit of work on the etherium Jas implementation<00:04:09.049> of<00:04:09.139> the<00:04:09.230> virtual<00:04:09.590> machine<00:04:09.889> as 00:04:10.150 --> 00:04:10.160 align:start position:0% implementation of the virtual machine as 00:04:10.160 --> 00:04:12.940 align:start position:0% implementation of the virtual machine as well<00:04:10.579> as<00:04:10.730> other<00:04:10.970> projects<00:04:11.450> the<00:04:11.950> virtual 00:04:12.940 --> 00:04:12.950 align:start position:0% well as other projects the virtual 00:04:12.950 --> 00:04:15.490 align:start position:0% well as other projects the virtual machine<00:04:13.220> is<00:04:13.489> designed<00:04:13.700> to<00:04:14.090> be<00:04:14.239> a<00:04:14.780> web<00:04:15.260> first 00:04:15.490 --> 00:04:15.500 align:start position:0% machine is designed to be a web first 00:04:15.500 --> 00:04:18.069 align:start position:0% machine is designed to be a web first library<00:04:16.160> it's<00:04:17.120> embedded<00:04:17.419> in<00:04:17.630> tools<00:04:17.870> like 00:04:18.069 --> 00:04:18.079 align:start position:0% library it's embedded in tools like 00:04:18.079 --> 00:04:21.279 align:start position:0% library it's embedded in tools like remix<00:04:18.500> and<00:04:18.769> used<00:04:19.220> in<00:04:19.910> other<00:04:20.209> tools<00:04:20.570> like<00:04:21.049> meta 00:04:21.279 --> 00:04:21.289 align:start position:0% remix and used in other tools like meta 00:04:21.289 --> 00:04:25.300 align:start position:0% remix and used in other tools like meta mask<00:04:21.500> it<00:04:22.810> captures<00:04:23.810> ëthere<00:04:24.560> iam<00:04:24.650> J<00:04:24.800> theorem 00:04:25.300 --> 00:04:25.310 align:start position:0% mask it captures ëthere iam J theorem 00:04:25.310 --> 00:04:26.180 align:start position:0% mask it captures ëthere iam J theorem state<00:04:25.610> transition 00:04:26.180 --> 00:04:26.190 align:start position:0% state transition 00:04:26.190 --> 00:04:28.970 align:start position:0% state transition rules<00:04:26.400> as<00:04:26.610> defined<00:04:27.000> by<00:04:27.120> the<00:04:27.350> official<00:04:28.350> test 00:04:28.970 --> 00:04:28.980 align:start position:0% rules as defined by the official test 00:04:28.980 --> 00:04:32.960 align:start position:0% rules as defined by the official test suite<00:04:29.250> and<00:04:29.690> it<00:04:30.690> provides<00:04:31.460> we<00:04:32.460> like<00:04:32.700> to<00:04:32.820> think 00:04:32.960 --> 00:04:32.970 align:start position:0% suite and it provides we like to think 00:04:32.970 --> 00:04:33.950 align:start position:0% suite and it provides we like to think that<00:04:33.000> it<00:04:33.150> provides<00:04:33.420> a<00:04:33.540> modular 00:04:33.950 --> 00:04:33.960 align:start position:0% that it provides a modular 00:04:33.960 --> 00:04:35.780 align:start position:0% that it provides a modular implementation<00:04:34.650> of<00:04:34.770> the<00:04:34.860> various<00:04:35.160> blockchain 00:04:35.780 --> 00:04:35.790 align:start position:0% implementation of the various blockchain 00:04:35.790 --> 00:04:39.170 align:start position:0% implementation of the various blockchain components<00:04:36.420> like<00:04:36.660> the<00:04:37.020> block<00:04:37.920> blockchain<00:04:38.580> the 00:04:39.170 --> 00:04:39.180 align:start position:0% components like the block blockchain the 00:04:39.180 --> 00:04:42.230 align:start position:0% components like the block blockchain the VM<00:04:39.480> it's<00:04:40.380> so<00:04:40.680> that<00:04:41.190> the<00:04:41.430> community<00:04:41.940> can<00:04:42.180> make 00:04:42.230 --> 00:04:42.240 align:start position:0% VM it's so that the community can make 00:04:42.240 --> 00:04:45.020 align:start position:0% VM it's so that the community can make use<00:04:42.690> of<00:04:42.720> them<00:04:43.050> in<00:04:43.320> the<00:04:43.530> browser<00:04:43.740> and<00:04:44.070> with 00:04:45.020 --> 00:04:45.030 align:start position:0% use of them in the browser and with 00:04:45.030 --> 00:04:49.280 align:start position:0% use of them in the browser and with nodejs<00:04:45.450> applications<00:04:47.090> so<00:04:48.090> just<00:04:49.080> to<00:04:49.140> give<00:04:49.260> you 00:04:49.280 --> 00:04:49.290 align:start position:0% nodejs applications so just to give you 00:04:49.290 --> 00:04:53.560 align:start position:0% nodejs applications so just to give you an<00:04:49.920> idea<00:04:50.190> of<00:04:50.670> what<00:04:51.450> we<00:04:51.690> are<00:04:51.720> doing<00:04:52.020> regarding 00:04:53.560 --> 00:04:53.570 align:start position:0% an idea of what we are doing regarding 00:04:53.570 --> 00:04:56.300 align:start position:0% an idea of what we are doing regarding updating<00:04:54.570> to<00:04:54.840> Constantinople<00:04:55.770> we've 00:04:56.300 --> 00:04:56.310 align:start position:0% updating to Constantinople we've 00:04:56.310 --> 00:04:57.890 align:start position:0% updating to Constantinople we've implemented<00:04:56.880> all<00:04:57.180> a<00:04:57.420> IPs 00:04:57.890 --> 00:04:57.900 align:start position:0% implemented all a IPs 00:04:57.900 --> 00:05:00.950 align:start position:0% implemented all a IPs in<00:04:58.020> the<00:04:58.170> VM<00:04:58.640> where<00:04:59.640> we're<00:05:00.360> still<00:05:00.630> waiting<00:05:00.930> for 00:05:00.950 --> 00:05:00.960 align:start position:0% in the VM where we're still waiting for 00:05:00.960 --> 00:05:03.980 align:start position:0% in the VM where we're still waiting for some<00:05:01.590> additional<00:05:02.160> testing<00:05:02.850> around<00:05:03.210> xt<00:05:03.780> code 00:05:03.980 --> 00:05:03.990 align:start position:0% some additional testing around xt code 00:05:03.990 --> 00:05:06.590 align:start position:0% some additional testing around xt code hash<00:05:04.370> and<00:05:05.370> we<00:05:05.490> thank<00:05:05.670> the<00:05:05.820> testing<00:05:06.210> team<00:05:06.360> so 00:05:06.590 --> 00:05:06.600 align:start position:0% hash and we thank the testing team so 00:05:06.600 --> 00:05:11.060 align:start position:0% hash and we thank the testing team so much<00:05:06.780> for<00:05:07.940> doing<00:05:08.960> the<00:05:09.960> hard<00:05:10.170> job<00:05:10.410> to<00:05:10.740> provide 00:05:11.060 --> 00:05:11.070 align:start position:0% much for doing the hard job to provide 00:05:11.070 --> 00:05:14.810 align:start position:0% much for doing the hard job to provide those<00:05:11.310> tests<00:05:11.550> to<00:05:11.730> us<00:05:12.470> we<00:05:13.470> also<00:05:13.620> have<00:05:14.250> a<00:05:14.610> few 00:05:14.810 --> 00:05:14.820 align:start position:0% those tests to us we also have a few 00:05:14.820 --> 00:05:17.390 align:start position:0% those tests to us we also have a few edge<00:05:14.970> cases<00:05:15.240> in<00:05:15.720> the<00:05:16.110> create<00:05:16.380> to<00:05:16.530> opcode<00:05:16.980> that 00:05:17.390 --> 00:05:17.400 align:start position:0% edge cases in the create to opcode that 00:05:17.400 --> 00:05:19.610 align:start position:0% edge cases in the create to opcode that we're<00:05:17.670> working<00:05:18.090> to<00:05:18.360> fix<00:05:18.570> and<00:05:18.990> we're<00:05:19.290> thinking 00:05:19.610 --> 00:05:19.620 align:start position:0% we're working to fix and we're thinking 00:05:19.620 --> 00:05:21.800 align:start position:0% we're working to fix and we're thinking that<00:05:19.830> a<00:05:20.010> release<00:05:20.400> should<00:05:20.850> come<00:05:21.090> around<00:05:21.420> two<00:05:21.690> to 00:05:21.800 --> 00:05:21.810 align:start position:0% that a release should come around two to 00:05:21.810 --> 00:05:23.600 align:start position:0% that a release should come around two to three<00:05:22.020> weeks<00:05:22.170> from<00:05:22.410> now 00:05:23.600 --> 00:05:23.610 align:start position:0% three weeks from now 00:05:23.610 --> 00:05:28.130 align:start position:0% three weeks from now in<00:05:23.880> addition<00:05:24.530> thanks<00:05:25.530> to<00:05:26.930> generous<00:05:27.930> community 00:05:28.130 --> 00:05:28.140 align:start position:0% in addition thanks to generous community 00:05:28.140 --> 00:05:32.450 align:start position:0% in addition thanks to generous community contributions<00:05:29.040> we<00:05:29.340> have<00:05:29.730> a<00:05:30.000> brand<00:05:30.360> new<00:05:31.460> API 00:05:32.450 --> 00:05:32.460 align:start position:0% contributions we have a brand new API 00:05:32.460 --> 00:05:33.940 align:start position:0% contributions we have a brand new API test<00:05:32.850> suite<00:05:33.090> for 00:05:33.940 --> 00:05:33.950 align:start position:0% test suite for 00:05:33.950 --> 00:05:37.120 align:start position:0% test suite for etherium<00:05:34.950> Jas<00:05:35.280> and<00:05:35.520> that<00:05:35.880> has<00:05:36.180> brought<00:05:36.450> our 00:05:37.120 --> 00:05:37.130 align:start position:0% etherium Jas and that has brought our 00:05:37.130 --> 00:05:42.260 align:start position:0% etherium Jas and that has brought our test<00:05:38.130> coverage<00:05:38.550> to<00:05:38.850> 93%<00:05:39.419> so<00:05:40.820> you<00:05:41.820> know<00:05:41.940> like 00:05:42.260 --> 00:05:42.270 align:start position:0% test coverage to 93% so you know like 00:05:42.270 --> 00:05:44.150 align:start position:0% test coverage to 93% so you know like like<00:05:42.600> the<00:05:42.720> whole<00:05:42.840> the<00:05:43.260> the<00:05:43.710> theme<00:05:43.919> of<00:05:43.950> this 00:05:44.150 --> 00:05:44.160 align:start position:0% like the whole the the theme of this 00:05:44.160 --> 00:05:45.530 align:start position:0% like the whole the the theme of this conference<00:05:44.370> I'd<00:05:44.910> like<00:05:45.120> to<00:05:45.240> think<00:05:45.330> is<00:05:45.510> that 00:05:45.530 --> 00:05:45.540 align:start position:0% conference I'd like to think is that 00:05:45.540 --> 00:05:47.120 align:start position:0% conference I'd like to think is that we're<00:05:45.840> trying<00:05:46.169> to<00:05:46.260> put<00:05:46.530> the<00:05:46.590> spotlight<00:05:46.800> back 00:05:47.120 --> 00:05:47.130 align:start position:0% we're trying to put the spotlight back 00:05:47.130 --> 00:05:49.510 align:start position:0% we're trying to put the spotlight back on<00:05:47.310> the<00:05:47.430> community<00:05:47.820> and<00:05:48.060> I<00:05:48.270> think<00:05:48.300> that<00:05:48.540> this 00:05:49.510 --> 00:05:49.520 align:start position:0% on the community and I think that this 00:05:49.520 --> 00:05:52.340 align:start position:0% on the community and I think that this demonstrates<00:05:50.520> that<00:05:50.640> and<00:05:51.060> you<00:05:51.840> know<00:05:51.930> as<00:05:52.050> Holger 00:05:52.340 --> 00:05:52.350 align:start position:0% demonstrates that and you know as Holger 00:05:52.350 --> 00:05:54.409 align:start position:0% demonstrates that and you know as Holger said<00:05:52.560> we've<00:05:52.740> just<00:05:52.980> gotten<00:05:53.250> so<00:05:53.550> many<00:05:53.730> community 00:05:54.409 --> 00:05:54.419 align:start position:0% said we've just gotten so many community 00:05:54.419 --> 00:05:58.790 align:start position:0% said we've just gotten so many community contributions<00:05:55.320> and<00:05:55.470> it's<00:05:55.790> so<00:05:56.790> wonderful<00:05:57.800> so 00:05:58.790 --> 00:05:58.800 align:start position:0% contributions and it's so wonderful so 00:05:58.800 --> 00:06:01.159 align:start position:0% contributions and it's so wonderful so just<00:05:59.640> to<00:05:59.760> kind<00:05:59.910> of<00:06:00.000> give<00:06:00.180> a<00:06:00.210> brief<00:06:00.510> outlook<00:06:00.960> on 00:06:01.159 --> 00:06:01.169 align:start position:0% just to kind of give a brief outlook on 00:06:01.169 --> 00:06:04.990 align:start position:0% just to kind of give a brief outlook on what<00:06:01.800> the<00:06:02.550> future<00:06:02.850> holds<00:06:03.210> we're<00:06:04.110> looking<00:06:04.440> at 00:06:04.990 --> 00:06:05.000 align:start position:0% what the future holds we're looking at 00:06:05.000 --> 00:06:07.730 align:start position:0% what the future holds we're looking at integration<00:06:06.000> with<00:06:06.300> a<00:06:06.480> wasum<00:06:06.900> which<00:06:07.200> is<00:06:07.410> the 00:06:07.730 --> 00:06:07.740 align:start position:0% integration with a wasum which is the 00:06:07.740 --> 00:06:11.600 align:start position:0% integration with a wasum which is the execution<00:06:08.340> layer<00:06:09.090> for<00:06:09.450> aetherium<00:06:09.750> 2.0<00:06:10.610> but 00:06:11.600 --> 00:06:11.610 align:start position:0% execution layer for aetherium 2.0 but 00:06:11.610 --> 00:06:14.720 align:start position:0% execution layer for aetherium 2.0 but there's<00:06:11.910> a<00:06:12.000> few<00:06:12.770> difficulties<00:06:13.770> here<00:06:14.280> that<00:06:14.520> I 00:06:14.720 --> 00:06:14.730 align:start position:0% there's a few difficulties here that I 00:06:14.730 --> 00:06:19.220 align:start position:0% there's a few difficulties here that I can<00:06:15.570> kind<00:06:15.780> of<00:06:15.840> touch<00:06:16.020> on<00:06:16.340> so<00:06:17.340> II<00:06:17.700> wasum<00:06:18.230> defines 00:06:19.220 --> 00:06:19.230 align:start position:0% can kind of touch on so II wasum defines 00:06:19.230 --> 00:06:21.380 align:start position:0% can kind of touch on so II wasum defines an<00:06:19.410> API<00:06:19.770> that<00:06:20.040> isn't<00:06:20.340> exactly<00:06:20.430> compatible 00:06:21.380 --> 00:06:21.390 align:start position:0% an API that isn't exactly compatible 00:06:21.390 --> 00:06:23.000 align:start position:0% an API that isn't exactly compatible with<00:06:21.480> the<00:06:21.570> browser<00:06:21.810> in<00:06:22.230> the<00:06:22.350> sense<00:06:22.590> that<00:06:22.680> it's 00:06:23.000 --> 00:06:23.010 align:start position:0% with the browser in the sense that it's 00:06:23.010 --> 00:06:26.930 align:start position:0% with the browser in the sense that it's synchronous<00:06:23.520> whereas<00:06:23.970> the<00:06:24.660> browser<00:06:25.940> anybody 00:06:26.930 --> 00:06:26.940 align:start position:0% synchronous whereas the browser anybody 00:06:26.940 --> 00:06:29.570 align:start position:0% synchronous whereas the browser anybody who's<00:06:27.090> program<00:06:27.419> j/s<00:06:27.810> knows<00:06:28.169> that<00:06:28.590> everything 00:06:29.570 --> 00:06:29.580 align:start position:0% who's program j/s knows that everything 00:06:29.580 --> 00:06:31.000 align:start position:0% who's program j/s knows that everything is<00:06:29.700> async 00:06:31.000 --> 00:06:31.010 align:start position:0% is async 00:06:31.010 --> 00:06:34.400 align:start position:0% is async so<00:06:32.060> we<00:06:33.060> have<00:06:33.150> a<00:06:33.180> few<00:06:33.390> possible<00:06:33.900> solutions 00:06:34.400 --> 00:06:34.410 align:start position:0% so we have a few possible solutions 00:06:34.410 --> 00:06:36.800 align:start position:0% so we have a few possible solutions we're<00:06:34.740> looking<00:06:35.160> at<00:06:35.310> one<00:06:35.729> is<00:06:35.910> to<00:06:36.150> rewrite<00:06:36.600> the 00:06:36.800 --> 00:06:36.810 align:start position:0% we're looking at one is to rewrite the 00:06:36.810 --> 00:06:39.140 align:start position:0% we're looking at one is to rewrite the VM<00:06:37.080> to<00:06:37.110> be<00:06:37.530> synchronous<00:06:38.039> I<00:06:38.400> don't<00:06:38.700> personally 00:06:39.140 --> 00:06:39.150 align:start position:0% VM to be synchronous I don't personally 00:06:39.150 --> 00:06:39.710 align:start position:0% VM to be synchronous I don't personally think<00:06:39.180> that<00:06:39.390> will 00:06:39.710 --> 00:06:39.720 align:start position:0% think that will 00:06:39.720 --> 00:06:43.000 align:start position:0% think that will work<00:06:39.920> for<00:06:40.920> various<00:06:41.250> reasons<00:06:41.730> but<00:06:42.000> another 00:06:43.000 --> 00:06:43.010 align:start position:0% work for various reasons but another 00:06:43.010 --> 00:06:45.110 align:start position:0% work for various reasons but another approach<00:06:44.010> could<00:06:44.340> be<00:06:44.490> to<00:06:44.670> implement<00:06:44.880> a 00:06:45.110 --> 00:06:45.120 align:start position:0% approach could be to implement a 00:06:45.120 --> 00:06:48.290 align:start position:0% approach could be to implement a translation<00:06:45.810> tool<00:06:46.250> and<00:06:47.250> I<00:06:47.640> won't<00:06:47.820> go<00:06:47.970> into<00:06:48.000> too 00:06:48.290 --> 00:06:48.300 align:start position:0% translation tool and I won't go into too 00:06:48.300 --> 00:06:51.110 align:start position:0% translation tool and I won't go into too much<00:06:48.330> detail<00:06:48.660> because<00:06:49.080> we<00:06:49.620> could<00:06:49.770> we<00:06:49.980> could<00:06:50.130> go 00:06:51.110 --> 00:06:51.120 align:start position:0% much detail because we could we could go 00:06:51.120 --> 00:06:55.580 align:start position:0% much detail because we could we could go a<00:06:51.150> whole<00:06:51.390> day<00:06:51.450> on<00:06:51.810> that<00:06:52.970> so<00:06:53.970> if<00:06:54.420> you<00:06:54.990> want<00:06:55.290> to 00:06:55.580 --> 00:06:55.590 align:start position:0% a whole day on that so if you want to 00:06:55.590 --> 00:06:57.680 align:start position:0% a whole day on that so if you want to know<00:06:55.710> more<00:06:55.890> about<00:06:56.010> this<00:06:56.340> I<00:06:56.580> would<00:06:57.240> invite<00:06:57.660> you 00:06:57.680 --> 00:06:57.690 align:start position:0% know more about this I would invite you 00:06:57.690 --> 00:07:00.770 align:start position:0% know more about this I would invite you to<00:06:58.410> go<00:06:58.800> to<00:06:58.860> this<00:06:59.100> link<00:06:59.400> I<00:06:59.640> have<00:07:00.000> under<00:07:00.600> more 00:07:00.770 --> 00:07:00.780 align:start position:0% to go to this link I have under more 00:07:00.780 --> 00:07:03.230 align:start position:0% to go to this link I have under more resources<00:07:01.260> and<00:07:01.560> we<00:07:01.950> would<00:07:02.130> very<00:07:02.790> much<00:07:02.910> welcome 00:07:03.230 --> 00:07:03.240 align:start position:0% resources and we would very much welcome 00:07:03.240 --> 00:07:06.470 align:start position:0% resources and we would very much welcome contributions<00:07:04.110> on<00:07:04.260> this<00:07:04.410> front<00:07:04.680> so<00:07:05.210> if<00:07:06.210> you 00:07:06.470 --> 00:07:06.480 align:start position:0% contributions on this front so if you 00:07:06.480 --> 00:07:07.850 align:start position:0% contributions on this front so if you want<00:07:06.660> to<00:07:06.720> if<00:07:06.930> you<00:07:07.020> want<00:07:07.140> to<00:07:07.260> contribute<00:07:07.590> on 00:07:07.850 --> 00:07:07.860 align:start position:0% want to if you want to contribute on 00:07:07.860 --> 00:07:09.200 align:start position:0% want to if you want to contribute on this<00:07:08.070> if<00:07:08.220> you<00:07:08.250> want<00:07:08.430> to<00:07:08.490> do<00:07:08.580> something<00:07:08.850> please 00:07:09.200 --> 00:07:09.210 align:start position:0% this if you want to do something please 00:07:09.210 --> 00:07:12.680 align:start position:0% this if you want to do something please reach<00:07:09.480> out<00:07:09.720> we're<00:07:10.200> on<00:07:10.290> git<00:07:10.500> er<00:07:10.970> is<00:07:11.970> generally<00:07:12.630> a 00:07:12.680 --> 00:07:12.690 align:start position:0% reach out we're on git er is generally a 00:07:12.690 --> 00:07:15.230 align:start position:0% reach out we're on git er is generally a good<00:07:12.780> place<00:07:12.990> to<00:07:13.140> find<00:07:13.320> us<00:07:13.700> I'm<00:07:14.700> gonna<00:07:14.880> pass 00:07:15.230 --> 00:07:15.240 align:start position:0% good place to find us I'm gonna pass 00:07:15.240 --> 00:07:18.500 align:start position:0% good place to find us I'm gonna pass this<00:07:15.510> off<00:07:15.750> to<00:07:15.890> Vinay<00:07:17.090> who<00:07:18.090> works<00:07:18.270> on<00:07:18.420> the 00:07:18.500 --> 00:07:18.510 align:start position:0% this off to Vinay who works on the 00:07:18.510 --> 00:07:27.680 align:start position:0% this off to Vinay who works on the client<00:07:24.980> hi<00:07:25.980> my<00:07:26.460> name<00:07:26.580> is<00:07:26.640> Vinay<00:07:26.940> and<00:07:27.210> working 00:07:27.680 --> 00:07:27.690 align:start position:0% client hi my name is Vinay and working 00:07:27.690 --> 00:07:30.710 align:start position:0% client hi my name is Vinay and working on<00:07:27.780> the<00:07:27.870> etherium<00:07:28.560> JavaScript<00:07:29.100> client<00:07:29.400> and<00:07:30.300> so 00:07:30.710 --> 00:07:30.720 align:start position:0% on the etherium JavaScript client and so 00:07:30.720 --> 00:07:33.020 align:start position:0% on the etherium JavaScript client and so why<00:07:30.810> do<00:07:30.870> we<00:07:30.990> need<00:07:31.169> another<00:07:31.470> client<00:07:32.070> so<00:07:32.790> our 00:07:33.020 --> 00:07:33.030 align:start position:0% why do we need another client so our 00:07:33.030 --> 00:07:35.300 align:start position:0% why do we need another client so our goal<00:07:33.240> is<00:07:33.390> not<00:07:33.810> to<00:07:33.870> actually<00:07:34.380> build<00:07:34.620> another 00:07:35.300 --> 00:07:35.310 align:start position:0% goal is not to actually build another 00:07:35.310 --> 00:07:37.550 align:start position:0% goal is not to actually build another consensus<00:07:35.910> critical<00:07:36.330> client<00:07:36.990> like<00:07:37.110> death<00:07:37.350> or 00:07:37.550 --> 00:07:37.560 align:start position:0% consensus critical client like death or 00:07:37.560 --> 00:07:40.640 align:start position:0% consensus critical client like death or parity<00:07:37.980> instead<00:07:38.910> we<00:07:39.780> want<00:07:40.260> to<00:07:40.320> build<00:07:40.470> a 00:07:40.640 --> 00:07:40.650 align:start position:0% parity instead we want to build a 00:07:40.650 --> 00:07:42.470 align:start position:0% parity instead we want to build a working<00:07:41.040> client<00:07:41.520> to<00:07:41.610> help<00:07:41.730> harden<00:07:42.180> some<00:07:42.390> of 00:07:42.470 --> 00:07:42.480 align:start position:0% working client to help harden some of 00:07:42.480 --> 00:07:44.720 align:start position:0% working client to help harden some of the<00:07:42.630> other<00:07:43.350> existing<00:07:43.800> JavaScript<00:07:44.130> libraries 00:07:44.720 --> 00:07:44.730 align:start position:0% the other existing JavaScript libraries 00:07:44.730 --> 00:07:46.970 align:start position:0% the other existing JavaScript libraries like<00:07:44.970> the<00:07:45.000> VM<00:07:45.330> and<00:07:45.690> that<00:07:46.350> merkel<00:07:46.620> patrician 00:07:46.970 --> 00:07:46.980 align:start position:0% like the VM and that merkel patrician 00:07:46.980 --> 00:07:50.840 align:start position:0% like the VM and that merkel patrician tree<00:07:47.220> etc<00:07:47.990> another<00:07:48.990> goal<00:07:49.350> is<00:07:49.530> to<00:07:49.800> provide<00:07:50.520> an 00:07:50.840 --> 00:07:50.850 align:start position:0% tree etc another goal is to provide an 00:07:50.850 --> 00:07:53.690 align:start position:0% tree etc another goal is to provide an R&D<00:07:51.090> platform<00:07:51.440> for<00:07:52.440> new<00:07:52.590> features<00:07:52.770> like<00:07:53.100> lit 00:07:53.690 --> 00:07:53.700 align:start position:0% R&D platform for new features like lit 00:07:53.700 --> 00:07:57.800 align:start position:0% R&D platform for new features like lit PDP<00:07:54.060> support<00:07:54.890> the<00:07:55.890> etherium<00:07:56.729> 2.0<00:07:57.360> stateless 00:07:57.800 --> 00:07:57.810 align:start position:0% PDP support the etherium 2.0 stateless 00:07:57.810 --> 00:08:00.560 align:start position:0% PDP support the etherium 2.0 stateless clients<00:07:58.169> for<00:07:58.590> example<00:07:58.669> and<00:07:59.669> then<00:07:59.790> in<00:08:00.120> you<00:08:00.450> know 00:08:00.560 --> 00:08:00.570 align:start position:0% clients for example and then in you know 00:08:00.570 --> 00:08:03.170 align:start position:0% clients for example and then in you know future<00:08:00.900> research<00:08:01.620> efforts<00:08:01.979> and<00:08:02.280> finally<00:08:03.030> I'm 00:08:03.170 --> 00:08:03.180 align:start position:0% future research efforts and finally I'm 00:08:03.180 --> 00:08:04.850 align:start position:0% future research efforts and finally I'm wanted<00:08:03.690> to<00:08:03.780> provide<00:08:04.020> an<00:08:04.200> educational<00:08:04.710> tool 00:08:04.850 --> 00:08:04.860 align:start position:0% wanted to provide an educational tool 00:08:04.860 --> 00:08:07.520 align:start position:0% wanted to provide an educational tool javascript<00:08:05.700> is<00:08:05.850> really<00:08:06.120> friendly<00:08:07.050> to<00:08:07.260> a<00:08:07.290> large 00:08:07.520 --> 00:08:07.530 align:start position:0% javascript is really friendly to a large 00:08:07.530 --> 00:08:09.350 align:start position:0% javascript is really friendly to a large community<00:08:07.919> of<00:08:08.190> developers<00:08:08.370> and<00:08:08.910> it's<00:08:09.150> a<00:08:09.240> great 00:08:09.350 --> 00:08:09.360 align:start position:0% community of developers and it's a great 00:08:09.360 --> 00:08:13.219 align:start position:0% community of developers and it's a great way<00:08:09.540> to<00:08:09.900> to<00:08:10.620> learn<00:08:10.770> about<00:08:10.919> the<00:08:11.910> details<00:08:12.810> of<00:08:13.020> how 00:08:13.219 --> 00:08:13.229 align:start position:0% way to to learn about the details of how 00:08:13.229 --> 00:08:17.330 align:start position:0% way to to learn about the details of how a<00:08:13.260> theorem<00:08:13.680> client<00:08:14.100> would<00:08:14.669> work<00:08:14.850> and<00:08:16.190> so<00:08:17.190> in 00:08:17.330 --> 00:08:17.340 align:start position:0% a theorem client would work and so in 00:08:17.340 --> 00:08:19.460 align:start position:0% a theorem client would work and so in terms<00:08:17.460> of<00:08:17.580> the<00:08:17.700> architecture<00:08:18.270> is<00:08:18.960> heavily 00:08:19.460 --> 00:08:19.470 align:start position:0% terms of the architecture is heavily 00:08:19.470 --> 00:08:22.870 align:start position:0% terms of the architecture is heavily inspired<00:08:19.830> by<00:08:20.720> Bitcoin<00:08:21.720> which<00:08:21.960> is<00:08:22.200> the<00:08:22.470> Bitcoin 00:08:22.870 --> 00:08:22.880 align:start position:0% inspired by Bitcoin which is the Bitcoin 00:08:22.880 --> 00:08:26.450 align:start position:0% inspired by Bitcoin which is the Bitcoin JavaScript<00:08:23.880> client<00:08:24.360> and<00:08:24.770> I'd<00:08:25.770> like<00:08:25.979> that<00:08:26.220> it's 00:08:26.450 --> 00:08:26.460 align:start position:0% JavaScript client and I'd like that it's 00:08:26.460 --> 00:08:29.090 align:start position:0% JavaScript client and I'd like that it's it's<00:08:26.700> heavily<00:08:27.150> event<00:08:27.540> written<00:08:27.870> and<00:08:28.229> based<00:08:28.860> on 00:08:29.090 --> 00:08:29.100 align:start position:0% it's heavily event written and based on 00:08:29.100 --> 00:08:30.909 align:start position:0% it's heavily event written and based on a<00:08:29.490> set<00:08:29.790> of<00:08:29.820> loosely<00:08:30.150> coupled<00:08:30.479> components 00:08:30.909 --> 00:08:30.919 align:start position:0% a set of loosely coupled components 00:08:30.919 --> 00:08:33.850 align:start position:0% a set of loosely coupled components which<00:08:31.919> leads<00:08:32.250> to<00:08:32.339> a<00:08:32.430> very<00:08:32.520> extensible<00:08:33.210> design 00:08:33.850 --> 00:08:33.860 align:start position:0% which leads to a very extensible design 00:08:33.860 --> 00:08:38.930 align:start position:0% which leads to a very extensible design for<00:08:34.860> example<00:08:34.950> through<00:08:35.520> plugins<00:08:37.339> and<00:08:38.339> in<00:08:38.789> terms 00:08:38.930 --> 00:08:38.940 align:start position:0% for example through plugins and in terms 00:08:38.940 --> 00:08:41.240 align:start position:0% for example through plugins and in terms of<00:08:39.060> the<00:08:39.120> road<00:08:39.270> map<00:08:39.539> currently<00:08:40.349> we<00:08:40.710> have<00:08:40.890> a 00:08:41.240 --> 00:08:41.250 align:start position:0% of the road map currently we have a 00:08:41.250 --> 00:08:44.380 align:start position:0% of the road map currently we have a proof<00:08:41.490> of<00:08:41.610> concept<00:08:42.120> of<00:08:42.330> a<00:08:42.900> client<00:08:43.680> that<00:08:43.740> could 00:08:44.380 --> 00:08:44.390 align:start position:0% proof of concept of a client that could 00:08:44.390 --> 00:08:47.480 align:start position:0% proof of concept of a client that could sync<00:08:45.390> to<00:08:45.510> me<00:08:45.660> net<00:08:45.900> and<00:08:46.110> other<00:08:46.490> networks 00:08:47.480 --> 00:08:47.490 align:start position:0% sync to me net and other networks 00:08:47.490 --> 00:08:50.079 align:start position:0% sync to me net and other networks through<00:08:47.760> fast<00:08:48.120> and<00:08:48.690> licensing<00:08:49.050> protocols<00:08:49.470> and 00:08:50.079 --> 00:08:50.089 align:start position:0% through fast and licensing protocols and 00:08:50.089 --> 00:08:53.510 align:start position:0% through fast and licensing protocols and also<00:08:51.089> a<00:08:51.120> prototype<00:08:51.750> of<00:08:51.780> Lib<00:08:52.500> p2p 00:08:53.510 --> 00:08:53.520 align:start position:0% also a prototype of Lib p2p 00:08:53.520 --> 00:08:56.000 align:start position:0% also a prototype of Lib p2p obviously<00:08:54.110> that's<00:08:55.110> not<00:08:55.410> used<00:08:55.649> to<00:08:55.740> things<00:08:55.890> to 00:08:56.000 --> 00:08:56.010 align:start position:0% obviously that's not used to things to 00:08:56.010 --> 00:08:57.350 align:start position:0% obviously that's not used to things to other<00:08:56.160> clients<00:08:56.339> because<00:08:56.670> they<00:08:56.910> don't<00:08:57.209> support 00:08:57.350 --> 00:08:57.360 align:start position:0% other clients because they don't support 00:08:57.360 --> 00:09:00.880 align:start position:0% other clients because they don't support it<00:08:57.570> yet<00:08:57.750> but<00:08:58.020> within<00:08:58.680> the<00:08:58.920> theory<00:08:59.130> and<00:08:59.250> jeaious 00:09:00.880 --> 00:09:00.890 align:start position:0% it yet but within the theory and jeaious 00:09:00.890 --> 00:09:04.180 align:start position:0% it yet but within the theory and jeaious environment<00:09:01.890> it<00:09:02.310> does<00:09:02.580> work<00:09:02.730> and<00:09:03.060> also 00:09:04.180 --> 00:09:04.190 align:start position:0% environment it does work and also 00:09:04.190 --> 00:09:07.910 align:start position:0% environment it does work and also browser<00:09:05.190> support<00:09:05.670> and<00:09:06.470> by<00:09:07.470> the<00:09:07.529> end<00:09:07.709> of<00:09:07.800> the 00:09:07.910 --> 00:09:07.920 align:start position:0% browser support and by the end of the 00:09:07.920 --> 00:09:10.360 align:start position:0% browser support and by the end of the year<00:09:08.160> we<00:09:08.670> want<00:09:08.880> to<00:09:08.970> hopefully<00:09:09.630> provide 00:09:10.360 --> 00:09:10.370 align:start position:0% year we want to hopefully provide 00:09:10.370 --> 00:09:15.650 align:start position:0% year we want to hopefully provide reliable<00:09:11.570> mean<00:09:12.570> that<00:09:12.810> change<00:09:13.529> sync<00:09:13.770> and<00:09:14.660> with 00:09:15.650 --> 00:09:15.660 align:start position:0% reliable mean that change sync and with 00:09:15.660 --> 00:09:17.720 align:start position:0% reliable mean that change sync and with this<00:09:15.750> includes<00:09:16.110> block<00:09:16.649> validation<00:09:17.520> in 00:09:17.720 --> 00:09:17.730 align:start position:0% this includes block validation in 00:09:17.730 --> 00:09:20.510 align:start position:0% this includes block validation in transaction<00:09:18.510> execution<00:09:19.080> as<00:09:19.560> well<00:09:19.709> and<00:09:20.010> then 00:09:20.510 --> 00:09:20.520 align:start position:0% transaction execution as well and then 00:09:20.520 --> 00:09:23.079 align:start position:0% transaction execution as well and then integration<00:09:21.060> with<00:09:21.360> a<00:09:21.690> high<00:09:21.959> which<00:09:22.260> is<00:09:22.290> a<00:09:22.410> test 00:09:23.079 --> 00:09:23.089 align:start position:0% integration with a high which is a test 00:09:23.089 --> 00:09:26.470 align:start position:0% integration with a high which is a test setup<00:09:24.089> to<00:09:24.330> test<00:09:24.959> a<00:09:25.200> sync<00:09:25.500> functionality<00:09:26.130> and 00:09:26.470 --> 00:09:26.480 align:start position:0% setup to test a sync functionality and 00:09:26.480 --> 00:09:29.570 align:start position:0% setup to test a sync functionality and the<00:09:27.480> goal<00:09:27.660> about<00:09:27.870> but<00:09:28.110> a<00:09:28.140> mid<00:09:28.589> of<00:09:28.800> next<00:09:29.190> year<00:09:29.339> is 00:09:29.570 --> 00:09:29.580 align:start position:0% the goal about but a mid of next year is 00:09:29.580 --> 00:09:31.820 align:start position:0% the goal about but a mid of next year is to<00:09:29.610> have<00:09:30.089> a<00:09:30.149> proof<00:09:30.480> of<00:09:30.540> concept<00:09:30.720> of<00:09:31.290> a<00:09:31.380> 2.0 00:09:31.820 --> 00:09:31.830 align:start position:0% to have a proof of concept of a 2.0 00:09:31.830 --> 00:09:34.610 align:start position:0% to have a proof of concept of a 2.0 stateless<00:09:32.399> client<00:09:32.760> and<00:09:32.910> an<00:09:33.750> alpha<00:09:33.930> release<00:09:34.080> of 00:09:34.610 --> 00:09:34.620 align:start position:0% stateless client and an alpha release of 00:09:34.620 --> 00:09:38.900 align:start position:0% stateless client and an alpha release of the<00:09:34.800> current<00:09:35.399> client<00:09:36.080> so<00:09:37.080> now<00:09:37.550> there's<00:09:38.550> enough 00:09:38.900 --> 00:09:38.910 align:start position:0% the current client so now there's enough 00:09:38.910 --> 00:09:40.940 align:start position:0% the current client so now there's enough time<00:09:39.149> we're<00:09:39.420> do<00:09:39.510> a<00:09:39.570> quick<00:09:39.810> demo<00:09:40.380> this<00:09:40.709> is<00:09:40.800> a 00:09:40.940 --> 00:09:40.950 align:start position:0% time we're do a quick demo this is a 00:09:40.950 --> 00:09:42.620 align:start position:0% time we're do a quick demo this is a video<00:09:41.190> this<00:09:41.520> is<00:09:41.580> just<00:09:41.730> furniture<00:09:42.209> about<00:09:42.540> the 00:09:42.620 --> 00:09:42.630 align:start position:0% video this is just furniture about the 00:09:42.630 --> 00:09:45.410 align:start position:0% video this is just furniture about the Wi-Fi<00:09:42.779> impairment<00:09:43.620> here<00:09:43.800> so<00:09:44.089> all<00:09:45.089> of<00:09:45.330> this 00:09:45.410 --> 00:09:45.420 align:start position:0% Wi-Fi impairment here so all of this 00:09:45.420 --> 00:09:47.120 align:start position:0% Wi-Fi impairment here so all of this code<00:09:45.660> is<00:09:45.870> downloads<00:09:46.230> is<00:09:46.500> available<00:09:46.920> on<00:09:47.010> github 00:09:47.120 --> 00:09:47.130 align:start position:0% code is downloads is available on github 00:09:47.130 --> 00:09:49.190 align:start position:0% code is downloads is available on github and<00:09:47.550> feel<00:09:48.270> free<00:09:48.420> to<00:09:48.480> run<00:09:48.600> these<00:09:48.750> examples 00:09:49.190 --> 00:09:49.200 align:start position:0% and feel free to run these examples 00:09:49.200 --> 00:09:51.829 align:start position:0% and feel free to run these examples yourself<00:09:49.529> so<00:09:50.399> this<00:09:50.940> is<00:09:51.240> an<00:09:51.360> example<00:09:51.630> of<00:09:51.750> the 00:09:51.829 --> 00:09:51.839 align:start position:0% yourself so this is an example of the 00:09:51.839 --> 00:09:54.050 align:start position:0% yourself so this is an example of the JavaScript<00:09:52.350> client<00:09:52.440> syncing<00:09:53.310> to<00:09:53.339> the<00:09:53.790> rinkeby 00:09:54.050 --> 00:09:54.060 align:start position:0% JavaScript client syncing to the rinkeby 00:09:54.060 --> 00:09:57.199 align:start position:0% JavaScript client syncing to the rinkeby network<00:09:54.450> launching<00:09:55.850> including<00:09:56.850> light<00:09:56.970> serve 00:09:57.199 --> 00:09:57.209 align:start position:0% network launching including light serve 00:09:57.209 --> 00:09:59.150 align:start position:0% network launching including light serve functionality<00:09:57.870> and<00:09:58.050> you<00:09:58.560> can<00:09:58.709> see<00:09:58.860> here<00:09:59.040> it's 00:09:59.150 --> 00:09:59.160 align:start position:0% functionality and you can see here it's 00:09:59.160 --> 00:10:02.930 align:start position:0% functionality and you can see here it's listening<00:09:59.370> on<00:09:59.730> both<00:09:59.910> our<00:10:00.240> LP<00:10:00.600> x<00:10:00.720> and<00:10:01.050> our<00:10:01.820> LP<00:10:02.820> x 00:10:02.930 --> 00:10:02.940 align:start position:0% listening on both our LP x and our LP x 00:10:02.940 --> 00:10:07.010 align:start position:0% listening on both our LP x and our LP x and<00:10:03.270> lib<00:10:04.200> p2p<00:10:04.560> transports<00:10:05.100> and<00:10:05.750> we'll<00:10:06.750> save 00:10:07.010 --> 00:10:07.020 align:start position:0% and lib p2p transports and we'll save 00:10:07.020 --> 00:10:10.220 align:start position:0% and lib p2p transports and we'll save the<00:10:07.290> live<00:10:07.560> PDP<00:10:07.950> URL<00:10:08.339> for<00:10:08.610> the<00:10:08.730> next<00:10:09.050> step<00:10:10.050> in 00:10:10.220 --> 00:10:10.230 align:start position:0% the live PDP URL for the next step in 00:10:10.230 --> 00:10:13.210 align:start position:0% the live PDP URL for the next step in the<00:10:10.290> demo<00:10:11.120> and<00:10:12.120> you<00:10:12.420> can<00:10:12.540> see<00:10:12.720> it's 00:10:13.210 --> 00:10:13.220 align:start position:0% the demo and you can see it's 00:10:13.220 --> 00:10:17.630 align:start position:0% the demo and you can see it's downloading<00:10:14.220> blocks<00:10:15.410> so<00:10:16.410> now<00:10:17.070> we'll<00:10:17.339> move<00:10:17.370> on 00:10:17.630 --> 00:10:17.640 align:start position:0% downloading blocks so now we'll move on 00:10:17.640 --> 00:10:20.360 align:start position:0% downloading blocks so now we'll move on to<00:10:18.000> the<00:10:18.690> more<00:10:18.839> fun<00:10:19.050> stuff<00:10:19.290> which<00:10:19.500> is<00:10:19.529> this<00:10:20.310> is 00:10:20.360 --> 00:10:20.370 align:start position:0% to the more fun stuff which is this is 00:10:20.370 --> 00:10:23.000 align:start position:0% to the more fun stuff which is this is an<00:10:20.490> actual<00:10:20.760> demo<00:10:21.300> of<00:10:21.600> a<00:10:22.020> browser<00:10:22.440> that's 00:10:23.000 --> 00:10:23.010 align:start position:0% an actual demo of a browser that's 00:10:23.010 --> 00:10:24.500 align:start position:0% an actual demo of a browser that's connecting<00:10:23.459> to<00:10:23.579> the<00:10:23.790> client<00:10:24.180> we<00:10:24.270> just 00:10:24.500 --> 00:10:24.510 align:start position:0% connecting to the client we just 00:10:24.510 --> 00:10:27.620 align:start position:0% connecting to the client we just launched<00:10:24.899> over<00:10:25.860> WebSockets<00:10:26.700> which<00:10:27.510> is 00:10:27.620 --> 00:10:27.630 align:start position:0% launched over WebSockets which is 00:10:27.630 --> 00:10:30.740 align:start position:0% launched over WebSockets which is available<00:10:27.810> through<00:10:28.200> the<00:10:28.320> PDP<00:10:28.709> and<00:10:29.510> so<00:10:30.510> we'll 00:10:30.740 --> 00:10:30.750 align:start position:0% available through the PDP and so we'll 00:10:30.750 --> 00:10:32.870 align:start position:0% available through the PDP and so we'll launch<00:10:31.680> the<00:10:31.890> clients<00:10:32.190> in<00:10:32.279> the<00:10:32.339> console<00:10:32.730> we 00:10:32.870 --> 00:10:32.880 align:start position:0% launch the clients in the console we 00:10:32.880 --> 00:10:34.910 align:start position:0% launch the clients in the console we don't<00:10:33.000> have<00:10:33.089> a<00:10:33.120> UI<00:10:33.329> yet<00:10:33.660> but<00:10:34.529> you<00:10:34.649> can<00:10:34.740> them 00:10:34.910 --> 00:10:34.920 align:start position:0% don't have a UI yet but you can them 00:10:34.920 --> 00:10:37.220 align:start position:0% don't have a UI yet but you can them here<00:10:35.459> we're<00:10:35.670> pasting<00:10:36.149> in<00:10:36.240> the<00:10:36.360> URL<00:10:36.750> that<00:10:37.020> we 00:10:37.220 --> 00:10:37.230 align:start position:0% here we're pasting in the URL that we 00:10:37.230 --> 00:10:39.949 align:start position:0% here we're pasting in the URL that we copied<00:10:37.320> in<00:10:37.770> the<00:10:37.800> previous<00:10:37.860> step<00:10:38.250> and<00:10:38.959> so 00:10:39.949 --> 00:10:39.959 align:start position:0% copied in the previous step and so 00:10:39.959 --> 00:10:41.120 align:start position:0% copied in the previous step and so directly<00:10:40.260> from<00:10:40.410> the<00:10:40.529> browser<00:10:40.680> we're<00:10:41.040> gonna 00:10:41.120 --> 00:10:41.130 align:start position:0% directly from the browser we're gonna 00:10:41.130 --> 00:10:43.490 align:start position:0% directly from the browser we're gonna connect<00:10:41.430> it<00:10:41.520> to<00:10:41.579> that<00:10:41.640> client<00:10:41.970> and<00:10:42.500> start 00:10:43.490 --> 00:10:43.500 align:start position:0% connect it to that client and start 00:10:43.500 --> 00:10:47.210 align:start position:0% connect it to that client and start downloading<00:10:44.490> blocks<00:10:44.940> and<00:10:45.270> this<00:10:46.200> this<00:10:46.709> uses 00:10:47.210 --> 00:10:47.220 align:start position:0% downloading blocks and this this uses 00:10:47.220 --> 00:10:50.660 align:start position:0% downloading blocks and this this uses the<00:10:47.570> local<00:10:48.570> storage<00:10:48.839> in<00:10:49.110> the<00:10:49.170> browser<00:10:49.670> via 00:10:50.660 --> 00:10:50.670 align:start position:0% the local storage in the browser via 00:10:50.670 --> 00:10:53.480 align:start position:0% the local storage in the browser via indexeddb<00:10:51.300> and<00:10:51.480> you<00:10:51.570> can<00:10:51.690> see<00:10:51.899> here<00:10:52.370> this<00:10:53.370> is 00:10:53.480 --> 00:10:53.490 align:start position:0% indexeddb and you can see here this is 00:10:53.490 --> 00:10:54.829 align:start position:0% indexeddb and you can see here this is just<00:10:53.730> some<00:10:53.880> of<00:10:53.940> the<00:10:54.029> raw<00:10:54.149> data<00:10:54.540> in<00:10:54.750> the 00:10:54.829 --> 00:10:54.839 align:start position:0% just some of the raw data in the 00:10:54.839 --> 00:11:01.790 align:start position:0% just some of the raw data in the database<00:10:55.640> so<00:10:56.930> yeah<00:10:57.930> so<00:10:58.320> that's<00:10:58.440> it 00:11:01.790 --> 00:11:01.800 align:start position:0% 00:11:01.800 --> 00:11:05.970 align:start position:0% so<00:11:03.300> yeah<00:11:04.300> it's<00:11:04.540> great<00:11:04.630> I<00:11:04.870> know<00:11:05.080> I'm<00:11:05.230> again<00:11:05.860> on 00:11:05.970 --> 00:11:05.980 align:start position:0% so yeah it's great I know I'm again on 00:11:05.980 --> 00:11:08.340 align:start position:0% so yeah it's great I know I'm again on the<00:11:06.070> team<00:11:06.250> of<00:11:06.370> contributions<00:11:07.110> there's<00:11:08.110> ton<00:11:08.320> of 00:11:08.340 --> 00:11:08.350 align:start position:0% the team of contributions there's ton of 00:11:08.350 --> 00:11:11.280 align:start position:0% the team of contributions there's ton of work<00:11:08.590> left<00:11:09.040> to<00:11:09.160> do<00:11:09.280> so<00:11:09.400> we're<00:11:09.850> hoping<00:11:10.210> to<00:11:10.540> get 00:11:11.280 --> 00:11:11.290 align:start position:0% work left to do so we're hoping to get 00:11:11.290 --> 00:11:12.960 align:start position:0% work left to do so we're hoping to get the<00:11:11.350> community<00:11:11.740> to<00:11:11.980> help<00:11:12.100> contribute<00:11:12.850> them 00:11:12.960 --> 00:11:12.970 align:start position:0% the community to help contribute them 00:11:12.970 --> 00:11:15.540 align:start position:0% the community to help contribute them with<00:11:13.120> it<00:11:13.270> move<00:11:13.450> things<00:11:13.720> quickly<00:11:14.370> so<00:11:15.370> I'm<00:11:15.430> going 00:11:15.540 --> 00:11:15.550 align:start position:0% with it move things quickly so I'm going 00:11:15.550 --> 00:11:27.990 align:start position:0% with it move things quickly so I'm going to<00:11:15.610> hand<00:11:16.030> this<00:11:16.240> off<00:11:16.570> now<00:11:16.870> -<00:11:16.930> Casey<00:11:26.400> I'm<00:11:27.400> Casey<00:11:27.430> I 00:11:27.990 --> 00:11:28.000 align:start position:0% to hand this off now - Casey I'm Casey I 00:11:28.000 --> 00:11:30.870 align:start position:0% to hand this off now - Casey I'm Casey I started<00:11:28.720> contributing<00:11:29.680> to<00:11:29.950> a<00:11:30.400> theorem<00:11:30.850> just 00:11:30.870 --> 00:11:30.880 align:start position:0% started contributing to a theorem just 00:11:30.880 --> 00:11:34.110 align:start position:0% started contributing to a theorem just last<00:11:31.450> year<00:11:31.750> for<00:11:32.650> Byzantium<00:11:33.490> so<00:11:33.700> implementing 00:11:34.110 --> 00:11:34.120 align:start position:0% last year for Byzantium so implementing 00:11:34.120 --> 00:11:39.450 align:start position:0% last year for Byzantium so implementing Byzantium<00:11:34.870> features<00:11:35.790> in<00:11:36.790> 2017<00:11:37.450> and<00:11:38.040> I<00:11:39.040> wanted 00:11:39.450 --> 00:11:39.460 align:start position:0% Byzantium features in 2017 and I wanted 00:11:39.460 --> 00:11:44.190 align:start position:0% Byzantium features in 2017 and I wanted to<00:11:40.530> just<00:11:41.530> highlight<00:11:41.740> one<00:11:42.520> of<00:11:42.550> our<00:11:43.200> research 00:11:44.190 --> 00:11:44.200 align:start position:0% to just highlight one of our research 00:11:44.200 --> 00:11:48.170 align:start position:0% to just highlight one of our research project<00:11:45.190> -<00:11:45.610> duze<00:11:45.810> on<00:11:46.810> the<00:11:47.020> theory<00:11:47.230> MJS<00:11:47.500> team 00:11:48.170 --> 00:11:48.180 align:start position:0% project - duze on the theory MJS team 00:11:48.180 --> 00:11:51.900 align:start position:0% project - duze on the theory MJS team i'm<00:11:49.180> also<00:11:49.470> now<00:11:50.470> working<00:11:51.040> with<00:11:51.220> the<00:11:51.340> EU<00:11:51.580> azam 00:11:51.900 --> 00:11:51.910 align:start position:0% i'm also now working with the EU azam 00:11:51.910 --> 00:11:56.460 align:start position:0% i'm also now working with the EU azam team<00:11:52.860> so<00:11:53.910> that's<00:11:54.910> why<00:11:55.060> we're<00:11:55.240> get<00:11:56.080> into<00:11:56.320> this 00:11:56.460 --> 00:11:56.470 align:start position:0% team so that's why we're get into this 00:11:56.470 --> 00:12:03.210 align:start position:0% team so that's why we're get into this phase<00:11:57.040> -<00:11:57.370> because<00:11:59.340> most<00:12:00.340> etherium<00:12:01.230> 2.0<00:12:02.230> R&D 00:12:03.210 --> 00:12:03.220 align:start position:0% phase - because most etherium 2.0 R&D 00:12:03.220 --> 00:12:05.550 align:start position:0% phase - because most etherium 2.0 R&D efforts<00:12:03.640> right<00:12:03.820> now<00:12:03.880> are<00:12:04.120> focused<00:12:04.480> on<00:12:04.600> phase<00:12:05.290> 1 00:12:05.550 --> 00:12:05.560 align:start position:0% efforts right now are focused on phase 1 00:12:05.560 --> 00:12:08.360 align:start position:0% efforts right now are focused on phase 1 which<00:12:05.800> is<00:12:05.980> implementing<00:12:06.700> the<00:12:06.910> beacon<00:12:07.660> chain 00:12:08.360 --> 00:12:08.370 align:start position:0% which is implementing the beacon chain 00:12:08.370 --> 00:12:11.520 align:start position:0% which is implementing the beacon chain there's<00:12:09.370> another<00:12:09.580> team<00:12:10.080> chain<00:12:11.080> safe<00:12:11.320> who's 00:12:11.520 --> 00:12:11.530 align:start position:0% there's another team chain safe who's 00:12:11.530 --> 00:12:13.140 align:start position:0% there's another team chain safe who's working<00:12:11.800> on<00:12:11.890> a<00:12:12.030> JavaScript<00:12:13.030> implementation 00:12:13.140 --> 00:12:13.150 align:start position:0% working on a JavaScript implementation 00:12:13.150 --> 00:12:18.540 align:start position:0% working on a JavaScript implementation of<00:12:13.720> the<00:12:13.930> beacon<00:12:14.410> chain<00:12:14.590> called<00:12:14.830> lodestar<00:12:17.550> but 00:12:18.540 --> 00:12:18.550 align:start position:0% of the beacon chain called lodestar but 00:12:18.550 --> 00:12:21.090 align:start position:0% of the beacon chain called lodestar but as<00:12:18.820> a<00:12:18.850> member<00:12:19.210> of<00:12:19.450> the<00:12:19.690> II<00:12:19.990> wasn't<00:12:20.590> team<00:12:20.890> we're 00:12:21.090 --> 00:12:21.100 align:start position:0% as a member of the II wasn't team we're 00:12:21.100 --> 00:12:23.400 align:start position:0% as a member of the II wasn't team we're not<00:12:21.220> so<00:12:21.430> concerned<00:12:21.460> with<00:12:22.150> phase<00:12:22.840> 1<00:12:23.110> we're 00:12:23.400 --> 00:12:23.410 align:start position:0% not so concerned with phase 1 we're 00:12:23.410 --> 00:12:25.920 align:start position:0% not so concerned with phase 1 we're focused<00:12:23.800> on<00:12:23.920> Phase<00:12:24.310> two<00:12:24.340> which<00:12:24.820> is<00:12:25.000> the<00:12:25.210> going 00:12:25.920 --> 00:12:25.930 align:start position:0% focused on Phase two which is the going 00:12:25.930 --> 00:12:30.500 align:start position:0% focused on Phase two which is the going to<00:12:26.020> be<00:12:26.110> the<00:12:26.290> execution<00:12:27.040> engine<00:12:27.310> of<00:12:27.490> Jasper<00:12:29.490> so 00:12:30.500 --> 00:12:30.510 align:start position:0% to be the execution engine of Jasper so 00:12:30.510 --> 00:12:34.920 align:start position:0% to be the execution engine of Jasper so one<00:12:31.510> of<00:12:31.540> our<00:12:31.720> two<00:12:32.140> days<00:12:32.320> is<00:12:32.590> prototype<00:12:33.630> phase<00:12:34.630> 2 00:12:34.920 --> 00:12:34.930 align:start position:0% one of our two days is prototype phase 2 00:12:34.930 --> 00:12:38.700 align:start position:0% one of our two days is prototype phase 2 right<00:12:35.680> now<00:12:35.800> there's<00:12:36.480> a<00:12:37.480> lot<00:12:38.200> of<00:12:38.320> ideas 00:12:38.700 --> 00:12:38.710 align:start position:0% right now there's a lot of ideas 00:12:38.710 --> 00:12:43.800 align:start position:0% right now there's a lot of ideas bouncing<00:12:39.190> around<00:12:39.280> for<00:12:39.730> how<00:12:40.210> -<00:12:42.360> what<00:12:43.360> the<00:12:43.540> specs 00:12:43.800 --> 00:12:43.810 align:start position:0% bouncing around for how - what the specs 00:12:43.810 --> 00:12:46.140 align:start position:0% bouncing around for how - what the specs should<00:12:43.960> be<00:12:44.080> for<00:12:44.350> the<00:12:44.500> phase<00:12:45.310> 2<00:12:45.550> execution 00:12:46.140 --> 00:12:46.150 align:start position:0% should be for the phase 2 execution 00:12:46.150 --> 00:12:50.250 align:start position:0% should be for the phase 2 execution engine<00:12:46.920> all<00:12:47.920> phase<00:12:48.340> one<00:12:48.640> does<00:12:48.880> is<00:12:49.230> orders<00:12:50.230> a 00:12:50.250 --> 00:12:50.260 align:start position:0% engine all phase one does is orders a 00:12:50.260 --> 00:12:53.880 align:start position:0% engine all phase one does is orders a set<00:12:50.620> of<00:12:50.800> data<00:12:51.700> blobs<00:12:52.000> and<00:12:52.740> that's<00:12:53.740> actually 00:12:53.880 --> 00:12:53.890 align:start position:0% set of data blobs and that's actually 00:12:53.890 --> 00:12:58.110 align:start position:0% set of data blobs and that's actually the<00:12:54.040> hard<00:12:54.250> part<00:12:54.490> so<00:12:55.090> it's<00:12:56.370> actually<00:12:57.370> easier<00:12:57.550> - 00:12:58.110 --> 00:12:58.120 align:start position:0% the hard part so it's actually easier - 00:12:58.120 --> 00:13:00.270 align:start position:0% the hard part so it's actually easier - if<00:12:58.510> you<00:12:58.930> have<00:12:59.140> an<00:12:59.290> order<00:12:59.530> set<00:12:59.680> of<00:12:59.800> data<00:13:00.010> blobs 00:13:00.270 --> 00:13:00.280 align:start position:0% if you have an order set of data blobs 00:13:00.280 --> 00:13:02.090 align:start position:0% if you have an order set of data blobs then<00:13:00.580> should<00:13:00.700> just<00:13:00.880> process<00:13:01.360> them<00:13:01.540> as 00:13:02.090 --> 00:13:02.100 align:start position:0% then should just process them as 00:13:02.100 --> 00:13:05.310 align:start position:0% then should just process them as transactions<00:13:03.100> and<00:13:03.600> that's<00:13:04.600> what<00:13:04.870> the<00:13:04.990> goal<00:13:05.140> is 00:13:05.310 --> 00:13:05.320 align:start position:0% transactions and that's what the goal is 00:13:05.320 --> 00:13:09.870 align:start position:0% transactions and that's what the goal is for<00:13:05.350> prototyping<00:13:06.190> phase<00:13:06.610> 2<00:13:08.370> one<00:13:09.370> of<00:13:09.400> the<00:13:09.490> ideas 00:13:09.870 --> 00:13:09.880 align:start position:0% for prototyping phase 2 one of the ideas 00:13:09.880 --> 00:13:13.170 align:start position:0% for prototyping phase 2 one of the ideas being<00:13:10.450> bounced<00:13:10.750> around<00:13:10.840> for<00:13:11.710> phase<00:13:12.100> 2<00:13:12.370> is 00:13:13.170 --> 00:13:13.180 align:start position:0% being bounced around for phase 2 is 00:13:13.180 --> 00:13:17.640 align:start position:0% being bounced around for phase 2 is stateless<00:13:13.660> clients<00:13:14.190> and<00:13:15.690> it's<00:13:16.690> actually 00:13:17.640 --> 00:13:17.650 align:start position:0% stateless clients and it's actually 00:13:17.650 --> 00:13:20.130 align:start position:0% stateless clients and it's actually probably<00:13:17.920> the<00:13:18.190> most<00:13:18.490> this<00:13:19.390> simplest<00:13:19.870> you<00:13:19.990> can 00:13:20.130 --> 00:13:20.140 align:start position:0% probably the most this simplest you can 00:13:20.140 --> 00:13:23.880 align:start position:0% probably the most this simplest you can do<00:13:20.260> clients<00:13:20.830> just<00:13:21.430> has<00:13:22.170> 32<00:13:23.170> bytes<00:13:23.380> state<00:13:23.680> route 00:13:23.880 --> 00:13:23.890 align:start position:0% do clients just has 32 bytes state route 00:13:23.890 --> 00:13:27.980 align:start position:0% do clients just has 32 bytes state route and<00:13:25.290> I<00:13:26.290> mean<00:13:26.800> the<00:13:26.890> trade-off<00:13:27.250> is<00:13:27.400> that<00:13:27.430> then 00:13:27.980 --> 00:13:27.990 align:start position:0% and I mean the trade-off is that then 00:13:27.990 --> 00:13:29.880 align:start position:0% and I mean the trade-off is that then transactions<00:13:28.990> become<00:13:29.230> much<00:13:29.410> larger<00:13:29.800> because 00:13:29.880 --> 00:13:29.890 align:start position:0% transactions become much larger because 00:13:29.890 --> 00:13:32.130 align:start position:0% transactions become much larger because they<00:13:30.160> have<00:13:30.310> to<00:13:30.490> include<00:13:30.700> the<00:13:31.000> merkel<00:13:31.720> proof<00:13:31.930> of 00:13:32.130 --> 00:13:32.140 align:start position:0% they have to include the merkel proof of 00:13:32.140 --> 00:13:35.160 align:start position:0% they have to include the merkel proof of all<00:13:32.380> the<00:13:32.680> touched<00:13:33.100> accounts<00:13:34.050> hopefully<00:13:35.050> you 00:13:35.160 --> 00:13:35.170 align:start position:0% all the touched accounts hopefully you 00:13:35.170 --> 00:13:39.300 align:start position:0% all the touched accounts hopefully you can<00:13:35.320> see<00:13:35.560> this<00:13:35.740> this<00:13:36.640> is<00:13:36.790> a<00:13:37.710> visualization<00:13:38.710> of 00:13:39.300 --> 00:13:39.310 align:start position:0% can see this this is a visualization of 00:13:39.310 --> 00:13:43.460 align:start position:0% can see this this is a visualization of the<00:13:41.130> merkel<00:13:42.130> patricia<00:13:42.520> tree<00:13:42.760> which<00:13:43.000> is<00:13:43.029> the 00:13:43.460 --> 00:13:43.470 align:start position:0% the merkel patricia tree which is the 00:13:43.470 --> 00:13:46.890 align:start position:0% the merkel patricia tree which is the tree<00:13:44.470> that's<00:13:44.710> used<00:13:44.980> in<00:13:45.220> aetherium<00:13:45.900> current 00:13:46.890 --> 00:13:46.900 align:start position:0% tree that's used in aetherium current 00:13:46.900 --> 00:13:51.269 align:start position:0% tree that's used in aetherium current aetherium<00:13:47.200> 1.0<00:13:48.839> so<00:13:49.839> this<00:13:50.020> is<00:13:50.080> an<00:13:50.140> example<00:13:50.950> of 00:13:51.269 --> 00:13:51.279 align:start position:0% aetherium 1.0 so this is an example of 00:13:51.279 --> 00:13:53.670 align:start position:0% aetherium 1.0 so this is an example of an<00:13:51.490> advantage<00:13:51.760> of<00:13:52.089> when<00:13:52.660> you<00:13:52.810> have<00:13:53.050> lots<00:13:53.529> of 00:13:53.670 --> 00:13:53.680 align:start position:0% an advantage of when you have lots of 00:13:53.680 --> 00:13:56.310 align:start position:0% an advantage of when you have lots of libraries<00:13:54.400> and<00:13:54.580> tooling<00:13:54.910> and<00:13:55.060> javascript<00:13:55.690> you 00:13:56.310 --> 00:13:56.320 align:start position:0% libraries and tooling and javascript you 00:13:56.320 --> 00:13:58.760 align:start position:0% libraries and tooling and javascript you can<00:13:56.350> do<00:13:56.589> neat<00:13:56.770> things<00:13:57.010> like<00:13:57.220> visualize<00:13:58.089> them 00:13:58.760 --> 00:13:58.770 align:start position:0% can do neat things like visualize them 00:13:58.770 --> 00:14:02.100 align:start position:0% can do neat things like visualize them fairly<00:13:59.770> easily<00:13:59.920> and<00:14:00.250> in<00:14:00.880> the<00:14:01.029> browser<00:14:01.150> which 00:14:02.100 --> 00:14:02.110 align:start position:0% fairly easily and in the browser which 00:14:02.110 --> 00:14:06.079 align:start position:0% fairly easily and in the browser which really<00:14:02.320> helps<00:14:02.560> with<00:14:02.650> debugging<00:14:02.980> and<00:14:04.410> and 00:14:06.079 --> 00:14:06.089 align:start position:0% really helps with debugging and and 00:14:06.089 --> 00:14:09.690 align:start position:0% really helps with debugging and and explaining<00:14:07.089> how<00:14:07.210> things<00:14:07.690> work<00:14:07.900> so<00:14:08.700> to 00:14:09.690 --> 00:14:09.700 align:start position:0% explaining how things work so to 00:14:09.700 --> 00:14:11.640 align:start position:0% explaining how things work so to conclude<00:14:09.880> why<00:14:10.360> do<00:14:10.420> we<00:14:10.660> want<00:14:10.839> to<00:14:10.960> prototype 00:14:11.640 --> 00:14:11.650 align:start position:0% conclude why do we want to prototype 00:14:11.650 --> 00:14:15.840 align:start position:0% conclude why do we want to prototype Shaftesbury<00:14:12.190> jeaious<00:14:13.680> because<00:14:14.850> there's 00:14:15.840 --> 00:14:15.850 align:start position:0% Shaftesbury jeaious because there's 00:14:15.850 --> 00:14:17.910 align:start position:0% Shaftesbury jeaious because there's already<00:14:16.029> a<00:14:16.150> lot<00:14:16.300> of<00:14:16.330> base<00:14:17.260> libraries<00:14:17.770> in 00:14:17.910 --> 00:14:17.920 align:start position:0% already a lot of base libraries in 00:14:17.920 --> 00:14:20.670 align:start position:0% already a lot of base libraries in jeaious<00:14:18.250> and<00:14:18.490> also<00:14:18.820> you<00:14:19.480> know<00:14:19.570> user<00:14:20.200> interface 00:14:20.670 --> 00:14:20.680 align:start position:0% jeaious and also you know user interface 00:14:20.680 --> 00:14:23.040 align:start position:0% jeaious and also you know user interface tools<00:14:21.010> for<00:14:21.880> example<00:14:22.240> if<00:14:22.420> we<00:14:22.660> have<00:14:22.779> to<00:14:22.839> change 00:14:23.040 --> 00:14:23.050 align:start position:0% tools for example if we have to change 00:14:23.050 --> 00:14:24.750 align:start position:0% tools for example if we have to change the<00:14:23.230> transaction<00:14:23.890> format<00:14:24.250> for<00:14:24.459> a<00:14:24.490> three-room 00:14:24.750 --> 00:14:24.760 align:start position:0% the transaction format for a three-room 00:14:24.760 --> 00:14:28.110 align:start position:0% the transaction format for a three-room 2.0<00:14:25.270> then<00:14:26.279> getting<00:14:27.279> those<00:14:27.430> working<00:14:27.700> in 00:14:28.110 --> 00:14:28.120 align:start position:0% 2.0 then getting those working in 00:14:28.120 --> 00:14:31.410 align:start position:0% 2.0 then getting those working in javascript<00:14:29.110> libraries<00:14:29.620> let's<00:14:30.420> other 00:14:31.410 --> 00:14:31.420 align:start position:0% javascript libraries let's other 00:14:31.420 --> 00:14:34.769 align:start position:0% javascript libraries let's other projects<00:14:31.959> like<00:14:31.990> my<00:14:32.890> crypto<00:14:33.310> and<00:14:33.580> made<00:14:34.510> a<00:14:34.540> mask 00:14:34.769 --> 00:14:34.779 align:start position:0% projects like my crypto and made a mask 00:14:34.779 --> 00:14:38.100 align:start position:0% projects like my crypto and made a mask in<00:14:34.930> different<00:14:35.170> wallets<00:14:35.529> more<00:14:36.490> easily<00:14:37.110> test 00:14:38.100 --> 00:14:38.110 align:start position:0% in different wallets more easily test 00:14:38.110 --> 00:14:40.410 align:start position:0% in different wallets more easily test out<00:14:38.290> these<00:14:38.470> UI<00:14:38.740> changes<00:14:39.250> also<00:14:40.089> there<00:14:40.360> are 00:14:40.410 --> 00:14:40.420 align:start position:0% out these UI changes also there are 00:14:40.420 --> 00:14:42.269 align:start position:0% out these UI changes also there are mature<00:14:40.690> networking<00:14:41.140> libraries<00:14:41.529> for<00:14:42.220> example 00:14:42.269 --> 00:14:42.279 align:start position:0% mature networking libraries for example 00:14:42.279 --> 00:14:46.130 align:start position:0% mature networking libraries for example the<00:14:42.760> p2p<00:14:43.060> lib<00:14:43.420> p2p<00:14:43.810> is<00:14:43.870> being<00:14:44.700> adopted 00:14:46.130 --> 00:14:46.140 align:start position:0% the p2p lib p2p is being adopted 00:14:46.140 --> 00:14:49.680 align:start position:0% the p2p lib p2p is being adopted probably<00:14:47.140> as<00:14:47.350> the<00:14:47.970> networking<00:14:48.970> library<00:14:49.450> for 00:14:49.680 --> 00:14:49.690 align:start position:0% probably as the networking library for 00:14:49.690 --> 00:14:54.269 align:start position:0% probably as the networking library for its<00:14:49.810> theorem<00:14:50.020> 2.0<00:14:50.470> and<00:14:51.360> it's<00:14:52.680> not<00:14:53.680> doesn't 00:14:54.269 --> 00:14:54.279 align:start position:0% its theorem 2.0 and it's not doesn't 00:14:54.279 --> 00:14:55.470 align:start position:0% its theorem 2.0 and it's not doesn't have<00:14:54.370> a<00:14:54.400> mature<00:14:54.610> implementation<00:14:55.270> in<00:14:55.330> every 00:14:55.470 --> 00:14:55.480 align:start position:0% have a mature implementation in every 00:14:55.480 --> 00:14:57.750 align:start position:0% have a mature implementation in every language<00:14:55.630> but<00:14:56.050> it<00:14:56.589> does<00:14:56.740> have<00:14:56.920> pretty<00:14:57.640> decent 00:14:57.750 --> 00:14:57.760 align:start position:0% language but it does have pretty decent 00:14:57.760 --> 00:15:01.380 align:start position:0% language but it does have pretty decent one<00:14:58.060> in<00:14:58.209> JavaScript<00:14:58.779> also<00:14:59.320> if<00:15:00.190> the<00:15:01.000> phase<00:15:01.180> 2 00:15:01.380 --> 00:15:01.390 align:start position:0% one in JavaScript also if the phase 2 00:15:01.390 --> 00:15:03.900 align:start position:0% one in JavaScript also if the phase 2 execution<00:15:01.900> engine<00:15:02.200> is<00:15:02.350> awasum<00:15:02.950> then<00:15:03.610> it's 00:15:03.900 --> 00:15:03.910 align:start position:0% execution engine is awasum then it's 00:15:03.910 --> 00:15:07.350 align:start position:0% execution engine is awasum then it's very<00:15:04.180> convenient<00:15:04.600> to<00:15:04.870> have<00:15:04.900> a<00:15:05.380> native<00:15:06.360> JIT 00:15:07.350 --> 00:15:07.360 align:start position:0% very convenient to have a native JIT 00:15:07.360 --> 00:15:09.590 align:start position:0% very convenient to have a native JIT powerful<00:15:07.870> you<00:15:08.200> know<00:15:08.290> webassembly<00:15:08.709> JIT<00:15:09.040> engine 00:15:09.590 --> 00:15:09.600 align:start position:0% powerful you know webassembly JIT engine 00:15:09.600 --> 00:15:11.940 align:start position:0% powerful you know webassembly JIT engine from<00:15:10.600> the<00:15:10.690> browser<00:15:10.870> so<00:15:11.260> we<00:15:11.290> get<00:15:11.529> that<00:15:11.680> for<00:15:11.860> free 00:15:11.940 --> 00:15:11.950 align:start position:0% from the browser so we get that for free 00:15:11.950 --> 00:15:14.820 align:start position:0% from the browser so we get that for free implementing<00:15:12.940> in<00:15:13.000> JavaScript<00:15:13.510> and<00:15:13.660> of<00:15:14.589> course 00:15:14.820 --> 00:15:14.830 align:start position:0% implementing in JavaScript and of course 00:15:14.830 --> 00:15:16.440 align:start position:0% implementing in JavaScript and of course I<00:15:14.980> mean<00:15:15.130> Java<00:15:15.430> scripts<00:15:15.730> everybody's<00:15:16.089> favorite 00:15:16.440 --> 00:15:16.450 align:start position:0% I mean Java scripts everybody's favorite 00:15:16.450 --> 00:15:18.540 align:start position:0% I mean Java scripts everybody's favorite language<00:15:16.750> so<00:15:16.990> obviously<00:15:17.860> should<00:15:18.250> implement 00:15:18.540 --> 00:15:18.550 align:start position:0% language so obviously should implement 00:15:18.550 --> 00:15:22.890 align:start position:0% language so obviously should implement it<00:15:19.140> in<00:15:20.140> JavaScript<00:15:20.650> and<00:15:21.690> that's<00:15:22.690> what<00:15:22.810> I'm 00:15:22.890 --> 00:15:22.900 align:start position:0% it in JavaScript and that's what I'm 00:15:22.900 --> 00:15:25.740 align:start position:0% it in JavaScript and that's what I'm gonna<00:15:22.990> pass<00:15:23.200> off<00:15:23.380> to<00:15:23.410> Alex<00:15:24.040> now 00:15:25.740 --> 00:15:25.750 align:start position:0% gonna pass off to Alex now 00:15:25.750 --> 00:15:30.919 align:start position:0% gonna pass off to Alex now [Applause] 00:15:30.919 --> 00:15:30.929 align:start position:0% [Applause] 00:15:30.929 --> 00:15:32.609 align:start position:0% [Applause] Thank<00:15:31.929> You<00:15:31.990> Casey 00:15:32.609 --> 00:15:32.619 align:start position:0% Thank You Casey 00:15:32.619 --> 00:15:34.619 align:start position:0% Thank You Casey so<00:15:33.189> my<00:15:33.279> name<00:15:33.399> is<00:15:33.490> Alex<00:15:33.639> I've<00:15:34.089> worked<00:15:34.420> in<00:15:34.569> the 00:15:34.619 --> 00:15:34.629 align:start position:0% so my name is Alex I've worked in the 00:15:34.629 --> 00:15:36.710 align:start position:0% so my name is Alex I've worked in the theorem<00:15:34.869> GS<00:15:35.139> for<00:15:35.410> a<00:15:35.439> long<00:15:35.589> while<00:15:35.800> but<00:15:36.189> today 00:15:36.710 --> 00:15:36.720 align:start position:0% theorem GS for a long while but today 00:15:36.720 --> 00:15:39.119 align:start position:0% theorem GS for a long while but today mostly<00:15:37.720> I'm<00:15:37.809> focus<00:15:38.079> on<00:15:38.170> e<00:15:38.199> massaman<00:15:38.709> and<00:15:38.949> this 00:15:39.119 --> 00:15:39.129 align:start position:0% mostly I'm focus on e massaman and this 00:15:39.129 --> 00:15:41.999 align:start position:0% mostly I'm focus on e massaman and this already<00:15:39.279> compiler<00:15:39.790> and<00:15:40.559> anyhow<00:15:41.559> I<00:15:41.589> do<00:15:41.769> have<00:15:41.980> a 00:15:41.999 --> 00:15:42.009 align:start position:0% already compiler and anyhow I do have a 00:15:42.009 --> 00:15:44.189 align:start position:0% already compiler and anyhow I do have a couple<00:15:42.189> of<00:15:42.339> things<00:15:42.490> to<00:15:42.670> say<00:15:42.699> here<00:15:42.850> so<00:15:43.689> there 00:15:44.189 --> 00:15:44.199 align:start position:0% couple of things to say here so there 00:15:44.199 --> 00:15:46.109 align:start position:0% couple of things to say here so there are<00:15:44.259> a<00:15:44.290> lot<00:15:44.319> of<00:15:44.439> 2.0<00:15:44.980> things<00:15:45.279> flying<00:15:45.850> around 00:15:46.109 --> 00:15:46.119 align:start position:0% are a lot of 2.0 things flying around 00:15:46.119 --> 00:15:48.389 align:start position:0% are a lot of 2.0 things flying around nowadays<00:15:46.749> so<00:15:47.649> just<00:15:47.860> gonna<00:15:48.009> talk<00:15:48.189> a<00:15:48.220> bit<00:15:48.369> about 00:15:48.389 --> 00:15:48.399 align:start position:0% nowadays so just gonna talk a bit about 00:15:48.399 --> 00:15:50.460 align:start position:0% nowadays so just gonna talk a bit about the<00:15:48.610> term<00:15:48.759> GS<00:15:49.029> 2.0<00:15:49.420> and<00:15:49.569> what<00:15:49.749> death<00:15:49.990> may<00:15:50.259> look 00:15:50.460 --> 00:15:50.470 align:start position:0% the term GS 2.0 and what death may look 00:15:50.470 --> 00:15:53.189 align:start position:0% the term GS 2.0 and what death may look like<00:15:50.649> but<00:15:51.579> first<00:15:51.790> just<00:15:51.970> take<00:15:52.149> a<00:15:52.209> step<00:15:52.509> back<00:15:52.839> and 00:15:53.189 --> 00:15:53.199 align:start position:0% like but first just take a step back and 00:15:53.199 --> 00:15:56.069 align:start position:0% like but first just take a step back and you<00:15:53.949> know<00:15:54.160> what<00:15:54.670> is<00:15:54.759> it<00:15:54.879> Tim<00:15:54.970> GS<00:15:55.300> currently<00:15:55.899> a 00:15:56.069 --> 00:15:56.079 align:start position:0% you know what is it Tim GS currently a 00:15:56.079 --> 00:15:59.489 align:start position:0% you know what is it Tim GS currently a lot<00:15:56.800> of<00:15:56.920> the<00:15:57.040> API<00:15:57.309> is<00:15:57.429> in<00:15:57.550> idioms<00:15:57.970> es<00:15:58.240> are<00:15:58.869> fully 00:15:59.489 --> 00:15:59.499 align:start position:0% lot of the API is in idioms es are fully 00:15:59.499 --> 00:16:01.109 align:start position:0% lot of the API is in idioms es are fully synchronous<00:16:00.040> a<00:16:00.279> good<00:16:00.459> example<00:16:00.730> for<00:16:00.850> that<00:16:00.999> is 00:16:01.109 --> 00:16:01.119 align:start position:0% synchronous a good example for that is 00:16:01.119 --> 00:16:03.749 align:start position:0% synchronous a good example for that is the<00:16:01.389> wallet<00:16:01.679> and<00:16:02.679> one<00:16:03.069> particularly<00:16:03.519> except 00:16:03.749 --> 00:16:03.759 align:start position:0% the wallet and one particularly except 00:16:03.759 --> 00:16:05.730 align:start position:0% the wallet and one particularly except from<00:16:03.850> the<00:16:03.970> wallet<00:16:04.119> itself<00:16:04.540> is<00:16:04.869> random<00:16:05.529> number 00:16:05.730 --> 00:16:05.740 align:start position:0% from the wallet itself is random number 00:16:05.740 --> 00:16:07.379 align:start position:0% from the wallet itself is random number generation<00:16:06.100> that<00:16:06.399> is<00:16:06.459> expected<00:16:07.029> to<00:16:07.119> be<00:16:07.209> fully 00:16:07.379 --> 00:16:07.389 align:start position:0% generation that is expected to be fully 00:16:07.389 --> 00:16:09.389 align:start position:0% generation that is expected to be fully synchronous<00:16:07.869> today<00:16:08.139> a<00:16:08.350> lot<00:16:08.829> of<00:16:08.920> people<00:16:09.160> run 00:16:09.389 --> 00:16:09.399 align:start position:0% synchronous today a lot of people run 00:16:09.399 --> 00:16:10.980 align:start position:0% synchronous today a lot of people run into<00:16:09.519> issues<00:16:09.759> trying<00:16:10.329> to<00:16:10.389> integrate<00:16:10.779> it<00:16:10.929> into 00:16:10.980 --> 00:16:10.990 align:start position:0% into issues trying to integrate it into 00:16:10.990 --> 00:16:12.840 align:start position:0% into issues trying to integrate it into mobile<00:16:11.319> devices<00:16:12.009> for<00:16:12.309> a<00:16:12.339> random<00:16:12.639> number 00:16:12.840 --> 00:16:12.850 align:start position:0% mobile devices for a random number 00:16:12.850 --> 00:16:15.239 align:start position:0% mobile devices for a random number generation<00:16:13.119> would<00:16:13.389> be<00:16:13.449> asynchronous<00:16:14.249> but 00:16:15.239 --> 00:16:15.249 align:start position:0% generation would be asynchronous but 00:16:15.249 --> 00:16:17.460 align:start position:0% generation would be asynchronous but compared<00:16:15.610> to<00:16:15.670> that<00:16:15.759> a<00:16:16.240> lot<00:16:16.869> of<00:16:16.990> the<00:16:17.110> code<00:16:17.290> in 00:16:17.460 --> 00:16:17.470 align:start position:0% compared to that a lot of the code in 00:16:17.470 --> 00:16:20.160 align:start position:0% compared to that a lot of the code in atrium<00:16:17.769> J's<00:16:17.980> is<00:16:18.309> fully<00:16:18.639> asynchronous<00:16:19.389> as<00:16:19.959> it 00:16:20.160 --> 00:16:20.170 align:start position:0% atrium J's is fully asynchronous as it 00:16:20.170 --> 00:16:22.799 align:start position:0% atrium J's is fully asynchronous as it was<00:16:20.319> mentioned<00:16:20.499> before<00:16:21.029> so<00:16:22.029> one<00:16:22.360> example<00:16:22.480> for 00:16:22.799 --> 00:16:22.809 align:start position:0% was mentioned before so one example for 00:16:22.809 --> 00:16:24.480 align:start position:0% was mentioned before so one example for that<00:16:22.869> is<00:16:22.929> the<00:16:23.079> VM<00:16:23.379> that's<00:16:23.679> fully<00:16:23.980> synchronous 00:16:24.480 --> 00:16:24.490 align:start position:0% that is the VM that's fully synchronous 00:16:24.490 --> 00:16:27.359 align:start position:0% that is the VM that's fully synchronous um<00:16:25.470> maybe<00:16:26.470> we<00:16:26.740> should<00:16:26.920> have<00:16:27.040> a<00:16:27.069> bit<00:16:27.220> more 00:16:27.359 --> 00:16:27.369 align:start position:0% um maybe we should have a bit more 00:16:27.369 --> 00:16:28.949 align:start position:0% um maybe we should have a bit more consistency<00:16:27.879> between<00:16:28.119> the<00:16:28.300> libraries<00:16:28.660> and 00:16:28.949 --> 00:16:28.959 align:start position:0% consistency between the libraries and 00:16:28.959 --> 00:16:32.280 align:start position:0% consistency between the libraries and you<00:16:29.290> know<00:16:29.379> choose<00:16:29.649> one<00:16:29.860> way<00:16:30.040> or<00:16:30.220> Dadar<00:16:30.990> also<00:16:31.990> a 00:16:32.280 --> 00:16:32.290 align:start position:0% you know choose one way or Dadar also a 00:16:32.290 --> 00:16:34.139 align:start position:0% you know choose one way or Dadar also a team<00:16:32.889> chess<00:16:33.100> was<00:16:33.279> mostly<00:16:33.549> written<00:16:33.610> like<00:16:33.999> two 00:16:34.139 --> 00:16:34.149 align:start position:0% team chess was mostly written like two 00:16:34.149 --> 00:16:36.269 align:start position:0% team chess was mostly written like two years<00:16:34.360> ago<00:16:34.420> and<00:16:34.629> it<00:16:34.869> has<00:16:35.049> been<00:16:35.350> upgraded<00:16:35.799> and 00:16:36.269 --> 00:16:36.279 align:start position:0% years ago and it has been upgraded and 00:16:36.279 --> 00:16:38.669 align:start position:0% years ago and it has been upgraded and improved<00:16:36.429> but<00:16:37.329> only<00:16:37.480> incrementally<00:16:38.230> it 00:16:38.669 --> 00:16:38.679 align:start position:0% improved but only incrementally it 00:16:38.679 --> 00:16:40.619 align:start position:0% improved but only incrementally it hasn't<00:16:39.129> been<00:16:39.279> it<00:16:39.670> hasn't<00:16:40.089> had<00:16:40.179> like<00:16:40.329> a<00:16:40.360> big 00:16:40.619 --> 00:16:40.629 align:start position:0% hasn't been it hasn't had like a big 00:16:40.629 --> 00:16:42.989 align:start position:0% hasn't been it hasn't had like a big wave<00:16:40.809> right<00:16:41.019> so<00:16:41.709> maybe<00:16:41.860> we<00:16:42.069> should<00:16:42.309> we<00:16:42.850> should 00:16:42.989 --> 00:16:42.999 align:start position:0% wave right so maybe we should we should 00:16:42.999 --> 00:16:44.939 align:start position:0% wave right so maybe we should we should consider<00:16:43.269> doing<00:16:43.420> like<00:16:43.779> bigger<00:16:44.049> changes<00:16:44.649> and 00:16:44.939 --> 00:16:44.949 align:start position:0% consider doing like bigger changes and 00:16:44.949 --> 00:16:48.289 align:start position:0% consider doing like bigger changes and you<00:16:45.519> know<00:16:45.610> improving<00:16:45.970> it<00:16:46.269> from<00:16:46.959> the<00:16:47.139> ground<00:16:47.379> up 00:16:48.289 --> 00:16:48.299 align:start position:0% you know improving it from the ground up 00:16:48.299 --> 00:16:51.989 align:start position:0% you know improving it from the ground up while<00:16:49.299> doing<00:16:49.509> test<00:16:49.689> improvements<00:16:50.319> we<00:16:50.499> may<00:16:50.999> you 00:16:51.989 --> 00:16:51.999 align:start position:0% while doing test improvements we may you 00:16:51.999 --> 00:16:52.980 align:start position:0% while doing test improvements we may you know<00:16:52.119> decide<00:16:52.449> on<00:16:52.600> choosing<00:16:52.839> a<00:16:52.899> different 00:16:52.980 --> 00:16:52.990 align:start position:0% know decide on choosing a different 00:16:52.990 --> 00:16:55.980 align:start position:0% know decide on choosing a different language<00:16:53.410> so<00:16:53.759> in<00:16:54.759> the<00:16:54.850> team<00:16:55.029> there's<00:16:55.269> like<00:16:55.480> a 00:16:55.980 --> 00:16:55.990 align:start position:0% language so in the team there's like a 00:16:55.990 --> 00:16:58.019 align:start position:0% language so in the team there's like a bit<00:16:56.649> of<00:16:56.679> understanding<00:16:57.129> that<00:16:57.429> they<00:16:57.579> may<00:16:57.970> be 00:16:58.019 --> 00:16:58.029 align:start position:0% bit of understanding that they may be 00:16:58.029 --> 00:17:00.059 align:start position:0% bit of understanding that they may be going<00:16:58.990> to<00:16:59.350> typescript 00:17:00.059 --> 00:17:00.069 align:start position:0% going to typescript 00:17:00.069 --> 00:17:04.490 align:start position:0% going to typescript would<00:17:01.029> give<00:17:01.269> us<00:17:01.480> some<00:17:01.720> benefits 00:17:04.490 --> 00:17:04.500 align:start position:0% 00:17:04.500 --> 00:17:08.240 align:start position:0% [Applause] 00:17:08.240 --> 00:17:08.250 align:start position:0% [Applause] 00:17:08.250 --> 00:17:10.470 align:start position:0% [Applause] okay<00:17:09.250> with<00:17:09.460> typescript<00:17:09.700> that<00:17:10.210> the<00:17:10.300> main 00:17:10.470 --> 00:17:10.480 align:start position:0% okay with typescript that the main 00:17:10.480 --> 00:17:13.130 align:start position:0% okay with typescript that the main benefit<00:17:10.900> there<00:17:11.110> is<00:17:11.290> types<00:17:11.710> types<00:17:12.040> and<00:17:12.280> types 00:17:13.130 --> 00:17:13.140 align:start position:0% benefit there is types types and types 00:17:13.140 --> 00:17:16.680 align:start position:0% benefit there is types types and types one<00:17:14.140> big<00:17:14.440> part<00:17:14.740> of<00:17:14.800> it<00:17:14.920> Ria's<00:17:15.310> today<00:17:15.580> is<00:17:15.820> with 00:17:16.680 --> 00:17:16.690 align:start position:0% one big part of it Ria's today is with 00:17:16.690 --> 00:17:18.570 align:start position:0% one big part of it Ria's today is with dealing<00:17:16.870> with<00:17:16.990> types<00:17:17.290> and<00:17:17.589> having<00:17:18.190> a<00:17:18.310> lot<00:17:18.460> of 00:17:18.570 --> 00:17:18.580 align:start position:0% dealing with types and having a lot of 00:17:18.580 --> 00:17:20.940 align:start position:0% dealing with types and having a lot of code<00:17:18.790> to<00:17:18.940> ensure<00:17:19.089> that<00:17:19.270> the<00:17:19.480> data<00:17:19.660> is<00:17:19.930> valid<00:17:20.170> if 00:17:20.940 --> 00:17:20.950 align:start position:0% code to ensure that the data is valid if 00:17:20.950 --> 00:17:22.200 align:start position:0% code to ensure that the data is valid if we<00:17:21.070> do<00:17:21.160> that<00:17:21.339> because<00:17:21.460> we<00:17:21.700> don't<00:17:21.790> have<00:17:21.970> types 00:17:22.200 --> 00:17:22.210 align:start position:0% we do that because we don't have types 00:17:22.210 --> 00:17:24.780 align:start position:0% we do that because we don't have types and<00:17:22.570> and<00:17:23.440> there<00:17:23.980> were<00:17:24.070> a<00:17:24.100> couple<00:17:24.130> of<00:17:24.400> bugs<00:17:24.580> with 00:17:24.780 --> 00:17:24.790 align:start position:0% and and there were a couple of bugs with 00:17:24.790 --> 00:17:28.070 align:start position:0% and and there were a couple of bugs with that<00:17:24.940> so<00:17:25.570> this<00:17:25.810> example<00:17:26.050> here<00:17:26.530> is<00:17:26.620> from<00:17:26.740> 2015 00:17:28.070 --> 00:17:28.080 align:start position:0% that so this example here is from 2015 00:17:28.080 --> 00:17:30.810 align:start position:0% that so this example here is from 2015 the<00:17:29.080> back<00:17:29.650> in<00:17:29.770> 2015<00:17:30.250> it<00:17:30.340> was<00:17:30.430> the<00:17:30.550> famous 00:17:30.810 --> 00:17:30.820 align:start position:0% the back in 2015 it was the famous 00:17:30.820 --> 00:17:34.470 align:start position:0% the back in 2015 it was the famous yttrium<00:17:31.420> J's<00:17:31.570> bug<00:17:32.190> where<00:17:33.190> in<00:17:33.430> 1<00:17:33.610> in<00:17:33.850> 256 00:17:34.470 --> 00:17:34.480 align:start position:0% yttrium J's bug where in 1 in 256 00:17:34.480 --> 00:17:36.540 align:start position:0% yttrium J's bug where in 1 in 256 instances<00:17:35.350> the<00:17:35.920> public<00:17:36.250> key<00:17:36.370> would<00:17:36.520> be 00:17:36.540 --> 00:17:36.550 align:start position:0% instances the public key would be 00:17:36.550 --> 00:17:39.840 align:start position:0% instances the public key would be invalid<00:17:37.180> and<00:17:37.450> some<00:17:38.350> ether<00:17:38.560> was<00:17:38.860> lost<00:17:39.100> during 00:17:39.840 --> 00:17:39.850 align:start position:0% invalid and some ether was lost during 00:17:39.850 --> 00:17:42.690 align:start position:0% invalid and some ether was lost during that<00:17:40.060> process<00:17:40.830> so<00:17:41.830> the<00:17:41.920> interest<00:17:42.160> example<00:17:42.580> we 00:17:42.690 --> 00:17:42.700 align:start position:0% that process so the interest example we 00:17:42.700 --> 00:17:43.950 align:start position:0% that process so the interest example we are<00:17:42.730> concatenating<00:17:43.000> the<00:17:43.510> x<00:17:43.660> and<00:17:43.810> y<00:17:43.900> components 00:17:43.950 --> 00:17:43.960 align:start position:0% are concatenating the x and y components 00:17:43.960 --> 00:17:46.380 align:start position:0% are concatenating the x and y components of<00:17:44.530> the<00:17:44.620> public<00:17:44.920> key<00:17:45.070> and<00:17:45.250> in<00:17:45.700> a<00:17:45.730> case<00:17:45.940> of<00:17:46.120> the<00:17:46.210> x 00:17:46.380 --> 00:17:46.390 align:start position:0% of the public key and in a case of the x 00:17:46.390 --> 00:17:48.450 align:start position:0% of the public key and in a case of the x component<00:17:46.660> because<00:17:47.590> it's<00:17:47.740> represented<00:17:48.250> as<00:17:48.340> an 00:17:48.450 --> 00:17:48.460 align:start position:0% component because it's represented as an 00:17:48.460 --> 00:17:50.790 align:start position:0% component because it's represented as an array<00:17:48.670> if<00:17:49.150> the<00:17:49.360> x<00:17:49.480> component<00:17:49.630> starts<00:17:50.140> with<00:17:50.410> a<00:17:50.440> 0 00:17:50.790 --> 00:17:50.800 align:start position:0% array if the x component starts with a 0 00:17:50.800 --> 00:17:53.490 align:start position:0% array if the x component starts with a 0 byte<00:17:51.070> that<00:17:51.730> is<00:17:51.880> just<00:17:52.120> ignored<00:17:52.450> we<00:17:53.230> wouldn't 00:17:53.490 --> 00:17:53.500 align:start position:0% byte that is just ignored we wouldn't 00:17:53.500 --> 00:17:55.110 align:start position:0% byte that is just ignored we wouldn't have<00:17:53.650> had<00:17:53.860> this<00:17:54.040> problem<00:17:54.250> with<00:17:54.880> typescript 00:17:55.110 --> 00:17:55.120 align:start position:0% have had this problem with typescript 00:17:55.120 --> 00:17:57.660 align:start position:0% have had this problem with typescript because<00:17:55.660> all<00:17:55.840> of<00:17:55.870> like<00:17:56.590> x<00:17:56.830> and<00:17:57.040> y<00:17:57.160> component 00:17:57.660 --> 00:17:57.670 align:start position:0% because all of like x and y component 00:17:57.670 --> 00:18:01.500 align:start position:0% because all of like x and y component would<00:17:57.760> have<00:17:58.000> been<00:17:58.210> a<00:17:58.450> proper<00:17:59.170> type<00:18:00.210> also<00:18:01.210> don't 00:18:01.500 --> 00:18:01.510 align:start position:0% would have been a proper type also don't 00:18:01.510 --> 00:18:04.590 align:start position:0% would have been a proper type also don't be<00:18:01.600> afraid<00:18:01.630> this<00:18:02.170> comet<00:18:02.980> is<00:18:03.070> from<00:18:03.250> 2015<00:18:03.940> the 00:18:04.590 --> 00:18:04.600 align:start position:0% be afraid this comet is from 2015 the 00:18:04.600 --> 00:18:06.240 align:start position:0% be afraid this comet is from 2015 the code<00:18:04.840> has<00:18:05.050> improved<00:18:05.380> it<00:18:05.680> doesn't<00:18:06.010> look<00:18:06.100> like 00:18:06.240 --> 00:18:06.250 align:start position:0% code has improved it doesn't look like 00:18:06.250 --> 00:18:09.930 align:start position:0% code has improved it doesn't look like this<00:18:06.370> anymore<00:18:08.340> some<00:18:09.340> other<00:18:09.460> reasons<00:18:09.820> for 00:18:09.930 --> 00:18:09.940 align:start position:0% this anymore some other reasons for 00:18:09.940 --> 00:18:12.630 align:start position:0% this anymore some other reasons for typescript<00:18:10.510> it<00:18:11.350> is<00:18:11.500> practically<00:18:12.220> a<00:18:12.340> typed 00:18:12.630 --> 00:18:12.640 align:start position:0% typescript it is practically a typed 00:18:12.640 --> 00:18:14.580 align:start position:0% typescript it is practically a typed extension<00:18:13.240> of<00:18:13.360> JavaScript<00:18:13.930> so<00:18:14.080> it<00:18:14.200> should 00:18:14.580 --> 00:18:14.590 align:start position:0% extension of JavaScript so it should 00:18:14.590 --> 00:18:16.890 align:start position:0% extension of JavaScript so it should look<00:18:14.620> familiar<00:18:14.890> to<00:18:15.220> everyone<00:18:15.820> who<00:18:16.690> has 00:18:16.890 --> 00:18:16.900 align:start position:0% look familiar to everyone who has 00:18:16.900 --> 00:18:18.360 align:start position:0% look familiar to everyone who has JavaScript<00:18:17.320> testing<00:18:17.560> favorite<00:18:17.830> language<00:18:18.160> and 00:18:18.360 --> 00:18:18.370 align:start position:0% JavaScript testing favorite language and 00:18:18.370 --> 00:18:20.010 align:start position:0% JavaScript testing favorite language and it<00:18:19.120> can<00:18:19.270> also<00:18:19.420> be<00:18:19.510> compiled<00:18:19.900> to<00:18:19.990> JavaScript 00:18:20.010 --> 00:18:20.020 align:start position:0% it can also be compiled to JavaScript 00:18:20.020 --> 00:18:22.710 align:start position:0% it can also be compiled to JavaScript and<00:18:20.620> it<00:18:20.740> can<00:18:20.890> be<00:18:21.010> mixed<00:18:21.220> with<00:18:21.550> JavaScript<00:18:22.240> that 00:18:22.710 --> 00:18:22.720 align:start position:0% and it can be mixed with JavaScript that 00:18:22.720 --> 00:18:25.260 align:start position:0% and it can be mixed with JavaScript that means<00:18:22.960> Java<00:18:23.500> code<00:18:23.710> can<00:18:23.890> be<00:18:23.920> imported<00:18:24.400> as<00:18:25.210> a 00:18:25.260 --> 00:18:25.270 align:start position:0% means Java code can be imported as a 00:18:25.270 --> 00:18:26.580 align:start position:0% means Java code can be imported as a result<00:18:25.720> we<00:18:25.870> don't<00:18:26.050> need<00:18:26.110> to<00:18:26.230> rewrite 00:18:26.580 --> 00:18:26.590 align:start position:0% result we don't need to rewrite 00:18:26.590 --> 00:18:28.860 align:start position:0% result we don't need to rewrite everything<00:18:26.980> at<00:18:27.250> once<00:18:27.490> we<00:18:27.700> can<00:18:27.880> do<00:18:28.030> it<00:18:28.180> step<00:18:28.840> by 00:18:28.860 --> 00:18:28.870 align:start position:0% everything at once we can do it step by 00:18:28.870 --> 00:18:31.440 align:start position:0% everything at once we can do it step by step<00:18:28.990> I<00:18:29.500> have<00:18:30.490> an<00:18:30.730> important<00:18:31.090> thing<00:18:31.300> to 00:18:31.440 --> 00:18:31.450 align:start position:0% step I have an important thing to 00:18:31.450 --> 00:18:34.020 align:start position:0% step I have an important thing to mention<00:18:31.570> here<00:18:31.780> is<00:18:31.990> assembly<00:18:32.650> script<00:18:33.030> so 00:18:34.020 --> 00:18:34.030 align:start position:0% mention here is assembly script so 00:18:34.030 --> 00:18:36.690 align:start position:0% mention here is assembly script so assembly<00:18:34.390> script<00:18:34.630> is<00:18:34.840> a<00:18:35.670> subset<00:18:36.670> of 00:18:36.690 --> 00:18:36.700 align:start position:0% assembly script is a subset of 00:18:36.700 --> 00:18:38.010 align:start position:0% assembly script is a subset of typescript<00:18:37.120> which<00:18:37.420> can<00:18:37.600> be<00:18:37.690> competitive 00:18:38.010 --> 00:18:38.020 align:start position:0% typescript which can be competitive 00:18:38.020 --> 00:18:40.140 align:start position:0% typescript which can be competitive webassembly<00:18:38.610> kisi<00:18:39.610> has<00:18:39.700> mentioned<00:18:39.880> the 00:18:40.140 --> 00:18:40.150 align:start position:0% webassembly kisi has mentioned the 00:18:40.150 --> 00:18:41.910 align:start position:0% webassembly kisi has mentioned the bottom<00:18:40.480> as<00:18:40.660> like<00:18:40.990> a<00:18:41.020> future<00:18:41.440> potential 00:18:41.910 --> 00:18:41.920 align:start position:0% bottom as like a future potential 00:18:41.920 --> 00:18:44.460 align:start position:0% bottom as like a future potential execution<00:18:42.550> engine<00:18:42.820> and<00:18:43.000> so<00:18:43.780> assembly<00:18:44.170> script 00:18:44.460 --> 00:18:44.470 align:start position:0% execution engine and so assembly script 00:18:44.470 --> 00:18:47.340 align:start position:0% execution engine and so assembly script and<00:18:44.970> supporting<00:18:45.970> typescript<00:18:46.360> nerium<00:18:46.930> Jason 00:18:47.340 --> 00:18:47.350 align:start position:0% and supporting typescript nerium Jason 00:18:47.350 --> 00:18:48.690 align:start position:0% and supporting typescript nerium Jason having<00:18:47.530> assembly<00:18:47.950> script<00:18:48.190> would<00:18:48.250> enable<00:18:48.520> us 00:18:48.690 --> 00:18:48.700 align:start position:0% having assembly script would enable us 00:18:48.700 --> 00:18:51.180 align:start position:0% having assembly script would enable us to<00:18:48.730> write<00:18:49.060> smart<00:18:49.480> contracts<00:18:50.050> in<00:18:50.200> JavaScript 00:18:51.180 --> 00:18:51.190 align:start position:0% to write smart contracts in JavaScript 00:18:51.190 --> 00:18:54.600 align:start position:0% to write smart contracts in JavaScript and<00:18:51.400> have<00:18:52.300> it<00:18:52.420> only<00:18:52.570> wasn't<00:18:53.160> and<00:18:54.160> what<00:18:54.310> doing 00:18:54.600 --> 00:18:54.610 align:start position:0% and have it only wasn't and what doing 00:18:54.610 --> 00:18:56.250 align:start position:0% and have it only wasn't and what doing this<00:18:54.700> right<00:18:55.060> be<00:18:55.270> an<00:18:55.360> opportunity<00:18:55.870> to<00:18:55.990> make 00:18:56.250 --> 00:18:56.260 align:start position:0% this right be an opportunity to make 00:18:56.260 --> 00:18:59.360 align:start position:0% this right be an opportunity to make things<00:18:56.440> right<00:18:56.710> and<00:18:56.770> did<00:18:57.040> it<00:18:57.220> redesign<00:18:57.820> it<00:18:57.970> well 00:18:59.360 --> 00:18:59.370 align:start position:0% things right and did it redesign it well 00:18:59.370 --> 00:19:02.550 align:start position:0% things right and did it redesign it well ok<00:19:00.370> what's<00:19:00.610> the<00:19:00.700> future<00:19:00.910> like<00:19:01.150> so<00:19:02.080> today 00:19:02.550 --> 00:19:02.560 align:start position:0% ok what's the future like so today 00:19:02.560 --> 00:19:03.780 align:start position:0% ok what's the future like so today there's<00:19:02.860> already<00:19:03.100> an<00:19:03.370> incomplete 00:19:03.780 --> 00:19:03.790 align:start position:0% there's already an incomplete 00:19:03.790 --> 00:19:06.720 align:start position:0% there's already an incomplete implementation<00:19:03.910> of<00:19:04.680> the<00:19:05.680> EVM<00:19:06.100> in<00:19:06.220> typescript 00:19:06.720 --> 00:19:06.730 align:start position:0% implementation of the EVM in typescript 00:19:06.730 --> 00:19:09.060 align:start position:0% implementation of the EVM in typescript and<00:19:06.910> it's<00:19:07.420> not<00:19:07.660> done<00:19:07.840> by<00:19:08.020> this<00:19:08.080> team<00:19:08.410> it's<00:19:08.920> done 00:19:09.060 --> 00:19:09.070 align:start position:0% and it's not done by this team it's done 00:19:09.070 --> 00:19:11.280 align:start position:0% and it's not done by this team it's done by<00:19:09.190> someone<00:19:09.400> else<00:19:09.610> and<00:19:09.880> our<00:19:10.630> own<00:19:10.780> initiative 00:19:11.280 --> 00:19:11.290 align:start position:0% by someone else and our own initiative 00:19:11.290 --> 00:19:14.100 align:start position:0% by someone else and our own initiative is<00:19:11.410> called<00:19:11.470> et<00:19:11.800> MTS<00:19:12.210> but<00:19:13.210> it<00:19:13.360> features<00:19:13.660> the 00:19:14.100 --> 00:19:14.110 align:start position:0% is called et MTS but it features the 00:19:14.110 --> 00:19:17.190 align:start position:0% is called et MTS but it features the chess<00:19:14.490> team<00:19:15.520> well<00:19:16.090> the<00:19:16.780> single<00:19:17.020> person 00:19:17.190 --> 00:19:17.200 align:start position:0% chess team well the single person 00:19:17.200 --> 00:19:20.340 align:start position:0% chess team well the single person working<00:19:17.500> on<00:19:17.680> it<00:19:17.910> has<00:19:18.910> done<00:19:19.450> a<00:19:19.480> lot<00:19:19.690> of<00:19:19.720> work<00:19:20.080> in 00:19:20.340 --> 00:19:20.350 align:start position:0% working on it has done a lot of work in 00:19:20.350 --> 00:19:21.769 align:start position:0% working on it has done a lot of work in rewriting<00:19:21.160> the<00:19:21.250> code<00:19:21.340> inside 00:19:21.769 --> 00:19:21.779 align:start position:0% rewriting the code inside 00:19:21.779 --> 00:19:25.039 align:start position:0% rewriting the code inside yep<00:19:21.929> I<00:19:22.139> think<00:19:22.859> we<00:19:23.340> shouldn't<00:19:23.669> hey<00:19:23.940> I<00:19:24.299> think<00:19:24.779> we 00:19:25.039 --> 00:19:25.049 align:start position:0% yep I think we shouldn't hey I think we 00:19:25.049 --> 00:19:26.629 align:start position:0% yep I think we shouldn't hey I think we shouldn't<00:19:25.469> have<00:19:26.009> all<00:19:26.129> these<00:19:26.309> competing 00:19:26.629 --> 00:19:26.639 align:start position:0% shouldn't have all these competing 00:19:26.639 --> 00:19:28.969 align:start position:0% shouldn't have all these competing projects<00:19:27.239> and<00:19:28.049> we<00:19:28.169> should<00:19:28.409> just<00:19:28.619> combine<00:19:28.950> our 00:19:28.969 --> 00:19:28.979 align:start position:0% projects and we should just combine our 00:19:28.979 --> 00:19:31.700 align:start position:0% projects and we should just combine our efforts<00:19:29.249> and<00:19:29.940> have<00:19:30.179> one<00:19:30.389> complete<00:19:30.929> fully 00:19:31.700 --> 00:19:31.710 align:start position:0% efforts and have one complete fully 00:19:31.710 --> 00:19:34.399 align:start position:0% efforts and have one complete fully tested<00:19:32.279> comprehensive<00:19:33.269> idiom<00:19:33.869> typescript 00:19:34.399 --> 00:19:34.409 align:start position:0% tested comprehensive idiom typescript 00:19:34.409 --> 00:19:36.349 align:start position:0% tested comprehensive idiom typescript implementation<00:19:35.039> so<00:19:35.940> I<00:19:35.969> think<00:19:36.090> that's<00:19:36.269> the 00:19:36.349 --> 00:19:36.359 align:start position:0% implementation so I think that's the 00:19:36.359 --> 00:19:39.910 align:start position:0% implementation so I think that's the future<00:19:37.099> thank<00:19:38.099> you 00:19:39.910 --> 00:19:39.920 align:start position:0% future thank you 00:19:39.920 --> 00:19:48.930 align:start position:0% future thank you [Applause] 00:19:48.930 --> 00:19:48.940 align:start position:0% 00:19:48.940 --> 00:19:51.000 align:start position:0% you