WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:12.090 align:start position:0% [Applause] 00:00:12.090 --> 00:00:12.100 align:start position:0% 00:00:12.100 --> 00:00:14.740 align:start position:0% like<00:00:13.100> the<00:00:13.280> concerns<00:00:13.730> of<00:00:13.940> this<00:00:14.120> proposal<00:00:14.480> is 00:00:14.740 --> 00:00:14.750 align:start position:0% like the concerns of this proposal is 00:00:14.750 --> 00:00:16.570 align:start position:0% like the concerns of this proposal is immense<00:00:15.019> to<00:00:15.200> adjust<00:00:15.650> mean<00:00:15.920> we<00:00:16.099> have<00:00:16.250> to<00:00:16.400> do 00:00:16.570 --> 00:00:16.580 align:start position:0% immense to adjust mean we have to do 00:00:16.580 --> 00:00:18.609 align:start position:0% immense to adjust mean we have to do with<00:00:16.760> kind<00:00:16.939> of<00:00:17.060> other<00:00:17.270> things<00:00:17.599> that<00:00:17.900> people 00:00:18.609 --> 00:00:18.619 align:start position:0% with kind of other things that people 00:00:18.619 --> 00:00:20.769 align:start position:0% with kind of other things that people have<00:00:19.070> been<00:00:19.099> complaining<00:00:19.610> of<00:00:20.240> Annabelle<00:00:20.630> at 00:00:20.769 --> 00:00:20.779 align:start position:0% have been complaining of Annabelle at 00:00:20.779 --> 00:00:23.470 align:start position:0% have been complaining of Annabelle at four<00:00:21.140> months<00:00:21.500> the<00:00:22.250> biggest<00:00:22.400> one<00:00:22.849> being<00:00:23.119> like 00:00:23.470 --> 00:00:23.480 align:start position:0% four months the biggest one being like 00:00:23.480 --> 00:00:26.650 align:start position:0% four months the biggest one being like few<00:00:23.750> markets<00:00:24.110> and<00:00:24.320> real<00:00:24.470> labor<00:00:24.680> markets<00:00:25.300> so<00:00:26.300> I 00:00:26.650 --> 00:00:26.660 align:start position:0% few markets and real labor markets so I 00:00:26.660 --> 00:00:29.650 align:start position:0% few markets and real labor markets so I will<00:00:27.380> kind<00:00:27.650> of<00:00:27.769> explain<00:00:28.189> the<00:00:28.550> problem<00:00:29.449> first 00:00:29.650 --> 00:00:29.660 align:start position:0% will kind of explain the problem first 00:00:29.660 --> 00:00:31.839 align:start position:0% will kind of explain the problem first so<00:00:30.080> the<00:00:30.199> problem<00:00:30.619> is<00:00:30.679> like<00:00:31.010> status<00:00:31.340> quo<00:00:31.640> is 00:00:31.839 --> 00:00:31.849 align:start position:0% so the problem is like status quo is 00:00:31.849 --> 00:00:34.750 align:start position:0% so the problem is like status quo is basically<00:00:32.269> a<00:00:32.390> bunch<00:00:32.870> of<00:00:32.960> shards<00:00:33.379> and<00:00:33.650> each<00:00:34.580> of 00:00:34.750 --> 00:00:34.760 align:start position:0% basically a bunch of shards and each of 00:00:34.760 --> 00:00:38.530 align:start position:0% basically a bunch of shards and each of these<00:00:34.910> shards<00:00:35.269> have<00:00:35.660> claws<00:00:36.370> but<00:00:37.370> the<00:00:37.940> shards 00:00:38.530 --> 00:00:38.540 align:start position:0% these shards have claws but the shards 00:00:38.540 --> 00:00:41.200 align:start position:0% these shards have claws but the shards only<00:00:39.140> fear<00:00:39.559> above<00:00:39.830> each<00:00:40.040> other<00:00:40.280> had<00:00:40.550> a<00:00:40.910> kind<00:00:41.150> of 00:00:41.200 --> 00:00:41.210 align:start position:0% only fear above each other had a kind of 00:00:41.210 --> 00:00:43.030 align:start position:0% only fear above each other had a kind of theory<00:00:41.420> delayed<00:00:41.870> schedule<00:00:42.110> and<00:00:42.559> like<00:00:42.680> this<00:00:42.860> is 00:00:43.030 --> 00:00:43.040 align:start position:0% theory delayed schedule and like this is 00:00:43.040 --> 00:00:44.950 align:start position:0% theory delayed schedule and like this is because<00:00:43.370> like<00:00:43.640> it's<00:00:44.479> somewhere<00:00:44.780> in<00:00:44.870> the 00:00:44.950 --> 00:00:44.960 align:start position:0% because like it's somewhere in the 00:00:44.960 --> 00:00:47.200 align:start position:0% because like it's somewhere in the middle<00:00:44.989> here<00:00:45.470> you<00:00:45.500> have<00:00:45.739> a<00:00:45.769> cross<00:00:46.010> linked<00:00:46.309> into 00:00:47.200 --> 00:00:47.210 align:start position:0% middle here you have a cross linked into 00:00:47.210 --> 00:00:50.410 align:start position:0% middle here you have a cross linked into the<00:00:47.239> beacon<00:00:47.600> chain<00:00:47.839> in<00:00:48.790> this<00:00:49.790> case<00:00:50.059> if<00:00:50.360> that 00:00:50.410 --> 00:00:50.420 align:start position:0% the beacon chain in this case if that 00:00:50.420 --> 00:00:53.910 align:start position:0% the beacon chain in this case if that was<00:00:50.780> about<00:00:51.769> one<00:00:52.040> block<00:00:52.400> and<00:00:53.030> so<00:00:53.239> basically 00:00:53.910 --> 00:00:53.920 align:start position:0% was about one block and so basically 00:00:53.920 --> 00:00:57.759 align:start position:0% was about one block and so basically like<00:00:54.920> at<00:00:55.250> base<00:00:55.970> in<00:00:56.570> the<00:00:56.690> status<00:00:57.019> quo<00:00:57.140> proposal 00:00:57.759 --> 00:00:57.769 align:start position:0% like at base in the status quo proposal 00:00:57.769 --> 00:01:00.100 align:start position:0% like at base in the status quo proposal had<00:00:57.890> basically<00:00:58.280> here<00:00:58.519> for<00:00:58.909> one<00:00:59.210> shard<00:00:59.540> to 00:01:00.100 --> 00:01:00.110 align:start position:0% had basically here for one shard to 00:01:00.110 --> 00:01:02.350 align:start position:0% had basically here for one shard to worm-like<00:01:00.650> state<00:01:01.159> birds<00:01:01.400> of<00:01:01.580> other<00:01:01.760> shards<00:01:02.210> it 00:01:02.350 --> 00:01:02.360 align:start position:0% worm-like state birds of other shards it 00:01:02.360 --> 00:01:06.700 align:start position:0% worm-like state birds of other shards it takes<00:01:02.570> like<00:01:02.869> about<00:01:03.170> six<00:01:03.409> minutes<00:01:03.790> and<00:01:05.200> vo<00:01:06.200> this 00:01:06.700 --> 00:01:06.710 align:start position:0% takes like about six minutes and vo this 00:01:06.710 --> 00:01:09.850 align:start position:0% takes like about six minutes and vo this is<00:01:06.770> obviously<00:01:07.460> bad<00:01:07.729> for<00:01:08.270> if<00:01:08.659> you<00:01:08.990> want<00:01:09.290> to<00:01:09.650> be 00:01:09.850 --> 00:01:09.860 align:start position:0% is obviously bad for if you want to be 00:01:09.860 --> 00:01:11.500 align:start position:0% is obviously bad for if you want to be able<00:01:09.950> to<00:01:10.070> have<00:01:10.280> any<00:01:10.400> kind<00:01:10.610> of<00:01:10.729> cross<00:01:10.970> straps 00:01:11.500 --> 00:01:11.510 align:start position:0% able to have any kind of cross straps 00:01:11.510 --> 00:01:13.929 align:start position:0% able to have any kind of cross straps and<00:01:12.260> the<00:01:12.380> purple<00:01:12.710> small<00:01:12.950> w<00:01:13.250> pants<00:01:13.460> just<00:01:13.729> thing 00:01:13.929 --> 00:01:13.939 align:start position:0% and the purple small w pants just thing 00:01:13.939 --> 00:01:15.639 align:start position:0% and the purple small w pants just thing to<00:01:14.060> get<00:01:14.210> around<00:01:14.420> this<00:01:14.659> basically<00:01:15.109> has<00:01:15.350> to<00:01:15.500> do 00:01:15.639 --> 00:01:15.649 align:start position:0% to get around this basically has to do 00:01:15.649 --> 00:01:17.230 align:start position:0% to get around this basically has to do with<00:01:15.799> these<00:01:16.039> connect<00:01:16.369> lofty<00:01:16.670> mystic<00:01:17.000> states 00:01:17.230 --> 00:01:17.240 align:start position:0% with these connect lofty mystic states 00:01:17.240 --> 00:01:19.389 align:start position:0% with these connect lofty mystic states so<00:01:18.079> basically<00:01:18.560> the<00:01:18.799> top<00:01:18.979> of<00:01:19.070> us<00:01:19.189> have 00:01:19.389 --> 00:01:19.399 align:start position:0% so basically the top of us have 00:01:19.399 --> 00:01:22.300 align:start position:0% so basically the top of us have optimistic<00:01:20.000> mechanism<00:01:20.570> that<00:01:20.719> says<00:01:21.020> oh<00:01:21.310> well 00:01:22.300 --> 00:01:22.310 align:start position:0% optimistic mechanism that says oh well 00:01:22.310 --> 00:01:26.080 align:start position:0% optimistic mechanism that says oh well if<00:01:22.850> you're<00:01:23.090> over<00:01:23.420> here<00:01:23.689> then<00:01:24.409> you<00:01:25.070> can<00:01:25.759> make<00:01:25.939> a 00:01:26.080 --> 00:01:26.090 align:start position:0% if you're over here then you can make a 00:01:26.090 --> 00:01:27.880 align:start position:0% if you're over here then you can make a kind<00:01:26.299> of<00:01:26.390> conditional<00:01:26.990> block<00:01:27.140> that<00:01:27.530> said<00:01:27.770> I<00:01:27.859> am 00:01:27.880 --> 00:01:27.890 align:start position:0% kind of conditional block that said I am 00:01:27.890 --> 00:01:30.370 align:start position:0% kind of conditional block that said I am this<00:01:28.670> conditional<00:01:29.270> block<00:01:29.390> just<00:01:29.899> that<00:01:30.049> access 00:01:30.370 --> 00:01:30.380 align:start position:0% this conditional block just that access 00:01:30.380 --> 00:01:32.560 align:start position:0% this conditional block just that access all<00:01:30.619> I<00:01:30.649> think<00:01:30.770> this<00:01:31.100> team<00:01:31.310> I<00:01:31.579> think<00:01:31.909> the<00:01:32.359> state 00:01:32.560 --> 00:01:32.570 align:start position:0% all I think this team I think the state 00:01:32.570 --> 00:01:34.270 align:start position:0% all I think this team I think the state route<00:01:32.840> of<00:01:33.049> this<00:01:33.200> chart<00:01:33.530> actually<00:01:34.039> is<00:01:34.130> this 00:01:34.270 --> 00:01:34.280 align:start position:0% route of this chart actually is this 00:01:34.280 --> 00:01:36.840 align:start position:0% route of this chart actually is this value<00:01:35.020> given<00:01:36.020> is<00:01:36.140> missed 00:01:36.840 --> 00:01:36.850 align:start position:0% value given is missed 00:01:36.850 --> 00:01:40.469 align:start position:0% value given is missed that<00:01:37.000> is<00:01:37.540> going<00:01:37.689> to<00:01:37.750> do<00:01:37.840> this<00:01:38.580> and<00:01:39.580> you<00:01:40.240> just 00:01:40.469 --> 00:01:40.479 align:start position:0% that is going to do this and you just 00:01:40.479 --> 00:01:42.330 align:start position:0% that is going to do this and you just have<00:01:40.689> these<00:01:40.869> blocks<00:01:41.110> identity<00:01:41.799> exists<00:01:42.130> as 00:01:42.330 --> 00:01:42.340 align:start position:0% have these blocks identity exists as 00:01:42.340 --> 00:01:43.920 align:start position:0% have these blocks identity exists as something<00:01:42.369> on<00:01:42.790> way<00:01:42.939> or<00:01:43.090> two<00:01:43.299> and<00:01:43.630> that<00:01:43.780> there 00:01:43.920 --> 00:01:43.930 align:start position:0% something on way or two and that there 00:01:43.930 --> 00:01:45.390 align:start position:0% something on way or two and that there would<00:01:44.049> be<00:01:44.080> these<00:01:44.380> different<00:01:44.770> at<00:01:44.860> a<00:01:44.890> protocols 00:01:45.390 --> 00:01:45.400 align:start position:0% would be these different at a protocols 00:01:45.400 --> 00:01:47.910 align:start position:0% would be these different at a protocols for<00:01:45.580> achieving<00:01:45.880> this<00:01:46.210> and<00:01:46.479> at<00:01:47.320> some<00:01:47.619> point 00:01:47.910 --> 00:01:47.920 align:start position:0% for achieving this and at some point 00:01:47.920 --> 00:01:50.219 align:start position:0% for achieving this and at some point later<00:01:48.130> there<00:01:49.030> would<00:01:49.090> be<00:01:49.150> some<00:01:49.479> leader<00:01:49.720> process 00:01:50.219 --> 00:01:50.229 align:start position:0% later there would be some leader process 00:01:50.229 --> 00:01:51.810 align:start position:0% later there would be some leader process over<00:01:50.470> here<00:01:50.740> and<00:01:50.920> then<00:01:51.009> I<00:01:51.250> kind<00:01:51.460> of<00:01:51.520> storms 00:01:51.810 --> 00:01:51.820 align:start position:0% over here and then I kind of storms 00:01:51.820 --> 00:01:53.190 align:start position:0% over here and then I kind of storms through<00:01:52.000> all<00:01:52.090> these<00:01:52.240> small<00:01:52.479> X<00:01:52.659> figures<00:01:53.020> out 00:01:53.190 --> 00:01:53.200 align:start position:0% through all these small X figures out 00:01:53.200 --> 00:01:55.530 align:start position:0% through all these small X figures out which<00:01:53.380> ones<00:01:53.710> are<00:01:54.040> kind<00:01:54.850> of<00:01:54.940> correct<00:01:55.330> which 00:01:55.530 --> 00:01:55.540 align:start position:0% which ones are kind of correct which 00:01:55.540 --> 00:01:57.870 align:start position:0% which ones are kind of correct which ones<00:01:55.750> are<00:01:55.869> not<00:01:56.020> correct<00:01:56.440> and<00:01:56.830> kind<00:01:57.460> of<00:01:57.580> threads 00:01:57.870 --> 00:01:57.880 align:start position:0% ones are not correct and kind of threads 00:01:57.880 --> 00:02:00.630 align:start position:0% ones are not correct and kind of threads everything<00:01:58.330> together<00:01:58.479> red<00:01:59.350> so<00:01:59.619> and<00:02:00.220> if<00:02:00.369> step 00:02:00.630 --> 00:02:00.640 align:start position:0% everything together red so and if step 00:02:00.640 --> 00:02:02.789 align:start position:0% everything together red so and if step one<00:02:00.850> block<00:02:01.539> silver<00:02:01.930> sphere<00:02:01.990> or<00:02:02.500> kind<00:02:02.710> of 00:02:02.789 --> 00:02:02.799 align:start position:0% one block silver sphere or kind of 00:02:02.799 --> 00:02:04.859 align:start position:0% one block silver sphere or kind of packages<00:02:03.310> over<00:02:03.549> here<00:02:03.850> out<00:02:04.119> of<00:02:04.149> publish<00:02:04.600> ahead 00:02:04.859 --> 00:02:04.869 align:start position:0% packages over here out of publish ahead 00:02:04.869 --> 00:02:07.200 align:start position:0% packages over here out of publish ahead of<00:02:04.960> time<00:02:05.220> opinions<00:02:06.220> about<00:02:06.399> what<00:02:06.759> happens<00:02:07.090> in 00:02:07.200 --> 00:02:07.210 align:start position:0% of time opinions about what happens in 00:02:07.210 --> 00:02:09.120 align:start position:0% of time opinions about what happens in other<00:02:07.360> shorts<00:02:07.869> and<00:02:08.229> these<00:02:08.500> opinions<00:02:08.800> are<00:02:09.100> not 00:02:09.120 --> 00:02:09.130 align:start position:0% other shorts and these opinions are not 00:02:09.130 --> 00:02:10.650 align:start position:0% other shorts and these opinions are not necessarily<00:02:09.729> over<00:02:09.819> two<00:02:10.000> percent<00:02:10.119> correct 00:02:10.650 --> 00:02:10.660 align:start position:0% necessarily over two percent correct 00:02:10.660 --> 00:02:12.090 align:start position:0% necessarily over two percent correct where<00:02:10.840> things<00:02:11.080> have<00:02:11.290> it<00:02:11.440> based<00:02:11.620> off<00:02:11.800> of<00:02:11.860> those 00:02:12.090 --> 00:02:12.100 align:start position:0% where things have it based off of those 00:02:12.100 --> 00:02:13.979 align:start position:0% where things have it based off of those opinions<00:02:12.340> until<00:02:12.970> things<00:02:13.150> have<00:02:13.360> dependencies 00:02:13.979 --> 00:02:13.989 align:start position:0% opinions until things have dependencies 00:02:13.989 --> 00:02:18.120 align:start position:0% opinions until things have dependencies and<00:02:14.739> clients<00:02:15.550> can<00:02:16.420> like<00:02:17.200> basically<00:02:17.739> figure 00:02:18.120 --> 00:02:18.130 align:start position:0% and clients can like basically figure 00:02:18.130 --> 00:02:20.040 align:start position:0% and clients can like basically figure out<00:02:18.250> ahead<00:02:18.489> of<00:02:18.610> time<00:02:18.880> like<00:02:19.180> all<00:02:19.600> these<00:02:19.750> walks 00:02:20.040 --> 00:02:20.050 align:start position:0% out ahead of time like all these walks 00:02:20.050 --> 00:02:21.690 align:start position:0% out ahead of time like all these walks will<00:02:20.260> get<00:02:20.410> one<00:02:20.620> yes<00:02:20.769> I<00:02:21.130> kind<00:02:21.370> of<00:02:21.430> glued 00:02:21.690 --> 00:02:21.700 align:start position:0% will get one yes I kind of glued 00:02:21.700 --> 00:02:24.000 align:start position:0% will get one yes I kind of glued together<00:02:21.850> but<00:02:22.390> then<00:02:22.630> there<00:02:23.230> is<00:02:23.380> a<00:02:23.410> process 00:02:24.000 --> 00:02:24.010 align:start position:0% together but then there is a process 00:02:24.010 --> 00:02:25.770 align:start position:0% together but then there is a process that<00:02:24.220> kind<00:02:24.459> of<00:02:24.519> whose<00:02:24.790> these<00:02:24.970> walks<00:02:25.269> to<00:02:25.569> cut 00:02:25.770 --> 00:02:25.780 align:start position:0% that kind of whose these walks to cut 00:02:25.780 --> 00:02:27.710 align:start position:0% that kind of whose these walks to cut together<00:02:26.019> one<00:02:26.380> chain<00:02:26.680> and<00:02:26.709> up<00:02:27.040> in<00:02:27.130> the<00:02:27.220> future 00:02:27.710 --> 00:02:27.720 align:start position:0% together one chain and up in the future 00:02:27.720 --> 00:02:30.809 align:start position:0% together one chain and up in the future and<00:02:28.860> execution<00:02:29.860> environments<00:02:30.400> are<00:02:30.519> supposed 00:02:30.809 --> 00:02:30.819 align:start position:0% and execution environments are supposed 00:02:30.819 --> 00:02:32.220 align:start position:0% and execution environments are supposed to<00:02:30.880> rather<00:02:31.180> than<00:02:31.420> be<00:02:31.569> able<00:02:31.840> to<00:02:31.959> implement 00:02:32.220 --> 00:02:32.230 align:start position:0% to rather than be able to implement 00:02:32.230 --> 00:02:37.289 align:start position:0% to rather than be able to implement signals<00:02:32.819> the<00:02:33.819> reason<00:02:34.299> why<00:02:34.660> this<00:02:34.720> is<00:02:36.299> because 00:02:37.289 --> 00:02:37.299 align:start position:0% signals the reason why this is because 00:02:37.299 --> 00:02:39.900 align:start position:0% signals the reason why this is because this<00:02:38.019> is<00:02:38.200> not<00:02:38.350> very<00:02:38.560> nice<00:02:38.920> it's<00:02:39.459> basically 00:02:39.900 --> 00:02:39.910 align:start position:0% this is not very nice it's basically 00:02:39.910 --> 00:02:42.930 align:start position:0% this is not very nice it's basically because<00:02:40.269> if<00:02:41.079> he<00:02:41.530> wants<00:02:41.860> to<00:02:41.980> look<00:02:42.190> at<00:02:42.400> this<00:02:42.640> from 00:02:42.930 --> 00:02:42.940 align:start position:0% because if he wants to look at this from 00:02:42.940 --> 00:02:44.850 align:start position:0% because if he wants to look at this from a<00:02:42.970> point<00:02:43.239> of<00:02:43.390> view<00:02:43.450> of<00:02:43.720> like<00:02:44.140> I<00:02:44.380> am<00:02:44.620> a 00:02:44.850 --> 00:02:44.860 align:start position:0% a point of view of like I am a 00:02:44.860 --> 00:02:49.280 align:start position:0% a point of view of like I am a transaction<00:02:45.459> center<00:02:45.820> you<00:02:46.420> know<00:02:46.510> hi<00:02:47.230> I'm<00:02:47.680> Alice 00:02:49.280 --> 00:02:49.290 align:start position:0% transaction center you know hi I'm Alice 00:02:49.290 --> 00:02:52.890 align:start position:0% transaction center you know hi I'm Alice and<00:02:50.519> I<00:02:51.519> want<00:02:51.820> to<00:02:51.940> send<00:02:52.150> some<00:02:52.239> points<00:02:52.630> to<00:02:52.720> Bob 00:02:52.890 --> 00:02:52.900 align:start position:0% and I want to send some points to Bob 00:02:52.900 --> 00:02:57.449 align:start position:0% and I want to send some points to Bob and<00:02:53.829> I<00:02:54.480> Alice<00:02:55.480> I<00:02:55.720> have<00:02:55.930> points<00:02:56.650> on<00:02:56.890> this<00:02:57.160> chart 00:02:57.449 --> 00:02:57.459 align:start position:0% and I Alice I have points on this chart 00:02:57.459 --> 00:03:01.470 align:start position:0% and I Alice I have points on this chart but<00:02:58.150> it<00:02:58.769> turns<00:02:59.769> but<00:03:00.130> what<00:03:00.910> I<00:03:00.940> do<00:03:01.090> what<00:03:01.239> someone 00:03:01.470 --> 00:03:01.480 align:start position:0% but it turns but what I do what someone 00:03:01.480 --> 00:03:02.030 align:start position:0% but it turns but what I do what someone says 00:03:02.030 --> 00:03:02.040 align:start position:0% says 00:03:02.040 --> 00:03:05.119 align:start position:0% says it's<00:03:02.220> over<00:03:02.400> to<00:03:02.489> Bob<00:03:02.670> and<00:03:03.180> you<00:03:03.450> have<00:03:03.980> Bob<00:03:04.980> over 00:03:05.119 --> 00:03:05.129 align:start position:0% it's over to Bob and you have Bob over 00:03:05.129 --> 00:03:07.130 align:start position:0% it's over to Bob and you have Bob over Sierra<00:03:05.549> and<00:03:05.819> Alice<00:03:06.510> well<00:03:06.720> successful 00:03:07.130 --> 00:03:07.140 align:start position:0% Sierra and Alice well successful 00:03:07.140 --> 00:03:08.990 align:start position:0% Sierra and Alice well successful defensive<00:03:07.590> Wednesday<00:03:07.950> law<00:03:08.099> and<00:03:08.549> then<00:03:08.730> Bob 00:03:08.990 --> 00:03:09.000 align:start position:0% defensive Wednesday law and then Bob 00:03:09.000 --> 00:03:10.850 align:start position:0% defensive Wednesday law and then Bob Ameet<00:03:09.450> wants<00:03:09.810> to<00:03:09.930> be<00:03:10.049> able<00:03:10.140> to<00:03:10.290> do<00:03:10.439> things<00:03:10.680> with 00:03:10.850 --> 00:03:10.860 align:start position:0% Ameet wants to be able to do things with 00:03:10.860 --> 00:03:12.440 align:start position:0% Ameet wants to be able to do things with those<00:03:11.010> points<00:03:11.370> immediately<00:03:11.849> like<00:03:12.060> sending 00:03:12.440 --> 00:03:12.450 align:start position:0% those points immediately like sending 00:03:12.450 --> 00:03:13.970 align:start position:0% those points immediately like sending them<00:03:12.599> to<00:03:12.720> Charlie<00:03:13.110> or<00:03:13.140> putting<00:03:13.620> them<00:03:13.860> into 00:03:13.970 --> 00:03:13.980 align:start position:0% them to Charlie or putting them into 00:03:13.980 --> 00:03:15.619 align:start position:0% them to Charlie or putting them into Eunice<00:03:14.310> lava<00:03:14.579> which<00:03:15.269> one<00:03:15.480> would 00:03:15.619 --> 00:03:15.629 align:start position:0% Eunice lava which one would 00:03:15.629 --> 00:03:17.240 align:start position:0% Eunice lava which one would automatically<00:03:16.140> send<00:03:16.439> some<00:03:16.620> die<00:03:16.769> to<00:03:16.829> generally 00:03:17.240 --> 00:03:17.250 align:start position:0% automatically send some die to generally 00:03:17.250 --> 00:03:20.449 align:start position:0% automatically send some die to generally but<00:03:18.180> if<00:03:18.629> Alice<00:03:19.079> test<00:03:19.409> planes<00:03:19.680> and<00:03:19.920> Alice<00:03:20.220> sense 00:03:20.449 --> 00:03:20.459 align:start position:0% but if Alice test planes and Alice sense 00:03:20.459 --> 00:03:22.850 align:start position:0% but if Alice test planes and Alice sense wins<00:03:20.760> the<00:03:20.909> bottom<00:03:21.239> then<00:03:21.659> the<00:03:21.959> coins<00:03:22.319> like<00:03:22.709> the 00:03:22.850 --> 00:03:22.860 align:start position:0% wins the bottom then the coins like the 00:03:22.860 --> 00:03:25.309 align:start position:0% wins the bottom then the coins like the underlying<00:03:23.370> based<00:03:23.730> protocol<00:03:24.239> of<00:03:24.420> ether<00:03:24.870> we're 00:03:25.309 --> 00:03:25.319 align:start position:0% underlying based protocol of ether we're 00:03:25.319 --> 00:03:27.380 align:start position:0% underlying based protocol of ether we're not<00:03:25.470> going<00:03:25.709> over<00:03:25.799> here<00:03:26.099> immediately<00:03:26.579> and<00:03:26.879> so 00:03:27.380 --> 00:03:27.390 align:start position:0% not going over here immediately and so 00:03:27.390 --> 00:03:29.809 align:start position:0% not going over here immediately and so Bob<00:03:27.659> does<00:03:28.019> not<00:03:28.200> yet<00:03:28.470> have<00:03:28.530> protocol<00:03:29.489> level 00:03:29.809 --> 00:03:29.819 align:start position:0% Bob does not yet have protocol level 00:03:29.819 --> 00:03:31.910 align:start position:0% Bob does not yet have protocol level either<00:03:29.909> Bob<00:03:30.599> has<00:03:30.930> kind<00:03:31.290> of<00:03:31.349> gone<00:03:31.500> from<00:03:31.739> too 00:03:31.910 --> 00:03:31.920 align:start position:0% either Bob has kind of gone from too 00:03:31.920 --> 00:03:33.470 align:start position:0% either Bob has kind of gone from too optimistic<00:03:32.099> ether<00:03:32.819> which<00:03:33.209> will<00:03:33.359> become 00:03:33.470 --> 00:03:33.480 align:start position:0% optimistic ether which will become 00:03:33.480 --> 00:03:36.649 align:start position:0% optimistic ether which will become protocol<00:03:34.079> no<00:03:34.230> mediator<00:03:34.500> but<00:03:35.280> I<00:03:35.909> mean<00:03:36.510> what 00:03:36.649 --> 00:03:36.659 align:start position:0% protocol no mediator but I mean what 00:03:36.659 --> 00:03:39.680 align:start position:0% protocol no mediator but I mean what because<00:03:37.140> like<00:03:37.650> it's<00:03:38.310> voodoo<00:03:38.940> ether<00:03:39.359> is<00:03:39.510> only 00:03:39.680 --> 00:03:39.690 align:start position:0% because like it's voodoo ether is only 00:03:39.690 --> 00:03:42.140 align:start position:0% because like it's voodoo ether is only your<00:03:39.840> two<00:03:40.049> things<00:03:40.349> like<00:03:40.829> we<00:03:41.010> can't<00:03:41.310> trust<00:03:41.730> what 00:03:42.140 --> 00:03:42.150 align:start position:0% your two things like we can't trust what 00:03:42.150 --> 00:03:44.300 align:start position:0% your two things like we can't trust what proposers<00:03:42.780> to<00:03:43.019> understand<00:03:43.560> what<00:03:43.799> who<00:03:43.950> Demeter 00:03:44.300 --> 00:03:44.310 align:start position:0% proposers to understand what who Demeter 00:03:44.310 --> 00:03:46.520 align:start position:0% proposers to understand what who Demeter is<00:03:44.340> because<00:03:44.909> what<00:03:45.150> reporters<00:03:45.659> are<00:03:45.959> not 00:03:46.520 --> 00:03:46.530 align:start position:0% is because what reporters are not 00:03:46.530 --> 00:03:48.680 align:start position:0% is because what reporters are not expected<00:03:47.190> to<00:03:47.340> speak<00:03:47.639> all<00:03:47.819> of<00:03:47.849> these<00:03:48.120> execution 00:03:48.680 --> 00:03:48.690 align:start position:0% expected to speak all of these execution 00:03:48.690 --> 00:03:51.740 align:start position:0% expected to speak all of these execution environment<00:03:49.170> languages<00:03:49.709> and<00:03:49.950> so<00:03:50.750> block 00:03:51.740 --> 00:03:51.750 align:start position:0% environment languages and so block 00:03:51.750 --> 00:03:54.110 align:start position:0% environment languages and so block proposal<00:03:52.409> I<00:03:52.709> basically<00:03:53.099> bought<00:03:53.400> has<00:03:53.700> nothing 00:03:54.110 --> 00:03:54.120 align:start position:0% proposal I basically bought has nothing 00:03:54.120 --> 00:03:55.640 align:start position:0% proposal I basically bought has nothing with<00:03:54.239> which<00:03:54.299> to<00:03:54.480> take<00:03:54.780> love<00:03:54.989> proposers 00:03:55.640 --> 00:03:55.650 align:start position:0% with which to take love proposers 00:03:55.650 --> 00:03:58.399 align:start position:0% with which to take love proposers until<00:03:56.579> media<00:03:57.420> stuff<00:03:57.720> with<00:03:57.930> later<00:03:58.170> in<00:03:58.319> the 00:03:58.399 --> 00:03:58.409 align:start position:0% until media stuff with later in the 00:03:58.409 --> 00:03:59.930 align:start position:0% until media stuff with later in the future<00:03:58.560> is<00:03:58.920> either<00:03:59.190> becomes<00:03:59.519> real 00:03:59.930 --> 00:03:59.940 align:start position:0% future is either becomes real 00:03:59.940 --> 00:04:02.089 align:start position:0% future is either becomes real which<00:04:00.090> one<00:04:00.269> happen<00:04:00.540> over<00:04:00.750> here<00:04:00.930> and<00:04:01.650> so<00:04:01.859> Bob 00:04:02.089 --> 00:04:02.099 align:start position:0% which one happen over here and so Bob 00:04:02.099 --> 00:04:03.920 align:start position:0% which one happen over here and so Bob like<00:04:02.459> theoretically<00:04:02.940> has<00:04:03.150> coins<00:04:03.420> but<00:04:03.659> do<00:04:03.810> not 00:04:03.920 --> 00:04:03.930 align:start position:0% like theoretically has coins but do not 00:04:03.930 --> 00:04:07.099 align:start position:0% like theoretically has coins but do not pay<00:04:04.109> transaction<00:04:04.680> fees<00:04:04.879> so<00:04:05.879> this<00:04:06.840> has 00:04:07.099 --> 00:04:07.109 align:start position:0% pay transaction fees so this has 00:04:07.109 --> 00:04:08.839 align:start position:0% pay transaction fees so this has historically<00:04:07.650> even<00:04:08.010> kind<00:04:08.220> of<00:04:08.250> salt<00:04:08.519> with<00:04:08.819> the 00:04:08.839 --> 00:04:08.849 align:start position:0% historically even kind of salt with the 00:04:08.849 --> 00:04:10.819 align:start position:0% historically even kind of salt with the scent<00:04:09.269> of<00:04:09.299> magic<00:04:09.510> catch<00:04:09.870> but<00:04:10.139> it's<00:04:10.260> really<00:04:10.590> our 00:04:10.819 --> 00:04:10.829 align:start position:0% scent of magic catch but it's really our 00:04:10.829 --> 00:04:13.220 align:start position:0% scent of magic catch but it's really our markets<00:04:11.310> but<00:04:11.609> we've<00:04:12.419> been<00:04:12.750> kind<00:04:13.019> of<00:04:13.109> thinking 00:04:13.220 --> 00:04:13.230 align:start position:0% markets but we've been kind of thinking 00:04:13.230 --> 00:04:16.400 align:start position:0% markets but we've been kind of thinking about<00:04:13.650> the<00:04:13.949> labor<00:04:14.160> markets<00:04:14.579> recently<00:04:15.410> like 00:04:16.400 --> 00:04:16.410 align:start position:0% about the labor markets recently like 00:04:16.410 --> 00:04:18.949 align:start position:0% about the labor markets recently like realizing<00:04:17.400> more<00:04:17.729> and<00:04:17.789> more<00:04:17.940> that<00:04:18.090> first<00:04:18.810> of 00:04:18.949 --> 00:04:18.959 align:start position:0% realizing more and more that first of 00:04:18.959 --> 00:04:21.229 align:start position:0% realizing more and more that first of all<00:04:19.109> this<00:04:19.709> kind<00:04:19.949> of<00:04:20.039> design<00:04:20.340> like<00:04:20.400> it<00:04:20.760> seems<00:04:21.030> to 00:04:21.229 --> 00:04:21.239 align:start position:0% all this kind of design like it seems to 00:04:21.239 --> 00:04:23.029 align:start position:0% all this kind of design like it seems to minimize<00:04:21.570> away<00:04:21.810> or<00:04:21.930> one<00:04:22.079> complexity<00:04:22.770> but<00:04:22.919> in 00:04:23.029 --> 00:04:23.039 align:start position:0% minimize away or one complexity but in 00:04:23.039 --> 00:04:25.100 align:start position:0% minimize away or one complexity but in passing<00:04:23.520> a<00:04:23.639> lot<00:04:23.880> employer<00:04:24.180> to<00:04:24.419> complexity 00:04:25.100 --> 00:04:25.110 align:start position:0% passing a lot employer to complexity 00:04:25.110 --> 00:04:26.810 align:start position:0% passing a lot employer to complexity around<00:04:25.349> all<00:04:25.470> these<00:04:25.530> optimistic<00:04:26.160> games<00:04:26.400> and 00:04:26.810 --> 00:04:26.820 align:start position:0% around all these optimistic games and 00:04:26.820 --> 00:04:29.060 align:start position:0% around all these optimistic games and real<00:04:27.810> labor<00:04:27.990> markets<00:04:28.380> get<00:04:28.530> monopolized 00:04:29.060 --> 00:04:29.070 align:start position:0% real labor markets get monopolized 00:04:29.070 --> 00:04:30.250 align:start position:0% real labor markets get monopolized easily<00:04:29.580> there's 00:04:30.250 --> 00:04:30.260 align:start position:0% easily there's 00:04:30.260 --> 00:04:32.250 align:start position:0% easily there's and<00:04:31.190> a<00:04:31.310> lot<00:04:31.460> of<00:04:31.490> other<00:04:31.730> nasty<00:04:32.120> stuff 00:04:32.250 --> 00:04:32.260 align:start position:0% and a lot of other nasty stuff 00:04:32.260 --> 00:04:35.880 align:start position:0% and a lot of other nasty stuff so<00:04:33.280> that's<00:04:34.280> the<00:04:34.430> problem 00:04:35.880 --> 00:04:35.890 align:start position:0% so that's the problem 00:04:35.890 --> 00:04:45.120 align:start position:0% so that's the problem so<00:04:36.890> here<00:04:37.220> is<00:04:37.430> the<00:04:37.970> solution<00:04:43.540> the<00:04:44.540> solution 00:04:45.120 --> 00:04:45.130 align:start position:0% so here is the solution the solution 00:04:45.130 --> 00:04:48.730 align:start position:0% so here is the solution the solution basically<00:04:46.130> says<00:04:46.370> we<00:04:46.880> have<00:04:47.240> that<00:04:48.200> we<00:04:48.560> have<00:04:48.590> a 00:04:48.730 --> 00:04:48.740 align:start position:0% basically says we have that we have a 00:04:48.740 --> 00:04:51.940 align:start position:0% basically says we have that we have a bunch<00:04:48.980> of<00:04:49.070> different<00:04:49.250> charts<00:04:49.730> and<00:04:50.830> what<00:04:51.830> we're 00:04:51.940 --> 00:04:51.950 align:start position:0% bunch of different charts and what we're 00:04:51.950 --> 00:04:53.200 align:start position:0% bunch of different charts and what we're going<00:04:52.160> to<00:04:52.220> do<00:04:52.400> is<00:04:52.550> basically<00:04:52.700> have<00:04:53.180> a 00:04:53.200 --> 00:04:53.210 align:start position:0% going to do is basically have a 00:04:53.210 --> 00:04:55.120 align:start position:0% going to do is basically have a cross-linked<00:04:53.780> kinetics<00:04:54.110> lab<00:04:54.320> so<00:04:54.860> these 00:04:55.120 --> 00:04:55.130 align:start position:0% cross-linked kinetics lab so these 00:04:55.130 --> 00:04:56.830 align:start position:0% cross-linked kinetics lab so these charts<00:04:55.460> are<00:04:55.670> going<00:04:56.090> to<00:04:56.150> get<00:04:56.270> across<00:04:56.390> with<00:04:56.660> a 00:04:56.830 --> 00:04:56.840 align:start position:0% charts are going to get across with a 00:04:56.840 --> 00:05:01.180 align:start position:0% charts are going to get across with a good<00:04:57.320> block<00:04:57.560> and<00:04:58.490> then<00:04:59.200> the<00:05:00.200> short<00:05:00.500> blocks<00:05:00.800> of 00:05:01.180 --> 00:05:01.190 align:start position:0% good block and then the short blocks of 00:05:01.190 --> 00:05:02.500 align:start position:0% good block and then the short blocks of the<00:05:01.310> next<00:05:01.580> slide<00:05:01.790> are<00:05:02.030> going<00:05:02.150> to<00:05:02.210> be<00:05:02.270> aware<00:05:02.450> of 00:05:02.500 --> 00:05:02.510 align:start position:0% the next slide are going to be aware of 00:05:02.510 --> 00:05:05.140 align:start position:0% the next slide are going to be aware of the<00:05:03.170> output<00:05:03.800> of<00:05:03.830> the<00:05:03.980> beacon<00:05:04.250> water<00:05:04.520> they're 00:05:05.140 --> 00:05:05.150 align:start position:0% the output of the beacon water they're 00:05:05.150 --> 00:05:06.820 align:start position:0% the output of the beacon water they're gonna<00:05:05.330> do<00:05:05.540> things<00:05:05.750> and<00:05:06.080> then<00:05:06.410> they're<00:05:06.710> going 00:05:06.820 --> 00:05:06.830 align:start position:0% gonna do things and then they're going 00:05:06.830 --> 00:05:08.770 align:start position:0% gonna do things and then they're going to<00:05:06.890> be<00:05:06.950> included<00:05:07.400> over<00:05:07.610> here<00:05:07.910> and<00:05:08.390> then<00:05:08.690> you 00:05:08.770 --> 00:05:08.780 align:start position:0% to be included over here and then you 00:05:08.780 --> 00:05:11.920 align:start position:0% to be included over here and then you have<00:05:08.810> another<00:05:09.020> region<00:05:09.530> plug<00:05:10.750> then<00:05:11.750> an 00:05:11.920 --> 00:05:11.930 align:start position:0% have another region plug then an 00:05:11.930 --> 00:05:14.890 align:start position:0% have another region plug then an overseer<00:05:12.530> human<00:05:12.890> have<00:05:13.300> more<00:05:14.300> sharp<00:05:14.570> blocks 00:05:14.890 --> 00:05:14.900 align:start position:0% overseer human have more sharp blocks 00:05:14.900 --> 00:05:18.340 align:start position:0% overseer human have more sharp blocks and<00:05:15.230> so<00:05:15.890> you<00:05:15.950> have<00:05:16.460> kind<00:05:16.760> of<00:05:16.970> a<00:05:17.240> much<00:05:17.960> tighter 00:05:18.340 --> 00:05:18.350 align:start position:0% and so you have kind of a much tighter 00:05:18.350 --> 00:05:21.160 align:start position:0% and so you have kind of a much tighter coupling<00:05:19.070> between<00:05:19.250> the<00:05:19.580> shards<00:05:20.030> where<00:05:20.300> each 00:05:21.160 --> 00:05:21.170 align:start position:0% coupling between the shards where each 00:05:21.170 --> 00:05:23.800 align:start position:0% coupling between the shards where each shard<00:05:21.590> like<00:05:22.190> any<00:05:22.490> block<00:05:22.910> on<00:05:23.090> any<00:05:23.270> lunch<00:05:23.450> lauren 00:05:23.800 --> 00:05:23.810 align:start position:0% shard like any block on any lunch lauren 00:05:23.810 --> 00:05:25.540 align:start position:0% shard like any block on any lunch lauren is<00:05:23.930> aware<00:05:24.200> of<00:05:24.320> everything<00:05:24.590> that<00:05:25.070> happens<00:05:25.460> on 00:05:25.540 --> 00:05:25.550 align:start position:0% is aware of everything that happens on 00:05:25.550 --> 00:05:29.920 align:start position:0% is aware of everything that happens on the<00:05:25.760> previous<00:05:26.390> charts<00:05:27.190> so<00:05:28.300> the<00:05:29.300> reason<00:05:29.660> why 00:05:29.920 --> 00:05:29.930 align:start position:0% the previous charts so the reason why 00:05:29.930 --> 00:05:32.590 align:start position:0% the previous charts so the reason why you<00:05:29.960> this<00:05:30.350> is<00:05:30.530> nice<00:05:30.770> now<00:05:31.010> is<00:05:31.370> because<00:05:31.820> like<00:05:32.450> on 00:05:32.590 --> 00:05:32.600 align:start position:0% you this is nice now is because like on 00:05:32.600 --> 00:05:33.910 align:start position:0% you this is nice now is because like on top<00:05:32.840> of<00:05:33.020> this<00:05:33.140> we<00:05:33.320> can<00:05:33.470> also<00:05:33.650> add 00:05:33.910 --> 00:05:33.920 align:start position:0% top of this we can also add 00:05:33.920 --> 00:05:35.860 align:start position:0% top of this we can also add functionality<00:05:34.520> for<00:05:35.030> Andrew<00:05:35.450> may<00:05:35.570> be<00:05:35.630> there 00:05:35.860 --> 00:05:35.870 align:start position:0% functionality for Andrew may be there 00:05:35.870 --> 00:05:37.720 align:start position:0% functionality for Andrew may be there between<00:05:35.960> charts<00:05:36.530> within<00:05:36.800> a<00:05:36.860> single<00:05:37.040> slot<00:05:37.400> and 00:05:37.720 --> 00:05:37.730 align:start position:0% between charts within a single slot and 00:05:37.730 --> 00:05:42.490 align:start position:0% between charts within a single slot and so<00:05:38.300> if<00:05:39.070> Alice<00:05:40.070> has<00:05:40.400> peso<00:05:41.390> coins<00:05:41.840> over<00:05:42.020> here 00:05:42.490 --> 00:05:42.500 align:start position:0% so if Alice has peso coins over here 00:05:42.500 --> 00:05:44.680 align:start position:0% so if Alice has peso coins over here then<00:05:43.040> Alice<00:05:43.610> over<00:05:43.850> here<00:05:44.090> I<00:05:44.120> can<00:05:44.300> just<00:05:44.480> make<00:05:44.630> a 00:05:44.680 --> 00:05:44.690 align:start position:0% then Alice over here I can just make a 00:05:44.690 --> 00:05:48.960 align:start position:0% then Alice over here I can just make a receipt<00:05:45.140> that<00:05:46.010> says<00:05:46.340> AI<00:05:47.120> wants<00:05:47.780> to<00:05:47.810> give 00:05:48.960 --> 00:05:48.970 align:start position:0% receipt that says AI wants to give 00:05:48.970 --> 00:05:55.390 align:start position:0% receipt that says AI wants to give points<00:05:49.970> of<00:05:50.590> points<00:05:51.590> the<00:05:51.680> fog<00:05:52.240> and<00:05:53.240> the<00:05:54.250> you<00:05:55.250> can 00:05:55.390 --> 00:05:55.400 align:start position:0% points of points the fog and the you can 00:05:55.400 --> 00:05:57.190 align:start position:0% points of points the fog and the you can even<00:05:55.610> have<00:05:55.880> functionality<00:05:56.690> where<00:05:56.900> a<00:05:56.930> head<00:05:57.110> of 00:05:57.190 --> 00:05:57.200 align:start position:0% even have functionality where a head of 00:05:57.200 --> 00:05:58.930 align:start position:0% even have functionality where a head of the<00:05:57.320> underlying<00:05:57.770> execution<00:05:58.430> environments 00:05:58.930 --> 00:05:58.940 align:start position:0% the underlying execution environments 00:05:58.940 --> 00:05:59.870 align:start position:0% the underlying execution environments can<00:05:59.030> even<00:05:59.300> much 00:05:59.870 --> 00:05:59.880 align:start position:0% can even much 00:05:59.880 --> 00:06:02.150 align:start position:0% can even much from<00:06:00.240> one<00:06:00.390> chart<00:06:00.660> to<00:06:00.780> the<00:06:00.810> other<00:06:01.080> and<00:06:01.380> then<00:06:01.860> Bob 00:06:02.150 --> 00:06:02.160 align:start position:0% from one chart to the other and then Bob 00:06:02.160 --> 00:06:04.870 align:start position:0% from one chart to the other and then Bob who<00:06:02.610> was<00:06:02.640> so<00:06:02.910> there's<00:06:03.450> gonna<00:06:03.600> be<00:06:03.810> over<00:06:04.290> here 00:06:04.870 --> 00:06:04.880 align:start position:0% who was so there's gonna be over here 00:06:04.880 --> 00:06:09.140 align:start position:0% who was so there's gonna be over here the<00:06:05.880> blog<00:06:06.150> will<00:06:06.570> I<00:06:06.960> basically<00:06:07.590> get<00:06:08.340> me<00:06:08.550> able<00:06:09.030> to 00:06:09.140 --> 00:06:09.150 align:start position:0% the blog will I basically get me able to 00:06:09.150 --> 00:06:10.820 align:start position:0% the blog will I basically get me able to include<00:06:09.510> the<00:06:09.720> received<00:06:10.080> and<00:06:10.500> its<00:06:10.620> blog 00:06:10.820 --> 00:06:10.830 align:start position:0% include the received and its blog 00:06:10.830 --> 00:06:13.820 align:start position:0% include the received and its blog actually<00:06:11.310> asking<00:06:11.700> you<00:06:12.330> know<00:06:12.590> because<00:06:13.590> well 00:06:13.820 --> 00:06:13.830 align:start position:0% actually asking you know because well 00:06:13.830 --> 00:06:15.650 align:start position:0% actually asking you know because well actually<00:06:14.010> has<00:06:14.370> Ethan<00:06:14.790> over<00:06:14.910> here<00:06:15.180> ball<00:06:15.450> can 00:06:15.650 --> 00:06:15.660 align:start position:0% actually has Ethan over here ball can 00:06:15.660 --> 00:06:17.240 align:start position:0% actually has Ethan over here ball can immediately<00:06:15.900> use<00:06:16.170> these<00:06:16.530> to<00:06:16.740> do<00:06:16.860> things<00:06:17.070> like 00:06:17.240 --> 00:06:17.250 align:start position:0% immediately use these to do things like 00:06:17.250 --> 00:06:21.620 align:start position:0% immediately use these to do things like BAM<00:06:17.520> transaction<00:06:18.120> fees<00:06:18.830> so<00:06:19.830> I<00:06:20.280> guess<00:06:20.910> like 00:06:21.620 --> 00:06:21.630 align:start position:0% BAM transaction fees so I guess like 00:06:21.630 --> 00:06:23.720 align:start position:0% BAM transaction fees so I guess like when<00:06:21.870> we<00:06:22.020> look<00:06:22.260> at<00:06:22.440> like<00:06:22.680> what<00:06:22.890> really<00:06:23.070> or<00:06:23.310> what 00:06:23.720 --> 00:06:23.730 align:start position:0% when we look at like what really or what 00:06:23.730 --> 00:06:25.640 align:start position:0% when we look at like what really or what really<00:06:23.910> are<00:06:24.060> sort<00:06:24.930> of<00:06:24.960> what<00:06:25.110> execution 00:06:25.640 --> 00:06:25.650 align:start position:0% really are sort of what execution 00:06:25.650 --> 00:06:30.260 align:start position:0% really are sort of what execution environments<00:06:26.250> are<00:06:26.370> forth<00:06:28.310> like<00:06:29.310> execution 00:06:30.260 --> 00:06:30.270 align:start position:0% environments are forth like execution 00:06:30.270 --> 00:06:31.970 align:start position:0% environments are forth like execution environments<00:06:30.960> kind<00:06:31.200> of<00:06:31.290> serve<00:06:31.530> different 00:06:31.970 --> 00:06:31.980 align:start position:0% environments kind of serve different 00:06:31.980 --> 00:06:36.230 align:start position:0% environments kind of serve different roles<00:06:32.610> and<00:06:33.030> eath<00:06:33.690> to<00:06:34.100> so<00:06:35.100> one<00:06:35.430> of<00:06:35.580> them<00:06:35.760> is<00:06:36.000> they 00:06:36.230 --> 00:06:36.240 align:start position:0% roles and eath to so one of them is they 00:06:36.240 --> 00:06:41.050 align:start position:0% roles and eath to so one of them is they dis<00:06:36.450> provide<00:06:36.810> like<00:06:37.110> Java<00:06:37.290> semantics<00:06:38.360> so 00:06:41.050 --> 00:06:41.060 align:start position:0% dis provide like Java semantics so 00:06:41.060 --> 00:06:45.820 align:start position:0% dis provide like Java semantics so basically<00:06:42.060> like<00:06:42.360> is<00:06:42.780> this<00:06:43.140> like<00:06:43.670> balances 00:06:45.820 --> 00:06:45.830 align:start position:0% basically like is this like balances 00:06:45.830 --> 00:06:53.170 align:start position:0% basically like is this like balances Beauty<00:06:46.830> xhose<00:06:48.740> receipts<00:06:50.240> and<00:06:51.290> they<00:06:52.290> also 00:06:53.170 --> 00:06:53.180 align:start position:0% Beauty xhose receipts and they also 00:06:53.180 --> 00:06:56.810 align:start position:0% Beauty xhose receipts and they also described<00:06:54.180> by<00:06:55.100> and<00:06:56.100> they<00:06:56.250> also<00:06:56.400> kind<00:06:56.730> of 00:06:56.810 --> 00:06:56.820 align:start position:0% described by and they also kind of 00:06:56.820 --> 00:07:01.550 align:start position:0% described by and they also kind of prehistoric<00:06:57.120> system<00:06:58.280> and<00:06:59.360> they<00:07:00.360> also<00:07:00.660> have<00:07:01.290> to 00:07:01.550 --> 00:07:01.560 align:start position:0% prehistoric system and they also have to 00:07:01.560 --> 00:07:13.730 align:start position:0% prehistoric system and they also have to handle<00:07:02.100> like<00:07:02.730> basically<00:07:06.380> cross<00:07:07.910> sure<00:07:12.530> we<00:07:13.530> also 00:07:13.730 --> 00:07:13.740 align:start position:0% handle like basically cross sure we also 00:07:13.740 --> 00:07:15.980 align:start position:0% handle like basically cross sure we also have<00:07:14.070> the<00:07:14.220> support<00:07:14.670> things<00:07:15.000> like<00:07:15.120> optimistic 00:07:15.980 --> 00:07:15.990 align:start position:0% have the support things like optimistic 00:07:15.990 --> 00:07:18.160 align:start position:0% have the support things like optimistic state 00:07:18.160 --> 00:07:18.170 align:start position:0% state 00:07:18.170 --> 00:07:21.590 align:start position:0% state might<00:07:19.170> be<00:07:19.350> without<00:07:19.620> the<00:07:19.770> support<00:07:20.420> they<00:07:21.420> would 00:07:21.590 --> 00:07:21.600 align:start position:0% might be without the support they would 00:07:21.600 --> 00:07:23.510 align:start position:0% might be without the support they would have<00:07:21.810> to<00:07:21.960> come<00:07:22.140> up<00:07:22.170> with<00:07:22.320> some<00:07:22.800> like<00:07:23.010> special 00:07:23.510 --> 00:07:23.520 align:start position:0% have to come up with some like special 00:07:23.520 --> 00:07:27.350 align:start position:0% have to come up with some like special purpose<00:07:24.210> like<00:07:24.540> vehement<00:07:25.170> strategy<00:07:25.800> is<00:07:25.950> so<00:07:26.640> be 00:07:27.350 --> 00:07:27.360 align:start position:0% purpose like vehement strategy is so be 00:07:27.360 --> 00:07:29.630 align:start position:0% purpose like vehement strategy is so be keying<00:07:27.630> a<00:07:28.050> kind<00:07:28.320> of<00:07:28.440> full<00:07:29.010> execution 00:07:29.630 --> 00:07:29.640 align:start position:0% keying a kind of full execution 00:07:29.640 --> 00:07:30.650 align:start position:0% keying a kind of full execution environment<00:07:30.120> like<00:07:30.210> have<00:07:30.390> all<00:07:30.510> these 00:07:30.650 --> 00:07:30.660 align:start position:0% environment like have all these 00:07:30.660 --> 00:07:32.540 align:start position:0% environment like have all these components<00:07:31.290> spread<00:07:31.560> and<00:07:31.770> this<00:07:31.980> proposal 00:07:32.540 --> 00:07:32.550 align:start position:0% components spread and this proposal 00:07:32.550 --> 00:07:34.700 align:start position:0% components spread and this proposal basically<00:07:33.000> says<00:07:33.240> you<00:07:34.050> don't<00:07:34.170> need<00:07:34.350> to<00:07:34.470> do<00:07:34.560> this 00:07:34.700 --> 00:07:34.710 align:start position:0% basically says you don't need to do this 00:07:34.710 --> 00:07:35.180 align:start position:0% basically says you don't need to do this anymore 00:07:35.180 --> 00:07:35.190 align:start position:0% anymore 00:07:35.190 --> 00:07:37.120 align:start position:0% anymore in<00:07:35.370> you<00:07:35.520> know<00:07:35.610> you<00:07:35.670> do<00:07:36.060> this<00:07:36.210> anymore<00:07:36.510> because 00:07:37.120 --> 00:07:37.130 align:start position:0% in you know you do this anymore because 00:07:37.130 --> 00:07:40.100 align:start position:0% in you know you do this anymore because the<00:07:38.130> protocol<00:07:38.700> is<00:07:38.880> kind<00:07:39.150> of<00:07:39.300> tightly 00:07:40.100 --> 00:07:40.110 align:start position:0% the protocol is kind of tightly 00:07:40.110 --> 00:07:42.440 align:start position:0% the protocol is kind of tightly connected<00:07:40.380> enough<00:07:40.860> to<00:07:41.040> just<00:07:41.250> be<00:07:42.000> able<00:07:42.120> to<00:07:42.360> do 00:07:42.440 --> 00:07:42.450 align:start position:0% connected enough to just be able to do 00:07:42.450 --> 00:07:47.300 align:start position:0% connected enough to just be able to do this<00:07:42.630> both<00:07:42.840> natively<00:07:43.880> so<00:07:44.990> to<00:07:45.990> kind<00:07:46.350> of<00:07:46.500> poke<00:07:47.100> a 00:07:47.300 --> 00:07:47.310 align:start position:0% this both natively so to kind of poke a 00:07:47.310 --> 00:07:51.020 align:start position:0% this both natively so to kind of poke a bit<00:07:47.460> more<00:07:47.670> deeply<00:07:48.590> one<00:07:49.590> it's<00:07:50.010> like<00:07:50.130> basically 00:07:51.020 --> 00:07:51.030 align:start position:0% bit more deeply one it's like basically 00:07:51.030 --> 00:07:52.880 align:start position:0% bit more deeply one it's like basically the<00:07:51.150> way<00:07:51.450> that<00:07:51.480> fee<00:07:51.810> payment<00:07:52.200> could<00:07:52.440> happen 00:07:52.880 --> 00:07:52.890 align:start position:0% the way that fee payment could happen 00:07:52.890 --> 00:07:58.010 align:start position:0% the way that fee payment could happen yes<00:07:53.490> you<00:07:54.480> have<00:07:55.340> Alice<00:07:56.340> over<00:07:56.550> here<00:07:56.880> and<00:07:57.180> Alice 00:07:58.010 --> 00:07:58.020 align:start position:0% yes you have Alice over here and Alice 00:07:58.020 --> 00:07:59.420 align:start position:0% yes you have Alice over here and Alice is<00:07:58.140> just<00:07:58.350> going<00:07:58.470> to<00:07:58.560> send<00:07:58.800> the<00:07:58.860> transaction 00:07:59.420 --> 00:07:59.430 align:start position:0% is just going to send the transaction 00:07:59.430 --> 00:08:03.520 align:start position:0% is just going to send the transaction and<00:08:00.060> the<00:08:00.260> transaction<00:08:01.260> would<00:08:02.070> have<00:08:02.450> wasa 00:08:03.520 --> 00:08:03.530 align:start position:0% and the transaction would have wasa 00:08:03.530 --> 00:08:06.650 align:start position:0% and the transaction would have wasa execution<00:08:04.530> and<00:08:05.010> the<00:08:05.760> ones<00:08:05.940> of<00:08:06.060> execution 00:08:06.650 --> 00:08:06.660 align:start position:0% execution and the ones of execution 00:08:06.660 --> 00:08:08.420 align:start position:0% execution and the ones of execution would<00:08:06.900> be<00:08:07.050> see<00:08:07.230> what<00:08:07.410> have<00:08:07.620> one<00:08:08.220> of<00:08:08.310> the 00:08:08.420 --> 00:08:08.430 align:start position:0% would be see what have one of the 00:08:08.430 --> 00:08:10.190 align:start position:0% would be see what have one of the outputs<00:08:08.820> that<00:08:08.910> it<00:08:09.090> could<00:08:09.240> do<00:08:09.390> is<00:08:09.990> it<00:08:10.050> could 00:08:10.190 --> 00:08:10.200 align:start position:0% outputs that it could do is it could 00:08:10.200 --> 00:08:12.230 align:start position:0% outputs that it could do is it could give<00:08:10.530> an<00:08:10.650> opcode<00:08:10.830> the<00:08:11.190> B<00:08:11.340> C's<00:08:11.550> we<00:08:11.700> dyslexia 00:08:12.230 --> 00:08:12.240 align:start position:0% give an opcode the B C's we dyslexia 00:08:12.240 --> 00:08:15.800 align:start position:0% give an opcode the B C's we dyslexia payments<00:08:12.690> but<00:08:13.260> in<00:08:13.940> few<00:08:14.940> payments<00:08:15.210> is 00:08:15.800 --> 00:08:15.810 align:start position:0% payments but in few payments is 00:08:15.810 --> 00:08:18.620 align:start position:0% payments but in few payments is basically<00:08:16.290> an<00:08:16.500> opcode<00:08:16.710> that<00:08:17.130> says<00:08:17.370> take<00:08:18.180> ether 00:08:18.620 --> 00:08:18.630 align:start position:0% basically an opcode that says take ether 00:08:18.630 --> 00:08:20.450 align:start position:0% basically an opcode that says take ether out<00:08:18.660> of<00:08:18.930> the<00:08:19.050> current<00:08:19.260> execution<00:08:19.650> environment 00:08:20.450 --> 00:08:20.460 align:start position:0% out of the current execution environment 00:08:20.460 --> 00:08:22.780 align:start position:0% out of the current execution environment and<00:08:20.880> paying<00:08:21.390> ether<00:08:21.780> to<00:08:21.990> the<00:08:22.170> current<00:08:22.440> proposal 00:08:22.780 --> 00:08:22.790 align:start position:0% and paying ether to the current proposal 00:08:22.790 --> 00:08:25.160 align:start position:0% and paying ether to the current proposal so<00:08:23.790> look<00:08:23.940> we<00:08:24.060> have<00:08:24.150> a<00:08:24.180> special<00:08:24.570> upload<00:08:24.900> this<00:08:25.050> is 00:08:25.160 --> 00:08:25.170 align:start position:0% so look we have a special upload this is 00:08:25.170 --> 00:08:27.350 align:start position:0% so look we have a special upload this is basically<00:08:25.470> the<00:08:25.680> PAS<00:08:26.010> proposal<00:08:26.550> right<00:08:26.850> you 00:08:27.350 --> 00:08:27.360 align:start position:0% basically the PAS proposal right you 00:08:27.360 --> 00:08:29.060 align:start position:0% basically the PAS proposal right you have<00:08:27.540> like<00:08:27.810> this<00:08:27.960> kind<00:08:28.200> of<00:08:28.290> top-level<00:08:28.710> wants 00:08:29.060 --> 00:08:29.070 align:start position:0% have like this kind of top-level wants 00:08:29.070 --> 00:08:30.980 align:start position:0% have like this kind of top-level wants and<00:08:29.190> Wako<00:08:29.460> that<00:08:29.670> just<00:08:29.880> said<00:08:30.090> our<00:08:30.330> welcome<00:08:30.750> and 00:08:30.980 --> 00:08:30.990 align:start position:0% and Wako that just said our welcome and 00:08:30.990 --> 00:08:33.440 align:start position:0% and Wako that just said our welcome and the<00:08:31.680> five<00:08:31.890> that<00:08:32.130> just<00:08:32.340> has<00:08:32.520> to<00:08:33.030> keep<00:08:33.270> her<00:08:33.420> out 00:08:33.440 --> 00:08:33.450 align:start position:0% the five that just has to keep her out 00:08:33.450 --> 00:08:35.150 align:start position:0% the five that just has to keep her out of<00:08:33.660> the<00:08:33.750> excuse<00:08:34.140> environment<00:08:34.800> and<00:08:34.920> kind<00:08:35.100> of 00:08:35.150 --> 00:08:35.160 align:start position:0% of the excuse environment and kind of 00:08:35.160 --> 00:08:39.590 align:start position:0% of the excuse environment and kind of give<00:08:35.370> it<00:08:35.460> as<00:08:35.550> a<00:08:35.580> fee<00:08:35.850> and<00:08:37.220> Baja<00:08:38.220> whoever<00:08:39.150> is<00:08:39.390> the 00:08:39.590 --> 00:08:39.600 align:start position:0% give it as a fee and Baja whoever is the 00:08:39.600 --> 00:08:42.050 align:start position:0% give it as a fee and Baja whoever is the one<00:08:39.810> proposer<00:08:40.200> does<00:08:41.010> not<00:08:41.190> need<00:08:41.400> to<00:08:41.580> understand 00:08:42.050 --> 00:08:42.060 align:start position:0% one proposer does not need to understand 00:08:42.060 --> 00:08:44.000 align:start position:0% one proposer does not need to understand execution<00:08:42.660> environments<00:08:43.229> because<00:08:43.530> bog<00:08:43.800> can 00:08:44.000 --> 00:08:44.010 align:start position:0% execution environments because bog can 00:08:44.010 --> 00:08:45.890 align:start position:0% execution environments because bog can just<00:08:44.220> run<00:08:44.430> code<00:08:44.670> and<00:08:44.970> sneeze<00:08:45.240> politics<00:08:45.690> made 00:08:45.890 --> 00:08:45.900 align:start position:0% just run code and sneeze politics made 00:08:45.900 --> 00:08:48.170 align:start position:0% just run code and sneeze politics made the<00:08:46.020> fear<00:08:46.290> and<00:08:46.890> Bob<00:08:47.250> Noah<00:08:47.460> said<00:08:47.700> both<00:08:47.850> that<00:08:48.030> Bob 00:08:48.170 --> 00:08:48.180 align:start position:0% the fear and Bob Noah said both that Bob 00:08:48.180 --> 00:08:52.700 align:start position:0% the fear and Bob Noah said both that Bob will<00:08:48.330> get<00:08:48.450> paid<00:08:49.580> so<00:08:51.110> is<00:08:52.110> there<00:08:52.260> enough<00:08:52.440> off<00:08:52.590> the 00:08:52.700 --> 00:08:52.710 align:start position:0% will get paid so is there enough off the 00:08:52.710 --> 00:08:54.560 align:start position:0% will get paid so is there enough off the proposer<00:08:53.010> no<00:08:53.340> us<00:08:53.550> have<00:08:53.730> to<00:08:53.850> propose<00:08:54.090> that<00:08:54.150> the 00:08:54.560 --> 00:08:54.570 align:start position:0% proposer no us have to propose that the 00:08:54.570 --> 00:08:57.360 align:start position:0% proposer no us have to propose that the proposal 00:08:57.360 --> 00:08:57.370 align:start position:0% 00:08:57.370 --> 00:09:00.150 align:start position:0% now<00:08:57.970> there's<00:08:58.480> kind<00:08:59.200> of<00:08:59.350> like<00:08:59.560> there's<00:08:59.890> stuff 00:09:00.150 --> 00:09:00.160 align:start position:0% now there's kind of like there's stuff 00:09:00.160 --> 00:09:01.500 align:start position:0% now there's kind of like there's stuff that<00:09:00.190> you<00:09:00.370> didn't<00:09:00.730> do<00:09:00.790> that<00:09:00.820> you<00:09:01.090> can<00:09:01.270> do<00:09:01.390> on 00:09:01.500 --> 00:09:01.510 align:start position:0% that you didn't do that you can do on 00:09:01.510 --> 00:09:03.710 align:start position:0% that you didn't do that you can do on top<00:09:01.750> so<00:09:02.020> like<00:09:02.200> for<00:09:02.410> example<00:09:02.440> if<00:09:02.920> you<00:09:03.070> wants<00:09:03.400> to 00:09:03.710 --> 00:09:03.720 align:start position:0% top so like for example if you wants to 00:09:03.720 --> 00:09:06.300 align:start position:0% top so like for example if you wants to allow<00:09:04.720> transactions<00:09:05.380> to<00:09:05.500> be<00:09:05.530> merged<00:09:05.830> to<00:09:06.100> share 00:09:06.300 --> 00:09:06.310 align:start position:0% allow transactions to be merged to share 00:09:06.310 --> 00:09:07.650 align:start position:0% allow transactions to be merged to share morkul<00:09:06.700> groups<00:09:06.940> and<00:09:07.120> all<00:09:07.210> that<00:09:07.450> nice<00:09:07.630> stuff 00:09:07.650 --> 00:09:07.660 align:start position:0% morkul groups and all that nice stuff 00:09:07.660 --> 00:09:10.890 align:start position:0% morkul groups and all that nice stuff you<00:09:08.020> can<00:09:08.200> do<00:09:08.320> this<00:09:08.880> but<00:09:09.880> like<00:09:10.180> that's<00:09:10.690> more 00:09:10.890 --> 00:09:10.900 align:start position:0% you can do this but like that's more 00:09:10.900 --> 00:09:15.300 align:start position:0% you can do this but like that's more detail<00:09:11.490> so<00:09:13.020> question<00:09:14.020> like<00:09:14.530> the<00:09:14.710> big<00:09:14.860> question 00:09:15.300 --> 00:09:15.310 align:start position:0% detail so question like the big question 00:09:15.310 --> 00:09:18.300 align:start position:0% detail so question like the big question here<00:09:15.340> is<00:09:15.550> like<00:09:15.910> what<00:09:16.390> sacrifices<00:09:16.990> are<00:09:17.290> we<00:09:17.440> but 00:09:18.300 --> 00:09:18.310 align:start position:0% here is like what sacrifices are we but 00:09:18.310 --> 00:09:19.710 align:start position:0% here is like what sacrifices are we but do<00:09:18.400> we<00:09:18.490> have<00:09:18.520> to<00:09:18.790> be<00:09:18.880> together<00:09:19.090> that's<00:09:19.420> great 00:09:19.710 --> 00:09:19.720 align:start position:0% do we have to be together that's great 00:09:19.720 --> 00:09:21.660 align:start position:0% do we have to be together that's great so<00:09:20.320> if<00:09:20.680> we<00:09:20.860> do<00:09:21.010> this<00:09:21.130> without<00:09:21.370> changing 00:09:21.660 --> 00:09:21.670 align:start position:0% so if we do this without changing 00:09:21.670 --> 00:09:25.440 align:start position:0% so if we do this without changing parameters<00:09:22.150> then<00:09:23.730> basically<00:09:24.730> the<00:09:25.000> overhead 00:09:25.440 --> 00:09:25.450 align:start position:0% parameters then basically the overhead 00:09:25.450 --> 00:09:27.270 align:start position:0% parameters then basically the overhead is<00:09:25.660> of<00:09:25.840> the<00:09:25.930> b-team<00:09:26.380> is<00:09:26.530> going<00:09:26.710> to<00:09:26.770> increase<00:09:27.010> by 00:09:27.270 --> 00:09:27.280 align:start position:0% is of the b-team is going to increase by 00:09:27.280 --> 00:09:30.510 align:start position:0% is of the b-team is going to increase by a<00:09:27.310> factor<00:09:27.370> of<00:09:27.700> 64<00:09:28.060> and<00:09:28.960> increasing<00:09:29.830> the<00:09:29.980> media 00:09:30.510 --> 00:09:30.520 align:start position:0% a factor of 64 and increasing the media 00:09:30.520 --> 00:09:33.660 align:start position:0% a factor of 64 and increasing the media welfare<00:09:30.910> specifically<00:09:31.510> the<00:09:32.320> at<00:09:33.100> the<00:09:33.280> station 00:09:33.660 --> 00:09:33.670 align:start position:0% welfare specifically the at the station 00:09:33.670 --> 00:09:35.970 align:start position:0% welfare specifically the at the station processing<00:09:34.360> overhead<00:09:34.660> is<00:09:35.350> going<00:09:35.650> to<00:09:35.740> increase 00:09:35.970 --> 00:09:35.980 align:start position:0% processing overhead is going to increase 00:09:35.980 --> 00:09:41.510 align:start position:0% processing overhead is going to increase by<00:09:36.250> a<00:09:36.280> factor<00:09:36.370> of<00:09:36.790> 60<00:09:37.350> now<00:09:38.610> that's<00:09:39.610> kind<00:09:40.270> of<00:09:40.450> and 00:09:41.510 --> 00:09:41.520 align:start position:0% by a factor of 60 now that's kind of and 00:09:41.520 --> 00:09:44.910 align:start position:0% by a factor of 60 now that's kind of and the<00:09:42.520> other<00:09:42.730> problem<00:09:43.450> that<00:09:43.480> we<00:09:43.780> would<00:09:43.930> have<00:09:44.230> is 00:09:44.910 --> 00:09:44.920 align:start position:0% the other problem that we would have is 00:09:44.920 --> 00:09:48.450 align:start position:0% the other problem that we would have is that<00:09:45.070> the<00:09:46.000> number<00:09:46.540> of<00:09:46.780> active<00:09:47.460> validators 00:09:48.450 --> 00:09:48.460 align:start position:0% that the number of active validators 00:09:48.460 --> 00:09:51.570 align:start position:0% that the number of active validators that<00:09:49.420> we<00:09:49.540> wouldn't<00:09:49.810> eat<00:09:49.960> for<00:09:50.260> salat<00:09:50.590> in<00:09:51.340> order 00:09:51.570 --> 00:09:51.580 align:start position:0% that we wouldn't eat for salat in order 00:09:51.580 --> 00:09:52.920 align:start position:0% that we wouldn't eat for salat in order to<00:09:51.760> actually<00:09:51.940> be<00:09:52.180> able<00:09:52.330> to<00:09:52.480> process 00:09:52.920 --> 00:09:52.930 align:start position:0% to actually be able to process 00:09:52.930 --> 00:09:54.480 align:start position:0% to actually be able to process everything<00:09:53.170> in<00:09:53.410> every<00:09:53.650> short<00:09:53.890> light<00:09:54.100> goes<00:09:54.280> up 00:09:54.480 --> 00:09:54.490 align:start position:0% everything in every short light goes up 00:09:54.490 --> 00:09:57.150 align:start position:0% everything in every short light goes up right<00:09:54.760> so<00:09:55.120> basically<00:09:56.110> over<00:09:56.410> European<00:09:56.860> and 00:09:57.150 --> 00:09:57.160 align:start position:0% right so basically over European and 00:09:57.160 --> 00:09:59.090 align:start position:0% right so basically over European and shards<00:09:57.700> then<00:09:57.940> like<00:09:58.210> you<00:09:58.330> would<00:09:58.450> want 00:09:59.090 --> 00:09:59.100 align:start position:0% shards then like you would want 00:09:59.100 --> 00:10:03.860 align:start position:0% shards then like you would want mm<00:09:59.520> 28<00:09:59.970> or<00:10:00.420> 128<00:10:01.320> back<00:10:01.620> then<00:10:02.000> and<00:10:03.000> then<00:10:03.180> if<00:10:03.630> you 00:10:03.860 --> 00:10:03.870 align:start position:0% mm 28 or 128 back then and then if you 00:10:03.870 --> 00:10:07.100 align:start position:0% mm 28 or 128 back then and then if you want<00:10:04.170> like<00:10:04.800> to<00:10:04.920> basically<00:10:05.540> if<00:10:06.540> we're<00:10:06.810> still 00:10:07.100 --> 00:10:07.110 align:start position:0% want like to basically if we're still 00:10:07.110 --> 00:10:09.170 align:start position:0% want like to basically if we're still like<00:10:07.560> if<00:10:07.740> we<00:10:07.890> still<00:10:08.190> have<00:10:08.460> a<00:10:08.490> good<00:10:08.760> luck<00:10:08.910> length 00:10:09.170 --> 00:10:09.180 align:start position:0% like if we still have a good luck length 00:10:09.180 --> 00:10:11.930 align:start position:0% like if we still have a good luck length of<00:10:09.450> 64<00:10:10.080> then<00:10:10.770> we<00:10:11.100> would<00:10:11.250> actually<00:10:11.400> need<00:10:11.790> a 00:10:11.930 --> 00:10:11.940 align:start position:0% of 64 then we would actually need a 00:10:11.940 --> 00:10:13.400 align:start position:0% of 64 then we would actually need a hundred<00:10:12.120> and<00:10:12.330> twenty<00:10:12.600> eight<00:10:12.660> times<00:10:12.930> ten<00:10:13.200> times 00:10:13.400 --> 00:10:13.410 align:start position:0% hundred and twenty eight times ten times 00:10:13.410 --> 00:10:17.390 align:start position:0% hundred and twenty eight times ten times 64<00:10:14.100> and<00:10:14.430> as<00:10:14.520> 1024<00:10:15.090> and<00:10:15.960> so<00:10:16.470> the<00:10:17.070> grew<00:10:17.250> would 00:10:17.390 --> 00:10:17.400 align:start position:0% 64 and as 1024 and so the grew would 00:10:17.400 --> 00:10:19.130 align:start position:0% 64 and as 1024 and so the grew would need<00:10:17.610> there<00:10:17.850> to<00:10:17.880> be<00:10:18.060> like<00:10:18.390> basically<00:10:18.570> more<00:10:19.050> you 00:10:19.130 --> 00:10:19.140 align:start position:0% need there to be like basically more you 00:10:19.140 --> 00:10:21.200 align:start position:0% need there to be like basically more you throw<00:10:19.380> them<00:10:19.500> actually<00:10:19.950> this<00:10:20.220> validated<00:10:20.880> to<00:10:21.090> be 00:10:21.200 --> 00:10:21.210 align:start position:0% throw them actually this validated to be 00:10:21.210 --> 00:10:22.670 align:start position:0% throw them actually this validated to be able<00:10:21.300> to<00:10:21.420> process<00:10:21.690> very<00:10:22.020> anything<00:10:22.380> everything 00:10:22.670 --> 00:10:22.680 align:start position:0% able to process very anything everything 00:10:22.680 --> 00:10:25.130 align:start position:0% able to process very anything everything in<00:10:22.800> a<00:10:22.860> single<00:10:23.010> salade<00:10:23.490> or<00:10:24.210> else<00:10:24.570> we<00:10:24.840> have<00:10:25.020> to 00:10:25.130 --> 00:10:25.140 align:start position:0% in a single salade or else we have to 00:10:25.140 --> 00:10:26.840 align:start position:0% in a single salade or else we have to cut<00:10:25.350> down<00:10:25.380> the<00:10:25.710> ePub<00:10:25.950> length<00:10:26.280> that<00:10:26.460> if<00:10:26.580> we<00:10:26.670> cut 00:10:26.840 --> 00:10:26.850 align:start position:0% cut down the ePub length that if we cut 00:10:26.850 --> 00:10:28.880 align:start position:0% cut down the ePub length that if we cut down<00:10:26.880> the<00:10:27.060> ePub<00:10:27.420> length<00:10:27.720> that<00:10:28.080> we<00:10:28.350> have<00:10:28.500> kind 00:10:28.880 --> 00:10:28.890 align:start position:0% down the ePub length that we have kind 00:10:28.890 --> 00:10:30.230 align:start position:0% down the ePub length that we have kind of<00:10:29.010> compress<00:10:29.400> things<00:10:29.580> have<00:10:29.760> been<00:10:29.850> bored<00:10:30.090> and 00:10:30.230 --> 00:10:30.240 align:start position:0% of compress things have been bored and 00:10:30.240 --> 00:10:32.960 align:start position:0% of compress things have been bored and really<00:10:30.390> blow<00:10:30.660> up<00:10:30.720> the<00:10:30.870> chain<00:10:31.110> so<00:10:32.070> the<00:10:32.580> second 00:10:32.960 --> 00:10:32.970 align:start position:0% really blow up the chain so the second 00:10:32.970 --> 00:10:34.760 align:start position:0% really blow up the chain so the second part<00:10:33.150> of<00:10:33.330> this<00:10:33.510> proposal<00:10:33.960> is<00:10:34.260> that<00:10:34.290> we<00:10:34.560> kind<00:10:34.740> of 00:10:34.760 --> 00:10:34.770 align:start position:0% part of this proposal is that we kind of 00:10:34.770 --> 00:10:36.760 align:start position:0% part of this proposal is that we kind of do<00:10:34.950> something<00:10:35.220> to<00:10:35.520> some<00:10:35.700> parameters<00:10:36.150> weekend 00:10:36.760 --> 00:10:36.770 align:start position:0% do something to some parameters weekend 00:10:36.770 --> 00:10:42.350 align:start position:0% do something to some parameters weekend in<00:10:38.060> perimeter<00:10:39.060> it<00:10:39.390> speaking<00:10:39.690> that<00:10:41.360> I'm 00:10:42.350 --> 00:10:42.360 align:start position:0% in perimeter it speaking that I'm 00:10:42.360 --> 00:10:47.710 align:start position:0% in perimeter it speaking that I'm suggesting<00:10:42.930> is<00:10:44.690> short<00:10:45.690> counts<00:10:46.230> goes<00:10:46.890> from 00:10:47.710 --> 00:10:47.720 align:start position:0% suggesting is short counts goes from 00:10:47.720 --> 00:10:53.270 align:start position:0% suggesting is short counts goes from 1024<00:10:48.720> down<00:10:48.960> to<00:10:49.140> 64<00:10:50.210> shard<00:10:51.210> block<00:10:51.750> size<00:10:52.280> goes 00:10:53.270 --> 00:10:53.280 align:start position:0% 1024 down to 64 shard block size goes 00:10:53.280 --> 00:10:56.780 align:start position:0% 1024 down to 64 shard block size goes down<00:10:53.580> from<00:10:54.120> goes<00:10:54.780> up<00:10:55.050> from<00:10:55.260> 16<00:10:55.830> to<00:10:55.860> target<00:10:56.250> 64 00:10:56.780 --> 00:10:56.790 align:start position:0% down from goes up from 16 to target 64 00:10:56.790 --> 00:10:59.249 align:start position:0% down from goes up from 16 to target 64 max<00:10:57.180> to 00:10:59.249 --> 00:10:59.259 align:start position:0% max to 00:10:59.259 --> 00:11:05.049 align:start position:0% max to 1:28<00:11:00.290> sorry<00:11:00.680> Gibble's<00:11:01.839> biomass<00:11:02.980> and<00:11:03.980> so<00:11:04.309> this 00:11:05.049 --> 00:11:05.059 align:start position:0% 1:28 sorry Gibble's biomass and so this 00:11:05.059 --> 00:11:06.939 align:start position:0% 1:28 sorry Gibble's biomass and so this altogether<00:11:05.449> this<00:11:05.959> is<00:11:06.110> obviously<00:11:06.410> divided<00:11:06.889> by 00:11:06.939 --> 00:11:06.949 align:start position:0% altogether this is obviously divided by 00:11:06.949 --> 00:11:10.360 align:start position:0% altogether this is obviously divided by 16<00:11:07.430> times<00:11:08.209> 8<00:11:08.569> and<00:11:08.809> so<00:11:09.259> we<00:11:09.559> obviously<00:11:09.680> get<00:11:10.069> times 00:11:10.360 --> 00:11:10.370 align:start position:0% 16 times 8 and so we obviously get times 00:11:10.370 --> 00:11:13.540 align:start position:0% 16 times 8 and so we obviously get times 1/2<00:11:10.819> times<00:11:11.120> 1/2<00:11:11.480> charge<00:11:11.930> throughput<00:11:12.410> or<00:11:13.100> total 00:11:13.540 --> 00:11:13.550 align:start position:0% 1/2 times 1/2 charge throughput or total 00:11:13.550 --> 00:11:17.439 align:start position:0% 1/2 times 1/2 charge throughput or total system<00:11:13.910> throughput<00:11:14.230> but<00:11:15.879> I'm<00:11:16.879> arguing<00:11:17.120> that 00:11:17.439 --> 00:11:17.449 align:start position:0% system throughput but I'm arguing that 00:11:17.449 --> 00:11:20.079 align:start position:0% system throughput but I'm arguing that this<00:11:17.689> is<00:11:17.749> fine<00:11:18.139> and<00:11:18.379> the<00:11:18.740> reason<00:11:19.129> actually<00:11:19.759> we 00:11:20.079 --> 00:11:20.089 align:start position:0% this is fine and the reason actually we 00:11:20.089 --> 00:11:22.420 align:start position:0% this is fine and the reason actually we also<00:11:20.240> we're<00:11:20.569> also<00:11:20.600> doubling<00:11:21.199> the<00:11:21.290> what<00:11:21.529> well 00:11:22.420 --> 00:11:22.430 align:start position:0% also we're also doubling the what well 00:11:22.430 --> 00:11:24.100 align:start position:0% also we're also doubling the what well instead<00:11:22.730> of<00:11:22.879> having<00:11:23.029> the<00:11:23.209> smallest<00:11:23.600> one<00:11:23.870> times 00:11:24.100 --> 00:11:24.110 align:start position:0% instead of having the smallest one times 00:11:24.110 --> 00:11:25.600 align:start position:0% instead of having the smallest one times who<00:11:24.259> would<00:11:24.379> have<00:11:24.499> larger<00:11:24.860> more<00:11:25.069> clients<00:11:25.490> so 00:11:25.600 --> 00:11:25.610 align:start position:0% who would have larger more clients so 00:11:25.610 --> 00:11:26.949 align:start position:0% who would have larger more clients so there<00:11:25.759> would<00:11:25.850> be<00:11:25.879> another<00:11:26.120> platter<00:11:26.480> by<00:11:26.629> Tears 00:11:26.949 --> 00:11:26.959 align:start position:0% there would be another platter by Tears 00:11:26.959 --> 00:11:29.889 align:start position:0% there would be another platter by Tears so<00:11:27.230> we<00:11:28.069> would<00:11:28.220> be<00:11:28.399> kind<00:11:28.790> of<00:11:28.910> one<00:11:29.540> quart 00:11:29.889 --> 00:11:29.899 align:start position:0% so we would be kind of one quart 00:11:29.899 --> 00:11:33.519 align:start position:0% so we would be kind of one quart basically<00:11:30.589> cutting<00:11:31.430> down<00:11:31.730> the<00:11:31.970> throughput<00:11:32.529> to 00:11:33.519 --> 00:11:33.529 align:start position:0% basically cutting down the throughput to 00:11:33.529 --> 00:11:35.590 align:start position:0% basically cutting down the throughput to about<00:11:33.829> a<00:11:33.860> quarter<00:11:34.100> of<00:11:34.339> what<00:11:34.490> it<00:11:34.579> was<00:11:34.790> and<00:11:35.449> my 00:11:35.590 --> 00:11:35.600 align:start position:0% about a quarter of what it was and my 00:11:35.600 --> 00:11:37.210 align:start position:0% about a quarter of what it was and my argument<00:11:35.779> is<00:11:36.139> that<00:11:36.290> this<00:11:36.529> is<00:11:36.589> flying<00:11:36.980> because 00:11:37.210 --> 00:11:37.220 align:start position:0% argument is that this is flying because 00:11:37.220 --> 00:11:38.829 align:start position:0% argument is that this is flying because select<00:11:37.639> realistic<00:11:38.149> weather<00:11:38.300> is<00:11:38.449> not<00:11:38.600> going<00:11:38.720> to 00:11:38.829 --> 00:11:38.839 align:start position:0% select realistic weather is not going to 00:11:38.839 --> 00:11:40.269 align:start position:0% select realistic weather is not going to be<00:11:38.930> a<00:11:38.959> thousand<00:11:39.379> X<00:11:39.499> increase<00:11:39.860> in<00:11:40.009> the<00:11:40.100> number 00:11:40.269 --> 00:11:40.279 align:start position:0% be a thousand X increase in the number 00:11:40.279 --> 00:11:42.850 align:start position:0% be a thousand X increase in the number of<00:11:40.309> users<00:11:40.519> anyway<00:11:41.120> and<00:11:41.600> we<00:11:42.170> can<00:11:42.379> just<00:11:42.559> kind<00:11:42.769> of 00:11:42.850 --> 00:11:42.860 align:start position:0% of users anyway and we can just kind of 00:11:42.860 --> 00:11:44.650 align:start position:0% of users anyway and we can just kind of start<00:11:43.249> these<00:11:43.550> numbers<00:11:43.879> below<00:11:44.149> and<00:11:44.420> kind<00:11:44.569> of 00:11:44.650 --> 00:11:44.660 align:start position:0% start these numbers below and kind of 00:11:44.660 --> 00:11:47.460 align:start position:0% start these numbers below and kind of conservatively<00:11:45.230> ratchet<00:11:45.649> them<00:11:45.800> up<00:11:45.920> over<00:11:46.069> time 00:11:47.460 --> 00:11:47.470 align:start position:0% conservatively ratchet them up over time 00:11:47.470 --> 00:11:51.970 align:start position:0% conservatively ratchet them up over time so<00:11:49.089> what<00:11:50.089> this<00:11:50.449> you<00:11:50.930> know<00:11:51.050> there's<00:11:51.379> kind<00:11:51.829> of 00:11:51.970 --> 00:11:51.980 align:start position:0% so what this you know there's kind of 00:11:51.980 --> 00:11:55.230 align:start position:0% so what this you know there's kind of other<00:11:52.420> optimistic<00:11:53.420> of<00:11:53.569> optimizations<00:11:54.439> that 00:11:55.230 --> 00:11:55.240 align:start position:0% other optimistic of optimizations that 00:11:55.240 --> 00:11:58.600 align:start position:0% other optimistic of optimizations that we<00:11:56.379> so<00:11:57.379> I<00:11:57.410> guess<00:11:57.680> so<00:11:57.860> first<00:11:58.100> of<00:11:58.249> all<00:11:58.339> just<00:11:58.579> to 00:11:58.600 --> 00:11:58.610 align:start position:0% we so I guess so first of all just to 00:11:58.610 --> 00:12:01.449 align:start position:0% we so I guess so first of all just to clarify<00:11:58.879> like<00:11:59.149> in<00:11:59.569> this<00:11:59.749> architecture<00:12:00.459> even 00:12:01.449 --> 00:12:01.459 align:start position:0% clarify like in this architecture even 00:12:01.459 --> 00:12:02.829 align:start position:0% clarify like in this architecture even though<00:12:01.639> you<00:12:01.699> have<00:12:01.939> a<00:12:01.970> cross-linked<00:12:02.569> every 00:12:02.829 --> 00:12:02.839 align:start position:0% though you have a cross-linked every 00:12:02.839 --> 00:12:06.460 align:start position:0% though you have a cross-linked every SWAT<00:12:03.459> from<00:12:04.459> the<00:12:04.730> point<00:12:05.059> of<00:12:05.179> view<00:12:05.240> of<00:12:05.480> FFG<00:12:06.079> you 00:12:06.460 --> 00:12:06.470 align:start position:0% SWAT from the point of view of FFG you 00:12:06.470 --> 00:12:09.100 align:start position:0% SWAT from the point of view of FFG you would<00:12:06.589> still<00:12:06.829> have<00:12:06.860> ebooks<00:12:07.279> and<00:12:07.749> fge<00:12:08.749> blocks 00:12:09.100 --> 00:12:09.110 align:start position:0% would still have ebooks and fge blocks 00:12:09.110 --> 00:12:12.040 align:start position:0% would still have ebooks and fge blocks will<00:12:09.410> still<00:12:09.649> have<00:12:09.860> a<00:12:09.889> length<00:12:10.220> of<00:12:10.449> 64<00:12:11.449> swats<00:12:11.839> I 00:12:12.040 --> 00:12:12.050 align:start position:0% will still have a length of 64 swats I 00:12:12.050 --> 00:12:14.019 align:start position:0% will still have a length of 64 swats I mean<00:12:12.170> if<00:12:12.259> we<00:12:12.379> want<00:12:12.649> we<00:12:12.769> can<00:12:12.889> make<00:12:13.040> of<00:12:13.160> 32<00:12:13.610> but 00:12:14.019 --> 00:12:14.029 align:start position:0% mean if we want we can make of 32 but 00:12:14.029 --> 00:12:15.819 align:start position:0% mean if we want we can make of 32 but let's<00:12:14.600> tear<00:12:14.720> it<00:12:14.899> up<00:12:15.019> when<00:12:15.230> you<00:12:15.319> reduce<00:12:15.589> that 00:12:15.819 --> 00:12:15.829 align:start position:0% let's tear it up when you reduce that 00:12:15.829 --> 00:12:18.129 align:start position:0% let's tear it up when you reduce that okay<00:12:16.490> so<00:12:16.550> the<00:12:16.790> treetop<00:12:17.179> who<00:12:17.480> for<00:12:17.629> used<00:12:17.870> Scylla 00:12:18.129 --> 00:12:18.139 align:start position:0% okay so the treetop who for used Scylla 00:12:18.139 --> 00:12:20.889 align:start position:0% okay so the treetop who for used Scylla so<00:12:18.350> kind<00:12:18.620> of<00:12:18.740> overhead<00:12:19.550> analysis<00:12:20.120> so<00:12:20.300> from<00:12:20.689> a 00:12:20.889 --> 00:12:20.899 align:start position:0% so kind of overhead analysis so from a 00:12:20.899 --> 00:12:24.840 align:start position:0% so kind of overhead analysis so from a overhead<00:12:21.740> point<00:12:22.009> of<00:12:22.129> view<00:12:22.309> right<00:12:22.629> there<00:12:23.629> is 00:12:24.840 --> 00:12:24.850 align:start position:0% overhead point of view right there is 00:12:24.850 --> 00:12:29.379 align:start position:0% overhead point of view right there is basically<00:12:25.850> kind<00:12:26.329> of<00:12:26.620> two<00:12:27.670> major<00:12:28.670> there's<00:12:29.179> a 00:12:29.379 --> 00:12:29.389 align:start position:0% basically kind of two major there's a 00:12:29.389 --> 00:12:31.269 align:start position:0% basically kind of two major there's a couple<00:12:29.720> of<00:12:29.809> major<00:12:29.990> components<00:12:30.740> to<00:12:30.800> overhead 00:12:31.269 --> 00:12:31.279 align:start position:0% couple of major components to overhead 00:12:31.279 --> 00:12:38.669 align:start position:0% couple of major components to overhead one<00:12:31.939> is<00:12:32.389> PC<00:12:33.290> pairings<00:12:35.019> the<00:12:36.019> other<00:12:36.290> is<00:12:37.059> you<00:12:38.059> see 00:12:38.669 --> 00:12:38.679 align:start position:0% one is PC pairings the other is you see 00:12:38.679 --> 00:12:44.860 align:start position:0% one is PC pairings the other is you see additions<00:12:39.850> and<00:12:40.850> kind<00:12:41.389> of<00:12:41.509> T<00:12:41.870> reads<00:12:43.059> and<00:12:44.059> a 00:12:44.860 --> 00:12:44.870 align:start position:0% additions and kind of T reads and a 00:12:44.870 --> 00:12:47.580 align:start position:0% additions and kind of T reads and a third<00:12:45.230> is<00:12:45.620> like<00:12:46.160> and 00:12:47.580 --> 00:12:47.590 align:start position:0% third is like and 00:12:47.590 --> 00:12:56.240 align:start position:0% third is like and of<00:12:47.850> EPOC<00:12:48.850> kind<00:12:49.750> of<00:12:49.870> balance<00:12:50.260> updating<00:12:51.810> so<00:12:52.810> I<00:12:53.340> am 00:12:56.240 --> 00:12:56.250 align:start position:0% of EPOC kind of balance updating so I am 00:12:56.250 --> 00:13:01.110 align:start position:0% of EPOC kind of balance updating so I am basically<00:12:57.660> ec<00:12:58.660> pairings<00:12:59.170> are<00:12:59.700> there<00:13:00.700> actually 00:13:01.110 --> 00:13:01.120 align:start position:0% basically ec pairings are there actually 00:13:01.120 --> 00:13:04.230 align:start position:0% basically ec pairings are there actually EC<00:13:01.660> pairings<00:13:02.080> are<00:13:02.260> proportional<00:13:03.100> to<00:13:03.240> the 00:13:04.230 --> 00:13:04.240 align:start position:0% EC pairings are proportional to the 00:13:04.240 --> 00:13:06.360 align:start position:0% EC pairings are proportional to the number<00:13:04.480> of<00:13:04.720> cross<00:13:05.140> links<00:13:05.530> that<00:13:05.650> you<00:13:05.770> have<00:13:06.010> but 00:13:06.360 --> 00:13:06.370 align:start position:0% number of cross links that you have but 00:13:06.370 --> 00:13:09.210 align:start position:0% number of cross links that you have but no<00:13:06.580> lot<00:13:06.730> to<00:13:07.390> the<00:13:07.840> number<00:13:08.110> of<00:13:08.140> total<00:13:08.410> validators 00:13:09.210 --> 00:13:09.220 align:start position:0% no lot to the number of total validators 00:13:09.220 --> 00:13:13.470 align:start position:0% no lot to the number of total validators and<00:13:09.970> so<00:13:11.040> basically<00:13:12.040> EC<00:13:12.640> pairings<00:13:13.060> are<00:13:13.300> the 00:13:13.470 --> 00:13:13.480 align:start position:0% and so basically EC pairings are the 00:13:13.480 --> 00:13:15.480 align:start position:0% and so basically EC pairings are the thing<00:13:13.660> that<00:13:13.900> this<00:13:14.080> proposal<00:13:14.650> alright<00:13:14.950> might 00:13:15.480 --> 00:13:15.490 align:start position:0% thing that this proposal alright might 00:13:15.490 --> 00:13:18.000 align:start position:0% thing that this proposal alright might end<00:13:15.670> up<00:13:15.880> going<00:13:16.060> up<00:13:16.300> by<00:13:16.480> a<00:13:16.510> factor<00:13:16.750> of<00:13:16.960> floor<00:13:17.320> but 00:13:18.000 --> 00:13:18.010 align:start position:0% end up going up by a factor of floor but 00:13:18.010 --> 00:13:20.940 align:start position:0% end up going up by a factor of floor but I<00:13:18.340> have<00:13:19.030> an<00:13:19.360> idea<00:13:20.050> for<00:13:20.170> instead<00:13:20.740> of<00:13:20.830> maybe 00:13:20.940 --> 00:13:20.950 align:start position:0% I have an idea for instead of maybe 00:13:20.950 --> 00:13:22.980 align:start position:0% I have an idea for instead of maybe going<00:13:21.250> up<00:13:21.370> by<00:13:21.580> factor<00:13:21.940> for<00:13:22.270> like<00:13:22.450> maybe<00:13:22.690> only 00:13:22.980 --> 00:13:22.990 align:start position:0% going up by factor for like maybe only 00:13:22.990 --> 00:13:25.920 align:start position:0% going up by factor for like maybe only be<00:13:23.200> to<00:13:23.350> go<00:13:23.440> up<00:13:23.590> by<00:13:23.710> a<00:13:23.740> factor<00:13:23.770> of<00:13:24.100> two<00:13:24.630> the<00:13:25.630> idea 00:13:25.920 --> 00:13:25.930 align:start position:0% be to go up by a factor of two the idea 00:13:25.930 --> 00:13:28.080 align:start position:0% be to go up by a factor of two the idea here<00:13:26.200> is<00:13:26.230> basically<00:13:26.620> that<00:13:26.830> like<00:13:27.010> delayed<00:13:27.910> at 00:13:28.080 --> 00:13:28.090 align:start position:0% here is basically that like delayed at 00:13:28.090 --> 00:13:29.580 align:start position:0% here is basically that like delayed at the<00:13:28.120> station<00:13:28.660> is<00:13:28.750> just<00:13:28.990> going<00:13:29.140> to<00:13:29.230> get<00:13:29.380> merged 00:13:29.580 --> 00:13:29.590 align:start position:0% the station is just going to get merged 00:13:29.590 --> 00:13:32.130 align:start position:0% the station is just going to get merged all<00:13:30.040> get<00:13:30.220> emergency<00:13:30.430> up<00:13:30.880> there<00:13:31.060> to<00:13:31.300> publish 00:13:32.130 --> 00:13:32.140 align:start position:0% all get emergency up there to publish 00:13:32.140 --> 00:13:33.330 align:start position:0% all get emergency up there to publish something<00:13:32.350> else<00:13:32.620> for<00:13:32.800> the<00:13:32.920> wait<00:13:33.040> at<00:13:33.190> the 00:13:33.330 --> 00:13:33.340 align:start position:0% something else for the wait at the 00:13:33.340 --> 00:13:37.700 align:start position:0% something else for the wait at the station<00:13:34.470> and<00:13:35.470> then<00:13:35.770> you<00:13:36.160> see<00:13:36.730> ads<00:13:36.940> business 00:13:37.700 --> 00:13:37.710 align:start position:0% station and then you see ads business 00:13:37.710 --> 00:13:39.720 align:start position:0% station and then you see ads business proportional<00:13:38.710> to<00:13:38.830> the<00:13:38.890> number<00:13:39.010> of<00:13:39.160> Ella<00:13:39.370> this 00:13:39.720 --> 00:13:39.730 align:start position:0% proportional to the number of Ella this 00:13:39.730 --> 00:13:41.790 align:start position:0% proportional to the number of Ella this is<00:13:39.910> like<00:13:40.060> basically<00:13:40.450> validators<00:13:41.080> divided<00:13:41.650> by 00:13:41.790 --> 00:13:41.800 align:start position:0% is like basically validators divided by 00:13:41.800 --> 00:13:44.610 align:start position:0% is like basically validators divided by equal<00:13:42.190> a<00:13:42.220> blank<00:13:42.550> and<00:13:42.790> this<00:13:43.360> is<00:13:43.510> also<00:13:43.720> no<00:13:44.350> health 00:13:44.610 --> 00:13:44.620 align:start position:0% equal a blank and this is also no health 00:13:44.620 --> 00:13:47.460 align:start position:0% equal a blank and this is also no health leaders<00:13:44.860> divided<00:13:45.250> by<00:13:45.340> you<00:13:45.400> mark<00:13:45.640> life<00:13:45.820> so<00:13:46.690> if 00:13:47.460 --> 00:13:47.470 align:start position:0% leaders divided by you mark life so if 00:13:47.470 --> 00:13:50.610 align:start position:0% leaders divided by you mark life so if the<00:13:47.680> employment<00:13:47.950> goes<00:13:48.460> down<00:13:48.670> then<00:13:49.360> a<00:13:49.840> work 00:13:50.610 --> 00:13:50.620 align:start position:0% the employment goes down then a work 00:13:50.620 --> 00:13:52.830 align:start position:0% the employment goes down then a work walks<00:13:50.920> will<00:13:51.220> be<00:13:51.370> up<00:13:51.550> these<00:13:51.760> end<00:13:52.060> every<00:13:52.630> block 00:13:52.830 --> 00:13:52.840 align:start position:0% walks will be up these end every block 00:13:52.840 --> 00:13:54.480 align:start position:0% walks will be up these end every block walks<00:13:53.230> to<00:13:53.410> take<00:13:53.590> a<00:13:53.620> rolling<00:13:53.890> large<00:13:54.130> amount<00:13:54.430> of 00:13:54.480 --> 00:13:54.490 align:start position:0% walks to take a rolling large amount of 00:13:54.490 --> 00:14:00.960 align:start position:0% walks to take a rolling large amount of time<00:13:54.670> the<00:13:54.790> process<00:13:58.470> you<00:13:59.470> know<00:13:59.560> we<00:13:59.830> be<00:14:00.220> what<00:14:00.820> we 00:14:00.960 --> 00:14:00.970 align:start position:0% time the process you know we be what we 00:14:00.970 --> 00:14:03.930 align:start position:0% time the process you know we be what we basically<00:14:01.180> kind<00:14:01.630> of<00:14:01.690> have<00:14:01.900> a<00:14:02.580> have<00:14:03.580> someone 00:14:03.930 --> 00:14:03.940 align:start position:0% basically kind of have a have someone 00:14:03.940 --> 00:14:05.720 align:start position:0% basically kind of have a have someone have<00:14:04.150> a<00:14:04.180> kind<00:14:04.420> of<00:14:04.450> trade<00:14:04.690> out<00:14:04.810> to<00:14:04.990> meet<00:14:05.140> here 00:14:05.720 --> 00:14:05.730 align:start position:0% have a kind of trade out to meet here 00:14:05.730 --> 00:14:10.620 align:start position:0% have a kind of trade out to meet here then<00:14:06.730> you<00:14:06.940> would<00:14:07.090> you<00:14:07.300> agree<00:14:07.720> in<00:14:08.410> that<00:14:09.060> like<00:14:10.060> at 00:14:10.620 --> 00:14:10.630 align:start position:0% then you would you agree in that like at 00:14:10.630 --> 00:14:13.020 align:start position:0% then you would you agree in that like at the<00:14:10.960> status<00:14:11.350> right<00:14:11.740> now<00:14:11.800> and<00:14:12.610> then<00:14:12.850> people 00:14:13.020 --> 00:14:13.030 align:start position:0% the status right now and then people 00:14:13.030 --> 00:14:14.580 align:start position:0% the status right now and then people walkable<00:14:13.450> walks<00:14:13.600> are<00:14:13.840> and<00:14:13.990> of<00:14:14.050> closer<00:14:14.440> to 00:14:14.580 --> 00:14:14.590 align:start position:0% walkable walks are and of closer to 00:14:14.590 --> 00:14:17.820 align:start position:0% walkable walks are and of closer to being<00:14:14.830> like<00:14:15.660> taste<00:14:16.660> considerably<00:14:17.320> longer<00:14:17.650> to 00:14:17.820 --> 00:14:17.830 align:start position:0% being like taste considerably longer to 00:14:17.830 --> 00:14:19.460 align:start position:0% being like taste considerably longer to process<00:14:18.010> that<00:14:18.520> like<00:14:18.850> hundred 00:14:19.460 --> 00:14:19.470 align:start position:0% process that like hundred 00:14:19.470 --> 00:14:22.430 align:start position:0% process that like hundred zatia<00:14:20.220> blocks<00:14:20.610> I<00:14:20.940> think<00:14:21.510> it's<00:14:21.630> actually<00:14:21.840> the 00:14:22.430 --> 00:14:22.440 align:start position:0% zatia blocks I think it's actually the 00:14:22.440 --> 00:14:25.610 align:start position:0% zatia blocks I think it's actually the other<00:14:22.650> way<00:14:22.770> well<00:14:23.510> I<00:14:24.510> think<00:14:24.840> that<00:14:25.170> even<00:14:25.380> have 00:14:25.610 --> 00:14:25.620 align:start position:0% other way well I think that even have 00:14:25.620 --> 00:14:27.770 align:start position:0% other way well I think that even have even<00:14:25.980> then<00:14:26.130> muscle<00:14:26.670> comes<00:14:27.330> from<00:14:27.570> the<00:14:27.660> other 00:14:27.770 --> 00:14:27.780 align:start position:0% even then muscle comes from the other 00:14:27.780 --> 00:14:30.530 align:start position:0% even then muscle comes from the other stations<00:14:28.400> at<00:14:29.400> least<00:14:29.580> in<00:14:29.880> the<00:14:30.150> lighthouse 00:14:30.530 --> 00:14:30.540 align:start position:0% stations at least in the lighthouse 00:14:30.540 --> 00:14:32.510 align:start position:0% stations at least in the lighthouse benchmarks<00:14:31.200> that<00:14:31.350> I've<00:14:31.440> seen<00:14:31.680> the<00:14:32.310> you 00:14:32.510 --> 00:14:32.520 align:start position:0% benchmarks that I've seen the you 00:14:32.520 --> 00:14:34.610 align:start position:0% benchmarks that I've seen the you proportion<00:14:33.360> of<00:14:33.450> that<00:14:33.510> even<00:14:34.200> at<00:14:34.290> like<00:14:34.440> 4 00:14:34.610 --> 00:14:34.620 align:start position:0% proportion of that even at like 4 00:14:34.620 --> 00:14:36.770 align:start position:0% proportion of that even at like 4 million<00:14:34.860> validators<00:14:35.340> is<00:14:35.550> a<00:14:35.850> fraction<00:14:36.360> of<00:14:36.450> the 00:14:36.770 --> 00:14:36.780 align:start position:0% million validators is a fraction of the 00:14:36.780 --> 00:14:38.930 align:start position:0% million validators is a fraction of the actual<00:14:37.110> bottom<00:14:37.680> so<00:14:37.890> that's<00:14:38.010> actually<00:14:38.460> not<00:14:38.610> as 00:14:38.930 --> 00:14:38.940 align:start position:0% actual bottom so that's actually not as 00:14:38.940 --> 00:14:40.790 align:start position:0% actual bottom so that's actually not as big<00:14:39.150> a<00:14:39.180> concern<00:14:39.650> okay 00:14:40.790 --> 00:14:40.800 align:start position:0% big a concern okay 00:14:40.800 --> 00:14:42.650 align:start position:0% big a concern okay I<00:14:40.980> mean<00:14:41.220> if<00:14:41.400> this<00:14:41.520> is<00:14:41.580> true<00:14:41.910> we<00:14:42.060> don't<00:14:42.270> look<00:14:42.480> at 00:14:42.650 --> 00:14:42.660 align:start position:0% I mean if this is true we don't look at 00:14:42.660 --> 00:14:44.900 align:start position:0% I mean if this is true we don't look at what<00:14:42.900> went<00:14:43.140> down<00:14:43.410> from<00:14:43.500> 64<00:14:44.040> to<00:14:44.070> 32<00:14:44.550> at<00:14:44.730> that 00:14:44.900 --> 00:14:44.910 align:start position:0% what went down from 64 to 32 at that 00:14:44.910 --> 00:14:47.560 align:start position:0% what went down from 64 to 32 at that time<00:14:45.180> actually<00:14:45.930> to<00:14:46.170> it<00:14:46.380> for<00:14:46.530> other<00:14:46.620> reasons 00:14:47.560 --> 00:14:47.570 align:start position:0% time actually to it for other reasons 00:14:47.570 --> 00:14:50.600 align:start position:0% time actually to it for other reasons like<00:14:48.570> it<00:14:48.810> cuts<00:14:49.050> it<00:14:49.380> cuts<00:14:49.590> in<00:14:49.740> half<00:14:49.920> the<00:14:50.160> ability 00:14:50.600 --> 00:14:50.610 align:start position:0% like it cuts it cuts in half the ability 00:14:50.610 --> 00:14:52.520 align:start position:0% like it cuts it cuts in half the ability that<00:14:50.820> we<00:14:50.880> wouldn't<00:14:51.180> even<00:14:51.300> for<00:14:51.630> of<00:14:51.870> the<00:14:52.110> study 00:14:52.520 --> 00:14:52.530 align:start position:0% that we wouldn't even for of the study 00:14:52.530 --> 00:14:54.860 align:start position:0% that we wouldn't even for of the study but<00:14:53.010> to<00:14:53.460> actually<00:14:53.580> be<00:14:53.790> able<00:14:54.090> to<00:14:54.270> process<00:14:54.480> I 00:14:54.860 --> 00:14:54.870 align:start position:0% but to actually be able to process I 00:14:54.870 --> 00:14:56.540 align:start position:0% but to actually be able to process I call<00:14:55.020> charts<00:14:55.350> of<00:14:55.440> a<00:14:55.530> single<00:14:55.830> spot<00:14:56.040> another 00:14:56.540 --> 00:14:56.550 align:start position:0% call charts of a single spot another 00:14:56.550 --> 00:15:03.350 align:start position:0% call charts of a single spot another parameter<00:14:56.820> is<00:15:01.010> right<00:15:02.010> and<00:15:02.280> I<00:15:02.370> think<00:15:02.640> in 00:15:03.350 --> 00:15:03.360 align:start position:0% parameter is right and I think in 00:15:03.360 --> 00:15:05.270 align:start position:0% parameter is right and I think in general<00:15:03.630> I<00:15:04.080> don't<00:15:04.140> like<00:15:04.500> I<00:15:04.650> would<00:15:04.890> not<00:15:05.040> support 00:15:05.270 --> 00:15:05.280 align:start position:0% general I don't like I would not support 00:15:05.280 --> 00:15:09.110 align:start position:0% general I don't like I would not support reducing<00:15:05.730> you<00:15:06.030> for<00:15:06.210> a<00:15:06.240> validator<00:15:07.790> like<00:15:08.790> if<00:15:09.030> I 00:15:09.110 --> 00:15:09.120 align:start position:0% reducing you for a validator like if I 00:15:09.120 --> 00:15:10.820 align:start position:0% reducing you for a validator like if I was<00:15:09.300> coming<00:15:09.780> up<00:15:09.930> with<00:15:09.990> a<00:15:10.110> nice<00:15:10.260> firm<00:15:10.470> elevator 00:15:10.820 --> 00:15:10.830 align:start position:0% was coming up with a nice firm elevator 00:15:10.830 --> 00:15:12.500 align:start position:0% was coming up with a nice firm elevator number<00:15:10.950> from<00:15:11.220> scratch<00:15:11.520> I<00:15:11.700> would<00:15:11.730> say<00:15:12.000> 64 00:15:12.500 --> 00:15:12.510 align:start position:0% number from scratch I would say 64 00:15:12.510 --> 00:15:16.760 align:start position:0% number from scratch I would say 64 instead<00:15:12.810> of<00:15:12.900> 32<00:15:13.380> but<00:15:14.450> maybe<00:15:15.450> and<00:15:15.720> so<00:15:16.260> I<00:15:16.290> feel 00:15:16.760 --> 00:15:16.770 align:start position:0% instead of 32 but maybe and so I feel 00:15:16.770 --> 00:15:18.740 align:start position:0% instead of 32 but maybe and so I feel like<00:15:16.800> the<00:15:17.070> mean<00:15:17.250> value<00:15:17.580> of<00:15:17.610> 32<00:15:17.970> is<00:15:18.330> worth<00:15:18.540> more 00:15:18.740 --> 00:15:18.750 align:start position:0% like the mean value of 32 is worth more 00:15:18.750 --> 00:15:21.800 align:start position:0% like the mean value of 32 is worth more than<00:15:19.460> 24<00:15:20.460> right<00:15:20.700> like<00:15:20.910> if<00:15:21.090> we<00:15:21.210> have<00:15:21.390> to 00:15:21.800 --> 00:15:21.810 align:start position:0% than 24 right like if we have to 00:15:21.810 --> 00:15:25.130 align:start position:0% than 24 right like if we have to yeah<00:15:22.800> in<00:15:23.310> the<00:15:23.910> value<00:15:24.180> and<00:15:24.330> the<00:15:24.510> mean<00:15:24.660> value<00:15:24.690> of 00:15:25.130 --> 00:15:25.140 align:start position:0% yeah in the value and the mean value of 00:15:25.140 --> 00:15:27.110 align:start position:0% yeah in the value and the mean value of luckiest<00:15:25.680> the<00:15:25.890> composability<00:15:26.430> is<00:15:26.760> also 00:15:27.110 --> 00:15:27.120 align:start position:0% luckiest the composability is also 00:15:27.120 --> 00:15:31.240 align:start position:0% luckiest the composability is also pretty<00:15:27.330> high<00:15:27.420> so<00:15:28.850> sacrificing 00:15:31.240 --> 00:15:31.250 align:start position:0% pretty high so sacrificing 00:15:31.250 --> 00:15:34.300 align:start position:0% pretty high so sacrificing eight<00:15:31.430> degrees<00:15:31.670> the<00:15:31.819> other<00:15:31.850> seems<00:15:32.269> good<00:15:33.310> yes 00:15:34.300 --> 00:15:34.310 align:start position:0% eight degrees the other seems good yes 00:15:34.310 --> 00:15:38.860 align:start position:0% eight degrees the other seems good yes yes<00:15:35.350> to<00:15:36.350> what<00:15:36.470> extent<00:15:36.860> can<00:15:36.949> I<00:15:37.129> rely<00:15:37.759> on<00:15:38.120> a<00:15:38.209> cross 00:15:38.860 --> 00:15:38.870 align:start position:0% yes to what extent can I rely on a cross 00:15:38.870 --> 00:15:41.949 align:start position:0% yes to what extent can I rely on a cross linked<00:15:39.259> because<00:15:39.470> shots<00:15:40.089> can<00:15:41.089> fall<00:15:41.300> cried<00:15:41.629> so 00:15:41.949 --> 00:15:41.959 align:start position:0% linked because shots can fall cried so 00:15:41.959 --> 00:15:44.079 align:start position:0% linked because shots can fall cried so yes<00:15:42.350> presence<00:15:43.250> of<00:15:43.370> a<00:15:43.399> cross<00:15:43.639> link<00:15:43.879> doesn't 00:15:44.079 --> 00:15:44.089 align:start position:0% yes presence of a cross link doesn't 00:15:44.089 --> 00:15:45.910 align:start position:0% yes presence of a cross link doesn't mean<00:15:44.240> together<00:15:44.569> anything<00:15:44.959> is<00:15:45.170> final<00:15:45.620> at<00:15:45.740> least 00:15:45.910 --> 00:15:45.920 align:start position:0% mean together anything is final at least 00:15:45.920 --> 00:15:51.100 align:start position:0% mean together anything is final at least okay<00:15:47.319> so<00:15:48.610> one<00:15:49.610> thing<00:15:49.639> that<00:15:50.000> this<00:15:50.300> proposal<00:15:50.720> is 00:15:51.100 --> 00:15:51.110 align:start position:0% okay so one thing that this proposal is 00:15:51.110 --> 00:15:53.650 align:start position:0% okay so one thing that this proposal is not<00:15:51.649> like<00:15:51.800> in<00:15:52.069> this<00:15:52.339> one<00:15:52.579> like<00:15:52.819> like<00:15:53.029> one<00:15:53.540> thing 00:15:53.650 --> 00:15:53.660 align:start position:0% not like in this one like like one thing 00:15:53.660 --> 00:15:55.059 align:start position:0% not like in this one like like one thing you<00:15:53.779> might<00:15:53.899> notice<00:15:54.079> here<00:15:54.470> is<00:15:54.620> that<00:15:54.649> shard 00:15:55.059 --> 00:15:55.069 align:start position:0% you might notice here is that shard 00:15:55.069 --> 00:15:56.829 align:start position:0% you might notice here is that shard chains<00:15:55.339> don't<00:15:55.519> exist<00:15:55.910> right<00:15:56.089> now 00:15:56.829 --> 00:15:56.839 align:start position:0% chains don't exist right now 00:15:56.839 --> 00:15:59.110 align:start position:0% chains don't exist right now in<00:15:57.199> the<00:15:57.379> proposal<00:15:57.860> I<00:15:57.980> have<00:15:58.220> char<00:15:58.550> chains<00:15:58.850> do 00:15:59.110 --> 00:15:59.120 align:start position:0% in the proposal I have char chains do 00:15:59.120 --> 00:16:00.759 align:start position:0% in the proposal I have char chains do kind<00:15:59.420> of<00:15:59.480> exist<00:15:59.870> in<00:16:00.019> this<00:16:00.139> sort<00:16:00.350> of<00:16:00.379> limited 00:16:00.759 --> 00:16:00.769 align:start position:0% kind of exist in this sort of limited 00:16:00.769 --> 00:16:03.910 align:start position:0% kind of exist in this sort of limited ephemeral<00:16:01.250> form<00:16:01.779> you<00:16:02.779> know<00:16:02.930> the<00:16:03.350> in<00:16:03.560> shown 00:16:03.910 --> 00:16:03.920 align:start position:0% ephemeral form you know the in shown 00:16:03.920 --> 00:16:06.519 align:start position:0% ephemeral form you know the in shown kind<00:16:04.550> of<00:16:04.639> winders<00:16:05.060> value<00:16:05.480> but<00:16:06.170> okay<00:16:06.470> so 00:16:06.519 --> 00:16:06.529 align:start position:0% kind of winders value but okay so 00:16:06.529 --> 00:16:10.269 align:start position:0% kind of winders value but okay so basically<00:16:06.980> in<00:16:07.189> this<00:16:07.310> model<00:16:07.730> the<00:16:08.360> like<00:16:09.139> if<00:16:09.889> I 00:16:10.269 --> 00:16:10.279 align:start position:0% basically in this model the like if I 00:16:10.279 --> 00:16:12.699 align:start position:0% basically in this model the like if I publish<00:16:10.730> a<00:16:10.910> transaction<00:16:11.629> kind<00:16:12.079> of<00:16:12.199> Sears<00:16:12.470> the 00:16:12.699 --> 00:16:12.709 align:start position:0% publish a transaction kind of Sears the 00:16:12.709 --> 00:16:14.050 align:start position:0% publish a transaction kind of Sears the kind<00:16:13.009> of<00:16:13.040> increasing<00:16:13.639> levels<00:16:13.970> of 00:16:14.050 --> 00:16:14.060 align:start position:0% kind of increasing levels of 00:16:14.060 --> 00:16:16.269 align:start position:0% kind of increasing levels of confirmation<00:16:14.720> I've<00:16:14.839> experienced<00:16:15.439> right<00:16:15.740> so 00:16:16.269 --> 00:16:16.279 align:start position:0% confirmation I've experienced right so 00:16:16.279 --> 00:16:18.610 align:start position:0% confirmation I've experienced right so step<00:16:16.519> one<00:16:16.790> I<00:16:17.000> publish<00:16:17.600> a<00:16:17.629> transaction<00:16:18.350> so 00:16:18.610 --> 00:16:18.620 align:start position:0% step one I publish a transaction so 00:16:18.620 --> 00:16:20.079 align:start position:0% step one I publish a transaction so Alice<00:16:18.920> publishes<00:16:19.339> a<00:16:19.370> transaction<00:16:19.970> is 00:16:20.079 --> 00:16:20.089 align:start position:0% Alice publishes a transaction is 00:16:20.089 --> 00:16:23.710 align:start position:0% Alice publishes a transaction is floating<00:16:20.449> in<00:16:20.540> the<00:16:20.660> air<00:16:20.689> right<00:16:21.529> now<00:16:21.589> Bob<00:16:22.720> knows 00:16:23.710 --> 00:16:23.720 align:start position:0% floating in the air right now Bob knows 00:16:23.720 --> 00:16:25.990 align:start position:0% floating in the air right now Bob knows that<00:16:24.139> unless<00:16:24.410> Alice<00:16:24.920> double<00:16:25.220> Spencer<00:16:25.550> mob<00:16:25.879> is 00:16:25.990 --> 00:16:26.000 align:start position:0% that unless Alice double Spencer mob is 00:16:26.000 --> 00:16:26.889 align:start position:0% that unless Alice double Spencer mob is going<00:16:26.120> to<00:16:26.180> get<00:16:26.329> paid 00:16:26.889 --> 00:16:26.899 align:start position:0% going to get paid 00:16:26.899 --> 00:16:29.530 align:start position:0% going to get paid great<00:16:27.279> like<00:16:28.279> this<00:16:28.490> is<00:16:28.639> like<00:16:28.850> it<00:16:29.029> so<00:16:29.209> this<00:16:29.360> is 00:16:29.530 --> 00:16:29.540 align:start position:0% great like this is like it so this is 00:16:29.540 --> 00:16:31.300 align:start position:0% great like this is like it so this is the<00:16:29.629> same<00:16:29.810> as<00:16:30.050> like<00:16:30.290> Bitcoin<00:16:30.920> ease<00:16:31.069> that<00:16:31.250> you 00:16:31.300 --> 00:16:31.310 align:start position:0% the same as like Bitcoin ease that you 00:16:31.310 --> 00:16:34.119 align:start position:0% the same as like Bitcoin ease that you know<00:16:31.459> like<00:16:31.639> zeroconf<00:16:32.120> or<00:16:32.329> whatever<00:16:32.920> step<00:16:33.920> to 00:16:34.119 --> 00:16:34.129 align:start position:0% know like zeroconf or whatever step to 00:16:34.129 --> 00:16:36.610 align:start position:0% know like zeroconf or whatever step to this<00:16:34.610> transaction<00:16:35.089> gets<00:16:35.480> included<00:16:35.870> into<00:16:36.589> a 00:16:36.610 --> 00:16:36.620 align:start position:0% this transaction gets included into a 00:16:36.620 --> 00:16:40.150 align:start position:0% this transaction gets included into a block<00:16:37.129> into<00:16:37.939> a<00:16:37.970> shard<00:16:38.629> boy<00:16:38.839> proposal<00:16:39.439> now 00:16:40.150 --> 00:16:40.160 align:start position:0% block into a shard boy proposal now 00:16:40.160 --> 00:16:42.519 align:start position:0% block into a shard boy proposal now there<00:16:40.399> is<00:16:40.459> a<00:16:40.490> bit<00:16:40.699> more<00:16:40.730> confirmation<00:16:41.529> steps 00:16:42.519 --> 00:16:42.529 align:start position:0% there is a bit more confirmation steps 00:16:42.529 --> 00:16:45.189 align:start position:0% there is a bit more confirmation steps are<00:16:42.680> being<00:16:42.939> then<00:16:43.939> you<00:16:44.209> have<00:16:44.420> cross<00:16:44.689> link<00:16:44.959> votes 00:16:45.189 --> 00:16:45.199 align:start position:0% are being then you have cross link votes 00:16:45.199 --> 00:16:46.420 align:start position:0% are being then you have cross link votes and<00:16:45.439> crosses<00:16:45.769> and<00:16:45.829> clothes<00:16:46.100> start 00:16:46.420 --> 00:16:46.430 align:start position:0% and crosses and clothes start 00:16:46.430 --> 00:16:47.510 align:start position:0% and crosses and clothes start accumulating<00:16:46.670> on<00:16:47.089> the<00:16:47.240> show 00:16:47.510 --> 00:16:47.520 align:start position:0% accumulating on the show 00:16:47.520 --> 00:16:49.790 align:start position:0% accumulating on the show proposal<00:16:48.270> and<00:16:48.960> then<00:16:49.170> you<00:16:49.290> get<00:16:49.410> a<00:16:49.470> bit<00:16:49.650> more 00:16:49.790 --> 00:16:49.800 align:start position:0% proposal and then you get a bit more 00:16:49.800 --> 00:16:54.200 align:start position:0% proposal and then you get a bit more about<00:16:50.010> prevention<00:16:50.310> step<00:16:51.240> for<00:16:51.680> the<00:16:52.850> short<00:16:53.850> walk 00:16:54.200 --> 00:16:54.210 align:start position:0% about prevention step for the short walk 00:16:54.210 --> 00:16:57.260 align:start position:0% about prevention step for the short walk gets<00:16:54.600> proposed<00:16:55.020> and<00:16:55.800> this<00:16:56.640> short<00:16:56.910> vlog 00:16:57.260 --> 00:16:57.270 align:start position:0% gets proposed and this short vlog 00:16:57.270 --> 00:16:59.690 align:start position:0% gets proposed and this short vlog actually<00:16:58.110> like<00:16:58.260> two-thirds<00:16:58.950> of<00:16:59.190> the<00:16:59.340> votes<00:16:59.520> in 00:16:59.690 --> 00:16:59.700 align:start position:0% actually like two-thirds of the votes in 00:16:59.700 --> 00:17:01.460 align:start position:0% actually like two-thirds of the votes in the<00:16:59.820> char<00:17:00.030> block<00:17:00.360> for<00:17:00.630> this<00:17:00.780> party<00:17:01.080> or 00:17:01.460 --> 00:17:01.470 align:start position:0% the char block for this party or 00:17:01.470 --> 00:17:03.290 align:start position:0% the char block for this party or two-thirds<00:17:01.950> of<00:17:02.160> the<00:17:02.250> voters<00:17:02.490> over<00:17:02.760> here<00:17:03.000> I'm 00:17:03.290 --> 00:17:03.300 align:start position:0% two-thirds of the voters over here I'm 00:17:03.300 --> 00:17:05.480 align:start position:0% two-thirds of the voters over here I'm actually<00:17:03.750> are<00:17:04.140> for<00:17:04.380> this<00:17:04.470> block<00:17:04.740> in<00:17:05.280> which 00:17:05.480 --> 00:17:05.490 align:start position:0% actually are for this block in which 00:17:05.490 --> 00:17:08.120 align:start position:0% actually are for this block in which case<00:17:05.730> now<00:17:06.060> the<00:17:06.690> basically<00:17:07.410> the<00:17:07.620> region<00:17:07.920> chain 00:17:08.120 --> 00:17:08.130 align:start position:0% case now the basically the region chain 00:17:08.130 --> 00:17:10.670 align:start position:0% case now the basically the region chain matter<00:17:08.370> stands<00:17:08.670> behind<00:17:09.030> this<00:17:09.180> block<00:17:09.680> so 00:17:10.670 --> 00:17:10.680 align:start position:0% matter stands behind this block so 00:17:10.680 --> 00:17:14.510 align:start position:0% matter stands behind this block so that's<00:17:10.920> option<00:17:11.100> one<00:17:11.459> option<00:17:11.900> two<00:17:12.900> is<00:17:13.520> maybe 00:17:14.510 --> 00:17:14.520 align:start position:0% that's option one option two is maybe 00:17:14.520 --> 00:17:16.640 align:start position:0% that's option one option two is maybe less<00:17:15.420> than<00:17:15.690> two-thirds<00:17:16.080> of<00:17:16.260> the<00:17:16.380> committee 00:17:16.640 --> 00:17:16.650 align:start position:0% less than two-thirds of the committee 00:17:16.650 --> 00:17:18.740 align:start position:0% less than two-thirds of the committee votes<00:17:16.920> like<00:17:17.160> support<00:17:17.550> this<00:17:17.700> book<00:17:17.940> and<00:17:18.240> then 00:17:18.740 --> 00:17:18.750 align:start position:0% votes like support this book and then 00:17:18.750 --> 00:17:21.199 align:start position:0% votes like support this book and then there's<00:17:18.930> two<00:17:19.080> options<00:17:19.230> option<00:17:19.920> 2a<00:17:20.459> is<00:17:20.970> that 00:17:21.199 --> 00:17:21.209 align:start position:0% there's two options option 2a is that 00:17:21.209 --> 00:17:22.460 align:start position:0% there's two options option 2a is that two-thirds<00:17:21.420> of<00:17:21.780> the<00:17:21.900> votes<00:17:22.050> support 00:17:22.460 --> 00:17:22.470 align:start position:0% two-thirds of the votes support 00:17:22.470 --> 00:17:24.260 align:start position:0% two-thirds of the votes support something<00:17:22.680> else<00:17:22.980> and<00:17:23.550> if<00:17:23.670> two-thirds<00:17:23.940> of<00:17:24.150> the 00:17:24.260 --> 00:17:24.270 align:start position:0% something else and if two-thirds of the 00:17:24.270 --> 00:17:25.579 align:start position:0% something else and if two-thirds of the votes<00:17:24.420> support<00:17:24.720> something<00:17:25.020> else<00:17:25.200> then<00:17:25.470> this 00:17:25.579 --> 00:17:25.589 align:start position:0% votes support something else then this 00:17:25.589 --> 00:17:26.930 align:start position:0% votes support something else then this guy<00:17:25.740> then<00:17:26.010> this<00:17:26.220> guy's<00:17:26.400> gone<00:17:26.610> in<00:17:26.820> this 00:17:26.930 --> 00:17:26.940 align:start position:0% guy then this guy's gone in this 00:17:26.940 --> 00:17:28.310 align:start position:0% guy then this guy's gone in this transaction<00:17:27.270> should<00:17:27.630> just<00:17:27.810> wait<00:17:27.990> until<00:17:28.260> it 00:17:28.310 --> 00:17:28.320 align:start position:0% transaction should just wait until it 00:17:28.320 --> 00:17:31.310 align:start position:0% transaction should just wait until it gets<00:17:28.410> included<00:17:28.860> sometimes<00:17:29.420> option<00:17:30.420> to<00:17:30.600> be<00:17:30.870> is 00:17:31.310 --> 00:17:31.320 align:start position:0% gets included sometimes option to be is 00:17:31.320 --> 00:17:33.980 align:start position:0% gets included sometimes option to be is that<00:17:31.380> maybe<00:17:31.980> there's<00:17:32.400> two<00:17:32.610> blocks<00:17:32.880> and<00:17:33.510> that's 00:17:33.980 --> 00:17:33.990 align:start position:0% that maybe there's two blocks and that's 00:17:33.990 --> 00:17:35.930 align:start position:0% that maybe there's two blocks and that's maybe<00:17:34.440> none<00:17:34.770> of<00:17:34.890> them<00:17:35.010> got<00:17:35.190> two-thirds<00:17:35.730> right 00:17:35.930 --> 00:17:35.940 align:start position:0% maybe none of them got two-thirds right 00:17:35.940 --> 00:17:37.730 align:start position:0% maybe none of them got two-thirds right so<00:17:36.150> maybe<00:17:36.330> like<00:17:36.690> when<00:17:36.930> this<00:17:37.110> one<00:17:37.320> go<00:17:37.440> 40 00:17:37.730 --> 00:17:37.740 align:start position:0% so maybe like when this one go 40 00:17:37.740 --> 00:17:39.980 align:start position:0% so maybe like when this one go 40 percent<00:17:38.160> this<00:17:38.760> one<00:17:38.970> about<00:17:39.150> forty<00:17:39.420> percent<00:17:39.540> and 00:17:39.980 --> 00:17:39.990 align:start position:0% percent this one about forty percent and 00:17:39.990 --> 00:17:43.040 align:start position:0% percent this one about forty percent and the<00:17:40.080> other<00:17:40.200> 20%<00:17:40.590> were<00:17:40.920> just<00:17:41.130> offline<00:17:41.540> if<00:17:42.540> this 00:17:43.040 --> 00:17:43.050 align:start position:0% the other 20% were just offline if this 00:17:43.050 --> 00:17:46.400 align:start position:0% the other 20% were just offline if this happens<00:17:43.860> and<00:17:44.480> these<00:17:45.480> could<00:17:45.750> be<00:17:45.870> like<00:17:46.110> to 00:17:46.400 --> 00:17:46.410 align:start position:0% happens and these could be like to 00:17:46.410 --> 00:17:48.500 align:start position:0% happens and these could be like to compete<00:17:47.040> conflicting<00:17:47.610> vlog<00:17:47.850> so<00:17:48.120> the<00:17:48.210> proposer 00:17:48.500 --> 00:17:48.510 align:start position:0% compete conflicting vlog so the proposer 00:17:48.510 --> 00:17:50.540 align:start position:0% compete conflicting vlog so the proposer gets<00:17:48.810> slashed<00:17:49.080> or<00:17:49.380> this<00:17:49.530> one<00:17:50.100> of<00:17:50.220> them<00:17:50.370> per 00:17:50.540 --> 00:17:50.550 align:start position:0% gets slashed or this one of them per 00:17:50.550 --> 00:17:52.190 align:start position:0% gets slashed or this one of them per deal<00:17:50.730> at<00:17:50.850> the<00:17:50.970> zero<00:17:51.180> block<00:17:51.390> right<00:17:51.780> so<00:17:51.960> if<00:17:52.080> the 00:17:52.190 --> 00:17:52.200 align:start position:0% deal at the zero block right so if the 00:17:52.200 --> 00:17:53.390 align:start position:0% deal at the zero block right so if the product<00:17:52.500> of<00:17:52.560> choice<00:17:52.590> are<00:17:52.890> published<00:17:53.190> a<00:17:53.280> little 00:17:53.390 --> 00:17:53.400 align:start position:0% product of choice are published a little 00:17:53.400 --> 00:17:55.310 align:start position:0% product of choice are published a little bit<00:17:53.580> late<00:17:53.820> then<00:17:54.420> like<00:17:54.840> you<00:17:54.960> might<00:17:55.110> have<00:17:55.140> a 00:17:55.310 --> 00:17:55.320 align:start position:0% bit late then like you might have a 00:17:55.320 --> 00:17:59.900 align:start position:0% bit late then like you might have a 50-50<00:17:55.980> if<00:17:56.850> this<00:17:57.180> happens<00:17:57.690> then<00:17:58.490> what<00:17:59.490> we<00:17:59.670> have 00:17:59.900 --> 00:17:59.910 align:start position:0% 50-50 if this happens then what we have 00:17:59.910 --> 00:18:02.830 align:start position:0% 50-50 if this happens then what we have or<00:18:00.570> the<00:18:00.930> third<00:18:01.440> possibility<00:18:01.950> is<00:18:02.220> out<00:18:02.370> there 00:18:02.830 --> 00:18:02.840 align:start position:0% or the third possibility is out there 00:18:02.840 --> 00:18:05.470 align:start position:0% or the third possibility is out there our<00:18:02.930> 70<00:18:03.350> percents<00:18:03.770> but<00:18:03.920> the<00:18:04.100> well<00:18:04.760> beacon<00:18:05.270> blog 00:18:05.470 --> 00:18:05.480 align:start position:0% our 70 percents but the well beacon blog 00:18:05.480 --> 00:18:07.180 align:start position:0% our 70 percents but the well beacon blog proposers<00:18:05.990> like<00:18:06.230> being<00:18:06.500> a<00:18:06.590> little<00:18:06.830> evil<00:18:07.070> and 00:18:07.180 --> 00:18:07.190 align:start position:0% proposers like being a little evil and 00:18:07.190 --> 00:18:09.700 align:start position:0% proposers like being a little evil and deciding<00:18:07.550> not<00:18:07.700> to<00:18:07.760> include<00:18:08.150> things<00:18:08.560> so<00:18:09.560> if 00:18:09.700 --> 00:18:09.710 align:start position:0% deciding not to include things so if 00:18:09.710 --> 00:18:13.360 align:start position:0% deciding not to include things so if this<00:18:09.860> happens<00:18:10.690> then<00:18:11.690> our<00:18:12.560> channel<00:18:12.950> just<00:18:13.100> draw 00:18:13.360 --> 00:18:13.370 align:start position:0% this happens then our channel just draw 00:18:13.370 --> 00:18:15.400 align:start position:0% this happens then our channel just draw it<00:18:13.430> out<00:18:13.580> let's<00:18:14.330> say<00:18:14.510> you<00:18:14.570> have<00:18:14.810> another<00:18:14.840> beacon 00:18:15.400 --> 00:18:15.410 align:start position:0% it out let's say you have another beacon 00:18:15.410 --> 00:18:17.440 align:start position:0% it out let's say you have another beacon block<00:18:15.650> and<00:18:16.220> include<00:18:16.640> it<00:18:16.880> weird<00:18:17.120> it<00:18:17.240> would 00:18:17.440 --> 00:18:17.450 align:start position:0% block and include it weird it would 00:18:17.450 --> 00:18:19.990 align:start position:0% block and include it weird it would include<00:18:17.780> but<00:18:18.530> this<00:18:19.010> is<00:18:19.220> not<00:18:19.400> getting<00:18:19.640> funded 00:18:19.990 --> 00:18:20.000 align:start position:0% include but this is not getting funded 00:18:20.000 --> 00:18:23.500 align:start position:0% include but this is not getting funded great<00:18:20.660> then<00:18:21.530> what<00:18:22.010> happens<00:18:22.460> is<00:18:22.940> that<00:18:23.240> a 00:18:23.500 --> 00:18:23.510 align:start position:0% great then what happens is that a 00:18:23.510 --> 00:18:26.710 align:start position:0% great then what happens is that a proposal<00:18:24.020> over<00:18:24.530> here<00:18:25.010> but<00:18:26.000> basically<00:18:26.450> it 00:18:26.710 --> 00:18:26.720 align:start position:0% proposal over here but basically it 00:18:26.720 --> 00:18:29.620 align:start position:0% proposal over here but basically it would<00:18:26.840> be<00:18:26.990> pointing<00:18:27.560> to<00:18:27.920> this<00:18:28.550> and<00:18:29.360> it<00:18:29.570> would 00:18:29.620 --> 00:18:29.630 align:start position:0% would be pointing to this and it would 00:18:29.630 --> 00:18:32.230 align:start position:0% would be pointing to this and it would also<00:18:29.810> have<00:18:30.080> another<00:18:30.290> pointer<00:18:30.740> to<00:18:30.890> this<00:18:31.240> right 00:18:32.230 --> 00:18:32.240 align:start position:0% also have another pointer to this right 00:18:32.240 --> 00:18:40.000 align:start position:0% also have another pointer to this right so<00:18:32.870> this<00:18:33.500> is<00:18:33.710> like<00:18:34.540> shards<00:18:35.540> 0<00:18:36.250> slot<00:18:37.480> 1<00:18:38.480> 2<00:18:38.660> 3<00:18:39.010> this 00:18:40.000 --> 00:18:40.010 align:start position:0% so this is like shards 0 slot 1 2 3 this 00:18:40.010 --> 00:18:42.070 align:start position:0% so this is like shards 0 slot 1 2 3 this would<00:18:40.250> be<00:18:40.370> a<00:18:40.400> short<00:18:40.490> 0s<00:18:41.210> to<00:18:41.240> left<00:18:41.540> for<00:18:41.780> a 00:18:42.070 --> 00:18:42.080 align:start position:0% would be a short 0s to left for a 00:18:42.080 --> 00:18:44.680 align:start position:0% would be a short 0s to left for a somewhat<00:18:42.740> poor<00:18:42.920> proposal<00:18:43.550> but<00:18:44.090> basically<00:18:44.570> a 00:18:44.680 --> 00:18:44.690 align:start position:0% somewhat poor proposal but basically a 00:18:44.690 --> 00:18:46.510 align:start position:0% somewhat poor proposal but basically a salon<00:18:44.990> or<00:18:45.170> proposal<00:18:45.710> if<00:18:45.800> it's<00:18:45.980> pointing<00:18:46.370> to<00:18:46.490> a 00:18:46.510 --> 00:18:46.520 align:start position:0% salon or proposal if it's pointing to a 00:18:46.520 --> 00:18:49.570 align:start position:0% salon or proposal if it's pointing to a B<00:18:46.700> pitch<00:18:46.880> in<00:18:47.120> which<00:18:47.900> we<00:18:48.560> are<00:18:48.620> in<00:18:48.950> the<00:18:49.130> previous 00:18:49.570 --> 00:18:49.580 align:start position:0% B pitch in which we are in the previous 00:18:49.580 --> 00:18:51.280 align:start position:0% B pitch in which we are in the previous sensible<00:18:50.210> the<00:18:50.300> previous<00:18:50.630> included<00:18:51.050> as<00:18:51.140> long 00:18:51.280 --> 00:18:51.290 align:start position:0% sensible the previous included as long 00:18:51.290 --> 00:18:53.800 align:start position:0% sensible the previous included as long as<00:18:51.380> less<00:18:51.560> than<00:18:51.590> 3<00:18:52.010> M<00:18:52.160> it<00:18:52.760> has<00:18:53.000> the<00:18:53.240> proposal<00:18:53.690> has 00:18:53.800 --> 00:18:53.810 align:start position:0% as less than 3 M it has the proposal has 00:18:53.810 --> 00:18:55.120 align:start position:0% as less than 3 M it has the proposal has to<00:18:53.930> contain<00:18:54.260> an<00:18:54.380> opinion<00:18:54.770> about<00:18:54.950> what 00:18:55.120 --> 00:18:55.130 align:start position:0% to contain an opinion about what 00:18:55.130 --> 00:18:58.240 align:start position:0% to contain an opinion about what happened<00:18:55.400> in<00:18:55.460> small<00:18:55.670> cream<00:18:55.970> and<00:18:56.720> then<00:18:57.350> sure 00:18:58.240 --> 00:18:58.250 align:start position:0% happened in small cream and then sure 00:18:58.250 --> 00:19:01.120 align:start position:0% happened in small cream and then sure look<00:18:59.120> what's<00:18:59.660> suppose<00:19:00.080> what<00:19:00.620> loss<00:19:00.950> of 00:19:01.120 --> 00:19:01.130 align:start position:0% look what's suppose what loss of 00:19:01.130 --> 00:19:04.570 align:start position:0% look what's suppose what loss of generality<00:19:01.400> this<00:19:02.000> nice<00:19:02.150> legitimate<00:19:02.830> then<00:19:03.830> he 00:19:04.570 --> 00:19:04.580 align:start position:0% generality this nice legitimate then he 00:19:04.580 --> 00:19:10.150 align:start position:0% generality this nice legitimate then he is<00:19:04.790> going<00:19:05.120> to<00:19:05.410> include<00:19:08.410> 1/2<00:19:09.410> of<00:19:09.590> these<00:19:09.860> things 00:19:10.150 --> 00:19:10.160 align:start position:0% is going to include 1/2 of these things 00:19:10.160 --> 00:19:13.330 align:start position:0% is going to include 1/2 of these things and<00:19:10.610> he's<00:19:11.510> gonna<00:19:11.690> include<00:19:12.050> crossly<00:19:12.650> and<00:19:12.890> that 00:19:13.330 --> 00:19:13.340 align:start position:0% and he's gonna include crossly and that 00:19:13.340 --> 00:19:14.860 align:start position:0% and he's gonna include crossly and that cross<00:19:13.640> link<00:19:13.970> is<00:19:14.090> going<00:19:14.240> to<00:19:14.300> get<00:19:14.480> you<00:19:14.630> in<00:19:14.720> the 00:19:14.860 --> 00:19:14.870 align:start position:0% cross link is going to get you in the 00:19:14.870 --> 00:19:16.509 align:start position:0% cross link is going to get you in the indian<00:19:15.200> about<00:19:15.410> this<00:19:15.620> and<00:19:15.980> its<00:19:16.130> making 00:19:16.509 --> 00:19:16.519 align:start position:0% indian about this and its making 00:19:16.519 --> 00:19:20.789 align:start position:0% indian about this and its making about<00:19:17.149> this<00:19:17.330> and<00:19:17.599> so<00:19:17.959> this<00:19:18.080> gets<00:19:18.259> immunity<00:19:18.940> so 00:19:20.789 --> 00:19:20.799 align:start position:0% about this and so this gets immunity so 00:19:20.799 --> 00:19:23.349 align:start position:0% about this and so this gets immunity so there<00:19:21.799> ESP<00:19:22.339> I<00:19:22.369> definitely<00:19:22.969> didn't<00:19:23.179> worship 00:19:23.349 --> 00:19:23.359 align:start position:0% there ESP I definitely didn't worship 00:19:23.359 --> 00:19:28.479 align:start position:0% there ESP I definitely didn't worship functionality<00:19:25.659> now<00:19:26.659> so<00:19:27.529> the<00:19:27.739> only<00:19:27.919> thing<00:19:28.279> that 00:19:28.479 --> 00:19:28.489 align:start position:0% functionality now so the only thing that 00:19:28.489 --> 00:19:31.419 align:start position:0% functionality now so the only thing that you<00:19:28.580> lose<00:19:28.909> here<00:19:29.359> is<00:19:29.869> basically<00:19:30.529> in<00:19:30.889> that<00:19:31.070> over 00:19:31.419 --> 00:19:31.429 align:start position:0% you lose here is basically in that over 00:19:31.429 --> 00:19:33.609 align:start position:0% you lose here is basically in that over here<00:19:31.789> to<00:19:32.209> cross<00:19:32.479> charter<00:19:32.869> can<00:19:33.049> be<00:19:33.139> like<00:19:33.320> cross 00:19:33.609 --> 00:19:33.619 align:start position:0% here to cross charter can be like cross 00:19:33.619 --> 00:19:35.229 align:start position:0% here to cross charter can be like cross right<00:19:33.799> communication<00:19:34.159> gets<00:19:34.580> delayed<00:19:34.849> by<00:19:35.029> one 00:19:35.229 --> 00:19:35.239 align:start position:0% right communication gets delayed by one 00:19:35.239 --> 00:19:38.769 align:start position:0% right communication gets delayed by one slot<00:19:35.479> because<00:19:36.349> this<00:19:37.279> isn't<00:19:37.879> like<00:19:38.179> this<00:19:38.389> is<00:19:38.599> not 00:19:38.769 --> 00:19:38.779 align:start position:0% slot because this isn't like this is not 00:19:38.779 --> 00:19:41.680 align:start position:0% slot because this isn't like this is not aware<00:19:38.989> of<00:19:39.049> this<00:19:39.289> but<00:19:39.879> otherwise<00:19:40.879> like<00:19:41.539> you 00:19:41.680 --> 00:19:41.690 align:start position:0% aware of this but otherwise like you 00:19:41.690 --> 00:19:43.089 align:start position:0% aware of this but otherwise like you have<00:19:41.869> to<00:19:41.989> wait<00:19:42.139> a<00:19:42.169> you<00:19:42.649> have<00:19:42.830> to<00:19:42.950> wait 00:19:43.089 --> 00:19:43.099 align:start position:0% have to wait a you have to wait 00:19:43.099 --> 00:19:45.519 align:start position:0% have to wait a you have to wait encourage<00:19:43.429> in<00:19:43.580> its<00:19:43.820> life<00:19:44.019> and<00:19:45.019> then<00:19:45.200> the<00:19:45.320> final 00:19:45.519 --> 00:19:45.529 align:start position:0% encourage in its life and then the final 00:19:45.529 --> 00:19:47.499 align:start position:0% encourage in its life and then the final level<00:19:45.919> of<00:19:45.950> confirmation<00:19:46.669> is<00:19:46.849> one<00:19:47.059> like<00:19:47.330> this 00:19:47.499 --> 00:19:47.509 align:start position:0% level of confirmation is one like this 00:19:47.509 --> 00:19:49.989 align:start position:0% level of confirmation is one like this tie<00:19:47.659> gets<00:19:47.869> finalized<00:19:48.349> and<00:19:48.649> that<00:19:48.799> lol<00:19:49.639> is<00:19:49.820> says 00:19:49.989 --> 00:19:49.999 align:start position:0% tie gets finalized and that lol is says 00:19:49.999 --> 00:19:53.529 align:start position:0% tie gets finalized and that lol is says such<00:19:50.239> transactions<00:19:50.779> about<00:19:51.019> is<00:19:51.109> finalized<00:19:52.539> so 00:19:53.529 --> 00:19:53.539 align:start position:0% such transactions about is finalized so 00:19:53.539 --> 00:19:55.690 align:start position:0% such transactions about is finalized so the<00:19:53.659> only<00:19:53.899> poor<00:19:54.619> thing<00:19:54.889> that's<00:19:55.219> happening 00:19:55.690 --> 00:19:55.700 align:start position:0% the only poor thing that's happening 00:19:55.700 --> 00:19:58.529 align:start position:0% the only poor thing that's happening with<00:19:55.969> respect<00:19:56.419> to<00:19:56.599> a<00:19:56.629> shark<00:19:57.229> tank 00:19:58.529 --> 00:19:58.539 align:start position:0% with respect to a shark tank 00:19:58.539 --> 00:20:00.700 align:start position:0% with respect to a shark tank actually<00:19:59.539> contain<00:19:59.960> words<00:20:00.230> because<00:20:00.590> these 00:20:00.700 --> 00:20:00.710 align:start position:0% actually contain words because these 00:20:00.710 --> 00:20:02.350 align:start position:0% actually contain words because these sharp<00:20:01.039> block<00:20:01.249> is<00:20:01.460> containing<00:20:01.789> a<00:20:01.940> previous 00:20:02.350 --> 00:20:02.360 align:start position:0% sharp block is containing a previous 00:20:02.360 --> 00:20:05.799 align:start position:0% sharp block is containing a previous reference<00:20:02.539> to<00:20:02.869> do<00:20:03.519> so<00:20:04.519> only<00:20:04.669> only<00:20:05.600> if<00:20:05.720> you 00:20:05.799 --> 00:20:05.809 align:start position:0% reference to do so only only if you 00:20:05.809 --> 00:20:06.940 align:start position:0% reference to do so only only if you reorder<00:20:06.110> that<00:20:06.289> you<00:20:06.379> can<00:20:06.499> change<00:20:06.679> what<00:20:06.919> you 00:20:06.940 --> 00:20:06.950 align:start position:0% reorder that you can change what you 00:20:06.950 --> 00:20:12.850 align:start position:0% reorder that you can change what you actually<00:20:07.460> could<00:20:07.730> you<00:20:09.820> okay<00:20:11.529> and<00:20:12.529> then<00:20:12.649> in<00:20:12.769> this 00:20:12.850 --> 00:20:12.860 align:start position:0% actually could you okay and then in this 00:20:12.860 --> 00:20:15.639 align:start position:0% actually could you okay and then in this case<00:20:13.490> really<00:20:14.419> kind<00:20:14.629> of<00:20:14.659> an<00:20:14.779> American<00:20:15.409> chart 00:20:15.639 --> 00:20:15.649 align:start position:0% case really kind of an American chart 00:20:15.649 --> 00:20:18.279 align:start position:0% case really kind of an American chart change<00:20:15.889> you<00:20:16.009> do<00:20:16.159> have<00:20:16.389> less<00:20:17.389> confirmation<00:20:18.139> but 00:20:18.279 --> 00:20:18.289 align:start position:0% change you do have less confirmation but 00:20:18.289 --> 00:20:19.869 align:start position:0% change you do have less confirmation but it<00:20:18.379> hasn't<00:20:18.529> yet<00:20:18.710> communicated<00:20:19.399> with<00:20:19.490> other 00:20:19.869 --> 00:20:19.879 align:start position:0% it hasn't yet communicated with other 00:20:19.879 --> 00:20:22.989 align:start position:0% it hasn't yet communicated with other charts<00:20:20.509> so<00:20:21.200> you<00:20:21.259> don't<00:20:22.009> have<00:20:22.190> the<00:20:22.369> issue<00:20:22.549> like 00:20:22.989 --> 00:20:22.999 align:start position:0% charts so you don't have the issue like 00:20:22.999 --> 00:20:29.710 align:start position:0% charts so you don't have the issue like shards<00:20:23.840> me<00:20:24.309> right 00:20:29.710 --> 00:20:29.720 align:start position:0% 00:20:29.720 --> 00:20:32.029 align:start position:0% we<00:20:30.720> assumed<00:20:31.049> that<00:20:31.200> one<00:20:31.409> of<00:20:31.559> the<00:20:31.679> shots<00:20:31.919> was 00:20:32.029 --> 00:20:32.039 align:start position:0% we assumed that one of the shots was 00:20:32.039 --> 00:20:34.519 align:start position:0% we assumed that one of the shots was completely<00:20:32.580> oppressor<00:20:33.029> of<00:20:33.320> books<00:20:34.320> and 00:20:34.519 --> 00:20:34.529 align:start position:0% completely oppressor of books and 00:20:34.529 --> 00:20:36.019 align:start position:0% completely oppressor of books and protections<00:20:35.159> that<00:20:35.220> actually<00:20:35.700> better<00:20:35.880> than 00:20:36.019 --> 00:20:36.029 align:start position:0% protections that actually better than 00:20:36.029 --> 00:20:38.510 align:start position:0% protections that actually better than just<00:20:36.330> a<00:20:36.539> transition<00:20:37.010> but<00:20:38.010> since<00:20:38.279> everybody 00:20:38.510 --> 00:20:38.520 align:start position:0% just a transition but since everybody 00:20:38.520 --> 00:20:41.269 align:start position:0% just a transition but since everybody Sebastian<00:20:39.149> any<00:20:40.049> will<00:20:40.380> it<00:20:40.470> be<00:20:40.649> accepted<00:20:40.710> by 00:20:41.269 --> 00:20:41.279 align:start position:0% Sebastian any will it be accepted by 00:20:41.279 --> 00:20:43.100 align:start position:0% Sebastian any will it be accepted by them<00:20:41.490> becomes<00:20:41.940> a<00:20:42.120> no<00:20:42.179> good<00:20:42.450> actually<00:20:42.750> do<00:20:42.870> some 00:20:43.100 --> 00:20:43.110 align:start position:0% them becomes a no good actually do some 00:20:43.110 --> 00:20:45.169 align:start position:0% them becomes a no good actually do some sort<00:20:43.409> of<00:20:43.470> validation<00:20:43.770> on<00:20:44.220> this<00:20:44.399> stage<00:20:44.640> well<00:20:45.000> it 00:20:45.169 --> 00:20:45.179 align:start position:0% sort of validation on this stage well it 00:20:45.179 --> 00:20:46.970 align:start position:0% sort of validation on this stage well it depends<00:20:45.600> what<00:20:45.720> we<00:20:45.750> mean<00:20:46.020> by<00:20:46.080> like<00:20:46.470> cruise<00:20:46.740> day 00:20:46.970 --> 00:20:46.980 align:start position:0% depends what we mean by like cruise day 00:20:46.980 --> 00:20:49.549 align:start position:0% depends what we mean by like cruise day right<00:20:47.370> because<00:20:47.760> so<00:20:48.270> a<00:20:48.659> list<00:20:48.929> who<00:20:49.110> the<00:20:49.230> actors 00:20:49.549 --> 00:20:49.559 align:start position:0% right because so a list who the actors 00:20:49.559 --> 00:20:52.669 align:start position:0% right because so a list who the actors are<00:20:49.740> one<00:20:50.460> accurate<00:20:51.000> sharp<00:20:51.299> reporters<00:20:51.809> in 00:20:52.669 --> 00:20:52.679 align:start position:0% are one accurate sharp reporters in 00:20:52.679 --> 00:20:55.580 align:start position:0% are one accurate sharp reporters in other<00:20:52.950> actor<00:20:53.460> s<00:20:53.700> committees<00:20:54.149> so<00:20:54.960> if<00:20:55.470> the 00:20:55.580 --> 00:20:55.590 align:start position:0% other actor s committees so if the 00:20:55.590 --> 00:20:57.620 align:start position:0% other actor s committees so if the proposer<00:20:55.950> is<00:20:56.159> malicious<00:20:56.490> and<00:20:56.909> prim<00:20:57.149> proposes 00:20:57.620 --> 00:20:57.630 align:start position:0% proposer is malicious and prim proposes 00:20:57.630 --> 00:21:00.049 align:start position:0% proposer is malicious and prim proposes a<00:20:57.720> bad<00:20:57.870> walk<00:20:58.200> then<00:20:58.740> generally<00:20:59.549> the<00:20:59.730> committee 00:21:00.049 --> 00:21:00.059 align:start position:0% a bad walk then generally the committee 00:21:00.059 --> 00:21:02.149 align:start position:0% a bad walk then generally the committee will<00:21:00.270> not<00:21:00.419> accept<00:21:00.779> it<00:21:00.960> another<00:21:01.649> possibility 00:21:02.149 --> 00:21:02.159 align:start position:0% will not accept it another possibility 00:21:02.159 --> 00:21:04.519 align:start position:0% will not accept it another possibility is<00:21:02.429> the<00:21:02.610> proposers<00:21:03.029> malicious<00:21:03.630> the<00:21:04.080> media<00:21:04.440> is 00:21:04.519 --> 00:21:04.529 align:start position:0% is the proposers malicious the media is 00:21:04.529 --> 00:21:06.080 align:start position:0% is the proposers malicious the media is also<00:21:04.710> malicious<00:21:05.340> the<00:21:05.490> community<00:21:05.820> points 00:21:06.080 --> 00:21:06.090 align:start position:0% also malicious the community points 00:21:06.090 --> 00:21:12.409 align:start position:0% also malicious the community points delicious<00:21:06.630> thing<00:21:07.070> and<00:21:10.250> and<00:21:11.250> then<00:21:11.789> this<00:21:12.179> he 00:21:12.409 --> 00:21:12.419 align:start position:0% delicious thing and and then this he 00:21:12.419 --> 00:21:14.029 align:start position:0% delicious thing and and then this he didn't<00:21:12.690> want<00:21:12.870> and<00:21:13.110> if<00:21:13.200> theoretically<00:21:13.649> points 00:21:14.029 --> 00:21:14.039 align:start position:0% didn't want and if theoretically points 00:21:14.039 --> 00:21:17.480 align:start position:0% didn't want and if theoretically points to<00:21:14.159> invalid<00:21:14.610> starchy<00:21:15.000> did<00:21:15.210> it<00:21:15.360> even<00:21:16.110> yeah<00:21:16.799> it's 00:21:17.480 --> 00:21:17.490 align:start position:0% to invalid starchy did it even yeah it's 00:21:17.490 --> 00:21:20.090 align:start position:0% to invalid starchy did it even yeah it's really<00:21:17.640> good<00:21:18.029> right<00:21:18.960> look<00:21:19.080> you<00:21:19.200> know<00:21:19.230> so<00:21:19.500> if 00:21:20.090 --> 00:21:20.100 align:start position:0% really good right look you know so if 00:21:20.100 --> 00:21:21.919 align:start position:0% really good right look you know so if this<00:21:20.399> happens<00:21:20.730> right<00:21:21.149> then<00:21:21.390> first<00:21:21.659> of<00:21:21.840> all 00:21:21.919 --> 00:21:21.929 align:start position:0% this happens right then first of all 00:21:21.929 --> 00:21:23.659 align:start position:0% this happens right then first of all like<00:21:22.049> this<00:21:22.260> is<00:21:22.380> already<00:21:22.679> violating<00:21:23.250> like<00:21:23.490> the 00:21:23.659 --> 00:21:23.669 align:start position:0% like this is already violating like the 00:21:23.669 --> 00:21:28.820 align:start position:0% like this is already violating like the security<00:21:24.510> assumptions<00:21:25.520> so<00:21:26.840> there's<00:21:27.840> like<00:21:28.470> to 00:21:28.820 --> 00:21:28.830 align:start position:0% security assumptions so there's like to 00:21:28.830 --> 00:21:31.430 align:start position:0% security assumptions so there's like to recover<00:21:29.159> from<00:21:29.549> this<00:21:29.970> kind<00:21:30.210> of<00:21:30.390> situation<00:21:31.049> like 00:21:31.430 --> 00:21:31.440 align:start position:0% recover from this kind of situation like 00:21:31.440 --> 00:21:36.980 align:start position:0% recover from this kind of situation like you<00:21:31.649> would<00:21:31.799> be<00:21:31.980> simply<00:21:32.640> need<00:21:33.600> to<00:21:35.659> so<00:21:36.659> I<00:21:36.690> wrote<00:21:36.960> a 00:21:36.980 --> 00:21:36.990 align:start position:0% you would be simply need to so I wrote a 00:21:36.990 --> 00:21:38.600 align:start position:0% you would be simply need to so I wrote a separate<00:21:37.380> proposal<00:21:37.830> about<00:21:37.919> this<00:21:38.190> actually 00:21:38.600 --> 00:21:38.610 align:start position:0% separate proposal about this actually 00:21:38.610 --> 00:21:41.480 align:start position:0% separate proposal about this actually like<00:21:38.730> what<00:21:38.940> but<00:21:39.870> so<00:21:40.770> that's<00:21:40.980> not<00:21:41.070> basically 00:21:41.480 --> 00:21:41.490 align:start position:0% like what but so that's not basically 00:21:41.490 --> 00:21:43.279 align:start position:0% like what but so that's not basically there's<00:21:41.760> two<00:21:41.820> kind<00:21:42.210> of<00:21:42.299> possibilities<00:21:42.929> one<00:21:43.200> of 00:21:43.279 --> 00:21:43.289 align:start position:0% there's two kind of possibilities one of 00:21:43.289 --> 00:21:44.690 align:start position:0% there's two kind of possibilities one of them<00:21:43.470> is<00:21:43.590> that<00:21:43.679> it<00:21:43.799> got<00:21:43.950> this<00:21:44.100> work<00:21:44.370> then 00:21:44.690 --> 00:21:44.700 align:start position:0% them is that it got this work then 00:21:44.700 --> 00:21:46.580 align:start position:0% them is that it got this work then eventually<00:21:45.510> it'll<00:21:45.899> be<00:21:45.960> discovered<00:21:46.559> through 00:21:46.580 --> 00:21:46.590 align:start position:0% eventually it'll be discovered through 00:21:46.590 --> 00:21:48.320 align:start position:0% eventually it'll be discovered through fraud<00:21:47.130> proofs<00:21:47.429> and<00:21:47.640> when<00:21:47.789> it<00:21:47.880> gets<00:21:47.970> discovered 00:21:48.320 --> 00:21:48.330 align:start position:0% fraud proofs and when it gets discovered 00:21:48.330 --> 00:21:49.909 align:start position:0% fraud proofs and when it gets discovered through<00:21:48.570> fraud<00:21:48.809> books<00:21:49.169> then<00:21:49.409> like<00:21:49.620> everything 00:21:49.909 --> 00:21:49.919 align:start position:0% through fraud books then like everything 00:21:49.919 --> 00:21:53.810 align:start position:0% through fraud books then like everything gets<00:21:50.250> her<00:21:50.399> bit<00:21:51.020> and<00:21:52.020> you<00:21:52.649> can't<00:21:52.950> really<00:21:53.309> revert 00:21:53.810 --> 00:21:53.820 align:start position:0% gets her bit and you can't really revert 00:21:53.820 --> 00:21:54.810 align:start position:0% gets her bit and you can't really revert lost<00:21:54.090> everything 00:21:54.810 --> 00:21:54.820 align:start position:0% lost everything 00:21:54.820 --> 00:21:57.220 align:start position:0% lost everything because<00:21:55.820> the<00:21:56.000> reality<00:21:56.480> in<00:21:56.630> practice<00:21:57.080> the 00:21:57.220 --> 00:21:57.230 align:start position:0% because the reality in practice the 00:21:57.230 --> 00:21:58.690 align:start position:0% because the reality in practice the dependency<00:21:57.710> graphs<00:21:57.950> especially<00:21:58.550> between 00:21:58.690 --> 00:21:58.700 align:start position:0% dependency graphs especially between 00:21:58.700 --> 00:22:00.750 align:start position:0% dependency graphs especially between four<00:21:59.360> sharks<00:21:59.630> are<00:21:59.809> going<00:21:59.990> to<00:22:00.050> be<00:22:00.110> super<00:22:00.410> tight 00:22:00.750 --> 00:22:00.760 align:start position:0% four sharks are going to be super tight 00:22:00.760 --> 00:22:04.540 align:start position:0% four sharks are going to be super tight the<00:22:01.760> second<00:22:02.180> proposal<00:22:02.590> that<00:22:03.590> is<00:22:03.920> basically 00:22:04.540 --> 00:22:04.550 align:start position:0% the second proposal that is basically 00:22:04.550 --> 00:22:06.100 align:start position:0% the second proposal that is basically that<00:22:04.970> you<00:22:05.090> have<00:22:05.120> this<00:22:05.480> kind<00:22:05.690> of<00:22:05.870> roll<00:22:06.080> off 00:22:06.100 --> 00:22:06.110 align:start position:0% that you have this kind of roll off 00:22:06.110 --> 00:22:08.890 align:start position:0% that you have this kind of roll off lights<00:22:06.470> iam<00:22:06.860> where<00:22:07.100> you<00:22:07.400> don't<00:22:08.180> like<00:22:08.510> if<00:22:08.690> it's 00:22:08.890 --> 00:22:08.900 align:start position:0% lights iam where you don't like if it's 00:22:08.900 --> 00:22:10.600 align:start position:0% lights iam where you don't like if it's unavailable<00:22:09.410> than<00:22:09.890> you<00:22:09.980> referred<00:22:10.280> but<00:22:10.520> if 00:22:10.600 --> 00:22:10.610 align:start position:0% unavailable than you referred but if 00:22:10.610 --> 00:22:13.020 align:start position:0% unavailable than you referred but if it's<00:22:10.760> invalid<00:22:11.390> that<00:22:11.660> if<00:22:12.110> you<00:22:12.230> don't<00:22:12.470> revert 00:22:13.020 --> 00:22:13.030 align:start position:0% it's invalid that if you don't revert 00:22:13.030 --> 00:22:15.970 align:start position:0% it's invalid that if you don't revert like<00:22:14.030> you<00:22:14.600> revert<00:22:14.990> than<00:22:15.260> each<00:22:15.440> chart<00:22:15.740> state 00:22:15.970 --> 00:22:15.980 align:start position:0% like you revert than each chart state 00:22:15.980 --> 00:22:17.799 align:start position:0% like you revert than each chart state but<00:22:16.220> you<00:22:16.250> did<00:22:16.460> not<00:22:16.580> revert<00:22:16.850> the<00:22:17.000> chain<00:22:17.210> and<00:22:17.690> you 00:22:17.799 --> 00:22:17.809 align:start position:0% but you did not revert the chain and you 00:22:17.809 --> 00:22:19.420 align:start position:0% but you did not revert the chain and you kind<00:22:18.020> of<00:22:18.110> revert<00:22:18.320> the<00:22:18.710> shard<00:22:18.950> state<00:22:19.250> with 00:22:19.420 --> 00:22:19.430 align:start position:0% kind of revert the shard state with 00:22:19.430 --> 00:22:23.830 align:start position:0% kind of revert the shard state with image<00:22:19.670> within<00:22:20.270> the<00:22:20.420> chain<00:22:22.150> the<00:22:23.150> idea<00:22:23.450> for<00:22:23.720> this 00:22:23.830 --> 00:22:23.840 align:start position:0% image within the chain the idea for this 00:22:23.840 --> 00:22:26.170 align:start position:0% image within the chain the idea for this behind<00:22:24.470> this<00:22:24.620> is<00:22:24.830> that<00:22:24.980> this<00:22:25.130> allows<00:22:25.490> us<00:22:25.520> kind 00:22:26.170 --> 00:22:26.180 align:start position:0% behind this is that this allows us kind 00:22:26.180 --> 00:22:27.880 align:start position:0% behind this is that this allows us kind of<00:22:26.300> brought<00:22:26.600> your<00:22:26.809> assumptions<00:22:27.350> to<00:22:27.530> be<00:22:27.650> a<00:22:27.679> kind 00:22:27.880 --> 00:22:27.890 align:start position:0% of brought your assumptions to be a kind 00:22:27.890 --> 00:22:29.470 align:start position:0% of brought your assumptions to be a kind of<00:22:27.950> a<00:22:28.130> subjective<00:22:28.370> at<00:22:28.820> more<00:22:28.970> of<00:22:29.059> the<00:22:29.120> clients 00:22:29.470 --> 00:22:29.480 align:start position:0% of a subjective at more of the clients 00:22:29.480 --> 00:22:31.270 align:start position:0% of a subjective at more of the clients that<00:22:29.630> choice<00:22:29.840> instead<00:22:30.410> of<00:22:30.530> like<00:22:30.770> forcing<00:22:31.190> a 00:22:31.270 --> 00:22:31.280 align:start position:0% that choice instead of like forcing a 00:22:31.280 --> 00:22:34.240 align:start position:0% that choice instead of like forcing a secret<00:22:31.580> assumption<00:22:32.030> on<00:22:32.120> everyone<00:22:32.920> but<00:22:33.920> these 00:22:34.240 --> 00:22:34.250 align:start position:0% secret assumption on everyone but these 00:22:34.250 --> 00:22:35.710 align:start position:0% secret assumption on everyone but these things<00:22:34.429> will<00:22:34.610> only<00:22:34.760> happen<00:22:35.030> in<00:22:35.240> the<00:22:35.360> extreme 00:22:35.710 --> 00:22:35.720 align:start position:0% things will only happen in the extreme 00:22:35.720 --> 00:22:39.010 align:start position:0% things will only happen in the extreme case<00:22:35.990> where<00:22:36.290> a<00:22:36.620> community<00:22:37.160> gets<00:22:37.809> broken<00:22:38.809> by<00:22:38.960> an 00:22:39.010 --> 00:22:39.020 align:start position:0% case where a community gets broken by an 00:22:39.020 --> 00:22:41.680 align:start position:0% case where a community gets broken by an attacker<00:22:39.410> which<00:22:39.830> in<00:22:40.340> general<00:22:40.700> requires<00:22:41.360> more 00:22:41.680 --> 00:22:41.690 align:start position:0% attacker which in general requires more 00:22:41.690 --> 00:22:49.760 align:start position:0% attacker which in general requires more than<00:22:41.750> conscience<00:22:43.179> yes 00:22:49.760 --> 00:22:49.770 align:start position:0% 00:22:49.770 --> 00:22:54.860 align:start position:0% I'll<00:22:50.700> change<00:22:51.770> what<00:22:52.770> will<00:22:52.950> happen<00:22:53.550> it's<00:22:54.420> not 00:22:54.860 --> 00:22:54.870 align:start position:0% I'll change what will happen it's not 00:22:54.870 --> 00:22:57.770 align:start position:0% I'll change what will happen it's not possible<00:22:55.740> for<00:22:55.800> to<00:22:56.250> deflect<00:22:56.790> a<00:22:57.000> charging<00:22:57.510> watch 00:22:57.770 --> 00:22:57.780 align:start position:0% possible for to deflect a charging watch 00:22:57.780 --> 00:23:03.680 align:start position:0% possible for to deflect a charging watch to<00:22:57.960> be<00:22:58.080> included<00:22:58.470> on<00:22:58.530> this<00:22:58.650> a<00:22:58.800> baby<00:22:59.100> chick<00:23:02.690> oh 00:23:03.680 --> 00:23:03.690 align:start position:0% to be included on this a baby chick oh 00:23:03.690 --> 00:23:05.810 align:start position:0% to be included on this a baby chick oh wait<00:23:04.559> my<00:23:04.710> different-looking<00:23:05.130> so<00:23:05.460> what<00:23:05.670> we're 00:23:05.810 --> 00:23:05.820 align:start position:0% wait my different-looking so what we're 00:23:05.820 --> 00:23:07.660 align:start position:0% wait my different-looking so what we're seeing<00:23:06.030> is<00:23:06.330> that<00:23:06.360> there's<00:23:06.750> to<00:23:06.960> be<00:23:07.110> in<00:23:07.290> Chains 00:23:07.660 --> 00:23:07.670 align:start position:0% seeing is that there's to be in Chains 00:23:07.670 --> 00:23:09.980 align:start position:0% seeing is that there's to be in Chains and<00:23:08.670> then<00:23:08.820> there's<00:23:09.030> like<00:23:09.270> the<00:23:09.450> shark<00:23:09.690> chain 00:23:09.980 --> 00:23:09.990 align:start position:0% and then there's like the shark chain 00:23:09.990 --> 00:23:12.140 align:start position:0% and then there's like the shark chain which<00:23:10.290> gets<00:23:10.500> included<00:23:10.770> over<00:23:11.130> here<00:23:11.429> and<00:23:11.970> then 00:23:12.140 --> 00:23:12.150 align:start position:0% which gets included over here and then 00:23:12.150 --> 00:23:14.240 align:start position:0% which gets included over here and then over<00:23:12.300> here<00:23:12.450> let's<00:23:12.929> say<00:23:13.110> this<00:23:13.440> one<00:23:14.070> gets 00:23:14.240 --> 00:23:14.250 align:start position:0% over here let's say this one gets 00:23:14.250 --> 00:23:15.770 align:start position:0% over here let's say this one gets included<00:23:14.429> here<00:23:14.880> and<00:23:15.090> then<00:23:15.210> this<00:23:15.360> is<00:23:15.420> the<00:23:15.600> zero 00:23:15.770 --> 00:23:15.780 align:start position:0% included here and then this is the zero 00:23:15.780 --> 00:23:17.780 align:start position:0% included here and then this is the zero block<00:23:16.080> and<00:23:16.290> he<00:23:16.350> gets<00:23:16.530> it<00:23:16.650> to<00:23:16.770> live<00:23:16.920> here<00:23:17.130> right 00:23:17.780 --> 00:23:17.790 align:start position:0% block and he gets it to live here right 00:23:17.790 --> 00:23:20.150 align:start position:0% block and he gets it to live here right is<00:23:18.510> that<00:23:18.570> what<00:23:18.809> you're<00:23:18.960> saying<00:23:19.200> I<00:23:19.530> mean<00:23:19.920> this 00:23:20.150 --> 00:23:20.160 align:start position:0% is that what you're saying I mean this 00:23:20.160 --> 00:23:24.620 align:start position:0% is that what you're saying I mean this is<00:23:20.340> too<00:23:20.700> busy<00:23:20.940> to<00:23:21.090> shop<00:23:22.370> job<00:23:23.370> changes<00:23:23.910> yeah<00:23:24.210> so 00:23:24.620 --> 00:23:24.630 align:start position:0% is too busy to shop job changes yeah so 00:23:24.630 --> 00:23:29.030 align:start position:0% is too busy to shop job changes yeah so basically<00:23:26.690> okay<00:23:27.690> so<00:23:27.750> in<00:23:28.080> this<00:23:28.230> diagram<00:23:28.590> right 00:23:29.030 --> 00:23:29.040 align:start position:0% basically okay so in this diagram right 00:23:29.040 --> 00:23:30.650 align:start position:0% basically okay so in this diagram right like<00:23:29.250> the<00:23:29.520> the<00:23:29.730> zeroes<00:23:30.059> was<00:23:30.240> a<00:23:30.270> hole<00:23:30.480> between 00:23:30.650 --> 00:23:30.660 align:start position:0% like the the zeroes was a hole between 00:23:30.660 --> 00:23:33.799 align:start position:0% like the the zeroes was a hole between the<00:23:30.840> barbecue<00:23:31.320> chain<00:23:31.530> watch<00:23:31.850> began<00:23:32.850> the<00:23:33.330> the 00:23:33.799 --> 00:23:33.809 align:start position:0% the barbecue chain watch began the the 00:23:33.809 --> 00:23:36.110 align:start position:0% the barbecue chain watch began the the the<00:23:34.380> Pullman's<00:23:34.890> are<00:23:35.010> searching<00:23:35.429> twice<00:23:35.670> right 00:23:36.110 --> 00:23:36.120 align:start position:0% the Pullman's are searching twice right 00:23:36.120 --> 00:23:38.470 align:start position:0% the Pullman's are searching twice right like<00:23:36.990> is<00:23:37.140> this<00:23:37.290> wigger<00:23:37.590> is<00:23:37.710> basically<00:23:38.070> saying 00:23:38.470 --> 00:23:38.480 align:start position:0% like is this wigger is basically saying 00:23:38.480 --> 00:23:41.030 align:start position:0% like is this wigger is basically saying or<00:23:39.480> are<00:23:39.510> you<00:23:39.660> saying<00:23:39.840> some<00:23:40.020> other<00:23:40.710> fashion 00:23:41.030 --> 00:23:41.040 align:start position:0% or are you saying some other fashion 00:23:41.040 --> 00:23:41.810 align:start position:0% or are you saying some other fashion pointers 00:23:41.810 --> 00:23:41.820 align:start position:0% pointers 00:23:41.820 --> 00:23:44.770 align:start position:0% pointers Oh<00:23:42.110> like<00:23:43.110> these<00:23:43.320> are<00:23:43.470> the<00:23:43.500> hash<00:23:43.740> pointers<00:23:44.190> I 00:23:44.770 --> 00:23:44.780 align:start position:0% Oh like these are the hash pointers I 00:23:44.780 --> 00:23:47.990 align:start position:0% Oh like these are the hash pointers I think<00:23:45.780> yeah<00:23:46.440> so<00:23:46.470> that<00:23:46.800> pork<00:23:47.040> at<00:23:47.160> the<00:23:47.280> end<00:23:47.400> you 00:23:47.990 --> 00:23:48.000 align:start position:0% think yeah so that pork at the end you 00:23:48.000 --> 00:23:50.270 align:start position:0% think yeah so that pork at the end you the<00:23:48.270> the<00:23:48.690> dot<00:23:48.870> at<00:23:49.110> the<00:23:49.200> top<00:23:49.410> is<00:23:49.590> one<00:23:49.800> shark<00:23:50.070> lock 00:23:50.270 --> 00:23:50.280 align:start position:0% the the dot at the top is one shark lock 00:23:50.280 --> 00:23:52.040 align:start position:0% the the dot at the top is one shark lock that<00:23:50.460> Obama's<00:23:51.120> different<00:23:51.420> rope<00:23:51.570> yeah<00:23:51.720> they've 00:23:52.040 --> 00:23:52.050 align:start position:0% that Obama's different rope yeah they've 00:23:52.050 --> 00:23:53.060 align:start position:0% that Obama's different rope yeah they've entered<00:23:52.230> into 00:23:53.060 --> 00:23:53.070 align:start position:0% entered into 00:23:53.070 --> 00:23:56.210 align:start position:0% entered into or<00:23:53.419> yeah<00:23:54.419> this<00:23:54.600> is<00:23:54.720> fighting<00:23:55.110> in<00:23:55.289> inflicting 00:23:56.210 --> 00:23:56.220 align:start position:0% or yeah this is fighting in inflicting 00:23:56.220 --> 00:23:57.769 align:start position:0% or yeah this is fighting in inflicting but<00:23:56.370> what's<00:23:56.730> the<00:23:56.850> point<00:23:56.970> to<00:23:57.179> get<00:23:57.269> my<00:23:57.419> picture 00:23:57.769 --> 00:23:57.779 align:start position:0% but what's the point to get my picture 00:23:57.779 --> 00:24:00.769 align:start position:0% but what's the point to get my picture James<00:23:58.370> it's<00:23:59.370> a<00:23:59.460> matter<00:23:59.669> of<00:23:59.759> so<00:24:00.269> eventually<00:24:00.539> the 00:24:00.769 --> 00:24:00.779 align:start position:0% James it's a matter of so eventually the 00:24:00.779 --> 00:24:03.289 align:start position:0% James it's a matter of so eventually the task<00:24:01.320> that<00:24:01.500> most<00:24:01.799> the<00:24:01.980> majority<00:24:02.100> to<00:24:02.490> go<00:24:03.059> goals 00:24:03.289 --> 00:24:03.299 align:start position:0% task that most the majority to go goals 00:24:03.299 --> 00:24:06.080 align:start position:0% task that most the majority to go goals become<00:24:04.230> whoever<00:24:04.799> the<00:24:05.100> Viva<00:24:05.399> which<00:24:05.669> ever<00:24:05.880> beat 00:24:06.080 --> 00:24:06.090 align:start position:0% become whoever the Viva which ever beat 00:24:06.090 --> 00:24:08.080 align:start position:0% become whoever the Viva which ever beat me<00:24:06.120> Shane<00:24:06.389> wins<00:24:06.630> this<00:24:06.870> fight<00:24:07.080> so<00:24:07.529> when<00:24:07.710> you're 00:24:08.080 --> 00:24:08.090 align:start position:0% me Shane wins this fight so when you're 00:24:08.090 --> 00:24:10.009 align:start position:0% me Shane wins this fight so when you're when<00:24:09.090> you're<00:24:09.120> in<00:24:09.269> tested<00:24:09.659> with<00:24:09.750> a<00:24:09.809> sharp 00:24:10.009 --> 00:24:10.019 align:start position:0% when you're in tested with a sharp 00:24:10.019 --> 00:24:11.389 align:start position:0% when you're in tested with a sharp lecture<00:24:10.320> also<00:24:10.620> testing<00:24:10.950> to<00:24:11.039> the<00:24:11.070> head<00:24:11.279> of<00:24:11.309> the 00:24:11.389 --> 00:24:11.399 align:start position:0% lecture also testing to the head of the 00:24:11.399 --> 00:24:15.519 align:start position:0% lecture also testing to the head of the pain<00:24:11.850> so<00:24:11.880> you're<00:24:12.269> giving<00:24:12.539> the<00:24:12.659> weight<00:24:12.929> to<00:24:13.139> the 00:24:15.519 --> 00:24:15.529 align:start position:0% 00:24:15.529 --> 00:24:18.019 align:start position:0% result<00:24:16.529> by<00:24:16.679> other<00:24:16.889> for<00:24:17.070> choice<00:24:17.279> by<00:24:17.519> just<00:24:17.789> five 00:24:18.019 --> 00:24:18.029 align:start position:0% result by other for choice by just five 00:24:18.029 --> 00:24:25.070 align:start position:0% result by other for choice by just five bucks<00:24:19.669> so<00:24:20.669> much<00:24:22.820> because<00:24:23.820> we<00:24:24.450> have<00:24:24.570> some<00:24:24.779> sort 00:24:25.070 --> 00:24:25.080 align:start position:0% bucks so much because we have some sort 00:24:25.080 --> 00:24:27.169 align:start position:0% bucks so much because we have some sort of<00:24:25.139> consensus<00:24:25.740> which<00:24:26.009> music<00:24:26.429> company<00:24:26.820> offers 00:24:27.169 --> 00:24:27.179 align:start position:0% of consensus which music company offers 00:24:27.179 --> 00:24:34.030 align:start position:0% of consensus which music company offers many<00:24:27.840> new<00:24:27.929> chambers<00:24:28.549> sensors<00:24:29.549> cavities 00:24:34.030 --> 00:24:34.040 align:start position:0% 00:24:34.040 --> 00:24:38.249 align:start position:0% a<00:24:34.070> coordinated<00:24:34.670> system<00:24:35.170> so<00:24:36.170> I'm<00:24:36.320> also 00:24:38.249 --> 00:24:38.259 align:start position:0% a coordinated system so I'm also 00:24:38.259 --> 00:24:41.400 align:start position:0% a coordinated system so I'm also it<00:24:39.259> doesn't<00:24:39.559> mean<00:24:39.649> to 00:24:41.400 --> 00:24:41.410 align:start position:0% it doesn't mean to 00:24:41.410 --> 00:24:52.630 align:start position:0% it doesn't mean to of<00:24:41.470> such<00:24:42.130> an<00:24:42.340> approach<00:24:42.490> or<00:24:43.390> become<00:24:43.690> Jacob 00:24:52.630 --> 00:24:52.640 align:start position:0% 00:24:52.640 --> 00:24:56.240 align:start position:0% question<00:24:53.640> so<00:24:54.150> so<00:24:54.570> I<00:24:54.780> think<00:24:54.900> in<00:24:55.290> this<00:24:55.620> context 00:24:56.240 --> 00:24:56.250 align:start position:0% question so so I think in this context 00:24:56.250 --> 00:24:58.570 align:start position:0% question so so I think in this context that's<00:24:56.970> that's<00:24:57.750> be<00:24:57.900> able<00:24:58.110> to<00:24:58.200> fly<00:24:58.380> the 00:24:58.570 --> 00:24:58.580 align:start position:0% that's that's be able to fly the 00:24:58.580 --> 00:25:02.860 align:start position:0% that's that's be able to fly the peaceable<00:24:59.580> kingdom<00:24:59.640> chain<00:25:00.270> run<00:25:00.600> some<00:25:01.500> pls 00:25:02.860 --> 00:25:02.870 align:start position:0% peaceable kingdom chain run some pls 00:25:02.870 --> 00:25:05.270 align:start position:0% peaceable kingdom chain run some pls give<00:25:03.870> any<00:25:04.050> weight<00:25:04.260> of<00:25:04.380> the<00:25:04.470> initiated<00:25:04.950> members 00:25:05.270 --> 00:25:05.280 align:start position:0% give any weight of the initiated members 00:25:05.280 --> 00:25:10.250 align:start position:0% give any weight of the initiated members or<00:25:05.550> if<00:25:05.700> you<00:25:05.790> really<00:25:05.940> wanted<00:25:06.270> to 00:25:10.250 --> 00:25:10.260 align:start position:0% 00:25:10.260 --> 00:25:12.350 align:start position:0% someone<00:25:11.010> asked<00:25:11.160> a<00:25:11.250> question<00:25:11.280> about<00:25:11.700> the 00:25:12.350 --> 00:25:12.360 align:start position:0% someone asked a question about the 00:25:12.360 --> 00:25:16.700 align:start position:0% someone asked a question about the previous<00:25:13.430> proposal<00:25:14.430> looking<00:25:15.030> at<00:25:15.120> the<00:25:15.710> yes 00:25:16.700 --> 00:25:16.710 align:start position:0% previous proposal looking at the yes 00:25:16.710 --> 00:25:18.700 align:start position:0% previous proposal looking at the yes okay<00:25:17.130> you<00:25:17.190> shared<00:25:17.490> before<00:25:17.910> they<00:25:18.060> interrupt 00:25:18.700 --> 00:25:18.710 align:start position:0% okay you shared before they interrupt 00:25:18.710 --> 00:25:21.500 align:start position:0% okay you shared before they interrupt longtime<00:25:19.710> leader<00:25:20.010> on<00:25:20.130> focus<00:25:20.550> and<00:25:21.330> it<00:25:21.420> was 00:25:21.500 --> 00:25:21.510 align:start position:0% longtime leader on focus and it was 00:25:21.510 --> 00:25:27.700 align:start position:0% longtime leader on focus and it was probably<00:25:21.750> an<00:25:21.840> alternative<00:25:22.520> case<00:25:23.520> -<00:25:24.270> yes<00:25:26.180> with 00:25:27.700 --> 00:25:27.710 align:start position:0% probably an alternative case - yes with 00:25:27.710 --> 00:25:30.290 align:start position:0% probably an alternative case - yes with removing<00:25:28.710> persistent<00:25:29.580> state<00:25:29.790> groups<00:25:30.000> from 00:25:30.290 --> 00:25:30.300 align:start position:0% removing persistent state groups from 00:25:30.300 --> 00:25:35.720 align:start position:0% removing persistent state groups from shards<00:25:31.260> and<00:25:32.420> executing<00:25:33.420> code<00:25:33.660> on<00:25:34.610> while<00:25:35.610> the 00:25:35.720 --> 00:25:35.730 align:start position:0% shards and executing code on while the 00:25:35.730 --> 00:25:41.060 align:start position:0% shards and executing code on while the court<00:25:35.940> in<00:25:36.570> beacon<00:25:36.900> box<00:25:37.640> I<00:25:39.200> think<00:25:40.200> we<00:25:40.560> almost 00:25:41.060 --> 00:25:41.070 align:start position:0% court in beacon box I think we almost 00:25:41.070 --> 00:25:44.060 align:start position:0% court in beacon box I think we almost liked<00:25:41.460> that<00:25:41.970> proposal<00:25:42.690> because<00:25:43.020> we've<00:25:43.680> got<00:25:43.890> to 00:25:44.060 --> 00:25:44.070 align:start position:0% liked that proposal because we've got to 00:25:44.070 --> 00:25:48.380 align:start position:0% liked that proposal because we've got to offer<00:25:45.440> start<00:25:46.440> transparency<00:25:47.220> great<00:25:47.790> innocence 00:25:48.380 --> 00:25:48.390 align:start position:0% offer start transparency great innocence 00:25:48.390 --> 00:25:52.610 align:start position:0% offer start transparency great innocence soon<00:25:48.990> and<00:25:49.920> then<00:25:50.130> put<00:25:50.370> then<00:25:50.580> in<00:25:50.610> this<00:25:51.620> radical 00:25:52.610 --> 00:25:52.620 align:start position:0% soon and then put then in this radical 00:25:52.620 --> 00:25:56.900 align:start position:0% soon and then put then in this radical new<00:25:52.650> new<00:25:53.100> proposal<00:25:54.710> is<00:25:55.710> it<00:25:55.980> we're<00:25:56.520> returning 00:25:56.900 --> 00:25:56.910 align:start position:0% new new proposal is it we're returning 00:25:56.910 --> 00:25:59.510 align:start position:0% new new proposal is it we're returning back<00:25:57.210> to<00:25:57.560> versus<00:25:58.560> insurance<00:25:59.010> or<00:25:59.130> is<00:25:59.340> there<00:25:59.490> a 00:25:59.510 --> 00:25:59.520 align:start position:0% back to versus insurance or is there a 00:25:59.520 --> 00:26:01.190 align:start position:0% back to versus insurance or is there a way<00:25:59.580> to<00:25:59.730> combine<00:26:00.030> the<00:26:00.240> two<00:26:00.450> so<00:26:00.840> I<00:26:00.990> actually 00:26:01.190 --> 00:26:01.200 align:start position:0% way to combine the two so I actually 00:26:01.200 --> 00:26:02.870 align:start position:0% way to combine the two so I actually think<00:26:01.590> that<00:26:01.710> you<00:26:01.950> are<00:26:01.980> in<00:26:02.220> a<00:26:02.310> kind<00:26:02.460> of<00:26:02.550> similar 00:26:02.870 --> 00:26:02.880 align:start position:0% think that you are in a kind of similar 00:26:02.880 --> 00:26:05.180 align:start position:0% think that you are in a kind of similar Cola<00:26:03.120> softball<00:26:03.540> direction<00:26:03.990> and<00:26:04.800> if<00:26:05.040> the 00:26:05.180 --> 00:26:05.190 align:start position:0% Cola softball direction and if the 00:26:05.190 --> 00:26:07.820 align:start position:0% Cola softball direction and if the reasons<00:26:05.580> I<00:26:05.760> would<00:26:05.820> give<00:26:06.150> for<00:26:06.180> that<00:26:06.450> are<00:26:06.870> like 00:26:07.820 --> 00:26:07.830 align:start position:0% reasons I would give for that are like 00:26:07.830 --> 00:26:10.250 align:start position:0% reasons I would give for that are like one<00:26:08.220> is<00:26:08.610> that<00:26:08.880> because<00:26:09.030> you<00:26:09.330> have<00:26:09.570> like<00:26:09.900> short 00:26:10.250 --> 00:26:10.260 align:start position:0% one is that because you have like short 00:26:10.260 --> 00:26:11.960 align:start position:0% one is that because you have like short chain<00:26:10.650> like<00:26:10.920> the<00:26:11.280> shorts<00:26:11.610> are<00:26:11.730> kind<00:26:11.850> of 00:26:11.960 --> 00:26:11.970 align:start position:0% chain like the shorts are kind of 00:26:11.970 --> 00:26:13.790 align:start position:0% chain like the shorts are kind of tightly<00:26:12.180> connected<00:26:12.540> to<00:26:12.750> each<00:26:12.960> other<00:26:13.140> like 00:26:13.790 --> 00:26:13.800 align:start position:0% tightly connected to each other like 00:26:13.800 --> 00:26:15.500 align:start position:0% tightly connected to each other like theoretically<00:26:14.490> you<00:26:14.640> could<00:26:14.820> have<00:26:14.880> designs 00:26:15.500 --> 00:26:15.510 align:start position:0% theoretically you could have designs 00:26:15.510 --> 00:26:17.300 align:start position:0% theoretically you could have designs where<00:26:15.900> I<00:26:16.110> have<00:26:16.260> things<00:26:16.470> happen<00:26:16.800> on<00:26:16.860> one<00:26:17.010> char 00:26:17.300 --> 00:26:17.310 align:start position:0% where I have things happen on one char 00:26:17.310 --> 00:26:18.710 align:start position:0% where I have things happen on one char but<00:26:17.490> let<00:26:17.580> me<00:26:17.670> just<00:26:17.880> get<00:26:18.030> moved<00:26:18.300> over<00:26:18.600> to 00:26:18.710 --> 00:26:18.720 align:start position:0% but let me just get moved over to 00:26:18.720 --> 00:26:19.100 align:start position:0% but let me just get moved over to another 00:26:19.100 --> 00:26:19.110 align:start position:0% another 00:26:19.110 --> 00:26:22.159 align:start position:0% another like<00:26:20.039> the<00:26:20.700> kind<00:26:21.120> of<00:26:21.269> secret<00:26:21.600> easier<00:26:21.929> makes 00:26:22.159 --> 00:26:22.169 align:start position:0% like the kind of secret easier makes 00:26:22.169 --> 00:26:25.490 align:start position:0% like the kind of secret easier makes that<00:26:22.380> easier<00:26:22.769> and<00:26:23.669> the<00:26:24.539> second<00:26:25.019> thing<00:26:25.200> is<00:26:25.470> that 00:26:25.490 --> 00:26:25.500 align:start position:0% that easier and the second thing is that 00:26:25.500 --> 00:26:28.850 align:start position:0% that easier and the second thing is that this<00:26:25.860> is<00:26:26.070> proposal<00:26:27.000> a<00:26:27.029> kind<00:26:27.390> of<00:26:27.860> execution 00:26:28.850 --> 00:26:28.860 align:start position:0% this is proposal a kind of execution 00:26:28.860 --> 00:26:33.950 align:start position:0% this is proposal a kind of execution aptly<00:26:29.429> the<00:26:29.850> proposal<00:26:30.450> of<00:26:32.000> having<00:26:33.000> execution 00:26:33.950 --> 00:26:33.960 align:start position:0% aptly the proposal of having execution 00:26:33.960 --> 00:27:16.129 align:start position:0% aptly the proposal of having execution happen<00:26:34.350> on<00:26:34.679> the<00:26:34.860> beacon<00:26:35.130> chain<00:26:35.399> like<00:26:35.730> if<00:27:15.139> in 00:27:16.129 --> 00:27:16.139 align:start position:0% happen on the beacon chain like if in 00:27:16.139 --> 00:27:18.289 align:start position:0% happen on the beacon chain like if in this<00:27:16.769> particular<00:27:16.980> case<00:27:17.669> the<00:27:17.880> move<00:27:18.029> would<00:27:18.179> be 00:27:18.289 --> 00:27:18.299 align:start position:0% this particular case the move would be 00:27:18.299 --> 00:27:19.009 align:start position:0% this particular case the move would be delivered 00:27:19.009 --> 00:27:19.019 align:start position:0% delivered 00:27:19.019 --> 00:27:21.289 align:start position:0% delivered yeah<00:27:19.620> but<00:27:19.799> in<00:27:20.220> any<00:27:20.370> other<00:27:20.519> case<00:27:20.760> I<00:27:20.940> don't<00:27:21.090> leave 00:27:21.289 --> 00:27:21.299 align:start position:0% yeah but in any other case I don't leave 00:27:21.299 --> 00:27:23.520 align:start position:0% yeah but in any other case I don't leave any<00:27:21.419> other<00:27:21.539> names<00:27:21.929> so<00:27:22.110> like<00:27:22.230> basically 00:27:23.520 --> 00:27:23.530 align:start position:0% any other names so like basically 00:27:23.530 --> 00:27:25.950 align:start position:0% any other names so like basically the<00:27:23.850> execution<00:27:24.850> environment<00:27:25.420> is<00:27:25.570> going<00:27:25.750> to<00:27:25.840> be 00:27:25.950 --> 00:27:25.960 align:start position:0% the execution environment is going to be 00:27:25.960 --> 00:27:27.990 align:start position:0% the execution environment is going to be or<00:27:26.200> every<00:27:26.530> one<00:27:26.770> of<00:27:26.800> these<00:27:26.980> lies<00:27:27.250> can<00:27:27.580> be<00:27:27.760> aware 00:27:27.990 --> 00:27:28.000 align:start position:0% or every one of these lies can be aware 00:27:28.000 --> 00:27:29.850 align:start position:0% or every one of these lies can be aware of<00:27:28.060> the<00:27:28.360> post<00:27:28.600> seat<00:27:28.840> all<00:27:29.050> of<00:27:29.260> po<00:27:29.410> state<00:27:29.650> routes 00:27:29.850 --> 00:27:29.860 align:start position:0% of the post seat all of po state routes 00:27:29.860 --> 00:27:35.040 align:start position:0% of the post seat all of po state routes over<00:27:29.980> here<00:27:32.460> sorry<00:27:33.460> you<00:27:33.880> could<00:27:34.150> just<00:27:34.420> get<00:27:34.990> a 00:27:35.040 --> 00:27:35.050 align:start position:0% over here sorry you could just get a 00:27:35.050 --> 00:27:40.350 align:start position:0% over here sorry you could just get a second<00:27:35.380> instance<00:27:35.650> that<00:27:38.700> you<00:27:39.700> can<00:27:39.730> you<00:27:40.330> can 00:27:40.350 --> 00:27:40.360 align:start position:0% second instance that you can you can 00:27:40.360 --> 00:27:44.370 align:start position:0% second instance that you can you can have<00:27:40.570> a<00:27:40.660> PE<00:27:40.900> that<00:27:41.230> swaps<00:27:42.130> yeah<00:27:43.080> to<00:27:44.080> someone 00:27:44.370 --> 00:27:44.380 align:start position:0% have a PE that swaps yeah to someone 00:27:44.380 --> 00:27:47.070 align:start position:0% have a PE that swaps yeah to someone else<00:27:44.530> that's<00:27:45.220> way<00:27:45.430> so<00:27:45.910> this<00:27:46.270> like<00:27:46.780> each 00:27:47.070 --> 00:27:47.080 align:start position:0% else that's way so this like each 00:27:47.080 --> 00:27:49.200 align:start position:0% else that's way so this like each general<00:27:47.470> the<00:27:47.740> thing<00:27:47.950> that<00:27:48.130> EE<00:27:48.310> execution<00:27:49.060> is 00:27:49.200 --> 00:27:49.210 align:start position:0% general the thing that EE execution is 00:27:49.210 --> 00:27:51.840 align:start position:0% general the thing that EE execution is aware<00:27:49.480> of<00:27:49.660> is<00:27:49.840> that<00:27:49.870> OPA<00:27:50.290> aware<00:27:50.560> of<00:27:50.830> the<00:27:51.250> like 00:27:51.840 --> 00:27:51.850 align:start position:0% aware of is that OPA aware of the like 00:27:51.850 --> 00:27:53.730 align:start position:0% aware of is that OPA aware of the like it's<00:27:52.030> always<00:27:52.420> aware<00:27:52.690> of<00:27:52.750> previously<00:27:53.470> route<00:27:53.620> of 00:27:53.730 --> 00:27:53.740 align:start position:0% it's always aware of previously route of 00:27:53.740 --> 00:27:55.410 align:start position:0% it's always aware of previously route of its<00:27:53.860> own<00:27:54.010> chart<00:27:54.280> and<00:27:54.580> it's<00:27:54.730> also<00:27:55.120> aware<00:27:55.360> of 00:27:55.410 --> 00:27:55.420 align:start position:0% its own chart and it's also aware of 00:27:55.420 --> 00:27:57.780 align:start position:0% its own chart and it's also aware of recent<00:27:55.750> statements<00:27:56.320> of<00:27:56.410> other<00:27:56.560> charts<00:27:56.950> but 00:27:57.780 --> 00:27:57.790 align:start position:0% recent statements of other charts but 00:27:57.790 --> 00:28:01.230 align:start position:0% recent statements of other charts but like<00:27:58.090> that<00:27:59.020> if<00:27:59.230> you<00:27:59.440> like<00:28:00.040> the<00:28:00.400> way<00:28:00.910> that 00:28:01.230 --> 00:28:01.240 align:start position:0% like that if you like the way that 00:28:01.240 --> 00:28:02.820 align:start position:0% like that if you like the way that you've<00:28:01.360> used<00:28:01.630> that<00:28:01.750> abstraction<00:28:02.260> to<00:28:02.470> be<00:28:02.800> a 00:28:02.820 --> 00:28:02.830 align:start position:0% you've used that abstraction to be a 00:28:02.830 --> 00:28:06.300 align:start position:0% you've used that abstraction to be a lots<00:28:03.340> of<00:28:03.460> things<00:28:03.700> like<00:28:04.060> you<00:28:04.180> could<00:28:05.070> yeah<00:28:06.070> and 00:28:06.300 --> 00:28:06.310 align:start position:0% lots of things like you could yeah and 00:28:06.310 --> 00:28:09.030 align:start position:0% lots of things like you could yeah and I'd<00:28:06.460> say<00:28:06.730> like<00:28:07.030> be<00:28:07.210> softly<00:28:07.600> the<00:28:08.350> facts<00:28:08.800> of<00:28:08.920> this 00:28:09.030 --> 00:28:09.040 align:start position:0% I'd say like be softly the facts of this 00:28:09.040 --> 00:28:12.720 align:start position:0% I'd say like be softly the facts of this proposal<00:28:09.490> is<00:28:10.000> kind<00:28:10.300> of<00:28:10.450> biasing<00:28:11.440> toward<00:28:11.980> more 00:28:12.720 --> 00:28:12.730 align:start position:0% proposal is kind of biasing toward more 00:28:12.730 --> 00:28:15.870 align:start position:0% proposal is kind of biasing toward more layer<00:28:13.600> one<00:28:13.960> communication<00:28:14.590> like<00:28:15.370> basically 00:28:15.870 --> 00:28:15.880 align:start position:0% layer one communication like basically 00:28:15.880 --> 00:28:18.330 align:start position:0% layer one communication like basically it<00:28:16.120> does<00:28:16.360> kind<00:28:16.720> of<00:28:16.840> oh<00:28:17.230> more<00:28:17.500> toward<00:28:17.980> this 00:28:18.330 --> 00:28:18.340 align:start position:0% it does kind of oh more toward this 00:28:18.340 --> 00:28:22.140 align:start position:0% it does kind of oh more toward this kind<00:28:18.790> of<00:28:19.360> idea<00:28:19.720> like<00:28:20.110> shards<00:28:20.560> is<00:28:20.710> being<00:28:21.150> things 00:28:22.140 --> 00:28:22.150 align:start position:0% kind of idea like shards is being things 00:28:22.150 --> 00:28:25.800 align:start position:0% kind of idea like shards is being things that<00:28:22.240> you<00:28:22.390> just<00:28:22.660> do<00:28:22.780> computation<00:28:24.510> you<00:28:25.510> want<00:28:25.690> to 00:28:25.800 --> 00:28:25.810 align:start position:0% that you just do computation you want to 00:28:25.810 --> 00:28:28.500 align:start position:0% that you just do computation you want to keep<00:28:26.380> the<00:28:26.950> state<00:28:27.220> from<00:28:27.250> the<00:28:27.490> shirt<00:28:27.730> just<00:28:28.390> we 00:28:28.500 --> 00:28:28.510 align:start position:0% keep the state from the shirt just we 00:28:28.510 --> 00:28:30.659 align:start position:0% keep the state from the shirt just we have<00:28:28.690> to<00:28:28.900> fit<00:28:29.830> missing 00:28:30.659 --> 00:28:30.669 align:start position:0% have to fit missing 00:28:30.669 --> 00:28:35.460 align:start position:0% have to fit missing it's<00:28:31.239> an<00:28:31.330> option<00:28:33.539> oh<00:28:34.539> you<00:28:35.109> mean<00:28:35.230> over<00:28:35.440> here 00:28:35.460 --> 00:28:35.470 align:start position:0% it's an option oh you mean over here 00:28:35.470 --> 00:28:39.720 align:start position:0% it's an option oh you mean over here yeah<00:28:36.340> yeah<00:28:36.850> yeah<00:28:37.330> so<00:28:38.249> so<00:28:39.249> he's<00:28:39.340> right<00:28:39.519> if<00:28:39.639> you 00:28:39.720 --> 00:28:39.730 align:start position:0% yeah yeah yeah so so he's right if you 00:28:39.730 --> 00:28:42.989 align:start position:0% yeah yeah yeah so so he's right if you want<00:28:39.940> that<00:28:40.059> feature<00:28:40.299> offender<00:28:40.779> need<00:28:40.929> a<00:28:41.759> caress 00:28:42.989 --> 00:28:42.999 align:start position:0% want that feature offender need a caress 00:28:42.999 --> 00:28:45.269 align:start position:0% want that feature offender need a caress well<00:28:43.179> you<00:28:43.330> know<00:28:43.480> like<00:28:44.440> well<00:28:44.739> every<00:28:45.070> sharp 00:28:45.269 --> 00:28:45.279 align:start position:0% well you know like well every sharp 00:28:45.279 --> 00:28:46.739 align:start position:0% well you know like well every sharp block<00:28:45.460> is<00:28:45.609> read<00:28:45.789> like<00:28:45.940> it's<00:28:46.090> given<00:28:46.299> points<00:28:46.600> for 00:28:46.739 --> 00:28:46.749 align:start position:0% block is read like it's given points for 00:28:46.749 --> 00:28:51.029 align:start position:0% block is read like it's given points for this<00:28:46.840> pretty<00:28:47.169> ansible<00:28:47.440> life<00:28:47.649> so<00:28:47.889> I<00:28:49.830> think<00:28:50.830> what 00:28:51.029 --> 00:28:51.039 align:start position:0% this pretty ansible life so I think what 00:28:51.039 --> 00:28:53.430 align:start position:0% this pretty ansible life so I think what Keyes<00:28:51.249> was<00:28:51.279> asking<00:28:51.820> better<00:28:51.999> be<00:28:52.179> could<00:28:52.440> they 00:28:53.430 --> 00:28:53.440 align:start position:0% Keyes was asking better be could they 00:28:53.440 --> 00:28:55.139 align:start position:0% Keyes was asking better be could they really<00:28:53.980> just<00:28:54.220> move<00:28:54.369> this<00:28:54.609> state<00:28:54.820> from<00:28:54.940> the 00:28:55.139 --> 00:28:55.149 align:start position:0% really just move this state from the 00:28:55.149 --> 00:28:58.080 align:start position:0% really just move this state from the Stratus<00:28:55.509> Oh<00:28:55.720> removal<00:28:56.320> yes<00:28:56.619> okay<00:28:56.950> so<00:28:57.090> this 00:28:58.080 --> 00:28:58.090 align:start position:0% Stratus Oh removal yes okay so this 00:28:58.090 --> 00:29:00.899 align:start position:0% Stratus Oh removal yes okay so this proposal<00:28:58.869> right<00:28:59.499> so<00:28:59.769> in<00:29:00.009> this<00:29:00.159> proposal<00:29:00.549> I 00:29:00.899 --> 00:29:00.909 align:start position:0% proposal right so in this proposal I 00:29:00.909 --> 00:29:02.820 align:start position:0% proposal right so in this proposal I guess<00:29:01.119> one<00:29:01.330> question<00:29:01.450> is<00:29:01.840> like<00:29:02.109> why<00:29:02.649> not 00:29:02.820 --> 00:29:02.830 align:start position:0% guess one question is like why not 00:29:02.830 --> 00:29:04.739 align:start position:0% guess one question is like why not simplify<00:29:03.429> even<00:29:03.700> more<00:29:03.879> radically<00:29:04.359> and<00:29:04.480> just 00:29:04.739 --> 00:29:04.749 align:start position:0% simplify even more radically and just 00:29:04.749 --> 00:29:06.509 align:start position:0% simplify even more radically and just say<00:29:04.960> like<00:29:05.200> if<00:29:05.529> this<00:29:05.830> thing<00:29:06.039> does<00:29:06.190> not<00:29:06.220> get 00:29:06.509 --> 00:29:06.519 align:start position:0% say like if this thing does not get 00:29:06.519 --> 00:29:09.930 align:start position:0% say like if this thing does not get included<00:29:06.639> then<00:29:07.149> this<00:29:07.299> thing<00:29:07.450> is<00:29:07.539> just<00:29:08.940> great 00:29:09.930 --> 00:29:09.940 align:start position:0% included then this thing is just great 00:29:09.940 --> 00:29:12.539 align:start position:0% included then this thing is just great and<00:29:10.179> if<00:29:10.720> you<00:29:10.749> do<00:29:10.989> that<00:29:11.230> then<00:29:11.559> like<00:29:12.129> you<00:29:12.279> really 00:29:12.539 --> 00:29:12.549 align:start position:0% and if you do that then like you really 00:29:12.549 --> 00:29:13.889 align:start position:0% and if you do that then like you really are<00:29:12.730> removing<00:29:13.179> state<00:29:13.419> from<00:29:13.570> chunks 00:29:13.889 --> 00:29:13.899 align:start position:0% are removing state from chunks 00:29:13.899 --> 00:29:16.169 align:start position:0% are removing state from chunks completely<00:29:14.379> because<00:29:14.769> like<00:29:15.279> all<00:29:15.730> the<00:29:15.970> state 00:29:16.169 --> 00:29:16.179 align:start position:0% completely because like all the state 00:29:16.179 --> 00:29:17.820 align:start position:0% completely because like all the state like<00:29:16.389> when<00:29:16.779> we<00:29:16.869> say<00:29:17.019> that<00:29:17.200> exists<00:29:17.559> a<00:29:17.619> state 00:29:17.820 --> 00:29:17.830 align:start position:0% like when we say that exists a state 00:29:17.830 --> 00:29:19.680 align:start position:0% like when we say that exists a state that<00:29:17.980> gets<00:29:18.070> faster<00:29:18.489> to<00:29:18.609> beat<00:29:18.759> the<00:29:18.850> chin<00:29:19.119> do<00:29:19.600> you 00:29:19.680 --> 00:29:19.690 align:start position:0% that gets faster to beat the chin do you 00:29:19.690 --> 00:29:22.289 align:start position:0% that gets faster to beat the chin do you give<00:29:19.840> a<00:29:19.869> lot<00:29:20.080> of<00:29:20.139> power<00:29:20.379> to<00:29:20.830> make<00:29:21.299> yes 00:29:22.289 --> 00:29:22.299 align:start position:0% give a lot of power to make yes 00:29:22.299 --> 00:29:27.180 align:start position:0% give a lot of power to make yes basically<00:29:24.840> because<00:29:25.840> I<00:29:25.960> can<00:29:26.139> I<00:29:26.379> can<00:29:26.559> just<00:29:26.739> say<00:29:26.889> I 00:29:27.180 --> 00:29:27.190 align:start position:0% basically because I can I can just say I 00:29:27.190 --> 00:29:29.940 align:start position:0% basically because I can I can just say I don't<00:29:27.340> like<00:29:27.489> that<00:29:27.549> block<00:29:28.019> and<00:29:29.019> now<00:29:29.320> that<00:29:29.769> block 00:29:29.940 --> 00:29:29.950 align:start position:0% don't like that block and now that block 00:29:29.950 --> 00:29:34.080 align:start position:0% don't like that block and now that block in<00:29:30.129> the<00:29:30.190> camera<00:29:32.190> we're<00:29:33.190> going<00:29:33.429> some<00:29:33.730> sort<00:29:33.970> of 00:29:34.080 --> 00:29:34.090 align:start position:0% in the camera we're going some sort of 00:29:34.090 --> 00:29:36.530 align:start position:0% in the camera we're going some sort of topic 00:29:36.530 --> 00:29:36.540 align:start position:0% 00:29:36.540 --> 00:29:40.380 align:start position:0% but<00:29:37.540> if<00:29:37.900> we<00:29:38.080> want<00:29:38.470> to<00:29:38.679> kind<00:29:39.190> of<00:29:39.309> make<00:29:40.120> things 00:29:40.380 --> 00:29:40.390 align:start position:0% but if we want to kind of make things 00:29:40.390 --> 00:29:42.240 align:start position:0% but if we want to kind of make things slightly<00:29:40.809> better<00:29:41.170> we<00:29:41.470> could<00:29:41.679> say<00:29:42.220> something 00:29:42.240 --> 00:29:42.250 align:start position:0% slightly better we could say something 00:29:42.250 --> 00:29:45.419 align:start position:0% slightly better we could say something like<00:29:42.850> oh<00:29:43.300> we<00:29:43.990> have<00:29:44.170> a<00:29:44.200> period<00:29:44.650> of<00:29:44.770> two<00:29:45.010> selasa 00:29:45.419 --> 00:29:45.429 align:start position:0% like oh we have a period of two selasa 00:29:45.429 --> 00:29:47.190 align:start position:0% like oh we have a period of two selasa move<00:29:45.700> in<00:29:45.820> which<00:29:46.000> to<00:29:46.179> move<00:29:46.510> these<00:29:46.660> things<00:29:46.900> and 00:29:47.190 --> 00:29:47.200 align:start position:0% move in which to move these things and 00:29:47.200 --> 00:29:48.510 align:start position:0% move in which to move these things and that<00:29:47.320> would<00:29:47.470> turn<00:29:47.590> the<00:29:47.710> power<00:29:47.980> to<00:29:48.250> a<00:29:48.280> wonderful 00:29:48.510 --> 00:29:48.520 align:start position:0% that would turn the power to a wonderful 00:29:48.520 --> 00:29:51.690 align:start position:0% that would turn the power to a wonderful to<00:29:48.790> go<00:29:49.030> like<00:29:49.240> I'm<00:29:50.110> scared<00:29:50.380> an<00:29:50.710> adjusted<00:29:51.309> on<00:29:51.460> his 00:29:51.690 --> 00:29:51.700 align:start position:0% to go like I'm scared an adjusted on his 00:29:51.700 --> 00:29:53.430 align:start position:0% to go like I'm scared an adjusted on his head<00:29:51.940> for<00:29:52.480> it<00:29:52.600> you<00:29:52.780> know<00:29:52.870> I<00:29:52.929> did<00:29:53.080> not<00:29:53.200> think<00:29:53.320> in 00:29:53.430 --> 00:29:53.440 align:start position:0% head for it you know I did not think in 00:29:53.440 --> 00:29:54.540 align:start position:0% head for it you know I did not think in the<00:29:53.500> board<00:29:53.679> so<00:29:53.860> it's<00:29:54.010> all<00:29:54.100> I<00:29:54.250> can<00:29:54.309> answer 00:29:54.540 --> 00:29:54.550 align:start position:0% the board so it's all I can answer 00:29:54.550 --> 00:29:58.169 align:start position:0% the board so it's all I can answer actually<00:29:55.770> yes<00:29:56.770> so<00:29:57.070> we<00:29:57.220> need<00:29:57.370> sorry<00:29:57.820> its<00:29:58.030> I 00:29:58.169 --> 00:29:58.179 align:start position:0% actually yes so we need sorry its I 00:29:58.179 --> 00:29:59.940 align:start position:0% actually yes so we need sorry its I don't<00:29:58.809> know<00:29:58.870> if<00:29:58.960> this<00:29:59.080> is<00:29:59.110> kind<00:29:59.380> of<00:29:59.410> a<00:29:59.650> second 00:29:59.940 --> 00:29:59.950 align:start position:0% don't know if this is kind of a second 00:29:59.950 --> 00:30:03.419 align:start position:0% don't know if this is kind of a second but<00:30:00.300> in<00:30:01.300> this<00:30:01.480> new<00:30:01.720> model<00:30:02.140> if<00:30:02.440> you<00:30:02.679> dose<00:30:02.950> the 00:30:03.419 --> 00:30:03.429 align:start position:0% but in this new model if you dose the 00:30:03.429 --> 00:30:05.549 align:start position:0% but in this new model if you dose the block<00:30:03.760> those<00:30:04.210> are<00:30:04.420> the<00:30:04.630> breakfast<00:30:05.020> is<00:30:05.170> one<00:30:05.410> of 00:30:05.549 --> 00:30:05.559 align:start position:0% block those are the breakfast is one of 00:30:05.559 --> 00:30:08.540 align:start position:0% block those are the breakfast is one of the<00:30:05.850> difficult<00:30:06.850> is<00:30:06.970> all<00:30:07.150> the<00:30:07.270> shards<00:30:07.510> falls 00:30:08.540 --> 00:30:08.550 align:start position:0% the difficult is all the shards falls 00:30:08.550 --> 00:30:11.010 align:start position:0% the difficult is all the shards falls short<00:30:09.550> see<00:30:09.850> why<00:30:10.000> you<00:30:10.059> of<00:30:10.360> a<00:30:10.480> cross<00:30:10.720> short 00:30:11.010 --> 00:30:11.020 align:start position:0% short see why you of a cross short 00:30:11.020 --> 00:30:12.660 align:start position:0% short see why you of a cross short communication<00:30:11.710> across<00:30:11.890> our<00:30:12.130> communications 00:30:12.660 --> 00:30:12.670 align:start position:0% communication across our communications 00:30:12.670 --> 00:30:15.660 align:start position:0% communication across our communications won't<00:30:12.850> repeat<00:30:13.360> drums<00:30:13.840> like<00:30:14.020> yeah<00:30:14.260> what<00:30:15.160> I 00:30:15.660 --> 00:30:15.670 align:start position:0% won't repeat drums like yeah what I 00:30:15.670 --> 00:30:17.340 align:start position:0% won't repeat drums like yeah what I guess<00:30:16.360> where<00:30:16.540> our<00:30:16.630> thoughts<00:30:16.809> are<00:30:16.990> out<00:30:17.110> back 00:30:17.340 --> 00:30:17.350 align:start position:0% guess where our thoughts are out back 00:30:17.350 --> 00:30:19.350 align:start position:0% guess where our thoughts are out back this<00:30:17.920> is<00:30:18.100> one<00:30:18.490> of<00:30:18.670> this<00:30:18.850> is<00:30:18.910> one<00:30:19.030> of<00:30:19.270> the 00:30:19.350 --> 00:30:19.360 align:start position:0% this is one of this is one of the 00:30:19.360 --> 00:30:21.120 align:start position:0% this is one of this is one of the reasons<00:30:19.690> just<00:30:19.929> as<00:30:20.080> excited<00:30:20.590> about<00:30:20.650> see<00:30:20.950> group 00:30:21.120 --> 00:30:21.130 align:start position:0% reasons just as excited about see group 00:30:21.130 --> 00:30:25.130 align:start position:0% reasons just as excited about see group leader<00:30:21.340> election<00:30:22.860> I<00:30:23.860> mean<00:30:24.220> so<00:30:24.610> thank<00:30:24.910> you 00:30:25.130 --> 00:30:25.140 align:start position:0% leader election I mean so thank you 00:30:25.140 --> 00:30:27.710 align:start position:0% leader election I mean so thank you the<00:30:26.040> optimistic<00:30:26.460> stuff<00:30:26.850> as<00:30:27.120> we<00:30:27.300> might<00:30:27.540> be 00:30:27.710 --> 00:30:27.720 align:start position:0% the optimistic stuff as we might be 00:30:27.720 --> 00:30:29.300 align:start position:0% the optimistic stuff as we might be avoided<00:30:28.110> in<00:30:28.200> the<00:30:28.290> short<00:30:28.500> term<00:30:28.680> I<00:30:28.890> think<00:30:28.980> will 00:30:29.300 --> 00:30:29.310 align:start position:0% avoided in the short term I think will 00:30:29.310 --> 00:30:33.500 align:start position:0% avoided in the short term I think will still<00:30:29.490> be<00:30:29.640> valuable<00:30:31.970> secret<00:30:32.970> leader<00:30:33.210> election 00:30:33.500 --> 00:30:33.510 align:start position:0% still be valuable secret leader election 00:30:33.510 --> 00:30:35.900 align:start position:0% still be valuable secret leader election protocols<00:30:34.140> I<00:30:34.350> are<00:30:34.590> not<00:30:34.830> too<00:30:35.070> scary<00:30:35.430> I<00:30:35.550> guess 00:30:35.900 --> 00:30:35.910 align:start position:0% protocols I are not too scary I guess 00:30:35.910 --> 00:30:37.910 align:start position:0% protocols I are not too scary I guess but<00:30:36.090> like<00:30:36.240> especially<00:30:36.540> 41<00:30:37.140> most<00:30:37.320> based<00:30:37.740> on 00:30:37.910 --> 00:30:37.920 align:start position:0% but like especially 41 most based on 00:30:37.920 --> 00:30:41.540 align:start position:0% but like especially 41 most based on written<00:30:38.100> signatures<00:30:40.070> do<00:30:41.070> you<00:30:41.190> know<00:30:41.310> anything 00:30:41.540 --> 00:30:41.550 align:start position:0% written signatures do you know anything 00:30:41.550 --> 00:30:44.060 align:start position:0% written signatures do you know anything is<00:30:41.820> the<00:30:41.970> toy<00:30:42.210> integration<00:30:42.870> so<00:30:43.560> basically<00:30:43.890> it's 00:30:44.060 --> 00:30:44.070 align:start position:0% is the toy integration so basically it's 00:30:44.070 --> 00:30:45.980 align:start position:0% is the toy integration so basically it's like<00:30:44.160> a<00:30:44.340> two-step<00:30:44.850> process<00:30:45.030> the<00:30:45.600> first<00:30:45.840> step 00:30:45.980 --> 00:30:45.990 align:start position:0% like a two-step process the first step 00:30:45.990 --> 00:30:49.790 align:start position:0% like a two-step process the first step because<00:30:46.440> this<00:30:48.530> pre-registration<00:30:49.560> when<00:30:49.680> you 00:30:49.790 --> 00:30:49.800 align:start position:0% because this pre-registration when you 00:30:49.800 --> 00:30:55.120 align:start position:0% because this pre-registration when you send<00:30:50.040> a<00:30:50.130> message<00:30:50.520> wishes<00:30:51.770> which<00:30:52.770> is<00:30:52.950> secretly 00:30:55.120 --> 00:30:55.130 align:start position:0% send a message wishes which is secretly 00:30:55.130 --> 00:30:57.290 align:start position:0% send a message wishes which is secretly actually<00:30:56.130> identity<00:30:56.670> but<00:30:56.850> people<00:30:57.150> don't 00:30:57.290 --> 00:30:57.300 align:start position:0% actually identity but people don't 00:30:57.300 --> 00:30:59.990 align:start position:0% actually identity but people don't realize<00:30:57.780> that<00:30:57.810> I<00:30:58.020> forgot<00:30:58.050> to<00:30:58.440> take<00:30:58.740> that<00:30:59.000> and 00:30:59.990 --> 00:31:00.000 align:start position:0% realize that I forgot to take that and 00:31:00.000 --> 00:31:01.640 align:start position:0% realize that I forgot to take that and this<00:31:00.150> has<00:31:00.360> to<00:31:00.480> be<00:31:00.570> double<00:31:00.990> to<00:31:01.110> also<00:31:01.440> when<00:31:01.560> you 00:31:01.640 --> 00:31:01.650 align:start position:0% this has to be double to also when you 00:31:01.650 --> 00:31:03.810 align:start position:0% this has to be double to also when you don't<00:31:01.860> do<00:31:02.400> linking 00:31:03.810 --> 00:31:03.820 align:start position:0% don't do linking 00:31:03.820 --> 00:31:08.980 align:start position:0% don't do linking Zebulon<00:31:04.820> he<00:31:05.000> produced<00:31:05.390> a<00:31:05.539> block<00:31:06.610> element<00:31:07.960> so<00:31:08.960> I 00:31:08.980 --> 00:31:08.990 align:start position:0% Zebulon he produced a block element so I 00:31:08.990 --> 00:31:11.590 align:start position:0% Zebulon he produced a block element so I guess<00:31:09.200> like<00:31:09.409> it's<00:31:09.860> not<00:31:10.190> useful<00:31:10.669> to<00:31:10.970> do<00:31:11.240> secret 00:31:11.590 --> 00:31:11.600 align:start position:0% guess like it's not useful to do secret 00:31:11.600 --> 00:31:13.389 align:start position:0% guess like it's not useful to do secret leader<00:31:11.779> election<00:31:12.169> until<00:31:12.740> we<00:31:12.890> have<00:31:13.070> look<00:31:13.309> at 00:31:13.389 --> 00:31:13.399 align:start position:0% leader election until we have look at 00:31:13.399 --> 00:31:15.700 align:start position:0% leader election until we have look at the<00:31:13.460> tour<00:31:13.669> backing<00:31:14.029> right<00:31:14.419> right<00:31:15.169> okay<00:31:15.470> and 00:31:15.700 --> 00:31:15.710 align:start position:0% the tour backing right right okay and 00:31:15.710 --> 00:31:18.610 align:start position:0% the tour backing right right okay and that's<00:31:16.460> that's<00:31:17.210> good<00:31:17.809> rationale<00:31:18.409> for 00:31:18.610 --> 00:31:18.620 align:start position:0% that's that's good rationale for 00:31:18.620 --> 00:31:20.970 align:start position:0% that's that's good rationale for delaying<00:31:19.010> and<00:31:19.220> until<00:31:19.490> phase<00:31:19.700> two<00:31:19.970> or<00:31:20.000> three 00:31:20.970 --> 00:31:20.980 align:start position:0% delaying and until phase two or three 00:31:20.980 --> 00:31:22.810 align:start position:0% delaying and until phase two or three what<00:31:21.980> do<00:31:22.100> you<00:31:22.190> mean<00:31:22.309> by<00:31:22.429> crushed 00:31:22.810 --> 00:31:22.820 align:start position:0% what do you mean by crushed 00:31:22.820 --> 00:31:25.570 align:start position:0% what do you mean by crushed recommendation<00:31:23.720> attempt<00:31:24.140> always<00:31:24.580> basically 00:31:25.570 --> 00:31:25.580 align:start position:0% recommendation attempt always basically 00:31:25.580 --> 00:31:28.149 align:start position:0% recommendation attempt always basically so<00:31:26.210> let's<00:31:26.480> assume<00:31:26.809> that<00:31:27.140> all<00:31:27.320> block<00:31:27.590> recorders 00:31:28.149 --> 00:31:28.159 align:start position:0% so let's assume that all block recorders 00:31:28.159 --> 00:31:30.370 align:start position:0% so let's assume that all block recorders become<00:31:28.460> bet<00:31:28.730> for<00:31:28.970> a<00:31:29.000> while<00:31:29.179> then<00:31:29.870> you<00:31:30.169> have 00:31:30.370 --> 00:31:30.380 align:start position:0% become bet for a while then you have 00:31:30.380 --> 00:31:39.490 align:start position:0% become bet for a while then you have like<00:31:30.679> short<00:31:30.950> walks<00:31:31.419> and<00:31:32.419> then<00:31:38.110> each<00:31:39.110> other<00:31:39.320> in 00:31:39.490 --> 00:31:39.500 align:start position:0% like short walks and then each other in 00:31:39.500 --> 00:32:01.060 align:start position:0% like short walks and then each other in this<00:31:39.649> direction<00:31:58.480> like<00:31:59.480> if<00:31:59.779> no<00:32:00.110> if<00:32:00.380> we<00:32:00.559> think 00:32:01.060 --> 00:32:01.070 align:start position:0% this direction like if no if we think 00:32:01.070 --> 00:32:02.769 align:start position:0% this direction like if no if we think what<00:32:01.399> you<00:32:01.549> might<00:32:01.730> be<00:32:01.940> saying<00:32:02.179> is<00:32:02.419> that<00:32:02.630> like 00:32:02.769 --> 00:32:02.779 align:start position:0% what you might be saying is that like 00:32:02.779 --> 00:32:04.659 align:start position:0% what you might be saying is that like you<00:32:02.990> could<00:32:03.230> also<00:32:03.380> have<00:32:03.710> communication<00:32:04.399> graphs 00:32:04.659 --> 00:32:04.669 align:start position:0% you could also have communication graphs 00:32:04.669 --> 00:32:06.460 align:start position:0% you could also have communication graphs that<00:32:04.850> are<00:32:05.090> kind<00:32:05.330> of<00:32:05.450> partially<00:32:05.929> intertwined 00:32:06.460 --> 00:32:06.470 align:start position:0% that are kind of partially intertwined 00:32:06.470 --> 00:32:09.279 align:start position:0% that are kind of partially intertwined so<00:32:07.309> like<00:32:07.490> for<00:32:07.700> example<00:32:07.850> like<00:32:08.690> gonna<00:32:08.899> require 00:32:09.279 --> 00:32:09.289 align:start position:0% so like for example like gonna require 00:32:09.289 --> 00:32:11.769 align:start position:0% so like for example like gonna require charts<00:32:09.950> you<00:32:10.340> could<00:32:10.520> require<00:32:10.880> this<00:32:11.179> block<00:32:11.570> to 00:32:11.769 --> 00:32:11.779 align:start position:0% charts you could require this block to 00:32:11.779 --> 00:32:13.840 align:start position:0% charts you could require this block to have<00:32:11.960> an<00:32:12.110> opinion<00:32:12.409> on<00:32:12.740> like<00:32:12.980> these<00:32:13.190> two<00:32:13.399> and 00:32:13.840 --> 00:32:13.850 align:start position:0% have an opinion on like these two and 00:32:13.850 --> 00:32:17.409 align:start position:0% have an opinion on like these two and you<00:32:13.970> could<00:32:14.120> have<00:32:14.270> a<00:32:14.330> look<00:32:14.659> at<00:32:14.809> way<00:32:16.090> like<00:32:17.090> in<00:32:17.390> a 00:32:17.409 --> 00:32:17.419 align:start position:0% you could have a look at way like in a 00:32:17.419 --> 00:32:18.820 align:start position:0% you could have a look at way like in a dependent 00:32:18.820 --> 00:32:18.830 align:start position:0% dependent 00:32:18.830 --> 00:32:21.880 align:start position:0% dependent anyway<00:32:19.190> I<00:32:19.490> guess<00:32:20.480> the<00:32:20.659> problem<00:32:21.049> of<00:32:21.500> the<00:32:21.620> air<00:32:21.740> is 00:32:21.880 --> 00:32:21.890 align:start position:0% anyway I guess the problem of the air is 00:32:21.890 --> 00:32:23.889 align:start position:0% anyway I guess the problem of the air is that<00:32:22.130> like<00:32:22.669> when<00:32:22.850> you<00:32:22.940> have<00:32:23.059> things<00:32:23.480> actually 00:32:23.889 --> 00:32:23.899 align:start position:0% that like when you have things actually 00:32:23.899 --> 00:32:25.450 align:start position:0% that like when you have things actually have<00:32:24.049> to<00:32:24.230> come<00:32:24.409> together<00:32:24.590> like<00:32:25.100> you<00:32:25.279> would 00:32:25.450 --> 00:32:25.460 align:start position:0% have to come together like you would 00:32:25.460 --> 00:32:28.480 align:start position:0% have to come together like you would have<00:32:25.669> to<00:32:25.970> kind<00:32:26.720> of<00:32:26.899> first<00:32:27.440> include<00:32:27.799> these<00:32:28.070> and 00:32:28.480 --> 00:32:28.490 align:start position:0% have to kind of first include these and 00:32:28.490 --> 00:32:30.070 align:start position:0% have to kind of first include these and then<00:32:28.580> based<00:32:28.789> on<00:32:28.940> that<00:32:29.000> activity<00:32:29.539> to<00:32:29.720> be<00:32:29.750> from 00:32:30.070 --> 00:32:30.080 align:start position:0% then based on that activity to be from 00:32:30.080 --> 00:32:32.860 align:start position:0% then based on that activity to be from that<00:32:30.110> it<00:32:30.320> would<00:32:30.529> be<00:32:30.649> so<00:32:31.580> the<00:32:32.390> opera's<00:32:32.840> of 00:32:32.860 --> 00:32:32.870 align:start position:0% that it would be so the opera's of 00:32:32.870 --> 00:32:34.509 align:start position:0% that it would be so the opera's of pre-caching<00:32:33.289> out<00:32:33.590> would<00:32:33.710> be<00:32:33.740> more<00:32:33.950> complex 00:32:34.509 --> 00:32:34.519 align:start position:0% pre-caching out would be more complex 00:32:34.519 --> 00:32:50.159 align:start position:0% pre-caching out would be more complex maybe<00:32:38.590> so<00:32:39.590> my<00:32:39.799> understanding<00:32:39.950> is<00:32:40.490> that<00:32:40.519> so<00:32:45.730> in 00:32:50.159 --> 00:32:50.169 align:start position:0% 00:32:50.169 --> 00:32:52.659 align:start position:0% short<00:32:51.169> what<00:32:51.440> is<00:32:51.649> it<00:32:51.799> really<00:32:52.220> good<00:32:52.340> boy<00:32:52.490> it's 00:32:52.659 --> 00:32:52.669 align:start position:0% short what is it really good boy it's 00:32:52.669 --> 00:32:56.129 align:start position:0% short what is it really good boy it's awesome 00:32:56.129 --> 00:32:56.139 align:start position:0% 00:32:56.139 --> 00:32:58.779 align:start position:0% yes<00:32:57.139> yeah<00:32:57.529> absolutely 00:32:58.779 --> 00:32:58.789 align:start position:0% yes yeah absolutely 00:32:58.789 --> 00:33:01.450 align:start position:0% yes yeah absolutely in<00:32:58.880> that<00:32:59.179> case<00:32:59.480> is<00:33:00.110> that<00:33:00.200> me<00:33:00.500> talk<00:33:00.740> about<00:33:00.769> some 00:33:01.450 --> 00:33:01.460 align:start position:0% in that case is that me talk about some 00:33:01.460 --> 00:33:06.220 align:start position:0% in that case is that me talk about some of<00:33:01.549> the<00:33:02.230> research<00:33:04.659> somebody<00:33:05.659> can<00:33:05.840> always<00:33:05.960> use 00:33:06.220 --> 00:33:06.230 align:start position:0% of the research somebody can always use 00:33:06.230 --> 00:33:07.930 align:start position:0% of the research somebody can always use how<00:33:06.350> do<00:33:06.409> you<00:33:06.500> exercise<00:33:06.769> at<00:33:07.070> all<00:33:07.100> just<00:33:07.880> about 00:33:07.930 --> 00:33:07.940 align:start position:0% how do you exercise at all just about 00:33:07.940 --> 00:33:12.399 align:start position:0% how do you exercise at all just about sir<00:33:09.580> yeah<00:33:10.580> how<00:33:11.179> do<00:33:11.240> you<00:33:11.360> resolve<00:33:11.929> the<00:33:12.200> crusher 00:33:12.399 --> 00:33:12.409 align:start position:0% sir yeah how do you resolve the crusher 00:33:12.409 --> 00:33:14.289 align:start position:0% sir yeah how do you resolve the crusher transactions<00:33:13.190> in<00:33:13.370> that<00:33:13.490> next<00:33:13.669> block<00:33:13.940> are<00:33:14.149> they 00:33:14.289 --> 00:33:14.299 align:start position:0% transactions in that next block are they 00:33:14.299 --> 00:33:16.060 align:start position:0% transactions in that next block are they personally<00:33:14.750> done<00:33:14.990> or<00:33:15.380> would<00:33:15.649> you<00:33:15.769> have<00:33:15.799> the 00:33:16.060 --> 00:33:16.070 align:start position:0% personally done or would you have the 00:33:16.070 --> 00:33:18.580 align:start position:0% personally done or would you have the options<00:33:16.490> so<00:33:16.789> here's<00:33:17.210> the<00:33:17.570> proposal<00:33:17.840> that<00:33:18.350> I 00:33:18.580 --> 00:33:18.590 align:start position:0% options so here's the proposal that I 00:33:18.590 --> 00:33:21.129 align:start position:0% options so here's the proposal that I have<00:33:18.830> the<00:33:19.419> total<00:33:20.419> the<00:33:20.779> total 00:33:21.129 --> 00:33:21.139 align:start position:0% have the total the total 00:33:21.139 --> 00:33:22.779 align:start position:0% have the total the total internetting<00:33:21.679> is<00:33:21.799> forcibly<00:33:22.159> done<00:33:22.490> but<00:33:22.730> the 00:33:22.779 --> 00:33:22.789 align:start position:0% internetting is forcibly done but the 00:33:22.789 --> 00:33:24.279 align:start position:0% internetting is forcibly done but the receipts<00:33:23.149> you<00:33:23.269> have<00:33:23.450> to<00:33:23.539> go<00:33:23.659> to<00:33:23.720> do<00:33:23.899> yourself 00:33:24.279 --> 00:33:24.289 align:start position:0% receipts you have to go to do yourself 00:33:24.289 --> 00:33:28.720 align:start position:0% receipts you have to go to do yourself and<00:33:24.470> there<00:33:24.559> an<00:33:24.649> execution<00:33:25.190> whole<00:33:25.370> thing 00:33:28.720 --> 00:33:28.730 align:start position:0% 00:33:28.730 --> 00:33:33.409 align:start position:0% you<00:33:29.730> must<00:33:30.000> be<00:33:30.179> is<00:33:30.570> curable<00:33:30.990> successfully<00:33:32.419> so 00:33:33.409 --> 00:33:33.419 align:start position:0% you must be is curable successfully so 00:33:33.419 --> 00:33:36.350 align:start position:0% you must be is curable successfully so basically<00:33:34.039> so<00:33:35.039> the<00:33:35.370> approach<00:33:35.669> in<00:33:35.909> my<00:33:36.029> proposal 00:33:36.350 --> 00:33:36.360 align:start position:0% basically so the approach in my proposal 00:33:36.360 --> 00:33:39.950 align:start position:0% basically so the approach in my proposal is<00:33:36.929> that<00:33:37.380> you<00:33:38.279> basically<00:33:38.549> require<00:33:39.360> each<00:33:39.659> chart 00:33:39.950 --> 00:33:39.960 align:start position:0% is that you basically require each chart 00:33:39.960 --> 00:33:42.560 align:start position:0% is that you basically require each chart blocks<00:33:40.260> here<00:33:40.620> so<00:33:40.919> like<00:33:41.490> if<00:33:41.669> mrs.<00:33:42.029> say<00:33:42.210> shard 00:33:42.560 --> 00:33:42.570 align:start position:0% blocks here so like if mrs. say shard 00:33:42.570 --> 00:33:44.810 align:start position:0% blocks here so like if mrs. say shard index<00:33:42.960> one<00:33:43.230> then<00:33:43.830> over<00:33:44.100> here<00:33:44.130> at<00:33:44.520> each<00:33:44.669> of 00:33:44.810 --> 00:33:44.820 align:start position:0% index one then over here at each of 00:33:44.820 --> 00:33:46.250 align:start position:0% index one then over here at each of these<00:33:44.940> short<00:33:45.210> blocks<00:33:45.480> is<00:33:45.720> going<00:33:45.870> to<00:33:45.929> publish<00:33:46.230> a 00:33:46.250 --> 00:33:46.260 align:start position:0% these short blocks is going to publish a 00:33:46.260 --> 00:33:48.409 align:start position:0% these short blocks is going to publish a more<00:33:46.500> poetry<00:33:46.799> that<00:33:47.070> just<00:33:47.250> says<00:33:47.429> like<00:33:47.669> this<00:33:48.210> is 00:33:48.409 --> 00:33:48.419 align:start position:0% more poetry that just says like this is 00:33:48.419 --> 00:33:49.700 align:start position:0% more poetry that just says like this is how<00:33:48.539> much<00:33:48.690> people<00:33:48.929> are<00:33:49.140> sending<00:33:49.440> to<00:33:49.559> each 00:33:49.700 --> 00:33:49.710 align:start position:0% how much people are sending to each 00:33:49.710 --> 00:33:51.590 align:start position:0% how much people are sending to each other<00:33:49.890> shark<00:33:50.250> and<00:33:50.520> so<00:33:50.940> this<00:33:51.179> chart<00:33:51.450> you're 00:33:51.590 --> 00:33:51.600 align:start position:0% other shark and so this chart you're 00:33:51.600 --> 00:33:52.970 align:start position:0% other shark and so this chart you're going<00:33:51.720> to<00:33:51.779> have<00:33:51.929> to<00:33:52.080> quit<00:33:52.440> the<00:33:52.529> morkul<00:33:52.799> bridge 00:33:52.970 --> 00:33:52.980 align:start position:0% going to have to quit the morkul bridge 00:33:52.980 --> 00:33:54.919 align:start position:0% going to have to quit the morkul bridge here<00:33:53.490> and<00:33:53.700> will<00:33:53.789> have<00:33:53.940> to<00:33:54.090> include<00:33:54.419> the 00:33:54.919 --> 00:33:54.929 align:start position:0% here and will have to include the 00:33:54.929 --> 00:33:56.269 align:start position:0% here and will have to include the moreover<00:33:55.320> actually<00:33:55.620> Sierra<00:33:55.919> will<00:33:56.070> have<00:33:56.159> to 00:33:56.269 --> 00:33:56.279 align:start position:0% moreover actually Sierra will have to 00:33:56.279 --> 00:33:58.510 align:start position:0% moreover actually Sierra will have to include<00:33:56.490> that<00:33:56.640> same<00:33:56.970> level<00:33:57.150> directions<00:33:57.630> here 00:33:58.510 --> 00:33:58.520 align:start position:0% include that same level directions here 00:33:58.520 --> 00:34:01.340 align:start position:0% include that same level directions here good<00:33:59.520> versus<00:34:00.299> one<00:34:00.510> proposal<00:34:01.080> I<00:34:01.110> mean<00:34:01.260> you 00:34:01.340 --> 00:34:01.350 align:start position:0% good versus one proposal I mean you 00:34:01.350 --> 00:34:02.870 align:start position:0% good versus one proposal I mean you could<00:34:01.559> also<00:34:01.710> have<00:34:02.100> it<00:34:02.130> make<00:34:02.399> it<00:34:02.580> more 00:34:02.870 --> 00:34:02.880 align:start position:0% could also have it make it more 00:34:02.880 --> 00:34:08.990 align:start position:0% could also have it make it more forgiving<00:34:06.649> the<00:34:07.649> following<00:34:07.980> question<00:34:08.429> is<00:34:08.669> like 00:34:08.990 --> 00:34:09.000 align:start position:0% forgiving the following question is like 00:34:09.000 --> 00:34:12.680 align:start position:0% forgiving the following question is like how<00:34:09.060> to<00:34:09.589> percent<00:34:10.589> motive<00:34:11.010> that<00:34:11.580> salsa<00:34:12.149> post<00:34:12.480> in 00:34:12.680 --> 00:34:12.690 align:start position:0% how to percent motive that salsa post in 00:34:12.690 --> 00:34:14.930 align:start position:0% how to percent motive that salsa post in the<00:34:12.839> latest<00:34:13.290> case<00:34:13.530> one<00:34:14.310> of<00:34:14.399> the<00:34:14.460> gloves<00:34:14.639> down 00:34:14.930 --> 00:34:14.940 align:start position:0% the latest case one of the gloves down 00:34:14.940 --> 00:34:16.000 align:start position:0% the latest case one of the gloves down not 00:34:16.000 --> 00:34:16.010 align:start position:0% not 00:34:16.010 --> 00:34:20.109 align:start position:0% not I've<00:34:16.280> become<00:34:16.669> black<00:34:17.330> and<00:34:17.600> later 00:34:20.109 --> 00:34:20.119 align:start position:0% 00:34:20.119 --> 00:34:22.849 align:start position:0% shamrocks<00:34:21.119> yes<00:34:21.450> and<00:34:21.779> so<00:34:22.109> that<00:34:22.349> means<00:34:22.619> they're 00:34:22.849 --> 00:34:22.859 align:start position:0% shamrocks yes and so that means they're 00:34:22.859 --> 00:34:26.809 align:start position:0% shamrocks yes and so that means they're mostly<00:34:23.159> converted<00:34:24.059> that's<00:34:25.279> for<00:34:26.279> an 00:34:26.809 --> 00:34:26.819 align:start position:0% mostly converted that's for an 00:34:26.819 --> 00:34:29.049 align:start position:0% mostly converted that's for an opportunity<00:34:27.329> through<00:34:27.509> all<00:34:27.779> these 00:34:29.049 --> 00:34:29.059 align:start position:0% opportunity through all these 00:34:29.059 --> 00:34:31.669 align:start position:0% opportunity through all these transactions<00:34:30.059> or<00:34:30.389> shanks<00:34:30.899> are<00:34:31.049> crossed<00:34:31.559> out 00:34:31.669 --> 00:34:31.679 align:start position:0% transactions or shanks are crossed out 00:34:31.679 --> 00:34:33.889 align:start position:0% transactions or shanks are crossed out messages<00:34:32.069> yeah<00:34:32.879> it's<00:34:33.329> possible 00:34:33.889 --> 00:34:33.899 align:start position:0% messages yeah it's possible 00:34:33.899 --> 00:34:36.950 align:start position:0% messages yeah it's possible so<00:34:34.200> that's<00:34:34.649> not<00:34:34.829> it's<00:34:35.519> not<00:34:35.730> gonna<00:34:35.879> be<00:34:36.089> forced 00:34:36.950 --> 00:34:36.960 align:start position:0% so that's not it's not gonna be forced 00:34:36.960 --> 00:34:39.230 align:start position:0% so that's not it's not gonna be forced but<00:34:37.349> even<00:34:37.589> on<00:34:37.679> these<00:34:37.799> ones<00:34:38.490> there's<00:34:38.879> still<00:34:39.119> be 00:34:39.230 --> 00:34:39.240 align:start position:0% but even on these ones there's still be 00:34:39.240 --> 00:34:44.059 align:start position:0% but even on these ones there's still be a<00:34:39.269> little<00:34:39.659> bit<00:34:39.809> used<00:34:40.339> right<00:34:42.409> yeah<00:34:43.440> so<00:34:43.740> if<00:34:43.889> there 00:34:44.059 --> 00:34:44.069 align:start position:0% a little bit used right yeah so if there 00:34:44.069 --> 00:35:00.259 align:start position:0% a little bit used right yeah so if there are<00:34:44.129> some<00:34:44.279> limit<00:34:44.519> to<00:34:44.549> how<00:34:44.759> much<00:34:44.879> you<00:34:44.940> can<00:34:59.269> in 00:35:00.259 --> 00:35:00.269 align:start position:0% are some limit to how much you can in 00:35:00.269 --> 00:35:02.480 align:start position:0% are some limit to how much you can in this<00:35:00.720> wall<00:35:01.230> okay<00:35:01.529> so<00:35:01.710> in<00:35:01.859> this<00:35:01.980> one<00:35:02.220> I'm 00:35:02.480 --> 00:35:02.490 align:start position:0% this wall okay so in this one I'm 00:35:02.490 --> 00:35:04.009 align:start position:0% this wall okay so in this one I'm generally<00:35:03.210> assuming<00:35:03.660> that<00:35:03.779> I've<00:35:03.869> here<00:35:03.990> a 00:35:04.009 --> 00:35:04.019 align:start position:0% generally assuming that I've here a 00:35:04.019 --> 00:35:05.509 align:start position:0% generally assuming that I've here a large<00:35:04.319> portion<00:35:04.619> of<00:35:04.799> transactions<00:35:05.369> will<00:35:05.490> be 00:35:05.509 --> 00:35:05.519 align:start position:0% large portion of transactions will be 00:35:05.519 --> 00:35:07.120 align:start position:0% large portion of transactions will be cross<00:35:05.789> shard 00:35:07.120 --> 00:35:07.130 align:start position:0% cross shard 00:35:07.130 --> 00:35:10.099 align:start position:0% cross shard so<00:35:08.130> okay<00:35:08.640> the<00:35:08.789> be<00:35:08.940> a<00:35:08.970> chain<00:35:09.329> is<00:35:09.509> not<00:35:09.690> required 00:35:10.099 --> 00:35:10.109 align:start position:0% so okay the be a chain is not required 00:35:10.109 --> 00:35:11.990 align:start position:0% so okay the be a chain is not required to<00:35:10.380> like<00:35:10.529> literally<00:35:10.890> include<00:35:11.400> like<00:35:11.670> a<00:35:11.700> lot<00:35:11.940> of 00:35:11.990 --> 00:35:12.000 align:start position:0% to like literally include like a lot of 00:35:12.000 --> 00:35:13.609 align:start position:0% to like literally include like a lot of one<00:35:12.150> data<00:35:12.390> for<00:35:12.690> every<00:35:12.809> single<00:35:13.230> cross<00:35:13.440> your 00:35:13.609 --> 00:35:13.619 align:start position:0% one data for every single cross your 00:35:13.619 --> 00:35:15.109 align:start position:0% one data for every single cross your transaction<00:35:14.279> great<00:35:14.460> like<00:35:14.640> most<00:35:14.880> of<00:35:15.029> it 00:35:15.109 --> 00:35:15.119 align:start position:0% transaction great like most of it 00:35:15.119 --> 00:35:17.380 align:start position:0% transaction great like most of it happens<00:35:15.420> to<00:35:15.539> receive<00:35:15.839> passing<00:35:16.259> like 00:35:17.380 --> 00:35:17.390 align:start position:0% happens to receive passing like 00:35:17.390 --> 00:35:20.420 align:start position:0% happens to receive passing like basically<00:35:18.390> in<00:35:18.720> everybody<00:35:19.470> thinks<00:35:19.890> you<00:35:19.980> need 00:35:20.420 --> 00:35:20.430 align:start position:0% basically in everybody thinks you need 00:35:20.430 --> 00:35:22.190 align:start position:0% basically in everybody thinks you need is<00:35:20.579> you<00:35:20.700> need<00:35:20.730> a<00:35:21.089> shower<00:35:21.329> chance<00:35:21.569> to<00:35:21.809> be<00:35:21.930> aware 00:35:22.190 --> 00:35:22.200 align:start position:0% is you need a shower chance to be aware 00:35:22.200 --> 00:35:26.059 align:start position:0% is you need a shower chance to be aware of<00:35:23.779> from<00:35:24.779> all<00:35:24.960> these<00:35:25.079> other<00:35:25.230> short<00:35:25.559> chains<00:35:25.829> you 00:35:26.059 --> 00:35:26.069 align:start position:0% of from all these other short chains you 00:35:26.069 --> 00:35:28.849 align:start position:0% of from all these other short chains you can<00:35:26.220> do<00:35:26.309> things<00:35:26.460> with<00:35:26.700> receipts<00:35:27.059> and<00:35:27.619> if<00:35:28.619> he 00:35:28.849 --> 00:35:28.859 align:start position:0% can do things with receipts and if he 00:35:28.859 --> 00:35:30.740 align:start position:0% can do things with receipts and if he wants<00:35:29.160> to<00:35:29.190> move<00:35:29.400> across<00:35:29.849> char<00:35:30.210> then<00:35:30.480> you<00:35:30.569> need 00:35:30.740 --> 00:35:30.750 align:start position:0% wants to move across char then you need 00:35:30.750 --> 00:35:32.690 align:start position:0% wants to move across char then you need to<00:35:30.869> have<00:35:30.990> up<00:35:31.230> some<00:35:31.500> kind<00:35:31.799> of<00:35:31.890> basically 00:35:32.690 --> 00:35:32.700 align:start position:0% to have up some kind of basically 00:35:32.700 --> 00:35:33.900 align:start position:0% to have up some kind of basically betting<00:35:33.150> capability 00:35:33.900 --> 00:35:33.910 align:start position:0% betting capability 00:35:33.910 --> 00:35:35.400 align:start position:0% betting capability we<00:35:34.030> can<00:35:34.150> have<00:35:34.270> different<00:35:34.539> execution<00:35:35.020> targets 00:35:35.400 --> 00:35:35.410 align:start position:0% we can have different execution targets 00:35:35.410 --> 00:35:40.890 align:start position:0% we can have different execution targets on<00:35:35.530> their<00:35:35.710> charts<00:35:37.770> so<00:35:39.510> we're<00:35:40.510> here<00:35:40.660> today<00:35:40.809> to 00:35:40.890 --> 00:35:40.900 align:start position:0% on their charts so we're here today to 00:35:40.900 --> 00:35:43.680 align:start position:0% on their charts so we're here today to talk<00:35:41.020> about<00:35:41.079> EPC<00:35:42.069> execution<00:35:42.700> in<00:35:42.970> general<00:35:43.359> and 00:35:43.680 --> 00:35:43.690 align:start position:0% talk about EPC execution in general and 00:35:43.690 --> 00:35:46.890 align:start position:0% talk about EPC execution in general and this<00:35:44.049> is<00:35:44.319> highly<00:35:44.890> relevant<00:35:45.569> just<00:35:46.569> because 00:35:46.890 --> 00:35:46.900 align:start position:0% this is highly relevant just because 00:35:46.900 --> 00:35:49.700 align:start position:0% this is highly relevant just because this<00:35:47.430> reconfiguring<00:35:48.430> of<00:35:48.549> the<00:35:48.640> architecture 00:35:49.700 --> 00:35:49.710 align:start position:0% this reconfiguring of the architecture 00:35:49.710 --> 00:36:30.029 align:start position:0% this reconfiguring of the architecture is<00:35:50.710> a<00:35:51.099> changes<00:35:51.849> how<00:35:51.970> we<00:35:52.000> might<00:36:28.740> need<00:36:29.740> to<00:36:29.890> keep 00:36:30.029 --> 00:36:30.039 align:start position:0% is a changes how we might need to keep 00:36:30.039 --> 00:36:34.200 align:start position:0% is a changes how we might need to keep an<00:36:30.220> eye<00:36:30.339> on<00:36:31.049> so<00:36:32.049> I<00:36:32.079> guess<00:36:32.440> if<00:36:32.829> I'm<00:36:33.099> accuser<00:36:33.579> then 00:36:34.200 --> 00:36:34.210 align:start position:0% an eye on so I guess if I'm accuser then 00:36:34.210 --> 00:36:36.510 align:start position:0% an eye on so I guess if I'm accuser then one<00:36:35.079> thing<00:36:35.260> you<00:36:35.349> could<00:36:35.589> do<00:36:35.770> is<00:36:35.950> you<00:36:36.099> could<00:36:36.220> say 00:36:36.510 --> 00:36:36.520 align:start position:0% one thing you could do is you could say 00:36:36.520 --> 00:36:40.049 align:start position:0% one thing you could do is you could say Oh<00:36:36.839> boom<00:36:37.839> I<00:36:38.109> am<00:36:38.740> a<00:36:38.770> good<00:36:39.130> I<00:36:39.339> have<00:36:39.579> like<00:36:39.819> full 00:36:40.049 --> 00:36:40.059 align:start position:0% Oh boom I am a good I have like full 00:36:40.059 --> 00:36:41.730 align:start position:0% Oh boom I am a good I have like full state<00:36:40.329> on<00:36:40.450> this<00:36:40.599> Shore<00:36:40.869> and<00:36:41.020> I<00:36:41.140> can<00:36:41.380> just<00:36:41.559> like 00:36:41.730 --> 00:36:41.740 align:start position:0% state on this Shore and I can just like 00:36:41.740 --> 00:36:44.099 align:start position:0% state on this Shore and I can just like self<00:36:42.039> package<00:36:42.430> another<00:36:43.329> thing<00:36:43.630> you<00:36:43.750> could<00:36:43.930> do 00:36:44.099 --> 00:36:44.109 align:start position:0% self package another thing you could do 00:36:44.109 --> 00:36:45.930 align:start position:0% self package another thing you could do is<00:36:44.230> you<00:36:44.349> could<00:36:44.529> just<00:36:44.799> like<00:36:44.980> talk<00:36:45.309> to<00:36:45.369> a<00:36:45.609> folk 00:36:45.930 --> 00:36:45.940 align:start position:0% is you could just like talk to a folk 00:36:45.940 --> 00:36:49.799 align:start position:0% is you could just like talk to a folk like<00:36:46.240> you<00:36:46.779> basically<00:36:46.960> use<00:36:47.650> like<00:36:48.329> my<00:36:49.329> client 00:36:49.799 --> 00:36:49.809 align:start position:0% like you basically use like my client 00:36:49.809 --> 00:36:50.690 align:start position:0% like you basically use like my client protocols 00:36:50.690 --> 00:36:50.700 align:start position:0% protocols 00:36:50.700 --> 00:36:54.380 align:start position:0% protocols like<00:36:51.060> I<00:36:51.360> see<00:36:51.990> two<00:36:52.410> spots<00:36:52.680> but<00:36:52.860> I<00:36:52.890> do<00:36:53.070> it<00:36:53.390> yeah 00:36:54.380 --> 00:36:54.390 align:start position:0% like I see two spots but I do it yeah 00:36:54.390 --> 00:36:56.330 align:start position:0% like I see two spots but I do it yeah yeah<00:36:54.930> you<00:36:55.080> use<00:36:55.260> a<00:36:55.290> length<00:36:55.500> length<00:36:55.710> protocol<00:36:56.310> a 00:36:56.330 --> 00:36:56.340 align:start position:0% yeah you use a length length protocol a 00:36:56.340 --> 00:36:58.400 align:start position:0% yeah you use a length length protocol a blank<00:36:56.820> blank<00:36:57.060> protocols<00:36:57.570> right<00:36:57.810> so<00:36:57.990> basically 00:36:58.400 --> 00:36:58.410 align:start position:0% blank blank protocols right so basically 00:36:58.410 --> 00:37:00.440 align:start position:0% blank blank protocols right so basically likes<00:36:58.740> you<00:36:58.920> talk<00:36:59.280> to<00:36:59.580> if<00:36:59.760> you<00:36:59.910> don't<00:37:00.120> have<00:37:00.270> full 00:37:00.440 --> 00:37:00.450 align:start position:0% likes you talk to if you don't have full 00:37:00.450 --> 00:37:03.290 align:start position:0% likes you talk to if you don't have full state<00:37:00.660> and<00:37:00.810> some<00:37:00.960> charge<00:37:01.230> for<00:37:02.130> some<00:37:02.340> the 00:37:03.290 --> 00:37:03.300 align:start position:0% state and some charge for some the 00:37:03.300 --> 00:37:05.090 align:start position:0% state and some charge for some the execution<00:37:03.960> environment<00:37:04.530> then<00:37:04.740> you<00:37:04.770> would 00:37:05.090 --> 00:37:05.100 align:start position:0% execution environment then you would 00:37:05.100 --> 00:37:06.980 align:start position:0% execution environment then you would just<00:37:05.310> talk<00:37:05.790> to<00:37:06.000> a<00:37:06.030> server<00:37:06.270> but<00:37:06.540> does<00:37:06.750> the 00:37:06.980 --> 00:37:06.990 align:start position:0% just talk to a server but does the 00:37:06.990 --> 00:37:08.750 align:start position:0% just talk to a server but does the server<00:37:07.230> gives<00:37:07.470> you<00:37:07.590> branches<00:37:08.130> so<00:37:08.400> that<00:37:08.610> you 00:37:08.750 --> 00:37:08.760 align:start position:0% server gives you branches so that you 00:37:08.760 --> 00:37:11.810 align:start position:0% server gives you branches so that you have<00:37:08.910> a<00:37:08.940> package<00:37:09.420> of<00:37:09.570> broadcast<00:37:10.640> right<00:37:11.640> so 00:37:11.810 --> 00:37:11.820 align:start position:0% have a package of broadcast right so 00:37:11.820 --> 00:37:13.790 align:start position:0% have a package of broadcast right so that<00:37:12.000> simple<00:37:12.360> great<00:37:12.660> supposed<00:37:13.230> to<00:37:13.320> be<00:37:13.470> market 00:37:13.790 --> 00:37:13.800 align:start position:0% that simple great supposed to be market 00:37:13.800 --> 00:37:15.770 align:start position:0% that simple great supposed to be market but<00:37:13.950> there's<00:37:14.130> still<00:37:14.340> a<00:37:14.400> notion<00:37:14.790> of<00:37:14.910> stay 00:37:15.770 --> 00:37:15.780 align:start position:0% but there's still a notion of stay 00:37:15.780 --> 00:37:18.020 align:start position:0% but there's still a notion of stay providers<00:37:16.260> really<00:37:16.980> layers<00:37:17.340> I<00:37:17.520> don't<00:37:17.910> know 00:37:18.020 --> 00:37:18.030 align:start position:0% providers really layers I don't know 00:37:18.030 --> 00:37:19.760 align:start position:0% providers really layers I don't know that<00:37:18.300> term<00:37:18.480> that<00:37:18.750> really<00:37:19.020> applies<00:37:19.320> to<00:37:19.350> all 00:37:19.760 --> 00:37:19.770 align:start position:0% that term that really applies to all 00:37:19.770 --> 00:37:22.010 align:start position:0% that term that really applies to all sorts<00:37:20.040> of<00:37:20.100> things<00:37:20.250> but<00:37:20.430> there's<00:37:21.330> still<00:37:21.510> an 00:37:22.010 --> 00:37:22.020 align:start position:0% sorts of things but there's still an 00:37:22.020 --> 00:37:26.690 align:start position:0% sorts of things but there's still an idea<00:37:22.380> of<00:37:22.530> like<00:37:22.680> other<00:37:24.890> like<00:37:25.890> weird 00:37:26.690 --> 00:37:26.700 align:start position:0% idea of like other like weird 00:37:26.700 --> 00:37:28.610 align:start position:0% idea of like other like weird general<00:37:27.240> general<00:37:27.390> purpose<00:37:27.960> hash<00:37:28.170> preimage 00:37:28.610 --> 00:37:28.620 align:start position:0% general general purpose hash preimage 00:37:28.620 --> 00:37:31.580 align:start position:0% general general purpose hash preimage for<00:37:28.830> lovers<00:37:29.130> that<00:37:29.460> market<00:37:30.030> for<00:37:30.420> just<00:37:30.600> market 00:37:31.580 --> 00:37:31.590 align:start position:0% for lovers that market for just market 00:37:31.590 --> 00:37:36.500 align:start position:0% for lovers that market for just market participants<00:37:33.920> one<00:37:34.920> concern<00:37:35.490> with<00:37:36.000> this<00:37:36.180> we 00:37:36.500 --> 00:37:36.510 align:start position:0% participants one concern with this we 00:37:36.510 --> 00:37:39.800 align:start position:0% participants one concern with this we had<00:37:36.720> was<00:37:37.550> in<00:37:38.550> the<00:37:38.610> previous<00:37:39.060> one<00:37:39.270> it<00:37:39.540> was<00:37:39.660> being 00:37:39.800 --> 00:37:39.810 align:start position:0% had was in the previous one it was being 00:37:39.810 --> 00:37:41.120 align:start position:0% had was in the previous one it was being a<00:37:39.960> bigger<00:37:40.140> concern<00:37:40.410> because<00:37:40.860> you<00:37:41.010> had<00:37:41.100> a 00:37:41.120 --> 00:37:41.130 align:start position:0% a bigger concern because you had a 00:37:41.130 --> 00:37:43.760 align:start position:0% a bigger concern because you had a passenger<00:37:42.060> port<00:37:42.420> charts<00:37:42.780> and<00:37:43.410> the<00:37:43.620> same 00:37:43.760 --> 00:37:43.770 align:start position:0% passenger port charts and the same 00:37:43.770 --> 00:37:45.620 align:start position:0% passenger port charts and the same provider<00:37:43.920> would<00:37:44.220> have<00:37:44.430> to<00:37:44.640> have<00:37:44.940> an<00:37:45.060> eye<00:37:45.150> on 00:37:45.620 --> 00:37:45.630 align:start position:0% provider would have to have an eye on 00:37:45.630 --> 00:37:52.550 align:start position:0% provider would have to have an eye on each<00:37:46.140> of<00:37:46.350> those<00:37:50.750> and<00:37:51.750> I<00:37:51.930> think<00:37:51.960> the<00:37:52.170> reasons<00:37:52.470> we 00:37:52.550 --> 00:37:52.560 align:start position:0% each of those and I think the reasons we 00:37:52.560 --> 00:37:55.720 align:start position:0% each of those and I think the reasons we like<00:37:52.740> the<00:37:53.040> the<00:37:53.630> pre<00:37:54.630> interrupt 00:37:55.720 --> 00:37:55.730 align:start position:0% like the the pre interrupt 00:37:55.730 --> 00:37:59.230 align:start position:0% like the the pre interrupt red<00:37:56.650> was<00:37:57.650> that<00:37:57.920> you<00:37:58.310> could<00:37:58.550> maybe<00:37:58.730> have<00:37:59.030> some 00:37:59.230 --> 00:37:59.240 align:start position:0% red was that you could maybe have some 00:37:59.240 --> 00:38:00.970 align:start position:0% red was that you could maybe have some kind<00:37:59.450> of<00:37:59.540> scheduling<00:38:00.050> figuring<00:38:00.589> out<00:38:00.740> which 00:38:00.970 --> 00:38:00.980 align:start position:0% kind of scheduling figuring out which 00:38:00.980 --> 00:38:03.370 align:start position:0% kind of scheduling figuring out which charts<00:38:01.550> given<00:38:01.940> insufficient<00:38:02.390> marketing<00:38:02.869> so 00:38:03.370 --> 00:38:03.380 align:start position:0% charts given insufficient marketing so 00:38:03.380 --> 00:38:05.819 align:start position:0% charts given insufficient marketing so state<00:38:03.800> water<00:38:04.070> could<00:38:04.490> just<00:38:05.000> respective<00:38:05.630> you 00:38:05.819 --> 00:38:05.829 align:start position:0% state water could just respective you 00:38:05.829 --> 00:38:08.230 align:start position:0% state water could just respective you yeah<00:38:06.859> I<00:38:07.040> mean<00:38:07.280> here<00:38:07.520> you<00:38:07.550> can<00:38:07.760> also<00:38:07.880> have<00:38:08.089> your 00:38:08.230 --> 00:38:08.240 align:start position:0% yeah I mean here you can also have your 00:38:08.240 --> 00:38:21.250 align:start position:0% yeah I mean here you can also have your exit<00:38:08.630> environments<00:38:19.540> funny<00:38:20.540> that<00:38:20.720> like<00:38:20.990> I 00:38:21.250 --> 00:38:21.260 align:start position:0% exit environments funny that like I 00:38:21.260 --> 00:38:27.490 align:start position:0% exit environments funny that like I think<00:38:21.500> that<00:38:21.619> maybe<00:38:24.310> like<00:38:25.310> the<00:38:26.030> issue<00:38:26.900> of<00:38:27.200> just 00:38:27.490 --> 00:38:27.500 align:start position:0% think that maybe like the issue of just 00:38:27.500 --> 00:38:29.859 align:start position:0% think that maybe like the issue of just like<00:38:27.680> in<00:38:28.339> general<00:38:28.490> aggregated<00:38:29.270> transactions 00:38:29.859 --> 00:38:29.869 align:start position:0% like in general aggregated transactions 00:38:29.869 --> 00:38:31.690 align:start position:0% like in general aggregated transactions for<00:38:30.050> I<00:38:30.109> retains<00:38:30.500> that<00:38:30.710> state<00:38:31.130> isn't<00:38:31.520> something 00:38:31.690 --> 00:38:31.700 align:start position:0% for I retains that state isn't something 00:38:31.700 --> 00:38:33.910 align:start position:0% for I retains that state isn't something that<00:38:32.030> the<00:38:32.380> specification<00:38:33.380> actually 00:38:33.910 --> 00:38:33.920 align:start position:0% that the specification actually 00:38:33.920 --> 00:38:36.190 align:start position:0% that the specification actually addresses<00:38:34.339> right<00:38:34.520> so<00:38:35.240> it's<00:38:35.420> more<00:38:35.660> about<00:38:35.810> like 00:38:36.190 --> 00:38:36.200 align:start position:0% addresses right so it's more about like 00:38:36.200 --> 00:38:39.099 align:start position:0% addresses right so it's more about like I<00:38:36.680> feel<00:38:37.190> like<00:38:37.250> you<00:38:37.720> initially<00:38:38.720> at<00:38:38.810> least<00:38:38.960> like 00:38:39.099 --> 00:38:39.109 align:start position:0% I feel like you initially at least like 00:38:39.109 --> 00:38:42.400 align:start position:0% I feel like you initially at least like i<00:38:39.200> mean<00:38:39.320> e-to<00:38:39.950> is<00:38:40.339> mostly<00:38:40.700> about<00:38:41.410> achieving 00:38:42.400 --> 00:38:42.410 align:start position:0% i mean e-to is mostly about achieving 00:38:42.410 --> 00:38:46.890 align:start position:0% i mean e-to is mostly about achieving consensus<00:38:42.950> then<00:38:45.040> just<00:38:46.040> you<00:38:46.190> know<00:38:46.220> like<00:38:46.490> making 00:38:46.890 --> 00:38:46.900 align:start position:0% consensus then just you know like making 00:38:46.900 --> 00:38:49.569 align:start position:0% consensus then just you know like making state<00:38:47.900> and<00:38:48.079> execution<00:38:48.530> is<00:38:48.650> an<00:38:48.859> abstract<00:38:49.400> thing 00:38:49.569 --> 00:38:49.579 align:start position:0% state and execution is an abstract thing 00:38:49.579 --> 00:38:51.760 align:start position:0% state and execution is an abstract thing that<00:38:49.760> is<00:38:49.880> so<00:38:50.480> funny<00:38:50.750> because<00:38:50.869> I<00:38:51.140> can<00:38:51.320> eat<00:38:51.500> one 00:38:51.760 --> 00:38:51.770 align:start position:0% that is so funny because I can eat one 00:38:51.770 --> 00:38:53.680 align:start position:0% that is so funny because I can eat one all<00:38:52.010> we've<00:38:52.220> ever<00:38:52.369> been<00:38:52.609> doing<00:38:52.910> is<00:38:53.030> like<00:38:53.210> people 00:38:53.680 --> 00:38:53.690 align:start position:0% all we've ever been doing is like people 00:38:53.690 --> 00:38:55.240 align:start position:0% all we've ever been doing is like people always<00:38:54.020> just<00:38:54.440> been<00:38:54.560> worrying<00:38:54.890> about<00:38:54.980> like 00:38:55.240 --> 00:38:55.250 align:start position:0% always just been worrying about like 00:38:55.250 --> 00:38:56.770 align:start position:0% always just been worrying about like state<00:38:55.490> in<00:38:55.609> execution<00:38:56.210> I<00:38:56.300> can't<00:38:56.480> think<00:38:56.690> what 00:38:56.770 --> 00:38:56.780 align:start position:0% state in execution I can't think what 00:38:56.780 --> 00:38:59.050 align:start position:0% state in execution I can't think what census<00:38:57.140> portion<00:38:57.470> of<00:38:57.530> each<00:38:57.650> want<00:38:57.950> is<00:38:58.160> that<00:38:58.369> like 00:38:59.050 --> 00:38:59.060 align:start position:0% census portion of each want is that like 00:38:59.060 --> 00:39:01.540 align:start position:0% census portion of each want is that like never<00:38:59.359> Bryce<00:38:59.710> so<00:39:00.710> like<00:39:00.950> I<00:39:00.980> mean<00:39:01.220> all<00:39:01.400> that 00:39:01.540 --> 00:39:01.550 align:start position:0% never Bryce so like I mean all that 00:39:01.550 --> 00:39:02.920 align:start position:0% never Bryce so like I mean all that never<00:39:01.730> breaks<00:39:01.940> in<00:39:02.119> each<00:39:02.240> one<00:39:02.450> is<00:39:02.599> you<00:39:02.810> know 00:39:02.920 --> 00:39:02.930 align:start position:0% never breaks in each one is you know 00:39:02.930 --> 00:39:04.420 align:start position:0% never breaks in each one is you know like<00:39:03.109> say<00:39:03.319> that<00:39:03.500> execution<00:39:03.890> so<00:39:04.130> I<00:39:04.160> feel<00:39:04.400> like 00:39:04.420 --> 00:39:04.430 align:start position:0% like say that execution so I feel like 00:39:04.430 --> 00:39:10.480 align:start position:0% like say that execution so I feel like this<00:39:05.109> something<00:39:06.109> where<00:39:08.140> this<00:39:09.140> is<00:39:09.349> all<00:39:09.619> there's 00:39:10.480 --> 00:39:10.490 align:start position:0% this something where this is all there's 00:39:10.490 --> 00:39:13.540 align:start position:0% this something where this is all there's definitely<00:39:11.390> kind<00:39:11.630> of<00:39:11.750> bad<00:39:12.589> in<00:39:12.619> good<00:39:13.010> aspects 00:39:13.540 --> 00:39:13.550 align:start position:0% definitely kind of bad in good aspects 00:39:13.550 --> 00:39:16.900 align:start position:0% definitely kind of bad in good aspects to<00:39:13.730> this<00:39:13.880> like<00:39:14.390> one<00:39:15.170> good<00:39:15.410> aspect<00:39:15.920> is<00:39:16.190> that<00:39:16.220> it 00:39:16.900 --> 00:39:16.910 align:start position:0% to this like one good aspect is that it 00:39:16.910 --> 00:39:18.970 align:start position:0% to this like one good aspect is that it basically<00:39:17.150> mats<00:39:17.750> that<00:39:17.960> like<00:39:18.140> if<00:39:18.290> we<00:39:18.500> want<00:39:18.740> we 00:39:18.970 --> 00:39:18.980 align:start position:0% basically mats that like if we want we 00:39:18.980 --> 00:39:20.580 align:start position:0% basically mats that like if we want we can<00:39:19.099> just<00:39:19.339> like<00:39:19.520> bring 00:39:20.580 --> 00:39:20.590 align:start position:0% can just like bring 00:39:20.590 --> 00:39:22.620 align:start position:0% can just like bring state<00:39:20.890> an<00:39:21.010> execution<00:39:21.610> and<00:39:21.850> it<00:39:21.970> rules<00:39:22.180> almost 00:39:22.620 --> 00:39:22.630 align:start position:0% state an execution and it rules almost 00:39:22.630 --> 00:39:25.680 align:start position:0% state an execution and it rules almost as<00:39:22.780> they<00:39:22.930> are<00:39:23.110> inside<00:39:23.440> of<00:39:23.470> this<00:39:24.090> the<00:39:25.090> in<00:39:25.270> absent 00:39:25.680 --> 00:39:25.690 align:start position:0% as they are inside of this the in absent 00:39:25.690 --> 00:39:29.130 align:start position:0% as they are inside of this the in absent Prosser<00:39:25.900> and<00:39:26.080> stuff<00:39:26.410> but<00:39:26.770> and<00:39:27.580> another<00:39:28.390> and 00:39:29.130 --> 00:39:29.140 align:start position:0% Prosser and stuff but and another and 00:39:29.140 --> 00:39:31.740 align:start position:0% Prosser and stuff but and another and about<00:39:30.100> thing<00:39:30.370> obviously<00:39:30.580> acceptance<00:39:31.420> means 00:39:31.740 --> 00:39:31.750 align:start position:0% about thing obviously acceptance means 00:39:31.750 --> 00:39:34.740 align:start position:0% about thing obviously acceptance means that<00:39:32.140> kind<00:39:32.410> of<00:39:32.590> work<00:39:33.340> is<00:39:33.490> being<00:39:33.700> done<00:39:33.820> to<00:39:34.090> and 00:39:34.740 --> 00:39:34.750 align:start position:0% that kind of work is being done to and 00:39:34.750 --> 00:39:37.230 align:start position:0% that kind of work is being done to and have<00:39:34.930> allow<00:39:35.620> lots<00:39:36.190> of<00:39:36.430> different<00:39:36.820> kinds<00:39:37.180> of 00:39:37.230 --> 00:39:37.240 align:start position:0% have allow lots of different kinds of 00:39:37.240 --> 00:39:39.750 align:start position:0% have allow lots of different kinds of things<00:39:37.510> to<00:39:37.720> work<00:39:37.930> but<00:39:38.260> the<00:39:38.530> kind<00:39:38.770> of<00:39:38.920> less<00:39:39.520> work 00:39:39.750 --> 00:39:39.760 align:start position:0% things to work but the kind of less work 00:39:39.760 --> 00:39:41.700 align:start position:0% things to work but the kind of less work as<00:39:39.940> we<00:39:40.090> have<00:39:40.120> done<00:39:40.390> to<00:39:40.570> grieve<00:39:40.810> one<00:39:41.140> specific 00:39:41.700 --> 00:39:41.710 align:start position:0% as we have done to grieve one specific 00:39:41.710 --> 00:39:43.170 align:start position:0% as we have done to grieve one specific very<00:39:41.920> good<00:39:42.130> thing<00:39:42.310> that<00:39:42.490> works<00:39:42.700> but<00:39:43.000> like 00:39:43.170 --> 00:39:43.180 align:start position:0% very good thing that works but like 00:39:43.180 --> 00:39:45.030 align:start position:0% very good thing that works but like that's<00:39:43.360> that's<00:39:43.930> parallelizable<00:39:44.620> it<00:39:44.860> just 00:39:45.030 --> 00:39:45.040 align:start position:0% that's that's parallelizable it just 00:39:45.040 --> 00:39:47.520 align:start position:0% that's that's parallelizable it just means<00:39:45.250> that<00:39:45.400> we<00:39:45.970> need<00:39:46.270> more<00:39:46.480> two<00:39:46.660> more<00:39:47.290> teams 00:39:47.520 --> 00:39:47.530 align:start position:0% means that we need more two more teams 00:39:47.530 --> 00:39:48.750 align:start position:0% means that we need more two more teams that<00:39:47.770> get<00:39:48.010> it's<00:39:48.160> a<00:39:48.220> greeting<00:39:48.430> of<00:39:48.610> your 00:39:48.750 --> 00:39:48.760 align:start position:0% that get it's a greeting of your 00:39:48.760 --> 00:39:51.630 align:start position:0% that get it's a greeting of your specific<00:39:48.990> they<00:39:49.990> know<00:39:50.230> thing<00:39:50.890> that<00:39:50.920> works<00:39:51.280> in 00:39:51.630 --> 00:39:51.640 align:start position:0% specific they know thing that works in 00:39:51.640 --> 00:39:55.640 align:start position:0% specific they know thing that works in one<00:39:51.880> benefit<00:39:52.330> is<00:39:52.360> that<00:39:52.690> it<00:39:53.590> means<00:39:53.950> that<00:39:54.520> I 00:39:55.640 --> 00:39:55.650 align:start position:0% one benefit is that it means that I 00:39:55.650 --> 00:39:59.310 align:start position:0% one benefit is that it means that I think<00:39:56.650> if<00:39:56.860> we<00:39:57.040> if<00:39:57.310> we<00:39:57.370> do<00:39:57.790> have<00:39:58.060> a<00:39:58.090> kind<00:39:58.450> of<00:39:58.570> good 00:39:59.310 --> 00:39:59.320 align:start position:0% think if we if we do have a kind of good 00:39:59.320 --> 00:40:01.620 align:start position:0% think if we if we do have a kind of good solid<00:39:59.740> and<00:40:00.220> census<00:40:00.580> layer<00:40:00.820> that<00:40:01.180> provides 00:40:01.620 --> 00:40:01.630 align:start position:0% solid and census layer that provides 00:40:01.630 --> 00:40:03.630 align:start position:0% solid and census layer that provides kind<00:40:01.990> of<00:40:02.140> enough<00:40:02.530> base<00:40:02.800> functionality<00:40:03.310> that 00:40:03.630 --> 00:40:03.640 align:start position:0% kind of enough base functionality that 00:40:03.640 --> 00:40:08.100 align:start position:0% kind of enough base functionality that people<00:40:03.700> want<00:40:04.240> then<00:40:06.450> you<00:40:07.450> can<00:40:07.480> see<00:40:07.810> more<00:40:08.020> you 00:40:08.100 --> 00:40:08.110 align:start position:0% people want then you can see more you 00:40:08.110 --> 00:40:09.420 align:start position:0% people want then you can see more you know<00:40:08.170> we<00:40:08.290> keep<00:40:08.410> working<00:40:08.980> on<00:40:09.100> those<00:40:09.250> other 00:40:09.420 --> 00:40:09.430 align:start position:0% know we keep working on those other 00:40:09.430 --> 00:40:11.400 align:start position:0% know we keep working on those other things<00:40:09.700> so<00:40:10.210> I<00:40:10.240> do<00:40:10.540> feel<00:40:10.840> like<00:40:10.870> we<00:40:11.200> actually 00:40:11.400 --> 00:40:11.410 align:start position:0% things so I do feel like we actually 00:40:11.410 --> 00:40:12.870 align:start position:0% things so I do feel like we actually already<00:40:11.770> have<00:40:12.130> like<00:40:12.310> a<00:40:12.370> couple<00:40:12.700> of<00:40:12.730> things 00:40:12.870 --> 00:40:12.880 align:start position:0% already have like a couple of things 00:40:12.880 --> 00:40:15.029 align:start position:0% already have like a couple of things working<00:40:13.120> with 00:40:15.029 --> 00:40:15.039 align:start position:0% working with 00:40:15.039 --> 00:40:20.049 align:start position:0% working with one<00:40:16.039> good<00:40:16.220> thing<00:40:16.279> and<00:40:16.609> that's<00:40:16.730> this<00:40:16.970> one<00:40:19.059> yeah 00:40:20.049 --> 00:40:20.059 align:start position:0% one good thing and that's this one yeah 00:40:20.059 --> 00:40:23.769 align:start position:0% one good thing and that's this one yeah yeah<00:40:20.690> I<00:40:21.049> think<00:40:21.200> like<00:40:21.470> making<00:40:22.130> if<00:40:22.519> one<00:40:22.880> like<00:40:23.480> be 00:40:23.769 --> 00:40:23.779 align:start position:0% yeah I think like making if one like be 00:40:23.779 --> 00:40:27.220 align:start position:0% yeah I think like making if one like be a<00:40:23.809> popular<00:40:24.589> like<00:40:24.890> making<00:40:25.849> eath<00:40:26.059> one<00:40:26.329> plus<00:40:26.869> like 00:40:27.220 --> 00:40:27.230 align:start position:0% a popular like making eath one plus like 00:40:27.230 --> 00:40:29.259 align:start position:0% a popular like making eath one plus like simple<00:40:27.680> cross<00:40:27.920> harbor<00:40:28.339> scene<00:40:28.519> passing<00:40:29.000> like 00:40:29.259 --> 00:40:29.269 align:start position:0% simple cross harbor scene passing like 00:40:29.269 --> 00:40:30.940 align:start position:0% simple cross harbor scene passing like be<00:40:29.480> a<00:40:29.510> popular<00:40:29.990> execution<00:40:30.500> target<00:40:30.769> at<00:40:30.859> the 00:40:30.940 --> 00:40:30.950 align:start position:0% be a popular execution target at the 00:40:30.950 --> 00:40:34.660 align:start position:0% be a popular execution target at the beginning<00:40:31.869> it<00:40:32.869> seems<00:40:33.200> to<00:40:33.410> be<00:40:33.559> kind<00:40:33.890> of<00:40:34.099> fairly 00:40:34.660 --> 00:40:34.670 align:start position:0% beginning it seems to be kind of fairly 00:40:34.670 --> 00:40:36.870 align:start position:0% beginning it seems to be kind of fairly Network<00:40:35.450> effects<00:40:35.779> preserving<00:40:36.349> a 00:40:36.870 --> 00:40:36.880 align:start position:0% Network effects preserving a 00:40:36.880 --> 00:40:39.630 align:start position:0% Network effects preserving a conversation<00:40:37.880> with<00:40:37.970> some<00:40:38.150> mystery<00:40:38.510> teams<00:40:38.839> and 00:40:39.630 --> 00:40:39.640 align:start position:0% conversation with some mystery teams and 00:40:39.640 --> 00:40:43.180 align:start position:0% conversation with some mystery teams and suggesting<00:40:40.960> depth<00:40:41.960> and<00:40:42.589> the<00:40:42.680> context<00:40:43.010> people 00:40:43.180 --> 00:40:43.190 align:start position:0% suggesting depth and the context people 00:40:43.190 --> 00:40:46.180 align:start position:0% suggesting depth and the context people wanted<00:40:43.490> me<00:40:43.670> he<00:40:43.730> is<00:40:44.029> like<00:40:44.269> still<00:40:44.750> like<00:40:45.190> crucial 00:40:46.180 --> 00:40:46.190 align:start position:0% wanted me he is like still like crucial 00:40:46.190 --> 00:40:48.099 align:start position:0% wanted me he is like still like crucial portion<00:40:46.670> or<00:40:46.789> some<00:40:47.059> diversion<00:40:47.569> or<00:40:47.690> iteration 00:40:48.099 --> 00:40:48.109 align:start position:0% portion or some diversion or iteration 00:40:48.109 --> 00:40:49.509 align:start position:0% portion or some diversion or iteration cousin<00:40:48.500> is<00:40:48.589> a<00:40:48.619> crucial<00:40:49.010> portion<00:40:49.339> of<00:40:49.430> the 00:40:49.509 --> 00:40:49.519 align:start position:0% cousin is a crucial portion of the 00:40:49.519 --> 00:40:54.579 align:start position:0% cousin is a crucial portion of the stoppers<00:40:49.880> that<00:40:50.710> it<00:40:51.710> is<00:40:52.130> that<00:40:53.200> view<00:40:54.200> into<00:40:54.500> the 00:40:54.579 --> 00:40:54.589 align:start position:0% stoppers that it is that view into the 00:40:54.589 --> 00:40:56.230 align:start position:0% stoppers that it is that view into the state<00:40:54.829> that<00:40:55.099> you<00:40:55.369> and<00:40:55.519> I<00:40:55.549> see<00:40:55.700> immediately 00:40:56.230 --> 00:40:56.240 align:start position:0% state that you and I see immediately 00:40:56.240 --> 00:40:58.299 align:start position:0% state that you and I see immediately well<00:40:57.140> there's<00:40:57.319> a<00:40:57.440> lot<00:40:57.589> of<00:40:57.740> the<00:40:57.920> system 00:40:58.299 --> 00:40:58.309 align:start position:0% well there's a lot of the system 00:40:58.309 --> 00:40:59.680 align:start position:0% well there's a lot of the system basically<00:40:58.579> a<00:40:58.700> lot<00:40:58.940> of<00:40:59.059> things<00:40:59.269> about<00:40:59.420> each<00:40:59.660> one 00:40:59.680 --> 00:40:59.690 align:start position:0% basically a lot of things about each one 00:40:59.690 --> 00:41:02.289 align:start position:0% basically a lot of things about each one points<00:41:00.289> that<00:41:00.410> are<00:41:00.500> like<00:41:00.940> outside<00:41:01.940> of<00:41:01.970> the<00:41:02.150> he 00:41:02.289 --> 00:41:02.299 align:start position:0% points that are like outside of the he 00:41:02.299 --> 00:41:04.180 align:start position:0% points that are like outside of the he specification<00:41:03.049> like<00:41:03.230> one<00:41:03.500> thing<00:41:03.650> that<00:41:03.859> having 00:41:04.180 --> 00:41:04.190 align:start position:0% specification like one thing that having 00:41:04.190 --> 00:41:05.440 align:start position:0% specification like one thing that having there's<00:41:04.400> obviously<00:41:04.940> like<00:41:05.180> those 00:41:05.440 --> 00:41:05.450 align:start position:0% there's obviously like those 00:41:05.450 --> 00:41:08.109 align:start position:0% there's obviously like those transactions<00:41:06.109> and<00:41:07.010> laying<00:41:07.369> rights<00:41:07.670> they<00:41:07.940> have 00:41:08.109 --> 00:41:08.119 align:start position:0% transactions and laying rights they have 00:41:08.119 --> 00:41:10.210 align:start position:0% transactions and laying rights they have increasing<00:41:08.630> there's<00:41:09.410> actually<00:41:09.740> no<00:41:09.890> need<00:41:10.069> to 00:41:10.210 --> 00:41:10.220 align:start position:0% increasing there's actually no need to 00:41:10.220 --> 00:41:11.500 align:start position:0% increasing there's actually no need to specify<00:41:10.400> these<00:41:10.819> things<00:41:11.000> because<00:41:11.299> there's 00:41:11.500 --> 00:41:11.510 align:start position:0% specify these things because there's 00:41:11.510 --> 00:41:13.599 align:start position:0% specify these things because there's always<00:41:11.779> better<00:41:12.109> ways<00:41:12.319> to<00:41:12.349> like<00:41:12.950> them<00:41:13.339> in<00:41:13.460> any 00:41:13.599 --> 00:41:13.609 align:start position:0% always better ways to like them in any 00:41:13.609 --> 00:41:15.220 align:start position:0% always better ways to like them in any kind<00:41:13.880> of<00:41:14.000> software<00:41:14.299> and<00:41:14.450> this<00:41:14.690> is<00:41:14.750> just<00:41:14.869> like<00:41:15.200> a 00:41:15.220 --> 00:41:15.230 align:start position:0% kind of software and this is just like a 00:41:15.230 --> 00:41:17.380 align:start position:0% kind of software and this is just like a software<00:41:15.710> problem<00:41:15.920> it<00:41:16.279> is<00:41:16.400> moving<00:41:17.240> in<00:41:17.359> a 00:41:17.380 --> 00:41:17.390 align:start position:0% software problem it is moving in a 00:41:17.390 --> 00:41:19.779 align:start position:0% software problem it is moving in a circle<00:41:17.869> it's<00:41:18.049> really<00:41:18.259> beautiful<00:41:18.769> that<00:41:19.009> you 00:41:19.779 --> 00:41:19.789 align:start position:0% circle it's really beautiful that you 00:41:19.789 --> 00:41:21.400 align:start position:0% circle it's really beautiful that you took<00:41:20.210> the<00:41:20.359> step<00:41:20.599> and<00:41:20.750> actually<00:41:20.869> like<00:41:21.170> so<00:41:21.349> to 00:41:21.400 --> 00:41:21.410 align:start position:0% took the step and actually like so to 00:41:21.410 --> 00:41:22.839 align:start position:0% took the step and actually like so to say<00:41:21.650> that<00:41:21.890> you<00:41:21.920> know<00:41:22.130> this<00:41:22.279> is<00:41:22.460> not<00:41:22.640> our 00:41:22.839 --> 00:41:22.849 align:start position:0% say that you know this is not our 00:41:22.849 --> 00:41:24.510 align:start position:0% say that you know this is not our problem<00:41:22.960> with 00:41:24.510 --> 00:41:24.520 align:start position:0% problem with 00:41:24.520 --> 00:41:27.270 align:start position:0% problem with dougies<00:41:25.300> it<00:41:25.840> was<00:41:25.960> just<00:41:26.140> it<00:41:26.530> just<00:41:26.560> means<00:41:26.920> that<00:41:27.040> I 00:41:27.270 --> 00:41:27.280 align:start position:0% dougies it was just it just means that I 00:41:27.280 --> 00:41:28.350 align:start position:0% dougies it was just it just means that I could<00:41:27.340> never<00:41:27.640> get<00:41:27.850> someone<00:41:28.150> else<00:41:28.270> to 00:41:28.350 --> 00:41:28.360 align:start position:0% could never get someone else to 00:41:28.360 --> 00:41:31.260 align:start position:0% could never get someone else to someone's<00:41:29.080> problem<00:41:29.440> yeah<00:41:29.650> yeah<00:41:30.150> we<00:41:31.150> do 00:41:31.260 --> 00:41:31.270 align:start position:0% someone's problem yeah yeah we do 00:41:31.270 --> 00:41:32.790 align:start position:0% someone's problem yeah yeah we do actually<00:41:31.450> have<00:41:31.660> like<00:41:31.930> a<00:41:31.990> pretty<00:41:32.260> good<00:41:32.440> idea<00:41:32.500> of 00:41:32.790 --> 00:41:32.800 align:start position:0% actually have like a pretty good idea of 00:41:32.800 --> 00:41:34.290 align:start position:0% actually have like a pretty good idea of like<00:41:33.010> what<00:41:33.040> that<00:41:33.310> problem<00:41:33.520> is<00:41:33.700> because<00:41:34.120> what 00:41:34.290 --> 00:41:34.300 align:start position:0% like what that problem is because what 00:41:34.300 --> 00:41:35.520 align:start position:0% like what that problem is because what we've<00:41:34.480> never<00:41:34.600> been<00:41:34.810> doing<00:41:35.080> it<00:41:35.200> like<00:41:35.320> we've 00:41:35.520 --> 00:41:35.530 align:start position:0% we've never been doing it like we've 00:41:35.530 --> 00:41:37.290 align:start position:0% we've never been doing it like we've been<00:41:35.680> living<00:41:35.830> inside<00:41:36.190> this<00:41:36.370> one<00:41:36.640> specific<00:41:37.180> to 00:41:37.290 --> 00:41:37.300 align:start position:0% been living inside this one specific to 00:41:37.300 --> 00:41:39.330 align:start position:0% been living inside this one specific to eat<00:41:37.510> at<00:41:37.660> least<00:41:37.840> before<00:41:38.050> right<00:41:38.410> now<00:41:38.560> so<00:41:39.190> it's 00:41:39.330 --> 00:41:39.340 align:start position:0% eat at least before right now so it's 00:41:39.340 --> 00:41:40.770 align:start position:0% eat at least before right now so it's kind<00:41:39.520> of<00:41:39.580> like<00:41:39.700> we<00:41:39.880> already<00:41:40.030> know<00:41:40.240> that<00:41:40.360> what's 00:41:40.770 --> 00:41:40.780 align:start position:0% kind of like we already know that what's 00:41:40.780 --> 00:41:47.550 align:start position:0% kind of like we already know that what's going<00:41:40.930> to<00:41:40.960> happen<00:41:44.460> yes<00:41:45.460> if<00:41:46.360> that<00:41:46.420> model<00:41:47.290> is 00:41:47.550 --> 00:41:47.560 align:start position:0% going to happen yes if that model is 00:41:47.560 --> 00:41:52.109 align:start position:0% going to happen yes if that model is based<00:41:47.860> on<00:41:47.980> the<00:41:48.250> problem<00:41:48.940> here 00:41:52.109 --> 00:41:52.119 align:start position:0% 00:41:52.119 --> 00:41:54.700 align:start position:0% I 00:41:54.700 --> 00:41:54.710 align:start position:0% 00:41:54.710 --> 00:41:57.340 align:start position:0% you'd<00:41:55.190> like<00:41:55.370> is<00:41:55.520> being<00:41:55.760> used<00:41:55.940> for<00:41:56.030> FSU<00:41:56.390> yeah<00:41:56.990> so 00:41:57.340 --> 00:41:57.350 align:start position:0% you'd like is being used for FSU yeah so 00:41:57.350 --> 00:42:00.970 align:start position:0% you'd like is being used for FSU yeah so you<00:41:57.410> still<00:41:58.090> divide<00:41:59.090> slots<00:41:59.840> and<00:41:59.990> 80<00:42:00.170> bucks<00:42:00.410> all 00:42:00.970 --> 00:42:00.980 align:start position:0% you still divide slots and 80 bucks all 00:42:00.980 --> 00:42:03.670 align:start position:0% you still divide slots and 80 bucks all validators<00:42:01.760> are<00:42:02.360> called<00:42:02.600> upon<00:42:02.750> to<00:42:02.870> do<00:42:03.110> to 00:42:03.670 --> 00:42:03.680 align:start position:0% validators are called upon to do to 00:42:03.680 --> 00:42:07.660 align:start position:0% validators are called upon to do to attest<00:42:04.010> once<00:42:04.430> per<00:42:04.880> that<00:42:05.120> unit<00:42:05.660> if<00:42:05.750> you<00:42:05.870> pump<00:42:06.670> to 00:42:07.660 --> 00:42:07.670 align:start position:0% attest once per that unit if you pump to 00:42:07.670 --> 00:42:09.430 align:start position:0% attest once per that unit if you pump to go<00:42:07.820> cross-linked<00:42:08.390> but<00:42:08.570> also<00:42:08.720> to<00:42:08.990> vote<00:42:09.200> on<00:42:09.410> that 00:42:09.430 --> 00:42:09.440 align:start position:0% go cross-linked but also to vote on that 00:42:09.440 --> 00:42:12.100 align:start position:0% go cross-linked but also to vote on that management<00:42:09.890> so<00:42:10.520> the<00:42:11.090> cycle<00:42:11.510> of<00:42:11.540> effigy<00:42:11.990> is 00:42:12.100 --> 00:42:12.110 align:start position:0% management so the cycle of effigy is 00:42:12.110 --> 00:42:14.680 align:start position:0% management so the cycle of effigy is still<00:42:12.350> like<00:42:12.560> large<00:42:12.830> units<00:42:13.280> of<00:42:13.690> rather 00:42:14.680 --> 00:42:14.690 align:start position:0% still like large units of rather 00:42:14.690 --> 00:42:17.080 align:start position:0% still like large units of rather than<00:42:15.460> the<00:42:16.460> other<00:42:16.640> thing<00:42:16.730> it<00:42:16.820> does<00:42:16.850> is 00:42:17.080 --> 00:42:17.090 align:start position:0% than the other thing it does is 00:42:17.090 --> 00:42:18.520 align:start position:0% than the other thing it does is essentially<00:42:17.450> it<00:42:17.630> takes<00:42:17.750> that<00:42:17.960> shuffling<00:42:18.440> of 00:42:18.520 --> 00:42:18.530 align:start position:0% essentially it takes that shuffling of 00:42:18.530 --> 00:42:22.360 align:start position:0% essentially it takes that shuffling of committees<00:42:18.920> and<00:42:19.400> rather<00:42:19.580> than<00:42:20.350> having<00:42:21.350> a<00:42:21.800> set 00:42:22.360 --> 00:42:22.370 align:start position:0% committees and rather than having a set 00:42:22.370 --> 00:42:23.680 align:start position:0% committees and rather than having a set of<00:42:22.490> shards<00:42:22.760> a<00:42:22.820> set<00:42:23.000> of<00:42:23.090> shards<00:42:23.360> instead<00:42:23.600> of 00:42:23.680 --> 00:42:23.690 align:start position:0% of shards a set of shards instead of 00:42:23.690 --> 00:42:25.510 align:start position:0% of shards a set of shards instead of charts<00:42:23.960> the<00:42:24.170> different<00:42:24.440> set<00:42:24.560> of<00:42:24.650> charts<00:42:24.980> per 00:42:25.510 --> 00:42:25.520 align:start position:0% charts the different set of charts per 00:42:25.520 --> 00:42:27.750 align:start position:0% charts the different set of charts per slot<00:42:25.760> is<00:42:26.030> just<00:42:26.240> the<00:42:26.450> same<00:42:26.630> chart<00:42:26.960> each<00:42:27.410> slide 00:42:27.750 --> 00:42:27.760 align:start position:0% slot is just the same chart each slide 00:42:27.760 --> 00:42:32.020 align:start position:0% slot is just the same chart each slide address<00:42:28.760> the<00:42:28.910> mechanics<00:42:29.330> repair<00:42:30.340> so<00:42:31.340> actually 00:42:32.020 --> 00:42:32.030 align:start position:0% address the mechanics repair so actually 00:42:32.030 --> 00:42:34.120 align:start position:0% address the mechanics repair so actually an<00:42:32.780> exercise<00:42:33.110> right<00:42:33.380> now<00:42:33.440> essentially<00:42:33.980> just 00:42:34.120 --> 00:42:34.130 align:start position:0% an exercise right now essentially just 00:42:34.130 --> 00:42:35.950 align:start position:0% an exercise right now essentially just like<00:42:34.310> removing<00:42:35.060> the<00:42:35.270> notion<00:42:35.570> of<00:42:35.660> a<00:42:35.750> crossing 00:42:35.950 --> 00:42:35.960 align:start position:0% like removing the notion of a crossing 00:42:35.960 --> 00:42:39.910 align:start position:0% like removing the notion of a crossing of<00:42:36.320> a<00:42:36.500> zero<00:42:37.060> so<00:42:38.060> that<00:42:38.240> space<00:42:38.870> zero<00:42:39.170> in<00:42:39.410> terms<00:42:39.710> of 00:42:39.910 --> 00:42:39.920 align:start position:0% of a zero so that space zero in terms of 00:42:39.920 --> 00:42:42.460 align:start position:0% of a zero so that space zero in terms of for<00:42:40.640> choice<00:42:40.880> in<00:42:41.210> terms<00:42:41.360> of<00:42:41.600> the<00:42:41.840> validate<00:42:42.350> with 00:42:42.460 --> 00:42:42.470 align:start position:0% for choice in terms of the validate with 00:42:42.470 --> 00:42:44.620 align:start position:0% for choice in terms of the validate with validators<00:42:43.010> doing<00:42:43.430> in<00:42:43.670> terms<00:42:43.820> of<00:42:44.000> like<00:42:44.180> voting 00:42:44.620 --> 00:42:44.630 align:start position:0% validators doing in terms of like voting 00:42:44.630 --> 00:42:47.620 align:start position:0% validators doing in terms of like voting on<00:42:44.750> it's<00:42:44.930> all<00:42:46.300> barristers 00:42:47.620 --> 00:42:47.630 align:start position:0% on it's all barristers 00:42:47.630 --> 00:42:50.920 align:start position:0% on it's all barristers we<00:42:48.380> have<00:42:48.530> final<00:42:48.890> questions<00:42:49.600> one<00:42:50.600> limit 00:42:50.920 --> 00:42:50.930 align:start position:0% we have final questions one limit 00:42:50.930 --> 00:42:55.519 align:start position:0% we have final questions one limit communication 00:42:55.519 --> 00:42:55.529 align:start position:0% 00:42:55.529 --> 00:42:58.799 align:start position:0% my<00:42:56.529> being<00:42:57.039> answer<00:42:57.519> to<00:42:57.759> this<00:42:57.969> would<00:42:58.269> be<00:42:58.479> it<00:42:58.630> that 00:42:58.799 --> 00:42:58.809 align:start position:0% my being answer to this would be it that 00:42:58.809 --> 00:43:00.900 align:start position:0% my being answer to this would be it that like<00:42:59.079> then<00:42:59.679> you<00:42:59.890> would<00:43:00.069> have<00:43:00.279> to<00:43:00.519> deal<00:43:00.880> with 00:43:00.900 --> 00:43:00.910 align:start position:0% like then you would have to deal with 00:43:00.910 --> 00:43:03.689 align:start position:0% like then you would have to deal with wipes<00:43:01.539> easy<00:43:02.259> level<00:43:02.499> reenters<00:43:03.189> and<00:43:03.429> stuff 00:43:03.689 --> 00:43:03.699 align:start position:0% wipes easy level reenters and stuff 00:43:03.699 --> 00:43:05.219 align:start position:0% wipes easy level reenters and stuff which<00:43:03.999> just<00:43:04.269> seems<00:43:04.539> like<00:43:04.809> weird<00:43:05.109> and 00:43:05.219 --> 00:43:05.229 align:start position:0% which just seems like weird and 00:43:05.229 --> 00:43:07.589 align:start position:0% which just seems like weird and complicated<00:43:05.410> but<00:43:06.309> like<00:43:06.939> if<00:43:07.089> people<00:43:07.329> want<00:43:07.509> me 00:43:07.589 --> 00:43:07.599 align:start position:0% complicated but like if people want me 00:43:07.599 --> 00:43:12.199 align:start position:0% complicated but like if people want me to<00:43:07.719> do<00:43:07.869> it<00:43:08.019> is<00:43:08.589> the<00:43:08.829> like<00:43:09.609> the<00:43:09.789> post<00:43:10.089> state 00:43:12.199 --> 00:43:12.209 align:start position:0% to do it is the like the post state 00:43:12.209 --> 00:43:14.219 align:start position:0% to do it is the like the post state execution<00:43:13.209> would<00:43:13.299> then<00:43:13.449> be<00:43:13.630> like<00:43:13.809> two 00:43:14.219 --> 00:43:14.229 align:start position:0% execution would then be like two 00:43:14.229 --> 00:43:18.390 align:start position:0% execution would then be like two favorites<00:43:16.319> well<00:43:17.319> I<00:43:17.349> guess<00:43:17.589> the<00:43:17.769> idea<00:43:17.919> would<00:43:18.249> be 00:43:18.390 --> 00:43:18.400 align:start position:0% favorites well I guess the idea would be 00:43:18.400 --> 00:43:20.429 align:start position:0% favorites well I guess the idea would be like<00:43:18.699> right<00:43:18.910> now<00:43:19.089> like<00:43:19.390> if<00:43:19.569> these<00:43:19.869> cans<00:43:20.169> call 00:43:20.429 --> 00:43:20.439 align:start position:0% like right now like if these cans call 00:43:20.439 --> 00:43:21.959 align:start position:0% like right now like if these cans call each<00:43:20.589> other<00:43:20.739> it's<00:43:21.009> more<00:43:21.219> like<00:43:21.429> you<00:43:21.549> have<00:43:21.729> like 00:43:21.959 --> 00:43:21.969 align:start position:0% each other it's more like you have like 00:43:21.969 --> 00:43:24.449 align:start position:0% each other it's more like you have like a<00:43:22.179> and<00:43:22.449> then<00:43:22.539> B<00:43:22.599> and<00:43:22.809> then<00:43:23.019> C<00:43:23.109> it<00:43:23.499> but<00:43:23.979> then<00:43:24.160> here 00:43:24.449 --> 00:43:24.459 align:start position:0% a and then B and then C it but then here 00:43:24.459 --> 00:43:26.669 align:start position:0% a and then B and then C it but then here you<00:43:24.609> would<00:43:24.759> have<00:43:24.910> like<00:43:25.179> a<00:43:25.359> and<00:43:25.809> then<00:43:26.349> you<00:43:26.499> might 00:43:26.669 --> 00:43:26.679 align:start position:0% you would have like a and then you might 00:43:26.679 --> 00:43:29.009 align:start position:0% you would have like a and then you might have<00:43:26.709> it<00:43:27.219> and<00:43:27.640> then<00:43:27.819> he<00:43:28.029> just<00:43:28.269> decides<00:43:28.689> that<00:43:28.959> oh 00:43:29.009 --> 00:43:29.019 align:start position:0% have it and then he just decides that oh 00:43:29.019 --> 00:43:31.049 align:start position:0% have it and then he just decides that oh we're<00:43:29.289> gonna<00:43:29.380> call<00:43:29.679> a<00:43:29.709> inside<00:43:30.189> a<00:43:30.219> CRNA<00:43:30.669> decide 00:43:31.049 --> 00:43:31.059 align:start position:0% we're gonna call a inside a CRNA decide 00:43:31.059 --> 00:43:32.759 align:start position:0% we're gonna call a inside a CRNA decide so<00:43:31.299> we're<00:43:31.449> gonna<00:43:31.539> call<00:43:31.749> the<00:43:31.989> inside<00:43:32.319> of<00:43:32.469> here 00:43:32.759 --> 00:43:32.769 align:start position:0% so we're gonna call the inside of here 00:43:32.769 --> 00:43:35.159 align:start position:0% so we're gonna call the inside of here and<00:43:33.039> then<00:43:33.849> he<00:43:34.119> ends<00:43:34.419> and<00:43:34.569> the<00:43:34.630> dance<00:43:34.900> and<00:43:35.109> the 00:43:35.159 --> 00:43:35.169 align:start position:0% and then he ends and the dance and the 00:43:35.169 --> 00:43:37.019 align:start position:0% and then he ends and the dance and the pants<00:43:35.469> again<00:43:35.679> then<00:43:36.279> you<00:43:36.400> have<00:43:36.549> like<00:43:36.759> C<00:43:36.999> and 00:43:37.019 --> 00:43:37.029 align:start position:0% pants again then you have like C and 00:43:37.029 --> 00:43:41.279 align:start position:0% pants again then you have like C and then<00:43:37.390> B<00:43:37.419> over<00:43:37.809> here<00:43:38.549> like<00:43:39.569> there<00:43:40.569> is<00:43:40.719> benefits 00:43:41.279 --> 00:43:41.289 align:start position:0% then B over here like there is benefits 00:43:41.289 --> 00:43:42.900 align:start position:0% then B over here like there is benefits but<00:43:41.589> legs<00:43:41.799> you<00:43:42.039> can<00:43:42.189> see<00:43:42.400> how<00:43:42.549> this<00:43:42.699> is<00:43:42.880> a 00:43:42.900 --> 00:43:42.910 align:start position:0% but legs you can see how this is a 00:43:42.910 --> 00:43:46.829 align:start position:0% but legs you can see how this is a potential<00:43:43.269> a<00:43:43.509> security<00:43:43.959> nightmare<00:43:45.599> even<00:43:46.599> if 00:43:46.829 --> 00:43:46.839 align:start position:0% potential a security nightmare even if 00:43:46.839 --> 00:43:48.239 align:start position:0% potential a security nightmare even if you<00:43:46.989> don't<00:43:47.229> have<00:43:47.380> that<00:43:47.559> secrets 00:43:48.239 --> 00:43:48.249 align:start position:0% you don't have that secrets 00:43:48.249 --> 00:43:50.200 align:start position:0% you don't have that secrets could<00:43:48.519> be 00:43:50.200 --> 00:43:50.210 align:start position:0% could be 00:43:50.210 --> 00:43:52.870 align:start position:0% could be in<00:43:50.570> the<00:43:50.750> same<00:43:50.960> shark<00:43:51.230> lung<00:43:51.500> and<00:43:51.890> if<00:43:52.130> they<00:43:52.820> don't 00:43:52.870 --> 00:43:52.880 align:start position:0% in the same shark lung and if they don't 00:43:52.880 --> 00:43:54.820 align:start position:0% in the same shark lung and if they don't you<00:43:53.000> know<00:43:53.090> so<00:43:53.780> what<00:43:54.050> are<00:43:54.260> the<00:43:54.350> same<00:43:54.560> part 00:43:54.820 --> 00:43:54.830 align:start position:0% you know so what are the same part 00:43:54.830 --> 00:43:56.520 align:start position:0% you know so what are the same part everyone<00:43:55.820> first 00:43:56.520 --> 00:43:56.530 align:start position:0% everyone first 00:43:56.530 --> 00:43:59.290 align:start position:0% everyone first yep<00:43:57.800> so<00:43:57.980> one<00:43:58.160> thing<00:43:58.340> we<00:43:58.460> can't<00:43:58.700> do<00:43:58.880> is<00:43:58.910> win<00:43:59.270> I 00:43:59.290 --> 00:43:59.300 align:start position:0% yep so one thing we can't do is win I 00:43:59.300 --> 00:44:02.140 align:start position:0% yep so one thing we can't do is win I think<00:43:59.450> we<00:43:59.900> can<00:44:00.170> kind<00:44:00.500> of<00:44:00.650> allow<00:44:01.340> a<00:44:01.760> temp<00:44:01.970> data 00:44:02.140 --> 00:44:02.150 align:start position:0% think we can kind of allow a temp data 00:44:02.150 --> 00:44:04.360 align:start position:0% think we can kind of allow a temp data free<00:44:02.660> like<00:44:02.900> basically<00:44:03.260> free<00:44:03.590> receipt<00:44:03.920> passing 00:44:04.360 --> 00:44:04.370 align:start position:0% free like basically free receipt passing 00:44:04.370 --> 00:44:06.970 align:start position:0% free like basically free receipt passing between<00:44:05.020> from<00:44:06.020> what<00:44:06.230> executioner's<00:44:06.860> of 00:44:06.970 --> 00:44:06.980 align:start position:0% between from what executioner's of 00:44:06.980 --> 00:44:08.650 align:start position:0% between from what executioner's of second<00:44:07.280> ones<00:44:07.490> I<00:44:07.640> think<00:44:07.700> that's<00:44:08.000> uh 00:44:08.650 --> 00:44:08.660 align:start position:0% second ones I think that's uh 00:44:08.660 --> 00:44:11.500 align:start position:0% second ones I think that's uh don't<00:44:09.350> do<00:44:09.590> that<00:44:09.800> you<00:44:10.100> can<00:44:10.310> parallelize<00:44:10.940> so 00:44:11.500 --> 00:44:11.510 align:start position:0% don't do that you can parallelize so 00:44:11.510 --> 00:44:13.480 align:start position:0% don't do that you can parallelize so there<00:44:11.690> is<00:44:11.750> actually<00:44:12.200> one<00:44:12.230> very<00:44:12.740> good<00:44:12.860> reason 00:44:13.480 --> 00:44:13.490 align:start position:0% there is actually one very good reason 00:44:13.490 --> 00:44:16.330 align:start position:0% there is actually one very good reason to<00:44:13.520> allow<00:44:13.960> receive<00:44:14.960> passing<00:44:15.500> between<00:44:15.740> kind<00:44:16.220> of 00:44:16.330 --> 00:44:16.340 align:start position:0% to allow receive passing between kind of 00:44:16.340 --> 00:44:18.370 align:start position:0% to allow receive passing between kind of separate<00:44:16.670> institutions<00:44:16.910> of<00:44:17.450> any<00:44:17.630> EU<00:44:17.900> which<00:44:18.170> is 00:44:18.370 --> 00:44:18.380 align:start position:0% separate institutions of any EU which is 00:44:18.380 --> 00:44:21.430 align:start position:0% separate institutions of any EU which is basically<00:44:18.830> that<00:44:18.980> if<00:44:19.820> one<00:44:20.300> updates<00:44:20.870> the<00:44:21.080> market 00:44:21.430 --> 00:44:21.440 align:start position:0% basically that if one updates the market 00:44:21.440 --> 00:44:23.410 align:start position:0% basically that if one updates the market area<00:44:21.590> that<00:44:21.980> the<00:44:22.220> other<00:44:22.400> might<00:44:22.730> have<00:44:22.760> witnesses 00:44:23.410 --> 00:44:23.420 align:start position:0% area that the other might have witnesses 00:44:23.420 --> 00:44:24.730 align:start position:0% area that the other might have witnesses that<00:44:23.480> are<00:44:23.660> all<00:44:23.870> they<00:44:24.050> might<00:44:24.320> have<00:44:24.470> to<00:44:24.590> update 00:44:24.730 --> 00:44:24.740 align:start position:0% that are all they might have to update 00:44:24.740 --> 00:44:30.580 align:start position:0% that are all they might have to update them<00:44:27.940> generally<00:44:28.940> kind<00:44:29.180> of<00:44:29.330> it's<00:44:30.200> absolutely 00:44:30.580 --> 00:44:30.590 align:start position:0% them generally kind of it's absolutely 00:44:30.590 --> 00:44:35.880 align:start position:0% them generally kind of it's absolutely good<00:44:30.770> for<00:44:32.710> elimination 00:44:35.880 --> 00:44:35.890 align:start position:0% 00:44:35.890 --> 00:44:40.210 align:start position:0% explain<00:44:36.890> oh<00:44:37.430> you<00:44:38.120> had<00:44:38.590> well<00:44:39.590> this<00:44:39.710> is<00:44:39.860> like<00:44:40.040> if 00:44:40.210 --> 00:44:40.220 align:start position:0% explain oh you had well this is like if 00:44:40.220 --> 00:44:42.640 align:start position:0% explain oh you had well this is like if you<00:44:40.250> have<00:44:40.370> new<00:44:40.940> ability<00:44:41.540> to<00:44:41.780> kind<00:44:42.440> of 00:44:42.640 --> 00:44:42.650 align:start position:0% you have new ability to kind of 00:44:42.650 --> 00:44:44.440 align:start position:0% you have new ability to kind of communicate<00:44:42.980> between<00:44:43.490> different<00:44:44.000> is<00:44:44.120> that 00:44:44.440 --> 00:44:44.450 align:start position:0% communicate between different is that 00:44:44.450 --> 00:44:45.640 align:start position:0% communicate between different is that you<00:44:44.540> would<00:44:44.690> just<00:44:44.870> know<00:44:44.960> excited<00:44:45.440> it<00:44:45.590> was 00:44:45.640 --> 00:44:45.650 align:start position:0% you would just know excited it was 00:44:45.650 --> 00:44:47.110 align:start position:0% you would just know excited it was single<00:44:45.950> yeah<00:44:46.220> then<00:44:46.400> you<00:44:46.490> could<00:44:46.610> just<00:44:46.820> say<00:44:46.940> what 00:44:47.110 --> 00:44:47.120 align:start position:0% single yeah then you could just say what 00:44:47.120 --> 00:44:48.580 align:start position:0% single yeah then you could just say what one<00:44:47.360> thread<00:44:47.630> brought<00:44:47.840> us<00:44:47.930> all<00:44:48.020> the<00:44:48.170> a<00:44:48.200> what 00:44:48.580 --> 00:44:48.590 align:start position:0% one thread brought us all the a what 00:44:48.590 --> 00:44:50.410 align:start position:0% one thread brought us all the a what thread<00:44:48.830> runs<00:44:49.070> all<00:44:49.250> to<00:44:49.370> be<00:44:49.520> one<00:44:49.760> thread<00:44:50.000> runs<00:44:50.240> on 00:44:50.410 --> 00:44:50.420 align:start position:0% thread runs all to be one thread runs on 00:44:50.420 --> 00:44:53.560 align:start position:0% thread runs all to be one thread runs on the<00:44:50.510> CI<00:44:50.720> that<00:44:50.930> you<00:44:50.990> had<00:44:51.140> at<00:44:51.290> the<00:44:51.380> end<00:44:52.240> yeah<00:44:53.240> like 00:44:53.560 --> 00:44:53.570 align:start position:0% the CI that you had at the end yeah like 00:44:53.570 --> 00:44:56.770 align:start position:0% the CI that you had at the end yeah like that<00:44:53.720> might<00:44:53.900> even<00:44:54.050> be<00:44:54.200> here<00:44:54.670> good<00:44:55.780> because 00:44:56.770 --> 00:44:56.780 align:start position:0% that might even be here good because 00:44:56.780 --> 00:45:03.430 align:start position:0% that might even be here good because that<00:44:57.110> way<00:44:57.470> we<00:44:57.860> would<00:44:58.100> be<00:45:00.130> able<00:45:01.130> to<00:45:02.020> get<00:45:03.020> watched 00:45:03.430 --> 00:45:03.440 align:start position:0% that way we would be able to get watched 00:45:03.440 --> 00:45:06.340 align:start position:0% that way we would be able to get watched produced<00:45:04.040> and<00:45:04.280> verifying<00:45:04.760> the<00:45:04.970> more 00:45:06.340 --> 00:45:06.350 align:start position:0% produced and verifying the more 00:45:06.350 --> 00:45:07.960 align:start position:0% produced and verifying the more you<00:45:06.530> can<00:45:06.740> store<00:45:07.100> your<00:45:07.160> essence<00:45:07.760> in<00:45:07.940> a 00:45:07.960 --> 00:45:07.970 align:start position:0% you can store your essence in a 00:45:07.970 --> 00:45:10.450 align:start position:0% you can store your essence in a different<00:45:08.390> thank<00:45:09.290> you<00:45:09.380> kindly 00:45:10.450 --> 00:45:10.460 align:start position:0% different thank you kindly 00:45:10.460 --> 00:45:17.100 align:start position:0% different thank you kindly that's<00:45:11.210> true 00:45:17.100 --> 00:45:17.110 align:start position:0% 00:45:17.110 --> 00:45:19.590 align:start position:0% right<00:45:17.710> this<00:45:17.980> is<00:45:18.160> true<00:45:18.340> so<00:45:18.910> me<00:45:19.030> me<00:45:19.090> a<00:45:19.180> lot<00:45:19.330> more 00:45:19.590 --> 00:45:19.600 align:start position:0% right this is true so me me a lot more 00:45:19.600 --> 00:45:25.320 align:start position:0% right this is true so me me a lot more communication<00:45:19.900> is<00:45:20.320> due 00:45:25.320 --> 00:45:25.330 align:start position:0% 00:45:25.330 --> 00:45:27.930 align:start position:0% we'll<00:45:25.690> use<00:45:25.720> pension 00:45:27.930 --> 00:45:27.940 align:start position:0% we'll use pension 00:45:27.940 --> 00:45:30.900 align:start position:0% we'll use pension should<00:45:28.509> ease<00:45:28.720> be<00:45:29.019> open<00:45:29.380> for<00:45:29.619> any<00:45:29.769> we<00:45:30.670> talked 00:45:30.900 --> 00:45:30.910 align:start position:0% should ease be open for any we talked 00:45:30.910 --> 00:45:33.059 align:start position:0% should ease be open for any we talked about<00:45:31.059> should<00:45:31.630> be<00:45:31.660> easy<00:45:31.869> open<00:45:32.170> for<00:45:32.289> anyone<00:45:32.559> to 00:45:33.059 --> 00:45:33.069 align:start position:0% about should be easy open for anyone to 00:45:33.069 --> 00:45:41.880 align:start position:0% about should be easy open for anyone to deploy<00:45:33.339> or<00:45:33.519> originally<00:45:37.650> put<00:45:40.500> joggers<00:45:41.500> are<00:45:41.619> no 00:45:41.880 --> 00:45:41.890 align:start position:0% deploy or originally put joggers are no 00:45:41.890 --> 00:45:47.490 align:start position:0% deploy or originally put joggers are no face<00:45:42.160> to<00:45:42.430> adjust<00:45:42.849> phase<00:45:43.359> one<00:45:45.420> so<00:45:46.420> we<00:45:46.839> thought 00:45:47.490 --> 00:45:47.500 align:start position:0% face to adjust phase one so we thought 00:45:47.500 --> 00:45:53.400 align:start position:0% face to adjust phase one so we thought about<00:45:47.769> this<00:45:48.369> I<00:45:50.339> guess<00:45:51.339> I<00:45:51.700> am<00:45:51.789> the<00:45:52.630> mean<00:45:53.079> read 00:45:53.400 --> 00:45:53.410 align:start position:0% about this I guess I am the mean read 00:45:53.410 --> 00:45:56.249 align:start position:0% about this I guess I am the mean read night<00:45:53.819> one<00:45:54.819> of<00:45:54.940> the<00:45:55.059> big<00:45:55.210> reasons<00:45:55.390> face<00:45:55.809> to<00:45:56.079> is 00:45:56.249 --> 00:45:56.259 align:start position:0% night one of the big reasons face to is 00:45:56.259 --> 00:45:57.690 align:start position:0% night one of the big reasons face to is nice<00:45:56.500> is<00:45:56.710> that<00:45:56.740> we<00:45:56.920> have<00:45:57.099> a<00:45:57.130> goaltending 00:45:57.690 --> 00:45:57.700 align:start position:0% nice is that we have a goaltending 00:45:57.700 --> 00:45:59.970 align:start position:0% nice is that we have a goaltending market<00:45:58.089> I<00:45:58.299> mean<00:45:58.660> we<00:45:58.839> could<00:45:59.079> do<00:45:59.259> like<00:45:59.410> this<00:45:59.650> 1 00:45:59.970 --> 00:45:59.980 align:start position:0% market I mean we could do like this 1 00:45:59.980 --> 00:46:02.789 align:start position:0% market I mean we could do like this 1 plus<00:46:00.250> mu<00:46:00.609> in<00:46:00.849> a<00:46:00.940> multi<00:46:01.359> you<00:46:01.509> market<00:46:01.960> but<00:46:02.559> if<00:46:02.650> we 00:46:02.789 --> 00:46:02.799 align:start position:0% plus mu in a multi you market but if we 00:46:02.799 --> 00:46:04.950 align:start position:0% plus mu in a multi you market but if we do<00:46:02.980> that<00:46:03.190> then<00:46:03.549> like<00:46:03.789> a<00:46:04.000> minimum<00:46:04.480> fee<00:46:04.690> of<00:46:04.779> like 00:46:04.950 --> 00:46:04.960 align:start position:0% do that then like a minimum fee of like 00:46:04.960 --> 00:46:06.990 align:start position:0% do that then like a minimum fee of like that<00:46:05.140> requires<00:46:05.440> you<00:46:05.680> to<00:46:05.740> be<00:46:06.069> more<00:46:06.279> diary<00:46:06.609> than 00:46:06.990 --> 00:46:07.000 align:start position:0% that requires you to be more diary than 00:46:07.000 --> 00:46:10.710 align:start position:0% that requires you to be more diary than the<00:46:07.089> old<00:46:07.240> by<00:46:07.390> smart<00:46:07.660> contracts<00:46:08.410> and<00:46:08.589> so<00:46:09.720> yeah 00:46:10.710 --> 00:46:10.720 align:start position:0% the old by smart contracts and so yeah 00:46:10.720 --> 00:46:14.220 align:start position:0% the old by smart contracts and so yeah well<00:46:11.079> I<00:46:11.410> mean<00:46:11.589> there's<00:46:11.920> two<00:46:12.450> does<00:46:13.450> this<00:46:13.660> mean 00:46:14.220 --> 00:46:14.230 align:start position:0% well I mean there's two does this mean 00:46:14.230 --> 00:46:16.109 align:start position:0% well I mean there's two does this mean that<00:46:14.259> you<00:46:14.920> know<00:46:15.039> the<00:46:15.160> the<00:46:15.190> current<00:46:15.970> keeps 00:46:16.109 --> 00:46:16.119 align:start position:0% that you know the the current keeps 00:46:16.119 --> 00:46:18.779 align:start position:0% that you know the the current keeps changing<00:46:16.390> running<00:46:16.930> in<00:46:17.019> parallel<00:46:17.170> river<00:46:17.789> you 00:46:18.779 --> 00:46:18.789 align:start position:0% changing running in parallel river you 00:46:18.789 --> 00:46:23.080 align:start position:0% changing running in parallel river you know<00:46:18.849> what<00:46:19.089> just<00:46:19.269> means<00:46:19.450> each<00:46:19.750> chain<00:46:20.049> becomes 00:46:23.080 --> 00:46:23.090 align:start position:0% 00:46:23.090 --> 00:46:28.450 align:start position:0% [Music] 00:46:28.450 --> 00:46:28.460 align:start position:0% 00:46:28.460 --> 00:46:30.829 align:start position:0% yeah<00:46:29.460> it's<00:46:29.609> no<00:46:29.730> need<00:46:29.880> to<00:46:30.000> execute<00:46:30.240> it<00:46:30.569> I<00:46:30.660> don't 00:46:30.829 --> 00:46:30.839 align:start position:0% yeah it's no need to execute it I don't 00:46:30.839 --> 00:46:32.509 align:start position:0% yeah it's no need to execute it I don't like<00:46:30.900> even<00:46:31.589> if<00:46:31.710> the<00:46:31.799> under<00:46:31.980> roll-up<00:46:32.309> chain 00:46:32.509 --> 00:46:32.519 align:start position:0% like even if the under roll-up chain 00:46:32.519 --> 00:46:34.250 align:start position:0% like even if the under roll-up chain right<00:46:32.730> from<00:46:32.970> whose<00:46:33.119> context<00:46:33.839> into<00:46:34.049> that 00:46:34.250 --> 00:46:34.260 align:start position:0% right from whose context into that 00:46:34.260 --> 00:46:36.230 align:start position:0% right from whose context into that because<00:46:34.440> proposers<00:46:35.190> need<00:46:35.460> to<00:46:35.640> know<00:46:35.819> and<00:46:36.089> what 00:46:36.230 --> 00:46:36.240 align:start position:0% because proposers need to know and what 00:46:36.240 --> 00:46:37.579 align:start position:0% because proposers need to know and what the<00:46:36.359> hell<00:46:36.480> am<00:46:36.539> I<00:46:36.630> supposed<00:46:36.690> to<00:46:37.019> include<00:46:37.260> what's 00:46:37.579 --> 00:46:37.589 align:start position:0% the hell am I supposed to include what's 00:46:37.589 --> 00:46:40.730 align:start position:0% the hell am I supposed to include what's actually<00:46:37.769> going<00:46:38.099> to<00:46:38.160> get<00:46:38.369> me<00:46:38.490> pious<00:46:39.109> but<00:46:40.109> like 00:46:40.730 --> 00:46:40.740 align:start position:0% actually going to get me pious but like 00:46:40.740 --> 00:46:43.039 align:start position:0% actually going to get me pious but like if<00:46:41.099> you<00:46:41.430> if<00:46:41.670> we<00:46:41.910> kind<00:46:42.180> of<00:46:42.269> go<00:46:42.450> roll<00:46:42.720> up<00:46:42.900> style 00:46:43.039 --> 00:46:43.049 align:start position:0% if you if we kind of go roll up style 00:46:43.049 --> 00:46:45.710 align:start position:0% if you if we kind of go roll up style that<00:46:43.880> cross-linked<00:46:44.880> committees<00:46:45.359> wouldn't 00:46:45.710 --> 00:46:45.720 align:start position:0% that cross-linked committees wouldn't 00:46:45.720 --> 00:46:47.599 align:start position:0% that cross-linked committees wouldn't would<00:46:45.930> theoretically<00:46:46.319> not<00:46:46.859> need<00:46:47.160> to<00:46:47.369> vote<00:46:47.549> on 00:46:47.599 --> 00:46:47.609 align:start position:0% would theoretically not need to vote on 00:46:47.609 --> 00:46:50.329 align:start position:0% would theoretically not need to vote on the<00:46:48.059> execution<00:46:48.900> results<00:46:49.470> which<00:46:49.799> could<00:46:50.190> be 00:46:50.329 --> 00:46:50.339 align:start position:0% the execution results which could be 00:46:50.339 --> 00:46:52.819 align:start position:0% the execution results which could be interesting<00:46:50.930> like<00:46:51.930> you<00:46:52.140> could<00:46:52.319> have<00:46:52.500> a<00:46:52.529> setup 00:46:52.819 --> 00:46:52.829 align:start position:0% interesting like you could have a setup 00:46:52.829 --> 00:46:55.430 align:start position:0% interesting like you could have a setup we're<00:46:53.269> floating<00:46:54.269> on<00:46:54.420> execution<00:46:55.019> results 00:46:55.430 --> 00:46:55.440 align:start position:0% we're floating on execution results 00:46:55.440 --> 00:46:56.809 align:start position:0% we're floating on execution results that's<00:46:55.589> kind<00:46:55.769> of<00:46:55.799> delayed<00:46:56.160> a<00:46:56.190> bit<00:46:56.279> you<00:46:56.760> know 00:46:56.809 --> 00:46:56.819 align:start position:0% that's kind of delayed a bit you know 00:46:56.819 --> 00:47:00.079 align:start position:0% that's kind of delayed a bit you know this<00:46:57.000> occurred<00:46:57.359> immediate<00:46:57.779> well<00:46:58.880> no<00:46:59.880> that's 00:47:00.079 --> 00:47:00.089 align:start position:0% this occurred immediate well no that's 00:47:00.089 --> 00:47:01.339 align:start position:0% this occurred immediate well no that's not<00:47:00.240> good<00:47:00.510> because<00:47:00.630> that<00:47:00.809> currents<00:47:01.260> like 00:47:01.339 --> 00:47:01.349 align:start position:0% not good because that currents like 00:47:01.349 --> 00:47:07.730 align:start position:0% not good because that currents like fresh<00:47:01.650> start 00:47:07.730 --> 00:47:07.740 align:start position:0% 00:47:07.740 --> 00:47:11.160 align:start position:0% why<00:47:08.740> do<00:47:08.800> we<00:47:09.010> even<00:47:09.250> need<00:47:09.370> shards<00:47:10.120> she<00:47:10.870> would<00:47:11.020> say 00:47:11.160 --> 00:47:11.170 align:start position:0% why do we even need shards she would say 00:47:11.170 --> 00:47:12.930 align:start position:0% why do we even need shards she would say my<00:47:11.320> date<00:47:11.590> availability<00:47:12.010> throughput<00:47:12.610> in<00:47:12.820> an 00:47:12.930 --> 00:47:12.940 align:start position:0% my date availability throughput in an 00:47:12.940 --> 00:47:15.180 align:start position:0% my date availability throughput in an Amish<00:47:13.240> are<00:47:13.420> consistent<00:47:14.050> with<00:47:14.380> the<00:47:14.500> ratio<00:47:14.800> go 00:47:15.180 --> 00:47:15.190 align:start position:0% Amish are consistent with the ratio go 00:47:15.190 --> 00:47:16.770 align:start position:0% Amish are consistent with the ratio go to<00:47:15.250> gate<00:47:15.640> availability<00:47:16.330> groups 00:47:16.770 --> 00:47:16.780 align:start position:0% to gate availability groups 00:47:16.780 --> 00:47:19.920 align:start position:0% to gate availability groups I<00:47:17.190> guess<00:47:18.190> because<00:47:18.460> that<00:47:18.910> kind<00:47:19.240> of<00:47:19.330> centralized 00:47:19.920 --> 00:47:19.930 align:start position:0% I guess because that kind of centralized 00:47:19.930 --> 00:47:22.110 align:start position:0% I guess because that kind of centralized proposing 00:47:22.110 --> 00:47:22.120 align:start position:0% proposing 00:47:22.120 --> 00:47:28.779 align:start position:0% proposing [Music] 00:47:28.779 --> 00:47:28.789 align:start position:0% 00:47:28.789 --> 00:47:34.890 align:start position:0% well<00:47:29.789> I<00:47:29.819> think<00:47:29.970> that<00:47:30.210> you<00:47:30.599> to<00:47:30.779> question<00:47:31.410> that 00:47:34.890 --> 00:47:34.900 align:start position:0% 00:47:34.900 --> 00:47:37.110 align:start position:0% and<00:47:35.380> if<00:47:35.530> you<00:47:35.650> say<00:47:35.830> you<00:47:35.890> have<00:47:36.100> no<00:47:36.310> execute<00:47:36.880> among 00:47:37.110 --> 00:47:37.120 align:start position:0% and if you say you have no execute among 00:47:37.120 --> 00:47:39.840 align:start position:0% and if you say you have no execute among chives 00:47:39.840 --> 00:47:39.850 align:start position:0% 00:47:39.850 --> 00:47:42.690 align:start position:0% and<00:47:40.060> their<00:47:40.330> shirts<00:47:40.690> and<00:47:40.960> you<00:47:41.650> don't<00:47:41.830> then<00:47:42.580> you 00:47:42.690 --> 00:47:42.700 align:start position:0% and their shirts and you don't then you 00:47:42.700 --> 00:47:46.940 align:start position:0% and their shirts and you don't then you don't<00:47:42.730> you<00:47:43.030> chose<00:47:43.770> this<00:47:44.770> is<00:47:44.950> well<00:47:45.670> I<00:47:45.970> guess 00:47:46.940 --> 00:47:46.950 align:start position:0% don't you chose this is well I guess 00:47:46.950 --> 00:47:50.340 align:start position:0% don't you chose this is well I guess like<00:47:47.950> when<00:47:48.520> you<00:47:48.640> put<00:47:49.000> it<00:47:49.240> like<00:47:49.540> that<00:47:49.600> they're 00:47:50.340 --> 00:47:50.350 align:start position:0% like when you put it like that they're 00:47:50.350 --> 00:47:51.870 align:start position:0% like when you put it like that they're kind<00:47:50.560> of<00:47:50.620> the<00:47:50.800> data<00:47:51.010> availability<00:47:51.460> chain 00:47:51.870 --> 00:47:51.880 align:start position:0% kind of the data availability chain 00:47:51.880 --> 00:47:53.460 align:start position:0% kind of the data availability chain proposals<00:47:52.570> like<00:47:52.780> there<00:47:52.990> has<00:47:53.080> been<00:47:53.170> a<00:47:53.230> couple 00:47:53.460 --> 00:47:53.470 align:start position:0% proposals like there has been a couple 00:47:53.470 --> 00:47:56.040 align:start position:0% proposals like there has been a couple of<00:47:53.650> them<00:47:53.860> recently<00:47:54.040> read<00:47:54.610> like<00:47:54.850> they're<00:47:55.060> it's 00:47:56.040 --> 00:47:56.050 align:start position:0% of them recently read like they're it's 00:47:56.050 --> 00:47:57.720 align:start position:0% of them recently read like they're it's an<00:47:56.170> interesting<00:47:56.380> idea<00:47:56.740> like<00:47:57.220> you<00:47:57.370> just<00:47:57.550> go 00:47:57.720 --> 00:47:57.730 align:start position:0% an interesting idea like you just go 00:47:57.730 --> 00:47:59.490 align:start position:0% an interesting idea like you just go like<00:47:57.910> political<00:47:58.540> let<00:47:58.660> someone<00:47:58.840> the<00:47:59.080> charts 00:47:59.490 --> 00:47:59.500 align:start position:0% like political let someone the charts 00:47:59.500 --> 00:48:01.560 align:start position:0% like political let someone the charts and<00:47:59.680> then<00:47:59.740> you<00:47:59.890> just<00:48:00.130> like<00:48:00.310> have<00:48:00.580> you<00:48:01.180> just<00:48:01.420> say 00:48:01.560 --> 00:48:01.570 align:start position:0% and then you just like have you just say 00:48:01.570 --> 00:48:02.820 align:start position:0% and then you just like have you just say the<00:48:01.780> whole<00:48:01.930> thing<00:48:02.140> is<00:48:02.260> supposed<00:48:02.380> to<00:48:02.620> be<00:48:02.800> a 00:48:02.820 --> 00:48:02.830 align:start position:0% the whole thing is supposed to be a 00:48:02.830 --> 00:48:08.190 align:start position:0% the whole thing is supposed to be a rollup<00:48:03.570> then<00:48:04.570> you<00:48:05.110> basically<00:48:06.480> like<00:48:07.480> the 00:48:08.190 --> 00:48:08.200 align:start position:0% rollup then you basically like the 00:48:08.200 --> 00:48:09.810 align:start position:0% rollup then you basically like the proposals<00:48:08.800> that<00:48:08.950> I've<00:48:09.070> seen<00:48:09.310> like<00:48:09.550> they<00:48:09.760> do 00:48:09.810 --> 00:48:09.820 align:start position:0% proposals that I've seen like they do 00:48:09.820 --> 00:48:13.260 align:start position:0% proposals that I've seen like they do kind<00:48:10.210> of<00:48:10.360> allow<00:48:11.050> different<00:48:11.830> people<00:48:12.730> to<00:48:12.970> submit 00:48:13.260 --> 00:48:13.270 align:start position:0% kind of allow different people to submit 00:48:13.270 --> 00:48:15.510 align:start position:0% kind of allow different people to submit like<00:48:13.810> different<00:48:14.380> bloggers<00:48:15.130> routes<00:48:15.310> in 00:48:15.510 --> 00:48:15.520 align:start position:0% like different bloggers routes in 00:48:15.520 --> 00:48:19.500 align:start position:0% like different bloggers routes in parallel<00:48:16.030> and<00:48:16.510> I<00:48:17.140> think<00:48:17.290> that<00:48:17.470> is<00:48:17.680> showing<00:48:18.510> but 00:48:19.500 --> 00:48:19.510 align:start position:0% parallel and I think that is showing but 00:48:19.510 --> 00:48:21.720 align:start position:0% parallel and I think that is showing but in<00:48:19.630> any<00:48:19.870> system<00:48:20.410> that<00:48:20.440> I<00:48:20.710> like<00:48:20.890> I<00:48:21.070> think<00:48:21.370> any 00:48:21.720 --> 00:48:21.730 align:start position:0% in any system that I like I think any 00:48:21.730 --> 00:48:23.430 align:start position:0% in any system that I like I think any system<00:48:22.180> that<00:48:22.330> doesn't<00:48:22.540> kind<00:48:22.900> of<00:48:23.080> bottleneck 00:48:23.430 --> 00:48:23.440 align:start position:0% system that doesn't kind of bottleneck 00:48:23.440 --> 00:48:25.320 align:start position:0% system that doesn't kind of bottleneck proposing<00:48:24.070> so<00:48:24.250> that<00:48:24.370> one<00:48:24.550> person<00:48:24.730> needs<00:48:25.120> to<00:48:25.180> be 00:48:25.320 --> 00:48:25.330 align:start position:0% proposing so that one person needs to be 00:48:25.330 --> 00:48:26.880 align:start position:0% proposing so that one person needs to be aware<00:48:25.540> of<00:48:25.600> everything<00:48:25.930> is<00:48:26.230> -<00:48:26.410> are<00:48:26.650> by 00:48:26.880 --> 00:48:26.890 align:start position:0% aware of everything is - are by 00:48:26.890 --> 00:48:32.850 align:start position:0% aware of everything is - are by definition<00:48:31.320> there's<00:48:32.320> definitely<00:48:32.830> a 00:48:32.850 --> 00:48:32.860 align:start position:0% definition there's definitely a 00:48:32.860 --> 00:48:34.590 align:start position:0% definition there's definitely a trade-off<00:48:33.190> between<00:48:33.340> like<00:48:33.970> how<00:48:34.150> much<00:48:34.300> you<00:48:34.450> have 00:48:34.590 --> 00:48:34.600 align:start position:0% trade-off between like how much you have 00:48:34.600 --> 00:48:36.990 align:start position:0% trade-off between like how much you have strategy<00:48:35.080> versus<00:48:35.560> be<00:48:35.830> more<00:48:35.980> complexity<00:48:36.760> and 00:48:36.990 --> 00:48:37.000 align:start position:0% strategy versus be more complexity and 00:48:37.000 --> 00:48:38.310 align:start position:0% strategy versus be more complexity and that's<00:48:37.450> one<00:48:37.630> of<00:48:37.660> the<00:48:37.780> big<00:48:37.930> things<00:48:38.050> anymore 00:48:38.310 --> 00:48:38.320 align:start position:0% that's one of the big things anymore 00:48:38.320 --> 00:48:44.060 align:start position:0% that's one of the big things anymore there<00:48:38.650> were<00:48:38.710> a<00:48:38.740> lot<00:48:38.920> of<00:48:38.950> six<00:48:39.160> months 00:48:44.060 --> 00:48:44.070 align:start position:0% 00:48:44.070 --> 00:48:47.340 align:start position:0% the<00:48:45.070> execution<00:48:45.790> of<00:48:45.910> those<00:48:46.120> like<00:48:46.420> actually 00:48:47.340 --> 00:48:47.350 align:start position:0% the execution of those like actually 00:48:47.350 --> 00:48:49.260 align:start position:0% the execution of those like actually happens<00:48:47.650> unlike<00:48:48.010> the<00:48:48.190> shark<00:48:48.490> client<00:48:49.150> himself 00:48:49.260 --> 00:48:49.270 align:start position:0% happens unlike the shark client himself 00:48:49.270 --> 00:48:53.690 align:start position:0% happens unlike the shark client himself early<00:48:49.900> we<00:48:50.230> need<00:48:50.560> small<00:48:50.830> external<00:48:51.490> clients<00:48:52.120> the 00:48:53.690 --> 00:48:53.700 align:start position:0% early we need small external clients the 00:48:53.700 --> 00:48:56.030 align:start position:0% early we need small external clients the so<00:48:54.240> like<00:48:54.540> running<00:48:54.990> the<00:48:55.140> code<00:48:55.380> would<00:48:55.680> be<00:48:55.829> done 00:48:56.030 --> 00:48:56.040 align:start position:0% so like running the code would be done 00:48:56.040 --> 00:48:57.770 align:start position:0% so like running the code would be done by<00:48:56.220> shark<00:48:56.490> clients<00:48:57.059> as<00:48:57.210> you<00:48:57.240> have<00:48:57.480> to<00:48:57.630> like 00:48:57.770 --> 00:48:57.780 align:start position:0% by shark clients as you have to like 00:48:57.780 --> 00:49:00.319 align:start position:0% by shark clients as you have to like check<00:48:57.990> the<00:48:58.109> state<00:48:58.319> routes<00:48:58.940> doing<00:48:59.940> kind<00:49:00.210> of 00:49:00.319 --> 00:49:00.329 align:start position:0% check the state routes doing kind of 00:49:00.329 --> 00:49:02.630 align:start position:0% check the state routes doing kind of user<00:49:00.660> specific<00:49:01.200> activity<00:49:01.770> like<00:49:02.040> maintaining 00:49:02.630 --> 00:49:02.640 align:start position:0% user specific activity like maintaining 00:49:02.640 --> 00:49:04.849 align:start position:0% user specific activity like maintaining States<00:49:03.150> and<00:49:03.480> like<00:49:03.690> generating<00:49:04.319> witnesses 00:49:04.849 --> 00:49:04.859 align:start position:0% States and like generating witnesses 00:49:04.859 --> 00:49:07.490 align:start position:0% States and like generating witnesses like<00:49:05.609> all<00:49:06.150> of<00:49:06.420> that<00:49:06.599> is<00:49:06.780> definitely<00:49:07.319> right 00:49:07.490 --> 00:49:07.500 align:start position:0% like all of that is definitely right 00:49:07.500 --> 00:49:10.970 align:start position:0% like all of that is definitely right upgraded<00:49:08.069> terrain<00:49:08.819> that<00:49:09.410> make<00:49:10.410> things<00:49:10.710> like 00:49:10.970 --> 00:49:10.980 align:start position:0% upgraded terrain that make things like 00:49:10.980 --> 00:49:12.610 align:start position:0% upgraded terrain that make things like definitely<00:49:11.579> we<00:49:11.940> need<00:49:12.089> to 00:49:12.610 --> 00:49:12.620 align:start position:0% definitely we need to 00:49:12.620 --> 00:49:18.559 align:start position:0% definitely we need to who's<00:49:12.800> this<00:49:13.010> for 00:49:18.559 --> 00:49:18.569 align:start position:0% 00:49:18.569 --> 00:49:20.599 align:start position:0% challenges<00:49:19.569> three<00:49:19.809> labor<00:49:20.049> markets 00:49:20.599 --> 00:49:20.609 align:start position:0% challenges three labor markets 00:49:20.609 --> 00:49:24.680 align:start position:0% challenges three labor markets challenges<00:49:21.609> with<00:49:21.730> the<00:49:21.880> markets 00:49:24.680 --> 00:49:24.690 align:start position:0% 00:49:24.690 --> 00:49:26.420 align:start position:0% [Music] 00:49:26.420 --> 00:49:26.430 align:start position:0% [Music] 00:49:26.430 --> 00:49:28.430 align:start position:0% [Music] and<00:49:26.789> you<00:49:27.029> know<00:49:27.089> what<00:49:27.630> you're<00:49:27.809> up<00:49:27.960> to<00:49:27.990> points 00:49:28.430 --> 00:49:28.440 align:start position:0% and you know what you're up to points 00:49:28.440 --> 00:49:33.260 align:start position:0% and you know what you're up to points about<00:49:28.799> challenges<00:49:29.309> over<00:49:29.579> labor<00:49:29.880> markets<00:49:32.240> the 00:49:33.260 --> 00:49:33.270 align:start position:0% about challenges over labor markets the 00:49:33.270 --> 00:49:37.069 align:start position:0% about challenges over labor markets the I<00:49:33.809> I<00:49:33.930> think<00:49:34.349> the<00:49:35.240> challenge<00:49:36.240> with<00:49:36.510> the<00:49:36.660> relayer 00:49:37.069 --> 00:49:37.079 align:start position:0% I I think the challenge with the relayer 00:49:37.079 --> 00:49:40.250 align:start position:0% I I think the challenge with the relayer markets<00:49:37.770> as<00:49:38.069> basically<00:49:38.609> a<00:49:38.789> bit<00:49:39.000> like<00:49:39.210> and<00:49:39.690> this 00:49:40.250 --> 00:49:40.260 align:start position:0% markets as basically a bit like and this 00:49:40.260 --> 00:49:41.960 align:start position:0% markets as basically a bit like and this scene<00:49:40.470> this<00:49:40.619> is<00:49:40.680> like<00:49:40.950> a<00:49:40.980> common<00:49:41.309> opinion<00:49:41.640> I've 00:49:41.960 --> 00:49:41.970 align:start position:0% scene this is like a common opinion I've 00:49:41.970 --> 00:49:44.870 align:start position:0% scene this is like a common opinion I've quite<00:49:42.240> so<00:49:42.900> and<00:49:43.260> I<00:49:43.650> begin<00:49:43.950> I<00:49:44.099> had<00:49:44.339> like<00:49:44.579> two<00:49:44.760> or 00:49:44.870 --> 00:49:44.880 align:start position:0% quite so and I begin I had like two or 00:49:44.880 --> 00:49:46.430 align:start position:0% quite so and I begin I had like two or three<00:49:44.910> months<00:49:45.180> ago<00:49:45.539> as<00:49:45.720> the<00:49:45.839> dungeons<00:49:46.200> good 00:49:46.430 --> 00:49:46.440 align:start position:0% three months ago as the dungeons good 00:49:46.440 --> 00:49:48.349 align:start position:0% three months ago as the dungeons good that<00:49:46.619> we<00:49:46.740> have<00:49:46.890> like<00:49:47.220> optimistic<00:49:47.910> roll<00:49:48.089> up<00:49:48.210> in 00:49:48.349 --> 00:49:48.359 align:start position:0% that we have like optimistic roll up in 00:49:48.359 --> 00:49:49.940 align:start position:0% that we have like optimistic roll up in the<00:49:48.539> C<00:49:48.690> key<00:49:48.839> role<00:49:49.020> of<00:49:49.109> happening<00:49:49.470> on<00:49:49.559> this<00:49:49.650> one 00:49:49.940 --> 00:49:49.950 align:start position:0% the C key role of happening on this one 00:49:49.950 --> 00:49:51.410 align:start position:0% the C key role of happening on this one because<00:49:50.190> like<00:49:50.609> that<00:49:50.849> means<00:49:51.089> that<00:49:51.240> there<00:49:51.359> was 00:49:51.410 --> 00:49:51.420 align:start position:0% because like that means that there was 00:49:51.420 --> 00:49:53.480 align:start position:0% because like that means that there was more<00:49:51.630> people<00:49:51.839> like<00:49:52.289> T<00:49:52.920> thinking<00:49:53.309> and 00:49:53.480 --> 00:49:53.490 align:start position:0% more people like T thinking and 00:49:53.490 --> 00:49:55.220 align:start position:0% more people like T thinking and experimenting<00:49:54.180> about<00:49:54.450> real<00:49:54.599> labor<00:49:54.779> markets 00:49:55.220 --> 00:49:55.230 align:start position:0% experimenting about real labor markets 00:49:55.230 --> 00:49:58.430 align:start position:0% experimenting about real labor markets and<00:49:55.470> that<00:49:56.339> community<00:49:56.970> seems<00:49:57.390> to<00:49:57.660> keep<00:49:57.839> coming 00:49:58.430 --> 00:49:58.440 align:start position:0% and that community seems to keep coming 00:49:58.440 --> 00:50:01.010 align:start position:0% and that community seems to keep coming to<00:49:58.559> the<00:49:58.650> conclusion<00:49:58.829> that<00:49:59.430> roll<00:50:00.359> up<00:50:00.599> chains 00:50:01.010 --> 00:50:01.020 align:start position:0% to the conclusion that roll up chains 00:50:01.020 --> 00:50:05.180 align:start position:0% to the conclusion that roll up chains are<00:50:01.380> likely<00:50:01.859> to<00:50:02.039> have<00:50:02.220> monopoly<00:50:02.849> promoters<00:50:04.190> in 00:50:05.180 --> 00:50:05.190 align:start position:0% are likely to have monopoly promoters in 00:50:05.190 --> 00:50:07.010 align:start position:0% are likely to have monopoly promoters in the<00:50:05.430> argument<00:50:05.880> basically<00:50:06.059> has<00:50:06.420> been<00:50:06.450> like<00:50:06.779> as 00:50:07.010 --> 00:50:07.020 align:start position:0% the argument basically has been like as 00:50:07.020 --> 00:50:09.019 align:start position:0% the argument basically has been like as soon<00:50:07.559> as<00:50:07.799> there's<00:50:08.010> one<00:50:08.069> party<00:50:08.609> that's<00:50:08.730> better 00:50:09.019 --> 00:50:09.029 align:start position:0% soon as there's one party that's better 00:50:09.029 --> 00:50:11.480 align:start position:0% soon as there's one party that's better at<00:50:09.180> sequencing<00:50:09.779> that<00:50:09.930> others<00:50:10.289> that<00:50:10.680> they<00:50:11.309> need 00:50:11.480 --> 00:50:11.490 align:start position:0% at sequencing that others that they need 00:50:11.490 --> 00:50:13.020 align:start position:0% at sequencing that others that they need to<00:50:11.609> be<00:50:11.670> only<00:50:11.849> slightly<00:50:12.029> better 00:50:13.020 --> 00:50:13.030 align:start position:0% to be only slightly better 00:50:13.030 --> 00:50:17.040 align:start position:0% to be only slightly better that<00:50:13.180> everyone<00:50:13.480> else<00:50:13.890> and<00:50:15.120> this<00:50:16.120> potentially 00:50:17.040 --> 00:50:17.050 align:start position:0% that everyone else and this potentially 00:50:17.050 --> 00:50:19.650 align:start position:0% that everyone else and this potentially has<00:50:17.260> censorship<00:50:17.980> risks<00:50:18.400> and<00:50:18.730> so<00:50:19.210> like<00:50:19.480> that 00:50:19.650 --> 00:50:19.660 align:start position:0% has censorship risks and so like that 00:50:19.660 --> 00:50:21.240 align:start position:0% has censorship risks and so like that means<00:50:19.870> to<00:50:20.110> funnel<00:50:20.320> your<00:50:20.590> tuna<00:50:20.890> later<00:50:21.070> to 00:50:21.240 --> 00:50:21.250 align:start position:0% means to funnel your tuna later to 00:50:21.250 --> 00:50:22.860 align:start position:0% means to funnel your tuna later to context<00:50:21.820> you<00:50:21.910> can<00:50:22.060> obviously<00:50:22.300> switch<00:50:22.690> the 00:50:22.860 --> 00:50:22.870 align:start position:0% context you can obviously switch the 00:50:22.870 --> 00:50:24.360 align:start position:0% context you can obviously switch the differences<00:50:23.320> that<00:50:23.350> was<00:50:23.650> what<00:50:23.800> annoy<00:50:24.010> or<00:50:24.190> what 00:50:24.360 --> 00:50:24.370 align:start position:0% differences that was what annoy or what 00:50:24.370 --> 00:50:28.620 align:start position:0% differences that was what annoy or what contacts<00:50:24.910> what<00:50:25.210> you<00:50:25.360> get<00:50:26.160> so<00:50:27.300> yeah<00:50:28.300> a<00:50:28.450> layer 00:50:28.620 --> 00:50:28.630 align:start position:0% contacts what you get so yeah a layer 00:50:28.630 --> 00:50:30.930 align:start position:0% contacts what you get so yeah a layer one<00:50:28.870> context<00:50:29.530> like<00:50:29.740> you<00:50:29.890> want<00:50:30.130> more<00:50:30.400> security 00:50:30.930 --> 00:50:30.940 align:start position:0% one context like you want more security 00:50:30.940 --> 00:50:32.750 align:start position:0% one context like you want more security of<00:50:31.000> Mexico<00:50:31.570> gliding 00:50:32.750 --> 00:50:32.760 align:start position:0% of Mexico gliding 00:50:32.760 --> 00:50:35.310 align:start position:0% of Mexico gliding so<00:50:33.760> the<00:50:33.970> next<00:50:34.180> one<00:50:34.420> we<00:50:34.660> kind<00:50:34.840> of<00:50:34.960> hug<00:50:35.110> below 00:50:35.310 --> 00:50:35.320 align:start position:0% so the next one we kind of hug below 00:50:35.320 --> 00:50:38.190 align:start position:0% so the next one we kind of hug below this<00:50:35.470> morning<00:50:35.590> and<00:50:36.100> is<00:50:36.660> just<00:50:37.660> among<00:50:37.900> some<00:50:38.110> of 00:50:38.190 --> 00:50:38.200 align:start position:0% this morning and is just among some of 00:50:38.200 --> 00:50:43.020 align:start position:0% this morning and is just among some of the<00:50:38.260> participants<00:50:40.920> should<00:50:41.920> E's<00:50:42.310> be<00:50:42.550> open<00:50:42.880> for 00:50:43.020 --> 00:50:43.030 align:start position:0% the participants should E's be open for 00:50:43.030 --> 00:50:44.910 align:start position:0% the participants should E's be open for anyone<00:50:43.330> to<00:50:43.540> deploy<00:50:43.870> or<00:50:44.170> restrictive<00:50:44.680> I'll 00:50:44.910 --> 00:50:44.920 align:start position:0% anyone to deploy or restrictive I'll 00:50:44.920 --> 00:50:49.680 align:start position:0% anyone to deploy or restrictive I'll give<00:50:45.100> you<00:50:45.220> a<00:50:45.310> quick<00:50:45.580> on<00:50:46.150> the<00:50:47.220> range<00:50:48.220> there<00:50:48.940> so 00:50:49.680 --> 00:50:49.690 align:start position:0% give you a quick on the range there so 00:50:49.690 --> 00:50:52.710 align:start position:0% give you a quick on the range there so on<00:50:49.870> the<00:50:49.900> one<00:50:50.080> end<00:50:50.790> you<00:50:51.790> could<00:50:52.000> deploy<00:50:52.570> the 00:50:52.710 --> 00:50:52.720 align:start position:0% on the one end you could deploy the 00:50:52.720 --> 00:50:55.200 align:start position:0% on the one end you could deploy the system<00:50:53.070> such<00:50:54.070> that<00:50:54.100> these<00:50:54.610> can<00:50:54.850> be<00:50:54.880> employed 00:50:55.200 --> 00:50:55.210 align:start position:0% system such that these can be employed 00:50:55.210 --> 00:50:57.210 align:start position:0% system such that these can be employed by<00:50:55.690> anyone<00:50:56.020> with<00:50:56.200> a<00:50:56.230> certain<00:50:56.530> economic<00:50:56.650> model 00:50:57.210 --> 00:50:57.220 align:start position:0% by anyone with a certain economic model 00:50:57.220 --> 00:50:58.620 align:start position:0% by anyone with a certain economic model to<00:50:57.430> deploy<00:50:57.700> these<00:50:57.880> probably<00:50:58.270> very<00:50:58.510> expensive 00:50:58.620 --> 00:50:58.630 align:start position:0% to deploy these probably very expensive 00:50:58.630 --> 00:51:02.490 align:start position:0% to deploy these probably very expensive to<00:50:59.170> do<00:50:59.350> so<00:50:59.820> but<00:51:00.820> people<00:51:01.750> play<00:51:01.960> with<00:51:01.990> them<00:51:02.290> let 00:51:02.490 --> 00:51:02.500 align:start position:0% to do so but people play with them let 00:51:02.500 --> 00:51:04.020 align:start position:0% to do so but people play with them let standards<00:51:02.950> emerge<00:51:03.250> and<00:51:03.550> just<00:51:03.670> kind<00:51:03.850> of<00:51:03.880> see 00:51:04.020 --> 00:51:04.030 align:start position:0% standards emerge and just kind of see 00:51:04.030 --> 00:51:07.140 align:start position:0% standards emerge and just kind of see what<00:51:04.180> happens<00:51:04.510> on<00:51:05.380> the<00:51:05.770> other<00:51:05.950> extreme<00:51:06.430> there 00:51:07.140 --> 00:51:07.150 align:start position:0% what happens on the other extreme there 00:51:07.150 --> 00:51:08.940 align:start position:0% what happens on the other extreme there are<00:51:07.570> some<00:51:07.840> participants<00:51:08.200> that<00:51:08.410> argue<00:51:08.770> that 00:51:08.940 --> 00:51:08.950 align:start position:0% are some participants that argue that 00:51:08.950 --> 00:51:12.300 align:start position:0% are some participants that argue that maybe<00:51:09.310> we<00:51:09.610> should<00:51:09.790> deploy<00:51:10.120> one<00:51:10.800> very<00:51:11.800> good<00:51:12.010> EEG 00:51:12.300 --> 00:51:12.310 align:start position:0% maybe we should deploy one very good EEG 00:51:12.310 --> 00:51:14.250 align:start position:0% maybe we should deploy one very good EEG that<00:51:12.400> feels<00:51:13.240> like<00:51:13.450> ethereum<00:51:13.960> it<00:51:14.080> kind<00:51:14.230> of 00:51:14.250 --> 00:51:14.260 align:start position:0% that feels like ethereum it kind of 00:51:14.260 --> 00:51:16.890 align:start position:0% that feels like ethereum it kind of gives<00:51:14.440> a<00:51:14.560> very<00:51:14.680> clear<00:51:14.800> user<00:51:15.310> story<00:51:15.670> and<00:51:16.660> allows 00:51:16.890 --> 00:51:16.900 align:start position:0% gives a very clear user story and allows 00:51:16.900 --> 00:51:19.290 align:start position:0% gives a very clear user story and allows people<00:51:17.650> to<00:51:17.860> like<00:51:18.220> build<00:51:18.460> up<00:51:18.640> and<00:51:18.910> make<00:51:19.240> it 00:51:19.290 --> 00:51:19.300 align:start position:0% people to like build up and make it 00:51:19.300 --> 00:51:21.180 align:start position:0% people to like build up and make it operate<00:51:19.690> in<00:51:19.780> this<00:51:19.870> rashard<00:51:20.260> context<00:51:20.860> and<00:51:21.010> then 00:51:21.180 --> 00:51:21.190 align:start position:0% operate in this rashard context and then 00:51:21.190 --> 00:51:23.160 align:start position:0% operate in this rashard context and then eventually<00:51:21.520> open<00:51:22.000> up<00:51:22.090> be<00:51:22.210> used<00:51:22.450> to<00:51:22.630> the<00:51:22.780> the 00:51:23.160 --> 00:51:23.170 align:start position:0% eventually open up be used to the the 00:51:23.170 --> 00:51:26.850 align:start position:0% eventually open up be used to the the deploy<00:51:23.500> and<00:51:23.920> let<00:51:24.670> people<00:51:25.000> experiment<00:51:25.860> the 00:51:26.850 --> 00:51:26.860 align:start position:0% deploy and let people experiment the 00:51:26.860 --> 00:51:28.290 align:start position:0% deploy and let people experiment the second<00:51:27.220> proposal<00:51:27.370> was<00:51:27.700> called<00:51:27.910> dictatorial 00:51:28.290 --> 00:51:28.300 align:start position:0% second proposal was called dictatorial 00:51:28.300 --> 00:51:32.040 align:start position:0% second proposal was called dictatorial at<00:51:28.840> this<00:51:29.050> point<00:51:30.270> but<00:51:31.270> at<00:51:31.540> the<00:51:31.690> same<00:51:31.840> time 00:51:32.040 --> 00:51:32.050 align:start position:0% at this point but at the same time 00:51:32.050 --> 00:51:33.480 align:start position:0% at this point but at the same time provides<00:51:32.500> like<00:51:32.830> a<00:51:32.980> little<00:51:33.250> bit<00:51:33.370> more 00:51:33.480 --> 00:51:33.490 align:start position:0% provides like a little bit more 00:51:33.490 --> 00:51:34.770 align:start position:0% provides like a little bit more guarantee<00:51:33.910> that<00:51:34.120> we<00:51:34.240> get<00:51:34.390> something<00:51:34.600> out 00:51:34.770 --> 00:51:34.780 align:start position:0% guarantee that we get something out 00:51:34.780 --> 00:51:35.460 align:start position:0% guarantee that we get something out looks 00:51:35.460 --> 00:51:35.470 align:start position:0% looks 00:51:35.470 --> 00:51:41.579 align:start position:0% looks area<00:51:35.829> so<00:51:36.700> it's<00:51:36.880> a<00:51:37.000> it's<00:51:37.300> a<00:51:39.660> to<00:51:40.660> be<00:51:40.839> debated 00:51:41.579 --> 00:51:41.589 align:start position:0% area so it's a it's a to be debated 00:51:41.589 --> 00:51:44.550 align:start position:0% area so it's a it's a to be debated still<00:51:42.480> the<00:51:43.480> second<00:51:43.810> proposal<00:51:44.140> that<00:51:44.349> does 00:51:44.550 --> 00:51:44.560 align:start position:0% still the second proposal that does 00:51:44.560 --> 00:51:46.530 align:start position:0% still the second proposal that does about<00:51:44.890> what<00:51:45.010> you<00:51:45.099> eat<00:51:45.310> still<00:51:45.700> as<00:51:46.359> you<00:51:46.480> can 00:51:46.530 --> 00:51:46.540 align:start position:0% about what you eat still as you can 00:51:46.540 --> 00:51:47.250 align:start position:0% about what you eat still as you can Billie's 00:51:47.250 --> 00:51:47.260 align:start position:0% Billie's 00:51:47.260 --> 00:51:53.180 align:start position:0% Billie's and<00:51:47.500> top<00:51:47.800> of<00:51:47.950> this<00:51:48.160> nice<00:51:49.650> yes 00:51:53.180 --> 00:51:53.190 align:start position:0% 00:51:53.190 --> 00:51:54.950 align:start position:0% so<00:51:53.730> I<00:51:53.789> guess<00:51:53.940> the<00:51:54.089> question<00:51:54.119> is<00:51:54.480> what<00:51:54.720> it<00:51:54.839> means 00:51:54.950 --> 00:51:54.960 align:start position:0% so I guess the question is what it means 00:51:54.960 --> 00:51:58.250 align:start position:0% so I guess the question is what it means to<00:51:55.170> have<00:51:55.410> a<00:51:55.640> flip<00:51:56.640> top<00:51:56.819> level<00:51:57.180> T<00:51:57.329> versus 00:51:58.250 --> 00:51:58.260 align:start position:0% to have a flip top level T versus 00:51:58.260 --> 00:52:01.069 align:start position:0% to have a flip top level T versus deploying<00:51:58.849> will<00:51:59.849> all<00:51:59.970> recall<00:52:00.539> beat<00:52:00.900> each 00:52:01.069 --> 00:52:01.079 align:start position:0% deploying will all recall beat each 00:52:01.079 --> 00:52:05.359 align:start position:0% deploying will all recall beat each other<00:52:01.740> contracts<00:52:02.280> that's<00:52:03.950> the<00:52:04.950> person<00:52:05.280> in 00:52:05.359 --> 00:52:05.369 align:start position:0% other contracts that's the person in 00:52:05.369 --> 00:52:08.839 align:start position:0% other contracts that's the person in question<00:52:06.859> it's<00:52:07.859> probably<00:52:07.950> that<00:52:08.460> would<00:52:08.670> be 00:52:08.839 --> 00:52:08.849 align:start position:0% question it's probably that would be 00:52:08.849 --> 00:52:12.079 align:start position:0% question it's probably that would be what<00:52:09.329> one<00:52:09.720> of<00:52:09.750> two<00:52:10.049> bees<00:52:10.380> that<00:52:11.039> some<00:52:11.880> big 00:52:12.079 --> 00:52:12.089 align:start position:0% what one of two bees that some big 00:52:12.089 --> 00:52:14.329 align:start position:0% what one of two bees that some big things<00:52:12.390> are<00:52:12.630> going<00:52:12.780> to<00:52:12.900> develop<00:52:13.109> at<00:52:13.559> the<00:52:13.770> so 00:52:14.329 --> 00:52:14.339 align:start position:0% things are going to develop at the so 00:52:14.339 --> 00:52:16.250 align:start position:0% things are going to develop at the so what<00:52:14.640> would<00:52:14.849> be<00:52:14.970> the<00:52:15.119> benefits<00:52:15.599> or<00:52:15.900> not 00:52:16.250 --> 00:52:16.260 align:start position:0% what would be the benefits or not 00:52:16.260 --> 00:52:18.230 align:start position:0% what would be the benefits or not nothing<00:52:16.650> anymore<00:52:16.770> experiment<00:52:17.700> with<00:52:17.940> some 00:52:18.230 --> 00:52:18.240 align:start position:0% nothing anymore experiment with some 00:52:18.240 --> 00:52:23.599 align:start position:0% nothing anymore experiment with some other<00:52:20.210> one<00:52:21.240> nakiya<00:52:22.079> nerve<00:52:22.349> distinction<00:52:23.220> has 00:52:23.599 --> 00:52:23.609 align:start position:0% other one nakiya nerve distinction has 00:52:23.609 --> 00:52:26.420 align:start position:0% other one nakiya nerve distinction has to<00:52:23.819> do<00:52:24.030> with<00:52:24.299> like<00:52:24.750> state<00:52:25.170> so<00:52:25.859> one<00:52:26.130> of<00:52:26.280> the 00:52:26.420 --> 00:52:26.430 align:start position:0% to do with like state so one of the 00:52:26.430 --> 00:52:28.279 align:start position:0% to do with like state so one of the remaining<00:52:26.670> rules<00:52:27.030> of<00:52:27.240> an<00:52:27.329> EVD<00:52:27.599> is<00:52:27.839> kind<00:52:28.140> of 00:52:28.279 --> 00:52:28.289 align:start position:0% remaining rules of an EVD is kind of 00:52:28.289 --> 00:52:30.890 align:start position:0% remaining rules of an EVD is kind of like<00:52:29.010> describing<00:52:29.549> a<00:52:29.880> diffuser<00:52:30.390> almost<00:52:30.720> state 00:52:30.890 --> 00:52:30.900 align:start position:0% like describing a diffuser almost state 00:52:30.900 --> 00:52:34.490 align:start position:0% like describing a diffuser almost state structure<00:52:31.910> if<00:52:32.910> we<00:52:33.150> have<00:52:33.329> one<00:52:33.599> and<00:52:33.780> try<00:52:33.960> to<00:52:34.020> even 00:52:34.490 --> 00:52:34.500 align:start position:0% structure if we have one and try to even 00:52:34.500 --> 00:52:36.589 align:start position:0% structure if we have one and try to even and<00:52:34.680> let<00:52:34.799> abilities<00:52:35.520> Italy<00:52:35.849> in<00:52:36.089> that<00:52:36.270> idea 00:52:36.589 --> 00:52:36.599 align:start position:0% and let abilities Italy in that idea 00:52:36.599 --> 00:52:39.170 align:start position:0% and let abilities Italy in that idea then<00:52:37.020> like<00:52:37.650> no<00:52:37.890> matter<00:52:38.069> how<00:52:38.430> successful<00:52:38.730> this 00:52:39.170 --> 00:52:39.180 align:start position:0% then like no matter how successful this 00:52:39.180 --> 00:52:40.789 align:start position:0% then like no matter how successful this integrity<00:52:39.690> is<00:52:39.960> are<00:52:40.109> there<00:52:40.349> because<00:52:40.500> they 00:52:40.789 --> 00:52:40.799 align:start position:0% integrity is are there because they 00:52:40.799 --> 00:52:43.430 align:start position:0% integrity is are there because they depend<00:52:41.010> on<00:52:41.400> the<00:52:41.549> original<00:52:42.000> year<00:52:42.359> whatever<00:52:43.260> the 00:52:43.430 --> 00:52:43.440 align:start position:0% depend on the original year whatever the 00:52:43.440 --> 00:52:45.349 align:start position:0% depend on the original year whatever the state<00:52:43.680> model<00:52:44.069> of<00:52:44.220> the<00:52:44.369> original<00:52:44.460> you<00:52:44.970> know 00:52:45.349 --> 00:52:45.359 align:start position:0% state model of the original you know 00:52:45.359 --> 00:52:47.599 align:start position:0% state model of the original you know steps<00:52:45.720> like<00:52:45.900> a<00:52:45.960> statement<00:52:46.319> like<00:52:46.559> that<00:52:46.619> status 00:52:47.599 --> 00:52:47.609 align:start position:0% steps like a statement like that status 00:52:47.609 --> 00:52:49.339 align:start position:0% steps like a statement like that status state<00:52:47.849> that<00:52:48.119> basically<00:52:48.690> everyone<00:52:48.990> will<00:52:49.260> need 00:52:49.339 --> 00:52:49.349 align:start position:0% state that basically everyone will need 00:52:49.349 --> 00:52:53.359 align:start position:0% state that basically everyone will need to<00:52:49.530> have<00:52:50.420> whereas<00:52:51.420> if<00:52:52.260> these<00:52:52.710> are<00:52:53.099> more 00:52:53.359 --> 00:52:53.369 align:start position:0% to have whereas if these are more 00:52:53.369 --> 00:52:55.359 align:start position:0% to have whereas if these are more parallel<00:52:53.849> with<00:52:54.030> each<00:52:54.150> other<00:52:54.420> that 00:52:55.359 --> 00:52:55.369 align:start position:0% parallel with each other that 00:52:55.369 --> 00:52:57.370 align:start position:0% parallel with each other that falls<00:52:55.970> into<00:52:56.150> this<00:52:56.329> yearís<00:52:56.690> that<00:52:56.900> had<00:52:57.079> a<00:52:57.109> fewer 00:52:57.370 --> 00:52:57.380 align:start position:0% falls into this yearís that had a fewer 00:52:57.380 --> 00:53:00.970 align:start position:0% falls into this yearís that had a fewer people<00:52:57.619> can<00:52:57.799> store<00:52:58.190> it<00:52:58.309> state<00:52:58.900> again<00:52:59.900> you<00:53:00.859> were 00:53:00.970 --> 00:53:00.980 align:start position:0% people can store it state again you were 00:53:00.980 --> 00:53:05.289 align:start position:0% people can store it state again you were then<00:53:01.130> and<00:53:01.369> so<00:53:01.549> fewer<00:53:01.880> people<00:53:02.150> think<00:53:03.640> like<00:53:04.640> it 00:53:05.289 --> 00:53:05.299 align:start position:0% then and so fewer people think like it 00:53:05.299 --> 00:53:07.870 align:start position:0% then and so fewer people think like it might<00:53:05.509> become<00:53:05.960> like<00:53:06.700> slightly<00:53:07.700> more 00:53:07.870 --> 00:53:07.880 align:start position:0% might become like slightly more 00:53:07.880 --> 00:53:09.640 align:start position:0% might become like slightly more difficult<00:53:08.059> to<00:53:08.539> do<00:53:08.660> things<00:53:08.930> what<00:53:09.200> that<00:53:09.380> but 00:53:09.640 --> 00:53:09.650 align:start position:0% difficult to do things what that but 00:53:09.650 --> 00:53:10.870 align:start position:0% difficult to do things what that but like<00:53:09.829> other<00:53:10.069> people<00:53:10.400> don't<00:53:10.549> need<00:53:10.700> to<00:53:10.759> be 00:53:10.870 --> 00:53:10.880 align:start position:0% like other people don't need to be 00:53:10.880 --> 00:53:14.349 align:start position:0% like other people don't need to be bothered<00:53:11.059> with<00:53:11.269> that<00:53:11.539> data<00:53:11.749> and<00:53:12.440> so<00:53:13.220> I've<00:53:14.119> had 00:53:14.349 --> 00:53:14.359 align:start position:0% bothered with that data and so I've had 00:53:14.359 --> 00:53:16.900 align:start position:0% bothered with that data and so I've had to<00:53:14.390> a<00:53:14.809> parallel<00:53:15.680> approach<00:53:16.099> like<00:53:16.430> at<00:53:16.579> least<00:53:16.759> in 00:53:16.900 --> 00:53:16.910 align:start position:0% to a parallel approach like at least in 00:53:16.910 --> 00:53:18.640 align:start position:0% to a parallel approach like at least in the<00:53:16.999> short<00:53:17.210> term<00:53:17.299> it<00:53:17.630> gives<00:53:17.809> us<00:53:18.019> freedom<00:53:18.200> not 00:53:18.640 --> 00:53:18.650 align:start position:0% the short term it gives us freedom not 00:53:18.650 --> 00:53:20.019 align:start position:0% the short term it gives us freedom not to<00:53:18.829> commit<00:53:19.069> to<00:53:19.249> a<00:53:19.309> particular<00:53:19.819> state 00:53:20.019 --> 00:53:20.029 align:start position:0% to commit to a particular state 00:53:20.029 --> 00:53:22.779 align:start position:0% to commit to a particular state structure<00:53:20.599> and<00:53:20.900> to<00:53:21.470> a<00:53:21.499> particular<00:53:22.339> trade<00:53:22.640> off 00:53:22.779 --> 00:53:22.789 align:start position:0% structure and to a particular trade off 00:53:22.789 --> 00:53:25.569 align:start position:0% structure and to a particular trade off between<00:53:23.559> involving<00:53:24.559> things<00:53:24.829> away<00:53:25.099> events 00:53:25.569 --> 00:53:25.579 align:start position:0% between involving things away events 00:53:25.579 --> 00:53:29.130 align:start position:0% between involving things away events versus<00:53:26.559> storage<00:53:27.559> status<00:53:28.009> versus<00:53:28.430> like<00:53:28.730> pasta 00:53:29.130 --> 00:53:29.140 align:start position:0% versus storage status versus like pasta 00:53:29.140 --> 00:53:31.509 align:start position:0% versus storage status versus like pasta filling<00:53:30.140> that<00:53:30.289> confers<00:53:30.769> resistance<00:53:30.950> date 00:53:31.509 --> 00:53:31.519 align:start position:0% filling that confers resistance date 00:53:31.519 --> 00:53:34.430 align:start position:0% filling that confers resistance date there's<00:53:31.940> also<00:53:32.059> risks<00:53:32.660> and<00:53:32.839> how<00:53:32.990> a<00:53:33.019> CER 00:53:34.430 --> 00:53:34.440 align:start position:0% there's also risks and how a CER 00:53:34.440 --> 00:53:37.940 align:start position:0% there's also risks and how a CER and<00:53:35.220> also<00:53:35.400> with<00:53:35.760> respect<00:53:35.910> to<00:53:36.740> potential<00:53:37.740> bugs 00:53:37.940 --> 00:53:37.950 align:start position:0% and also with respect to potential bugs 00:53:37.950 --> 00:53:40.370 align:start position:0% and also with respect to potential bugs someone<00:53:38.609> brought<00:53:38.760> up<00:53:38.819> this<00:53:38.970> morning<00:53:39.300> like<00:53:39.450> the 00:53:40.370 --> 00:53:40.380 align:start position:0% someone brought up this morning like the 00:53:40.380 --> 00:53:41.780 align:start position:0% someone brought up this morning like the omen<00:53:40.619> from<00:53:40.710> mallero<00:53:41.099> perspective<00:53:41.550> the<00:53:41.640> only 00:53:41.780 --> 00:53:41.790 align:start position:0% omen from mallero perspective the only 00:53:41.790 --> 00:53:43.040 align:start position:0% omen from mallero perspective the only thing<00:53:41.910> that<00:53:42.060> going<00:53:42.240> to<00:53:42.359> keep<00:53:42.510> her<00:53:42.810> like 00:53:43.040 --> 00:53:43.050 align:start position:0% thing that going to keep her like 00:53:43.050 --> 00:53:46.309 align:start position:0% thing that going to keep her like validators<00:53:43.619> enemies<00:53:44.339> and<00:53:44.670> then<00:53:44.839> you<00:53:45.839> actually 00:53:46.309 --> 00:53:46.319 align:start position:0% validators enemies and then you actually 00:53:46.319 --> 00:53:48.140 align:start position:0% validators enemies and then you actually as<00:53:46.440> a<00:53:46.470> user<00:53:46.740> own<00:53:47.010> beings<00:53:47.310> within<00:53:47.520> the<00:53:47.730> context 00:53:48.140 --> 00:53:48.150 align:start position:0% as a user own beings within the context 00:53:48.150 --> 00:53:49.720 align:start position:0% as a user own beings within the context of<00:53:48.300> the<00:53:48.390> account<00:53:48.660> structure<00:53:48.930> of<00:53:49.170> the<00:53:49.260> night 00:53:49.720 --> 00:53:49.730 align:start position:0% of the account structure of the night 00:53:49.730 --> 00:53:52.040 align:start position:0% of the account structure of the night but<00:53:50.730> if<00:53:50.849> for<00:53:51.270> example<00:53:51.329> there<00:53:51.839> was<00:53:51.900> a<00:53:51.960> very 00:53:52.040 --> 00:53:52.050 align:start position:0% but if for example there was a very 00:53:52.050 --> 00:53:54.230 align:start position:0% but if for example there was a very popular<00:53:52.380> ee<00:53:52.800> that<00:53:53.130> exchange<00:53:53.550> is<00:53:53.670> recognized 00:53:54.230 --> 00:53:54.240 align:start position:0% popular ee that exchange is recognized 00:53:54.240 --> 00:53:57.589 align:start position:0% popular ee that exchange is recognized and<00:53:55.280> someone<00:53:56.280> exploited<00:53:56.730> a<00:53:56.790> bug<00:53:56.970> such<00:53:57.329> that 00:53:57.589 --> 00:53:57.599 align:start position:0% and someone exploited a bug such that 00:53:57.599 --> 00:54:00.680 align:start position:0% and someone exploited a bug such that the<00:53:57.810> account<00:53:58.200> structure<00:53:58.650> within<00:53:59.010> me<00:53:59.690> thought 00:54:00.680 --> 00:54:00.690 align:start position:0% the account structure within me thought 00:54:00.690 --> 00:54:03.109 align:start position:0% the account structure within me thought that<00:54:00.990> it<00:54:01.470> had<00:54:01.500> a<00:54:01.710> bunch<00:54:01.980> more<00:54:02.040> even<00:54:02.790> the<00:54:02.910> layer 00:54:03.109 --> 00:54:03.119 align:start position:0% that it had a bunch more even the layer 00:54:03.119 --> 00:54:04.970 align:start position:0% that it had a bunch more even the layer one<00:54:03.420> still<00:54:04.079> loved<00:54:04.349> that<00:54:04.530> it<00:54:04.560> only<00:54:04.740> had 00:54:04.970 --> 00:54:04.980 align:start position:0% one still loved that it only had 00:54:04.980 --> 00:54:07.069 align:start position:0% one still loved that it only had attending<00:54:05.310> than<00:54:05.550> that<00:54:05.670> he<00:54:05.790> someone's<00:54:06.630> account 00:54:07.069 --> 00:54:07.079 align:start position:0% attending than that he someone's account 00:54:07.079 --> 00:54:09.050 align:start position:0% attending than that he someone's account now<00:54:07.440> that<00:54:07.770> the<00:54:07.890> exchange<00:54:08.250> recognizes<00:54:08.910> it's 00:54:09.050 --> 00:54:09.060 align:start position:0% now that the exchange recognizes it's 00:54:09.060 --> 00:54:11.750 align:start position:0% now that the exchange recognizes it's invalid<00:54:09.329> account<00:54:09.720> might<00:54:09.960> have<00:54:10.490> worried<00:54:11.490> so 00:54:11.750 --> 00:54:11.760 align:start position:0% invalid account might have worried so 00:54:11.760 --> 00:54:13.099 align:start position:0% invalid account might have worried so this<00:54:12.000> is<00:54:12.119> kind<00:54:12.300> of<00:54:12.329> like<00:54:12.450> I<00:54:12.480> can<00:54:12.720> do<00:54:12.839> a<00:54:12.869> bug 00:54:13.099 --> 00:54:13.109 align:start position:0% this is kind of like I can do a bug 00:54:13.109 --> 00:54:15.740 align:start position:0% this is kind of like I can do a bug where<00:54:13.380> rap<00:54:13.619> teeth<00:54:13.890> might<00:54:14.160> print<00:54:14.510> rap<00:54:15.510> teeth 00:54:15.740 --> 00:54:15.750 align:start position:0% where rap teeth might print rap teeth 00:54:15.750 --> 00:54:17.329 align:start position:0% where rap teeth might print rap teeth but<00:54:16.020> there's<00:54:16.170> actually<00:54:16.560> not<00:54:16.680> that<00:54:17.040> much<00:54:17.190> ease 00:54:17.329 --> 00:54:17.339 align:start position:0% but there's actually not that much ease 00:54:17.339 --> 00:54:19.520 align:start position:0% but there's actually not that much ease back<00:54:17.520> again<00:54:17.849> so<00:54:18.780> there's<00:54:18.960> there's<00:54:19.200> like<00:54:19.349> all 00:54:19.520 --> 00:54:19.530 align:start position:0% back again so there's there's like all 00:54:19.530 --> 00:54:23.260 align:start position:0% back again so there's there's like all sorts<00:54:19.680> of<00:54:19.829> complexities<00:54:20.190> on<00:54:20.670> like<00:54:21.349> how<00:54:22.349> this 00:54:23.260 --> 00:54:23.270 align:start position:0% sorts of complexities on like how this 00:54:23.270 --> 00:54:26.240 align:start position:0% sorts of complexities on like how this concept<00:54:24.270> of<00:54:24.630> domain<00:54:25.200> issues<00:54:25.500> rolled<00:54:25.920> out<00:54:26.069> to 00:54:26.240 --> 00:54:26.250 align:start position:0% concept of domain issues rolled out to 00:54:26.250 --> 00:54:28.069 align:start position:0% concept of domain issues rolled out to users<00:54:26.609> rolled<00:54:26.849> up<00:54:27.000> to<00:54:27.180> exchanges<00:54:27.720> rolled<00:54:27.960> out 00:54:28.069 --> 00:54:28.079 align:start position:0% users rolled up to exchanges rolled out 00:54:28.079 --> 00:54:29.930 align:start position:0% users rolled up to exchanges rolled out select<00:54:28.440> the<00:54:28.589> various<00:54:28.890> participants<00:54:29.130> and<00:54:29.849> the 00:54:29.930 --> 00:54:29.940 align:start position:0% select the various participants and the 00:54:29.940 --> 00:54:31.490 align:start position:0% select the various participants and the various<00:54:30.240> all<00:54:30.480> sorts<00:54:30.780> of<00:54:30.810> other<00:54:30.990> company 00:54:31.490 --> 00:54:31.500 align:start position:0% various all sorts of other company 00:54:31.500 --> 00:54:34.490 align:start position:0% various all sorts of other company software<00:54:31.890> that<00:54:32.069> maybe<00:54:32.280> go<00:54:32.460> with<00:54:33.500> interfaces 00:54:34.490 --> 00:54:34.500 align:start position:0% software that maybe go with interfaces 00:54:34.500 --> 00:54:36.829 align:start position:0% software that maybe go with interfaces so<00:54:35.430> there's<00:54:35.640> just<00:54:35.700> a<00:54:36.060> lot<00:54:36.210> of<00:54:36.329> complexities 00:54:36.829 --> 00:54:36.839 align:start position:0% so there's just a lot of complexities 00:54:36.839 --> 00:54:38.120 align:start position:0% so there's just a lot of complexities and<00:54:36.960> a<00:54:37.020> lot<00:54:37.140> of<00:54:37.170> conversation<00:54:37.710> still<00:54:37.980> have 00:54:38.120 --> 00:54:38.130 align:start position:0% and a lot of conversation still have 00:54:38.130 --> 00:54:43.130 align:start position:0% and a lot of conversation still have around<00:54:38.310> what<00:54:38.910> is<00:54:40.490> so<00:54:41.490> what<00:54:41.819> committee<00:54:42.140> about 00:54:43.130 --> 00:54:43.140 align:start position:0% around what is so what committee about 00:54:43.140 --> 00:54:44.570 align:start position:0% around what is so what committee about the<00:54:43.319> ease 00:54:44.570 --> 00:54:44.580 align:start position:0% the ease 00:54:44.580 --> 00:54:47.530 align:start position:0% the ease since<00:54:44.970> issues<00:54:45.420> to<00:54:46.140> the<00:54:46.290> universe<00:54:46.650> of<00:54:46.980> the 00:54:47.530 --> 00:54:47.540 align:start position:0% since issues to the universe of the 00:54:47.540 --> 00:54:51.040 align:start position:0% since issues to the universe of the network<00:54:48.540> from<00:54:48.750> walking<00:54:49.110> because 00:54:51.040 --> 00:54:51.050 align:start position:0% network from walking because 00:54:51.050 --> 00:54:54.380 align:start position:0% network from walking because right<00:54:52.050> because<00:54:52.560> if<00:54:53.100> they<00:54:53.340> are<00:54:53.490> for<00:54:53.820> what<00:54:54.000> ve 00:54:54.380 --> 00:54:54.390 align:start position:0% right because if they are for what ve 00:54:54.390 --> 00:54:57.770 align:start position:0% right because if they are for what ve this<00:54:54.840> 20<00:54:55.380> premonitions<00:54:56.300> they<00:54:57.300> commence<00:54:57.600> would 00:54:57.770 --> 00:54:57.780 align:start position:0% this 20 premonitions they commence would 00:54:57.780 --> 00:54:59.540 align:start position:0% this 20 premonitions they commence would be<00:54:57.900> ready<00:54:58.110> Nations<00:54:58.530> the<00:54:58.950> ears<00:54:59.310> will<00:54:59.460> be 00:54:59.540 --> 00:54:59.550 align:start position:0% be ready Nations the ears will be 00:54:59.550 --> 00:55:01.580 align:start position:0% be ready Nations the ears will be written<00:54:59.850> about<00:54:59.940> assembly<00:55:00.600> right<00:55:01.140> so<00:55:01.350> there's 00:55:01.580 --> 00:55:01.590 align:start position:0% written about assembly right so there's 00:55:01.590 --> 00:55:03.440 align:start position:0% written about assembly right so there's a<00:55:01.650> like<00:55:02.220> there<00:55:02.400> is<00:55:02.490> no<00:55:02.610> notion<00:55:02.820> like<00:55:03.060> it<00:55:03.300> since 00:55:03.440 --> 00:55:03.450 align:start position:0% a like there is no notion like it since 00:55:03.450 --> 00:55:07.450 align:start position:0% a like there is no notion like it since ceremony<00:55:04.020> it's<00:55:04.530> just<00:55:04.740> the<00:55:05.310> code<00:55:05.580> that<00:55:05.850> runs 00:55:07.450 --> 00:55:07.460 align:start position:0% ceremony it's just the code that runs 00:55:07.460 --> 00:55:12.050 align:start position:0% ceremony it's just the code that runs okay<00:55:08.460> so<00:55:08.520> the<00:55:08.700> energies<00:55:09.060> have<00:55:10.760> yeah<00:55:11.760> it<00:55:11.940> gets 00:55:12.050 --> 00:55:12.060 align:start position:0% okay so the energies have yeah it gets 00:55:12.060 --> 00:55:13.610 align:start position:0% okay so the energies have yeah it gets to<00:55:12.270> a<00:55:12.300> point<00:55:12.330> to<00:55:12.630> the<00:55:12.810> beacon<00:55:13.080> pain<00:55:13.230> as<00:55:13.320> a<00:55:13.410> code 00:55:13.610 --> 00:55:13.620 align:start position:0% to a point to the beacon pain as a code 00:55:13.620 --> 00:55:18.350 align:start position:0% to a point to the beacon pain as a code it's<00:55:13.860> code 00:55:18.350 --> 00:55:18.360 align:start position:0% 00:55:18.360 --> 00:55:22.760 align:start position:0% it's<00:55:19.350> a<00:55:19.440> comment<00:55:20.960> so<00:55:21.960> I<00:55:21.990> understand<00:55:22.440> the<00:55:22.560> risk 00:55:22.760 --> 00:55:22.770 align:start position:0% it's a comment so I understand the risk 00:55:22.770 --> 00:55:25.880 align:start position:0% it's a comment so I understand the risk that<00:55:23.040> if<00:55:23.310> anybody<00:55:24.090> can<00:55:24.570> be<00:55:24.810> pleased<00:55:25.290> some<00:55:25.620> pain 00:55:25.880 --> 00:55:25.890 align:start position:0% that if anybody can be pleased some pain 00:55:25.890 --> 00:55:28.250 align:start position:0% that if anybody can be pleased some pain pulling<00:55:26.370> to<00:55:26.490> misuse<00:55:26.670> and<00:55:27.090> then<00:55:27.240> you<00:55:27.360> have<00:55:27.510> to 00:55:28.250 --> 00:55:28.260 align:start position:0% pulling to misuse and then you have to 00:55:28.260 --> 00:55:31.250 align:start position:0% pulling to misuse and then you have to stay<00:55:28.650> on<00:55:29.010> the<00:55:29.820> beacon<00:55:30.060> gene<00:55:30.270> there<00:55:30.480> was 00:55:31.250 --> 00:55:31.260 align:start position:0% stay on the beacon gene there was 00:55:31.260 --> 00:55:34.820 align:start position:0% stay on the beacon gene there was that<00:55:31.440> maybe<00:55:31.880> you<00:55:32.880> look<00:55:33.090> up<00:55:33.300> each<00:55:33.570> or<00:55:33.780> to<00:55:33.930> deploy 00:55:34.820 --> 00:55:34.830 align:start position:0% that maybe you look up each or to deploy 00:55:34.830 --> 00:55:38.510 align:start position:0% that maybe you look up each or to deploy it<00:55:35.040> yes<00:55:35.550> and<00:55:35.850> you<00:55:36.360> may<00:55:36.750> need<00:55:36.960> to<00:55:37.160> wear<00:55:38.160> time<00:55:38.340> you 00:55:38.510 --> 00:55:38.520 align:start position:0% it yes and you may need to wear time you 00:55:38.520 --> 00:55:39.920 align:start position:0% it yes and you may need to wear time you may<00:55:38.640> need<00:55:38.790> to<00:55:38.940> look<00:55:39.030> of<00:55:39.210> course<00:55:39.390> the<00:55:39.570> kind<00:55:39.840> of 00:55:39.920 --> 00:55:39.930 align:start position:0% may need to look of course the kind of 00:55:39.930 --> 00:55:41.810 align:start position:0% may need to look of course the kind of like<00:55:40.020> event<00:55:40.320> but<00:55:40.830> if<00:55:40.950> you<00:55:41.160> actually<00:55:41.370> burned 00:55:41.810 --> 00:55:41.820 align:start position:0% like event but if you actually burned 00:55:41.820 --> 00:55:44.500 align:start position:0% like event but if you actually burned that<00:55:42.000> then<00:55:42.390> it's<00:55:42.570> gonna<00:55:42.690> stay<00:55:42.960> there<00:55:43.020> forever 00:55:44.500 --> 00:55:44.510 align:start position:0% that then it's gonna stay there forever 00:55:44.510 --> 00:55:46.040 align:start position:0% that then it's gonna stay there forever if<00:55:44.780> there<00:55:45.050> should<00:55:45.080> be<00:55:45.320> something 00:55:46.040 --> 00:55:46.050 align:start position:0% if there should be something 00:55:46.050 --> 00:55:48.980 align:start position:0% if there should be something or<00:55:46.260> exploring<00:55:46.980> because<00:55:47.880> I'm<00:55:48.570> really<00:55:48.810> sure 00:55:48.980 --> 00:55:48.990 align:start position:0% or exploring because I'm really sure 00:55:48.990 --> 00:55:50.810 align:start position:0% or exploring because I'm really sure that<00:55:49.140> the<00:55:49.260> risk<00:55:49.470> one<00:55:50.040> of<00:55:50.130> the<00:55:50.190> risks<00:55:50.490> you<00:55:50.640> guys 00:55:50.810 --> 00:55:50.820 align:start position:0% that the risk one of the risks you guys 00:55:50.820 --> 00:55:53.000 align:start position:0% that the risk one of the risks you guys really<00:55:51.030> think<00:55:51.150> of<00:55:51.450> is<00:55:51.690> that<00:55:51.720> it's<00:55:52.320> blow<00:55:52.620> to<00:55:52.680> the 00:55:53.000 --> 00:55:53.010 align:start position:0% really think of is that it's blow to the 00:55:53.010 --> 00:55:57.200 align:start position:0% really think of is that it's blow to the engine<00:55:53.480> like<00:55:54.480> allowing<00:55:54.840> the<00:55:55.170> e's<00:55:55.940> which<00:55:56.940> may 00:55:57.200 --> 00:55:57.210 align:start position:0% engine like allowing the e's which may 00:55:57.210 --> 00:56:02.720 align:start position:0% engine like allowing the e's which may spell<00:55:57.830> intimacy<00:56:00.410> and<00:56:01.410> to<00:56:02.010> be<00:56:02.130> welcome<00:56:02.460> out<00:56:02.640> of 00:56:02.720 --> 00:56:02.730 align:start position:0% spell intimacy and to be welcome out of 00:56:02.730 --> 00:56:05.270 align:start position:0% spell intimacy and to be welcome out of the<00:56:02.820> room<00:56:03.570> as<00:56:03.840> long<00:56:03.870> as<00:56:04.140> other<00:56:04.620> participants 00:56:05.270 --> 00:56:05.280 align:start position:0% the room as long as other participants 00:56:05.280 --> 00:56:08.750 align:start position:0% the room as long as other participants and<00:56:05.900> pitch<00:56:06.900> em<00:56:07.080> to<00:56:07.260> lock<00:56:07.350> up<00:56:07.620> and<00:56:07.800> that<00:56:08.310> there's 00:56:08.750 --> 00:56:08.760 align:start position:0% and pitch em to lock up and that there's 00:56:08.760 --> 00:56:10.640 align:start position:0% and pitch em to lock up and that there's like<00:56:08.940> on<00:56:09.360> your<00:56:09.570> time<00:56:09.780> because<00:56:10.170> you<00:56:10.440> wouldn't 00:56:10.640 --> 00:56:10.650 align:start position:0% like on your time because you wouldn't 00:56:10.650 --> 00:56:14.570 align:start position:0% like on your time because you wouldn't want<00:56:10.830> to<00:56:11.040> eat<00:56:12.030> it<00:56:12.330> just<00:56:13.070> is<00:56:14.070> it<00:56:14.250> definitely 00:56:14.570 --> 00:56:14.580 align:start position:0% want to eat it just is it definitely 00:56:14.580 --> 00:56:16.130 align:start position:0% want to eat it just is it definitely zijn<00:56:14.730> you<00:56:14.820> throw<00:56:15.030> that<00:56:15.210> base<00:56:15.450> that<00:56:15.720> there 00:56:16.130 --> 00:56:16.140 align:start position:0% zijn you throw that base that there 00:56:16.140 --> 00:56:19.090 align:start position:0% zijn you throw that base that there might<00:56:16.290> be<00:56:16.320> a<00:56:16.470> funny<00:56:16.920> your<00:56:17.190> friend<00:56:17.660> actively 00:56:19.090 --> 00:56:19.100 align:start position:0% might be a funny your friend actively 00:56:19.100 --> 00:56:22.370 align:start position:0% might be a funny your friend actively operating<00:56:20.100> system<00:56:21.110> yeahbsolutely 00:56:22.370 --> 00:56:22.380 align:start position:0% operating system yeahbsolutely 00:56:22.380 --> 00:56:26.560 align:start position:0% operating system yeahbsolutely and<00:56:23.250> there<00:56:23.400> are<00:56:23.520> risks<00:56:23.880> like<00:56:24.150> an<00:56:24.270> exchange 00:56:26.560 --> 00:56:26.570 align:start position:0% 00:56:26.570 --> 00:56:31.040 align:start position:0% having<00:56:27.570> rap<00:56:27.930> teeth<00:56:28.910> as<00:56:29.910> you're<00:56:30.360> looking<00:56:30.780> as 00:56:31.040 --> 00:56:31.050 align:start position:0% having rap teeth as you're looking as 00:56:31.050 --> 00:56:32.810 align:start position:0% having rap teeth as you're looking as good<00:56:31.230> as<00:56:31.290> he<00:56:31.530> in<00:56:31.800> there<00:56:32.010> exchange<00:56:32.400> if<00:56:32.610> there's 00:56:32.810 --> 00:56:32.820 align:start position:0% good as he in there exchange if there's 00:56:32.820 --> 00:56:33.830 align:start position:0% good as he in there exchange if there's there<00:56:33.060> take<00:56:33.270> Congress 00:56:33.830 --> 00:56:33.840 align:start position:0% there take Congress 00:56:33.840 --> 00:56:38.210 align:start position:0% there take Congress I<00:56:35.900> mean<00:56:36.900> if<00:56:37.050> exchanges<00:56:37.620> are<00:56:37.740> gonna<00:56:37.860> create<00:56:38.130> a 00:56:38.210 --> 00:56:38.220 align:start position:0% I mean if exchanges are gonna create a 00:56:38.220 --> 00:56:44.090 align:start position:0% I mean if exchanges are gonna create a separate<00:56:38.610> token<00:56:39.000> for<00:56:39.210> beacon 00:56:44.090 --> 00:56:44.100 align:start position:0% 00:56:44.100 --> 00:56:50.980 align:start position:0% [Music] 00:56:50.980 --> 00:56:50.990 align:start position:0% 00:56:50.990 --> 00:56:53.840 align:start position:0% especially<00:56:51.990> given<00:56:52.170> a<00:56:52.440> dis<00:56:53.130> proposal<00:56:53.700> maybe 00:56:53.840 --> 00:56:53.850 align:start position:0% especially given a dis proposal maybe 00:56:53.850 --> 00:56:55.910 align:start position:0% especially given a dis proposal maybe the<00:56:54.150> different<00:56:54.510> user<00:56:55.080> be<00:56:55.260> synchronous<00:56:55.680> we 00:56:55.910 --> 00:56:55.920 align:start position:0% the different user be synchronous we 00:56:55.920 --> 00:57:01.010 align:start position:0% the different user be synchronous we prefer<00:56:56.190> multiple<00:56:56.670> children 00:57:01.010 --> 00:57:01.020 align:start position:0% 00:57:01.020 --> 00:57:02.910 align:start position:0% yes<00:57:01.619> but<00:57:01.890> then<00:57:02.040> it<00:57:02.190> doesn't<00:57:02.369> bargain 00:57:02.910 --> 00:57:02.920 align:start position:0% yes but then it doesn't bargain 00:57:02.920 --> 00:57:04.420 align:start position:0% yes but then it doesn't bargain [Music] 00:57:04.420 --> 00:57:04.430 align:start position:0% [Music] 00:57:04.430 --> 00:57:07.150 align:start position:0% [Music] but<00:57:04.970> nonetheless<00:57:05.420> let's<00:57:06.019> get<00:57:06.200> straight<00:57:06.380> away 00:57:07.150 --> 00:57:07.160 align:start position:0% but nonetheless let's get straight away 00:57:07.160 --> 00:57:15.730 align:start position:0% but nonetheless let's get straight away or<00:57:07.910> maybe<00:57:08.060> it<00:57:08.210> just<00:57:08.840> becomes<00:57:13.570> okay<00:57:14.740> either 00:57:15.730 --> 00:57:15.740 align:start position:0% or maybe it just becomes okay either 00:57:15.740 --> 00:57:19.280 align:start position:0% or maybe it just becomes okay either pound<00:57:16.190> said<00:57:16.700> like<00:57:16.880> outside 00:57:19.280 --> 00:57:19.290 align:start position:0% pound said like outside 00:57:19.290 --> 00:57:22.460 align:start position:0% pound said like outside we<00:57:19.770> go<00:57:19.920> hey<00:57:20.640> yeah<00:57:20.910> so<00:57:21.210> are<00:57:21.570> there<00:57:21.690> bounds<00:57:22.260> on 00:57:22.460 --> 00:57:22.470 align:start position:0% we go hey yeah so are there bounds on 00:57:22.470 --> 00:57:25.720 align:start position:0% we go hey yeah so are there bounds on he's<00:57:23.220> like<00:57:23.250> so<00:57:23.670> soon<00:57:23.910> we<00:57:24.120> can<00:57:24.270> deploy<00:57:24.540> our<00:57:24.690> own 00:57:25.720 --> 00:57:25.730 align:start position:0% he's like so soon we can deploy our own 00:57:25.730 --> 00:57:29.980 align:start position:0% he's like so soon we can deploy our own is<00:57:26.730> it<00:57:26.910> deterministic<00:57:27.510> you<00:57:28.290> sometime 00:57:29.980 --> 00:57:29.990 align:start position:0% is it deterministic you sometime 00:57:29.990 --> 00:57:32.390 align:start position:0% is it deterministic you sometime like<00:57:30.990> is<00:57:31.110> there<00:57:31.230> a<00:57:31.290> bound<00:57:31.590> or<00:57:31.890> there<00:57:32.280> was 00:57:32.390 --> 00:57:32.400 align:start position:0% like is there a bound or there was 00:57:32.400 --> 00:57:34.310 align:start position:0% like is there a bound or there was through<00:57:32.730> what<00:57:33.180> we're<00:57:33.510> assuming<00:57:33.780> that<00:57:34.020> got 00:57:34.310 --> 00:57:34.320 align:start position:0% through what we're assuming that got 00:57:34.320 --> 00:57:37.520 align:start position:0% through what we're assuming that got system-level<00:57:34.740> Castle<00:57:35.400> okay<00:57:35.790> that's<00:57:36.780> so<00:57:37.470> you 00:57:37.520 --> 00:57:37.530 align:start position:0% system-level Castle okay that's so you 00:57:37.530 --> 00:57:39.830 align:start position:0% system-level Castle okay that's so you could<00:57:37.740> deploy<00:57:38.040> any<00:57:38.370> that<00:57:38.970> like<00:57:39.210> say<00:57:39.480> just 00:57:39.830 --> 00:57:39.840 align:start position:0% could deploy any that like say just 00:57:39.840 --> 00:57:41.900 align:start position:0% could deploy any that like say just burns<00:57:40.410> your<00:57:40.650> computation<00:57:41.250> they<00:57:41.550> don't<00:57:41.730> know 00:57:41.900 --> 00:57:41.910 align:start position:0% burns your computation they don't know 00:57:41.910 --> 00:57:43.670 align:start position:0% burns your computation they don't know you<00:57:42.150> don't<00:57:42.300> be<00:57:42.480> able<00:57:42.630> to<00:57:42.690> make<00:57:42.780> a<00:57:42.810> block<00:57:43.110> on<00:57:43.500> it 00:57:43.670 --> 00:57:43.680 align:start position:0% you don't be able to make a block on it 00:57:43.680 --> 00:57:50.840 align:start position:0% you don't be able to make a block on it if<00:57:43.860> it<00:57:44.400> always<00:57:45.050> capital<00:57:46.050> the<00:57:46.140> gas<00:57:49.640> so<00:57:50.640> this 00:57:50.840 --> 00:57:50.850 align:start position:0% if it always capital the gas so this 00:57:50.850 --> 00:57:54.170 align:start position:0% if it always capital the gas so this issue<00:57:51.090> with<00:57:51.390> like<00:57:51.750> for<00:57:52.650> techies<00:57:53.180> potentially 00:57:54.170 --> 00:57:54.180 align:start position:0% issue with like for techies potentially 00:57:54.180 --> 00:57:56.180 align:start position:0% issue with like for techies potentially accumulating<00:57:54.870> on<00:57:55.050> the<00:57:55.110> Deccan<00:57:55.530> change<00:57:55.800> sounds 00:57:56.180 --> 00:57:56.190 align:start position:0% accumulating on the Deccan change sounds 00:57:56.190 --> 00:57:57.650 align:start position:0% accumulating on the Deccan change sounds like<00:57:56.370> you<00:57:56.610> might<00:57:56.790> just<00:57:57.030> want<00:57:57.210> to<00:57:57.300> go<00:57:57.390> to<00:57:57.540> the 00:57:57.650 --> 00:57:57.660 align:start position:0% like you might just want to go to the 00:57:57.660 --> 00:57:59.540 align:start position:0% like you might just want to go to the next<00:57:57.840> level<00:57:58.200> and<00:57:58.320> have<00:57:58.530> like<00:57:58.800> stateless 00:57:59.540 --> 00:57:59.550 align:start position:0% next level and have like stateless 00:57:59.550 --> 00:58:02.350 align:start position:0% next level and have like stateless beacon<00:57:59.910> chain<00:58:00.120> where<00:58:00.390> like<00:58:00.660> the<00:58:00.870> ultimate 00:58:02.350 --> 00:58:02.360 align:start position:0% beacon chain where like the ultimate 00:58:02.360 --> 00:58:06.220 align:start position:0% beacon chain where like the ultimate gonna<00:58:03.360> exist<00:58:03.570> somehow<00:58:04.020> access<00:58:04.560> events<00:58:04.920> feel<00:58:05.100> a 00:58:06.220 --> 00:58:06.230 align:start position:0% gonna exist somehow access events feel a 00:58:06.230 --> 00:58:08.870 align:start position:0% gonna exist somehow access events feel a computer<00:58:07.230> well<00:58:07.680> I<00:58:07.710> know<00:58:07.860> it's<00:58:08.460> more<00:58:08.670> about 00:58:08.870 --> 00:58:08.880 align:start position:0% computer well I know it's more about 00:58:08.880 --> 00:58:10.730 align:start position:0% computer well I know it's more about like<00:58:09.120> I<00:58:09.150> think<00:58:09.360> we<00:58:09.870> already<00:58:10.290> kind<00:58:10.530> of<00:58:10.590> like 00:58:10.730 --> 00:58:10.740 align:start position:0% like I think we already kind of like 00:58:10.740 --> 00:58:12.740 align:start position:0% like I think we already kind of like like<00:58:11.460> we've<00:58:11.670> seen<00:58:11.910> that<00:58:12.030> problem<00:58:12.240> happened 00:58:12.740 --> 00:58:12.750 align:start position:0% like we've seen that problem happened 00:58:12.750 --> 00:58:14.240 align:start position:0% like we've seen that problem happened before<00:58:13.080> you<00:58:13.290> know<00:58:13.410> what<00:58:13.590> the<00:58:13.710> stay<00:58:13.920> for<00:58:13.950> a 00:58:14.240 --> 00:58:14.250 align:start position:0% before you know what the stay for a 00:58:14.250 --> 00:58:16.430 align:start position:0% before you know what the stay for a blanket<00:58:14.760> but<00:58:15.060> I<00:58:15.300> feel<00:58:15.630> like<00:58:15.780> I<00:58:15.810> need<00:58:15.990> is<00:58:16.200> you<00:58:16.380> my 00:58:16.430 --> 00:58:16.440 align:start position:0% blanket but I feel like I need is you my 00:58:16.440 --> 00:58:18.770 align:start position:0% blanket but I feel like I need is you my opportunity<00:58:17.100> not<00:58:17.250> like<00:58:17.520> to<00:58:17.640> avoid<00:58:17.850> yeah<00:58:18.480> you 00:58:18.770 --> 00:58:18.780 align:start position:0% opportunity not like to avoid yeah you 00:58:18.780 --> 00:58:21.470 align:start position:0% opportunity not like to avoid yeah you can<00:58:18.930> make<00:58:19.080> the<00:58:19.770> tea<00:58:20.040> I<00:58:20.070> like<00:58:20.400> the<00:58:21.030> ideas<00:58:21.300> you 00:58:21.470 --> 00:58:21.480 align:start position:0% can make the tea I like the ideas you 00:58:21.480 --> 00:58:22.460 align:start position:0% can make the tea I like the ideas you generally<00:58:21.870> want<00:58:21.960> these<00:58:22.110> to<00:58:22.230> be<00:58:22.260> very 00:58:22.460 --> 00:58:22.470 align:start position:0% generally want these to be very 00:58:22.470 --> 00:58:24.260 align:start position:0% generally want these to be very expensive<00:58:22.680> and<00:58:23.010> you<00:58:23.130> wanted<00:58:23.400> a<00:58:23.490> I'm<00:58:24.030> show<00:58:24.210> you 00:58:24.260 --> 00:58:24.270 align:start position:0% expensive and you wanted a I'm show you 00:58:24.270 --> 00:58:27.290 align:start position:0% expensive and you wanted a I'm show you so<00:58:24.570> blocking<00:58:25.230> up<00:58:25.350> bounds<00:58:25.860> state<00:58:26.700> size<00:58:26.910> if 00:58:27.290 --> 00:58:27.300 align:start position:0% so blocking up bounds state size if 00:58:27.300 --> 00:58:29.390 align:start position:0% so blocking up bounds state size if there's<00:58:27.570> like<00:58:27.720> a<00:58:27.750> second<00:58:28.530> on<00:58:28.620> a<00:58:28.650> block<00:58:28.890> for 00:58:29.390 --> 00:58:29.400 align:start position:0% there's like a second on a block for 00:58:29.400 --> 00:58:32.270 align:start position:0% there's like a second on a block for size<00:58:29.910> 30<00:58:30.210> or<00:58:30.990> and<00:58:31.230> burning<00:58:31.560> also<00:58:31.740> found<00:58:32.100> this 00:58:32.270 --> 00:58:32.280 align:start position:0% size 30 or and burning also found this 00:58:32.280 --> 00:58:35.020 align:start position:0% size 30 or and burning also found this so<00:58:32.640> like<00:58:32.820> we<00:58:33.330> don't<00:58:33.540> explore<00:58:33.840> those<00:58:34.050> rather 00:58:35.020 --> 00:58:35.030 align:start position:0% so like we don't explore those rather 00:58:35.030 --> 00:58:36.850 align:start position:0% so like we don't explore those rather even<00:58:35.480> if<00:58:35.570> it<00:58:35.630> was<00:58:35.750> inexpensive<00:58:36.080> but<00:58:36.590> just<00:58:36.770> a 00:58:36.850 --> 00:58:36.860 align:start position:0% even if it was inexpensive but just a 00:58:36.860 --> 00:58:40.210 align:start position:0% even if it was inexpensive but just a fee<00:58:37.100> model<00:58:38.440> like<00:58:39.440> to<00:58:39.590> see<00:58:39.740> your<00:58:39.890> rent<00:58:40.070> or 00:58:40.210 --> 00:58:40.220 align:start position:0% fee model like to see your rent or 00:58:40.220 --> 00:58:42.840 align:start position:0% fee model like to see your rent or something<00:58:40.400> yeah<00:58:40.910> essentially<00:58:41.900> has<00:58:42.140> to<00:58:42.290> have 00:58:42.840 --> 00:58:42.850 align:start position:0% something yeah essentially has to have 00:58:42.850 --> 00:58:46.390 align:start position:0% something yeah essentially has to have is<00:58:43.850> the<00:58:44.000> bacon<00:58:44.270> chain<00:58:44.420> it<00:58:44.630> has<00:58:44.660> to<00:58:45.140> be<00:58:45.400> synced 00:58:46.390 --> 00:58:46.400 align:start position:0% is the bacon chain it has to be synced 00:58:46.400 --> 00:58:48.490 align:start position:0% is the bacon chain it has to be synced by<00:58:46.610> any<00:58:47.300> production<00:58:47.600> on<00:58:47.780> this<00:58:47.900> fully<00:58:48.110> sinking 00:58:48.490 --> 00:58:48.500 align:start position:0% by any production on this fully sinking 00:58:48.500 --> 00:58:49.960 align:start position:0% by any production on this fully sinking into<00:58:48.650> our<00:58:48.920> chains<00:58:49.130> they<00:58:49.340> have<00:58:49.520> to<00:58:49.670> sync<00:58:49.880> this 00:58:49.960 --> 00:58:49.970 align:start position:0% into our chains they have to sync this 00:58:49.970 --> 00:58:53.980 align:start position:0% into our chains they have to sync this component<00:58:50.450> server<00:58:51.400> yeah<00:58:52.400> like<00:58:52.940> if<00:58:53.119> we<00:58:53.300> set<00:58:53.869> it 00:58:53.980 --> 00:58:53.990 align:start position:0% component server yeah like if we set it 00:58:53.990 --> 00:58:56.470 align:start position:0% component server yeah like if we set it so<00:58:54.170> you<00:58:54.290> have<00:58:54.440> to<00:58:54.619> like<00:58:54.920> the<00:58:55.040> Walker<00:58:55.490> for<00:58:55.790> any 00:58:56.470 --> 00:58:56.480 align:start position:0% so you have to like the Walker for any 00:58:56.480 --> 00:58:58.359 align:start position:0% so you have to like the Walker for any ether<00:58:56.780> per<00:58:56.990> kilobyte<00:58:57.380> and<00:58:57.740> people<00:58:58.040> decide<00:58:58.340> to 00:58:58.359 --> 00:58:58.369 align:start position:0% ether per kilobyte and people decide to 00:58:58.369 --> 00:59:01.720 align:start position:0% ether per kilobyte and people decide to form<00:58:58.670> 30<00:58:59.000> 30<00:58:59.390> million<00:58:59.780> to<00:59:00.350> create<00:59:00.800> to<00:59:01.310> blow<00:59:01.550> the 00:59:01.720 --> 00:59:01.730 align:start position:0% form 30 30 million to create to blow the 00:59:01.730 --> 00:59:04.090 align:start position:0% form 30 30 million to create to blow the state<00:59:01.970> by<00:59:02.119> 30<00:59:02.390> gigabytes<00:59:02.750> that<00:59:03.140> I<00:59:03.500> think<00:59:04.010> you 00:59:04.090 --> 00:59:04.100 align:start position:0% state by 30 gigabytes that I think you 00:59:04.100 --> 00:59:12.110 align:start position:0% state by 30 gigabytes that I think you maximalist<00:59:04.670> a<00:59:04.760> lot<00:59:04.910> he<00:59:05.030> is<00:59:05.090> going<00:59:05.300> to<00:59:05.360> be 00:59:12.110 --> 00:59:12.120 align:start position:0% 00:59:12.120 --> 00:59:13.640 align:start position:0% which 00:59:13.640 --> 00:59:13.650 align:start position:0% which 00:59:13.650 --> 00:59:16.280 align:start position:0% which how<00:59:14.040> often<00:59:14.490> do<00:59:14.670> we<00:59:14.700> need<00:59:14.970> to<00:59:15.119> over<00:59:15.330> 70<00:59:15.990> design 00:59:16.280 --> 00:59:16.290 align:start position:0% how often do we need to over 70 design 00:59:16.290 --> 00:59:18.710 align:start position:0% how often do we need to over 70 design and<00:59:16.470> hope<00:59:16.590> and<00:59:16.800> business<00:59:17.130> meal 00:59:18.710 --> 00:59:18.720 align:start position:0% and hope and business meal 00:59:18.720 --> 00:59:21.480 align:start position:0% and hope and business meal so<00:59:19.720> here<00:59:20.260> like<00:59:20.590> these<00:59:20.770> are<00:59:20.980> just<00:59:21.220> crossing 00:59:21.480 --> 00:59:21.490 align:start position:0% so here like these are just crossing 00:59:21.490 --> 00:59:33.640 align:start position:0% so here like these are just crossing committees<00:59:22.180> so<00:59:22.390> they<00:59:22.540> adjust<00:59:22.660> everyone 00:59:33.640 --> 00:59:33.650 align:start position:0% 00:59:33.650 --> 00:59:37.599 align:start position:0% Willie<00:59:34.130> set<00:59:34.609> their<00:59:34.759> own<00:59:34.789> gas<00:59:36.069> that's<00:59:37.069> actually 00:59:37.599 --> 00:59:37.609 align:start position:0% Willie set their own gas that's actually 00:59:37.609 --> 00:59:39.549 align:start position:0% Willie set their own gas that's actually more<00:59:37.819> of<00:59:37.910> this<00:59:38.029> layer<00:59:38.299> one<00:59:38.509> concept<00:59:38.930> is<00:59:39.349> like 00:59:39.549 --> 00:59:39.559 align:start position:0% more of this layer one concept is like 00:59:39.559 --> 00:59:51.720 align:start position:0% more of this layer one concept is like the<00:59:40.069> gas<00:59:40.279> against<00:59:41.710> the<00:59:42.710> gas<00:59:42.920> limits<00:59:45.579> by<00:59:46.579> time 00:59:51.720 --> 00:59:51.730 align:start position:0% 00:59:51.730 --> 01:00:08.760 align:start position:0% when<00:59:52.089> launched<01:00:06.030> solid<01:00:07.230> we<01:00:08.230> have<01:00:08.349> all<01:00:08.500> sort<01:00:08.740> of 01:00:08.760 --> 01:00:08.770 align:start position:0% when launched solid we have all sort of 01:00:08.770 --> 01:00:14.490 align:start position:0% when launched solid we have all sort of stuff<01:00:08.950> moving<01:00:10.140> it's<01:00:11.140> moving<01:00:11.260> as<01:00:11.530> fast<01:00:13.349> we<01:00:14.349> have 01:00:14.490 --> 01:00:14.500 align:start position:0% stuff moving it's moving as fast we have 01:00:14.500 --> 01:00:22.230 align:start position:0% stuff moving it's moving as fast we have 64<01:00:15.040> choice<01:00:16.349> the<01:00:17.349> ultimately<01:00:17.920> this<01:00:21.000> and<01:00:22.000> one 01:00:22.230 --> 01:00:22.240 align:start position:0% 64 choice the ultimately this and one 01:00:22.240 --> 01:00:23.790 align:start position:0% 64 choice the ultimately this and one that<01:00:22.420> will<01:00:22.570> allow<01:00:22.930> some<01:00:23.230> good<01:00:23.470> things<01:00:23.680> out 01:00:23.790 --> 01:00:23.800 align:start position:0% that will allow some good things out 01:00:23.800 --> 01:00:26.099 align:start position:0% that will allow some good things out Bastion<01:00:24.250> seriously<01:00:25.089> similarly<01:00:25.720> with<01:00:25.960> the 01:00:26.099 --> 01:00:26.109 align:start position:0% Bastion seriously similarly with the 01:00:26.109 --> 01:00:32.089 align:start position:0% Bastion seriously similarly with the ease<01:00:26.260> it's<01:00:27.099> a<01:00:27.190> simple<01:00:27.460> blanket<01:00:27.609> rustles<01:00:28.150> so 01:00:32.089 --> 01:00:32.099 align:start position:0% 01:00:32.099 --> 01:00:35.130 align:start position:0% you<01:00:33.099> know<01:00:33.190> it<01:00:33.730> service<01:00:34.030> like<01:00:34.270> in<01:00:34.480> the<01:00:34.660> other 01:00:35.130 --> 01:00:35.140 align:start position:0% you know it service like in the other 01:00:35.140 --> 01:00:38.190 align:start position:0% you know it service like in the other reason<01:00:35.530> why<01:00:35.829> I<01:00:36.030> like<01:00:37.030> this<01:00:37.180> as<01:00:37.390> simplification 01:00:38.190 --> 01:00:38.200 align:start position:0% reason why I like this as simplification 01:00:38.200 --> 01:00:41.339 align:start position:0% reason why I like this as simplification games<01:00:38.440> like<01:00:38.770> basically<01:00:39.369> if<01:00:39.550> a<01:00:39.880> lot<01:00:40.660> of<01:00:40.960> kind<01:00:41.260> of 01:00:41.339 --> 01:00:41.349 align:start position:0% games like basically if a lot of kind of 01:00:41.349 --> 01:00:43.349 align:start position:0% games like basically if a lot of kind of sharp<01:00:41.650> chain<01:00:41.920> logic<01:00:42.430> that<01:00:42.730> we<01:00:42.849> have<01:00:42.970> been<01:00:43.119> kind 01:00:43.349 --> 01:00:43.359 align:start position:0% sharp chain logic that we have been kind 01:00:43.359 --> 01:00:44.700 align:start position:0% sharp chain logic that we have been kind of<01:00:43.420> wrangling<01:00:43.720> whatever<01:00:44.320> comes<01:00:44.530> unless 01:00:44.700 --> 01:00:44.710 align:start position:0% of wrangling whatever comes unless 01:00:44.710 --> 01:00:47.280 align:start position:0% of wrangling whatever comes unless needed<01:00:45.220> also<01:00:46.119> like<01:00:46.480> a<01:00:46.570> lot<01:00:46.720> of<01:00:46.810> groups<01:00:47.020> like 01:00:47.280 --> 01:00:47.290 align:start position:0% needed also like a lot of groups like 01:00:47.290 --> 01:00:49.079 align:start position:0% needed also like a lot of groups like this<01:00:47.410> crew<01:00:47.770> of<01:00:47.859> custody<01:00:48.250> complexity<01:00:48.880> can<01:00:49.060> be 01:00:49.079 --> 01:00:49.089 align:start position:0% this crew of custody complexity can be 01:00:49.089 --> 01:00:50.660 align:start position:0% this crew of custody complexity can be better<01:00:49.329> produced<01:00:49.810> down<01:00:50.020> further<01:00:50.320> because 01:00:50.660 --> 01:00:50.670 align:start position:0% better produced down further because 01:00:50.670 --> 01:00:53.190 align:start position:0% better produced down further because well<01:00:51.670> basically<01:00:51.940> you<01:00:52.450> would<01:00:52.780> be<01:00:52.930> able<01:00:52.990> to 01:00:53.190 --> 01:00:53.200 align:start position:0% well basically you would be able to 01:00:53.200 --> 01:00:55.620 align:start position:0% well basically you would be able to reduce<01:00:54.070> everything<01:00:54.460> to<01:00:54.670> a<01:00:54.820> single<01:00:55.270> kind<01:00:55.480> of 01:00:55.620 --> 01:00:55.630 align:start position:0% reduce everything to a single kind of 01:00:55.630 --> 01:00:57.089 align:start position:0% reduce everything to a single kind of front<01:00:55.869> groups<01:00:56.170> where<01:00:56.380> the<01:00:56.500> single<01:00:56.859> front 01:00:57.089 --> 01:00:57.099 align:start position:0% front groups where the single front 01:00:57.099 --> 01:00:59.490 align:start position:0% front groups where the single front group<01:00:57.369> is<01:00:57.550> it<01:00:57.700> just<01:00:57.880> is<01:00:58.109> importing<01:00:59.109> an<01:00:59.200> entire 01:00:59.490 --> 01:00:59.500 align:start position:0% group is it just is importing an entire 01:00:59.500 --> 01:01:00.550 align:start position:0% group is it just is importing an entire Charlotte 01:01:00.550 --> 01:01:00.560 align:start position:0% Charlotte 01:01:00.560 --> 01:01:02.410 align:start position:0% Charlotte and<01:01:00.650> chin<01:01:00.890> and<01:01:01.130> that's<01:01:01.820> something<01:01:02.090> that<01:01:02.240> was 01:01:02.410 --> 01:01:02.420 align:start position:0% and chin and that's something that was 01:01:02.420 --> 01:01:04.030 align:start position:0% and chin and that's something that was not<01:01:02.600> possible<01:01:02.810> with<01:01:03.110> cross-links<01:01:03.740> because 01:01:04.030 --> 01:01:04.040 align:start position:0% not possible with cross-links because 01:01:04.040 --> 01:01:05.860 align:start position:0% not possible with cross-links because across<01:01:04.250> was<01:01:04.730> just<01:01:04.910> too<01:01:05.030> big<01:01:05.210> a<01:01:05.390> importance<01:01:05.780> in 01:01:05.860 --> 01:01:05.870 align:start position:0% across was just too big a importance in 01:01:05.870 --> 01:01:07.800 align:start position:0% across was just too big a importance in the<01:01:05.930> beta<01:01:06.110> channel 01:01:07.800 --> 01:01:07.810 align:start position:0% the beta channel 01:01:07.810 --> 01:01:13.770 align:start position:0% the beta channel [Music] 01:01:13.770 --> 01:01:13.780 align:start position:0% 01:01:13.780 --> 01:01:16.380 align:start position:0% the<01:01:14.470> last<01:01:14.650> one<01:01:14.890> answered<01:01:15.340> have<01:01:15.520> a<01:01:15.550> Mississippi 01:01:16.380 --> 01:01:16.390 align:start position:0% the last one answered have a Mississippi 01:01:16.390 --> 01:01:16.830 align:start position:0% the last one answered have a Mississippi lesson 01:01:16.830 --> 01:01:16.840 align:start position:0% lesson 01:01:16.840 --> 01:01:18.330 align:start position:0% lesson what<01:01:16.960> will<01:01:17.110> the<01:01:17.200> transaction<01:01:17.860> throughput 01:01:18.330 --> 01:01:18.340 align:start position:0% what will the transaction throughput 01:01:18.340 --> 01:01:20.790 align:start position:0% what will the transaction throughput being<01:01:18.610> pressured<01:01:19.630> yeah 01:01:20.790 --> 01:01:20.800 align:start position:0% being pressured yeah 01:01:20.800 --> 01:01:23.640 align:start position:0% being pressured yeah so<01:01:21.010> I<01:01:21.520> mean<01:01:22.120> by<01:01:22.300> these<01:01:22.360> numbers<01:01:22.720> I<01:01:23.170> estimated 01:01:23.640 --> 01:01:23.650 align:start position:0% so I mean by these numbers I estimated 01:01:23.650 --> 01:01:26.010 align:start position:0% so I mean by these numbers I estimated at<01:01:24.400> one<01:01:24.580> point<01:01:24.820> for<01:01:25.150> me<01:01:25.330> it's<01:01:25.450> a<01:01:25.630> two<01:01:25.810> point 01:01:26.010 --> 01:01:26.020 align:start position:0% at one point for me it's a two point 01:01:26.020 --> 01:01:29.220 align:start position:0% at one point for me it's a two point seven<01:01:26.470> megabytes<01:01:27.010> per<01:01:27.160> second<01:01:27.790> of<01:01:27.940> data<01:01:28.050> so<01:01:29.050> if 01:01:29.220 --> 01:01:29.230 align:start position:0% seven megabytes per second of data so if 01:01:29.230 --> 01:01:31.860 align:start position:0% seven megabytes per second of data so if we<01:01:29.440> allow<01:01:29.740> like<01:01:30.280> computation<01:01:30.940> and<01:01:31.390> if<01:01:31.750> we 01:01:31.860 --> 01:01:31.870 align:start position:0% we allow like computation and if we 01:01:31.870 --> 01:01:35.340 align:start position:0% we allow like computation and if we assume<01:01:32.140> what<01:01:32.380> transaction<01:01:32.980> is<01:01:33.630> as<01:01:34.630> vehicle 01:01:35.340 --> 01:01:35.350 align:start position:0% assume what transaction is as vehicle 01:01:35.350 --> 01:01:38.010 align:start position:0% assume what transaction is as vehicle injured<01:01:35.620> bytes<01:01:35.860> and<01:01:36.280> that's<01:01:36.550> well<01:01:37.510> worth<01:01:37.840> a 01:01:38.010 --> 01:01:38.020 align:start position:0% injured bytes and that's well worth a 01:01:38.020 --> 01:01:42.170 align:start position:0% injured bytes and that's well worth a billion<01:01:38.230> divided<01:01:38.650> by<01:01:38.940> 30<01:01:39.970> that<01:01:40.180> was<01:01:40.300> good<01:01:40.510> but 01:01:42.170 --> 01:01:42.180 align:start position:0% billion divided by 30 that was good but 01:01:42.180 --> 01:01:44.730 align:start position:0% billion divided by 30 that was good but depends<01:01:43.180> on<01:01:43.300> the<01:01:43.390> construction<01:01:43.810> yes<01:01:44.170> all<01:01:44.650> the 01:01:44.730 --> 01:01:44.740 align:start position:0% depends on the construction yes all the 01:01:44.740 --> 01:01:46.170 align:start position:0% depends on the construction yes all the constructions<01:01:45.340> it<01:01:45.520> depends<01:01:45.850> on<01:01:45.910> whether<01:01:46.090> or 01:01:46.170 --> 01:01:46.180 align:start position:0% constructions it depends on whether or 01:01:46.180 --> 01:01:47.640 align:start position:0% constructions it depends on whether or not<01:01:46.240> you're<01:01:46.480> using<01:01:46.510> a<01:01:46.720> rollup<01:01:46.930> it<01:01:47.200> depends<01:01:47.530> on 01:01:47.640 --> 01:01:47.650 align:start position:0% not you're using a rollup it depends on 01:01:47.650 --> 01:01:50.840 align:start position:0% not you're using a rollup it depends on like<01:01:47.830> what<01:01:48.040> the<01:01:48.130> gas<01:01:48.280> do<01:01:48.550> many<01:01:49.140> people<01:01:50.140> write 01:01:50.840 --> 01:01:50.850 align:start position:0% like what the gas do many people write 01:01:50.850 --> 01:01:54.230 align:start position:0% like what the gas do many people write [Music] 01:01:54.230 --> 01:01:54.240 align:start position:0% 01:01:54.240 --> 01:01:57.750 align:start position:0% in<01:01:55.240> no<01:01:55.570> version<01:01:56.170> of<01:01:56.440> the<01:01:56.740> poses 01:01:57.750 --> 01:01:57.760 align:start position:0% in no version of the poses 01:01:57.760 --> 01:02:02.270 align:start position:0% in no version of the poses do<01:01:58.630> we<01:01:58.720> not<01:01:58.900> open<01:01:59.290> up 01:02:02.270 --> 01:02:02.280 align:start position:0% 01:02:02.280 --> 01:02:06.230 align:start position:0% I<01:02:02.330> also<01:02:03.330> I<01:02:03.960> just<01:02:04.530> I<01:02:05.040> just<01:02:05.160> want<01:02:05.670> to<01:02:05.730> speak<01:02:06.030> to 01:02:06.230 --> 01:02:06.240 align:start position:0% I also I just I just want to speak to 01:02:06.240 --> 01:02:10.320 align:start position:0% I also I just I just want to speak to the<01:02:06.330> two<01:02:06.570> ranges<01:02:07.470> of<01:02:07.650> it<01:02:07.800> I<01:02:07.830> don't<01:02:08.490> firmly 01:02:10.320 --> 01:02:10.330 align:start position:0% the two ranges of it I don't firmly 01:02:10.330 --> 01:02:13.170 align:start position:0% the two ranges of it I don't firmly [Music] 01:02:13.170 --> 01:02:13.180 align:start position:0% [Music] 01:02:13.180 --> 01:02:16.170 align:start position:0% [Music] and<01:02:13.539> they're<01:02:13.869> going<01:02:14.079> out<01:02:14.170> to<01:02:14.500> meet<01:02:14.799> up<01:02:15.760> to<01:02:15.940> have 01:02:16.170 --> 01:02:16.180 align:start position:0% and they're going out to meet up to have 01:02:16.180 --> 01:02:18.480 align:start position:0% and they're going out to meet up to have you<01:02:16.720> for<01:02:16.839> a<01:02:16.930> multi-state<01:02:17.680> it's<01:02:18.190> gonna<01:02:18.279> hold 01:02:18.480 --> 01:02:18.490 align:start position:0% you for a multi-state it's gonna hold 01:02:18.490 --> 01:02:30.870 align:start position:0% you for a multi-state it's gonna hold one<01:02:19.020> it's<01:02:20.020> a<01:02:28.980> yeah<01:02:29.980> so<01:02:30.190> when<01:02:30.309> you<01:02:30.369> make<01:02:30.520> a<01:02:30.549> block 01:02:30.870 --> 01:02:30.880 align:start position:0% one it's a yeah so when you make a block 01:02:30.880 --> 01:02:33.000 align:start position:0% one it's a yeah so when you make a block you'd<01:02:31.089> probably<01:02:31.299> specify<01:02:31.930> what<01:02:32.380> he<01:02:32.440> eats<01:02:32.650> or 01:02:33.000 --> 01:02:33.010 align:start position:0% you'd probably specify what he eats or 01:02:33.010 --> 01:02:34.710 align:start position:0% you'd probably specify what he eats or or<01:02:33.190> what<01:02:33.339> side<01:02:33.579> of<01:02:33.609> BT's<01:02:34.000> and<01:02:34.270> that<01:02:34.569> would 01:02:34.710 --> 01:02:34.720 align:start position:0% or what side of BT's and that would 01:02:34.720 --> 01:02:41.870 align:start position:0% or what side of BT's and that would interpret<01:02:34.990> the<01:02:35.319> block<01:02:35.500> data<01:02:35.740> as<01:02:36.069> such<01:02:36.279> against 01:02:41.870 --> 01:02:41.880 align:start position:0% 01:02:41.880 --> 01:02:44.339 align:start position:0% likely<01:02:42.880> be<01:02:43.029> asynchronous<01:02:43.599> on<01:02:44.020> the<01:02:44.109> order 01:02:44.339 --> 01:02:44.349 align:start position:0% likely be asynchronous on the order 01:02:44.349 --> 01:02:48.260 align:start position:0% likely be asynchronous on the order block<01:02:45.900> sloppiness<01:02:46.900> proposal<01:02:47.500> but<01:02:47.650> there's 01:02:48.260 --> 01:02:48.270 align:start position:0% block sloppiness proposal but there's 01:02:48.270 --> 01:02:51.660 align:start position:0% block sloppiness proposal but there's there's<01:02:49.270> definitely<01:02:49.750> room<01:02:49.809> to<01:02:50.109> discuss<01:02:50.670> intra 01:02:51.660 --> 01:02:51.670 align:start position:0% there's definitely room to discuss intra 01:02:51.670 --> 01:02:59.940 align:start position:0% there's definitely room to discuss intra be<01:02:52.450> within<01:02:52.990> lunch<01:02:53.319> our<01:02:56.700> last<01:02:57.700> question<01:02:58.950> tiny 01:02:59.940 --> 01:02:59.950 align:start position:0% be within lunch our last question tiny 01:02:59.950 --> 01:03:02.549 align:start position:0% be within lunch our last question tiny about<01:03:00.369> other<01:03:00.970> pups<01:03:01.240> epistles<01:03:01.690> of<01:03:01.750> Paul<01:03:02.020> talks 01:03:02.549 --> 01:03:02.559 align:start position:0% about other pups epistles of Paul talks 01:03:02.559 --> 01:03:08.790 align:start position:0% about other pups epistles of Paul talks about<01:03:05.730> this<01:03:06.730> today 01:03:08.790 --> 01:03:08.800 align:start position:0% about this today 01:03:08.800 --> 01:03:12.370 align:start position:0% about this today validators<01:03:09.800> don't<01:03:10.040> select<01:03:10.340> a<01:03:11.050> variable<01:03:12.050> oh 01:03:12.370 --> 01:03:12.380 align:start position:0% validators don't select a variable oh 01:03:12.380 --> 01:03:15.100 align:start position:0% validators don't select a variable oh yeah<01:03:12.760> so<01:03:13.760> I<01:03:14.000> don't<01:03:14.330> seem<01:03:14.450> like<01:03:14.690> you're<01:03:14.870> running 01:03:15.100 --> 01:03:15.110 align:start position:0% yeah so I don't seem like you're running 01:03:15.110 --> 01:03:21.540 align:start position:0% yeah so I don't seem like you're running to<01:03:15.380> your<01:03:15.560> ease<01:03:16.480> right<01:03:17.510> how<01:03:18.080> does<01:03:18.850> ostracize<01:03:19.850> me 01:03:21.540 --> 01:03:21.550 align:start position:0% to your ease right how does ostracize me 01:03:21.550 --> 01:03:25.330 align:start position:0% to your ease right how does ostracize me yeah<01:03:22.550> so<01:03:22.910> I<01:03:22.940> mean<01:03:23.120> if<01:03:23.240> you're<01:03:23.450> it's<01:03:24.440> it's<01:03:24.740> a 01:03:25.330 --> 01:03:25.340 align:start position:0% yeah so I mean if you're it's it's a 01:03:25.340 --> 01:03:28.780 align:start position:0% yeah so I mean if you're it's it's a free<01:03:26.000> market<01:03:26.420> so<01:03:26.690> in<01:03:27.050> general<01:03:27.830> like<01:03:28.070> if<01:03:28.340> say 01:03:28.780 --> 01:03:28.790 align:start position:0% free market so in general like if say 01:03:28.790 --> 01:03:31.360 align:start position:0% free market so in general like if say one<01:03:29.420> block<01:03:29.690> can<01:03:29.930> have<01:03:30.080> one<01:03:30.470> evening<01:03:30.920> there<01:03:31.310> are 01:03:31.360 --> 01:03:31.370 align:start position:0% one block can have one evening there are 01:03:31.370 --> 01:03:33.720 align:start position:0% one block can have one evening there are very<01:03:31.610> high<01:03:31.790> about<01:03:31.970> a<01:03:32.030> beauty<01:03:32.480> store<01:03:32.630> lots<01:03:32.810> and 01:03:33.720 --> 01:03:33.730 align:start position:0% very high about a beauty store lots and 01:03:33.730 --> 01:03:36.400 align:start position:0% very high about a beauty store lots and lots<01:03:34.730> of<01:03:34.820> hiding<01:03:35.210> transactions<01:03:35.750> was<01:03:35.930> being 01:03:36.400 --> 01:03:36.410 align:start position:0% lots of hiding transactions was being 01:03:36.410 --> 01:03:38.880 align:start position:0% lots of hiding transactions was being picked<01:03:36.530> up<01:03:36.680> more<01:03:36.920> than<01:03:37.190> say<01:03:37.790> an<01:03:38.390> underutilized 01:03:38.880 --> 01:03:38.890 align:start position:0% picked up more than say an underutilized 01:03:38.890 --> 01:03:42.130 align:start position:0% picked up more than say an underutilized might<01:03:39.890> only<01:03:40.490> have<01:03:40.820> demand<01:03:41.270> to<01:03:41.480> be<01:03:41.630> processed 01:03:42.130 --> 01:03:42.140 align:start position:0% might only have demand to be processed 01:03:42.140 --> 01:03:44.200 align:start position:0% might only have demand to be processed every<01:03:42.410> handful<01:03:42.650> block<01:03:42.980> so<01:03:43.250> but<01:03:43.610> that<01:03:43.790> the 01:03:44.200 --> 01:03:44.210 align:start position:0% every handful block so but that the 01:03:44.210 --> 01:03:46.570 align:start position:0% every handful block so but that the actual<01:03:44.900> mechanics<01:03:45.290> are<01:03:45.440> there<01:03:45.590> but<01:03:46.280> wouldn't 01:03:46.570 --> 01:03:46.580 align:start position:0% actual mechanics are there but wouldn't 01:03:46.580 --> 01:03:50.350 align:start position:0% actual mechanics are there but wouldn't that<01:03:46.610> just<01:03:46.730> needed<01:03:47.150> an<01:03:47.750> illogical<01:03:48.140> team<01:03:49.360> not 01:03:50.350 --> 01:03:50.360 align:start position:0% that just needed an illogical team not 01:03:50.360 --> 01:03:53.230 align:start position:0% that just needed an illogical team not necessarily<01:03:50.930> and<01:03:51.140> the<01:03:51.680> that<01:03:52.550> was<01:03:52.760> an<01:03:52.910> extreme 01:03:53.230 --> 01:03:53.240 align:start position:0% necessarily and the that was an extreme 01:03:53.240 --> 01:03:54.790 align:start position:0% necessarily and the that was an extreme case<01:03:53.420> where<01:03:53.450> we<01:03:53.750> just<01:03:53.780> have<01:03:54.110> one<01:03:54.290> eating<01:03:54.590> her 01:03:54.790 --> 01:03:54.800 align:start position:0% case where we just have one eating her 01:03:54.800 --> 01:03:56.920 align:start position:0% case where we just have one eating her but<01:03:55.100> if<01:03:55.310> you<01:03:55.460> allow<01:03:55.760> multiple<01:03:56.060> easier<01:03:56.660> than 01:03:56.920 --> 01:03:56.930 align:start position:0% but if you allow multiple easier than 01:03:56.930 --> 01:03:58.450 align:start position:0% but if you allow multiple easier than yet<01:03:57.200> likely<01:03:57.620> like<01:03:57.770> you<01:03:57.890> might<01:03:58.070> fill<01:03:58.220> in<01:03:58.370> the 01:03:58.450 --> 01:03:58.460 align:start position:0% yet likely like you might fill in the 01:03:58.460 --> 01:04:05.230 align:start position:0% yet likely like you might fill in the gaps<01:03:58.640> at<01:03:58.880> the<01:03:58.970> end<01:03:59.120> with<01:03:59.330> like<01:03:59.680> underutilized 01:04:05.230 --> 01:04:05.240 align:start position:0% 01:04:05.240 --> 01:04:07.849 align:start position:0% but<01:04:06.240> actual<01:04:06.660> last<01:04:06.839> question<01:04:07.230> but<01:04:07.349> is<01:04:07.500> it<01:04:07.770> I 01:04:07.849 --> 01:04:07.859 align:start position:0% but actual last question but is it I 01:04:07.859 --> 01:04:10.010 align:start position:0% but actual last question but is it I mean<01:04:08.010> is<01:04:08.130> there<01:04:08.490> rinsing<01:04:08.880> would<01:04:09.059> like<01:04:09.720> to<01:04:09.900> be 01:04:10.010 --> 01:04:10.020 align:start position:0% mean is there rinsing would like to be 01:04:10.020 --> 01:04:12.890 align:start position:0% mean is there rinsing would like to be saying<01:04:10.260> that<01:04:10.470> to<01:04:10.849> the<01:04:11.849> crystal<01:04:12.180> isn't<01:04:12.270> sponsor 01:04:12.890 --> 01:04:12.900 align:start position:0% saying that to the crystal isn't sponsor 01:04:12.900 --> 01:04:15.140 align:start position:0% saying that to the crystal isn't sponsor clock<01:04:13.140> so<01:04:13.440> it's<01:04:13.920> proportional<01:04:14.099> to<01:04:14.730> the<01:04:14.819> amount 01:04:15.140 --> 01:04:15.150 align:start position:0% clock so it's proportional to the amount 01:04:15.150 --> 01:04:17.230 align:start position:0% clock so it's proportional to the amount of<01:04:15.390> contact 01:04:17.230 --> 01:04:17.240 align:start position:0% of contact 01:04:17.240 --> 01:04:21.170 align:start position:0% of contact that's<01:04:18.240> not<01:04:18.450> well<01:04:19.140> everyone<01:04:19.589> so<01:04:19.859> if<01:04:20.849> a 01:04:21.170 --> 01:04:21.180 align:start position:0% that's not well everyone so if a 01:04:21.180 --> 01:04:24.880 align:start position:0% that's not well everyone so if a proposer<01:04:21.829> similar<01:04:22.829> to<01:04:23.040> oppose<01:04:23.910> or<01:04:24.059> anyone 01:04:24.880 --> 01:04:24.890 align:start position:0% proposer similar to oppose or anyone 01:04:24.890 --> 01:04:27.859 align:start position:0% proposer similar to oppose or anyone gets<01:04:25.890> to<01:04:26.220> kind<01:04:26.609> of<01:04:26.700> bundle<01:04:26.880> things<01:04:27.240> in<01:04:27.420> as<01:04:27.720> they 01:04:27.859 --> 01:04:27.869 align:start position:0% gets to kind of bundle things in as they 01:04:27.869 --> 01:04:29.480 align:start position:0% gets to kind of bundle things in as they see<01:04:27.930> fit 01:04:29.480 --> 01:04:29.490 align:start position:0% see fit 01:04:29.490 --> 01:04:31.460 align:start position:0% see fit it's<01:04:29.940> not<01:04:30.119> a<01:04:30.150> matter<01:04:30.480> of<01:04:30.599> like<01:04:30.900> all<01:04:31.170> the<01:04:31.290> other 01:04:31.460 --> 01:04:31.470 align:start position:0% it's not a matter of like all the other 01:04:31.470 --> 01:04:33.530 align:start position:0% it's not a matter of like all the other validators<01:04:31.859> coming<01:04:32.130> in<01:04:32.220> on<01:04:32.339> coating<01:04:32.670> you're 01:04:33.530 --> 01:04:33.540 align:start position:0% validators coming in on coating you're 01:04:33.540 --> 01:04:37.849 align:start position:0% validators coming in on coating you're not<01:04:33.780> so<01:04:34.140> but<01:04:35.099> again<01:04:35.220> if<01:04:36.059> you're<01:04:36.300> in<01:04:36.450> a<01:04:36.859> very 01:04:37.849 --> 01:04:37.859 align:start position:0% not so but again if you're in a very 01:04:37.859 --> 01:04:40.010 align:start position:0% not so but again if you're in a very underlip<01:04:38.400> utilize<01:04:38.760> e<01:04:38.790> you<01:04:39.240> might<01:04:39.420> pay<01:04:39.660> so<01:04:39.720> very 01:04:40.010 --> 01:04:40.020 align:start position:0% underlip utilize e you might pay so very 01:04:40.020 --> 01:04:43.309 align:start position:0% underlip utilize e you might pay so very high<01:04:40.260> i<01:04:41.270> receive<01:04:42.270> it<01:04:42.450> will<01:04:42.720> check<01:04:42.869> if<01:04:43.079> that's 01:04:43.309 --> 01:04:43.319 align:start position:0% high i receive it will check if that's 01:04:43.319 --> 01:04:50.500 align:start position:0% high i receive it will check if that's somebody<01:04:43.530> include<01:04:47.180> it's<01:04:48.180> almost<01:04:48.450> thing<01:04:49.079> that 01:04:50.500 --> 01:04:50.510 align:start position:0% somebody include it's almost thing that 01:04:50.510 --> 01:04:53.830 align:start position:0% somebody include it's almost thing that those<01:04:50.840> bees<01:04:51.470> have<01:04:52.400> some<01:04:52.640> kind<01:04:52.850> of<01:04:52.880> catch<01:04:53.150> to 01:04:53.830 --> 01:04:53.840 align:start position:0% those bees have some kind of catch to 01:04:53.840 --> 01:04:55.120 align:start position:0% those bees have some kind of catch to save<01:04:53.870> on<01:04:54.290> local<01:04:54.710> boost 01:04:55.120 --> 01:04:55.130 align:start position:0% save on local boost 01:04:55.130 --> 01:04:58.310 align:start position:0% save on local boost I<01:04:55.490> was<01:04:55.850> just<01:04:55.970> wondering<01:04:56.330> how<01:04:56.740> this 01:04:58.310 --> 01:04:58.320 align:start position:0% I was just wondering how this 01:04:58.320 --> 01:05:02.630 align:start position:0% I was just wondering how this [Music] 01:05:02.630 --> 01:05:02.640 align:start position:0% 01:05:02.640 --> 01:05:07.799 align:start position:0% and<01:05:03.640> this<01:05:03.849> proposal<01:05:04.270> indefinitely<01:05:05.079> I<01:05:05.349> do<01:05:06.809> it 01:05:07.799 --> 01:05:07.809 align:start position:0% and this proposal indefinitely I do it 01:05:07.809 --> 01:05:10.980 align:start position:0% and this proposal indefinitely I do it reduces<01:05:08.470> the<01:05:08.680> amounts<01:05:09.280> of<01:05:09.369> kind<01:05:09.670> of<01:05:09.990> crossable 01:05:10.980 --> 01:05:10.990 align:start position:0% reduces the amounts of kind of crossable 01:05:10.990 --> 01:05:13.440 align:start position:0% reduces the amounts of kind of crossable locks<01:05:11.290> a<01:05:11.589> thing<01:05:11.859> that<01:05:12.160> you<01:05:12.250> can<01:05:12.460> do<01:05:12.640> but<01:05:12.940> like 01:05:13.440 --> 01:05:13.450 align:start position:0% locks a thing that you can do but like 01:05:13.450 --> 01:05:15.480 align:start position:0% locks a thing that you can do but like you<01:05:13.960> get<01:05:14.170> some<01:05:14.410> of<01:05:14.559> the<01:05:14.650> benefits<01:05:15.040> back<01:05:15.220> you 01:05:15.480 --> 01:05:15.490 align:start position:0% you get some of the benefits back you 01:05:15.490 --> 01:05:17.339 align:start position:0% you get some of the benefits back you penciling<01:05:15.880> the<01:05:16.059> one<01:05:16.240> good<01:05:16.660> your<01:05:16.839> wife's<01:05:17.079> get 01:05:17.339 --> 01:05:17.349 align:start position:0% penciling the one good your wife's get 01:05:17.349 --> 01:05:21.180 align:start position:0% penciling the one good your wife's get bigger<01:05:18.660> so<01:05:19.660> but<01:05:20.200> they<01:05:20.380> in<01:05:20.680> terms<01:05:20.920> of<01:05:21.040> like 01:05:21.180 --> 01:05:21.190 align:start position:0% bigger so but they in terms of like 01:05:21.190 --> 01:05:23.280 align:start position:0% bigger so but they in terms of like having<01:05:21.430> it<01:05:21.670> the<01:05:21.790> cash<01:05:22.000> generally<01:05:22.809> we<01:05:22.960> usually 01:05:23.280 --> 01:05:23.290 align:start position:0% having it the cash generally we usually 01:05:23.290 --> 01:05:26.130 align:start position:0% having it the cash generally we usually think<01:05:23.410> of<01:05:23.559> these<01:05:23.740> as<01:05:23.859> having<01:05:24.520> like<01:05:25.089> a<01:05:25.359> stapler 01:05:26.130 --> 01:05:26.140 align:start position:0% think of these as having like a stapler 01:05:26.140 --> 01:05:30.589 align:start position:0% think of these as having like a stapler 32<01:05:26.589> bytes<01:05:26.799> per<01:05:27.160> chart<01:05:27.609> but<01:05:28.510> we've<01:05:29.099> discussed 01:05:30.589 --> 01:05:30.599 align:start position:0% 32 bytes per chart but we've discussed 01:05:30.599 --> 01:05:32.970 align:start position:0% 32 bytes per chart but we've discussed option<01:05:31.599> opportunity<01:05:32.170> of<01:05:32.290> like<01:05:32.470> when 01:05:32.970 --> 01:05:32.980 align:start position:0% option opportunity of like when 01:05:32.980 --> 01:05:34.380 align:start position:0% option opportunity of like when deploying<01:05:33.339> the<01:05:33.579> e<01:05:33.609> depending<01:05:34.119> on<01:05:34.210> the<01:05:34.270> amount 01:05:34.380 --> 01:05:34.390 align:start position:0% deploying the e depending on the amount 01:05:34.390 --> 01:05:36.329 align:start position:0% deploying the e depending on the amount of<01:05:34.480> capital<01:05:34.660> of<01:05:34.990> earned<01:05:35.410> like<01:05:35.710> you<01:05:36.190> can 01:05:36.329 --> 01:05:36.339 align:start position:0% of capital of earned like you can 01:05:36.339 --> 01:05:38.549 align:start position:0% of capital of earned like you can specify<01:05:36.609> you<01:05:37.510> know<01:05:37.569> state<01:05:37.869> refer<01:05:38.140> short<01:05:38.380> or 01:05:38.549 --> 01:05:38.559 align:start position:0% specify you know state refer short or 01:05:38.559 --> 01:05:40.020 align:start position:0% specify you know state refer short or maybe<01:05:38.710> like<01:05:38.980> some<01:05:39.190> larger<01:05:39.549> chunk<01:05:39.790> of<01:05:39.880> data 01:05:40.020 --> 01:05:40.030 align:start position:0% maybe like some larger chunk of data 01:05:40.030 --> 01:05:41.549 align:start position:0% maybe like some larger chunk of data which<01:05:40.270> means<01:05:40.450> that<01:05:40.569> being<01:05:40.869> like<01:05:41.079> it<01:05:41.230> like<01:05:41.410> my 01:05:41.549 --> 01:05:41.559 align:start position:0% which means that being like it like my 01:05:41.559 --> 01:05:45.420 align:start position:0% which means that being like it like my cash<01:05:42.450> so<01:05:43.450> that's<01:05:44.290> still<01:05:44.650> kind<01:05:45.190> of<01:05:45.250> up<01:05:45.400> to 01:05:45.420 --> 01:05:45.430 align:start position:0% cash so that's still kind of up to 01:05:45.430 --> 01:05:46.920 align:start position:0% cash so that's still kind of up to debate<01:05:45.790> the<01:05:45.970> actual<01:05:46.240> mechanics<01:05:46.690> and 01:05:46.920 --> 01:05:46.930 align:start position:0% debate the actual mechanics and 01:05:46.930 --> 01:05:48.329 align:start position:0% debate the actual mechanics and economics<01:05:47.619> around<01:05:47.710> how<01:05:47.890> these<01:05:48.010> things<01:05:48.190> relate 01:05:48.329 --> 01:05:48.339 align:start position:0% economics around how these things relate 01:05:48.339 --> 01:05:53.010 align:start position:0% economics around how these things relate but<01:05:48.790> it's<01:05:49.420> something<01:05:49.780> we're<01:05:50.079> definitely<01:05:52.020> I 01:05:53.010 --> 01:05:53.020 align:start position:0% but it's something we're definitely I 01:05:53.020 --> 01:05:54.660 align:start position:0% but it's something we're definitely I think<01:05:53.440> we're<01:05:53.530> gonna<01:05:53.619> call<01:05:53.770> it<01:05:53.950> cuz<01:05:54.549> I<01:05:54.579> think 01:05:54.660 --> 01:05:54.670 align:start position:0% think we're gonna call it cuz I think 01:05:54.670 --> 01:06:02.320 align:start position:0% think we're gonna call it cuz I think we're<01:05:54.849> over<01:05:54.970> time<01:05:55.510> and<01:05:56.280> great 01:06:02.320 --> 01:06:02.330 align:start position:0% 01:06:02.330 --> 01:06:09.390 align:start position:0% [Applause] 01:06:09.390 --> 01:06:09.400 align:start position:0% 01:06:09.400 --> 01:06:11.460 align:start position:0% you