WEBVTT Kind: captions Language: en 00:00:03.640 --> 00:00:08.549 align:start position:0% [Music] 00:00:08.549 --> 00:00:08.559 align:start position:0% 00:00:08.559 --> 00:00:11.830 align:start position:0% so<00:00:09.120> hi<00:00:09.360> everyone<00:00:10.160> thanks<00:00:10.400> for<00:00:10.599> being 00:00:11.830 --> 00:00:11.840 align:start position:0% so hi everyone thanks for being 00:00:11.840 --> 00:00:15.430 align:start position:0% so hi everyone thanks for being here<00:00:12.840> I'm<00:00:13.200> Patricio<00:00:13.759> Paladino<00:00:14.759> I'm<00:00:15.120> one<00:00:15.280> of 00:00:15.430 --> 00:00:15.440 align:start position:0% here I'm Patricio Paladino I'm one of 00:00:15.440 --> 00:00:19.189 align:start position:0% here I'm Patricio Paladino I'm one of the<00:00:15.599> co-founders<00:00:16.560> and<00:00:16.920> the<00:00:17.240> CTO<00:00:18.240> of<00:00:18.560> nomic 00:00:19.189 --> 00:00:19.199 align:start position:0% the co-founders and the CTO of nomic 00:00:19.199 --> 00:00:21.950 align:start position:0% the co-founders and the CTO of nomic foundation<00:00:20.199> nomic<00:00:20.800> is<00:00:20.920> a<00:00:21.119> nonprofit 00:00:21.950 --> 00:00:21.960 align:start position:0% foundation nomic is a nonprofit 00:00:21.960 --> 00:00:24.509 align:start position:0% foundation nomic is a nonprofit dedicated<00:00:22.680> to<00:00:23.439> improve<00:00:23.880> the<00:00:24.039> ethereum 00:00:24.509 --> 00:00:24.519 align:start position:0% dedicated to improve the ethereum 00:00:24.519 --> 00:00:26.830 align:start position:0% dedicated to improve the ethereum development<00:00:25.080> platforms<00:00:25.720> for<00:00:25.960> Builders<00:00:26.640> like 00:00:26.830 --> 00:00:26.840 align:start position:0% development platforms for Builders like 00:00:26.840 --> 00:00:30.269 align:start position:0% development platforms for Builders like you<00:00:27.720> at<00:00:27.960> Nomi<00:00:28.439> what<00:00:28.560> we<00:00:28.720> do<00:00:29.080> is<00:00:29.279> creating<00:00:30.000> open 00:00:30.269 --> 00:00:30.279 align:start position:0% you at Nomi what we do is creating open 00:00:30.279 --> 00:00:33.310 align:start position:0% you at Nomi what we do is creating open source<00:00:30.720> infrastructure<00:00:31.720> and<00:00:31.920> tooling<00:00:32.320> for 00:00:33.310 --> 00:00:33.320 align:start position:0% source infrastructure and tooling for 00:00:33.320 --> 00:00:37.150 align:start position:0% source infrastructure and tooling for ethereum<00:00:34.320> and<00:00:34.520> our<00:00:35.360> most<00:00:35.680> well-known<00:00:36.200> tool<00:00:36.680> is 00:00:37.150 --> 00:00:37.160 align:start position:0% ethereum and our most well-known tool is 00:00:37.160 --> 00:00:40.229 align:start position:0% ethereum and our most well-known tool is harut<00:00:38.160> and<00:00:38.320> we've<00:00:38.480> been<00:00:38.640> building<00:00:39.040> harut<00:00:39.600> for 00:00:40.229 --> 00:00:40.239 align:start position:0% harut and we've been building harut for 00:00:40.239 --> 00:00:43.790 align:start position:0% harut and we've been building harut for quite<00:00:40.600> some<00:00:40.879> time<00:00:41.480> we<00:00:41.640> started<00:00:42.120> it<00:00:42.320> in<00:00:42.480> 2018<00:00:43.399> so 00:00:43.790 --> 00:00:43.800 align:start position:0% quite some time we started it in 2018 so 00:00:43.800 --> 00:00:46.350 align:start position:0% quite some time we started it in 2018 so almost<00:00:44.160> 7<00:00:44.440> years<00:00:44.680> ago<00:00:45.440> and<00:00:45.600> it<00:00:45.719> grew<00:00:46.120> from 00:00:46.350 --> 00:00:46.360 align:start position:0% almost 7 years ago and it grew from 00:00:46.360 --> 00:00:48.510 align:start position:0% almost 7 years ago and it grew from being<00:00:46.680> a<00:00:46.960> side<00:00:47.320> project<00:00:47.920> to<00:00:48.120> being<00:00:48.360> a 00:00:48.510 --> 00:00:48.520 align:start position:0% being a side project to being a 00:00:48.520 --> 00:00:50.549 align:start position:0% being a side project to being a collection<00:00:48.879> of<00:00:49.079> different<00:00:49.440> tools<00:00:50.199> that 00:00:50.549 --> 00:00:50.559 align:start position:0% collection of different tools that 00:00:50.559 --> 00:00:54.029 align:start position:0% collection of different tools that include<00:00:51.559> not<00:00:51.800> just<00:00:52.079> Hara<00:00:52.559> the<00:00:52.719> task<00:00:53.039> Runner 00:00:54.029 --> 00:00:54.039 align:start position:0% include not just Hara the task Runner 00:00:54.039 --> 00:00:55.549 align:start position:0% include not just Hara the task Runner and<00:00:54.160> the<00:00:54.320> framework<00:00:54.840> also<00:00:55.079> a<00:00:55.199> network 00:00:55.549 --> 00:00:55.559 align:start position:0% and the framework also a network 00:00:55.559 --> 00:00:58.270 align:start position:0% and the framework also a network simulator<00:00:56.480> it<00:00:56.680> includes<00:00:57.280> things<00:00:57.600> like<00:00:57.879> a<00:00:58.120> a 00:00:58.270 --> 00:00:58.280 align:start position:0% simulator it includes things like a a 00:00:58.280 --> 00:01:01.069 align:start position:0% simulator it includes things like a a deployment<00:00:58.760> solution<00:00:59.760> and<00:01:00.120> and<00:01:00.760> better 00:01:01.069 --> 00:01:01.079 align:start position:0% deployment solution and and better 00:01:01.079 --> 00:01:03.709 align:start position:0% deployment solution and and better support<00:01:01.440> for<00:01:01.640> solidity<00:01:02.440> in<00:01:02.680> vs<00:01:03.079> code<00:01:03.480> and 00:01:03.709 --> 00:01:03.719 align:start position:0% support for solidity in vs code and 00:01:03.719 --> 00:01:05.230 align:start position:0% support for solidity in vs code and different 00:01:05.230 --> 00:01:05.240 align:start position:0% different 00:01:05.240 --> 00:01:08.190 align:start position:0% different editors<00:01:06.240> creating<00:01:06.760> these<00:01:06.960> things<00:01:07.520> expose<00:01:08.000> us 00:01:08.190 --> 00:01:08.200 align:start position:0% editors creating these things expose us 00:01:08.200 --> 00:01:10.910 align:start position:0% editors creating these things expose us to<00:01:08.840> almost<00:01:09.200> the<00:01:09.320> entirety<00:01:10.040> of<00:01:10.240> the 00:01:10.910 --> 00:01:10.920 align:start position:0% to almost the entirety of the 00:01:10.920 --> 00:01:13.749 align:start position:0% to almost the entirety of the infrastructure<00:01:11.920> landscape<00:01:12.560> of<00:01:12.720> ethereum<00:01:13.600> and 00:01:13.749 --> 00:01:13.759 align:start position:0% infrastructure landscape of ethereum and 00:01:13.759 --> 00:01:19.630 align:start position:0% infrastructure landscape of ethereum and we<00:01:14.040> got<00:01:14.240> to<00:01:14.400> learn<00:01:14.799> about<00:01:15.520> its 00:01:19.630 --> 00:01:19.640 align:start position:0% 00:01:19.640 --> 00:01:21.749 align:start position:0% limitations<00:01:20.640> and<00:01:20.799> I<00:01:20.920> want<00:01:21.079> to<00:01:21.159> share<00:01:21.479> a<00:01:21.600> few 00:01:21.749 --> 00:01:21.759 align:start position:0% limitations and I want to share a few 00:01:21.759 --> 00:01:26.030 align:start position:0% limitations and I want to share a few learnings<00:01:23.000> that<00:01:24.000> we<00:01:24.159> got<00:01:24.360> so<00:01:24.600> far<00:01:25.600> the<00:01:25.759> first 00:01:26.030 --> 00:01:26.040 align:start position:0% learnings that we got so far the first 00:01:26.040 --> 00:01:28.390 align:start position:0% learnings that we got so far the first learning<00:01:26.840> is<00:01:27.079> that<00:01:27.439> building<00:01:27.799> touring<00:01:28.159> for 00:01:28.390 --> 00:01:28.400 align:start position:0% learning is that building touring for 00:01:28.400 --> 00:01:31.149 align:start position:0% learning is that building touring for ethereum<00:01:29.079> is<00:01:29.280> challenging<00:01:30.400> it's<00:01:30.759> actually 00:01:31.149 --> 00:01:31.159 align:start position:0% ethereum is challenging it's actually 00:01:31.159 --> 00:01:32.109 align:start position:0% ethereum is challenging it's actually pretty 00:01:32.109 --> 00:01:32.119 align:start position:0% pretty 00:01:32.119 --> 00:01:34.630 align:start position:0% pretty challenging<00:01:33.119> and<00:01:33.280> this<00:01:33.399> is<00:01:33.560> not<00:01:34.200> something 00:01:34.630 --> 00:01:34.640 align:start position:0% challenging and this is not something 00:01:34.640 --> 00:01:37.469 align:start position:0% challenging and this is not something exclusive<00:01:35.079> to<00:01:35.240> harut<00:01:36.240> if<00:01:36.360> you<00:01:36.520> were<00:01:36.759> to<00:01:37.119> to 00:01:37.469 --> 00:01:37.479 align:start position:0% exclusive to harut if you were to to 00:01:37.479 --> 00:01:40.069 align:start position:0% exclusive to harut if you were to to build<00:01:38.079> any<00:01:38.320> kind<00:01:38.479> of<00:01:38.640> tool<00:01:38.880> or<00:01:39.079> infrastructure 00:01:40.069 --> 00:01:40.079 align:start position:0% build any kind of tool or infrastructure 00:01:40.079 --> 00:01:42.950 align:start position:0% build any kind of tool or infrastructure in<00:01:40.320> ethereum<00:01:41.320> most<00:01:41.600> probably<00:01:42.159> you'll<00:01:42.640> find 00:01:42.950 --> 00:01:42.960 align:start position:0% in ethereum most probably you'll find 00:01:42.960 --> 00:01:46.429 align:start position:0% in ethereum most probably you'll find yourself<00:01:43.399> with<00:01:43.560> a<00:01:43.799> me<00:01:44.079> unmet<00:01:44.640> needs<00:01:45.600> and<00:01:46.000> you 00:01:46.429 --> 00:01:46.439 align:start position:0% yourself with a me unmet needs and you 00:01:46.439 --> 00:01:49.069 align:start position:0% yourself with a me unmet needs and you you<00:01:46.560> will<00:01:46.799> have<00:01:47.000> to<00:01:47.520> either<00:01:48.360> create<00:01:48.680> your<00:01:48.840> own 00:01:49.069 --> 00:01:49.079 align:start position:0% you will have to either create your own 00:01:49.079 --> 00:01:52.230 align:start position:0% you will have to either create your own Solutions<00:01:50.040> or<00:01:50.320> or<00:01:50.479> your<00:01:50.600> own<00:01:50.799> workarounds<00:01:51.479> or 00:01:52.230 --> 00:01:52.240 align:start position:0% Solutions or or your own workarounds or 00:01:52.240 --> 00:01:55.630 align:start position:0% Solutions or or your own workarounds or hacks<00:01:53.240> to<00:01:53.399> see<00:01:53.640> some<00:01:53.920> examples<00:01:54.880> if<00:01:55.040> we<00:01:55.159> were<00:01:55.399> to 00:01:55.630 --> 00:01:55.640 align:start position:0% hacks to see some examples if we were to 00:01:55.640 --> 00:01:57.709 align:start position:0% hacks to see some examples if we were to create<00:01:56.159> a<00:01:56.399> solidity 00:01:57.709 --> 00:01:57.719 align:start position:0% create a solidity 00:01:57.719 --> 00:02:00.069 align:start position:0% create a solidity formatter<00:01:58.719> which<00:01:58.920> is<00:01:59.200> just<00:01:59.399> a<00:01:59.560> tool<00:01:59.920> that 00:02:00.069 --> 00:02:00.079 align:start position:0% formatter which is just a tool that 00:02:00.079 --> 00:02:01.950 align:start position:0% formatter which is just a tool that takes<00:02:00.320> your<00:02:00.479> solity<00:02:00.960> source<00:02:01.280> code<00:02:01.640> and 00:02:01.950 --> 00:02:01.960 align:start position:0% takes your solity source code and 00:02:01.960 --> 00:02:06.510 align:start position:0% takes your solity source code and reprint<00:02:02.560> it<00:02:03.119> reprint<00:02:03.799> it<00:02:04.360> in<00:02:04.520> a<00:02:04.920> nice<00:02:05.520> format 00:02:06.510 --> 00:02:06.520 align:start position:0% reprint it reprint it in a nice format 00:02:06.520 --> 00:02:08.430 align:start position:0% reprint it reprint it in a nice format the<00:02:06.680> first<00:02:06.920> thing<00:02:07.119> that<00:02:07.240> you<00:02:07.360> would<00:02:07.560> need<00:02:08.080> is<00:02:08.239> a 00:02:08.430 --> 00:02:08.440 align:start position:0% the first thing that you would need is a 00:02:08.440 --> 00:02:11.309 align:start position:0% the first thing that you would need is a parer<00:02:09.360> a<00:02:09.560> library<00:02:10.080> or<00:02:10.239> a<00:02:10.399> tool<00:02:10.800> that<00:02:11.000> takes 00:02:11.309 --> 00:02:11.319 align:start position:0% parer a library or a tool that takes 00:02:11.319 --> 00:02:15.350 align:start position:0% parer a library or a tool that takes that<00:02:12.000> text<00:02:13.000> process<00:02:13.440> it<00:02:13.720> in<00:02:13.879> a<00:02:14.080> in<00:02:14.160> a<00:02:14.400> way<00:02:14.920> that 00:02:15.350 --> 00:02:15.360 align:start position:0% that text process it in a in a way that 00:02:15.360 --> 00:02:18.630 align:start position:0% that text process it in a in a way that it<00:02:15.519> will<00:02:15.720> allow<00:02:16.080> you<00:02:16.239> to<00:02:16.480> then<00:02:17.080> pre-int<00:02:17.840> it 00:02:18.630 --> 00:02:18.640 align:start position:0% it will allow you to then pre-int it 00:02:18.640 --> 00:02:21.110 align:start position:0% it will allow you to then pre-int it easily<00:02:19.640> and<00:02:19.879> yeah<00:02:20.080> you<00:02:20.200> will<00:02:20.519> find<00:02:20.840> some 00:02:21.110 --> 00:02:21.120 align:start position:0% easily and yeah you will find some 00:02:21.120 --> 00:02:23.630 align:start position:0% easily and yeah you will find some parcels<00:02:21.560> for<00:02:21.760> solidity<00:02:22.280> out<00:02:22.560> there<00:02:23.319> but<00:02:23.519> all 00:02:23.630 --> 00:02:23.640 align:start position:0% parcels for solidity out there but all 00:02:23.640 --> 00:02:25.830 align:start position:0% parcels for solidity out there but all of<00:02:23.800> them<00:02:24.000> will<00:02:24.200> have<00:02:24.599> their<00:02:25.239> set<00:02:25.480> of 00:02:25.830 --> 00:02:25.840 align:start position:0% of them will have their set of 00:02:25.840 --> 00:02:29.390 align:start position:0% of them will have their set of limitations<00:02:26.840> they<00:02:27.000> may<00:02:27.400> either<00:02:27.959> pass<00:02:28.400> in 00:02:29.390 --> 00:02:29.400 align:start position:0% limitations they may either pass in 00:02:29.400 --> 00:02:31.869 align:start position:0% limitations they may either pass in somewhere<00:02:30.200> approximation<00:02:30.840> of 00:02:31.869 --> 00:02:31.879 align:start position:0% somewhere approximation of 00:02:31.879 --> 00:02:34.670 align:start position:0% somewhere approximation of solidity<00:02:32.879> that<00:02:33.040> it's<00:02:33.280> not<00:02:33.560> clear<00:02:34.080> which<00:02:34.440> which 00:02:34.670 --> 00:02:34.680 align:start position:0% solidity that it's not clear which which 00:02:34.680 --> 00:02:36.710 align:start position:0% solidity that it's not clear which which particular<00:02:35.160> version<00:02:35.480> they<00:02:35.599> are<00:02:35.760> passsing<00:02:36.519> or 00:02:36.710 --> 00:02:36.720 align:start position:0% particular version they are passsing or 00:02:36.720 --> 00:02:38.550 align:start position:0% particular version they are passsing or they<00:02:36.879> may<00:02:37.040> be<00:02:37.239> passsing<00:02:37.640> a<00:02:37.800> single<00:02:38.160> version 00:02:38.550 --> 00:02:38.560 align:start position:0% they may be passsing a single version 00:02:38.560 --> 00:02:41.110 align:start position:0% they may be passsing a single version where<00:02:38.800> your<00:02:38.959> tool<00:02:39.239> wants<00:02:39.519> to<00:02:40.200> process<00:02:40.800> every 00:02:41.110 --> 00:02:41.120 align:start position:0% where your tool wants to process every 00:02:41.120 --> 00:02:42.949 align:start position:0% where your tool wants to process every version<00:02:41.800> of 00:02:42.949 --> 00:02:42.959 align:start position:0% version of 00:02:42.959 --> 00:02:45.670 align:start position:0% version of solidity<00:02:43.959> or<00:02:44.159> they<00:02:44.319> may<00:02:44.480> be<00:02:44.680> tied<00:02:44.959> to<00:02:45.120> a<00:02:45.319> single 00:02:45.670 --> 00:02:45.680 align:start position:0% solidity or they may be tied to a single 00:02:45.680 --> 00:02:47.589 align:start position:0% solidity or they may be tied to a single programming<00:02:46.159> language<00:02:46.720> like<00:02:47.000> I<00:02:47.080> want<00:02:47.280> my<00:02:47.400> tool 00:02:47.589 --> 00:02:47.599 align:start position:0% programming language like I want my tool 00:02:47.599 --> 00:02:50.270 align:start position:0% programming language like I want my tool to<00:02:47.760> be<00:02:47.920> buil<00:02:48.159> in<00:02:48.319> R<00:02:49.080> but<00:02:49.360> the<00:02:49.519> part<00:02:49.879> that<00:02:50.000> I<00:02:50.120> want 00:02:50.270 --> 00:02:50.280 align:start position:0% to be buil in R but the part that I want 00:02:50.280 --> 00:02:52.509 align:start position:0% to be buil in R but the part that I want to<00:02:50.400> use<00:02:50.720> is<00:02:50.959> built<00:02:51.200> in<00:02:51.400> JavaScript<00:02:52.040> and<00:02:52.200> I<00:02:52.319> can 00:02:52.509 --> 00:02:52.519 align:start position:0% to use is built in JavaScript and I can 00:02:52.519 --> 00:02:56.309 align:start position:0% to use is built in JavaScript and I can do<00:02:52.720> it<00:02:53.120> and<00:02:53.879> I<00:02:54.760> I<00:02:54.840> don't<00:02:55.040> know<00:02:55.640> find<00:02:55.879> a<00:02:56.040> work 00:02:56.309 --> 00:02:56.319 align:start position:0% do it and I I don't know find a work 00:02:56.319 --> 00:02:59.110 align:start position:0% do it and I I don't know find a work around<00:02:56.840> or<00:02:57.120> hack<00:02:57.400> it<00:02:57.720> together<00:02:58.640> and<00:02:58.840> this 00:02:59.110 --> 00:02:59.120 align:start position:0% around or hack it together and this 00:02:59.120 --> 00:03:01.910 align:start position:0% around or hack it together and this leads<00:02:59.480> to<00:03:00.120> clearly<00:03:00.720> less<00:03:01.000> than<00:03:01.200> ideal 00:03:01.910 --> 00:03:01.920 align:start position:0% leads to clearly less than ideal 00:03:01.920 --> 00:03:04.670 align:start position:0% leads to clearly less than ideal solutions<00:03:02.920> to<00:03:03.080> see<00:03:03.280> some<00:03:03.440> more<00:03:03.680> examples<00:03:04.560> if 00:03:04.670 --> 00:03:04.680 align:start position:0% solutions to see some more examples if 00:03:04.680 --> 00:03:06.789 align:start position:0% solutions to see some more examples if we<00:03:04.799> were<00:03:05.000> to<00:03:05.400> build<00:03:05.640> a<00:03:05.799> linter<00:03:06.200> a<00:03:06.360> solidity 00:03:06.789 --> 00:03:06.799 align:start position:0% we were to build a linter a solidity 00:03:06.799 --> 00:03:08.949 align:start position:0% we were to build a linter a solidity linter<00:03:07.440> we<00:03:07.560> would<00:03:07.840> have<00:03:08.159> all<00:03:08.400> those<00:03:08.640> same 00:03:08.949 --> 00:03:08.959 align:start position:0% linter we would have all those same 00:03:08.959 --> 00:03:11.630 align:start position:0% linter we would have all those same problems<00:03:09.480> and<00:03:09.640> more<00:03:10.360> what<00:03:10.519> if<00:03:10.680> we<00:03:10.799> want<00:03:11.120> to 00:03:11.630 --> 00:03:11.640 align:start position:0% problems and more what if we want to 00:03:11.640 --> 00:03:14.309 align:start position:0% problems and more what if we want to type<00:03:11.959> away<00:03:12.239> a<00:03:12.400> rule<00:03:13.000> that<00:03:13.920> I<00:03:14.000> don't<00:03:14.159> know 00:03:14.309 --> 00:03:14.319 align:start position:0% type away a rule that I don't know 00:03:14.319 --> 00:03:16.949 align:start position:0% type away a rule that I don't know forbids<00:03:15.000> that<00:03:15.159> you<00:03:15.280> use<00:03:15.519> a<00:03:15.799> certain<00:03:16.159> type<00:03:16.440> of 00:03:16.949 --> 00:03:16.959 align:start position:0% forbids that you use a certain type of 00:03:16.959 --> 00:03:19.630 align:start position:0% forbids that you use a certain type of storage<00:03:17.400> of<00:03:17.599> your<00:03:17.799> context<00:03:18.799> well<00:03:19.159> you'll 00:03:19.630 --> 00:03:19.640 align:start position:0% storage of your context well you'll 00:03:19.640 --> 00:03:22.910 align:start position:0% storage of your context well you'll definitely<00:03:20.440> definitely<00:03:21.159> not<00:03:21.599> find<00:03:22.159> a<00:03:22.319> library 00:03:22.910 --> 00:03:22.920 align:start position:0% definitely definitely not find a library 00:03:22.920 --> 00:03:25.949 align:start position:0% definitely definitely not find a library that<00:03:23.200> exposes<00:03:23.799> the<00:03:23.920> solid<00:03:24.720> type<00:03:25.040> system<00:03:25.720> for 00:03:25.949 --> 00:03:25.959 align:start position:0% that exposes the solid type system for 00:03:25.959 --> 00:03:28.270 align:start position:0% that exposes the solid type system for you<00:03:26.080> to<00:03:26.280> build<00:03:26.560> this<00:03:26.680> rule<00:03:27.000> simply<00:03:27.840> so<00:03:28.120> what 00:03:28.270 --> 00:03:28.280 align:start position:0% you to build this rule simply so what 00:03:28.280 --> 00:03:30.550 align:start position:0% you to build this rule simply so what would<00:03:28.439> you<00:03:28.560> do<00:03:29.200> well<00:03:29.360> you<00:03:29.519> either<00:03:29.920> bu<00:03:30.200> a<00:03:30.360> part 00:03:30.550 --> 00:03:30.560 align:start position:0% would you do well you either bu a part 00:03:30.560 --> 00:03:33.229 align:start position:0% would you do well you either bu a part of<00:03:30.799> that<00:03:31.519> probably<00:03:32.159> in<00:03:32.319> a<00:03:32.519> quick<00:03:32.680> and<00:03:32.840> dirty 00:03:33.229 --> 00:03:33.239 align:start position:0% of that probably in a quick and dirty 00:03:33.239 --> 00:03:37.030 align:start position:0% of that probably in a quick and dirty fashion<00:03:34.239> or<00:03:34.920> maybe<00:03:35.920> come<00:03:36.159> up<00:03:36.400> with<00:03:36.519> a<00:03:36.760> Half 00:03:37.030 --> 00:03:37.040 align:start position:0% fashion or maybe come up with a Half 00:03:37.040 --> 00:03:38.910 align:start position:0% fashion or maybe come up with a Half Bake<00:03:37.319> solution<00:03:37.840> that<00:03:38.040> it's<00:03:38.280> just<00:03:38.439> a<00:03:38.560> bunch<00:03:38.760> of 00:03:38.910 --> 00:03:38.920 align:start position:0% Bake solution that it's just a bunch of 00:03:38.920 --> 00:03:41.030 align:start position:0% Bake solution that it's just a bunch of characteristics<00:03:39.760> maybe<00:03:40.360> a<00:03:40.560> regular 00:03:41.030 --> 00:03:41.040 align:start position:0% characteristics maybe a regular 00:03:41.040 --> 00:03:43.309 align:start position:0% characteristics maybe a regular expression<00:03:41.640> or<00:03:41.840> something<00:03:42.200> like 00:03:43.309 --> 00:03:43.319 align:start position:0% expression or something like 00:03:43.319 --> 00:03:46.710 align:start position:0% expression or something like that<00:03:44.319> if<00:03:44.439> you<00:03:44.560> were<00:03:44.799> to<00:03:45.120> build<00:03:45.480> a<00:03:45.640> Sol<00:03:46.159> editor 00:03:46.710 --> 00:03:46.720 align:start position:0% that if you were to build a Sol editor 00:03:46.720 --> 00:03:49.550 align:start position:0% that if you were to build a Sol editor things<00:03:47.120> were<00:03:47.360> would<00:03:47.560> be<00:03:48.000> way<00:03:48.319> way<00:03:48.599> worse<00:03:49.360> and 00:03:49.550 --> 00:03:49.560 align:start position:0% things were would be way way worse and 00:03:49.560 --> 00:03:52.630 align:start position:0% things were would be way way worse and trust<00:03:49.840> me<00:03:50.239> we've<00:03:50.480> been<00:03:50.840> there<00:03:51.159> we<00:03:51.319> built<00:03:51.640> one 00:03:52.630 --> 00:03:52.640 align:start position:0% trust me we've been there we built one 00:03:52.640 --> 00:03:55.309 align:start position:0% trust me we've been there we built one and<00:03:53.239> you<00:03:53.760> pretty<00:03:54.000> much<00:03:54.239> have<00:03:54.360> to<00:03:54.560> reimplement 00:03:55.309 --> 00:03:55.319 align:start position:0% and you pretty much have to reimplement 00:03:55.319 --> 00:03:59.869 align:start position:0% and you pretty much have to reimplement a<00:03:55.480> good<00:03:55.640> chunk<00:03:55.959> of<00:03:56.079> Sal<00:03:56.439> seed<00:03:56.799> code<00:03:57.079> analysis 00:03:59.869 --> 00:03:59.879 align:start position:0% a good chunk of Sal seed code analysis 00:03:59.879 --> 00:04:02.429 align:start position:0% a good chunk of Sal seed code analysis but<00:04:00.120> those<00:04:00.360> examples<00:04:00.760> that<00:04:00.920> I<00:04:01.239> named<00:04:01.640> are<00:04:01.879> just 00:04:02.429 --> 00:04:02.439 align:start position:0% but those examples that I named are just 00:04:02.439 --> 00:04:05.270 align:start position:0% but those examples that I named are just three<00:04:02.959> out<00:04:03.200> of<00:04:03.480> a<00:04:03.640> ton<00:04:03.840> of<00:04:04.040> different<00:04:04.400> tools 00:04:05.270 --> 00:04:05.280 align:start position:0% three out of a ton of different tools 00:04:05.280 --> 00:04:09.390 align:start position:0% three out of a ton of different tools and<00:04:05.720> infra<00:04:06.400> infra<00:04:06.799> pieces<00:04:07.400> that<00:04:07.799> any<00:04:08.400> any 00:04:09.390 --> 00:04:09.400 align:start position:0% and infra infra pieces that any any 00:04:09.400 --> 00:04:12.149 align:start position:0% and infra infra pieces that any any realistic<00:04:10.000> or<00:04:10.200> mature<00:04:11.079> development<00:04:11.680> platform 00:04:12.149 --> 00:04:12.159 align:start position:0% realistic or mature development platform 00:04:12.159 --> 00:04:14.509 align:start position:0% realistic or mature development platform has<00:04:12.959> there<00:04:13.079> are<00:04:13.239> more<00:04:13.560> examples<00:04:14.159> that<00:04:14.319> I 00:04:14.509 --> 00:04:14.519 align:start position:0% has there are more examples that I 00:04:14.519 --> 00:04:16.629 align:start position:0% has there are more examples that I listed<00:04:15.000> here<00:04:15.480> but<00:04:15.640> to<00:04:15.760> be<00:04:15.879> honestly<00:04:16.280> these<00:04:16.400> are 00:04:16.629 --> 00:04:16.639 align:start position:0% listed here but to be honestly these are 00:04:16.639 --> 00:04:18.670 align:start position:0% listed here but to be honestly these are just<00:04:17.000> some<00:04:17.239> examples<00:04:17.680> that<00:04:17.840> came<00:04:18.000> to<00:04:18.160> my<00:04:18.320> mind 00:04:18.670 --> 00:04:18.680 align:start position:0% just some examples that came to my mind 00:04:18.680 --> 00:04:21.430 align:start position:0% just some examples that came to my mind and<00:04:18.840> that<00:04:19.040> could<00:04:19.239> fit<00:04:19.560> in<00:04:19.680> a<00:04:19.840> single<00:04:20.320> slide<00:04:21.320> in 00:04:21.430 --> 00:04:21.440 align:start position:0% and that could fit in a single slide in 00:04:21.440 --> 00:04:24.310 align:start position:0% and that could fit in a single slide in a<00:04:21.680> in<00:04:21.799> a<00:04:21.919> mature<00:04:22.360> platform<00:04:23.000> in<00:04:23.120> a<00:04:23.360> real<00:04:23.759> world 00:04:24.310 --> 00:04:24.320 align:start position:0% a in a mature platform in a real world 00:04:24.320 --> 00:04:26.670 align:start position:0% a in a mature platform in a real world well<00:04:24.600> it's<00:04:24.759> not<00:04:24.919> that<00:04:25.520> it's<00:04:25.639> not<00:04:25.800> real<00:04:26.080> world 00:04:26.670 --> 00:04:26.680 align:start position:0% well it's not that it's not real world 00:04:26.680 --> 00:04:29.990 align:start position:0% well it's not that it's not real world just<00:04:27.560> less<00:04:27.840> mature<00:04:28.680> in<00:04:28.800> a<00:04:28.960> mature<00:04:29.320> platform 00:04:29.990 --> 00:04:30.000 align:start position:0% just less mature in a mature platform 00:04:30.000 --> 00:04:31.710 align:start position:0% just less mature in a mature platform there<00:04:30.120> are<00:04:30.280> tons<00:04:30.560> and<00:04:30.720> tons<00:04:30.960> of<00:04:31.120> tools<00:04:31.560> and 00:04:31.710 --> 00:04:31.720 align:start position:0% there are tons and tons of tools and 00:04:31.720 --> 00:04:34.110 align:start position:0% there are tons and tons of tools and they<00:04:31.840> are<00:04:32.520> constantly<00:04:33.120> new<00:04:33.320> tools<00:04:33.639> being 00:04:34.110 --> 00:04:34.120 align:start position:0% they are constantly new tools being 00:04:34.120 --> 00:04:37.469 align:start position:0% they are constantly new tools being created<00:04:35.120> but<00:04:35.479> in<00:04:35.680> ethereum<00:04:36.320> if<00:04:36.440> you<00:04:36.560> were<00:04:36.800> to 00:04:37.469 --> 00:04:37.479 align:start position:0% created but in ethereum if you were to 00:04:37.479 --> 00:04:40.550 align:start position:0% created but in ethereum if you were to create<00:04:38.479> any<00:04:38.680> one<00:04:38.880> of<00:04:39.039> these<00:04:39.199> tools<00:04:39.960> I<00:04:40.160> assure 00:04:40.550 --> 00:04:40.560 align:start position:0% create any one of these tools I assure 00:04:40.560 --> 00:04:42.950 align:start position:0% create any one of these tools I assure you<00:04:40.840> that<00:04:41.160> your<00:04:41.440> experience<00:04:41.880> won't<00:04:42.120> be<00:04:42.320> smooth 00:04:42.950 --> 00:04:42.960 align:start position:0% you that your experience won't be smooth 00:04:42.960 --> 00:04:46.230 align:start position:0% you that your experience won't be smooth it<00:04:43.080> will<00:04:43.240> be<00:04:43.800> simple<00:04:44.800> it<00:04:44.919> will<00:04:45.080> be<00:04:45.280> similar<00:04:46.039> to 00:04:46.230 --> 00:04:46.240 align:start position:0% it will be simple it will be similar to 00:04:46.240 --> 00:04:48.029 align:start position:0% it will be simple it will be similar to the<00:04:46.400> things<00:04:46.639> that<00:04:46.840> I<00:04:47.000> mentioned<00:04:47.720> you<00:04:47.840> will 00:04:48.029 --> 00:04:48.039 align:start position:0% the things that I mentioned you will 00:04:48.039 --> 00:04:51.029 align:start position:0% the things that I mentioned you will find<00:04:48.360> yourself<00:04:49.360> unmet<00:04:50.000> limitations<00:04:50.800> and<00:04:50.919> you 00:04:51.029 --> 00:04:51.039 align:start position:0% find yourself unmet limitations and you 00:04:51.039 --> 00:04:53.070 align:start position:0% find yourself unmet limitations and you would<00:04:51.280> have<00:04:51.440> to<00:04:51.639> come<00:04:51.880> up<00:04:52.320> with<00:04:52.479> your<00:04:52.639> own 00:04:53.070 --> 00:04:53.080 align:start position:0% would have to come up with your own 00:04:53.080 --> 00:04:55.870 align:start position:0% would have to come up with your own Solutions<00:04:54.080> and<00:04:54.280> to<00:04:54.440> make<00:04:54.639> things<00:04:54.840> a<00:04:54.960> bit<00:04:55.199> worse 00:04:55.870 --> 00:04:55.880 align:start position:0% Solutions and to make things a bit worse 00:04:55.880 --> 00:04:57.830 align:start position:0% Solutions and to make things a bit worse some<00:04:56.080> of<00:04:56.240> these<00:04:56.400> tools<00:04:56.880> you<00:04:57.039> would<00:04:57.240> want<00:04:57.639> them 00:04:57.830 --> 00:04:57.840 align:start position:0% some of these tools you would want them 00:04:57.840 --> 00:05:00.150 align:start position:0% some of these tools you would want them to<00:04:58.080> exist<00:04:58.400> in<00:04:58.560> different<00:04:58.880> languages<00:04:59.840> maybe 00:05:00.150 --> 00:05:00.160 align:start position:0% to exist in different languages maybe 00:05:00.160 --> 00:05:02.189 align:start position:0% to exist in different languages maybe you<00:05:00.280> want<00:05:00.479> a<00:05:00.639> connector<00:05:01.120> language<00:05:01.600> in 00:05:02.189 --> 00:05:02.199 align:start position:0% you want a connector language in 00:05:02.199 --> 00:05:06.070 align:start position:0% you want a connector language in JavaScript<00:05:03.199> in<00:05:03.680> typescript<00:05:04.560> in<00:05:04.960> Python<00:05:05.680> in 00:05:06.070 --> 00:05:06.080 align:start position:0% JavaScript in typescript in Python in 00:05:06.080 --> 00:05:09.390 align:start position:0% JavaScript in typescript in Python in shva<00:05:07.080> and<00:05:07.360> that<00:05:07.759> just<00:05:08.479> add<00:05:08.800> some<00:05:09.039> kind<00:05:09.199> of 00:05:09.390 --> 00:05:09.400 align:start position:0% shva and that just add some kind of 00:05:09.400 --> 00:05:16.310 align:start position:0% shva and that just add some kind of multiplication<00:05:10.120> to<00:05:10.280> the<00:05:10.479> problem<00:05:10.880> making<00:05:11.160> it 00:05:16.310 --> 00:05:16.320 align:start position:0% 00:05:16.320 --> 00:05:18.590 align:start position:0% larger<00:05:17.320> then<00:05:17.520> another<00:05:17.840> learning<00:05:18.280> that<00:05:18.440> we 00:05:18.590 --> 00:05:18.600 align:start position:0% larger then another learning that we 00:05:18.600 --> 00:05:20.309 align:start position:0% larger then another learning that we have<00:05:18.919> is<00:05:19.039> that<00:05:19.240> ethereum<00:05:19.639> is<00:05:19.759> a<00:05:19.880> moving 00:05:20.309 --> 00:05:20.319 align:start position:0% have is that ethereum is a moving 00:05:20.319 --> 00:05:22.870 align:start position:0% have is that ethereum is a moving platform<00:05:21.240> and<00:05:21.479> what<00:05:21.600> do<00:05:21.720> I<00:05:21.840> mean<00:05:22.120> by 00:05:22.870 --> 00:05:22.880 align:start position:0% platform and what do I mean by 00:05:22.880 --> 00:05:25.870 align:start position:0% platform and what do I mean by this<00:05:23.880> well<00:05:24.680> for<00:05:24.919> once<00:05:25.240> ethereum<00:05:25.680> is 00:05:25.870 --> 00:05:25.880 align:start position:0% this well for once ethereum is 00:05:25.880 --> 00:05:28.469 align:start position:0% this well for once ethereum is constantly<00:05:26.360> evolving<00:05:27.160> it<00:05:27.360> evolves<00:05:28.120> through 00:05:28.469 --> 00:05:28.479 align:start position:0% constantly evolving it evolves through 00:05:28.479 --> 00:05:31.230 align:start position:0% constantly evolving it evolves through hard<00:05:28.800> Forks<00:05:29.199> but<00:05:29.360> also<00:05:29.800> through<00:05:29.960> layer<00:05:30.240> twos 00:05:31.230 --> 00:05:31.240 align:start position:0% hard Forks but also through layer twos 00:05:31.240 --> 00:05:33.550 align:start position:0% hard Forks but also through layer twos and<00:05:31.600> there's<00:05:32.280> tons<00:05:32.560> and<00:05:32.720> tons<00:05:32.960> of<00:05:33.080> changes 00:05:33.550 --> 00:05:33.560 align:start position:0% and there's tons and tons of changes 00:05:33.560 --> 00:05:38.749 align:start position:0% and there's tons and tons of changes coming<00:05:33.960> coming<00:05:34.280> up<00:05:34.600> now<00:05:35.520> that<00:05:36.720> are<00:05:37.720> due<00:05:37.919> to<00:05:38.120> new 00:05:38.749 --> 00:05:38.759 align:start position:0% coming coming up now that are due to new 00:05:38.759 --> 00:05:41.749 align:start position:0% coming coming up now that are due to new layer<00:05:39.080> tws<00:05:39.479> popping<00:05:39.800> up<00:05:40.120> every<00:05:40.400> day<00:05:41.319> also<00:05:41.600> the 00:05:41.749 --> 00:05:41.759 align:start position:0% layer tws popping up every day also the 00:05:41.759 --> 00:05:43.430 align:start position:0% layer tws popping up every day also the tooling<00:05:42.120> and<00:05:42.280> librar 00:05:43.430 --> 00:05:43.440 align:start position:0% tooling and librar 00:05:43.440 --> 00:05:47.029 align:start position:0% tooling and librar Chang<00:05:44.440> we<00:05:44.639> went<00:05:45.160> from<00:05:45.560> using<00:05:45.960> web<00:05:46.160> 3<00:05:46.360> shs<00:05:46.880> at 00:05:47.029 --> 00:05:47.039 align:start position:0% Chang we went from using web 3 shs at 00:05:47.039 --> 00:05:49.029 align:start position:0% Chang we went from using web 3 shs at one<00:05:47.240> point<00:05:47.560> then<00:05:47.680> to<00:05:47.840> a<00:05:48.000> new<00:05:48.199> version<00:05:48.479> of<00:05:48.639> web<00:05:48.840> 3 00:05:49.029 --> 00:05:49.039 align:start position:0% one point then to a new version of web 3 00:05:49.039 --> 00:05:51.110 align:start position:0% one point then to a new version of web 3 shs<00:05:49.520> that<00:05:49.639> was<00:05:49.840> completely<00:05:50.319> different<00:05:50.919> then 00:05:51.110 --> 00:05:51.120 align:start position:0% shs that was completely different then 00:05:51.120 --> 00:05:53.510 align:start position:0% shs that was completely different then tether<00:05:51.800> then<00:05:52.000> BM<00:05:52.560> and<00:05:52.680> I'm<00:05:52.800> sure<00:05:53.080> that<00:05:53.280> things 00:05:53.510 --> 00:05:53.520 align:start position:0% tether then BM and I'm sure that things 00:05:53.520 --> 00:05:54.950 align:start position:0% tether then BM and I'm sure that things will<00:05:53.840> still 00:05:54.950 --> 00:05:54.960 align:start position:0% will still 00:05:54.960 --> 00:05:57.670 align:start position:0% will still change<00:05:55.960> finally<00:05:56.600> another<00:05:56.960> thing<00:05:57.160> that<00:05:57.360> also 00:05:57.670 --> 00:05:57.680 align:start position:0% change finally another thing that also 00:05:57.680 --> 00:06:00.710 align:start position:0% change finally another thing that also change<00:05:58.440> is<00:05:58.800> the<00:05:59.000> developer<00:05:59.440> need<00:05:59.680> need 00:06:00.710 --> 00:06:00.720 align:start position:0% change is the developer need need 00:06:00.720 --> 00:06:03.029 align:start position:0% change is the developer need need themselves<00:06:01.720> they<00:06:01.880> buil<00:06:02.280> different<00:06:02.639> kinds<00:06:02.840> of 00:06:03.029 --> 00:06:03.039 align:start position:0% themselves they buil different kinds of 00:06:03.039 --> 00:06:05.790 align:start position:0% themselves they buil different kinds of applications<00:06:03.880> at<00:06:04.039> one<00:06:04.280> point<00:06:04.880> we<00:06:05.039> were<00:06:05.520> all 00:06:05.790 --> 00:06:05.800 align:start position:0% applications at one point we were all 00:06:05.800 --> 00:06:09.510 align:start position:0% applications at one point we were all building<00:06:06.360> stable<00:06:06.800> coins<00:06:07.319> then<00:06:07.599> nfts<00:06:08.319> then<00:06:08.599> Dow 00:06:09.510 --> 00:06:09.520 align:start position:0% building stable coins then nfts then Dow 00:06:09.520 --> 00:06:11.749 align:start position:0% building stable coins then nfts then Dow then<00:06:10.520> different<00:06:10.919> things<00:06:11.319> and<00:06:11.560> those 00:06:11.749 --> 00:06:11.759 align:start position:0% then different things and those 00:06:11.759 --> 00:06:13.390 align:start position:0% then different things and those different<00:06:12.039> things<00:06:12.400> have<00:06:12.680> different<00:06:13.039> needs 00:06:13.390 --> 00:06:13.400 align:start position:0% different things have different needs 00:06:13.400 --> 00:06:15.710 align:start position:0% different things have different needs and<00:06:13.599> different<00:06:13.919> levels<00:06:14.240> of<00:06:14.479> complexity<00:06:15.039> and 00:06:15.710 --> 00:06:15.720 align:start position:0% and different levels of complexity and 00:06:15.720 --> 00:06:19.189 align:start position:0% and different levels of complexity and size<00:06:16.720> not<00:06:16.919> to<00:06:17.080> say<00:06:17.479> that<00:06:18.000> anything<00:06:18.479> about 00:06:19.189 --> 00:06:19.199 align:start position:0% size not to say that anything about 00:06:19.199 --> 00:06:21.550 align:start position:0% size not to say that anything about multi-chain<00:06:20.000> that<00:06:20.240> it's<00:06:20.479> now<00:06:21.080> completely 00:06:21.550 --> 00:06:21.560 align:start position:0% multi-chain that it's now completely 00:06:21.560 --> 00:06:23.830 align:start position:0% multi-chain that it's now completely changing<00:06:22.000> the<00:06:22.120> needs<00:06:22.400> of<00:06:22.680> developers<00:06:23.599> just<00:06:23.759> a 00:06:23.830 --> 00:06:23.840 align:start position:0% changing the needs of developers just a 00:06:23.840 --> 00:06:26.230 align:start position:0% changing the needs of developers just a few<00:06:24.039> years<00:06:24.280> ago<00:06:24.840> things<00:06:25.080> were<00:06:25.599> way<00:06:25.840> simpler 00:06:26.230 --> 00:06:26.240 align:start position:0% few years ago things were way simpler 00:06:26.240 --> 00:06:28.589 align:start position:0% few years ago things were way simpler for<00:06:26.560> an<00:06:26.759> ethereum<00:06:27.199> developer<00:06:28.039> now<00:06:28.280> they<00:06:28.440> have 00:06:28.589 --> 00:06:28.599 align:start position:0% for an ethereum developer now they have 00:06:28.599 --> 00:06:30.710 align:start position:0% for an ethereum developer now they have to<00:06:28.720> deal<00:06:28.960> with<00:06:29.120> multiple<00:06:29.639> change<00:06:29.880> at<00:06:30.000> the<00:06:30.120> same 00:06:30.710 --> 00:06:30.720 align:start position:0% to deal with multiple change at the same 00:06:30.720 --> 00:06:33.629 align:start position:0% to deal with multiple change at the same time<00:06:31.720> and<00:06:31.919> things<00:06:32.199> just<00:06:32.680> get 00:06:33.629 --> 00:06:33.639 align:start position:0% time and things just get 00:06:33.639 --> 00:06:37.110 align:start position:0% time and things just get harder<00:06:34.639> now<00:06:35.400> to<00:06:35.560> be<00:06:35.759> honest<00:06:36.560> this<00:06:36.720> is<00:06:36.880> not 00:06:37.110 --> 00:06:37.120 align:start position:0% harder now to be honest this is not 00:06:37.120 --> 00:06:39.189 align:start position:0% harder now to be honest this is not something<00:06:37.400> unique<00:06:37.720> to<00:06:37.880> ethereum<00:06:38.400> it<00:06:38.560> happens 00:06:39.189 --> 00:06:39.199 align:start position:0% something unique to ethereum it happens 00:06:39.199 --> 00:06:41.469 align:start position:0% something unique to ethereum it happens everywhere<00:06:40.160> every<00:06:40.680> every<00:06:41.039> software 00:06:41.469 --> 00:06:41.479 align:start position:0% everywhere every every software 00:06:41.479 --> 00:06:44.390 align:start position:0% everywhere every every software development<00:06:42.039> platform<00:06:42.560> that<00:06:42.759> it's<00:06:43.000> alive<00:06:43.560> and 00:06:44.390 --> 00:06:44.400 align:start position:0% development platform that it's alive and 00:06:44.400 --> 00:06:46.270 align:start position:0% development platform that it's alive and continues<00:06:44.880> to<00:06:45.080> evolve<00:06:45.759> goes<00:06:46.000> through 00:06:46.270 --> 00:06:46.280 align:start position:0% continues to evolve goes through 00:06:46.280 --> 00:06:49.150 align:start position:0% continues to evolve goes through constant<00:06:46.720> change<00:06:47.479> and<00:06:47.759> renewal<00:06:48.720> it<00:06:48.880> happens 00:06:49.150 --> 00:06:49.160 align:start position:0% constant change and renewal it happens 00:06:49.160 --> 00:06:51.550 align:start position:0% constant change and renewal it happens to<00:06:49.319> node<00:06:49.759> it<00:06:49.919> happens<00:06:50.240> to<00:06:50.599> every<00:06:50.919> every<00:06:51.120> single 00:06:51.550 --> 00:06:51.560 align:start position:0% to node it happens to every every single 00:06:51.560 --> 00:06:54.710 align:start position:0% to node it happens to every every single language<00:06:52.560> what<00:06:52.759> it's<00:06:53.160> Unique<00:06:53.560> to<00:06:53.759> ethereum 00:06:54.710 --> 00:06:54.720 align:start position:0% language what it's Unique to ethereum 00:06:54.720 --> 00:06:56.710 align:start position:0% language what it's Unique to ethereum it's<00:06:55.479> the<00:06:55.639> speed<00:06:55.919> of 00:06:56.710 --> 00:06:56.720 align:start position:0% it's the speed of 00:06:56.720 --> 00:06:59.230 align:start position:0% it's the speed of change<00:06:57.720> and<00:06:57.919> the<00:06:58.080> fact<00:06:58.360> that<00:06:58.599> every<00:06:58.840> tool<00:06:59.120> is 00:06:59.230 --> 00:06:59.240 align:start position:0% change and the fact that every tool is 00:06:59.240 --> 00:07:00.029 align:start position:0% change and the fact that every tool is built 00:07:00.029 --> 00:07:00.039 align:start position:0% built 00:07:00.039 --> 00:07:02.469 align:start position:0% built based<00:07:00.280> on<00:07:00.680> hacks<00:07:01.000> and<00:07:01.160> workarounds<00:07:01.919> as<00:07:02.280> I 00:07:02.469 --> 00:07:02.479 align:start position:0% based on hacks and workarounds as I 00:07:02.479 --> 00:07:04.629 align:start position:0% based on hacks and workarounds as I described<00:07:03.199> and<00:07:03.360> when<00:07:03.440> you<00:07:03.599> combine<00:07:04.039> those<00:07:04.319> two 00:07:04.629 --> 00:07:04.639 align:start position:0% described and when you combine those two 00:07:04.639 --> 00:07:07.830 align:start position:0% described and when you combine those two things<00:07:05.560> things<00:07:06.440> changing<00:07:07.039> quickly<00:07:07.639> and 00:07:07.830 --> 00:07:07.840 align:start position:0% things things changing quickly and 00:07:07.840 --> 00:07:09.990 align:start position:0% things things changing quickly and things<00:07:08.120> being<00:07:08.360> unreliable<00:07:09.199> you<00:07:09.360> get<00:07:09.560> a<00:07:09.680> ton<00:07:09.879> of 00:07:09.990 --> 00:07:10.000 align:start position:0% things being unreliable you get a ton of 00:07:10.000 --> 00:07:12.869 align:start position:0% things being unreliable you get a ton of fragility<00:07:10.560> in<00:07:10.680> the<00:07:10.840> platform 00:07:12.869 --> 00:07:12.879 align:start position:0% fragility in the platform 00:07:12.879 --> 00:07:16.710 align:start position:0% fragility in the platform itself<00:07:13.879> and<00:07:14.360> finally<00:07:15.360> the<00:07:15.919> other<00:07:16.240> thing<00:07:16.479> that 00:07:16.710 --> 00:07:16.720 align:start position:0% itself and finally the other thing that 00:07:16.720 --> 00:07:19.710 align:start position:0% itself and finally the other thing that I<00:07:17.360> or<00:07:17.520> learning<00:07:17.960> that<00:07:18.120> I<00:07:18.240> want<00:07:18.440> to<00:07:18.759> to<00:07:18.919> mention 00:07:19.710 --> 00:07:19.720 align:start position:0% I or learning that I want to to mention 00:07:19.720 --> 00:07:23.550 align:start position:0% I or learning that I want to to mention is<00:07:19.960> that<00:07:20.759> as<00:07:20.879> I<00:07:21.080> mentioned<00:07:21.960> before<00:07:22.680> at<00:07:22.960> nomic 00:07:23.550 --> 00:07:23.560 align:start position:0% is that as I mentioned before at nomic 00:07:23.560 --> 00:07:25.629 align:start position:0% is that as I mentioned before at nomic we<00:07:23.680> don't<00:07:23.840> work<00:07:24.080> just<00:07:24.280> for<00:07:24.479> harat<00:07:25.080> we<00:07:25.240> work<00:07:25.440> for 00:07:25.629 --> 00:07:25.639 align:start position:0% we don't work just for harat we work for 00:07:25.639 --> 00:07:27.589 align:start position:0% we don't work just for harat we work for the<00:07:25.759> entirety<00:07:26.479> of<00:07:26.599> the<00:07:26.759> theum<00:07:27.120> development 00:07:27.589 --> 00:07:27.599 align:start position:0% the entirety of the theum development 00:07:27.599 --> 00:07:30.270 align:start position:0% the entirety of the theum development platform<00:07:28.199> we<00:07:28.319> want<00:07:28.479> to<00:07:28.680> improve<00:07:28.960> it<00:07:29.080> all 00:07:30.270 --> 00:07:30.280 align:start position:0% platform we want to improve it all 00:07:30.280 --> 00:07:33.909 align:start position:0% platform we want to improve it all and<00:07:30.720> if<00:07:31.520> and<00:07:31.800> at<00:07:31.960> one<00:07:32.160> point<00:07:32.400> we<00:07:32.599> realize<00:07:33.520> that 00:07:33.909 --> 00:07:33.919 align:start position:0% and if and at one point we realize that 00:07:33.919 --> 00:07:36.510 align:start position:0% and if and at one point we realize that we<00:07:34.080> can't<00:07:34.360> just<00:07:34.560> do<00:07:34.680> it<00:07:34.800> through<00:07:35.199> harad<00:07:36.199> and<00:07:36.400> we 00:07:36.510 --> 00:07:36.520 align:start position:0% we can't just do it through harad and we 00:07:36.520 --> 00:07:38.670 align:start position:0% we can't just do it through harad and we can<00:07:36.720> just<00:07:36.960> do<00:07:37.120> it<00:07:37.319> by<00:07:37.560> being<00:07:37.840> direct<00:07:38.199> providers 00:07:38.670 --> 00:07:38.680 align:start position:0% can just do it by being direct providers 00:07:38.680 --> 00:07:42.070 align:start position:0% can just do it by being direct providers of<00:07:38.879> final<00:07:39.280> Solutions<00:07:39.919> or<00:07:40.840> developer 00:07:42.070 --> 00:07:42.080 align:start position:0% of final Solutions or developer 00:07:42.080 --> 00:07:44.869 align:start position:0% of final Solutions or developer Solutions<00:07:43.080> why<00:07:43.599> because<00:07:44.000> we<00:07:44.199> have<00:07:44.479> liit 00:07:44.869 --> 00:07:44.879 align:start position:0% Solutions why because we have liit 00:07:44.879 --> 00:07:46.950 align:start position:0% Solutions why because we have liit limited<00:07:45.319> B<00:07:45.599> with<00:07:45.800> we<00:07:45.879> can<00:07:46.039> only<00:07:46.280> focus<00:07:46.599> on<00:07:46.759> so 00:07:46.950 --> 00:07:46.960 align:start position:0% limited B with we can only focus on so 00:07:46.960 --> 00:07:50.270 align:start position:0% limited B with we can only focus on so many<00:07:47.240> things<00:07:47.759> our<00:07:48.000> team<00:07:48.319> is<00:07:48.960> has<00:07:49.120> a<00:07:49.319> limited 00:07:50.270 --> 00:07:50.280 align:start position:0% many things our team is has a limited 00:07:50.280 --> 00:07:53.309 align:start position:0% many things our team is has a limited set<00:07:50.520> of<00:07:50.759> people<00:07:51.720> hopefully<00:07:52.240> it<00:07:52.360> will<00:07:52.560> increase 00:07:53.309 --> 00:07:53.319 align:start position:0% set of people hopefully it will increase 00:07:53.319 --> 00:07:56.110 align:start position:0% set of people hopefully it will increase but<00:07:53.599> it<00:07:53.720> will<00:07:53.919> still<00:07:54.120> be<00:07:54.440> limited<00:07:55.440> and<00:07:55.720> we<00:07:55.879> just 00:07:56.110 --> 00:07:56.120 align:start position:0% but it will still be limited and we just 00:07:56.120 --> 00:07:59.589 align:start position:0% but it will still be limited and we just can't<00:07:56.400> fix<00:07:57.000> everything<00:07:58.000> also<00:07:58.800> if<00:07:58.919> we<00:07:59.039> were<00:07:59.240> to 00:07:59.589 --> 00:07:59.599 align:start position:0% can't fix everything also if we were to 00:07:59.599 --> 00:08:01.469 align:start position:0% can't fix everything also if we were to be<00:07:59.759> direct<00:08:00.080> providers<00:08:00.520> of<00:08:00.919> every<00:08:01.120> single 00:08:01.469 --> 00:08:01.479 align:start position:0% be direct providers of every single 00:08:01.479 --> 00:08:05.469 align:start position:0% be direct providers of every single solution<00:08:02.360> we<00:08:02.560> could<00:08:02.840> become<00:08:03.800> a<00:08:04.800> an<00:08:04.919> ecosystem 00:08:05.469 --> 00:08:05.479 align:start position:0% solution we could become a an ecosystem 00:08:05.479 --> 00:08:07.510 align:start position:0% solution we could become a an ecosystem dependency<00:08:05.960> a<00:08:06.120> core<00:08:06.280> ecosystem 00:08:07.510 --> 00:08:07.520 align:start position:0% dependency a core ecosystem 00:08:07.520 --> 00:08:09.830 align:start position:0% dependency a core ecosystem dependency<00:08:08.520> and<00:08:08.720> that<00:08:09.039> that's<00:08:09.240> not<00:08:09.479> something 00:08:09.830 --> 00:08:09.840 align:start position:0% dependency and that that's not something 00:08:09.840 --> 00:08:14.350 align:start position:0% dependency and that that's not something that<00:08:10.039> we<00:08:10.360> want<00:08:10.599> to<00:08:11.039> be<00:08:12.039> and<00:08:12.960> at<00:08:13.120> the<00:08:13.240> same<00:08:13.520> time 00:08:14.350 --> 00:08:14.360 align:start position:0% that we want to be and at the same time 00:08:14.360 --> 00:08:17.309 align:start position:0% that we want to be and at the same time doing<00:08:14.800> that<00:08:15.280> would<00:08:16.039> or<00:08:16.319> could 00:08:17.309 --> 00:08:17.319 align:start position:0% doing that would or could 00:08:17.319 --> 00:08:19.909 align:start position:0% doing that would or could potentially<00:08:18.319> make<00:08:18.560> us<00:08:18.800> gain<00:08:19.199> a<00:08:19.400> a<00:08:19.520> ton<00:08:19.720> of 00:08:19.909 --> 00:08:19.919 align:start position:0% potentially make us gain a a ton of 00:08:19.919 --> 00:08:22.270 align:start position:0% potentially make us gain a a ton of influence<00:08:20.319> on<00:08:20.479> the<00:08:20.639> platform<00:08:21.280> and<00:08:21.479> that's<00:08:21.680> not 00:08:22.270 --> 00:08:22.280 align:start position:0% influence on the platform and that's not 00:08:22.280 --> 00:08:24.670 align:start position:0% influence on the platform and that's not not<00:08:22.520> aligned<00:08:22.919> with<00:08:23.039> the<00:08:23.159> values<00:08:23.759> of 00:08:24.670 --> 00:08:24.680 align:start position:0% not aligned with the values of 00:08:24.680 --> 00:08:26.309 align:start position:0% not aligned with the values of nomic 00:08:26.309 --> 00:08:26.319 align:start position:0% nomic 00:08:26.319 --> 00:08:28.430 align:start position:0% nomic finally<00:08:27.319> if<00:08:27.479> we<00:08:27.639> were<00:08:27.840> to<00:08:28.000> build<00:08:28.240> the 00:08:28.430 --> 00:08:28.440 align:start position:0% finally if we were to build the 00:08:28.440 --> 00:08:30.070 align:start position:0% finally if we were to build the resolution<00:08:28.919> ourselves 00:08:30.070 --> 00:08:30.080 align:start position:0% resolution ourselves 00:08:30.080 --> 00:08:32.469 align:start position:0% resolution ourselves we<00:08:30.240> would<00:08:30.479> be<00:08:31.080> making<00:08:31.360> a<00:08:31.520> ton<00:08:31.680> of<00:08:31.879> decisions 00:08:32.469 --> 00:08:32.479 align:start position:0% we would be making a ton of decisions 00:08:32.479 --> 00:08:35.790 align:start position:0% we would be making a ton of decisions because<00:08:32.800> we<00:08:32.959> won't<00:08:33.440> build<00:08:33.959> any<00:08:34.919> any<00:08:35.360> any<00:08:35.599> of 00:08:35.790 --> 00:08:35.800 align:start position:0% because we won't build any any any of 00:08:35.800 --> 00:08:38.630 align:start position:0% because we won't build any any any of the<00:08:36.039> many<00:08:37.039> technical<00:08:37.640> approaches<00:08:38.120> for<00:08:38.399> every 00:08:38.630 --> 00:08:38.640 align:start position:0% the many technical approaches for every 00:08:38.640 --> 00:08:40.550 align:start position:0% the many technical approaches for every single<00:08:38.959> tool<00:08:39.479> but<00:08:39.680> we<00:08:39.800> would<00:08:40.039> have<00:08:40.159> to<00:08:40.320> pick 00:08:40.550 --> 00:08:40.560 align:start position:0% single tool but we would have to pick 00:08:40.560 --> 00:08:42.709 align:start position:0% single tool but we would have to pick one<00:08:40.800> or<00:08:40.959> at<00:08:41.120> most<00:08:41.360> two<00:08:42.000> and<00:08:42.159> that<00:08:42.279> would<00:08:42.479> lead 00:08:42.709 --> 00:08:42.719 align:start position:0% one or at most two and that would lead 00:08:42.719 --> 00:08:45.310 align:start position:0% one or at most two and that would lead to<00:08:43.240> less<00:08:43.839> technical<00:08:44.279> exploration<00:08:45.000> less 00:08:45.310 --> 00:08:45.320 align:start position:0% to less technical exploration less 00:08:45.320 --> 00:08:48.550 align:start position:0% to less technical exploration less approaches<00:08:46.160> to<00:08:46.480> every<00:08:46.720> single<00:08:47.120> problem<00:08:48.120> and 00:08:48.550 --> 00:08:48.560 align:start position:0% approaches to every single problem and 00:08:48.560 --> 00:08:50.350 align:start position:0% approaches to every single problem and that<00:08:48.839> could<00:08:49.080> inhibit<00:08:49.560> part<00:08:49.720> of<00:08:49.839> the<00:08:50.000> potential 00:08:50.350 --> 00:08:50.360 align:start position:0% that could inhibit part of the potential 00:08:50.360 --> 00:08:52.550 align:start position:0% that could inhibit part of the potential of<00:08:50.480> the<00:08:50.640> platform<00:08:51.160> it's<00:08:51.360> better<00:08:51.720> to<00:08:51.920> have 00:08:52.550 --> 00:08:52.560 align:start position:0% of the platform it's better to have 00:08:52.560 --> 00:08:54.990 align:start position:0% of the platform it's better to have diversity<00:08:53.560> of<00:08:53.760> ideas<00:08:54.360> diversity<00:08:54.839> of 00:08:54.990 --> 00:08:55.000 align:start position:0% diversity of ideas diversity of 00:08:55.000 --> 00:08:59.550 align:start position:0% diversity of ideas diversity of Technical<00:08:55.600> Solutions<00:08:56.600> and<00:08:57.279> that<00:08:58.279> then<00:08:58.800> every 00:08:59.550 --> 00:08:59.560 align:start position:0% Technical Solutions and that then every 00:08:59.560 --> 00:09:01.750 align:start position:0% Technical Solutions and that then every every<00:08:59.880> every<00:09:00.160> developer<00:09:00.839> every<00:09:01.079> project<00:09:01.480> will 00:09:01.750 --> 00:09:01.760 align:start position:0% every every developer every project will 00:09:01.760 --> 00:09:07.470 align:start position:0% every every developer every project will pick<00:09:02.200> whatever<00:09:03.040> fits<00:09:03.440> best<00:09:03.640> for 00:09:07.470 --> 00:09:07.480 align:start position:0% 00:09:07.480 --> 00:09:11.069 align:start position:0% them<00:09:08.480> so<00:09:08.760> instead<00:09:09.600> at<00:09:09.800> nomic<00:09:10.279> our<00:09:10.519> long-term 00:09:11.069 --> 00:09:11.079 align:start position:0% them so instead at nomic our long-term 00:09:11.079 --> 00:09:13.870 align:start position:0% them so instead at nomic our long-term vision<00:09:11.760> is<00:09:11.880> to<00:09:12.040> build<00:09:12.320> the<00:09:12.480> core<00:09:12.720> pieces<00:09:13.040> of 00:09:13.870 --> 00:09:13.880 align:start position:0% vision is to build the core pieces of 00:09:13.880 --> 00:09:16.790 align:start position:0% vision is to build the core pieces of infrastructure<00:09:14.880> that<00:09:15.040> would<00:09:15.360> enable<00:09:16.360> the 00:09:16.790 --> 00:09:16.800 align:start position:0% infrastructure that would enable the 00:09:16.800 --> 00:09:18.750 align:start position:0% infrastructure that would enable the ecosystem<00:09:17.440> itself<00:09:17.920> to<00:09:18.120> build<00:09:18.399> its<00:09:18.519> own 00:09:18.750 --> 00:09:18.760 align:start position:0% ecosystem itself to build its own 00:09:18.760 --> 00:09:22.230 align:start position:0% ecosystem itself to build its own tooling<00:09:19.480> and<00:09:19.640> do<00:09:19.839> it<00:09:20.399> efficiently<00:09:21.399> and<00:09:21.959> at<00:09:22.120> the 00:09:22.230 --> 00:09:22.240 align:start position:0% tooling and do it efficiently and at the 00:09:22.240 --> 00:09:24.509 align:start position:0% tooling and do it efficiently and at the same<00:09:22.519> time<00:09:22.920> do<00:09:23.120> we<00:09:23.240> need<00:09:23.519> from<00:09:23.680> a<00:09:23.880> nonprofit 00:09:24.509 --> 00:09:24.519 align:start position:0% same time do we need from a nonprofit 00:09:24.519 --> 00:09:26.910 align:start position:0% same time do we need from a nonprofit and<00:09:24.720> independent<00:09:25.200> nonprofit<00:09:26.160> that<00:09:26.399> it<00:09:26.640> has 00:09:26.910 --> 00:09:26.920 align:start position:0% and independent nonprofit that it has 00:09:26.920 --> 00:09:31.710 align:start position:0% and independent nonprofit that it has clear<00:09:27.640> ethereum<00:09:28.120> align<00:09:28.839> incentive 00:09:31.710 --> 00:09:31.720 align:start position:0% 00:09:31.720 --> 00:09:33.350 align:start position:0% which<00:09:31.880> are<00:09:32.079> these<00:09:32.279> pieces<00:09:32.600> of 00:09:33.350 --> 00:09:33.360 align:start position:0% which are these pieces of 00:09:33.360 --> 00:09:35.870 align:start position:0% which are these pieces of infrastructure<00:09:34.360> they<00:09:34.480> are<00:09:34.680> two<00:09:35.440> one<00:09:35.680> is 00:09:35.870 --> 00:09:35.880 align:start position:0% infrastructure they are two one is 00:09:35.880 --> 00:09:38.710 align:start position:0% infrastructure they are two one is called<00:09:36.200> slang<00:09:36.839> and<00:09:36.959> the<00:09:37.079> other<00:09:37.240> one<00:09:37.560> EDR<00:09:38.360> for 00:09:38.710 --> 00:09:38.720 align:start position:0% called slang and the other one EDR for 00:09:38.720 --> 00:09:40.350 align:start position:0% called slang and the other one EDR for ethereum<00:09:39.240> development 00:09:40.350 --> 00:09:40.360 align:start position:0% ethereum development 00:09:40.360 --> 00:09:44.430 align:start position:0% ethereum development runtime<00:09:41.800> slang<00:09:42.800> it's<00:09:43.000> a<00:09:43.160> solidity<00:09:43.640> compiler 00:09:44.430 --> 00:09:44.440 align:start position:0% runtime slang it's a solidity compiler 00:09:44.440 --> 00:09:47.710 align:start position:0% runtime slang it's a solidity compiler as<00:09:44.600> a<00:09:44.760> set<00:09:44.959> of<00:09:45.120> API<00:09:46.000> focus<00:09:46.360> on<00:09:46.560> tooling<00:09:47.560> what 00:09:47.710 --> 00:09:47.720 align:start position:0% as a set of API focus on tooling what 00:09:47.720 --> 00:09:50.710 align:start position:0% as a set of API focus on tooling what does<00:09:47.880> it<00:09:48.279> mean<00:09:49.279> well<00:09:49.800> if<00:09:49.920> we<00:09:50.040> go<00:09:50.240> back<00:09:50.399> to<00:09:50.519> the 00:09:50.710 --> 00:09:50.720 align:start position:0% does it mean well if we go back to the 00:09:50.720 --> 00:09:53.190 align:start position:0% does it mean well if we go back to the examples<00:09:51.360> that<00:09:51.519> I<00:09:51.720> mentioned<00:09:52.519> and<00:09:52.680> we<00:09:52.839> wanted 00:09:53.190 --> 00:09:53.200 align:start position:0% examples that I mentioned and we wanted 00:09:53.200 --> 00:09:55.269 align:start position:0% examples that I mentioned and we wanted to<00:09:53.480> create<00:09:53.680> a<00:09:53.839> formatter<00:09:54.839> and<00:09:55.000> this<00:09:55.120> is 00:09:55.269 --> 00:09:55.279 align:start position:0% to create a formatter and this is 00:09:55.279 --> 00:09:58.069 align:start position:0% to create a formatter and this is actually<00:09:55.600> doable<00:09:56.079> now<00:09:56.839> you<00:09:57.000> could<00:09:57.200> use<00:09:57.600> slangs 00:09:58.069 --> 00:09:58.079 align:start position:0% actually doable now you could use slangs 00:09:58.079 --> 00:10:01.509 align:start position:0% actually doable now you could use slangs formatter<00:09:59.000> sorry<00:09:59.600> not<00:09:59.760> for<00:10:00.000> matter<00:10:00.519> slang 00:10:01.509 --> 00:10:01.519 align:start position:0% formatter sorry not for matter slang 00:10:01.519 --> 00:10:04.949 align:start position:0% formatter sorry not for matter slang parer<00:10:02.519> that<00:10:02.839> that<00:10:03.040> parer<00:10:03.680> will<00:10:03.880> be<00:10:04.519> ready<00:10:04.800> to 00:10:04.949 --> 00:10:04.959 align:start position:0% parer that that parer will be ready to 00:10:04.959 --> 00:10:07.870 align:start position:0% parer that that parer will be ready to be<00:10:05.200> consumed<00:10:05.839> from<00:10:06.120> many<00:10:06.440> languages<00:10:07.440> is<00:10:07.640> ready 00:10:07.870 --> 00:10:07.880 align:start position:0% be consumed from many languages is ready 00:10:07.880 --> 00:10:10.150 align:start position:0% be consumed from many languages is ready to<00:10:08.000> be<00:10:08.200> consumed<00:10:08.640> from<00:10:08.839> many<00:10:09.079> languages<00:10:10.000> and 00:10:10.150 --> 00:10:10.160 align:start position:0% to be consumed from many languages and 00:10:10.160 --> 00:10:12.150 align:start position:0% to be consumed from many languages and it's<00:10:10.360> easy<00:10:10.600> to<00:10:10.760> use<00:10:11.040> supports<00:10:11.519> many<00:10:11.720> languages 00:10:12.150 --> 00:10:12.160 align:start position:0% it's easy to use supports many languages 00:10:12.160 --> 00:10:15.350 align:start position:0% it's easy to use supports many languages of<00:10:12.480> solidity<00:10:13.480> and<00:10:13.760> it's<00:10:14.000> actually<00:10:14.519> being<00:10:14.839> used 00:10:15.350 --> 00:10:15.360 align:start position:0% of solidity and it's actually being used 00:10:15.360 --> 00:10:18.550 align:start position:0% of solidity and it's actually being used by<00:10:15.760> a<00:10:16.000> beta<00:10:16.399> version<00:10:17.000> of<00:10:17.480> of<00:10:17.600> prer<00:10:18.000> solidity 00:10:18.550 --> 00:10:18.560 align:start position:0% by a beta version of of prer solidity 00:10:18.560 --> 00:10:22.509 align:start position:0% by a beta version of of prer solidity right<00:10:18.760> now<00:10:19.279> and<00:10:19.399> it<00:10:19.600> improve<00:10:21.040> how<00:10:22.040> prer 00:10:22.509 --> 00:10:22.519 align:start position:0% right now and it improve how prer 00:10:22.519 --> 00:10:26.310 align:start position:0% right now and it improve how prer solidity<00:10:23.480> can<00:10:24.000> form<00:10:24.279> a<00:10:24.760> form<00:10:25.040> a<00:10:25.320> different 00:10:26.310 --> 00:10:26.320 align:start position:0% solidity can form a form a different 00:10:26.320 --> 00:10:29.550 align:start position:0% solidity can form a form a different versions<00:10:26.680> of<00:10:26.959> solidity<00:10:27.959> for<00:10:28.120> a<00:10:28.279> lter<00:10:28.959> similar 00:10:29.550 --> 00:10:29.560 align:start position:0% versions of solidity for a lter similar 00:10:29.560 --> 00:10:33.190 align:start position:0% versions of solidity for a lter similar thing<00:10:30.160> you<00:10:30.519> get<00:10:30.720> slang<00:10:31.240> it's<00:10:31.360> a<00:10:32.040> library<00:10:33.040> you 00:10:33.190 --> 00:10:33.200 align:start position:0% thing you get slang it's a library you 00:10:33.200 --> 00:10:35.750 align:start position:0% thing you get slang it's a library you get<00:10:33.360> to<00:10:33.480> use<00:10:34.040> a<00:10:34.200> different<00:10:34.480> set<00:10:34.680> of<00:10:34.880> apis<00:10:35.600> that 00:10:35.750 --> 00:10:35.760 align:start position:0% get to use a different set of apis that 00:10:35.760 --> 00:10:39.750 align:start position:0% get to use a different set of apis that slang<00:10:36.639> proposes<00:10:37.720> exposes<00:10:38.720> but<00:10:39.160> same<00:10:39.399> thing 00:10:39.750 --> 00:10:39.760 align:start position:0% slang proposes exposes but same thing 00:10:39.760 --> 00:10:41.670 align:start position:0% slang proposes exposes but same thing you<00:10:40.000> just<00:10:40.399> have<00:10:40.680> the<00:10:40.920> the<00:10:41.040> building<00:10:41.320> blocks 00:10:41.670 --> 00:10:41.680 align:start position:0% you just have the the building blocks 00:10:41.680 --> 00:10:44.949 align:start position:0% you just have the the building blocks available<00:10:42.079> for<00:10:42.560> you<00:10:43.560> by<00:10:43.760> Design<00:10:44.360> slang<00:10:44.760> it 00:10:44.949 --> 00:10:44.959 align:start position:0% available for you by Design slang it 00:10:44.959 --> 00:10:47.310 align:start position:0% available for you by Design slang it Focus<00:10:45.320> On<00:10:45.440> Tools<00:10:46.200> because<00:10:46.519> tools<00:10:46.920> tend<00:10:47.120> to 00:10:47.310 --> 00:10:47.320 align:start position:0% Focus On Tools because tools tend to 00:10:47.320 --> 00:10:50.230 align:start position:0% Focus On Tools because tools tend to have<00:10:47.600> a<00:10:47.760> different<00:10:48.040> set<00:10:48.240> of<00:10:48.920> constraints<00:10:49.920> that 00:10:50.230 --> 00:10:50.240 align:start position:0% have a different set of constraints that 00:10:50.240 --> 00:10:52.470 align:start position:0% have a different set of constraints that just<00:10:50.600> than<00:10:50.800> just<00:10:50.959> a<00:10:51.120> traditional<00:10:51.680> compiler 00:10:52.470 --> 00:10:52.480 align:start position:0% just than just a traditional compiler 00:10:52.480 --> 00:10:55.269 align:start position:0% just than just a traditional compiler for<00:10:52.760> example<00:10:53.600> they<00:10:53.760> may<00:10:53.959> need<00:10:54.200> to<00:10:54.760> deal<00:10:55.040> with 00:10:55.269 --> 00:10:55.279 align:start position:0% for example they may need to deal with 00:10:55.279 --> 00:10:58.590 align:start position:0% for example they may need to deal with different<00:10:55.639> versions<00:10:56.279> of<00:10:56.680> the<00:10:57.240> language<00:10:58.240> uh 00:10:58.590 --> 00:10:58.600 align:start position:0% different versions of the language uh 00:10:58.600 --> 00:11:01.230 align:start position:0% different versions of the language uh while<00:10:58.959> is<00:10:59.480> a<00:10:59.639> traditional<00:11:00.160> compiler<00:11:00.600> just 00:11:01.230 --> 00:11:01.240 align:start position:0% while is a traditional compiler just 00:11:01.240 --> 00:11:04.269 align:start position:0% while is a traditional compiler just deals<00:11:01.639> with<00:11:01.839> one<00:11:02.519> in<00:11:02.680> a<00:11:03.000> tool<00:11:03.480> you<00:11:03.920> want<00:11:04.120> a 00:11:04.269 --> 00:11:04.279 align:start position:0% deals with one in a tool you want a 00:11:04.279 --> 00:11:06.990 align:start position:0% deals with one in a tool you want a single<00:11:04.600> tool<00:11:04.920> to<00:11:05.079> be<00:11:05.200> able<00:11:05.399> to<00:11:05.560> handle<00:11:06.440> the 00:11:06.990 --> 00:11:07.000 align:start position:0% single tool to be able to handle the 00:11:07.000 --> 00:11:09.389 align:start position:0% single tool to be able to handle the then<00:11:07.440> almost<00:11:07.800> or<00:11:08.040> all<00:11:08.200> the<00:11:08.320> entire<00:11:08.760> history<00:11:09.200> of 00:11:09.389 --> 00:11:09.399 align:start position:0% then almost or all the entire history of 00:11:09.399 --> 00:11:11.670 align:start position:0% then almost or all the entire history of the<00:11:09.560> language<00:11:10.360> while<00:11:10.680> a<00:11:10.839> compiler<00:11:11.279> can<00:11:11.480> just 00:11:11.670 --> 00:11:11.680 align:start position:0% the language while a compiler can just 00:11:11.680 --> 00:11:13.670 align:start position:0% the language while a compiler can just focus<00:11:11.959> on<00:11:12.360> a<00:11:12.480> normal<00:11:12.800> compiler<00:11:13.240> can<00:11:13.399> just 00:11:13.670 --> 00:11:13.680 align:start position:0% focus on a normal compiler can just 00:11:13.680 --> 00:11:16.389 align:start position:0% focus on a normal compiler can just focus<00:11:13.920> on<00:11:14.040> a<00:11:14.200> single<00:11:14.519> one<00:11:15.320> same<00:11:15.680> with<00:11:16.120> things 00:11:16.389 --> 00:11:16.399 align:start position:0% focus on a single one same with things 00:11:16.399 --> 00:11:18.550 align:start position:0% focus on a single one same with things like<00:11:16.680> error<00:11:17.120> recovery<00:11:17.680> you<00:11:17.839> may<00:11:18.040> want<00:11:18.360> your 00:11:18.550 --> 00:11:18.560 align:start position:0% like error recovery you may want your 00:11:18.560 --> 00:11:21.870 align:start position:0% like error recovery you may want your formatter<00:11:19.240> to<00:11:19.800> to<00:11:19.959> be<00:11:20.200> more<00:11:21.160> permissive<00:11:21.760> in 00:11:21.870 --> 00:11:21.880 align:start position:0% formatter to to be more permissive in 00:11:21.880 --> 00:11:24.069 align:start position:0% formatter to to be more permissive in the<00:11:22.040> presence<00:11:22.399> of<00:11:22.839> or<00:11:23.000> or<00:11:23.320> forgiving<00:11:23.839> in<00:11:23.959> the 00:11:24.069 --> 00:11:24.079 align:start position:0% the presence of or or forgiving in the 00:11:24.079 --> 00:11:26.990 align:start position:0% the presence of or or forgiving in the presence<00:11:24.360> of<00:11:24.519> errors<00:11:25.360> and<00:11:26.320> similar 00:11:26.990 --> 00:11:27.000 align:start position:0% presence of errors and similar 00:11:27.000 --> 00:11:30.110 align:start position:0% presence of errors and similar constraints<00:11:27.680> like<00:11:27.880> that<00:11:28.480> that<00:11:28.880> make<00:11:29.360> having<00:11:29.639> a 00:11:30.110 --> 00:11:30.120 align:start position:0% constraints like that that make having a 00:11:30.120 --> 00:11:33.310 align:start position:0% constraints like that that make having a tooling<00:11:30.560> oriented<00:11:31.160> compiler<00:11:32.160> a<00:11:32.839> great<00:11:33.160> piece 00:11:33.310 --> 00:11:33.320 align:start position:0% tooling oriented compiler a great piece 00:11:33.320 --> 00:11:35.990 align:start position:0% tooling oriented compiler a great piece of<00:11:33.480> infrastructure<00:11:34.160> for<00:11:34.680> Tool<00:11:35.000> developers 00:11:35.990 --> 00:11:36.000 align:start position:0% of infrastructure for Tool developers 00:11:36.000 --> 00:11:38.750 align:start position:0% of infrastructure for Tool developers and<00:11:36.240> it's<00:11:37.079> publish<00:11:37.480> as<00:11:37.560> a<00:11:37.720> library<00:11:38.240> so<00:11:38.480> you<00:11:38.600> can 00:11:38.750 --> 00:11:38.760 align:start position:0% and it's publish as a library so you can 00:11:38.760 --> 00:11:43.030 align:start position:0% and it's publish as a library so you can use<00:11:39.399> it<00:11:40.399> either<00:11:40.839> from<00:11:41.320> rust<00:11:41.800> or<00:11:42.040> typescript 00:11:43.030 --> 00:11:43.040 align:start position:0% use it either from rust or typescript 00:11:43.040 --> 00:11:45.310 align:start position:0% use it either from rust or typescript and<00:11:43.279> it's<00:11:43.440> also<00:11:43.760> targeting<00:11:44.200> wasm<00:11:44.680> so<00:11:44.959> you<00:11:45.079> can 00:11:45.310 --> 00:11:45.320 align:start position:0% and it's also targeting wasm so you can 00:11:45.320 --> 00:11:48.389 align:start position:0% and it's also targeting wasm so you can even<00:11:45.519> import<00:11:45.839> it<00:11:46.120> from<00:11:46.560> other<00:11:47.040> other 00:11:48.389 --> 00:11:48.399 align:start position:0% even import it from other other 00:11:48.399 --> 00:11:52.750 align:start position:0% even import it from other other places<00:11:49.399> now<00:11:49.800> EDR<00:11:50.639> it's<00:11:50.839> a<00:11:51.160> portable<00:11:52.120> library 00:11:52.750 --> 00:11:52.760 align:start position:0% places now EDR it's a portable library 00:11:52.760 --> 00:11:57.190 align:start position:0% places now EDR it's a portable library also<00:11:53.040> written<00:11:53.399> in<00:11:53.680> Rust<00:11:54.920> it<00:11:55.920> it<00:11:56.079> implements<00:11:56.760> an 00:11:57.190 --> 00:11:57.200 align:start position:0% also written in Rust it it implements an 00:11:57.200 --> 00:12:00.030 align:start position:0% also written in Rust it it implements an ethereum<00:11:57.920> simulator<00:11:58.920> in<00:11:59.240> including<00:11:59.600> some 00:12:00.030 --> 00:12:00.040 align:start position:0% ethereum simulator in including some 00:12:00.040 --> 00:12:01.069 align:start position:0% ethereum simulator in including some layer 00:12:01.069 --> 00:12:01.079 align:start position:0% layer 00:12:01.079 --> 00:12:03.389 align:start position:0% layer choose<00:12:02.079> that<00:12:02.200> means<00:12:02.480> that<00:12:02.600> it<00:12:02.760> simulates<00:12:03.240> the 00:12:03.389 --> 00:12:03.399 align:start position:0% choose that means that it simulates the 00:12:03.399 --> 00:12:06.430 align:start position:0% choose that means that it simulates the network<00:12:04.360> it<00:12:04.720> it's<00:12:05.000> already<00:12:05.320> in<00:12:05.440> production<00:12:06.240> it 00:12:06.430 --> 00:12:06.440 align:start position:0% network it it's already in production it 00:12:06.440 --> 00:12:08.870 align:start position:0% network it it's already in production it Powers<00:12:06.959> carat<00:12:07.440> 2<00:12:07.959> the<00:12:08.079> current<00:12:08.440> version<00:12:08.680> of 00:12:08.870 --> 00:12:08.880 align:start position:0% Powers carat 2 the current version of 00:12:08.880 --> 00:12:12.470 align:start position:0% Powers carat 2 the current version of carat<00:12:09.880> and<00:12:10.440> when<00:12:10.600> we<00:12:10.800> release<00:12:11.200> it<00:12:11.560> we<00:12:11.680> saw 00:12:12.470 --> 00:12:12.480 align:start position:0% carat and when we release it we saw 00:12:12.480 --> 00:12:15.310 align:start position:0% carat and when we release it we saw performance<00:12:13.320> improvements<00:12:14.320> in<00:12:14.880> massive 00:12:15.310 --> 00:12:15.320 align:start position:0% performance improvements in massive 00:12:15.320 --> 00:12:17.069 align:start position:0% performance improvements in massive performance<00:12:15.720> improvements<00:12:16.199> actually<00:12:16.880> in 00:12:17.069 --> 00:12:17.079 align:start position:0% performance improvements actually in 00:12:17.079 --> 00:12:20.150 align:start position:0% performance improvements actually in some<00:12:17.480> Car<00:12:17.920> Projects<00:12:18.440> some<00:12:18.600> of<00:12:18.800> them<00:12:19.160> just 00:12:20.150 --> 00:12:20.160 align:start position:0% some Car Projects some of them just 00:12:20.160 --> 00:12:21.990 align:start position:0% some Car Projects some of them just without<00:12:20.480> changing<00:12:20.920> any<00:12:21.120> single<00:12:21.399> line<00:12:21.560> of<00:12:21.720> code 00:12:21.990 --> 00:12:22.000 align:start position:0% without changing any single line of code 00:12:22.000 --> 00:12:24.750 align:start position:0% without changing any single line of code just<00:12:22.240> byting<00:12:22.920> their<00:12:23.279> dependencies<00:12:24.279> starting 00:12:24.750 --> 00:12:24.760 align:start position:0% just byting their dependencies starting 00:12:24.760 --> 00:12:26.230 align:start position:0% just byting their dependencies starting running<00:12:25.120> 10<00:12:25.399> times 00:12:26.230 --> 00:12:26.240 align:start position:0% running 10 times 00:12:26.240 --> 00:12:30.910 align:start position:0% running 10 times faster<00:12:27.480> and<00:12:28.480> at<00:12:28.600> the<00:12:28.720> same<00:12:28.920> time<00:12:29.519> EDR<00:12:30.519> will 00:12:30.910 --> 00:12:30.920 align:start position:0% faster and at the same time EDR will 00:12:30.920 --> 00:12:33.790 align:start position:0% faster and at the same time EDR will simulate<00:12:31.920> do<00:12:32.160> Sim<00:12:32.480> will<00:12:32.639> simulate<00:12:33.120> optimism 00:12:33.790 --> 00:12:33.800 align:start position:0% simulate do Sim will simulate optimism 00:12:33.800 --> 00:12:36.189 align:start position:0% simulate do Sim will simulate optimism or<00:12:34.079> upstack<00:12:34.760> chain<00:12:35.199> soon<00:12:35.720> and<00:12:35.880> it<00:12:36.000> will 00:12:36.189 --> 00:12:36.199 align:start position:0% or upstack chain soon and it will 00:12:36.199 --> 00:12:39.670 align:start position:0% or upstack chain soon and it will include<00:12:36.600> a<00:12:36.760> solidity<00:12:37.279> test<00:12:38.000> Runner<00:12:39.000> it's 00:12:39.670 --> 00:12:39.680 align:start position:0% include a solidity test Runner it's 00:12:39.680 --> 00:12:41.750 align:start position:0% include a solidity test Runner it's again<00:12:40.079> this<00:12:40.199> is<00:12:40.320> a<00:12:40.480> library<00:12:41.040> this<00:12:41.160> is<00:12:41.320> not<00:12:41.519> just 00:12:41.750 --> 00:12:41.760 align:start position:0% again this is a library this is not just 00:12:41.760 --> 00:12:44.310 align:start position:0% again this is a library this is not just build<00:12:42.000> for<00:12:42.160> harat<00:12:42.680> anyone<00:12:43.040> can<00:12:43.240> install<00:12:43.639> it 00:12:44.310 --> 00:12:44.320 align:start position:0% build for harat anyone can install it 00:12:44.320 --> 00:12:46.470 align:start position:0% build for harat anyone can install it and<00:12:44.639> it<00:12:44.800> can<00:12:44.920> be<00:12:45.079> used<00:12:45.360> for<00:12:45.720> any<00:12:45.920> kind<00:12:46.079> of<00:12:46.199> tool 00:12:46.470 --> 00:12:46.480 align:start position:0% and it can be used for any kind of tool 00:12:46.480 --> 00:12:49.069 align:start position:0% and it can be used for any kind of tool that<00:12:46.639> needs<00:12:46.880> to<00:12:47.040> run<00:12:47.360> simulator<00:12:48.079> simulations 00:12:49.069 --> 00:12:49.079 align:start position:0% that needs to run simulator simulations 00:12:49.079 --> 00:12:52.150 align:start position:0% that needs to run simulator simulations or<00:12:49.279> do<00:12:49.639> any<00:12:49.880> kind<00:12:50.040> of<00:12:50.240> runtime 00:12:52.150 --> 00:12:52.160 align:start position:0% or do any kind of runtime 00:12:52.160 --> 00:12:56.470 align:start position:0% or do any kind of runtime analysis<00:12:53.279> finally<00:12:54.279> slang<00:12:54.800> and<00:12:55.079> EDR<00:12:56.079> are 00:12:56.470 --> 00:12:56.480 align:start position:0% analysis finally slang and EDR are 00:12:56.480 --> 00:12:58.870 align:start position:0% analysis finally slang and EDR are system<00:12:56.920> projects<00:12:57.680> what<00:12:57.839> does<00:12:58.040> that<00:12:58.199> mean<00:12:58.680> that 00:12:58.870 --> 00:12:58.880 align:start position:0% system projects what does that mean that 00:12:58.880 --> 00:13:02.710 align:start position:0% system projects what does that mean that they<00:12:59.240> are<00:12:59.560> designed<00:13:00.000> to<00:13:00.279> work 00:13:02.710 --> 00:13:02.720 align:start position:0% 00:13:02.720 --> 00:13:05.470 align:start position:0% together<00:13:03.720> and<00:13:03.920> but<00:13:04.160> that<00:13:04.920> and<00:13:05.040> that's<00:13:05.240> because 00:13:05.470 --> 00:13:05.480 align:start position:0% together and but that and that's because 00:13:05.480 --> 00:13:07.870 align:start position:0% together and but that and that's because the<00:13:05.600> combination<00:13:06.120> of<00:13:06.320> both<00:13:06.839> will<00:13:07.160> allow<00:13:07.440> us<00:13:07.600> to 00:13:07.870 --> 00:13:07.880 align:start position:0% the combination of both will allow us to 00:13:07.880 --> 00:13:10.430 align:start position:0% the combination of both will allow us to do<00:13:08.440> way<00:13:08.639> more<00:13:08.880> advanced<00:13:09.360> things<00:13:09.920> than<00:13:10.160> what<00:13:10.279> we 00:13:10.430 --> 00:13:10.440 align:start position:0% do way more advanced things than what we 00:13:10.440 --> 00:13:13.230 align:start position:0% do way more advanced things than what we can<00:13:10.600> do<00:13:10.920> with<00:13:11.160> each<00:13:11.320> of<00:13:11.480> them<00:13:11.680> in<00:13:12.240> isolation 00:13:13.230 --> 00:13:13.240 align:start position:0% can do with each of them in isolation 00:13:13.240 --> 00:13:15.910 align:start position:0% can do with each of them in isolation right<00:13:13.399> now<00:13:13.600> we<00:13:13.720> have<00:13:13.880> a<00:13:14.399> a<00:13:14.560> compiler<00:13:15.160> so<00:13:15.399> see 00:13:15.910 --> 00:13:15.920 align:start position:0% right now we have a a compiler so see 00:13:15.920 --> 00:13:18.430 align:start position:0% right now we have a a compiler so see build<00:13:16.240> by<00:13:16.440> one<00:13:16.680> team<00:13:17.279> we<00:13:17.440> have<00:13:17.720> our<00:13:17.920> own<00:13:18.160> Ram 00:13:18.430 --> 00:13:18.440 align:start position:0% build by one team we have our own Ram 00:13:18.440 --> 00:13:21.470 align:start position:0% build by one team we have our own Ram times<00:13:19.040> it's<00:13:19.240> hard<00:13:19.440> to<00:13:19.959> collaborate<00:13:20.959> deeply 00:13:21.470 --> 00:13:21.480 align:start position:0% times it's hard to collaborate deeply 00:13:21.480 --> 00:13:23.750 align:start position:0% times it's hard to collaborate deeply enough<00:13:21.880> to<00:13:22.199> build<00:13:22.600> things<00:13:22.959> like<00:13:23.320> I<00:13:23.399> don't<00:13:23.560> know 00:13:23.750 --> 00:13:23.760 align:start position:0% enough to build things like I don't know 00:13:23.760 --> 00:13:26.590 align:start position:0% enough to build things like I don't know picture<00:13:24.560> chrome<00:13:25.079> chrome<00:13:25.480> development<00:13:25.959> tools 00:13:26.590 --> 00:13:26.600 align:start position:0% picture chrome chrome development tools 00:13:26.600 --> 00:13:28.829 align:start position:0% picture chrome chrome development tools they<00:13:26.720> are<00:13:27.000> dagger<00:13:27.600> you<00:13:27.760> can<00:13:28.079> change<00:13:28.440> variables 00:13:28.829 --> 00:13:28.839 align:start position:0% they are dagger you can change variables 00:13:28.839 --> 00:13:30.829 align:start position:0% they are dagger you can change variables in<00:13:29.160> real<00:13:29.399> time<00:13:29.639> you<00:13:29.800> can<00:13:30.000> rewrite<00:13:30.480> parts<00:13:30.680> of 00:13:30.829 --> 00:13:30.839 align:start position:0% in real time you can rewrite parts of 00:13:30.839 --> 00:13:33.230 align:start position:0% in real time you can rewrite parts of the<00:13:31.000> code<00:13:31.480> keep<00:13:31.680> running<00:13:32.680> those<00:13:32.880> kind<00:13:33.040> of 00:13:33.230 --> 00:13:33.240 align:start position:0% the code keep running those kind of 00:13:33.240 --> 00:13:35.590 align:start position:0% the code keep running those kind of things<00:13:33.880> are<00:13:34.199> possible<00:13:34.760> we<00:13:34.880> can<00:13:35.040> build<00:13:35.279> them<00:13:35.440> in 00:13:35.590 --> 00:13:35.600 align:start position:0% things are possible we can build them in 00:13:35.600 --> 00:13:37.750 align:start position:0% things are possible we can build them in ethereum<00:13:36.120> but<00:13:36.519> they<00:13:36.639> do<00:13:36.839> require<00:13:37.279> a<00:13:37.399> ton<00:13:37.600> of 00:13:37.750 --> 00:13:37.760 align:start position:0% ethereum but they do require a ton of 00:13:37.760 --> 00:13:39.910 align:start position:0% ethereum but they do require a ton of deep<00:13:38.040> collaboration<00:13:38.639> and<00:13:38.920> integration 00:13:39.910 --> 00:13:39.920 align:start position:0% deep collaboration and integration 00:13:39.920 --> 00:13:42.750 align:start position:0% deep collaboration and integration between<00:13:40.240> the<00:13:40.440> compiler<00:13:41.360> and<00:13:41.519> the<00:13:41.680> runtime<00:13:42.560> and 00:13:42.750 --> 00:13:42.760 align:start position:0% between the compiler and the runtime and 00:13:42.760 --> 00:13:44.230 align:start position:0% between the compiler and the runtime and that's<00:13:43.079> the<00:13:43.279> the<00:13:43.399> kind<00:13:43.519> of<00:13:43.680> thing<00:13:43.839> that<00:13:43.959> we<00:13:44.079> are 00:13:44.230 --> 00:13:44.240 align:start position:0% that's the the kind of thing that we are 00:13:44.240 --> 00:13:46.710 align:start position:0% that's the the kind of thing that we are going<00:13:44.519> after<00:13:44.800> at<00:13:44.959> nomic<00:13:45.360> we<00:13:45.480> want<00:13:46.079> EDR<00:13:46.560> and 00:13:46.710 --> 00:13:46.720 align:start position:0% going after at nomic we want EDR and 00:13:46.720 --> 00:13:48.949 align:start position:0% going after at nomic we want EDR and slang<00:13:47.199> to<00:13:47.360> mature<00:13:47.839> to<00:13:48.000> be<00:13:48.199> libraries<00:13:48.760> that 00:13:48.949 --> 00:13:48.959 align:start position:0% slang to mature to be libraries that 00:13:48.959 --> 00:13:50.990 align:start position:0% slang to mature to be libraries that everyone<00:13:49.320> can<00:13:49.519> use<00:13:50.160> they<00:13:50.279> will<00:13:50.519> provide<00:13:50.800> the 00:13:50.990 --> 00:13:51.000 align:start position:0% everyone can use they will provide the 00:13:51.000 --> 00:13:54.030 align:start position:0% everyone can use they will provide the basis<00:13:51.880> for<00:13:52.320> anyone<00:13:52.759> to<00:13:53.199> grab<00:13:53.480> those<00:13:53.680> tools 00:13:54.030 --> 00:13:54.040 align:start position:0% basis for anyone to grab those tools 00:13:54.040 --> 00:13:56.790 align:start position:0% basis for anyone to grab those tools grab<00:13:54.320> those<00:13:54.480> libraries<00:13:55.480> and<00:13:55.839> build<00:13:56.160> the<00:13:56.360> next 00:13:56.790 --> 00:13:56.800 align:start position:0% grab those libraries and build the next 00:13:56.800 --> 00:14:00.990 align:start position:0% grab those libraries and build the next generation<00:13:57.800> of<00:13:58.000> ethereum<00:13:58.399> tooling<00:13:58.759> with<00:13:58.880> them 00:14:00.990 --> 00:14:01.000 align:start position:0% generation of ethereum tooling with them 00:14:01.000 --> 00:14:03.629 align:start position:0% generation of ethereum tooling with them and<00:14:01.440> that's<00:14:01.680> it<00:14:02.120> if<00:14:02.240> you<00:14:02.360> want<00:14:02.560> to<00:14:02.880> learn<00:14:03.199> more 00:14:03.629 --> 00:14:03.639 align:start position:0% and that's it if you want to learn more 00:14:03.639 --> 00:14:07.749 align:start position:0% and that's it if you want to learn more about<00:14:04.519> nomic<00:14:05.519> uh<00:14:05.720> you<00:14:05.839> can<00:14:06.079> scan<00:14:06.480> the<00:14:06.680> QR<00:14:07.279> code 00:14:07.749 --> 00:14:07.759 align:start position:0% about nomic uh you can scan the QR code 00:14:07.759 --> 00:14:11.269 align:start position:0% about nomic uh you can scan the QR code I<00:14:07.920> guess<00:14:08.040> it's<00:14:08.199> on<00:14:08.399> your<00:14:08.759> left<00:14:09.759> um<00:14:10.600> that<00:14:10.920> one 00:14:11.269 --> 00:14:11.279 align:start position:0% I guess it's on your left um that one 00:14:11.279 --> 00:14:13.110 align:start position:0% I guess it's on your left um that one has<00:14:11.600> information<00:14:12.160> about<00:14:12.399> the<00:14:12.600> different 00:14:13.110 --> 00:14:13.120 align:start position:0% has information about the different 00:14:13.120 --> 00:14:15.150 align:start position:0% has information about the different presentations<00:14:14.120> that<00:14:14.240> we<00:14:14.360> are<00:14:14.519> giving<00:14:14.759> at 00:14:15.150 --> 00:14:15.160 align:start position:0% presentations that we are giving at 00:14:15.160 --> 00:14:18.550 align:start position:0% presentations that we are giving at nomic<00:14:16.160> that<00:14:16.279> we<00:14:16.399> are<00:14:16.519> giving<00:14:16.839> at<00:14:17.199> Decon<00:14:18.199> one<00:14:18.360> of 00:14:18.550 --> 00:14:18.560 align:start position:0% nomic that we are giving at Decon one of 00:14:18.560 --> 00:14:21.030 align:start position:0% nomic that we are giving at Decon one of them<00:14:19.000> yesterday<00:14:19.480> I<00:14:19.639> already<00:14:20.000> gave<00:14:20.240> it<00:14:20.800> it's 00:14:21.030 --> 00:14:21.040 align:start position:0% them yesterday I already gave it it's 00:14:21.040 --> 00:14:23.870 align:start position:0% them yesterday I already gave it it's about<00:14:21.440> harat<00:14:21.920> 3<00:14:22.680> the<00:14:23.079> upcoming<00:14:23.480> version<00:14:23.720> of 00:14:23.870 --> 00:14:23.880 align:start position:0% about harat 3 the upcoming version of 00:14:23.880 --> 00:14:27.230 align:start position:0% about harat 3 the upcoming version of carat<00:14:24.600> it's<00:14:24.800> not<00:14:25.000> ready<00:14:25.279> for<00:14:26.199> production<00:14:26.800> yet 00:14:27.230 --> 00:14:27.240 align:start position:0% carat it's not ready for production yet 00:14:27.240 --> 00:14:29.269 align:start position:0% carat it's not ready for production yet but<00:14:27.519> there<00:14:27.639> is<00:14:27.759> an<00:14:27.920> internal<00:14:28.360> Alpha<00:14:28.680> and<00:14:29.160> of 00:14:29.269 --> 00:14:29.279 align:start position:0% but there is an internal Alpha and of 00:14:29.279 --> 00:14:31.509 align:start position:0% but there is an internal Alpha and of information<00:14:29.759> in<00:14:29.959> that<00:14:30.240> presentation<00:14:31.240> it's 00:14:31.509 --> 00:14:31.519 align:start position:0% information in that presentation it's 00:14:31.519 --> 00:14:34.749 align:start position:0% information in that presentation it's recorded<00:14:32.079> so<00:14:32.360> you<00:14:32.480> can<00:14:32.720> watch<00:14:32.920> it<00:14:33.639> today<00:14:34.639> I 00:14:34.749 --> 00:14:34.759 align:start position:0% recorded so you can watch it today I 00:14:34.759 --> 00:14:37.509 align:start position:0% recorded so you can watch it today I think<00:14:35.000> at<00:14:35.279> 5<00:14:35.519> or<00:14:35.720> 6<00:14:36.040> p.m.<00:14:36.680> there's 00:14:37.509 --> 00:14:37.519 align:start position:0% think at 5 or 6 p.m. there's 00:14:37.519 --> 00:14:40.310 align:start position:0% think at 5 or 6 p.m. there's a<00:14:38.519> presentation<00:14:39.199> by<00:14:39.480> one<00:14:39.639> of<00:14:39.800> our<00:14:40.040> team 00:14:40.310 --> 00:14:40.320 align:start position:0% a presentation by one of our team 00:14:40.320 --> 00:14:43.509 align:start position:0% a presentation by one of our team members<00:14:41.240> that's<00:14:41.519> going<00:14:41.680> to<00:14:41.880> explain<00:14:42.440> how<00:14:42.680> EDR 00:14:43.509 --> 00:14:43.519 align:start position:0% members that's going to explain how EDR 00:14:43.519 --> 00:14:46.030 align:start position:0% members that's going to explain how EDR can<00:14:43.759> simulate<00:14:44.360> different<00:14:44.720> T<00:14:44.959> CH<00:14:45.399> different 00:14:46.030 --> 00:14:46.040 align:start position:0% can simulate different T CH different 00:14:46.040 --> 00:14:49.710 align:start position:0% can simulate different T CH different networks<00:14:47.040> and<00:14:47.399> tomorrow<00:14:48.120> at<00:14:48.320> 12<00:14:48.680> or<00:14:48.880> 12:30 00:14:49.710 --> 00:14:49.720 align:start position:0% networks and tomorrow at 12 or 12:30 00:14:49.720 --> 00:14:52.269 align:start position:0% networks and tomorrow at 12 or 12:30 there<00:14:49.839> is<00:14:49.959> a<00:14:50.160> presentation<00:14:50.720> about<00:14:51.040> slang<00:14:52.040> and 00:14:52.269 --> 00:14:52.279 align:start position:0% there is a presentation about slang and 00:14:52.279 --> 00:14:54.030 align:start position:0% there is a presentation about slang and how<00:14:52.480> you<00:14:52.600> can<00:14:52.759> use<00:14:52.959> it<00:14:53.199> to<00:14:53.399> analyze<00:14:53.880> your 00:14:54.030 --> 00:14:54.040 align:start position:0% how you can use it to analyze your 00:14:54.040 --> 00:14:57.870 align:start position:0% how you can use it to analyze your solidity<00:14:54.560> code<00:14:55.240> with<00:14:55.920> some<00:14:56.199> pretty<00:14:56.440> cool<00:14:56.880> apis 00:14:57.870 --> 00:14:57.880 align:start position:0% solidity code with some pretty cool apis 00:14:57.880 --> 00:15:00.230 align:start position:0% solidity code with some pretty cool apis finally<00:14:58.440> if<00:14:58.600> you<00:14:58.839> want<00:14:59.040> want<00:14:59.199> to<00:14:59.320> work<00:14:59.600> with<00:14:59.800> us 00:15:00.230 --> 00:15:00.240 align:start position:0% finally if you want want to work with us 00:15:00.240 --> 00:15:02.150 align:start position:0% finally if you want want to work with us you<00:15:00.600> enjoy<00:15:01.079> the<00:15:01.240> the<00:15:01.320> kind<00:15:01.480> of<00:15:01.600> thing<00:15:01.800> that<00:15:01.920> we 00:15:02.150 --> 00:15:02.160 align:start position:0% you enjoy the the kind of thing that we 00:15:02.160 --> 00:15:05.150 align:start position:0% you enjoy the the kind of thing that we do<00:15:02.680> you<00:15:02.800> can<00:15:03.079> scan<00:15:03.519> the<00:15:03.639> other<00:15:03.959> QR<00:15:04.279> code<00:15:04.959> and 00:15:05.150 --> 00:15:05.160 align:start position:0% do you can scan the other QR code and 00:15:05.160 --> 00:15:07.949 align:start position:0% do you can scan the other QR code and learn<00:15:05.399> more<00:15:05.680> about<00:15:06.240> show<00:15:07.160> show<00:15:07.480> offerings 00:15:07.949 --> 00:15:07.959 align:start position:0% learn more about show show offerings 00:15:07.959 --> 00:15:10.629 align:start position:0% learn more about show show offerings show<00:15:08.199> positions<00:15:08.600> at<00:15:08.839> nomic<00:15:09.839> and<00:15:10.040> that's<00:15:10.240> it 00:15:10.629 --> 00:15:10.639 align:start position:0% show positions at nomic and that's it 00:15:10.639 --> 00:15:15.269 align:start position:0% show positions at nomic and that's it thank 00:15:15.269 --> 00:15:15.279 align:start position:0% 00:15:15.279 --> 00:15:18.470 align:start position:0% you<00:15:16.279> patrio<00:15:17.120> thank<00:15:17.320> you<00:15:17.560> so<00:15:17.839> much<00:15:18.079> and<00:15:18.240> for 00:15:18.470 --> 00:15:18.480 align:start position:0% you patrio thank you so much and for 00:15:18.480 --> 00:15:21.269 align:start position:0% you patrio thank you so much and for everyone<00:15:19.120> it's<00:15:19.360> still<00:15:19.680> open<00:15:19.880> for<00:15:20.120> qaa<00:15:20.720> so<00:15:21.000> just 00:15:21.269 --> 00:15:21.279 align:start position:0% everyone it's still open for qaa so just 00:15:21.279 --> 00:15:23.990 align:start position:0% everyone it's still open for qaa so just Q<00:15:21.800> disc<00:15:22.160> code<00:15:22.600> we<00:15:22.720> do<00:15:22.880> have<00:15:23.079> one<00:15:23.360> question<00:15:23.800> here 00:15:23.990 --> 00:15:24.000 align:start position:0% Q disc code we do have one question here 00:15:24.000 --> 00:15:29.069 align:start position:0% Q disc code we do have one question here for<00:15:24.240> you<00:15:24.480> so<00:15:25.399> can<00:15:26.480> EDR<00:15:27.480> be<00:15:28.000> used<00:15:28.399> for<00:15:28.680> things 00:15:29.069 --> 00:15:29.079 align:start position:0% for you so can EDR be used for things 00:15:29.079 --> 00:15:31.150 align:start position:0% for you so can EDR be used for things like<00:15:29.319> simulation<00:15:29.959> with<00:15:30.160> altered<00:15:30.680> storage 00:15:31.150 --> 00:15:31.160 align:start position:0% like simulation with altered storage 00:15:31.160 --> 00:15:34.790 align:start position:0% like simulation with altered storage State<00:15:31.800> Storage<00:15:32.160> over<00:15:32.480> rights<00:15:33.120> in<00:15:33.319> tenderly 00:15:34.790 --> 00:15:34.800 align:start position:0% State Storage over rights in tenderly 00:15:34.800 --> 00:15:38.030 align:start position:0% State Storage over rights in tenderly terms<00:15:35.959> yes<00:15:36.959> sorry<00:15:37.240> but<00:15:37.440> that's<00:15:37.639> the<00:15:37.759> whole 00:15:38.030 --> 00:15:38.040 align:start position:0% terms yes sorry but that's the whole 00:15:38.040 --> 00:15:42.590 align:start position:0% terms yes sorry but that's the whole answer<00:15:38.440> yes<00:15:39.440> it 00:15:42.590 --> 00:15:42.600 align:start position:0% 00:15:42.600 --> 00:15:45.910 align:start position:0% can<00:15:43.600> we<00:15:43.720> have<00:15:43.959> another<00:15:44.440> question<00:15:44.839> here<00:15:45.720> when 00:15:45.910 --> 00:15:45.920 align:start position:0% can we have another question here when 00:15:45.920 --> 00:15:48.710 align:start position:0% can we have another question here when we<00:15:46.160> advance<00:15:46.680> testing<00:15:47.440> features<00:15:48.440> like 00:15:48.710 --> 00:15:48.720 align:start position:0% we advance testing features like 00:15:48.720 --> 00:15:52.230 align:start position:0% we advance testing features like symbolic<00:15:49.240> debugging<00:15:50.000> be<00:15:50.279> integrated<00:15:51.120> or<00:15:52.040> will 00:15:52.230 --> 00:15:52.240 align:start position:0% symbolic debugging be integrated or will 00:15:52.240 --> 00:15:54.790 align:start position:0% symbolic debugging be integrated or will it<00:15:52.399> be<00:15:52.639> possible<00:15:53.199> to<00:15:53.399> connect<00:15:53.680> in<00:15:53.920> Advan<00:15:54.360> noes 00:15:54.790 --> 00:15:54.800 align:start position:0% it be possible to connect in Advan noes 00:15:54.800 --> 00:15:57.910 align:start position:0% it be possible to connect in Advan noes like<00:15:55.000> build<00:15:55.360> bear<00:15:55.800> sandbox<00:15:56.440> instead<00:15:56.839> of<00:15:57.399> hard 00:15:57.910 --> 00:15:57.920 align:start position:0% like build bear sandbox instead of hard 00:15:57.920 --> 00:16:00.030 align:start position:0% like build bear sandbox instead of hard heart<00:15:58.560> notes 00:16:00.030 --> 00:16:00.040 align:start position:0% heart notes 00:16:00.040 --> 00:16:01.470 align:start position:0% heart notes uh<00:16:00.199> well<00:16:00.360> I<00:16:00.440> don't<00:16:00.680> have<00:16:00.959> I<00:16:01.040> don't<00:16:01.199> think<00:16:01.360> I 00:16:01.470 --> 00:16:01.480 align:start position:0% uh well I don't have I don't think I 00:16:01.480 --> 00:16:04.309 align:start position:0% uh well I don't have I don't think I have<00:16:01.600> an<00:16:01.839> answer<00:16:02.440> for<00:16:02.759> the<00:16:02.959> first<00:16:03.720> uh<00:16:03.959> part<00:16:04.160> of 00:16:04.309 --> 00:16:04.319 align:start position:0% have an answer for the first uh part of 00:16:04.319 --> 00:16:07.590 align:start position:0% have an answer for the first uh part of the<00:16:04.639> question<00:16:05.639> uh<00:16:06.199> we'll<00:16:06.560> have<00:16:06.720> to<00:16:06.959> analyze<00:16:07.360> it 00:16:07.590 --> 00:16:07.600 align:start position:0% the question uh we'll have to analyze it 00:16:07.600 --> 00:16:10.590 align:start position:0% the question uh we'll have to analyze it I<00:16:07.720> can<00:16:07.920> promise<00:16:08.240> on<00:16:08.399> any<00:16:08.680> timeline<00:16:09.399> right<00:16:09.600> now 00:16:10.590 --> 00:16:10.600 align:start position:0% I can promise on any timeline right now 00:16:10.600 --> 00:16:12.150 align:start position:0% I can promise on any timeline right now uh<00:16:10.759> the<00:16:10.920> second<00:16:11.160> one<00:16:11.360> I<00:16:11.480> think<00:16:11.639> should<00:16:11.880> be 00:16:12.150 --> 00:16:12.160 align:start position:0% uh the second one I think should be 00:16:12.160 --> 00:16:15.230 align:start position:0% uh the second one I think should be possible<00:16:12.720> yes<00:16:13.360> uh<00:16:13.480> if<00:16:13.680> not<00:16:14.240> just<00:16:14.680> reach<00:16:15.000> out 00:16:15.230 --> 00:16:15.240 align:start position:0% possible yes uh if not just reach out 00:16:15.240 --> 00:16:19.670 align:start position:0% possible yes uh if not just reach out through<00:16:15.560> GitHub<00:16:16.279> and<00:16:16.600> we<00:16:16.759> we<00:16:16.880> can<00:16:17.079> analyze 00:16:19.670 --> 00:16:19.680 align:start position:0% 00:16:19.680 --> 00:16:22.389 align:start position:0% it<00:16:20.680> we<00:16:20.800> do<00:16:20.959> have<00:16:21.160> another<00:16:21.600> question<00:16:22.079> here 00:16:22.389 --> 00:16:22.399 align:start position:0% it we do have another question here 00:16:22.399 --> 00:16:24.389 align:start position:0% it we do have another question here automatic<00:16:23.120> test<00:16:23.440> generation<00:16:24.000> is<00:16:24.120> that 00:16:24.389 --> 00:16:24.399 align:start position:0% automatic test generation is that 00:16:24.399 --> 00:16:26.629 align:start position:0% automatic test generation is that something<00:16:24.920> that<00:16:25.160> anomic<00:16:25.639> Foundation<00:16:26.360> is 00:16:26.629 --> 00:16:26.639 align:start position:0% something that anomic Foundation is 00:16:26.639 --> 00:16:30.189 align:start position:0% something that anomic Foundation is interested<00:16:27.519> in<00:16:27.880> adding<00:16:28.560> wait<00:16:28.959> I<00:16:29.040> can<00:16:29.279> read<00:16:29.519> it 00:16:30.189 --> 00:16:30.199 align:start position:0% interested in adding wait I can read it 00:16:30.199 --> 00:16:31.910 align:start position:0% interested in adding wait I can read it is 00:16:31.910 --> 00:16:31.920 align:start position:0% is 00:16:31.920 --> 00:16:36.309 align:start position:0% is it<00:16:32.920> shouldn't<00:16:33.279> we<00:16:33.440> do<00:16:33.800> can<00:16:34.040> EDR<00:16:34.600> used<00:16:35.519> be<00:16:35.720> used 00:16:36.309 --> 00:16:36.319 align:start position:0% it shouldn't we do can EDR used be used 00:16:36.319 --> 00:16:41.550 align:start position:0% it shouldn't we do can EDR used be used for<00:16:37.319> oh<00:16:37.800> okay<00:16:38.040> cool<00:16:38.360> thank 00:16:41.550 --> 00:16:41.560 align:start position:0% 00:16:41.560 --> 00:16:45.710 align:start position:0% you<00:16:42.560> uh<00:16:43.000> it's<00:16:43.160> not<00:16:43.480> our<00:16:44.480> I'll<00:16:44.880> reread<00:16:45.279> it<00:16:45.519> just 00:16:45.710 --> 00:16:45.720 align:start position:0% you uh it's not our I'll reread it just 00:16:45.720 --> 00:16:48.189 align:start position:0% you uh it's not our I'll reread it just in<00:16:45.880> case<00:16:46.199> automatic<00:16:46.720> test<00:16:47.000> generation<00:16:48.000> is 00:16:48.189 --> 00:16:48.199 align:start position:0% in case automatic test generation is 00:16:48.199 --> 00:16:50.030 align:start position:0% in case automatic test generation is that<00:16:48.440> something<00:16:48.880> that<00:16:49.279> the<00:16:49.399> foundation<00:16:49.880> is 00:16:50.030 --> 00:16:50.040 align:start position:0% that something that the foundation is 00:16:50.040 --> 00:16:52.509 align:start position:0% that something that the foundation is interested<00:16:50.519> in<00:16:50.680> not<00:16:50.880> in<00:16:51.560> not<00:16:52.079> we're<00:16:52.240> current 00:16:52.509 --> 00:16:52.519 align:start position:0% interested in not in not we're current 00:16:52.519 --> 00:16:54.509 align:start position:0% interested in not in not we're current Focus<00:16:53.279> I<00:16:53.440> think<00:16:53.839> there's<00:16:54.000> a<00:16:54.160> ton<00:16:54.360> of 00:16:54.509 --> 00:16:54.519 align:start position:0% Focus I think there's a ton of 00:16:54.519 --> 00:16:57.030 align:start position:0% Focus I think there's a ton of development<00:16:55.120> going<00:16:55.360> on<00:16:55.920> super<00:16:56.240> interesting 00:16:57.030 --> 00:16:57.040 align:start position:0% development going on super interesting 00:16:57.040 --> 00:17:00.749 align:start position:0% development going on super interesting on<00:16:57.639> AI<00:16:58.600> but<00:16:59.079> that's<00:16:59.240> not<00:16:59.440> the<00:16:59.560> focus<00:16:59.920> of<00:17:00.160> our 00:17:00.749 --> 00:17:00.759 align:start position:0% on AI but that's not the focus of our 00:17:00.759 --> 00:17:02.910 align:start position:0% on AI but that's not the focus of our organization<00:17:01.759> if<00:17:01.959> there<00:17:02.079> is<00:17:02.240> a<00:17:02.440> way<00:17:02.600> to 00:17:02.910 --> 00:17:02.920 align:start position:0% organization if there is a way to 00:17:02.920 --> 00:17:05.350 align:start position:0% organization if there is a way to integrate<00:17:03.880> those<00:17:04.199> things 00:17:05.350 --> 00:17:05.360 align:start position:0% integrate those things 00:17:05.360 --> 00:17:10.949 align:start position:0% integrate those things cheaply<00:17:06.360> we<00:17:06.520> will<00:17:07.400> but<00:17:08.160> harad<00:17:08.839> itself<00:17:09.240> it's<00:17:09.959> a 00:17:10.949 --> 00:17:10.959 align:start position:0% cheaply we will but harad itself it's a 00:17:10.959 --> 00:17:12.750 align:start position:0% cheaply we will but harad itself it's a super<00:17:11.280> flexible<00:17:11.839> platform<00:17:12.280> you<00:17:12.400> can<00:17:12.520> build 00:17:12.750 --> 00:17:12.760 align:start position:0% super flexible platform you can build 00:17:12.760 --> 00:17:14.270 align:start position:0% super flexible platform you can build your<00:17:12.880> own<00:17:13.039> plugin<00:17:13.480> so<00:17:13.720> if<00:17:13.839> you<00:17:13.959> want<00:17:14.120> to 00:17:14.270 --> 00:17:14.280 align:start position:0% your own plugin so if you want to 00:17:14.280 --> 00:17:16.949 align:start position:0% your own plugin so if you want to experiment<00:17:14.720> with<00:17:15.000> this<00:17:15.760> and<00:17:16.039> create<00:17:16.400> your<00:17:16.559> own 00:17:16.949 --> 00:17:16.959 align:start position:0% experiment with this and create your own 00:17:16.959 --> 00:17:19.429 align:start position:0% experiment with this and create your own automatic<00:17:17.480> generation<00:17:18.480> plug-in<00:17:19.000> automatic 00:17:19.429 --> 00:17:19.439 align:start position:0% automatic generation plug-in automatic 00:17:19.439 --> 00:17:21.590 align:start position:0% automatic generation plug-in automatic test<00:17:19.720> generation<00:17:20.160> plugin<00:17:20.799> should<00:17:21.079> be<00:17:21.280> super 00:17:21.590 --> 00:17:21.600 align:start position:0% test generation plugin should be super 00:17:21.600 --> 00:17:25.429 align:start position:0% test generation plugin should be super safe<00:17:21.880> for<00:17:22.079> where<00:17:23.039> go<00:17:23.760> try<00:17:24.000> it<00:17:24.160> out<00:17:24.520> and<00:17:24.799> tell<00:17:25.039> us 00:17:25.429 --> 00:17:25.439 align:start position:0% safe for where go try it out and tell us 00:17:25.439 --> 00:17:29.430 align:start position:0% safe for where go try it out and tell us how<00:17:25.679> it<00:17:26.160> it<00:17:26.559> went<00:17:27.120> yeah 00:17:29.430 --> 00:17:29.440 align:start position:0% how it it went yeah 00:17:29.440 --> 00:17:31.350 align:start position:0% how it it went yeah perfect<00:17:29.960> patri<00:17:30.320> you<00:17:30.600> thank<00:17:30.760> you<00:17:30.880> so<00:17:31.080> much<00:17:31.240> for 00:17:31.350 --> 00:17:31.360 align:start position:0% perfect patri you thank you so much for 00:17:31.360 --> 00:17:33.070 align:start position:0% perfect patri you thank you so much for your<00:17:31.600> presentation<00:17:32.280> thanks<00:17:32.559> everyone<00:17:32.919> for 00:17:33.070 --> 00:17:33.080 align:start position:0% your presentation thanks everyone for 00:17:33.080 --> 00:17:35.909 align:start position:0% your presentation thanks everyone for your<00:17:33.320> questions<00:17:33.960> we'll<00:17:34.200> be<00:17:34.440> back<00:17:35.000> in<00:17:35.520> 15 00:17:35.909 --> 00:17:35.919 align:start position:0% your questions we'll be back in 15 00:17:35.919 --> 00:17:38.200 align:start position:0% your questions we'll be back in 15 minutes