WEBVTT Kind: captions Language: en 00:00:04.410 --> 00:00:08.209 align:start position:0% my<00:00:05.310> name<00:00:05.430> is<00:00:05.520> Greg<00:00:06.560> might<00:00:07.560> know<00:00:07.680> me<00:00:07.830> online<00:00:07.979> is 00:00:08.209 --> 00:00:08.219 align:start position:0% my name is Greg might know me online is 00:00:08.219 --> 00:00:10.310 align:start position:0% my name is Greg might know me online is Greg<00:00:08.400> the<00:00:08.549> Greek<00:00:09.080> today<00:00:10.080> I'm<00:00:10.139> gonna<00:00:10.230> be 00:00:10.310 --> 00:00:10.320 align:start position:0% Greg the Greek today I'm gonna be 00:00:10.320 --> 00:00:12.410 align:start position:0% Greg the Greek today I'm gonna be talking<00:00:10.440> about<00:00:10.639> towards<00:00:11.639> e2<00:00:11.940> developer 00:00:12.410 --> 00:00:12.420 align:start position:0% talking about towards e2 developer 00:00:12.420 --> 00:00:16.160 align:start position:0% talking about towards e2 developer tooling<00:00:12.690> basically<00:00:14.330> you<00:00:15.330> know<00:00:15.420> how<00:00:16.049> are<00:00:16.109> you 00:00:16.160 --> 00:00:16.170 align:start position:0% tooling basically you know how are you 00:00:16.170 --> 00:00:18.109 align:start position:0% tooling basically you know how are you gonna<00:00:16.289> go<00:00:16.500> from<00:00:16.650> you<00:00:16.770> 22<00:00:17.340> and<00:00:17.580> is<00:00:17.850> it<00:00:18.000> gonna 00:00:18.109 --> 00:00:18.119 align:start position:0% gonna go from you 22 and is it gonna 00:00:18.119 --> 00:00:20.230 align:start position:0% gonna go from you 22 and is it gonna work<00:00:18.410> and<00:00:19.410> what<00:00:19.619> are<00:00:19.680> we<00:00:19.740> gonna<00:00:19.859> do<00:00:20.010> about<00:00:20.070> it 00:00:20.230 --> 00:00:20.240 align:start position:0% work and what are we gonna do about it 00:00:20.240 --> 00:00:24.050 align:start position:0% work and what are we gonna do about it so<00:00:21.350> why<00:00:22.350> not<00:00:22.650> get<00:00:22.740> a<00:00:22.800> preview<00:00:23.040> here<00:00:23.220> okay 00:00:24.050 --> 00:00:24.060 align:start position:0% so why not get a preview here okay 00:00:24.060 --> 00:00:28.090 align:start position:0% so why not get a preview here okay so<00:00:24.390> quickly<00:00:24.810> who's<00:00:25.110> changed 00:00:28.090 --> 00:00:28.100 align:start position:0% 00:00:28.100 --> 00:00:31.100 align:start position:0% who<00:00:29.100> is<00:00:29.220> changed<00:00:29.460> safe<00:00:29.610> I<00:00:29.850> changed<00:00:30.360> we're<00:00:30.480> a<00:00:30.510> Rd 00:00:31.100 --> 00:00:31.110 align:start position:0% who is changed safe I changed we're a Rd 00:00:31.110 --> 00:00:34.430 align:start position:0% who is changed safe I changed we're a Rd protocol<00:00:32.099> shop<00:00:32.279> of<00:00:32.489> Toronto<00:00:32.940> about<00:00:33.780> 26<00:00:34.170> people 00:00:34.430 --> 00:00:34.440 align:start position:0% protocol shop of Toronto about 26 people 00:00:34.440 --> 00:00:35.930 align:start position:0% protocol shop of Toronto about 26 people mainly<00:00:34.829> in<00:00:34.980> Toronto<00:00:35.250> and<00:00:35.460> a<00:00:35.489> little<00:00:35.850> bit 00:00:35.930 --> 00:00:35.940 align:start position:0% mainly in Toronto and a little bit 00:00:35.940 --> 00:00:38.599 align:start position:0% mainly in Toronto and a little bit distributed<00:00:36.390> and<00:00:37.379> we're<00:00:37.679> working<00:00:38.039> on<00:00:38.129> an<00:00:38.280> e2 00:00:38.599 --> 00:00:38.609 align:start position:0% distributed and we're working on an e2 00:00:38.609 --> 00:00:42.860 align:start position:0% distributed and we're working on an e2 client<00:00:38.909> called<00:00:39.059> lodestar<00:00:39.980> and<00:00:41.329> who<00:00:42.329> I<00:00:42.390> am<00:00:42.600> I'm 00:00:42.860 --> 00:00:42.870 align:start position:0% client called lodestar and who I am I'm 00:00:42.870 --> 00:00:44.329 align:start position:0% client called lodestar and who I am I'm one<00:00:43.019> of<00:00:43.109> the<00:00:43.170> cofounders<00:00:43.260> of<00:00:43.620> VP<00:00:43.829> engineering 00:00:44.329 --> 00:00:44.339 align:start position:0% one of the cofounders of VP engineering 00:00:44.339 --> 00:00:46.610 align:start position:0% one of the cofounders of VP engineering you<00:00:45.179> can<00:00:45.329> find<00:00:45.539> me<00:00:45.659> Greg<00:00:45.929> the<00:00:46.050> Greek<00:00:46.260> just 00:00:46.610 --> 00:00:46.620 align:start position:0% you can find me Greg the Greek just 00:00:46.620 --> 00:00:49.669 align:start position:0% you can find me Greg the Greek just about<00:00:46.739> on<00:00:46.890> everything<00:00:47.659> and<00:00:48.659> yeah<00:00:48.899> so<00:00:49.139> what<00:00:49.589> is 00:00:49.669 --> 00:00:49.679 align:start position:0% about on everything and yeah so what is 00:00:49.679 --> 00:00:51.500 align:start position:0% about on everything and yeah so what is lodestar<00:00:50.039> so<00:00:50.280> lodestar<00:00:50.819> is<00:00:50.879> a<00:00:50.969> type<00:00:51.120> script<00:00:51.359> an 00:00:51.500 --> 00:00:51.510 align:start position:0% lodestar so lodestar is a type script an 00:00:51.510 --> 00:00:53.389 align:start position:0% lodestar so lodestar is a type script an assembly<00:00:51.809> script<00:00:52.079> basically<00:00:52.889> eath<00:00:53.219> to 00:00:53.389 --> 00:00:53.399 align:start position:0% assembly script basically eath to 00:00:53.399 --> 00:00:54.829 align:start position:0% assembly script basically eath to ecosystem<00:00:53.969> we're<00:00:54.210> building<00:00:54.510> just<00:00:54.690> about 00:00:54.829 --> 00:00:54.839 align:start position:0% ecosystem we're building just about 00:00:54.839 --> 00:00:56.799 align:start position:0% ecosystem we're building just about everything<00:00:55.289> that<00:00:55.889> we<00:00:55.979> can<00:00:56.129> in<00:00:56.190> there 00:00:56.799 --> 00:00:56.809 align:start position:0% everything that we can in there 00:00:56.809 --> 00:00:59.869 align:start position:0% everything that we can in there rationale<00:00:57.809> you<00:00:58.589> know<00:00:58.710> a<00:00:58.920> lot<00:00:59.219> of<00:00:59.339> when<00:00:59.789> it 00:00:59.869 --> 00:00:59.879 align:start position:0% rationale you know a lot of when it 00:00:59.879 --> 00:01:02.299 align:start position:0% rationale you know a lot of when it comes<00:00:59.909> to<00:01:00.440> interacting<00:01:01.440> with<00:01:01.769> blockchains 00:01:02.299 --> 00:01:02.309 align:start position:0% comes to interacting with blockchains 00:01:02.309 --> 00:01:04.939 align:start position:0% comes to interacting with blockchains 90%<00:01:03.239> of<00:01:03.329> time<00:01:03.449> you're<00:01:03.629> using<00:01:03.780> javascript<00:01:04.110> so 00:01:04.939 --> 00:01:04.949 align:start position:0% 90% of time you're using javascript so 00:01:04.949 --> 00:01:06.680 align:start position:0% 90% of time you're using javascript so we<00:01:05.370> actually<00:01:05.549> we're<00:01:05.940> gonna<00:01:06.060> need<00:01:06.270> the<00:01:06.360> support 00:01:06.680 --> 00:01:06.690 align:start position:0% we actually we're gonna need the support 00:01:06.690 --> 00:01:10.190 align:start position:0% we actually we're gonna need the support there<00:01:07.040> and<00:01:08.149> basically<00:01:09.149> some<00:01:09.570> of<00:01:09.689> our<00:01:09.810> focuses 00:01:10.190 --> 00:01:10.200 align:start position:0% there and basically some of our focuses 00:01:10.200 --> 00:01:13.639 align:start position:0% there and basically some of our focuses are<00:01:10.469> on<00:01:10.590> like<00:01:10.829> clients<00:01:11.250> the<00:01:11.759> beacon<00:01:12.439> our<00:01:13.439> main 00:01:13.639 --> 00:01:13.649 align:start position:0% are on like clients the beacon our main 00:01:13.649 --> 00:01:15.230 align:start position:0% are on like clients the beacon our main focuses<00:01:14.009> are<00:01:14.130> on<00:01:14.219> a<00:01:14.520> beacon<00:01:14.939> chain<00:01:15.090> of<00:01:15.210> a 00:01:15.230 --> 00:01:15.240 align:start position:0% focuses are on a beacon chain of a 00:01:15.240 --> 00:01:17.510 align:start position:0% focuses are on a beacon chain of a foundation<00:01:15.630> like<00:01:16.200> client<00:01:16.590> implementation 00:01:17.510 --> 00:01:17.520 align:start position:0% foundation like client implementation 00:01:17.520 --> 00:01:19.340 align:start position:0% foundation like client implementation which<00:01:18.299> came<00:01:18.479> and<00:01:18.630> had<00:01:18.719> a<00:01:18.750> really<00:01:18.960> good<00:01:19.049> talk<00:01:19.170> on 00:01:19.340 --> 00:01:19.350 align:start position:0% which came and had a really good talk on 00:01:19.350 --> 00:01:20.450 align:start position:0% which came and had a really good talk on yesterday<00:01:19.770> and<00:01:19.890> how<00:01:20.100> they<00:01:20.219> advise<00:01:20.430> checking 00:01:20.450 --> 00:01:20.460 align:start position:0% yesterday and how they advise checking 00:01:20.460 --> 00:01:22.760 align:start position:0% yesterday and how they advise checking out<00:01:20.850> the<00:01:20.939> videos<00:01:21.210> and<00:01:21.390> slides 00:01:22.760 --> 00:01:22.770 align:start position:0% out the videos and slides 00:01:22.770 --> 00:01:24.950 align:start position:0% out the videos and slides and<00:01:23.039> as<00:01:23.430> well<00:01:23.549> as<00:01:23.640> developer<00:01:24.329> tooling<00:01:24.570> because 00:01:24.950 --> 00:01:24.960 align:start position:0% and as well as developer tooling because 00:01:24.960 --> 00:01:26.810 align:start position:0% and as well as developer tooling because naturally<00:01:25.469> you<00:01:25.829> know<00:01:25.950> as<00:01:26.189> i<00:01:26.340> said<00:01:26.520> we're<00:01:26.729> gonna 00:01:26.810 --> 00:01:26.820 align:start position:0% naturally you know as i said we're gonna 00:01:26.820 --> 00:01:28.999 align:start position:0% naturally you know as i said we're gonna have<00:01:26.939> to<00:01:27.000> interact<00:01:27.180> somehow<00:01:27.689> and<00:01:27.899> web<00:01:28.770> sites 00:01:28.999 --> 00:01:29.009 align:start position:0% have to interact somehow and web sites 00:01:29.009 --> 00:01:34.490 align:start position:0% have to interact somehow and web sites mainly<00:01:29.399> do<00:01:29.490> it<00:01:29.640> do<00:01:30.090> javascript<00:01:31.460> so<00:01:33.320> my<00:01:34.320> agenda 00:01:34.490 --> 00:01:34.500 align:start position:0% mainly do it do javascript so my agenda 00:01:34.500 --> 00:01:36.469 align:start position:0% mainly do it do javascript so my agenda is<00:01:34.619> really<00:01:34.829> simple<00:01:35.189> today<00:01:35.429> we're<00:01:36.210> gonna<00:01:36.329> look 00:01:36.469 --> 00:01:36.479 align:start position:0% is really simple today we're gonna look 00:01:36.479 --> 00:01:38.359 align:start position:0% is really simple today we're gonna look at<00:01:36.600> like<00:01:36.780> where<00:01:36.960> we<00:01:37.079> are<00:01:37.109> now<00:01:37.320> and<00:01:37.560> then<00:01:38.100> how 00:01:38.359 --> 00:01:38.369 align:start position:0% at like where we are now and then how 00:01:38.369 --> 00:01:40.910 align:start position:0% at like where we are now and then how we're<00:01:38.820> gonna<00:01:38.909> try<00:01:39.539> and<00:01:39.899> you<00:01:40.409> know<00:01:40.439> do<00:01:40.890> a 00:01:40.910 --> 00:01:40.920 align:start position:0% we're gonna try and you know do a 00:01:40.920 --> 00:01:42.410 align:start position:0% we're gonna try and you know do a migration<00:01:41.310> some<00:01:41.609> sort<00:01:41.759> of<00:01:41.789> a<00:01:41.850> migration<00:01:42.149> path 00:01:42.410 --> 00:01:42.420 align:start position:0% migration some sort of a migration path 00:01:42.420 --> 00:01:44.330 align:start position:0% migration some sort of a migration path that<00:01:42.600> makes<00:01:42.750> sense<00:01:42.990> so<00:01:43.649> that<00:01:43.829> you<00:01:44.219> know 00:01:44.330 --> 00:01:44.340 align:start position:0% that makes sense so that you know 00:01:44.340 --> 00:01:46.279 align:start position:0% that makes sense so that you know everybody<00:01:44.789> working<00:01:45.149> really<00:01:45.750> hard<00:01:45.840> unlike 00:01:46.279 --> 00:01:46.289 align:start position:0% everybody working really hard unlike 00:01:46.289 --> 00:01:47.719 align:start position:0% everybody working really hard unlike their<00:01:46.500> tool<00:01:46.649> sets<00:01:46.920> don't<00:01:47.159> have<00:01:47.369> to<00:01:47.490> rewrite 00:01:47.719 --> 00:01:47.729 align:start position:0% their tool sets don't have to rewrite 00:01:47.729 --> 00:01:51.200 align:start position:0% their tool sets don't have to rewrite everything<00:01:47.969> cuz<00:01:48.450> ode<00:01:49.229> suck<00:01:49.579> and<00:01:50.579> a<00:01:51.030> lot<00:01:51.179> of 00:01:51.200 --> 00:01:51.210 align:start position:0% everything cuz ode suck and a lot of 00:01:51.210 --> 00:01:54.319 align:start position:0% everything cuz ode suck and a lot of waste<00:01:51.420> of<00:01:51.539> time<00:01:51.689> so<00:01:52.729> basically<00:01:53.729> like<00:01:53.969> where 00:01:54.319 --> 00:01:54.329 align:start position:0% waste of time so basically like where 00:01:54.329 --> 00:01:55.730 align:start position:0% waste of time so basically like where are<00:01:54.450> we<00:01:54.539> are<00:01:54.630> now<00:01:54.780> that<00:01:55.079> this<00:01:55.229> slide<00:01:55.409> was<00:01:55.590> so 00:01:55.730 --> 00:01:55.740 align:start position:0% are we are now that this slide was so 00:01:55.740 --> 00:01:57.319 align:start position:0% are we are now that this slide was so hard<00:01:55.920> to<00:01:55.950> make<00:01:56.039> by<00:01:56.310> the<00:01:56.369> way<00:01:56.520> like<00:01:56.759> there's<00:01:57.030> way 00:01:57.319 --> 00:01:57.329 align:start position:0% hard to make by the way like there's way 00:01:57.329 --> 00:01:59.719 align:start position:0% hard to make by the way like there's way too<00:01:57.390> many<00:01:57.689> like<00:01:58.320> teams<00:01:58.829> out<00:01:59.039> there<00:01:59.100> and<00:01:59.429> if<00:01:59.609> I 00:01:59.719 --> 00:01:59.729 align:start position:0% too many like teams out there and if I 00:01:59.729 --> 00:02:01.249 align:start position:0% too many like teams out there and if I didn't<00:01:59.939> add<00:02:00.149> your<00:02:00.359> stuff<00:02:00.539> I'm<00:02:00.659> sorry<00:02:00.869> this<00:02:01.079> is 00:02:01.249 --> 00:02:01.259 align:start position:0% didn't add your stuff I'm sorry this is 00:02:01.259 --> 00:02:03.669 align:start position:0% didn't add your stuff I'm sorry this is just<00:02:01.439> like<00:02:01.590> what<00:02:01.799> I<00:02:01.829> typically<00:02:02.429> interact<00:02:02.850> with 00:02:03.669 --> 00:02:03.679 align:start position:0% just like what I typically interact with 00:02:03.679 --> 00:02:06.289 align:start position:0% just like what I typically interact with but<00:02:04.679> I<00:02:04.950> mean<00:02:05.249> we<00:02:05.369> have<00:02:05.460> a<00:02:05.490> lot<00:02:05.520> of<00:02:05.819> a<00:02:05.850> whole<00:02:05.880> vast 00:02:06.289 --> 00:02:06.299 align:start position:0% but I mean we have a lot of a whole vast 00:02:06.299 --> 00:02:09.680 align:start position:0% but I mean we have a lot of a whole vast type<00:02:07.049> of<00:02:07.819> tooling<00:02:08.819> that<00:02:08.940> exists<00:02:09.240> right<00:02:09.330> now<00:02:09.390> a 00:02:09.680 --> 00:02:09.690 align:start position:0% type of tooling that exists right now a 00:02:09.690 --> 00:02:11.720 align:start position:0% type of tooling that exists right now a lot<00:02:10.170> of<00:02:10.200> it<00:02:10.410> we<00:02:10.560> have<00:02:10.679> providers<00:02:10.979> like<00:02:11.520> what 00:02:11.720 --> 00:02:11.730 align:start position:0% lot of it we have providers like what 00:02:11.730 --> 00:02:14.600 align:start position:0% lot of it we have providers like what 3GS<00:02:12.180> ethers<00:02:12.480> j/s<00:02:13.160> development<00:02:14.160> related<00:02:14.430> stuff 00:02:14.600 --> 00:02:14.610 align:start position:0% 3GS ethers j/s development related stuff 00:02:14.610 --> 00:02:17.510 align:start position:0% 3GS ethers j/s development related stuff like<00:02:14.760> truffle<00:02:15.120> ganache<00:02:15.450> soul<00:02:15.840> CJ<00:02:16.260> s 00:02:17.510 --> 00:02:17.520 align:start position:0% like truffle ganache soul CJ s 00:02:17.520 --> 00:02:20.690 align:start position:0% like truffle ganache soul CJ s you<00:02:18.180> know<00:02:18.270> wallets<00:02:18.780> that<00:02:19.320> do<00:02:20.070> a<00:02:20.100> lot<00:02:20.340> of<00:02:20.370> like 00:02:20.690 --> 00:02:20.700 align:start position:0% you know wallets that do a lot of like 00:02:20.700 --> 00:02:22.550 align:start position:0% you know wallets that do a lot of like the<00:02:21.390> hard<00:02:21.570> work<00:02:21.750> for<00:02:21.780> everybody<00:02:22.170> and<00:02:22.380> they 00:02:22.550 --> 00:02:22.560 align:start position:0% the hard work for everybody and they 00:02:22.560 --> 00:02:23.600 align:start position:0% the hard work for everybody and they don't<00:02:22.740> really<00:02:22.830> realize<00:02:22.920> what<00:02:23.310> they're<00:02:23.430> doing 00:02:23.600 --> 00:02:23.610 align:start position:0% don't really realize what they're doing 00:02:23.610 --> 00:02:25.820 align:start position:0% don't really realize what they're doing in<00:02:23.700> behind<00:02:24.000> such<00:02:24.720> as<00:02:24.840> like<00:02:25.050> well<00:02:25.260> connect<00:02:25.590> meta 00:02:25.820 --> 00:02:25.830 align:start position:0% in behind such as like well connect meta 00:02:25.830 --> 00:02:29.870 align:start position:0% in behind such as like well connect meta mask<00:02:26.040> frame<00:02:26.720> so<00:02:27.720> many<00:02:27.900> more<00:02:28.670> really<00:02:29.670> helpful 00:02:29.870 --> 00:02:29.880 align:start position:0% mask frame so many more really helpful 00:02:29.880 --> 00:02:33.020 align:start position:0% mask frame so many more really helpful debugging<00:02:30.240> tools<00:02:30.450> like<00:02:30.690> EVM<00:02:30.990> lab<00:02:31.280> and<00:02:32.280> some<00:02:32.970> of 00:02:33.020 --> 00:02:33.030 align:start position:0% debugging tools like EVM lab and some of 00:02:33.030 --> 00:02:34.820 align:start position:0% debugging tools like EVM lab and some of you<00:02:33.720> might<00:02:33.870> not<00:02:33.990> know<00:02:34.050> what<00:02:34.260> it<00:02:34.320> is<00:02:34.470> but<00:02:34.650> it's 00:02:34.820 --> 00:02:34.830 align:start position:0% you might not know what it is but it's 00:02:34.830 --> 00:02:36.530 align:start position:0% you might not know what it is but it's like<00:02:34.890> helps<00:02:35.220> you<00:02:35.280> really<00:02:35.550> like<00:02:35.700> dive<00:02:36.090> deep<00:02:36.390> and 00:02:36.530 --> 00:02:36.540 align:start position:0% like helps you really like dive deep and 00:02:36.540 --> 00:02:37.880 align:start position:0% like helps you really like dive deep and is<00:02:36.690> seeing<00:02:36.840> what's<00:02:37.020> going<00:02:37.170> on<00:02:37.350> like<00:02:37.620> within 00:02:37.880 --> 00:02:37.890 align:start position:0% is seeing what's going on like within 00:02:37.890 --> 00:02:39.290 align:start position:0% is seeing what's going on like within the<00:02:38.010> EVM<00:02:38.340> while<00:02:38.490> you're<00:02:38.610> running<00:02:38.670> executing 00:02:39.290 --> 00:02:39.300 align:start position:0% the EVM while you're running executing 00:02:39.300 --> 00:02:42.230 align:start position:0% the EVM while you're running executing your<00:02:39.390> smart<00:02:39.570> contracts<00:02:40.700> and<00:02:41.700> now<00:02:41.850> I<00:02:41.880> see<00:02:42.120> there 00:02:42.230 --> 00:02:42.240 align:start position:0% your smart contracts and now I see there 00:02:42.240 --> 00:02:43.550 align:start position:0% your smart contracts and now I see there we<00:02:42.300> got<00:02:42.420> like<00:02:42.570> really<00:02:42.720> great<00:02:42.900> websites<00:02:43.320> that 00:02:43.550 --> 00:02:43.560 align:start position:0% we got like really great websites that 00:02:43.560 --> 00:02:44.870 align:start position:0% we got like really great websites that like<00:02:43.770> help<00:02:43.980> you<00:02:44.070> build<00:02:44.190> some<00:02:44.310> our<00:02:44.460> contracts 00:02:44.870 --> 00:02:44.880 align:start position:0% like help you build some our contracts 00:02:44.880 --> 00:02:47.180 align:start position:0% like help you build some our contracts like<00:02:45.000> play<00:02:45.270> and<00:02:45.510> remix<00:02:45.840> that<00:02:46.650> are<00:02:46.800> integral 00:02:47.180 --> 00:02:47.190 align:start position:0% like play and remix that are integral 00:02:47.190 --> 00:02:49.190 align:start position:0% like play and remix that are integral and<00:02:47.400> one<00:02:48.240> thing<00:02:48.420> to<00:02:48.600> note<00:02:48.750> with<00:02:48.870> like<00:02:49.020> just 00:02:49.190 --> 00:02:49.200 align:start position:0% and one thing to note with like just 00:02:49.200 --> 00:02:50.870 align:start position:0% and one thing to note with like just about<00:02:49.260> all<00:02:49.500> these<00:02:49.770> things<00:02:50.340> I've<00:02:50.550> listed<00:02:50.730> here 00:02:50.870 --> 00:02:50.880 align:start position:0% about all these things I've listed here 00:02:50.880 --> 00:02:55.520 align:start position:0% about all these things I've listed here I'm<00:02:51.810> pretty<00:02:52.230> sure<00:02:52.560> they<00:02:53.130> all<00:02:54.050> use<00:02:55.050> JavaScript 00:02:55.520 --> 00:02:55.530 align:start position:0% I'm pretty sure they all use JavaScript 00:02:55.530 --> 00:02:58.040 align:start position:0% I'm pretty sure they all use JavaScript right<00:02:55.860> now<00:02:56.040> and<00:02:56.970> it's<00:02:57.210> like<00:02:57.360> very<00:02:57.390> deeply 00:02:58.040 --> 00:02:58.050 align:start position:0% right now and it's like very deeply 00:02:58.050 --> 00:02:59.900 align:start position:0% right now and it's like very deeply nested<00:02:58.230> in<00:02:58.500> them<00:02:58.650> for<00:02:59.010> how<00:02:59.430> they<00:02:59.580> make<00:02:59.760> their 00:02:59.900 --> 00:02:59.910 align:start position:0% nested in them for how they make their 00:02:59.910 --> 00:03:01.370 align:start position:0% nested in them for how they make their connections<00:03:00.330> and<00:03:00.540> actually<00:03:00.870> interact<00:03:01.050> with 00:03:01.370 --> 00:03:01.380 align:start position:0% connections and actually interact with 00:03:01.380 --> 00:03:05.540 align:start position:0% connections and actually interact with the<00:03:02.220> theorem<00:03:02.580> so<00:03:03.210> moving<00:03:04.140> forward<00:03:04.430> you<00:03:05.430> know 00:03:05.540 --> 00:03:05.550 align:start position:0% the theorem so moving forward you know 00:03:05.550 --> 00:03:07.520 align:start position:0% the theorem so moving forward you know with<00:03:05.700> theorem<00:03:05.970> 2.0<00:03:06.450> there's<00:03:06.900> one<00:03:07.140> big<00:03:07.320> thing 00:03:07.520 --> 00:03:07.530 align:start position:0% with theorem 2.0 there's one big thing 00:03:07.530 --> 00:03:09.350 align:start position:0% with theorem 2.0 there's one big thing that<00:03:07.830> we<00:03:07.980> have<00:03:08.100> to<00:03:08.220> note<00:03:08.400> and<00:03:08.670> it's<00:03:08.910> that<00:03:09.120> you 00:03:09.350 --> 00:03:09.360 align:start position:0% that we have to note and it's that you 00:03:09.360 --> 00:03:12.530 align:start position:0% that we have to note and it's that you know<00:03:09.510> our<00:03:09.720> api's<00:03:10.140> are<00:03:10.710> not<00:03:11.190> at<00:03:11.550> all<00:03:11.910> equivalent 00:03:12.530 --> 00:03:12.540 align:start position:0% know our api's are not at all equivalent 00:03:12.540 --> 00:03:15.440 align:start position:0% know our api's are not at all equivalent like<00:03:13.070> zero<00:03:14.070> like<00:03:14.280> the<00:03:14.430> compatibility<00:03:15.060> is<00:03:15.120> like 00:03:15.440 --> 00:03:15.450 align:start position:0% like zero like the compatibility is like 00:03:15.450 --> 00:03:17.720 align:start position:0% like zero like the compatibility is like next<00:03:15.870> to<00:03:15.960> nothing<00:03:16.380> which<00:03:17.280> means<00:03:17.520> that 00:03:17.720 --> 00:03:17.730 align:start position:0% next to nothing which means that 00:03:17.730 --> 00:03:20.000 align:start position:0% next to nothing which means that everything<00:03:17.970> we've<00:03:18.210> just<00:03:18.240> listed<00:03:18.720> here<00:03:19.010> would 00:03:20.000 --> 00:03:20.010 align:start position:0% everything we've just listed here would 00:03:20.010 --> 00:03:21.740 align:start position:0% everything we've just listed here would not<00:03:20.190> work<00:03:20.460> right<00:03:21.030> out<00:03:21.150> of<00:03:21.180> the<00:03:21.300> gate<00:03:21.450> it 00:03:21.740 --> 00:03:21.750 align:start position:0% not work right out of the gate it 00:03:21.750 --> 00:03:22.940 align:start position:0% not work right out of the gate it actually<00:03:22.110> takes<00:03:22.290> quite<00:03:22.440> a<00:03:22.530> lot<00:03:22.710> of<00:03:22.830> an 00:03:22.940 --> 00:03:22.950 align:start position:0% actually takes quite a lot of an 00:03:22.950 --> 00:03:23.480 align:start position:0% actually takes quite a lot of an overhaul 00:03:23.480 --> 00:03:23.490 align:start position:0% overhaul 00:03:23.490 --> 00:03:26.570 align:start position:0% overhaul borderline<00:03:23.940> to<00:03:24.060> rewrite<00:03:24.360> if<00:03:25.230> we<00:03:25.560> didn't<00:03:26.040> do 00:03:26.570 --> 00:03:26.580 align:start position:0% borderline to rewrite if we didn't do 00:03:26.580 --> 00:03:28.220 align:start position:0% borderline to rewrite if we didn't do something<00:03:26.610> to<00:03:26.970> help<00:03:27.120> better<00:03:27.720> support<00:03:28.200> a 00:03:28.220 --> 00:03:28.230 align:start position:0% something to help better support a 00:03:28.230 --> 00:03:31.160 align:start position:0% something to help better support a transition<00:03:28.680> period<00:03:29.840> so<00:03:30.840> that's<00:03:30.960> what<00:03:31.080> I've 00:03:31.160 --> 00:03:31.170 align:start position:0% transition period so that's what I've 00:03:31.170 --> 00:03:33.200 align:start position:0% transition period so that's what I've been<00:03:31.200> focusing<00:03:31.380> on<00:03:31.650> personally<00:03:32.070> so<00:03:32.250> I've<00:03:32.730> been 00:03:33.200 --> 00:03:33.210 align:start position:0% been focusing on personally so I've been 00:03:33.210 --> 00:03:35.060 align:start position:0% been focusing on personally so I've been spending<00:03:33.420> a<00:03:33.570> lot<00:03:33.660> of<00:03:33.720> time<00:03:33.810> personally<00:03:34.350> on<00:03:34.530> you 00:03:35.060 --> 00:03:35.070 align:start position:0% spending a lot of time personally on you 00:03:35.070 --> 00:03:37.490 align:start position:0% spending a lot of time personally on you know<00:03:35.190> how<00:03:35.400> can<00:03:35.790> we<00:03:35.820> make<00:03:36.300> this<00:03:36.690> smoother 00:03:37.490 --> 00:03:37.500 align:start position:0% know how can we make this smoother 00:03:37.500 --> 00:03:40.450 align:start position:0% know how can we make this smoother transition<00:03:38.010> for<00:03:38.580> teams<00:03:39.510> who<00:03:39.690> are<00:03:40.020> building 00:03:40.450 --> 00:03:40.460 align:start position:0% transition for teams who are building 00:03:40.460 --> 00:03:43.400 align:start position:0% transition for teams who are building quality<00:03:41.460> tools<00:03:41.820> that<00:03:42.120> are<00:03:42.210> used<00:03:42.330> every<00:03:42.600> day<00:03:42.630> I 00:03:43.400 --> 00:03:43.410 align:start position:0% quality tools that are used every day I 00:03:43.410 --> 00:03:45.800 align:start position:0% quality tools that are used every day I mean<00:03:44.130> like<00:03:44.310> I<00:03:44.400> think<00:03:44.430> ethers<00:03:44.970> alone<00:03:45.330> does<00:03:45.660> like 00:03:45.800 --> 00:03:45.810 align:start position:0% mean like I think ethers alone does like 00:03:45.810 --> 00:03:48.910 align:start position:0% mean like I think ethers alone does like 13,000<00:03:46.680> thousand<00:03:47.520> downloads<00:03:47.940> on<00:03:48.270> the<00:03:48.390> little 00:03:48.910 --> 00:03:48.920 align:start position:0% 13,000 thousand downloads on the little 00:03:48.920 --> 00:03:51.400 align:start position:0% 13,000 thousand downloads on the little used<00:03:49.920> packages<00:03:50.460> on<00:03:50.580> like<00:03:50.730> the<00:03:50.850> github 00:03:51.400 --> 00:03:51.410 align:start position:0% used packages on like the github 00:03:51.410 --> 00:03:53.750 align:start position:0% used packages on like the github downloads<00:03:52.410> thing<00:03:52.530> which<00:03:52.680> is<00:03:52.830> like<00:03:52.980> that's<00:03:53.700> a 00:03:53.750 --> 00:03:53.760 align:start position:0% downloads thing which is like that's a 00:03:53.760 --> 00:03:55.310 align:start position:0% downloads thing which is like that's a lot<00:03:53.880> of<00:03:53.910> people<00:03:54.150> like<00:03:54.270> depending<00:03:54.630> on<00:03:54.750> you<00:03:55.290> know 00:03:55.310 --> 00:03:55.320 align:start position:0% lot of people like depending on you know 00:03:55.320 --> 00:03:57.740 align:start position:0% lot of people like depending on you know one<00:03:55.650> small<00:03:56.040> piece<00:03:56.190> of<00:03:56.340> software<00:03:56.640> within<00:03:57.450> the 00:03:57.740 --> 00:03:57.750 align:start position:0% one small piece of software within the 00:03:57.750 --> 00:04:01.370 align:start position:0% one small piece of software within the larger<00:03:58.200> context<00:03:58.590> of<00:03:58.680> the<00:03:58.740> ecosystem<00:03:59.310> so<00:04:00.380> just 00:04:01.370 --> 00:04:01.380 align:start position:0% larger context of the ecosystem so just 00:04:01.380 --> 00:04:03.380 align:start position:0% larger context of the ecosystem so just like<00:04:01.740> to<00:04:01.920> highlight<00:04:02.190> the<00:04:02.550> example<00:04:03.000> you<00:04:03.270> know 00:04:03.380 --> 00:04:03.390 align:start position:0% like to highlight the example you know 00:04:03.390 --> 00:04:07.540 align:start position:0% like to highlight the example you know we<00:04:03.660> have<00:04:03.900> a<00:04:03.930> block<00:04:04.380> in<00:04:05.450> you<00:04:06.450> know<00:04:06.540> eath<00:04:06.750> lon<00:04:06.990> and 00:04:07.540 --> 00:04:07.550 align:start position:0% we have a block in you know eath lon and 00:04:07.550 --> 00:04:10.220 align:start position:0% we have a block in you know eath lon and we<00:04:08.550> don't<00:04:08.730> really<00:04:09.000> have<00:04:09.120> a<00:04:09.630> one-to-one 00:04:10.220 --> 00:04:10.230 align:start position:0% we don't really have a one-to-one 00:04:10.230 --> 00:04:11.810 align:start position:0% we don't really have a one-to-one equivalent<00:04:10.830> because<00:04:10.950> we<00:04:11.130> have<00:04:11.310> two<00:04:11.490> types<00:04:11.700> of 00:04:11.810 --> 00:04:11.820 align:start position:0% equivalent because we have two types of 00:04:11.820 --> 00:04:14.449 align:start position:0% equivalent because we have two types of blocks<00:04:12.060> and<00:04:12.300> eath<00:04:12.450> too<00:04:13.040> so<00:04:14.040> that's<00:04:14.190> a<00:04:14.250> problem 00:04:14.449 --> 00:04:14.459 align:start position:0% blocks and eath too so that's a problem 00:04:14.459 --> 00:04:16.849 align:start position:0% blocks and eath too so that's a problem we<00:04:15.000> also<00:04:15.120> have<00:04:15.360> shards<00:04:15.690> shards<00:04:16.350> don't<00:04:16.560> exist 00:04:16.849 --> 00:04:16.859 align:start position:0% we also have shards shards don't exist 00:04:16.859 --> 00:04:18.860 align:start position:0% we also have shards shards don't exist so<00:04:16.950> your<00:04:17.160> eighth<00:04:17.340> one<00:04:17.549> I<00:04:17.760> don't<00:04:18.330> know<00:04:18.540> what<00:04:18.750> you 00:04:18.860 --> 00:04:18.870 align:start position:0% so your eighth one I don't know what you 00:04:18.870 --> 00:04:20.449 align:start position:0% so your eighth one I don't know what you would<00:04:18.989> what<00:04:19.380> you<00:04:19.410> do<00:04:19.709> there<00:04:19.890> you<00:04:20.100> know<00:04:20.220> like 00:04:20.449 --> 00:04:20.459 align:start position:0% would what you do there you know like 00:04:20.459 --> 00:04:23.270 align:start position:0% would what you do there you know like you<00:04:20.670> what<00:04:21.600> would<00:04:21.840> a<00:04:22.109> Thursday<00:04:22.770> when<00:04:22.950> you<00:04:23.070> say 00:04:23.270 --> 00:04:23.280 align:start position:0% you what would a Thursday when you say 00:04:23.280 --> 00:04:27.020 align:start position:0% you what would a Thursday when you say get<00:04:23.550> block<00:04:24.919> where<00:04:25.919> do<00:04:26.040> you<00:04:26.130> go<00:04:26.310> you<00:04:26.910> know 00:04:27.020 --> 00:04:27.030 align:start position:0% get block where do you go you know 00:04:27.030 --> 00:04:29.330 align:start position:0% get block where do you go you know there's<00:04:27.419> two<00:04:27.600> blocks<00:04:27.840> and<00:04:28.770> there's<00:04:28.979> also<00:04:29.130> many 00:04:29.330 --> 00:04:29.340 align:start position:0% there's two blocks and there's also many 00:04:29.340 --> 00:04:31.279 align:start position:0% there's two blocks and there's also many shards<00:04:29.760> so 00:04:31.279 --> 00:04:31.289 align:start position:0% shards so 00:04:31.289 --> 00:04:32.420 align:start position:0% shards so and<00:04:31.349> then<00:04:31.439> we<00:04:31.529> have<00:04:31.619> execution<00:04:32.069> environments 00:04:32.420 --> 00:04:32.430 align:start position:0% and then we have execution environments 00:04:32.430 --> 00:04:33.439 align:start position:0% and then we have execution environments I<00:04:32.460> don't<00:04:32.610> even<00:04:32.669> want<00:04:32.849> to<00:04:32.879> touch<00:04:32.999> that<00:04:33.059> and<00:04:33.389> I 00:04:33.439 --> 00:04:33.449 align:start position:0% I don't even want to touch that and I 00:04:33.449 --> 00:04:35.510 align:start position:0% I don't even want to touch that and I won't<00:04:33.599> be<00:04:33.749> touching<00:04:33.960> today<00:04:34.439> is<00:04:34.649> like<00:04:34.860> that's 00:04:35.510 --> 00:04:35.520 align:start position:0% won't be touching today is like that's 00:04:35.520 --> 00:04:38.779 align:start position:0% won't be touching today is like that's something<00:04:35.729> else<00:04:36.680> but<00:04:37.680> to<00:04:38.189> highlight<00:04:38.339> my<00:04:38.520> point 00:04:38.779 --> 00:04:38.789 align:start position:0% something else but to highlight my point 00:04:38.789 --> 00:04:39.649 align:start position:0% something else but to highlight my point is<00:04:38.909> like<00:04:39.029> there's<00:04:39.210> so<00:04:39.270> many<00:04:39.360> discrepancies 00:04:39.649 --> 00:04:39.659 align:start position:0% is like there's so many discrepancies 00:04:39.659 --> 00:04:41.899 align:start position:0% is like there's so many discrepancies that<00:04:40.229> the<00:04:40.589> api's<00:04:40.889> will<00:04:41.219> never<00:04:41.369> line<00:04:41.550> up<00:04:41.729> and 00:04:41.899 --> 00:04:41.909 align:start position:0% that the api's will never line up and 00:04:41.909 --> 00:04:43.249 align:start position:0% that the api's will never line up and they<00:04:42.059> won't<00:04:42.270> but<00:04:42.719> there's<00:04:42.899> some<00:04:43.020> things<00:04:43.199> we 00:04:43.249 --> 00:04:43.259 align:start position:0% they won't but there's some things we 00:04:43.259 --> 00:04:44.749 align:start position:0% they won't but there's some things we can<00:04:43.439> do<00:04:43.559> and<00:04:43.770> there's<00:04:44.099> some<00:04:44.219> clever<00:04:44.369> things<00:04:44.490> we 00:04:44.749 --> 00:04:44.759 align:start position:0% can do and there's some clever things we 00:04:44.759 --> 00:04:47.899 align:start position:0% can do and there's some clever things we can<00:04:44.909> do<00:04:45.499> so<00:04:46.669> something<00:04:47.669> I've<00:04:47.789> been<00:04:47.819> thinking 00:04:47.899 --> 00:04:47.909 align:start position:0% can do so something I've been thinking 00:04:47.909 --> 00:04:49.249 align:start position:0% can do so something I've been thinking about<00:04:48.149> as<00:04:48.330> an<00:04:48.449> interim<00:04:48.779> solution<00:04:48.899> and 00:04:49.249 --> 00:04:49.259 align:start position:0% about as an interim solution and 00:04:49.259 --> 00:04:51.049 align:start position:0% about as an interim solution and obviously<00:04:49.499> this<00:04:49.589> is<00:04:49.710> not<00:04:49.770> great<00:04:50.039> you<00:04:50.789> know<00:04:50.909> the 00:04:51.049 --> 00:04:51.059 align:start position:0% obviously this is not great you know the 00:04:51.059 --> 00:04:52.279 align:start position:0% obviously this is not great you know the more<00:04:51.210> I've<00:04:51.449> been<00:04:51.569> talking<00:04:51.809> a<00:04:51.869> lot<00:04:51.930> of<00:04:52.080> teams 00:04:52.279 --> 00:04:52.289 align:start position:0% more I've been talking a lot of teams 00:04:52.289 --> 00:04:54.529 align:start position:0% more I've been talking a lot of teams especially<00:04:52.949> truffle<00:04:53.460> has<00:04:53.580> been<00:04:53.759> like<00:04:53.909> no<00:04:54.330> they 00:04:54.529 --> 00:04:54.539 align:start position:0% especially truffle has been like no they 00:04:54.539 --> 00:04:56.540 align:start position:0% especially truffle has been like no they want<00:04:54.749> like<00:04:54.899> they're<00:04:55.740> happy<00:04:56.099> to<00:04:56.219> do<00:04:56.339> like<00:04:56.520> a 00:04:56.540 --> 00:04:56.550 align:start position:0% want like they're happy to do like a 00:04:56.550 --> 00:04:59.869 align:start position:0% want like they're happy to do like a like<00:04:56.939> a<00:04:56.999> proper<00:04:57.800> baked<00:04:58.800> in<00:04:58.979> solution<00:04:59.369> but 00:04:59.869 --> 00:04:59.879 align:start position:0% like a proper baked in solution but 00:04:59.879 --> 00:05:01.999 align:start position:0% like a proper baked in solution but something<00:05:00.149> interim<00:05:00.539> that<00:05:00.569> we<00:05:00.779> could<00:05:00.930> do<00:05:01.080> you 00:05:01.999 --> 00:05:02.009 align:start position:0% something interim that we could do you 00:05:02.009 --> 00:05:03.350 align:start position:0% something interim that we could do you know<00:05:02.159> you<00:05:02.339> know<00:05:02.460> with<00:05:02.669> ether<00:05:03.029> is<00:05:03.089> what<00:05:03.270> we 00:05:03.350 --> 00:05:03.360 align:start position:0% know you know with ether is what we 00:05:03.360 --> 00:05:05.149 align:start position:0% know you know with ether is what we typically<00:05:03.659> do<00:05:03.809> is<00:05:03.839> you<00:05:04.020> pass<00:05:04.499> in<00:05:04.709> you<00:05:04.889> know<00:05:05.009> the 00:05:05.149 --> 00:05:05.159 align:start position:0% typically do is you pass in you know the 00:05:05.159 --> 00:05:06.589 align:start position:0% typically do is you pass in you know the test<00:05:05.369> net<00:05:05.520> or<00:05:05.729> the<00:05:05.849> network<00:05:06.029> you<00:05:06.240> want<00:05:06.360> to<00:05:06.419> use 00:05:06.589 --> 00:05:06.599 align:start position:0% test net or the network you want to use 00:05:06.599 --> 00:05:08.389 align:start position:0% test net or the network you want to use and<00:05:07.469> what<00:05:07.619> we<00:05:07.709> can<00:05:07.830> actually<00:05:07.949> do<00:05:08.129> is<00:05:08.189> we<00:05:08.279> can 00:05:08.389 --> 00:05:08.399 align:start position:0% and what we can actually do is we can 00:05:08.399 --> 00:05:10.429 align:start position:0% and what we can actually do is we can create<00:05:08.520> about<00:05:08.759> a<00:05:08.819> like<00:05:09.449> an<00:05:09.539> adapter<00:05:09.990> sort<00:05:10.349> of 00:05:10.429 --> 00:05:10.439 align:start position:0% create about a like an adapter sort of 00:05:10.439 --> 00:05:12.350 align:start position:0% create about a like an adapter sort of like<00:05:10.559> that<00:05:11.009> sits<00:05:11.309> right<00:05:11.520> on<00:05:11.879> in<00:05:11.999> the<00:05:12.059> outside 00:05:12.350 --> 00:05:12.360 align:start position:0% like that sits right on in the outside 00:05:12.360 --> 00:05:15.139 align:start position:0% like that sits right on in the outside and<00:05:12.539> wraps<00:05:12.869> all<00:05:13.080> the<00:05:13.169> requests<00:05:13.619> and<00:05:14.550> basically 00:05:15.139 --> 00:05:15.149 align:start position:0% and wraps all the requests and basically 00:05:15.149 --> 00:05:16.820 align:start position:0% and wraps all the requests and basically the<00:05:15.209> idea<00:05:15.389> behind<00:05:15.419> did<00:05:16.050> that<00:05:16.289> slide<00:05:16.559> getting 00:05:16.820 --> 00:05:16.830 align:start position:0% the idea behind did that slide getting 00:05:16.830 --> 00:05:18.589 align:start position:0% the idea behind did that slide getting to<00:05:16.919> know<00:05:17.039> and<00:05:17.879> basically<00:05:18.149> the<00:05:18.270> idea<00:05:18.479> behind 00:05:18.589 --> 00:05:18.599 align:start position:0% to know and basically the idea behind 00:05:18.599 --> 00:05:21.230 align:start position:0% to know and basically the idea behind that<00:05:18.779> is<00:05:18.899> something<00:05:19.860> that<00:05:20.099> we<00:05:20.490> did<00:05:20.909> a<00:05:20.939> chain 00:05:21.230 --> 00:05:21.240 align:start position:0% that is something that we did a chain 00:05:21.240 --> 00:05:23.809 align:start position:0% that is something that we did a chain safe<00:05:21.449> with<00:05:22.259> something<00:05:22.800> called<00:05:23.219> ether<00:05:23.669> meant 00:05:23.809 --> 00:05:23.819 align:start position:0% safe with something called ether meant 00:05:23.819 --> 00:05:26.989 align:start position:0% safe with something called ether meant from<00:05:24.149> the<00:05:24.270> cosmos<00:05:24.599> ecosystem<00:05:25.229> where<00:05:25.919> we<00:05:26.369> made 00:05:26.989 --> 00:05:26.999 align:start position:0% from the cosmos ecosystem where we made 00:05:26.999 --> 00:05:29.600 align:start position:0% from the cosmos ecosystem where we made the<00:05:27.119> EVM<00:05:27.449> work<00:05:27.659> on<00:05:28.259> top<00:05:28.469> at<00:05:28.619> Endermen<00:05:28.949> but 00:05:29.600 --> 00:05:29.610 align:start position:0% the EVM work on top at Endermen but 00:05:29.610 --> 00:05:31.070 align:start position:0% the EVM work on top at Endermen but naturally<00:05:30.029> they<00:05:30.180> again<00:05:30.599> it's<00:05:30.779> kind<00:05:30.959> of<00:05:30.990> a 00:05:31.070 --> 00:05:31.080 align:start position:0% naturally they again it's kind of a 00:05:31.080 --> 00:05:32.989 align:start position:0% naturally they again it's kind of a similar<00:05:31.259> situation<00:05:31.379> they<00:05:31.949> don't<00:05:31.979> line<00:05:32.430> up<00:05:32.459> but 00:05:32.989 --> 00:05:32.999 align:start position:0% similar situation they don't line up but 00:05:32.999 --> 00:05:34.040 align:start position:0% similar situation they don't line up but we<00:05:33.149> had<00:05:33.300> to<00:05:33.419> make<00:05:33.509> sure<00:05:33.659> that<00:05:33.749> all<00:05:33.959> the 00:05:34.040 --> 00:05:34.050 align:start position:0% we had to make sure that all the 00:05:34.050 --> 00:05:35.839 align:start position:0% we had to make sure that all the developer<00:05:34.529> tooling<00:05:34.860> like<00:05:35.219> worked<00:05:35.430> right<00:05:35.729> out 00:05:35.839 --> 00:05:35.849 align:start position:0% developer tooling like worked right out 00:05:35.849 --> 00:05:37.459 align:start position:0% developer tooling like worked right out of<00:05:35.879> the<00:05:36.029> gate<00:05:36.180> so<00:05:36.419> that<00:05:36.569> you<00:05:36.689> could<00:05:36.930> it<00:05:37.289> was 00:05:37.459 --> 00:05:37.469 align:start position:0% of the gate so that you could it was 00:05:37.469 --> 00:05:41.239 align:start position:0% of the gate so that you could it was like<00:05:37.620> playing<00:05:37.860> in<00:05:38.279> a<00:05:38.370> theorem<00:05:39.409> cuz<00:05:40.409> you<00:05:41.159> know 00:05:41.239 --> 00:05:41.249 align:start position:0% like playing in a theorem cuz you know 00:05:41.249 --> 00:05:44.570 align:start position:0% like playing in a theorem cuz you know otherwise<00:05:41.759> why<00:05:41.969> would<00:05:42.089> you<00:05:42.149> use<00:05:42.240> it<00:05:42.389> so<00:05:43.580> what 00:05:44.570 --> 00:05:44.580 align:start position:0% otherwise why would you use it so what 00:05:44.580 --> 00:05:46.399 align:start position:0% otherwise why would you use it so what we<00:05:44.669> did<00:05:44.819> was<00:05:44.969> we<00:05:44.999> basically<00:05:45.419> added<00:05:46.080> this<00:05:46.199> layer 00:05:46.399 --> 00:05:46.409 align:start position:0% we did was we basically added this layer 00:05:46.409 --> 00:05:48.469 align:start position:0% we did was we basically added this layer in<00:05:46.620> front<00:05:47.069> that<00:05:47.249> every<00:05:47.580> time<00:05:47.759> an<00:05:47.879> API<00:05:48.120> request 00:05:48.469 --> 00:05:48.479 align:start position:0% in front that every time an API request 00:05:48.479 --> 00:05:52.009 align:start position:0% in front that every time an API request came<00:05:48.689> into<00:05:49.129> the<00:05:50.129> EVM<00:05:50.490> or<00:05:50.789> in<00:05:51.360> this<00:05:51.539> case<00:05:51.749> it 00:05:52.009 --> 00:05:52.019 align:start position:0% came into the EVM or in this case it 00:05:52.019 --> 00:05:53.089 align:start position:0% came into the EVM or in this case it would<00:05:52.110> be<00:05:52.139> like<00:05:52.229> when<00:05:52.559> it<00:05:52.620> hits<00:05:52.769> the<00:05:52.830> beacon 00:05:53.089 --> 00:05:53.099 align:start position:0% would be like when it hits the beacon 00:05:53.099 --> 00:05:56.389 align:start position:0% would be like when it hits the beacon chain<00:05:53.309> or<00:05:53.490> AOL<00:05:54.269> whatever's<00:05:54.779> there<00:05:55.399> we're 00:05:56.389 --> 00:05:56.399 align:start position:0% chain or AOL whatever's there we're 00:05:56.399 --> 00:05:58.399 align:start position:0% chain or AOL whatever's there we're basically<00:05:56.699> looking<00:05:57.659> at<00:05:57.899> it<00:05:58.080> and<00:05:58.199> then 00:05:58.399 --> 00:05:58.409 align:start position:0% basically looking at it and then 00:05:58.409 --> 00:06:00.230 align:start position:0% basically looking at it and then translating<00:05:59.009> to<00:05:59.159> whatever<00:05:59.370> we<00:05:59.669> think<00:05:59.879> makes 00:06:00.230 --> 00:06:00.240 align:start position:0% translating to whatever we think makes 00:06:00.240 --> 00:06:03.920 align:start position:0% translating to whatever we think makes the<00:06:00.389> most<00:06:00.419> sense<00:06:01.099> from<00:06:02.099> that<00:06:02.610> side<00:06:03.419> so<00:06:03.599> we<00:06:03.809> can 00:06:03.920 --> 00:06:03.930 align:start position:0% the most sense from that side so we can 00:06:03.930 --> 00:06:05.059 align:start position:0% the most sense from that side so we can do<00:06:04.019> that<00:06:04.169> with<00:06:04.259> the<00:06:04.319> beacon<00:06:04.529> chain<00:06:04.680> right<00:06:04.830> and 00:06:05.059 --> 00:06:05.069 align:start position:0% do that with the beacon chain right and 00:06:05.069 --> 00:06:07.309 align:start position:0% do that with the beacon chain right and with<00:06:05.610> this<00:06:05.789> so<00:06:06.089> chances<00:06:06.869> are<00:06:07.019> you<00:06:07.199> have<00:06:07.289> a 00:06:07.309 --> 00:06:07.319 align:start position:0% with this so chances are you have a 00:06:07.319 --> 00:06:08.420 align:start position:0% with this so chances are you have a contract<00:06:07.740> you're<00:06:07.889> saying<00:06:08.099> hey<00:06:08.189> I<00:06:08.219> want<00:06:08.369> to 00:06:08.420 --> 00:06:08.430 align:start position:0% contract you're saying hey I want to 00:06:08.430 --> 00:06:11.209 align:start position:0% contract you're saying hey I want to look<00:06:08.490> up<00:06:08.610> this<00:06:08.729> contract<00:06:09.830> you're<00:06:10.830> probably 00:06:11.209 --> 00:06:11.219 align:start position:0% look up this contract you're probably 00:06:11.219 --> 00:06:12.499 align:start position:0% look up this contract you're probably you<00:06:11.639> have<00:06:11.729> to<00:06:11.819> get<00:06:11.909> routed<00:06:12.029> to<00:06:12.240> a<00:06:12.269> shard 00:06:12.499 --> 00:06:12.509 align:start position:0% you have to get routed to a shard 00:06:12.509 --> 00:06:14.089 align:start position:0% you have to get routed to a shard because<00:06:13.199> that's<00:06:13.349> where<00:06:13.559> your<00:06:13.709> contracts<00:06:14.069> and 00:06:14.089 --> 00:06:14.099 align:start position:0% because that's where your contracts and 00:06:14.099 --> 00:06:15.829 align:start position:0% because that's where your contracts and be<00:06:14.279> living<00:06:14.550> and<00:06:15.209> you're<00:06:15.360> gonna<00:06:15.479> have<00:06:15.599> to<00:06:15.659> you 00:06:15.829 --> 00:06:15.839 align:start position:0% be living and you're gonna have to you 00:06:15.839 --> 00:06:17.449 align:start position:0% be living and you're gonna have to you do<00:06:16.229> it<00:06:16.319> that<00:06:16.439> way<00:06:16.499> so<00:06:16.559> we<00:06:16.769> can<00:06:16.919> just<00:06:17.159> take<00:06:17.279> like 00:06:17.449 --> 00:06:17.459 align:start position:0% do it that way so we can just take like 00:06:17.459 --> 00:06:21.230 align:start position:0% do it that way so we can just take like a<00:06:17.490> generic<00:06:17.969> request<00:06:18.740> from<00:06:19.999> you<00:06:20.999> know<00:06:21.089> the 00:06:21.230 --> 00:06:21.240 align:start position:0% a generic request from you know the 00:06:21.240 --> 00:06:23.749 align:start position:0% a generic request from you know the standard<00:06:21.449> eath<00:06:21.749> one<00:06:21.990> API<00:06:22.589> and<00:06:23.039> like<00:06:23.279> rewrap<00:06:23.729> it 00:06:23.749 --> 00:06:23.759 align:start position:0% standard eath one API and like rewrap it 00:06:23.759 --> 00:06:28.129 align:start position:0% standard eath one API and like rewrap it and<00:06:24.119> pop<00:06:24.990> it<00:06:25.139> back<00:06:25.169> out<00:06:25.999> that<00:06:26.999> works<00:06:27.209> it's<00:06:28.080> not 00:06:28.129 --> 00:06:28.139 align:start position:0% and pop it back out that works it's not 00:06:28.139 --> 00:06:28.670 align:start position:0% and pop it back out that works it's not great 00:06:28.670 --> 00:06:28.680 align:start position:0% great 00:06:28.680 --> 00:06:30.769 align:start position:0% great you<00:06:29.069> know<00:06:29.189> we<00:06:29.490> that<00:06:29.669> mean<00:06:30.029> every<00:06:30.300> client<00:06:30.659> team 00:06:30.769 --> 00:06:30.779 align:start position:0% you know we that mean every client team 00:06:30.779 --> 00:06:33.049 align:start position:0% you know we that mean every client team would<00:06:30.959> have<00:06:31.110> to<00:06:31.229> go<00:06:31.349> and<00:06:31.379> adopt<00:06:32.159> this<00:06:32.369> like<00:06:33.029> a 00:06:33.049 --> 00:06:33.059 align:start position:0% would have to go and adopt this like a 00:06:33.059 --> 00:06:35.149 align:start position:0% would have to go and adopt this like a interface<00:06:33.689> sitting<00:06:34.349> in<00:06:34.409> front<00:06:34.559> of<00:06:34.800> their 00:06:35.149 --> 00:06:35.159 align:start position:0% interface sitting in front of their 00:06:35.159 --> 00:06:36.949 align:start position:0% interface sitting in front of their current<00:06:35.729> whatever<00:06:36.089> we<00:06:36.300> end<00:06:36.419> up<00:06:36.509> making<00:06:36.659> these 00:06:36.949 --> 00:06:36.959 align:start position:0% current whatever we end up making these 00:06:36.959 --> 00:06:39.109 align:start position:0% current whatever we end up making these two<00:06:37.169> API<00:06:37.409> whether<00:06:37.830> it's<00:06:38.039> Jason<00:06:38.309> or<00:06:38.399> you<00:06:39.029> know 00:06:39.109 --> 00:06:39.119 align:start position:0% two API whether it's Jason or you know 00:06:39.119 --> 00:06:40.839 align:start position:0% two API whether it's Jason or you know whatever 00:06:40.839 --> 00:06:40.849 align:start position:0% whatever 00:06:40.849 --> 00:06:43.759 align:start position:0% whatever it<00:06:41.849> does<00:06:42.060> the<00:06:42.209> job<00:06:42.539> it's<00:06:42.659> not<00:06:42.839> great<00:06:43.349> you<00:06:43.680> know 00:06:43.759 --> 00:06:43.769 align:start position:0% it does the job it's not great you know 00:06:43.769 --> 00:06:45.050 align:start position:0% it does the job it's not great you know we<00:06:43.889> could<00:06:44.069> also<00:06:44.370> integrate 00:06:45.050 --> 00:06:45.060 align:start position:0% we could also integrate 00:06:45.060 --> 00:06:46.340 align:start position:0% we could also integrate into<00:06:45.419> the<00:06:45.510> provider<00:06:45.810> so<00:06:45.960> you<00:06:46.050> know<00:06:46.110> we<00:06:46.230> could 00:06:46.340 --> 00:06:46.350 align:start position:0% into the provider so you know we could 00:06:46.350 --> 00:06:48.350 align:start position:0% into the provider so you know we could actually<00:06:46.560> put<00:06:46.830> it<00:06:46.919> into<00:06:47.040> ethers<00:06:47.370> again<00:06:47.700> not 00:06:48.350 --> 00:06:48.360 align:start position:0% actually put it into ethers again not 00:06:48.360 --> 00:06:51.650 align:start position:0% actually put it into ethers again not the<00:06:48.480> optimal<00:06:48.810> solution<00:06:50.330> this<00:06:51.330> is<00:06:51.389> something 00:06:51.650 --> 00:06:51.660 align:start position:0% the optimal solution this is something 00:06:51.660 --> 00:06:53.240 align:start position:0% the optimal solution this is something we're<00:06:51.750> thinking<00:06:51.780> about<00:06:52.040> ideally<00:06:53.040> we're<00:06:53.160> gonna 00:06:53.240 --> 00:06:53.250 align:start position:0% we're thinking about ideally we're gonna 00:06:53.250 --> 00:06:54.620 align:start position:0% we're thinking about ideally we're gonna have<00:06:53.370> to<00:06:53.460> do<00:06:53.580> some<00:06:54.000> sort<00:06:54.180> of<00:06:54.210> a<00:06:54.270> ground-up 00:06:54.620 --> 00:06:54.630 align:start position:0% have to do some sort of a ground-up 00:06:54.630 --> 00:06:57.590 align:start position:0% have to do some sort of a ground-up rewrite<00:06:54.990> on<00:06:55.740> our<00:06:56.669> providers<00:06:57.120> and<00:06:57.300> if<00:06:57.360> we<00:06:57.450> can 00:06:57.590 --> 00:06:57.600 align:start position:0% rewrite on our providers and if we can 00:06:57.600 --> 00:06:58.610 align:start position:0% rewrite on our providers and if we can do<00:06:57.660> it<00:06:57.720> from<00:06:57.780> the<00:06:57.930> providers<00:06:58.410> perspective 00:06:58.610 --> 00:06:58.620 align:start position:0% do it from the providers perspective 00:06:58.620 --> 00:07:00.740 align:start position:0% do it from the providers perspective then<00:06:59.100> we<00:06:59.190> actually<00:06:59.460> save<00:06:59.639> ourselves<00:06:59.760> as<00:07:00.180> long 00:07:00.740 --> 00:07:00.750 align:start position:0% then we actually save ourselves as long 00:07:00.750 --> 00:07:02.900 align:start position:0% then we actually save ourselves as long as<00:07:00.870> the<00:07:00.930> providers<00:07:01.350> maintain<00:07:01.889> the<00:07:02.490> same<00:07:02.730> API 00:07:02.900 --> 00:07:02.910 align:start position:0% as the providers maintain the same API 00:07:02.910 --> 00:07:04.760 align:start position:0% as the providers maintain the same API format<00:07:03.630> and<00:07:03.840> then<00:07:03.960> we're<00:07:04.110> just<00:07:04.410> doing<00:07:04.500> a<00:07:04.680> lot 00:07:04.760 --> 00:07:04.770 align:start position:0% format and then we're just doing a lot 00:07:04.770 --> 00:07:06.470 align:start position:0% format and then we're just doing a lot of<00:07:04.889> magic<00:07:05.040> and<00:07:05.340> behind<00:07:05.610> we<00:07:06.000> actually<00:07:06.330> won't 00:07:06.470 --> 00:07:06.480 align:start position:0% of magic and behind we actually won't 00:07:06.480 --> 00:07:08.000 align:start position:0% of magic and behind we actually won't have<00:07:06.630> to<00:07:06.780> rewrite<00:07:07.080> a<00:07:07.139> lot<00:07:07.320> of<00:07:07.410> our<00:07:07.530> dev<00:07:07.680> tooling 00:07:08.000 --> 00:07:08.010 align:start position:0% have to rewrite a lot of our dev tooling 00:07:08.010 --> 00:07:09.710 align:start position:0% have to rewrite a lot of our dev tooling and<00:07:08.220> like<00:07:08.370> dev<00:07:08.550> teams<00:07:08.790> can<00:07:08.970> continue<00:07:09.480> to 00:07:09.710 --> 00:07:09.720 align:start position:0% and like dev teams can continue to 00:07:09.720 --> 00:07:12.170 align:start position:0% and like dev teams can continue to operate<00:07:10.080> as<00:07:10.380> they<00:07:11.070> did<00:07:11.220> before 00:07:12.170 --> 00:07:12.180 align:start position:0% operate as they did before 00:07:12.180 --> 00:07:13.580 align:start position:0% operate as they did before naturally<00:07:12.750> it'd<00:07:12.810> be<00:07:12.930> nice<00:07:13.050> to<00:07:13.200> get<00:07:13.290> some<00:07:13.440> like 00:07:13.580 --> 00:07:13.590 align:start position:0% naturally it'd be nice to get some like 00:07:13.590 --> 00:07:15.770 align:start position:0% naturally it'd be nice to get some like native<00:07:13.980> you<00:07:14.190> know<00:07:14.280> if<00:07:14.520> two<00:07:14.820> tooling<00:07:15.389> but<00:07:15.419> to 00:07:15.770 --> 00:07:15.780 align:start position:0% native you know if two tooling but to 00:07:15.780 --> 00:07:18.350 align:start position:0% native you know if two tooling but to help<00:07:15.960> ease<00:07:16.350> the<00:07:16.889> transition<00:07:16.919> over<00:07:17.669> this<00:07:18.180> is 00:07:18.350 --> 00:07:18.360 align:start position:0% help ease the transition over this is 00:07:18.360 --> 00:07:20.000 align:start position:0% help ease the transition over this is one<00:07:18.750> it's<00:07:18.900> something<00:07:19.020> along<00:07:19.380> this<00:07:19.680> line<00:07:19.860> will 00:07:20.000 --> 00:07:20.010 align:start position:0% one it's something along this line will 00:07:20.010 --> 00:07:21.650 align:start position:0% one it's something along this line will probably<00:07:20.310> have<00:07:20.400> to<00:07:20.460> be<00:07:20.520> the<00:07:20.700> best<00:07:20.940> best<00:07:21.479> case 00:07:21.650 --> 00:07:21.660 align:start position:0% probably have to be the best best case 00:07:21.660 --> 00:07:24.469 align:start position:0% probably have to be the best best case we<00:07:21.810> can<00:07:21.960> do<00:07:22.250> otherwise<00:07:23.250> we<00:07:24.090> just<00:07:24.120> won't<00:07:24.419> have 00:07:24.469 --> 00:07:24.479 align:start position:0% we can do otherwise we just won't have 00:07:24.479 --> 00:07:25.850 align:start position:0% we can do otherwise we just won't have anything<00:07:24.780> ready<00:07:25.080> by<00:07:25.320> the<00:07:25.380> time<00:07:25.440> youth<00:07:25.680> two 00:07:25.850 --> 00:07:25.860 align:start position:0% anything ready by the time youth two 00:07:25.860 --> 00:07:27.080 align:start position:0% anything ready by the time youth two launches<00:07:26.220> and<00:07:26.460> there's<00:07:26.639> no<00:07:26.760> point<00:07:27.000> in 00:07:27.080 --> 00:07:27.090 align:start position:0% launches and there's no point in 00:07:27.090 --> 00:07:30.620 align:start position:0% launches and there's no point in spending<00:07:27.479> resources<00:07:28.110> doing<00:07:28.380> twice<00:07:29.510> so<00:07:30.510> that's 00:07:30.620 --> 00:07:30.630 align:start position:0% spending resources doing twice so that's 00:07:30.630 --> 00:07:33.500 align:start position:0% spending resources doing twice so that's my<00:07:30.780> little<00:07:30.930> provider<00:07:31.350> show<00:07:32.120> and<00:07:33.120> I'm<00:07:33.240> happy<00:07:33.479> to 00:07:33.500 --> 00:07:33.510 align:start position:0% my little provider show and I'm happy to 00:07:33.510 --> 00:07:35.230 align:start position:0% my little provider show and I'm happy to talk<00:07:33.720> about<00:07:33.810> this<00:07:33.990> a<00:07:34.050> lot<00:07:34.169> more<00:07:34.290> after 00:07:35.230 --> 00:07:35.240 align:start position:0% talk about this a lot more after 00:07:35.240 --> 00:07:37.490 align:start position:0% talk about this a lot more after something<00:07:36.240> else<00:07:36.419> that's<00:07:37.169> kind<00:07:37.410> of 00:07:37.490 --> 00:07:37.500 align:start position:0% something else that's kind of 00:07:37.500 --> 00:07:38.840 align:start position:0% something else that's kind of interesting<00:07:37.710> and<00:07:38.190> this<00:07:38.250> is<00:07:38.310> funny 00:07:38.840 --> 00:07:38.850 align:start position:0% interesting and this is funny 00:07:38.850 --> 00:07:40.280 align:start position:0% interesting and this is funny you<00:07:39.000> know<00:07:39.090> it's<00:07:39.300> like<00:07:39.479> hey<00:07:39.780> maybe<00:07:39.960> we<00:07:40.169> can 00:07:40.280 --> 00:07:40.290 align:start position:0% you know it's like hey maybe we can 00:07:40.290 --> 00:07:42.379 align:start position:0% you know it's like hey maybe we can solve<00:07:40.410> it<00:07:40.590> after<00:07:40.770> 30<00:07:40.950> years<00:07:41.040> but<00:07:41.280> we<00:07:41.400> won't<00:07:41.580> is 00:07:42.379 --> 00:07:42.389 align:start position:0% solve it after 30 years but we won't is 00:07:42.389 --> 00:07:44.120 align:start position:0% solve it after 30 years but we won't is the<00:07:42.840> intersection<00:07:43.260> of<00:07:43.440> like<00:07:43.590> like<00:07:43.800> clients 00:07:44.120 --> 00:07:44.130 align:start position:0% the intersection of like like clients 00:07:44.130 --> 00:07:45.260 align:start position:0% the intersection of like like clients and<00:07:44.220> developer<00:07:44.580> tooling<00:07:44.820> and<00:07:44.970> how<00:07:45.030> we<00:07:45.090> can 00:07:45.260 --> 00:07:45.270 align:start position:0% and developer tooling and how we can 00:07:45.270 --> 00:07:46.790 align:start position:0% and developer tooling and how we can actually<00:07:45.389> potentially<00:07:45.960> make<00:07:46.380> smarter 00:07:46.790 --> 00:07:46.800 align:start position:0% actually potentially make smarter 00:07:46.800 --> 00:07:47.300 align:start position:0% actually potentially make smarter developers 00:07:47.300 --> 00:07:47.310 align:start position:0% developers 00:07:47.310 --> 00:07:49.460 align:start position:0% developers and<00:07:48.000> by<00:07:48.389> this<00:07:48.450> I<00:07:48.690> mean<00:07:48.720> like<00:07:48.990> more<00:07:49.229> on<00:07:49.289> the 00:07:49.460 --> 00:07:49.470 align:start position:0% and by this I mean like more on the 00:07:49.470 --> 00:07:51.560 align:start position:0% and by this I mean like more on the front<00:07:49.650> end<00:07:49.770> the<00:07:49.890> D<00:07:50.130> app<00:07:50.220> side<00:07:50.520> because<00:07:51.390> right 00:07:51.560 --> 00:07:51.570 align:start position:0% front end the D app side because right 00:07:51.570 --> 00:07:55.250 align:start position:0% front end the D app side because right now<00:07:52.220> you<00:07:53.220> know<00:07:53.340> we<00:07:53.610> spend<00:07:54.000> a<00:07:54.090> lot<00:07:54.120> of<00:07:54.270> time<00:07:54.570> a 00:07:55.250 --> 00:07:55.260 align:start position:0% now you know we spend a lot of time a 00:07:55.260 --> 00:07:57.290 align:start position:0% now you know we spend a lot of time a lot<00:07:55.710> of<00:07:55.770> our<00:07:55.950> the<00:07:56.280> ways<00:07:56.580> we<00:07:56.760> do<00:07:56.880> things<00:07:57.090> we<00:07:57.180> do<00:07:57.270> a 00:07:57.290 --> 00:07:57.300 align:start position:0% lot of our the ways we do things we do a 00:07:57.300 --> 00:07:58.460 align:start position:0% lot of our the ways we do things we do a lot<00:07:57.450> polling<00:07:57.870> for<00:07:57.990> instance<00:07:58.260> a<00:07:58.320> lot<00:07:58.380> of 00:07:58.460 --> 00:07:58.470 align:start position:0% lot polling for instance a lot of 00:07:58.470 --> 00:07:59.900 align:start position:0% lot polling for instance a lot of developers<00:07:58.800> like<00:07:58.979> go<00:07:59.100> and<00:07:59.250> pull<00:07:59.490> the<00:07:59.700> chain 00:07:59.900 --> 00:07:59.910 align:start position:0% developers like go and pull the chain 00:07:59.910 --> 00:08:01.250 align:start position:0% developers like go and pull the chain like<00:08:00.120> a<00:08:00.150> million<00:08:00.479> times<00:08:00.690> over<00:08:00.810> and<00:08:00.960> a<00:08:01.020> million 00:08:01.250 --> 00:08:01.260 align:start position:0% like a million times over and a million 00:08:01.260 --> 00:08:02.510 align:start position:0% like a million times over and a million times<00:08:01.410> over<00:08:01.530> and<00:08:01.680> then<00:08:01.800> like<00:08:01.979> you<00:08:02.370> know<00:08:02.460> if 00:08:02.510 --> 00:08:02.520 align:start position:0% times over and then like you know if 00:08:02.520 --> 00:08:04.279 align:start position:0% times over and then like you know if they're<00:08:02.640> hitting<00:08:02.850> in<00:08:02.940> fear<00:08:03.210> of<00:08:03.240> getting<00:08:04.169> like 00:08:04.279 --> 00:08:04.289 align:start position:0% they're hitting in fear of getting like 00:08:04.289 --> 00:08:05.690 align:start position:0% they're hitting in fear of getting like you're<00:08:04.470> bombarding<00:08:05.039> in<00:08:05.130> fear<00:08:05.370> with<00:08:05.520> like 00:08:05.690 --> 00:08:05.700 align:start position:0% you're bombarding in fear with like 00:08:05.700 --> 00:08:08.060 align:start position:0% you're bombarding in fear with like thousands<00:08:06.630> of<00:08:06.780> requests<00:08:07.229> it's<00:08:07.620> not<00:08:07.770> a<00:08:07.800> great 00:08:08.060 --> 00:08:08.070 align:start position:0% thousands of requests it's not a great 00:08:08.070 --> 00:08:11.180 align:start position:0% thousands of requests it's not a great solution<00:08:08.479> but<00:08:09.479> moving<00:08:09.720> forward<00:08:09.810> because<00:08:10.190> you 00:08:11.180 --> 00:08:11.190 align:start position:0% solution but moving forward because you 00:08:11.190 --> 00:08:14.480 align:start position:0% solution but moving forward because you know<00:08:11.310> like<00:08:11.850> clients<00:08:12.210> are<00:08:12.330> becoming<00:08:12.690> our<00:08:13.490> first 00:08:14.480 --> 00:08:14.490 align:start position:0% know like clients are becoming our first 00:08:14.490 --> 00:08:16.520 align:start position:0% know like clients are becoming our first class<00:08:14.639> citizens<00:08:15.060> in<00:08:15.120> 8th<00:08:15.240> -<00:08:15.450> which<00:08:16.139> means<00:08:16.320> we 00:08:16.520 --> 00:08:16.530 align:start position:0% class citizens in 8th - which means we 00:08:16.530 --> 00:08:18.469 align:start position:0% class citizens in 8th - which means we actually<00:08:16.830> can<00:08:16.979> use<00:08:17.130> this<00:08:17.250> as<00:08:17.700> like<00:08:18.090> a<00:08:18.150> powerful 00:08:18.469 --> 00:08:18.479 align:start position:0% actually can use this as like a powerful 00:08:18.479 --> 00:08:21.350 align:start position:0% actually can use this as like a powerful tool<00:08:18.750> to<00:08:18.810> help<00:08:19.080> us<00:08:19.440> you<00:08:19.770> know<00:08:20.280> not<00:08:20.850> exhaust 00:08:21.350 --> 00:08:21.360 align:start position:0% tool to help us you know not exhaust 00:08:21.360 --> 00:08:25.190 align:start position:0% tool to help us you know not exhaust resources<00:08:21.990> and<00:08:22.280> actually<00:08:23.280> utilize<00:08:24.120> only<00:08:24.600> what 00:08:25.190 --> 00:08:25.200 align:start position:0% resources and actually utilize only what 00:08:25.200 --> 00:08:28.219 align:start position:0% resources and actually utilize only what we<00:08:25.320> need<00:08:25.580> to<00:08:26.580> you<00:08:27.060> know<00:08:27.150> serve<00:08:27.450> our<00:08:27.600> DAPs<00:08:27.840> or 00:08:28.219 --> 00:08:28.229 align:start position:0% we need to you know serve our DAPs or 00:08:28.229 --> 00:08:30.409 align:start position:0% we need to you know serve our DAPs or serve<00:08:28.590> whatever<00:08:28.830> the<00:08:29.100> application<00:08:29.250> is<00:08:29.760> moving 00:08:30.409 --> 00:08:30.419 align:start position:0% serve whatever the application is moving 00:08:30.419 --> 00:08:35.510 align:start position:0% serve whatever the application is moving forward<00:08:31.909> so<00:08:32.909> I've<00:08:33.950> naively<00:08:34.950> put<00:08:35.130> you<00:08:35.400> know 00:08:35.510 --> 00:08:35.520 align:start position:0% forward so I've naively put you know 00:08:35.520 --> 00:08:36.740 align:start position:0% forward so I've naively put you know we're<00:08:35.729> still<00:08:35.880> working<00:08:35.940> on<00:08:36.300> this<00:08:36.450> and<00:08:36.630> it's 00:08:36.740 --> 00:08:36.750 align:start position:0% we're still working on this and it's 00:08:36.750 --> 00:08:38.209 align:start position:0% we're still working on this and it's kind<00:08:36.900> of<00:08:36.959> like<00:08:37.169> I<00:08:37.409> want<00:08:37.709> to<00:08:37.770> try<00:08:37.919> it<00:08:38.010> we're 00:08:38.209 --> 00:08:38.219 align:start position:0% kind of like I want to try it we're 00:08:38.219 --> 00:08:39.440 align:start position:0% kind of like I want to try it we're trying<00:08:38.310> to<00:08:38.490> think<00:08:38.640> of<00:08:38.700> a<00:08:38.789> new<00:08:38.969> way<00:08:39.120> to<00:08:39.150> like 00:08:39.440 --> 00:08:39.450 align:start position:0% trying to think of a new way to like 00:08:39.450 --> 00:08:40.820 align:start position:0% trying to think of a new way to like reshape<00:08:39.870> the<00:08:39.990> way<00:08:40.110> we<00:08:40.229> interact<00:08:40.589> with<00:08:40.680> the 00:08:40.820 --> 00:08:40.830 align:start position:0% reshape the way we interact with the 00:08:40.830 --> 00:08:43.399 align:start position:0% reshape the way we interact with the chain<00:08:41.039> I<00:08:41.969> don't<00:08:42.479> want<00:08:42.599> to<00:08:42.690> go<00:08:42.810> too<00:08:42.870> deep<00:08:43.020> on<00:08:43.229> my 00:08:43.399 --> 00:08:43.409 align:start position:0% chain I don't want to go too deep on my 00:08:43.409 --> 00:08:45.110 align:start position:0% chain I don't want to go too deep on my clients<00:08:43.740> but<00:08:43.890> like<00:08:44.010> it<00:08:44.219> so<00:08:44.550> basically<00:08:44.970> the 00:08:45.110 --> 00:08:45.120 align:start position:0% clients but like it so basically the 00:08:45.120 --> 00:08:46.579 align:start position:0% clients but like it so basically the idea<00:08:45.150> is<00:08:45.330> you<00:08:45.390> subscribe<00:08:45.870> to<00:08:45.990> a<00:08:46.020> shard<00:08:46.350> that 00:08:46.579 --> 00:08:46.589 align:start position:0% idea is you subscribe to a shard that 00:08:46.589 --> 00:08:48.199 align:start position:0% idea is you subscribe to a shard that you<00:08:46.680> want<00:08:46.950> or<00:08:47.250> a<00:08:47.279> subset<00:08:47.670> of<00:08:47.700> shards<00:08:48.000> that<00:08:48.150> you 00:08:48.199 --> 00:08:48.209 align:start position:0% you want or a subset of shards that you 00:08:48.209 --> 00:08:50.360 align:start position:0% you want or a subset of shards that you want<00:08:48.420> and<00:08:48.690> you<00:08:49.380> only<00:08:49.529> get<00:08:49.709> the<00:08:49.860> relevant<00:08:50.160> data 00:08:50.360 --> 00:08:50.370 align:start position:0% want and you only get the relevant data 00:08:50.370 --> 00:08:54.470 align:start position:0% want and you only get the relevant data that<00:08:50.580> you<00:08:50.670> need<00:08:50.790> very<00:08:51.570> lightly<00:08:51.870> put<00:08:53.480> and 00:08:54.470 --> 00:08:54.480 align:start position:0% that you need very lightly put and 00:08:54.480 --> 00:08:56.780 align:start position:0% that you need very lightly put and something<00:08:55.050> that<00:08:55.110> we<00:08:55.230> can<00:08:55.260> do<00:08:55.530> here<00:08:55.890> is<00:08:56.100> the 00:08:56.780 --> 00:08:56.790 align:start position:0% something that we can do here is the 00:08:56.790 --> 00:08:57.350 align:start position:0% something that we can do here is the current 00:08:57.350 --> 00:08:57.360 align:start position:0% current 00:08:57.360 --> 00:08:59.120 align:start position:0% current and<00:08:57.720> flow<00:08:57.930> in<00:08:58.140> eath<00:08:58.290> one<00:08:58.500> is<00:08:58.649> that<00:08:58.829> you<00:08:59.040> know 00:08:59.120 --> 00:08:59.130 align:start position:0% and flow in eath one is that you know 00:08:59.130 --> 00:09:00.860 align:start position:0% and flow in eath one is that you know the<00:08:59.310> website<00:08:59.490> to<00:09:00.149> connect<00:09:00.360> to<00:09:00.480> the<00:09:00.570> provider 00:09:00.860 --> 00:09:00.870 align:start position:0% the website to connect to the provider 00:09:00.870 --> 00:09:05.060 align:start position:0% the website to connect to the provider that<00:09:01.110> provider<00:09:01.740> then<00:09:01.950> hits<00:09:02.250> a<00:09:02.610> full<00:09:03.480> node<00:09:04.070> has 00:09:05.060 --> 00:09:05.070 align:start position:0% that provider then hits a full node has 00:09:05.070 --> 00:09:06.470 align:start position:0% that provider then hits a full node has to<00:09:05.250> the<00:09:05.459> full<00:09:05.610> node<00:09:05.760> asset<00:09:06.000> like<00:09:06.149> basically 00:09:06.470 --> 00:09:06.480 align:start position:0% to the full node asset like basically 00:09:06.480 --> 00:09:08.600 align:start position:0% to the full node asset like basically index<00:09:06.839> the<00:09:06.930> whole<00:09:07.079> thing<00:09:07.529> to<00:09:07.800> find<00:09:08.010> what<00:09:08.190> exact 00:09:08.600 --> 00:09:08.610 align:start position:0% index the whole thing to find what exact 00:09:08.610 --> 00:09:10.190 align:start position:0% index the whole thing to find what exact information<00:09:09.180> you<00:09:09.269> need<00:09:09.450> and<00:09:09.600> then<00:09:09.779> returns<00:09:10.079> it 00:09:10.190 --> 00:09:10.200 align:start position:0% information you need and then returns it 00:09:10.200 --> 00:09:12.440 align:start position:0% information you need and then returns it very<00:09:10.769> slow<00:09:10.980> very<00:09:11.010> cumbersome<00:09:11.579> with<00:09:12.209> like 00:09:12.440 --> 00:09:12.450 align:start position:0% very slow very cumbersome with like 00:09:12.450 --> 00:09:13.699 align:start position:0% very slow very cumbersome with like clients<00:09:12.810> we<00:09:12.899> can<00:09:13.019> use<00:09:13.200> we<00:09:13.290> actually<00:09:13.320> couldn't 00:09:13.699 --> 00:09:13.709 align:start position:0% clients we can use we actually couldn't 00:09:13.709 --> 00:09:15.350 align:start position:0% clients we can use we actually couldn't put<00:09:13.890> the<00:09:13.980> burden<00:09:14.190> back<00:09:14.399> on<00:09:14.640> the<00:09:14.760> website<00:09:15.149> or 00:09:15.350 --> 00:09:15.360 align:start position:0% put the burden back on the website or 00:09:15.360 --> 00:09:17.569 align:start position:0% put the burden back on the website or the<00:09:15.480> client<00:09:15.899> or<00:09:16.140> the<00:09:16.170> browser<00:09:16.500> itself<00:09:16.950> and 00:09:17.569 --> 00:09:17.579 align:start position:0% the client or the browser itself and 00:09:17.579 --> 00:09:18.829 align:start position:0% the client or the browser itself and this<00:09:17.700> is<00:09:17.790> kind<00:09:17.940> of<00:09:17.970> interesting<00:09:18.149> because<00:09:18.540> what 00:09:18.829 --> 00:09:18.839 align:start position:0% this is kind of interesting because what 00:09:18.839 --> 00:09:19.850 align:start position:0% this is kind of interesting because what we<00:09:18.930> can<00:09:19.050> do<00:09:19.140> is<00:09:19.230> we<00:09:19.290> can<00:09:19.380> do<00:09:19.500> one<00:09:19.620> of<00:09:19.740> two<00:09:19.829> things 00:09:19.850 --> 00:09:19.860 align:start position:0% we can do is we can do one of two things 00:09:19.860 --> 00:09:23.120 align:start position:0% we can do is we can do one of two things we<00:09:20.610> can<00:09:20.640> say<00:09:20.970> when<00:09:21.959> you<00:09:22.170> go<00:09:22.290> into<00:09:22.500> a<00:09:22.529> website<00:09:22.890> we 00:09:23.120 --> 00:09:23.130 align:start position:0% we can say when you go into a website we 00:09:23.130 --> 00:09:24.590 align:start position:0% we can say when you go into a website we can<00:09:23.160> look<00:09:23.459> for<00:09:23.670> now<00:09:23.940> I<00:09:23.970> know<00:09:24.120> a<00:09:24.240> lot<00:09:24.390> of<00:09:24.420> people 00:09:24.590 --> 00:09:24.600 align:start position:0% can look for now I know a lot of people 00:09:24.600 --> 00:09:25.759 align:start position:0% can look for now I know a lot of people are<00:09:24.660> gonna<00:09:24.750> be<00:09:24.899> like<00:09:25.019> you<00:09:25.529> shouldn't<00:09:25.709> be 00:09:25.759 --> 00:09:25.769 align:start position:0% are gonna be like you shouldn't be 00:09:25.769 --> 00:09:27.380 align:start position:0% are gonna be like you shouldn't be injecting<00:09:26.190> like<00:09:26.399> web<00:09:26.579> 3<00:09:26.850> into<00:09:27.089> the<00:09:27.180> browser 00:09:27.380 --> 00:09:27.390 align:start position:0% injecting like web 3 into the browser 00:09:27.390 --> 00:09:28.460 align:start position:0% injecting like web 3 into the browser but<00:09:27.720> we're<00:09:27.839> not<00:09:27.930> gonna<00:09:28.050> talk<00:09:28.230> about<00:09:28.260> there 00:09:28.460 --> 00:09:28.470 align:start position:0% but we're not gonna talk about there 00:09:28.470 --> 00:09:29.660 align:start position:0% but we're not gonna talk about there right<00:09:28.589> now<00:09:28.680> let's<00:09:29.130> just<00:09:29.250> make<00:09:29.370> a<00:09:29.399> naive 00:09:29.660 --> 00:09:29.670 align:start position:0% right now let's just make a naive 00:09:29.670 --> 00:09:32.420 align:start position:0% right now let's just make a naive assumption<00:09:30.089> so<00:09:30.720> is<00:09:31.019> there<00:09:31.500> like<00:09:31.800> an<00:09:32.130> e<00:09:32.220> 2 00:09:32.420 --> 00:09:32.430 align:start position:0% assumption so is there like an e 2 00:09:32.430 --> 00:09:34.400 align:start position:0% assumption so is there like an e 2 object<00:09:32.790> in<00:09:32.850> the<00:09:32.910> browser<00:09:33.120> if<00:09:33.450> there<00:09:34.019> is<00:09:34.140> we<00:09:34.290> can 00:09:34.400 --> 00:09:34.410 align:start position:0% object in the browser if there is we can 00:09:34.410 --> 00:09:35.720 align:start position:0% object in the browser if there is we can assume<00:09:34.649> that<00:09:34.829> there's<00:09:35.010> some<00:09:35.250> sort<00:09:35.550> of<00:09:35.640> a 00:09:35.720 --> 00:09:35.730 align:start position:0% assume that there's some sort of a 00:09:35.730 --> 00:09:37.190 align:start position:0% assume that there's some sort of a provider<00:09:36.060> already<00:09:36.360> existing<00:09:36.779> and<00:09:36.930> there's 00:09:37.190 --> 00:09:37.200 align:start position:0% provider already existing and there's 00:09:37.200 --> 00:09:38.449 align:start position:0% provider already existing and there's like<00:09:37.350> potentially<00:09:37.800> a<00:09:37.860> plug-in<00:09:38.190> like<00:09:38.220> meta 00:09:38.449 --> 00:09:38.459 align:start position:0% like potentially a plug-in like meta 00:09:38.459 --> 00:09:42.740 align:start position:0% like potentially a plug-in like meta mask<00:09:38.670> in<00:09:39.600> that<00:09:39.839> case<00:09:40.079> we<00:09:40.740> can't<00:09:41.209> meta<00:09:42.209> mask<00:09:42.450> in 00:09:42.740 --> 00:09:42.750 align:start position:0% mask in that case we can't meta mask in 00:09:42.750 --> 00:09:44.540 align:start position:0% mask in that case we can't meta mask in this<00:09:42.990> instance<00:09:43.560> would<00:09:43.709> be<00:09:43.769> hosting<00:09:44.279> a<00:09:44.370> like 00:09:44.540 --> 00:09:44.550 align:start position:0% this instance would be hosting a like 00:09:44.550 --> 00:09:47.509 align:start position:0% this instance would be hosting a like client<00:09:44.910> actually<00:09:45.540> within<00:09:45.690> the<00:09:46.230> plugin<00:09:46.680> this 00:09:47.509 --> 00:09:47.519 align:start position:0% client actually within the plugin this 00:09:47.519 --> 00:09:49.490 align:start position:0% client actually within the plugin this allows<00:09:47.850> then<00:09:48.300> the<00:09:48.630> web<00:09:48.779> site<00:09:48.990> to<00:09:49.140> go<00:09:49.230> and<00:09:49.380> say 00:09:49.490 --> 00:09:49.500 align:start position:0% allows then the web site to go and say 00:09:49.500 --> 00:09:51.530 align:start position:0% allows then the web site to go and say hey<00:09:49.740> I<00:09:50.010> need<00:09:50.550> you<00:09:50.730> to<00:09:50.880> subscribe<00:09:51.060> to<00:09:51.450> this 00:09:51.530 --> 00:09:51.540 align:start position:0% hey I need you to subscribe to this 00:09:51.540 --> 00:09:53.360 align:start position:0% hey I need you to subscribe to this chart<00:09:51.810> for<00:09:52.050> me<00:09:52.170> and<00:09:52.380> then<00:09:52.500> start<00:09:52.920> persisting 00:09:53.360 --> 00:09:53.370 align:start position:0% chart for me and then start persisting 00:09:53.370 --> 00:09:55.190 align:start position:0% chart for me and then start persisting and<00:09:53.430> maintaining<00:09:53.880> the<00:09:53.970> data<00:09:54.149> while<00:09:54.870> that<00:09:55.079> and 00:09:55.190 --> 00:09:55.200 align:start position:0% and maintaining the data while that and 00:09:55.200 --> 00:09:56.870 align:start position:0% and maintaining the data while that and then<00:09:55.290> you<00:09:55.500> know<00:09:55.620> once<00:09:56.190> the<00:09:56.310> day<00:09:56.399> is<00:09:56.459> requested 00:09:56.870 --> 00:09:56.880 align:start position:0% then you know once the day is requested 00:09:56.880 --> 00:09:58.819 align:start position:0% then you know once the day is requested the<00:09:57.180> website<00:09:57.510> use<00:09:57.630> it<00:09:57.779> as<00:09:57.930> it's<00:09:58.110> going<00:09:58.260> while 00:09:58.819 --> 00:09:58.829 align:start position:0% the website use it as it's going while 00:09:58.829 --> 00:10:00.050 align:start position:0% the website use it as it's going while that's<00:09:59.010> happening<00:09:59.100> we<00:09:59.430> can<00:09:59.459> actually<00:09:59.670> cache 00:10:00.050 --> 00:10:00.060 align:start position:0% that's happening we can actually cache 00:10:00.060 --> 00:10:02.030 align:start position:0% that's happening we can actually cache you<00:10:00.570> know<00:10:00.690> that<00:10:00.870> shard<00:10:01.170> data<00:10:01.380> I<00:10:01.470> know<00:10:01.649> a<00:10:01.680> cookie 00:10:02.030 --> 00:10:02.040 align:start position:0% you know that shard data I know a cookie 00:10:02.040 --> 00:10:04.280 align:start position:0% you know that shard data I know a cookie local<00:10:02.370> storage<00:10:02.610> or<00:10:02.970> even<00:10:03.750> if<00:10:03.870> it's<00:10:04.019> a<00:10:04.079> plugin 00:10:04.280 --> 00:10:04.290 align:start position:0% local storage or even if it's a plugin 00:10:04.290 --> 00:10:07.160 align:start position:0% local storage or even if it's a plugin the<00:10:04.529> plugins<00:10:04.829> state<00:10:05.120> and<00:10:06.120> alternatively<00:10:06.810> if 00:10:07.160 --> 00:10:07.170 align:start position:0% the plugins state and alternatively if 00:10:07.170 --> 00:10:10.400 align:start position:0% the plugins state and alternatively if we<00:10:07.380> make<00:10:07.529> our<00:10:07.560> provider<00:10:07.949> smart<00:10:08.690> we<00:10:09.690> can<00:10:09.720> then 00:10:10.400 --> 00:10:10.410 align:start position:0% we make our provider smart we can then 00:10:10.410 --> 00:10:12.829 align:start position:0% we make our provider smart we can then actually<00:10:10.829> have<00:10:11.550> the<00:10:11.880> website<00:10:12.120> itself<00:10:12.600> if<00:10:12.810> the 00:10:12.829 --> 00:10:12.839 align:start position:0% actually have the website itself if the 00:10:12.839 --> 00:10:15.319 align:start position:0% actually have the website itself if the user<00:10:13.110> doesn't<00:10:13.350> have<00:10:13.680> a<00:10:14.070> plug-in<00:10:14.519> we<00:10:15.089> have<00:10:15.240> the 00:10:15.319 --> 00:10:15.329 align:start position:0% user doesn't have a plug-in we have the 00:10:15.329 --> 00:10:16.880 align:start position:0% user doesn't have a plug-in we have the website<00:10:15.510> itself<00:10:15.810> actually<00:10:16.050> spin<00:10:16.470> up<00:10:16.589> a<00:10:16.740> light 00:10:16.880 --> 00:10:16.890 align:start position:0% website itself actually spin up a light 00:10:16.890 --> 00:10:18.380 align:start position:0% website itself actually spin up a light client<00:10:17.190> and<00:10:17.279> this<00:10:17.399> is<00:10:17.519> because<00:10:17.850> we're<00:10:18.240> gonna 00:10:18.380 --> 00:10:18.390 align:start position:0% client and this is because we're gonna 00:10:18.390 --> 00:10:19.880 align:start position:0% client and this is because we're gonna we<00:10:18.810> will<00:10:18.990> be<00:10:19.110> able<00:10:19.230> to<00:10:19.320> do<00:10:19.440> this<00:10:19.560> simply 00:10:19.880 --> 00:10:19.890 align:start position:0% we will be able to do this simply 00:10:19.890 --> 00:10:21.889 align:start position:0% we will be able to do this simply because<00:10:20.190> we've<00:10:20.850> got<00:10:21.060> languages<00:10:21.510> you<00:10:21.779> know 00:10:21.889 --> 00:10:21.899 align:start position:0% because we've got languages you know 00:10:21.899 --> 00:10:23.750 align:start position:0% because we've got languages you know compiling<00:10:22.410> to<00:10:22.500> wasum<00:10:22.860> but<00:10:23.070> also<00:10:23.279> load<00:10:23.490> stars 00:10:23.750 --> 00:10:23.760 align:start position:0% compiling to wasum but also load stars 00:10:23.760 --> 00:10:26.090 align:start position:0% compiling to wasum but also load stars like<00:10:23.940> whole<00:10:24.149> goal<00:10:24.420> is<00:10:24.720> to<00:10:25.649> have<00:10:25.890> a<00:10:25.949> light 00:10:26.090 --> 00:10:26.100 align:start position:0% like whole goal is to have a light 00:10:26.100 --> 00:10:27.470 align:start position:0% like whole goal is to have a light client<00:10:26.430> that<00:10:26.550> runs<00:10:26.730> in<00:10:26.850> the<00:10:26.910> browser<00:10:27.000> that's 00:10:27.470 --> 00:10:27.480 align:start position:0% client that runs in the browser that's 00:10:27.480 --> 00:10:30.110 align:start position:0% client that runs in the browser that's native<00:10:27.750> to<00:10:27.839> the<00:10:28.050> browser<00:10:28.230> and<00:10:28.529> works<00:10:28.920> so<00:10:29.579> with 00:10:30.110 --> 00:10:30.120 align:start position:0% native to the browser and works so with 00:10:30.120 --> 00:10:31.550 align:start position:0% native to the browser and works so with that<00:10:30.300> we<00:10:30.510> can<00:10:30.720> actually<00:10:31.079> kind<00:10:31.260> of<00:10:31.380> like 00:10:31.550 --> 00:10:31.560 align:start position:0% that we can actually kind of like 00:10:31.560 --> 00:10:33.680 align:start position:0% that we can actually kind of like exploit<00:10:32.220> the<00:10:32.579> browser<00:10:33.000> to<00:10:33.300> its<00:10:33.329> fullest 00:10:33.680 --> 00:10:33.690 align:start position:0% exploit the browser to its fullest 00:10:33.690 --> 00:10:35.240 align:start position:0% exploit the browser to its fullest capabilities<00:10:34.260> so<00:10:34.440> that<00:10:34.560> the<00:10:34.800> burden<00:10:34.980> doesn't 00:10:35.240 --> 00:10:35.250 align:start position:0% capabilities so that the burden doesn't 00:10:35.250 --> 00:10:37.130 align:start position:0% capabilities so that the burden doesn't go<00:10:35.490> on<00:10:35.640> like<00:10:35.820> a<00:10:35.850> centralized<00:10:36.420> service<00:10:36.690> like<00:10:37.019> in 00:10:37.130 --> 00:10:37.140 align:start position:0% go on like a centralized service like in 00:10:37.140 --> 00:10:38.630 align:start position:0% go on like a centralized service like in fear<00:10:37.320> and<00:10:37.440> don't<00:10:37.740> get<00:10:37.890> me<00:10:37.980> wrong<00:10:38.010> I<00:10:38.279> configured 00:10:38.630 --> 00:10:38.640 align:start position:0% fear and don't get me wrong I configured 00:10:38.640 --> 00:10:40.850 align:start position:0% fear and don't get me wrong I configured as<00:10:38.730> is<00:10:39.089> amazing<00:10:39.510> you<00:10:39.990> know<00:10:40.079> that<00:10:40.350> we<00:10:40.529> have<00:10:40.709> two 00:10:40.850 --> 00:10:40.860 align:start position:0% as is amazing you know that we have two 00:10:40.860 --> 00:10:42.710 align:start position:0% as is amazing you know that we have two lot<00:10:41.190> to<00:10:41.339> thank<00:10:41.550> for<00:10:41.699> them<00:10:41.790> but<00:10:42.029> let's<00:10:42.510> try<00:10:42.600> and 00:10:42.710 --> 00:10:42.720 align:start position:0% lot to thank for them but let's try and 00:10:42.720 --> 00:10:44.170 align:start position:0% lot to thank for them but let's try and take<00:10:42.750> the<00:10:42.899> burden<00:10:43.019> away<00:10:43.320> from<00:10:43.500> them<00:10:43.649> if<00:10:43.769> we<00:10:43.890> can 00:10:44.170 --> 00:10:44.180 align:start position:0% take the burden away from them if we can 00:10:44.180 --> 00:10:47.420 align:start position:0% take the burden away from them if we can and<00:10:45.180> a<00:10:45.269> scheme<00:10:45.600> something<00:10:46.019> like<00:10:46.170> this<00:10:46.430> would 00:10:47.420 --> 00:10:47.430 align:start position:0% and a scheme something like this would 00:10:47.430 --> 00:10:49.160 align:start position:0% and a scheme something like this would definitely<00:10:47.850> help<00:10:48.029> solve<00:10:48.480> a<00:10:48.750> lot<00:10:48.990> of<00:10:49.019> those 00:10:49.160 --> 00:10:49.170 align:start position:0% definitely help solve a lot of those 00:10:49.170 --> 00:10:50.900 align:start position:0% definitely help solve a lot of those issues<00:10:49.529> and<00:10:49.680> could<00:10:49.949> potentially<00:10:50.220> change<00:10:50.820> the 00:10:50.900 --> 00:10:50.910 align:start position:0% issues and could potentially change the 00:10:50.910 --> 00:10:58.189 align:start position:0% issues and could potentially change the way<00:10:51.149> we<00:10:51.390> develop<00:10:52.040> and<00:10:53.040> serve<00:10:53.640> data<00:10:56.570> yeah<00:10:57.570> that 00:10:58.189 --> 00:10:58.199 align:start position:0% way we develop and serve data yeah that 00:10:58.199 --> 00:11:02.360 align:start position:0% way we develop and serve data yeah that that's<00:10:58.380> then<00:10:59.279> I<00:10:59.550> under<00:11:00.269> my<00:11:00.390> talk<00:11:00.600> I<00:11:00.930> let's<00:11:01.680> chat 00:11:02.360 --> 00:11:02.370 align:start position:0% that's then I under my talk I let's chat 00:11:02.370 --> 00:11:03.829 align:start position:0% that's then I under my talk I let's chat afterwards<00:11:02.760> if<00:11:03.060> you<00:11:03.089> are<00:11:03.269> tooling<00:11:03.660> team 00:11:03.829 --> 00:11:03.839 align:start position:0% afterwards if you are tooling team 00:11:03.839 --> 00:11:05.269 align:start position:0% afterwards if you are tooling team because<00:11:04.079> like<00:11:04.290> there's<00:11:04.680> a<00:11:04.740> lot<00:11:04.920> to<00:11:05.070> kind<00:11:05.190> of 00:11:05.269 --> 00:11:05.279 align:start position:0% because like there's a lot to kind of 00:11:05.279 --> 00:11:07.250 align:start position:0% because like there's a lot to kind of discuss<00:11:05.610> here<00:11:05.760> it's<00:11:05.910> still<00:11:06.060> pretty<00:11:06.240> early<00:11:06.360> but 00:11:07.250 --> 00:11:07.260 align:start position:0% discuss here it's still pretty early but 00:11:07.260 --> 00:11:08.480 align:start position:0% discuss here it's still pretty early but there's<00:11:07.589> things<00:11:07.829> that<00:11:07.980> we<00:11:08.160> need<00:11:08.310> to<00:11:08.370> start 00:11:08.480 --> 00:11:08.490 align:start position:0% there's things that we need to start 00:11:08.490 --> 00:11:10.610 align:start position:0% there's things that we need to start talking<00:11:08.819> about<00:11:08.880> now<00:11:09.149> I<00:11:09.390> know<00:11:10.199> there's<00:11:10.470> a<00:11:10.500> lot 00:11:10.610 --> 00:11:10.620 align:start position:0% talking about now I know there's a lot 00:11:10.620 --> 00:11:11.300 align:start position:0% talking about now I know there's a lot of<00:11:10.680> pain<00:11:10.829> points<00:11:11.010> and 00:11:11.300 --> 00:11:11.310 align:start position:0% of pain points and 00:11:11.310 --> 00:11:13.910 align:start position:0% of pain points and current<00:11:11.520> api<00:11:11.730> and<00:11:12.120> the<00:11:12.300> current<00:11:12.570> way<00:11:12.660> eath<00:11:13.650> one 00:11:13.910 --> 00:11:13.920 align:start position:0% current api and the current way eath one 00:11:13.920 --> 00:11:16.810 align:start position:0% current api and the current way eath one works<00:11:14.190> in<00:11:14.670> regrets<00:11:15.270> like<00:11:15.390> the<00:11:15.540> json-rpc<00:11:15.900> api 00:11:16.810 --> 00:11:16.820 align:start position:0% works in regrets like the json-rpc api 00:11:16.820 --> 00:11:20.000 align:start position:0% works in regrets like the json-rpc api and<00:11:17.820> we<00:11:18.450> have<00:11:18.690> an<00:11:18.810> opportunity<00:11:19.080> to<00:11:19.620> kind<00:11:19.920> of 00:11:20.000 --> 00:11:20.010 align:start position:0% and we have an opportunity to kind of 00:11:20.010 --> 00:11:22.100 align:start position:0% and we have an opportunity to kind of learn<00:11:20.279> from<00:11:20.310> our<00:11:20.640> mistakes<00:11:20.970> reshape<00:11:21.840> it<00:11:21.960> from 00:11:22.100 --> 00:11:22.110 align:start position:0% learn from our mistakes reshape it from 00:11:22.110 --> 00:11:24.740 align:start position:0% learn from our mistakes reshape it from the<00:11:22.200> beginning<00:11:22.590> and<00:11:22.760> just<00:11:23.760> saw<00:11:23.940> and<00:11:24.150> basically 00:11:24.740 --> 00:11:24.750 align:start position:0% the beginning and just saw and basically 00:11:24.750 --> 00:11:27.470 align:start position:0% the beginning and just saw and basically you<00:11:25.500> know<00:11:25.620> make<00:11:26.340> it<00:11:26.460> as<00:11:26.550> optimal<00:11:27.060> as<00:11:27.090> we<00:11:27.300> can 00:11:27.470 --> 00:11:27.480 align:start position:0% you know make it as optimal as we can 00:11:27.480 --> 00:11:30.230 align:start position:0% you know make it as optimal as we can right<00:11:27.900> out<00:11:28.020> of<00:11:28.050> the<00:11:28.140> gate<00:11:28.520> so<00:11:29.520> thank<00:11:29.910> you<00:11:30.000> and 00:11:30.230 --> 00:11:30.240 align:start position:0% right out of the gate so thank you and 00:11:30.240 --> 00:11:32.280 align:start position:0% right out of the gate so thank you and you<00:11:31.200> can<00:11:31.320> contact<00:11:31.650> me<00:11:31.770> here 00:11:32.280 --> 00:11:32.290 align:start position:0% you can contact me here 00:11:32.290 --> 00:11:43.070 align:start position:0% you can contact me here [Applause] 00:11:43.070 --> 00:11:43.080 align:start position:0% 00:11:43.080 --> 00:11:45.140 align:start position:0% you