WEBVTT Kind: captions Language: en 00:00:00.050 --> 00:00:02.480 align:start position:0% okay<00:00:01.050> so<00:00:01.110> we<00:00:01.380> this<00:00:01.770> is<00:00:01.979> the<00:00:02.010> II<00:00:02.190> was<00:00:02.460> in 00:00:02.480 --> 00:00:02.490 align:start position:0% okay so we this is the II was in 00:00:02.490 --> 00:00:05.599 align:start position:0% okay so we this is the II was in breakout<00:00:02.879> session<00:00:03.300> that's<00:00:03.959> our<00:00:04.080> logo<00:00:04.609> this 00:00:05.599 --> 00:00:05.609 align:start position:0% breakout session that's our logo this 00:00:05.609 --> 00:00:07.550 align:start position:0% breakout session that's our logo this first<00:00:05.879> time<00:00:06.029> we<00:00:06.150> have<00:00:06.270> shown<00:00:06.450> the<00:00:06.569> logo<00:00:06.810> please 00:00:07.550 --> 00:00:07.560 align:start position:0% first time we have shown the logo please 00:00:07.560 --> 00:00:10.759 align:start position:0% first time we have shown the logo please remember<00:00:07.799> it<00:00:08.010> um<00:00:08.660> if<00:00:09.660> you<00:00:10.469> want<00:00:10.590> to<00:00:10.650> take 00:00:10.759 --> 00:00:10.769 align:start position:0% remember it um if you want to take 00:00:10.769 --> 00:00:15.259 align:start position:0% remember it um if you want to take photos<00:00:11.070> we<00:00:11.610> don't<00:00:11.790> have<00:00:11.880> time<00:00:11.969> for<00:00:12.030> that<00:00:14.269> okay 00:00:15.259 --> 00:00:15.269 align:start position:0% photos we don't have time for that okay 00:00:15.269 --> 00:00:17.720 align:start position:0% photos we don't have time for that okay thank<00:00:15.570> you<00:00:15.630> all<00:00:15.719> for<00:00:16.049> coming<00:00:16.080> this<00:00:16.590> is<00:00:17.430> all<00:00:17.580> the 00:00:17.720 --> 00:00:17.730 align:start position:0% thank you all for coming this is all the 00:00:17.730 --> 00:00:19.820 align:start position:0% thank you all for coming this is all the content<00:00:17.850> we're<00:00:18.180> gonna<00:00:18.270> have<00:00:18.449> here<00:00:18.750> so<00:00:19.380> I'm 00:00:19.820 --> 00:00:19.830 align:start position:0% content we're gonna have here so I'm 00:00:19.830 --> 00:00:21.710 align:start position:0% content we're gonna have here so I'm gonna<00:00:19.949> start<00:00:20.250> with<00:00:20.369> some<00:00:20.430> kind<00:00:20.670> of<00:00:20.760> intro<00:00:21.090> high 00:00:21.710 --> 00:00:21.720 align:start position:0% gonna start with some kind of intro high 00:00:21.720 --> 00:00:23.240 align:start position:0% gonna start with some kind of intro high level<00:00:21.990> intro<00:00:22.289> and<00:00:22.560> what<00:00:22.769> was<00:00:22.949> amazed<00:00:23.220> it 00:00:23.240 --> 00:00:23.250 align:start position:0% level intro and what was amazed it 00:00:23.250 --> 00:00:26.150 align:start position:0% level intro and what was amazed it cetera<00:00:23.730> and<00:00:24.029> then<00:00:24.960> we<00:00:25.109> dive<00:00:25.590> a<00:00:25.619> bit<00:00:25.920> deeper 00:00:26.150 --> 00:00:26.160 align:start position:0% cetera and then we dive a bit deeper 00:00:26.160 --> 00:00:29.630 align:start position:0% cetera and then we dive a bit deeper into<00:00:27.199> the<00:00:28.199> tooling<00:00:28.529> behave<00:00:28.830> the<00:00:29.070> languages<00:00:29.490> we 00:00:29.630 --> 00:00:29.640 align:start position:0% into the tooling behave the languages we 00:00:29.640 --> 00:00:32.690 align:start position:0% into the tooling behave the languages we have<00:00:30.380> we<00:00:31.410> after<00:00:31.980> that<00:00:32.099> we<00:00:32.219> go<00:00:32.340> into<00:00:32.489> this 00:00:32.690 --> 00:00:32.700 align:start position:0% have we after that we go into this 00:00:32.700 --> 00:00:35.540 align:start position:0% have we after that we go into this really<00:00:33.180> hard<00:00:33.390> core<00:00:33.660> part<00:00:33.930> of<00:00:34.110> edmc<00:00:34.649> and<00:00:34.950> ABMC 00:00:35.540 --> 00:00:35.550 align:start position:0% really hard core part of edmc and ABMC 00:00:35.550 --> 00:00:37.490 align:start position:0% really hard core part of edmc and ABMC is<00:00:35.730> like<00:00:35.910> a<00:00:35.940> connection<00:00:36.360> layer<00:00:36.660> between<00:00:36.899> VMs 00:00:37.490 --> 00:00:37.500 align:start position:0% is like a connection layer between VMs 00:00:37.500 --> 00:00:40.580 align:start position:0% is like a connection layer between VMs and<00:00:37.680> clients<00:00:38.340> and<00:00:38.520> so<00:00:39.270> if<00:00:39.390> you<00:00:39.510> are<00:00:39.660> client<00:00:40.500> in 00:00:40.580 --> 00:00:40.590 align:start position:0% and clients and so if you are client in 00:00:40.590 --> 00:00:42.470 align:start position:0% and clients and so if you are client in implementer<00:00:41.280> you<00:00:41.610> should<00:00:41.790> definitely<00:00:42.329> watch 00:00:42.470 --> 00:00:42.480 align:start position:0% implementer you should definitely watch 00:00:42.480 --> 00:00:44.779 align:start position:0% implementer you should definitely watch that<00:00:42.780> and<00:00:43.020> also<00:00:43.829> probably<00:00:44.070> going<00:00:44.250> to<00:00:44.430> deep 00:00:44.779 --> 00:00:44.789 align:start position:0% that and also probably going to deep 00:00:44.789 --> 00:00:46.790 align:start position:0% that and also probably going to deep dive<00:00:44.820> a<00:00:45.030> bit<00:00:45.270> more<00:00:45.450> into<00:00:45.719> the<00:00:46.230> interfaces 00:00:46.790 --> 00:00:46.800 align:start position:0% dive a bit more into the interfaces 00:00:46.800 --> 00:00:49.790 align:start position:0% dive a bit more into the interfaces that's<00:00:47.489> the<00:00:47.610> e<00:00:47.640> I<00:00:47.789> and<00:00:48.270> that's<00:00:48.719> a<00:00:48.870> way<00:00:48.989> to<00:00:49.469> write 00:00:49.790 --> 00:00:49.800 align:start position:0% that's the e I and that's a way to write 00:00:49.800 --> 00:00:53.240 align:start position:0% that's the e I and that's a way to write contracts<00:00:50.489> in<00:00:51.030> it<00:00:51.210> was<00:00:51.329> em<00:00:51.510> and<00:00:51.890> then<00:00:52.890> the<00:00:53.070> most 00:00:53.240 --> 00:00:53.250 align:start position:0% contracts in it was em and then the most 00:00:53.250 --> 00:00:55.880 align:start position:0% contracts in it was em and then the most important<00:00:53.670> part<00:00:53.910> is<00:00:54.149> the<00:00:54.480> test<00:00:54.930> net<00:00:55.110> so 00:00:55.880 --> 00:00:55.890 align:start position:0% important part is the test net so 00:00:55.890 --> 00:00:57.170 align:start position:0% important part is the test net so hopefully<00:00:56.129> we<00:00:56.219> got<00:00:56.370> we<00:00:56.579> can<00:00:56.699> I<00:00:56.730> have<00:00:56.879> a<00:00:56.910> demo 00:00:57.170 --> 00:00:57.180 align:start position:0% hopefully we got we can I have a demo 00:00:57.180 --> 00:00:59.810 align:start position:0% hopefully we got we can I have a demo here<00:00:57.629> and<00:00:57.840> we<00:00:58.649> gonna<00:00:58.770> give<00:00:59.190> you<00:00:59.309> a<00:00:59.340> glimpse<00:00:59.579> how 00:00:59.810 --> 00:00:59.820 align:start position:0% here and we gonna give you a glimpse how 00:00:59.820 --> 00:01:01.700 align:start position:0% here and we gonna give you a glimpse how to<00:00:59.879> use<00:01:00.090> the<00:01:00.239> test<00:01:00.420> net<00:01:00.629> which<00:01:01.260> is<00:01:01.289> already 00:01:01.700 --> 00:01:01.710 align:start position:0% to use the test net which is already 00:01:01.710 --> 00:01:06.500 align:start position:0% to use the test net which is already life<00:01:02.180> is<00:01:03.180> so<00:01:03.300> good<00:01:03.480> okay<00:01:05.000> so<00:01:06.000> we<00:01:06.090> blend<00:01:06.270> this 00:01:06.500 --> 00:01:06.510 align:start position:0% life is so good okay so we blend this 00:01:06.510 --> 00:01:08.649 align:start position:0% life is so good okay so we blend this part<00:01:06.990> to<00:01:07.140> be<00:01:07.229> rough<00:01:07.439> like<00:01:07.619> 40<00:01:07.979> minutes<00:01:08.100> and 00:01:08.649 --> 00:01:08.659 align:start position:0% part to be rough like 40 minutes and 00:01:08.659 --> 00:01:12.469 align:start position:0% part to be rough like 40 minutes and it's<00:01:09.659> really<00:01:09.960> strict<00:01:10.650> in<00:01:11.100> length<00:01:11.520> and<00:01:11.820> time<00:01:12.210> so 00:01:12.469 --> 00:01:12.479 align:start position:0% it's really strict in length and time so 00:01:12.479 --> 00:01:14.840 align:start position:0% it's really strict in length and time so we<00:01:12.600> don't<00:01:12.780> have<00:01:12.990> time<00:01:13.290> during<00:01:13.710> those<00:01:14.070> to<00:01:14.700> have 00:01:14.840 --> 00:01:14.850 align:start position:0% we don't have time during those to have 00:01:14.850 --> 00:01:17.780 align:start position:0% we don't have time during those to have questions<00:01:15.420> but<00:01:16.200> we<00:01:16.320> did<00:01:16.619> reserve<00:01:17.009> a<00:01:17.220> time<00:01:17.490> like 00:01:17.780 --> 00:01:17.790 align:start position:0% questions but we did reserve a time like 00:01:17.790 --> 00:01:19.390 align:start position:0% questions but we did reserve a time like a<00:01:17.820> ten<00:01:18.030> minutes<00:01:18.270> thought<00:01:18.450> after<00:01:19.110> these 00:01:19.390 --> 00:01:19.400 align:start position:0% a ten minutes thought after these 00:01:19.400 --> 00:01:22.249 align:start position:0% a ten minutes thought after these introductory<00:01:20.400> parts<00:01:20.909> to<00:01:21.390> have<00:01:21.600> a<00:01:21.630> longer<00:01:21.810> Q&A 00:01:22.249 --> 00:01:22.259 align:start position:0% introductory parts to have a longer Q&A 00:01:22.259 --> 00:01:24.679 align:start position:0% introductory parts to have a longer Q&A section<00:01:22.500> so<00:01:23.100> please<00:01:23.310> keep<00:01:23.850> your<00:01:23.909> questions<00:01:24.270> to 00:01:24.679 --> 00:01:24.689 align:start position:0% section so please keep your questions to 00:01:24.689 --> 00:01:26.420 align:start position:0% section so please keep your questions to that<00:01:24.780> point<00:01:25.049> and<00:01:25.290> then<00:01:25.860> depending<00:01:26.189> on<00:01:26.280> you 00:01:26.420 --> 00:01:26.430 align:start position:0% that point and then depending on you 00:01:26.430 --> 00:01:28.039 align:start position:0% that point and then depending on you don't<00:01:26.580> have<00:01:26.729> tired<00:01:27.090> people<00:01:27.450> are<00:01:27.540> we<00:01:27.720> can<00:01:27.900> take 00:01:28.039 --> 00:01:28.049 align:start position:0% don't have tired people are we can take 00:01:28.049 --> 00:01:29.990 align:start position:0% don't have tired people are we can take like<00:01:28.200> a<00:01:28.229> five-minute<00:01:28.439> break<00:01:28.710> or<00:01:29.400> we<00:01:29.610> can<00:01:29.759> go 00:01:29.990 --> 00:01:30.000 align:start position:0% like a five-minute break or we can go 00:01:30.000 --> 00:01:32.840 align:start position:0% like a five-minute break or we can go even<00:01:30.299> deeper<00:01:30.420> with<00:01:31.079> the<00:01:31.170> second<00:01:31.590> block<00:01:31.850> and 00:01:32.840 --> 00:01:32.850 align:start position:0% even deeper with the second block and 00:01:32.850 --> 00:01:34.100 align:start position:0% even deeper with the second block and the<00:01:32.909> second<00:01:33.240> block<00:01:33.420> it's<00:01:33.600> gonna<00:01:33.720> be<00:01:33.869> a<00:01:33.900> lot<00:01:34.079> of 00:01:34.100 --> 00:01:34.110 align:start position:0% the second block it's gonna be a lot of 00:01:34.110 --> 00:01:36.170 align:start position:0% the second block it's gonna be a lot of research<00:01:34.500> questions<00:01:35.040> and<00:01:35.250> all<00:01:35.640> the<00:01:35.700> really 00:01:36.170 --> 00:01:36.180 align:start position:0% research questions and all the really 00:01:36.180 --> 00:01:38.090 align:start position:0% research questions and all the really interesting<00:01:36.420> things<00:01:36.960> are<00:01:37.560> gonna<00:01:37.799> have<00:01:37.979> him 00:01:38.090 --> 00:01:38.100 align:start position:0% interesting things are gonna have him 00:01:38.100 --> 00:01:40.609 align:start position:0% interesting things are gonna have him there<00:01:38.280> and<00:01:39.240> lastly<00:01:39.540> if<00:01:39.869> we<00:01:40.079> still<00:01:40.290> have<00:01:40.380> time 00:01:40.609 --> 00:01:40.619 align:start position:0% there and lastly if we still have time 00:01:40.619 --> 00:01:41.480 align:start position:0% there and lastly if we still have time we<00:01:40.799> can<00:01:40.920> have<00:01:41.009> a<00:01:41.070> QA 00:01:41.480 --> 00:01:41.490 align:start position:0% we can have a QA 00:01:41.490 --> 00:01:45.830 align:start position:0% we can have a QA part<00:01:42.270> after<00:01:42.420> that<00:01:43.790> okay<00:01:44.790> so<00:01:44.850> Appetit<00:01:45.509> was<00:01:45.720> in 00:01:45.830 --> 00:01:45.840 align:start position:0% part after that okay so Appetit was in 00:01:45.840 --> 00:01:48.889 align:start position:0% part after that okay so Appetit was in itself<00:01:46.110> it's<00:01:46.439> just<00:01:46.530> introduction<00:01:47.220> and<00:01:47.899> my 00:01:48.889 --> 00:01:48.899 align:start position:0% itself it's just introduction and my 00:01:48.899 --> 00:01:50.780 align:start position:0% itself it's just introduction and my name<00:01:49.049> is<00:01:49.170> Alex<00:01:49.439> or<00:01:49.710> actually<00:01:50.280> gonna<00:01:50.399> github 00:01:50.780 --> 00:01:50.790 align:start position:0% name is Alex or actually gonna github 00:01:50.790 --> 00:01:53.569 align:start position:0% name is Alex or actually gonna github that's<00:01:51.210> have<00:01:51.630> more<00:01:51.990> people<00:01:52.290> know<00:01:52.380> me<00:01:52.560> and<00:01:52.740> I've 00:01:53.569 --> 00:01:53.579 align:start position:0% that's have more people know me and I've 00:01:53.579 --> 00:01:55.100 align:start position:0% that's have more people know me and I've been<00:01:53.790> working<00:01:54.030> on<00:01:54.240> it<00:01:54.360> was<00:01:54.479> em<00:01:54.689> for<00:01:54.930> a<00:01:54.960> while 00:01:55.100 --> 00:01:55.110 align:start position:0% been working on it was em for a while 00:01:55.110 --> 00:01:57.950 align:start position:0% been working on it was em for a while and<00:01:55.409> I<00:01:55.829> also<00:01:56.009> work<00:01:56.250> on<00:01:56.369> solidity<00:01:56.960> language 00:01:57.950 --> 00:01:57.960 align:start position:0% and I also work on solidity language 00:01:57.960 --> 00:02:02.030 align:start position:0% and I also work on solidity language design<00:01:58.200> and<00:01:58.380> a<00:01:58.409> compiler<00:01:59.600> but<00:02:00.600> first<00:02:01.079> let's 00:02:02.030 --> 00:02:02.040 align:start position:0% design and a compiler but first let's 00:02:02.040 --> 00:02:04.670 align:start position:0% design and a compiler but first let's just<00:02:02.100> take<00:02:02.430> a<00:02:02.729> step<00:02:02.909> back<00:02:03.420> and<00:02:03.719> this<00:02:04.350> is<00:02:04.409> just 00:02:04.670 --> 00:02:04.680 align:start position:0% just take a step back and this is just 00:02:04.680 --> 00:02:07.089 align:start position:0% just take a step back and this is just really<00:02:04.860> just<00:02:04.920> a<00:02:05.159> high-level<00:02:05.369> goal<00:02:05.939> and<00:02:06.299> vision 00:02:07.089 --> 00:02:07.099 align:start position:0% really just a high-level goal and vision 00:02:07.099 --> 00:02:10.940 align:start position:0% really just a high-level goal and vision we<00:02:08.099> want<00:02:08.190> to<00:02:08.310> talk<00:02:08.489> a<00:02:08.520> bit<00:02:08.640> about<00:02:08.869> so<00:02:09.869> today<00:02:09.950> we 00:02:10.940 --> 00:02:10.950 align:start position:0% we want to talk a bit about so today we 00:02:10.950 --> 00:02:13.040 align:start position:0% we want to talk a bit about so today we still<00:02:11.160> say<00:02:11.489> that<00:02:11.700> we<00:02:11.849> are<00:02:11.910> in<00:02:12.000> a<00:02:12.030> web<00:02:12.239> 3.0<00:02:12.810> vert 00:02:13.040 --> 00:02:13.050 align:start position:0% still say that we are in a web 3.0 vert 00:02:13.050 --> 00:02:13.910 align:start position:0% still say that we are in a web 3.0 vert but<00:02:13.200> I<00:02:13.230> don't<00:02:13.470> think<00:02:13.650> your 00:02:13.910 --> 00:02:13.920 align:start position:0% but I don't think your 00:02:13.920 --> 00:02:16.309 align:start position:0% but I don't think your Vetri<00:02:14.340> point<00:02:14.550> over<00:02:14.819> yet<00:02:15.090> you're<00:02:15.930> kind<00:02:16.140> of<00:02:16.200> like 00:02:16.309 --> 00:02:16.319 align:start position:0% Vetri point over yet you're kind of like 00:02:16.319 --> 00:02:19.580 align:start position:0% Vetri point over yet you're kind of like in<00:02:16.440> a<00:02:16.500> 2.5<00:02:17.069> stage<00:02:17.370> and<00:02:18.239> at<00:02:18.390> this<00:02:18.510> stage<00:02:18.590> divides 00:02:19.580 --> 00:02:19.590 align:start position:0% in a 2.5 stage and at this stage divides 00:02:19.590 --> 00:02:22.520 align:start position:0% in a 2.5 stage and at this stage divides mine<00:02:19.920> contracts<00:02:20.459> in<00:02:20.520> a<00:02:20.580> language<00:02:21.290> we<00:02:22.290> write 00:02:22.520 --> 00:02:22.530 align:start position:0% mine contracts in a language we write 00:02:22.530 --> 00:02:24.830 align:start position:0% mine contracts in a language we write some<00:02:22.739> kind<00:02:22.920> of<00:02:23.069> presentation<00:02:23.520> and<00:02:24.120> a 00:02:24.830 --> 00:02:24.840 align:start position:0% some kind of presentation and a 00:02:24.840 --> 00:02:27.199 align:start position:0% some kind of presentation and a client-side<00:02:25.230> code<00:02:25.440> like<00:02:25.650> the<00:02:25.739> front<00:02:25.980> end<00:02:26.209> and 00:02:27.199 --> 00:02:27.209 align:start position:0% client-side code like the front end and 00:02:27.209 --> 00:02:28.640 align:start position:0% client-side code like the front end and these<00:02:27.360> are<00:02:27.480> done<00:02:27.660> independently<00:02:28.380> of<00:02:28.530> each 00:02:28.640 --> 00:02:28.650 align:start position:0% these are done independently of each 00:02:28.650 --> 00:02:31.150 align:start position:0% these are done independently of each other<00:02:28.830> and<00:02:29.550> then<00:02:30.420> they<00:02:30.540> are<00:02:30.690> also 00:02:31.150 --> 00:02:31.160 align:start position:0% other and then they are also 00:02:31.160 --> 00:02:35.990 align:start position:0% other and then they are also independently<00:02:32.160> deployed<00:02:32.880> and<00:02:33.980> nobody<00:02:35.000> nobody 00:02:35.990 --> 00:02:36.000 align:start position:0% independently deployed and nobody nobody 00:02:36.000 --> 00:02:37.460 align:start position:0% independently deployed and nobody nobody has<00:02:36.330> like<00:02:36.480> any<00:02:36.630> connection<00:02:36.989> between<00:02:37.020> these 00:02:37.460 --> 00:02:37.470 align:start position:0% has like any connection between these 00:02:37.470 --> 00:02:39.680 align:start position:0% has like any connection between these and<00:02:37.770> usually<00:02:38.400> the<00:02:38.760> person<00:02:39.000> working<00:02:39.569> on<00:02:39.630> the 00:02:39.680 --> 00:02:39.690 align:start position:0% and usually the person working on the 00:02:39.690 --> 00:02:42.020 align:start position:0% and usually the person working on the contract<00:02:40.319> versus<00:02:40.709> version<00:02:41.069> person<00:02:41.760> work<00:02:41.910> in 00:02:42.020 --> 00:02:42.030 align:start position:0% contract versus version person work in 00:02:42.030 --> 00:02:44.360 align:start position:0% contract versus version person work in the<00:02:42.120> front<00:02:42.360> end<00:02:42.569> is<00:02:42.750> a<00:02:43.140> different<00:02:43.560> guy<00:02:43.680> or 00:02:44.360 --> 00:02:44.370 align:start position:0% the front end is a different guy or 00:02:44.370 --> 00:02:48.140 align:start position:0% the front end is a different guy or different<00:02:44.730> girl<00:02:44.849> and<00:02:45.620> they<00:02:46.620> have<00:02:46.880> maybe<00:02:47.880> don't 00:02:48.140 --> 00:02:48.150 align:start position:0% different girl and they have maybe don't 00:02:48.150 --> 00:02:49.640 align:start position:0% different girl and they have maybe don't have<00:02:48.269> too<00:02:48.360> much<00:02:48.480> connection<00:02:48.780> between<00:02:49.019> the<00:02:49.500> two 00:02:49.640 --> 00:02:49.650 align:start position:0% have too much connection between the two 00:02:49.650 --> 00:02:52.970 align:start position:0% have too much connection between the two parts<00:02:49.980> so<00:02:50.670> it's<00:02:51.030> not<00:02:51.180> really<00:02:51.420> integrated<00:02:51.980> but 00:02:52.970 --> 00:02:52.980 align:start position:0% parts so it's not really integrated but 00:02:52.980 --> 00:02:55.520 align:start position:0% parts so it's not really integrated but I<00:02:53.010> think<00:02:53.250> in<00:02:53.370> web<00:02:53.610> 3<00:02:53.910> all<00:02:54.780> of<00:02:55.049> this<00:02:55.170> should<00:02:55.380> be 00:02:55.520 --> 00:02:55.530 align:start position:0% I think in web 3 all of this should be 00:02:55.530 --> 00:02:58.150 align:start position:0% I think in web 3 all of this should be very<00:02:55.739> more<00:02:55.950> seamless<00:02:56.430> than<00:02:56.880> it<00:02:57.000> is<00:02:57.150> today<00:02:57.299> and 00:02:58.150 --> 00:02:58.160 align:start position:0% very more seamless than it is today and 00:02:58.160 --> 00:03:02.870 align:start position:0% very more seamless than it is today and I<00:02:59.160> think<00:02:59.220> that<00:03:00.799> this<00:03:01.799> is<00:03:01.950> like<00:03:02.100> an<00:03:02.250> idea<00:03:02.519> right 00:03:02.870 --> 00:03:02.880 align:start position:0% I think that this is like an idea right 00:03:02.880 --> 00:03:06.440 align:start position:0% I think that this is like an idea right this<00:03:03.060> could<00:03:03.239> look<00:03:03.390> like<00:03:04.910> so<00:03:05.910> basically<00:03:06.239> if<00:03:06.420> you 00:03:06.440 --> 00:03:06.450 align:start position:0% this could look like so basically if you 00:03:06.450 --> 00:03:10.340 align:start position:0% this could look like so basically if you look<00:03:06.569> at<00:03:08.450> this<00:03:09.450> this<00:03:09.630> would<00:03:09.840> be<00:03:09.930> like<00:03:10.049> the<00:03:10.200> dot 00:03:10.340 --> 00:03:10.350 align:start position:0% look at this this would be like the dot 00:03:10.350 --> 00:03:12.440 align:start position:0% look at this this would be like the dot from<00:03:10.590> from<00:03:10.830> the<00:03:10.950> front<00:03:11.220> and<00:03:11.430> on<00:03:11.610> okay<00:03:12.239> and 00:03:12.440 --> 00:03:12.450 align:start position:0% from from the front and on okay and 00:03:12.450 --> 00:03:14.900 align:start position:0% from from the front and on okay and there's<00:03:13.080> one<00:03:13.319> single<00:03:13.739> part<00:03:14.040> called<00:03:14.819> the 00:03:14.900 --> 00:03:14.910 align:start position:0% there's one single part called the 00:03:14.910 --> 00:03:16.759 align:start position:0% there's one single part called the transfer<00:03:15.239> function<00:03:15.660> which<00:03:16.170> is<00:03:16.319> only<00:03:16.500> part 00:03:16.759 --> 00:03:16.769 align:start position:0% transfer function which is only part 00:03:16.769 --> 00:03:19.910 align:start position:0% transfer function which is only part which<00:03:16.890> requires<00:03:17.489> consensus<00:03:18.329> and<00:03:18.600> so<00:03:19.560> I<00:03:19.620> have 00:03:19.910 --> 00:03:19.920 align:start position:0% which requires consensus and so I have 00:03:19.920 --> 00:03:23.180 align:start position:0% which requires consensus and so I have marked<00:03:20.640> it<00:03:20.850> with<00:03:21.060> consensus<00:03:21.750> and<00:03:22.170> and<00:03:22.980> if<00:03:23.130> you 00:03:23.180 --> 00:03:23.190 align:start position:0% marked it with consensus and and if you 00:03:23.190 --> 00:03:26.599 align:start position:0% marked it with consensus and and if you consider<00:03:23.370> this<00:03:23.790> screen<00:03:24.480> then<00:03:25.320> if<00:03:25.650> you<00:03:26.459> have 00:03:26.599 --> 00:03:26.609 align:start position:0% consider this screen then if you have 00:03:26.609 --> 00:03:29.000 align:start position:0% consider this screen then if you have this<00:03:26.730> in<00:03:26.880> an<00:03:27.000> ID<00:03:27.150> or<00:03:27.450> whatever<00:03:27.570> the<00:03:28.290> deployment 00:03:29.000 --> 00:03:29.010 align:start position:0% this in an ID or whatever the deployment 00:03:29.010 --> 00:03:30.860 align:start position:0% this in an ID or whatever the deployment time<00:03:29.280> or<00:03:29.549> the<00:03:29.640> compiler<00:03:30.000> and<00:03:30.209> everything<00:03:30.630> will 00:03:30.860 --> 00:03:30.870 align:start position:0% time or the compiler and everything will 00:03:30.870 --> 00:03:32.660 align:start position:0% time or the compiler and everything will know<00:03:31.170> that<00:03:31.200> this<00:03:31.680> is<00:03:31.739> only<00:03:32.010> part<00:03:32.459> which 00:03:32.660 --> 00:03:32.670 align:start position:0% know that this is only part which 00:03:32.670 --> 00:03:34.580 align:start position:0% know that this is only part which requires<00:03:33.420> consensus<00:03:33.989> that's<00:03:34.109> only<00:03:34.320> part 00:03:34.580 --> 00:03:34.590 align:start position:0% requires consensus that's only part 00:03:34.590 --> 00:03:35.750 align:start position:0% requires consensus that's only part which<00:03:34.709> is<00:03:34.739> gonna<00:03:34.920> get<00:03:35.040> to<00:03:35.160> the<00:03:35.250> blockchain 00:03:35.750 --> 00:03:35.760 align:start position:0% which is gonna get to the blockchain 00:03:35.760 --> 00:03:38.210 align:start position:0% which is gonna get to the blockchain and<00:03:35.970> everything<00:03:36.660> else<00:03:36.810> stays<00:03:37.049> outside<00:03:37.530> the 00:03:38.210 --> 00:03:38.220 align:start position:0% and everything else stays outside the 00:03:38.220 --> 00:03:40.580 align:start position:0% and everything else stays outside the benefits<00:03:38.609> we<00:03:38.760> have<00:03:38.970> here<00:03:39.329> is<00:03:39.480> you<00:03:40.170> see<00:03:40.200> all<00:03:40.380> the 00:03:40.580 --> 00:03:40.590 align:start position:0% benefits we have here is you see all the 00:03:40.590 --> 00:03:42.890 align:start position:0% benefits we have here is you see all the data<00:03:40.799> and<00:03:41.010> everything<00:03:41.459> in<00:03:41.790> in<00:03:42.120> one<00:03:42.329> block<00:03:42.570> you 00:03:42.890 --> 00:03:42.900 align:start position:0% data and everything in in one block you 00:03:42.900 --> 00:03:44.509 align:start position:0% data and everything in in one block you don't<00:03:43.230> have<00:03:43.410> to<00:03:43.530> make<00:03:43.680> these<00:03:43.859> decisions<00:03:44.190> you 00:03:44.509 --> 00:03:44.519 align:start position:0% don't have to make these decisions you 00:03:44.519 --> 00:03:45.979 align:start position:0% don't have to make these decisions you know<00:03:44.609> where<00:03:44.850> where<00:03:45.150> it's<00:03:45.269> like<00:03:45.420> the<00:03:45.510> consensus 00:03:45.979 --> 00:03:45.989 align:start position:0% know where where it's like the consensus 00:03:45.989 --> 00:03:47.479 align:start position:0% know where where it's like the consensus level<00:03:46.260> data<00:03:46.380> where<00:03:46.620> it's<00:03:46.709> like<00:03:46.829> the<00:03:47.160> front<00:03:47.340> end 00:03:47.479 --> 00:03:47.489 align:start position:0% level data where it's like the front end 00:03:47.489 --> 00:03:49.580 align:start position:0% level data where it's like the front end data<00:03:47.700> and<00:03:48.090> hopefully<00:03:48.840> it<00:03:49.170> will<00:03:49.230> be<00:03:49.380> a<00:03:49.410> much 00:03:49.580 --> 00:03:49.590 align:start position:0% data and hopefully it will be a much 00:03:49.590 --> 00:03:51.500 align:start position:0% data and hopefully it will be a much easier<00:03:49.859> decision<00:03:50.190> to<00:03:50.670> see<00:03:50.880> you<00:03:51.299> know<00:03:51.390> what 00:03:51.500 --> 00:03:51.510 align:start position:0% easier decision to see you know what 00:03:51.510 --> 00:03:53.270 align:start position:0% easier decision to see you know what belongs<00:03:51.810> where<00:03:52.109> because<00:03:52.680> right<00:03:52.859> now<00:03:53.040> we<00:03:53.100> do<00:03:53.250> a 00:03:53.270 --> 00:03:53.280 align:start position:0% belongs where because right now we do a 00:03:53.280 --> 00:03:56.479 align:start position:0% belongs where because right now we do a lot<00:03:53.459> of<00:03:53.489> duplication<00:03:55.160> and<00:03:56.160> I<00:03:56.220> think 00:03:56.479 --> 00:03:56.489 align:start position:0% lot of duplication and I think 00:03:56.489 --> 00:03:59.539 align:start position:0% lot of duplication and I think webassembly<00:03:56.910> can<00:03:57.840> help<00:03:58.109> a<00:03:58.230> lot<00:03:58.350> in<00:03:58.590> this<00:03:58.799> there 00:03:59.539 --> 00:03:59.549 align:start position:0% webassembly can help a lot in this there 00:03:59.549 --> 00:04:00.740 align:start position:0% webassembly can help a lot in this there already<00:03:59.670> is<00:03:59.819> a<00:03:59.880> couple<00:04:00.120> of<00:04:00.180> tools<00:04:00.329> which<00:04:00.569> try 00:04:00.740 --> 00:04:00.750 align:start position:0% already is a couple of tools which try 00:04:00.750 --> 00:04:03.050 align:start position:0% already is a couple of tools which try to<00:04:00.780> achieve<00:04:00.989> the<00:04:01.230> same<00:04:01.410> thing<00:04:01.760> victory<00:04:02.760> I<00:04:02.880> made 00:04:03.050 --> 00:04:03.060 align:start position:0% to achieve the same thing victory I made 00:04:03.060 --> 00:04:05.930 align:start position:0% to achieve the same thing victory I made a<00:04:03.090> presentation<00:04:03.510> about<00:04:04.760> Luna 00:04:05.930 --> 00:04:05.940 align:start position:0% a presentation about Luna 00:04:05.940 --> 00:04:07.789 align:start position:0% a presentation about Luna I<00:04:06.060> think<00:04:06.329> Luna<00:04:06.540> is<00:04:06.600> the<00:04:06.690> name<00:04:06.840> which<00:04:07.560> has 00:04:07.789 --> 00:04:07.799 align:start position:0% I think Luna is the name which has 00:04:07.799 --> 00:04:11.180 align:start position:0% I think Luna is the name which has similar<00:04:08.100> goals<00:04:08.359> but<00:04:09.359> we<00:04:09.510> try<00:04:09.720> to<00:04:09.780> to<00:04:10.440> get<00:04:11.130> to 00:04:11.180 --> 00:04:11.190 align:start position:0% similar goals but we try to to get to 00:04:11.190 --> 00:04:13.490 align:start position:0% similar goals but we try to to get to there<00:04:11.459> from<00:04:11.700> a<00:04:11.819> different<00:04:12.000> angle<00:04:12.299> now<00:04:13.170> this<00:04:13.380> is 00:04:13.490 --> 00:04:13.500 align:start position:0% there from a different angle now this is 00:04:13.500 --> 00:04:15.620 align:start position:0% there from a different angle now this is just<00:04:13.650> like<00:04:13.859> a<00:04:13.889> high-level<00:04:14.430> you<00:04:15.239> know<00:04:15.359> future 00:04:15.620 --> 00:04:15.630 align:start position:0% just like a high-level you know future 00:04:15.630 --> 00:04:18.080 align:start position:0% just like a high-level you know future vision<00:04:16.160> but<00:04:17.160> what<00:04:17.310> we<00:04:17.430> are<00:04:17.489> focusing<00:04:17.910> here 00:04:18.080 --> 00:04:18.090 align:start position:0% vision but what we are focusing here 00:04:18.090 --> 00:04:20.750 align:start position:0% vision but what we are focusing here today<00:04:18.359> on<00:04:18.600> is<00:04:18.810> only<00:04:19.109> the<00:04:19.680> consensus<00:04:20.280> layer<00:04:20.459> and 00:04:20.750 --> 00:04:20.760 align:start position:0% today on is only the consensus layer and 00:04:20.760 --> 00:04:23.270 align:start position:0% today on is only the consensus layer and how<00:04:21.450> do<00:04:21.510> we<00:04:21.660> get<00:04:21.900> webassembly<00:04:22.380> into<00:04:23.159> that 00:04:23.270 --> 00:04:23.280 align:start position:0% how do we get webassembly into that 00:04:23.280 --> 00:04:26.360 align:start position:0% how do we get webassembly into that consensus<00:04:23.789> layer<00:04:24.770> so<00:04:25.770> what<00:04:25.890> it<00:04:25.979> was<00:04:26.159> and 00:04:26.360 --> 00:04:26.370 align:start position:0% consensus layer so what it was and 00:04:26.370 --> 00:04:27.680 align:start position:0% consensus layer so what it was and wasn't<00:04:26.550> is 00:04:27.680 --> 00:04:27.690 align:start position:0% wasn't is 00:04:27.690 --> 00:04:29.960 align:start position:0% wasn't is executable<00:04:28.560> binary<00:04:28.710> format<00:04:29.190> design<00:04:29.580> for<00:04:29.880> the 00:04:29.960 --> 00:04:29.970 align:start position:0% executable binary format design for the 00:04:29.970 --> 00:04:32.510 align:start position:0% executable binary format design for the web<00:04:30.620> it<00:04:31.620> is<00:04:31.830> designed<00:04:32.160> to<00:04:32.250> be<00:04:32.370> highly 00:04:32.510 --> 00:04:32.520 align:start position:0% web it is designed to be highly 00:04:32.520 --> 00:04:35.360 align:start position:0% web it is designed to be highly performant<00:04:33.120> it<00:04:33.870> really<00:04:34.320> models<00:04:34.650> a<00:04:34.890> regular 00:04:35.360 --> 00:04:35.370 align:start position:0% performant it really models a regular 00:04:35.370 --> 00:04:39.200 align:start position:0% performant it really models a regular computer<00:04:35.840> and<00:04:36.840> basically<00:04:37.710> if<00:04:38.310> you<00:04:38.970> take<00:04:39.150> a 00:04:39.200 --> 00:04:39.210 align:start position:0% computer and basically if you take a 00:04:39.210 --> 00:04:40.820 align:start position:0% computer and basically if you take a step<00:04:39.480> back<00:04:39.690> how<00:04:40.170> webassembly 00:04:40.820 --> 00:04:40.830 align:start position:0% step back how webassembly 00:04:40.830 --> 00:04:44.090 align:start position:0% step back how webassembly came<00:04:41.280> into<00:04:41.460> existence<00:04:42.620> it<00:04:43.620> starts<00:04:43.920> with<00:04:44.040> the 00:04:44.090 --> 00:04:44.100 align:start position:0% came into existence it starts with the 00:04:44.100 --> 00:04:47.450 align:start position:0% came into existence it starts with the web<00:04:44.220> itself<00:04:44.490> so<00:04:45.420> we<00:04:45.540> had<00:04:45.750> JavaScript<00:04:46.590> first<00:04:47.130> to 00:04:47.450 --> 00:04:47.460 align:start position:0% web itself so we had JavaScript first to 00:04:47.460 --> 00:04:49.310 align:start position:0% web itself so we had JavaScript first to to<00:04:47.670> create<00:04:48.090> you<00:04:48.630> know<00:04:48.750> any<00:04:48.900> kind<00:04:49.080> of<00:04:49.140> code 00:04:49.310 --> 00:04:49.320 align:start position:0% to create you know any kind of code 00:04:49.320 --> 00:04:52.190 align:start position:0% to create you know any kind of code which<00:04:50.220> evolved<00:04:50.580> into<00:04:50.610> web<00:04:50.910> 2.0<00:04:51.360> with<00:04:51.600> a<00:04:51.630> way 00:04:52.190 --> 00:04:52.200 align:start position:0% which evolved into web 2.0 with a way 00:04:52.200 --> 00:04:54.860 align:start position:0% which evolved into web 2.0 with a way more<00:04:52.560> JavaScript<00:04:53.150> and<00:04:54.150> the<00:04:54.240> people<00:04:54.540> started 00:04:54.860 --> 00:04:54.870 align:start position:0% more JavaScript and the people started 00:04:54.870 --> 00:04:56.690 align:start position:0% more JavaScript and the people started to<00:04:54.990> use<00:04:55.020> other<00:04:55.380> tools<00:04:55.440> like<00:04:55.920> in<00:04:56.070> scripting<00:04:56.460> to 00:04:56.690 --> 00:04:56.700 align:start position:0% to use other tools like in scripting to 00:04:56.700 --> 00:04:59.090 align:start position:0% to use other tools like in scripting to compile<00:04:57.120> non<00:04:57.720> javascript<00:04:58.320> code<00:04:58.530> into 00:04:59.090 --> 00:04:59.100 align:start position:0% compile non javascript code into 00:04:59.100 --> 00:05:01.490 align:start position:0% compile non javascript code into JavaScript<00:04:59.840> and<00:05:00.840> that<00:05:00.960> was<00:05:01.050> quite<00:05:01.230> slow 00:05:01.490 --> 00:05:01.500 align:start position:0% JavaScript and that was quite slow 00:05:01.500 --> 00:05:02.900 align:start position:0% JavaScript and that was quite slow because<00:05:01.860> JavaScript<00:05:02.370> wasn't<00:05:02.580> designed<00:05:02.790> for 00:05:02.900 --> 00:05:02.910 align:start position:0% because JavaScript wasn't designed for 00:05:02.910 --> 00:05:05.210 align:start position:0% because JavaScript wasn't designed for this<00:05:03.090> so<00:05:03.900> there<00:05:04.020> was<00:05:04.140> this<00:05:04.230> other<00:05:04.380> step<00:05:04.770> called 00:05:05.210 --> 00:05:05.220 align:start position:0% this so there was this other step called 00:05:05.220 --> 00:05:09.830 align:start position:0% this so there was this other step called a<00:05:05.340> SMGs<00:05:06.080> which<00:05:07.280> the<00:05:08.280> the<00:05:08.670> javascript<00:05:09.480> engines 00:05:09.830 --> 00:05:09.840 align:start position:0% a SMGs which the the javascript engines 00:05:09.840 --> 00:05:11.810 align:start position:0% a SMGs which the the javascript engines could<00:05:10.050> detect<00:05:10.290> certain<00:05:10.620> patterns<00:05:11.220> which<00:05:11.700> are 00:05:11.810 --> 00:05:11.820 align:start position:0% could detect certain patterns which are 00:05:11.820 --> 00:05:15.560 align:start position:0% could detect certain patterns which are a<00:05:11.880> SMGs<00:05:12.420> patterns<00:05:12.810> and<00:05:13.020> optimize<00:05:13.440> those<00:05:14.570> now 00:05:15.560 --> 00:05:15.570 align:start position:0% a SMGs patterns and optimize those now 00:05:15.570 --> 00:05:17.360 align:start position:0% a SMGs patterns and optimize those now we<00:05:15.630> can<00:05:16.020> optimize<00:05:16.170> this<00:05:16.500> even<00:05:16.740> more<00:05:16.950> by 00:05:17.360 --> 00:05:17.370 align:start position:0% we can optimize this even more by 00:05:17.370 --> 00:05:18.740 align:start position:0% we can optimize this even more by introducing<00:05:17.880> webassembly<00:05:18.210> we<00:05:18.480> don't<00:05:18.660> need 00:05:18.740 --> 00:05:18.750 align:start position:0% introducing webassembly we don't need 00:05:18.750 --> 00:05:21.260 align:start position:0% introducing webassembly we don't need these<00:05:18.900> special<00:05:19.260> patterns<00:05:19.620> so<00:05:20.160> that's<00:05:20.640> that's 00:05:21.260 --> 00:05:21.270 align:start position:0% these special patterns so that's that's 00:05:21.270 --> 00:05:23.180 align:start position:0% these special patterns so that's that's where<00:05:21.540> this<00:05:22.050> reason<00:05:22.380> webassembly<00:05:22.710> came<00:05:23.040> into 00:05:23.180 --> 00:05:23.190 align:start position:0% where this reason webassembly came into 00:05:23.190 --> 00:05:28.760 align:start position:0% where this reason webassembly came into existence<00:05:23.610> to<00:05:24.440> improve<00:05:25.440> the<00:05:25.650> web<00:05:27.260> as<00:05:28.260> a<00:05:28.320> result 00:05:28.760 --> 00:05:28.770 align:start position:0% existence to improve the web as a result 00:05:28.770 --> 00:05:31.370 align:start position:0% existence to improve the web as a result web<00:05:28.950> assembly<00:05:29.250> itself<00:05:29.520> is<00:05:30.020> designed<00:05:31.020> to 00:05:31.370 --> 00:05:31.380 align:start position:0% web assembly itself is designed to 00:05:31.380 --> 00:05:34.070 align:start position:0% web assembly itself is designed to support<00:05:31.680> a<00:05:31.740> lot<00:05:31.860> of<00:05:31.980> languages<00:05:32.430> it<00:05:33.270> is<00:05:33.450> really 00:05:34.070 --> 00:05:34.080 align:start position:0% support a lot of languages it is really 00:05:34.080 --> 00:05:36.110 align:start position:0% support a lot of languages it is really low<00:05:34.230> level<00:05:34.500> and<00:05:34.740> a<00:05:35.100> lot<00:05:35.610> of<00:05:35.670> languages 00:05:36.110 --> 00:05:36.120 align:start position:0% low level and a lot of languages 00:05:36.120 --> 00:05:38.690 align:start position:0% low level and a lot of languages supporting<00:05:36.570> it<00:05:36.860> there's<00:05:37.860> this<00:05:37.980> awesome<00:05:38.190> was 00:05:38.690 --> 00:05:38.700 align:start position:0% supporting it there's this awesome was 00:05:38.700 --> 00:05:40.820 align:start position:0% supporting it there's this awesome was in<00:05:38.880> lengths<00:05:39.180> repo<00:05:39.510> which<00:05:39.690> lists<00:05:40.080> I<00:05:40.290> think 00:05:40.820 --> 00:05:40.830 align:start position:0% in lengths repo which lists I think 00:05:40.830 --> 00:05:42.830 align:start position:0% in lengths repo which lists I think pretty<00:05:41.010> much<00:05:41.160> all<00:05:41.280> of<00:05:41.310> them<00:05:41.580> they're<00:05:42.300> like<00:05:42.450> 28 00:05:42.830 --> 00:05:42.840 align:start position:0% pretty much all of them they're like 28 00:05:42.840 --> 00:05:45.770 align:start position:0% pretty much all of them they're like 28 today<00:05:43.110> but<00:05:43.440> with<00:05:43.620> various<00:05:44.450> you<00:05:45.450> know<00:05:45.540> various 00:05:45.770 --> 00:05:45.780 align:start position:0% today but with various you know various 00:05:45.780 --> 00:05:48.560 align:start position:0% today but with various you know various level<00:05:46.020> of<00:05:46.110> integration<00:05:46.730> C<00:05:47.730> and<00:05:47.940> rust<00:05:48.150> would<00:05:48.419> be 00:05:48.560 --> 00:05:48.570 align:start position:0% level of integration C and rust would be 00:05:48.570 --> 00:05:51.170 align:start position:0% level of integration C and rust would be the<00:05:48.720> best<00:05:48.960> ones<00:05:49.200> today<00:05:49.490> but<00:05:50.490> go<00:05:50.669> Haskell<00:05:51.060> it's 00:05:51.170 --> 00:05:51.180 align:start position:0% the best ones today but go Haskell it's 00:05:51.180 --> 00:05:55.000 align:start position:0% the best ones today but go Haskell it's this<00:05:51.270> assembly<00:05:51.840> script<00:05:52.080> are<00:05:52.230> also<00:05:52.680> usable 00:05:55.000 --> 00:05:55.010 align:start position:0% 00:05:55.010 --> 00:05:57.530 align:start position:0% because<00:05:56.010> it<00:05:56.130> originates<00:05:56.550> from<00:05:56.610> the<00:05:56.850> web<00:05:57.030> it<00:05:57.300> is 00:05:57.530 --> 00:05:57.540 align:start position:0% because it originates from the web it is 00:05:57.540 --> 00:06:00.620 align:start position:0% because it originates from the web it is supported<00:05:58.080> by<00:05:58.110> all<00:05:58.200> major<00:05:58.380> browsers<00:05:59.630> but 00:06:00.620 --> 00:06:00.630 align:start position:0% supported by all major browsers but 00:06:00.630 --> 00:06:02.480 align:start position:0% supported by all major browsers but ourselves<00:06:01.590> we<00:06:01.680> are<00:06:01.710> not<00:06:01.770> focusing<00:06:02.190> on<00:06:02.310> the<00:06:02.370> web 00:06:02.480 --> 00:06:02.490 align:start position:0% ourselves we are not focusing on the web 00:06:02.490 --> 00:06:04.550 align:start position:0% ourselves we are not focusing on the web right<00:06:02.669> now<00:06:02.730> we<00:06:03.450> are<00:06:03.510> only<00:06:03.630> focusing<00:06:03.990> about<00:06:04.440> the 00:06:04.550 --> 00:06:04.560 align:start position:0% right now we are only focusing about the 00:06:04.560 --> 00:06:06.920 align:start position:0% right now we are only focusing about the consensus<00:06:05.160> layer<00:06:05.340> and<00:06:05.669> in<00:06:06.210> a<00:06:06.270> consensus<00:06:06.750> layer 00:06:06.920 --> 00:06:06.930 align:start position:0% consensus layer and in a consensus layer 00:06:06.930 --> 00:06:08.360 align:start position:0% consensus layer and in a consensus layer we<00:06:07.200> don't<00:06:07.380> want<00:06:07.500> to<00:06:07.560> use<00:06:07.680> any<00:06:07.980> of<00:06:08.070> the<00:06:08.220> web 00:06:08.360 --> 00:06:08.370 align:start position:0% we don't want to use any of the web 00:06:08.370 --> 00:06:12.020 align:start position:0% we don't want to use any of the web engines<00:06:08.850> and<00:06:09.440> we<00:06:10.440> are<00:06:10.500> lucky<00:06:10.800> because<00:06:10.919> a<00:06:11.520> lot 00:06:12.020 --> 00:06:12.030 align:start position:0% engines and we are lucky because a lot 00:06:12.030 --> 00:06:13.850 align:start position:0% engines and we are lucky because a lot of<00:06:12.060> other<00:06:12.300> awesome<00:06:12.960> implementations<00:06:13.680> we 00:06:13.850 --> 00:06:13.860 align:start position:0% of other awesome implementations we 00:06:13.860 --> 00:06:15.680 align:start position:0% of other awesome implementations we don't<00:06:14.040> have<00:06:14.160> to<00:06:14.310> use<00:06:14.490> their<00:06:15.000> browsers<00:06:15.390> to<00:06:15.540> run 00:06:15.680 --> 00:06:15.690 align:start position:0% don't have to use their browsers to run 00:06:15.690 --> 00:06:17.450 align:start position:0% don't have to use their browsers to run Watson<00:06:16.110> there<00:06:17.100> are<00:06:17.190> a<00:06:17.220> couple<00:06:17.310> of 00:06:17.450 --> 00:06:17.460 align:start position:0% Watson there are a couple of 00:06:17.460 --> 00:06:19.280 align:start position:0% Watson there are a couple of implementations<00:06:18.030> in<00:06:18.240> C<00:06:18.510> there's<00:06:19.140> an 00:06:19.280 --> 00:06:19.290 align:start position:0% implementations in C there's an 00:06:19.290 --> 00:06:21.350 align:start position:0% implementations in C there's an implementation<00:06:19.680> in<00:06:20.100> rust<00:06:20.280> by<00:06:20.550> parity<00:06:21.000> there's 00:06:21.350 --> 00:06:21.360 align:start position:0% implementation in rust by parity there's 00:06:21.360 --> 00:06:23.750 align:start position:0% implementation in rust by parity there's implementation<00:06:21.990> and<00:06:22.110> go<00:06:22.340> so<00:06:23.340> we<00:06:23.460> don't<00:06:23.610> have 00:06:23.750 --> 00:06:23.760 align:start position:0% implementation and go so we don't have 00:06:23.760 --> 00:06:25.850 align:start position:0% implementation and go so we don't have to<00:06:23.880> rely<00:06:24.030> on<00:06:24.419> all<00:06:24.720> this<00:06:24.870> browser<00:06:25.470> specific 00:06:25.850 --> 00:06:25.860 align:start position:0% to rely on all this browser specific 00:06:25.860 --> 00:06:30.260 align:start position:0% to rely on all this browser specific toolkit<00:06:26.550> so<00:06:27.919> wait<00:06:28.919> it<00:06:29.160> it<00:06:29.430> kind<00:06:29.760> of<00:06:29.880> sounds 00:06:30.260 --> 00:06:30.270 align:start position:0% toolkit so wait it it kind of sounds 00:06:30.270 --> 00:06:33.560 align:start position:0% toolkit so wait it it kind of sounds like<00:06:30.300> Java<00:06:30.720> and<00:06:30.870> JVM<00:06:31.410> right<00:06:32.000> it<00:06:33.000> is<00:06:33.210> kind<00:06:33.480> of 00:06:33.560 --> 00:06:33.570 align:start position:0% like Java and JVM right it is kind of 00:06:33.570 --> 00:06:35.750 align:start position:0% like Java and JVM right it is kind of but<00:06:33.690> it<00:06:33.810> it<00:06:34.050> isn't<00:06:34.410> fully<00:06:34.590> one<00:06:35.460> main 00:06:35.750 --> 00:06:35.760 align:start position:0% but it it isn't fully one main 00:06:35.760 --> 00:06:37.969 align:start position:0% but it it isn't fully one main difference<00:06:36.120> is<00:06:36.479> Java<00:06:37.080> wasn't<00:06:37.470> designed<00:06:37.770> for 00:06:37.969 --> 00:06:37.979 align:start position:0% difference is Java wasn't designed for 00:06:37.979 --> 00:06:40.980 align:start position:0% difference is Java wasn't designed for the<00:06:38.220> web<00:06:38.370> it<00:06:38.550> was<00:06:38.700> designed<00:06:39.090> before<00:06:39.810> the<00:06:40.140> web 00:06:40.980 --> 00:06:40.990 align:start position:0% the web it was designed before the web 00:06:40.990 --> 00:06:43.170 align:start position:0% the web it was designed before the web and<00:06:41.080> it<00:06:41.830> was<00:06:41.979> tightly<00:06:42.340> coupled<00:06:42.699> with<00:06:43.000> the 00:06:43.170 --> 00:06:43.180 align:start position:0% and it was tightly coupled with the 00:06:43.180 --> 00:06:46.439 align:start position:0% and it was tightly coupled with the language<00:06:43.509> with<00:06:43.990> Java<00:06:44.229> itself<00:06:44.970> so<00:06:45.970> as<00:06:46.060> a<00:06:46.090> result 00:06:46.439 --> 00:06:46.449 align:start position:0% language with Java itself so as a result 00:06:46.449 --> 00:06:48.749 align:start position:0% language with Java itself so as a result it<00:06:46.569> really<00:06:46.600> had<00:06:47.020> high<00:06:47.319> level<00:06:47.650> features<00:06:48.039> and 00:06:48.749 --> 00:06:48.759 align:start position:0% it really had high level features and 00:06:48.759 --> 00:06:49.980 align:start position:0% it really had high level features and they<00:06:49.000> don't<00:06:49.180> have<00:06:49.300> like<00:06:49.389> a<00:06:49.449> lot<00:06:49.569> of<00:06:49.750> low<00:06:49.960> level 00:06:49.980 --> 00:06:49.990 align:start position:0% they don't have like a lot of low level 00:06:49.990 --> 00:06:51.839 align:start position:0% they don't have like a lot of low level abstraction<00:06:50.380> it<00:06:50.979> has<00:06:51.190> these<00:06:51.340> high<00:06:51.580> level 00:06:51.839 --> 00:06:51.849 align:start position:0% abstraction it has these high level 00:06:51.849 --> 00:06:54.420 align:start position:0% abstraction it has these high level features<00:06:52.349> which<00:06:53.349> tightly<00:06:54.009> coupled<00:06:54.190> it<00:06:54.400> with 00:06:54.420 --> 00:06:54.430 align:start position:0% features which tightly coupled it with 00:06:54.430 --> 00:06:58.469 align:start position:0% features which tightly coupled it with Java<00:06:55.150> is<00:06:55.300> a<00:06:55.419> language<00:06:56.069> now<00:06:57.069> we<00:06:57.130> don't<00:06:57.370> have<00:06:57.580> we 00:06:58.469 --> 00:06:58.479 align:start position:0% Java is a language now we don't have we 00:06:58.479 --> 00:07:00.749 align:start position:0% Java is a language now we don't have we don't<00:06:58.660> have<00:06:58.780> any<00:06:58.930> of<00:06:59.080> these<00:06:59.199> in<00:06:59.380> wasum<00:06:59.800> but 00:07:00.749 --> 00:07:00.759 align:start position:0% don't have any of these in wasum but 00:07:00.759 --> 00:07:03.960 align:start position:0% don't have any of these in wasum but wasum<00:07:01.090> is<00:07:01.210> designed<00:07:01.690> to<00:07:02.020> be<00:07:02.169> extensible<00:07:02.970> so 00:07:03.960 --> 00:07:03.970 align:start position:0% wasum is designed to be extensible so 00:07:03.970 --> 00:07:05.909 align:start position:0% wasum is designed to be extensible so awesome<00:07:04.360> can<00:07:04.509> actually<00:07:04.810> turn<00:07:05.020> into<00:07:05.319> what<00:07:05.830> the 00:07:05.909 --> 00:07:05.919 align:start position:0% awesome can actually turn into what the 00:07:05.919 --> 00:07:07.969 align:start position:0% awesome can actually turn into what the JVM<00:07:06.340> is<00:07:06.430> doing<00:07:06.699> so<00:07:07.360> one<00:07:07.539> quick<00:07:07.840> example 00:07:07.969 --> 00:07:07.979 align:start position:0% JVM is doing so one quick example 00:07:07.979 --> 00:07:10.339 align:start position:0% JVM is doing so one quick example example<00:07:08.979> I<00:07:09.009> want<00:07:09.160> to<00:07:09.220> give<00:07:09.340> you<00:07:09.490> here<00:07:09.819> is 00:07:10.339 --> 00:07:10.349 align:start position:0% example I want to give you here is 00:07:10.349 --> 00:07:14.420 align:start position:0% example I want to give you here is garbage<00:07:11.349> collection<00:07:12.720> today<00:07:13.720> there's<00:07:13.990> like<00:07:14.169> no 00:07:14.420 --> 00:07:14.430 align:start position:0% garbage collection today there's like no 00:07:14.430 --> 00:07:16.770 align:start position:0% garbage collection today there's like no wasum<00:07:15.430> level<00:07:15.729> support<00:07:15.910> for<00:07:16.300> garbage 00:07:16.770 --> 00:07:16.780 align:start position:0% wasum level support for garbage 00:07:16.780 --> 00:07:18.540 align:start position:0% wasum level support for garbage collection<00:07:17.229> and<00:07:17.410> that<00:07:17.500> means<00:07:17.979> if<00:07:18.130> you<00:07:18.220> compile 00:07:18.540 --> 00:07:18.550 align:start position:0% collection and that means if you compile 00:07:18.550 --> 00:07:19.860 align:start position:0% collection and that means if you compile a<00:07:18.580> language<00:07:19.000> which<00:07:19.180> requires<00:07:19.539> garbage 00:07:19.860 --> 00:07:19.870 align:start position:0% a language which requires garbage 00:07:19.870 --> 00:07:21.570 align:start position:0% a language which requires garbage collection<00:07:20.259> all<00:07:20.620> this<00:07:20.830> garbage<00:07:21.070> collection 00:07:21.570 --> 00:07:21.580 align:start position:0% collection all this garbage collection 00:07:21.580 --> 00:07:24.029 align:start position:0% collection all this garbage collection helper<00:07:22.030> code<00:07:22.449> going<00:07:22.960> to<00:07:23.020> be<00:07:23.110> in<00:07:23.199> the<00:07:23.320> output<00:07:23.650> as 00:07:24.029 --> 00:07:24.039 align:start position:0% helper code going to be in the output as 00:07:24.039 --> 00:07:25.680 align:start position:0% helper code going to be in the output as a<00:07:24.099> result<00:07:24.550> it<00:07:24.669> will<00:07:24.820> be<00:07:24.970> big<00:07:25.180> and<00:07:25.360> it<00:07:25.449> will<00:07:25.599> be 00:07:25.680 --> 00:07:25.690 align:start position:0% a result it will be big and it will be 00:07:25.690 --> 00:07:28.110 align:start position:0% a result it will be big and it will be slow<00:07:25.949> but<00:07:26.949> sense<00:07:27.220> was<00:07:27.490> amazed<00:07:27.669> designed<00:07:27.940> to<00:07:28.030> be 00:07:28.110 --> 00:07:28.120 align:start position:0% slow but sense was amazed designed to be 00:07:28.120 --> 00:07:30.950 align:start position:0% slow but sense was amazed designed to be extensible<00:07:28.599> and<00:07:28.810> anybody<00:07:29.680> can<00:07:30.190> propose 00:07:30.950 --> 00:07:30.960 align:start position:0% extensible and anybody can propose 00:07:30.960 --> 00:07:33.570 align:start position:0% extensible and anybody can propose extensions<00:07:31.960> to<00:07:32.110> it<00:07:32.229> their<00:07:32.740> proposals<00:07:33.220> to<00:07:33.400> add 00:07:33.570 --> 00:07:33.580 align:start position:0% extensions to it their proposals to add 00:07:33.580 --> 00:07:35.790 align:start position:0% extensions to it their proposals to add like<00:07:33.820> you<00:07:34.599> know<00:07:34.690> what<00:07:34.900> was<00:07:35.199> in<00:07:35.380> level<00:07:35.650> support 00:07:35.790 --> 00:07:35.800 align:start position:0% like you know what was in level support 00:07:35.800 --> 00:07:38.189 align:start position:0% like you know what was in level support for<00:07:36.610> garbage<00:07:36.880> collection<00:07:36.970> so<00:07:37.840> maybe<00:07:38.020> that 00:07:38.189 --> 00:07:38.199 align:start position:0% for garbage collection so maybe that 00:07:38.199 --> 00:07:40.499 align:start position:0% for garbage collection so maybe that will<00:07:38.289> happen<00:07:38.500> and<00:07:39.340> maybe<00:07:39.580> we<00:07:39.909> get<00:07:40.060> closer<00:07:40.360> to 00:07:40.499 --> 00:07:40.509 align:start position:0% will happen and maybe we get closer to 00:07:40.509 --> 00:07:43.710 align:start position:0% will happen and maybe we get closer to all<00:07:40.930> these<00:07:41.080> features<00:07:41.500> Java<00:07:42.069> has<00:07:42.340> but<00:07:43.210> we<00:07:43.509> at 00:07:43.710 --> 00:07:43.720 align:start position:0% all these features Java has but we at 00:07:43.720 --> 00:07:46.080 align:start position:0% all these features Java has but we at the<00:07:43.870> consensus<00:07:44.380> layer<00:07:44.590> are<00:07:45.099> not<00:07:45.430> forced<00:07:45.820> to 00:07:46.080 --> 00:07:46.090 align:start position:0% the consensus layer are not forced to 00:07:46.090 --> 00:07:48.749 align:start position:0% the consensus layer are not forced to take<00:07:46.539> these<00:07:46.690> new<00:07:46.960> features<00:07:47.349> we<00:07:47.740> can<00:07:47.770> stay<00:07:48.159> with 00:07:48.749 --> 00:07:48.759 align:start position:0% take these new features we can stay with 00:07:48.759 --> 00:07:50.100 align:start position:0% take these new features we can stay with the<00:07:48.849> core<00:07:49.030> level<00:07:49.270> of<00:07:49.360> functionality<00:07:49.720> we<00:07:50.020> have 00:07:50.100 --> 00:07:50.110 align:start position:0% the core level of functionality we have 00:07:50.110 --> 00:07:51.680 align:start position:0% the core level of functionality we have today 00:07:51.680 --> 00:07:51.690 align:start position:0% today 00:07:51.690 --> 00:07:54.180 align:start position:0% today okay<00:07:52.690> let's<00:07:53.110> talk<00:07:53.320> it<00:07:53.500> Heine<00:07:53.740> bit<00:07:53.949> about<00:07:54.099> the 00:07:54.180 --> 00:07:54.190 align:start position:0% okay let's talk it Heine bit about the 00:07:54.190 --> 00:07:59.600 align:start position:0% okay let's talk it Heine bit about the EVM<00:07:54.550> itself<00:07:55.830> EVM<00:07:56.830> had<00:07:57.610> different<00:07:57.969> design 00:07:59.600 --> 00:07:59.610 align:start position:0% EVM itself EVM had different design 00:07:59.610 --> 00:08:02.790 align:start position:0% EVM itself EVM had different design rules<00:08:00.610> and<00:08:00.880> different<00:08:01.599> goals<00:08:01.810> when<00:08:02.590> it<00:08:02.680> was 00:08:02.790 --> 00:08:02.800 align:start position:0% rules and different goals when it was 00:08:02.800 --> 00:08:05.339 align:start position:0% rules and different goals when it was designed<00:08:03.240> it<00:08:04.240> is<00:08:04.570> really<00:08:04.840> focusing<00:08:05.199> on 00:08:05.339 --> 00:08:05.349 align:start position:0% designed it is really focusing on 00:08:05.349 --> 00:08:07.890 align:start position:0% designed it is really focusing on cryptography<00:08:06.159> and<00:08:06.370> it<00:08:07.180> doesn't<00:08:07.509> really<00:08:07.659> model 00:08:07.890 --> 00:08:07.900 align:start position:0% cryptography and it doesn't really model 00:08:07.900 --> 00:08:11.730 align:start position:0% cryptography and it doesn't really model a<00:08:08.020> regular<00:08:08.409> computer<00:08:08.889> I<00:08:09.210> believe<00:08:10.440> EVM<00:08:11.440> really 00:08:11.730 --> 00:08:11.740 align:start position:0% a regular computer I believe EVM really 00:08:11.740 --> 00:08:14.459 align:start position:0% a regular computer I believe EVM really has<00:08:11.860> its<00:08:12.039> origins<00:08:12.460> in<00:08:12.610> Bitcoin<00:08:13.000> script<00:08:13.469> which 00:08:14.459 --> 00:08:14.469 align:start position:0% has its origins in Bitcoin script which 00:08:14.469 --> 00:08:17.700 align:start position:0% has its origins in Bitcoin script which is<00:08:14.770> only<00:08:15.190> focused<00:08:15.699> on<00:08:15.880> cryptography<00:08:16.750> and<00:08:16.960> you 00:08:17.700 --> 00:08:17.710 align:start position:0% is only focused on cryptography and you 00:08:17.710 --> 00:08:21.350 align:start position:0% is only focused on cryptography and you know<00:08:17.800> public<00:08:18.039> keys<00:08:18.370> hashing<00:08:19.210> all<00:08:19.659> of<00:08:19.960> that<00:08:20.169> is 00:08:21.350 --> 00:08:21.360 align:start position:0% know public keys hashing all of that is 00:08:21.360 --> 00:08:24.810 align:start position:0% know public keys hashing all of that is so<00:08:22.380> and<00:08:23.380> we<00:08:23.710> don't<00:08:23.889> really<00:08:24.009> need<00:08:24.190> a<00:08:24.520> lot<00:08:24.580> of 00:08:24.810 --> 00:08:24.820 align:start position:0% so and we don't really need a lot of 00:08:24.820 --> 00:08:28.529 align:start position:0% so and we don't really need a lot of these<00:08:24.940> things<00:08:25.169> I<00:08:26.250> think<00:08:27.250> the<00:08:27.340> reason<00:08:27.639> EVM<00:08:28.419> is 00:08:28.529 --> 00:08:28.539 align:start position:0% these things I think the reason EVM is 00:08:28.539 --> 00:08:30.749 align:start position:0% these things I think the reason EVM is kind<00:08:28.780> of<00:08:28.840> slow<00:08:29.080> could<00:08:29.979> be<00:08:30.130> summarized<00:08:30.639> in 00:08:30.749 --> 00:08:30.759 align:start position:0% kind of slow could be summarized in 00:08:30.759 --> 00:08:34.069 align:start position:0% kind of slow could be summarized in these<00:08:30.880> two<00:08:31.060> points<00:08:31.440> it<00:08:32.440> is<00:08:32.500> 256<00:08:33.159> bits<00:08:33.520> focused 00:08:34.069 --> 00:08:34.079 align:start position:0% these two points it is 256 bits focused 00:08:34.079 --> 00:08:36.329 align:start position:0% these two points it is 256 bits focused so<00:08:35.079> that<00:08:35.229> means<00:08:35.409> all<00:08:35.709> the<00:08:35.860> instructions 00:08:36.329 --> 00:08:36.339 align:start position:0% so that means all the instructions 00:08:36.339 --> 00:08:38.850 align:start position:0% so that means all the instructions handle<00:08:36.729> data<00:08:36.909> with<00:08:37.180> 256<00:08:37.839> bit<00:08:38.050> precision<00:08:38.529> we<00:08:38.740> do 00:08:38.850 --> 00:08:38.860 align:start position:0% handle data with 256 bit precision we do 00:08:38.860 --> 00:08:40.860 align:start position:0% handle data with 256 bit precision we do calculations<00:08:39.550> between<00:08:39.820> 56<00:08:40.450> bit<00:08:40.659> precision 00:08:40.860 --> 00:08:40.870 align:start position:0% calculations between 56 bit precision 00:08:40.870 --> 00:08:43.050 align:start position:0% calculations between 56 bit precision and<00:08:41.320> we<00:08:41.800> don't<00:08:41.979> need<00:08:42.130> that<00:08:42.339> in<00:08:42.579> most<00:08:42.820> of<00:08:42.969> the 00:08:43.050 --> 00:08:43.060 align:start position:0% and we don't need that in most of the 00:08:43.060 --> 00:08:45.300 align:start position:0% and we don't need that in most of the time<00:08:43.270> it<00:08:44.200> also<00:08:44.380> makes<00:08:44.649> this<00:08:44.770> high-end 00:08:45.300 --> 00:08:45.310 align:start position:0% time it also makes this high-end 00:08:45.310 --> 00:08:47.699 align:start position:0% time it also makes this high-end low-level<00:08:45.700> features<00:08:46.020> which<00:08:47.020> you<00:08:47.589> know 00:08:47.699 --> 00:08:47.709 align:start position:0% low-level features which you know 00:08:47.709 --> 00:08:50.370 align:start position:0% low-level features which you know probably<00:08:48.190> is<00:08:48.399> not<00:08:48.490> a<00:08:48.550> good<00:08:48.610> idea<00:08:49.230> now<00:08:50.230> I<00:08:50.260> don't 00:08:50.370 --> 00:08:50.380 align:start position:0% probably is not a good idea now I don't 00:08:50.380 --> 00:08:52.949 align:start position:0% probably is not a good idea now I don't want<00:08:50.589> to<00:08:50.650> go<00:08:50.740> too<00:08:51.070> deep<00:08:51.100> into<00:08:51.310> EVM<00:08:52.000> here<00:08:52.300> but 00:08:52.949 --> 00:08:52.959 align:start position:0% want to go too deep into EVM here but 00:08:52.959 --> 00:08:54.670 align:start position:0% want to go too deep into EVM here but we're<00:08:53.079> gonna<00:08:53.199> have<00:08:53.440> after<00:08:53.829> this<00:08:54.310> two<00:08:54.430> hours 00:08:54.670 --> 00:08:54.680 align:start position:0% we're gonna have after this two hours 00:08:54.680 --> 00:08:57.130 align:start position:0% we're gonna have after this two hours session<00:08:54.950> began<00:08:55.160> I<00:08:55.220> have<00:08:55.339> a<00:08:55.399> panel<00:08:55.760> a<00:08:55.970> medium<00:08:56.420> so 00:08:57.130 --> 00:08:57.140 align:start position:0% session began I have a panel a medium so 00:08:57.140 --> 00:08:58.510 align:start position:0% session began I have a panel a medium so I<00:08:57.170> encourage<00:08:57.380> you<00:08:57.529> guys<00:08:57.740> to<00:08:57.800> stay<00:08:58.160> for<00:08:58.370> that 00:08:58.510 --> 00:08:58.520 align:start position:0% I encourage you guys to stay for that 00:08:58.520 --> 00:09:00.970 align:start position:0% I encourage you guys to stay for that and<00:08:58.790> learn<00:08:58.970> more<00:08:59.210> about<00:08:59.330> the<00:08:59.480> VM<00:08:59.779> you<00:09:00.589> know<00:09:00.830> the 00:09:00.970 --> 00:09:00.980 align:start position:0% and learn more about the VM you know the 00:09:00.980 --> 00:09:05.079 align:start position:0% and learn more about the VM you know the past<00:09:01.190> present<00:09:01.580> and<00:09:01.700> future<00:09:01.730> of<00:09:02.120> the<00:09:02.510> EVM<00:09:04.089> but 00:09:05.079 --> 00:09:05.089 align:start position:0% past present and future of the EVM but 00:09:05.089 --> 00:09:07.480 align:start position:0% past present and future of the EVM but the<00:09:05.330> EVM<00:09:05.630> itself<00:09:06.020> does<00:09:06.350> have<00:09:06.560> one<00:09:06.800> big<00:09:07.040> benefit 00:09:07.480 --> 00:09:07.490 align:start position:0% the EVM itself does have one big benefit 00:09:07.490 --> 00:09:10.480 align:start position:0% the EVM itself does have one big benefit it<00:09:08.450> is<00:09:08.630> kind<00:09:08.870> of<00:09:08.960> small<00:09:09.100> can<00:09:10.100> easy<00:09:10.310> to 00:09:10.480 --> 00:09:10.490 align:start position:0% it is kind of small can easy to 00:09:10.490 --> 00:09:12.329 align:start position:0% it is kind of small can easy to implement<00:09:10.640> and<00:09:11.029> easy<00:09:11.270> to<00:09:11.510> comprehend<00:09:12.020> a 00:09:12.329 --> 00:09:12.339 align:start position:0% implement and easy to comprehend a 00:09:12.339 --> 00:09:15.370 align:start position:0% implement and easy to comprehend a single<00:09:13.339> person<00:09:13.700> can<00:09:13.940> easily<00:09:14.480> write<00:09:14.930> in<00:09:15.140> a<00:09:15.200> VM 00:09:15.370 --> 00:09:15.380 align:start position:0% single person can easily write in a VM 00:09:15.380 --> 00:09:19.810 align:start position:0% single person can easily write in a VM interpreter<00:09:15.830> and<00:09:16.100> grasp<00:09:17.000> the<00:09:17.420> entire<00:09:18.230> EVM<00:09:18.820> you 00:09:19.810 --> 00:09:19.820 align:start position:0% interpreter and grasp the entire EVM you 00:09:19.820 --> 00:09:22.630 align:start position:0% interpreter and grasp the entire EVM you know<00:09:19.910> specification<00:09:20.570> I<00:09:21.190> think<00:09:22.190> the<00:09:22.279> same<00:09:22.430> kind 00:09:22.630 --> 00:09:22.640 align:start position:0% know specification I think the same kind 00:09:22.640 --> 00:09:24.160 align:start position:0% know specification I think the same kind of<00:09:22.790> applies<00:09:23.000> to<00:09:23.149> awesome<00:09:23.450> but<00:09:23.930> there<00:09:24.020> wasn't 00:09:24.160 --> 00:09:24.170 align:start position:0% of applies to awesome but there wasn't 00:09:24.170 --> 00:09:27.010 align:start position:0% of applies to awesome but there wasn't specification<00:09:24.980> is<00:09:25.279> a<00:09:25.760> proper<00:09:26.330> specification 00:09:27.010 --> 00:09:27.020 align:start position:0% specification is a proper specification 00:09:27.020 --> 00:09:30.370 align:start position:0% specification is a proper specification so<00:09:27.830> it<00:09:27.980> is<00:09:28.100> long<00:09:28.370> and<00:09:28.790> it<00:09:29.360> is<00:09:29.390> extensive<00:09:30.170> and 00:09:30.370 --> 00:09:30.380 align:start position:0% so it is long and it is extensive and 00:09:30.380 --> 00:09:32.829 align:start position:0% so it is long and it is extensive and explains<00:09:30.980> every<00:09:31.370> single<00:09:31.730> edge<00:09:31.850> case<00:09:32.089> there's 00:09:32.829 --> 00:09:32.839 align:start position:0% explains every single edge case there's 00:09:32.839 --> 00:09:34.990 align:start position:0% explains every single edge case there's no<00:09:33.080> such<00:09:33.320> specification<00:09:33.920> for<00:09:34.040> the<00:09:34.160> VM<00:09:34.430> so<00:09:34.940> if 00:09:34.990 --> 00:09:35.000 align:start position:0% no such specification for the VM so if 00:09:35.000 --> 00:09:36.579 align:start position:0% no such specification for the VM so if you<00:09:35.120> look<00:09:35.240> at<00:09:35.330> the<00:09:35.420> EVM<00:09:35.690> spec<00:09:35.990> it<00:09:36.140> looks<00:09:36.350> small 00:09:36.579 --> 00:09:36.589 align:start position:0% you look at the EVM spec it looks small 00:09:36.589 --> 00:09:39.160 align:start position:0% you look at the EVM spec it looks small and<00:09:36.620> simple<00:09:37.100> but<00:09:38.089> I<00:09:38.149> don't<00:09:38.420> think<00:09:38.570> they<00:09:38.660> differ 00:09:39.160 --> 00:09:39.170 align:start position:0% and simple but I don't think they differ 00:09:39.170 --> 00:09:41.710 align:start position:0% and simple but I don't think they differ that<00:09:39.320> much<00:09:39.580> Paul<00:09:40.580> gonna<00:09:40.790> talk<00:09:41.000> V<00:09:41.270> more<00:09:41.510> about 00:09:41.710 --> 00:09:41.720 align:start position:0% that much Paul gonna talk V more about 00:09:41.720 --> 00:09:45.510 align:start position:0% that much Paul gonna talk V more about this<00:09:41.899> in<00:09:42.410> the<00:09:42.589> second<00:09:42.890> part<00:09:43.040> of<00:09:43.190> the<00:09:43.630> session 00:09:45.510 --> 00:09:45.520 align:start position:0% this in the second part of the session 00:09:45.520 --> 00:09:48.910 align:start position:0% this in the second part of the session okay<00:09:46.520> finally<00:09:47.149> we<00:09:47.270> reached<00:09:47.510> you<00:09:47.720> awesome<00:09:48.050> so 00:09:48.910 --> 00:09:48.920 align:start position:0% okay finally we reached you awesome so 00:09:48.920 --> 00:09:51.550 align:start position:0% okay finally we reached you awesome so what<00:09:49.010> is<00:09:49.160> he<00:09:49.279> wasn't<00:09:49.870> we<00:09:50.870> are<00:09:50.959> trying<00:09:51.230> to<00:09:51.380> Mary 00:09:51.550 --> 00:09:51.560 align:start position:0% what is he wasn't we are trying to Mary 00:09:51.560 --> 00:09:55.060 align:start position:0% what is he wasn't we are trying to Mary was<00:09:51.860> him<00:09:52.070> and<00:09:52.399> etherium<00:09:52.820> together<00:09:53.830> but<00:09:54.830> he<00:09:54.890> was 00:09:55.060 --> 00:09:55.070 align:start position:0% was him and etherium together but he was 00:09:55.070 --> 00:09:57.370 align:start position:0% was him and etherium together but he was amazed<00:09:55.310> really<00:09:55.430> just<00:09:55.730> wasn't<00:09:56.089> we<00:09:56.930> didn't<00:09:57.230> have 00:09:57.370 --> 00:09:57.380 align:start position:0% amazed really just wasn't we didn't have 00:09:57.380 --> 00:09:59.260 align:start position:0% amazed really just wasn't we didn't have to<00:09:57.500> change<00:09:57.649> anything<00:09:57.830> in<00:09:58.190> it<00:09:58.310> and<00:09:58.940> that's<00:09:59.150> the 00:09:59.260 --> 00:09:59.270 align:start position:0% to change anything in it and that's the 00:09:59.270 --> 00:10:01.780 align:start position:0% to change anything in it and that's the beauty<00:09:59.510> of<00:09:59.540> the<00:10:00.170> design<00:10:00.560> of<00:10:00.830> extensibility<00:10:01.459> it 00:10:01.780 --> 00:10:01.790 align:start position:0% beauty of the design of extensibility it 00:10:01.790 --> 00:10:06.370 align:start position:0% beauty of the design of extensibility it has<00:10:03.430> so<00:10:04.430> basically<00:10:04.730> the<00:10:05.390> extensibility<00:10:05.839> we 00:10:06.370 --> 00:10:06.380 align:start position:0% has so basically the extensibility we 00:10:06.380 --> 00:10:09.579 align:start position:0% has so basically the extensibility we have<00:10:06.620> to<00:10:06.770> adhere<00:10:06.950> is<00:10:07.490> we<00:10:07.970> have<00:10:08.060> to<00:10:08.180> expose<00:10:08.660> DTM 00:10:09.579 --> 00:10:09.589 align:start position:0% have to adhere is we have to expose DTM 00:10:09.589 --> 00:10:12.790 align:start position:0% have to adhere is we have to expose DTM state<00:10:09.920> access<00:10:10.459> and<00:10:10.959> modification<00:10:11.959> and<00:10:12.170> access 00:10:12.790 --> 00:10:12.800 align:start position:0% state access and modification and access 00:10:12.800 --> 00:10:15.850 align:start position:0% state access and modification and access features<00:10:13.270> into<00:10:14.270> web<00:10:14.540> assembly<00:10:14.959> and<00:10:15.230> that<00:10:15.680> can 00:10:15.850 --> 00:10:15.860 align:start position:0% features into web assembly and that can 00:10:15.860 --> 00:10:17.320 align:start position:0% features into web assembly and that can be<00:10:15.980> done<00:10:16.160> without<00:10:16.400> changing<00:10:16.820> web<00:10:16.910> assembly 00:10:17.320 --> 00:10:17.330 align:start position:0% be done without changing web assembly 00:10:17.330 --> 00:10:19.570 align:start position:0% be done without changing web assembly because<00:10:17.810> web<00:10:17.990> assembly<00:10:18.290> is<00:10:18.380> designed<00:10:18.709> to<00:10:19.310> have 00:10:19.570 --> 00:10:19.580 align:start position:0% because web assembly is designed to have 00:10:19.580 --> 00:10:22.660 align:start position:0% because web assembly is designed to have a<00:10:19.940> way<00:10:20.570> to<00:10:20.630> import<00:10:21.230> external<00:10:21.589> calls<00:10:21.980> and<00:10:22.310> we're 00:10:22.660 --> 00:10:22.670 align:start position:0% a way to import external calls and we're 00:10:22.670 --> 00:10:24.880 align:start position:0% a way to import external calls and we're exposing<00:10:23.060> all<00:10:23.510> these<00:10:23.690> features<00:10:23.990> as<00:10:24.410> external 00:10:24.880 --> 00:10:24.890 align:start position:0% exposing all these features as external 00:10:24.890 --> 00:10:28.420 align:start position:0% exposing all these features as external calls<00:10:25.130> to<00:10:25.370> the<00:10:25.459> wasn't<00:10:25.790> bytecode<00:10:27.160> that<00:10:28.160> being 00:10:28.420 --> 00:10:28.430 align:start position:0% calls to the wasn't bytecode that being 00:10:28.430 --> 00:10:31.840 align:start position:0% calls to the wasn't bytecode that being said<00:10:28.850> we<00:10:29.690> don't<00:10:29.930> want<00:10:30.110> like<00:10:30.520> regular<00:10:31.520> wasn't 00:10:31.840 --> 00:10:31.850 align:start position:0% said we don't want like regular wasn't 00:10:31.850 --> 00:10:34.420 align:start position:0% said we don't want like regular wasn't bytecode<00:10:32.270> to<00:10:32.510> be<00:10:32.600> deployed<00:10:32.900> we<00:10:33.860> do<00:10:34.010> want<00:10:34.279> to 00:10:34.420 --> 00:10:34.430 align:start position:0% bytecode to be deployed we do want to 00:10:34.430 --> 00:10:36.400 align:start position:0% bytecode to be deployed we do want to verify<00:10:34.610> the<00:10:34.880> debate<00:10:35.330> killed<00:10:35.660> complies<00:10:36.380> to 00:10:36.400 --> 00:10:36.410 align:start position:0% verify the debate killed complies to 00:10:36.410 --> 00:10:39.579 align:start position:0% verify the debate killed complies to certain<00:10:36.980> rules<00:10:37.130> we<00:10:37.430> want<00:10:37.520> to<00:10:37.640> enforce<00:10:38.589> the 00:10:39.579 --> 00:10:39.589 align:start position:0% certain rules we want to enforce the 00:10:39.589 --> 00:10:41.500 align:start position:0% certain rules we want to enforce the good<00:10:39.740> news<00:10:39.950> is<00:10:40.100> though<00:10:40.339> that<00:10:41.000> you<00:10:41.150> can<00:10:41.270> use<00:10:41.480> a 00:10:41.500 --> 00:10:41.510 align:start position:0% good news is though that you can use a 00:10:41.510 --> 00:10:43.390 align:start position:0% good news is though that you can use a regular<00:10:41.779> compiler<00:10:42.380> which<00:10:42.680> supports<00:10:43.040> possum 00:10:43.390 --> 00:10:43.400 align:start position:0% regular compiler which supports possum 00:10:43.400 --> 00:10:44.769 align:start position:0% regular compiler which supports possum and<00:10:43.550> you<00:10:43.640> can<00:10:43.790> compile<00:10:44.089> the<00:10:44.240> code<00:10:44.390> with<00:10:44.600> that 00:10:44.769 --> 00:10:44.779 align:start position:0% and you can compile the code with that 00:10:44.779 --> 00:10:47.890 align:start position:0% and you can compile the code with that you<00:10:45.260> don't<00:10:45.440> need<00:10:45.529> any<00:10:45.680> change<00:10:45.950> there<00:10:46.660> and<00:10:47.660> most 00:10:47.890 --> 00:10:47.900 align:start position:0% you don't need any change there and most 00:10:47.900 --> 00:10:49.240 align:start position:0% you don't need any change there and most of<00:10:48.020> the<00:10:48.110> time<00:10:48.320> you<00:10:48.470> don't<00:10:48.560> even<00:10:48.680> need<00:10:48.890> any<00:10:49.010> kind 00:10:49.240 --> 00:10:49.250 align:start position:0% of the time you don't even need any kind 00:10:49.250 --> 00:10:51.730 align:start position:0% of the time you don't even need any kind of<00:10:49.310> post-processing<00:10:50.230> but<00:10:51.230> we<00:10:51.350> do<00:10:51.470> have<00:10:51.649> to 00:10:51.730 --> 00:10:51.740 align:start position:0% of post-processing but we do have to 00:10:51.740 --> 00:10:53.380 align:start position:0% of post-processing but we do have to ensure<00:10:52.070> that<00:10:52.100> nothing<00:10:52.730> goes<00:10:52.880> wrong<00:10:53.120> in<00:10:53.300> a 00:10:53.380 --> 00:10:53.390 align:start position:0% ensure that nothing goes wrong in a 00:10:53.390 --> 00:10:55.930 align:start position:0% ensure that nothing goes wrong in a consensus<00:10:54.230> setting<00:10:54.560> in<00:10:54.649> a<00:10:54.709> block<00:10:54.890> chain<00:10:55.190> so<00:10:55.910> we 00:10:55.930 --> 00:10:55.940 align:start position:0% consensus setting in a block chain so we 00:10:55.940 --> 00:10:57.760 align:start position:0% consensus setting in a block chain so we have<00:10:56.149> this<00:10:56.270> verification<00:10:56.899> step<00:10:57.170> when<00:10:57.500> someone 00:10:57.760 --> 00:10:57.770 align:start position:0% have this verification step when someone 00:10:57.770 --> 00:11:00.430 align:start position:0% have this verification step when someone is<00:10:57.950> supplying<00:10:58.329> deploying<00:10:59.329> wasn't<00:11:00.050> bytecode 00:11:00.430 --> 00:11:00.440 align:start position:0% is supplying deploying wasn't bytecode 00:11:00.440 --> 00:11:03.790 align:start position:0% is supplying deploying wasn't bytecode we<00:11:01.339> run<00:11:01.730> it<00:11:01.820> to<00:11:02.060> another<00:11:02.329> contract<00:11:02.990> which<00:11:03.620> we 00:11:03.790 --> 00:11:03.800 align:start position:0% we run it to another contract which we 00:11:03.800 --> 00:11:05.650 align:start position:0% we run it to another contract which we call<00:11:03.950> the<00:11:04.070> seminal<00:11:04.459> contract<00:11:04.910> and<00:11:05.180> this 00:11:05.650 --> 00:11:05.660 align:start position:0% call the seminal contract and this 00:11:05.660 --> 00:11:07.929 align:start position:0% call the seminal contract and this contract<00:11:06.200> is<00:11:06.470> looking<00:11:06.980> up 00:11:07.929 --> 00:11:07.939 align:start position:0% contract is looking up 00:11:07.939 --> 00:11:09.699 align:start position:0% contract is looking up features<00:11:08.359> which<00:11:08.720> shouldn't<00:11:09.019> be<00:11:09.109> using<00:11:09.289> wasn't 00:11:09.699 --> 00:11:09.709 align:start position:0% features which shouldn't be using wasn't 00:11:09.709 --> 00:11:12.039 align:start position:0% features which shouldn't be using wasn't bytecode<00:11:10.099> so<00:11:10.879> one<00:11:11.029> feature<00:11:11.329> which<00:11:11.749> always 00:11:12.039 --> 00:11:12.049 align:start position:0% bytecode so one feature which always 00:11:12.049 --> 00:11:13.839 align:start position:0% bytecode so one feature which always comes<00:11:12.379> up<00:11:12.589> and<00:11:12.739> which<00:11:12.889> is<00:11:13.009> the<00:11:13.129> major<00:11:13.309> one<00:11:13.489> we 00:11:13.839 --> 00:11:13.849 align:start position:0% comes up and which is the major one we 00:11:13.849 --> 00:11:15.819 align:start position:0% comes up and which is the major one we have<00:11:13.999> to<00:11:14.179> restrict<00:11:14.599> is<00:11:14.959> floating-point 00:11:15.819 --> 00:11:15.829 align:start position:0% have to restrict is floating-point 00:11:15.829 --> 00:11:18.159 align:start position:0% have to restrict is floating-point numbers<00:11:16.749> they<00:11:17.749> cannot<00:11:17.959> deal<00:11:18.109> with 00:11:18.159 --> 00:11:18.169 align:start position:0% numbers they cannot deal with 00:11:18.169 --> 00:11:21.699 align:start position:0% numbers they cannot deal with floating-point<00:11:18.619> numbers<00:11:19.369> right<00:11:20.269> now<00:11:20.539> in<00:11:20.839> in<00:11:21.559> a 00:11:21.699 --> 00:11:21.709 align:start position:0% floating-point numbers right now in in a 00:11:21.709 --> 00:11:25.689 align:start position:0% floating-point numbers right now in in a consensus<00:11:22.249> setting<00:11:22.809> so<00:11:23.809> we<00:11:24.109> just<00:11:24.379> reject<00:11:25.189> any 00:11:25.689 --> 00:11:25.699 align:start position:0% consensus setting so we just reject any 00:11:25.699 --> 00:11:29.289 align:start position:0% consensus setting so we just reject any contract<00:11:26.299> which<00:11:26.809> uses<00:11:27.259> floating-point<00:11:28.299> but 00:11:29.289 --> 00:11:29.299 align:start position:0% contract which uses floating-point but 00:11:29.299 --> 00:11:30.639 align:start position:0% contract which uses floating-point but in<00:11:29.479> most<00:11:29.599> of<00:11:29.720> the<00:11:29.779> languages<00:11:30.169> you<00:11:30.379> don't<00:11:30.529> have 00:11:30.639 --> 00:11:30.649 align:start position:0% in most of the languages you don't have 00:11:30.649 --> 00:11:32.619 align:start position:0% in most of the languages you don't have to<00:11:30.769> use<00:11:30.859> floating-point<00:11:31.220> anyway<00:11:31.789> for 00:11:32.619 --> 00:11:32.629 align:start position:0% to use floating-point anyway for 00:11:32.629 --> 00:11:34.210 align:start position:0% to use floating-point anyway for contracts<00:11:33.079> that<00:11:33.169> this<00:11:33.319> is<00:11:33.409> not<00:11:33.559> a<00:11:33.589> problem 00:11:34.210 --> 00:11:34.220 align:start position:0% contracts that this is not a problem 00:11:34.220 --> 00:11:36.729 align:start position:0% contracts that this is not a problem the<00:11:35.119> other<00:11:35.479> big<00:11:35.749> part<00:11:35.899> we<00:11:36.109> have<00:11:36.229> to<00:11:36.409> do<00:11:36.499> during 00:11:36.729 --> 00:11:36.739 align:start position:0% the other big part we have to do during 00:11:36.739 --> 00:11:38.829 align:start position:0% the other big part we have to do during test<00:11:37.039> deployment<00:11:37.279> process<00:11:37.939> is<00:11:38.149> to<00:11:38.449> inject 00:11:38.829 --> 00:11:38.839 align:start position:0% test deployment process is to inject 00:11:38.839 --> 00:11:42.249 align:start position:0% test deployment process is to inject metering<00:11:39.519> into<00:11:40.519> web<00:11:40.729> assembly<00:11:41.149> the<00:11:41.989> reason 00:11:42.249 --> 00:11:42.259 align:start position:0% metering into web assembly the reason 00:11:42.259 --> 00:11:43.659 align:start position:0% metering into web assembly the reason for<00:11:42.379> that<00:11:42.439> is<00:11:42.739> we<00:11:42.979> don't<00:11:43.159> want<00:11:43.309> to<00:11:43.459> have 00:11:43.659 --> 00:11:43.669 align:start position:0% for that is we don't want to have 00:11:43.669 --> 00:11:46.749 align:start position:0% for that is we don't want to have specific<00:11:44.089> was<00:11:44.779> in<00:11:44.989> VMs<00:11:45.529> which<00:11:46.099> do<00:11:46.309> run<00:11:46.519> time 00:11:46.749 --> 00:11:46.759 align:start position:0% specific was in VMs which do run time 00:11:46.759 --> 00:11:49.599 align:start position:0% specific was in VMs which do run time metering<00:11:47.209> we<00:11:47.869> still<00:11:48.109> want<00:11:48.289> to<00:11:48.319> use<00:11:48.519> you<00:11:49.519> know 00:11:49.599 --> 00:11:49.609 align:start position:0% metering we still want to use you know 00:11:49.609 --> 00:11:52.059 align:start position:0% metering we still want to use you know generic<00:11:50.029> was<00:11:50.239> in<00:11:50.449> VMs<00:11:50.749> or<00:11:51.079> at<00:11:51.589> least<00:11:51.799> have<00:11:52.039> the 00:11:52.059 --> 00:11:52.069 align:start position:0% generic was in VMs or at least have the 00:11:52.069 --> 00:11:54.069 align:start position:0% generic was in VMs or at least have the ability<00:11:52.639> to<00:11:52.669> use<00:11:52.909> generate<00:11:53.239> was<00:11:53.449> in<00:11:53.629> VMs 00:11:54.069 --> 00:11:54.079 align:start position:0% ability to use generate was in VMs 00:11:54.079 --> 00:11:57.519 align:start position:0% ability to use generate was in VMs that<00:11:55.009> being<00:11:55.249> said<00:11:55.579> I<00:11:55.879> do<00:11:56.539> believe<00:11:57.109> that<00:11:57.319> we 00:11:57.519 --> 00:11:57.529 align:start position:0% that being said I do believe that we 00:11:57.529 --> 00:12:00.399 align:start position:0% that being said I do believe that we have<00:11:57.769> to<00:11:57.799> have<00:11:58.220> specific<00:11:59.149> was<00:11:59.959> MVM 00:12:00.399 --> 00:12:00.409 align:start position:0% have to have specific was MVM 00:12:00.409 --> 00:12:03.669 align:start position:0% have to have specific was MVM implementations<00:12:01.069> in<00:12:01.279> our<00:12:01.549> nodes<00:12:02.119> which<00:12:03.109> you 00:12:03.669 --> 00:12:03.679 align:start position:0% implementations in our nodes which you 00:12:03.679 --> 00:12:05.979 align:start position:0% implementations in our nodes which you know<00:12:03.799> are<00:12:03.949> really<00:12:04.099> designed<00:12:04.579> to<00:12:04.849> work<00:12:05.569> in<00:12:05.749> this 00:12:05.979 --> 00:12:05.989 align:start position:0% know are really designed to work in this 00:12:05.989 --> 00:12:07.019 align:start position:0% know are really designed to work in this environment 00:12:07.019 --> 00:12:07.029 align:start position:0% environment 00:12:07.029 --> 00:12:09.039 align:start position:0% environment but<00:12:08.029> they're<00:12:08.149> still<00:12:08.329> compatible<00:12:08.659> with<00:12:08.959> it 00:12:09.039 --> 00:12:09.049 align:start position:0% but they're still compatible with it 00:12:09.049 --> 00:12:11.499 align:start position:0% but they're still compatible with it wasn't<00:12:09.319> byte<00:12:09.439> code<00:12:09.999> okay<00:12:10.999> some<00:12:11.239> of<00:12:11.269> the 00:12:11.499 --> 00:12:11.509 align:start position:0% wasn't byte code okay some of the 00:12:11.509 --> 00:12:13.239 align:start position:0% wasn't byte code okay some of the high-level<00:12:11.839> design<00:12:12.079> goals<00:12:12.470> we<00:12:12.709> have<00:12:12.859> followed 00:12:13.239 --> 00:12:13.249 align:start position:0% high-level design goals we have followed 00:12:13.249 --> 00:12:16.329 align:start position:0% high-level design goals we have followed are<00:12:14.529> it's<00:12:15.529> really<00:12:15.769> just<00:12:15.979> to<00:12:16.099> have<00:12:16.249> an 00:12:16.329 --> 00:12:16.339 align:start position:0% are it's really just to have an 00:12:16.339 --> 00:12:18.579 align:start position:0% are it's really just to have an extensible<00:12:16.819> foundation<00:12:17.479> for<00:12:17.989> code<00:12:18.169> execution 00:12:18.579 --> 00:12:18.589 align:start position:0% extensible foundation for code execution 00:12:18.589 --> 00:12:20.979 align:start position:0% extensible foundation for code execution and<00:12:19.309> it<00:12:20.269> wasn't<00:12:20.419> it's<00:12:20.629> kind<00:12:20.809> of<00:12:20.839> like<00:12:20.959> a 00:12:20.979 --> 00:12:20.989 align:start position:0% and it wasn't it's kind of like a 00:12:20.989 --> 00:12:25.089 align:start position:0% and it wasn't it's kind of like a blueprint<00:12:21.409> for<00:12:22.479> computational<00:12:24.009> you<00:12:25.009> know 00:12:25.089 --> 00:12:25.099 align:start position:0% blueprint for computational you know 00:12:25.099 --> 00:12:28.479 align:start position:0% blueprint for computational you know describing<00:12:25.579> computation<00:12:26.329> so<00:12:26.899> you<00:12:27.349> can<00:12:28.129> take 00:12:28.479 --> 00:12:28.489 align:start position:0% describing computation so you can take 00:12:28.489 --> 00:12:30.279 align:start position:0% describing computation so you can take this<00:12:28.669> wasn't<00:12:28.879> blueprint<00:12:29.569> and<00:12:29.959> you<00:12:30.079> can 00:12:30.279 --> 00:12:30.289 align:start position:0% this wasn't blueprint and you can 00:12:30.289 --> 00:12:31.569 align:start position:0% this wasn't blueprint and you can translate<00:12:30.589> it<00:12:30.799> to<00:12:30.829> local<00:12:31.069> machine<00:12:31.399> code 00:12:31.569 --> 00:12:31.579 align:start position:0% translate it to local machine code 00:12:31.579 --> 00:12:34.089 align:start position:0% translate it to local machine code that's<00:12:32.029> high<00:12:32.239> it's<00:12:32.389> design<00:12:32.779> so<00:12:33.709> I<00:12:33.769> think<00:12:33.979> it's 00:12:34.089 --> 00:12:34.099 align:start position:0% that's high it's design so I think it's 00:12:34.099 --> 00:12:37.569 align:start position:0% that's high it's design so I think it's a<00:12:34.129> really<00:12:34.309> good<00:12:34.369> foundation<00:12:34.519> for<00:12:35.479> this<00:12:36.579> we're 00:12:37.569 --> 00:12:37.579 align:start position:0% a really good foundation for this we're 00:12:37.579 --> 00:12:39.159 align:start position:0% a really good foundation for this we're also<00:12:37.669> trying<00:12:37.970> to<00:12:38.149> tap<00:12:38.299> into<00:12:38.569> a<00:12:38.599> very<00:12:38.720> bigger 00:12:39.159 --> 00:12:39.169 align:start position:0% also trying to tap into a very bigger 00:12:39.169 --> 00:12:42.609 align:start position:0% also trying to tap into a very bigger ecosystem<00:12:39.559> here<00:12:40.189> until<00:12:41.149> more<00:12:41.449> languages<00:12:41.989> but 00:12:42.609 --> 00:12:42.619 align:start position:0% ecosystem here until more languages but 00:12:42.619 --> 00:12:45.219 align:start position:0% ecosystem here until more languages but more<00:12:43.029> or<00:12:44.029> importantly<00:12:44.539> a<00:12:44.659> lot<00:12:44.779> of<00:12:45.049> more 00:12:45.219 --> 00:12:45.229 align:start position:0% more or importantly a lot of more 00:12:45.229 --> 00:12:47.519 align:start position:0% more or importantly a lot of more tooling<00:12:45.939> especially<00:12:46.939> regarding<00:12:47.299> security 00:12:47.519 --> 00:12:47.529 align:start position:0% tooling especially regarding security 00:12:47.529 --> 00:12:52.359 align:start position:0% tooling especially regarding security analysis<00:12:48.529> or<00:12:49.189> Danang<00:12:49.579> etc<00:12:50.229> and<00:12:51.229> there's<00:12:52.189> this 00:12:52.359 --> 00:12:52.369 align:start position:0% analysis or Danang etc and there's this 00:12:52.369 --> 00:12:54.429 align:start position:0% analysis or Danang etc and there's this point<00:12:52.609> of<00:12:52.789> reducing<00:12:53.299> complexity<00:12:53.839> in 00:12:54.429 --> 00:12:54.439 align:start position:0% point of reducing complexity in 00:12:54.439 --> 00:12:57.549 align:start position:0% point of reducing complexity in aetherium<00:12:55.009> and<00:12:55.970> how<00:12:56.179> if<00:12:56.479> you're<00:12:56.929> introducing 00:12:57.549 --> 00:12:57.559 align:start position:0% aetherium and how if you're introducing 00:12:57.559 --> 00:12:59.979 align:start position:0% aetherium and how if you're introducing this<00:12:57.739> kind<00:12:58.189> of<00:12:58.399> more<00:12:58.579> complicated<00:12:58.909> thing<00:12:59.809> at 00:12:59.979 --> 00:12:59.989 align:start position:0% this kind of more complicated thing at 00:12:59.989 --> 00:13:01.029 align:start position:0% this kind of more complicated thing at least<00:13:00.169> some<00:13:00.259> people<00:13:00.499> claim<00:13:00.679> it's<00:13:00.829> kind<00:13:00.979> of 00:13:01.029 --> 00:13:01.039 align:start position:0% least some people claim it's kind of 00:13:01.039 --> 00:13:03.819 align:start position:0% least some people claim it's kind of more<00:13:01.129> complicated<00:13:02.229> but<00:13:03.229> there<00:13:03.589> are<00:13:03.679> ways<00:13:03.799> to 00:13:03.819 --> 00:13:03.829 align:start position:0% more complicated but there are ways to 00:13:03.829 --> 00:13:05.619 align:start position:0% more complicated but there are ways to reduce<00:13:04.129> the<00:13:04.399> complexity<00:13:04.879> in<00:13:05.059> atrium<00:13:05.479> by 00:13:05.619 --> 00:13:05.629 align:start position:0% reduce the complexity in atrium by 00:13:05.629 --> 00:13:08.409 align:start position:0% reduce the complexity in atrium by having<00:13:05.959> wasum<00:13:06.579> so<00:13:07.579> one<00:13:07.699> example<00:13:07.970> here<00:13:08.269> when<00:13:08.389> I 00:13:08.409 --> 00:13:08.419 align:start position:0% having wasum so one example here when I 00:13:08.419 --> 00:13:10.629 align:start position:0% having wasum so one example here when I highlight<00:13:08.659> is<00:13:08.989> pecan<00:13:09.409> pies<00:13:09.589> so<00:13:10.220> today<00:13:10.459> with 00:13:10.629 --> 00:13:10.639 align:start position:0% highlight is pecan pies so today with 00:13:10.639 --> 00:13:12.429 align:start position:0% highlight is pecan pies so today with freaking<00:13:10.939> pies<00:13:11.119> every<00:13:11.599> single<00:13:11.869> client<00:13:12.019> has<00:13:12.289> to 00:13:12.429 --> 00:13:12.439 align:start position:0% freaking pies every single client has to 00:13:12.439 --> 00:13:14.949 align:start position:0% freaking pies every single client has to implant<00:13:12.739> pecan<00:13:13.009> pies<00:13:13.220> themselves<00:13:13.809> which<00:13:14.809> was 00:13:14.949 --> 00:13:14.959 align:start position:0% implant pecan pies themselves which was 00:13:14.959 --> 00:13:16.269 align:start position:0% implant pecan pies themselves which was him<00:13:15.139> you<00:13:15.229> could<00:13:15.409> just<00:13:15.649> apply<00:13:15.829> a<00:13:15.919> single 00:13:16.269 --> 00:13:16.279 align:start position:0% him you could just apply a single 00:13:16.279 --> 00:13:18.219 align:start position:0% him you could just apply a single implementation<00:13:16.939> of<00:13:17.059> this<00:13:17.239> pecan<00:13:17.569> pie<00:13:17.749> in 00:13:18.219 --> 00:13:18.229 align:start position:0% implementation of this pecan pie in 00:13:18.229 --> 00:13:20.139 align:start position:0% implementation of this pecan pie in volume<00:13:18.709> itself<00:13:19.039> and<00:13:19.249> everything<00:13:19.669> each<00:13:19.909> of<00:13:20.059> the 00:13:20.139 --> 00:13:20.149 align:start position:0% volume itself and everything each of the 00:13:20.149 --> 00:13:21.850 align:start position:0% volume itself and everything each of the clients<00:13:20.539> say<00:13:21.019> that's<00:13:21.229> you<00:13:21.439> know 00:13:21.850 --> 00:13:21.860 align:start position:0% clients say that's you know 00:13:21.860 --> 00:13:25.900 align:start position:0% clients say that's you know to<00:13:22.279> be<00:13:22.370> written<00:13:23.920> but<00:13:24.920> one<00:13:25.130> really<00:13:25.730> interesting 00:13:25.900 --> 00:13:25.910 align:start position:0% to be written but one really interesting 00:13:25.910 --> 00:13:28.210 align:start position:0% to be written but one really interesting thing<00:13:26.269> which<00:13:26.720> came<00:13:26.930> up<00:13:27.140> before<00:13:27.620> defconn<00:13:28.130> at 00:13:28.210 --> 00:13:28.220 align:start position:0% thing which came up before defconn at 00:13:28.220 --> 00:13:31.139 align:start position:0% thing which came up before defconn at the<00:13:28.310> swarm<00:13:28.519> summit<00:13:28.990> shows<00:13:29.990> from<00:13:30.230> the<00:13:30.290> light 00:13:31.139 --> 00:13:31.149 align:start position:0% the swarm summit shows from the light 00:13:31.149 --> 00:13:33.060 align:start position:0% the swarm summit shows from the light delight<00:13:32.149> flying<00:13:32.420> protocol 00:13:33.060 --> 00:13:33.070 align:start position:0% delight flying protocol 00:13:33.070 --> 00:13:35.769 align:start position:0% delight flying protocol what<00:13:34.070> does<00:13:34.190> Elia<00:13:34.610> stand<00:13:34.940> for<00:13:35.149> but<00:13:35.360> that's<00:13:35.510> the 00:13:35.769 --> 00:13:35.779 align:start position:0% what does Elia stand for but that's the 00:13:35.779 --> 00:13:38.590 align:start position:0% what does Elia stand for but that's the light<00:13:36.140> idiom<00:13:36.560> whatever<00:13:37.220> but<00:13:38.209> he's<00:13:38.360> the<00:13:38.480> light 00:13:38.590 --> 00:13:38.600 align:start position:0% light idiom whatever but he's the light 00:13:38.600 --> 00:13:39.880 align:start position:0% light idiom whatever but he's the light client<00:13:38.899> for<00:13:39.019> the<00:13:39.079> whole<00:13:39.200> person<00:13:39.380> he's 00:13:39.880 --> 00:13:39.890 align:start position:0% client for the whole person he's 00:13:39.890 --> 00:13:41.410 align:start position:0% client for the whole person he's designing<00:13:40.220> the<00:13:40.459> entire<00:13:40.670> life<00:13:40.850> line<00:13:41.060> protocol 00:13:41.410 --> 00:13:41.420 align:start position:0% designing the entire life line protocol 00:13:41.420 --> 00:13:43.030 align:start position:0% designing the entire life line protocol for<00:13:41.540> it<00:13:41.600> cerium<00:13:41.899> and<00:13:42.200> he<00:13:42.470> came<00:13:42.620> up<00:13:42.680> with<00:13:42.950> this 00:13:43.030 --> 00:13:43.040 align:start position:0% for it cerium and he came up with this 00:13:43.040 --> 00:13:45.490 align:start position:0% for it cerium and he came up with this idea<00:13:43.279> to<00:13:43.640> use<00:13:43.760> wasum<00:13:44.240> in<00:13:44.390> there<00:13:44.630> the<00:13:45.170> problem 00:13:45.490 --> 00:13:45.500 align:start position:0% idea to use wasum in there the problem 00:13:45.500 --> 00:13:47.710 align:start position:0% idea to use wasum in there the problem he's<00:13:45.649> facing<00:13:46.160> is<00:13:46.339> in<00:13:47.089> the<00:13:47.209> light<00:13:47.360> client 00:13:47.710 --> 00:13:47.720 align:start position:0% he's facing is in the light client 00:13:47.720 --> 00:13:49.750 align:start position:0% he's facing is in the light client protocol<00:13:48.260> you<00:13:48.380> have<00:13:48.500> to<00:13:48.649> make<00:13:48.829> say<00:13:49.459> you<00:13:49.519> make 00:13:49.750 --> 00:13:49.760 align:start position:0% protocol you have to make say you make 00:13:49.760 --> 00:13:52.300 align:start position:0% protocol you have to make say you make one<00:13:50.089> query<00:13:50.480> to<00:13:50.779> get<00:13:50.899> like<00:13:51.110> a<00:13:51.140> hash<00:13:51.440> and<00:13:51.709> then 00:13:52.300 --> 00:13:52.310 align:start position:0% one query to get like a hash and then 00:13:52.310 --> 00:13:53.680 align:start position:0% one query to get like a hash and then you<00:13:52.579> receive<00:13:52.880> more<00:13:53.029> data<00:13:53.240> and<00:13:53.420> then<00:13:53.510> you<00:13:53.570> have 00:13:53.680 --> 00:13:53.690 align:start position:0% you receive more data and then you have 00:13:53.690 --> 00:13:56.110 align:start position:0% you receive more data and then you have to<00:13:53.810> make<00:13:53.990> subsequent<00:13:54.410> queries<00:13:55.010> so<00:13:55.490> it<00:13:55.610> you 00:13:56.110 --> 00:13:56.120 align:start position:0% to make subsequent queries so it you 00:13:56.120 --> 00:13:57.040 align:start position:0% to make subsequent queries so it you know<00:13:56.149> bubbles<00:13:56.510> up<00:13:56.630> into<00:13:56.870> a<00:13:56.899> lot<00:13:57.019> of 00:13:57.040 --> 00:13:57.050 align:start position:0% know bubbles up into a lot of 00:13:57.050 --> 00:13:59.050 align:start position:0% know bubbles up into a lot of communities<00:13:57.560> so<00:13:58.279> what<00:13:58.430> you<00:13:58.519> could<00:13:58.670> do<00:13:58.850> is 00:13:59.050 --> 00:13:59.060 align:start position:0% communities so what you could do is 00:13:59.060 --> 00:14:02.769 align:start position:0% communities so what you could do is submit<00:13:59.480> a<00:13:59.540> computation<00:14:00.260> in<00:14:01.010> wasum<00:14:01.660> do<00:14:02.660> not 00:14:02.769 --> 00:14:02.779 align:start position:0% submit a computation in wasum do not 00:14:02.779 --> 00:14:03.790 align:start position:0% submit a computation in wasum do not know<00:14:02.870> what<00:14:02.990> the<00:14:03.110> node<00:14:03.350> executes<00:14:03.769> that 00:14:03.790 --> 00:14:03.800 align:start position:0% know what the node executes that 00:14:03.800 --> 00:14:05.259 align:start position:0% know what the node executes that computation<00:14:04.430> it<00:14:04.550> gives<00:14:04.700> you<00:14:04.820> back<00:14:04.970> all<00:14:05.180> the 00:14:05.259 --> 00:14:05.269 align:start position:0% computation it gives you back all the 00:14:05.269 --> 00:14:06.910 align:start position:0% computation it gives you back all the results<00:14:05.630> so<00:14:06.140> you<00:14:06.230> don't<00:14:06.380> need<00:14:06.500> all<00:14:06.620> this<00:14:06.740> data 00:14:06.910 --> 00:14:06.920 align:start position:0% results so you don't need all this data 00:14:06.920 --> 00:14:10.240 align:start position:0% results so you don't need all this data exchange<00:14:07.370> you<00:14:07.760> can<00:14:07.790> get<00:14:08.060> the<00:14:08.209> note<00:14:08.390> to<00:14:09.010> get<00:14:10.010> you 00:14:10.240 --> 00:14:10.250 align:start position:0% exchange you can get the note to get you 00:14:10.250 --> 00:14:12.370 align:start position:0% exchange you can get the note to get you the<00:14:10.370> data<00:14:10.550> you<00:14:10.760> need<00:14:10.790> exactly<00:14:11.230> so<00:14:12.230> I<00:14:12.260> think 00:14:12.370 --> 00:14:12.380 align:start position:0% the data you need exactly so I think 00:14:12.380 --> 00:14:13.900 align:start position:0% the data you need exactly so I think that's<00:14:12.560> really<00:14:12.620> interesting<00:14:12.800> you<00:14:13.519> know 00:14:13.900 --> 00:14:13.910 align:start position:0% that's really interesting you know 00:14:13.910 --> 00:14:16.569 align:start position:0% that's really interesting you know direction<00:14:14.329> we<00:14:14.420> could<00:14:14.540> go<00:14:15.160> but<00:14:16.160> lastly<00:14:16.490> a 00:14:16.569 --> 00:14:16.579 align:start position:0% direction we could go but lastly a 00:14:16.579 --> 00:14:18.759 align:start position:0% direction we could go but lastly a really<00:14:16.880> important<00:14:17.209> point<00:14:17.300> is<00:14:17.600> with<00:14:17.870> wisdom<00:14:18.079> we 00:14:18.759 --> 00:14:18.769 align:start position:0% really important point is with wisdom we 00:14:18.769 --> 00:14:21.310 align:start position:0% really important point is with wisdom we do<00:14:18.920> get<00:14:19.220> a<00:14:19.250> better<00:14:19.550> interaction<00:14:20.170> with<00:14:21.170> other 00:14:21.310 --> 00:14:21.320 align:start position:0% do get a better interaction with other 00:14:21.320 --> 00:14:23.500 align:start position:0% do get a better interaction with other blockchains<00:14:21.920> so<00:14:22.490> I<00:14:22.550> can<00:14:22.670> I<00:14:22.700> expand<00:14:23.089> on<00:14:23.209> those<00:14:23.450> a 00:14:23.500 --> 00:14:23.510 align:start position:0% blockchains so I can I expand on those a 00:14:23.510 --> 00:14:27.009 align:start position:0% blockchains so I can I expand on those a bit<00:14:23.720> later<00:14:25.000> so<00:14:26.000> with<00:14:26.120> the<00:14:26.180> languages<00:14:26.540> itself 00:14:27.009 --> 00:14:27.019 align:start position:0% bit later so with the languages itself 00:14:27.019 --> 00:14:29.350 align:start position:0% bit later so with the languages itself we<00:14:27.560> are<00:14:27.709> tapping<00:14:27.980> into<00:14:28.250> a<00:14:28.399> bigger<00:14:28.730> pool<00:14:29.329> of 00:14:29.350 --> 00:14:29.360 align:start position:0% we are tapping into a bigger pool of 00:14:29.360 --> 00:14:32.500 align:start position:0% we are tapping into a bigger pool of languages<00:14:30.230> that<00:14:31.130> being<00:14:31.339> said<00:14:31.699> we<00:14:32.120> still<00:14:32.329> wanna 00:14:32.500 --> 00:14:32.510 align:start position:0% languages that being said we still wanna 00:14:32.510 --> 00:14:33.550 align:start position:0% languages that being said we still wanna support<00:14:32.839> solidity 00:14:33.550 --> 00:14:33.560 align:start position:0% support solidity 00:14:33.560 --> 00:14:35.889 align:start position:0% support solidity so<00:14:34.190> the<00:14:34.339> solid<00:14:34.490> team<00:14:34.940> is<00:14:35.120> working<00:14:35.300> on<00:14:35.540> having 00:14:35.889 --> 00:14:35.899 align:start position:0% so the solid team is working on having 00:14:35.899 --> 00:14:37.900 align:start position:0% so the solid team is working on having awesome<00:14:36.320> output<00:14:36.890> and<00:14:37.100> hopefully<00:14:37.670> that<00:14:37.790> gonna 00:14:37.900 --> 00:14:37.910 align:start position:0% awesome output and hopefully that gonna 00:14:37.910 --> 00:14:40.870 align:start position:0% awesome output and hopefully that gonna happen<00:14:38.120> early<00:14:38.870> mid<00:14:39.290> next<00:14:39.529> year<00:14:39.880> no 00:14:40.870 --> 00:14:40.880 align:start position:0% happen early mid next year no 00:14:40.880 --> 00:14:44.769 align:start position:0% happen early mid next year no commitments<00:14:41.360> here<00:14:41.510> though<00:14:43.180> but<00:14:44.180> today<00:14:44.510> we 00:14:44.769 --> 00:14:44.779 align:start position:0% commitments here though but today we 00:14:44.779 --> 00:14:47.139 align:start position:0% commitments here though but today we already<00:14:44.930> have<00:14:45.410> a<00:14:45.740> lot<00:14:46.010> of<00:14:46.040> the<00:14:46.220> tooling<00:14:46.610> for<00:14:46.640> us 00:14:47.139 --> 00:14:47.149 align:start position:0% already have a lot of the tooling for us 00:14:47.149 --> 00:14:49.389 align:start position:0% already have a lot of the tooling for us I'm<00:14:47.329> in<00:14:47.480> rust<00:14:47.750> because<00:14:48.380> rust<00:14:48.740> is<00:14:48.920> like<00:14:49.070> the<00:14:49.220> the 00:14:49.389 --> 00:14:49.399 align:start position:0% I'm in rust because rust is like the the 00:14:49.399 --> 00:14:52.540 align:start position:0% I'm in rust because rust is like the the most<00:14:49.579> mature<00:14:50.740> language<00:14:51.740> do<00:14:51.890> you<00:14:51.920> have<00:14:52.070> to<00:14:52.310> link 00:14:52.540 --> 00:14:52.550 align:start position:0% most mature language do you have to link 00:14:52.550 --> 00:14:56.230 align:start position:0% most mature language do you have to link for<00:14:53.120> wasn't<00:14:53.860> but<00:14:54.860> there's<00:14:55.430> this<00:14:55.670> last<00:14:56.000> thing 00:14:56.230 --> 00:14:56.240 align:start position:0% for wasn't but there's this last thing 00:14:56.240 --> 00:14:58.060 align:start position:0% for wasn't but there's this last thing which<00:14:56.480> we<00:14:56.870> also<00:14:57.019> gonna<00:14:57.260> touch<00:14:57.500> on<00:14:57.620> today<00:14:57.769> is<00:14:58.040> a 00:14:58.060 --> 00:14:58.070 align:start position:0% which we also gonna touch on today is a 00:14:58.070 --> 00:15:00.160 align:start position:0% which we also gonna touch on today is a similar<00:14:58.490> script<00:14:58.760> which<00:14:59.660> is<00:14:59.690> a<00:14:59.839> language 00:15:00.160 --> 00:15:00.170 align:start position:0% similar script which is a language 00:15:00.170 --> 00:15:04.750 align:start position:0% similar script which is a language similar<00:15:00.470> to<00:15:00.649> JavaScript<00:15:01.339> and<00:15:01.839> it<00:15:02.839> is<00:15:03.730> we<00:15:04.730> are 00:15:04.750 --> 00:15:04.760 align:start position:0% similar to JavaScript and it is we are 00:15:04.760 --> 00:15:06.639 align:start position:0% similar to JavaScript and it is we are working<00:15:05.149> on<00:15:05.390> framework<00:15:05.810> in<00:15:06.019> assembly<00:15:06.410> script 00:15:06.639 --> 00:15:06.649 align:start position:0% working on framework in assembly script 00:15:06.649 --> 00:15:09.790 align:start position:0% working on framework in assembly script to<00:15:07.040> write<00:15:07.250> contracts<00:15:08.140> and<00:15:09.140> so<00:15:09.440> it's<00:15:09.589> it's 00:15:09.790 --> 00:15:09.800 align:start position:0% to write contracts and so it's it's 00:15:09.800 --> 00:15:11.470 align:start position:0% to write contracts and so it's it's really<00:15:10.190> looks<00:15:10.339> like<00:15:10.399> JavaScript<00:15:11.029> it<00:15:11.149> is<00:15:11.240> easy 00:15:11.470 --> 00:15:11.480 align:start position:0% really looks like JavaScript it is easy 00:15:11.480 --> 00:15:15.240 align:start position:0% really looks like JavaScript it is easy to<00:15:11.660> use<00:15:11.690> and<00:15:12.140> it's<00:15:12.740> compiling<00:15:13.220> -<00:15:13.519> he<00:15:13.610> wasn't 00:15:15.240 --> 00:15:15.250 align:start position:0% to use and it's compiling - he wasn't 00:15:15.250 --> 00:15:17.019 align:start position:0% to use and it's compiling - he wasn't just<00:15:16.250> if<00:15:16.399> you<00:15:16.519> know<00:15:16.640> it's<00:15:16.790> about<00:15:16.910> other 00:15:17.019 --> 00:15:17.029 align:start position:0% just if you know it's about other 00:15:17.029 --> 00:15:19.960 align:start position:0% just if you know it's about other blockchains<00:15:17.589> a<00:15:18.589> lot<00:15:19.160> of<00:15:19.279> other<00:15:19.399> blockchains 00:15:19.960 --> 00:15:19.970 align:start position:0% blockchains a lot of other blockchains 00:15:19.970 --> 00:15:22.960 align:start position:0% blockchains a lot of other blockchains using<00:15:20.779> or<00:15:20.959> considering<00:15:21.440> awesome<00:15:21.740> and<00:15:22.070> if<00:15:22.820> you 00:15:22.960 --> 00:15:22.970 align:start position:0% using or considering awesome and if you 00:15:22.970 --> 00:15:25.480 align:start position:0% using or considering awesome and if you also<00:15:23.329> do<00:15:23.690> use<00:15:23.870> wasum<00:15:24.260> that<00:15:24.949> you're<00:15:25.310> going<00:15:25.430> to 00:15:25.480 --> 00:15:25.490 align:start position:0% also do use wasum that you're going to 00:15:25.490 --> 00:15:27.699 align:start position:0% also do use wasum that you're going to have<00:15:25.610> way<00:15:26.029> more<00:15:26.060> options<00:15:26.660> -<00:15:26.899> we<00:15:27.230> have<00:15:27.470> code 00:15:27.699 --> 00:15:27.709 align:start position:0% have way more options - we have code 00:15:27.709 --> 00:15:29.590 align:start position:0% have way more options - we have code sorry<00:15:28.399> you<00:15:28.640> have<00:15:28.730> code<00:15:28.910> shared<00:15:29.240> between<00:15:29.390> all 00:15:29.590 --> 00:15:29.600 align:start position:0% sorry you have code shared between all 00:15:29.600 --> 00:15:30.069 align:start position:0% sorry you have code shared between all of<00:15:29.660> them 00:15:30.069 --> 00:15:30.079 align:start position:0% of them 00:15:30.079 --> 00:15:33.639 align:start position:0% of them so<00:15:30.770> I<00:15:30.800> think<00:15:30.860> that's<00:15:31.130> super<00:15:31.310> exciting<00:15:32.649> okay 00:15:33.639 --> 00:15:33.649 align:start position:0% so I think that's super exciting okay 00:15:33.649 --> 00:15:35.650 align:start position:0% so I think that's super exciting okay just<00:15:33.949> two<00:15:34.100> more<00:15:34.220> things<00:15:34.279> to<00:15:34.610> mention 00:15:35.650 --> 00:15:35.660 align:start position:0% just two more things to mention 00:15:35.660 --> 00:15:37.140 align:start position:0% just two more things to mention because<00:15:36.050> we<00:15:36.170> haven't<00:15:36.320> really<00:15:36.530> mentioned<00:15:36.740> like 00:15:37.140 --> 00:15:37.150 align:start position:0% because we haven't really mentioned like 00:15:37.150 --> 00:15:39.490 align:start position:0% because we haven't really mentioned like backwards-compatibility<00:15:38.150> so<00:15:39.140> if<00:15:39.260> we<00:15:39.380> have 00:15:39.490 --> 00:15:39.500 align:start position:0% backwards-compatibility so if we have 00:15:39.500 --> 00:15:41.490 align:start position:0% backwards-compatibility so if we have this<00:15:39.650> tool<00:15:39.860> called<00:15:40.130> room<00:15:40.430> VM<00:15:40.670> or<00:15:40.880> run<00:15:41.000> a<00:15:41.030> VM 00:15:41.490 --> 00:15:41.500 align:start position:0% this tool called room VM or run a VM 00:15:41.500 --> 00:15:45.220 align:start position:0% this tool called room VM or run a VM which<00:15:42.500> is<00:15:42.680> an<00:15:42.800> AVM<00:15:43.190> interpreter<00:15:43.900> compiled<00:15:44.900> Yui 00:15:45.220 --> 00:15:45.230 align:start position:0% which is an AVM interpreter compiled Yui 00:15:45.230 --> 00:15:50.140 align:start position:0% which is an AVM interpreter compiled Yui wasum<00:15:45.590> and<00:15:46.090> you<00:15:47.090> can<00:15:47.270> use<00:15:47.510> this<00:15:47.780> in<00:15:48.080> a<00:15:49.150> entirely 00:15:50.140 --> 00:15:50.150 align:start position:0% wasum and you can use this in a entirely 00:15:50.150 --> 00:15:52.330 align:start position:0% wasum and you can use this in a entirely wasum<00:15:50.660> only<00:15:50.900> client<00:15:51.290> and<00:15:51.650> you<00:15:51.770> can<00:15:51.920> run<00:15:52.100> even 00:15:52.330 --> 00:15:52.340 align:start position:0% wasum only client and you can run even 00:15:52.340 --> 00:15:55.390 align:start position:0% wasum only client and you can run even bytecode<00:15:52.910> on<00:15:53.090> this<00:15:53.450> was<00:15:53.630> only<00:15:53.960> client<00:15:54.320> and<00:15:54.740> why 00:15:55.390 --> 00:15:55.400 align:start position:0% bytecode on this was only client and why 00:15:55.400 --> 00:15:57.280 align:start position:0% bytecode on this was only client and why you<00:15:55.460> VM<00:15:55.730> is<00:15:55.850> a<00:15:55.880> similar<00:15:56.210> tool<00:15:56.450> but<00:15:56.960> instead<00:15:57.230> of 00:15:57.280 --> 00:15:57.290 align:start position:0% you VM is a similar tool but instead of 00:15:57.290 --> 00:16:00.130 align:start position:0% you VM is a similar tool but instead of having<00:15:57.710> an<00:15:57.920> interpreter<00:15:58.160> it<00:15:58.910> is<00:15:59.030> compiling<00:15:59.510> a 00:16:00.130 --> 00:16:00.140 align:start position:0% having an interpreter it is compiling a 00:16:00.140 --> 00:16:02.590 align:start position:0% having an interpreter it is compiling a VM<00:16:00.650> to<00:16:00.950> wasn't<00:16:01.280> bytecode<00:16:01.640> now<00:16:02.270> these<00:16:02.420> are 00:16:02.590 --> 00:16:02.600 align:start position:0% VM to wasn't bytecode now these are 00:16:02.600 --> 00:16:04.600 align:start position:0% VM to wasn't bytecode now these are early<00:16:02.720> prototypes<00:16:03.410> so<00:16:04.130> if<00:16:04.250> anybody<00:16:04.550> is 00:16:04.600 --> 00:16:04.610 align:start position:0% early prototypes so if anybody is 00:16:04.610 --> 00:16:05.620 align:start position:0% early prototypes so if anybody is interested<00:16:04.760> in<00:16:05.000> working<00:16:05.210> on<00:16:05.360> these<00:16:05.450> really 00:16:05.620 --> 00:16:05.630 align:start position:0% interested in working on these really 00:16:05.630 --> 00:16:09.730 align:start position:0% interested in working on these really cool<00:16:05.840> projects<00:16:06.320> please<00:16:07.250> talk<00:16:07.460> to<00:16:07.490> us<00:16:08.620> so<00:16:09.620> the 00:16:09.730 --> 00:16:09.740 align:start position:0% cool projects please talk to us so the 00:16:09.740 --> 00:16:11.680 align:start position:0% cool projects please talk to us so the next<00:16:09.920> steps<00:16:10.280> we<00:16:10.520> have<00:16:10.760> now<00:16:11.030> is<00:16:11.330> we're 00:16:11.680 --> 00:16:11.690 align:start position:0% next steps we have now is we're 00:16:11.690 --> 00:16:13.780 align:start position:0% next steps we have now is we're launching<00:16:12.380> a<00:16:12.440> test<00:16:12.650> net<00:16:12.830> and<00:16:13.040> then<00:16:13.610> we<00:16:13.730> are 00:16:13.780 --> 00:16:13.790 align:start position:0% launching a test net and then we are 00:16:13.790 --> 00:16:14.980 align:start position:0% launching a test net and then we are trying<00:16:13.880> to<00:16:14.090> get<00:16:14.210> all<00:16:14.330> of<00:16:14.450> this<00:16:14.540> into<00:16:14.780> the<00:16:14.870> main 00:16:14.980 --> 00:16:14.990 align:start position:0% trying to get all of this into the main 00:16:14.990 --> 00:16:17.470 align:start position:0% trying to get all of this into the main net<00:16:15.140> but<00:16:15.290> we<00:16:15.410> cannot<00:16:15.620> do<00:16:15.830> that<00:16:15.980> at<00:16:16.190> once<00:16:16.490> so<00:16:17.450> we 00:16:17.470 --> 00:16:17.480 align:start position:0% net but we cannot do that at once so we 00:16:17.480 --> 00:16:18.820 align:start position:0% net but we cannot do that at once so we are<00:16:17.630> trying<00:16:17.870> to<00:16:17.960> get<00:16:18.080> a<00:16:18.110> subset<00:16:18.620> of 00:16:18.820 --> 00:16:18.830 align:start position:0% are trying to get a subset of 00:16:18.830 --> 00:16:21.070 align:start position:0% are trying to get a subset of pre-compiled<00:16:19.790> only<00:16:20.180> support<00:16:20.570> into<00:16:20.840> the<00:16:20.930> manor 00:16:21.070 --> 00:16:21.080 align:start position:0% pre-compiled only support into the manor 00:16:21.080 --> 00:16:23.680 align:start position:0% pre-compiled only support into the manor and<00:16:21.380> then<00:16:22.040> I<00:16:22.070> have<00:16:22.340> the<00:16:22.520> entirety<00:16:22.880> of<00:16:23.150> ewaz<00:16:23.540> I'm 00:16:23.680 --> 00:16:23.690 align:start position:0% and then I have the entirety of ewaz I'm 00:16:23.690 --> 00:16:25.900 align:start position:0% and then I have the entirety of ewaz I'm in<00:16:23.810> the<00:16:23.900> main<00:16:24.020> that<00:16:24.520> even<00:16:25.520> though<00:16:25.580> it's<00:16:25.730> said 00:16:25.900 --> 00:16:25.910 align:start position:0% in the main that even though it's said 00:16:25.910 --> 00:16:28.840 align:start position:0% in the main that even though it's said like<00:16:26.090> a<00:16:26.120> goal<00:16:26.510> goal<00:16:26.990> number<00:16:27.380> four<00:16:27.710> I<00:16:28.010> think 00:16:28.840 --> 00:16:28.850 align:start position:0% like a goal goal number four I think 00:16:28.850 --> 00:16:33.490 align:start position:0% like a goal goal number four I think chess<00:16:29.270> /<00:16:29.480> /<00:16:30.320> e<00:16:30.650> 2.0<00:16:31.220> certainty<00:16:32.060> work<00:16:32.840> gonna 00:16:33.490 --> 00:16:33.500 align:start position:0% chess / / e 2.0 certainty work gonna 00:16:33.500 --> 00:16:37.450 align:start position:0% chess / / e 2.0 certainty work gonna happen<00:16:33.860> parallel<00:16:34.310> to<00:16:34.460> all<00:16:34.550> of<00:16:34.700> this<00:16:36.430> so<00:16:37.430> that 00:16:37.450 --> 00:16:37.460 align:start position:0% happen parallel to all of this so that 00:16:37.460 --> 00:16:39.490 align:start position:0% happen parallel to all of this so that was<00:16:37.700> the<00:16:37.820> intro<00:16:38.060> please<00:16:38.660> check<00:16:38.960> these<00:16:39.140> back 00:16:39.490 --> 00:16:39.500 align:start position:0% was the intro please check these back 00:16:39.500 --> 00:16:41.520 align:start position:0% was the intro please check these back and<00:16:39.710> all<00:16:39.770> the<00:16:39.890> code<00:16:40.010> we<00:16:40.190> have<00:16:40.220> show<00:16:40.700> and<00:16:40.850> get<00:16:41.000> er 00:16:41.520 --> 00:16:41.530 align:start position:0% and all the code we have show and get er 00:16:41.530 --> 00:16:49.710 align:start position:0% and all the code we have show and get er create<00:16:42.530> apps<00:16:42.710> and<00:16:42.980> talk<00:16:43.160> to<00:16:43.310> us<00:16:43.780> thank<00:16:44.780> you 00:16:49.710 --> 00:16:49.720 align:start position:0% 00:16:49.720 --> 00:16:51.820 align:start position:0% sorry<00:16:50.720> I<00:16:50.780> didn't<00:16:51.050> sort<00:16:51.230> of<00:16:51.320> do<00:16:51.440> an<00:16:51.530> intro<00:16:51.770> in 00:16:51.820 --> 00:16:51.830 align:start position:0% sorry I didn't sort of do an intro in 00:16:51.830 --> 00:16:53.410 align:start position:0% sorry I didn't sort of do an intro in the<00:16:51.890> beginning<00:16:52.130> that<00:16:52.370> was<00:16:52.520> Alex<00:16:53.120> Parrish<00:16:53.330> I 00:16:53.410 --> 00:16:53.420 align:start position:0% the beginning that was Alex Parrish I 00:16:53.420 --> 00:16:54.880 align:start position:0% the beginning that was Alex Parrish I see<00:16:53.570> he's<00:16:53.720> our<00:16:53.870> team<00:16:54.050> lead<00:16:54.230> one<00:16:54.530> more<00:16:54.680> round<00:16:54.800> of 00:16:54.880 --> 00:16:54.890 align:start position:0% see he's our team lead one more round of 00:16:54.890 --> 00:17:03.010 align:start position:0% see he's our team lead one more round of applause<00:16:55.130> for<00:16:55.160> Alex<00:17:01.300> all<00:17:02.300> right<00:17:02.360> up<00:17:02.600> next<00:17:02.630> I 00:17:03.010 --> 00:17:03.020 align:start position:0% applause for Alex all right up next I 00:17:03.020 --> 00:17:04.870 align:start position:0% applause for Alex all right up next I think<00:17:03.230> we're<00:17:03.350> gonna<00:17:03.440> do<00:17:03.800> demos<00:17:04.430> of<00:17:04.459> some<00:17:04.640> of 00:17:04.870 --> 00:17:04.880 align:start position:0% think we're gonna do demos of some of 00:17:04.880 --> 00:17:06.179 align:start position:0% think we're gonna do demos of some of the<00:17:04.939> language<00:17:05.240> tooling<00:17:05.600> that<00:17:05.630> we've<00:17:05.810> built 00:17:06.179 --> 00:17:06.189 align:start position:0% the language tooling that we've built 00:17:06.189 --> 00:17:11.140 align:start position:0% the language tooling that we've built Paul<00:17:07.189> are<00:17:07.610> you<00:17:07.850> up<00:17:08.089> first<00:17:09.880> obviously<00:17:10.880> one<00:17:11.120> of 00:17:11.140 --> 00:17:11.150 align:start position:0% Paul are you up first obviously one of 00:17:11.150 --> 00:17:13.929 align:start position:0% Paul are you up first obviously one of the<00:17:11.360> nice<00:17:11.750> things<00:17:12.020> we<00:17:12.199> get<00:17:12.380> with<00:17:12.920> the<00:17:13.550> e<00:17:13.579> azam 00:17:13.929 --> 00:17:13.939 align:start position:0% the nice things we get with the e azam 00:17:13.939 --> 00:17:15.550 align:start position:0% the nice things we get with the e azam tool<00:17:14.089> chain<00:17:14.329> is<00:17:14.569> the<00:17:14.810> ability<00:17:15.020> to<00:17:15.199> develop 00:17:15.550 --> 00:17:15.560 align:start position:0% tool chain is the ability to develop 00:17:15.560 --> 00:17:17.110 align:start position:0% tool chain is the ability to develop smart<00:17:15.980> contracts<00:17:16.370> and<00:17:16.550> a<00:17:16.579> whole<00:17:16.760> host<00:17:16.939> of 00:17:17.110 --> 00:17:17.120 align:start position:0% smart contracts and a whole host of 00:17:17.120 --> 00:17:18.699 align:start position:0% smart contracts and a whole host of different<00:17:17.390> programming<00:17:17.660> languages<00:17:17.959> Alex<00:17:18.439> a 00:17:18.699 --> 00:17:18.709 align:start position:0% different programming languages Alex a 00:17:18.709 --> 00:17:20.290 align:start position:0% different programming languages Alex a moment<00:17:19.160> ago<00:17:19.310> mentioned<00:17:19.760> some<00:17:19.910> of<00:17:19.939> them<00:17:20.120> these 00:17:20.290 --> 00:17:20.300 align:start position:0% moment ago mentioned some of them these 00:17:20.300 --> 00:17:23.140 align:start position:0% moment ago mentioned some of them these include<00:17:20.630> rust<00:17:20.900> C<00:17:21.470> C++<00:17:21.850> assembly<00:17:22.850> script 00:17:23.140 --> 00:17:23.150 align:start position:0% include rust C C++ assembly script 00:17:23.150 --> 00:17:24.910 align:start position:0% include rust C C++ assembly script you're<00:17:23.689> gonna<00:17:23.810> we're<00:17:24.110> gonna<00:17:24.199> do<00:17:24.410> quick<00:17:24.680> demos 00:17:24.910 --> 00:17:24.920 align:start position:0% you're gonna we're gonna do quick demos 00:17:24.920 --> 00:17:26.620 align:start position:0% you're gonna we're gonna do quick demos of<00:17:24.949> two<00:17:25.490> or<00:17:25.610> three<00:17:25.760> of<00:17:25.850> these<00:17:25.939> right<00:17:26.180> now<00:17:26.209> and 00:17:26.620 --> 00:17:26.630 align:start position:0% of two or three of these right now and 00:17:26.630 --> 00:17:30.340 align:start position:0% of two or three of these right now and as<00:17:27.140> a<00:17:27.170> first<00:17:27.730> framework<00:17:28.730> for<00:17:28.940> doing<00:17:29.030> that<00:17:29.350> we 00:17:30.340 --> 00:17:30.350 align:start position:0% as a first framework for doing that we 00:17:30.350 --> 00:17:31.840 align:start position:0% as a first framework for doing that we created<00:17:30.710> alex<00:17:31.220> created<00:17:31.550> something<00:17:31.730> called 00:17:31.840 --> 00:17:31.850 align:start position:0% created alex created something called 00:17:31.850 --> 00:17:34.210 align:start position:0% created alex created something called the<00:17:32.030> WRC<00:17:32.480> 20<00:17:33.020> challenge<00:17:33.440> the<00:17:33.590> w<00:17:33.890> refers<00:17:34.190> to 00:17:34.210 --> 00:17:34.220 align:start position:0% the WRC 20 challenge the w refers to 00:17:34.220 --> 00:17:36.700 align:start position:0% the WRC 20 challenge the w refers to wasum<00:17:34.700> and<00:17:34.970> it<00:17:35.240> was<00:17:35.330> just<00:17:35.570> a<00:17:35.720> challenge<00:17:36.440> that 00:17:36.700 --> 00:17:36.710 align:start position:0% wasum and it was just a challenge that 00:17:36.710 --> 00:17:37.870 align:start position:0% wasum and it was just a challenge that we<00:17:36.770> put<00:17:36.920> out<00:17:37.010> there<00:17:37.160> a<00:17:37.220> few<00:17:37.460> months<00:17:37.670> ago<00:17:37.760> to 00:17:37.870 --> 00:17:37.880 align:start position:0% we put out there a few months ago to 00:17:37.880 --> 00:17:42.610 align:start position:0% we put out there a few months ago to build<00:17:38.600> a<00:17:38.840> simple<00:17:39.280> ERC<00:17:40.280> 20<00:17:40.640> style<00:17:41.620> contract 00:17:42.610 --> 00:17:42.620 align:start position:0% build a simple ERC 20 style contract 00:17:42.620 --> 00:17:44.650 align:start position:0% build a simple ERC 20 style contract like<00:17:42.830> a<00:17:42.860> token<00:17:43.220> contract<00:17:43.670> using<00:17:43.970> the<00:17:44.330> various 00:17:44.650 --> 00:17:44.660 align:start position:0% like a token contract using the various 00:17:44.660 --> 00:17:46.390 align:start position:0% like a token contract using the various languages<00:17:45.170> we've<00:17:45.350> had<00:17:45.500> implementations<00:17:46.160> done 00:17:46.390 --> 00:17:46.400 align:start position:0% languages we've had implementations done 00:17:46.400 --> 00:17:48.940 align:start position:0% languages we've had implementations done in<00:17:46.550> eight<00:17:46.790> or<00:17:46.970> nine<00:17:47.150> languages<00:17:47.600> so<00:17:47.930> far 00:17:48.940 --> 00:17:48.950 align:start position:0% in eight or nine languages so far 00:17:48.950 --> 00:17:50.440 align:start position:0% in eight or nine languages so far I<00:17:48.980> think<00:17:49.670> you<00:17:49.730> can<00:17:49.850> find<00:17:50.000> this<00:17:50.120> in<00:17:50.240> our<00:17:50.330> github 00:17:50.440 --> 00:17:50.450 align:start position:0% I think you can find this in our github 00:17:50.450 --> 00:17:54.370 align:start position:0% I think you can find this in our github repository<00:17:51.370> github<00:17:52.370> dot<00:17:52.520> github.com<00:17:53.420> slash 00:17:54.370 --> 00:17:54.380 align:start position:0% repository github dot github.com slash 00:17:54.380 --> 00:17:55.690 align:start position:0% repository github dot github.com slash you<00:17:54.679> awesome<00:17:54.980> if<00:17:55.100> you're<00:17:55.280> interested<00:17:55.610> in 00:17:55.690 --> 00:17:55.700 align:start position:0% you awesome if you're interested in 00:17:55.700 --> 00:17:58.150 align:start position:0% you awesome if you're interested in contributing<00:17:56.179> one<00:17:56.480> and<00:17:56.750> Paul's<00:17:57.290> gonna<00:17:57.530> do<00:17:57.710> C 00:17:58.150 --> 00:17:58.160 align:start position:0% contributing one and Paul's gonna do C 00:17:58.160 --> 00:17:59.440 align:start position:0% contributing one and Paul's gonna do C C++<00:17:58.370> right<00:17:58.820> yes 00:17:59.440 --> 00:17:59.450 align:start position:0% C++ right yes 00:17:59.450 --> 00:18:06.880 align:start position:0% C++ right yes you<00:18:00.410> don't<00:18:00.950> like<00:18:03.760> right<00:18:04.809> yes<00:18:05.809> we<00:18:06.020> had<00:18:06.170> this<00:18:06.260> WRC 00:18:06.880 --> 00:18:06.890 align:start position:0% you don't like right yes we had this WRC 00:18:06.890 --> 00:18:09.580 align:start position:0% you don't like right yes we had this WRC twenty<00:18:07.190> challenge<00:18:07.640> to<00:18:08.510> implement<00:18:08.690> GRC<00:18:09.290> twenty 00:18:09.580 --> 00:18:09.590 align:start position:0% twenty challenge to implement GRC twenty 00:18:09.590 --> 00:18:12.940 align:start position:0% twenty challenge to implement GRC twenty and<00:18:09.850> I<00:18:10.850> wanted<00:18:11.270> to<00:18:11.390> implement<00:18:11.570> it<00:18:11.929> in<00:18:12.080> C<00:18:12.679> and 00:18:12.940 --> 00:18:12.950 align:start position:0% and I wanted to implement it in C and 00:18:12.950 --> 00:18:14.070 align:start position:0% and I wanted to implement it in C and C++ 00:18:14.070 --> 00:18:14.080 align:start position:0% C++ 00:18:14.080 --> 00:18:18.549 align:start position:0% C++ so<00:18:15.080> I<00:18:15.110> think<00:18:15.440> most<00:18:15.820> people<00:18:16.820> engineer<00:18:17.090> x'<00:18:17.559> many 00:18:18.549 --> 00:18:18.559 align:start position:0% so I think most people engineer x' many 00:18:18.559 --> 00:18:20.470 align:start position:0% so I think most people engineer x' many engineers<00:18:18.980> learn<00:18:19.190> C<00:18:19.460> as<00:18:19.670> an<00:18:19.820> undergrad<00:18:20.210> and 00:18:20.470 --> 00:18:20.480 align:start position:0% engineers learn C as an undergrad and 00:18:20.480 --> 00:18:24.610 align:start position:0% engineers learn C as an undergrad and seen<00:18:21.169> C++<00:18:21.890> is<00:18:22.100> as<00:18:22.460> ubiquitous<00:18:22.820> and<00:18:23.559> people<00:18:24.559> are 00:18:24.610 --> 00:18:24.620 align:start position:0% seen C++ is as ubiquitous and people are 00:18:24.620 --> 00:18:25.960 align:start position:0% seen C++ is as ubiquitous and people are talking<00:18:24.860> about<00:18:24.919> these<00:18:25.100> languages<00:18:25.520> like<00:18:25.669> rust 00:18:25.960 --> 00:18:25.970 align:start position:0% talking about these languages like rust 00:18:25.970 --> 00:18:28.360 align:start position:0% talking about these languages like rust and<00:18:26.330> assembly<00:18:27.049> script<00:18:27.350> but<00:18:27.590> I'm<00:18:27.890> sort<00:18:28.190> of 00:18:28.360 --> 00:18:28.370 align:start position:0% and assembly script but I'm sort of 00:18:28.370 --> 00:18:30.669 align:start position:0% and assembly script but I'm sort of naive<00:18:28.820> and<00:18:29.059> I<00:18:29.179> am<00:18:29.660> stuck<00:18:29.960> in<00:18:30.080> my<00:18:30.169> ways<00:18:30.200> and<00:18:30.380> I 00:18:30.669 --> 00:18:30.679 align:start position:0% naive and I am stuck in my ways and I 00:18:30.679 --> 00:18:33.669 align:start position:0% naive and I am stuck in my ways and I like<00:18:30.860> C<00:18:31.070> and<00:18:31.190> C++<00:18:31.480> so<00:18:32.480> that's<00:18:32.630> why<00:18:32.780> I<00:18:33.140> wrote<00:18:33.500> it 00:18:33.669 --> 00:18:33.679 align:start position:0% like C and C++ so that's why I wrote it 00:18:33.679 --> 00:18:40.409 align:start position:0% like C and C++ so that's why I wrote it in<00:18:33.770> C<00:18:33.950> or<00:18:33.980> C++<00:18:36.610> so<00:18:37.610> anyway<00:18:37.850> I<00:18:37.880> found<00:18:38.150> some 00:18:40.409 --> 00:18:40.419 align:start position:0% in C or C++ so anyway I found some 00:18:40.419 --> 00:18:43.930 align:start position:0% in C or C++ so anyway I found some anyway<00:18:41.419> this<00:18:41.540> is<00:18:41.660> just<00:18:41.840> the<00:18:41.900> gist<00:18:42.169> of<00:18:42.380> the<00:18:42.890> code 00:18:43.930 --> 00:18:43.940 align:start position:0% anyway this is just the gist of the code 00:18:43.940 --> 00:18:45.840 align:start position:0% anyway this is just the gist of the code [Music] 00:18:45.840 --> 00:18:45.850 align:start position:0% [Music] 00:18:45.850 --> 00:18:49.030 align:start position:0% [Music] boy<00:18:46.850> I<00:18:46.910> don't<00:18:47.179> know<00:18:47.470> some<00:18:48.470> reverse<00:18:48.740> bytes 00:18:49.030 --> 00:18:49.040 align:start position:0% boy I don't know some reverse bytes 00:18:49.040 --> 00:18:51.460 align:start position:0% boy I don't know some reverse bytes stuff<00:18:49.460> and<00:18:49.820> I<00:18:50.090> wasn't<00:18:50.690> really<00:18:50.870> I<00:18:51.200> don't<00:18:51.410> know 00:18:51.460 --> 00:18:51.470 align:start position:0% stuff and I wasn't really I don't know 00:18:51.470 --> 00:18:53.049 align:start position:0% stuff and I wasn't really I don't know what<00:18:51.620> to<00:18:51.799> really<00:18:51.950> say<00:18:52.040> we<00:18:52.490> we<00:18:52.790> have<00:18:52.910> some 00:18:53.049 --> 00:18:53.059 align:start position:0% what to really say we we have some 00:18:53.059 --> 00:18:54.580 align:start position:0% what to really say we we have some functions<00:18:53.450> that<00:18:53.510> we<00:18:53.690> were<00:18:53.780> to<00:18:53.929> implement<00:18:54.020> and 00:18:54.580 --> 00:18:54.590 align:start position:0% functions that we were to implement and 00:18:54.590 --> 00:18:59.380 align:start position:0% functions that we were to implement and I<00:18:54.860> implemented<00:18:55.340> them<00:18:55.490> and<00:18:55.900> this<00:18:56.900> is<00:18:56.960> how<00:18:58.390> it's 00:18:59.380 --> 00:18:59.390 align:start position:0% I implemented them and this is how it's 00:18:59.390 --> 00:19:00.789 align:start position:0% I implemented them and this is how it's it's<00:18:59.630> like<00:18:59.720> I<00:18:59.840> know<00:18:59.900> this<00:19:00.169> is<00:19:00.320> like<00:19:00.470> you<00:19:00.650> know<00:19:00.770> a 00:19:00.789 --> 00:19:00.799 align:start position:0% it's like I know this is like you know a 00:19:00.799 --> 00:19:02.950 align:start position:0% it's like I know this is like you know a lot<00:19:01.700> to<00:19:02.030> just<00:19:02.240> you<00:19:02.510> know<00:19:02.600> I<00:19:02.660> don't<00:19:02.780> know<00:19:02.840> how 00:19:02.950 --> 00:19:02.960 align:start position:0% lot to just you know I don't know how 00:19:02.960 --> 00:19:04.060 align:start position:0% lot to just you know I don't know how I'm<00:19:03.049> supposed<00:19:03.140> to<00:19:03.320> explain<00:19:03.650> this<00:19:03.740> in<00:19:03.890> five 00:19:04.060 --> 00:19:04.070 align:start position:0% I'm supposed to explain this in five 00:19:04.070 --> 00:19:06.909 align:start position:0% I'm supposed to explain this in five minutes<00:19:04.429> but<00:19:04.610> anyway<00:19:05.590> anyway<00:19:06.590> this<00:19:06.710> is<00:19:06.830> the 00:19:06.909 --> 00:19:06.919 align:start position:0% minutes but anyway anyway this is the 00:19:06.919 --> 00:19:08.650 align:start position:0% minutes but anyway anyway this is the smart<00:19:07.160> contract<00:19:07.340> and<00:19:07.730> C<00:19:07.910> and<00:19:08.030> C<00:19:08.210> for<00:19:08.450> is 00:19:08.650 --> 00:19:08.660 align:start position:0% smart contract and C and C for is 00:19:08.660 --> 00:19:10.840 align:start position:0% smart contract and C and C for is similar<00:19:09.080> for<00:19:09.620> C++<00:19:10.220> and<00:19:10.429> we're<00:19:10.520> hoping<00:19:10.790> that 00:19:10.840 --> 00:19:10.850 align:start position:0% similar for C++ and we're hoping that 00:19:10.850 --> 00:19:13.060 align:start position:0% similar for C++ and we're hoping that you<00:19:11.179> know<00:19:11.230> if<00:19:12.230> we're<00:19:12.380> gonna<00:19:12.440> on<00:19:12.650> board<00:19:12.919> you 00:19:13.060 --> 00:19:13.070 align:start position:0% you know if we're gonna on board you 00:19:13.070 --> 00:19:14.680 align:start position:0% you know if we're gonna on board you know<00:19:13.160> hundreds<00:19:13.520> of<00:19:13.549> thousands<00:19:13.970> millions<00:19:14.419> of 00:19:14.680 --> 00:19:14.690 align:start position:0% know hundreds of thousands millions of 00:19:14.690 --> 00:19:16.690 align:start position:0% know hundreds of thousands millions of people<00:19:14.750> you<00:19:15.410> know<00:19:15.500> a<00:19:15.530> lot<00:19:15.799> of<00:19:15.830> seen<00:19:16.100> C++ 00:19:16.690 --> 00:19:16.700 align:start position:0% people you know a lot of seen C++ 00:19:16.700 --> 00:19:19.060 align:start position:0% people you know a lot of seen C++ programmers<00:19:17.270> might<00:19:18.110> want<00:19:18.290> to<00:19:18.320> write<00:19:18.740> smart 00:19:19.060 --> 00:19:19.070 align:start position:0% programmers might want to write smart 00:19:19.070 --> 00:19:21.580 align:start position:0% programmers might want to write smart contracts<00:19:19.460> too<00:19:19.640> so<00:19:19.990> maybe<00:19:20.990> we<00:19:21.200> should<00:19:21.230> give 00:19:21.580 --> 00:19:21.590 align:start position:0% contracts too so maybe we should give 00:19:21.590 --> 00:19:22.570 align:start position:0% contracts too so maybe we should give them<00:19:21.710> tools<00:19:22.010> to<00:19:22.190> do<00:19:22.309> it 00:19:22.570 --> 00:19:22.580 align:start position:0% them tools to do it 00:19:22.580 --> 00:19:26.250 align:start position:0% them tools to do it and<00:19:23.440> some<00:19:24.440> make<00:19:24.830> stuff<00:19:25.070> so<00:19:25.340> I'm<00:19:25.429> using<00:19:25.580> this 00:19:26.250 --> 00:19:26.260 align:start position:0% and some make stuff so I'm using this 00:19:26.260 --> 00:19:30.250 align:start position:0% and some make stuff so I'm using this some<00:19:27.260> LLVM<00:19:28.040> back-end<00:19:28.669> but<00:19:29.090> there<00:19:30.049> are<00:19:30.140> some 00:19:30.250 --> 00:19:30.260 align:start position:0% some LLVM back-end but there are some 00:19:30.260 --> 00:19:32.350 align:start position:0% some LLVM back-end but there are some problems<00:19:30.740> the<00:19:30.860> toolings<00:19:31.250> are<00:19:31.400> the<00:19:32.120> tools 00:19:32.350 --> 00:19:32.360 align:start position:0% problems the toolings are the tools 00:19:32.360 --> 00:19:33.760 align:start position:0% problems the toolings are the tools aren't<00:19:32.570> ready<00:19:32.809> yet 00:19:33.760 --> 00:19:33.770 align:start position:0% aren't ready yet 00:19:33.770 --> 00:19:36.630 align:start position:0% aren't ready yet but<00:19:34.309> there<00:19:34.460> are<00:19:34.549> some<00:19:34.700> people<00:19:34.820> writing<00:19:35.150> tools 00:19:36.630 --> 00:19:36.640 align:start position:0% but there are some people writing tools 00:19:36.640 --> 00:19:39.110 align:start position:0% but there are some people writing tools to<00:19:37.570> do<00:19:37.690> this<00:19:37.840> kind<00:19:38.020> of<00:19:38.050> thing<00:19:38.200> lien<00:19:38.620> can<00:19:38.980> you 00:19:39.110 --> 00:19:39.120 align:start position:0% to do this kind of thing lien can you 00:19:39.120 --> 00:19:42.000 align:start position:0% to do this kind of thing lien can you come<00:19:40.120> and<00:19:40.720> also<00:19:41.170> I<00:19:41.200> wanted<00:19:41.410> to<00:19:41.500> show<00:19:41.590> another 00:19:42.000 --> 00:19:42.010 align:start position:0% come and also I wanted to show another 00:19:42.010 --> 00:19:48.540 align:start position:0% come and also I wanted to show another implementation<00:19:42.310> of<00:19:42.940> WRC<00:19:43.600> 20<00:19:46.560> I'm<00:19:47.560> not<00:19:48.070> a<00:19:48.100> MEK 00:19:48.540 --> 00:19:48.550 align:start position:0% implementation of WRC 20 I'm not a MEK 00:19:48.550 --> 00:19:57.290 align:start position:0% implementation of WRC 20 I'm not a MEK person<00:19:49.030> that's<00:19:49.180> why<00:19:55.620> okay<00:19:56.620> so<00:19:56.650> if<00:19:56.950> you<00:19:57.070> don't 00:19:57.290 --> 00:19:57.300 align:start position:0% person that's why okay so if you don't 00:19:57.300 --> 00:20:00.030 align:start position:0% person that's why okay so if you don't so<00:19:58.300> see<00:19:58.480> is<00:19:58.600> one<00:19:58.780> option<00:19:58.960> C++<00:19:59.560> is<00:19:59.680> one<00:19:59.890> option 00:20:00.030 --> 00:20:00.040 align:start position:0% so see is one option C++ is one option 00:20:00.040 --> 00:20:02.270 align:start position:0% so see is one option C++ is one option but<00:20:00.460> if<00:20:00.550> you<00:20:00.640> want<00:20:00.790> to<00:20:00.850> handwrite<00:20:01.270> it<00:20:01.300> in<00:20:01.630> in 00:20:02.270 --> 00:20:02.280 align:start position:0% but if you want to handwrite it in in 00:20:02.280 --> 00:20:04.380 align:start position:0% but if you want to handwrite it in in webassembly<00:20:03.280> you<00:20:03.520> can<00:20:03.670> do<00:20:03.790> this<00:20:03.970> so<00:20:04.180> this<00:20:04.330> is 00:20:04.380 --> 00:20:04.390 align:start position:0% webassembly you can do this so this is 00:20:04.390 --> 00:20:06.540 align:start position:0% webassembly you can do this so this is my<00:20:04.680> version<00:20:05.680> and<00:20:05.950> I<00:20:05.980> think<00:20:06.190> this<00:20:06.310> is<00:20:06.430> the 00:20:06.540 --> 00:20:06.550 align:start position:0% my version and I think this is the 00:20:06.550 --> 00:20:09.390 align:start position:0% my version and I think this is the shortest<00:20:06.880> version<00:20:07.270> of<00:20:07.390> the<00:20:07.510> WRC<00:20:07.870> 20<00:20:08.350> the<00:20:09.280> most 00:20:09.390 --> 00:20:09.400 align:start position:0% shortest version of the WRC 20 the most 00:20:09.400 --> 00:20:10.770 align:start position:0% shortest version of the WRC 20 the most efficient<00:20:09.910> one<00:20:10.090> and<00:20:10.300> if<00:20:10.360> you're<00:20:10.450> going<00:20:10.540> to<00:20:10.630> use 00:20:10.770 --> 00:20:10.780 align:start position:0% efficient one and if you're going to use 00:20:10.780 --> 00:20:12.750 align:start position:0% efficient one and if you're going to use it<00:20:10.990> this<00:20:11.170> might<00:20:11.380> be<00:20:11.530> the<00:20:12.220> best<00:20:12.370> one<00:20:12.550> it's<00:20:12.730> like 00:20:12.750 --> 00:20:12.760 align:start position:0% it this might be the best one it's like 00:20:12.760 --> 00:20:14.940 align:start position:0% it this might be the best one it's like a<00:20:12.850> hundred<00:20:13.300> eighty<00:20:13.960> lines<00:20:14.230> of<00:20:14.410> what<00:20:14.560> assembly 00:20:14.940 --> 00:20:14.950 align:start position:0% a hundred eighty lines of what assembly 00:20:14.950 --> 00:20:20.130 align:start position:0% a hundred eighty lines of what assembly code<00:20:16.920> no<00:20:17.920> but<00:20:18.430> I<00:20:18.700> did<00:20:19.180> have<00:20:19.330> test<00:20:19.570> cases<00:20:19.660> in<00:20:20.080> the 00:20:20.130 --> 00:20:20.140 align:start position:0% code no but I did have test cases in the 00:20:20.140 --> 00:20:26.340 align:start position:0% code no but I did have test cases in the past<00:20:20.290> the<00:20:20.470> test<00:20:20.680> cases<00:20:24.930> yeah<00:20:25.930> so<00:20:26.080> maybe<00:20:26.230> I 00:20:26.340 --> 00:20:26.350 align:start position:0% past the test cases yeah so maybe I 00:20:26.350 --> 00:20:28.310 align:start position:0% past the test cases yeah so maybe I don't<00:20:26.470> know<00:20:26.650> maybe<00:20:26.950> you<00:20:27.040> won't<00:20:27.160> trust<00:20:27.460> it<00:20:27.640> but 00:20:28.310 --> 00:20:28.320 align:start position:0% don't know maybe you won't trust it but 00:20:28.320 --> 00:20:38.360 align:start position:0% don't know maybe you won't trust it but 180<00:20:29.320> lines<00:20:29.560> isn't<00:20:29.830> beg<00:20:30.460> your<00:20:30.580> pardon<00:20:31.200> okay 00:20:38.360 --> 00:20:38.370 align:start position:0% 00:20:38.370 --> 00:20:40.680 align:start position:0% right<00:20:39.370> so<00:20:39.550> we<00:20:39.640> have<00:20:39.760> a<00:20:39.790> WRC<00:20:40.300> 20<00:20:40.570> examples 00:20:40.680 --> 00:20:40.690 align:start position:0% right so we have a WRC 20 examples 00:20:40.690 --> 00:20:43.650 align:start position:0% right so we have a WRC 20 examples repository<00:20:41.590> here<00:20:41.920> it's<00:20:42.240> you<00:20:43.240> awesome<00:20:43.510> slash 00:20:43.650 --> 00:20:43.660 align:start position:0% repository here it's you awesome slash 00:20:43.660 --> 00:20:48.540 align:start position:0% repository here it's you awesome slash WRC<00:20:44.050> 20<00:20:44.290> examples<00:20:46.560> and<00:20:47.560> right<00:20:48.220> now<00:20:48.340> there's<00:20:48.490> an 00:20:48.540 --> 00:20:48.550 align:start position:0% WRC 20 examples and right now there's an 00:20:48.550 --> 00:20:50.490 align:start position:0% WRC 20 examples and right now there's an issue<00:20:48.700> open<00:20:49.030> and<00:20:49.360> you<00:20:49.420> can<00:20:49.540> see<00:20:49.690> I<00:20:49.960> think<00:20:49.990> most 00:20:50.490 --> 00:20:50.500 align:start position:0% issue open and you can see I think most 00:20:50.500 --> 00:20:51.750 align:start position:0% issue open and you can see I think most of<00:20:50.590> them<00:20:50.680> are<00:20:50.740> listed<00:20:51.040> here<00:20:51.070> so<00:20:51.340> we<00:20:51.430> have<00:20:51.550> rust 00:20:51.750 --> 00:20:51.760 align:start position:0% of them are listed here so we have rust 00:20:51.760 --> 00:20:53.760 align:start position:0% of them are listed here so we have rust we<00:20:52.030> have<00:20:52.260> assembly<00:20:53.260> script<00:20:53.470> which<00:20:53.560> I'll<00:20:53.650> show 00:20:53.760 --> 00:20:53.770 align:start position:0% we have assembly script which I'll show 00:20:53.770 --> 00:20:55.290 align:start position:0% we have assembly script which I'll show you<00:20:53.800> in<00:20:53.890> a<00:20:54.010> sec<00:20:54.160> we<00:20:54.280> have<00:20:54.400> NIM<00:20:54.640> which<00:20:55.000> is<00:20:55.120> very 00:20:55.290 --> 00:20:55.300 align:start position:0% you in a sec we have NIM which is very 00:20:55.300 --> 00:20:58.400 align:start position:0% you in a sec we have NIM which is very cool<00:20:55.450> c<00:20:55.750> c++<00:20:56.170> handwritten<00:20:56.950> web<00:20:57.130> assembly 00:20:58.400 --> 00:20:58.410 align:start position:0% cool c c++ handwritten web assembly 00:20:58.410 --> 00:21:00.210 align:start position:0% cool c c++ handwritten web assembly think<00:20:59.410> there<00:20:59.500> may<00:20:59.560> be<00:20:59.590> a<00:20:59.680> couple<00:20:59.860> of<00:20:59.920> others<00:21:00.130> as 00:21:00.210 --> 00:21:00.220 align:start position:0% think there may be a couple of others as 00:21:00.220 --> 00:21:07.000 align:start position:0% think there may be a couple of others as well<00:21:04.140> thanks<00:21:05.140> Paul 00:21:07.000 --> 00:21:07.010 align:start position:0% well thanks Paul 00:21:07.010 --> 00:21:09.500 align:start position:0% well thanks Paul [Music] 00:21:09.500 --> 00:21:09.510 align:start position:0% [Music] 00:21:09.510 --> 00:21:12.030 align:start position:0% [Music] alright<00:21:10.510> I'm<00:21:10.690> gonna<00:21:10.810> show<00:21:11.140> you<00:21:11.200> guys<00:21:11.350> what<00:21:11.950> the 00:21:12.030 --> 00:21:12.040 align:start position:0% alright I'm gonna show you guys what the 00:21:12.040 --> 00:21:14.190 align:start position:0% alright I'm gonna show you guys what the assembly<00:21:12.370> script<00:21:12.610> 1<00:21:12.730> looks<00:21:12.910> like<00:21:12.970> now<00:21:13.300> so<00:21:14.170> I 00:21:14.190 --> 00:21:14.200 align:start position:0% assembly script 1 looks like now so I 00:21:14.200 --> 00:21:15.330 align:start position:0% assembly script 1 looks like now so I initially<00:21:14.560> came<00:21:14.590> up<00:21:14.830> with<00:21:14.920> a<00:21:14.950> really<00:21:15.160> clever 00:21:15.330 --> 00:21:15.340 align:start position:0% initially came up with a really clever 00:21:15.340 --> 00:21:18.120 align:start position:0% initially came up with a really clever name<00:21:15.940> for<00:21:16.180> this<00:21:16.240> talk<00:21:16.510> smart<00:21:17.320> contracts<00:21:17.950> in 00:21:18.120 --> 00:21:18.130 align:start position:0% name for this talk smart contracts in 00:21:18.130 --> 00:21:22.080 align:start position:0% name for this talk smart contracts in JavaScript<00:21:18.670> no<00:21:19.300> really<00:21:19.780> almost<00:21:21.000> let<00:21:22.000> me 00:21:22.080 --> 00:21:22.090 align:start position:0% JavaScript no really almost let me 00:21:22.090 --> 00:21:25.230 align:start position:0% JavaScript no really almost let me explain<00:21:22.330> what<00:21:22.510> I<00:21:22.540> mean<00:21:22.600> by<00:21:22.750> that<00:21:23.820> so<00:21:24.820> first 00:21:25.230 --> 00:21:25.240 align:start position:0% explain what I mean by that so first 00:21:25.240 --> 00:21:27.660 align:start position:0% explain what I mean by that so first what<00:21:25.660> is<00:21:25.690> webOS<00:21:26.530> I'm<00:21:26.680> sorry<00:21:26.980> what<00:21:27.070> is<00:21:27.100> assembly 00:21:27.660 --> 00:21:27.670 align:start position:0% what is webOS I'm sorry what is assembly 00:21:27.670 --> 00:21:30.840 align:start position:0% what is webOS I'm sorry what is assembly script<00:21:27.970> so<00:21:28.120> assembly<00:21:28.510> script<00:21:28.840> is<00:21:29.020> a<00:21:29.820> subset<00:21:30.820> of 00:21:30.840 --> 00:21:30.850 align:start position:0% script so assembly script is a subset of 00:21:30.850 --> 00:21:32.640 align:start position:0% script so assembly script is a subset of typescript<00:21:31.390> which<00:21:31.930> I'm<00:21:32.050> sure<00:21:32.170> many<00:21:32.320> of<00:21:32.500> you 00:21:32.640 --> 00:21:32.650 align:start position:0% typescript which I'm sure many of you 00:21:32.650 --> 00:21:35.100 align:start position:0% typescript which I'm sure many of you are<00:21:32.890> familiar<00:21:33.010> with<00:21:33.310> right<00:21:33.700> type<00:21:34.110> typescript 00:21:35.100 --> 00:21:35.110 align:start position:0% are familiar with right type typescript 00:21:35.110 --> 00:21:37.770 align:start position:0% are familiar with right type typescript is<00:21:35.230> a<00:21:35.670> strictly<00:21:36.670> typed<00:21:36.970> superset<00:21:37.750> of 00:21:37.770 --> 00:21:37.780 align:start position:0% is a strictly typed superset of 00:21:37.780 --> 00:21:40.020 align:start position:0% is a strictly typed superset of JavaScript<00:21:37.930> and<00:21:38.680> types<00:21:39.490> are<00:21:39.640> good<00:21:39.790> for<00:21:39.970> a 00:21:40.020 --> 00:21:40.030 align:start position:0% JavaScript and types are good for a 00:21:40.030 --> 00:21:41.460 align:start position:0% JavaScript and types are good for a whole<00:21:40.180> host<00:21:40.420> of<00:21:40.540> reasons<00:21:40.720> we<00:21:41.020> believe<00:21:41.260> they 00:21:41.460 --> 00:21:41.470 align:start position:0% whole host of reasons we believe they 00:21:41.470 --> 00:21:44.190 align:start position:0% whole host of reasons we believe they produce<00:21:41.680> better<00:21:41.950> code<00:21:42.960> it's<00:21:43.960> a<00:21:44.020> better 00:21:44.190 --> 00:21:44.200 align:start position:0% produce better code it's a better 00:21:44.200 --> 00:21:45.510 align:start position:0% produce better code it's a better programming<00:21:44.650> paradigm<00:21:45.010> and<00:21:45.310> in<00:21:45.400> particular 00:21:45.510 --> 00:21:45.520 align:start position:0% programming paradigm and in particular 00:21:45.520 --> 00:21:47.340 align:start position:0% programming paradigm and in particular in<00:21:46.090> sort<00:21:46.600> of<00:21:46.660> mission-critical<00:21:47.050> applications 00:21:47.340 --> 00:21:47.350 align:start position:0% in sort of mission-critical applications 00:21:47.350 --> 00:21:50.460 align:start position:0% in sort of mission-critical applications like<00:21:48.010> we're<00:21:48.280> writing<00:21:48.550> on<00:21:48.640> aetherium<00:21:49.260> we<00:21:50.260> think 00:21:50.460 --> 00:21:50.470 align:start position:0% like we're writing on aetherium we think 00:21:50.470 --> 00:21:52.950 align:start position:0% like we're writing on aetherium we think the<00:21:50.679> types<00:21:50.890> go<00:21:51.039> a<00:21:51.070> long<00:21:51.250> way<00:21:51.370> -<00:21:51.970> like<00:21:52.720> I<00:21:52.750> said 00:21:52.950 --> 00:21:52.960 align:start position:0% the types go a long way - like I said 00:21:52.960 --> 00:21:54.659 align:start position:0% the types go a long way - like I said writing<00:21:53.140> better<00:21:53.350> more<00:21:53.770> secure<00:21:54.039> better 00:21:54.659 --> 00:21:54.669 align:start position:0% writing better more secure better 00:21:54.669 --> 00:21:57.149 align:start position:0% writing better more secure better performant<00:21:55.179> code<00:21:55.419> as<00:21:55.630> well<00:21:55.840> and<00:21:56.799> on<00:21:56.980> top<00:21:57.130> of 00:21:57.149 --> 00:21:57.159 align:start position:0% performant code as well and on top of 00:21:57.159 --> 00:21:59.370 align:start position:0% performant code as well and on top of all<00:21:57.309> that<00:21:57.340> of<00:21:57.640> course<00:21:57.690> webassembly<00:21:58.690> itself<00:21:59.140> is 00:21:59.370 --> 00:21:59.380 align:start position:0% all that of course webassembly itself is 00:21:59.380 --> 00:22:02.250 align:start position:0% all that of course webassembly itself is strictly<00:21:59.650> typed<00:21:59.890> so<00:22:00.570> yeah<00:22:01.570> so<00:22:01.780> so<00:22:02.049> there's<00:22:02.200> a 00:22:02.250 --> 00:22:02.260 align:start position:0% strictly typed so yeah so so there's a 00:22:02.260 --> 00:22:03.990 align:start position:0% strictly typed so yeah so so there's a really<00:22:02.559> cool<00:22:02.710> project<00:22:02.980> called<00:22:03.789> assembly 00:22:03.990 --> 00:22:04.000 align:start position:0% really cool project called assembly 00:22:04.000 --> 00:22:09.149 align:start position:0% really cool project called assembly script<00:22:04.679> which<00:22:05.679> allows<00:22:06.610> you<00:22:06.789> to<00:22:06.940> write<00:22:07.740> in<00:22:08.740> a 00:22:09.149 --> 00:22:09.159 align:start position:0% script which allows you to write in a 00:22:09.159 --> 00:22:10.529 align:start position:0% script which allows you to write in a language<00:22:09.460> which<00:22:09.640> looks<00:22:09.880> and<00:22:10.059> feels<00:22:10.240> a<00:22:10.419> lot 00:22:10.529 --> 00:22:10.539 align:start position:0% language which looks and feels a lot 00:22:10.539 --> 00:22:12.390 align:start position:0% language which looks and feels a lot like<00:22:10.780> JavaScript<00:22:11.350> or<00:22:11.470> of<00:22:11.770> course<00:22:11.919> typescript 00:22:12.390 --> 00:22:12.400 align:start position:0% like JavaScript or of course typescript 00:22:12.400 --> 00:22:13.860 align:start position:0% like JavaScript or of course typescript if<00:22:12.520> you've<00:22:12.669> used<00:22:12.820> it<00:22:13.030> and<00:22:13.210> compiled<00:22:13.510> that<00:22:13.690> down 00:22:13.860 --> 00:22:13.870 align:start position:0% if you've used it and compiled that down 00:22:13.870 --> 00:22:17.130 align:start position:0% if you've used it and compiled that down to<00:22:14.230> web<00:22:14.650> assembly<00:22:15.059> and<00:22:16.059> so<00:22:16.240> sort<00:22:16.600> of<00:22:16.659> from<00:22:16.929> my 00:22:17.130 --> 00:22:17.140 align:start position:0% to web assembly and so sort of from my 00:22:17.140 --> 00:22:19.560 align:start position:0% to web assembly and so sort of from my perspective<00:22:17.470> I<00:22:18.070> have<00:22:18.789> nothing<00:22:19.210> against 00:22:19.560 --> 00:22:19.570 align:start position:0% perspective I have nothing against 00:22:19.570 --> 00:22:21.840 align:start position:0% perspective I have nothing against domain-specific<00:22:20.350> languages<00:22:21.159> like<00:22:21.429> solidity 00:22:21.840 --> 00:22:21.850 align:start position:0% domain-specific languages like solidity 00:22:21.850 --> 00:22:23.310 align:start position:0% domain-specific languages like solidity and<00:22:22.059> Viper<00:22:22.270> and<00:22:22.539> all<00:22:22.600> the<00:22:22.690> other<00:22:22.809> great<00:22:22.960> ones<00:22:23.110> I 00:22:23.310 --> 00:22:23.320 align:start position:0% and Viper and all the other great ones I 00:22:23.320 --> 00:22:24.899 align:start position:0% and Viper and all the other great ones I think<00:22:23.500> that<00:22:23.650> they're<00:22:24.309> very<00:22:24.490> important 00:22:24.899 --> 00:22:24.909 align:start position:0% think that they're very important 00:22:24.909 --> 00:22:26.460 align:start position:0% think that they're very important they've<00:22:25.330> gotten<00:22:25.600> us<00:22:25.720> quite<00:22:25.929> far<00:22:26.140> and<00:22:26.380> they'll 00:22:26.460 --> 00:22:26.470 align:start position:0% they've gotten us quite far and they'll 00:22:26.470 --> 00:22:29.159 align:start position:0% they've gotten us quite far and they'll sort<00:22:26.650> of<00:22:26.770> have<00:22:27.010> a<00:22:27.520> role<00:22:27.940> in<00:22:28.210> the<00:22:28.870> etherium 00:22:29.159 --> 00:22:29.169 align:start position:0% sort of have a role in the etherium 00:22:29.169 --> 00:22:31.289 align:start position:0% sort of have a role in the etherium ecosystem<00:22:29.620> for<00:22:29.799> some<00:22:29.919> time<00:22:30.100> to<00:22:30.250> come<00:22:30.299> however 00:22:31.289 --> 00:22:31.299 align:start position:0% ecosystem for some time to come however 00:22:31.299 --> 00:22:34.380 align:start position:0% ecosystem for some time to come however my<00:22:32.169> personal<00:22:32.710> sort<00:22:33.340> of<00:22:33.429> goal<00:22:33.820> for<00:22:34.120> aetherium 00:22:34.380 --> 00:22:34.390 align:start position:0% my personal sort of goal for aetherium 00:22:34.390 --> 00:22:36.029 align:start position:0% my personal sort of goal for aetherium is<00:22:34.630> I<00:22:34.720> want<00:22:34.900> to<00:22:34.929> see<00:22:35.110> millions<00:22:35.530> of<00:22:35.740> people 00:22:36.029 --> 00:22:36.039 align:start position:0% is I want to see millions of people 00:22:36.039 --> 00:22:38.690 align:start position:0% is I want to see millions of people developing<00:22:36.580> applications<00:22:37.240> on<00:22:37.360> aetherium<00:22:37.659> and 00:22:38.690 --> 00:22:38.700 align:start position:0% developing applications on aetherium and 00:22:38.700 --> 00:22:40.830 align:start position:0% developing applications on aetherium and personally<00:22:39.700> I<00:22:39.760> don't<00:22:39.970> believe<00:22:40.210> that<00:22:40.240> way<00:22:40.539> the 00:22:40.830 --> 00:22:40.840 align:start position:0% personally I don't believe that way the 00:22:40.840 --> 00:22:44.120 align:start position:0% personally I don't believe that way the way<00:22:40.960> we<00:22:41.110> get<00:22:41.289> there<00:22:41.500> is<00:22:41.740> is<00:22:42.640> by<00:22:43.090> requiring 00:22:44.120 --> 00:22:44.130 align:start position:0% way we get there is is by requiring 00:22:44.130 --> 00:22:46.590 align:start position:0% way we get there is is by requiring people<00:22:45.130> to<00:22:45.280> learn<00:22:45.460> brand-new<00:22:46.240> programming 00:22:46.590 --> 00:22:46.600 align:start position:0% people to learn brand-new programming 00:22:46.600 --> 00:22:48.120 align:start position:0% people to learn brand-new programming languages<00:22:47.020> and<00:22:47.289> brand-new<00:22:47.740> programming 00:22:48.120 --> 00:22:48.130 align:start position:0% languages and brand-new programming 00:22:48.130 --> 00:22:50.039 align:start position:0% languages and brand-new programming paradigms<00:22:48.520> from<00:22:48.730> scratch<00:22:49.000> right<00:22:49.450> let<00:22:49.929> me<00:22:49.990> just 00:22:50.039 --> 00:22:50.049 align:start position:0% paradigms from scratch right let me just 00:22:50.049 --> 00:22:51.750 align:start position:0% paradigms from scratch right let me just go<00:22:50.260> over<00:22:50.380> this<00:22:50.530> point<00:22:50.919> one<00:22:51.190> more<00:22:51.340> time<00:22:51.520> because 00:22:51.750 --> 00:22:51.760 align:start position:0% go over this point one more time because 00:22:51.760 --> 00:22:53.610 align:start position:0% go over this point one more time because I<00:22:51.820> think<00:22:51.880> it's<00:22:52.090> important<00:22:52.510> there's<00:22:53.140> a<00:22:53.230> huge 00:22:53.610 --> 00:22:53.620 align:start position:0% I think it's important there's a huge 00:22:53.620 --> 00:22:55.409 align:start position:0% I think it's important there's a huge advantage<00:22:54.100> to<00:22:54.429> doing<00:22:54.580> that<00:22:54.789> right<00:22:55.150> if<00:22:55.299> you're 00:22:55.409 --> 00:22:55.419 align:start position:0% advantage to doing that right if you're 00:22:55.419 --> 00:22:57.360 align:start position:0% advantage to doing that right if you're writing<00:22:55.720> mission-critical<00:22:56.710> code<00:22:57.130> if<00:22:57.280> you're 00:22:57.360 --> 00:22:57.370 align:start position:0% writing mission-critical code if you're 00:22:57.370 --> 00:22:58.980 align:start position:0% writing mission-critical code if you're writing<00:22:57.549> a<00:22:57.700> piece<00:22:57.850> of<00:22:57.970> wallet<00:22:58.240> software<00:22:58.630> by 00:22:58.980 --> 00:22:58.990 align:start position:0% writing a piece of wallet software by 00:22:58.990 --> 00:23:01.260 align:start position:0% writing a piece of wallet software by all<00:22:59.169> means<00:22:59.380> do<00:22:59.740> it<00:22:59.770> in<00:22:59.950> solidity<00:23:00.280> do<00:23:01.090> it<00:23:01.179> in 00:23:01.260 --> 00:23:01.270 align:start position:0% all means do it in solidity do it in 00:23:01.270 --> 00:23:04.529 align:start position:0% all means do it in solidity do it in Viper<00:23:01.450> learn<00:23:02.260> EVM<00:23:02.970> get<00:23:03.970> that<00:23:04.090> code<00:23:04.240> audited 00:23:04.529 --> 00:23:04.539 align:start position:0% Viper learn EVM get that code audited 00:23:04.539 --> 00:23:06.149 align:start position:0% Viper learn EVM get that code audited right<00:23:05.020> I<00:23:05.049> don't<00:23:05.230> want<00:23:05.500> that<00:23:05.650> process<00:23:06.039> to 00:23:06.149 --> 00:23:06.159 align:start position:0% right I don't want that process to 00:23:06.159 --> 00:23:07.620 align:start position:0% right I don't want that process to change<00:23:06.370> but<00:23:07.030> if<00:23:07.120> you're<00:23:07.210> building<00:23:07.390> something 00:23:07.620 --> 00:23:07.630 align:start position:0% change but if you're building something 00:23:07.630 --> 00:23:09.510 align:start position:0% change but if you're building something for<00:23:08.140> fun<00:23:08.350> right<00:23:08.710> if<00:23:08.830> you're<00:23:08.980> building<00:23:09.100> a<00:23:09.309> toy 00:23:09.510 --> 00:23:09.520 align:start position:0% for fun right if you're building a toy 00:23:09.520 --> 00:23:10.860 align:start position:0% for fun right if you're building a toy if<00:23:09.760> you're<00:23:09.909> hacking<00:23:10.150> at<00:23:10.240> a<00:23:10.270> hackathon<00:23:10.570> I 00:23:10.860 --> 00:23:10.870 align:start position:0% if you're hacking at a hackathon I 00:23:10.870 --> 00:23:13.169 align:start position:0% if you're hacking at a hackathon I really<00:23:11.260> think<00:23:11.470> that<00:23:11.530> having<00:23:12.250> something<00:23:12.850> that 00:23:13.169 --> 00:23:13.179 align:start position:0% really think that having something that 00:23:13.179 --> 00:23:14.580 align:start position:0% really think that having something that as<00:23:13.299> I<00:23:13.390> said<00:23:13.450> looks<00:23:13.870> and<00:23:14.140> feels<00:23:14.380> like 00:23:14.580 --> 00:23:14.590 align:start position:0% as I said looks and feels like 00:23:14.590 --> 00:23:18.000 align:start position:0% as I said looks and feels like JavaScript<00:23:15.159> and<00:23:15.510> uses<00:23:16.679> existing<00:23:17.679> JavaScript 00:23:18.000 --> 00:23:18.010 align:start position:0% JavaScript and uses existing JavaScript 00:23:18.010 --> 00:23:21.110 align:start position:0% JavaScript and uses existing JavaScript tooling<00:23:18.580> tools<00:23:18.850> like<00:23:19.000> nvm<00:23:19.419> and<00:23:19.630> yarn<00:23:19.809> etc<00:23:20.350> NPM 00:23:21.110 --> 00:23:21.120 align:start position:0% tooling tools like nvm and yarn etc NPM 00:23:21.120 --> 00:23:26.370 align:start position:0% tooling tools like nvm and yarn etc NPM etc<00:23:23.760> is<00:23:24.760> will<00:23:25.419> go<00:23:25.510> a<00:23:25.539> long<00:23:25.750> way<00:23:25.900> towards 00:23:26.370 --> 00:23:26.380 align:start position:0% etc is will go a long way towards 00:23:26.380 --> 00:23:29.909 align:start position:0% etc is will go a long way towards towards<00:23:27.390> opening<00:23:28.390> the<00:23:28.890> ecosystem<00:23:29.890> to 00:23:29.909 --> 00:23:29.919 align:start position:0% towards opening the ecosystem to 00:23:29.919 --> 00:23:31.470 align:start position:0% towards opening the ecosystem to millions<00:23:30.309> of<00:23:30.460> developers<00:23:30.940> who<00:23:31.240> are<00:23:31.299> very 00:23:31.470 --> 00:23:31.480 align:start position:0% millions of developers who are very 00:23:31.480 --> 00:23:32.669 align:start position:0% millions of developers who are very familiar<00:23:31.570> with<00:23:31.900> those<00:23:32.020> tools<00:23:32.260> so<00:23:32.380> that's<00:23:32.559> my 00:23:32.669 --> 00:23:32.679 align:start position:0% familiar with those tools so that's my 00:23:32.679 --> 00:23:33.899 align:start position:0% familiar with those tools so that's my personal<00:23:32.890> motivation<00:23:33.100> for<00:23:33.580> working<00:23:33.820> on 00:23:33.899 --> 00:23:33.909 align:start position:0% personal motivation for working on 00:23:33.909 --> 00:23:36.480 align:start position:0% personal motivation for working on assembly<00:23:34.240> script<00:23:34.980> so<00:23:35.980> I'm<00:23:36.070> just<00:23:36.159> gonna<00:23:36.250> this 00:23:36.480 --> 00:23:36.490 align:start position:0% assembly script so I'm just gonna this 00:23:36.490 --> 00:23:38.430 align:start position:0% assembly script so I'm just gonna this is<00:23:36.640> as<00:23:36.820> Paul<00:23:37.659> said<00:23:37.840> a<00:23:37.870> moment<00:23:37.990> ago<00:23:38.169> this<00:23:38.380> is 00:23:38.430 --> 00:23:38.440 align:start position:0% is as Paul said a moment ago this is 00:23:38.440 --> 00:23:40.049 align:start position:0% is as Paul said a moment ago this is kind<00:23:38.679> of<00:23:38.740> a<00:23:38.799> lightning<00:23:39.100> talk<00:23:39.309> I'm<00:23:39.760> just<00:23:39.940> gonna 00:23:40.049 --> 00:23:40.059 align:start position:0% kind of a lightning talk I'm just gonna 00:23:40.059 --> 00:23:41.730 align:start position:0% kind of a lightning talk I'm just gonna super<00:23:40.450> quickly<00:23:40.659> show<00:23:40.929> you<00:23:40.990> kind<00:23:41.380> of<00:23:41.409> what<00:23:41.620> this 00:23:41.730 --> 00:23:41.740 align:start position:0% super quickly show you kind of what this 00:23:41.740 --> 00:23:43.919 align:start position:0% super quickly show you kind of what this looks<00:23:41.950> like<00:23:42.070> and<00:23:42.460> the<00:23:43.419> first<00:23:43.570> thing<00:23:43.750> I'm<00:23:43.840> gonna 00:23:43.919 --> 00:23:43.929 align:start position:0% looks like and the first thing I'm gonna 00:23:43.929 --> 00:23:49.200 align:start position:0% looks like and the first thing I'm gonna show<00:23:44.020> you<00:23:44.200> here<00:23:44.590> is<00:23:45.900> my<00:23:46.900> WRC<00:23:47.860> 20<00:23:48.159> example<00:23:49.059> code 00:23:49.200 --> 00:23:49.210 align:start position:0% show you here is my WRC 20 example code 00:23:49.210 --> 00:23:51.480 align:start position:0% show you here is my WRC 20 example code so<00:23:49.360> this<00:23:49.450> works<00:23:49.720> this<00:23:50.110> is<00:23:50.260> this<00:23:51.010> is<00:23:51.159> assembly 00:23:51.480 --> 00:23:51.490 align:start position:0% so this works this is this is assembly 00:23:51.490 --> 00:23:53.240 align:start position:0% so this works this is this is assembly script<00:23:51.700> it's<00:23:51.850> valid<00:23:52.150> it<00:23:52.240> compiles<00:23:52.690> it<00:23:52.960> runs 00:23:53.240 --> 00:23:53.250 align:start position:0% script it's valid it compiles it runs 00:23:53.250 --> 00:23:55.610 align:start position:0% script it's valid it compiles it runs we've<00:23:54.250> deployed<00:23:54.549> it<00:23:54.700> on<00:23:54.760> the<00:23:54.850> test<00:23:55.030> net<00:23:55.240> and 00:23:55.610 --> 00:23:55.620 align:start position:0% we've deployed it on the test net and 00:23:55.620 --> 00:23:58.620 align:start position:0% we've deployed it on the test net and I'm<00:23:56.620> sorry<00:23:57.220> if<00:23:57.340> that<00:23:57.460> font<00:23:57.640> size<00:23:57.820> is<00:23:58.059> not<00:23:58.179> super 00:23:58.620 --> 00:23:58.630 align:start position:0% I'm sorry if that font size is not super 00:23:58.630 --> 00:23:59.760 align:start position:0% I'm sorry if that font size is not super large<00:23:58.809> I<00:23:58.899> don't<00:23:58.929> think<00:23:59.169> I<00:23:59.230> can<00:23:59.409> easily 00:23:59.760 --> 00:23:59.770 align:start position:0% large I don't think I can easily 00:23:59.770 --> 00:24:00.990 align:start position:0% large I don't think I can easily increase<00:24:00.190> it<00:24:00.399> but<00:24:00.490> hopefully<00:24:00.730> you<00:24:00.820> guys<00:24:00.940> can 00:24:00.990 --> 00:24:01.000 align:start position:0% increase it but hopefully you guys can 00:24:01.000 --> 00:24:03.650 align:start position:0% increase it but hopefully you guys can get<00:24:01.330> a<00:24:01.360> sense<00:24:01.570> of<00:24:01.720> this<00:24:01.840> you<00:24:02.679> know 00:24:03.650 --> 00:24:03.660 align:start position:0% get a sense of this you know 00:24:03.660 --> 00:24:05.270 align:start position:0% get a sense of this you know it's<00:24:03.780> kind<00:24:03.990> of<00:24:04.020> funny<00:24:04.230> right<00:24:04.500> it<00:24:04.620> looks<00:24:04.830> sort 00:24:05.270 --> 00:24:05.280 align:start position:0% it's kind of funny right it looks sort 00:24:05.280 --> 00:24:06.320 align:start position:0% it's kind of funny right it looks sort of<00:24:05.310> like<00:24:05.370> JavaScript<00:24:05.940> it<00:24:06.030> kind<00:24:06.180> of<00:24:06.210> has 00:24:06.320 --> 00:24:06.330 align:start position:0% of like JavaScript it kind of has 00:24:06.330 --> 00:24:08.690 align:start position:0% of like JavaScript it kind of has JavaScript<00:24:06.810> syntax<00:24:06.990> but<00:24:07.950> we've<00:24:08.160> got<00:24:08.370> so<00:24:08.580> we've 00:24:08.690 --> 00:24:08.700 align:start position:0% JavaScript syntax but we've got so we've 00:24:08.700 --> 00:24:10.670 align:start position:0% JavaScript syntax but we've got so we've got<00:24:08.790> the<00:24:08.880> strict<00:24:09.090> types<00:24:09.300> of<00:24:09.570> typescript<00:24:10.350> and 00:24:10.670 --> 00:24:10.680 align:start position:0% got the strict types of typescript and 00:24:10.680 --> 00:24:12.770 align:start position:0% got the strict types of typescript and then<00:24:11.160> we've<00:24:11.280> got<00:24:11.460> stuff<00:24:12.210> which<00:24:12.390> looks<00:24:12.630> and 00:24:12.770 --> 00:24:12.780 align:start position:0% then we've got stuff which looks and 00:24:12.780 --> 00:24:14.720 align:start position:0% then we've got stuff which looks and feels<00:24:12.900> a<00:24:13.020> bit<00:24:13.110> like<00:24:13.170> assembly<00:24:13.680> so<00:24:14.580> what's 00:24:14.720 --> 00:24:14.730 align:start position:0% feels a bit like assembly so what's 00:24:14.730 --> 00:24:16.070 align:start position:0% feels a bit like assembly so what's going<00:24:14.910> on<00:24:15.030> here<00:24:15.270> is<00:24:15.330> we<00:24:15.450> have<00:24:15.570> a<00:24:15.600> single<00:24:15.930> main 00:24:16.070 --> 00:24:16.080 align:start position:0% going on here is we have a single main 00:24:16.080 --> 00:24:18.640 align:start position:0% going on here is we have a single main function<00:24:16.530> which<00:24:16.830> is<00:24:16.950> the<00:24:17.070> entry<00:24:17.340> point<00:24:17.370> and 00:24:18.640 --> 00:24:18.650 align:start position:0% function which is the entry point and 00:24:18.650 --> 00:24:21.200 align:start position:0% function which is the entry point and what<00:24:19.650> you<00:24:19.740> see<00:24:19.950> with<00:24:20.100> this<00:24:20.220> the<00:24:20.490> switch<00:24:20.820> here 00:24:21.200 --> 00:24:21.210 align:start position:0% what you see with this the switch here 00:24:21.210 --> 00:24:23.660 align:start position:0% what you see with this the switch here and<00:24:21.410> these<00:24:22.410> sort<00:24:22.560> of<00:24:22.620> hexadecimal<00:24:23.430> strings 00:24:23.660 --> 00:24:23.670 align:start position:0% and these sort of hexadecimal strings 00:24:23.670 --> 00:24:25.790 align:start position:0% and these sort of hexadecimal strings this<00:24:24.240> is<00:24:24.420> a<00:24:24.450> simplified<00:24:25.020> version<00:24:25.170> of<00:24:25.350> ABI 00:24:25.790 --> 00:24:25.800 align:start position:0% this is a simplified version of ABI 00:24:25.800 --> 00:24:29.110 align:start position:0% this is a simplified version of ABI so<00:24:26.640> we've<00:24:26.940> manually<00:24:27.450> implemented<00:24:27.900> this<00:24:28.050> the 00:24:29.110 --> 00:24:29.120 align:start position:0% so we've manually implemented this the 00:24:29.120 --> 00:24:32.690 align:start position:0% so we've manually implemented this the main<00:24:30.120> function<00:24:30.540> receives<00:24:31.400> receives<00:24:32.400> a<00:24:32.520> call 00:24:32.690 --> 00:24:32.700 align:start position:0% main function receives receives a call 00:24:32.700 --> 00:24:35.840 align:start position:0% main function receives receives a call and<00:24:33.620> it<00:24:34.620> sort<00:24:34.890> of<00:24:34.920> unpacked<00:24:35.310> the<00:24:35.520> first<00:24:35.700> few 00:24:35.840 --> 00:24:35.850 align:start position:0% and it sort of unpacked the first few 00:24:35.850 --> 00:24:37.580 align:start position:0% and it sort of unpacked the first few bytes<00:24:36.030> and<00:24:36.300> uses<00:24:36.630> that<00:24:36.660> to<00:24:36.840> figure<00:24:37.200> out<00:24:37.320> which 00:24:37.580 --> 00:24:37.590 align:start position:0% bytes and uses that to figure out which 00:24:37.590 --> 00:24:39.890 align:start position:0% bytes and uses that to figure out which function<00:24:37.770> is<00:24:38.040> being<00:24:38.190> called<00:24:38.430> and<00:24:38.760> I<00:24:39.630> think<00:24:39.840> I 00:24:39.890 --> 00:24:39.900 align:start position:0% function is being called and I think I 00:24:39.900 --> 00:24:41.720 align:start position:0% function is being called and I think I have<00:24:40.020> the<00:24:40.170> do<00:24:40.350> balance<00:24:40.680> function<00:24:41.550> over<00:24:41.700> here 00:24:41.720 --> 00:24:41.730 align:start position:0% have the do balance function over here 00:24:41.730 --> 00:24:42.860 align:start position:0% have the do balance function over here which<00:24:42.000> is<00:24:42.120> the<00:24:42.210> one<00:24:42.330> that<00:24:42.420> returns<00:24:42.720> the 00:24:42.860 --> 00:24:42.870 align:start position:0% which is the one that returns the 00:24:42.870 --> 00:24:45.350 align:start position:0% which is the one that returns the current<00:24:43.200> balance<00:24:43.350> and<00:24:43.830> you<00:24:44.700> see<00:24:44.910> things<00:24:45.120> which 00:24:45.350 --> 00:24:45.360 align:start position:0% current balance and you see things which 00:24:45.360 --> 00:24:47.240 align:start position:0% current balance and you see things which are<00:24:45.510> basically<00:24:45.840> more<00:24:46.770> or<00:24:46.830> less<00:24:46.950> map 00:24:47.240 --> 00:24:47.250 align:start position:0% are basically more or less map 00:24:47.250 --> 00:24:50.210 align:start position:0% are basically more or less map one-to-one<00:24:47.940> to<00:24:48.180> EVM<00:24:48.950> operations<00:24:49.950> right<00:24:50.100> so 00:24:50.210 --> 00:24:50.220 align:start position:0% one-to-one to EVM operations right so 00:24:50.220 --> 00:24:51.800 align:start position:0% one-to-one to EVM operations right so things<00:24:50.400> like<00:24:50.550> get<00:24:50.700> call<00:24:50.850> data<00:24:51.030> size<00:24:51.270> call<00:24:51.660> data 00:24:51.800 --> 00:24:51.810 align:start position:0% things like get call data size call data 00:24:51.810 --> 00:24:52.700 align:start position:0% things like get call data size call data copy 00:24:52.700 --> 00:24:52.710 align:start position:0% copy 00:24:52.710 --> 00:24:54.800 align:start position:0% copy we're<00:24:52.980> also<00:24:53.130> manually<00:24:53.820> managing<00:24:54.600> memory 00:24:54.800 --> 00:24:54.810 align:start position:0% we're also manually managing memory 00:24:54.810 --> 00:24:57.590 align:start position:0% we're also manually managing memory we're<00:24:55.050> loading<00:24:55.910> things<00:24:56.910> into<00:24:57.150> pointers<00:24:57.450> and 00:24:57.590 --> 00:24:57.600 align:start position:0% we're loading things into pointers and 00:24:57.600 --> 00:24:59.840 align:start position:0% we're loading things into pointers and stuff<00:24:57.780> I<00:24:58.020> think<00:24:58.680> I<00:24:58.740> have<00:24:58.860> another<00:24:59.100> one<00:24:59.190> here 00:24:59.840 --> 00:24:59.850 align:start position:0% stuff I think I have another one here 00:24:59.850 --> 00:25:02.330 align:start position:0% stuff I think I have another one here this<00:25:00.060> is<00:25:00.120> the<00:25:00.360> do<00:25:00.510> transfer<00:25:00.990> function<00:25:01.380> so 00:25:02.330 --> 00:25:02.340 align:start position:0% this is the do transfer function so 00:25:02.340 --> 00:25:05.720 align:start position:0% this is the do transfer function so again<00:25:02.670> this<00:25:03.210> kind<00:25:03.390> of<00:25:03.950> reads<00:25:04.950> the<00:25:05.250> input<00:25:05.610> data 00:25:05.720 --> 00:25:05.730 align:start position:0% again this kind of reads the input data 00:25:05.730 --> 00:25:07.490 align:start position:0% again this kind of reads the input data gets<00:25:06.570> the<00:25:06.690> length<00:25:06.840> of<00:25:06.960> it<00:25:07.050> reads<00:25:07.200> the<00:25:07.260> input 00:25:07.490 --> 00:25:07.500 align:start position:0% gets the length of it reads the input 00:25:07.500 --> 00:25:09.860 align:start position:0% gets the length of it reads the input data<00:25:07.620> at<00:25:07.860> allocates<00:25:08.220> memory<00:25:08.400> you<00:25:09.360> know<00:25:09.480> moves 00:25:09.860 --> 00:25:09.870 align:start position:0% data at allocates memory you know moves 00:25:09.870 --> 00:25:11.720 align:start position:0% data at allocates memory you know moves pointers<00:25:10.230> around<00:25:10.470> etc<00:25:10.890> and<00:25:11.070> then<00:25:11.430> there's<00:25:11.640> no 00:25:11.720 --> 00:25:11.730 align:start position:0% pointers around etc and then there's no 00:25:11.730 --> 00:25:13.910 align:start position:0% pointers around etc and then there's no return<00:25:12.060> because<00:25:12.780> what<00:25:13.260> has<00:25:13.380> to<00:25:13.500> happen<00:25:13.620> is<00:25:13.830> it 00:25:13.910 --> 00:25:13.920 align:start position:0% return because what has to happen is it 00:25:13.920 --> 00:25:16.550 align:start position:0% return because what has to happen is it has<00:25:14.010> to<00:25:14.160> store<00:25:14.450> the<00:25:15.450> return<00:25:15.600> value<00:25:16.050> into<00:25:16.530> a 00:25:16.550 --> 00:25:16.560 align:start position:0% has to store the return value into a 00:25:16.560 --> 00:25:20.510 align:start position:0% has to store the return value into a pointer<00:25:16.950> so<00:25:18.590> this<00:25:19.590> is<00:25:19.770> a<00:25:20.010> step<00:25:20.220> in<00:25:20.370> the<00:25:20.430> right 00:25:20.510 --> 00:25:20.520 align:start position:0% pointer so this is a step in the right 00:25:20.520 --> 00:25:21.890 align:start position:0% pointer so this is a step in the right direction<00:25:20.580> but<00:25:21.060> this<00:25:21.180> is<00:25:21.300> not<00:25:21.420> exactly<00:25:21.810> the 00:25:21.890 --> 00:25:21.900 align:start position:0% direction but this is not exactly the 00:25:21.900 --> 00:25:24.140 align:start position:0% direction but this is not exactly the way<00:25:22.590> I<00:25:22.620> want<00:25:22.890> to<00:25:22.920> write<00:25:23.070> code<00:25:23.100> and<00:25:23.850> so<00:25:23.970> I<00:25:24.000> want 00:25:24.140 --> 00:25:24.150 align:start position:0% way I want to write code and so I want 00:25:24.150 --> 00:25:25.280 align:start position:0% way I want to write code and so I want to<00:25:24.210> show<00:25:24.360> you<00:25:24.420> this<00:25:24.720> is<00:25:24.870> what<00:25:24.990> it<00:25:25.080> will<00:25:25.230> look 00:25:25.280 --> 00:25:25.290 align:start position:0% to show you this is what it will look 00:25:25.290 --> 00:25:28.220 align:start position:0% to show you this is what it will look like<00:25:25.560> and<00:25:26.450> this<00:25:27.450> should<00:25:27.690> look<00:25:27.720> and<00:25:27.960> feel<00:25:28.080> a<00:25:28.110> lot 00:25:28.220 --> 00:25:28.230 align:start position:0% like and this should look and feel a lot 00:25:28.230 --> 00:25:30.170 align:start position:0% like and this should look and feel a lot more<00:25:28.470> like<00:25:28.860> JavaScript<00:25:29.790> like<00:25:29.910> modern 00:25:30.170 --> 00:25:30.180 align:start position:0% more like JavaScript like modern 00:25:30.180 --> 00:25:34.520 align:start position:0% more like JavaScript like modern JavaScript<00:25:30.860> we<00:25:31.860> have<00:25:32.570> you<00:25:33.570> know<00:25:33.690> some 00:25:34.520 --> 00:25:34.530 align:start position:0% JavaScript we have you know some 00:25:34.530 --> 00:25:36.170 align:start position:0% JavaScript we have you know some abstracted<00:25:35.250> classes<00:25:35.850> things<00:25:36.030> like<00:25:36.150> a 00:25:36.170 --> 00:25:36.180 align:start position:0% abstracted classes things like a 00:25:36.180 --> 00:25:38.930 align:start position:0% abstracted classes things like a contract<00:25:36.720> we<00:25:36.990> have<00:25:37.020> decorators<00:25:37.740> so<00:25:38.490> we<00:25:38.670> use<00:25:38.790> it 00:25:38.930 --> 00:25:38.940 align:start position:0% contract we have decorators so we use it 00:25:38.940 --> 00:25:40.430 align:start position:0% contract we have decorators so we use it II<00:25:39.000> was<00:25:39.180> in<00:25:39.210> decorator<00:25:39.690> to<00:25:39.870> indicate<00:25:40.260> that 00:25:40.430 --> 00:25:40.440 align:start position:0% II was in decorator to indicate that 00:25:40.440 --> 00:25:43.130 align:start position:0% II was in decorator to indicate that this<00:25:40.590> class<00:25:40.920> is<00:25:41.280> the<00:25:41.340> class<00:25:41.550> that<00:25:42.060> is<00:25:42.660> the 00:25:43.130 --> 00:25:43.140 align:start position:0% this class is the class that is the 00:25:43.140 --> 00:25:46.070 align:start position:0% this class is the class that is the entry<00:25:43.380> point<00:25:43.590> in<00:25:43.830> this<00:25:44.340> code<00:25:44.630> we<00:25:45.630> use<00:25:45.750> a<00:25:45.780> simple 00:25:46.070 --> 00:25:46.080 align:start position:0% entry point in this code we use a simple 00:25:46.080 --> 00:25:47.810 align:start position:0% entry point in this code we use a simple store<00:25:46.410> decorator<00:25:46.830> so<00:25:47.010> this<00:25:47.130> looks<00:25:47.640> and<00:25:47.790> feels 00:25:47.810 --> 00:25:47.820 align:start position:0% store decorator so this looks and feels 00:25:47.820 --> 00:25:49.310 align:start position:0% store decorator so this looks and feels a<00:25:48.090> little<00:25:48.210> bit<00:25:48.360> more<00:25:48.540> like<00:25:48.690> solidity<00:25:48.990> it's 00:25:49.310 --> 00:25:49.320 align:start position:0% a little bit more like solidity it's 00:25:49.320 --> 00:25:50.780 align:start position:0% a little bit more like solidity it's inspired<00:25:49.680> by<00:25:49.770> solidity<00:25:50.220> we<00:25:50.340> have<00:25:50.460> things<00:25:50.640> like 00:25:50.780 --> 00:25:50.790 align:start position:0% inspired by solidity we have things like 00:25:50.790 --> 00:25:53.330 align:start position:0% inspired by solidity we have things like maps<00:25:51.060> and<00:25:51.350> look<00:25:52.350> how<00:25:52.470> much<00:25:52.590> less<00:25:52.830> code<00:25:53.040> this<00:25:53.160> is 00:25:53.330 --> 00:25:53.340 align:start position:0% maps and look how much less code this is 00:25:53.340 --> 00:25:54.440 align:start position:0% maps and look how much less code this is look<00:25:53.520> how<00:25:53.580> much<00:25:53.730> more<00:25:53.880> readable<00:25:54.090> this<00:25:54.300> is 00:25:54.440 --> 00:25:54.450 align:start position:0% look how much more readable this is 00:25:54.450 --> 00:25:56.300 align:start position:0% look how much more readable this is right<00:25:54.840> get<00:25:55.230> balanced<00:25:55.620> set<00:25:55.830> balance<00:25:56.160> or<00:25:56.280> a 00:25:56.300 --> 00:25:56.310 align:start position:0% right get balanced set balance or a 00:25:56.310 --> 00:25:58.190 align:start position:0% right get balanced set balance or a single<00:25:56.520> line<00:25:56.760> the<00:25:57.330> transfer<00:25:57.750> code<00:25:57.900> should<00:25:58.140> be 00:25:58.190 --> 00:25:58.200 align:start position:0% single line the transfer code should be 00:25:58.200 --> 00:25:59.780 align:start position:0% single line the transfer code should be pretty<00:25:58.380> pretty<00:25:58.770> clear<00:25:58.980> so<00:25:59.460> this<00:25:59.580> is<00:25:59.700> the 00:25:59.780 --> 00:25:59.790 align:start position:0% pretty pretty clear so this is the 00:25:59.790 --> 00:26:01.460 align:start position:0% pretty pretty clear so this is the direction<00:26:00.000> we're<00:26:00.210> going<00:26:00.360> the<00:26:00.990> first<00:26:01.230> part 00:26:01.460 --> 00:26:01.470 align:start position:0% direction we're going the first part 00:26:01.470 --> 00:26:03.920 align:start position:0% direction we're going the first part here<00:26:01.890> as<00:26:02.460> I<00:26:02.610> said<00:26:02.760> this<00:26:02.910> works<00:26:03.180> this<00:26:03.450> compiles 00:26:03.920 --> 00:26:03.930 align:start position:0% here as I said this works this compiles 00:26:03.930 --> 00:26:06.940 align:start position:0% here as I said this works this compiles this<00:26:04.530> code<00:26:04.710> is<00:26:04.890> in<00:26:05.430> that<00:26:05.640> WRC<00:26:06.480> 20<00:26:06.690> examples 00:26:06.940 --> 00:26:06.950 align:start position:0% this code is in that WRC 20 examples 00:26:06.950 --> 00:26:08.780 align:start position:0% this code is in that WRC 20 examples directory<00:26:07.950> that<00:26:08.010> I<00:26:08.130> showed<00:26:08.310> you<00:26:08.340> a<00:26:08.460> moment<00:26:08.580> ago 00:26:08.780 --> 00:26:08.790 align:start position:0% directory that I showed you a moment ago 00:26:08.790 --> 00:26:12.860 align:start position:0% directory that I showed you a moment ago this<00:26:09.750> is<00:26:10.410> like<00:26:11.100> halfway<00:26:11.490> there<00:26:11.750> I've<00:26:12.750> been 00:26:12.860 --> 00:26:12.870 align:start position:0% this is like halfway there I've been 00:26:12.870 --> 00:26:14.810 align:start position:0% this is like halfway there I've been working<00:26:13.170> on<00:26:13.230> this<00:26:13.380> myself<00:26:13.830> and<00:26:14.430> could 00:26:14.810 --> 00:26:14.820 align:start position:0% working on this myself and could 00:26:14.820 --> 00:26:18.050 align:start position:0% working on this myself and could definitely<00:26:14.970> use<00:26:15.270> help<00:26:15.420> so<00:26:16.050> this<00:26:16.320> is<00:26:16.380> under<00:26:16.830> the 00:26:18.050 --> 00:26:18.060 align:start position:0% definitely use help so this is under the 00:26:18.060 --> 00:26:21.260 align:start position:0% definitely use help so this is under the ether<00:26:18.630> TS<00:26:19.850> organization<00:26:20.850> on<00:26:20.970> github 00:26:21.260 --> 00:26:21.270 align:start position:0% ether TS organization on github 00:26:21.270 --> 00:26:24.620 align:start position:0% ether TS organization on github github.com<00:26:21.600> /e<00:26:22.230> 30's<00:26:22.970> TS<00:26:23.970> being<00:26:24.180> typescript 00:26:24.620 --> 00:26:24.630 align:start position:0% github.com /e 30's TS being typescript 00:26:24.630 --> 00:26:25.400 align:start position:0% github.com /e 30's TS being typescript we're<00:26:24.720> trying<00:26:24.870> to<00:26:24.930> build<00:26:25.080> out<00:26:25.170> some<00:26:25.200> more 00:26:25.400 --> 00:26:25.410 align:start position:0% we're trying to build out some more 00:26:25.410 --> 00:26:28.160 align:start position:0% we're trying to build out some more typescript<00:26:26.100> tooling<00:26:26.780> yeah<00:26:27.780> i<00:26:27.810> was<00:26:28.020> going<00:26:28.110> to 00:26:28.160 --> 00:26:28.170 align:start position:0% typescript tooling yeah i was going to 00:26:28.170 --> 00:26:30.380 align:start position:0% typescript tooling yeah i was going to do<00:26:28.290> a<00:26:28.320> quick<00:26:28.590> live<00:26:28.830> demo<00:26:29.160> of<00:26:29.210> showing<00:26:30.210> you<00:26:30.270> how 00:26:30.380 --> 00:26:30.390 align:start position:0% do a quick live demo of showing you how 00:26:30.390 --> 00:26:34.310 align:start position:0% do a quick live demo of showing you how easy<00:26:30.420> it<00:26:30.660> is<00:26:30.750> to<00:26:31.550> to<00:26:32.550> initialize<00:26:33.420> this<00:26:33.630> you<00:26:34.140> can 00:26:34.310 --> 00:26:34.320 align:start position:0% easy it is to to initialize this you can 00:26:34.320 --> 00:26:35.900 align:start position:0% easy it is to to initialize this you can you<00:26:34.440> just<00:26:34.590> install<00:26:34.830> a<00:26:34.860> single<00:26:35.070> npm<00:26:35.490> module<00:26:35.790> you 00:26:35.900 --> 00:26:35.910 align:start position:0% you just install a single npm module you 00:26:35.910 --> 00:26:37.610 align:start position:0% you just install a single npm module you run<00:26:36.030> a<00:26:36.060> single<00:26:36.360> command<00:26:36.630> and<00:26:36.960> you've<00:26:37.200> got<00:26:37.350> the 00:26:37.610 --> 00:26:37.620 align:start position:0% run a single command and you've got the 00:26:37.620 --> 00:26:38.660 align:start position:0% run a single command and you've got the framework<00:26:37.980> but<00:26:38.130> I<00:26:38.160> think<00:26:38.520> we're<00:26:38.610> running 00:26:38.660 --> 00:26:38.670 align:start position:0% framework but I think we're running 00:26:38.670 --> 00:26:40.520 align:start position:0% framework but I think we're running short<00:26:38.940> on<00:26:39.000> time<00:26:39.150> so<00:26:39.210> let's<00:26:39.900> go<00:26:40.140> on<00:26:40.230> to<00:26:40.350> our<00:26:40.380> next 00:26:40.520 --> 00:26:40.530 align:start position:0% short on time so let's go on to our next 00:26:40.530 --> 00:26:56.740 align:start position:0% short on time so let's go on to our next talk<00:26:40.800> thank<00:26:41.370> you<00:26:47.120> so<00:26:48.120> up<00:26:48.240> next<00:26:48.270> we<00:26:48.540> have<00:26:48.660> Pavel 00:26:56.740 --> 00:26:56.750 align:start position:0% 00:26:56.750 --> 00:26:59.870 align:start position:0% so<00:26:57.750> Pavel<00:26:58.140> is<00:26:58.560> a<00:26:58.980> member<00:26:59.250> of<00:26:59.280> the<00:26:59.370> EOS<00:26:59.550> m<00:26:59.580> team 00:26:59.870 --> 00:26:59.880 align:start position:0% so Pavel is a member of the EOS m team 00:26:59.880 --> 00:27:02.000 align:start position:0% so Pavel is a member of the EOS m team he's<00:27:00.120> also<00:27:00.330> on<00:27:00.720> the<00:27:00.750> Alif<00:27:01.110> team<00:27:01.350> and<00:27:01.620> he's 00:27:02.000 --> 00:27:02.010 align:start position:0% he's also on the Alif team and he's 00:27:02.010 --> 00:27:07.750 align:start position:0% he's also on the Alif team and he's going<00:27:02.130> to<00:27:02.190> talk<00:27:02.340> to<00:27:02.400> you<00:27:02.490> about<00:27:02.580> EVM<00:27:03.000> C<00:27:05.390> hello 00:27:07.750 --> 00:27:07.760 align:start position:0% going to talk to you about EVM C hello 00:27:07.760 --> 00:27:13.310 align:start position:0% going to talk to you about EVM C hello yeah<00:27:08.760> okay<00:27:09.170> hello<00:27:10.170> everyone<00:27:11.300> I'm<00:27:12.320> C++ 00:27:13.310 --> 00:27:13.320 align:start position:0% yeah okay hello everyone I'm C++ 00:27:13.320 --> 00:27:16.100 align:start position:0% yeah okay hello everyone I'm C++ developer<00:27:14.100> within<00:27:14.460> a<00:27:14.790> team<00:27:14.970> foundation<00:27:15.510> and 00:27:16.100 --> 00:27:16.110 align:start position:0% developer within a team foundation and 00:27:16.110 --> 00:27:19.400 align:start position:0% developer within a team foundation and one<00:27:16.710> of<00:27:16.830> the<00:27:16.950> project<00:27:17.340> I<00:27:17.460> was<00:27:17.490> working<00:27:18.410> for 00:27:19.400 --> 00:27:19.410 align:start position:0% one of the project I was working for 00:27:19.410 --> 00:27:26.990 align:start position:0% one of the project I was working for some<00:27:19.650> time<00:27:19.890> is<00:27:20.240> called<00:27:21.240> EVM<00:27:21.840> see<00:27:22.460> it's<00:27:24.500> I<00:27:26.000> would 00:27:26.990 --> 00:27:27.000 align:start position:0% some time is called EVM see it's I would 00:27:27.000 --> 00:27:29.510 align:start position:0% some time is called EVM see it's I would try<00:27:27.180> to<00:27:27.210> explain<00:27:27.420> what<00:27:27.870> it<00:27:28.140> and<00:27:28.470> give<00:27:29.250> some 00:27:29.510 --> 00:27:29.520 align:start position:0% try to explain what it and give some 00:27:29.520 --> 00:27:33.830 align:start position:0% try to explain what it and give some quick<00:27:30.390> updates<00:27:30.950> what<00:27:31.950> what<00:27:32.730> has<00:27:33.090> happened<00:27:33.570> in 00:27:33.830 --> 00:27:33.840 align:start position:0% quick updates what what has happened in 00:27:33.840 --> 00:27:48.170 align:start position:0% quick updates what what has happened in the<00:27:33.960> project<00:27:34.350> recently<00:27:34.800> and<00:27:40.610> and<00:27:43.430> well<00:27:47.180> keep 00:27:48.170 --> 00:27:48.180 align:start position:0% the project recently and and well keep 00:27:48.180 --> 00:27:52.270 align:start position:0% the project recently and and well keep the<00:27:48.330> lot<00:27:49.370> okay<00:27:50.370> here<00:27:50.670> we<00:27:50.730> go 00:27:52.270 --> 00:27:52.280 align:start position:0% the lot okay here we go 00:27:52.280 --> 00:27:55.010 align:start position:0% the lot okay here we go and<00:27:53.280> in<00:27:54.210> the<00:27:54.300> second<00:27:54.600> part<00:27:54.780> of<00:27:54.900> this 00:27:55.010 --> 00:27:55.020 align:start position:0% and in the second part of this 00:27:55.020 --> 00:28:00.770 align:start position:0% and in the second part of this presentation<00:27:55.530> I'd<00:27:55.890> like<00:27:55.920> to<00:27:57.230> go<00:27:59.240> go<00:28:00.240> from<00:28:00.540> this 00:28:00.770 --> 00:28:00.780 align:start position:0% presentation I'd like to go go from this 00:28:00.780 --> 00:28:05.930 align:start position:0% presentation I'd like to go go from this EVM<00:28:01.650> C<00:28:01.920> and<00:28:02.220> through<00:28:02.700> EVM<00:28:03.270> as<00:28:03.480> well<00:28:04.490> go<00:28:05.490> back<00:28:05.730> to 00:28:05.930 --> 00:28:05.940 align:start position:0% EVM C and through EVM as well go back to 00:28:05.940 --> 00:28:10.040 align:start position:0% EVM C and through EVM as well go back to awasum<00:28:06.900> and<00:28:07.280> some<00:28:08.280> dis<00:28:08.660> explained<00:28:09.660> some 00:28:10.040 --> 00:28:10.050 align:start position:0% awasum and some dis explained some 00:28:10.050 --> 00:28:12.800 align:start position:0% awasum and some dis explained some design<00:28:10.440> decisions<00:28:10.470> we<00:28:11.250> might<00:28:11.460> and<00:28:11.910> where<00:28:12.600> they 00:28:12.800 --> 00:28:12.810 align:start position:0% design decisions we might and where they 00:28:12.810 --> 00:28:19.450 align:start position:0% design decisions we might and where they come<00:28:13.110> from 00:28:19.450 --> 00:28:19.460 align:start position:0% 00:28:19.460 --> 00:28:24.560 align:start position:0% ok<00:28:20.460> so<00:28:20.520> let's<00:28:20.910> start<00:28:21.000> with<00:28:21.300> this<00:28:21.450> EVM<00:28:21.900> see<00:28:23.570> this 00:28:24.560 --> 00:28:24.570 align:start position:0% ok so let's start with this EVM see this 00:28:24.570 --> 00:28:28.340 align:start position:0% ok so let's start with this EVM see this is<00:28:24.750> a<00:28:24.780> project<00:28:25.200> that<00:28:25.800> has<00:28:26.930> mostly<00:28:27.930> one<00:28:28.080> goal 00:28:28.340 --> 00:28:28.350 align:start position:0% is a project that has mostly one goal 00:28:28.350 --> 00:28:31.610 align:start position:0% is a project that has mostly one goal and<00:28:28.650> it<00:28:29.580> wants<00:28:30.060> to<00:28:30.120> define 00:28:31.610 --> 00:28:31.620 align:start position:0% and it wants to define 00:28:31.620 --> 00:28:35.750 align:start position:0% and it wants to define the<00:28:31.950> API<00:28:32.399> in<00:28:32.970> the<00:28:33.360> classical<00:28:34.049> sense<00:28:34.429> of<00:28:35.429> the 00:28:35.750 --> 00:28:35.760 align:start position:0% the API in the classical sense of the 00:28:35.760 --> 00:28:38.419 align:start position:0% the API in the classical sense of the way<00:28:35.940> the<00:28:36.750> VM<00:28:37.380> implementation<00:28:38.220> can 00:28:38.419 --> 00:28:38.429 align:start position:0% way the VM implementation can 00:28:38.429 --> 00:28:41.029 align:start position:0% way the VM implementation can communicate<00:28:39.120> with<00:28:39.480> the<00:28:40.049> full<00:28:40.320> achieve<00:28:40.919> on 00:28:41.029 --> 00:28:41.039 align:start position:0% communicate with the full achieve on 00:28:41.039 --> 00:28:44.570 align:start position:0% communicate with the full achieve on client<00:28:41.490> and<00:28:41.760> how<00:28:42.720> we<00:28:42.779> call<00:28:43.049> it<00:28:43.080> here<00:28:43.500> we<00:28:44.309> called 00:28:44.570 --> 00:28:44.580 align:start position:0% client and how we call it here we called 00:28:44.580 --> 00:28:46.190 align:start position:0% client and how we call it here we called we<00:28:45.179> call<00:28:45.389> it<00:28:45.480> a<00:28:45.570> host 00:28:46.190 --> 00:28:46.200 align:start position:0% we call it a host 00:28:46.200 --> 00:28:51.289 align:start position:0% we call it a host so<00:28:46.830> it's<00:28:47.370> describes<00:28:49.370> rasa<00:28:50.370> functions<00:28:50.970> the 00:28:51.289 --> 00:28:51.299 align:start position:0% so it's describes rasa functions the 00:28:51.299 --> 00:28:53.299 align:start position:0% so it's describes rasa functions the both<00:28:51.450> sides<00:28:51.779> of<00:28:52.019> this<00:28:52.169> equation<00:28:52.740> has<00:28:53.100> to 00:28:53.299 --> 00:28:53.309 align:start position:0% both sides of this equation has to 00:28:53.309 --> 00:29:00.169 align:start position:0% both sides of this equation has to implement<00:28:56.269> so<00:28:57.269> on<00:28:57.539> the<00:28:57.659> hot<00:28:57.840> side<00:28:58.200> we<00:28:59.179> require 00:29:00.169 --> 00:29:00.179 align:start position:0% implement so on the hot side we require 00:29:00.179 --> 00:29:03.259 align:start position:0% implement so on the hot side we require some<00:29:00.659> some<00:29:01.500> functions<00:29:02.010> some<00:29:02.250> methods<00:29:02.610> the<00:29:03.000> the 00:29:03.259 --> 00:29:03.269 align:start position:0% some some functions some methods the the 00:29:03.269 --> 00:29:07.789 align:start position:0% some some functions some methods the the client<00:29:03.630> has<00:29:03.960> to<00:29:04.139> provide<00:29:04.500> the<00:29:06.049> EVM<00:29:07.049> execution 00:29:07.789 --> 00:29:07.799 align:start position:0% client has to provide the EVM execution 00:29:07.799 --> 00:29:11.930 align:start position:0% client has to provide the EVM execution and<00:29:08.929> on<00:29:09.929> the<00:29:10.169> VM<00:29:10.440> side<00:29:10.710> we<00:29:11.190> just<00:29:11.429> define<00:29:11.909> what 00:29:11.930 --> 00:29:11.940 align:start position:0% and on the VM side we just define what 00:29:11.940 --> 00:29:14.419 align:start position:0% and on the VM side we just define what what<00:29:12.570> are<00:29:12.720> the<00:29:12.809> entry<00:29:13.230> points<00:29:13.620> for<00:29:13.649> execution 00:29:14.419 --> 00:29:14.429 align:start position:0% what are the entry points for execution 00:29:14.429 --> 00:29:18.409 align:start position:0% what are the entry points for execution and<00:29:14.610> how<00:29:15.360> the<00:29:15.419> VM<00:29:15.929> should<00:29:16.830> be<00:29:17.010> created<00:29:18.000> and<00:29:18.149> how 00:29:18.409 --> 00:29:18.419 align:start position:0% and how the VM should be created and how 00:29:18.419 --> 00:29:21.740 align:start position:0% and how the VM should be created and how can<00:29:18.840> be<00:29:18.960> used<00:29:19.169> by<00:29:20.389> Julian<00:29:21.389> client 00:29:21.740 --> 00:29:21.750 align:start position:0% can be used by Julian client 00:29:21.750 --> 00:29:27.379 align:start position:0% can be used by Julian client implementations<00:29:24.350> and<00:29:25.350> if<00:29:26.220> we<00:29:26.490> can<00:29:26.730> focus<00:29:27.000> on 00:29:27.379 --> 00:29:27.389 align:start position:0% implementations and if we can focus on 00:29:27.389 --> 00:29:30.220 align:start position:0% implementations and if we can focus on the<00:29:27.600> the<00:29:28.019> host<00:29:28.289> methods<00:29:28.860> that<00:29:29.309> are<00:29:29.580> there 00:29:30.220 --> 00:29:30.230 align:start position:0% the the host methods that are there 00:29:30.230 --> 00:29:34.370 align:start position:0% the the host methods that are there there<00:29:31.230> are<00:29:31.350> 12<00:29:31.950> of<00:29:32.130> them<00:29:32.370> and<00:29:33.049> most<00:29:34.049> of<00:29:34.260> the 00:29:34.370 --> 00:29:34.380 align:start position:0% there are 12 of them and most of the 00:29:34.380 --> 00:29:36.320 align:start position:0% there are 12 of them and most of the most<00:29:34.830> of<00:29:35.039> these<00:29:35.190> these<00:29:35.820> basic<00:29:36.299> definitions 00:29:36.320 --> 00:29:36.330 align:start position:0% most of these these basic definitions 00:29:36.330 --> 00:29:39.529 align:start position:0% most of these these basic definitions are<00:29:37.200> written<00:29:37.470> in<00:29:37.620> in<00:29:37.860> C<00:29:38.220> code<00:29:38.429> however<00:29:39.240> I 00:29:39.529 --> 00:29:39.539 align:start position:0% are written in in C code however I 00:29:39.539 --> 00:29:44.120 align:start position:0% are written in in C code however I decided<00:29:40.230> to<00:29:40.620> to<00:29:41.250> show<00:29:41.490> you<00:29:42.380> example<00:29:43.380> of<00:29:43.529> what 00:29:44.120 --> 00:29:44.130 align:start position:0% decided to to show you example of what 00:29:44.130 --> 00:29:47.289 align:start position:0% decided to to show you example of what how<00:29:44.669> they<00:29:44.850> this<00:29:45.210> this<00:29:45.779> methods<00:29:46.230> looks<00:29:46.620> like 00:29:47.289 --> 00:29:47.299 align:start position:0% how they this this methods looks like 00:29:47.299 --> 00:29:50.870 align:start position:0% how they this this methods looks like taking<00:29:48.299> the<00:29:48.539> go<00:29:48.750> part<00:29:49.080> of<00:29:49.200> of<00:29:49.470> the<00:29:49.769> project<00:29:50.250> you 00:29:50.870 --> 00:29:50.880 align:start position:0% taking the go part of of the project you 00:29:50.880 --> 00:29:54.169 align:start position:0% taking the go part of of the project you don't<00:29:51.029> you<00:29:52.019> don't<00:29:52.169> need<00:29:52.769> to<00:29:53.039> read<00:29:53.190> it<00:29:53.309> all<00:29:53.460> it's 00:29:54.169 --> 00:29:54.179 align:start position:0% don't you don't need to read it all it's 00:29:54.179 --> 00:29:57.590 align:start position:0% don't you don't need to read it all it's mostly<00:29:54.750> I<00:29:55.169> wanted<00:29:56.100> to<00:29:56.190> show<00:29:56.370> how<00:29:56.700> how<00:29:57.120> complex 00:29:57.590 --> 00:29:57.600 align:start position:0% mostly I wanted to show how how complex 00:29:57.600 --> 00:30:01.340 align:start position:0% mostly I wanted to show how how complex it<00:29:57.779> is<00:29:57.929> to<00:29:58.519> to<00:29:59.519> enable<00:29:59.760> this<00:30:00.090> EVM<00:30:00.570> support<00:30:01.049> in 00:30:01.340 --> 00:30:01.350 align:start position:0% it is to to enable this EVM support in 00:30:01.350 --> 00:30:11.440 align:start position:0% it is to to enable this EVM support in in<00:30:02.779> achieving<00:30:03.779> client<00:30:04.169> implementation<00:30:08.539> and 00:30:11.440 --> 00:30:11.450 align:start position:0% in achieving client implementation and 00:30:11.450 --> 00:30:22.200 align:start position:0% in achieving client implementation and so 00:30:22.200 --> 00:30:22.210 align:start position:0% 00:30:22.210 --> 00:30:27.010 align:start position:0% so<00:30:23.210> to<00:30:24.110> explain<00:30:24.590> where<00:30:25.090> where<00:30:26.090> it<00:30:26.510> was<00:30:26.720> amiss 00:30:27.010 --> 00:30:27.020 align:start position:0% so to explain where where it was amiss 00:30:27.020 --> 00:30:31.060 align:start position:0% so to explain where where it was amiss is<00:30:27.350> all<00:30:27.559> this<00:30:27.710> picture<00:30:28.160> so<00:30:29.169> it's<00:30:30.169> not<00:30:30.470> so<00:30:30.679> I 00:30:31.060 --> 00:30:31.070 align:start position:0% is all this picture so it's not so I 00:30:31.070 --> 00:30:33.430 align:start position:0% is all this picture so it's not so I mean<00:30:31.669> it<00:30:32.059> it<00:30:32.419> seems<00:30:32.660> it's<00:30:32.870> completely 00:30:33.430 --> 00:30:33.440 align:start position:0% mean it it seems it's completely 00:30:33.440 --> 00:30:36.730 align:start position:0% mean it it seems it's completely different<00:30:33.770> execution<00:30:34.340> engine<00:30:34.730> but<00:30:35.470> EVM<00:30:36.470> see 00:30:36.730 --> 00:30:36.740 align:start position:0% different execution engine but EVM see 00:30:36.740 --> 00:30:38.350 align:start position:0% different execution engine but EVM see actually<00:30:37.190> doesn't<00:30:37.580> care<00:30:37.820> about<00:30:37.940> the 00:30:38.350 --> 00:30:38.360 align:start position:0% actually doesn't care about the 00:30:38.360 --> 00:30:40.840 align:start position:0% actually doesn't care about the execution<00:30:38.630> itself<00:30:39.290> it<00:30:40.040> defines<00:30:40.490> what 00:30:40.840 --> 00:30:40.850 align:start position:0% execution itself it defines what 00:30:40.850 --> 00:30:43.000 align:start position:0% execution itself it defines what actually<00:30:41.299> data<00:30:41.510> has<00:30:41.870> to<00:30:41.900> be<00:30:42.080> provided<00:30:42.710> to<00:30:42.740> the 00:30:43.000 --> 00:30:43.010 align:start position:0% actually data has to be provided to the 00:30:43.010 --> 00:30:46.840 align:start position:0% actually data has to be provided to the execution<00:30:43.610> so<00:30:44.590> this<00:30:45.590> product<00:30:46.100> was<00:30:46.309> started 00:30:46.840 --> 00:30:46.850 align:start position:0% execution so this product was started 00:30:46.850 --> 00:30:50.110 align:start position:0% execution so this product was started more<00:30:47.240> or<00:30:47.299> less<00:30:47.559> the<00:30:48.559> same<00:30:48.799> time<00:30:48.860> the<00:30:49.370> USM<00:30:49.820> idea 00:30:50.110 --> 00:30:50.120 align:start position:0% more or less the same time the USM idea 00:30:50.120 --> 00:30:53.860 align:start position:0% more or less the same time the USM idea was<00:30:51.220> was<00:30:52.220> brought<00:30:52.820> up<00:30:53.030> to<00:30:53.299> the<00:30:53.450> achievement 00:30:53.860 --> 00:30:53.870 align:start position:0% was was brought up to the achievement 00:30:53.870 --> 00:30:57.990 align:start position:0% was was brought up to the achievement community<00:30:54.410> but<00:30:55.130> it<00:30:55.400> wasn't<00:30:55.820> it<00:30:56.450> didn't<00:30:56.960> have 00:30:57.990 --> 00:30:58.000 align:start position:0% community but it wasn't it didn't have 00:30:58.000 --> 00:31:01.270 align:start position:0% community but it wasn't it didn't have didn't<00:30:59.000> have<00:30:59.030> the<00:30:59.510> the<00:30:59.870> wasn't<00:31:00.320> in<00:31:00.559> mind<00:31:00.890> but 00:31:01.270 --> 00:31:01.280 align:start position:0% didn't have the the wasn't in mind but 00:31:01.280 --> 00:31:04.450 align:start position:0% didn't have the the wasn't in mind but it<00:31:01.520> it's<00:31:02.120> it<00:31:02.540> turned<00:31:03.080> out<00:31:03.230> it's<00:31:03.530> you<00:31:04.130> can<00:31:04.280> also 00:31:04.450 --> 00:31:04.460 align:start position:0% it it's it turned out it's you can also 00:31:04.460 --> 00:31:07.510 align:start position:0% it it's it turned out it's you can also implement<00:31:05.030> it<00:31:05.929> was<00:31:06.110> an<00:31:06.290> execution<00:31:06.559> engines 00:31:07.510 --> 00:31:07.520 align:start position:0% implement it was an execution engines 00:31:07.520 --> 00:31:10.870 align:start position:0% implement it was an execution engines use<00:31:07.880> exactly<00:31:08.450> the<00:31:08.630> same<00:31:08.660> API<00:31:09.290> to<00:31:10.190> bring<00:31:10.429> it<00:31:10.700> was 00:31:10.870 --> 00:31:10.880 align:start position:0% use exactly the same API to bring it was 00:31:10.880 --> 00:31:13.510 align:start position:0% use exactly the same API to bring it was intuitive<00:31:11.270> iam<00:31:11.720> clients<00:31:12.230> and<00:31:12.440> here<00:31:13.100> is<00:31:13.220> one<00:31:13.490> of 00:31:13.510 --> 00:31:13.520 align:start position:0% intuitive iam clients and here is one of 00:31:13.520 --> 00:31:17.230 align:start position:0% intuitive iam clients and here is one of the<00:31:13.760> examples<00:31:14.299> that<00:31:14.780> actually<00:31:15.020> support<00:31:16.240> EVM 00:31:17.230 --> 00:31:17.240 align:start position:0% the examples that actually support EVM 00:31:17.240 --> 00:31:20.530 align:start position:0% the examples that actually support EVM see<00:31:17.510> from<00:31:17.929> the<00:31:18.049> beginning<00:31:18.200> and<00:31:18.770> it's<00:31:19.540> fully 00:31:20.530 --> 00:31:20.540 align:start position:0% see from the beginning and it's fully 00:31:20.540 --> 00:31:23.310 align:start position:0% see from the beginning and it's fully compatible<00:31:20.780> with<00:31:21.230> any<00:31:21.919> Experian<00:31:22.400> client<00:31:22.760> that 00:31:23.310 --> 00:31:23.320 align:start position:0% compatible with any Experian client that 00:31:23.320 --> 00:31:26.580 align:start position:0% compatible with any Experian client that that<00:31:24.320> actually<00:31:24.500> has<00:31:24.860> also<00:31:25.250> the<00:31:25.610> EVM<00:31:25.970> support 00:31:26.580 --> 00:31:26.590 align:start position:0% that actually has also the EVM support 00:31:26.590 --> 00:31:34.060 align:start position:0% that actually has also the EVM support in<00:31:27.590> the<00:31:27.770> bank<00:31:30.790> so<00:31:31.790> within<00:31:32.000> this<00:31:32.270> EMC<00:31:33.070> project 00:31:34.060 --> 00:31:34.070 align:start position:0% in the bank so within this EMC project 00:31:34.070 --> 00:31:38.490 align:start position:0% in the bank so within this EMC project they<00:31:34.190> also<00:31:34.309> try<00:31:34.730> to<00:31:35.320> have<00:31:36.320> language<00:31:37.160> bindings 00:31:38.490 --> 00:31:38.500 align:start position:0% they also try to have language bindings 00:31:38.500 --> 00:31:41.890 align:start position:0% they also try to have language bindings directly<00:31:39.500> inside<00:31:39.799> the<00:31:39.860> project<00:31:40.250> and<00:31:40.900> we 00:31:41.890 --> 00:31:41.900 align:start position:0% directly inside the project and we 00:31:41.900 --> 00:31:44.710 align:start position:0% directly inside the project and we started<00:31:42.730> well<00:31:43.730> the<00:31:43.910> first<00:31:44.150> one<00:31:44.390> was<00:31:44.419> the 00:31:44.710 --> 00:31:44.720 align:start position:0% started well the first one was the 00:31:44.720 --> 00:31:48.490 align:start position:0% started well the first one was the Python<00:31:45.200> prototype<00:31:45.830> of<00:31:46.330> of<00:31:47.330> that<00:31:47.750> to<00:31:48.200> figure 00:31:48.490 --> 00:31:48.500 align:start position:0% Python prototype of of that to figure 00:31:48.500 --> 00:31:51.159 align:start position:0% Python prototype of of that to figure out<00:31:48.740> if<00:31:49.010> final<00:31:49.790> fight<00:31:50.270> on<00:31:50.419> being<00:31:50.660> scripting 00:31:51.159 --> 00:31:51.169 align:start position:0% out if final fight on being scripting 00:31:51.169 --> 00:31:55.840 align:start position:0% out if final fight on being scripting language<00:31:51.940> is<00:31:52.940> it<00:31:53.480> is<00:31:53.750> it<00:31:53.960> the<00:31:54.679> the<00:31:55.070> C<00:31:55.370> API<00:31:55.520> is 00:31:55.840 --> 00:31:55.850 align:start position:0% language is it is it the the C API is 00:31:55.850 --> 00:31:57.970 align:start position:0% language is it is it the the C API is good<00:31:56.150> enough<00:31:56.330> to<00:31:56.390> have<00:31:56.840> Python<00:31:57.200> Python 00:31:57.970 --> 00:31:57.980 align:start position:0% good enough to have Python Python 00:31:57.980 --> 00:32:01.840 align:start position:0% good enough to have Python Python support<00:31:58.549> and<00:31:58.820> that<00:31:58.970> worked<00:31:59.410> very<00:32:00.410> well<00:32:00.850> but 00:32:01.840 --> 00:32:01.850 align:start position:0% support and that worked very well but 00:32:01.850 --> 00:32:06.190 align:start position:0% support and that worked very well but now<00:32:02.120> we<00:32:02.600> have<00:32:02.840> go<00:32:03.140> support<00:32:04.660> ready<00:32:05.660> to<00:32:05.929> be<00:32:06.049> used 00:32:06.190 --> 00:32:06.200 align:start position:0% now we have go support ready to be used 00:32:06.200 --> 00:32:12.070 align:start position:0% now we have go support ready to be used and<00:32:06.620> Jeff<00:32:07.549> is<00:32:07.790> using<00:32:08.179> that<00:32:09.820> does<00:32:10.820> go<00:32:11.540> bindings 00:32:12.070 --> 00:32:12.080 align:start position:0% and Jeff is using that does go bindings 00:32:12.080 --> 00:32:16.510 align:start position:0% and Jeff is using that does go bindings in<00:32:12.919> the<00:32:13.160> Indigo<00:32:13.730> assyrian<00:32:14.150> project<00:32:14.570> and<00:32:15.070> and<00:32:16.070> i 00:32:16.510 --> 00:32:16.520 align:start position:0% in the Indigo assyrian project and and i 00:32:16.520 --> 00:32:21.610 align:start position:0% in the Indigo assyrian project and and i hope<00:32:16.700> there<00:32:16.970> will<00:32:17.030> be<00:32:17.090> more<00:32:18.700> but<00:32:19.700> mostly<00:32:20.090> I<00:32:21.020> try 00:32:21.610 --> 00:32:21.620 align:start position:0% hope there will be more but mostly I try 00:32:21.620 --> 00:32:24.580 align:start position:0% hope there will be more but mostly I try to<00:32:21.919> keep<00:32:22.250> them<00:32:22.490> inside<00:32:23.240> the<00:32:23.720> project<00:32:23.960> to<00:32:24.440> be 00:32:24.580 --> 00:32:24.590 align:start position:0% to keep them inside the project to be 00:32:24.590 --> 00:32:27.250 align:start position:0% to keep them inside the project to be tested<00:32:25.130> with<00:32:25.309> all<00:32:25.580> the<00:32:25.970> changes<00:32:26.870> were<00:32:27.049> made<00:32:27.230> in 00:32:27.250 --> 00:32:27.260 align:start position:0% tested with all the changes were made in 00:32:27.260 --> 00:32:30.030 align:start position:0% tested with all the changes were made in there 00:32:30.030 --> 00:32:30.040 align:start position:0% 00:32:30.040 --> 00:32:34.550 align:start position:0% and<00:32:31.260> just<00:32:32.260> before<00:32:32.470> bath<00:32:32.860> Def<00:32:33.640> Con<00:32:33.940> there<00:32:34.270> was 00:32:34.550 --> 00:32:34.560 align:start position:0% and just before bath Def Con there was 00:32:34.560 --> 00:32:41.850 align:start position:0% and just before bath Def Con there was released<00:32:35.560> six<00:32:35.940> 0.0<00:32:36.940> 0.0<00:32:37.510> of<00:32:38.350> of<00:32:39.190> EVM<00:32:39.940> see<00:32:40.860> we're 00:32:41.850 --> 00:32:41.860 align:start position:0% released six 0.0 0.0 of of EVM see we're 00:32:41.860 --> 00:32:44.700 align:start position:0% released six 0.0 0.0 of of EVM see we're using<00:32:42.150> semantic<00:32:43.150> versioning<00:32:43.750> for<00:32:43.810> that<00:32:44.200> and 00:32:44.700 --> 00:32:44.710 align:start position:0% using semantic versioning for that and 00:32:44.710 --> 00:32:49.860 align:start position:0% using semantic versioning for that and also<00:32:46.680> we<00:32:47.680> describe<00:32:48.520> a<00:32:48.760> number<00:32:48.880> called<00:32:49.360> a<00:32:49.570> bi 00:32:49.860 --> 00:32:49.870 align:start position:0% also we describe a number called a bi 00:32:49.870 --> 00:32:52.470 align:start position:0% also we describe a number called a bi version<00:32:50.440> which<00:32:50.620> is<00:32:50.830> the<00:32:51.130> first<00:32:51.610> number<00:32:51.850> of<00:32:52.150> the 00:32:52.470 --> 00:32:52.480 align:start position:0% version which is the first number of the 00:32:52.480 --> 00:32:54.780 align:start position:0% version which is the first number of the full<00:32:52.690> version<00:32:53.140> and<00:32:53.350> this<00:32:53.830> number<00:32:54.040> is<00:32:54.190> exposed 00:32:54.780 --> 00:32:54.790 align:start position:0% full version and this number is exposed 00:32:54.790 --> 00:32:57.840 align:start position:0% full version and this number is exposed today<00:32:55.060> to<00:32:55.510> the<00:32:55.630> implementation<00:32:56.340> to<00:32:57.340> check<00:32:57.580> for 00:32:57.840 --> 00:32:57.850 align:start position:0% today to the implementation to check for 00:32:57.850 --> 00:33:01.230 align:start position:0% today to the implementation to check for basic<00:32:58.270> compatibility<00:32:59.730> especially<00:33:00.730> we<00:33:00.850> when 00:33:01.230 --> 00:33:01.240 align:start position:0% basic compatibility especially we when 00:33:01.240 --> 00:33:05.280 align:start position:0% basic compatibility especially we when we<00:33:01.420> use<00:33:01.710> dynamic<00:33:02.710> loaded<00:33:03.370> libraries<00:33:04.290> for 00:33:05.280 --> 00:33:05.290 align:start position:0% we use dynamic loaded libraries for 00:33:05.290 --> 00:33:11.060 align:start position:0% we use dynamic loaded libraries for deployment<00:33:07.500> and<00:33:08.520> at<00:33:09.520> the<00:33:09.850> current<00:33:10.210> moment 00:33:11.060 --> 00:33:11.070 align:start position:0% deployment and at the current moment 00:33:11.070 --> 00:33:14.340 align:start position:0% deployment and at the current moment I'll<00:33:12.070> have<00:33:12.340> the<00:33:12.490> C++<00:33:13.090> implementation<00:33:13.270> of<00:33:14.020> of 00:33:14.340 --> 00:33:14.350 align:start position:0% I'll have the C++ implementation of of 00:33:14.350 --> 00:33:17.460 align:start position:0% I'll have the C++ implementation of of of<00:33:14.980> a<00:33:15.130> Tyrian<00:33:15.430> client<00:33:15.880> and<00:33:16.150> GAF<00:33:16.540> within<00:33:17.350> the 00:33:17.460 --> 00:33:17.470 align:start position:0% of a Tyrian client and GAF within the 00:33:17.470 --> 00:33:19.950 align:start position:0% of a Tyrian client and GAF within the pre<00:33:17.680> quest<00:33:18.040> that<00:33:18.280> was<00:33:18.490> submitted<00:33:19.030> supports 00:33:19.950 --> 00:33:19.960 align:start position:0% pre quest that was submitted supports 00:33:19.960 --> 00:33:23.730 align:start position:0% pre quest that was submitted supports EVM<00:33:20.320> C<00:33:20.590> and<00:33:20.830> on<00:33:21.640> the<00:33:21.760> VM<00:33:22.030> side<00:33:22.300> we<00:33:23.110> have<00:33:23.350> a<00:33:23.590> live 00:33:23.730 --> 00:33:23.740 align:start position:0% EVM C and on the VM side we have a live 00:33:23.740 --> 00:33:25.620 align:start position:0% EVM C and on the VM side we have a live interpreter<00:33:24.100> which<00:33:24.610> is<00:33:24.760> part<00:33:25.030> of<00:33:25.180> a<00:33:25.480> live 00:33:25.620 --> 00:33:25.630 align:start position:0% interpreter which is part of a live 00:33:25.630 --> 00:33:28.670 align:start position:0% interpreter which is part of a live product<00:33:25.930> and<00:33:26.500> also<00:33:27.310> here<00:33:27.580> that<00:33:27.820> suppose<00:33:28.180> that 00:33:28.670 --> 00:33:28.680 align:start position:0% product and also here that suppose that 00:33:28.680 --> 00:33:33.330 align:start position:0% product and also here that suppose that currently<00:33:29.680> and<00:33:31.110> there<00:33:32.110> is<00:33:32.260> there<00:33:32.920> is<00:33:32.950> a<00:33:33.040> node 00:33:33.330 --> 00:33:33.340 align:start position:0% currently and there is there is a node 00:33:33.340 --> 00:33:36.150 align:start position:0% currently and there is there is a node that<00:33:33.610> actually<00:33:34.060> uses<00:33:34.900> this<00:33:35.080> gaff<00:33:35.440> plus<00:33:35.740> a<00:33:35.920> live 00:33:36.150 --> 00:33:36.160 align:start position:0% that actually uses this gaff plus a live 00:33:36.160 --> 00:33:39.740 align:start position:0% that actually uses this gaff plus a live interpreter<00:33:36.510> combination<00:33:37.510> that<00:33:37.750> it's<00:33:38.500> fully 00:33:39.740 --> 00:33:39.750 align:start position:0% interpreter combination that it's fully 00:33:39.750 --> 00:33:42.930 align:start position:0% interpreter combination that it's fully production<00:33:40.750> ready<00:33:40.900> and<00:33:41.770> can<00:33:42.190> be<00:33:42.370> used<00:33:42.520> on<00:33:42.880> the 00:33:42.930 --> 00:33:42.940 align:start position:0% production ready and can be used on the 00:33:42.940 --> 00:33:45.690 align:start position:0% production ready and can be used on the minute<00:33:43.420> I<00:33:43.690> have<00:33:44.170> one<00:33:44.410> node<00:33:44.830> running<00:33:45.280> myself 00:33:45.690 --> 00:33:45.700 align:start position:0% minute I have one node running myself 00:33:45.700 --> 00:33:49.590 align:start position:0% minute I have one node running myself and<00:33:46.440> we<00:33:47.440> using<00:33:48.160> graph<00:33:48.490> and<00:33:48.790> here<00:33:49.570> a 00:33:49.590 --> 00:33:49.600 align:start position:0% and we using graph and here a 00:33:49.600 --> 00:33:54.150 align:start position:0% and we using graph and here a combination<00:33:50.790> to<00:33:51.790> run<00:33:52.540> the<00:33:52.960> it<00:33:53.560> wasn't<00:33:53.980> test 00:33:54.150 --> 00:33:54.160 align:start position:0% combination to run the it wasn't test 00:33:54.160 --> 00:34:01.290 align:start position:0% combination to run the it wasn't test net<00:33:56.580> and<00:33:57.580> some<00:33:58.030> of<00:33:58.180> the<00:33:59.250> plans<00:34:00.250> but<00:34:00.670> I<00:34:00.940> chained 00:34:01.290 --> 00:34:01.300 align:start position:0% net and some of the plans but I chained 00:34:01.300 --> 00:34:03.330 align:start position:0% net and some of the plans but I chained it<00:34:01.390> to<00:34:01.600> wishes<00:34:01.960> because<00:34:02.170> there<00:34:03.130> is<00:34:03.190> no 00:34:03.330 --> 00:34:03.340 align:start position:0% it to wishes because there is no 00:34:03.340 --> 00:34:05.430 align:start position:0% it to wishes because there is no commitment<00:34:03.640> to<00:34:03.970> that<00:34:04.120> it<00:34:04.360> kind<00:34:04.810> of<00:34:04.900> works<00:34:05.110> in 00:34:05.430 --> 00:34:05.440 align:start position:0% commitment to that it kind of works in 00:34:05.440 --> 00:34:09.720 align:start position:0% commitment to that it kind of works in the<00:34:07.080> reactive<00:34:08.080> way<00:34:08.260> so<00:34:08.620> if<00:34:08.919> if<00:34:09.310> you<00:34:09.490> would<00:34:09.580> like 00:34:09.720 --> 00:34:09.730 align:start position:0% the reactive way so if if you would like 00:34:09.730 --> 00:34:13.770 align:start position:0% the reactive way so if if you would like to<00:34:09.909> have<00:34:11.730> to<00:34:12.730> bring<00:34:12.940> this<00:34:13.120> support<00:34:13.570> to<00:34:13.600> your 00:34:13.770 --> 00:34:13.780 align:start position:0% to have to bring this support to your 00:34:13.780 --> 00:34:16.110 align:start position:0% to have to bring this support to your projects<00:34:14.440> or<00:34:14.560> you<00:34:14.679> need<00:34:14.919> some<00:34:15.220> other<00:34:15.460> language 00:34:16.110 --> 00:34:16.120 align:start position:0% projects or you need some other language 00:34:16.120 --> 00:34:16.909 align:start position:0% projects or you need some other language bindings 00:34:16.909 --> 00:34:16.919 align:start position:0% bindings 00:34:16.919 --> 00:34:21.389 align:start position:0% bindings please<00:34:17.919> express<00:34:18.370> this<00:34:19.230> its<00:34:20.230> needs<00:34:20.530> and<00:34:20.800> we're 00:34:21.389 --> 00:34:21.399 align:start position:0% please express this its needs and we're 00:34:21.399 --> 00:34:29.220 align:start position:0% please express this its needs and we're happy<00:34:21.639> to<00:34:21.820> have<00:34:25.379> and<00:34:26.379> this<00:34:26.950> is<00:34:27.129> like<00:34:27.970> way<00:34:28.330> when 00:34:29.220 --> 00:34:29.230 align:start position:0% happy to have and this is like way when 00:34:29.230 --> 00:34:30.899 align:start position:0% happy to have and this is like way when you<00:34:29.590> can<00:34:29.770> you<00:34:29.980> can<00:34:30.159> learn<00:34:30.280> more<00:34:30.490> about<00:34:30.639> the 00:34:30.899 --> 00:34:30.909 align:start position:0% you can you can learn more about the 00:34:30.909 --> 00:34:33.450 align:start position:0% you can you can learn more about the project<00:34:31.120> where<00:34:31.990> you<00:34:32.139> can<00:34:32.290> find<00:34:32.560> documentation 00:34:33.450 --> 00:34:33.460 align:start position:0% project where you can find documentation 00:34:33.460 --> 00:34:37.290 align:start position:0% project where you can find documentation the<00:34:34.379> implementation<00:34:35.379> guides<00:34:35.679> both<00:34:36.669> for<00:34:37.000> vm 00:34:37.290 --> 00:34:37.300 align:start position:0% the implementation guides both for vm 00:34:37.300 --> 00:34:40.770 align:start position:0% the implementation guides both for vm site<00:34:37.600> and<00:34:38.020> for<00:34:38.560> host<00:34:38.800> site<00:34:39.100> some<00:34:39.940> examples<00:34:40.540> and 00:34:40.770 --> 00:34:40.780 align:start position:0% site and for host site some examples and 00:34:40.780 --> 00:34:44.180 align:start position:0% site and for host site some examples and chat<00:34:41.290> room<00:34:41.500> when<00:34:41.800> we<00:34:42.250> are<00:34:42.370> available 00:34:44.180 --> 00:34:44.190 align:start position:0% chat room when we are available 00:34:44.190 --> 00:34:47.399 align:start position:0% chat room when we are available so<00:34:45.190> from<00:34:45.460> that<00:34:45.639> I<00:34:46.000> would<00:34:46.269> like<00:34:46.779> to<00:34:46.809> go<00:34:47.109> to<00:34:47.169> this 00:34:47.399 --> 00:34:47.409 align:start position:0% so from that I would like to go to this 00:34:47.409 --> 00:34:51.149 align:start position:0% so from that I would like to go to this second<00:34:47.980> part<00:34:48.279> of<00:34:48.399> the<00:34:48.519> talk<00:34:48.730> and<00:34:49.950> spend<00:34:50.950> very 00:34:51.149 --> 00:34:51.159 align:start position:0% second part of the talk and spend very 00:34:51.159 --> 00:34:53.700 align:start position:0% second part of the talk and spend very little<00:34:51.309> time<00:34:51.490> on<00:34:51.730> explaining<00:34:52.599> how<00:34:53.470> this 00:34:53.700 --> 00:34:53.710 align:start position:0% little time on explaining how this 00:34:53.710 --> 00:34:58.250 align:start position:0% little time on explaining how this affect<00:34:54.339> it<00:34:54.760> wasn't<00:34:55.149> designed<00:34:55.269> to<00:34:55.629> some<00:34:55.899> sense 00:34:58.250 --> 00:34:58.260 align:start position:0% 00:34:58.260 --> 00:35:03.000 align:start position:0% so<00:34:59.910> I'd<00:35:00.910> like<00:35:01.119> to<00:35:01.359> put<00:35:02.289> your<00:35:02.410> attention<00:35:02.529> on 00:35:03.000 --> 00:35:03.010 align:start position:0% so I'd like to put your attention on 00:35:03.010 --> 00:35:05.670 align:start position:0% so I'd like to put your attention on three<00:35:03.339> three<00:35:03.730> aspects<00:35:04.210> of<00:35:04.559> starting<00:35:05.559> with 00:35:05.670 --> 00:35:05.680 align:start position:0% three three aspects of starting with 00:35:05.680 --> 00:35:08.759 align:start position:0% three three aspects of starting with Viviane<00:35:06.010> that<00:35:06.460> this<00:35:07.089> kind<00:35:07.720> of<00:35:07.839> special<00:35:08.319> opcode 00:35:08.759 --> 00:35:08.769 align:start position:0% Viviane that this kind of special opcode 00:35:08.769 --> 00:35:13.220 align:start position:0% Viviane that this kind of special opcode stir<00:35:09.420> that<00:35:10.420> I<00:35:10.660> know<00:35:10.809> it's<00:35:10.960> many<00:35:11.170> people<00:35:11.619> but 00:35:13.220 --> 00:35:13.230 align:start position:0% stir that I know it's many people but 00:35:13.230 --> 00:35:16.980 align:start position:0% stir that I know it's many people but and<00:35:14.430> how<00:35:15.430> they<00:35:15.640> map<00:35:15.880> and<00:35:16.210> I<00:35:16.630> would<00:35:16.779> like<00:35:16.869> to 00:35:16.980 --> 00:35:16.990 align:start position:0% and how they map and I would like to 00:35:16.990 --> 00:35:19.710 align:start position:0% and how they map and I would like to explain<00:35:17.349> how<00:35:17.410> they<00:35:17.710> map<00:35:17.920> to<00:35:17.950> be<00:35:18.549> BMC<00:35:19.390> design 00:35:19.710 --> 00:35:19.720 align:start position:0% explain how they map to be BMC design 00:35:19.720 --> 00:35:25.109 align:start position:0% explain how they map to be BMC design and<00:35:19.990> both<00:35:20.880> the<00:35:22.109> awasum<00:35:23.109> design<00:35:23.789> so<00:35:24.789> this 00:35:25.109 --> 00:35:25.119 align:start position:0% and both the awasum design so this 00:35:25.119 --> 00:35:29.960 align:start position:0% and both the awasum design so this special<00:35:25.539> instructions<00:35:26.380> I<00:35:26.500> mean<00:35:26.740> are<00:35:27.900> from 00:35:29.960 --> 00:35:29.970 align:start position:0% special instructions I mean are from 00:35:29.970 --> 00:35:35.279 align:start position:0% special instructions I mean are from some<00:35:32.460> some<00:35:33.460> instructions<00:35:34.210> that<00:35:34.359> allows<00:35:34.960> you 00:35:35.279 --> 00:35:35.289 align:start position:0% some some instructions that allows you 00:35:35.289 --> 00:35:37.410 align:start position:0% some some instructions that allows you from<00:35:35.619> the<00:35:35.769> car<00:35:35.950> from<00:35:36.160> the<00:35:36.490> contract<00:35:36.970> execution 00:35:37.410 --> 00:35:37.420 align:start position:0% from the car from the contract execution 00:35:37.420 --> 00:35:40.140 align:start position:0% from the car from the contract execution to<00:35:38.140> access<00:35:38.589> et<00:35:38.829> on<00:35:39.190> state<00:35:39.490> and<00:35:39.789> some<00:35:39.970> other 00:35:40.140 --> 00:35:40.150 align:start position:0% to access et on state and some other 00:35:40.150 --> 00:35:42.120 align:start position:0% to access et on state and some other environment<00:35:40.960> information<00:35:41.289> about<00:35:41.859> what's 00:35:42.120 --> 00:35:42.130 align:start position:0% environment information about what's 00:35:42.130 --> 00:35:44.910 align:start position:0% environment information about what's going<00:35:42.220> on<00:35:42.549> currently<00:35:42.849> on<00:35:43.450> the<00:35:43.869> blockchain<00:35:44.079> so 00:35:44.910 --> 00:35:44.920 align:start position:0% going on currently on the blockchain so 00:35:44.920 --> 00:35:47.910 align:start position:0% going on currently on the blockchain so you<00:35:44.980> are<00:35:45.160> allowed<00:35:45.369> to<00:35:45.720> put<00:35:46.720> some<00:35:46.960> data<00:35:47.140> in<00:35:47.710> this 00:35:47.910 --> 00:35:47.920 align:start position:0% you are allowed to put some data in this 00:35:47.920 --> 00:35:51.720 align:start position:0% you are allowed to put some data in this database<00:35:48.509> called<00:35:49.509> storage<00:35:50.190> read<00:35:51.190> data<00:35:51.519> from 00:35:51.720 --> 00:35:51.730 align:start position:0% database called storage read data from 00:35:51.730 --> 00:35:54.420 align:start position:0% database called storage read data from there<00:35:52.150> and<00:35:52.480> check<00:35:53.349> the<00:35:53.529> balances<00:35:54.069> of<00:35:54.220> other 00:35:54.420 --> 00:35:54.430 align:start position:0% there and check the balances of other 00:35:54.430 --> 00:36:02.160 align:start position:0% there and check the balances of other accounts<00:35:55.119> and<00:35:55.359> many<00:35:55.599> other<00:35:55.869> things<00:35:59.490> and<00:36:01.170> just 00:36:02.160 --> 00:36:02.170 align:start position:0% accounts and many other things and just 00:36:02.170 --> 00:36:04.859 align:start position:0% accounts and many other things and just for<00:36:02.710> this<00:36:02.859> example<00:36:03.400> I<00:36:04.029> will<00:36:04.059> focus<00:36:04.390> on<00:36:04.750> this 00:36:04.859 --> 00:36:04.869 align:start position:0% for this example I will focus on this 00:36:04.869 --> 00:36:11.970 align:start position:0% for this example I will focus on this float<00:36:05.740> and<00:36:06.009> Esther<00:36:08.160> and<00:36:09.930> so<00:36:10.930> because<00:36:11.470> this<00:36:11.799> is 00:36:11.970 --> 00:36:11.980 align:start position:0% float and Esther and so because this is 00:36:11.980 --> 00:36:16.190 align:start position:0% float and Esther and so because this is this<00:36:12.730> storage<00:36:13.660> access<00:36:14.019> is<00:36:14.529> it's<00:36:15.309> required<00:36:15.789> for 00:36:16.190 --> 00:36:16.200 align:start position:0% this storage access is it's required for 00:36:16.200 --> 00:36:18.870 align:start position:0% this storage access is it's required for contract<00:36:17.200> execution<00:36:17.680> but<00:36:18.069> it's<00:36:18.220> not<00:36:18.519> about 00:36:18.870 --> 00:36:18.880 align:start position:0% contract execution but it's not about 00:36:18.880 --> 00:36:21.150 align:start position:0% contract execution but it's not about the<00:36:19.119> execution<00:36:19.359> itself<00:36:20.049> it's<00:36:20.829> a<00:36:20.980> way<00:36:21.099> to 00:36:21.150 --> 00:36:21.160 align:start position:0% the execution itself it's a way to 00:36:21.160 --> 00:36:23.960 align:start position:0% the execution itself it's a way to access<00:36:21.700> some<00:36:21.880> data<00:36:22.089> that<00:36:22.240> is<00:36:22.569> outside<00:36:23.109> of<00:36:23.349> this 00:36:23.960 --> 00:36:23.970 align:start position:0% access some data that is outside of this 00:36:23.970 --> 00:36:26.789 align:start position:0% access some data that is outside of this virtual<00:36:24.970> machine<00:36:25.059> that<00:36:25.390> it's<00:36:26.200> it's 00:36:26.789 --> 00:36:26.799 align:start position:0% virtual machine that it's it's 00:36:26.799 --> 00:36:31.440 align:start position:0% virtual machine that it's it's conducting<00:36:27.579> execution<00:36:28.289> so<00:36:29.289> for<00:36:30.299> example<00:36:31.299> in 00:36:31.440 --> 00:36:31.450 align:start position:0% conducting execution so for example in 00:36:31.450 --> 00:36:35.339 align:start position:0% conducting execution so for example in EVs<00:36:31.900> Eve<00:36:32.230> EMC<00:36:33.480> design<00:36:34.480> we<00:36:34.660> have<00:36:34.839> to<00:36:35.019> provide 00:36:35.339 --> 00:36:35.349 align:start position:0% EVs Eve EMC design we have to provide 00:36:35.349 --> 00:36:38.640 align:start position:0% EVs Eve EMC design we have to provide that<00:36:35.410> so<00:36:35.829> this<00:36:36.009> is<00:36:36.390> like<00:36:37.390> one<00:36:37.690> of<00:36:37.720> the<00:36:37.869> required 00:36:38.640 --> 00:36:38.650 align:start position:0% that so this is like one of the required 00:36:38.650 --> 00:36:41.670 align:start position:0% that so this is like one of the required methods<00:36:39.279> the<00:36:40.000> host<00:36:40.269> has<00:36:40.599> to<00:36:40.839> implement<00:36:41.140> to 00:36:41.670 --> 00:36:41.680 align:start position:0% methods the host has to implement to 00:36:41.680 --> 00:36:44.940 align:start position:0% methods the host has to implement to allow<00:36:41.890> contracts<00:36:42.700> to<00:36:42.880> access<00:36:43.240> that<00:36:43.390> and<00:36:43.950> we 00:36:44.940 --> 00:36:44.950 align:start position:0% allow contracts to access that and we 00:36:44.950 --> 00:36:47.549 align:start position:0% allow contracts to access that and we cannot<00:36:45.220> provide<00:36:45.640> this<00:36:45.849> this<00:36:46.359> this<00:36:47.259> data 00:36:47.549 --> 00:36:47.559 align:start position:0% cannot provide this this this data 00:36:47.559 --> 00:36:51.089 align:start position:0% cannot provide this this this data upfront<00:36:48.130> because<00:36:48.509> that<00:36:49.509> would<00:36:49.720> be<00:36:49.900> we<00:36:50.500> don't 00:36:51.089 --> 00:36:51.099 align:start position:0% upfront because that would be we don't 00:36:51.099 --> 00:36:54.390 align:start position:0% upfront because that would be we don't know<00:36:51.309> which<00:36:51.970> exactly<00:36:52.630> portion<00:36:53.619> of<00:36:53.710> data<00:36:53.950> would 00:36:54.390 --> 00:36:54.400 align:start position:0% know which exactly portion of data would 00:36:54.400 --> 00:36:56.670 align:start position:0% know which exactly portion of data would be<00:36:54.609> needed<00:36:54.910> for<00:36:55.059> execution 00:36:56.670 --> 00:36:56.680 align:start position:0% be needed for execution 00:36:56.680 --> 00:37:00.160 align:start position:0% be needed for execution so<00:36:57.680> this<00:36:58.370> is<00:36:58.550> this<00:36:58.850> is<00:36:58.970> also<00:36:59.180> taken<00:36:59.660> from<00:36:59.690> gold 00:37:00.160 --> 00:37:00.170 align:start position:0% so this is this is also taken from gold 00:37:00.170 --> 00:37:03.970 align:start position:0% so this is this is also taken from gold bindings<00:37:00.710> of<00:37:01.150> EVM<00:37:02.150> C<00:37:02.420> and<00:37:02.720> this<00:37:03.320> is<00:37:03.380> there<00:37:03.890> are 00:37:03.970 --> 00:37:03.980 align:start position:0% bindings of EVM C and this is there are 00:37:03.980 --> 00:37:07.510 align:start position:0% bindings of EVM C and this is there are two<00:37:04.190> functions<00:37:04.430> that<00:37:04.850> this<00:37:05.150> host<00:37:05.500> class<00:37:06.520> has 00:37:07.510 --> 00:37:07.520 align:start position:0% two functions that this host class has 00:37:07.520 --> 00:37:17.260 align:start position:0% two functions that this host class has to<00:37:08.620> have<00:37:09.620> to<00:37:09.830> provide<00:37:10.190> for<00:37:11.080> four<00:37:12.080> VMs<00:37:14.980> and<00:37:16.270> and 00:37:17.260 --> 00:37:17.270 align:start position:0% to have to provide for four VMs and and 00:37:17.270 --> 00:37:21.790 align:start position:0% to have to provide for four VMs and and when<00:37:17.630> we<00:37:17.780> go<00:37:17.960> to<00:37:18.760> USM<00:37:19.760> and<00:37:20.080> precisely<00:37:21.080> to<00:37:21.560> this 00:37:21.790 --> 00:37:21.800 align:start position:0% when we go to USM and precisely to this 00:37:21.800 --> 00:37:25.500 align:start position:0% when we go to USM and precisely to this material<00:37:22.580> in<00:37:23.180> the<00:37:23.590> environment<00:37:24.590> interface 00:37:25.500 --> 00:37:25.510 align:start position:0% material in the environment interface 00:37:25.510 --> 00:37:28.810 align:start position:0% material in the environment interface this<00:37:26.510> is<00:37:26.570> a<00:37:26.720> part<00:37:27.080> of<00:37:27.290> us<00:37:27.800> and<00:37:28.190> that<00:37:28.370> tries<00:37:28.790> to 00:37:28.810 --> 00:37:28.820 align:start position:0% this is a part of us and that tries to 00:37:28.820 --> 00:37:32.590 align:start position:0% this is a part of us and that tries to describe<00:37:29.710> very<00:37:30.710> similar<00:37:31.190> aspect<00:37:32.030> of<00:37:32.150> that 00:37:32.590 --> 00:37:32.600 align:start position:0% describe very similar aspect of that 00:37:32.600 --> 00:37:36.280 align:start position:0% describe very similar aspect of that so<00:37:32.840> how<00:37:33.490> code<00:37:34.490> written<00:37:34.790> in<00:37:35.090> webassembly<00:37:35.810> can 00:37:36.280 --> 00:37:36.290 align:start position:0% so how code written in webassembly can 00:37:36.290 --> 00:37:41.410 align:start position:0% so how code written in webassembly can access<00:37:39.040> environment<00:37:40.040> and<00:37:40.250> information<00:37:41.240> that 00:37:41.410 --> 00:37:41.420 align:start position:0% access environment and information that 00:37:41.420 --> 00:37:45.850 align:start position:0% access environment and information that are<00:37:41.630> specific<00:37:42.290> to<00:37:42.320> aterial<00:37:43.360> so<00:37:44.360> here<00:37:44.800> this<00:37:45.800> is 00:37:45.850 --> 00:37:45.860 align:start position:0% are specific to aterial so here this is 00:37:45.860 --> 00:37:49.510 align:start position:0% are specific to aterial so here this is a<00:37:46.430> snippet<00:37:47.000> of<00:37:47.890> webassembly<00:37:48.890> text 00:37:49.510 --> 00:37:49.520 align:start position:0% a snippet of webassembly text 00:37:49.520 --> 00:37:52.210 align:start position:0% a snippet of webassembly text representation<00:37:49.940> and<00:37:50.620> mostly<00:37:51.620> what<00:37:51.740> it<00:37:51.770> shows 00:37:52.210 --> 00:37:52.220 align:start position:0% representation and mostly what it shows 00:37:52.220 --> 00:37:55.810 align:start position:0% representation and mostly what it shows its<00:37:53.440> first<00:37:54.440> of<00:37:54.620> all<00:37:54.770> this<00:37:55.100> notion<00:37:55.610> of 00:37:55.810 --> 00:37:55.820 align:start position:0% its first of all this notion of 00:37:55.820 --> 00:37:59.050 align:start position:0% its first of all this notion of important<00:37:56.810> functions<00:37:56.990> in<00:37:57.500> any<00:37:58.310> web<00:37:58.550> assembly 00:37:59.050 --> 00:37:59.060 align:start position:0% important functions in any web assembly 00:37:59.060 --> 00:38:03.360 align:start position:0% important functions in any web assembly so<00:37:59.720> this<00:38:00.170> these<00:38:00.500> are<00:38:00.650> functions<00:38:01.220> that<00:38:01.780> given 00:38:03.360 --> 00:38:03.370 align:start position:0% so this these are functions that given 00:38:03.370 --> 00:38:08.380 align:start position:0% so this these are functions that given webassembly<00:38:04.370> binary<00:38:06.700> specify<00:38:07.700> and<00:38:08.000> required 00:38:08.380 --> 00:38:08.390 align:start position:0% webassembly binary specify and required 00:38:08.390 --> 00:38:13.030 align:start position:0% webassembly binary specify and required for<00:38:08.690> execution<00:38:09.350> so<00:38:09.830> every<00:38:11.200> every<00:38:12.200> contract 00:38:13.030 --> 00:38:13.040 align:start position:0% for execution so every every contract 00:38:13.040 --> 00:38:15.580 align:start position:0% for execution so every every contract with<00:38:13.310> possibly<00:38:13.670> written<00:38:13.880> contract<00:38:14.540> we<00:38:15.260> need 00:38:15.580 --> 00:38:15.590 align:start position:0% with possibly written contract we need 00:38:15.590 --> 00:38:19.870 align:start position:0% with possibly written contract we need will<00:38:16.010> have<00:38:16.340> a<00:38:16.610> set<00:38:17.090> of<00:38:17.240> these<00:38:17.480> and<00:38:18.880> probably 00:38:19.870 --> 00:38:19.880 align:start position:0% will have a set of these and probably 00:38:19.880 --> 00:38:24.040 align:start position:0% will have a set of these and probably will<00:38:20.390> specify<00:38:20.660> that<00:38:21.170> okay<00:38:21.740> I<00:38:21.770> need<00:38:22.120> this<00:38:23.120> this 00:38:24.040 --> 00:38:24.050 align:start position:0% will specify that okay I need this this 00:38:24.050 --> 00:38:27.550 align:start position:0% will specify that okay I need this this function<00:38:24.260> is<00:38:24.560> provided<00:38:24.770> by<00:38:25.720> the<00:38:26.720> ID<00:38:26.780> the 00:38:27.550 --> 00:38:27.560 align:start position:0% function is provided by the ID the 00:38:27.560 --> 00:38:29.650 align:start position:0% function is provided by the ID the environment<00:38:28.190> I'm<00:38:28.370> running<00:38:28.670> it<00:38:28.880> to<00:38:29.450> access 00:38:29.650 --> 00:38:29.660 align:start position:0% environment I'm running it to access 00:38:29.660 --> 00:38:37.480 align:start position:0% environment I'm running it to access some<00:38:30.370> ethereal<00:38:31.370> specific<00:38:32.090> information<00:38:36.490> and 00:38:37.480 --> 00:38:37.490 align:start position:0% some ethereal specific information and 00:38:37.490 --> 00:38:40.210 align:start position:0% some ethereal specific information and to<00:38:38.390> learn<00:38:38.510> more<00:38:39.110> about<00:38:39.170> that<00:38:39.560> there<00:38:40.100> is<00:38:40.190> a 00:38:40.210 --> 00:38:40.220 align:start position:0% to learn more about that there is a 00:38:40.220 --> 00:38:43.830 align:start position:0% to learn more about that there is a section<00:38:40.730> if<00:38:40.940> in<00:38:41.330> the<00:38:41.630> design<00:38:42.260> design<00:38:42.920> repo<00:38:43.490> of 00:38:43.830 --> 00:38:43.840 align:start position:0% section if in the design design repo of 00:38:43.840 --> 00:38:47.380 align:start position:0% section if in the design design repo of of<00:38:44.840> it<00:38:45.170> wasn't<00:38:45.560> so<00:38:46.160> I'm<00:38:46.580> occurring<00:38:46.970> to<00:38:47.060> you<00:38:47.120> to 00:38:47.380 --> 00:38:47.390 align:start position:0% of it wasn't so I'm occurring to you to 00:38:47.390 --> 00:38:49.720 align:start position:0% of it wasn't so I'm occurring to you to check<00:38:48.020> out<00:38:48.170> all<00:38:48.470> other<00:38:48.860> methods<00:38:49.190> that<00:38:49.460> are 00:38:49.720 --> 00:38:49.730 align:start position:0% check out all other methods that are 00:38:49.730 --> 00:38:52.390 align:start position:0% check out all other methods that are there<00:38:49.910> and<00:38:50.180> maybe<00:38:51.080> leave<00:38:51.350> some<00:38:51.560> comments<00:38:52.100> if 00:38:52.390 --> 00:38:52.400 align:start position:0% there and maybe leave some comments if 00:38:52.400 --> 00:38:55.270 align:start position:0% there and maybe leave some comments if you<00:38:52.640> think<00:38:52.970> we<00:38:53.810> can<00:38:53.960> do<00:38:54.170> but<00:38:54.350> I<00:38:54.560> mean<00:38:54.680> most<00:38:55.130> of 00:38:55.270 --> 00:38:55.280 align:start position:0% you think we can do but I mean most of 00:38:55.280 --> 00:38:58.900 align:start position:0% you think we can do but I mean most of them<00:38:55.490> map<00:38:56.120> more<00:38:56.870> or<00:38:56.960> less<00:38:57.080> directly<00:38:57.260> to<00:38:57.910> EVM 00:38:58.900 --> 00:38:58.910 align:start position:0% them map more or less directly to EVM 00:38:58.910 --> 00:39:02.230 align:start position:0% them map more or less directly to EVM semantics<00:38:59.540> because<00:38:59.960> I<00:39:00.700> mean<00:39:01.700> there's<00:39:01.910> many 00:39:02.230 --> 00:39:02.240 align:start position:0% semantics because I mean there's many 00:39:02.240 --> 00:39:04.900 align:start position:0% semantics because I mean there's many reasons<00:39:02.630> for<00:39:02.810> that<00:39:02.960> one<00:39:03.290> of<00:39:03.410> them<00:39:03.590> was<00:39:03.830> to<00:39:04.670> have 00:39:04.900 --> 00:39:04.910 align:start position:0% reasons for that one of them was to have 00:39:04.910 --> 00:39:10.060 align:start position:0% reasons for that one of them was to have full<00:39:05.240> compatibility<00:39:05.690> with<00:39:06.350> EVM<00:39:07.840> that<00:39:08.840> is 00:39:10.060 --> 00:39:10.070 align:start position:0% full compatibility with EVM that is 00:39:10.070 --> 00:39:13.030 align:start position:0% full compatibility with EVM that is now<00:39:10.870> questionable<00:39:11.870> if<00:39:12.080> we<00:39:12.260> want<00:39:12.440> it<00:39:12.650> or<00:39:12.830> not 00:39:13.030 --> 00:39:13.040 align:start position:0% now questionable if we want it or not 00:39:13.040 --> 00:39:16.720 align:start position:0% now questionable if we want it or not but<00:39:13.460> if<00:39:14.090> you<00:39:14.240> have<00:39:14.420> opinion<00:39:14.810> about<00:39:15.020> that<00:39:15.730> yeah 00:39:16.720 --> 00:39:16.730 align:start position:0% but if you have opinion about that yeah 00:39:16.730 --> 00:39:18.820 align:start position:0% but if you have opinion about that yeah this<00:39:17.000> is<00:39:17.150> the<00:39:17.300> place<00:39:17.510> you<00:39:17.870> can<00:39:17.900> find<00:39:18.620> more 00:39:18.820 --> 00:39:18.830 align:start position:0% this is the place you can find more 00:39:18.830 --> 00:39:22.320 align:start position:0% this is the place you can find more information<00:39:20.470> okay<00:39:21.470> that's<00:39:21.740> all<00:39:21.890> for<00:39:22.040> me 00:39:22.320 --> 00:39:22.330 align:start position:0% information okay that's all for me 00:39:22.330 --> 00:39:24.610 align:start position:0% information okay that's all for me thanks<00:39:23.330> for<00:39:23.510> attention 00:39:24.610 --> 00:39:24.620 align:start position:0% thanks for attention 00:39:24.620 --> 00:39:31.950 align:start position:0% thanks for attention [Applause] 00:39:31.950 --> 00:39:31.960 align:start position:0% [Applause] 00:39:31.960 --> 00:39:35.320 align:start position:0% [Applause] thank<00:39:32.960> you<00:39:33.050> Powell<00:39:33.410> that<00:39:33.530> was<00:39:33.680> great<00:39:34.180> what<00:39:35.180> if 00:39:35.320 --> 00:39:35.330 align:start position:0% thank you Powell that was great what if 00:39:35.330 --> 00:39:37.210 align:start position:0% thank you Powell that was great what if you<00:39:35.450> don't<00:39:35.570> know<00:39:35.840> does<00:39:36.320> it<00:39:36.350> work<00:39:36.770> and<00:39:36.950> you<00:39:37.010> yes 00:39:37.210 --> 00:39:37.220 align:start position:0% you don't know does it work and you yes 00:39:37.220 --> 00:39:38.470 align:start position:0% you don't know does it work and you yes okay 00:39:38.470 --> 00:39:38.480 align:start position:0% okay 00:39:38.480 --> 00:39:40.510 align:start position:0% okay most<00:39:38.930> of<00:39:39.050> you<00:39:39.140> don't<00:39:39.230> know<00:39:39.410> that<00:39:39.650> without<00:39:40.040> evm 00:39:40.510 --> 00:39:40.520 align:start position:0% most of you don't know that without evm 00:39:40.520 --> 00:39:43.030 align:start position:0% most of you don't know that without evm see<00:39:40.850> we<00:39:41.360> wouldn't<00:39:41.600> have<00:39:41.720> been<00:39:41.870> able<00:39:41.990> to<00:39:42.140> enable 00:39:43.030 --> 00:39:43.040 align:start position:0% see we wouldn't have been able to enable 00:39:43.040 --> 00:39:46.540 align:start position:0% see we wouldn't have been able to enable to<00:39:43.310> test<00:39:43.520> Anton<00:39:43.790> both<00:39:44.300> Alice<00:39:44.840> and<00:39:44.870> gif<00:39:45.500> so<00:39:46.400> it's 00:39:46.540 --> 00:39:46.550 align:start position:0% to test Anton both Alice and gif so it's 00:39:46.550 --> 00:39:48.040 align:start position:0% to test Anton both Alice and gif so it's a<00:39:46.640> really<00:39:46.790> important<00:39:47.180> project 00:39:48.040 --> 00:39:48.050 align:start position:0% a really important project 00:39:48.050 --> 00:39:50.650 align:start position:0% a really important project please<00:39:48.620> check<00:39:48.830> the<00:39:48.980> repo<00:39:49.310> pavel<00:39:50.210> has<00:39:50.390> shown 00:39:50.650 --> 00:39:50.660 align:start position:0% please check the repo pavel has shown 00:39:50.660 --> 00:39:53.590 align:start position:0% please check the repo pavel has shown and<00:39:50.960> it<00:39:51.650> is<00:39:51.830> the<00:39:51.980> way<00:39:52.100> to<00:39:52.130> get<00:39:52.700> rapid<00:39:53.180> support 00:39:53.590 --> 00:39:53.600 align:start position:0% and it is the way to get rapid support 00:39:53.600 --> 00:39:56.500 align:start position:0% and it is the way to get rapid support for<00:39:53.780> he<00:39:53.870> wasn't<00:39:54.230> in<00:39:54.410> any<00:39:54.590> new<00:39:54.770> client<00:39:55.270> and<00:39:56.270> now 00:39:56.500 --> 00:39:56.510 align:start position:0% for he wasn't in any new client and now 00:39:56.510 --> 00:39:58.540 align:start position:0% for he wasn't in any new client and now the<00:39:57.440> the<00:39:57.710> most<00:39:57.860> important<00:39:58.190> but<00:39:58.280> you<00:39:58.370> want<00:39:58.520> to 00:39:58.540 --> 00:39:58.550 align:start position:0% the the most important but you want to 00:39:58.550 --> 00:40:00.550 align:start position:0% the the most important but you want to load<00:39:58.700> the<00:39:58.790> video<00:39:58.880> the<00:39:59.630> most<00:39:59.870> important<00:40:00.260> part 00:40:00.550 --> 00:40:00.560 align:start position:0% load the video the most important part 00:40:00.560 --> 00:40:05.860 align:start position:0% load the video the most important part is<00:40:00.770> the<00:40:01.010> test<00:40:01.400> net<00:40:01.750> so<00:40:02.750> we<00:40:02.870> have<00:40:02.990> Jared<00:40:04.870> welcome 00:40:05.860 --> 00:40:05.870 align:start position:0% is the test net so we have Jared welcome 00:40:05.870 --> 00:40:09.360 align:start position:0% is the test net so we have Jared welcome Jared 00:40:09.360 --> 00:40:09.370 align:start position:0% 00:40:09.370 --> 00:40:12.310 align:start position:0% so<00:40:10.370> Jared<00:40:10.640> started<00:40:10.910> working<00:40:11.180> on<00:40:11.210> it<00:40:11.390> to<00:40:11.600> MJS<00:40:12.050> he 00:40:12.310 --> 00:40:12.320 align:start position:0% so Jared started working on it to MJS he 00:40:12.320 --> 00:40:14.380 align:start position:0% so Jared started working on it to MJS he did<00:40:12.440> a<00:40:12.470> lot<00:40:12.650> of<00:40:12.710> the<00:40:12.980> VM<00:40:13.220> work<00:40:13.370> at<00:40:13.490> TT<00:40:13.730> MJS<00:40:14.120> and 00:40:14.380 --> 00:40:14.390 align:start position:0% did a lot of the VM work at TT MJS and 00:40:14.390 --> 00:40:16.000 align:start position:0% did a lot of the VM work at TT MJS and then<00:40:14.600> he<00:40:14.780> also<00:40:14.900> did<00:40:15.110> a<00:40:15.140> lot<00:40:15.260> of<00:40:15.320> work<00:40:15.530> in<00:40:15.770> Russ 00:40:16.000 --> 00:40:16.010 align:start position:0% then he also did a lot of work in Russ 00:40:16.010 --> 00:40:18.340 align:start position:0% then he also did a lot of work in Russ on<00:40:16.310> on<00:40:17.210> the<00:40:17.330> awesome<00:40:17.690> team<00:40:17.870> and<00:40:18.050> he's<00:40:18.140> also 00:40:18.340 --> 00:40:18.350 align:start position:0% on on the awesome team and he's also 00:40:18.350 --> 00:40:20.740 align:start position:0% on on the awesome team and he's also working<00:40:18.560> on<00:40:18.860> POA<00:40:19.730> stuff<00:40:20.150> before<00:40:20.540> authorities 00:40:20.740 --> 00:40:20.750 align:start position:0% working on POA stuff before authorities 00:40:20.750 --> 00:40:23.110 align:start position:0% working on POA stuff before authorities stuff<00:40:21.380> in<00:40:21.530> rust<00:40:21.770> but<00:40:22.610> in<00:40:22.700> last<00:40:22.850> couple<00:40:22.970> of 00:40:23.110 --> 00:40:23.120 align:start position:0% stuff in rust but in last couple of 00:40:23.120 --> 00:40:24.970 align:start position:0% stuff in rust but in last couple of months<00:40:23.330> he<00:40:23.390> has<00:40:23.570> focused<00:40:23.750> a<00:40:24.020> lot<00:40:24.200> on<00:40:24.470> the<00:40:24.530> dev 00:40:24.970 --> 00:40:24.980 align:start position:0% months he has focused a lot on the dev 00:40:24.980 --> 00:40:29.560 align:start position:0% months he has focused a lot on the dev ops<00:40:25.220> side<00:40:26.030> on<00:40:26.300> iwo<00:40:27.050> Sam<00:40:27.260> so<00:40:28.220> it's<00:40:28.940> really<00:40:29.300> due 00:40:29.560 --> 00:40:29.570 align:start position:0% ops side on iwo Sam so it's really due 00:40:29.570 --> 00:40:32.320 align:start position:0% ops side on iwo Sam so it's really due to<00:40:29.600> Jared<00:40:30.200> and<00:40:30.380> KC<00:40:30.680> that<00:40:31.100> if<00:40:31.640> dev<00:40:31.880> ops<00:40:32.060> team 00:40:32.320 --> 00:40:32.330 align:start position:0% to Jared and KC that if dev ops team 00:40:32.330 --> 00:40:34.350 align:start position:0% to Jared and KC that if dev ops team that<00:40:32.720> he<00:40:33.020> wasn't<00:40:33.200> that<00:40:33.470> we<00:40:33.620> have<00:40:33.710> a<00:40:33.740> test<00:40:33.950> net 00:40:34.350 --> 00:40:34.360 align:start position:0% that he wasn't that we have a test net 00:40:34.360 --> 00:40:36.370 align:start position:0% that he wasn't that we have a test net just<00:40:35.360> one<00:40:35.510> last<00:40:35.720> note<00:40:35.840> about<00:40:35.990> the<00:40:36.080> tested 00:40:36.370 --> 00:40:36.380 align:start position:0% just one last note about the tested 00:40:36.380 --> 00:40:38.800 align:start position:0% just one last note about the tested itself<00:40:36.680> it<00:40:37.550> is<00:40:37.610> actually<00:40:38.090> working<00:40:38.270> it<00:40:38.600> has 00:40:38.800 --> 00:40:38.810 align:start position:0% itself it is actually working it has 00:40:38.810 --> 00:40:41.200 align:start position:0% itself it is actually working it has been<00:40:39.020> working<00:40:39.520> for<00:40:40.520> the<00:40:40.610> last<00:40:40.640> couple<00:40:41.090> of 00:40:41.200 --> 00:40:41.210 align:start position:0% been working for the last couple of 00:40:41.210 --> 00:40:44.320 align:start position:0% been working for the last couple of months<00:40:42.310> but<00:40:43.310> it's<00:40:43.490> the<00:40:43.580> first<00:40:43.760> time<00:40:43.910> we<00:40:44.090> share 00:40:44.320 --> 00:40:44.330 align:start position:0% months but it's the first time we share 00:40:44.330 --> 00:40:46.330 align:start position:0% months but it's the first time we share it<00:40:44.420> with<00:40:44.540> you<00:40:44.690> guys<00:40:44.720> but<00:40:45.710> keep<00:40:45.860> in<00:40:45.980> mind<00:40:46.010> if 00:40:46.330 --> 00:40:46.340 align:start position:0% it with you guys but keep in mind if 00:40:46.340 --> 00:40:47.680 align:start position:0% it with you guys but keep in mind if you're<00:40:46.490> still<00:40:46.700> making<00:40:46.850> changes<00:40:47.330> to<00:40:47.390> it<00:40:47.510> we're 00:40:47.680 --> 00:40:47.690 align:start position:0% you're still making changes to it we're 00:40:47.690 --> 00:40:49.720 align:start position:0% you're still making changes to it we're making<00:40:47.840> updates<00:40:48.140> to<00:40:48.500> it<00:40:48.590> it<00:40:49.190> is<00:40:49.340> a<00:40:49.370> proof<00:40:49.640> of 00:40:49.720 --> 00:40:49.730 align:start position:0% making updates to it it is a proof of 00:40:49.730 --> 00:40:52.270 align:start position:0% making updates to it it is a proof of our<00:40:49.880> test<00:40:50.180> net<00:40:50.390> so<00:40:51.230> we<00:40:51.320> gonna<00:40:51.440> just<00:40:51.710> rebuilt<00:40:52.100> it 00:40:52.270 --> 00:40:52.280 align:start position:0% our test net so we gonna just rebuilt it 00:40:52.280 --> 00:40:54.100 align:start position:0% our test net so we gonna just rebuilt it with<00:40:52.520> the<00:40:52.640> new<00:40:52.760> updates<00:40:53.120> every<00:40:53.660> now<00:40:53.810> and<00:40:53.960> then 00:40:54.100 --> 00:40:54.110 align:start position:0% with the new updates every now and then 00:40:54.110 --> 00:40:56.470 align:start position:0% with the new updates every now and then but<00:40:55.010> it's<00:40:55.160> still<00:40:55.310> it's<00:40:55.520> already<00:40:55.850> ready<00:40:56.000> to<00:40:56.360> be 00:40:56.470 --> 00:40:56.480 align:start position:0% but it's still it's already ready to be 00:40:56.480 --> 00:40:59.170 align:start position:0% but it's still it's already ready to be used<00:40:56.600> so<00:40:57.500> big<00:40:57.650> applause<00:40:57.980> for<00:40:58.280> Jared<00:40:58.730> again<00:40:58.910> and 00:40:59.170 --> 00:40:59.180 align:start position:0% used so big applause for Jared again and 00:40:59.180 --> 00:41:00.880 align:start position:0% used so big applause for Jared again and you<00:40:59.570> can<00:40:59.690> explain<00:41:00.050> everything<00:41:00.350> to<00:41:00.590> you<00:41:00.680> guys 00:41:00.880 --> 00:41:00.890 align:start position:0% you can explain everything to you guys 00:41:00.890 --> 00:41:04.920 align:start position:0% you can explain everything to you guys [Applause] 00:41:04.920 --> 00:41:04.930 align:start position:0% [Applause] 00:41:04.930 --> 00:41:07.270 align:start position:0% [Applause] up<00:41:05.930> is<00:41:06.559> this<00:41:06.829> working 00:41:07.270 --> 00:41:07.280 align:start position:0% up is this working 00:41:07.280 --> 00:41:09.430 align:start position:0% up is this working yeah<00:41:07.460> it<00:41:07.579> is<00:41:08.329> thanks<00:41:08.900> for<00:41:09.049> the<00:41:09.109> introduction 00:41:09.430 --> 00:41:09.440 align:start position:0% yeah it is thanks for the introduction 00:41:09.440 --> 00:41:11.260 align:start position:0% yeah it is thanks for the introduction Alex<00:41:09.859> hi<00:41:10.099> everybody 00:41:11.260 --> 00:41:11.270 align:start position:0% Alex hi everybody 00:41:11.270 --> 00:41:14.319 align:start position:0% Alex hi everybody I<00:41:11.299> prepared<00:41:12.260> a<00:41:12.319> short<00:41:12.470> video<00:41:12.740> because<00:41:13.190> well<00:41:14.119> we 00:41:14.319 --> 00:41:14.329 align:start position:0% I prepared a short video because well we 00:41:14.329 --> 00:41:17.910 align:start position:0% I prepared a short video because well we know<00:41:14.450> how<00:41:14.690> live<00:41:15.140> demos<00:41:15.530> go 00:41:17.910 --> 00:41:17.920 align:start position:0% 00:41:17.920 --> 00:41:20.859 align:start position:0% so<00:41:18.920> let's<00:41:19.130> it<00:41:19.970> doesn't<00:41:20.240> have<00:41:20.329> sound<00:41:20.599> so<00:41:20.780> I'll 00:41:20.859 --> 00:41:20.869 align:start position:0% so let's it doesn't have sound so I'll 00:41:20.869 --> 00:41:29.200 align:start position:0% so let's it doesn't have sound so I'll just<00:41:21.020> kind<00:41:21.200> of<00:41:25.990> yeah<00:41:26.990> so<00:41:27.940> what<00:41:28.940> we're<00:41:29.059> seeing 00:41:29.200 --> 00:41:29.210 align:start position:0% just kind of yeah so what we're seeing 00:41:29.210 --> 00:41:33.430 align:start position:0% just kind of yeah so what we're seeing here<00:41:29.329> is<00:41:29.780> just<00:41:31.510> the<00:41:32.510> basic<00:41:32.869> components<00:41:33.319> of<00:41:33.349> a 00:41:33.430 --> 00:41:33.440 align:start position:0% here is just the basic components of a 00:41:33.440 --> 00:41:36.339 align:start position:0% here is just the basic components of a test<00:41:33.680> net<00:41:33.920> I've<00:41:34.160> created<00:41:34.670> an<00:41:34.880> empty<00:41:35.180> account<00:41:35.599> I 00:41:36.339 --> 00:41:36.349 align:start position:0% test net I've created an empty account I 00:41:36.349 --> 00:41:41.670 align:start position:0% test net I've created an empty account I am<00:41:37.250> connecting<00:41:38.119> to<00:41:38.359> the<00:41:38.510> RPC<00:41:38.809> endpoint<00:41:39.440> and 00:41:41.670 --> 00:41:41.680 align:start position:0% am connecting to the RPC endpoint and 00:41:41.680 --> 00:41:48.700 align:start position:0% am connecting to the RPC endpoint and getting<00:41:42.680> some<00:41:42.859> ether<00:41:46.900> and<00:41:47.900> now<00:41:48.109> we<00:41:48.170> wait<00:41:48.650> a 00:41:48.700 --> 00:41:48.710 align:start position:0% getting some ether and now we wait a 00:41:48.710 --> 00:41:56.380 align:start position:0% getting some ether and now we wait a little<00:41:48.920> bit<00:41:53.859> okay<00:41:54.859> so<00:41:54.920> the<00:41:55.190> next<00:41:55.309> step<00:41:55.640> I'm 00:41:56.380 --> 00:41:56.390 align:start position:0% little bit okay so the next step I'm 00:41:56.390 --> 00:41:59.230 align:start position:0% little bit okay so the next step I'm gonna<00:41:56.569> deploy<00:41:56.900> a<00:41:56.930> contract<00:41:57.650> I<00:41:57.950> have<00:41:58.099> here<00:41:58.760> and 00:41:59.230 --> 00:41:59.240 align:start position:0% gonna deploy a contract I have here and 00:41:59.240 --> 00:42:00.520 align:start position:0% gonna deploy a contract I have here and this<00:41:59.299> is<00:41:59.450> actually<00:41:59.720> a<00:41:59.780> contract<00:42:00.260> from<00:42:00.440> our 00:42:00.520 --> 00:42:00.530 align:start position:0% this is actually a contract from our 00:42:00.530 --> 00:42:02.740 align:start position:0% this is actually a contract from our test<00:42:00.770> suite<00:42:00.950> and<00:42:01.359> basically<00:42:02.359> all<00:42:02.569> this<00:42:02.690> does 00:42:02.740 --> 00:42:02.750 align:start position:0% test suite and basically all this does 00:42:02.750 --> 00:42:05.440 align:start position:0% test suite and basically all this does is<00:42:03.140> it<00:42:03.260> just<00:42:03.290> it's<00:42:03.829> some<00:42:04.040> deployment<00:42:04.549> code<00:42:04.700> to 00:42:05.440 --> 00:42:05.450 align:start position:0% is it just it's some deployment code to 00:42:05.450 --> 00:42:09.940 align:start position:0% is it just it's some deployment code to put<00:42:05.839> up<00:42:05.960> a<00:42:06.280> simple<00:42:07.280> web<00:42:07.520> sembly<00:42:07.880> contract<00:42:08.950> and 00:42:09.940 --> 00:42:09.950 align:start position:0% put up a simple web sembly contract and 00:42:09.950 --> 00:42:11.620 align:start position:0% put up a simple web sembly contract and this<00:42:10.280> is<00:42:10.430> a<00:42:10.460> simple<00:42:10.760> tool<00:42:11.000> we've<00:42:11.150> developed 00:42:11.620 --> 00:42:11.630 align:start position:0% this is a simple tool we've developed 00:42:11.630 --> 00:42:13.920 align:start position:0% this is a simple tool we've developed that<00:42:12.319> should<00:42:12.470> make<00:42:12.710> deploying<00:42:13.309> contracts 00:42:13.920 --> 00:42:13.930 align:start position:0% that should make deploying contracts 00:42:13.930 --> 00:42:19.420 align:start position:0% that should make deploying contracts fairly<00:42:14.930> easy<00:42:15.109> so<00:42:17.410> yeah<00:42:18.410> one<00:42:19.099> of<00:42:19.130> the<00:42:19.250> things 00:42:19.420 --> 00:42:19.430 align:start position:0% fairly easy so yeah one of the things 00:42:19.430 --> 00:42:22.480 align:start position:0% fairly easy so yeah one of the things that<00:42:19.869> you<00:42:20.869> should<00:42:20.900> note<00:42:21.319> about<00:42:21.650> this<00:42:21.950> is<00:42:22.010> that 00:42:22.480 --> 00:42:22.490 align:start position:0% that you should note about this is that 00:42:22.490 --> 00:42:26.710 align:start position:0% that you should note about this is that you'll<00:42:22.760> see<00:42:23.000> that<00:42:23.510> at<00:42:24.470> no<00:42:24.710> point<00:42:25.720> before 00:42:26.710 --> 00:42:26.720 align:start position:0% you'll see that at no point before 00:42:26.720 --> 00:42:30.970 align:start position:0% you'll see that at no point before deploying<00:42:27.640> there<00:42:29.410> well<00:42:30.410> actually<00:42:30.650> I'll<00:42:30.950> just 00:42:30.970 --> 00:42:30.980 align:start position:0% deploying there well actually I'll just 00:42:30.980 --> 00:43:04.000 align:start position:0% deploying there well actually I'll just let<00:42:31.309> it<00:42:31.400> be<00:42:31.490> deployed<00:42:31.760> in<00:42:31.940> I<00:42:32.030> explained 00:43:04.000 --> 00:43:04.010 align:start position:0% 00:43:04.010 --> 00:43:07.480 align:start position:0% cool<00:43:04.610> okay<00:43:05.380> yeah<00:43:06.380> and<00:43:06.650> unfortunately<00:43:06.770> this 00:43:07.480 --> 00:43:07.490 align:start position:0% cool okay yeah and unfortunately this 00:43:07.490 --> 00:43:09.940 align:start position:0% cool okay yeah and unfortunately this highlights<00:43:07.910> a<00:43:08.030> little<00:43:08.200> bug<00:43:09.200> that<00:43:09.230> recently 00:43:09.940 --> 00:43:09.950 align:start position:0% highlights a little bug that recently 00:43:09.950 --> 00:43:12.610 align:start position:0% highlights a little bug that recently appeared<00:43:10.220> in<00:43:10.370> our<00:43:10.550> Explorer<00:43:11.410> don't<00:43:12.410> worry 00:43:12.610 --> 00:43:12.620 align:start position:0% appeared in our Explorer don't worry 00:43:12.620 --> 00:43:15.280 align:start position:0% appeared in our Explorer don't worry we're<00:43:12.770> gonna<00:43:12.830> hotfix<00:43:13.340> it<00:43:13.610> but<00:43:14.300> you're<00:43:15.200> gonna 00:43:15.280 --> 00:43:15.290 align:start position:0% we're gonna hotfix it but you're gonna 00:43:15.290 --> 00:43:17.680 align:start position:0% we're gonna hotfix it but you're gonna watch<00:43:15.470> me<00:43:15.790> scroll<00:43:16.790> through<00:43:17.030> the<00:43:17.210> list<00:43:17.240> of<00:43:17.540> all 00:43:17.680 --> 00:43:17.690 align:start position:0% watch me scroll through the list of all 00:43:17.690 --> 00:43:19.950 align:start position:0% watch me scroll through the list of all accounts<00:43:18.170> to<00:43:18.380> find<00:43:18.650> my<00:43:18.800> deployed<00:43:19.280> contract 00:43:19.950 --> 00:43:19.960 align:start position:0% accounts to find my deployed contract 00:43:19.960 --> 00:43:23.050 align:start position:0% accounts to find my deployed contract and<00:43:20.960> I<00:43:21.890> guess<00:43:22.130> one<00:43:22.340> of<00:43:22.370> the<00:43:22.490> things<00:43:22.640> that<00:43:22.850> I 00:43:23.050 --> 00:43:23.060 align:start position:0% and I guess one of the things that I 00:43:23.060 --> 00:43:27.030 align:start position:0% and I guess one of the things that I want<00:43:23.210> to<00:43:23.270> highlight<00:43:23.420> here<00:43:23.800> did<00:43:24.800> once<00:43:25.310> I<00:43:25.880> once<00:43:26.810> I 00:43:27.030 --> 00:43:27.040 align:start position:0% want to highlight here did once I once I 00:43:27.040 --> 00:43:32.500 align:start position:0% want to highlight here did once I once I scroll<00:43:28.040> through<00:43:28.070> all<00:43:28.370> the<00:43:28.490> pages<00:43:28.700> but<00:43:29.150> so<00:43:31.510> I'm 00:43:32.500 --> 00:43:32.510 align:start position:0% scroll through all the pages but so I'm 00:43:32.510 --> 00:43:34.840 align:start position:0% scroll through all the pages but so I'm if<00:43:32.840> you<00:43:33.020> if<00:43:33.400> when<00:43:34.400> you<00:43:34.520> saw<00:43:34.670> earlier 00:43:34.840 --> 00:43:34.850 align:start position:0% if you if when you saw earlier 00:43:34.850 --> 00:43:36.340 align:start position:0% if you if when you saw earlier presentations<00:43:35.720> you<00:43:35.960> may<00:43:36.080> have<00:43:36.170> heard<00:43:36.290> about 00:43:36.340 --> 00:43:36.350 align:start position:0% presentations you may have heard about 00:43:36.350 --> 00:43:40.330 align:start position:0% presentations you may have heard about metering<00:43:36.950> and<00:43:38.470> so<00:43:39.470> if<00:43:39.740> you<00:43:39.830> saw<00:43:39.980> the<00:43:40.040> contract 00:43:40.330 --> 00:43:40.340 align:start position:0% metering and so if you saw the contract 00:43:40.340 --> 00:43:43.990 align:start position:0% metering and so if you saw the contract code<00:43:40.700> I<00:43:40.760> had<00:43:41.000> to<00:43:41.200> deployed<00:43:42.200> before<00:43:43.000> you'll 00:43:43.990 --> 00:43:44.000 align:start position:0% code I had to deployed before you'll 00:43:44.000 --> 00:43:46.450 align:start position:0% code I had to deployed before you'll notice<00:43:44.150> that<00:43:44.390> there<00:43:44.540> were<00:43:44.660> no<00:43:45.190> metering<00:43:46.190> or 00:43:46.450 --> 00:43:46.460 align:start position:0% notice that there were no metering or 00:43:46.460 --> 00:43:49.750 align:start position:0% notice that there were no metering or use<00:43:47.000> gas<00:43:47.270> calls<00:43:47.950> and<00:43:48.950> what's<00:43:49.160> gonna<00:43:49.280> happen<00:43:49.340> is 00:43:49.750 --> 00:43:49.760 align:start position:0% use gas calls and what's gonna happen is 00:43:49.760 --> 00:43:51.400 align:start position:0% use gas calls and what's gonna happen is that<00:43:49.820> when<00:43:50.210> I've<00:43:50.330> deployed<00:43:50.660> this<00:43:50.840> contract 00:43:51.400 --> 00:43:51.410 align:start position:0% that when I've deployed this contract 00:43:51.410 --> 00:43:54.730 align:start position:0% that when I've deployed this contract actually<00:43:52.070> what's<00:43:53.030> going<00:43:53.180> on<00:43:53.420> is<00:43:53.630> we<00:43:54.620> have 00:43:54.730 --> 00:43:54.740 align:start position:0% actually what's going on is we have 00:43:54.740 --> 00:43:56.470 align:start position:0% actually what's going on is we have another<00:43:54.950> contract<00:43:55.490> called<00:43:55.910> The<00:43:56.180> Sentinel 00:43:56.470 --> 00:43:56.480 align:start position:0% another contract called The Sentinel 00:43:56.480 --> 00:43:58.120 align:start position:0% another contract called The Sentinel contract<00:43:57.200> which<00:43:57.380> is<00:43:57.500> going<00:43:57.650> to<00:43:57.740> take<00:43:57.950> my 00:43:58.120 --> 00:43:58.130 align:start position:0% contract which is going to take my 00:43:58.130 --> 00:44:01.180 align:start position:0% contract which is going to take my deployed<00:43:58.460> contract<00:43:59.060> parse<00:43:59.630> it<00:43:59.840> out<00:43:59.930> and<00:44:00.200> apply 00:44:01.180 --> 00:44:01.190 align:start position:0% deployed contract parse it out and apply 00:44:01.190 --> 00:44:06.220 align:start position:0% deployed contract parse it out and apply metering<00:44:02.120> injection<00:44:02.600> to<00:44:02.750> it<00:44:02.900> so<00:44:05.200> after<00:44:06.200> I 00:44:06.220 --> 00:44:06.230 align:start position:0% metering injection to it so after I 00:44:06.230 --> 00:44:09.100 align:start position:0% metering injection to it so after I finished<00:44:06.700> scrolling<00:44:07.700> through<00:44:07.930> some<00:44:08.930> pages 00:44:09.100 --> 00:44:09.110 align:start position:0% finished scrolling through some pages 00:44:09.110 --> 00:44:12.850 align:start position:0% finished scrolling through some pages here<00:44:10.780> don't<00:44:11.780> worry<00:44:11.930> this<00:44:12.080> will<00:44:12.260> be<00:44:12.350> hot<00:44:12.500> fixed 00:44:12.850 --> 00:44:12.860 align:start position:0% here don't worry this will be hot fixed 00:44:12.860 --> 00:44:30.580 align:start position:0% here don't worry this will be hot fixed it 00:44:30.580 --> 00:44:30.590 align:start position:0% 00:44:30.590 --> 00:44:42.620 align:start position:0% should<00:44:31.590> be<00:44:31.710> one<00:44:33.470> yeah<00:44:34.470> there<00:44:34.800> it<00:44:34.920> is<00:44:34.980> okay<00:44:41.630> cool 00:44:42.620 --> 00:44:42.630 align:start position:0% should be one yeah there it is okay cool 00:44:42.630 --> 00:44:45.680 align:start position:0% should be one yeah there it is okay cool yeah<00:44:42.810> so<00:44:43.080> yeah<00:44:43.890> this<00:44:44.040> is<00:44:44.100> a<00:44:44.460> little<00:44:44.970> this<00:44:45.630> is 00:44:45.680 --> 00:44:45.690 align:start position:0% yeah so yeah this is a little this is 00:44:45.690 --> 00:44:47.680 align:start position:0% yeah so yeah this is a little this is the<00:44:45.930> block<00:44:46.260> Explorer<00:44:46.740> that<00:44:46.950> we've<00:44:47.070> modified 00:44:47.680 --> 00:44:47.690 align:start position:0% the block Explorer that we've modified 00:44:47.690 --> 00:44:52.190 align:start position:0% the block Explorer that we've modified now<00:44:48.690> you<00:44:49.440> can<00:44:50.130> see<00:44:50.370> the<00:44:51.120> code<00:44:51.300> now<00:44:51.630> has<00:44:51.930> this 00:44:52.190 --> 00:44:52.200 align:start position:0% now you can see the code now has this 00:44:52.200 --> 00:44:55.220 align:start position:0% now you can see the code now has this used<00:44:52.530> gas<00:44:52.770> import<00:44:53.400> and<00:44:53.580> the<00:44:53.820> entire<00:44:54.230> branch 00:44:55.220 --> 00:44:55.230 align:start position:0% used gas import and the entire branch 00:44:55.230 --> 00:45:04.730 align:start position:0% used gas import and the entire branch has<00:44:55.830> been<00:44:56.570> metered<00:44:57.570> by<00:45:02.180> so<00:45:03.380> you'll<00:45:04.380> see<00:45:04.590> the 00:45:04.730 --> 00:45:04.740 align:start position:0% has been metered by so you'll see the 00:45:04.740 --> 00:45:07.070 align:start position:0% has been metered by so you'll see the the<00:45:04.980> use<00:45:05.190> gas<00:45:05.430> statement<00:45:06.000> is<00:45:06.210> was<00:45:06.630> applied<00:45:06.900> by 00:45:07.070 --> 00:45:07.080 align:start position:0% the use gas statement is was applied by 00:45:07.080 --> 00:45:08.540 align:start position:0% the use gas statement is was applied by the<00:45:07.140> metering<00:45:07.410> contract<00:45:07.980> it's<00:45:08.130> applied<00:45:08.400> to 00:45:08.540 --> 00:45:08.550 align:start position:0% the metering contract it's applied to 00:45:08.550 --> 00:45:13.760 align:start position:0% the metering contract it's applied to the<00:45:08.640> entire<00:45:08.760> branch<00:45:09.770> and<00:45:11.180> I<00:45:12.180> believe<00:45:12.770> metering 00:45:13.760 --> 00:45:13.770 align:start position:0% the entire branch and I believe metering 00:45:13.770 --> 00:45:17.290 align:start position:0% the entire branch and I believe metering as<00:45:13.890> it<00:45:14.010> currently<00:45:14.280> works<00:45:14.820> is<00:45:15.090> applied<00:45:16.080> by 00:45:17.290 --> 00:45:17.300 align:start position:0% as it currently works is applied by 00:45:17.300 --> 00:45:21.950 align:start position:0% as it currently works is applied by branch<00:45:18.300> so<00:45:18.810> I<00:45:20.420> can't<00:45:21.420> tell<00:45:21.570> you<00:45:21.660> much<00:45:21.750> more 00:45:21.950 --> 00:45:21.960 align:start position:0% branch so I can't tell you much more 00:45:21.960 --> 00:45:24.320 align:start position:0% branch so I can't tell you much more than<00:45:22.020> that<00:45:22.230> because<00:45:22.470> my<00:45:23.040> job<00:45:23.280> mostly<00:45:23.730> involves 00:45:24.320 --> 00:45:24.330 align:start position:0% than that because my job mostly involves 00:45:24.330 --> 00:45:26.390 align:start position:0% than that because my job mostly involves breaking<00:45:25.140> things<00:45:25.530> on<00:45:25.710> the<00:45:25.800> test<00:45:26.010> net<00:45:26.190> and<00:45:26.310> then 00:45:26.390 --> 00:45:26.400 align:start position:0% breaking things on the test net and then 00:45:26.400 --> 00:45:28.280 align:start position:0% breaking things on the test net and then fixing<00:45:26.730> them<00:45:26.910> I<00:45:27.210> didn't<00:45:27.780> actually<00:45:27.900> write<00:45:28.170> the 00:45:28.280 --> 00:45:28.290 align:start position:0% fixing them I didn't actually write the 00:45:28.290 --> 00:45:37.670 align:start position:0% fixing them I didn't actually write the metering<00:45:28.530> contract<00:45:29.040> so<00:45:33.890> yeah<00:45:35.660> so<00:45:36.660> yeah<00:45:37.470> that's 00:45:37.670 --> 00:45:37.680 align:start position:0% metering contract so yeah so yeah that's 00:45:37.680 --> 00:45:40.150 align:start position:0% metering contract so yeah so yeah that's kind<00:45:38.010> of<00:45:38.070> that's<00:45:38.430> gonna<00:45:38.550> it<00:45:38.790> for<00:45:39.210> the<00:45:39.300> demo 00:45:40.150 --> 00:45:40.160 align:start position:0% kind of that's gonna it for the demo 00:45:40.160 --> 00:45:42.920 align:start position:0% kind of that's gonna it for the demo please<00:45:41.160> feel<00:45:41.400> free<00:45:41.430> to<00:45:41.700> go<00:45:42.180> up<00:45:42.360> I<00:45:42.480> mean<00:45:42.510> it's<00:45:42.780> up 00:45:42.920 --> 00:45:42.930 align:start position:0% please feel free to go up I mean it's up 00:45:42.930 --> 00:45:46.430 align:start position:0% please feel free to go up I mean it's up now<00:45:43.170> so<00:45:43.980> go<00:45:44.190> and<00:45:44.660> try<00:45:45.660> and<00:45:45.690> break<00:45:45.900> our<00:45:46.110> break 00:45:46.430 --> 00:45:46.440 align:start position:0% now so go and try and break our break 00:45:46.440 --> 00:45:51.220 align:start position:0% now so go and try and break our break our<00:45:46.650> stuff<00:45:48.230> we<00:45:49.230> are<00:45:49.560> gonna<00:45:49.980> be<00:45:50.160> releasing 00:45:51.220 --> 00:45:51.230 align:start position:0% our stuff we are gonna be releasing 00:45:51.230 --> 00:45:54.380 align:start position:0% our stuff we are gonna be releasing later<00:45:52.230> today<00:45:52.560> some<00:45:53.490> instructions<00:45:54.180> if<00:45:54.300> you 00:45:54.380 --> 00:45:54.390 align:start position:0% later today some instructions if you 00:45:54.390 --> 00:45:55.700 align:start position:0% later today some instructions if you want<00:45:54.540> to<00:45:54.600> connect<00:45:54.840> your<00:45:54.960> own<00:45:54.990> node<00:45:55.380> to<00:45:55.620> the 00:45:55.700 --> 00:45:55.710 align:start position:0% want to connect your own node to the 00:45:55.710 --> 00:45:57.590 align:start position:0% want to connect your own node to the test<00:45:55.920> Nets<00:45:56.160> you<00:45:56.370> don't<00:45:56.520> necessarily<00:45:57.030> have<00:45:57.450> to 00:45:57.590 --> 00:45:57.600 align:start position:0% test Nets you don't necessarily have to 00:45:57.600 --> 00:46:02.780 align:start position:0% test Nets you don't necessarily have to use<00:45:57.810> our<00:45:57.960> tooling<00:46:00.200> so<00:46:01.200> yeah<00:46:01.380> that's<00:46:01.920> that's 00:46:02.780 --> 00:46:02.790 align:start position:0% use our tooling so yeah that's that's 00:46:02.790 --> 00:46:05.250 align:start position:0% use our tooling so yeah that's that's the<00:46:03.030> demo 00:46:05.250 --> 00:46:05.260 align:start position:0% 00:46:05.260 --> 00:46:09.859 align:start position:0% [Applause] 00:46:09.859 --> 00:46:09.869 align:start position:0% 00:46:09.869 --> 00:46:12.390 align:start position:0% Thank<00:46:10.869> You<00:46:10.900> Jared<00:46:11.230> for<00:46:11.349> the<00:46:11.410> demo<00:46:11.619> yeah<00:46:12.220> we're 00:46:12.390 --> 00:46:12.400 align:start position:0% Thank You Jared for the demo yeah we're 00:46:12.400 --> 00:46:13.769 align:start position:0% Thank You Jared for the demo yeah we're really<00:46:12.519> excited<00:46:12.609> to<00:46:13.000> share<00:46:13.329> the<00:46:13.480> test<00:46:13.660> night 00:46:13.769 --> 00:46:13.779 align:start position:0% really excited to share the test night 00:46:13.779 --> 00:46:16.499 align:start position:0% really excited to share the test night it's<00:46:13.930> live<00:46:14.109> as<00:46:14.289> he<00:46:14.410> said<00:46:14.619> the<00:46:15.250> RPC<00:46:15.759> URL<00:46:16.180> I<00:46:16.269> think 00:46:16.499 --> 00:46:16.509 align:start position:0% it's live as he said the RPC URL I think 00:46:16.509 --> 00:46:19.170 align:start position:0% it's live as he said the RPC URL I think is<00:46:16.599> just<00:46:16.839> ye<00:46:17.019> Hwa's<00:46:17.200> m-theory<00:46:17.710> org<00:46:18.160> port<00:46:18.640> 8<00:46:18.789> 5<00:46:18.970> 4 00:46:19.170 --> 00:46:19.180 align:start position:0% is just ye Hwa's m-theory org port 8 5 4 00:46:19.180 --> 00:46:20.579 align:start position:0% is just ye Hwa's m-theory org port 8 5 4 5<00:46:19.390> so<00:46:19.690> you<00:46:19.750> can<00:46:19.960> actually<00:46:20.079> plug<00:46:20.319> that<00:46:20.440> into 00:46:20.579 --> 00:46:20.589 align:start position:0% 5 so you can actually plug that into 00:46:20.589 --> 00:46:22.049 align:start position:0% 5 so you can actually plug that into meta<00:46:20.769> mask<00:46:20.980> you<00:46:21.369> can<00:46:21.519> plug<00:46:21.730> that<00:46:21.849> in<00:46:21.940> your 00:46:22.049 --> 00:46:22.059 align:start position:0% meta mask you can plug that in your 00:46:22.059 --> 00:46:23.370 align:start position:0% meta mask you can plug that in your browser<00:46:22.240> you<00:46:22.420> can<00:46:22.720> get<00:46:22.839> testing<00:46:23.170> it<00:46:23.259> either 00:46:23.370 --> 00:46:23.380 align:start position:0% browser you can get testing it either 00:46:23.380 --> 00:46:26.819 align:start position:0% browser you can get testing it either already<00:46:24.509> there<00:46:25.509> are<00:46:25.660> instructions<00:46:26.200> up<00:46:26.380> in<00:46:26.559> the 00:46:26.819 --> 00:46:26.829 align:start position:0% already there are instructions up in the 00:46:26.829 --> 00:46:29.400 align:start position:0% already there are instructions up in the USM<00:46:27.730> slash<00:46:27.940> test<00:46:28.210> at<00:46:28.359> repository<00:46:28.930> about 00:46:29.400 --> 00:46:29.410 align:start position:0% USM slash test at repository about 00:46:29.410 --> 00:46:30.960 align:start position:0% USM slash test at repository about connecting<00:46:29.859> your<00:46:29.950> own<00:46:30.099> node<00:46:30.309> but<00:46:30.519> I<00:46:30.549> think<00:46:30.819> it 00:46:30.960 --> 00:46:30.970 align:start position:0% connecting your own node but I think it 00:46:30.970 --> 00:46:33.509 align:start position:0% connecting your own node but I think it doesn't<00:46:31.210> include<00:46:31.690> the<00:46:31.990> latest<00:46:32.200> like<00:46:33.069> Genesis 00:46:33.509 --> 00:46:33.519 align:start position:0% doesn't include the latest like Genesis 00:46:33.519 --> 00:46:35.400 align:start position:0% doesn't include the latest like Genesis file<00:46:33.789> so<00:46:34.089> you<00:46:34.119> probably<00:46:34.450> if<00:46:34.809> you<00:46:34.990> were<00:46:35.140> to<00:46:35.259> try 00:46:35.400 --> 00:46:35.410 align:start position:0% file so you probably if you were to try 00:46:35.410 --> 00:46:36.930 align:start position:0% file so you probably if you were to try to<00:46:35.470> do<00:46:35.559> that<00:46:35.680> right<00:46:36.009> now<00:46:36.039> you<00:46:36.220> get<00:46:36.519> an<00:46:36.609> error 00:46:36.930 --> 00:46:36.940 align:start position:0% to do that right now you get an error 00:46:36.940 --> 00:46:38.670 align:start position:0% to do that right now you get an error sorry<00:46:37.660> I've<00:46:37.809> even<00:46:38.079> other<00:46:38.230> people<00:46:38.440> in<00:46:38.500> the<00:46:38.559> room 00:46:38.670 --> 00:46:38.680 align:start position:0% sorry I've even other people in the room 00:46:38.680 --> 00:46:39.930 align:start position:0% sorry I've even other people in the room who<00:46:38.859> have<00:46:38.950> already<00:46:39.130> tried<00:46:39.309> to<00:46:39.490> do<00:46:39.609> that 00:46:39.930 --> 00:46:39.940 align:start position:0% who have already tried to do that 00:46:39.940 --> 00:46:41.849 align:start position:0% who have already tried to do that well<00:46:40.269> we'll<00:46:40.450> update<00:46:40.599> that<00:46:40.720> later<00:46:40.960> today<00:46:41.109> so 00:46:41.849 --> 00:46:41.859 align:start position:0% well we'll update that later today so 00:46:41.859 --> 00:46:44.759 align:start position:0% well we'll update that later today so cool<00:46:42.220> we're<00:46:42.369> gonna<00:46:42.460> move<00:46:42.670> into<00:46:42.819> a<00:46:42.970> QA<00:46:43.470> for<00:46:44.470> 5<00:46:44.740> or 00:46:44.759 --> 00:46:44.769 align:start position:0% cool we're gonna move into a QA for 5 or 00:46:44.769 --> 00:46:46.140 align:start position:0% cool we're gonna move into a QA for 5 or 10<00:46:44.980> minutes<00:46:45.250> so<00:46:45.549> we<00:46:45.640> can<00:46:45.670> have<00:46:45.880> all<00:46:46.000> the 00:46:46.140 --> 00:46:46.150 align:start position:0% 10 minutes so we can have all the 00:46:46.150 --> 00:46:47.279 align:start position:0% 10 minutes so we can have all the teammates<00:46:46.599> come<00:46:46.839> up<00:46:46.930> and<00:46:47.019> we'll<00:46:47.140> answer 00:46:47.279 --> 00:46:47.289 align:start position:0% teammates come up and we'll answer 00:46:47.289 --> 00:46:49.559 align:start position:0% teammates come up and we'll answer questions<00:46:47.880> CX<00:46:48.880> are<00:46:49.000> you<00:46:49.089> good<00:46:49.210> to<00:46:49.299> go<00:46:49.390> with<00:46:49.480> the 00:46:49.559 --> 00:46:49.569 align:start position:0% questions CX are you good to go with the 00:46:49.569 --> 00:46:52.230 align:start position:0% questions CX are you good to go with the mic<00:46:49.720> excellent<00:46:50.559> and<00:46:51.400> then<00:46:51.549> after<00:46:52.029> that<00:46:52.119> we're 00:46:52.230 --> 00:46:52.240 align:start position:0% mic excellent and then after that we're 00:46:52.240 --> 00:46:53.609 align:start position:0% mic excellent and then after that we're gonna<00:46:52.299> do<00:46:52.480> a<00:46:52.509> short<00:46:53.079> break<00:46:53.200> and<00:46:53.380> then<00:46:53.440> come 00:46:53.609 --> 00:46:53.619 align:start position:0% gonna do a short break and then come 00:46:53.619 --> 00:46:54.870 align:start position:0% gonna do a short break and then come back<00:46:53.680> for<00:46:53.799> the<00:46:53.980> second<00:46:54.220> half<00:46:54.250> of<00:46:54.430> the<00:46:54.549> breakout 00:46:54.870 --> 00:46:54.880 align:start position:0% back for the second half of the breakout 00:46:54.880 --> 00:46:56.339 align:start position:0% back for the second half of the breakout so<00:46:55.000> if<00:46:55.059> you<00:46:55.119> have<00:46:55.210> a<00:46:55.240> question<00:46:55.599> raise<00:46:55.839> your 00:46:56.339 --> 00:46:56.349 align:start position:0% so if you have a question raise your 00:46:56.349 --> 00:47:03.210 align:start position:0% so if you have a question raise your hand<00:46:56.500> about<00:46:57.490> anything<00:46:57.730> you've<00:46:57.940> seen<00:46:57.970> I<00:47:02.130> have<00:47:03.130> a 00:47:03.210 --> 00:47:03.220 align:start position:0% hand about anything you've seen I have a 00:47:03.220 --> 00:47:05.160 align:start position:0% hand about anything you've seen I have a question<00:47:03.490> about<00:47:03.549> this<00:47:03.759> EVM<00:47:04.329> see<00:47:04.630> you 00:47:05.160 --> 00:47:05.170 align:start position:0% question about this EVM see you 00:47:05.170 --> 00:47:07.470 align:start position:0% question about this EVM see you mentioned<00:47:05.589> that<00:47:05.650> it's<00:47:05.829> running<00:47:06.039> on<00:47:06.250> one<00:47:06.640> main 00:47:07.470 --> 00:47:07.480 align:start position:0% mentioned that it's running on one main 00:47:07.480 --> 00:47:11.430 align:start position:0% mentioned that it's running on one main net<00:47:07.750> node<00:47:08.640> what<00:47:09.640> does<00:47:09.789> it<00:47:09.940> mean<00:47:10.150> for<00:47:10.750> me<00:47:11.200> as 00:47:11.430 --> 00:47:11.440 align:start position:0% net node what does it mean for me as 00:47:11.440 --> 00:47:14.910 align:start position:0% net node what does it mean for me as like<00:47:11.799> can<00:47:12.069> I<00:47:12.160> run<00:47:13.230> evil<00:47:14.230> resume<00:47:14.470> code<00:47:14.650> on<00:47:14.799> the 00:47:14.910 --> 00:47:14.920 align:start position:0% like can I run evil resume code on the 00:47:14.920 --> 00:47:16.710 align:start position:0% like can I run evil resume code on the may<00:47:15.039> net<00:47:15.250> if<00:47:15.400> you<00:47:15.730> pick<00:47:15.940> up<00:47:16.089> my<00:47:16.210> transaction<00:47:16.660> a 00:47:16.710 --> 00:47:16.720 align:start position:0% may net if you pick up my transaction a 00:47:16.720 --> 00:47:19.529 align:start position:0% may net if you pick up my transaction a minor<00:47:16.869> block<00:47:17.079> or<00:47:17.230> like<00:47:17.650> what<00:47:17.980> does<00:47:18.039> it<00:47:18.099> mean<00:47:18.539> so 00:47:19.529 --> 00:47:19.539 align:start position:0% minor block or like what does it mean so 00:47:19.539 --> 00:47:22.410 align:start position:0% minor block or like what does it mean so it's<00:47:19.720> just<00:47:20.079> basic<00:47:20.559> it's<00:47:20.920> you<00:47:21.069> note<00:47:21.339> if<00:47:22.000> you<00:47:22.210> go 00:47:22.410 --> 00:47:22.420 align:start position:0% it's just basic it's you note if you go 00:47:22.420 --> 00:47:26.249 align:start position:0% it's just basic it's you note if you go to<00:47:23.200> either<00:47:23.589> stop<00:47:24.220> it'll<00:47:24.730> starts<00:47:25.180> that<00:47:25.509> dotnet 00:47:26.249 --> 00:47:26.259 align:start position:0% to either stop it'll starts that dotnet 00:47:26.259 --> 00:47:29.130 align:start position:0% to either stop it'll starts that dotnet there's<00:47:27.099> one<00:47:27.369> node<00:47:27.609> called<00:47:28.089> a<00:47:28.630> live 00:47:29.130 --> 00:47:29.140 align:start position:0% there's one node called a live 00:47:29.140 --> 00:47:31.499 align:start position:0% there's one node called a live interpreter<00:47:29.579> so<00:47:30.579> it's<00:47:30.730> combination<00:47:31.029> with 00:47:31.499 --> 00:47:31.509 align:start position:0% interpreter so it's combination with 00:47:31.509 --> 00:47:34.019 align:start position:0% interpreter so it's combination with with<00:47:31.990> the<00:47:32.140> gate<00:47:32.410> client<00:47:33.009> and<00:47:33.250> a<00:47:33.759> live 00:47:34.019 --> 00:47:34.029 align:start position:0% with the gate client and a live 00:47:34.029 --> 00:47:37.170 align:start position:0% with the gate client and a live interpreter<00:47:34.359> as<00:47:34.900> a<00:47:34.960> VM<00:47:35.710> implementation<00:47:36.519> so 00:47:37.170 --> 00:47:37.180 align:start position:0% interpreter as a VM implementation so 00:47:37.180 --> 00:47:39.450 align:start position:0% interpreter as a VM implementation so that's<00:47:37.359> I<00:47:37.450> did<00:47:37.630> it<00:47:37.809> just<00:47:37.990> if<00:47:38.710> you<00:47:39.160> want<00:47:39.250> your 00:47:39.450 --> 00:47:39.460 align:start position:0% that's I did it just if you want your 00:47:39.460 --> 00:47:42.329 align:start position:0% that's I did it just if you want your run<00:47:40.390> your<00:47:40.569> own<00:47:40.599> node<00:47:40.990> you<00:47:41.529> can<00:47:41.559> just<00:47:41.920> use<00:47:42.130> this 00:47:42.329 --> 00:47:42.339 align:start position:0% run your own node you can just use this 00:47:42.339 --> 00:47:47.400 align:start position:0% run your own node you can just use this this<00:47:43.440> implementation<00:47:44.440> I<00:47:45.750> think<00:47:46.750> so<00:47:47.259> that 00:47:47.400 --> 00:47:47.410 align:start position:0% this implementation I think so that 00:47:47.410 --> 00:47:51.539 align:start position:0% this implementation I think so that talks<00:47:48.539> from<00:47:49.539> your<00:47:49.809> experience<00:47:50.529> like<00:47:50.890> you<00:47:51.430> have 00:47:51.539 --> 00:47:51.549 align:start position:0% talks from your experience like you have 00:47:51.549 --> 00:47:53.190 align:start position:0% talks from your experience like you have mentioned<00:47:51.759> several<00:47:52.089> languages<00:47:52.750> solidity 00:47:53.190 --> 00:47:53.200 align:start position:0% mentioned several languages solidity 00:47:53.200 --> 00:47:57.779 align:start position:0% mentioned several languages solidity vast<00:47:54.089> assembly<00:47:55.089> script<00:47:55.890> C++<00:47:56.890> which<00:47:57.279> one<00:47:57.609> is 00:47:57.779 --> 00:47:57.789 align:start position:0% vast assembly script C++ which one is 00:47:57.789 --> 00:48:00.690 align:start position:0% vast assembly script C++ which one is like<00:47:58.000> a<00:47:58.029> better<00:47:58.809> or<00:47:59.200> worse<00:47:59.259> in<00:48:00.039> case<00:48:00.309> of<00:48:00.490> like<00:48:00.670> a 00:48:00.690 --> 00:48:00.700 align:start position:0% like a better or worse in case of like a 00:48:00.700 --> 00:48:02.819 align:start position:0% like a better or worse in case of like a using<00:48:01.210> like<00:48:01.509> having<00:48:01.839> several<00:48:02.200> languages<00:48:02.650> is 00:48:02.819 --> 00:48:02.829 align:start position:0% using like having several languages is 00:48:02.829 --> 00:48:05.009 align:start position:0% using like having several languages is good<00:48:03.069> in<00:48:03.250> one<00:48:03.460> the<00:48:04.150> exit<00:48:04.450> direction<00:48:04.900> but<00:48:04.990> also 00:48:05.009 --> 00:48:05.019 align:start position:0% good in one the exit direction but also 00:48:05.019 --> 00:48:08.430 align:start position:0% good in one the exit direction but also there<00:48:05.589> might<00:48:05.799> be<00:48:05.829> some<00:48:06.250> problems<00:48:07.440> connecting 00:48:08.430 --> 00:48:08.440 align:start position:0% there might be some problems connecting 00:48:08.440 --> 00:48:10.319 align:start position:0% there might be some problems connecting with<00:48:08.589> like<00:48:08.980> a<00:48:09.009> using<00:48:09.490> one<00:48:09.700> language<00:48:09.910> or 00:48:10.319 --> 00:48:10.329 align:start position:0% with like a using one language or 00:48:10.329 --> 00:48:12.599 align:start position:0% with like a using one language or possible<00:48:10.809> I<00:48:10.960> don't<00:48:11.140> know<00:48:11.259> some<00:48:11.500> drawbacks<00:48:11.710> to 00:48:12.599 --> 00:48:12.609 align:start position:0% possible I don't know some drawbacks to 00:48:12.609 --> 00:48:14.430 align:start position:0% possible I don't know some drawbacks to do<00:48:12.730> shared<00:48:12.970> like<00:48:13.180> your<00:48:13.599> experience<00:48:14.170> when<00:48:14.410> you 00:48:14.430 --> 00:48:14.440 align:start position:0% do shared like your experience when you 00:48:14.440 --> 00:48:16.380 align:start position:0% do shared like your experience when you were<00:48:14.559> actually<00:48:15.069> trying<00:48:15.430> to<00:48:15.519> use<00:48:15.789> different 00:48:16.380 --> 00:48:16.390 align:start position:0% were actually trying to use different 00:48:16.390 --> 00:48:18.660 align:start position:0% were actually trying to use different languages<00:48:16.809> for<00:48:17.230> the<00:48:17.440> same<00:48:17.650> thing<00:48:17.859> yes<00:48:18.519> I'll 00:48:18.660 --> 00:48:18.670 align:start position:0% languages for the same thing yes I'll 00:48:18.670 --> 00:48:19.859 align:start position:0% languages for the same thing yes I'll just<00:48:18.700> repeat<00:48:19.059> the<00:48:19.180> question<00:48:19.210> first 00:48:19.859 --> 00:48:19.869 align:start position:0% just repeat the question first 00:48:19.869 --> 00:48:21.710 align:start position:0% just repeat the question first so<00:48:20.859> the 00:48:21.710 --> 00:48:21.720 align:start position:0% so the 00:48:21.720 --> 00:48:23.420 align:start position:0% so the if<00:48:22.140> I<00:48:22.260> understand<00:48:22.650> correctly<00:48:22.740> is<00:48:23.160> that<00:48:23.190> we 00:48:23.420 --> 00:48:23.430 align:start position:0% if I understand correctly is that we 00:48:23.430 --> 00:48:25.760 align:start position:0% if I understand correctly is that we just<00:48:23.670> explained<00:48:24.510> that<00:48:24.900> one<00:48:25.230> of<00:48:25.320> the<00:48:25.380> benefits 00:48:25.760 --> 00:48:25.770 align:start position:0% just explained that one of the benefits 00:48:25.770 --> 00:48:28.130 align:start position:0% just explained that one of the benefits of<00:48:25.920> a<00:48:26.400> well<00:48:26.760> Simon<00:48:26.910> wasum<00:48:27.330> is<00:48:27.450> that<00:48:27.599> it<00:48:27.720> allows 00:48:28.130 --> 00:48:28.140 align:start position:0% of a well Simon wasum is that it allows 00:48:28.140 --> 00:48:29.780 align:start position:0% of a well Simon wasum is that it allows us<00:48:28.170> to<00:48:28.349> write<00:48:28.590> contracts<00:48:29.070> in<00:48:29.190> many<00:48:29.310> languages 00:48:29.780 --> 00:48:29.790 align:start position:0% us to write contracts in many languages 00:48:29.790 --> 00:48:31.670 align:start position:0% us to write contracts in many languages you<00:48:30.330> saw<00:48:30.480> demos<00:48:30.780> of<00:48:30.810> two<00:48:31.109> of<00:48:31.230> them<00:48:31.349> right<00:48:31.530> now 00:48:31.670 --> 00:48:31.680 align:start position:0% you saw demos of two of them right now 00:48:31.680 --> 00:48:34.460 align:start position:0% you saw demos of two of them right now and<00:48:31.950> so<00:48:32.430> share<00:48:33.210> your<00:48:33.390> experiences<00:48:33.930> you<00:48:34.349> know 00:48:34.460 --> 00:48:34.470 align:start position:0% and so share your experiences you know 00:48:34.470 --> 00:48:35.690 align:start position:0% and so share your experiences you know which<00:48:34.800> ones<00:48:35.010> have<00:48:35.160> been<00:48:35.220> working<00:48:35.550> better 00:48:35.690 --> 00:48:35.700 align:start position:0% which ones have been working better 00:48:35.700 --> 00:48:37.310 align:start position:0% which ones have been working better which<00:48:35.970> have<00:48:36.180> not<00:48:36.450> been<00:48:36.570> working<00:48:36.690> so<00:48:36.990> well<00:48:37.140> are 00:48:37.310 --> 00:48:37.320 align:start position:0% which have not been working so well are 00:48:37.320 --> 00:48:39.680 align:start position:0% which have not been working so well are there<00:48:37.440> sort<00:48:37.680> of<00:48:37.820> advantages<00:48:38.820> or<00:48:39.060> drawbacks<00:48:39.240> to 00:48:39.680 --> 00:48:39.690 align:start position:0% there sort of advantages or drawbacks to 00:48:39.690 --> 00:48:41.330 align:start position:0% there sort of advantages or drawbacks to any<00:48:39.869> of<00:48:40.020> them<00:48:40.200> you<00:48:40.770> might<00:48:40.890> want<00:48:41.010> to<00:48:41.040> take<00:48:41.220> that 00:48:41.330 --> 00:48:41.340 align:start position:0% any of them you might want to take that 00:48:41.340 --> 00:48:44.720 align:start position:0% any of them you might want to take that question<00:48:43.099> I'm<00:48:44.099> just<00:48:44.280> gonna<00:48:44.369> put<00:48:44.550> it<00:48:44.640> out 00:48:44.720 --> 00:48:44.730 align:start position:0% question I'm just gonna put it out 00:48:44.730 --> 00:48:47.570 align:start position:0% question I'm just gonna put it out obviously<00:48:45.510> solidity<00:48:45.960> is<00:48:46.109> the<00:48:46.200> best<00:48:46.430> to<00:48:47.430> write 00:48:47.570 --> 00:48:47.580 align:start position:0% obviously solidity is the best to write 00:48:47.580 --> 00:48:50.000 align:start position:0% obviously solidity is the best to write contracts<00:48:48.000> in<00:48:48.180> but<00:48:49.140> that's<00:48:49.500> for<00:48:49.710> the<00:48:49.800> fact 00:48:50.000 --> 00:48:50.010 align:start position:0% contracts in but that's for the fact 00:48:50.010 --> 00:48:51.589 align:start position:0% contracts in but that's for the fact that<00:48:50.099> you<00:48:50.310> guys<00:48:50.520> are<00:48:50.730> familiar<00:48:50.849> with<00:48:51.119> solidity 00:48:51.589 --> 00:48:51.599 align:start position:0% that you guys are familiar with solidity 00:48:51.599 --> 00:48:53.780 align:start position:0% that you guys are familiar with solidity and<00:48:51.840> you<00:48:52.349> can<00:48:52.470> take<00:48:52.619> all<00:48:52.740> the<00:48:52.770> execs<00:48:53.130> existing 00:48:53.780 --> 00:48:53.790 align:start position:0% and you can take all the execs existing 00:48:53.790 --> 00:48:56.150 align:start position:0% and you can take all the execs existing code<00:48:54.000> and<00:48:54.030> compile<00:48:54.450> it<00:48:54.480> wasn't<00:48:54.990> once<00:48:55.830> we<00:48:56.040> get 00:48:56.150 --> 00:48:56.160 align:start position:0% code and compile it wasn't once we get 00:48:56.160 --> 00:48:58.180 align:start position:0% code and compile it wasn't once we get that<00:48:56.369> done<00:48:56.490> but<00:48:56.670> it's<00:48:56.820> not<00:48:56.880> done<00:48:57.090> yet 00:48:58.180 --> 00:48:58.190 align:start position:0% that done but it's not done yet 00:48:58.190 --> 00:49:00.680 align:start position:0% that done but it's not done yet so<00:48:59.190> right<00:48:59.369> now<00:48:59.580> the<00:48:59.640> the<00:48:59.940> next<00:49:00.390> best<00:49:00.570> thing 00:49:00.680 --> 00:49:00.690 align:start position:0% so right now the the next best thing 00:49:00.690 --> 00:49:04.730 align:start position:0% so right now the the next best thing probably<00:49:01.170> is<00:49:01.320> rust<00:49:01.820> if<00:49:02.820> you<00:49:03.000> know<00:49:03.119> rust<00:49:03.619> but<00:49:04.619> it 00:49:04.730 --> 00:49:04.740 align:start position:0% probably is rust if you know rust but it 00:49:04.740 --> 00:49:07.370 align:start position:0% probably is rust if you know rust but it does<00:49:04.859> have<00:49:05.010> a<00:49:05.070> steep<00:49:05.280> learning<00:49:05.430> curve<00:49:05.869> but<00:49:06.869> it 00:49:07.370 --> 00:49:07.380 align:start position:0% does have a steep learning curve but it 00:49:07.380 --> 00:49:09.290 align:start position:0% does have a steep learning curve but it has<00:49:07.560> the<00:49:07.740> most<00:49:07.920> mature<00:49:08.250> tooling<00:49:08.820> around<00:49:08.970> it 00:49:09.290 --> 00:49:09.300 align:start position:0% has the most mature tooling around it 00:49:09.300 --> 00:49:11.060 align:start position:0% has the most mature tooling around it and<00:49:09.540> even<00:49:09.869> our<00:49:10.080> tooling<00:49:10.440> around<00:49:10.560> it<00:49:10.859> is<00:49:10.980> the 00:49:11.060 --> 00:49:11.070 align:start position:0% and even our tooling around it is the 00:49:11.070 --> 00:49:12.440 align:start position:0% and even our tooling around it is the most<00:49:11.250> mature<00:49:11.400> one 00:49:12.440 --> 00:49:12.450 align:start position:0% most mature one 00:49:12.450 --> 00:49:16.070 align:start position:0% most mature one if<00:49:13.140> you<00:49:13.410> feel<00:49:13.970> extremely<00:49:14.990> confident<00:49:15.990> you 00:49:16.070 --> 00:49:16.080 align:start position:0% if you feel extremely confident you 00:49:16.080 --> 00:49:19.550 align:start position:0% if you feel extremely confident you could<00:49:16.230> try<00:49:16.380> C++<00:49:16.890> or<00:49:17.130> C<00:49:17.910> I<00:49:18.380> wouldn't<00:49:19.380> recommend 00:49:19.550 --> 00:49:19.560 align:start position:0% could try C++ or C I wouldn't recommend 00:49:19.560 --> 00:49:22.280 align:start position:0% could try C++ or C I wouldn't recommend it<00:49:19.710> personally<00:49:20.510> we<00:49:21.510> do<00:49:21.630> need<00:49:21.810> a<00:49:21.840> lot<00:49:21.960> of<00:49:22.020> help 00:49:22.280 --> 00:49:22.290 align:start position:0% it personally we do need a lot of help 00:49:22.290 --> 00:49:24.740 align:start position:0% it personally we do need a lot of help to<00:49:22.320> finish<00:49:22.680> the<00:49:22.859> assembly<00:49:23.010> script<00:49:23.369> and<00:49:23.849> so 00:49:24.740 --> 00:49:24.750 align:start position:0% to finish the assembly script and so 00:49:24.750 --> 00:49:27.200 align:start position:0% to finish the assembly script and so probably<00:49:25.020> I<00:49:25.230> would<00:49:25.830> try<00:49:26.010> to<00:49:26.040> direct<00:49:26.580> you<00:49:27.119> know 00:49:27.200 --> 00:49:27.210 align:start position:0% probably I would try to direct you know 00:49:27.210 --> 00:49:28.790 align:start position:0% probably I would try to direct you know all<00:49:27.390> the<00:49:27.510> effort<00:49:28.050> into<00:49:28.290> that<00:49:28.380> direction 00:49:28.790 --> 00:49:28.800 align:start position:0% all the effort into that direction 00:49:28.800 --> 00:49:30.500 align:start position:0% all the effort into that direction unless<00:49:29.490> you<00:49:29.700> want<00:49:29.820> to<00:49:29.880> work<00:49:30.000> on<00:49:30.119> solidity 00:49:30.500 --> 00:49:30.510 align:start position:0% unless you want to work on solidity 00:49:30.510 --> 00:49:32.900 align:start position:0% unless you want to work on solidity compiler<00:49:31.050> to<00:49:31.800> have<00:49:31.890> us<00:49:32.160> on<00:49:32.190> so<00:49:32.460> these<00:49:32.580> are<00:49:32.760> like 00:49:32.900 --> 00:49:32.910 align:start position:0% compiler to have us on so these are like 00:49:32.910 --> 00:49:36.170 align:start position:0% compiler to have us on so these are like the<00:49:33.030> two<00:49:33.210> main<00:49:33.619> directions<00:49:34.619> to<00:49:35.010> to<00:49:35.369> enable 00:49:36.170 --> 00:49:36.180 align:start position:0% the two main directions to to enable 00:49:36.180 --> 00:49:37.910 align:start position:0% the two main directions to to enable contracts<00:49:36.750> easy<00:49:36.930> contract<00:49:37.349> writing<00:49:37.530> to 00:49:37.910 --> 00:49:37.920 align:start position:0% contracts easy contract writing to 00:49:37.920 --> 00:49:42.500 align:start position:0% contracts easy contract writing to people<00:49:39.410> yeah<00:49:40.410> forget<00:49:40.650> about<00:49:40.710> it<00:49:40.950> go<00:49:41.359> we<00:49:42.359> should 00:49:42.500 --> 00:49:42.510 align:start position:0% people yeah forget about it go we should 00:49:42.510 --> 00:49:44.060 align:start position:0% people yeah forget about it go we should do<00:49:42.630> an<00:49:42.720> introduction<00:49:43.080> here<00:49:43.349> though<00:49:43.500> if<00:49:43.710> you 00:49:44.060 --> 00:49:44.070 align:start position:0% do an introduction here though if you 00:49:44.070 --> 00:49:45.980 align:start position:0% do an introduction here though if you want<00:49:44.130> to<00:49:44.250> ask<00:49:44.310> proper<00:49:44.670> questions<00:49:45.030> cause<00:49:45.900> you 00:49:45.980 --> 00:49:45.990 align:start position:0% want to ask proper questions cause you 00:49:45.990 --> 00:49:46.820 align:start position:0% want to ask proper questions cause you want<00:49:46.109> to<00:49:46.140> start<00:49:46.320> we'll<00:49:46.440> just<00:49:46.560> go<00:49:46.619> down<00:49:46.650> the 00:49:46.820 --> 00:49:46.830 align:start position:0% want to start we'll just go down the 00:49:46.830 --> 00:49:56.950 align:start position:0% want to start we'll just go down the line<00:49:48.440> doesn't<00:49:49.440> do<00:49:49.589> them<00:49:49.680> like<00:49:54.440> I'm<00:49:55.440> Casey<00:49:55.740> and 00:49:56.950 --> 00:49:56.960 align:start position:0% line doesn't do them like I'm Casey and 00:49:56.960 --> 00:49:59.300 align:start position:0% line doesn't do them like I'm Casey and just<00:49:57.960> to<00:49:58.050> answer<00:49:58.170> the<00:49:58.410> question<00:49:58.770> I<00:49:58.859> think<00:49:58.950> one 00:49:59.300 --> 00:49:59.310 align:start position:0% just to answer the question I think one 00:49:59.310 --> 00:50:01.880 align:start position:0% just to answer the question I think one of<00:49:59.339> the<00:50:00.140> advantages<00:50:01.140> of<00:50:01.200> webassembly 00:50:01.880 --> 00:50:01.890 align:start position:0% of the advantages of webassembly 00:50:01.890 --> 00:50:04.849 align:start position:0% of the advantages of webassembly is<00:50:02.869> the<00:50:03.869> interoperability<00:50:04.290> between 00:50:04.849 --> 00:50:04.859 align:start position:0% is the interoperability between 00:50:04.859 --> 00:50:06.680 align:start position:0% is the interoperability between different<00:50:05.790> languages<00:50:06.180> so<00:50:06.330> you<00:50:06.390> can<00:50:06.510> take 00:50:06.680 --> 00:50:06.690 align:start position:0% different languages so you can take 00:50:06.690 --> 00:50:09.410 align:start position:0% different languages so you can take library<00:50:07.290> that<00:50:07.650> was<00:50:07.800> you<00:50:08.280> know<00:50:08.400> that's<00:50:09.000> in<00:50:09.180> rust 00:50:09.410 --> 00:50:09.420 align:start position:0% library that was you know that's in rust 00:50:09.420 --> 00:50:11.420 align:start position:0% library that was you know that's in rust compile<00:50:10.290> it<00:50:10.380> down<00:50:10.410> to<00:50:10.500> web<00:50:10.680> assembly<00:50:11.130> then<00:50:11.339> you 00:50:11.420 --> 00:50:11.430 align:start position:0% compile it down to web assembly then you 00:50:11.430 --> 00:50:14.210 align:start position:0% compile it down to web assembly then you can<00:50:11.550> call<00:50:11.760> that<00:50:11.940> from<00:50:12.270> and<00:50:13.020> it's<00:50:13.230> some 00:50:14.210 --> 00:50:14.220 align:start position:0% can call that from and it's some 00:50:14.220 --> 00:50:17.420 align:start position:0% can call that from and it's some assembly<00:50:14.580> script<00:50:14.820> code<00:50:15.589> so<00:50:16.589> being<00:50:17.220> able<00:50:17.310> to 00:50:17.420 --> 00:50:17.430 align:start position:0% assembly script code so being able to 00:50:17.430 --> 00:50:19.700 align:start position:0% assembly script code so being able to mix<00:50:17.640> these<00:50:18.300> different<00:50:18.810> high<00:50:19.080> level<00:50:19.349> languages 00:50:19.700 --> 00:50:19.710 align:start position:0% mix these different high level languages 00:50:19.710 --> 00:50:24.650 align:start position:0% mix these different high level languages I<00:50:19.830> think<00:50:19.859> is<00:50:20.099> a<00:50:20.570> good<00:50:21.570> advantage<00:50:22.369> you<00:50:23.369> go<00:50:23.660> hi 00:50:24.650 --> 00:50:24.660 align:start position:0% I think is a good advantage you go hi 00:50:24.660 --> 00:50:29.500 align:start position:0% I think is a good advantage you go hi everyone<00:50:25.080> my<00:50:25.710> name<00:50:25.859> is<00:50:25.890> Google<00:50:26.839> I'm<00:50:27.839> working 00:50:29.500 --> 00:50:29.510 align:start position:0% everyone my name is Google I'm working 00:50:29.510 --> 00:50:33.079 align:start position:0% everyone my name is Google I'm working mostly<00:50:30.510> on<00:50:30.810> writing<00:50:31.290> test<00:50:31.920> cases<00:50:32.160> using<00:50:32.730> the 00:50:33.079 --> 00:50:33.089 align:start position:0% mostly on writing test cases using the 00:50:33.089 --> 00:50:35.450 align:start position:0% mostly on writing test cases using the web<00:50:33.480> assembly<00:50:33.960> text<00:50:34.560> format<00:50:34.950> which<00:50:35.130> is 00:50:35.450 --> 00:50:35.460 align:start position:0% web assembly text format which is 00:50:35.460 --> 00:50:39.589 align:start position:0% web assembly text format which is really<00:50:35.760> really<00:50:35.940> fun<00:50:36.710> and<00:50:38.000> yeah<00:50:39.000> helping<00:50:39.510> a 00:50:39.589 --> 00:50:39.599 align:start position:0% really really fun and yeah helping a 00:50:39.599 --> 00:50:41.750 align:start position:0% really really fun and yeah helping a little<00:50:39.869> bit<00:50:40.020> on<00:50:40.170> the<00:50:40.290> on<00:50:40.800> the<00:50:41.160> US<00:50:41.609> and 00:50:41.750 --> 00:50:41.760 align:start position:0% little bit on the on the US and 00:50:41.760 --> 00:50:46.250 align:start position:0% little bit on the on the US and explorers<00:50:42.210> well<00:50:44.599> hi<00:50:45.599> my<00:50:45.809> name<00:50:45.930> is<00:50:45.960> Guillaume 00:50:46.250 --> 00:50:46.260 align:start position:0% explorers well hi my name is Guillaume 00:50:46.260 --> 00:50:48.980 align:start position:0% explorers well hi my name is Guillaume I'm<00:50:46.500> a<00:50:46.650> member<00:50:46.920> of<00:50:47.069> the<00:50:47.369> go<00:50:47.579> team<00:50:47.849> and<00:50:48.210> also<00:50:48.359> of 00:50:48.980 --> 00:50:48.990 align:start position:0% I'm a member of the go team and also of 00:50:48.990 --> 00:50:52.250 align:start position:0% I'm a member of the go team and also of it<00:50:49.200> was<00:50:49.349> him<00:50:49.500> obviously<00:50:50.270> yes<00:50:51.270> so<00:50:51.510> just<00:50:52.079> to 00:50:52.250 --> 00:50:52.260 align:start position:0% it was him obviously yes so just to 00:50:52.260 --> 00:50:55.190 align:start position:0% it was him obviously yes so just to wanted<00:50:52.950> to<00:50:53.069> say<00:50:53.309> when<00:50:54.210> it<00:50:54.300> comes<00:50:54.480> to<00:50:54.599> gogo<00:50:55.020> as<00:50:55.170> a 00:50:55.190 --> 00:50:55.200 align:start position:0% wanted to say when it comes to gogo as a 00:50:55.200 --> 00:50:57.920 align:start position:0% wanted to say when it comes to gogo as a very<00:50:55.559> limited<00:50:56.010> support<00:50:56.579> of<00:50:56.849> well<00:50:57.690> very 00:50:57.920 --> 00:50:57.930 align:start position:0% very limited support of well very 00:50:57.930 --> 00:50:59.870 align:start position:0% very limited support of well very experimental<00:50:58.589> support<00:50:58.740> of<00:50:59.069> webassembly 00:50:59.870 --> 00:50:59.880 align:start position:0% experimental support of webassembly 00:50:59.880 --> 00:51:01.849 align:start position:0% experimental support of webassembly so<00:51:00.390> and<00:51:00.809> it's<00:51:00.960> got<00:51:01.140> all<00:51:01.319> those<00:51:01.470> features<00:51:01.829> that 00:51:01.849 --> 00:51:01.859 align:start position:0% so and it's got all those features that 00:51:01.859 --> 00:51:03.140 align:start position:0% so and it's got all those features that you<00:51:02.099> don't<00:51:02.309> need<00:51:02.460> in<00:51:02.609> the<00:51:02.760> case<00:51:03.000> of 00:51:03.140 --> 00:51:03.150 align:start position:0% you don't need in the case of 00:51:03.150 --> 00:51:05.059 align:start position:0% you don't need in the case of webassembly<00:51:03.839> like<00:51:04.170> the<00:51:04.290> garbage<00:51:04.650> collector 00:51:05.059 --> 00:51:05.069 align:start position:0% webassembly like the garbage collector 00:51:05.069 --> 00:51:08.870 align:start position:0% webassembly like the garbage collector all<00:51:05.250> that<00:51:05.400> stuff<00:51:05.670> so<00:51:06.680> like<00:51:07.680> binaries<00:51:08.550> you<00:51:08.700> get 00:51:08.870 --> 00:51:08.880 align:start position:0% all that stuff so like binaries you get 00:51:08.880 --> 00:51:11.000 align:start position:0% all that stuff so like binaries you get are<00:51:09.059> very<00:51:09.420> very<00:51:09.750> big<00:51:10.020> and<00:51:10.319> its<00:51:10.710> really<00:51:10.770> not 00:51:11.000 --> 00:51:11.010 align:start position:0% are very very big and its really not 00:51:11.010 --> 00:51:12.859 align:start position:0% are very very big and its really not appropriate<00:51:11.160> for<00:51:11.609> for<00:51:12.000> this<00:51:12.089> kind<00:51:12.270> of<00:51:12.329> use 00:51:12.859 --> 00:51:12.869 align:start position:0% appropriate for for this kind of use 00:51:12.869 --> 00:51:15.680 align:start position:0% appropriate for for this kind of use case<00:51:13.079> so<00:51:13.410> far<00:51:13.910> but<00:51:14.910> have<00:51:15.119> you<00:51:15.210> seen<00:51:15.390> that<00:51:15.510> there 00:51:15.680 --> 00:51:15.690 align:start position:0% case so far but have you seen that there 00:51:15.690 --> 00:51:19.460 align:start position:0% case so far but have you seen that there is<00:51:15.720> a<00:51:16.460> embedded<00:51:17.460> compiler<00:51:18.030> for<00:51:18.210> go<00:51:18.390> which<00:51:19.079> also 00:51:19.460 --> 00:51:19.470 align:start position:0% is a embedded compiler for go which also 00:51:19.470 --> 00:51:22.339 align:start position:0% is a embedded compiler for go which also supports<00:51:19.680> was<00:51:20.040> my<00:51:20.190> output<00:51:20.460> and<00:51:21.079> shows<00:51:22.079> out<00:51:22.230> the 00:51:22.339 --> 00:51:22.349 align:start position:0% supports was my output and shows out the 00:51:22.349 --> 00:51:26.750 align:start position:0% supports was my output and shows out the GC<00:51:22.680> and<00:51:23.309> its<00:51:23.609> GC<00:51:24.450> no<00:51:25.440> true<00:51:25.680> said<00:51:25.859> the<00:51:25.950> GC<00:51:26.250> of<00:51:26.339> go 00:51:26.750 --> 00:51:26.760 align:start position:0% GC and its GC no true said the GC of go 00:51:26.760 --> 00:51:29.000 align:start position:0% GC and its GC no true said the GC of go so<00:51:27.000> it's<00:51:27.150> tiny<00:51:27.300> yeah<00:51:27.780> okay<00:51:28.020> well<00:51:28.200> if<00:51:28.290> they<00:51:28.470> that 00:51:29.000 --> 00:51:29.010 align:start position:0% so it's tiny yeah okay well if they that 00:51:29.010 --> 00:51:30.140 align:start position:0% so it's tiny yeah okay well if they that would<00:51:29.130> be<00:51:29.220> interesting<00:51:29.550> no<00:51:29.609> I<00:51:29.640> didn't<00:51:29.910> know<00:51:30.000> it 00:51:30.140 --> 00:51:30.150 align:start position:0% would be interesting no I didn't know it 00:51:30.150 --> 00:51:31.579 align:start position:0% would be interesting no I didn't know it would<00:51:30.390> be<00:51:30.420> interesting<00:51:30.720> to<00:51:30.930> to<00:51:31.260> have<00:51:31.380> a<00:51:31.410> look 00:51:31.579 --> 00:51:31.589 align:start position:0% would be interesting to to have a look 00:51:31.589 --> 00:51:32.990 align:start position:0% would be interesting to to have a look at<00:51:31.680> it<00:51:31.800> still<00:51:32.369> don't<00:51:32.520> think<00:51:32.700> it's<00:51:32.819> a<00:51:32.910> great 00:51:32.990 --> 00:51:33.000 align:start position:0% at it still don't think it's a great 00:51:33.000 --> 00:51:38.780 align:start position:0% at it still don't think it's a great language<00:51:33.180> for<00:51:33.390> that<00:51:33.540> but<00:51:33.839> yeah<00:51:36.349> yeah<00:51:37.790> yeah 00:51:38.780 --> 00:51:38.790 align:start position:0% language for that but yeah yeah yeah 00:51:38.790 --> 00:51:43.839 align:start position:0% language for that but yeah yeah yeah Alex<00:51:39.180> Cody<00:51:39.900> gave<00:51:40.530> the<00:51:41.010> spiel<00:51:41.280> on<00:51:41.309> me<00:51:42.710> yeah 00:51:43.839 --> 00:51:43.849 align:start position:0% Alex Cody gave the spiel on me yeah 00:51:43.849 --> 00:51:46.450 align:start position:0% Alex Cody gave the spiel on me yeah Jared<00:51:44.849> party<00:51:45.359> Watson<00:51:45.720> team 00:51:46.450 --> 00:51:46.460 align:start position:0% Jared party Watson team 00:51:46.460 --> 00:51:50.390 align:start position:0% Jared party Watson team I've<00:51:47.460> also<00:51:47.900> in<00:51:48.900> addition<00:51:49.140> to<00:51:49.589> working<00:51:50.069> on 00:51:50.390 --> 00:51:50.400 align:start position:0% I've also in addition to working on 00:51:50.400 --> 00:51:51.109 align:start position:0% I've also in addition to working on DevOps 00:51:51.109 --> 00:51:51.119 align:start position:0% DevOps 00:51:51.119 --> 00:51:55.069 align:start position:0% DevOps I<00:51:51.420> have<00:51:52.290> written<00:51:52.770> a<00:51:53.250> few<00:51:53.760> adapters<00:51:54.630> for 00:51:55.069 --> 00:51:55.079 align:start position:0% I have written a few adapters for 00:51:55.079 --> 00:51:58.220 align:start position:0% I have written a few adapters for bringing<00:51:55.670> DNS<00:51:56.670> SEC<00:51:56.910> more<00:51:57.329> cryptography<00:51:58.200> for 00:51:58.220 --> 00:51:58.230 align:start position:0% bringing DNS SEC more cryptography for 00:51:58.230 --> 00:52:00.829 align:start position:0% bringing DNS SEC more cryptography for DNS<00:51:58.770> specifically<00:51:59.730> edy<00:52:00.150> two<00:52:00.299> five<00:52:00.480> five<00:52:00.630> one 00:52:00.829 --> 00:52:00.839 align:start position:0% DNS specifically edy two five five one 00:52:00.839 --> 00:52:05.870 align:start position:0% DNS specifically edy two five five one nine<00:52:01.730> two<00:52:02.780> the<00:52:03.780> as<00:52:04.619> a<00:52:04.680> pre<00:52:04.920> compile<00:52:05.250> three<00:52:05.790> he 00:52:05.870 --> 00:52:05.880 align:start position:0% nine two the as a pre compile three he 00:52:05.880 --> 00:52:14.329 align:start position:0% nine two the as a pre compile three he wasn't<00:52:08.089> yeah<00:52:09.619> that's<00:52:10.619> it<00:52:12.950> well<00:52:13.950> you<00:52:14.069> know<00:52:14.099> me<00:52:14.309> I 00:52:14.329 --> 00:52:14.339 align:start position:0% wasn't yeah that's it well you know me I 00:52:14.339 --> 00:52:16.789 align:start position:0% wasn't yeah that's it well you know me I had<00:52:14.609> to<00:52:14.700> talk<00:52:15.020> so<00:52:16.020> just<00:52:16.200> passi<00:52:16.349> don't<00:52:16.559> Alain 00:52:16.789 --> 00:52:16.799 align:start position:0% had to talk so just passi don't Alain 00:52:16.799 --> 00:52:21.410 align:start position:0% had to talk so just passi don't Alain Alain<00:52:17.660> I<00:52:18.829> have<00:52:19.829> been<00:52:20.220> working<00:52:20.760> on<00:52:20.880> tests<00:52:21.240> with 00:52:21.410 --> 00:52:21.420 align:start position:0% Alain I have been working on tests with 00:52:21.420 --> 00:52:23.059 align:start position:0% Alain I have been working on tests with Hugo<00:52:21.780> I've<00:52:22.109> been<00:52:22.290> working<00:52:22.589> on<00:52:22.710> the<00:52:22.859> assembly 00:52:23.059 --> 00:52:23.069 align:start position:0% Hugo I've been working on the assembly 00:52:23.069 --> 00:52:24.710 align:start position:0% Hugo I've been working on the assembly script<00:52:23.490> which<00:52:23.609> you<00:52:23.640> already<00:52:23.849> saw<00:52:23.970> and<00:52:24.569> then 00:52:24.710 --> 00:52:24.720 align:start position:0% script which you already saw and then 00:52:24.720 --> 00:52:27.099 align:start position:0% script which you already saw and then kind<00:52:25.020> of<00:52:25.079> things<00:52:25.260> like<00:52:25.410> documentation<00:52:26.130> and 00:52:27.099 --> 00:52:27.109 align:start position:0% kind of things like documentation and 00:52:27.109 --> 00:52:28.910 align:start position:0% kind of things like documentation and education<00:52:28.109> let's<00:52:28.290> call<00:52:28.470> it<00:52:28.530> like<00:52:28.619> trying<00:52:28.859> to 00:52:28.910 --> 00:52:28.920 align:start position:0% education let's call it like trying to 00:52:28.920 --> 00:52:30.289 align:start position:0% education let's call it like trying to organize<00:52:29.190> events<00:52:29.339> and<00:52:29.790> get<00:52:29.970> people<00:52:30.180> excited 00:52:30.289 --> 00:52:30.299 align:start position:0% organize events and get people excited 00:52:30.299 --> 00:52:35.500 align:start position:0% organize events and get people excited about<00:52:30.569> you<00:52:30.780> also<00:52:31.490> yeah<00:52:33.650> writing 00:52:35.500 --> 00:52:35.510 align:start position:0% about you also yeah writing 00:52:35.510 --> 00:52:38.029 align:start position:0% about you also yeah writing thank<00:52:36.510> you<00:52:36.599> for<00:52:36.720> writing<00:52:37.289> writing<00:52:37.710> code<00:52:37.890> is 00:52:38.029 --> 00:52:38.039 align:start position:0% thank you for writing writing code is 00:52:38.039 --> 00:52:39.500 align:start position:0% thank you for writing writing code is easy<00:52:38.220> building<00:52:38.640> communities<00:52:39.000> is<00:52:39.119> hard<00:52:39.329> so 00:52:39.500 --> 00:52:39.510 align:start position:0% easy building communities is hard so 00:52:39.510 --> 00:52:43.339 align:start position:0% easy building communities is hard so community<00:52:39.900> FTW<00:52:40.890> I'm<00:52:41.579> Paulo<00:52:41.910> and<00:52:42.240> yeah 00:52:43.339 --> 00:52:43.349 align:start position:0% community FTW I'm Paulo and yeah 00:52:43.349 --> 00:52:45.650 align:start position:0% community FTW I'm Paulo and yeah C++<00:52:43.710> stuff<00:52:44.190> maybe<00:52:44.460> we<00:52:44.819> just<00:52:45.059> go<00:52:45.299> back<00:52:45.450> to 00:52:45.650 --> 00:52:45.660 align:start position:0% C++ stuff maybe we just go back to 00:52:45.660 --> 00:52:48.109 align:start position:0% C++ stuff maybe we just go back to questions<00:52:46.490> what<00:52:47.490> Paul<00:52:47.730> won't<00:52:47.880> introduce 00:52:48.109 --> 00:52:48.119 align:start position:0% questions what Paul won't introduce 00:52:48.119 --> 00:52:50.930 align:start position:0% questions what Paul won't introduce yourself<00:52:48.599> when<00:52:49.230> Paul<00:52:50.069> trained<00:52:50.369> in<00:52:50.460> math<00:52:50.609> I 00:52:50.930 --> 00:52:50.940 align:start position:0% yourself when Paul trained in math I 00:52:50.940 --> 00:52:53.510 align:start position:0% yourself when Paul trained in math I just<00:52:51.480> do<00:52:51.839> some<00:52:52.049> basic<00:52:52.470> stuff<00:52:52.650> that<00:52:52.710> helps 00:52:53.510 --> 00:52:53.520 align:start position:0% just do some basic stuff that helps 00:52:53.520 --> 00:52:56.180 align:start position:0% just do some basic stuff that helps everyone<00:52:53.730> out<00:52:54.440> Paul<00:52:55.440> is<00:52:55.529> very<00:52:55.559> impulsive<00:52:55.920> Airy 00:52:56.180 --> 00:52:56.190 align:start position:0% everyone out Paul is very impulsive Airy 00:52:56.190 --> 00:52:58.010 align:start position:0% everyone out Paul is very impulsive Airy modest<00:52:56.549> but<00:52:56.730> he's<00:52:57.150> the<00:52:57.390> cornerstone<00:52:57.809> of<00:52:57.839> the 00:52:58.010 --> 00:52:58.020 align:start position:0% modest but he's the cornerstone of the 00:52:58.020 --> 00:53:11.029 align:start position:0% modest but he's the cornerstone of the team<00:53:08.359> all<00:53:09.359> right<00:53:09.539> sorry<00:53:10.230> you<00:53:10.470> guys 00:53:11.029 --> 00:53:11.039 align:start position:0% team all right sorry you guys 00:53:11.039 --> 00:53:13.339 align:start position:0% team all right sorry you guys yeah<00:53:11.279> I<00:53:11.309> thought<00:53:11.520> this<00:53:11.730> assembly<00:53:12.690> script<00:53:13.079> demo 00:53:13.339 --> 00:53:13.349 align:start position:0% yeah I thought this assembly script demo 00:53:13.349 --> 00:53:16.279 align:start position:0% yeah I thought this assembly script demo was<00:53:14.309> awesome<00:53:14.430> so<00:53:15.390> like<00:53:15.510> what<00:53:15.839> what 00:53:16.279 --> 00:53:16.289 align:start position:0% was awesome so like what what 00:53:16.289 --> 00:53:20.059 align:start position:0% was awesome so like what what work<00:53:16.950> is<00:53:17.279> left<00:53:17.670> to<00:53:18.299> sort<00:53:18.839> of<00:53:18.930> get<00:53:19.410> assembly 00:53:20.059 --> 00:53:20.069 align:start position:0% work is left to sort of get assembly 00:53:20.069 --> 00:53:26.210 align:start position:0% work is left to sort of get assembly script<00:53:20.839> to<00:53:21.839> a<00:53:21.890> a<00:53:23.660> good<00:53:24.660> level<00:53:24.900> and<00:53:25.440> like<00:53:25.950> so 00:53:26.210 --> 00:53:26.220 align:start position:0% script to a a good level and like so 00:53:26.220 --> 00:53:28.279 align:start position:0% script to a a good level and like so this<00:53:26.369> is<00:53:26.460> my<00:53:26.520> first<00:53:26.730> time<00:53:26.880> sort<00:53:27.299> of<00:53:27.420> learning<00:53:27.900> a 00:53:28.279 --> 00:53:28.289 align:start position:0% this is my first time sort of learning a 00:53:28.289 --> 00:53:30.349 align:start position:0% this is my first time sort of learning a lot<00:53:28.380> about<00:53:28.619> like<00:53:28.890> Wazza<00:53:29.369> mandy<00:53:29.849> was<00:53:30.059> um<00:53:30.240> so 00:53:30.349 --> 00:53:30.359 align:start position:0% lot about like Wazza mandy was um so 00:53:30.359 --> 00:53:34.400 align:start position:0% lot about like Wazza mandy was um so like<00:53:30.450> what<00:53:30.690> steps<00:53:31.049> are<00:53:31.770> there<00:53:32.490> left<00:53:33.000> to<00:53:33.720> you 00:53:34.400 --> 00:53:34.410 align:start position:0% like what steps are there left to you 00:53:34.410 --> 00:53:35.900 align:start position:0% like what steps are there left to you know<00:53:34.500> write<00:53:34.770> a<00:53:34.799> contract<00:53:35.400> and<00:53:35.549> assembly 00:53:35.900 --> 00:53:35.910 align:start position:0% know write a contract and assembly 00:53:35.910 --> 00:53:38.120 align:start position:0% know write a contract and assembly script<00:53:36.210> and<00:53:36.390> be<00:53:36.480> able<00:53:36.569> to<00:53:36.900> deploy<00:53:37.319> it<00:53:37.529> on<00:53:37.710> the 00:53:38.120 --> 00:53:38.130 align:start position:0% script and be able to deploy it on the 00:53:38.130 --> 00:53:39.069 align:start position:0% script and be able to deploy it on the current 00:53:39.069 --> 00:53:39.079 align:start position:0% current 00:53:39.079 --> 00:53:42.230 align:start position:0% current etherium<00:53:40.079> main<00:53:40.380> net<00:53:40.619> cool<00:53:41.369> I'm<00:53:41.579> glad<00:53:41.970> you're 00:53:42.230 --> 00:53:42.240 align:start position:0% etherium main net cool I'm glad you're 00:53:42.240 --> 00:53:43.880 align:start position:0% etherium main net cool I'm glad you're as<00:53:42.329> excited<00:53:42.450> about<00:53:42.779> assembly<00:53:43.380> script<00:53:43.589> as<00:53:43.680> I<00:53:43.770> am 00:53:43.880 --> 00:53:43.890 align:start position:0% as excited about assembly script as I am 00:53:43.890 --> 00:53:45.349 align:start position:0% as excited about assembly script as I am I<00:53:43.980> mean<00:53:44.099> I<00:53:44.160> really<00:53:44.430> I<00:53:44.609> said<00:53:44.819> this<00:53:44.910> before<00:53:45.059> I'll 00:53:45.349 --> 00:53:45.359 align:start position:0% I mean I really I said this before I'll 00:53:45.359 --> 00:53:46.519 align:start position:0% I mean I really I said this before I'll say<00:53:45.390> it<00:53:45.630> again<00:53:45.690> I<00:53:45.839> really<00:53:46.109> think<00:53:46.289> that<00:53:46.380> this<00:53:46.470> is 00:53:46.519 --> 00:53:46.529 align:start position:0% say it again I really think that this is 00:53:46.529 --> 00:53:48.140 align:start position:0% say it again I really think that this is a<00:53:46.650> platform<00:53:47.279> that<00:53:47.369> we<00:53:47.430> can<00:53:47.549> use<00:53:47.700> to<00:53:47.880> get<00:53:47.970> like 00:53:48.140 --> 00:53:48.150 align:start position:0% a platform that we can use to get like 00:53:48.150 --> 00:53:49.160 align:start position:0% a platform that we can use to get like millions<00:53:48.450> of<00:53:48.539> people<00:53:48.599> excited<00:53:48.990> about 00:53:49.160 --> 00:53:49.170 align:start position:0% millions of people excited about 00:53:49.170 --> 00:53:50.660 align:start position:0% millions of people excited about aetherium<00:53:49.650> who<00:53:49.770> may<00:53:49.890> not<00:53:50.039> be<00:53:50.309> excited<00:53:50.609> about 00:53:50.660 --> 00:53:50.670 align:start position:0% aetherium who may not be excited about 00:53:50.670 --> 00:53:54.260 align:start position:0% aetherium who may not be excited about solidity<00:53:51.150> all<00:53:51.510> due<00:53:51.720> respect<00:53:52.020> to<00:53:52.079> solidity<00:53:53.270> so 00:53:54.260 --> 00:53:54.270 align:start position:0% solidity all due respect to solidity so 00:53:54.270 --> 00:53:55.819 align:start position:0% solidity all due respect to solidity so I<00:53:54.569> didn't<00:53:54.930> have<00:53:54.990> a<00:53:55.049> chance<00:53:55.319> to<00:53:55.470> talk<00:53:55.650> about 00:53:55.819 --> 00:53:55.829 align:start position:0% I didn't have a chance to talk about 00:53:55.829 --> 00:53:56.299 align:start position:0% I didn't have a chance to talk about this 00:53:56.299 --> 00:53:56.309 align:start position:0% this 00:53:56.309 --> 00:53:59.089 align:start position:0% this so<00:53:56.750> assembly<00:53:57.750> script<00:53:58.020> is<00:53:58.230> a<00:53:58.260> obviously<00:53:58.980> an 00:53:59.089 --> 00:53:59.099 align:start position:0% so assembly script is a obviously an 00:53:59.099 --> 00:54:01.279 align:start position:0% so assembly script is a obviously an open<00:53:59.309> source<00:53:59.460> project<00:53:59.779> there's<00:54:00.779> a<00:54:00.839> small<00:54:01.079> team 00:54:01.279 --> 00:54:01.289 align:start position:0% open source project there's a small team 00:54:01.289 --> 00:54:03.319 align:start position:0% open source project there's a small team working<00:54:01.559> on<00:54:01.770> it<00:54:01.920> it's<00:54:02.220> kind<00:54:02.730> of<00:54:02.760> a<00:54:02.849> beta<00:54:03.059> I 00:54:03.319 --> 00:54:03.329 align:start position:0% working on it it's kind of a beta I 00:54:03.329 --> 00:54:05.960 align:start position:0% working on it it's kind of a beta I would<00:54:03.690> say<00:54:03.869> so<00:54:03.930> it<00:54:04.200> works<00:54:04.650> but<00:54:05.039> it's<00:54:05.279> volatile 00:54:05.960 --> 00:54:05.970 align:start position:0% would say so it works but it's volatile 00:54:05.970 --> 00:54:07.579 align:start position:0% would say so it works but it's volatile so<00:54:06.299> they<00:54:06.599> make<00:54:06.750> breaking<00:54:07.049> changes<00:54:07.380> sometimes 00:54:07.579 --> 00:54:07.589 align:start position:0% so they make breaking changes sometimes 00:54:07.589 --> 00:54:09.230 align:start position:0% so they make breaking changes sometimes which<00:54:07.950> has<00:54:08.069> sort<00:54:08.400> of<00:54:08.460> slowed<00:54:08.700> things<00:54:08.940> a<00:54:09.029> little 00:54:09.230 --> 00:54:09.240 align:start position:0% which has sort of slowed things a little 00:54:09.240 --> 00:54:13.130 align:start position:0% which has sort of slowed things a little bit<00:54:10.190> what<00:54:11.190> I've<00:54:11.339> done<00:54:11.730> is<00:54:12.059> I've<00:54:12.450> so<00:54:12.869> they<00:54:12.990> have 00:54:13.130 --> 00:54:13.140 align:start position:0% bit what I've done is I've so they have 00:54:13.140 --> 00:54:17.510 align:start position:0% bit what I've done is I've so they have a<00:54:13.170> data<00:54:13.650> compiler<00:54:14.119> that<00:54:15.119> takes<00:54:15.900> the<00:54:16.770> web 00:54:17.510 --> 00:54:17.520 align:start position:0% a data compiler that takes the web 00:54:17.520 --> 00:54:18.799 align:start position:0% a data compiler that takes the web assembly<00:54:17.880> sorry<00:54:18.150> the<00:54:18.270> assembly<00:54:18.539> script<00:54:18.750> that 00:54:18.799 --> 00:54:18.809 align:start position:0% assembly sorry the assembly script that 00:54:18.809 --> 00:54:20.569 align:start position:0% assembly sorry the assembly script that you<00:54:18.900> saw<00:54:19.049> and<00:54:19.319> and<00:54:19.559> runs<00:54:19.740> it<00:54:19.890> through<00:54:19.920> under 00:54:20.569 --> 00:54:20.579 align:start position:0% you saw and and runs it through under 00:54:20.579 --> 00:54:21.769 align:start position:0% you saw and and runs it through under the<00:54:20.670> hood<00:54:20.789> something<00:54:21.089> called<00:54:21.270> binary<00:54:21.599> and 00:54:21.769 --> 00:54:21.779 align:start position:0% the hood something called binary and 00:54:21.779 --> 00:54:24.200 align:start position:0% the hood something called binary and which<00:54:22.079> is<00:54:22.200> actually<00:54:22.529> a<00:54:22.770> sea<00:54:23.190> based<00:54:23.640> assembly 00:54:24.200 --> 00:54:24.210 align:start position:0% which is actually a sea based assembly 00:54:24.210 --> 00:54:25.400 align:start position:0% which is actually a sea based assembly script<00:54:24.420> compiler<00:54:24.750> and<00:54:24.839> then<00:54:24.930> produces<00:54:25.319> the 00:54:25.400 --> 00:54:25.410 align:start position:0% script compiler and then produces the 00:54:25.410 --> 00:54:27.019 align:start position:0% script compiler and then produces the assembly<00:54:25.680> script<00:54:25.920> code<00:54:26.039> sorry<00:54:26.520> the<00:54:26.700> wasum 00:54:27.019 --> 00:54:27.029 align:start position:0% assembly script code sorry the wasum 00:54:27.029 --> 00:54:30.019 align:start position:0% assembly script code sorry the wasum code<00:54:27.240> they<00:54:27.750> love<00:54:27.869> assembly<00:54:28.170> code<00:54:28.760> so<00:54:29.760> what 00:54:30.019 --> 00:54:30.029 align:start position:0% code they love assembly code so what 00:54:30.029 --> 00:54:31.789 align:start position:0% code they love assembly code so what i've<00:54:30.210> done<00:54:30.420> is<00:54:30.569> i've<00:54:30.690> hooked<00:54:31.079> into<00:54:31.410> their 00:54:31.789 --> 00:54:31.799 align:start position:0% i've done is i've hooked into their 00:54:31.799 --> 00:54:33.740 align:start position:0% i've done is i've hooked into their compiler<00:54:32.390> through<00:54:33.390> what's<00:54:33.569> called<00:54:33.599> a 00:54:33.740 --> 00:54:33.750 align:start position:0% compiler through what's called a 00:54:33.750 --> 00:54:35.089 align:start position:0% compiler through what's called a transform<00:54:34.319> step<00:54:34.589> so<00:54:34.740> if<00:54:34.799> you<00:54:34.859> know<00:54:34.950> anything 00:54:35.089 --> 00:54:35.099 align:start position:0% transform step so if you know anything 00:54:35.099 --> 00:54:36.940 align:start position:0% transform step so if you know anything about<00:54:35.220> the<00:54:35.520> way<00:54:35.609> compilers<00:54:36.089> work<00:54:36.299> you<00:54:36.450> have 00:54:36.940 --> 00:54:36.950 align:start position:0% about the way compilers work you have 00:54:36.950 --> 00:54:39.140 align:start position:0% about the way compilers work you have you<00:54:37.950> have<00:54:38.069> a<00:54:38.099> tokenized<00:54:38.490> step<00:54:38.760> and<00:54:38.940> you<00:54:39.000> have 00:54:39.140 --> 00:54:39.150 align:start position:0% you have a tokenized step and you have 00:54:39.150 --> 00:54:40.730 align:start position:0% you have a tokenized step and you have your<00:54:39.599> parsing<00:54:39.990> and<00:54:40.109> organizing<00:54:40.470> and<00:54:40.529> then<00:54:40.680> you 00:54:40.730 --> 00:54:40.740 align:start position:0% your parsing and organizing and then you 00:54:40.740 --> 00:54:42.980 align:start position:0% your parsing and organizing and then you have<00:54:40.890> a<00:54:41.190> compilation<00:54:41.640> step<00:54:41.940> and<00:54:42.210> then<00:54:42.299> so<00:54:42.839> in 00:54:42.980 --> 00:54:42.990 align:start position:0% have a compilation step and then so in 00:54:42.990 --> 00:54:45.200 align:start position:0% have a compilation step and then so in between<00:54:43.230> those<00:54:43.410> two<00:54:43.619> that<00:54:44.069> they<00:54:44.309> it<00:54:44.640> hands<00:54:45.059> us 00:54:45.200 --> 00:54:45.210 align:start position:0% between those two that they it hands us 00:54:45.210 --> 00:54:46.730 align:start position:0% between those two that they it hands us the<00:54:45.420> AST<00:54:45.809> which<00:54:45.990> is<00:54:46.109> the<00:54:46.200> abstract<00:54:46.589> syntax 00:54:46.730 --> 00:54:46.740 align:start position:0% the AST which is the abstract syntax 00:54:46.740 --> 00:54:48.559 align:start position:0% the AST which is the abstract syntax tree<00:54:47.220> and<00:54:47.430> we<00:54:47.819> can<00:54:47.849> kind<00:54:48.059> of<00:54:48.089> move<00:54:48.270> things 00:54:48.559 --> 00:54:48.569 align:start position:0% tree and we can kind of move things 00:54:48.569 --> 00:54:49.160 align:start position:0% tree and we can kind of move things around 00:54:49.160 --> 00:54:49.170 align:start position:0% around 00:54:49.170 --> 00:54:50.329 align:start position:0% around right<00:54:49.529> so<00:54:49.710> for<00:54:49.829> example<00:54:50.160> there<00:54:50.279> were 00:54:50.329 --> 00:54:50.339 align:start position:0% right so for example there were 00:54:50.339 --> 00:54:53.569 align:start position:0% right so for example there were decorators<00:54:50.849> like<00:54:51.059> that<00:54:51.210> at<00:54:51.890> UM<00:54:52.890> decorators<00:54:53.400> so 00:54:53.569 --> 00:54:53.579 align:start position:0% decorators like that at UM decorators so 00:54:53.579 --> 00:54:55.190 align:start position:0% decorators like that at UM decorators so in<00:54:53.700> the<00:54:53.789> transform<00:54:54.269> step<00:54:54.539> we<00:54:54.660> can<00:54:54.809> grab<00:54:55.019> that 00:54:55.190 --> 00:54:55.200 align:start position:0% in the transform step we can grab that 00:54:55.200 --> 00:54:58.759 align:start position:0% in the transform step we can grab that and<00:54:55.710> we<00:54:55.829> can<00:54:56.180> then<00:54:57.200> insert<00:54:58.200> things<00:54:58.500> like<00:54:58.680> the 00:54:58.759 --> 00:54:58.769 align:start position:0% and we can then insert things like the 00:54:58.769 --> 00:55:00.559 align:start position:0% and we can then insert things like the amid<00:54:59.010> code<00:54:59.190> that<00:54:59.549> we<00:54:59.670> need<00:54:59.700> into<00:55:00.089> the<00:55:00.180> tree<00:55:00.359> and 00:55:00.559 --> 00:55:00.569 align:start position:0% amid code that we need into the tree and 00:55:00.569 --> 00:55:01.700 align:start position:0% amid code that we need into the tree and then<00:55:00.750> that<00:55:00.839> gets<00:55:00.990> passed<00:55:01.200> back<00:55:01.319> to<00:55:01.470> the 00:55:01.700 --> 00:55:01.710 align:start position:0% then that gets passed back to the 00:55:01.710 --> 00:55:02.960 align:start position:0% then that gets passed back to the assembly<00:55:01.890> script<00:55:02.220> compiler<00:55:02.609> and<00:55:02.730> that<00:55:02.819> gets 00:55:02.960 --> 00:55:02.970 align:start position:0% assembly script compiler and that gets 00:55:02.970 --> 00:55:04.430 align:start position:0% assembly script compiler and that gets compiled<00:55:03.269> down<00:55:03.450> to<00:55:03.660> wozmak<00:55:03.990> code<00:55:04.109> so<00:55:04.260> that's 00:55:04.430 --> 00:55:04.440 align:start position:0% compiled down to wozmak code so that's 00:55:04.440 --> 00:55:05.779 align:start position:0% compiled down to wozmak code so that's just<00:55:04.500> a<00:55:04.619> high-level<00:55:04.950> overview<00:55:05.160> of<00:55:05.519> how<00:55:05.640> this 00:55:05.779 --> 00:55:05.789 align:start position:0% just a high-level overview of how this 00:55:05.789 --> 00:55:09.920 align:start position:0% just a high-level overview of how this works<00:55:06.049> so<00:55:07.640> that's<00:55:08.640> all<00:55:08.789> working<00:55:09.119> it's<00:55:09.779> just 00:55:09.920 --> 00:55:09.930 align:start position:0% works so that's all working it's just 00:55:09.930 --> 00:55:12.109 align:start position:0% works so that's all working it's just all<00:55:10.829> these<00:55:11.190> pieces<00:55:11.460> right<00:55:11.760> so<00:55:11.940> getting 00:55:12.109 --> 00:55:12.119 align:start position:0% all these pieces right so getting 00:55:12.119 --> 00:55:13.730 align:start position:0% all these pieces right so getting storage<00:55:12.569> working<00:55:13.019> getting<00:55:13.260> the<00:55:13.319> anit<00:55:13.559> code 00:55:13.730 --> 00:55:13.740 align:start position:0% storage working getting the anit code 00:55:13.740 --> 00:55:15.170 align:start position:0% storage working getting the anit code working<00:55:13.980> and<00:55:14.369> then<00:55:14.730> the<00:55:14.789> other<00:55:14.940> piece<00:55:15.150> that 00:55:15.170 --> 00:55:15.180 align:start position:0% working and then the other piece that 00:55:15.180 --> 00:55:17.539 align:start position:0% working and then the other piece that needs<00:55:15.510> to<00:55:15.599> be<00:55:15.660> done<00:55:15.839> is<00:55:16.109> hooking<00:55:16.829> into<00:55:17.010> tools 00:55:17.539 --> 00:55:17.549 align:start position:0% needs to be done is hooking into tools 00:55:17.549 --> 00:55:19.370 align:start position:0% needs to be done is hooking into tools like<00:55:17.880> embark<00:55:18.390> and<00:55:18.599> truffle<00:55:18.869> so<00:55:19.109> you<00:55:19.260> can 00:55:19.370 --> 00:55:19.380 align:start position:0% like embark and truffle so you can 00:55:19.380 --> 00:55:20.660 align:start position:0% like embark and truffle so you can easily<00:55:19.529> deploy<00:55:19.890> those<00:55:20.039> things<00:55:20.309> onto<00:55:20.579> the 00:55:20.660 --> 00:55:20.670 align:start position:0% easily deploy those things onto the 00:55:20.670 --> 00:55:22.430 align:start position:0% easily deploy those things onto the chain<00:55:20.849> so<00:55:21.569> I<00:55:21.599> would<00:55:21.900> say<00:55:22.019> the<00:55:22.140> work<00:55:22.260> is<00:55:22.319> about 00:55:22.430 --> 00:55:22.440 align:start position:0% chain so I would say the work is about 00:55:22.440 --> 00:55:24.140 align:start position:0% chain so I would say the work is about 50%<00:55:22.799> complete<00:55:23.369> there's<00:55:23.549> still<00:55:23.670> a<00:55:23.700> lot<00:55:23.880> to<00:55:24.029> do 00:55:24.140 --> 00:55:24.150 align:start position:0% 50% complete there's still a lot to do 00:55:24.150 --> 00:55:26.029 align:start position:0% 50% complete there's still a lot to do and<00:55:24.420> as<00:55:24.750> I<00:55:24.869> said<00:55:25.019> I've<00:55:25.140> been<00:55:25.260> doing<00:55:25.440> this<00:55:25.559> alone 00:55:26.029 --> 00:55:26.039 align:start position:0% and as I said I've been doing this alone 00:55:26.039 --> 00:55:27.559 align:start position:0% and as I said I've been doing this alone and<00:55:26.430> you<00:55:26.609> know<00:55:26.700> working<00:55:27.029> on<00:55:27.210> other<00:55:27.329> things<00:55:27.480> at 00:55:27.559 --> 00:55:27.569 align:start position:0% and you know working on other things at 00:55:27.569 --> 00:55:29.029 align:start position:0% and you know working on other things at the<00:55:27.630> same<00:55:27.779> time<00:55:28.019> so<00:55:28.289> if<00:55:28.440> anyone<00:55:28.799> in<00:55:28.920> this<00:55:28.980> room 00:55:29.029 --> 00:55:29.039 align:start position:0% the same time so if anyone in this room 00:55:29.039 --> 00:55:32.539 align:start position:0% the same time so if anyone in this room is<00:55:29.369> excited<00:55:29.940> about<00:55:30.240> this<00:55:30.890> yeah<00:55:31.890> so<00:55:32.099> just<00:55:32.309> check 00:55:32.539 --> 00:55:32.549 align:start position:0% is excited about this yeah so just check 00:55:32.549 --> 00:55:34.910 align:start position:0% is excited about this yeah so just check out<00:55:32.640> the<00:55:32.730> repository<00:55:33.210> it's<00:55:33.359> github.com<00:55:33.920> /e 00:55:34.910 --> 00:55:34.920 align:start position:0% out the repository it's github.com /e 00:55:34.920 --> 00:55:38.870 align:start position:0% out the repository it's github.com /e 30s<00:55:35.569> /e<00:55:36.569> woz<00:55:36.960> and<00:55:36.990> -<00:55:37.380> AAS<00:55:37.920> I'll<00:55:38.460> put<00:55:38.760> that<00:55:38.819> on 00:55:38.870 --> 00:55:38.880 align:start position:0% 30s /e woz and - AAS I'll put that on 00:55:38.880 --> 00:55:40.069 align:start position:0% 30s /e woz and - AAS I'll put that on the<00:55:39.000> screen<00:55:39.180> or<00:55:39.329> something<00:55:39.599> he<00:55:39.690> wasn't<00:55:39.869> - 00:55:40.069 --> 00:55:40.079 align:start position:0% the screen or something he wasn't - 00:55:40.079 --> 00:55:41.960 align:start position:0% the screen or something he wasn't - assembly<00:55:40.529> script<00:55:40.769> so<00:55:41.430> the<00:55:41.519> second<00:55:41.760> part<00:55:41.849> of 00:55:41.960 --> 00:55:41.970 align:start position:0% assembly script so the second part of 00:55:41.970 --> 00:55:43.700 align:start position:0% assembly script so the second part of your<00:55:42.059> question<00:55:42.180> which<00:55:42.599> is<00:55:42.779> kind<00:55:42.960> of<00:55:42.990> like<00:55:43.170> how 00:55:43.700 --> 00:55:43.710 align:start position:0% your question which is kind of like how 00:55:43.710 --> 00:55:45.140 align:start position:0% your question which is kind of like how far<00:55:43.980> are<00:55:44.099> we<00:55:44.160> away<00:55:44.220> from<00:55:44.400> being<00:55:44.910> able<00:55:45.000> to 00:55:45.140 --> 00:55:45.150 align:start position:0% far are we away from being able to 00:55:45.150 --> 00:55:47.000 align:start position:0% far are we away from being able to actually<00:55:45.359> write<00:55:45.750> contracts<00:55:46.289> actually<00:55:46.920> an 00:55:47.000 --> 00:55:47.010 align:start position:0% actually write contracts actually an 00:55:47.010 --> 00:55:48.500 align:start position:0% actually write contracts actually an assembly<00:55:47.369> script<00:55:47.640> and<00:55:47.789> actually<00:55:48.089> deploy<00:55:48.329> them 00:55:48.500 --> 00:55:48.510 align:start position:0% assembly script and actually deploy them 00:55:48.510 --> 00:55:51.079 align:start position:0% assembly script and actually deploy them on<00:55:48.599> the<00:55:48.690> main<00:55:48.839> that<00:55:49.549> that<00:55:50.549> basically<00:55:50.910> is<00:55:51.059> a 00:55:51.079 --> 00:55:51.089 align:start position:0% on the main that that basically is a 00:55:51.089 --> 00:55:52.700 align:start position:0% on the main that that basically is a question<00:55:51.420> about<00:55:51.510> the<00:55:51.630> e<00:55:51.750> azam<00:55:52.140> roadmap<00:55:52.650> I 00:55:52.700 --> 00:55:52.710 align:start position:0% question about the e azam roadmap I 00:55:52.710 --> 00:55:54.049 align:start position:0% question about the e azam roadmap I don't<00:55:52.859> know<00:55:52.920> you<00:55:53.099> touched<00:55:53.369> upon<00:55:53.490> this<00:55:53.700> Alex<00:55:53.970> do 00:55:54.049 --> 00:55:54.059 align:start position:0% don't know you touched upon this Alex do 00:55:54.059 --> 00:55:55.849 align:start position:0% don't know you touched upon this Alex do you<00:55:54.089> want<00:55:54.269> to<00:55:54.329> talk<00:55:54.569> about<00:55:54.599> how<00:55:55.380> this<00:55:55.529> might<00:55:55.589> go 00:55:55.849 --> 00:55:55.859 align:start position:0% you want to talk about how this might go 00:55:55.859 --> 00:55:59.329 align:start position:0% you want to talk about how this might go to<00:55:55.920> mean<00:55:56.069> that<00:55:57.740> yeah<00:55:58.740> I<00:55:58.769> don't<00:55:58.920> think<00:55:59.039> I<00:55:59.250> have 00:55:59.329 --> 00:55:59.339 align:start position:0% to mean that yeah I don't think I have 00:55:59.339 --> 00:56:02.059 align:start position:0% to mean that yeah I don't think I have much<00:55:59.880> more<00:55:59.910> to<00:56:00.119> say<00:56:00.359> to<00:56:00.420> that<00:56:00.799> when<00:56:01.799> it<00:56:01.920> goes<00:56:02.009> to 00:56:02.059 --> 00:56:02.069 align:start position:0% much more to say to that when it goes to 00:56:02.069 --> 00:56:04.490 align:start position:0% much more to say to that when it goes to domain<00:56:02.599> say<00:56:03.599> definitely<00:56:03.779> can<00:56:04.019> be<00:56:04.140> used<00:56:04.289> in<00:56:04.410> the 00:56:04.490 --> 00:56:04.500 align:start position:0% domain say definitely can be used in the 00:56:04.500 --> 00:56:07.220 align:start position:0% domain say definitely can be used in the test<00:56:04.710> net<00:56:04.890> and<00:56:05.660> they're<00:56:06.660> regarding<00:56:07.049> the<00:56:07.109> main 00:56:07.220 --> 00:56:07.230 align:start position:0% test net and they're regarding the main 00:56:07.230 --> 00:56:09.890 align:start position:0% test net and they're regarding the main ant<00:56:07.410> we<00:56:07.559> definitely<00:56:08.190> have<00:56:09.180> to<00:56:09.210> go<00:56:09.420> to<00:56:09.480> have<00:56:09.779> all 00:56:09.890 --> 00:56:09.900 align:start position:0% ant we definitely have to go to have all 00:56:09.900 --> 00:56:11.990 align:start position:0% ant we definitely have to go to have all of<00:56:10.019> this<00:56:10.109> in<00:56:10.259> the<00:56:10.319> main<00:56:10.440> net<00:56:10.619> but<00:56:11.430> that<00:56:11.670> that's 00:56:11.990 --> 00:56:12.000 align:start position:0% of this in the main net but that that's 00:56:12.000 --> 00:56:13.400 align:start position:0% of this in the main net but that that's gonna<00:56:12.240> take<00:56:12.450> a<00:56:12.480> while 00:56:13.400 --> 00:56:13.410 align:start position:0% gonna take a while 00:56:13.410 --> 00:56:15.920 align:start position:0% gonna take a while we<00:56:13.799> do<00:56:13.980> believe<00:56:14.250> that<00:56:14.369> we<00:56:14.849> can<00:56:15.240> accelerate 00:56:15.920 --> 00:56:15.930 align:start position:0% we do believe that we can accelerate 00:56:15.930 --> 00:56:18.289 align:start position:0% we do believe that we can accelerate that<00:56:16.259> process<00:56:16.500> by<00:56:16.920> first<00:56:17.549> proposing<00:56:18.029> just<00:56:18.059> a 00:56:18.289 --> 00:56:18.299 align:start position:0% that process by first proposing just a 00:56:18.299 --> 00:56:21.319 align:start position:0% that process by first proposing just a subset<00:56:18.720> of<00:56:19.349> he<00:56:19.769> wasn't<00:56:20.130> for<00:56:20.250> the<00:56:20.309> main<00:56:20.430> net<00:56:20.579> and 00:56:21.319 --> 00:56:21.329 align:start position:0% subset of he wasn't for the main net and 00:56:21.329 --> 00:56:23.720 align:start position:0% subset of he wasn't for the main net and that<00:56:21.450> would<00:56:21.630> be<00:56:21.720> only<00:56:21.839> for<00:56:21.930> pecan<00:56:22.319> pies<00:56:22.500> and<00:56:23.009> so 00:56:23.720 --> 00:56:23.730 align:start position:0% that would be only for pecan pies and so 00:56:23.730 --> 00:56:24.740 align:start position:0% that would be only for pecan pies and so that's<00:56:23.880> one<00:56:24.000> of<00:56:24.089> the<00:56:24.150> next<00:56:24.269> things<00:56:24.420> we're 00:56:24.740 --> 00:56:24.750 align:start position:0% that's one of the next things we're 00:56:24.750 --> 00:56:27.589 align:start position:0% that's one of the next things we're trying<00:56:24.900> to<00:56:25.400> to<00:56:26.400> discuss<00:56:26.759> with<00:56:27.180> other<00:56:27.329> teams 00:56:27.589 --> 00:56:27.599 align:start position:0% trying to to discuss with other teams 00:56:27.599 --> 00:56:29.900 align:start position:0% trying to to discuss with other teams how<00:56:28.289> we<00:56:28.349> could<00:56:28.559> do<00:56:28.650> that<00:56:28.680> have<00:56:29.549> you<00:56:29.609> brought<00:56:29.849> it 00:56:29.900 --> 00:56:29.910 align:start position:0% how we could do that have you brought it 00:56:29.910 --> 00:56:32.450 align:start position:0% how we could do that have you brought it up<00:56:30.269> on<00:56:30.630> one<00:56:30.990> of<00:56:31.019> those<00:56:31.200> awkward<00:56:31.500> F<00:56:31.799> calls<00:56:32.099> and 00:56:32.450 --> 00:56:32.460 align:start position:0% up on one of those awkward F calls and 00:56:32.460 --> 00:56:35.329 align:start position:0% up on one of those awkward F calls and and<00:56:32.759> there<00:56:33.450> was<00:56:33.539> a<00:56:33.569> good<00:56:33.720> reception<00:56:34.109> to<00:56:34.230> it<00:56:34.339> so 00:56:35.329 --> 00:56:35.339 align:start position:0% and there was a good reception to it so 00:56:35.339 --> 00:56:36.740 align:start position:0% and there was a good reception to it so I<00:56:35.369> think<00:56:35.490> we're<00:56:35.759> gonna<00:56:35.849> we<00:56:36.089> can<00:56:36.240> achieve<00:56:36.420> like 00:56:36.740 --> 00:56:36.750 align:start position:0% I think we're gonna we can achieve like 00:56:36.750 --> 00:56:38.720 align:start position:0% I think we're gonna we can achieve like pecan<00:56:37.019> pie<00:56:37.140> support<00:56:37.559> on<00:56:37.890> the<00:56:38.130> main<00:56:38.250> net<00:56:38.430> for 00:56:38.720 --> 00:56:38.730 align:start position:0% pecan pie support on the main net for 00:56:38.730 --> 00:56:41.480 align:start position:0% pecan pie support on the main net for was<00:56:38.880> in<00:56:39.059> next<00:56:39.329> year<00:56:39.539> sometime<00:56:39.930> perhaps<00:56:40.650> it 00:56:41.480 --> 00:56:41.490 align:start position:0% was in next year sometime perhaps it 00:56:41.490 --> 00:56:43.220 align:start position:0% was in next year sometime perhaps it also<00:56:41.640> depends<00:56:42.029> on<00:56:42.089> how<00:56:42.150> Constantinople<00:56:43.049> goes 00:56:43.220 --> 00:56:43.230 align:start position:0% also depends on how Constantinople goes 00:56:43.230 --> 00:56:46.970 align:start position:0% also depends on how Constantinople goes right<00:56:43.940> that's<00:56:44.940> a<00:56:45.029> big<00:56:45.180> question<00:56:45.410> and<00:56:46.410> after 00:56:46.970 --> 00:56:46.980 align:start position:0% right that's a big question and after 00:56:46.980 --> 00:56:49.460 align:start position:0% right that's a big question and after that<00:56:47.329> hopefully<00:56:48.329> you<00:56:48.599> can<00:56:48.750> expand<00:56:49.109> into<00:56:49.380> you 00:56:49.460 --> 00:56:49.470 align:start position:0% that hopefully you can expand into you 00:56:49.470 --> 00:56:52.430 align:start position:0% that hopefully you can expand into you fullfil<00:56:50.099> may<00:56:50.279> not<00:56:50.460> support<00:56:51.109> but<00:56:52.109> you<00:56:52.200> guys<00:56:52.289> can 00:56:52.430 --> 00:56:52.440 align:start position:0% fullfil may not support but you guys can 00:56:52.440 --> 00:56:54.680 align:start position:0% fullfil may not support but you guys can really<00:56:52.589> try<00:56:52.769> doing<00:56:52.980> a<00:56:53.039> test<00:56:53.220> net<00:56:53.400> and<00:56:53.730> that's 00:56:54.680 --> 00:56:54.690 align:start position:0% really try doing a test net and that's 00:56:54.690 --> 00:56:56.720 align:start position:0% really try doing a test net and that's what<00:56:54.869> matters<00:56:55.170> right<00:56:55.230> now<00:56:55.400> and<00:56:56.400> we<00:56:56.549> have<00:56:56.700> been 00:56:56.720 --> 00:56:56.730 align:start position:0% what matters right now and we have been 00:56:56.730 --> 00:56:58.430 align:start position:0% what matters right now and we have been closely<00:56:57.450> in<00:56:57.539> touch<00:56:57.660> with<00:56:57.809> other<00:56:57.960> projects 00:56:58.430 --> 00:56:58.440 align:start position:0% closely in touch with other projects 00:56:58.440 --> 00:57:02.070 align:start position:0% closely in touch with other projects including<00:56:58.740> parody<00:56:59.579> polka<00:57:00.089> dot 00:57:02.070 --> 00:57:02.080 align:start position:0% including parody polka dot 00:57:02.080 --> 00:57:04.990 align:start position:0% including parody polka dot it<00:57:03.080> space<00:57:04.040> meshes<00:57:04.340> another<00:57:04.580> example<00:57:04.880> of<00:57:04.940> a 00:57:04.990 --> 00:57:05.000 align:start position:0% it space meshes another example of a 00:57:05.000 --> 00:57:06.390 align:start position:0% it space meshes another example of a project<00:57:05.150> that's<00:57:05.450> really<00:57:05.570> excited<00:57:06.050> about 00:57:06.390 --> 00:57:06.400 align:start position:0% project that's really excited about 00:57:06.400 --> 00:57:08.980 align:start position:0% project that's really excited about about<00:57:07.400> us<00:57:07.760> and<00:57:07.940> about<00:57:08.210> things<00:57:08.510> like<00:57:08.600> assembly 00:57:08.980 --> 00:57:08.990 align:start position:0% about us and about things like assembly 00:57:08.990 --> 00:57:11.380 align:start position:0% about us and about things like assembly script<00:57:09.260> so<00:57:09.740> I<00:57:10.130> mean<00:57:10.460> none<00:57:10.640> of<00:57:10.760> these<00:57:10.910> are<00:57:11.210> like 00:57:11.380 --> 00:57:11.390 align:start position:0% script so I mean none of these are like 00:57:11.390 --> 00:57:12.910 align:start position:0% script so I mean none of these are like in<00:57:11.570> production<00:57:11.960> yet<00:57:12.110> but<00:57:12.380> the<00:57:12.530> code<00:57:12.680> that<00:57:12.800> you 00:57:12.910 --> 00:57:12.920 align:start position:0% in production yet but the code that you 00:57:12.920 --> 00:57:14.170 align:start position:0% in production yet but the code that you write<00:57:12.950> now<00:57:13.130> and<00:57:13.490> the<00:57:13.550> things<00:57:13.700> you<00:57:13.850> learn<00:57:14.000> now 00:57:14.170 --> 00:57:14.180 align:start position:0% write now and the things you learn now 00:57:14.180 --> 00:57:16.510 align:start position:0% write now and the things you learn now will<00:57:14.390> apply<00:57:14.660> actually<00:57:15.230> across<00:57:15.710> like<00:57:16.010> a<00:57:16.040> whole 00:57:16.510 --> 00:57:16.520 align:start position:0% will apply actually across like a whole 00:57:16.520 --> 00:57:19.660 align:start position:0% will apply actually across like a whole host<00:57:16.700> of<00:57:16.880> different<00:57:17.030> chains<00:57:17.480> in<00:57:17.600> the<00:57:17.660> future 00:57:19.660 --> 00:57:19.670 align:start position:0% host of different chains in the future 00:57:19.670 --> 00:57:21.910 align:start position:0% host of different chains in the future yeah<00:57:20.120> I<00:57:20.150> guess<00:57:20.300> for<00:57:20.480> one<00:57:20.720> more<00:57:20.870> question<00:57:21.110> you 00:57:21.910 --> 00:57:21.920 align:start position:0% yeah I guess for one more question you 00:57:21.920 --> 00:57:25.080 align:start position:0% yeah I guess for one more question you know<00:57:21.980> what<00:57:22.330> what<00:57:23.330> would<00:57:23.480> it<00:57:23.660> take<00:57:23.990> to<00:57:24.320> get<00:57:24.590> past 00:57:25.080 --> 00:57:25.090 align:start position:0% know what what would it take to get past 00:57:25.090 --> 00:57:29.890 align:start position:0% know what what would it take to get past maybe<00:57:26.090> a<00:57:26.330> year<00:57:26.810> a<00:57:26.840> while<00:57:27.440> awhile<00:57:27.890> to<00:57:28.850> an<00:57:29.210> actual 00:57:29.890 --> 00:57:29.900 align:start position:0% maybe a year a while awhile to an actual 00:57:29.900 --> 00:57:34.960 align:start position:0% maybe a year a while awhile to an actual schedule<00:57:31.810> allocated<00:57:32.810> resources<00:57:33.070> a<00:57:34.070> series<00:57:34.760> of 00:57:34.960 --> 00:57:34.970 align:start position:0% schedule allocated resources a series of 00:57:34.970 --> 00:57:37.600 align:start position:0% schedule allocated resources a series of tasks<00:57:35.570> the<00:57:35.990> kind<00:57:36.290> of<00:57:36.500> thing<00:57:36.770> I<00:57:36.980> would<00:57:37.130> expect 00:57:37.600 --> 00:57:37.610 align:start position:0% tasks the kind of thing I would expect 00:57:37.610 --> 00:57:41.740 align:start position:0% tasks the kind of thing I would expect to<00:57:37.760> see<00:57:37.990> in<00:57:38.990> a<00:57:39.170> real<00:57:39.410> engineering<00:57:40.160> project<00:57:41.030> so 00:57:41.740 --> 00:57:41.750 align:start position:0% to see in a real engineering project so 00:57:41.750 --> 00:57:44.770 align:start position:0% to see in a real engineering project so that<00:57:42.080> other<00:57:42.320> engineering<00:57:43.190> projects<00:57:43.880> can<00:57:44.450> plan 00:57:44.770 --> 00:57:44.780 align:start position:0% that other engineering projects can plan 00:57:44.780 --> 00:57:47.740 align:start position:0% that other engineering projects can plan their<00:57:45.110> work<00:57:45.440> and<00:57:45.800> have<00:57:46.460> some<00:57:47.330> degree<00:57:47.540> of 00:57:47.740 --> 00:57:47.750 align:start position:0% their work and have some degree of 00:57:47.750 --> 00:57:50.520 align:start position:0% their work and have some degree of confidence<00:57:48.140> that<00:57:48.770> if<00:57:49.070> they<00:57:49.100> spend<00:57:49.730> their 00:57:50.520 --> 00:57:50.530 align:start position:0% confidence that if they spend their 00:57:50.530 --> 00:57:53.140 align:start position:0% confidence that if they spend their thousands<00:57:51.530> hundreds<00:57:52.100> of<00:57:52.220> thousands<00:57:52.880> millions 00:57:53.140 --> 00:57:53.150 align:start position:0% thousands hundreds of thousands millions 00:57:53.150 --> 00:57:56.410 align:start position:0% thousands hundreds of thousands millions of<00:57:53.600> dollars<00:57:54.190> that<00:57:55.190> they<00:57:55.340> won't<00:57:55.580> find<00:57:55.850> out<00:57:56.120> that 00:57:56.410 --> 00:57:56.420 align:start position:0% of dollars that they won't find out that 00:57:56.420 --> 00:58:00.940 align:start position:0% of dollars that they won't find out that oh<00:57:56.600> no<00:57:57.410> not<00:57:57.920> this<00:57:58.190> year<00:57:58.250> next<00:57:59.030> year<00:57:59.510> oh<00:57:59.660> no<00:58:00.410> not 00:58:00.940 --> 00:58:00.950 align:start position:0% oh no not this year next year oh no not 00:58:00.950 --> 00:58:05.050 align:start position:0% oh no not this year next year oh no not next<00:58:01.310> year<00:58:01.520> the<00:58:02.060> year<00:58:02.090> after<00:58:02.480> that<00:58:03.940> you<00:58:04.940> know 00:58:05.050 --> 00:58:05.060 align:start position:0% next year the year after that you know 00:58:05.060 --> 00:58:06.670 align:start position:0% next year the year after that you know what<00:58:05.390> would<00:58:05.540> it<00:58:05.570> take<00:58:05.870> to<00:58:06.110> get<00:58:06.260> a<00:58:06.320> much<00:58:06.650> higher 00:58:06.670 --> 00:58:06.680 align:start position:0% what would it take to get a much higher 00:58:06.680 --> 00:58:09.820 align:start position:0% what would it take to get a much higher level<00:58:07.340> of<00:58:07.640> confidence<00:58:08.420> in<00:58:08.810> your<00:58:09.110> scheduling 00:58:09.820 --> 00:58:09.830 align:start position:0% level of confidence in your scheduling 00:58:09.830 --> 00:58:12.640 align:start position:0% level of confidence in your scheduling rather<00:58:10.430> than<00:58:10.820> what<00:58:11.060> appears<00:58:11.180> to<00:58:11.540> be<00:58:11.750> guess 00:58:12.640 --> 00:58:12.650 align:start position:0% rather than what appears to be guess 00:58:12.650 --> 00:58:15.910 align:start position:0% rather than what appears to be guess what<00:58:13.990> you're<00:58:14.990> asking<00:58:15.350> a<00:58:15.560> question<00:58:15.890> about 00:58:15.910 --> 00:58:15.920 align:start position:0% what you're asking a question about 00:58:15.920 --> 00:58:19.420 align:start position:0% what you're asking a question about confidence<00:58:16.610> yeah<00:58:17.390> how<00:58:18.110> can<00:58:18.170> we<00:58:18.380> get<00:58:18.830> more<00:58:19.130> than 00:58:19.420 --> 00:58:19.430 align:start position:0% confidence yeah how can we get more than 00:58:19.430 --> 00:58:21.880 align:start position:0% confidence yeah how can we get more than here's<00:58:20.060> a<00:58:20.180> road<00:58:20.480> map<00:58:20.810> but<00:58:20.840> maybe<00:58:21.410> we'll<00:58:21.740> get 00:58:21.880 --> 00:58:21.890 align:start position:0% here's a road map but maybe we'll get 00:58:21.890 --> 00:58:25.120 align:start position:0% here's a road map but maybe we'll get there<00:58:22.160> someday<00:58:22.960> versus<00:58:23.960> here's<00:58:24.620> a<00:58:24.710> schedule 00:58:25.120 --> 00:58:25.130 align:start position:0% there someday versus here's a schedule 00:58:25.130 --> 00:58:28.150 align:start position:0% there someday versus here's a schedule and<00:58:25.610> assigned<00:58:25.970> resources<00:58:26.900> and<00:58:27.410> a<00:58:27.500> fairly<00:58:27.950> high 00:58:28.150 --> 00:58:28.160 align:start position:0% and assigned resources and a fairly high 00:58:28.160 --> 00:58:30.760 align:start position:0% and assigned resources and a fairly high degree<00:58:28.190> of<00:58:28.640> confidence<00:58:29.420> that<00:58:29.840> we<00:58:30.290> will<00:58:30.500> get<00:58:30.710> to 00:58:30.760 --> 00:58:30.770 align:start position:0% degree of confidence that we will get to 00:58:30.770 --> 00:58:32.650 align:start position:0% degree of confidence that we will get to certain<00:58:31.340> stages 00:58:32.650 --> 00:58:32.660 align:start position:0% certain stages 00:58:32.660 --> 00:58:33.850 align:start position:0% certain stages we're<00:58:32.810> not<00:58:32.930> business<00:58:33.320> people<00:58:33.530> we're 00:58:33.850 --> 00:58:33.860 align:start position:0% we're not business people we're 00:58:33.860 --> 00:58:36.430 align:start position:0% we're not business people we're engineers<00:58:34.310> we're<00:58:34.700> developers<00:58:35.210> we<00:58:36.050> you<00:58:36.320> know 00:58:36.430 --> 00:58:36.440 align:start position:0% engineers we're developers we you know 00:58:36.440 --> 00:58:37.960 align:start position:0% engineers we're developers we you know to<00:58:36.500> define<00:58:36.860> what<00:58:37.100> confidence<00:58:37.550> means<00:58:37.730> you<00:58:37.880> have 00:58:37.960 --> 00:58:37.970 align:start position:0% to define what confidence means you have 00:58:37.970 --> 00:58:39.880 align:start position:0% to define what confidence means you have to<00:58:38.030> define<00:58:38.270> what<00:58:38.450> a<00:58:38.480> human<00:58:38.750> being<00:58:38.960> is<00:58:39.140> and<00:58:39.380> how 00:58:39.880 --> 00:58:39.890 align:start position:0% to define what a human being is and how 00:58:39.890 --> 00:58:41.650 align:start position:0% to define what a human being is and how human<00:58:40.190> beings<00:58:40.700> interact<00:58:41.000> with<00:58:41.360> each<00:58:41.480> other 00:58:41.650 --> 00:58:41.660 align:start position:0% human beings interact with each other 00:58:41.660 --> 00:58:42.820 align:start position:0% human beings interact with each other and<00:58:41.900> I<00:58:41.960> don't<00:58:42.110> even<00:58:42.200> know<00:58:42.380> what<00:58:42.530> that<00:58:42.650> means 00:58:42.820 --> 00:58:42.830 align:start position:0% and I don't even know what that means 00:58:42.830 --> 00:58:44.560 align:start position:0% and I don't even know what that means I'm<00:58:42.950> just<00:58:42.980> a<00:58:43.190> developer<00:58:43.700> I<00:58:43.730> don't<00:58:43.970> know<00:58:44.060> well 00:58:44.560 --> 00:58:44.570 align:start position:0% I'm just a developer I don't know well 00:58:44.570 --> 00:58:46.600 align:start position:0% I'm just a developer I don't know well then<00:58:44.780> it<00:58:44.870> bears<00:58:45.080> where<00:58:45.740> are<00:58:45.950> the<00:58:46.100> managers 00:58:46.600 --> 00:58:46.610 align:start position:0% then it bears where are the managers 00:58:46.610 --> 00:58:48.810 align:start position:0% then it bears where are the managers okay 00:58:48.810 --> 00:58:48.820 align:start position:0% okay 00:58:48.820 --> 00:58:53.060 align:start position:0% okay sorry<00:58:49.820> Alex<00:58:50.030> go<00:58:50.270> ahead<00:58:50.420> I've<00:58:50.570> spent<00:58:50.870> years 00:58:53.060 --> 00:58:53.070 align:start position:0% 00:58:53.070 --> 00:58:54.710 align:start position:0% it's<00:58:53.190> kind<00:58:53.370> of<00:58:53.400> a<00:58:53.520> question<00:58:53.760> partially<00:58:54.540> for 00:58:54.710 --> 00:58:54.720 align:start position:0% it's kind of a question partially for 00:58:54.720 --> 00:58:57.260 align:start position:0% it's kind of a question partially for the<00:58:54.780> foundation<00:58:55.380> and<00:58:55.560> not<00:58:56.400> only<00:58:56.550> a<00:58:56.670> foundation 00:58:57.260 --> 00:58:57.270 align:start position:0% the foundation and not only a foundation 00:58:57.270 --> 00:59:03.050 align:start position:0% the foundation and not only a foundation but<00:59:00.410> okay<00:59:01.410> I<00:59:01.440> do<00:59:01.770> think<00:59:02.040> we<00:59:02.130> have<00:59:02.160> we<00:59:02.790> have<00:59:02.880> some 00:59:03.050 --> 00:59:03.060 align:start position:0% but okay I do think we have we have some 00:59:03.060 --> 00:59:05.030 align:start position:0% but okay I do think we have we have some kind<00:59:03.210> of<00:59:03.270> answers<00:59:04.170> to<00:59:04.290> this<00:59:04.380> question<00:59:04.770> and<00:59:04.920> I'm 00:59:05.030 --> 00:59:05.040 align:start position:0% kind of answers to this question and I'm 00:59:05.040 --> 00:59:07.250 align:start position:0% kind of answers to this question and I'm glad<00:59:05.220> you<00:59:05.340> asked<00:59:05.490> this<00:59:05.610> question<00:59:06.050> so<00:59:07.050> in<00:59:07.170> the 00:59:07.250 --> 00:59:07.260 align:start position:0% glad you asked this question so in the 00:59:07.260 --> 00:59:10.100 align:start position:0% glad you asked this question so in the awasum<00:59:07.620> team<00:59:07.800> itself<00:59:08.190> video<00:59:08.900> started<00:59:09.900> to<00:59:09.960> use 00:59:10.100 --> 00:59:10.110 align:start position:0% awasum team itself video started to use 00:59:10.110 --> 00:59:11.990 align:start position:0% awasum team itself video started to use in<00:59:10.230> the<00:59:10.290> last<00:59:10.380> couple<00:59:10.620> of<00:59:10.650> months<00:59:10.800> the<00:59:11.580> project 00:59:11.990 --> 00:59:12.000 align:start position:0% in the last couple of months the project 00:59:12.000 --> 00:59:14.150 align:start position:0% in the last couple of months the project boards<00:59:12.270> and<00:59:12.390> github<00:59:12.570> and<00:59:12.990> set<00:59:13.620> up<00:59:13.740> projects 00:59:14.150 --> 00:59:14.160 align:start position:0% boards and github and set up projects 00:59:14.160 --> 00:59:16.370 align:start position:0% boards and github and set up projects and<00:59:14.310> goals<00:59:14.460> and<00:59:14.730> deadlines<00:59:15.090> for<00:59:15.270> those<00:59:15.420> and<00:59:16.230> we 00:59:16.370 --> 00:59:16.380 align:start position:0% and goals and deadlines for those and we 00:59:16.380 --> 00:59:18.590 align:start position:0% and goals and deadlines for those and we do<00:59:16.500> have<00:59:16.650> all<00:59:16.770> of<00:59:16.890> that<00:59:16.920> mapped<00:59:17.280> out<00:59:17.550> for<00:59:17.940> the 00:59:18.590 --> 00:59:18.600 align:start position:0% do have all of that mapped out for the 00:59:18.600 --> 00:59:20.210 align:start position:0% do have all of that mapped out for the tiny<00:59:18.990> tools<00:59:19.230> we<00:59:19.380> have<00:59:19.530> for<00:59:19.710> example<00:59:19.740> Hera 00:59:20.210 --> 00:59:20.220 align:start position:0% tiny tools we have for example Hera 00:59:20.220 --> 00:59:21.860 align:start position:0% tiny tools we have for example Hera which<00:59:20.430> pavel<00:59:20.730> has<00:59:20.820> mentioned<00:59:21.030> we<00:59:21.300> have<00:59:21.480> a<00:59:21.660> road 00:59:21.860 --> 00:59:21.870 align:start position:0% which pavel has mentioned we have a road 00:59:21.870 --> 00:59:23.780 align:start position:0% which pavel has mentioned we have a road map<00:59:21.900> when<00:59:22.710> which<00:59:22.920> version<00:59:23.370> with<00:59:23.610> what 00:59:23.780 --> 00:59:23.790 align:start position:0% map when which version with what 00:59:23.790 --> 00:59:27.110 align:start position:0% map when which version with what features<00:59:24.150> said<00:59:24.360> it<00:59:24.480> gonna<00:59:24.630> be<00:59:25.260> released<00:59:26.090> so<00:59:27.090> I 00:59:27.110 --> 00:59:27.120 align:start position:0% features said it gonna be released so I 00:59:27.120 --> 00:59:28.850 align:start position:0% features said it gonna be released so I think<00:59:27.750> we're<00:59:27.870> really<00:59:27.990> improving<00:59:28.470> and<00:59:28.680> they 00:59:28.850 --> 00:59:28.860 align:start position:0% think we're really improving and they 00:59:28.860 --> 00:59:30.410 align:start position:0% think we're really improving and they wasn't<00:59:29.040> project<00:59:29.430> itself<00:59:29.670> to<00:59:29.880> have<00:59:30.030> a<00:59:30.060> proper 00:59:30.410 --> 00:59:30.420 align:start position:0% wasn't project itself to have a proper 00:59:30.420 --> 00:59:33.110 align:start position:0% wasn't project itself to have a proper road<00:59:30.600> map<00:59:30.840> and<00:59:31.140> and<00:59:31.380> and<00:59:31.620> plans<00:59:31.890> for<00:59:32.190> those<00:59:32.280> but 00:59:33.110 --> 00:59:33.120 align:start position:0% road map and and and plans for those but 00:59:33.120 --> 00:59:34.580 align:start position:0% road map and and and plans for those but the<00:59:33.180> bigger<00:59:33.360> question<00:59:33.720> is<00:59:33.810> really<00:59:33.960> how<00:59:34.080> we<00:59:34.350> can 00:59:34.580 --> 00:59:34.590 align:start position:0% the bigger question is really how we can 00:59:34.590 --> 00:59:36.950 align:start position:0% the bigger question is really how we can apply<00:59:34.740> all<00:59:34.830> of<00:59:35.070> this<00:59:35.250> to<00:59:35.310> the<00:59:35.580> main<00:59:35.610> net<00:59:35.960> and 00:59:36.950 --> 00:59:36.960 align:start position:0% apply all of this to the main net and 00:59:36.960 --> 00:59:39.100 align:start position:0% apply all of this to the main net and the<00:59:37.560> good<00:59:37.710> news<00:59:37.890> I<00:59:38.040> think<00:59:38.100> is<00:59:38.460> that<00:59:38.520> there 00:59:39.100 --> 00:59:39.110 align:start position:0% the good news I think is that there 00:59:39.110 --> 00:59:41.630 align:start position:0% the good news I think is that there recently<00:59:40.110> there<00:59:40.260> have<00:59:40.440> been<00:59:40.470> a<00:59:40.950> lot<00:59:41.310> of<00:59:41.430> good 00:59:41.630 --> 00:59:41.640 align:start position:0% recently there have been a lot of good 00:59:41.640 --> 00:59:43.490 align:start position:0% recently there have been a lot of good discussions<00:59:42.150> between<00:59:42.360> all<00:59:43.320> the<00:59:43.470> different 00:59:43.490 --> 00:59:43.500 align:start position:0% discussions between all the different 00:59:43.500 --> 00:59:45.230 align:start position:0% discussions between all the different teams<00:59:43.980> involved<00:59:44.490> with<00:59:44.610> writing<00:59:44.820> main<00:59:45.090> net 00:59:45.230 --> 00:59:45.240 align:start position:0% teams involved with writing main net 00:59:45.240 --> 00:59:47.240 align:start position:0% teams involved with writing main net clients<00:59:45.720> and<00:59:46.440> it<00:59:46.560> seems<00:59:46.740> like<00:59:46.980> all<00:59:47.100> these 00:59:47.240 --> 00:59:47.250 align:start position:0% clients and it seems like all these 00:59:47.250 --> 00:59:49.400 align:start position:0% clients and it seems like all these teams<00:59:47.490> are<00:59:47.610> interested<00:59:48.090> in<00:59:48.210> improving<00:59:49.140> the 00:59:49.400 --> 00:59:49.410 align:start position:0% teams are interested in improving the 00:59:49.410 --> 00:59:50.930 align:start position:0% teams are interested in improving the process<00:59:49.800> the<00:59:49.950> non<00:59:50.100> existing<00:59:50.550> processes 00:59:50.930 --> 00:59:50.940 align:start position:0% process the non existing processes 00:59:50.940 --> 00:59:53.690 align:start position:0% process the non existing processes putting<00:59:51.510> something<00:59:51.780> in<00:59:52.020> place<00:59:52.170> of<00:59:52.350> that<00:59:52.700> so 00:59:53.690 --> 00:59:53.700 align:start position:0% putting something in place of that so 00:59:53.700 --> 00:59:56.360 align:start position:0% putting something in place of that so I'm<00:59:53.790> kind<00:59:54.300> of<00:59:54.890> hopeful<00:59:55.890> that<00:59:56.010> this<00:59:56.220> gonna 00:59:56.360 --> 00:59:56.370 align:start position:0% I'm kind of hopeful that this gonna 00:59:56.370 --> 00:59:59.330 align:start position:0% I'm kind of hopeful that this gonna happen<00:59:56.520> very<00:59:56.790> soon<00:59:57.800> the<00:59:58.800> first<00:59:59.010> step<00:59:59.160> has<00:59:59.280> been 00:59:59.330 --> 00:59:59.340 align:start position:0% happen very soon the first step has been 00:59:59.340 --> 01:00:00.890 align:start position:0% happen very soon the first step has been made<00:59:59.610> all<00:59:59.790> these<00:59:59.880> teams<01:00:00.150> started<01:00:00.810> to 01:00:00.890 --> 01:00:00.900 align:start position:0% made all these teams started to 01:00:00.900 --> 01:00:02.570 align:start position:0% made all these teams started to communicate<01:00:01.320> to<01:00:01.440> each<01:00:01.470> other<01:00:01.740> and<01:00:01.980> realize 01:00:02.570 --> 01:00:02.580 align:start position:0% communicate to each other and realize 01:00:02.580 --> 01:00:04.430 align:start position:0% communicate to each other and realize that<01:00:02.910> there<01:00:03.090> is<01:00:03.120> an<01:00:03.450> issue<01:00:03.540> which<01:00:04.110> has<01:00:04.290> to<01:00:04.410> be 01:00:04.430 --> 01:00:04.440 align:start position:0% that there is an issue which has to be 01:00:04.440 --> 01:00:06.410 align:start position:0% that there is an issue which has to be fixed<01:00:04.710> so<01:00:05.010> I<01:00:05.730> think<01:00:06.000> it's<01:00:06.120> gonna<01:00:06.240> become 01:00:06.410 --> 01:00:06.420 align:start position:0% fixed so I think it's gonna become 01:00:06.420 --> 01:00:10.730 align:start position:0% fixed so I think it's gonna become better<01:00:08.270> thanks<01:00:09.270> Greg<01:00:09.450> I<01:00:09.690> think<01:00:10.230> are<01:00:10.440> we<01:00:10.560> out<01:00:10.710> of 01:00:10.730 --> 01:00:10.740 align:start position:0% better thanks Greg I think are we out of 01:00:10.740 --> 01:00:12.350 align:start position:0% better thanks Greg I think are we out of time<01:00:10.860> for<01:00:11.040> questions<01:00:11.120> yeah<01:00:12.120> I<01:00:12.150> mean<01:00:12.270> the 01:00:12.350 --> 01:00:12.360 align:start position:0% time for questions yeah I mean the 01:00:12.360 --> 01:00:14.180 align:start position:0% time for questions yeah I mean the question<01:00:12.630> is<01:00:12.720> already<01:00:13.020> guys<01:00:13.170> tired<01:00:13.560> do<01:00:14.130> you 01:00:14.180 --> 01:00:14.190 align:start position:0% question is already guys tired do you 01:00:14.190 --> 01:00:15.710 align:start position:0% question is already guys tired do you want<01:00:14.340> to<01:00:14.400> take<01:00:14.520> a<01:00:14.550> break<01:00:14.790> what<01:00:15.480> do<01:00:15.540> you<01:00:15.600> wanna 01:00:15.710 --> 01:00:15.720 align:start position:0% want to take a break what do you wanna 01:00:15.720 --> 01:00:17.480 align:start position:0% want to take a break what do you wanna make<01:00:15.840> questions<01:00:16.040> because<01:00:17.040> we<01:00:17.190> still<01:00:17.340> have 01:00:17.480 --> 01:00:17.490 align:start position:0% make questions because we still have 01:00:17.490 --> 01:00:20.240 align:start position:0% make questions because we still have like<01:00:17.640> another<01:00:17.880> hour<01:00:18.120> to<01:00:18.420> to<01:00:18.930> go<01:00:19.140> and<01:00:19.350> give<01:00:20.130> them 01:00:20.240 --> 01:00:20.250 align:start position:0% like another hour to to go and give them 01:00:20.250 --> 01:00:21.530 align:start position:0% like another hour to to go and give them a<01:00:20.340> glimpse<01:00:20.820> of<01:00:20.910> what's<01:00:21.090> coming<01:00:21.240> up<01:00:21.360> in<01:00:21.480> the 01:00:21.530 --> 01:00:21.540 align:start position:0% a glimpse of what's coming up in the 01:00:21.540 --> 01:00:23.480 align:start position:0% a glimpse of what's coming up in the next<01:00:21.600> episodes<01:00:22.050> or<01:00:22.140> topics<01:00:22.470> I<01:00:22.680> think<01:00:23.160> roughly 01:00:23.480 --> 01:00:23.490 align:start position:0% next episodes or topics I think roughly 01:00:23.490 --> 01:00:25.460 align:start position:0% next episodes or topics I think roughly we<01:00:23.700> have<01:00:23.790> like<01:00:23.910> 40<01:00:24.360> minutes<01:00:24.570> of<01:00:24.810> content<01:00:25.200> left 01:00:25.460 --> 01:00:25.470 align:start position:0% we have like 40 minutes of content left 01:00:25.470 --> 01:00:28.370 align:start position:0% we have like 40 minutes of content left and<01:00:26.330> we<01:00:27.330> gonna<01:00:27.450> start<01:00:27.750> which<01:00:27.990> is<01:00:28.140> the<01:00:28.230> bottom 01:00:28.370 --> 01:00:28.380 align:start position:0% and we gonna start which is the bottom 01:00:28.380 --> 01:00:30.260 align:start position:0% and we gonna start which is the bottom engines<01:00:28.770> is<01:00:28.890> the<01:00:28.920> first<01:00:29.160> right<01:00:29.340> yeah<01:00:30.120> there 01:00:30.260 --> 01:00:30.270 align:start position:0% engines is the first right yeah there 01:00:30.270 --> 01:00:32.300 align:start position:0% engines is the first right yeah there was<01:00:30.420> a<01:00:30.450> man<01:00:30.660> gene<01:00:30.840> so<01:00:31.050> so<01:00:31.380> Paul<01:00:31.560> gonna<01:00:31.710> deep 01:00:32.300 --> 01:00:32.310 align:start position:0% was a man gene so so Paul gonna deep 01:00:32.310 --> 01:00:34.340 align:start position:0% was a man gene so so Paul gonna deep dive<01:00:32.550> into<01:00:32.790> how<01:00:33.240> Azam<01:00:33.600> actually<01:00:33.960> works<01:00:34.140> and 01:00:34.340 --> 01:00:34.350 align:start position:0% dive into how Azam actually works and 01:00:34.350 --> 01:00:36.770 align:start position:0% dive into how Azam actually works and how<01:00:34.530> what<01:00:35.100> some<01:00:35.220> engines<01:00:35.610> work<01:00:35.880> that's<01:00:36.570> super 01:00:36.770 --> 01:00:36.780 align:start position:0% how what some engines work that's super 01:00:36.780 --> 01:00:41.840 align:start position:0% how what some engines work that's super exciting<01:00:37.280> then<01:00:38.280> we<01:00:38.460> have<01:00:38.730> -<01:00:40.370> which<01:00:41.370> ins<01:00:41.580> and 01:00:41.840 --> 01:00:41.850 align:start position:0% exciting then we have - which ins and 01:00:41.850 --> 01:00:43.460 align:start position:0% exciting then we have - which ins and how<01:00:42.030> we<01:00:42.090> could<01:00:42.360> well<01:00:42.630> actually<01:00:42.750> tree<01:00:43.080> visions 01:00:43.460 --> 01:00:43.470 align:start position:0% how we could well actually tree visions 01:00:43.470 --> 01:00:45.920 align:start position:0% how we could well actually tree visions the<01:00:43.770> first<01:00:44.010> vision<01:00:44.280> is<01:00:44.580> called<01:00:45.270> tool<01:00:45.480> Bo<01:00:45.660> II 01:00:45.920 --> 01:00:45.930 align:start position:0% the first vision is called tool Bo II 01:00:45.930 --> 01:00:48.920 align:start position:0% the first vision is called tool Bo II wasum<01:00:46.650> which<01:00:47.240> explores<01:00:48.240> ideas<01:00:48.600> how<01:00:48.780> we<01:00:48.840> could 01:00:48.920 --> 01:00:48.930 align:start position:0% wasum which explores ideas how we could 01:00:48.930 --> 01:00:51.260 align:start position:0% wasum which explores ideas how we could speed<01:00:49.290> up<01:00:49.520> transaction<01:00:50.520> processing<01:00:50.970> speed 01:00:51.260 --> 01:00:51.270 align:start position:0% speed up transaction processing speed 01:00:51.270 --> 01:00:53.600 align:start position:0% speed up transaction processing speed and<01:00:51.540> increase<01:00:52.380> the<01:00:52.590> throughput<01:00:52.800> which 01:00:53.600 --> 01:00:53.610 align:start position:0% and increase the throughput which 01:00:53.610 --> 01:00:55.040 align:start position:0% and increase the throughput which applies<01:00:53.880> to<01:00:53.910> he<01:00:54.120> wasn't<01:00:54.390> but<01:00:54.450> also<01:00:54.630> applies<01:00:55.020> to 01:00:55.040 --> 01:00:55.050 align:start position:0% applies to he wasn't but also applies to 01:00:55.050 --> 01:00:57.050 align:start position:0% applies to he wasn't but also applies to EVM<01:00:55.530> on<01:00:55.620> the<01:00:55.680> main<01:00:55.830> net<01:00:56.010> so<01:00:56.730> it's<01:00:56.880> super 01:00:57.050 --> 01:00:57.060 align:start position:0% EVM on the main net so it's super 01:00:57.060 --> 01:01:00.170 align:start position:0% EVM on the main net so it's super exciting<01:00:57.300> and<01:00:57.600> then<01:00:57.930> we<01:00:58.110> have<01:00:58.350> a<01:00:58.760> really<01:00:59.760> grand 01:01:00.170 --> 01:01:00.180 align:start position:0% exciting and then we have a really grand 01:01:00.180 --> 01:01:03.590 align:start position:0% exciting and then we have a really grand vision<01:01:00.660> for<01:01:01.110> the<01:01:01.200> future<01:01:01.940> titled<01:01:02.940> was<01:01:03.360> MOS 01:01:03.590 --> 01:01:03.600 align:start position:0% vision for the future titled was MOS 01:01:03.600 --> 01:01:05.720 align:start position:0% vision for the future titled was MOS which<01:01:04.560> tries<01:01:04.800> to<01:01:04.950> pull<01:01:05.130> everything<01:01:05.400> together 01:01:05.720 --> 01:01:05.730 align:start position:0% which tries to pull everything together 01:01:05.730 --> 01:01:06.390 align:start position:0% which tries to pull everything together what<01:01:06.120> I<01:01:06.150> meant 01:01:06.390 --> 01:01:06.400 align:start position:0% what I meant 01:01:06.400 --> 01:01:08.279 align:start position:0% what I meant in<01:01:06.670> the<01:01:06.730> very<01:01:06.880> first<01:01:07.150> part<01:01:07.390> of<01:01:07.660> the<01:01:07.779> talk<01:01:08.020> as 01:01:08.279 --> 01:01:08.289 align:start position:0% in the very first part of the talk as 01:01:08.289 --> 01:01:11.010 align:start position:0% in the very first part of the talk as web<01:01:09.039> two<01:01:09.190> point<01:01:09.220> five<01:01:09.670> versus<01:01:10.119> battery<01:01:10.539> they 01:01:11.010 --> 01:01:11.020 align:start position:0% web two point five versus battery they 01:01:11.020 --> 01:01:13.049 align:start position:0% web two point five versus battery they are<01:01:11.109> like<01:01:11.230> this<01:01:11.380> combined<01:01:11.910> seamless<01:01:12.910> system 01:01:13.049 --> 01:01:13.059 align:start position:0% are like this combined seamless system 01:01:13.059 --> 01:01:15.059 align:start position:0% are like this combined seamless system so<01:01:13.809> that's<01:01:13.900> the<01:01:14.049> bottom<01:01:14.319> of<01:01:14.410> our<01:01:14.529> talk<01:01:14.829> and 01:01:15.059 --> 01:01:15.069 align:start position:0% so that's the bottom of our talk and 01:01:15.069 --> 01:01:18.599 align:start position:0% so that's the bottom of our talk and then<01:01:15.369> we<01:01:15.549> have<01:01:15.930> a<01:01:16.930> really<01:01:17.349> big<01:01:17.559> topic<01:01:18.010> on<01:01:18.160> how 01:01:18.599 --> 01:01:18.609 align:start position:0% then we have a really big topic on how 01:01:18.609 --> 01:01:21.539 align:start position:0% then we have a really big topic on how to<01:01:18.970> do<01:01:19.210> SH<01:01:19.270> as<01:01:19.569> per<01:01:19.779> in<01:01:20.020> a<01:01:20.109> different<01:01:20.349> way<01:01:20.549> so 01:01:21.539 --> 01:01:21.549 align:start position:0% to do SH as per in a different way so 01:01:21.549 --> 01:01:23.910 align:start position:0% to do SH as per in a different way so that's<01:01:21.970> like<01:01:22.089> 40<01:01:22.480> minutes<01:01:22.599> and<01:01:23.500> we<01:01:23.650> have<01:01:23.770> one 01:01:23.910 --> 01:01:23.920 align:start position:0% that's like 40 minutes and we have one 01:01:23.920 --> 01:01:27.269 align:start position:0% that's like 40 minutes and we have one hour<01:01:24.039> left<01:01:24.089> like<01:01:25.089> 55<01:01:25.480> minutes<01:01:26.069> anybody<01:01:27.069> wants 01:01:27.269 --> 01:01:27.279 align:start position:0% hour left like 55 minutes anybody wants 01:01:27.279 --> 01:01:36.130 align:start position:0% hour left like 55 minutes anybody wants to<01:01:27.369> take<01:01:27.490> a<01:01:27.520> break 01:01:36.130 --> 01:01:36.140 align:start position:0% 01:01:36.140 --> 01:01:38.200 align:start position:0% you