WEBVTT Kind: captions Language: en 00:00:04.910 --> 00:00:09.440 align:start position:0% so<00:00:05.910> I'm<00:00:06.029> here<00:00:06.240> to<00:00:06.390> talk<00:00:06.540> about<00:00:07.700> the<00:00:08.700> data 00:00:09.440 --> 00:00:09.450 align:start position:0% so I'm here to talk about the data 00:00:09.450 --> 00:00:11.119 align:start position:0% so I'm here to talk about the data availability<00:00:09.990> and<00:00:10.289> validity<00:00:10.559> scheme<00:00:11.010> in 00:00:11.119 --> 00:00:11.129 align:start position:0% availability and validity scheme in 00:00:11.129 --> 00:00:15.260 align:start position:0% availability and validity scheme in polkadot<00:00:13.190> now<00:00:14.190> this<00:00:14.340> this<00:00:14.549> talk<00:00:14.760> is<00:00:14.879> probably 00:00:15.260 --> 00:00:15.270 align:start position:0% polkadot now this this talk is probably 00:00:15.270 --> 00:00:17.450 align:start position:0% polkadot now this this talk is probably a<00:00:15.359> bit<00:00:15.719> technical<00:00:15.990> for<00:00:16.289> the<00:00:16.500> main<00:00:16.650> stage<00:00:16.920> in<00:00:17.130> 15 00:00:17.450 --> 00:00:17.460 align:start position:0% a bit technical for the main stage in 15 00:00:17.460 --> 00:00:21.440 align:start position:0% a bit technical for the main stage in 15 minutes<00:00:17.789> at<00:00:17.910> 9<00:00:18.090> a.m.<00:00:20.030> you<00:00:21.030> end<00:00:21.150> up<00:00:21.240> going<00:00:21.330> to 00:00:21.440 --> 00:00:21.450 align:start position:0% minutes at 9 a.m. you end up going to 00:00:21.450 --> 00:00:26.150 align:start position:0% minutes at 9 a.m. you end up going to sleep<00:00:21.690> it's<00:00:22.289> still<00:00:22.470> fine<00:00:22.650> but<00:00:24.740> I'm<00:00:25.740> sorry<00:00:26.010> I'm 00:00:26.150 --> 00:00:26.160 align:start position:0% sleep it's still fine but I'm sorry I'm 00:00:26.160 --> 00:00:28.880 align:start position:0% sleep it's still fine but I'm sorry I'm gonna<00:00:26.220> try<00:00:26.520> and<00:00:26.640> explain<00:00:26.850> this<00:00:27.030> so<00:00:27.990> what<00:00:28.740> do<00:00:28.830> we 00:00:28.880 --> 00:00:28.890 align:start position:0% gonna try and explain this so what do we 00:00:28.890 --> 00:00:34.660 align:start position:0% gonna try and explain this so what do we mean<00:00:29.220> by<00:00:32.629> data<00:00:33.629> availability<00:00:34.020> and<00:00:34.320> validity 00:00:34.660 --> 00:00:34.670 align:start position:0% mean by data availability and validity 00:00:34.670 --> 00:00:36.740 align:start position:0% mean by data availability and validity so<00:00:35.670> in<00:00:35.789> particular<00:00:35.910> what<00:00:36.329> we're<00:00:36.480> talking 00:00:36.740 --> 00:00:36.750 align:start position:0% so in particular what we're talking 00:00:36.750 --> 00:00:42.010 align:start position:0% so in particular what we're talking about<00:00:36.899> about<00:00:37.200> blocks<00:00:37.890> in<00:00:38.130> a<00:00:38.510> chartered<00:00:39.510> system 00:00:42.010 --> 00:00:42.020 align:start position:0% 00:00:42.020 --> 00:00:49.490 align:start position:0% so<00:00:43.020> if<00:00:43.440> you<00:00:43.620> have<00:00:43.860> a<00:00:46.190> single<00:00:47.190> chain<00:00:48.140> like<00:00:49.140> a 00:00:49.490 --> 00:00:49.500 align:start position:0% so if you have a single chain like a 00:00:49.500 --> 00:00:53.389 align:start position:0% so if you have a single chain like a theory<00:00:50.040> 1.0<00:00:50.670> or<00:00:51.950> Bitcoin<00:00:52.950> if<00:00:53.130> we<00:00:53.219> have<00:00:53.370> a 00:00:53.389 --> 00:00:53.399 align:start position:0% theory 1.0 or Bitcoin if we have a 00:00:53.399 --> 00:00:56.479 align:start position:0% theory 1.0 or Bitcoin if we have a header<00:00:53.700> and<00:00:53.940> the<00:00:54.540> block<00:00:54.750> doesn't<00:00:55.020> exist<00:00:55.489> then 00:00:56.479 --> 00:00:56.489 align:start position:0% header and the block doesn't exist then 00:00:56.489 --> 00:00:58.280 align:start position:0% header and the block doesn't exist then like<00:00:56.640> that<00:00:56.820> people<00:00:57.149> people<00:00:57.809> will<00:00:58.020> ignore<00:00:58.140> it 00:00:58.280 --> 00:00:58.290 align:start position:0% like that people people will ignore it 00:00:58.290 --> 00:01:02.900 align:start position:0% like that people people will ignore it if<00:00:59.629> they<00:01:00.629> download<00:01:01.050> the<00:01:01.079> block<00:01:01.399> full<00:01:02.399> load<00:01:02.579> and 00:01:02.900 --> 00:01:02.910 align:start position:0% if they download the block full load and 00:01:02.910 --> 00:01:06.319 align:start position:0% if they download the block full load and it<00:01:04.009> verifies<00:01:05.009> it<00:01:05.280> tries<00:01:05.640> to<00:01:05.789> run<00:01:05.939> it<00:01:06.090> it 00:01:06.319 --> 00:01:06.329 align:start position:0% it verifies it tries to run it it 00:01:06.329 --> 00:01:08.240 align:start position:0% it verifies it tries to run it it doesn't<00:01:06.689> succeed<00:01:06.899> it<00:01:07.590> would<00:01:07.799> ignore<00:01:08.009> that 00:01:08.240 --> 00:01:08.250 align:start position:0% doesn't succeed it would ignore that 00:01:08.250 --> 00:01:13.250 align:start position:0% doesn't succeed it would ignore that block<00:01:08.460> and<00:01:11.270> of<00:01:12.270> course<00:01:12.479> four<00:01:12.659> modes<00:01:12.840> include 00:01:13.250 --> 00:01:13.260 align:start position:0% block and of course four modes include 00:01:13.260 --> 00:01:17.180 align:start position:0% block and of course four modes include the<00:01:13.409> miners<00:01:13.799> and<00:01:15.049> if<00:01:16.049> you<00:01:16.170> have<00:01:16.260> made<00:01:16.440> 51%<00:01:17.040> it 00:01:17.180 --> 00:01:17.190 align:start position:0% the miners and if you have made 51% it 00:01:17.190 --> 00:01:20.929 align:start position:0% the miners and if you have made 51% it if<00:01:17.340> if<00:01:18.000> 51%<00:01:18.720> of<00:01:18.810> our<00:01:18.900> miners<00:01:19.290> are<00:01:19.380> honest<00:01:19.939> then 00:01:20.929 --> 00:01:20.939 align:start position:0% if if 51% of our miners are honest then 00:01:20.939 --> 00:01:23.690 align:start position:0% if if 51% of our miners are honest then they<00:01:21.630> won't<00:01:21.810> build<00:01:22.049> on<00:01:23.040> a<00:01:23.100> block<00:01:23.340> that<00:01:23.369> doesn't 00:01:23.690 --> 00:01:23.700 align:start position:0% they won't build on a block that doesn't 00:01:23.700 --> 00:01:27.770 align:start position:0% they won't build on a block that doesn't exist<00:01:23.909> was<00:01:24.299> implied<00:01:24.710> and<00:01:26.240> so<00:01:27.240> it'll<00:01:27.479> never<00:01:27.659> be 00:01:27.770 --> 00:01:27.780 align:start position:0% exist was implied and so it'll never be 00:01:27.780 --> 00:01:31.340 align:start position:0% exist was implied and so it'll never be in<00:01:27.960> the<00:01:28.080> longest<00:01:28.320> chain<00:01:28.500> eventually<00:01:29.780> but<00:01:30.780> if 00:01:31.340 --> 00:01:31.350 align:start position:0% in the longest chain eventually but if 00:01:31.350 --> 00:01:36.859 align:start position:0% in the longest chain eventually but if you're<00:01:31.830> in<00:01:31.920> a<00:01:31.950> shard<00:01:32.280> system<00:01:33.920> like<00:01:34.920> s<00:01:35.070> 2.0<00:01:35.869> like 00:01:36.859 --> 00:01:36.869 align:start position:0% you're in a shard system like s 2.0 like 00:01:36.869 --> 00:01:40.820 align:start position:0% you're in a shard system like s 2.0 like polka<00:01:37.110> dot<00:01:37.580> then<00:01:39.110> only<00:01:40.110> a<00:01:40.259> small<00:01:40.530> number<00:01:40.560> of 00:01:40.820 --> 00:01:40.830 align:start position:0% polka dot then only a small number of 00:01:40.830 --> 00:01:43.429 align:start position:0% polka dot then only a small number of people<00:01:40.950> check<00:01:41.640> the<00:01:41.820> block<00:01:42.020> that<00:01:43.020> the<00:01:43.229> set<00:01:43.409> of 00:01:43.429 --> 00:01:43.439 align:start position:0% people check the block that the set of 00:01:43.439 --> 00:01:45.770 align:start position:0% people check the block that the set of violators<00:01:44.009> we<00:01:44.220> which<00:01:45.119> form<00:01:45.360> the<00:01:45.420> content 00:01:45.770 --> 00:01:45.780 align:start position:0% violators we which form the content 00:01:45.780 --> 00:01:48.499 align:start position:0% violators we which form the content consensus<00:01:46.530> for<00:01:46.650> the<00:01:46.710> entire<00:01:46.950> system<00:01:47.509> they 00:01:48.499 --> 00:01:48.509 align:start position:0% consensus for the entire system they 00:01:48.509 --> 00:01:53.510 align:start position:0% consensus for the entire system they don't<00:01:48.900> know<00:01:50.540> if<00:01:51.540> the<00:01:52.259> book<00:01:52.409> exists<00:01:52.979> if<00:01:53.189> anyone 00:01:53.510 --> 00:01:53.520 align:start position:0% don't know if the book exists if anyone 00:01:53.520 --> 00:01:57.649 align:start position:0% don't know if the book exists if anyone has<00:01:53.700> it<00:01:53.850> the<00:01:54.000> data<00:01:54.180> or<00:01:54.930> if<00:01:56.119> it's<00:01:57.119> valid<00:01:57.360> if<00:01:57.570> it 00:01:57.649 --> 00:01:57.659 align:start position:0% has it the data or if it's valid if it 00:01:57.659 --> 00:02:01.010 align:start position:0% has it the data or if it's valid if it makes<00:01:57.840> sense<00:01:59.299> it's<00:02:00.299> not<00:02:00.329> going<00:02:00.570> to<00:02:00.630> sort<00:02:00.960> of 00:02:01.010 --> 00:02:01.020 align:start position:0% makes sense it's not going to sort of 00:02:01.020 --> 00:02:06.469 align:start position:0% makes sense it's not going to sort of explain<00:02:01.890> a<00:02:01.950> bit<00:02:02.159> how<00:02:03.290> polkadot<00:02:04.290> works<00:02:05.299> so<00:02:06.299> the 00:02:06.469 --> 00:02:06.479 align:start position:0% explain a bit how polkadot works so the 00:02:06.479 --> 00:02:07.310 align:start position:0% explain a bit how polkadot works so the rest<00:02:06.630> of<00:02:06.689> this<00:02:06.750> makes<00:02:06.990> sense 00:02:07.310 --> 00:02:07.320 align:start position:0% rest of this makes sense 00:02:07.320 --> 00:02:11.029 align:start position:0% rest of this makes sense so<00:02:08.250> polka<00:02:08.519> dots<00:02:08.729> a<00:02:08.819> multi-chain<00:02:09.209> system<00:02:10.039> we 00:02:11.029 --> 00:02:11.039 align:start position:0% so polka dots a multi-chain system we 00:02:11.039 --> 00:02:16.850 align:start position:0% so polka dots a multi-chain system we have<00:02:11.269> a<00:02:12.269> relay<00:02:13.019> chain<00:02:13.579> the<00:02:14.579> pair<00:02:14.760> of<00:02:14.819> chains 00:02:16.850 --> 00:02:16.860 align:start position:0% have a relay chain the pair of chains 00:02:16.860 --> 00:02:19.710 align:start position:0% have a relay chain the pair of chains and<00:02:17.860> these<00:02:18.069> are<00:02:18.250> secured<00:02:18.580> via<00:02:18.879> a<00:02:19.180> set<00:02:19.599> of 00:02:19.710 --> 00:02:19.720 align:start position:0% and these are secured via a set of 00:02:19.720 --> 00:02:25.410 align:start position:0% and these are secured via a set of validators<00:02:20.910> and<00:02:22.980> the<00:02:23.980> way<00:02:24.160> hurricane<00:02:25.090> blocks 00:02:25.410 --> 00:02:25.420 align:start position:0% validators and the way hurricane blocks 00:02:25.420 --> 00:02:32.479 align:start position:0% validators and the way hurricane blocks work<00:02:25.989> is<00:02:27.000> some<00:02:29.610> Claytor<00:02:30.870> produces<00:02:31.870> it<00:02:31.989> and 00:02:32.479 --> 00:02:32.489 align:start position:0% work is some Claytor produces it and 00:02:32.489 --> 00:02:35.009 align:start position:0% work is some Claytor produces it and there's<00:02:33.489> some<00:02:33.610> random<00:02:34.030> subset<00:02:34.390> to<00:02:34.480> validators 00:02:35.009 --> 00:02:35.019 align:start position:0% there's some random subset to validators 00:02:35.019 --> 00:02:37.050 align:start position:0% there's some random subset to validators to<00:02:35.140> all<00:02:35.379> the<00:02:35.530> set<00:02:35.680> of<00:02:35.769> bio-datas<00:02:36.280> and<00:02:36.760> we<00:02:36.849> sort 00:02:37.050 --> 00:02:37.060 align:start position:0% to all the set of bio-datas and we sort 00:02:37.060 --> 00:02:39.150 align:start position:0% to all the set of bio-datas and we sort of<00:02:37.120> divide<00:02:37.360> them<00:02:37.540> between<00:02:37.629> para<00:02:37.989> chains<00:02:38.260> and 00:02:39.150 --> 00:02:39.160 align:start position:0% of divide them between para chains and 00:02:39.160 --> 00:02:43.500 align:start position:0% of divide them between para chains and this<00:02:39.819> random<00:02:40.209> subset<00:02:41.670> checks<00:02:42.670> the<00:02:42.819> block<00:02:43.060> say 00:02:43.500 --> 00:02:43.510 align:start position:0% this random subset checks the block say 00:02:43.510 --> 00:02:45.900 align:start position:0% this random subset checks the block say it<00:02:43.870> says<00:02:44.230> it's<00:02:44.410> fired<00:02:44.590> and<00:02:44.799> available<00:02:45.190> they 00:02:45.900 --> 00:02:45.910 align:start position:0% it says it's fired and available they 00:02:45.910 --> 00:02:47.850 align:start position:0% it says it's fired and available they sign<00:02:46.150> this<00:02:46.299> header<00:02:46.540> the<00:02:47.110> header<00:02:47.140> goes<00:02:47.530> on<00:02:47.709> to 00:02:47.850 --> 00:02:47.860 align:start position:0% sign this header the header goes on to 00:02:47.860 --> 00:02:51.660 align:start position:0% sign this header the header goes on to the<00:02:47.980> relay<00:02:48.910> chain<00:02:49.150> and<00:02:49.980> then<00:02:50.980> it's<00:02:51.459> in<00:02:51.579> the 00:02:51.660 --> 00:02:51.670 align:start position:0% the relay chain and then it's in the 00:02:51.670 --> 00:02:53.400 align:start position:0% the relay chain and then it's in the relay<00:02:51.910> chain<00:02:52.120> we<00:02:52.360> count<00:02:52.569> it<00:02:52.720> is<00:02:52.780> happening<00:02:53.170> in 00:02:53.400 --> 00:02:53.410 align:start position:0% relay chain we count it is happening in 00:02:53.410 --> 00:02:54.509 align:start position:0% relay chain we count it is happening in particular<00:02:53.860> when<00:02:53.980> the<00:02:54.040> relay<00:02:54.250> chain<00:02:54.430> is 00:02:54.509 --> 00:02:54.519 align:start position:0% particular when the relay chain is 00:02:54.519 --> 00:02:56.670 align:start position:0% particular when the relay chain is finalized<00:02:54.940> which<00:02:55.209> we<00:02:55.360> do<00:02:55.510> by<00:02:55.690> you<00:02:56.319> finalized 00:02:56.670 --> 00:02:56.680 align:start position:0% finalized which we do by you finalized 00:02:56.680 --> 00:02:58.380 align:start position:0% finalized which we do by you finalized by<00:02:56.860> a<00:02:56.890> finality<00:02:57.310> gadget<00:02:57.790> get<00:02:58.030> Byzantine 00:02:58.380 --> 00:02:58.390 align:start position:0% by a finality gadget get Byzantine 00:02:58.390 --> 00:03:02.190 align:start position:0% by a finality gadget get Byzantine agreement<00:02:59.130> then<00:03:00.130> it's<00:03:00.310> final<00:03:00.610> so<00:03:01.540> you<00:03:01.870> compare 00:03:02.190 --> 00:03:02.200 align:start position:0% agreement then it's final so you compare 00:03:02.200 --> 00:03:06.059 align:start position:0% agreement then it's final so you compare this<00:03:02.319> with<00:03:02.500> at<00:03:03.010> 2.0<00:03:03.730> so<00:03:04.390> what<00:03:05.290> now<00:03:05.440> happens<00:03:05.650> is 00:03:06.059 --> 00:03:06.069 align:start position:0% this with at 2.0 so what now happens is 00:03:06.069 --> 00:03:09.660 align:start position:0% this with at 2.0 so what now happens is that<00:03:07.140> so<00:03:08.140> shell<00:03:08.349> blocks<00:03:08.560> it<00:03:08.680> produced<00:03:08.980> and 00:03:09.660 --> 00:03:09.670 align:start position:0% that so shell blocks it produced and 00:03:09.670 --> 00:03:10.740 align:start position:0% that so shell blocks it produced and then<00:03:09.790> we<00:03:09.879> have<00:03:10.000> a<00:03:10.030> random<00:03:10.360> subset<00:03:10.720> of 00:03:10.740 --> 00:03:10.750 align:start position:0% then we have a random subset of 00:03:10.750 --> 00:03:13.920 align:start position:0% then we have a random subset of violators<00:03:11.319> which<00:03:11.829> we<00:03:11.980> divide<00:03:12.220> between<00:03:12.930> all 00:03:13.920 --> 00:03:13.930 align:start position:0% violators which we divide between all 00:03:13.930 --> 00:03:16.890 align:start position:0% violators which we divide between all the<00:03:14.290> all<00:03:14.470> the<00:03:14.560> shards<00:03:15.120> they<00:03:16.120> call<00:03:16.540> the<00:03:16.629> cross 00:03:16.890 --> 00:03:16.900 align:start position:0% the all the shards they call the cross 00:03:16.900 --> 00:03:19.440 align:start position:0% the all the shards they call the cross link<00:03:17.140> committee<00:03:17.400> and<00:03:18.400> they<00:03:18.700> periodically 00:03:19.440 --> 00:03:19.450 align:start position:0% link committee and they periodically 00:03:19.450 --> 00:03:22.379 align:start position:0% link committee and they periodically they<00:03:19.840> all<00:03:19.989> sign<00:03:20.200> a<00:03:20.230> cross<00:03:20.530> link<00:03:21.359> which<00:03:22.359> says 00:03:22.379 --> 00:03:22.389 align:start position:0% they all sign a cross link which says 00:03:22.389 --> 00:03:23.699 align:start position:0% they all sign a cross link which says that<00:03:22.690> these<00:03:22.780> blocks<00:03:23.019> happen<00:03:23.440> that<00:03:23.590> they're 00:03:23.699 --> 00:03:23.709 align:start position:0% that these blocks happen that they're 00:03:23.709 --> 00:03:26.699 align:start position:0% that these blocks happen that they're Biden<00:03:24.010> available<00:03:24.459> and<00:03:25.139> then<00:03:26.139> that<00:03:26.319> goes<00:03:26.470> onto 00:03:26.699 --> 00:03:26.709 align:start position:0% Biden available and then that goes onto 00:03:26.709 --> 00:03:29.940 align:start position:0% Biden available and then that goes onto the<00:03:27.010> beacon<00:03:27.459> chain<00:03:28.290> if<00:03:29.290> two-thirds<00:03:29.680> of<00:03:29.859> those 00:03:29.940 --> 00:03:29.950 align:start position:0% the beacon chain if two-thirds of those 00:03:29.950 --> 00:03:35.520 align:start position:0% the beacon chain if two-thirds of those sign<00:03:30.220> it<00:03:30.400> and<00:03:31.470> then<00:03:32.549> the<00:03:33.549> block<00:03:34.049> it<00:03:35.049> happens 00:03:35.520 --> 00:03:35.530 align:start position:0% sign it and then the block it happens 00:03:35.530 --> 00:03:36.750 align:start position:0% sign it and then the block it happens because<00:03:35.739> it's<00:03:35.980> in<00:03:36.040> the<00:03:36.099> beacon<00:03:36.340> chain<00:03:36.549> its 00:03:36.750 --> 00:03:36.760 align:start position:0% because it's in the beacon chain its 00:03:36.760 --> 00:03:39.420 align:start position:0% because it's in the beacon chain its final<00:03:37.180> when<00:03:37.540> the<00:03:38.200> finality<00:03:38.530> gadget<00:03:38.980> Kaspar 00:03:39.420 --> 00:03:39.430 align:start position:0% final when the finality gadget Kaspar 00:03:39.430 --> 00:03:42.300 align:start position:0% final when the finality gadget Kaspar FFG<00:03:40.139> finalize<00:03:41.139> it<00:03:41.380> so<00:03:41.560> this<00:03:41.709> is<00:03:41.799> basically<00:03:42.130> the 00:03:42.300 --> 00:03:42.310 align:start position:0% FFG finalize it so this is basically the 00:03:42.310 --> 00:03:46.080 align:start position:0% FFG finalize it so this is basically the same<00:03:42.489> you<00:03:42.670> just<00:03:42.849> change<00:03:43.120> a<00:03:43.209> few<00:03:43.239> words<00:03:44.910> as<00:03:45.910> far 00:03:46.080 --> 00:03:46.090 align:start position:0% same you just change a few words as far 00:03:46.090 --> 00:03:48.259 align:start position:0% same you just change a few words as far as<00:03:46.239> this<00:03:46.389> talk<00:03:46.569> is<00:03:46.690> concerned<00:03:47.049> there's<00:03:47.829> a<00:03:47.889> few 00:03:48.259 --> 00:03:48.269 align:start position:0% as this talk is concerned there's a few 00:03:48.269 --> 00:03:55.860 align:start position:0% as this talk is concerned there's a few important<00:03:49.269> differences<00:03:52.349> things<00:03:53.349> like<00:03:54.870> the 00:03:55.860 --> 00:03:55.870 align:start position:0% important differences things like the 00:03:55.870 --> 00:03:57.900 align:start position:0% important differences things like the cross<00:03:56.079> links<00:03:56.349> aren't<00:03:56.500> every<00:03:56.739> blocked<00:03:57.040> the 00:03:57.900 --> 00:03:57.910 align:start position:0% cross links aren't every blocked the 00:03:57.910 --> 00:04:00.930 align:start position:0% cross links aren't every blocked the chains<00:03:58.150> are<00:03:59.220> different<00:04:00.220> it<00:04:00.310> more<00:04:00.489> para<00:04:00.760> chains 00:04:00.930 --> 00:04:00.940 align:start position:0% chains are different it more para chains 00:04:00.940 --> 00:04:03.509 align:start position:0% chains are different it more para chains are<00:04:01.030> different<00:04:01.299> in<00:04:01.389> polka<00:04:01.540> dots<00:04:01.859> but<00:04:02.859> the<00:04:03.069> only 00:04:03.509 --> 00:04:03.519 align:start position:0% are different in polka dots but the only 00:04:03.519 --> 00:04:05.909 align:start position:0% are different in polka dots but the only thing<00:04:03.700> that's<00:04:03.849> important<00:04:04.239> here<00:04:04.720> is<00:04:05.019> how<00:04:05.859> many 00:04:05.909 --> 00:04:05.919 align:start position:0% thing that's important here is how many 00:04:05.919 --> 00:04:08.460 align:start position:0% thing that's important here is how many validators<00:04:07.019> this<00:04:08.019> is<00:04:08.139> the<00:04:08.230> big<00:04:08.349> difference 00:04:08.460 --> 00:04:08.470 align:start position:0% validators this is the big difference 00:04:08.470 --> 00:04:09.360 align:start position:0% validators this is the big difference for<00:04:08.739> this<00:04:08.829> talk 00:04:09.360 --> 00:04:09.370 align:start position:0% for this talk 00:04:09.370 --> 00:04:12.120 align:start position:0% for this talk so<00:04:09.849> in<00:04:10.090> aetherium<00:04:10.510> 2.0<00:04:11.139> you're<00:04:11.709> going<00:04:11.889> for<00:04:12.069> you 00:04:12.120 --> 00:04:12.130 align:start position:0% so in aetherium 2.0 you're going for you 00:04:12.130 --> 00:04:13.680 align:start position:0% so in aetherium 2.0 you're going for you know<00:04:12.160> one<00:04:12.459> hundred<00:04:12.549> to<00:04:12.970> a<00:04:13.000> thousand 00:04:13.680 --> 00:04:13.690 align:start position:0% know one hundred to a thousand 00:04:13.690 --> 00:04:18.870 align:start position:0% know one hundred to a thousand validators<00:04:14.470> and<00:04:15.190> a<00:04:15.250> shard<00:04:16.590> and<00:04:17.590> in<00:04:18.459> polka<00:04:18.639> dot 00:04:18.870 --> 00:04:18.880 align:start position:0% validators and a shard and in polka dot 00:04:18.880 --> 00:04:24.240 align:start position:0% validators and a shard and in polka dot where<00:04:19.180> we're<00:04:19.450> looking<00:04:19.599> at<00:04:19.810> like<00:04:19.959> ten<00:04:20.229> and<00:04:23.250> this 00:04:24.240 --> 00:04:24.250 align:start position:0% where we're looking at like ten and this 00:04:24.250 --> 00:04:28.160 align:start position:0% where we're looking at like ten and this is<00:04:24.400> a<00:04:24.430> sort<00:04:24.669> of<00:04:24.729> a<00:04:24.820> bigger<00:04:25.090> problem<00:04:25.510> for<00:04:25.539> her 00:04:28.160 --> 00:04:28.170 align:start position:0% 00:04:28.170 --> 00:04:30.860 align:start position:0% and<00:04:28.650> basically<00:04:28.830> this<00:04:29.160> is<00:04:29.220> this<00:04:29.850> will<00:04:30.030> be<00:04:30.090> fine 00:04:30.860 --> 00:04:30.870 align:start position:0% and basically this is this will be fine 00:04:30.870 --> 00:04:34.040 align:start position:0% and basically this is this will be fine as<00:04:31.290> long<00:04:31.560> as<00:04:31.740> we<00:04:31.890> can<00:04:32.100> guarantee<00:04:32.280> that<00:04:33.050> the 00:04:34.040 --> 00:04:34.050 align:start position:0% as long as we can guarantee that the 00:04:34.050 --> 00:04:38.030 align:start position:0% as long as we can guarantee that the blocks<00:04:34.380> are<00:04:34.560> valid<00:04:34.910> and<00:04:36.950> they're<00:04:37.950> available 00:04:38.030 --> 00:04:38.040 align:start position:0% blocks are valid and they're available 00:04:38.040 --> 00:04:42.260 align:start position:0% blocks are valid and they're available any<00:04:38.640> any<00:04:38.880> fool<00:04:39.240> can<00:04:39.540> download<00:04:41.090> if<00:04:42.090> that 00:04:42.260 --> 00:04:42.270 align:start position:0% any any fool can download if that 00:04:42.270 --> 00:04:47.660 align:start position:0% any any fool can download if that happened<00:04:42.630> it's<00:04:42.750> fine<00:04:43.820> so<00:04:46.130> so<00:04:47.130> how<00:04:47.340> do<00:04:47.580> we 00:04:47.660 --> 00:04:47.670 align:start position:0% happened it's fine so so how do we 00:04:47.670 --> 00:04:49.610 align:start position:0% happened it's fine so so how do we guarantee<00:04:47.820> this<00:04:48.210> well<00:04:48.480> so<00:04:49.290> this<00:04:49.380> is<00:04:49.530> the 00:04:49.610 --> 00:04:49.620 align:start position:0% guarantee this well so this is the 00:04:49.620 --> 00:04:54.020 align:start position:0% guarantee this well so this is the reason<00:04:49.800> why<00:04:50.160> we<00:04:50.850> wanted<00:04:51.150> a<00:04:52.700> thousand<00:04:53.700> hydatid 00:04:54.020 --> 00:04:54.030 align:start position:0% reason why we wanted a thousand hydatid 00:04:54.030 --> 00:04:58.520 align:start position:0% reason why we wanted a thousand hydatid per<00:04:54.300> shot<00:04:55.040> so<00:04:56.040> well<00:04:56.760> f1<00:04:57.060> 2.0<00:04:57.780> plan<00:04:58.080> insist<00:04:58.380> it's 00:04:58.520 --> 00:04:58.530 align:start position:0% per shot so well f1 2.0 plan insist it's 00:04:58.530 --> 00:05:01.040 align:start position:0% per shot so well f1 2.0 plan insist it's to<00:04:58.650> have<00:04:58.830> sort<00:04:59.010> of<00:04:59.100> 16,000<00:05:00.090> initially<00:05:00.450> to<00:05:00.750> a 00:05:01.040 --> 00:05:01.050 align:start position:0% to have sort of 16,000 initially to a 00:05:01.050 --> 00:05:03.409 align:start position:0% to have sort of 16,000 initially to a million<00:05:01.500> validators<00:05:02.100> or<00:05:02.820> the<00:05:03.000> week<00:05:03.150> sort<00:05:03.360> of 00:05:03.409 --> 00:05:03.419 align:start position:0% million validators or the week sort of 00:05:03.419 --> 00:05:06.830 align:start position:0% million validators or the week sort of have<00:05:03.600> every<00:05:04.080> 32<00:05:04.380> ethers<00:05:04.710> of<00:05:04.800> our<00:05:04.950> data<00:05:05.130> and 00:05:06.830 --> 00:05:06.840 align:start position:0% have every 32 ethers of our data and 00:05:06.840 --> 00:05:09.400 align:start position:0% have every 32 ethers of our data and [Music] 00:05:09.400 --> 00:05:09.410 align:start position:0% [Music] 00:05:09.410 --> 00:05:12.440 align:start position:0% [Music] it's<00:05:10.410> like<00:05:10.560> if<00:05:10.710> we<00:05:10.740> say<00:05:11.520> 3/4<00:05:12.090> of<00:05:12.120> those<00:05:12.300> are 00:05:12.440 --> 00:05:12.450 align:start position:0% it's like if we say 3/4 of those are 00:05:12.450 --> 00:05:16.130 align:start position:0% it's like if we say 3/4 of those are honest<00:05:12.720> and<00:05:12.990> we<00:05:13.410> select<00:05:13.740> say<00:05:14.460> 100<00:05:14.960> then<00:05:15.960> with 00:05:16.130 --> 00:05:16.140 align:start position:0% honest and we select say 100 then with 00:05:16.140 --> 00:05:20.860 align:start position:0% honest and we select say 100 then with overwhelmingly<00:05:16.680> high<00:05:16.860> probability<00:05:19.640> you<00:05:20.640> know 00:05:20.860 --> 00:05:20.870 align:start position:0% overwhelmingly high probability you know 00:05:20.870 --> 00:05:23.720 align:start position:0% overwhelmingly high probability you know one-third<00:05:21.870> of<00:05:21.900> those<00:05:22.169> will<00:05:22.410> be<00:05:22.530> honest<00:05:23.160> and<00:05:23.400> so 00:05:23.720 --> 00:05:23.730 align:start position:0% one-third of those will be honest and so 00:05:23.730 --> 00:05:25.159 align:start position:0% one-third of those will be honest and so if<00:05:23.820> two<00:05:23.970> thirds<00:05:24.150> of<00:05:24.270> people<00:05:24.570> sign<00:05:24.750> to<00:05:24.900> say<00:05:25.050> it's 00:05:25.159 --> 00:05:25.169 align:start position:0% if two thirds of people sign to say it's 00:05:25.169 --> 00:05:27.230 align:start position:0% if two thirds of people sign to say it's bad<00:05:25.290> and<00:05:25.500> available<00:05:25.919> so<00:05:26.580> I'm<00:05:26.669> on<00:05:26.790> this<00:05:26.910> person 00:05:27.230 --> 00:05:27.240 align:start position:0% bad and available so I'm on this person 00:05:27.240 --> 00:05:29.600 align:start position:0% bad and available so I'm on this person will<00:05:27.690> keep<00:05:27.810> it<00:05:27.930> bad<00:05:28.080> and<00:05:28.110> available<00:05:28.620> probably 00:05:29.600 --> 00:05:29.610 align:start position:0% will keep it bad and available probably 00:05:29.610 --> 00:05:34.760 align:start position:0% will keep it bad and available probably a<00:05:29.640> whole<00:05:30.270> load<00:05:30.479> of<00:05:30.510> them<00:05:30.780> and<00:05:33.590> then<00:05:34.590> it<00:05:34.680> will 00:05:34.760 --> 00:05:34.770 align:start position:0% a whole load of them and then it will 00:05:34.770 --> 00:05:41.050 align:start position:0% a whole load of them and then it will carry<00:05:34.919> on<00:05:35.070> being<00:05:35.220> available<00:05:35.640> and<00:05:35.820> valid<00:05:37.490> but 00:05:41.050 --> 00:05:41.060 align:start position:0% 00:05:41.060 --> 00:05:43.370 align:start position:0% it's<00:05:42.060> still<00:05:42.270> sort<00:05:42.570> of<00:05:42.630> a<00:05:42.690> small<00:05:42.930> fraction<00:05:43.290> of 00:05:43.370 --> 00:05:43.380 align:start position:0% it's still sort of a small fraction of 00:05:43.380 --> 00:05:45.230 align:start position:0% it's still sort of a small fraction of the<00:05:43.470> entire<00:05:43.560> system<00:05:44.040> that<00:05:44.070> that's<00:05:44.729> backing 00:05:45.230 --> 00:05:45.240 align:start position:0% the entire system that that's backing 00:05:45.240 --> 00:05:51.890 align:start position:0% the entire system that that's backing that<00:05:45.660> is<00:05:45.720> giving<00:05:46.200> us<00:05:46.290> this<00:05:46.440> guarantee<00:05:48.770> and<00:05:50.900> so 00:05:51.890 --> 00:05:51.900 align:start position:0% that is giving us this guarantee and so 00:05:51.900 --> 00:05:53.870 align:start position:0% that is giving us this guarantee and so the<00:05:52.050> question<00:05:52.320> is<00:05:52.440> will<00:05:52.890> we<00:05:53.340> be<00:05:53.370> able<00:05:53.550> to<00:05:53.669> get<00:05:53.790> a 00:05:53.870 --> 00:05:53.880 align:start position:0% the question is will we be able to get a 00:05:53.880 --> 00:05:57.040 align:start position:0% the question is will we be able to get a million<00:05:54.030> validators<00:05:54.630> I<00:05:55.190> don't<00:05:56.190> know 00:05:57.040 --> 00:05:57.050 align:start position:0% million validators I don't know 00:05:57.050 --> 00:06:06.170 align:start position:0% million validators I don't know so<00:06:01.010> if<00:06:02.010> I<00:06:02.190> have<00:06:02.370> well<00:06:03.180> maybe<00:06:03.390> but<00:06:03.870> only<00:06:04.050> if<00:06:05.180> some 00:06:06.170 --> 00:06:06.180 align:start position:0% so if I have well maybe but only if some 00:06:06.180 --> 00:06:09.050 align:start position:0% so if I have well maybe but only if some people<00:06:06.300> run<00:06:06.600> a<00:06:06.630> lot<00:06:06.810> of<00:06:06.930> other<00:06:07.080> data<00:06:07.229> stripe<00:06:08.060> so 00:06:09.050 --> 00:06:09.060 align:start position:0% people run a lot of other data stripe so 00:06:09.060 --> 00:06:10.640 align:start position:0% people run a lot of other data stripe so if<00:06:09.150> I<00:06:09.270> have<00:06:09.360> a<00:06:09.419> thousand<00:06:09.780> death<00:06:09.930> then<00:06:10.380> I<00:06:10.470> should 00:06:10.640 --> 00:06:10.650 align:start position:0% if I have a thousand death then I should 00:06:10.650 --> 00:06:14.630 align:start position:0% if I have a thousand death then I should be<00:06:10.740> running<00:06:10.830> 30<00:06:11.160> validators<00:06:13.400> but<00:06:14.400> what<00:06:14.550> we 00:06:14.630 --> 00:06:14.640 align:start position:0% be running 30 validators but what we 00:06:14.640 --> 00:06:15.980 align:start position:0% be running 30 validators but what we really<00:06:14.970> you<00:06:15.210> know<00:06:15.300> what<00:06:15.479> sort<00:06:15.630> of<00:06:15.690> a<00:06:15.750> design 00:06:15.980 --> 00:06:15.990 align:start position:0% really you know what sort of a design 00:06:15.990 --> 00:06:17.810 align:start position:0% really you know what sort of a design goal<00:06:16.050> was<00:06:16.410> to<00:06:16.620> make<00:06:16.770> these<00:06:16.950> runnable<00:06:17.640> by 00:06:17.810 --> 00:06:17.820 align:start position:0% goal was to make these runnable by 00:06:17.820 --> 00:06:21.219 align:start position:0% goal was to make these runnable by someone<00:06:18.380> on<00:06:19.380> a<00:06:19.440> laptop<00:06:19.860> in<00:06:19.979> their<00:06:20.100> bedroom<00:06:20.430> or 00:06:21.219 --> 00:06:21.229 align:start position:0% someone on a laptop in their bedroom or 00:06:21.229 --> 00:06:25.219 align:start position:0% someone on a laptop in their bedroom or but<00:06:22.229> that<00:06:23.040> doesn't<00:06:23.370> really<00:06:23.720> work<00:06:24.720> so<00:06:24.960> well<00:06:25.140> if 00:06:25.219 --> 00:06:25.229 align:start position:0% but that doesn't really work so well if 00:06:25.229 --> 00:06:28.010 align:start position:0% but that doesn't really work so well if I<00:06:25.320> have<00:06:25.470> a<00:06:25.500> thousand<00:06:25.890> death<00:06:26.010> you<00:06:26.130> see<00:06:26.900> and<00:06:27.900> I'm 00:06:28.010 --> 00:06:28.020 align:start position:0% I have a thousand death you see and I'm 00:06:28.020 --> 00:06:29.360 align:start position:0% I have a thousand death you see and I'm not<00:06:28.169> sure<00:06:28.320> how<00:06:28.500> all<00:06:28.620> this<00:06:28.740> is<00:06:28.800> going<00:06:29.040> to<00:06:29.160> scale 00:06:29.360 --> 00:06:29.370 align:start position:0% not sure how all this is going to scale 00:06:29.370 --> 00:06:31.820 align:start position:0% not sure how all this is going to scale but<00:06:30.180> there's<00:06:30.630> like<00:06:30.870> sort<00:06:31.110> of<00:06:31.169> there's<00:06:31.470> Network 00:06:31.820 --> 00:06:31.830 align:start position:0% but there's like sort of there's Network 00:06:31.830 --> 00:06:34.010 align:start position:0% but there's like sort of there's Network and<00:06:32.040> computing<00:06:32.400> limitations<00:06:32.940> and<00:06:33.419> the 00:06:34.010 --> 00:06:34.020 align:start position:0% and computing limitations and the 00:06:34.020 --> 00:06:37.250 align:start position:0% and computing limitations and the networking<00:06:34.320> is<00:06:34.560> probably<00:06:35.130> a<00:06:35.220> problem<00:06:35.669> so<00:06:36.479> like 00:06:37.250 --> 00:06:37.260 align:start position:0% networking is probably a problem so like 00:06:37.260 --> 00:06:38.770 align:start position:0% networking is probably a problem so like how<00:06:37.470> many<00:06:37.650> validators<00:06:38.099> got<00:06:38.250> about<00:06:38.370> a<00:06:38.430> one 00:06:38.770 --> 00:06:38.780 align:start position:0% how many validators got about a one 00:06:38.780 --> 00:06:40.000 align:start position:0% how many validators got about a one well<00:06:39.140> kind<00:06:39.440> of<00:06:39.470> depends<00:06:39.740> on<00:06:39.800> how<00:06:39.860> many 00:06:40.000 --> 00:06:40.010 align:start position:0% well kind of depends on how many 00:06:40.010 --> 00:06:41.500 align:start position:0% well kind of depends on how many peer-to-peer<00:06:40.310> networks<00:06:40.880> I<00:06:41.000> can<00:06:41.120> connect<00:06:41.360> it 00:06:41.500 --> 00:06:41.510 align:start position:0% peer-to-peer networks I can connect it 00:06:41.510 --> 00:06:45.970 align:start position:0% peer-to-peer networks I can connect it can<00:06:41.960> i<00:06:42.020> connect<00:06:42.290> you<00:06:42.380> 30<00:06:42.560> networks<00:06:44.800> instead<00:06:45.800> of 00:06:45.970 --> 00:06:45.980 align:start position:0% can i connect you 30 networks instead of 00:06:45.980 --> 00:06:47.860 align:start position:0% can i connect you 30 networks instead of to<00:06:46.400> be<00:06:46.520> reversed<00:06:46.820> by<00:06:46.970> getting<00:06:47.270> 30<00:06:47.450> connections 00:06:47.860 --> 00:06:47.870 align:start position:0% to be reversed by getting 30 connections 00:06:47.870 --> 00:06:50.830 align:start position:0% to be reversed by getting 30 connections each<00:06:48.040> thousand<00:06:49.040> connections<00:06:49.220> I<00:06:49.790> can<00:06:50.630> do<00:06:50.720> that 00:06:50.830 --> 00:06:50.840 align:start position:0% each thousand connections I can do that 00:06:50.840 --> 00:06:52.810 align:start position:0% each thousand connections I can do that with<00:06:50.960> a<00:06:50.990> server<00:06:51.230> in<00:06:51.380> a<00:06:51.440> datacenter<00:06:51.830> probably 00:06:52.810 --> 00:06:52.820 align:start position:0% with a server in a datacenter probably 00:06:52.820 --> 00:06:54.820 align:start position:0% with a server in a datacenter probably if<00:06:52.970> the<00:06:53.060> code<00:06:53.240> is<00:06:53.360> good<00:06:53.510> but<00:06:54.290> probably<00:06:54.620> not<00:06:54.770> in 00:06:54.820 --> 00:06:54.830 align:start position:0% if the code is good but probably not in 00:06:54.830 --> 00:06:58.230 align:start position:0% if the code is good but probably not in my<00:06:55.010> bedroom<00:06:55.190> they<00:06:55.400> would<00:06:55.550> crash<00:06:55.700> my<00:06:55.730> reader 00:06:58.230 --> 00:06:58.240 align:start position:0% 00:06:58.240 --> 00:07:04.690 align:start position:0% and<00:07:02.650> this<00:07:03.650> is<00:07:03.800> why<00:07:03.920> we<00:07:04.070> kind<00:07:04.280> of<00:07:04.370> worried<00:07:04.580> in 00:07:04.690 --> 00:07:04.700 align:start position:0% and this is why we kind of worried in 00:07:04.700 --> 00:07:05.920 align:start position:0% and this is why we kind of worried in polkadot<00:07:04.970> that<00:07:05.210> we<00:07:05.270> won't<00:07:05.450> get<00:07:05.570> this<00:07:05.720> many 00:07:05.920 --> 00:07:05.930 align:start position:0% polkadot that we won't get this many 00:07:05.930 --> 00:07:07.120 align:start position:0% polkadot that we won't get this many validators<00:07:06.440> that<00:07:06.590> we're<00:07:06.680> trying<00:07:06.800> to<00:07:06.890> design 00:07:07.120 --> 00:07:07.130 align:start position:0% validators that we're trying to design 00:07:07.130 --> 00:07:09.040 align:start position:0% validators that we're trying to design the<00:07:07.250> system<00:07:07.520> with<00:07:07.640> less<00:07:07.760> but<00:07:08.720> I'd<00:07:08.840> like<00:07:08.990> to 00:07:09.040 --> 00:07:09.050 align:start position:0% the system with less but I'd like to 00:07:09.050 --> 00:07:11.050 align:start position:0% the system with less but I'd like to sort<00:07:09.350> of<00:07:09.440> point<00:07:09.680> out<00:07:09.800> that<00:07:10.100> because<00:07:10.310> SD<00:07:10.850> Point 00:07:11.050 --> 00:07:11.060 align:start position:0% sort of point out that because SD Point 00:07:11.060 --> 00:07:14.550 align:start position:0% sort of point out that because SD Point area<00:07:11.270> has<00:07:11.570> a<00:07:11.900> very<00:07:12.620> similar<00:07:12.890> architecture 00:07:14.550 --> 00:07:14.560 align:start position:0% area has a very similar architecture 00:07:14.560 --> 00:07:17.080 align:start position:0% area has a very similar architecture almost<00:07:15.560> all<00:07:15.650> parts<00:07:15.830> of<00:07:16.010> our<00:07:16.100> solution<00:07:16.940> would 00:07:17.080 --> 00:07:17.090 align:start position:0% almost all parts of our solution would 00:07:17.090 --> 00:07:20.640 align:start position:0% almost all parts of our solution would just<00:07:17.210> apply<00:07:17.390> so<00:07:18.080> you<00:07:18.140> could<00:07:18.440> use<00:07:18.590> any<00:07:18.740> of<00:07:18.830> them 00:07:20.640 --> 00:07:20.650 align:start position:0% just apply so you could use any of them 00:07:20.650 --> 00:07:24.220 align:start position:0% just apply so you could use any of them so<00:07:21.880> what<00:07:22.880> does<00:07:23.000> polkadot<00:07:23.419> do<00:07:23.570> so<00:07:23.750> they<00:07:24.080> said 00:07:24.220 --> 00:07:24.230 align:start position:0% so what does polkadot do so they said 00:07:24.230 --> 00:07:25.420 align:start position:0% so what does polkadot do so they said before<00:07:24.500> we<00:07:24.590> only<00:07:24.710> have<00:07:24.890> ten<00:07:25.040> by<00:07:25.190> a<00:07:25.220> day<00:07:25.370> to 00:07:25.420 --> 00:07:25.430 align:start position:0% before we only have ten by a day to 00:07:25.430 --> 00:07:26.220 align:start position:0% before we only have ten by a day to prepare<00:07:25.610> Jane 00:07:26.220 --> 00:07:26.230 align:start position:0% prepare Jane 00:07:26.230 --> 00:07:30.310 align:start position:0% prepare Jane it<00:07:27.230> means<00:07:27.470> we<00:07:27.620> only<00:07:27.770> need<00:07:27.890> sort<00:07:28.370> of<00:07:29.169> five<00:07:30.169> to 00:07:30.310 --> 00:07:30.320 align:start position:0% it means we only need sort of five to 00:07:30.320 --> 00:07:33.159 align:start position:0% it means we only need sort of five to seven<00:07:31.150> signatures<00:07:32.150> on<00:07:32.450> this<00:07:32.720> on<00:07:32.810> this<00:07:32.900> block 00:07:33.159 --> 00:07:33.169 align:start position:0% seven signatures on this on this block 00:07:33.169 --> 00:07:36.970 align:start position:0% seven signatures on this on this block and<00:07:34.540> the<00:07:35.540> basic<00:07:35.840> idea<00:07:36.110> for<00:07:36.140> validity<00:07:36.680> was<00:07:36.890> to 00:07:36.970 --> 00:07:36.980 align:start position:0% and the basic idea for validity was to 00:07:36.980 --> 00:07:40.240 align:start position:0% and the basic idea for validity was to rely<00:07:37.130> on<00:07:37.160> fisherman<00:07:38.230> so<00:07:39.230> every<00:07:39.800> collator 00:07:40.240 --> 00:07:40.250 align:start position:0% rely on fisherman so every collator 00:07:40.250 --> 00:07:41.530 align:start position:0% rely on fisherman so every collator will<00:07:40.550> be<00:07:40.640> a<00:07:40.669> fisherman<00:07:40.880> there<00:07:41.300> will<00:07:41.390> be<00:07:41.419> no 00:07:41.530 --> 00:07:41.540 align:start position:0% will be a fisherman there will be no 00:07:41.540 --> 00:07:42.909 align:start position:0% will be a fisherman there will be no shortage<00:07:41.690> of<00:07:41.900> fishing<00:07:42.169> whenever<00:07:42.380> you<00:07:42.470> fool<00:07:42.770> no 00:07:42.909 --> 00:07:42.919 align:start position:0% shortage of fishing whenever you fool no 00:07:42.919 --> 00:07:44.230 align:start position:0% shortage of fishing whenever you fool no can<00:07:43.100> just<00:07:43.250> production<00:07:43.610> stage<00:07:43.850> they<00:07:44.060> don't 00:07:44.230 --> 00:07:44.240 align:start position:0% can just production stage they don't 00:07:44.240 --> 00:07:46.000 align:start position:0% can just production stage they don't have<00:07:44.360> to<00:07:44.479> lock<00:07:44.600> anything<00:07:44.960> beforehand<00:07:45.380> they 00:07:46.000 --> 00:07:46.010 align:start position:0% have to lock anything beforehand they 00:07:46.010 --> 00:07:47.530 align:start position:0% have to lock anything beforehand they can<00:07:46.160> just<00:07:46.310> run<00:07:46.460> it<00:07:46.490> and<00:07:46.790> then<00:07:47.030> when<00:07:47.419> they 00:07:47.530 --> 00:07:47.540 align:start position:0% can just run it and then when they 00:07:47.540 --> 00:07:51.130 align:start position:0% can just run it and then when they discover<00:07:47.900> a<00:07:47.960> bucket<00:07:48.760> invalid<00:07:50.020> that<00:07:51.020> they're 00:07:51.130 --> 00:07:51.140 align:start position:0% discover a bucket invalid that they're 00:07:51.140 --> 00:07:55.600 align:start position:0% discover a bucket invalid that they're running<00:07:51.320> they'll<00:07:51.590> report<00:07:51.830> it<00:07:52.040> and<00:07:54.610> then 00:07:55.600 --> 00:07:55.610 align:start position:0% running they'll report it and then 00:07:55.610 --> 00:07:58.600 align:start position:0% running they'll report it and then people<00:07:56.479> check<00:07:56.750> it<00:07:56.960> and<00:07:57.140> if<00:07:58.010> we<00:07:58.310> discover 00:07:58.600 --> 00:07:58.610 align:start position:0% people check it and if we discover 00:07:58.610 --> 00:08:00.790 align:start position:0% people check it and if we discover someone<00:07:58.880> was<00:07:59.450> lying<00:07:59.660> one<00:08:00.290> of<00:08:00.410> these<00:08:00.500> five<00:08:00.680> to 00:08:00.790 --> 00:08:00.800 align:start position:0% someone was lying one of these five to 00:08:00.800 --> 00:08:04.840 align:start position:0% someone was lying one of these five to seven<00:08:01.040> signs<00:08:01.250> in<00:08:01.370> a<00:08:01.430> banded<00:08:01.729> block<00:08:02.140> will<00:08:03.850> will 00:08:04.840 --> 00:08:04.850 align:start position:0% seven signs in a banded block will will 00:08:04.850 --> 00:08:06.100 align:start position:0% seven signs in a banded block will will slash<00:08:05.120> them<00:08:05.330> we'll<00:08:05.450> take<00:08:05.479> away<00:08:05.720> their<00:08:05.900> stage 00:08:06.100 --> 00:08:06.110 align:start position:0% slash them we'll take away their stage 00:08:06.110 --> 00:08:11.020 align:start position:0% slash them we'll take away their stage and<00:08:08.470> we<00:08:09.470> can<00:08:09.650> allow<00:08:09.860> sort<00:08:10.190> of<00:08:10.250> fisherman<00:08:10.640> just 00:08:11.020 --> 00:08:11.030 align:start position:0% and we can allow sort of fisherman just 00:08:11.030 --> 00:08:12.490 align:start position:0% and we can allow sort of fisherman just take<00:08:11.240> themselves<00:08:11.450> we<00:08:11.930> can<00:08:12.080> band<00:08:12.350> them 00:08:12.490 --> 00:08:12.500 align:start position:0% take themselves we can band them 00:08:12.500 --> 00:08:14.920 align:start position:0% take themselves we can band them together<00:08:12.590> a<00:08:13.040> fisherman<00:08:13.790> lie<00:08:14.300> that<00:08:14.630> they<00:08:14.780> get 00:08:14.920 --> 00:08:14.930 align:start position:0% together a fisherman lie that they get 00:08:14.930 --> 00:08:17.610 align:start position:0% together a fisherman lie that they get slashed<00:08:15.229> it's<00:08:16.220> like<00:08:16.340> if<00:08:16.520> you're<00:08:16.640> in<00:08:16.729> there<00:08:17.000> a 00:08:17.610 --> 00:08:17.620 align:start position:0% slashed it's like if you're in there a 00:08:17.620 --> 00:08:21.340 align:start position:0% slashed it's like if you're in there a fisherman<00:08:18.620> and<00:08:19.750> you<00:08:20.750> want<00:08:20.900> to<00:08:20.990> convince<00:08:21.169> all 00:08:21.340 --> 00:08:21.350 align:start position:0% fisherman and you want to convince all 00:08:21.350 --> 00:08:22.810 align:start position:0% fisherman and you want to convince all your<00:08:21.500> friends<00:08:21.770> to<00:08:21.890> join<00:08:21.919> in<00:08:22.220> and<00:08:22.400> say<00:08:22.520> this<00:08:22.669> is 00:08:22.810 --> 00:08:22.820 align:start position:0% your friends to join in and say this is 00:08:22.820 --> 00:08:24.190 align:start position:0% your friends to join in and say this is true<00:08:22.970> and<00:08:23.300> this<00:08:23.390> will<00:08:23.540> ensure<00:08:23.930> that<00:08:23.960> we 00:08:24.190 --> 00:08:24.200 align:start position:0% true and this will ensure that we 00:08:24.200 --> 00:08:27.219 align:start position:0% true and this will ensure that we recheck<00:08:25.010> it<00:08:25.130> enough<00:08:25.370> and<00:08:25.690> if<00:08:26.690> you're<00:08:26.870> correct 00:08:27.219 --> 00:08:27.229 align:start position:0% recheck it enough and if you're correct 00:08:27.229 --> 00:08:33.000 align:start position:0% recheck it enough and if you're correct you<00:08:27.830> will<00:08:27.979> get<00:08:28.160> a<00:08:28.190> reward<00:08:30.130> but<00:08:31.130> the<00:08:31.250> problem<00:08:31.610> is 00:08:33.000 --> 00:08:33.010 align:start position:0% you will get a reward but the problem is 00:08:33.010 --> 00:08:35.079 align:start position:0% you will get a reward but the problem is you<00:08:34.010> can't<00:08:34.219> buy<00:08:34.339> a<00:08:34.370> datum<00:08:34.669> clock<00:08:34.789> you<00:08:34.909> never 00:08:35.079 --> 00:08:35.089 align:start position:0% you can't buy a datum clock you never 00:08:35.089 --> 00:08:38.230 align:start position:0% you can't buy a datum clock you never see<00:08:35.270> and<00:08:36.190> validators<00:08:37.190> don't<00:08:37.400> know<00:08:37.580> that<00:08:38.150> the 00:08:38.230 --> 00:08:38.240 align:start position:0% see and validators don't know that the 00:08:38.240 --> 00:08:41.740 align:start position:0% see and validators don't know that the full<00:08:38.390> nodes<00:08:38.570> never<00:08:38.810> saw<00:08:38.990> it<00:08:39.169> and<00:08:40.599> even<00:08:41.599> if<00:08:41.690> the 00:08:41.740 --> 00:08:41.750 align:start position:0% full nodes never saw it and even if the 00:08:41.750 --> 00:08:44.250 align:start position:0% full nodes never saw it and even if the pool<00:08:41.900> nodes<00:08:42.080> say<00:08:42.229> they<00:08:42.380> didn't<00:08:42.620> see<00:08:42.710> it<00:08:42.860> and 00:08:44.250 --> 00:08:44.260 align:start position:0% pool nodes say they didn't see it and 00:08:44.260 --> 00:08:46.780 align:start position:0% pool nodes say they didn't see it and instead<00:08:45.260> of<00:08:45.350> subjective<00:08:45.800> we<00:08:46.310> have<00:08:46.430> no<00:08:46.610> way<00:08:46.760> of 00:08:46.780 --> 00:08:46.790 align:start position:0% instead of subjective we have no way of 00:08:46.790 --> 00:08:48.820 align:start position:0% instead of subjective we have no way of verifying<00:08:46.880> that<00:08:47.300> all<00:08:47.660> we<00:08:48.290> can<00:08:48.410> do<00:08:48.500> is<00:08:48.620> after 00:08:48.820 --> 00:08:48.830 align:start position:0% verifying that all we can do is after 00:08:48.830 --> 00:08:50.150 align:start position:0% verifying that all we can do is after the<00:08:48.920> day<00:08:49.010> to<00:08:49.070> ourselves<00:08:49.190> which 00:08:50.150 --> 00:08:50.160 align:start position:0% the day to ourselves which 00:08:50.160 --> 00:08:52.519 align:start position:0% the day to ourselves which point<00:08:50.339> if<00:08:50.940> everyone<00:08:51.360> has<00:08:51.509> the<00:08:51.629> data<00:08:51.959> we're<00:08:52.440> not 00:08:52.519 --> 00:08:52.529 align:start position:0% point if everyone has the data we're not 00:08:52.529 --> 00:08:55.639 align:start position:0% point if everyone has the data we're not scalable<00:08:52.920> anymore<00:08:53.279> and<00:08:54.170> maybe<00:08:55.170> when<00:08:55.379> we<00:08:55.500> ask 00:08:55.639 --> 00:08:55.649 align:start position:0% scalable anymore and maybe when we ask 00:08:55.649 --> 00:08:56.960 align:start position:0% scalable anymore and maybe when we ask for<00:08:55.740> it<00:08:55.920> when<00:08:55.949> the<00:08:56.160> validators<00:08:56.579> aspirated 00:08:56.960 --> 00:08:56.970 align:start position:0% for it when the validators aspirated 00:08:56.970 --> 00:09:00.410 align:start position:0% for it when the validators aspirated shows<00:08:57.180> up<00:08:57.740> and<00:08:58.740> it's<00:08:58.980> correct<00:08:59.220> but<00:09:00.120> we<00:09:00.240> don't 00:09:00.410 --> 00:09:00.420 align:start position:0% shows up and it's correct but we don't 00:09:00.420 --> 00:09:03.530 align:start position:0% shows up and it's correct but we don't know<00:09:00.569> we<00:09:01.050> can't<00:09:01.230> slash<00:09:01.440> anyone<00:09:02.269> it's<00:09:03.269> a<00:09:03.329> kind 00:09:03.530 --> 00:09:03.540 align:start position:0% know we can't slash anyone it's a kind 00:09:03.540 --> 00:09:06.860 align:start position:0% know we can't slash anyone it's a kind of<00:09:04.490> the<00:09:05.490> reason<00:09:05.819> this<00:09:05.970> wasn't<00:09:06.269> the<00:09:06.480> problem 00:09:06.860 --> 00:09:06.870 align:start position:0% of the reason this wasn't the problem 00:09:06.870 --> 00:09:08.960 align:start position:0% of the reason this wasn't the problem with<00:09:06.990> it<00:09:07.139> with<00:09:07.259> the<00:09:07.350> theorem<00:09:07.709> Rob<00:09:08.490> Quintero 00:09:08.960 --> 00:09:08.970 align:start position:0% with it with the theorem Rob Quintero 00:09:08.970 --> 00:09:12.530 align:start position:0% with it with the theorem Rob Quintero his<00:09:09.240> Bitcoin<00:09:09.600> was<00:09:10.439> because<00:09:11.420> the<00:09:12.420> people 00:09:12.530 --> 00:09:12.540 align:start position:0% his Bitcoin was because the people 00:09:12.540 --> 00:09:14.420 align:start position:0% his Bitcoin was because the people responsible<00:09:13.290> for<00:09:13.500> the<00:09:13.680> entire<00:09:13.889> set<00:09:14.160> of<00:09:14.339> the 00:09:14.420 --> 00:09:14.430 align:start position:0% responsible for the entire set of the 00:09:14.430 --> 00:09:17.900 align:start position:0% responsible for the entire set of the consensus<00:09:15.680> were<00:09:16.680> the<00:09:16.800> same<00:09:16.949> people<00:09:17.129> who<00:09:17.550> kept 00:09:17.900 --> 00:09:17.910 align:start position:0% consensus were the same people who kept 00:09:17.910 --> 00:09:22.249 align:start position:0% consensus were the same people who kept the<00:09:18.120> data<00:09:18.300> available<00:09:20.120> and<00:09:21.120> you<00:09:21.959> know<00:09:22.050> at<00:09:22.170> least 00:09:22.249 --> 00:09:22.259 align:start position:0% the data available and you know at least 00:09:22.259 --> 00:09:23.600 align:start position:0% the data available and you know at least all<00:09:22.470> the<00:09:22.589> miners<00:09:22.860> keep<00:09:22.980> the<00:09:23.100> data<00:09:23.220> available 00:09:23.600 --> 00:09:23.610 align:start position:0% all the miners keep the data available 00:09:23.610 --> 00:09:27.650 align:start position:0% all the miners keep the data available as<00:09:23.759> do<00:09:23.910> all<00:09:24.029> other<00:09:24.060> full<00:09:24.389> nodes<00:09:26.389> so<00:09:27.389> what<00:09:27.540> we 00:09:27.650 --> 00:09:27.660 align:start position:0% as do all other full nodes so what we 00:09:27.660 --> 00:09:29.119 align:start position:0% as do all other full nodes so what we really<00:09:27.899> would<00:09:28.019> like<00:09:28.199> is<00:09:28.410> to<00:09:28.439> sort<00:09:28.740> of<00:09:28.769> do<00:09:28.980> that 00:09:29.119 --> 00:09:29.129 align:start position:0% really would like is to sort of do that 00:09:29.129 --> 00:09:31.369 align:start position:0% really would like is to sort of do that again<00:09:29.490> and<00:09:30.269> we<00:09:30.420> can<00:09:30.569> kind<00:09:30.779> of<00:09:30.839> do<00:09:30.959> this<00:09:31.079> there 00:09:31.369 --> 00:09:31.379 align:start position:0% again and we can kind of do this there 00:09:31.379 --> 00:09:33.980 align:start position:0% again and we can kind of do this there is<00:09:31.500> a<00:09:31.529> solution<00:09:32.040> everyone<00:09:32.490> kind<00:09:32.699> of<00:09:32.790> it's<00:09:33.689> an 00:09:33.980 --> 00:09:33.990 align:start position:0% is a solution everyone kind of it's an 00:09:33.990 --> 00:09:36.650 align:start position:0% is a solution everyone kind of it's an old<00:09:34.170> solution<00:09:34.939> for<00:09:35.939> a<00:09:35.970> busty<00:09:36.240> storing<00:09:36.509> data 00:09:36.650 --> 00:09:36.660 align:start position:0% old solution for a busty storing data 00:09:36.660 --> 00:09:40.300 align:start position:0% old solution for a busty storing data all<00:09:36.870> nice<00:09:37.050> you<00:09:37.259> do<00:09:37.379> use<00:09:37.589> of<00:09:37.709> radio<00:09:37.980> coding<00:09:38.660> so 00:09:40.300 --> 00:09:40.310 align:start position:0% all nice you do use of radio coding so 00:09:40.310 --> 00:09:42.769 align:start position:0% all nice you do use of radio coding so you<00:09:41.310> sort<00:09:41.490> of<00:09:41.579> had<00:09:41.910> some<00:09:42.060> redundancy<00:09:42.540> to<00:09:42.660> your 00:09:42.769 --> 00:09:42.779 align:start position:0% you sort of had some redundancy to your 00:09:42.779 --> 00:09:46.519 align:start position:0% you sort of had some redundancy to your data<00:09:42.959> and<00:09:43.589> then<00:09:44.810> you<00:09:45.810> divide<00:09:46.050> it<00:09:46.230> into<00:09:46.319> four 00:09:46.519 --> 00:09:46.529 align:start position:0% data and then you divide it into four 00:09:46.529 --> 00:09:51.650 align:start position:0% data and then you divide it into four pieces<00:09:46.560> and<00:09:49.310> even<00:09:50.310> if<00:09:50.399> a<00:09:50.790> large<00:09:51.360> number<00:09:51.420> of 00:09:51.650 --> 00:09:51.660 align:start position:0% pieces and even if a large number of 00:09:51.660 --> 00:09:52.999 align:start position:0% pieces and even if a large number of these<00:09:51.779> pieces<00:09:51.959> go<00:09:52.170> missing<00:09:52.529> you<00:09:52.680> can<00:09:52.740> still 00:09:52.999 --> 00:09:53.009 align:start position:0% these pieces go missing you can still 00:09:53.009 --> 00:09:55.790 align:start position:0% these pieces go missing you can still reconstruct<00:09:53.490> it<00:09:53.579> from<00:09:53.639> the<00:09:53.790> remainder<00:09:54.029> and<00:09:54.800> so 00:09:55.790 --> 00:09:55.800 align:start position:0% reconstruct it from the remainder and so 00:09:55.800 --> 00:09:59.990 align:start position:0% reconstruct it from the remainder and so we<00:09:55.920> can<00:09:56.040> use<00:09:56.189> this<00:09:57.709> to<00:09:58.709> make<00:09:58.949> the<00:09:59.220> that<00:09:59.880> the 00:09:59.990 --> 00:10:00.000 align:start position:0% we can use this to make the that the 00:10:00.000 --> 00:10:01.460 align:start position:0% we can use this to make the that the whole<00:10:00.180> set<00:10:00.360> up<00:10:00.480> validator<00:10:00.839> is<00:10:00.930> responsible 00:10:01.460 --> 00:10:01.470 align:start position:0% whole set up validator is responsible 00:10:01.470 --> 00:10:02.840 align:start position:0% whole set up validator is responsible for<00:10:01.500> the<00:10:01.680> availability<00:10:02.009> of<00:10:02.189> every<00:10:02.399> data<00:10:02.610> with 00:10:02.840 --> 00:10:02.850 align:start position:0% for the availability of every data with 00:10:02.850 --> 00:10:08.030 align:start position:0% for the availability of every data with all<00:10:03.329> the<00:10:03.360> data<00:10:03.709> without<00:10:06.680> overloading<00:10:07.680> any<00:10:07.949> of 00:10:08.030 --> 00:10:08.040 align:start position:0% all the data without overloading any of 00:10:08.040 --> 00:10:10.189 align:start position:0% all the data without overloading any of them<00:10:08.360> so<00:10:09.360> with<00:10:09.569> the<00:10:09.630> way<00:10:09.720> we<00:10:09.870> do<00:10:10.019> this 00:10:10.189 --> 00:10:10.199 align:start position:0% them so with the way we do this 00:10:10.199 --> 00:10:12.199 align:start position:0% them so with the way we do this hurricane<00:10:10.740> validators<00:10:11.279> send<00:10:11.819> the<00:10:11.910> pieces<00:10:12.149> of 00:10:12.199 --> 00:10:12.209 align:start position:0% hurricane validators send the pieces of 00:10:12.209 --> 00:10:14.900 align:start position:0% hurricane validators send the pieces of the<00:10:12.269> data<00:10:12.420> to<00:10:12.630> every<00:10:12.779> other<00:10:13.050> of<00:10:13.170> our<00:10:13.230> data<00:10:13.910> and 00:10:14.900 --> 00:10:14.910 align:start position:0% the data to every other of our data and 00:10:14.910 --> 00:10:17.960 align:start position:0% the data to every other of our data and one<00:10:15.180> third<00:10:15.420> of<00:10:15.509> bio-datas<00:10:16.019> it<00:10:16.819> pieces<00:10:17.819> belong 00:10:17.960 --> 00:10:17.970 align:start position:0% one third of bio-datas it pieces belong 00:10:17.970 --> 00:10:19.160 align:start position:0% one third of bio-datas it pieces belong to<00:10:18.120> a<00:10:18.180> third<00:10:18.360> of<00:10:18.389> our<00:10:18.540> data<00:10:18.779> -<00:10:18.899> enough<00:10:19.050> to 00:10:19.160 --> 00:10:19.170 align:start position:0% to a third of our data - enough to 00:10:19.170 --> 00:10:22.790 align:start position:0% to a third of our data - enough to reconstruct<00:10:19.649> and<00:10:20.279> then<00:10:20.819> we<00:10:21.029> make<00:10:21.680> voting<00:10:22.680> the 00:10:22.790 --> 00:10:22.800 align:start position:0% reconstruct and then we make voting the 00:10:22.800 --> 00:10:24.170 align:start position:0% reconstruct and then we make voting the consensus<00:10:23.250> particular<00:10:23.699> in<00:10:23.790> the<00:10:23.850> finality 00:10:24.170 --> 00:10:24.180 align:start position:0% consensus particular in the finality 00:10:24.180 --> 00:10:26.689 align:start position:0% consensus particular in the finality gadget<00:10:24.709> which<00:10:25.709> is<00:10:25.889> the<00:10:26.009> Byzantine<00:10:26.160> agreement 00:10:26.689 --> 00:10:26.699 align:start position:0% gadget which is the Byzantine agreement 00:10:26.699 --> 00:10:27.949 align:start position:0% gadget which is the Byzantine agreement our<00:10:26.790> than<00:10:27.029> we<00:10:27.089> need<00:10:27.240> two<00:10:27.360> thirds<00:10:27.569> of<00:10:27.630> people<00:10:27.750> to 00:10:27.949 --> 00:10:27.959 align:start position:0% our than we need two thirds of people to 00:10:27.959 --> 00:10:31.519 align:start position:0% our than we need two thirds of people to sign<00:10:29.569> conditional<00:10:30.569> on<00:10:30.630> having<00:10:30.959> all<00:10:31.230> the 00:10:31.519 --> 00:10:31.529 align:start position:0% sign conditional on having all the 00:10:31.529 --> 00:10:35.780 align:start position:0% sign conditional on having all the pieces<00:10:31.709> you<00:10:31.889> supposed<00:10:32.100> to<00:10:32.160> have<00:10:32.339> and<00:10:34.790> what 00:10:35.780 --> 00:10:35.790 align:start position:0% pieces you supposed to have and what 00:10:35.790 --> 00:10:37.340 align:start position:0% pieces you supposed to have and what this<00:10:35.910> means<00:10:36.180> is<00:10:36.480> that<00:10:36.540> if<00:10:36.779> we<00:10:36.809> finalize<00:10:37.319> a 00:10:37.340 --> 00:10:37.350 align:start position:0% this means is that if we finalize a 00:10:37.350 --> 00:10:39.860 align:start position:0% this means is that if we finalize a block<00:10:37.589> and<00:10:37.920> we're<00:10:38.490> two-thirds<00:10:38.850> honest<00:10:39.149> then 00:10:39.860 --> 00:10:39.870 align:start position:0% block and we're two-thirds honest then 00:10:39.870 --> 00:10:41.980 align:start position:0% block and we're two-thirds honest then the<00:10:39.959> block<00:10:40.139> is<00:10:40.259> available<00:10:40.649> in<00:10:40.740> principle 00:10:41.980 --> 00:10:41.990 align:start position:0% the block is available in principle 00:10:41.990 --> 00:10:45.019 align:start position:0% the block is available in principle right<00:10:42.990> we<00:10:43.259> can<00:10:43.410> reconstruct<00:10:43.709> it<00:10:43.980> so<00:10:44.130> the<00:10:44.850> data 00:10:45.019 --> 00:10:45.029 align:start position:0% right we can reconstruct it so the data 00:10:45.029 --> 00:10:48.769 align:start position:0% right we can reconstruct it so the data if<00:10:45.569> we<00:10:46.199> work<00:10:46.680> with<00:10:46.860> we<00:10:47.309> are<00:10:47.459> two<00:10:48.329> packs<00:10:48.569> of<00:10:48.660> two 00:10:48.769 --> 00:10:48.779 align:start position:0% if we work with we are two packs of two 00:10:48.779 --> 00:10:51.110 align:start position:0% if we work with we are two packs of two thirds<00:10:49.019> on<00:10:49.139> it<00:10:49.370> and<00:10:50.370> we'd<00:10:50.579> really<00:10:50.699> like<00:10:50.879> to<00:10:51.029> be 00:10:51.110 --> 00:10:51.120 align:start position:0% thirds on it and we'd really like to be 00:10:51.120 --> 00:10:54.579 align:start position:0% thirds on it and we'd really like to be rational<00:10:51.540> that<00:10:52.910> we<00:10:53.910> can<00:10:54.029> do<00:10:54.120> that<00:10:54.269> as<00:10:54.329> well 00:10:54.579 --> 00:10:54.589 align:start position:0% rational that we can do that as well 00:10:54.589 --> 00:10:59.620 align:start position:0% rational that we can do that as well then<00:10:57.559> it's<00:10:58.559> available 00:10:59.620 --> 00:10:59.630 align:start position:0% then it's available 00:10:59.630 --> 00:11:02.170 align:start position:0% then it's available but<00:11:00.410> there<00:11:00.529> is<00:11:00.589> a<00:11:00.649> problem<00:11:00.860> here<00:11:01.160> which<00:11:01.430> if<00:11:01.759> you 00:11:02.170 --> 00:11:02.180 align:start position:0% but there is a problem here which if you 00:11:02.180 --> 00:11:05.290 align:start position:0% but there is a problem here which if you launch<00:11:02.959> an<00:11:03.110> attack<00:11:03.790> are<00:11:04.790> we<00:11:04.910> going<00:11:05.089> to<00:11:05.149> catch 00:11:05.290 --> 00:11:05.300 align:start position:0% launch an attack are we going to catch 00:11:05.300 --> 00:11:06.040 align:start position:0% launch an attack are we going to catch you<00:11:05.449> in<00:11:05.569> the<00:11:05.600> end 00:11:06.040 --> 00:11:06.050 align:start position:0% you in the end 00:11:06.050 --> 00:11:09.490 align:start position:0% you in the end you<00:11:06.470> know<00:11:06.589> it's<00:11:06.860> these<00:11:07.250> 10<00:11:07.550> validators<00:11:08.500> sign 00:11:09.490 --> 00:11:09.500 align:start position:0% you know it's these 10 validators sign 00:11:09.500 --> 00:11:10.629 align:start position:0% you know it's these 10 validators sign in<00:11:09.649> the<00:11:09.709> ballot<00:11:09.980> box<00:11:10.009> we're<00:11:10.310> going<00:11:10.370> to<00:11:10.459> catch 00:11:10.629 --> 00:11:10.639 align:start position:0% in the ballot box we're going to catch 00:11:10.639 --> 00:11:13.030 align:start position:0% in the ballot box we're going to catch them<00:11:10.850> we're<00:11:10.970> gonna<00:11:11.060> slice<00:11:11.389> them<00:11:12.040> ideally 00:11:13.030 --> 00:11:13.040 align:start position:0% them we're gonna slice them ideally 00:11:13.040 --> 00:11:14.139 align:start position:0% them we're gonna slice them ideally that'd<00:11:13.220> be<00:11:13.339> sort<00:11:13.519> of<00:11:13.550> a<00:11:13.639> hundredth<00:11:13.940> of<00:11:14.029> the 00:11:14.139 --> 00:11:14.149 align:start position:0% that'd be sort of a hundredth of the 00:11:14.149 --> 00:11:19.949 align:start position:0% that'd be sort of a hundredth of the state<00:11:14.329> in<00:11:14.449> the<00:11:14.540> entire<00:11:14.750> system<00:11:17.529> but<00:11:18.529> that 00:11:19.949 --> 00:11:19.959 align:start position:0% state in the entire system but that 00:11:19.959 --> 00:11:21.309 align:start position:0% state in the entire system but that isn't<00:11:20.959> good<00:11:21.050> enough 00:11:21.309 --> 00:11:21.319 align:start position:0% isn't good enough 00:11:21.319 --> 00:11:24.100 align:start position:0% isn't good enough so<00:11:22.160> what<00:11:22.670> can<00:11:22.790> happen<00:11:23.000> is<00:11:23.240> that<00:11:23.269> these<00:11:23.870> guys 00:11:24.100 --> 00:11:24.110 align:start position:0% so what can happen is that these guys 00:11:24.110 --> 00:11:27.819 align:start position:0% so what can happen is that these guys can<00:11:24.350> send<00:11:26.019> signed<00:11:27.019> invalid<00:11:27.440> both<00:11:27.620> make<00:11:27.800> a 00:11:27.819 --> 00:11:27.829 align:start position:0% can send signed invalid both make a 00:11:27.829 --> 00:11:29.379 align:start position:0% can send signed invalid both make a sender<00:11:28.130> transaction<00:11:28.639> to<00:11:28.730> a<00:11:28.759> Bitcoin<00:11:29.089> bridge 00:11:29.379 --> 00:11:29.389 align:start position:0% sender transaction to a Bitcoin bridge 00:11:29.389 --> 00:11:31.720 align:start position:0% sender transaction to a Bitcoin bridge that<00:11:29.660> owns<00:11:29.810> a<00:11:29.959> lot<00:11:30.079> of<00:11:30.550> external<00:11:31.550> things 00:11:31.720 --> 00:11:31.730 align:start position:0% that owns a lot of external things 00:11:31.730 --> 00:11:34.930 align:start position:0% that owns a lot of external things Bitcoin<00:11:32.180> and<00:11:33.459> tells<00:11:34.459> them<00:11:34.610> to<00:11:34.699> pay<00:11:34.819> the 00:11:34.930 --> 00:11:34.940 align:start position:0% Bitcoin and tells them to pay the 00:11:34.940 --> 00:11:38.079 align:start position:0% Bitcoin and tells them to pay the Bitcoin<00:11:35.240> and<00:11:35.480> this<00:11:36.470> means<00:11:36.680> that<00:11:37.069> if<00:11:37.940> that's 00:11:38.079 --> 00:11:38.089 align:start position:0% Bitcoin and this means that if that's 00:11:38.089 --> 00:11:39.160 align:start position:0% Bitcoin and this means that if that's more<00:11:38.300> than<00:11:38.449> one<00:11:38.540> hundredth<00:11:38.779> of<00:11:38.810> the<00:11:38.870> stake<00:11:39.050> in 00:11:39.160 --> 00:11:39.170 align:start position:0% more than one hundredth of the stake in 00:11:39.170 --> 00:11:44.800 align:start position:0% more than one hundredth of the stake in the<00:11:39.230> system<00:11:39.380> they<00:11:39.949> make<00:11:40.100> a<00:11:40.130> profit<00:11:42.190> and<00:11:43.600> it<00:11:44.600> we 00:11:44.800 --> 00:11:44.810 align:start position:0% the system they make a profit and it we 00:11:44.810 --> 00:11:46.600 align:start position:0% the system they make a profit and it we can't<00:11:45.019> revert<00:11:45.199> it<00:11:45.380> on<00:11:45.470> our<00:11:45.589> chain<00:11:45.769> because 00:11:46.600 --> 00:11:46.610 align:start position:0% can't revert it on our chain because 00:11:46.610 --> 00:11:50.769 align:start position:0% can't revert it on our chain because we're<00:11:46.940> not<00:11:47.029> Bitcoin<00:11:48.940> but<00:11:49.940> we<00:11:50.389> can<00:11:50.509> get<00:11:50.630> around 00:11:50.769 --> 00:11:50.779 align:start position:0% we're not Bitcoin but we can get around 00:11:50.779 --> 00:11:52.389 align:start position:0% we're not Bitcoin but we can get around this<00:11:50.959> if<00:11:51.170> we<00:11:51.350> have<00:11:51.500> a<00:11:51.529> protocol<00:11:52.009> to<00:11:52.069> catch 00:11:52.389 --> 00:11:52.399 align:start position:0% this if we have a protocol to catch 00:11:52.399 --> 00:11:56.620 align:start position:0% this if we have a protocol to catch people<00:11:52.730> quickly<00:11:53.139> so<00:11:54.139> if<00:11:54.380> 99%<00:11:55.220> of<00:11:55.670> the<00:11:55.759> time<00:11:55.970> we 00:11:56.620 --> 00:11:56.630 align:start position:0% people quickly so if 99% of the time we 00:11:56.630 --> 00:11:57.819 align:start position:0% people quickly so if 99% of the time we catch<00:11:56.839> this<00:11:57.050> before<00:11:57.230> they<00:11:57.470> pay<00:11:57.620> you<00:11:57.680> the 00:11:57.819 --> 00:11:57.829 align:start position:0% catch this before they pay you the 00:11:57.829 --> 00:12:00.519 align:start position:0% catch this before they pay you the Bitcoin<00:11:58.360> every<00:11:59.360> 1%<00:11:59.509> of<00:11:59.810> the<00:11:59.870> time<00:11:59.959> you<00:12:00.139> succeed 00:12:00.519 --> 00:12:00.529 align:start position:0% Bitcoin every 1% of the time you succeed 00:12:00.529 --> 00:12:03.100 align:start position:0% Bitcoin every 1% of the time you succeed the<00:12:01.009> expected<00:12:01.459> cost<00:12:01.579> an<00:12:01.730> attack<00:12:02.029> under<00:12:02.899> the 00:12:03.100 --> 00:12:03.110 align:start position:0% the expected cost an attack under the 00:12:03.110 --> 00:12:05.290 align:start position:0% the expected cost an attack under the state<00:12:03.319> want<00:12:03.589> and<00:12:03.800> at<00:12:03.889> the<00:12:03.920> time<00:12:04.130> they<00:12:04.730> all<00:12:05.180> the 00:12:05.290 --> 00:12:05.300 align:start position:0% state want and at the time they all the 00:12:05.300 --> 00:12:07.059 align:start position:0% state want and at the time they all the stake<00:12:05.480> in<00:12:05.569> the<00:12:05.660> entire<00:12:05.839> system<00:12:06.019> it's<00:12:06.740> cheaper 00:12:07.059 --> 00:12:07.069 align:start position:0% stake in the entire system it's cheaper 00:12:07.069 --> 00:12:10.840 align:start position:0% stake in the entire system it's cheaper to<00:12:07.100> attack<00:12:07.399> the<00:12:07.579> the<00:12:08.230> the<00:12:09.230> main<00:12:09.410> chain<00:12:09.649> and<00:12:09.949> the 00:12:10.840 --> 00:12:10.850 align:start position:0% to attack the the the main chain and the 00:12:10.850 --> 00:12:14.610 align:start position:0% to attack the the the main chain and the entire<00:12:11.060> system<00:12:11.240> than<00:12:11.509> is<00:12:11.689> any<00:12:11.839> one<00:12:12.230> component 00:12:14.610 --> 00:12:14.620 align:start position:0% entire system than is any one component 00:12:14.620 --> 00:12:16.840 align:start position:0% entire system than is any one component but<00:12:15.620> we<00:12:15.680> need<00:12:15.829> a<00:12:15.860> protocol<00:12:16.220> for<00:12:16.370> this<00:12:16.490> so<00:12:16.699> what 00:12:16.840 --> 00:12:16.850 align:start position:0% but we need a protocol for this so what 00:12:16.850 --> 00:12:18.790 align:start position:0% but we need a protocol for this so what happens<00:12:17.240> is<00:12:17.509> that<00:12:17.569> we<00:12:18.050> take<00:12:18.290> reports<00:12:18.620> of 00:12:18.790 --> 00:12:18.800 align:start position:0% happens is that we take reports of 00:12:18.800 --> 00:12:21.629 align:start position:0% happens is that we take reports of invalidity<00:12:19.519> or<00:12:20.120> this<00:12:20.689> time<00:12:20.899> on<00:12:21.019> availability 00:12:21.629 --> 00:12:21.639 align:start position:0% invalidity or this time on availability 00:12:21.639 --> 00:12:25.749 align:start position:0% invalidity or this time on availability and<00:12:22.639> we<00:12:22.730> get<00:12:22.880> extra<00:12:23.089> people<00:12:23.300> to<00:12:23.449> check<00:12:23.689> it<00:12:24.759> we 00:12:25.749 --> 00:12:25.759 align:start position:0% and we get extra people to check it we 00:12:25.759 --> 00:12:28.240 align:start position:0% and we get extra people to check it we choose<00:12:25.939> the<00:12:26.029> extra<00:12:26.240> people<00:12:26.389> at<00:12:26.600> random<00:12:27.250> this 00:12:28.240 --> 00:12:28.250 align:start position:0% choose the extra people at random this 00:12:28.250 --> 00:12:30.579 align:start position:0% choose the extra people at random this is<00:12:28.430> this<00:12:28.670> is<00:12:28.790> important<00:12:29.269> I<00:12:29.540> will<00:12:30.290> use<00:12:30.439> a<00:12:30.529> to 00:12:30.579 --> 00:12:30.589 align:start position:0% is this is important I will use a to 00:12:30.589 --> 00:12:34.179 align:start position:0% is this is important I will use a to user<00:12:30.800> verifiable<00:12:31.399> random<00:12:31.670> function<00:12:32.000> so<00:12:33.189> the 00:12:34.179 --> 00:12:34.189 align:start position:0% user verifiable random function so the 00:12:34.189 --> 00:12:36.579 align:start position:0% user verifiable random function so the protein<00:12:34.610> the<00:12:35.149> people<00:12:35.660> validating<00:12:36.290> with<00:12:36.410> the 00:12:36.579 --> 00:12:36.589 align:start position:0% protein the people validating with the 00:12:36.589 --> 00:12:39.579 align:start position:0% protein the people validating with the shard<00:12:36.800> were<00:12:37.189> chosen<00:12:37.370> at<00:12:37.550> random<00:12:37.579> but<00:12:38.589> everyone 00:12:39.579 --> 00:12:39.589 align:start position:0% shard were chosen at random but everyone 00:12:39.589 --> 00:12:41.740 align:start position:0% shard were chosen at random but everyone knows<00:12:39.709> who<00:12:39.860> they<00:12:40.009> are<00:12:40.040> so<00:12:41.029> the<00:12:41.149> bad<00:12:41.269> guys<00:12:41.300> can 00:12:41.740 --> 00:12:41.750 align:start position:0% knows who they are so the bad guys can 00:12:41.750 --> 00:12:44.079 align:start position:0% knows who they are so the bad guys can just<00:12:41.899> wait<00:12:42.079> until<00:12:42.410> they<00:12:42.560> own<00:12:42.680> enough<00:12:43.220> attack 00:12:44.079 --> 00:12:44.089 align:start position:0% just wait until they own enough attack 00:12:44.089 --> 00:12:46.240 align:start position:0% just wait until they own enough attack the<00:12:44.240> rest<00:12:44.449> and<00:12:44.959> they're<00:12:45.350> fine<00:12:45.560> but<00:12:45.800> if<00:12:45.980> random 00:12:46.240 --> 00:12:46.250 align:start position:0% the rest and they're fine but if random 00:12:46.250 --> 00:12:48.519 align:start position:0% the rest and they're fine but if random people<00:12:46.490> checking<00:12:46.699> they<00:12:46.910> don't<00:12:47.089> know<00:12:47.439> on<00:12:48.439> the 00:12:48.519 --> 00:12:48.529 align:start position:0% people checking they don't know on the 00:12:48.529 --> 00:12:50.290 align:start position:0% people checking they don't know on the other<00:12:48.649> hand<00:12:48.860> of<00:12:48.980> vrf<00:12:49.310> everyone<00:12:49.790> can<00:12:49.910> knows 00:12:50.290 --> 00:12:50.300 align:start position:0% other hand of vrf everyone can knows 00:12:50.300 --> 00:12:52.030 align:start position:0% other hand of vrf everyone can knows who's<00:12:50.540> responsible<00:12:50.689> you<00:12:51.620> know<00:12:51.649> who<00:12:51.889> we<00:12:51.980> should 00:12:52.030 --> 00:12:52.040 align:start position:0% who's responsible you know who we should 00:12:52.040 --> 00:12:55.179 align:start position:0% who's responsible you know who we should be<00:12:52.579> checking<00:12:52.759> this<00:12:53.029> after<00:12:53.540> the<00:12:53.630> fact<00:12:54.100> we<00:12:55.100> know 00:12:55.179 --> 00:12:55.189 align:start position:0% be checking this after the fact we know 00:12:55.189 --> 00:12:56.590 align:start position:0% be checking this after the fact we know which<00:12:55.310> reports<00:12:55.639> we<00:12:55.730> should<00:12:55.880> pay<00:12:55.970> attention<00:12:56.149> to 00:12:56.590 --> 00:12:56.600 align:start position:0% which reports we should pay attention to 00:12:56.600 --> 00:12:59.740 align:start position:0% which reports we should pay attention to and<00:12:56.990> we<00:12:57.709> can<00:12:57.860> even<00:12:58.009> pay<00:12:58.189> them<00:12:58.540> and<00:12:59.540> then<00:12:59.660> if 00:12:59.740 --> 00:12:59.750 align:start position:0% and we can even pay them and then if 00:12:59.750 --> 00:13:01.420 align:start position:0% and we can even pay them and then if anyone<00:13:00.019> claims<00:13:00.139> it<00:13:00.380> in<00:13:00.500> behide<00:13:00.769> everyone 00:13:01.420 --> 00:13:01.430 align:start position:0% anyone claims it in behide everyone 00:13:01.430 --> 00:13:05.139 align:start position:0% anyone claims it in behide everyone downloads<00:13:01.790> it<00:13:01.910> in<00:13:01.970> checks<00:13:03.880> now<00:13:04.880> the<00:13:04.939> other 00:13:05.139 --> 00:13:05.149 align:start position:0% downloads it in checks now the other 00:13:05.149 --> 00:13:09.129 align:start position:0% downloads it in checks now the other things<00:13:05.389> you<00:13:05.480> could<00:13:05.569> do<00:13:05.750> you<00:13:06.579> could<00:13:07.809> do<00:13:08.809> random 00:13:09.129 --> 00:13:09.139 align:start position:0% things you could do you could do random 00:13:09.139 --> 00:13:11.280 align:start position:0% things you could do you could do random text<00:13:09.380> without<00:13:09.500> reports 00:13:11.280 --> 00:13:11.290 align:start position:0% text without reports 00:13:11.290 --> 00:13:13.530 align:start position:0% text without reports there's<00:13:11.740> this<00:13:11.830> this<00:13:11.890> great<00:13:12.250> idea<00:13:13.150> for<00:13:13.480> doing 00:13:13.530 --> 00:13:13.540 align:start position:0% there's this this great idea for doing 00:13:13.540 --> 00:13:15.660 align:start position:0% there's this this great idea for doing fraud<00:13:13.870> proofs<00:13:14.110> and<00:13:14.560> this<00:13:14.830> is<00:13:15.010> this<00:13:15.190> paper<00:13:15.430> that 00:13:15.660 --> 00:13:15.670 align:start position:0% fraud proofs and this is this paper that 00:13:15.670 --> 00:13:20.070 align:start position:0% fraud proofs and this is this paper that buy<00:13:15.940> the<00:13:16.600> stuff<00:13:16.750> robust<00:13:17.140> and<00:13:18.960> metallic<00:13:19.960> and 00:13:20.070 --> 00:13:20.080 align:start position:0% buy the stuff robust and metallic and 00:13:20.080 --> 00:13:23.550 align:start position:0% buy the stuff robust and metallic and Sonia<00:13:21.330> had<00:13:22.330> which<00:13:22.480> I<00:13:22.630> saw<00:13:22.780> Mustafa<00:13:23.200> talking 00:13:23.550 --> 00:13:23.560 align:start position:0% Sonia had which I saw Mustafa talking 00:13:23.560 --> 00:13:27.630 align:start position:0% Sonia had which I saw Mustafa talking about<00:13:23.740> Def<00:13:23.980> Con<00:13:24.130> last<00:13:24.160> year<00:13:24.840> where<00:13:25.840> we<00:13:26.490> do<00:13:27.490> some 00:13:27.630 --> 00:13:27.640 align:start position:0% about Def Con last year where we do some 00:13:27.640 --> 00:13:29.520 align:start position:0% about Def Con last year where we do some range<00:13:27.880> coding<00:13:28.330> but<00:13:28.630> we<00:13:28.750> sort<00:13:28.960> of<00:13:28.990> arrayed<00:13:29.410> your 00:13:29.520 --> 00:13:29.530 align:start position:0% range coding but we sort of arrayed your 00:13:29.530 --> 00:13:30.300 align:start position:0% range coding but we sort of arrayed your code<00:13:29.650> sub-blocks 00:13:30.300 --> 00:13:30.310 align:start position:0% code sub-blocks 00:13:30.310 --> 00:13:32.840 align:start position:0% code sub-blocks and<00:13:30.490> then<00:13:31.240> we<00:13:31.360> can<00:13:31.510> check<00:13:31.690> only<00:13:32.020> a<00:13:32.230> sub<00:13:32.470> block 00:13:32.840 --> 00:13:32.850 align:start position:0% and then we can check only a sub block 00:13:32.850 --> 00:13:35.130 align:start position:0% and then we can check only a sub block and<00:13:33.850> it<00:13:33.970> gives<00:13:34.120> us<00:13:34.210> a<00:13:34.240> small<00:13:34.420> proof<00:13:34.720> and<00:13:34.990> if<00:13:35.050> we 00:13:35.130 --> 00:13:35.140 align:start position:0% and it gives us a small proof and if we 00:13:35.140 --> 00:13:36.180 align:start position:0% and it gives us a small proof and if we have<00:13:35.230> a<00:13:35.260> small<00:13:35.470> proof<00:13:35.650> we<00:13:35.830> don't<00:13:35.980> need<00:13:36.070> this 00:13:36.180 --> 00:13:36.190 align:start position:0% have a small proof we don't need this 00:13:36.190 --> 00:13:40.980 align:start position:0% have a small proof we don't need this escalation<00:13:38.400> or<00:13:39.400> we<00:13:39.580> can<00:13:39.700> use<00:13:39.780> succinct<00:13:40.780> proofs 00:13:40.980 --> 00:13:40.990 align:start position:0% escalation or we can use succinct proofs 00:13:40.990 --> 00:13:42.930 align:start position:0% escalation or we can use succinct proofs to<00:13:41.230> come<00:13:42.130> into<00:13:42.250> every<00:13:42.490> one<00:13:42.580> of<00:13:42.640> the<00:13:42.730> validity 00:13:42.930 --> 00:13:42.940 align:start position:0% to come into every one of the validity 00:13:42.940 --> 00:13:44.910 align:start position:0% to come into every one of the validity and<00:13:43.210> reduce<00:13:43.420> the<00:13:43.690> only<00:13:43.900> problem<00:13:44.230> then<00:13:44.650> is 00:13:44.910 --> 00:13:44.920 align:start position:0% and reduce the only problem then is 00:13:44.920 --> 00:13:49.760 align:start position:0% and reduce the only problem then is availability<00:13:46.230> and<00:13:47.670> so<00:13:48.670> any<00:13:48.790> of<00:13:48.910> these<00:13:48.970> could 00:13:49.760 --> 00:13:49.770 align:start position:0% availability and so any of these could 00:13:49.770 --> 00:13:52.140 align:start position:0% availability and so any of these could could<00:13:50.770> be<00:13:50.800> used<00:13:51.010> in<00:13:51.130> F<00:13:51.220> 2.0<00:13:51.730> if<00:13:51.880> you<00:13:51.940> want<00:13:52.090> do 00:13:52.140 --> 00:13:52.150 align:start position:0% could be used in F 2.0 if you want do 00:13:52.150 --> 00:13:54.870 align:start position:0% could be used in F 2.0 if you want do the<00:13:52.270> same<00:13:52.420> thing<00:13:52.600> so<00:13:53.460> that<00:13:54.460> one<00:13:54.610> of<00:13:54.670> the<00:13:54.730> nice 00:13:54.870 --> 00:13:54.880 align:start position:0% the same thing so that one of the nice 00:13:54.880 --> 00:13:58.860 align:start position:0% the same thing so that one of the nice things<00:13:55.150> about<00:13:55.650> finality<00:13:56.650> gadgets<00:13:57.190> is<00:13:57.810> but<00:13:58.810> you 00:13:58.860 --> 00:13:58.870 align:start position:0% things about finality gadgets is but you 00:13:58.870 --> 00:14:00.620 align:start position:0% things about finality gadgets is but you don't<00:13:58.960> have<00:13:59.110> to<00:13:59.230> find<00:13:59.380> my<00:13:59.500> sink<00:13:59.710> straightaway 00:14:00.620 --> 00:14:00.630 align:start position:0% don't have to find my sink straightaway 00:14:00.630 --> 00:14:03.180 align:start position:0% don't have to find my sink straightaway so<00:14:01.630> what<00:14:01.720> we<00:14:01.840> do<00:14:01.990> is<00:14:02.170> we<00:14:02.320> delay<00:14:02.590> on<00:14:02.830> voting<00:14:03.010> on 00:14:03.180 --> 00:14:03.190 align:start position:0% so what we do is we delay on voting on 00:14:03.190 --> 00:14:05.010 align:start position:0% so what we do is we delay on voting on finality<00:14:03.490> until<00:14:04.390> we<00:14:04.480> have<00:14:04.630> all<00:14:04.660> the<00:14:04.810> array 00:14:05.010 --> 00:14:05.020 align:start position:0% finality until we have all the array 00:14:05.020 --> 00:14:08.100 align:start position:0% finality until we have all the array decoder<00:14:05.170> pieces<00:14:05.680> and<00:14:05.920> if<00:14:06.820> till<00:14:07.420> we<00:14:07.480> leave<00:14:07.930> some 00:14:08.100 --> 00:14:08.110 align:start position:0% decoder pieces and if till we leave some 00:14:08.110 --> 00:14:09.330 align:start position:0% decoder pieces and if till we leave some time<00:14:08.260> to<00:14:08.380> get<00:14:08.500> reports<00:14:08.890> and<00:14:09.010> if<00:14:09.070> they<00:14:09.190> don't 00:14:09.330 --> 00:14:09.340 align:start position:0% time to get reports and if they don't 00:14:09.340 --> 00:14:12.030 align:start position:0% time to get reports and if they don't show<00:14:09.550> up<00:14:10.050> they<00:14:11.050> do<00:14:11.170> show<00:14:11.350> up<00:14:11.410> then<00:14:11.680> we<00:14:11.770> have<00:14:11.920> to 00:14:12.030 --> 00:14:12.040 align:start position:0% show up they do show up then we have to 00:14:12.040 --> 00:14:14.970 align:start position:0% show up they do show up then we have to wait<00:14:12.160> for<00:14:12.460> checks<00:14:12.700> and<00:14:13.540> then<00:14:14.050> we<00:14:14.530> never<00:14:14.740> find 00:14:14.970 --> 00:14:14.980 align:start position:0% wait for checks and then we never find 00:14:14.980 --> 00:14:19.100 align:start position:0% wait for checks and then we never find lice<00:14:15.250> and<00:14:15.580> invalid<00:14:16.210> or<00:14:16.300> unavailable<00:14:16.900> block 00:14:19.100 --> 00:14:19.110 align:start position:0% lice and invalid or unavailable block 00:14:19.110 --> 00:14:21.780 align:start position:0% lice and invalid or unavailable block except<00:14:20.110> with<00:14:20.200> small<00:14:20.350> probability<00:14:20.800> as<00:14:21.040> long<00:14:21.640> as 00:14:21.780 --> 00:14:21.790 align:start position:0% except with small probability as long as 00:14:21.790 --> 00:14:23.640 align:start position:0% except with small probability as long as we<00:14:21.970> get<00:14:22.120> enough<00:14:22.270> reports<00:14:22.690> or<00:14:22.870> we<00:14:23.050> had<00:14:23.230> you<00:14:23.620> know 00:14:23.640 --> 00:14:23.650 align:start position:0% we get enough reports or we had you know 00:14:23.650 --> 00:14:26.310 align:start position:0% we get enough reports or we had you know enough<00:14:24.100> random<00:14:24.280> checks<00:14:24.930> and<00:14:25.930> that<00:14:26.050> doesn't 00:14:26.310 --> 00:14:26.320 align:start position:0% enough random checks and that doesn't 00:14:26.320 --> 00:14:27.450 align:start position:0% enough random checks and that doesn't slow<00:14:26.440> block<00:14:26.620> production<00:14:27.010> there's<00:14:27.250> a<00:14:27.280> bit<00:14:27.400> of 00:14:27.450 --> 00:14:27.460 align:start position:0% slow block production there's a bit of 00:14:27.460 --> 00:14:28.260 align:start position:0% slow block production there's a bit of an<00:14:27.520> issue<00:14:27.610> with<00:14:27.790> networking 00:14:28.260 --> 00:14:28.270 align:start position:0% an issue with networking 00:14:28.270 --> 00:14:30.360 align:start position:0% an issue with networking we<00:14:29.020> can't<00:14:29.200> gossip<00:14:29.470> all<00:14:29.590> these<00:14:29.680> pieces<00:14:29.830> but 00:14:30.360 --> 00:14:30.370 align:start position:0% we can't gossip all these pieces but 00:14:30.370 --> 00:14:33.390 align:start position:0% we can't gossip all these pieces but never<00:14:30.580> mind<00:14:30.700> that<00:14:30.810> we<00:14:31.810> can<00:14:31.930> solve<00:14:32.080> that<00:14:32.400> and 00:14:33.390 --> 00:14:33.400 align:start position:0% never mind that we can solve that and 00:14:33.400 --> 00:14:36.120 align:start position:0% never mind that we can solve that and the<00:14:33.970> result<00:14:34.270> is<00:14:34.390> that<00:14:34.600> we<00:14:34.750> can<00:14:34.930> secure<00:14:35.770> polka 00:14:36.120 --> 00:14:36.130 align:start position:0% the result is that we can secure polka 00:14:36.130 --> 00:14:38.370 align:start position:0% the result is that we can secure polka dot<00:14:36.280> with<00:14:36.640> only<00:14:37.240> ten<00:14:37.420> bio-datas<00:14:37.870> comparator 00:14:38.370 --> 00:14:38.380 align:start position:0% dot with only ten bio-datas comparator 00:14:38.380 --> 00:14:41.370 align:start position:0% dot with only ten bio-datas comparator and<00:14:38.640> still<00:14:39.640> have<00:14:39.760> that<00:14:39.790> secure<00:14:40.240> and<00:14:40.990> I<00:14:41.230> think 00:14:41.370 --> 00:14:41.380 align:start position:0% and still have that secure and I think 00:14:41.380 --> 00:14:42.510 align:start position:0% and still have that secure and I think if<00:14:41.470> they<00:14:41.590> Liam<00:14:41.770> could<00:14:41.890> use<00:14:42.010> a<00:14:42.100> similar<00:14:42.370> thing 00:14:42.510 --> 00:14:42.520 align:start position:0% if they Liam could use a similar thing 00:14:42.520 --> 00:14:43.950 align:start position:0% if they Liam could use a similar thing to<00:14:42.580> get<00:14:42.820> we<00:14:43.060> use<00:14:43.210> the<00:14:43.270> number<00:14:43.390> of<00:14:43.540> violators 00:14:43.950 --> 00:14:43.960 align:start position:0% to get we use the number of violators 00:14:43.960 --> 00:14:56.480 align:start position:0% to get we use the number of violators thank<00:14:44.530> you 00:14:56.480 --> 00:14:56.490 align:start position:0% 00:14:56.490 --> 00:14:58.550 align:start position:0% you