WEBVTT Kind: captions Language: en 00:00:04.319 --> 00:00:07.750 align:start position:0% welcome<00:00:05.309> everyone<00:00:05.549> to<00:00:05.970> the<00:00:06.149> a<00:00:06.509> theorem<00:00:06.960> 2.0 00:00:07.750 --> 00:00:07.760 align:start position:0% welcome everyone to the a theorem 2.0 00:00:07.760 --> 00:00:10.879 align:start position:0% welcome everyone to the a theorem 2.0 client<00:00:08.760> panel<00:00:09.030> discussion<00:00:09.510> the<00:00:09.869> idea<00:00:10.650> what 00:00:10.879 --> 00:00:10.889 align:start position:0% client panel discussion the idea what 00:00:10.889 --> 00:00:13.369 align:start position:0% client panel discussion the idea what this<00:00:11.070> is<00:00:11.309> -<00:00:11.719> well<00:00:12.719> after<00:00:12.840> this<00:00:13.109> morning's 00:00:13.369 --> 00:00:13.379 align:start position:0% this is - well after this morning's 00:00:13.379 --> 00:00:15.109 align:start position:0% this is - well after this morning's presentations<00:00:13.980> where<00:00:14.189> we<00:00:14.490> saw<00:00:14.699> lots<00:00:14.939> of<00:00:15.029> the 00:00:15.109 --> 00:00:15.119 align:start position:0% presentations where we saw lots of the 00:00:15.119 --> 00:00:17.929 align:start position:0% presentations where we saw lots of the work<00:00:15.270> that's<00:00:15.449> been<00:00:15.600> done<00:00:16.039> and<00:00:17.039> and<00:00:17.460> been<00:00:17.699> given 00:00:17.929 --> 00:00:17.939 align:start position:0% work that's been done and and been given 00:00:17.939 --> 00:00:20.540 align:start position:0% work that's been done and and been given insight<00:00:18.330> into<00:00:18.660> -<00:00:19.230> some<00:00:19.830> of<00:00:19.859> the<00:00:20.010> solutions 00:00:20.540 --> 00:00:20.550 align:start position:0% insight into - some of the solutions 00:00:20.550 --> 00:00:23.000 align:start position:0% insight into - some of the solutions that<00:00:20.730> have<00:00:20.820> come<00:00:21.030> up<00:00:21.150> with<00:00:21.180> to<00:00:22.050> explore<00:00:22.680> more 00:00:23.000 --> 00:00:23.010 align:start position:0% that have come up with to explore more 00:00:23.010 --> 00:00:26.060 align:start position:0% that have come up with to explore more how<00:00:23.369> we<00:00:23.400> move<00:00:24.360> on<00:00:24.539> from<00:00:24.570> here<00:00:25.020> in<00:00:25.770> particularly 00:00:26.060 --> 00:00:26.070 align:start position:0% how we move on from here in particularly 00:00:26.070 --> 00:00:29.689 align:start position:0% how we move on from here in particularly how<00:00:26.610> do<00:00:26.670> we<00:00:26.880> do<00:00:27.000> that<00:00:27.180> together<00:00:28.520> there's<00:00:29.520> a<00:00:29.580> lot 00:00:29.689 --> 00:00:29.699 align:start position:0% how do we do that together there's a lot 00:00:29.699 --> 00:00:34.220 align:start position:0% how do we do that together there's a lot of<00:00:31.369> -<00:00:32.369> togetherness<00:00:33.239> I<00:00:33.510> think<00:00:33.719> in<00:00:33.840> general<00:00:33.989> in 00:00:34.220 --> 00:00:34.230 align:start position:0% of - togetherness I think in general in 00:00:34.230 --> 00:00:36.889 align:start position:0% of - togetherness I think in general in a<00:00:34.320> theorem<00:00:34.590> 2.0<00:00:35.010> there's<00:00:35.280> there's<00:00:35.780> many<00:00:36.780> of 00:00:36.889 --> 00:00:36.899 align:start position:0% a theorem 2.0 there's there's many of 00:00:36.899 --> 00:00:38.719 align:start position:0% a theorem 2.0 there's there's many of the<00:00:36.989> the<00:00:37.260> the<00:00:37.620> design<00:00:37.949> aspects<00:00:38.519> have<00:00:38.699> been 00:00:38.719 --> 00:00:38.729 align:start position:0% the the the design aspects have been 00:00:38.729 --> 00:00:41.000 align:start position:0% the the the design aspects have been centered<00:00:39.329> around<00:00:39.449> trying<00:00:40.109> to<00:00:40.350> coordinate 00:00:41.000 --> 00:00:41.010 align:start position:0% centered around trying to coordinate 00:00:41.010 --> 00:00:44.079 align:start position:0% centered around trying to coordinate people<00:00:41.749> be<00:00:42.749> that<00:00:42.899> through<00:00:43.260> the<00:00:43.499> use<00:00:43.889> of 00:00:44.079 --> 00:00:44.089 align:start position:0% people be that through the use of 00:00:44.089 --> 00:00:45.979 align:start position:0% people be that through the use of technologies<00:00:45.089> that<00:00:45.389> other<00:00:45.600> people<00:00:45.839> are<00:00:45.960> using 00:00:45.979 --> 00:00:45.989 align:start position:0% technologies that other people are using 00:00:45.989 --> 00:00:49.939 align:start position:0% technologies that other people are using was<00:00:46.589> on<00:00:46.739> the<00:00:46.859> p2p<00:00:47.420> BLS<00:00:48.420> standardization<00:00:49.229> etc 00:00:49.939 --> 00:00:49.949 align:start position:0% was on the p2p BLS standardization etc 00:00:49.949 --> 00:00:53.660 align:start position:0% was on the p2p BLS standardization etc to<00:00:50.249> the<00:00:51.049> multi<00:00:52.049> client<00:00:52.429> approach<00:00:53.429> we're 00:00:53.660 --> 00:00:53.670 align:start position:0% to the multi client approach we're 00:00:53.670 --> 00:00:56.869 align:start position:0% to the multi client approach we're taking<00:00:54.170> and<00:00:55.280> I<00:00:56.280> think<00:00:56.519> it's<00:00:56.670> a<00:00:56.699> really 00:00:56.869 --> 00:00:56.879 align:start position:0% taking and I think it's a really 00:00:56.879 --> 00:00:59.180 align:start position:0% taking and I think it's a really powerful<00:00:57.030> a<00:00:57.569> powerful<00:00:58.170> thing<00:00:58.319> as<00:00:58.530> we've<00:00:58.739> we've 00:00:59.180 --> 00:00:59.190 align:start position:0% powerful a powerful thing as we've we've 00:00:59.190 --> 00:01:02.869 align:start position:0% powerful a powerful thing as we've we've we've<00:00:59.549> seen<00:01:01.100> and<00:01:02.100> so<00:01:02.339> I<00:01:02.369> think<00:01:02.489> a<00:01:02.639> good<00:01:02.729> place 00:01:02.869 --> 00:01:02.879 align:start position:0% we've seen and so I think a good place 00:01:02.879 --> 00:01:05.509 align:start position:0% we've seen and so I think a good place to<00:01:03.049> start<00:01:04.049> off<00:01:04.170> with<00:01:04.379> was<00:01:04.650> something<00:01:05.280> we<00:01:05.369> had 00:01:05.509 --> 00:01:05.519 align:start position:0% to start off with was something we had 00:01:05.519 --> 00:01:08.540 align:start position:0% to start off with was something we had quite<00:01:06.000> recently<00:01:06.360> which<00:01:07.170> was<00:01:07.350> the<00:01:07.550> Interop 00:01:08.540 --> 00:01:08.550 align:start position:0% quite recently which was the Interop 00:01:08.550 --> 00:01:12.410 align:start position:0% quite recently which was the Interop event<00:01:09.770> this<00:01:10.770> this<00:01:11.070> look<00:01:11.460> great<00:01:11.610> a<00:01:12.150> great 00:01:12.410 --> 00:01:12.420 align:start position:0% event this this look great a great 00:01:12.420 --> 00:01:15.710 align:start position:0% event this this look great a great opportunity<00:01:12.600> where<00:01:13.170> we<00:01:13.500> looked<00:01:13.680> well<00:01:14.160> some<00:01:14.730> he 00:01:15.710 --> 00:01:15.720 align:start position:0% opportunity where we looked well some he 00:01:15.720 --> 00:01:17.090 align:start position:0% opportunity where we looked well some he basically<00:01:16.200> locked<00:01:16.500> a<00:01:16.560> bunch<00:01:16.710> of<00:01:16.770> people<00:01:16.980> in<00:01:17.070> a 00:01:17.090 --> 00:01:17.100 align:start position:0% basically locked a bunch of people in a 00:01:17.100 --> 00:01:19.430 align:start position:0% basically locked a bunch of people in a room<00:01:17.220> to<00:01:17.370> see<00:01:17.520> what<00:01:17.640> happened<00:01:17.910> and<00:01:18.750> and<00:01:19.350> the 00:01:19.430 --> 00:01:19.440 align:start position:0% room to see what happened and and the 00:01:19.440 --> 00:01:21.260 align:start position:0% room to see what happened and and the results<00:01:19.770> of<00:01:19.830> this<00:01:19.890> experiment<00:01:20.250> was<00:01:20.580> we<00:01:21.150> got 00:01:21.260 --> 00:01:21.270 align:start position:0% results of this experiment was we got 00:01:21.270 --> 00:01:23.600 align:start position:0% results of this experiment was we got seven<00:01:21.900> clients<00:01:22.250> speaking<00:01:23.250> to<00:01:23.340> each<00:01:23.430> other 00:01:23.600 --> 00:01:23.610 align:start position:0% seven clients speaking to each other 00:01:23.610 --> 00:01:25.250 align:start position:0% seven clients speaking to each other which<00:01:23.820> is<00:01:24.060> pretty<00:01:24.720> pretty<00:01:24.960> freakin 00:01:25.250 --> 00:01:25.260 align:start position:0% which is pretty pretty freakin 00:01:25.260 --> 00:01:30.200 align:start position:0% which is pretty pretty freakin incredible<00:01:26.240> and<00:01:28.280> yeah<00:01:29.280> so<00:01:29.550> so<00:01:29.820> so<00:01:29.970> now<00:01:30.150> that 00:01:30.200 --> 00:01:30.210 align:start position:0% incredible and yeah so so so now that 00:01:30.210 --> 00:01:32.570 align:start position:0% incredible and yeah so so so now that we've<00:01:30.390> achieved<00:01:30.510> that<00:01:30.840> I<00:01:30.870> think<00:01:31.280> that's<00:01:32.280> that 00:01:32.570 --> 00:01:32.580 align:start position:0% we've achieved that I think that's that 00:01:32.580 --> 00:01:34.910 align:start position:0% we've achieved that I think that's that that's<00:01:32.730> allowed<00:01:33.090> us<00:01:33.120> to<00:01:33.420> do<00:01:34.020> to<00:01:34.260> get<00:01:34.410> a<00:01:34.680> lot 00:01:34.910 --> 00:01:34.920 align:start position:0% that's allowed us to do to get a lot 00:01:34.920 --> 00:01:38.060 align:start position:0% that's allowed us to do to get a lot further<00:01:35.100> along<00:01:35.640> this<00:01:35.850> this<00:01:36.270> route<00:01:36.480> so<00:01:36.720> I<00:01:37.110> think 00:01:38.060 --> 00:01:38.070 align:start position:0% further along this this route so I think 00:01:38.070 --> 00:01:38.930 align:start position:0% further along this this route so I think you<00:01:38.130> should<00:01:38.220> have<00:01:38.310> some<00:01:38.430> introductions 00:01:38.930 --> 00:01:38.940 align:start position:0% you should have some introductions 00:01:38.940 --> 00:01:40.640 align:start position:0% you should have some introductions before<00:01:39.600> we<00:01:39.660> quickly<00:01:39.780> dive<00:01:40.020> into<00:01:40.200> this<00:01:40.380> so<00:01:40.620> if 00:01:40.640 --> 00:01:40.650 align:start position:0% before we quickly dive into this so if 00:01:40.650 --> 00:01:43.670 align:start position:0% before we quickly dive into this so if you<00:01:41.070> can<00:01:41.190> start<00:01:41.430> down<00:01:41.940> that<00:01:41.970> side<00:01:42.300> and<00:01:42.680> have 00:01:43.670 --> 00:01:43.680 align:start position:0% you can start down that side and have 00:01:43.680 --> 00:01:45.320 align:start position:0% you can start down that side and have everyone<00:01:44.010> just<00:01:44.520> say<00:01:44.850> the<00:01:44.940> name 00:01:45.320 --> 00:01:45.330 align:start position:0% everyone just say the name 00:01:45.330 --> 00:01:48.080 align:start position:0% everyone just say the name what<00:01:45.660> who<00:01:45.930> they're<00:01:46.110> working<00:01:46.800> on<00:01:46.890> and<00:01:47.130> what<00:01:47.970> was 00:01:48.080 --> 00:01:48.090 align:start position:0% what who they're working on and what was 00:01:48.090 --> 00:01:49.520 align:start position:0% what who they're working on and what was the<00:01:48.270> sort<00:01:48.570> of<00:01:48.659> one<00:01:48.870> thing<00:01:48.900> that<00:01:49.230> they<00:01:49.320> took 00:01:49.520 --> 00:01:49.530 align:start position:0% the sort of one thing that they took 00:01:49.530 --> 00:01:51.950 align:start position:0% the sort of one thing that they took from<00:01:49.740> from<00:01:50.190> from<00:01:50.220> Interop<00:01:50.790> or<00:01:51.030> what's<00:01:51.270> the<00:01:51.480> the 00:01:51.950 --> 00:01:51.960 align:start position:0% from from from Interop or what's the the 00:01:51.960 --> 00:01:55.310 align:start position:0% from from from Interop or what's the the one<00:01:52.370> maybe<00:01:53.370> the<00:01:53.810> the<00:01:54.810> main<00:01:54.930> thing<00:01:54.960> that<00:01:55.140> you 00:01:55.310 --> 00:01:55.320 align:start position:0% one maybe the the main thing that you 00:01:55.320 --> 00:01:57.050 align:start position:0% one maybe the the main thing that you guys<00:01:55.470> are<00:01:55.620> now<00:01:55.680> working<00:01:55.860> on<00:01:56.130> as<00:01:56.280> a<00:01:56.310> result<00:01:56.940> of 00:01:57.050 --> 00:01:57.060 align:start position:0% guys are now working on as a result of 00:01:57.060 --> 00:02:01.940 align:start position:0% guys are now working on as a result of Interop<00:01:59.360> hey<00:02:00.360> I'm<00:02:00.570> Ben<00:02:00.870> I'm<00:02:01.170> just<00:02:01.530> standing<00:02:01.830> in 00:02:01.940 --> 00:02:01.950 align:start position:0% Interop hey I'm Ben I'm just standing in 00:02:01.950 --> 00:02:04.820 align:start position:0% Interop hey I'm Ben I'm just standing in for<00:02:02.220> the<00:02:02.820> great<00:02:03.030> Joe<00:02:03.360> DeLong<00:02:03.720> on<00:02:04.080> this<00:02:04.200> panel<00:02:04.590> I 00:02:04.820 --> 00:02:04.830 align:start position:0% for the great Joe DeLong on this panel I 00:02:04.830 --> 00:02:06.649 align:start position:0% for the great Joe DeLong on this panel I kind<00:02:05.400> of<00:02:05.460> assembled<00:02:05.940> the<00:02:06.030> Artemis<00:02:06.390> team<00:02:06.630> a 00:02:06.649 --> 00:02:06.659 align:start position:0% kind of assembled the Artemis team a 00:02:06.659 --> 00:02:09.350 align:start position:0% kind of assembled the Artemis team a year<00:02:06.930> ago<00:02:07.429> I'm<00:02:08.429> best<00:02:08.640> better<00:02:08.940> known<00:02:09.179> for 00:02:09.350 --> 00:02:09.360 align:start position:0% year ago I'm best better known for 00:02:09.360 --> 00:02:13.190 align:start position:0% year ago I'm best better known for what's<00:02:09.539> new<00:02:09.780> in<00:02:09.929> eath<00:02:10.140> to<00:02:10.440> these<00:02:11.280> days<00:02:11.550> I<00:02:12.480> was 00:02:13.190 --> 00:02:13.200 align:start position:0% what's new in eath to these days I was 00:02:13.200 --> 00:02:17.240 align:start position:0% what's new in eath to these days I was at<00:02:13.499> Interop<00:02:14.219> and<00:02:14.489> it<00:02:15.120> was<00:02:15.299> awesome 00:02:17.240 --> 00:02:17.250 align:start position:0% at Interop and it was awesome 00:02:17.250 --> 00:02:20.010 align:start position:0% at Interop and it was awesome takeaways<00:02:18.250> I<00:02:18.280> think<00:02:18.700> it's<00:02:19.390> time<00:02:19.569> to<00:02:19.599> press<00:02:19.870> on 00:02:20.010 --> 00:02:20.020 align:start position:0% takeaways I think it's time to press on 00:02:20.020 --> 00:02:21.240 align:start position:0% takeaways I think it's time to press on to<00:02:20.140> production<00:02:20.620> now<00:02:20.739> we've<00:02:20.920> proved<00:02:21.160> the 00:02:21.240 --> 00:02:21.250 align:start position:0% to production now we've proved the 00:02:21.250 --> 00:02:23.490 align:start position:0% to production now we've proved the concept<00:02:21.370> it<00:02:21.880> works<00:02:22.420> we<00:02:22.750> can<00:02:23.080> interoperate 00:02:23.490 --> 00:02:23.500 align:start position:0% concept it works we can interoperate 00:02:23.500 --> 00:02:26.070 align:start position:0% concept it works we can interoperate it's<00:02:24.099> it's<00:02:24.520> very<00:02:24.580> cool<00:02:25.000> but<00:02:25.390> now<00:02:25.690> we're<00:02:25.930> moving 00:02:26.070 --> 00:02:26.080 align:start position:0% it's it's very cool but now we're moving 00:02:26.080 --> 00:02:28.830 align:start position:0% it's it's very cool but now we're moving into<00:02:26.410> a<00:02:26.440> new<00:02:26.470> phase<00:02:26.739> with<00:02:27.040> without<00:02:27.430> a<00:02:27.489> Miss<00:02:27.840> and 00:02:28.830 --> 00:02:28.840 align:start position:0% into a new phase with without a Miss and 00:02:28.840 --> 00:02:30.809 align:start position:0% into a new phase with without a Miss and handing<00:02:29.440> it<00:02:29.560> over<00:02:29.709> to<00:02:30.010> the<00:02:30.280> production<00:02:30.459> team 00:02:30.809 --> 00:02:30.819 align:start position:0% handing it over to the production team 00:02:30.819 --> 00:02:32.220 align:start position:0% handing it over to the production team to<00:02:31.209> do<00:02:31.300> all<00:02:31.420> the<00:02:31.569> stuff<00:02:31.780> like<00:02:31.900> writing 00:02:32.220 --> 00:02:32.230 align:start position:0% to do all the stuff like writing 00:02:32.230 --> 00:02:35.640 align:start position:0% to do all the stuff like writing documentation<00:02:32.920> and<00:02:33.459> and<00:02:34.500> searching<00:02:35.500> the 00:02:35.640 --> 00:02:35.650 align:start position:0% documentation and and searching the 00:02:35.650 --> 00:02:39.240 align:start position:0% documentation and and searching the comments<00:02:36.489> for<00:02:36.640> to<00:02:36.940> do<00:02:37.120> and<00:02:37.510> all<00:02:37.840> that<00:02:38.050> all<00:02:39.040> that 00:02:39.240 --> 00:02:39.250 align:start position:0% comments for to do and all that all that 00:02:39.250 --> 00:02:43.140 align:start position:0% comments for to do and all that all that good<00:02:39.430> stuff<00:02:41.610> everyone<00:02:42.610> I'm<00:02:42.790> rolled<00:02:43.000> from 00:02:43.140 --> 00:02:43.150 align:start position:0% good stuff everyone I'm rolled from 00:02:43.150 --> 00:02:45.210 align:start position:0% good stuff everyone I'm rolled from prismatic<00:02:43.660> labs<00:02:43.870> I<00:02:44.260> was<00:02:44.739> unfortunately<00:02:44.980> not 00:02:45.210 --> 00:02:45.220 align:start position:0% prismatic labs I was unfortunately not 00:02:45.220 --> 00:02:47.670 align:start position:0% prismatic labs I was unfortunately not to<00:02:45.310> interrupt<00:02:45.610> but<00:02:45.970> uh<00:02:46.030> remotely<00:02:46.959> helping<00:02:47.590> out 00:02:47.670 --> 00:02:47.680 align:start position:0% to interrupt but uh remotely helping out 00:02:47.680 --> 00:02:49.530 align:start position:0% to interrupt but uh remotely helping out the<00:02:47.860> teams<00:02:48.099> there<00:02:48.400> and<00:02:48.700> figuring<00:02:49.090> out<00:02:49.120> kind<00:02:49.420> of 00:02:49.530 --> 00:02:49.540 align:start position:0% the teams there and figuring out kind of 00:02:49.540 --> 00:02:51.780 align:start position:0% the teams there and figuring out kind of how<00:02:49.630> to<00:02:49.660> get<00:02:50.080> people<00:02:50.170> on<00:02:50.410> board<00:02:50.440> prism<00:02:50.920> one<00:02:51.700> of 00:02:51.780 --> 00:02:51.790 align:start position:0% how to get people on board prism one of 00:02:51.790 --> 00:02:54.000 align:start position:0% how to get people on board prism one of the<00:02:51.850> biggest<00:02:52.090> takeaways<00:02:52.480> was<00:02:53.010> getting 00:02:54.000 --> 00:02:54.010 align:start position:0% the biggest takeaways was getting 00:02:54.010 --> 00:02:56.190 align:start position:0% the biggest takeaways was getting everyone<00:02:54.430> to<00:02:54.730> easily<00:02:55.150> run<00:02:55.480> a<00:02:55.540> beacon<00:02:55.930> chain 00:02:56.190 --> 00:02:56.200 align:start position:0% everyone to easily run a beacon chain 00:02:56.200 --> 00:02:59.640 align:start position:0% everyone to easily run a beacon chain and<00:02:56.350> a<00:02:56.410> validator<00:02:57.150> mate<00:02:58.150> like<00:02:58.600> we<00:02:59.170> had<00:02:59.350> to<00:02:59.500> make 00:02:59.640 --> 00:02:59.650 align:start position:0% and a validator mate like we had to make 00:02:59.650 --> 00:03:01.949 align:start position:0% and a validator mate like we had to make it<00:02:59.769> easy<00:02:59.980> for<00:03:00.280> everyone<00:03:00.549> and<00:03:01.299> it<00:03:01.420> improved<00:03:01.810> a 00:03:01.949 --> 00:03:01.959 align:start position:0% it easy for everyone and it improved a 00:03:01.959 --> 00:03:03.630 align:start position:0% it easy for everyone and it improved a lot<00:03:02.049> of<00:03:02.200> our<00:03:02.319> local<00:03:02.620> development<00:03:03.099> a<00:03:03.190> lot<00:03:03.370> I 00:03:03.630 --> 00:03:03.640 align:start position:0% lot of our local development a lot I 00:03:03.640 --> 00:03:06.930 align:start position:0% lot of our local development a lot I made<00:03:04.330> it<00:03:04.450> very<00:03:04.660> very<00:03:05.319> easy<00:03:05.680> to<00:03:06.549> launch<00:03:06.730> a 00:03:06.930 --> 00:03:06.940 align:start position:0% made it very very easy to launch a 00:03:06.940 --> 00:03:08.190 align:start position:0% made it very very easy to launch a beacon<00:03:07.180> chain<00:03:07.390> with<00:03:07.569> n<00:03:07.780> number<00:03:08.019> of 00:03:08.190 --> 00:03:08.200 align:start position:0% beacon chain with n number of 00:03:08.200 --> 00:03:11.070 align:start position:0% beacon chain with n number of deterministic<00:03:08.739> validators<00:03:09.400> so<00:03:10.360> that's<00:03:10.930> sort 00:03:11.070 --> 00:03:11.080 align:start position:0% deterministic validators so that's sort 00:03:11.080 --> 00:03:12.240 align:start position:0% deterministic validators so that's sort of<00:03:11.200> standardization<00:03:11.620> that<00:03:11.769> came<00:03:11.980> out<00:03:12.099> of<00:03:12.130> the 00:03:12.240 --> 00:03:12.250 align:start position:0% of standardization that came out of the 00:03:12.250 --> 00:03:14.460 align:start position:0% of standardization that came out of the effort<00:03:12.519> made<00:03:13.480> our<00:03:13.569> lives<00:03:13.750> easier<00:03:13.959> and 00:03:14.460 --> 00:03:14.470 align:start position:0% effort made our lives easier and 00:03:14.470 --> 00:03:18.539 align:start position:0% effort made our lives easier and hopefully<00:03:14.650> others<00:03:15.099> lives<00:03:15.370> easier<00:03:17.549> everyone 00:03:18.539 --> 00:03:18.549 align:start position:0% hopefully others lives easier everyone 00:03:18.549 --> 00:03:21.240 align:start position:0% hopefully others lives easier everyone I'm<00:03:18.910> Alex<00:03:19.269> Stokes<00:03:19.630> I<00:03:19.930> work<00:03:20.170> on<00:03:20.319> Trinity<00:03:20.769> which 00:03:21.240 --> 00:03:21.250 align:start position:0% I'm Alex Stokes I work on Trinity which 00:03:21.250 --> 00:03:23.880 align:start position:0% I'm Alex Stokes I work on Trinity which is<00:03:21.489> the<00:03:21.760> python<00:03:22.299> implementation<00:03:22.600> of<00:03:23.470> eath<00:03:23.620> - 00:03:23.880 --> 00:03:23.890 align:start position:0% is the python implementation of eath - 00:03:23.890 --> 00:03:26.460 align:start position:0% is the python implementation of eath - oh<00:03:24.390> yeah<00:03:25.390> Interop<00:03:25.690> was<00:03:25.900> great<00:03:26.170> as<00:03:26.410> well 00:03:26.460 --> 00:03:26.470 align:start position:0% oh yeah Interop was great as well 00:03:26.470 --> 00:03:29.880 align:start position:0% oh yeah Interop was great as well probably<00:03:26.980> I'll<00:03:27.070> tell<00:03:27.280> you<00:03:27.400> here<00:03:28.380> the<00:03:29.380> biggest 00:03:29.880 --> 00:03:29.890 align:start position:0% probably I'll tell you here the biggest 00:03:29.890 --> 00:03:31.470 align:start position:0% probably I'll tell you here the biggest thing<00:03:30.070> I<00:03:30.160> think<00:03:30.190> we<00:03:30.430> probably<00:03:30.549> all<00:03:30.760> saw<00:03:31.000> across 00:03:31.470 --> 00:03:31.480 align:start position:0% thing I think we probably all saw across 00:03:31.480 --> 00:03:33.720 align:start position:0% thing I think we probably all saw across the<00:03:31.930> board<00:03:32.140> was<00:03:32.530> yeah<00:03:32.890> just<00:03:33.190> having<00:03:33.400> like 00:03:33.720 --> 00:03:33.730 align:start position:0% the board was yeah just having like 00:03:33.730 --> 00:03:35.340 align:start position:0% the board was yeah just having like these<00:03:33.940> sort<00:03:34.090> of<00:03:34.180> coordinated<00:03:34.630> starts<00:03:34.989> and 00:03:35.340 --> 00:03:35.350 align:start position:0% these sort of coordinated starts and 00:03:35.350 --> 00:03:36.599 align:start position:0% these sort of coordinated starts and like<00:03:35.500> getting<00:03:35.859> these<00:03:35.980> tests<00:03:36.220> nets<00:03:36.430> to 00:03:36.599 --> 00:03:36.609 align:start position:0% like getting these tests nets to 00:03:36.609 --> 00:03:39.090 align:start position:0% like getting these tests nets to actually<00:03:36.880> like<00:03:37.060> all<00:03:37.299> go<00:03:37.540> at<00:03:37.660> the<00:03:37.750> same<00:03:37.930> time<00:03:38.170> we 00:03:39.090 --> 00:03:39.100 align:start position:0% actually like all go at the same time we 00:03:39.100 --> 00:03:42.300 align:start position:0% actually like all go at the same time we have<00:03:39.220> a<00:03:39.250> large<00:03:39.579> number<00:03:39.760> of<00:03:39.910> clients<00:03:40.450> and<00:03:40.690> so<00:03:41.310> we 00:03:42.300 --> 00:03:42.310 align:start position:0% have a large number of clients and so we 00:03:42.310 --> 00:03:44.220 align:start position:0% have a large number of clients and so we have<00:03:42.459> some<00:03:42.670> extra<00:03:42.910> fun<00:03:43.150> just<00:03:43.450> like<00:03:43.510> wrangling 00:03:44.220 --> 00:03:44.230 align:start position:0% have some extra fun just like wrangling 00:03:44.230 --> 00:03:47.520 align:start position:0% have some extra fun just like wrangling all<00:03:44.350> these<00:03:44.590> cats<00:03:45.989> there's<00:03:46.989> like<00:03:47.230> a<00:03:47.260> bunch<00:03:47.500> of 00:03:47.520 --> 00:03:47.530 align:start position:0% all these cats there's like a bunch of 00:03:47.530 --> 00:03:49.500 align:start position:0% all these cats there's like a bunch of little<00:03:47.650> stuff<00:03:47.920> that<00:03:47.980> we<00:03:48.519> saw<00:03:48.730> sort<00:03:49.420> of 00:03:49.500 --> 00:03:49.510 align:start position:0% little stuff that we saw sort of 00:03:49.510 --> 00:03:52.759 align:start position:0% little stuff that we saw sort of specific<00:03:50.410> to<00:03:50.500> Trinity<00:03:50.859> from<00:03:51.489> the<00:03:51.700> Interop<00:03:52.000> and 00:03:52.759 --> 00:03:52.769 align:start position:0% specific to Trinity from the Interop and 00:03:52.769 --> 00:03:54.870 align:start position:0% specific to Trinity from the Interop and the<00:03:53.769> big<00:03:53.980> thing<00:03:54.250> that<00:03:54.280> we'll<00:03:54.549> probably<00:03:54.670> be 00:03:54.870 --> 00:03:54.880 align:start position:0% the big thing that we'll probably be 00:03:54.880 --> 00:03:56.610 align:start position:0% the big thing that we'll probably be focusing<00:03:55.030> on<00:03:55.510> longer<00:03:55.870> term<00:03:56.049> over<00:03:56.350> like<00:03:56.470> the 00:03:56.610 --> 00:03:56.620 align:start position:0% focusing on longer term over like the 00:03:56.620 --> 00:03:58.110 align:start position:0% focusing on longer term over like the next<00:03:56.859> I<00:03:57.069> don't<00:03:57.340> know<00:03:57.400> let's<00:03:57.579> say<00:03:57.700> three<00:03:57.910> six 00:03:58.110 --> 00:03:58.120 align:start position:0% next I don't know let's say three six 00:03:58.120 --> 00:04:00.900 align:start position:0% next I don't know let's say three six months<00:03:58.209> is<00:03:58.709> a<00:03:59.709> heavy<00:04:00.069> focus<00:04:00.220> on<00:04:00.430> performance 00:04:00.900 --> 00:04:00.910 align:start position:0% months is a heavy focus on performance 00:04:00.910 --> 00:04:03.690 align:start position:0% months is a heavy focus on performance like<00:04:01.480> I<00:04:01.569> said<00:04:01.750> we're<00:04:01.900> a<00:04:01.930> Python<00:04:02.319> client<00:04:02.500> so<00:04:03.340> we 00:04:03.690 --> 00:04:03.700 align:start position:0% like I said we're a Python client so we 00:04:03.700 --> 00:04:05.190 align:start position:0% like I said we're a Python client so we kind<00:04:03.940> of<00:04:04.000> have<00:04:04.090> a<00:04:04.120> performance<00:04:04.480> penalty<00:04:04.900> we 00:04:05.190 --> 00:04:05.200 align:start position:0% kind of have a performance penalty we 00:04:05.200 --> 00:04:08.190 align:start position:0% kind of have a performance penalty we incur<00:04:05.620> de<00:04:05.950> facto<00:04:06.569> so<00:04:07.569> we'll<00:04:07.690> be<00:04:07.780> doing<00:04:08.019> a<00:04:08.079> lot 00:04:08.190 --> 00:04:08.200 align:start position:0% incur de facto so we'll be doing a lot 00:04:08.200 --> 00:04:10.559 align:start position:0% incur de facto so we'll be doing a lot of<00:04:08.380> a<00:04:08.620> lot<00:04:08.739> optimization<00:04:09.310> there<00:04:09.519> we<00:04:10.450> were 00:04:10.559 --> 00:04:10.569 align:start position:0% of a lot optimization there we were 00:04:10.569 --> 00:04:13.259 align:start position:0% of a lot optimization there we were looking<00:04:10.840> at<00:04:10.989> dropping<00:04:11.920> our<00:04:12.190> like<00:04:12.400> really<00:04:13.030> sort 00:04:13.259 --> 00:04:13.269 align:start position:0% looking at dropping our like really sort 00:04:13.269 --> 00:04:16.050 align:start position:0% looking at dropping our like really sort of<00:04:13.359> tight<00:04:13.930> loops<00:04:14.139> and<00:04:14.380> things<00:04:14.609> interests<00:04:15.609> so 00:04:16.050 --> 00:04:16.060 align:start position:0% of tight loops and things interests so 00:04:16.060 --> 00:04:17.789 align:start position:0% of tight loops and things interests so we've<00:04:16.150> had<00:04:16.239> some<00:04:16.299> work<00:04:16.570> on<00:04:16.690> like<00:04:16.870> rest<00:04:17.109> modules 00:04:17.789 --> 00:04:17.799 align:start position:0% we've had some work on like rest modules 00:04:17.799 --> 00:04:20.640 align:start position:0% we've had some work on like rest modules and<00:04:18.130> Python<00:04:18.459> which<00:04:18.609> is<00:04:18.729> fun<00:04:18.940> and<00:04:19.289> yeah<00:04:20.289> that's 00:04:20.640 --> 00:04:20.650 align:start position:0% and Python which is fun and yeah that's 00:04:20.650 --> 00:04:23.480 align:start position:0% and Python which is fun and yeah that's about<00:04:20.889> it 00:04:23.480 --> 00:04:23.490 align:start position:0% 00:04:23.490 --> 00:04:26.460 align:start position:0% hello<00:04:24.490> everyone<00:04:24.820> my<00:04:25.150> name<00:04:25.300> is<00:04:25.330> Paul<00:04:25.570> I<00:04:25.870> work<00:04:26.289> on 00:04:26.460 --> 00:04:26.470 align:start position:0% hello everyone my name is Paul I work on 00:04:26.470 --> 00:04:28.469 align:start position:0% hello everyone my name is Paul I work on lighthouse<00:04:26.890> it's<00:04:27.220> one<00:04:28.060> of<00:04:28.180> the<00:04:28.270> rust 00:04:28.469 --> 00:04:28.479 align:start position:0% lighthouse it's one of the rust 00:04:28.479 --> 00:04:30.189 align:start position:0% lighthouse it's one of the rust implementations 00:04:30.189 --> 00:04:30.199 align:start position:0% implementations 00:04:30.199 --> 00:04:31.600 align:start position:0% implementations I<00:04:30.229> think<00:04:30.979> one<00:04:31.099> of<00:04:31.129> the<00:04:31.250> great<00:04:31.370> things<00:04:31.550> that 00:04:31.600 --> 00:04:31.610 align:start position:0% I think one of the great things that 00:04:31.610 --> 00:04:34.719 align:start position:0% I think one of the great things that came<00:04:31.789> from<00:04:31.909> Interop<00:04:32.870> was<00:04:33.680> just<00:04:34.520> a<00:04:34.580> lot<00:04:34.699> of 00:04:34.719 --> 00:04:34.729 align:start position:0% came from Interop was just a lot of 00:04:34.729 --> 00:04:36.610 align:start position:0% came from Interop was just a lot of scripts<00:04:35.030> that<00:04:35.150> we<00:04:35.240> can<00:04:35.360> use<00:04:35.599> to<00:04:35.629> build<00:04:36.439> each 00:04:36.610 --> 00:04:36.620 align:start position:0% scripts that we can use to build each 00:04:36.620 --> 00:04:38.050 align:start position:0% scripts that we can use to build each other<00:04:36.770> so<00:04:36.919> Yessica<00:04:37.310> built<00:04:37.759> a<00:04:37.849> bunch<00:04:38.000> of 00:04:38.050 --> 00:04:38.060 align:start position:0% other so Yessica built a bunch of 00:04:38.060 --> 00:04:40.179 align:start position:0% other so Yessica built a bunch of scripts<00:04:38.270> which<00:04:38.419> was<00:04:38.539> great<00:04:38.740> so<00:04:39.740> now<00:04:39.889> we<00:04:39.949> have 00:04:40.179 --> 00:04:40.189 align:start position:0% scripts which was great so now we have 00:04:40.189 --> 00:04:42.029 align:start position:0% scripts which was great so now we have we<00:04:40.520> have<00:04:40.639> a<00:04:40.669> bunch<00:04:40.879> of<00:04:40.939> tools<00:04:41.120> that<00:04:41.240> we<00:04:41.389> can<00:04:41.419> use 00:04:42.029 --> 00:04:42.039 align:start position:0% we have a bunch of tools that we can use 00:04:42.039 --> 00:04:44.610 align:start position:0% we have a bunch of tools that we can use by<00:04:43.039> ourselves<00:04:43.610> to<00:04:43.759> test<00:04:43.969> with<00:04:44.120> other<00:04:44.240> clients 00:04:44.610 --> 00:04:44.620 align:start position:0% by ourselves to test with other clients 00:04:44.620 --> 00:04:47.559 align:start position:0% by ourselves to test with other clients so<00:04:45.620> that<00:04:45.770> really<00:04:45.919> helps<00:04:46.310> reduce<00:04:46.969> the<00:04:47.000> friction 00:04:47.559 --> 00:04:47.569 align:start position:0% so that really helps reduce the friction 00:04:47.569 --> 00:04:50.080 align:start position:0% so that really helps reduce the friction that<00:04:48.409> we<00:04:48.469> can<00:04:48.650> before<00:04:49.520> we<00:04:49.610> can<00:04:49.759> test<00:04:49.909> our 00:04:50.080 --> 00:04:50.090 align:start position:0% that we can before we can test our 00:04:50.090 --> 00:04:53.230 align:start position:0% that we can before we can test our client<00:04:50.360> against<00:04:50.599> others<00:04:51.969> what<00:04:52.969> we're<00:04:53.090> working 00:04:53.230 --> 00:04:53.240 align:start position:0% client against others what we're working 00:04:53.240 --> 00:04:57.399 align:start position:0% client against others what we're working on<00:04:53.509> now<00:04:54.789> after<00:04:55.789> Interop<00:04:56.210> we're<00:04:57.169> basically 00:04:57.399 --> 00:04:57.409 align:start position:0% on now after Interop we're basically 00:04:57.409 --> 00:05:00.159 align:start position:0% on now after Interop we're basically targeting<00:04:58.189> feature<00:04:58.370> completeness<00:04:59.020> we<00:05:00.020> have 00:05:00.159 --> 00:05:00.169 align:start position:0% targeting feature completeness we have 00:05:00.169 --> 00:05:02.080 align:start position:0% targeting feature completeness we have an<00:05:00.259> RFP<00:05:00.500> for<00:05:00.830> security<00:05:01.250> review<00:05:01.550> out<00:05:01.669> there<00:05:01.909> so 00:05:02.080 --> 00:05:02.090 align:start position:0% an RFP for security review out there so 00:05:02.090 --> 00:05:04.959 align:start position:0% an RFP for security review out there so we're<00:05:02.270> preparing<00:05:03.139> for<00:05:03.379> that<00:05:03.819> and<00:05:04.819> we're 00:05:04.959 --> 00:05:04.969 align:start position:0% we're preparing for that and we're 00:05:04.969 --> 00:05:08.350 align:start position:0% we're preparing for that and we're working<00:05:05.000> on<00:05:05.539> trying<00:05:06.289> to<00:05:06.379> take<00:05:06.530> a<00:05:06.560> client<00:05:07.360> into 00:05:08.350 --> 00:05:08.360 align:start position:0% working on trying to take a client into 00:05:08.360 --> 00:05:10.119 align:start position:0% working on trying to take a client into the<00:05:08.539> sort<00:05:09.259> of<00:05:09.319> the<00:05:09.379> tens<00:05:09.590> of<00:05:09.710> thousands<00:05:10.039> of 00:05:10.119 --> 00:05:10.129 align:start position:0% the sort of the tens of thousands of 00:05:10.129 --> 00:05:14.140 align:start position:0% the sort of the tens of thousands of validator<00:05:11.590> ranges<00:05:12.590> and<00:05:12.740> above<00:05:13.009> to<00:05:13.849> make<00:05:14.000> sure 00:05:14.140 --> 00:05:14.150 align:start position:0% validator ranges and above to make sure 00:05:14.150 --> 00:05:17.230 align:start position:0% validator ranges and above to make sure that<00:05:14.300> we<00:05:14.419> can<00:05:14.710> run<00:05:15.710> nice<00:05:16.400> and<00:05:16.639> quickly<00:05:16.819> and 00:05:17.230 --> 00:05:17.240 align:start position:0% that we can run nice and quickly and 00:05:17.240 --> 00:05:20.010 align:start position:0% that we can run nice and quickly and efficiently<00:05:17.479> with<00:05:18.319> production<00:05:19.250> level 00:05:20.010 --> 00:05:20.020 align:start position:0% efficiently with production level 00:05:20.020 --> 00:05:26.080 align:start position:0% efficiently with production level numbers<00:05:21.020> of<00:05:21.110> validated<00:05:24.400> I'm<00:05:25.400> sorry<00:05:25.759> from<00:05:26.029> the 00:05:26.080 --> 00:05:26.090 align:start position:0% numbers of validated I'm sorry from the 00:05:26.090 --> 00:05:29.140 align:start position:0% numbers of validated I'm sorry from the Nimbus<00:05:26.629> team<00:05:27.430> lesson<00:05:28.430> that<00:05:28.550> we<00:05:28.789> learned<00:05:29.060> from 00:05:29.140 --> 00:05:29.150 align:start position:0% Nimbus team lesson that we learned from 00:05:29.150 --> 00:05:31.179 align:start position:0% Nimbus team lesson that we learned from Interop<00:05:29.629> I<00:05:29.779> guess<00:05:29.990> is<00:05:30.139> the<00:05:30.319> importance<00:05:31.039> of 00:05:31.179 --> 00:05:31.189 align:start position:0% Interop I guess is the importance of 00:05:31.189 --> 00:05:34.480 align:start position:0% Interop I guess is the importance of testing<00:05:31.900> our<00:05:32.900> success<00:05:33.469> was<00:05:33.680> largely<00:05:34.069> due<00:05:34.400> to 00:05:34.480 --> 00:05:34.490 align:start position:0% testing our success was largely due to 00:05:34.490 --> 00:05:37.149 align:start position:0% testing our success was largely due to the<00:05:34.819> very<00:05:35.569> well-prepared<00:05:35.900> a<00:05:36.229> suit<00:05:36.529> and<00:05:36.740> where 00:05:37.149 --> 00:05:37.159 align:start position:0% the very well-prepared a suit and where 00:05:37.159 --> 00:05:39.550 align:start position:0% the very well-prepared a suit and where there<00:05:37.460> was<00:05:37.990> bumps<00:05:38.990> along<00:05:39.110> the<00:05:39.259> road 00:05:39.550 --> 00:05:39.560 align:start position:0% there was bumps along the road 00:05:39.560 --> 00:05:42.490 align:start position:0% there was bumps along the road this<00:05:40.159> is<00:05:40.370> places<00:05:41.330> where<00:05:41.479> the<00:05:41.599> tests<00:05:42.020> are<00:05:42.229> kind 00:05:42.490 --> 00:05:42.500 align:start position:0% this is places where the tests are kind 00:05:42.500 --> 00:05:46.990 align:start position:0% this is places where the tests are kind of<00:05:42.620> missing<00:05:42.889> I<00:05:44.319> would<00:05:45.319> repeat<00:05:45.620> what<00:05:45.680> what<00:05:46.069> Paul 00:05:46.990 --> 00:05:47.000 align:start position:0% of missing I would repeat what what Paul 00:05:47.000 --> 00:05:48.790 align:start position:0% of missing I would repeat what what Paul said<00:05:47.240> that<00:05:47.449> one<00:05:47.839> of<00:05:47.870> the<00:05:48.080> most<00:05:48.409> valuable 00:05:48.790 --> 00:05:48.800 align:start position:0% said that one of the most valuable 00:05:48.800 --> 00:05:51.430 align:start position:0% said that one of the most valuable takeaways<00:05:49.789> was<00:05:50.029> these<00:05:50.270> scripts<00:05:50.750> that<00:05:51.169> allow 00:05:51.430 --> 00:05:51.440 align:start position:0% takeaways was these scripts that allow 00:05:51.440 --> 00:05:55.180 align:start position:0% takeaways was these scripts that allow us<00:05:51.469> now<00:05:51.800> to<00:05:51.860> run<00:05:52.339> multi<00:05:53.089> client<00:05:53.360> s<00:05:53.539> nets<00:05:54.190> and 00:05:55.180 --> 00:05:55.190 align:start position:0% us now to run multi client s nets and 00:05:55.190 --> 00:05:57.879 align:start position:0% us now to run multi client s nets and now<00:05:55.430> I<00:05:55.879> think<00:05:56.120> we<00:05:56.509> should<00:05:56.690> all<00:05:57.080> keep<00:05:57.289> improving 00:05:57.879 --> 00:05:57.889 align:start position:0% now I think we should all keep improving 00:05:57.889 --> 00:06:01.659 align:start position:0% now I think we should all keep improving on<00:05:58.639> them<00:05:58.879> and<00:06:00.039> regarding<00:06:01.039> the<00:06:01.219> future<00:06:01.520> of 00:06:01.659 --> 00:06:01.669 align:start position:0% on them and regarding the future of 00:06:01.669 --> 00:06:04.269 align:start position:0% on them and regarding the future of Nimbus<00:06:02.509> plant<00:06:02.750> will<00:06:03.050> be<00:06:03.080> planning<00:06:03.860> we'll<00:06:04.099> be 00:06:04.269 --> 00:06:04.279 align:start position:0% Nimbus plant will be planning we'll be 00:06:04.279 --> 00:06:06.909 align:start position:0% Nimbus plant will be planning we'll be publishing<00:06:04.699> very<00:06:05.150> shortly<00:06:05.539> our<00:06:05.900> roadmap<00:06:06.589> for 00:06:06.909 --> 00:06:06.919 align:start position:0% publishing very shortly our roadmap for 00:06:06.919 --> 00:06:10.149 align:start position:0% publishing very shortly our roadmap for getting<00:06:07.310> Nimbus<00:06:07.759> production<00:06:08.479> ready<00:06:08.659> and<00:06:09.159> we 00:06:10.149 --> 00:06:10.159 align:start position:0% getting Nimbus production ready and we 00:06:10.159 --> 00:06:14.459 align:start position:0% getting Nimbus production ready and we hope<00:06:10.550> to<00:06:10.699> do<00:06:10.789> that<00:06:10.819> in<00:06:11.240> the<00:06:11.330> next<00:06:11.599> six<00:06:12.020> months 00:06:14.459 --> 00:06:14.469 align:start position:0% 00:06:14.469 --> 00:06:17.469 align:start position:0% hi<00:06:15.469> I'm<00:06:15.889> Desmond<00:06:16.339> from<00:06:17.089> wrong<00:06:17.300> time 00:06:17.469 --> 00:06:17.479 align:start position:0% hi I'm Desmond from wrong time 00:06:17.479 --> 00:06:21.969 align:start position:0% hi I'm Desmond from wrong time verification<00:06:18.139> so<00:06:18.440> we<00:06:19.300> developed<00:06:20.300> a<00:06:20.830> kind<00:06:21.830> of 00:06:21.969 --> 00:06:21.979 align:start position:0% verification so we developed a kind of 00:06:21.979 --> 00:06:25.269 align:start position:0% verification so we developed a kind of client<00:06:22.460> but<00:06:23.419> we<00:06:23.690> are<00:06:23.839> not<00:06:24.349> really<00:06:24.800> just 00:06:25.269 --> 00:06:25.279 align:start position:0% client but we are not really just 00:06:25.279 --> 00:06:27.249 align:start position:0% client but we are not really just running<00:06:25.639> the<00:06:25.729> client<00:06:26.000> but<00:06:26.259> formally 00:06:27.249 --> 00:06:27.259 align:start position:0% running the client but formally 00:06:27.259 --> 00:06:31.180 align:start position:0% running the client but formally verifying<00:06:27.680> the<00:06:27.800> client<00:06:28.190> so<00:06:29.080> but<00:06:30.080> I<00:06:30.440> hope 00:06:31.180 --> 00:06:31.190 align:start position:0% verifying the client so but I hope 00:06:31.190 --> 00:06:35.320 align:start position:0% verifying the client so but I hope there's<00:06:31.460> some<00:06:31.610> crazy<00:06:32.979> idea<00:06:33.979> of<00:06:34.159> crazy<00:06:34.400> users 00:06:35.320 --> 00:06:35.330 align:start position:0% there's some crazy idea of crazy users 00:06:35.330 --> 00:06:41.249 align:start position:0% there's some crazy idea of crazy users use<00:06:36.020> our<00:06:36.229> K<00:06:36.669> client<00:06:37.669> as<00:06:39.430> just<00:06:40.430> adding<00:06:40.909> another 00:06:41.249 --> 00:06:41.259 align:start position:0% use our K client as just adding another 00:06:41.259 --> 00:06:43.060 align:start position:0% use our K client as just adding another diversity 00:06:43.060 --> 00:06:43.070 align:start position:0% diversity 00:06:43.070 --> 00:06:47.350 align:start position:0% diversity and<00:06:43.240> yeah<00:06:44.240> but<00:06:44.720> yeah<00:06:45.320> so<00:06:45.530> far<00:06:45.740> we<00:06:45.830> just<00:06:46.360> for 00:06:47.350 --> 00:06:47.360 align:start position:0% and yeah but yeah so far we just for 00:06:47.360 --> 00:06:48.040 align:start position:0% and yeah but yeah so far we just for verification 00:06:48.040 --> 00:06:48.050 align:start position:0% verification 00:06:48.050 --> 00:06:57.820 align:start position:0% verification first<00:06:54.220> though<00:06:55.220> my<00:06:55.730> name<00:06:55.910> is<00:06:56.060> Mikhail<00:06:56.480> I'm<00:06:57.350> from 00:06:57.820 --> 00:06:57.830 align:start position:0% first though my name is Mikhail I'm from 00:06:57.830 --> 00:07:01.270 align:start position:0% first though my name is Mikhail I'm from harmony<00:06:58.430> team<00:06:58.670> and<00:06:59.200> the<00:07:00.200> Interop<00:07:00.590> went<00:07:00.920> very 00:07:01.270 --> 00:07:01.280 align:start position:0% harmony team and the Interop went very 00:07:01.280 --> 00:07:01.600 align:start position:0% harmony team and the Interop went very well 00:07:01.600 --> 00:07:01.610 align:start position:0% well 00:07:01.610 --> 00:07:05.710 align:start position:0% well and<00:07:01.880> I<00:07:02.810> even<00:07:03.620> didn't<00:07:04.130> expect<00:07:04.520> it<00:07:04.730> it<00:07:05.120> was<00:07:05.390> so 00:07:05.710 --> 00:07:05.720 align:start position:0% and I even didn't expect it it was so 00:07:05.720 --> 00:07:10.630 align:start position:0% and I even didn't expect it it was so productive<00:07:07.150> as<00:07:08.320> a<00:07:09.320> follow<00:07:09.740> ups<00:07:10.010> we<00:07:10.580> are 00:07:10.630 --> 00:07:10.640 align:start position:0% productive as a follow ups we are 00:07:10.640 --> 00:07:13.900 align:start position:0% productive as a follow ups we are continuing<00:07:11.420> to<00:07:11.450> work<00:07:11.750> on<00:07:12.050> EV<00:07:12.460> fork<00:07:13.460> choice 00:07:13.900 --> 00:07:13.910 align:start position:0% continuing to work on EV fork choice 00:07:13.910 --> 00:07:19.360 align:start position:0% continuing to work on EV fork choice tests<00:07:14.660> like<00:07:15.140> a<00:07:15.200> complex<00:07:15.710> test<00:07:17.050> also<00:07:18.050> we<00:07:18.920> need 00:07:19.360 --> 00:07:19.370 align:start position:0% tests like a complex test also we need 00:07:19.370 --> 00:07:24.190 align:start position:0% tests like a complex test also we need to<00:07:19.490> finish<00:07:19.760> sync<00:07:20.480> and<00:07:22.420> was<00:07:23.420> thinking<00:07:23.750> about 00:07:24.190 --> 00:07:24.200 align:start position:0% to finish sync and was thinking about 00:07:24.200 --> 00:07:26.950 align:start position:0% to finish sync and was thinking about start<00:07:24.830> working<00:07:25.280> on<00:07:25.400> Bella<00:07:25.760> stuff<00:07:26.060> finished<00:07:26.840> in 00:07:26.950 --> 00:07:26.960 align:start position:0% start working on Bella stuff finished in 00:07:26.960 --> 00:07:29.710 align:start position:0% start working on Bella stuff finished in discovery<00:07:27.440> and<00:07:27.760> the<00:07:28.760> main<00:07:28.970> takeaway<00:07:29.660> from 00:07:29.710 --> 00:07:29.720 align:start position:0% discovery and the main takeaway from 00:07:29.720 --> 00:07:31.990 align:start position:0% discovery and the main takeaway from interrupts<00:07:30.440> that<00:07:30.590> we<00:07:30.950> are<00:07:31.100> merging<00:07:31.430> efforts 00:07:31.990 --> 00:07:32.000 align:start position:0% interrupts that we are merging efforts 00:07:32.000 --> 00:07:37.090 align:start position:0% interrupts that we are merging efforts with<00:07:32.270> Artemis<00:07:32.720> so<00:07:33.440> we<00:07:33.620> probably<00:07:33.830> can<00:07:36.100> avoid 00:07:37.090 --> 00:07:37.100 align:start position:0% with Artemis so we probably can avoid 00:07:37.100 --> 00:07:40.810 align:start position:0% with Artemis so we probably can avoid this<00:07:37.430> production<00:07:38.240> really<00:07:38.570> stuff<00:07:38.960> so<00:07:39.230> yeah<00:07:39.820> ok 00:07:40.810 --> 00:07:40.820 align:start position:0% this production really stuff so yeah ok 00:07:40.820 --> 00:07:48.070 align:start position:0% this production really stuff so yeah ok that's<00:07:41.090> it<00:07:41.300> I'm<00:07:43.240> away<00:07:44.240> from<00:07:44.630> party<00:07:45.470> so<00:07:46.250> I<00:07:47.080> think 00:07:48.070 --> 00:07:48.080 align:start position:0% that's it I'm away from party so I think 00:07:48.080 --> 00:07:53.170 align:start position:0% that's it I'm away from party so I think I<00:07:49.090> I<00:07:50.090> didn't<00:07:50.780> join<00:07:50.960> the<00:07:51.320> interval<00:07:51.920> on<00:07:52.340> site<00:07:52.700> but 00:07:53.170 --> 00:07:53.180 align:start position:0% I I didn't join the interval on site but 00:07:53.180 --> 00:07:55.630 align:start position:0% I I didn't join the interval on site but I<00:07:53.210> was<00:07:53.690> doing<00:07:54.470> some<00:07:54.770> similar<00:07:55.220> interrupts 00:07:55.630 --> 00:07:55.640 align:start position:0% I was doing some similar interrupts 00:07:55.640 --> 00:07:58.930 align:start position:0% I was doing some similar interrupts stuff<00:07:56.200> at<00:07:57.200> home<00:07:57.440> trying<00:07:58.130> to<00:07:58.250> get<00:07:58.370> it<00:07:58.520> work 00:07:58.930 --> 00:07:58.940 align:start position:0% stuff at home trying to get it work 00:07:58.940 --> 00:08:01.330 align:start position:0% stuff at home trying to get it work put<00:07:59.120> them<00:07:59.330> all<00:07:59.480> nice<00:07:59.720> it<00:08:00.080> mostly<00:08:00.770> works<00:08:01.100> I 00:08:01.330 --> 00:08:01.340 align:start position:0% put them all nice it mostly works I 00:08:01.340 --> 00:08:04.180 align:start position:0% put them all nice it mostly works I think<00:08:01.370> the<00:08:01.850> most<00:08:02.380> important<00:08:03.380> lessons<00:08:03.830> we 00:08:04.180 --> 00:08:04.190 align:start position:0% think the most important lessons we 00:08:04.190 --> 00:08:08.920 align:start position:0% think the most important lessons we learn<00:08:04.400> is<00:08:04.640> to<00:08:04.670> testing<00:08:05.570> so<00:08:06.220> we<00:08:07.220> were<00:08:07.750> while<00:08:08.750> or 00:08:08.920 --> 00:08:08.930 align:start position:0% learn is to testing so we were while or 00:08:08.930 --> 00:08:11.760 align:start position:0% learn is to testing so we were while or to<00:08:09.200> patched<00:08:09.530> version<00:08:09.620> behind<00:08:10.250> but<00:08:10.490> even<00:08:10.850> even 00:08:11.760 --> 00:08:11.770 align:start position:0% to patched version behind but even even 00:08:11.770 --> 00:08:15.460 align:start position:0% to patched version behind but even even except<00:08:12.770> that<00:08:12.950> we<00:08:13.280> still<00:08:13.550> have<00:08:13.790> like<00:08:14.180> power<00:08:15.140> to 00:08:15.460 --> 00:08:15.470 align:start position:0% except that we still have like power to 00:08:15.470 --> 00:08:17.380 align:start position:0% except that we still have like power to consciousness<00:08:15.920> bugs<00:08:16.370> from<00:08:16.790> drawing<00:08:17.270> the 00:08:17.380 --> 00:08:17.390 align:start position:0% consciousness bugs from drawing the 00:08:17.390 --> 00:08:20.010 align:start position:0% consciousness bugs from drawing the interrupts<00:08:17.840> that<00:08:18.050> doesn't<00:08:18.920> pick<00:08:19.070> up<00:08:19.250> the<00:08:19.640> test 00:08:20.010 --> 00:08:20.020 align:start position:0% interrupts that doesn't pick up the test 00:08:20.020 --> 00:08:22.540 align:start position:0% interrupts that doesn't pick up the test doesn't<00:08:21.020> pick<00:08:21.140> up<00:08:21.290> by<00:08:21.410> the<00:08:21.440> tests<00:08:21.740> we<00:08:22.160> pass<00:08:22.400> all 00:08:22.540 --> 00:08:22.550 align:start position:0% doesn't pick up by the tests we pass all 00:08:22.550 --> 00:08:25.000 align:start position:0% doesn't pick up by the tests we pass all the<00:08:22.730> tests<00:08:22.940> before<00:08:23.330> so<00:08:24.140> I<00:08:24.170> think<00:08:24.500> that's<00:08:24.770> the 00:08:25.000 --> 00:08:25.010 align:start position:0% the tests before so I think that's the 00:08:25.010 --> 00:08:27.400 align:start position:0% the tests before so I think that's the biggest<00:08:25.340> lesson<00:08:25.850> we<00:08:26.150> learned<00:08:26.360> testing<00:08:27.320> is 00:08:27.400 --> 00:08:27.410 align:start position:0% biggest lesson we learned testing is 00:08:27.410 --> 00:08:31.690 align:start position:0% biggest lesson we learned testing is really<00:08:27.650> important<00:08:29.530> also<00:08:30.530> I<00:08:30.770> forgot<00:08:31.100> to<00:08:31.490> say 00:08:31.690 --> 00:08:31.700 align:start position:0% really important also I forgot to say 00:08:31.700 --> 00:08:35.230 align:start position:0% really important also I forgot to say that<00:08:31.730> we<00:08:32.570> tested<00:08:33.099> GBM<00:08:34.099> the<00:08:34.250> p2p<00:08:34.580> as<00:08:34.820> well<00:08:35.030> as 00:08:35.230 --> 00:08:35.240 align:start position:0% that we tested GBM the p2p as well as 00:08:35.240 --> 00:08:38.770 align:start position:0% that we tested GBM the p2p as well as our<00:08:35.419> client<00:08:36.020> and<00:08:36.169> he<00:08:36.830> fixed<00:08:37.550> some<00:08:38.120> bugs<00:08:38.150> and 00:08:38.770 --> 00:08:38.780 align:start position:0% our client and he fixed some bugs and 00:08:38.780 --> 00:08:42.850 align:start position:0% our client and he fixed some bugs and it's<00:08:39.169> now<00:08:39.460> compatible<00:08:40.460> at<00:08:40.849> least<00:08:41.570> the<00:08:42.349> stag 00:08:42.850 --> 00:08:42.860 align:start position:0% it's now compatible at least the stag 00:08:42.860 --> 00:08:44.860 align:start position:0% it's now compatible at least the stag that<00:08:43.099> used<00:08:43.400> for<00:08:43.520> Interop<00:08:44.090> is<00:08:44.300> now<00:08:44.450> compatible 00:08:44.860 --> 00:08:44.870 align:start position:0% that used for Interop is now compatible 00:08:44.870 --> 00:08:47.800 align:start position:0% that used for Interop is now compatible with<00:08:45.380> all<00:08:46.190> other<00:08:46.670> implementation<00:08:47.600> like 00:08:47.800 --> 00:08:47.810 align:start position:0% with all other implementation like 00:08:47.810 --> 00:08:53.900 align:start position:0% with all other implementation like JavaScript<00:08:48.620> Python<00:08:48.890> and<00:08:49.490> rust<00:08:50.060> and<00:08:50.270> you 00:08:53.900 --> 00:08:53.910 align:start position:0% 00:08:53.910 --> 00:08:56.389 align:start position:0% I<00:08:53.940> also<00:08:54.779> just<00:08:54.899> wanted<00:08:55.139> to<00:08:55.230> use<00:08:55.709> this<00:08:55.920> moment<00:08:56.220> to 00:08:56.389 --> 00:08:56.399 align:start position:0% I also just wanted to use this moment to 00:08:56.399 --> 00:08:59.150 align:start position:0% I also just wanted to use this moment to toss<00:08:56.610> out<00:08:56.790> a<00:08:56.819> PSA<00:08:57.360> we're<00:08:58.259> all<00:08:58.470> using<00:08:58.889> the<00:08:59.130> same 00:08:59.150 --> 00:08:59.160 align:start position:0% toss out a PSA we're all using the same 00:08:59.160 --> 00:09:01.759 align:start position:0% toss out a PSA we're all using the same BLS<00:08:59.940> library<00:09:00.420> at<00:09:00.509> the<00:09:00.600> moment<00:09:00.899> I<00:09:01.019> believe<00:09:01.380> yeah 00:09:01.759 --> 00:09:01.769 align:start position:0% BLS library at the moment I believe yeah 00:09:01.769 --> 00:09:04.280 align:start position:0% BLS library at the moment I believe yeah so<00:09:02.699> if<00:09:03.000> anyone<00:09:03.600> out<00:09:03.630> there<00:09:03.750> wants<00:09:04.050> to<00:09:04.139> write 00:09:04.280 --> 00:09:04.290 align:start position:0% so if anyone out there wants to write 00:09:04.290 --> 00:09:05.780 align:start position:0% so if anyone out there wants to write it'd<00:09:04.410> be<00:09:04.470> a<00:09:04.500> lot<00:09:04.620> of<00:09:04.709> implementation<00:09:05.399> more 00:09:05.780 --> 00:09:05.790 align:start position:0% it'd be a lot of implementation more 00:09:05.790 --> 00:09:10.370 align:start position:0% it'd be a lot of implementation more implementations<00:09:06.329> is<00:09:06.480> better<00:09:08.930> on<00:09:09.930> the<00:09:10.079> note<00:09:10.230> of 00:09:10.370 --> 00:09:10.380 align:start position:0% implementations is better on the note of 00:09:10.380 --> 00:09:12.490 align:start position:0% implementations is better on the note of bilis<00:09:11.069> implementations<00:09:11.850> the 00:09:12.490 --> 00:09:12.500 align:start position:0% bilis implementations the 00:09:12.500 --> 00:09:13.970 align:start position:0% bilis implementations the standardization<00:09:13.500> efforts<00:09:13.740> have<00:09:13.860> been 00:09:13.970 --> 00:09:13.980 align:start position:0% standardization efforts have been 00:09:13.980 --> 00:09:17.240 align:start position:0% standardization efforts have been charging<00:09:14.639> forward<00:09:15.050> and<00:09:16.050> we<00:09:16.740> have<00:09:16.769> some<00:09:17.100> more 00:09:17.240 --> 00:09:17.250 align:start position:0% charging forward and we have some more 00:09:17.250 --> 00:09:19.460 align:start position:0% charging forward and we have some more reference<00:09:17.579> implementations<00:09:18.329> from<00:09:18.930> those 00:09:19.460 --> 00:09:19.470 align:start position:0% reference implementations from those 00:09:19.470 --> 00:09:22.910 align:start position:0% reference implementations from those efforts<00:09:19.949> so<00:09:21.199> hopefully<00:09:22.199> within<00:09:22.380> the<00:09:22.500> next<00:09:22.589> 1 00:09:22.910 --> 00:09:22.920 align:start position:0% efforts so hopefully within the next 1 00:09:22.920 --> 00:09:24.650 align:start position:0% efforts so hopefully within the next 1 month<00:09:23.100> or<00:09:23.250> so<00:09:23.370> we<00:09:23.519> should<00:09:23.670> have<00:09:23.850> what<00:09:24.209> is<00:09:24.329> the 00:09:24.650 --> 00:09:24.660 align:start position:0% month or so we should have what is the 00:09:24.660 --> 00:09:27.829 align:start position:0% month or so we should have what is the final<00:09:25.470> specification<00:09:26.100> for<00:09:26.310> pls<00:09:26.699> and<00:09:27.569> which<00:09:27.720> is 00:09:27.829 --> 00:09:27.839 align:start position:0% final specification for pls and which is 00:09:27.839 --> 00:09:29.569 align:start position:0% final specification for pls and which is really<00:09:27.959> a<00:09:28.079> major<00:09:28.470> step<00:09:28.740> forward<00:09:29.040> and<00:09:29.160> means 00:09:29.569 --> 00:09:29.579 align:start position:0% really a major step forward and means 00:09:29.579 --> 00:09:32.030 align:start position:0% really a major step forward and means that<00:09:29.670> basically<00:09:30.089> then<00:09:30.569> that's<00:09:31.139> the<00:09:31.350> me<00:09:31.920> the 00:09:32.030 --> 00:09:32.040 align:start position:0% that basically then that's the me the 00:09:32.040 --> 00:09:33.860 align:start position:0% that basically then that's the me the last<00:09:32.190> hurdle<00:09:32.459> in<00:09:32.759> terms<00:09:32.940> of<00:09:33.089> specification 00:09:33.860 --> 00:09:33.870 align:start position:0% last hurdle in terms of specification 00:09:33.870 --> 00:09:38.680 align:start position:0% last hurdle in terms of specification that's<00:09:34.050> left<00:09:35.660> you<00:09:36.660> know<00:09:36.720> so<00:09:36.930> moving<00:09:37.589> on<00:09:37.740> and 00:09:38.680 --> 00:09:38.690 align:start position:0% that's left you know so moving on and 00:09:38.690 --> 00:09:42.079 align:start position:0% that's left you know so moving on and we've<00:09:39.690> had<00:09:39.899> all<00:09:40.079> these<00:09:40.290> these<00:09:41.100> interoperate 00:09:42.079 --> 00:09:42.089 align:start position:0% we've had all these these interoperate 00:09:42.089 --> 00:09:44.930 align:start position:0% we've had all these these interoperate events<00:09:42.569> but<00:09:42.839> we<00:09:43.620> need<00:09:44.069> to<00:09:44.220> now<00:09:44.519> start 00:09:44.930 --> 00:09:44.940 align:start position:0% events but we need to now start 00:09:44.940 --> 00:09:47.870 align:start position:0% events but we need to now start transitioning<00:09:45.180> to<00:09:45.660> more<00:09:46.589> organic<00:09:47.220> starting 00:09:47.870 --> 00:09:47.880 align:start position:0% transitioning to more organic starting 00:09:47.880 --> 00:09:50.110 align:start position:0% transitioning to more organic starting up<00:09:48.000> of<00:09:48.149> these<00:09:48.269> events<00:09:48.690> and<00:09:48.870> and<00:09:49.259> allowing 00:09:50.110 --> 00:09:50.120 align:start position:0% up of these events and and allowing 00:09:50.120 --> 00:09:53.240 align:start position:0% up of these events and and allowing nodes<00:09:51.290> clients<00:09:52.290> to<00:09:52.410> properly<00:09:52.769> sync<00:09:53.009> with<00:09:53.100> one 00:09:53.240 --> 00:09:53.250 align:start position:0% nodes clients to properly sync with one 00:09:53.250 --> 00:09:57.139 align:start position:0% nodes clients to properly sync with one another<00:09:53.630> with<00:09:54.630> with<00:09:55.550> we<00:09:56.550> previously<00:09:56.819> used 00:09:57.139 --> 00:09:57.149 align:start position:0% another with with we previously used 00:09:57.149 --> 00:10:00.350 align:start position:0% another with with we previously used scripts<00:09:57.839> and<00:09:58.079> files<00:09:58.949> to<00:09:59.100> start<00:09:59.430> up<00:09:59.550> these 00:10:00.350 --> 00:10:00.360 align:start position:0% scripts and files to start up these 00:10:00.360 --> 00:10:04.069 align:start position:0% scripts and files to start up these these<00:10:00.569> test<00:10:00.810> Nets<00:10:01.019> but<00:10:01.230> to<00:10:01.800> have<00:10:02.009> more<00:10:03.079> we 00:10:04.069 --> 00:10:04.079 align:start position:0% these test Nets but to have more we 00:10:04.079 --> 00:10:05.720 align:start position:0% these test Nets but to have more we allow<00:10:04.350> validators<00:10:05.100> to<00:10:05.220> join<00:10:05.399> into<00:10:05.579> your 00:10:05.720 --> 00:10:05.730 align:start position:0% allow validators to join into your 00:10:05.730 --> 00:10:08.749 align:start position:0% allow validators to join into your network<00:10:05.880> and<00:10:06.500> transitioning<00:10:07.500> into<00:10:07.759> proper 00:10:08.749 --> 00:10:08.759 align:start position:0% network and transitioning into proper 00:10:08.759 --> 00:10:11.240 align:start position:0% network and transitioning into proper test<00:10:08.970> nets<00:10:09.259> so<00:10:10.259> I<00:10:10.290> would<00:10:10.620> be<00:10:10.800> interested<00:10:11.160> to 00:10:11.240 --> 00:10:11.250 align:start position:0% test nets so I would be interested to 00:10:11.250 --> 00:10:15.230 align:start position:0% test nets so I would be interested to hear<00:10:11.279> comments<00:10:11.610> on<00:10:12.740> what<00:10:13.740> how<00:10:14.459> we<00:10:14.759> can<00:10:15.000> do<00:10:15.120> this 00:10:15.230 --> 00:10:15.240 align:start position:0% hear comments on what how we can do this 00:10:15.240 --> 00:10:16.939 align:start position:0% hear comments on what how we can do this and<00:10:15.509> sort<00:10:15.689> of<00:10:15.750> what<00:10:15.810> are<00:10:15.990> the<00:10:16.050> challenges<00:10:16.079> and 00:10:16.939 --> 00:10:16.949 align:start position:0% and sort of what are the challenges and 00:10:16.949 --> 00:10:23.470 align:start position:0% and sort of what are the challenges and what<00:10:17.220> are<00:10:17.310> the<00:10:17.370> next<00:10:17.490> steps<00:10:17.759> in<00:10:18.000> these<00:10:18.540> regards 00:10:23.470 --> 00:10:23.480 align:start position:0% 00:10:23.480 --> 00:10:28.009 align:start position:0% yeah<00:10:24.480> so<00:10:24.839> I<00:10:24.870> think<00:10:25.139> a<00:10:25.769> huge<00:10:26.459> step<00:10:27.209> forward<00:10:27.810> from 00:10:28.009 --> 00:10:28.019 align:start position:0% yeah so I think a huge step forward from 00:10:28.019 --> 00:10:30.350 align:start position:0% yeah so I think a huge step forward from what<00:10:28.110> we<00:10:28.259> had<00:10:28.470> at<00:10:28.589> Interop<00:10:28.949> would<00:10:29.490> be<00:10:29.670> sort<00:10:30.269> of 00:10:30.350 --> 00:10:30.360 align:start position:0% what we had at Interop would be sort of 00:10:30.360 --> 00:10:33.800 align:start position:0% what we had at Interop would be sort of testing<00:10:30.899> out<00:10:31.199> our<00:10:31.649> eighth<00:10:32.399> one<00:10:32.699> integration<00:10:33.420> I 00:10:33.800 --> 00:10:33.810 align:start position:0% testing out our eighth one integration I 00:10:33.810 --> 00:10:35.990 align:start position:0% testing out our eighth one integration I think<00:10:34.470> most<00:10:34.860> of<00:10:34.980> clients<00:10:35.310> have<00:10:35.430> at<00:10:35.610> least<00:10:35.699> some 00:10:35.990 --> 00:10:36.000 align:start position:0% think most of clients have at least some 00:10:36.000 --> 00:10:38.569 align:start position:0% think most of clients have at least some form<00:10:36.810> of<00:10:36.899> it<00:10:37.079> but<00:10:37.920> essentially<00:10:38.250> this<00:10:38.339> would<00:10:38.430> be 00:10:38.569 --> 00:10:38.579 align:start position:0% form of it but essentially this would be 00:10:38.579 --> 00:10:41.030 align:start position:0% form of it but essentially this would be like<00:10:38.759> having<00:10:39.029> you<00:10:39.389> know<00:10:39.509> some<00:10:39.870> eath<00:10:40.500> one<00:10:40.769> test 00:10:41.030 --> 00:10:41.040 align:start position:0% like having you know some eath one test 00:10:41.040 --> 00:10:43.759 align:start position:0% like having you know some eath one test nut<00:10:41.449> ideally<00:10:42.449> one<00:10:42.600> that<00:10:42.630> we<00:10:43.350> kind<00:10:43.529> of<00:10:43.589> all 00:10:43.759 --> 00:10:43.769 align:start position:0% nut ideally one that we kind of all 00:10:43.769 --> 00:10:46.699 align:start position:0% nut ideally one that we kind of all could<00:10:43.980> easily<00:10:44.779> for<00:10:45.779> example<00:10:45.810> produce<00:10:46.439> eath 00:10:46.699 --> 00:10:46.709 align:start position:0% could easily for example produce eath 00:10:46.709 --> 00:10:49.120 align:start position:0% could easily for example produce eath for<00:10:47.040> or<00:10:47.459> spin<00:10:48.209> up<00:10:48.300> or<00:10:48.329> spin<00:10:48.389> down<00:10:48.540> as<00:10:48.750> we<00:10:48.870> need 00:10:49.120 --> 00:10:49.130 align:start position:0% for or spin up or spin down as we need 00:10:49.130 --> 00:10:52.069 align:start position:0% for or spin up or spin down as we need and<00:10:50.130> then<00:10:50.250> use<00:10:50.430> that<00:10:50.459> to<00:10:50.670> kind<00:10:50.970> of<00:10:51.120> test<00:10:51.509> ok 00:10:52.069 --> 00:10:52.079 align:start position:0% and then use that to kind of test ok 00:10:52.079 --> 00:10:53.420 align:start position:0% and then use that to kind of test ok like<00:10:52.319> you're<00:10:52.470> saying<00:10:52.740> here's<00:10:52.980> a<00:10:53.040> real<00:10:53.310> world 00:10:53.420 --> 00:10:53.430 align:start position:0% like you're saying here's a real world 00:10:53.430 --> 00:10:55.160 align:start position:0% like you're saying here's a real world setting<00:10:53.730> where<00:10:54.149> it's<00:10:54.300> like<00:10:54.480> there's<00:10:54.720> no<00:10:54.899> eath 00:10:55.160 --> 00:10:55.170 align:start position:0% setting where it's like there's no eath 00:10:55.170 --> 00:10:57.350 align:start position:0% setting where it's like there's no eath one<00:10:55.439> network<00:10:55.620> we<00:10:56.399> then<00:10:56.550> have<00:10:56.730> this<00:10:56.939> if<00:10:57.149> to 00:10:57.350 --> 00:10:57.360 align:start position:0% one network we then have this if to 00:10:57.360 --> 00:10:59.749 align:start position:0% one network we then have this if to deployment<00:10:57.889> how<00:10:58.889> can<00:10:59.100> we<00:10:59.189> actually<00:10:59.610> have 00:10:59.749 --> 00:10:59.759 align:start position:0% deployment how can we actually have 00:10:59.759 --> 00:11:02.780 align:start position:0% deployment how can we actually have validators<00:11:00.269> join<00:11:01.079> and<00:11:01.529> leave<00:11:01.579> but<00:11:02.579> mainly 00:11:02.780 --> 00:11:02.790 align:start position:0% validators join and leave but mainly 00:11:02.790 --> 00:11:03.910 align:start position:0% validators join and leave but mainly join 00:11:03.910 --> 00:11:03.920 align:start position:0% join 00:11:03.920 --> 00:11:05.290 align:start position:0% join [Music] 00:11:05.290 --> 00:11:05.300 align:start position:0% [Music] 00:11:05.300 --> 00:11:08.449 align:start position:0% [Music] yeah<00:11:06.300> I<00:11:07.130> think<00:11:08.130> it's<00:11:08.310> time<00:11:08.430> for 00:11:08.449 --> 00:11:08.459 align:start position:0% yeah I think it's time for 00:11:08.459 --> 00:11:10.280 align:start position:0% yeah I think it's time for specialization<00:11:09.180> I<00:11:09.509> think<00:11:09.899> we're<00:11:10.019> gonna<00:11:10.110> see 00:11:10.280 --> 00:11:10.290 align:start position:0% specialization I think we're gonna see 00:11:10.290 --> 00:11:12.139 align:start position:0% specialization I think we're gonna see like<00:11:10.560> all<00:11:10.709> the<00:11:10.829> clients<00:11:11.250> at<00:11:11.370> this<00:11:11.490> point<00:11:11.790> now 00:11:12.139 --> 00:11:12.149 align:start position:0% like all the clients at this point now 00:11:12.149 --> 00:11:13.550 align:start position:0% like all the clients at this point now that<00:11:12.180> we<00:11:12.360> know<00:11:12.480> we<00:11:12.570> can<00:11:12.600> talk<00:11:12.899> and<00:11:13.139> we<00:11:13.410> know 00:11:13.550 --> 00:11:13.560 align:start position:0% that we know we can talk and we know 00:11:13.560 --> 00:11:14.870 align:start position:0% that we know we can talk and we know like<00:11:13.740> we<00:11:13.860> have<00:11:13.889> a<00:11:14.009> baseline<00:11:14.279> we're<00:11:14.670> gonna<00:11:14.790> see 00:11:14.870 --> 00:11:14.880 align:start position:0% like we have a baseline we're gonna see 00:11:14.880 --> 00:11:15.860 align:start position:0% like we have a baseline we're gonna see everybody<00:11:15.149> kind<00:11:15.209> of<00:11:15.329> splitting<00:11:15.600> down 00:11:15.860 --> 00:11:15.870 align:start position:0% everybody kind of splitting down 00:11:15.870 --> 00:11:19.870 align:start position:0% everybody kind of splitting down isolating<00:11:16.860> and<00:11:17.040> like<00:11:17.220> going<00:11:17.430> down<00:11:18.709> basically 00:11:19.870 --> 00:11:19.880 align:start position:0% isolating and like going down basically 00:11:19.880 --> 00:11:22.579 align:start position:0% isolating and like going down basically challenging<00:11:20.880> you<00:11:21.449> know<00:11:21.569> their<00:11:21.899> languages<00:11:22.529> and 00:11:22.579 --> 00:11:22.589 align:start position:0% challenging you know their languages and 00:11:22.589 --> 00:11:24.730 align:start position:0% challenging you know their languages and their<00:11:22.800> respective<00:11:23.009> implementations<00:11:23.850> to 00:11:24.730 --> 00:11:24.740 align:start position:0% their respective implementations to 00:11:24.740 --> 00:11:27.139 align:start position:0% their respective implementations to whatever<00:11:25.740> it<00:11:26.009> is<00:11:26.040> that<00:11:26.190> like<00:11:26.550> their<00:11:26.759> original 00:11:27.139 --> 00:11:27.149 align:start position:0% whatever it is that like their original 00:11:27.149 --> 00:11:30.050 align:start position:0% whatever it is that like their original goal<00:11:27.389> was<00:11:27.750> set<00:11:27.870> out<00:11:27.930> to<00:11:28.110> be<00:11:28.230> I<00:11:29.160> think<00:11:29.759> that's 00:11:30.050 --> 00:11:30.060 align:start position:0% goal was set out to be I think that's 00:11:30.060 --> 00:11:31.910 align:start position:0% goal was set out to be I think that's probably<00:11:30.300> will<00:11:30.930> see<00:11:31.050> like<00:11:31.290> half<00:11:31.649> in<00:11:31.800> the<00:11:31.860> next 00:11:31.910 --> 00:11:31.920 align:start position:0% probably will see like half in the next 00:11:31.920 --> 00:11:36.350 align:start position:0% probably will see like half in the next six<00:11:32.220> months<00:11:33.290> for<00:11:34.290> us<00:11:34.319> as<00:11:34.560> well<00:11:34.709> then<00:11:35.180> the<00:11:36.180> very 00:11:36.350 --> 00:11:36.360 align:start position:0% six months for us as well then the very 00:11:36.360 --> 00:11:38.300 align:start position:0% six months for us as well then the very next<00:11:36.509> milestone<00:11:37.019> is<00:11:37.230> running<00:11:37.829> test<00:11:38.100> nets 00:11:38.300 --> 00:11:38.310 align:start position:0% next milestone is running test nets 00:11:38.310 --> 00:11:41.449 align:start position:0% next milestone is running test nets connected<00:11:38.759> to<00:11:38.910> each<00:11:39.149> one<00:11:39.389> and<00:11:40.040> for<00:11:41.040> this<00:11:41.190> so 00:11:41.449 --> 00:11:41.459 align:start position:0% connected to each one and for this so 00:11:41.459 --> 00:11:43.910 align:start position:0% connected to each one and for this so we've<00:11:41.610> been<00:11:41.730> following<00:11:42.149> the<00:11:42.660> lead<00:11:43.050> of<00:11:43.079> prism 00:11:43.910 --> 00:11:43.920 align:start position:0% we've been following the lead of prism 00:11:43.920 --> 00:11:47.360 align:start position:0% we've been following the lead of prism and<00:11:44.250> we've<00:11:44.819> been<00:11:45.480> publishing<00:11:46.470> deposit 00:11:47.360 --> 00:11:47.370 align:start position:0% and we've been publishing deposit 00:11:47.370 --> 00:11:49.370 align:start position:0% and we've been publishing deposit contract<00:11:47.579> on<00:11:47.940> the<00:11:48.029> Gourley<00:11:48.360> Network<00:11:48.720> and<00:11:49.139> I 00:11:49.370 --> 00:11:49.380 align:start position:0% contract on the Gourley Network and I 00:11:49.380 --> 00:11:51.379 align:start position:0% contract on the Gourley Network and I expect<00:11:50.100> that<00:11:50.250> we<00:11:50.730> have<00:11:51.180> some 00:11:51.379 --> 00:11:51.389 align:start position:0% expect that we have some 00:11:51.389 --> 00:11:54.170 align:start position:0% expect that we have some interoperability<00:11:52.079> with<00:11:52.759> they'll<00:11:53.759> be<00:11:53.910> able<00:11:54.000> to 00:11:54.170 --> 00:11:54.180 align:start position:0% interoperability with they'll be able to 00:11:54.180 --> 00:11:55.790 align:start position:0% interoperability with they'll be able to use<00:11:54.449> ours<00:11:54.779> contract<00:11:55.319> and<00:11:55.440> you'll<00:11:55.529> be<00:11:55.649> using 00:11:55.790 --> 00:11:55.800 align:start position:0% use ours contract and you'll be using 00:11:55.800 --> 00:11:59.090 align:start position:0% use ours contract and you'll be using able<00:11:56.370> to<00:11:56.490> use<00:11:56.579> theirs<00:11:56.850> and<00:11:57.149> so<00:11:57.300> on<00:11:57.480> and<00:11:58.100> there 00:11:59.090 --> 00:11:59.100 align:start position:0% able to use theirs and so on and there 00:11:59.100 --> 00:12:01.550 align:start position:0% able to use theirs and so on and there have<00:11:59.190> been<00:11:59.250> some<00:11:59.819> talks<00:12:00.089> in<00:12:00.569> here<00:12:01.259> with<00:12:01.470> the 00:12:01.550 --> 00:12:01.560 align:start position:0% have been some talks in here with the 00:12:01.560 --> 00:12:04.699 align:start position:0% have been some talks in here with the past<00:12:01.949> few<00:12:02.250> days<00:12:02.870> one<00:12:03.870> of<00:12:03.959> the<00:12:04.019> clients<00:12:04.410> agree 00:12:04.699 --> 00:12:04.709 align:start position:0% past few days one of the clients agree 00:12:04.709 --> 00:12:06.860 align:start position:0% past few days one of the clients agree that<00:12:04.920> it<00:12:05.370> would<00:12:05.459> be<00:12:05.519> beneficial<00:12:06.060> if<00:12:06.329> we<00:12:06.480> set<00:12:06.839> up 00:12:06.860 --> 00:12:06.870 align:start position:0% that it would be beneficial if we set up 00:12:06.870 --> 00:12:10.220 align:start position:0% that it would be beneficial if we set up a<00:12:07.350> shared<00:12:08.279> organization<00:12:09.029> on<00:12:09.180> github<00:12:09.600> where 00:12:10.220 --> 00:12:10.230 align:start position:0% a shared organization on github where 00:12:10.230 --> 00:12:13.250 align:start position:0% a shared organization on github where everybody<00:12:10.740> has<00:12:10.949> commit<00:12:11.490> rights<00:12:11.760> and<00:12:12.180> where<00:12:13.050> we 00:12:13.250 --> 00:12:13.260 align:start position:0% everybody has commit rights and where we 00:12:13.260 --> 00:12:16.639 align:start position:0% everybody has commit rights and where we can<00:12:13.500> work<00:12:14.190> on<00:12:14.459> and<00:12:14.670> improve<00:12:14.760> these<00:12:15.649> scripts 00:12:16.639 --> 00:12:16.649 align:start position:0% can work on and improve these scripts 00:12:16.649 --> 00:12:19.129 align:start position:0% can work on and improve these scripts that<00:12:16.980> allow<00:12:17.399> each<00:12:17.760> developer<00:12:18.480> to<00:12:18.660> bounce<00:12:18.839> test 00:12:19.129 --> 00:12:19.139 align:start position:0% that allow each developer to bounce test 00:12:19.139 --> 00:12:22.129 align:start position:0% that allow each developer to bounce test nets<00:12:19.410> on<00:12:19.649> their<00:12:19.920> own<00:12:20.480> computer<00:12:21.480> on<00:12:21.630> their<00:12:21.779> own 00:12:22.129 --> 00:12:22.139 align:start position:0% nets on their own computer on their own 00:12:22.139 --> 00:12:25.730 align:start position:0% nets on their own computer on their own environment<00:12:22.910> so<00:12:23.910> I<00:12:23.940> see<00:12:24.420> two<00:12:25.050> directions<00:12:25.529> one 00:12:25.730 --> 00:12:25.740 align:start position:0% environment so I see two directions one 00:12:25.740 --> 00:12:27.980 align:start position:0% environment so I see two directions one is<00:12:25.949> public<00:12:26.639> facing<00:12:26.970> test<00:12:27.149> nets<00:12:27.360> running<00:12:27.810> on 00:12:27.980 --> 00:12:27.990 align:start position:0% is public facing test nets running on 00:12:27.990 --> 00:12:29.870 align:start position:0% is public facing test nets running on each<00:12:28.199> one<00:12:28.410> and<00:12:28.649> then<00:12:29.130> the<00:12:29.339> ability<00:12:29.760> for 00:12:29.870 --> 00:12:29.880 align:start position:0% each one and then the ability for 00:12:29.880 --> 00:12:35.500 align:start position:0% each one and then the ability for everyone<00:12:30.180> to<00:12:30.449> just<00:12:30.660> make<00:12:31.440> quick<00:12:31.769> walka<00:12:32.190> setups 00:12:35.500 --> 00:12:35.510 align:start position:0% 00:12:35.510 --> 00:12:38.389 align:start position:0% yeah<00:12:36.510> I<00:12:36.930> mean<00:12:37.319> that<00:12:37.470> we<00:12:37.649> really<00:12:38.010> enjoy<00:12:38.250> using 00:12:38.389 --> 00:12:38.399 align:start position:0% yeah I mean that we really enjoy using 00:12:38.399 --> 00:12:40.579 align:start position:0% yeah I mean that we really enjoy using early<00:12:38.850> I<00:12:38.880> think<00:12:39.000> corley<00:12:39.449> is<00:12:39.600> becoming<00:12:40.290> a<00:12:40.440> lot 00:12:40.579 --> 00:12:40.589 align:start position:0% early I think corley is becoming a lot 00:12:40.589 --> 00:12:42.019 align:start position:0% early I think corley is becoming a lot more<00:12:40.620> of<00:12:40.800> a<00:12:40.889> de-facto<00:12:41.010> standard<00:12:41.279> as<00:12:41.670> well<00:12:41.699> for 00:12:42.019 --> 00:12:42.029 align:start position:0% more of a de-facto standard as well for 00:12:42.029 --> 00:12:44.389 align:start position:0% more of a de-facto standard as well for like<00:12:42.149> each<00:12:42.660> one<00:12:42.720> devs<00:12:43.440> to<00:12:43.649> test<00:12:43.889> out<00:12:44.040> smart 00:12:44.389 --> 00:12:44.399 align:start position:0% like each one devs to test out smart 00:12:44.399 --> 00:12:46.100 align:start position:0% like each one devs to test out smart contracts<00:12:44.790> and<00:12:45.029> it's<00:12:45.149> been<00:12:45.329> really<00:12:45.540> nice<00:12:45.750> to 00:12:46.100 --> 00:12:46.110 align:start position:0% contracts and it's been really nice to 00:12:46.110 --> 00:12:48.829 align:start position:0% contracts and it's been really nice to try<00:12:46.290> out<00:12:46.440> deposits<00:12:47.149> another<00:12:48.149> big<00:12:48.449> effort<00:12:48.720> is 00:12:48.829 --> 00:12:48.839 align:start position:0% try out deposits another big effort is 00:12:48.839 --> 00:12:50.990 align:start position:0% try out deposits another big effort is the<00:12:48.990> ARP<00:12:49.139> is<00:12:49.350> like<00:12:49.589> the<00:12:49.769> API<00:12:50.069> standardization 00:12:50.990 --> 00:12:51.000 align:start position:0% the ARP is like the API standardization 00:12:51.000 --> 00:12:52.579 align:start position:0% the ARP is like the API standardization effort<00:12:51.300> that<00:12:51.870> will<00:12:51.959> come<00:12:52.139> over<00:12:52.260> the<00:12:52.410> coming 00:12:52.579 --> 00:12:52.589 align:start position:0% effort that will come over the coming 00:12:52.589 --> 00:12:54.290 align:start position:0% effort that will come over the coming months<00:12:52.680> so<00:12:53.100> there's<00:12:53.730> a<00:12:53.790> lot<00:12:53.910> of<00:12:53.939> talk<00:12:54.149> about 00:12:54.290 --> 00:12:54.300 align:start position:0% months so there's a lot of talk about 00:12:54.300 --> 00:12:56.449 align:start position:0% months so there's a lot of talk about not<00:12:54.600> having<00:12:55.170> people<00:12:55.260> use<00:12:55.500> the<00:12:55.560> CLI<00:12:55.920> to<00:12:56.220> stake 00:12:56.449 --> 00:12:56.459 align:start position:0% not having people use the CLI to stake 00:12:56.459 --> 00:12:58.790 align:start position:0% not having people use the CLI to stake to<00:12:56.699> run<00:12:56.819> validators<00:12:57.300> you<00:12:58.199> know<00:12:58.290> can<00:12:58.470> we<00:12:58.560> have<00:12:58.769> a 00:12:58.790 --> 00:12:58.800 align:start position:0% to run validators you know can we have a 00:12:58.800 --> 00:13:00.650 align:start position:0% to run validators you know can we have a standardized<00:12:59.579> API<00:12:59.670> that<00:13:00.149> allows<00:13:00.269> people<00:13:00.510> to 00:13:00.650 --> 00:13:00.660 align:start position:0% standardized API that allows people to 00:13:00.660 --> 00:13:02.150 align:start position:0% standardized API that allows people to build<00:13:00.899> things<00:13:01.170> interesting<00:13:01.500> things<00:13:01.860> like 00:13:02.150 --> 00:13:02.160 align:start position:0% build things interesting things like 00:13:02.160 --> 00:13:04.249 align:start position:0% build things interesting things like while<00:13:02.339> it<00:13:02.490> explores<00:13:02.870> other<00:13:03.870> things<00:13:04.139> that 00:13:04.249 --> 00:13:04.259 align:start position:0% while it explores other things that 00:13:04.259 --> 00:13:05.840 align:start position:0% while it explores other things that allow<00:13:04.350> you<00:13:04.439> to<00:13:04.529> interact<00:13:04.620> with<00:13:04.949> the<00:13:05.100> chain<00:13:05.310> and 00:13:05.840 --> 00:13:05.850 align:start position:0% allow you to interact with the chain and 00:13:05.850 --> 00:13:07.999 align:start position:0% allow you to interact with the chain and that<00:13:06.600> will<00:13:06.839> be<00:13:06.959> a<00:13:06.990> really<00:13:07.319> critical<00:13:07.529> effort 00:13:07.999 --> 00:13:08.009 align:start position:0% that will be a really critical effort 00:13:08.009 --> 00:13:12.710 align:start position:0% that will be a really critical effort over<00:13:08.310> the<00:13:08.339> coming<00:13:08.610> months<00:13:08.730> as<00:13:09.029> well<00:13:09.149> so<00:13:11.089> on<00:13:12.089> the 00:13:12.710 --> 00:13:12.720 align:start position:0% over the coming months as well so on the 00:13:12.720 --> 00:13:14.840 align:start position:0% over the coming months as well so on the note<00:13:13.079> of<00:13:13.260> sharing<00:13:13.949> deposit<00:13:14.339> contracts<00:13:14.699> do<00:13:14.790> you 00:13:14.840 --> 00:13:14.850 align:start position:0% note of sharing deposit contracts do you 00:13:14.850 --> 00:13:16.790 align:start position:0% note of sharing deposit contracts do you think<00:13:15.000> it's<00:13:15.149> worth<00:13:15.329> then<00:13:15.810> having<00:13:16.439> one 00:13:16.790 --> 00:13:16.800 align:start position:0% think it's worth then having one 00:13:16.800 --> 00:13:18.800 align:start position:0% think it's worth then having one centralized<00:13:17.699> deposit<00:13:18.180> contract<00:13:18.360> or 00:13:18.800 --> 00:13:18.810 align:start position:0% centralized deposit contract or 00:13:18.810 --> 00:13:21.800 align:start position:0% centralized deposit contract or earlier<00:13:19.200> so<00:13:20.070> similar<00:13:20.460> for<00:13:21.420> what<00:13:21.600> of<00:13:21.690> this 00:13:21.800 --> 00:13:21.810 align:start position:0% earlier so similar for what of this 00:13:21.810 --> 00:13:23.450 align:start position:0% earlier so similar for what of this night<00:13:21.990> last<00:13:22.470> night<00:13:22.560> this<00:13:22.860> makes<00:13:23.130> a<00:13:23.279> lot<00:13:23.370> of 00:13:23.450 --> 00:13:23.460 align:start position:0% night last night this makes a lot of 00:13:23.460 --> 00:13:25.010 align:start position:0% night last night this makes a lot of sense<00:13:23.760> to<00:13:24.000> restart<00:13:24.420> them<00:13:24.570> frequent 00:13:25.010 --> 00:13:25.020 align:start position:0% sense to restart them frequent 00:13:25.020 --> 00:13:27.769 align:start position:0% sense to restart them frequent frequently<00:13:25.590> and<00:13:25.980> then<00:13:26.270> nothing<00:13:27.270> prevents<00:13:27.690> you 00:13:27.769 --> 00:13:27.779 align:start position:0% frequently and then nothing prevents you 00:13:27.779 --> 00:13:30.590 align:start position:0% frequently and then nothing prevents you from<00:13:27.810> having<00:13:28.680> multiple<00:13:29.340> deposit<00:13:30.060> contracts 00:13:30.590 --> 00:13:30.600 align:start position:0% from having multiple deposit contracts 00:13:30.600 --> 00:13:32.269 align:start position:0% from having multiple deposit contracts being<00:13:31.020> active<00:13:31.380> at<00:13:31.529> the<00:13:31.620> same<00:13:31.800> time<00:13:32.040> you<00:13:32.220> know 00:13:32.269 --> 00:13:32.279 align:start position:0% being active at the same time you know 00:13:32.279 --> 00:13:33.710 align:start position:0% being active at the same time you know basically<00:13:32.760> the<00:13:32.850> client<00:13:33.150> only<00:13:33.330> needs<00:13:33.570> to 00:13:33.710 --> 00:13:33.720 align:start position:0% basically the client only needs to 00:13:33.720 --> 00:13:36.140 align:start position:0% basically the client only needs to specify<00:13:34.260> the<00:13:34.860> address<00:13:35.339> of<00:13:35.610> the<00:13:35.790> deposit 00:13:36.140 --> 00:13:36.150 align:start position:0% specify the address of the deposit 00:13:36.150 --> 00:13:41.630 align:start position:0% specify the address of the deposit contract<00:13:36.360> that<00:13:36.720> he'll<00:13:36.900> be<00:13:37.050> using<00:13:40.460> just<00:13:41.460> in 00:13:41.630 --> 00:13:41.640 align:start position:0% contract that he'll be using just in 00:13:41.640 --> 00:13:44.210 align:start position:0% contract that he'll be using just in terms<00:13:41.820> of<00:13:42.060> the<00:13:42.300> the<00:13:42.570> shared<00:13:42.900> deposit<00:13:43.770> contract 00:13:44.210 --> 00:13:44.220 align:start position:0% terms of the the shared deposit contract 00:13:44.220 --> 00:13:45.440 align:start position:0% terms of the the shared deposit contract I<00:13:44.310> think<00:13:44.339> something<00:13:44.760> that<00:13:44.850> would<00:13:44.940> be<00:13:45.029> nice<00:13:45.210> too 00:13:45.440 --> 00:13:45.450 align:start position:0% I think something that would be nice too 00:13:45.450 --> 00:13:50.600 align:start position:0% I think something that would be nice too would<00:13:45.630> be<00:13:45.810> a<00:13:46.410> common<00:13:47.210> onboarding<00:13:49.310> process<00:13:50.310> for 00:13:50.600 --> 00:13:50.610 align:start position:0% would be a common onboarding process for 00:13:50.610 --> 00:13:52.460 align:start position:0% would be a common onboarding process for validators<00:13:51.089> I<00:13:51.210> think<00:13:51.390> TF<00:13:51.900> was<00:13:52.110> maybe 00:13:52.460 --> 00:13:52.470 align:start position:0% validators I think TF was maybe 00:13:52.470 --> 00:13:54.640 align:start position:0% validators I think TF was maybe considering<00:13:52.980> about<00:13:53.279> jumping<00:13:53.940> on<00:13:54.060> that<00:13:54.240> so 00:13:54.640 --> 00:13:54.650 align:start position:0% considering about jumping on that so 00:13:54.650 --> 00:13:56.630 align:start position:0% considering about jumping on that so yeah<00:13:55.650> it<00:13:55.740> would<00:13:55.830> be<00:13:55.920> nice<00:13:56.040> if<00:13:56.220> we<00:13:56.279> don't<00:13:56.490> all 00:13:56.630 --> 00:13:56.640 align:start position:0% yeah it would be nice if we don't all 00:13:56.640 --> 00:13:58.100 align:start position:0% yeah it would be nice if we don't all have<00:13:56.670> to<00:13:56.820> build<00:13:57.210> you<00:13:57.810> know<00:13:57.870> a<00:13:57.930> million 00:13:58.100 --> 00:13:58.110 align:start position:0% have to build you know a million 00:13:58.110 --> 00:14:00.290 align:start position:0% have to build you know a million different<00:13:58.620> little<00:13:58.850> validator<00:13:59.850> onboarding 00:14:00.290 --> 00:14:00.300 align:start position:0% different little validator onboarding 00:14:00.300 --> 00:14:03.800 align:start position:0% different little validator onboarding things<00:14:00.600> than<00:14:01.410> to<00:14:01.560> be<00:14:01.650> superseded<00:14:02.250> by<00:14:02.810> an 00:14:03.800 --> 00:14:03.810 align:start position:0% things than to be superseded by an 00:14:03.810 --> 00:14:10.010 align:start position:0% things than to be superseded by an official<00:14:04.140> one<00:14:04.410> coming<00:14:04.710> out<00:14:08.330> we<00:14:09.330> also<00:14:09.570> probably 00:14:10.010 --> 00:14:10.020 align:start position:0% official one coming out we also probably 00:14:10.020 --> 00:14:14.930 align:start position:0% official one coming out we also probably want<00:14:10.500> to<00:14:10.589> test<00:14:11.400> this<00:14:12.440> beacon<00:14:13.440> chain<00:14:13.710> start<00:14:14.070> for 00:14:14.930 --> 00:14:14.940 align:start position:0% want to test this beacon chain start for 00:14:14.940 --> 00:14:17.480 align:start position:0% want to test this beacon chain start for many<00:14:15.480> times<00:14:15.839> because<00:14:16.620> it<00:14:16.770> could<00:14:16.950> be<00:14:17.130> a<00:14:17.160> huge 00:14:17.480 --> 00:14:17.490 align:start position:0% many times because it could be a huge 00:14:17.490 --> 00:14:20.120 align:start position:0% many times because it could be a huge point<00:14:17.760> of<00:14:17.910> failure<00:14:18.150> I<00:14:18.630> mean<00:14:19.380> the<00:14:19.589> kicking<00:14:20.010> off 00:14:20.120 --> 00:14:20.130 align:start position:0% point of failure I mean the kicking off 00:14:20.130 --> 00:14:24.470 align:start position:0% point of failure I mean the kicking off from<00:14:20.460> eath<00:14:21.060> one<00:14:21.710> chain<00:14:22.710> to<00:14:23.040> the<00:14:23.880> beacon<00:14:24.210> chain 00:14:24.470 --> 00:14:24.480 align:start position:0% from eath one chain to the beacon chain 00:14:24.480 --> 00:14:29.300 align:start position:0% from eath one chain to the beacon chain so<00:14:25.200> it's<00:14:25.740> probably<00:14:26.630> worth<00:14:27.630> to<00:14:28.200> focus<00:14:28.860> on<00:14:29.040> as 00:14:29.300 --> 00:14:29.310 align:start position:0% so it's probably worth to focus on as 00:14:29.310 --> 00:14:33.800 align:start position:0% so it's probably worth to focus on as well<00:14:31.220> definitely<00:14:32.220> we<00:14:32.490> don't<00:14:33.060> find<00:14:33.300> that<00:14:33.390> often 00:14:33.800 --> 00:14:33.810 align:start position:0% well definitely we don't find that often 00:14:33.810 --> 00:14:40.460 align:start position:0% well definitely we don't find that often in<00:14:34.080> production<00:14:36.950> and<00:14:38.450> on<00:14:39.450> that<00:14:39.960> topic<00:14:40.200> I<00:14:40.410> think 00:14:40.460 --> 00:14:40.470 align:start position:0% in production and on that topic I think 00:14:40.470 --> 00:14:41.990 align:start position:0% in production and on that topic I think it'll<00:14:40.680> also<00:14:40.830> be<00:14:40.980> worth<00:14:41.100> discussing<00:14:41.460> what<00:14:41.790> are 00:14:41.990 --> 00:14:42.000 align:start position:0% it'll also be worth discussing what are 00:14:42.000 --> 00:14:45.710 align:start position:0% it'll also be worth discussing what are the<00:14:43.280> what<00:14:44.280> a<00:14:44.310> valid<00:14:44.670> criteria<00:14:45.180> how<00:14:45.390> would<00:14:45.600> we 00:14:45.710 --> 00:14:45.720 align:start position:0% the what a valid criteria how would we 00:14:45.720 --> 00:14:48.829 align:start position:0% the what a valid criteria how would we decide<00:14:46.050> that<00:14:46.350> we<00:14:47.310> are<00:14:47.430> ready<00:14:47.610> to<00:14:47.970> do<00:14:48.480> this<00:14:48.630> main 00:14:48.829 --> 00:14:48.839 align:start position:0% decide that we are ready to do this main 00:14:48.839 --> 00:14:51.110 align:start position:0% decide that we are ready to do this main net<00:14:49.020> launch<00:14:49.230> so<00:14:49.620> I<00:14:50.130> agree<00:14:50.550> one<00:14:50.730> of<00:14:50.820> them<00:14:50.970> should 00:14:51.110 --> 00:14:51.120 align:start position:0% net launch so I agree one of them should 00:14:51.120 --> 00:14:55.070 align:start position:0% net launch so I agree one of them should be<00:14:51.180> that<00:14:51.390> we've<00:14:51.540> had<00:14:52.280> launchers<00:14:53.600> bastes<00:14:54.600> based 00:14:55.070 --> 00:14:55.080 align:start position:0% be that we've had launchers bastes based 00:14:55.080 --> 00:14:59.750 align:start position:0% be that we've had launchers bastes based off<00:14:55.260> f1<00:14:55.620> and<00:14:56.180> these<00:14:57.980> starts<00:14:58.980> but<00:14:59.220> how<00:14:59.580> do<00:14:59.640> we 00:14:59.750 --> 00:14:59.760 align:start position:0% off f1 and these starts but how do we 00:14:59.760 --> 00:15:01.670 align:start position:0% off f1 and these starts but how do we actually<00:15:00.089> decide<00:15:00.420> that<00:15:00.690> this<00:15:01.260> is<00:15:01.320> the 00:15:01.670 --> 00:15:01.680 align:start position:0% actually decide that this is the 00:15:01.680 --> 00:15:04.790 align:start position:0% actually decide that this is the finalized<00:15:02.190> version<00:15:02.810> both<00:15:03.810> in<00:15:03.990> terms<00:15:04.200> of<00:15:04.410> we 00:15:04.790 --> 00:15:04.800 align:start position:0% finalized version both in terms of we 00:15:04.800 --> 00:15:06.440 align:start position:0% finalized version both in terms of we can<00:15:04.920> specify<00:15:05.100> minimum<00:15:05.400> each<00:15:05.760> deposits<00:15:06.300> and 00:15:06.440 --> 00:15:06.450 align:start position:0% can specify minimum each deposits and 00:15:06.450 --> 00:15:08.660 align:start position:0% can specify minimum each deposits and that<00:15:06.540> kind<00:15:06.660> of<00:15:06.720> thing<00:15:06.870> but<00:15:06.990> also<00:15:07.400> more<00:15:08.400> in 00:15:08.660 --> 00:15:08.670 align:start position:0% that kind of thing but also more in 00:15:08.670 --> 00:15:12.140 align:start position:0% that kind of thing but also more in terms<00:15:08.880> of<00:15:09.030> how<00:15:10.040> what<00:15:11.040> we<00:15:11.190> require<00:15:11.550> of<00:15:11.670> clients 00:15:12.140 --> 00:15:12.150 align:start position:0% terms of how what we require of clients 00:15:12.150 --> 00:15:14.570 align:start position:0% terms of how what we require of clients to<00:15:12.570> be<00:15:12.690> able<00:15:12.780> to<00:15:13.110> participate<00:15:13.560> in<00:15:14.070> these 00:15:14.570 --> 00:15:14.580 align:start position:0% to be able to participate in these 00:15:14.580 --> 00:15:17.329 align:start position:0% to be able to participate in these networks<00:15:15.110> and<00:15:16.110> and<00:15:16.560> how<00:15:16.709> do<00:15:16.770> we<00:15:16.890> say<00:15:17.070> that<00:15:17.100> this 00:15:17.329 --> 00:15:17.339 align:start position:0% networks and and how do we say that this 00:15:17.339 --> 00:15:18.980 align:start position:0% networks and and how do we say that this client<00:15:17.760> should<00:15:18.120> should<00:15:18.690> or<00:15:18.810> shouldn't 00:15:18.980 --> 00:15:18.990 align:start position:0% client should should or shouldn't 00:15:18.990 --> 00:15:20.900 align:start position:0% client should should or shouldn't participate<00:15:19.620> I<00:15:20.040> mean<00:15:20.279> obviously<00:15:20.580> it's<00:15:20.760> not 00:15:20.900 --> 00:15:20.910 align:start position:0% participate I mean obviously it's not 00:15:20.910 --> 00:15:23.720 align:start position:0% participate I mean obviously it's not gonna<00:15:21.000> be<00:15:21.180> some<00:15:21.839> definitive<00:15:22.170> thing<00:15:22.860> but<00:15:23.100> what 00:15:23.720 --> 00:15:23.730 align:start position:0% gonna be some definitive thing but what 00:15:23.730 --> 00:15:25.370 align:start position:0% gonna be some definitive thing but what what<00:15:23.940> is<00:15:24.060> a<00:15:24.089> good<00:15:24.300> signal<00:15:24.660> for<00:15:24.690> deciding<00:15:25.260> that 00:15:25.370 --> 00:15:25.380 align:start position:0% what is a good signal for deciding that 00:15:25.380 --> 00:15:27.350 align:start position:0% what is a good signal for deciding that a<00:15:25.440> client<00:15:25.620> is<00:15:25.860> ready<00:15:26.370> for<00:15:26.580> participating<00:15:27.120> in 00:15:27.350 --> 00:15:27.360 align:start position:0% a client is ready for participating in 00:15:27.360 --> 00:15:31.760 align:start position:0% a client is ready for participating in in<00:15:27.600> am<00:15:27.720> a<00:15:27.810> net<00:15:27.990> launch 00:15:31.760 --> 00:15:31.770 align:start position:0% 00:15:31.770 --> 00:15:33.470 align:start position:0% I<00:15:31.800> mean<00:15:32.520> yeah<00:15:32.760> that's<00:15:32.880> obviously<00:15:33.270> a<00:15:33.360> big 00:15:33.470 --> 00:15:33.480 align:start position:0% I mean yeah that's obviously a big 00:15:33.480 --> 00:15:35.840 align:start position:0% I mean yeah that's obviously a big question<00:15:33.870> at<00:15:34.560> a<00:15:34.620> high<00:15:34.800> level<00:15:34.830> right<00:15:35.250> like<00:15:35.550> I 00:15:35.840 --> 00:15:35.850 align:start position:0% question at a high level right like I 00:15:35.850 --> 00:15:37.760 align:start position:0% question at a high level right like I would<00:15:36.180> expect<00:15:36.780> we<00:15:37.080> want<00:15:37.230> this<00:15:37.320> to<00:15:37.470> be<00:15:37.590> actually 00:15:37.760 --> 00:15:37.770 align:start position:0% would expect we want this to be actually 00:15:37.770 --> 00:15:39.830 align:start position:0% would expect we want this to be actually fairly<00:15:38.130> community<00:15:38.580> driven<00:15:38.760> probably<00:15:39.660> like 00:15:39.830 --> 00:15:39.840 align:start position:0% fairly community driven probably like 00:15:39.840 --> 00:15:42.200 align:start position:0% fairly community driven probably like highly<00:15:40.380> directed<00:15:40.800> by<00:15:40.950> the<00:15:41.460> client<00:15:41.790> developers 00:15:42.200 --> 00:15:42.210 align:start position:0% highly directed by the client developers 00:15:42.210 --> 00:15:45.770 align:start position:0% highly directed by the client developers themselves<00:15:43.730> obviously<00:15:44.730> there's<00:15:45.450> things<00:15:45.660> like 00:15:45.770 --> 00:15:45.780 align:start position:0% themselves obviously there's things like 00:15:45.780 --> 00:15:48.080 align:start position:0% themselves obviously there's things like uptime<00:15:46.320> and<00:15:46.740> performance<00:15:46.800> and<00:15:47.580> stuff<00:15:47.850> right 00:15:48.080 --> 00:15:48.090 align:start position:0% uptime and performance and stuff right 00:15:48.090 --> 00:15:50.570 align:start position:0% uptime and performance and stuff right so<00:15:48.150> for<00:15:48.930> example<00:15:49.350> if<00:15:49.560> we<00:15:49.710> end<00:15:49.860> up<00:15:49.950> with<00:15:50.160> like<00:15:50.310> a 00:15:50.570 --> 00:15:50.580 align:start position:0% so for example if we end up with like a 00:15:50.580 --> 00:15:52.340 align:start position:0% so for example if we end up with like a ton<00:15:51.030> of<00:15:51.060> early<00:15:51.330> validators<00:15:51.780> we<00:15:52.050> all<00:15:52.170> want 00:15:52.340 --> 00:15:52.350 align:start position:0% ton of early validators we all want 00:15:52.350 --> 00:15:54.350 align:start position:0% ton of early validators we all want clients<00:15:52.560> to<00:15:53.100> be<00:15:53.250> able<00:15:53.340> to<00:15:53.520> handle<00:15:53.850> that<00:15:54.180> many 00:15:54.350 --> 00:15:54.360 align:start position:0% clients to be able to handle that many 00:15:54.360 --> 00:15:57.170 align:start position:0% clients to be able to handle that many validators<00:15:54.870> I<00:15:55.680> know<00:15:56.310> for<00:15:56.520> example<00:15:56.550> Trinity 00:15:57.170 --> 00:15:57.180 align:start position:0% validators I know for example Trinity 00:15:57.180 --> 00:15:59.300 align:start position:0% validators I know for example Trinity like<00:15:57.450> can't<00:15:58.050> scale<00:15:58.380> to<00:15:58.620> like<00:15:58.740> the<00:15:58.890> theoretical 00:15:59.300 --> 00:15:59.310 align:start position:0% like can't scale to like the theoretical 00:15:59.310 --> 00:16:00.440 align:start position:0% like can't scale to like the theoretical max<00:15:59.460> right<00:15:59.610> now<00:15:59.700> like<00:16:00.030> we<00:16:00.150> just<00:16:00.270> don't<00:16:00.390> have 00:16:00.440 --> 00:16:00.450 align:start position:0% max right now like we just don't have 00:16:00.450 --> 00:16:02.330 align:start position:0% max right now like we just don't have the<00:16:00.540> performance<00:16:00.870> we'll<00:16:01.590> get<00:16:01.710> there<00:16:01.890> but 00:16:02.330 --> 00:16:02.340 align:start position:0% the performance we'll get there but 00:16:02.340 --> 00:16:05.180 align:start position:0% the performance we'll get there but we're<00:16:02.970> not<00:16:03.090> there<00:16:03.270> yet<00:16:03.390> so<00:16:04.050> these<00:16:04.980> types<00:16:05.160> of 00:16:05.180 --> 00:16:05.190 align:start position:0% we're not there yet so these types of 00:16:05.190 --> 00:16:06.200 align:start position:0% we're not there yet so these types of things<00:16:05.280> are<00:16:05.430> like<00:16:05.580> it<00:16:05.670> really<00:16:05.880> important 00:16:06.200 --> 00:16:06.210 align:start position:0% things are like it really important 00:16:06.210 --> 00:16:10.100 align:start position:0% things are like it really important qualifications<00:16:07.640> you<00:16:08.640> know<00:16:08.760> at<00:16:09.750> a<00:16:09.780> certain 00:16:10.100 --> 00:16:10.110 align:start position:0% qualifications you know at a certain 00:16:10.110 --> 00:16:11.510 align:start position:0% qualifications you know at a certain point<00:16:10.290> it's<00:16:10.500> hard<00:16:10.560> to<00:16:10.740> say<00:16:10.950> like<00:16:10.980> are<00:16:11.370> you 00:16:11.510 --> 00:16:11.520 align:start position:0% point it's hard to say like are you 00:16:11.520 --> 00:16:13.430 align:start position:0% point it's hard to say like are you ready<00:16:11.700> you<00:16:11.910> can<00:16:12.030> always<00:16:12.210> defer<00:16:12.840> and<00:16:13.140> like<00:16:13.290> do 00:16:13.430 --> 00:16:13.440 align:start position:0% ready you can always defer and like do 00:16:13.440 --> 00:16:15.440 align:start position:0% ready you can always defer and like do more<00:16:13.620> testing<00:16:13.980> so<00:16:14.820> a<00:16:14.850> certain<00:16:15.060> point<00:16:15.270> you<00:16:15.420> just 00:16:15.440 --> 00:16:15.450 align:start position:0% more testing so a certain point you just 00:16:15.450 --> 00:16:18.080 align:start position:0% more testing so a certain point you just have<00:16:15.660> to<00:16:15.750> like<00:16:15.870> you<00:16:16.260> know<00:16:16.340> I'll<00:16:17.340> say<00:16:17.520> well 00:16:18.080 --> 00:16:18.090 align:start position:0% have to like you know I'll say well 00:16:18.090 --> 00:16:20.300 align:start position:0% have to like you know I'll say well these<00:16:18.570> are<00:16:18.720> all<00:16:18.810> sounding<00:16:19.260> really<00:16:19.350> negative<00:16:19.710> I 00:16:20.300 --> 00:16:20.310 align:start position:0% these are all sounding really negative I 00:16:20.310 --> 00:16:21.710 align:start position:0% these are all sounding really negative I was<00:16:20.760> gonna<00:16:20.880> say<00:16:21.030> jump<00:16:21.240> off<00:16:21.330> the<00:16:21.450> cliff<00:16:21.570> or 00:16:21.710 --> 00:16:21.720 align:start position:0% was gonna say jump off the cliff or 00:16:21.720 --> 00:16:26.780 align:start position:0% was gonna say jump off the cliff or something<00:16:22.050> but<00:16:23.780> yeah<00:16:25.340> hopefully<00:16:26.340> we<00:16:26.580> know<00:16:26.700> it 00:16:26.780 --> 00:16:26.790 align:start position:0% something but yeah hopefully we know it 00:16:26.790 --> 00:16:28.490 align:start position:0% something but yeah hopefully we know it when<00:16:26.910> we<00:16:26.940> see<00:16:27.030> it<00:16:27.210> and<00:16:27.600> we're<00:16:27.780> like<00:16:27.900> okay<00:16:28.200> we 00:16:28.490 --> 00:16:28.500 align:start position:0% when we see it and we're like okay we 00:16:28.500 --> 00:16:32.480 align:start position:0% when we see it and we're like okay we all<00:16:28.620> feel<00:16:28.770> good<00:16:28.980> here<00:16:29.520> we<00:16:29.610> go<00:16:31.250> yeah<00:16:32.250> I<00:16:32.280> agree 00:16:32.480 --> 00:16:32.490 align:start position:0% all feel good here we go yeah I agree 00:16:32.490 --> 00:16:38.510 align:start position:0% all feel good here we go yeah I agree the<00:16:32.790> story<00:16:34.190> that<00:16:35.270> there<00:16:36.270> should<00:16:36.720> be<00:16:36.750> some<00:16:37.520> we 00:16:38.510 --> 00:16:38.520 align:start position:0% the story that there should be some we 00:16:38.520 --> 00:16:40.700 align:start position:0% the story that there should be some we should<00:16:38.700> start<00:16:38.940> testing<00:16:39.390> with<00:16:39.420> some<00:16:39.810> the 00:16:40.700 --> 00:16:40.710 align:start position:0% should start testing with some the 00:16:40.710 --> 00:16:42.050 align:start position:0% should start testing with some the parameters<00:16:41.190> that<00:16:41.310> affect<00:16:41.640> the<00:16:41.790> performance 00:16:42.050 --> 00:16:42.060 align:start position:0% parameters that affect the performance 00:16:42.060 --> 00:16:43.880 align:start position:0% parameters that affect the performance of<00:16:42.480> the<00:16:42.600> network<00:16:42.690> we<00:16:43.530> should<00:16:43.710> start 00:16:43.880 --> 00:16:43.890 align:start position:0% of the network we should start 00:16:43.890 --> 00:16:46.730 align:start position:0% of the network we should start validating<00:16:44.490> that<00:16:45.020> each<00:16:46.020> of<00:16:46.050> the<00:16:46.350> clans<00:16:46.560> is 00:16:46.730 --> 00:16:46.740 align:start position:0% validating that each of the clans is 00:16:46.740 --> 00:16:49.250 align:start position:0% validating that each of the clans is ready<00:16:46.950> for<00:16:47.100> this<00:16:47.250> but<00:16:47.460> our<00:16:47.640> own<00:16:48.030> roadmap<00:16:48.330> is 00:16:49.250 --> 00:16:49.260 align:start position:0% ready for this but our own roadmap is 00:16:49.260 --> 00:16:52.160 align:start position:0% ready for this but our own roadmap is also<00:16:49.920> built<00:16:50.190> around<00:16:50.430> the<00:16:51.000> need<00:16:51.150> for<00:16:51.180> security 00:16:52.160 --> 00:16:52.170 align:start position:0% also built around the need for security 00:16:52.170 --> 00:16:54.170 align:start position:0% also built around the need for security for<00:16:52.770> performing<00:16:53.250> security<00:16:53.700> audit<00:16:53.940> on<00:16:54.060> our 00:16:54.170 --> 00:16:54.180 align:start position:0% for performing security audit on our 00:16:54.180 --> 00:16:57.050 align:start position:0% for performing security audit on our code<00:16:54.540> and<00:16:54.840> this<00:16:55.680> is<00:16:55.860> a<00:16:55.890> pretty<00:16:56.670> complicated 00:16:57.050 --> 00:16:57.060 align:start position:0% code and this is a pretty complicated 00:16:57.060 --> 00:17:00.260 align:start position:0% code and this is a pretty complicated thing<00:16:57.840> to<00:16:58.020> plan<00:16:58.230> out<00:16:58.410> because<00:16:58.850> it<00:16:59.850> requires 00:17:00.260 --> 00:17:00.270 align:start position:0% thing to plan out because it requires 00:17:00.270 --> 00:17:03.200 align:start position:0% thing to plan out because it requires you<00:17:00.420> to<00:17:00.510> freeze<00:17:01.290> a<00:17:01.560> lot<00:17:01.740> of<00:17:01.890> the<00:17:01.980> code<00:17:02.220> so<00:17:02.940> we 00:17:03.200 --> 00:17:03.210 align:start position:0% you to freeze a lot of the code so we 00:17:03.210 --> 00:17:07.370 align:start position:0% you to freeze a lot of the code so we are<00:17:05.180> currently<00:17:06.180> creating<00:17:06.690> a<00:17:06.780> plan<00:17:06.990> that<00:17:07.200> will 00:17:07.370 --> 00:17:07.380 align:start position:0% are currently creating a plan that will 00:17:07.380 --> 00:17:10.850 align:start position:0% are currently creating a plan that will allow<00:17:07.650> us<00:17:07.980> to<00:17:09.050> create<00:17:10.050> sort<00:17:10.380> of<00:17:10.500> a<00:17:10.589> pipeline 00:17:10.850 --> 00:17:10.860 align:start position:0% allow us to create sort of a pipeline 00:17:10.860 --> 00:17:14.449 align:start position:0% allow us to create sort of a pipeline for<00:17:12.500> smaller<00:17:13.500> and<00:17:13.650> smaller<00:17:13.890> components<00:17:14.370> that 00:17:14.449 --> 00:17:14.459 align:start position:0% for smaller and smaller components that 00:17:14.459 --> 00:17:16.310 align:start position:0% for smaller and smaller components that will<00:17:14.640> go<00:17:14.790> through<00:17:15.060> audit<00:17:15.420> and<00:17:15.660> then<00:17:16.080> bigger 00:17:16.310 --> 00:17:16.320 align:start position:0% will go through audit and then bigger 00:17:16.320 --> 00:17:18.620 align:start position:0% will go through audit and then bigger and<00:17:16.530> bigger<00:17:16.709> parts<00:17:17.100> until<00:17:17.880> we<00:17:18.240> are<00:17:18.300> ready<00:17:18.480> to 00:17:18.620 --> 00:17:18.630 align:start position:0% and bigger parts until we are ready to 00:17:18.630 --> 00:17:22.880 align:start position:0% and bigger parts until we are ready to answer<00:17:19.880> yeah<00:17:20.880> as<00:17:21.120> country<00:17:21.480> comment<00:17:21.990> along<00:17:22.709> the 00:17:22.880 --> 00:17:22.890 align:start position:0% answer yeah as country comment along the 00:17:22.890 --> 00:17:24.710 align:start position:0% answer yeah as country comment along the same<00:17:23.070> lines<00:17:23.280> I<00:17:23.490> mean<00:17:23.520> in<00:17:24.060> this<00:17:24.209> network<00:17:24.450> you 00:17:24.710 --> 00:17:24.720 align:start position:0% same lines I mean in this network you 00:17:24.720 --> 00:17:27.320 align:start position:0% same lines I mean in this network you can't<00:17:24.959> prevent<00:17:25.230> anyone<00:17:25.589> from<00:17:25.970> saying<00:17:26.970> I'm<00:17:27.270> a 00:17:27.320 --> 00:17:27.330 align:start position:0% can't prevent anyone from saying I'm a 00:17:27.330 --> 00:17:28.940 align:start position:0% can't prevent anyone from saying I'm a validator<00:17:27.870> and<00:17:28.050> being<00:17:28.560> part<00:17:28.770> of<00:17:28.830> a<00:17:28.920> network 00:17:28.940 --> 00:17:28.950 align:start position:0% validator and being part of a network 00:17:28.950 --> 00:17:31.510 align:start position:0% validator and being part of a network Ronit<00:17:29.700> that's<00:17:30.000> the<00:17:30.120> whole<00:17:30.270> point 00:17:31.510 --> 00:17:31.520 align:start position:0% Ronit that's the whole point 00:17:31.520 --> 00:17:34.370 align:start position:0% Ronit that's the whole point so<00:17:32.520> it<00:17:32.790> requires<00:17:32.970> client<00:17:33.660> teams<00:17:33.870> need<00:17:34.140> to<00:17:34.170> take 00:17:34.370 --> 00:17:34.380 align:start position:0% so it requires client teams need to take 00:17:34.380 --> 00:17:38.840 align:start position:0% so it requires client teams need to take responsibility<00:17:36.020> on<00:17:37.020> the<00:17:37.260> one<00:17:37.440> hand<00:17:37.770> and<00:17:38.130> so<00:17:38.820> I 00:17:38.840 --> 00:17:38.850 align:start position:0% responsibility on the one hand and so I 00:17:38.850 --> 00:17:41.390 align:start position:0% responsibility on the one hand and so I think<00:17:39.000> exactly<00:17:39.750> right<00:17:39.930> audits<00:17:40.350> are<00:17:41.130> going<00:17:41.340> to 00:17:41.390 --> 00:17:41.400 align:start position:0% think exactly right audits are going to 00:17:41.400 --> 00:17:44.510 align:start position:0% think exactly right audits are going to be<00:17:41.490> important<00:17:41.940> one<00:17:42.540> of<00:17:42.570> the<00:17:42.780> very<00:17:43.460> strong 00:17:44.510 --> 00:17:44.520 align:start position:0% be important one of the very strong 00:17:44.520 --> 00:17:46.460 align:start position:0% be important one of the very strong differences<00:17:45.210> between<00:17:45.390> aetherium<00:17:46.140> two<00:17:46.290> and<00:17:46.410> a 00:17:46.460 --> 00:17:46.470 align:start position:0% differences between aetherium two and a 00:17:46.470 --> 00:17:48.350 align:start position:0% differences between aetherium two and a theorem<00:17:46.740> one<00:17:46.950> is<00:17:47.160> that<00:17:47.310> in<00:17:47.430> eighth<00:17:47.670> -<00:17:47.970> we<00:17:48.210> need 00:17:48.350 --> 00:17:48.360 align:start position:0% theorem one is that in eighth - we need 00:17:48.360 --> 00:17:50.300 align:start position:0% theorem one is that in eighth - we need to<00:17:48.480> do<00:17:48.600> online<00:17:48.870> signing<00:17:49.650> you<00:17:49.830> have<00:17:49.980> to<00:17:50.160> have 00:17:50.300 --> 00:17:50.310 align:start position:0% to do online signing you have to have 00:17:50.310 --> 00:17:54.410 align:start position:0% to do online signing you have to have your<00:17:50.810> key<00:17:51.920> available<00:17:52.920> to<00:17:53.130> sign<00:17:53.400> in<00:17:53.790> real<00:17:54.090> time 00:17:54.410 --> 00:17:54.420 align:start position:0% your key available to sign in real time 00:17:54.420 --> 00:17:56.810 align:start position:0% your key available to sign in real time which<00:17:55.170> is<00:17:55.440> something<00:17:55.620> that<00:17:55.860> all<00:17:56.040> the<00:17:56.340> f1 00:17:56.810 --> 00:17:56.820 align:start position:0% which is something that all the f1 00:17:56.820 --> 00:17:59.060 align:start position:0% which is something that all the f1 clients<00:17:57.330> and<00:17:58.020> nodes<00:17:58.320> have<00:17:58.560> moved<00:17:58.770> away<00:17:58.920> from 00:17:59.060 --> 00:17:59.070 align:start position:0% clients and nodes have moved away from 00:17:59.070 --> 00:18:00.080 align:start position:0% clients and nodes have moved away from over<00:17:59.580> the<00:17:59.670> years 00:18:00.080 --> 00:18:00.090 align:start position:0% over the years 00:18:00.090 --> 00:18:02.180 align:start position:0% over the years because<00:18:00.690> it<00:18:00.870> is<00:18:01.140> really<00:18:01.590> hard<00:18:01.770> to<00:18:01.980> do<00:18:02.070> it 00:18:02.180 --> 00:18:02.190 align:start position:0% because it is really hard to do it 00:18:02.190 --> 00:18:03.290 align:start position:0% because it is really hard to do it securely<00:18:02.520> so<00:18:02.790> that's<00:18:03.000> going<00:18:03.120> to<00:18:03.210> be<00:18:03.270> a 00:18:03.290 --> 00:18:03.300 align:start position:0% securely so that's going to be a 00:18:03.300 --> 00:18:06.080 align:start position:0% securely so that's going to be a critical<00:18:03.810> point<00:18:04.200> where<00:18:04.470> we<00:18:04.650> need<00:18:04.800> to<00:18:04.920> focus 00:18:06.080 --> 00:18:06.090 align:start position:0% critical point where we need to focus 00:18:06.090 --> 00:18:09.800 align:start position:0% critical point where we need to focus audit<00:18:06.750> and<00:18:07.410> security<00:18:07.890> effort<00:18:08.220> on<00:18:09.090> that<00:18:09.120> and<00:18:09.480> on 00:18:09.800 --> 00:18:09.810 align:start position:0% audit and security effort on that and on 00:18:09.810 --> 00:18:11.840 align:start position:0% audit and security effort on that and on the<00:18:09.840> other<00:18:10.020> hand<00:18:10.170> users<00:18:10.980> need<00:18:11.190> to<00:18:11.220> be<00:18:11.460> kind<00:18:11.760> of 00:18:11.840 --> 00:18:11.850 align:start position:0% the other hand users need to be kind of 00:18:11.850 --> 00:18:13.790 align:start position:0% the other hand users need to be kind of wise<00:18:12.030> as<00:18:12.780> well<00:18:12.990> because<00:18:13.290> they<00:18:13.410> have<00:18:13.530> to<00:18:13.620> choose 00:18:13.790 --> 00:18:13.800 align:start position:0% wise as well because they have to choose 00:18:13.800 --> 00:18:15.710 align:start position:0% wise as well because they have to choose a<00:18:13.830> client<00:18:14.220> in<00:18:14.310> which<00:18:14.430> to<00:18:14.670> to<00:18:14.940> run<00:18:15.120> and<00:18:15.390> to<00:18:15.480> stake 00:18:15.710 --> 00:18:15.720 align:start position:0% a client in which to to run and to stake 00:18:15.720 --> 00:18:17.540 align:start position:0% a client in which to to run and to stake and<00:18:15.990> so<00:18:16.110> forth<00:18:16.350> and<00:18:16.710> I<00:18:16.920> think<00:18:17.130> the<00:18:17.190> best<00:18:17.340> thing 00:18:17.540 --> 00:18:17.550 align:start position:0% and so forth and I think the best thing 00:18:17.550 --> 00:18:20.470 align:start position:0% and so forth and I think the best thing we<00:18:17.670> can<00:18:17.790> do<00:18:17.910> there<00:18:18.150> is<00:18:18.420> probably<00:18:19.080> to<00:18:19.350> have<00:18:19.530> some 00:18:20.470 --> 00:18:20.480 align:start position:0% we can do there is probably to have some 00:18:20.480 --> 00:18:23.720 align:start position:0% we can do there is probably to have some joint<00:18:21.480> benchmark<00:18:22.110> suite<00:18:22.350> or<00:18:22.830> you<00:18:23.340> know<00:18:23.460> some 00:18:23.720 --> 00:18:23.730 align:start position:0% joint benchmark suite or you know some 00:18:23.730 --> 00:18:25.940 align:start position:0% joint benchmark suite or you know some make<00:18:24.240> is<00:18:24.540> all<00:18:24.810> about<00:18:24.990> information<00:18:25.560> right<00:18:25.770> and 00:18:25.940 --> 00:18:25.950 align:start position:0% make is all about information right and 00:18:25.950 --> 00:18:28.250 align:start position:0% make is all about information right and making<00:18:26.070> it<00:18:26.220> consistent<00:18:26.550> and<00:18:27.030> so<00:18:27.180> people<00:18:28.020> can 00:18:28.250 --> 00:18:28.260 align:start position:0% making it consistent and so people can 00:18:28.260 --> 00:18:30.500 align:start position:0% making it consistent and so people can compare<00:18:28.890> and<00:18:29.190> contrast<00:18:29.310> and<00:18:29.940> you<00:18:30.240> know 00:18:30.500 --> 00:18:30.510 align:start position:0% compare and contrast and you know 00:18:30.510 --> 00:18:31.670 align:start position:0% compare and contrast and you know understand<00:18:30.840> which<00:18:30.990> is<00:18:31.170> the<00:18:31.260> client<00:18:31.440> that 00:18:31.670 --> 00:18:31.680 align:start position:0% understand which is the client that 00:18:31.680 --> 00:18:33.830 align:start position:0% understand which is the client that meets<00:18:31.860> their<00:18:32.670> needs<00:18:32.700> but<00:18:33.480> yeah<00:18:33.690> I<00:18:33.720> definitely 00:18:33.830 --> 00:18:33.840 align:start position:0% meets their needs but yeah I definitely 00:18:33.840 --> 00:18:35.630 align:start position:0% meets their needs but yeah I definitely like<00:18:34.200> to<00:18:34.410> see<00:18:34.440> a<00:18:34.500> diversity<00:18:34.920> I<00:18:35.160> think<00:18:35.430> it<00:18:35.520> would 00:18:35.630 --> 00:18:35.640 align:start position:0% like to see a diversity I think it would 00:18:35.640 --> 00:18:37.670 align:start position:0% like to see a diversity I think it would be<00:18:35.730> a<00:18:35.760> shame<00:18:36.000> if<00:18:36.060> the<00:18:36.510> network<00:18:36.840> were<00:18:36.990> dominated 00:18:37.670 --> 00:18:37.680 align:start position:0% be a shame if the network were dominated 00:18:37.680 --> 00:18:41.450 align:start position:0% be a shame if the network were dominated by<00:18:38.210> one<00:18:39.210> client<00:18:39.990> more<00:18:40.110> than<00:18:40.260> 50%<00:18:40.560> on<00:18:41.040> one 00:18:41.450 --> 00:18:41.460 align:start position:0% by one client more than 50% on one 00:18:41.460 --> 00:18:45.590 align:start position:0% by one client more than 50% on one client<00:18:41.820> would<00:18:41.940> be<00:18:42.090> would<00:18:42.390> be<00:18:42.420> a<00:18:42.540> pity<00:18:42.750> I<00:18:44.600> guess 00:18:45.590 --> 00:18:45.600 align:start position:0% client would be would be a pity I guess 00:18:45.600 --> 00:18:49.100 align:start position:0% client would be would be a pity I guess another<00:18:45.930> point<00:18:46.470> of<00:18:46.620> point<00:18:47.370> of<00:18:47.870> importance<00:18:48.870> is 00:18:49.100 --> 00:18:49.110 align:start position:0% another point of point of importance is 00:18:49.110 --> 00:18:51.860 align:start position:0% another point of point of importance is formally<00:18:49.590> verified<00:18:49.620> the<00:18:50.630> safety<00:18:51.630> and<00:18:51.720> live 00:18:51.860 --> 00:18:51.870 align:start position:0% formally verified the safety and live 00:18:51.870 --> 00:18:55.040 align:start position:0% formally verified the safety and live needs<00:18:52.200> of<00:18:52.290> the<00:18:52.410> beacon<00:18:52.650> chain<00:18:52.970> so<00:18:53.970> amazed<00:18:54.900> you 00:18:55.040 --> 00:18:55.050 align:start position:0% needs of the beacon chain so amazed you 00:18:55.050 --> 00:18:58.250 align:start position:0% needs of the beacon chain so amazed you know<00:18:55.080> that<00:18:55.800> I<00:18:56.310> mean<00:18:56.700> in<00:18:57.030> the<00:18:57.120> paper<00:18:57.300> was<00:18:57.600> the 00:18:58.250 --> 00:18:58.260 align:start position:0% know that I mean in the paper was the 00:18:58.260 --> 00:19:00.620 align:start position:0% know that I mean in the paper was the paper<00:18:58.980> that<00:18:59.130> proved<00:18:59.460> these<00:18:59.640> two<00:19:00.270> properties 00:19:00.620 --> 00:19:00.630 align:start position:0% paper that proved these two properties 00:19:00.630 --> 00:19:03.590 align:start position:0% paper that proved these two properties on<00:19:01.050> that<00:19:01.380> the<00:19:02.220> abstract<00:19:02.670> model<00:19:03.060> of<00:19:03.150> the<00:19:03.330> beacon 00:19:03.590 --> 00:19:03.600 align:start position:0% on that the abstract model of the beacon 00:19:03.600 --> 00:19:06.260 align:start position:0% on that the abstract model of the beacon chain<00:19:03.840> but<00:19:04.680> reality<00:19:04.950> is<00:19:05.370> the<00:19:05.760> implementation 00:19:06.260 --> 00:19:06.270 align:start position:0% chain but reality is the implementation 00:19:06.270 --> 00:19:08.690 align:start position:0% chain but reality is the implementation has<00:19:06.720> caught<00:19:07.500> a<00:19:07.530> lot<00:19:07.740> of<00:19:07.770> the<00:19:08.040> optimization<00:19:08.580> and 00:19:08.690 --> 00:19:08.700 align:start position:0% has caught a lot of the optimization and 00:19:08.700 --> 00:19:10.370 align:start position:0% has caught a lot of the optimization and also<00:19:09.000> it's<00:19:09.150> slightly<00:19:09.390> different<00:19:09.660> the 00:19:10.370 --> 00:19:10.380 align:start position:0% also it's slightly different the 00:19:10.380 --> 00:19:12.890 align:start position:0% also it's slightly different the finalization<00:19:10.860> rules<00:19:11.370> so<00:19:11.760> you<00:19:12.000> also<00:19:12.540> make<00:19:12.750> sure 00:19:12.890 --> 00:19:12.900 align:start position:0% finalization rules so you also make sure 00:19:12.900 --> 00:19:15.800 align:start position:0% finalization rules so you also make sure that<00:19:13.110> those<00:19:14.330> differences 00:19:15.800 --> 00:19:15.810 align:start position:0% that those differences 00:19:15.810 --> 00:19:17.720 align:start position:0% that those differences doesn't<00:19:16.200> actually<00:19:16.440> break<00:19:16.680> the<00:19:16.950> safety<00:19:17.670> and 00:19:17.720 --> 00:19:17.730 align:start position:0% doesn't actually break the safety and 00:19:17.730 --> 00:19:20.180 align:start position:0% doesn't actually break the safety and avenues<00:19:18.260> so<00:19:19.260> yeah<00:19:19.380> that's<00:19:19.650> our<00:19:19.740> actually 00:19:20.180 --> 00:19:20.190 align:start position:0% avenues so yeah that's our actually 00:19:20.190 --> 00:19:23.840 align:start position:0% avenues so yeah that's our actually calling<00:19:20.430> in<00:19:20.700> our<00:19:21.060> end<00:19:21.360> you<00:19:22.260> wanted<00:19:22.560> to<00:19:23.220> finish 00:19:23.840 --> 00:19:23.850 align:start position:0% calling in our end you wanted to finish 00:19:23.850 --> 00:19:27.620 align:start position:0% calling in our end you wanted to finish the<00:19:24.120> phone<00:19:24.360> verification<00:19:24.890> before<00:19:26.090> others<00:19:27.090> are 00:19:27.620 --> 00:19:27.630 align:start position:0% the phone verification before others are 00:19:27.630 --> 00:19:32.360 align:start position:0% the phone verification before others are actually<00:19:28.170> ready<00:19:28.740> to<00:19:28.830> release<00:19:30.800> and<00:19:31.800> the<00:19:32.010> the 00:19:32.360 --> 00:19:32.370 align:start position:0% actually ready to release and the the 00:19:32.370 --> 00:19:34.850 align:start position:0% actually ready to release and the the safety<00:19:32.760> of<00:19:32.850> all<00:19:32.970> our<00:19:33.000> clients<00:19:33.360> relies<00:19:34.170> on<00:19:34.530> this 00:19:34.850 --> 00:19:34.860 align:start position:0% safety of all our clients relies on this 00:19:34.860 --> 00:19:36.860 align:start position:0% safety of all our clients relies on this assumption<00:19:35.250> that<00:19:35.430> someone's<00:19:35.910> gonna<00:19:36.060> slash 00:19:36.860 --> 00:19:36.870 align:start position:0% assumption that someone's gonna slash 00:19:36.870 --> 00:19:39.500 align:start position:0% assumption that someone's gonna slash bad<00:19:37.200> people<00:19:37.650> I<00:19:38.130> don't<00:19:39.030> know<00:19:39.090> anyone<00:19:39.360> that's 00:19:39.500 --> 00:19:39.510 align:start position:0% bad people I don't know anyone that's 00:19:39.510 --> 00:19:42.440 align:start position:0% bad people I don't know anyone that's got<00:19:39.750> a<00:19:39.990> slash<00:19:40.860> of<00:19:41.040> working<00:19:41.340> that<00:19:41.460> can<00:19:41.730> that<00:19:42.300> can 00:19:42.440 --> 00:19:42.450 align:start position:0% got a slash of working that can that can 00:19:42.450 --> 00:19:45.200 align:start position:0% got a slash of working that can that can efficiently<00:19:42.900> run<00:19:43.820> they<00:19:44.820> can<00:19:44.940> efficiently 00:19:45.200 --> 00:19:45.210 align:start position:0% efficiently run they can efficiently 00:19:45.210 --> 00:19:47.690 align:start position:0% efficiently run they can efficiently cover<00:19:45.540> the<00:19:45.810> the<00:19:45.840> distance<00:19:46.410> that<00:19:46.560> we<00:19:46.650> need<00:19:46.860> and 00:19:47.690 --> 00:19:47.700 align:start position:0% cover the the distance that we need and 00:19:47.700 --> 00:19:49.310 align:start position:0% cover the the distance that we need and it's<00:19:47.790> still<00:19:48.030> in<00:19:48.150> research<00:19:48.480> as<00:19:48.900> to<00:19:48.930> you<00:19:49.230> know 00:19:49.310 --> 00:19:49.320 align:start position:0% it's still in research as to you know 00:19:49.320 --> 00:19:52.310 align:start position:0% it's still in research as to you know how<00:19:50.070> exactly<00:19:50.370> can<00:19:50.760> we<00:19:50.820> how<00:19:51.600> can<00:19:51.630> we<00:19:51.870> store<00:19:52.260> all 00:19:52.310 --> 00:19:52.320 align:start position:0% how exactly can we how can we store all 00:19:52.320 --> 00:19:54.680 align:start position:0% how exactly can we how can we store all of<00:19:52.740> the<00:19:52.890> previous<00:19:53.280> votes<00:19:53.580> and<00:19:54.210> efficiently 00:19:54.680 --> 00:19:54.690 align:start position:0% of the previous votes and efficiently 00:19:54.690 --> 00:19:57.020 align:start position:0% of the previous votes and efficiently search<00:19:54.960> them<00:19:55.230> so<00:19:56.040> we're<00:19:56.580> really<00:19:56.760> we're 00:19:57.020 --> 00:19:57.030 align:start position:0% search them so we're really we're 00:19:57.030 --> 00:19:58.250 align:start position:0% search them so we're really we're definitely<00:19:57.210> going<00:19:57.510> to<00:19:57.600> need 00:19:58.250 --> 00:19:58.260 align:start position:0% definitely going to need 00:19:58.260 --> 00:20:00.590 align:start position:0% definitely going to need Slash's<00:19:58.980> out<00:19:59.160> there<00:19:59.430> and<00:20:00.150> I<00:20:00.240> think<00:20:00.300> they're 00:20:00.590 --> 00:20:00.600 align:start position:0% Slash's out there and I think they're 00:20:00.600 --> 00:20:03.230 align:start position:0% Slash's out there and I think they're gonna<00:20:00.720> have<00:20:00.930> to<00:20:00.960> have<00:20:01.110> some<00:20:01.650> degree<00:20:01.800> of<00:20:02.240> review 00:20:03.230 --> 00:20:03.240 align:start position:0% gonna have to have some degree of review 00:20:03.240 --> 00:20:05.510 align:start position:0% gonna have to have some degree of review and<00:20:04.020> guarantee<00:20:04.500> that<00:20:04.530> you<00:20:05.130> know<00:20:05.340> they're 00:20:05.510 --> 00:20:05.520 align:start position:0% and guarantee that you know they're 00:20:05.520 --> 00:20:10.010 align:start position:0% and guarantee that you know they're watching<00:20:05.670> and<00:20:06.270> they'll<00:20:06.600> get<00:20:06.720> you<00:20:08.900> adding<00:20:09.900> on 00:20:10.010 --> 00:20:10.020 align:start position:0% watching and they'll get you adding on 00:20:10.020 --> 00:20:11.300 align:start position:0% watching and they'll get you adding on to<00:20:10.140> that<00:20:10.170> quickly<00:20:10.500> you<00:20:10.710> also<00:20:10.860> need<00:20:11.130> like 00:20:11.300 --> 00:20:11.310 align:start position:0% to that quickly you also need like 00:20:11.310 --> 00:20:13.610 align:start position:0% to that quickly you also need like slashing<00:20:11.850> protection<00:20:12.480> right<00:20:12.720> so<00:20:12.960> like<00:20:13.260> in 00:20:13.610 --> 00:20:13.620 align:start position:0% slashing protection right so like in 00:20:13.620 --> 00:20:15.680 align:start position:0% slashing protection right so like in terms<00:20:13.890> of<00:20:14.130> like<00:20:14.730> infrastructure<00:20:15.150> providers 00:20:15.680 --> 00:20:15.690 align:start position:0% terms of like infrastructure providers 00:20:15.690 --> 00:20:17.510 align:start position:0% terms of like infrastructure providers or<00:20:16.050> people<00:20:16.320> that<00:20:16.470> are<00:20:16.620> they<00:20:17.070> just<00:20:17.220> don't<00:20:17.370> want 00:20:17.510 --> 00:20:17.520 align:start position:0% or people that are they just don't want 00:20:17.520 --> 00:20:19.460 align:start position:0% or people that are they just don't want some<00:20:17.670> sort<00:20:17.850> of<00:20:17.940> crazy<00:20:18.270> situation<00:20:18.930> with<00:20:19.200> their 00:20:19.460 --> 00:20:19.470 align:start position:0% some sort of crazy situation with their 00:20:19.470 --> 00:20:22.850 align:start position:0% some sort of crazy situation with their infra<00:20:19.890> to<00:20:20.160> cause<00:20:20.340> them<00:20:20.640> to<00:20:21.090> double<00:20:21.660> propose<00:20:22.110> or 00:20:22.850 --> 00:20:22.860 align:start position:0% infra to cause them to double propose or 00:20:22.860 --> 00:20:25.220 align:start position:0% infra to cause them to double propose or double<00:20:23.130> sign<00:20:23.340> so<00:20:23.640> that's<00:20:24.420> also<00:20:24.660> something 00:20:25.220 --> 00:20:25.230 align:start position:0% double sign so that's also something 00:20:25.230 --> 00:20:27.830 align:start position:0% double sign so that's also something needs<00:20:25.500> to<00:20:25.590> be<00:20:25.680> built<00:20:25.860> in<00:20:26.010> and<00:20:26.730> users<00:20:27.630> will<00:20:27.780> be 00:20:27.830 --> 00:20:27.840 align:start position:0% needs to be built in and users will be 00:20:27.840 --> 00:20:31.280 align:start position:0% needs to be built in and users will be asking<00:20:28.380> for<00:20:28.410> that<00:20:28.680> I<00:20:29.840> totally<00:20:30.840> agree<00:20:31.050> with 00:20:31.280 --> 00:20:31.290 align:start position:0% asking for that I totally agree with 00:20:31.290 --> 00:20:33.350 align:start position:0% asking for that I totally agree with everything<00:20:31.680> that<00:20:31.890> Ben<00:20:32.190> said<00:20:32.460> and<00:20:32.820> one<00:20:33.090> just 00:20:33.350 --> 00:20:33.360 align:start position:0% everything that Ben said and one just 00:20:33.360 --> 00:20:36.050 align:start position:0% everything that Ben said and one just yet<00:20:33.690> that<00:20:34.020> we<00:20:34.530> might<00:20:34.980> probably<00:20:35.280> need<00:20:35.730> some 00:20:36.050 --> 00:20:36.060 align:start position:0% yet that we might probably need some 00:20:36.060 --> 00:20:39.890 align:start position:0% yet that we might probably need some more<00:20:36.570> QA<00:20:37.500> stuff<00:20:37.950> like<00:20:38.250> fuzzing<00:20:38.850> we<00:20:39.270> want<00:20:39.600> to<00:20:39.720> do 00:20:39.890 --> 00:20:39.900 align:start position:0% more QA stuff like fuzzing we want to do 00:20:39.900 --> 00:20:43.240 align:start position:0% more QA stuff like fuzzing we want to do cross<00:20:40.250> client<00:20:41.250> fuzzing<00:20:41.760> to<00:20:42.030> find<00:20:42.450> tricky 00:20:43.240 --> 00:20:43.250 align:start position:0% cross client fuzzing to find tricky 00:20:43.250 --> 00:20:46.070 align:start position:0% cross client fuzzing to find tricky consensus<00:20:44.250> breaks<00:20:44.550> that<00:20:45.330> could<00:20:45.690> not<00:20:46.050> be 00:20:46.070 --> 00:20:46.080 align:start position:0% consensus breaks that could not be 00:20:46.080 --> 00:20:48.050 align:start position:0% consensus breaks that could not be probably<00:20:46.860> fine 00:20:48.050 --> 00:20:48.060 align:start position:0% probably fine 00:20:48.060 --> 00:20:51.050 align:start position:0% probably fine it<00:20:48.660> could<00:20:48.870> not<00:20:49.020> be<00:20:49.050> probably<00:20:49.530> found<00:20:50.060> during 00:20:51.050 --> 00:20:51.060 align:start position:0% it could not be probably found during 00:20:51.060 --> 00:20:54.980 align:start position:0% it could not be probably found during test<00:20:51.570> net<00:20:51.840> runs<00:20:52.230> and<00:20:52.610> also<00:20:53.610> we<00:20:53.880> need<00:20:54.030> to<00:20:54.090> expose 00:20:54.980 --> 00:20:54.990 align:start position:0% test net runs and also we need to expose 00:20:54.990 --> 00:20:59.410 align:start position:0% test net runs and also we need to expose basic<00:20:55.710> interface<00:20:56.190> to<00:20:56.790> chain<00:20:57.150> data<00:20:57.510> to<00:20:58.410> build 00:20:59.410 --> 00:20:59.420 align:start position:0% basic interface to chain data to build 00:20:59.420 --> 00:21:02.510 align:start position:0% basic interface to chain data to build even<00:21:00.420> primitive<00:21:00.690> block<00:21:01.110> explorers<00:21:02.040> around 00:21:02.510 --> 00:21:02.520 align:start position:0% even primitive block explorers around 00:21:02.520 --> 00:21:07.310 align:start position:0% even primitive block explorers around that<00:21:02.850> and<00:21:03.090> to<00:21:03.930> get<00:21:04.710> some<00:21:05.180> network<00:21:06.180> monitors<00:21:06.690> to 00:21:07.310 --> 00:21:07.320 align:start position:0% that and to get some network monitors to 00:21:07.320 --> 00:21:10.790 align:start position:0% that and to get some network monitors to understand<00:21:07.800> what<00:21:07.980> is<00:21:08.100> going<00:21:08.250> on<00:21:09.320> so<00:21:10.320> yeah 00:21:10.790 --> 00:21:10.800 align:start position:0% understand what is going on so yeah 00:21:10.800 --> 00:21:13.270 align:start position:0% understand what is going on so yeah that's<00:21:11.310> that's<00:21:12.120> my<00:21:12.360> point 00:21:13.270 --> 00:21:13.280 align:start position:0% that's that's my point 00:21:13.280 --> 00:21:15.230 align:start position:0% that's that's my point another<00:21:14.280> fun<00:21:14.490> thing<00:21:14.520> leading<00:21:15.120> up<00:21:15.210> to 00:21:15.230 --> 00:21:15.240 align:start position:0% another fun thing leading up to 00:21:15.240 --> 00:21:16.700 align:start position:0% another fun thing leading up to production<00:21:15.570> would<00:21:15.870> be<00:21:15.930> incentive<00:21:16.380> ice<00:21:16.440> test 00:21:16.700 --> 00:21:16.710 align:start position:0% production would be incentive ice test 00:21:16.710 --> 00:21:18.800 align:start position:0% production would be incentive ice test nuts<00:21:16.950> so<00:21:17.790> in<00:21:17.940> a<00:21:18.030> cosmic<00:21:18.360> community<00:21:18.690> they've 00:21:18.800 --> 00:21:18.810 align:start position:0% nuts so in a cosmic community they've 00:21:18.810 --> 00:21:20.510 align:start position:0% nuts so in a cosmic community they've done<00:21:18.990> some<00:21:19.320> of<00:21:19.410> this<00:21:19.530> with<00:21:19.770> the<00:21:19.890> game<00:21:20.010> mistakes 00:21:20.510 --> 00:21:20.520 align:start position:0% done some of this with the game mistakes 00:21:20.520 --> 00:21:22.340 align:start position:0% done some of this with the game mistakes it'd<00:21:20.820> be<00:21:21.030> fun<00:21:21.210> if<00:21:21.240> we<00:21:21.390> do<00:21:21.540> the<00:21:21.630> same<00:21:21.780> thing<00:21:22.050> get 00:21:22.340 --> 00:21:22.350 align:start position:0% it'd be fun if we do the same thing get 00:21:22.350 --> 00:21:25.010 align:start position:0% it'd be fun if we do the same thing get together<00:21:22.530> prize<00:21:23.490> pool<00:21:23.760> and<00:21:24.210> the<00:21:24.570> idea<00:21:24.840> is<00:21:24.930> we 00:21:25.010 --> 00:21:25.020 align:start position:0% together prize pool and the idea is we 00:21:25.020 --> 00:21:26.570 align:start position:0% together prize pool and the idea is we have<00:21:25.110> a<00:21:25.140> test<00:21:25.380> net<00:21:25.560> public<00:21:25.890> test<00:21:26.100> net<00:21:26.280> anyone 00:21:26.570 --> 00:21:26.580 align:start position:0% have a test net public test net anyone 00:21:26.580 --> 00:21:29.000 align:start position:0% have a test net public test net anyone can<00:21:26.730> come<00:21:26.880> and<00:21:27.000> go<00:21:27.150> and<00:21:27.450> then<00:21:27.680> try<00:21:28.680> to<00:21:28.740> keep<00:21:28.920> the 00:21:29.000 --> 00:21:29.010 align:start position:0% can come and go and then try to keep the 00:21:29.010 --> 00:21:32.240 align:start position:0% can come and go and then try to keep the test<00:21:29.160> no<00:21:29.280> life<00:21:30.740> other<00:21:31.740> than<00:21:31.770> everything<00:21:32.130> would 00:21:32.240 --> 00:21:32.250 align:start position:0% test no life other than everything would 00:21:32.250 --> 00:21:33.920 align:start position:0% test no life other than everything would be<00:21:32.370> like<00:21:32.400> actually<00:21:32.730> talking<00:21:33.270> to<00:21:33.300> validators 00:21:33.920 --> 00:21:33.930 align:start position:0% be like actually talking to validators 00:21:33.930 --> 00:21:35.870 align:start position:0% be like actually talking to validators or<00:21:34.290> potential<00:21:34.890> validators<00:21:35.280> and<00:21:35.520> like<00:21:35.610> getting 00:21:35.870 --> 00:21:35.880 align:start position:0% or potential validators and like getting 00:21:35.880 --> 00:21:38.660 align:start position:0% or potential validators and like getting their<00:21:36.030> input<00:21:36.120> sort<00:21:36.570> of<00:21:36.660> been<00:21:36.750> like<00:21:36.870> a<00:21:37.670> product 00:21:38.660 --> 00:21:38.670 align:start position:0% their input sort of been like a product 00:21:38.670 --> 00:21:41.060 align:start position:0% their input sort of been like a product feedback<00:21:39.030> typesetting<00:21:39.720> I<00:21:40.020> think<00:21:40.650> we<00:21:40.830> were<00:21:40.920> all 00:21:41.060 --> 00:21:41.070 align:start position:0% feedback typesetting I think we were all 00:21:41.070 --> 00:21:42.830 align:start position:0% feedback typesetting I think we were all very<00:21:41.220> focused<00:21:41.670> on<00:21:41.850> like<00:21:42.000> the<00:21:42.180> spec<00:21:42.390> and<00:21:42.420> like 00:21:42.830 --> 00:21:42.840 align:start position:0% very focused on like the spec and like 00:21:42.840 --> 00:21:44.210 align:start position:0% very focused on like the spec and like the<00:21:42.960> engineering<00:21:43.350> and<00:21:43.650> like<00:21:43.770> making<00:21:44.040> really 00:21:44.210 --> 00:21:44.220 align:start position:0% the engineering and like making really 00:21:44.220 --> 00:21:46.850 align:start position:0% the engineering and like making really nice<00:21:44.370> sexy<00:21:44.850> clients<00:21:45.350> but<00:21:46.350> definitely<00:21:46.740> it's 00:21:46.850 --> 00:21:46.860 align:start position:0% nice sexy clients but definitely it's 00:21:46.860 --> 00:21:48.560 align:start position:0% nice sexy clients but definitely it's like<00:21:47.010> for<00:21:47.370> physio<00:21:47.820> who<00:21:48.120> are<00:21:48.240> the<00:21:48.330> users<00:21:48.420> of 00:21:48.560 --> 00:21:48.570 align:start position:0% like for physio who are the users of 00:21:48.570 --> 00:21:51.680 align:start position:0% like for physio who are the users of these<00:21:48.780> things<00:21:49.050> well<00:21:49.440> validators<00:21:50.160> so<00:21:50.700> talking 00:21:51.680 --> 00:21:51.690 align:start position:0% these things well validators so talking 00:21:51.690 --> 00:21:53.210 align:start position:0% these things well validators so talking to<00:21:51.720> operators<00:21:52.410> of<00:21:52.650> validating<00:21:53.190> that 00:21:53.210 --> 00:21:53.220 align:start position:0% to operators of validating that 00:21:53.220 --> 00:21:56.210 align:start position:0% to operators of validating that validation<00:21:53.820> pools<00:21:54.150> and<00:21:54.800> not<00:21:55.800> actually<00:21:56.040> just 00:21:56.210 --> 00:21:56.220 align:start position:0% validation pools and not actually just 00:21:56.220 --> 00:21:59.330 align:start position:0% validation pools and not actually just pools<00:21:56.490> but<00:21:56.760> validators<00:21:57.600> in<00:21:57.750> general<00:21:58.050> and<00:21:58.340> yeah 00:21:59.330 --> 00:21:59.340 align:start position:0% pools but validators in general and yeah 00:21:59.340 --> 00:22:04.580 align:start position:0% pools but validators in general and yeah seen<00:21:59.730> seen<00:22:00.240> how<00:22:00.600> that<00:22:00.750> process<00:22:00.900> unfolds<00:22:03.590> sorry 00:22:04.580 --> 00:22:04.590 align:start position:0% seen seen how that process unfolds sorry 00:22:04.590 --> 00:22:07.490 align:start position:0% seen seen how that process unfolds sorry one<00:22:04.770> more<00:22:04.950> I<00:22:05.340> think<00:22:05.640> we<00:22:05.880> need<00:22:06.030> some<00:22:06.930> interest 00:22:07.490 --> 00:22:07.500 align:start position:0% one more I think we need some interest 00:22:07.500 --> 00:22:11.540 align:start position:0% one more I think we need some interest from<00:22:08.330> external<00:22:09.330> I<00:22:10.230> get<00:22:10.830> guys<00:22:10.950> know<00:22:11.250> inclined 00:22:11.540 --> 00:22:11.550 align:start position:0% from external I get guys know inclined 00:22:11.550 --> 00:22:12.169 align:start position:0% from external I get guys know inclined developer<00:22:12.000> team 00:22:12.169 --> 00:22:12.179 align:start position:0% developer team 00:22:12.179 --> 00:22:14.659 align:start position:0% developer team you<00:22:12.480> eye<00:22:12.509> people<00:22:13.169> so<00:22:13.499> I<00:22:13.529> think<00:22:13.679> a<00:22:14.009> lot<00:22:14.309> of<00:22:14.340> the 00:22:14.659 --> 00:22:14.669 align:start position:0% you eye people so I think a lot of the 00:22:14.669 --> 00:22:16.369 align:start position:0% you eye people so I think a lot of the client<00:22:15.119> developers<00:22:15.570> where<00:22:15.960> systems 00:22:16.369 --> 00:22:16.379 align:start position:0% client developers where systems 00:22:16.379 --> 00:22:19.519 align:start position:0% client developers where systems programmers<00:22:17.299> and<00:22:18.299> the<00:22:18.509> idea<00:22:18.840> of<00:22:18.929> choosing<00:22:19.470> a 00:22:19.519 --> 00:22:19.529 align:start position:0% programmers and the idea of choosing a 00:22:19.529 --> 00:22:23.210 align:start position:0% programmers and the idea of choosing a color<00:22:19.740> makes<00:22:20.039> a<00:22:20.159> sweat<00:22:21.350> so<00:22:22.350> it<00:22:22.950> would<00:22:23.039> be<00:22:23.129> great 00:22:23.210 --> 00:22:23.220 align:start position:0% color makes a sweat so it would be great 00:22:23.220 --> 00:22:25.460 align:start position:0% color makes a sweat so it would be great to<00:22:23.460> have<00:22:23.639> and<00:22:24.389> we<00:22:24.480> don't<00:22:24.600> we<00:22:24.749> don't<00:22:24.869> I<00:22:25.110> think<00:22:25.230> at 00:22:25.460 --> 00:22:25.470 align:start position:0% to have and we don't we don't I think at 00:22:25.470 --> 00:22:27.590 align:start position:0% to have and we don't we don't I think at the<00:22:25.559> moment<00:22:25.830> have<00:22:26.009> maybe<00:22:26.789> a<00:22:26.850> few<00:22:27.090> of<00:22:27.269> people 00:22:27.590 --> 00:22:27.600 align:start position:0% the moment have maybe a few of people 00:22:27.600 --> 00:22:28.999 align:start position:0% the moment have maybe a few of people that<00:22:27.869> are<00:22:28.019> like<00:22:28.259> you<00:22:28.409> know<00:22:28.470> front-end<00:22:28.860> devs 00:22:28.999 --> 00:22:29.009 align:start position:0% that are like you know front-end devs 00:22:29.009 --> 00:22:30.409 align:start position:0% that are like you know front-end devs that<00:22:29.220> are<00:22:29.340> that<00:22:29.580> are<00:22:29.639> interested<00:22:30.149> in<00:22:30.240> building 00:22:30.409 --> 00:22:30.419 align:start position:0% that are that are interested in building 00:22:30.419 --> 00:22:32.590 align:start position:0% that are that are interested in building UIs<00:22:30.899> for<00:22:31.049> this<00:22:31.259> and<00:22:31.980> it'd<00:22:32.070> be<00:22:32.100> great<00:22:32.249> to<00:22:32.340> have 00:22:32.590 --> 00:22:32.600 align:start position:0% UIs for this and it'd be great to have 00:22:32.600 --> 00:22:36.769 align:start position:0% UIs for this and it'd be great to have these<00:22:33.600> things<00:22:33.929> as<00:22:34.740> a<00:22:34.799> common<00:22:35.279> good<00:22:35.610> that<00:22:35.779> lives 00:22:36.769 --> 00:22:36.779 align:start position:0% these things as a common good that lives 00:22:36.779 --> 00:22:38.960 align:start position:0% these things as a common good that lives outside<00:22:37.200> of<00:22:37.499> the<00:22:37.740> client<00:22:38.100> teams<00:22:38.309> that<00:22:38.669> gets<00:22:38.850> to 00:22:38.960 --> 00:22:38.970 align:start position:0% outside of the client teams that gets to 00:22:38.970 --> 00:22:42.350 align:start position:0% outside of the client teams that gets to love<00:22:39.119> that<00:22:39.269> they<00:22:39.419> deserve<00:22:39.690> and<00:22:41.149> on<00:22:42.149> top<00:22:42.330> of 00:22:42.350 --> 00:22:42.360 align:start position:0% love that they deserve and on top of 00:22:42.360 --> 00:22:44.629 align:start position:0% love that they deserve and on top of that<00:22:42.480> I<00:22:42.570> think<00:22:42.809> it's<00:22:42.929> very<00:22:43.429> important<00:22:44.429> for<00:22:44.519> the 00:22:44.629 --> 00:22:44.639 align:start position:0% that I think it's very important for the 00:22:44.639 --> 00:22:47.230 align:start position:0% that I think it's very important for the the<00:22:44.820> general<00:22:44.999> validating<00:22:45.539> experiences<00:22:46.169> to<00:22:46.379> to 00:22:47.230 --> 00:22:47.240 align:start position:0% the general validating experiences to to 00:22:47.240 --> 00:22:49.850 align:start position:0% the general validating experiences to to not<00:22:48.240> only<00:22:48.480> just<00:22:48.809> help<00:22:49.019> them<00:22:49.200> with<00:22:49.499> the<00:22:49.619> general 00:22:49.850 --> 00:22:49.860 align:start position:0% not only just help them with the general 00:22:49.860 --> 00:22:51.049 align:start position:0% not only just help them with the general running<00:22:49.980> of<00:22:50.100> the<00:22:50.159> clients<00:22:50.460> but<00:22:50.580> what<00:22:50.730> happens 00:22:51.049 --> 00:22:51.059 align:start position:0% running of the clients but what happens 00:22:51.059 --> 00:22:52.970 align:start position:0% running of the clients but what happens when<00:22:51.269> validators<00:22:52.230> get<00:22:52.379> slashed<00:22:52.619> how<00:22:52.830> do<00:22:52.889> we 00:22:52.970 --> 00:22:52.980 align:start position:0% when validators get slashed how do we 00:22:52.980 --> 00:22:56.299 align:start position:0% when validators get slashed how do we notify<00:22:53.340> them<00:22:53.519> of<00:22:53.610> this<00:22:53.820> or<00:22:54.950> when<00:22:55.950> there's<00:22:56.100> this 00:22:56.299 --> 00:22:56.309 align:start position:0% notify them of this or when there's this 00:22:56.309 --> 00:22:58.999 align:start position:0% notify them of this or when there's this major<00:22:56.519> chain<00:22:56.820> consensus<00:22:57.419> how<00:22:57.629> do<00:22:57.690> you<00:22:57.840> if<00:22:58.799> your 00:22:58.999 --> 00:22:59.009 align:start position:0% major chain consensus how do you if your 00:22:59.009 --> 00:23:00.200 align:start position:0% major chain consensus how do you if your clients<00:22:59.340> not<00:22:59.490> updating<00:22:59.940> or<00:23:00.059> there's 00:23:00.200 --> 00:23:00.210 align:start position:0% clients not updating or there's 00:23:00.210 --> 00:23:01.549 align:start position:0% clients not updating or there's something<00:23:00.360> did<00:23:00.779> this<00:23:01.019> there's<00:23:01.440> some 00:23:01.549 --> 00:23:01.559 align:start position:0% something did this there's some 00:23:01.559 --> 00:23:03.139 align:start position:0% something did this there's some fundamental<00:23:01.980> issue<00:23:02.129> how<00:23:02.549> do<00:23:02.610> we<00:23:02.730> notify 00:23:03.139 --> 00:23:03.149 align:start position:0% fundamental issue how do we notify 00:23:03.149 --> 00:23:05.450 align:start position:0% fundamental issue how do we notify clients<00:23:03.749> like<00:23:03.899> of<00:23:04.320> these<00:23:04.559> problems<00:23:04.950> and<00:23:05.159> I 00:23:05.450 --> 00:23:05.460 align:start position:0% clients like of these problems and I 00:23:05.460 --> 00:23:06.950 align:start position:0% clients like of these problems and I mean<00:23:05.850> we<00:23:06.119> could<00:23:06.269> trouble<00:23:06.419> you<00:23:06.539> have<00:23:06.720> some 00:23:06.950 --> 00:23:06.960 align:start position:0% mean we could trouble you have some 00:23:06.960 --> 00:23:08.779 align:start position:0% mean we could trouble you have some central<00:23:07.440> solution<00:23:07.590> which<00:23:08.070> sends<00:23:08.639> you<00:23:08.700> an 00:23:08.779 --> 00:23:08.789 align:start position:0% central solution which sends you an 00:23:08.789 --> 00:23:10.369 align:start position:0% central solution which sends you an email<00:23:08.909> or<00:23:09.119> something<00:23:09.450> but<00:23:09.659> having<00:23:10.230> people 00:23:10.369 --> 00:23:10.379 align:start position:0% email or something but having people 00:23:10.379 --> 00:23:11.810 align:start position:0% email or something but having people register<00:23:10.919> they<00:23:11.009> validators<00:23:11.519> with<00:23:11.669> such<00:23:11.789> a 00:23:11.810 --> 00:23:11.820 align:start position:0% register they validators with such a 00:23:11.820 --> 00:23:13.399 align:start position:0% register they validators with such a thing<00:23:12.029> as<00:23:12.149> a<00:23:12.179> kind<00:23:12.480> of<00:23:12.570> scary<00:23:12.779> concept<00:23:13.230> from<00:23:13.289> a 00:23:13.399 --> 00:23:13.409 align:start position:0% thing as a kind of scary concept from a 00:23:13.409 --> 00:23:16.549 align:start position:0% thing as a kind of scary concept from a privacy<00:23:13.740> standpoint<00:23:14.070> so<00:23:14.879> how<00:23:15.360> can<00:23:15.419> we<00:23:15.720> how<00:23:16.529> can 00:23:16.549 --> 00:23:16.559 align:start position:0% privacy standpoint so how can we how can 00:23:16.559 --> 00:23:18.409 align:start position:0% privacy standpoint so how can we how can we<00:23:16.799> enable<00:23:17.129> these<00:23:17.429> kinds<00:23:17.669> of<00:23:17.700> things<00:23:17.850> which<00:23:18.179> I 00:23:18.409 --> 00:23:18.419 align:start position:0% we enable these kinds of things which I 00:23:18.419 --> 00:23:20.960 align:start position:0% we enable these kinds of things which I think<00:23:18.450> also<00:23:18.929> very<00:23:19.049> important<00:23:19.679> for<00:23:20.490> the<00:23:20.580> for 00:23:20.960 --> 00:23:20.970 align:start position:0% think also very important for the for 00:23:20.970 --> 00:23:23.119 align:start position:0% think also very important for the for the<00:23:21.059> community<00:23:21.450> and<00:23:21.570> and<00:23:21.809> to<00:23:22.409> help<00:23:22.559> validators 00:23:23.119 --> 00:23:23.129 align:start position:0% the community and and to help validators 00:23:23.129 --> 00:23:24.769 align:start position:0% the community and and to help validators understand<00:23:23.639> a<00:23:23.850> what<00:23:24.029> their<00:23:24.179> clients<00:23:24.299> doing 00:23:24.769 --> 00:23:24.779 align:start position:0% understand a what their clients doing 00:23:24.779 --> 00:23:27.019 align:start position:0% understand a what their clients doing and<00:23:24.990> how<00:23:25.889> they<00:23:26.039> can<00:23:26.100> stay<00:23:26.669> on<00:23:26.759> to<00:23:26.850> all<00:23:26.909> the 00:23:27.019 --> 00:23:27.029 align:start position:0% and how they can stay on to all the 00:23:27.029 --> 00:23:34.220 align:start position:0% and how they can stay on to all the things<00:23:31.039> cool<00:23:32.119> well<00:23:33.119> with<00:23:33.570> that<00:23:33.720> I<00:23:33.749> think<00:23:33.929> cuz 00:23:34.220 --> 00:23:34.230 align:start position:0% things cool well with that I think cuz 00:23:34.230 --> 00:23:35.330 align:start position:0% things cool well with that I think cuz we<00:23:34.320> were<00:23:34.440> heading<00:23:34.649> into<00:23:34.769> the<00:23:34.889> final<00:23:35.100> minutes 00:23:35.330 --> 00:23:35.340 align:start position:0% we were heading into the final minutes 00:23:35.340 --> 00:23:36.859 align:start position:0% we were heading into the final minutes yeah<00:23:35.490> I'd<00:23:35.759> like<00:23:35.999> to<00:23:36.149> open<00:23:36.570> the<00:23:36.659> floor<00:23:36.690> to 00:23:36.859 --> 00:23:36.869 align:start position:0% yeah I'd like to open the floor to 00:23:36.869 --> 00:23:39.350 align:start position:0% yeah I'd like to open the floor to questions<00:23:36.990> for<00:23:37.679> anyone<00:23:38.070> who'd<00:23:38.309> like<00:23:38.460> to<00:23:38.490> talk 00:23:39.350 --> 00:23:39.360 align:start position:0% questions for anyone who'd like to talk 00:23:39.360 --> 00:23:42.320 align:start position:0% questions for anyone who'd like to talk about<00:23:39.559> anything<00:23:40.559> related<00:23:40.769> to<00:23:41.330> immediate 00:23:42.320 --> 00:23:42.330 align:start position:0% about anything related to immediate 00:23:42.330 --> 00:23:47.269 align:start position:0% about anything related to immediate future<00:23:42.419> v3<00:23:42.840> Pune<00:23:45.019> I'm<00:23:46.019> somewhat<00:23:46.710> forwarding 00:23:47.269 --> 00:23:47.279 align:start position:0% future v3 Pune I'm somewhat forwarding 00:23:47.279 --> 00:23:50.330 align:start position:0% future v3 Pune I'm somewhat forwarding this<00:23:47.429> question<00:23:47.970> from<00:23:48.649> Philip<00:23:49.649> casting<00:23:50.159> guy 00:23:50.330 --> 00:23:50.340 align:start position:0% this question from Philip casting guy 00:23:50.340 --> 00:23:52.879 align:start position:0% this question from Philip casting guy from<00:23:50.809> horizon<00:23:51.809> games<00:23:52.019> and<00:23:52.379> the<00:23:52.499> fairway<00:23:52.830> and 00:23:52.879 --> 00:23:52.889 align:start position:0% from horizon games and the fairway and 00:23:52.889 --> 00:23:56.749 align:start position:0% from horizon games and the fairway and Ponzi<00:23:53.369> scheme<00:23:53.639> revelation<00:23:55.369> my<00:23:56.369> name<00:23:56.519> is<00:23:56.610> John 00:23:56.749 --> 00:23:56.759 align:start position:0% Ponzi scheme revelation my name is John 00:23:56.759 --> 00:23:58.549 align:start position:0% Ponzi scheme revelation my name is John Marlon<00:23:57.059> I<00:23:57.179> do<00:23:57.240> security<00:23:57.779> audits<00:23:58.200> so<00:23:58.350> I'm<00:23:58.440> not 00:23:58.549 --> 00:23:58.559 align:start position:0% Marlon I do security audits so I'm not 00:23:58.559 --> 00:24:00.710 align:start position:0% Marlon I do security audits so I'm not adaptive<00:23:59.129> but<00:23:59.460> I<00:23:59.789> know<00:23:59.999> a<00:24:00.179> lot<00:24:00.360> about<00:24:00.389> smart 00:24:00.710 --> 00:24:00.720 align:start position:0% adaptive but I know a lot about smart 00:24:00.720 --> 00:24:04.190 align:start position:0% adaptive but I know a lot about smart contracts<00:24:01.110> and<00:24:01.879> his<00:24:02.879> question<00:24:03.210> is<00:24:03.509> about<00:24:03.659> like 00:24:04.190 --> 00:24:04.200 align:start position:0% contracts and his question is about like 00:24:04.200 --> 00:24:08.690 align:start position:0% contracts and his question is about like the<00:24:04.320> migration<00:24:04.860> process<00:24:05.809> and<00:24:07.340> if<00:24:08.340> there<00:24:08.549> will 00:24:08.690 --> 00:24:08.700 align:start position:0% the migration process and if there will 00:24:08.700 --> 00:24:11.830 align:start position:0% the migration process and if there will be<00:24:08.759> if<00:24:09.119> there<00:24:09.330> are<00:24:09.419> plans<00:24:09.720> for<00:24:09.960> doing<00:24:10.350> any 00:24:11.830 --> 00:24:11.840 align:start position:0% be if there are plans for doing any 00:24:11.840 --> 00:24:18.289 align:start position:0% be if there are plans for doing any migration<00:24:12.840> testing<00:24:13.799> for<00:24:15.110> gaps<00:24:16.549> moving<00:24:17.549> to<00:24:17.820> the 00:24:18.289 --> 00:24:18.299 align:start position:0% migration testing for gaps moving to the 00:24:18.299 --> 00:24:20.840 align:start position:0% migration testing for gaps moving to the youth<00:24:18.929> to<00:24:19.519> maintenance 00:24:20.840 --> 00:24:20.850 align:start position:0% youth to maintenance 00:24:20.850 --> 00:24:27.349 align:start position:0% youth to maintenance test<00:24:21.720> night 00:24:27.349 --> 00:24:27.359 align:start position:0% 00:24:27.359 --> 00:24:31.469 align:start position:0% yeah<00:24:28.359> no<00:24:28.570> definitely<00:24:28.959> so<00:24:29.229> the<00:24:29.669> the<00:24:30.669> migration 00:24:31.469 --> 00:24:31.479 align:start position:0% yeah no definitely so the the migration 00:24:31.479 --> 00:24:33.419 align:start position:0% yeah no definitely so the the migration from<00:24:31.629> f1<00:24:32.139> to<00:24:32.289> teeth<00:24:32.440> et<00:24:32.709> tu<00:24:32.979> is<00:24:33.159> clearly 00:24:33.419 --> 00:24:33.429 align:start position:0% from f1 to teeth et tu is clearly 00:24:33.429 --> 00:24:35.209 align:start position:0% from f1 to teeth et tu is clearly something<00:24:33.729> that<00:24:33.759> came<00:24:33.999> up<00:24:34.149> in<00:24:34.599> the 00:24:35.209 --> 00:24:35.219 align:start position:0% something that came up in the 00:24:35.219 --> 00:24:37.409 align:start position:0% something that came up in the discussions<00:24:36.219> yesterday<00:24:36.369> too<00:24:36.669> and<00:24:36.820> and<00:24:37.239> is<00:24:37.389> a 00:24:37.409 --> 00:24:37.419 align:start position:0% discussions yesterday too and and is a 00:24:37.419 --> 00:24:38.849 align:start position:0% discussions yesterday too and and is a very<00:24:37.629> important<00:24:38.049> thing<00:24:38.229> and<00:24:38.409> clearly<00:24:38.649> a<00:24:38.679> pain 00:24:38.849 --> 00:24:38.859 align:start position:0% very important thing and clearly a pain 00:24:38.859 --> 00:24:40.139 align:start position:0% very important thing and clearly a pain point<00:24:39.099> for<00:24:39.159> the<00:24:39.309> community<00:24:39.759> I<00:24:39.789> think<00:24:40.029> that's 00:24:40.139 --> 00:24:40.149 align:start position:0% point for the community I think that's 00:24:40.149 --> 00:24:41.549 align:start position:0% point for the community I think that's something<00:24:40.299> everyone<00:24:40.719> is<00:24:40.869> nervous<00:24:41.019> about<00:24:41.229> we 00:24:41.549 --> 00:24:41.559 align:start position:0% something everyone is nervous about we 00:24:41.559 --> 00:24:43.949 align:start position:0% something everyone is nervous about we have<00:24:41.709> this<00:24:41.799> great<00:24:42.009> community<00:24:42.519> within<00:24:42.959> varium 00:24:43.949 --> 00:24:43.959 align:start position:0% have this great community within varium 00:24:43.959 --> 00:24:46.529 align:start position:0% have this great community within varium one<00:24:44.289> how<00:24:44.559> can<00:24:44.619> we<00:24:45.009> we<00:24:45.279> transfer<00:24:46.179> that<00:24:46.329> as 00:24:46.529 --> 00:24:46.539 align:start position:0% one how can we we transfer that as 00:24:46.539 --> 00:24:48.269 align:start position:0% one how can we we transfer that as seamlessly<00:24:46.929> as<00:24:46.989> possible<00:24:47.589> we<00:24:47.979> don't<00:24:48.159> want 00:24:48.269 --> 00:24:48.279 align:start position:0% seamlessly as possible we don't want 00:24:48.279 --> 00:24:52.049 align:start position:0% seamlessly as possible we don't want bugs<00:24:48.489> in<00:24:48.699> any<00:24:48.849> of<00:24:48.940> these<00:24:49.029> scenarios<00:24:49.979> the<00:24:51.059> the 00:24:52.049 --> 00:24:52.059 align:start position:0% bugs in any of these scenarios the the 00:24:52.059 --> 00:24:54.419 align:start position:0% bugs in any of these scenarios the the verbs<00:24:52.299> the<00:24:53.169> challenge<00:24:53.829> with<00:24:53.949> answering<00:24:54.309> this 00:24:54.419 --> 00:24:54.429 align:start position:0% verbs the challenge with answering this 00:24:54.429 --> 00:24:58.349 align:start position:0% verbs the challenge with answering this question<00:24:54.579> is<00:24:55.089> that<00:24:55.389> right<00:24:55.569> now<00:24:56.669> we<00:24:57.669> have<00:24:58.179> such 00:24:58.349 --> 00:24:58.359 align:start position:0% question is that right now we have such 00:24:58.359 --> 00:24:59.939 align:start position:0% question is that right now we have such flexibility<00:24:58.959> in<00:24:59.109> the<00:24:59.199> space<00:24:59.440> that<00:24:59.619> is<00:24:59.769> very 00:24:59.939 --> 00:24:59.949 align:start position:0% flexibility in the space that is very 00:24:59.949 --> 00:25:01.409 align:start position:0% flexibility in the space that is very hard<00:25:00.129> to<00:25:00.190> answer<00:25:00.549> exactly<00:25:00.849> what<00:25:01.239> this<00:25:01.359> is 00:25:01.409 --> 00:25:01.419 align:start position:0% hard to answer exactly what this is 00:25:01.419 --> 00:25:03.949 align:start position:0% hard to answer exactly what this is going<00:25:01.629> to<00:25:01.719> look<00:25:01.899> like<00:25:02.049> so<00:25:02.109> it<00:25:02.379> is<00:25:02.409> some<00:25:03.099> form<00:25:03.399> of 00:25:03.949 --> 00:25:03.959 align:start position:0% going to look like so it is some form of 00:25:03.959 --> 00:25:07.459 align:start position:0% going to look like so it is some form of moving<00:25:04.959> routes<00:25:05.409> between<00:25:05.829> earth<00:25:06.549> 1<00:25:06.849> and<00:25:06.999> E<00:25:07.059> 2 00:25:07.459 --> 00:25:07.469 align:start position:0% moving routes between earth 1 and E 2 00:25:07.469 --> 00:25:12.149 align:start position:0% moving routes between earth 1 and E 2 and<00:25:09.209> we<00:25:10.229> will<00:25:11.229> have<00:25:11.349> an<00:25:11.440> execution<00:25:11.889> engine 00:25:12.149 --> 00:25:12.159 align:start position:0% and we will have an execution engine 00:25:12.159 --> 00:25:15.209 align:start position:0% and we will have an execution engine which<00:25:12.339> allows<00:25:12.549> each<00:25:13.119> one<00:25:13.449> to<00:25:13.809> run<00:25:14.289> very 00:25:15.209 --> 00:25:15.219 align:start position:0% which allows each one to run very 00:25:15.219 --> 00:25:17.549 align:start position:0% which allows each one to run very similarly<00:25:15.639> to<00:25:16.179> how<00:25:16.569> it<00:25:16.659> does<00:25:16.839> right<00:25:17.109> now<00:25:17.289> and 00:25:17.549 --> 00:25:17.559 align:start position:0% similarly to how it does right now and 00:25:17.559 --> 00:25:20.489 align:start position:0% similarly to how it does right now and that<00:25:18.009> will<00:25:18.190> be<00:25:18.389> very<00:25:19.389> well<00:25:19.509> tested<00:25:19.749> for<00:25:20.229> for 00:25:20.489 --> 00:25:20.499 align:start position:0% that will be very well tested for for 00:25:20.499 --> 00:25:22.379 align:start position:0% that will be very well tested for for these<00:25:20.559> kinds<00:25:20.889> of<00:25:20.919> purposes<00:25:21.129> but<00:25:21.940> I<00:25:21.969> think<00:25:22.239> the 00:25:22.379 --> 00:25:22.389 align:start position:0% these kinds of purposes but I think the 00:25:22.389 --> 00:25:24.919 align:start position:0% these kinds of purposes but I think the the<00:25:22.749> the<00:25:22.979> challenge<00:25:23.979> here<00:25:24.190> is<00:25:24.219> we're<00:25:24.639> trying 00:25:24.919 --> 00:25:24.929 align:start position:0% the the challenge here is we're trying 00:25:24.929 --> 00:25:28.229 align:start position:0% the the challenge here is we're trying with<00:25:26.099> with<00:25:27.099> these<00:25:27.249> execution<00:25:27.759> environments 00:25:28.229 --> 00:25:28.239 align:start position:0% with with these execution environments 00:25:28.239 --> 00:25:29.729 align:start position:0% with with these execution environments that<00:25:28.329> allow<00:25:28.419> us<00:25:28.509> such<00:25:28.809> flexibilities<00:25:29.499> and<00:25:29.529> so 00:25:29.729 --> 00:25:29.739 align:start position:0% that allow us such flexibilities and so 00:25:29.739 --> 00:25:32.459 align:start position:0% that allow us such flexibilities and so many<00:25:29.919> possibilities<00:25:30.279> we<00:25:30.729> trying<00:25:31.479> to<00:25:31.599> not<00:25:31.899> lock 00:25:32.459 --> 00:25:32.469 align:start position:0% many possibilities we trying to not lock 00:25:32.469 --> 00:25:34.349 align:start position:0% many possibilities we trying to not lock ourselves<00:25:32.649> down<00:25:33.039> just<00:25:33.399> to<00:25:33.609> to<00:25:33.849> committing<00:25:34.239> to 00:25:34.349 --> 00:25:34.359 align:start position:0% ourselves down just to to committing to 00:25:34.359 --> 00:25:35.549 align:start position:0% ourselves down just to to committing to saying<00:25:34.569> exactly<00:25:34.959> this<00:25:35.079> is<00:25:35.229> how<00:25:35.349> it's<00:25:35.499> gonna 00:25:35.549 --> 00:25:35.559 align:start position:0% saying exactly this is how it's gonna 00:25:35.559 --> 00:25:37.529 align:start position:0% saying exactly this is how it's gonna work<00:25:35.679> right<00:25:36.009> now<00:25:36.190> because<00:25:37.089> that<00:25:37.209> starts 00:25:37.529 --> 00:25:37.539 align:start position:0% work right now because that starts 00:25:37.539 --> 00:25:39.629 align:start position:0% work right now because that starts closing<00:25:37.869> down<00:25:38.109> the<00:25:38.319> the<00:25:38.649> design<00:25:39.009> space<00:25:39.309> for<00:25:39.519> us 00:25:39.629 --> 00:25:39.639 align:start position:0% closing down the the design space for us 00:25:39.639 --> 00:25:43.139 align:start position:0% closing down the the design space for us and<00:25:40.529> and<00:25:41.529> it<00:25:41.619> could<00:25:41.799> ultimately<00:25:42.369> end<00:25:42.789> up<00:25:42.969> in<00:25:43.059> a 00:25:43.139 --> 00:25:43.149 align:start position:0% and and it could ultimately end up in a 00:25:43.149 --> 00:25:46.079 align:start position:0% and and it could ultimately end up in a worse<00:25:43.299> product<00:25:43.659> so<00:25:43.899> the<00:25:44.529> the<00:25:45.279> answer<00:25:45.879> to<00:25:45.999> that 00:25:46.079 --> 00:25:46.089 align:start position:0% worse product so the the answer to that 00:25:46.089 --> 00:25:47.639 align:start position:0% worse product so the the answer to that is<00:25:46.239> yes<00:25:46.389> it<00:25:46.719> will<00:25:46.839> be<00:25:46.989> tested<00:25:47.379> there<00:25:47.499> will<00:25:47.619> be 00:25:47.639 --> 00:25:47.649 align:start position:0% is yes it will be tested there will be 00:25:47.649 --> 00:25:49.919 align:start position:0% is yes it will be tested there will be some<00:25:48.159> migration<00:25:48.639> path<00:25:48.879> exactly<00:25:49.659> what<00:25:49.779> that 00:25:49.919 --> 00:25:49.929 align:start position:0% some migration path exactly what that 00:25:49.929 --> 00:25:51.930 align:start position:0% some migration path exactly what that looks<00:25:50.199> like<00:25:50.379> I<00:25:50.529> can't<00:25:50.739> specify<00:25:50.949> right<00:25:51.399> now<00:25:51.579> but 00:25:51.930 --> 00:25:51.940 align:start position:0% looks like I can't specify right now but 00:25:51.940 --> 00:25:54.479 align:start position:0% looks like I can't specify right now but we<00:25:52.509> did<00:25:52.929> that<00:25:53.229> will<00:25:53.679> definitely<00:25:53.829> existent<00:25:54.399> is 00:25:54.479 --> 00:25:54.489 align:start position:0% we did that will definitely existent is 00:25:54.489 --> 00:25:58.049 align:start position:0% we did that will definitely existent is vital<00:25:55.119> for<00:25:55.149> for<00:25:55.809> the<00:25:56.079> continuation<00:25:56.559> of<00:25:57.059> a 00:25:58.049 --> 00:25:58.059 align:start position:0% vital for for the continuation of a 00:25:58.059 --> 00:26:01.619 align:start position:0% vital for for the continuation of a theorem<00:25:58.569> 2.0<00:25:59.699> and<00:26:00.699> just<00:26:00.909> add<00:26:01.029> on<00:26:01.149> to<00:26:01.239> that<00:26:01.299> like 00:26:01.619 --> 00:26:01.629 align:start position:0% theorem 2.0 and just add on to that like 00:26:01.629 --> 00:26:02.819 align:start position:0% theorem 2.0 and just add on to that like concretely<00:26:02.289> there's<00:26:02.469> definitely<00:26:02.769> an 00:26:02.819 --> 00:26:02.829 align:start position:0% concretely there's definitely an 00:26:02.829 --> 00:26:05.309 align:start position:0% concretely there's definitely an intention<00:26:03.249> to<00:26:03.519> essentially<00:26:04.269> move<00:26:04.719> eath<00:26:05.049> one 00:26:05.309 --> 00:26:05.319 align:start position:0% intention to essentially move eath one 00:26:05.319 --> 00:26:07.529 align:start position:0% intention to essentially move eath one into<00:26:05.799> the<00:26:05.979> new<00:26:06.129> eath<00:26:06.429> 2<00:26:06.669> infrastructure<00:26:07.209> in<00:26:07.449> a 00:26:07.529 --> 00:26:07.539 align:start position:0% into the new eath 2 infrastructure in a 00:26:07.539 --> 00:26:09.389 align:start position:0% into the new eath 2 infrastructure in a way<00:26:07.569> that<00:26:07.959> you<00:26:08.589> wouldn't<00:26:08.919> have<00:26:08.979> to<00:26:09.159> migrate 00:26:09.389 --> 00:26:09.399 align:start position:0% way that you wouldn't have to migrate 00:26:09.399 --> 00:26:11.369 align:start position:0% way that you wouldn't have to migrate your<00:26:09.759> adapt<00:26:09.999> and<00:26:10.299> it<00:26:10.779> would<00:26:10.899> just<00:26:11.049> continue<00:26:11.109> to 00:26:11.369 --> 00:26:11.379 align:start position:0% your adapt and it would just continue to 00:26:11.379 --> 00:26:14.909 align:start position:0% your adapt and it would just continue to run<00:26:12.389> not<00:26:13.389> quite<00:26:13.779> seamlessly<00:26:14.259> there'll<00:26:14.889> be 00:26:14.909 --> 00:26:14.919 align:start position:0% run not quite seamlessly there'll be 00:26:14.919 --> 00:26:16.799 align:start position:0% run not quite seamlessly there'll be some<00:26:15.309> sort<00:26:15.489> of<00:26:15.519> metadata<00:26:15.819> updates<00:26:16.239> of<00:26:16.449> like<00:26:16.629> Oh 00:26:16.799 --> 00:26:16.809 align:start position:0% some sort of metadata updates of like Oh 00:26:16.809 --> 00:26:18.859 align:start position:0% some sort of metadata updates of like Oh new<00:26:17.049> network<00:26:17.349> new<00:26:17.529> chain<00:26:17.769> that<00:26:18.309> sort<00:26:18.489> of<00:26:18.519> thing 00:26:18.859 --> 00:26:18.869 align:start position:0% new network new chain that sort of thing 00:26:18.869 --> 00:26:20.879 align:start position:0% new network new chain that sort of thing but<00:26:19.869> in<00:26:20.019> terms<00:26:20.199> of<00:26:20.319> like<00:26:20.469> you<00:26:20.619> would<00:26:20.709> enough 00:26:20.879 --> 00:26:20.889 align:start position:0% but in terms of like you would enough 00:26:20.889 --> 00:26:22.589 align:start position:0% but in terms of like you would enough like<00:26:21.069> rewrite<00:26:21.489> your<00:26:21.639> DAP<00:26:21.879> or<00:26:22.179> like<00:26:22.299> do<00:26:22.449> these 00:26:22.589 --> 00:26:22.599 align:start position:0% like rewrite your DAP or like do these 00:26:22.599 --> 00:26:25.409 align:start position:0% like rewrite your DAP or like do these things<00:26:23.279> that<00:26:24.279> being<00:26:24.489> said<00:26:24.729> there<00:26:25.089> will<00:26:25.179> be<00:26:25.239> an 00:26:25.409 --> 00:26:25.419 align:start position:0% things that being said there will be an 00:26:25.419 --> 00:26:27.809 align:start position:0% things that being said there will be an opt-in<00:26:25.809> upgrade<00:26:26.619> path<00:26:26.829> to<00:26:27.129> go<00:26:27.249> to<00:26:27.309> perhaps 00:26:27.809 --> 00:26:27.819 align:start position:0% opt-in upgrade path to go to perhaps 00:26:27.819 --> 00:26:30.389 align:start position:0% opt-in upgrade path to go to perhaps this<00:26:28.089> new<00:26:28.299> type<00:26:28.690> of<00:26:28.719> EVM<00:26:29.409> ee<00:26:29.649> that<00:26:29.949> karl<00:26:30.249> was 00:26:30.389 --> 00:26:30.399 align:start position:0% this new type of EVM ee that karl was 00:26:30.399 --> 00:26:32.959 align:start position:0% this new type of EVM ee that karl was alluding<00:26:30.669> to<00:26:30.789> which<00:26:31.719> you<00:26:31.839> get<00:26:31.989> like<00:26:32.169> a<00:26:32.349> lot<00:26:32.469> of 00:26:32.959 --> 00:26:32.969 align:start position:0% alluding to which you get like a lot of 00:26:32.969 --> 00:26:35.369 align:start position:0% alluding to which you get like a lot of honestly<00:26:33.969> like<00:26:34.149> great<00:26:34.419> improvements<00:26:34.929> on<00:26:35.139> top 00:26:35.369 --> 00:26:35.379 align:start position:0% honestly like great improvements on top 00:26:35.379 --> 00:26:36.210 align:start position:0% honestly like great improvements on top of<00:26:35.529> what<00:26:35.619> we<00:26:35.709> have<00:26:35.799> today 00:26:36.210 --> 00:26:36.220 align:start position:0% of what we have today 00:26:36.220 --> 00:26:41.549 align:start position:0% of what we have today so<00:26:37.620> yeah<00:26:38.620> keep<00:26:39.129> an<00:26:39.220> eye<00:26:39.309> out<00:26:39.809> and<00:26:40.809> I<00:26:41.350> think<00:26:41.409> a 00:26:41.549 --> 00:26:41.559 align:start position:0% so yeah keep an eye out and I think a 00:26:41.559 --> 00:26:43.470 align:start position:0% so yeah keep an eye out and I think a lot<00:26:41.679> of<00:26:41.710> this<00:26:41.919> ties<00:26:42.129> into<00:26:42.340> what<00:26:42.519> Griggs 00:26:43.470 --> 00:26:43.480 align:start position:0% lot of this ties into what Griggs 00:26:43.480 --> 00:26:45.450 align:start position:0% lot of this ties into what Griggs presentation<00:26:44.019> was<00:26:44.139> on<00:26:44.289> earlier<00:26:44.649> on<00:26:44.889> Harvey 00:26:45.450 --> 00:26:45.460 align:start position:0% presentation was on earlier on Harvey 00:26:45.460 --> 00:26:48.330 align:start position:0% presentation was on earlier on Harvey making<00:26:46.440> connections<00:26:47.440> and<00:26:47.620> building<00:26:48.159> common 00:26:48.330 --> 00:26:48.340 align:start position:0% making connections and building common 00:26:48.340 --> 00:26:50.669 align:start position:0% making connections and building common tooling<00:26:48.730> between<00:26:49.120> these<00:26:49.379> these<00:26:50.379> frameworks 00:26:50.669 --> 00:26:50.679 align:start position:0% tooling between these these frameworks 00:26:50.679 --> 00:26:52.860 align:start position:0% tooling between these these frameworks and<00:26:51.070> it's<00:26:51.610> very<00:26:51.789> important<00:26:52.389> to<00:26:52.509> have<00:26:52.659> these 00:26:52.860 --> 00:26:52.870 align:start position:0% and it's very important to have these 00:26:52.870 --> 00:26:55.499 align:start position:0% and it's very important to have these intermediate<00:26:53.470> tools<00:26:54.220> between<00:26:54.639> the<00:26:54.789> two 00:26:55.499 --> 00:26:55.509 align:start position:0% intermediate tools between the two 00:26:55.509 --> 00:26:56.299 align:start position:0% intermediate tools between the two chains 00:26:56.299 --> 00:26:56.309 align:start position:0% chains 00:26:56.309 --> 00:26:59.519 align:start position:0% chains it's<00:26:57.309> totally<00:26:57.759> having<00:26:58.690> a<00:26:58.779> easy<00:26:59.019> path<00:26:59.289> for 00:26:59.519 --> 00:26:59.529 align:start position:0% it's totally having a easy path for 00:26:59.529 --> 00:27:01.080 align:start position:0% it's totally having a easy path for upgrades<00:26:59.860> is<00:27:00.009> definitely<00:27:00.429> important<00:27:00.879> and 00:27:01.080 --> 00:27:01.090 align:start position:0% upgrades is definitely important and 00:27:01.090 --> 00:27:02.850 align:start position:0% upgrades is definitely important and it'll<00:27:01.509> be<00:27:01.600> there<00:27:01.809> something<00:27:02.409> else<00:27:02.500> worth 00:27:02.850 --> 00:27:02.860 align:start position:0% it'll be there something else worth 00:27:02.860 --> 00:27:04.619 align:start position:0% it'll be there something else worth considering<00:27:03.309> too<00:27:03.429> is<00:27:03.580> that<00:27:03.789> you<00:27:04.240> know<00:27:04.269> if<00:27:04.480> you 00:27:04.619 --> 00:27:04.629 align:start position:0% considering too is that you know if you 00:27:04.629 --> 00:27:07.350 align:start position:0% considering too is that you know if you if<00:27:05.350> if<00:27:05.769> you've<00:27:06.039> just<00:27:06.279> gone<00:27:06.549> from<00:27:06.879> like<00:27:07.090> this 00:27:07.350 --> 00:27:07.360 align:start position:0% if if you've just gone from like this 00:27:07.360 --> 00:27:09.080 align:start position:0% if if you've just gone from like this pocket<00:27:07.779> calculated<00:27:08.529> to<00:27:08.620> this<00:27:08.740> like 00:27:09.080 --> 00:27:09.090 align:start position:0% pocket calculated to this like 00:27:09.090 --> 00:27:12.659 align:start position:0% pocket calculated to this like multi-core<00:27:10.090> like<00:27:10.899> thousand<00:27:11.889> times<00:27:12.100> faster 00:27:12.659 --> 00:27:12.669 align:start position:0% multi-core like thousand times faster 00:27:12.669 --> 00:27:16.560 align:start position:0% multi-core like thousand times faster machine<00:27:13.029> that<00:27:13.960> perhaps<00:27:14.289> a<00:27:14.559> refactor<00:27:15.190> is<00:27:15.460> is<00:27:16.120> is 00:27:16.560 --> 00:27:16.570 align:start position:0% machine that perhaps a refactor is is is 00:27:16.570 --> 00:27:18.480 align:start position:0% machine that perhaps a refactor is is is gonna<00:27:16.809> be<00:27:16.990> important<00:27:17.830> for<00:27:17.919> a<00:27:17.980> lot<00:27:18.129> of<00:27:18.159> the<00:27:18.279> taps 00:27:18.480 --> 00:27:18.490 align:start position:0% gonna be important for a lot of the taps 00:27:18.490 --> 00:27:20.100 align:start position:0% gonna be important for a lot of the taps like<00:27:18.759> we're<00:27:19.179> not<00:27:19.299> not<00:27:19.509> saying<00:27:19.779> that<00:27:19.929> like 00:27:20.100 --> 00:27:20.110 align:start position:0% like we're not not saying that like 00:27:20.110 --> 00:27:21.840 align:start position:0% like we're not not saying that like you're<00:27:20.259> gonna<00:27:20.350> have<00:27:20.529> to<00:27:20.649> refactor<00:27:21.039> but<00:27:21.429> you 00:27:21.840 --> 00:27:21.850 align:start position:0% you're gonna have to refactor but you 00:27:21.850 --> 00:27:23.399 align:start position:0% you're gonna have to refactor but you got<00:27:21.970> a<00:27:22.000> lot<00:27:22.179> to<00:27:22.299> do<00:27:22.389> it<00:27:22.509> like<00:27:22.690> you<00:27:22.809> got<00:27:23.169> a<00:27:23.230> whole 00:27:23.399 --> 00:27:23.409 align:start position:0% got a lot to do it like you got a whole 00:27:23.409 --> 00:27:26.909 align:start position:0% got a lot to do it like you got a whole new<00:27:23.559> space<00:27:23.799> to<00:27:24.039> play<00:27:24.220> and<00:27:24.399> now<00:27:24.549> so<00:27:25.860> it<00:27:26.860> might 00:27:26.909 --> 00:27:26.919 align:start position:0% new space to play and now so it might 00:27:26.919 --> 00:27:28.619 align:start position:0% new space to play and now so it might might<00:27:27.429> bring<00:27:27.580> a<00:27:27.639> refactor<00:27:28.090> might<00:27:28.240> be<00:27:28.360> what<00:27:28.509> you 00:27:28.619 --> 00:27:28.629 align:start position:0% might bring a refactor might be what you 00:27:28.629 --> 00:27:30.450 align:start position:0% might bring a refactor might be what you end<00:27:28.750> up<00:27:28.809> choose<00:27:29.049> doing<00:27:29.379> because<00:27:29.529> it<00:27:29.620> will<00:27:29.710> be 00:27:30.450 --> 00:27:30.460 align:start position:0% end up choose doing because it will be 00:27:30.460 --> 00:27:34.470 align:start position:0% end up choose doing because it will be better<00:27:30.580> for<00:27:30.759> your<00:27:30.909> customers<00:27:32.909> or<00:27:33.909> not 00:27:34.470 --> 00:27:34.480 align:start position:0% better for your customers or not 00:27:34.480 --> 00:27:36.299 align:start position:0% better for your customers or not customers<00:27:35.080> people<00:27:35.440> that<00:27:35.590> are<00:27:35.710> using<00:27:36.039> your 00:27:36.299 --> 00:27:36.309 align:start position:0% customers people that are using your 00:27:36.309 --> 00:27:38.190 align:start position:0% customers people that are using your thing<00:27:36.519> opting<00:27:36.879> in<00:27:37.029> without<00:27:37.240> any<00:27:37.480> control<00:27:38.019> from 00:27:38.190 --> 00:27:38.200 align:start position:0% thing opting in without any control from 00:27:38.200 --> 00:27:48.269 align:start position:0% thing opting in without any control from you<00:27:45.870> where's<00:27:46.870> this<00:27:47.080> conversation<00:27:47.769> happening 00:27:48.269 --> 00:27:48.279 align:start position:0% you where's this conversation happening 00:27:48.279 --> 00:27:50.249 align:start position:0% you where's this conversation happening where<00:27:48.789> do<00:27:48.909> you<00:27:49.000> guys<00:27:49.120> like<00:27:49.450> you<00:27:49.779> know<00:27:49.870> interact 00:27:50.249 --> 00:27:50.259 align:start position:0% where do you guys like you know interact 00:27:50.259 --> 00:27:51.629 align:start position:0% where do you guys like you know interact with<00:27:50.409> the<00:27:50.529> DAP<00:27:50.710> dev<00:27:50.919> community<00:27:51.399> so<00:27:51.490> they<00:27:51.610> can 00:27:51.629 --> 00:27:51.639 align:start position:0% with the DAP dev community so they can 00:27:51.639 --> 00:27:54.659 align:start position:0% with the DAP dev community so they can ask<00:27:51.879> those<00:27:52.090> questions<00:27:52.240> it's<00:27:53.230> hey<00:27:53.919> I<00:27:53.950> can<00:27:54.429> speak 00:27:54.659 --> 00:27:54.669 align:start position:0% ask those questions it's hey I can speak 00:27:54.669 --> 00:27:56.129 align:start position:0% ask those questions it's hey I can speak on<00:27:54.789> behalf<00:27:54.940> of<00:27:55.210> that<00:27:55.360> a<00:27:55.389> little<00:27:55.539> bit<00:27:55.690> like 00:27:56.129 --> 00:27:56.139 align:start position:0% on behalf of that a little bit like 00:27:56.139 --> 00:27:58.110 align:start position:0% on behalf of that a little bit like we're<00:27:56.529> a<00:27:56.559> little<00:27:56.649> bit<00:27:57.070> early<00:27:57.100> still<00:27:57.669> you<00:27:58.000> know 00:27:58.110 --> 00:27:58.120 align:start position:0% we're a little bit early still you know 00:27:58.120 --> 00:28:00.990 align:start position:0% we're a little bit early still you know that's<00:27:58.330> like<00:27:58.480> phase<00:27:58.750> two<00:27:59.289> and<00:27:59.679> to<00:28:00.669> be<00:28:00.789> quite 00:28:00.990 --> 00:28:01.000 align:start position:0% that's like phase two and to be quite 00:28:01.000 --> 00:28:02.850 align:start position:0% that's like phase two and to be quite frank<00:28:01.029> like<00:28:01.539> the<00:28:01.659> role<00:28:01.840> a<00:28:02.080> lot<00:28:02.289> of<00:28:02.440> confusion 00:28:02.850 --> 00:28:02.860 align:start position:0% frank like the role a lot of confusion 00:28:02.860 --> 00:28:04.379 align:start position:0% frank like the role a lot of confusion around<00:28:02.950> this<00:28:03.190> is<00:28:03.309> because<00:28:03.580> like<00:28:03.789> some<00:28:04.000> of<00:28:04.120> the 00:28:04.379 --> 00:28:04.389 align:start position:0% around this is because like some of the 00:28:04.389 --> 00:28:05.820 align:start position:0% around this is because like some of the as<00:28:04.629> Carl<00:28:04.929> explains<00:28:05.230> it<00:28:05.350> like<00:28:05.379> the<00:28:05.559> design 00:28:05.820 --> 00:28:05.830 align:start position:0% as Carl explains it like the design 00:28:05.830 --> 00:28:07.680 align:start position:0% as Carl explains it like the design space<00:28:06.100> is<00:28:06.129> so<00:28:06.340> open<00:28:06.700> but<00:28:07.210> it<00:28:07.299> makes<00:28:07.450> it<00:28:07.570> also 00:28:07.680 --> 00:28:07.690 align:start position:0% space is so open but it makes it also 00:28:07.690 --> 00:28:09.840 align:start position:0% space is so open but it makes it also super<00:28:08.019> complicated<00:28:08.320> like<00:28:09.070> a<00:28:09.309> lot<00:28:09.580> of<00:28:09.610> people<00:28:09.730> I 00:28:09.840 --> 00:28:09.850 align:start position:0% super complicated like a lot of people I 00:28:09.850 --> 00:28:11.970 align:start position:0% super complicated like a lot of people I feel<00:28:10.000> like<00:28:10.120> rethink<00:28:10.690> the<00:28:10.990> way<00:28:11.139> this<00:28:11.470> is<00:28:11.679> I<00:28:11.710> mean 00:28:11.970 --> 00:28:11.980 align:start position:0% feel like rethink the way this is I mean 00:28:11.980 --> 00:28:13.529 align:start position:0% feel like rethink the way this is I mean how<00:28:12.100> long<00:28:12.250> did<00:28:12.460> it<00:28:12.490> take<00:28:12.549> most<00:28:12.940> developers<00:28:13.450> to 00:28:13.529 --> 00:28:13.539 align:start position:0% how long did it take most developers to 00:28:13.539 --> 00:28:15.990 align:start position:0% how long did it take most developers to actually<00:28:13.629> understand<00:28:14.080> the<00:28:14.110> EVM<00:28:14.500> like<00:28:15.370> two 00:28:15.990 --> 00:28:16.000 align:start position:0% actually understand the EVM like two 00:28:16.000 --> 00:28:16.379 align:start position:0% actually understand the EVM like two years 00:28:16.379 --> 00:28:16.389 align:start position:0% years 00:28:16.389 --> 00:28:18.960 align:start position:0% years like<00:28:16.960> before<00:28:17.320> people<00:28:17.529> like<00:28:17.769> fully<00:28:18.610> understood 00:28:18.960 --> 00:28:18.970 align:start position:0% like before people like fully understood 00:28:18.970 --> 00:28:20.279 align:start position:0% like before people like fully understood so<00:28:19.330> it's<00:28:19.600> gonna<00:28:19.690> take<00:28:19.899> some<00:28:20.080> time<00:28:20.110> to 00:28:20.279 --> 00:28:20.289 align:start position:0% so it's gonna take some time to 00:28:20.289 --> 00:28:22.619 align:start position:0% so it's gonna take some time to understand<00:28:20.679> these<00:28:20.799> new<00:28:20.950> concepts<00:28:21.429> and<00:28:21.639> once 00:28:22.619 --> 00:28:22.629 align:start position:0% understand these new concepts and once 00:28:22.629 --> 00:28:24.869 align:start position:0% understand these new concepts and once that<00:28:22.750> happens<00:28:23.110> you'll<00:28:23.289> see<00:28:23.500> a<00:28:23.529> lot<00:28:23.710> better<00:28:23.879> I 00:28:24.869 --> 00:28:24.879 align:start position:0% that happens you'll see a lot better I 00:28:24.879 --> 00:28:26.879 align:start position:0% that happens you'll see a lot better I don't<00:28:25.480> think<00:28:25.659> it's<00:28:25.779> immediate<00:28:26.200> to<00:28:26.320> fully 00:28:26.879 --> 00:28:26.889 align:start position:0% don't think it's immediate to fully 00:28:26.889 --> 00:28:29.039 align:start position:0% don't think it's immediate to fully discuss<00:28:27.519> with<00:28:27.700> them<00:28:27.850> I<00:28:27.879> think<00:28:28.059> the<00:28:28.539> first 00:28:29.039 --> 00:28:29.049 align:start position:0% discuss with them I think the first 00:28:29.049 --> 00:28:30.330 align:start position:0% discuss with them I think the first priority<00:28:29.169> is<00:28:29.350> just<00:28:29.559> talking<00:28:30.039> with<00:28:30.159> like 00:28:30.330 --> 00:28:30.340 align:start position:0% priority is just talking with like 00:28:30.340 --> 00:28:31.649 align:start position:0% priority is just talking with like tooling<00:28:30.669> teams<00:28:30.879> to<00:28:31.000> understand<00:28:31.330> that<00:28:31.480> we<00:28:31.539> can 00:28:31.649 --> 00:28:31.659 align:start position:0% tooling teams to understand that we can 00:28:31.659 --> 00:28:34.350 align:start position:0% tooling teams to understand that we can better<00:28:31.750> help<00:28:31.899> them<00:28:32.110> and<00:28:33.059> concurrently<00:28:34.059> going 00:28:34.350 --> 00:28:34.360 align:start position:0% better help them and concurrently going 00:28:34.360 --> 00:28:36.629 align:start position:0% better help them and concurrently going with<00:28:34.480> adapt<00:28:34.690> developers<00:28:35.230> yeah<00:28:36.009> the<00:28:36.159> quilt 00:28:36.629 --> 00:28:36.639 align:start position:0% with adapt developers yeah the quilt 00:28:36.639 --> 00:28:38.249 align:start position:0% with adapt developers yeah the quilt team<00:28:36.820> deserves<00:28:37.210> a<00:28:37.330> plug<00:28:37.570> here<00:28:37.779> -<00:28:37.960> they're 00:28:38.249 --> 00:28:38.259 align:start position:0% team deserves a plug here - they're 00:28:38.259 --> 00:28:42.629 align:start position:0% team deserves a plug here - they're building<00:28:38.649> a<00:28:40.409> simulator<00:28:41.409> so<00:28:41.830> that<00:28:42.070> you<00:28:42.460> can 00:28:42.629 --> 00:28:42.639 align:start position:0% building a simulator so that you can 00:28:42.639 --> 00:28:45.149 align:start position:0% building a simulator so that you can build<00:28:42.940> II's<00:28:43.899> or<00:28:44.139> tests<00:28:44.350> on<00:28:44.500> top<00:28:44.679> of<00:28:44.830> e's 00:28:45.149 --> 00:28:45.159 align:start position:0% build II's or tests on top of e's 00:28:45.159 --> 00:28:46.950 align:start position:0% build II's or tests on top of e's without<00:28:46.149> needing<00:28:46.419> all<00:28:46.539> the<00:28:46.750> chain 00:28:46.950 --> 00:28:46.960 align:start position:0% without needing all the chain 00:28:46.960 --> 00:28:48.149 align:start position:0% without needing all the chain infrastructure<00:28:47.529> you<00:28:47.619> can<00:28:47.740> just<00:28:47.919> start<00:28:48.070> a 00:28:48.149 --> 00:28:48.159 align:start position:0% infrastructure you can just start a 00:28:48.159 --> 00:28:49.980 align:start position:0% infrastructure you can just start a process<00:28:48.369> and<00:28:48.759> start<00:28:48.970> start<00:28:49.210> testing<00:28:49.720> so 00:28:49.980 --> 00:28:49.990 align:start position:0% process and start start testing so 00:28:49.990 --> 00:28:51.779 align:start position:0% process and start start testing so I<00:28:50.020> think<00:28:50.830> this<00:28:51.250> is<00:28:51.370> something<00:28:51.520> that's<00:28:51.700> gonna 00:28:51.779 --> 00:28:51.789 align:start position:0% I think this is something that's gonna 00:28:51.789 --> 00:28:53.909 align:start position:0% I think this is something that's gonna really<00:28:51.880> enabled<00:28:52.630> app<00:28:52.809> developers<00:28:53.409> developers 00:28:53.909 --> 00:28:53.919 align:start position:0% really enabled app developers developers 00:28:53.919 --> 00:28:55.680 align:start position:0% really enabled app developers developers to<00:28:54.070> get<00:28:54.159> involved<00:28:54.610> because<00:28:54.789> it's<00:28:55.090> a<00:28:55.149> bit<00:28:55.360> a<00:28:55.510> bit 00:28:55.680 --> 00:28:55.690 align:start position:0% to get involved because it's a bit a bit 00:28:55.690 --> 00:28:57.299 align:start position:0% to get involved because it's a bit a bit low<00:28:56.020> level<00:28:56.350> at<00:28:56.440> the<00:28:56.500> moment<00:28:56.529> I<00:28:56.860> think<00:28:56.919> for<00:28:57.100> them 00:28:57.299 --> 00:28:57.309 align:start position:0% low level at the moment I think for them 00:28:57.309 --> 00:29:02.610 align:start position:0% low level at the moment I think for them but<00:28:58.210> it's<00:28:58.330> opening<00:28:58.630> up<00:28:58.750> to<00:28:58.899> them<00:29:00.899> so<00:29:01.899> we<00:29:02.500> were 00:29:02.610 --> 00:29:02.620 align:start position:0% but it's opening up to them so we were 00:29:02.620 --> 00:29:05.399 align:start position:0% but it's opening up to them so we were at<00:29:02.710> interrupts<00:29:03.100> to<00:29:03.159> lose<00:29:03.669> my<00:29:03.820> blog<00:29:04.059> and<00:29:04.409> we're 00:29:05.399 --> 00:29:05.409 align:start position:0% at interrupts to lose my blog and we're 00:29:05.409 --> 00:29:08.730 align:start position:0% at interrupts to lose my blog and we're very<00:29:05.590> grateful<00:29:05.890> I<00:29:06.700> think<00:29:07.299> we<00:29:07.419> was<00:29:08.320> fun<00:29:08.500> to<00:29:08.620> work 00:29:08.730 --> 00:29:08.740 align:start position:0% very grateful I think we was fun to work 00:29:08.740 --> 00:29:09.919 align:start position:0% very grateful I think we was fun to work with<00:29:08.799> out<00:29:09.039> of<00:29:09.130> you 00:29:09.919 --> 00:29:09.929 align:start position:0% with out of you 00:29:09.929 --> 00:29:12.750 align:start position:0% with out of you we<00:29:10.929> did<00:29:11.080> a<00:29:11.110> couple<00:29:11.260> changes<00:29:11.740> so<00:29:12.159> that's<00:29:12.610> also 00:29:12.750 --> 00:29:12.760 align:start position:0% we did a couple changes so that's also 00:29:12.760 --> 00:29:14.159 align:start position:0% we did a couple changes so that's also an<00:29:12.909> announcement<00:29:13.000> for<00:29:13.419> change<00:29:13.929> safe<00:29:14.049> in 00:29:14.159 --> 00:29:14.169 align:start position:0% an announcement for change safe in 00:29:14.169 --> 00:29:16.860 align:start position:0% an announcement for change safe in particular<00:29:14.409> so<00:29:14.770> we<00:29:14.919> support<00:29:15.220> alpine<00:29:15.750> so<00:29:16.750> we 00:29:16.860 --> 00:29:16.870 align:start position:0% particular so we support alpine so we 00:29:16.870 --> 00:29:19.110 align:start position:0% particular so we support alpine so we don't<00:29:17.049> be<00:29:17.200> to<00:29:18.070> mess<00:29:18.669> around 00:29:19.110 --> 00:29:19.120 align:start position:0% don't be to mess around 00:29:19.120 --> 00:29:24.360 align:start position:0% don't be to mess around if<00:29:19.450> you<00:29:19.659> alpine<00:29:20.500> for<00:29:21.039> docker<00:29:21.250> images<00:29:21.659> so<00:29:23.370> it 00:29:24.360 --> 00:29:24.370 align:start position:0% if you alpine for docker images so it 00:29:24.370 --> 00:29:25.919 align:start position:0% if you alpine for docker images so it would<00:29:24.520> be<00:29:24.640> pretty<00:29:24.789> easy<00:29:25.029> for<00:29:25.299> us<00:29:25.419> to<00:29:25.450> set<00:29:25.750> up<00:29:25.840> a 00:29:25.919 --> 00:29:25.929 align:start position:0% would be pretty easy for us to set up a 00:29:25.929 --> 00:29:28.110 align:start position:0% would be pretty easy for us to set up a test<00:29:26.080> it<00:29:26.289> was<00:29:26.409> your<00:29:26.559> stuff<00:29:26.830> I<00:29:27.130> think<00:29:27.640> we<00:29:28.000> just 00:29:28.110 --> 00:29:28.120 align:start position:0% test it was your stuff I think we just 00:29:28.120 --> 00:29:31.950 align:start position:0% test it was your stuff I think we just do<00:29:28.570> you<00:29:28.630> have<00:29:28.750> a<00:29:28.779> docker<00:29:29.169> image<00:29:30.450> okay<00:29:31.450> cool<00:29:31.750> and 00:29:31.950 --> 00:29:31.960 align:start position:0% do you have a docker image okay cool and 00:29:31.960 --> 00:29:34.370 align:start position:0% do you have a docker image okay cool and Wade<00:29:32.770> you<00:29:32.890> have<00:29:32.919> a<00:29:33.039> docker<00:29:33.250> image<00:29:33.460> as<00:29:33.580> well 00:29:34.370 --> 00:29:34.380 align:start position:0% Wade you have a docker image as well 00:29:34.380 --> 00:29:38.159 align:start position:0% Wade you have a docker image as well okay<00:29:35.380> all<00:29:35.590> right<00:29:35.710> so<00:29:36.360> if<00:29:37.360> we<00:29:37.510> can<00:29:37.659> help<00:29:37.870> in<00:29:38.049> any 00:29:38.159 --> 00:29:38.169 align:start position:0% okay all right so if we can help in any 00:29:38.169 --> 00:29:40.880 align:start position:0% okay all right so if we can help in any way<00:29:38.610> we're<00:29:39.610> here<00:29:39.700> to<00:29:39.850> help<00:29:40.000> right<00:29:40.419> yeah<00:29:40.840> just 00:29:40.880 --> 00:29:40.890 align:start position:0% way we're here to help right yeah just 00:29:40.890 --> 00:29:43.409 align:start position:0% way we're here to help right yeah just give<00:29:41.890> you<00:29:41.950> this<00:29:42.130> like<00:29:42.460> credits<00:29:43.029> and<00:29:43.179> fonts 00:29:43.409 --> 00:29:43.419 align:start position:0% give you this like credits and fonts 00:29:43.419 --> 00:29:47.159 align:start position:0% give you this like credits and fonts with<00:29:43.510> that<00:29:43.600> so<00:29:44.250> please<00:29:45.250> involve<00:29:45.970> us<00:29:46.120> and<00:29:46.570> we'll 00:29:47.159 --> 00:29:47.169 align:start position:0% with that so please involve us and we'll 00:29:47.169 --> 00:29:56.149 align:start position:0% with that so please involve us and we'll be<00:29:47.260> happy<00:29:47.470> to<00:29:54.029> a<00:29:55.029> couple<00:29:55.600> you<00:29:55.779> you<00:29:56.020> know 00:29:56.149 --> 00:29:56.159 align:start position:0% be happy to a couple you you know 00:29:56.159 --> 00:29:59.399 align:start position:0% be happy to a couple you you know probably<00:29:57.159> know<00:29:57.580> like<00:29:58.000> some<00:29:58.480> of<00:29:58.600> the<00:29:58.659> eath<00:29:59.140> one 00:29:59.399 --> 00:29:59.409 align:start position:0% probably know like some of the eath one 00:29:59.409 --> 00:30:02.010 align:start position:0% probably know like some of the eath one core<00:29:59.770> core<00:30:00.220> devs<00:30:00.490> but<00:30:00.820> usually<00:30:01.299> a<00:30:01.600> lot<00:30:01.809> of<00:30:01.840> them 00:30:02.010 --> 00:30:02.020 align:start position:0% core core devs but usually a lot of them 00:30:02.020 --> 00:30:06.029 align:start position:0% core core devs but usually a lot of them are<00:30:02.250> kind<00:30:03.250> of<00:30:03.370> like<00:30:03.549> detached<00:30:03.970> so<00:30:04.770> it's<00:30:05.770> like 00:30:06.029 --> 00:30:06.039 align:start position:0% are kind of like detached so it's like 00:30:06.039 --> 00:30:08.789 align:start position:0% are kind of like detached so it's like if<00:30:06.330> if<00:30:07.330> there<00:30:07.570> were<00:30:07.690> some<00:30:08.020> things<00:30:08.289> with<00:30:08.559> eath 00:30:08.789 --> 00:30:08.799 align:start position:0% if if there were some things with eath 00:30:08.799 --> 00:30:11.639 align:start position:0% if if there were some things with eath to<00:30:09.070> designs<00:30:09.779> that<00:30:10.779> you<00:30:10.990> would<00:30:11.140> want<00:30:11.409> them<00:30:11.620> to 00:30:11.639 --> 00:30:11.649 align:start position:0% to designs that you would want them to 00:30:11.649 --> 00:30:16.260 align:start position:0% to designs that you would want them to like<00:30:11.980> try<00:30:12.309> to<00:30:12.370> look<00:30:13.210> at<00:30:14.130> like<00:30:15.130> maybe<00:30:15.520> each<00:30:16.059> of 00:30:16.260 --> 00:30:16.270 align:start position:0% like try to look at like maybe each of 00:30:16.270 --> 00:30:18.330 align:start position:0% like try to look at like maybe each of you<00:30:16.390> it's<00:30:16.539> like<00:30:16.720> what<00:30:16.990> what<00:30:17.470> is<00:30:17.590> it<00:30:17.620> that<00:30:17.770> you 00:30:18.330 --> 00:30:18.340 align:start position:0% you it's like what what is it that you 00:30:18.340 --> 00:30:20.460 align:start position:0% you it's like what what is it that you would<00:30:18.520> really<00:30:18.700> like<00:30:18.850> them<00:30:19.210> to<00:30:19.320> look<00:30:20.320> at 00:30:20.460 --> 00:30:20.470 align:start position:0% would really like them to look at 00:30:20.470 --> 00:30:22.350 align:start position:0% would really like them to look at because<00:30:20.679> there's<00:30:20.980> a<00:30:21.039> lot<00:30:21.220> of<00:30:21.360> brainpower 00:30:22.350 --> 00:30:22.360 align:start position:0% because there's a lot of brainpower 00:30:22.360 --> 00:30:27.710 align:start position:0% because there's a lot of brainpower there<00:30:22.870> as<00:30:22.990> well<00:30:23.200> thanks<00:30:25.830> sing<00:30:26.830> strategies 00:30:27.710 --> 00:30:27.720 align:start position:0% there as well thanks sing strategies 00:30:27.720 --> 00:30:32.149 align:start position:0% there as well thanks sing strategies [Music] 00:30:32.149 --> 00:30:32.159 align:start position:0% 00:30:32.159 --> 00:30:34.649 align:start position:0% we're<00:30:33.159> running<00:30:33.370> out<00:30:33.460> of<00:30:33.490> time<00:30:33.610> so<00:30:33.970> can<00:30:34.390> we<00:30:34.510> use 00:30:34.649 --> 00:30:34.659 align:start position:0% we're running out of time so can we use 00:30:34.659 --> 00:30:36.480 align:start position:0% we're running out of time so can we use this<00:30:34.779> as<00:30:34.960> like<00:30:35.140> sort<00:30:35.350> of<00:30:35.380> a<00:30:35.529> wrapping<00:30:36.159> up<00:30:36.279> thing 00:30:36.480 --> 00:30:36.490 align:start position:0% this as like sort of a wrapping up thing 00:30:36.490 --> 00:30:46.789 align:start position:0% this as like sort of a wrapping up thing as<00:30:36.669> what<00:30:37.630> yeah<00:30:40.350> data<00:30:41.350> serialization<00:30:45.690> API 00:30:46.789 --> 00:30:46.799 align:start position:0% as what yeah data serialization API 00:30:46.799 --> 00:30:50.039 align:start position:0% as what yeah data serialization API standardization<00:30:47.799> efforts<00:30:48.510> okay<00:30:49.510> this<00:30:49.750> is<00:30:49.899> not 00:30:50.039 --> 00:30:50.049 align:start position:0% standardization efforts okay this is not 00:30:50.049 --> 00:30:52.889 align:start position:0% standardization efforts okay this is not just<00:30:50.289> a<00:30:50.440> single<00:30:50.620> line<00:30:51.510> still<00:30:52.510> working<00:30:52.809> on 00:30:52.889 --> 00:30:52.899 align:start position:0% just a single line still working on 00:30:52.899 --> 00:30:54.630 align:start position:0% just a single line still working on Trinity<00:30:53.289> we<00:30:53.529> actually<00:30:53.770> have<00:30:53.860> a<00:30:53.919> focus<00:30:54.279> of<00:30:54.490> both 00:30:54.630 --> 00:30:54.640 align:start position:0% Trinity we actually have a focus of both 00:30:54.640 --> 00:30:58.110 align:start position:0% Trinity we actually have a focus of both eath<00:30:54.970> one<00:30:55.270> any<00:30:55.510> two<00:30:55.960> so<00:30:56.710> I<00:30:57.340> actually<00:30:57.820> feel<00:30:58.000> like 00:30:58.110 --> 00:30:58.120 align:start position:0% eath one any two so I actually feel like 00:30:58.120 --> 00:30:59.580 align:start position:0% eath one any two so I actually feel like I've<00:30:58.179> been<00:30:58.299> exposed<00:30:58.570> a<00:30:58.870> lot<00:30:59.049> to<00:30:59.260> a<00:30:59.289> lot<00:30:59.350> of<00:30:59.470> the 00:30:59.580 --> 00:30:59.590 align:start position:0% I've been exposed a lot to a lot of the 00:30:59.590 --> 00:31:01.110 align:start position:0% I've been exposed a lot to a lot of the eath<00:30:59.740> one<00:30:59.950> efforts<00:31:00.429> and<00:31:00.580> ongoing<00:31:00.669> two<00:31:00.940> things 00:31:01.110 --> 00:31:01.120 align:start position:0% eath one efforts and ongoing two things 00:31:01.120 --> 00:31:03.480 align:start position:0% eath one efforts and ongoing two things and<00:31:01.360> like<00:31:01.990> really<00:31:02.169> from<00:31:02.350> what<00:31:02.440> I've<00:31:02.529> seen<00:31:02.620> like 00:31:03.480 --> 00:31:03.490 align:start position:0% and like really from what I've seen like 00:31:03.490 --> 00:31:06.389 align:start position:0% and like really from what I've seen like both<00:31:03.760> groups<00:31:04.390> of<00:31:04.840> quote<00:31:05.529> weirdos<00:31:05.919> are<00:31:06.250> like 00:31:06.389 --> 00:31:06.399 align:start position:0% both groups of quote weirdos are like 00:31:06.399 --> 00:31:08.310 align:start position:0% both groups of quote weirdos are like starting<00:31:07.149> to<00:31:07.419> really<00:31:07.600> just<00:31:07.840> tackle<00:31:08.080> the<00:31:08.140> same 00:31:08.310 --> 00:31:08.320 align:start position:0% starting to really just tackle the same 00:31:08.320 --> 00:31:11.010 align:start position:0% starting to really just tackle the same questions<00:31:08.880> I<00:31:09.880> could<00:31:10.480> pick<00:31:10.570> one<00:31:10.600> that<00:31:10.750> comes<00:31:10.899> to 00:31:11.010 --> 00:31:11.020 align:start position:0% questions I could pick one that comes to 00:31:11.020 --> 00:31:12.950 align:start position:0% questions I could pick one that comes to mind<00:31:11.140> is<00:31:11.289> like<00:31:11.409> state<00:31:11.679> management<00:31:12.190> and<00:31:12.309> things 00:31:12.950 --> 00:31:12.960 align:start position:0% mind is like state management and things 00:31:12.960 --> 00:31:15.810 align:start position:0% mind is like state management and things we<00:31:13.960> obviously<00:31:14.140> want<00:31:14.590> to<00:31:14.679> like<00:31:14.860> you<00:31:15.130> know<00:31:15.549> we've 00:31:15.810 --> 00:31:15.820 align:start position:0% we obviously want to like you know we've 00:31:15.820 --> 00:31:17.430 align:start position:0% we obviously want to like you know we've seen<00:31:15.850> what<00:31:16.149> has<00:31:16.480> happened<00:31:16.809> on<00:31:16.870> 8th<00:31:16.990> one<00:31:17.200> in 00:31:17.430 --> 00:31:17.440 align:start position:0% seen what has happened on 8th one in 00:31:17.440 --> 00:31:19.470 align:start position:0% seen what has happened on 8th one in terms<00:31:18.070> of<00:31:18.220> the<00:31:18.309> state<00:31:18.520> growing<00:31:19.059> and<00:31:19.299> growing 00:31:19.470 --> 00:31:19.480 align:start position:0% terms of the state growing and growing 00:31:19.480 --> 00:31:22.769 align:start position:0% terms of the state growing and growing and<00:31:19.809> growing<00:31:20.049> and<00:31:20.610> we<00:31:21.610> want<00:31:21.820> to<00:31:22.000> you<00:31:22.750> know 00:31:22.769 --> 00:31:22.779 align:start position:0% and growing and we want to you know 00:31:22.779 --> 00:31:25.110 align:start position:0% and growing and we want to you know basically<00:31:23.320> find<00:31:23.980> a<00:31:24.130> solution<00:31:24.309> 8th<00:31:24.640> -<00:31:24.909> we're 00:31:25.110 --> 00:31:25.120 align:start position:0% basically find a solution 8th - we're 00:31:25.120 --> 00:31:27.840 align:start position:0% basically find a solution 8th - we're like<00:31:25.270> that's<00:31:25.480> not<00:31:25.990> going<00:31:26.230> to<00:31:26.289> be<00:31:26.409> a<00:31:26.440> problem 00:31:27.840 --> 00:31:27.850 align:start position:0% like that's not going to be a problem 00:31:27.850 --> 00:31:29.370 align:start position:0% like that's not going to be a problem and<00:31:28.120> yeah<00:31:28.510> like<00:31:28.750> the<00:31:28.840> law<00:31:28.929> there's<00:31:29.169> lot<00:31:29.320> of 00:31:29.370 --> 00:31:29.380 align:start position:0% and yeah like the law there's lot of 00:31:29.380 --> 00:31:30.630 align:start position:0% and yeah like the law there's lot of cool<00:31:29.500> ideas<00:31:29.559> are<00:31:29.830> like<00:31:29.860> state<00:31:30.159> those<00:31:30.309> clients 00:31:30.630 --> 00:31:30.640 align:start position:0% cool ideas are like state those clients 00:31:30.640 --> 00:31:33.000 align:start position:0% cool ideas are like state those clients and<00:31:30.760> things<00:31:30.909> that<00:31:31.200> again<00:31:32.200> have<00:31:32.440> application 00:31:33.000 --> 00:31:33.010 align:start position:0% and things that again have application 00:31:33.010 --> 00:31:37.620 align:start position:0% and things that again have application in<00:31:33.070> both<00:31:33.220> domains<00:31:35.309> might<00:31:36.309> be<00:31:36.460> I<00:31:36.820> think<00:31:37.210> a<00:31:37.539> good 00:31:37.620 --> 00:31:37.630 align:start position:0% in both domains might be I think a good 00:31:37.630 --> 00:31:39.810 align:start position:0% in both domains might be I think a good thing<00:31:37.690> we<00:31:37.899> can<00:31:38.020> learn<00:31:38.140> is<00:31:38.470> what<00:31:38.890> to<00:31:39.279> and<00:31:39.490> not<00:31:39.610> do 00:31:39.810 --> 00:31:39.820 align:start position:0% thing we can learn is what to and not do 00:31:39.820 --> 00:31:43.860 align:start position:0% thing we can learn is what to and not do with<00:31:40.179> in<00:31:41.110> terms<00:31:41.350> of<00:31:41.500> governance<00:31:42.600> what<00:31:43.600> we<00:31:43.720> have 00:31:43.860 --> 00:31:43.870 align:start position:0% with in terms of governance what we have 00:31:43.870 --> 00:31:45.899 align:start position:0% with in terms of governance what we have right<00:31:44.020> now<00:31:44.080> with<00:31:44.380> anything<00:31:44.679> point<00:31:44.860> to<00:31:44.980> is<00:31:45.340> if 00:31:45.899 --> 00:31:45.909 align:start position:0% right now with anything point to is if 00:31:45.909 --> 00:31:50.220 align:start position:0% right now with anything point to is if they're<00:31:46.090> 2.0<00:31:46.890> is<00:31:47.890> the<00:31:48.880> research<00:31:49.870> team<00:31:50.080> I<00:31:50.169> think 00:31:50.220 --> 00:31:50.230 align:start position:0% they're 2.0 is the research team I think 00:31:50.230 --> 00:31:52.710 align:start position:0% they're 2.0 is the research team I think leads<00:31:50.559> a<00:31:50.679> lot<00:31:50.830> of<00:31:50.950> the<00:31:51.190> decisions<00:31:52.090> and<00:31:52.360> so 00:31:52.710 --> 00:31:52.720 align:start position:0% leads a lot of the decisions and so 00:31:52.720 --> 00:31:54.090 align:start position:0% leads a lot of the decisions and so there's<00:31:52.899> sort<00:31:53.049> of<00:31:53.140> a<00:31:53.230> central<00:31:53.529> shelling<00:31:53.860> point 00:31:54.090 --> 00:31:54.100 align:start position:0% there's sort of a central shelling point 00:31:54.100 --> 00:31:55.919 align:start position:0% there's sort of a central shelling point which<00:31:54.399> exists<00:31:55.059> much<00:31:55.210> less<00:31:55.450> than<00:31:55.630> a<00:31:55.690> theorem 00:31:55.919 --> 00:31:55.929 align:start position:0% which exists much less than a theorem 00:31:55.929 --> 00:31:58.409 align:start position:0% which exists much less than a theorem 1.0<00:31:56.409> and<00:31:56.620> the<00:31:57.340> idea<00:31:57.640> is<00:31:57.850> that<00:31:57.880> the<00:31:58.179> the 00:31:58.409 --> 00:31:58.419 align:start position:0% 1.0 and the idea is that the the 00:31:58.419 --> 00:31:59.909 align:start position:0% 1.0 and the idea is that the the research<00:31:58.659> team<00:31:58.899> wants<00:31:59.140> to<00:31:59.200> have<00:31:59.529> less<00:31:59.770> and 00:31:59.909 --> 00:31:59.919 align:start position:0% research team wants to have less and 00:31:59.919 --> 00:32:02.159 align:start position:0% research team wants to have less and less<00:32:00.010> of<00:32:00.159> this<00:32:00.309> role<00:32:00.520> but<00:32:01.510> how<00:32:01.659> can<00:32:01.720> we<00:32:01.929> do<00:32:02.049> this 00:32:02.159 --> 00:32:02.169 align:start position:0% less of this role but how can we do this 00:32:02.169 --> 00:32:04.830 align:start position:0% less of this role but how can we do this in<00:32:02.320> a<00:32:02.440> manner<00:32:03.159> that<00:32:03.279> prevents<00:32:04.210> deadlock<00:32:04.630> and 00:32:04.830 --> 00:32:04.840 align:start position:0% in a manner that prevents deadlock and 00:32:04.840 --> 00:32:07.620 align:start position:0% in a manner that prevents deadlock and allows<00:32:05.140> for<00:32:05.409> continuous<00:32:05.590> innovation<00:32:06.399> I<00:32:06.630> think 00:32:07.620 --> 00:32:07.630 align:start position:0% allows for continuous innovation I think 00:32:07.630 --> 00:32:09.060 align:start position:0% allows for continuous innovation I think a<00:32:07.690> lot<00:32:07.840> of<00:32:07.929> lessons<00:32:08.080> to<00:32:08.260> be<00:32:08.350> learned<00:32:08.559> from<00:32:08.679> F 00:32:09.060 --> 00:32:09.070 align:start position:0% a lot of lessons to be learned from F 00:32:09.070 --> 00:32:12.950 align:start position:0% a lot of lessons to be learned from F 1.0<00:32:09.549> that<00:32:10.950> I'd<00:32:11.950> be<00:32:12.159> willing<00:32:12.279> to<00:32:12.429> take<00:32:12.640> anything 00:32:12.950 --> 00:32:12.960 align:start position:0% 1.0 that I'd be willing to take anything 00:32:12.960 --> 00:32:15.750 align:start position:0% 1.0 that I'd be willing to take anything I'll<00:32:13.960> take<00:32:14.620> any<00:32:14.799> advice<00:32:15.100> from<00:32:15.159> any<00:32:15.490> of<00:32:15.640> the 00:32:15.750 --> 00:32:15.760 align:start position:0% I'll take any advice from any of the 00:32:15.760 --> 00:32:17.130 align:start position:0% I'll take any advice from any of the people<00:32:16.059> that<00:32:16.090> have<00:32:16.299> building<00:32:16.570> been<00:32:16.809> building 00:32:17.130 --> 00:32:17.140 align:start position:0% people that have building been building 00:32:17.140 --> 00:32:18.659 align:start position:0% people that have building been building as<00:32:17.260> one<00:32:17.440> or<00:32:17.649> Bach<00:32:17.799> chains<00:32:18.039> or<00:32:18.279> people<00:32:18.549> like 00:32:18.659 --> 00:32:18.669 align:start position:0% as one or Bach chains or people like 00:32:18.669 --> 00:32:21.210 align:start position:0% as one or Bach chains or people like anything<00:32:19.539> they've<00:32:19.659> got<00:32:19.840> bringing<00:32:20.500> here<00:32:20.679> came 00:32:21.210 --> 00:32:21.220 align:start position:0% anything they've got bringing here came 00:32:21.220 --> 00:32:25.260 align:start position:0% anything they've got bringing here came for<00:32:21.429> it<00:32:21.520> I<00:32:23.250> think<00:32:24.250> there's<00:32:24.610> a<00:32:24.730> lot<00:32:24.880> of<00:32:25.000> who<00:32:25.179> we 00:32:25.260 --> 00:32:25.270 align:start position:0% for it I think there's a lot of who we 00:32:25.270 --> 00:32:27.350 align:start position:0% for it I think there's a lot of who we can<00:32:25.419> learn<00:32:25.600> about<00:32:25.750> right<00:32:26.350> clans<00:32:26.620> how<00:32:27.159> to 00:32:27.350 --> 00:32:27.360 align:start position:0% can learn about right clans how to 00:32:27.360 --> 00:32:30.570 align:start position:0% can learn about right clans how to create<00:32:28.360> light<00:32:28.539> trance<00:32:28.809> from<00:32:28.990> it<00:32:29.200> one<00:32:29.409> and<00:32:29.710> on 00:32:30.570 --> 00:32:30.580 align:start position:0% create light trance from it one and on 00:32:30.580 --> 00:32:32.850 align:start position:0% create light trance from it one and on the<00:32:30.700> other<00:32:30.760> hand<00:32:31.200> ATM<00:32:32.200> one<00:32:32.350> will<00:32:32.529> greatly 00:32:32.850 --> 00:32:32.860 align:start position:0% the other hand ATM one will greatly 00:32:32.860 --> 00:32:35.580 align:start position:0% the other hand ATM one will greatly benefit<00:32:33.370> from<00:32:33.760> the<00:32:34.330> fact<00:32:34.600> that<00:32:34.690> the<00:32:35.200> e<00:32:35.230> to 00:32:35.580 --> 00:32:35.590 align:start position:0% benefit from the fact that the e to 00:32:35.590 --> 00:32:37.889 align:start position:0% benefit from the fact that the e to chain<00:32:35.830> will<00:32:36.010> be<00:32:36.039> finalizing<00:32:36.669> it<00:32:37.120> one<00:32:37.570> as<00:32:37.720> well 00:32:37.889 --> 00:32:37.899 align:start position:0% chain will be finalizing it one as well 00:32:37.899 --> 00:32:40.380 align:start position:0% chain will be finalizing it one as well so<00:32:38.649> it<00:32:38.799> would<00:32:39.039> be<00:32:39.220> much<00:32:39.490> easier<00:32:39.520> to<00:32:39.909> create 00:32:40.380 --> 00:32:40.390 align:start position:0% so it would be much easier to create 00:32:40.390 --> 00:32:43.560 align:start position:0% so it would be much easier to create efficient<00:32:41.049> light<00:32:41.230> clans<00:32:41.529> for<00:32:41.770> it<00:32:41.919> one<00:32:42.130> but<00:32:42.789> the 00:32:43.560 --> 00:32:43.570 align:start position:0% efficient light clans for it one but the 00:32:43.570 --> 00:32:45.720 align:start position:0% efficient light clans for it one but the instant<00:32:43.840> evasion<00:32:44.260> schemes<00:32:44.620> the<00:32:45.370> dog 00:32:45.720 --> 00:32:45.730 align:start position:0% instant evasion schemes the dog 00:32:45.730 --> 00:32:48.779 align:start position:0% instant evasion schemes the dog balancing<00:32:45.970> of<00:32:46.570> the<00:32:46.809> requests<00:32:47.289> this<00:32:47.710> these<00:32:48.610> are 00:32:48.779 --> 00:32:48.789 align:start position:0% balancing of the requests this these are 00:32:48.789 --> 00:32:52.769 align:start position:0% balancing of the requests this these are areas<00:32:49.240> where<00:32:49.480> we<00:32:49.779> can<00:32:50.880> share<00:32:51.880> the<00:32:52.270> solutions 00:32:52.769 --> 00:32:52.779 align:start position:0% areas where we can share the solutions 00:32:52.779 --> 00:32:56.100 align:start position:0% areas where we can share the solutions and<00:32:53.730> and<00:32:54.730> on<00:32:54.850> that<00:32:55.029> grant<00:32:55.299> I'm<00:32:55.720> kind<00:32:56.049> of 00:32:56.100 --> 00:32:56.110 align:start position:0% and and on that grant I'm kind of 00:32:56.110 --> 00:32:59.130 align:start position:0% and and on that grant I'm kind of excited<00:32:56.830> about<00:32:57.520> the<00:32:57.669> possibility<00:32:58.240> of<00:32:58.270> each 00:32:59.130 --> 00:32:59.140 align:start position:0% excited about the possibility of each 00:32:59.140 --> 00:33:03.810 align:start position:0% excited about the possibility of each one<00:33:01.169> incorporating<00:33:02.169> the<00:33:02.529> p2p<00:33:02.830> support<00:33:03.340> in 00:33:03.810 --> 00:33:03.820 align:start position:0% one incorporating the p2p support in 00:33:03.820 --> 00:33:07.049 align:start position:0% one incorporating the p2p support in some<00:33:04.029> way<00:33:04.210> this<00:33:05.169> is<00:33:05.320> some<00:33:05.909> something<00:33:06.909> that's 00:33:07.049 --> 00:33:07.059 align:start position:0% some way this is some something that's 00:33:07.059 --> 00:33:12.580 align:start position:0% some way this is some something that's possible<00:33:07.480> in<00:33:07.570> the<00:33:07.659> future 00:33:12.580 --> 00:33:12.590 align:start position:0% 00:33:12.590 --> 00:33:16.880 align:start position:0% okay<00:33:13.590> probably<00:33:13.830> yeah<00:33:14.820> I'd<00:33:15.180> like<00:33:15.420> to<00:33:15.890> take 00:33:16.880 --> 00:33:16.890 align:start position:0% okay probably yeah I'd like to take 00:33:16.890 --> 00:33:21.190 align:start position:0% okay probably yeah I'd like to take advises<00:33:17.460> with<00:33:17.990> Network<00:33:18.990> reputation<00:33:19.740> systems 00:33:21.190 --> 00:33:21.200 align:start position:0% advises with Network reputation systems 00:33:21.200 --> 00:33:25.010 align:start position:0% advises with Network reputation systems connection<00:33:22.200> managers<00:33:22.770> and<00:33:23.360> sync<00:33:24.360> strategy 00:33:25.010 --> 00:33:25.020 align:start position:0% connection managers and sync strategy 00:33:25.020 --> 00:33:30.080 align:start position:0% connection managers and sync strategy and<00:33:27.140> optimized<00:33:28.140> incremental<00:33:29.070> storage<00:33:29.610> for 00:33:30.080 --> 00:33:30.090 align:start position:0% and optimized incremental storage for 00:33:30.090 --> 00:33:34.850 align:start position:0% and optimized incremental storage for this<00:33:30.960> state<00:33:31.260> yeah<00:33:31.830> that's<00:33:32.550> it<00:33:33.590> I'm<00:33:34.590> actually 00:33:34.850 --> 00:33:34.860 align:start position:0% this state yeah that's it I'm actually 00:33:34.860 --> 00:33:39.410 align:start position:0% this state yeah that's it I'm actually mostly<00:33:35.630> like<00:33:36.630> related<00:33:37.200> to<00:33:37.320> both<00:33:38.120> Israelis<00:33:39.120> who 00:33:39.410 --> 00:33:39.420 align:start position:0% mostly like related to both Israelis who 00:33:39.420 --> 00:33:42.500 align:start position:0% mostly like related to both Israelis who I'm<00:33:39.660> actually<00:33:39.870> both<00:33:40.430> curved<00:33:41.430> like<00:33:41.820> a<00:33:42.060> lot<00:33:42.480> of 00:33:42.500 --> 00:33:42.510 align:start position:0% I'm actually both curved like a lot of 00:33:42.510 --> 00:33:44.770 align:start position:0% I'm actually both curved like a lot of parts<00:33:42.960> of<00:33:43.110> pike<00:33:43.290> were<00:33:43.470> a<00:33:43.500> couple<00:33:43.680> really<00:33:43.980> issue 00:33:44.770 --> 00:33:44.780 align:start position:0% parts of pike were a couple really issue 00:33:44.780 --> 00:33:48.050 align:start position:0% parts of pike were a couple really issue like<00:33:45.780> the<00:33:46.140> thing<00:33:46.380> is<00:33:46.650> for<00:33:47.010> like<00:33:47.430> currently<00:33:47.970> if 00:33:48.050 --> 00:33:48.060 align:start position:0% like the thing is for like currently if 00:33:48.060 --> 00:33:50.510 align:start position:0% like the thing is for like currently if like<00:33:48.270> probably<00:33:49.140> all<00:33:49.350> of<00:33:49.500> you<00:33:49.680> know<00:33:49.890> the<00:33:50.130> unis 00:33:50.510 --> 00:33:50.520 align:start position:0% like probably all of you know the unis 00:33:50.520 --> 00:33:54.860 align:start position:0% like probably all of you know the unis when<00:33:50.790> we<00:33:50.970> have<00:33:51.180> a<00:33:53.210> breaking<00:33:54.210> change<00:33:54.240> that 00:33:54.860 --> 00:33:54.870 align:start position:0% when we have a breaking change that 00:33:54.870 --> 00:33:56.600 align:start position:0% when we have a breaking change that creates<00:33:55.500> a<00:33:55.590> lot<00:33:55.740> of<00:33:55.890> conflicts 00:33:56.600 --> 00:33:56.610 align:start position:0% creates a lot of conflicts 00:33:56.610 --> 00:34:00.590 align:start position:0% creates a lot of conflicts I<00:33:56.700> hope<00:33:57.000> we<00:33:57.210> can<00:33:57.450> try<00:33:58.320> to<00:33:58.850> avoid<00:33:59.850> the<00:34:00.420> same 00:34:00.590 --> 00:34:00.600 align:start position:0% I hope we can try to avoid the same 00:34:00.600 --> 00:34:02.890 align:start position:0% I hope we can try to avoid the same situation<00:34:01.320> I<00:34:01.470> mean<00:34:01.650> stew<00:34:01.950> by<00:34:02.220> designing<00:34:02.670> the 00:34:02.890 --> 00:34:02.900 align:start position:0% situation I mean stew by designing the 00:34:02.900 --> 00:34:05.870 align:start position:0% situation I mean stew by designing the execution<00:34:03.900> engine<00:34:04.320> biter<00:34:05.040> like<00:34:05.370> make<00:34:05.850> it 00:34:05.870 --> 00:34:05.880 align:start position:0% execution engine biter like make it 00:34:05.880 --> 00:34:08.270 align:start position:0% execution engine biter like make it forward<00:34:06.390> cut<00:34:06.810> Cabello<00:34:07.200> from<00:34:07.590> the<00:34:07.740> beginning<00:34:08.130> I 00:34:08.270 --> 00:34:08.280 align:start position:0% forward cut Cabello from the beginning I 00:34:08.280 --> 00:34:11.030 align:start position:0% forward cut Cabello from the beginning I think<00:34:09.270> that's<00:34:09.600> something<00:34:10.080> quite<00:34:10.500> important 00:34:11.030 --> 00:34:11.040 align:start position:0% think that's something quite important 00:34:11.040 --> 00:34:13.600 align:start position:0% think that's something quite important it's<00:34:11.340> also<00:34:11.550> really<00:34:11.940> important<00:34:12.480> to<00:34:12.720> consider 00:34:13.600 --> 00:34:13.610 align:start position:0% it's also really important to consider 00:34:13.610 --> 00:34:16.430 align:start position:0% it's also really important to consider future<00:34:14.610> changes<00:34:14.970> of<00:34:15.179> webassembly<00:34:15.929> because 00:34:16.430 --> 00:34:16.440 align:start position:0% future changes of webassembly because 00:34:16.440 --> 00:34:18.740 align:start position:0% future changes of webassembly because there<00:34:17.100> will<00:34:17.280> be<00:34:17.340> a<00:34:17.490> pwease<00:34:17.669> a<00:34:18.000> diversion<00:34:18.600> is 00:34:18.740 --> 00:34:18.750 align:start position:0% there will be a pwease a diversion is 00:34:18.750 --> 00:34:21.380 align:start position:0% there will be a pwease a diversion is that's<00:34:19.020> how<00:34:19.169> the<00:34:19.230> web<00:34:19.530> works<00:34:20.060> that<00:34:21.060> will<00:34:21.210> be 00:34:21.380 --> 00:34:21.390 align:start position:0% that's how the web works that will be 00:34:21.390 --> 00:34:23.750 align:start position:0% that's how the web works that will be how<00:34:21.630> webassembly<00:34:22.280> specification<00:34:23.280> works<00:34:23.490> so 00:34:23.750 --> 00:34:23.760 align:start position:0% how webassembly specification works so 00:34:23.760 --> 00:34:26.800 align:start position:0% how webassembly specification works so how<00:34:24.060> do<00:34:24.120> we<00:34:24.300> incorporate<00:34:25.290> those<00:34:25.590> new<00:34:26.100> features 00:34:26.800 --> 00:34:26.810 align:start position:0% how do we incorporate those new features 00:34:26.810 --> 00:34:31.940 align:start position:0% how do we incorporate those new features adopted<00:34:27.810> in<00:34:28.020> web<00:34:28.410> assembly<00:34:28.919> into<00:34:29.520> our<00:34:30.950> my 00:34:31.940 --> 00:34:31.950 align:start position:0% adopted in web assembly into our my 00:34:31.950 --> 00:34:34.430 align:start position:0% adopted in web assembly into our my person<00:34:32.280> reacts<00:34:32.550> a<00:34:32.669> fusion<00:34:33.000> engine<00:34:33.330> as<00:34:33.990> to<00:34:34.260> I 00:34:34.430 --> 00:34:34.440 align:start position:0% person reacts a fusion engine as to I 00:34:34.440 --> 00:34:37.820 align:start position:0% person reacts a fusion engine as to I think<00:34:34.560> that's<00:34:34.890> also<00:34:35.160> something<00:34:36.560> that's<00:34:37.560> quite 00:34:37.820 --> 00:34:37.830 align:start position:0% think that's also something that's quite 00:34:37.830 --> 00:34:40.760 align:start position:0% think that's also something that's quite important<00:34:38.340> to<00:34:38.370> consider<00:34:39.530> just<00:34:40.530> quickly 00:34:40.760 --> 00:34:40.770 align:start position:0% important to consider just quickly 00:34:40.770 --> 00:34:42.860 align:start position:0% important to consider just quickly before<00:34:41.130> Carl<00:34:41.400> wraps<00:34:41.700> this<00:34:41.850> up<00:34:42.060> I<00:34:42.300> just<00:34:42.690> wanted 00:34:42.860 --> 00:34:42.870 align:start position:0% before Carl wraps this up I just wanted 00:34:42.870 --> 00:34:44.810 align:start position:0% before Carl wraps this up I just wanted to<00:34:43.050> just<00:34:43.440> to<00:34:43.620> announce<00:34:43.919> that<00:34:44.040> we're<00:34:44.730> looking 00:34:44.810 --> 00:34:44.820 align:start position:0% to just to announce that we're looking 00:34:44.820 --> 00:34:46.790 align:start position:0% to just to announce that we're looking for<00:34:45.090> a<00:34:45.120> senior<00:34:45.419> US<00:34:45.600> developer<00:34:46.080> if<00:34:46.260> you<00:34:46.470> are 00:34:46.790 --> 00:34:46.800 align:start position:0% for a senior US developer if you are 00:34:46.800 --> 00:34:48.830 align:start position:0% for a senior US developer if you are rust<00:34:47.070> developer<00:34:47.580> and<00:34:47.820> you<00:34:48.179> wanna<00:34:48.330> work<00:34:48.540> enough 00:34:48.830 --> 00:34:48.840 align:start position:0% rust developer and you wanna work enough 00:34:48.840 --> 00:34:52.240 align:start position:0% rust developer and you wanna work enough to<00:34:49.050> come<00:34:49.560> talk<00:34:49.919> to<00:34:49.950> us<00:34:50.100> thank<00:34:50.580> you 00:34:52.240 --> 00:34:52.250 align:start position:0% to come talk to us thank you 00:34:52.250 --> 00:34:54.919 align:start position:0% to come talk to us thank you well<00:34:53.250> thanks<00:34:53.910> everyone<00:34:54.120> for<00:34:54.240> attending<00:34:54.480> that 00:34:54.919 --> 00:34:54.929 align:start position:0% well thanks everyone for attending that 00:34:54.929 --> 00:34:57.050 align:start position:0% well thanks everyone for attending that thank<00:34:55.290> you<00:34:55.320> to<00:34:55.440> all<00:34:56.100> of<00:34:56.460> the<00:34:56.550> clients 00:34:57.050 --> 00:34:57.060 align:start position:0% thank you to all of the clients 00:34:57.060 --> 00:35:00.140 align:start position:0% thank you to all of the clients represented<00:34:57.600> here<00:34:57.870> and<00:34:58.560> I'm<00:34:59.340> really<00:34:59.700> like 00:35:00.140 --> 00:35:00.150 align:start position:0% represented here and I'm really like 00:35:00.150 --> 00:35:02.210 align:start position:0% represented here and I'm really like excited<00:35:00.600> to<00:35:00.630> see<00:35:00.930> the<00:35:01.110> DVP<00:35:01.590> work<00:35:01.890> that's<00:35:02.100> gonna 00:35:02.210 --> 00:35:02.220 align:start position:0% excited to see the DVP work that's gonna 00:35:02.220 --> 00:35:04.250 align:start position:0% excited to see the DVP work that's gonna happen<00:35:02.400> these<00:35:03.000> these<00:35:03.150> incentivize<00:35:03.690> test<00:35:04.020> nets 00:35:04.250 --> 00:35:04.260 align:start position:0% happen these these incentivize test nets 00:35:04.260 --> 00:35:06.710 align:start position:0% happen these these incentivize test nets this<00:35:04.590> may<00:35:04.950> net<00:35:05.130> launch<00:35:05.400> which<00:35:05.700> is<00:35:05.730> like<00:35:06.150> this 00:35:06.710 --> 00:35:06.720 align:start position:0% this may net launch which is like this 00:35:06.720 --> 00:35:09.560 align:start position:0% this may net launch which is like this is<00:35:06.870> this<00:35:06.960> incredible<00:35:07.440> event<00:35:07.730> and<00:35:08.730> then<00:35:08.970> this 00:35:09.560 --> 00:35:09.570 align:start position:0% is this incredible event and then this 00:35:09.570 --> 00:35:11.030 align:start position:0% is this incredible event and then this time<00:35:09.780> next<00:35:09.990> year<00:35:10.140> I<00:35:10.230> look<00:35:10.590> forward<00:35:10.620> to<00:35:10.830> seeing 00:35:11.030 --> 00:35:11.040 align:start position:0% time next year I look forward to seeing 00:35:11.040 --> 00:35:12.710 align:start position:0% time next year I look forward to seeing all<00:35:11.370> of<00:35:11.430> you<00:35:11.550> back<00:35:11.880> here<00:35:12.090> on<00:35:12.120> stage<00:35:12.480> hopefully 00:35:12.710 --> 00:35:12.720 align:start position:0% all of you back here on stage hopefully 00:35:12.720 --> 00:35:14.300 align:start position:0% all of you back here on stage hopefully we<00:35:12.990> can<00:35:13.110> talk<00:35:13.230> about<00:35:13.380> these<00:35:13.950> experiences 00:35:14.300 --> 00:35:14.310 align:start position:0% we can talk about these experiences 00:35:14.310 --> 00:35:17.930 align:start position:0% we can talk about these experiences we've<00:35:14.670> had<00:35:14.700> all<00:35:15.420> in<00:35:15.660> good<00:35:15.810> light<00:35:16.130> and<00:35:17.130> yeah<00:35:17.760> I 00:35:17.930 --> 00:35:17.940 align:start position:0% we've had all in good light and yeah I 00:35:17.940 --> 00:35:18.920 align:start position:0% we've had all in good light and yeah I hope<00:35:18.060> there<00:35:18.270> are<00:35:18.330> things<00:35:18.480> very<00:35:18.630> exciting<00:35:18.870> to 00:35:18.920 --> 00:35:18.930 align:start position:0% hope there are things very exciting to 00:35:18.930 --> 00:35:19.760 align:start position:0% hope there are things very exciting to see<00:35:18.990> where<00:35:19.140> this<00:35:19.200> is<00:35:19.290> going 00:35:19.760 --> 00:35:19.770 align:start position:0% see where this is going 00:35:19.770 --> 00:35:21.140 align:start position:0% see where this is going thank<00:35:20.340> you 00:35:21.140 --> 00:35:21.150 align:start position:0% thank you 00:35:21.150 --> 00:35:31.830 align:start position:0% thank you [Applause] 00:35:31.830 --> 00:35:31.840 align:start position:0% 00:35:31.840 --> 00:35:33.900 align:start position:0% you