WEBVTT Kind: captions Language: en 00:00:04.410 --> 00:00:08.310 align:start position:0% Andrea<00:00:05.410> from<00:00:05.710> Leia<00:00:06.029> x-ray<00:00:07.029> X<00:00:07.270> is<00:00:07.509> a<00:00:07.540> Brockton 00:00:08.310 --> 00:00:08.320 align:start position:0% Andrea from Leia x-ray X is a Brockton 00:00:08.320 --> 00:00:10.770 align:start position:0% Andrea from Leia x-ray X is a Brockton startup<00:00:08.650> based<00:00:08.860> on<00:00:09.070> Tokyo<00:00:09.429> and<00:00:10.179> working<00:00:10.570> on 00:00:10.770 --> 00:00:10.780 align:start position:0% startup based on Tokyo and working on 00:00:10.780 --> 00:00:13.080 align:start position:0% startup based on Tokyo and working on Casper<00:00:11.380> research<00:00:11.680> and<00:00:12.040> its<00:00:12.640> positive<00:00:12.970> power 00:00:13.080 --> 00:00:13.090 align:start position:0% Casper research and its positive power 00:00:13.090 --> 00:00:16.589 align:start position:0% Casper research and its positive power its<00:00:13.360> own<00:00:13.480> Foundation<00:00:13.990> grant<00:00:14.400> so<00:00:15.400> today<00:00:15.790> I<00:00:16.209> will 00:00:16.589 --> 00:00:16.599 align:start position:0% its own Foundation grant so today I will 00:00:16.599 --> 00:00:19.019 align:start position:0% its own Foundation grant so today I will talk<00:00:16.810> about<00:00:17.080> my<00:00:17.830> research<00:00:18.070> on<00:00:18.279> the<00:00:18.670> security 00:00:19.019 --> 00:00:19.029 align:start position:0% talk about my research on the security 00:00:19.029 --> 00:00:22.560 align:start position:0% talk about my research on the security of<00:00:19.090> Casper<00:00:19.539> so<00:00:20.169> you<00:00:20.829> know<00:00:21.179> Casper<00:00:22.179> what 00:00:22.560 --> 00:00:22.570 align:start position:0% of Casper so you know Casper what 00:00:22.570 --> 00:00:24.359 align:start position:0% of Casper so you know Casper what consensus<00:00:22.989> protocol<00:00:23.439> has<00:00:23.769> two<00:00:23.980> property 00:00:24.359 --> 00:00:24.369 align:start position:0% consensus protocol has two property 00:00:24.369 --> 00:00:26.790 align:start position:0% consensus protocol has two property safety<00:00:25.029> and<00:00:25.179> aliveness<00:00:25.359> so<00:00:26.140> the<00:00:26.560> talk<00:00:26.769> is 00:00:26.790 --> 00:00:26.800 align:start position:0% safety and aliveness so the talk is 00:00:26.800 --> 00:00:29.370 align:start position:0% safety and aliveness so the talk is divided<00:00:27.279> into<00:00:27.489> two<00:00:27.759> parts<00:00:28.089> and<00:00:28.390> safety<00:00:29.140> part 00:00:29.370 --> 00:00:29.380 align:start position:0% divided into two parts and safety part 00:00:29.380 --> 00:00:33.930 align:start position:0% divided into two parts and safety part and<00:00:29.589> the<00:00:29.800> Lebanese<00:00:30.130> border<00:00:31.890> so<00:00:32.890> first<00:00:33.250> I<00:00:33.520> want 00:00:33.930 --> 00:00:33.940 align:start position:0% and the Lebanese border so first I want 00:00:33.940 --> 00:00:36.119 align:start position:0% and the Lebanese border so first I want to<00:00:33.970> introduce<00:00:34.170> Casper<00:00:35.170> is<00:00:35.380> not<00:00:35.680> that 00:00:36.119 --> 00:00:36.129 align:start position:0% to introduce Casper is not that 00:00:36.129 --> 00:00:38.040 align:start position:0% to introduce Casper is not that different<00:00:36.370> from<00:00:36.609> traditional<00:00:37.180> protocols<00:00:37.870> and 00:00:38.040 --> 00:00:38.050 align:start position:0% different from traditional protocols and 00:00:38.050 --> 00:00:40.259 align:start position:0% different from traditional protocols and Casper<00:00:38.769> FFG<00:00:39.280> and<00:00:39.550> the<00:00:39.609> shippi<00:00:39.850> she<00:00:39.910> is<00:00:40.059> not 00:00:40.259 --> 00:00:40.269 align:start position:0% Casper FFG and the shippi she is not 00:00:40.269 --> 00:00:41.400 align:start position:0% Casper FFG and the shippi she is not that<00:00:40.719> different<00:00:40.960> also 00:00:41.400 --> 00:00:41.410 align:start position:0% that different also 00:00:41.410 --> 00:00:47.430 align:start position:0% that different also so<00:00:43.679> first<00:00:44.820> pbft<00:00:45.820> tender<00:00:46.480> mint<00:00:46.690> and<00:00:46.929> Casper 00:00:47.430 --> 00:00:47.440 align:start position:0% so first pbft tender mint and Casper 00:00:47.440 --> 00:00:50.669 align:start position:0% so first pbft tender mint and Casper Fuji<00:00:47.800> and<00:00:47.920> Shiva<00:00:48.280> are<00:00:48.670> all<00:00:49.260> categorized<00:00:50.260> into 00:00:50.669 --> 00:00:50.679 align:start position:0% Fuji and Shiva are all categorized into 00:00:50.679 --> 00:00:53.099 align:start position:0% Fuji and Shiva are all categorized into a<00:00:51.070> synchronous<00:00:51.760> resaved<00:00:52.179> consensus<00:00:52.690> protocol 00:00:53.099 --> 00:00:53.109 align:start position:0% a synchronous resaved consensus protocol 00:00:53.109 --> 00:00:56.069 align:start position:0% a synchronous resaved consensus protocol so<00:00:53.920> I<00:00:53.949> mean<00:00:54.219> safety<00:00:55.030> does<00:00:55.179> not<00:00:55.329> require<00:00:55.780> any 00:00:56.069 --> 00:00:56.079 align:start position:0% so I mean safety does not require any 00:00:56.079 --> 00:01:00.840 align:start position:0% so I mean safety does not require any timing<00:00:56.670> assumptions<00:00:58.050> so<00:00:59.219> basically<00:01:00.219> in<00:01:00.550> these 00:01:00.840 --> 00:01:00.850 align:start position:0% timing assumptions so basically in these 00:01:00.850 --> 00:01:04.439 align:start position:0% timing assumptions so basically in these protocols<00:01:01.499> minority<00:01:02.499> comes<00:01:02.829> when<00:01:03.449> sufficient 00:01:04.439 --> 00:01:04.449 align:start position:0% protocols minority comes when sufficient 00:01:04.449 --> 00:01:06.510 align:start position:0% protocols minority comes when sufficient number<00:01:05.110> of<00:01:05.140> our<00:01:05.290> data's<00:01:05.680> is<00:01:05.890> locked<00:01:06.250> on<00:01:06.430> a 00:01:06.510 --> 00:01:06.520 align:start position:0% number of our data's is locked on a 00:01:06.520 --> 00:01:10.920 align:start position:0% number of our data's is locked on a block<00:01:08.880> so<00:01:09.880> let's<00:01:10.210> start<00:01:10.450> with<00:01:10.570> his<00:01:10.690> tender 00:01:10.920 --> 00:01:10.930 align:start position:0% block so let's start with his tender 00:01:10.930 --> 00:01:15.810 align:start position:0% block so let's start with his tender meat<00:01:11.140> so<00:01:12.100> in<00:01:12.370> tandem<00:01:12.700> int<00:01:13.680> a<00:01:14.680> Brock<00:01:15.280> is<00:01:15.490> called 00:01:15.810 --> 00:01:15.820 align:start position:0% meat so in tandem int a Brock is called 00:01:15.820 --> 00:01:19.560 align:start position:0% meat so in tandem int a Brock is called notarized<00:01:16.450> when<00:01:17.110> to<00:01:17.440> F<00:01:17.650> plus<00:01:17.890> one<00:01:18.570> birthday 00:01:19.560 --> 00:01:19.570 align:start position:0% notarized when to F plus one birthday 00:01:19.570 --> 00:01:22.350 align:start position:0% notarized when to F plus one birthday that<00:01:19.840> is<00:01:19.870> brought<00:01:20.170> on<00:01:20.350> the<00:01:20.440> block<00:01:20.620> so<00:01:21.180> here<00:01:22.180> F 00:01:22.350 --> 00:01:22.360 align:start position:0% that is brought on the block so here F 00:01:22.360 --> 00:01:25.560 align:start position:0% that is brought on the block so here F is<00:01:22.570> with<00:01:22.780> an<00:01:22.930> chain<00:01:23.170> for<00:01:23.650> treasure<00:01:24.040> and<00:01:24.570> the 00:01:25.560 --> 00:01:25.570 align:start position:0% is with an chain for treasure and the 00:01:25.570 --> 00:01:28.230 align:start position:0% is with an chain for treasure and the Brock<00:01:25.810> is<00:01:26.140> finalized<00:01:26.920> when<00:01:27.550> it's<00:01:27.760> directed 00:01:28.230 --> 00:01:28.240 align:start position:0% Brock is finalized when it's directed 00:01:28.240 --> 00:01:31.830 align:start position:0% Brock is finalized when it's directed child<00:01:28.480> Brock<00:01:28.780> is<00:01:29.080> notarized<00:01:29.620> and<00:01:30.690> then<00:01:31.690> when 00:01:31.830 --> 00:01:31.840 align:start position:0% child Brock is notarized and then when 00:01:31.840 --> 00:01:34.830 align:start position:0% child Brock is notarized and then when birth<00:01:32.080> data<00:01:32.290> its<00:01:32.860> bottle<00:01:33.370> for<00:01:33.880> notarized 00:01:34.830 --> 00:01:34.840 align:start position:0% birth data its bottle for notarized 00:01:34.840 --> 00:01:37.410 align:start position:0% birth data its bottle for notarized block<00:01:35.140> that<00:01:35.920> VAR<00:01:36.220> data<00:01:36.370> is<00:01:36.640> locked<00:01:36.910> on<00:01:37.150> a<00:01:37.180> Brock 00:01:37.410 --> 00:01:37.420 align:start position:0% block that VAR data is locked on a Brock 00:01:37.420 --> 00:01:40.590 align:start position:0% block that VAR data is locked on a Brock so<00:01:38.380> he<00:01:38.590> cannot<00:01:38.860> vote<00:01:39.760> for<00:01:39.820> a<00:01:40.090> conflicting 00:01:40.590 --> 00:01:40.600 align:start position:0% so he cannot vote for a conflicting 00:01:40.600 --> 00:01:44.400 align:start position:0% so he cannot vote for a conflicting Brock<00:01:40.890> so<00:01:41.890> in<00:01:42.010> this<00:01:42.100> case<00:01:42.690> the<00:01:43.690> past<00:01:43.960> Brock<00:01:44.200> is 00:01:44.400 --> 00:01:44.410 align:start position:0% Brock so in this case the past Brock is 00:01:44.410 --> 00:01:51.330 align:start position:0% Brock so in this case the past Brock is finalized<00:01:46.350> and<00:01:47.970> here<00:01:49.290> the<00:01:50.290> boards<00:01:50.740> must<00:01:51.070> be 00:01:51.330 --> 00:01:51.340 align:start position:0% finalized and here the boards must be 00:01:51.340 --> 00:01:53.400 align:start position:0% finalized and here the boards must be collected<00:01:51.640> in<00:01:52.120> own<00:01:52.420> chain<00:01:52.720> this<00:01:53.020> is<00:01:53.170> very 00:01:53.400 --> 00:01:53.410 align:start position:0% collected in own chain this is very 00:01:53.410 --> 00:01:57.660 align:start position:0% collected in own chain this is very important<00:01:53.860> point<00:01:54.010> so<00:01:55.050> here<00:01:56.280> the<00:01:57.280> reason<00:01:57.430> why 00:01:57.660 --> 00:01:57.670 align:start position:0% important point so here the reason why 00:01:57.670 --> 00:02:00.090 align:start position:0% important point so here the reason why we<00:01:57.970> can<00:01:58.120> say<00:01:58.330> the<00:01:58.870> post<00:01:59.110> Brock<00:01:59.380> is<00:01:59.560> finalized 00:02:00.090 --> 00:02:00.100 align:start position:0% we can say the post Brock is finalized 00:02:00.100 --> 00:02:05.180 align:start position:0% we can say the post Brock is finalized is<00:02:00.370> we<00:02:01.180> know<00:02:01.420> that<00:02:02.170> these<00:02:03.070> validated<00:02:03.790> vote<00:02:04.420> for 00:02:05.180 --> 00:02:05.190 align:start position:0% is we know that these validated vote for 00:02:05.190 --> 00:02:09.749 align:start position:0% is we know that these validated vote for the<00:02:06.190> second<00:02:06.490> Brock<00:02:06.730> knows<00:02:08.160> we<00:02:09.160> know<00:02:09.340> that<00:02:09.550> this 00:02:09.749 --> 00:02:09.759 align:start position:0% the second Brock knows we know that this 00:02:09.759 --> 00:02:11.550 align:start position:0% the second Brock knows we know that this value<00:02:09.970> tie<00:02:10.239> is<00:02:10.300> locked<00:02:10.599> because<00:02:11.110> we<00:02:11.379> know<00:02:11.530> that 00:02:11.550 --> 00:02:11.560 align:start position:0% value tie is locked because we know that 00:02:11.560 --> 00:02:14.460 align:start position:0% value tie is locked because we know that the<00:02:11.950> posts<00:02:12.250> are<00:02:12.400> on<00:02:12.550> chain<00:02:12.820> right<00:02:13.420> this<00:02:14.200> is<00:02:14.290> why 00:02:14.460 --> 00:02:14.470 align:start position:0% the posts are on chain right this is why 00:02:14.470 --> 00:02:16.470 align:start position:0% the posts are on chain right this is why on<00:02:14.800> sham<00:02:15.220> voting<00:02:15.490> is<00:02:15.610> very<00:02:15.670> important<00:02:16.270> for 00:02:16.470 --> 00:02:16.480 align:start position:0% on sham voting is very important for 00:02:16.480 --> 00:02:17.100 align:start position:0% on sham voting is very important for this<00:02:16.690> bro 00:02:17.100 --> 00:02:17.110 align:start position:0% this bro 00:02:17.110 --> 00:02:17.410 align:start position:0% this bro what 00:02:17.410 --> 00:02:17.420 align:start position:0% what 00:02:17.420 --> 00:02:24.220 align:start position:0% what it's<00:02:17.540> protocols<00:02:21.520> the<00:02:22.520> reason<00:02:22.760> why<00:02:23.230> minority 00:02:24.220 --> 00:02:24.230 align:start position:0% it's protocols the reason why minority 00:02:24.230 --> 00:02:27.220 align:start position:0% it's protocols the reason why minority comes<00:02:24.560> around<00:02:24.860> only<00:02:25.670> when<00:02:25.880> it's<00:02:26.569> direct<00:02:26.930> Brock 00:02:27.220 --> 00:02:27.230 align:start position:0% comes around only when it's direct Brock 00:02:27.230 --> 00:02:30.540 align:start position:0% comes around only when it's direct Brock it's<00:02:27.560> it's<00:02:28.099> notarized<00:02:28.720> there<00:02:29.720> might<00:02:29.870> be<00:02:29.900> some 00:02:30.540 --> 00:02:30.550 align:start position:0% it's it's notarized there might be some 00:02:30.550 --> 00:02:39.190 align:start position:0% it's it's notarized there might be some another<00:02:31.550> drop<00:02:31.819> in<00:02:32.000> the<00:02:32.090> middle<00:02:36.100> and<00:02:38.080> you<00:02:39.080> know 00:02:39.190 --> 00:02:39.200 align:start position:0% another drop in the middle and you know 00:02:39.200 --> 00:02:41.650 align:start position:0% another drop in the middle and you know we<00:02:39.500> discussed<00:02:39.709> locking<00:02:40.520> is<00:02:40.760> necessary<00:02:41.540> for 00:02:41.650 --> 00:02:41.660 align:start position:0% we discussed locking is necessary for 00:02:41.660 --> 00:02:44.320 align:start position:0% we discussed locking is necessary for safety<00:02:41.840> but<00:02:42.770> you<00:02:42.980> know<00:02:43.160> if<00:02:43.580> locking<00:02:44.060> is<00:02:44.150> too 00:02:44.320 --> 00:02:44.330 align:start position:0% safety but you know if locking is too 00:02:44.330 --> 00:02:47.440 align:start position:0% safety but you know if locking is too much<00:02:44.510> too<00:02:45.050> much<00:02:45.140> strong<00:02:45.440> does<00:02:46.250> not<00:02:46.450> create 00:02:47.440 --> 00:02:47.450 align:start position:0% much too much strong does not create 00:02:47.450 --> 00:02:50.080 align:start position:0% much too much strong does not create some<00:02:47.660> liveness<00:02:48.019> property<00:02:48.230> so<00:02:49.220> here<00:02:49.610> we<00:02:49.819> have 00:02:50.080 --> 00:02:50.090 align:start position:0% some liveness property so here we have 00:02:50.090 --> 00:02:52.690 align:start position:0% some liveness property so here we have some<00:02:50.390> unlocking<00:02:50.959> condition<00:02:51.410> so<00:02:52.130> in<00:02:52.310> tandem 00:02:52.690 --> 00:02:52.700 align:start position:0% some unlocking condition so in tandem 00:02:52.700 --> 00:02:55.930 align:start position:0% some unlocking condition so in tandem ain't<00:02:52.880> a<00:02:53.590> validator<00:02:54.590> locked<00:02:55.190> on<00:02:55.370> the<00:02:55.459> brock<00:02:55.670> is 00:02:55.930 --> 00:02:55.940 align:start position:0% ain't a validator locked on the brock is 00:02:55.940 --> 00:03:00.370 align:start position:0% ain't a validator locked on the brock is unlocked<00:02:56.660> when<00:02:57.500> he<00:02:58.190> see<00:02:58.459> a<00:02:58.730> higher<00:02:59.380> notarized 00:03:00.370 --> 00:03:00.380 align:start position:0% unlocked when he see a higher notarized 00:03:00.380 --> 00:03:03.520 align:start position:0% unlocked when he see a higher notarized Brock<00:03:00.680> so<00:03:01.340> in<00:03:01.400> his<00:03:01.459> picture<00:03:01.880> I<00:03:02.200> was<00:03:03.200> taught<00:03:03.500> to 00:03:03.520 --> 00:03:03.530 align:start position:0% Brock so in his picture I was taught to 00:03:03.530 --> 00:03:07.420 align:start position:0% Brock so in his picture I was taught to but<00:03:04.489> I'm<00:03:04.870> unlocked<00:03:05.870> because<00:03:06.440> I<00:03:06.680> see<00:03:06.890> that<00:03:07.100> new 00:03:07.420 --> 00:03:07.430 align:start position:0% but I'm unlocked because I see that new 00:03:07.430 --> 00:03:13.509 align:start position:0% but I'm unlocked because I see that new notarized<00:03:07.910> abroad<00:03:08.150> clear<00:03:11.950> so<00:03:12.950> let's<00:03:13.280> start 00:03:13.509 --> 00:03:13.519 align:start position:0% notarized abroad clear so let's start 00:03:13.519 --> 00:03:15.850 align:start position:0% notarized abroad clear so let's start with<00:03:13.670> the<00:03:14.420> next<00:03:14.600> is<00:03:14.870> Casper<00:03:15.170> a<00:03:15.200> refugee<00:03:15.590> the 00:03:15.850 --> 00:03:15.860 align:start position:0% with the next is Casper a refugee the 00:03:15.860 --> 00:03:18.610 align:start position:0% with the next is Casper a refugee the cash<00:03:16.850> point<00:03:17.000> of<00:03:17.150> G<00:03:17.390> is<00:03:17.660> fundamentally<00:03:18.410> similar 00:03:18.610 --> 00:03:18.620 align:start position:0% cash point of G is fundamentally similar 00:03:18.620 --> 00:03:20.949 align:start position:0% cash point of G is fundamentally similar to<00:03:18.830> tandem<00:03:19.130> it<00:03:19.250> but<00:03:19.730> it's<00:03:19.940> more<00:03:20.180> like<00:03:20.360> chain 00:03:20.949 --> 00:03:20.959 align:start position:0% to tandem it but it's more like chain 00:03:20.959 --> 00:03:25.990 align:start position:0% to tandem it but it's more like chain based<00:03:21.290> leader<00:03:22.010> s<00:03:22.310> tandem<00:03:22.820> it<00:03:23.140> so<00:03:24.640> in<00:03:25.640> Casper 00:03:25.990 --> 00:03:26.000 align:start position:0% based leader s tandem it so in Casper 00:03:26.000 --> 00:03:28.090 align:start position:0% based leader s tandem it so in Casper refugee<00:03:26.420> we<00:03:26.810> don't<00:03:27.019> use<00:03:27.230> not<00:03:27.440> finalized<00:03:27.859> block 00:03:28.090 --> 00:03:28.100 align:start position:0% refugee we don't use not finalized block 00:03:28.100 --> 00:03:31.090 align:start position:0% refugee we don't use not finalized block we<00:03:28.640> finalize<00:03:29.120> checkpoints<00:03:29.989> so<00:03:30.920> in<00:03:31.040> this 00:03:31.090 --> 00:03:31.100 align:start position:0% we finalize checkpoints so in this 00:03:31.100 --> 00:03:33.550 align:start position:0% we finalize checkpoints so in this picture<00:03:31.280> we<00:03:31.880> have<00:03:31.910> Brock<00:03:32.390> chained<00:03:32.630> but<00:03:33.410> we 00:03:33.550 --> 00:03:33.560 align:start position:0% picture we have Brock chained but we 00:03:33.560 --> 00:03:37.060 align:start position:0% picture we have Brock chained but we finalized<00:03:34.070> on<00:03:34.570> say<00:03:35.570> every<00:03:36.290> 50<00:03:36.650> blocks<00:03:36.859> or 00:03:37.060 --> 00:03:37.070 align:start position:0% finalized on say every 50 blocks or 00:03:37.070 --> 00:03:41.789 align:start position:0% finalized on say every 50 blocks or every<00:03:37.670> fifty<00:03:38.000> strötzbach<00:03:38.299> right<00:03:38.959> so<00:03:40.000> yeah<00:03:41.030> and 00:03:41.789 --> 00:03:41.799 align:start position:0% every fifty strötzbach right so yeah and 00:03:41.799 --> 00:03:46.840 align:start position:0% every fifty strötzbach right so yeah and again<00:03:42.799> foods<00:03:43.489> a<00:03:43.730> steer<00:03:44.060> on<00:03:44.209> chain<00:03:45.850> the 00:03:46.840 --> 00:03:46.850 align:start position:0% again foods a steer on chain the 00:03:46.850 --> 00:03:49.960 align:start position:0% again foods a steer on chain the difference<00:03:47.239> between<00:03:47.359> tandem<00:03:48.230> it<00:03:48.350> is<00:03:48.640> the<00:03:49.640> fork 00:03:49.960 --> 00:03:49.970 align:start position:0% difference between tandem it is the fork 00:03:49.970 --> 00:03:52.780 align:start position:0% difference between tandem it is the fork choice<00:03:50.209> itself<00:03:50.660> is<00:03:51.070> doing<00:03:52.070> the<00:03:52.250> similar<00:03:52.459> role 00:03:52.780 --> 00:03:52.790 align:start position:0% choice itself is doing the similar role 00:03:52.790 --> 00:03:56.770 align:start position:0% choice itself is doing the similar role of<00:03:53.120> leader<00:03:53.720> so<00:03:54.560> in<00:03:54.709> tandem<00:03:55.040> ain't<00:03:55.780> everybody 00:03:56.770 --> 00:03:56.780 align:start position:0% of leader so in tandem ain't everybody 00:03:56.780 --> 00:03:59.500 align:start position:0% of leader so in tandem ain't everybody that<00:03:56.959> bought<00:03:57.380> for<00:03:57.680> Brock<00:03:57.980> which<00:03:58.940> decided<00:03:59.390> to 00:03:59.500 --> 00:03:59.510 align:start position:0% that bought for Brock which decided to 00:03:59.510 --> 00:04:01.630 align:start position:0% that bought for Brock which decided to buy<00:03:59.630> the<00:03:59.690> leader<00:03:59.989> of<00:04:00.260> that<00:04:00.500> round<00:04:00.739> but<00:04:01.489> in 00:04:01.630 --> 00:04:01.640 align:start position:0% buy the leader of that round but in 00:04:01.640 --> 00:04:05.550 align:start position:0% buy the leader of that round but in class<00:04:01.880> by<00:04:02.030> 50<00:04:02.239> G<00:04:02.420> it's<00:04:03.049> a<00:04:03.260> folk<00:04:03.500> choice<00:04:03.739> that 00:04:05.550 --> 00:04:05.560 align:start position:0% class by 50 G it's a folk choice that 00:04:05.560 --> 00:04:11.500 align:start position:0% class by 50 G it's a folk choice that decides<00:04:06.560> of<00:04:06.709> you<00:04:08.290> and<00:04:10.150> unlocking<00:04:11.150> and<00:04:11.359> locking 00:04:11.500 --> 00:04:11.510 align:start position:0% decides of you and unlocking and locking 00:04:11.510 --> 00:04:13.720 align:start position:0% decides of you and unlocking and locking it's<00:04:11.989> super<00:04:12.290> similar<00:04:12.530> to<00:04:12.650> tender<00:04:12.920> meat<00:04:13.069> so<00:04:13.579> in 00:04:13.720 --> 00:04:13.730 align:start position:0% it's super similar to tender meat so in 00:04:13.730 --> 00:04:17.529 align:start position:0% it's super similar to tender meat so in every<00:04:14.329> case<00:04:14.650> they<00:04:15.650> are<00:04:15.889> unlocked<00:04:16.400> when<00:04:17.299> they 00:04:17.529 --> 00:04:17.539 align:start position:0% every case they are unlocked when they 00:04:17.539 --> 00:04:21.159 align:start position:0% every case they are unlocked when they see<00:04:17.600> higher<00:04:19.090> notarized<00:04:20.090> what<00:04:20.450> just<00:04:20.690> justify 00:04:21.159 --> 00:04:21.169 align:start position:0% see higher notarized what just justify 00:04:21.169 --> 00:04:26.290 align:start position:0% see higher notarized what just justify the<00:04:21.229> checkpoint 00:04:26.290 --> 00:04:26.300 align:start position:0% 00:04:26.300 --> 00:04:30.680 align:start position:0% so<00:04:27.300> finally<00:04:27.780> she<00:04:27.990> Misha<00:04:28.890> Casper<00:04:29.280> is<00:04:29.690> also 00:04:30.680 --> 00:04:30.690 align:start position:0% so finally she Misha Casper is also 00:04:30.690 --> 00:04:33.500 align:start position:0% so finally she Misha Casper is also locking<00:04:31.050> abased<00:04:31.320> consider<00:04:32.010> protocol<00:04:32.430> but<00:04:33.330> the 00:04:33.500 --> 00:04:33.510 align:start position:0% locking abased consider protocol but the 00:04:33.510 --> 00:04:35.720 align:start position:0% locking abased consider protocol but the log<00:04:33.720> king<00:04:33.990> and<00:04:34.200> the<00:04:34.410> unlocking<00:04:34.860> is<00:04:35.130> purely<00:04:35.490> by 00:04:35.720 --> 00:04:35.730 align:start position:0% log king and the unlocking is purely by 00:04:35.730 --> 00:04:40.700 align:start position:0% log king and the unlocking is purely by the<00:04:35.790> fortress<00:04:36.300> itself<00:04:37.190> so<00:04:38.990> in<00:04:39.990> shabby<00:04:40.410> chic<00:04:40.530> as 00:04:40.700 --> 00:04:40.710 align:start position:0% the fortress itself so in shabby chic as 00:04:40.710 --> 00:04:44.330 align:start position:0% the fortress itself so in shabby chic as per<00:04:40.890> every<00:04:41.670> message<00:04:42.330> boats<00:04:42.750> rock<00:04:43.200> must<00:04:43.980> follow 00:04:44.330 --> 00:04:44.340 align:start position:0% per every message boats rock must follow 00:04:44.340 --> 00:04:49.430 align:start position:0% per every message boats rock must follow the<00:04:45.240> folk<00:04:45.450> choice<00:04:45.690> and<00:04:46.650> in<00:04:47.640> tandem<00:04:48.360> int<00:04:48.660> or<00:04:48.900> FFG 00:04:49.430 --> 00:04:49.440 align:start position:0% the folk choice and in tandem int or FFG 00:04:49.440 --> 00:04:52.460 align:start position:0% the folk choice and in tandem int or FFG we<00:04:50.070> included<00:04:50.610> supports<00:04:51.090> on<00:04:51.270> chain<00:04:51.600> but<00:04:52.260> in 00:04:52.460 --> 00:04:52.470 align:start position:0% we included supports on chain but in 00:04:52.470 --> 00:04:56.780 align:start position:0% we included supports on chain but in Shiva<00:04:53.340> she<00:04:53.630> weeken<00:04:54.630> the<00:04:54.930> same<00:04:55.110> thing<00:04:55.380> but<00:04:56.190> more 00:04:56.780 --> 00:04:56.790 align:start position:0% Shiva she weeken the same thing but more 00:04:56.790 --> 00:05:00.050 align:start position:0% Shiva she weeken the same thing but more for<00:04:57.000> x-ray<00:04:57.360> we<00:04:58.050> can<00:04:58.290> allow<00:04:59.100> the<00:04:59.160> message<00:04:59.760> to 00:05:00.050 --> 00:05:00.060 align:start position:0% for x-ray we can allow the message to 00:05:00.060 --> 00:05:02.480 align:start position:0% for x-ray we can allow the message to point<00:05:00.480> to<00:05:00.720> the<00:05:00.810> every<00:05:01.200> all<00:05:01.440> front<00:05:01.800> boats<00:05:02.040> were 00:05:02.480 --> 00:05:02.490 align:start position:0% point to the every all front boats were 00:05:02.490 --> 00:05:06.500 align:start position:0% point to the every all front boats were broke<00:05:02.790> so<00:05:03.690> in<00:05:03.810> this<00:05:03.900> picture<00:05:04.760> the<00:05:05.760> block<00:05:05.970> P<00:05:06.240> is 00:05:06.500 --> 00:05:06.510 align:start position:0% broke so in this picture the block P is 00:05:06.510 --> 00:05:12.470 align:start position:0% broke so in this picture the block P is pointing<00:05:07.050> to<00:05:07.200> open<00:05:07.620> block<00:05:08.030> but<00:05:11.090> the<00:05:12.090> reason<00:05:12.330> is 00:05:12.470 --> 00:05:12.480 align:start position:0% pointing to open block but the reason is 00:05:12.480 --> 00:05:23.930 align:start position:0% pointing to open block but the reason is um<00:05:14.210> okay<00:05:15.210> so<00:05:20.630> yeah<00:05:22.370> additional<00:05:23.370> explanation 00:05:23.930 --> 00:05:23.940 align:start position:0% um okay so yeah additional explanation 00:05:23.940 --> 00:05:26.810 align:start position:0% um okay so yeah additional explanation so<00:05:24.420> in<00:05:24.720> this<00:05:24.840> case<00:05:25.110> this<00:05:25.830> proc<00:05:26.250> is<00:05:26.400> invalid 00:05:26.810 --> 00:05:26.820 align:start position:0% so in this case this proc is invalid 00:05:26.820 --> 00:05:29.210 align:start position:0% so in this case this proc is invalid because<00:05:27.270> they<00:05:27.600> know<00:05:27.780> that<00:05:27.810> the<00:05:28.770> different 00:05:29.210 --> 00:05:29.220 align:start position:0% because they know that the different 00:05:29.220 --> 00:05:31.850 align:start position:0% because they know that the different chain<00:05:29.460> is<00:05:29.700> more<00:05:29.970> heavier<00:05:30.590> so<00:05:31.590> this<00:05:31.740> is 00:05:31.850 --> 00:05:31.860 align:start position:0% chain is more heavier so this is 00:05:31.860 --> 00:05:35.600 align:start position:0% chain is more heavier so this is inverted<00:05:32.250> and<00:05:34.040> unlocking<00:05:35.040> condition<00:05:35.460> it's 00:05:35.600 --> 00:05:35.610 align:start position:0% inverted and unlocking condition it's 00:05:35.610 --> 00:05:37.880 align:start position:0% inverted and unlocking condition it's super<00:05:35.940> obstructed<00:05:36.450> into<00:05:36.890> equivocation 00:05:37.880 --> 00:05:37.890 align:start position:0% super obstructed into equivocation 00:05:37.890 --> 00:05:41.510 align:start position:0% super obstructed into equivocation condition<00:05:38.280> that<00:05:39.290> every<00:05:40.290> vote<00:05:40.590> must<00:05:41.070> include 00:05:41.510 --> 00:05:41.520 align:start position:0% condition that every vote must include 00:05:41.520 --> 00:05:44.720 align:start position:0% condition that every vote must include is<00:05:42.150> the<00:05:42.210> previous<00:05:42.630> message<00:05:43.110> in<00:05:43.770> its<00:05:44.250> message 00:05:44.720 --> 00:05:44.730 align:start position:0% is the previous message in its message 00:05:44.730 --> 00:05:48.020 align:start position:0% is the previous message in its message so<00:05:45.540> in<00:05:45.660> this<00:05:45.720> picture<00:05:45.900> this<00:05:46.620> block<00:05:46.950> is<00:05:47.190> invalid 00:05:48.020 --> 00:05:48.030 align:start position:0% so in this picture this block is invalid 00:05:48.030 --> 00:05:50.930 align:start position:0% so in this picture this block is invalid because<00:05:48.600> he<00:05:48.930> has<00:05:49.140> previous<00:05:49.740> message<00:05:50.040> here<00:05:50.370> but 00:05:50.930 --> 00:05:50.940 align:start position:0% because he has previous message here but 00:05:50.940 --> 00:05:56.750 align:start position:0% because he has previous message here but is<00:05:51.060> not<00:05:51.210> including<00:05:51.750> on<00:05:51.870> chain<00:05:52.080> in<00:05:52.680> message<00:05:55.760> so 00:05:56.750 --> 00:05:56.760 align:start position:0% is not including on chain in message so 00:05:56.760 --> 00:05:59.660 align:start position:0% is not including on chain in message so the<00:05:57.270> similarity<00:05:57.840> of<00:05:57.870> she<00:05:58.380> be<00:05:58.500> she<00:05:58.680> and<00:05:58.890> FFG<00:05:59.400> is 00:05:59.660 --> 00:05:59.670 align:start position:0% the similarity of she be she and FFG is 00:05:59.670 --> 00:06:02.540 align:start position:0% the similarity of she be she and FFG is that<00:06:00.150> the<00:06:00.210> boss<00:06:00.420> is<00:06:00.690> chain<00:06:01.050> based<00:06:01.350> so<00:06:02.160> every 00:06:02.540 --> 00:06:02.550 align:start position:0% that the boss is chain based so every 00:06:02.550 --> 00:06:06.620 align:start position:0% that the boss is chain based so every vote<00:06:02.820> Brock<00:06:03.540> is<00:06:04.460> voting<00:06:05.460> was<00:06:05.790> supporting<00:06:06.300> for 00:06:06.620 --> 00:06:06.630 align:start position:0% vote Brock is voting was supporting for 00:06:06.630 --> 00:06:09.770 align:start position:0% vote Brock is voting was supporting for the<00:06:06.720> same<00:06:06.990> ancestor<00:06:08.600> right 00:06:09.770 --> 00:06:09.780 align:start position:0% the same ancestor right 00:06:09.780 --> 00:06:14.420 align:start position:0% the same ancestor right so<00:06:10.170> in<00:06:10.380> FFG<00:06:10.920> what<00:06:11.250> 2.0<00:06:11.760> they<00:06:12.450> include<00:06:13.080> all<00:06:14.040> from 00:06:14.420 --> 00:06:14.430 align:start position:0% so in FFG what 2.0 they include all from 00:06:14.430 --> 00:06:16.880 align:start position:0% so in FFG what 2.0 they include all from boats<00:06:14.700> in<00:06:15.060> own<00:06:15.420> shame<00:06:15.690> because<00:06:16.470> they<00:06:16.710> are 00:06:16.880 --> 00:06:16.890 align:start position:0% boats in own shame because they are 00:06:16.890 --> 00:06:20.450 align:start position:0% boats in own shame because they are supporting<00:06:17.400> for<00:06:17.580> the<00:06:17.640> same<00:06:17.820> checkpoints<00:06:19.460> this 00:06:20.450 --> 00:06:20.460 align:start position:0% supporting for the same checkpoints this 00:06:20.460 --> 00:06:22.610 align:start position:0% supporting for the same checkpoints this is<00:06:20.580> also<00:06:20.790> same<00:06:21.030> force<00:06:21.300> revision<00:06:21.660> Kasper<00:06:21.960> but 00:06:22.610 --> 00:06:22.620 align:start position:0% is also same force revision Kasper but 00:06:22.620 --> 00:06:30.710 align:start position:0% is also same force revision Kasper but it's<00:06:22.830> more<00:06:23.220> flexible<00:06:23.520> way<00:06:27.620> so<00:06:29.330> exact<00:06:30.330> finality 00:06:30.710 --> 00:06:30.720 align:start position:0% it's more flexible way so exact finality 00:06:30.720 --> 00:06:33.230 align:start position:0% it's more flexible way so exact finality condition<00:06:31.320> is<00:06:31.650> something<00:06:31.980> like<00:06:32.220> I<00:06:32.400> do<00:06:32.520> not<00:06:32.670> do 00:06:33.230 --> 00:06:33.240 align:start position:0% condition is something like I do not do 00:06:33.240 --> 00:06:35.420 align:start position:0% condition is something like I do not do not<00:06:33.390> talk<00:06:33.600> in<00:06:33.840> this<00:06:33.990> talk<00:06:34.200> but<00:06:34.860> we<00:06:35.040> finally 00:06:35.420 --> 00:06:35.430 align:start position:0% not talk in this talk but we finally 00:06:35.430 --> 00:06:37.130 align:start position:0% not talk in this talk but we finally finished<00:06:35.760> our<00:06:36.090> formal<00:06:36.510> education<00:06:36.990> in 00:06:37.130 --> 00:06:37.140 align:start position:0% finished our formal education in 00:06:37.140 --> 00:06:39.310 align:start position:0% finished our formal education in elaboration<00:06:38.030> it 00:06:39.310 --> 00:06:39.320 align:start position:0% elaboration it 00:06:39.320 --> 00:06:41.620 align:start position:0% elaboration it more<00:06:39.590> than<00:06:39.710> half<00:06:39.950> a<00:06:40.070> year<00:06:40.100> but<00:06:40.880> you<00:06:41.300> know<00:06:41.390> it's 00:06:41.620 --> 00:06:41.630 align:start position:0% more than half a year but you know it's 00:06:41.630 --> 00:06:47.020 align:start position:0% more than half a year but you know it's great<00:06:42.350> job<00:06:42.530> I<00:06:42.620> think<00:06:45.520> so<00:06:46.520> yeah<00:06:46.700> pretty<00:06:46.910> much 00:06:47.020 --> 00:06:47.030 align:start position:0% great job I think so yeah pretty much 00:06:47.030 --> 00:06:49.210 align:start position:0% great job I think so yeah pretty much summary<00:06:47.480> is<00:06:47.690> ten<00:06:48.110> demand<00:06:48.410> cashback<00:06:48.860> refugee 00:06:49.210 --> 00:06:49.220 align:start position:0% summary is ten demand cashback refugee 00:06:49.220 --> 00:06:51.700 align:start position:0% summary is ten demand cashback refugee and<00:06:49.400> ceviche<00:06:49.730> is<00:06:50.090> based<00:06:50.360> basically<00:06:50.930> based<00:06:51.530> on 00:06:51.700 --> 00:06:51.710 align:start position:0% and ceviche is based basically based on 00:06:51.710 --> 00:06:55.540 align:start position:0% and ceviche is based basically based on some<00:06:51.890> locking<00:06:52.270> idea<00:06:53.270> and<00:06:54.340> you<00:06:55.340> know<00:06:55.400> the 00:06:55.540 --> 00:06:55.550 align:start position:0% some locking idea and you know the 00:06:55.550 --> 00:06:57.790 align:start position:0% some locking idea and you know the difference<00:06:55.880> comes<00:06:56.090> from<00:06:56.360> where<00:06:56.930> the<00:06:57.050> locking 00:06:57.790 --> 00:06:57.800 align:start position:0% difference comes from where the locking 00:06:57.800 --> 00:07:00.220 align:start position:0% difference comes from where the locking is<00:06:57.980> based<00:06:58.190> on<00:06:58.370> the<00:06:58.640> notarized<00:06:59.180> checkpoint<00:07:00.080> of 00:07:00.220 --> 00:07:00.230 align:start position:0% is based on the notarized checkpoint of 00:07:00.230 --> 00:07:06.670 align:start position:0% is based on the notarized checkpoint of rock<00:07:00.470> or<00:07:00.940> folk<00:07:01.940> choice<00:07:02.180> itself<00:07:04.780> so<00:07:05.780> to<00:07:06.320> me<00:07:06.500> I 00:07:06.670 --> 00:07:06.680 align:start position:0% rock or folk choice itself so to me I 00:07:06.680 --> 00:07:10.360 align:start position:0% rock or folk choice itself so to me I want<00:07:06.890> to<00:07:06.950> move<00:07:07.160> to<00:07:07.190> ravenous<00:07:07.970> but<00:07:09.370> ravenous 00:07:10.360 --> 00:07:10.370 align:start position:0% want to move to ravenous but ravenous 00:07:10.370 --> 00:07:13.000 align:start position:0% want to move to ravenous but ravenous has<00:07:10.940> a<00:07:11.270> lot<00:07:11.480> of<00:07:11.540> design<00:07:11.840> strategies<00:07:12.350> so<00:07:12.920> I<00:07:12.950> do 00:07:13.000 --> 00:07:13.010 align:start position:0% has a lot of design strategies so I do 00:07:13.010 --> 00:07:15.940 align:start position:0% has a lot of design strategies so I do not<00:07:13.190> cannot<00:07:13.670> talk<00:07:13.970> in<00:07:14.270> this<00:07:14.510> 20<00:07:15.110> minutes<00:07:15.380> so 00:07:15.940 --> 00:07:15.950 align:start position:0% not cannot talk in this 20 minutes so 00:07:15.950 --> 00:07:18.730 align:start position:0% not cannot talk in this 20 minutes so today<00:07:16.280> I<00:07:16.340> want<00:07:16.610> to<00:07:16.700> focus<00:07:16.730> on<00:07:17.120> 2.0<00:07:17.630> ravenous<00:07:18.020> so 00:07:18.730 --> 00:07:18.740 align:start position:0% today I want to focus on 2.0 ravenous so 00:07:18.740 --> 00:07:21.610 align:start position:0% today I want to focus on 2.0 ravenous so basically<00:07:19.160> in<00:07:19.580> 2.0<00:07:20.150> Lebanon<00:07:21.020> strategy<00:07:21.470> is 00:07:21.610 --> 00:07:21.620 align:start position:0% basically in 2.0 Lebanon strategy is 00:07:21.620 --> 00:07:24.490 align:start position:0% basically in 2.0 Lebanon strategy is super<00:07:21.980> simple<00:07:22.130> it's<00:07:23.030> just<00:07:23.300> a<00:07:23.540> remedy<00:07:24.200> ghost 00:07:24.490 --> 00:07:24.500 align:start position:0% super simple it's just a remedy ghost 00:07:24.500 --> 00:07:30.250 align:start position:0% super simple it's just a remedy ghost press<00:07:25.040> just<00:07:25.490> by<00:07:25.610> refugee<00:07:27.850> so<00:07:28.850> remedy<00:07:29.810> ghost<00:07:29.990> is 00:07:30.250 --> 00:07:30.260 align:start position:0% press just by refugee so remedy ghost is 00:07:30.260 --> 00:07:34.000 align:start position:0% press just by refugee so remedy ghost is a<00:07:31.060> variant<00:07:32.060> of<00:07:32.150> ghost<00:07:32.480> in<00:07:32.810> which<00:07:33.440> where<00:07:33.740> the 00:07:34.000 --> 00:07:34.010 align:start position:0% a variant of ghost in which where the 00:07:34.010 --> 00:07:36.250 align:start position:0% a variant of ghost in which where the latest<00:07:34.310> message<00:07:34.880> is<00:07:35.150> only<00:07:35.480> counted<00:07:35.870> so<00:07:36.140> in 00:07:36.250 --> 00:07:36.260 align:start position:0% latest message is only counted so in 00:07:36.260 --> 00:07:39.160 align:start position:0% latest message is only counted so in this<00:07:36.380> picture<00:07:37.000> the<00:07:38.000> traditional<00:07:38.810> longest 00:07:39.160 --> 00:07:39.170 align:start position:0% this picture the traditional longest 00:07:39.170 --> 00:07:42.870 align:start position:0% this picture the traditional longest chain<00:07:39.290> rule<00:07:39.500> this<00:07:40.010> chain<00:07:40.610> that<00:07:41.300> is<00:07:41.390> ahead<00:07:41.510> in 00:07:42.870 --> 00:07:42.880 align:start position:0% chain rule this chain that is ahead in 00:07:42.880 --> 00:07:47.590 align:start position:0% chain rule this chain that is ahead in normal<00:07:43.880> ghost<00:07:44.090> this<00:07:45.250> chain<00:07:46.250> is<00:07:46.600> head-butting 00:07:47.590 --> 00:07:47.600 align:start position:0% normal ghost this chain is head-butting 00:07:47.600 --> 00:07:49.720 align:start position:0% normal ghost this chain is head-butting aromatic<00:07:48.020> ghost<00:07:48.200> we<00:07:48.500> only<00:07:48.710> count<00:07:49.130> the<00:07:49.460> latest 00:07:49.720 --> 00:07:49.730 align:start position:0% aromatic ghost we only count the latest 00:07:49.730 --> 00:07:50.110 align:start position:0% aromatic ghost we only count the latest message 00:07:50.110 --> 00:07:50.120 align:start position:0% message 00:07:50.120 --> 00:07:59.020 align:start position:0% message so<00:07:50.510> the<00:07:51.490> the<00:07:52.490> third<00:07:52.700> chain<00:07:53.090> is<00:07:53.360> ahead<00:07:57.970> so<00:07:58.970> to 00:07:59.020 --> 00:07:59.030 align:start position:0% so the the third chain is ahead so to 00:07:59.030 --> 00:08:01.360 align:start position:0% so the the third chain is ahead so to talk<00:07:59.270> about<00:07:59.330> the<00:07:59.570> liveness<00:08:00.050> based<00:08:00.770> on<00:08:00.950> our<00:08:01.130> MD 00:08:01.360 --> 00:08:01.370 align:start position:0% talk about the liveness based on our MD 00:08:01.370 --> 00:08:04.360 align:start position:0% talk about the liveness based on our MD goals<00:08:01.580> we<00:08:01.940> need<00:08:01.970> to<00:08:02.180> define<00:08:02.540> when<00:08:03.350> the<00:08:03.740> chain 00:08:04.360 --> 00:08:04.370 align:start position:0% goals we need to define when the chain 00:08:04.370 --> 00:08:07.810 align:start position:0% goals we need to define when the chain converges<00:08:05.000> and<00:08:05.320> in<00:08:06.320> a<00:08:06.470> remedy<00:08:06.710> ghost<00:08:07.010> a<00:08:07.340> block 00:08:07.810 --> 00:08:07.820 align:start position:0% converges and in a remedy ghost a block 00:08:07.820 --> 00:08:11.470 align:start position:0% converges and in a remedy ghost a block is<00:08:08.120> not<00:08:08.540> opened<00:08:09.110> when<00:08:10.010> the<00:08:10.210> chain<00:08:11.210> is 00:08:11.470 --> 00:08:11.480 align:start position:0% is not opened when the chain is 00:08:11.480 --> 00:08:13.810 align:start position:0% is not opened when the chain is supported<00:08:12.110> by<00:08:12.320> modern<00:08:12.680> majority<00:08:13.340> of<00:08:13.490> honest 00:08:13.810 --> 00:08:13.820 align:start position:0% supported by modern majority of honest 00:08:13.820 --> 00:08:20.700 align:start position:0% supported by modern majority of honest supports<00:08:16.690> so<00:08:17.690> in<00:08:17.780> this<00:08:17.870> example<00:08:18.020> say<00:08:18.950> says<00:08:19.670> 100 00:08:20.700 --> 00:08:20.710 align:start position:0% supports so in this example say says 100 00:08:20.710 --> 00:08:26.500 align:start position:0% supports so in this example say says 100 total<00:08:21.710> bar<00:08:21.950> details<00:08:22.280> and<00:08:23.950> the<00:08:24.950> brew<00:08:25.250> chain<00:08:25.970> is 00:08:26.500 --> 00:08:26.510 align:start position:0% total bar details and the brew chain is 00:08:26.510 --> 00:08:30.580 align:start position:0% total bar details and the brew chain is supported<00:08:26.960> by<00:08:27.140> more<00:08:27.500> than<00:08:27.620> 51<00:08:28.390> votes<00:08:29.390> in<00:08:30.320> this 00:08:30.580 --> 00:08:30.590 align:start position:0% supported by more than 51 votes in this 00:08:30.590 --> 00:08:33.820 align:start position:0% supported by more than 51 votes in this case<00:08:30.860> whatever<00:08:31.520> the<00:08:31.760> what<00:08:32.030> I<00:08:32.060> do<00:08:32.360> the<00:08:33.229> top 00:08:33.820 --> 00:08:33.830 align:start position:0% case whatever the what I do the top 00:08:33.830 --> 00:08:37.990 align:start position:0% case whatever the what I do the top chain<00:08:34.130> does<00:08:34.310> not<00:08:34.520> orbit<00:08:34.940> reorganised<00:08:36.280> so<00:08:37.280> this 00:08:37.990 --> 00:08:38.000 align:start position:0% chain does not orbit reorganised so this 00:08:38.000 --> 00:08:39.790 align:start position:0% chain does not orbit reorganised so this is<00:08:38.120> a<00:08:38.150> convergence<00:08:38.690> condition<00:08:38.900> of<00:08:39.289> aromatic 00:08:39.790 --> 00:08:39.800 align:start position:0% is a convergence condition of aromatic 00:08:39.800 --> 00:08:43.029 align:start position:0% is a convergence condition of aromatic ghost<00:08:39.950> but<00:08:40.700> it<00:08:41.060> cannot<00:08:41.360> be<00:08:41.419> observed<00:08:42.110> by<00:08:42.500> you 00:08:43.029 --> 00:08:43.039 align:start position:0% ghost but it cannot be observed by you 00:08:43.039 --> 00:08:44.560 align:start position:0% ghost but it cannot be observed by you know<00:08:43.130> protocol<00:08:43.729> boring<00:08:44.000> part<00:08:44.150> data's 00:08:44.560 --> 00:08:44.570 align:start position:0% know protocol boring part data's 00:08:44.570 --> 00:08:46.930 align:start position:0% know protocol boring part data's this<00:08:44.720> is<00:08:44.840> why<00:08:45.020> we<00:08:45.200> want<00:08:45.410> Casper<00:08:45.890> to<00:08:46.550> detect 00:08:46.930 --> 00:08:46.940 align:start position:0% this is why we want Casper to detect 00:08:46.940 --> 00:08:49.690 align:start position:0% this is why we want Casper to detect finality<00:08:47.470> but<00:08:48.470> for<00:08:48.680> revenue<00:08:48.950> analysis<00:08:49.370> this 00:08:49.690 --> 00:08:49.700 align:start position:0% finality but for revenue analysis this 00:08:49.700 --> 00:08:54.990 align:start position:0% finality but for revenue analysis this is<00:08:49.880> the<00:08:49.970> convergence<00:08:50.390> condition 00:08:54.990 --> 00:08:55.000 align:start position:0% 00:08:55.000 --> 00:08:56.200 align:start position:0% yeah 00:08:56.200 --> 00:08:56.210 align:start position:0% yeah 00:08:56.210 --> 00:08:59.200 align:start position:0% yeah so<00:08:56.620> before<00:08:57.620> I<00:08:57.650> introduce<00:08:57.970> attack<00:08:58.970> on 00:08:59.200 --> 00:08:59.210 align:start position:0% so before I introduce attack on 00:08:59.210 --> 00:09:02.230 align:start position:0% so before I introduce attack on elementary<00:08:59.630> ghosts<00:08:59.810> I<00:09:00.140> want<00:09:00.740> to<00:09:01.240> introduce 00:09:02.230 --> 00:09:02.240 align:start position:0% elementary ghosts I want to introduce 00:09:02.240 --> 00:09:04.600 align:start position:0% elementary ghosts I want to introduce some<00:09:02.690> very<00:09:03.200> nice<00:09:03.350> property<00:09:03.740> on<00:09:03.950> folk<00:09:04.190> trees 00:09:04.600 --> 00:09:04.610 align:start position:0% some very nice property on folk trees 00:09:04.610 --> 00:09:08.140 align:start position:0% some very nice property on folk trees so<00:09:05.120> in<00:09:05.510> basically<00:09:06.080> in<00:09:06.410> any<00:09:06.950> constant<00:09:07.670> protocol 00:09:08.140 --> 00:09:08.150 align:start position:0% so in basically in any constant protocol 00:09:08.150 --> 00:09:11.560 align:start position:0% so in basically in any constant protocol we<00:09:08.600> want<00:09:08.870> some<00:09:09.140> property<00:09:09.860> called<00:09:10.160> fairness<00:09:10.610> so 00:09:11.560 --> 00:09:11.570 align:start position:0% we want some property called fairness so 00:09:11.570 --> 00:09:14.950 align:start position:0% we want some property called fairness so I<00:09:11.900> mean<00:09:12.230> any<00:09:13.190> player<00:09:13.610> cannot<00:09:14.240> increase<00:09:14.750> the 00:09:14.950 --> 00:09:14.960 align:start position:0% I mean any player cannot increase the 00:09:14.960 --> 00:09:18.990 align:start position:0% I mean any player cannot increase the power<00:09:15.580> against<00:09:16.580> the<00:09:16.730> stake<00:09:17.000> or<00:09:17.300> hash<00:09:17.870> power 00:09:18.990 --> 00:09:19.000 align:start position:0% power against the stake or hash power 00:09:19.000 --> 00:09:22.900 align:start position:0% power against the stake or hash power but<00:09:20.000> the<00:09:20.810> something<00:09:21.260> break<00:09:22.070> this<00:09:22.370> property 00:09:22.900 --> 00:09:22.910 align:start position:0% but the something break this property 00:09:22.910 --> 00:09:28.090 align:start position:0% but the something break this property called<00:09:23.660> saving<00:09:24.110> strategy<00:09:24.560> so<00:09:26.620> the<00:09:27.620> bursary 00:09:28.090 --> 00:09:28.100 align:start position:0% called saving strategy so the bursary 00:09:28.100 --> 00:09:31.510 align:start position:0% called saving strategy so the bursary can<00:09:28.700> skip<00:09:29.030> their<00:09:29.510> votes<00:09:29.720> and<00:09:29.960> the<00:09:30.800> later<00:09:31.010> use 00:09:31.510 --> 00:09:31.520 align:start position:0% can skip their votes and the later use 00:09:31.520 --> 00:09:37.420 align:start position:0% can skip their votes and the later use their<00:09:31.760> votes<00:09:31.940> to<00:09:32.240> free<00:09:32.900> prop<00:09:35.530> this<00:09:36.530> not<00:09:37.040> work 00:09:37.420 --> 00:09:37.430 align:start position:0% their votes to free prop this not work 00:09:37.430 --> 00:09:42.100 align:start position:0% their votes to free prop this not work in<00:09:37.670> the<00:09:37.730> longest<00:09:38.060> chain<00:09:38.500> because<00:09:39.500> so<00:09:40.220> say<00:09:41.110> we 00:09:42.100 --> 00:09:42.110 align:start position:0% in the longest chain because so say we 00:09:42.110 --> 00:09:43.860 align:start position:0% in the longest chain because so say we divided<00:09:42.470> into<00:09:42.770> climbing<00:09:43.280> the<00:09:43.400> slots 00:09:43.860 --> 00:09:43.870 align:start position:0% divided into climbing the slots 00:09:43.870 --> 00:09:46.390 align:start position:0% divided into climbing the slots six-second<00:09:44.870> the<00:09:44.960> ten<00:09:45.110> seconds<00:09:45.440> and<00:09:45.830> every 00:09:46.390 --> 00:09:46.400 align:start position:0% six-second the ten seconds and every 00:09:46.400 --> 00:09:49.630 align:start position:0% six-second the ten seconds and every three<00:09:47.180> block<00:09:47.480> were<00:09:48.080> vote<00:09:48.320> is<00:09:48.620> but<00:09:49.040> otherwise 00:09:49.630 --> 00:09:49.640 align:start position:0% three block were vote is but otherwise 00:09:49.640 --> 00:09:51.630 align:start position:0% three block were vote is but otherwise for<00:09:49.940> the<00:09:50.000> battery<00:09:50.300> and<00:09:50.540> in<00:09:51.200> this<00:09:51.320> case 00:09:51.630 --> 00:09:51.640 align:start position:0% for the battery and in this case 00:09:51.640 --> 00:09:55.330 align:start position:0% for the battery and in this case adversary<00:09:52.640> with<00:09:53.570> horde<00:09:53.960> was<00:09:54.440> save<00:09:54.770> every 00:09:55.330 --> 00:09:55.340 align:start position:0% adversary with horde was save every 00:09:55.340 --> 00:09:59.380 align:start position:0% adversary with horde was save every block<00:09:56.140> but<00:09:57.140> in<00:09:57.320> longest<00:09:57.650> chain<00:09:58.000> we<00:09:59.000> can<00:09:59.180> add 00:09:59.380 --> 00:09:59.390 align:start position:0% block but in longest chain we can add 00:09:59.390 --> 00:10:01.450 align:start position:0% block but in longest chain we can add some<00:09:59.690> validity<00:09:59.900> conditions<00:10:00.620> that<00:10:00.950> every 00:10:01.450 --> 00:10:01.460 align:start position:0% some validity conditions that every 00:10:01.460 --> 00:10:04.090 align:start position:0% some validity conditions that every block<00:10:01.730> wall<00:10:02.150> vote<00:10:02.360> cannot<00:10:03.110> extend<00:10:03.680> the<00:10:03.830> future 00:10:04.090 --> 00:10:04.100 align:start position:0% block wall vote cannot extend the future 00:10:04.100 --> 00:10:08.140 align:start position:0% block wall vote cannot extend the future rock<00:10:04.570> so<00:10:05.570> here<00:10:06.440> after<00:10:06.620> some<00:10:07.340> network<00:10:07.760> failure 00:10:08.140 --> 00:10:08.150 align:start position:0% rock so here after some network failure 00:10:08.150 --> 00:10:11.530 align:start position:0% rock so here after some network failure they<00:10:08.900> cannot<00:10:09.200> use<00:10:09.500> the<00:10:10.070> save<00:10:10.280> the<00:10:10.430> board<00:10:10.640> to 00:10:11.530 --> 00:10:11.540 align:start position:0% they cannot use the save the board to 00:10:11.540 --> 00:10:17.370 align:start position:0% they cannot use the save the board to prevent<00:10:12.260> the<00:10:12.410> revenues<00:10:12.740> here<00:10:15.520> but<00:10:16.520> in<00:10:16.790> ghost 00:10:17.370 --> 00:10:17.380 align:start position:0% prevent the revenues here but in ghost 00:10:17.380 --> 00:10:22.450 align:start position:0% prevent the revenues here but in ghost every<00:10:18.380> vote<00:10:18.680> does<00:10:19.010> not<00:10:19.400> expired<00:10:21.070> so<00:10:22.070> here 00:10:22.450 --> 00:10:22.460 align:start position:0% every vote does not expired so here 00:10:22.460 --> 00:10:26.560 align:start position:0% every vote does not expired so here there<00:10:23.090> is<00:10:23.120> a<00:10:23.210> huge<00:10:24.130> to<00:10:25.130> fog<00:10:25.400> from<00:10:26.120> rock<00:10:26.300> from 00:10:26.560 --> 00:10:26.570 align:start position:0% there is a huge to fog from rock from 00:10:26.570 --> 00:10:29.410 align:start position:0% there is a huge to fog from rock from early<00:10:26.780> days<00:10:27.070> and<00:10:28.070> but<00:10:28.340> you<00:10:28.490> can<00:10:28.670> use<00:10:28.880> the<00:10:29.120> save 00:10:29.410 --> 00:10:29.420 align:start position:0% early days and but you can use the save 00:10:29.420 --> 00:10:32.130 align:start position:0% early days and but you can use the save save<00:10:29.720> the<00:10:29.840> bro<00:10:30.050> save<00:10:30.440> the<00:10:30.560> boat<00:10:30.760> in<00:10:31.760> ghost 00:10:32.130 --> 00:10:32.140 align:start position:0% save the bro save the boat in ghost 00:10:32.140 --> 00:10:35.890 align:start position:0% save the bro save the boat in ghost using<00:10:33.140> ghost<00:10:33.760> the<00:10:34.760> fog<00:10:34.970> choice<00:10:35.210> is<00:10:35.480> based<00:10:35.660> on 00:10:35.890 --> 00:10:35.900 align:start position:0% using ghost the fog choice is based on 00:10:35.900 --> 00:10:37.930 align:start position:0% using ghost the fog choice is based on every<00:10:36.320> per<00:10:36.710> student<00:10:37.040> election<00:10:37.550> on<00:10:37.730> each 00:10:37.930 --> 00:10:37.940 align:start position:0% every per student election on each 00:10:37.940 --> 00:10:46.210 align:start position:0% every per student election on each height<00:10:38.240> so<00:10:39.140> every<00:10:39.440> word<00:10:39.590> has<00:10:39.710> not<00:10:39.890> expired<00:10:45.220> so 00:10:46.210 --> 00:10:46.220 align:start position:0% height so every word has not expired so 00:10:46.220 --> 00:10:49.300 align:start position:0% height so every word has not expired so this<00:10:46.460> turns<00:10:47.300> into<00:10:47.600> creating<00:10:48.410> a<00:10:48.470> new<00:10:48.650> attack<00:10:49.070> on 00:10:49.300 --> 00:10:49.310 align:start position:0% this turns into creating a new attack on 00:10:49.310 --> 00:10:52.240 align:start position:0% this turns into creating a new attack on a<00:10:49.760> remedy<00:10:50.030> ghost<00:10:50.300> which<00:10:51.080> I<00:10:51.260> call<00:10:51.470> decoy<00:10:51.920> flip 00:10:52.240 --> 00:10:52.250 align:start position:0% a remedy ghost which I call decoy flip 00:10:52.250 --> 00:10:55.360 align:start position:0% a remedy ghost which I call decoy flip flop<00:10:52.520> attack<00:10:52.880> so<00:10:53.840> basically<00:10:54.200> what<00:10:54.950> I<00:10:55.100> want<00:10:55.310> to 00:10:55.360 --> 00:10:55.370 align:start position:0% flop attack so basically what I want to 00:10:55.370 --> 00:10:59.410 align:start position:0% flop attack so basically what I want to do<00:10:55.580> is<00:10:55.850> to<00:10:56.300> flip<00:10:57.220> every<00:10:58.220> roads<00:10:58.490> into<00:10:59.210> another 00:10:59.410 --> 00:10:59.420 align:start position:0% do is to flip every roads into another 00:10:59.420 --> 00:11:02.220 align:start position:0% do is to flip every roads into another chain<00:10:59.720> and<00:11:00.250> go<00:11:01.250> back<00:11:01.400> to<00:11:01.520> another<00:11:01.640> chain<00:11:01.940> and 00:11:02.220 --> 00:11:02.230 align:start position:0% chain and go back to another chain and 00:11:02.230 --> 00:11:04.759 align:start position:0% chain and go back to another chain and continue<00:11:03.580> the 00:11:04.759 --> 00:11:04.769 align:start position:0% continue the 00:11:04.769 --> 00:11:06.889 align:start position:0% continue the friends<00:11:05.069> the<00:11:05.220> big<00:11:05.369> difference<00:11:05.759> in<00:11:06.029> normal 00:11:06.889 --> 00:11:06.899 align:start position:0% friends the big difference in normal 00:11:06.899 --> 00:11:07.999 align:start position:0% friends the big difference in normal ghosts<00:11:07.170> and<00:11:07.499> error 00:11:07.999 --> 00:11:08.009 align:start position:0% ghosts and error 00:11:08.009 --> 00:11:13.269 align:start position:0% ghosts and error Emily<00:11:08.279> ghost<00:11:08.610> is<00:11:10.189> the<00:11:11.189> flip<00:11:11.489> of<00:11:11.869> volts 00:11:13.269 --> 00:11:13.279 align:start position:0% Emily ghost is the flip of volts 00:11:13.279 --> 00:11:16.729 align:start position:0% Emily ghost is the flip of volts decreases<00:11:14.279> the<00:11:14.459> score<00:11:15.019> in<00:11:16.019> longest<00:11:16.470> chain 00:11:16.729 --> 00:11:16.739 align:start position:0% decreases the score in longest chain 00:11:16.739 --> 00:11:19.699 align:start position:0% decreases the score in longest chain what<00:11:16.980> normal<00:11:17.220> ghost<00:11:17.489> some<00:11:18.360> squirrel<00:11:19.350> chain 00:11:19.699 --> 00:11:19.709 align:start position:0% what normal ghost some squirrel chain 00:11:19.709 --> 00:11:22.789 align:start position:0% what normal ghost some squirrel chain monotonically<00:11:20.699> increasing<00:11:21.329> and<00:11:21.540> every<00:11:22.470> Raven 00:11:22.789 --> 00:11:22.799 align:start position:0% monotonically increasing and every Raven 00:11:22.799 --> 00:11:24.769 align:start position:0% monotonically increasing and every Raven is<00:11:22.860> proof<00:11:23.069> is<00:11:23.249> based<00:11:23.399> on<00:11:23.610> that<00:11:23.730> property<00:11:24.149> but 00:11:24.769 --> 00:11:24.779 align:start position:0% is proof is based on that property but 00:11:24.779 --> 00:11:26.780 align:start position:0% is proof is based on that property but in<00:11:24.989> a<00:11:25.110> remedy<00:11:25.319> ghost<00:11:25.589> you<00:11:25.949> cannot<00:11:26.249> have<00:11:26.579> that 00:11:26.780 --> 00:11:26.790 align:start position:0% in a remedy ghost you cannot have that 00:11:26.790 --> 00:11:32.389 align:start position:0% in a remedy ghost you cannot have that property<00:11:28.879> this<00:11:29.879> is<00:11:29.939> the<00:11:30.480> situation<00:11:30.959> I<00:11:31.079> have<00:11:31.399> so 00:11:32.389 --> 00:11:32.399 align:start position:0% property this is the situation I have so 00:11:32.399 --> 00:11:35.539 align:start position:0% property this is the situation I have so imagine<00:11:32.910> that<00:11:32.939> to<00:11:33.619> chain<00:11:34.619> that<00:11:34.920> chain<00:11:34.980> brew 00:11:35.539 --> 00:11:35.549 align:start position:0% imagine that to chain that chain brew 00:11:35.549 --> 00:11:39.079 align:start position:0% imagine that to chain that chain brew chain<00:11:35.790> and<00:11:36.059> we<00:11:36.720> continuously<00:11:37.279> flip-flop<00:11:38.279> just 00:11:39.079 --> 00:11:39.089 align:start position:0% chain and we continuously flip-flop just 00:11:39.089 --> 00:11:44.840 align:start position:0% chain and we continuously flip-flop just before<00:11:39.420> the<00:11:39.569> chain<00:11:39.749> converges<00:11:43.519> and<00:11:44.519> the 00:11:44.840 --> 00:11:44.850 align:start position:0% before the chain converges and the 00:11:44.850 --> 00:11:49.189 align:start position:0% before the chain converges and the desert<00:11:45.209> is<00:11:46.730> the<00:11:47.730> necessary<00:11:47.999> saving<00:11:48.779> which 00:11:49.189 --> 00:11:49.199 align:start position:0% desert is the necessary saving which 00:11:49.199 --> 00:11:51.729 align:start position:0% desert is the necessary saving which that<00:11:49.529> the<00:11:49.619> battery<00:11:49.949> needs<00:11:50.369> to<00:11:50.579> prepare 00:11:51.729 --> 00:11:51.739 align:start position:0% that the battery needs to prepare 00:11:51.739 --> 00:11:54.590 align:start position:0% that the battery needs to prepare exponential<00:11:52.739> disgraces<00:11:53.389> against<00:11:54.389> the 00:11:54.590 --> 00:11:54.600 align:start position:0% exponential disgraces against the 00:11:54.600 --> 00:11:59.530 align:start position:0% exponential disgraces against the adversary<00:11:54.929> power<00:11:55.589> and<00:11:57.290> for<00:11:58.290> some<00:11:58.410> parameter 00:11:59.530 --> 00:11:59.540 align:start position:0% adversary power and for some parameter 00:11:59.540 --> 00:12:03.229 align:start position:0% adversary power and for some parameter 33%<00:12:00.540> attacker<00:12:00.959> can<00:12:01.429> prevent<00:12:02.429> ripeness<00:12:02.939> for 00:12:03.229 --> 00:12:03.239 align:start position:0% 33% attacker can prevent ripeness for 00:12:03.239 --> 00:12:06.199 align:start position:0% 33% attacker can prevent ripeness for 100<00:12:03.660> epic<00:12:03.989> it's<00:12:04.290> like<00:12:04.470> a<00:12:04.739> few<00:12:05.429> hours<00:12:05.489> or<00:12:06.029> 10 00:12:06.199 --> 00:12:06.209 align:start position:0% 100 epic it's like a few hours or 10 00:12:06.209 --> 00:12:10.819 align:start position:0% 100 epic it's like a few hours or 10 hours<00:12:06.470> by<00:12:07.470> 5<00:12:08.100> epochs<00:12:08.730> of<00:12:08.939> savings<00:12:09.619> now<00:12:10.619> for 00:12:10.819 --> 00:12:10.829 align:start position:0% hours by 5 epochs of savings now for 00:12:10.829 --> 00:12:14.119 align:start position:0% hours by 5 epochs of savings now for more<00:12:11.249> big<00:12:12.240> adversary<00:12:12.929> it<00:12:13.259> takes<00:12:13.709> much<00:12:13.980> longer 00:12:14.119 --> 00:12:14.129 align:start position:0% more big adversary it takes much longer 00:12:14.129 --> 00:12:24.220 align:start position:0% more big adversary it takes much longer to<00:12:14.309> the<00:12:15.149> chain<00:12:15.360> for<00:12:15.629> the<00:12:15.720> chain<00:12:15.869> wineries<00:12:22.519> yeah 00:12:24.220 --> 00:12:24.230 align:start position:0% to the chain for the chain wineries yeah 00:12:24.230 --> 00:12:26.960 align:start position:0% to the chain for the chain wineries yeah small<00:12:25.230> might<00:12:25.679> occasion<00:12:26.100> of<00:12:26.249> this<00:12:26.369> attack<00:12:26.730> is 00:12:26.960 --> 00:12:26.970 align:start position:0% small might occasion of this attack is 00:12:26.970 --> 00:12:30.590 align:start position:0% small might occasion of this attack is FMOD<00:12:27.809> ghost<00:12:28.049> it's<00:12:28.769> a<00:12:29.040> variant<00:12:29.579> of<00:12:29.790> a<00:12:30.179> remedy 00:12:30.590 --> 00:12:30.600 align:start position:0% FMOD ghost it's a variant of a remedy 00:12:30.600 --> 00:12:33.919 align:start position:0% FMOD ghost it's a variant of a remedy ghost<00:12:31.220> to<00:12:32.220> mitigating<00:12:32.730> saving<00:12:33.299> strategy 00:12:33.919 --> 00:12:33.929 align:start position:0% ghost to mitigating saving strategy 00:12:33.929 --> 00:12:36.859 align:start position:0% ghost to mitigating saving strategy so<00:12:34.379> in<00:12:34.679> aromatic<00:12:35.129> ghost<00:12:35.309> we<00:12:35.759> count<00:12:36.149> every<00:12:36.839> vote 00:12:36.859 --> 00:12:36.869 align:start position:0% so in aromatic ghost we count every vote 00:12:36.869 --> 00:12:40.309 align:start position:0% so in aromatic ghost we count every vote every<00:12:37.379> old<00:12:38.009> abroad<00:12:38.339> if<00:12:38.850> it<00:12:39.179> is<00:12:39.329> greatest<00:12:39.809> but 00:12:40.309 --> 00:12:40.319 align:start position:0% every old abroad if it is greatest but 00:12:40.319 --> 00:12:42.980 align:start position:0% every old abroad if it is greatest but in<00:12:40.439> affinity<00:12:40.889> ghost<00:12:41.069> we<00:12:41.579> only<00:12:41.759> count<00:12:42.179> a<00:12:42.509> vote 00:12:42.980 --> 00:12:42.990 align:start position:0% in affinity ghost we only count a vote 00:12:42.990 --> 00:12:45.710 align:start position:0% in affinity ghost we only count a vote from<00:12:43.350> the<00:12:43.410> current<00:12:43.949> epoch<00:12:44.299> was<00:12:45.299> a<00:12:45.329> previous 00:12:45.710 --> 00:12:45.720 align:start position:0% from the current epoch was a previous 00:12:45.720 --> 00:12:51.980 align:start position:0% from the current epoch was a previous block<00:12:49.220> someone<00:12:50.220> say<00:12:50.459> that<00:12:50.910> it's<00:12:51.209> kind<00:12:51.839> of 00:12:51.980 --> 00:12:51.990 align:start position:0% block someone say that it's kind of 00:12:51.990 --> 00:12:53.809 align:start position:0% block someone say that it's kind of introduce<00:12:52.470> a<00:12:52.589> new<00:12:52.740> synchronous<00:12:53.279> function<00:12:53.669> on 00:12:53.809 --> 00:12:53.819 align:start position:0% introduce a new synchronous function on 00:12:53.819 --> 00:12:56.539 align:start position:0% introduce a new synchronous function on consensus<00:12:54.360> but<00:12:54.600> it's<00:12:54.749> not<00:12:54.959> that<00:12:55.559> true<00:12:55.799> because 00:12:56.539 --> 00:12:56.549 align:start position:0% consensus but it's not that true because 00:12:56.549 --> 00:13:00.499 align:start position:0% consensus but it's not that true because in<00:12:57.119> 2.0<00:12:57.899> case<00:12:58.110> the<00:12:58.980> effigy<00:12:59.699> is<00:12:59.850> decoupled<00:13:00.269> from 00:13:00.499 --> 00:13:00.509 align:start position:0% in 2.0 case the effigy is decoupled from 00:13:00.509 --> 00:13:03.079 align:start position:0% in 2.0 case the effigy is decoupled from the<00:13:00.689> chain<00:13:01.110> so<00:13:02.100> the<00:13:02.429> synchronous<00:13:02.850> sumption 00:13:03.079 --> 00:13:03.089 align:start position:0% the chain so the synchronous sumption 00:13:03.089 --> 00:13:06.739 align:start position:0% the chain so the synchronous sumption does<00:13:03.239> not<00:13:03.419> change<00:13:04.309> but<00:13:05.309> here<00:13:05.610> still<00:13:05.999> the<00:13:06.329> coil 00:13:06.739 --> 00:13:06.749 align:start position:0% does not change but here still the coil 00:13:06.749 --> 00:13:08.600 align:start position:0% does not change but here still the coil flip-flop<00:13:07.230> is<00:13:07.410> possible<00:13:07.889> because<00:13:08.160> we<00:13:08.429> can 00:13:08.600 --> 00:13:08.610 align:start position:0% flip-flop is possible because we can 00:13:08.610 --> 00:13:13.980 align:start position:0% flip-flop is possible because we can have<00:13:08.819> one<00:13:09.209> epoch<00:13:09.600> of<00:13:09.689> savings<00:13:12.410> so 00:13:13.980 --> 00:13:13.990 align:start position:0% have one epoch of savings so 00:13:13.990 --> 00:13:16.260 align:start position:0% have one epoch of savings so this<00:13:14.170> starts<00:13:14.590> a<00:13:14.740> pretty<00:13:15.010> much<00:13:15.220> a<00:13:15.460> new<00:13:15.760> question 00:13:16.260 --> 00:13:16.270 align:start position:0% this starts a pretty much a new question 00:13:16.270 --> 00:13:18.540 align:start position:0% this starts a pretty much a new question that<00:13:16.480> why<00:13:16.870> a<00:13:17.200> remedy<00:13:17.470> goes<00:13:17.680> in<00:13:18.190> the<00:13:18.340> first 00:13:18.540 --> 00:13:18.550 align:start position:0% that why a remedy goes in the first 00:13:18.550 --> 00:13:21.270 align:start position:0% that why a remedy goes in the first place<00:13:18.790> compared<00:13:19.780> to<00:13:19.900> non<00:13:20.080> aromatic<00:13:20.410> parental 00:13:21.270 --> 00:13:21.280 align:start position:0% place compared to non aromatic parental 00:13:21.280 --> 00:13:23.220 align:start position:0% place compared to non aromatic parental ghosts<00:13:21.520> especially<00:13:22.450> there's<00:13:22.630> no<00:13:22.780> sheepish 00:13:23.220 --> 00:13:23.230 align:start position:0% ghosts especially there's no sheepish 00:13:23.230 --> 00:13:27.090 align:start position:0% ghosts especially there's no sheepish Casper<00:13:23.620> in<00:13:23.770> 2.0<00:13:24.160> for<00:13:25.090> now<00:13:25.240> so<00:13:25.960> it's<00:13:26.200> a<00:13:26.410> bit<00:13:26.890> easy 00:13:27.090 --> 00:13:27.100 align:start position:0% Casper in 2.0 for now so it's a bit easy 00:13:27.100 --> 00:13:30.390 align:start position:0% Casper in 2.0 for now so it's a bit easy to<00:13:27.280> manipulate<00:13:27.460> the<00:13:27.940> factories<00:13:29.220> the<00:13:30.220> another 00:13:30.390 --> 00:13:30.400 align:start position:0% to manipulate the factories the another 00:13:30.400 --> 00:13:32.790 align:start position:0% to manipulate the factories the another interesting<00:13:31.090> topic<00:13:31.360> which<00:13:31.840> I<00:13:31.960> don't<00:13:32.170> cannot 00:13:32.790 --> 00:13:32.800 align:start position:0% interesting topic which I don't cannot 00:13:32.800 --> 00:13:35.340 align:start position:0% interesting topic which I don't cannot talk<00:13:33.190> today<00:13:33.460> is<00:13:34.050> flip-flopping<00:13:35.050> a<00:13:35.140> remedy 00:13:35.340 --> 00:13:35.350 align:start position:0% talk today is flip-flopping a remedy 00:13:35.350 --> 00:13:37.560 align:start position:0% talk today is flip-flopping a remedy ghost<00:13:35.590> in<00:13:36.070> sheepish<00:13:36.610> Casper<00:13:37.000> it<00:13:37.360> was<00:13:37.480> in 00:13:37.560 --> 00:13:37.570 align:start position:0% ghost in sheepish Casper it was in 00:13:37.570 --> 00:13:40.110 align:start position:0% ghost in sheepish Casper it was in sheepish<00:13:37.810> Casper<00:13:38.230> every<00:13:38.770> message<00:13:39.160> is<00:13:39.340> imposed 00:13:40.110 --> 00:13:40.120 align:start position:0% sheepish Casper every message is imposed 00:13:40.120 --> 00:13:42.570 align:start position:0% sheepish Casper every message is imposed to<00:13:40.420> follow<00:13:40.720> the<00:13:40.960> folk<00:13:41.140> choice<00:13:41.380> so<00:13:42.100> the 00:13:42.570 --> 00:13:42.580 align:start position:0% to follow the folk choice so the 00:13:42.580 --> 00:13:44.820 align:start position:0% to follow the folk choice so the analysis<00:13:43.030> gets<00:13:43.480> a<00:13:43.600> bit<00:13:43.750> complicated<00:13:44.050> but 00:13:44.820 --> 00:13:44.830 align:start position:0% analysis gets a bit complicated but 00:13:44.830 --> 00:13:46.860 align:start position:0% analysis gets a bit complicated but basically<00:13:44.890> it's<00:13:45.430> mighty<00:13:45.640> gated<00:13:46.180> free<00:13:46.600> flow<00:13:46.840> of 00:13:46.860 --> 00:13:46.870 align:start position:0% basically it's mighty gated free flow of 00:13:46.870 --> 00:13:55.290 align:start position:0% basically it's mighty gated free flow of strategy<00:13:51.000> so<00:13:52.000> a<00:13:52.030> bit<00:13:52.210> not<00:13:52.660> incentives<00:13:53.350> so<00:13:54.300> you 00:13:55.290 --> 00:13:55.300 align:start position:0% strategy so a bit not incentives so you 00:13:55.300 --> 00:13:58.080 align:start position:0% strategy so a bit not incentives so you might<00:13:55.420> say<00:13:55.660> savings<00:13:56.260> can<00:13:56.500> be<00:13:56.530> detected<00:13:57.370> and 00:13:58.080 --> 00:13:58.090 align:start position:0% might say savings can be detected and 00:13:58.090 --> 00:14:03.450 align:start position:0% might say savings can be detected and rushed<00:13:58.990> but<00:14:00.450> basically<00:14:01.450> to<00:14:02.070> punish<00:14:03.070> driving 00:14:03.450 --> 00:14:03.460 align:start position:0% rushed but basically to punish driving 00:14:03.460 --> 00:14:05.730 align:start position:0% rushed but basically to punish driving this<00:14:03.520> failure<00:14:03.790> is<00:14:04.120> as<00:14:04.630> I<00:14:05.110> explained<00:14:05.650> in<00:14:05.680> the 00:14:05.730 --> 00:14:05.740 align:start position:0% this failure is as I explained in the 00:14:05.740 --> 00:14:08.760 align:start position:0% this failure is as I explained in the bicep<00:14:06.040> italic<00:14:06.430> in<00:14:06.610> this<00:14:06.790> morning<00:14:07.330> is<00:14:07.770> defined 00:14:08.760 --> 00:14:08.770 align:start position:0% bicep italic in this morning is defined 00:14:08.770 --> 00:14:11.310 align:start position:0% bicep italic in this morning is defined a<00:14:09.070> difficult<00:14:09.520> to<00:14:09.730> distinguish<00:14:10.660> between<00:14:10.720> no 00:14:11.310 --> 00:14:11.320 align:start position:0% a difficult to distinguish between no 00:14:11.320 --> 00:14:13.530 align:start position:0% a difficult to distinguish between no malicious<00:14:11.740> failure<00:14:12.070> because<00:14:12.730> it<00:14:12.760> just<00:14:13.030> might 00:14:13.530 --> 00:14:13.540 align:start position:0% malicious failure because it just might 00:14:13.540 --> 00:14:15.930 align:start position:0% malicious failure because it just might honest<00:14:14.050> no<00:14:14.860> just<00:14:15.310> get<00:14:15.520> down 00:14:15.930 --> 00:14:15.940 align:start position:0% honest no just get down 00:14:15.940 --> 00:14:19.800 align:start position:0% honest no just get down so<00:14:16.630> in<00:14:17.170> 2.0<00:14:17.830> has<00:14:18.220> some<00:14:18.490> incentive<00:14:19.030> mechanism 00:14:19.800 --> 00:14:19.810 align:start position:0% so in 2.0 has some incentive mechanism 00:14:19.810 --> 00:14:21.750 align:start position:0% so in 2.0 has some incentive mechanism to<00:14:19.990> punish<00:14:20.350> driving<00:14:20.710> this<00:14:20.800> failure<00:14:21.010> called<00:14:21.490> in 00:14:21.750 --> 00:14:21.760 align:start position:0% to punish driving this failure called in 00:14:21.760 --> 00:14:25.470 align:start position:0% to punish driving this failure called in activity<00:14:22.240> link<00:14:22.420> but<00:14:22.990> it's<00:14:23.170> just<00:14:23.820> kind<00:14:24.820> mild 00:14:25.470 --> 00:14:25.480 align:start position:0% activity link but it's just kind mild 00:14:25.480 --> 00:14:28.050 align:start position:0% activity link but it's just kind mild punishment<00:14:26.400> so<00:14:27.400> the<00:14:27.730> current 00:14:28.050 --> 00:14:28.060 align:start position:0% punishment so the current 00:14:28.060 --> 00:14:32.120 align:start position:0% punishment so the current parameterization<00:14:29.050> with<00:14:29.920> develop<00:14:30.460> robotic 00:14:32.120 --> 00:14:32.130 align:start position:0% parameterization with develop robotic 00:14:32.130 --> 00:14:35.010 align:start position:0% parameterization with develop robotic 33%<00:14:33.130> attacker<00:14:33.370> attacker<00:14:33.910> can<00:14:34.570> prevent 00:14:35.010 --> 00:14:35.020 align:start position:0% 33% attacker attacker can prevent 00:14:35.020 --> 00:14:39.030 align:start position:0% 33% attacker attacker can prevent finality<00:14:35.440> for<00:14:35.770> a<00:14:35.830> few<00:14:36.010> days<00:14:36.190> with<00:14:37.060> 1%<00:14:37.900> cost<00:14:38.770> of 00:14:39.030 --> 00:14:39.040 align:start position:0% finality for a few days with 1% cost of 00:14:39.040 --> 00:14:43.820 align:start position:0% finality for a few days with 1% cost of the<00:14:39.250> stake<00:14:40.200> and<00:14:41.880> you<00:14:42.880> know<00:14:43.000> ravenous<00:14:43.480> attack 00:14:43.820 --> 00:14:43.830 align:start position:0% the stake and you know ravenous attack 00:14:43.830 --> 00:14:46.890 align:start position:0% the stake and you know ravenous attack sometimes<00:14:44.830> has<00:14:45.280> a<00:14:45.490> lot<00:14:45.700> of<00:14:45.730> the<00:14:45.940> world<00:14:46.180> because 00:14:46.890 --> 00:14:46.900 align:start position:0% sometimes has a lot of the world because 00:14:46.900 --> 00:14:50.300 align:start position:0% sometimes has a lot of the world because there's<00:14:47.200> a<00:14:47.290> layer<00:14:47.680> two<00:14:48.660> solutions<00:14:49.660> in<00:14:49.900> which 00:14:50.300 --> 00:14:50.310 align:start position:0% there's a layer two solutions in which 00:14:50.310 --> 00:14:53.310 align:start position:0% there's a layer two solutions in which they<00:14:51.310> had<00:14:51.430> some<00:14:51.640> challenge<00:14:52.210> period<00:14:52.630> and<00:14:52.960> if 00:14:53.310 --> 00:14:53.320 align:start position:0% they had some challenge period and if 00:14:53.320 --> 00:14:55.710 align:start position:0% they had some challenge period and if they<00:14:53.950> can<00:14:54.070> not<00:14:54.250> if<00:14:54.580> they<00:14:54.820> can<00:14:54.970> sense<00:14:55.420> a<00:14:55.540> shape 00:14:55.710 --> 00:14:55.720 align:start position:0% they can not if they can sense a shape 00:14:55.720 --> 00:14:58.800 align:start position:0% they can not if they can sense a shape on<00:14:55.930> the<00:14:56.020> fraud<00:14:56.530> proof<00:14:56.880> in<00:14:57.880> plasma<00:14:58.360> and<00:14:58.450> writing 00:14:58.800 --> 00:14:58.810 align:start position:0% on the fraud proof in plasma and writing 00:14:58.810 --> 00:15:00.180 align:start position:0% on the fraud proof in plasma and writing otherwise<00:14:59.230> so<00:14:59.350> you<00:14:59.440> can<00:14:59.560> get<00:14:59.740> a<00:14:59.860> bunch<00:15:00.070> of 00:15:00.180 --> 00:15:00.190 align:start position:0% otherwise so you can get a bunch of 00:15:00.190 --> 00:15:03.270 align:start position:0% otherwise so you can get a bunch of money<00:15:00.460> from<00:15:00.790> the<00:15:01.000> layer<00:15:01.120> two<00:15:01.390> construction<00:15:02.380> so 00:15:03.270 --> 00:15:03.280 align:start position:0% money from the layer two construction so 00:15:03.280 --> 00:15:06.540 align:start position:0% money from the layer two construction so I<00:15:03.310> think<00:15:03.520> it's<00:15:04.450> a<00:15:04.690> new<00:15:04.840> question<00:15:05.110> to<00:15:05.490> how<00:15:06.490> to 00:15:06.540 --> 00:15:06.550 align:start position:0% I think it's a new question to how to 00:15:06.550 --> 00:15:08.340 align:start position:0% I think it's a new question to how to nourish<00:15:07.120> this<00:15:07.330> incentive<00:15:07.750> compatibility 00:15:08.340 --> 00:15:08.350 align:start position:0% nourish this incentive compatibility 00:15:08.350 --> 00:15:13.710 align:start position:0% nourish this incentive compatibility enlivens<00:15:09.070> failure<00:15:11.580> so<00:15:12.580> I<00:15:12.940> think<00:15:13.390> I<00:15:13.570> have<00:15:13.690> a 00:15:13.710 --> 00:15:13.720 align:start position:0% enlivens failure so I think I have a 00:15:13.720 --> 00:15:17.490 align:start position:0% enlivens failure so I think I have a time<00:15:14.050> so<00:15:14.470> I<00:15:14.770> quickly<00:15:15.430> introduced<00:15:15.880> some<00:15:16.500> attack 00:15:17.490 --> 00:15:17.500 align:start position:0% time so I quickly introduced some attack 00:15:17.500 --> 00:15:19.760 align:start position:0% time so I quickly introduced some attack on<00:15:17.740> class<00:15:17.920> by<00:15:18.070> refugee<00:15:18.460> which<00:15:18.880> is<00:15:19.030> funded<00:15:19.600> by 00:15:19.760 --> 00:15:19.770 align:start position:0% on class by refugee which is funded by 00:15:19.770 --> 00:15:27.660 align:start position:0% on class by refugee which is funded by last<00:15:20.770> year<00:15:21.810> so<00:15:24.450> in<00:15:25.450> FFG<00:15:26.080> so<00:15:26.500> originally<00:15:26.950> effigy 00:15:27.660 --> 00:15:27.670 align:start position:0% last year so in FFG so originally effigy 00:15:27.670 --> 00:15:31.110 align:start position:0% last year so in FFG so originally effigy removing<00:15:28.670> the<00:15:28.850> leader<00:15:29.090> in<00:15:29.810> kinds<00:15:30.500> of<00:15:30.590> bad<00:15:30.860> way 00:15:31.110 --> 00:15:31.120 align:start position:0% removing the leader in kinds of bad way 00:15:31.120 --> 00:15:35.920 align:start position:0% removing the leader in kinds of bad way because<00:15:32.120> so<00:15:32.840> these<00:15:33.730> squares<00:15:34.730> are<00:15:34.970> not<00:15:35.240> rocks 00:15:35.920 --> 00:15:35.930 align:start position:0% because so these squares are not rocks 00:15:35.930 --> 00:15:39.610 align:start position:0% because so these squares are not rocks it's<00:15:36.110> checkpoints<00:15:36.680> and<00:15:38.110> remember<00:15:39.110> that 00:15:39.610 --> 00:15:39.620 align:start position:0% it's checkpoints and remember that 00:15:39.620 --> 00:15:43.050 align:start position:0% it's checkpoints and remember that unlocking<00:15:40.310> lure<00:15:40.520> in<00:15:40.730> Casper<00:15:41.060> effigy<00:15:41.510> is 00:15:43.050 --> 00:15:43.060 align:start position:0% unlocking lure in Casper effigy is 00:15:43.060 --> 00:15:46.150 align:start position:0% unlocking lure in Casper effigy is observation<00:15:44.060> of<00:15:44.270> high<00:15:44.780> year<00:15:45.160> notarized 00:15:46.150 --> 00:15:46.160 align:start position:0% observation of high year notarized 00:15:46.160 --> 00:15:50.980 align:start position:0% observation of high year notarized checkpoint<00:15:46.670> and<00:15:48.010> so<00:15:49.010> in<00:15:49.310> this<00:15:49.430> case<00:15:49.990> imagine 00:15:50.980 --> 00:15:50.990 align:start position:0% checkpoint and so in this case imagine 00:15:50.990 --> 00:15:55.030 align:start position:0% checkpoint and so in this case imagine that<00:15:52.120> 104<00:15:53.120> letters<00:15:53.420> and<00:15:53.630> this<00:15:54.440> checkpoint 00:15:55.030 --> 00:15:55.040 align:start position:0% that 104 letters and this checkpoint 00:15:55.040 --> 00:15:57.880 align:start position:0% that 104 letters and this checkpoint it's<00:15:55.460> close<00:15:55.850> to<00:15:56.150> two<00:15:56.780> swords<00:15:57.140> that<00:15:57.590> is<00:15:57.710> not 00:15:57.880 --> 00:15:57.890 align:start position:0% it's close to two swords that is not 00:15:57.890 --> 00:16:01.860 align:start position:0% it's close to two swords that is not notarized<00:15:58.670> yet<00:15:59.020> but<00:16:00.020> the<00:16:00.500> bursary<00:16:00.830> can 00:16:01.860 --> 00:16:01.870 align:start position:0% notarized yet but the bursary can 00:16:01.870 --> 00:16:04.750 align:start position:0% notarized yet but the bursary can justify<00:16:02.870> this<00:16:02.930> checkpoint<00:16:03.560> arbitrary<00:16:04.460> any 00:16:04.750 --> 00:16:04.760 align:start position:0% justify this checkpoint arbitrary any 00:16:04.760 --> 00:16:08.800 align:start position:0% justify this checkpoint arbitrary any time<00:16:05.000> so<00:16:05.780> in<00:16:06.710> this<00:16:07.100> situation<00:16:07.600> the<00:16:08.600> folk 00:16:08.800 --> 00:16:08.810 align:start position:0% time so in this situation the folk 00:16:08.810 --> 00:16:11.980 align:start position:0% time so in this situation the folk choice<00:16:09.050> favors<00:16:09.620> this<00:16:09.920> side<00:16:10.580> of<00:16:10.700> a<00:16:10.730> chain<00:16:11.000> so 00:16:11.980 --> 00:16:11.990 align:start position:0% choice favors this side of a chain so 00:16:11.990 --> 00:16:14.500 align:start position:0% choice favors this side of a chain so creating<00:16:12.410> a<00:16:12.500> new<00:16:12.880> checkpoint<00:16:13.880> which<00:16:14.060> is<00:16:14.180> close 00:16:14.500 --> 00:16:14.510 align:start position:0% creating a new checkpoint which is close 00:16:14.510 --> 00:16:18.100 align:start position:0% creating a new checkpoint which is close to<00:16:14.540> the<00:16:15.100> notarization<00:16:16.100> but<00:16:17.090> exactly<00:16:17.810> the<00:16:17.930> same 00:16:18.100 --> 00:16:18.110 align:start position:0% to the notarization but exactly the same 00:16:18.110 --> 00:16:22.240 align:start position:0% to the notarization but exactly the same that<00:16:18.410> at<00:16:18.740> the<00:16:18.950> time<00:16:19.220> at<00:16:19.970> the<00:16:20.090> grocery<00:16:20.120> flip<00:16:21.250> the 00:16:22.240 --> 00:16:22.250 align:start position:0% that at the time at the grocery flip the 00:16:22.250 --> 00:16:25.210 align:start position:0% that at the time at the grocery flip the head<00:16:22.490> of<00:16:22.670> the<00:16:22.790> folk<00:16:22.970> choice<00:16:23.740> that<00:16:24.740> in<00:16:24.920> that<00:16:25.040> way 00:16:25.210 --> 00:16:25.220 align:start position:0% head of the folk choice that in that way 00:16:25.220 --> 00:16:28.510 align:start position:0% head of the folk choice that in that way and<00:16:25.460> in<00:16:26.240> high<00:16:26.630> synchrony<00:16:27.260> Network<00:16:27.860> other 00:16:28.510 --> 00:16:28.520 align:start position:0% and in high synchrony Network other 00:16:28.520 --> 00:16:30.040 align:start position:0% and in high synchrony Network other words<00:16:28.670> so<00:16:28.760> you<00:16:28.820> can<00:16:29.000> continue<00:16:29.630> this<00:16:29.840> attack 00:16:30.040 --> 00:16:30.050 align:start position:0% words so you can continue this attack 00:16:30.050 --> 00:16:34.870 align:start position:0% words so you can continue this attack whoever<00:16:32.290> so<00:16:33.290> why<00:16:33.589> this<00:16:33.980> does<00:16:34.190> not<00:16:34.339> happen<00:16:34.790> in 00:16:34.870 --> 00:16:34.880 align:start position:0% whoever so why this does not happen in 00:16:34.880 --> 00:16:38.560 align:start position:0% whoever so why this does not happen in tandem<00:16:35.150> and<00:16:36.190> it's<00:16:37.190> simply<00:16:37.580> because<00:16:37.850> leader 00:16:38.560 --> 00:16:38.570 align:start position:0% tandem and it's simply because leader 00:16:38.570 --> 00:16:40.890 align:start position:0% tandem and it's simply because leader decides<00:16:39.230> the<00:16:39.410> view<00:16:39.650> of<00:16:39.890> the<00:16:40.070> current<00:16:40.190> around 00:16:40.890 --> 00:16:40.900 align:start position:0% decides the view of the current around 00:16:40.900 --> 00:16:47.170 align:start position:0% decides the view of the current around so<00:16:41.900> what<00:16:42.140> we<00:16:42.320> should<00:16:42.380> do<00:16:42.740> is<00:16:44.500> to<00:16:45.940> have<00:16:46.940> some 00:16:47.170 --> 00:16:47.180 align:start position:0% so what we should do is to have some 00:16:47.180 --> 00:16:50.890 align:start position:0% so what we should do is to have some sort<00:16:47.570> of<00:16:47.630> thickness<00:16:48.230> property<00:16:48.800> in<00:16:49.010> effigy<00:16:49.900> so 00:16:50.890 --> 00:16:50.900 align:start position:0% sort of thickness property in effigy so 00:16:50.900 --> 00:16:52.960 align:start position:0% sort of thickness property in effigy so there's<00:16:51.620> a<00:16:51.710> lot<00:16:51.860> of<00:16:51.890> construction<00:16:52.339> to<00:16:52.610> prevent 00:16:52.960 --> 00:16:52.970 align:start position:0% there's a lot of construction to prevent 00:16:52.970 --> 00:16:55.510 align:start position:0% there's a lot of construction to prevent this<00:16:53.089> attack<00:16:53.240> it's<00:16:53.839> one<00:16:54.050> idea<00:16:54.230> is<00:16:54.740> to<00:16:55.490> not 00:16:55.510 --> 00:16:55.520 align:start position:0% this attack it's one idea is to not 00:16:55.520 --> 00:16:58.540 align:start position:0% this attack it's one idea is to not allow<00:16:56.120> the<00:16:56.540> change<00:16:57.050> was<00:16:57.530> a<00:16:57.560> view<00:16:57.830> in<00:16:58.310> the 00:16:58.540 --> 00:16:58.550 align:start position:0% allow the change was a view in the 00:16:58.550 --> 00:17:01.540 align:start position:0% allow the change was a view in the middle<00:16:58.850> of<00:16:58.910> the<00:16:59.030> epoch<00:16:59.770> for<00:17:00.770> example<00:17:01.190> we<00:17:01.490> do 00:17:01.540 --> 00:17:01.550 align:start position:0% middle of the epoch for example we do 00:17:01.550 --> 00:17:04.929 align:start position:0% middle of the epoch for example we do not<00:17:01.730> allow<00:17:02.720> any<00:17:02.960> new<00:17:03.530> justified<00:17:04.250> checkpoint 00:17:04.929 --> 00:17:04.939 align:start position:0% not allow any new justified checkpoint 00:17:04.939 --> 00:17:13.540 align:start position:0% not allow any new justified checkpoint if<00:17:05.420> it's<00:17:05.810> in<00:17:06.020> the<00:17:06.110> middle<00:17:06.230> of<00:17:06.439> the<00:17:06.500> epoch<00:17:11.920> yes<00:17:12.920> I 00:17:13.540 --> 00:17:13.550 align:start position:0% if it's in the middle of the epoch yes I 00:17:13.550 --> 00:17:25.500 align:start position:0% if it's in the middle of the epoch yes I think<00:17:13.730> it's<00:17:14.030> finish<00:17:14.990> thank<00:17:15.589> you 00:17:25.500 --> 00:17:25.510 align:start position:0% 00:17:25.510 --> 00:17:27.570 align:start position:0% you