WEBVTT Kind: captions Language: en 00:00:03.980 --> 00:00:06.710 align:start position:0% thank<00:00:04.980> you<00:00:05.130> all<00:00:05.250> for<00:00:05.430> coming 00:00:06.710 --> 00:00:06.720 align:start position:0% thank you all for coming 00:00:06.720 --> 00:00:09.199 align:start position:0% thank you all for coming myself<00:00:07.649> shall<00:00:07.950> we<00:00:08.100> chat<00:00:08.400> chang-dong<00:00:08.910> could 00:00:09.199 --> 00:00:09.209 align:start position:0% myself shall we chat chang-dong could 00:00:09.209 --> 00:00:11.959 align:start position:0% myself shall we chat chang-dong could justin<00:00:10.139> and<00:00:10.500> metallic<00:00:11.160> who<00:00:11.309> is<00:00:11.459> apparently<00:00:11.730> on 00:00:11.959 --> 00:00:11.969 align:start position:0% justin and metallic who is apparently on 00:00:11.969 --> 00:00:16.369 align:start position:0% justin and metallic who is apparently on this<00:00:12.270> floor<00:00:12.559> will<00:00:14.059> today<00:00:15.059> give<00:00:15.420> you<00:00:15.539> a<00:00:15.600> deep 00:00:16.369 --> 00:00:16.379 align:start position:0% this floor will today give you a deep 00:00:16.379 --> 00:00:17.960 align:start position:0% this floor will today give you a deep dive<00:00:16.529> into<00:00:16.590> the<00:00:16.859> phase<00:00:17.070> zero<00:00:17.340> specification 00:00:17.960 --> 00:00:17.970 align:start position:0% dive into the phase zero specification 00:00:17.970 --> 00:00:20.570 align:start position:0% dive into the phase zero specification that<00:00:18.240> is<00:00:18.449> the<00:00:18.689> beacon<00:00:19.050> chain<00:00:19.289> of<00:00:19.550> Ethier<00:00:20.550> and 00:00:20.570 --> 00:00:20.580 align:start position:0% that is the beacon chain of Ethier and 00:00:20.580 --> 00:00:26.690 align:start position:0% that is the beacon chain of Ethier and 2.0<00:00:21.120> protocol<00:00:23.630> today<00:00:24.630> we<00:00:25.170> will<00:00:25.380> get<00:00:26.280> a<00:00:26.340> sec 00:00:26.690 --> 00:00:26.700 align:start position:0% 2.0 protocol today we will get a sec 00:00:26.700 --> 00:00:28.730 align:start position:0% 2.0 protocol today we will get a sec nickel<00:00:26.970> as<00:00:27.150> we<00:00:27.360> can<00:00:27.660> with<00:00:28.200> the<00:00:28.440> time 00:00:28.730 --> 00:00:28.740 align:start position:0% nickel as we can with the time 00:00:28.740 --> 00:00:31.130 align:start position:0% nickel as we can with the time permitting<00:00:29.550> and<00:00:29.789> at<00:00:30.180> the<00:00:30.300> same<00:00:30.449> time<00:00:30.750> point 00:00:31.130 --> 00:00:31.140 align:start position:0% permitting and at the same time point 00:00:31.140 --> 00:00:32.900 align:start position:0% permitting and at the same time point you<00:00:31.289> to<00:00:31.470> portions<00:00:32.070> of<00:00:32.129> the<00:00:32.219> spec<00:00:32.489> so<00:00:32.669> you<00:00:32.759> can 00:00:32.900 --> 00:00:32.910 align:start position:0% you to portions of the spec so you can 00:00:32.910 --> 00:00:35.569 align:start position:0% you to portions of the spec so you can dive<00:00:33.059> in<00:00:33.239> deeper<00:00:33.570> and<00:00:34.320> hopefully<00:00:34.680> just<00:00:35.010> get 00:00:35.569 --> 00:00:35.579 align:start position:0% dive in deeper and hopefully just get 00:00:35.579 --> 00:00:38.000 align:start position:0% dive in deeper and hopefully just get you<00:00:35.670> more<00:00:35.909> acquainted<00:00:36.420> with<00:00:36.649> what's<00:00:37.649> going<00:00:37.800> on 00:00:38.000 --> 00:00:38.010 align:start position:0% you more acquainted with what's going on 00:00:38.010 --> 00:00:39.410 align:start position:0% you more acquainted with what's going on so<00:00:38.280> that<00:00:38.429> you<00:00:38.519> can<00:00:38.730> better<00:00:39.030> technically 00:00:39.410 --> 00:00:39.420 align:start position:0% so that you can better technically 00:00:39.420 --> 00:00:41.149 align:start position:0% so that you can better technically understand<00:00:39.870> the<00:00:40.170> problems<00:00:40.469> at<00:00:40.589> hand<00:00:40.620> and<00:00:41.100> the 00:00:41.149 --> 00:00:41.159 align:start position:0% understand the problems at hand and the 00:00:41.159 --> 00:00:45.319 align:start position:0% understand the problems at hand and the solutions<00:00:41.579> and<00:00:42.920> kindig<00:00:43.920> and<00:00:44.069> contribute<00:00:44.550> all 00:00:45.319 --> 00:00:45.329 align:start position:0% solutions and kindig and contribute all 00:00:45.329 --> 00:00:51.349 align:start position:0% solutions and kindig and contribute all that<00:00:45.739> so<00:00:49.489> we're<00:00:50.489> building<00:00:50.609> this<00:00:50.850> thing<00:00:50.909> as<00:00:51.329> it 00:00:51.349 --> 00:00:51.359 align:start position:0% that so we're building this thing as it 00:00:51.359 --> 00:00:52.759 align:start position:0% that so we're building this thing as it theorem<00:00:51.659> -<00:00:51.839> it's<00:00:52.019> a<00:00:52.079> chartered<00:00:52.350> protocol 00:00:52.759 --> 00:00:52.769 align:start position:0% theorem - it's a chartered protocol 00:00:52.769 --> 00:00:54.979 align:start position:0% theorem - it's a chartered protocol there<00:00:53.309> are<00:00:53.519> many<00:00:54.120> shards<00:00:54.510> connected<00:00:54.870> to<00:00:54.960> a 00:00:54.979 --> 00:00:54.989 align:start position:0% there are many shards connected to a 00:00:54.989 --> 00:00:58.910 align:start position:0% there are many shards connected to a central<00:00:55.229> beacon<00:00:55.799> chain<00:00:56.569> it<00:00:57.569> also<00:00:57.960> is<00:00:58.530> has 00:00:58.910 --> 00:00:58.920 align:start position:0% central beacon chain it also is has 00:00:58.920 --> 00:01:01.729 align:start position:0% central beacon chain it also is has loose<00:00:59.159> coupling<00:00:59.370> to<00:00:59.760> the<00:01:00.379> existing<00:01:01.379> ethereum 00:01:01.729 --> 00:01:01.739 align:start position:0% loose coupling to the existing ethereum 00:01:01.739 --> 00:01:03.590 align:start position:0% loose coupling to the existing ethereum chain<00:01:01.979> which<00:01:02.760> at<00:01:02.940> the<00:01:02.999> beginning<00:01:03.299> just 00:01:03.590 --> 00:01:03.600 align:start position:0% chain which at the beginning just 00:01:03.600 --> 00:01:05.750 align:start position:0% chain which at the beginning just supports<00:01:03.959> deposits<00:01:04.500> coming<00:01:04.949> into<00:01:05.100> the<00:01:05.519> beacon 00:01:05.750 --> 00:01:05.760 align:start position:0% supports deposits coming into the beacon 00:01:05.760 --> 00:01:09.410 align:start position:0% supports deposits coming into the beacon chain<00:01:05.970> today<00:01:06.810> phase<00:01:07.619> zero<00:01:07.950> is<00:01:08.189> just<00:01:08.610> this<00:01:08.820> pure 00:01:09.410 --> 00:01:09.420 align:start position:0% chain today phase zero is just this pure 00:01:09.420 --> 00:01:11.300 align:start position:0% chain today phase zero is just this pure proof<00:01:09.630> of<00:01:09.750> stake<00:01:09.960> chain<00:01:10.259> connected<00:01:11.039> to<00:01:11.130> the 00:01:11.300 --> 00:01:11.310 align:start position:0% proof of stake chain connected to the 00:01:11.310 --> 00:01:14.539 align:start position:0% proof of stake chain connected to the etherium<00:01:12.030> one<00:01:12.180> protocol<00:01:12.600> so<00:01:13.500> that<00:01:13.710> is<00:01:13.890> what 00:01:14.539 --> 00:01:14.549 align:start position:0% etherium one protocol so that is what 00:01:14.549 --> 00:01:16.340 align:start position:0% etherium one protocol so that is what we'll<00:01:14.670> talk<00:01:14.850> about<00:01:14.909> today<00:01:15.090> I<00:01:15.479> believe<00:01:16.079> at<00:01:16.320> the 00:01:16.340 --> 00:01:16.350 align:start position:0% we'll talk about today I believe at the 00:01:16.350 --> 00:01:18.380 align:start position:0% we'll talk about today I believe at the same<00:01:16.590> time<00:01:16.890> will<00:01:17.369> at<00:01:17.490> least<00:01:17.579> show<00:01:18.119> you<00:01:18.180> the 00:01:18.380 --> 00:01:18.390 align:start position:0% same time will at least show you the 00:01:18.390 --> 00:01:20.389 align:start position:0% same time will at least show you the scaffolding<00:01:19.200> upon<00:01:19.380> which<00:01:19.740> shard<00:01:20.009> chains<00:01:20.250> will 00:01:20.389 --> 00:01:20.399 align:start position:0% scaffolding upon which shard chains will 00:01:20.399 --> 00:01:22.249 align:start position:0% scaffolding upon which shard chains will be<00:01:20.430> connected<00:01:20.909> but<00:01:21.600> will<00:01:21.719> you'll<00:01:21.810> not<00:01:21.990> dive 00:01:22.249 --> 00:01:22.259 align:start position:0% be connected but will you'll not dive 00:01:22.259 --> 00:01:26.649 align:start position:0% be connected but will you'll not dive deep<00:01:22.560> into<00:01:22.799> this<00:01:23.070> portion<00:01:23.460> of<00:01:23.670> the<00:01:23.850> protocol 00:01:26.649 --> 00:01:26.659 align:start position:0% 00:01:26.659 --> 00:01:31.459 align:start position:0% the<00:01:29.600> beginning<00:01:30.600> what<00:01:30.750> we're<00:01:30.840> gonna<00:01:30.960> start<00:01:31.289> off 00:01:31.459 --> 00:01:31.469 align:start position:0% the beginning what we're gonna start off 00:01:31.469 --> 00:01:33.289 align:start position:0% the beginning what we're gonna start off with<00:01:31.649> today<00:01:31.770> is<00:01:32.189> we're<00:01:32.759> gonna<00:01:32.880> look<00:01:33.060> at<00:01:33.210> the 00:01:33.289 --> 00:01:33.299 align:start position:0% with today is we're gonna look at the 00:01:33.299 --> 00:01:34.940 align:start position:0% with today is we're gonna look at the kind<00:01:33.450> of<00:01:33.479> the<00:01:33.600> some<00:01:34.049> of<00:01:34.079> the<00:01:34.200> core<00:01:34.530> building 00:01:34.940 --> 00:01:34.950 align:start position:0% kind of the some of the core building 00:01:34.950 --> 00:01:37.609 align:start position:0% kind of the some of the core building blocks<00:01:35.189> of<00:01:35.399> consensus<00:01:36.000> that's<00:01:36.270> the<00:01:37.049> cast<00:01:37.320> for 00:01:37.609 --> 00:01:37.619 align:start position:0% blocks of consensus that's the cast for 00:01:37.619 --> 00:01:42.099 align:start position:0% blocks of consensus that's the cast for FFG<00:01:38.130> protocol<00:01:38.969> the<00:01:39.840> LNG<00:01:40.289> ghost<00:01:40.770> fork<00:01:41.460> choice 00:01:42.099 --> 00:01:42.109 align:start position:0% FFG protocol the LNG ghost fork choice 00:01:42.109 --> 00:01:47.719 align:start position:0% FFG protocol the LNG ghost fork choice randomness<00:01:43.109> and<00:01:44.240> BLS<00:01:45.270> signatures<00:01:46.609> after<00:01:47.609> that 00:01:47.719 --> 00:01:47.729 align:start position:0% randomness and BLS signatures after that 00:01:47.729 --> 00:01:49.639 align:start position:0% randomness and BLS signatures after that we'll<00:01:47.909> take<00:01:47.939> a<00:01:48.119> short<00:01:48.450> break<00:01:48.509> maybe<00:01:49.109> take<00:01:49.469> some 00:01:49.639 --> 00:01:49.649 align:start position:0% we'll take a short break maybe take some 00:01:49.649 --> 00:01:51.620 align:start position:0% we'll take a short break maybe take some questions<00:01:49.799> and<00:01:50.219> then<00:01:50.700> we'll<00:01:50.850> dive<00:01:51.030> into<00:01:51.329> the 00:01:51.620 --> 00:01:51.630 align:start position:0% questions and then we'll dive into the 00:01:51.630 --> 00:01:53.840 align:start position:0% questions and then we'll dive into the actual<00:01:52.009> some<00:01:53.009> of<00:01:53.100> the<00:01:53.159> mechanics<00:01:53.609> and<00:01:53.729> in 00:01:53.840 --> 00:01:53.850 align:start position:0% actual some of the mechanics and in 00:01:53.850 --> 00:01:56.179 align:start position:0% actual some of the mechanics and in stage<00:01:54.030> concrete<00:01:54.719> instantiation<00:01:55.619> of<00:01:55.920> the 00:01:56.179 --> 00:01:56.189 align:start position:0% stage concrete instantiation of the 00:01:56.189 --> 00:01:58.580 align:start position:0% stage concrete instantiation of the protocol<00:01:56.609> with<00:01:57.570> the<00:01:57.899> actual<00:01:58.350> state 00:01:58.580 --> 00:01:58.590 align:start position:0% protocol with the actual state 00:01:58.590 --> 00:02:00.499 align:start position:0% protocol with the actual state transition<00:01:59.070> and<00:01:59.280> things<00:01:59.490> and<00:01:59.880> validators<00:02:00.359> and 00:02:00.499 --> 00:02:00.509 align:start position:0% transition and things and validators and 00:02:00.509 --> 00:02:01.730 align:start position:0% transition and things and validators and things<00:02:00.659> built<00:02:00.899> on<00:02:01.020> top<00:02:01.229> of<00:02:01.409> some<00:02:01.590> of<00:02:01.619> these 00:02:01.730 --> 00:02:01.740 align:start position:0% things built on top of some of these 00:02:01.740 --> 00:02:06.919 align:start position:0% things built on top of some of these components<00:02:02.719> so<00:02:04.130> f<00:02:05.130> of<00:02:05.670> G<00:02:05.729> applied<00:02:06.299> to<00:02:06.630> proof<00:02:06.840> of 00:02:06.919 --> 00:02:06.929 align:start position:0% components so f of G applied to proof of 00:02:06.929 --> 00:02:08.570 align:start position:0% components so f of G applied to proof of stake<00:02:07.200> so<00:02:07.770> there<00:02:08.069> was<00:02:08.190> a<00:02:08.220> paper<00:02:08.340> written 00:02:08.570 --> 00:02:08.580 align:start position:0% stake so there was a paper written 00:02:08.580 --> 00:02:10.100 align:start position:0% stake so there was a paper written probably<00:02:09.240> bout<00:02:09.450> a<00:02:09.479> year<00:02:09.539> and<00:02:09.720> a<00:02:09.780> half<00:02:09.869> ago<00:02:10.020> now 00:02:10.100 --> 00:02:10.110 align:start position:0% probably bout a year and a half ago now 00:02:10.110 --> 00:02:14.660 align:start position:0% probably bout a year and a half ago now by<00:02:10.440> Vitalik<00:02:10.920> and<00:02:11.510> Virgil<00:02:12.510> Griffith<00:02:13.670> Casper 00:02:14.660 --> 00:02:14.670 align:start position:0% by Vitalik and Virgil Griffith Casper 00:02:14.670 --> 00:02:17.600 align:start position:0% by Vitalik and Virgil Griffith Casper effigy<00:02:15.290> consensus<00:02:16.290> protocol 00:02:17.600 --> 00:02:17.610 align:start position:0% effigy consensus protocol 00:02:17.610 --> 00:02:20.320 align:start position:0% effigy consensus protocol generally<00:02:18.180> built<00:02:18.360> to<00:02:18.480> be<00:02:18.570> layered<00:02:18.780> upon<00:02:19.230> a 00:02:20.320 --> 00:02:20.330 align:start position:0% generally built to be layered upon a 00:02:20.330 --> 00:02:22.760 align:start position:0% generally built to be layered upon a block<00:02:21.330> proposal<00:02:21.780> mechanism<00:02:22.230> the<00:02:22.350> original 00:02:22.760 --> 00:02:22.770 align:start position:0% block proposal mechanism the original 00:02:22.770 --> 00:02:25.160 align:start position:0% block proposal mechanism the original being<00:02:22.980> a<00:02:23.280> proof-of-work<00:02:23.670> mechanism<00:02:24.330> but 00:02:25.160 --> 00:02:25.170 align:start position:0% being a proof-of-work mechanism but 00:02:25.170 --> 00:02:27.920 align:start position:0% being a proof-of-work mechanism but there's<00:02:25.800> some<00:02:26.010> modifications<00:02:26.850> to<00:02:27.150> bring<00:02:27.750> this 00:02:27.920 --> 00:02:27.930 align:start position:0% there's some modifications to bring this 00:02:27.930 --> 00:02:30.350 align:start position:0% there's some modifications to bring this protocol<00:02:28.380> to<00:02:28.440> be<00:02:29.280> on<00:02:29.370> top<00:02:29.610> of<00:02:29.640> a<00:02:29.910> previous<00:02:30.210> take 00:02:30.350 --> 00:02:30.360 align:start position:0% protocol to be on top of a previous take 00:02:30.360 --> 00:02:31.880 align:start position:0% protocol to be on top of a previous take protocol<00:02:30.750> and<00:02:31.050> more<00:02:31.440> importantly<00:02:31.740> some 00:02:31.880 --> 00:02:31.890 align:start position:0% protocol and more importantly some 00:02:31.890 --> 00:02:33.290 align:start position:0% protocol and more importantly some modifications<00:02:32.520> that<00:02:32.730> get<00:02:32.880> us<00:02:33.000> to<00:02:33.150> where<00:02:33.210> we 00:02:33.290 --> 00:02:33.300 align:start position:0% modifications that get us to where we 00:02:33.300 --> 00:02:35.570 align:start position:0% modifications that get us to where we need<00:02:33.390> to<00:02:33.600> go<00:02:33.750> for<00:02:34.320> his<00:02:34.410> protocol<00:02:34.740> so<00:02:35.400> I'm<00:02:35.490> gonna 00:02:35.570 --> 00:02:35.580 align:start position:0% need to go for his protocol so I'm gonna 00:02:35.580 --> 00:02:39.260 align:start position:0% need to go for his protocol so I'm gonna go<00:02:35.730> over<00:02:35.760> some<00:02:36.530> of<00:02:37.670> some<00:02:38.670> of<00:02:38.820> some<00:02:39.000> of<00:02:39.150> those 00:02:39.260 --> 00:02:39.270 align:start position:0% go over some of some of some of those 00:02:39.270 --> 00:02:41.030 align:start position:0% go over some of some of some of those modifications<00:02:39.630> how<00:02:40.200> we<00:02:40.260> think<00:02:40.470> about<00:02:40.590> slots 00:02:41.030 --> 00:02:41.040 align:start position:0% modifications how we think about slots 00:02:41.040 --> 00:02:44.630 align:start position:0% modifications how we think about slots checkpoints<00:02:41.790> epochs<00:02:43.100> slashing<00:02:44.100> finality 00:02:44.630 --> 00:02:44.640 align:start position:0% checkpoints epochs slashing finality 00:02:44.640 --> 00:02:47.000 align:start position:0% checkpoints epochs slashing finality that<00:02:44.910> kind<00:02:45.390> of<00:02:45.420> stuff<00:02:45.660> I<00:02:46.320> will<00:02:46.530> give<00:02:46.740> you<00:02:46.860> an 00:02:47.000 --> 00:02:47.010 align:start position:0% that kind of stuff I will give you an 00:02:47.010 --> 00:02:50.000 align:start position:0% that kind of stuff I will give you an intuition<00:02:47.400> for<00:02:47.580> the<00:02:48.360> safety<00:02:48.780> proof<00:02:49.050> but<00:02:49.890> will 00:02:50.000 --> 00:02:50.010 align:start position:0% intuition for the safety proof but will 00:02:50.010 --> 00:02:52.580 align:start position:0% intuition for the safety proof but will not<00:02:50.100> have<00:02:50.310> time<00:02:50.460> to<00:02:50.640> dig<00:02:50.850> deep<00:02:51.240> into<00:02:51.480> that<00:02:51.690> and 00:02:52.580 --> 00:02:52.590 align:start position:0% not have time to dig deep into that and 00:02:52.590 --> 00:02:57.500 align:start position:0% not have time to dig deep into that and we<00:02:52.860> have<00:02:53.130> a<00:02:54.950> yeah<00:02:55.950> I'll<00:02:56.160> talk<00:02:56.370> I'll<00:02:56.880> talk<00:02:57.090> like 00:02:57.500 --> 00:02:57.510 align:start position:0% we have a yeah I'll talk I'll talk like 00:02:57.510 --> 00:03:03.620 align:start position:0% we have a yeah I'll talk I'll talk like that<00:03:00.020> now<00:03:01.020> I<00:03:01.050> can<00:03:01.230> hear<00:03:01.350> myself<00:03:01.550> we<00:03:02.550> will<00:03:02.820> we 00:03:03.620 --> 00:03:03.630 align:start position:0% that now I can hear myself we will we 00:03:03.630 --> 00:03:07.220 align:start position:0% that now I can hear myself we will we have<00:03:03.780> a<00:03:04.700> modification<00:03:05.700> of<00:03:06.150> the<00:03:06.300> FFG<00:03:06.690> protocol 00:03:07.220 --> 00:03:07.230 align:start position:0% have a modification of the FFG protocol 00:03:07.230 --> 00:03:09.650 align:start position:0% have a modification of the FFG protocol in<00:03:07.440> a<00:03:07.530> paper<00:03:07.800> it<00:03:08.250> is<00:03:08.520> a<00:03:08.610> draft<00:03:08.880> I<00:03:09.180> really<00:03:09.540> wish 00:03:09.650 --> 00:03:09.660 align:start position:0% in a paper it is a draft I really wish 00:03:09.660 --> 00:03:11.270 align:start position:0% in a paper it is a draft I really wish it<00:03:09.780> was<00:03:09.870> gonna<00:03:09.960> be<00:03:10.110> done<00:03:10.260> by<00:03:10.620> today<00:03:10.830> it's<00:03:11.160> in 00:03:11.270 --> 00:03:11.280 align:start position:0% it was gonna be done by today it's in 00:03:11.280 --> 00:03:13.280 align:start position:0% it was gonna be done by today it's in last<00:03:11.550> round<00:03:11.880> of<00:03:12.030> edits<00:03:12.360> and<00:03:12.540> will<00:03:12.750> be<00:03:12.930> released 00:03:13.280 --> 00:03:13.290 align:start position:0% last round of edits and will be released 00:03:13.290 --> 00:03:16.520 align:start position:0% last round of edits and will be released on<00:03:13.440> archive<00:03:13.830> very<00:03:14.610> soon<00:03:15.330> so<00:03:16.050> hopefully<00:03:16.380> this 00:03:16.520 --> 00:03:16.530 align:start position:0% on archive very soon so hopefully this 00:03:16.530 --> 00:03:18.020 align:start position:0% on archive very soon so hopefully this will<00:03:16.650> help<00:03:16.920> you<00:03:17.040> read<00:03:17.310> that<00:03:17.460> paper<00:03:17.670> when<00:03:17.940> it 00:03:18.020 --> 00:03:18.030 align:start position:0% will help you read that paper when it 00:03:18.030 --> 00:03:21.590 align:start position:0% will help you read that paper when it comes<00:03:18.180> out<00:03:18.330> so<00:03:20.240> traditionally<00:03:21.240> when<00:03:21.360> we<00:03:21.480> think 00:03:21.590 --> 00:03:21.600 align:start position:0% comes out so traditionally when we think 00:03:21.600 --> 00:03:25.340 align:start position:0% comes out so traditionally when we think about<00:03:22.400> blockchain<00:03:23.400> protocols<00:03:24.230> we<00:03:25.230> think 00:03:25.340 --> 00:03:25.350 align:start position:0% about blockchain protocols we think 00:03:25.350 --> 00:03:27.830 align:start position:0% about blockchain protocols we think about<00:03:25.440> blocks<00:03:25.800> and<00:03:26.220> block<00:03:26.850> Heights<00:03:27.120> and<00:03:27.510> every 00:03:27.830 --> 00:03:27.840 align:start position:0% about blocks and block Heights and every 00:03:27.840 --> 00:03:29.000 align:start position:0% about blocks and block Heights and every block<00:03:28.020> you<00:03:28.200> build<00:03:28.350> on<00:03:28.410> top<00:03:28.590> of<00:03:28.650> another<00:03:28.770> block 00:03:29.000 --> 00:03:29.010 align:start position:0% block you build on top of another block 00:03:29.010 --> 00:03:30.949 align:start position:0% block you build on top of another block moves<00:03:29.489> us<00:03:29.610> into<00:03:29.760> another<00:03:29.940> block<00:03:30.209> height<00:03:30.420> the 00:03:30.949 --> 00:03:30.959 align:start position:0% moves us into another block height the 00:03:30.959 --> 00:03:33.790 align:start position:0% moves us into another block height the original<00:03:31.320> FFG<00:03:31.620> protocol<00:03:32.300> considered 00:03:33.790 --> 00:03:33.800 align:start position:0% original FFG protocol considered 00:03:33.800 --> 00:03:36.170 align:start position:0% original FFG protocol considered considered<00:03:34.800> block<00:03:35.070> Heights<00:03:35.340> and<00:03:35.610> actions 00:03:36.170 --> 00:03:36.180 align:start position:0% considered block Heights and actions 00:03:36.180 --> 00:03:38.060 align:start position:0% considered block Heights and actions that<00:03:36.300> validators<00:03:36.989> could<00:03:37.200> take<00:03:37.440> with<00:03:37.650> respect 00:03:38.060 --> 00:03:38.070 align:start position:0% that validators could take with respect 00:03:38.070 --> 00:03:40.280 align:start position:0% that validators could take with respect to<00:03:38.250> block<00:03:38.370> Heights<00:03:38.760> these<00:03:39.720> Heights<00:03:40.020> were 00:03:40.280 --> 00:03:40.290 align:start position:0% to block Heights these Heights were 00:03:40.290 --> 00:03:46.490 align:start position:0% to block Heights these Heights were divided<00:03:41.010> into<00:03:43.520> epochs<00:03:44.520> and<00:03:45.180> units<00:03:46.140> of<00:03:46.320> work 00:03:46.490 --> 00:03:46.500 align:start position:0% divided into epochs and units of work 00:03:46.500 --> 00:03:48.260 align:start position:0% divided into epochs and units of work would<00:03:46.680> be<00:03:46.770> done<00:03:46.800> per<00:03:47.310> Epoque<00:03:47.640> so<00:03:47.850> essentially 00:03:48.260 --> 00:03:48.270 align:start position:0% would be done per Epoque so essentially 00:03:48.270 --> 00:03:50.360 align:start position:0% would be done per Epoque so essentially a<00:03:48.300> round<00:03:48.630> of<00:03:48.870> voting<00:03:49.020> by<00:03:49.470> all<00:03:49.650> validators<00:03:50.190> can 00:03:50.360 --> 00:03:50.370 align:start position:0% a round of voting by all validators can 00:03:50.370 --> 00:03:53.030 align:start position:0% a round of voting by all validators can happen<00:03:50.730> per<00:03:51.209> a<00:03:51.330> PUC<00:03:51.540> what<00:03:52.020> you<00:03:52.140> can<00:03:52.350> do<00:03:52.590> and<00:03:53.010> not 00:03:53.030 --> 00:03:53.040 align:start position:0% happen per a PUC what you can do and not 00:03:53.040 --> 00:03:55.760 align:start position:0% happen per a PUC what you can do and not do<00:03:53.730> to<00:03:54.660> the<00:03:54.780> protocol<00:03:55.170> is<00:03:55.320> also<00:03:55.560> kind<00:03:55.739> of 00:03:55.760 --> 00:03:55.770 align:start position:0% do to the protocol is also kind of 00:03:55.770 --> 00:03:58.610 align:start position:0% do to the protocol is also kind of defined<00:03:56.100> within<00:03:56.280> these<00:03:57.030> epochs<00:03:57.440> we<00:03:58.440> have<00:03:58.590> a 00:03:58.610 --> 00:03:58.620 align:start position:0% defined within these epochs we have a 00:03:58.620 --> 00:04:02.030 align:start position:0% defined within these epochs we have a slight<00:03:59.040> modification<00:03:59.850> to<00:04:00.709> how<00:04:01.709> we<00:04:01.770> think 00:04:02.030 --> 00:04:02.040 align:start position:0% slight modification to how we think 00:04:02.040 --> 00:04:04.070 align:start position:0% slight modification to how we think about<00:04:02.310> a<00:04:02.340> chain<00:04:02.760> being<00:04:03.060> built<00:04:03.270> still<00:04:03.660> we<00:04:03.900> have 00:04:04.070 --> 00:04:04.080 align:start position:0% about a chain being built still we have 00:04:04.080 --> 00:04:06.740 align:start position:0% about a chain being built still we have blocks<00:04:04.380> linked<00:04:05.040> to<00:04:05.190> each<00:04:05.310> other<00:04:05.459> block<00:04:06.180> by 00:04:06.740 --> 00:04:06.750 align:start position:0% blocks linked to each other block by 00:04:06.750 --> 00:04:09.020 align:start position:0% blocks linked to each other block by block<00:04:06.959> building<00:04:07.739> a<00:04:07.800> block<00:04:08.010> chain<00:04:08.250> but<00:04:08.820> we<00:04:08.910> have 00:04:09.020 --> 00:04:09.030 align:start position:0% block building a block chain but we have 00:04:09.030 --> 00:04:11.900 align:start position:0% block building a block chain but we have this<00:04:09.150> notion<00:04:09.540> of<00:04:09.930> of<00:04:10.470> time<00:04:10.980> called<00:04:11.520> a<00:04:11.610> slot 00:04:11.900 --> 00:04:11.910 align:start position:0% this notion of of time called a slot 00:04:11.910 --> 00:04:14.780 align:start position:0% this notion of of time called a slot also<00:04:12.660> embedded<00:04:13.290> into<00:04:13.620> this<00:04:13.769> kind<00:04:14.250> of<00:04:14.280> overlaid 00:04:14.780 --> 00:04:14.790 align:start position:0% also embedded into this kind of overlaid 00:04:14.790 --> 00:04:21.999 align:start position:0% also embedded into this kind of overlaid on<00:04:15.030> this<00:04:15.269> structure<00:04:15.600> and<00:04:15.989> so<00:04:18.769> what<00:04:19.769> we<00:04:19.950> can 00:04:21.999 --> 00:04:22.009 align:start position:0% on this structure and so what we can 00:04:22.009 --> 00:04:25.850 align:start position:0% on this structure and so what we can what<00:04:23.009> can<00:04:23.610> or<00:04:23.819> cannot<00:04:24.210> be<00:04:24.270> done<00:04:24.479> by<00:04:25.199> a<00:04:25.229> by<00:04:25.830> a 00:04:25.850 --> 00:04:25.860 align:start position:0% what can or cannot be done by a by a 00:04:25.860 --> 00:04:27.950 align:start position:0% what can or cannot be done by a by a validator<00:04:26.490> in<00:04:26.610> any<00:04:26.729> given<00:04:27.030> time<00:04:27.240> it<00:04:27.569> was<00:04:27.750> with 00:04:27.950 --> 00:04:27.960 align:start position:0% validator in any given time it was with 00:04:27.960 --> 00:04:31.490 align:start position:0% validator in any given time it was with respect<00:04:28.680> to<00:04:29.280> a<00:04:29.310> slot<00:04:29.759> so<00:04:29.969> my<00:04:30.120> duty<00:04:30.599> to<00:04:31.080> propose 00:04:31.490 --> 00:04:31.500 align:start position:0% respect to a slot so my duty to propose 00:04:31.500 --> 00:04:33.110 align:start position:0% respect to a slot so my duty to propose or<00:04:31.830> to<00:04:31.919> a<00:04:31.949> test<00:04:32.250> or<00:04:32.430> do<00:04:32.490> any<00:04:32.639> type<00:04:32.879> of<00:04:32.909> these 00:04:33.110 --> 00:04:33.120 align:start position:0% or to a test or do any type of these 00:04:33.120 --> 00:04:35.450 align:start position:0% or to a test or do any type of these messages<00:04:33.599> it's<00:04:34.020> with<00:04:34.199> respect<00:04:34.289> to<00:04:34.680> a<00:04:34.830> slot<00:04:35.189> and 00:04:35.450 --> 00:04:35.460 align:start position:0% messages it's with respect to a slot and 00:04:35.460 --> 00:04:38.450 align:start position:0% messages it's with respect to a slot and so<00:04:35.849> a<00:04:36.150> block<00:04:36.870> someone<00:04:37.590> someone<00:04:37.979> shows<00:04:38.129> up<00:04:38.159> and 00:04:38.450 --> 00:04:38.460 align:start position:0% so a block someone someone shows up and 00:04:38.460 --> 00:04:40.520 align:start position:0% so a block someone someone shows up and they<00:04:38.520> propose<00:04:38.849> this<00:04:39.150> at<00:04:39.360> slot<00:04:39.569> 0<00:04:39.840> this<00:04:40.169> is<00:04:40.319> slot 00:04:40.520 --> 00:04:40.530 align:start position:0% they propose this at slot 0 this is slot 00:04:40.530 --> 00:04:43.040 align:start position:0% they propose this at slot 0 this is slot 1<00:04:40.710> no<00:04:41.310> one<00:04:41.490> showed<00:04:41.729> up<00:04:41.759> at<00:04:42.000> slot<00:04:42.180> 2<00:04:42.360> or<00:04:42.569> maybe<00:04:42.689> it 00:04:43.040 --> 00:04:43.050 align:start position:0% 1 no one showed up at slot 2 or maybe it 00:04:43.050 --> 00:04:44.689 align:start position:0% 1 no one showed up at slot 2 or maybe it didn't<00:04:43.289> get<00:04:43.349> propagated<00:04:43.889> the<00:04:43.949> network<00:04:44.219> and<00:04:44.400> so 00:04:44.689 --> 00:04:44.699 align:start position:0% didn't get propagated the network and so 00:04:44.699 --> 00:04:47.719 align:start position:0% didn't get propagated the network and so the<00:04:44.819> proposer<00:04:45.240> at<00:04:45.509> slot<00:04:45.719> 3<00:04:46.020> built<00:04:46.439> upon<00:04:46.770> slot<00:04:47.520> 2 00:04:47.719 --> 00:04:47.729 align:start position:0% the proposer at slot 3 built upon slot 2 00:04:47.729 --> 00:04:50.029 align:start position:0% the proposer at slot 3 built upon slot 2 but<00:04:48.330> the<00:04:48.479> the<00:04:48.810> state-transition<00:04:49.110> the 00:04:50.029 --> 00:04:50.039 align:start position:0% but the the state-transition the 00:04:50.039 --> 00:04:52.339 align:start position:0% but the the state-transition the internal<00:04:50.520> mechanics<00:04:50.669> of<00:04:51.270> the<00:04:51.900> consensus 00:04:52.339 --> 00:04:52.349 align:start position:0% internal mechanics of the consensus 00:04:52.349 --> 00:04:53.809 align:start position:0% internal mechanics of the consensus protocol<00:04:52.710> and<00:04:53.009> other<00:04:53.250> portions<00:04:53.520> of<00:04:53.729> the 00:04:53.809 --> 00:04:53.819 align:start position:0% protocol and other portions of the 00:04:53.819 --> 00:04:57.070 align:start position:0% protocol and other portions of the protocol<00:04:54.210> are<00:04:54.360> aware<00:04:54.900> of<00:04:54.960> this<00:04:55.319> skip<00:04:55.770> and<00:04:56.039> so 00:04:57.070 --> 00:04:57.080 align:start position:0% protocol are aware of this skip and so 00:04:57.080 --> 00:04:59.809 align:start position:0% protocol are aware of this skip and so instead<00:04:58.080> of<00:04:58.139> things<00:04:58.650> being<00:04:58.919> divided<00:04:59.340> and<00:04:59.639> to 00:04:59.809 --> 00:04:59.819 align:start position:0% instead of things being divided and to 00:04:59.819 --> 00:05:01.519 align:start position:0% instead of things being divided and to strictly<00:05:00.300> block<00:05:00.750> heights<00:05:01.080> because<00:05:01.289> this 00:05:01.519 --> 00:05:01.529 align:start position:0% strictly block heights because this 00:05:01.529 --> 00:05:02.719 align:start position:0% strictly block heights because this would<00:05:01.680> just<00:05:01.770> be<00:05:01.860> a<00:05:01.949> block<00:05:02.159> height<00:05:02.400> of<00:05:02.520> 3 00:05:02.719 --> 00:05:02.729 align:start position:0% would just be a block height of 3 00:05:02.729 --> 00:05:05.450 align:start position:0% would just be a block height of 3 although<00:05:03.169> much<00:05:04.169> more<00:05:04.469> has<00:05:04.710> transpired<00:05:05.189> with 00:05:05.450 --> 00:05:05.460 align:start position:0% although much more has transpired with 00:05:05.460 --> 00:05:07.580 align:start position:0% although much more has transpired with respect<00:05:05.819> to<00:05:05.969> the<00:05:06.090> the<00:05:06.120> duties<00:05:06.779> and<00:05:07.020> positions 00:05:07.580 --> 00:05:07.590 align:start position:0% respect to the the duties and positions 00:05:07.590 --> 00:05:10.850 align:start position:0% respect to the the duties and positions of<00:05:07.650> the<00:05:07.770> protocol<00:05:08.069> so<00:05:08.639> instead<00:05:09.199> a<00:05:10.199> pox<00:05:10.650> are 00:05:10.850 --> 00:05:10.860 align:start position:0% of the protocol so instead a pox are 00:05:10.860 --> 00:05:13.909 align:start position:0% of the protocol so instead a pox are divided<00:05:11.279> into<00:05:11.460> slots<00:05:11.870> slots<00:05:12.870> epochs<00:05:13.620> in 00:05:13.909 --> 00:05:13.919 align:start position:0% divided into slots slots epochs in 00:05:13.919 --> 00:05:15.950 align:start position:0% divided into slots slots epochs in actuality<00:05:14.610> or<00:05:14.969> on<00:05:15.060> the<00:05:15.120> order<00:05:15.330> of<00:05:15.360> like<00:05:15.509> 64 00:05:15.950 --> 00:05:15.960 align:start position:0% actuality or on the order of like 64 00:05:15.960 --> 00:05:18.890 align:start position:0% actuality or on the order of like 64 slots<00:05:16.199> this<00:05:16.740> is<00:05:16.919> just<00:05:17.129> illustrative<00:05:17.699> so<00:05:18.659> this 00:05:18.890 --> 00:05:18.900 align:start position:0% slots this is just illustrative so this 00:05:18.900 --> 00:05:21.350 align:start position:0% slots this is just illustrative so this consensus<00:05:19.379> protocol<00:05:19.770> needs<00:05:20.069> to<00:05:20.219> be<00:05:20.360> modified 00:05:21.350 --> 00:05:21.360 align:start position:0% consensus protocol needs to be modified 00:05:21.360 --> 00:05:23.749 align:start position:0% consensus protocol needs to be modified FFG<00:05:22.169> needs<00:05:22.379> to<00:05:22.439> be<00:05:22.500> modified<00:05:22.740> to<00:05:23.039> work<00:05:23.219> on<00:05:23.460> top 00:05:23.749 --> 00:05:23.759 align:start position:0% FFG needs to be modified to work on top 00:05:23.759 --> 00:05:27.559 align:start position:0% FFG needs to be modified to work on top of<00:05:24.020> this<00:05:25.020> new<00:05:25.589> kind<00:05:26.009> of<00:05:26.069> slot<00:05:26.400> and<00:05:26.669> epoch 00:05:27.559 --> 00:05:27.569 align:start position:0% of this new kind of slot and epoch 00:05:27.569 --> 00:05:33.290 align:start position:0% of this new kind of slot and epoch mechanism<00:05:30.919> checkpoints<00:05:31.919> so<00:05:32.279> in<00:05:32.610> Kasparov<00:05:33.180> oh 00:05:33.290 --> 00:05:33.300 align:start position:0% mechanism checkpoints so in Kasparov oh 00:05:33.300 --> 00:05:35.659 align:start position:0% mechanism checkpoints so in Kasparov oh gee<00:05:33.479> we<00:05:33.750> checkpoint<00:05:34.289> we<00:05:34.500> attempt<00:05:34.830> to<00:05:34.949> finalize 00:05:35.659 --> 00:05:35.669 align:start position:0% gee we checkpoint we attempt to finalize 00:05:35.669 --> 00:05:41.409 align:start position:0% gee we checkpoint we attempt to finalize checkpoints<00:05:36.240> checkpoints<00:05:36.750> are<00:05:37.310> blocks<00:05:38.310> at 00:05:41.409 --> 00:05:41.419 align:start position:0% 00:05:41.419 --> 00:05:45.439 align:start position:0% per<00:05:42.419> units<00:05:42.779> of<00:05:42.900> time<00:05:43.580> here<00:05:44.580> checkpoint<00:05:45.240> might 00:05:45.439 --> 00:05:45.449 align:start position:0% per units of time here checkpoint might 00:05:45.449 --> 00:05:47.809 align:start position:0% per units of time here checkpoint might be<00:05:45.629> this<00:05:46.139> block<00:05:46.379> whereas<00:05:47.009> there<00:05:47.190> may<00:05:47.400> be<00:05:47.430> might 00:05:47.809 --> 00:05:47.819 align:start position:0% be this block whereas there may be might 00:05:47.819 --> 00:05:51.409 align:start position:0% be this block whereas there may be might that<00:05:48.060> but<00:05:49.020> importantly<00:05:50.029> because<00:05:51.029> we<00:05:51.240> have 00:05:51.409 --> 00:05:51.419 align:start position:0% that but importantly because we have 00:05:51.419 --> 00:05:54.439 align:start position:0% that but importantly because we have this<00:05:51.539> notion<00:05:51.810> of<00:05:52.110> skipped<00:05:52.650> slots<00:05:53.159> we<00:05:54.120> have<00:05:54.300> to 00:05:54.439 --> 00:05:54.449 align:start position:0% this notion of skipped slots we have to 00:05:54.449 --> 00:05:56.869 align:start position:0% this notion of skipped slots we have to define<00:05:54.779> what<00:05:55.139> actually<00:05:55.770> a<00:05:55.800> block<00:05:56.159> being<00:05:56.520> at<00:05:56.849> a 00:05:56.869 --> 00:05:56.879 align:start position:0% define what actually a block being at a 00:05:56.879 --> 00:06:00.740 align:start position:0% define what actually a block being at a checkpoint<00:05:57.240> is<00:05:57.689> and<00:05:58.199> means<00:05:58.439> and<00:05:58.710> so<00:05:59.509> we<00:06:00.509> call 00:06:00.740 --> 00:06:00.750 align:start position:0% checkpoint is and means and so we call 00:06:00.750 --> 00:06:02.629 align:start position:0% checkpoint is and means and so we call it<00:06:00.900> in<00:06:01.439> the<00:06:01.589> in<00:06:01.710> this<00:06:01.860> paper<00:06:02.099> coming<00:06:02.370> out<00:06:02.490> it's 00:06:02.629 --> 00:06:02.639 align:start position:0% it in the in this paper coming out it's 00:06:02.639 --> 00:06:05.450 align:start position:0% it in the in this paper coming out it's called<00:06:02.699> an<00:06:02.819> epoch<00:06:03.089> boundary<00:06:03.479> block<00:06:03.659> EB<00:06:04.050> B<00:06:04.460> so 00:06:05.450 --> 00:06:05.460 align:start position:0% called an epoch boundary block EB B so 00:06:05.460 --> 00:06:07.820 align:start position:0% called an epoch boundary block EB B so in<00:06:05.580> this<00:06:05.699> Fork<00:06:06.029> of<00:06:06.120> the<00:06:06.240> chain<00:06:06.449> we<00:06:07.110> have<00:06:07.349> the 00:06:07.820 --> 00:06:07.830 align:start position:0% in this Fork of the chain we have the 00:06:07.830 --> 00:06:09.379 align:start position:0% in this Fork of the chain we have the epoch<00:06:08.099> boundary<00:06:08.460> block<00:06:08.610> which<00:06:08.789> is<00:06:08.939> the<00:06:09.089> 0th 00:06:09.379 --> 00:06:09.389 align:start position:0% epoch boundary block which is the 0th 00:06:09.389 --> 00:06:12.829 align:start position:0% epoch boundary block which is the 0th block<00:06:09.689> in<00:06:09.930> that<00:06:10.080> epoch<00:06:10.409> is<00:06:10.620> actually<00:06:11.250> B<00:06:11.599> but<00:06:12.599> in 00:06:12.829 --> 00:06:12.839 align:start position:0% block in that epoch is actually B but in 00:06:12.839 --> 00:06:15.829 align:start position:0% block in that epoch is actually B but in this<00:06:13.379> Fork<00:06:13.770> of<00:06:13.860> the<00:06:13.919> chain<00:06:14.189> where<00:06:14.490> a<00:06:14.699> slot<00:06:15.569> at 00:06:15.829 --> 00:06:15.839 align:start position:0% this Fork of the chain where a slot at 00:06:15.839 --> 00:06:20.240 align:start position:0% this Fork of the chain where a slot at slot<00:06:16.199> 66<00:06:16.830> was<00:06:17.250> built<00:06:17.550> on<00:06:17.699> top<00:06:17.789> of<00:06:18.180> a<00:06:18.889> the<00:06:19.889> epoch 00:06:20.240 --> 00:06:20.250 align:start position:0% slot 66 was built on top of a the epoch 00:06:20.250 --> 00:06:22.159 align:start position:0% slot 66 was built on top of a the epoch boundary<00:06:20.669> block<00:06:20.849> is<00:06:21.029> actually<00:06:21.210> it's<00:06:21.750> the 00:06:22.159 --> 00:06:22.169 align:start position:0% boundary block is actually it's the 00:06:22.169 --> 00:06:25.790 align:start position:0% boundary block is actually it's the block<00:06:23.129> at<00:06:23.430> the<00:06:24.150> zeroth<00:06:24.810> slot<00:06:25.110> or<00:06:25.319> the<00:06:25.560> most 00:06:25.790 --> 00:06:25.800 align:start position:0% block at the zeroth slot or the most 00:06:25.800 --> 00:06:27.679 align:start position:0% block at the zeroth slot or the most immediate<00:06:26.370> block<00:06:26.639> prior<00:06:27.120> so<00:06:27.389> it's<00:06:27.509> actually 00:06:27.679 --> 00:06:27.689 align:start position:0% immediate block prior so it's actually 00:06:27.689 --> 00:06:31.219 align:start position:0% immediate block prior so it's actually it's<00:06:28.500> actually<00:06:28.680> a<00:06:28.889> so<00:06:29.639> in<00:06:30.089> this<00:06:30.539> version<00:06:30.930> of 00:06:31.219 --> 00:06:31.229 align:start position:0% it's actually a so in this version of 00:06:31.229 --> 00:06:33.639 align:start position:0% it's actually a so in this version of the<00:06:31.349> chain<00:06:31.649> this<00:06:32.550> fork<00:06:32.909> of<00:06:33.029> the<00:06:33.060> chain<00:06:33.360> if 00:06:33.639 --> 00:06:33.649 align:start position:0% the chain this fork of the chain if 00:06:33.649 --> 00:06:34.810 align:start position:0% the chain this fork of the chain if votes 00:06:34.810 --> 00:06:34.820 align:start position:0% votes 00:06:34.820 --> 00:06:36.670 align:start position:0% votes happening<00:06:35.270> and<00:06:35.510> blocks<00:06:35.780> are<00:06:35.930> justified<00:06:36.470> if 00:06:36.670 --> 00:06:36.680 align:start position:0% happening and blocks are justified if 00:06:36.680 --> 00:06:38.440 align:start position:0% happening and blocks are justified if something<00:06:36.950> was<00:06:37.070> was<00:06:37.490> check<00:06:37.850> pointed<00:06:38.270> or 00:06:38.440 --> 00:06:38.450 align:start position:0% something was was check pointed or 00:06:38.450 --> 00:06:44.440 align:start position:0% something was was check pointed or finalized<00:06:39.340> it<00:06:40.340> would<00:06:40.490> actually<00:06:40.670> be<00:06:41.090> a<00:06:42.880> at<00:06:43.880> this 00:06:44.440 --> 00:06:44.450 align:start position:0% finalized it would actually be a at this 00:06:44.450 --> 00:06:46.930 align:start position:0% finalized it would actually be a at this slot<00:06:44.840> because<00:06:45.500> a<00:06:45.710> can<00:06:46.370> be<00:06:46.460> transitioned 00:06:46.930 --> 00:06:46.940 align:start position:0% slot because a can be transitioned 00:06:46.940 --> 00:06:50.980 align:start position:0% slot because a can be transitioned through<00:06:47.450> empty<00:06:47.870> slots<00:06:48.460> up<00:06:49.460> until<00:06:50.150> B<00:06:50.420> exists 00:06:50.980 --> 00:06:50.990 align:start position:0% through empty slots up until B exists 00:06:50.990 --> 00:06:53.770 align:start position:0% through empty slots up until B exists you're<00:06:51.350> actually<00:06:52.030> check<00:06:53.030> pointing<00:06:53.510> and 00:06:53.770 --> 00:06:53.780 align:start position:0% you're actually check pointing and 00:06:53.780 --> 00:06:57.420 align:start position:0% you're actually check pointing and ultimately<00:06:54.290> finalizing<00:06:55.040> this<00:06:55.160> tuple<00:06:55.610> of<00:06:55.880> a<00:06:56.090> at 00:06:57.420 --> 00:06:57.430 align:start position:0% ultimately finalizing this tuple of a at 00:06:57.430 --> 00:07:03.490 align:start position:0% ultimately finalizing this tuple of a at the<00:06:58.430> start<00:06:58.760> of<00:06:58.940> this<00:06:59.240> slot<00:07:02.050> to<00:07:03.050> illustrate 00:07:03.490 --> 00:07:03.500 align:start position:0% the start of this slot to illustrate 00:07:03.500 --> 00:07:04.510 align:start position:0% the start of this slot to illustrate that<00:07:03.620> a<00:07:03.680> little<00:07:03.860> bit<00:07:03.950> more<00:07:04.100> what<00:07:04.310> I<00:07:04.340> was 00:07:04.510 --> 00:07:04.520 align:start position:0% that a little bit more what I was 00:07:04.520 --> 00:07:05.830 align:start position:0% that a little bit more what I was implying<00:07:04.760> is<00:07:04.940> we<00:07:05.060> have<00:07:05.180> this<00:07:05.300> notion<00:07:05.660> of 00:07:05.830 --> 00:07:05.840 align:start position:0% implying is we have this notion of 00:07:05.840 --> 00:07:08.410 align:start position:0% implying is we have this notion of paired<00:07:06.280> justification<00:07:07.280> impaired<00:07:07.820> finality 00:07:08.410 --> 00:07:08.420 align:start position:0% paired justification impaired finality 00:07:08.420 --> 00:07:11.760 align:start position:0% paired justification impaired finality in<00:07:09.050> the<00:07:09.380> optimal<00:07:09.980> case<00:07:10.250> we're<00:07:10.880> always<00:07:11.270> just 00:07:11.760 --> 00:07:11.770 align:start position:0% in the optimal case we're always just 00:07:11.770 --> 00:07:16.930 align:start position:0% in the optimal case we're always just say<00:07:12.770> justifying<00:07:13.640> the<00:07:13.940> 0th<00:07:15.070> in<00:07:16.070> the<00:07:16.550> optimal 00:07:16.930 --> 00:07:16.940 align:start position:0% say justifying the 0th in the optimal 00:07:16.940 --> 00:07:19.210 align:start position:0% say justifying the 0th in the optimal case<00:07:17.150> we're<00:07:17.660> always<00:07:17.810> justifying<00:07:18.650> and<00:07:18.860> final 00:07:19.210 --> 00:07:19.220 align:start position:0% case we're always justifying and final 00:07:19.220 --> 00:07:21.460 align:start position:0% case we're always justifying and final exams<00:07:19.630> exists<00:07:20.630> at<00:07:20.720> all<00:07:20.810> slots<00:07:21.080> then<00:07:21.290> we<00:07:21.350> can 00:07:21.460 --> 00:07:21.470 align:start position:0% exams exists at all slots then we can 00:07:21.470 --> 00:07:24.070 align:start position:0% exams exists at all slots then we can just<00:07:21.620> always<00:07:21.800> justify<00:07:22.340> the<00:07:22.400> 0th<00:07:22.820> one<00:07:23.060> here<00:07:23.570> but 00:07:24.070 --> 00:07:24.080 align:start position:0% just always justify the 0th one here but 00:07:24.080 --> 00:07:26.260 align:start position:0% just always justify the 0th one here but instead<00:07:24.320> because<00:07:24.980> we<00:07:25.130> we<00:07:25.430> can<00:07:25.790> have<00:07:26.030> drop 00:07:26.260 --> 00:07:26.270 align:start position:0% instead because we we can have drop 00:07:26.270 --> 00:07:27.610 align:start position:0% instead because we we can have drop slots<00:07:26.600> and<00:07:26.720> skip<00:07:26.900> slots<00:07:27.140> we<00:07:27.260> have<00:07:27.410> to<00:07:27.470> have<00:07:27.560> a 00:07:27.610 --> 00:07:27.620 align:start position:0% slots and skip slots we have to have a 00:07:27.620 --> 00:07:29.980 align:start position:0% slots and skip slots we have to have a notion<00:07:27.800> of<00:07:28.070> what<00:07:28.220> we're<00:07:28.370> actually<00:07:28.550> at<00:07:29.270> a<00:07:29.330> given 00:07:29.980 --> 00:07:29.990 align:start position:0% notion of what we're actually at a given 00:07:29.990 --> 00:07:31.750 align:start position:0% notion of what we're actually at a given a<00:07:30.140> PUC<00:07:30.350> what<00:07:30.590> we're<00:07:30.710> actually<00:07:30.890> finalizing<00:07:31.640> and 00:07:31.750 --> 00:07:31.760 align:start position:0% a PUC what we're actually finalizing and 00:07:31.760 --> 00:07:34.210 align:start position:0% a PUC what we're actually finalizing and it<00:07:31.970> turns<00:07:32.570> out<00:07:32.780> that<00:07:32.960> we're<00:07:33.110> we're<00:07:33.770> finalizing 00:07:34.210 --> 00:07:34.220 align:start position:0% it turns out that we're we're finalizing 00:07:34.220 --> 00:07:36.310 align:start position:0% it turns out that we're we're finalizing this<00:07:34.520> notion<00:07:34.730> of<00:07:34.940> a<00:07:35.030> paired<00:07:35.360> justification<00:07:36.170> of 00:07:36.310 --> 00:07:36.320 align:start position:0% this notion of a paired justification of 00:07:36.320 --> 00:07:39.850 align:start position:0% this notion of a paired justification of a<00:07:36.740> block<00:07:37.460> at<00:07:37.820> an<00:07:38.300> epoch<00:07:38.720> so<00:07:39.080> just<00:07:39.770> to 00:07:39.850 --> 00:07:39.860 align:start position:0% a block at an epoch so just to 00:07:39.860 --> 00:07:42.040 align:start position:0% a block at an epoch so just to illustrate<00:07:39.980> that<00:07:40.370> a<00:07:40.400> little<00:07:40.610> bit<00:07:40.730> more<00:07:41.050> we 00:07:42.040 --> 00:07:42.050 align:start position:0% illustrate that a little bit more we 00:07:42.050 --> 00:07:44.350 align:start position:0% illustrate that a little bit more we have<00:07:42.080> a<00:07:42.290> block<00:07:42.590> at<00:07:42.890> epoch<00:07:43.340> one<00:07:43.550> the<00:07:44.030> zeroth 00:07:44.350 --> 00:07:44.360 align:start position:0% have a block at epoch one the zeroth 00:07:44.360 --> 00:07:47.950 align:start position:0% have a block at epoch one the zeroth slot<00:07:44.690> at<00:07:44.870> 64<00:07:45.550> but<00:07:46.550> then<00:07:46.700> a<00:07:46.940> nothing<00:07:47.630> happens 00:07:47.950 --> 00:07:47.960 align:start position:0% slot at 64 but then a nothing happens 00:07:47.960 --> 00:07:50.290 align:start position:0% slot at 64 but then a nothing happens like<00:07:48.170> some<00:07:48.380> everyone<00:07:48.890> goes<00:07:49.130> offline<00:07:49.460> or<00:07:49.880> some 00:07:50.290 --> 00:07:50.300 align:start position:0% like some everyone goes offline or some 00:07:50.300 --> 00:07:53.590 align:start position:0% like some everyone goes offline or some massive<00:07:50.750> forking<00:07:51.140> happens<00:07:51.470> and<00:07:52.090> the<00:07:53.090> proposer 00:07:53.590 --> 00:07:53.600 align:start position:0% massive forking happens and the proposer 00:07:53.600 --> 00:07:56.380 align:start position:0% massive forking happens and the proposer the<00:07:54.110> next<00:07:54.380> proposer<00:07:54.740> actually<00:07:55.550> in<00:07:55.760> epoch<00:07:56.150> - 00:07:56.380 --> 00:07:56.390 align:start position:0% the next proposer actually in epoch - 00:07:56.390 --> 00:08:01.480 align:start position:0% the next proposer actually in epoch - it's<00:07:56.600> la<00:07:56.780> 129<00:07:57.440> builds<00:07:58.400> on<00:07:58.550> top<00:07:58.850> of<00:07:59.270> this<00:08:00.230> 64<00:08:01.160> and 00:08:01.480 --> 00:08:01.490 align:start position:0% it's la 129 builds on top of this 64 and 00:08:01.490 --> 00:08:06.730 align:start position:0% it's la 129 builds on top of this 64 and so<00:08:02.890> and<00:08:03.890> we<00:08:04.880> go<00:08:05.090> on<00:08:05.330> in<00:08:05.690> this<00:08:05.870> epoch<00:08:06.260> to<00:08:06.530> to 00:08:06.730 --> 00:08:06.740 align:start position:0% so and we go on in this epoch to to 00:08:06.740 --> 00:08:10.030 align:start position:0% so and we go on in this epoch to to actually<00:08:06.920> justify<00:08:08.080> this<00:08:09.080> epoch<00:08:09.530> boundary 00:08:10.030 --> 00:08:10.040 align:start position:0% actually justify this epoch boundary 00:08:10.040 --> 00:08:12.490 align:start position:0% actually justify this epoch boundary which<00:08:10.490> ended<00:08:10.880> up<00:08:10.970> being<00:08:11.030> a<00:08:11.480> block<00:08:12.110> from<00:08:12.380> a 00:08:12.490 --> 00:08:12.500 align:start position:0% which ended up being a block from a 00:08:12.500 --> 00:08:15.580 align:start position:0% which ended up being a block from a prior<00:08:12.800> epoch<00:08:13.250> but<00:08:13.460> at<00:08:13.670> this<00:08:14.570> slot<00:08:14.870> and<00:08:15.230> so<00:08:15.440> then 00:08:15.580 --> 00:08:15.590 align:start position:0% prior epoch but at this slot and so then 00:08:15.590 --> 00:08:16.690 align:start position:0% prior epoch but at this slot and so then we<00:08:15.680> can<00:08:15.770> go<00:08:15.920> on<00:08:15.950> to<00:08:16.250> do<00:08:16.520> further 00:08:16.690 --> 00:08:16.700 align:start position:0% we can go on to do further 00:08:16.700 --> 00:08:18.250 align:start position:0% we can go on to do further justifications<00:08:17.360> and<00:08:17.510> actually<00:08:17.750> finalize 00:08:18.250 --> 00:08:18.260 align:start position:0% justifications and actually finalize 00:08:18.260 --> 00:08:20.950 align:start position:0% justifications and actually finalize this<00:08:18.500> and<00:08:18.740> so<00:08:19.250> what<00:08:19.400> that<00:08:19.520> does<00:08:19.700> is<00:08:19.960> finality 00:08:20.950 --> 00:08:20.960 align:start position:0% this and so what that does is finality 00:08:20.960 --> 00:08:25.030 align:start position:0% this and so what that does is finality in<00:08:21.080> this<00:08:21.230> mechanism<00:08:21.590> ends<00:08:22.310> up<00:08:22.400> being<00:08:23.980> not<00:08:24.980> only 00:08:25.030 --> 00:08:25.040 align:start position:0% in this mechanism ends up being not only 00:08:25.040 --> 00:08:28.660 align:start position:0% in this mechanism ends up being not only will<00:08:25.910> this<00:08:26.120> block<00:08:26.900> say<00:08:27.650> this<00:08:27.860> block<00:08:28.040> is<00:08:28.250> at 00:08:28.660 --> 00:08:28.670 align:start position:0% will this block say this block is at 00:08:28.670 --> 00:08:31.120 align:start position:0% will this block say this block is at this<00:08:28.910> epoch<00:08:29.450> is<00:08:29.600> finalized<00:08:30.110> not<00:08:30.620> only<00:08:30.950> will 00:08:31.120 --> 00:08:31.130 align:start position:0% this epoch is finalized not only will 00:08:31.130 --> 00:08:35.770 align:start position:0% this epoch is finalized not only will this<00:08:31.250> block<00:08:31.550> never<00:08:32.479> revert<00:08:32.930> but<00:08:34.210> blocks<00:08:35.210> that 00:08:35.770 --> 00:08:35.780 align:start position:0% this block never revert but blocks that 00:08:35.780 --> 00:08:39.339 align:start position:0% this block never revert but blocks that are<00:08:36.050> lower<00:08:36.950> than<00:08:37.400> this<00:08:37.700> epoch<00:08:38.450> boundary<00:08:39.020> slot 00:08:39.339 --> 00:08:39.349 align:start position:0% are lower than this epoch boundary slot 00:08:39.349 --> 00:08:42.100 align:start position:0% are lower than this epoch boundary slot can<00:08:40.010> also<00:08:40.219> but<00:08:40.789> built<00:08:41.090> upon<00:08:41.419> this<00:08:41.599> can<00:08:41.840> also 00:08:42.100 --> 00:08:42.110 align:start position:0% can also but built upon this can also 00:08:42.110 --> 00:08:45.250 align:start position:0% can also but built upon this can also are<00:08:42.770> also<00:08:43.040> not<00:08:43.310> valid<00:08:43.669> so<00:08:44.090> for<00:08:44.420> example<00:08:44.840> if 00:08:45.250 --> 00:08:45.260 align:start position:0% are also not valid so for example if 00:08:45.260 --> 00:08:47.650 align:start position:0% are also not valid so for example if someone<00:08:45.590> built<00:08:45.830> a<00:08:46.400> block<00:08:47.030> right<00:08:47.300> here<00:08:47.510> it's 00:08:47.650 --> 00:08:47.660 align:start position:0% someone built a block right here it's 00:08:47.660 --> 00:08:48.560 align:start position:0% someone built a block right here it's lost<00:08:47.870> 65 00:08:48.560 --> 00:08:48.570 align:start position:0% lost 65 00:08:48.570 --> 00:08:51.170 align:start position:0% lost 65 cc6<00:08:49.050> but<00:08:49.860> this<00:08:50.070> was<00:08:50.310> finalized<00:08:50.820> those<00:08:51.030> are 00:08:51.170 --> 00:08:51.180 align:start position:0% cc6 but this was finalized those are 00:08:51.180 --> 00:08:52.520 align:start position:0% cc6 but this was finalized those are those<00:08:51.360> are<00:08:51.420> considered<00:08:51.870> invalid<00:08:52.080> and<00:08:52.410> I<00:08:52.470> don't 00:08:52.520 --> 00:08:52.530 align:start position:0% those are considered invalid and I don't 00:08:52.530 --> 00:08:54.500 align:start position:0% those are considered invalid and I don't consider<00:08:52.950> them<00:08:53.310> a<00:08:53.370> part<00:08:53.670> of<00:08:53.730> my<00:08:53.850> fork<00:08:54.060> choice 00:08:54.500 --> 00:08:54.510 align:start position:0% consider them a part of my fork choice 00:08:54.510 --> 00:08:57.620 align:start position:0% consider them a part of my fork choice so<00:08:54.870> we<00:08:55.020> have<00:08:55.170> this<00:08:55.320> this<00:08:55.590> notion<00:08:55.860> of<00:08:56.630> coupling 00:08:57.620 --> 00:08:57.630 align:start position:0% so we have this this notion of coupling 00:08:57.630 --> 00:08:59.810 align:start position:0% so we have this this notion of coupling blocks<00:08:57.990> with<00:08:58.530> an<00:08:58.650> epoch<00:08:58.980> in<00:08:59.280> finality 00:08:59.810 --> 00:08:59.820 align:start position:0% blocks with an epoch in finality 00:08:59.820 --> 00:09:01.900 align:start position:0% blocks with an epoch in finality [Music] 00:09:01.900 --> 00:09:01.910 align:start position:0% [Music] 00:09:01.910 --> 00:09:06.260 align:start position:0% [Music] so<00:09:03.410> justification<00:09:04.410> rules<00:09:05.150> similarly<00:09:06.150> to 00:09:06.260 --> 00:09:06.270 align:start position:0% so justification rules similarly to 00:09:06.270 --> 00:09:09.050 align:start position:0% so justification rules similarly to Caspar<00:09:06.990> FFG<00:09:07.380> the<00:09:07.530> original<00:09:07.830> protocol<00:09:08.220> the 00:09:09.050 --> 00:09:09.060 align:start position:0% Caspar FFG the original protocol the 00:09:09.060 --> 00:09:13.220 align:start position:0% Caspar FFG the original protocol the genesis<00:09:09.750> block<00:09:10.220> at<00:09:11.220> epoch<00:09:11.700> zero<00:09:12.000> is<00:09:12.300> justified 00:09:13.220 --> 00:09:13.230 align:start position:0% genesis block at epoch zero is justified 00:09:13.230 --> 00:09:16.040 align:start position:0% genesis block at epoch zero is justified and<00:09:13.790> subsequently<00:09:14.790> we<00:09:15.150> have<00:09:15.300> justified<00:09:15.840> and 00:09:16.040 --> 00:09:16.050 align:start position:0% and subsequently we have justified and 00:09:16.050 --> 00:09:17.750 align:start position:0% and subsequently we have justified and again<00:09:16.740> we<00:09:16.830> have<00:09:16.920> these<00:09:17.010> pairs<00:09:17.310> these<00:09:17.520> block 00:09:17.750 --> 00:09:17.760 align:start position:0% again we have these pairs these block 00:09:17.760 --> 00:09:24.560 align:start position:0% again we have these pairs these block epoch<00:09:18.300> pairs<00:09:19.220> any<00:09:22.070> justification<00:09:23.070> pair<00:09:23.570> from 00:09:24.560 --> 00:09:24.570 align:start position:0% epoch pairs any justification pair from 00:09:24.570 --> 00:09:27.170 align:start position:0% epoch pairs any justification pair from a<00:09:24.930> source<00:09:25.530> of<00:09:25.830> a<00:09:25.980> prior<00:09:26.190> justification<00:09:26.970> pair 00:09:27.170 --> 00:09:27.180 align:start position:0% a source of a prior justification pair 00:09:27.180 --> 00:09:31.490 align:start position:0% a source of a prior justification pair is<00:09:27.390> justified<00:09:28.140> and<00:09:29.100> when<00:09:30.090> votes<00:09:30.510> are<00:09:30.810> cast 00:09:31.490 --> 00:09:31.500 align:start position:0% is justified and when votes are cast 00:09:31.500 --> 00:09:36.500 align:start position:0% is justified and when votes are cast we're<00:09:32.220> always<00:09:32.370> specifying<00:09:33.000> a<00:09:34.340> source<00:09:35.340> and<00:09:35.760> a 00:09:36.500 --> 00:09:36.510 align:start position:0% we're always specifying a source and a 00:09:36.510 --> 00:09:39.320 align:start position:0% we're always specifying a source and a target<00:09:36.870> so<00:09:36.990> here<00:09:37.350> in<00:09:37.650> this<00:09:38.160> link<00:09:38.910> that<00:09:39.210> was 00:09:39.320 --> 00:09:39.330 align:start position:0% target so here in this link that was 00:09:39.330 --> 00:09:43.130 align:start position:0% target so here in this link that was created<00:09:39.860> this<00:09:40.860> prior<00:09:41.220> justification<00:09:42.030> was<00:09:42.810> the 00:09:43.130 --> 00:09:43.140 align:start position:0% created this prior justification was the 00:09:43.140 --> 00:09:46.280 align:start position:0% created this prior justification was the source<00:09:43.380> and<00:09:43.680> this<00:09:44.430> new<00:09:44.550> one<00:09:44.670> is<00:09:44.820> the<00:09:44.850> target<00:09:45.290> so 00:09:46.280 --> 00:09:46.290 align:start position:0% source and this new one is the target so 00:09:46.290 --> 00:09:51.050 align:start position:0% source and this new one is the target so we<00:09:46.590> create<00:09:47.250> a<00:09:48.260> justified<00:09:49.400> link<00:09:50.400> I<00:09:50.670> think<00:09:50.790> it's 00:09:51.050 --> 00:09:51.060 align:start position:0% we create a justified link I think it's 00:09:51.060 --> 00:09:54.830 align:start position:0% we create a justified link I think it's called<00:09:51.210> a<00:09:51.300> supermajority<00:09:51.900> link<00:09:53.660> to<00:09:54.660> create 00:09:54.830 --> 00:09:54.840 align:start position:0% called a supermajority link to create 00:09:54.840 --> 00:09:56.360 align:start position:0% called a supermajority link to create these<00:09:55.110> just<00:09:55.440> this<00:09:55.650> chain<00:09:55.890> of<00:09:55.920> justified 00:09:56.360 --> 00:09:56.370 align:start position:0% these just this chain of justified 00:09:56.370 --> 00:09:58.130 align:start position:0% these just this chain of justified blocks<00:09:56.640> and<00:09:56.880> a<00:09:57.030> subset<00:09:57.480> of<00:09:57.510> them<00:09:57.630> depending<00:09:58.080> on 00:09:58.130 --> 00:09:58.140 align:start position:0% blocks and a subset of them depending on 00:09:58.140 --> 00:10:02.840 align:start position:0% blocks and a subset of them depending on the<00:09:58.260> rules<00:09:58.470> can<00:09:58.740> be<00:09:58.800> finalized<00:10:00.800> so<00:10:01.850> finality 00:10:02.840 --> 00:10:02.850 align:start position:0% the rules can be finalized so finality 00:10:02.850 --> 00:10:05.120 align:start position:0% the rules can be finalized so finality rules<00:10:03.090> I<00:10:03.360> know<00:10:04.170> this<00:10:04.320> isn't<00:10:04.620> actually<00:10:04.710> super 00:10:05.120 --> 00:10:05.130 align:start position:0% rules I know this isn't actually super 00:10:05.130 --> 00:10:07.780 align:start position:0% rules I know this isn't actually super meaningful<00:10:05.310> this<00:10:05.910> is<00:10:06.090> taken<00:10:06.420> from<00:10:06.480> the<00:10:06.630> paper 00:10:07.780 --> 00:10:07.790 align:start position:0% meaningful this is taken from the paper 00:10:07.790 --> 00:10:10.400 align:start position:0% meaningful this is taken from the paper the<00:10:08.790> finality<00:10:09.150> rules<00:10:09.450> in<00:10:09.750> the<00:10:09.930> original<00:10:10.230> cast 00:10:10.400 --> 00:10:10.410 align:start position:0% the finality rules in the original cast 00:10:10.410 --> 00:10:12.260 align:start position:0% the finality rules in the original cast ref<00:10:10.710> of<00:10:10.800> G<00:10:10.920> paper<00:10:11.130> were<00:10:11.430> essentially<00:10:12.060> you<00:10:12.150> had 00:10:12.260 --> 00:10:12.270 align:start position:0% ref of G paper were essentially you had 00:10:12.270 --> 00:10:14.810 align:start position:0% ref of G paper were essentially you had to<00:10:12.360> have<00:10:12.480> to<00:10:12.870> epochs<00:10:13.800> that<00:10:14.130> were<00:10:14.220> sequentially 00:10:14.810 --> 00:10:14.820 align:start position:0% to have to epochs that were sequentially 00:10:14.820 --> 00:10:17.810 align:start position:0% to have to epochs that were sequentially justified<00:10:15.330> where<00:10:15.780> the<00:10:16.130> the<00:10:17.130> lower<00:10:17.340> of<00:10:17.640> those 00:10:17.810 --> 00:10:17.820 align:start position:0% justified where the the lower of those 00:10:17.820 --> 00:10:20.600 align:start position:0% justified where the the lower of those two<00:10:18.120> becomes<00:10:18.600> finalized<00:10:19.190> here<00:10:20.190> we<00:10:20.430> actually 00:10:20.600 --> 00:10:20.610 align:start position:0% two becomes finalized here we actually 00:10:20.610 --> 00:10:23.720 align:start position:0% two becomes finalized here we actually extend<00:10:21.270> the<00:10:21.450> finality<00:10:21.840> rules<00:10:22.340> to<00:10:23.340> be<00:10:23.460> a<00:10:23.490> little 00:10:23.720 --> 00:10:23.730 align:start position:0% extend the finality rules to be a little 00:10:23.730 --> 00:10:25.640 align:start position:0% extend the finality rules to be a little bit<00:10:23.880> include<00:10:24.600> a<00:10:24.720> little<00:10:24.870> bit<00:10:24.990> more<00:10:25.170> cases 00:10:25.640 --> 00:10:25.650 align:start position:0% bit include a little bit more cases 00:10:25.650 --> 00:10:30.260 align:start position:0% bit include a little bit more cases where<00:10:26.660> we<00:10:27.740> generalize<00:10:28.740> it<00:10:28.980> the<00:10:29.430> original<00:10:30.060> case 00:10:30.260 --> 00:10:30.270 align:start position:0% where we generalize it the original case 00:10:30.270 --> 00:10:31.880 align:start position:0% where we generalize it the original case that<00:10:30.540> I<00:10:30.570> just<00:10:30.780> described<00:10:31.170> is<00:10:31.350> called<00:10:31.560> the<00:10:31.650> K 00:10:31.880 --> 00:10:31.890 align:start position:0% that I just described is called the K 00:10:31.890 --> 00:10:33.560 align:start position:0% that I just described is called the K equals<00:10:32.340> one<00:10:32.550> case<00:10:32.850> where<00:10:33.360> we<00:10:33.540> are 00:10:33.560 --> 00:10:33.570 align:start position:0% equals one case where we are 00:10:33.570 --> 00:10:36.410 align:start position:0% equals one case where we are sequentially<00:10:34.380> justifying<00:10:34.920> but<00:10:35.730> we<00:10:36.090> can<00:10:36.240> we 00:10:36.410 --> 00:10:36.420 align:start position:0% sequentially justifying but we can we 00:10:36.420 --> 00:10:39.140 align:start position:0% sequentially justifying but we can we can<00:10:36.570> generalize<00:10:36.930> this<00:10:37.140> and<00:10:37.200> add<00:10:37.860> cases<00:10:38.490> to<00:10:38.970> the 00:10:39.140 --> 00:10:39.150 align:start position:0% can generalize this and add cases to the 00:10:39.150 --> 00:10:42.440 align:start position:0% can generalize this and add cases to the K<00:10:39.330> equals<00:10:39.690> n<00:10:39.870> such<00:10:40.500> that<00:10:40.530> the<00:10:41.490> rule<00:10:41.700> becomes<00:10:42.120> if 00:10:42.440 --> 00:10:42.450 align:start position:0% K equals n such that the rule becomes if 00:10:42.450 --> 00:10:47.510 align:start position:0% K equals n such that the rule becomes if we<00:10:42.930> have<00:10:43.170> a<00:10:43.730> justification<00:10:44.730> link<00:10:45.860> and<00:10:46.860> or 00:10:47.510 --> 00:10:47.520 align:start position:0% we have a justification link and or 00:10:47.520 --> 00:10:51.070 align:start position:0% we have a justification link and or here's<00:10:47.850> our<00:10:48.000> justification<00:10:48.240> link<00:10:48.720> but<00:10:49.230> all 00:10:51.070 --> 00:10:51.080 align:start position:0% here's our justification link but all 00:10:51.080 --> 00:10:53.900 align:start position:0% here's our justification link but all epochs<00:10:52.190> contained<00:10:53.190> within<00:10:53.460> that 00:10:53.900 --> 00:10:53.910 align:start position:0% epochs contained within that 00:10:53.910 --> 00:10:55.820 align:start position:0% epochs contained within that justification<00:10:54.360> link<00:10:54.780> are<00:10:54.900> also<00:10:55.110> justified 00:10:55.820 --> 00:10:55.830 align:start position:0% justification link are also justified 00:10:55.830 --> 00:10:58.100 align:start position:0% justification link are also justified then<00:10:56.370> we<00:10:56.490> can<00:10:56.640> finalize<00:10:57.090> the<00:10:57.420> source<00:10:57.660> of<00:10:57.930> this 00:10:58.100 --> 00:10:58.110 align:start position:0% then we can finalize the source of this 00:10:58.110 --> 00:11:01.319 align:start position:0% then we can finalize the source of this link<00:10:58.320> so<00:10:59.250> here<00:10:59.460> we<00:10:59.610> jump<00:10:59.850> to<00:11:00.060> but<00:11:00.300> we<00:11:00.420> justify 00:11:01.319 --> 00:11:01.329 align:start position:0% link so here we jump to but we justify 00:11:01.329 --> 00:11:03.900 align:start position:0% link so here we jump to but we justify the<00:11:01.420> center<00:11:01.720> so<00:11:01.959> we<00:11:02.079> can<00:11:02.199> finalize<00:11:02.619> here<00:11:03.189> here 00:11:03.900 --> 00:11:03.910 align:start position:0% the center so we can finalize here here 00:11:03.910 --> 00:11:08.160 align:start position:0% the center so we can finalize here here we<00:11:04.540> jump<00:11:04.809> over<00:11:04.989> over<00:11:06.179> three<00:11:07.179> but<00:11:07.720> we<00:11:07.839> had 00:11:08.160 --> 00:11:08.170 align:start position:0% we jump over over three but we had 00:11:08.170 --> 00:11:09.749 align:start position:0% we jump over over three but we had justifications<00:11:08.829> in<00:11:08.920> the<00:11:09.040> center<00:11:09.309> and<00:11:09.519> so<00:11:09.670> we 00:11:09.749 --> 00:11:09.759 align:start position:0% justifications in the center and so we 00:11:09.759 --> 00:11:12.419 align:start position:0% justifications in the center and so we can<00:11:09.879> finalize<00:11:10.299> the<00:11:10.929> base<00:11:11.110> and<00:11:11.410> the<00:11:11.889> intuition 00:11:12.419 --> 00:11:12.429 align:start position:0% can finalize the base and the intuition 00:11:12.429 --> 00:11:19.979 align:start position:0% can finalize the base and the intuition here<00:11:12.459> is<00:11:12.850> that<00:11:16.769> here<00:11:17.769> our<00:11:18.579> justification<00:11:19.389> and 00:11:19.979 --> 00:11:19.989 align:start position:0% here is that here our justification and 00:11:19.989 --> 00:11:23.039 align:start position:0% here is that here our justification and finality<00:11:20.290> here<00:11:20.529> is<00:11:20.709> we<00:11:21.459> can't<00:11:21.730> double<00:11:22.329> vote<00:11:22.540> to 00:11:23.039 --> 00:11:23.049 align:start position:0% finality here is we can't double vote to 00:11:23.049 --> 00:11:25.979 align:start position:0% finality here is we can't double vote to try<00:11:23.230> to<00:11:23.290> finalize<00:11:24.279> something<00:11:24.850> exactly<00:11:25.239> and<00:11:25.660> if 00:11:25.979 --> 00:11:25.989 align:start position:0% try to finalize something exactly and if 00:11:25.989 --> 00:11:29.669 align:start position:0% try to finalize something exactly and if we<00:11:26.139> wanted<00:11:26.559> to<00:11:27.839> essentially<00:11:28.839> like<00:11:29.110> skirt<00:11:29.499> the 00:11:29.669 --> 00:11:29.679 align:start position:0% we wanted to essentially like skirt the 00:11:29.679 --> 00:11:33.179 align:start position:0% we wanted to essentially like skirt the double<00:11:29.949> vote<00:11:30.069> and<00:11:30.309> and<00:11:30.519> jump<00:11:30.819> over<00:11:30.970> then<00:11:31.569> we<00:11:32.189> we 00:11:33.179 --> 00:11:33.189 align:start position:0% double vote and and jump over then we we 00:11:33.189 --> 00:11:35.489 align:start position:0% double vote and and jump over then we we we<00:11:33.519> can't<00:11:33.759> there's<00:11:34.449> an<00:11:34.600> and<00:11:35.139> I'll<00:11:35.230> get<00:11:35.379> to<00:11:35.410> that 00:11:35.489 --> 00:11:35.499 align:start position:0% we can't there's an and I'll get to that 00:11:35.499 --> 00:11:35.999 align:start position:0% we can't there's an and I'll get to that in<00:11:35.589> a<00:11:35.679> moment 00:11:35.999 --> 00:11:36.009 align:start position:0% in a moment 00:11:36.009 --> 00:11:40.289 align:start position:0% in a moment we<00:11:36.399> can't<00:11:37.559> surround<00:11:38.559> this<00:11:39.009> vote<00:11:39.730> to 00:11:40.289 --> 00:11:40.299 align:start position:0% we can't surround this vote to 00:11:40.299 --> 00:11:42.359 align:start position:0% we can't surround this vote to essentially<00:11:40.720> jump<00:11:40.959> over<00:11:41.230> and<00:11:41.410> here<00:11:41.949> we've 00:11:42.359 --> 00:11:42.369 align:start position:0% essentially jump over and here we've 00:11:42.369 --> 00:11:44.489 align:start position:0% essentially jump over and here we've like<00:11:42.519> plug<00:11:42.910> to<00:11:43.119> the<00:11:43.239> holes<00:11:43.480> so<00:11:44.170> we<00:11:44.199> have<00:11:44.470> a 00:11:44.489 --> 00:11:44.499 align:start position:0% like plug to the holes so we have a 00:11:44.499 --> 00:11:46.229 align:start position:0% like plug to the holes so we have a similar<00:11:45.069> mechanism<00:11:45.220> and<00:11:45.759> we've<00:11:45.879> plugged<00:11:46.059> the 00:11:46.229 --> 00:11:46.239 align:start position:0% similar mechanism and we've plugged the 00:11:46.239 --> 00:11:48.119 align:start position:0% similar mechanism and we've plugged the hole<00:11:46.389> and<00:11:46.660> then<00:11:46.749> now<00:11:47.139> we<00:11:47.769> just<00:11:47.920> need<00:11:48.069> to 00:11:48.119 --> 00:11:48.129 align:start position:0% hole and then now we just need to 00:11:48.129 --> 00:11:50.819 align:start position:0% hole and then now we just need to prevent<00:11:48.369> surrounds<00:11:48.910> to<00:11:49.119> avoid<00:11:49.779> that<00:11:49.989> finality 00:11:50.819 --> 00:11:50.829 align:start position:0% prevent surrounds to avoid that finality 00:11:50.829 --> 00:11:57.809 align:start position:0% prevent surrounds to avoid that finality issue<00:11:53.160> in<00:11:55.290> the<00:11:56.290> actual<00:11:56.649> e<00:11:56.889> theorem<00:11:57.699> to 00:11:57.809 --> 00:11:57.819 align:start position:0% issue in the actual e theorem to 00:11:57.819 --> 00:12:00.059 align:start position:0% issue in the actual e theorem to protocol<00:11:58.209> we<00:11:58.360> only<00:11:58.509> consider<00:11:58.959> the<00:11:59.170> K<00:11:59.410> up<00:11:59.709> to<00:11:59.920> K 00:12:00.059 --> 00:12:00.069 align:start position:0% protocol we only consider the K up to K 00:12:00.069 --> 00:12:02.970 align:start position:0% protocol we only consider the K up to K equals<00:12:00.129> 2<00:12:00.489> case<00:12:01.170> because<00:12:02.170> and<00:12:02.649> the<00:12:02.739> reason 00:12:02.970 --> 00:12:02.980 align:start position:0% equals 2 case because and the reason 00:12:02.980 --> 00:12:04.650 align:start position:0% equals 2 case because and the reason that<00:12:03.009> we<00:12:03.189> need<00:12:03.339> this<00:12:03.549> is<00:12:03.790> because<00:12:04.029> we<00:12:04.149> allow<00:12:04.389> at 00:12:04.650 --> 00:12:04.660 align:start position:0% that we need this is because we allow at 00:12:04.660 --> 00:12:07.109 align:start position:0% that we need this is because we allow at two<00:12:04.779> stations<00:12:05.199> to<00:12:05.319> be<00:12:05.410> included<00:12:06.029> during<00:12:07.029> the 00:12:07.109 --> 00:12:07.119 align:start position:0% two stations to be included during the 00:12:07.119 --> 00:12:09.960 align:start position:0% two stations to be included during the epoch<00:12:07.449> that<00:12:07.480> they're<00:12:07.779> created<00:12:08.230> on<00:12:08.410> chain<00:12:09.040> up 00:12:09.960 --> 00:12:09.970 align:start position:0% epoch that they're created on chain up 00:12:09.970 --> 00:12:12.359 align:start position:0% epoch that they're created on chain up through<00:12:10.600> the<00:12:10.839> next<00:12:11.079> epoch<00:12:11.559> and<00:12:11.829> so<00:12:12.040> you<00:12:12.100> have<00:12:12.339> a 00:12:12.359 --> 00:12:12.369 align:start position:0% through the next epoch and so you have a 00:12:12.369 --> 00:12:16.049 align:start position:0% through the next epoch and so you have a few<00:12:13.019> if<00:12:14.019> things<00:12:14.799> are<00:12:14.980> not<00:12:15.100> performing<00:12:15.759> super 00:12:16.049 --> 00:12:16.059 align:start position:0% few if things are not performing super 00:12:16.059 --> 00:12:17.699 align:start position:0% few if things are not performing super optimally<00:12:16.540> and<00:12:16.660> at<00:12:16.809> a<00:12:16.839> stations<00:12:17.290> aren't<00:12:17.470> being 00:12:17.699 --> 00:12:17.709 align:start position:0% optimally and at a stations aren't being 00:12:17.709 --> 00:12:20.429 align:start position:0% optimally and at a stations aren't being included<00:12:18.100> on<00:12:18.189> each<00:12:18.429> epoch<00:12:18.790> every<00:12:19.329> time<00:12:19.540> and 00:12:20.429 --> 00:12:20.439 align:start position:0% included on each epoch every time and 00:12:20.439 --> 00:12:21.840 align:start position:0% included on each epoch every time and they're<00:12:20.559> included<00:12:21.100> a<00:12:21.309> little<00:12:21.459> bit<00:12:21.610> delayed 00:12:21.840 --> 00:12:21.850 align:start position:0% they're included a little bit delayed 00:12:21.850 --> 00:12:24.689 align:start position:0% they're included a little bit delayed the<00:12:22.239> the<00:12:22.600> state<00:12:22.959> of<00:12:23.230> the<00:12:23.589> chain<00:12:23.949> and<00:12:24.339> what<00:12:24.579> is 00:12:24.689 --> 00:12:24.699 align:start position:0% the the state of the chain and what is 00:12:24.699 --> 00:12:26.699 align:start position:0% the the state of the chain and what is actually<00:12:25.029> justified<00:12:25.480> in<00:12:25.839> the<00:12:25.989> view<00:12:26.199> on<00:12:26.410> chain 00:12:26.699 --> 00:12:26.709 align:start position:0% actually justified in the view on chain 00:12:26.709 --> 00:12:29.579 align:start position:0% actually justified in the view on chain can<00:12:26.919> be<00:12:27.009> delayed<00:12:27.329> and<00:12:28.329> so<00:12:28.389> we<00:12:28.749> have<00:12:28.959> these 00:12:29.579 --> 00:12:29.589 align:start position:0% can be delayed and so we have these 00:12:29.589 --> 00:12:32.639 align:start position:0% can be delayed and so we have these cases<00:12:30.069> where<00:12:30.699> if<00:12:31.029> we<00:12:31.419> open<00:12:31.809> up<00:12:31.899> here's<00:12:32.319> our<00:12:32.499> K 00:12:32.639 --> 00:12:32.649 align:start position:0% cases where if we open up here's our K 00:12:32.649 --> 00:12:35.549 align:start position:0% cases where if we open up here's our K equals<00:12:32.949> 1<00:12:33.129> cases<00:12:33.549> case<00:12:34.449> 2<00:12:34.689> in<00:12:34.869> case<00:12:34.989> for<00:12:35.230> those 00:12:35.549 --> 00:12:35.559 align:start position:0% equals 1 cases case 2 in case for those 00:12:35.559 --> 00:12:38.159 align:start position:0% equals 1 cases case 2 in case for those are<00:12:35.739> nice<00:12:35.889> but<00:12:36.730> here<00:12:37.089> we<00:12:37.239> have<00:12:37.419> these<00:12:37.540> other<00:12:37.749> K 00:12:38.159 --> 00:12:38.169 align:start position:0% are nice but here we have these other K 00:12:38.169 --> 00:12:43.049 align:start position:0% are nice but here we have these other K equals<00:12:38.999> 2<00:12:39.999> cases<00:12:40.509> where<00:12:41.249> by<00:12:42.249> extending<00:12:42.970> the 00:12:43.049 --> 00:12:43.059 align:start position:0% equals 2 cases where by extending the 00:12:43.059 --> 00:12:45.030 align:start position:0% equals 2 cases where by extending the finality<00:12:43.389> rules<00:12:43.660> we<00:12:43.959> actually<00:12:44.439> can<00:12:44.709> capture 00:12:45.030 --> 00:12:45.040 align:start position:0% finality rules we actually can capture 00:12:45.040 --> 00:12:50.249 align:start position:0% finality rules we actually can capture finality<00:12:45.579> in<00:12:45.669> a<00:12:45.730> few<00:12:45.910> more<00:12:46.029> cases<00:12:48.480> I<00:12:49.480> think 00:12:50.249 --> 00:12:50.259 align:start position:0% finality in a few more cases I think 00:12:50.259 --> 00:12:51.659 align:start position:0% finality in a few more cases I think Justin<00:12:50.589> will<00:12:50.709> probably<00:12:50.980> get<00:12:51.069> into<00:12:51.220> this<00:12:51.429> a 00:12:51.659 --> 00:12:51.669 align:start position:0% Justin will probably get into this a 00:12:51.669 --> 00:12:53.429 align:start position:0% Justin will probably get into this a little<00:12:51.819> bit<00:12:51.970> later<00:12:52.209> but<00:12:52.689> in<00:12:52.839> the<00:12:52.959> beacon<00:12:53.230> state 00:12:53.429 --> 00:12:53.439 align:start position:0% little bit later but in the beacon state 00:12:53.439 --> 00:12:56.489 align:start position:0% little bit later but in the beacon state we<00:12:53.619> do<00:12:53.829> have<00:12:54.449> these<00:12:55.449> are<00:12:55.629> the<00:12:55.660> portions<00:12:56.139> of<00:12:56.379> the 00:12:56.489 --> 00:12:56.499 align:start position:0% we do have these are the portions of the 00:12:56.499 --> 00:12:59.489 align:start position:0% we do have these are the portions of the state<00:12:56.709> that<00:12:57.279> are<00:12:57.399> related<00:12:57.790> to<00:12:57.819> finality<00:12:58.689> we 00:12:59.489 --> 00:12:59.499 align:start position:0% state that are related to finality we 00:12:59.499 --> 00:13:03.090 align:start position:0% state that are related to finality we track<00:12:59.999> the<00:13:00.999> last<00:13:01.269> for<00:13:01.809> just<00:13:02.319> a<00:13:02.470> epochs<00:13:02.769> whether 00:13:03.090 --> 00:13:03.100 align:start position:0% track the last for just a epochs whether 00:13:03.100 --> 00:13:05.549 align:start position:0% track the last for just a epochs whether we<00:13:03.249> justified<00:13:03.699> them<00:13:03.879> and<00:13:04.660> a<00:13:04.749> few<00:13:04.929> things<00:13:05.350> about 00:13:05.549 --> 00:13:05.559 align:start position:0% we justified them and a few things about 00:13:05.559 --> 00:13:07.470 align:start position:0% we justified them and a few things about the<00:13:05.769> checkpoints<00:13:06.249> and<00:13:06.429> with<00:13:06.639> that<00:13:06.939> data<00:13:07.239> we 00:13:07.470 --> 00:13:07.480 align:start position:0% the checkpoints and with that data we 00:13:07.480 --> 00:13:12.179 align:start position:0% the checkpoints and with that data we can<00:13:07.769> track<00:13:08.769> these<00:13:09.249> cases<00:13:09.879> and<00:13:10.319> no<00:13:11.319> finality<00:13:11.649> on 00:13:12.179 --> 00:13:12.189 align:start position:0% can track these cases and no finality on 00:13:12.189 --> 00:13:14.220 align:start position:0% can track these cases and no finality on the<00:13:12.399> case<00:13:12.579> of<00:13:12.730> on<00:13:12.850> chain 00:13:14.220 --> 00:13:14.230 align:start position:0% the case of on chain 00:13:14.230 --> 00:13:18.140 align:start position:0% the case of on chain here's<00:13:14.740> this<00:13:14.950> massive<00:13:15.490> nasty<00:13:15.880> function<00:13:17.130> that 00:13:18.140 --> 00:13:18.150 align:start position:0% here's this massive nasty function that 00:13:18.150 --> 00:13:20.640 align:start position:0% here's this massive nasty function that processes<00:13:19.200> justifications<00:13:20.200> and<00:13:20.440> also 00:13:20.640 --> 00:13:20.650 align:start position:0% processes justifications and also 00:13:20.650 --> 00:13:22.710 align:start position:0% processes justifications and also processes<00:13:21.130> finality<00:13:21.550> based<00:13:22.390> upon<00:13:22.540> those 00:13:22.710 --> 00:13:22.720 align:start position:0% processes finality based upon those 00:13:22.720 --> 00:13:25.890 align:start position:0% processes finality based upon those mechanisms<00:13:23.730> I<00:13:24.730> was<00:13:25.210> kind<00:13:25.390> of<00:13:25.420> alluding<00:13:25.630> to 00:13:25.890 --> 00:13:25.900 align:start position:0% mechanisms I was kind of alluding to 00:13:25.900 --> 00:13:26.910 align:start position:0% mechanisms I was kind of alluding to these<00:13:26.020> and<00:13:26.200> I<00:13:26.230> probably<00:13:26.380> should<00:13:26.620> have<00:13:26.650> these 00:13:26.910 --> 00:13:26.920 align:start position:0% these and I probably should have these 00:13:26.920 --> 00:13:30.660 align:start position:0% these and I probably should have these earlier<00:13:27.310> in<00:13:27.550> the<00:13:27.700> slides<00:13:27.970> but<00:13:28.870> we<00:13:29.370> the<00:13:30.370> things 00:13:30.660 --> 00:13:30.670 align:start position:0% earlier in the slides but we the things 00:13:30.670 --> 00:13:33.060 align:start position:0% earlier in the slides but we the things that<00:13:31.000> keep<00:13:31.180> this<00:13:31.390> protocol<00:13:31.839> safe<00:13:32.170> is<00:13:32.410> we 00:13:33.060 --> 00:13:33.070 align:start position:0% that keep this protocol safe is we 00:13:33.070 --> 00:13:36.390 align:start position:0% that keep this protocol safe is we prevent<00:13:33.870> making<00:13:34.870> double<00:13:35.440> attestation<00:13:36.040> so 00:13:36.390 --> 00:13:36.400 align:start position:0% prevent making double attestation so 00:13:36.400 --> 00:13:39.570 align:start position:0% prevent making double attestation so voting<00:13:36.970> for<00:13:37.150> the<00:13:37.240> same<00:13:37.420> target<00:13:38.170> in<00:13:38.560> the<00:13:39.070> end 00:13:39.570 --> 00:13:39.580 align:start position:0% voting for the same target in the end 00:13:39.580 --> 00:13:43.860 align:start position:0% voting for the same target in the end within<00:13:40.000> one<00:13:40.240> epoch<00:13:40.570> and<00:13:41.470> we<00:13:42.010> as<00:13:42.490> I<00:13:42.790> eluded<00:13:43.120> said 00:13:43.860 --> 00:13:43.870 align:start position:0% within one epoch and we as I eluded said 00:13:43.870 --> 00:13:47.360 align:start position:0% within one epoch and we as I eluded said earlier<00:13:44.200> we<00:13:44.440> want<00:13:44.890> to<00:13:44.980> prevent<00:13:45.630> given<00:13:46.630> any 00:13:47.360 --> 00:13:47.370 align:start position:0% earlier we want to prevent given any 00:13:47.370 --> 00:13:51.810 align:start position:0% earlier we want to prevent given any source<00:13:48.370> target<00:13:48.730> link<00:13:49.060> here<00:13:49.990> here<00:13:50.290> here<00:13:50.620> we<00:13:51.160> to 00:13:51.810 --> 00:13:51.820 align:start position:0% source target link here here here we to 00:13:51.820 --> 00:13:54.480 align:start position:0% source target link here here here we to to<00:13:52.210> prevent<00:13:52.920> essentially<00:13:53.920> getting<00:13:54.130> around 00:13:54.480 --> 00:13:54.490 align:start position:0% to prevent essentially getting around 00:13:54.490 --> 00:13:57.480 align:start position:0% to prevent essentially getting around the<00:13:54.670> node<00:13:54.820> double<00:13:55.120> vote<00:13:55.300> we<00:13:56.050> prevent<00:13:56.920> a<00:13:57.040> no 00:13:57.480 --> 00:13:57.490 align:start position:0% the node double vote we prevent a no 00:13:57.490 --> 00:13:58.860 align:start position:0% the node double vote we prevent a no surround<00:13:57.850> so<00:13:58.029> I<00:13:58.060> can't<00:13:58.270> come<00:13:58.450> from<00:13:58.630> something 00:13:58.860 --> 00:13:58.870 align:start position:0% surround so I can't come from something 00:13:58.870 --> 00:14:00.600 align:start position:0% surround so I can't come from something earlier<00:13:59.140> jump<00:13:59.830> over<00:14:00.130> and<00:14:00.339> then<00:14:00.490> begin 00:14:00.600 --> 00:14:00.610 align:start position:0% earlier jump over and then begin 00:14:00.610 --> 00:14:07.920 align:start position:0% earlier jump over and then begin finalizing<00:14:04.650> here's<00:14:05.650> the<00:14:05.830> actual<00:14:06.130> code<00:14:06.870> we<00:14:07.870> can 00:14:07.920 --> 00:14:07.930 align:start position:0% finalizing here's the actual code we can 00:14:07.930 --> 00:14:09.030 align:start position:0% finalizing here's the actual code we can probably<00:14:08.200> get<00:14:08.440> into<00:14:08.560> this<00:14:08.620> little<00:14:08.710> bit<00:14:08.890> later 00:14:09.030 --> 00:14:09.040 align:start position:0% probably get into this little bit later 00:14:09.040 --> 00:14:11.820 align:start position:0% probably get into this little bit later where<00:14:09.490> we<00:14:09.670> take<00:14:09.850> attestation<00:14:10.390> data<00:14:10.830> can't 00:14:11.820 --> 00:14:11.830 align:start position:0% where we take attestation data can't 00:14:11.830 --> 00:14:16.190 align:start position:0% where we take attestation data can't have<00:14:11.950> the<00:14:12.070> same<00:14:12.250> target<00:14:12.850> epoch<00:14:13.240> can<00:14:13.690> surround 00:14:16.190 --> 00:14:16.200 align:start position:0% 00:14:16.200 --> 00:14:19.320 align:start position:0% that's<00:14:17.200> that<00:14:17.800> for<00:14:18.040> now<00:14:18.220> sorry<00:14:18.760> that<00:14:19.030> was<00:14:19.150> so 00:14:19.320 --> 00:14:19.330 align:start position:0% that's that for now sorry that was so 00:14:19.330 --> 00:14:22.110 align:start position:0% that's that for now sorry that was so fast<00:14:19.660> we<00:14:20.530> have<00:14:20.620> a<00:14:20.680> lot<00:14:20.920> to<00:14:21.190> cover<00:14:21.339> today<00:14:21.700> and 00:14:22.110 --> 00:14:22.120 align:start position:0% fast we have a lot to cover today and 00:14:22.120 --> 00:14:25.380 align:start position:0% fast we have a lot to cover today and that's<00:14:22.300> like<00:14:22.480> one<00:14:22.960> of<00:14:23.080> the<00:14:23.140> more<00:14:24.390> detailed 00:14:25.380 --> 00:14:25.390 align:start position:0% that's like one of the more detailed 00:14:25.390 --> 00:14:38.480 align:start position:0% that's like one of the more detailed components<00:14:27.089> metallic 00:14:38.480 --> 00:14:38.490 align:start position:0% 00:14:38.490 --> 00:14:41.850 align:start position:0% all<00:14:39.490> right<00:14:39.670> so<00:14:40.000> I<00:14:40.390> am<00:14:40.510> going<00:14:40.959> to<00:14:41.260> be<00:14:41.470> talking 00:14:41.850 --> 00:14:41.860 align:start position:0% all right so I am going to be talking 00:14:41.860 --> 00:14:45.570 align:start position:0% all right so I am going to be talking about<00:14:42.520> as<00:14:43.390> you<00:14:43.600> can<00:14:43.779> guess<00:14:44.050> the<00:14:44.350> LMG<00:14:45.070> goes<00:14:45.310> for 00:14:45.570 --> 00:14:45.580 align:start position:0% about as you can guess the LMG goes for 00:14:45.580 --> 00:14:52.110 align:start position:0% about as you can guess the LMG goes for choice<00:14:45.820> rule<00:14:46.890> so<00:14:48.510> I<00:14:49.620> guess<00:14:50.620> so<00:14:51.550> to<00:14:51.730> start<00:14:51.940> off 00:14:52.110 --> 00:14:52.120 align:start position:0% choice rule so I guess so to start off 00:14:52.120 --> 00:14:54.389 align:start position:0% choice rule so I guess so to start off kind<00:14:52.390> of<00:14:52.540> what<00:14:52.779> is<00:14:52.959> LMG<00:14:53.380> ghost<00:14:53.620> it's<00:14:54.190> an 00:14:54.389 --> 00:14:54.399 align:start position:0% kind of what is LMG ghost it's an 00:14:54.399 --> 00:14:56.130 align:start position:0% kind of what is LMG ghost it's an adaptation<00:14:54.580> of<00:14:55.510> ghost 00:14:56.130 --> 00:14:56.140 align:start position:0% adaptation of ghost 00:14:56.140 --> 00:14:59.490 align:start position:0% adaptation of ghost aka<00:14:56.950> a<00:14:57.430> greedy<00:14:58.000> heaviest<00:14:58.540> observed<00:14:58.959> subtree 00:14:59.490 --> 00:14:59.500 align:start position:0% aka a greedy heaviest observed subtree 00:14:59.500 --> 00:15:02.430 align:start position:0% aka a greedy heaviest observed subtree which<00:14:59.740> is<00:14:59.950> a<00:15:00.660> alternative<00:15:01.660> proof-of-work 00:15:02.430 --> 00:15:02.440 align:start position:0% which is a alternative proof-of-work 00:15:02.440 --> 00:15:06.060 align:start position:0% which is a alternative proof-of-work fortress<00:15:03.220> rule<00:15:03.490> that<00:15:03.700> some<00:15:04.620> academics<00:15:05.620> humans 00:15:06.060 --> 00:15:06.070 align:start position:0% fortress rule that some academics humans 00:15:06.070 --> 00:15:08.100 align:start position:0% fortress rule that some academics humans ensemble<00:15:06.580> in<00:15:06.670> ski<00:15:06.850> anivia<00:15:07.149> so<00:15:07.360> hard<00:15:07.570> developed 00:15:08.100 --> 00:15:08.110 align:start position:0% ensemble in ski anivia so hard developed 00:15:08.110 --> 00:15:11.519 align:start position:0% ensemble in ski anivia so hard developed in<00:15:08.490> 2014<00:15:09.490> and<00:15:10.209> it<00:15:10.390> basically<00:15:10.540> takes<00:15:11.080> the<00:15:11.320> same 00:15:11.519 --> 00:15:11.529 align:start position:0% in 2014 and it basically takes the same 00:15:11.529 --> 00:15:14.699 align:start position:0% in 2014 and it basically takes the same principles<00:15:12.190> as<00:15:12.520> original<00:15:13.240> ghosts<00:15:13.510> and<00:15:13.839> try 00:15:14.699 --> 00:15:14.709 align:start position:0% principles as original ghosts and try 00:15:14.709 --> 00:15:16.290 align:start position:0% principles as original ghosts and try stone<00:15:15.010> have<00:15:15.190> modified<00:15:15.610> them<00:15:15.790> slightly<00:15:15.850> and 00:15:16.290 --> 00:15:16.300 align:start position:0% stone have modified them slightly and 00:15:16.300 --> 00:15:19.650 align:start position:0% stone have modified them slightly and fit<00:15:16.480> them<00:15:16.660> into<00:15:16.899> a<00:15:17.190> proof<00:15:18.190> of<00:15:18.339> stake<00:15:18.660> context 00:15:19.650 --> 00:15:19.660 align:start position:0% fit them into a proof of stake context 00:15:19.660 --> 00:15:24.120 align:start position:0% fit them into a proof of stake context so<00:15:20.440> to<00:15:21.399> start<00:15:22.390> just<00:15:23.020> a<00:15:23.170> kind<00:15:23.410> of<00:15:23.500> quick<00:15:23.740> intro 00:15:24.120 --> 00:15:24.130 align:start position:0% so to start just a kind of quick intro 00:15:24.130 --> 00:15:26.790 align:start position:0% so to start just a kind of quick intro of<00:15:24.310> what<00:15:24.490> ghost<00:15:24.730> itself<00:15:25.149> is<00:15:25.360> basically<00:15:25.800> the 00:15:26.790 --> 00:15:26.800 align:start position:0% of what ghost itself is basically the 00:15:26.800 --> 00:15:30.750 align:start position:0% of what ghost itself is basically the idea<00:15:27.279> here<00:15:28.149> is<00:15:28.180> that<00:15:29.110> if<00:15:29.740> you<00:15:29.890> imagine<00:15:30.070> a 00:15:30.750 --> 00:15:30.760 align:start position:0% idea here is that if you imagine a 00:15:30.760 --> 00:15:33.210 align:start position:0% idea here is that if you imagine a network<00:15:31.480> where<00:15:31.899> there<00:15:32.500> is<00:15:32.589> a<00:15:32.620> lot<00:15:32.860> of<00:15:32.950> network 00:15:33.210 --> 00:15:33.220 align:start position:0% network where there is a lot of network 00:15:33.220 --> 00:15:35.310 align:start position:0% network where there is a lot of network latency<00:15:33.670> or<00:15:34.089> there<00:15:34.630> is<00:15:34.720> normal<00:15:35.050> network 00:15:35.310 --> 00:15:35.320 align:start position:0% latency or there is normal network 00:15:35.320 --> 00:15:37.260 align:start position:0% latency or there is normal network latency<00:15:35.800> network<00:15:36.310> latency<00:15:36.670> but<00:15:36.790> blocks<00:15:37.060> are 00:15:37.260 --> 00:15:37.270 align:start position:0% latency network latency but blocks are 00:15:37.270 --> 00:15:39.120 align:start position:0% latency network latency but blocks are very<00:15:37.450> fast<00:15:37.720> so<00:15:38.020> say<00:15:38.170> network<00:15:38.500> latency<00:15:38.860> is<00:15:38.920> one 00:15:39.120 --> 00:15:39.130 align:start position:0% very fast so say network latency is one 00:15:39.130 --> 00:15:40.560 align:start position:0% very fast so say network latency is one second<00:15:39.580> you<00:15:39.640> have<00:15:39.730> a<00:15:39.790> block<00:15:40.029> coming<00:15:40.360> every 00:15:40.560 --> 00:15:40.570 align:start position:0% second you have a block coming every 00:15:40.570 --> 00:15:45.120 align:start position:0% second you have a block coming every three<00:15:40.600> seconds<00:15:41.200> then<00:15:42.180> maybe<00:15:43.180> like<00:15:44.130> something 00:15:45.120 --> 00:15:45.130 align:start position:0% three seconds then maybe like something 00:15:45.130 --> 00:15:47.850 align:start position:0% three seconds then maybe like something like<00:15:45.399> a<00:15:45.430> quarter<00:15:45.910> of<00:15:46.060> all<00:15:46.149> the<00:15:46.209> blocks<00:15:46.600> are<00:15:46.959> not 00:15:47.850 --> 00:15:47.860 align:start position:0% like a quarter of all the blocks are not 00:15:47.860 --> 00:15:50.040 align:start position:0% like a quarter of all the blocks are not going<00:15:48.339> to<00:15:48.430> be<00:15:48.520> here<00:15:48.730> kind<00:15:48.910> of<00:15:49.000> conveniently<00:15:49.930> in 00:15:50.040 --> 00:15:50.050 align:start position:0% going to be here kind of conveniently in 00:15:50.050 --> 00:15:51.900 align:start position:0% going to be here kind of conveniently in the<00:15:50.170> same<00:15:50.350> chain<00:15:50.709> right<00:15:51.130> because<00:15:51.550> you<00:15:51.760> might 00:15:51.900 --> 00:15:51.910 align:start position:0% the same chain right because you might 00:15:51.910 --> 00:15:53.610 align:start position:0% the same chain right because you might just<00:15:52.089> have<00:15:52.300> a<00:15:52.360> block<00:15:52.660> get<00:15:52.839> produced<00:15:53.260> to<00:15:53.470> end 00:15:53.610 --> 00:15:53.620 align:start position:0% just have a block get produced to end 00:15:53.620 --> 00:15:55.769 align:start position:0% just have a block get produced to end before<00:15:54.339> that<00:15:54.670> block<00:15:54.910> gets<00:15:55.120> broadcasted 00:15:55.769 --> 00:15:55.779 align:start position:0% before that block gets broadcasted 00:15:55.779 --> 00:15:57.540 align:start position:0% before that block gets broadcasted another<00:15:56.020> block<00:15:56.290> gets<00:15:56.529> created<00:15:56.890> at<00:15:57.190> the<00:15:57.370> same 00:15:57.540 --> 00:15:57.550 align:start position:0% another block gets created at the same 00:15:57.550 --> 00:16:03.120 align:start position:0% another block gets created at the same time<00:15:57.820> and<00:15:59.040> the<00:16:00.040> reason<00:16:00.490> why<00:16:01.120> like<00:16:01.660> this<00:16:02.290> is<00:16:02.620> bad 00:16:03.120 --> 00:16:03.130 align:start position:0% time and the reason why like this is bad 00:16:03.130 --> 00:16:05.430 align:start position:0% time and the reason why like this is bad and<00:16:03.220> so<00:16:03.790> in<00:16:04.149> Bitcoin<00:16:04.510> they<00:16:04.660> call<00:16:04.870> this<00:16:04.990> orphans 00:16:05.430 --> 00:16:05.440 align:start position:0% and so in Bitcoin they call this orphans 00:16:05.440 --> 00:16:07.380 align:start position:0% and so in Bitcoin they call this orphans or<00:16:05.589> sales<00:16:05.860> and<00:16:06.220> aetherium<00:16:06.610> we<00:16:06.730> call<00:16:06.880> it<00:16:07.000> uncles 00:16:07.380 --> 00:16:07.390 align:start position:0% or sales and aetherium we call it uncles 00:16:07.390 --> 00:16:11.069 align:start position:0% or sales and aetherium we call it uncles the<00:16:08.170> reason<00:16:08.440> why<00:16:08.560> it's<00:16:08.709> bad<00:16:08.890> is<00:16:09.310> because<00:16:10.079> if 00:16:11.069 --> 00:16:11.079 align:start position:0% the reason why it's bad is because if 00:16:11.079 --> 00:16:14.670 align:start position:0% the reason why it's bad is because if you<00:16:12.000> imagine<00:16:13.000> there<00:16:13.149> is<00:16:13.209> an<00:16:13.329> attacker<00:16:13.630> and<00:16:14.140> the 00:16:14.670 --> 00:16:14.680 align:start position:0% you imagine there is an attacker and the 00:16:14.680 --> 00:16:18.150 align:start position:0% you imagine there is an attacker and the attacker<00:16:15.339> is<00:16:15.730> trying<00:16:16.240> to<00:16:16.600> do<00:16:16.839> a<00:16:16.870> 51%<00:16:17.380> attack<00:16:17.740> so 00:16:18.150 --> 00:16:18.160 align:start position:0% attacker is trying to do a 51% attack so 00:16:18.160 --> 00:16:20.610 align:start position:0% attacker is trying to do a 51% attack so make<00:16:18.310> an<00:16:18.430> attack<00:16:18.730> chain<00:16:19.000> that's<00:16:19.410> longer<00:16:20.410> than 00:16:20.610 --> 00:16:20.620 align:start position:0% make an attack chain that's longer than 00:16:20.620 --> 00:16:22.290 align:start position:0% make an attack chain that's longer than the<00:16:20.980> honest<00:16:21.279> chain<00:16:21.490> after<00:16:21.790> at<00:16:21.880> some<00:16:22.060> point 00:16:22.290 --> 00:16:22.300 align:start position:0% the honest chain after at some point 00:16:22.300 --> 00:16:24.360 align:start position:0% the honest chain after at some point then<00:16:22.899> the<00:16:23.020> attacker<00:16:23.350> has<00:16:23.620> an<00:16:23.770> advantage<00:16:24.040> right 00:16:24.360 --> 00:16:24.370 align:start position:0% then the attacker has an advantage right 00:16:24.370 --> 00:16:27.030 align:start position:0% then the attacker has an advantage right because<00:16:24.790> the<00:16:24.910> fork<00:16:25.120> choice<00:16:25.360> is<00:16:25.870> tries<00:16:26.410> to<00:16:26.589> look 00:16:27.030 --> 00:16:27.040 align:start position:0% because the fork choice is tries to look 00:16:27.040 --> 00:16:29.519 align:start position:0% because the fork choice is tries to look for<00:16:27.250> the<00:16:27.310> longest<00:16:27.520> chain<00:16:27.880> so<00:16:28.450> the<00:16:29.170> honest 00:16:29.519 --> 00:16:29.529 align:start position:0% for the longest chain so the honest 00:16:29.529 --> 00:16:32.160 align:start position:0% for the longest chain so the honest chain<00:16:29.800> one<00:16:30.399> of<00:16:30.610> every<00:16:30.820> four<00:16:31.000> blocks<00:16:31.329> is<00:16:31.660> not 00:16:32.160 --> 00:16:32.170 align:start position:0% chain one of every four blocks is not 00:16:32.170 --> 00:16:33.780 align:start position:0% chain one of every four blocks is not lengthening<00:16:32.680> the<00:16:32.890> chain<00:16:33.130> it's<00:16:33.370> kind<00:16:33.610> of<00:16:33.700> a 00:16:33.780 --> 00:16:33.790 align:start position:0% lengthening the chain it's kind of a 00:16:33.790 --> 00:16:35.730 align:start position:0% lengthening the chain it's kind of a sister<00:16:34.149> of<00:16:34.300> some<00:16:34.480> other<00:16:34.630> block<00:16:34.899> but<00:16:35.470> on<00:16:35.620> the 00:16:35.730 --> 00:16:35.740 align:start position:0% sister of some other block but on the 00:16:35.740 --> 00:16:37.470 align:start position:0% sister of some other block but on the attack<00:16:36.010> chain<00:16:36.310> it's<00:16:36.550> just<00:16:36.790> the<00:16:36.880> attacker<00:16:37.209> and 00:16:37.470 --> 00:16:37.480 align:start position:0% attack chain it's just the attacker and 00:16:37.480 --> 00:16:40.590 align:start position:0% attack chain it's just the attacker and so<00:16:37.660> everything<00:16:38.050> works<00:16:38.230> perfectly<00:16:38.740> so<00:16:39.600> instead 00:16:40.590 --> 00:16:40.600 align:start position:0% so everything works perfectly so instead 00:16:40.600 --> 00:16:43.170 align:start position:0% so everything works perfectly so instead of<00:16:40.660> needing<00:16:41.050> to<00:16:41.079> have<00:16:41.350> 51%<00:16:41.980> of<00:16:42.459> the<00:16:42.610> hash<00:16:42.880> power 00:16:43.170 --> 00:16:43.180 align:start position:0% of needing to have 51% of the hash power 00:16:43.180 --> 00:16:45.660 align:start position:0% of needing to have 51% of the hash power the<00:16:43.450> attacker<00:16:43.750> might<00:16:44.020> only<00:16:44.260> need<00:16:44.529> to<00:16:44.650> have<00:16:44.800> 43% 00:16:45.660 --> 00:16:45.670 align:start position:0% the attacker might only need to have 43% 00:16:45.670 --> 00:16:48.150 align:start position:0% the attacker might only need to have 43% of<00:16:45.699> the<00:16:45.820> hash<00:16:46.000> power<00:16:46.270> and<00:16:46.600> if<00:16:47.410> network<00:16:47.740> latency 00:16:48.150 --> 00:16:48.160 align:start position:0% of the hash power and if network latency 00:16:48.160 --> 00:16:49.769 align:start position:0% of the hash power and if network latency goes<00:16:48.190> higher<00:16:48.610> than<00:16:48.910> the<00:16:49.060> percentage<00:16:49.180> drops 00:16:49.769 --> 00:16:49.779 align:start position:0% goes higher than the percentage drops 00:16:49.779 --> 00:16:50.249 align:start position:0% goes higher than the percentage drops more 00:16:50.249 --> 00:16:50.259 align:start position:0% more 00:16:50.259 --> 00:16:52.439 align:start position:0% more or<00:16:50.379> announced<00:16:51.069> Network<00:16:51.399> latency<00:16:51.879> approaches 00:16:52.439 --> 00:16:52.449 align:start position:0% or announced Network latency approaches 00:16:52.449 --> 00:16:53.939 align:start position:0% or announced Network latency approaches infinity<00:16:52.689> of<00:16:52.959> the<00:16:53.109> attacker<00:16:53.439> can<00:16:53.739> through<00:16:53.889> a 00:16:53.939 --> 00:16:53.949 align:start position:0% infinity of the attacker can through a 00:16:53.949 --> 00:16:56.099 align:start position:0% infinity of the attacker can through a 51%<00:16:54.399> attack<00:16:54.759> with<00:16:55.149> basically<00:16:55.509> nothing 00:16:56.099 --> 00:16:56.109 align:start position:0% 51% attack with basically nothing 00:16:56.109 --> 00:17:00.389 align:start position:0% 51% attack with basically nothing so<00:16:57.479> ghost<00:16:58.479> fixes<00:16:59.019> this<00:16:59.199> and<00:16:59.649> the<00:17:00.100> kind<00:17:00.279> of 00:17:00.389 --> 00:17:00.399 align:start position:0% so ghost fixes this and the kind of 00:17:00.399 --> 00:17:02.309 align:start position:0% so ghost fixes this and the kind of philosophy<00:17:01.059> behind<00:17:01.239> this<00:17:01.660> right<00:17:01.899> is<00:17:02.079> that<00:17:02.229> if 00:17:02.309 --> 00:17:02.319 align:start position:0% philosophy behind this right is that if 00:17:02.319 --> 00:17:04.470 align:start position:0% philosophy behind this right is that if you<00:17:02.410> imagine<00:17:02.529> a<00:17:02.949> chain<00:17:03.189> here<00:17:03.489> where<00:17:03.790> let's<00:17:04.089> say 00:17:04.470 --> 00:17:04.480 align:start position:0% you imagine a chain here where let's say 00:17:04.480 --> 00:17:07.860 align:start position:0% you imagine a chain here where let's say block<00:17:04.870> D<00:17:05.230> was<00:17:06.010> built<00:17:06.250> on<00:17:06.429> top<00:17:06.610> of<00:17:06.669> block<00:17:07.029> PE<00:17:07.269> but 00:17:07.860 --> 00:17:07.870 align:start position:0% block D was built on top of block PE but 00:17:07.870 --> 00:17:09.689 align:start position:0% block D was built on top of block PE but then<00:17:08.139> this<00:17:08.470> chain<00:17:08.799> was<00:17:09.010> block<00:17:09.220> C<00:17:09.429> and<00:17:09.579> then 00:17:09.689 --> 00:17:09.699 align:start position:0% then this chain was block C and then 00:17:09.699 --> 00:17:11.909 align:start position:0% then this chain was block C and then block<00:17:09.939> he<00:17:10.089> ended<00:17:10.360> up<00:17:10.449> winning<00:17:10.659> if<00:17:11.409> you<00:17:11.620> look<00:17:11.799> at 00:17:11.909 --> 00:17:11.919 align:start position:0% block he ended up winning if you look at 00:17:11.919 --> 00:17:14.549 align:start position:0% block he ended up winning if you look at block<00:17:12.100> D<00:17:12.279> like<00:17:12.819> block<00:17:13.179> G<00:17:13.449> ultimately<00:17:14.079> is<00:17:14.289> still 00:17:14.549 --> 00:17:14.559 align:start position:0% block D like block G ultimately is still 00:17:14.559 --> 00:17:17.069 align:start position:0% block D like block G ultimately is still a<00:17:14.799> vote<00:17:15.010> for<00:17:15.250> B<00:17:15.399> right<00:17:15.909> it<00:17:16.240> may<00:17:16.449> not<00:17:16.600> be<00:17:16.779> a<00:17:16.809> part 00:17:17.069 --> 00:17:17.079 align:start position:0% a vote for B right it may not be a part 00:17:17.079 --> 00:17:19.439 align:start position:0% a vote for B right it may not be a part of<00:17:17.199> correctly<00:17:17.919> on<00:17:18.159> the<00:17:18.429> same<00:17:18.639> chain<00:17:18.939> but<00:17:19.209> D<00:17:19.360> is 00:17:19.439 --> 00:17:19.449 align:start position:0% of correctly on the same chain but D is 00:17:19.449 --> 00:17:21.299 align:start position:0% of correctly on the same chain but D is still<00:17:19.689> voting<00:17:20.199> for<00:17:20.409> B<00:17:20.529> who<00:17:20.740> ever<00:17:20.889> voted<00:17:21.159> for 00:17:21.299 --> 00:17:21.309 align:start position:0% still voting for B who ever voted for 00:17:21.309 --> 00:17:23.699 align:start position:0% still voting for B who ever voted for overbuilt<00:17:21.970> D<00:17:22.179> still<00:17:22.839> thought<00:17:23.199> that<00:17:23.230> B<00:17:23.559> is<00:17:23.679> a 00:17:23.699 --> 00:17:23.709 align:start position:0% overbuilt D still thought that B is a 00:17:23.709 --> 00:17:26.059 align:start position:0% overbuilt D still thought that B is a good<00:17:23.949> block<00:17:24.220> to<00:17:24.399> build<00:17:24.579> a<00:17:24.669> chain<00:17:24.819> on<00:17:25.029> and<00:17:25.240> so 00:17:26.059 --> 00:17:26.069 align:start position:0% good block to build a chain on and so 00:17:26.069 --> 00:17:28.919 align:start position:0% good block to build a chain on and so really<00:17:27.069> you<00:17:27.459> should<00:17:27.490> be<00:17:27.850> taking<00:17:28.600> into<00:17:28.779> account 00:17:28.919 --> 00:17:28.929 align:start position:0% really you should be taking into account 00:17:28.929 --> 00:17:33.720 align:start position:0% really you should be taking into account both<00:17:29.740> D<00:17:30.100> and<00:17:30.130> E<00:17:30.789> as<00:17:31.200> of<00:17:32.200> blocks<00:17:32.889> that's<00:17:33.279> that 00:17:33.720 --> 00:17:33.730 align:start position:0% both D and E as of blocks that's that 00:17:33.730 --> 00:17:36.659 align:start position:0% both D and E as of blocks that's that support<00:17:34.299> B's<00:17:34.630> rightful<00:17:35.200> position<00:17:35.470> as<00:17:35.799> as<00:17:36.309> part 00:17:36.659 --> 00:17:36.669 align:start position:0% support B's rightful position as as part 00:17:36.669 --> 00:17:39.600 align:start position:0% support B's rightful position as as part of<00:17:36.730> the<00:17:36.880> chain<00:17:37.120> so<00:17:37.740> the<00:17:38.740> way<00:17:38.860> that<00:17:39.070> ghost<00:17:39.279> works 00:17:39.600 --> 00:17:39.610 align:start position:0% of the chain so the way that ghost works 00:17:39.610 --> 00:17:41.970 align:start position:0% of the chain so the way that ghost works is<00:17:39.880> basically<00:17:40.320> instead<00:17:41.320> of<00:17:41.440> looking<00:17:41.740> at<00:17:41.830> the 00:17:41.970 --> 00:17:41.980 align:start position:0% is basically instead of looking at the 00:17:41.980 --> 00:17:44.310 align:start position:0% is basically instead of looking at the longest<00:17:42.309> chain<00:17:42.549> you<00:17:43.149> have<00:17:43.389> the<00:17:43.750> you<00:17:43.960> run<00:17:44.139> this 00:17:44.310 --> 00:17:44.320 align:start position:0% longest chain you have the you run this 00:17:44.320 --> 00:17:45.779 align:start position:0% longest chain you have the you run this kind<00:17:44.529> of<00:17:44.590> iterative<00:17:44.830> process<00:17:45.490> where<00:17:45.610> you 00:17:45.779 --> 00:17:45.789 align:start position:0% kind of iterative process where you 00:17:45.789 --> 00:17:48.360 align:start position:0% kind of iterative process where you start<00:17:46.059> from<00:17:46.090> the<00:17:46.360> root<00:17:46.510> if<00:17:47.470> some<00:17:47.769> block<00:17:48.010> only 00:17:48.360 --> 00:17:48.370 align:start position:0% start from the root if some block only 00:17:48.370 --> 00:17:50.159 align:start position:0% start from the root if some block only has<00:17:48.490> one<00:17:48.730> child<00:17:48.940> you<00:17:49.149> walk<00:17:49.480> over<00:17:49.510> to<00:17:49.750> the<00:17:49.899> child 00:17:50.159 --> 00:17:50.169 align:start position:0% has one child you walk over to the child 00:17:50.169 --> 00:17:53.159 align:start position:0% has one child you walk over to the child if<00:17:51.130> you<00:17:51.519> if<00:17:51.669> a<00:17:51.760> block<00:17:51.970> has<00:17:52.210> multiple<00:17:52.690> children 00:17:53.159 --> 00:17:53.169 align:start position:0% if you if a block has multiple children 00:17:53.169 --> 00:17:56.669 align:start position:0% if you if a block has multiple children then<00:17:53.590> you<00:17:53.769> select<00:17:53.980> the<00:17:54.370> child<00:17:54.990> whose<00:17:55.990> tree<00:17:56.470> of 00:17:56.669 --> 00:17:56.679 align:start position:0% then you select the child whose tree of 00:17:56.679 --> 00:17:58.680 align:start position:0% then you select the child whose tree of descendants<00:17:57.309> is<00:17:57.460> larger<00:17:57.909> right<00:17:58.149> so<00:17:58.330> over<00:17:58.389> here 00:17:58.680 --> 00:17:58.690 align:start position:0% descendants is larger right so over here 00:17:58.690 --> 00:18:01.139 align:start position:0% descendants is larger right so over here this<00:17:58.899> block<00:17:59.169> has<00:17:59.379> no<00:17:59.620> descendants<00:18:00.159> so<00:18:00.700> total 00:18:01.139 --> 00:18:01.149 align:start position:0% this block has no descendants so total 00:18:01.149 --> 00:18:03.000 align:start position:0% this block has no descendants so total of<00:18:01.269> 1<00:18:01.480> including<00:18:01.840> itself<00:18:02.230> over<00:18:02.620> here<00:18:02.830> this 00:18:03.000 --> 00:18:03.010 align:start position:0% of 1 including itself over here this 00:18:03.010 --> 00:18:06.269 align:start position:0% of 1 including itself over here this block<00:18:03.309> has<00:18:03.490> 1<00:18:03.760> 2<00:18:03.909> 3<00:18:04.029> 4<00:18:04.299> 5<00:18:04.450> 6<00:18:04.690> descendants<00:18:05.320> and<00:18:06.070> so 00:18:06.269 --> 00:18:06.279 align:start position:0% block has 1 2 3 4 5 6 descendants and so 00:18:06.279 --> 00:18:07.950 align:start position:0% block has 1 2 3 4 5 6 descendants and so we<00:18:06.370> go<00:18:06.519> over<00:18:06.669> here<00:18:06.909> then<00:18:07.149> you<00:18:07.210> walk<00:18:07.450> over<00:18:07.720> here 00:18:07.950 --> 00:18:07.960 align:start position:0% we go over here then you walk over here 00:18:07.960 --> 00:18:10.080 align:start position:0% we go over here then you walk over here then<00:18:08.200> you<00:18:08.289> have<00:18:08.440> another<00:18:08.649> fork<00:18:09.070> then<00:18:09.610> this<00:18:09.909> is 00:18:10.080 --> 00:18:10.090 align:start position:0% then you have another fork then this is 00:18:10.090 --> 00:18:11.940 align:start position:0% then you have another fork then this is the<00:18:10.269> kind<00:18:10.570> of<00:18:10.600> heaviest<00:18:10.960> subtree<00:18:11.409> again<00:18:11.679> and 00:18:11.940 --> 00:18:11.950 align:start position:0% the kind of heaviest subtree again and 00:18:11.950 --> 00:18:14.970 align:start position:0% the kind of heaviest subtree again and so<00:18:12.100> E<00:18:12.309> is<00:18:12.340> the<00:18:12.549> head<00:18:12.750> now<00:18:13.750> in<00:18:14.559> this<00:18:14.769> particular 00:18:14.970 --> 00:18:14.980 align:start position:0% so E is the head now in this particular 00:18:14.980 --> 00:18:17.610 align:start position:0% so E is the head now in this particular case<00:18:15.639> right<00:18:16.000> like<00:18:16.240> the<00:18:16.510> the<00:18:16.990> Wong<00:18:17.169> is<00:18:17.350> chain 00:18:17.610 --> 00:18:17.620 align:start position:0% case right like the the Wong is chain 00:18:17.620 --> 00:18:20.700 align:start position:0% case right like the the Wong is chain rule<00:18:17.919> and<00:18:18.250> ghost<00:18:18.760> agree<00:18:19.360> but<00:18:20.049> there<00:18:20.200> are<00:18:20.350> going 00:18:20.700 --> 00:18:20.710 align:start position:0% rule and ghost agree but there are going 00:18:20.710 --> 00:18:24.299 align:start position:0% rule and ghost agree but there are going to<00:18:20.919> be<00:18:21.070> points<00:18:21.909> like<00:18:22.179> many<00:18:23.080> theoretical<00:18:23.799> cases 00:18:24.299 --> 00:18:24.309 align:start position:0% to be points like many theoretical cases 00:18:24.309 --> 00:18:26.070 align:start position:0% to be points like many theoretical cases especially<00:18:25.059> when<00:18:25.269> there<00:18:25.419> is<00:18:25.510> an<00:18:25.690> active 00:18:26.070 --> 00:18:26.080 align:start position:0% especially when there is an active 00:18:26.080 --> 00:18:28.619 align:start position:0% especially when there is an active attack<00:18:26.350> being<00:18:26.679> attempted<00:18:26.950> when<00:18:27.789> these<00:18:28.149> extra 00:18:28.619 --> 00:18:28.629 align:start position:0% attack being attempted when these extra 00:18:28.629 --> 00:18:30.269 align:start position:0% attack being attempted when these extra blocks<00:18:28.899> that<00:18:29.230> really<00:18:29.559> do<00:18:29.710> matter<00:18:29.860> and<00:18:30.190> they 00:18:30.269 --> 00:18:30.279 align:start position:0% blocks that really do matter and they 00:18:30.279 --> 00:18:33.360 align:start position:0% blocks that really do matter and they can<00:18:30.460> save<00:18:30.669> you<00:18:30.850> from<00:18:31.059> an<00:18:31.179> attack<00:18:31.480> now<00:18:32.200> the<00:18:33.159> way 00:18:33.360 --> 00:18:33.370 align:start position:0% can save you from an attack now the way 00:18:33.370 --> 00:18:36.149 align:start position:0% can save you from an attack now the way that<00:18:33.639> ghost<00:18:34.230> applies<00:18:35.230> this<00:18:35.620> to<00:18:35.830> a<00:18:35.860> proof<00:18:36.070> of 00:18:36.149 --> 00:18:36.159 align:start position:0% that ghost applies this to a proof of 00:18:36.159 --> 00:18:40.680 align:start position:0% that ghost applies this to a proof of state<00:18:36.399> context<00:18:37.059> is<00:18:38.250> basically<00:18:39.269> to<00:18:40.269> start<00:18:40.539> off 00:18:40.680 --> 00:18:40.690 align:start position:0% state context is basically to start off 00:18:40.690 --> 00:18:42.990 align:start position:0% state context is basically to start off it's<00:18:40.870> very<00:18:41.049> similar<00:18:41.500> except<00:18:42.370> instead<00:18:42.760> of 00:18:42.990 --> 00:18:43.000 align:start position:0% it's very similar except instead of 00:18:43.000 --> 00:18:45.720 align:start position:0% it's very similar except instead of looking<00:18:43.299> at<00:18:43.570> all<00:18:43.779> blocks<00:18:44.110> it<00:18:44.710> only<00:18:44.950> looks<00:18:45.429> at 00:18:45.720 --> 00:18:45.730 align:start position:0% looking at all blocks it only looks at 00:18:45.730 --> 00:18:48.840 align:start position:0% looking at all blocks it only looks at the<00:18:46.090> block<00:18:46.690> that<00:18:47.019> is<00:18:47.379> the<00:18:48.039> most<00:18:48.250> recent 00:18:48.840 --> 00:18:48.850 align:start position:0% the block that is the most recent 00:18:48.850 --> 00:18:52.289 align:start position:0% the block that is the most recent message<00:18:49.500> submitted<00:18:50.500> by<00:18:50.710> that<00:18:50.919> validator<00:18:51.399> so 00:18:52.289 --> 00:18:52.299 align:start position:0% message submitted by that validator so 00:18:52.299 --> 00:18:54.299 align:start position:0% message submitted by that validator so for<00:18:52.510> example<00:18:52.990> in<00:18:53.110> this<00:18:53.230> case<00:18:53.470> imagine<00:18:54.100> you 00:18:54.299 --> 00:18:54.309 align:start position:0% for example in this case imagine you 00:18:54.309 --> 00:18:56.070 align:start position:0% for example in this case imagine you have<00:18:54.490> a<00:18:54.519> proof<00:18:54.879> of<00:18:55.000> stake<00:18:55.210> chain<00:18:55.480> you<00:18:55.659> have<00:18:55.690> 5 00:18:56.070 --> 00:18:56.080 align:start position:0% have a proof of stake chain you have 5 00:18:56.080 --> 00:18:59.009 align:start position:0% have a proof of stake chain you have 5 validators<00:18:56.740> we'll<00:18:57.010> call<00:18:57.220> them<00:18:57.490> like<00:18:58.149> la<00:18:58.450> Alice 00:18:59.009 --> 00:18:59.019 align:start position:0% validators we'll call them like la Alice 00:18:59.019 --> 00:19:02.279 align:start position:0% validators we'll call them like la Alice Bob<00:18:59.289> Charlie<00:18:59.830> David<00:19:00.190> and<00:19:00.309> Evan<00:19:00.639> and<00:19:00.879> if<00:19:01.840> you 00:19:02.279 --> 00:19:02.289 align:start position:0% Bob Charlie David and Evan and if you 00:19:02.289 --> 00:19:04.289 align:start position:0% Bob Charlie David and Evan and if you look<00:19:02.500> at<00:19:02.620> Alice<00:19:02.980> now<00:19:03.129> has<00:19:03.279> created<00:19:03.639> two<00:19:03.789> blocks 00:19:04.289 --> 00:19:04.299 align:start position:0% look at Alice now has created two blocks 00:19:04.299 --> 00:19:07.289 align:start position:0% look at Alice now has created two blocks over<00:19:04.570> here<00:19:04.809> and<00:19:05.019> then<00:19:05.139> one<00:19:05.289> over<00:19:05.320> here<00:19:05.889> and<00:19:06.299> a 00:19:07.289 --> 00:19:07.299 align:start position:0% over here and then one over here and a 00:19:07.299 --> 00:19:09.060 align:start position:0% over here and then one over here and a Bob<00:19:07.719> over<00:19:07.929> here<00:19:08.200> created<00:19:08.559> this<00:19:08.739> and<00:19:08.950> this 00:19:09.060 --> 00:19:09.070 align:start position:0% Bob over here created this and this 00:19:09.070 --> 00:19:11.369 align:start position:0% Bob over here created this and this Charlie<00:19:09.609> created<00:19:09.940> these<00:19:10.089> two<00:19:10.359> David<00:19:11.049> created 00:19:11.369 --> 00:19:11.379 align:start position:0% Charlie created these two David created 00:19:11.379 --> 00:19:13.229 align:start position:0% Charlie created these two David created this<00:19:11.499> one<00:19:11.769> but<00:19:11.979> then<00:19:12.190> David<00:19:12.940> might<00:19:13.119> have 00:19:13.229 --> 00:19:13.239 align:start position:0% this one but then David might have 00:19:13.239 --> 00:19:15.119 align:start position:0% this one but then David might have dropped<00:19:13.509> off<00:19:13.719> line<00:19:13.989> so<00:19:14.320> he's<00:19:14.440> got<00:19:14.619> nothing 00:19:15.119 --> 00:19:15.129 align:start position:0% dropped off line so he's got nothing 00:19:15.129 --> 00:19:17.039 align:start position:0% dropped off line so he's got nothing over<00:19:15.219> here<00:19:15.549> so<00:19:15.820> this<00:19:15.969> is<00:19:16.119> his<00:19:16.239> most<00:19:16.450> recent<00:19:16.659> one 00:19:17.039 --> 00:19:17.049 align:start position:0% over here so this is his most recent one 00:19:17.049 --> 00:19:18.989 align:start position:0% over here so this is his most recent one and<00:19:17.259> Evan<00:19:17.950> created<00:19:18.309> two<00:19:18.429> blocks<00:19:18.729> and<00:19:18.879> that's 00:19:18.989 --> 00:19:18.999 align:start position:0% and Evan created two blocks and that's 00:19:18.999 --> 00:19:21.869 align:start position:0% and Evan created two blocks and that's his<00:19:19.389> more<00:19:19.599> recent<00:19:19.719> one<00:19:20.080> so<00:19:20.649> what<00:19:21.369> we<00:19:21.489> do<00:19:21.669> first 00:19:21.869 --> 00:19:21.879 align:start position:0% his more recent one so what we do first 00:19:21.879 --> 00:19:23.549 align:start position:0% his more recent one so what we do first is<00:19:22.149> we<00:19:22.209> only<00:19:22.509> look<00:19:22.899> at<00:19:23.080> the<00:19:23.229> most<00:19:23.409> recent 00:19:23.549 --> 00:19:23.559 align:start position:0% is we only look at the most recent 00:19:23.559 --> 00:19:25.589 align:start position:0% is we only look at the most recent blocks<00:19:24.190> from<00:19:24.369> each<00:19:24.549> individual<00:19:25.089> validator 00:19:25.589 --> 00:19:25.599 align:start position:0% blocks from each individual validator 00:19:25.599 --> 00:19:28.949 align:start position:0% blocks from each individual validator would<00:19:26.109> you<00:19:26.580> basically<00:19:27.580> means<00:19:27.879> this<00:19:28.269> this<00:19:28.749> does 00:19:28.949 --> 00:19:28.959 align:start position:0% would you basically means this this does 00:19:28.959 --> 00:19:33.119 align:start position:0% would you basically means this this does this<00:19:29.169> and<00:19:30.929> we<00:19:31.929> run<00:19:32.229> through<00:19:32.440> the<00:19:32.589> exact<00:19:33.009> same 00:19:33.119 --> 00:19:33.129 align:start position:0% this and we run through the exact same 00:19:33.129 --> 00:19:36.899 align:start position:0% this and we run through the exact same process<00:19:33.549> but<00:19:34.330> only<00:19:34.889> using<00:19:35.889> those<00:19:36.190> five<00:19:36.519> blocks 00:19:36.899 --> 00:19:36.909 align:start position:0% process but only using those five blocks 00:19:36.909 --> 00:19:38.819 align:start position:0% process but only using those five blocks two<00:19:37.149> counts<00:19:37.450> toward<00:19:37.779> the<00:19:37.899> weight<00:19:38.049> right<00:19:38.589> so 00:19:38.819 --> 00:19:38.829 align:start position:0% two counts toward the weight right so 00:19:38.829 --> 00:19:40.799 align:start position:0% two counts toward the weight right so over<00:19:39.039> here<00:19:39.279> you<00:19:39.399> start<00:19:39.700> from<00:19:39.849> the<00:19:39.999> root<00:19:40.119> one 00:19:40.799 --> 00:19:40.809 align:start position:0% over here you start from the root one 00:19:40.809 --> 00:19:43.199 align:start position:0% over here you start from the root one child<00:19:41.109> go<00:19:41.440> over<00:19:41.589> here<00:19:41.950> then<00:19:42.399> over<00:19:42.609> here<00:19:42.639> this 00:19:43.199 --> 00:19:43.209 align:start position:0% child go over here then over here this 00:19:43.209 --> 00:19:44.729 align:start position:0% child go over here then over here this side<00:19:43.419> you<00:19:43.599> have<00:19:43.749> a<00:19:43.779> score<00:19:44.079> of<00:19:44.139> one<00:19:44.409> on<00:19:44.559> this 00:19:44.729 --> 00:19:44.739 align:start position:0% side you have a score of one on this 00:19:44.739 --> 00:19:46.829 align:start position:0% side you have a score of one on this idea<00:19:45.039> of<00:19:45.129> a<00:19:45.190> score<00:19:45.459> of<00:19:45.489> 1<00:19:45.729> 2<00:19:45.879> 3<00:19:46.029> 4<00:19:46.359> you<00:19:46.389> go<00:19:46.659> over 00:19:46.829 --> 00:19:46.839 align:start position:0% idea of a score of 1 2 3 4 you go over 00:19:46.839 --> 00:19:49.229 align:start position:0% idea of a score of 1 2 3 4 you go over here<00:19:47.169> then<00:19:47.799> you<00:19:47.919> go<00:19:48.070> here<00:19:48.429> and<00:19:48.609> then<00:19:48.759> score<00:19:49.149> of 00:19:49.229 --> 00:19:49.239 align:start position:0% here then you go here and then score of 00:19:49.239 --> 00:19:51.180 align:start position:0% here then you go here and then score of 1<00:19:49.389> score<00:19:49.659> of<00:19:49.749> 1<00:19:49.899> score<00:19:50.200> of<00:19:50.289> two<00:19:50.499> go<00:19:50.769> here<00:19:51.039> and 00:19:51.180 --> 00:19:51.190 align:start position:0% 1 score of 1 score of two go here and 00:19:51.190 --> 00:19:52.289 align:start position:0% 1 score of 1 score of two go here and here<00:19:51.399> and<00:19:51.549> that's<00:19:51.729> the<00:19:51.820> head 00:19:52.289 --> 00:19:52.299 align:start position:0% here and that's the head 00:19:52.299 --> 00:19:57.629 align:start position:0% here and that's the head now<00:19:54.659> for<00:19:55.659> now<00:19:55.839> we're<00:19:56.469> assuming<00:19:56.769> a<00:19:57.009> simple<00:19:57.429> kind 00:19:57.629 --> 00:19:57.639 align:start position:0% now for now we're assuming a simple kind 00:19:57.639 --> 00:20:00.029 align:start position:0% now for now we're assuming a simple kind of<00:19:57.759> model<00:19:58.149> where<00:19:58.329> what<00:19:58.869> I<00:19:58.899> call<00:19:59.169> blocks<00:19:59.589> and 00:20:00.029 --> 00:20:00.039 align:start position:0% of model where what I call blocks and 00:20:00.039 --> 00:20:01.769 align:start position:0% of model where what I call blocks and what<00:20:00.279> I<00:20:00.309> call<00:20:00.519> messages<00:20:00.999> are<00:20:01.179> the<00:20:01.299> same<00:20:01.509> thing 00:20:01.769 --> 00:20:01.779 align:start position:0% what I call messages are the same thing 00:20:01.779 --> 00:20:04.349 align:start position:0% what I call messages are the same thing right<00:20:02.109> ends<00:20:02.709> basically<00:20:03.669> so<00:20:03.849> in<00:20:03.969> this<00:20:04.089> case 00:20:04.349 --> 00:20:04.359 align:start position:0% right ends basically so in this case 00:20:04.359 --> 00:20:06.209 align:start position:0% right ends basically so in this case blocks<00:20:04.989> are<00:20:05.259> serving<00:20:05.649> a<00:20:05.739> kind<00:20:05.950> of<00:20:06.009> dual 00:20:06.209 --> 00:20:06.219 align:start position:0% blocks are serving a kind of dual 00:20:06.219 --> 00:20:08.789 align:start position:0% blocks are serving a kind of dual purpose<00:20:06.639> one<00:20:07.329> of<00:20:07.479> them<00:20:07.629> is<00:20:07.839> that<00:20:07.989> blocks<00:20:08.379> are 00:20:08.789 --> 00:20:08.799 align:start position:0% purpose one of them is that blocks are 00:20:08.799 --> 00:20:10.709 align:start position:0% purpose one of them is that blocks are kind<00:20:09.099> of<00:20:09.219> entries<00:20:09.609> in<00:20:09.849> this<00:20:09.969> graph<00:20:10.239> structure 00:20:10.709 --> 00:20:10.719 align:start position:0% kind of entries in this graph structure 00:20:10.719 --> 00:20:13.049 align:start position:0% kind of entries in this graph structure and<00:20:10.959> like<00:20:11.619> your<00:20:11.769> fork<00:20:12.070> choices<00:20:12.489> walking<00:20:12.849> along 00:20:13.049 --> 00:20:13.059 align:start position:0% and like your fork choices walking along 00:20:13.059 --> 00:20:14.969 align:start position:0% and like your fork choices walking along the<00:20:13.209> blocks<00:20:13.419> but<00:20:14.200> the<00:20:14.259> other<00:20:14.499> rule<00:20:14.829> that 00:20:14.969 --> 00:20:14.979 align:start position:0% the blocks but the other rule that 00:20:14.979 --> 00:20:16.859 align:start position:0% the blocks but the other rule that blocks<00:20:15.249> have<00:20:15.459> is<00:20:15.609> watch<00:20:15.820> they're<00:20:16.029> voting<00:20:16.359> now 00:20:16.859 --> 00:20:16.869 align:start position:0% blocks have is watch they're voting now 00:20:16.869 --> 00:20:20.310 align:start position:0% blocks have is watch they're voting now in<00:20:17.349> LMZ<00:20:18.099> ghosts<00:20:18.369> as<00:20:18.700> we<00:20:18.999> use<00:20:19.269> it<00:20:19.479> blog<00:20:20.079> sent 00:20:20.310 --> 00:20:20.320 align:start position:0% in LMZ ghosts as we use it blog sent 00:20:20.320 --> 00:20:22.169 align:start position:0% in LMZ ghosts as we use it blog sent messages<00:20:20.679> will<00:20:20.859> be<00:20:20.950> split<00:20:21.249> and<00:20:21.489> I<00:20:21.909> will<00:20:22.029> get 00:20:22.169 --> 00:20:22.179 align:start position:0% messages will be split and I will get 00:20:22.179 --> 00:20:25.849 align:start position:0% messages will be split and I will get into<00:20:22.479> this<00:20:22.809> and<00:20:23.169> why<00:20:24.129> we<00:20:24.339> do<00:20:24.489> this<00:20:24.609> later 00:20:25.849 --> 00:20:25.859 align:start position:0% into this and why we do this later 00:20:25.859 --> 00:20:29.069 align:start position:0% into this and why we do this later so<00:20:26.859> as<00:20:27.099> in<00:20:27.369> ghost<00:20:27.940> start<00:20:28.329> from<00:20:28.479> the<00:20:28.629> Genesis 00:20:29.069 --> 00:20:29.079 align:start position:0% so as in ghost start from the Genesis 00:20:29.079 --> 00:20:31.049 align:start position:0% so as in ghost start from the Genesis walk<00:20:29.320> up<00:20:29.499> the<00:20:29.649> tree<00:20:29.889> at<00:20:30.249> each<00:20:30.399> branch<00:20:30.669> choose 00:20:31.049 --> 00:20:31.059 align:start position:0% walk up the tree at each branch choose 00:20:31.059 --> 00:20:33.299 align:start position:0% walk up the tree at each branch choose the<00:20:31.269> child<00:20:31.509> that<00:20:31.659> has<00:20:31.839> more<00:20:32.169> latest<00:20:32.950> message 00:20:33.299 --> 00:20:33.309 align:start position:0% the child that has more latest message 00:20:33.309 --> 00:20:35.549 align:start position:0% the child that has more latest message latest<00:20:33.999> messages<00:20:34.389> supporting<00:20:34.899> it<00:20:35.049> and<00:20:35.289> keep 00:20:35.549 --> 00:20:35.559 align:start position:0% latest messages supporting it and keep 00:20:35.559 --> 00:20:40.680 align:start position:0% latest messages supporting it and keep going<00:20:35.589> until<00:20:35.950> you<00:20:36.279> find<00:20:36.519> the<00:20:36.639> head<00:20:36.989> so<00:20:39.149> why<00:20:40.149> LM 00:20:40.680 --> 00:20:40.690 align:start position:0% going until you find the head so why LM 00:20:40.690 --> 00:20:44.699 align:start position:0% going until you find the head so why LM D<00:20:40.839> ghost<00:20:41.079> right<00:20:41.649> the<00:20:42.609> so<00:20:43.119> this<00:20:43.469> here<00:20:44.469> were 00:20:44.699 --> 00:20:44.709 align:start position:0% D ghost right the so this here were 00:20:44.709 --> 00:20:47.009 align:start position:0% D ghost right the so this here were interred<00:20:45.190> bringing<00:20:45.609> back<00:20:45.820> kind<00:20:46.179> of<00:20:46.239> LM<00:20:46.869> t 00:20:47.009 --> 00:20:47.019 align:start position:0% interred bringing back kind of LM t 00:20:47.019 --> 00:20:49.979 align:start position:0% interred bringing back kind of LM t ghost<00:20:47.259> as<00:20:47.499> more<00:20:48.489> like<00:20:48.700> it<00:20:48.849> actually<00:20:48.969> exists<00:20:49.749> in 00:20:49.979 --> 00:20:49.989 align:start position:0% ghost as more like it actually exists in 00:20:49.989 --> 00:20:53.249 align:start position:0% ghost as more like it actually exists in aetherium<00:20:50.769> 2.0<00:20:51.309> and<00:20:51.639> what<00:20:52.450> we<00:20:52.539> have<00:20:52.749> here<00:20:53.109> is 00:20:53.249 --> 00:20:53.259 align:start position:0% aetherium 2.0 and what we have here is 00:20:53.259 --> 00:20:56.069 align:start position:0% aetherium 2.0 and what we have here is he<00:20:53.409> have<00:20:53.619> blocks<00:20:54.039> and<00:20:54.369> votes<00:20:55.149> on<00:20:55.509> a<00:20:55.779> key<00:20:56.049> a 00:20:56.069 --> 00:20:56.079 align:start position:0% he have blocks and votes on a key a 00:20:56.079 --> 00:20:58.560 align:start position:0% he have blocks and votes on a key a attestations<00:20:56.709> as<00:20:57.219> kind<00:20:57.999> of<00:20:58.029> three<00:20:58.239> separate 00:20:58.560 --> 00:20:58.570 align:start position:0% attestations as kind of three separate 00:20:58.570 --> 00:21:00.839 align:start position:0% attestations as kind of three separate concepts<00:20:59.200> right<00:20:59.409> so<00:20:59.979> you<00:21:00.039> have<00:21:00.219> a<00:21:00.279> block<00:21:00.609> and 00:21:00.839 --> 00:21:00.849 align:start position:0% concepts right so you have a block and 00:21:00.849 --> 00:21:02.369 align:start position:0% concepts right so you have a block and then<00:21:01.149> you<00:21:01.239> have<00:21:01.389> five<00:21:01.690> votes<00:21:01.929> you<00:21:02.259> have<00:21:02.349> a 00:21:02.369 --> 00:21:02.379 align:start position:0% then you have five votes you have a 00:21:02.379 --> 00:21:05.099 align:start position:0% then you have five votes you have a blocking<00:21:02.889> or<00:21:03.099> like<00:21:03.639> in<00:21:03.999> reality<00:21:04.690> this<00:21:04.869> might 00:21:05.099 --> 00:21:05.109 align:start position:0% blocking or like in reality this might 00:21:05.109 --> 00:21:08.039 align:start position:0% blocking or like in reality this might be<00:21:05.289> could<00:21:05.499> be<00:21:05.529> anywhere<00:21:06.009> up<00:21:06.070> to<00:21:06.940> about<00:21:07.269> 50,000 00:21:08.039 --> 00:21:08.049 align:start position:0% be could be anywhere up to about 50,000 00:21:08.049 --> 00:21:09.749 align:start position:0% be could be anywhere up to about 50,000 votes<00:21:08.200> then<00:21:08.859> you<00:21:08.950> have<00:21:09.099> a<00:21:09.129> block<00:21:09.399> you<00:21:09.429> have<00:21:09.609> a 00:21:09.749 --> 00:21:09.759 align:start position:0% votes then you have a block you have a 00:21:09.759 --> 00:21:11.999 align:start position:0% votes then you have a block you have a huge<00:21:09.969> pile<00:21:10.179> of<00:21:10.209> votes<00:21:10.539> a<00:21:10.839> blog<00:21:11.349> a<00:21:11.559> huge<00:21:11.769> pile<00:21:11.979> of 00:21:11.999 --> 00:21:12.009 align:start position:0% huge pile of votes a blog a huge pile of 00:21:12.009 --> 00:21:14.430 align:start position:0% huge pile of votes a blog a huge pile of votes<00:21:12.369> now<00:21:13.210> over<00:21:13.479> here<00:21:13.690> you<00:21:13.749> might<00:21:13.899> have<00:21:14.229> two 00:21:14.430 --> 00:21:14.440 align:start position:0% votes now over here you might have two 00:21:14.440 --> 00:21:17.099 align:start position:0% votes now over here you might have two different<00:21:14.649> competing<00:21:15.070> blocks<00:21:15.549> and<00:21:16.109> this 00:21:17.099 --> 00:21:17.109 align:start position:0% different competing blocks and this 00:21:17.109 --> 00:21:17.470 align:start position:0% different competing blocks and this could 00:21:17.470 --> 00:21:17.480 align:start position:0% could 00:21:17.480 --> 00:21:19.270 align:start position:0% could because<00:21:18.049> one<00:21:18.380> of<00:21:18.410> the<00:21:18.590> blocks<00:21:18.830> just<00:21:19.130> got 00:21:19.270 --> 00:21:19.280 align:start position:0% because one of the blocks just got 00:21:19.280 --> 00:21:20.919 align:start position:0% because one of the blocks just got delayed<00:21:19.640> and<00:21:19.940> the<00:21:20.030> other<00:21:20.150> boy<00:21:20.330> and<00:21:20.540> then<00:21:20.690> the 00:21:20.919 --> 00:21:20.929 align:start position:0% delayed and the other boy and then the 00:21:20.929 --> 00:21:22.299 align:start position:0% delayed and the other boy and then the next<00:21:21.140> proposed<00:21:21.410> who<00:21:21.590> created<00:21:21.830> the<00:21:21.919> block<00:21:22.160> and 00:21:22.299 --> 00:21:22.309 align:start position:0% next proposed who created the block and 00:21:22.309 --> 00:21:24.039 align:start position:0% next proposed who created the block and this<00:21:22.429> block<00:21:22.490> appeared<00:21:23.120> this<00:21:23.660> could<00:21:23.900> be 00:21:24.039 --> 00:21:24.049 align:start position:0% this block appeared this could be 00:21:24.049 --> 00:21:25.810 align:start position:0% this block appeared this could be because<00:21:24.230> a<00:21:24.380> proposer<00:21:24.860> was<00:21:25.190> malicious<00:21:25.669> and 00:21:25.810 --> 00:21:25.820 align:start position:0% because a proposer was malicious and 00:21:25.820 --> 00:21:27.340 align:start position:0% because a proposer was malicious and created<00:21:26.120> two<00:21:26.240> competing<00:21:26.570> blocks<00:21:26.900> we<00:21:27.169> don't 00:21:27.340 --> 00:21:27.350 align:start position:0% created two competing blocks we don't 00:21:27.350 --> 00:21:31.210 align:start position:0% created two competing blocks we don't know<00:21:27.760> so<00:21:28.760> now<00:21:29.650> everyone<00:21:30.650> who's<00:21:30.860> voting 00:21:31.210 --> 00:21:31.220 align:start position:0% know so now everyone who's voting 00:21:31.220 --> 00:21:32.710 align:start position:0% know so now everyone who's voting chooses<00:21:31.580> either<00:21:31.730> this<00:21:32.090> side<00:21:32.150> or<00:21:32.360> this<00:21:32.510> side 00:21:32.710 --> 00:21:32.720 align:start position:0% chooses either this side or this side 00:21:32.720 --> 00:21:35.169 align:start position:0% chooses either this side or this side and<00:21:33.500> if<00:21:33.950> they<00:21:34.070> choose<00:21:34.250> this<00:21:34.520> side<00:21:34.760> then<00:21:35.150> this 00:21:35.169 --> 00:21:35.179 align:start position:0% and if they choose this side then this 00:21:35.179 --> 00:21:37.810 align:start position:0% and if they choose this side then this block<00:21:35.570> wins<00:21:35.950> and<00:21:36.950> then<00:21:37.190> you<00:21:37.340> keep<00:21:37.520> on<00:21:37.610> going 00:21:37.810 --> 00:21:37.820 align:start position:0% block wins and then you keep on going 00:21:37.820 --> 00:21:42.130 align:start position:0% block wins and then you keep on going right<00:21:38.750> so<00:21:39.640> the<00:21:40.640> ghost<00:21:40.880> fork<00:21:41.270> choice<00:21:41.450> rule<00:21:41.870> is 00:21:42.130 --> 00:21:42.140 align:start position:0% right so the ghost fork choice rule is 00:21:42.140 --> 00:21:44.860 align:start position:0% right so the ghost fork choice rule is going<00:21:42.830> to<00:21:42.950> be<00:21:43.040> counting<00:21:43.520> these<00:21:43.730> the<00:21:44.600> antis 00:21:44.860 --> 00:21:44.870 align:start position:0% going to be counting these the antis 00:21:44.870 --> 00:21:47.289 align:start position:0% going to be counting these the antis Nations<00:21:45.260> and<00:21:45.980> specifically<00:21:46.760> it<00:21:46.940> counts 00:21:47.289 --> 00:21:47.299 align:start position:0% Nations and specifically it counts 00:21:47.299 --> 00:21:50.020 align:start position:0% Nations and specifically it counts latest<00:21:47.750> data<00:21:47.900> stations<00:21:48.440> so<00:21:49.070> if<00:21:49.370> this<00:21:49.610> like<00:21:49.880> if 00:21:50.020 --> 00:21:50.030 align:start position:0% latest data stations so if this like if 00:21:50.030 --> 00:21:51.850 align:start position:0% latest data stations so if this like if this<00:21:50.150> is<00:21:50.210> all<00:21:50.510> inside<00:21:50.900> of<00:21:51.080> one<00:21:51.230> epoch<00:21:51.559> then 00:21:51.850 --> 00:21:51.860 align:start position:0% this is all inside of one epoch then 00:21:51.860 --> 00:21:53.350 align:start position:0% this is all inside of one epoch then there's<00:21:52.040> no<00:21:52.190> difference<00:21:52.640> because<00:21:52.790> everyone 00:21:53.350 --> 00:21:53.360 align:start position:0% there's no difference because everyone 00:21:53.360 --> 00:21:55.360 align:start position:0% there's no difference because everyone only<00:21:53.540> votes<00:21:53.809> once<00:21:54.080> per<00:21:54.290> you<00:21:54.410> park<00:21:54.620> but<00:21:55.160> if<00:21:55.250> you 00:21:55.360 --> 00:21:55.370 align:start position:0% only votes once per you park but if you 00:21:55.370 --> 00:21:57.190 align:start position:0% only votes once per you park but if you imagine<00:21:55.610> that<00:21:55.850> say<00:21:56.210> this<00:21:56.480> and<00:21:56.750> this<00:21:56.840> are<00:21:57.049> two 00:21:57.190 --> 00:21:57.200 align:start position:0% imagine that say this and this are two 00:21:57.200 --> 00:21:59.620 align:start position:0% imagine that say this and this are two separate<00:21:57.590> epochs<00:21:57.980> then<00:21:58.669> maybe<00:21:58.970> this<00:21:59.330> at<00:21:59.510> the 00:21:59.620 --> 00:21:59.630 align:start position:0% separate epochs then maybe this at the 00:21:59.630 --> 00:22:01.120 align:start position:0% separate epochs then maybe this at the station<00:21:59.870> and<00:22:00.169> this<00:22:00.260> at<00:22:00.440> the<00:22:00.590> station<00:22:00.799> come 00:22:01.120 --> 00:22:01.130 align:start position:0% station and this at the station come 00:22:01.130 --> 00:22:03.070 align:start position:0% station and this at the station come from<00:22:01.280> the<00:22:01.370> same<00:22:01.549> validator<00:22:02.059> in<00:22:02.330> which<00:22:02.840> case 00:22:03.070 --> 00:22:03.080 align:start position:0% from the same validator in which case 00:22:03.080 --> 00:22:04.630 align:start position:0% from the same validator in which case you<00:22:03.230> don't<00:22:03.260> count<00:22:03.650> this<00:22:03.890> one<00:22:04.100> but<00:22:04.309> you<00:22:04.340> count 00:22:04.630 --> 00:22:04.640 align:start position:0% you don't count this one but you count 00:22:04.640 --> 00:22:08.980 align:start position:0% you don't count this one but you count this<00:22:04.820> one<00:22:04.990> now<00:22:05.990> in<00:22:06.740> general<00:22:07.700> if<00:22:07.940> a<00:22:08.390> chain<00:22:08.690> is 00:22:08.980 --> 00:22:08.990 align:start position:0% this one now in general if a chain is 00:22:08.990 --> 00:22:13.150 align:start position:0% this one now in general if a chain is progressing<00:22:09.679> then<00:22:10.370> the<00:22:11.290> if<00:22:12.290> you<00:22:12.620> vote<00:22:12.860> once 00:22:13.150 --> 00:22:13.160 align:start position:0% progressing then the if you vote once 00:22:13.160 --> 00:22:15.850 align:start position:0% progressing then the if you vote once over<00:22:13.490> here<00:22:13.880> then<00:22:14.360> the<00:22:15.049> next<00:22:15.350> vote<00:22:15.530> that<00:22:15.770> you 00:22:15.850 --> 00:22:15.860 align:start position:0% over here then the next vote that you 00:22:15.860 --> 00:22:17.530 align:start position:0% over here then the next vote that you make<00:22:16.040> is<00:22:16.250> going<00:22:16.520> to<00:22:16.610> be<00:22:16.730> a<00:22:16.760> descendant<00:22:17.150> of<00:22:17.390> this 00:22:17.530 --> 00:22:17.540 align:start position:0% make is going to be a descendant of this 00:22:17.540 --> 00:22:19.950 align:start position:0% make is going to be a descendant of this block<00:22:17.840> right<00:22:18.140> so<00:22:18.470> most<00:22:19.250> of<00:22:19.490> the<00:22:19.640> time 00:22:19.950 --> 00:22:19.960 align:start position:0% block right so most of the time 00:22:19.960 --> 00:22:22.270 align:start position:0% block right so most of the time validators<00:22:20.960> aren't<00:22:21.320> changing<00:22:21.830> their<00:22:22.010> opinion 00:22:22.270 --> 00:22:22.280 align:start position:0% validators aren't changing their opinion 00:22:22.280 --> 00:22:24.340 align:start position:0% validators aren't changing their opinion they're<00:22:22.610> extending<00:22:23.090> their<00:22:23.120> opinion<00:22:23.630> so<00:22:23.840> if 00:22:24.340 --> 00:22:24.350 align:start position:0% they're extending their opinion so if 00:22:24.350 --> 00:22:26.530 align:start position:0% they're extending their opinion so if you<00:22:24.500> made<00:22:24.679> a<00:22:24.710> an<00:22:25.370> attestation<00:22:25.730> supporting 00:22:26.530 --> 00:22:26.540 align:start position:0% you made a an attestation supporting 00:22:26.540 --> 00:22:28.630 align:start position:0% you made a an attestation supporting this<00:22:26.630> block<00:22:26.900> then<00:22:27.140> you're<00:22:27.230> saying<00:22:27.500> my<00:22:28.160> opinion 00:22:28.630 --> 00:22:28.640 align:start position:0% this block then you're saying my opinion 00:22:28.640 --> 00:22:31.000 align:start position:0% this block then you're saying my opinion is<00:22:28.790> this<00:22:28.970> block<00:22:29.210> is<00:22:29.360> the<00:22:29.480> best<00:22:29.660> if<00:22:30.140> you<00:22:30.650> then 00:22:31.000 --> 00:22:31.010 align:start position:0% is this block is the best if you then 00:22:31.010 --> 00:22:32.860 align:start position:0% is this block is the best if you then later<00:22:31.370> make<00:22:31.730> an<00:22:31.910> attestation<00:22:32.150> over<00:22:32.630> here 00:22:32.860 --> 00:22:32.870 align:start position:0% later make an attestation over here 00:22:32.870 --> 00:22:34.720 align:start position:0% later make an attestation over here saying<00:22:33.169> my<00:22:33.470> opinion<00:22:33.830> this<00:22:33.950> block<00:22:34.220> is<00:22:34.400> the<00:22:34.520> best 00:22:34.720 --> 00:22:34.730 align:start position:0% saying my opinion this block is the best 00:22:34.730 --> 00:22:37.510 align:start position:0% saying my opinion this block is the best then<00:22:35.390> like<00:22:36.110> you're<00:22:36.559> not<00:22:36.770> disagreeing<00:22:37.490> with 00:22:37.510 --> 00:22:37.520 align:start position:0% then like you're not disagreeing with 00:22:37.520 --> 00:22:39.220 align:start position:0% then like you're not disagreeing with your<00:22:37.790> opinion<00:22:38.179> before<00:22:38.360> right<00:22:38.780> you're<00:22:39.049> an 00:22:39.220 --> 00:22:39.230 align:start position:0% your opinion before right you're an 00:22:39.230 --> 00:22:40.630 align:start position:0% your opinion before right you're an opinion<00:22:39.590> though<00:22:39.650> this<00:22:39.770> block<00:22:40.010> is<00:22:40.160> the<00:22:40.280> best<00:22:40.460> is 00:22:40.630 --> 00:22:40.640 align:start position:0% opinion though this block is the best is 00:22:40.640 --> 00:22:42.130 align:start position:0% opinion though this block is the best is also<00:22:40.940> an<00:22:41.059> NPN<00:22:41.330> you<00:22:41.419> know<00:22:41.510> this<00:22:41.660> plug<00:22:41.870> is<00:22:42.020> the 00:22:42.130 --> 00:22:42.140 align:start position:0% also an NPN you know this plug is the 00:22:42.140 --> 00:22:43.659 align:start position:0% also an NPN you know this plug is the best<00:22:42.320> and<00:22:42.620> of<00:22:42.740> this<00:22:42.860> block<00:22:43.040> is<00:22:43.160> the<00:22:43.280> best<00:22:43.490> and 00:22:43.659 --> 00:22:43.669 align:start position:0% best and of this block is the best and 00:22:43.669 --> 00:22:45.909 align:start position:0% best and of this block is the best and then<00:22:43.820> this<00:22:43.940> block<00:22:44.120> is<00:22:44.360> the<00:22:44.480> best<00:22:44.690> but<00:22:45.440> before 00:22:45.909 --> 00:22:45.919 align:start position:0% then this block is the best but before 00:22:45.919 --> 00:22:47.799 align:start position:0% then this block is the best but before you<00:22:46.460> did<00:22:46.640> not<00:22:46.790> have<00:22:47.000> an<00:22:47.150> opinion<00:22:47.360> on<00:22:47.630> these 00:22:47.799 --> 00:22:47.809 align:start position:0% you did not have an opinion on these 00:22:47.809 --> 00:22:49.570 align:start position:0% you did not have an opinion on these guys<00:22:48.049> and<00:22:48.350> now<00:22:48.470> you<00:22:48.530> do<00:22:48.799> have<00:22:49.010> an<00:22:49.130> opinion<00:22:49.309> on 00:22:49.570 --> 00:22:49.580 align:start position:0% guys and now you do have an opinion on 00:22:49.580 --> 00:22:52.390 align:start position:0% guys and now you do have an opinion on these<00:22:49.730> guys<00:22:50.290> but<00:22:51.290> maybe<00:22:51.500> you<00:22:52.100> made<00:22:52.250> an 00:22:52.390 --> 00:22:52.400 align:start position:0% these guys but maybe you made an 00:22:52.400 --> 00:22:54.400 align:start position:0% these guys but maybe you made an attestation<00:22:52.700> here<00:22:53.419> then<00:22:53.750> you<00:22:53.870> make<00:22:54.049> this<00:22:54.200> at 00:22:54.400 --> 00:22:54.410 align:start position:0% attestation here then you make this at 00:22:54.410 --> 00:22:56.409 align:start position:0% attestation here then you make this at the<00:22:54.530> station<00:22:54.980> then<00:22:55.400> you<00:22:55.520> realize<00:22:55.910> this<00:22:56.179> chain 00:22:56.409 --> 00:22:56.419 align:start position:0% the station then you realize this chain 00:22:56.419 --> 00:22:59.140 align:start position:0% the station then you realize this chain wins<00:22:56.660> and<00:22:57.020> so<00:22:57.200> at<00:22:57.410> some<00:22:57.440> point<00:22:57.650> late<00:22:58.309> at<00:22:58.910> some 00:22:59.140 --> 00:22:59.150 align:start position:0% wins and so at some point late at some 00:22:59.150 --> 00:23:00.580 align:start position:0% wins and so at some point late at some point<00:22:59.330> later<00:22:59.450> you<00:22:59.690> do<00:22:59.840> change<00:23:00.080> your<00:23:00.260> mind 00:23:00.580 --> 00:23:00.590 align:start position:0% point later you do change your mind 00:23:00.590 --> 00:23:03.180 align:start position:0% point later you do change your mind so<00:23:01.400> like<00:23:01.760> both<00:23:02.030> these<00:23:02.419> things<00:23:02.690> are<00:23:02.870> possible 00:23:03.180 --> 00:23:03.190 align:start position:0% so like both these things are possible 00:23:03.190 --> 00:23:06.400 align:start position:0% so like both these things are possible now<00:23:04.190> the<00:23:04.250> reason<00:23:05.000> why<00:23:05.299> we<00:23:05.330> do<00:23:05.750> this<00:23:05.780> is<00:23:06.200> because 00:23:06.400 --> 00:23:06.410 align:start position:0% now the reason why we do this is because 00:23:06.410 --> 00:23:09.039 align:start position:0% now the reason why we do this is because this<00:23:07.340> allows<00:23:07.669> basically<00:23:08.630> parallel 00:23:09.039 --> 00:23:09.049 align:start position:0% this allows basically parallel 00:23:09.049 --> 00:23:12.250 align:start position:0% this allows basically parallel confirmations<00:23:09.830> right<00:23:10.340> so<00:23:10.700> in<00:23:11.510> a<00:23:11.900> kind<00:23:12.110> of 00:23:12.250 --> 00:23:12.260 align:start position:0% confirmations right so in a kind of 00:23:12.260 --> 00:23:14.140 align:start position:0% confirmations right so in a kind of probabilistic<00:23:12.890> for<00:23:13.370> curious<00:23:13.669> role<00:23:13.880> there<00:23:14.059> is 00:23:14.140 --> 00:23:14.150 align:start position:0% probabilistic for curious role there is 00:23:14.150 --> 00:23:16.000 align:start position:0% probabilistic for curious role there is this<00:23:14.299> general<00:23:14.690> concept<00:23:15.200> of<00:23:15.260> confirmations 00:23:16.000 --> 00:23:16.010 align:start position:0% this general concept of confirmations 00:23:16.010 --> 00:23:18.990 align:start position:0% this general concept of confirmations like<00:23:16.280> basically<00:23:16.850> how<00:23:17.480> many<00:23:17.809> kind<00:23:18.169> of<00:23:18.230> units<00:23:18.650> of 00:23:18.990 --> 00:23:19.000 align:start position:0% like basically how many kind of units of 00:23:19.000 --> 00:23:21.490 align:start position:0% like basically how many kind of units of information<00:23:20.000> in<00:23:20.240> favor<00:23:20.570> of<00:23:20.840> a<00:23:20.929> block<00:23:21.230> are 00:23:21.490 --> 00:23:21.500 align:start position:0% information in favor of a block are 00:23:21.500 --> 00:23:24.190 align:start position:0% information in favor of a block are there<00:23:21.740> and<00:23:22.610> how<00:23:22.910> many<00:23:22.940> gee<00:23:23.330> wants<00:23:23.630> to<00:23:23.750> wait<00:23:23.900> for 00:23:24.190 --> 00:23:24.200 align:start position:0% there and how many gee wants to wait for 00:23:24.200 --> 00:23:26.289 align:start position:0% there and how many gee wants to wait for to<00:23:24.410> achieve<00:23:24.530> a<00:23:24.860> certain<00:23:25.130> degree<00:23:25.280> of<00:23:25.520> safety<00:23:25.700> in 00:23:26.289 --> 00:23:26.299 align:start position:0% to achieve a certain degree of safety in 00:23:26.299 --> 00:23:29.830 align:start position:0% to achieve a certain degree of safety in Bitcoin<00:23:27.110> you<00:23:27.320> would<00:23:27.409> wait<00:23:27.590> for<00:23:27.620> six<00:23:28.150> and<00:23:29.150> that 00:23:29.830 --> 00:23:29.840 align:start position:0% Bitcoin you would wait for six and that 00:23:29.840 --> 00:23:31.240 align:start position:0% Bitcoin you would wait for six and that means<00:23:30.080> waiting<00:23:30.380> for<00:23:30.650> six 00:23:31.240 --> 00:23:31.250 align:start position:0% means waiting for six 00:23:31.250 --> 00:23:33.669 align:start position:0% means waiting for six in<00:23:31.820> etherium<00:23:32.419> like<00:23:32.840> you<00:23:32.960> would<00:23:33.049> wait<00:23:33.230> for<00:23:33.260> 12 00:23:33.669 --> 00:23:33.679 align:start position:0% in etherium like you would wait for 12 00:23:33.679 --> 00:23:36.490 align:start position:0% in etherium like you would wait for 12 so<00:23:33.980> you'd<00:23:34.130> wait<00:23:34.309> for<00:23:34.490> 12<00:23:34.730> blocks<00:23:34.970> but<00:23:35.690> here<00:23:36.110> you 00:23:36.490 --> 00:23:36.500 align:start position:0% so you'd wait for 12 blocks but here you 00:23:36.500 --> 00:23:38.440 align:start position:0% so you'd wait for 12 blocks but here you basically<00:23:36.650> get<00:23:37.190> tens<00:23:37.700> of<00:23:37.850> thousands<00:23:38.240> of<00:23:38.299> at 00:23:38.440 --> 00:23:38.450 align:start position:0% basically get tens of thousands of at 00:23:38.450 --> 00:23:40.299 align:start position:0% basically get tens of thousands of at the<00:23:38.600> station's<00:23:39.020> happening<00:23:39.470> in<00:23:39.559> parallel<00:23:39.860> and 00:23:40.299 --> 00:23:40.309 align:start position:0% the station's happening in parallel and 00:23:40.309 --> 00:23:43.299 align:start position:0% the station's happening in parallel and so<00:23:40.880> you<00:23:41.480> get<00:23:41.750> a<00:23:41.929> very<00:23:42.260> high<00:23:42.350> assurance<00:23:42.679> that<00:23:43.280> a 00:23:43.299 --> 00:23:43.309 align:start position:0% so you get a very high assurance that a 00:23:43.309 --> 00:23:45.789 align:start position:0% so you get a very high assurance that a block<00:23:43.580> is<00:23:44.110> overwhelmingly<00:23:45.110> likely<00:23:45.440> to<00:23:45.679> be 00:23:45.789 --> 00:23:45.799 align:start position:0% block is overwhelmingly likely to be 00:23:45.799 --> 00:23:48.190 align:start position:0% block is overwhelmingly likely to be included<00:23:46.250> in<00:23:46.340> the<00:23:46.460> chain<00:23:46.730> pretty<00:23:47.510> much<00:23:47.750> like 00:23:48.190 --> 00:23:48.200 align:start position:0% included in the chain pretty much like 00:23:48.200 --> 00:23:50.080 align:start position:0% included in the chain pretty much like in<00:23:48.470> the<00:23:48.620> average<00:23:48.950> case<00:23:49.159> after<00:23:49.460> one<00:23:49.850> single 00:23:50.080 --> 00:23:50.090 align:start position:0% in the average case after one single 00:23:50.090 --> 00:23:53.590 align:start position:0% in the average case after one single SWAT<00:23:50.510> so<00:23:51.320> the<00:23:52.190> goal<00:23:52.400> here<00:23:52.700> basically<00:23:52.940> is<00:23:53.419> to 00:23:53.590 --> 00:23:53.600 align:start position:0% SWAT so the goal here basically is to 00:23:53.600 --> 00:23:55.840 align:start position:0% SWAT so the goal here basically is to give<00:23:53.780> the<00:23:54.320> same<00:23:54.559> level<00:23:54.950> of<00:23:55.010> security<00:23:55.340> after 00:23:55.840 --> 00:23:55.850 align:start position:0% give the same level of security after 00:23:55.850 --> 00:23:58.539 align:start position:0% give the same level of security after ten<00:23:56.090> seconds<00:23:56.539> that<00:23:56.750> a<00:23:57.549> traditional 00:23:58.539 --> 00:23:58.549 align:start position:0% ten seconds that a traditional 00:23:58.549 --> 00:23:59.919 align:start position:0% ten seconds that a traditional proof-of-work<00:23:58.909> chain<00:23:59.330> would<00:23:59.480> only<00:23:59.630> give 00:23:59.919 --> 00:23:59.929 align:start position:0% proof-of-work chain would only give 00:23:59.929 --> 00:24:02.740 align:start position:0% proof-of-work chain would only give after<00:24:00.169> minutes<00:24:00.620> or<00:24:00.740> hours<00:24:01.010> and<00:24:02.000> because<00:24:02.570> you 00:24:02.740 --> 00:24:02.750 align:start position:0% after minutes or hours and because you 00:24:02.750 --> 00:24:04.210 align:start position:0% after minutes or hours and because you have<00:24:02.900> messages<00:24:03.140> happening<00:24:03.799> in<00:24:03.919> parallel 00:24:04.210 --> 00:24:04.220 align:start position:0% have messages happening in parallel 00:24:04.220 --> 00:24:06.430 align:start position:0% have messages happening in parallel there's<00:24:04.850> no<00:24:05.090> way<00:24:05.360> that<00:24:05.600> all<00:24:05.659> of<00:24:05.900> them<00:24:06.049> are<00:24:06.200> like 00:24:06.430 --> 00:24:06.440 align:start position:0% there's no way that all of them are like 00:24:06.440 --> 00:24:08.260 align:start position:0% there's no way that all of them are like you<00:24:06.620> can<00:24:06.799> even<00:24:07.070> possibly<00:24:07.610> make<00:24:07.850> all<00:24:08.000> of<00:24:08.030> them 00:24:08.260 --> 00:24:08.270 align:start position:0% you can even possibly make all of them 00:24:08.270 --> 00:24:11.049 align:start position:0% you can even possibly make all of them form<00:24:08.510> a<00:24:08.630> chain<00:24:08.870> if<00:24:09.110> you<00:24:09.200> try<00:24:09.500> and<00:24:09.890> so<00:24:10.100> a<00:24:10.429> longest 00:24:11.049 --> 00:24:11.059 align:start position:0% form a chain if you try and so a longest 00:24:11.059 --> 00:24:13.480 align:start position:0% form a chain if you try and so a longest chain<00:24:11.330> rule<00:24:11.570> was<00:24:11.659> not<00:24:11.809> even<00:24:11.990> sensible<00:24:12.620> and<00:24:12.890> LMD 00:24:13.480 --> 00:24:13.490 align:start position:0% chain rule was not even sensible and LMD 00:24:13.490 --> 00:24:16.810 align:start position:0% chain rule was not even sensible and LMD go<00:24:13.669> strength<00:24:14.090> is<00:24:14.510> the<00:24:15.049> obvious<00:24:15.500> approach<00:24:15.860> for 00:24:16.810 --> 00:24:16.820 align:start position:0% go strength is the obvious approach for 00:24:16.820 --> 00:24:18.850 align:start position:0% go strength is the obvious approach for how<00:24:17.090> to<00:24:17.150> have<00:24:17.750> taken<00:24:18.230> to<00:24:18.380> account<00:24:18.650> the 00:24:18.850 --> 00:24:18.860 align:start position:0% how to have taken to account the 00:24:18.860 --> 00:24:23.080 align:start position:0% how to have taken to account the information<00:24:19.460> from<00:24:19.789> all<00:24:20.120> of<00:24:20.270> these<00:24:20.419> validators 00:24:23.080 --> 00:24:23.090 align:start position:0% 00:24:23.090 --> 00:24:27.039 align:start position:0% so<00:24:24.020> why<00:24:24.230> LMD<00:24:24.650> ghost<00:24:24.890> right<00:24:25.220> so<00:24:25.520> one<00:24:26.419> reason<00:24:26.630> is 00:24:27.039 --> 00:24:27.049 align:start position:0% so why LMD ghost right so one reason is 00:24:27.049 --> 00:24:29.620 align:start position:0% so why LMD ghost right so one reason is that<00:24:27.080> the<00:24:27.830> longest<00:24:28.130> longest<00:24:28.820> chain<00:24:29.090> rules 00:24:29.620 --> 00:24:29.630 align:start position:0% that the longest longest chain rules 00:24:29.630 --> 00:24:31.779 align:start position:0% that the longest longest chain rules cannot<00:24:30.140> take<00:24:30.409> into<00:24:30.980> account<00:24:31.250> information 00:24:31.779 --> 00:24:31.789 align:start position:0% cannot take into account information 00:24:31.789 --> 00:24:34.899 align:start position:0% cannot take into account information from<00:24:32.270> parallel<00:24:32.659> testers<00:24:33.230> and<00:24:33.580> ghost<00:24:34.580> based 00:24:34.899 --> 00:24:34.909 align:start position:0% from parallel testers and ghost based 00:24:34.909 --> 00:24:38.140 align:start position:0% from parallel testers and ghost based rules<00:24:35.240> that<00:24:35.510> do<00:24:36.250> another<00:24:37.250> interesting 00:24:38.140 --> 00:24:38.150 align:start position:0% rules that do another interesting 00:24:38.150 --> 00:24:40.899 align:start position:0% rules that do another interesting property<00:24:38.419> that<00:24:38.870> LMG<00:24:39.320> ghost<00:24:39.559> has<00:24:39.890> is<00:24:40.490> it<00:24:40.730> has<00:24:40.760> a 00:24:40.899 --> 00:24:40.909 align:start position:0% property that LMG ghost has is it has a 00:24:40.909 --> 00:24:42.820 align:start position:0% property that LMG ghost has is it has a property<00:24:41.450> that<00:24:41.539> the<00:24:41.840> minority<00:24:42.020> can<00:24:42.590> never 00:24:42.820 --> 00:24:42.830 align:start position:0% property that the minority can never 00:24:42.830 --> 00:24:45.070 align:start position:0% property that the minority can never beat<00:24:43.100> the<00:24:43.250> majority<00:24:43.789> regardless<00:24:44.720> of<00:24:44.870> how<00:24:45.020> many 00:24:45.070 --> 00:24:45.080 align:start position:0% beat the majority regardless of how many 00:24:45.080 --> 00:24:48.039 align:start position:0% beat the majority regardless of how many messages<00:24:45.679> they<00:24:45.830> sign<00:24:46.070> right<00:24:46.580> so<00:24:47.240> for<00:24:47.480> example 00:24:48.039 --> 00:24:48.049 align:start position:0% messages they sign right so for example 00:24:48.049 --> 00:24:50.980 align:start position:0% messages they sign right so for example suppose<00:24:49.010> that<00:24:49.039> you<00:24:49.370> have<00:24:49.610> like<00:24:49.909> a<00:24:50.030> structure 00:24:50.980 --> 00:24:50.990 align:start position:0% suppose that you have like a structure 00:24:50.990 --> 00:24:54.669 align:start position:0% suppose that you have like a structure that<00:24:51.020> looks<00:24:51.320> like<00:24:51.530> this<00:24:51.770> and<00:24:52.549> then<00:24:53.020> base<00:24:54.020> so 00:24:54.669 --> 00:24:54.679 align:start position:0% that looks like this and then base so 00:24:54.679 --> 00:24:56.649 align:start position:0% that looks like this and then base so you<00:24:55.159> have<00:24:55.340> these<00:24:55.490> four<00:24:55.549> validators<00:24:56.360> that<00:24:56.539> are 00:24:56.649 --> 00:24:56.659 align:start position:0% you have these four validators that are 00:24:56.659 --> 00:24:58.630 align:start position:0% you have these four validators that are all<00:24:56.780> on<00:24:56.929> this<00:24:57.110> chain<00:24:57.440> and<00:24:57.679> these<00:24:58.130> four 00:24:58.630 --> 00:24:58.640 align:start position:0% all on this chain and these four 00:24:58.640 --> 00:25:00.399 align:start position:0% all on this chain and these four validators<00:24:59.270> have<00:24:59.480> all<00:24:59.750> agreed<00:25:00.140> that<00:25:00.169> this 00:25:00.399 --> 00:25:00.409 align:start position:0% validators have all agreed that this 00:25:00.409 --> 00:25:03.760 align:start position:0% validators have all agreed that this chain<00:25:00.710> is<00:25:00.860> best<00:25:01.130> and<00:25:02.090> you<00:25:02.750> have<00:25:02.900> this<00:25:03.080> one<00:25:03.440> kind 00:25:03.760 --> 00:25:03.770 align:start position:0% chain is best and you have this one kind 00:25:03.770 --> 00:25:06.250 align:start position:0% chain is best and you have this one kind of<00:25:03.799> a<00:25:03.919> lone<00:25:04.070> attacker<00:25:04.270> now<00:25:05.270> let's<00:25:06.110> suppose 00:25:06.250 --> 00:25:06.260 align:start position:0% of a lone attacker now let's suppose 00:25:06.260 --> 00:25:08.140 align:start position:0% of a lone attacker now let's suppose that<00:25:06.440> a<00:25:06.830> CD<00:25:07.220> and<00:25:07.309> E<00:25:07.429> just<00:25:07.669> get<00:25:07.789> knocked<00:25:07.970> off 00:25:08.140 --> 00:25:08.150 align:start position:0% that a CD and E just get knocked off 00:25:08.150 --> 00:25:11.080 align:start position:0% that a CD and E just get knocked off line<00:25:08.390> they<00:25:08.600> disappear<00:25:09.049> then<00:25:09.950> if<00:25:10.669> you<00:25:10.880> use 00:25:11.080 --> 00:25:11.090 align:start position:0% line they disappear then if you use 00:25:11.090 --> 00:25:13.659 align:start position:0% line they disappear then if you use traditional<00:25:11.360> ghost<00:25:11.960> right<00:25:12.470> eventually<00:25:13.159> be 00:25:13.659 --> 00:25:13.669 align:start position:0% traditional ghost right eventually be 00:25:13.669 --> 00:25:15.039 align:start position:0% traditional ghost right eventually be could<00:25:13.880> just<00:25:14.059> make<00:25:14.210> blocks<00:25:14.480> we<00:25:14.750> could<00:25:14.900> make 00:25:15.039 --> 00:25:15.049 align:start position:0% could just make blocks we could make 00:25:15.049 --> 00:25:16.500 align:start position:0% could just make blocks we could make blocks<00:25:15.200> B<00:25:15.500> could<00:25:15.620> make<00:25:15.770> blocks<00:25:16.010> and 00:25:16.500 --> 00:25:16.510 align:start position:0% blocks B could make blocks and 00:25:16.510 --> 00:25:18.789 align:start position:0% blocks B could make blocks and eventually<00:25:17.510> be<00:25:17.630> what<00:25:17.809> B's<00:25:18.350> chain<00:25:18.650> will<00:25:18.770> be 00:25:18.789 --> 00:25:18.799 align:start position:0% eventually be what B's chain will be 00:25:18.799 --> 00:25:22.149 align:start position:0% eventually be what B's chain will be longer<00:25:19.250> and<00:25:19.340> B<00:25:19.490> would<00:25:19.580> win<00:25:19.840> but<00:25:20.840> in<00:25:21.140> LMT<00:25:21.740> ghost 00:25:22.149 --> 00:25:22.159 align:start position:0% longer and B would win but in LMT ghost 00:25:22.159 --> 00:25:24.399 align:start position:0% longer and B would win but in LMT ghost if<00:25:22.460> all<00:25:23.030> four<00:25:23.510> of<00:25:23.539> these<00:25:23.750> guys<00:25:23.960> get<00:25:24.230> knocked 00:25:24.399 --> 00:25:24.409 align:start position:0% if all four of these guys get knocked 00:25:24.409 --> 00:25:27.010 align:start position:0% if all four of these guys get knocked off<00:25:24.620> line<00:25:24.890> then<00:25:25.549> you<00:25:26.360> could<00:25:26.570> keep<00:25:26.720> on<00:25:26.900> making 00:25:27.010 --> 00:25:27.020 align:start position:0% off line then you could keep on making 00:25:27.020 --> 00:25:28.810 align:start position:0% off line then you could keep on making blocks<00:25:27.440> and<00:25:27.740> B<00:25:27.830> could<00:25:27.980> keep<00:25:28.130> on<00:25:28.280> making<00:25:28.429> vlogs 00:25:28.810 --> 00:25:28.820 align:start position:0% blocks and B could keep on making vlogs 00:25:28.820 --> 00:25:32.010 align:start position:0% blocks and B could keep on making vlogs for<00:25:29.059> a<00:25:29.120> long<00:25:29.360> time<00:25:29.630> but<00:25:30.289> this<00:25:30.740> chain<00:25:31.130> is<00:25:31.370> still 00:25:32.010 --> 00:25:32.020 align:start position:0% for a long time but this chain is still 00:25:32.020 --> 00:25:34.270 align:start position:0% for a long time but this chain is still going<00:25:33.020> to<00:25:33.200> continue<00:25:33.710> to<00:25:33.860> be<00:25:33.950> the<00:25:34.100> winning 00:25:34.270 --> 00:25:34.280 align:start position:0% going to continue to be the winning 00:25:34.280 --> 00:25:36.730 align:start position:0% going to continue to be the winning chain<00:25:34.640> because<00:25:35.150> it's<00:25:35.780> not<00:25:36.140> about<00:25:36.500> the 00:25:36.730 --> 00:25:36.740 align:start position:0% chain because it's not about the 00:25:36.740 --> 00:25:38.620 align:start position:0% chain because it's not about the quantity<00:25:37.010> of<00:25:37.250> messages<00:25:37.850> it's<00:25:38.120> about<00:25:38.419> the 00:25:38.620 --> 00:25:38.630 align:start position:0% quantity of messages it's about the 00:25:38.630 --> 00:25:41.860 align:start position:0% quantity of messages it's about the quantity<00:25:38.900> of<00:25:39.169> distinct<00:25:39.710> supporters<00:25:40.340> of<00:25:40.870> one 00:25:41.860 --> 00:25:41.870 align:start position:0% quantity of distinct supporters of one 00:25:41.870 --> 00:25:44.919 align:start position:0% quantity of distinct supporters of one chain<00:25:42.140> versus<00:25:42.500> the<00:25:42.620> other<00:25:42.770> and<00:25:43.090> if<00:25:44.090> these<00:25:44.659> four 00:25:44.919 --> 00:25:44.929 align:start position:0% chain versus the other and if these four 00:25:44.929 --> 00:25:45.190 align:start position:0% chain versus the other and if these four Val 00:25:45.190 --> 00:25:45.200 align:start position:0% Val 00:25:45.200 --> 00:25:47.019 align:start position:0% Val don't<00:25:45.710> make<00:25:45.830> any<00:25:46.070> new<00:25:46.190> messages<00:25:46.700> than<00:25:46.940> the 00:25:47.019 --> 00:25:47.029 align:start position:0% don't make any new messages than the 00:25:47.029 --> 00:25:48.279 align:start position:0% don't make any new messages than the system<00:25:47.360> assumes<00:25:47.720> that<00:25:47.840> they're<00:25:48.049> just 00:25:48.279 --> 00:25:48.289 align:start position:0% system assumes that they're just 00:25:48.289 --> 00:25:50.560 align:start position:0% system assumes that they're just supporting<00:25:48.679> these<00:25:48.799> four<00:25:49.070> things<00:25:49.220> forever<00:25:49.570> so 00:25:50.560 --> 00:25:50.570 align:start position:0% supporting these four things forever so 00:25:50.570 --> 00:25:53.649 align:start position:0% supporting these four things forever so this<00:25:51.470> kind<00:25:51.860> of<00:25:51.950> insight<00:25:52.370> this<00:25:52.820> idea<00:25:53.269> that 00:25:53.649 --> 00:25:53.659 align:start position:0% this kind of insight this idea that 00:25:53.659 --> 00:25:56.500 align:start position:0% this kind of insight this idea that unlike<00:25:54.260> longest<00:25:54.710> chain<00:25:54.950> rules<00:25:55.250> lmg<00:25:55.940> ghost<00:25:56.210> has 00:25:56.500 --> 00:25:56.510 align:start position:0% unlike longest chain rules lmg ghost has 00:25:56.510 --> 00:25:59.710 align:start position:0% unlike longest chain rules lmg ghost has this<00:25:56.750> mechanism<00:25:57.200> where<00:25:57.799> if<00:25:58.100> it<00:25:59.029> gets<00:25:59.389> into 00:25:59.710 --> 00:25:59.720 align:start position:0% this mechanism where if it gets into 00:25:59.720 --> 00:26:01.860 align:start position:0% this mechanism where if it gets into this<00:25:59.840> configuration<00:26:00.230> but<00:26:01.130> you<00:26:01.279> just<00:26:01.490> can't 00:26:01.860 --> 00:26:01.870 align:start position:0% this configuration but you just can't 00:26:01.870 --> 00:26:04.870 align:start position:0% this configuration but you just can't move<00:26:02.870> over<00:26:03.200> to<00:26:03.380> this<00:26:03.500> chin<00:26:03.860> pretty<00:26:04.429> much<00:26:04.639> like 00:26:04.870 --> 00:26:04.880 align:start position:0% move over to this chin pretty much like 00:26:04.880 --> 00:26:07.690 align:start position:0% move over to this chin pretty much like no<00:26:05.720> matter<00:26:05.929> how<00:26:06.200> long<00:26:06.470> beach<00:26:06.710> rise<00:26:06.980> this<00:26:07.639> is 00:26:07.690 --> 00:26:07.700 align:start position:0% no matter how long beach rise this is 00:26:07.700 --> 00:26:10.539 align:start position:0% no matter how long beach rise this is actually<00:26:08.269> the<00:26:08.389> basis<00:26:08.809> of<00:26:09.049> ICBC<00:26:09.860> casper<00:26:10.340> which 00:26:10.539 --> 00:26:10.549 align:start position:0% actually the basis of ICBC casper which 00:26:10.549 --> 00:26:12.840 align:start position:0% actually the basis of ICBC casper which is<00:26:10.700> something<00:26:11.000> that<00:26:11.179> we're<00:26:11.809> interested<00:26:12.110> in 00:26:12.840 --> 00:26:12.850 align:start position:0% is something that we're interested in 00:26:12.850 --> 00:26:17.259 align:start position:0% is something that we're interested in switching<00:26:13.850> to<00:26:14.149> for<00:26:14.330> the<00:26:14.419> longer<00:26:14.690> term<00:26:15.880> but<00:26:16.880> so 00:26:17.259 --> 00:26:17.269 align:start position:0% switching to for the longer term but so 00:26:17.269 --> 00:26:19.810 align:start position:0% switching to for the longer term but so this<00:26:17.389> is<00:26:17.570> one<00:26:17.750> reason<00:26:17.929> why<00:26:18.250> and<00:26:19.250> a<00:26:19.429> second 00:26:19.810 --> 00:26:19.820 align:start position:0% this is one reason why and a second 00:26:19.820 --> 00:26:23.430 align:start position:0% this is one reason why and a second reason<00:26:19.970> why<00:26:20.210> LMG<00:26:20.659> ghost<00:26:20.840> is<00:26:21.049> interesting<00:26:21.559> now 00:26:23.430 --> 00:26:23.440 align:start position:0% reason why LMG ghost is interesting now 00:26:23.440 --> 00:26:27.399 align:start position:0% reason why LMG ghost is interesting now let's<00:26:24.440> look<00:26:24.830> at<00:26:25.039> some<00:26:25.429> edge<00:26:25.700> cases<00:26:26.090> of<00:26:26.630> LMG 00:26:27.399 --> 00:26:27.409 align:start position:0% let's look at some edge cases of LMG 00:26:27.409 --> 00:26:31.080 align:start position:0% let's look at some edge cases of LMG ghosts<00:26:27.679> and<00:26:28.750> specifically<00:26:29.750> LMG<00:26:30.470> ghosts 00:26:31.080 --> 00:26:31.090 align:start position:0% ghosts and specifically LMG ghosts 00:26:31.090 --> 00:26:34.779 align:start position:0% ghosts and specifically LMG ghosts interaction<00:26:32.090> with<00:26:32.539> the<00:26:33.350> with<00:26:34.340> the<00:26:34.490> finality 00:26:34.779 --> 00:26:34.789 align:start position:0% interaction with the with the finality 00:26:34.789 --> 00:26:38.139 align:start position:0% interaction with the with the finality gadget<00:26:35.389> right<00:26:36.049> so<00:26:36.549> safety<00:26:37.549> message<00:26:37.820> attacks 00:26:38.139 --> 00:26:38.149 align:start position:0% gadget right so safety message attacks 00:26:38.149 --> 00:26:43.090 align:start position:0% gadget right so safety message attacks are<00:26:38.450> one<00:26:39.250> one<00:26:40.250> a<00:26:40.580> kind<00:26:41.570> of<00:26:41.799> example<00:26:42.799> of<00:26:42.860> an<00:26:42.980> edge 00:26:43.090 --> 00:26:43.100 align:start position:0% are one one a kind of example of an edge 00:26:43.100 --> 00:26:46.090 align:start position:0% are one one a kind of example of an edge case<00:26:43.340> first<00:26:43.639> right<00:26:44.120> so<00:26:44.360> basically<00:26:44.830> here<00:26:45.830> look 00:26:46.090 --> 00:26:46.100 align:start position:0% case first right so basically here look 00:26:46.100 --> 00:26:47.860 align:start position:0% case first right so basically here look that<00:26:46.279> here's<00:26:46.549> the<00:26:46.730> intuition<00:26:47.480> behind<00:26:47.630> a 00:26:47.860 --> 00:26:47.870 align:start position:0% that here's the intuition behind a 00:26:47.870 --> 00:26:51.180 align:start position:0% that here's the intuition behind a safety<00:26:48.200> message<00:26:48.470> attack<00:26:48.799> so<00:26:49.460> a<00:26:49.820> validator<00:26:50.750> is 00:26:51.180 --> 00:26:51.190 align:start position:0% safety message attack so a validator is 00:26:51.190 --> 00:26:55.629 align:start position:0% safety message attack so a validator is allowed<00:26:52.190> to<00:26:52.539> make<00:26:53.539> a<00:26:53.809> maximum<00:26:54.620> of<00:26:54.649> one 00:26:55.629 --> 00:26:55.639 align:start position:0% allowed to make a maximum of one 00:26:55.639 --> 00:26:57.909 align:start position:0% allowed to make a maximum of one attestation<00:26:56.179> in<00:26:56.510> each<00:26:56.630> epoch<00:26:56.809> and<00:26:57.230> the<00:26:57.799> way 00:26:57.909 --> 00:26:57.919 align:start position:0% attestation in each epoch and the way 00:26:57.919 --> 00:26:59.379 align:start position:0% attestation in each epoch and the way you<00:26:57.980> enforce<00:26:58.460> that<00:26:58.549> is<00:26:58.940> that<00:26:59.149> every 00:26:59.379 --> 00:26:59.389 align:start position:0% you enforce that is that every 00:26:59.389 --> 00:27:00.970 align:start position:0% you enforce that is that every attestation<00:26:59.809> has<00:27:00.169> to<00:27:00.289> come<00:27:00.470> with<00:27:00.620> a<00:27:00.649> tag<00:27:00.950> that 00:27:00.970 --> 00:27:00.980 align:start position:0% attestation has to come with a tag that 00:27:00.980 --> 00:27:03.009 align:start position:0% attestation has to come with a tag that says<00:27:01.250> this<00:27:01.580> is<00:27:01.639> the<00:27:01.760> epoch<00:27:02.149> I<00:27:02.299> come<00:27:02.539> from<00:27:02.809> and 00:27:03.009 --> 00:27:03.019 align:start position:0% says this is the epoch I come from and 00:27:03.019 --> 00:27:05.139 align:start position:0% says this is the epoch I come from and if<00:27:03.440> you<00:27:03.559> send<00:27:03.860> two<00:27:04.039> distinct<00:27:04.519> at<00:27:04.639> the<00:27:04.760> stations 00:27:05.139 --> 00:27:05.149 align:start position:0% if you send two distinct at the stations 00:27:05.149 --> 00:27:07.389 align:start position:0% if you send two distinct at the stations with<00:27:05.330> the<00:27:05.450> same<00:27:05.630> epoch<00:27:06.019> tag<00:27:06.320> then<00:27:06.889> you<00:27:07.100> can<00:27:07.250> get 00:27:07.389 --> 00:27:07.399 align:start position:0% with the same epoch tag then you can get 00:27:07.399 --> 00:27:10.450 align:start position:0% with the same epoch tag then you can get slashed<00:27:07.730> for<00:27:07.940> it<00:27:08.059> now<00:27:09.049> a<00:27:09.440> thing<00:27:10.039> that<00:27:10.190> you<00:27:10.279> can 00:27:10.450 --> 00:27:10.460 align:start position:0% slashed for it now a thing that you can 00:27:10.460 --> 00:27:12.850 align:start position:0% slashed for it now a thing that you can do<00:27:10.639> is<00:27:10.909> you<00:27:11.299> can<00:27:11.450> say<00:27:11.690> well<00:27:11.720> I'm<00:27:12.289> gonna<00:27:12.620> just 00:27:12.850 --> 00:27:12.860 align:start position:0% do is you can say well I'm gonna just 00:27:12.860 --> 00:27:15.700 align:start position:0% do is you can say well I'm gonna just drop<00:27:13.159> off<00:27:13.309> line<00:27:13.580> for<00:27:13.610> any<00:27:13.970> box<00:27:14.330> and<00:27:14.659> now<00:27:15.230> I<00:27:15.289> have 00:27:15.700 --> 00:27:15.710 align:start position:0% drop off line for any box and now I have 00:27:15.710 --> 00:27:18.340 align:start position:0% drop off line for any box and now I have in<00:27:16.090> historical<00:27:17.090> tags<00:27:17.389> that<00:27:17.539> I've<00:27:17.659> unused<00:27:18.139> and 00:27:18.340 --> 00:27:18.350 align:start position:0% in historical tags that I've unused and 00:27:18.350 --> 00:27:21.070 align:start position:0% in historical tags that I've unused and then<00:27:18.950> within<00:27:19.610> one<00:27:19.760> epoch<00:27:20.330> I<00:27:20.510> can<00:27:20.690> just<00:27:20.899> like 00:27:21.070 --> 00:27:21.080 align:start position:0% then within one epoch I can just like 00:27:21.080 --> 00:27:22.720 align:start position:0% then within one epoch I can just like send<00:27:21.409> all<00:27:21.590> of<00:27:21.620> those<00:27:21.830> messages<00:27:22.250> with<00:27:22.519> all<00:27:22.639> of 00:27:22.720 --> 00:27:22.730 align:start position:0% send all of those messages with all of 00:27:22.730 --> 00:27:27.060 align:start position:0% send all of those messages with all of those<00:27:22.880> tags<00:27:23.179> all<00:27:23.450> at<00:27:23.600> once<00:27:23.750> so<00:27:24.490> a<00:27:25.720> worst-case 00:27:27.060 --> 00:27:27.070 align:start position:0% those tags all at once so a worst-case 00:27:27.070 --> 00:27:29.230 align:start position:0% those tags all at once so a worst-case traditional<00:27:28.070> ghost<00:27:28.309> like<00:27:28.669> it's<00:27:28.850> not<00:27:29.000> very 00:27:29.230 --> 00:27:29.240 align:start position:0% traditional ghost like it's not very 00:27:29.240 --> 00:27:31.360 align:start position:0% traditional ghost like it's not very it's<00:27:29.779> not<00:27:29.929> very<00:27:30.320> good<00:27:30.500> at<00:27:30.590> handling<00:27:30.860> this<00:27:31.130> kind 00:27:31.360 --> 00:27:31.370 align:start position:0% it's not very good at handling this kind 00:27:31.370 --> 00:27:36.070 align:start position:0% it's not very good at handling this kind of<00:27:31.429> situation<00:27:32.860> LMT<00:27:33.860> ghost<00:27:34.340> is<00:27:34.720> better<00:27:35.720> because 00:27:36.070 --> 00:27:36.080 align:start position:0% of situation LMT ghost is better because 00:27:36.080 --> 00:27:38.740 align:start position:0% of situation LMT ghost is better because at<00:27:36.769> least<00:27:37.130> those<00:27:37.519> n<00:27:37.700> votes<00:27:37.940> do<00:27:38.149> not<00:27:38.330> stack<00:27:38.570> on 00:27:38.740 --> 00:27:38.750 align:start position:0% at least those n votes do not stack on 00:27:38.750 --> 00:27:41.259 align:start position:0% at least those n votes do not stack on top<00:27:38.779> of<00:27:38.960> each<00:27:39.139> other<00:27:39.350> but<00:27:40.340> lmd<00:27:40.820> ghost<00:27:41.029> is<00:27:41.240> still 00:27:41.259 --> 00:27:41.269 align:start position:0% top of each other but lmd ghost is still 00:27:41.269 --> 00:27:43.870 align:start position:0% top of each other but lmd ghost is still imperfect<00:27:42.110> because<00:27:42.350> with<00:27:43.340> this<00:27:43.580> kind<00:27:43.789> of 00:27:43.870 --> 00:27:43.880 align:start position:0% imperfect because with this kind of 00:27:43.880 --> 00:27:45.669 align:start position:0% imperfect because with this kind of mechanism<00:27:44.059> well<00:27:44.750> you<00:27:44.929> have<00:27:45.080> the<00:27:45.230> ability<00:27:45.649> to 00:27:45.669 --> 00:27:45.679 align:start position:0% mechanism well you have the ability to 00:27:45.679 --> 00:27:48.250 align:start position:0% mechanism well you have the ability to and<00:27:46.460> if<00:27:46.610> influenced<00:27:47.120> to<00:27:47.269> basically<00:27:47.809> make<00:27:48.110> the 00:27:48.250 --> 00:27:48.260 align:start position:0% and if influenced to basically make the 00:27:48.260 --> 00:27:49.870 align:start position:0% and if influenced to basically make the fork<00:27:48.470> choice<00:27:48.740> go<00:27:48.889> back<00:27:49.070> and<00:27:49.250> forth<00:27:49.490> right<00:27:49.760> you 00:27:49.870 --> 00:27:49.880 align:start position:0% fork choice go back and forth right you 00:27:49.880 --> 00:27:51.940 align:start position:0% fork choice go back and forth right you can<00:27:50.059> say<00:27:50.299> I<00:27:50.480> vote<00:27:50.870> for<00:27:50.990> you<00:27:51.169> now<00:27:51.529> I<00:27:51.559> vote<00:27:51.830> for 00:27:51.940 --> 00:27:51.950 align:start position:0% can say I vote for you now I vote for 00:27:51.950 --> 00:27:53.230 align:start position:0% can say I vote for you now I vote for you<00:27:52.010> now<00:27:52.250> I<00:27:52.279> vote<00:27:52.519> for<00:27:52.669> you<00:27:52.760> and<00:27:52.789> now<00:27:52.970> I<00:27:53.000> vote 00:27:53.230 --> 00:27:53.240 align:start position:0% you now I vote for you and now I vote 00:27:53.240 --> 00:27:55.389 align:start position:0% you now I vote for you and now I vote for<00:27:53.389> you<00:27:53.450> and<00:27:53.809> you<00:27:53.929> can<00:27:54.649> repeat<00:27:54.889> this<00:27:55.070> a<00:27:55.129> bunch 00:27:55.389 --> 00:27:55.399 align:start position:0% for you and you can repeat this a bunch 00:27:55.399 --> 00:27:57.639 align:start position:0% for you and you can repeat this a bunch of<00:27:55.490> times<00:27:55.760> in<00:27:55.970> a<00:27:56.059> single<00:27:56.210> epoch<00:27:56.720> and<00:27:57.169> this 00:27:57.639 --> 00:27:57.649 align:start position:0% of times in a single epoch and this 00:27:57.649 --> 00:27:58.749 align:start position:0% of times in a single epoch and this could<00:27:57.889> be<00:27:58.039> used<00:27:58.279> for<00:27:58.429> some 00:27:58.749 --> 00:27:58.759 align:start position:0% could be used for some 00:27:58.759 --> 00:28:01.569 align:start position:0% could be used for some attack<00:27:59.029> still<00:27:59.839> alive<00:28:00.169> nacinda<00:28:00.529> lay<00:28:00.769> finality 00:28:01.569 --> 00:28:01.579 align:start position:0% attack still alive nacinda lay finality 00:28:01.579 --> 00:28:06.039 align:start position:0% attack still alive nacinda lay finality so<00:28:01.940> a<00:28:02.469> proposed<00:28:03.469> solution<00:28:03.919> here<00:28:04.609> is<00:28:04.779> FMD<00:28:05.779> ghost 00:28:06.039 --> 00:28:06.049 align:start position:0% so a proposed solution here is FMD ghost 00:28:06.049 --> 00:28:09.430 align:start position:0% so a proposed solution here is FMD ghost which<00:28:06.320> basically<00:28:06.709> says<00:28:07.359> clients<00:28:08.359> only<00:28:08.929> look 00:28:09.430 --> 00:28:09.440 align:start position:0% which basically says clients only look 00:28:09.440 --> 00:28:11.409 align:start position:0% which basically says clients only look at<00:28:09.589> messages<00:28:09.799> and<00:28:10.399> have<00:28:10.519> tagged<00:28:10.879> with<00:28:11.209> the 00:28:11.409 --> 00:28:11.419 align:start position:0% at messages and have tagged with the 00:28:11.419 --> 00:28:13.359 align:start position:0% at messages and have tagged with the current<00:28:11.690> or<00:28:11.779> previous<00:28:11.989> epoch<00:28:12.589> and<00:28:12.859> this 00:28:13.359 --> 00:28:13.369 align:start position:0% current or previous epoch and this 00:28:13.369 --> 00:28:16.149 align:start position:0% current or previous epoch and this prevents<00:28:13.940> kind<00:28:14.359> of<00:28:14.449> saving<00:28:14.869> saving<00:28:15.739> up<00:28:15.889> more 00:28:16.149 --> 00:28:16.159 align:start position:0% prevents kind of saving saving up more 00:28:16.159 --> 00:28:18.699 align:start position:0% prevents kind of saving saving up more than<00:28:16.339> one<00:28:16.519> more<00:28:16.820> than<00:28:16.849> two<00:28:16.999> epochs<00:28:17.449> from<00:28:17.929> being 00:28:18.699 --> 00:28:18.709 align:start position:0% than one more than two epochs from being 00:28:18.709 --> 00:28:21.600 align:start position:0% than one more than two epochs from being a<00:28:18.789> being<00:28:19.789> useful<00:28:20.269> for<00:28:20.419> any<00:28:20.539> kind<00:28:20.779> of<00:28:20.869> attack 00:28:21.600 --> 00:28:21.610 align:start position:0% a being useful for any kind of attack 00:28:21.610 --> 00:28:23.430 align:start position:0% a being useful for any kind of attack [Music] 00:28:23.430 --> 00:28:23.440 align:start position:0% [Music] 00:28:23.440 --> 00:28:26.759 align:start position:0% [Music] interaction<00:28:24.440> between<00:28:24.589> oMG<00:28:25.159> ghost<00:28:25.339> and<00:28:25.579> FFG<00:28:26.029> so 00:28:26.759 --> 00:28:26.769 align:start position:0% interaction between oMG ghost and FFG so 00:28:26.769 --> 00:28:31.239 align:start position:0% interaction between oMG ghost and FFG so we<00:28:27.769> use<00:28:28.039> both<00:28:28.179> LMG<00:28:29.179> ghost<00:28:29.479> and<00:28:29.809> the<00:28:30.229> FFG<00:28:30.739> in 00:28:31.239 --> 00:28:31.249 align:start position:0% we use both LMG ghost and the FFG in 00:28:31.249 --> 00:28:34.329 align:start position:0% we use both LMG ghost and the FFG in this<00:28:31.459> kind<00:28:31.669> of<00:28:31.729> combined<00:28:32.389> way<00:28:32.629> basically<00:28:33.619> lmd 00:28:34.329 --> 00:28:34.339 align:start position:0% this kind of combined way basically lmd 00:28:34.339 --> 00:28:36.249 align:start position:0% this kind of combined way basically lmd ghost<00:28:34.549> provides<00:28:34.940> block<00:28:35.209> by<00:28:35.389> block<00:28:35.509> consensus 00:28:36.249 --> 00:28:36.259 align:start position:0% ghost provides block by block consensus 00:28:36.259 --> 00:28:41.229 align:start position:0% ghost provides block by block consensus and<00:28:36.609> FFG<00:28:37.609> provides<00:28:38.179> finality<00:28:38.899> and<00:28:39.940> like<00:28:40.940> you 00:28:41.229 --> 00:28:41.239 align:start position:0% and FFG provides finality and like you 00:28:41.239 --> 00:28:42.789 align:start position:0% and FFG provides finality and like you do<00:28:41.389> have<00:28:41.599> to<00:28:41.779> kind<00:28:41.899> of<00:28:41.989> glue<00:28:42.259> these<00:28:42.469> algorithms 00:28:42.789 --> 00:28:42.799 align:start position:0% do have to kind of glue these algorithms 00:28:42.799 --> 00:28:45.699 align:start position:0% do have to kind of glue these algorithms together<00:28:43.459> right<00:28:43.789> so<00:28:44.269> our<00:28:44.599> actual<00:28:45.049> a<00:28:45.409> fork 00:28:45.699 --> 00:28:45.709 align:start position:0% together right so our actual a fork 00:28:45.709 --> 00:28:48.909 align:start position:0% together right so our actual a fork surest<00:28:45.979> rule<00:28:46.190> basically<00:28:46.399> says<00:28:46.759> first<00:28:47.919> select 00:28:48.909 --> 00:28:48.919 align:start position:0% surest rule basically says first select 00:28:48.919 --> 00:28:50.739 align:start position:0% surest rule basically says first select the<00:28:49.129> last<00:28:49.339> finalized<00:28:49.909> block<00:28:50.209> you<00:28:50.359> were<00:28:50.509> aware 00:28:50.739 --> 00:28:50.749 align:start position:0% the last finalized block you were aware 00:28:50.749 --> 00:28:52.419 align:start position:0% the last finalized block you were aware of<00:28:50.809> and<00:28:51.259> at<00:28:51.559> the<00:28:51.679> beginning<00:28:52.039> this<00:28:52.159> is<00:28:52.219> the 00:28:52.419 --> 00:28:52.429 align:start position:0% of and at the beginning this is the 00:28:52.429 --> 00:28:54.489 align:start position:0% of and at the beginning this is the genisis<00:28:52.940> eventually<00:28:53.599> you<00:28:53.869> become<00:28:54.019> aware<00:28:54.259> of 00:28:54.489 --> 00:28:54.499 align:start position:0% genisis eventually you become aware of 00:28:54.499 --> 00:28:57.849 align:start position:0% genisis eventually you become aware of new<00:28:54.619> finalized<00:28:55.129> blocks<00:28:55.719> second<00:28:56.719> you<00:28:57.440> selects 00:28:57.849 --> 00:28:57.859 align:start position:0% new finalized blocks second you selects 00:28:57.859 --> 00:28:59.919 align:start position:0% new finalized blocks second you selects the<00:28:58.039> highest<00:28:58.459> highest<00:28:59.059> epoch<00:28:59.569> the<00:28:59.779> most 00:28:59.919 --> 00:28:59.929 align:start position:0% the highest highest epoch the most 00:28:59.929 --> 00:29:01.839 align:start position:0% the highest highest epoch the most recent<00:29:00.349> justified<00:29:00.889> block<00:29:01.129> that's<00:29:01.729> a 00:29:01.839 --> 00:29:01.849 align:start position:0% recent justified block that's a 00:29:01.849 --> 00:29:03.430 align:start position:0% recent justified block that's a descendent<00:29:02.359> of<00:29:02.419> the<00:29:02.479> last<00:29:02.599> finalized<00:29:03.169> walk 00:29:03.430 --> 00:29:03.440 align:start position:0% descendent of the last finalized walk 00:29:03.440 --> 00:29:06.009 align:start position:0% descendent of the last finalized walk and<00:29:03.709> then<00:29:04.159> third<00:29:04.489> starting<00:29:05.389> from<00:29:05.659> the<00:29:05.899> last 00:29:06.009 --> 00:29:06.019 align:start position:0% and then third starting from the last 00:29:06.019 --> 00:29:08.589 align:start position:0% and then third starting from the last justified<00:29:06.679> block<00:29:06.949> you<00:29:07.309> run<00:29:07.519> LMG<00:29:07.940> goes<00:29:08.119> to<00:29:08.359> find 00:29:08.589 --> 00:29:08.599 align:start position:0% justified block you run LMG goes to find 00:29:08.599 --> 00:29:11.889 align:start position:0% justified block you run LMG goes to find the<00:29:08.719> head<00:29:08.839> so<00:29:09.829> it's<00:29:10.039> basically<00:29:10.459> running<00:29:11.239> FFG 00:29:11.889 --> 00:29:11.899 align:start position:0% the head so it's basically running FFG 00:29:11.899 --> 00:29:13.930 align:start position:0% the head so it's basically running FFG first<00:29:12.229> to<00:29:12.469> figure<00:29:12.739> out<00:29:12.859> the<00:29:13.009> last<00:29:13.429> justified 00:29:13.930 --> 00:29:13.940 align:start position:0% first to figure out the last justified 00:29:13.940 --> 00:29:16.449 align:start position:0% first to figure out the last justified block<00:29:14.209> and<00:29:14.359> then<00:29:14.449> writing<00:29:14.659> lmg<00:29:15.079> lmg<00:29:16.039> goes<00:29:16.219> from 00:29:16.449 --> 00:29:16.459 align:start position:0% block and then writing lmg lmg goes from 00:29:16.459 --> 00:29:20.199 align:start position:0% block and then writing lmg lmg goes from there<00:29:16.579> to<00:29:16.759> find<00:29:16.940> what<00:29:17.149> the<00:29:17.239> head<00:29:17.389> is<00:29:17.599> now<00:29:19.209> this 00:29:20.199 --> 00:29:20.209 align:start position:0% there to find what the head is now this 00:29:20.209 --> 00:29:23.109 align:start position:0% there to find what the head is now this does<00:29:20.629> open<00:29:20.959> room<00:29:21.559> for<00:29:21.979> certain<00:29:22.399> kinds<00:29:22.759> of<00:29:22.879> like 00:29:23.109 --> 00:29:23.119 align:start position:0% does open room for certain kinds of like 00:29:23.119 --> 00:29:25.539 align:start position:0% does open room for certain kinds of like bounced<00:29:23.359> attacks<00:29:23.809> so<00:29:24.559> basically<00:29:25.129> the<00:29:25.399> issue 00:29:25.539 --> 00:29:25.549 align:start position:0% bounced attacks so basically the issue 00:29:25.549 --> 00:29:28.959 align:start position:0% bounced attacks so basically the issue here<00:29:26.119> is<00:29:26.329> that<00:29:26.499> you<00:29:27.499> might<00:29:27.769> have<00:29:28.009> a<00:29:28.069> situation 00:29:28.959 --> 00:29:28.969 align:start position:0% here is that you might have a situation 00:29:28.969 --> 00:29:31.479 align:start position:0% here is that you might have a situation where<00:29:29.209> you<00:29:29.809> have<00:29:29.989> one<00:29:30.019> block<00:29:30.469> on<00:29:30.679> one<00:29:30.859> side<00:29:31.129> and 00:29:31.479 --> 00:29:31.489 align:start position:0% where you have one block on one side and 00:29:31.489 --> 00:29:33.249 align:start position:0% where you have one block on one side and you<00:29:31.969> have<00:29:32.119> a<00:29:32.149> block<00:29:32.419> that's<00:29:32.659> winning<00:29:32.869> the<00:29:33.049> fork 00:29:33.249 --> 00:29:33.259 align:start position:0% you have a block that's winning the fork 00:29:33.259 --> 00:29:35.079 align:start position:0% you have a block that's winning the fork choice<00:29:33.469> rule<00:29:33.739> but<00:29:34.219> then<00:29:34.339> you<00:29:34.459> have<00:29:34.609> some<00:29:34.849> block 00:29:35.079 --> 00:29:35.089 align:start position:0% choice rule but then you have some block 00:29:35.089 --> 00:29:38.049 align:start position:0% choice rule but then you have some block over<00:29:35.329> here<00:29:35.359> with<00:29:35.809> 65%<00:29:36.440> of<00:29:36.949> the<00:29:37.009> votes<00:29:37.309> and<00:29:37.609> then 00:29:38.049 --> 00:29:38.059 align:start position:0% over here with 65% of the votes and then 00:29:38.059 --> 00:29:39.639 align:start position:0% over here with 65% of the votes and then the<00:29:38.209> attacker<00:29:38.509> has<00:29:38.749> a<00:29:38.779> few<00:29:39.019> votes<00:29:39.199> so<00:29:39.409> then<00:29:39.529> the 00:29:39.639 --> 00:29:39.649 align:start position:0% the attacker has a few votes so then the 00:29:39.649 --> 00:29:41.409 align:start position:0% the attacker has a few votes so then the attacker<00:29:39.949> waits<00:29:40.339> until<00:29:40.519> some<00:29:40.940> block<00:29:41.179> here 00:29:41.409 --> 00:29:41.419 align:start position:0% attacker waits until some block here 00:29:41.419 --> 00:29:43.899 align:start position:0% attacker waits until some block here gets<00:29:41.659> a<00:29:41.779> 65%<00:29:42.499> and<00:29:43.369> then<00:29:43.549> the<00:29:43.609> attacker 00:29:43.899 --> 00:29:43.909 align:start position:0% gets a 65% and then the attacker 00:29:43.909 --> 00:29:45.639 align:start position:0% gets a 65% and then the attacker releases<00:29:44.449> a<00:29:44.479> few<00:29:44.719> votes<00:29:44.839> here<00:29:45.229> this<00:29:45.440> block 00:29:45.639 --> 00:29:45.649 align:start position:0% releases a few votes here this block 00:29:45.649 --> 00:29:48.219 align:start position:0% releases a few votes here this block becomes<00:29:45.979> justified<00:29:46.609> and<00:29:46.879> so<00:29:47.389> suddenly<00:29:47.899> the 00:29:48.219 --> 00:29:48.229 align:start position:0% becomes justified and so suddenly the 00:29:48.229 --> 00:29:49.779 align:start position:0% becomes justified and so suddenly the fork<00:29:48.440> sure<00:29:48.589> is<00:29:48.709> the<00:29:48.799> rule<00:29:48.979> kind<00:29:49.219> of<00:29:49.339> flips<00:29:49.609> over 00:29:49.779 --> 00:29:49.789 align:start position:0% fork sure is the rule kind of flips over 00:29:49.789 --> 00:29:52.419 align:start position:0% fork sure is the rule kind of flips over from<00:29:50.089> here<00:29:50.239> to<00:29:50.389> here<00:29:50.719> and<00:29:50.869> then<00:29:51.469> people<00:29:52.039> build 00:29:52.419 --> 00:29:52.429 align:start position:0% from here to here and then people build 00:29:52.429 --> 00:29:54.339 align:start position:0% from here to here and then people build over<00:29:52.579> here<00:29:53.089> and<00:29:53.299> then<00:29:53.749> when<00:29:53.959> this<00:29:54.139> block 00:29:54.339 --> 00:29:54.349 align:start position:0% over here and then when this block 00:29:54.349 --> 00:29:57.489 align:start position:0% over here and then when this block starts<00:29:54.949> getting<00:29:55.249> close<00:29:55.459> to<00:29:55.639> over<00:29:55.819> to<00:29:55.969> 65%<00:29:56.509> then 00:29:57.489 --> 00:29:57.499 align:start position:0% starts getting close to over to 65% then 00:29:57.499 --> 00:30:00.039 align:start position:0% starts getting close to over to 65% then this<00:29:57.799> blocks<00:29:58.009> at<00:29:58.190> 65%<00:29:58.669> the<00:29:59.179> attacker<00:29:59.449> releases 00:30:00.039 --> 00:30:00.049 align:start position:0% this blocks at 65% the attacker releases 00:30:00.049 --> 00:30:02.469 align:start position:0% this blocks at 65% the attacker releases another<00:30:00.259> 5%<00:30:00.529> now<00:30:01.039> this<00:30:01.249> is<00:30:01.399> justified<00:30:01.940> now 00:30:02.469 --> 00:30:02.479 align:start position:0% another 5% now this is justified now 00:30:02.479 --> 00:30:04.389 align:start position:0% another 5% now this is justified now this<00:30:02.749> halts<00:30:03.079> everyone<00:30:03.409> moves<00:30:03.619> over<00:30:03.889> here<00:30:03.919> and 00:30:04.389 --> 00:30:04.399 align:start position:0% this halts everyone moves over here and 00:30:04.399 --> 00:30:06.039 align:start position:0% this halts everyone moves over here and so<00:30:04.879> he<00:30:04.999> can<00:30:05.149> kind<00:30:05.359> of<00:30:05.419> bounce<00:30:05.599> the<00:30:05.839> chain 00:30:06.039 --> 00:30:06.049 align:start position:0% so he can kind of bounce the chain 00:30:06.049 --> 00:30:09.609 align:start position:0% so he can kind of bounce the chain around<00:30:06.349> right<00:30:07.009> and<00:30:07.329> there's<00:30:08.329> some<00:30:08.659> a<00:30:08.899> couple 00:30:09.609 --> 00:30:09.619 align:start position:0% around right and there's some a couple 00:30:09.619 --> 00:30:12.320 align:start position:0% around right and there's some a couple of<00:30:09.769> solutions<00:30:10.459> that<00:30:10.940> are 00:30:12.320 --> 00:30:12.330 align:start position:0% of solutions that are 00:30:12.330 --> 00:30:14.960 align:start position:0% of solutions that are intended<00:30:13.330> to<00:30:13.450> mitigate<00:30:13.810> this<00:30:13.930> kind<00:30:14.200> of<00:30:14.290> attack 00:30:14.960 --> 00:30:14.970 align:start position:0% intended to mitigate this kind of attack 00:30:14.970 --> 00:30:17.850 align:start position:0% intended to mitigate this kind of attack one<00:30:15.970> of<00:30:16.120> them<00:30:16.330> has<00:30:16.630> to<00:30:16.840> basically<00:30:17.290> they<00:30:17.830> all 00:30:17.850 --> 00:30:17.860 align:start position:0% one of them has to basically they all 00:30:17.860 --> 00:30:20.820 align:start position:0% one of them has to basically they all have<00:30:18.310> to<00:30:18.520> do<00:30:18.700> with<00:30:18.970> kind<00:30:19.330> of<00:30:19.750> delaying<00:30:20.200> when 00:30:20.820 --> 00:30:20.830 align:start position:0% have to do with kind of delaying when 00:30:20.830 --> 00:30:23.490 align:start position:0% have to do with kind of delaying when you<00:30:21.760> justified<00:30:22.390> epochs<00:30:22.810> have<00:30:23.080> an<00:30:23.200> effect 00:30:23.490 --> 00:30:23.500 align:start position:0% you justified epochs have an effect 00:30:23.500 --> 00:30:26.640 align:start position:0% you justified epochs have an effect right<00:30:23.890> so<00:30:24.190> one<00:30:25.000> of<00:30:25.120> them<00:30:25.270> would<00:30:25.450> say<00:30:25.480> in<00:30:26.230> most 00:30:26.640 --> 00:30:26.650 align:start position:0% right so one of them would say in most 00:30:26.650 --> 00:30:29.550 align:start position:0% right so one of them would say in most like<00:30:26.920> in<00:30:27.220> most<00:30:27.580> cases<00:30:27.880> delay<00:30:28.450> until<00:30:28.630> always 00:30:29.550 --> 00:30:29.560 align:start position:0% like in most cases delay until always 00:30:29.560 --> 00:30:32.400 align:start position:0% like in most cases delay until always switching<00:30:29.950> until<00:30:30.520> when<00:30:30.730> epoch<00:30:31.000> boundary<00:30:31.480> so 00:30:32.400 --> 00:30:32.410 align:start position:0% switching until when epoch boundary so 00:30:32.410 --> 00:30:34.830 align:start position:0% switching until when epoch boundary so either<00:30:32.740> finalization<00:30:33.700> happens<00:30:34.060> a<00:30:34.210> coast<00:30:34.660> of 00:30:34.830 --> 00:30:34.840 align:start position:0% either finalization happens a coast of 00:30:34.840 --> 00:30:36.480 align:start position:0% either finalization happens a coast of the<00:30:34.900> start<00:30:35.110> of<00:30:35.230> an<00:30:35.320> epoch<00:30:35.440> or<00:30:35.860> it<00:30:36.010> happens<00:30:36.340> much 00:30:36.480 --> 00:30:36.490 align:start position:0% the start of an epoch or it happens much 00:30:36.490 --> 00:30:39.570 align:start position:0% the start of an epoch or it happens much late<00:30:36.760> or<00:30:36.940> or<00:30:37.330> you<00:30:37.600> wait<00:30:37.750> until<00:30:37.930> the<00:30:38.200> end<00:30:38.350> or<00:30:38.680> and 00:30:39.570 --> 00:30:39.580 align:start position:0% late or or you wait until the end or and 00:30:39.580 --> 00:30:42.810 align:start position:0% late or or you wait until the end or and I<00:30:39.670> another<00:30:40.030> idea<00:30:40.480> is<00:30:40.720> that<00:30:40.960> a<00:30:41.280> checkpoint<00:30:42.280> can 00:30:42.810 --> 00:30:42.820 align:start position:0% I another idea is that a checkpoint can 00:30:42.820 --> 00:30:43.590 align:start position:0% I another idea is that a checkpoint can only<00:30:42.970> be<00:30:43.150> used 00:30:43.590 --> 00:30:43.600 align:start position:0% only be used 00:30:43.600 --> 00:30:47.700 align:start position:0% only be used can<00:30:44.110> only<00:30:44.230> be<00:30:44.350> used<00:30:44.830> to<00:30:45.960> as<00:30:46.960> part<00:30:47.320> of<00:30:47.410> the<00:30:47.500> fork 00:30:47.700 --> 00:30:47.710 align:start position:0% can only be used to as part of the fork 00:30:47.710 --> 00:30:50.760 align:start position:0% can only be used to as part of the fork choice<00:30:47.980> until<00:30:48.640> like<00:30:49.000> basically<00:30:49.530> the<00:30:50.530> height 00:30:50.760 --> 00:30:50.770 align:start position:0% choice until like basically the height 00:30:50.770 --> 00:30:52.200 align:start position:0% choice until like basically the height since<00:30:51.100> the<00:30:51.250> last<00:30:51.400> justified<00:30:51.940> epoch 00:30:52.200 --> 00:30:52.210 align:start position:0% since the last justified epoch 00:30:52.210 --> 00:30:54.330 align:start position:0% since the last justified epoch multiplies<00:30:52.720> by<00:30:52.750> three<00:30:53.290> year<00:30:53.500> and<00:30:53.770> this 00:30:54.330 --> 00:30:54.340 align:start position:0% multiplies by three year and this 00:30:54.340 --> 00:30:56.700 align:start position:0% multiplies by three year and this ensures<00:30:54.610> that<00:30:54.970> there's<00:30:55.390> kind<00:30:55.960> of<00:30:56.050> periods<00:30:56.530> of 00:30:56.700 --> 00:30:56.710 align:start position:0% ensures that there's kind of periods of 00:30:56.710 --> 00:30:59.100 align:start position:0% ensures that there's kind of periods of three<00:30:56.950> epochs<00:30:57.250> eventually<00:30:58.000> within<00:30:58.240> which<00:30:58.570> the 00:30:59.100 --> 00:30:59.110 align:start position:0% three epochs eventually within which the 00:30:59.110 --> 00:31:00.810 align:start position:0% three epochs eventually within which the fork<00:30:59.320> choice<00:30:59.560> is<00:30:59.710> not<00:30:59.860> going<00:31:00.100> to<00:31:00.220> change<00:31:00.460> and 00:31:00.810 --> 00:31:00.820 align:start position:0% fork choice is not going to change and 00:31:00.820 --> 00:31:02.250 align:start position:0% fork choice is not going to change and you<00:31:00.910> have<00:31:00.940> the<00:31:01.210> opportunity<00:31:01.720> to<00:31:01.840> finalize 00:31:02.250 --> 00:31:02.260 align:start position:0% you have the opportunity to finalize 00:31:02.260 --> 00:31:09.750 align:start position:0% you have the opportunity to finalize something<00:31:04.020> so<00:31:05.730> then<00:31:06.730> like<00:31:07.920> LMT<00:31:08.920> go<00:31:09.220> stick<00:31:09.550> is 00:31:09.750 --> 00:31:09.760 align:start position:0% something so then like LMT go stick is 00:31:09.760 --> 00:31:11.850 align:start position:0% something so then like LMT go stick is not<00:31:10.090> really<00:31:10.480> more<00:31:10.780> complicated<00:31:11.020> more 00:31:11.850 --> 00:31:11.860 align:start position:0% not really more complicated more 00:31:11.860 --> 00:31:13.680 align:start position:0% not really more complicated more complicated<00:31:12.460> than<00:31:12.610> this<00:31:12.790> right<00:31:13.120> it<00:31:13.270> basically 00:31:13.680 --> 00:31:13.690 align:start position:0% complicated than this right it basically 00:31:13.690 --> 00:31:16.410 align:start position:0% complicated than this right it basically is<00:31:13.990> you<00:31:14.470> have<00:31:14.620> a<00:31:14.650> block<00:31:14.950> and<00:31:15.430> if<00:31:15.970> that<00:31:16.150> block 00:31:16.410 --> 00:31:16.420 align:start position:0% is you have a block and if that block 00:31:16.420 --> 00:31:18.300 align:start position:0% is you have a block and if that block has<00:31:16.600> multiple<00:31:17.050> children<00:31:17.230> to<00:31:17.890> figure<00:31:18.160> out 00:31:18.300 --> 00:31:18.310 align:start position:0% has multiple children to figure out 00:31:18.310 --> 00:31:19.950 align:start position:0% has multiple children to figure out whether<00:31:18.580> you<00:31:18.700> go<00:31:18.940> to<00:31:18.970> one<00:31:19.270> child<00:31:19.570> or<00:31:19.720> the<00:31:19.840> other 00:31:19.950 --> 00:31:19.960 align:start position:0% whether you go to one child or the other 00:31:19.960 --> 00:31:21.840 align:start position:0% whether you go to one child or the other a<00:31:20.020> child<00:31:20.320> you<00:31:20.800> choose<00:31:21.010> the<00:31:21.190> child<00:31:21.460> that<00:31:21.670> has 00:31:21.840 --> 00:31:21.850 align:start position:0% a child you choose the child that has 00:31:21.850 --> 00:31:24.030 align:start position:0% a child you choose the child that has the<00:31:22.270> most<00:31:22.720> validators<00:31:23.500> that<00:31:23.770> you<00:31:23.860> might<00:31:23.980> have 00:31:24.030 --> 00:31:24.040 align:start position:0% the most validators that you might have 00:31:24.040 --> 00:31:26.010 align:start position:0% the most validators that you might have most<00:31:24.310> recently<00:31:24.760> supported<00:31:25.270> that<00:31:25.390> block<00:31:25.660> and 00:31:26.010 --> 00:31:26.020 align:start position:0% most recently supported that block and 00:31:26.020 --> 00:31:29.010 align:start position:0% most recently supported that block and you<00:31:26.830> can<00:31:26.860> use<00:31:27.160> that<00:31:27.370> by<00:31:27.580> itself<00:31:27.940> as<00:31:28.210> a<00:31:28.450> as<00:31:28.960> a 00:31:29.010 --> 00:31:29.020 align:start position:0% you can use that by itself as a as a 00:31:29.020 --> 00:31:31.440 align:start position:0% you can use that by itself as a as a fork<00:31:29.320> choice<00:31:29.530> rule<00:31:29.830> and<00:31:30.580> you<00:31:30.790> have<00:31:30.940> a<00:31:30.970> bunch<00:31:31.270> of 00:31:31.440 --> 00:31:31.450 align:start position:0% fork choice rule and you have a bunch of 00:31:31.450 --> 00:31:32.880 align:start position:0% fork choice rule and you have a bunch of validators<00:31:32.110> that<00:31:32.320> are<00:31:32.410> making<00:31:32.590> these 00:31:32.880 --> 00:31:32.890 align:start position:0% validators that are making these 00:31:32.890 --> 00:31:35.490 align:start position:0% validators that are making these messages<00:31:33.340> in<00:31:33.490> parallel<00:31:33.970> and<00:31:34.240> each<00:31:35.110> of<00:31:35.350> those 00:31:35.490 --> 00:31:35.500 align:start position:0% messages in parallel and each of those 00:31:35.500 --> 00:31:37.170 align:start position:0% messages in parallel and each of those messages<00:31:35.770> contributes<00:31:36.550> to<00:31:36.670> the<00:31:36.760> fork<00:31:36.940> choice 00:31:37.170 --> 00:31:37.180 align:start position:0% messages contributes to the fork choice 00:31:37.180 --> 00:31:39.780 align:start position:0% messages contributes to the fork choice rule<00:31:37.480> allowing<00:31:38.170> the<00:31:38.500> chain<00:31:38.800> to<00:31:39.190> kind<00:31:39.460> of<00:31:39.520> soft 00:31:39.780 --> 00:31:39.790 align:start position:0% rule allowing the chain to kind of soft 00:31:39.790 --> 00:31:42.900 align:start position:0% rule allowing the chain to kind of soft converge<00:31:40.180> very<00:31:40.450> quickly<00:31:40.750> and<00:31:41.550> after<00:31:42.550> those 00:31:42.900 --> 00:31:42.910 align:start position:0% converge very quickly and after those 00:31:42.910 --> 00:31:45.270 align:start position:0% converge very quickly and after those messages<00:31:43.510> are<00:31:43.690> also<00:31:43.840> simultaneously<00:31:44.440> votes 00:31:45.270 --> 00:31:45.280 align:start position:0% messages are also simultaneously votes 00:31:45.280 --> 00:31:47.970 align:start position:0% messages are also simultaneously votes in<00:31:45.610> FFG<00:31:46.180> and<00:31:46.450> so<00:31:46.630> after<00:31:46.930> about<00:31:47.110> one<00:31:47.320> epoch<00:31:47.710> the 00:31:47.970 --> 00:31:47.980 align:start position:0% in FFG and so after about one epoch the 00:31:47.980 --> 00:31:52.230 align:start position:0% in FFG and so after about one epoch the blog<00:31:48.790> gets<00:31:49.270> justified<00:31:49.930> and<00:31:50.200> then<00:31:51.000> which<00:31:52.000> kind 00:31:52.230 --> 00:31:52.240 align:start position:0% blog gets justified and then which kind 00:31:52.240 --> 00:31:53.610 align:start position:0% blog gets justified and then which kind of<00:31:52.300> entrenches<00:31:52.870> it<00:31:53.020> in<00:31:53.110> the<00:31:53.170> fork<00:31:53.380> choice 00:31:53.610 --> 00:31:53.620 align:start position:0% of entrenches it in the fork choice 00:31:53.620 --> 00:31:55.500 align:start position:0% of entrenches it in the fork choice further<00:31:53.890> and<00:31:54.190> then<00:31:54.310> after<00:31:54.670> one<00:31:54.850> more<00:31:55.030> epoch<00:31:55.360> he 00:31:55.500 --> 00:31:55.510 align:start position:0% further and then after one more epoch he 00:31:55.510 --> 00:32:12.339 align:start position:0% further and then after one more epoch he gets<00:31:55.690> it<00:31:55.870> gets<00:31:56.230> finalized 00:32:12.339 --> 00:32:12.349 align:start position:0% 00:32:12.349 --> 00:32:15.919 align:start position:0% hey<00:32:13.349> I'm<00:32:14.009> dicot<00:32:14.429> Feist<00:32:14.699> and<00:32:15.059> I'm<00:32:15.570> going<00:32:15.839> to 00:32:15.919 --> 00:32:15.929 align:start position:0% hey I'm dicot Feist and I'm going to 00:32:15.929 --> 00:32:19.879 align:start position:0% hey I'm dicot Feist and I'm going to talk<00:32:16.139> about<00:32:16.399> randomness<00:32:17.399> in<00:32:18.619> Ethier<00:32:19.619> two 00:32:19.879 --> 00:32:19.889 align:start position:0% talk about randomness in Ethier two 00:32:19.889 --> 00:32:31.549 align:start position:0% talk about randomness in Ethier two point<00:32:20.099> oh<00:32:29.419> okay 00:32:31.549 --> 00:32:31.559 align:start position:0% point oh okay 00:32:31.559 --> 00:32:34.430 align:start position:0% point oh okay so<00:32:32.009> basically<00:32:32.519> I<00:32:33.089> quickly<00:32:33.659> want<00:32:34.019> to<00:32:34.109> summarize 00:32:34.430 --> 00:32:34.440 align:start position:0% so basically I quickly want to summarize 00:32:34.440 --> 00:32:37.339 align:start position:0% so basically I quickly want to summarize why<00:32:35.239> randomness<00:32:36.239> is<00:32:36.479> such<00:32:36.690> an<00:32:36.869> important 00:32:37.339 --> 00:32:37.349 align:start position:0% why randomness is such an important 00:32:37.349 --> 00:32:40.549 align:start position:0% why randomness is such an important problem<00:32:37.589> in<00:32:38.399> if<00:32:38.549> in<00:32:38.940> any<00:32:39.299> kind<00:32:40.109> of<00:32:40.199> proof<00:32:40.440> of 00:32:40.549 --> 00:32:40.559 align:start position:0% problem in if in any kind of proof of 00:32:40.559 --> 00:32:44.599 align:start position:0% problem in if in any kind of proof of stake<00:32:40.769> protocol<00:32:41.309> and<00:32:41.579> if<00:32:42.029> 2.0<00:32:43.190> I'm<00:32:44.190> going<00:32:44.519> to 00:32:44.599 --> 00:32:44.609 align:start position:0% stake protocol and if 2.0 I'm going to 00:32:44.609 --> 00:32:47.089 align:start position:0% stake protocol and if 2.0 I'm going to talk<00:32:44.789> about<00:32:44.969> run<00:32:45.539> now<00:32:45.749> which<00:32:46.079> is<00:32:46.319> our<00:32:46.499> first 00:32:47.089 --> 00:32:47.099 align:start position:0% talk about run now which is our first 00:32:47.099 --> 00:32:49.909 align:start position:0% talk about run now which is our first and<00:32:47.519> like<00:32:47.969> routine<00:32:48.599> routine<00:32:48.959> airy<00:32:49.289> source<00:32:49.649> of 00:32:49.909 --> 00:32:49.919 align:start position:0% and like routine routine airy source of 00:32:49.919 --> 00:32:53.809 align:start position:0% and like routine routine airy source of randomness<00:32:51.709> quickly<00:32:52.709> like<00:32:53.009> also<00:32:53.459> going<00:32:53.639> to 00:32:53.809 --> 00:32:53.819 align:start position:0% randomness quickly like also going to 00:32:53.819 --> 00:32:55.939 align:start position:0% randomness quickly like also going to the<00:32:54.149> the<00:32:54.599> issues<00:32:54.959> that<00:32:55.169> this<00:32:55.289> has<00:32:55.529> and<00:32:55.799> why 00:32:55.939 --> 00:32:55.949 align:start position:0% the the issues that this has and why 00:32:55.949 --> 00:32:58.399 align:start position:0% the the issues that this has and why like<00:32:56.399> in<00:32:56.789> the<00:32:57.149> final<00:32:57.359> protocol<00:32:58.019> in<00:32:58.169> a<00:32:58.259> few 00:32:58.399 --> 00:32:58.409 align:start position:0% like in the final protocol in a few 00:32:58.409 --> 00:32:59.989 align:start position:0% like in the final protocol in a few years<00:32:58.679> we're<00:32:58.799> going<00:32:58.979> to<00:32:59.069> use<00:32:59.219> a<00:32:59.519> verifiable 00:32:59.989 --> 00:32:59.999 align:start position:0% years we're going to use a verifiable 00:32:59.999 --> 00:33:03.199 align:start position:0% years we're going to use a verifiable delay<00:33:00.359> functions<00:33:00.839> to<00:33:01.049> improve<00:33:01.440> this<00:33:02.209> source 00:33:03.199 --> 00:33:03.209 align:start position:0% delay functions to improve this source 00:33:03.209 --> 00:33:07.639 align:start position:0% delay functions to improve this source of<00:33:03.329> randomness<00:33:05.419> so<00:33:06.419> why<00:33:06.599> is<00:33:06.659> it<00:33:06.929> so<00:33:07.109> important 00:33:07.639 --> 00:33:07.649 align:start position:0% of randomness so why is it so important 00:33:07.649 --> 00:33:09.169 align:start position:0% of randomness so why is it so important to<00:33:07.709> have<00:33:07.769> a<00:33:07.919> good<00:33:08.099> source<00:33:08.339> of<00:33:08.549> randomness<00:33:08.759> and 00:33:09.169 --> 00:33:09.179 align:start position:0% to have a good source of randomness and 00:33:09.179 --> 00:33:12.949 align:start position:0% to have a good source of randomness and proof<00:33:09.329> of<00:33:09.419> stake<00:33:10.309> well<00:33:11.309> so<00:33:11.789> we<00:33:12.509> need<00:33:12.690> to<00:33:12.809> do 00:33:12.949 --> 00:33:12.959 align:start position:0% proof of stake well so we need to do 00:33:12.959 --> 00:33:16.399 align:start position:0% proof of stake well so we need to do several<00:33:13.139> things<00:33:14.299> randomly<00:33:15.299> and<00:33:15.690> we<00:33:16.199> don't 00:33:16.399 --> 00:33:16.409 align:start position:0% several things randomly and we don't 00:33:16.409 --> 00:33:17.899 align:start position:0% several things randomly and we don't have<00:33:16.709> this<00:33:16.949> kind<00:33:17.309> of<00:33:17.399> proof<00:33:17.609> of<00:33:17.759> work 00:33:17.899 --> 00:33:17.909 align:start position:0% have this kind of proof of work 00:33:17.909 --> 00:33:19.789 align:start position:0% have this kind of proof of work randomness<00:33:18.539> that<00:33:18.569> we<00:33:18.839> have<00:33:18.959> in<00:33:19.109> proof<00:33:19.559> work 00:33:19.789 --> 00:33:19.799 align:start position:0% randomness that we have in proof work 00:33:19.799 --> 00:33:23.029 align:start position:0% randomness that we have in proof work chains<00:33:20.129> anymore<00:33:21.379> so<00:33:22.379> we<00:33:22.529> need<00:33:22.679> to<00:33:22.799> select 00:33:23.029 --> 00:33:23.039 align:start position:0% chains anymore so we need to select 00:33:23.039 --> 00:33:25.939 align:start position:0% chains anymore so we need to select proposes<00:33:23.669> we<00:33:24.509> need<00:33:24.629> to<00:33:24.779> select<00:33:25.049> committees 00:33:25.939 --> 00:33:25.949 align:start position:0% proposes we need to select committees 00:33:25.949 --> 00:33:30.289 align:start position:0% proposes we need to select committees and<00:33:26.819> we<00:33:27.719> need<00:33:28.159> also<00:33:29.159> like<00:33:29.609> as<00:33:29.789> an<00:33:29.909> extension 00:33:30.289 --> 00:33:30.299 align:start position:0% and we need also like as an extension 00:33:30.299 --> 00:33:33.979 align:start position:0% and we need also like as an extension like<00:33:30.779> some<00:33:31.699> contracts<00:33:32.699> on<00:33:32.849> chain<00:33:33.149> want<00:33:33.749> to<00:33:33.869> use 00:33:33.979 --> 00:33:33.989 align:start position:0% like some contracts on chain want to use 00:33:33.989 --> 00:33:35.299 align:start position:0% like some contracts on chain want to use randomness<00:33:34.619> and<00:33:34.769> we<00:33:34.889> need<00:33:35.039> to<00:33:35.129> provide 00:33:35.299 --> 00:33:35.309 align:start position:0% randomness and we need to provide 00:33:35.309 --> 00:33:36.799 align:start position:0% randomness and we need to provide randomness<00:33:35.969> for<00:33:36.149> these<00:33:36.269> as<00:33:36.449> well 00:33:36.799 --> 00:33:36.809 align:start position:0% randomness for these as well 00:33:36.809 --> 00:33:43.759 align:start position:0% randomness for these as well and<00:33:37.999> so<00:33:38.999> for<00:33:39.869> each<00:33:39.899> of<00:33:40.019> these<00:33:40.289> like<00:33:42.169> like<00:33:43.169> good 00:33:43.759 --> 00:33:43.769 align:start position:0% and so for each of these like like good 00:33:43.769 --> 00:33:46.809 align:start position:0% and so for each of these like like good roundness<00:33:44.219> required<00:33:44.789> for<00:33:45.119> proposes<00:33:45.719> because 00:33:46.809 --> 00:33:46.819 align:start position:0% roundness required for proposes because 00:33:46.819 --> 00:33:49.939 align:start position:0% roundness required for proposes because we<00:33:47.819> need<00:33:48.209> to<00:33:48.299> be<00:33:48.419> fair<00:33:48.719> like<00:33:48.959> we<00:33:49.169> distribute 00:33:49.939 --> 00:33:49.949 align:start position:0% we need to be fair like we distribute 00:33:49.949 --> 00:33:53.389 align:start position:0% we need to be fair like we distribute rewards<00:33:50.609> to<00:33:50.759> them<00:33:50.909> and<00:33:51.179> also<00:33:51.649> we<00:33:52.649> we<00:33:53.129> want<00:33:53.309> to 00:33:53.389 --> 00:33:53.399 align:start position:0% rewards to them and also we we want to 00:33:53.399 --> 00:33:55.430 align:start position:0% rewards to them and also we we want to protect<00:33:53.579> against<00:33:54.239> denial<00:33:54.959> of<00:33:55.109> service 00:33:55.430 --> 00:33:55.440 align:start position:0% protect against denial of service 00:33:55.440 --> 00:34:00.499 align:start position:0% protect against denial of service attacks<00:33:56.839> but<00:33:57.839> it's<00:33:58.829> especially<00:33:59.609> important 00:34:00.499 --> 00:34:00.509 align:start position:0% attacks but it's especially important 00:34:00.509 --> 00:34:03.319 align:start position:0% attacks but it's especially important for<00:34:00.809> the<00:34:01.589> for<00:34:02.039> the<00:34:02.129> committee<00:34:02.549> is<00:34:02.729> that<00:34:02.969> it<00:34:03.119> has 00:34:03.319 --> 00:34:03.329 align:start position:0% for the for the committee is that it has 00:34:03.329 --> 00:34:07.699 align:start position:0% for the for the committee is that it has to<00:34:04.289> the<00:34:04.409> short<00:34:04.679> chains<00:34:05.659> because<00:34:06.659> if<00:34:06.959> like<00:34:07.259> if 00:34:07.699 --> 00:34:07.709 align:start position:0% to the short chains because if like if 00:34:07.709 --> 00:34:09.829 align:start position:0% to the short chains because if like if the<00:34:07.919> committees<00:34:08.369> are<00:34:08.549> not<00:34:08.669> honest<00:34:09.059> like<00:34:09.480> the 00:34:09.829 --> 00:34:09.839 align:start position:0% the committees are not honest like the 00:34:09.839 --> 00:34:13.879 align:start position:0% the committees are not honest like the the<00:34:10.500> beacon<00:34:10.859> chain<00:34:11.069> cannot<00:34:12.019> cannot<00:34:13.019> check<00:34:13.559> the 00:34:13.879 --> 00:34:13.889 align:start position:0% the beacon chain cannot cannot check the 00:34:13.889 --> 00:34:16.430 align:start position:0% the beacon chain cannot cannot check the state<00:34:14.579> transitions<00:34:15.179> of<00:34:15.299> all<00:34:15.480> the<00:34:15.629> charge 00:34:16.430 --> 00:34:16.440 align:start position:0% state transitions of all the charge 00:34:16.440 --> 00:34:17.930 align:start position:0% state transitions of all the charge changed<00:34:16.889> because<00:34:17.099> that's<00:34:17.460> the<00:34:17.639> whole<00:34:17.730> point 00:34:17.930 --> 00:34:17.940 align:start position:0% changed because that's the whole point 00:34:17.940 --> 00:34:19.879 align:start position:0% changed because that's the whole point of<00:34:18.119> shouting<00:34:18.389> that<00:34:19.020> you<00:34:19.169> don't<00:34:19.349> have<00:34:19.649> this 00:34:19.879 --> 00:34:19.889 align:start position:0% of shouting that you don't have this 00:34:19.889 --> 00:34:22.790 align:start position:0% of shouting that you don't have this huge<00:34:20.429> load<00:34:20.669> on<00:34:20.849> the<00:34:20.940> beacon<00:34:21.179> chain<00:34:21.649> but<00:34:22.649> that 00:34:22.790 --> 00:34:22.800 align:start position:0% huge load on the beacon chain but that 00:34:22.800 --> 00:34:24.500 align:start position:0% huge load on the beacon chain but that means<00:34:23.069> we<00:34:23.339> can<00:34:23.520> have<00:34:23.700> to<00:34:24.000> trust<00:34:24.300> these 00:34:24.500 --> 00:34:24.510 align:start position:0% means we can have to trust these 00:34:24.510 --> 00:34:28.579 align:start position:0% means we can have to trust these committees<00:34:25.020> to<00:34:25.230> be<00:34:25.319> honest<00:34:26.089> and<00:34:27.349> we<00:34:28.349> can 00:34:28.579 --> 00:34:28.589 align:start position:0% committees to be honest and we can 00:34:28.589 --> 00:34:30.649 align:start position:0% committees to be honest and we can remedy<00:34:29.129> against<00:34:29.639> an<00:34:29.760> incorrect<00:34:30.210> vote<00:34:30.419> by<00:34:30.629> a 00:34:30.649 --> 00:34:30.659 align:start position:0% remedy against an incorrect vote by a 00:34:30.659 --> 00:34:32.510 align:start position:0% remedy against an incorrect vote by a commenter<00:34:31.139> using<00:34:31.409> for<00:34:31.679> proofs<00:34:32.010> but<00:34:32.250> we<00:34:32.369> don't 00:34:32.510 --> 00:34:32.520 align:start position:0% commenter using for proofs but we don't 00:34:32.520 --> 00:34:35.119 align:start position:0% commenter using for proofs but we don't want<00:34:32.760> to<00:34:32.849> have<00:34:32.970> too<00:34:33.149> many<00:34:33.300> of<00:34:33.510> these<00:34:34.129> and 00:34:35.119 --> 00:34:35.129 align:start position:0% want to have too many of these and 00:34:35.129 --> 00:34:40.159 align:start position:0% want to have too many of these and finally<00:34:37.310> we<00:34:38.310> also<00:34:38.669> want<00:34:39.210> that<00:34:39.419> smart<00:34:39.720> contacts 00:34:40.159 --> 00:34:40.169 align:start position:0% finally we also want that smart contacts 00:34:40.169 --> 00:34:43.700 align:start position:0% finally we also want that smart contacts can<00:34:40.379> use<00:34:40.589> randomness<00:34:41.429> and<00:34:42.530> yes<00:34:43.530> some 00:34:43.700 --> 00:34:43.710 align:start position:0% can use randomness and yes some 00:34:43.710 --> 00:34:45.710 align:start position:0% can use randomness and yes some applications<00:34:44.339> like<00:34:44.460> lotteries<00:34:45.089> or<00:34:45.270> so<00:34:45.450> might 00:34:45.710 --> 00:34:45.720 align:start position:0% applications like lotteries or so might 00:34:45.720 --> 00:34:47.659 align:start position:0% applications like lotteries or so might attach<00:34:46.200> a<00:34:46.319> huge<00:34:46.500> value<00:34:46.740> to<00:34:47.010> random<00:34:47.310> numbers 00:34:47.659 --> 00:34:47.669 align:start position:0% attach a huge value to random numbers 00:34:47.669 --> 00:34:50.419 align:start position:0% attach a huge value to random numbers and<00:34:47.879> like<00:34:48.780> if<00:34:49.109> you<00:34:49.290> can<00:34:49.530> somehow<00:34:49.800> attack<00:34:50.190> them 00:34:50.419 --> 00:34:50.429 align:start position:0% and like if you can somehow attack them 00:34:50.429 --> 00:34:52.659 align:start position:0% and like if you can somehow attack them that<00:34:50.639> might<00:34:50.879> degrade<00:34:51.599> the<00:34:51.990> randomness<00:34:52.440> in<00:34:52.470> the 00:34:52.659 --> 00:34:52.669 align:start position:0% that might degrade the randomness in the 00:34:52.669 --> 00:35:01.910 align:start position:0% that might degrade the randomness in the whole<00:34:53.669> system<00:34:59.990> right<00:35:00.990> and<00:35:01.290> then<00:35:01.589> a<00:35:01.770> bit 00:35:01.910 --> 00:35:01.920 align:start position:0% whole system right and then a bit 00:35:01.920 --> 00:35:04.730 align:start position:0% whole system right and then a bit further<00:35:02.190> on<00:35:02.490> their<00:35:02.670> committees<00:35:03.150> why<00:35:03.990> it<00:35:04.349> is<00:35:04.530> so 00:35:04.730 --> 00:35:04.740 align:start position:0% further on their committees why it is so 00:35:04.740 --> 00:35:06.890 align:start position:0% further on their committees why it is so important<00:35:05.190> this<00:35:05.339> is<00:35:05.430> like<00:35:05.700> a<00:35:05.940> very<00:35:06.390> central 00:35:06.890 --> 00:35:06.900 align:start position:0% important this is like a very central 00:35:06.900 --> 00:35:12.140 align:start position:0% important this is like a very central issue<00:35:07.319> they're<00:35:07.770> like<00:35:08.339> if<00:35:09.030> the<00:35:10.579> the<00:35:11.579> problem<00:35:12.000> is 00:35:12.140 --> 00:35:12.150 align:start position:0% issue they're like if the the problem is 00:35:12.150 --> 00:35:14.150 align:start position:0% issue they're like if the the problem is that<00:35:12.390> we<00:35:13.079> want<00:35:13.109> to<00:35:13.319> minimize<00:35:13.560> the<00:35:14.010> probability 00:35:14.150 --> 00:35:14.160 align:start position:0% that we want to minimize the probability 00:35:14.160 --> 00:35:18.309 align:start position:0% that we want to minimize the probability for<00:35:14.790> having<00:35:15.000> a<00:35:15.089> dishonest<00:35:15.960> committee<00:35:17.180> and 00:35:18.309 --> 00:35:18.319 align:start position:0% for having a dishonest committee and 00:35:18.319 --> 00:35:21.559 align:start position:0% for having a dishonest committee and like<00:35:19.319> a<00:35:19.650> bad<00:35:20.160> committee<00:35:20.670> could<00:35:21.000> potentially 00:35:21.559 --> 00:35:21.569 align:start position:0% like a bad committee could potentially 00:35:21.569 --> 00:35:23.990 align:start position:0% like a bad committee could potentially create<00:35:21.930> a<00:35:22.589> link<00:35:23.130> to<00:35:23.369> an<00:35:23.430> invalid<00:35:23.700> or 00:35:23.990 --> 00:35:24.000 align:start position:0% create a link to an invalid or 00:35:24.000 --> 00:35:27.650 align:start position:0% create a link to an invalid or non-existent<00:35:24.690> block<00:35:25.400> and<00:35:26.400> a<00:35:26.790> fraud<00:35:27.300> proof 00:35:27.650 --> 00:35:27.660 align:start position:0% non-existent block and a fraud proof 00:35:27.660 --> 00:35:29.270 align:start position:0% non-existent block and a fraud proof would<00:35:28.079> mean<00:35:28.290> that<00:35:28.440> you<00:35:28.589> have<00:35:28.770> to<00:35:28.950> revert<00:35:29.250> the 00:35:29.270 --> 00:35:29.280 align:start position:0% would mean that you have to revert the 00:35:29.280 --> 00:35:32.120 align:start position:0% would mean that you have to revert the state<00:35:30.089> of<00:35:30.240> the<00:35:30.359> beacon<00:35:30.690> chain<00:35:30.900> until<00:35:31.200> like 00:35:32.120 --> 00:35:32.130 align:start position:0% state of the beacon chain until like 00:35:32.130 --> 00:35:34.609 align:start position:0% state of the beacon chain until like when<00:35:32.430> that<00:35:32.579> happened<00:35:33.000> so<00:35:33.900> like<00:35:34.410> the 00:35:34.609 --> 00:35:34.619 align:start position:0% when that happened so like the 00:35:34.619 --> 00:35:36.319 align:start position:0% when that happened so like the probability<00:35:35.010> if<00:35:35.369> you<00:35:35.490> have<00:35:35.609> a<00:35:35.640> committee<00:35:36.119> size 00:35:36.319 --> 00:35:36.329 align:start position:0% probability if you have a committee size 00:35:36.329 --> 00:35:40.040 align:start position:0% probability if you have a committee size of<00:35:36.859> 128<00:35:37.859> then<00:35:38.579> it's<00:35:38.760> quite<00:35:38.970> small<00:35:39.359> five<00:35:39.750> times 00:35:40.040 --> 00:35:40.050 align:start position:0% of 128 then it's quite small five times 00:35:40.050 --> 00:35:43.460 align:start position:0% of 128 then it's quite small five times 10<00:35:40.290> to<00:35:40.380> the<00:35:40.440> minus<00:35:40.710> 15<00:35:41.180> but<00:35:42.180> this<00:35:42.690> kind<00:35:43.109> of<00:35:43.170> kind 00:35:43.460 --> 00:35:43.470 align:start position:0% 10 to the minus 15 but this kind of kind 00:35:43.470 --> 00:35:45.349 align:start position:0% 10 to the minus 15 but this kind of kind of<00:35:43.619> cost<00:35:43.890> completely<00:35:44.339> changed<00:35:44.730> as<00:35:44.880> soon<00:35:45.119> as 00:35:45.349 --> 00:35:45.359 align:start position:0% of cost completely changed as soon as 00:35:45.359 --> 00:35:47.870 align:start position:0% of cost completely changed as soon as someone<00:35:46.230> can<00:35:46.500> bias<00:35:46.740> the<00:35:47.069> randomness<00:35:47.640> that 00:35:47.870 --> 00:35:47.880 align:start position:0% someone can bias the randomness that 00:35:47.880 --> 00:35:51.770 align:start position:0% someone can bias the randomness that we're<00:35:48.300> using<00:35:49.280> right<00:35:50.280> so<00:35:50.790> the<00:35:50.910> idea<00:35:51.210> behind<00:35:51.359> run 00:35:51.770 --> 00:35:51.780 align:start position:0% we're using right so the idea behind run 00:35:51.780 --> 00:35:55.040 align:start position:0% we're using right so the idea behind run now<00:35:51.990> is<00:35:52.260> let's<00:35:53.160> say<00:35:53.369> like<00:35:53.609> we<00:35:53.849> have<00:35:53.880> n<00:35:54.750> people 00:35:55.040 --> 00:35:55.050 align:start position:0% now is let's say like we have n people 00:35:55.050 --> 00:35:57.550 align:start position:0% now is let's say like we have n people who<00:35:55.500> want<00:35:55.740> to<00:35:55.800> generate<00:35:56.220> a<00:35:56.280> random<00:35:56.490> number 00:35:57.550 --> 00:35:57.560 align:start position:0% who want to generate a random number 00:35:57.560 --> 00:36:00.859 align:start position:0% who want to generate a random number everyone<00:35:58.560> goes<00:35:58.770> into<00:35:58.950> a<00:35:59.069> room<00:35:59.869> everyone 00:36:00.859 --> 00:36:00.869 align:start position:0% everyone goes into a room everyone 00:36:00.869 --> 00:36:04.130 align:start position:0% everyone goes into a room everyone contributes<00:36:01.440> one<00:36:01.800> random<00:36:02.280> value<00:36:02.579> X<00:36:02.790> I<00:36:03.140> you 00:36:04.130 --> 00:36:04.140 align:start position:0% contributes one random value X I you 00:36:04.140 --> 00:36:06.970 align:start position:0% contributes one random value X I you compute<00:36:04.710> the<00:36:04.859> X<00:36:05.040> off<00:36:05.310> all<00:36:05.609> these<00:36:05.790> values<00:36:06.240> right 00:36:06.970 --> 00:36:06.980 align:start position:0% compute the X off all these values right 00:36:06.980 --> 00:36:09.800 align:start position:0% compute the X off all these values right so<00:36:07.980> that<00:36:08.369> sounds<00:36:09.180> like<00:36:09.240> it<00:36:09.480> could<00:36:09.660> get 00:36:09.800 --> 00:36:09.810 align:start position:0% so that sounds like it could get 00:36:09.810 --> 00:36:12.230 align:start position:0% so that sounds like it could get generate<00:36:10.230> good<00:36:10.410> randomness<00:36:11.010> but<00:36:11.700> the<00:36:11.849> problem 00:36:12.230 --> 00:36:12.240 align:start position:0% generate good randomness but the problem 00:36:12.240 --> 00:36:14.180 align:start position:0% generate good randomness but the problem with<00:36:12.390> that<00:36:12.480> is<00:36:12.720> the<00:36:13.020> last<00:36:13.170> player<00:36:13.560> can<00:36:13.980> just 00:36:14.180 --> 00:36:14.190 align:start position:0% with that is the last player can just 00:36:14.190 --> 00:36:16.819 align:start position:0% with that is the last player can just change<00:36:14.490> their<00:36:14.819> value<00:36:15.270> after<00:36:16.050> they<00:36:16.440> have<00:36:16.560> seen 00:36:16.819 --> 00:36:16.829 align:start position:0% change their value after they have seen 00:36:16.829 --> 00:36:19.760 align:start position:0% change their value after they have seen everyone<00:36:17.130> else's<00:36:17.430> value<00:36:18.150> and<00:36:18.359> then<00:36:18.770> they 00:36:19.760 --> 00:36:19.770 align:start position:0% everyone else's value and then they 00:36:19.770 --> 00:36:21.950 align:start position:0% everyone else's value and then they change<00:36:20.069> their<00:36:20.339> choice<00:36:20.550> and<00:36:20.940> like<00:36:21.420> get 00:36:21.950 --> 00:36:21.960 align:start position:0% change their choice and like get 00:36:21.960 --> 00:36:22.760 align:start position:0% change their choice and like get whatever<00:36:22.230> they<00:36:22.410> want 00:36:22.760 --> 00:36:22.770 align:start position:0% whatever they want 00:36:22.770 --> 00:36:29.569 align:start position:0% whatever they want okay<00:36:23.430> so<00:36:24.089> let's<00:36:24.300> improve<00:36:24.660> this<00:36:26.000> so<00:36:28.579> with 00:36:29.569 --> 00:36:29.579 align:start position:0% okay so let's improve this so with 00:36:29.579 --> 00:36:30.620 align:start position:0% okay so let's improve this so with commits<00:36:29.910> reveal 00:36:30.620 --> 00:36:30.630 align:start position:0% commits reveal 00:36:30.630 --> 00:36:34.250 align:start position:0% commits reveal we<00:36:31.230> can<00:36:32.120> start<00:36:33.120> the<00:36:33.300> same<00:36:33.510> they<00:36:33.750> all<00:36:33.840> go<00:36:33.990> into<00:36:34.230> a 00:36:34.250 --> 00:36:34.260 align:start position:0% we can start the same they all go into a 00:36:34.260 --> 00:36:38.180 align:start position:0% we can start the same they all go into a room<00:36:34.440> and<00:36:35.000> they<00:36:36.000> each<00:36:36.330> commit<00:36:36.900> to<00:36:37.590> their<00:36:37.860> value 00:36:38.180 --> 00:36:38.190 align:start position:0% room and they each commit to their value 00:36:38.190 --> 00:36:41.620 align:start position:0% room and they each commit to their value ex<00:36:38.370> I<00:36:38.640> by<00:36:39.530> telling<00:36:40.530> everyone<00:36:40.740> the<00:36:40.920> hash<00:36:41.100> and 00:36:41.620 --> 00:36:41.630 align:start position:0% ex I by telling everyone the hash and 00:36:41.630 --> 00:36:44.120 align:start position:0% ex I by telling everyone the hash and then<00:36:42.630> they<00:36:42.840> reveal<00:36:43.110> their<00:36:43.290> value<00:36:43.590> we<00:36:43.740> compute 00:36:44.120 --> 00:36:44.130 align:start position:0% then they reveal their value we compute 00:36:44.130 --> 00:36:47.720 align:start position:0% then they reveal their value we compute the<00:36:44.220> XOR<00:36:44.640> of<00:36:44.700> those<00:36:45.030> values<00:36:45.420> again<00:36:45.690> okay<00:36:46.530> so<00:36:47.340> in 00:36:47.720 --> 00:36:47.730 align:start position:0% the XOR of those values again okay so in 00:36:47.730 --> 00:36:49.910 align:start position:0% the XOR of those values again okay so in this<00:36:47.850> case<00:36:48.150> this<00:36:48.450> cannot<00:36:49.080> be<00:36:49.230> manipulated 00:36:49.910 --> 00:36:49.920 align:start position:0% this case this cannot be manipulated 00:36:49.920 --> 00:36:52.850 align:start position:0% this case this cannot be manipulated because<00:36:50.550> we<00:36:50.700> force<00:36:51.000> everyone<00:36:51.570> to<00:36:52.260> reveal 00:36:52.850 --> 00:36:52.860 align:start position:0% because we force everyone to reveal 00:36:52.860 --> 00:36:54.080 align:start position:0% because we force everyone to reveal their<00:36:53.070> value<00:36:53.370> because<00:36:53.490> they<00:36:53.790> were<00:36:53.850> all<00:36:53.970> in<00:36:54.000> the 00:36:54.080 --> 00:36:54.090 align:start position:0% their value because they were all in the 00:36:54.090 --> 00:36:57.980 align:start position:0% their value because they were all in the same<00:36:54.300> room<00:36:54.830> but<00:36:56.180> in<00:36:57.180> the<00:36:57.420> real<00:36:57.600> world<00:36:57.780> the 00:36:57.980 --> 00:36:57.990 align:start position:0% same room but in the real world the 00:36:57.990 --> 00:36:59.870 align:start position:0% same room but in the real world the problem<00:36:58.230> is<00:36:58.500> anyone<00:36:58.890> can<00:36:59.100> stop<00:36:59.400> this<00:36:59.580> process 00:36:59.870 --> 00:36:59.880 align:start position:0% problem is anyone can stop this process 00:36:59.880 --> 00:37:03.200 align:start position:0% problem is anyone can stop this process by<00:37:00.720> not<00:37:01.320> not<00:37:02.250> actually<00:37:02.610> revealing<00:37:02.970> their 00:37:03.200 --> 00:37:03.210 align:start position:0% by not not actually revealing their 00:37:03.210 --> 00:37:04.880 align:start position:0% by not not actually revealing their preimage<00:37:03.630> and<00:37:03.840> then<00:37:03.960> we<00:37:04.110> can't<00:37:04.320> compute<00:37:04.680> this 00:37:04.880 --> 00:37:04.890 align:start position:0% preimage and then we can't compute this 00:37:04.890 --> 00:37:09.950 align:start position:0% preimage and then we can't compute this XOR<00:37:05.360> right<00:37:06.680> so<00:37:07.680> run<00:37:08.460> now<00:37:08.640> basically<00:37:09.150> builds<00:37:09.450> on 00:37:09.950 --> 00:37:09.960 align:start position:0% XOR right so run now basically builds on 00:37:09.960 --> 00:37:15.640 align:start position:0% XOR right so run now basically builds on this<00:37:10.200> idea<00:37:10.880> so<00:37:11.880> we<00:37:12.600> make<00:37:13.230> every<00:37:13.820> everyone 00:37:15.640 --> 00:37:15.650 align:start position:0% this idea so we make every everyone 00:37:15.650 --> 00:37:19.270 align:start position:0% this idea so we make every everyone who's<00:37:16.650> a<00:37:16.680> validator<00:37:17.160> has<00:37:17.430> already<00:37:17.610> committed 00:37:19.270 --> 00:37:19.280 align:start position:0% who's a validator has already committed 00:37:19.280 --> 00:37:21.770 align:start position:0% who's a validator has already committed to<00:37:20.280> something<00:37:20.490> in<00:37:20.970> our<00:37:21.090> case<00:37:21.420> is<00:37:21.600> actually 00:37:21.770 --> 00:37:21.780 align:start position:0% to something in our case is actually 00:37:21.780 --> 00:37:23.890 align:start position:0% to something in our case is actually their<00:37:22.290> signature<00:37:22.800> because<00:37:23.460> we<00:37:23.610> have<00:37:23.760> a 00:37:23.890 --> 00:37:23.900 align:start position:0% their signature because we have a 00:37:23.900 --> 00:37:28.850 align:start position:0% their signature because we have a deterministic<00:37:24.900> signature<00:37:25.700> scheme<00:37:26.700> BLS<00:37:27.860> we 00:37:28.850 --> 00:37:28.860 align:start position:0% deterministic signature scheme BLS we 00:37:28.860 --> 00:37:31.040 align:start position:0% deterministic signature scheme BLS we can<00:37:29.010> just<00:37:29.220> use<00:37:29.400> a<00:37:29.430> signature<00:37:29.820> as<00:37:30.180> a<00:37:30.690> reveal 00:37:31.040 --> 00:37:31.050 align:start position:0% can just use a signature as a reveal 00:37:31.050 --> 00:37:32.480 align:start position:0% can just use a signature as a reveal everyone<00:37:31.560> can<00:37:31.800> check<00:37:31.980> that<00:37:32.190> this<00:37:32.340> was<00:37:32.460> a 00:37:32.480 --> 00:37:32.490 align:start position:0% everyone can check that this was a 00:37:32.490 --> 00:37:35.060 align:start position:0% everyone can check that this was a correct<00:37:32.850> signature<00:37:33.150> so<00:37:33.810> you<00:37:33.870> sign<00:37:34.230> the<00:37:34.680> epoch 00:37:35.060 --> 00:37:35.070 align:start position:0% correct signature so you sign the epoch 00:37:35.070 --> 00:37:38.930 align:start position:0% correct signature so you sign the epoch this<00:37:35.490> is<00:37:36.240> denoted<00:37:36.750> by<00:37:36.930> E<00:37:37.050> here<00:37:37.470> and<00:37:37.940> that's 00:37:38.930 --> 00:37:38.940 align:start position:0% this is denoted by E here and that's 00:37:38.940 --> 00:37:42.050 align:start position:0% this is denoted by E here and that's that's<00:37:39.210> the<00:37:39.510> reveals<00:37:39.810> and<00:37:40.170> then<00:37:40.730> what<00:37:41.730> can<00:37:41.910> of 00:37:42.050 --> 00:37:42.060 align:start position:0% that's the reveals and then what can of 00:37:42.060 --> 00:37:45.070 align:start position:0% that's the reveals and then what can of course<00:37:42.270> happen<00:37:42.600> is<00:37:42.810> that<00:37:43.320> someone<00:37:43.770> does<00:37:44.010> not 00:37:45.070 --> 00:37:45.080 align:start position:0% course happen is that someone does not 00:37:45.080 --> 00:37:48.020 align:start position:0% course happen is that someone does not produce<00:37:46.080> a<00:37:46.350> block<00:37:46.530> and<00:37:46.890> so<00:37:47.130> they<00:37:47.280> they<00:37:47.700> haven't 00:37:48.020 --> 00:37:48.030 align:start position:0% produce a block and so they they haven't 00:37:48.030 --> 00:37:50.300 align:start position:0% produce a block and so they they haven't revered<00:37:48.330> the<00:37:48.480> randomness<00:37:48.930> and<00:37:49.110> then<00:37:49.650> we 00:37:50.300 --> 00:37:50.310 align:start position:0% revered the randomness and then we 00:37:50.310 --> 00:37:56.710 align:start position:0% revered the randomness and then we cannot<00:37:50.610> include<00:37:50.940> them<00:37:51.650> in<00:37:52.650> this<00:37:53.930> XOR<00:37:54.930> yeah 00:37:56.710 --> 00:37:56.720 align:start position:0% cannot include them in this XOR yeah 00:37:56.720 --> 00:37:59.180 align:start position:0% cannot include them in this XOR yeah okay<00:37:57.720> so<00:37:57.780> that<00:37:57.990> is<00:37:58.140> the<00:37:58.260> basic<00:37:58.560> process<00:37:58.770> of<00:37:59.010> run 00:37:59.180 --> 00:37:59.190 align:start position:0% okay so that is the basic process of run 00:37:59.190 --> 00:38:02.900 align:start position:0% okay so that is the basic process of run now<00:37:59.480> and<00:38:00.480> and<00:38:01.140> this<00:38:01.260> is<00:38:01.320> used<00:38:01.830> as<00:38:02.190> a<00:38:02.580> first 00:38:02.900 --> 00:38:02.910 align:start position:0% now and and this is used as a first 00:38:02.910 --> 00:38:06.490 align:start position:0% now and and this is used as a first instance<00:38:03.390> to<00:38:03.450> generate<00:38:03.930> randomness<00:38:04.470> eath<00:38:04.980> 2.0 00:38:06.490 --> 00:38:06.500 align:start position:0% instance to generate randomness eath 2.0 00:38:06.500 --> 00:38:10.810 align:start position:0% instance to generate randomness eath 2.0 it<00:38:07.500> only<00:38:08.430> has<00:38:08.730> one<00:38:08.760> problem<00:38:09.210> basically<00:38:09.740> that 00:38:10.810 --> 00:38:10.820 align:start position:0% it only has one problem basically that 00:38:10.820 --> 00:38:14.690 align:start position:0% it only has one problem basically that whoever<00:38:11.820> is<00:38:12.030> last<00:38:12.330> in<00:38:12.600> an<00:38:12.720> epoch<00:38:13.490> can<00:38:14.490> just 00:38:14.690 --> 00:38:14.700 align:start position:0% whoever is last in an epoch can just 00:38:14.700 --> 00:38:18.200 align:start position:0% whoever is last in an epoch can just choose<00:38:15.030> to<00:38:15.330> not<00:38:15.510> produce<00:38:16.020> a<00:38:16.170> block<00:38:17.210> so 00:38:18.200 --> 00:38:18.210 align:start position:0% choose to not produce a block so 00:38:18.210 --> 00:38:21.170 align:start position:0% choose to not produce a block so basically<00:38:18.960> what<00:38:19.470> does<00:38:19.620> what<00:38:20.550> this<00:38:20.700> means<00:38:20.910> is 00:38:21.170 --> 00:38:21.180 align:start position:0% basically what does what this means is 00:38:21.180 --> 00:38:23.870 align:start position:0% basically what does what this means is if<00:38:22.080> I<00:38:22.410> don't<00:38:22.590> like<00:38:22.770> the<00:38:22.980> result<00:38:23.400> of<00:38:23.640> whatever 00:38:23.870 --> 00:38:23.880 align:start position:0% if I don't like the result of whatever 00:38:23.880 --> 00:38:26.240 align:start position:0% if I don't like the result of whatever this<00:38:24.480> reveal<00:38:25.320> that<00:38:25.560> I'm<00:38:25.710> going<00:38:25.920> to<00:38:25.980> contribute 00:38:26.240 --> 00:38:26.250 align:start position:0% this reveal that I'm going to contribute 00:38:26.250 --> 00:38:29.270 align:start position:0% this reveal that I'm going to contribute this<00:38:26.520> like<00:38:26.850> I<00:38:26.970> can<00:38:27.150> compute<00:38:27.510> whatever<00:38:27.780> the<00:38:28.470> mix 00:38:29.270 --> 00:38:29.280 align:start position:0% this like I can compute whatever the mix 00:38:29.280 --> 00:38:31.820 align:start position:0% this like I can compute whatever the mix would<00:38:29.520> be<00:38:29.960> then<00:38:30.960> I<00:38:30.990> just<00:38:31.320> don't<00:38:31.530> contribute 00:38:31.820 --> 00:38:31.830 align:start position:0% would be then I just don't contribute 00:38:31.830 --> 00:38:34.280 align:start position:0% would be then I just don't contribute and<00:38:32.190> it's<00:38:32.280> as<00:38:32.430> if<00:38:32.610> I<00:38:32.760> would<00:38:32.970> get<00:38:33.270> another<00:38:33.600> roll 00:38:34.280 --> 00:38:34.290 align:start position:0% and it's as if I would get another roll 00:38:34.290 --> 00:38:38.330 align:start position:0% and it's as if I would get another roll of<00:38:34.440> dice<00:38:34.650> essentially<00:38:36.470> and<00:38:37.470> like<00:38:37.770> you<00:38:38.100> can 00:38:38.330 --> 00:38:38.340 align:start position:0% of dice essentially and like you can 00:38:38.340 --> 00:38:42.170 align:start position:0% of dice essentially and like you can that<00:38:38.940> can<00:38:39.180> be<00:38:39.330> worse<00:38:39.810> if<00:38:40.490> if<00:38:41.490> you<00:38:41.730> control 00:38:42.170 --> 00:38:42.180 align:start position:0% that can be worse if if you control 00:38:42.180 --> 00:38:43.830 align:start position:0% that can be worse if if you control several<00:38:42.480> validators<00:38:43.230> in<00:38:43.320> a<00:38:43.410> row 00:38:43.830 --> 00:38:43.840 align:start position:0% several validators in a row 00:38:43.840 --> 00:38:46.920 align:start position:0% several validators in a row course<00:38:43.990> than<00:38:44.230> more<00:38:44.470> bias<00:38:44.680> as<00:38:44.950> possible<00:38:45.930> so 00:38:46.920 --> 00:38:46.930 align:start position:0% course than more bias as possible so 00:38:46.930 --> 00:38:50.130 align:start position:0% course than more bias as possible so like<00:38:47.140> there<00:38:47.350> was<00:38:47.530> one<00:38:48.480> nice<00:38:49.480> analysis<00:38:49.990> by 00:38:50.130 --> 00:38:50.140 align:start position:0% like there was one nice analysis by 00:38:50.140 --> 00:38:52.350 align:start position:0% like there was one nice analysis by vitalic<00:38:50.620> on<00:38:51.160> his<00:38:51.280> research<00:38:51.670> where<00:38:52.000> he<00:38:52.120> showed 00:38:52.350 --> 00:38:52.360 align:start position:0% vitalic on his research where he showed 00:38:52.360 --> 00:38:54.450 align:start position:0% vitalic on his research where he showed that<00:38:52.570> if<00:38:52.780> you<00:38:53.080> just<00:38:53.500> have<00:38:53.710> a<00:38:53.740> longest<00:38:54.130> chain 00:38:54.450 --> 00:38:54.460 align:start position:0% that if you just have a longest chain 00:38:54.460 --> 00:38:57.330 align:start position:0% that if you just have a longest chain fork<00:38:54.880> choice<00:38:55.120> rule<00:38:55.360> then<00:38:56.050> with<00:38:56.740> just<00:38:57.010> 36 00:38:57.330 --> 00:38:57.340 align:start position:0% fork choice rule then with just 36 00:38:57.340 --> 00:38:59.870 align:start position:0% fork choice rule then with just 36 percent<00:38:57.940> of<00:38:58.060> the<00:38:58.210> stake<00:38:58.450> you<00:38:58.960> can<00:38:59.170> actually 00:38:59.870 --> 00:38:59.880 align:start position:0% percent of the stake you can actually 00:38:59.880 --> 00:39:02.520 align:start position:0% percent of the stake you can actually completely<00:39:00.880> take<00:39:01.090> over<00:39:01.270> a<00:39:01.660> chain<00:39:01.900> that's<00:39:02.170> bait 00:39:02.520 --> 00:39:02.530 align:start position:0% completely take over a chain that's bait 00:39:02.530 --> 00:39:04.620 align:start position:0% completely take over a chain that's bait that<00:39:02.800> choose<00:39:03.310> the<00:39:03.460> step<00:39:03.670> blocks<00:39:03.940> based<00:39:04.240> on<00:39:04.450> run 00:39:04.620 --> 00:39:04.630 align:start position:0% that choose the step blocks based on run 00:39:04.630 --> 00:39:10.380 align:start position:0% that choose the step blocks based on run down<00:39:04.840> that<00:39:05.560> block<00:39:05.740> producers<00:39:07.440> right<00:39:08.440> so<00:39:09.390> what 00:39:10.380 --> 00:39:10.390 align:start position:0% down that block producers right so what 00:39:10.390 --> 00:39:13.200 align:start position:0% down that block producers right so what ran<00:39:10.570> now<00:39:10.750> is<00:39:10.900> sort<00:39:11.080> of<00:39:11.200> our<00:39:11.350> first<00:39:12.120> source<00:39:13.120> of 00:39:13.200 --> 00:39:13.210 align:start position:0% ran now is sort of our first source of 00:39:13.210 --> 00:39:14.430 align:start position:0% ran now is sort of our first source of randomness<00:39:13.390> in<00:39:13.720> the<00:39:13.840> beginning<00:39:14.230> it's 00:39:14.430 --> 00:39:14.440 align:start position:0% randomness in the beginning it's 00:39:14.440 --> 00:39:18.020 align:start position:0% randomness in the beginning it's obviously<00:39:15.250> as<00:39:15.400> I've<00:39:15.550> shown<00:39:15.790> not<00:39:16.230> perfect<00:39:17.230> but 00:39:18.020 --> 00:39:18.030 align:start position:0% obviously as I've shown not perfect but 00:39:18.030 --> 00:39:20.340 align:start position:0% obviously as I've shown not perfect but at<00:39:19.030> the<00:39:19.210> moment<00:39:19.360> we<00:39:19.630> don't<00:39:19.750> have<00:39:19.870> anything 00:39:20.340 --> 00:39:20.350 align:start position:0% at the moment we don't have anything 00:39:20.350 --> 00:39:23.760 align:start position:0% at the moment we don't have anything better<00:39:21.090> so<00:39:22.090> like<00:39:22.360> in<00:39:22.630> the<00:39:22.720> future<00:39:23.080> what<00:39:23.590> we're 00:39:23.760 --> 00:39:23.770 align:start position:0% better so like in the future what we're 00:39:23.770 --> 00:39:25.620 align:start position:0% better so like in the future what we're going<00:39:23.950> to<00:39:24.010> build<00:39:24.220> is<00:39:24.460> honestly<00:39:25.390> like 00:39:25.620 --> 00:39:25.630 align:start position:0% going to build is honestly like 00:39:25.630 --> 00:39:28.500 align:start position:0% going to build is honestly like so-called<00:39:26.530> verifiable<00:39:27.040> delay<00:39:27.310> function<00:39:27.820> the 00:39:28.500 --> 00:39:28.510 align:start position:0% so-called verifiable delay function the 00:39:28.510 --> 00:39:33.990 align:start position:0% so-called verifiable delay function the idea<00:39:28.810> is<00:39:29.050> that<00:39:29.470> you<00:39:30.250> have<00:39:30.430> a<00:39:30.640> function<00:39:32.580> f<00:39:33.580> of<00:39:33.730> X 00:39:33.990 --> 00:39:34.000 align:start position:0% idea is that you have a function f of X 00:39:34.000 --> 00:39:36.840 align:start position:0% idea is that you have a function f of X that<00:39:34.210> produce<00:39:34.390> the<00:39:34.690> results<00:39:35.140> Y<00:39:35.530> and<00:39:35.920> prove<00:39:36.580> PI 00:39:36.840 --> 00:39:36.850 align:start position:0% that produce the results Y and prove PI 00:39:36.850 --> 00:39:39.660 align:start position:0% that produce the results Y and prove PI and<00:39:37.180> such<00:39:38.140> that<00:39:38.440> the<00:39:38.800> computing<00:39:39.550> this 00:39:39.660 --> 00:39:39.670 align:start position:0% and such that the computing this 00:39:39.670 --> 00:39:42.330 align:start position:0% and such that the computing this function<00:39:40.120> takes<00:39:40.360> a<00:39:40.480> long<00:39:40.690> serial<00:39:41.230> time<00:39:41.470> right 00:39:42.330 --> 00:39:42.340 align:start position:0% function takes a long serial time right 00:39:42.340 --> 00:39:44.490 align:start position:0% function takes a long serial time right so<00:39:42.370> you<00:39:42.640> can't<00:39:43.000> speed<00:39:43.480> it<00:39:43.510> up<00:39:43.780> by<00:39:44.080> having<00:39:44.260> many 00:39:44.490 --> 00:39:44.500 align:start position:0% so you can't speed it up by having many 00:39:44.500 --> 00:39:46.800 align:start position:0% so you can't speed it up by having many processors<00:39:45.070> it's<00:39:45.430> like<00:39:45.610> you<00:39:46.090> have<00:39:46.270> to<00:39:46.420> run<00:39:46.630> and 00:39:46.800 --> 00:39:46.810 align:start position:0% processors it's like you have to run and 00:39:46.810 --> 00:39:49.830 align:start position:0% processors it's like you have to run and see<00:39:46.990> really<00:39:47.230> on<00:39:47.470> one<00:39:47.650> processor<00:39:48.600> and<00:39:49.600> then 00:39:49.830 --> 00:39:49.840 align:start position:0% see really on one processor and then 00:39:49.840 --> 00:39:52.410 align:start position:0% see really on one processor and then checking<00:39:50.170> the<00:39:50.470> result<00:39:50.890> that<00:39:51.100> the<00:39:51.760> reason<00:39:52.210> why 00:39:52.410 --> 00:39:52.420 align:start position:0% checking the result that the reason why 00:39:52.420 --> 00:39:53.360 align:start position:0% checking the result that the reason why is<00:39:52.480> correct 00:39:53.360 --> 00:39:53.370 align:start position:0% is correct 00:39:53.370 --> 00:39:58.290 align:start position:0% is correct using<00:39:54.370> the<00:39:54.460> proof<00:39:54.640> pi<00:39:54.850> is<00:39:55.180> fast<00:39:56.100> and<00:39:57.100> so<00:39:58.090> one 00:39:58.290 --> 00:39:58.300 align:start position:0% using the proof pi is fast and so one 00:39:58.300 --> 00:39:59.850 align:start position:0% using the proof pi is fast and so one example<00:39:58.660> which<00:39:58.960> is<00:39:59.080> actually<00:39:59.410> the<00:39:59.530> one<00:39:59.650> that 00:39:59.850 --> 00:39:59.860 align:start position:0% example which is actually the one that 00:39:59.860 --> 00:40:02.520 align:start position:0% example which is actually the one that will<00:40:00.670> we<00:40:01.300> are<00:40:01.420> very<00:40:01.630> likely<00:40:01.840> going<00:40:02.140> to<00:40:02.230> end<00:40:02.410> up 00:40:02.520 --> 00:40:02.530 align:start position:0% will we are very likely going to end up 00:40:02.530 --> 00:40:07.290 align:start position:0% will we are very likely going to end up using<00:40:02.850> is<00:40:03.850> this<00:40:04.890> squaring<00:40:05.890> modular<00:40:06.370> and<00:40:06.640> RSA 00:40:07.290 --> 00:40:07.300 align:start position:0% using is this squaring modular and RSA 00:40:07.300 --> 00:40:10.620 align:start position:0% using is this squaring modular and RSA modulus<00:40:07.750> so<00:40:08.020> power<00:40:08.470> taking<00:40:09.460> many<00:40:10.000> squares<00:40:10.450> of 00:40:10.620 --> 00:40:10.630 align:start position:0% modulus so power taking many squares of 00:40:10.630 --> 00:40:15.480 align:start position:0% modulus so power taking many squares of X<00:40:10.840> modulo<00:40:11.370> M<00:40:12.370> where<00:40:12.700> m<00:40:12.730> is<00:40:12.880> P<00:40:13.480> times<00:40:13.660> Q<00:40:14.160> is<00:40:15.160> like 00:40:15.480 --> 00:40:15.490 align:start position:0% X modulo M where m is P times Q is like 00:40:15.490 --> 00:40:18.780 align:start position:0% X modulo M where m is P times Q is like one<00:40:16.060> way<00:40:16.240> to<00:40:16.300> construct<00:40:16.810> such<00:40:17.110> a<00:40:17.790> verifiable 00:40:18.780 --> 00:40:18.790 align:start position:0% one way to construct such a verifiable 00:40:18.790 --> 00:40:23.610 align:start position:0% one way to construct such a verifiable di<00:40:19.120> function<00:40:20.310> and<00:40:21.360> by<00:40:22.360> using<00:40:22.600> the<00:40:22.810> vdf<00:40:23.140> output 00:40:23.610 --> 00:40:23.620 align:start position:0% di function and by using the vdf output 00:40:23.620 --> 00:40:28.140 align:start position:0% di function and by using the vdf output on<00:40:23.830> run<00:40:24.040> now<00:40:25.380> VD<00:40:26.380> f<00:40:26.500> sorry<00:40:27.130> the<00:40:27.250> vdf<00:40:27.580> on<00:40:27.790> run<00:40:27.970> now 00:40:28.140 --> 00:40:28.150 align:start position:0% on run now VD f sorry the vdf on run now 00:40:28.150 --> 00:40:30.960 align:start position:0% on run now VD f sorry the vdf on run now so<00:40:28.750> using<00:40:29.260> the<00:40:29.410> ran<00:40:29.860> Arad<00:40:30.160> as<00:40:30.310> input<00:40:30.700> for<00:40:30.850> the 00:40:30.960 --> 00:40:30.970 align:start position:0% so using the ran Arad as input for the 00:40:30.970 --> 00:40:33.990 align:start position:0% so using the ran Arad as input for the PDF<00:40:31.270> the<00:40:31.540> last<00:40:32.290> revealer<00:40:32.850> loses<00:40:33.850> the 00:40:33.990 --> 00:40:34.000 align:start position:0% PDF the last revealer loses the 00:40:34.000 --> 00:40:36.150 align:start position:0% PDF the last revealer loses the advantage<00:40:34.450> and<00:40:34.720> the<00:40:34.780> way<00:40:35.110> that<00:40:35.380> works<00:40:35.620> can<00:40:36.040> be 00:40:36.150 --> 00:40:36.160 align:start position:0% advantage and the way that works can be 00:40:36.160 --> 00:40:37.470 align:start position:0% advantage and the way that works can be Illustrated<00:40:36.580> here<00:40:36.730> so<00:40:36.940> basically<00:40:37.300> what 00:40:37.470 --> 00:40:37.480 align:start position:0% Illustrated here so basically what 00:40:37.480 --> 00:40:39.840 align:start position:0% Illustrated here so basically what happens<00:40:37.810> is<00:40:38.020> you<00:40:38.080> have<00:40:38.260> this<00:40:38.590> last<00:40:39.250> block<00:40:39.640> of 00:40:39.840 --> 00:40:39.850 align:start position:0% happens is you have this last block of 00:40:39.850 --> 00:40:42.950 align:start position:0% happens is you have this last block of an<00:40:40.000> epoch<00:40:40.150> that<00:40:40.660> starts<00:40:41.560> the<00:40:41.710> vdf<00:40:42.010> computation 00:40:42.950 --> 00:40:42.960 align:start position:0% an epoch that starts the vdf computation 00:40:42.960 --> 00:40:48.060 align:start position:0% an epoch that starts the vdf computation and<00:40:43.960> so<00:40:45.390> later<00:40:46.390> the<00:40:47.050> vdf<00:40:47.380> computation<00:40:47.980> will 00:40:48.060 --> 00:40:48.070 align:start position:0% and so later the vdf computation will 00:40:48.070 --> 00:40:51.420 align:start position:0% and so later the vdf computation will have<00:40:48.250> an<00:40:48.340> output<00:40:48.460> and<00:40:49.380> that<00:40:50.380> will<00:40:50.530> be<00:40:50.650> used<00:40:50.860> as 00:40:51.420 --> 00:40:51.430 align:start position:0% have an output and that will be used as 00:40:51.430 --> 00:40:54.150 align:start position:0% have an output and that will be used as randomness<00:40:52.180> on<00:40:52.360> chain<00:40:52.650> but<00:40:53.650> by<00:40:53.890> that<00:40:54.100> time 00:40:54.150 --> 00:40:54.160 align:start position:0% randomness on chain but by that time 00:40:54.160 --> 00:40:57.540 align:start position:0% randomness on chain but by that time they<00:40:54.970> will<00:40:55.150> already<00:40:55.300> be<00:40:55.740> many<00:40:56.740> more<00:40:56.980> blocks<00:40:57.220> so 00:40:57.540 --> 00:40:57.550 align:start position:0% they will already be many more blocks so 00:40:57.550 --> 00:40:58.060 align:start position:0% they will already be many more blocks so it 00:40:58.060 --> 00:40:58.070 align:start position:0% it 00:40:58.070 --> 00:41:01.900 align:start position:0% it the<00:40:59.320> there<00:41:00.320> the<00:41:00.800> last<00:41:01.040> reveal<00:41:01.490> I<00:41:01.520> wouldn't 00:41:01.900 --> 00:41:01.910 align:start position:0% the there the last reveal I wouldn't 00:41:01.910 --> 00:41:04.810 align:start position:0% the there the last reveal I wouldn't have<00:41:02.030> a<00:41:02.060> chance<00:41:02.360> to<00:41:02.660> know<00:41:02.870> what<00:41:03.580> how<00:41:04.580> they 00:41:04.810 --> 00:41:04.820 align:start position:0% have a chance to know what how they 00:41:04.820 --> 00:41:06.940 align:start position:0% have a chance to know what how they could<00:41:05.030> have<00:41:05.120> influenced<00:41:05.840> by<00:41:06.140> not<00:41:06.410> not 00:41:06.940 --> 00:41:06.950 align:start position:0% could have influenced by not not 00:41:06.950 --> 00:41:12.310 align:start position:0% could have influenced by not not revealing<00:41:07.310> their<00:41:07.780> reveal<00:41:10.240> yeah<00:41:11.240> that's<00:41:11.990> it 00:41:12.310 --> 00:41:12.320 align:start position:0% revealing their reveal yeah that's it 00:41:12.320 --> 00:41:31.330 align:start position:0% revealing their reveal yeah that's it thank<00:41:12.590> you<00:41:27.340> so<00:41:28.340> a<00:41:28.370> stock<00:41:29.030> is<00:41:29.240> a<00:41:29.680> POS<00:41:30.680> signature 00:41:31.330 --> 00:41:31.340 align:start position:0% thank you so a stock is a POS signature 00:41:31.340 --> 00:41:36.400 align:start position:0% thank you so a stock is a POS signature aggregation<00:41:33.310> so<00:41:34.310> the<00:41:34.430> goal<00:41:34.670> is<00:41:34.880> to<00:41:35.350> provide<00:41:36.350> a 00:41:36.400 --> 00:41:36.410 align:start position:0% aggregation so the goal is to provide a 00:41:36.410 --> 00:41:40.750 align:start position:0% aggregation so the goal is to provide a minimal<00:41:36.950> set<00:41:37.190> of<00:41:37.400> knowledge<00:41:37.670> that<00:41:39.130> that<00:41:40.130> make 00:41:40.750 --> 00:41:40.760 align:start position:0% minimal set of knowledge that that make 00:41:40.760 --> 00:41:44.890 align:start position:0% minimal set of knowledge that that make developers<00:41:41.120> life<00:41:41.690> easier<00:41:42.590> so<00:41:43.480> the<00:41:44.480> goal<00:41:44.660> is<00:41:44.870> to 00:41:44.890 --> 00:41:44.900 align:start position:0% developers life easier so the goal is to 00:41:44.900 --> 00:41:47.380 align:start position:0% developers life easier so the goal is to introduce<00:41:45.350> the<00:41:45.800> signature<00:41:46.460> scheme<00:41:46.850> on<00:41:47.030> a<00:41:47.060> top 00:41:47.380 --> 00:41:47.390 align:start position:0% introduce the signature scheme on a top 00:41:47.390 --> 00:41:51.280 align:start position:0% introduce the signature scheme on a top but<00:41:47.960> that<00:41:48.490> it<00:41:49.490> is<00:41:49.670> built<00:41:49.970> on<00:41:50.240> the<00:41:50.570> pairing 00:41:51.280 --> 00:41:51.290 align:start position:0% but that it is built on the pairing 00:41:51.290 --> 00:41:55.140 align:start position:0% but that it is built on the pairing operations<00:41:52.010> and<00:41:52.340> curved<00:41:53.000> horns<00:41:53.240> groups<00:41:53.810> and 00:41:55.140 --> 00:41:55.150 align:start position:0% operations and curved horns groups and 00:41:55.150 --> 00:42:00.960 align:start position:0% operations and curved horns groups and they<00:41:56.150> all<00:41:56.300> built<00:41:56.690> under<00:41:57.170> of<00:41:57.640> field<00:41:58.640> operations 00:42:00.960 --> 00:42:00.970 align:start position:0% they all built under of field operations 00:42:00.970 --> 00:42:10.930 align:start position:0% they all built under of field operations button<00:42:01.970> so<00:42:05.740> yeah<00:42:06.770> so<00:42:07.370> a<00:42:08.770> takeaway<00:42:09.770> here<00:42:10.580> is 00:42:10.930 --> 00:42:10.940 align:start position:0% button so yeah so a takeaway here is 00:42:10.940 --> 00:42:14.170 align:start position:0% button so yeah so a takeaway here is that<00:42:11.320> when<00:42:12.320> we<00:42:12.350> say<00:42:12.590> BOS<00:42:13.010> we<00:42:13.250> might<00:42:13.670> talk<00:42:14.120> about 00:42:14.170 --> 00:42:14.180 align:start position:0% that when we say BOS we might talk about 00:42:14.180 --> 00:42:16.930 align:start position:0% that when we say BOS we might talk about two<00:42:14.510> things<00:42:14.540> the<00:42:15.350> one<00:42:15.590> is<00:42:15.830> the<00:42:16.070> BOS<00:42:16.460> signature 00:42:16.930 --> 00:42:16.940 align:start position:0% two things the one is the BOS signature 00:42:16.940 --> 00:42:19.600 align:start position:0% two things the one is the BOS signature aggregation<00:42:17.480> scheme<00:42:17.780> and<00:42:18.020> the<00:42:18.770> other<00:42:18.920> is<00:42:19.280> the 00:42:19.600 --> 00:42:19.610 align:start position:0% aggregation scheme and the other is the 00:42:19.610 --> 00:42:23.800 align:start position:0% aggregation scheme and the other is the curve<00:42:20.530> parameter<00:42:21.530> that<00:42:21.860> of<00:42:22.120> chosen<00:42:23.120> by<00:42:23.270> z 00:42:23.800 --> 00:42:23.810 align:start position:0% curve parameter that of chosen by z 00:42:23.810 --> 00:42:25.690 align:start position:0% curve parameter that of chosen by z cache<00:42:24.080> is<00:42:24.410> called<00:42:24.800> BOS<00:42:25.220> 12 00:42:25.690 --> 00:42:25.700 align:start position:0% cache is called BOS 12 00:42:25.700 --> 00:42:32.070 align:start position:0% cache is called BOS 12 3:81<00:42:26.510> curve<00:42:26.780> there<00:42:27.650> are<00:42:27.740> different<00:42:28.160> authors 00:42:32.070 --> 00:42:32.080 align:start position:0% 00:42:32.080 --> 00:42:35.890 align:start position:0% so<00:42:33.080> first<00:42:33.350> I'll<00:42:33.530> give<00:42:33.830> a<00:42:33.860> primary<00:42:34.760> how<00:42:34.910> a<00:42:35.270> queue 00:42:35.890 --> 00:42:35.900 align:start position:0% so first I'll give a primary how a queue 00:42:35.900 --> 00:42:41.620 align:start position:0% so first I'll give a primary how a queue operation<00:42:36.620> works<00:42:38.020> so<00:42:39.460> you<00:42:40.460> have<00:42:40.640> a<00:42:40.670> feel 00:42:41.620 --> 00:42:41.630 align:start position:0% operation works so you have a feel 00:42:41.630 --> 00:42:46.380 align:start position:0% operation works so you have a feel number<00:42:42.080> like<00:42:42.460> fill<00:42:43.460> 13<00:42:44.030> that<00:42:44.390> means<00:42:44.650> it<00:42:45.650> is 00:42:46.380 --> 00:42:46.390 align:start position:0% number like fill 13 that means it is 00:42:46.390 --> 00:42:50.440 align:start position:0% number like fill 13 that means it is operator<00:42:47.680> operator<00:42:48.680> on<00:42:48.830> the<00:42:49.120> prime<00:42:50.120> prime 00:42:50.440 --> 00:42:50.450 align:start position:0% operator operator on the prime prime 00:42:50.450 --> 00:42:54.460 align:start position:0% operator operator on the prime prime number<00:42:50.720> 13<00:42:51.400> and<00:42:52.400> then<00:42:52.900> you<00:42:53.900> can<00:42:54.110> define 00:42:54.460 --> 00:42:54.470 align:start position:0% number 13 and then you can define 00:42:54.470 --> 00:42:57.250 align:start position:0% number 13 and then you can define addition<00:42:55.400> subtraction<00:42:56.180> multiplication<00:42:56.260> and 00:42:57.250 --> 00:42:57.260 align:start position:0% addition subtraction multiplication and 00:42:57.260 --> 00:43:03.130 align:start position:0% addition subtraction multiplication and division<00:42:58.840> with<00:42:59.840> this<00:43:00.110> number<00:43:00.700> and<00:43:02.110> note<00:43:03.110> that 00:43:03.130 --> 00:43:03.140 align:start position:0% division with this number and note that 00:43:03.140 --> 00:43:08.290 align:start position:0% division with this number and note that the<00:43:03.620> outputs<00:43:04.280> are<00:43:05.240> always<00:43:05.660> between<00:43:06.230> 0<00:43:06.710> and<00:43:07.300> Q 00:43:08.290 --> 00:43:08.300 align:start position:0% the outputs are always between 0 and Q 00:43:08.300 --> 00:43:10.360 align:start position:0% the outputs are always between 0 and Q minus<00:43:08.750> 1<00:43:08.780> so 00:43:10.360 --> 00:43:10.370 align:start position:0% minus 1 so 00:43:10.370 --> 00:43:13.410 align:start position:0% minus 1 so you<00:43:10.610> have<00:43:10.880> a<00:43:10.910> no<00:43:11.900> matter<00:43:12.080> how<00:43:12.260> complex 00:43:13.410 --> 00:43:13.420 align:start position:0% you have a no matter how complex 00:43:13.420 --> 00:43:18.630 align:start position:0% you have a no matter how complex commutation<00:43:14.420> you<00:43:14.600> if<00:43:15.020> none<00:43:15.350> on<00:43:16.000> @q<00:43:17.000> you<00:43:17.750> always 00:43:18.630 --> 00:43:18.640 align:start position:0% commutation you if none on @q you always 00:43:18.640 --> 00:43:22.480 align:start position:0% commutation you if none on @q you always get<00:43:19.640> the<00:43:19.760> same<00:43:19.940> data<00:43:20.180> size<00:43:20.920> and<00:43:21.920> you<00:43:22.100> can<00:43:22.160> use 00:43:22.480 --> 00:43:22.490 align:start position:0% get the same data size and you can use 00:43:22.490 --> 00:43:27.250 align:start position:0% get the same data size and you can use the<00:43:22.760> py<00:43:23.450> ECC<00:43:23.930> library<00:43:24.380> to<00:43:25.300> to<00:43:26.300> try<00:43:26.600> try<00:43:27.080> on 00:43:27.250 --> 00:43:27.260 align:start position:0% the py ECC library to to try try on 00:43:27.260 --> 00:43:35.080 align:start position:0% the py ECC library to to try try on different<00:43:27.830> of<00:43:28.400> primer<00:43:29.150> fields<00:43:33.010> and<00:43:34.090> here's 00:43:35.080 --> 00:43:35.090 align:start position:0% different of primer fields and here's 00:43:35.090 --> 00:43:37.870 align:start position:0% different of primer fields and here's another<00:43:35.300> primer<00:43:35.810> on<00:43:36.110> elliptic<00:43:36.740> curves<00:43:37.190> you 00:43:37.870 --> 00:43:37.880 align:start position:0% another primer on elliptic curves you 00:43:37.880 --> 00:43:41.170 align:start position:0% another primer on elliptic curves you when<00:43:38.660> we<00:43:38.780> say<00:43:38.990> elliptic<00:43:39.590> curves<00:43:39.890> it's<00:43:40.250> a<00:43:40.460> it's 00:43:41.170 --> 00:43:41.180 align:start position:0% when we say elliptic curves it's a it's 00:43:41.180 --> 00:43:45.670 align:start position:0% when we say elliptic curves it's a it's an<00:43:41.330> equation<00:43:41.750> in<00:43:42.200> this<00:43:42.830> form<00:43:43.210> is<00:43:44.290> it's<00:43:45.290> a<00:43:45.440> Y 00:43:45.670 --> 00:43:45.680 align:start position:0% an equation in this form is it's a Y 00:43:45.680 --> 00:43:50.110 align:start position:0% an equation in this form is it's a Y Square<00:43:46.160> and<00:43:46.430> X<00:43:46.700> cubic<00:43:47.300> and<00:43:48.580> when<00:43:49.580> you<00:43:49.700> define 00:43:50.110 --> 00:43:50.120 align:start position:0% Square and X cubic and when you define 00:43:50.120 --> 00:43:53.440 align:start position:0% Square and X cubic and when you define it<00:43:50.360> on<00:43:50.540> a<00:43:50.870> real<00:43:51.230> number<00:43:51.680> when<00:43:52.250> X<00:43:52.550> Y<00:43:52.850> is<00:43:52.910> a<00:43:53.150> real 00:43:53.440 --> 00:43:53.450 align:start position:0% it on a real number when X Y is a real 00:43:53.450 --> 00:43:57.040 align:start position:0% it on a real number when X Y is a real number<00:43:53.840> you<00:43:54.050> see<00:43:54.530> a<00:43:54.880> curved<00:43:55.880> shape<00:43:55.940> but<00:43:56.810> if<00:43:56.930> you 00:43:57.040 --> 00:43:57.050 align:start position:0% number you see a curved shape but if you 00:43:57.050 --> 00:43:59.160 align:start position:0% number you see a curved shape but if you defined<00:43:57.560> on<00:43:57.770> a<00:43:57.800> finite<00:43:57.920> field 00:43:59.160 --> 00:43:59.170 align:start position:0% defined on a finite field 00:43:59.170 --> 00:44:04.720 align:start position:0% defined on a finite field it<00:44:00.170> looks<00:44:00.680> like<00:44:00.890> scattered<00:44:01.310> and<00:44:02.950> so<00:44:03.950> a<00:44:04.370> point 00:44:04.720 --> 00:44:04.730 align:start position:0% it looks like scattered and so a point 00:44:04.730 --> 00:44:08.050 align:start position:0% it looks like scattered and so a point on<00:44:05.000> the<00:44:05.120> curve<00:44:05.360> is<00:44:05.890> has<00:44:06.890> a<00:44:06.920> x<00:44:07.610> and<00:44:07.910> y 00:44:08.050 --> 00:44:08.060 align:start position:0% on the curve is has a x and y 00:44:08.060 --> 00:44:11.380 align:start position:0% on the curve is has a x and y coordinates<00:44:08.720> and<00:44:09.610> usually<00:44:10.610> you<00:44:10.700> need<00:44:10.880> to<00:44:11.030> send 00:44:11.380 --> 00:44:11.390 align:start position:0% coordinates and usually you need to send 00:44:11.390 --> 00:44:15.220 align:start position:0% coordinates and usually you need to send the<00:44:11.600> points<00:44:12.140> over<00:44:12.740> the<00:44:12.860> network<00:44:13.660> so<00:44:14.660> you<00:44:14.990> can 00:44:15.220 --> 00:44:15.230 align:start position:0% the points over the network so you can 00:44:15.230 --> 00:44:18.910 align:start position:0% the points over the network so you can compress<00:44:15.620> it<00:44:15.980> by<00:44:16.160> only<00:44:16.430> specify<00:44:17.090> X<00:44:17.450> and<00:44:17.920> only 00:44:18.910 --> 00:44:18.920 align:start position:0% compress it by only specify X and only 00:44:18.920 --> 00:44:22.840 align:start position:0% compress it by only specify X and only one<00:44:19.100> pitch<00:44:19.370> to<00:44:19.400> him<00:44:19.880> for<00:44:20.120> which<00:44:20.660> Y<00:44:21.730> you<00:44:22.730> are 00:44:22.840 --> 00:44:22.850 align:start position:0% one pitch to him for which Y you are 00:44:22.850 --> 00:44:26.160 align:start position:0% one pitch to him for which Y you are talking<00:44:23.150> about<00:44:23.390> because<00:44:24.010> given<00:44:25.010> X<00:44:25.280> the<00:44:25.520> Y<00:44:25.730> is 00:44:26.160 --> 00:44:26.170 align:start position:0% talking about because given X the Y is 00:44:26.170 --> 00:44:29.800 align:start position:0% talking about because given X the Y is symmetric<00:44:27.170> it's<00:44:27.470> it's<00:44:27.740> only<00:44:28.160> two<00:44:28.940> points<00:44:29.660> on 00:44:29.800 --> 00:44:29.810 align:start position:0% symmetric it's it's only two points on 00:44:29.810 --> 00:44:35.200 align:start position:0% symmetric it's it's only two points on our<00:44:30.710> graph<00:44:31.280> so<00:44:32.200> and<00:44:33.200> you<00:44:33.470> can<00:44:33.770> you<00:44:34.040> can<00:44:34.280> add<00:44:35.150> a 00:44:35.200 --> 00:44:35.210 align:start position:0% our graph so and you can you can add a 00:44:35.210 --> 00:44:38.950 align:start position:0% our graph so and you can you can add a point<00:44:35.750> to<00:44:36.020> another<00:44:36.410> point<00:44:36.620> so<00:44:37.550> you<00:44:38.480> can<00:44:38.660> define 00:44:38.950 --> 00:44:38.960 align:start position:0% point to another point so you can define 00:44:38.960 --> 00:44:43.300 align:start position:0% point to another point so you can define additions<00:44:39.700> of<00:44:40.700> the<00:44:41.210> points<00:44:41.930> on<00:44:42.050> the<00:44:42.200> curve<00:44:42.440> and 00:44:43.300 --> 00:44:43.310 align:start position:0% additions of the points on the curve and 00:44:43.310 --> 00:44:46.660 align:start position:0% additions of the points on the curve and it<00:44:43.550> is<00:44:43.970> usually<00:44:44.630> on<00:44:44.900> line<00:44:45.380> when<00:44:46.280> you<00:44:46.400> want<00:44:46.610> to 00:44:46.660 --> 00:44:46.670 align:start position:0% it is usually on line when you want to 00:44:46.670 --> 00:44:51.960 align:start position:0% it is usually on line when you want to add<00:44:46.820> P<00:44:47.240> to<00:44:47.540> Q<00:44:47.570> you<00:44:48.850> draw<00:44:49.850> a<00:44:49.880> straight<00:44:50.090> line<00:44:50.540> and 00:44:51.960 --> 00:44:51.970 align:start position:0% add P to Q you draw a straight line and 00:44:51.970 --> 00:44:54.580 align:start position:0% add P to Q you draw a straight line and intersect<00:44:52.970> the<00:44:53.120> curve<00:44:53.360> on<00:44:53.630> another<00:44:53.960> point<00:44:54.290> and 00:44:54.580 --> 00:44:54.590 align:start position:0% intersect the curve on another point and 00:44:54.590 --> 00:44:57.400 align:start position:0% intersect the curve on another point and then<00:44:55.070> mirrored<00:44:55.700> it<00:44:55.880> down<00:44:56.090> to<00:44:56.450> find<00:44:56.780> a<00:44:56.900> peep<00:44:57.140> ask 00:44:57.400 --> 00:44:57.410 align:start position:0% then mirrored it down to find a peep ask 00:44:57.410 --> 00:45:01.360 align:start position:0% then mirrored it down to find a peep ask you<00:44:57.680> so<00:44:58.430> when<00:44:59.210> we<00:44:59.330> have<00:44:59.540> the<00:44:59.690> addition<00:45:00.200> of<00:45:00.370> the 00:45:01.360 --> 00:45:01.370 align:start position:0% you so when we have the addition of the 00:45:01.370 --> 00:45:05.800 align:start position:0% you so when we have the addition of the point<00:45:01.640> you<00:45:02.390> can<00:45:02.690> define<00:45:03.440> multiplication<00:45:04.810> for 00:45:05.800 --> 00:45:05.810 align:start position:0% point you can define multiplication for 00:45:05.810 --> 00:45:08.860 align:start position:0% point you can define multiplication for a<00:45:05.840> point<00:45:06.140> you<00:45:07.100> can<00:45:07.310> multiply<00:45:07.730> a<00:45:07.970> point<00:45:08.330> like<00:45:08.660> by 00:45:08.860 --> 00:45:08.870 align:start position:0% a point you can multiply a point like by 00:45:08.870 --> 00:45:12.240 align:start position:0% a point you can multiply a point like by ten<00:45:09.260> times<00:45:09.590> like<00:45:09.980> adding<00:45:10.700> your<00:45:10.820> 10<00:45:11.090> times<00:45:11.360> and 00:45:12.240 --> 00:45:12.250 align:start position:0% ten times like adding your 10 times and 00:45:12.250 --> 00:45:16.420 align:start position:0% ten times like adding your 10 times and this<00:45:13.250> is<00:45:13.550> this<00:45:14.210> is<00:45:14.420> a<00:45:14.450> hard<00:45:15.350> math<00:45:15.620> problem<00:45:16.190> that 00:45:16.420 --> 00:45:16.430 align:start position:0% this is this is a hard math problem that 00:45:16.430 --> 00:45:21.049 align:start position:0% this is this is a hard math problem that you<00:45:16.640> can<00:45:17.290> given<00:45:18.290> you<00:45:18.650> have<00:45:18.920> P<00:45:19.640> and<00:45:19.820> Q<00:45:20.210> and 00:45:21.049 --> 00:45:21.059 align:start position:0% you can given you have P and Q and 00:45:21.059 --> 00:45:24.380 align:start position:0% you can given you have P and Q and you<00:45:21.209> cannot<00:45:21.449> find<00:45:21.839> 10<00:45:22.529> easy<00:45:23.249> it's<00:45:23.789> really<00:45:24.150> hard 00:45:24.380 --> 00:45:24.390 align:start position:0% you cannot find 10 easy it's really hard 00:45:24.390 --> 00:45:29.749 align:start position:0% you cannot find 10 easy it's really hard so<00:45:24.689> you<00:45:24.809> can<00:45:25.019> hide<00:45:25.259> bodies<00:45:25.589> in<00:45:26.039> here<00:45:28.759> it's 00:45:29.749 --> 00:45:29.759 align:start position:0% so you can hide bodies in here it's 00:45:29.759 --> 00:45:31.399 align:start position:0% so you can hide bodies in here it's actually<00:45:29.880> a<00:45:30.089> secret<00:45:30.599> key<00:45:30.809> yeah 00:45:31.399 --> 00:45:31.409 align:start position:0% actually a secret key yeah 00:45:31.409 --> 00:45:38.359 align:start position:0% actually a secret key yeah and<00:45:32.659> so<00:45:34.189> here<00:45:35.189> let's<00:45:36.119> talk<00:45:36.359> about<00:45:36.449> the<00:45:36.779> PRS<00:45:37.619> 12 00:45:38.359 --> 00:45:38.369 align:start position:0% and so here let's talk about the PRS 12 00:45:38.369 --> 00:45:45.499 align:start position:0% and so here let's talk about the PRS 12 381<00:45:40.130> specifications<00:45:42.380> it<00:45:43.380> has<00:45:43.589> a<00:45:43.849> small<00:45:44.849> small 00:45:45.499 --> 00:45:45.509 align:start position:0% 381 specifications it has a small small 00:45:45.509 --> 00:45:48.829 align:start position:0% 381 specifications it has a small small point<00:45:45.809> called<00:45:46.529> g1<00:45:46.979> and<00:45:47.279> a<00:45:47.939> big<00:45:48.209> point<00:45:48.479> called 00:45:48.829 --> 00:45:48.839 align:start position:0% point called g1 and a big point called 00:45:48.839 --> 00:45:53.019 align:start position:0% point called g1 and a big point called g2<00:45:49.669> if<00:45:50.669> we<00:45:50.880> remember<00:45:51.449> the<00:45:51.599> first<00:45:51.900> pyramid<00:45:52.559> is 00:45:53.019 --> 00:45:53.029 align:start position:0% g2 if we remember the first pyramid is 00:45:53.029 --> 00:45:57.199 align:start position:0% g2 if we remember the first pyramid is they<00:45:54.029> have<00:45:54.479> different<00:45:55.140> finite<00:45:55.919> prime<00:45:56.789> fields 00:45:57.199 --> 00:45:57.209 align:start position:0% they have different finite prime fields 00:45:57.209 --> 00:46:01.880 align:start position:0% they have different finite prime fields on<00:45:57.749> a<00:45:57.809> button<00:45:58.519> the<00:45:59.519> smoke<00:45:59.939> smoke<00:46:00.929> small<00:46:01.650> point 00:46:01.880 --> 00:46:01.890 align:start position:0% on a button the smoke smoke small point 00:46:01.890 --> 00:46:05.449 align:start position:0% on a button the smoke smoke small point has<00:46:02.159> 48<00:46:03.029> bytes<00:46:03.239> and<00:46:03.539> a<00:46:03.989> larger<00:46:04.319> one<00:46:04.439> has<00:46:04.679> 96 00:46:05.449 --> 00:46:05.459 align:start position:0% has 48 bytes and a larger one has 96 00:46:05.459 --> 00:46:10.159 align:start position:0% has 48 bytes and a larger one has 96 bytes<00:46:05.939> and<00:46:07.099> they<00:46:08.099> have<00:46:08.309> different<00:46:09.169> elliptic 00:46:10.159 --> 00:46:10.169 align:start position:0% bytes and they have different elliptic 00:46:10.169 --> 00:46:17.019 align:start position:0% bytes and they have different elliptic curve<00:46:12.289> defined<00:46:13.289> and<00:46:13.789> note<00:46:14.789> that 00:46:17.019 --> 00:46:17.029 align:start position:0% 00:46:17.029 --> 00:46:21.199 align:start position:0% so<00:46:18.029> the<00:46:18.390> fq2<00:46:18.839> is<00:46:19.199> like<00:46:20.069> a<00:46:20.099> complex<00:46:20.640> numbers 00:46:21.199 --> 00:46:21.209 align:start position:0% so the fq2 is like a complex numbers 00:46:21.209 --> 00:46:24.559 align:start position:0% so the fq2 is like a complex numbers it's<00:46:21.959> a<00:46:22.109> double<00:46:22.739> the<00:46:22.859> size<00:46:23.130> of<00:46:23.369> the<00:46:23.640> small 00:46:24.559 --> 00:46:24.569 align:start position:0% it's a double the size of the small 00:46:24.569 --> 00:46:27.890 align:start position:0% it's a double the size of the small curve<00:46:24.839> and<00:46:25.109> there's<00:46:25.739> a<00:46:25.829> image<00:46:26.309> in<00:46:26.900> imaginary 00:46:27.890 --> 00:46:27.900 align:start position:0% curve and there's a image in imaginary 00:46:27.900 --> 00:46:31.759 align:start position:0% curve and there's a image in imaginary number<00:46:28.650> I<00:46:28.890> there<00:46:29.249> and<00:46:29.569> the<00:46:30.569> G<00:46:30.839> 1<00:46:31.049> and<00:46:31.079> G<00:46:31.349> 2<00:46:31.529> is 00:46:31.759 --> 00:46:31.769 align:start position:0% number I there and the G 1 and G 2 is 00:46:31.769 --> 00:46:36.939 align:start position:0% number I there and the G 1 and G 2 is that<00:46:32.369> generator<00:46:33.229> points<00:46:34.229> that<00:46:35.659> has<00:46:36.659> a 00:46:36.939 --> 00:46:36.949 align:start position:0% that generator points that has a 00:46:36.949 --> 00:46:42.819 align:start position:0% that generator points that has a specific<00:46:37.949> x<00:46:38.669> and<00:46:39.059> y<00:46:39.719> coordinates<00:46:40.679> specified 00:46:42.819 --> 00:46:42.829 align:start position:0% specific x and y coordinates specified 00:46:42.829 --> 00:46:51.049 align:start position:0% specific x and y coordinates specified for<00:46:43.829> the<00:46:44.869> for<00:46:45.869> the<00:46:45.959> curve<00:46:46.199> and<00:46:47.479> so<00:46:48.859> I'm<00:46:50.059> colored 00:46:51.049 --> 00:46:51.059 align:start position:0% for the for the curve and so I'm colored 00:46:51.059 --> 00:46:55.699 align:start position:0% for the for the curve and so I'm colored whole<00:46:51.299> days<00:46:51.509> then<00:46:52.049> so<00:46:52.439> it<00:46:53.959> don't<00:46:54.959> don't<00:46:55.529> get 00:46:55.699 --> 00:46:55.709 align:start position:0% whole days then so it don't don't get 00:46:55.709 --> 00:47:02.359 align:start position:0% whole days then so it don't don't get lost<00:46:55.919> with<00:46:56.819> G<00:46:57.089> 1<00:46:57.239> and<00:46:57.269> G<00:46:57.479> 2<00:46:59.479> so<00:47:00.859> a<00:47:01.859> pairing 00:47:02.359 --> 00:47:02.369 align:start position:0% lost with G 1 and G 2 so a pairing 00:47:02.369 --> 00:47:04.069 align:start position:0% lost with G 1 and G 2 so a pairing function<00:47:02.789> pairing<00:47:03.209> function<00:47:03.630> is<00:47:03.809> a<00:47:03.839> function 00:47:04.069 --> 00:47:04.079 align:start position:0% function pairing function is a function 00:47:04.079 --> 00:47:09.219 align:start position:0% function pairing function is a function that<00:47:04.499> takes<00:47:05.069> a<00:47:05.789> g1<00:47:06.659> group<00:47:06.959> and<00:47:07.259> G<00:47:07.499> to<00:47:07.650> group<00:47:07.949> and 00:47:09.219 --> 00:47:09.229 align:start position:0% that takes a g1 group and G to group and 00:47:09.229 --> 00:47:12.529 align:start position:0% that takes a g1 group and G to group and the<00:47:10.229> magic<00:47:10.650> of<00:47:10.799> the<00:47:11.039> pairing<00:47:11.939> function<00:47:12.359> is 00:47:12.529 --> 00:47:12.539 align:start position:0% the magic of the pairing function is 00:47:12.539 --> 00:47:16.699 align:start position:0% the magic of the pairing function is that<00:47:13.369> when<00:47:14.369> you<00:47:14.519> like<00:47:14.989> multiplier<00:47:15.989> constant<00:47:16.619> a 00:47:16.699 --> 00:47:16.709 align:start position:0% that when you like multiplier constant a 00:47:16.709 --> 00:47:21.109 align:start position:0% that when you like multiplier constant a or<00:47:17.159> b<00:47:17.459> to<00:47:18.140> group<00:47:19.140> elements<00:47:19.799> and<00:47:19.979> you<00:47:20.640> can<00:47:20.849> tag 00:47:21.109 --> 00:47:21.119 align:start position:0% or b to group elements and you can tag 00:47:21.119 --> 00:47:23.419 align:start position:0% or b to group elements and you can tag the<00:47:21.269> IV<00:47:21.599> to<00:47:21.779> the<00:47:21.809> shoulders<00:47:22.469> and<00:47:22.769> that<00:47:23.189> means 00:47:23.419 --> 00:47:23.429 align:start position:0% the IV to the shoulders and that means 00:47:23.429 --> 00:47:28.819 align:start position:0% the IV to the shoulders and that means that<00:47:23.759> you<00:47:23.969> can<00:47:24.239> take<00:47:24.569> that<00:47:24.599> AV<00:47:25.469> into<00:47:27.199> the<00:47:28.199> first 00:47:28.819 --> 00:47:28.829 align:start position:0% that you can take that AV into the first 00:47:28.829 --> 00:47:32.059 align:start position:0% that you can take that AV into the first one<00:47:29.009> in<00:47:29.219> a<00:47:29.249> second<00:47:29.699> one<00:47:29.849> and<00:47:30.089> that's<00:47:31.079> rule 00:47:32.059 --> 00:47:32.069 align:start position:0% one in a second one and that's rule 00:47:32.069 --> 00:47:32.569 align:start position:0% one in a second one and that's rule number<00:47:32.099> one 00:47:32.569 --> 00:47:32.579 align:start position:0% number one 00:47:32.579 --> 00:47:34.650 align:start position:0% number one and<00:47:33.150> rule<00:47:33.419> number<00:47:33.449> two<00:47:33.809> is<00:47:33.839> that 00:47:34.650 --> 00:47:34.660 align:start position:0% and rule number two is that 00:47:34.660 --> 00:47:38.160 align:start position:0% and rule number two is that when<00:47:34.809> you<00:47:34.930> are<00:47:35.049> adding<00:47:35.410> points<00:47:36.480> now<00:47:37.480> you<00:47:37.539> are 00:47:38.160 --> 00:47:38.170 align:start position:0% when you are adding points now you are 00:47:38.170 --> 00:47:41.069 align:start position:0% when you are adding points now you are adding<00:47:38.319> points<00:47:38.680> in<00:47:38.950> g1<00:47:39.279> adding<00:47:40.119> points<00:47:40.329> in<00:47:40.599> g2 00:47:41.069 --> 00:47:41.079 align:start position:0% adding points in g1 adding points in g2 00:47:41.079 --> 00:47:44.339 align:start position:0% adding points in g1 adding points in g2 you<00:47:41.619> can<00:47:41.890> like<00:47:42.069> distribute<00:47:42.730> them<00:47:42.970> and<00:47:43.660> spread 00:47:44.339 --> 00:47:44.349 align:start position:0% you can like distribute them and spread 00:47:44.349 --> 00:47:49.650 align:start position:0% you can like distribute them and spread them<00:47:44.559> out<00:47:44.769> so<00:47:47.460> with<00:47:48.460> this<00:47:48.670> construction<00:47:49.240> we 00:47:49.650 --> 00:47:49.660 align:start position:0% them out so with this construction we 00:47:49.660 --> 00:47:52.799 align:start position:0% them out so with this construction we can<00:47:49.900> introduce<00:47:50.500> how<00:47:50.950> we<00:47:51.009> can<00:47:51.750> how<00:47:52.750> the 00:47:52.799 --> 00:47:52.809 align:start position:0% can introduce how we can how the 00:47:52.809 --> 00:47:57.900 align:start position:0% can introduce how we can how the signature<00:47:53.529> scheme<00:47:53.920> is<00:47:54.130> built<00:47:54.400> and<00:47:54.670> this<00:47:56.910> type 00:47:57.900 --> 00:47:57.910 align:start position:0% signature scheme is built and this type 00:47:57.910 --> 00:48:00.870 align:start position:0% signature scheme is built and this type of<00:47:57.940> construction<00:47:58.390> and<00:47:59.099> if<00:48:00.099> you<00:48:00.250> look<00:48:00.460> at<00:48:00.670> the 00:48:00.870 --> 00:48:00.880 align:start position:0% of construction and if you look at the 00:48:00.880 --> 00:48:03.900 align:start position:0% of construction and if you look at the pairing<00:48:01.450> function<00:48:01.950> there<00:48:02.950> are<00:48:03.069> some<00:48:03.279> monies 00:48:03.900 --> 00:48:03.910 align:start position:0% pairing function there are some monies 00:48:03.910 --> 00:48:08.329 align:start position:0% pairing function there are some monies over<00:48:04.210> there<00:48:04.480> because<00:48:04.839> it's<00:48:05.319> expensive<00:48:05.799> to<00:48:06.309> run 00:48:08.329 --> 00:48:08.339 align:start position:0% over there because it's expensive to run 00:48:08.339 --> 00:48:13.309 align:start position:0% over there because it's expensive to run so<00:48:09.720> it's<00:48:10.720> a<00:48:10.900> it's<00:48:11.829> a<00:48:11.950> computational<00:48:12.490> heavily 00:48:13.309 --> 00:48:13.319 align:start position:0% so it's a it's a computational heavily 00:48:13.319 --> 00:48:19.170 align:start position:0% so it's a it's a computational heavily functions<00:48:15.450> so<00:48:16.450> we<00:48:16.809> try<00:48:17.349> to<00:48:17.380> minimize<00:48:18.180> the 00:48:19.170 --> 00:48:19.180 align:start position:0% functions so we try to minimize the 00:48:19.180 --> 00:48:24.200 align:start position:0% functions so we try to minimize the times<00:48:19.450> you<00:48:19.779> try<00:48:20.230> to<00:48:20.339> run<00:48:21.339> pairings<00:48:22.559> so<00:48:23.559> here 00:48:24.200 --> 00:48:24.210 align:start position:0% times you try to run pairings so here 00:48:24.210 --> 00:48:28.370 align:start position:0% times you try to run pairings so here here<00:48:25.210> is<00:48:25.329> the<00:48:26.190> POS<00:48:27.190> a<00:48:27.460> signature<00:48:27.910> scheme 00:48:28.370 --> 00:48:28.380 align:start position:0% here is the POS a signature scheme 00:48:28.380 --> 00:48:31.470 align:start position:0% here is the POS a signature scheme private<00:48:29.380> key<00:48:29.529> is<00:48:29.799> an<00:48:30.069> integer<00:48:30.400> thinking<00:48:31.299> like 00:48:31.470 --> 00:48:31.480 align:start position:0% private key is an integer thinking like 00:48:31.480 --> 00:48:35.609 align:start position:0% private key is an integer thinking like 1<00:48:32.349> 2<00:48:32.500> 3<00:48:32.559> 4<00:48:32.769> 5<00:48:32.980> and<00:48:33.480> you<00:48:34.480> get<00:48:34.720> a<00:48:34.779> public<00:48:35.289> key<00:48:35.440> you 00:48:35.609 --> 00:48:35.619 align:start position:0% 1 2 3 4 5 and you get a public key you 00:48:35.619 --> 00:48:38.970 align:start position:0% 1 2 3 4 5 and you get a public key you just<00:48:35.890> multiply<00:48:36.190> the<00:48:36.549> private<00:48:37.180> key<00:48:37.299> with<00:48:37.950> G<00:48:38.950> 1 00:48:38.970 --> 00:48:38.980 align:start position:0% just multiply the private key with G 1 00:48:38.980 --> 00:48:44.089 align:start position:0% just multiply the private key with G 1 point<00:48:39.940> and<00:48:40.829> to<00:48:41.829> sign<00:48:42.190> a<00:48:42.220> message<00:48:42.849> you<00:48:43.450> need<00:48:43.690> to 00:48:44.089 --> 00:48:44.099 align:start position:0% point and to sign a message you need to 00:48:44.099 --> 00:48:47.910 align:start position:0% point and to sign a message you need to hatch<00:48:45.099> the<00:48:45.539> message<00:48:46.539> to<00:48:46.809> a<00:48:46.839> group<00:48:47.170> of<00:48:47.559> point 00:48:47.910 --> 00:48:47.920 align:start position:0% hatch the message to a group of point 00:48:47.920 --> 00:48:51.569 align:start position:0% hatch the message to a group of point and<00:48:48.279> that's<00:48:48.670> the<00:48:49.410> when<00:48:50.410> you<00:48:50.500> her<00:48:51.250> people 00:48:51.569 --> 00:48:51.579 align:start position:0% and that's the when you her people 00:48:51.579 --> 00:48:54.240 align:start position:0% and that's the when you her people saying<00:48:51.849> the<00:48:52.119> POS<00:48:52.859> standardization<00:48:53.859> effort 00:48:54.240 --> 00:48:54.250 align:start position:0% saying the POS standardization effort 00:48:54.250 --> 00:48:56.849 align:start position:0% saying the POS standardization effort they<00:48:54.460> are<00:48:54.539> standardized<00:48:55.539> the<00:48:55.750> way<00:48:55.960> we<00:48:56.289> hash 00:48:56.849 --> 00:48:56.859 align:start position:0% they are standardized the way we hash 00:48:56.859 --> 00:49:02.210 align:start position:0% they are standardized the way we hash the<00:48:56.890> message<00:48:57.819> to<00:48:58.049> two<00:48:59.049> points<00:48:59.559> and<00:48:59.740> then<00:49:00.309> you 00:49:02.210 --> 00:49:02.220 align:start position:0% the message to two points and then you 00:49:02.220 --> 00:49:06.660 align:start position:0% the message to two points and then you multiply<00:49:03.220> your<00:49:03.759> primary<00:49:04.480> key<00:49:04.660> to<00:49:04.839> a<00:49:05.670> message 00:49:06.660 --> 00:49:06.670 align:start position:0% multiply your primary key to a message 00:49:06.670 --> 00:49:09.660 align:start position:0% multiply your primary key to a message and<00:49:06.940> you<00:49:07.119> get<00:49:07.420> a<00:49:07.450> signature<00:49:08.049> here<00:49:08.500> and<00:49:08.710> to 00:49:09.660 --> 00:49:09.670 align:start position:0% and you get a signature here and to 00:49:09.670 --> 00:49:13.410 align:start position:0% and you get a signature here and to verify<00:49:10.470> the<00:49:11.470> signature<00:49:12.130> and<00:49:12.339> a<00:49:12.490> public<00:49:13.240> key 00:49:13.410 --> 00:49:13.420 align:start position:0% verify the signature and a public key 00:49:13.420 --> 00:49:15.539 align:start position:0% verify the signature and a public key and<00:49:13.450> message<00:49:14.019> you<00:49:14.559> are<00:49:14.920> used<00:49:15.250> to 00:49:15.539 --> 00:49:15.549 align:start position:0% and message you are used to 00:49:15.549 --> 00:49:18.660 align:start position:0% and message you are used to pairing<00:49:16.150> functions<00:49:17.009> and<00:49:18.009> the<00:49:18.190> proof<00:49:18.430> is 00:49:18.660 --> 00:49:18.670 align:start position:0% pairing functions and the proof is 00:49:18.670 --> 00:49:21.660 align:start position:0% pairing functions and the proof is really<00:49:19.029> simple<00:49:19.660> it's<00:49:20.230> like<00:49:20.529> you<00:49:20.710> write<00:49:21.009> a<00:49:21.039> G<00:49:21.460> 1 00:49:21.660 --> 00:49:21.670 align:start position:0% really simple it's like you write a G 1 00:49:21.670 --> 00:49:24.059 align:start position:0% really simple it's like you write a G 1 and<00:49:21.970> s<00:49:22.180> on<00:49:22.450> the<00:49:22.569> left-hand<00:49:22.960> side<00:49:23.049> and<00:49:23.500> then 00:49:24.059 --> 00:49:24.069 align:start position:0% and s on the left-hand side and then 00:49:24.069 --> 00:49:27.749 align:start position:0% and s on the left-hand side and then that<00:49:24.609> you<00:49:24.970> can<00:49:25.210> move<00:49:25.420> the<00:49:25.890> K<00:49:26.890> from<00:49:27.400> the<00:49:27.549> right 00:49:27.749 --> 00:49:27.759 align:start position:0% that you can move the K from the right 00:49:27.759 --> 00:49:29.999 align:start position:0% that you can move the K from the right to<00:49:27.940> the<00:49:28.059> left<00:49:28.240> and<00:49:28.539> you<00:49:28.960> get<00:49:29.170> the<00:49:29.349> expression 00:49:29.999 --> 00:49:30.009 align:start position:0% to the left and you get the expression 00:49:30.009 --> 00:49:34.200 align:start position:0% to the left and you get the expression of<00:49:30.160> the<00:49:30.309> right<00:49:30.519> hand<00:49:30.759> side<00:49:31.000> and<00:49:32.430> so<00:49:33.430> the<00:49:33.970> most 00:49:34.200 --> 00:49:34.210 align:start position:0% of the right hand side and so the most 00:49:34.210 --> 00:49:38.339 align:start position:0% of the right hand side and so the most powerful<00:49:36.329> thing<00:49:37.329> about<00:49:37.450> be<00:49:37.809> our<00:49:37.930> signature 00:49:38.339 --> 00:49:38.349 align:start position:0% powerful thing about be our signature 00:49:38.349 --> 00:49:42.240 align:start position:0% powerful thing about be our signature seen<00:49:38.859> is<00:49:39.130> it<00:49:39.369> can<00:49:40.140> aggregate<00:49:41.140> signatures<00:49:41.950> and 00:49:42.240 --> 00:49:42.250 align:start position:0% seen is it can aggregate signatures and 00:49:42.250 --> 00:49:46.620 align:start position:0% seen is it can aggregate signatures and public<00:49:42.700> keys<00:49:42.910> so<00:49:43.630> this<00:49:44.319> just<00:49:44.619> a<00:49:45.059> curve<00:49:46.059> point 00:49:46.620 --> 00:49:46.630 align:start position:0% public keys so this just a curve point 00:49:46.630 --> 00:49:48.480 align:start position:0% public keys so this just a curve point additions<00:49:47.140> which 00:49:48.480 --> 00:49:48.490 align:start position:0% additions which 00:49:48.490 --> 00:49:51.870 align:start position:0% additions which before<00:49:48.850> and<00:49:49.090> this<00:49:49.750> is<00:49:49.930> you<00:49:50.860> can<00:49:51.100> aggregate 00:49:51.870 --> 00:49:51.880 align:start position:0% before and this is you can aggregate 00:49:51.880 --> 00:49:55.980 align:start position:0% before and this is you can aggregate three<00:49:53.430> signatures<00:49:54.430> and<00:49:54.820> you<00:49:55.090> can<00:49:55.480> agree<00:49:55.840> get 00:49:55.980 --> 00:49:55.990 align:start position:0% three signatures and you can agree get 00:49:55.990 --> 00:50:00.240 align:start position:0% three signatures and you can agree get as<00:49:56.860> many<00:49:57.250> signatures<00:49:57.580> as<00:49:57.990> you<00:49:58.990> want<00:49:59.290> and<00:49:59.590> then 00:50:00.240 --> 00:50:00.250 align:start position:0% as many signatures as you want and then 00:50:00.250 --> 00:50:03.359 align:start position:0% as many signatures as you want and then verify<00:50:00.760> using<00:50:01.119> two<00:50:01.740> pairing<00:50:02.740> functions<00:50:03.160> to 00:50:03.359 --> 00:50:03.369 align:start position:0% verify using two pairing functions to 00:50:03.369 --> 00:50:09.590 align:start position:0% verify using two pairing functions to verify<00:50:04.380> so<00:50:05.380> yeah<00:50:06.369> so<00:50:06.700> the<00:50:07.150> proof<00:50:07.450> lived<00:50:08.320> as<00:50:08.560> a 00:50:09.590 --> 00:50:09.600 align:start position:0% verify so yeah so the proof lived as a 00:50:09.600 --> 00:50:15.480 align:start position:0% verify so yeah so the proof lived as a exercise<00:50:10.710> but<00:50:11.730> what<00:50:12.730> we<00:50:12.910> are<00:50:12.940> looking<00:50:14.280> so<00:50:15.280> what 00:50:15.480 --> 00:50:15.490 align:start position:0% exercise but what we are looking so what 00:50:15.490 --> 00:50:17.460 align:start position:0% exercise but what we are looking so what you<00:50:15.610> are<00:50:15.640> looking<00:50:15.850> at<00:50:16.150> here<00:50:16.450> you<00:50:17.020> are<00:50:17.140> looking 00:50:17.460 --> 00:50:17.470 align:start position:0% you are looking at here you are looking 00:50:17.470 --> 00:50:24.200 align:start position:0% you are looking at here you are looking at<00:50:17.590> a<00:50:17.850> scalability<00:50:18.900> so<00:50:19.900> this<00:50:21.690> this<00:50:22.690> this<00:50:23.050> is 00:50:24.200 --> 00:50:24.210 align:start position:0% at a scalability so this this this is 00:50:24.210 --> 00:50:29.730 align:start position:0% at a scalability so this this this is how<00:50:25.210> you<00:50:25.270> can<00:50:26.340> aggregate<00:50:27.340> many<00:50:28.740> validators 00:50:29.730 --> 00:50:29.740 align:start position:0% how you can aggregate many validators 00:50:29.740 --> 00:50:35.040 align:start position:0% how you can aggregate many validators messages<00:50:31.800> so<00:50:32.800> here<00:50:33.490> I<00:50:33.520> present<00:50:34.270> and<00:50:34.810> it 00:50:35.040 --> 00:50:35.050 align:start position:0% messages so here I present and it 00:50:35.050 --> 00:50:39.870 align:start position:0% messages so here I present and it samples<00:50:35.700> that<00:50:36.700> kind<00:50:37.540> of<00:50:37.600> power<00:50:37.840> on<00:50:38.350> the<00:50:38.880> chain 00:50:39.870 --> 00:50:39.880 align:start position:0% samples that kind of power on the chain 00:50:39.880 --> 00:50:44.210 align:start position:0% samples that kind of power on the chain saves<00:50:40.150> simple<00:50:41.080> C<00:50:41.260> or<00:50:41.410> istick<00:50:41.740> on<00:50:41.980> so<00:50:42.670> it<00:50:43.090> is<00:50:43.119> an 00:50:44.210 --> 00:50:44.220 align:start position:0% saves simple C or istick on so it is an 00:50:44.220 --> 00:50:48.140 align:start position:0% saves simple C or istick on so it is an attestation<00:50:45.480> message<00:50:46.480> and<00:50:46.780> it<00:50:47.560> has 00:50:48.140 --> 00:50:48.150 align:start position:0% attestation message and it has 00:50:48.150 --> 00:50:53.390 align:start position:0% attestation message and it has signatures<00:50:49.150> it<00:50:49.450> looks<00:50:49.630> like<00:50:49.869> this<00:50:50.140> and<00:50:50.500> then<00:50:51.430> I 00:50:53.390 --> 00:50:53.400 align:start position:0% signatures it looks like this and then I 00:50:53.400 --> 00:50:56.760 align:start position:0% signatures it looks like this and then I hide<00:50:54.400> data<00:50:55.060> part<00:50:55.540> and<00:50:55.810> you<00:50:56.260> will<00:50:56.410> see<00:50:56.619> an 00:50:56.760 --> 00:50:56.770 align:start position:0% hide data part and you will see an 00:50:56.770 --> 00:50:59.180 align:start position:0% hide data part and you will see an aggregation<00:50:57.280> page<00:50:57.760> looks<00:50:58.330> like<00:50:58.420> this<00:50:58.600> and 00:50:59.180 --> 00:50:59.190 align:start position:0% aggregation page looks like this and 00:50:59.190 --> 00:51:06.300 align:start position:0% aggregation page looks like this and this<00:51:00.190> is<00:51:00.430> actually<00:51:01.980> a<00:51:03.150> record<00:51:04.150> SS<00:51:04.780> or<00:51:05.310> varied 00:51:06.300 --> 00:51:06.310 align:start position:0% this is actually a record SS or varied 00:51:06.310 --> 00:51:10.190 align:start position:0% this is actually a record SS or varied 805<00:51:07.090> is<00:51:08.080> your<00:51:08.440> signature<00:51:08.859> included<00:51:09.580> in<00:51:09.760> this 00:51:10.190 --> 00:51:10.200 align:start position:0% 805 is your signature included in this 00:51:10.200 --> 00:51:13.680 align:start position:0% 805 is your signature included in this bunch<00:51:11.200> of<00:51:11.380> aggregation<00:51:12.100> and<00:51:12.310> then<00:51:13.060> a<00:51:13.359> kind 00:51:13.680 --> 00:51:13.690 align:start position:0% bunch of aggregation and then a kind 00:51:13.690 --> 00:51:16.320 align:start position:0% bunch of aggregation and then a kind used<00:51:14.350> that<00:51:14.560> information<00:51:14.800> to<00:51:15.340> look<00:51:15.670> up<00:51:15.850> public 00:51:16.320 --> 00:51:16.330 align:start position:0% used that information to look up public 00:51:16.330 --> 00:51:19.200 align:start position:0% used that information to look up public keys<00:51:16.540> and<00:51:16.900> to<00:51:17.109> verify<00:51:17.320> these<00:51:17.590> signatures<00:51:18.460> so 00:51:19.200 --> 00:51:19.210 align:start position:0% keys and to verify these signatures so 00:51:19.210 --> 00:51:23.430 align:start position:0% keys and to verify these signatures so yeah<00:51:19.900> this<00:51:20.490> how<00:51:21.490> tos<00:51:22.330> signatures<00:51:23.080> works 00:51:23.430 --> 00:51:23.440 align:start position:0% yeah this how tos signatures works 00:51:23.440 --> 00:51:27.390 align:start position:0% yeah this how tos signatures works hopefully<00:51:24.390> hopefully<00:51:25.390> that<00:51:26.050> helps<00:51:26.470> you<00:51:26.530> thank 00:51:27.390 --> 00:51:27.400 align:start position:0% hopefully hopefully that helps you thank 00:51:27.400 --> 00:51:35.249 align:start position:0% hopefully hopefully that helps you thank you<00:51:27.520> very<00:51:27.550> much 00:51:35.249 --> 00:51:35.259 align:start position:0% 00:51:35.259 --> 00:51:40.450 align:start position:0% thank<00:51:36.259> you<00:51:36.440> metallic<00:51:37.160> dr.<00:51:37.670> Chang<00:51:39.009> next<00:51:40.009> up<00:51:40.190> was 00:51:40.450 --> 00:51:40.460 align:start position:0% thank you metallic dr. Chang next up was 00:51:40.460 --> 00:51:44.140 align:start position:0% thank you metallic dr. Chang next up was a<00:51:41.619> break<00:51:42.619> but<00:51:42.890> we<00:51:43.460> don't<00:51:43.579> have<00:51:43.730> time<00:51:43.880> for<00:51:43.910> that 00:51:44.140 --> 00:51:44.150 align:start position:0% a break but we don't have time for that 00:51:44.150 --> 00:51:46.720 align:start position:0% a break but we don't have time for that because<00:51:44.269> we're<00:51:44.569> definitely<00:51:45.730> definitely 00:51:46.720 --> 00:51:46.730 align:start position:0% because we're definitely definitely 00:51:46.730 --> 00:51:48.489 align:start position:0% because we're definitely definitely running<00:51:47.150> late<00:51:47.420> already 00:51:48.489 --> 00:51:48.499 align:start position:0% running late already 00:51:48.499 --> 00:51:51.160 align:start position:0% running late already we<00:51:49.490> might<00:51:49.880> have<00:51:50.089> some<00:51:50.299> time<00:51:50.329> for<00:51:50.720> questions<00:51:50.809> at 00:51:51.160 --> 00:51:51.170 align:start position:0% we might have some time for questions at 00:51:51.170 --> 00:51:52.029 align:start position:0% we might have some time for questions at the<00:51:51.200> end<00:51:51.289> but<00:51:51.499> we're<00:51:51.710> just<00:51:51.740> gonna<00:51:51.890> keep 00:51:52.029 --> 00:51:52.039 align:start position:0% the end but we're just gonna keep 00:51:52.039 --> 00:51:53.319 align:start position:0% the end but we're just gonna keep driving 00:51:53.319 --> 00:51:53.329 align:start position:0% driving 00:51:53.329 --> 00:51:55.390 align:start position:0% driving next<00:51:54.019> up<00:51:54.200> shall<00:51:54.499> we<00:51:54.529> gonna<00:51:54.740> talk<00:51:54.920> about<00:51:54.980> we're 00:51:55.390 --> 00:51:55.400 align:start position:0% next up shall we gonna talk about we're 00:51:55.400 --> 00:51:57.759 align:start position:0% next up shall we gonna talk about we're moving<00:51:55.970> into<00:51:56.119> these<00:51:57.109> are<00:51:57.289> the<00:51:57.440> kind<00:51:57.589> of<00:51:57.619> some 00:51:57.759 --> 00:51:57.769 align:start position:0% moving into these are the kind of some 00:51:57.769 --> 00:51:58.870 align:start position:0% moving into these are the kind of some of<00:51:57.859> the<00:51:57.950> building<00:51:58.249> blocks<00:51:58.279> to<00:51:58.579> help<00:51:58.730> you 00:51:58.870 --> 00:51:58.880 align:start position:0% of the building blocks to help you 00:51:58.880 --> 00:52:00.430 align:start position:0% of the building blocks to help you understand<00:51:59.329> some<00:51:59.660> of<00:51:59.690> the<00:51:59.900> underlying 00:52:00.430 --> 00:52:00.440 align:start position:0% understand some of the underlying 00:52:00.440 --> 00:52:02.289 align:start position:0% understand some of the underlying concepts<00:52:01.009> that<00:52:01.190> we<00:52:01.309> use<00:52:01.519> to<00:52:01.759> construct<00:52:02.180> these 00:52:02.289 --> 00:52:02.299 align:start position:0% concepts that we use to construct these 00:52:02.299 --> 00:52:04.059 align:start position:0% concepts that we use to construct these things<00:52:02.539> and<00:52:02.779> now<00:52:03.109> we're<00:52:03.259> gonna<00:52:03.349> move<00:52:03.529> into<00:52:03.680> the 00:52:04.059 --> 00:52:04.069 align:start position:0% things and now we're gonna move into the 00:52:04.069 --> 00:52:06.190 align:start position:0% things and now we're gonna move into the more<00:52:04.519> concrete<00:52:04.849> and<00:52:05.210> San<00:52:05.359> Shi<00:52:05.539> ation<00:52:05.749> of<00:52:05.779> the 00:52:06.190 --> 00:52:06.200 align:start position:0% more concrete and San Shi ation of the 00:52:06.200 --> 00:52:07.620 align:start position:0% more concrete and San Shi ation of the protocol<00:52:06.589> shall<00:52:07.009> we 00:52:07.620 --> 00:52:07.630 align:start position:0% protocol shall we 00:52:07.630 --> 00:52:10.870 align:start position:0% protocol shall we so<00:52:08.630> hello<00:52:09.140> everyone<00:52:09.589> I'm<00:52:09.980> sorry<00:52:10.279> I'm<00:52:10.430> pretty 00:52:10.870 --> 00:52:10.880 align:start position:0% so hello everyone I'm sorry I'm pretty 00:52:10.880 --> 00:52:16.900 align:start position:0% so hello everyone I'm sorry I'm pretty sick<00:52:11.210> right<00:52:11.390> now<00:52:11.509> and<00:52:12.309> konichiwa<00:52:15.430> so<00:52:16.430> my<00:52:16.730> topic 00:52:16.900 --> 00:52:16.910 align:start position:0% sick right now and konichiwa so my topic 00:52:16.910 --> 00:52:20.349 align:start position:0% sick right now and konichiwa so my topic is<00:52:17.180> the<00:52:17.450> life<00:52:17.809> of<00:52:18.049> the<00:52:18.670> serum<00:52:19.670> the<00:52:19.999> concern 00:52:20.349 --> 00:52:20.359 align:start position:0% is the life of the serum the concern 00:52:20.359 --> 00:52:24.579 align:start position:0% is the life of the serum the concern validator<00:52:22.240> so<00:52:23.240> this<00:52:23.509> is<00:52:23.690> the<00:52:23.839> outline<00:52:24.170> of<00:52:24.200> this 00:52:24.579 --> 00:52:24.589 align:start position:0% validator so this is the outline of this 00:52:24.589 --> 00:52:27.849 align:start position:0% validator so this is the outline of this topic<00:52:25.130> so<00:52:25.910> we<00:52:26.059> were<00:52:26.150> talking<00:52:26.359> about<00:52:26.710> two<00:52:27.710> main 00:52:27.849 --> 00:52:27.859 align:start position:0% topic so we were talking about two main 00:52:27.859 --> 00:52:30.849 align:start position:0% topic so we were talking about two main factors<00:52:28.130> to<00:52:28.849> define<00:52:29.299> the<00:52:29.569> editor<00:52:30.140> state<00:52:30.529> and 00:52:30.849 --> 00:52:30.859 align:start position:0% factors to define the editor state and 00:52:30.859 --> 00:52:34.180 align:start position:0% factors to define the editor state and then<00:52:31.400> we<00:52:31.670> will<00:52:31.789> talk<00:52:31.970> about<00:52:32.119> the<00:52:32.990> entry<00:52:33.950> and 00:52:34.180 --> 00:52:34.190 align:start position:0% then we will talk about the entry and 00:52:34.190 --> 00:52:37.029 align:start position:0% then we will talk about the entry and exit<00:52:34.640> cues<00:52:35.239> and<00:52:35.660> then<00:52:36.289> the<00:52:36.440> life<00:52:36.559> cycle<00:52:36.980> of 00:52:37.029 --> 00:52:37.039 align:start position:0% exit cues and then the life cycle of 00:52:37.039 --> 00:52:45.249 align:start position:0% exit cues and then the life cycle of this<00:52:41.529> so<00:52:42.529> the<00:52:42.829> current<00:52:43.279> spec<00:52:44.059> defined<00:52:44.259> list 00:52:45.249 --> 00:52:45.259 align:start position:0% this so the current spec defined list 00:52:45.259 --> 00:52:49.979 align:start position:0% this so the current spec defined list for<00:52:45.759> status<00:52:46.789> there<00:52:47.539> are<00:52:48.549> activation 00:52:49.979 --> 00:52:49.989 align:start position:0% for status there are activation 00:52:49.989 --> 00:52:53.440 align:start position:0% for status there are activation eligibility<00:52:50.989> which<00:52:51.559> is<00:52:51.769> the<00:52:51.999> preparing<00:52:52.999> stage 00:52:53.440 --> 00:52:53.450 align:start position:0% eligibility which is the preparing stage 00:52:53.450 --> 00:52:57.309 align:start position:0% eligibility which is the preparing stage before<00:52:54.049> it<00:52:54.259> actually<00:52:54.529> be<00:52:55.009> activated<00:52:55.999> and<00:52:56.319> then 00:52:57.309 --> 00:52:57.319 align:start position:0% before it actually be activated and then 00:52:57.319 --> 00:52:59.829 align:start position:0% before it actually be activated and then the<00:52:57.859> second<00:52:58.130> one<00:52:58.220> is<00:52:58.369> to<00:52:58.400> it<00:52:58.700> the<00:52:59.299> state<00:52:59.660> that 00:52:59.829 --> 00:52:59.839 align:start position:0% the second one is to it the state that 00:52:59.839 --> 00:53:03.880 align:start position:0% the second one is to it the state that later<00:53:00.650> is<00:53:00.859> alive<00:53:01.190> active<00:53:01.880> and<00:53:02.150> is<00:53:02.599> helped<00:53:03.559> to 00:53:03.880 --> 00:53:03.890 align:start position:0% later is alive active and is helped to 00:53:03.890 --> 00:53:08.200 align:start position:0% later is alive active and is helped to validate<00:53:04.539> the<00:53:05.539> state<00:53:05.869> the<00:53:06.349> blockchain<00:53:07.210> and 00:53:08.200 --> 00:53:08.210 align:start position:0% validate the state the blockchain and 00:53:08.210 --> 00:53:11.970 align:start position:0% validate the state the blockchain and then<00:53:08.690> when<00:53:09.619> the<00:53:10.220> editor<00:53:10.549> they<00:53:11.089> can<00:53:11.299> choose<00:53:11.599> to 00:53:11.970 --> 00:53:11.980 align:start position:0% then when the editor they can choose to 00:53:11.980 --> 00:53:15.069 align:start position:0% then when the editor they can choose to accede<00:53:12.980> then<00:53:13.700> after<00:53:14.420> a<00:53:14.450> while<00:53:14.720> they<00:53:14.779> were 00:53:15.069 --> 00:53:15.079 align:start position:0% accede then after a while they were 00:53:15.079 --> 00:53:19.269 align:start position:0% accede then after a while they were getting<00:53:15.559> to<00:53:15.920> to<00:53:16.130> exceed<00:53:16.489> status<00:53:17.420> and<00:53:18.289> finally 00:53:19.269 --> 00:53:19.279 align:start position:0% getting to to exceed status and finally 00:53:19.279 --> 00:53:22.029 align:start position:0% getting to to exceed status and finally the<00:53:20.269> beacon<00:53:20.930> chamber<00:53:21.289> later<00:53:21.470> we're<00:53:21.680> getting 00:53:22.029 --> 00:53:22.039 align:start position:0% the beacon chamber later we're getting 00:53:22.039 --> 00:53:26.140 align:start position:0% the beacon chamber later we're getting to<00:53:22.249> to<00:53:22.519> withdraw<00:53:23.299> Ball<00:53:23.599> State<00:53:23.900> so<00:53:24.880> here<00:53:25.880> we 00:53:26.140 --> 00:53:26.150 align:start position:0% to to withdraw Ball State so here we 00:53:26.150 --> 00:53:29.289 align:start position:0% to to withdraw Ball State so here we need<00:53:26.329> to<00:53:26.480> know<00:53:26.809> is<00:53:27.200> that<00:53:27.819> in<00:53:28.819> the<00:53:28.880> big<00:53:29.089> engine 00:53:29.289 --> 00:53:29.299 align:start position:0% need to know is that in the big engine 00:53:29.299 --> 00:53:31.960 align:start position:0% need to know is that in the big engine phase<00:53:29.509> zero<00:53:29.809> we<00:53:30.529> only<00:53:30.680> have<00:53:30.950> with<00:53:31.430> drawable 00:53:31.960 --> 00:53:31.970 align:start position:0% phase zero we only have with drawable 00:53:31.970 --> 00:53:36.009 align:start position:0% phase zero we only have with drawable state<00:53:32.239> there's<00:53:33.579> the<00:53:34.579> actually<00:53:35.239> withdrawn 00:53:36.009 --> 00:53:36.019 align:start position:0% state there's the actually withdrawn 00:53:36.019 --> 00:53:39.370 align:start position:0% state there's the actually withdrawn state<00:53:36.829> will<00:53:37.220> be<00:53:37.549> introduced<00:53:38.390> in<00:53:38.660> the<00:53:38.989> Phase 00:53:39.370 --> 00:53:39.380 align:start position:0% state will be introduced in the Phase 00:53:39.380 --> 00:53:42.420 align:start position:0% state will be introduced in the Phase two<00:53:39.410> where<00:53:40.309> we<00:53:40.369> have<00:53:40.730> yeast<00:53:41.319> execution 00:53:42.420 --> 00:53:42.430 align:start position:0% two where we have yeast execution 00:53:42.430 --> 00:53:44.560 align:start position:0% two where we have yeast execution environments<00:53:43.430> then<00:53:43.970> that<00:53:44.150> Square 00:53:44.560 --> 00:53:44.570 align:start position:0% environments then that Square 00:53:44.570 --> 00:53:48.250 align:start position:0% environments then that Square the<00:53:44.810> litter<00:53:45.260> can<00:53:45.770> actually<00:53:46.840> withdraw<00:53:47.840> their 00:53:48.250 --> 00:53:48.260 align:start position:0% the litter can actually withdraw their 00:53:48.260 --> 00:53:57.120 align:start position:0% the litter can actually withdraw their deposit<00:53:49.250> to<00:53:49.910> the<00:53:49.940> e<00:53:50.180> to<00:53:51.820> distractions<00:53:53.380> okay<00:53:55.510> so 00:53:57.120 --> 00:53:57.130 align:start position:0% deposit to the e to distractions okay so 00:53:57.130 --> 00:54:01.270 align:start position:0% deposit to the e to distractions okay so here<00:53:58.130> is<00:53:58.400> the<00:53:59.020> validate<00:54:00.020> Hearst<00:54:00.280> data 00:54:01.270 --> 00:54:01.280 align:start position:0% here is the validate Hearst data 00:54:01.280 --> 00:54:03.610 align:start position:0% here is the validate Hearst data structure<00:54:01.760> found<00:54:02.420> the<00:54:02.630> beacon<00:54:02.750> train<00:54:03.050> state 00:54:03.610 --> 00:54:03.620 align:start position:0% structure found the beacon train state 00:54:03.620 --> 00:54:08.190 align:start position:0% structure found the beacon train state so<00:54:04.220> the<00:54:05.000> validator<00:54:05.360> is<00:54:06.400> has<00:54:07.400> these 00:54:08.190 --> 00:54:08.200 align:start position:0% so the validator is has these 00:54:08.200 --> 00:54:11.320 align:start position:0% so the validator is has these informations<00:54:09.200> we<00:54:09.440> need<00:54:09.590> to<00:54:09.680> know<00:54:09.880> it's<00:54:10.880> inside 00:54:11.320 --> 00:54:11.330 align:start position:0% informations we need to know it's inside 00:54:11.330 --> 00:54:15.420 align:start position:0% informations we need to know it's inside the<00:54:11.570> content<00:54:12.080> state<00:54:12.320> so<00:54:13.130> here<00:54:13.550> I<00:54:13.610> highlight<00:54:14.090> is 00:54:15.420 --> 00:54:15.430 align:start position:0% the content state so here I highlight is 00:54:15.430 --> 00:54:18.850 align:start position:0% the content state so here I highlight is the<00:54:16.430> status<00:54:17.090> a<00:54:17.270> parks<00:54:17.570> so<00:54:18.290> we<00:54:18.410> can<00:54:18.530> see<00:54:18.680> this 00:54:18.850 --> 00:54:18.860 align:start position:0% the status a parks so we can see this 00:54:18.860 --> 00:54:22.570 align:start position:0% the status a parks so we can see this four<00:54:19.390> different<00:54:20.830> state<00:54:21.830> of<00:54:21.860> each<00:54:22.130> park<00:54:22.340> are 00:54:22.570 --> 00:54:22.580 align:start position:0% four different state of each park are 00:54:22.580 --> 00:54:27.520 align:start position:0% four different state of each park are defined<00:54:23.090> here<00:54:23.240> and<00:54:24.670> initially<00:54:25.670> the<00:54:26.260> the<00:54:27.260> state 00:54:27.520 --> 00:54:27.530 align:start position:0% defined here and initially the the state 00:54:27.530 --> 00:54:32.290 align:start position:0% defined here and initially the the state epoch<00:54:27.950> is<00:54:28.700> set<00:54:29.060> into<00:54:29.330> the<00:54:30.940> unsigned<00:54:31.940> integer 00:54:32.290 --> 00:54:32.300 align:start position:0% epoch is set into the unsigned integer 00:54:32.300 --> 00:54:37.510 align:start position:0% epoch is set into the unsigned integer of<00:54:34.360> 64<00:54:35.360> bits<00:54:35.680> which<00:54:36.680> is<00:54:36.890> the<00:54:37.070> maximum<00:54:37.370> number 00:54:37.510 --> 00:54:37.520 align:start position:0% of 64 bits which is the maximum number 00:54:37.520 --> 00:54:43.090 align:start position:0% of 64 bits which is the maximum number of<00:54:37.910> here<00:54:38.270> so<00:54:38.840> the<00:54:39.230> reason<00:54:39.740> is<00:54:39.950> that<00:54:40.870> we<00:54:41.870> can<00:54:42.500> we 00:54:43.090 --> 00:54:43.100 align:start position:0% of here so the reason is that we can we 00:54:43.100 --> 00:54:46.360 align:start position:0% of here so the reason is that we can we haven't<00:54:43.640> defined<00:54:43.820> this<00:54:44.300> status<00:54:45.230> we<00:54:46.070> haven't 00:54:46.360 --> 00:54:46.370 align:start position:0% haven't defined this status we haven't 00:54:46.370 --> 00:54:48.340 align:start position:0% haven't defined this status we haven't defined<00:54:46.490> when<00:54:46.940> this<00:54:47.270> status<00:54:47.780> will<00:54:48.050> be 00:54:48.340 --> 00:54:48.350 align:start position:0% defined when this status will be 00:54:48.350 --> 00:54:49.000 align:start position:0% defined when this status will be happened 00:54:49.000 --> 00:54:49.010 align:start position:0% happened 00:54:49.010 --> 00:54:54.570 align:start position:0% happened so<00:54:49.430> we<00:54:49.640> said<00:54:49.820> a<00:54:49.850> rebel<00:54:50.240> own<00:54:50.360> wave<00:54:50.630> long<00:54:52.810> epoch 00:54:54.570 --> 00:54:54.580 align:start position:0% so we said a rebel own wave long epoch 00:54:54.580 --> 00:55:01.540 align:start position:0% so we said a rebel own wave long epoch okay<00:54:57.700> so<00:54:58.700> Stanley<00:54:59.660> explained<00:55:00.350> it<00:55:00.500> that<00:55:01.040> we 00:55:01.540 --> 00:55:01.550 align:start position:0% okay so Stanley explained it that we 00:55:01.550 --> 00:55:05.760 align:start position:0% okay so Stanley explained it that we defined<00:55:02.030> the<00:55:02.300> slot<00:55:02.660> and<00:55:02.930> epoch<00:55:03.470> so<00:55:03.740> each<00:55:04.550> epoch 00:55:05.760 --> 00:55:05.770 align:start position:0% defined the slot and epoch so each epoch 00:55:05.770 --> 00:55:10.930 align:start position:0% defined the slot and epoch so each epoch consists<00:55:06.770> of<00:55:07.120> 64<00:55:08.120> slots<00:55:08.540> and<00:55:08.870> each<00:55:09.650> slot<00:55:09.710> is<00:55:10.190> 6 00:55:10.930 --> 00:55:10.940 align:start position:0% consists of 64 slots and each slot is 6 00:55:10.940 --> 00:55:14.560 align:start position:0% consists of 64 slots and each slot is 6 seconds<00:55:11.330> so<00:55:12.140> we<00:55:12.350> can<00:55:12.560> use<00:55:12.800> this<00:55:13.100> epoch<00:55:13.820> number 00:55:14.560 --> 00:55:14.570 align:start position:0% seconds so we can use this epoch number 00:55:14.570 --> 00:55:17.280 align:start position:0% seconds so we can use this epoch number as<00:55:14.870> the<00:55:15.490> timestamp<00:55:16.490> here 00:55:17.280 --> 00:55:17.290 align:start position:0% as the timestamp here 00:55:17.290 --> 00:55:22.060 align:start position:0% as the timestamp here so<00:55:18.290> as<00:55:18.620> we<00:55:19.220> define<00:55:19.700> that<00:55:19.990> we<00:55:20.990> can<00:55:21.320> see<00:55:21.770> the 00:55:22.060 --> 00:55:22.070 align:start position:0% so as we define that we can see the 00:55:22.070 --> 00:55:25.780 align:start position:0% so as we define that we can see the epoch<00:55:22.520> of<00:55:22.640> hyaline<00:55:23.150> and<00:55:23.590> if<00:55:24.590> the<00:55:24.980> data<00:55:25.400> has 00:55:25.780 --> 00:55:25.790 align:start position:0% epoch of hyaline and if the data has 00:55:25.790 --> 00:55:30.100 align:start position:0% epoch of hyaline and if the data has been<00:55:26.150> set<00:55:26.900> to<00:55:27.200> with<00:55:28.100> activation<00:55:29.110> eligibility 00:55:30.100 --> 00:55:30.110 align:start position:0% been set to with activation eligibility 00:55:30.110 --> 00:55:33.790 align:start position:0% been set to with activation eligibility epoch<00:55:30.440> 100<00:55:31.040> and<00:55:31.360> also<00:55:32.360> the<00:55:32.660> activation<00:55:33.410> impact 00:55:33.790 --> 00:55:33.800 align:start position:0% epoch 100 and also the activation impact 00:55:33.800 --> 00:55:37.930 align:start position:0% epoch 100 and also the activation impact 200<00:55:34.390> then<00:55:35.390> when<00:55:35.840> the<00:55:36.020> time<00:55:36.290> actually<00:55:37.040> between 00:55:37.930 --> 00:55:37.940 align:start position:0% 200 then when the time actually between 00:55:37.940 --> 00:55:44.290 align:start position:0% 200 then when the time actually between two<00:55:38.300> of<00:55:38.420> this<00:55:39.200> to<00:55:39.560> ePub<00:55:40.810> for<00:55:41.810> example<00:55:42.250> 150<00:55:43.300> the 00:55:44.290 --> 00:55:44.300 align:start position:0% two of this to ePub for example 150 the 00:55:44.300 --> 00:55:48.420 align:start position:0% two of this to ePub for example 150 the violator<00:55:44.840> is<00:55:45.050> not<00:55:45.350> activate<00:55:46.130> yet 00:55:48.420 --> 00:55:48.430 align:start position:0% violator is not activate yet 00:55:48.430 --> 00:55:56.800 align:start position:0% violator is not activate yet and<00:55:52.120> when<00:55:53.120> after<00:55:53.450> 200<00:55:54.170> parks<00:55:54.560> the<00:55:55.510> data<00:55:56.510> will 00:55:56.800 --> 00:55:56.810 align:start position:0% and when after 200 parks the data will 00:55:56.810 --> 00:55:58.260 align:start position:0% and when after 200 parks the data will be<00:55:56.840> actually<00:55:57.470> at 00:55:58.260 --> 00:55:58.270 align:start position:0% be actually at 00:55:58.270 --> 00:56:12.650 align:start position:0% be actually at it<00:56:01.560> activate<00:56:04.980> and<00:56:10.230> so<00:56:11.230> we<00:56:11.980> introduced<00:56:12.310> the 00:56:12.650 --> 00:56:12.660 align:start position:0% it activate and so we introduced the 00:56:12.660 --> 00:56:16.890 align:start position:0% it activate and so we introduced the state<00:56:13.660> epochs<00:56:14.140> no<00:56:14.980> there's<00:56:15.250> another<00:56:15.790> flat<00:56:16.630> oh 00:56:16.890 --> 00:56:16.900 align:start position:0% state epochs no there's another flat oh 00:56:16.900 --> 00:56:26.090 align:start position:0% state epochs no there's another flat oh it's<00:56:20.250> another<00:56:21.250> factor<00:56:21.850> that<00:56:23.850> in<00:56:24.850> fact<00:56:25.090> uh<00:56:25.270> the 00:56:26.090 --> 00:56:26.100 align:start position:0% it's another factor that in fact uh the 00:56:26.100 --> 00:56:29.370 align:start position:0% it's another factor that in fact uh the peak<00:56:27.100> enchants<00:56:27.460> the<00:56:27.760> data<00:56:28.180> state<00:56:28.540> which<00:56:29.230> is 00:56:29.370 --> 00:56:29.380 align:start position:0% peak enchants the data state which is 00:56:29.380 --> 00:56:33.030 align:start position:0% peak enchants the data state which is called<00:56:29.410> dashed<00:56:30.360> which<00:56:31.360> I<00:56:31.540> think<00:56:31.990> Danny<00:56:32.770> will 00:56:33.030 --> 00:56:33.040 align:start position:0% called dashed which I think Danny will 00:56:33.040 --> 00:56:35.280 align:start position:0% called dashed which I think Danny will talk<00:56:33.310> about<00:56:33.430> how<00:56:33.820> the<00:56:33.880> idea<00:56:34.480> to<00:56:34.660> actually<00:56:35.020> be 00:56:35.280 --> 00:56:35.290 align:start position:0% talk about how the idea to actually be 00:56:35.290 --> 00:56:40.290 align:start position:0% talk about how the idea to actually be slashed<00:56:35.820> in<00:56:36.820> the<00:56:36.880> later<00:56:37.530> session<00:56:38.530> so<00:56:39.490> in<00:56:40.030> here 00:56:40.290 --> 00:56:40.300 align:start position:0% slashed in the later session so in here 00:56:40.300 --> 00:56:42.690 align:start position:0% slashed in the later session so in here you<00:56:40.510> only<00:56:40.630> need<00:56:40.930> to<00:56:41.050> know<00:56:41.110> is<00:56:41.590> that<00:56:41.830> a<00:56:42.070> flashed 00:56:42.690 --> 00:56:42.700 align:start position:0% you only need to know is that a flashed 00:56:42.700 --> 00:56:46.110 align:start position:0% you only need to know is that a flashed the<00:56:43.120> later<00:56:43.330> will<00:56:43.960> be<00:56:44.140> forced<00:56:44.650> to<00:56:45.100> exceed<00:56:45.850> it 00:56:46.110 --> 00:56:46.120 align:start position:0% the later will be forced to exceed it 00:56:46.120 --> 00:56:48.410 align:start position:0% the later will be forced to exceed it which<00:56:46.780> is<00:56:46.960> very<00:56:47.050> reasonable<00:56:47.380> because<00:56:47.830> they 00:56:48.410 --> 00:56:48.420 align:start position:0% which is very reasonable because they 00:56:48.420 --> 00:56:50.970 align:start position:0% which is very reasonable because they might<00:56:49.420> be<00:56:49.690> something<00:56:50.140> that<00:56:50.170> we<00:56:50.710> have 00:56:50.970 --> 00:56:50.980 align:start position:0% might be something that we have 00:56:50.980 --> 00:56:54.240 align:start position:0% might be something that we have misbehaved<00:56:51.820> so<00:56:52.420> they<00:56:52.990> were<00:56:53.050> big<00:56:53.380> thoughts<00:56:53.860> it 00:56:54.240 --> 00:56:54.250 align:start position:0% misbehaved so they were big thoughts it 00:56:54.250 --> 00:57:03.300 align:start position:0% misbehaved so they were big thoughts it to<00:56:54.940> be<00:56:55.330> yeah<00:56:58.710> I'm<00:56:59.710> going<00:57:00.670> to<00:57:00.700> talk<00:57:01.000> about<00:57:02.310> the 00:57:03.300 --> 00:57:03.310 align:start position:0% to be yeah I'm going to talk about the 00:57:03.310 --> 00:57:07.320 align:start position:0% to be yeah I'm going to talk about the red<00:57:03.490> limiting<00:57:04.000> cues<00:57:04.630> before<00:57:05.620> that<00:57:06.150> want<00:57:07.150> to 00:57:07.320 --> 00:57:07.330 align:start position:0% red limiting cues before that want to 00:57:07.330 --> 00:57:12.630 align:start position:0% red limiting cues before that want to introduce<00:57:07.720> the<00:57:08.080> quick<00:57:08.440> subjectivity<00:57:10.140> this<00:57:11.640> is 00:57:12.630 --> 00:57:12.640 align:start position:0% introduce the quick subjectivity this is 00:57:12.640 --> 00:57:16.020 align:start position:0% introduce the quick subjectivity this is a<00:57:12.700> feature<00:57:13.180> of<00:57:13.450> the<00:57:14.020> proof<00:57:14.230> of<00:57:14.350> stake<00:57:15.190> duction 00:57:16.020 --> 00:57:16.030 align:start position:0% a feature of the proof of stake duction 00:57:16.030 --> 00:57:22.800 align:start position:0% a feature of the proof of stake duction and<00:57:17.340> so<00:57:18.340> if<00:57:19.060> if<00:57:19.840> you<00:57:20.140> are<00:57:20.580> new<00:57:21.580> by<00:57:21.970> daters<00:57:22.390> we 00:57:22.800 --> 00:57:22.810 align:start position:0% and so if if you are new by daters we 00:57:22.810 --> 00:57:27.360 align:start position:0% and so if if you are new by daters we got<00:57:22.990> it<00:57:23.140> online<00:57:23.350> and<00:57:23.860> you<00:57:24.730> you<00:57:25.660> can<00:57:25.960> only<00:57:26.370> join 00:57:27.360 --> 00:57:27.370 align:start position:0% got it online and you you can only join 00:57:27.370 --> 00:57:32.130 align:start position:0% got it online and you you can only join you<00:57:27.820> can<00:57:27.970> only<00:57:28.150> trust<00:57:28.780> the<00:57:29.230> your<00:57:29.970> peers<00:57:31.140> around 00:57:32.130 --> 00:57:32.140 align:start position:0% you can only trust the your peers around 00:57:32.140 --> 00:57:36.090 align:start position:0% you can only trust the your peers around you<00:57:32.290> and<00:57:33.130> also<00:57:33.610> if<00:57:34.060> you<00:57:34.420> get<00:57:35.080> offline<00:57:35.530> and<00:57:35.860> then 00:57:36.090 --> 00:57:36.100 align:start position:0% you and also if you get offline and then 00:57:36.100 --> 00:57:39.780 align:start position:0% you and also if you get offline and then be<00:57:36.370> back<00:57:36.610> again<00:57:36.790> you<00:57:37.750> can<00:57:38.340> doing<00:57:39.340> the<00:57:39.520> same 00:57:39.780 --> 00:57:39.790 align:start position:0% be back again you can doing the same 00:57:39.790 --> 00:57:42.780 align:start position:0% be back again you can doing the same situations<00:57:40.600> that<00:57:41.140> you<00:57:41.410> can<00:57:41.590> only<00:57:41.710> trust<00:57:42.490> your 00:57:42.780 --> 00:57:42.790 align:start position:0% situations that you can only trust your 00:57:42.790 --> 00:57:48.540 align:start position:0% situations that you can only trust your neighborhood<00:57:43.270> so<00:57:44.940> then<00:57:46.050> how<00:57:47.050> long<00:57:47.350> you<00:57:47.770> can<00:57:48.040> be 00:57:48.540 --> 00:57:48.550 align:start position:0% neighborhood so then how long you can be 00:57:48.550 --> 00:57:52.170 align:start position:0% neighborhood so then how long you can be with<00:57:48.760> the<00:57:49.210> offline<00:57:49.450> its<00:57:50.110> introduced<00:57:51.180> it 00:57:52.170 --> 00:57:52.180 align:start position:0% with the offline its introduced it 00:57:52.180 --> 00:57:55.290 align:start position:0% with the offline its introduced it depends<00:57:52.630> on<00:57:52.720> how<00:57:53.050> long<00:57:53.380> the<00:57:54.100> it<00:57:54.310> takes<00:57:54.700> for<00:57:55.150> the 00:57:55.290 --> 00:57:55.300 align:start position:0% depends on how long the it takes for the 00:57:55.300 --> 00:57:59.750 align:start position:0% depends on how long the it takes for the attacker<00:57:55.690> to<00:57:55.870> withdraw<00:57:56.530> their<00:57:56.860> stake<00:57:57.690> then 00:57:59.750 --> 00:57:59.760 align:start position:0% attacker to withdraw their stake then 00:57:59.760 --> 00:58:05.550 align:start position:0% attacker to withdraw their stake then then<00:58:00.760> that's<00:58:01.150> why<00:58:01.570> the<00:58:02.430> state<00:58:03.430> I<00:58:04.380> mean<00:58:05.380> the 00:58:05.550 --> 00:58:05.560 align:start position:0% then that's why the state I mean the 00:58:05.560 --> 00:58:08.400 align:start position:0% then that's why the state I mean the exit<00:58:05.950> rate<00:58:06.310> is<00:58:06.580> important<00:58:07.180> here<00:58:07.390> and<00:58:07.540> also<00:58:08.020> the 00:58:08.400 --> 00:58:08.410 align:start position:0% exit rate is important here and also the 00:58:08.410 --> 00:58:11.340 align:start position:0% exit rate is important here and also the tie<00:58:08.740> line<00:58:09.220> the<00:58:09.610> the<00:58:09.970> tie<00:58:10.150> period<00:58:10.600> we<00:58:10.810> set<00:58:11.080> for 00:58:11.340 --> 00:58:11.350 align:start position:0% tie line the the tie period we set for 00:58:11.350 --> 00:58:12.120 align:start position:0% tie line the the tie period we set for and 00:58:12.120 --> 00:58:12.130 align:start position:0% and 00:58:12.130 --> 00:58:14.990 align:start position:0% and but<00:58:12.370> yet<00:58:12.520> her<00:58:12.640> from<00:58:13.000> the<00:58:13.300> time<00:58:13.540> it<00:58:13.810> initiates 00:58:14.990 --> 00:58:15.000 align:start position:0% but yet her from the time it initiates 00:58:15.000 --> 00:58:17.700 align:start position:0% but yet her from the time it initiates exceed<00:58:16.000> my<00:58:16.560> operation 00:58:17.700 --> 00:58:17.710 align:start position:0% exceed my operation 00:58:17.710 --> 00:58:21.480 align:start position:0% exceed my operation -<00:58:18.100> it's<00:58:18.790> actually<00:58:19.090> be<00:58:19.600> excited<00:58:20.290> that<00:58:21.040> triggers 00:58:21.480 --> 00:58:21.490 align:start position:0% - it's actually be excited that triggers 00:58:21.490 --> 00:58:28.230 align:start position:0% - it's actually be excited that triggers is<00:58:21.640> also<00:58:21.940> important<00:58:22.510> so<00:58:25.770> in<00:58:26.770> the<00:58:27.250> potential<00:58:27.910> we 00:58:28.230 --> 00:58:28.240 align:start position:0% is also important so in the potential we 00:58:28.240 --> 00:58:31.590 align:start position:0% is also important so in the potential we have<00:58:28.270> to<00:58:28.840> choose<00:58:29.740> which<00:58:30.160> is<00:58:30.220> twice<00:58:30.700> the<00:58:31.120> entry 00:58:31.590 --> 00:58:31.600 align:start position:0% have to choose which is twice the entry 00:58:31.600 --> 00:58:37.250 align:start position:0% have to choose which is twice the entry queue<00:58:32.140> and<00:58:32.380> another<00:58:32.800> wise<00:58:33.040> exceed<00:58:33.850> cubed<00:58:34.980> so 00:58:37.250 --> 00:58:37.260 align:start position:0% queue and another wise exceed cubed so 00:58:37.260 --> 00:58:42.120 align:start position:0% queue and another wise exceed cubed so let's<00:58:38.260> two<00:58:38.620> queues<00:58:38.920> are<00:58:40.290> the<00:58:41.290> reason<00:58:41.590> why<00:58:41.860> we 00:58:42.120 --> 00:58:42.130 align:start position:0% let's two queues are the reason why we 00:58:42.130 --> 00:58:45.810 align:start position:0% let's two queues are the reason why we use<00:58:42.160> queue<00:58:42.790> is<00:58:43.060> that<00:58:43.890> we<00:58:44.890> need<00:58:45.070> to<00:58:45.280> network 00:58:45.810 --> 00:58:45.820 align:start position:0% use queue is that we need to network 00:58:45.820 --> 00:58:48.690 align:start position:0% use queue is that we need to network also<00:58:46.300> the<00:58:46.870> you<00:58:47.800> know<00:58:47.920> that<00:58:48.070> network<00:58:48.400> and<00:58:48.580> also 00:58:48.690 --> 00:58:48.700 align:start position:0% also the you know that network and also 00:58:48.700 --> 00:58:51.600 align:start position:0% also the you know that network and also the<00:58:49.060> data<00:58:49.360> set<00:58:49.660> to<00:58:50.230> be<00:58:50.380> as<00:58:50.560> stable<00:58:50.830> as<00:58:51.130> it<00:58:51.310> can 00:58:51.600 --> 00:58:51.610 align:start position:0% the data set to be as stable as it can 00:58:51.610 --> 00:58:55.560 align:start position:0% the data set to be as stable as it can be<00:58:51.990> so<00:58:52.990> we<00:58:53.260> we<00:58:54.100> won't<00:58:54.310> allow<00:58:54.670> that<00:58:54.700> enough 00:58:55.560 --> 00:58:55.570 align:start position:0% be so we we won't allow that enough 00:58:55.570 --> 00:58:58.620 align:start position:0% be so we we won't allow that enough short<00:58:55.810> short<00:58:56.470> period<00:58:56.950> a<00:58:57.220> lot<00:58:57.520> of<00:58:57.730> the<00:58:58.480> data 00:58:58.620 --> 00:58:58.630 align:start position:0% short short period a lot of the data 00:58:58.630 --> 00:59:02.910 align:start position:0% short short period a lot of the data that<00:58:58.770> they<00:58:59.770> initiate<00:59:00.490> exceeds<00:59:01.120> then<00:59:01.720> the<00:59:02.050> data 00:59:02.910 --> 00:59:02.920 align:start position:0% that they initiate exceeds then the data 00:59:02.920 --> 00:59:06.960 align:start position:0% that they initiate exceeds then the data state<00:59:03.280> will<00:59:03.640> be<00:59:03.940> like<00:59:04.780> you<00:59:05.230> can't<00:59:05.970> select 00:59:06.960 --> 00:59:06.970 align:start position:0% state will be like you can't select 00:59:06.970 --> 00:59:12.570 align:start position:0% state will be like you can't select enough<00:59:07.930> weather<00:59:09.060> enough<00:59:10.060> and<00:59:10.530> the<00:59:11.530> since<00:59:11.830> say 00:59:12.570 --> 00:59:12.580 align:start position:0% enough weather enough and the since say 00:59:12.580 --> 00:59:18.030 align:start position:0% enough weather enough and the since say it<00:59:12.640> from<00:59:13.030> the<00:59:13.240> ladies<00:59:13.570> estate<00:59:14.010> and<00:59:15.690> also<00:59:17.040> it 00:59:18.030 --> 00:59:18.040 align:start position:0% it from the ladies estate and also it 00:59:18.040 --> 00:59:21.450 align:start position:0% it from the ladies estate and also it ensure<00:59:18.820> that<00:59:19.120> the<00:59:19.780> penalty<00:59:20.350> guarantees<00:59:20.890> is 00:59:21.450 --> 00:59:21.460 align:start position:0% ensure that the penalty guarantees is 00:59:21.460 --> 00:59:26.130 align:start position:0% ensure that the penalty guarantees is still<00:59:21.880> remained<00:59:22.450> between<00:59:23.200> the<00:59:23.700> two<00:59:24.700> chains<00:59:25.150> as 00:59:26.130 --> 00:59:26.140 align:start position:0% still remained between the two chains as 00:59:26.140 --> 00:59:30.240 align:start position:0% still remained between the two chains as well<00:59:26.470> as<00:59:26.680> the<00:59:26.920> later<00:59:27.370> locks<00:59:28.060> on<00:59:28.330> of<00:59:29.250> often 00:59:30.240 --> 00:59:30.250 align:start position:0% well as the later locks on of often 00:59:30.250 --> 00:59:35.160 align:start position:0% well as the later locks on of often enough<00:59:30.640> so<00:59:32.580> we<00:59:33.580> will<00:59:33.760> see<00:59:34.030> that<00:59:34.240> how<00:59:34.630> the<00:59:34.690> queue 00:59:35.160 --> 00:59:35.170 align:start position:0% enough so we will see that how the queue 00:59:35.170 --> 00:59:42.510 align:start position:0% enough so we will see that how the queue is<00:59:35.440> happen<00:59:37.350> so<00:59:38.760> so<00:59:39.760> this<00:59:40.300> is<00:59:40.360> the<00:59:41.220> channel<00:59:42.220> rate 00:59:42.510 --> 00:59:42.520 align:start position:0% is happen so so this is the channel rate 00:59:42.520 --> 00:59:48.840 align:start position:0% is happen so so this is the channel rate functions<00:59:43.360> we<00:59:44.170> you<00:59:45.130> can<00:59:45.250> see<00:59:45.520> that<00:59:46.050> the<00:59:47.850> for 00:59:48.840 --> 00:59:48.850 align:start position:0% functions we you can see that the for 00:59:48.850 --> 00:59:53.130 align:start position:0% functions we you can see that the for each<00:59:49.090> epoch<00:59:49.770> the<00:59:50.880> maximal<00:59:51.880> number<00:59:51.910> of<00:59:52.690> a<00:59:52.900> later 00:59:53.130 --> 00:59:53.140 align:start position:0% each epoch the maximal number of a later 00:59:53.140 --> 00:59:59.490 align:start position:0% each epoch the maximal number of a later can't<00:59:53.530> join<00:59:53.920> or<00:59:54.280> to<00:59:55.000> exceed<00:59:55.870> 85<00:59:57.870> it's<00:59:58.870> based<00:59:59.230> on 00:59:59.490 --> 00:59:59.500 align:start position:0% can't join or to exceed 85 it's based on 00:59:59.500 --> 01:00:04.020 align:start position:0% can't join or to exceed 85 it's based on the<00:59:59.860> current<01:00:00.190> active<01:00:01.000> very<01:00:01.930> data<01:00:02.110> count<01:00:03.030> so 01:00:04.020 --> 01:00:04.030 align:start position:0% the current active very data count so 01:00:04.030 --> 01:00:07.290 align:start position:0% the current active very data count so you<01:00:04.360> can<01:00:05.050> see<01:00:05.260> that<01:00:05.410> it<01:00:05.620> the<01:00:05.860> number<01:00:06.160> is<01:00:06.400> set<01:00:07.090> us 01:00:07.290 --> 01:00:07.300 align:start position:0% you can see that it the number is set us 01:00:07.300 --> 01:00:12.240 align:start position:0% you can see that it the number is set us this<01:00:08.200> and<01:00:08.500> the<01:00:08.890> tron<01:00:09.190> red<01:00:10.320> curtain<01:00:11.320> is<01:00:11.560> set<01:00:11.920> to 01:00:12.240 --> 01:00:12.250 align:start position:0% this and the tron red curtain is set to 01:00:12.250 --> 01:00:18.810 align:start position:0% this and the tron red curtain is set to like<01:00:13.260> 65<01:00:14.260> thousands<01:00:15.220> so<01:00:17.130> as<01:00:18.130> you<01:00:18.430> can<01:00:18.580> see<01:00:18.640> the 01:00:18.810 --> 01:00:18.820 align:start position:0% like 65 thousands so as you can see the 01:00:18.820 --> 01:00:20.970 align:start position:0% like 65 thousands so as you can see the number<01:00:19.150> we<01:00:19.270> can<01:00:19.450> estimate<01:00:20.020> that<01:00:20.500> how<01:00:20.920> many 01:00:20.970 --> 01:00:20.980 align:start position:0% number we can estimate that how many 01:00:20.980 --> 01:00:27.460 align:start position:0% number we can estimate that how many later<01:00:21.700> can<01:00:22.030> be<01:00:22.270> is<01:00:22.420> it<01:00:22.630> at<01:00:23.170> the<01:00:23.320> same<01:00:23.530> time 01:00:27.460 --> 01:00:27.470 align:start position:0% 01:00:27.470 --> 01:00:34.420 align:start position:0% and<01:00:28.470> the<01:00:29.160> lifecycle<01:00:32.330> so<01:00:33.330> at<01:00:33.660> the<01:00:33.930> beginning 01:00:34.420 --> 01:00:34.430 align:start position:0% and the lifecycle so at the beginning 01:00:34.430 --> 01:00:39.710 align:start position:0% and the lifecycle so at the beginning beginning<01:00:35.930> the<01:00:36.930> relator<01:00:37.820> they<01:00:38.820> will<01:00:39.030> make<01:00:39.690> a 01:00:39.710 --> 01:00:39.720 align:start position:0% beginning the relator they will make a 01:00:39.720 --> 01:00:42.470 align:start position:0% beginning the relator they will make a deposit<01:00:40.109> on<01:00:40.500> the<01:00:40.890> east<01:00:41.040> one<01:00:41.220> trend<01:00:41.550> and<01:00:41.849> it's 01:00:42.470 --> 01:00:42.480 align:start position:0% deposit on the east one trend and it's 01:00:42.480 --> 01:00:46.370 align:start position:0% deposit on the east one trend and it's one<01:00:42.630> change<01:00:42.900> is<01:00:43.080> the<01:00:43.470> end<01:00:43.800> point<01:00:44.599> get<01:00:45.599> to<01:00:45.869> get 01:00:46.370 --> 01:00:46.380 align:start position:0% one change is the end point get to get 01:00:46.380 --> 01:00:49.339 align:start position:0% one change is the end point get to get let<01:00:46.680> you<01:00:46.890> get<01:00:47.280> from<01:00:47.580> the<01:00:48.270> east<01:00:48.480> one<01:00:48.660> chain<01:00:48.930> to 01:00:49.339 --> 01:00:49.349 align:start position:0% let you get from the east one chain to 01:00:49.349 --> 01:00:53.570 align:start position:0% let you get from the east one chain to its<01:00:49.589> the<01:00:49.770> world<01:00:50.510> so<01:00:51.510> when<01:00:51.839> the<01:00:52.140> later<01:00:52.580> they 01:00:53.570 --> 01:00:53.580 align:start position:0% its the world so when the later they 01:00:53.580 --> 01:00:58.010 align:start position:0% its the world so when the later they make<01:00:54.300> a<01:00:54.330> deposit<01:00:54.630> of<01:00:54.960> the<01:00:55.619> 32<01:00:56.490> either<01:00:57.020> to 01:00:58.010 --> 01:00:58.020 align:start position:0% make a deposit of the 32 either to 01:00:58.020 --> 01:01:00.700 align:start position:0% make a deposit of the 32 either to discuss<01:00:58.550> deposit<01:00:59.550> contract 01:01:00.700 --> 01:01:00.710 align:start position:0% discuss deposit contract 01:01:00.710 --> 01:01:04.240 align:start position:0% discuss deposit contract you<01:01:01.710> also<01:01:01.920> watch<01:01:02.640> the<01:01:02.940> past<01:01:03.300> encounter<01:01:03.780> status 01:01:04.240 --> 01:01:04.250 align:start position:0% you also watch the past encounter status 01:01:04.250 --> 01:01:10.700 align:start position:0% you also watch the past encounter status from<01:01:05.250> the<01:01:05.430> be<01:01:05.550> control<01:01:08.450> so<01:01:09.450> so<01:01:10.320> this<01:01:10.500> is<01:01:10.560> a 01:01:10.700 --> 01:01:10.710 align:start position:0% from the be control so so this is a 01:01:10.710 --> 01:01:13.310 align:start position:0% from the be control so so this is a diagram<01:01:10.980> here<01:01:11.280> and<01:01:11.580> we<01:01:12.240> were<01:01:12.359> show<01:01:12.570> the<01:01:12.630> four 01:01:13.310 --> 01:01:13.320 align:start position:0% diagram here and we were show the four 01:01:13.320 --> 01:01:14.450 align:start position:0% diagram here and we were show the four that<01:01:13.980> were<01:01:14.130> later 01:01:14.450 --> 01:01:14.460 align:start position:0% that were later 01:01:14.460 --> 01:01:20.300 align:start position:0% that were later so<01:01:15.390> at<01:01:15.660> the<01:01:16.050> beginning<01:01:17.330> the<01:01:18.330> deposit<01:01:19.200> data<01:01:20.130> is 01:01:20.300 --> 01:01:20.310 align:start position:0% so at the beginning the deposit data is 01:01:20.310 --> 01:01:25.400 align:start position:0% so at the beginning the deposit data is here<01:01:20.780> and<01:01:22.640> we<01:01:23.640> will<01:01:23.790> check<01:01:24.060> online<01:01:24.420> and<01:01:25.080> on<01:01:25.260> the 01:01:25.400 --> 01:01:25.410 align:start position:0% here and we will check online and on the 01:01:25.410 --> 01:01:29.960 align:start position:0% here and we will check online and on the pension<01:01:25.710> logic<01:01:26.190> that<01:01:26.970> is<01:01:27.859> has<01:01:28.859> enough<01:01:29.490> balance 01:01:29.960 --> 01:01:29.970 align:start position:0% pension logic that is has enough balance 01:01:29.970 --> 01:01:35.030 align:start position:0% pension logic that is has enough balance and<01:01:30.240> ready<01:01:30.990> to<01:01:31.260> activate<01:01:32.450> and<01:01:33.560> after<01:01:34.560> full 01:01:35.030 --> 01:01:35.040 align:start position:0% and ready to activate and after full 01:01:35.040 --> 01:01:38.150 align:start position:0% and ready to activate and after full epochs<01:01:35.609> and<01:01:35.910> also<01:01:36.900> it's<01:01:37.290> a<01:01:37.470> first<01:01:37.710> influence 01:01:38.150 --> 01:01:38.160 align:start position:0% epochs and also it's a first influence 01:01:38.160 --> 01:01:41.660 align:start position:0% epochs and also it's a first influence of<01:01:38.339> our<01:01:38.670> queue<01:01:38.970> we<01:01:39.780> defined<01:01:40.200> that<01:01:40.380> the<01:01:41.040> tron 01:01:41.660 --> 01:01:41.670 align:start position:0% of our queue we defined that the tron 01:01:41.670 --> 01:01:45.650 align:start position:0% of our queue we defined that the tron rate<01:01:41.970> earlier<01:01:42.960> like<01:01:43.290> in<01:01:44.099> that<01:01:44.400> function<01:01:44.660> so 01:01:45.650 --> 01:01:45.660 align:start position:0% rate earlier like in that function so 01:01:45.660 --> 01:01:50.450 align:start position:0% rate earlier like in that function so only<01:01:45.869> the<01:01:46.430> small<01:01:47.430> amount<01:01:47.730> of<01:01:47.970> data<01:01:48.960> can<01:01:49.460> join 01:01:50.450 --> 01:01:50.460 align:start position:0% only the small amount of data can join 01:01:50.460 --> 01:01:53.570 align:start position:0% only the small amount of data can join the<01:01:50.730> various<01:01:51.510> said<01:01:51.750> this<01:01:52.710> is<01:01:52.920> the<01:01:53.070> entry<01:01:53.369> to 01:01:53.570 --> 01:01:53.580 align:start position:0% the various said this is the entry to 01:01:53.580 --> 01:02:03.589 align:start position:0% the various said this is the entry to here<01:01:57.200> okay<01:01:58.200> and<01:01:58.410> then<01:01:58.970> leave<01:02:01.910> now<01:02:02.910> let's<01:02:03.180> take 01:02:03.589 --> 01:02:03.599 align:start position:0% here okay and then leave now let's take 01:02:03.599 --> 01:02:09.910 align:start position:0% here okay and then leave now let's take a<01:02:03.630> look<01:02:03.930> the<01:02:04.170> button<01:02:05.839> diagram<01:02:06.920> so<01:02:07.920> from<01:02:08.400> the 01:02:09.910 --> 01:02:09.920 align:start position:0% a look the button diagram so from the 01:02:09.920 --> 01:02:15.040 align:start position:0% a look the button diagram so from the window<01:02:11.720> the<01:02:12.720> validator<01:02:13.020> is<01:02:13.099> activated<01:02:14.099> and 01:02:15.040 --> 01:02:15.050 align:start position:0% window the validator is activated and 01:02:15.050 --> 01:02:19.329 align:start position:0% window the validator is activated and there's<01:02:16.050> two<01:02:16.440> possible<01:02:17.420> in<01:02:18.420> this<01:02:18.690> road<01:02:18.960> is 01:02:19.329 --> 01:02:19.339 align:start position:0% there's two possible in this road is 01:02:19.339 --> 01:02:23.120 align:start position:0% there's two possible in this road is maybe<01:02:20.339> the<01:02:20.790> radiators<01:02:21.599> and<01:02:21.630> he<01:02:22.440> got<01:02:22.650> penalized 01:02:23.120 --> 01:02:23.130 align:start position:0% maybe the radiators and he got penalized 01:02:23.130 --> 01:02:27.140 align:start position:0% maybe the radiators and he got penalized and<01:02:23.609> times<01:02:24.390> my<01:02:24.540> times<01:02:24.780> and<01:02:25.430> the<01:02:26.430> the<01:02:26.790> radiative 01:02:27.140 --> 01:02:27.150 align:start position:0% and times my times and the the radiative 01:02:27.150 --> 01:02:30.410 align:start position:0% and times my times and the the radiative balance<01:02:27.270> is<01:02:27.750> insufficient<01:02:28.710> so<01:02:29.580> then<01:02:30.150> in<01:02:30.390> that 01:02:30.410 --> 01:02:30.420 align:start position:0% balance is insufficient so then in that 01:02:30.420 --> 01:02:36.380 align:start position:0% balance is insufficient so then in that time<01:02:30.890> the<01:02:31.890> ladies<01:02:32.400> will<01:02:32.609> be<01:02:33.170> objected<01:02:34.400> and<01:02:35.400> a 01:02:36.380 --> 01:02:36.390 align:start position:0% time the ladies will be objected and a 01:02:36.390 --> 01:02:39.080 align:start position:0% time the ladies will be objected and a knowledge<01:02:37.520> option<01:02:38.520> is<01:02:38.700> that 01:02:39.080 --> 01:02:39.090 align:start position:0% knowledge option is that 01:02:39.090 --> 01:02:42.530 align:start position:0% knowledge option is that but<01:02:39.420> nobody<01:02:40.050> that<01:02:40.260> can<01:02:40.820> volunteer<01:02:41.880> wellin 01:02:42.530 --> 01:02:42.540 align:start position:0% but nobody that can volunteer wellin 01:02:42.540 --> 01:02:46.880 align:start position:0% but nobody that can volunteer wellin Harry<01:02:43.250> exceed<01:02:44.250> here's<01:02:45.000> the<01:02:45.210> second<01:02:45.540> road<01:02:45.890> so 01:02:46.880 --> 01:02:46.890 align:start position:0% Harry exceed here's the second road so 01:02:46.890 --> 01:02:51.650 align:start position:0% Harry exceed here's the second road so both<01:02:47.730> roads<01:02:48.060> we'll<01:02:48.300> get<01:02:48.960> into<01:02:50.240> will<01:02:51.240> push 01:02:51.650 --> 01:02:51.660 align:start position:0% both roads we'll get into will push 01:02:51.660 --> 01:02:57.590 align:start position:0% both roads we'll get into will push Terminator<01:02:52.380> in<01:02:53.150> exceed<01:02:54.150> cue<01:02:54.510> here<01:02:55.580> so<01:02:56.600> it's 01:02:57.590 --> 01:02:57.600 align:start position:0% Terminator in exceed cue here so it's 01:02:57.600 --> 01:03:02.180 align:start position:0% Terminator in exceed cue here so it's also<01:02:59.360> it<01:03:00.360> has<01:03:00.600> to<01:03:00.900> wait<01:03:01.200> for<01:03:01.470> at<01:03:01.650> its<01:03:01.830> four 01:03:02.180 --> 01:03:02.190 align:start position:0% also it has to wait for at its four 01:03:02.190 --> 01:03:05.540 align:start position:0% also it has to wait for at its four epochs<01:03:02.610> and<01:03:02.970> also<01:03:03.900> it<01:03:04.170> has<01:03:04.410> to<01:03:04.650> be<01:03:04.830> enough<01:03:05.370> room 01:03:05.540 --> 01:03:05.550 align:start position:0% epochs and also it has to be enough room 01:03:05.550 --> 01:03:09.530 align:start position:0% epochs and also it has to be enough room Foley's<01:03:06.180> theater<01:03:06.600> to<01:03:06.900> exceed<01:03:07.700> and<01:03:08.700> then<01:03:09.270> we 01:03:09.530 --> 01:03:09.540 align:start position:0% Foley's theater to exceed and then we 01:03:09.540 --> 01:03:12.740 align:start position:0% Foley's theater to exceed and then we call<01:03:09.870> that<01:03:09.900> this<01:03:10.860> valley<01:03:11.130> it<01:03:11.250> is<01:03:11.400> in<01:03:12.180> the<01:03:12.420> state 01:03:12.740 --> 01:03:12.750 align:start position:0% call that this valley it is in the state 01:03:12.750 --> 01:03:21.950 align:start position:0% call that this valley it is in the state of<01:03:12.780> it's<01:03:13.770> our<01:03:14.010> -<01:03:14.670> but<01:03:15.380> is<01:03:16.380> exceeded<01:03:20.900> okay<01:03:21.900> so 01:03:21.950 --> 01:03:21.960 align:start position:0% of it's our - but is exceeded okay so 01:03:21.960 --> 01:03:30.530 align:start position:0% of it's our - but is exceeded okay so and<01:03:22.440> then<01:03:23.780> after<01:03:27.020> 27<01:03:28.020> hours<01:03:28.430> it<01:03:29.430> will<01:03:29.640> be<01:03:29.700> with 01:03:30.530 --> 01:03:30.540 align:start position:0% and then after 27 hours it will be with 01:03:30.540 --> 01:03:36.230 align:start position:0% and then after 27 hours it will be with durable<01:03:31.160> the<01:03:32.160> reason<01:03:32.580> why<01:03:32.970> we<01:03:33.350> remain<01:03:34.350> we<01:03:35.240> set 01:03:36.230 --> 01:03:36.240 align:start position:0% durable the reason why we remain we set 01:03:36.240 --> 01:03:39.560 align:start position:0% durable the reason why we remain we set a<01:03:36.270> delayed<01:03:36.750> high<01:03:36.990> between<01:03:37.590> the<01:03:38.330> excited<01:03:39.330> and 01:03:39.560 --> 01:03:39.570 align:start position:0% a delayed high between the excited and 01:03:39.570 --> 01:03:44.360 align:start position:0% a delayed high between the excited and we<01:03:40.140> Straubel<01:03:41.240> 3<01:03:42.240> most<01:03:42.690> reasons<01:03:43.350> why<01:03:44.160> is<01:03:44.220> that 01:03:44.360 --> 01:03:44.370 align:start position:0% we Straubel 3 most reasons why is that 01:03:44.370 --> 01:03:47.930 align:start position:0% we Straubel 3 most reasons why is that the<01:03:45.180> very<01:03:45.390> literally<01:03:45.690> after<01:03:46.260> the<01:03:47.130> it's 01:03:47.930 --> 01:03:47.940 align:start position:0% the very literally after the it's 01:03:47.940 --> 01:03:51.200 align:start position:0% the very literally after the it's exceeded<01:03:48.780> it's<01:03:49.290> still<01:03:49.530> possible<01:03:49.770> that<01:03:50.210> it 01:03:51.200 --> 01:03:51.210 align:start position:0% exceeded it's still possible that it 01:03:51.210 --> 01:03:57.760 align:start position:0% exceeded it's still possible that it will<01:03:51.360> cut<01:03:51.600> slashed<01:03:52.260> which<01:03:53.220> is<01:03:54.320> this<01:03:55.320> route<01:03:56.150> and 01:03:57.760 --> 01:03:57.770 align:start position:0% will cut slashed which is this route and 01:03:57.770 --> 01:04:02.240 align:start position:0% will cut slashed which is this route and also<01:03:59.360> maybe<01:04:00.360> the<01:04:00.780> very<01:04:00.930> still<01:04:01.650> have<01:04:01.830> chance<01:04:02.130> to 01:04:02.240 --> 01:04:02.250 align:start position:0% also maybe the very still have chance to 01:04:02.250 --> 01:04:05.050 align:start position:0% also maybe the very still have chance to get<01:04:02.640> some<01:04:03.120> a<01:04:03.450> small<01:04:03.900> amount<01:04:04.260> of<01:04:04.380> free<01:04:04.590> world 01:04:05.050 --> 01:04:05.060 align:start position:0% get some a small amount of free world 01:04:05.060 --> 01:04:09.770 align:start position:0% get some a small amount of free world before<01:04:06.060> it<01:04:06.480> actually<01:04:06.930> exit<01:04:07.580> and<01:04:08.580> also<01:04:08.880> it<01:04:09.330> will 01:04:09.770 --> 01:04:09.780 align:start position:0% before it actually exit and also it will 01:04:09.780 --> 01:04:12.830 align:start position:0% before it actually exit and also it will provide<01:04:10.530> proof<01:04:11.070> of<01:04:11.220> custody<01:04:12.060> challenges<01:04:12.600> high 01:04:12.830 --> 01:04:12.840 align:start position:0% provide proof of custody challenges high 01:04:12.840 --> 01:04:18.170 align:start position:0% provide proof of custody challenges high to<01:04:13.710> be<01:04:13.860> made<01:04:14.070> during<01:04:14.670> this<01:04:14.910> period<01:04:16.880> I'm<01:04:17.880> sorry 01:04:18.170 --> 01:04:18.180 align:start position:0% to be made during this period I'm sorry 01:04:18.180 --> 01:04:21.440 align:start position:0% to be made during this period I'm sorry the<01:04:18.390> poor<01:04:18.750> velocity<01:04:19.260> things<01:04:19.800> to<01:04:20.190> face<01:04:21.180> one 01:04:21.440 --> 01:04:21.450 align:start position:0% the poor velocity things to face one 01:04:21.450 --> 01:04:28.420 align:start position:0% the poor velocity things to face one thing<01:04:21.980> that<01:04:22.980> we<01:04:23.220> will<01:04:23.340> prepare<01:04:23.760> this<01:04:26.480> and<01:04:27.480> then 01:04:28.420 --> 01:04:28.430 align:start position:0% thing that we will prepare this and then 01:04:28.430 --> 01:04:32.330 align:start position:0% thing that we will prepare this and then let's<01:04:29.430> take<01:04:29.910> a<01:04:29.940> look<01:04:30.150> the<01:04:30.330> top<01:04:31.130> diagram 01:04:32.330 --> 01:04:32.340 align:start position:0% let's take a look the top diagram 01:04:32.340 --> 01:04:38.660 align:start position:0% let's take a look the top diagram so<01:04:34.610> the<01:04:35.610> activated<01:04:36.390> my<01:04:37.290> later<01:04:37.500> my<01:04:37.920> got<01:04:38.310> slashed 01:04:38.660 --> 01:04:38.670 align:start position:0% so the activated my later my got slashed 01:04:38.670 --> 01:04:43.160 align:start position:0% so the activated my later my got slashed and<01:04:39.770> after<01:04:40.770> it<01:04:41.130> got<01:04:41.460> stashed<01:04:41.880> you<01:04:42.600> will<01:04:42.810> wear 01:04:43.160 --> 01:04:43.170 align:start position:0% and after it got stashed you will wear 01:04:43.170 --> 01:04:47.350 align:start position:0% and after it got stashed you will wear the<01:04:43.290> short<01:04:43.650> delay<01:04:44.250> until<01:04:44.700> a<01:04:45.330> we<01:04:45.630> can<01:04:46.050> can 01:04:47.350 --> 01:04:47.360 align:start position:0% the short delay until a we can can 01:04:47.360 --> 01:04:52.120 align:start position:0% the short delay until a we can can initiate<01:04:48.360> withdraw<01:04:49.430> operation 01:04:52.120 --> 01:04:52.130 align:start position:0% initiate withdraw operation 01:04:52.130 --> 01:04:56.980 align:start position:0% initiate withdraw operation then<01:04:52.670> you<01:04:53.570> got<01:04:53.750> into<01:04:54.650> that<01:04:55.390> the<01:04:56.390> /<01:04:56.630> and 01:04:56.980 --> 01:04:56.990 align:start position:0% then you got into that the / and 01:04:56.990 --> 01:05:04.060 align:start position:0% then you got into that the / and exceeded<01:04:57.950> status<01:04:59.590> and<01:05:00.590> after<01:05:01.430> at<01:05:02.180> least<01:05:03.070> 36 01:05:04.060 --> 01:05:04.070 align:start position:0% exceeded status and after at least 36 01:05:04.070 --> 01:05:08.470 align:start position:0% exceeded status and after at least 36 days<01:05:05.110> it<01:05:06.110> will<01:05:06.320> be<01:05:06.530> with<01:05:06.800> durable<01:05:07.280> so<01:05:08.240> it's 01:05:08.470 --> 01:05:08.480 align:start position:0% days it will be with durable so it's 01:05:08.480 --> 01:05:13.660 align:start position:0% days it will be with durable so it's very<01:05:09.700> you<01:05:10.700> can<01:05:10.730> see<01:05:11.090> that<01:05:11.470> the<01:05:12.470> stash<01:05:13.010> theater 01:05:13.660 --> 01:05:13.670 align:start position:0% very you can see that the stash theater 01:05:13.670 --> 01:05:16.420 align:start position:0% very you can see that the stash theater has<01:05:13.940> to<01:05:14.180> wait<01:05:14.510> for<01:05:14.690> more<01:05:14.930> time<01:05:15.200> it's<01:05:16.160> got 01:05:16.420 --> 01:05:16.430 align:start position:0% has to wait for more time it's got 01:05:16.430 --> 01:05:18.610 align:start position:0% has to wait for more time it's got punished<01:05:16.940> because<01:05:17.270> the<01:05:17.720> there<01:05:18.050> either<01:05:18.350> is 01:05:18.610 --> 01:05:18.620 align:start position:0% punished because the there either is 01:05:18.620 --> 01:05:24.610 align:start position:0% punished because the there either is locked<01:05:18.950> into<01:05:19.250> the<01:05:19.820> kitchen<01:05:22.780> that's<01:05:23.780> the<01:05:24.170> full 01:05:24.610 --> 01:05:24.620 align:start position:0% locked into the kitchen that's the full 01:05:24.620 --> 01:05:28.770 align:start position:0% locked into the kitchen that's the full picture<01:05:24.860> that<01:05:25.640> you<01:05:25.820> can<01:05:26.000> see<01:05:26.210> how<01:05:26.900> the<01:05:27.430> little 01:05:28.770 --> 01:05:28.780 align:start position:0% picture that you can see how the little 01:05:28.780 --> 01:05:53.700 align:start position:0% picture that you can see how the little B<01:05:30.370> switch<01:05:31.370> between<01:05:31.640> those<01:05:32.060> data's<01:05:33.880> okay<01:05:36.880> okay 01:05:53.700 --> 01:05:53.710 align:start position:0% 01:05:53.710 --> 01:05:54.940 align:start position:0% okay 01:05:54.940 --> 01:05:54.950 align:start position:0% okay 01:05:54.950 --> 01:05:56.740 align:start position:0% okay so<01:05:55.130> I'm<01:05:55.280> going<01:05:55.430> to<01:05:55.490> talk<01:05:55.610> about<01:05:55.640> the<01:05:56.240> state 01:05:56.740 --> 01:05:56.750 align:start position:0% so I'm going to talk about the state 01:05:56.750 --> 01:05:59.530 align:start position:0% so I'm going to talk about the state transition<01:05:57.200> function<01:05:57.610> of<01:05:58.610> the<01:05:58.910> of<01:05:59.210> the<01:05:59.300> beacon 01:05:59.530 --> 01:05:59.540 align:start position:0% transition function of the of the beacon 01:05:59.540 --> 01:06:03.430 align:start position:0% transition function of the of the beacon chain<01:06:00.880> and<01:06:01.880> I<01:06:01.970> encourage<01:06:02.300> you<01:06:02.360> to<01:06:02.480> just<01:06:02.810> you 01:06:03.430 --> 01:06:03.440 align:start position:0% chain and I encourage you to just you 01:06:03.440 --> 01:06:05.800 align:start position:0% chain and I encourage you to just you know<01:06:03.500> read<01:06:04.070> the<01:06:04.220> specs<01:06:04.490> it's<01:06:05.150> actually<01:06:05.600> not 01:06:05.800 --> 01:06:05.810 align:start position:0% know read the specs it's actually not 01:06:05.810 --> 01:06:07.870 align:start position:0% know read the specs it's actually not too<01:06:06.050> bad<01:06:06.230> it's<01:06:06.470> only<01:06:06.620> roughly<01:06:07.490> a<01:06:07.520> thousand 01:06:07.870 --> 01:06:07.880 align:start position:0% too bad it's only roughly a thousand 01:06:07.880 --> 01:06:14.050 align:start position:0% too bad it's only roughly a thousand lines<01:06:08.030> of<01:06:08.120> code<01:06:11.530> quite<01:06:12.530> readable<01:06:12.800> and<01:06:13.490> the 01:06:14.050 --> 01:06:14.060 align:start position:0% lines of code quite readable and the 01:06:14.060 --> 01:06:16.600 align:start position:0% lines of code quite readable and the link<01:06:14.300> up<01:06:14.660> there<01:06:14.690> is<01:06:15.050> quite<01:06:15.380> long<01:06:15.800> so<01:06:15.860> I've<01:06:16.430> also 01:06:16.600 --> 01:06:16.610 align:start position:0% link up there is quite long so I've also 01:06:16.610 --> 01:06:19.840 align:start position:0% link up there is quite long so I've also shortened<01:06:17.420> it<01:06:18.070> okay<01:06:19.070> just<01:06:19.100> to<01:06:19.430> give<01:06:19.610> a<01:06:19.640> bit<01:06:19.820> of 01:06:19.840 --> 01:06:19.850 align:start position:0% shortened it okay just to give a bit of 01:06:19.850 --> 01:06:22.720 align:start position:0% shortened it okay just to give a bit of context<01:06:20.570> you<01:06:21.230> know<01:06:21.680> you<01:06:22.070> all<01:06:22.160> know<01:06:22.190> this<01:06:22.490> we 01:06:22.720 --> 01:06:22.730 align:start position:0% context you know you all know this we 01:06:22.730 --> 01:06:24.130 align:start position:0% context you know you all know this we have<01:06:22.850> the<01:06:22.940> beacon<01:06:23.240> chain<01:06:23.480> which<01:06:23.720> is<01:06:23.870> kind<01:06:24.050> of 01:06:24.130 --> 01:06:24.140 align:start position:0% have the beacon chain which is kind of 01:06:24.140 --> 01:06:26.740 align:start position:0% have the beacon chain which is kind of the<01:06:24.350> the<01:06:24.760> system<01:06:25.760> chain<01:06:26.030> of<01:06:26.240> the<01:06:26.330> whole<01:06:26.510> system 01:06:26.740 --> 01:06:26.750 align:start position:0% the the system chain of the whole system 01:06:26.750 --> 01:06:29.620 align:start position:0% the the system chain of the whole system the<01:06:27.260> spine<01:06:27.590> all<01:06:28.130> the<01:06:28.370> shards<01:06:28.880> kind<01:06:29.210> of<01:06:29.270> connect 01:06:29.620 --> 01:06:29.630 align:start position:0% the spine all the shards kind of connect 01:06:29.630 --> 01:06:32.230 align:start position:0% the spine all the shards kind of connect to<01:06:29.780> it<01:06:29.930> via<01:06:30.500> cross<01:06:30.830> links<01:06:31.220> the<01:06:31.730> shots<01:06:32.000> come 01:06:32.230 --> 01:06:32.240 align:start position:0% to it via cross links the shots come 01:06:32.240 --> 01:06:34.600 align:start position:0% to it via cross links the shots come later<01:06:32.480> and<01:06:32.930> I'm<01:06:33.290> going<01:06:33.440> to<01:06:33.500> focus<01:06:33.680> on<01:06:34.070> the 01:06:34.600 --> 01:06:34.610 align:start position:0% later and I'm going to focus on the 01:06:34.610 --> 01:06:36.420 align:start position:0% later and I'm going to focus on the beacon<01:06:34.880> chain 01:06:36.420 --> 01:06:36.430 align:start position:0% beacon chain 01:06:36.430 --> 01:06:40.390 align:start position:0% beacon chain okay<01:06:37.430> so<01:06:37.600> we<01:06:38.600> have<01:06:38.780> slots<01:06:39.050> we<01:06:39.290> know<01:06:39.440> this<01:06:39.650> we 01:06:40.390 --> 01:06:40.400 align:start position:0% okay so we have slots we know this we 01:06:40.400 --> 01:06:43.570 align:start position:0% okay so we have slots we know this we have<01:06:40.550> blocks<01:06:40.880> and<01:06:41.240> we<01:06:41.960> can<01:06:42.140> chain<01:06:42.380> and<01:06:42.650> we<01:06:43.430> also 01:06:43.570 --> 01:06:43.580 align:start position:0% have blocks and we can chain and we also 01:06:43.580 --> 01:06:47.020 align:start position:0% have blocks and we can chain and we also have<01:06:43.910> state<01:06:44.240> and<01:06:44.510> basically<01:06:45.130> state<01:06:46.130> advances 01:06:47.020 --> 01:06:47.030 align:start position:0% have state and basically state advances 01:06:47.030 --> 01:06:51.310 align:start position:0% have state and basically state advances for<01:06:47.780> every<01:06:48.110> block<01:06:48.320> and<01:06:49.510> so<01:06:50.510> what<01:06:51.080> I'd<01:06:51.140> like<01:06:51.260> to 01:06:51.310 --> 01:06:51.320 align:start position:0% for every block and so what I'd like to 01:06:51.320 --> 01:06:53.800 align:start position:0% for every block and so what I'd like to focus<01:06:51.590> on<01:06:51.890> today<01:06:52.130> is<01:06:52.280> you<01:06:53.030> know<01:06:53.090> what<01:06:53.600> is<01:06:53.780> a 01:06:53.800 --> 01:06:53.810 align:start position:0% focus on today is you know what is a 01:06:53.810 --> 01:06:56.620 align:start position:0% focus on today is you know what is a block<01:06:54.260> what<01:06:55.040> is<01:06:55.220> state<01:06:55.610> and<01:06:55.940> what<01:06:56.240> is<01:06:56.390> the 01:06:56.620 --> 01:06:56.630 align:start position:0% block what is state and what is the 01:06:56.630 --> 01:07:01.300 align:start position:0% block what is state and what is the state<01:06:56.840> transition<01:06:59.200> so<01:07:00.200> this<01:07:00.380> is<01:07:00.590> the<01:07:00.830> state 01:07:01.300 --> 01:07:01.310 align:start position:0% state transition so this is the state 01:07:01.310 --> 01:07:04.570 align:start position:0% state transition so this is the state transition<01:07:01.340> function<01:07:01.760> and<01:07:03.340> you<01:07:04.340> know<01:07:04.460> it 01:07:04.570 --> 01:07:04.580 align:start position:0% transition function and you know it 01:07:04.580 --> 01:07:06.190 align:start position:0% transition function and you know it takes<01:07:04.940> a<01:07:05.060> state 01:07:06.190 --> 01:07:06.200 align:start position:0% takes a state 01:07:06.200 --> 01:07:09.580 align:start position:0% takes a state which<01:07:06.770> returned<01:07:07.670> the<01:07:07.790> post<01:07:08.060> state<01:07:08.360> or<01:07:08.930> an 01:07:09.580 --> 01:07:09.590 align:start position:0% which returned the post state or an 01:07:09.590 --> 01:07:11.770 align:start position:0% which returned the post state or an error<01:07:09.800> so<01:07:10.520> we<01:07:10.550> can<01:07:10.910> just<01:07:11.060> say<01:07:11.150> okay<01:07:11.390> this<01:07:11.600> this 01:07:11.770 --> 01:07:11.780 align:start position:0% error so we can just say okay this this 01:07:11.780 --> 01:07:14.020 align:start position:0% error so we can just say okay this this block<01:07:12.110> is<01:07:12.260> just<01:07:12.470> invalid<01:07:12.950> and<01:07:13.160> I'm<01:07:13.340> gonna 01:07:14.020 --> 01:07:14.030 align:start position:0% block is just invalid and I'm gonna 01:07:14.030 --> 01:07:16.930 align:start position:0% block is just invalid and I'm gonna abort<01:07:14.360> there<01:07:14.710> and<01:07:15.710> if<01:07:15.980> it's<01:07:16.130> valid<01:07:16.310> I'll<01:07:16.670> give 01:07:16.930 --> 01:07:16.940 align:start position:0% abort there and if it's valid I'll give 01:07:16.940 --> 01:07:21.430 align:start position:0% abort there and if it's valid I'll give you<01:07:17.180> the<01:07:17.660> next<01:07:17.930> version<01:07:18.320> of<01:07:18.380> the<01:07:18.560> state<01:07:19.930> and<01:07:20.930> in 01:07:21.430 --> 01:07:21.440 align:start position:0% you the next version of the state and in 01:07:21.440 --> 01:07:25.510 align:start position:0% you the next version of the state and in addition<01:07:21.920> to<01:07:22.070> slots<01:07:22.370> we<01:07:23.150> have<01:07:23.330> a<01:07:23.480> box<01:07:23.750> so<01:07:24.520> 64 01:07:25.510 --> 01:07:25.520 align:start position:0% addition to slots we have a box so 64 01:07:25.520 --> 01:07:28.030 align:start position:0% addition to slots we have a box so 64 slots<01:07:25.760> for<01:07:25.940> a<01:07:26.090> park<01:07:26.360> which<01:07:27.110> is<01:07:27.350> six<01:07:27.620> point<01:07:27.830> four 01:07:28.030 --> 01:07:28.040 align:start position:0% slots for a park which is six point four 01:07:28.040 --> 01:07:33.610 align:start position:0% slots for a park which is six point four minutes<01:07:28.400> and<01:07:29.500> epochs<01:07:30.500> are<01:07:32.020> kind<01:07:33.020> of<01:07:33.110> important 01:07:33.610 --> 01:07:33.620 align:start position:0% minutes and epochs are kind of important 01:07:33.620 --> 01:07:34.420 align:start position:0% minutes and epochs are kind of important from<01:07:33.770> the<01:07:33.860> point<01:07:33.980> of<01:07:34.070> view<01:07:34.130> of<01:07:34.280> the<01:07:34.370> state 01:07:34.420 --> 01:07:34.430 align:start position:0% from the point of view of the state 01:07:34.430 --> 01:07:35.920 align:start position:0% from the point of view of the state transition<01:07:34.970> function<01:07:35.030> because<01:07:35.630> this<01:07:35.750> is 01:07:35.920 --> 01:07:35.930 align:start position:0% transition function because this is 01:07:35.930 --> 01:07:40.180 align:start position:0% transition function because this is where<01:07:36.200> some<01:07:37.010> of<01:07:37.040> the<01:07:37.990> kind<01:07:38.990> of<01:07:39.190> accounting 01:07:40.180 --> 01:07:40.190 align:start position:0% where some of the kind of accounting 01:07:40.190 --> 01:07:42.160 align:start position:0% where some of the kind of accounting happens<01:07:40.580> at<01:07:40.970> the<01:07:41.300> epoch<01:07:41.600> boundaries<01:07:41.990> so<01:07:42.110> you 01:07:42.160 --> 01:07:42.170 align:start position:0% happens at the epoch boundaries so you 01:07:42.170 --> 01:07:44.410 align:start position:0% happens at the epoch boundaries so you have<01:07:42.410> these<01:07:42.560> state<01:07:43.220> transition<01:07:43.730> functions<01:07:44.120> on 01:07:44.410 --> 01:07:44.420 align:start position:0% have these state transition functions on 01:07:44.420 --> 01:07:47.050 align:start position:0% have these state transition functions on the<01:07:44.540> Block<01:07:45.080> basis<01:07:45.530> and<01:07:45.770> then<01:07:46.190> you<01:07:46.310> have<01:07:46.550> also 01:07:47.050 --> 01:07:47.060 align:start position:0% the Block basis and then you have also 01:07:47.060 --> 01:07:48.580 align:start position:0% the Block basis and then you have also state<01:07:47.690> transition<01:07:48.050> functions<01:07:48.380> that<01:07:48.440> happen 01:07:48.580 --> 01:07:48.590 align:start position:0% state transition functions that happen 01:07:48.590 --> 01:07:54.820 align:start position:0% state transition functions that happen on<01:07:48.890> a<01:07:49.450> Airpark<01:07:50.450> basis<01:07:53.080> okay<01:07:54.080> so<01:07:54.140> this<01:07:54.560> is<01:07:54.800> a 01:07:54.820 --> 01:07:54.830 align:start position:0% on a Airpark basis okay so this is a 01:07:54.830 --> 01:07:57.700 align:start position:0% on a Airpark basis okay so this is a kind<01:07:55.130> of<01:07:55.220> a<01:07:55.910> high-level<01:07:56.420> overview<01:07:56.900> of<01:07:57.320> the 01:07:57.700 --> 01:07:57.710 align:start position:0% kind of a high-level overview of the 01:07:57.710 --> 01:08:00.730 align:start position:0% kind of a high-level overview of the various<01:07:58.010> components<01:07:58.670> of<01:07:59.230> of<01:08:00.230> the<01:08:00.440> beacon 01:08:00.730 --> 01:08:00.740 align:start position:0% various components of of the beacon 01:08:00.740 --> 01:08:04.060 align:start position:0% various components of of the beacon chain<01:08:00.950> and<01:08:01.990> you<01:08:02.990> can<01:08:03.020> kind<01:08:03.410> of<01:08:03.470> think<01:08:03.620> of<01:08:03.770> it<01:08:03.920> as 01:08:04.060 --> 01:08:04.070 align:start position:0% chain and you can kind of think of it as 01:08:04.070 --> 01:08:06.760 align:start position:0% chain and you can kind of think of it as an<01:08:04.220> organism<01:08:04.700> with<01:08:05.060> various<01:08:05.330> organs<01:08:05.780> that 01:08:06.760 --> 01:08:06.770 align:start position:0% an organism with various organs that 01:08:06.770 --> 01:08:08.140 align:start position:0% an organism with various organs that connect<01:08:07.160> to<01:08:07.220> each<01:08:07.370> other<01:08:07.490> so<01:08:07.700> you<01:08:07.820> might<01:08:08.030> have 01:08:08.140 --> 01:08:08.150 align:start position:0% connect to each other so you might have 01:08:08.150 --> 01:08:10.360 align:start position:0% connect to each other so you might have a<01:08:08.180> little<01:08:08.630> Long's<01:08:08.870> the<01:08:09.260> heart<01:08:09.530> whatever<01:08:09.890> all 01:08:10.360 --> 01:08:10.370 align:start position:0% a little Long's the heart whatever all 01:08:10.370 --> 01:08:12.520 align:start position:0% a little Long's the heart whatever all these<01:08:10.490> things<01:08:10.790> and<01:08:11.030> here<01:08:11.870> they<01:08:12.050> each<01:08:12.260> provide 01:08:12.520 --> 01:08:12.530 align:start position:0% these things and here they each provide 01:08:12.530 --> 01:08:15.910 align:start position:0% these things and here they each provide kind<01:08:12.920> of<01:08:13.010> vital<01:08:13.520> functions<01:08:14.030> so<01:08:14.590> for<01:08:15.590> example 01:08:15.910 --> 01:08:15.920 align:start position:0% kind of vital functions so for example 01:08:15.920 --> 01:08:19.570 align:start position:0% kind of vital functions so for example randomness<01:08:16.700> you<01:08:16.970> have<01:08:17.440> the<01:08:18.440> registry<01:08:19.400> which 01:08:19.570 --> 01:08:19.580 align:start position:0% randomness you have the registry which 01:08:19.580 --> 01:08:21.750 align:start position:0% randomness you have the registry which keeps<01:08:19.880> track<01:08:19.940> of<01:08:20.120> the<01:08:20.300> validators<01:08:20.870> you<01:08:21.260> have 01:08:21.750 --> 01:08:21.760 align:start position:0% keeps track of the validators you have 01:08:21.760 --> 01:08:24.160 align:start position:0% keeps track of the validators you have finality<01:08:22.760> down<01:08:23.240> there 01:08:24.160 --> 01:08:24.170 align:start position:0% finality down there 01:08:24.170 --> 01:08:26.170 align:start position:0% finality down there you<01:08:24.530> need<01:08:24.680> deposits<01:08:25.250> of<01:08:25.400> course<01:08:25.670> if<01:08:25.880> you<01:08:25.970> want 01:08:26.170 --> 01:08:26.180 align:start position:0% you need deposits of course if you want 01:08:26.180 --> 01:08:31.870 align:start position:0% you need deposits of course if you want proof<01:08:26.360> of<01:08:26.510> stake<01:08:27.100> and<01:08:30.070> yeah<01:08:31.070> everything<01:08:31.580> is 01:08:31.870 --> 01:08:31.880 align:start position:0% proof of stake and yeah everything is 01:08:31.880 --> 01:08:34.240 align:start position:0% proof of stake and yeah everything is kind<01:08:32.270> of<01:08:32.360> flat<01:08:32.780> so<01:08:32.990> it's<01:08:33.110> not<01:08:33.200> like<01:08:33.380> a<01:08:33.410> layered 01:08:34.240 --> 01:08:34.250 align:start position:0% kind of flat so it's not like a layered 01:08:34.250 --> 01:08:37.120 align:start position:0% kind of flat so it's not like a layered system<01:08:34.460> but<01:08:35.210> we<01:08:35.330> do<01:08:35.720> have<01:08:35.900> like<01:08:36.140> the<01:08:36.800> beacon 01:08:37.120 --> 01:08:37.130 align:start position:0% system but we do have like the beacon 01:08:37.130 --> 01:08:39.790 align:start position:0% system but we do have like the beacon chain<01:08:37.370> and<01:08:37.690> the<01:08:38.690> shard<01:08:38.930> data<01:08:39.200> and<01:08:39.500> the<01:08:39.590> short 01:08:39.790 --> 01:08:39.800 align:start position:0% chain and the shard data and the short 01:08:39.800 --> 01:08:41.650 align:start position:0% chain and the shard data and the short state<01:08:40.070> but<01:08:40.400> within<01:08:40.820> the<01:08:41.060> beacon<01:08:41.360> chain<01:08:41.540> is 01:08:41.650 --> 01:08:41.660 align:start position:0% state but within the beacon chain is 01:08:41.660 --> 01:08:44.580 align:start position:0% state but within the beacon chain is actually<01:08:41.780> quite<01:08:42.140> flat<01:08:42.410> and<01:08:42.440> and<01:08:42.970> horizontal 01:08:44.580 --> 01:08:44.590 align:start position:0% actually quite flat and and horizontal 01:08:44.590 --> 01:08:47.470 align:start position:0% actually quite flat and and horizontal and<01:08:45.590> each<01:08:45.770> of<01:08:45.920> these<01:08:46.070> things<01:08:46.340> you<01:08:47.090> know<01:08:47.210> we<01:08:47.300> can 01:08:47.470 --> 01:08:47.480 align:start position:0% and each of these things you know we can 01:08:47.480 --> 01:08:49.720 align:start position:0% and each of these things you know we can be<01:08:47.600> swapped<01:08:47.870> out<01:08:48.080> it's<01:08:48.350> very<01:08:48.530> modular<01:08:48.710> and<01:08:49.190> so 01:08:49.720 --> 01:08:49.730 align:start position:0% be swapped out it's very modular and so 01:08:49.730 --> 01:08:52.030 align:start position:0% be swapped out it's very modular and so you<01:08:49.970> know<01:08:50.060> one<01:08:50.210> of<01:08:50.240> the<01:08:50.420> goal<01:08:50.990> the<01:08:51.260> roles<01:08:51.500> of<01:08:51.740> a 01:08:52.030 --> 01:08:52.040 align:start position:0% you know one of the goal the roles of a 01:08:52.040 --> 01:08:53.920 align:start position:0% you know one of the goal the roles of a designer<01:08:52.370> is<01:08:52.640> kind<01:08:52.820> of<01:08:52.850> to<01:08:53.180> pick<01:08:53.420> the<01:08:53.720> best 01:08:53.920 --> 01:08:53.930 align:start position:0% designer is kind of to pick the best 01:08:53.930 --> 01:08:58.330 align:start position:0% designer is kind of to pick the best ingredients<01:08:54.590> there<01:08:54.800> and<01:08:55.840> try<01:08:56.840> and<01:08:57.190> put<01:08:58.190> them 01:08:58.330 --> 01:08:58.340 align:start position:0% ingredients there and try and put them 01:08:58.340 --> 01:09:03.610 align:start position:0% ingredients there and try and put them together<01:08:58.580> in<01:08:59.120> a<01:08:59.270> in<01:08:59.300> a<01:08:59.630> harmonious<01:09:00.320> system<01:09:02.620> and 01:09:03.610 --> 01:09:03.620 align:start position:0% together in a in a harmonious system and 01:09:03.620 --> 01:09:05.970 align:start position:0% together in a in a harmonious system and in<01:09:03.770> terms<01:09:03.920> of<01:09:04.040> color<01:09:04.250> coding<01:09:04.640> I'm<01:09:04.790> gonna<01:09:04.970> use 01:09:05.970 --> 01:09:05.980 align:start position:0% in terms of color coding I'm gonna use 01:09:05.980 --> 01:09:09.010 align:start position:0% in terms of color coding I'm gonna use blue<01:09:06.980> for<01:09:07.010> the<01:09:07.370> state<01:09:07.670> and<01:09:08.030> and<01:09:08.330> green<01:09:08.630> for<01:09:08.900> the 01:09:09.010 --> 01:09:09.020 align:start position:0% blue for the state and and green for the 01:09:09.020 --> 01:09:14.620 align:start position:0% blue for the state and and green for the blocks<01:09:10.480> okay<01:09:11.950> so<01:09:12.950> what<01:09:13.580> is<01:09:13.700> the<01:09:13.850> state<01:09:14.060> let's 01:09:14.620 --> 01:09:14.630 align:start position:0% blocks okay so what is the state let's 01:09:14.630 --> 01:09:18.070 align:start position:0% blocks okay so what is the state let's try<01:09:14.930> and<01:09:15.290> actually<01:09:16.010> read<01:09:16.460> the<01:09:16.610> code<01:09:16.960> chunk<01:09:17.960> by 01:09:18.070 --> 01:09:18.080 align:start position:0% try and actually read the code chunk by 01:09:18.080 --> 01:09:20.249 align:start position:0% try and actually read the code chunk by chunk 01:09:20.249 --> 01:09:20.259 align:start position:0% 01:09:20.259 --> 01:09:22.909 align:start position:0% trying<01:09:20.769> to<01:09:20.829> understand<01:09:21.129> what<01:09:21.909> is<01:09:22.059> in<01:09:22.269> there<01:09:22.509> so 01:09:22.909 --> 01:09:22.919 align:start position:0% trying to understand what is in there so 01:09:22.919 --> 01:09:26.819 align:start position:0% trying to understand what is in there so we<01:09:23.919> have<01:09:24.189> these<01:09:24.369> three<01:09:24.609> properties<01:09:25.679> which<01:09:26.679> are 01:09:26.819 --> 01:09:26.829 align:start position:0% we have these three properties which are 01:09:26.829 --> 01:09:28.889 align:start position:0% we have these three properties which are basically<01:09:27.219> related<01:09:27.459> to<01:09:27.729> two<01:09:28.089> versioning<01:09:28.629> in 01:09:28.889 --> 01:09:28.899 align:start position:0% basically related to two versioning in 01:09:28.899 --> 01:09:31.619 align:start position:0% basically related to two versioning in space<01:09:29.259> and<01:09:29.499> time<01:09:29.679> so<01:09:29.739> the<01:09:30.219> the<01:09:31.029> the<01:09:31.059> Genesis 01:09:31.619 --> 01:09:31.629 align:start position:0% space and time so the the the Genesis 01:09:31.629 --> 01:09:33.809 align:start position:0% space and time so the the the Genesis time<01:09:31.899> tells<01:09:32.679> you<01:09:32.829> when<01:09:33.069> when<01:09:33.459> the<01:09:33.579> state<01:09:33.789> was 01:09:33.809 --> 01:09:33.819 align:start position:0% time tells you when when the state was 01:09:33.819 --> 01:09:37.349 align:start position:0% time tells you when when the state was was<01:09:34.299> created<01:09:35.489> slot<01:09:36.489> kind<01:09:36.849> of<01:09:36.939> gives<01:09:37.179> you<01:09:37.329> a 01:09:37.349 --> 01:09:37.359 align:start position:0% was created slot kind of gives you a 01:09:37.359 --> 01:09:39.959 align:start position:0% was created slot kind of gives you a more<01:09:37.569> granular<01:09:38.339> notion<01:09:39.339> of<01:09:39.489> how<01:09:39.639> much<01:09:39.789> time 01:09:39.959 --> 01:09:39.969 align:start position:0% more granular notion of how much time 01:09:39.969 --> 01:09:42.419 align:start position:0% more granular notion of how much time has<01:09:40.209> processed<01:09:40.479> and<01:09:40.899> then<01:09:41.469> the<01:09:41.859> four<01:09:42.189> core 01:09:42.419 --> 01:09:42.429 align:start position:0% has processed and then the four core 01:09:42.429 --> 01:09:45.089 align:start position:0% has processed and then the four core kind<01:09:42.669> of<01:09:42.789> be<01:09:42.909> versioning<01:09:43.449> in<01:09:43.749> in<01:09:44.079> space<01:09:44.469> as<01:09:44.889> it 01:09:45.089 --> 01:09:45.099 align:start position:0% kind of be versioning in in space as it 01:09:45.099 --> 01:09:47.279 align:start position:0% kind of be versioning in in space as it was<01:09:45.279> as<01:09:45.429> opposed<01:09:45.699> to<01:09:45.789> versioning<01:09:46.209> in<01:09:46.329> time<01:09:46.599> so 01:09:47.279 --> 01:09:47.289 align:start position:0% was as opposed to versioning in time so 01:09:47.289 --> 01:09:49.739 align:start position:0% was as opposed to versioning in time so every<01:09:47.559> time<01:09:47.769> we<01:09:47.949> do<01:09:48.099> a<01:09:48.129> hard<01:09:48.429> fork<01:09:48.759> we're<01:09:49.599> going 01:09:49.739 --> 01:09:49.749 align:start position:0% every time we do a hard fork we're going 01:09:49.749 --> 01:09:52.499 align:start position:0% every time we do a hard fork we're going to<01:09:49.839> update<01:09:49.989> this<01:09:50.409> and<01:09:50.739> one<01:09:51.699> of<01:09:51.729> the<01:09:51.999> the 01:09:52.499 --> 01:09:52.509 align:start position:0% to update this and one of the the 01:09:52.509 --> 01:09:55.229 align:start position:0% to update this and one of the the impacts<01:09:52.989> that<01:09:53.079> has<01:09:53.319> is<01:09:53.589> on<01:09:53.619> the<01:09:53.949> the<01:09:54.909> way<01:09:55.030> that 01:09:55.229 --> 01:09:55.239 align:start position:0% impacts that has is on the the way that 01:09:55.239 --> 01:10:00.029 align:start position:0% impacts that has is on the the way that signatures<01:09:55.659> are<01:09:55.809> verified<01:09:58.439> okay<01:09:59.439> so<01:09:59.889> that's 01:10:00.029 --> 01:10:00.039 align:start position:0% signatures are verified okay so that's 01:10:00.039 --> 01:10:06.179 align:start position:0% signatures are verified okay so that's all<01:10:00.189> all<01:10:00.550> basic<01:10:00.969> stuff<01:10:02.219> more<01:10:03.219> kind<01:10:03.579> of<01:10:05.189> basic 01:10:06.179 --> 01:10:06.189 align:start position:0% all all basic stuff more kind of basic 01:10:06.189 --> 01:10:10.729 align:start position:0% all all basic stuff more kind of basic infrastructure<01:10:06.699> is<01:10:07.979> you<01:10:08.979> know<01:10:09.070> the<01:10:09.189> notion<01:10:09.550> of 01:10:10.729 --> 01:10:10.739 align:start position:0% infrastructure is you know the notion of 01:10:10.739 --> 01:10:14.759 align:start position:0% infrastructure is you know the notion of of<01:10:11.739> roots<01:10:12.639> so<01:10:12.909> we<01:10:12.939> have<01:10:13.209> state<01:10:14.169> roots<01:10:14.469> and 01:10:14.759 --> 01:10:14.769 align:start position:0% of roots so we have state roots and 01:10:14.769 --> 01:10:17.369 align:start position:0% of roots so we have state roots and block<01:10:14.979> roots<01:10:15.280> which<01:10:15.909> is<01:10:15.939> the<01:10:16.659> equivalent<01:10:17.169> to 01:10:17.369 --> 01:10:17.379 align:start position:0% block roots which is the equivalent to 01:10:17.379 --> 01:10:19.770 align:start position:0% block roots which is the equivalent to what<01:10:18.189> what<01:10:18.669> is<01:10:18.789> traditionally<01:10:19.300> called<01:10:19.570> a 01:10:19.770 --> 01:10:19.780 align:start position:0% what what is traditionally called a 01:10:19.780 --> 01:10:25.229 align:start position:0% what what is traditionally called a block<01:10:20.229> hash<01:10:20.530> or<01:10:20.919> an<01:10:21.820> estate<01:10:22.510> roots<01:10:23.219> and<01:10:24.239> this 01:10:25.229 --> 01:10:25.239 align:start position:0% block hash or an estate roots and this 01:10:25.239 --> 01:10:29.149 align:start position:0% block hash or an estate roots and this is<01:10:25.360> just<01:10:25.599> a<01:10:26.019> way<01:10:26.649> of<01:10:27.840> cryptographically 01:10:29.149 --> 01:10:29.159 align:start position:0% is just a way of cryptographically 01:10:29.159 --> 01:10:31.739 align:start position:0% is just a way of cryptographically keeping<01:10:30.159> track<01:10:30.459> of<01:10:30.760> the<01:10:31.059> various<01:10:31.179> objects 01:10:31.739 --> 01:10:31.749 align:start position:0% keeping track of the various objects 01:10:31.749 --> 01:10:36.359 align:start position:0% keeping track of the various objects that<01:10:32.379> we're<01:10:32.709> working<01:10:33.070> with<01:10:33.429> and<01:10:35.369> representing 01:10:36.359 --> 01:10:36.369 align:start position:0% that we're working with and representing 01:10:36.369 --> 01:10:39.060 align:start position:0% that we're working with and representing them<01:10:36.459> in<01:10:36.610> a<01:10:36.699> way<01:10:36.820> which<01:10:37.030> is<01:10:37.059> friendly<01:10:37.599> to<01:10:38.070> to 01:10:39.060 --> 01:10:39.070 align:start position:0% them in a way which is friendly to to 01:10:39.070 --> 01:10:41.520 align:start position:0% them in a way which is friendly to to work<01:10:39.249> with<01:10:39.489> so<01:10:39.789> the<01:10:40.629> reason<01:10:41.199> why<01:10:41.320> we're 01:10:41.520 --> 01:10:41.530 align:start position:0% work with so the reason why we're 01:10:41.530 --> 01:10:43.229 align:start position:0% work with so the reason why we're working<01:10:41.679> with<01:10:41.979> roots<01:10:42.309> as<01:10:42.489> opposed<01:10:42.789> to<01:10:42.849> two 01:10:43.229 --> 01:10:43.239 align:start position:0% working with roots as opposed to two 01:10:43.239 --> 01:10:45.839 align:start position:0% working with roots as opposed to two hashes<01:10:43.749> is<01:10:43.899> because<01:10:44.229> the<01:10:44.949> objects<01:10:45.550> that<01:10:45.699> we're 01:10:45.839 --> 01:10:45.849 align:start position:0% hashes is because the objects that we're 01:10:45.849 --> 01:10:48.479 align:start position:0% hashes is because the objects that we're working<01:10:46.030> with<01:10:46.239> are<01:10:46.629> structured<01:10:47.289> and<01:10:47.499> we<01:10:48.189> have 01:10:48.479 --> 01:10:48.489 align:start position:0% working with are structured and we have 01:10:48.489 --> 01:10:53.879 align:start position:0% working with are structured and we have this<01:10:48.760> notion<01:10:49.629> of<01:10:49.869> a<01:10:50.079> tree<01:10:51.179> of<01:10:52.179> hashes<01:10:52.749> and<01:10:53.739> so 01:10:53.879 --> 01:10:53.889 align:start position:0% this notion of a tree of hashes and so 01:10:53.889 --> 01:10:56.029 align:start position:0% this notion of a tree of hashes and so if<01:10:54.039> you're<01:10:54.189> interested<01:10:54.340> in<01:10:54.610> a<01:10:54.669> very<01:10:54.849> specific 01:10:56.029 --> 01:10:56.039 align:start position:0% if you're interested in a very specific 01:10:56.039 --> 01:11:00.770 align:start position:0% if you're interested in a very specific property<01:10:57.039> of<01:10:57.189> an<01:10:57.280> object<01:10:57.369> then<01:10:58.239> you<01:10:58.659> can 01:11:00.770 --> 01:11:00.780 align:start position:0% property of an object then you can 01:11:00.780 --> 01:11:04.290 align:start position:0% property of an object then you can access<01:11:01.780> it<01:11:01.989> via<01:11:02.019> a<01:11:02.550> americorps<01:11:03.550> path<01:11:03.760> for<01:11:04.030> just 01:11:04.290 --> 01:11:04.300 align:start position:0% access it via a americorps path for just 01:11:04.300 --> 01:11:05.909 align:start position:0% access it via a americorps path for just a<01:11:04.419> specific<01:11:04.809> object<01:11:04.959> as<01:11:05.289> opposed<01:11:05.559> to<01:11:05.649> having 01:11:05.909 --> 01:11:05.919 align:start position:0% a specific object as opposed to having 01:11:05.919 --> 01:11:12.119 align:start position:0% a specific object as opposed to having to<01:11:06.429> need<01:11:06.639> the<01:11:06.820> whole<01:11:06.999> object<01:11:09.840> and<01:11:10.979> then<01:11:11.979> we 01:11:12.119 --> 01:11:12.129 align:start position:0% to need the whole object and then we 01:11:12.129 --> 01:11:16.350 align:start position:0% to need the whole object and then we have<01:11:12.629> kind<01:11:13.629> of<01:11:13.689> the<01:11:13.899> the<01:11:14.260> economic<01:11:14.969> link<01:11:15.969> to 01:11:16.350 --> 01:11:16.360 align:start position:0% have kind of the the economic link to 01:11:16.360 --> 01:11:19.409 align:start position:0% have kind of the the economic link to 'if<01:11:16.570> one<01:11:16.869> so<01:11:17.309> we<01:11:18.309> need<01:11:18.489> deposit<01:11:18.999> in<01:11:19.179> to<01:11:19.300> leave 01:11:19.409 --> 01:11:19.419 align:start position:0% 'if one so we need deposit in to leave 01:11:19.419 --> 01:11:21.750 align:start position:0% 'if one so we need deposit in to leave to<01:11:19.689> the<01:11:20.199> deposits<01:11:20.679> come<01:11:20.860> from<01:11:21.070> if<01:11:21.219> one<01:11:21.429> and<01:11:21.669> so 01:11:21.750 --> 01:11:21.760 align:start position:0% to the deposits come from if one and so 01:11:21.760 --> 01:11:24.119 align:start position:0% to the deposits come from if one and so the<01:11:21.999> if<01:11:22.419> two<01:11:22.809> needs<01:11:23.079> to<01:11:23.199> be<01:11:23.320> aware<01:11:23.590> of<01:11:23.649> if<01:11:23.919> one 01:11:24.119 --> 01:11:24.129 align:start position:0% the if two needs to be aware of if one 01:11:24.129 --> 01:11:26.040 align:start position:0% the if two needs to be aware of if one and<01:11:24.369> and<01:11:24.519> this<01:11:24.669> is<01:11:24.909> the<01:11:25.449> state<01:11:25.719> that<01:11:25.749> is<01:11:25.989> going 01:11:26.040 --> 01:11:26.050 align:start position:0% and and this is the state that is going 01:11:26.050 --> 01:11:31.469 align:start position:0% and and this is the state that is going to<01:11:26.320> help<01:11:26.499> us<01:11:27.209> be<01:11:28.209> aware<01:11:28.539> of<01:11:28.599> if<01:11:28.959> one<01:11:29.139> and<01:11:30.479> then 01:11:31.469 --> 01:11:31.479 align:start position:0% to help us be aware of if one and then 01:11:31.479 --> 01:11:32.740 align:start position:0% to help us be aware of if one and then we<01:11:31.929> have<01:11:32.079> the<01:11:32.260> register 01:11:32.740 --> 01:11:32.750 align:start position:0% we have the register 01:11:32.750 --> 01:11:36.880 align:start position:0% we have the register this<01:11:33.320> is<01:11:33.440> going<01:11:33.620> to<01:11:33.770> be<01:11:34.780> like<01:11:35.780> probably<01:11:36.650> the 01:11:36.880 --> 01:11:36.890 align:start position:0% this is going to be like probably the 01:11:36.890 --> 01:11:39.220 align:start position:0% this is going to be like probably the most<01:11:37.040> important<01:11:37.610> part<01:11:37.790> of<01:11:38.000> the<01:11:38.090> state<01:11:38.360> so<01:11:38.990> it's 01:11:39.220 --> 01:11:39.230 align:start position:0% most important part of the state so it's 01:11:39.230 --> 01:11:41.800 align:start position:0% most important part of the state so it's just<01:11:39.520> the<01:11:40.520> data<01:11:40.700> structure<01:11:41.150> that<01:11:41.180> keeps<01:11:41.510> track 01:11:41.800 --> 01:11:41.810 align:start position:0% just the data structure that keeps track 01:11:41.810 --> 01:11:44.050 align:start position:0% just the data structure that keeps track of<01:11:41.840> all<01:11:42.050> the<01:11:42.200> validators<01:11:42.800> and<01:11:43.040> it's<01:11:43.550> by<01:11:43.760> far 01:11:44.050 --> 01:11:44.060 align:start position:0% of all the validators and it's by far 01:11:44.060 --> 01:11:46.330 align:start position:0% of all the validators and it's by far the<01:11:44.210> largest<01:11:44.570> part<01:11:44.870> of<01:11:44.990> the<01:11:45.560> state<01:11:45.800> so<01:11:45.830> you 01:11:46.330 --> 01:11:46.340 align:start position:0% the largest part of the state so you 01:11:46.340 --> 01:11:49.750 align:start position:0% the largest part of the state so you know<01:11:46.820> this<01:11:46.970> might<01:11:47.180> be<01:11:47.210> hundreds<01:11:48.020> of<01:11:48.760> hundreds 01:11:49.750 --> 01:11:49.760 align:start position:0% know this might be hundreds of hundreds 01:11:49.760 --> 01:11:52.000 align:start position:0% know this might be hundreds of hundreds of<01:11:49.850> megabytes<01:11:50.630> let's<01:11:51.020> say<01:11:51.200> and<01:11:51.440> the<01:11:51.800> rest 01:11:52.000 --> 01:11:52.010 align:start position:0% of megabytes let's say and the rest 01:11:52.010 --> 01:11:58.120 align:start position:0% of megabytes let's say and the rest might<01:11:52.280> be<01:11:52.430> tiny<01:11:52.820> just<01:11:53.180> a<01:11:53.840> few<01:11:54.560> megabytes<01:11:57.130> we 01:11:58.120 --> 01:11:58.130 align:start position:0% might be tiny just a few megabytes we 01:11:58.130 --> 01:12:01.330 align:start position:0% might be tiny just a few megabytes we have<01:11:58.720> some<01:11:59.720> state<01:11:59.990> related<01:12:00.440> to<01:12:00.590> shuffling<01:12:01.040> and 01:12:01.330 --> 01:12:01.340 align:start position:0% have some state related to shuffling and 01:12:01.340 --> 01:12:06.070 align:start position:0% have some state related to shuffling and and<01:12:01.550> randomness<01:12:03.550> we<01:12:04.550> have<01:12:04.790> state<01:12:05.270> related<01:12:05.660> to 01:12:06.070 --> 01:12:06.080 align:start position:0% and randomness we have state related to 01:12:06.080 --> 01:12:11.190 align:start position:0% and randomness we have state related to slashings<01:12:09.220> we<01:12:10.220> have<01:12:10.370> state<01:12:10.610> related<01:12:10.850> to 01:12:11.190 --> 01:12:11.200 align:start position:0% slashings we have state related to 01:12:11.200 --> 01:12:12.580 align:start position:0% slashings we have state related to attestations 01:12:12.580 --> 01:12:12.590 align:start position:0% attestations 01:12:12.590 --> 01:12:15.820 align:start position:0% attestations so<01:12:13.040> at<01:12:13.580> the<01:12:13.850> stations<01:12:14.300> is<01:12:14.480> basically<01:12:14.840> what<01:12:15.680> the 01:12:15.820 --> 01:12:15.830 align:start position:0% so at the stations is basically what the 01:12:15.830 --> 01:12:17.470 align:start position:0% so at the stations is basically what the validators<01:12:16.400> need<01:12:16.580> to<01:12:16.700> do<01:12:16.850> that's<01:12:17.030> the<01:12:17.240> work 01:12:17.470 --> 01:12:17.480 align:start position:0% validators need to do that's the work 01:12:17.480 --> 01:12:20.860 align:start position:0% validators need to do that's the work that<01:12:18.260> they<01:12:18.350> have<01:12:18.530> to<01:12:18.560> do<01:12:18.830> it<01:12:19.400> helps<01:12:19.870> advance 01:12:20.860 --> 01:12:20.870 align:start position:0% that they have to do it helps advance 01:12:20.870 --> 01:12:23.440 align:start position:0% that they have to do it helps advance the<01:12:21.080> system<01:12:21.440> and<01:12:21.710> make<01:12:22.430> it<01:12:22.580> move<01:12:22.760> forward<01:12:23.030> and 01:12:23.440 --> 01:12:23.450 align:start position:0% the system and make it move forward and 01:12:23.450 --> 01:12:25.750 align:start position:0% the system and make it move forward and this<01:12:23.900> is<01:12:24.050> what<01:12:24.290> the<01:12:24.500> the<01:12:24.710> validators<01:12:25.220> get<01:12:25.430> get 01:12:25.750 --> 01:12:25.760 align:start position:0% this is what the the validators get get 01:12:25.760 --> 01:12:30.550 align:start position:0% this is what the the validators get get paid<01:12:25.970> for<01:12:28.510> we<01:12:29.510> have<01:12:29.660> the<01:12:29.780> cross<01:12:29.990> links<01:12:30.350> which 01:12:30.550 --> 01:12:30.560 align:start position:0% paid for we have the cross links which 01:12:30.560 --> 01:12:33.310 align:start position:0% paid for we have the cross links which is<01:12:30.710> the<01:12:30.920> link<01:12:31.280> to<01:12:31.610> the<01:12:32.240> to<01:12:32.480> the<01:12:32.600> various<01:12:32.900> shards 01:12:33.310 --> 01:12:33.320 align:start position:0% is the link to the to the various shards 01:12:33.320 --> 01:12:36.790 align:start position:0% is the link to the to the various shards and<01:12:33.500> then<01:12:34.400> finally<01:12:34.910> we<01:12:35.120> have<01:12:35.360> the<01:12:36.290> finality 01:12:36.790 --> 01:12:36.800 align:start position:0% and then finally we have the finality 01:12:36.800 --> 01:12:41.710 align:start position:0% and then finally we have the finality mechanism<01:12:39.400> and<01:12:40.400> in<01:12:40.670> terms<01:12:40.880> of<01:12:41.090> concretely 01:12:41.710 --> 01:12:41.720 align:start position:0% mechanism and in terms of concretely 01:12:41.720 --> 01:12:43.810 align:start position:0% mechanism and in terms of concretely what<01:12:41.990> are<01:12:42.350> the<01:12:42.470> the<01:12:43.130> modules<01:12:43.490> that<01:12:43.610> we've 01:12:43.810 --> 01:12:43.820 align:start position:0% what are the the modules that we've 01:12:43.820 --> 01:12:48.190 align:start position:0% what are the the modules that we've chosen<01:12:44.030> here<01:12:44.510> are<01:12:44.600> some<01:12:44.720> of<01:12:44.840> the<01:12:46.630> key<01:12:47.630> words<01:12:47.870> so 01:12:48.190 --> 01:12:48.200 align:start position:0% chosen here are some of the key words so 01:12:48.200 --> 01:12:50.500 align:start position:0% chosen here are some of the key words so we<01:12:48.320> have<01:12:48.500> F<01:12:49.070> F<01:12:49.310> G<01:12:49.490> for<01:12:49.700> finality 01:12:50.500 --> 01:12:50.510 align:start position:0% we have F F G for finality 01:12:50.510 --> 01:12:53.890 align:start position:0% we have F F G for finality we<01:12:50.960> have<01:12:51.370> BLS<01:12:52.370> signatures<01:12:52.910> for<01:12:53.840> the 01:12:53.890 --> 01:12:53.900 align:start position:0% we have BLS signatures for the 01:12:53.900 --> 01:12:56.800 align:start position:0% we have BLS signatures for the attestation<01:12:54.170> x'<01:12:54.530> goes<01:12:55.280> for<01:12:56.090> the<01:12:56.180> focus<01:12:56.540> rule 01:12:56.800 --> 01:12:56.810 align:start position:0% attestation x' goes for the focus rule 01:12:56.810 --> 01:13:00.430 align:start position:0% attestation x' goes for the focus rule we<01:12:57.680> have<01:12:57.920> Rand<01:12:58.250> out<01:12:58.460> for<01:12:58.700> randomness<01:12:59.290> swap<01:13:00.290> or 01:13:00.430 --> 01:13:00.440 align:start position:0% we have Rand out for randomness swap or 01:13:00.440 --> 01:13:03.460 align:start position:0% we have Rand out for randomness swap or not<01:13:00.620> for<01:13:00.980> the<01:13:01.070> shuffling<01:13:01.460> we<01:13:02.270> have<01:13:02.480> surety<01:13:03.020> 56 01:13:03.460 --> 01:13:03.470 align:start position:0% not for the shuffling we have surety 56 01:13:03.470 --> 01:13:05.560 align:start position:0% not for the shuffling we have surety 56 as<01:13:03.620> a<01:13:03.650> hash<01:13:03.890> function<01:13:03.920> and<01:13:04.550> we<01:13:05.120> have<01:13:05.270> tree 01:13:05.560 --> 01:13:05.570 align:start position:0% as a hash function and we have tree 01:13:05.570 --> 01:13:15.520 align:start position:0% as a hash function and we have tree hashing<01:13:06.080> as<01:13:06.290> the<01:13:07.010> way<01:13:07.190> that<01:13:07.970> we<01:13:10.990> we<01:13:14.530> Merck 01:13:15.520 --> 01:13:15.530 align:start position:0% hashing as the way that we we Merck 01:13:15.530 --> 01:13:20.500 align:start position:0% hashing as the way that we we Merck realize<01:13:15.830> the<01:13:16.160> the<01:13:16.940> objects<01:13:19.360> okay 01:13:20.500 --> 01:13:20.510 align:start position:0% realize the the objects okay 01:13:20.510 --> 01:13:22.210 align:start position:0% realize the the objects okay so<01:13:20.840> it<01:13:20.930> all<01:13:21.020> fits<01:13:21.260> in<01:13:21.350> this<01:13:21.470> slide<01:13:21.680> this<01:13:22.010> is 01:13:22.210 --> 01:13:22.220 align:start position:0% so it all fits in this slide this is 01:13:22.220 --> 01:13:28.660 align:start position:0% so it all fits in this slide this is this<01:13:22.730> is<01:13:22.910> the<01:13:23.090> the<01:13:23.660> state<01:13:25.510> okay<01:13:26.740> so<01:13:27.740> let's<01:13:28.220> try 01:13:28.660 --> 01:13:28.670 align:start position:0% this is the the state okay so let's try 01:13:28.670 --> 01:13:33.580 align:start position:0% this is the the state okay so let's try and<01:13:28.820> understand<01:13:29.150> what's<01:13:29.330> in<01:13:29.480> a<01:13:30.050> block<01:13:31.960> so<01:13:32.960> in 01:13:33.580 --> 01:13:33.590 align:start position:0% and understand what's in a block so in 01:13:33.590 --> 01:13:35.680 align:start position:0% and understand what's in a block so in the<01:13:33.770> block<01:13:33.950> we<01:13:34.040> kind<01:13:34.220> of<01:13:34.280> have<01:13:34.490> the<01:13:35.210> header 01:13:35.680 --> 01:13:35.690 align:start position:0% the block we kind of have the header 01:13:35.690 --> 01:13:39.010 align:start position:0% the block we kind of have the header this<01:13:36.080> is<01:13:36.260> the<01:13:36.380> header<01:13:36.770> with<01:13:37.840> things<01:13:38.840> you'd 01:13:39.010 --> 01:13:39.020 align:start position:0% this is the header with things you'd 01:13:39.020 --> 01:13:41.560 align:start position:0% this is the header with things you'd expect<01:13:39.140> like<01:13:39.830> the<01:13:40.100> slot<01:13:41.030> which<01:13:41.330> is<01:13:41.360> the 01:13:41.560 --> 01:13:41.570 align:start position:0% expect like the slot which is the 01:13:41.570 --> 01:13:42.760 align:start position:0% expect like the slot which is the equivalent<01:13:41.750> of<01:13:42.050> the<01:13:42.200> height<01:13:42.440> and<01:13:42.680> other 01:13:42.760 --> 01:13:42.770 align:start position:0% equivalent of the height and other 01:13:42.770 --> 01:13:45.800 align:start position:0% equivalent of the height and other systems<01:13:43.250> the<01:13:44.000> parent<01:13:44.540> route<01:13:44.810> which<01:13:45.620> the 01:13:45.800 --> 01:13:45.810 align:start position:0% systems the parent route which the 01:13:45.810 --> 01:13:48.320 align:start position:0% systems the parent route which the the<01:13:45.900> parent<01:13:46.530> hash<01:13:46.770> in<01:13:47.160> a<01:13:47.430> novice<01:13:47.700> system<01:13:48.000> state 01:13:48.320 --> 01:13:48.330 align:start position:0% the parent hash in a novice system state 01:13:48.330 --> 01:13:51.440 align:start position:0% the parent hash in a novice system state route<01:13:48.740> the<01:13:49.740> signature<01:13:50.280> which<01:13:50.820> is<01:13:50.850> going<01:13:51.090> to<01:13:51.180> be 01:13:51.440 --> 01:13:51.450 align:start position:0% route the signature which is going to be 01:13:51.450 --> 01:13:54.230 align:start position:0% route the signature which is going to be the<01:13:51.600> BLS<01:13:52.350> signature<01:13:52.770> and<01:13:52.980> then<01:13:53.520> the<01:13:54.030> body 01:13:54.230 --> 01:13:54.240 align:start position:0% the BLS signature and then the body 01:13:54.240 --> 01:13:56.840 align:start position:0% the BLS signature and then the body which<01:13:54.600> is<01:13:54.630> going<01:13:54.870> to<01:13:55.080> be<01:13:55.260> like<01:13:56.190> the<01:13:56.370> more 01:13:56.840 --> 01:13:56.850 align:start position:0% which is going to be like the more 01:13:56.850 --> 01:14:01.250 align:start position:0% which is going to be like the more important<01:13:57.300> part<01:13:57.620> of<01:13:58.620> the<01:13:59.340> block<01:14:00.200> okay<01:14:01.200> so 01:14:01.250 --> 01:14:01.260 align:start position:0% important part of the block okay so 01:14:01.260 --> 01:14:03.380 align:start position:0% important part of the block okay so let's<01:14:01.620> let's<01:14:02.250> look<01:14:02.400> at<01:14:02.610> the<01:14:02.700> body<01:14:02.910> what's<01:14:03.240> in 01:14:03.380 --> 01:14:03.390 align:start position:0% let's let's look at the body what's in 01:14:03.390 --> 01:14:08.630 align:start position:0% let's let's look at the body what's in there<01:14:04.400> so<01:14:05.990> you<01:14:06.990> know<01:14:07.110> we<01:14:07.500> have<01:14:07.740> fields<01:14:08.490> that 01:14:08.630 --> 01:14:08.640 align:start position:0% there so you know we have fields that 01:14:08.640 --> 01:14:14.600 align:start position:0% there so you know we have fields that are<01:14:08.930> relevant<01:14:09.930> to<01:14:10.140> two<01:14:10.440> of<01:14:10.800> these<01:14:13.250> systems<01:14:14.250> one 01:14:14.600 --> 01:14:14.610 align:start position:0% are relevant to two of these systems one 01:14:14.610 --> 01:14:16.970 align:start position:0% are relevant to two of these systems one is<01:14:14.820> the<01:14:15.000> randomness<01:14:15.480> system<01:14:15.870> making<01:14:16.710> progress 01:14:16.970 --> 01:14:16.980 align:start position:0% is the randomness system making progress 01:14:16.980 --> 01:14:20.440 align:start position:0% is the randomness system making progress ran<01:14:17.850> down<01:14:18.120> and<01:14:18.420> then<01:14:18.990> the<01:14:19.200> other<01:14:19.350> one<01:14:19.620> is 01:14:20.440 --> 01:14:20.450 align:start position:0% ran down and then the other one is 01:14:20.450 --> 01:14:25.340 align:start position:0% ran down and then the other one is related<01:14:21.450> to<01:14:21.480> the<01:14:22.350> link<01:14:22.620> to<01:14:22.770> f1<01:14:23.190> so<01:14:24.320> trying<01:14:25.320> to 01:14:25.340 --> 01:14:25.350 align:start position:0% related to the link to f1 so trying to 01:14:25.350 --> 01:14:27.380 align:start position:0% related to the link to f1 so trying to make<01:14:25.470> that<01:14:25.740> progress<01:14:26.010> through<01:14:26.490> voting<01:14:26.970> and 01:14:27.380 --> 01:14:27.390 align:start position:0% make that progress through voting and 01:14:27.390 --> 01:14:30.680 align:start position:0% make that progress through voting and then<01:14:27.930> we<01:14:28.080> have<01:14:28.350> a<01:14:28.710> graffiti<01:14:29.340> which<01:14:29.910> is<01:14:30.180> just 01:14:30.680 --> 01:14:30.690 align:start position:0% then we have a graffiti which is just 01:14:30.690 --> 01:14:33.170 align:start position:0% then we have a graffiti which is just any<01:14:31.320> any<01:14:31.830> data<01:14:32.130> so<01:14:32.640> this<01:14:32.850> is<01:14:32.970> kind<01:14:33.120> of 01:14:33.170 --> 01:14:33.180 align:start position:0% any any data so this is kind of 01:14:33.180 --> 01:14:38.000 align:start position:0% any any data so this is kind of encouraging<01:14:34.020> people<01:14:34.200> to<01:14:34.410> to<01:14:35.220> innovate<01:14:37.010> with 01:14:38.000 --> 01:14:38.010 align:start position:0% encouraging people to to innovate with 01:14:38.010 --> 01:14:43.430 align:start position:0% encouraging people to to innovate with putting<01:14:38.610> data<01:14:38.880> on<01:14:39.150> the<01:14:39.270> beacon<01:14:39.510> chain<01:14:42.440> and 01:14:43.430 --> 01:14:43.440 align:start position:0% putting data on the beacon chain and 01:14:43.440 --> 01:14:45.320 align:start position:0% putting data on the beacon chain and then<01:14:43.770> we<01:14:43.950> have<01:14:44.160> the<01:14:44.340> equivalents<01:14:44.760> of<01:14:44.850> a 01:14:45.320 --> 01:14:45.330 align:start position:0% then we have the equivalents of a 01:14:45.330 --> 01:14:48.110 align:start position:0% then we have the equivalents of a transaction<01:14:46.110> so<01:14:46.440> normally<01:14:46.830> in<01:14:47.460> a<01:14:47.580> block<01:14:47.850> you'd 01:14:48.110 --> 01:14:48.120 align:start position:0% transaction so normally in a block you'd 01:14:48.120 --> 01:14:50.600 align:start position:0% transaction so normally in a block you'd put<01:14:48.330> transactions<01:14:49.190> here<01:14:50.190> it's<01:14:50.340> a<01:14:50.460> bit 01:14:50.600 --> 01:14:50.610 align:start position:0% put transactions here it's a bit 01:14:50.610 --> 01:14:52.220 align:start position:0% put transactions here it's a bit different<01:14:50.820> because<01:14:51.060> the<01:14:51.330> transactions<01:14:51.990> are 01:14:52.220 --> 01:14:52.230 align:start position:0% different because the transactions are 01:14:52.230 --> 01:14:53.750 align:start position:0% different because the transactions are not<01:14:52.260> user<01:14:52.800> transactions<01:14:53.490> they're 01:14:53.750 --> 01:14:53.760 align:start position:0% not user transactions they're 01:14:53.760 --> 01:14:56.540 align:start position:0% not user transactions they're system-level<01:14:54.240> transactions<01:14:55.050> so<01:14:55.650> we<01:14:56.370> call 01:14:56.540 --> 01:14:56.550 align:start position:0% system-level transactions so we call 01:14:56.550 --> 01:14:59.750 align:start position:0% system-level transactions so we call them<01:14:56.700> operations<01:14:57.360> and<01:14:57.630> we<01:14:58.590> have<01:14:58.830> these<01:14:59.460> five 01:14:59.750 --> 01:14:59.760 align:start position:0% them operations and we have these five 01:14:59.760 --> 01:15:03.230 align:start position:0% them operations and we have these five different<01:15:00.000> operations<01:15:01.280> two<01:15:02.280> are<01:15:02.550> related<01:15:03.030> to 01:15:03.230 --> 01:15:03.240 align:start position:0% different operations two are related to 01:15:03.240 --> 01:15:06.950 align:start position:0% different operations two are related to to<01:15:03.900> slashing<01:15:04.550> one<01:15:05.550> is<01:15:05.790> the<01:15:06.510> attestations 01:15:06.950 --> 01:15:06.960 align:start position:0% to slashing one is the attestations 01:15:06.960 --> 01:15:09.680 align:start position:0% to slashing one is the attestations which<01:15:07.380> is<01:15:07.530> where<01:15:07.710> like<01:15:08.040> the<01:15:08.580> real<01:15:09.150> work<01:15:09.450> should 01:15:09.680 --> 01:15:09.690 align:start position:0% which is where like the real work should 01:15:09.690 --> 01:15:14.900 align:start position:0% which is where like the real work should happen<01:15:10.020> and<01:15:10.490> then<01:15:11.490> you<01:15:12.150> have<01:15:13.910> transactions 01:15:14.900 --> 01:15:14.910 align:start position:0% happen and then you have transactions 01:15:14.910 --> 01:15:19.610 align:start position:0% happen and then you have transactions which<01:15:15.240> are<01:15:16.640> related<01:15:17.640> to<01:15:17.990> people<01:15:18.990> coming<01:15:19.320> in<01:15:19.470> of 01:15:19.610 --> 01:15:19.620 align:start position:0% which are related to people coming in of 01:15:19.620 --> 01:15:22.640 align:start position:0% which are related to people coming in of the<01:15:19.740> system<01:15:20.210> leaving<01:15:21.210> the<01:15:21.330> system<01:15:21.540> or<01:15:22.140> moving 01:15:22.640 --> 01:15:22.650 align:start position:0% the system leaving the system or moving 01:15:22.650 --> 01:15:24.710 align:start position:0% the system leaving the system or moving funds<01:15:22.950> within<01:15:23.340> within<01:15:23.730> the<01:15:24.000> system<01:15:24.330> so<01:15:24.540> these 01:15:24.710 --> 01:15:24.720 align:start position:0% funds within within the system so these 01:15:24.720 --> 01:15:28.130 align:start position:0% funds within within the system so these are<01:15:24.780> just<01:15:25.490> registry<01:15:26.490> operations<01:15:27.140> the 01:15:28.130 --> 01:15:28.140 align:start position:0% are just registry operations the 01:15:28.140 --> 01:15:29.960 align:start position:0% are just registry operations the attestation<01:15:28.560> is<01:15:28.830> probably<01:15:29.130> the<01:15:29.280> most 01:15:29.960 --> 01:15:29.970 align:start position:0% attestation is probably the most 01:15:29.970 --> 01:15:32.210 align:start position:0% attestation is probably the most important<01:15:30.480> so<01:15:30.630> block<01:15:31.560> contains<01:15:31.980> at<01:15:32.130> the 01:15:32.210 --> 01:15:32.220 align:start position:0% important so block contains at the 01:15:32.220 --> 01:15:33.890 align:start position:0% important so block contains at the stations<01:15:32.640> and<01:15:32.910> that's<01:15:33.330> what<01:15:33.510> moves<01:15:33.690> the 01:15:33.890 --> 01:15:33.900 align:start position:0% stations and that's what moves the 01:15:33.900 --> 01:15:38.960 align:start position:0% stations and that's what moves the system<01:15:34.230> forward<01:15:37.070> okay<01:15:38.070> so<01:15:38.130> I<01:15:38.280> want<01:15:38.460> to<01:15:38.520> try<01:15:38.670> and 01:15:38.960 --> 01:15:38.970 align:start position:0% system forward okay so I want to try and 01:15:38.970 --> 01:15:41.360 align:start position:0% system forward okay so I want to try and give<01:15:39.240> you<01:15:39.390> like<01:15:39.600> the<01:15:39.630> really<01:15:40.050> high<01:15:40.650> level<01:15:41.070> of 01:15:41.360 --> 01:15:41.370 align:start position:0% give you like the really high level of 01:15:41.370 --> 01:15:43.520 align:start position:0% give you like the really high level of the<01:15:41.700> state<01:15:41.940> transition<01:15:42.390> function<01:15:42.420> and<01:15:42.960> I'm 01:15:43.520 --> 01:15:43.530 align:start position:0% the state transition function and I'm 01:15:43.530 --> 01:15:46.130 align:start position:0% the state transition function and I'm gonna<01:15:43.830> cheat<01:15:44.220> a<01:15:44.250> little<01:15:44.460> bit<01:15:44.690> and<01:15:45.690> I'm<01:15:45.840> going 01:15:46.130 --> 01:15:46.140 align:start position:0% gonna cheat a little bit and I'm going 01:15:46.140 --> 01:15:50.450 align:start position:0% gonna cheat a little bit and I'm going to<01:15:46.400> only<01:15:47.400> present<01:15:48.170> what<01:15:49.170> I<01:15:49.230> call<01:15:49.530> the<01:15:49.680> honest 01:15:50.450 --> 01:15:50.460 align:start position:0% to only present what I call the honest 01:15:50.460 --> 01:15:53.420 align:start position:0% to only present what I call the honest state<01:15:51.120> transition<01:15:51.600> function<01:15:51.630> and<01:15:52.230> by<01:15:52.980> honest 01:15:53.420 --> 01:15:53.430 align:start position:0% state transition function and by honest 01:15:53.430 --> 01:15:56.960 align:start position:0% state transition function and by honest I<01:15:53.550> mean<01:15:53.730> that<01:15:54.030> I'm<01:15:54.480> going<01:15:54.780> to<01:15:54.900> assume<01:15:55.470> that<01:15:55.970> the 01:15:56.960 --> 01:15:56.970 align:start position:0% I mean that I'm going to assume that the 01:15:56.970 --> 01:15:59.779 align:start position:0% I mean that I'm going to assume that the block<01:15:57.300> has<01:15:58.230> been<01:15:58.410> honestly<01:15:58.890> constructed 01:15:59.779 --> 01:15:59.789 align:start position:0% block has been honestly constructed 01:15:59.789 --> 01:16:02.959 align:start position:0% block has been honestly constructed so<01:16:00.059> it's<01:16:00.510> a<01:16:00.599> valid<01:16:00.929> block<01:16:01.199> and<01:16:01.610> and<01:16:02.610> what<01:16:02.849> this 01:16:02.959 --> 01:16:02.969 align:start position:0% so it's a valid block and and what this 01:16:02.969 --> 01:16:07.040 align:start position:0% so it's a valid block and and what this means<01:16:03.769> in<01:16:04.769> practice<01:16:05.250> is<01:16:05.429> that<01:16:05.719> I'm<01:16:06.719> going<01:16:06.989> to 01:16:07.040 --> 01:16:07.050 align:start position:0% means in practice is that I'm going to 01:16:07.050 --> 01:16:09.410 align:start position:0% means in practice is that I'm going to try<01:16:07.260> and<01:16:07.440> tell<01:16:07.949> you<01:16:08.010> what<01:16:08.639> are<01:16:08.820> the<01:16:08.969> mutations 01:16:09.410 --> 01:16:09.420 align:start position:0% try and tell you what are the mutations 01:16:09.420 --> 01:16:13.689 align:start position:0% try and tell you what are the mutations that<01:16:10.670> the<01:16:11.670> block<01:16:11.969> will<01:16:12.539> make<01:16:12.809> on<01:16:13.050> the<01:16:13.320> state 01:16:13.689 --> 01:16:13.699 align:start position:0% that the block will make on the state 01:16:13.699 --> 01:16:15.919 align:start position:0% that the block will make on the state but<01:16:14.699> what<01:16:14.849> I'm<01:16:14.969> not<01:16:15.000> going<01:16:15.360> to<01:16:15.449> tell<01:16:15.659> you<01:16:15.809> about 01:16:15.919 --> 01:16:15.929 align:start position:0% but what I'm not going to tell you about 01:16:15.929 --> 01:16:19.399 align:start position:0% but what I'm not going to tell you about is<01:16:16.820> all<01:16:17.820> the<01:16:17.880> various<01:16:18.480> ways<01:16:18.690> that<01:16:18.719> you<01:16:18.960> that 01:16:19.399 --> 01:16:19.409 align:start position:0% is all the various ways that you that 01:16:19.409 --> 01:16:21.709 align:start position:0% is all the various ways that you that the<01:16:19.769> state<01:16:20.280> transition<01:16:20.760> function<01:16:20.820> can<01:16:21.300> can 01:16:21.709 --> 01:16:21.719 align:start position:0% the state transition function can can 01:16:21.719 --> 01:16:23.660 align:start position:0% the state transition function can can throw<01:16:21.960> an<01:16:22.110> error<01:16:22.289> so<01:16:23.010> all<01:16:23.190> the<01:16:23.309> various 01:16:23.660 --> 01:16:23.670 align:start position:0% throw an error so all the various 01:16:23.670 --> 01:16:26.839 align:start position:0% throw an error so all the various assertions<01:16:24.570> and<01:16:25.110> it<01:16:25.289> turns<01:16:25.829> out<01:16:26.070> that<01:16:26.250> the 01:16:26.839 --> 01:16:26.849 align:start position:0% assertions and it turns out that the 01:16:26.849 --> 01:16:28.850 align:start position:0% assertions and it turns out that the bulk<01:16:27.090> of<01:16:27.239> the<01:16:27.360> complexity<01:16:27.900> is<01:16:28.110> actually<01:16:28.500> here 01:16:28.850 --> 01:16:28.860 align:start position:0% bulk of the complexity is actually here 01:16:28.860 --> 01:16:31.160 align:start position:0% bulk of the complexity is actually here but<01:16:29.429> here<01:16:29.760> is<01:16:29.880> really<01:16:30.210> boring<01:16:30.449> stuff<01:16:30.690> is<01:16:31.019> like 01:16:31.160 --> 01:16:31.170 align:start position:0% but here is really boring stuff is like 01:16:31.170 --> 01:16:33.859 align:start position:0% but here is really boring stuff is like Oh<01:16:31.519> verified<01:16:32.519> that<01:16:32.760> the<01:16:32.909> signatures<01:16:33.449> valid 01:16:33.859 --> 01:16:33.869 align:start position:0% Oh verified that the signatures valid 01:16:33.869 --> 01:16:36.140 align:start position:0% Oh verified that the signatures valid verify<01:16:34.679> that<01:16:34.889> if<01:16:35.099> you're<01:16:35.309> transferring<01:16:35.699> funds 01:16:36.140 --> 01:16:36.150 align:start position:0% verify that if you're transferring funds 01:16:36.150 --> 01:16:43.399 align:start position:0% verify that if you're transferring funds you<01:16:36.869> have<01:16:36.900> enough<01:16:37.380> funds<01:16:37.679> I<01:16:42.050> think<01:16:43.050> most<01:16:43.289> of 01:16:43.399 --> 01:16:43.409 align:start position:0% you have enough funds I think most of 01:16:43.409 --> 01:16:46.220 align:start position:0% you have enough funds I think most of the<01:16:43.530> insight<01:16:43.920> actually<01:16:44.369> you<01:16:44.849> know<01:16:44.969> comes<01:16:45.929> here 01:16:46.220 --> 01:16:46.230 align:start position:0% the insight actually you know comes here 01:16:46.230 --> 01:16:49.669 align:start position:0% the insight actually you know comes here like<01:16:47.119> you<01:16:48.119> know<01:16:48.210> just<01:16:48.690> to<01:16:48.750> try<01:16:48.900> understand<01:16:49.440> how 01:16:49.669 --> 01:16:49.679 align:start position:0% like you know just to try understand how 01:16:49.679 --> 01:16:51.439 align:start position:0% like you know just to try understand how the<01:16:49.739> state<01:16:50.070> evolves<01:16:50.369> and<01:16:50.699> this<01:16:51.059> is<01:16:51.210> where<01:16:51.360> it 01:16:51.439 --> 01:16:51.449 align:start position:0% the state evolves and this is where it 01:16:51.449 --> 01:16:56.990 align:start position:0% the state evolves and this is where it all<01:16:51.539> happens<01:16:54.260> ok<01:16:55.260> and<01:16:55.469> so<01:16:55.829> I've<01:16:56.579> kind<01:16:56.880> of 01:16:56.990 --> 01:16:57.000 align:start position:0% all happens ok and so I've kind of 01:16:57.000 --> 01:17:00.890 align:start position:0% all happens ok and so I've kind of subdivided<01:16:58.429> the<01:16:59.429> modules<01:16:59.969> into<01:17:00.179> into<01:17:00.659> three 01:17:00.890 --> 01:17:00.900 align:start position:0% subdivided the modules into into three 01:17:00.900 --> 01:17:04.100 align:start position:0% subdivided the modules into into three columns<01:17:01.320> so<01:17:01.440> you<01:17:01.619> have<01:17:01.889> the<01:17:02.269> the<01:17:03.269> scaffolding 01:17:04.100 --> 01:17:04.110 align:start position:0% columns so you have the the scaffolding 01:17:04.110 --> 01:17:05.450 align:start position:0% columns so you have the the scaffolding which<01:17:04.320> is<01:17:04.469> development<01:17:04.860> pretty<01:17:05.099> much<01:17:05.250> for<01:17:05.429> all 01:17:05.450 --> 01:17:05.460 align:start position:0% which is development pretty much for all 01:17:05.460 --> 01:17:09.580 align:start position:0% which is development pretty much for all block<01:17:05.760> chains<01:17:06.030> time<01:17:07.010> routes<01:17:08.010> and<01:17:08.400> randomness 01:17:09.580 --> 01:17:09.590 align:start position:0% block chains time routes and randomness 01:17:09.590 --> 01:17:14.060 align:start position:0% block chains time routes and randomness and<01:17:10.590> then<01:17:11.510> you<01:17:12.510> have<01:17:12.750> the<01:17:13.019> the<01:17:13.289> registry<01:17:13.860> which 01:17:14.060 --> 01:17:14.070 align:start position:0% and then you have the the registry which 01:17:14.070 --> 01:17:18.259 align:start position:0% and then you have the the registry which is<01:17:14.099> which<01:17:14.940> is<01:17:15.090> the<01:17:15.480> one<01:17:16.050> unique<01:17:16.349> part<01:17:16.909> to<01:17:17.909> proof 01:17:18.259 --> 01:17:18.269 align:start position:0% is which is the one unique part to proof 01:17:18.269 --> 01:17:21.229 align:start position:0% is which is the one unique part to proof of<01:17:18.389> stake<01:17:18.920> so<01:17:19.920> you<01:17:20.610> know<01:17:20.730> you<01:17:20.820> have<01:17:21.000> things 01:17:21.229 --> 01:17:21.239 align:start position:0% of stake so you know you have things 01:17:21.239 --> 01:17:27.080 align:start position:0% of stake so you know you have things like<01:17:21.360> deposits<01:17:22.170> and<01:17:22.469> exits<01:17:24.380> and<01:17:25.730> then<01:17:26.730> you 01:17:27.080 --> 01:17:27.090 align:start position:0% like deposits and exits and then you 01:17:27.090 --> 01:17:31.370 align:start position:0% like deposits and exits and then you have<01:17:27.650> a<01:17:28.940> final<01:17:29.940> bit<01:17:30.090> which<01:17:30.329> is<01:17:30.570> you<01:17:31.289> know 01:17:31.370 --> 01:17:31.380 align:start position:0% have a final bit which is you know 01:17:31.380 --> 01:17:33.890 align:start position:0% have a final bit which is you know technically<01:17:31.889> you<01:17:32.610> know<01:17:32.670> optional<01:17:33.179> but<01:17:33.360> it's 01:17:33.890 --> 01:17:33.900 align:start position:0% technically you know optional but it's 01:17:33.900 --> 01:17:37.220 align:start position:0% technically you know optional but it's still<01:17:34.349> extremely<01:17:34.590> powerful<01:17:35.340> related<01:17:35.880> to<01:17:36.230> to 01:17:37.220 --> 01:17:37.230 align:start position:0% still extremely powerful related to to 01:17:37.230 --> 01:17:40.399 align:start position:0% still extremely powerful related to to finalization<01:17:38.070> and<01:17:38.750> cross<01:17:39.750> links<01:17:40.110> if<01:17:40.260> you<01:17:40.289> want 01:17:40.399 --> 01:17:40.409 align:start position:0% finalization and cross links if you want 01:17:40.409 --> 01:17:50.479 align:start position:0% finalization and cross links if you want sharding<01:17:41.039> and<01:17:42.980> and<01:17:44.179> also<01:17:47.659> ghost<01:17:49.489> 3d 01:17:50.479 --> 01:17:50.489 align:start position:0% sharding and and also ghost 3d 01:17:50.489 --> 01:17:53.839 align:start position:0% sharding and and also ghost 3d attestations<01:17:52.309> okay<01:17:53.309> so<01:17:53.369> let's<01:17:53.639> go<01:17:53.730> through 01:17:53.839 --> 01:17:53.849 align:start position:0% attestations okay so let's go through 01:17:53.849 --> 01:17:57.140 align:start position:0% attestations okay so let's go through these<01:17:54.090> components<01:17:54.510> one<01:17:54.630> by<01:17:54.780> one<01:17:54.960> so<01:17:55.760> blue<01:17:56.760> is 01:17:57.140 --> 01:17:57.150 align:start position:0% these components one by one so blue is 01:17:57.150 --> 01:18:04.419 align:start position:0% these components one by one so blue is the<01:17:57.809> state<01:17:58.309> green<01:17:59.309> is<01:17:59.840> the<01:18:00.980> the<01:18:01.980> blocks<01:18:02.190> so 01:18:04.419 --> 01:18:04.429 align:start position:0% the state green is the the blocks so 01:18:04.429 --> 01:18:09.919 align:start position:0% the state green is the the blocks so what<01:18:05.429> happens<01:18:05.820> at<01:18:06.090> every<01:18:06.829> every<01:18:08.690> every<01:18:09.690> slot 01:18:09.919 --> 01:18:09.929 align:start position:0% what happens at every every every slot 01:18:09.929 --> 01:18:12.979 align:start position:0% what happens at every every every slot the<01:18:10.769> slot<01:18:10.800> the<01:18:11.670> slot<01:18:11.699> number<01:18:12.269> will<01:18:12.510> increment 01:18:12.979 --> 01:18:12.989 align:start position:0% the slot the slot number will increment 01:18:12.989 --> 01:18:13.290 align:start position:0% the slot the slot number will increment so 01:18:13.290 --> 01:18:13.300 align:start position:0% so 01:18:13.300 --> 01:18:15.660 align:start position:0% so you<01:18:13.390> you<01:18:13.900> you<01:18:14.110> read<01:18:14.350> the<01:18:14.560> slot<01:18:14.920> value<01:18:15.280> and<01:18:15.430> you 01:18:15.660 --> 01:18:15.670 align:start position:0% you you you read the slot value and you 01:18:15.670 --> 01:18:17.280 align:start position:0% you you you read the slot value and you just<01:18:15.880> increment<01:18:16.090> it<01:18:16.420> nothing 01:18:17.280 --> 01:18:17.290 align:start position:0% just increment it nothing 01:18:17.290 --> 01:18:19.710 align:start position:0% just increment it nothing nothing<01:18:17.620> complicated<01:18:18.190> here<01:18:18.640> and<01:18:18.790> the<01:18:19.240> Genesis 01:18:19.710 --> 01:18:19.720 align:start position:0% nothing complicated here and the Genesis 01:18:19.720 --> 01:18:23.250 align:start position:0% nothing complicated here and the Genesis time<01:18:19.960> and<01:18:20.290> the<01:18:20.380> fork<01:18:20.680> don't<01:18:20.950> change<01:18:21.810> I<01:18:22.810> mean 01:18:23.250 --> 01:18:23.260 align:start position:0% time and the fork don't change I mean 01:18:23.260 --> 01:18:24.980 align:start position:0% time and the fork don't change I mean the<01:18:23.380> fork<01:18:23.650> will<01:18:23.920> change<01:18:24.220> kind<01:18:24.490> of<01:18:24.580> at<01:18:24.730> the 01:18:24.980 --> 01:18:24.990 align:start position:0% the fork will change kind of at the 01:18:24.990 --> 01:18:27.150 align:start position:0% the fork will change kind of at the social<01:18:25.990> consensus<01:18:26.440> layer<01:18:26.620> but<01:18:26.830> it<01:18:26.890> doesn't 01:18:27.150 --> 01:18:27.160 align:start position:0% social consensus layer but it doesn't 01:18:27.160 --> 01:18:29.490 align:start position:0% social consensus layer but it doesn't change<01:18:27.220> within<01:18:27.640> the<01:18:28.110> state<01:18:29.110> transition 01:18:29.490 --> 01:18:29.500 align:start position:0% change within the state transition 01:18:29.500 --> 01:18:35.370 align:start position:0% change within the state transition function<01:18:31.410> then<01:18:32.410> you<01:18:32.620> have<01:18:33.840> kind<01:18:34.840> of<01:18:34.900> the<01:18:35.080> the 01:18:35.370 --> 01:18:35.380 align:start position:0% function then you have kind of the the 01:18:35.380 --> 01:18:37.890 align:start position:0% function then you have kind of the the header<01:18:35.620> part<01:18:35.920> of<01:18:36.190> the<01:18:36.280> block<01:18:36.490> in<01:18:36.760> green<01:18:37.090> which 01:18:37.890 --> 01:18:37.900 align:start position:0% header part of the block in green which 01:18:37.900 --> 01:18:41.790 align:start position:0% header part of the block in green which gets<01:18:38.910> saved<01:18:39.910> into<01:18:40.200> into<01:18:41.200> a<01:18:41.230> data<01:18:41.440> structure 01:18:41.790 --> 01:18:41.800 align:start position:0% gets saved into into a data structure 01:18:41.800 --> 01:18:47.580 align:start position:0% gets saved into into a data structure and<01:18:42.190> also<01:18:44.100> gets<01:18:45.100> America<01:18:46.030> lies<01:18:46.330> into<01:18:46.600> into 01:18:47.580 --> 01:18:47.590 align:start position:0% and also gets America lies into into 01:18:47.590 --> 01:18:49.380 align:start position:0% and also gets America lies into into block<01:18:47.800> routes<01:18:48.070> so<01:18:48.220> the<01:18:48.370> the<01:18:48.700> beacon<01:18:49.000> chain<01:18:49.240> is 01:18:49.380 --> 01:18:49.390 align:start position:0% block routes so the the beacon chain is 01:18:49.390 --> 01:18:52.440 align:start position:0% block routes so the the beacon chain is kind<01:18:49.540> of<01:18:49.570> aware<01:18:49.990> of<01:18:50.530> its<01:18:50.860> of<01:18:51.640> its<01:18:51.880> block<01:18:52.180> routes 01:18:52.440 --> 01:18:52.450 align:start position:0% kind of aware of its of its block routes 01:18:52.450 --> 01:18:55.800 align:start position:0% kind of aware of its of its block routes and<01:18:53.290> in<01:18:53.590> the<01:18:53.710> past<01:18:54.030> the<01:18:55.030> recent<01:18:55.390> block<01:18:55.570> routes 01:18:55.800 --> 01:18:55.810 align:start position:0% and in the past the recent block routes 01:18:55.810 --> 01:19:01.410 align:start position:0% and in the past the recent block routes and<01:18:56.280> also<01:18:57.280> recent<01:18:57.700> state<01:18:57.910> routes<01:18:59.250> and<01:19:00.250> it<01:19:00.910> will 01:19:01.410 --> 01:19:01.420 align:start position:0% and also recent state routes and it will 01:19:01.420 --> 01:19:06.570 align:start position:0% and also recent state routes and it will basically<01:19:02.350> come<01:19:03.840> build<01:19:04.840> from<01:19:05.200> these<01:19:05.580> so 01:19:06.570 --> 01:19:06.580 align:start position:0% basically come build from these so 01:19:06.580 --> 01:19:11.990 align:start position:0% basically come build from these so called<01:19:06.850> historical<01:19:07.450> routes<01:19:08.190> so<01:19:09.190> this<01:19:09.550> is<01:19:09.760> a 01:19:11.990 --> 01:19:12.000 align:start position:0% called historical routes so this is a 01:19:12.000 --> 01:19:14.520 align:start position:0% called historical routes so this is a historical<01:19:13.000> accumulator<01:19:13.660> which<01:19:13.960> allows<01:19:14.260> you 01:19:14.520 --> 01:19:14.530 align:start position:0% historical accumulator which allows you 01:19:14.530 --> 01:19:17.700 align:start position:0% historical accumulator which allows you to<01:19:14.790> go<01:19:15.790> back<01:19:16.000> in<01:19:16.180> time<01:19:16.390> arbitrarily<01:19:17.050> far<01:19:17.410> and 01:19:17.700 --> 01:19:17.710 align:start position:0% to go back in time arbitrarily far and 01:19:17.710 --> 01:19:22.020 align:start position:0% to go back in time arbitrarily far and provide<01:19:18.610> a<01:19:18.640> witness<01:19:19.470> to<01:19:20.470> any<01:19:20.890> part<01:19:21.550> of<01:19:21.820> the 01:19:22.020 --> 01:19:22.030 align:start position:0% provide a witness to any part of the 01:19:22.030 --> 01:19:25.590 align:start position:0% provide a witness to any part of the state<01:19:22.270> or<01:19:22.540> any<01:19:22.900> part<01:19:23.440> of<01:19:23.680> a<01:19:23.800> block<01:19:24.070> and<01:19:24.480> one<01:19:25.480> of 01:19:25.590 --> 01:19:25.600 align:start position:0% state or any part of a block and one of 01:19:25.600 --> 01:19:27.810 align:start position:0% state or any part of a block and one of the<01:19:25.720> cool<01:19:25.960> properties<01:19:26.380> of<01:19:26.560> this<01:19:26.820> accumulator 01:19:27.810 --> 01:19:27.820 align:start position:0% the cool properties of this accumulator 01:19:27.820 --> 01:19:30.390 align:start position:0% the cool properties of this accumulator is<01:19:28.090> that<01:19:28.270> the<01:19:29.110> witnesses<01:19:29.620> don't<01:19:29.800> change<01:19:30.130> over 01:19:30.390 --> 01:19:30.400 align:start position:0% is that the witnesses don't change over 01:19:30.400 --> 01:19:35.370 align:start position:0% is that the witnesses don't change over time<01:19:30.780> so<01:19:31.780> if<01:19:31.960> you<01:19:31.990> have<01:19:33.540> you<01:19:34.540> know<01:19:34.660> a<01:19:34.930> statement 01:19:35.370 --> 01:19:35.380 align:start position:0% time so if you have you know a statement 01:19:35.380 --> 01:19:38.480 align:start position:0% time so if you have you know a statement saying<01:19:35.800> I<01:19:36.250> know<01:19:36.730> that<01:19:37.210> you<01:19:37.510> know<01:19:37.600> its<01:19:37.810> lot 01:19:38.480 --> 01:19:38.490 align:start position:0% saying I know that you know its lot 01:19:38.490 --> 01:19:41.610 align:start position:0% saying I know that you know its lot 1,000<01:19:39.490> the<01:19:40.180> the<01:19:40.480> balance<01:19:40.630> of<01:19:40.930> this<01:19:41.110> validator 01:19:41.610 --> 01:19:41.620 align:start position:0% 1,000 the the balance of this validator 01:19:41.620 --> 01:19:44.880 align:start position:0% 1,000 the the balance of this validator was<01:19:42.010> this<01:19:42.790> amount<01:19:43.210> well<01:19:43.840> whatever<01:19:44.320> proof<01:19:44.680> you 01:19:44.880 --> 01:19:44.890 align:start position:0% was this amount well whatever proof you 01:19:44.890 --> 01:19:47.810 align:start position:0% was this amount well whatever proof you had<01:19:45.130> the<01:19:45.550> miracle<01:19:46.060> path<01:19:46.420> will<01:19:46.660> remain<01:19:46.930> valid 01:19:47.810 --> 01:19:47.820 align:start position:0% had the miracle path will remain valid 01:19:47.820 --> 01:19:52.860 align:start position:0% had the miracle path will remain valid forever<01:19:50.640> and<01:19:51.640> then<01:19:51.940> you<01:19:52.060> have<01:19:52.210> the<01:19:52.360> randomness 01:19:52.860 --> 01:19:52.870 align:start position:0% forever and then you have the randomness 01:19:52.870 --> 01:19:55.820 align:start position:0% forever and then you have the randomness which<01:19:53.710> was<01:19:53.860> explained<01:19:54.220> by<01:19:54.340> dank<01:19:54.550> hat<01:19:54.760> and 01:19:55.820 --> 01:19:55.830 align:start position:0% which was explained by dank hat and 01:19:55.830 --> 01:19:57.990 align:start position:0% which was explained by dank hat and these<01:19:56.830> is<01:19:57.040> the<01:19:57.160> basic<01:19:57.460> this<01:19:57.640> is<01:19:57.700> the<01:19:57.820> basic 01:19:57.990 --> 01:19:58.000 align:start position:0% these is the basic this is the basic 01:19:58.000 --> 01:20:01.470 align:start position:0% these is the basic this is the basic scaffolding<01:19:58.750> and<01:19:59.310> the<01:20:00.310> way<01:20:00.850> that<01:20:01.030> the<01:20:01.210> the 01:20:01.470 --> 01:20:01.480 align:start position:0% scaffolding and the way that the the 01:20:01.480 --> 01:20:03.030 align:start position:0% scaffolding and the way that the the randomness<01:20:01.960> moves<01:20:02.230> forward<01:20:02.620> is<01:20:02.710> that<01:20:02.830> in 01:20:03.030 --> 01:20:03.040 align:start position:0% randomness moves forward is that in 01:20:03.040 --> 01:20:07.800 align:start position:0% randomness moves forward is that in every<01:20:03.490> every<01:20:04.030> block<01:20:04.270> the<01:20:04.840> green<01:20:05.080> part<01:20:05.790> you<01:20:06.810> XOR 01:20:07.800 --> 01:20:07.810 align:start position:0% every every block the green part you XOR 01:20:07.810 --> 01:20:11.640 align:start position:0% every every block the green part you XOR in<01:20:08.050> the<01:20:08.710> reveal<01:20:09.100> into<01:20:09.820> the<01:20:09.970> Randall<01:20:10.390> mix<01:20:10.650> so 01:20:11.640 --> 01:20:11.650 align:start position:0% in the reveal into the Randall mix so 01:20:11.650 --> 01:20:13.860 align:start position:0% in the reveal into the Randall mix so the<01:20:12.250> random<01:20:12.430> makes<01:20:12.820> just<01:20:13.060> keep<01:20:13.330> keeps<01:20:13.660> on 01:20:13.860 --> 01:20:13.870 align:start position:0% the random makes just keep keeps on 01:20:13.870 --> 01:20:16.440 align:start position:0% the random makes just keep keeps on mixing<01:20:14.410> in<01:20:14.560> entropy<01:20:14.890> and<01:20:15.220> and<01:20:15.880> this<01:20:16.090> entropy 01:20:16.440 --> 01:20:16.450 align:start position:0% mixing in entropy and and this entropy 01:20:16.450 --> 01:20:19.440 align:start position:0% mixing in entropy and and this entropy is<01:20:16.750> kept<01:20:17.110> in<01:20:17.680> the<01:20:17.980> state<01:20:18.220> and<01:20:18.520> it<01:20:19.000> is<01:20:19.120> it 01:20:19.440 --> 01:20:19.450 align:start position:0% is kept in the state and it is it 01:20:19.450 --> 01:20:25.169 align:start position:0% is kept in the state and it is it sampled<01:20:20.110> every<01:20:20.440> epoch<01:20:20.800> to<01:20:21.400> do<01:20:21.580> shuffling 01:20:25.169 --> 01:20:25.179 align:start position:0% 01:20:25.179 --> 01:20:28.830 align:start position:0% okay<01:20:25.570> then<01:20:26.080> we<01:20:26.230> have<01:20:26.440> the<01:20:26.710> the<01:20:27.159> registry<01:20:27.840> with 01:20:28.830 --> 01:20:28.840 align:start position:0% okay then we have the the registry with 01:20:28.840 --> 01:20:32.520 align:start position:0% okay then we have the the registry with the<01:20:29.020> validators<01:20:29.590> and<01:20:31.140> one<01:20:32.140> of<01:20:32.230> the<01:20:32.350> things 01:20:32.520 --> 01:20:32.530 align:start position:0% the validators and one of the things 01:20:32.530 --> 01:20:34.470 align:start position:0% the validators and one of the things that<01:20:32.679> we've<01:20:32.800> done<01:20:32.830> here<01:20:33.280> as<01:20:33.940> an<01:20:34.120> optimization 01:20:34.470 --> 01:20:34.480 align:start position:0% that we've done here as an optimization 01:20:34.480 --> 01:20:39.780 align:start position:0% that we've done here as an optimization is<01:20:35.050> we've<01:20:35.739> decoupled<01:20:36.580> the<01:20:38.190> the<01:20:39.190> Val<01:20:39.370> the 01:20:39.780 --> 01:20:39.790 align:start position:0% is we've decoupled the the Val the 01:20:39.790 --> 01:20:42.180 align:start position:0% is we've decoupled the the Val the balances<01:20:40.510> from<01:20:40.750> from<01:20:41.199> the<01:20:41.290> rest<01:20:41.440> of<01:20:41.679> the<01:20:41.890> of 01:20:42.180 --> 01:20:42.190 align:start position:0% balances from from the rest of the of 01:20:42.190 --> 01:20:46.800 align:start position:0% balances from from the rest of the of the<01:20:44.040> the<01:20:45.040> validated<01:20:45.580> fields<01:20:45.940> and<01:20:46.120> the<01:20:46.480> reason 01:20:46.800 --> 01:20:46.810 align:start position:0% the the validated fields and the reason 01:20:46.810 --> 01:20:49.770 align:start position:0% the the validated fields and the reason is<01:20:46.960> that<01:20:47.190> the<01:20:48.190> validator<01:20:48.610> fields<01:20:49.150> will<01:20:49.360> change 01:20:49.770 --> 01:20:49.780 align:start position:0% is that the validator fields will change 01:20:49.780 --> 01:20:52.200 align:start position:0% is that the validator fields will change very<01:20:50.140> infrequently<01:20:50.710> whereas<01:20:51.520> the<01:20:51.730> balances 01:20:52.200 --> 01:20:52.210 align:start position:0% very infrequently whereas the balances 01:20:52.210 --> 01:20:55.470 align:start position:0% very infrequently whereas the balances will<01:20:52.449> change<01:20:53.070> very<01:20:54.070> frequently<01:20:54.280> so<01:20:54.640> there's<01:20:55.390> a 01:20:55.470 --> 01:20:55.480 align:start position:0% will change very frequently so there's a 01:20:55.480 --> 01:21:01.950 align:start position:0% will change very frequently so there's a high<01:20:56.080> overhead<01:20:57.040> to<01:20:58.170> constantly<01:20:59.170> be<01:21:00.960> mark 01:21:01.950 --> 01:21:01.960 align:start position:0% high overhead to constantly be mark 01:21:01.960 --> 01:21:04.350 align:start position:0% high overhead to constantly be mark realizing<01:21:02.469> what<01:21:02.679> what<01:21:02.980> change<01:21:03.250> is<01:21:03.429> fast<01:21:04.030> and 01:21:04.350 --> 01:21:04.360 align:start position:0% realizing what what change is fast and 01:21:04.360 --> 01:21:07.229 align:start position:0% realizing what what change is fast and so<01:21:04.810> we<01:21:05.080> want<01:21:05.230> to<01:21:05.320> segregate<01:21:05.730> in<01:21:06.730> one<01:21:07.000> place 01:21:07.229 --> 01:21:07.239 align:start position:0% so we want to segregate in one place 01:21:07.239 --> 01:21:11.880 align:start position:0% so we want to segregate in one place everything<01:21:07.810> that<01:21:07.960> changes<01:21:08.350> fast<01:21:08.969> and<01:21:10.890> this 01:21:11.880 --> 01:21:11.890 align:start position:0% everything that changes fast and this 01:21:11.890 --> 01:21:19.260 align:start position:0% everything that changes fast and this was<01:21:12.070> covered<01:21:12.250> by<01:21:12.489> Yahweh<01:21:14.070> so<01:21:15.070> in<01:21:15.790> the<01:21:18.270> let's 01:21:19.260 --> 01:21:19.270 align:start position:0% was covered by Yahweh so in the let's 01:21:19.270 --> 01:21:22.290 align:start position:0% was covered by Yahweh so in the let's have<01:21:19.390> a<01:21:19.560> quick<01:21:20.560> deep<01:21:20.830> dive<01:21:21.070> as<01:21:21.250> to<01:21:21.400> what<01:21:21.610> was 01:21:22.290 --> 01:21:22.300 align:start position:0% have a quick deep dive as to what was 01:21:22.300 --> 01:21:24.090 align:start position:0% have a quick deep dive as to what was inside<01:21:22.750> these<01:21:22.929> validators<01:21:23.530> so<01:21:23.710> the 01:21:24.090 --> 01:21:24.100 align:start position:0% inside these validators so the 01:21:24.100 --> 01:21:25.830 align:start position:0% inside these validators so the validators<01:21:24.610> is<01:21:24.760> a<01:21:24.790> list<01:21:25.120> of<01:21:25.360> valid<01:21:25.600> data 01:21:25.830 --> 01:21:25.840 align:start position:0% validators is a list of valid data 01:21:25.840 --> 01:21:28.260 align:start position:0% validators is a list of valid data objects<01:21:26.440> this<01:21:26.920> is<01:21:26.980> what<01:21:27.250> the<01:21:27.370> validator 01:21:28.260 --> 01:21:28.270 align:start position:0% objects this is what the validator 01:21:28.270 --> 01:21:31.439 align:start position:0% objects this is what the validator object<01:21:28.659> looks<01:21:29.080> like<01:21:29.260> it<01:21:29.890> has<01:21:30.159> the<01:21:30.850> the<01:21:31.090> public 01:21:31.439 --> 01:21:31.449 align:start position:0% object looks like it has the the public 01:21:31.449 --> 01:21:34.200 align:start position:0% object looks like it has the the public key<01:21:31.659> as<01:21:31.810> you'd<01:21:31.960> expect<01:21:32.790> this<01:21:33.790> is<01:21:33.940> kind<01:21:34.150> of 01:21:34.200 --> 01:21:34.210 align:start position:0% key as you'd expect this is kind of 01:21:34.210 --> 01:21:38.280 align:start position:0% key as you'd expect this is kind of interesting<01:21:34.719> it's<01:21:35.580> the<01:21:36.580> hash<01:21:36.820> of<01:21:37.290> another 01:21:38.280 --> 01:21:38.290 align:start position:0% interesting it's the hash of another 01:21:38.290 --> 01:21:40.860 align:start position:0% interesting it's the hash of another public<01:21:38.530> key<01:21:38.890> so<01:21:39.400> this<01:21:39.610> other<01:21:39.909> public<01:21:40.480> key<01:21:40.690> is 01:21:40.860 --> 01:21:40.870 align:start position:0% public key so this other public key is 01:21:40.870 --> 01:21:43.890 align:start position:0% public key so this other public key is meant<01:21:41.080> to<01:21:41.260> be<01:21:41.429> your<01:21:42.429> with<01:21:42.640> withdraw<01:21:43.300> key<01:21:43.690> that 01:21:43.890 --> 01:21:43.900 align:start position:0% meant to be your with withdraw key that 01:21:43.900 --> 01:21:46.200 align:start position:0% meant to be your with withdraw key that you<01:21:43.989> keep<01:21:44.230> in<01:21:44.380> cold<01:21:44.620> storage<01:21:45.040> so<01:21:45.670> you<01:21:45.699> as<01:21:46.150> a 01:21:46.200 --> 01:21:46.210 align:start position:0% you keep in cold storage so you as a 01:21:46.210 --> 01:21:48.660 align:start position:0% you keep in cold storage so you as a validator<01:21:46.750> you<01:21:46.960> have<01:21:47.170> two<01:21:48.070> keys<01:21:48.310> you<01:21:48.460> kind<01:21:48.610> of 01:21:48.660 --> 01:21:48.670 align:start position:0% validator you have two keys you kind of 01:21:48.670 --> 01:21:50.669 align:start position:0% validator you have two keys you kind of have<01:21:48.790> a<01:21:48.820> hot<01:21:49.120> one<01:21:49.360> that<01:21:49.570> you<01:21:49.659> use<01:21:49.929> on<01:21:50.080> the<01:21:50.110> on<01:21:50.590> a 01:21:50.669 --> 01:21:50.679 align:start position:0% have a hot one that you use on the on a 01:21:50.679 --> 01:21:52.200 align:start position:0% have a hot one that you use on the on a day<01:21:50.890> to<01:21:50.949> day<01:21:51.070> basis<01:21:51.640> to<01:21:51.909> sign<01:21:52.090> your 01:21:52.200 --> 01:21:52.210 align:start position:0% day to day basis to sign your 01:21:52.210 --> 01:21:55.560 align:start position:0% day to day basis to sign your attestation<01:21:52.600> and<01:21:53.130> then<01:21:54.130> you<01:21:54.219> have<01:21:54.400> a<01:21:54.790> cold<01:21:55.360> one 01:21:55.560 --> 01:21:55.570 align:start position:0% attestation and then you have a cold one 01:21:55.570 --> 01:21:56.850 align:start position:0% attestation and then you have a cold one which<01:21:55.750> you<01:21:55.900> use<01:21:56.080> for<01:21:56.110> withdrawals<01:21:56.650> and 01:21:56.850 --> 01:21:56.860 align:start position:0% which you use for withdrawals and 01:21:56.860 --> 01:21:59.939 align:start position:0% which you use for withdrawals and transfers<01:21:57.340> and<01:21:57.610> so<01:21:58.239> if<01:21:58.480> you<01:21:59.110> validate<01:21:59.530> a<01:21:59.590> node 01:21:59.939 --> 01:21:59.949 align:start position:0% transfers and so if you validate a node 01:21:59.949 --> 01:22:02.580 align:start position:0% transfers and so if you validate a node which<01:22:00.219> is<01:22:00.250> online<01:22:00.489> gets<01:22:00.909> hacked<01:22:01.469> then<01:22:02.469> the 01:22:02.580 --> 01:22:02.590 align:start position:0% which is online gets hacked then the 01:22:02.590 --> 01:22:05.459 align:start position:0% which is online gets hacked then the hacker<01:22:02.770> cannot<01:22:03.190> steal<01:22:03.429> your<01:22:03.610> funds<01:22:04.290> so<01:22:05.290> that's 01:22:05.459 --> 01:22:05.469 align:start position:0% hacker cannot steal your funds so that's 01:22:05.469 --> 01:22:08.100 align:start position:0% hacker cannot steal your funds so that's why<01:22:05.679> it's<01:22:05.860> a<01:22:06.250> nice<01:22:06.790> level<01:22:07.000> of<01:22:07.420> protection<01:22:07.659> for 01:22:08.100 --> 01:22:08.110 align:start position:0% why it's a nice level of protection for 01:22:08.110 --> 01:22:16.080 align:start position:0% why it's a nice level of protection for you<01:22:13.380> okay<01:22:14.380> all<01:22:14.530> of<01:22:14.980> this<01:22:15.100> was<01:22:15.310> covered<01:22:15.610> by<01:22:15.760> bi 01:22:16.080 --> 01:22:16.090 align:start position:0% you okay all of this was covered by bi 01:22:16.090 --> 01:22:21.870 align:start position:0% you okay all of this was covered by bi shall<01:22:16.330> we<01:22:18.510> okay<01:22:19.510> so<01:22:19.860> which<01:22:20.860> parts<01:22:21.670> of<01:22:21.790> the 01:22:21.870 --> 01:22:21.880 align:start position:0% shall we okay so which parts of the 01:22:21.880 --> 01:22:24.419 align:start position:0% shall we okay so which parts of the systems<01:22:22.350> interact<01:22:23.350> with<01:22:23.590> the<01:22:23.710> registry<01:22:24.159> well 01:22:24.419 --> 01:22:24.429 align:start position:0% systems interact with the registry well 01:22:24.429 --> 01:22:30.149 align:start position:0% systems interact with the registry well we<01:22:25.060> have<01:22:26.310> the<01:22:27.310> deposits<01:22:27.820> so<01:22:28.600> every<01:22:29.530> block<01:22:29.830> in 01:22:30.149 --> 01:22:30.159 align:start position:0% we have the deposits so every block in 01:22:30.159 --> 01:22:32.910 align:start position:0% we have the deposits so every block in the<01:22:30.610> beacon<01:22:30.969> chain<01:22:31.300> will<01:22:31.659> contain<01:22:32.380> a<01:22:32.440> list<01:22:32.739> of 01:22:32.910 --> 01:22:32.920 align:start position:0% the beacon chain will contain a list of 01:22:32.920 --> 01:22:35.280 align:start position:0% the beacon chain will contain a list of deposits<01:22:33.429> here<01:22:33.730> and<01:22:33.909> these<01:22:34.570> deposits<01:22:35.110> will 01:22:35.280 --> 01:22:35.290 align:start position:0% deposits here and these deposits will 01:22:35.290 --> 01:22:39.000 align:start position:0% deposits here and these deposits will get<01:22:35.409> processed<01:22:35.949> and<01:22:36.250> then<01:22:37.210> that<01:22:37.840> will<01:22:37.989> create 01:22:39.000 --> 01:22:39.010 align:start position:0% get processed and then that will create 01:22:39.010 --> 01:22:44.610 align:start position:0% get processed and then that will create validator<01:22:39.760> entries<01:22:40.300> in<01:22:40.600> the<01:22:41.470> registry<01:22:43.620> but 01:22:44.610 --> 01:22:44.620 align:start position:0% validator entries in the registry but 01:22:44.620 --> 01:22:46.830 align:start position:0% validator entries in the registry but then<01:22:44.860> the<01:22:45.100> beacon<01:22:45.400> chain<01:22:45.610> is<01:22:45.790> to<01:22:45.940> know<01:22:46.120> what<01:22:46.720> is 01:22:46.830 --> 01:22:46.840 align:start position:0% then the beacon chain is to know what is 01:22:46.840 --> 01:22:50.310 align:start position:0% then the beacon chain is to know what is a<01:22:46.870> valid<01:22:47.290> deposit<01:22:47.770> and<01:22:48.690> for<01:22:49.690> that<01:22:49.810> it<01:22:50.080> needs<01:22:50.140> to 01:22:50.310 --> 01:22:50.320 align:start position:0% a valid deposit and for that it needs to 01:22:50.320 --> 01:22:52.740 align:start position:0% a valid deposit and for that it needs to be<01:22:50.410> aware<01:22:50.770> of<01:22:50.830> the<01:22:51.100> f1<01:22:51.550> chain<01:22:51.850> so<01:22:52.540> how<01:22:52.690> does 01:22:52.740 --> 01:22:52.750 align:start position:0% be aware of the f1 chain so how does 01:22:52.750 --> 01:22:57.479 align:start position:0% be aware of the f1 chain so how does that<01:22:53.020> work<01:22:53.460> so<01:22:54.460> in<01:22:54.910> every<01:22:55.630> block<01:22:55.900> we<01:22:56.800> the<01:22:57.190> the 01:22:57.479 --> 01:22:57.489 align:start position:0% that work so in every block we the the 01:22:57.489 --> 01:23:01.229 align:start position:0% that work so in every block we the the block<01:22:57.700> proposal<01:22:58.210> will<01:22:58.420> have<01:22:59.260> f1<01:22:59.830> data<01:23:00.430> saying 01:23:01.229 --> 01:23:01.239 align:start position:0% block proposal will have f1 data saying 01:23:01.239 --> 01:23:04.700 align:start position:0% block proposal will have f1 data saying you<01:23:01.900> know<01:23:01.989> this<01:23:02.230> this<01:23:02.950> is<01:23:03.130> what<01:23:03.280> I<01:23:03.310> think<01:23:03.730> is 01:23:04.700 --> 01:23:04.710 align:start position:0% you know this this is what I think is 01:23:04.710 --> 01:23:10.710 align:start position:0% you know this this is what I think is the<01:23:05.710> block<01:23:05.950> hash<01:23:06.250> of<01:23:07.980> of<01:23:09.040> f1<01:23:09.580> around<01:23:10.420> which<01:23:10.570> we 01:23:10.710 --> 01:23:10.720 align:start position:0% the block hash of of f1 around which we 01:23:10.720 --> 01:23:13.050 align:start position:0% the block hash of of f1 around which we need<01:23:10.840> to<01:23:10.960> come<01:23:11.110> to<01:23:11.230> consensus<01:23:11.800> and<01:23:12.580> so<01:23:12.820> this 01:23:13.050 --> 01:23:13.060 align:start position:0% need to come to consensus and so this 01:23:13.060 --> 01:23:16.200 align:start position:0% need to come to consensus and so this data<01:23:13.300> gets<01:23:14.230> stored<01:23:14.800> in<01:23:15.280> in<01:23:15.550> the<01:23:15.700> state<01:23:15.970> as 01:23:16.200 --> 01:23:16.210 align:start position:0% data gets stored in in the state as 01:23:16.210 --> 01:23:21.570 align:start position:0% data gets stored in in the state as votes<01:23:16.780> and<01:23:17.080> then<01:23:17.770> at<01:23:18.460> the<01:23:19.739> at<01:23:20.739> a<01:23:20.800> certain<01:23:21.280> epoch 01:23:21.570 --> 01:23:21.580 align:start position:0% votes and then at the at a certain epoch 01:23:21.580 --> 01:23:25.500 align:start position:0% votes and then at the at a certain epoch boundary<01:23:22.030> these<01:23:23.020> votes<01:23:23.260> are<01:23:23.440> counted<01:23:23.620> and<01:23:24.510> if 01:23:25.500 --> 01:23:25.510 align:start position:0% boundary these votes are counted and if 01:23:25.510 --> 01:23:29.310 align:start position:0% boundary these votes are counted and if there<01:23:25.750> is<01:23:26.190> a<01:23:27.300> majority<01:23:28.300> of<01:23:28.330> votes<01:23:28.660> for<01:23:29.290> a 01:23:29.310 --> 01:23:29.320 align:start position:0% there is a majority of votes for a 01:23:29.320 --> 01:23:32.990 align:start position:0% there is a majority of votes for a specific<01:23:29.620> f1<01:23:30.550> data<01:23:30.820> this<01:23:31.570> specific<01:23:32.260> f1<01:23:32.530> data 01:23:32.990 --> 01:23:33.000 align:start position:0% specific f1 data this specific f1 data 01:23:33.000 --> 01:23:37.140 align:start position:0% specific f1 data this specific f1 data is<01:23:34.000> updated<01:23:34.600> in<01:23:34.810> the<01:23:35.200> state<01:23:35.440> as<01:23:35.680> the<01:23:36.610> the 01:23:37.140 --> 01:23:37.150 align:start position:0% is updated in the state as the the 01:23:37.150 --> 01:23:43.020 align:start position:0% is updated in the state as the the latest<01:23:39.270> snapshot<01:23:40.270> of<01:23:40.750> f1<01:23:41.530> and<01:23:41.710> the<01:23:42.580> idea<01:23:42.820> here 01:23:43.020 --> 01:23:43.030 align:start position:0% latest snapshot of f1 and the idea here 01:23:43.030 --> 01:23:47.490 align:start position:0% latest snapshot of f1 and the idea here basic<01:23:43.420> basically<01:23:44.200> is<01:23:45.720> on<01:23:46.720> this<01:23:46.960> majority 01:23:47.490 --> 01:23:47.500 align:start position:0% basic basically is on this majority 01:23:47.500 --> 01:23:52.320 align:start position:0% basic basically is on this majority sampling<01:23:47.920> so<01:23:48.660> we<01:23:49.660> have<01:23:50.489> we<01:23:51.489> have<01:23:51.640> the<01:23:52.000> large 01:23:52.320 --> 01:23:52.330 align:start position:0% sampling so we have we have the large 01:23:52.330 --> 01:23:54.390 align:start position:0% sampling so we have we have the large number<01:23:52.660> of<01:23:52.690> validators<01:23:53.320> that's<01:23:53.530> a<01:23:53.620> million 01:23:54.390 --> 01:23:54.400 align:start position:0% number of validators that's a million 01:23:54.400 --> 01:23:56.340 align:start position:0% number of validators that's a million validators<01:23:55.060> we<01:23:55.600> have<01:23:55.780> this<01:23:55.900> honesty 01:23:56.340 --> 01:23:56.350 align:start position:0% validators we have this honesty 01:23:56.350 --> 01:23:59.070 align:start position:0% validators we have this honesty assumption<01:23:56.890> that<01:23:57.070> at<01:23:57.610> least<01:23:57.820> 2/3<01:23:58.420> of<01:23:58.660> the 01:23:59.070 --> 01:23:59.080 align:start position:0% assumption that at least 2/3 of the 01:23:59.080 --> 01:24:03.360 align:start position:0% assumption that at least 2/3 of the active<01:24:00.330> validators<01:24:01.330> are<01:24:01.540> honest<01:24:02.190> we're<01:24:03.190> going 01:24:03.360 --> 01:24:03.370 align:start position:0% active validators are honest we're going 01:24:03.370 --> 01:24:06.420 align:start position:0% active validators are honest we're going to<01:24:03.460> sample<01:24:03.700> a<01:24:04.180> thousand<01:24:05.110> of<01:24:05.200> them<01:24:05.380> and<01:24:05.590> and<01:24:06.280> the 01:24:06.420 --> 01:24:06.430 align:start position:0% to sample a thousand of them and and the 01:24:06.430 --> 01:24:10.290 align:start position:0% to sample a thousand of them and and the way<01:24:06.550> that<01:24:06.730> this<01:24:06.820> the<01:24:07.360> sampling<01:24:07.920> works<01:24:08.920> is<01:24:09.300> over 01:24:10.290 --> 01:24:10.300 align:start position:0% way that this the sampling works is over 01:24:10.300 --> 01:24:16.350 align:start position:0% way that this the sampling works is over a<01:24:10.440> thousand<01:24:11.730> sequential<01:24:12.730> slots<01:24:13.080> and<01:24:14.670> if<01:24:15.670> we<01:24:16.030> if 01:24:16.350 --> 01:24:16.360 align:start position:0% a thousand sequential slots and if we if 01:24:16.360 --> 01:24:18.450 align:start position:0% a thousand sequential slots and if we if this<01:24:16.540> randomness<01:24:16.960> is<01:24:17.230> good<01:24:17.410> enough<01:24:17.680> then<01:24:18.250> we 01:24:18.450 --> 01:24:18.460 align:start position:0% this randomness is good enough then we 01:24:18.460 --> 01:24:20.790 align:start position:0% this randomness is good enough then we know<01:24:18.910> if<01:24:19.090> high<01:24:19.270> probability<01:24:19.810> that<01:24:19.840> least<01:24:20.200> one 01:24:20.790 --> 01:24:20.800 align:start position:0% know if high probability that least one 01:24:20.800 --> 01:24:23.760 align:start position:0% know if high probability that least one half<01:24:21.100> of<01:24:21.370> the<01:24:21.910> f1<01:24:22.360> voting<01:24:23.050> committee<01:24:23.200> will<01:24:23.650> be 01:24:23.760 --> 01:24:23.770 align:start position:0% half of the f1 voting committee will be 01:24:23.770 --> 01:24:26.240 align:start position:0% half of the f1 voting committee will be honest<01:24:24.100> the<01:24:24.850> voting<01:24:25.150> committee<01:24:25.480> being<01:24:25.720> these 01:24:26.240 --> 01:24:26.250 align:start position:0% honest the voting committee being these 01:24:26.250 --> 01:24:32.490 align:start position:0% honest the voting committee being these 1000<01:24:27.780> block<01:24:28.780> proposes<01:24:29.320> and<01:24:30.450> and<01:24:31.470> so<01:24:32.470> that 01:24:32.490 --> 01:24:32.500 align:start position:0% 1000 block proposes and and so that 01:24:32.500 --> 01:24:36.660 align:start position:0% 1000 block proposes and and so that means<01:24:32.890> that<01:24:33.130> if<01:24:33.700> we<01:24:34.000> have<01:24:34.030> at<01:24:34.480> least<01:24:35.520> half<01:24:36.520> of 01:24:36.660 --> 01:24:36.670 align:start position:0% means that if we have at least half of 01:24:36.670 --> 01:24:40.020 align:start position:0% means that if we have at least half of the<01:24:36.820> votes<01:24:37.000> here<01:24:38.130> vote<01:24:39.130> for<01:24:39.370> a<01:24:39.400> given<01:24:39.730> piece<01:24:39.910> of 01:24:40.020 --> 01:24:40.030 align:start position:0% the votes here vote for a given piece of 01:24:40.030 --> 01:24:42.330 align:start position:0% the votes here vote for a given piece of data<01:24:40.180> then<01:24:40.510> that<01:24:40.690> piece<01:24:41.410> of<01:24:41.590> data<01:24:41.800> will<01:24:42.250> be 01:24:42.330 --> 01:24:42.340 align:start position:0% data then that piece of data will be 01:24:42.340 --> 01:24:44.610 align:start position:0% data then that piece of data will be representative<01:24:43.180> of<01:24:43.300> reality<01:24:43.840> representative 01:24:44.610 --> 01:24:44.620 align:start position:0% representative of reality representative 01:24:44.620 --> 01:24:48.360 align:start position:0% representative of reality representative of<01:24:45.090> f1<01:24:46.090> and<01:24:46.540> and<01:24:46.960> by<01:24:47.200> the<01:24:47.260> way<01:24:47.440> this<01:24:47.620> on<01:24:47.950> this 01:24:48.360 --> 01:24:48.370 align:start position:0% of f1 and and by the way this on this 01:24:48.370 --> 01:24:50.610 align:start position:0% of f1 and and by the way this on this majority<01:24:48.969> idea<01:24:49.330> is<01:24:49.480> reused<01:24:49.840> for<01:24:49.989> cross<01:24:50.200> Nexus 01:24:50.610 --> 01:24:50.620 align:start position:0% majority idea is reused for cross Nexus 01:24:50.620 --> 01:24:54.080 align:start position:0% majority idea is reused for cross Nexus as<01:24:51.010> well 01:24:54.080 --> 01:24:54.090 align:start position:0% 01:24:54.090 --> 01:25:00.270 align:start position:0% okay<01:24:55.560> so<01:24:56.820> now<01:24:57.820> I<01:24:57.850> guess<01:24:58.179> comes<01:24:58.600> the<01:24:59.100> the<01:25:00.100> more 01:25:00.270 --> 01:25:00.280 align:start position:0% okay so now I guess comes the the more 01:25:00.280 --> 01:25:03.810 align:start position:0% okay so now I guess comes the the more interesting<01:25:00.850> stuff<01:25:01.510> so<01:25:01.810> the<01:25:02.520> the<01:25:03.520> attestation 01:25:03.810 --> 01:25:03.820 align:start position:0% interesting stuff so the the attestation 01:25:03.820 --> 01:25:06.510 align:start position:0% interesting stuff so the the attestation this<01:25:04.510> is<01:25:04.659> the<01:25:04.810> work<01:25:05.199> that<01:25:05.469> the<01:25:05.800> validators 01:25:06.510 --> 01:25:06.520 align:start position:0% this is the work that the validators 01:25:06.520 --> 01:25:09.899 align:start position:0% this is the work that the validators have<01:25:06.699> to<01:25:06.850> do<01:25:07.170> so<01:25:08.170> what<01:25:09.010> is<01:25:09.159> inside<01:25:09.699> an 01:25:09.899 --> 01:25:09.909 align:start position:0% have to do so what is inside an 01:25:09.909 --> 01:25:13.200 align:start position:0% have to do so what is inside an attestation<01:25:11.219> so<01:25:12.219> this<01:25:12.489> is<01:25:12.640> kind<01:25:12.850> of<01:25:12.969> the 01:25:13.200 --> 01:25:13.210 align:start position:0% attestation so this is kind of the 01:25:13.210 --> 01:25:16.950 align:start position:0% attestation so this is kind of the header<01:25:13.900> of<01:25:14.260> the<01:25:14.320> attestation<01:25:15.210> it<01:25:16.210> has<01:25:16.570> a 01:25:16.950 --> 01:25:16.960 align:start position:0% header of the attestation it has a 01:25:16.960 --> 01:25:20.490 align:start position:0% header of the attestation it has a signature<01:25:17.860> and<01:25:18.840> here<01:25:19.840> it's<01:25:20.020> important<01:25:20.469> that 01:25:20.490 --> 01:25:20.500 align:start position:0% signature and here it's important that 01:25:20.500 --> 01:25:24.709 align:start position:0% signature and here it's important that we<01:25:20.710> have<01:25:20.860> the<01:25:21.010> BLS<01:25:21.460> because<01:25:22.210> we<01:25:22.420> have 01:25:24.709 --> 01:25:24.719 align:start position:0% 01:25:24.719 --> 01:25:28.410 align:start position:0% different<01:25:26.790> validators<01:25:27.790> all<01:25:27.969> part<01:25:28.239> of<01:25:28.300> the 01:25:28.410 --> 01:25:28.420 align:start position:0% different validators all part of the 01:25:28.420 --> 01:25:30.959 align:start position:0% different validators all part of the same<01:25:28.630> committee<01:25:28.989> that<01:25:29.770> will<01:25:29.949> be<01:25:30.400> signing<01:25:30.820> the 01:25:30.959 --> 01:25:30.969 align:start position:0% same committee that will be signing the 01:25:30.969 --> 01:25:33.600 align:start position:0% same committee that will be signing the same<01:25:31.270> attestation<01:25:31.780> and<01:25:32.219> the<01:25:33.219> way<01:25:33.340> that<01:25:33.520> the 01:25:33.600 --> 01:25:33.610 align:start position:0% same attestation and the way that the 01:25:33.610 --> 01:25:35.850 align:start position:0% same attestation and the way that the aggregation<01:25:34.000> works<01:25:34.449> is<01:25:34.750> that<01:25:35.469> we're<01:25:35.620> going<01:25:35.770> to 01:25:35.850 --> 01:25:35.860 align:start position:0% aggregation works is that we're going to 01:25:35.860 --> 01:25:38.790 align:start position:0% aggregation works is that we're going to specify<01:25:36.130> in<01:25:36.820> in<01:25:37.390> the<01:25:37.630> aggregation<01:25:38.140> bits<01:25:38.530> here 01:25:38.790 --> 01:25:38.800 align:start position:0% specify in in the aggregation bits here 01:25:38.800 --> 01:25:43.320 align:start position:0% specify in in the aggregation bits here which<01:25:39.900> validators<01:25:40.900> have<01:25:41.590> participated<01:25:42.400> in<01:25:43.120> a 01:25:43.320 --> 01:25:43.330 align:start position:0% which validators have participated in a 01:25:43.330 --> 01:25:45.930 align:start position:0% which validators have participated in a specific<01:25:43.510> aggregation<01:25:44.380> so<01:25:44.760> we<01:25:45.760> have<01:25:45.909> a 01:25:45.930 --> 01:25:45.940 align:start position:0% specific aggregation so we have a 01:25:45.940 --> 01:25:47.880 align:start position:0% specific aggregation so we have a committee<01:25:46.480> let's<01:25:46.929> say<01:25:47.110> of<01:25:47.320> a<01:25:47.350> thousand 01:25:47.880 --> 01:25:47.890 align:start position:0% committee let's say of a thousand 01:25:47.890 --> 01:25:51.270 align:start position:0% committee let's say of a thousand validators<01:25:48.659> they're<01:25:49.659> ordered<01:25:50.080> and<01:25:50.350> this<01:25:51.040> bit 01:25:51.270 --> 01:25:51.280 align:start position:0% validators they're ordered and this bit 01:25:51.280 --> 01:25:53.399 align:start position:0% validators they're ordered and this bit list<01:25:51.520> is<01:25:51.730> going<01:25:51.850> to<01:25:51.909> be<01:25:52.060> a<01:25:52.090> thousand<01:25:52.630> bits<01:25:52.810> each 01:25:53.399 --> 01:25:53.409 align:start position:0% list is going to be a thousand bits each 01:25:53.409 --> 01:25:58.260 align:start position:0% list is going to be a thousand bits each 0<01:25:53.949> 1<01:25:54.370> 1<01:25:55.090> indicating<01:25:55.690> that<01:25:56.040> the<01:25:57.040> a<01:25:57.489> validator 01:25:58.260 --> 01:25:58.270 align:start position:0% 0 1 1 indicating that the a validator 01:25:58.270 --> 01:26:00.660 align:start position:0% 0 1 1 indicating that the a validator was<01:25:58.690> included<01:25:59.409> in<01:25:59.590> the<01:25:59.770> aggregate<01:26:00.070> signature 01:26:00.660 --> 01:26:00.670 align:start position:0% was included in the aggregate signature 01:26:00.670 --> 01:26:04.620 align:start position:0% was included in the aggregate signature here<01:26:00.880> for<01:26:01.060> this<01:26:01.120> attestation<01:26:01.570> and<01:26:03.480> then<01:26:04.480> we 01:26:04.620 --> 01:26:04.630 align:start position:0% here for this attestation and then we 01:26:04.630 --> 01:26:06.000 align:start position:0% here for this attestation and then we have<01:26:04.780> the<01:26:04.900> data<01:26:05.050> which<01:26:05.440> is<01:26:05.560> going<01:26:05.710> to<01:26:05.770> be<01:26:05.860> the 01:26:06.000 --> 01:26:06.010 align:start position:0% have the data which is going to be the 01:26:06.010 --> 01:26:07.770 align:start position:0% have the data which is going to be the body<01:26:06.400> of<01:26:06.670> the<01:26:06.760> attestation<01:26:06.969> which<01:26:07.270> is<01:26:07.570> more 01:26:07.770 --> 01:26:07.780 align:start position:0% body of the attestation which is more 01:26:07.780 --> 01:26:10.260 align:start position:0% body of the attestation which is more interesting<01:26:08.550> and<01:26:09.550> it<01:26:09.670> basically<01:26:09.790> has<01:26:10.239> three 01:26:10.260 --> 01:26:10.270 align:start position:0% interesting and it basically has three 01:26:10.270 --> 01:26:13.620 align:start position:0% interesting and it basically has three parts<01:26:10.840> the<01:26:11.739> attestation<01:26:11.980> that<01:26:12.390> when<01:26:13.390> you<01:26:13.480> make 01:26:13.620 --> 01:26:13.630 align:start position:0% parts the attestation that when you make 01:26:13.630 --> 01:26:15.209 align:start position:0% parts the attestation that when you make an<01:26:13.780> attestation<01:26:14.020> as<01:26:14.500> a<01:26:14.530> validator<01:26:14.980> you're 01:26:15.209 --> 01:26:15.219 align:start position:0% an attestation as a validator you're 01:26:15.219 --> 01:26:18.600 align:start position:0% an attestation as a validator you're making<01:26:15.489> three<01:26:15.850> votes<01:26:16.690> all<01:26:17.260> in<01:26:17.650> one<01:26:17.860> go<01:26:18.070> and 01:26:18.600 --> 01:26:18.610 align:start position:0% making three votes all in one go and 01:26:18.610 --> 01:26:21.689 align:start position:0% making three votes all in one go and this<01:26:19.210> is<01:26:19.360> part<01:26:20.050> of<01:26:20.140> the<01:26:20.290> reason<01:26:20.440> why<01:26:20.800> this<01:26:21.520> is 01:26:21.689 --> 01:26:21.699 align:start position:0% this is part of the reason why this is 01:26:21.699 --> 01:26:23.910 align:start position:0% this is part of the reason why this is part<01:26:21.969> of<01:26:22.090> what<01:26:22.270> I<01:26:22.300> mean<01:26:22.540> by<01:26:22.920> harmoniously 01:26:23.910 --> 01:26:23.920 align:start position:0% part of what I mean by harmoniously 01:26:23.920 --> 01:26:28.140 align:start position:0% part of what I mean by harmoniously connecting<01:26:24.670> the<01:26:25.239> various<01:26:25.570> elements<01:26:26.940> this<01:26:27.940> is 01:26:28.140 --> 01:26:28.150 align:start position:0% connecting the various elements this is 01:26:28.150 --> 01:26:31.020 align:start position:0% connecting the various elements this is one<01:26:28.630> one<01:26:28.989> place<01:26:29.230> where<01:26:29.440> we've<01:26:29.650> done<01:26:29.800> it<01:26:30.030> so 01:26:31.020 --> 01:26:31.030 align:start position:0% one one place where we've done it so 01:26:31.030 --> 01:26:33.720 align:start position:0% one one place where we've done it so when<01:26:31.239> you<01:26:32.100> when<01:26:33.100> you<01:26:33.250> make<01:26:33.280> an<01:26:33.520> attestation 01:26:33.720 --> 01:26:33.730 align:start position:0% when you when you make an attestation 01:26:33.730 --> 01:26:40.080 align:start position:0% when you when you make an attestation you<01:26:34.239> you're<01:26:35.230> voting<01:26:35.710> for<01:26:36.090> a<01:26:37.090> a<01:26:37.750> past<01:26:39.090> beacon 01:26:40.080 --> 01:26:40.090 align:start position:0% you you're voting for a a past beacon 01:26:40.090 --> 01:26:42.570 align:start position:0% you you're voting for a a past beacon block<01:26:40.300> and<01:26:40.600> that's<01:26:41.320> going<01:26:41.500> to<01:26:41.620> count<01:26:42.010> towards 01:26:42.570 --> 01:26:42.580 align:start position:0% block and that's going to count towards 01:26:42.580 --> 01:26:46.020 align:start position:0% block and that's going to count towards the<01:26:43.360> focus<01:26:43.780> rule<01:26:44.050> LMD<01:26:44.530> ghost<01:26:44.770> but<01:26:45.580> at<01:26:45.699> the<01:26:45.820> same 01:26:46.020 --> 01:26:46.030 align:start position:0% the focus rule LMD ghost but at the same 01:26:46.030 --> 01:26:49.560 align:start position:0% the focus rule LMD ghost but at the same time<01:26:46.560> you're<01:26:47.560> making<01:26:47.949> a<01:26:48.130> finality<01:26:48.880> vote<01:26:49.300> and 01:26:49.560 --> 01:26:49.570 align:start position:0% time you're making a finality vote and 01:26:49.570 --> 01:26:51.810 align:start position:0% time you're making a finality vote and FFG<01:26:50.080> vote<01:26:50.290> and<01:26:50.560> so<01:26:51.159> you're<01:26:51.370> going<01:26:51.460> to<01:26:51.550> be<01:26:51.640> vote 01:26:51.810 --> 01:26:51.820 align:start position:0% FFG vote and so you're going to be vote 01:26:51.820 --> 01:26:53.640 align:start position:0% FFG vote and so you're going to be vote you're<01:26:52.270> going<01:26:52.420> to<01:26:52.510> be<01:26:52.600> voting<01:26:52.960> for<01:26:52.989> a<01:26:53.230> source 01:26:53.640 --> 01:26:53.650 align:start position:0% you're going to be voting for a source 01:26:53.650 --> 01:26:58.439 align:start position:0% you're going to be voting for a source target<01:26:54.429> pair<01:26:55.140> and<01:26:56.730> so<01:26:57.730> that's<01:26:57.940> going<01:26:58.060> to<01:26:58.179> lead 01:26:58.439 --> 01:26:58.449 align:start position:0% target pair and so that's going to lead 01:26:58.449 --> 01:27:02.399 align:start position:0% target pair and so that's going to lead to<01:26:58.679> justifications<01:26:59.679> and<01:26:59.980> finality<01:27:00.610> and<01:27:01.409> in 01:27:02.399 --> 01:27:02.409 align:start position:0% to justifications and finality and in 01:27:02.409 --> 01:27:05.459 align:start position:0% to justifications and finality and in addition<01:27:02.920> you're<01:27:03.429> voting<01:27:03.940> for<01:27:04.659> a<01:27:04.690> cross<01:27:05.230> link 01:27:05.459 --> 01:27:05.469 align:start position:0% addition you're voting for a cross link 01:27:05.469 --> 01:27:06.919 align:start position:0% addition you're voting for a cross link so<01:27:06.010> as<01:27:06.159> a 01:27:06.919 --> 01:27:06.929 align:start position:0% so as a 01:27:06.929 --> 01:27:10.160 align:start position:0% so as a you<01:27:07.560> assigned<01:27:07.980> to<01:27:08.190> a<01:27:08.250> specific<01:27:08.429> shot<01:27:09.170> you 01:27:10.160 --> 01:27:10.170 align:start position:0% you assigned to a specific shot you 01:27:10.170 --> 01:27:14.330 align:start position:0% you assigned to a specific shot you meant<01:27:10.350> to<01:27:10.760> download<01:27:11.760> the<01:27:12.650> piece<01:27:13.650> a<01:27:13.890> chunk<01:27:14.219> of 01:27:14.330 --> 01:27:14.340 align:start position:0% meant to download the piece a chunk of 01:27:14.340 --> 01:27:16.970 align:start position:0% meant to download the piece a chunk of the<01:27:14.460> short<01:27:14.730> run<01:27:15.600> it<01:27:15.750> validate<01:27:16.230> it<01:27:16.440> and<01:27:16.620> if<01:27:16.800> it's 01:27:16.970 --> 01:27:16.980 align:start position:0% the short run it validate it and if it's 01:27:16.980 --> 01:27:21.709 align:start position:0% the short run it validate it and if it's good<01:27:17.219> then<01:27:18.980> make<01:27:19.980> a<01:27:20.010> cross<01:27:20.340> link<01:27:20.580> so<01:27:20.760> vote<01:27:21.060> vote 01:27:21.709 --> 01:27:21.719 align:start position:0% good then make a cross link so vote vote 01:27:21.719 --> 01:27:29.060 align:start position:0% good then make a cross link so vote vote for<01:27:21.989> that<01:27:22.110> specific<01:27:22.620> chunk<01:27:23.190> of<01:27:23.370> shot<01:27:28.040> so<01:27:29.040> I 01:27:29.060 --> 01:27:29.070 align:start position:0% for that specific chunk of shot so I 01:27:29.070 --> 01:27:31.310 align:start position:0% for that specific chunk of shot so I mean<01:27:29.370> this<01:27:29.460> was<01:27:30.179> covered<01:27:30.449> by<01:27:30.570> Danny<01:27:30.780> basically 01:27:31.310 --> 01:27:31.320 align:start position:0% mean this was covered by Danny basically 01:27:31.320 --> 01:27:34.280 align:start position:0% mean this was covered by Danny basically the<01:27:31.500> the<01:27:31.830> the<01:27:32.130> in<01:27:32.400> the<01:27:32.880> what<01:27:33.810> is<01:27:33.929> a<01:27:33.960> checkpoint 01:27:34.280 --> 01:27:34.290 align:start position:0% the the the in the what is a checkpoint 01:27:34.290 --> 01:27:36.950 align:start position:0% the the the in the what is a checkpoint here<01:27:34.830> in<01:27:35.010> the<01:27:35.159> FFG<01:27:35.610> vote<01:27:35.820> is<01:27:36.300> nothing<01:27:36.750> more 01:27:36.950 --> 01:27:36.960 align:start position:0% here in the FFG vote is nothing more 01:27:36.960 --> 01:27:41.620 align:start position:0% here in the FFG vote is nothing more than<01:27:37.170> a<01:27:37.409> pair<01:27:37.860> of<01:27:37.890> an<01:27:38.219> epic<01:27:38.610> and<01:27:39.020> an<01:27:40.020> hash<01:27:40.380> and 01:27:41.620 --> 01:27:41.630 align:start position:0% than a pair of an epic and an hash and 01:27:41.630 --> 01:27:44.720 align:start position:0% than a pair of an epic and an hash and what<01:27:42.630> is<01:27:42.750> a<01:27:42.780> cross<01:27:43.080> link<01:27:43.350> well<01:27:44.070> the<01:27:44.219> cross<01:27:44.460> link 01:27:44.720 --> 01:27:44.730 align:start position:0% what is a cross link well the cross link 01:27:44.730 --> 01:27:48.649 align:start position:0% what is a cross link well the cross link is<01:27:44.969> a<01:27:45.380> small<01:27:46.380> segment<01:27:46.679> of<01:27:47.010> a<01:27:47.250> shot<01:27:47.489> so<01:27:48.270> how<01:27:48.600> do 01:27:48.649 --> 01:27:48.659 align:start position:0% is a small segment of a shot so how do 01:27:48.659 --> 01:27:50.300 align:start position:0% is a small segment of a shot so how do you<01:27:48.900> represent<01:27:49.230> that<01:27:49.679> well<01:27:49.920> you<01:27:50.040> need<01:27:50.190> the 01:27:50.300 --> 01:27:50.310 align:start position:0% you represent that well you need the 01:27:50.310 --> 01:27:53.149 align:start position:0% you represent that well you need the shot<01:27:50.550> number<01:27:51.170> you're<01:27:52.170> going<01:27:52.320> to<01:27:52.409> need<01:27:52.620> the 01:27:53.149 --> 01:27:53.159 align:start position:0% shot number you're going to need the 01:27:53.159 --> 01:27:54.740 align:start position:0% shot number you're going to need the start<01:27:53.550> of<01:27:53.790> the<01:27:53.969> end<01:27:54.150> the<01:27:54.390> end 01:27:54.740 --> 01:27:54.750 align:start position:0% start of the end the end 01:27:54.750 --> 01:27:58.100 align:start position:0% start of the end the end Apoc<01:27:55.170> of<01:27:55.380> this<01:27:55.949> chunk<01:27:56.580> of<01:27:56.699> shot<01:27:56.989> that<01:27:57.989> you're 01:27:58.100 --> 01:27:58.110 align:start position:0% Apoc of this chunk of shot that you're 01:27:58.110 --> 01:28:02.570 align:start position:0% Apoc of this chunk of shot that you're cross-linking<01:27:58.739> and<01:28:00.710> you're<01:28:01.710> gonna<01:28:01.860> need<01:28:02.130> the 01:28:02.570 --> 01:28:02.580 align:start position:0% cross-linking and you're gonna need the 01:28:02.580 --> 01:28:04.430 align:start position:0% cross-linking and you're gonna need the the<01:28:02.880> data<01:28:03.120> roots<01:28:03.480> which<01:28:03.960> is<01:28:03.989> going<01:28:04.260> to 01:28:04.430 --> 01:28:04.440 align:start position:0% the data roots which is going to 01:28:04.440 --> 01:28:07.970 align:start position:0% the data roots which is going to represent<01:28:05.570> this<01:28:06.570> can<01:28:06.780> be<01:28:06.870> the<01:28:06.989> merkel<01:28:07.710> is<01:28:07.830> a 01:28:07.970 --> 01:28:07.980 align:start position:0% represent this can be the merkel is a 01:28:07.980 --> 01:28:10.399 align:start position:0% represent this can be the merkel is a ssin<01:28:08.190> of<01:28:08.400> the<01:28:08.880> chunk<01:28:09.179> that<01:28:09.390> your<01:28:09.719> cross 01:28:10.399 --> 01:28:10.409 align:start position:0% ssin of the chunk that your cross 01:28:10.409 --> 01:28:17.479 align:start position:0% ssin of the chunk that your cross linking<01:28:14.239> okay<01:28:15.239> so<01:28:15.300> in<01:28:15.960> green<01:28:16.469> we<01:28:17.130> have<01:28:17.370> the 01:28:17.479 --> 01:28:17.489 align:start position:0% linking okay so in green we have the 01:28:17.489 --> 01:28:20.060 align:start position:0% linking okay so in green we have the attestation<01:28:17.640> in<01:28:18.270> the<01:28:18.390> blocks<01:28:18.659> and<01:28:18.900> then<01:28:19.679> on<01:28:20.010> a 01:28:20.060 --> 01:28:20.070 align:start position:0% attestation in the blocks and then on a 01:28:20.070 --> 01:28:23.720 align:start position:0% attestation in the blocks and then on a slot<01:28:20.940> by<01:28:21.120> slot<01:28:21.420> basis<01:28:21.870> they<01:28:22.590> get<01:28:22.830> stored<01:28:23.310> into 01:28:23.720 --> 01:28:23.730 align:start position:0% slot by slot basis they get stored into 01:28:23.730 --> 01:28:26.240 align:start position:0% slot by slot basis they get stored into the<01:28:24.090> states<01:28:24.480> and<01:28:24.659> they<01:28:25.380> can<01:28:25.560> either<01:28:25.920> get 01:28:26.240 --> 01:28:26.250 align:start position:0% the states and they can either get 01:28:26.250 --> 01:28:29.660 align:start position:0% the states and they can either get stored<01:28:26.640> in<01:28:26.909> the<01:28:27.390> as<01:28:27.860> previous<01:28:28.860> époque<01:28:29.280> or 01:28:29.660 --> 01:28:29.670 align:start position:0% stored in the as previous époque or 01:28:29.670 --> 01:28:31.880 align:start position:0% stored in the as previous époque or current<01:28:30.120> epoch<01:28:30.390> attestation<01:28:30.810> so<01:28:31.230> if<01:28:31.710> your 01:28:31.880 --> 01:28:31.890 align:start position:0% current epoch attestation so if your 01:28:31.890 --> 01:28:34.280 align:start position:0% current epoch attestation so if your attestation<01:28:32.310> is<01:28:32.670> stale<01:28:33.090> it's<01:28:33.449> very<01:28:33.659> old<01:28:33.929> it's 01:28:34.280 --> 01:28:34.290 align:start position:0% attestation is stale it's very old it's 01:28:34.290 --> 01:28:36.229 align:start position:0% attestation is stale it's very old it's older<01:28:34.650> than<01:28:34.679> the<01:28:34.890> previous<01:28:35.250> app<01:28:35.400> book<01:28:35.640> then<01:28:36.150> we 01:28:36.229 --> 01:28:36.239 align:start position:0% older than the previous app book then we 01:28:36.239 --> 01:28:39.500 align:start position:0% older than the previous app book then we don't<01:28:36.360> even<01:28:36.540> bother<01:28:37.100> saving<01:28:38.100> it<01:28:38.370> in<01:28:38.489> state<01:28:38.760> we 01:28:39.500 --> 01:28:39.510 align:start position:0% don't even bother saving it in state we 01:28:39.510 --> 01:28:42.380 align:start position:0% don't even bother saving it in state we only<01:28:39.770> record<01:28:40.770> the<01:28:40.949> current<01:28:41.610> and<01:28:41.850> previous 01:28:42.380 --> 01:28:42.390 align:start position:0% only record the current and previous 01:28:42.390 --> 01:28:51.830 align:start position:0% only record the current and previous epoch<01:28:42.960> at<01:28:43.080> the<01:28:43.199> stations<01:28:47.929> and<01:28:48.929> then<01:28:50.179> and<01:28:51.179> then 01:28:51.830 --> 01:28:51.840 align:start position:0% epoch at the stations and then and then 01:28:51.840 --> 01:28:54.260 align:start position:0% epoch at the stations and then and then here<01:28:52.110> we<01:28:52.230> have<01:28:52.260> the<01:28:52.650> the<01:28:53.030> beginnings<01:28:54.030> of<01:28:54.150> the 01:28:54.260 --> 01:28:54.270 align:start position:0% here we have the the beginnings of the 01:28:54.270 --> 01:28:56.540 align:start position:0% here we have the the beginnings of the finality<01:28:54.830> mechanism<01:28:55.830> so<01:28:56.010> the<01:28:56.130> financing 01:28:56.540 --> 01:28:56.550 align:start position:0% finality mechanism so the financing 01:28:56.550 --> 01:29:00.740 align:start position:0% finality mechanism so the financing mechanism<01:28:57.090> works<01:28:57.810> on<01:28:58.110> an<01:28:58.440> epic<01:28:58.980> by<01:28:59.250> epic<01:29:00.239> basis 01:29:00.740 --> 01:29:00.750 align:start position:0% mechanism works on an epic by epic basis 01:29:00.750 --> 01:29:04.640 align:start position:0% mechanism works on an epic by epic basis hence<01:29:01.710> the<01:29:01.980> the<01:29:02.429> blue<01:29:02.909> arrow<01:29:03.120> and<01:29:03.540> what<01:29:04.530> it 01:29:04.640 --> 01:29:04.650 align:start position:0% hence the the blue arrow and what it 01:29:04.650 --> 01:29:07.790 align:start position:0% hence the the blue arrow and what it does<01:29:04.860> is<01:29:05.100> that<01:29:05.130> it<01:29:05.310> is<01:29:05.610> going<01:29:06.120> to<01:29:06.420> look<01:29:06.719> at<01:29:07.020> the 01:29:07.790 --> 01:29:07.800 align:start position:0% does is that it is going to look at the 01:29:07.800 --> 01:29:10.760 align:start position:0% does is that it is going to look at the the<01:29:08.040> cache<01:29:08.340> of<01:29:08.840> recent<01:29:09.840> data<01:29:09.960> stations<01:29:10.500> and 01:29:10.760 --> 01:29:10.770 align:start position:0% the cache of recent data stations and 01:29:10.770 --> 01:29:14.750 align:start position:0% the cache of recent data stations and then<01:29:11.219> count<01:29:11.550> count<01:29:12.330> the<01:29:12.510> votes<01:29:12.719> and<01:29:13.370> if<01:29:14.370> we<01:29:14.520> if 01:29:14.750 --> 01:29:14.760 align:start position:0% then count count the votes and if we if 01:29:14.760 --> 01:29:19.190 align:start position:0% then count count the votes and if we if we<01:29:14.820> get<01:29:15.179> to<01:29:15.420> this<01:29:15.949> two-third<01:29:16.949> threshold<01:29:17.550> is<01:29:17.790> go 01:29:19.190 --> 01:29:19.200 align:start position:0% we get to this two-third threshold is go 01:29:19.200 --> 01:29:22.250 align:start position:0% we get to this two-third threshold is go and<01:29:19.290> we're<01:29:19.890> going<01:29:20.160> to<01:29:20.750> record<01:29:21.750> that<01:29:22.080> we<01:29:22.230> have 01:29:22.250 --> 01:29:22.260 align:start position:0% and we're going to record that we have 01:29:22.260 --> 01:29:24.620 align:start position:0% and we're going to record that we have met<01:29:23.010> the<01:29:23.160> two<01:29:23.340> first<01:29:23.580> fresh<01:29:23.820> hold<01:29:24.090> by 01:29:24.620 --> 01:29:24.630 align:start position:0% met the two first fresh hold by 01:29:24.630 --> 01:29:28.490 align:start position:0% met the two first fresh hold by modifying<01:29:25.260> the<01:29:25.760> justification<01:29:26.760> bit<01:29:27.170> and<01:29:28.170> also 01:29:28.490 --> 01:29:28.500 align:start position:0% modifying the justification bit and also 01:29:28.500 --> 01:29:35.000 align:start position:0% modifying the justification bit and also by<01:29:30.920> potentially<01:29:31.920> advancing<01:29:32.580> the<01:29:33.800> the<01:29:34.800> last 01:29:35.000 --> 01:29:35.010 align:start position:0% by potentially advancing the the last 01:29:35.010 --> 01:29:39.740 align:start position:0% by potentially advancing the the last and<01:29:35.460> the<01:29:36.030> previous<01:29:36.590> justified<01:29:37.590> at<01:29:37.770> Bach<01:29:38.750> and 01:29:39.740 --> 01:29:39.750 align:start position:0% and the previous justified at Bach and 01:29:39.750 --> 01:29:43.700 align:start position:0% and the previous justified at Bach and then<01:29:40.740> if<01:29:41.100> we<01:29:41.550> have<01:29:41.790> this<01:29:42.350> so-called<01:29:43.350> finality 01:29:43.700 --> 01:29:43.710 align:start position:0% then if we have this so-called finality 01:29:43.710 --> 01:29:46.130 align:start position:0% then if we have this so-called finality patterns<01:29:44.400> of<01:29:44.820> which<01:29:45.060> we<01:29:45.210> have<01:29:45.360> four<01:29:45.660> as 01:29:46.130 --> 01:29:46.140 align:start position:0% patterns of which we have four as 01:29:46.140 --> 01:29:49.520 align:start position:0% patterns of which we have four as explained<01:29:46.560> by<01:29:46.680> Danny<01:29:47.420> then<01:29:48.420> we're<01:29:48.870> also<01:29:49.200> going 01:29:49.520 --> 01:29:49.530 align:start position:0% explained by Danny then we're also going 01:29:49.530 --> 01:29:52.640 align:start position:0% explained by Danny then we're also going to<01:29:49.650> advance<01:29:50.100> the<01:29:50.660> the<01:29:51.660> finalize<01:29:52.110> checkpoints 01:29:52.640 --> 01:29:52.650 align:start position:0% to advance the the finalize checkpoints 01:29:52.650 --> 01:29:54.770 align:start position:0% to advance the the finalize checkpoints so<01:29:53.130> the<01:29:53.250> the<01:29:53.610> beacon<01:29:53.970> chain<01:29:54.180> is<01:29:54.330> going<01:29:54.480> to<01:29:54.660> be 01:29:54.770 --> 01:29:54.780 align:start position:0% so the the beacon chain is going to be 01:29:54.780 --> 01:29:58.160 align:start position:0% so the the beacon chain is going to be aware<01:29:55.080> of<01:29:55.640> its<01:29:56.640> its<01:29:57.330> last<01:29:57.660> finalized 01:29:58.160 --> 01:29:58.170 align:start position:0% aware of its its last finalized 01:29:58.170 --> 01:30:03.530 align:start position:0% aware of its its last finalized checkpoint<01:30:00.020> and<01:30:01.130> as<01:30:02.130> part<01:30:02.400> as<01:30:02.820> part<01:30:02.970> of<01:30:03.330> this 01:30:03.530 --> 01:30:03.540 align:start position:0% checkpoint and as part as part of this 01:30:03.540 --> 01:30:06.260 align:start position:0% checkpoint and as part as part of this you<01:30:04.440> know<01:30:04.560> as<01:30:04.860> part<01:30:05.040> of<01:30:05.190> the<01:30:05.340> the<01:30:05.820> safety<01:30:06.180> of 01:30:06.260 --> 01:30:06.270 align:start position:0% you know as part of the the safety of 01:30:06.270 --> 01:30:09.040 align:start position:0% you know as part of the the safety of this<01:30:06.390> this<01:30:07.110> mechanism<01:30:07.440> is<01:30:07.890> the<01:30:08.070> idea<01:30:08.340> of 01:30:09.040 --> 01:30:09.050 align:start position:0% this this mechanism is the idea of 01:30:09.050 --> 01:30:12.320 align:start position:0% this this mechanism is the idea of slashing<01:30:10.050> the<01:30:10.170> testers<01:30:10.710> that<01:30:11.430> that<01:30:11.820> make<01:30:12.060> bad 01:30:12.320 --> 01:30:12.330 align:start position:0% slashing the testers that that make bad 01:30:12.330 --> 01:30:16.250 align:start position:0% slashing the testers that that make bad votes<01:30:12.660> so<01:30:13.470> how<01:30:14.160> does<01:30:14.220> this<01:30:14.550> work<01:30:15.000> well<01:30:15.720> we<01:30:15.990> have 01:30:16.250 --> 01:30:16.260 align:start position:0% votes so how does this work well we have 01:30:16.260 --> 01:30:20.210 align:start position:0% votes so how does this work well we have fraud<01:30:17.220> proofs<01:30:17.610> we<01:30:18.270> have<01:30:18.450> proofs<01:30:18.840> that<01:30:19.230> our 01:30:20.210 --> 01:30:20.220 align:start position:0% fraud proofs we have proofs that our 01:30:20.220 --> 01:30:22.640 align:start position:0% fraud proofs we have proofs that our testers<01:30:20.730> have<01:30:20.910> been<01:30:21.120> doing<01:30:21.420> a<01:30:21.540> bad<01:30:21.720> job<01:30:21.750> these 01:30:22.640 --> 01:30:22.650 align:start position:0% testers have been doing a bad job these 01:30:22.650 --> 01:30:25.780 align:start position:0% testers have been doing a bad job these are<01:30:22.710> included<01:30:23.100> in<01:30:23.460> in<01:30:23.610> blocks<01:30:23.940> in<01:30:24.300> green<01:30:24.540> and 01:30:25.780 --> 01:30:25.790 align:start position:0% are included in in blocks in green and 01:30:25.790 --> 01:30:27.680 align:start position:0% are included in in blocks in green and they're<01:30:26.790> going<01:30:26.910> to<01:30:27.030> have<01:30:27.150> an<01:30:27.270> immediate 01:30:27.680 --> 01:30:27.690 align:start position:0% they're going to have an immediate 01:30:27.690 --> 01:30:31.280 align:start position:0% they're going to have an immediate effect<01:30:27.810> a<01:30:28.350> green<01:30:29.250> arrow<01:30:29.520> on<01:30:29.910> on<01:30:30.600> the<01:30:30.780> registry 01:30:31.280 --> 01:30:31.290 align:start position:0% effect a green arrow on on the registry 01:30:31.290 --> 01:30:34.820 align:start position:0% effect a green arrow on on the registry so<01:30:31.320> if<01:30:31.920> someone<01:30:32.790> has<01:30:33.240> has<01:30:33.720> done<01:30:34.200> /<01:30:34.500> herbal 01:30:34.820 --> 01:30:34.830 align:start position:0% so if someone has has done / herbal 01:30:34.830 --> 01:30:37.850 align:start position:0% so if someone has has done / herbal behavior<01:30:35.310> they<01:30:35.880> will<01:30:36.060> be<01:30:36.210> marked<01:30:36.450> as<01:30:36.860> slashed 01:30:37.850 --> 01:30:37.860 align:start position:0% behavior they will be marked as slashed 01:30:37.860 --> 01:30:42.080 align:start position:0% behavior they will be marked as slashed immediately<01:30:38.550> on<01:30:38.870> in<01:30:39.870> the<01:30:40.020> registry<01:30:40.470> and<01:30:41.090> in 01:30:42.080 --> 01:30:42.090 align:start position:0% immediately on in the registry and in 01:30:42.090 --> 01:30:44.920 align:start position:0% immediately on in the registry and in addition<01:30:42.510> to<01:30:42.600> that<01:30:42.780> would<01:30:42.960> we<01:30:43.230> keep<01:30:43.440> track<01:30:43.740> of 01:30:44.920 --> 01:30:44.930 align:start position:0% addition to that would we keep track of 01:30:44.930 --> 01:30:53.690 align:start position:0% addition to that would we keep track of the<01:30:45.930> total<01:30:46.380> amount<01:30:46.980> of<01:30:49.790> of<01:30:51.020> 'if<01:30:52.020> that<01:30:52.950> that 01:30:53.690 --> 01:30:53.700 align:start position:0% the total amount of of 'if that that 01:30:53.700 --> 01:30:56.570 align:start position:0% the total amount of of 'if that that that<01:30:54.630> was<01:30:54.900> slashed<01:30:55.200> and<01:30:55.530> the<01:30:55.920> reason<01:30:56.250> we<01:30:56.400> do 01:30:56.570 --> 01:30:56.580 align:start position:0% that was slashed and the reason we do 01:30:56.580 --> 01:31:03.560 align:start position:0% that was slashed and the reason we do that<01:30:56.610> is<01:30:57.090> because<01:30:58.220> we<01:30:59.220> want<01:30:59.400> to<01:31:00.770> the<01:31:01.770> the<01:31:02.250> we<01:31:03.090> we 01:31:03.560 --> 01:31:03.570 align:start position:0% that is because we want to the the we we 01:31:03.570 --> 01:31:05.990 align:start position:0% that is because we want to the the we we want<01:31:03.750> to<01:31:03.780> have<01:31:03.960> a<01:31:03.990> mechanism<01:31:04.440> whereby<01:31:04.800> if<01:31:05.460> only 01:31:05.990 --> 01:31:06.000 align:start position:0% want to have a mechanism whereby if only 01:31:06.000 --> 01:31:10.520 align:start position:0% want to have a mechanism whereby if only a<01:31:06.030> few<01:31:06.120> a<01:31:06.660> testers<01:31:07.880> do<01:31:08.880> bad<01:31:09.120> stuff<01:31:09.170> for<01:31:10.170> example 01:31:10.520 --> 01:31:10.530 align:start position:0% a few a testers do bad stuff for example 01:31:10.530 --> 01:31:13.130 align:start position:0% a few a testers do bad stuff for example then<01:31:10.830> we<01:31:11.280> they're<01:31:12.090> not<01:31:12.270> really<01:31:12.450> jeopardizing 01:31:13.130 --> 01:31:13.140 align:start position:0% then we they're not really jeopardizing 01:31:13.140 --> 01:31:14.540 align:start position:0% then we they're not really jeopardizing the<01:31:13.260> system<01:31:13.590> so<01:31:13.800> we<01:31:13.920> don't<01:31:13.950> want<01:31:14.250> to<01:31:14.280> penalize 01:31:14.540 --> 01:31:14.550 align:start position:0% the system so we don't want to penalize 01:31:14.550 --> 01:31:17.330 align:start position:0% the system so we don't want to penalize them<01:31:15.030> to<01:31:15.270> too<01:31:15.630> strongly<01:31:15.960> but<01:31:16.680> if<01:31:16.830> lots<01:31:17.190> of 01:31:17.330 --> 01:31:17.340 align:start position:0% them to too strongly but if lots of 01:31:17.340 --> 01:31:19.490 align:start position:0% them to too strongly but if lots of people<01:31:17.400> are<01:31:17.910> doing<01:31:18.060> bad<01:31:18.390> stuff<01:31:18.420> then<01:31:19.320> the 01:31:19.490 --> 01:31:19.500 align:start position:0% people are doing bad stuff then the 01:31:19.500 --> 01:31:21.320 align:start position:0% people are doing bad stuff then the system<01:31:19.830> is<01:31:19.920> at<01:31:20.070> risk<01:31:20.280> and<01:31:20.670> so<01:31:20.970> we<01:31:21.090> want<01:31:21.240> to 01:31:21.320 --> 01:31:21.330 align:start position:0% system is at risk and so we want to 01:31:21.330 --> 01:31:24.470 align:start position:0% system is at risk and so we want to penalize<01:31:21.570> everyone<01:31:22.490> -<01:31:23.490> to<01:31:23.790> a<01:31:23.820> large<01:31:24.060> extent 01:31:24.470 --> 01:31:24.480 align:start position:0% penalize everyone - to a large extent 01:31:24.480 --> 01:31:27.710 align:start position:0% penalize everyone - to a large extent and<01:31:24.630> so<01:31:25.110> this<01:31:25.740> this<01:31:26.640> variable<01:31:27.210> here<01:31:27.510> in<01:31:27.630> the 01:31:27.710 --> 01:31:27.720 align:start position:0% and so this this variable here in the 01:31:27.720 --> 01:31:31.790 align:start position:0% and so this this variable here in the state<01:31:27.990> in<01:31:28.260> blue<01:31:28.470> is<01:31:28.770> is<01:31:29.730> keeping<01:31:30.480> track<01:31:30.630> of<01:31:30.800> how 01:31:31.790 --> 01:31:31.800 align:start position:0% state in blue is is keeping track of how 01:31:31.800 --> 01:31:33.020 align:start position:0% state in blue is is keeping track of how much<01:31:31.980> bad<01:31:32.310> behavior<01:31:32.790> has 01:31:33.020 --> 01:31:33.030 align:start position:0% much bad behavior has 01:31:33.030 --> 01:31:39.200 align:start position:0% much bad behavior has happened<01:31:33.329> in<01:31:33.539> the<01:31:33.809> recent<01:31:34.139> past<01:31:37.579> and<01:31:38.579> then<01:31:39.090> we 01:31:39.200 --> 01:31:39.210 align:start position:0% happened in the recent past and then we 01:31:39.210 --> 01:31:42.319 align:start position:0% happened in the recent past and then we have<01:31:39.480> the<01:31:39.960> cross<01:31:40.199> links<01:31:40.559> and<01:31:40.739> this<01:31:41.280> this<01:31:42.030> works 01:31:42.319 --> 01:31:42.329 align:start position:0% have the cross links and this this works 01:31:42.329 --> 01:31:44.089 align:start position:0% have the cross links and this this works pretty<01:31:42.809> much<01:31:42.960> exactly<01:31:43.260> the<01:31:43.500> well<01:31:43.889> very 01:31:44.089 --> 01:31:44.099 align:start position:0% pretty much exactly the well very 01:31:44.099 --> 01:31:54.370 align:start position:0% pretty much exactly the well very similar<01:31:44.489> to<01:31:46.969> mmm<01:31:48.530> yeah<01:31:49.530> to<01:31:49.949> to<01:31:50.130> to<01:31:51.030> to<01:31:51.300> this<01:31:51.599> so 01:31:54.370 --> 01:31:54.380 align:start position:0% 01:31:54.380 --> 01:32:06.379 align:start position:0% no<01:31:55.380> doesn't<01:31:55.980> work<01:31:56.010> the<01:31:56.219> same<01:31:56.400> oh<01:32:04.849> no<01:32:05.849> this<01:32:06.270> is 01:32:06.379 --> 01:32:06.389 align:start position:0% no doesn't work the same oh no this is 01:32:06.389 --> 01:32:07.970 align:start position:0% no doesn't work the same oh no this is different<01:32:06.480> sorry<01:32:06.840> so<01:32:07.020> this<01:32:07.260> is<01:32:07.409> basically<01:32:07.679> is 01:32:07.970 --> 01:32:07.980 align:start position:0% different sorry so this is basically is 01:32:07.980 --> 01:32:14.270 align:start position:0% different sorry so this is basically is as<01:32:08.760> a<01:32:08.820> mapping<01:32:09.360> from<01:32:10.190> from<01:32:11.190> shard<01:32:11.550> to<01:32:12.300> to<01:32:13.280> to 01:32:14.270 --> 01:32:14.280 align:start position:0% as a mapping from from shard to to to 01:32:14.280 --> 01:32:18.439 align:start position:0% as a mapping from from shard to to to cross<01:32:14.550> link<01:32:14.730> and<01:32:15.000> it<01:32:15.420> records<01:32:15.809> the<01:32:17.239> either<01:32:18.239> the 01:32:18.439 --> 01:32:18.449 align:start position:0% cross link and it records the either the 01:32:18.449 --> 01:32:20.720 align:start position:0% cross link and it records the either the the<01:32:18.599> previous<01:32:19.199> cross<01:32:19.530> links<01:32:19.860> all<01:32:20.099> the<01:32:20.400> current 01:32:20.720 --> 01:32:20.730 align:start position:0% the previous cross links all the current 01:32:20.730 --> 01:32:24.200 align:start position:0% the previous cross links all the current cross<01:32:20.909> links<01:32:21.179> and<01:32:21.329> basically<01:32:21.960> on<01:32:22.320> on<01:32:23.010> an<01:32:23.250> every 01:32:24.200 --> 01:32:24.210 align:start position:0% cross links and basically on on an every 01:32:24.210 --> 01:32:26.810 align:start position:0% cross links and basically on on an every every<01:32:24.900> epoch<01:32:25.289> hence<01:32:25.920> the<01:32:26.099> blue<01:32:26.219> arrow<01:32:26.489> we 01:32:26.810 --> 01:32:26.820 align:start position:0% every epoch hence the blue arrow we 01:32:26.820 --> 01:32:30.319 align:start position:0% every epoch hence the blue arrow we would<01:32:27.000> we<01:32:27.510> save<01:32:27.840> the<01:32:28.230> current<01:32:28.789> cross<01:32:29.789> links<01:32:30.179> in 01:32:30.319 --> 01:32:30.329 align:start position:0% would we save the current cross links in 01:32:30.329 --> 01:32:34.700 align:start position:0% would we save the current cross links in the<01:32:30.420> in<01:32:30.989> the<01:32:31.079> previous<01:32:31.260> cross<01:32:31.619> links<01:32:32.539> and<01:32:33.710> that 01:32:34.700 --> 01:32:34.710 align:start position:0% the in the previous cross links and that 01:32:34.710 --> 01:32:36.229 align:start position:0% the in the previous cross links and that basically<01:32:34.980> allows<01:32:35.309> for<01:32:35.550> the<01:32:35.639> for<01:32:35.880> the<01:32:35.969> beacon 01:32:36.229 --> 01:32:36.239 align:start position:0% basically allows for the for the beacon 01:32:36.239 --> 01:32:39.859 align:start position:0% basically allows for the for the beacon chain<01:32:36.510> to<01:32:37.050> be<01:32:37.170> aware<01:32:37.500> of<01:32:38.239> of<01:32:39.239> recent<01:32:39.690> cross 01:32:39.859 --> 01:32:39.869 align:start position:0% chain to be aware of of recent cross 01:32:39.869 --> 01:32:41.810 align:start position:0% chain to be aware of of recent cross links<01:32:40.079> across<01:32:40.289> all<01:32:40.619> the<01:32:40.739> shards<01:32:41.099> and<01:32:41.219> hence 01:32:41.810 --> 01:32:41.820 align:start position:0% links across all the shards and hence 01:32:41.820 --> 01:32:44.839 align:start position:0% links across all the shards and hence for<01:32:42.179> every<01:32:43.020> shot<01:32:43.289> to<01:32:43.559> be<01:32:43.679> aware<01:32:44.010> through<01:32:44.699> the 01:32:44.839 --> 01:32:44.849 align:start position:0% for every shot to be aware through the 01:32:44.849 --> 01:32:46.970 align:start position:0% for every shot to be aware through the beacon<01:32:45.119> chain<01:32:45.360> of<01:32:45.599> the<01:32:45.960> cross<01:32:46.199> links<01:32:46.530> on<01:32:46.650> on 01:32:46.970 --> 01:32:46.980 align:start position:0% beacon chain of the cross links on on 01:32:46.980 --> 01:32:52.939 align:start position:0% beacon chain of the cross links on on every<01:32:47.250> other<01:32:47.369> shot<01:32:49.639> and<01:32:50.840> yeah<01:32:51.840> this<01:32:52.079> is<01:32:52.679> this 01:32:52.939 --> 01:32:52.949 align:start position:0% every other shot and yeah this is this 01:32:52.949 --> 01:32:55.069 align:start position:0% every other shot and yeah this is this is<01:32:53.099> pretty<01:32:53.219> much<01:32:53.429> it<01:32:53.639> so<01:32:53.670> we<01:32:53.909> have<01:32:54.059> the<01:32:54.780> full 01:32:55.069 --> 01:32:55.079 align:start position:0% is pretty much it so we have the full 01:32:55.079 --> 01:32:58.120 align:start position:0% is pretty much it so we have the full kind<01:32:55.559> of<01:32:55.679> honest<01:32:56.130> state<01:32:56.579> transition<01:32:57.000> function 01:32:58.120 --> 01:32:58.130 align:start position:0% kind of honest state transition function 01:32:58.130 --> 01:33:02.120 align:start position:0% kind of honest state transition function at<01:32:59.130> a<01:32:59.190> high<01:32:59.489> level<01:32:59.809> again<01:33:00.809> like<01:33:01.289> made<01:33:01.770> out<01:33:01.800> of 01:33:02.120 --> 01:33:02.130 align:start position:0% at a high level again like made out of 01:33:02.130 --> 01:33:04.370 align:start position:0% at a high level again like made out of these<01:33:02.340> modules<01:33:03.030> which<01:33:03.510> are<01:33:03.630> replaceable 01:33:04.370 --> 01:33:04.380 align:start position:0% these modules which are replaceable 01:33:04.380 --> 01:33:06.620 align:start position:0% these modules which are replaceable which<01:33:05.010> talk<01:33:05.309> to<01:33:05.520> each<01:33:05.610> other<01:33:05.849> and<01:33:06.179> at<01:33:06.449> the<01:33:06.539> end 01:33:06.620 --> 01:33:06.630 align:start position:0% which talk to each other and at the end 01:33:06.630 --> 01:33:07.700 align:start position:0% which talk to each other and at the end of<01:33:06.690> the<01:33:06.809> day<01:33:06.960> there<01:33:07.170> isn't<01:33:07.440> that<01:33:07.500> much 01:33:07.700 --> 01:33:07.710 align:start position:0% of the day there isn't that much 01:33:07.710 --> 01:33:10.279 align:start position:0% of the day there isn't that much happening<01:33:08.190> there's<01:33:08.460> basic<01:33:09.360> scaffolding 01:33:10.279 --> 01:33:10.289 align:start position:0% happening there's basic scaffolding 01:33:10.289 --> 01:33:12.649 align:start position:0% happening there's basic scaffolding there's<01:33:11.010> you<01:33:11.610> know<01:33:11.639> maintenance<01:33:12.300> of<01:33:12.539> the 01:33:12.649 --> 01:33:12.659 align:start position:0% there's you know maintenance of the 01:33:12.659 --> 01:33:14.390 align:start position:0% there's you know maintenance of the registry<01:33:13.170> which<01:33:13.409> is<01:33:13.500> kind<01:33:13.679> of<01:33:13.739> obvious<01:33:13.889> stuff 01:33:14.390 --> 01:33:14.400 align:start position:0% registry which is kind of obvious stuff 01:33:14.400 --> 01:33:18.529 align:start position:0% registry which is kind of obvious stuff and<01:33:14.670> then<01:33:15.270> there's<01:33:16.909> finality<01:33:17.909> which<01:33:18.389> is<01:33:18.510> a 01:33:18.529 --> 01:33:18.539 align:start position:0% and then there's finality which is a 01:33:18.539 --> 01:33:20.600 align:start position:0% and then there's finality which is a very<01:33:18.809> important<01:33:19.260> gadget<01:33:19.619> and<01:33:19.860> then<01:33:20.280> we<01:33:20.460> have 01:33:20.600 --> 01:33:20.610 align:start position:0% very important gadget and then we have 01:33:20.610 --> 01:33:25.959 align:start position:0% very important gadget and then we have this<01:33:20.699> cross<01:33:20.969> linking<01:33:21.329> gadget<01:33:21.770> for<01:33:22.770> shouting 01:33:25.959 --> 01:33:25.969 align:start position:0% 01:33:25.969 --> 01:33:28.609 align:start position:0% okay<01:33:26.969> great<01:33:27.300> so<01:33:28.110> that's<01:33:28.230> what<01:33:28.440> we're<01:33:28.590> looking 01:33:28.609 --> 01:33:28.619 align:start position:0% okay great so that's what we're looking 01:33:28.619 --> 01:33:31.040 align:start position:0% okay great so that's what we're looking to<01:33:29.010> launch<01:33:29.250> in<01:33:29.489> phase<01:33:29.670> 0<01:33:29.940> but<01:33:30.239> what<01:33:30.389> what<01:33:30.780> comes 01:33:31.040 --> 01:33:31.050 align:start position:0% to launch in phase 0 but what what comes 01:33:31.050 --> 01:33:36.589 align:start position:0% to launch in phase 0 but what what comes afterwards<01:33:32.150> we<01:33:33.860> we<01:33:34.860> have<01:33:35.329> transfers<01:33:36.329> which 01:33:36.589 --> 01:33:36.599 align:start position:0% afterwards we we have transfers which 01:33:36.599 --> 01:33:41.209 align:start position:0% afterwards we we have transfers which are<01:33:37.159> slated<01:33:38.159> to<01:33:38.340> come<01:33:39.380> likely<01:33:40.380> in<01:33:40.500> in<01:33:40.739> phase<01:33:40.949> 1 01:33:41.209 --> 01:33:41.219 align:start position:0% are slated to come likely in in phase 1 01:33:41.219 --> 01:33:44.149 align:start position:0% are slated to come likely in in phase 1 which<01:33:41.550> will<01:33:41.699> basically<01:33:41.849> allow<01:33:42.269> for<01:33:42.889> efj<01:33:43.889> on 01:33:44.149 --> 01:33:44.159 align:start position:0% which will basically allow for efj on 01:33:44.159 --> 01:33:46.090 align:start position:0% which will basically allow for efj on the<01:33:44.250> beacon<01:33:44.429> chain<01:33:44.789> to<01:33:45.059> be 01:33:46.090 --> 01:33:46.100 align:start position:0% the beacon chain to be 01:33:46.100 --> 01:33:49.150 align:start position:0% the beacon chain to be and<01:33:46.490> that<01:33:46.580> will<01:33:46.700> create<01:33:46.850> a<01:33:47.020> market<01:33:48.070> for<01:33:49.070> this 01:33:49.150 --> 01:33:49.160 align:start position:0% and that will create a market for this 01:33:49.160 --> 01:33:53.110 align:start position:0% and that will create a market for this if<01:33:49.990> now<01:33:50.990> we<01:33:51.080> also<01:33:51.230> have<01:33:51.470> a<01:33:51.500> bunch<01:33:51.770> of<01:33:52.120> security 01:33:53.110 --> 01:33:53.120 align:start position:0% if now we also have a bunch of security 01:33:53.120 --> 01:33:54.730 align:start position:0% if now we also have a bunch of security upgrades<01:33:53.510> that<01:33:53.780> we're<01:33:53.870> looking<01:33:53.990> to<01:33:54.260> do<01:33:54.380> and 01:33:54.730 --> 01:33:54.740 align:start position:0% upgrades that we're looking to do and 01:33:54.740 --> 01:33:56.530 align:start position:0% upgrades that we're looking to do and each<01:33:55.190> of<01:33:55.400> these<01:33:55.520> security<01:33:56.090> upgrades<01:33:56.420> are 01:33:56.530 --> 01:33:56.540 align:start position:0% each of these security upgrades are 01:33:56.540 --> 01:33:58.360 align:start position:0% each of these security upgrades are optional<01:33:57.020> but<01:33:57.230> they're<01:33:57.620> very<01:33:57.740> nice<01:33:58.010> to<01:33:58.190> have 01:33:58.360 --> 01:33:58.370 align:start position:0% optional but they're very nice to have 01:33:58.370 --> 01:34:01.030 align:start position:0% optional but they're very nice to have and<01:33:59.170> you<01:34:00.170> know<01:34:00.260> one<01:34:00.410> of<01:34:00.440> the<01:34:00.620> reasons<01:34:00.920> why 01:34:01.030 --> 01:34:01.040 align:start position:0% and you know one of the reasons why 01:34:01.040 --> 01:34:03.130 align:start position:0% and you know one of the reasons why we're<01:34:01.250> not<01:34:01.370> putting<01:34:01.760> them<01:34:02.120> up<01:34:02.540> front<01:34:02.930> is 01:34:03.130 --> 01:34:03.140 align:start position:0% we're not putting them up front is 01:34:03.140 --> 01:34:07.300 align:start position:0% we're not putting them up front is because<01:34:03.760> they<01:34:04.760> all<01:34:05.150> have<01:34:05.390> you<01:34:05.960> know<01:34:06.310> fancy 01:34:07.300 --> 01:34:07.310 align:start position:0% because they all have you know fancy 01:34:07.310 --> 01:34:09.370 align:start position:0% because they all have you know fancy constructions<01:34:08.030> and<01:34:08.210> fancy<01:34:08.540> cryptography<01:34:09.140> so 01:34:09.370 --> 01:34:09.380 align:start position:0% constructions and fancy cryptography so 01:34:09.380 --> 01:34:12.910 align:start position:0% constructions and fancy cryptography so one<01:34:10.130> one<01:34:10.640> of<01:34:10.760> them<01:34:10.970> is<01:34:11.290> Cassidy<01:34:12.290> proofs<01:34:12.680> which 01:34:12.910 --> 01:34:12.920 align:start position:0% one one of them is Cassidy proofs which 01:34:12.920 --> 01:34:15.610 align:start position:0% one one of them is Cassidy proofs which we're<01:34:13.070> looking<01:34:13.280> to<01:34:13.370> do<01:34:13.460> in<01:34:13.550> phase<01:34:13.700> one<01:34:14.470> we<01:34:15.470> have 01:34:15.610 --> 01:34:15.620 align:start position:0% we're looking to do in phase one we have 01:34:15.620 --> 01:34:17.370 align:start position:0% we're looking to do in phase one we have the<01:34:15.740> idea<01:34:15.980> of<01:34:16.040> secret<01:34:16.460> proposes<01:34:17.030> where 01:34:17.370 --> 01:34:17.380 align:start position:0% the idea of secret proposes where 01:34:17.380 --> 01:34:23.080 align:start position:0% the idea of secret proposes where instead<01:34:18.380> of<01:34:19.030> knowing<01:34:20.140> upfront<01:34:21.490> who<01:34:22.490> then<01:34:22.760> who 01:34:23.080 --> 01:34:23.090 align:start position:0% instead of knowing upfront who then who 01:34:23.090 --> 01:34:26.140 align:start position:0% instead of knowing upfront who then who the<01:34:23.210> next<01:34:23.330> proposals<01:34:23.840> will<01:34:23.990> be<01:34:24.790> we<01:34:25.790> can<01:34:25.820> have<01:34:26.120> a 01:34:26.140 --> 01:34:26.150 align:start position:0% the next proposals will be we can have a 01:34:26.150 --> 01:34:28.930 align:start position:0% the next proposals will be we can have a system<01:34:26.420> whereby<01:34:26.840> we<01:34:27.620> don't<01:34:27.860> know<01:34:28.100> which 01:34:28.930 --> 01:34:28.940 align:start position:0% system whereby we don't know which 01:34:28.940 --> 01:34:31.060 align:start position:0% system whereby we don't know which proposes<01:34:29.420> will<01:34:30.140> be<01:34:30.260> invited<01:34:30.740> to<01:34:30.770> create 01:34:31.060 --> 01:34:31.070 align:start position:0% proposes will be invited to create 01:34:31.070 --> 01:34:33.610 align:start position:0% proposes will be invited to create beacon<01:34:31.430> blocks<01:34:31.670> and<01:34:31.910> that<01:34:32.420> is<01:34:32.600> a<01:34:33.170> way<01:34:33.560> to 01:34:33.610 --> 01:34:33.620 align:start position:0% beacon blocks and that is a way to 01:34:33.620 --> 01:34:35.650 align:start position:0% beacon blocks and that is a way to protect<01:34:33.890> ourselves<01:34:34.160> against<01:34:35.030> in<01:34:35.150> our<01:34:35.240> service 01:34:35.650 --> 01:34:35.660 align:start position:0% protect ourselves against in our service 01:34:35.660 --> 01:34:37.990 align:start position:0% protect ourselves against in our service attacks<01:34:35.990> because<01:34:36.710> if<01:34:36.830> you<01:34:36.950> know<01:34:37.160> who<01:34:37.760> the<01:34:37.880> next 01:34:37.990 --> 01:34:38.000 align:start position:0% attacks because if you know who the next 01:34:38.000 --> 01:34:39.940 align:start position:0% attacks because if you know who the next proposals<01:34:38.510> will<01:34:38.630> be<01:34:38.780> then<01:34:39.350> you<01:34:39.470> can<01:34:39.620> target 01:34:39.940 --> 01:34:39.950 align:start position:0% proposals will be then you can target 01:34:39.950 --> 01:34:44.200 align:start position:0% proposals will be then you can target them<01:34:40.280> I<01:34:42.460> didn't<01:34:43.460> add<01:34:43.640> the<01:34:43.670> networking<01:34:44.150> layer 01:34:44.200 --> 01:34:44.210 align:start position:0% them I didn't add the networking layer 01:34:44.210 --> 01:34:50.860 align:start position:0% them I didn't add the networking layer we<01:34:45.200> have<01:34:45.910> vdf<01:34:47.080> randomness<01:34:48.080> upgrade<01:34:49.180> which<01:34:50.180> you 01:34:50.860 --> 01:34:50.870 align:start position:0% we have vdf randomness upgrade which you 01:34:50.870 --> 01:34:52.900 align:start position:0% we have vdf randomness upgrade which you know<01:34:50.960> my<01:34:51.290> comment<01:34:51.740> phase<01:34:51.920> to<01:34:52.190> my<01:34:52.430> Combinator 01:34:52.900 --> 01:34:52.910 align:start position:0% know my comment phase to my Combinator 01:34:52.910 --> 01:34:56.170 align:start position:0% know my comment phase to my Combinator and<01:34:53.180> then<01:34:54.050> we<01:34:54.200> have<01:34:54.730> data<01:34:55.730> availability 01:34:56.170 --> 01:34:56.180 align:start position:0% and then we have data availability 01:34:56.180 --> 01:35:02.410 align:start position:0% and then we have data availability proofs<01:34:58.690> and<01:35:00.250> I<01:35:01.250> mean<01:35:01.760> one<01:35:02.030> thing<01:35:02.180> I<01:35:02.270> didn't 01:35:02.410 --> 01:35:02.420 align:start position:0% proofs and I mean one thing I didn't 01:35:02.420 --> 01:35:05.830 align:start position:0% proofs and I mean one thing I didn't mention<01:35:02.480> here<01:35:02.870> actually<01:35:03.020> is<01:35:03.610> like<01:35:04.610> clients<01:35:05.120> in 01:35:05.830 --> 01:35:05.840 align:start position:0% mention here actually is like clients in 01:35:05.840 --> 01:35:07.780 align:start position:0% mention here actually is like clients in infrastructure<01:35:06.590> so<01:35:07.190> we<01:35:07.220> want<01:35:07.520> to<01:35:07.580> make<01:35:07.670> it 01:35:07.780 --> 01:35:07.790 align:start position:0% infrastructure so we want to make it 01:35:07.790 --> 01:35:13.150 align:start position:0% infrastructure so we want to make it very<01:35:07.820> easy<01:35:08.240> for<01:35:10.210> for<01:35:11.210> to<01:35:11.690> have<01:35:11.900> a<01:35:12.440> beacon<01:35:12.980> chain 01:35:13.150 --> 01:35:13.160 align:start position:0% very easy for for to have a beacon chain 01:35:13.160 --> 01:35:14.890 align:start position:0% very easy for for to have a beacon chain like<01:35:13.340> clients<01:35:13.730> and<01:35:13.880> and<01:35:14.030> this<01:35:14.390> infrastructure 01:35:14.890 --> 01:35:14.900 align:start position:0% like clients and and this infrastructure 01:35:14.900 --> 01:35:17.750 align:start position:0% like clients and and this infrastructure will<01:35:15.170> come<01:35:15.350> in<01:35:15.410> phase<01:35:15.590> one<01:35:15.800> and<01:35:15.980> we<01:35:16.490> also<01:35:16.640> have 01:35:17.750 --> 01:35:17.760 align:start position:0% will come in phase one and we also have 01:35:17.760 --> 01:35:19.740 align:start position:0% will come in phase one and we also have [Music] 01:35:19.740 --> 01:35:19.750 align:start position:0% [Music] 01:35:19.750 --> 01:35:22.990 align:start position:0% [Music] CBC<01:35:20.750> Ghost<01:35:21.020> which<01:35:21.260> is<01:35:21.410> e<01:35:22.100> CBC<01:35:22.430> Casper<01:35:22.760> which<01:35:22.910> I 01:35:22.990 --> 01:35:23.000 align:start position:0% CBC Ghost which is e CBC Casper which I 01:35:23.000 --> 01:35:26.440 align:start position:0% CBC Ghost which is e CBC Casper which I haven't<01:35:23.150> listed<01:35:23.390> here<01:35:23.690> and<01:35:24.280> then<01:35:25.280> kind<01:35:25.850> of<01:35:25.970> to 01:35:26.440 --> 01:35:26.450 align:start position:0% haven't listed here and then kind of to 01:35:26.450 --> 01:35:31.420 align:start position:0% haven't listed here and then kind of to two<01:35:26.990> other<01:35:27.230> ways<01:35:27.440> in<01:35:27.710> which<01:35:27.740> we<01:35:30.010> we<01:35:31.010> may 01:35:31.420 --> 01:35:31.430 align:start position:0% two other ways in which we we may 01:35:31.430 --> 01:35:35.020 align:start position:0% two other ways in which we we may upgrade<01:35:31.700> the<01:35:32.570> beacon<01:35:32.840> chain<01:35:33.050> is<01:35:33.260> to<01:35:34.190> have 01:35:35.020 --> 01:35:35.030 align:start position:0% upgrade the beacon chain is to have 01:35:35.030 --> 01:35:37.930 align:start position:0% upgrade the beacon chain is to have multi<01:35:35.360> hashing<01:35:35.780> so<01:35:35.930> instead<01:35:36.230> of<01:35:36.290> having<01:35:36.940> one 01:35:37.930 --> 01:35:37.940 align:start position:0% multi hashing so instead of having one 01:35:37.940 --> 01:35:40.720 align:start position:0% multi hashing so instead of having one single<01:35:38.180> hash<01:35:38.570> function<01:35:38.990> sha-256<01:35:39.950> we<01:35:40.490> might 01:35:40.720 --> 01:35:40.730 align:start position:0% single hash function sha-256 we might 01:35:40.730 --> 01:35:43.300 align:start position:0% single hash function sha-256 we might add<01:35:41.690> native<01:35:42.230> support<01:35:42.410> for<01:35:42.650> another<01:35:42.950> hash 01:35:43.300 --> 01:35:43.310 align:start position:0% add native support for another hash 01:35:43.310 --> 01:35:46.240 align:start position:0% add native support for another hash function<01:35:43.760> one<01:35:44.660> which<01:35:44.870> could<01:35:45.080> be<01:35:45.260> friendly<01:35:46.040> to 01:35:46.240 --> 01:35:46.250 align:start position:0% function one which could be friendly to 01:35:46.250 --> 01:35:50.950 align:start position:0% function one which could be friendly to stocks<01:35:46.640> and<01:35:46.970> to<01:35:47.120> stocks<01:35:48.580> and<01:35:49.580> you<01:35:50.120> know<01:35:50.690> later 01:35:50.950 --> 01:35:50.960 align:start position:0% stocks and to stocks and you know later 01:35:50.960 --> 01:35:52.480 align:start position:0% stocks and to stocks and you know later down<01:35:51.170> the<01:35:51.200> line<01:35:51.380> we're<01:35:51.740> also<01:35:51.860> looking<01:35:52.160> to 01:35:52.480 --> 01:35:52.490 align:start position:0% down the line we're also looking to 01:35:52.490 --> 01:35:54.100 align:start position:0% down the line we're also looking to change<01:35:53.390> the<01:35:53.690> various<01:35:53.930> cryptographic 01:35:54.100 --> 01:35:54.110 align:start position:0% change the various cryptographic 01:35:54.110 --> 01:35:57.120 align:start position:0% change the various cryptographic primitives<01:35:54.920> which<01:35:55.550> are<01:35:55.760> not<01:35:56.150> quantum<01:35:56.510> secure 01:35:57.120 --> 01:35:57.130 align:start position:0% primitives which are not quantum secure 01:35:57.130 --> 01:35:59.770 align:start position:0% primitives which are not quantum secure and<01:35:58.130> change<01:35:58.550> them<01:35:58.700> over<01:35:58.940> to<01:35:59.090> quantum<01:35:59.420> secure 01:35:59.770 --> 01:35:59.780 align:start position:0% and change them over to quantum secure 01:35:59.780 --> 01:36:02.860 align:start position:0% and change them over to quantum secure equivalents<01:36:00.350> and<01:36:00.530> so<01:36:01.220> this<01:36:01.400> includes<01:36:01.640> BLS<01:36:02.630> 12 01:36:02.860 --> 01:36:02.870 align:start position:0% equivalents and so this includes BLS 12 01:36:02.870 --> 01:36:04.600 align:start position:0% equivalents and so this includes BLS 12 381<01:36:03.380> which<01:36:03.560> is<01:36:03.680> not<01:36:03.800> quite<01:36:03.890> and<01:36:04.100> secure<01:36:04.430> and 01:36:04.600 --> 01:36:04.610 align:start position:0% 381 which is not quite and secure and 01:36:04.610 --> 01:36:08.440 align:start position:0% 381 which is not quite and secure and also<01:36:05.180> the<01:36:05.510> RSA<01:36:05.930> based<01:36:06.310> vdf<01:36:07.310> which<01:36:08.120> is<01:36:08.270> not 01:36:08.440 --> 01:36:08.450 align:start position:0% also the RSA based vdf which is not 01:36:08.450 --> 01:36:11.440 align:start position:0% also the RSA based vdf which is not quantum<01:36:08.750> secure<01:36:09.790> so<01:36:10.790> I<01:36:10.820> guess<01:36:11.030> that<01:36:11.180> will<01:36:11.270> keep 01:36:11.440 --> 01:36:11.450 align:start position:0% quantum secure so I guess that will keep 01:36:11.450 --> 01:36:15.760 align:start position:0% quantum secure so I guess that will keep us<01:36:11.630> busy<01:36:11.840> for<01:36:12.260> a<01:36:12.290> few<01:36:12.350> years<01:36:13.480> and<01:36:14.500> yeah<01:36:15.500> that's 01:36:15.760 --> 01:36:15.770 align:start position:0% us busy for a few years and yeah that's 01:36:15.770 --> 01:36:21.800 align:start position:0% us busy for a few years and yeah that's it<01:36:15.980> Thanks 01:36:21.800 --> 01:36:21.810 align:start position:0% 01:36:21.810 --> 01:36:24.540 align:start position:0% [Applause] 01:36:24.540 --> 01:36:24.550 align:start position:0% [Applause] 01:36:24.550 --> 01:36:28.480 align:start position:0% [Applause] Thank<01:36:25.550> You<01:36:25.610> Justin<01:36:26.170> I'm<01:36:27.170> gonna<01:36:27.530> close<01:36:28.130> it<01:36:28.400> out 01:36:28.480 --> 01:36:28.490 align:start position:0% Thank You Justin I'm gonna close it out 01:36:28.490 --> 01:36:32.080 align:start position:0% Thank You Justin I'm gonna close it out talking<01:36:29.090> about<01:36:29.330> the<01:36:29.570> validator<01:36:30.260> duties<01:36:30.680> in<01:36:31.090> or 01:36:32.080 --> 01:36:32.090 align:start position:0% talking about the validator duties in or 01:36:32.090 --> 01:36:37.480 align:start position:0% talking about the validator duties in or as<01:36:32.980> age<01:36:33.980> says<01:36:34.370> duties<01:36:36.100> I'm<01:36:37.100> talking<01:36:37.310> about<01:36:37.340> the 01:36:37.480 --> 01:36:37.490 align:start position:0% as age says duties I'm talking about the 01:36:37.490 --> 01:36:39.640 align:start position:0% as age says duties I'm talking about the validator<01:36:37.850> duties<01:36:38.150> in<01:36:38.300> phase<01:36:38.450> zero<01:36:38.690> some<01:36:39.470> of 01:36:39.640 --> 01:36:39.650 align:start position:0% validator duties in phase zero some of 01:36:39.650 --> 01:36:42.010 align:start position:0% validator duties in phase zero some of this<01:36:39.860> if<01:36:40.190> you<01:36:40.670> actually<01:36:40.970> look<01:36:41.510> at<01:36:41.630> the<01:36:41.780> phase 01:36:42.010 --> 01:36:42.020 align:start position:0% this if you actually look at the phase 01:36:42.020 --> 01:36:45.880 align:start position:0% this if you actually look at the phase zero<01:36:42.350> state<01:36:43.160> transition<01:36:43.610> spec<01:36:43.910> the<01:36:44.890> validity 01:36:45.880 --> 01:36:45.890 align:start position:0% zero state transition spec the validity 01:36:45.890 --> 01:36:47.950 align:start position:0% zero state transition spec the validity conditions<01:36:46.490> that<01:36:46.700> Justin<01:36:47.120> didn't<01:36:47.480> go<01:36:47.660> into 01:36:47.950 --> 01:36:47.960 align:start position:0% conditions that Justin didn't go into 01:36:47.960 --> 01:36:50.800 align:start position:0% conditions that Justin didn't go into kind<01:36:48.410> of<01:36:48.560> imply<01:36:49.060> what<01:36:50.060> a<01:36:50.090> validator<01:36:50.540> should<01:36:50.750> be 01:36:50.800 --> 01:36:50.810 align:start position:0% kind of imply what a validator should be 01:36:50.810 --> 01:36:52.960 align:start position:0% kind of imply what a validator should be doing<01:36:51.020> but<01:36:51.620> to<01:36:51.920> make<01:36:52.250> that<01:36:52.340> explicit<01:36:52.610> we<01:36:52.850> have 01:36:52.960 --> 01:36:52.970 align:start position:0% doing but to make that explicit we have 01:36:52.970 --> 01:36:54.370 align:start position:0% doing but to make that explicit we have the<01:36:53.060> separate<01:36:53.360> dock<01:36:53.570> and<01:36:53.810> when<01:36:54.200> I<01:36:54.260> was 01:36:54.370 --> 01:36:54.380 align:start position:0% the separate dock and when I was 01:36:54.380 --> 01:36:55.870 align:start position:0% the separate dock and when I was compiling<01:36:54.620> my<01:36:54.920> slides<01:36:55.190> I<01:36:55.460> thought<01:36:55.640> that<01:36:55.730> was<01:36:55.850> a 01:36:55.870 --> 01:36:55.880 align:start position:0% compiling my slides I thought that was a 01:36:55.880 --> 01:36:59.320 align:start position:0% compiling my slides I thought that was a good<01:36:55.970> idea<01:36:56.240> so<01:36:56.540> I<01:36:56.570> made<01:36:56.870> a<01:36:57.580> QR<01:36:58.580> code<01:36:58.790> and<01:36:59.000> a<01:36:59.090> tiny 01:36:59.320 --> 01:36:59.330 align:start position:0% good idea so I made a QR code and a tiny 01:36:59.330 --> 01:37:02.590 align:start position:0% good idea so I made a QR code and a tiny URL<01:36:59.680> so<01:37:00.680> this<01:37:00.830> document<01:37:01.340> which<01:37:02.240> I'll<01:37:02.360> go<01:37:02.480> over 01:37:02.590 --> 01:37:02.600 align:start position:0% URL so this document which I'll go over 01:37:02.600 --> 01:37:04.710 align:start position:0% URL so this document which I'll go over some<01:37:02.690> of<01:37:02.930> the<01:37:03.020> the<01:37:03.350> core<01:37:03.560> components<01:37:04.040> of<01:37:04.100> it 01:37:04.710 --> 01:37:04.720 align:start position:0% some of the the core components of it 01:37:04.720 --> 01:37:08.140 align:start position:0% some of the the core components of it explain<01:37:05.720> what<01:37:06.500> and<01:37:06.860> when<01:37:07.190> a<01:37:07.490> validator<01:37:07.910> should 01:37:08.140 --> 01:37:08.150 align:start position:0% explain what and when a validator should 01:37:08.150 --> 01:37:10.060 align:start position:0% explain what and when a validator should be<01:37:08.240> doing<01:37:08.540> with<01:37:09.350> respect<01:37:09.680> to<01:37:09.740> the<01:37:09.830> beacon 01:37:10.060 --> 01:37:10.070 align:start position:0% be doing with respect to the beacon 01:37:10.070 --> 01:37:13.060 align:start position:0% be doing with respect to the beacon chain<01:37:10.250> the<01:37:10.940> initial<01:37:11.630> part<01:37:12.080> of<01:37:12.260> this<01:37:12.500> document 01:37:13.060 --> 01:37:13.070 align:start position:0% chain the initial part of this document 01:37:13.070 --> 01:37:14.980 align:start position:0% chain the initial part of this document talks<01:37:13.400> about<01:37:13.730> creating<01:37:14.540> public<01:37:14.630> keys 01:37:14.980 --> 01:37:14.990 align:start position:0% talks about creating public keys 01:37:14.990 --> 01:37:17.940 align:start position:0% talks about creating public keys initiating<01:37:15.890> deposits<01:37:16.400> and<01:37:17.180> a<01:37:17.270> lot<01:37:17.450> of<01:37:17.480> that 01:37:17.940 --> 01:37:17.950 align:start position:0% initiating deposits and a lot of that 01:37:17.950 --> 01:37:21.310 align:start position:0% initiating deposits and a lot of that was<01:37:18.950> kind<01:37:19.250> of<01:37:19.400> covered<01:37:19.640> in<01:37:19.760> sha<01:37:19.940> ways<01:37:20.180> and<01:37:20.510> just 01:37:21.310 --> 01:37:21.320 align:start position:0% was kind of covered in sha ways and just 01:37:21.320 --> 01:37:23.950 align:start position:0% was kind of covered in sha ways and just will<01:37:21.530> be<01:37:21.650> out<01:37:21.890> of<01:37:22.130> scope<01:37:22.370> for<01:37:22.610> this<01:37:22.850> portion<01:37:23.750> so 01:37:23.950 --> 01:37:23.960 align:start position:0% will be out of scope for this portion so 01:37:23.960 --> 01:37:30.640 align:start position:0% will be out of scope for this portion so you<01:37:24.920> the<01:37:25.220> tooth<01:37:28.450> the<01:37:29.450> two<01:37:29.810> main<01:37:30.140> things<01:37:30.440> that 01:37:30.640 --> 01:37:30.650 align:start position:0% you the tooth the two main things that 01:37:30.650 --> 01:37:32.530 align:start position:0% you the tooth the two main things that you<01:37:30.800> do<01:37:31.070> in<01:37:31.280> phase<01:37:31.460> zero<01:37:31.760> is<01:37:32.000> you<01:37:32.210> propose 01:37:32.530 --> 01:37:32.540 align:start position:0% you do in phase zero is you propose 01:37:32.540 --> 01:37:36.480 align:start position:0% you do in phase zero is you propose blocks<01:37:32.840> and<01:37:33.080> you<01:37:33.140> attest<01:37:33.410> to<01:37:33.500> blocks<01:37:34.300> in 01:37:36.480 --> 01:37:36.490 align:start position:0% blocks and you attest to blocks in 01:37:36.490 --> 01:37:39.310 align:start position:0% blocks and you attest to blocks in subsequent<01:37:37.490> phases<01:37:37.790> you<01:37:38.450> would<01:37:38.600> do<01:37:38.780> similar 01:37:39.310 --> 01:37:39.320 align:start position:0% subsequent phases you would do similar 01:37:39.320 --> 01:37:44.290 align:start position:0% subsequent phases you would do similar activity<01:37:39.830> but<01:37:40.010> also<01:37:40.220> on<01:37:41.410> chart<01:37:42.410> chains<01:37:43.000> so<01:37:44.000> we 01:37:44.290 --> 01:37:44.300 align:start position:0% activity but also on chart chains so we 01:37:44.300 --> 01:37:46.330 align:start position:0% activity but also on chart chains so we have<01:37:44.420> some<01:37:44.570> stuff<01:37:44.660> going<01:37:44.930> on<01:37:45.050> pretty<01:37:45.980> much<01:37:46.130> at 01:37:46.330 --> 01:37:46.340 align:start position:0% have some stuff going on pretty much at 01:37:46.340 --> 01:37:48.070 align:start position:0% have some stuff going on pretty much at any<01:37:46.370> given<01:37:46.700> slot<01:37:47.000> you<01:37:47.300> can<01:37:47.450> say<01:37:47.630> am<01:37:47.870> i<01:37:48.020> the 01:37:48.070 --> 01:37:48.080 align:start position:0% any given slot you can say am i the 01:37:48.080 --> 01:37:51.180 align:start position:0% any given slot you can say am i the proposer<01:37:48.410> and<01:37:48.770> if<01:37:48.920> you<01:37:49.010> are<01:37:49.160> make<01:37:49.730> a<01:37:49.760> block 01:37:51.180 --> 01:37:51.190 align:start position:0% proposer and if you are make a block 01:37:51.190 --> 01:37:55.780 align:start position:0% proposer and if you are make a block this<01:37:52.190> can<01:37:52.610> be<01:37:52.930> this<01:37:53.930> is<01:37:54.080> independent<01:37:54.530> of<01:37:55.010> your 01:37:55.780 --> 01:37:55.790 align:start position:0% this can be this is independent of your 01:37:55.790 --> 01:37:57.250 align:start position:0% this can be this is independent of your at<01:37:56.090> the<01:37:56.390> station<01:37:56.720> committee<01:37:57.020> your 01:37:57.250 --> 01:37:57.260 align:start position:0% at the station committee your 01:37:57.260 --> 01:37:58.690 align:start position:0% at the station committee your cross-linked<01:37:57.770> committee<01:37:57.980> assignment<01:37:58.490> and 01:37:58.690 --> 01:37:58.700 align:start position:0% cross-linked committee assignment and 01:37:58.700 --> 01:38:02.920 align:start position:0% cross-linked committee assignment and it's<01:37:59.060> Noble<01:37:59.630> within<01:38:00.020> the<01:38:00.200> epoch<01:38:00.740> of<01:38:01.930> of 01:38:02.920 --> 01:38:02.930 align:start position:0% it's Noble within the epoch of of 01:38:02.930 --> 01:38:04.780 align:start position:0% it's Noble within the epoch of of assignment<01:38:03.650> you<01:38:03.830> you<01:38:04.160> don't<01:38:04.400> have<01:38:04.550> a<01:38:04.610> look 01:38:04.780 --> 01:38:04.790 align:start position:0% assignment you you don't have a look 01:38:04.790 --> 01:38:06.880 align:start position:0% assignment you you don't have a look ahead<01:38:04.970> in<01:38:05.360> a<01:38:05.690> prior<01:38:05.900> epoch<01:38:06.260> which<01:38:06.440> is<01:38:06.560> also 01:38:06.880 --> 01:38:06.890 align:start position:0% ahead in a prior epoch which is also 01:38:06.890 --> 01:38:08.260 align:start position:0% ahead in a prior epoch which is also different<01:38:07.190> from<01:38:07.310> the<01:38:07.520> committee<01:38:07.790> assignments 01:38:08.260 --> 01:38:08.270 align:start position:0% different from the committee assignments 01:38:08.270 --> 01:38:12.250 align:start position:0% different from the committee assignments and<01:38:09.260> the<01:38:09.830> action<01:38:10.430> of<01:38:10.690> proposing<01:38:11.690> a<01:38:11.780> block<01:38:11.990> is 01:38:12.250 --> 01:38:12.260 align:start position:0% and the action of proposing a block is 01:38:12.260 --> 01:38:13.530 align:start position:0% and the action of proposing a block is is<01:38:12.650> at<01:38:12.980> the 01:38:13.530 --> 01:38:13.540 align:start position:0% is at the 01:38:13.540 --> 01:38:17.040 align:start position:0% is at the the<01:38:13.890> initial<01:38:14.890> start<01:38:15.400> of<01:38:15.640> a<01:38:15.730> slot<01:38:15.970> so<01:38:16.420> slot<01:38:16.780> ten 01:38:17.040 --> 01:38:17.050 align:start position:0% the initial start of a slot so slot ten 01:38:17.050 --> 01:38:19.200 align:start position:0% the initial start of a slot so slot ten starts<01:38:17.440> I<01:38:17.560> make<01:38:17.800> my<01:38:17.980> block<01:38:18.190> I<01:38:18.490> give<01:38:18.940> it<01:38:19.030> to<01:38:19.120> the 01:38:19.200 --> 01:38:19.210 align:start position:0% starts I make my block I give it to the 01:38:19.210 --> 01:38:23.610 align:start position:0% starts I make my block I give it to the world<01:38:19.470> and<01:38:20.470> this<01:38:21.250> is<01:38:21.600> this<01:38:22.600> is<01:38:22.780> your<01:38:23.320> proposal 01:38:23.610 --> 01:38:23.620 align:start position:0% world and this is this is your proposal 01:38:23.620 --> 01:38:27.380 align:start position:0% world and this is this is your proposal is<01:38:23.980> publicly<01:38:24.640> publicly<01:38:25.180> known<01:38:25.390> and<01:38:26.380> so<01:38:26.710> as 01:38:27.380 --> 01:38:27.390 align:start position:0% is publicly publicly known and so as 01:38:27.390 --> 01:38:29.760 align:start position:0% is publicly publicly known and so as Justin<01:38:28.390> talked<01:38:28.720> about<01:38:28.900> secretly<01:38:29.290> to<01:38:29.380> election 01:38:29.760 --> 01:38:29.770 align:start position:0% Justin talked about secretly to election 01:38:29.770 --> 01:38:32.060 align:start position:0% Justin talked about secretly to election of<01:38:29.830> something<01:38:30.010> that<01:38:30.100> we're<01:38:30.220> looking<01:38:30.430> at<01:38:30.520> you 01:38:32.060 --> 01:38:32.070 align:start position:0% of something that we're looking at you 01:38:32.070 --> 01:38:34.200 align:start position:0% of something that we're looking at you computing<01:38:33.070> the<01:38:33.130> proposer<01:38:33.520> index<01:38:33.940> is 01:38:34.200 --> 01:38:34.210 align:start position:0% computing the proposer index is 01:38:34.210 --> 01:38:36.620 align:start position:0% computing the proposer index is essentially<01:38:34.780> taking<01:38:35.710> all<01:38:35.770> the<01:38:35.860> validators 01:38:36.620 --> 01:38:36.630 align:start position:0% essentially taking all the validators 01:38:36.630 --> 01:38:39.990 align:start position:0% essentially taking all the validators shuffling<01:38:37.630> them<01:38:37.810> and<01:38:38.220> using<01:38:39.220> some<01:38:39.370> some<01:38:39.910> of 01:38:39.990 --> 01:38:40.000 align:start position:0% shuffling them and using some some of 01:38:40.000 --> 01:38:41.820 align:start position:0% shuffling them and using some some of the<01:38:40.060> recent<01:38:40.360> randomness<01:38:40.750> along<01:38:41.260> with<01:38:41.500> their 01:38:41.820 --> 01:38:41.830 align:start position:0% the recent randomness along with their 01:38:41.830 --> 01:38:47.040 align:start position:0% the recent randomness along with their effective<01:38:42.370> balance<01:38:42.490> to<01:38:43.260> sample<01:38:44.260> them<01:38:46.050> great 01:38:47.040 --> 01:38:47.050 align:start position:0% effective balance to sample them great 01:38:47.050 --> 01:38:49.080 align:start position:0% effective balance to sample them great so<01:38:47.410> you<01:38:47.470> the<01:38:47.890> the<01:38:48.280> chance<01:38:48.790> of<01:38:48.970> you<01:38:49.060> being 01:38:49.080 --> 01:38:49.090 align:start position:0% so you the the chance of you being 01:38:49.090 --> 01:38:50.700 align:start position:0% so you the the chance of you being selected<01:38:49.720> is<01:38:49.810> also<01:38:50.020> proportional<01:38:50.290> to<01:38:50.650> your 01:38:50.700 --> 01:38:50.710 align:start position:0% selected is also proportional to your 01:38:50.710 --> 01:38:54.870 align:start position:0% selected is also proportional to your balance<01:38:51.070> most<01:38:52.740> most<01:38:53.740> validators<01:38:54.490> and<01:38:54.670> normal 01:38:54.870 --> 01:38:54.880 align:start position:0% balance most most validators and normal 01:38:54.880 --> 01:38:56.190 align:start position:0% balance most most validators and normal operating<01:38:55.180> conditions<01:38:55.630> would<01:38:55.810> have<01:38:56.020> an 01:38:56.190 --> 01:38:56.200 align:start position:0% operating conditions would have an 01:38:56.200 --> 01:38:58.380 align:start position:0% operating conditions would have an effective<01:38:56.770> balance<01:38:56.950> as<01:38:57.400> we<01:38:57.550> call<01:38:57.760> which<01:38:58.270> is 01:38:58.380 --> 01:38:58.390 align:start position:0% effective balance as we call which is 01:38:58.390 --> 01:39:00.300 align:start position:0% effective balance as we call which is capped<01:38:58.660> out<01:38:58.840> at<01:38:58.900> the<01:38:59.170> max<01:38:59.410> which<01:38:59.830> is<01:38:59.860> capped 01:39:00.300 --> 01:39:00.310 align:start position:0% capped out at the max which is capped 01:39:00.310 --> 01:39:03.990 align:start position:0% capped out at the max which is capped out<01:39:00.400> of<01:39:00.550> 32<01:39:00.790> so<01:39:01.750> most<01:39:01.990> in<01:39:02.350> many<01:39:03.280> situations 01:39:03.990 --> 01:39:04.000 align:start position:0% out of 32 so most in many situations 01:39:04.000 --> 01:39:07.650 align:start position:0% out of 32 so most in many situations that<01:39:04.390> be<01:39:04.900> an<01:39:05.550> equal<01:39:06.550> equivalent<01:39:07.270> chance<01:39:07.510> of 01:39:07.650 --> 01:39:07.660 align:start position:0% that be an equal equivalent chance of 01:39:07.660 --> 01:39:10.770 align:start position:0% that be an equal equivalent chance of being<01:39:07.780> selected<01:39:08.170> for<01:39:08.260> proposal<01:39:08.730> so<01:39:09.780> Justin 01:39:10.770 --> 01:39:10.780 align:start position:0% being selected for proposal so Justin 01:39:10.780 --> 01:39:12.780 align:start position:0% being selected for proposal so Justin are<01:39:11.500> you<01:39:11.560> talked<01:39:11.830> about<01:39:12.040> these<01:39:12.550> data 01:39:12.780 --> 01:39:12.790 align:start position:0% are you talked about these data 01:39:12.790 --> 01:39:15.060 align:start position:0% are you talked about these data structures<01:39:13.090> the<01:39:13.690> beacon<01:39:13.930> block<01:39:14.110> pikna<01:39:14.890> block 01:39:15.060 --> 01:39:15.070 align:start position:0% structures the beacon block pikna block 01:39:15.070 --> 01:39:18.900 align:start position:0% structures the beacon block pikna block body<01:39:15.280> what<01:39:16.270> I<01:39:16.300> do<01:39:16.510> is<01:39:17.140> I<01:39:17.350> reveal<01:39:18.280> my<01:39:18.490> R<01:39:18.520> and<01:39:18.730> L 01:39:18.900 --> 01:39:18.910 align:start position:0% body what I do is I reveal my R and L 01:39:18.910 --> 01:39:22.140 align:start position:0% body what I do is I reveal my R and L which<01:39:19.240> is<01:39:19.270> a<01:39:19.420> signature<01:39:19.780> upon<01:39:20.140> the<01:39:20.380> epoch<01:39:20.710> I<01:39:21.520> go 01:39:22.140 --> 01:39:22.150 align:start position:0% which is a signature upon the epoch I go 01:39:22.150 --> 01:39:23.430 align:start position:0% which is a signature upon the epoch I go and<01:39:22.330> find<01:39:22.390> my<01:39:22.600> eighth<01:39:22.750> one<01:39:22.900> data<01:39:23.110> which<01:39:23.290> I'll 01:39:23.430 --> 01:39:23.440 align:start position:0% and find my eighth one data which I'll 01:39:23.440 --> 01:39:25.380 align:start position:0% and find my eighth one data which I'll show<01:39:23.590> you<01:39:23.680> about<01:39:23.800> in<01:39:24.100> a<01:39:24.160> second<01:39:24.520> I<01:39:24.670> signed<01:39:25.240> some 01:39:25.380 --> 01:39:25.390 align:start position:0% show you about in a second I signed some 01:39:25.390 --> 01:39:27.570 align:start position:0% show you about in a second I signed some graffiti<01:39:25.600> maybe<01:39:26.320> I'll<01:39:26.590> vote<01:39:27.160> on<01:39:27.340> some 01:39:27.570 --> 01:39:27.580 align:start position:0% graffiti maybe I'll vote on some 01:39:27.580 --> 01:39:30.600 align:start position:0% graffiti maybe I'll vote on some proposal<01:39:28.060> or<01:39:28.300> I'll<01:39:28.450> say<01:39:29.290> things<01:39:29.350> about<01:39:29.620> Who<01:39:30.550> I 01:39:30.600 --> 01:39:30.610 align:start position:0% proposal or I'll say things about Who I 01:39:30.610 --> 01:39:34.250 align:start position:0% proposal or I'll say things about Who I am<01:39:31.050> and<01:39:32.050> I<01:39:32.710> fill<01:39:33.220> in<01:39:33.430> any<01:39:33.730> of<01:39:33.760> these<01:39:33.880> operations 01:39:34.250 --> 01:39:34.260 align:start position:0% am and I fill in any of these operations 01:39:34.260 --> 01:39:37.650 align:start position:0% am and I fill in any of these operations most<01:39:35.260> importantly<01:39:36.130> I'm<01:39:36.490> gathering<01:39:37.000> up<01:39:37.360> at<01:39:37.510> two 01:39:37.650 --> 01:39:37.660 align:start position:0% most importantly I'm gathering up at two 01:39:37.660 --> 01:39:39.390 align:start position:0% most importantly I'm gathering up at two stations<01:39:38.020> because<01:39:38.350> that's<01:39:38.560> how<01:39:38.770> I<01:39:38.800> make<01:39:39.190> my 01:39:39.390 --> 01:39:39.400 align:start position:0% stations because that's how I make my 01:39:39.400 --> 01:39:41.600 align:start position:0% stations because that's how I make my block<01:39:39.670> proposal<01:39:40.150> worth<01:39:40.330> it<01:39:40.510> and<01:39:40.630> profitable 01:39:41.600 --> 01:39:41.610 align:start position:0% block proposal worth it and profitable 01:39:41.610 --> 01:39:44.580 align:start position:0% block proposal worth it and profitable by<01:39:42.610> including<01:39:43.150> high<01:39:43.600> value<01:39:43.990> add<01:39:44.110> two<01:39:44.230> stations 01:39:44.580 --> 01:39:44.590 align:start position:0% by including high value add two stations 01:39:44.590 --> 01:39:46.710 align:start position:0% by including high value add two stations which<01:39:45.100> are<01:39:45.370> add<01:39:45.850> two<01:39:46.060> stations<01:39:46.360> that<01:39:46.480> have<01:39:46.600> not 01:39:46.710 --> 01:39:46.720 align:start position:0% which are add two stations that have not 01:39:46.720 --> 01:39:49.050 align:start position:0% which are add two stations that have not yet<01:39:46.930> been<01:39:47.110> included<01:39:47.590> a<01:39:48.220> decisions<01:39:48.850> that<01:39:48.970> are 01:39:49.050 --> 01:39:49.060 align:start position:0% yet been included a decisions that are 01:39:49.060 --> 01:39:50.670 align:start position:0% yet been included a decisions that are highly<01:39:49.360> aggregated<01:39:49.900> so<01:39:50.050> it<01:39:50.170> has<01:39:50.350> a<01:39:50.380> lot<01:39:50.650> of 01:39:50.670 --> 01:39:50.680 align:start position:0% highly aggregated so it has a lot of 01:39:50.680 --> 01:39:52.320 align:start position:0% highly aggregated so it has a lot of participants<01:39:51.220> in<01:39:51.430> them<01:39:51.550> and<01:39:51.730> add<01:39:52.180> two 01:39:52.320 --> 01:39:52.330 align:start position:0% participants in them and add two 01:39:52.330 --> 01:39:55.260 align:start position:0% participants in them and add two stations<01:39:52.720> that<01:39:53.200> are<01:39:53.380> a<01:39:53.410> more<01:39:54.040> recent<01:39:54.270> by 01:39:55.260 --> 01:39:55.270 align:start position:0% stations that are a more recent by 01:39:55.270 --> 01:39:57.240 align:start position:0% stations that are a more recent by optimizing<01:39:56.230> those<01:39:56.320> things<01:39:56.620> I<01:39:56.740> can<01:39:56.770> optimize 01:39:57.240 --> 01:39:57.250 align:start position:0% optimizing those things I can optimize 01:39:57.250 --> 01:40:00.630 align:start position:0% optimizing those things I can optimize my<01:39:57.670> reward<01:39:58.090> I<01:39:58.630> think<01:39:59.020> you<01:39:59.080> get<01:39:59.280> one-eighth<01:40:00.280> of 01:40:00.630 --> 01:40:00.640 align:start position:0% my reward I think you get one-eighth of 01:40:00.640 --> 01:40:02.940 align:start position:0% my reward I think you get one-eighth of the<01:40:00.730> reward<01:40:01.660> that<01:40:01.780> was<01:40:02.110> given<01:40:02.500> to<01:40:02.530> at<01:40:02.920> a 01:40:02.940 --> 01:40:02.950 align:start position:0% the reward that was given to at a 01:40:02.950 --> 01:40:05.310 align:start position:0% the reward that was given to at a stations<01:40:03.460> for<01:40:04.180> added<01:40:04.360> stations<01:40:04.660> you<01:40:04.990> receive 01:40:05.310 --> 01:40:05.320 align:start position:0% stations for added stations you receive 01:40:05.320 --> 01:40:10.110 align:start position:0% stations for added stations you receive yourself<01:40:06.000> so<01:40:07.000> in<01:40:07.350> general<01:40:08.350> by<01:40:08.830> proposing<01:40:09.550> by 01:40:10.110 --> 01:40:10.120 align:start position:0% yourself so in general by proposing by 01:40:10.120 --> 01:40:12.150 align:start position:0% yourself so in general by proposing by being<01:40:10.360> a<01:40:10.450> good<01:40:10.630> proposer<01:40:10.990> over<01:40:11.620> time<01:40:11.890> you're 01:40:12.150 --> 01:40:12.160 align:start position:0% being a good proposer over time you're 01:40:12.160 --> 01:40:15.800 align:start position:0% being a good proposer over time you're increasing<01:40:12.430> your<01:40:12.640> award<01:40:12.970> by<01:40:13.090> about<01:40:13.300> 1/8 01:40:15.800 --> 01:40:15.810 align:start position:0% 01:40:15.810 --> 01:40:20.160 align:start position:0% deposits<01:40:16.810> deposits<01:40:17.730> we<01:40:18.730> come<01:40:19.600> to<01:40:19.690> consensus 01:40:20.160 --> 01:40:20.170 align:start position:0% deposits deposits we come to consensus 01:40:20.170 --> 01:40:22.920 align:start position:0% deposits deposits we come to consensus upon<01:40:20.410> the<01:40:20.770> eath<01:40:20.920> one<01:40:21.160> data<01:40:21.480> which<01:40:22.480> is<01:40:22.660> some 01:40:22.920 --> 01:40:22.930 align:start position:0% upon the eath one data which is some 01:40:22.930 --> 01:40:25.200 align:start position:0% upon the eath one data which is some past<01:40:23.320> eath<01:40:23.980> block 01:40:25.200 --> 01:40:25.210 align:start position:0% past eath block 01:40:25.210 --> 01:40:28.800 align:start position:0% past eath block and<01:40:25.300> the<01:40:26.020> deposit<01:40:27.010> contract<01:40:27.600> deposit<01:40:28.600> route 01:40:28.800 --> 01:40:28.810 align:start position:0% and the deposit contract deposit route 01:40:28.810 --> 01:40:31.590 align:start position:0% and the deposit contract deposit route and<01:40:29.170> this<01:40:30.040> deposit<01:40:30.460> route<01:40:30.850> allows<01:40:31.210> us<01:40:31.450> to 01:40:31.590 --> 01:40:31.600 align:start position:0% and this deposit route allows us to 01:40:31.600 --> 01:40:35.490 align:start position:0% and this deposit route allows us to process<01:40:31.870> deposits<01:40:32.680> in<01:40:32.860> order<01:40:33.340> of<01:40:34.440> making<01:40:35.440> a 01:40:35.490 --> 01:40:35.500 align:start position:0% process deposits in order of making a 01:40:35.500 --> 01:40:37.380 align:start position:0% process deposits in order of making a proof<01:40:35.710> against<01:40:36.100> that<01:40:36.220> route<01:40:36.400> a<01:40:36.670> merkel<01:40:37.180> proof 01:40:37.380 --> 01:40:37.390 align:start position:0% proof against that route a merkel proof 01:40:37.390 --> 01:40:42.570 align:start position:0% proof against that route a merkel proof and<01:40:38.290> this<01:40:39.220> number<01:40:39.430> max<01:40:39.760> deposits<01:40:40.360> is<01:40:41.130> I<01:40:42.130> have 01:40:42.570 --> 01:40:42.580 align:start position:0% and this number max deposits is I have 01:40:42.580 --> 01:40:44.550 align:start position:0% and this number max deposits is I have to<01:40:42.760> I<01:40:43.150> have<01:40:43.180> to<01:40:43.720> buy<01:40:43.960> the<01:40:44.020> rules<01:40:44.320> of<01:40:44.470> the 01:40:44.550 --> 01:40:44.560 align:start position:0% to I have to buy the rules of the 01:40:44.560 --> 01:40:47.730 align:start position:0% to I have to buy the rules of the protocol<01:40:45.070> include<01:40:46.200> deposits<01:40:47.200> any 01:40:47.730 --> 01:40:47.740 align:start position:0% protocol include deposits any 01:40:47.740 --> 01:40:50.640 align:start position:0% protocol include deposits any unprocessed<01:40:48.520> deposits<01:40:49.000> up<01:40:49.180> into<01:40:49.690> that<01:40:50.410> max 01:40:50.640 --> 01:40:50.650 align:start position:0% unprocessed deposits up into that max 01:40:50.650 --> 01:40:52.440 align:start position:0% unprocessed deposits up into that max deposit<01:40:51.100> so<01:40:51.220> I<01:40:51.250> think<01:40:51.430> that's<01:40:51.580> the<01:40:51.760> number<01:40:51.970> 16 01:40:52.440 --> 01:40:52.450 align:start position:0% deposit so I think that's the number 16 01:40:52.450 --> 01:40:55.800 align:start position:0% deposit so I think that's the number 16 so<01:40:53.440> if<01:40:53.590> there<01:40:53.830> were<01:40:54.010> 32<01:40:54.880> deposits<01:40:55.480> that<01:40:55.750> are 01:40:55.800 --> 01:40:55.810 align:start position:0% so if there were 32 deposits that are 01:40:55.810 --> 01:40:57.990 align:start position:0% so if there were 32 deposits that are unprocessed<01:40:56.530> I<01:40:56.650> have<01:40:56.950> to<01:40:57.130> include<01:40:57.310> 16<01:40:57.670> if 01:40:57.990 --> 01:40:58.000 align:start position:0% unprocessed I have to include 16 if 01:40:58.000 --> 01:40:59.940 align:start position:0% unprocessed I have to include 16 if there<01:40:58.390> were<01:40:58.480> 2<01:40:58.660> I<01:40:58.870> include<01:40:59.230> the<01:40:59.380> 2<01:40:59.530> and<01:40:59.710> then<01:40:59.800> no 01:40:59.940 --> 01:40:59.950 align:start position:0% there were 2 I include the 2 and then no 01:40:59.950 --> 01:41:02.100 align:start position:0% there were 2 I include the 2 and then no more<01:41:00.100> if<01:41:00.340> there's<01:41:00.580> zero<01:41:00.670> zero 01:41:02.100 --> 01:41:02.110 align:start position:0% more if there's zero zero 01:41:02.110 --> 01:41:04.770 align:start position:0% more if there's zero zero I<01:41:02.170> also<01:41:03.100> voluntary<01:41:03.910> exits<01:41:04.300> might<01:41:04.480> be<01:41:04.600> flying 01:41:04.770 --> 01:41:04.780 align:start position:0% I also voluntary exits might be flying 01:41:04.780 --> 01:41:06.570 align:start position:0% I also voluntary exits might be flying around<01:41:04.960> on<01:41:05.170> the<01:41:05.230> network<01:41:05.500> I<01:41:05.740> can<01:41:06.280> pick<01:41:06.430> those 01:41:06.570 --> 01:41:06.580 align:start position:0% around on the network I can pick those 01:41:06.580 --> 01:41:08.550 align:start position:0% around on the network I can pick those up<01:41:06.610> put<01:41:07.120> them<01:41:07.270> in<01:41:07.390> I'm<01:41:07.810> kind<01:41:08.050> of<01:41:08.080> naturally 01:41:08.550 --> 01:41:08.560 align:start position:0% up put them in I'm kind of naturally 01:41:08.560 --> 01:41:10.200 align:start position:0% up put them in I'm kind of naturally incentivized<01:41:09.070> to<01:41:09.190> put<01:41:09.400> those<01:41:09.490> in<01:41:09.730> because<01:41:10.030> the 01:41:10.200 --> 01:41:10.210 align:start position:0% incentivized to put those in because the 01:41:10.210 --> 01:41:11.640 align:start position:0% incentivized to put those in because the fewer<01:41:10.420> validators<01:41:10.990> that<01:41:11.200> exist 01:41:11.640 --> 01:41:11.650 align:start position:0% fewer validators that exist 01:41:11.650 --> 01:41:15.420 align:start position:0% fewer validators that exist I'm<01:41:13.260> the<01:41:14.260> functions<01:41:14.620> a<01:41:14.710> little<01:41:14.890> bit<01:41:15.040> dynamic 01:41:15.420 --> 01:41:15.430 align:start position:0% I'm the functions a little bit dynamic 01:41:15.430 --> 01:41:19.290 align:start position:0% I'm the functions a little bit dynamic but<01:41:15.550> I<01:41:16.770> get<01:41:17.770> a<01:41:17.800> little<01:41:17.920> bit<01:41:18.160> less<01:41:18.340> overhead<01:41:19.060> and 01:41:19.290 --> 01:41:19.300 align:start position:0% but I get a little bit less overhead and 01:41:19.300 --> 01:41:22.380 align:start position:0% but I get a little bit less overhead and and<01:41:19.570> it's<01:41:19.900> nice<01:41:20.340> proposer<01:41:21.340> slashings<01:41:22.030> and<01:41:22.240> a 01:41:22.380 --> 01:41:22.390 align:start position:0% and it's nice proposer slashings and a 01:41:22.390 --> 01:41:24.810 align:start position:0% and it's nice proposer slashings and a tester<01:41:22.780> slashings<01:41:23.290> I<01:41:23.500> might<01:41:24.010> also<01:41:24.250> choose<01:41:24.640> to 01:41:24.810 --> 01:41:24.820 align:start position:0% tester slashings I might also choose to 01:41:24.820 --> 01:41:26.970 align:start position:0% tester slashings I might also choose to be<01:41:24.970> I<01:41:25.480> might<01:41:25.900> be<01:41:26.020> policing<01:41:26.590> the<01:41:26.710> network 01:41:26.970 --> 01:41:26.980 align:start position:0% be I might be policing the network 01:41:26.980 --> 01:41:30.060 align:start position:0% be I might be policing the network looking<01:41:27.370> for<01:41:27.580> nefarious<01:41:28.170> activity<01:41:29.170> and<01:41:29.830> if<01:41:29.950> I 01:41:30.060 --> 01:41:30.070 align:start position:0% looking for nefarious activity and if I 01:41:30.070 --> 01:41:32.040 align:start position:0% looking for nefarious activity and if I find<01:41:30.310> these<01:41:30.550> things<01:41:30.580> submit<01:41:31.210> proof<01:41:31.420> proof<01:41:31.840> of 01:41:32.040 --> 01:41:32.050 align:start position:0% find these things submit proof proof of 01:41:32.050 --> 01:41:35.610 align:start position:0% find these things submit proof proof of them<01:41:32.170> I<01:41:32.590> get<01:41:33.520> a<01:41:33.550> portion<01:41:34.180> of<01:41:34.390> the<01:41:34.810> I<01:41:35.080> I<01:41:35.140> get<01:41:35.590> a 01:41:35.610 --> 01:41:35.620 align:start position:0% them I get a portion of the I I get a 01:41:35.620 --> 01:41:37.560 align:start position:0% them I get a portion of the I I get a small<01:41:36.130> reward<01:41:36.280> a<01:41:36.580> small<01:41:36.970> amount<01:41:37.090> of<01:41:37.270> what<01:41:37.420> was 01:41:37.560 --> 01:41:37.570 align:start position:0% small reward a small amount of what was 01:41:37.570 --> 01:41:41.160 align:start position:0% small reward a small amount of what was slashed<01:41:38.340> so<01:41:39.340> we<01:41:39.460> can<01:41:39.640> look<01:41:39.910> into<01:41:40.540> a<01:41:40.570> little<01:41:41.080> bit 01:41:41.160 --> 01:41:41.170 align:start position:0% slashed so we can look into a little bit 01:41:41.170 --> 01:41:44.400 align:start position:0% slashed so we can look into a little bit more<01:41:41.350> into<01:41:41.590> this<01:41:41.710> eath<01:41:41.920> 1<01:41:42.100> data<01:41:43.410> essentially 01:41:44.400 --> 01:41:44.410 align:start position:0% more into this eath 1 data essentially 01:41:44.410 --> 01:41:47.040 align:start position:0% more into this eath 1 data essentially what<01:41:44.620> this<01:41:44.710> function<01:41:44.920> does<01:41:45.250> is<01:41:45.460> like<01:41:46.060> what<01:41:47.020> I 01:41:47.040 --> 01:41:47.050 align:start position:0% what this function does is like what I 01:41:47.050 --> 01:41:52.200 align:start position:0% what this function does is like what I call<01:41:47.260> a<01:41:47.290> pile-on<01:41:47.950> vote<01:41:48.250> like<01:41:49.440> once<01:41:50.440> I<01:41:50.740> see<01:41:51.210> we 01:41:52.200 --> 01:41:52.210 align:start position:0% call a pile-on vote like once I see we 01:41:52.210 --> 01:41:56.070 align:start position:0% call a pile-on vote like once I see we divide<01:41:52.510> the<01:41:54.390> voting<01:41:55.390> period<01:41:55.750> the<01:41:55.840> youth<01:41:55.930> 1 01:41:56.070 --> 01:41:56.080 align:start position:0% divide the voting period the youth 1 01:41:56.080 --> 01:41:57.870 align:start position:0% divide the voting period the youth 1 voting<01:41:56.350> period<01:41:56.680> into<01:41:56.890> a<01:41:57.160> number<01:41:57.640> of<01:41:57.730> epochs 01:41:57.870 --> 01:41:57.880 align:start position:0% voting period into a number of epochs 01:41:57.880 --> 01:42:01.860 align:start position:0% voting period into a number of epochs and<01:41:58.330> if<01:41:59.050> I<01:41:59.200> see<01:41:59.730> good<01:42:00.730> votes<01:42:01.030> for<01:42:01.570> each<01:42:01.600> one 01:42:01.860 --> 01:42:01.870 align:start position:0% and if I see good votes for each one 01:42:01.870 --> 01:42:04.170 align:start position:0% and if I see good votes for each one data<01:42:02.080> I<01:42:02.380> just<01:42:02.860> picked<01:42:03.130> that<01:42:03.220> vote<01:42:03.520> and<01:42:03.760> and<01:42:04.060> I 01:42:04.170 --> 01:42:04.180 align:start position:0% data I just picked that vote and and I 01:42:04.180 --> 01:42:06.900 align:start position:0% data I just picked that vote and and I and<01:42:04.390> I<01:42:04.510> vote<01:42:04.690> on<01:42:04.840> it<01:42:04.990> some<01:42:05.860> of<01:42:05.980> the<01:42:06.100> some<01:42:06.760> of<01:42:06.790> the 01:42:06.900 --> 01:42:06.910 align:start position:0% and I vote on it some of the some of the 01:42:06.910 --> 01:42:10.170 align:start position:0% and I vote on it some of the some of the mechanism<01:42:07.360> in<01:42:07.450> here<01:42:07.690> is<01:42:07.810> to<01:42:08.410> prevent<01:42:09.180> me 01:42:10.170 --> 01:42:10.180 align:start position:0% mechanism in here is to prevent me 01:42:10.180 --> 01:42:12.420 align:start position:0% mechanism in here is to prevent me piling<01:42:10.810> on<01:42:10.960> to<01:42:11.140> votes<01:42:11.350> that<01:42:11.710> were<01:42:11.860> that<01:42:12.280> were<01:42:12.400> a 01:42:12.420 --> 01:42:12.430 align:start position:0% piling on to votes that were that were a 01:42:12.430 --> 01:42:14.160 align:start position:0% piling on to votes that were that were a little<01:42:12.670> bit<01:42:12.880> stale<01:42:13.120> so<01:42:13.390> early<01:42:13.780> on<01:42:13.930> in<01:42:14.110> the 01:42:14.160 --> 01:42:14.170 align:start position:0% little bit stale so early on in the 01:42:14.170 --> 01:42:16.650 align:start position:0% little bit stale so early on in the period<01:42:14.560> if<01:42:14.740> that's<01:42:15.280> less<01:42:15.970> than<01:42:16.240> the<01:42:16.330> integer 01:42:16.650 --> 01:42:16.660 align:start position:0% period if that's less than the integer 01:42:16.660 --> 01:42:18.330 align:start position:0% period if that's less than the integer square<01:42:16.960> root<01:42:17.140> of<01:42:17.350> the<01:42:17.500> slots<01:42:17.740> per<01:42:18.040> Earth<01:42:18.190> one 01:42:18.330 --> 01:42:18.340 align:start position:0% square root of the slots per Earth one 01:42:18.340 --> 01:42:23.100 align:start position:0% square root of the slots per Earth one data<01:42:18.550> period<01:42:18.940> I<01:42:19.210> am<01:42:20.310> will<01:42:21.310> not<01:42:21.730> pile<01:42:22.720> on<01:42:22.930> my 01:42:23.100 --> 01:42:23.110 align:start position:0% data period I am will not pile on my 01:42:23.110 --> 01:42:24.690 align:start position:0% data period I am will not pile on my vote<01:42:23.320> if<01:42:23.560> it<01:42:23.890> looks<01:42:24.100> like<01:42:24.250> someone<01:42:24.610> was 01:42:24.690 --> 01:42:24.700 align:start position:0% vote if it looks like someone was 01:42:24.700 --> 01:42:26.760 align:start position:0% vote if it looks like someone was putting<01:42:25.060> in<01:42:25.240> some<01:42:25.420> stale<01:42:25.600> information<01:42:26.080> but 01:42:26.760 --> 01:42:26.770 align:start position:0% putting in some stale information but 01:42:26.770 --> 01:42:28.350 align:start position:0% putting in some stale information but otherwise<01:42:27.040> I<01:42:27.100> just<01:42:27.250> vote<01:42:27.550> on<01:42:27.580> what<01:42:28.150> the 01:42:28.350 --> 01:42:28.360 align:start position:0% otherwise I just vote on what the 01:42:28.360 --> 01:42:31.080 align:start position:0% otherwise I just vote on what the majority<01:42:28.510> is<01:42:29.140> and<01:42:29.500> is<01:42:29.620> valid<01:42:29.950> if<01:42:30.610> there's<01:42:30.880> no 01:42:31.080 --> 01:42:31.090 align:start position:0% majority is and is valid if there's no 01:42:31.090 --> 01:42:31.790 align:start position:0% majority is and is valid if there's no votes 01:42:31.790 --> 01:42:31.800 align:start position:0% votes 01:42:31.800 --> 01:42:34.209 align:start position:0% votes [Music] 01:42:34.209 --> 01:42:34.219 align:start position:0% [Music] 01:42:34.219 --> 01:42:37.930 align:start position:0% [Music] the<01:42:35.219> default<01:42:35.670> I<01:42:35.820> go<01:42:36.179> get<01:42:36.449> my<01:42:36.480> oneth<01:42:36.989> one<01:42:37.170> data 01:42:37.930 --> 01:42:37.940 align:start position:0% the default I go get my oneth one data 01:42:37.940 --> 01:42:41.350 align:start position:0% the default I go get my oneth one data and<01:42:38.940> what<01:42:39.179> what<01:42:39.449> we<01:42:39.480> do<01:42:39.690> in<01:42:39.840> this<01:42:39.960> this<01:42:40.440> initial 01:42:41.350 --> 01:42:41.360 align:start position:0% and what what we do in this this initial 01:42:41.360 --> 01:42:44.510 align:start position:0% and what what we do in this this initial release<01:42:42.360> is<01:42:42.630> that<01:42:42.659> we<01:42:43.380> follow<01:42:43.739> the<01:42:44.159> eighth<01:42:44.280> one 01:42:44.510 --> 01:42:44.520 align:start position:0% release is that we follow the eighth one 01:42:44.520 --> 01:42:47.570 align:start position:0% release is that we follow the eighth one chain<01:42:44.820> by<01:42:45.030> like<01:42:45.179> a<01:42:45.210> thousand<01:42:45.750> blocks<01:42:46.429> to<01:42:47.429> be 01:42:47.570 --> 01:42:47.580 align:start position:0% chain by like a thousand blocks to be 01:42:47.580 --> 01:42:51.800 align:start position:0% chain by like a thousand blocks to be safe<01:42:47.820> this<01:42:48.090> is<01:42:48.239> not<01:42:48.420> the<01:42:49.020> eighth<01:42:49.199> one<01:42:50.810> the 01:42:51.800 --> 01:42:51.810 align:start position:0% safe this is not the eighth one the 01:42:51.810 --> 01:42:53.750 align:start position:0% safe this is not the eighth one the beacon<01:42:52.110> chain<01:42:52.320> cannot<01:42:52.650> handle<01:42:53.159> if<01:42:53.429> there<01:42:53.670> were 01:42:53.750 --> 01:42:53.760 align:start position:0% beacon chain cannot handle if there were 01:42:53.760 --> 01:42:56.720 align:start position:0% beacon chain cannot handle if there were a<01:42:53.790> reorg<01:42:54.150> past<01:42:54.449> that<01:42:54.690> and<01:42:54.929> the<01:42:55.770> eath<01:42:56.310> one<01:42:56.520> chain 01:42:56.720 --> 01:42:56.730 align:start position:0% a reorg past that and the eath one chain 01:42:56.730 --> 01:42:58.520 align:start position:0% a reorg past that and the eath one chain knows<01:42:56.969> nothing<01:42:57.360> about<01:42:57.420> the<01:42:57.690> beacon<01:42:57.900> chain<01:42:58.110> so 01:42:58.520 --> 01:42:58.530 align:start position:0% knows nothing about the beacon chain so 01:42:58.530 --> 01:43:02.270 align:start position:0% knows nothing about the beacon chain so this<01:42:58.679> is<01:42:58.830> an<01:42:59.040> assumed<01:43:00.290> safe<01:43:01.290> distance<01:43:02.010> to 01:43:02.270 --> 01:43:02.280 align:start position:0% this is an assumed safe distance to 01:43:02.280 --> 01:43:04.040 align:start position:0% this is an assumed safe distance to follow<01:43:02.489> the<01:43:02.670> chain<01:43:02.909> and<01:43:03.120> so<01:43:03.480> you<01:43:03.540> do<01:43:03.719> have<01:43:03.900> like 01:43:04.040 --> 01:43:04.050 align:start position:0% follow the chain and so you do have like 01:43:04.050 --> 01:43:06.050 align:start position:0% follow the chain and so you do have like an<01:43:04.230> induced<01:43:04.530> latency<01:43:05.010> on<01:43:05.190> handling<01:43:05.550> deposits 01:43:06.050 --> 01:43:06.060 align:start position:0% an induced latency on handling deposits 01:43:06.060 --> 01:43:08.630 align:start position:0% an induced latency on handling deposits because<01:43:06.300> of<01:43:06.449> that<01:43:06.540> I'm<01:43:07.469> not<01:43:07.530> certain<01:43:08.400> what<01:43:08.429> the 01:43:08.630 --> 01:43:08.640 align:start position:0% because of that I'm not certain what the 01:43:08.640 --> 01:43:10.970 align:start position:0% because of that I'm not certain what the most<01:43:08.940> deep<01:43:09.179> reorg<01:43:09.719> has<01:43:09.960> ever<01:43:10.440> been<01:43:10.710> in<01:43:10.860> eath 01:43:10.970 --> 01:43:10.980 align:start position:0% most deep reorg has ever been in eath 01:43:10.980 --> 01:43:13.850 align:start position:0% most deep reorg has ever been in eath one<01:43:11.219> but<01:43:11.790> it's<01:43:11.940> not<01:43:12.360> even<01:43:12.719> on<01:43:13.260> the<01:43:13.560> order<01:43:13.800> of 01:43:13.850 --> 01:43:13.860 align:start position:0% one but it's not even on the order of 01:43:13.860 --> 01:43:16.520 align:start position:0% one but it's not even on the order of like<01:43:13.980> 100<01:43:14.190> so<01:43:14.909> assumed<01:43:15.870> to<01:43:15.960> be<01:43:16.020> safe<01:43:16.260> unless 01:43:16.520 --> 01:43:16.530 align:start position:0% like 100 so assumed to be safe unless 01:43:16.530 --> 01:43:18.410 align:start position:0% like 100 so assumed to be safe unless there<01:43:16.770> was<01:43:16.830> an<01:43:17.040> attack<01:43:17.489> if<01:43:17.760> there<01:43:18.210> was<01:43:18.330> an 01:43:18.410 --> 01:43:18.420 align:start position:0% there was an attack if there was an 01:43:18.420 --> 01:43:19.640 align:start position:0% there was an attack if there was an attack 01:43:19.640 --> 01:43:19.650 align:start position:0% attack 01:43:19.650 --> 01:43:21.770 align:start position:0% attack maybe<01:43:20.640> we<01:43:20.790> should<01:43:20.969> revert<01:43:21.270> the<01:43:21.420> eath<01:43:21.540> one 01:43:21.770 --> 01:43:21.780 align:start position:0% maybe we should revert the eath one 01:43:21.780 --> 01:43:23.209 align:start position:0% maybe we should revert the eath one chain<01:43:22.020> instead<01:43:22.350> of<01:43:22.440> the<01:43:22.710> beacon<01:43:23.070> chain 01:43:23.209 --> 01:43:23.219 align:start position:0% chain instead of the beacon chain 01:43:23.219 --> 01:43:25.490 align:start position:0% chain instead of the beacon chain because<01:43:23.460> it<01:43:23.610> was<01:43:23.699> attacked<01:43:24.030> but<01:43:24.989> that's 01:43:25.490 --> 01:43:25.500 align:start position:0% because it was attacked but that's 01:43:25.500 --> 01:43:32.360 align:start position:0% because it was attacked but that's mostly<01:43:27.679> cool<01:43:30.739> slash<01:43:31.739> ability<01:43:32.159> to<01:43:32.219> block 01:43:32.360 --> 01:43:32.370 align:start position:0% mostly cool slash ability to block 01:43:32.370 --> 01:43:35.540 align:start position:0% mostly cool slash ability to block proposals<01:43:33.230> it's<01:43:34.230> really<01:43:34.830> cheap<01:43:35.100> to<01:43:35.310> sign 01:43:35.540 --> 01:43:35.550 align:start position:0% proposals it's really cheap to sign 01:43:35.550 --> 01:43:39.709 align:start position:0% proposals it's really cheap to sign things<01:43:35.820> so<01:43:36.750> we<01:43:36.840> have<01:43:36.989> to<01:43:37.140> make<01:43:37.320> it<01:43:37.500> but<01:43:38.219> it's<01:43:38.730> as 01:43:39.709 --> 01:43:39.719 align:start position:0% things so we have to make it but it's as 01:43:39.719 --> 01:43:41.270 align:start position:0% things so we have to make it but it's as opposed<01:43:40.110> to<01:43:40.260> improve<01:43:40.560> work<01:43:40.800> it's<01:43:41.010> it's<01:43:41.219> very 01:43:41.270 --> 01:43:41.280 align:start position:0% opposed to improve work it's it's very 01:43:41.280 --> 01:43:43.100 align:start position:0% opposed to improve work it's it's very expensive<01:43:41.699> to<01:43:42.060> make<01:43:42.270> blocks<01:43:42.480> that<01:43:42.690> look<01:43:42.810> valid 01:43:43.100 --> 01:43:43.110 align:start position:0% expensive to make blocks that look valid 01:43:43.110 --> 01:43:44.570 align:start position:0% expensive to make blocks that look valid because<01:43:43.739> you<01:43:43.949> have<01:43:44.040> to<01:43:44.190> exert<01:43:44.400> the 01:43:44.570 --> 01:43:44.580 align:start position:0% because you have to exert the 01:43:44.580 --> 01:43:46.580 align:start position:0% because you have to exert the computational<01:43:45.330> power<01:43:45.510> so<01:43:46.170> if<01:43:46.409> I've<01:43:46.560> been 01:43:46.580 --> 01:43:46.590 align:start position:0% computational power so if I've been 01:43:46.590 --> 01:43:50.870 align:start position:0% computational power so if I've been chosen<01:43:46.980> to<01:43:48.080> make<01:43:49.080> a<01:43:49.110> block<01:43:49.380> I<01:43:49.679> need<01:43:50.370> to<01:43:50.520> the 01:43:50.870 --> 01:43:50.880 align:start position:0% chosen to make a block I need to the 01:43:50.880 --> 01:43:53.180 align:start position:0% chosen to make a block I need to the protocol<01:43:51.179> needs<01:43:51.330> to<01:43:51.510> make<01:43:51.659> that<01:43:51.860> expensive<01:43:52.860> so 01:43:53.180 --> 01:43:53.190 align:start position:0% protocol needs to make that expensive so 01:43:53.190 --> 01:43:55.130 align:start position:0% protocol needs to make that expensive so that<01:43:53.310> I<01:43:53.340> can't<01:43:53.610> make<01:43:53.730> a<01:43:53.760> ton<01:43:54.000> of<01:43:54.030> them<01:43:54.270> so 01:43:55.130 --> 01:43:55.140 align:start position:0% that I can't make a ton of them so 01:43:55.140 --> 01:43:56.209 align:start position:0% that I can't make a ton of them so essentially<01:43:55.530> we<01:43:55.590> have<01:43:55.620> a<01:43:55.770> very<01:43:55.920> simple 01:43:56.209 --> 01:43:56.219 align:start position:0% essentially we have a very simple 01:43:56.219 --> 01:43:59.090 align:start position:0% essentially we have a very simple slashing<01:43:56.699> addition<01:43:57.060> that<01:43:58.020> is<01:43:58.290> making<01:43:58.949> sure 01:43:59.090 --> 01:43:59.100 align:start position:0% slashing addition that is making sure 01:43:59.100 --> 01:44:01.220 align:start position:0% slashing addition that is making sure that<01:43:59.130> I'm<01:43:59.400> not<01:43:59.550> making<01:43:59.850> too<01:44:00.000> the<01:44:00.840> same<01:44:00.989> block 01:44:01.220 --> 01:44:01.230 align:start position:0% that I'm not making too the same block 01:44:01.230 --> 01:44:03.950 align:start position:0% that I'm not making too the same block in<01:44:01.469> the<01:44:01.650> epoch<01:44:02.060> actually<01:44:03.060> in<01:44:03.719> a 01:44:03.950 --> 01:44:03.960 align:start position:0% in the epoch actually in a 01:44:03.960 --> 01:44:05.660 align:start position:0% in the epoch actually in a soon-to-be-released<01:44:04.920> version<01:44:05.489> that's 01:44:05.660 --> 01:44:05.670 align:start position:0% soon-to-be-released version that's 01:44:05.670 --> 01:44:08.510 align:start position:0% soon-to-be-released version that's changed<01:44:06.000> to<01:44:06.179> me<01:44:06.449> not<01:44:06.630> making<01:44:06.810> the<01:44:07.020> same<01:44:07.520> block 01:44:08.510 --> 01:44:08.520 align:start position:0% changed to me not making the same block 01:44:08.520 --> 01:44:10.669 align:start position:0% changed to me not making the same block in<01:44:08.550> the<01:44:08.760> same<01:44:08.909> slot<01:44:09.120> but<01:44:10.110> essentially<01:44:10.530> it's 01:44:10.669 --> 01:44:10.679 align:start position:0% in the same slot but essentially it's 01:44:10.679 --> 01:44:13.399 align:start position:0% in the same slot but essentially it's like<01:44:10.739> a<01:44:10.830> no<01:44:11.040> double<01:44:11.370> vote<01:44:11.550> no<01:44:12.449> double<01:44:12.989> proposal 01:44:13.399 --> 01:44:13.409 align:start position:0% like a no double vote no double proposal 01:44:13.409 --> 01:44:19.189 align:start position:0% like a no double vote no double proposal mechanism<01:44:16.040> committees<01:44:17.040> so<01:44:17.489> I<01:44:18.050> don't<01:44:19.050> know<01:44:19.110> if 01:44:19.189 --> 01:44:19.199 align:start position:0% mechanism committees so I don't know if 01:44:19.199 --> 01:44:21.200 align:start position:0% mechanism committees so I don't know if we've<01:44:19.320> explicitly<01:44:19.890> talked<01:44:20.610> too<01:44:20.850> much<01:44:20.880> about 01:44:21.200 --> 01:44:21.210 align:start position:0% we've explicitly talked too much about 01:44:21.210 --> 01:44:22.310 align:start position:0% we've explicitly talked too much about committees<01:44:21.570> we<01:44:21.690> talked<01:44:21.870> about<01:44:22.050> like<01:44:22.170> how<01:44:22.260> we 01:44:22.310 --> 01:44:22.320 align:start position:0% committees we talked about like how we 01:44:22.320 --> 01:44:23.720 align:start position:0% committees we talked about like how we shuffle<01:44:22.679> those<01:44:22.800> people<01:44:23.040> into<01:44:23.190> committees<01:44:23.550> but 01:44:23.720 --> 01:44:23.730 align:start position:0% shuffle those people into committees but 01:44:23.730 --> 01:44:28.280 align:start position:0% shuffle those people into committees but essentially<01:44:24.600> within<01:44:25.140> a<01:44:25.969> given<01:44:26.969> epoch<01:44:27.480> every 01:44:28.280 --> 01:44:28.290 align:start position:0% essentially within a given epoch every 01:44:28.290 --> 01:44:30.410 align:start position:0% essentially within a given epoch every validator<01:44:28.800> is<01:44:28.980> assigned<01:44:29.550> to<01:44:29.699> exactly<01:44:30.150> one 01:44:30.410 --> 01:44:30.420 align:start position:0% validator is assigned to exactly one 01:44:30.420 --> 01:44:32.899 align:start position:0% validator is assigned to exactly one slot<01:44:30.719> to<01:44:31.230> attest<01:44:31.530> to<01:44:31.650> it<01:44:31.830> to<01:44:32.429> create<01:44:32.760> an 01:44:32.899 --> 01:44:32.909 align:start position:0% slot to attest to it to create an 01:44:32.909 --> 01:44:34.760 align:start position:0% slot to attest to it to create an attestation<01:44:33.270> that<01:44:33.719> they<01:44:34.199> destructor<01:44:34.650> that 01:44:34.760 --> 01:44:34.770 align:start position:0% attestation that they destructor that 01:44:34.770 --> 01:44:38.810 align:start position:0% attestation that they destructor that has<01:44:34.860> all<01:44:34.980> the<01:44:35.100> things<01:44:35.159> votes<01:44:36.060> on<01:44:37.400> the<01:44:38.400> head<01:44:38.580> for 01:44:38.810 --> 01:44:38.820 align:start position:0% has all the things votes on the head for 01:44:38.820 --> 01:44:40.520 align:start position:0% has all the things votes on the head for the<01:44:38.909> fork<01:44:39.120> choice<01:44:39.330> votes<01:44:39.989> on<01:44:40.140> a<01:44:40.170> cast<01:44:40.409> for 01:44:40.520 --> 01:44:40.530 align:start position:0% the fork choice votes on a cast for 01:44:40.530 --> 01:44:42.800 align:start position:0% the fork choice votes on a cast for every<01:44:40.739> vote<01:44:41.040> votes<01:44:41.550> on<01:44:41.670> a<01:44:41.699> cross<01:44:41.909> link<01:44:42.210> it<01:44:42.570> does 01:44:42.800 --> 01:44:42.810 align:start position:0% every vote votes on a cross link it does 01:44:42.810 --> 01:44:45.530 align:start position:0% every vote votes on a cross link it does all<01:44:42.960> sorts<01:44:43.170> of<01:44:43.320> stuff<01:44:44.060> so<01:44:45.060> I<01:44:45.090> can<01:44:45.270> use<01:44:45.389> this 01:44:45.530 --> 01:44:45.540 align:start position:0% all sorts of stuff so I can use this 01:44:45.540 --> 01:44:46.590 align:start position:0% all sorts of stuff so I can use this function 01:44:46.590 --> 01:44:46.600 align:start position:0% function 01:44:46.600 --> 01:44:50.010 align:start position:0% function -<01:44:47.050> essentially<01:44:47.650> query<01:44:48.520> which<01:44:49.420> slot<01:44:49.840> I'm 01:44:50.010 --> 01:44:50.020 align:start position:0% - essentially query which slot I'm 01:44:50.020 --> 01:44:51.600 align:start position:0% - essentially query which slot I'm assigned<01:44:50.350> to<01:44:50.530> what<01:44:50.830> shard<01:44:51.160> I'm<01:44:51.250> assigned<01:44:51.520> to 01:44:51.600 --> 01:44:51.610 align:start position:0% assigned to what shard I'm assigned to 01:44:51.610 --> 01:44:56.220 align:start position:0% assigned to what shard I'm assigned to and<01:44:52.030> I<01:44:52.330> can<01:44:52.540> do<01:44:52.690> my<01:44:52.840> duty<01:44:53.170> I<01:44:54.600> get<01:44:55.600> a<01:44:55.780> look<01:44:56.050> ahead 01:44:56.220 --> 01:44:56.230 align:start position:0% and I can do my duty I get a look ahead 01:44:56.230 --> 01:45:01.260 align:start position:0% and I can do my duty I get a look ahead of<01:44:56.620> at<01:44:56.830> least<01:44:57.130> one<01:44:57.850> epoch<01:44:58.330> so<01:45:00.000> during<01:45:01.000> the 01:45:01.260 --> 01:45:01.270 align:start position:0% of at least one epoch so during the 01:45:01.270 --> 01:45:03.600 align:start position:0% of at least one epoch so during the current<01:45:01.630> epoch<01:45:01.960> I<01:45:02.230> know<01:45:02.350> my<01:45:02.800> assignment<01:45:03.430> in 01:45:03.600 --> 01:45:03.610 align:start position:0% current epoch I know my assignment in 01:45:03.610 --> 01:45:08.880 align:start position:0% current epoch I know my assignment in the<01:45:04.120> next<01:45:04.420> epoch<01:45:04.780> this<01:45:05.650> allows<01:45:06.010> me<01:45:06.280> to<01:45:07.560> sync 01:45:08.880 --> 01:45:08.890 align:start position:0% the next epoch this allows me to sync 01:45:08.890 --> 01:45:10.500 align:start position:0% the next epoch this allows me to sync whatever<01:45:09.340> shard<01:45:09.610> I<01:45:09.670> need<01:45:09.850> to<01:45:10.000> and<01:45:10.270> kind<01:45:10.450> of 01:45:10.500 --> 01:45:10.510 align:start position:0% whatever shard I need to and kind of 01:45:10.510 --> 01:45:13.170 align:start position:0% whatever shard I need to and kind of like<01:45:10.630> get<01:45:10.810> ready<01:45:11.080> for<01:45:11.710> my<01:45:11.890> duty<01:45:12.160> this<01:45:13.030> is 01:45:13.170 --> 01:45:13.180 align:start position:0% like get ready for my duty this is 01:45:13.180 --> 01:45:16.830 align:start position:0% like get ready for my duty this is actually<01:45:13.480> tunable<01:45:14.340> in<01:45:15.340> Mincey<01:45:16.150> look<01:45:16.360> ahead<01:45:16.630> if 01:45:16.830 --> 01:45:16.840 align:start position:0% actually tunable in Mincey look ahead if 01:45:16.840 --> 01:45:19.800 align:start position:0% actually tunable in Mincey look ahead if we<01:45:17.050> for<01:45:17.739> some<01:45:17.890> reason<01:45:18.190> needed<01:45:18.370> a<01:45:18.640> longer<01:45:19.570> look 01:45:19.800 --> 01:45:19.810 align:start position:0% we for some reason needed a longer look 01:45:19.810 --> 01:45:21.780 align:start position:0% we for some reason needed a longer look ahead<01:45:19.960> because<01:45:20.290> the<01:45:20.980> overhead<01:45:21.340> of<01:45:21.370> syncing<01:45:21.730> a 01:45:21.780 --> 01:45:21.790 align:start position:0% ahead because the overhead of syncing a 01:45:21.790 --> 01:45:22.860 align:start position:0% ahead because the overhead of syncing a chart<01:45:22.000> or<01:45:22.060> something<01:45:22.330> was<01:45:22.450> long<01:45:22.600> we<01:45:22.750> could 01:45:22.860 --> 01:45:22.870 align:start position:0% chart or something was long we could 01:45:22.870 --> 01:45:25.080 align:start position:0% chart or something was long we could tune<01:45:23.020> that<01:45:23.200> constant<01:45:23.670> it's<01:45:24.670> a<01:45:24.790> trade-off 01:45:25.080 --> 01:45:25.090 align:start position:0% tune that constant it's a trade-off 01:45:25.090 --> 01:45:27.150 align:start position:0% tune that constant it's a trade-off between<01:45:25.270> a<01:45:25.840> kind<01:45:26.320> of<01:45:26.380> the<01:45:26.469> longer<01:45:26.830> you<01:45:26.980> have 01:45:27.150 --> 01:45:27.160 align:start position:0% between a kind of the longer you have 01:45:27.160 --> 01:45:29.430 align:start position:0% between a kind of the longer you have you<01:45:27.670> know<01:45:27.820> the<01:45:27.969> committee<01:45:28.239> is<01:45:28.390> the<01:45:28.510> easier<01:45:28.780> it 01:45:29.430 --> 01:45:29.440 align:start position:0% you know the committee is the easier it 01:45:29.440 --> 01:45:31.800 align:start position:0% you know the committee is the easier it is<01:45:29.530> to<01:45:29.590> potentially<01:45:30.160> dose<01:45:30.310> or<01:45:30.640> bribe<01:45:31.600> or 01:45:31.800 --> 01:45:31.810 align:start position:0% is to potentially dose or bribe or 01:45:31.810 --> 01:45:38.670 align:start position:0% is to potentially dose or bribe or whatever<01:45:33.060> so<01:45:34.060> I<01:45:34.530> make<01:45:35.530> an<01:45:35.650> attestation<01:45:37.050> yeah<01:45:38.050> I 01:45:38.670 --> 01:45:38.680 align:start position:0% whatever so I make an attestation yeah I 01:45:38.680 --> 01:45:41.880 align:start position:0% whatever so I make an attestation yeah I had<01:45:39.489> the<01:45:39.760> cursor<01:45:40.719> highlighted<01:45:41.260> so<01:45:41.560> that's<01:45:41.770> why 01:45:41.880 --> 01:45:41.890 align:start position:0% had the cursor highlighted so that's why 01:45:41.890 --> 01:45:43.790 align:start position:0% had the cursor highlighted so that's why it's<01:45:42.070> green 01:45:43.790 --> 01:45:43.800 align:start position:0% it's green 01:45:43.800 --> 01:45:47.300 align:start position:0% it's green so<01:45:44.800> I<01:45:44.830> make<01:45:45.010> this<01:45:45.100> out<01:45:45.280> to<01:45:45.310> station<01:45:45.730> I<01:45:45.910> do<01:45:46.570> it<01:45:46.930> at 01:45:47.300 --> 01:45:47.310 align:start position:0% so I make this out to station I do it at 01:45:47.310 --> 01:45:50.729 align:start position:0% so I make this out to station I do it at the<01:45:48.330> slot<01:45:49.330> might<01:45:49.570> the<01:45:49.989> slot<01:45:50.230> I'm<01:45:50.380> assigned<01:45:50.680> to 01:45:50.729 --> 01:45:50.739 align:start position:0% the slot might the slot I'm assigned to 01:45:50.739 --> 01:45:54.060 align:start position:0% the slot might the slot I'm assigned to that<01:45:50.980> time<01:45:51.370> plus<01:45:52.239> half<01:45:52.750> of<01:45:53.020> a<01:45:53.350> slot<01:45:53.590> duration 01:45:54.060 --> 01:45:54.070 align:start position:0% that time plus half of a slot duration 01:45:54.070 --> 01:45:57.690 align:start position:0% that time plus half of a slot duration so<01:45:54.580> the<01:45:55.390> ideas<01:45:55.930> and<01:45:56.320> optimal<01:45:56.980> conditions<01:45:57.430> a 01:45:57.690 --> 01:45:57.700 align:start position:0% so the ideas and optimal conditions a 01:45:57.700 --> 01:45:59.490 align:start position:0% so the ideas and optimal conditions a proposer<01:45:58.150> has<01:45:58.450> created<01:45:58.870> a<01:45:58.930> block<01:45:59.140> at<01:45:59.350> the 01:45:59.490 --> 01:45:59.500 align:start position:0% proposer has created a block at the 01:45:59.500 --> 01:46:01.380 align:start position:0% proposer has created a block at the start<01:45:59.739> of<01:45:59.800> a<01:45:59.890> slot<01:46:00.100> and<01:46:00.370> by<01:46:00.760> halfway<01:46:01.150> through 01:46:01.380 --> 01:46:01.390 align:start position:0% start of a slot and by halfway through 01:46:01.390 --> 01:46:03.450 align:start position:0% start of a slot and by halfway through the<01:46:01.480> slot<01:46:01.719> I've<01:46:01.989> gotten<01:46:02.560> that<01:46:02.680> block<01:46:02.920> I<01:46:03.190> see 01:46:03.450 --> 01:46:03.460 align:start position:0% the slot I've gotten that block I see 01:46:03.460 --> 01:46:05.040 align:start position:0% the slot I've gotten that block I see that<01:46:03.670> as<01:46:03.790> the<01:46:03.820> state<01:46:04.090> of<01:46:04.150> the<01:46:04.300> world<01:46:04.450> I<01:46:04.660> vote<01:46:04.870> on 01:46:05.040 --> 01:46:05.050 align:start position:0% that as the state of the world I vote on 01:46:05.050 --> 01:46:07.800 align:start position:0% that as the state of the world I vote on it<01:46:05.190> in<01:46:06.190> certain<01:46:06.580> non<01:46:06.820> optimal<01:46:07.180> conditions<01:46:07.600> I 01:46:07.800 --> 01:46:07.810 align:start position:0% it in certain non optimal conditions I 01:46:07.810 --> 01:46:10.080 align:start position:0% it in certain non optimal conditions I might<01:46:08.020> vote<01:46:08.170> on<01:46:08.350> some<01:46:08.560> prior<01:46:08.800> block<01:46:09.100> but<01:46:09.910> I<01:46:09.940> can 01:46:10.080 --> 01:46:10.090 align:start position:0% might vote on some prior block but I can 01:46:10.090 --> 01:46:11.910 align:start position:0% might vote on some prior block but I can still<01:46:10.270> kind<01:46:10.420> of<01:46:10.510> add<01:46:10.719> weight<01:46:10.960> as<01:46:11.170> Vitalik 01:46:11.910 --> 01:46:11.920 align:start position:0% still kind of add weight as Vitalik 01:46:11.920 --> 01:46:13.830 align:start position:0% still kind of add weight as Vitalik showed<01:46:12.100> an<01:46:12.310> in<01:46:12.489> fork<01:46:13.060> choice<01:46:13.270> and<01:46:13.480> I<01:46:13.510> can<01:46:13.660> still 01:46:13.830 --> 01:46:13.840 align:start position:0% showed an in fork choice and I can still 01:46:13.840 --> 01:46:16.380 align:start position:0% showed an in fork choice and I can still manage<01:46:14.530> to<01:46:14.710> we<01:46:15.190> can<01:46:15.340> still<01:46:15.820> keep<01:46:16.000> the<01:46:16.180> chain 01:46:16.380 --> 01:46:16.390 align:start position:0% manage to we can still keep the chain 01:46:16.390 --> 01:46:19.310 align:start position:0% manage to we can still keep the chain moving<01:46:16.660> forward<01:46:17.110> and<01:46:17.260> finalize<01:46:17.620> things 01:46:19.310 --> 01:46:19.320 align:start position:0% moving forward and finalize things 01:46:19.320 --> 01:46:24.690 align:start position:0% moving forward and finalize things around<01:46:20.320> my<01:46:20.500> fork<01:46:20.710> choice<01:46:20.920> and<01:46:21.460> I<01:46:22.330> get<01:46:22.600> I<01:46:23.700> see 01:46:24.690 --> 01:46:24.700 align:start position:0% around my fork choice and I get I see 01:46:24.700 --> 01:46:27.959 align:start position:0% around my fork choice and I get I see where<01:46:25.230> the<01:46:26.230> head<01:46:26.350> of<01:46:26.380> the<01:46:26.530> chain<01:46:26.710> is<01:46:26.890> the<01:46:27.489> state 01:46:27.959 --> 01:46:27.969 align:start position:0% where the head of the chain is the state 01:46:27.969 --> 01:46:30.390 align:start position:0% where the head of the chain is the state relative<01:46:28.900> to<01:46:29.050> that<01:46:29.170> head<01:46:29.410> of<01:46:29.530> the<01:46:29.620> chain<01:46:29.860> at 01:46:30.390 --> 01:46:30.400 align:start position:0% relative to that head of the chain at 01:46:30.400 --> 01:46:33.420 align:start position:0% relative to that head of the chain at the<01:46:30.460> slot<01:46:31.120> that<01:46:31.150> I'm<01:46:31.540> assigned<01:46:31.870> to<01:46:32.050> is<01:46:33.010> also 01:46:33.420 --> 01:46:33.430 align:start position:0% the slot that I'm assigned to is also 01:46:33.430 --> 01:46:35.670 align:start position:0% the slot that I'm assigned to is also going<01:46:33.550> to<01:46:33.610> give<01:46:33.790> me<01:46:33.940> this<01:46:34.930> information<01:46:34.989> so<01:46:35.650> I 01:46:35.670 --> 01:46:35.680 align:start position:0% going to give me this information so I 01:46:35.680 --> 01:46:37.170 align:start position:0% going to give me this information so I can<01:46:35.890> actually<01:46:36.010> just<01:46:36.280> go<01:46:36.430> into<01:46:36.610> the<01:46:36.790> state<01:46:37.000> and 01:46:37.170 --> 01:46:37.180 align:start position:0% can actually just go into the state and 01:46:37.180 --> 01:46:39.660 align:start position:0% can actually just go into the state and say<01:46:37.600> hey<01:46:37.840> what<01:46:38.500> was<01:46:38.650> the<01:46:38.680> checkpoint<01:46:39.310> what<01:46:39.580> are 01:46:39.660 --> 01:46:39.670 align:start position:0% say hey what was the checkpoint what are 01:46:39.670 --> 01:46:41.610 align:start position:0% say hey what was the checkpoint what are we<01:46:39.760> voting<01:46:39.880> on<01:46:40.120> right<01:46:40.300> now<01:46:40.450> and<01:46:41.260> just<01:46:41.469> pull 01:46:41.610 --> 01:46:41.620 align:start position:0% we voting on right now and just pull 01:46:41.620 --> 01:46:42.990 align:start position:0% we voting on right now and just pull that<01:46:41.650> information<01:46:42.219> and<01:46:42.310> construct<01:46:42.670> this<01:46:42.790> data 01:46:42.990 --> 01:46:43.000 align:start position:0% that information and construct this data 01:46:43.000 --> 01:46:45.870 align:start position:0% that information and construct this data this<01:46:43.660> is<01:46:44.650> actually<01:46:45.070> just<01:46:45.250> stubbed<01:46:45.489> in<01:46:45.670> phase 01:46:45.870 --> 01:46:45.880 align:start position:0% this is actually just stubbed in phase 01:46:45.880 --> 01:46:49.050 align:start position:0% this is actually just stubbed in phase zero<01:46:46.150> but<01:46:46.930> this<01:46:47.170> is<01:46:47.350> relative<01:46:48.340> to<01:46:48.370> me<01:46:48.790> running 01:46:49.050 --> 01:46:49.060 align:start position:0% zero but this is relative to me running 01:46:49.060 --> 01:46:53.060 align:start position:0% zero but this is relative to me running the<01:46:49.390> fork<01:46:49.630> choice<01:46:49.870> on<01:46:50.110> the<01:46:50.650> sharp<01:46:50.890> chain 01:46:53.060 --> 01:46:53.070 align:start position:0% the fork choice on the sharp chain 01:46:53.070 --> 01:46:56.780 align:start position:0% the fork choice on the sharp chain um<01:46:53.480> that's<01:46:54.480> not<01:46:54.630> super<01:46:55.490> important<01:46:56.490> that's 01:46:56.780 --> 01:46:56.790 align:start position:0% um that's not super important that's 01:46:56.790 --> 01:46:58.940 align:start position:0% um that's not super important that's actually<01:46:57.210> what<01:46:57.360> I'm<01:46:57.480> gonna<01:46:57.660> put<01:46:57.870> into<01:46:58.350> the 01:46:58.940 --> 01:46:58.950 align:start position:0% actually what I'm gonna put into the 01:46:58.950 --> 01:47:01.160 align:start position:0% actually what I'm gonna put into the crosslink<01:46:59.640> which<01:47:00.420> Justin<01:47:00.840> pretty<01:47:01.020> much 01:47:01.160 --> 01:47:01.170 align:start position:0% crosslink which Justin pretty much 01:47:01.170 --> 01:47:04.430 align:start position:0% crosslink which Justin pretty much covered<01:47:01.530> the<01:47:01.920> fun<01:47:02.070> part<01:47:02.310> is<01:47:02.490> that<01:47:03.440> because 01:47:04.430 --> 01:47:04.440 align:start position:0% covered the fun part is that because 01:47:04.440 --> 01:47:06.140 align:start position:0% covered the fun part is that because it's<01:47:04.620> a<01:47:04.710> zero<01:47:05.010> and<01:47:05.280> there's<01:47:05.490> no<01:47:05.700> short<01:47:05.940> chains 01:47:06.140 --> 01:47:06.150 align:start position:0% it's a zero and there's no short chains 01:47:06.150 --> 01:47:11.420 align:start position:0% it's a zero and there's no short chains so<01:47:06.390> just<01:47:06.660> a<01:47:06.720> zero<01:47:06.930> Hashim<01:47:09.620> because<01:47:10.620> he<01:47:10.800> bit<01:47:10.980> so 01:47:11.420 --> 01:47:11.430 align:start position:0% so just a zero Hashim because he bit so 01:47:11.430 --> 01:47:13.070 align:start position:0% so just a zero Hashim because he bit so this<01:47:11.580> is<01:47:11.790> I<01:47:11.820> just<01:47:12.270> want<01:47:12.510> to<01:47:12.600> show<01:47:12.780> you<01:47:12.840> this 01:47:13.070 --> 01:47:13.080 align:start position:0% this is I just want to show you this 01:47:13.080 --> 01:47:15.350 align:start position:0% this is I just want to show you this data<01:47:13.320> structure<01:47:13.650> because<01:47:14.370> even<01:47:15.150> though<01:47:15.240> it 01:47:15.350 --> 01:47:15.360 align:start position:0% data structure because even though it 01:47:15.360 --> 01:47:18.350 align:start position:0% data structure because even though it phase<01:47:15.600> zero<01:47:16.520> we<01:47:17.520> don't<01:47:17.700> have<01:47:17.880> a<01:47:17.910> notion<01:47:18.180> of 01:47:18.350 --> 01:47:18.360 align:start position:0% phase zero we don't have a notion of 01:47:18.360 --> 01:47:19.700 align:start position:0% phase zero we don't have a notion of sure<01:47:18.540> we<01:47:18.660> don't<01:47:18.750> have<01:47:18.870> any<01:47:18.930> chart<01:47:19.260> chains<01:47:19.470> so 01:47:19.700 --> 01:47:19.710 align:start position:0% sure we don't have any chart chains so 01:47:19.710 --> 01:47:21.410 align:start position:0% sure we don't have any chart chains so we<01:47:19.800> don't<01:47:19.950> have<01:47:20.070> this<01:47:20.220> notion<01:47:20.430> of<01:47:20.700> custody 01:47:21.410 --> 01:47:21.420 align:start position:0% we don't have this notion of custody 01:47:21.420 --> 01:47:23.050 align:start position:0% we don't have this notion of custody games<01:47:21.630> and<01:47:21.900> having<01:47:22.110> custody<01:47:22.470> of<01:47:22.560> shard<01:47:22.770> data 01:47:23.050 --> 01:47:23.060 align:start position:0% games and having custody of shard data 01:47:23.060 --> 01:47:26.420 align:start position:0% games and having custody of shard data but<01:47:24.060> there<01:47:24.630> is<01:47:24.810> this<01:47:24.990> notion<01:47:25.410> of<01:47:25.710> like<01:47:25.860> a<01:47:26.040> bit 01:47:26.420 --> 01:47:26.430 align:start position:0% but there is this notion of like a bit 01:47:26.430 --> 01:47:31.430 align:start position:0% but there is this notion of like a bit in<01:47:27.360> a<01:47:27.480> custody<01:47:27.840> bit<01:47:28.080> which<01:47:28.560> is<01:47:28.910> tied<01:47:29.910> to<01:47:30.440> my 01:47:31.430 --> 01:47:31.440 align:start position:0% in a custody bit which is tied to my 01:47:31.440 --> 01:47:34.220 align:start position:0% in a custody bit which is tied to my personal<01:47:32.340> a<01:47:32.880> personal<01:47:33.270> secret<01:47:33.960> that<01:47:34.080> I<01:47:34.140> have 01:47:34.220 --> 01:47:34.230 align:start position:0% personal a personal secret that I have 01:47:34.230 --> 01:47:37.220 align:start position:0% personal a personal secret that I have and<01:47:34.710> the<01:47:35.100> attestation<01:47:35.540> the<01:47:36.540> cus<01:47:36.690> of<01:47:36.900> the<01:47:36.990> cross 01:47:37.220 --> 01:47:37.230 align:start position:0% and the attestation the cus of the cross 01:47:37.230 --> 01:47:39.350 align:start position:0% and the attestation the cus of the cross link<01:47:37.440> that<01:47:37.560> I'm<01:47:37.650> cross<01:47:37.860> linking<01:47:38.220> and<01:47:38.430> so<01:47:38.820> I'm 01:47:39.350 --> 01:47:39.360 align:start position:0% link that I'm cross linking and so I'm 01:47:39.360 --> 01:47:42.020 align:start position:0% link that I'm cross linking and so I'm not<01:47:39.570> actually<01:47:39.720> signing<01:47:40.430> just<01:47:41.430> the 01:47:42.020 --> 01:47:42.030 align:start position:0% not actually signing just the 01:47:42.030 --> 01:47:44.510 align:start position:0% not actually signing just the attestation<01:47:42.360> data<01:47:42.930> I<01:47:43.230> sign<01:47:43.920> the<01:47:44.220> attestation 01:47:44.510 --> 01:47:44.520 align:start position:0% attestation data I sign the attestation 01:47:44.520 --> 01:47:48.320 align:start position:0% attestation data I sign the attestation data<01:47:45.030> with<01:47:45.840> my<01:47:46.110> bit<01:47:46.320> zero<01:47:47.010> or<01:47:47.220> one<01:47:47.400> and<01:47:47.640> so<01:47:48.030> for 01:47:48.320 --> 01:47:48.330 align:start position:0% data with my bit zero or one and so for 01:47:48.330 --> 01:47:52.250 align:start position:0% data with my bit zero or one and so for any<01:47:48.480> given<01:47:48.770> Committee<01:47:49.770> in<01:47:50.340> phase<01:47:50.730> one<01:47:51.260> we'd 01:47:52.250 --> 01:47:52.260 align:start position:0% any given Committee in phase one we'd 01:47:52.260 --> 01:47:55.070 align:start position:0% any given Committee in phase one we'd have<01:47:52.470> two<01:47:52.800> versions<01:47:53.400> of<01:47:53.670> this<01:47:54.210> aggregate<01:47:54.840> able 01:47:55.070 --> 01:47:55.080 align:start position:0% have two versions of this aggregate able 01:47:55.080 --> 01:47:57.650 align:start position:0% have two versions of this aggregate able signature<01:47:55.470> the<01:47:55.920> one<01:47:56.130> with<01:47:56.340> the<01:47:57.000> zero<01:47:57.240> bit<01:47:57.420> and 01:47:57.650 --> 01:47:57.660 align:start position:0% signature the one with the zero bit and 01:47:57.660 --> 01:48:01.070 align:start position:0% signature the one with the zero bit and the<01:47:58.140> ones<01:47:58.320> with<01:47:58.590> the<01:47:58.950> one<01:47:59.220> bit<01:47:59.430> in<01:47:59.840> phase<01:48:00.840> zero 01:48:01.070 --> 01:48:01.080 align:start position:0% the ones with the one bit in phase zero 01:48:01.080 --> 01:48:05.840 align:start position:0% the ones with the one bit in phase zero this<01:48:01.410> is<01:48:01.620> stubbed<01:48:01.950> as<01:48:02.190> a<01:48:02.220> zero<01:48:02.940> bit<01:48:04.640> right<01:48:05.640> but 01:48:05.840 --> 01:48:05.850 align:start position:0% this is stubbed as a zero bit right but 01:48:05.850 --> 01:48:07.910 align:start position:0% this is stubbed as a zero bit right but in<01:48:06.030> this<01:48:06.210> outer<01:48:06.480> data<01:48:06.780> structure<01:48:07.230> with<01:48:07.800> the 01:48:07.910 --> 01:48:07.920 align:start position:0% in this outer data structure with the 01:48:07.920 --> 01:48:10.580 align:start position:0% in this outer data structure with the custody<01:48:08.340> bits<01:48:08.750> so<01:48:09.750> we<01:48:09.870> remember<01:48:10.350> we<01:48:10.560> remember 01:48:10.580 --> 01:48:10.590 align:start position:0% custody bits so we remember we remember 01:48:10.590 --> 01:48:12.680 align:start position:0% custody bits so we remember we remember who<01:48:11.100> participated<01:48:11.790> with<01:48:12.120> the<01:48:12.150> aggregation 01:48:12.680 --> 01:48:12.690 align:start position:0% who participated with the aggregation 01:48:12.690 --> 01:48:15.590 align:start position:0% who participated with the aggregation bits<01:48:13.020> and<01:48:13.290> we<01:48:13.680> remember<01:48:13.980> which<01:48:14.580> custody<01:48:15.390> bit 01:48:15.590 --> 01:48:15.600 align:start position:0% bits and we remember which custody bit 01:48:15.600 --> 01:48:17.180 align:start position:0% bits and we remember which custody bit they<01:48:15.840> participated<01:48:16.500> with<01:48:16.650> so<01:48:16.800> that<01:48:16.950> we<01:48:17.040> can 01:48:17.180 --> 01:48:17.190 align:start position:0% they participated with so that we can 01:48:17.190 --> 01:48:19.550 align:start position:0% they participated with so that we can reconstruct<01:48:17.720> the<01:48:18.720> mess<01:48:18.900> the<01:48:19.080> proper<01:48:19.380> message 01:48:19.550 --> 01:48:19.560 align:start position:0% reconstruct the mess the proper message 01:48:19.560 --> 01:48:21.230 align:start position:0% reconstruct the mess the proper message to<01:48:19.920> validate<01:48:20.250> the<01:48:20.370> signature<01:48:20.790> in<01:48:20.880> the<01:48:20.970> future 01:48:21.230 --> 01:48:21.240 align:start position:0% to validate the signature in the future 01:48:21.240 --> 01:48:24.170 align:start position:0% to validate the signature in the future in<01:48:21.570> phase<01:48:22.140> zero<01:48:22.440> when<01:48:23.340> I'm<01:48:23.460> constructing<01:48:24.060> my 01:48:24.170 --> 01:48:24.180 align:start position:0% in phase zero when I'm constructing my 01:48:24.180 --> 01:48:26.330 align:start position:0% in phase zero when I'm constructing my antis<01:48:24.510> a<01:48:24.660> Shinto<01:48:25.020> broadcast<01:48:25.440> I<01:48:25.710> flipped<01:48:26.250> my 01:48:26.330 --> 01:48:26.340 align:start position:0% antis a Shinto broadcast I flipped my 01:48:26.340 --> 01:48:30.050 align:start position:0% antis a Shinto broadcast I flipped my bit<01:48:26.840> my<01:48:28.010> position<01:48:29.010> in<01:48:29.250> the<01:48:29.370> shuffling<01:48:29.790> of<01:48:29.940> the 01:48:30.050 --> 01:48:30.060 align:start position:0% bit my position in the shuffling of the 01:48:30.060 --> 01:48:32.120 align:start position:0% bit my position in the shuffling of the committee<01:48:30.300> I<01:48:30.390> flipped<01:48:30.750> that<01:48:30.900> bit<01:48:31.110> and<01:48:31.290> for<01:48:31.920> the 01:48:32.120 --> 01:48:32.130 align:start position:0% committee I flipped that bit and for the 01:48:32.130 --> 01:48:33.920 align:start position:0% committee I flipped that bit and for the custody<01:48:32.430> of<01:48:32.520> its<01:48:32.700> that's<01:48:33.030> all<01:48:33.210> 0<01:48:33.510> and<01:48:33.750> I 01:48:33.920 --> 01:48:33.930 align:start position:0% custody of its that's all 0 and I 01:48:33.930 --> 01:48:35.660 align:start position:0% custody of its that's all 0 and I broadcast<01:48:34.470> that<01:48:34.650> to<01:48:34.710> the<01:48:34.860> network<01:48:35.130> at<01:48:35.370> the 01:48:35.660 --> 01:48:35.670 align:start position:0% broadcast that to the network at the 01:48:35.670 --> 01:48:40.120 align:start position:0% broadcast that to the network at the halfway<01:48:35.910> point<01:48:36.090> of<01:48:36.420> the<01:48:36.540> slide<01:48:38.420> let's<01:48:39.420> see 01:48:40.120 --> 01:48:40.130 align:start position:0% halfway point of the slide let's see 01:48:40.130 --> 01:48:43.370 align:start position:0% halfway point of the slide let's see there<01:48:41.130> are<01:48:41.250> some<01:48:41.810> micro<01:48:42.810> called<01:48:43.140> micro 01:48:43.370 --> 01:48:43.380 align:start position:0% there are some micro called micro 01:48:43.380 --> 01:48:46.460 align:start position:0% there are some micro called micro incentives<01:48:43.800> related<01:48:44.340> to<01:48:44.960> the<01:48:45.960> creation<01:48:46.290> of<01:48:46.350> an 01:48:46.460 --> 01:48:46.470 align:start position:0% incentives related to the creation of an 01:48:46.470 --> 01:48:49.430 align:start position:0% incentives related to the creation of an attestation<01:48:47.000> it's<01:48:48.000> pretty<01:48:48.240> much<01:48:48.360> the<01:48:48.990> various 01:48:49.430 --> 01:48:49.440 align:start position:0% attestation it's pretty much the various 01:48:49.440 --> 01:48:51.590 align:start position:0% attestation it's pretty much the various components<01:48:50.040> of<01:48:50.130> what<01:48:50.310> I'm<01:48:50.400> doing<01:48:50.430> is<01:48:50.940> the<01:48:51.180> head 01:48:51.590 --> 01:48:51.600 align:start position:0% components of what I'm doing is the head 01:48:51.600 --> 01:48:54.110 align:start position:0% components of what I'm doing is the head correct<01:48:51.990> correct<01:48:52.560> being<01:48:52.920> defined<01:48:53.280> by<01:48:53.550> what 01:48:54.110 --> 01:48:54.120 align:start position:0% correct correct being defined by what 01:48:54.120 --> 01:48:56.030 align:start position:0% correct correct being defined by what ends<01:48:54.300> up<01:48:54.390> being<01:48:54.450> the<01:48:54.660> canonical<01:48:54.960> chain<01:48:55.350> was 01:48:56.030 --> 01:48:56.040 align:start position:0% ends up being the canonical chain was 01:48:56.040 --> 01:48:58.700 align:start position:0% ends up being the canonical chain was the<01:48:56.640> target<01:48:57.090> of<01:48:57.240> the<01:48:57.360> F<01:48:57.780> of<01:48:57.960> G<01:48:58.140> vote<01:48:58.320> correct 01:48:58.700 --> 01:48:58.710 align:start position:0% the target of the F of G vote correct 01:48:58.710 --> 01:49:01.670 align:start position:0% the target of the F of G vote correct was<01:48:59.580> the<01:48:59.820> source<01:49:00.210> of<01:49:00.510> the<01:49:00.690> FG<01:49:00.900> FG<01:49:00.990> vote<01:49:01.320> correct 01:49:01.670 --> 01:49:01.680 align:start position:0% was the source of the FG FG vote correct 01:49:01.680 --> 01:49:05.690 align:start position:0% was the source of the FG FG vote correct the<01:49:02.490> crosslink<01:49:03.120> so<01:49:04.020> pretty<01:49:04.530> much<01:49:04.680> any<01:49:05.490> of 01:49:05.690 --> 01:49:05.700 align:start position:0% the crosslink so pretty much any of 01:49:05.700 --> 01:49:06.739 align:start position:0% the crosslink so pretty much any of these<01:49:05.910> things<01:49:06.150> that<01:49:06.360> end<01:49:06.480> up 01:49:06.739 --> 01:49:06.749 align:start position:0% these things that end up 01:49:06.749 --> 01:49:08.959 align:start position:0% these things that end up canonical<01:49:07.139> if<01:49:07.559> I<01:49:07.710> got<01:49:07.949> the<01:49:08.130> vote<01:49:08.280> right<01:49:08.489> I<01:49:08.729> get 01:49:08.959 --> 01:49:08.969 align:start position:0% canonical if I got the vote right I get 01:49:08.969 --> 01:49:11.750 align:start position:0% canonical if I got the vote right I get a<01:49:08.999> good<01:49:09.210> reward<01:49:09.539> and<01:49:09.900> I<01:49:10.679> also<01:49:11.130> get<01:49:11.400> rewarded 01:49:11.750 --> 01:49:11.760 align:start position:0% a good reward and I also get rewarded 01:49:11.760 --> 01:49:16.310 align:start position:0% a good reward and I also get rewarded for<01:49:11.820> fast<01:49:12.150> inclusion<01:49:13.219> this<01:49:14.219> is<01:49:14.840> so<01:49:15.840> the<01:49:15.989> sooner 01:49:16.310 --> 01:49:16.320 align:start position:0% for fast inclusion this is so the sooner 01:49:16.320 --> 01:49:18.080 align:start position:0% for fast inclusion this is so the sooner the<01:49:16.409> opposition<01:49:16.889> gets<01:49:17.099> included<01:49:17.789> on<01:49:17.880> chain 01:49:18.080 --> 01:49:18.090 align:start position:0% the opposition gets included on chain 01:49:18.090 --> 01:49:19.759 align:start position:0% the opposition gets included on chain the<01:49:18.210> more<01:49:18.239> reward<01:49:18.659> and<01:49:18.900> this<01:49:19.229> portion<01:49:19.530> of<01:49:19.710> the 01:49:19.759 --> 01:49:19.769 align:start position:0% the more reward and this portion of the 01:49:19.769 --> 01:49:21.580 align:start position:0% the more reward and this portion of the world<01:49:19.949> were<01:49:20.400> word<01:49:20.639> degrades<01:49:21.059> very<01:49:21.329> quickly 01:49:21.580 --> 01:49:21.590 align:start position:0% world were word degrades very quickly 01:49:21.590 --> 01:49:23.750 align:start position:0% world were word degrades very quickly and<01:49:22.590> this<01:49:22.739> is<01:49:22.889> so<01:49:23.010> that<01:49:23.190> I<01:49:23.219> don't<01:49:23.369> I'm<01:49:23.729> not 01:49:23.750 --> 01:49:23.760 align:start position:0% and this is so that I don't I'm not 01:49:23.760 --> 01:49:25.910 align:start position:0% and this is so that I don't I'm not incentivized<01:49:24.269> to<01:49:24.539> like<01:49:24.690> wait<01:49:25.380> a<01:49:25.409> little<01:49:25.769> bit 01:49:25.910 --> 01:49:25.920 align:start position:0% incentivized to like wait a little bit 01:49:25.920 --> 01:49:27.739 align:start position:0% incentivized to like wait a little bit longer<01:49:25.979> see<01:49:26.699> what<01:49:26.849> everyone<01:49:27.179> else<01:49:27.269> is<01:49:27.510> doing 01:49:27.739 --> 01:49:27.749 align:start position:0% longer see what everyone else is doing 01:49:27.749 --> 01:49:30.580 align:start position:0% longer see what everyone else is doing before<01:49:28.739> I<01:49:28.949> actually<01:49:29.099> cast<01:49:29.460> my<01:49:29.639> vote<01:49:29.670> I<01:49:30.030> want<01:49:30.360> to 01:49:30.580 --> 01:49:30.590 align:start position:0% before I actually cast my vote I want to 01:49:30.590 --> 01:49:32.270 align:start position:0% before I actually cast my vote I want to move<01:49:31.590> very<01:49:31.619> quickly 01:49:32.270 --> 01:49:32.280 align:start position:0% move very quickly 01:49:32.280 --> 01:49:34.089 align:start position:0% move very quickly get<01:49:32.579> my<01:49:32.699> vote<01:49:32.849> in<01:49:33.030> and<01:49:33.269> get<01:49:33.420> maximum<01:49:33.809> reward 01:49:34.089 --> 01:49:34.099 align:start position:0% get my vote in and get maximum reward 01:49:34.099 --> 01:49:37.339 align:start position:0% get my vote in and get maximum reward this<01:49:35.099> is<01:49:35.309> handled<01:49:35.729> in<01:49:36.360> processed<01:49:36.960> rewards<01:49:37.260> and 01:49:37.339 --> 01:49:37.349 align:start position:0% this is handled in processed rewards and 01:49:37.349 --> 01:49:41.270 align:start position:0% this is handled in processed rewards and penalties<01:49:38.479> this<01:49:39.479> is<01:49:39.769> maybe<01:49:40.769> not<01:49:40.920> so 01:49:41.270 --> 01:49:41.280 align:start position:0% penalties this is maybe not so 01:49:41.280 --> 01:49:43.819 align:start position:0% penalties this is maybe not so surprisingly<01:49:41.849> after<01:49:42.690> our<01:49:43.019> Interop<01:49:43.440> session 01:49:43.819 --> 01:49:43.829 align:start position:0% surprisingly after our Interop session 01:49:43.829 --> 01:49:45.439 align:start position:0% surprisingly after our Interop session this<01:49:44.280> is<01:49:44.340> where<01:49:44.670> we<01:49:44.849> found<01:49:45.030> the<01:49:45.269> most 01:49:45.439 --> 01:49:45.449 align:start position:0% this is where we found the most 01:49:45.449 --> 01:49:48.520 align:start position:0% this is where we found the most consensus<01:49:46.409> bugs<01:49:46.650> on<01:49:46.949> our<01:49:47.099> initial<01:49:47.280> networks 01:49:48.520 --> 01:49:48.530 align:start position:0% consensus bugs on our initial networks 01:49:48.530 --> 01:49:51.439 align:start position:0% consensus bugs on our initial networks obviously<01:49:49.530> the<01:49:50.159> calculations<01:49:50.909> that<01:49:51.269> deal 01:49:51.439 --> 01:49:51.449 align:start position:0% obviously the calculations that deal 01:49:51.449 --> 01:49:53.569 align:start position:0% obviously the calculations that deal with<01:49:51.599> everyone's<01:49:51.989> balances<01:49:52.590> was<01:49:52.889> where<01:49:53.460> we 01:49:53.569 --> 01:49:53.579 align:start position:0% with everyone's balances was where we 01:49:53.579 --> 01:49:55.640 align:start position:0% with everyone's balances was where we had<01:49:53.699> bugs<01:49:53.909> but<01:49:54.269> then<01:49:54.929> reading<01:49:55.229> writing<01:49:55.499> some 01:49:55.640 --> 01:49:55.650 align:start position:0% had bugs but then reading writing some 01:49:55.650 --> 01:49:58.250 align:start position:0% had bugs but then reading writing some new<01:49:55.769> tests<01:49:56.130> and<01:49:56.309> enhancing<01:49:56.820> that<01:49:57.260> getting 01:49:58.250 --> 01:49:58.260 align:start position:0% new tests and enhancing that getting 01:49:58.260 --> 01:50:00.770 align:start position:0% new tests and enhancing that getting ready<01:49:58.670> slash<01:49:59.670> ability<01:50:00.030> about<01:50:00.239> his<01:50:00.389> stations 01:50:00.770 --> 01:50:00.780 align:start position:0% ready slash ability about his stations 01:50:00.780 --> 01:50:04.060 align:start position:0% ready slash ability about his stations this<01:50:01.530> these<01:50:01.889> correspond<01:50:02.400> to<01:50:02.519> the<01:50:02.869> two 01:50:04.060 --> 01:50:04.070 align:start position:0% this these correspond to the two 01:50:04.070 --> 01:50:06.770 align:start position:0% this these correspond to the two slashing<01:50:05.070> conditions<01:50:05.489> found<01:50:05.729> in<01:50:05.940> Casper<01:50:06.300> FFG 01:50:06.770 --> 01:50:06.780 align:start position:0% slashing conditions found in Casper FFG 01:50:06.780 --> 01:50:11.419 align:start position:0% slashing conditions found in Casper FFG pretty<01:50:07.590> much<01:50:08.150> if<01:50:09.150> it's<01:50:09.630> not<01:50:09.840> the<01:50:10.110> same<01:50:10.380> vote<01:50:10.710> it 01:50:11.419 --> 01:50:11.429 align:start position:0% pretty much if it's not the same vote it 01:50:11.429 --> 01:50:14.180 align:start position:0% pretty much if it's not the same vote it can't<01:50:11.760> I<01:50:12.749> mean<01:50:13.199> if<01:50:13.530> it's<01:50:13.679> not<01:50:13.710> the<01:50:13.860> same<01:50:14.039> boat 01:50:14.180 --> 01:50:14.190 align:start position:0% can't I mean if it's not the same boat 01:50:14.190 --> 01:50:15.709 align:start position:0% can't I mean if it's not the same boat it<01:50:14.309> can't<01:50:14.489> be<01:50:14.579> the<01:50:14.670> same<01:50:14.880> the<01:50:15.269> same<01:50:15.300> epoch 01:50:15.709 --> 01:50:15.719 align:start position:0% it can't be the same the same epoch 01:50:15.719 --> 01:50:17.089 align:start position:0% it can't be the same the same epoch essentially<01:50:16.260> if<01:50:16.320> you<01:50:16.440> double<01:50:16.679> signed<01:50:16.889> in<01:50:17.010> an 01:50:17.089 --> 01:50:17.099 align:start position:0% essentially if you double signed in an 01:50:17.099 --> 01:50:19.430 align:start position:0% essentially if you double signed in an epoch<01:50:17.219> you're<01:50:17.579> slashed<01:50:17.869> and<01:50:18.869> you<01:50:19.110> can't<01:50:19.289> do 01:50:19.430 --> 01:50:19.440 align:start position:0% epoch you're slashed and you can't do 01:50:19.440 --> 01:50:22.609 align:start position:0% epoch you're slashed and you can't do this<01:50:19.590> surround<01:50:19.979> vote<01:50:20.249> so<01:50:20.760> if<01:50:20.940> we<01:50:21.059> have<01:50:21.619> this 01:50:22.609 --> 01:50:22.619 align:start position:0% this surround vote so if we have this 01:50:22.619 --> 01:50:23.989 align:start position:0% this surround vote so if we have this add<01:50:22.829> to<01:50:22.979> station'<01:50:23.039> that<01:50:23.429> has<01:50:23.550> a<01:50:23.579> source<01:50:23.820> and 01:50:23.989 --> 01:50:23.999 align:start position:0% add to station' that has a source and 01:50:23.999 --> 01:50:25.549 align:start position:0% add to station' that has a source and target<01:50:24.090> we<01:50:24.389> can't<01:50:24.599> have<01:50:24.749> a<01:50:24.780> kind<01:50:25.440> of<01:50:25.469> a 01:50:25.549 --> 01:50:25.559 align:start position:0% target we can't have a kind of a 01:50:25.559 --> 01:50:27.399 align:start position:0% target we can't have a kind of a surrounding<01:50:25.979> attestation<01:50:26.400> that<01:50:26.699> just<01:50:26.880> like 01:50:27.399 --> 01:50:27.409 align:start position:0% surrounding attestation that just like 01:50:27.409 --> 01:50:38.839 align:start position:0% surrounding attestation that just like jumps<01:50:28.409> over<01:50:28.619> it<01:50:32.479> that's<01:50:33.479> it<01:50:34.940> cool<01:50:35.940> yeah<01:50:37.849> thank 01:50:38.839 --> 01:50:38.849 align:start position:0% jumps over it that's it cool yeah thank 01:50:38.849 --> 01:50:40.819 align:start position:0% jumps over it that's it cool yeah thank you<01:50:38.999> that<01:50:39.360> was<01:50:39.449> a<01:50:39.479> long<01:50:39.630> session<01:50:39.900> appreciate 01:50:40.819 --> 01:50:40.829 align:start position:0% you that was a long session appreciate 01:50:40.829 --> 01:50:42.160 align:start position:0% you that was a long session appreciate you<01:50:40.949> all<01:50:41.070> being<01:50:41.099> here 01:50:42.160 --> 01:50:42.170 align:start position:0% you all being here 01:50:42.170 --> 01:50:43.690 align:start position:0% you all being here [Music] 01:50:43.690 --> 01:50:43.700 align:start position:0% [Music] 01:50:43.700 --> 01:50:52.050 align:start position:0% [Music] you 01:50:52.050 --> 01:50:52.060 align:start position:0% 01:50:52.060 --> 01:50:54.120 align:start position:0% you