WEBVTT Kind: captions Language: en 00:00:04.680 --> 00:00:07.639 align:start position:0% welcome<00:00:05.580> to<00:00:05.759> the<00:00:05.910> 8th<00:00:06.180> to<00:00:06.480> Q&A<00:00:06.870> session 00:00:07.639 --> 00:00:07.649 align:start position:0% welcome to the 8th to Q&A session 00:00:07.649 --> 00:00:10.490 align:start position:0% welcome to the 8th to Q&A session and<00:00:07.740> what<00:00:08.519> we're<00:00:08.700> gonna<00:00:08.850> do<00:00:09.150> is<00:00:09.450> I'm<00:00:10.110> gonna<00:00:10.290> add 00:00:10.490 --> 00:00:10.500 align:start position:0% and what we're gonna do is I'm gonna add 00:00:10.500 --> 00:00:13.310 align:start position:0% and what we're gonna do is I'm gonna add some<00:00:10.530> very<00:00:11.070> very<00:00:11.430> basic<00:00:11.790> questions<00:00:12.170> just<00:00:13.170> to 00:00:13.310 --> 00:00:13.320 align:start position:0% some very very basic questions just to 00:00:13.320 --> 00:00:15.709 align:start position:0% some very very basic questions just to get<00:00:13.530> you<00:00:13.889> all<00:00:14.130> up<00:00:14.519> to<00:00:14.549> speed<00:00:14.759> and<00:00:15.150> then<00:00:15.599> I'm 00:00:15.709 --> 00:00:15.719 align:start position:0% get you all up to speed and then I'm 00:00:15.719 --> 00:00:19.480 align:start position:0% get you all up to speed and then I'm gonna<00:00:15.870> open<00:00:15.990> the<00:00:16.410> microphone<00:00:17.130> to<00:00:17.520> the<00:00:18.029> crowd 00:00:19.480 --> 00:00:19.490 align:start position:0% gonna open the microphone to the crowd 00:00:19.490 --> 00:00:24.380 align:start position:0% gonna open the microphone to the crowd just<00:00:20.490> a<00:00:20.910> few<00:00:21.300> things<00:00:21.509> I'd<00:00:21.899> so<00:00:22.800> like<00:00:23.730> the<00:00:23.970> whole 00:00:24.380 --> 00:00:24.390 align:start position:0% just a few things I'd so like the whole 00:00:24.390 --> 00:00:26.720 align:start position:0% just a few things I'd so like the whole thing<00:00:24.599> about<00:00:24.840> validator<00:00:25.470> rewards<00:00:26.189> and<00:00:26.399> so<00:00:26.520> on 00:00:26.720 --> 00:00:26.730 align:start position:0% thing about validator rewards and so on 00:00:26.730 --> 00:00:30.109 align:start position:0% thing about validator rewards and so on I<00:00:27.630> don't<00:00:28.380> know<00:00:28.559> if<00:00:28.800> you<00:00:29.040> want<00:00:29.279> to<00:00:29.399> like<00:00:29.849> dig 00:00:30.109 --> 00:00:30.119 align:start position:0% I don't know if you want to like dig 00:00:30.119 --> 00:00:32.659 align:start position:0% I don't know if you want to like dig into<00:00:30.360> it<00:00:30.630> otherwise<00:00:31.259> you<00:00:31.500> know<00:00:31.619> I<00:00:31.980> think<00:00:32.189> it's 00:00:32.659 --> 00:00:32.669 align:start position:0% into it otherwise you know I think it's 00:00:32.669 --> 00:00:34.370 align:start position:0% into it otherwise you know I think it's consensus<00:00:33.239> that<00:00:33.360> we<00:00:33.540> can<00:00:33.719> skip<00:00:33.989> those 00:00:34.370 --> 00:00:34.380 align:start position:0% consensus that we can skip those 00:00:34.380 --> 00:00:38.360 align:start position:0% consensus that we can skip those questions<00:00:34.890> make<00:00:35.489> sense<00:00:35.730> yeah<00:00:36.210> cool<00:00:37.129> all<00:00:38.129> right 00:00:38.360 --> 00:00:38.370 align:start position:0% questions make sense yeah cool all right 00:00:38.370 --> 00:00:44.329 align:start position:0% questions make sense yeah cool all right so<00:00:38.839> maybe<00:00:39.839> let's<00:00:40.440> start<00:00:40.949> with<00:00:41.250> Joe<00:00:43.309> can<00:00:44.309> you 00:00:44.329 --> 00:00:44.339 align:start position:0% so maybe let's start with Joe can you 00:00:44.339 --> 00:00:47.479 align:start position:0% so maybe let's start with Joe can you give<00:00:44.579> us<00:00:44.730> an<00:00:45.480> update<00:00:45.660> I<00:00:46.140> over<00:00:46.649> they<00:00:46.859> interrupt 00:00:47.479 --> 00:00:47.489 align:start position:0% give us an update I over they interrupt 00:00:47.489 --> 00:00:49.369 align:start position:0% give us an update I over they interrupt locking<00:00:48.120> and<00:00:48.359> what<00:00:48.510> you<00:00:48.629> achieve<00:00:48.960> and<00:00:49.199> what 00:00:49.369 --> 00:00:49.379 align:start position:0% locking and what you achieve and what 00:00:49.379 --> 00:00:54.439 align:start position:0% locking and what you achieve and what that<00:00:49.620> exactly<00:00:50.100> means<00:00:52.190> so<00:00:53.190> we<00:00:53.399> had<00:00:53.579> this 00:00:54.439 --> 00:00:54.449 align:start position:0% that exactly means so we had this 00:00:54.449 --> 00:00:58.099 align:start position:0% that exactly means so we had this lock-in<00:00:55.440> is<00:00:56.429> what<00:00:56.640> we<00:00:56.730> called<00:00:56.940> it<00:00:57.149> it's<00:00:57.929> kind 00:00:58.099 --> 00:00:58.109 align:start position:0% lock-in is what we called it it's kind 00:00:58.109 --> 00:01:01.130 align:start position:0% lock-in is what we called it it's kind of<00:00:58.140> a<00:00:58.230> workshop<00:00:58.469> for<00:00:59.190> a<00:00:59.219> week<00:00:59.460> out<00:00:59.730> in<00:01:00.140> Muskoka 00:01:01.130 --> 00:01:01.140 align:start position:0% of a workshop for a week out in Muskoka 00:01:01.140 --> 00:01:04.579 align:start position:0% of a workshop for a week out in Muskoka Canada<00:01:02.269> and<00:01:03.269> I<00:01:03.300> guess<00:01:03.960> we<00:01:04.080> got<00:01:04.199> somebody<00:01:04.379> from 00:01:04.579 --> 00:01:04.589 align:start position:0% Canada and I guess we got somebody from 00:01:04.589 --> 00:01:14.510 align:start position:0% Canada and I guess we got somebody from Muskoka<00:01:05.129> here<00:01:11.780> pretty<00:01:13.070> so<00:01:14.070> basically<00:01:14.370> the 00:01:14.510 --> 00:01:14.520 align:start position:0% Muskoka here pretty so basically the 00:01:14.520 --> 00:01:16.250 align:start position:0% Muskoka here pretty so basically the idea<00:01:14.550> was<00:01:14.940> that<00:01:14.970> we<00:01:15.120> like<00:01:15.300> basically<00:01:15.660> trap<00:01:16.050> all 00:01:16.250 --> 00:01:16.260 align:start position:0% idea was that we like basically trap all 00:01:16.260 --> 00:01:20.480 align:start position:0% idea was that we like basically trap all the<00:01:16.500> developers<00:01:17.070> in<00:01:17.970> this<00:01:18.180> place<00:01:18.450> and<00:01:19.490> make 00:01:20.480 --> 00:01:20.490 align:start position:0% the developers in this place and make 00:01:20.490 --> 00:01:23.960 align:start position:0% the developers in this place and make them<00:01:20.610> join<00:01:20.790> our<00:01:20.970> two<00:01:21.300> cult<00:01:21.990> and<00:01:22.200> then<00:01:22.970> we'll 00:01:23.960 --> 00:01:23.970 align:start position:0% them join our two cult and then we'll 00:01:23.970 --> 00:01:26.480 align:start position:0% them join our two cult and then we'll work<00:01:24.180> on<00:01:24.360> our<00:01:24.510> clients<00:01:24.990> together<00:01:25.190> and<00:01:26.190> reduce 00:01:26.480 --> 00:01:26.490 align:start position:0% work on our clients together and reduce 00:01:26.490 --> 00:01:30.290 align:start position:0% work on our clients together and reduce the<00:01:26.760> round-trip<00:01:27.600> time<00:01:27.920> for<00:01:29.300> communication 00:01:30.290 --> 00:01:30.300 align:start position:0% the round-trip time for communication 00:01:30.300 --> 00:01:32.720 align:start position:0% the round-trip time for communication for<00:01:30.660> everybody<00:01:31.140> on<00:01:31.380> getting<00:01:32.280> their<00:01:32.400> clients 00:01:32.720 --> 00:01:32.730 align:start position:0% for everybody on getting their clients 00:01:32.730 --> 00:01:34.700 align:start position:0% for everybody on getting their clients to<00:01:32.790> interrupt<00:01:33.120> Interop<00:01:33.870> is<00:01:34.110> essentially 00:01:34.700 --> 00:01:34.710 align:start position:0% to interrupt Interop is essentially 00:01:34.710 --> 00:01:39.560 align:start position:0% to interrupt Interop is essentially being<00:01:34.950> able<00:01:35.070> to<00:01:36.680> talk<00:01:37.680> over<00:01:37.980> live<00:01:38.280> p2p<00:01:38.700> to<00:01:39.420> the 00:01:39.560 --> 00:01:39.570 align:start position:0% being able to talk over live p2p to the 00:01:39.570 --> 00:01:42.020 align:start position:0% being able to talk over live p2p to the individual<00:01:39.990> clients<00:01:40.500> and<00:01:40.700> gossip<00:01:41.700> baptists 00:01:42.020 --> 00:01:42.030 align:start position:0% individual clients and gossip baptists 00:01:42.030 --> 00:01:45.850 align:start position:0% individual clients and gossip baptists stations<00:01:42.390> and<00:01:42.660> block<00:01:43.410> proposals<00:01:44.090> with 00:01:45.850 --> 00:01:45.860 align:start position:0% stations and block proposals with 00:01:45.860 --> 00:01:48.440 align:start position:0% stations and block proposals with validators<00:01:46.860> kind<00:01:47.070> of<00:01:47.130> like<00:01:47.310> shared<00:01:47.880> among<00:01:48.210> the 00:01:48.440 --> 00:01:48.450 align:start position:0% validators kind of like shared among the 00:01:48.450 --> 00:01:51.860 align:start position:0% validators kind of like shared among the individual<00:01:49.050> clients<00:01:49.760> everything<00:01:50.810> that<00:01:51.810> you 00:01:51.860 --> 00:01:51.870 align:start position:0% individual clients everything that you 00:01:51.870 --> 00:01:55.640 align:start position:0% individual clients everything that you need<00:01:52.050> without<00:01:52.410> sinking<00:01:52.680> and<00:01:53.040> so<00:01:54.200> we<00:01:55.200> were 00:01:55.640 --> 00:01:55.650 align:start position:0% need without sinking and so we were 00:01:55.650 --> 00:02:00.220 align:start position:0% need without sinking and so we were expecting<00:01:56.280> I<00:01:56.760> think<00:01:57.330> eight<00:01:57.990> clients<00:01:58.710> game 00:02:00.220 --> 00:02:00.230 align:start position:0% expecting I think eight clients game 00:02:00.230 --> 00:02:04.760 align:start position:0% expecting I think eight clients game seven<00:02:01.230> got<00:02:02.010> two<00:02:02.190> Interop<00:02:02.930> and<00:02:03.930> that<00:02:04.650> was 00:02:04.760 --> 00:02:04.770 align:start position:0% seven got two Interop and that was 00:02:04.770 --> 00:02:06.380 align:start position:0% seven got two Interop and that was really<00:02:05.010> exciting<00:02:05.220> I<00:02:05.430> think<00:02:05.700> we<00:02:05.850> thought<00:02:06.180> that 00:02:06.380 --> 00:02:06.390 align:start position:0% really exciting I think we thought that 00:02:06.390 --> 00:02:07.490 align:start position:0% really exciting I think we thought that there<00:02:06.510> were<00:02:06.600> probably<00:02:06.780> only<00:02:06.960> be<00:02:07.200> three<00:02:07.470> or 00:02:07.490 --> 00:02:07.500 align:start position:0% there were probably only be three or 00:02:07.500 --> 00:02:09.949 align:start position:0% there were probably only be three or four<00:02:07.800> that<00:02:08.489> would<00:02:08.610> achieve<00:02:09.239> interrupt<00:02:09.810> in 00:02:09.949 --> 00:02:09.959 align:start position:0% four that would achieve interrupt in 00:02:09.959 --> 00:02:13.209 align:start position:0% four that would achieve interrupt in that<00:02:10.080> time<00:02:10.289> which<00:02:10.950> means<00:02:11.129> that<00:02:11.459> all<00:02:12.420> the 00:02:13.209 --> 00:02:13.219 align:start position:0% that time which means that all the 00:02:13.219 --> 00:02:16.520 align:start position:0% that time which means that all the individual<00:02:14.219> clients<00:02:14.640> are<00:02:14.819> really<00:02:15.499> doing<00:02:16.499> a 00:02:16.520 --> 00:02:16.530 align:start position:0% individual clients are really doing a 00:02:16.530 --> 00:02:18.620 align:start position:0% individual clients are really doing a great<00:02:16.650> job<00:02:16.939> so 00:02:18.620 --> 00:02:18.630 align:start position:0% great job so 00:02:18.630 --> 00:02:22.510 align:start position:0% great job so um<00:02:18.810> I<00:02:19.410> think<00:02:19.560> that<00:02:19.770> that<00:02:20.150> gives<00:02:21.150> us<00:02:21.300> more 00:02:22.510 --> 00:02:22.520 align:start position:0% um I think that that gives us more 00:02:22.520 --> 00:02:27.260 align:start position:0% um I think that that gives us more higher<00:02:23.520> probability<00:02:24.120> that<00:02:24.390> will<00:02:24.770> make<00:02:26.270> some 00:02:27.260 --> 00:02:27.270 align:start position:0% higher probability that will make some 00:02:27.270 --> 00:02:31.850 align:start position:0% higher probability that will make some early<00:02:28.200> q1<00:02:28.800> don't<00:02:29.670> quote<00:02:29.880> that<00:02:30.180> but<00:02:30.510> but<00:02:31.350> there 00:02:31.850 --> 00:02:31.860 align:start position:0% early q1 don't quote that but but there 00:02:31.860 --> 00:02:33.620 align:start position:0% early q1 don't quote that but but there that's<00:02:32.190> kind<00:02:32.430> of<00:02:32.460> like<00:02:32.610> the<00:02:32.790> idea<00:02:33.210> right<00:02:33.600> now 00:02:33.620 --> 00:02:33.630 align:start position:0% that's kind of like the idea right now 00:02:33.630 --> 00:02:35.840 align:start position:0% that's kind of like the idea right now so<00:02:33.960> where<00:02:34.080> people<00:02:34.350> are<00:02:34.470> saying<00:02:34.700> when<00:02:35.700> they 00:02:35.840 --> 00:02:35.850 align:start position:0% so where people are saying when they 00:02:35.850 --> 00:02:38.570 align:start position:0% so where people are saying when they want<00:02:36.090> to<00:02:36.300> see<00:02:36.450> a<00:02:36.480> beacon<00:02:37.200> chained<00:02:37.440> up<00:02:37.680> and<00:02:38.250> so<00:02:38.550> I 00:02:38.570 --> 00:02:38.580 align:start position:0% want to see a beacon chained up and so I 00:02:38.580 --> 00:02:39.950 align:start position:0% want to see a beacon chained up and so I think<00:02:38.700> there's<00:02:39.030> a<00:02:39.180> higher<00:02:39.330> probability<00:02:39.540> of 00:02:39.950 --> 00:02:39.960 align:start position:0% think there's a higher probability of 00:02:39.960 --> 00:02:45.350 align:start position:0% think there's a higher probability of that<00:02:40.140> now<00:02:41.840> so<00:02:42.840> just<00:02:43.680> to<00:02:44.280> give<00:02:44.550> an<00:02:44.790> update<00:02:44.940> does 00:02:45.350 --> 00:02:45.360 align:start position:0% that now so just to give an update does 00:02:45.360 --> 00:02:48.620 align:start position:0% that now so just to give an update does everyone<00:02:45.960> know<00:02:46.200> what<00:02:46.230> if<00:02:47.100> two<00:02:47.580> is<00:02:48.000> formed<00:02:48.480> by 00:02:48.620 --> 00:02:48.630 align:start position:0% everyone know what if two is formed by 00:02:48.630 --> 00:02:51.740 align:start position:0% everyone know what if two is formed by how<00:02:49.350> many<00:02:49.590> clients<00:02:49.890> we<00:02:50.760> have<00:02:51.000> and<00:02:51.480> all<00:02:51.570> of<00:02:51.720> that 00:02:51.740 --> 00:02:51.750 align:start position:0% how many clients we have and all of that 00:02:51.750 --> 00:02:54.680 align:start position:0% how many clients we have and all of that I'm<00:02:52.350> asking<00:02:52.650> the<00:02:52.860> crowd<00:02:53.360> because<00:02:54.360> otherwise 00:02:54.680 --> 00:02:54.690 align:start position:0% I'm asking the crowd because otherwise 00:02:54.690 --> 00:02:56.990 align:start position:0% I'm asking the crowd because otherwise we<00:02:55.350> should<00:02:55.410> give<00:02:55.710> a<00:02:55.740> primer<00:02:56.040> okay<00:02:56.520> like 00:02:56.990 --> 00:02:57.000 align:start position:0% we should give a primer okay like 00:02:57.000 --> 00:03:01.940 align:start position:0% we should give a primer okay like apparently<00:02:57.510> everyone<00:02:57.990> knows<00:03:00.260> all<00:03:01.260> right<00:03:01.530> so 00:03:01.940 --> 00:03:01.950 align:start position:0% apparently everyone knows all right so 00:03:01.950 --> 00:03:05.360 align:start position:0% apparently everyone knows all right so um<00:03:02.630> so<00:03:03.630> I<00:03:03.930> I<00:03:04.020> don't<00:03:04.290> know<00:03:04.500> like<00:03:04.830> so<00:03:05.070> we<00:03:05.190> have<00:03:05.340> a 00:03:05.360 --> 00:03:05.370 align:start position:0% um so I I don't know like so we have a 00:03:05.370 --> 00:03:07.510 align:start position:0% um so I I don't know like so we have a couple<00:03:05.610> of<00:03:05.820> the<00:03:05.970> clients<00:03:06.300> here<00:03:06.510> we<00:03:06.690> have<00:03:06.840> meme 00:03:07.510 --> 00:03:07.520 align:start position:0% couple of the clients here we have meme 00:03:07.520 --> 00:03:12.680 align:start position:0% couple of the clients here we have meme Nimbus<00:03:08.520> we<00:03:08.850> have<00:03:09.980> lighthouse<00:03:10.980> we<00:03:11.580> I<00:03:11.850> I<00:03:12.180> just 00:03:12.680 --> 00:03:12.690 align:start position:0% Nimbus we have lighthouse we I I just 00:03:12.690 --> 00:03:18.830 align:start position:0% Nimbus we have lighthouse we I I just like<00:03:13.020> I<00:03:13.200> can't<00:03:16.790> these<00:03:17.790> two<00:03:18.180> specification 00:03:18.830 --> 00:03:18.840 align:start position:0% like I can't these two specification 00:03:18.840 --> 00:03:23.240 align:start position:0% like I can't these two specification team<00:03:19.320> we<00:03:20.220> have<00:03:20.550> a<00:03:20.910> lodestar<00:03:21.870> as<00:03:22.140> well<00:03:22.380> and<00:03:22.800> we 00:03:23.240 --> 00:03:23.250 align:start position:0% team we have a lodestar as well and we 00:03:23.250 --> 00:03:30.500 align:start position:0% team we have a lodestar as well and we have<00:03:23.870> anyone<00:03:24.870> else<00:03:25.020> oh<00:03:26.060> oh<00:03:27.110> sorry<00:03:28.400> yeah<00:03:29.510> JD 00:03:30.500 --> 00:03:30.510 align:start position:0% have anyone else oh oh sorry yeah JD 00:03:30.510 --> 00:03:35.680 align:start position:0% have anyone else oh oh sorry yeah JD okay 00:03:35.680 --> 00:03:35.690 align:start position:0% 00:03:35.690 --> 00:03:38.450 align:start position:0% quills<00:03:36.690> is<00:03:36.930> here<00:03:37.260> their<00:03:37.680> prototyping<00:03:38.310> phase 00:03:38.450 --> 00:03:38.460 align:start position:0% quills is here their prototyping phase 00:03:38.460 --> 00:03:44.510 align:start position:0% quills is here their prototyping phase one<00:03:38.700> and<00:03:38.820> two<00:03:41.930> all<00:03:42.930> right<00:03:43.110> which<00:03:43.770> of<00:03:44.220> the 00:03:44.510 --> 00:03:44.520 align:start position:0% one and two all right which of the 00:03:44.520 --> 00:03:51.780 align:start position:0% one and two all right which of the clients<00:03:44.850> is<00:03:44.940> the<00:03:45.090> one<00:03:45.270> that's<00:03:45.540> most<00:03:45.750> advanced 00:03:51.780 --> 00:03:51.790 align:start position:0% 00:03:51.790 --> 00:03:54.490 align:start position:0% lodestar<00:03:52.790> does<00:03:52.970> a<00:03:53.000> really<00:03:53.330> good<00:03:53.750> job<00:03:53.810> at<00:03:54.170> fuzzy 00:03:54.490 --> 00:03:54.500 align:start position:0% lodestar does a really good job at fuzzy 00:03:54.500 --> 00:03:58.450 align:start position:0% lodestar does a really good job at fuzzy tests<00:03:54.710> and<00:03:54.890> other<00:03:54.980> clients<00:03:56.110> we<00:03:57.110> blow<00:03:58.070> them<00:03:58.250> up 00:03:58.450 --> 00:03:58.460 align:start position:0% tests and other clients we blow them up 00:03:58.460 --> 00:04:01.750 align:start position:0% tests and other clients we blow them up like<00:03:59.500> yeah<00:04:00.500> lighthouse<00:04:01.340> thought<00:04:01.580> they 00:04:01.750 --> 00:04:01.760 align:start position:0% like yeah lighthouse thought they 00:04:01.760 --> 00:04:04.360 align:start position:0% like yeah lighthouse thought they weren't<00:04:01.940> gonna<00:04:02.270> you<00:04:02.750> know<00:04:02.870> panic<00:04:03.380> we<00:04:04.190> made 00:04:04.360 --> 00:04:04.370 align:start position:0% weren't gonna you know panic we made 00:04:04.370 --> 00:04:07.150 align:start position:0% weren't gonna you know panic we made them<00:04:04.520> panic<00:04:04.900> they<00:04:05.900> fixed<00:04:06.290> it<00:04:06.410> we<00:04:06.830> made<00:04:07.010> them 00:04:07.150 --> 00:04:07.160 align:start position:0% them panic they fixed it we made them 00:04:07.160 --> 00:04:09.910 align:start position:0% them panic they fixed it we made them panic<00:04:07.460> again<00:04:07.630> those<00:04:08.630> are<00:04:08.660> best<00:04:09.260> lying<00:04:09.530> a<00:04:09.710> full 00:04:09.910 --> 00:04:09.920 align:start position:0% panic again those are best lying a full 00:04:09.920 --> 00:04:10.420 align:start position:0% panic again those are best lying a full time 00:04:10.420 --> 00:04:10.430 align:start position:0% time 00:04:10.430 --> 00:04:15.040 align:start position:0% time oh<00:04:10.460> no<00:04:13.030> that's<00:04:14.030> what<00:04:14.210> we<00:04:14.240> got<00:04:14.540> best<00:04:14.840> in<00:04:14.990> the 00:04:15.040 --> 00:04:15.050 align:start position:0% oh no that's what we got best in the 00:04:15.050 --> 00:04:17.190 align:start position:0% oh no that's what we got best in the browser 00:04:17.190 --> 00:04:17.200 align:start position:0% browser 00:04:17.200 --> 00:04:20.290 align:start position:0% browser all<00:04:18.200> right<00:04:18.380> the<00:04:18.500> adieu<00:04:19.190> the<00:04:19.340> existing<00:04:19.880> clients 00:04:20.290 --> 00:04:20.300 align:start position:0% all right the adieu the existing clients 00:04:20.300 --> 00:04:22.740 align:start position:0% all right the adieu the existing clients here<00:04:20.959> wanna<00:04:21.230> give<00:04:21.470> a<00:04:21.500> really<00:04:22.100> quick<00:04:22.250> update 00:04:22.740 --> 00:04:22.750 align:start position:0% here wanna give a really quick update 00:04:22.750 --> 00:04:28.090 align:start position:0% here wanna give a really quick update maybe<00:04:23.750> we<00:04:24.020> start<00:04:24.350> with<00:04:26.410> okay<00:04:27.410> we<00:04:27.620> don't<00:04:27.740> start 00:04:28.090 --> 00:04:28.100 align:start position:0% maybe we start with okay we don't start 00:04:28.100 --> 00:04:33.460 align:start position:0% maybe we start with okay we don't start with<00:04:28.250> you<00:04:28.370> yes 00:04:33.460 --> 00:04:33.470 align:start position:0% 00:04:33.470 --> 00:04:37.200 align:start position:0% yeah<00:04:34.100> nimbus<00:04:34.960> first<00:04:35.960> of<00:04:36.080> all<00:04:36.140> yeah<00:04:36.350> thanks<00:04:36.680> to 00:04:37.200 --> 00:04:37.210 align:start position:0% yeah nimbus first of all yeah thanks to 00:04:37.210 --> 00:04:40.840 align:start position:0% yeah nimbus first of all yeah thanks to consensus<00:04:38.210> and<00:04:38.390> and<00:04:38.980> the<00:04:39.980> organizers<00:04:40.460> of<00:04:40.490> the 00:04:40.840 --> 00:04:40.850 align:start position:0% consensus and and the organizers of the 00:04:40.850 --> 00:04:42.850 align:start position:0% consensus and and the organizers of the entropic<00:04:41.480> was<00:04:41.810> really<00:04:42.080> really<00:04:42.320> really<00:04:42.620> good 00:04:42.850 --> 00:04:42.860 align:start position:0% entropic was really really really good 00:04:42.860 --> 00:04:46.300 align:start position:0% entropic was really really really good to<00:04:43.160> get<00:04:43.250> together<00:04:43.580> their<00:04:44.800> work<00:04:45.800> out<00:04:45.980> a<00:04:46.010> lot<00:04:46.220> of 00:04:46.300 --> 00:04:46.310 align:start position:0% to get together their work out a lot of 00:04:46.310 --> 00:04:48.340 align:start position:0% to get together their work out a lot of practical<00:04:47.030> little<00:04:47.450> details<00:04:47.840> that<00:04:47.990> have<00:04:48.200> to<00:04:48.320> be 00:04:48.340 --> 00:04:48.350 align:start position:0% practical little details that have to be 00:04:48.350 --> 00:04:50.740 align:start position:0% practical little details that have to be worked<00:04:48.470> out<00:04:48.830> when<00:04:49.040> you're<00:04:49.360> trying<00:04:50.360> to<00:04:50.480> make 00:04:50.740 --> 00:04:50.750 align:start position:0% worked out when you're trying to make 00:04:50.750 --> 00:04:52.600 align:start position:0% worked out when you're trying to make two<00:04:50.930> pieces<00:04:51.290> of<00:04:51.320> software<00:04:51.710> work<00:04:51.980> you'd<00:04:52.190> think 00:04:52.600 --> 00:04:52.610 align:start position:0% two pieces of software work you'd think 00:04:52.610 --> 00:04:54.070 align:start position:0% two pieces of software work you'd think that<00:04:52.850> it's<00:04:52.970> easy<00:04:53.240> like<00:04:53.450> their<00:04:53.660> suspect 00:04:54.070 --> 00:04:54.080 align:start position:0% that it's easy like their suspect 00:04:54.080 --> 00:04:56.080 align:start position:0% that it's easy like their suspect everybody<00:04:54.740> just<00:04:55.130> writes<00:04:55.340> the<00:04:55.520> code<00:04:55.700> and<00:04:55.970> then 00:04:56.080 --> 00:04:56.090 align:start position:0% everybody just writes the code and then 00:04:56.090 --> 00:04:59.560 align:start position:0% everybody just writes the code and then you<00:04:56.480> know<00:04:56.570> boots<00:04:56.900> it<00:04:57.050> up<00:04:57.170> and<00:04:57.320> it<00:04:57.380> works<00:04:58.570> and 00:04:59.560 --> 00:04:59.570 align:start position:0% you know boots it up and it works and 00:04:59.570 --> 00:05:02.590 align:start position:0% you know boots it up and it works and that's<00:04:59.660> obviously<00:05:00.080> not<00:05:00.260> the<00:05:00.290> way<00:05:00.500> it<00:05:00.560> works<00:05:01.600> we 00:05:02.590 --> 00:05:02.600 align:start position:0% that's obviously not the way it works we 00:05:02.600 --> 00:05:04.830 align:start position:0% that's obviously not the way it works we have<00:05:02.630> a<00:05:02.900> pretty<00:05:03.440> complex<00:05:03.800> product<00:05:04.250> coming<00:05:04.580> out 00:05:04.830 --> 00:05:04.840 align:start position:0% have a pretty complex product coming out 00:05:04.840 --> 00:05:08.470 align:start position:0% have a pretty complex product coming out and<00:05:05.860> they're<00:05:06.860> having<00:05:06.890> very<00:05:07.400> many<00:05:07.610> basic 00:05:08.470 --> 00:05:08.480 align:start position:0% and they're having very many basic 00:05:08.480 --> 00:05:10.390 align:start position:0% and they're having very many basic building<00:05:08.780> blocks<00:05:09.020> that<00:05:09.200> have<00:05:09.260> to<00:05:09.530> fall<00:05:10.220> into 00:05:10.390 --> 00:05:10.400 align:start position:0% building blocks that have to fall into 00:05:10.400 --> 00:05:13.030 align:start position:0% building blocks that have to fall into place<00:05:10.520> like<00:05:11.200> that's<00:05:12.200> the<00:05:12.350> networking<00:05:12.740> that's 00:05:13.030 --> 00:05:13.040 align:start position:0% place like that's the networking that's 00:05:13.040 --> 00:05:16.950 align:start position:0% place like that's the networking that's the<00:05:13.220> cryptography<00:05:14.000> that's<00:05:14.210> this<00:05:14.840> pack<00:05:15.080> itself 00:05:16.950 --> 00:05:16.960 align:start position:0% the cryptography that's this pack itself 00:05:16.960 --> 00:05:21.550 align:start position:0% the cryptography that's this pack itself and<00:05:17.960> I<00:05:18.170> think<00:05:19.180> really<00:05:20.180> valuable<00:05:20.540> was<00:05:20.870> finding 00:05:21.550 --> 00:05:21.560 align:start position:0% and I think really valuable was finding 00:05:21.560 --> 00:05:24.010 align:start position:0% and I think really valuable was finding out<00:05:21.680> and<00:05:21.890> using<00:05:22.220> each<00:05:22.360> other's<00:05:23.360> clients<00:05:23.870> as 00:05:24.010 --> 00:05:24.020 align:start position:0% out and using each other's clients as 00:05:24.020 --> 00:05:26.560 align:start position:0% out and using each other's clients as stress<00:05:24.380> tests<00:05:24.800> as<00:05:25.130> a<00:05:25.190> first<00:05:25.550> sort<00:05:25.910> of<00:05:26.000> fast 00:05:26.560 --> 00:05:26.570 align:start position:0% stress tests as a first sort of fast 00:05:26.570 --> 00:05:31.810 align:start position:0% stress tests as a first sort of fast testing<00:05:27.020> platform<00:05:29.620> so<00:05:30.620> that<00:05:30.650> we<00:05:30.920> could<00:05:31.130> feel 00:05:31.810 --> 00:05:31.820 align:start position:0% testing platform so that we could feel 00:05:31.820 --> 00:05:34.360 align:start position:0% testing platform so that we could feel out<00:05:32.060> where<00:05:32.780> the<00:05:33.530> other<00:05:33.650> clients<00:05:34.070> have<00:05:34.160> put 00:05:34.360 --> 00:05:34.370 align:start position:0% out where the other clients have put 00:05:34.370 --> 00:05:38.140 align:start position:0% out where the other clients have put their<00:05:34.640> effort<00:05:35.540> the<00:05:35.840> most<00:05:36.050> and<00:05:36.400> then<00:05:37.400> that's 00:05:38.140 --> 00:05:38.150 align:start position:0% their effort the most and then that's 00:05:38.150 --> 00:05:39.880 align:start position:0% their effort the most and then that's how<00:05:38.330> we<00:05:38.390> could<00:05:38.630> improve<00:05:38.960> our<00:05:39.230> own<00:05:39.380> client<00:05:39.770> to 00:05:39.880 --> 00:05:39.890 align:start position:0% how we could improve our own client to 00:05:39.890 --> 00:05:44.800 align:start position:0% how we could improve our own client to sort<00:05:40.070> of<00:05:40.160> match<00:05:40.340> that<00:05:40.370> level<00:05:42.970> so<00:05:43.970> I<00:05:44.450> think 00:05:44.800 --> 00:05:44.810 align:start position:0% sort of match that level so I think 00:05:44.810 --> 00:05:46.930 align:start position:0% sort of match that level so I think Interop<00:05:45.530> was<00:05:45.680> great<00:05:45.890> for<00:05:46.100> this<00:05:46.250> we<00:05:46.490> found<00:05:46.730> lots 00:05:46.930 --> 00:05:46.940 align:start position:0% Interop was great for this we found lots 00:05:46.940 --> 00:05:48.940 align:start position:0% Interop was great for this we found lots of<00:05:47.120> bugs<00:05:47.360> lots<00:05:47.600> of<00:05:47.780> issues<00:05:47.930> lots<00:05:48.410> of<00:05:48.560> places 00:05:48.940 --> 00:05:48.950 align:start position:0% of bugs lots of issues lots of places 00:05:48.950 --> 00:05:51.620 align:start position:0% of bugs lots of issues lots of places where 00:05:51.620 --> 00:05:51.630 align:start position:0% 00:05:51.630 --> 00:05:54.240 align:start position:0% the<00:05:52.630> thinking<00:05:53.140> was<00:05:53.320> not<00:05:53.470> consistent<00:05:53.890> between 00:05:54.240 --> 00:05:54.250 align:start position:0% the thinking was not consistent between 00:05:54.250 --> 00:05:57.900 align:start position:0% the thinking was not consistent between the<00:05:54.550> kinds<00:05:54.970> and<00:05:55.150> that<00:05:55.900> was<00:05:56.410> sorted<00:05:56.770> out<00:05:56.950> during 00:05:57.900 --> 00:05:57.910 align:start position:0% the kinds and that was sorted out during 00:05:57.910 --> 00:06:00.300 align:start position:0% the kinds and that was sorted out during that<00:05:58.060> intro<00:05:58.450> I<00:05:58.900> mean<00:05:59.560> there<00:05:59.710> was<00:05:59.830> a<00:05:59.860> lead-up<00:06:00.160> to 00:06:00.300 --> 00:06:00.310 align:start position:0% that intro I mean there was a lead-up to 00:06:00.310 --> 00:06:02.190 align:start position:0% that intro I mean there was a lead-up to the<00:06:00.700> interrupt<00:06:01.120> where<00:06:01.330> were<00:06:01.600> clients<00:06:02.080> were 00:06:02.190 --> 00:06:02.200 align:start position:0% the interrupt where were clients were 00:06:02.200 --> 00:06:05.790 align:start position:0% the interrupt where were clients were sort<00:06:02.440> of<00:06:02.500> pairing<00:06:02.860> off<00:06:03.010> and<00:06:03.220> trying<00:06:03.490> to<00:06:04.800> solve 00:06:05.790 --> 00:06:05.800 align:start position:0% sort of pairing off and trying to solve 00:06:05.800 --> 00:06:07.260 align:start position:0% sort of pairing off and trying to solve some<00:06:06.040> of<00:06:06.070> the<00:06:06.250> initial<00:06:06.610> things<00:06:06.640> to<00:06:07.000> make<00:06:07.120> it 00:06:07.260 --> 00:06:07.270 align:start position:0% some of the initial things to make it 00:06:07.270 --> 00:06:09.870 align:start position:0% some of the initial things to make it smooth<00:06:07.540> right<00:06:07.840> so<00:06:08.140> that's<00:06:08.950> that's<00:06:09.610> probably 00:06:09.870 --> 00:06:09.880 align:start position:0% smooth right so that's that's probably 00:06:09.880 --> 00:06:12.660 align:start position:0% smooth right so that's that's probably why<00:06:10.300> we<00:06:10.510> saw<00:06:10.720> so<00:06:10.930> many<00:06:11.050> successes<00:06:11.560> right<00:06:11.950> on 00:06:12.660 --> 00:06:12.670 align:start position:0% why we saw so many successes right on 00:06:12.670 --> 00:06:16.740 align:start position:0% why we saw so many successes right on the<00:06:12.790> spot<00:06:13.000> as<00:06:13.150> well<00:06:13.300> like<00:06:13.620> yeah<00:06:15.270> thank<00:06:16.270> you 00:06:16.740 --> 00:06:16.750 align:start position:0% the spot as well like yeah thank you 00:06:16.750 --> 00:06:21.870 align:start position:0% the spot as well like yeah thank you Artemis<00:06:19.060> so<00:06:19.480> after<00:06:20.380> Interop<00:06:20.770> we<00:06:21.040> ripped<00:06:21.700> out 00:06:21.870 --> 00:06:21.880 align:start position:0% Artemis so after Interop we ripped out 00:06:21.880 --> 00:06:25.260 align:start position:0% Artemis so after Interop we ripped out our<00:06:22.120> rust<00:06:22.960> implementation<00:06:23.710> of<00:06:23.830> lit<00:06:23.980> p2p<00:06:24.370> were 00:06:25.260 --> 00:06:25.270 align:start position:0% our rust implementation of lit p2p were 00:06:25.270 --> 00:06:28.080 align:start position:0% our rust implementation of lit p2p were the<00:06:25.690> Java<00:06:25.990> client<00:06:26.260> so<00:06:26.680> we<00:06:26.890> went<00:06:27.130> for<00:06:27.340> the<00:06:27.550> JVM 00:06:28.080 --> 00:06:28.090 align:start position:0% the Java client so we went for the JVM 00:06:28.090 --> 00:06:32.310 align:start position:0% the Java client so we went for the JVM lit<00:06:28.330> b2b<00:06:29.070> that<00:06:30.070> was<00:06:30.370> built<00:06:30.730> by<00:06:30.850> harmony<00:06:31.240> and<00:06:32.140> we 00:06:32.310 --> 00:06:32.320 align:start position:0% lit b2b that was built by harmony and we 00:06:32.320 --> 00:06:34.590 align:start position:0% lit b2b that was built by harmony and we put<00:06:32.740> that<00:06:32.860> in<00:06:33.100> and<00:06:34.000> now<00:06:34.210> we're<00:06:34.390> kind<00:06:34.510> of 00:06:34.590 --> 00:06:34.600 align:start position:0% put that in and now we're kind of 00:06:34.600 --> 00:06:40.910 align:start position:0% put that in and now we're kind of working<00:06:34.780> on<00:06:35.430> some<00:06:37.590> sync<00:06:38.590> issues<00:06:38.950> and<00:06:39.250> some 00:06:40.910 --> 00:06:40.920 align:start position:0% working on some sync issues and some 00:06:40.920 --> 00:06:43.380 align:start position:0% working on some sync issues and some implementation<00:06:41.920> issues<00:06:42.010> to<00:06:42.970> kind<00:06:43.210> of<00:06:43.240> get 00:06:43.380 --> 00:06:43.390 align:start position:0% implementation issues to kind of get 00:06:43.390 --> 00:06:46.560 align:start position:0% implementation issues to kind of get ready<00:06:43.570> we're<00:06:44.230> turning<00:06:44.590> our<00:06:45.340> team<00:06:46.150> over<00:06:46.540> to 00:06:46.560 --> 00:06:46.570 align:start position:0% ready we're turning our team over to 00:06:46.570 --> 00:06:50.570 align:start position:0% ready we're turning our team over to start<00:06:46.960> working<00:06:47.170> on<00:06:47.230> a<00:06:47.290> sharding<00:06:47.650> client<00:06:48.570> we're 00:06:50.570 --> 00:06:50.580 align:start position:0% start working on a sharding client we're 00:06:50.580 --> 00:06:52.830 align:start position:0% start working on a sharding client we're leaving<00:06:51.580> our<00:06:51.730> beacon<00:06:52.000> chain<00:06:52.180> client<00:06:52.570> with<00:06:52.690> the 00:06:52.830 --> 00:06:52.840 align:start position:0% leaving our beacon chain client with the 00:06:52.840 --> 00:06:54.330 align:start position:0% leaving our beacon chain client with the production<00:06:53.260> team<00:06:53.440> who's<00:06:53.890> going<00:06:53.920> to<00:06:54.130> kind<00:06:54.280> of 00:06:54.330 --> 00:06:54.340 align:start position:0% production team who's going to kind of 00:06:54.340 --> 00:06:57.450 align:start position:0% production team who's going to kind of like<00:06:54.520> get<00:06:55.150> the<00:06:55.770> more<00:06:56.770> hardened<00:06:57.220> for 00:06:57.450 --> 00:06:57.460 align:start position:0% like get the more hardened for 00:06:57.460 --> 00:07:02.070 align:start position:0% like get the more hardened for production<00:06:58.410> and<00:07:00.180> yeah<00:07:01.180> that's<00:07:01.510> kind<00:07:01.750> of<00:07:01.780> where 00:07:02.070 --> 00:07:02.080 align:start position:0% production and yeah that's kind of where 00:07:02.080 --> 00:07:05.370 align:start position:0% production and yeah that's kind of where we<00:07:02.200> are<00:07:03.090> we're<00:07:04.090> going<00:07:04.300> to<00:07:04.420> work<00:07:05.020> on<00:07:05.140> a<00:07:05.170> new 00:07:05.370 --> 00:07:05.380 align:start position:0% we are we're going to work on a new 00:07:05.380 --> 00:07:06.660 align:start position:0% we are we're going to work on a new sharding<00:07:05.710> client<00:07:06.070> that's<00:07:06.190> going<00:07:06.310> to<00:07:06.370> be<00:07:06.460> built 00:07:06.660 --> 00:07:06.670 align:start position:0% sharding client that's going to be built 00:07:06.670 --> 00:07:09.830 align:start position:0% sharding client that's going to be built in<00:07:06.790> Kotlin<00:07:07.410> just<00:07:08.410> super<00:07:08.740> set<00:07:08.920> of<00:07:08.950> Java<00:07:09.250> and 00:07:09.830 --> 00:07:09.840 align:start position:0% in Kotlin just super set of Java and 00:07:09.840 --> 00:07:16.010 align:start position:0% in Kotlin just super set of Java and also<00:07:10.840> compiled<00:07:11.380> to<00:07:11.500> machine<00:07:11.530> code<00:07:14.460> notes<00:07:15.460> sir 00:07:16.010 --> 00:07:16.020 align:start position:0% also compiled to machine code notes sir 00:07:16.020 --> 00:07:20.070 align:start position:0% also compiled to machine code notes sir yeah<00:07:17.310> Interop<00:07:18.330> we<00:07:19.330> started<00:07:19.630> we<00:07:19.750> kind<00:07:19.900> of<00:07:19.960> broke 00:07:20.070 --> 00:07:20.080 align:start position:0% yeah Interop we started we kind of broke 00:07:20.080 --> 00:07:23.610 align:start position:0% yeah Interop we started we kind of broke into<00:07:20.350> several<00:07:20.530> different<00:07:21.450> sub<00:07:22.450> teams<00:07:22.690> we're 00:07:23.610 --> 00:07:23.620 align:start position:0% into several different sub teams we're 00:07:23.620 --> 00:07:26.340 align:start position:0% into several different sub teams we're working<00:07:24.100> on<00:07:24.280> getting<00:07:24.640> lodestar<00:07:25.510> kind<00:07:26.290> of 00:07:26.340 --> 00:07:26.350 align:start position:0% working on getting lodestar kind of 00:07:26.350 --> 00:07:28.530 align:start position:0% working on getting lodestar kind of productionize<00:07:27.240> we<00:07:28.240> have<00:07:28.360> a<00:07:28.390> lot<00:07:28.510> of 00:07:28.530 --> 00:07:28.540 align:start position:0% productionize we have a lot of 00:07:28.540 --> 00:07:30.750 align:start position:0% productionize we have a lot of optimization<00:07:29.200> to<00:07:29.320> do<00:07:29.440> to<00:07:29.710> really<00:07:29.980> get<00:07:30.580> to<00:07:30.670> like 00:07:30.750 --> 00:07:30.760 align:start position:0% optimization to do to really get to like 00:07:30.760 --> 00:07:33.420 align:start position:0% optimization to do to really get to like this<00:07:30.940> production<00:07:31.860> level<00:07:32.860> that<00:07:33.070> Danny<00:07:33.280> was 00:07:33.420 --> 00:07:33.430 align:start position:0% this production level that Danny was 00:07:33.430 --> 00:07:38.100 align:start position:0% this production level that Danny was talking<00:07:33.460> about<00:07:34.530> and<00:07:35.700> we<00:07:36.700> also<00:07:36.970> were<00:07:37.750> kind<00:07:38.080> of 00:07:38.100 --> 00:07:38.110 align:start position:0% talking about and we also were kind of 00:07:38.110 --> 00:07:41.870 align:start position:0% talking about and we also were kind of looking<00:07:38.230> ahead<00:07:38.440> at<00:07:39.310> a<00:07:39.850> light<00:07:40.330> client<00:07:40.780> work<00:07:41.200> so 00:07:41.870 --> 00:07:41.880 align:start position:0% looking ahead at a light client work so 00:07:41.880 --> 00:07:46.260 align:start position:0% looking ahead at a light client work so we<00:07:42.880> start<00:07:43.150> we've<00:07:43.360> started<00:07:43.630> to<00:07:44.430> prototype<00:07:45.430> some 00:07:46.260 --> 00:07:46.270 align:start position:0% we start we've started to prototype some 00:07:46.270 --> 00:07:51.120 align:start position:0% we start we've started to prototype some of<00:07:46.420> that<00:07:46.570> work<00:07:47.110> out<00:07:47.590> and<00:07:48.990> we're<00:07:50.130> hopefully 00:07:51.120 --> 00:07:51.130 align:start position:0% of that work out and we're hopefully 00:07:51.130 --> 00:07:52.320 align:start position:0% of that work out and we're hopefully going<00:07:51.250> to<00:07:51.370> start<00:07:51.550> contributing<00:07:51.790> back<00:07:52.090> to<00:07:52.150> the 00:07:52.320 --> 00:07:52.330 align:start position:0% going to start contributing back to the 00:07:52.330 --> 00:07:56.010 align:start position:0% going to start contributing back to the spec<00:07:52.630> a<00:07:52.660> little<00:07:52.960> bit 00:07:56.010 --> 00:07:56.020 align:start position:0% 00:07:56.020 --> 00:08:00.129 align:start position:0% thank<00:07:57.020> you<00:07:57.110> that<00:07:57.589> house<00:07:58.270> we're<00:07:59.270> going<00:07:59.449> well<00:07:59.599> I 00:08:00.129 --> 00:08:00.139 align:start position:0% thank you that house we're going well I 00:08:00.139 --> 00:08:02.079 align:start position:0% thank you that house we're going well I mean<00:08:00.919> focus<00:08:01.249> at<00:08:01.339> the<00:08:01.399> moment<00:08:01.429> is<00:08:01.789> to<00:08:01.909> target 00:08:02.079 --> 00:08:02.089 align:start position:0% mean focus at the moment is to target 00:08:02.089 --> 00:08:04.059 align:start position:0% mean focus at the moment is to target feature<00:08:02.419> completeness<00:08:02.839> so<00:08:03.589> phase<00:08:03.830> zero 00:08:04.059 --> 00:08:04.069 align:start position:0% feature completeness so phase zero 00:08:04.069 --> 00:08:05.919 align:start position:0% feature completeness so phase zero feature<00:08:04.279> completeness<00:08:04.729> we're<00:08:05.599> getting<00:08:05.779> quite 00:08:05.919 --> 00:08:05.929 align:start position:0% feature completeness we're getting quite 00:08:05.929 --> 00:08:08.019 align:start position:0% feature completeness we're getting quite close<00:08:06.080> we're<00:08:06.589> just<00:08:06.800> sort<00:08:07.459> of<00:08:07.489> polishing<00:08:07.879> off 00:08:08.019 --> 00:08:08.029 align:start position:0% close we're just sort of polishing off 00:08:08.029 --> 00:08:09.969 align:start position:0% close we're just sort of polishing off the<00:08:08.269> integration<00:08:08.869> to<00:08:09.019> f12<00:08:09.379> the<00:08:09.619> deposit 00:08:09.969 --> 00:08:09.979 align:start position:0% the integration to f12 the deposit 00:08:09.979 --> 00:08:12.600 align:start position:0% the integration to f12 the deposit contract<00:08:10.399> we're<00:08:11.389> also<00:08:11.509> working<00:08:11.809> on<00:08:12.110> some 00:08:12.600 --> 00:08:12.610 align:start position:0% contract we're also working on some 00:08:12.610 --> 00:08:15.639 align:start position:0% contract we're also working on some slashing<00:08:13.610> protection<00:08:14.059> for<00:08:14.269> validators<00:08:14.779> so 00:08:15.639 --> 00:08:15.649 align:start position:0% slashing protection for validators so 00:08:15.649 --> 00:08:17.979 align:start position:0% slashing protection for validators so this<00:08:15.800> is<00:08:15.919> kind<00:08:16.459> of<00:08:16.580> the<00:08:17.509> idea<00:08:17.689> of<00:08:17.839> feature 00:08:17.979 --> 00:08:17.989 align:start position:0% this is kind of the idea of feature 00:08:17.989 --> 00:08:20.739 align:start position:0% this is kind of the idea of feature complete<00:08:18.289> being<00:08:18.699> that<00:08:19.699> we<00:08:20.269> can<00:08:20.419> run<00:08:20.569> the 00:08:20.739 --> 00:08:20.749 align:start position:0% complete being that we can run the 00:08:20.749 --> 00:08:23.229 align:start position:0% complete being that we can run the protocol<00:08:21.169> we<00:08:21.589> can<00:08:22.099> we<00:08:22.610> have<00:08:22.729> everything<00:08:22.999> we 00:08:23.229 --> 00:08:23.239 align:start position:0% protocol we can we have everything we 00:08:23.239 --> 00:08:24.820 align:start position:0% protocol we can we have everything we need<00:08:23.389> to<00:08:23.779> run<00:08:23.959> and<00:08:24.169> we<00:08:24.229> can<00:08:24.379> run<00:08:24.529> off<00:08:24.709> the 00:08:24.820 --> 00:08:24.830 align:start position:0% need to run and we can run off the 00:08:24.830 --> 00:08:27.339 align:start position:0% need to run and we can run off the deposit<00:08:25.189> contract<00:08:25.369> but<00:08:26.149> not<00:08:26.300> necessarily<00:08:26.869> can 00:08:27.339 --> 00:08:27.349 align:start position:0% deposit contract but not necessarily can 00:08:27.349 --> 00:08:29.919 align:start position:0% deposit contract but not necessarily can we<00:08:27.469> run<00:08:27.709> to<00:08:28.189> say<00:08:28.339> a<00:08:28.580> year<00:08:28.819> and<00:08:29.149> use<00:08:29.360> reasonable 00:08:29.919 --> 00:08:29.929 align:start position:0% we run to say a year and use reasonable 00:08:29.929 --> 00:08:32.170 align:start position:0% we run to say a year and use reasonable disk<00:08:30.169> usage<00:08:30.439> so<00:08:31.399> that's<00:08:31.550> something<00:08:31.729> we're 00:08:32.170 --> 00:08:32.180 align:start position:0% disk usage so that's something we're 00:08:32.180 --> 00:08:34.329 align:start position:0% disk usage so that's something we're working<00:08:32.209> on<00:08:32.569> now<00:08:32.750> is<00:08:32.959> trying<00:08:33.949> to<00:08:34.009> figure<00:08:34.159> out 00:08:34.329 --> 00:08:34.339 align:start position:0% working on now is trying to figure out 00:08:34.339 --> 00:08:36.159 align:start position:0% working on now is trying to figure out how<00:08:34.490> to<00:08:34.550> optimize<00:08:34.729> that<00:08:35.180> database<00:08:35.509> storage<00:08:35.990> so 00:08:36.159 --> 00:08:36.169 align:start position:0% how to optimize that database storage so 00:08:36.169 --> 00:08:39.149 align:start position:0% how to optimize that database storage so that<00:08:36.199> so<00:08:36.529> that<00:08:36.560> we<00:08:36.740> can<00:08:36.860> run<00:08:37.009> for<00:08:37.250> a<00:08:37.310> long<00:08:37.459> time 00:08:39.149 --> 00:08:39.159 align:start position:0% that so that we can run for a long time 00:08:39.159 --> 00:08:41.889 align:start position:0% that so that we can run for a long time yeah<00:08:40.159> so<00:08:40.399> I<00:08:40.430> think<00:08:40.519> the<00:08:40.819> next<00:08:41.209> thing<00:08:41.360> for<00:08:41.449> us<00:08:41.659> is 00:08:41.889 --> 00:08:41.899 align:start position:0% yeah so I think the next thing for us is 00:08:41.899 --> 00:08:44.920 align:start position:0% yeah so I think the next thing for us is we<00:08:42.139> really<00:08:42.349> need<00:08:42.469> to<00:08:42.589> start<00:08:43.120> testing<00:08:44.120> more 00:08:44.920 --> 00:08:44.930 align:start position:0% we really need to start testing more 00:08:44.930 --> 00:08:46.900 align:start position:0% we really need to start testing more public<00:08:45.410> test<00:08:45.800> nets<00:08:46.009> we<00:08:46.220> need<00:08:46.339> to<00:08:46.459> get<00:08:46.610> one<00:08:46.759> of 00:08:46.900 --> 00:08:46.910 align:start position:0% public test nets we need to get one of 00:08:46.910 --> 00:08:49.059 align:start position:0% public test nets we need to get one of our<00:08:46.970> own<00:08:47.149> public<00:08:47.300> test<00:08:47.660> nuts<00:08:47.839> up<00:08:48.050> and<00:08:48.829> we<00:08:48.920> also 00:08:49.059 --> 00:08:49.069 align:start position:0% our own public test nuts up and we also 00:08:49.069 --> 00:08:51.400 align:start position:0% our own public test nuts up and we also need<00:08:49.370> to<00:08:49.490> start<00:08:49.730> doing<00:08:49.880> test<00:08:50.779> nets<00:08:50.990> with<00:08:51.199> other 00:08:51.400 --> 00:08:51.410 align:start position:0% need to start doing test nets with other 00:08:51.410 --> 00:08:54.280 align:start position:0% need to start doing test nets with other clients<00:08:51.920> using<00:08:52.430> the<00:08:52.880> f1<00:08:53.269> chain<00:08:53.600> as<00:08:53.870> the<00:08:54.050> source 00:08:54.280 --> 00:08:54.290 align:start position:0% clients using the f1 chain as the source 00:08:54.290 --> 00:08:56.980 align:start position:0% clients using the f1 chain as the source of<00:08:54.500> deposits<00:08:55.310> so<00:08:55.970> we<00:08:56.060> can<00:08:56.240> test<00:08:56.449> this<00:08:56.720> like 00:08:56.980 --> 00:08:56.990 align:start position:0% of deposits so we can test this like 00:08:56.990 --> 00:08:59.230 align:start position:0% of deposits so we can test this like dynamic<00:08:57.579> validator<00:08:58.579> set<00:08:58.819> because<00:08:59.000> this<00:08:59.089> is 00:08:59.230 --> 00:08:59.240 align:start position:0% dynamic validator set because this is 00:08:59.240 --> 00:09:01.530 align:start position:0% dynamic validator set because this is the<00:08:59.329> thing<00:08:59.480> that<00:08:59.600> we<00:08:59.660> didn't<00:08:59.899> test<00:09:00.079> at<00:09:00.319> Interop 00:09:01.530 --> 00:09:01.540 align:start position:0% the thing that we didn't test at Interop 00:09:01.540 --> 00:09:03.639 align:start position:0% the thing that we didn't test at Interop yeah<00:09:02.540> that's<00:09:02.779> that's<00:09:02.959> awesome<00:09:03.170> we're<00:09:03.500> we're 00:09:03.639 --> 00:09:03.649 align:start position:0% yeah that's that's awesome we're we're 00:09:03.649 --> 00:09:05.910 align:start position:0% yeah that's that's awesome we're we're also<00:09:03.769> really<00:09:04.040> trying<00:09:04.370> to<00:09:04.579> help<00:09:05.240> foster<00:09:05.449> the 00:09:05.910 --> 00:09:05.920 align:start position:0% also really trying to help foster the 00:09:05.920 --> 00:09:08.980 align:start position:0% also really trying to help foster the cool<00:09:06.920> team<00:09:07.130> to<00:09:07.490> to<00:09:08.269> make<00:09:08.389> sure<00:09:08.509> that<00:09:08.689> they<00:09:08.810> can 00:09:08.980 --> 00:09:08.990 align:start position:0% cool team to to make sure that they can 00:09:08.990 --> 00:09:11.939 align:start position:0% cool team to to make sure that they can keep<00:09:09.110> researching<00:09:09.439> the<00:09:10.130> the<00:09:10.850> next<00:09:11.240> phases 00:09:11.939 --> 00:09:11.949 align:start position:0% keep researching the the next phases 00:09:11.949 --> 00:09:16.990 align:start position:0% keep researching the the next phases whilst<00:09:12.949> still<00:09:13.430> delivering<00:09:13.790> phase<00:09:14.029> zero<00:09:16.000> yeah 00:09:16.990 --> 00:09:17.000 align:start position:0% whilst still delivering phase zero yeah 00:09:17.000 --> 00:09:20.110 align:start position:0% whilst still delivering phase zero yeah so<00:09:17.470> Trudy<00:09:18.470> was<00:09:18.589> a<00:09:18.620> Interop<00:09:19.009> we<00:09:19.670> had<00:09:19.819> a<00:09:19.850> lot<00:09:20.000> of 00:09:20.110 --> 00:09:20.120 align:start position:0% so Trudy was a Interop we had a lot of 00:09:20.120 --> 00:09:22.660 align:start position:0% so Trudy was a Interop we had a lot of fun<00:09:20.329> working<00:09:20.509> with<00:09:20.779> everyone<00:09:21.490> since<00:09:22.490> then 00:09:22.660 --> 00:09:22.670 align:start position:0% fun working with everyone since then 00:09:22.670 --> 00:09:24.309 align:start position:0% fun working with everyone since then we've<00:09:22.910> been<00:09:22.939> just<00:09:23.449> sort<00:09:23.600> of<00:09:23.630> merging<00:09:23.899> in<00:09:24.110> all 00:09:24.309 --> 00:09:24.319 align:start position:0% we've been just sort of merging in all 00:09:24.319 --> 00:09:26.230 align:start position:0% we've been just sort of merging in all the<00:09:24.439> things<00:09:24.620> we<00:09:24.769> found<00:09:24.949> there<00:09:25.250> nothing<00:09:26.060> major 00:09:26.230 --> 00:09:26.240 align:start position:0% the things we found there nothing major 00:09:26.240 --> 00:09:27.819 align:start position:0% the things we found there nothing major but<00:09:26.630> just<00:09:26.810> a<00:09:26.899> lot<00:09:27.019> of<00:09:27.050> like<00:09:27.290> tiny<00:09:27.649> little 00:09:27.819 --> 00:09:27.829 align:start position:0% but just a lot of like tiny little 00:09:27.829 --> 00:09:29.999 align:start position:0% but just a lot of like tiny little things<00:09:28.160> as<00:09:28.550> I'm<00:09:28.819> sure<00:09:28.970> other<00:09:29.120> people<00:09:29.180> found 00:09:29.999 --> 00:09:30.009 align:start position:0% things as I'm sure other people found 00:09:30.009 --> 00:09:32.410 align:start position:0% things as I'm sure other people found the<00:09:31.009> big<00:09:31.250> thing<00:09:31.430> arrest<00:09:31.610> will<00:09:31.699> be<00:09:31.730> performance 00:09:32.410 --> 00:09:32.420 align:start position:0% the big thing arrest will be performance 00:09:32.420 --> 00:09:34.480 align:start position:0% the big thing arrest will be performance so<00:09:32.810> Trinity<00:09:33.259> is<00:09:33.350> a<00:09:33.380> client<00:09:33.800> written<00:09:33.889> in<00:09:34.100> Python 00:09:34.480 --> 00:09:34.490 align:start position:0% so Trinity is a client written in Python 00:09:34.490 --> 00:09:37.660 align:start position:0% so Trinity is a client written in Python so<00:09:35.230> well<00:09:36.230> it's<00:09:36.560> great<00:09:37.069> in<00:09:37.250> terms<00:09:37.370> of<00:09:37.519> being 00:09:37.660 --> 00:09:37.670 align:start position:0% so well it's great in terms of being 00:09:37.670 --> 00:09:38.889 align:start position:0% so well it's great in terms of being readable<00:09:38.000> and<00:09:38.149> very<00:09:38.329> approachable<00:09:38.569> and 00:09:38.889 --> 00:09:38.899 align:start position:0% readable and very approachable and 00:09:38.899 --> 00:09:41.079 align:start position:0% readable and very approachable and accessible<00:09:39.130> we<00:09:40.130> definitely<00:09:40.459> have<00:09:40.550> to<00:09:40.579> deal 00:09:41.079 --> 00:09:41.089 align:start position:0% accessible we definitely have to deal 00:09:41.089 --> 00:09:42.670 align:start position:0% accessible we definitely have to deal with<00:09:41.149> sort<00:09:41.480> of<00:09:41.509> this<00:09:41.630> performance<00:09:42.019> penalty<00:09:42.410> we 00:09:42.670 --> 00:09:42.680 align:start position:0% with sort of this performance penalty we 00:09:42.680 --> 00:09:45.759 align:start position:0% with sort of this performance penalty we accept<00:09:43.579> by<00:09:43.790> choice<00:09:44.199> so<00:09:45.199> that'll<00:09:45.410> be<00:09:45.500> a<00:09:45.529> lot<00:09:45.649> of 00:09:45.759 --> 00:09:45.769 align:start position:0% accept by choice so that'll be a lot of 00:09:45.769 --> 00:09:47.230 align:start position:0% accept by choice so that'll be a lot of our<00:09:45.889> work<00:09:45.980> moving<00:09:46.459> forward<00:09:46.880> for<00:09:47.000> the<00:09:47.089> next 00:09:47.230 --> 00:09:47.240 align:start position:0% our work moving forward for the next 00:09:47.240 --> 00:09:49.540 align:start position:0% our work moving forward for the next couple<00:09:47.329> months<00:09:47.449> is<00:09:47.899> making<00:09:48.529> really<00:09:49.279> fast 00:09:49.540 --> 00:09:49.550 align:start position:0% couple months is making really fast 00:09:49.550 --> 00:09:54.670 align:start position:0% couple months is making really fast interpreter<00:09:50.120> code<00:09:51.189> well<00:09:52.189> thank<00:09:52.519> you<00:09:52.699> I<00:09:53.680> am 00:09:54.670 --> 00:09:54.680 align:start position:0% interpreter code well thank you I am 00:09:54.680 --> 00:09:57.639 align:start position:0% interpreter code well thank you I am losing<00:09:55.339> my<00:09:55.519> voice<00:09:55.730> so<00:09:56.149> excuse<00:09:56.839> me 00:09:57.639 --> 00:09:57.649 align:start position:0% losing my voice so excuse me 00:09:57.649 --> 00:10:01.540 align:start position:0% losing my voice so excuse me so<00:09:58.300> the<00:09:59.300> quilt<00:09:59.509> team<00:09:59.689> has<00:10:00.199> been<00:10:00.560> focused<00:10:01.430> on 00:10:01.540 --> 00:10:01.550 align:start position:0% so the quilt team has been focused on 00:10:01.550 --> 00:10:04.720 align:start position:0% so the quilt team has been focused on doing<00:10:01.939> research<00:10:02.240> around<00:10:02.389> phase<00:10:02.720> two<00:10:03.730> building 00:10:04.720 --> 00:10:04.730 align:start position:0% doing research around phase two building 00:10:04.730 --> 00:10:08.889 align:start position:0% doing research around phase two building on<00:10:05.170> execution<00:10:06.170> environments<00:10:07.240> and<00:10:08.240> doing<00:10:08.600> some 00:10:08.889 --> 00:10:08.899 align:start position:0% on execution environments and doing some 00:10:08.899 --> 00:10:12.579 align:start position:0% on execution environments and doing some early<00:10:09.259> prototypes<00:10:09.769> on<00:10:11.500> basically<00:10:12.500> the 00:10:12.579 --> 00:10:12.589 align:start position:0% early prototypes on basically the 00:10:12.589 --> 00:10:15.819 align:start position:0% early prototypes on basically the stateless<00:10:12.949> paradigm<00:10:13.399> so<00:10:13.870> we<00:10:14.870> are<00:10:15.529> already 00:10:15.819 --> 00:10:15.829 align:start position:0% stateless paradigm so we are already 00:10:15.829 --> 00:10:19.049 align:start position:0% stateless paradigm so we are already building<00:10:16.730> execution<00:10:17.420> environments<00:10:17.959> that<00:10:18.079> are 00:10:19.049 --> 00:10:19.059 align:start position:0% building execution environments that are 00:10:19.059 --> 00:10:23.379 align:start position:0% building execution environments that are operating<00:10:20.059> with<00:10:20.319> in<00:10:21.319> a<00:10:21.589> stateless<00:10:21.949> way<00:10:22.269> and<00:10:23.269> we 00:10:23.379 --> 00:10:23.389 align:start position:0% operating with in a stateless way and we 00:10:23.389 --> 00:10:26.949 align:start position:0% operating with in a stateless way and we built<00:10:23.660> a<00:10:23.870> simulation<00:10:25.480> within<00:10:26.480> lighthouses 00:10:26.949 --> 00:10:26.959 align:start position:0% built a simulation within lighthouses 00:10:26.959 --> 00:10:30.069 align:start position:0% built a simulation within lighthouses kind<00:10:27.740> of<00:10:27.829> based<00:10:28.339> code<00:10:28.610> base<00:10:28.819> where<00:10:29.120> we<00:10:29.449> now 00:10:30.069 --> 00:10:30.079 align:start position:0% kind of based code base where we now 00:10:30.079 --> 00:10:32.439 align:start position:0% kind of based code base where we now have<00:10:30.290> shard<00:10:31.130> chains<00:10:31.459> or<00:10:31.670> multiple<00:10:31.970> char<00:10:32.149> genes 00:10:32.439 --> 00:10:32.449 align:start position:0% have shard chains or multiple char genes 00:10:32.449 --> 00:10:35.259 align:start position:0% have shard chains or multiple char genes interacting<00:10:33.199> with<00:10:33.350> the<00:10:33.410> beacon<00:10:33.649> chain<00:10:34.269> and 00:10:35.259 --> 00:10:35.269 align:start position:0% interacting with the beacon chain and 00:10:35.269 --> 00:10:37.030 align:start position:0% interacting with the beacon chain and we're<00:10:35.420> able<00:10:35.509> to<00:10:35.689> actually<00:10:35.839> run<00:10:36.380> the<00:10:36.800> state 00:10:37.030 --> 00:10:37.040 align:start position:0% we're able to actually run the state 00:10:37.040 --> 00:10:39.220 align:start position:0% we're able to actually run the state execution<00:10:37.610> on<00:10:37.790> that<00:10:37.970> as<00:10:38.089> well<00:10:38.269> and<00:10:38.509> run<00:10:39.079> these 00:10:39.220 --> 00:10:39.230 align:start position:0% execution on that as well and run these 00:10:39.230 --> 00:10:41.079 align:start position:0% execution on that as well and run these execution<00:10:39.800> environments<00:10:40.279> on<00:10:40.399> it<00:10:40.550> as<00:10:40.639> well<00:10:40.790> and 00:10:41.079 --> 00:10:41.089 align:start position:0% execution environments on it as well and 00:10:41.089 --> 00:10:45.699 align:start position:0% execution environments on it as well and so<00:10:41.750> we<00:10:42.470> have<00:10:42.500> been<00:10:43.069> I<00:10:43.870> guess<00:10:44.870> kind<00:10:45.170> of<00:10:45.199> what 00:10:45.699 --> 00:10:45.709 align:start position:0% so we have been I guess kind of what 00:10:45.709 --> 00:10:47.889 align:start position:0% so we have been I guess kind of what we're<00:10:45.829> doing<00:10:45.949> next<00:10:46.250> is<00:10:46.750> expanding<00:10:47.750> that<00:10:47.839> to 00:10:47.889 --> 00:10:47.899 align:start position:0% we're doing next is expanding that to 00:10:47.899 --> 00:10:51.400 align:start position:0% we're doing next is expanding that to include<00:10:48.410> more<00:10:49.160> simulations<00:10:49.759> of<00:10:49.910> what<00:10:50.410> the 00:10:51.400 --> 00:10:51.410 align:start position:0% include more simulations of what the 00:10:51.410 --> 00:10:54.329 align:start position:0% include more simulations of what the state<00:10:52.069> market<00:10:52.430> might<00:10:52.579> look<00:10:52.759> like 00:10:54.329 --> 00:10:54.339 align:start position:0% state market might look like 00:10:54.339 --> 00:10:58.420 align:start position:0% state market might look like advancing<00:10:55.339> on<00:10:55.600> what<00:10:56.600> may<00:10:56.779> be<00:10:56.860> ease<00:10:57.860> for<00:10:58.189> some 00:10:58.420 --> 00:10:58.430 align:start position:0% advancing on what may be ease for some 00:10:58.430 --> 00:11:00.749 align:start position:0% advancing on what may be ease for some of<00:10:58.490> those<00:10:58.550> contract<00:10:59.029> frameworks<00:10:59.509> as<00:10:59.660> well 00:11:00.749 --> 00:11:00.759 align:start position:0% of those contract frameworks as well 00:11:00.759 --> 00:11:06.480 align:start position:0% of those contract frameworks as well yeah<00:11:03.639> you<00:11:04.639> guys<00:11:04.819> want<00:11:05.059> to<00:11:05.120> give<00:11:05.240> an<00:11:05.360> update 00:11:06.480 --> 00:11:06.490 align:start position:0% yeah you guys want to give an update 00:11:06.490 --> 00:11:10.860 align:start position:0% yeah you guys want to give an update yeah<00:11:07.490> we're<00:11:08.480> going<00:11:08.600> on<00:11:08.660> all<00:11:08.779> sorts<00:11:09.050> of<00:11:09.139> things 00:11:10.860 --> 00:11:10.870 align:start position:0% yeah we're going on all sorts of things 00:11:10.870 --> 00:11:13.420 align:start position:0% yeah we're going on all sorts of things adding<00:11:11.870> add<00:11:12.319> some<00:11:12.680> additional<00:11:12.829> tests<00:11:13.339> to 00:11:13.420 --> 00:11:13.430 align:start position:0% adding add some additional tests to 00:11:13.430 --> 00:11:16.059 align:start position:0% adding add some additional tests to phase<00:11:13.579> zero<00:11:14.410> justin<00:11:15.410> Drake<00:11:15.620> did<00:11:15.860> some 00:11:16.059 --> 00:11:16.069 align:start position:0% phase zero justin Drake did some 00:11:16.069 --> 00:11:18.490 align:start position:0% phase zero justin Drake did some excellent<00:11:16.459> work<00:11:16.790> making<00:11:17.420> phase<00:11:17.750> one<00:11:18.050> look 00:11:18.490 --> 00:11:18.500 align:start position:0% excellent work making phase one look 00:11:18.500 --> 00:11:20.860 align:start position:0% excellent work making phase one look really<00:11:18.769> nice<00:11:18.920> and<00:11:19.279> easy<00:11:19.939> to<00:11:20.209> reason<00:11:20.480> about<00:11:20.569> an 00:11:20.860 --> 00:11:20.870 align:start position:0% really nice and easy to reason about an 00:11:20.870 --> 00:11:25.090 align:start position:0% really nice and easy to reason about an elegant<00:11:22.509> a<00:11:23.509> lot<00:11:23.839> of<00:11:24.019> research<00:11:24.800> and<00:11:24.980> thought 00:11:25.090 --> 00:11:25.100 align:start position:0% elegant a lot of research and thought 00:11:25.100 --> 00:11:27.790 align:start position:0% elegant a lot of research and thought and<00:11:25.309> conversations<00:11:25.880> around<00:11:26.029> phase<00:11:26.300> two<00:11:26.800> and 00:11:27.790 --> 00:11:27.800 align:start position:0% and conversations around phase two and 00:11:27.800 --> 00:11:29.759 align:start position:0% and conversations around phase two and more<00:11:28.100> recently<00:11:28.490> some<00:11:28.639> conversations<00:11:29.240> around 00:11:29.759 --> 00:11:29.769 align:start position:0% more recently some conversations around 00:11:29.769 --> 00:11:32.169 align:start position:0% more recently some conversations around potential<00:11:30.769> alternate<00:11:31.339> structures<00:11:31.819> with 00:11:32.169 --> 00:11:32.179 align:start position:0% potential alternate structures with 00:11:32.179 --> 00:11:35.620 align:start position:0% potential alternate structures with phase<00:11:32.389> one<00:11:32.630> that<00:11:32.839> might<00:11:32.990> allow<00:11:34.269> more<00:11:35.269> rapid 00:11:35.620 --> 00:11:35.630 align:start position:0% phase one that might allow more rapid 00:11:35.630 --> 00:11:37.509 align:start position:0% phase one that might allow more rapid cross-linking<00:11:36.259> and<00:11:36.410> better<00:11:36.889> communication 00:11:37.509 --> 00:11:37.519 align:start position:0% cross-linking and better communication 00:11:37.519 --> 00:11:41.769 align:start position:0% cross-linking and better communication between<00:11:37.610> shards<00:11:39.009> at<00:11:40.009> the<00:11:40.160> same<00:11:40.429> time<00:11:40.790> working 00:11:41.769 --> 00:11:41.779 align:start position:0% between shards at the same time working 00:11:41.779 --> 00:11:43.660 align:start position:0% between shards at the same time working on<00:11:41.929> some<00:11:42.110> standards<00:11:42.529> helping<00:11:43.370> drive<00:11:43.550> the 00:11:43.660 --> 00:11:43.670 align:start position:0% on some standards helping drive the 00:11:43.670 --> 00:11:47.049 align:start position:0% on some standards helping drive the standards<00:11:44.029> process<00:11:44.059> on<00:11:44.540> BLS<00:11:45.880> Karl's<00:11:46.880> been 00:11:47.049 --> 00:11:47.059 align:start position:0% standards process on BLS Karl's been 00:11:47.059 --> 00:11:50.319 align:start position:0% standards process on BLS Karl's been looking<00:11:47.360> into<00:11:47.480> key<00:11:47.809> store<00:11:48.079> formats<00:11:49.329> pushing 00:11:50.319 --> 00:11:50.329 align:start position:0% looking into key store formats pushing 00:11:50.329 --> 00:11:53.220 align:start position:0% looking into key store formats pushing on<00:11:50.480> the<00:11:50.689> deposit<00:11:51.259> contract<00:11:51.500> stuff<00:11:52.160> which<00:11:52.699> is 00:11:53.220 --> 00:11:53.230 align:start position:0% on the deposit contract stuff which is 00:11:53.230 --> 00:11:55.840 align:start position:0% on the deposit contract stuff which is formally<00:11:54.230> verified<00:11:54.290> and<00:11:55.040> ready<00:11:55.279> but<00:11:55.699> we're 00:11:55.840 --> 00:11:55.850 align:start position:0% formally verified and ready but we're 00:11:55.850 --> 00:11:57.429 align:start position:0% formally verified and ready but we're waiting<00:11:56.029> on<00:11:56.300> the<00:11:56.509> be<00:11:56.630> lost<00:11:56.779> standardization 00:11:57.429 --> 00:11:57.439 align:start position:0% waiting on the be lost standardization 00:11:57.439 --> 00:12:01.689 align:start position:0% waiting on the be lost standardization to<00:11:57.740> launch<00:11:58.220> that<00:11:58.490> oh<00:11:59.449> and<00:12:00.579> opening<00:12:01.579> up<00:12:01.670> the 00:12:01.689 --> 00:12:01.699 align:start position:0% to launch that oh and opening up the 00:12:01.699 --> 00:12:03.819 align:start position:0% to launch that oh and opening up the conversations<00:12:02.269> around<00:12:02.449> the<00:12:02.779> coming<00:12:03.319> public 00:12:03.819 --> 00:12:03.829 align:start position:0% conversations around the coming public 00:12:03.829 --> 00:12:05.160 align:start position:0% conversations around the coming public test<00:12:04.040> nets<00:12:04.250> with 00:12:05.160 --> 00:12:05.170 align:start position:0% test nets with 00:12:05.170 --> 00:12:07.079 align:start position:0% test nets with with<00:12:05.319> the<00:12:05.439> clients<00:12:05.859> and<00:12:06.009> always<00:12:06.759> kind<00:12:06.970> of 00:12:07.079 --> 00:12:07.089 align:start position:0% with the clients and always kind of 00:12:07.089 --> 00:12:09.509 align:start position:0% with the clients and always kind of providing<00:12:07.600> support<00:12:07.989> and<00:12:08.519> answering 00:12:09.509 --> 00:12:09.519 align:start position:0% providing support and answering 00:12:09.519 --> 00:12:12.739 align:start position:0% providing support and answering questions<00:12:09.879> on<00:12:10.299> a<00:12:10.660> client<00:12:11.019> side<00:12:11.230> so<00:12:11.920> just 00:12:12.739 --> 00:12:12.749 align:start position:0% questions on a client side so just 00:12:12.749 --> 00:12:16.079 align:start position:0% questions on a client side so just keeping<00:12:13.749> everything<00:12:14.019> moving<00:12:14.170> forward<00:12:15.059> yep 00:12:16.079 --> 00:12:16.089 align:start position:0% keeping everything moving forward yep 00:12:16.089 --> 00:12:18.379 align:start position:0% keeping everything moving forward yep and<00:12:16.509> I've<00:12:16.660> been<00:12:16.899> coming<00:12:17.649> up<00:12:17.920> with<00:12:18.100> this 00:12:18.379 --> 00:12:18.389 align:start position:0% and I've been coming up with this 00:12:18.389 --> 00:12:20.939 align:start position:0% and I've been coming up with this alternate<00:12:19.389> structure<00:12:20.290> is<00:12:20.410> for<00:12:20.619> faster 00:12:20.939 --> 00:12:20.949 align:start position:0% alternate structure is for faster 00:12:20.949 --> 00:12:22.829 align:start position:0% alternate structure is for faster cross-linking<00:12:21.669> that<00:12:21.939> Danny<00:12:22.179> mentioned<00:12:22.720> that 00:12:22.829 --> 00:12:22.839 align:start position:0% cross-linking that Danny mentioned that 00:12:22.839 --> 00:12:26.039 align:start position:0% cross-linking that Danny mentioned that we<00:12:22.989> should<00:12:23.019> have<00:12:23.290> some<00:12:23.819> information<00:12:24.819> about<00:12:25.749> me 00:12:26.039 --> 00:12:26.049 align:start position:0% we should have some information about me 00:12:26.049 --> 00:12:30.809 align:start position:0% we should have some information about me maybe<00:12:26.589> very<00:12:26.829> soon<00:12:27.869> also<00:12:29.309> data<00:12:30.309> availability 00:12:30.809 --> 00:12:30.819 align:start position:0% maybe very soon also data availability 00:12:30.819 --> 00:12:34.019 align:start position:0% maybe very soon also data availability here<00:12:31.329> there's<00:12:31.899> a<00:12:32.309> data<00:12:33.309> field<00:12:33.519> there's<00:12:33.819> been<00:12:33.999> a 00:12:34.019 --> 00:12:34.029 align:start position:0% here there's a data field there's been a 00:12:34.029 --> 00:12:37.199 align:start position:0% here there's a data field there's been a lot<00:12:34.239> of<00:12:34.269> kind<00:12:34.869> of<00:12:35.249> progress<00:12:36.249> on<00:12:36.489> different 00:12:37.199 --> 00:12:37.209 align:start position:0% lot of kind of progress on different 00:12:37.209 --> 00:12:38.909 align:start position:0% lot of kind of progress on different kinds<00:12:37.600> of<00:12:37.689> data<00:12:37.929> availability<00:12:38.350> proving 00:12:38.909 --> 00:12:38.919 align:start position:0% kinds of data availability proving 00:12:38.919 --> 00:12:40.819 align:start position:0% kinds of data availability proving mechanisms<00:12:39.519> there<00:12:39.819> was<00:12:39.939> also<00:12:40.119> that 00:12:40.819 --> 00:12:40.829 align:start position:0% mechanisms there was also that 00:12:40.829 --> 00:12:43.499 align:start position:0% mechanisms there was also that interesting<00:12:41.829> coded<00:12:42.220> Merkle<00:12:42.549> tree<00:12:42.819> paper<00:12:43.059> from 00:12:43.499 --> 00:12:43.509 align:start position:0% interesting coded Merkle tree paper from 00:12:43.509 --> 00:12:46.919 align:start position:0% interesting coded Merkle tree paper from Agra<00:12:44.350> a<00:12:44.889> couple<00:12:45.579> of<00:12:45.699> days<00:12:45.850> ago<00:12:46.089> that<00:12:46.269> lets<00:12:46.749> you 00:12:46.919 --> 00:12:46.929 align:start position:0% Agra a couple of days ago that lets you 00:12:46.929 --> 00:12:50.009 align:start position:0% Agra a couple of days ago that lets you do<00:12:47.199> I<00:12:47.619> raise<00:12:48.309> your<00:12:48.519> coated<00:12:48.879> roots<00:12:49.119> with<00:12:49.480> much 00:12:50.009 --> 00:12:50.019 align:start position:0% do I raise your coated roots with much 00:12:50.019 --> 00:12:51.539 align:start position:0% do I raise your coated roots with much smaller<00:12:50.319> fraud<00:12:50.679> proofs<00:12:51.009> which<00:12:51.249> is<00:12:51.399> also 00:12:51.539 --> 00:12:51.549 align:start position:0% smaller fraud proofs which is also 00:12:51.549 --> 00:12:55.349 align:start position:0% smaller fraud proofs which is also really<00:12:52.029> which<00:12:52.540> was<00:12:52.689> also<00:12:52.839> really<00:12:53.169> nice<00:12:54.359> also 00:12:55.349 --> 00:12:55.359 align:start position:0% really which was also really nice also 00:12:55.359 --> 00:12:58.619 align:start position:0% really which was also really nice also we're<00:12:55.929> thinking<00:12:56.799> about<00:12:57.009> half<00:12:57.489> fee<00:12:58.119> mark<00:12:58.389> it's 00:12:58.619 --> 00:12:58.629 align:start position:0% we're thinking about half fee mark it's 00:12:58.629 --> 00:13:01.439 align:start position:0% we're thinking about half fee mark it's simple<00:12:59.019> a<00:12:59.399> simplification<00:13:00.399> and<00:13:00.999> coming<00:13:01.269> and 00:13:01.439 --> 00:13:01.449 align:start position:0% simple a simplification and coming and 00:13:01.449 --> 00:13:05.759 align:start position:0% simple a simplification and coming and coming<00:13:01.779> up<00:13:02.439> with<00:13:02.649> ways<00:13:03.339> to<00:13:03.449> and<00:13:04.709> deal<00:13:05.709> with 00:13:05.759 --> 00:13:05.769 align:start position:0% coming up with ways to and deal with 00:13:05.769 --> 00:13:07.739 align:start position:0% coming up with ways to and deal with edge<00:13:06.100> cases<00:13:06.369> and<00:13:06.699> really<00:13:06.819> real<00:13:07.209> your<00:13:07.389> markets 00:13:07.739 --> 00:13:07.749 align:start position:0% edge cases and really real your markets 00:13:07.749 --> 00:13:13.829 align:start position:0% edge cases and really real your markets and<00:13:07.899> all<00:13:07.959> of<00:13:08.049> those<00:13:08.169> issues<00:13:08.589> I<00:13:11.519> guess<00:13:12.839> I've 00:13:13.829 --> 00:13:13.839 align:start position:0% and all of those issues I guess I've 00:13:13.839 --> 00:13:17.780 align:start position:0% and all of those issues I guess I've been<00:13:13.959> thinking<00:13:14.439> about<00:13:15.269> optional<00:13:16.269> upgrades 00:13:17.780 --> 00:13:17.790 align:start position:0% been thinking about optional upgrades 00:13:17.790 --> 00:13:22.280 align:start position:0% been thinking about optional upgrades one<00:13:18.790> of<00:13:18.939> them<00:13:19.119> is<00:13:20.129> the<00:13:21.129> idea<00:13:21.369> of<00:13:21.489> a<00:13:21.610> secret 00:13:22.280 --> 00:13:22.290 align:start position:0% one of them is the idea of a secret 00:13:22.290 --> 00:13:24.809 align:start position:0% one of them is the idea of a secret leader<00:13:23.290> election<00:13:23.619> so<00:13:24.069> right<00:13:24.309> now 00:13:24.809 --> 00:13:24.819 align:start position:0% leader election so right now 00:13:24.819 --> 00:13:27.030 align:start position:0% leader election so right now beacon<00:13:25.480> proposes<00:13:26.049> and<00:13:26.290> Shah<00:13:26.470> proposes 00:13:27.030 --> 00:13:27.040 align:start position:0% beacon proposes and Shah proposes 00:13:27.040 --> 00:13:28.679 align:start position:0% beacon proposes and Shah proposes they're<00:13:27.519> known<00:13:27.699> in<00:13:27.730> advance<00:13:27.970> that<00:13:28.540> they're 00:13:28.679 --> 00:13:28.689 align:start position:0% they're known in advance that they're 00:13:28.689 --> 00:13:31.949 align:start position:0% they're known in advance that they're going<00:13:28.929> to<00:13:29.579> create<00:13:30.579> a<00:13:30.669> block<00:13:30.970> and<00:13:31.179> then<00:13:31.509> these 00:13:31.949 --> 00:13:31.959 align:start position:0% going to create a block and then these 00:13:31.959 --> 00:13:34.710 align:start position:0% going to create a block and then these these<00:13:32.019> leader<00:13:32.649> based<00:13:33.549> systems<00:13:34.059> suffer<00:13:34.569> from 00:13:34.710 --> 00:13:34.720 align:start position:0% these leader based systems suffer from 00:13:34.720 --> 00:13:39.150 align:start position:0% these leader based systems suffer from denial<00:13:35.529> of<00:13:35.619> service<00:13:35.980> attack<00:13:36.879> surface<00:13:37.529> and<00:13:38.529> so 00:13:39.150 --> 00:13:39.160 align:start position:0% denial of service attack surface and so 00:13:39.160 --> 00:13:41.879 align:start position:0% denial of service attack surface and so what<00:13:39.879> if<00:13:39.999> we<00:13:40.149> can<00:13:40.419> have<00:13:41.079> a<00:13:41.110> system<00:13:41.410> where<00:13:41.829> you 00:13:41.879 --> 00:13:41.889 align:start position:0% what if we can have a system where you 00:13:41.889 --> 00:13:44.159 align:start position:0% what if we can have a system where you don't<00:13:42.339> know<00:13:42.549> ahead<00:13:43.179> of<00:13:43.209> time<00:13:43.509> who<00:13:43.899> will<00:13:44.019> be 00:13:44.159 --> 00:13:44.169 align:start position:0% don't know ahead of time who will be 00:13:44.169 --> 00:13:45.569 align:start position:0% don't know ahead of time who will be creating<00:13:44.589> the<00:13:44.649> next<00:13:44.799> block<00:13:45.069> that<00:13:45.339> would<00:13:45.459> be 00:13:45.569 --> 00:13:45.579 align:start position:0% creating the next block that would be 00:13:45.579 --> 00:13:49.049 align:start position:0% creating the next block that would be much<00:13:45.759> more<00:13:45.910> resilient<00:13:47.699> another<00:13:48.699> kind<00:13:48.999> of 00:13:49.049 --> 00:13:49.059 align:start position:0% much more resilient another kind of 00:13:49.059 --> 00:13:50.460 align:start position:0% much more resilient another kind of optional<00:13:49.449> security<00:13:49.660> upgrade<00:13:50.139> that<00:13:50.289> I've<00:13:50.379> been 00:13:50.460 --> 00:13:50.470 align:start position:0% optional security upgrade that I've been 00:13:50.470 --> 00:13:52.529 align:start position:0% optional security upgrade that I've been working<00:13:50.799> on<00:13:50.980> for<00:13:51.039> some<00:13:51.399> time<00:13:51.429> and<00:13:51.939> it's<00:13:52.089> still 00:13:52.529 --> 00:13:52.539 align:start position:0% working on for some time and it's still 00:13:52.539 --> 00:13:53.699 align:start position:0% working on for some time and it's still ongoing<00:13:52.689> and<00:13:53.139> we<00:13:53.199> making<00:13:53.410> lots<00:13:53.559> of<00:13:53.649> progress 00:13:53.699 --> 00:13:53.709 align:start position:0% ongoing and we making lots of progress 00:13:53.709 --> 00:13:56.220 align:start position:0% ongoing and we making lots of progress is<00:13:54.220> the<00:13:54.429> the<00:13:54.639> vdf<00:13:55.059> project<00:13:55.539> to<00:13:55.869> have<00:13:56.049> an 00:13:56.220 --> 00:13:56.230 align:start position:0% is the the vdf project to have an 00:13:56.230 --> 00:13:58.979 align:start position:0% is the the vdf project to have an unbiased<00:13:56.529> ball<00:13:56.829> randomness<00:13:57.660> and<00:13:58.660> I<00:13:58.809> guess 00:13:58.979 --> 00:13:58.989 align:start position:0% unbiased ball randomness and I guess 00:13:58.989 --> 00:14:01.379 align:start position:0% unbiased ball randomness and I guess I've<00:13:59.139> also<00:13:59.289> been<00:13:59.559> thinking<00:13:59.799> you<00:14:00.459> know<00:14:00.489> maybe<00:14:01.239> a 00:14:01.379 --> 00:14:01.389 align:start position:0% I've also been thinking you know maybe a 00:14:01.389 --> 00:14:04.679 align:start position:0% I've also been thinking you know maybe a decade<00:14:01.809> into<00:14:01.959> the<00:14:02.139> future<00:14:02.499> on<00:14:02.709> on<00:14:03.459> e3<00:14:03.939> and<00:14:04.539> how 00:14:04.679 --> 00:14:04.689 align:start position:0% decade into the future on on e3 and how 00:14:04.689 --> 00:14:11.100 align:start position:0% decade into the future on on e3 and how to<00:14:04.749> make<00:14:05.109> a<00:14:05.819> quantum<00:14:06.819> secure 00:14:11.100 --> 00:14:11.110 align:start position:0% 00:14:11.110 --> 00:14:14.530 align:start position:0% at<00:14:12.110> least<00:14:12.380> ten<00:14:12.620> years<00:14:12.649> I'd<00:14:12.980> say<00:14:13.190> damn<00:14:13.910> bonus<00:14:14.300> is 00:14:14.530 --> 00:14:14.540 align:start position:0% at least ten years I'd say damn bonus is 00:14:14.540 --> 00:14:30.930 align:start position:0% at least ten years I'd say damn bonus is 30<00:14:23.080> Dan<00:14:24.080> also<00:14:24.260> said<00:14:24.529> don't<00:14:24.740> quote<00:14:24.920> me<00:14:25.100> on<00:14:25.130> that 00:14:30.930 --> 00:14:30.940 align:start position:0% 00:14:30.940 --> 00:14:33.610 align:start position:0% all<00:14:31.940> right<00:14:32.209> I'm<00:14:32.540> gonna<00:14:32.720> open<00:14:32.899> up<00:14:33.200> now<00:14:33.560> to 00:14:33.610 --> 00:14:33.620 align:start position:0% all right I'm gonna open up now to 00:14:33.620 --> 00:14:36.940 align:start position:0% all right I'm gonna open up now to questions<00:14:34.579> from<00:14:34.760> the<00:14:34.850> audience<00:14:35.000> I<00:14:35.769> wanna<00:14:36.769> go 00:14:36.940 --> 00:14:36.950 align:start position:0% questions from the audience I wanna go 00:14:36.950 --> 00:14:41.790 align:start position:0% questions from the audience I wanna go first 00:14:41.790 --> 00:14:41.800 align:start position:0% 00:14:41.800 --> 00:14:43.900 align:start position:0% you<00:14:42.800> mean<00:14:42.920> teaching<00:14:43.190> a<00:14:43.339> lot<00:14:43.610> of<00:14:43.700> work<00:14:43.790> on 00:14:43.900 --> 00:14:43.910 align:start position:0% you mean teaching a lot of work on 00:14:43.910 --> 00:14:46.090 align:start position:0% you mean teaching a lot of work on themarket<00:14:44.240> one<00:14:45.140> thing<00:14:45.320> that<00:14:45.500> I<00:14:45.560> would<00:14:45.709> love<00:14:45.920> to 00:14:46.090 --> 00:14:46.100 align:start position:0% themarket one thing that I would love to 00:14:46.100 --> 00:14:48.340 align:start position:0% themarket one thing that I would love to see<00:14:46.370> is<00:14:46.790> a<00:14:47.000> bit<00:14:47.300> of<00:14:47.390> a<00:14:47.510> high<00:14:47.660> level<00:14:47.930> abstraction 00:14:48.340 --> 00:14:48.350 align:start position:0% see is a bit of a high level abstraction 00:14:48.350 --> 00:14:52.150 align:start position:0% see is a bit of a high level abstraction so<00:14:48.980> that<00:14:49.160> you<00:14:49.339> can<00:14:49.550> specify<00:14:50.149> how<00:14:50.890> fast<00:14:51.890> you 00:14:52.150 --> 00:14:52.160 align:start position:0% so that you can specify how fast you 00:14:52.160 --> 00:14:54.400 align:start position:0% so that you can specify how fast you want<00:14:52.370> a<00:14:52.579> transaction<00:14:53.209> to<00:14:53.240> happen<00:14:53.660> like<00:14:54.200> I 00:14:54.400 --> 00:14:54.410 align:start position:0% want a transaction to happen like I 00:14:54.410 --> 00:14:56.199 align:start position:0% want a transaction to happen like I wanted<00:14:54.709> to<00:14:54.829> happen<00:14:54.980> in<00:14:55.220> a<00:14:55.310> minute<00:14:55.430> or<00:14:55.850> five 00:14:56.199 --> 00:14:56.209 align:start position:0% wanted to happen in a minute or five 00:14:56.209 --> 00:14:58.030 align:start position:0% wanted to happen in a minute or five minutes<00:14:56.480> or<00:14:56.630> an<00:14:56.750> hour<00:14:56.839> or<00:14:57.170> I<00:14:57.230> don't<00:14:57.350> care<00:14:57.769> and 00:14:58.030 --> 00:14:58.040 align:start position:0% minutes or an hour or I don't care and 00:14:58.040 --> 00:15:01.090 align:start position:0% minutes or an hour or I don't care and then<00:14:58.490> and<00:14:58.730> then<00:14:59.149> it<00:14:59.269> builds<00:14:59.450> you<00:14:59.750> like<00:15:00.680> however 00:15:01.090 --> 00:15:01.100 align:start position:0% then and then it builds you like however 00:15:01.100 --> 00:15:02.920 align:start position:0% then and then it builds you like however much<00:15:01.279> it<00:15:01.610> should<00:15:01.970> the<00:15:02.240> market<00:15:02.540> rate<00:15:02.660> would<00:15:02.779> be 00:15:02.920 --> 00:15:02.930 align:start position:0% much it should the market rate would be 00:15:02.930 --> 00:15:08.230 align:start position:0% much it should the market rate would be for<00:15:03.560> that<00:15:05.950> right<00:15:06.950> you<00:15:07.100> could<00:15:07.250> pay<00:15:07.760> more<00:15:07.970> and 00:15:08.230 --> 00:15:08.240 align:start position:0% for that right you could pay more and 00:15:08.240 --> 00:15:09.160 align:start position:0% for that right you could pay more and then<00:15:08.329> it<00:15:08.420> would<00:15:08.510> refund<00:15:08.810> you<00:15:09.019> the<00:15:09.079> difference 00:15:09.160 --> 00:15:09.170 align:start position:0% then it would refund you the difference 00:15:09.170 --> 00:15:11.259 align:start position:0% then it would refund you the difference because<00:15:09.800> right<00:15:09.950> now<00:15:10.070> it's<00:15:10.190> guesswork<00:15:10.490> like 00:15:11.259 --> 00:15:11.269 align:start position:0% because right now it's guesswork like 00:15:11.269 --> 00:15:13.660 align:start position:0% because right now it's guesswork like trying<00:15:12.050> it<00:15:12.140> trying<00:15:12.470> to<00:15:12.529> you<00:15:12.980> know<00:15:13.040> guess<00:15:13.519> the 00:15:13.660 --> 00:15:13.670 align:start position:0% trying it trying to you know guess the 00:15:13.670 --> 00:15:16.410 align:start position:0% trying it trying to you know guess the right<00:15:13.790> amount<00:15:14.089> of<00:15:14.149> gas<00:15:14.560> although<00:15:15.560> the<00:15:15.709> gas 00:15:16.410 --> 00:15:16.420 align:start position:0% right amount of gas although the gas 00:15:16.420 --> 00:15:19.090 align:start position:0% right amount of gas although the gas this<00:15:17.420> is<00:15:17.600> the<00:15:17.750> sort<00:15:17.990> of<00:15:18.079> problem<00:15:18.470> that<00:15:18.500> EAP<00:15:19.070> a 00:15:19.090 --> 00:15:19.100 align:start position:0% this is the sort of problem that EAP a 00:15:19.100 --> 00:15:21.100 align:start position:0% this is the sort of problem that EAP a one<00:15:19.399> five<00:15:19.610> five<00:15:19.850> nine<00:15:19.880> is<00:15:20.360> meant<00:15:20.600> to<00:15:20.750> basically 00:15:21.100 --> 00:15:21.110 align:start position:0% one five five nine is meant to basically 00:15:21.110 --> 00:15:24.130 align:start position:0% one five five nine is meant to basically eliminate<00:15:21.520> like<00:15:22.520> users<00:15:23.420> would<00:15:23.779> in<00:15:23.990> the<00:15:24.110> normal 00:15:24.130 --> 00:15:24.140 align:start position:0% eliminate like users would in the normal 00:15:24.140 --> 00:15:26.380 align:start position:0% eliminate like users would in the normal case<00:15:24.620> either<00:15:24.890> transactions<00:15:25.640> just<00:15:25.880> included 00:15:26.380 --> 00:15:26.390 align:start position:0% case either transactions just included 00:15:26.390 --> 00:15:40.870 align:start position:0% case either transactions just included immediately<00:15:31.450> anyone<00:15:32.450> else<00:15:32.920> questions<00:15:33.920> Oh 00:15:40.870 --> 00:15:40.880 align:start position:0% 00:15:40.880 --> 00:15:43.370 align:start position:0% okay<00:15:41.880> we<00:15:42.090> have<00:15:42.240> cable<00:15:42.630> so<00:15:42.779> can<00:15:42.960> you<00:15:43.050> come<00:15:43.230> over 00:15:43.370 --> 00:15:43.380 align:start position:0% okay we have cable so can you come over 00:15:43.380 --> 00:15:50.740 align:start position:0% okay we have cable so can you come over please<00:15:48.020> -<00:15:49.020> she<00:15:49.350> actually<00:15:49.620> have<00:15:49.920> questions<00:15:50.490> so 00:15:50.740 --> 00:15:50.750 align:start position:0% please - she actually have questions so 00:15:50.750 --> 00:15:53.570 align:start position:0% please - she actually have questions so the<00:15:51.750> number<00:15:51.990> of<00:15:52.020> straws<00:15:52.320> i<00:15:52.529> do<00:15:52.920> -<00:15:53.040> times<00:15:53.370> we 00:15:53.570 --> 00:15:53.580 align:start position:0% the number of straws i do - times we 00:15:53.580 --> 00:15:56.870 align:start position:0% the number of straws i do - times we start<00:15:53.790> with<00:15:54.000> 1024<00:15:54.980> so<00:15:55.980> i'm<00:15:56.160> wondering<00:15:56.490> what 00:15:56.870 --> 00:15:56.880 align:start position:0% start with 1024 so i'm wondering what 00:15:56.880 --> 00:15:59.000 align:start position:0% start with 1024 so i'm wondering what why<00:15:57.210> -<00:15:57.240> stitch<00:15:57.660> number<00:15:57.900> especially<00:15:58.860> together 00:15:59.000 --> 00:15:59.010 align:start position:0% why - stitch number especially together 00:15:59.010 --> 00:16:01.040 align:start position:0% why - stitch number especially together with<00:15:59.370> a<00:15:59.430> large<00:15:59.610> number<00:15:59.790> of<00:15:59.910> agitators<00:16:00.450> there 00:16:01.040 --> 00:16:01.050 align:start position:0% with a large number of agitators there 00:16:01.050 --> 00:16:02.329 align:start position:0% with a large number of agitators there will<00:16:01.140> be<00:16:01.170> significant<00:16:01.650> costs<00:16:01.980> on<00:16:02.130> camera 00:16:02.329 --> 00:16:02.339 align:start position:0% will be significant costs on camera 00:16:02.339 --> 00:16:05.300 align:start position:0% will be significant costs on camera cause<00:16:02.580> especially<00:16:02.970> as<00:16:03.450> starting<00:16:04.170> of<00:16:05.100> the 00:16:05.300 --> 00:16:05.310 align:start position:0% cause especially as starting of the 00:16:05.310 --> 00:16:07.700 align:start position:0% cause especially as starting of the easter<00:16:05.520> -<00:16:05.730> is<00:16:06.150> that<00:16:06.450> concern<00:16:06.960> that<00:16:07.230> maybe<00:16:07.410> we 00:16:07.700 --> 00:16:07.710 align:start position:0% easter - is that concern that maybe we 00:16:07.710 --> 00:16:09.980 align:start position:0% easter - is that concern that maybe we may<00:16:07.920> not<00:16:08.040> be<00:16:08.100> able<00:16:08.279> to<00:16:08.670> reach<00:16:08.850> so<00:16:09.420> many<00:16:09.450> nodes 00:16:09.980 --> 00:16:09.990 align:start position:0% may not be able to reach so many nodes 00:16:09.990 --> 00:16:15.920 align:start position:0% may not be able to reach so many nodes or<00:16:10.320> validators<00:16:10.800> at<00:16:11.339> the<00:16:11.460> beginning<00:16:14.450> and<00:16:15.450> so 00:16:15.920 --> 00:16:15.930 align:start position:0% or validators at the beginning and so 00:16:15.930 --> 00:16:19.550 align:start position:0% or validators at the beginning and so this<00:16:16.770> is<00:16:16.950> one<00:16:17.339> of<00:16:17.520> the<00:16:17.750> one<00:16:18.750> one<00:16:19.050> of<00:16:19.200> the<00:16:19.320> things 00:16:19.550 --> 00:16:19.560 align:start position:0% this is one of the one one of the things 00:16:19.560 --> 00:16:21.620 align:start position:0% this is one of the one one of the things that<00:16:19.920> this<00:16:20.130> kind<00:16:20.550> of<00:16:20.640> faster<00:16:21.060> cross-linking 00:16:21.620 --> 00:16:21.630 align:start position:0% that this kind of faster cross-linking 00:16:21.630 --> 00:16:23.180 align:start position:0% that this kind of faster cross-linking proposal<00:16:22.110> might<00:16:22.260> actually<00:16:22.470> end<00:16:22.680> up<00:16:22.950> changing 00:16:23.180 --> 00:16:23.190 align:start position:0% proposal might actually end up changing 00:16:23.190 --> 00:16:26.560 align:start position:0% proposal might actually end up changing potentially<00:16:24.029> but<00:16:24.779> I<00:16:25.020> think<00:16:25.290> in<00:16:25.800> general<00:16:25.860> the 00:16:26.560 --> 00:16:26.570 align:start position:0% potentially but I think in general the 00:16:26.570 --> 00:16:28.760 align:start position:0% potentially but I think in general the justification<00:16:27.570> here<00:16:27.960> is<00:16:28.140> that<00:16:28.380> we're<00:16:28.589> trying 00:16:28.760 --> 00:16:28.770 align:start position:0% justification here is that we're trying 00:16:28.770 --> 00:16:30.970 align:start position:0% justification here is that we're trying to<00:16:29.040> kind<00:16:29.190> of<00:16:29.370> but<00:16:30.180> there's<00:16:30.660> two<00:16:30.930> different 00:16:30.970 --> 00:16:30.980 align:start position:0% to kind of but there's two different 00:16:30.980 --> 00:16:33.829 align:start position:0% to kind of but there's two different kind<00:16:31.980> of<00:16:32.100> constraints<00:16:32.640> that<00:16:32.670> we<00:16:32.880> have<00:16:33.089> one<00:16:33.810> of 00:16:33.829 --> 00:16:33.839 align:start position:0% kind of constraints that we have one of 00:16:33.839 --> 00:16:35.600 align:start position:0% kind of constraints that we have one of the<00:16:33.990> constraints<00:16:34.830> is<00:16:34.980> the<00:16:35.130> load<00:16:35.370> on<00:16:35.580> the 00:16:35.600 --> 00:16:35.610 align:start position:0% the constraints is the load on the 00:16:35.610 --> 00:16:39.320 align:start position:0% the constraints is the load on the beacon<00:16:35.940> chain<00:16:36.180> so<00:16:37.050> we<00:16:37.260> want<00:16:37.520> like<00:16:38.520> the<00:16:39.089> higher 00:16:39.320 --> 00:16:39.330 align:start position:0% beacon chain so we want like the higher 00:16:39.330 --> 00:16:41.480 align:start position:0% beacon chain so we want like the higher the<00:16:39.630> shard<00:16:40.080> count<00:16:40.350> the<00:16:40.470> more<00:16:40.620> scalability<00:16:41.310> but 00:16:41.480 --> 00:16:41.490 align:start position:0% the shard count the more scalability but 00:16:41.490 --> 00:16:42.710 align:start position:0% the shard count the more scalability but on<00:16:41.610> the<00:16:41.730> other<00:16:41.820> hand<00:16:41.910> higher<00:16:42.360> the<00:16:42.540> showery 00:16:42.710 --> 00:16:42.720 align:start position:0% on the other hand higher the showery 00:16:42.720 --> 00:16:44.000 align:start position:0% on the other hand higher the showery take<00:16:42.900> out<00:16:42.960> the<00:16:43.050> more<00:16:43.200> cross<00:16:43.470> links<00:16:43.770> on<00:16:43.890> the 00:16:44.000 --> 00:16:44.010 align:start position:0% take out the more cross links on the 00:16:44.010 --> 00:16:46.910 align:start position:0% take out the more cross links on the beacon<00:16:44.250> chain<00:16:44.550> and<00:16:45.020> the<00:16:46.020> more<00:16:46.200> expensive<00:16:46.589> the 00:16:46.910 --> 00:16:46.920 align:start position:0% beacon chain and the more expensive the 00:16:46.920 --> 00:16:49.160 align:start position:0% beacon chain and the more expensive the beacon<00:16:47.190> chain<00:16:47.370> will<00:16:47.580> be<00:16:47.610> the<00:16:47.790> process<00:16:48.240> in<00:16:48.900> the 00:16:49.160 --> 00:16:49.170 align:start position:0% beacon chain will be the process in the 00:16:49.170 --> 00:16:51.530 align:start position:0% beacon chain will be the process in the other<00:16:49.370> constraints<00:16:50.370> that<00:16:50.400> we<00:16:50.670> have<00:16:50.910> is<00:16:51.210> just 00:16:51.530 --> 00:16:51.540 align:start position:0% other constraints that we have is just 00:16:51.540 --> 00:16:53.690 align:start position:0% other constraints that we have is just like<00:16:51.750> the<00:16:52.230> higher<00:16:52.500> the<00:16:52.830> total<00:16:53.190> throughput<00:16:53.490> of 00:16:53.690 --> 00:16:53.700 align:start position:0% like the higher the total throughput of 00:16:53.700 --> 00:16:55.550 align:start position:0% like the higher the total throughput of the<00:16:53.910> system<00:16:53.940> the<00:16:54.510> higher<00:16:54.750> the<00:16:55.080> harder<00:16:55.410> it<00:16:55.530> is 00:16:55.550 --> 00:16:55.560 align:start position:0% the system the higher the harder it is 00:16:55.560 --> 00:16:58.340 align:start position:0% the system the higher the harder it is to<00:16:55.680> be<00:16:56.070> like<00:16:56.310> to<00:16:56.790> be<00:16:56.910> a<00:16:56.940> block<00:16:57.210> Explorer<00:16:57.720> the 00:16:58.340 --> 00:16:58.350 align:start position:0% to be like to be a block Explorer the 00:16:58.350 --> 00:17:00.170 align:start position:0% to be like to be a block Explorer the higher<00:16:58.560> the<00:16:58.860> risk<00:16:59.040> that<00:16:59.220> some<00:16:59.610> historical 00:17:00.170 --> 00:17:00.180 align:start position:0% higher the risk that some historical 00:17:00.180 --> 00:17:01.880 align:start position:0% higher the risk that some historical data<00:17:00.240> will<00:17:00.630> eventually<00:17:01.140> just<00:17:01.380> end<00:17:01.589> up<00:17:01.680> being 00:17:01.880 --> 00:17:01.890 align:start position:0% data will eventually just end up being 00:17:01.890 --> 00:17:03.560 align:start position:0% data will eventually just end up being forgotten<00:17:02.190> completely<00:17:02.490> and<00:17:03.030> so<00:17:03.180> forth 00:17:03.560 --> 00:17:03.570 align:start position:0% forgotten completely and so forth 00:17:03.570 --> 00:17:07.550 align:start position:0% forgotten completely and so forth so<00:17:04.640> the<00:17:05.640> scalability<00:17:06.420> that<00:17:06.689> we<00:17:06.810> that<00:17:07.380> were 00:17:07.550 --> 00:17:07.560 align:start position:0% so the scalability that we that were 00:17:07.560 --> 00:17:09.500 align:start position:0% so the scalability that we that were expecting<00:17:08.280> like<00:17:08.579> the<00:17:08.819> data<00:17:09.000> throughput<00:17:09.270> that 00:17:09.500 --> 00:17:09.510 align:start position:0% expecting like the data throughput that 00:17:09.510 --> 00:17:12.079 align:start position:0% expecting like the data throughput that we're<00:17:09.600> expecting<00:17:09.900> the<00:17:10.199> number<00:17:10.470> though<00:17:11.089> like 00:17:12.079 --> 00:17:12.089 align:start position:0% we're expecting the number though like 00:17:12.089 --> 00:17:14.270 align:start position:0% we're expecting the number though like we've<00:17:12.240> committed<00:17:12.510> numbers<00:17:12.900> between<00:17:13.170> 1<00:17:13.860> to<00:17:14.040> 10 00:17:14.270 --> 00:17:14.280 align:start position:0% we've committed numbers between 1 to 10 00:17:14.280 --> 00:17:18.410 align:start position:0% we've committed numbers between 1 to 10 megabytes<00:17:14.760> per<00:17:14.970> second<00:17:15.720> and<00:17:16.520> that<00:17:17.520> seems<00:17:17.970> kind 00:17:18.410 --> 00:17:18.420 align:start position:0% megabytes per second and that seems kind 00:17:18.420 --> 00:17:21.800 align:start position:0% megabytes per second and that seems kind of<00:17:18.569> to<00:17:19.290> be<00:17:19.470> close<00:17:20.370> to<00:17:20.579> the<00:17:20.699> upper<00:17:21.420> limit<00:17:21.600> of 00:17:21.800 --> 00:17:21.810 align:start position:0% of to be close to the upper limit of 00:17:21.810 --> 00:17:23.480 align:start position:0% of to be close to the upper limit of people<00:17:22.110> of<00:17:22.170> like<00:17:22.650> what<00:17:22.829> people<00:17:23.010> are<00:17:23.250> fine<00:17:23.459> with 00:17:23.480 --> 00:17:23.490 align:start position:0% people of like what people are fine with 00:17:23.490 --> 00:17:25.850 align:start position:0% people of like what people are fine with so<00:17:23.850> far<00:17:24.120> and<00:17:24.810> for<00:17:24.870> the<00:17:25.199> vote<00:17:25.350> on<00:17:25.500> the<00:17:25.620> beacon 00:17:25.850 --> 00:17:25.860 align:start position:0% so far and for the vote on the beacon 00:17:25.860 --> 00:17:27.500 align:start position:0% so far and for the vote on the beacon chain<00:17:26.130> like<00:17:26.339> we've<00:17:26.459> done<00:17:26.640> numbers<00:17:27.150> and<00:17:27.420> it 00:17:27.500 --> 00:17:27.510 align:start position:0% chain like we've done numbers and it 00:17:27.510 --> 00:17:29.780 align:start position:0% chain like we've done numbers and it seems<00:17:27.780> like<00:17:28.079> beacon<00:17:28.860> chain<00:17:29.100> blocks<00:17:29.370> can<00:17:29.670> in 00:17:29.780 --> 00:17:29.790 align:start position:0% seems like beacon chain blocks can in 00:17:29.790 --> 00:17:32.120 align:start position:0% seems like beacon chain blocks can in the<00:17:29.880> worst<00:17:30.090> case<00:17:30.420> be<00:17:30.660> verified<00:17:31.260> in<00:17:31.560> like<00:17:31.830> about 00:17:32.120 --> 00:17:32.130 align:start position:0% the worst case be verified in like about 00:17:32.130 --> 00:17:37.820 align:start position:0% the worst case be verified in like about us<00:17:32.280> about<00:17:32.610> a<00:17:32.820> second<00:17:33.240> now<00:17:33.360> is<00:17:33.540> it<00:17:34.490> so<00:17:36.560> yeah<00:17:37.560> so 00:17:37.820 --> 00:17:37.830 align:start position:0% us about a second now is it so yeah so 00:17:37.830 --> 00:17:39.680 align:start position:0% us about a second now is it so yeah so once<00:17:38.070> again<00:17:38.220> it's<00:17:38.520> they<00:17:38.640> kind<00:17:38.880> of<00:17:39.000> like<00:17:39.240> that 00:17:39.680 --> 00:17:39.690 align:start position:0% once again it's they kind of like that 00:17:39.690 --> 00:17:42.860 align:start position:0% once again it's they kind of like that much<00:17:39.960> but<00:17:40.140> not<00:17:40.350> more<00:17:40.590> sort<00:17:40.890> of<00:17:40.950> thing<00:17:41.840> yeah<00:17:42.840> I 00:17:42.860 --> 00:17:42.870 align:start position:0% much but not more sort of thing yeah I 00:17:42.870 --> 00:17:43.850 align:start position:0% much but not more sort of thing yeah I think<00:17:42.960> there<00:17:43.170> was<00:17:43.260> like<00:17:43.410> four<00:17:43.679> million 00:17:43.850 --> 00:17:43.860 align:start position:0% think there was like four million 00:17:43.860 --> 00:17:45.890 align:start position:0% think there was like four million validated<00:17:44.460> were<00:17:44.610> starting<00:17:44.940> to<00:17:44.970> encroach<00:17:45.450> over 00:17:45.890 --> 00:17:45.900 align:start position:0% validated were starting to encroach over 00:17:45.900 --> 00:17:50.570 align:start position:0% validated were starting to encroach over a<00:17:45.929> second<00:17:46.410> so<00:17:47.929> yeah<00:17:48.929> I<00:17:49.650> personally<00:17:50.160> want<00:17:50.400> to<00:17:50.460> be 00:17:50.570 --> 00:17:50.580 align:start position:0% a second so yeah I personally want to be 00:17:50.580 --> 00:17:51.860 align:start position:0% a second so yeah I personally want to be concerned<00:17:50.910> want<00:17:51.179> to<00:17:51.240> be<00:17:51.330> conservative<00:17:51.720> or 00:17:51.860 --> 00:17:51.870 align:start position:0% concerned want to be conservative or 00:17:51.870 --> 00:17:53.690 align:start position:0% concerned want to be conservative or speaking<00:17:52.170> to<00:17:52.230> a<00:17:52.350> number<00:17:52.650> so<00:17:52.800> I<00:17:52.830> kind<00:17:53.130> wants<00:17:53.400> to 00:17:53.690 --> 00:17:53.700 align:start position:0% speaking to a number so I kind wants to 00:17:53.700 --> 00:17:56.180 align:start position:0% speaking to a number so I kind wants to I<00:17:53.750> personally<00:17:54.750> really<00:17:55.380> wants<00:17:55.650> to<00:17:55.770> avoid<00:17:56.010> the 00:17:56.180 --> 00:17:56.190 align:start position:0% I personally really wants to avoid the 00:17:56.190 --> 00:17:58.730 align:start position:0% I personally really wants to avoid the mistake<00:17:56.550> that<00:17:56.820> we<00:17:56.970> made<00:17:57.210> of<00:17:57.450> like<00:17:57.690> in<00:17:58.200> eighth 00:17:58.730 --> 00:17:58.740 align:start position:0% mistake that we made of like in eighth 00:17:58.740 --> 00:18:00.950 align:start position:0% mistake that we made of like in eighth one<00:17:59.070> where<00:17:59.430> because<00:18:00.000> the<00:18:00.180> chain<00:18:00.450> was<00:18:00.690> heavy 00:18:00.950 --> 00:18:00.960 align:start position:0% one where because the chain was heavy 00:18:00.960 --> 00:18:02.810 align:start position:0% one where because the chain was heavy like<00:18:01.320> Sophie<00:18:01.710> people<00:18:02.040> wants<00:18:02.310> to<00:18:02.340> run<00:18:02.550> a<00:18:02.580> note 00:18:02.810 --> 00:18:02.820 align:start position:0% like Sophie people wants to run a note 00:18:02.820 --> 00:18:04.820 align:start position:0% like Sophie people wants to run a note like<00:18:03.090> I<00:18:03.120> would<00:18:03.390> prefer<00:18:03.570> a<00:18:03.720> beacon<00:18:04.200> chain<00:18:04.470> note 00:18:04.820 --> 00:18:04.830 align:start position:0% like I would prefer a beacon chain note 00:18:04.830 --> 00:18:07.100 align:start position:0% like I would prefer a beacon chain note to<00:18:05.010> be<00:18:05.130> just<00:18:05.430> a<00:18:05.550> thing<00:18:05.730> that<00:18:05.940> you<00:18:06.030> would<00:18:06.210> run<00:18:06.870> by 00:18:07.100 --> 00:18:07.110 align:start position:0% to be just a thing that you would run by 00:18:07.110 --> 00:18:09.050 align:start position:0% to be just a thing that you would run by default<00:18:07.530> rather<00:18:07.860> than<00:18:08.130> like<00:18:08.400> running<00:18:08.790> only 00:18:09.050 --> 00:18:09.060 align:start position:0% default rather than like running only 00:18:09.060 --> 00:18:10.790 align:start position:0% default rather than like running only what<00:18:09.450> you<00:18:09.540> need<00:18:09.750> it<00:18:09.900> and<00:18:10.080> that<00:18:10.590> does 00:18:10.790 --> 00:18:10.800 align:start position:0% what you need it and that does 00:18:10.800 --> 00:18:13.190 align:start position:0% what you need it and that does necessitate<00:18:11.550> kind<00:18:11.790> of<00:18:11.880> fairly<00:18:12.120> like<00:18:12.510> strange 00:18:13.190 --> 00:18:13.200 align:start position:0% necessitate kind of fairly like strange 00:18:13.200 --> 00:18:15.470 align:start position:0% necessitate kind of fairly like strange it<00:18:13.350> performance<00:18:13.740> requirements<00:18:14.490> yeah<00:18:15.240> I<00:18:15.270> agree 00:18:15.470 --> 00:18:15.480 align:start position:0% it performance requirements yeah I agree 00:18:15.480 --> 00:18:18.520 align:start position:0% it performance requirements yeah I agree things<00:18:15.900> are<00:18:16.050> the<00:18:16.110> faster<00:18:16.500> harder<00:18:16.680> does<00:18:17.040> to<00:18:17.310> I 00:18:18.520 --> 00:18:18.530 align:start position:0% things are the faster harder does to I 00:18:18.530 --> 00:18:20.780 align:start position:0% things are the faster harder does to I mean<00:18:19.530> on<00:18:19.650> the<00:18:19.770> concern<00:18:20.160> that<00:18:20.370> that<00:18:20.400> won't<00:18:20.670> be 00:18:20.780 --> 00:18:20.790 align:start position:0% mean on the concern that that won't be 00:18:20.790 --> 00:18:22.690 align:start position:0% mean on the concern that that won't be enough<00:18:21.000> validators<00:18:21.570> to<00:18:21.690> start<00:18:21.960> with<00:18:22.170> we're 00:18:22.690 --> 00:18:22.700 align:start position:0% enough validators to start with we're 00:18:22.700 --> 00:18:25.490 align:start position:0% enough validators to start with we're essentially<00:18:23.700> handling<00:18:24.210> that<00:18:24.390> by<00:18:24.690> only<00:18:25.140> doing 00:18:25.490 --> 00:18:25.500 align:start position:0% essentially handling that by only doing 00:18:25.500 --> 00:18:27.290 align:start position:0% essentially handling that by only doing the<00:18:25.680> Genesis<00:18:26.310> once<00:18:26.610> we<00:18:26.760> have<00:18:26.880> sufficient 00:18:27.290 --> 00:18:27.300 align:start position:0% the Genesis once we have sufficient 00:18:27.300 --> 00:18:29.450 align:start position:0% the Genesis once we have sufficient validators<00:18:27.840> so<00:18:28.410> will<00:18:28.590> the<00:18:28.860> current<00:18:29.160> numbers 00:18:29.450 --> 00:18:29.460 align:start position:0% validators so will the current numbers 00:18:29.460 --> 00:18:33.490 align:start position:0% validators so will the current numbers are<00:18:30.260> 65,000<00:18:31.260> validators<00:18:31.800> to<00:18:32.160> Megan<00:18:32.430> if 00:18:33.490 --> 00:18:33.500 align:start position:0% are 65,000 validators to Megan if 00:18:33.500 --> 00:18:35.960 align:start position:0% are 65,000 validators to Megan if another<00:18:34.500> idea<00:18:34.830> that<00:18:34.860> we're<00:18:35.220> considering<00:18:35.580> is 00:18:35.960 --> 00:18:35.970 align:start position:0% another idea that we're considering is 00:18:35.970 --> 00:18:39.140 align:start position:0% another idea that we're considering is that<00:18:36.210> even<00:18:36.770> even<00:18:37.770> if<00:18:38.040> we<00:18:38.190> go<00:18:38.430> four<00:18:38.730> thousand 00:18:39.140 --> 00:18:39.150 align:start position:0% that even even if we go four thousand 00:18:39.150 --> 00:18:42.320 align:start position:0% that even even if we go four thousand shots<00:18:39.360> in<00:18:39.570> the<00:18:39.660> very<00:18:39.840> long<00:18:39.990> term<00:18:40.760> we<00:18:41.760> could<00:18:41.940> you 00:18:42.320 --> 00:18:42.330 align:start position:0% shots in the very long term we could you 00:18:42.330 --> 00:18:45.500 align:start position:0% shots in the very long term we could you know<00:18:42.390> we<00:18:42.480> could<00:18:42.690> slowly<00:18:44.330> enable<00:18:45.330> them 00:18:45.500 --> 00:18:45.510 align:start position:0% know we could slowly enable them 00:18:45.510 --> 00:18:47.720 align:start position:0% know we could slowly enable them ratcheted<00:18:46.050> up<00:18:46.200> so<00:18:46.470> start<00:18:46.800> maybe<00:18:46.980> with<00:18:47.100> sixty 00:18:47.720 --> 00:18:47.730 align:start position:0% ratcheted up so start maybe with sixty 00:18:47.730 --> 00:18:50.270 align:start position:0% ratcheted up so start maybe with sixty four<00:18:47.910> shots<00:18:48.180> and<00:18:48.420> then<00:18:48.540> over<00:18:48.930> time<00:18:49.170> have<00:18:50.160> it 00:18:50.270 --> 00:18:50.280 align:start position:0% four shots and then over time have it 00:18:50.280 --> 00:18:51.650 align:start position:0% four shots and then over time have it increased<00:18:50.580> because<00:18:50.730> at<00:18:50.970> the<00:18:51.060> very<00:18:51.090> beginning 00:18:51.650 --> 00:18:51.660 align:start position:0% increased because at the very beginning 00:18:51.660 --> 00:18:53.480 align:start position:0% increased because at the very beginning there's<00:18:51.870> gonna<00:18:51.960> be<00:18:52.140> very<00:18:52.320> little<00:18:52.590> activity 00:18:53.480 --> 00:18:53.490 align:start position:0% there's gonna be very little activity 00:18:53.490 --> 00:18:58.870 align:start position:0% there's gonna be very little activity and<00:18:53.790> it<00:18:54.720> might<00:18:54.900> be<00:18:55.050> worth<00:18:56.750> using<00:18:57.750> less<00:18:58.050> shots 00:18:58.870 --> 00:18:58.880 align:start position:0% and it might be worth using less shots 00:18:58.880 --> 00:19:02.360 align:start position:0% and it might be worth using less shots yeah<00:18:59.880> speaking<00:19:00.300> of<00:19:00.480> block<00:19:01.350> times<00:19:01.650> or<00:19:02.010> a 00:19:02.360 --> 00:19:02.370 align:start position:0% yeah speaking of block times or a 00:19:02.370 --> 00:19:05.480 align:start position:0% yeah speaking of block times or a process<00:19:02.820> block<00:19:03.120> processing<00:19:04.020> times<00:19:04.230> it's<00:19:04.500> it's 00:19:05.480 --> 00:19:05.490 align:start position:0% process block processing times it's it's 00:19:05.490 --> 00:19:07.010 align:start position:0% process block processing times it's it's important<00:19:05.880> to<00:19:06.000> remember<00:19:06.210> there<00:19:06.480> are<00:19:06.540> cases 00:19:07.010 --> 00:19:07.020 align:start position:0% important to remember there are cases 00:19:07.020 --> 00:19:08.720 align:start position:0% important to remember there are cases where<00:19:07.350> we<00:19:07.380> have<00:19:07.650> to<00:19:07.680> process<00:19:08.010> blocks<00:19:08.460> which 00:19:08.720 --> 00:19:08.730 align:start position:0% where we have to process blocks which 00:19:08.730 --> 00:19:10.760 align:start position:0% where we have to process blocks which are<00:19:08.910> not<00:19:09.060> necessarily<00:19:09.900> good<00:19:10.050> ones<00:19:10.260> that<00:19:10.590> might 00:19:10.760 --> 00:19:10.770 align:start position:0% are not necessarily good ones that might 00:19:10.770 --> 00:19:13.130 align:start position:0% are not necessarily good ones that might be<00:19:10.800> spammed<00:19:11.220> might<00:19:11.610> be<00:19:12.140> maliciously 00:19:13.130 --> 00:19:13.140 align:start position:0% be spammed might be maliciously 00:19:13.140 --> 00:19:16.340 align:start position:0% be spammed might be maliciously constructed<00:19:13.890> that<00:19:14.220> takes<00:19:14.460> time<00:19:14.730> away<00:19:14.960> so<00:19:15.960> we 00:19:16.340 --> 00:19:16.350 align:start position:0% constructed that takes time away so we 00:19:16.350 --> 00:19:18.520 align:start position:0% constructed that takes time away so we need<00:19:16.470> to<00:19:16.650> have<00:19:16.770> a<00:19:16.830> little<00:19:17.100> bit<00:19:17.190> of<00:19:17.220> a<00:19:17.370> buffer 00:19:18.520 --> 00:19:18.530 align:start position:0% need to have a little bit of a buffer 00:19:18.530 --> 00:19:21.700 align:start position:0% need to have a little bit of a buffer and<00:19:19.530> that<00:19:19.560> also<00:19:20.310> affects<00:19:20.700> the<00:19:20.940> way<00:19:21.090> that 00:19:21.700 --> 00:19:21.710 align:start position:0% and that also affects the way that 00:19:21.710 --> 00:19:24.590 align:start position:0% and that also affects the way that messages<00:19:22.710> propagate<00:19:23.220> in<00:19:23.340> the<00:19:23.460> network<00:19:23.820> so 00:19:24.590 --> 00:19:24.600 align:start position:0% messages propagate in the network so 00:19:24.600 --> 00:19:28.340 align:start position:0% messages propagate in the network so we're<00:19:24.750> using<00:19:25.580> an<00:19:26.580> epidemic<00:19:27.090> network<00:19:27.450> which 00:19:28.340 --> 00:19:28.350 align:start position:0% we're using an epidemic network which 00:19:28.350 --> 00:19:30.230 align:start position:0% we're using an epidemic network which basically<00:19:28.740> means<00:19:29.040> that<00:19:29.160> all<00:19:29.760> the<00:19:29.940> data<00:19:30.120> is 00:19:30.230 --> 00:19:30.240 align:start position:0% basically means that all the data is 00:19:30.240 --> 00:19:32.780 align:start position:0% basically means that all the data is replicated<00:19:30.450> all<00:19:30.960> over<00:19:31.230> the<00:19:31.320> network<00:19:31.680> and<00:19:31.890> the 00:19:32.780 --> 00:19:32.790 align:start position:0% replicated all over the network and the 00:19:32.790 --> 00:19:35.150 align:start position:0% replicated all over the network and the longer<00:19:33.210> it<00:19:33.330> takes<00:19:33.360> to<00:19:33.630> process<00:19:33.870> or<00:19:34.440> the<00:19:34.860> longer 00:19:35.150 --> 00:19:35.160 align:start position:0% longer it takes to process or the longer 00:19:35.160 --> 00:19:39.530 align:start position:0% longer it takes to process or the longer full<00:19:35.580> block<00:19:36.510> processing<00:19:37.410> takes<00:19:37.790> the<00:19:38.790> less 00:19:39.530 --> 00:19:39.540 align:start position:0% full block processing takes the less 00:19:39.540 --> 00:19:41.120 align:start position:0% full block processing takes the less validation<00:19:40.320> we<00:19:40.440> can<00:19:40.620> do<00:19:40.740> ahead<00:19:40.860> of<00:19:41.010> time 00:19:41.120 --> 00:19:41.130 align:start position:0% validation we can do ahead of time 00:19:41.130 --> 00:19:44.420 align:start position:0% validation we can do ahead of time meaning<00:19:41.580> that<00:19:41.700> the<00:19:42.030> more<00:19:43.010> risk<00:19:44.010> there<00:19:44.280> is<00:19:44.340> that 00:19:44.420 --> 00:19:44.430 align:start position:0% meaning that the more risk there is that 00:19:44.430 --> 00:19:46.100 align:start position:0% meaning that the more risk there is that the<00:19:44.700> data<00:19:44.910> that<00:19:45.270> the<00:19:45.420> network<00:19:45.810> will<00:19:45.990> be 00:19:46.100 --> 00:19:46.110 align:start position:0% the data that the network will be 00:19:46.110 --> 00:19:48.500 align:start position:0% the data that the network will be flooded<00:19:46.440> by<00:19:46.560> bad<00:19:46.770> data<00:19:47.010> or<00:19:47.370> that<00:19:47.790> it<00:19:48.210> will<00:19:48.330> be 00:19:48.500 --> 00:19:48.510 align:start position:0% flooded by bad data or that it will be 00:19:48.510 --> 00:19:51.410 align:start position:0% flooded by bad data or that it will be slow<00:19:48.750> either<00:19:49.410> of<00:19:49.620> those<00:19:49.770> two<00:19:50.040> right<00:19:50.250> so<00:19:50.520> so 00:19:51.410 --> 00:19:51.420 align:start position:0% slow either of those two right so so 00:19:51.420 --> 00:19:53.450 align:start position:0% slow either of those two right so so there's<00:19:51.570> also<00:19:51.780> that<00:19:51.960> argument<00:19:52.440> that<00:19:52.590> if<00:19:53.220> we 00:19:53.450 --> 00:19:53.460 align:start position:0% there's also that argument that if we 00:19:53.460 --> 00:19:55.610 align:start position:0% there's also that argument that if we can<00:19:53.610> do<00:19:53.730> more<00:19:53.760> good<00:19:54.030> validation<00:19:54.600> upfront<00:19:55.200> and 00:19:55.610 --> 00:19:55.620 align:start position:0% can do more good validation upfront and 00:19:55.620 --> 00:19:59.090 align:start position:0% can do more good validation upfront and still<00:19:56.310> maintain<00:19:56.790> low<00:19:57.150> latencies<00:19:57.920> we<00:19:58.920> also 00:19:59.090 --> 00:19:59.100 align:start position:0% still maintain low latencies we also 00:19:59.100 --> 00:20:01.520 align:start position:0% still maintain low latencies we also gain<00:19:59.430> in<00:19:59.670> other<00:19:59.820> parts<00:20:00.690> of<00:20:00.810> the<00:20:00.960> system<00:20:01.170> as<00:20:01.500> a 00:20:01.520 --> 00:20:01.530 align:start position:0% gain in other parts of the system as a 00:20:01.530 --> 00:20:05.269 align:start position:0% gain in other parts of the system as a whole 00:20:05.269 --> 00:20:05.279 align:start position:0% 00:20:05.279 --> 00:20:08.039 align:start position:0% yes<00:20:06.279> I'm<00:20:06.549> wondering<00:20:07.059> what<00:20:07.179> the<00:20:07.210> plan<00:20:07.750> is<00:20:07.929> in 00:20:08.039 --> 00:20:08.049 align:start position:0% yes I'm wondering what the plan is in 00:20:08.049 --> 00:20:10.049 align:start position:0% yes I'm wondering what the plan is in general<00:20:08.259> terms<00:20:08.500> for<00:20:08.799> handling<00:20:09.009> of<00:20:09.190> VRC<00:20:09.639> 20 00:20:10.049 --> 00:20:10.059 align:start position:0% general terms for handling of VRC 20 00:20:10.059 --> 00:20:12.509 align:start position:0% general terms for handling of VRC 20 assets<00:20:10.389> in<00:20:11.139> particular<00:20:11.649> transfer<00:20:12.100> functions 00:20:12.509 --> 00:20:12.519 align:start position:0% assets in particular transfer functions 00:20:12.519 --> 00:20:14.310 align:start position:0% assets in particular transfer functions as<00:20:12.850> a<00:20:12.909> developer<00:20:13.419> it's<00:20:13.509> somewhat<00:20:13.899> difficult 00:20:14.310 --> 00:20:14.320 align:start position:0% as a developer it's somewhat difficult 00:20:14.320 --> 00:20:15.899 align:start position:0% as a developer it's somewhat difficult from<00:20:14.740> user<00:20:14.950> experience<00:20:15.370> standpoint<00:20:15.549> and 00:20:15.899 --> 00:20:15.909 align:start position:0% from user experience standpoint and 00:20:15.909 --> 00:20:18.990 align:start position:0% from user experience standpoint and there's<00:20:16.299> been<00:20:16.450> many<00:20:16.600> proposals<00:20:16.919> er<00:20:17.919> c-23<00:20:18.820> for 00:20:18.990 --> 00:20:19.000 align:start position:0% there's been many proposals er c-23 for 00:20:19.000 --> 00:20:21.629 align:start position:0% there's been many proposals er c-23 for instance<00:20:19.360> as<00:20:19.600> an<00:20:20.080> interesting<00:20:20.500> proposal<00:20:20.649> but 00:20:21.629 --> 00:20:21.639 align:start position:0% instance as an interesting proposal but 00:20:21.639 --> 00:20:23.490 align:start position:0% instance as an interesting proposal but as<00:20:21.730> we<00:20:21.880> transition<00:20:22.450> to<00:20:22.570> e<00:20:22.630> 2.0<00:20:23.169> I'm<00:20:23.230> curious 00:20:23.490 --> 00:20:23.500 align:start position:0% as we transition to e 2.0 I'm curious 00:20:23.500 --> 00:20:25.710 align:start position:0% as we transition to e 2.0 I'm curious what<00:20:23.740> the<00:20:23.860> general<00:20:24.220> plan<00:20:24.850> is<00:20:24.880> for<00:20:25.240> handling 00:20:25.710 --> 00:20:25.720 align:start position:0% what the general plan is for handling 00:20:25.720 --> 00:20:26.850 align:start position:0% what the general plan is for handling those<00:20:25.899> assets<00:20:26.289> because<00:20:26.470> there's<00:20:26.649> just 00:20:26.850 --> 00:20:26.860 align:start position:0% those assets because there's just 00:20:26.860 --> 00:20:28.769 align:start position:0% those assets because there's just hundreds<00:20:27.490> of<00:20:27.610> whom<00:20:27.730> just<00:20:27.759> migrating<00:20:28.539> them<00:20:28.630> to 00:20:28.769 --> 00:20:28.779 align:start position:0% hundreds of whom just migrating them to 00:20:28.779 --> 00:20:30.149 align:start position:0% hundreds of whom just migrating them to two-threes<00:20:29.380> and<00:20:29.559> it<00:20:29.649> sort<00:20:29.799> of<00:20:29.830> feasible 00:20:30.149 --> 00:20:30.159 align:start position:0% two-threes and it sort of feasible 00:20:30.159 --> 00:20:33.450 align:start position:0% two-threes and it sort of feasible curious<00:20:30.940> your<00:20:31.029> thoughts<00:20:31.210> so<00:20:32.340> kind<00:20:33.340> of 00:20:33.450 --> 00:20:33.460 align:start position:0% curious your thoughts so kind of 00:20:33.460 --> 00:20:35.399 align:start position:0% curious your thoughts so kind of unrelated<00:20:34.210> to<00:20:34.389> the<00:20:34.480> whole<00:20:34.630> transfer<00:20:35.169> from 00:20:35.399 --> 00:20:35.409 align:start position:0% unrelated to the whole transfer from 00:20:35.409 --> 00:20:37.440 align:start position:0% unrelated to the whole transfer from thing<00:20:35.830> which<00:20:36.039> I<00:20:36.220> agree<00:20:36.490> needs<00:20:36.610> to<00:20:36.850> be<00:20:36.970> reformed 00:20:37.440 --> 00:20:37.450 align:start position:0% thing which I agree needs to be reformed 00:20:37.450 --> 00:20:40.379 align:start position:0% thing which I agree needs to be reformed somehow<00:20:37.870> another<00:20:38.710> issue<00:20:39.129> another<00:20:39.820> reason<00:20:40.269> why 00:20:40.379 --> 00:20:40.389 align:start position:0% somehow another issue another reason why 00:20:40.389 --> 00:20:42.269 align:start position:0% somehow another issue another reason why things<00:20:40.720> need<00:20:40.899> to<00:20:40.929> be<00:20:41.049> reformed<00:20:41.470> anyway<00:20:42.009> is 00:20:42.269 --> 00:20:42.279 align:start position:0% things need to be reformed anyway is 00:20:42.279 --> 00:20:44.669 align:start position:0% things need to be reformed anyway is that<00:20:42.690> assets<00:20:43.690> are<00:20:43.899> probably<00:20:44.259> the<00:20:44.470> major 00:20:44.669 --> 00:20:44.679 align:start position:0% that assets are probably the major 00:20:44.679 --> 00:20:47.039 align:start position:0% that assets are probably the major category<00:20:45.490> of<00:20:45.549> application<00:20:46.330> that<00:20:46.539> we<00:20:46.629> expect 00:20:47.039 --> 00:20:47.049 align:start position:0% category of application that we expect 00:20:47.049 --> 00:20:49.769 align:start position:0% category of application that we expect like<00:20:47.259> in<00:20:47.830> any<00:20:48.519> particular<00:20:48.730> token<00:20:49.330> will<00:20:49.659> need 00:20:49.769 --> 00:20:49.779 align:start position:0% like in any particular token will need 00:20:49.779 --> 00:20:52.169 align:start position:0% like in any particular token will need to<00:20:49.899> be<00:20:50.019> accessible<00:20:50.440> in<00:20:50.620> all<00:20:50.710> shards<00:20:51.129> like<00:20:51.879> most 00:20:52.169 --> 00:20:52.179 align:start position:0% to be accessible in all shards like most 00:20:52.179 --> 00:20:54.480 align:start position:0% to be accessible in all shards like most applications<00:20:52.990> agree<00:20:53.470> like<00:20:53.529> realistically 00:20:54.480 --> 00:20:54.490 align:start position:0% applications agree like realistically 00:20:54.490 --> 00:20:55.919 align:start position:0% applications agree like realistically unless<00:20:54.820> you're<00:20:55.000> in<00:20:55.090> the<00:20:55.210> top<00:20:55.360> 10<00:20:55.629> you<00:20:55.809> could 00:20:55.919 --> 00:20:55.929 align:start position:0% unless you're in the top 10 you could 00:20:55.929 --> 00:20:57.509 align:start position:0% unless you're in the top 10 you could just<00:20:56.139> live<00:20:56.350> inside<00:20:56.590> of<00:20:56.769> one<00:20:56.950> shard<00:20:57.220> and<00:20:57.370> you 00:20:57.509 --> 00:20:57.519 align:start position:0% just live inside of one shard and you 00:20:57.519 --> 00:20:58.860 align:start position:0% just live inside of one shard and you could<00:20:57.639> expect<00:20:57.970> people<00:20:58.149> to<00:20:58.299> just<00:20:58.389> move<00:20:58.659> their 00:20:58.860 --> 00:20:58.870 align:start position:0% could expect people to just move their 00:20:58.870 --> 00:21:00.480 align:start position:0% could expect people to just move their points<00:20:59.169> to<00:20:59.230> your<00:20:59.320> shard<00:20:59.590> do<00:20:59.740> stuff<00:21:00.009> inside<00:21:00.370> of 00:21:00.480 --> 00:21:00.490 align:start position:0% points to your shard do stuff inside of 00:21:00.490 --> 00:21:01.980 align:start position:0% points to your shard do stuff inside of your<00:21:00.610> application<00:21:00.759> then<00:21:01.389> go<00:21:01.539> somewhere<00:21:01.720> else 00:21:01.980 --> 00:21:01.990 align:start position:0% your application then go somewhere else 00:21:01.990 --> 00:21:04.619 align:start position:0% your application then go somewhere else but<00:21:02.769> tokens<00:21:03.250> need<00:21:03.519> to<00:21:03.669> be<00:21:03.789> able<00:21:03.850> to<00:21:04.000> move<00:21:04.269> to<00:21:04.450> be 00:21:04.619 --> 00:21:04.629 align:start position:0% but tokens need to be able to move to be 00:21:04.629 --> 00:21:07.860 align:start position:0% but tokens need to be able to move to be moved<00:21:04.870> around<00:21:05.019> everywhere<00:21:05.620> and<00:21:05.889> so<00:21:06.370> like<00:21:07.330> the 00:21:07.860 --> 00:21:07.870 align:start position:0% moved around everywhere and so like the 00:21:07.870 --> 00:21:10.740 align:start position:0% moved around everywhere and so like the idea<00:21:08.289> of<00:21:08.350> a<00:21:08.620> token<00:21:09.100> as<00:21:09.340> being<00:21:09.820> a<00:21:10.059> balance<00:21:10.539> of 00:21:10.740 --> 00:21:10.750 align:start position:0% idea of a token as being a balance of 00:21:10.750 --> 00:21:12.749 align:start position:0% idea of a token as being a balance of one<00:21:11.080> particular<00:21:11.259> model<00:21:11.860> with<00:21:11.980> a<00:21:12.009> contract<00:21:12.549> is 00:21:12.749 --> 00:21:12.759 align:start position:0% one particular model with a contract is 00:21:12.759 --> 00:21:14.100 align:start position:0% one particular model with a contract is not<00:21:12.879> something<00:21:13.299> that<00:21:13.330> can<00:21:13.539> really<00:21:13.690> survive 00:21:14.100 --> 00:21:14.110 align:start position:0% not something that can really survive 00:21:14.110 --> 00:21:16.619 align:start position:0% not something that can really survive and<00:21:14.409> so<00:21:14.529> you'd<00:21:14.740> expect<00:21:15.159> like<00:21:15.250> token<00:21:16.179> Holdings 00:21:16.619 --> 00:21:16.629 align:start position:0% and so you'd expect like token Holdings 00:21:16.629 --> 00:21:19.169 align:start position:0% and so you'd expect like token Holdings to<00:21:16.870> themselves<00:21:17.379> be<00:21:17.980> more<00:21:18.250> like<00:21:18.490> individual 00:21:19.169 --> 00:21:19.179 align:start position:0% to themselves be more like individual 00:21:19.179 --> 00:21:22.680 align:start position:0% to themselves be more like individual contracts<00:21:19.809> and<00:21:20.730> when<00:21:21.730> like<00:21:22.090> when<00:21:22.509> that 00:21:22.680 --> 00:21:22.690 align:start position:0% contracts and when like when that 00:21:22.690 --> 00:21:26.279 align:start position:0% contracts and when like when that happens<00:21:23.009> you're<00:21:24.009> pretty<00:21:24.279> much<00:21:24.490> like<00:21:25.179> it's<00:21:26.049> an 00:21:26.279 --> 00:21:26.289 align:start position:0% happens you're pretty much like it's an 00:21:26.289 --> 00:21:28.200 align:start position:0% happens you're pretty much like it's an opportunity<00:21:26.980> to<00:21:27.220> kind<00:21:27.399> of<00:21:27.580> reform<00:21:28.000> other 00:21:28.200 --> 00:21:28.210 align:start position:0% opportunity to kind of reform other 00:21:28.210 --> 00:21:29.970 align:start position:0% opportunity to kind of reform other things<00:21:28.600> about<00:21:28.779> how<00:21:29.019> the<00:21:29.080> standard<00:21:29.529> works<00:21:29.769> as 00:21:29.970 --> 00:21:29.980 align:start position:0% things about how the standard works as 00:21:29.980 --> 00:21:36.180 align:start position:0% things about how the standard works as well<00:21:32.610> another<00:21:33.610> question<00:21:34.090> I<00:21:34.389> had<00:21:34.570> just<00:21:34.990> to<00:21:35.190> go 00:21:36.180 --> 00:21:36.190 align:start position:0% well another question I had just to go 00:21:36.190 --> 00:21:41.940 align:start position:0% well another question I had just to go back<00:21:36.220> to<00:21:36.370> Justin<00:21:39.750> you<00:21:40.750> you<00:21:41.110> just<00:21:41.440> a<00:21:41.620> minute<00:21:41.860> ago 00:21:41.940 --> 00:21:41.950 align:start position:0% back to Justin you you just a minute ago 00:21:41.950 --> 00:21:44.100 align:start position:0% back to Justin you you just a minute ago mentioned<00:21:42.399> that<00:21:42.610> it<00:21:42.759> could<00:21:43.000> start<00:21:43.330> with<00:21:43.480> 64 00:21:44.100 --> 00:21:44.110 align:start position:0% mentioned that it could start with 64 00:21:44.110 --> 00:21:46.350 align:start position:0% mentioned that it could start with 64 shards<00:21:44.500> previously<00:21:45.429> I<00:21:45.519> hadn't<00:21:45.789> heard<00:21:45.909> this<00:21:46.090> so 00:21:46.350 --> 00:21:46.360 align:start position:0% shards previously I hadn't heard this so 00:21:46.360 --> 00:21:48.090 align:start position:0% shards previously I hadn't heard this so can<00:21:46.690> you<00:21:46.779> expand<00:21:47.289> on<00:21:47.350> that<00:21:47.409> a<00:21:47.559> little<00:21:47.679> bit<00:21:47.889> more 00:21:48.090 --> 00:21:48.100 align:start position:0% can you expand on that a little bit more 00:21:48.100 --> 00:21:49.970 align:start position:0% can you expand on that a little bit more as<00:21:48.250> to<00:21:48.279> how<00:21:48.820> that<00:21:48.879> could<00:21:49.240> happen<00:21:49.389> because 00:21:49.970 --> 00:21:49.980 align:start position:0% as to how that could happen because 00:21:49.980 --> 00:21:52.619 align:start position:0% as to how that could happen because previously<00:21:50.980> the<00:21:51.639> response<00:21:51.970> was<00:21:52.120> that<00:21:52.179> it 00:21:52.619 --> 00:21:52.629 align:start position:0% previously the response was that it 00:21:52.629 --> 00:21:54.389 align:start position:0% previously the response was that it you'd<00:21:53.139> be<00:21:53.259> under<00:21:53.500> utilizing<00:21:53.919> it<00:21:54.100> but<00:21:54.220> is<00:21:54.309> that 00:21:54.389 --> 00:21:54.399 align:start position:0% you'd be under utilizing it but is that 00:21:54.399 --> 00:21:56.190 align:start position:0% you'd be under utilizing it but is that really<00:21:54.700> the<00:21:54.909> only<00:21:55.059> consideration<00:21:55.480> that<00:21:56.080> you'd 00:21:56.190 --> 00:21:56.200 align:start position:0% really the only consideration that you'd 00:21:56.200 --> 00:21:58.200 align:start position:0% really the only consideration that you'd be<00:21:56.320> under<00:21:56.830> utilizing<00:21:57.309> the<00:21:57.399> beacon<00:21:57.639> chain<00:21:57.850> the 00:21:58.200 --> 00:21:58.210 align:start position:0% be under utilizing the beacon chain the 00:21:58.210 --> 00:21:59.970 align:start position:0% be under utilizing the beacon chain the throughput<00:21:58.659> that<00:21:59.019> that's<00:21:59.350> made<00:21:59.500> available 00:21:59.970 --> 00:21:59.980 align:start position:0% throughput that that's made available 00:21:59.980 --> 00:22:01.769 align:start position:0% throughput that that's made available why<00:22:00.639> couldn't<00:22:01.059> we<00:22:01.179> start<00:22:01.419> with<00:22:01.570> the<00:22:01.629> lower 00:22:01.769 --> 00:22:01.779 align:start position:0% why couldn't we start with the lower 00:22:01.779 --> 00:22:03.659 align:start position:0% why couldn't we start with the lower number<00:22:02.019> and<00:22:02.139> then<00:22:02.259> scale<00:22:02.529> up<00:22:02.679> what<00:22:03.429> you<00:22:03.519> have 00:22:03.659 --> 00:22:03.669 align:start position:0% number and then scale up what you have 00:22:03.669 --> 00:22:05.789 align:start position:0% number and then scale up what you have like<00:22:03.879> validators<00:22:04.450> sitting<00:22:04.870> out<00:22:05.019> and<00:22:05.320> not 00:22:05.789 --> 00:22:05.799 align:start position:0% like validators sitting out and not 00:22:05.799 --> 00:22:09.600 align:start position:0% like validators sitting out and not really<00:22:06.299> activated<00:22:07.299> I<00:22:08.070> mean<00:22:09.070> the<00:22:09.159> validators 00:22:09.600 --> 00:22:09.610 align:start position:0% really activated I mean the validators 00:22:09.610 --> 00:22:11.700 align:start position:0% really activated I mean the validators do<00:22:09.759> all<00:22:09.970> sorts<00:22:10.210> of<00:22:10.269> things<00:22:10.330> one<00:22:11.289> of<00:22:11.320> them<00:22:11.559> is 00:22:11.700 --> 00:22:11.710 align:start position:0% do all sorts of things one of them is 00:22:11.710 --> 00:22:13.500 align:start position:0% do all sorts of things one of them is cross-linking<00:22:12.309> and<00:22:12.490> so<00:22:12.639> technically 00:22:13.500 --> 00:22:13.510 align:start position:0% cross-linking and so technically 00:22:13.510 --> 00:22:15.690 align:start position:0% cross-linking and so technically speaking<00:22:13.629> to<00:22:14.590> reduce<00:22:14.919> number<00:22:15.190> of<00:22:15.250> shards<00:22:15.610> is 00:22:15.690 --> 00:22:15.700 align:start position:0% speaking to reduce number of shards is 00:22:15.700 --> 00:22:16.890 align:start position:0% speaking to reduce number of shards is pretty<00:22:15.940> trivial<00:22:16.149> like 00:22:16.890 --> 00:22:16.900 align:start position:0% pretty trivial like 00:22:16.900 --> 00:22:19.530 align:start position:0% pretty trivial like when<00:22:17.380> they<00:22:17.530> do<00:22:17.590> the<00:22:17.800> crosslink<00:22:18.280> some<00:22:19.240> of<00:22:19.360> these 00:22:19.530 --> 00:22:19.540 align:start position:0% when they do the crosslink some of these 00:22:19.540 --> 00:22:21.390 align:start position:0% when they do the crosslink some of these cross-links<00:22:20.110> will<00:22:20.500> just<00:22:20.650> be<00:22:20.740> hard-coded<00:22:21.040> to 00:22:21.390 --> 00:22:21.400 align:start position:0% cross-links will just be hard-coded to 00:22:21.400 --> 00:22:24.480 align:start position:0% cross-links will just be hard-coded to zero<00:22:21.670> and<00:22:21.970> that<00:22:22.510> will<00:22:22.900> this<00:22:23.260> zero<00:22:23.559> hash<00:22:23.920> will 00:22:24.480 --> 00:22:24.490 align:start position:0% zero and that will this zero hash will 00:22:24.490 --> 00:22:26.190 align:start position:0% zero and that will this zero hash will mean<00:22:24.670> that<00:22:24.910> there's<00:22:25.330> no<00:22:25.510> data<00:22:25.750> flowing 00:22:26.190 --> 00:22:26.200 align:start position:0% mean that there's no data flowing 00:22:26.200 --> 00:22:30.390 align:start position:0% mean that there's no data flowing through<00:22:26.530> the<00:22:26.680> respective<00:22:27.430> shots<00:22:29.340> but<00:22:30.340> you 00:22:30.390 --> 00:22:30.400 align:start position:0% through the respective shots but you 00:22:30.400 --> 00:22:32.010 align:start position:0% through the respective shots but you know<00:22:30.610> these<00:22:30.880> validators<00:22:31.510> would<00:22:31.660> still<00:22:31.870> be 00:22:32.010 --> 00:22:32.020 align:start position:0% know these validators would still be 00:22:32.020 --> 00:22:33.630 align:start position:0% know these validators would still be providing<00:22:32.410> value<00:22:32.740> for<00:22:32.890> example<00:22:32.980> they'd<00:22:33.460> be 00:22:33.630 --> 00:22:33.640 align:start position:0% providing value for example they'd be 00:22:33.640 --> 00:22:35.370 align:start position:0% providing value for example they'd be contributing<00:22:34.240> towards<00:22:34.630> the<00:22:34.750> finality<00:22:35.020> of<00:22:35.320> the 00:22:35.370 --> 00:22:35.380 align:start position:0% contributing towards the finality of the 00:22:35.380 --> 00:22:36.750 align:start position:0% contributing towards the finality of the beacon<00:22:35.680> chain<00:22:35.890> and<00:22:36.160> all<00:22:36.430> sorts<00:22:36.640> of<00:22:36.670> other 00:22:36.750 --> 00:22:36.760 align:start position:0% beacon chain and all sorts of other 00:22:36.760 --> 00:22:41.130 align:start position:0% beacon chain and all sorts of other things<00:22:37.090> I<00:22:38.850> mean<00:22:39.850> one<00:22:40.059> one<00:22:40.390> good<00:22:40.420> reason<00:22:40.930> to 00:22:41.130 --> 00:22:41.140 align:start position:0% things I mean one one good reason to 00:22:41.140 --> 00:22:43.440 align:start position:0% things I mean one one good reason to start<00:22:41.500> with<00:22:41.710> lower<00:22:42.010> shots<00:22:42.400> is<00:22:42.730> in<00:22:43.270> lower 00:22:43.440 --> 00:22:43.450 align:start position:0% start with lower shots is in lower 00:22:43.450 --> 00:22:45.600 align:start position:0% start with lower shots is in lower counties<00:22:44.020> that<00:22:44.320> you<00:22:44.740> know<00:22:44.830> maybe<00:22:45.309> more 00:22:45.600 --> 00:22:45.610 align:start position:0% counties that you know maybe more 00:22:45.610 --> 00:22:47.370 align:start position:0% counties that you know maybe more network<00:22:46.059> stability<00:22:46.540> we<00:22:46.750> wouldn't<00:22:46.990> have<00:22:47.170> so 00:22:47.370 --> 00:22:47.380 align:start position:0% network stability we wouldn't have so 00:22:47.380 --> 00:22:50.640 align:start position:0% network stability we wouldn't have so many<00:22:47.559> short<00:22:48.130> subnets<00:22:49.120> that<00:22:50.080> that's<00:22:50.380> a<00:22:50.470> nice 00:22:50.640 --> 00:22:50.650 align:start position:0% many short subnets that that's a nice 00:22:50.650 --> 00:22:55.680 align:start position:0% many short subnets that that's a nice thing<00:22:50.920> was<00:22:52.350> also<00:22:53.350> it<00:22:53.470> allows<00:22:53.890> for<00:22:54.690> services 00:22:55.680 --> 00:22:55.690 align:start position:0% thing was also it allows for services 00:22:55.690 --> 00:22:57.450 align:start position:0% thing was also it allows for services like<00:22:55.929> like<00:22:56.170> block<00:22:56.410> explorers<00:22:56.950> to<00:22:57.130> give<00:22:57.280> them<00:22:57.400> a 00:22:57.450 --> 00:22:57.460 align:start position:0% like like block explorers to give them a 00:22:57.460 --> 00:23:00.060 align:start position:0% like like block explorers to give them a bit<00:22:57.580> of<00:22:57.670> breathing<00:22:57.910> space<00:22:58.090> to<00:22:58.960> ramp<00:22:59.440> up<00:22:59.620> to<00:22:59.860> to 00:23:00.060 --> 00:23:00.070 align:start position:0% bit of breathing space to ramp up to to 00:23:00.070 --> 00:23:03.450 align:start position:0% bit of breathing space to ramp up to to bigger<00:23:00.250> numbers<00:23:00.640> as<00:23:01.150> to<00:23:01.360> how<00:23:01.570> we<00:23:02.070> increase<00:23:03.070> to 00:23:03.450 --> 00:23:03.460 align:start position:0% bigger numbers as to how we increase to 00:23:03.460 --> 00:23:06.180 align:start position:0% bigger numbers as to how we increase to higher<00:23:04.179> number<00:23:04.540> of<00:23:04.570> shots<00:23:04.840> we<00:23:05.620> can<00:23:05.800> have<00:23:06.040> some 00:23:06.180 --> 00:23:06.190 align:start position:0% higher number of shots we can have some 00:23:06.190 --> 00:23:08.880 align:start position:0% higher number of shots we can have some sort<00:23:06.400> of<00:23:06.490> automatic<00:23:07.030> schedule<00:23:07.660> or<00:23:08.110> we<00:23:08.620> could 00:23:08.880 --> 00:23:08.890 align:start position:0% sort of automatic schedule or we could 00:23:08.890 --> 00:23:11.220 align:start position:0% sort of automatic schedule or we could kind<00:23:09.520> of<00:23:09.550> push<00:23:09.820> this<00:23:10.000> to<00:23:10.150> this<00:23:10.270> also<00:23:10.510> social 00:23:11.220 --> 00:23:11.230 align:start position:0% kind of push this to this also social 00:23:11.230 --> 00:23:14.940 align:start position:0% kind of push this to this also social consensus<00:23:11.710> layer<00:23:12.150> with<00:23:13.150> with<00:23:13.510> hot<00:23:13.690> folks<00:23:13.990> so 00:23:14.940 --> 00:23:14.950 align:start position:0% consensus layer with with hot folks so 00:23:14.950 --> 00:23:17.070 align:start position:0% consensus layer with with hot folks so this<00:23:15.370> is<00:23:15.550> a<00:23:15.580> possibility<00:23:16.240> that<00:23:16.450> it<00:23:16.870> could 00:23:17.070 --> 00:23:17.080 align:start position:0% this is a possibility that it could 00:23:17.080 --> 00:23:19.770 align:start position:0% this is a possibility that it could start<00:23:17.380> much<00:23:17.800> lower<00:23:18.160> yes<00:23:18.970> and<00:23:19.240> I<00:23:19.300> think<00:23:19.360> it's 00:23:19.770 --> 00:23:19.780 align:start position:0% start much lower yes and I think it's 00:23:19.780 --> 00:23:21.419 align:start position:0% start much lower yes and I think it's the<00:23:20.080> natural<00:23:20.290> thing<00:23:20.679> to<00:23:20.800> do<00:23:20.920> I<00:23:20.950> think<00:23:21.070> right 00:23:21.419 --> 00:23:21.429 align:start position:0% the natural thing to do I think right 00:23:21.429 --> 00:23:22.950 align:start position:0% the natural thing to do I think right yeah<00:23:21.700> yeah<00:23:21.880> because<00:23:21.970> I've<00:23:22.330> heard<00:23:22.690> for<00:23:22.870> many 00:23:22.950 --> 00:23:22.960 align:start position:0% yeah yeah because I've heard for many 00:23:22.960 --> 00:23:24.510 align:start position:0% yeah yeah because I've heard for many people<00:23:23.320> and<00:23:23.500> I'm<00:23:23.590> sympathetic<00:23:23.860> to<00:23:24.309> the<00:23:24.490> idea 00:23:24.510 --> 00:23:24.520 align:start position:0% people and I'm sympathetic to the idea 00:23:24.520 --> 00:23:29.549 align:start position:0% people and I'm sympathetic to the idea that<00:23:26.280> block<00:23:27.280> space<00:23:27.840> should<00:23:28.840> be<00:23:28.900> economically 00:23:29.549 --> 00:23:29.559 align:start position:0% that block space should be economically 00:23:29.559 --> 00:23:32.180 align:start position:0% that block space should be economically valued<00:23:30.040> or<00:23:30.250> it<00:23:30.490> has<00:23:30.820> economic<00:23:31.480> implications 00:23:32.180 --> 00:23:32.190 align:start position:0% valued or it has economic implications 00:23:32.190 --> 00:23:34.830 align:start position:0% valued or it has economic implications and<00:23:33.190> it<00:23:33.309> should<00:23:33.460> be<00:23:33.550> valued<00:23:33.820> highly<00:23:34.450> and<00:23:34.720> if 00:23:34.830 --> 00:23:34.840 align:start position:0% and it should be valued highly and if 00:23:34.840 --> 00:23:37.740 align:start position:0% and it should be valued highly and if you<00:23:34.929> have<00:23:35.110> a<00:23:35.520> and<00:23:36.520> a<00:23:36.790> bunt<00:23:36.970> overabundance<00:23:37.630> of 00:23:37.740 --> 00:23:37.750 align:start position:0% you have a and a bunt overabundance of 00:23:37.750 --> 00:23:39.960 align:start position:0% you have a and a bunt overabundance of it<00:23:37.900> then<00:23:38.140> you<00:23:38.260> end<00:23:38.410> up<00:23:38.850> devaluing<00:23:39.850> the 00:23:39.960 --> 00:23:39.970 align:start position:0% it then you end up devaluing the 00:23:39.970 --> 00:23:41.520 align:start position:0% it then you end up devaluing the transactions<00:23:40.480> that<00:23:40.570> are<00:23:40.690> contained<00:23:41.080> in<00:23:41.200> it<00:23:41.350> I 00:23:41.520 --> 00:23:41.530 align:start position:0% transactions that are contained in it I 00:23:41.530 --> 00:23:43.620 align:start position:0% transactions that are contained in it I mean<00:23:42.130> that's<00:23:42.309> a<00:23:42.340> good<00:23:42.490> point<00:23:42.670> if<00:23:43.030> we<00:23:43.240> have<00:23:43.360> few 00:23:43.620 --> 00:23:43.630 align:start position:0% mean that's a good point if we have few 00:23:43.630 --> 00:23:45.510 align:start position:0% mean that's a good point if we have few fewer<00:23:44.020> shots<00:23:44.260> in<00:23:44.590> music<00:23:44.920> that<00:23:45.010> we<00:23:45.130> can<00:23:45.280> really 00:23:45.510 --> 00:23:45.520 align:start position:0% fewer shots in music that we can really 00:23:45.520 --> 00:23:48.480 align:start position:0% fewer shots in music that we can really test<00:23:46.000> the<00:23:46.720> new<00:23:46.900> you<00:23:47.530> know<00:23:47.620> gas<00:23:47.830> market<00:23:48.309> with 00:23:48.480 --> 00:23:48.490 align:start position:0% test the new you know gas market with 00:23:48.490 --> 00:23:51.720 align:start position:0% test the new you know gas market with VIP<00:23:48.760> one<00:23:49.179> one<00:23:49.330> five<00:23:50.170> nine<00:23:50.429> which<00:23:51.429> by<00:23:51.580> the<00:23:51.640> way 00:23:51.720 --> 00:23:51.730 align:start position:0% VIP one one five nine which by the way 00:23:51.730 --> 00:23:53.760 align:start position:0% VIP one one five nine which by the way is<00:23:51.910> awesome<00:23:52.300> it<00:23:52.450> just<00:23:52.690> seems<00:23:53.170> to<00:23:53.320> solve<00:23:53.590> so 00:23:53.760 --> 00:23:53.770 align:start position:0% is awesome it just seems to solve so 00:23:53.770 --> 00:24:01.470 align:start position:0% is awesome it just seems to solve so many<00:23:53.830> problems 00:24:01.470 --> 00:24:01.480 align:start position:0% 00:24:01.480 --> 00:24:04.270 align:start position:0% hi<00:24:02.480> I'm<00:24:02.660> Kent<00:24:02.930> I'm<00:24:03.140> the<00:24:03.320> head<00:24:03.470> of<00:24:03.500> R&D<00:24:03.740> at<00:24:04.250> a 00:24:04.270 --> 00:24:04.280 align:start position:0% hi I'm Kent I'm the head of R&D at a 00:24:04.280 --> 00:24:06.310 align:start position:0% hi I'm Kent I'm the head of R&D at a shape<00:24:04.790> shift<00:24:05.060> and<00:24:05.360> I'd<00:24:05.450> love<00:24:05.570> to<00:24:05.630> hear<00:24:05.900> more 00:24:06.310 --> 00:24:06.320 align:start position:0% shape shift and I'd love to hear more 00:24:06.320 --> 00:24:08.560 align:start position:0% shape shift and I'd love to hear more from<00:24:06.440> you<00:24:06.590> Vitalik<00:24:07.100> about<00:24:07.370> the<00:24:07.580> use<00:24:07.760> of<00:24:07.790> phase 00:24:08.560 --> 00:24:08.570 align:start position:0% from you Vitalik about the use of phase 00:24:08.570 --> 00:24:10.870 align:start position:0% from you Vitalik about the use of phase one<00:24:08.780> and<00:24:08.990> the<00:24:09.050> data<00:24:09.230> availability<00:24:10.160> context 00:24:10.870 --> 00:24:10.880 align:start position:0% one and the data availability context 00:24:10.880 --> 00:24:13.690 align:start position:0% one and the data availability context this<00:24:11.150> excites<00:24:11.540> me<00:24:11.720> a<00:24:11.750> lot<00:24:11.930> because<00:24:12.190> it<00:24:13.190> seems 00:24:13.690 --> 00:24:13.700 align:start position:0% this excites me a lot because it seems 00:24:13.700 --> 00:24:15.280 align:start position:0% this excites me a lot because it seems to<00:24:13.820> me<00:24:13.880> that<00:24:14.120> a<00:24:14.150> lot<00:24:14.480> of<00:24:14.510> the<00:24:14.630> really<00:24:14.750> vexing 00:24:15.280 --> 00:24:15.290 align:start position:0% to me that a lot of the really vexing 00:24:15.290 --> 00:24:17.950 align:start position:0% to me that a lot of the really vexing challenges<00:24:15.320> with<00:24:16.100> e<00:24:16.130> 2.0<00:24:16.790> are<00:24:17.390> are<00:24:17.600> in<00:24:17.750> phase 00:24:17.950 --> 00:24:17.960 align:start position:0% challenges with e 2.0 are are in phase 00:24:17.960 --> 00:24:20.050 align:start position:0% challenges with e 2.0 are are in phase two<00:24:18.290> with<00:24:18.620> the<00:24:18.800> Chardonnay<00:24:19.040> ease<00:24:19.490> and 00:24:20.050 --> 00:24:20.060 align:start position:0% two with the Chardonnay ease and 00:24:20.060 --> 00:24:21.340 align:start position:0% two with the Chardonnay ease and Crossgate<00:24:20.570> trot<00:24:20.900> cross<00:24:21.140> during 00:24:21.340 --> 00:24:21.350 align:start position:0% Crossgate trot cross during 00:24:21.350 --> 00:24:23.860 align:start position:0% Crossgate trot cross during communication<00:24:22.270> this<00:24:23.270> could<00:24:23.510> effectively 00:24:23.860 --> 00:24:23.870 align:start position:0% communication this could effectively 00:24:23.870 --> 00:24:25.750 align:start position:0% communication this could effectively really<00:24:24.320> give<00:24:24.470> us<00:24:24.590> a<00:24:24.710> very<00:24:25.010> nice<00:24:25.190> bridge<00:24:25.490> where 00:24:25.750 --> 00:24:25.760 align:start position:0% really give us a very nice bridge where 00:24:25.760 --> 00:24:27.640 align:start position:0% really give us a very nice bridge where we<00:24:25.790> have<00:24:26.030> layer<00:24:26.420> two<00:24:26.600> solutions<00:24:27.110> with<00:24:27.260> Starks 00:24:27.640 --> 00:24:27.650 align:start position:0% we have layer two solutions with Starks 00:24:27.650 --> 00:24:30.010 align:start position:0% we have layer two solutions with Starks and<00:24:27.860> snarks<00:24:28.330> so<00:24:29.330> kind<00:24:29.510> of<00:24:29.540> a<00:24:29.660> two-fold 00:24:30.010 --> 00:24:30.020 align:start position:0% and snarks so kind of a two-fold 00:24:30.020 --> 00:24:33.790 align:start position:0% and snarks so kind of a two-fold question<00:24:30.130> to<00:24:31.130> what<00:24:31.310> what<00:24:31.610> extent<00:24:32.060> is<00:24:32.590> the<00:24:33.590> data 00:24:33.790 --> 00:24:33.800 align:start position:0% question to what what extent is the data 00:24:33.800 --> 00:24:36.010 align:start position:0% question to what what extent is the data availability<00:24:34.400> aspect<00:24:35.090> being<00:24:35.270> Specht<00:24:35.690> out<00:24:35.840> and 00:24:36.010 --> 00:24:36.020 align:start position:0% availability aspect being Specht out and 00:24:36.020 --> 00:24:37.990 align:start position:0% availability aspect being Specht out and built<00:24:36.200> with<00:24:36.410> those<00:24:36.680> particular<00:24:36.950> use<00:24:37.460> cases<00:24:37.730> in 00:24:37.990 --> 00:24:38.000 align:start position:0% built with those particular use cases in 00:24:38.000 --> 00:24:40.510 align:start position:0% built with those particular use cases in mind<00:24:38.180> and<00:24:38.390> also<00:24:38.990> if<00:24:39.200> you<00:24:39.320> could<00:24:39.490> shed<00:24:40.490> some 00:24:40.510 --> 00:24:40.520 align:start position:0% mind and also if you could shed some 00:24:40.520 --> 00:24:43.680 align:start position:0% mind and also if you could shed some light<00:24:40.640> on<00:24:40.970> the<00:24:41.090> big<00:24:41.300> research<00:24:42.100> challenges<00:24:43.100> and 00:24:43.680 --> 00:24:43.690 align:start position:0% light on the big research challenges and 00:24:43.690 --> 00:24:47.700 align:start position:0% light on the big research challenges and questions<00:24:44.690> as<00:24:44.930> that<00:24:45.710> aspect<00:24:46.190> is<00:24:46.370> built<00:24:46.670> out 00:24:47.700 --> 00:24:47.710 align:start position:0% questions as that aspect is built out 00:24:47.710 --> 00:24:50.920 align:start position:0% questions as that aspect is built out sure<00:24:48.710> so<00:24:49.460> their<00:24:49.760> existing<00:24:50.360> a<00:24:50.480> scalability 00:24:50.920 --> 00:24:50.930 align:start position:0% sure so their existing a scalability 00:24:50.930 --> 00:24:53.470 align:start position:0% sure so their existing a scalability solution<00:24:51.590> already<00:24:51.920> like<00:24:52.220> plasmid<00:24:53.150> group<00:24:53.360> is 00:24:53.470 --> 00:24:53.480 align:start position:0% solution already like plasmid group is 00:24:53.480 --> 00:24:57.010 align:start position:0% solution already like plasmid group is doing<00:24:53.780> a<00:24:53.900> demo<00:24:54.410> of<00:24:54.440> it<00:24:54.740> like<00:24:55.010> a<00:24:55.540> theory<00:24:56.540> I<00:24:56.960> think 00:24:57.010 --> 00:24:57.020 align:start position:0% doing a demo of it like a theory I think 00:24:57.020 --> 00:24:59.170 align:start position:0% doing a demo of it like a theory I think at<00:24:57.260> Def<00:24:57.500> Con<00:24:57.530> they<00:24:58.130> called<00:24:58.370> them<00:24:58.580> optimistic 00:24:59.170 --> 00:24:59.180 align:start position:0% at Def Con they called them optimistic 00:24:59.180 --> 00:25:01.660 align:start position:0% at Def Con they called them optimistic roll-up<00:24:59.540> an<00:24:59.720> optimistic<00:25:00.560> roll-up<00:25:01.100> basically 00:25:01.660 --> 00:25:01.670 align:start position:0% roll-up an optimistic roll-up basically 00:25:01.670 --> 00:25:05.380 align:start position:0% roll-up an optimistic roll-up basically works<00:25:01.940> by<00:25:02.350> publishing<00:25:03.670> transaction<00:25:04.670> data<00:25:05.000> in 00:25:05.380 --> 00:25:05.390 align:start position:0% works by publishing transaction data in 00:25:05.390 --> 00:25:08.080 align:start position:0% works by publishing transaction data in a<00:25:05.540> very<00:25:05.810> compressed<00:25:06.260> form<00:25:06.620> on<00:25:06.830> chain<00:25:07.160> but<00:25:07.730> not 00:25:08.080 --> 00:25:08.090 align:start position:0% a very compressed form on chain but not 00:25:08.090 --> 00:25:11.670 align:start position:0% a very compressed form on chain but not doing<00:25:08.660> like<00:25:08.960> the<00:25:09.260> execution<00:25:09.830> on<00:25:10.280> chain<00:25:10.520> and 00:25:11.670 --> 00:25:11.680 align:start position:0% doing like the execution on chain and 00:25:11.680 --> 00:25:15.850 align:start position:0% doing like the execution on chain and optimistic<00:25:12.910> because<00:25:13.910> you<00:25:14.750> avoid<00:25:14.900> executing 00:25:15.850 --> 00:25:15.860 align:start position:0% optimistic because you avoid executing 00:25:15.860 --> 00:25:17.440 align:start position:0% optimistic because you avoid executing you<00:25:15.950> only<00:25:16.100> have<00:25:16.310> a<00:25:16.340> little<00:25:16.580> bit<00:25:16.730> of<00:25:16.880> data<00:25:17.060> and 00:25:17.440 --> 00:25:17.450 align:start position:0% you only have a little bit of data and 00:25:17.450 --> 00:25:19.630 align:start position:0% you only have a little bit of data and especially<00:25:18.170> because<00:25:18.500> data<00:25:18.890> is<00:25:19.040> relative<00:25:19.550> is 00:25:19.630 --> 00:25:19.640 align:start position:0% especially because data is relative is 00:25:19.640 --> 00:25:22.510 align:start position:0% especially because data is relative is very<00:25:20.180> cheap<00:25:20.360> relative<00:25:20.750> to<00:25:20.870> computation<00:25:21.590> even 00:25:22.510 --> 00:25:22.520 align:start position:0% very cheap relative to computation even 00:25:22.520 --> 00:25:24.280 align:start position:0% very cheap relative to computation even on<00:25:22.760> the<00:25:22.970> East<00:25:23.120> one<00:25:23.390> system<00:25:23.840> you<00:25:23.960> can<00:25:24.140> achieve 00:25:24.280 --> 00:25:24.290 align:start position:0% on the East one system you can achieve 00:25:24.290 --> 00:25:28.870 align:start position:0% on the East one system you can achieve scale<00:25:24.800> a<00:25:25.540> scalability<00:25:26.540> of<00:25:26.810> like<00:25:27.500> 10<00:25:28.100> to<00:25:28.250> 100<00:25:28.700> X 00:25:28.870 --> 00:25:28.880 align:start position:0% scale a scalability of like 10 to 100 X 00:25:28.880 --> 00:25:30.640 align:start position:0% scale a scalability of like 10 to 100 X like<00:25:29.180> the<00:25:29.360> theoretical<00:25:29.900> max<00:25:30.080> throughput<00:25:30.350> is 00:25:30.640 --> 00:25:30.650 align:start position:0% like the theoretical max throughput is 00:25:30.650 --> 00:25:33.220 align:start position:0% like the theoretical max throughput is somewhere<00:25:30.920> around<00:25:31.040> 3000<00:25:31.910> CPS<00:25:32.750> if<00:25:33.020> like 00:25:33.220 --> 00:25:33.230 align:start position:0% somewhere around 3000 CPS if like 00:25:33.230 --> 00:25:35.230 align:start position:0% somewhere around 3000 CPS if like everyone<00:25:33.680> were<00:25:33.830> to<00:25:33.890> just<00:25:34.220> use<00:25:34.520> optimistic 00:25:35.230 --> 00:25:35.240 align:start position:0% everyone were to just use optimistic 00:25:35.240 --> 00:25:38.830 align:start position:0% everyone were to just use optimistic roll-up<00:25:35.570> for<00:25:35.780> moving<00:25:35.930> coins<00:25:36.230> around<00:25:36.410> and<00:25:37.360> if<00:25:38.360> 2 00:25:38.830 --> 00:25:38.840 align:start position:0% roll-up for moving coins around and if 2 00:25:38.840 --> 00:25:42.070 align:start position:0% roll-up for moving coins around and if 2 could<00:25:39.230> potentially<00:25:39.950> take<00:25:40.700> make<00:25:41.180> optimistic 00:25:42.070 --> 00:25:42.080 align:start position:0% could potentially take make optimistic 00:25:42.080 --> 00:25:44.280 align:start position:0% could potentially take make optimistic roll-up<00:25:42.500> even<00:25:42.860> more<00:25:43.040> powerful<00:25:43.640> because 00:25:44.280 --> 00:25:44.290 align:start position:0% roll-up even more powerful because 00:25:44.290 --> 00:25:46.990 align:start position:0% roll-up even more powerful because instead<00:25:45.290> of<00:25:45.440> using<00:25:45.800> the<00:25:46.280> ease<00:25:46.430> one<00:25:46.700> chains 00:25:46.990 --> 00:25:47.000 align:start position:0% instead of using the ease one chains 00:25:47.000 --> 00:25:49.240 align:start position:0% instead of using the ease one chains data<00:25:47.300> store<00:25:47.630> off<00:25:47.780> the<00:25:47.960> store<00:25:48.230> that's<00:25:48.920> a<00:25:49.040> store 00:25:49.240 --> 00:25:49.250 align:start position:0% data store off the store that's a store 00:25:49.250 --> 00:25:50.530 align:start position:0% data store off the store that's a store this<00:25:49.400> data<00:25:49.460> to<00:25:49.940> make<00:25:50.030> sure<00:25:50.090> that<00:25:50.420> it's 00:25:50.530 --> 00:25:50.540 align:start position:0% this data to make sure that it's 00:25:50.540 --> 00:25:52.030 align:start position:0% this data to make sure that it's available<00:25:50.690> you<00:25:51.050> would<00:25:51.290> be<00:25:51.410> storing<00:25:51.830> that<00:25:51.980> data 00:25:52.030 --> 00:25:52.040 align:start position:0% available you would be storing that data 00:25:52.040 --> 00:25:54.100 align:start position:0% available you would be storing that data on<00:25:52.490> these<00:25:52.640> two<00:25:52.910> chain<00:25:53.180> and<00:25:53.840> you<00:25:53.990> would 00:25:54.100 --> 00:25:54.110 align:start position:0% on these two chain and you would 00:25:54.110 --> 00:25:56.200 align:start position:0% on these two chain and you would basically<00:25:54.260> kind<00:25:54.920> of<00:25:55.040> feed<00:25:55.370> into<00:25:55.730> these<00:25:55.850> one 00:25:56.200 --> 00:25:56.210 align:start position:0% basically kind of feed into these one 00:25:56.210 --> 00:25:58.720 align:start position:0% basically kind of feed into these one side<00:25:56.450> merkel<00:25:56.930> proofs<00:25:57.200> that<00:25:57.350> prove<00:25:57.800> that<00:25:58.220> hey 00:25:58.720 --> 00:25:58.730 align:start position:0% side merkel proofs that prove that hey 00:25:58.730 --> 00:26:01.180 align:start position:0% side merkel proofs that prove that hey this<00:25:59.030> data<00:25:59.240> actually<00:25:59.690> has<00:25:59.870> been<00:26:00.080> accepted<00:26:01.070> by 00:26:01.180 --> 00:26:01.190 align:start position:0% this data actually has been accepted by 00:26:01.190 --> 00:26:03.910 align:start position:0% this data actually has been accepted by youth<00:26:01.340> too<00:26:01.610> and<00:26:01.940> so<00:26:02.450> if<00:26:02.630> you<00:26:02.780> imagine<00:26:03.350> like 00:26:03.910 --> 00:26:03.920 align:start position:0% youth too and so if you imagine like 00:26:03.920 --> 00:26:05.680 align:start position:0% youth too and so if you imagine like even<00:26:04.220> if<00:26:04.340> say<00:26:04.520> we<00:26:04.670> reduce<00:26:04.910> the<00:26:05.090> chard<00:26:05.300> kale<00:26:05.510> and 00:26:05.680 --> 00:26:05.690 align:start position:0% even if say we reduce the chard kale and 00:26:05.690 --> 00:26:07.630 align:start position:0% even if say we reduce the chard kale and some<00:26:05.810> they're<00:26:06.020> like<00:26:06.170> even<00:26:06.470> the<00:26:07.040> scalability 00:26:07.630 --> 00:26:07.640 align:start position:0% some they're like even the scalability 00:26:07.640 --> 00:26:09.130 align:start position:0% some they're like even the scalability at<00:26:07.730> the<00:26:07.790> beginning<00:26:08.120> is<00:26:08.240> toward<00:26:08.540> the<00:26:08.600> lower<00:26:08.840> end 00:26:09.130 --> 00:26:09.140 align:start position:0% at the beginning is toward the lower end 00:26:09.140 --> 00:26:10.960 align:start position:0% at the beginning is toward the lower end and<00:26:09.320> say<00:26:09.500> there<00:26:09.650> is<00:26:09.740> one<00:26:09.920> megabyte<00:26:10.340> per<00:26:10.580> second 00:26:10.960 --> 00:26:10.970 align:start position:0% and say there is one megabyte per second 00:26:10.970 --> 00:26:11.619 align:start position:0% and say there is one megabyte per second of<00:26:11.090> data 00:26:11.619 --> 00:26:11.629 align:start position:0% of data 00:26:11.629 --> 00:26:14.629 align:start position:0% of data then<00:26:12.629> if<00:26:13.139> we<00:26:13.409> talk<00:26:13.590> about<00:26:13.649> say<00:26:14.129> 20<00:26:14.489> buy 00:26:14.629 --> 00:26:14.639 align:start position:0% then if we talk about say 20 buy 00:26:14.639 --> 00:26:17.720 align:start position:0% then if we talk about say 20 buy transactions<00:26:15.450> then<00:26:15.720> that's<00:26:16.730> 50,000 00:26:17.720 --> 00:26:17.730 align:start position:0% transactions then that's 50,000 00:26:17.730 --> 00:26:20.180 align:start position:0% transactions then that's 50,000 transactions<00:26:18.299> a<00:26:18.389> second<00:26:18.840> that<00:26:19.080> could<00:26:19.499> fit 00:26:20.180 --> 00:26:20.190 align:start position:0% transactions a second that could fit 00:26:20.190 --> 00:26:24.169 align:start position:0% transactions a second that could fit inside<00:26:20.369> of<00:26:20.610> a<00:26:20.820> rollup<00:26:21.029> and<00:26:21.919> that's<00:26:23.029> and<00:26:24.029> it's 00:26:24.169 --> 00:26:24.179 align:start position:0% inside of a rollup and that's and it's 00:26:24.179 --> 00:26:29.269 align:start position:0% inside of a rollup and that's and it's like<00:26:24.360> a<00:26:24.840> system<00:26:25.710> that<00:26:25.980> could<00:26:26.789> like<00:26:27.350> the<00:26:28.350> logic 00:26:29.269 --> 00:26:29.279 align:start position:0% like a system that could like the logic 00:26:29.279 --> 00:26:30.830 align:start position:0% like a system that could like the logic for<00:26:29.460> for<00:26:29.909> kind<00:26:30.149> of<00:26:30.210> doing<00:26:30.480> it<00:26:30.600> is<00:26:30.690> something 00:26:30.830 --> 00:26:30.840 align:start position:0% for for kind of doing it is something 00:26:30.840 --> 00:26:33.259 align:start position:0% for for kind of doing it is something that<00:26:31.019> is<00:26:31.289> being<00:26:31.499> developed<00:26:31.889> already<00:26:32.249> I<00:26:32.700> think 00:26:33.259 --> 00:26:33.269 align:start position:0% that is being developed already I think 00:26:33.269 --> 00:26:35.539 align:start position:0% that is being developed already I think the<00:26:33.869> main<00:26:34.080> challenge<00:26:34.110> that<00:26:35.039> would<00:26:35.159> need<00:26:35.309> to<00:26:35.369> be 00:26:35.539 --> 00:26:35.549 align:start position:0% the main challenge that would need to be 00:26:35.549 --> 00:26:37.220 align:start position:0% the main challenge that would need to be solved<00:26:36.059> as<00:26:36.179> AG<00:26:36.330> you<00:26:36.450> it<00:26:36.570> needs<00:26:36.749> to<00:26:36.929> have<00:26:37.080> at 00:26:37.220 --> 00:26:37.230 align:start position:0% solved as AG you it needs to have at 00:26:37.230 --> 00:26:39.560 align:start position:0% solved as AG you it needs to have at least<00:26:37.379> a<00:26:37.590> minimal<00:26:37.980> sort<00:26:38.249> of<00:26:38.369> fee<00:26:38.549> market<00:26:38.970> on 00:26:39.560 --> 00:26:39.570 align:start position:0% least a minimal sort of fee market on 00:26:39.570 --> 00:26:40.519 align:start position:0% least a minimal sort of fee market on the<00:26:39.720> youth<00:26:39.869> suicide 00:26:40.519 --> 00:26:40.529 align:start position:0% the youth suicide 00:26:40.529 --> 00:26:43.639 align:start position:0% the youth suicide so<00:26:41.009> that<00:26:41.600> optimistic<00:26:42.600> roll-up<00:26:43.139> real<00:26:43.379> layers 00:26:43.639 --> 00:26:43.649 align:start position:0% so that optimistic roll-up real layers 00:26:43.649 --> 00:26:45.769 align:start position:0% so that optimistic roll-up real layers would<00:26:43.980> at<00:26:44.129> least<00:26:44.220> have<00:26:44.489> the<00:26:44.700> ability<00:26:45.149> to<00:26:45.179> kind 00:26:45.769 --> 00:26:45.779 align:start position:0% would at least have the ability to kind 00:26:45.779 --> 00:26:49.099 align:start position:0% would at least have the ability to kind of<00:26:45.899> pop<00:26:46.139> publish<00:26:46.830> their<00:26:47.580> data<00:26:47.609> and<00:26:48.600> I<00:26:48.960> think 00:26:49.099 --> 00:26:49.109 align:start position:0% of pop publish their data and I think 00:26:49.109 --> 00:26:50.389 align:start position:0% of pop publish their data and I think that<00:26:49.259> is<00:26:49.379> one<00:26:49.559> of<00:26:49.649> the<00:26:49.710> things<00:26:49.919> we're<00:26:50.100> actively 00:26:50.389 --> 00:26:50.399 align:start position:0% that is one of the things we're actively 00:26:50.399 --> 00:26:54.409 align:start position:0% that is one of the things we're actively thinking<00:26:50.789> about<00:26:52.519> and<00:26:53.519> the<00:26:53.669> other<00:26:53.820> challenges 00:26:54.409 --> 00:26:54.419 align:start position:0% thinking about and the other challenges 00:26:54.419 --> 00:26:56.599 align:start position:0% thinking about and the other challenges if<00:26:54.659> you<00:26:54.899> do<00:26:55.139> want<00:26:55.499> to<00:26:55.619> use<00:26:55.889> phase<00:26:56.220> one<00:26:56.460> as<00:26:56.580> a 00:26:56.599 --> 00:26:56.609 align:start position:0% if you do want to use phase one as a 00:26:56.609 --> 00:26:58.700 align:start position:0% if you do want to use phase one as a date<00:26:56.759> availability<00:26:57.179> layer<00:26:57.539> of<00:26:57.779> on<00:26:58.230> eighth<00:26:58.499> one 00:26:58.700 --> 00:26:58.710 align:start position:0% date availability layer of on eighth one 00:26:58.710 --> 00:27:01.460 align:start position:0% date availability layer of on eighth one you<00:26:59.039> need<00:26:59.249> to<00:26:59.489> go<00:27:00.359> down<00:27:00.570> the<00:27:00.779> finality<00:27:01.109> gadget 00:27:01.460 --> 00:27:01.470 align:start position:0% you need to go down the finality gadget 00:27:01.470 --> 00:27:05.239 align:start position:0% you need to go down the finality gadget road<00:27:01.679> and<00:27:01.980> expose<00:27:02.929> it<00:27:03.929> to<00:27:03.989> data<00:27:04.470> to<00:27:05.039> state 00:27:05.239 --> 00:27:05.249 align:start position:0% road and expose it to data to state 00:27:05.249 --> 00:27:07.039 align:start position:0% road and expose it to data to state routes<00:27:05.460> to<00:27:05.970> eath<00:27:06.330> one<00:27:06.539> so<00:27:06.809> you<00:27:06.899> can<00:27:06.989> make 00:27:07.039 --> 00:27:07.049 align:start position:0% routes to eath one so you can make 00:27:07.049 --> 00:27:11.989 align:start position:0% routes to eath one so you can make proofs<00:27:07.320> against<00:27:07.590> it<00:27:07.739> so<00:27:10.220> depending<00:27:11.220> on<00:27:11.340> as<00:27:11.850> we 00:27:11.989 --> 00:27:11.999 align:start position:0% proofs against it so depending on as we 00:27:11.999 --> 00:27:13.279 align:start position:0% proofs against it so depending on as we talked<00:27:12.210> about<00:27:12.299> in<00:27:12.600> the<00:27:12.690> last<00:27:12.840> session 00:27:13.279 --> 00:27:13.289 align:start position:0% talked about in the last session 00:27:13.289 --> 00:27:15.979 align:start position:0% talked about in the last session depending<00:27:13.649> on<00:27:13.980> kind<00:27:14.190> of<00:27:14.480> parallel<00:27:15.480> roadmaps 00:27:15.979 --> 00:27:15.989 align:start position:0% depending on kind of parallel roadmaps 00:27:15.989 --> 00:27:17.810 align:start position:0% depending on kind of parallel roadmaps and<00:27:16.200> how<00:27:16.350> long<00:27:16.529> expected<00:27:17.340> things<00:27:17.489> gonna<00:27:17.639> take 00:27:17.810 --> 00:27:17.820 align:start position:0% and how long expected things gonna take 00:27:17.820 --> 00:27:22.099 align:start position:0% and how long expected things gonna take it<00:27:17.970> may<00:27:18.090> or<00:27:18.179> may<00:27:18.239> not<00:27:18.269> be<00:27:18.509> worth<00:27:18.629> it<00:27:20.419> right<00:27:21.419> next 00:27:22.099 --> 00:27:22.109 align:start position:0% it may or may not be worth it right next 00:27:22.109 --> 00:27:22.639 align:start position:0% it may or may not be worth it right next question 00:27:22.639 --> 00:27:22.649 align:start position:0% question 00:27:22.649 --> 00:27:35.170 align:start position:0% question Oh<00:27:25.309> Marty<00:27:27.019> hey<00:27:28.019> Martin 00:27:35.170 --> 00:27:35.180 align:start position:0% 00:27:35.180 --> 00:27:38.350 align:start position:0% yeah<00:27:35.630> so<00:27:35.870> I<00:27:36.400> came<00:27:37.400> a<00:27:37.460> little<00:27:37.640> late<00:27:37.910> so<00:27:38.090> I<00:27:38.150> hope 00:27:38.350 --> 00:27:38.360 align:start position:0% yeah so I came a little late so I hope 00:27:38.360 --> 00:27:40.660 align:start position:0% yeah so I came a little late so I hope this<00:27:38.540> question<00:27:38.870> hasn't<00:27:39.080> been<00:27:39.290> asked<00:27:39.740> if<00:27:40.490> so 00:27:40.660 --> 00:27:40.670 align:start position:0% this question hasn't been asked if so 00:27:40.670 --> 00:27:42.790 align:start position:0% this question hasn't been asked if so I'll<00:27:41.180> just<00:27:41.360> excuse<00:27:41.750> myself<00:27:41.930> but<00:27:42.350> the<00:27:42.470> question 00:27:42.790 --> 00:27:42.800 align:start position:0% I'll just excuse myself but the question 00:27:42.800 --> 00:27:45.730 align:start position:0% I'll just excuse myself but the question is<00:27:43.390> around<00:27:44.390> the<00:27:44.510> process<00:27:44.990> by<00:27:45.170> which<00:27:45.230> a 00:27:45.730 --> 00:27:45.740 align:start position:0% is around the process by which a 00:27:45.740 --> 00:27:47.830 align:start position:0% is around the process by which a particular<00:27:46.430> execution<00:27:47.270> environment<00:27:47.690> is 00:27:47.830 --> 00:27:47.840 align:start position:0% particular execution environment is 00:27:47.840 --> 00:27:51.310 align:start position:0% particular execution environment is chosen<00:27:48.490> for<00:27:49.490> a<00:27:49.550> shard<00:27:50.090> if<00:27:50.600> there's<00:27:51.050> like<00:27:51.290> some 00:27:51.310 --> 00:27:51.320 align:start position:0% chosen for a shard if there's like some 00:27:51.320 --> 00:27:54.520 align:start position:0% chosen for a shard if there's like some auction<00:27:51.920> going<00:27:52.190> on<00:27:52.340> or<00:27:52.870> renting<00:27:53.870> that<00:27:53.900> space 00:27:54.520 --> 00:27:54.530 align:start position:0% auction going on or renting that space 00:27:54.530 --> 00:27:59.080 align:start position:0% auction going on or renting that space and<00:27:56.590> also<00:27:57.590> what<00:27:57.920> might<00:27:58.070> happen<00:27:58.310> if<00:27:58.760> you<00:27:58.940> need 00:27:59.080 --> 00:27:59.090 align:start position:0% and also what might happen if you need 00:27:59.090 --> 00:28:01.420 align:start position:0% and also what might happen if you need to<00:27:59.470> change<00:28:00.470> something<00:28:00.770> about<00:28:00.950> the<00:28:01.190> execution 00:28:01.420 --> 00:28:01.430 align:start position:0% to change something about the execution 00:28:01.430 --> 00:28:03.790 align:start position:0% to change something about the execution environment<00:28:02.030> like<00:28:02.230> forking<00:28:03.230> it<00:28:03.380> or<00:28:03.530> something 00:28:03.790 --> 00:28:03.800 align:start position:0% environment like forking it or something 00:28:03.800 --> 00:28:09.610 align:start position:0% environment like forking it or something like<00:28:03.830> that<00:28:06.910> look<00:28:07.910> in<00:28:08.180> all<00:28:08.570> of<00:28:08.810> the<00:28:08.960> proposals 00:28:09.610 --> 00:28:09.620 align:start position:0% like that look in all of the proposals 00:28:09.620 --> 00:28:12.580 align:start position:0% like that look in all of the proposals were<00:28:09.830> considering<00:28:10.490> so<00:28:10.730> far<00:28:10.760> I<00:28:11.060> think<00:28:11.590> blocks 00:28:12.580 --> 00:28:12.590 align:start position:0% were considering so far I think blocks 00:28:12.590 --> 00:28:15.520 align:start position:0% were considering so far I think blocks would<00:28:13.010> have<00:28:13.310> the<00:28:13.790> ability<00:28:14.300> to<00:28:14.330> contain<00:28:14.990> space 00:28:15.520 --> 00:28:15.530 align:start position:0% would have the ability to contain space 00:28:15.530 --> 00:28:18.660 align:start position:0% would have the ability to contain space for<00:28:15.950> multiple<00:28:16.520> execution<00:28:17.120> and<00:28:17.240> by<00:28:17.390> kind<00:28:17.630> of 00:28:18.660 --> 00:28:18.670 align:start position:0% for multiple execution and by kind of 00:28:18.670 --> 00:28:21.520 align:start position:0% for multiple execution and by kind of environment<00:28:19.670> spaces<00:28:20.390> in<00:28:20.540> them<00:28:20.720> and<00:28:20.960> so 00:28:21.520 --> 00:28:21.530 align:start position:0% environment spaces in them and so 00:28:21.530 --> 00:28:24.130 align:start position:0% environment spaces in them and so basically<00:28:22.040> like<00:28:22.490> you<00:28:22.670> would<00:28:22.790> expect<00:28:23.140> like 00:28:24.130 --> 00:28:24.140 align:start position:0% basically like you would expect like 00:28:24.140 --> 00:28:25.750 align:start position:0% basically like you would expect like it's<00:28:24.470> ultimately<00:28:24.890> the<00:28:25.070> block<00:28:25.250> proposes<00:28:25.730> that 00:28:25.750 --> 00:28:25.760 align:start position:0% it's ultimately the block proposes that 00:28:25.760 --> 00:28:27.910 align:start position:0% it's ultimately the block proposes that chooses<00:28:26.330> what<00:28:26.510> to<00:28:26.540> include<00:28:26.810> and<00:28:27.350> different 00:28:27.910 --> 00:28:27.920 align:start position:0% chooses what to include and different 00:28:27.920 --> 00:28:30.400 align:start position:0% chooses what to include and different people<00:28:28.040> it<00:28:28.340> would<00:28:28.520> would<00:28:29.150> be<00:28:29.270> able<00:28:29.360> to<00:28:29.510> bid<00:28:29.840> but 00:28:30.400 --> 00:28:30.410 align:start position:0% people it would would be able to bid but 00:28:30.410 --> 00:28:31.630 align:start position:0% people it would would be able to bid but like<00:28:30.740> you<00:28:30.890> would<00:28:31.010> expect 00:28:31.630 --> 00:28:31.640 align:start position:0% like you would expect 00:28:31.640 --> 00:28:33.730 align:start position:0% like you would expect I<00:28:31.790> mean<00:28:32.240> if<00:28:32.330> at<00:28:32.420> least<00:28:32.540> popular<00:28:33.110> execution 00:28:33.730 --> 00:28:33.740 align:start position:0% I mean if at least popular execution 00:28:33.740 --> 00:28:36.910 align:start position:0% I mean if at least popular execution environments<00:28:34.370> to<00:28:34.460> have<00:28:34.610> a<00:28:35.350> presence<00:28:36.350> and<00:28:36.530> be 00:28:36.910 --> 00:28:36.920 align:start position:0% environments to have a presence and be 00:28:36.920 --> 00:28:39.520 align:start position:0% environments to have a presence and be executed<00:28:37.490> even<00:28:37.640> in<00:28:38.240> every<00:28:38.660> slot<00:28:38.990> in<00:28:39.320> the<00:28:39.500> show 00:28:39.520 --> 00:28:39.530 align:start position:0% executed even in every slot in the show 00:28:39.530 --> 00:28:43.260 align:start position:0% executed even in every slot in the show the<00:28:40.130> shards<00:28:40.550> in<00:28:40.760> in<00:28:41.240> which<00:28:41.480> they're<00:28:41.690> located 00:28:43.260 --> 00:28:43.270 align:start position:0% the shards in in which they're located 00:28:43.270 --> 00:28:45.670 align:start position:0% the shards in in which they're located to<00:28:44.270> be<00:28:44.390> clear<00:28:44.630> the<00:28:44.750> execution<00:28:45.170> environment<00:28:45.590> is 00:28:45.670 --> 00:28:45.680 align:start position:0% to be clear the execution environment is 00:28:45.680 --> 00:28:47.860 align:start position:0% to be clear the execution environment is defined<00:28:46.160> on<00:28:46.520> the<00:28:47.090> beacon<00:28:47.330> chain<00:28:47.570> and<00:28:47.750> thus 00:28:47.860 --> 00:28:47.870 align:start position:0% defined on the beacon chain and thus 00:28:47.870 --> 00:28:50.590 align:start position:0% defined on the beacon chain and thus available<00:28:48.620> on<00:28:48.830> all<00:28:49.700> of<00:28:49.730> the<00:28:49.910> shark<00:28:50.150> chains<00:28:50.390> and 00:28:50.590 --> 00:28:50.600 align:start position:0% available on all of the shark chains and 00:28:50.600 --> 00:28:52.630 align:start position:0% available on all of the shark chains and so<00:28:51.110> when<00:28:51.740> you<00:28:51.830> make<00:28:51.920> a<00:28:51.980> block<00:28:52.250> you're<00:28:52.430> kind<00:28:52.580> of 00:28:52.630 --> 00:28:52.640 align:start position:0% so when you make a block you're kind of 00:28:52.640 --> 00:28:54.550 align:start position:0% so when you make a block you're kind of signaling<00:28:53.120> this<00:28:53.270> block<00:28:53.540> is<00:28:53.720> for<00:28:54.020> this 00:28:54.550 --> 00:28:54.560 align:start position:0% signaling this block is for this 00:28:54.560 --> 00:28:56.080 align:start position:0% signaling this block is for this execution<00:28:54.950> environment<00:28:55.490> and<00:28:55.580> thus<00:28:55.700> the<00:28:55.910> data 00:28:56.080 --> 00:28:56.090 align:start position:0% execution environment and thus the data 00:28:56.090 --> 00:28:58.360 align:start position:0% execution environment and thus the data in<00:28:56.390> this<00:28:56.540> block<00:28:56.780> or<00:28:57.020> chunk<00:28:57.590> of<00:28:57.710> data<00:28:57.890> maybe 00:28:58.360 --> 00:28:58.370 align:start position:0% in this block or chunk of data maybe 00:28:58.370 --> 00:29:01.090 align:start position:0% in this block or chunk of data maybe multiple<00:28:58.700> is<00:28:59.120> for<00:28:59.780> that<00:29:00.100> execution 00:29:01.090 --> 00:29:01.100 align:start position:0% multiple is for that execution 00:29:01.100 --> 00:29:02.200 align:start position:0% multiple is for that execution environment<00:29:01.550> and<00:29:01.640> so<00:29:01.700> you<00:29:01.760> can<00:29:01.880> kind<00:29:02.030> of<00:29:02.060> think 00:29:02.200 --> 00:29:02.210 align:start position:0% environment and so you can kind of think 00:29:02.210 --> 00:29:05.230 align:start position:0% environment and so you can kind of think of<00:29:02.390> say<00:29:03.320> this<00:29:03.770> this<00:29:04.100> block<00:29:04.430> was<00:29:04.670> for<00:29:04.880> execution 00:29:05.230 --> 00:29:05.240 align:start position:0% of say this this block was for execution 00:29:05.240 --> 00:29:07.090 align:start position:0% of say this this block was for execution fire<00:29:05.420> in<00:29:05.540> a<00:29:05.690> this<00:29:06.020> block<00:29:06.230> was<00:29:06.410> for<00:29:06.740> execution 00:29:07.090 --> 00:29:07.100 align:start position:0% fire in a this block was for execution 00:29:07.100 --> 00:29:09.010 align:start position:0% fire in a this block was for execution of<00:29:07.130> IRB<00:29:07.460> and<00:29:07.610> the<00:29:07.700> next<00:29:07.910> one<00:29:08.030> was<00:29:08.150> for<00:29:08.300> a<00:29:08.330> like 00:29:09.010 --> 00:29:09.020 align:start position:0% of IRB and the next one was for a like 00:29:09.020 --> 00:29:11.590 align:start position:0% of IRB and the next one was for a like the<00:29:09.170> actual<00:29:09.530> blockchain<00:29:10.370> of<00:29:10.640> a<00:29:10.910> is<00:29:11.180> like<00:29:11.390> this 00:29:11.590 --> 00:29:11.600 align:start position:0% the actual blockchain of a is like this 00:29:11.600 --> 00:29:15.040 align:start position:0% the actual blockchain of a is like this this<00:29:12.260> subset<00:29:13.010> of<00:29:13.130> the<00:29:13.970> the<00:29:14.510> actual<00:29:14.840> shard 00:29:15.040 --> 00:29:15.050 align:start position:0% this subset of the the actual shard 00:29:15.050 --> 00:29:22.420 align:start position:0% this subset of the the actual shard chain<00:29:15.460> and<00:29:16.460> on<00:29:16.910> the<00:29:17.510> forking<00:29:18.050> I<00:29:19.000> think<00:29:20.890> so<00:29:21.890> the 00:29:22.420 --> 00:29:22.430 align:start position:0% chain and on the forking I think so the 00:29:22.430 --> 00:29:23.590 align:start position:0% chain and on the forking I think so the nice<00:29:22.580> thing<00:29:22.760> about<00:29:22.790> it<00:29:22.970> is<00:29:23.060> you<00:29:23.420> could 00:29:23.590 --> 00:29:23.600 align:start position:0% nice thing about it is you could 00:29:23.600 --> 00:29:25.690 align:start position:0% nice thing about it is you could actually<00:29:23.840> define<00:29:24.320> migration<00:29:24.800> paths<00:29:24.980> such 00:29:25.690 --> 00:29:25.700 align:start position:0% actually define migration paths such 00:29:25.700 --> 00:29:28.240 align:start position:0% actually define migration paths such that<00:29:26.000> you<00:29:26.480> could<00:29:26.720> deploy<00:29:27.260> a<00:29:27.290> new<00:29:27.410> Yi<00:29:27.680> and<00:29:28.100> have 00:29:28.240 --> 00:29:28.250 align:start position:0% that you could deploy a new Yi and have 00:29:28.250 --> 00:29:30.850 align:start position:0% that you could deploy a new Yi and have some<00:29:28.460> sort<00:29:28.610> of<00:29:28.640> migration<00:29:29.150> from<00:29:29.860> previously 00:29:30.850 --> 00:29:30.860 align:start position:0% some sort of migration from previously 00:29:30.860 --> 00:29:33.100 align:start position:0% some sort of migration from previously to<00:29:31.460> new<00:29:31.610> Yi<00:29:31.790> and<00:29:32.030> I<00:29:32.390> do<00:29:32.450> expect<00:29:32.840> these<00:29:33.050> things 00:29:33.100 --> 00:29:33.110 align:start position:0% to new Yi and I do expect these things 00:29:33.110 --> 00:29:34.840 align:start position:0% to new Yi and I do expect these things to<00:29:33.410> kind<00:29:33.650> of<00:29:33.710> emerge<00:29:33.980> in<00:29:34.190> a<00:29:34.430> standards 00:29:34.840 --> 00:29:34.850 align:start position:0% to kind of emerge in a standards 00:29:34.850 --> 00:29:37.080 align:start position:0% to kind of emerge in a standards standards<00:29:35.540> way<00:29:35.690> kind<00:29:36.140> of<00:29:36.200> like<00:29:36.320> in<00:29:36.440> the<00:29:36.530> ERC 00:29:37.080 --> 00:29:37.090 align:start position:0% standards way kind of like in the ERC 00:29:37.090 --> 00:29:41.200 align:start position:0% standards way kind of like in the ERC standards<00:29:38.090> but<00:29:38.840> I<00:29:39.440> could<00:29:40.160> also<00:29:40.400> see<00:29:40.880> that 00:29:41.200 --> 00:29:41.210 align:start position:0% standards but I could also see that 00:29:41.210 --> 00:29:44.000 align:start position:0% standards but I could also see that certain<00:29:41.450> ease<00:29:41.720> especially<00:29:42.440> like<00:29:42.650> the<00:29:42.770> eath<00:29:42.890> 1e 00:29:44.000 --> 00:29:44.010 align:start position:0% certain ease especially like the eath 1e 00:29:44.010 --> 00:29:46.520 align:start position:0% certain ease especially like the eath 1e could<00:29:44.400> still<00:29:45.330> maybe<00:29:45.750> be<00:29:45.990> subject<00:29:46.470> to 00:29:46.520 --> 00:29:46.530 align:start position:0% could still maybe be subject to 00:29:46.530 --> 00:29:49.070 align:start position:0% could still maybe be subject to hard-working<00:29:47.250> to<00:29:48.210> upgrade<00:29:48.510> and<00:29:48.630> manipulate 00:29:49.070 --> 00:29:49.080 align:start position:0% hard-working to upgrade and manipulate 00:29:49.080 --> 00:29:51.500 align:start position:0% hard-working to upgrade and manipulate depending<00:29:49.919> on<00:29:50.010> the<00:29:50.160> kind<00:29:50.549> of<00:29:50.580> social<00:29:50.790> dynamic 00:29:51.500 --> 00:29:51.510 align:start position:0% depending on the kind of social dynamic 00:29:51.510 --> 00:29:57.710 align:start position:0% depending on the kind of social dynamic remnant<00:29:55.700> yes<00:29:56.700> yes<00:29:56.940> so<00:29:57.120> I'm<00:29:57.210> saying<00:29:57.419> that<00:29:57.600> would 00:29:57.710 --> 00:29:57.720 align:start position:0% remnant yes yes so I'm saying that would 00:29:57.720 --> 00:30:01.760 align:start position:0% remnant yes yes so I'm saying that would be<00:29:57.870> a<00:29:57.900> like<00:29:58.380> to<00:29:59.370> actually<00:29:59.580> change<00:30:00.540> in<00:30:00.809> EE<00:30:00.929> would 00:30:01.760 --> 00:30:01.770 align:start position:0% be a like to actually change in EE would 00:30:01.770 --> 00:30:04.820 align:start position:0% be a like to actually change in EE would require<00:30:02.600> kind<00:30:03.600> of<00:30:03.690> changing<00:30:04.290> changing<00:30:04.590> the 00:30:04.820 --> 00:30:04.830 align:start position:0% require kind of changing changing the 00:30:04.830 --> 00:30:06.440 align:start position:0% require kind of changing changing the actual<00:30:05.070> code<00:30:05.280> of<00:30:05.429> the<00:30:05.700> protocol<00:30:05.970> and<00:30:06.330> an 00:30:06.440 --> 00:30:06.450 align:start position:0% actual code of the protocol and an 00:30:06.450 --> 00:30:10.159 align:start position:0% actual code of the protocol and an irregular<00:30:06.870> state<00:30:07.350> change<00:30:08.360> there<00:30:09.360> are<00:30:09.390> options 00:30:10.159 --> 00:30:10.169 align:start position:0% irregular state change there are options 00:30:10.169 --> 00:30:13.610 align:start position:0% irregular state change there are options to<00:30:10.970> migrate<00:30:11.970> an<00:30:12.120> upgrade<00:30:12.419> ease<00:30:12.720> without<00:30:13.230> doing 00:30:13.610 --> 00:30:13.620 align:start position:0% to migrate an upgrade ease without doing 00:30:13.620 --> 00:30:15.860 align:start position:0% to migrate an upgrade ease without doing that<00:30:13.650> but<00:30:14.130> there<00:30:14.429> it<00:30:14.730> might<00:30:15.030> still<00:30:15.360> be<00:30:15.390> like<00:30:15.840> a 00:30:15.860 --> 00:30:15.870 align:start position:0% that but there it might still be like a 00:30:15.870 --> 00:30:17.960 align:start position:0% that but there it might still be like a social<00:30:16.290> tool<00:30:16.500> to<00:30:16.770> coordinate<00:30:17.370> and<00:30:17.520> manipulate 00:30:17.960 --> 00:30:17.970 align:start position:0% social tool to coordinate and manipulate 00:30:17.970 --> 00:30:20.299 align:start position:0% social tool to coordinate and manipulate these<00:30:18.059> things<00:30:18.650> will<00:30:19.650> the<00:30:19.770> E's<00:30:20.070> be 00:30:20.299 --> 00:30:20.309 align:start position:0% these things will the E's be 00:30:20.309 --> 00:30:23.780 align:start position:0% these things will the E's be permissioned<00:30:20.820> or<00:30:21.570> like<00:30:22.140> is<00:30:22.919> you're<00:30:23.549> not<00:30:23.669> gonna 00:30:23.780 --> 00:30:23.790 align:start position:0% permissioned or like is you're not gonna 00:30:23.790 --> 00:30:26.450 align:start position:0% permissioned or like is you're not gonna so<00:30:24.450> if<00:30:24.780> you<00:30:24.960> want<00:30:25.110> to<00:30:25.169> add<00:30:25.320> a<00:30:25.350> new<00:30:25.590> EE<00:30:25.890> do<00:30:26.370> you 00:30:26.450 --> 00:30:26.460 align:start position:0% so if you want to add a new EE do you 00:30:26.460 --> 00:30:27.919 align:start position:0% so if you want to add a new EE do you need<00:30:26.640> to<00:30:26.820> fork<00:30:27.059> anything<00:30:27.480> or<00:30:27.690> can<00:30:27.809> you<00:30:27.900> just 00:30:27.919 --> 00:30:27.929 align:start position:0% need to fork anything or can you just 00:30:27.929 --> 00:30:32.840 align:start position:0% need to fork anything or can you just add<00:30:28.200> new<00:30:28.500> use<00:30:31.070> transaction<00:30:32.070> for<00:30:32.190> your<00:30:32.309> deposit 00:30:32.840 --> 00:30:32.850 align:start position:0% add new use transaction for your deposit 00:30:32.850 --> 00:30:34.430 align:start position:0% add new use transaction for your deposit requirements<00:30:33.210> so<00:30:33.660> we<00:30:33.690> do<00:30:33.900> the<00:30:34.020> beacon<00:30:34.260> chain 00:30:34.430 --> 00:30:34.440 align:start position:0% requirements so we do the beacon chain 00:30:34.440 --> 00:30:36.140 align:start position:0% requirements so we do the beacon chain doesn't<00:30:34.770> get<00:30:34.860> filled<00:30:35.100> up<00:30:35.220> too<00:30:35.400> much<00:30:35.580> but<00:30:35.910> like 00:30:36.140 --> 00:30:36.150 align:start position:0% doesn't get filled up too much but like 00:30:36.150 --> 00:30:38.150 align:start position:0% doesn't get filled up too much but like anyone<00:30:36.419> like<00:30:36.870> it<00:30:37.110> would<00:30:37.530> be<00:30:37.559> able<00:30:37.710> to<00:30:37.830> do<00:30:38.010> it 00:30:38.150 --> 00:30:38.160 align:start position:0% anyone like it would be able to do it 00:30:38.160 --> 00:30:39.590 align:start position:0% anyone like it would be able to do it you're<00:30:38.340> not<00:30:38.370> optioning<00:30:38.850> them<00:30:38.970> like<00:30:39.150> some<00:30:39.510> of 00:30:39.590 --> 00:30:39.600 align:start position:0% you're not optioning them like some of 00:30:39.600 --> 00:30:43.100 align:start position:0% you're not optioning them like some of the<00:30:39.660> guys<00:30:40.970> and<00:30:41.970> as<00:30:42.270> are<00:30:42.510> you<00:30:42.600> expecting 00:30:43.100 --> 00:30:43.110 align:start position:0% the guys and as are you expecting 00:30:43.110 --> 00:30:44.450 align:start position:0% the guys and as are you expecting applications 00:30:44.450 --> 00:30:44.460 align:start position:0% applications 00:30:44.460 --> 00:30:46.549 align:start position:0% applications expecting<00:30:45.299> applications<00:30:45.900> some<00:30:46.410> of<00:30:46.440> the 00:30:46.549 --> 00:30:46.559 align:start position:0% expecting applications some of the 00:30:46.559 --> 00:30:49.810 align:start position:0% expecting applications some of the bigger<00:30:46.710> ones<00:30:46.919> to<00:30:47.130> have<00:30:47.250> their<00:30:47.370> own<00:30:47.490> EE 00:30:49.810 --> 00:30:49.820 align:start position:0% 00:30:49.820 --> 00:30:55.340 align:start position:0% yeah<00:30:50.820> possible<00:30:51.330> some<00:30:51.630> a<00:30:51.929> lot<00:30:52.799> of<00:30:53.540> a<00:30:54.540> lot<00:30:55.320> of 00:30:55.340 --> 00:30:55.350 align:start position:0% yeah possible some a lot of a lot of 00:30:55.350 --> 00:30:56.780 align:start position:0% yeah possible some a lot of a lot of like<00:30:55.650> the<00:30:55.860> reasons<00:30:56.160> you<00:30:56.280> might<00:30:56.370> have<00:30:56.580> an<00:30:56.700> e 00:30:56.780 --> 00:30:56.790 align:start position:0% like the reasons you might have an e 00:30:56.790 --> 00:30:58.880 align:start position:0% like the reasons you might have an e like<00:30:57.059> it<00:30:57.690> doesn't<00:30:58.169> actually<00:30:58.260> make<00:30:58.530> sense<00:30:58.679> and 00:30:58.880 --> 00:30:58.890 align:start position:0% like it doesn't actually make sense and 00:30:58.890 --> 00:31:00.049 align:start position:0% like it doesn't actually make sense and it<00:30:58.950> might<00:30:59.070> just<00:30:59.100> make<00:30:59.370> sense<00:30:59.549> to<00:30:59.730> operate 00:31:00.049 --> 00:31:00.059 align:start position:0% it might just make sense to operate 00:31:00.059 --> 00:31:02.600 align:start position:0% it might just make sense to operate within<00:31:00.299> an<00:31:00.510> e<00:31:00.630> but<00:31:01.559> I<00:31:01.620> do<00:31:01.740> funny<00:31:02.280> that<00:31:02.490> you 00:31:02.600 --> 00:31:02.610 align:start position:0% within an e but I do funny that you 00:31:02.610 --> 00:31:05.030 align:start position:0% within an e but I do funny that you asked<00:31:02.790> that<00:31:02.880> I<00:31:03.240> have<00:31:04.230> thought<00:31:04.559> it<00:31:04.770> could<00:31:04.919> be 00:31:05.030 --> 00:31:05.040 align:start position:0% asked that I have thought it could be 00:31:05.040 --> 00:31:06.770 align:start position:0% asked that I have thought it could be like<00:31:05.280> certainly<00:31:05.910> an<00:31:06.150> a<00:31:06.299> way<00:31:06.510> to<00:31:06.570> advertise 00:31:06.770 --> 00:31:06.780 align:start position:0% like certainly an a way to advertise 00:31:06.780 --> 00:31:09.260 align:start position:0% like certainly an a way to advertise like<00:31:07.260> if<00:31:07.380> the<00:31:07.500> casino<00:31:07.950> has<00:31:08.220> their<00:31:08.460> own<00:31:08.490> e<00:31:08.610> come 00:31:09.260 --> 00:31:09.270 align:start position:0% like if the casino has their own e come 00:31:09.270 --> 00:31:12.470 align:start position:0% like if the casino has their own e come join<00:31:09.570> us<00:31:10.790> gaming<00:31:11.790> e<00:31:11.880> I<00:31:12.120> mean<00:31:12.240> there's<00:31:12.390> probably 00:31:12.470 --> 00:31:12.480 align:start position:0% join us gaming e I mean there's probably 00:31:12.480 --> 00:31:14.659 align:start position:0% join us gaming e I mean there's probably some<00:31:12.780> yeah<00:31:12.960> some<00:31:13.169> data<00:31:13.890> that<00:31:14.070> we<00:31:14.280> would<00:31:14.429> want 00:31:14.659 --> 00:31:14.669 align:start position:0% some yeah some data that we would want 00:31:14.669 --> 00:31:16.520 align:start position:0% some yeah some data that we would want to<00:31:14.730> store<00:31:14.940> that<00:31:14.970> no<00:31:15.210> one<00:31:15.360> else<00:31:15.510> wants<00:31:15.780> to<00:31:15.809> so 00:31:16.520 --> 00:31:16.530 align:start position:0% to store that no one else wants to so 00:31:16.530 --> 00:31:20.539 align:start position:0% to store that no one else wants to so yeah<00:31:16.950> or<00:31:17.900> maybe<00:31:18.900> not<00:31:19.200> data<00:31:19.470> but<00:31:19.860> more<00:31:20.070> like<00:31:20.340> how 00:31:20.539 --> 00:31:20.549 align:start position:0% yeah or maybe not data but more like how 00:31:20.549 --> 00:31:23.060 align:start position:0% yeah or maybe not data but more like how you<00:31:20.610> optimize<00:31:21.000> the<00:31:21.750> structure<00:31:22.169> of<00:31:22.500> accessing 00:31:23.060 --> 00:31:23.070 align:start position:0% you optimize the structure of accessing 00:31:23.070 --> 00:31:25.070 align:start position:0% you optimize the structure of accessing certain<00:31:23.280> things<00:31:23.640> in<00:31:24.030> a<00:31:24.090> fraction<00:31:24.510> of<00:31:24.600> a<00:31:24.720> second 00:31:25.070 --> 00:31:25.080 align:start position:0% certain things in a fraction of a second 00:31:25.080 --> 00:31:27.860 align:start position:0% certain things in a fraction of a second block<00:31:25.260> time<00:31:25.440> would<00:31:25.590> be<00:31:25.679> really<00:31:25.950> good<00:31:26.840> yeah<00:31:27.840> I 00:31:27.860 --> 00:31:27.870 align:start position:0% block time would be really good yeah I 00:31:27.870 --> 00:31:30.289 align:start position:0% block time would be really good yeah I think<00:31:28.830> it<00:31:29.070> might<00:31:29.220> be<00:31:29.250> like<00:31:29.520> another<00:31:29.790> tier<00:31:30.179> of 00:31:30.289 --> 00:31:30.299 align:start position:0% think it might be like another tier of 00:31:30.299 --> 00:31:31.909 align:start position:0% think it might be like another tier of developer<00:31:30.780> that<00:31:30.900> makes<00:31:31.080> an<00:31:31.200> EE<00:31:31.320> it<00:31:31.650> might<00:31:31.799> be 00:31:31.909 --> 00:31:31.919 align:start position:0% developer that makes an EE it might be 00:31:31.919 --> 00:31:33.740 align:start position:0% developer that makes an EE it might be someone<00:31:32.280> that's<00:31:32.370> working<00:31:32.640> really<00:31:32.970> deeply<00:31:33.660> in 00:31:33.740 --> 00:31:33.750 align:start position:0% someone that's working really deeply in 00:31:33.750 --> 00:31:35.480 align:start position:0% someone that's working really deeply in protocol<00:31:34.140> research<00:31:34.530> or<00:31:34.799> like<00:31:34.919> zero<00:31:35.340> knowledge 00:31:35.480 --> 00:31:35.490 align:start position:0% protocol research or like zero knowledge 00:31:35.490 --> 00:31:37.220 align:start position:0% protocol research or like zero knowledge proof<00:31:35.610> research<00:31:36.150> or<00:31:36.360> something<00:31:36.540> they<00:31:37.080> really 00:31:37.220 --> 00:31:37.230 align:start position:0% proof research or something they really 00:31:37.230 --> 00:31:38.480 align:start position:0% proof research or something they really know<00:31:37.410> what<00:31:37.559> they're<00:31:37.679> doing<00:31:37.710> and<00:31:38.130> they<00:31:38.250> can't 00:31:38.480 --> 00:31:38.490 align:start position:0% know what they're doing and they can't 00:31:38.490 --> 00:31:39.890 align:start position:0% know what they're doing and they can't do<00:31:38.610> it<00:31:38.640> anywhere<00:31:38.910> else<00:31:39.150> and<00:31:39.419> then<00:31:39.510> they'll<00:31:39.720> go 00:31:39.890 --> 00:31:39.900 align:start position:0% do it anywhere else and then they'll go 00:31:39.900 --> 00:31:41.539 align:start position:0% do it anywhere else and then they'll go to<00:31:39.929> that<00:31:40.200> but<00:31:40.679> then<00:31:40.799> you<00:31:40.830> know<00:31:40.980> like<00:31:41.190> kind<00:31:41.370> of 00:31:41.539 --> 00:31:41.549 align:start position:0% to that but then you know like kind of 00:31:41.549 --> 00:31:43.070 align:start position:0% to that but then you know like kind of typical<00:31:42.240> developer<00:31:42.720> that's<00:31:42.870> at<00:31:42.990> the 00:31:43.070 --> 00:31:43.080 align:start position:0% typical developer that's at the 00:31:43.080 --> 00:31:44.570 align:start position:0% typical developer that's at the application<00:31:43.710> layer<00:31:43.890> would<00:31:44.100> probably<00:31:44.370> want<00:31:44.520> to 00:31:44.570 --> 00:31:44.580 align:start position:0% application layer would probably want to 00:31:44.580 --> 00:31:49.490 align:start position:0% application layer would probably want to stay<00:31:45.150> away<00:31:45.179> from<00:31:45.390> it<00:31:47.870> any<00:31:48.870> other<00:31:48.960> question 00:31:49.490 --> 00:31:49.500 align:start position:0% stay away from it any other question 00:31:49.500 --> 00:31:52.580 align:start position:0% stay away from it any other question from<00:31:49.620> the<00:31:49.830> audience<00:31:49.919> I<00:31:51.110> mean<00:31:52.110> while<00:31:52.440> we're 00:31:52.580 --> 00:31:52.590 align:start position:0% from the audience I mean while we're 00:31:52.590 --> 00:31:55.669 align:start position:0% from the audience I mean while we're waiting<00:31:52.830> for<00:31:52.860> a<00:31:53.040> question<00:31:53.309> I<00:31:54.169> mean<00:31:55.169> maybe<00:31:55.500> it's 00:31:55.669 --> 00:31:55.679 align:start position:0% waiting for a question I mean maybe it's 00:31:55.679 --> 00:31:57.200 align:start position:0% waiting for a question I mean maybe it's put<00:31:55.799> a<00:31:55.860> bit<00:31:55.980> of<00:31:56.010> cold<00:31:56.460> water<00:31:56.520> on<00:31:56.970> the 00:31:57.200 --> 00:31:57.210 align:start position:0% put a bit of cold water on the 00:31:57.210 --> 00:32:00.560 align:start position:0% put a bit of cold water on the like<00:31:58.020> I<00:31:58.470> mean<00:31:58.560> it's<00:31:58.770> the<00:31:59.010> ease<00:31:59.190> of<00:31:59.220> a<00:31:59.940> beautiful 00:32:00.560 --> 00:32:00.570 align:start position:0% like I mean it's the ease of a beautiful 00:32:00.570 --> 00:32:03.920 align:start position:0% like I mean it's the ease of a beautiful piece<00:32:00.780> of<00:32:00.810> layer<00:32:01.530> of<00:32:01.680> abstraction<00:32:02.450> and<00:32:03.450> very 00:32:03.920 --> 00:32:03.930 align:start position:0% piece of layer of abstraction and very 00:32:03.930 --> 00:32:06.860 align:start position:0% piece of layer of abstraction and very useful<00:32:04.380> in<00:32:04.500> the<00:32:04.560> context<00:32:05.070> of<00:32:05.190> migrating<00:32:06.090> in<00:32:06.270> f1 00:32:06.860 --> 00:32:06.870 align:start position:0% useful in the context of migrating in f1 00:32:06.870 --> 00:32:09.170 align:start position:0% useful in the context of migrating in f1 into<00:32:07.110> if<00:32:07.350> -<00:32:07.560> but<00:32:08.190> there<00:32:08.370> is<00:32:08.520> also<00:32:08.790> the 00:32:09.170 --> 00:32:09.180 align:start position:0% into if - but there is also the 00:32:09.180 --> 00:32:12.950 align:start position:0% into if - but there is also the possibility<00:32:09.330> that<00:32:10.760> you<00:32:11.760> know<00:32:11.790> E's<00:32:12.390> you<00:32:12.870> know 00:32:12.950 --> 00:32:12.960 align:start position:0% possibility that you know E's you know 00:32:12.960 --> 00:32:15.800 align:start position:0% possibility that you know E's you know add<00:32:13.320> extra<00:32:13.980> friction<00:32:14.250> between<00:32:14.760> them<00:32:15.240> in 00:32:15.800 --> 00:32:15.810 align:start position:0% add extra friction between them in 00:32:15.810 --> 00:32:17.750 align:start position:0% add extra friction between them in addition<00:32:16.170> to<00:32:16.500> the<00:32:16.620> friction<00:32:17.130> between<00:32:17.160> shots 00:32:17.750 --> 00:32:17.760 align:start position:0% addition to the friction between shots 00:32:17.760 --> 00:32:21.020 align:start position:0% addition to the friction between shots and<00:32:19.040> you<00:32:20.040> know<00:32:20.190> there's<00:32:20.640> also<00:32:20.820> the 00:32:21.020 --> 00:32:21.030 align:start position:0% and you know there's also the 00:32:21.030 --> 00:32:21.950 align:start position:0% and you know there's also the possibility<00:32:21.180> that<00:32:21.540> we'll<00:32:21.780> have 00:32:21.950 --> 00:32:21.960 align:start position:0% possibility that we'll have 00:32:21.960 --> 00:32:24.680 align:start position:0% possibility that we'll have unsustainable<00:32:22.770> ease<00:32:23.040> so<00:32:23.520> ease<00:32:24.000> for<00:32:24.300> example 00:32:24.680 --> 00:32:24.690 align:start position:0% unsustainable ease so ease for example 00:32:24.690 --> 00:32:27.740 align:start position:0% unsustainable ease so ease for example without<00:32:25.250> statement<00:32:26.300> similar<00:32:27.300> to<00:32:27.540> what<00:32:27.660> we 00:32:27.740 --> 00:32:27.750 align:start position:0% without statement similar to what we 00:32:27.750 --> 00:32:29.390 align:start position:0% without statement similar to what we have<00:32:27.900> right<00:32:28.050> now<00:32:28.110> and<00:32:28.260> if<00:32:28.530> one<00:32:28.770> and<00:32:29.040> if<00:32:29.250> they 00:32:29.390 --> 00:32:29.400 align:start position:0% have right now and if one and if they 00:32:29.400 --> 00:32:32.360 align:start position:0% have right now and if one and if they become<00:32:29.580> popular<00:32:29.910> then<00:32:30.440> you<00:32:31.440> know<00:32:31.530> it's<00:32:31.920> all 00:32:32.360 --> 00:32:32.370 align:start position:0% become popular then you know it's all 00:32:32.370 --> 00:32:34.730 align:start position:0% become popular then you know it's all sorts<00:32:32.640> of<00:32:32.670> complicated<00:32:33.060> questions<00:32:33.570> so<00:32:33.900> it<00:32:34.470> is 00:32:34.730 --> 00:32:34.740 align:start position:0% sorts of complicated questions so it is 00:32:34.740 --> 00:32:37.550 align:start position:0% sorts of complicated questions so it is possible<00:32:35.040> that<00:32:35.580> at<00:32:36.240> least<00:32:36.510> in<00:32:36.900> the<00:32:37.140> short<00:32:37.410> and 00:32:37.550 --> 00:32:37.560 align:start position:0% possible that at least in the short and 00:32:37.560 --> 00:32:39.830 align:start position:0% possible that at least in the short and medium<00:32:37.950> term<00:32:37.980> we<00:32:38.640> will<00:32:38.820> roll<00:32:39.210> out<00:32:39.420> with<00:32:39.690> some 00:32:39.830 --> 00:32:39.840 align:start position:0% medium term we will roll out with some 00:32:39.840 --> 00:32:42.470 align:start position:0% medium term we will roll out with some sort<00:32:40.080> of<00:32:40.140> default<00:32:40.830> and<00:32:41.040> shrine<00:32:41.430> de<00:32:41.640> some<00:32:42.330> sort 00:32:42.470 --> 00:32:42.480 align:start position:0% sort of default and shrine de some sort 00:32:42.480 --> 00:32:46.100 align:start position:0% sort of default and shrine de some sort of<00:32:42.710> you<00:32:43.710> know<00:32:43.740> native<00:32:44.160> if<00:32:44.400> tui<00:32:44.700> which<00:32:45.180> just 00:32:46.100 --> 00:32:46.110 align:start position:0% of you know native if tui which just 00:32:46.110 --> 00:32:49.940 align:start position:0% of you know native if tui which just acts<00:32:46.590> and<00:32:46.980> behaves<00:32:47.100> like<00:32:48.560> somewhat<00:32:49.560> like<00:32:49.740> if 00:32:49.940 --> 00:32:49.950 align:start position:0% acts and behaves like somewhat like if 00:32:49.950 --> 00:32:52.190 align:start position:0% acts and behaves like somewhat like if one<00:32:50.190> does<00:32:50.550> today<00:32:50.850> and<00:32:51.060> you<00:32:51.390> won't<00:32:51.510> have<00:32:51.840> that 00:32:52.190 --> 00:32:52.200 align:start position:0% one does today and you won't have that 00:32:52.200 --> 00:32:55.130 align:start position:0% one does today and you won't have that much<00:32:52.590> room<00:32:53.250> to<00:32:53.280> play<00:32:53.490> with<00:32:53.720> in<00:32:54.720> the<00:32:54.870> medium 00:32:55.130 --> 00:32:55.140 align:start position:0% much room to play with in the medium 00:32:55.140 --> 00:32:57.620 align:start position:0% much room to play with in the medium term<00:32:55.350> and<00:32:55.590> then<00:32:56.430> in<00:32:56.610> the<00:32:56.700> long<00:32:56.850> term<00:32:57.060> we<00:32:57.270> open 00:32:57.620 --> 00:32:57.630 align:start position:0% term and then in the long term we open 00:32:57.630 --> 00:33:00.410 align:start position:0% term and then in the long term we open up<00:32:57.720> the<00:32:57.870> ease<00:32:58.020> to<00:32:58.170> everyone<00:32:59.150> rate<00:33:00.150> but<00:33:00.270> how<00:33:00.360> do 00:33:00.410 --> 00:33:00.420 align:start position:0% up the ease to everyone rate but how do 00:33:00.420 --> 00:33:03.980 align:start position:0% up the ease to everyone rate but how do you<00:33:00.540> manage<00:33:00.690> that<00:33:00.900> process<00:33:02.180> of<00:33:03.180> opening<00:33:03.750> up<00:33:03.870> to 00:33:03.980 --> 00:33:03.990 align:start position:0% you manage that process of opening up to 00:33:03.990 --> 00:33:06.260 align:start position:0% you manage that process of opening up to everyone<00:33:04.320> right<00:33:04.670> well<00:33:05.670> that<00:33:05.880> will<00:33:06.030> happen 00:33:06.260 --> 00:33:06.270 align:start position:0% everyone right well that will happen 00:33:06.270 --> 00:33:08.090 align:start position:0% everyone right well that will happen under<00:33:06.390> consensus<00:33:06.990> layer<00:33:07.170> and<00:33:07.440> one<00:33:07.590> day<00:33:07.740> we<00:33:07.920> say 00:33:08.090 --> 00:33:08.100 align:start position:0% under consensus layer and one day we say 00:33:08.100 --> 00:33:13.010 align:start position:0% under consensus layer and one day we say hey<00:33:08.580> anyone<00:33:08.940> can<00:33:09.180> can<00:33:09.480> publish<00:33:09.750> an<00:33:09.900> e<00:33:10.850> so<00:33:12.020> you 00:33:13.010 --> 00:33:13.020 align:start position:0% hey anyone can can publish an e so you 00:33:13.020 --> 00:33:14.390 align:start position:0% hey anyone can can publish an e so you know<00:33:13.110> going<00:33:13.500> back<00:33:13.590> to<00:33:13.740> the<00:33:13.830> permissioning 00:33:14.390 --> 00:33:14.400 align:start position:0% know going back to the permissioning 00:33:14.400 --> 00:33:18.170 align:start position:0% know going back to the permissioning question<00:33:14.820> maybe<00:33:15.060> they<00:33:15.330> you<00:33:15.690> know<00:33:16.850> no<00:33:17.850> one<00:33:18.030> will 00:33:18.170 --> 00:33:18.180 align:start position:0% question maybe they you know no one will 00:33:18.180 --> 00:33:20.390 align:start position:0% question maybe they you know no one will be<00:33:18.270> able<00:33:18.420> to<00:33:18.630> publish<00:33:18.780> is<00:33:19.050> for<00:33:19.440> some<00:33:19.590> time<00:33:19.830> I'm 00:33:20.390 --> 00:33:20.400 align:start position:0% be able to publish is for some time I'm 00:33:20.400 --> 00:33:21.680 align:start position:0% be able to publish is for some time I'm not<00:33:20.520> saying<00:33:20.730> it<00:33:20.850> will<00:33:20.970> happen<00:33:21.300> there<00:33:21.510> it's<00:33:21.630> a 00:33:21.680 --> 00:33:21.690 align:start position:0% not saying it will happen there it's a 00:33:21.690 --> 00:33:26.590 align:start position:0% not saying it will happen there it's a possibility 00:33:26.590 --> 00:33:26.600 align:start position:0% 00:33:26.600 --> 00:33:31.160 align:start position:0% all<00:33:27.600> right<00:33:27.750> questions<00:33:29.600> how<00:33:30.600> much<00:33:30.810> thought<00:33:30.990> is 00:33:31.160 --> 00:33:31.170 align:start position:0% all right questions how much thought is 00:33:31.170 --> 00:33:32.870 align:start position:0% all right questions how much thought is there<00:33:31.350> been<00:33:31.530> to<00:33:31.710> a<00:33:31.740> transparent<00:33:32.490> sharding 00:33:32.870 --> 00:33:32.880 align:start position:0% there been to a transparent sharding 00:33:32.880 --> 00:33:34.880 align:start position:0% there been to a transparent sharding where<00:33:33.060> that<00:33:33.570> developers<00:33:34.140> don't<00:33:34.350> have<00:33:34.470> to<00:33:34.770> UM 00:33:34.880 --> 00:33:34.890 align:start position:0% where that developers don't have to UM 00:33:34.890 --> 00:33:37.010 align:start position:0% where that developers don't have to UM figure<00:33:35.250> out<00:33:35.340> which<00:33:35.490> are<00:33:35.730> they<00:33:35.940> want<00:33:36.390> to<00:33:36.690> be<00:33:36.840> on 00:33:37.010 --> 00:33:37.020 align:start position:0% figure out which are they want to be on 00:33:37.020 --> 00:33:39.080 align:start position:0% figure out which are they want to be on because<00:33:37.440> if<00:33:38.280> you<00:33:38.430> give<00:33:38.580> them<00:33:38.700> that<00:33:38.880> choice 00:33:39.080 --> 00:33:39.090 align:start position:0% because if you give them that choice 00:33:39.090 --> 00:33:40.850 align:start position:0% because if you give them that choice maybe<00:33:39.510> they<00:33:39.720> all<00:33:39.810> just<00:33:40.050> all<00:33:40.200> choose<00:33:40.500> to<00:33:40.650> be<00:33:40.770> on 00:33:40.850 --> 00:33:40.860 align:start position:0% maybe they all just all choose to be on 00:33:40.860 --> 00:33:41.630 align:start position:0% maybe they all just all choose to be on the<00:33:40.980> same<00:33:41.160> shard 00:33:41.630 --> 00:33:41.640 align:start position:0% the same shard 00:33:41.640 --> 00:33:46.610 align:start position:0% the same shard I<00:33:44.120> mean<00:33:45.120> that's<00:33:45.300> one<00:33:45.450> of<00:33:45.540> the<00:33:45.660> really<00:33:46.410> good 00:33:46.610 --> 00:33:46.620 align:start position:0% I mean that's one of the really good 00:33:46.620 --> 00:33:48.740 align:start position:0% I mean that's one of the really good benefits<00:33:46.740> of<00:33:47.250> opening<00:33:47.730> up<00:33:47.850> two<00:33:47.970> E's<00:33:48.330> is<00:33:48.570> that 00:33:48.740 --> 00:33:48.750 align:start position:0% benefits of opening up two E's is that 00:33:48.750 --> 00:33:50.570 align:start position:0% benefits of opening up two E's is that all<00:33:48.930> this<00:33:49.080> innovation<00:33:49.290> on<00:33:49.890> transparent 00:33:50.570 --> 00:33:50.580 align:start position:0% all this innovation on transparent 00:33:50.580 --> 00:33:52.460 align:start position:0% all this innovation on transparent shouting<00:33:50.940> can<00:33:51.270> be<00:33:51.450> done<00:33:51.660> at<00:33:51.840> the<00:33:51.960> application 00:33:52.460 --> 00:33:52.470 align:start position:0% shouting can be done at the application 00:33:52.470 --> 00:33:55.280 align:start position:0% shouting can be done at the application layer<00:33:52.590> and<00:33:53.090> assess<00:33:54.090> consensus<00:33:54.660> like 00:33:55.280 --> 00:33:55.290 align:start position:0% layer and assess consensus like 00:33:55.290 --> 00:33:57.050 align:start position:0% layer and assess consensus like designers<00:33:55.950> we<00:33:56.100> don't<00:33:56.280> have<00:33:56.370> to<00:33:56.490> bother<00:33:56.910> about 00:33:57.050 --> 00:33:57.060 align:start position:0% designers we don't have to bother about 00:33:57.060 --> 00:34:01.400 align:start position:0% designers we don't have to bother about that<00:33:57.450> and<00:33:58.350> so<00:33:58.500> if<00:33:58.650> if<00:33:59.340> you<00:33:59.850> nail<00:34:00.360> polka<00:34:00.990> dot<00:34:01.260> or 00:34:01.400 --> 00:34:01.410 align:start position:0% that and so if if you nail polka dot or 00:34:01.410 --> 00:34:02.840 align:start position:0% that and so if if you nail polka dot or whatever<00:34:01.680> comes<00:34:01.980> up<00:34:02.130> with<00:34:02.310> some<00:34:02.490> cool 00:34:02.840 --> 00:34:02.850 align:start position:0% whatever comes up with some cool 00:34:02.850 --> 00:34:05.630 align:start position:0% whatever comes up with some cool innovation<00:34:03.390> that<00:34:03.570> can<00:34:03.810> be<00:34:03.960> integrated<00:34:04.640> with 00:34:05.630 --> 00:34:05.640 align:start position:0% innovation that can be integrated with 00:34:05.640 --> 00:34:08.030 align:start position:0% innovation that can be integrated with very<00:34:05.940> little<00:34:06.300> friction<00:34:06.770> and<00:34:07.770> there's<00:34:07.920> already 00:34:08.030 --> 00:34:08.040 align:start position:0% very little friction and there's already 00:34:08.040 --> 00:34:10.670 align:start position:0% very little friction and there's already ideas<00:34:08.580> out<00:34:08.940> there<00:34:09.270> for 00:34:10.670 --> 00:34:10.680 align:start position:0% ideas out there for 00:34:10.680 --> 00:34:13.640 align:start position:0% ideas out there for you<00:34:10.920> know<00:34:11.010> using<00:34:11.460> the<00:34:11.580> shards<00:34:12.060> as<00:34:12.560> you<00:34:13.560> know 00:34:13.640 --> 00:34:13.650 align:start position:0% you know using the shards as you know 00:34:13.650 --> 00:34:18.110 align:start position:0% you know using the shards as you know fungible<00:34:14.810> data<00:34:15.810> availability<00:34:16.320> resource<00:34:17.190> that 00:34:18.110 --> 00:34:18.120 align:start position:0% fungible data availability resource that 00:34:18.120 --> 00:34:23.950 align:start position:0% fungible data availability resource that can<00:34:18.300> be<00:34:18.420> used<00:34:20.180> and<00:34:21.180> kind<00:34:21.570> of<00:34:21.630> decoupling<00:34:22.470> the 00:34:23.950 --> 00:34:23.960 align:start position:0% can be used and kind of decoupling the 00:34:23.960 --> 00:34:26.570 align:start position:0% can be used and kind of decoupling the the<00:34:24.960> the<00:34:25.140> logical<00:34:25.590> centralization<00:34:26.340> of<00:34:26.520> the 00:34:26.570 --> 00:34:26.580 align:start position:0% the the logical centralization of the 00:34:26.580 --> 00:34:28.970 align:start position:0% the the logical centralization of the application<00:34:27.210> from<00:34:27.570> the<00:34:27.810> underlying<00:34:28.320> resource 00:34:28.970 --> 00:34:28.980 align:start position:0% application from the underlying resource 00:34:28.980 --> 00:34:31.490 align:start position:0% application from the underlying resource which<00:34:29.220> is<00:34:29.250> shorted<00:34:29.880> who<00:34:30.750> decides<00:34:31.110> where<00:34:31.380> the 00:34:31.490 --> 00:34:31.500 align:start position:0% which is shorted who decides where the 00:34:31.500 --> 00:34:33.170 align:start position:0% which is shorted who decides where the application<00:34:32.070> goes<00:34:32.310> like<00:34:32.850> does<00:34:33.090> the 00:34:33.170 --> 00:34:33.180 align:start position:0% application goes like does the 00:34:33.180 --> 00:34:34.640 align:start position:0% application goes like does the application<00:34:33.630> get<00:34:33.780> to<00:34:33.900> decide<00:34:34.080> what<00:34:34.290> shard<00:34:34.500> it 00:34:34.640 --> 00:34:34.650 align:start position:0% application get to decide what shard it 00:34:34.650 --> 00:34:36.830 align:start position:0% application get to decide what shard it goes<00:34:34.800> on<00:34:34.980> or<00:34:35.520> is<00:34:35.670> it<00:34:35.790> do<00:34:36.300> they<00:34:36.420> have<00:34:36.540> no<00:34:36.660> control 00:34:36.830 --> 00:34:36.840 align:start position:0% goes on or is it do they have no control 00:34:36.840 --> 00:34:41.750 align:start position:0% goes on or is it do they have no control over<00:34:36.990> that<00:34:37.200> I<00:34:38.630> mean<00:34:39.770> at<00:34:40.770> the<00:34:40.860> lower<00:34:41.070> level<00:34:41.430> the 00:34:41.750 --> 00:34:41.760 align:start position:0% over that I mean at the lower level the 00:34:41.760 --> 00:34:44.840 align:start position:0% over that I mean at the lower level the every<00:34:42.330> de<00:34:42.660> lives<00:34:43.650> in<00:34:43.920> the<00:34:44.010> beacon<00:34:44.310> chain<00:34:44.550> and 00:34:44.840 --> 00:34:44.850 align:start position:0% every de lives in the beacon chain and 00:34:44.850 --> 00:34:47.270 align:start position:0% every de lives in the beacon chain and it's<00:34:45.270> made<00:34:45.480> accessible<00:34:45.780> to<00:34:46.050> every<00:34:46.440> shard<00:34:46.710> but 00:34:47.270 --> 00:34:47.280 align:start position:0% it's made accessible to every shard but 00:34:47.280 --> 00:34:52.550 align:start position:0% it's made accessible to every shard but then<00:34:47.490> you<00:34:48.480> know<00:34:49.700> then<00:34:50.700> it<00:34:51.690> becomes<00:34:52.440> a<00:34:52.530> question 00:34:52.550 --> 00:34:52.560 align:start position:0% then you know then it becomes a question 00:34:52.560 --> 00:34:55.610 align:start position:0% then you know then it becomes a question of<00:34:53.270> for<00:34:54.270> the<00:34:54.360> dab<00:34:54.510> developers<00:34:55.020> how<00:34:55.260> do<00:34:55.320> they 00:34:55.610 --> 00:34:55.620 align:start position:0% of for the dab developers how do they 00:34:55.620 --> 00:34:58.880 align:start position:0% of for the dab developers how do they want<00:34:55.920> to<00:34:56.220> you<00:34:57.210> know<00:34:57.300> I've<00:34:57.540> you<00:34:58.050> know<00:34:58.080> restrict 00:34:58.880 --> 00:34:58.890 align:start position:0% want to you know I've you know restrict 00:34:58.890 --> 00:35:02.690 align:start position:0% want to you know I've you know restrict themselves<00:34:59.190> to<00:34:59.520> a<00:34:59.640> specific<00:35:00.060> shard<00:35:00.590> or<00:35:01.700> have 00:35:02.690 --> 00:35:02.700 align:start position:0% themselves to a specific shard or have 00:35:02.700 --> 00:35:05.330 align:start position:0% themselves to a specific shard or have some<00:35:02.880> sort<00:35:03.030> of<00:35:03.060> virtual<00:35:03.600> or<00:35:04.200> virtual<00:35:05.040> virtual 00:35:05.330 --> 00:35:05.340 align:start position:0% some sort of virtual or virtual virtual 00:35:05.340 --> 00:35:08.330 align:start position:0% some sort of virtual or virtual virtual execution<00:35:06.000> environment<00:35:06.900> which<00:35:07.080> is<00:35:07.340> separate 00:35:08.330 --> 00:35:08.340 align:start position:0% execution environment which is separate 00:35:08.340 --> 00:35:13.120 align:start position:0% execution environment which is separate from<00:35:08.520> the<00:35:08.730> the<00:35:09.240> consensus<00:35:09.810> level<00:35:10.170> concept 00:35:13.120 --> 00:35:13.130 align:start position:0% 00:35:13.130 --> 00:35:15.830 align:start position:0% also<00:35:14.130> within<00:35:14.340> e<00:35:14.790> development<00:35:15.630> there's 00:35:15.830 --> 00:35:15.840 align:start position:0% also within e development there's 00:35:15.840 --> 00:35:17.780 align:start position:0% also within e development there's there's<00:35:16.290> a<00:35:16.380> few<00:35:16.530> things<00:35:16.710> you<00:35:16.830> can<00:35:16.950> do<00:35:17.100> and<00:35:17.310> you 00:35:17.780 --> 00:35:17.790 align:start position:0% there's a few things you can do and you 00:35:17.790 --> 00:35:21.080 align:start position:0% there's a few things you can do and you know<00:35:17.880> when<00:35:18.060> when<00:35:18.420> this<00:35:18.540> opens<00:35:18.930> up<00:35:19.050> as<00:35:19.410> well<00:35:20.090> I 00:35:21.080 --> 00:35:21.090 align:start position:0% know when when this opens up as well I 00:35:21.090 --> 00:35:22.700 align:start position:0% know when when this opens up as well I think<00:35:21.750> there<00:35:21.870> are<00:35:21.900> a<00:35:21.960> couple<00:35:22.110> questions<00:35:22.350> so 00:35:22.700 --> 00:35:22.710 align:start position:0% think there are a couple questions so 00:35:22.710 --> 00:35:25.010 align:start position:0% think there are a couple questions so one<00:35:22.920> one<00:35:23.280> question<00:35:23.430> is<00:35:23.850> do<00:35:24.630> you<00:35:24.660> have<00:35:24.750> to 00:35:25.010 --> 00:35:25.020 align:start position:0% one one question is do you have to 00:35:25.020 --> 00:35:26.930 align:start position:0% one one question is do you have to deploy<00:35:25.290> to<00:35:25.530> the<00:35:25.560> beacon<00:35:25.860> chain<00:35:26.070> and<00:35:26.340> do<00:35:26.850> you 00:35:26.930 --> 00:35:26.940 align:start position:0% deploy to the beacon chain and do you 00:35:26.940 --> 00:35:28.990 align:start position:0% deploy to the beacon chain and do you also<00:35:27.090> have<00:35:27.300> to<00:35:27.420> deploy<00:35:27.630> to<00:35:28.050> multiple<00:35:28.080> shards 00:35:28.990 --> 00:35:29.000 align:start position:0% also have to deploy to multiple shards 00:35:29.000 --> 00:35:31.190 align:start position:0% also have to deploy to multiple shards or<00:35:30.000> do<00:35:30.120> you<00:35:30.210> automatically<00:35:30.960> have<00:35:31.170> it 00:35:31.190 --> 00:35:31.200 align:start position:0% or do you automatically have it 00:35:31.200 --> 00:35:34.190 align:start position:0% or do you automatically have it available<00:35:31.470> across<00:35:32.160> all<00:35:32.430> the<00:35:32.550> shards<00:35:33.200> so 00:35:34.190 --> 00:35:34.200 align:start position:0% available across all the shards so 00:35:34.200 --> 00:35:36.230 align:start position:0% available across all the shards so that's<00:35:34.350> one<00:35:34.530> piece<00:35:34.740> but<00:35:35.280> also<00:35:35.550> within<00:35:35.940> your 00:35:36.230 --> 00:35:36.240 align:start position:0% that's one piece but also within your 00:35:36.240 --> 00:35:38.030 align:start position:0% that's one piece but also within your execution<00:35:36.810> environment<00:35:37.290> you<00:35:37.860> could 00:35:38.030 --> 00:35:38.040 align:start position:0% execution environment you could 00:35:38.040 --> 00:35:43.100 align:start position:0% execution environment you could technically<00:35:38.610> build<00:35:40.250> some<00:35:41.570> basic<00:35:42.570> level<00:35:42.780> of 00:35:43.100 --> 00:35:43.110 align:start position:0% technically build some basic level of 00:35:43.110 --> 00:35:44.740 align:start position:0% technically build some basic level of scheduling<00:35:43.680> yourself<00:35:44.100> as<00:35:44.280> well 00:35:44.740 --> 00:35:44.750 align:start position:0% scheduling yourself as well 00:35:44.750 --> 00:35:49.940 align:start position:0% scheduling yourself as well saying<00:35:45.750> I<00:35:46.110> will<00:35:46.800> only<00:35:47.130> operates<00:35:47.640> or<00:35:47.970> in<00:35:48.950> you 00:35:49.940 --> 00:35:49.950 align:start position:0% saying I will only operates or in you 00:35:49.950 --> 00:35:52.820 align:start position:0% saying I will only operates or in you know<00:35:49.980> certain<00:35:50.370> transactions<00:35:51.260> on<00:35:52.260> short<00:35:52.590> five 00:35:52.820 --> 00:35:52.830 align:start position:0% know certain transactions on short five 00:35:52.830 --> 00:35:53.690 align:start position:0% know certain transactions on short five four 00:35:53.690 --> 00:35:53.700 align:start position:0% four 00:35:53.700 --> 00:35:56.510 align:start position:0% four you<00:35:53.790> know<00:35:53.910> this<00:35:54.210> series<00:35:54.750> of<00:35:54.900> epics<00:35:55.260> or<00:35:55.530> shard 00:35:56.510 --> 00:35:56.520 align:start position:0% you know this series of epics or shard 00:35:56.520 --> 00:35:58.580 align:start position:0% you know this series of epics or shard five<00:35:56.730> six<00:35:57.210> and<00:35:57.390> seven<00:35:57.480> for<00:35:57.930> this<00:35:58.080> series<00:35:58.470> of 00:35:58.580 --> 00:35:58.590 align:start position:0% five six and seven for this series of 00:35:58.590 --> 00:36:00.920 align:start position:0% five six and seven for this series of epics<00:35:58.970> so<00:35:59.970> there's<00:36:00.120> a<00:36:00.180> lot<00:36:00.300> of<00:36:00.390> flexibility 00:36:00.920 --> 00:36:00.930 align:start position:0% epics so there's a lot of flexibility 00:36:00.930 --> 00:36:03.050 align:start position:0% epics so there's a lot of flexibility and<00:36:01.020> how<00:36:01.230> how<00:36:01.620> you<00:36:01.680> can<00:36:01.890> write<00:36:02.040> these<00:36:02.250> and<00:36:02.610> how 00:36:03.050 --> 00:36:03.060 align:start position:0% and how how you can write these and how 00:36:03.060 --> 00:36:04.550 align:start position:0% and how how you can write these and how you<00:36:03.120> may<00:36:03.330> be<00:36:03.360> able<00:36:03.630> to<00:36:03.840> enforce<00:36:04.260> the<00:36:04.440> load 00:36:04.550 --> 00:36:04.560 align:start position:0% you may be able to enforce the load 00:36:04.560 --> 00:36:07.640 align:start position:0% you may be able to enforce the load balancing<00:36:05.130> yourself<00:36:06.090> just<00:36:06.840> within<00:36:07.080> the 00:36:07.640 --> 00:36:07.650 align:start position:0% balancing yourself just within the 00:36:07.650 --> 00:36:09.020 align:start position:0% balancing yourself just within the semantics<00:36:08.190> behind<00:36:08.490> an<00:36:08.580> execution 00:36:09.020 --> 00:36:09.030 align:start position:0% semantics behind an execution 00:36:09.030 --> 00:36:13.260 align:start position:0% semantics behind an execution environment 00:36:13.260 --> 00:36:13.270 align:start position:0% 00:36:13.270 --> 00:36:18.220 align:start position:0% are<00:36:14.270> we<00:36:14.390> going<00:36:14.600> to<00:36:14.690> retain<00:36:15.220> the<00:36:17.230> financial 00:36:18.220 --> 00:36:18.230 align:start position:0% are we going to retain the financial 00:36:18.230 --> 00:36:22.240 align:start position:0% are we going to retain the financial Lego<00:36:19.600> that<00:36:20.600> we've<00:36:20.720> got<00:36:20.930> a<00:36:21.140> plug<00:36:22.040> and<00:36:22.190> play 00:36:22.240 --> 00:36:22.250 align:start position:0% Lego that we've got a plug and play 00:36:22.250 --> 00:36:24.850 align:start position:0% Lego that we've got a plug and play between<00:36:23.620> composability 00:36:24.850 --> 00:36:24.860 align:start position:0% between composability 00:36:24.860 --> 00:36:29.470 align:start position:0% between composability that<00:36:25.430> are<00:36:25.610> we<00:36:25.730> losing<00:36:26.030> that<00:36:26.390> or<00:36:28.480> compromising 00:36:29.470 --> 00:36:29.480 align:start position:0% that are we losing that or compromising 00:36:29.480 --> 00:36:34.180 align:start position:0% that are we losing that or compromising that<00:36:29.630> with<00:36:29.960> the<00:36:30.080> sharding<00:36:32.710> from<00:36:33.710> a<00:36:33.800> tooling 00:36:34.180 --> 00:36:34.190 align:start position:0% that with the sharding from a tooling 00:36:34.190 --> 00:36:37.780 align:start position:0% that with the sharding from a tooling perspective<00:36:34.760> well<00:36:35.660> right<00:36:35.870> now<00:36:36.050> you<00:36:36.110> can<00:36:36.790> you 00:36:37.780 --> 00:36:37.790 align:start position:0% perspective well right now you can you 00:36:37.790 --> 00:36:40.570 align:start position:0% perspective well right now you can you know<00:36:37.910> you<00:36:38.240> can<00:36:38.420> plug<00:36:39.130> compound<00:36:40.130> and<00:36:40.400> die 00:36:40.570 --> 00:36:40.580 align:start position:0% know you can plug compound and die 00:36:40.580 --> 00:36:43.870 align:start position:0% know you can plug compound and die together<00:36:41.090> or<00:36:41.480> something<00:36:41.920> if<00:36:42.920> you<00:36:43.370> don't<00:36:43.640> know 00:36:43.870 --> 00:36:43.880 align:start position:0% together or something if you don't know 00:36:43.880 --> 00:36:45.970 align:start position:0% together or something if you don't know if<00:36:44.090> your<00:36:44.480> Lego<00:36:44.720> blocks<00:36:45.080> are<00:36:45.290> now<00:36:45.410> on<00:36:45.590> different 00:36:45.970 --> 00:36:45.980 align:start position:0% if your Lego blocks are now on different 00:36:45.980 --> 00:36:48.940 align:start position:0% if your Lego blocks are now on different shards<00:36:46.340> and<00:36:46.460> they<00:36:46.880> can't<00:36:47.120> interrupt<00:36:47.950> without 00:36:48.940 --> 00:36:48.950 align:start position:0% shards and they can't interrupt without 00:36:48.950 --> 00:36:51.730 align:start position:0% shards and they can't interrupt without cross<00:36:49.760> shard<00:36:50.000> links<00:36:50.390> which<00:36:51.110> might<00:36:51.320> be<00:36:51.470> slower 00:36:51.730 --> 00:36:51.740 align:start position:0% cross shard links which might be slower 00:36:51.740 --> 00:36:57.820 align:start position:0% cross shard links which might be slower and<00:36:52.100> have<00:36:52.310> some<00:36:52.490> penalty<00:36:55.510> I<00:36:56.510> mean<00:36:57.350> I<00:36:57.470> get<00:36:57.680> the 00:36:57.820 --> 00:36:57.830 align:start position:0% and have some penalty I mean I get the 00:36:57.830 --> 00:37:00.550 align:start position:0% and have some penalty I mean I get the concern<00:36:58.340> but<00:36:58.580> I<00:36:58.700> think<00:36:59.090> all<00:36:59.630> of<00:36:59.660> the<00:36:59.990> kind<00:37:00.200> of<00:37:00.290> T 00:37:00.550 --> 00:37:00.560 align:start position:0% concern but I think all of the kind of T 00:37:00.560 --> 00:37:02.650 align:start position:0% concern but I think all of the kind of T Phi<00:37:00.770> integrations<00:37:01.580> like<00:37:01.910> for<00:37:02.150> just<00:37:02.300> as<00:37:02.450> one 00:37:02.650 --> 00:37:02.660 align:start position:0% Phi integrations like for just as one 00:37:02.660 --> 00:37:04.480 align:start position:0% Phi integrations like for just as one example<00:37:02.810> I've<00:37:03.290> seen<00:37:03.470> in<00:37:03.650> practice<00:37:04.130> I<00:37:04.310> don't 00:37:04.480 --> 00:37:04.490 align:start position:0% example I've seen in practice I don't 00:37:04.490 --> 00:37:06.070 align:start position:0% example I've seen in practice I don't think<00:37:04.700> any<00:37:04.880> of<00:37:05.000> them<00:37:05.210> really<00:37:05.450> break<00:37:05.780> from<00:37:05.960> me 00:37:06.070 --> 00:37:06.080 align:start position:0% think any of them really break from me 00:37:06.080 --> 00:37:08.500 align:start position:0% think any of them really break from me synchrony<00:37:06.530> one<00:37:07.490> of<00:37:07.610> the<00:37:07.730> reasons<00:37:08.060> why<00:37:08.270> is<00:37:08.330> that 00:37:08.500 --> 00:37:08.510 align:start position:0% synchrony one of the reasons why is that 00:37:08.510 --> 00:37:10.390 align:start position:0% synchrony one of the reasons why is that half<00:37:08.870> of<00:37:09.020> these<00:37:09.170> integrations<00:37:09.830> just<00:37:10.100> happen 00:37:10.390 --> 00:37:10.400 align:start position:0% half of these integrations just happen 00:37:10.400 --> 00:37:12.250 align:start position:0% half of these integrations just happen to<00:37:10.520> do<00:37:10.670> with<00:37:10.790> like<00:37:11.000> one<00:37:11.240> system<00:37:11.630> containing<00:37:12.170> a 00:37:12.250 --> 00:37:12.260 align:start position:0% to do with like one system containing a 00:37:12.260 --> 00:37:14.800 align:start position:0% to do with like one system containing a token<00:37:12.590> from<00:37:12.710> another<00:37:13.010> system<00:37:13.520> but<00:37:14.180> tokens<00:37:14.660> are 00:37:14.800 --> 00:37:14.810 align:start position:0% token from another system but tokens are 00:37:14.810 --> 00:37:16.720 align:start position:0% token from another system but tokens are a<00:37:14.840> thing<00:37:15.320> that's<00:37:15.560> like<00:37:15.830> they've<00:37:16.100> probably 00:37:16.720 --> 00:37:16.730 align:start position:0% a thing that's like they've probably 00:37:16.730 --> 00:37:18.310 align:start position:0% a thing that's like they've probably easier<00:37:17.210> than<00:37:17.390> anything<00:37:17.600> else<00:37:17.840> to<00:37:17.930> move<00:37:18.110> across 00:37:18.310 --> 00:37:18.320 align:start position:0% easier than anything else to move across 00:37:18.320 --> 00:37:20.830 align:start position:0% easier than anything else to move across shards<00:37:18.770> you<00:37:18.950> just<00:37:19.190> like<00:37:19.460> yank<00:37:20.210> the<00:37:20.360> contract 00:37:20.830 --> 00:37:20.840 align:start position:0% shards you just like yank the contract 00:37:20.840 --> 00:37:23.560 align:start position:0% shards you just like yank the contract over<00:37:21.170> and<00:37:21.380> like<00:37:21.650> one<00:37:21.890> one<00:37:22.730> myrtle<00:37:23.090> branches 00:37:23.560 --> 00:37:23.570 align:start position:0% over and like one one myrtle branches 00:37:23.570 --> 00:37:25.870 align:start position:0% over and like one one myrtle branches and<00:37:24.530> it's<00:37:24.740> like<00:37:25.070> somewhere<00:37:25.400> else<00:37:25.550> wherever 00:37:25.870 --> 00:37:25.880 align:start position:0% and it's like somewhere else wherever 00:37:25.880 --> 00:37:32.100 align:start position:0% and it's like somewhere else wherever you<00:37:26.060> want<00:37:26.240> it<00:37:26.360> to<00:37:26.390> be<00:37:26.630> him<00:37:26.720> I<00:37:27.250> think<00:37:29.320> the<00:37:30.320> thing 00:37:32.100 --> 00:37:32.110 align:start position:0% you want it to be him I think the thing 00:37:32.110 --> 00:37:35.500 align:start position:0% you want it to be him I think the thing and<00:37:33.110> then<00:37:33.380> if<00:37:33.530> you<00:37:33.680> look<00:37:33.920> at<00:37:34.070> like<00:37:34.340> even<00:37:34.670> unit 00:37:35.500 --> 00:37:35.510 align:start position:0% and then if you look at like even unit 00:37:35.510 --> 00:37:37.300 align:start position:0% and then if you look at like even unit swap<00:37:35.750> for<00:37:35.960> example<00:37:36.440> just<00:37:36.740> moves<00:37:36.920> tokens 00:37:37.300 --> 00:37:37.310 align:start position:0% swap for example just moves tokens 00:37:37.310 --> 00:37:38.590 align:start position:0% swap for example just moves tokens around<00:37:37.580> you<00:37:37.670> move<00:37:37.760> the<00:37:37.910> token<00:37:38.210> to<00:37:38.240> the<00:37:38.330> unit 00:37:38.590 --> 00:37:38.600 align:start position:0% around you move the token to the unit 00:37:38.600 --> 00:37:40.150 align:start position:0% around you move the token to the unit swap<00:37:38.780> shard<00:37:39.050> swap<00:37:39.380> it<00:37:39.560> move<00:37:39.710> a<00:37:39.800> token 00:37:40.150 --> 00:37:40.160 align:start position:0% swap shard swap it move a token 00:37:40.160 --> 00:37:43.720 align:start position:0% swap shard swap it move a token somewhere<00:37:40.640> else<00:37:40.790> so<00:37:41.830> most<00:37:42.830> of<00:37:43.130> the<00:37:43.310> the 00:37:43.720 --> 00:37:43.730 align:start position:0% somewhere else so most of the the 00:37:43.730 --> 00:37:46.000 align:start position:0% somewhere else so most of the the integrations<00:37:44.420> do<00:37:44.660> kind<00:37:44.870> of<00:37:44.990> work<00:37:45.230> like<00:37:45.530> work 00:37:46.000 --> 00:37:46.010 align:start position:0% integrations do kind of work like work 00:37:46.010 --> 00:37:47.890 align:start position:0% integrations do kind of work like work that<00:37:46.280> way<00:37:46.460> the<00:37:46.790> ones<00:37:47.240> that<00:37:47.450> don't<00:37:47.630> are 00:37:47.890 --> 00:37:47.900 align:start position:0% that way the ones that don't are 00:37:47.900 --> 00:37:49.960 align:start position:0% that way the ones that don't are basically<00:37:48.440> the<00:37:48.590> ones<00:37:48.770> that<00:37:48.980> involve<00:37:49.280> kind<00:37:49.850> of 00:37:49.960 --> 00:37:49.970 align:start position:0% basically the ones that involve kind of 00:37:49.970 --> 00:37:51.850 align:start position:0% basically the ones that involve kind of synchronous<00:37:50.480> we<00:37:50.630> calling<00:37:50.960> other<00:37:51.140> Apple<00:37:51.470> other 00:37:51.850 --> 00:37:51.860 align:start position:0% synchronous we calling other Apple other 00:37:51.860 --> 00:37:54.580 align:start position:0% synchronous we calling other Apple other applications<00:37:52.640> but<00:37:53.000> like<00:37:53.180> even<00:37:53.960> in<00:37:54.230> that<00:37:54.350> case 00:37:54.580 --> 00:37:54.590 align:start position:0% applications but like even in that case 00:37:54.590 --> 00:37:56.530 align:start position:0% applications but like even in that case a<00:37:54.800> lot<00:37:54.980> of<00:37:55.100> a<00:37:55.250> lot<00:37:55.430> of<00:37:55.550> the<00:37:55.670> calls<00:37:55.850> are<00:37:56.030> AC<00:37:56.210> like 00:37:56.530 --> 00:37:56.540 align:start position:0% a lot of a lot of the calls are AC like 00:37:56.540 --> 00:37:58.930 align:start position:0% a lot of a lot of the calls are AC like dude<00:37:56.780> tends<00:37:57.140> to<00:37:57.350> be<00:37:57.470> a<00:37:57.500> a<00:37:57.800> synchronous<00:37:58.700> or<00:37:58.880> at 00:37:58.930 --> 00:37:58.940 align:start position:0% dude tends to be a a synchronous or at 00:37:58.940 --> 00:38:00.340 align:start position:0% dude tends to be a a synchronous or at least<00:37:59.120> would<00:37:59.300> be<00:37:59.330> perfectly<00:37:59.780> fine<00:37:59.900> if<00:38:00.260> you 00:38:00.340 --> 00:38:00.350 align:start position:0% least would be perfectly fine if you 00:38:00.350 --> 00:38:01.750 align:start position:0% least would be perfectly fine if you didn't<00:38:00.710> move<00:38:00.770> in<00:38:01.040> did<00:38:01.430> them<00:38:01.580> in<00:38:01.640> an 00:38:01.750 --> 00:38:01.760 align:start position:0% didn't move in did them in an 00:38:01.760 --> 00:38:05.260 align:start position:0% didn't move in did them in an asynchronous<00:38:02.180> way<00:38:02.480> so<00:38:03.370> now<00:38:04.370> we<00:38:04.580> start<00:38:04.640> given 00:38:05.260 --> 00:38:05.270 align:start position:0% asynchronous way so now we start given 00:38:05.270 --> 00:38:06.910 align:start position:0% asynchronous way so now we start given the<00:38:05.390> applications<00:38:06.080> that<00:38:06.170> we<00:38:06.410> know<00:38:06.590> about<00:38:06.740> I 00:38:06.910 --> 00:38:06.920 align:start position:0% the applications that we know about I 00:38:06.920 --> 00:38:09.280 align:start position:0% the applications that we know about I think<00:38:07.280> that's<00:38:07.520> a<00:38:07.730> you<00:38:07.790> kind<00:38:07.970> of<00:38:08.120> like<00:38:09.110> a 00:38:09.280 --> 00:38:09.290 align:start position:0% think that's a you kind of like a 00:38:09.290 --> 00:38:11.260 align:start position:0% think that's a you kind of like a smaller<00:38:09.860> risk<00:38:10.160> that<00:38:10.370> a<00:38:10.430> lot<00:38:10.610> of<00:38:10.640> people<00:38:11.000> think 00:38:11.260 --> 00:38:11.270 align:start position:0% smaller risk that a lot of people think 00:38:11.270 --> 00:38:14.020 align:start position:0% smaller risk that a lot of people think I<00:38:11.510> mean<00:38:12.230> I<00:38:12.380> could<00:38:12.590> see<00:38:12.890> like<00:38:13.190> execution 00:38:14.020 --> 00:38:14.030 align:start position:0% I mean I could see like execution 00:38:14.030 --> 00:38:16.470 align:start position:0% I mean I could see like execution environment<00:38:14.570> fragmentation<00:38:15.410> being<00:38:15.830> in<00:38:16.010> up 00:38:16.470 --> 00:38:16.480 align:start position:0% environment fragmentation being in up 00:38:16.480 --> 00:38:18.750 align:start position:0% environment fragmentation being in up even<00:38:16.839> a<00:38:17.050> bigger<00:38:17.320> issue<00:38:17.530> than<00:38:17.859> shorter<00:38:18.310> than 00:38:18.750 --> 00:38:18.760 align:start position:0% even a bigger issue than shorter than 00:38:18.760 --> 00:38:20.910 align:start position:0% even a bigger issue than shorter than short<00:38:19.540> fragmentation<00:38:20.380> if<00:38:20.500> not<00:38:20.680> handled 00:38:20.910 --> 00:38:20.920 align:start position:0% short fragmentation if not handled 00:38:20.920 --> 00:38:23.250 align:start position:0% short fragmentation if not handled correctly<00:38:21.250> and<00:38:21.760> that's<00:38:21.820> it's<00:38:22.810> definitely 00:38:23.250 --> 00:38:23.260 align:start position:0% correctly and that's it's definitely 00:38:23.260 --> 00:38:24.930 align:start position:0% correctly and that's it's definitely something<00:38:23.500> that<00:38:23.650> we're<00:38:23.950> thinking<00:38:24.700> very 00:38:24.930 --> 00:38:24.940 align:start position:0% something that we're thinking very 00:38:24.940 --> 00:38:30.750 align:start position:0% something that we're thinking very actively<00:38:25.540> about<00:38:25.839> how<00:38:25.960> to<00:38:26.020> smooth<00:38:26.320> over<00:38:29.550> and<00:38:30.550> I 00:38:30.750 --> 00:38:30.760 align:start position:0% actively about how to smooth over and I 00:38:30.760 --> 00:38:32.910 align:start position:0% actively about how to smooth over and I mean<00:38:30.940> concretely<00:38:31.359> it<00:38:32.079> might<00:38:32.440> turn<00:38:32.710> out<00:38:32.859> that 00:38:32.910 --> 00:38:32.920 align:start position:0% mean concretely it might turn out that 00:38:32.920 --> 00:38:34.400 align:start position:0% mean concretely it might turn out that crush<00:38:33.430> team<00:38:33.670> communication<00:38:34.089> is<00:38:34.300> actually 00:38:34.400 --> 00:38:34.410 align:start position:0% crush team communication is actually 00:38:34.410 --> 00:38:38.670 align:start position:0% crush team communication is actually faster<00:38:35.410> on<00:38:35.710> if<00:38:35.980> -<00:38:36.280> then<00:38:36.910> you<00:38:37.869> know<00:38:37.990> an<00:38:38.230> f1 00:38:38.670 --> 00:38:38.680 align:start position:0% faster on if - then you know an f1 00:38:38.680 --> 00:38:41.130 align:start position:0% faster on if - then you know an f1 transaction<00:38:39.250> if<00:38:39.940> one<00:38:40.210> on<00:38:40.390> average<00:38:40.690> is<00:38:40.839> 15 00:38:41.130 --> 00:38:41.140 align:start position:0% transaction if one on average is 15 00:38:41.140 --> 00:38:43.920 align:start position:0% transaction if one on average is 15 seconds<00:38:41.560> and<00:38:41.859> you<00:38:42.609> know<00:38:42.700> two<00:38:43.300> ways<00:38:43.510> that<00:38:43.810> we 00:38:43.920 --> 00:38:43.930 align:start position:0% seconds and you know two ways that we 00:38:43.930 --> 00:38:45.120 align:start position:0% seconds and you know two ways that we could<00:38:44.079> have<00:38:44.260> fast<00:38:44.619> crushed<00:38:44.980> our 00:38:45.120 --> 00:38:45.130 align:start position:0% could have fast crushed our 00:38:45.130 --> 00:38:46.890 align:start position:0% could have fast crushed our communication<00:38:45.640> is<00:38:45.760> one<00:38:46.089> we<00:38:46.359> have<00:38:46.390> this<00:38:46.750> new 00:38:46.890 --> 00:38:46.900 align:start position:0% communication is one we have this new 00:38:46.900 --> 00:38:48.810 align:start position:0% communication is one we have this new proposal<00:38:47.290> where<00:38:47.710> we<00:38:47.829> have<00:38:48.070> cross<00:38:48.310> links<00:38:48.609> in 00:38:48.810 --> 00:38:48.820 align:start position:0% proposal where we have cross links in 00:38:48.820 --> 00:38:51.810 align:start position:0% proposal where we have cross links in every<00:38:49.150> slot<00:38:49.480> on<00:38:49.869> the<00:38:49.960> beacon<00:38:50.349> chain<00:38:50.670> you<00:38:51.670> know 00:38:51.810 --> 00:38:51.820 align:start position:0% every slot on the beacon chain you know 00:38:51.820 --> 00:38:53.910 align:start position:0% every slot on the beacon chain you know we<00:38:52.000> might<00:38:52.359> have<00:38:52.540> crossed<00:38:52.780> cross<00:38:53.440> link<00:38:53.619> regular 00:38:53.910 --> 00:38:53.920 align:start position:0% we might have crossed cross link regular 00:38:53.920 --> 00:38:55.770 align:start position:0% we might have crossed cross link regular collaborate<00:38:54.490> and<00:38:54.670> communication<00:38:55.390> in<00:38:55.540> just 00:38:55.770 --> 00:38:55.780 align:start position:0% collaborate and communication in just 00:38:55.780 --> 00:38:58.800 align:start position:0% collaborate and communication in just just<00:38:56.380> a<00:38:56.470> few<00:38:56.680> slots<00:38:57.000> and<00:38:58.000> then<00:38:58.240> the<00:38:58.359> other<00:38:58.510> way 00:38:58.800 --> 00:38:58.810 align:start position:0% just a few slots and then the other way 00:38:58.810 --> 00:39:02.310 align:start position:0% just a few slots and then the other way kind<00:38:59.680> of<00:38:59.740> which<00:38:59.859> is<00:38:59.980> generic<00:39:00.720> is<00:39:01.720> to<00:39:02.079> use 00:39:02.310 --> 00:39:02.320 align:start position:0% kind of which is generic is to use 00:39:02.320 --> 00:39:05.960 align:start position:0% kind of which is generic is to use optimistic<00:39:03.099> cross<00:39:03.280> links<00:39:03.900> where<00:39:04.900> basically 00:39:05.960 --> 00:39:05.970 align:start position:0% optimistic cross links where basically 00:39:05.970 --> 00:39:08.190 align:start position:0% optimistic cross links where basically you<00:39:06.970> have<00:39:07.150> some<00:39:07.329> sort<00:39:07.510> of<00:39:07.570> off<00:39:07.839> chain 00:39:08.190 --> 00:39:08.200 align:start position:0% you have some sort of off chain 00:39:08.200 --> 00:39:10.220 align:start position:0% you have some sort of off chain mechanism<00:39:08.440> to<00:39:09.099> gauge<00:39:09.339> the<00:39:09.579> probability<00:39:10.180> that 00:39:10.220 --> 00:39:10.230 align:start position:0% mechanism to gauge the probability that 00:39:10.230 --> 00:39:12.900 align:start position:0% mechanism to gauge the probability that some<00:39:11.230> cross<00:39:11.500> link<00:39:11.740> will<00:39:11.920> eventually<00:39:12.490> make<00:39:12.730> it 00:39:12.900 --> 00:39:12.910 align:start position:0% some cross link will eventually make it 00:39:12.910 --> 00:39:14.579 align:start position:0% some cross link will eventually make it into<00:39:13.150> the<00:39:13.240> beacon<00:39:13.540> chain<00:39:13.750> and<00:39:13.960> get<00:39:14.079> finalized 00:39:14.579 --> 00:39:14.589 align:start position:0% into the beacon chain and get finalized 00:39:14.589 --> 00:39:18.210 align:start position:0% into the beacon chain and get finalized but<00:39:15.130> you<00:39:15.220> don't<00:39:15.400> have<00:39:15.520> 100%<00:39:16.240> probability<00:39:17.220> that 00:39:18.210 --> 00:39:18.220 align:start position:0% but you don't have 100% probability that 00:39:18.220 --> 00:39:20.339 align:start position:0% but you don't have 100% probability that will<00:39:18.400> happen<00:39:18.550> and<00:39:18.910> then<00:39:19.030> you<00:39:19.300> you<00:39:19.990> can<00:39:20.140> design 00:39:20.339 --> 00:39:20.349 align:start position:0% will happen and then you you can design 00:39:20.349 --> 00:39:22.559 align:start position:0% will happen and then you you can design your<00:39:20.619> application<00:39:21.069> around<00:39:21.190> that<00:39:21.550> and<00:39:21.790> benefit 00:39:22.559 --> 00:39:22.569 align:start position:0% your application around that and benefit 00:39:22.569 --> 00:39:25.140 align:start position:0% your application around that and benefit from<00:39:22.690> the<00:39:22.960> low<00:39:23.800> latency<00:39:24.250> can<00:39:24.579> you<00:39:24.640> do<00:39:24.819> any<00:39:24.970> some 00:39:25.140 --> 00:39:25.150 align:start position:0% from the low latency can you do any some 00:39:25.150 --> 00:39:27.120 align:start position:0% from the low latency can you do any some kind<00:39:25.359> of<00:39:25.450> automated<00:39:26.020> garbage<00:39:26.349> collection<00:39:27.040> and 00:39:27.120 --> 00:39:27.130 align:start position:0% kind of automated garbage collection and 00:39:27.130 --> 00:39:29.430 align:start position:0% kind of automated garbage collection and start<00:39:27.369> moving<00:39:27.640> smart<00:39:28.599> contracts<00:39:28.990> that<00:39:29.140> want 00:39:29.430 --> 00:39:29.440 align:start position:0% start moving smart contracts that want 00:39:29.440 --> 00:39:31.079 align:start position:0% start moving smart contracts that want to<00:39:29.530> be<00:39:29.619> on<00:39:29.740> the<00:39:29.829> same<00:39:30.010> chain<00:39:30.250> together<00:39:30.550> so<00:39:30.970> that 00:39:31.079 --> 00:39:31.089 align:start position:0% to be on the same chain together so that 00:39:31.089 --> 00:39:41.579 align:start position:0% to be on the same chain together so that they're<00:39:31.240> faster<00:39:36.000> so<00:39:37.000> I<00:39:38.160> think<00:39:39.160> the<00:39:39.310> space<00:39:40.589> the 00:39:41.579 --> 00:39:41.589 align:start position:0% they're faster so I think the space the 00:39:41.589 --> 00:39:43.260 align:start position:0% they're faster so I think the space the cross<00:39:41.770> interaction<00:39:42.310> around<00:39:42.400> multiple<00:39:43.030> shards 00:39:43.260 --> 00:39:43.270 align:start position:0% cross interaction around multiple shards 00:39:43.270 --> 00:39:47.730 align:start position:0% cross interaction around multiple shards I<00:39:43.630> think<00:39:44.849> there<00:39:45.849> should<00:39:45.880> generally<00:39:46.420> be<00:39:46.450> a<00:39:46.960> set 00:39:47.730 --> 00:39:47.740 align:start position:0% I think there should generally be a set 00:39:47.740 --> 00:39:51.390 align:start position:0% I think there should generally be a set of<00:39:47.859> tooling<00:39:48.690> within<00:39:49.690> the<00:39:49.810> hll<00:39:50.380> sort<00:39:50.740> ESL's 00:39:51.390 --> 00:39:51.400 align:start position:0% of tooling within the hll sort ESL's 00:39:51.400 --> 00:39:54.349 align:start position:0% of tooling within the hll sort ESL's that<00:39:51.579> are<00:39:51.670> used<00:39:51.880> within<00:39:52.420> solidity<00:39:52.900> viper 00:39:54.349 --> 00:39:54.359 align:start position:0% that are used within solidity viper 00:39:54.359 --> 00:39:58.620 align:start position:0% that are used within solidity viper anything<00:39:55.359> else<00:39:55.540> so<00:39:56.640> from<00:39:57.640> a<00:39:57.730> developer 00:39:58.620 --> 00:39:58.630 align:start position:0% anything else so from a developer 00:39:58.630 --> 00:40:00.660 align:start position:0% anything else so from a developer perspective<00:39:58.810> if<00:39:59.319> you<00:39:59.440> accept<00:40:00.010> asynchronous 00:40:00.660 --> 00:40:00.670 align:start position:0% perspective if you accept asynchronous 00:40:00.670 --> 00:40:04.740 align:start position:0% perspective if you accept asynchronous as<00:40:00.910> you<00:40:01.569> know<00:40:01.690> a<00:40:02.040> basic<00:40:03.040> concept<00:40:03.510> construct<00:40:04.510> of 00:40:04.740 --> 00:40:04.750 align:start position:0% as you know a basic concept construct of 00:40:04.750 --> 00:40:07.109 align:start position:0% as you know a basic concept construct of communication<00:40:05.349> across<00:40:05.530> shards<00:40:06.010> you<00:40:06.849> can<00:40:06.970> have 00:40:07.109 --> 00:40:07.119 align:start position:0% communication across shards you can have 00:40:07.119 --> 00:40:09.480 align:start position:0% communication across shards you can have tooling<00:40:07.569> that<00:40:07.680> does<00:40:08.680> that<00:40:08.920> through<00:40:09.160> message 00:40:09.480 --> 00:40:09.490 align:start position:0% tooling that does that through message 00:40:09.490 --> 00:40:11.130 align:start position:0% tooling that does that through message passing 00:40:11.130 --> 00:40:11.140 align:start position:0% passing 00:40:11.140 --> 00:40:13.079 align:start position:0% passing you<00:40:11.470> could<00:40:11.680> have<00:40:12.010> tooling<00:40:12.430> that<00:40:12.460> does<00:40:12.849> that 00:40:13.079 --> 00:40:13.089 align:start position:0% you could have tooling that does that 00:40:13.089 --> 00:40:16.170 align:start position:0% you could have tooling that does that through<00:40:13.540> you<00:40:14.410> know<00:40:14.530> two-phase<00:40:15.010> commit<00:40:15.550> you 00:40:16.170 --> 00:40:16.180 align:start position:0% through you know two-phase commit you 00:40:16.180 --> 00:40:18.270 align:start position:0% through you know two-phase commit you know<00:40:16.210> system<00:40:16.839> if<00:40:16.960> you<00:40:17.050> need<00:40:17.230> some<00:40:18.099> type<00:40:18.250> of 00:40:18.270 --> 00:40:18.280 align:start position:0% know system if you need some type of 00:40:18.280 --> 00:40:21.660 align:start position:0% know system if you need some type of atomic<00:40:18.760> transaction<00:40:19.740> you<00:40:20.740> could<00:40:20.890> have<00:40:21.069> you 00:40:21.660 --> 00:40:21.670 align:start position:0% atomic transaction you could have you 00:40:21.670 --> 00:40:23.970 align:start position:0% atomic transaction you could have you know<00:40:21.700> tooling<00:40:22.180> that<00:40:22.240> so<00:40:22.869> I<00:40:22.900> think<00:40:23.500> from<00:40:23.680> a<00:40:23.800> dot 00:40:23.970 --> 00:40:23.980 align:start position:0% know tooling that so I think from a dot 00:40:23.980 --> 00:40:26.790 align:start position:0% know tooling that so I think from a dot developers<00:40:24.940> perspective<00:40:25.380> you're<00:40:26.380> going<00:40:26.619> to 00:40:26.790 --> 00:40:26.800 align:start position:0% developers perspective you're going to 00:40:26.800 --> 00:40:28.589 align:start position:0% developers perspective you're going to have<00:40:27.250> more<00:40:27.490> tooling<00:40:27.880> in<00:40:28.000> these<00:40:28.119> languages 00:40:28.589 --> 00:40:28.599 align:start position:0% have more tooling in these languages 00:40:28.599 --> 00:40:29.410 align:start position:0% have more tooling in these languages that<00:40:28.780> you<00:40:29.170> would 00:40:29.410 --> 00:40:29.420 align:start position:0% that you would 00:40:29.420 --> 00:40:32.020 align:start position:0% that you would go<00:40:29.750> ahead<00:40:29.900> and<00:40:30.080> and<00:40:30.370> utilize<00:40:31.370> for<00:40:31.670> the<00:40:31.700> problem 00:40:32.020 --> 00:40:32.030 align:start position:0% go ahead and and utilize for the problem 00:40:32.030 --> 00:40:43.480 align:start position:0% go ahead and and utilize for the problem that<00:40:32.120> you<00:40:32.240> need<00:40:32.500> so<00:40:40.270> yeah<00:40:41.500> the<00:40:42.500> archive<00:40:43.250> notes 00:40:43.480 --> 00:40:43.490 align:start position:0% that you need so yeah the archive notes 00:40:43.490 --> 00:40:46.060 align:start position:0% that you need so yeah the archive notes look<00:40:43.730> like<00:40:43.970> forth<00:40:44.330> to<00:40:44.630> and<00:40:44.900> our<00:40:45.680> blog 00:40:46.060 --> 00:40:46.070 align:start position:0% look like forth to and our blog 00:40:46.070 --> 00:40:56.200 align:start position:0% look like forth to and our blog explorers<00:40:46.580> ready<00:40:46.970> for<00:40:47.210> this<00:40:54.850> if<00:40:55.850> you're<00:40:56.180> a 00:40:56.200 --> 00:40:56.210 align:start position:0% explorers ready for this if you're a 00:40:56.210 --> 00:40:58.540 align:start position:0% explorers ready for this if you're a blog<00:40:56.750> explorer<00:40:57.350> you<00:40:57.590> would<00:40:57.740> pretty<00:40:57.950> much<00:40:58.070> have 00:40:58.540 --> 00:40:58.550 align:start position:0% blog explorer you would pretty much have 00:40:58.550 --> 00:41:01.090 align:start position:0% blog explorer you would pretty much have to<00:40:58.580> download<00:40:59.300> every<00:40:59.900> blog<00:41:00.170> on<00:41:00.470> every<00:41:00.800> shard 00:41:01.090 --> 00:41:01.100 align:start position:0% to download every blog on every shard 00:41:01.100 --> 00:41:04.240 align:start position:0% to download every blog on every shard which<00:41:01.550> is<00:41:01.820> one<00:41:02.600> to<00:41:02.780> ten<00:41:02.990> megabytes<00:41:03.440> per<00:41:03.620> second 00:41:04.240 --> 00:41:04.250 align:start position:0% which is one to ten megabytes per second 00:41:04.250 --> 00:41:08.650 align:start position:0% which is one to ten megabytes per second x<00:41:05.620> 86,400<00:41:06.620> and<00:41:06.710> we're<00:41:06.860> talking<00:41:07.070> 80<00:41:07.880> to<00:41:08.150> 100 00:41:08.650 --> 00:41:08.660 align:start position:0% x 86,400 and we're talking 80 to 100 00:41:08.660 --> 00:41:12.820 align:start position:0% x 86,400 and we're talking 80 to 100 gigabytes<00:41:09.410> a<00:41:09.620> day<00:41:09.830> so<00:41:10.060> it's<00:41:11.060> like<00:41:11.840> you<00:41:12.620> have 00:41:12.820 --> 00:41:12.830 align:start position:0% gigabytes a day so it's like you have 00:41:12.830 --> 00:41:20.100 align:start position:0% gigabytes a day so it's like you have you<00:41:13.340> have<00:41:13.790> like<00:41:14.060> more<00:41:14.300> hardware<00:41:14.660> requirements 00:41:20.100 --> 00:41:20.110 align:start position:0% 00:41:20.110 --> 00:41:23.110 align:start position:0% and<00:41:21.110> then<00:41:21.500> of<00:41:21.650> course<00:41:21.680> so<00:41:22.340> that<00:41:22.520> like<00:41:22.940> that's 00:41:23.110 --> 00:41:23.120 align:start position:0% and then of course so that like that's 00:41:23.120 --> 00:41:24.970 align:start position:0% and then of course so that like that's one<00:41:23.390> issue<00:41:23.540> -<00:41:23.810> hi<00:41:23.930> Ricardo<00:41:24.260> requirements 00:41:24.970 --> 00:41:24.980 align:start position:0% one issue - hi Ricardo requirements 00:41:24.980 --> 00:41:31.450 align:start position:0% one issue - hi Ricardo requirements going<00:41:25.250> up<00:41:25.400> in<00:41:26.030> another<00:41:26.780> issue<00:41:27.320> is<00:41:28.480> that<00:41:30.460> you'll 00:41:31.450 --> 00:41:31.460 align:start position:0% going up in another issue is that you'll 00:41:31.460 --> 00:41:34.180 align:start position:0% going up in another issue is that you'll have<00:41:31.700> to<00:41:31.760> deal<00:41:32.180> like<00:41:32.540> I<00:41:32.570> kind<00:41:33.080> of<00:41:33.200> understood 00:41:34.180 --> 00:41:34.190 align:start position:0% have to deal like I kind of understood 00:41:34.190 --> 00:41:36.790 align:start position:0% have to deal like I kind of understood with<00:41:34.760> you<00:41:34.940> to<00:41:35.270> basically<00:41:35.810> more<00:41:36.230> things<00:41:36.590> or 00:41:36.790 --> 00:41:36.800 align:start position:0% with you to basically more things or 00:41:36.800 --> 00:41:38.320 align:start position:0% with you to basically more things or being<00:41:36.980> kind<00:41:37.250> of<00:41:37.370> lawyer<00:41:37.610> to<00:41:37.820> a<00:41:37.850> fight<00:41:38.120> than 00:41:38.320 --> 00:41:38.330 align:start position:0% being kind of lawyer to a fight than 00:41:38.330 --> 00:41:40.270 align:start position:0% being kind of lawyer to a fight than before<00:41:38.690> so<00:41:39.320> if<00:41:39.440> you<00:41:39.530> have<00:41:39.680> execution 00:41:40.270 --> 00:41:40.280 align:start position:0% before so if you have execution 00:41:40.280 --> 00:41:42.820 align:start position:0% before so if you have execution environments<00:41:40.940> and<00:41:41.090> then<00:41:41.240> within<00:41:41.990> execution 00:41:42.820 --> 00:41:42.830 align:start position:0% environments and then within execution 00:41:42.830 --> 00:41:44.860 align:start position:0% environments and then within execution environments<00:41:43.490> we're<00:41:43.850> also<00:41:43.970> planning<00:41:44.330> to<00:41:44.540> push 00:41:44.860 --> 00:41:44.870 align:start position:0% environments we're also planning to push 00:41:44.870 --> 00:41:46.900 align:start position:0% environments we're also planning to push forward<00:41:45.260> on<00:41:45.410> transaction<00:41:46.010> abstraction<00:41:46.730> and 00:41:46.900 --> 00:41:46.910 align:start position:0% forward on transaction abstraction and 00:41:46.910 --> 00:41:48.910 align:start position:0% forward on transaction abstraction and so<00:41:47.090> now<00:41:47.270> you<00:41:47.330> don't<00:41:47.630> like<00:41:47.750> you<00:41:47.900> don't<00:41:48.050> have<00:41:48.260> yo 00:41:48.910 --> 00:41:48.920 align:start position:0% so now you don't like you don't have yo 00:41:48.920 --> 00:41:51.010 align:start position:0% so now you don't like you don't have yo ways<00:41:49.220> and<00:41:49.490> contracts<00:41:50.060> as<00:41:50.180> different<00:41:50.510> costs<00:41:50.900> of 00:41:51.010 --> 00:41:51.020 align:start position:0% ways and contracts as different costs of 00:41:51.020 --> 00:41:53.110 align:start position:0% ways and contracts as different costs of things<00:41:51.170> anymore<00:41:51.500> and<00:41:51.740> then<00:41:52.010> you<00:41:52.100> have<00:41:52.310> crossed 00:41:53.110 --> 00:41:53.120 align:start position:0% things anymore and then you have crossed 00:41:53.120 --> 00:41:54.760 align:start position:0% things anymore and then you have crossed our<00:41:53.330> transactions<00:41:54.020> the<00:41:54.170> different<00:41:54.470> ways<00:41:54.590> of 00:41:54.760 --> 00:41:54.770 align:start position:0% our transactions the different ways of 00:41:54.770 --> 00:41:57.150 align:start position:0% our transactions the different ways of implementing<00:41:55.220> them<00:41:55.580> and<00:41:55.820> so<00:41:56.110> your 00:41:57.150 --> 00:41:57.160 align:start position:0% implementing them and so your 00:41:57.160 --> 00:41:59.470 align:start position:0% implementing them and so your responsibility<00:41:58.160> to<00:41:58.190> and<00:41:58.820> have<00:41:58.910> understands 00:41:59.470 --> 00:41:59.480 align:start position:0% responsibility to and have understands 00:41:59.480 --> 00:42:01.450 align:start position:0% responsibility to and have understands popular<00:42:00.170> layer<00:42:00.380> 2<00:42:00.620> protocols<00:42:01.160> will 00:42:01.450 --> 00:42:01.460 align:start position:0% popular layer 2 protocols will 00:42:01.460 --> 00:42:03.460 align:start position:0% popular layer 2 protocols will realistically<00:42:02.150> end<00:42:02.570> up<00:42:02.660> increasing<00:42:03.080> and 00:42:03.460 --> 00:42:03.470 align:start position:0% realistically end up increasing and 00:42:03.470 --> 00:42:04.840 align:start position:0% realistically end up increasing and that's<00:42:03.530> another<00:42:03.830> thing<00:42:04.160> that<00:42:04.220> you<00:42:04.550> might<00:42:04.700> need 00:42:04.840 --> 00:42:04.850 align:start position:0% that's another thing that you might need 00:42:04.850 --> 00:42:07.330 align:start position:0% that's another thing that you might need to<00:42:05.000> what<00:42:05.230> that<00:42:06.230> you'll<00:42:06.440> probably<00:42:06.680> needs<00:42:07.160> to 00:42:07.330 --> 00:42:07.340 align:start position:0% to what that you'll probably needs to 00:42:07.340 --> 00:42:10.300 align:start position:0% to what that you'll probably needs to watch<00:42:07.520> out<00:42:07.700> for<00:42:07.760> so<00:42:08.750> I<00:42:08.780> guess<00:42:09.110> you<00:42:09.890> know<00:42:09.920> in 00:42:10.300 --> 00:42:10.310 align:start position:0% watch out for so I guess you know in 00:42:10.310 --> 00:42:12.580 align:start position:0% watch out for so I guess you know in general<00:42:10.820> for<00:42:11.090> being<00:42:11.960> a<00:42:12.080> general-purpose 00:42:12.580 --> 00:42:12.590 align:start position:0% general for being a general-purpose 00:42:12.590 --> 00:42:14.920 align:start position:0% general for being a general-purpose black<00:42:13.310> explorers<00:42:13.970> like<00:42:14.210> realistically<00:42:14.750> is 00:42:14.920 --> 00:42:14.930 align:start position:0% black explorers like realistically is 00:42:14.930 --> 00:42:21.150 align:start position:0% black explorers like realistically is one<00:42:15.110> of<00:42:15.200> the<00:42:15.320> things<00:42:15.500> that<00:42:15.710> will<00:42:15.860> get<00:42:16.130> harder 00:42:21.150 --> 00:42:21.160 align:start position:0% 00:42:21.160 --> 00:42:23.609 align:start position:0% all<00:42:21.700> right<00:42:21.880> we<00:42:22.059> have<00:42:22.109> time<00:42:23.109> for<00:42:23.140> one<00:42:23.589> last 00:42:23.609 --> 00:42:23.619 align:start position:0% all right we have time for one last 00:42:23.619 --> 00:42:24.509 align:start position:0% all right we have time for one last question 00:42:24.509 --> 00:42:24.519 align:start position:0% question 00:42:24.519 --> 00:42:27.240 align:start position:0% question make<00:42:24.910> it<00:42:25.089> quick<00:42:25.359> so<00:42:25.720> as<00:42:25.990> a<00:42:26.019> DAP<00:42:26.470> developer<00:42:27.009> that 00:42:27.240 --> 00:42:27.250 align:start position:0% make it quick so as a DAP developer that 00:42:27.250 --> 00:42:29.609 align:start position:0% make it quick so as a DAP developer that has<00:42:27.400> an<00:42:27.549> IRC<00:42:27.759> 20<00:42:28.089> asset<00:42:28.839> is<00:42:29.259> there<00:42:29.410> anything 00:42:29.609 --> 00:42:29.619 align:start position:0% has an IRC 20 asset is there anything 00:42:29.619 --> 00:42:31.799 align:start position:0% has an IRC 20 asset is there anything specifically<00:42:30.369> we<00:42:30.579> should<00:42:30.759> do<00:42:30.940> or<00:42:31.269> maybe<00:42:31.569> not 00:42:31.799 --> 00:42:31.809 align:start position:0% specifically we should do or maybe not 00:42:31.809 --> 00:42:38.160 align:start position:0% specifically we should do or maybe not do<00:42:33.750> right<00:42:34.750> now<00:42:35.200> no<00:42:35.710> I<00:42:36.150> mean<00:42:37.150> in<00:42:37.420> the<00:42:37.539> in<00:42:38.079> the 00:42:38.160 --> 00:42:38.170 align:start position:0% do right now no I mean in the in the 00:42:38.170 --> 00:42:42.569 align:start position:0% do right now no I mean in the in the future<00:42:38.319> when<00:42:38.829> I<00:42:38.859> think<00:42:40.289> I'm<00:42:41.289> inclined<00:42:42.160> to<00:42:42.279> just 00:42:42.569 --> 00:42:42.579 align:start position:0% future when I think I'm inclined to just 00:42:42.579 --> 00:42:44.430 align:start position:0% future when I think I'm inclined to just say<00:42:42.789> like<00:42:42.970> don't<00:42:43.240> don't<00:42:43.809> think<00:42:44.109> about<00:42:44.319> the 00:42:44.430 --> 00:42:44.440 align:start position:0% say like don't don't think about the 00:42:44.440 --> 00:42:46.200 align:start position:0% say like don't don't think about the problem<00:42:44.829> now<00:42:44.980> and<00:42:45.220> like<00:42:45.460> in<00:42:45.579> the<00:42:45.700> future<00:42:46.029> as 00:42:46.200 --> 00:42:46.210 align:start position:0% problem now and like in the future as 00:42:46.210 --> 00:42:48.960 align:start position:0% problem now and like in the future as the<00:42:46.390> X<00:42:46.569> execution<00:42:47.200> environments<00:42:47.829> and<00:42:48.460> if 00:42:48.960 --> 00:42:48.970 align:start position:0% the X execution environments and if 00:42:48.970 --> 00:42:51.420 align:start position:0% the X execution environments and if start<00:42:49.269> becoming<00:42:49.599> more<00:42:49.809> nailed<00:42:50.710> down<00:42:51.009> then 00:42:51.420 --> 00:42:51.430 align:start position:0% start becoming more nailed down then 00:42:51.430 --> 00:42:54.420 align:start position:0% start becoming more nailed down then you'll<00:42:51.759> be<00:42:51.910> able<00:42:52.089> to<00:42:52.319> have<00:42:53.319> think<00:42:53.890> more<00:42:54.160> about 00:42:54.420 --> 00:42:54.430 align:start position:0% you'll be able to have think more about 00:42:54.430 --> 00:42:56.700 align:start position:0% you'll be able to have think more about like<00:42:54.640> how<00:42:54.819> to<00:42:54.880> design<00:42:55.599> design<00:42:56.200> the<00:42:56.410> kind<00:42:56.680> of 00:42:56.700 --> 00:42:56.710 align:start position:0% like how to design design the kind of 00:42:56.710 --> 00:42:58.410 align:start position:0% like how to design design the kind of token<00:42:56.980> and<00:42:57.250> like<00:42:57.369> application<00:42:58.000> specific 00:42:58.410 --> 00:42:58.420 align:start position:0% token and like application specific 00:42:58.420 --> 00:43:01.079 align:start position:0% token and like application specific details<00:42:58.779> around<00:42:59.079> across<00:42:59.259> shard<00:42:59.589> context<00:43:00.190> but 00:43:01.079 --> 00:43:01.089 align:start position:0% details around across shard context but 00:43:01.089 --> 00:43:06.390 align:start position:0% details around across shard context but no<00:43:01.269> migrations<00:43:04.500> like<00:43:05.500> there<00:43:06.279> is<00:43:06.369> a 00:43:06.390 --> 00:43:06.400 align:start position:0% no migrations like there is a 00:43:06.400 --> 00:43:10.079 align:start position:0% no migrations like there is a possibility<00:43:06.940> you'll<00:43:07.390> have<00:43:07.630> to<00:43:07.839> do<00:43:08.380> a<00:43:09.089> one-time 00:43:10.079 --> 00:43:10.089 align:start position:0% possibility you'll have to do a one-time 00:43:10.089 --> 00:43:11.880 align:start position:0% possibility you'll have to do a one-time token<00:43:10.690> upgrade<00:43:11.109> but<00:43:11.289> that<00:43:11.410> could<00:43:11.589> also<00:43:11.740> be 00:43:11.880 --> 00:43:11.890 align:start position:0% token upgrade but that could also be 00:43:11.890 --> 00:43:13.819 align:start position:0% token upgrade but that could also be done<00:43:12.130> with<00:43:12.190> a<00:43:12.339> wrapper 00:43:13.819 --> 00:43:13.829 align:start position:0% done with a wrapper 00:43:13.829 --> 00:43:17.069 align:start position:0% done with a wrapper knowing<00:43:14.829> that<00:43:14.859> tokens<00:43:15.460> are<00:43:15.759> the<00:43:16.059> most<00:43:16.269> used 00:43:17.069 --> 00:43:17.079 align:start position:0% knowing that tokens are the most used 00:43:17.079 --> 00:43:20.099 align:start position:0% knowing that tokens are the most used function<00:43:17.890> in<00:43:18.130> the<00:43:18.279> current<00:43:19.000> chain<00:43:19.210> is<00:43:19.599> it<00:43:19.869> not 00:43:20.099 --> 00:43:20.109 align:start position:0% function in the current chain is it not 00:43:20.109 --> 00:43:22.049 align:start position:0% function in the current chain is it not worth<00:43:20.319> considering<00:43:21.009> hard<00:43:21.190> coding<00:43:21.609> them<00:43:21.819> and 00:43:22.049 --> 00:43:22.059 align:start position:0% worth considering hard coding them and 00:43:22.059 --> 00:43:25.349 align:start position:0% worth considering hard coding them and by<00:43:22.799> making<00:43:23.799> them<00:43:24.099> much<00:43:24.640> more<00:43:24.849> efficient<00:43:25.269> than 00:43:25.349 --> 00:43:25.359 align:start position:0% by making them much more efficient than 00:43:25.359 --> 00:43:26.880 align:start position:0% by making them much more efficient than they<00:43:25.599> are<00:43:25.630> right<00:43:25.869> now<00:43:25.930> or<00:43:26.170> taking<00:43:26.559> a<00:43:26.619> snapshot 00:43:26.880 --> 00:43:26.890 align:start position:0% they are right now or taking a snapshot 00:43:26.890 --> 00:43:28.920 align:start position:0% they are right now or taking a snapshot potentially<00:43:27.609> what<00:43:28.089> hard<00:43:28.299> coding<00:43:28.630> make<00:43:28.779> them 00:43:28.920 --> 00:43:28.930 align:start position:0% potentially what hard coding make them 00:43:28.930 --> 00:43:30.569 align:start position:0% potentially what hard coding make them more<00:43:29.049> efficient<00:43:29.619> well<00:43:30.039> because<00:43:30.279> right<00:43:30.460> now 00:43:30.569 --> 00:43:30.579 align:start position:0% more efficient well because right now 00:43:30.579 --> 00:43:32.579 align:start position:0% more efficient well because right now they<00:43:30.730> execute<00:43:31.299> code<00:43:31.539> just<00:43:31.900> to<00:43:31.990> do<00:43:32.109> basic 00:43:32.579 --> 00:43:32.589 align:start position:0% they execute code just to do basic 00:43:32.589 --> 00:43:34.650 align:start position:0% they execute code just to do basic functionality<00:43:33.279> of<00:43:33.400> the<00:43:33.490> token<00:43:33.849> the<00:43:34.029> cord<00:43:34.420> is 00:43:34.650 --> 00:43:34.660 align:start position:0% functionality of the token the cord is 00:43:34.660 --> 00:43:37.279 align:start position:0% functionality of the token the cord is like<00:43:34.900> fairly<00:43:35.710> is<00:43:35.859> small<00:43:36.400> right<00:43:36.789> like 00:43:37.279 --> 00:43:37.289 align:start position:0% like fairly is small right like 00:43:37.289 --> 00:43:40.200 align:start position:0% like fairly is small right like execution<00:43:38.289> of<00:43:38.410> EVM<00:43:38.769> code<00:43:39.009> is<00:43:39.160> not<00:43:39.430> like<00:43:39.730> a 00:43:40.200 --> 00:43:40.210 align:start position:0% execution of EVM code is not like a 00:43:40.210 --> 00:43:45.359 align:start position:0% execution of EVM code is not like a dominant<00:43:41.079> factor<00:43:41.259> of<00:43:41.799> like<00:43:42.670> watching<00:43:44.369> over 00:43:45.359 --> 00:43:45.369 align:start position:0% dominant factor of like watching over 00:43:45.369 --> 00:43:48.690 align:start position:0% dominant factor of like watching over and<00:43:45.519> overhead<00:43:46.000> time<00:43:46.299> like<00:43:47.170> the<00:43:47.920> one<00:43:48.130> okay<00:43:48.670> so 00:43:48.690 --> 00:43:48.700 align:start position:0% and overhead time like the one okay so 00:43:48.700 --> 00:43:50.880 align:start position:0% and overhead time like the one okay so the<00:43:49.000> thing<00:43:49.180> that<00:43:49.210> I<00:43:49.480> would<00:43:49.690> look<00:43:49.839> into<00:43:50.049> like<00:43:50.349> if 00:43:50.880 --> 00:43:50.890 align:start position:0% the thing that I would look into like if 00:43:50.890 --> 00:43:52.890 align:start position:0% the thing that I would look into like if we<00:43:51.190> wants<00:43:51.519> to<00:43:51.640> like<00:43:51.759> really<00:43:51.970> optimize<00:43:52.480> tokens 00:43:52.890 --> 00:43:52.900 align:start position:0% we wants to like really optimize tokens 00:43:52.900 --> 00:43:54.299 align:start position:0% we wants to like really optimize tokens have<00:43:53.079> only<00:43:53.230> things<00:43:53.589> that<00:43:53.740> I<00:43:53.829> would<00:43:53.980> look<00:43:54.099> into 00:43:54.299 --> 00:43:54.309 align:start position:0% have only things that I would look into 00:43:54.309 --> 00:43:56.880 align:start position:0% have only things that I would look into I<00:43:54.819> mean<00:43:55.210> one<00:43:55.480> is<00:43:55.509> to<00:43:55.750> just<00:43:55.779> like<00:43:56.140> review<00:43:56.559> like 00:43:56.880 --> 00:43:56.890 align:start position:0% I mean one is to just like review like 00:43:56.890 --> 00:43:58.559 align:start position:0% I mean one is to just like review like the<00:43:57.099> whole<00:43:57.250> year<00:43:57.460> see<00:43:57.700> 20<00:43:58.000> transfer<00:43:58.450> from 00:43:58.559 --> 00:43:58.569 align:start position:0% the whole year see 20 transfer from 00:43:58.569 --> 00:44:00.299 align:start position:0% the whole year see 20 transfer from architecture<00:43:59.380> and<00:43:59.529> like<00:43:59.680> think<00:43:59.950> hard<00:44:00.160> about 00:44:00.299 --> 00:44:00.309 align:start position:0% architecture and like think hard about 00:44:00.309 --> 00:44:03.059 align:start position:0% architecture and like think hard about do<00:44:01.299> we<00:44:01.329> wants<00:44:01.750> to<00:44:01.900> build<00:44:02.079> into<00:44:02.410> a<00:44:02.440> much<00:44:02.799> higher 00:44:03.059 --> 00:44:03.069 align:start position:0% do we wants to build into a much higher 00:44:03.069 --> 00:44:05.130 align:start position:0% do we wants to build into a much higher level<00:44:03.309> of<00:44:03.910> language<00:44:04.359> standards<00:44:04.869> a<00:44:04.960> more 00:44:05.130 --> 00:44:05.140 align:start position:0% level of language standards a more 00:44:05.140 --> 00:44:06.990 align:start position:0% level of language standards a more explicit<00:44:05.559> like<00:44:06.009> pay<00:44:06.250> for<00:44:06.490> token<00:44:06.849> with 00:44:06.990 --> 00:44:07.000 align:start position:0% explicit like pay for token with 00:44:07.000 --> 00:44:09.630 align:start position:0% explicit like pay for token with function<00:44:07.359> calling<00:44:07.599> em<00:44:07.930> strategy<00:44:08.640> another 00:44:09.630 --> 00:44:09.640 align:start position:0% function calling em strategy another 00:44:09.640 --> 00:44:13.499 align:start position:0% function calling em strategy another thing<00:44:10.000> to<00:44:10.180> look<00:44:10.329> into<00:44:10.750> is<00:44:10.990> that<00:44:12.000> actually<00:44:13.000> one 00:44:13.499 --> 00:44:13.509 align:start position:0% thing to look into is that actually one 00:44:13.509 --> 00:44:15.960 align:start position:0% thing to look into is that actually one kind<00:44:14.079> of<00:44:14.220> functionality<00:44:15.220> that<00:44:15.400> I<00:44:15.460> think<00:44:15.819> well 00:44:15.960 --> 00:44:15.970 align:start position:0% kind of functionality that I think well 00:44:15.970 --> 00:44:17.819 align:start position:0% kind of functionality that I think well light<00:44:16.210> will<00:44:16.390> likely<00:44:16.630> put<00:44:16.930> in<00:44:17.049> is<00:44:17.289> the<00:44:17.319> ability 00:44:17.819 --> 00:44:17.829 align:start position:0% light will likely put in is the ability 00:44:17.829 --> 00:44:20.039 align:start position:0% light will likely put in is the ability to<00:44:18.009> store<00:44:18.490> pieces<00:44:18.970> of<00:44:19.059> contract<00:44:19.539> code<00:44:19.750> on<00:44:19.960> the 00:44:20.039 --> 00:44:20.049 align:start position:0% to store pieces of contract code on the 00:44:20.049 --> 00:44:22.529 align:start position:0% to store pieces of contract code on the beacon<00:44:20.319> chain<00:44:20.559> and<00:44:21.430> then<00:44:21.730> have<00:44:22.000> the<00:44:22.180> ability 00:44:22.529 --> 00:44:22.539 align:start position:0% beacon chain and then have the ability 00:44:22.539 --> 00:44:24.569 align:start position:0% beacon chain and then have the ability to<00:44:22.569> just<00:44:22.869> reference<00:44:23.079> them<00:44:23.559> by<00:44:23.740> address<00:44:24.190> and 00:44:24.569 --> 00:44:24.579 align:start position:0% to just reference them by address and 00:44:24.579 --> 00:44:27.599 align:start position:0% to just reference them by address and this<00:44:25.299> would<00:44:25.799> like<00:44:26.799> this<00:44:27.009> would<00:44:27.220> prevent 00:44:27.599 --> 00:44:27.609 align:start position:0% this would like this would prevent 00:44:27.609 --> 00:44:30.180 align:start position:0% this would like this would prevent things<00:44:27.970> like<00:44:28.390> account<00:44:28.839> abstraction<00:44:29.769> like 00:44:30.180 --> 00:44:30.190 align:start position:0% things like account abstraction like 00:44:30.190 --> 00:44:33.390 align:start position:0% things like account abstraction like tokens<00:44:30.730> not<00:44:31.150> being<00:44:31.420> abstracted<00:44:32.140> and<00:44:32.380> or<00:44:32.769> token 00:44:33.390 --> 00:44:33.400 align:start position:0% tokens not being abstracted and or token 00:44:33.400 --> 00:44:34.589 align:start position:0% tokens not being abstracted and or token it's<00:44:33.490> already<00:44:33.730> being<00:44:33.940> abstracted 00:44:34.589 --> 00:44:34.599 align:start position:0% it's already being abstracted 00:44:34.599 --> 00:44:35.999 align:start position:0% it's already being abstracted all<00:44:34.630> these<00:44:34.779> other<00:44:34.989> things<00:44:35.049> from<00:44:35.589> blowing<00:44:35.769> up 00:44:35.999 --> 00:44:36.009 align:start position:0% all these other things from blowing up 00:44:36.009 --> 00:44:37.710 align:start position:0% all these other things from blowing up witness<00:44:36.369> sizes<00:44:36.759> because<00:44:37.089> you<00:44:37.239> know<00:44:37.299> instead 00:44:37.710 --> 00:44:37.720 align:start position:0% witness sizes because you know instead 00:44:37.720 --> 00:44:39.779 align:start position:0% witness sizes because you know instead of<00:44:37.779> having<00:44:38.109> a<00:44:39.069> piece<00:44:39.249> of<00:44:39.400> code<00:44:39.609> in<00:44:39.759> your 00:44:39.779 --> 00:44:39.789 align:start position:0% of having a piece of code in your 00:44:39.789 --> 00:44:41.339 align:start position:0% of having a piece of code in your witness<00:44:40.180> you'll<00:44:40.359> just<00:44:40.569> be<00:44:40.690> able<00:44:40.809> to<00:44:41.049> point<00:44:41.200> to 00:44:41.339 --> 00:44:41.349 align:start position:0% witness you'll just be able to point to 00:44:41.349 --> 00:44:43.620 align:start position:0% witness you'll just be able to point to an<00:44:41.499> index<00:44:41.799> so<00:44:42.519> a<00:44:42.549> lot<00:44:42.849> of<00:44:42.880> those<00:44:43.180> games<00:44:43.420> have 00:44:43.620 --> 00:44:43.630 align:start position:0% an index so a lot of those games have 00:44:43.630 --> 00:44:45.930 align:start position:0% an index so a lot of those games have kind<00:44:43.960> of<00:44:44.079> been<00:44:44.259> factored<00:44:45.069> into<00:44:45.220> the<00:44:45.430> existing 00:44:45.930 --> 00:44:45.940 align:start position:0% kind of been factored into the existing 00:44:45.940 --> 00:44:50.759 align:start position:0% kind of been factored into the existing design<00:44:46.150> already<00:44:47.190> another<00:44:49.229> thing<00:44:50.229> to<00:44:50.589> look 00:44:50.759 --> 00:44:50.769 align:start position:0% design already another thing to look 00:44:50.769 --> 00:44:53.940 align:start position:0% design already another thing to look into<00:44:51.190> either<00:44:51.400> would<00:44:51.999> it<00:44:52.150> be<00:44:52.390> I<00:44:53.079> know 00:44:53.940 --> 00:44:53.950 align:start position:0% into either would it be I know 00:44:53.950 --> 00:44:56.789 align:start position:0% into either would it be I know redesigning<00:44:54.789> user<00:44:55.329> accounts<00:44:56.049> so<00:44:56.319> that<00:44:56.349> you 00:44:56.789 --> 00:44:56.799 align:start position:0% redesigning user accounts so that you 00:44:56.799 --> 00:44:59.759 align:start position:0% redesigning user accounts so that you would<00:44:56.979> have<00:44:57.190> the<00:44:57.910> benefit<00:44:58.420> of<00:44:58.450> kind<00:44:59.410> of<00:44:59.470> being 00:44:59.759 --> 00:44:59.769 align:start position:0% would have the benefit of kind of being 00:44:59.769 --> 00:45:02.549 align:start position:0% would have the benefit of kind of being able<00:44:59.890> to<00:45:00.420> like<00:45:01.420> you<00:45:01.989> would<00:45:02.109> be<00:45:02.200> able<00:45:02.259> to<00:45:02.380> get 00:45:02.549 --> 00:45:02.559 align:start position:0% able to like you would be able to get 00:45:02.559 --> 00:45:04.229 align:start position:0% able to like you would be able to get the<00:45:02.680> efficiency<00:45:03.039> benefits<00:45:03.609> of<00:45:03.759> being<00:45:03.940> able<00:45:04.089> to 00:45:04.229 --> 00:45:04.239 align:start position:0% the efficiency benefits of being able to 00:45:04.239 --> 00:45:07.559 align:start position:0% the efficiency benefits of being able to hold<00:45:04.539> many<00:45:05.319> units<00:45:05.769> of<00:45:05.920> a<00:45:06.009> token<00:45:06.400> within<00:45:06.849> one 00:45:07.559 --> 00:45:07.569 align:start position:0% hold many units of a token within one 00:45:07.569 --> 00:45:09.420 align:start position:0% hold many units of a token within one particular<00:45:07.779> package<00:45:08.589> that<00:45:08.859> could<00:45:08.979> get<00:45:09.190> passed 00:45:09.420 --> 00:45:09.430 align:start position:0% particular package that could get passed 00:45:09.430 --> 00:45:11.910 align:start position:0% particular package that could get passed around<00:45:09.609> between<00:45:09.910> shards<00:45:10.509> but<00:45:10.749> like<00:45:11.499> there's 00:45:11.910 --> 00:45:11.920 align:start position:0% around between shards but like there's 00:45:11.920 --> 00:45:13.589 align:start position:0% around between shards but like there's trade-offs<00:45:12.309> there<00:45:12.489> right<00:45:12.789> because<00:45:13.089> from<00:45:13.479> a 00:45:13.589 --> 00:45:13.599 align:start position:0% trade-offs there right because from a 00:45:13.599 --> 00:45:15.029 align:start position:0% trade-offs there right because from a privacy<00:45:14.079> point<00:45:14.259> of<00:45:14.440> view<00:45:14.559> if<00:45:14.680> you<00:45:14.799> want<00:45:14.979> to 00:45:15.029 --> 00:45:15.039 align:start position:0% privacy point of view if you want to 00:45:15.039 --> 00:45:16.559 align:start position:0% privacy point of view if you want to improve<00:45:15.249> your<00:45:15.369> privacy<00:45:15.849> it<00:45:15.940> actually<00:45:16.359> makes 00:45:16.559 --> 00:45:16.569 align:start position:0% improve your privacy it actually makes 00:45:16.569 --> 00:45:19.349 align:start position:0% improve your privacy it actually makes sense<00:45:16.839> to<00:45:17.109> kind<00:45:17.440> of<00:45:17.799> separate<00:45:18.729> out<00:45:18.880> all<00:45:19.089> of<00:45:19.119> you 00:45:19.349 --> 00:45:19.359 align:start position:0% sense to kind of separate out all of you 00:45:19.359 --> 00:45:22.049 align:start position:0% sense to kind of separate out all of you all<00:45:19.509> of<00:45:19.539> your<00:45:19.809> token<00:45:20.200> holdings<00:45:20.559> from<00:45:21.339> from 00:45:22.049 --> 00:45:22.059 align:start position:0% all of your token holdings from from 00:45:22.059 --> 00:45:23.190 align:start position:0% all of your token holdings from from each<00:45:22.180> other<00:45:22.420> and<00:45:22.599> even<00:45:22.839> have<00:45:22.989> multiple 00:45:23.190 --> 00:45:23.200 align:start position:0% each other and even have multiple 00:45:23.200 --> 00:45:27.299 align:start position:0% each other and even have multiple accounts<00:45:23.859> per<00:45:24.009> tokens<00:45:24.460> so<00:45:24.789> it's<00:45:25.440> like<00:45:26.440> in 00:45:27.299 --> 00:45:27.309 align:start position:0% accounts per tokens so it's like in 00:45:27.309 --> 00:45:29.969 align:start position:0% accounts per tokens so it's like in general<00:45:27.729> I<00:45:28.180> feel<00:45:28.420> like<00:45:28.660> there's<00:45:29.319> a<00:45:29.410> way<00:45:29.680> like 00:45:29.969 --> 00:45:29.979 align:start position:0% general I feel like there's a way like 00:45:29.979 --> 00:45:32.009 align:start position:0% general I feel like there's a way like the<00:45:30.430> optimizations<00:45:31.180> are<00:45:31.390> needed<00:45:31.690> but<00:45:31.869> there's 00:45:32.009 --> 00:45:32.019 align:start position:0% the optimizations are needed but there's 00:45:32.019 --> 00:45:34.079 align:start position:0% the optimizations are needed but there's generally<00:45:32.289> ways<00:45:32.859> to<00:45:33.069> make<00:45:33.220> the<00:45:33.369> optimization 00:45:34.079 --> 00:45:34.089 align:start position:0% generally ways to make the optimization 00:45:34.089 --> 00:45:37.829 align:start position:0% generally ways to make the optimization without<00:45:34.359> enshrining<00:45:34.749> too<00:45:34.960> many<00:45:35.140> things<00:45:36.839> it's 00:45:37.829 --> 00:45:37.839 align:start position:0% without enshrining too many things it's 00:45:37.839 --> 00:45:41.459 align:start position:0% without enshrining too many things it's important<00:45:38.140> to<00:45:38.229> note<00:45:38.380> the<00:45:39.779> the<00:45:40.779> notion<00:45:41.289> of 00:45:41.459 --> 00:45:41.469 align:start position:0% important to note the the notion of 00:45:41.469 --> 00:45:43.529 align:start position:0% important to note the the notion of owning<00:45:42.039> ether<00:45:42.489> actually<00:45:42.969> becomes<00:45:43.269> a<00:45:43.359> layer 00:45:43.529 --> 00:45:43.539 align:start position:0% owning ether actually becomes a layer 00:45:43.539 --> 00:45:45.959 align:start position:0% owning ether actually becomes a layer two<00:45:43.719> concept<00:45:44.140> in<00:45:44.380> ease<00:45:44.710> so<00:45:45.519> the<00:45:45.640> only<00:45:45.789> thing 00:45:45.959 --> 00:45:45.969 align:start position:0% two concept in ease so the only thing 00:45:45.969 --> 00:45:48.839 align:start position:0% two concept in ease so the only thing that<00:45:45.999> owns<00:45:46.329> ease<00:45:46.569> is<00:45:47.049> the<00:45:47.410> actually<00:45:47.920> easy<00:45:48.519> has 00:45:48.839 --> 00:45:48.849 align:start position:0% that owns ease is the actually easy has 00:45:48.849 --> 00:45:50.400 align:start position:0% that owns ease is the actually easy has a<00:45:48.880> balance<00:45:49.329> and<00:45:49.569> then<00:45:49.660> there's<00:45:49.839> some<00:45:50.049> sort<00:45:50.229> of 00:45:50.400 --> 00:45:50.410 align:start position:0% a balance and then there's some sort of 00:45:50.410 --> 00:45:52.440 align:start position:0% a balance and then there's some sort of presumably<00:45:51.339> some<00:45:51.609> sort<00:45:51.819> of<00:45:51.849> account<00:45:52.150> model 00:45:52.440 --> 00:45:52.450 align:start position:0% presumably some sort of account model 00:45:52.450 --> 00:45:53.969 align:start position:0% presumably some sort of account model and<00:45:52.569> state<00:45:52.749> model<00:45:53.049> within<00:45:53.229> that<00:45:53.469> ee<00:45:53.680> that's 00:45:53.969 --> 00:45:53.979 align:start position:0% and state model within that ee that's 00:45:53.979 --> 00:45:55.890 align:start position:0% and state model within that ee that's defined<00:45:54.369> that<00:45:54.880> allows<00:45:55.089> you<00:45:55.299> to<00:45:55.390> actually<00:45:55.749> have 00:45:55.890 --> 00:45:55.900 align:start position:0% defined that allows you to actually have 00:45:55.900 --> 00:45:57.719 align:start position:0% defined that allows you to actually have a<00:45:55.930> right<00:45:56.170> to<00:45:56.469> a<00:45:56.499> portion<00:45:57.069> of<00:45:57.160> that<00:45:57.219> either<00:45:57.400> and 00:45:57.719 --> 00:45:57.729 align:start position:0% a right to a portion of that either and 00:45:57.729 --> 00:45:59.370 align:start position:0% a right to a portion of that either and so<00:45:58.059> we've<00:45:58.210> actually<00:45:58.329> instead<00:45:58.869> of<00:45:58.930> enshrining 00:45:59.370 --> 00:45:59.380 align:start position:0% so we've actually instead of enshrining 00:45:59.380 --> 00:46:02.759 align:start position:0% so we've actually instead of enshrining tokens<00:45:59.859> we're<00:46:00.009> not<00:46:00.130> like<00:46:00.749> d<00:46:01.749> shrining<00:46:02.109> either 00:46:02.759 --> 00:46:02.769 align:start position:0% tokens we're not like d shrining either 00:46:02.769 --> 00:46:06.690 align:start position:0% tokens we're not like d shrining either within<00:46:03.190> within<00:46:03.880> the<00:46:05.249> alright<00:46:06.249> we<00:46:06.369> have<00:46:06.519> to 00:46:06.690 --> 00:46:06.700 align:start position:0% within within the alright we have to 00:46:06.700 --> 00:46:10.170 align:start position:0% within within the alright we have to stop<00:46:06.999> here<00:46:07.479> sorry<00:46:08.019> everyone<00:46:08.880> do<00:46:09.880> you<00:46:09.940> want<00:46:10.119> to 00:46:10.170 --> 00:46:10.180 align:start position:0% stop here sorry everyone do you want to 00:46:10.180 --> 00:46:12.690 align:start position:0% stop here sorry everyone do you want to talk<00:46:10.299> less<00:46:10.900> herded<00:46:11.349> coded<00:46:11.829> things<00:46:12.009> at<00:46:12.489> the<00:46:12.609> end 00:46:12.690 --> 00:46:12.700 align:start position:0% talk less herded coded things at the end 00:46:12.700 --> 00:46:15.469 align:start position:0% talk less herded coded things at the end of<00:46:12.789> the<00:46:12.849> day<00:46:12.940> is<00:46:12.999> better<00:46:13.349> you<00:46:14.349> know<00:46:14.469> so<00:46:14.799> I'm<00:46:14.950> not 00:46:15.469 --> 00:46:15.479 align:start position:0% of the day is better you know so I'm not 00:46:15.479 --> 00:46:19.410 align:start position:0% of the day is better you know so I'm not having<00:46:16.479> like<00:46:16.630> a<00:46:16.690> yeah<00:46:17.410> you<00:46:18.039> know<00:46:18.160> like<00:46:18.369> a<00:46:18.420> ERC 00:46:19.410 --> 00:46:19.420 align:start position:0% having like a yeah you know like a ERC 00:46:19.420 --> 00:46:21.479 align:start position:0% having like a yeah you know like a ERC hard-coded<00:46:20.049> just<00:46:20.410> gonna<00:46:20.710> be<00:46:21.039> better<00:46:21.309> because 00:46:21.479 --> 00:46:21.489 align:start position:0% hard-coded just gonna be better because 00:46:21.489 --> 00:46:24.359 align:start position:0% hard-coded just gonna be better because less<00:46:22.089> hard<00:46:22.329> Forex<00:46:22.719> less<00:46:23.069> nonsense<00:46:24.069> to<00:46:24.219> deal 00:46:24.359 --> 00:46:24.369 align:start position:0% less hard Forex less nonsense to deal 00:46:24.369 --> 00:46:33.830 align:start position:0% less hard Forex less nonsense to deal with<00:46:24.489> from<00:46:24.670> a<00:46:24.700> p.m.<00:46:25.180> perspective 00:46:33.830 --> 00:46:33.840 align:start position:0% 00:46:33.840 --> 00:46:35.900 align:start position:0% you