WEBVTT Kind: captions Language: en 00:00:04.680 --> 00:00:06.560 align:start position:0% we're<00:00:05.310> gonna<00:00:05.400> talk<00:00:05.640> today<00:00:05.820> about<00:00:05.910> the<00:00:06.120> CDC 00:00:06.560 --> 00:00:06.570 align:start position:0% we're gonna talk today about the CDC 00:00:06.570 --> 00:00:08.480 align:start position:0% we're gonna talk today about the CDC Casper<00:00:06.900> roadmap<00:00:07.260> and<00:00:07.529> there's<00:00:08.220> gonna<00:00:08.310> be<00:00:08.400> a 00:00:08.480 --> 00:00:08.490 align:start position:0% Casper roadmap and there's gonna be a 00:00:08.490 --> 00:00:10.070 align:start position:0% Casper roadmap and there's gonna be a little<00:00:08.700> bit<00:00:08.820> less<00:00:08.970> action-packed<00:00:09.600> than<00:00:09.900> the 00:00:10.070 --> 00:00:10.080 align:start position:0% little bit less action-packed than the 00:00:10.080 --> 00:00:15.500 align:start position:0% little bit less action-packed than the normal<00:00:10.440> Def<00:00:11.190> Con<00:00:11.400> talk<00:00:12.710> so<00:00:14.150> here's<00:00:15.150> my<00:00:15.360> little 00:00:15.500 --> 00:00:15.510 align:start position:0% normal Def Con talk so here's my little 00:00:15.510 --> 00:00:20.120 align:start position:0% normal Def Con talk so here's my little outline<00:00:15.870> we're<00:00:16.619> gonna<00:00:17.040> be<00:00:17.130> talking<00:00:17.430> about<00:00:19.130> the 00:00:20.120 --> 00:00:20.130 align:start position:0% outline we're gonna be talking about the 00:00:20.130 --> 00:00:22.700 align:start position:0% outline we're gonna be talking about the roadmap<00:00:20.430> as<00:00:20.850> a<00:00:21.150> research<00:00:21.539> roadmap<00:00:21.900> as<00:00:22.410> opposed 00:00:22.700 --> 00:00:22.710 align:start position:0% roadmap as a research roadmap as opposed 00:00:22.710 --> 00:00:26.920 align:start position:0% roadmap as a research roadmap as opposed to<00:00:22.800> an<00:00:22.920> implementation<00:00:23.100> roadmap<00:00:23.880> or<00:00:24.060> like 00:00:26.920 --> 00:00:26.930 align:start position:0% 00:00:26.930 --> 00:00:31.160 align:start position:0% roadmap<00:00:27.930> for<00:00:28.289> developers<00:00:29.840> I'm<00:00:30.840> gonna<00:00:31.050> talk 00:00:31.160 --> 00:00:31.170 align:start position:0% roadmap for developers I'm gonna talk 00:00:31.170 --> 00:00:33.020 align:start position:0% roadmap for developers I'm gonna talk about<00:00:31.320> the<00:00:31.380> relationship<00:00:31.830> between<00:00:32.030> my 00:00:33.020 --> 00:00:33.030 align:start position:0% about the relationship between my 00:00:33.030 --> 00:00:34.850 align:start position:0% about the relationship between my roadmap<00:00:33.239> and<00:00:33.570> the<00:00:33.660> theorem<00:00:33.870> roadmaps<00:00:34.350> I'm 00:00:34.850 --> 00:00:34.860 align:start position:0% roadmap and the theorem roadmaps I'm 00:00:34.860 --> 00:00:36.049 align:start position:0% roadmap and the theorem roadmaps I'm gonna<00:00:35.070> talk<00:00:35.190> about<00:00:35.400> our<00:00:35.640> past<00:00:35.850> and<00:00:35.970> future 00:00:36.049 --> 00:00:36.059 align:start position:0% gonna talk about our past and future 00:00:36.059 --> 00:00:37.639 align:start position:0% gonna talk about our past and future work<00:00:36.420> because<00:00:36.750> to<00:00:36.780> some<00:00:37.050> how<00:00:37.170> the<00:00:37.230> roadmap<00:00:37.620> is 00:00:37.639 --> 00:00:37.649 align:start position:0% work because to some how the roadmap is 00:00:37.649 --> 00:00:39.830 align:start position:0% work because to some how the roadmap is made<00:00:37.950> up<00:00:38.100> of<00:00:38.250> all<00:00:38.550> the<00:00:39.120> stuff<00:00:39.300> we've<00:00:39.450> done<00:00:39.480> and 00:00:39.830 --> 00:00:39.840 align:start position:0% made up of all the stuff we've done and 00:00:39.840 --> 00:00:41.090 align:start position:0% made up of all the stuff we've done and all<00:00:39.899> the<00:00:39.989> stuff<00:00:40.170> I'm<00:00:40.320> going<00:00:40.470> to<00:00:40.559> do<00:00:40.770> or 00:00:41.090 --> 00:00:41.100 align:start position:0% all the stuff I'm going to do or 00:00:41.100 --> 00:00:43.370 align:start position:0% all the stuff I'm going to do or planning<00:00:41.489> to<00:00:41.520> do<00:00:41.700> and<00:00:41.940> then<00:00:42.870> I'm<00:00:42.989> gonna<00:00:43.110> talk 00:00:43.370 --> 00:00:43.380 align:start position:0% planning to do and then I'm gonna talk 00:00:43.380 --> 00:00:45.170 align:start position:0% planning to do and then I'm gonna talk about<00:00:43.530> and<00:00:43.800> I'm<00:00:43.890> gonna<00:00:44.010> give<00:00:44.160> some<00:00:44.190> resources 00:00:45.170 --> 00:00:45.180 align:start position:0% about and I'm gonna give some resources 00:00:45.180 --> 00:00:50.270 align:start position:0% about and I'm gonna give some resources and<00:00:45.360> announcements<00:00:46.219> so<00:00:48.710> CBC<00:00:49.710> Casper<00:00:49.980> roadmap 00:00:50.270 --> 00:00:50.280 align:start position:0% and announcements so CBC Casper roadmap 00:00:50.280 --> 00:00:52.940 align:start position:0% and announcements so CBC Casper roadmap is<00:00:50.430> I<00:00:50.969> was<00:00:51.360> saying<00:00:51.570> it's<00:00:52.020> a<00:00:52.200> research<00:00:52.620> and 00:00:52.940 --> 00:00:52.950 align:start position:0% is I was saying it's a research and 00:00:52.950 --> 00:00:55.250 align:start position:0% is I was saying it's a research and architecture<00:00:53.489> roadmap<00:00:53.879> the<00:00:54.210> outputs<00:00:55.050> of<00:00:55.170> this 00:00:55.250 --> 00:00:55.260 align:start position:0% architecture roadmap the outputs of this 00:00:55.260 --> 00:00:57.740 align:start position:0% architecture roadmap the outputs of this roadmap<00:00:55.739> or<00:00:56.309> research<00:00:56.910> the<00:00:57.030> specifications 00:00:57.740 --> 00:00:57.750 align:start position:0% roadmap or research the specifications 00:00:57.750 --> 00:01:00.650 align:start position:0% roadmap or research the specifications you<00:00:57.989> know<00:00:58.590> we<00:00:58.739> don't<00:00:58.890> like<00:00:59.700> the<00:00:59.850> goal<00:01:00.239> of<00:01:00.539> the 00:01:00.650 --> 00:01:00.660 align:start position:0% you know we don't like the goal of the 00:01:00.660 --> 00:01:03.049 align:start position:0% you know we don't like the goal of the roadmap<00:01:00.840> is<00:01:01.140> to<00:01:01.289> produce<00:01:01.469> architecture<00:01:02.280> to 00:01:03.049 --> 00:01:03.059 align:start position:0% roadmap is to produce architecture to 00:01:03.059 --> 00:01:07.150 align:start position:0% roadmap is to produce architecture to produce<00:01:03.239> you<00:01:03.989> know<00:01:04.369> research<00:01:05.369> in<00:01:05.789> the<00:01:05.910> form<00:01:06.180> of 00:01:07.150 --> 00:01:07.160 align:start position:0% produce you know research in the form of 00:01:07.160 --> 00:01:10.749 align:start position:0% produce you know research in the form of distributed<00:01:08.160> systems<00:01:08.580> computer<00:01:09.420> science 00:01:10.749 --> 00:01:10.759 align:start position:0% distributed systems computer science 00:01:10.759 --> 00:01:13.550 align:start position:0% distributed systems computer science like<00:01:11.759> theoretical<00:01:12.539> computer<00:01:12.899> science<00:01:13.289> you 00:01:13.550 --> 00:01:13.560 align:start position:0% like theoretical computer science you 00:01:13.560 --> 00:01:14.840 align:start position:0% like theoretical computer science you know<00:01:13.649> and<00:01:14.310> but<00:01:14.459> also<00:01:14.580> to<00:01:14.729> produce 00:01:14.840 --> 00:01:14.850 align:start position:0% know and but also to produce 00:01:14.850 --> 00:01:18.410 align:start position:0% know and but also to produce specifications<00:01:15.690> which<00:01:16.200> serve<00:01:16.890> as<00:01:17.420> abstract 00:01:18.410 --> 00:01:18.420 align:start position:0% specifications which serve as abstract 00:01:18.420 --> 00:01:21.559 align:start position:0% specifications which serve as abstract descriptions<00:01:19.140> of<00:01:19.410> protocols<00:01:20.190> which<00:01:20.940> if<00:01:21.179> you 00:01:21.559 --> 00:01:21.569 align:start position:0% descriptions of protocols which if you 00:01:21.569 --> 00:01:23.270 align:start position:0% descriptions of protocols which if you can<00:01:21.959> if<00:01:22.289> you<00:01:22.380> implement<00:01:22.619> anything<00:01:22.920> that<00:01:23.130> match 00:01:23.270 --> 00:01:23.280 align:start position:0% can if you implement anything that match 00:01:23.280 --> 00:01:24.919 align:start position:0% can if you implement anything that match the<00:01:23.490> specifications<00:01:24.179> you'll<00:01:24.599> get<00:01:24.720> all<00:01:24.840> the 00:01:24.919 --> 00:01:24.929 align:start position:0% the specifications you'll get all the 00:01:24.929 --> 00:01:27.080 align:start position:0% the specifications you'll get all the benefits<00:01:25.259> of<00:01:25.319> the<00:01:25.410> architecture<00:01:25.830> so<00:01:26.550> somehow 00:01:27.080 --> 00:01:27.090 align:start position:0% benefits of the architecture so somehow 00:01:27.090 --> 00:01:30.109 align:start position:0% benefits of the architecture so somehow the<00:01:27.720> CVC<00:01:28.140> Casper<00:01:28.530> roadmap<00:01:29.119> produces 00:01:30.109 --> 00:01:30.119 align:start position:0% the CVC Casper roadmap produces 00:01:30.119 --> 00:01:33.620 align:start position:0% the CVC Casper roadmap produces architecture<00:01:30.869> and<00:01:31.759> research<00:01:32.759> and<00:01:33.060> then<00:01:33.450> it's 00:01:33.620 --> 00:01:33.630 align:start position:0% architecture and research and then it's 00:01:33.630 --> 00:01:35.449 align:start position:0% architecture and research and then it's up<00:01:33.720> to<00:01:33.750> engineers<00:01:34.200> to<00:01:34.590> implement<00:01:35.369> the 00:01:35.449 --> 00:01:35.459 align:start position:0% up to engineers to implement the 00:01:35.459 --> 00:01:37.580 align:start position:0% up to engineers to implement the architecture<00:01:36.000> in<00:01:36.360> a<00:01:36.450> way<00:01:36.599> that<00:01:36.840> works<00:01:37.470> for 00:01:37.580 --> 00:01:37.590 align:start position:0% architecture in a way that works for 00:01:37.590 --> 00:01:39.260 align:start position:0% architecture in a way that works for them<00:01:37.800> and<00:01:38.099> any<00:01:38.580> way<00:01:38.759> that<00:01:38.910> implement<00:01:39.240> the 00:01:39.260 --> 00:01:39.270 align:start position:0% them and any way that implement the 00:01:39.270 --> 00:01:41.089 align:start position:0% them and any way that implement the architecture<00:01:39.720> will<00:01:39.899> inherit<00:01:40.440> the<00:01:40.590> properties 00:01:41.089 --> 00:01:41.099 align:start position:0% architecture will inherit the properties 00:01:41.099 --> 00:01:44.059 align:start position:0% architecture will inherit the properties of<00:01:41.130> the<00:01:41.399> architecture<00:01:41.910> so<00:01:42.660> you<00:01:43.500> know<00:01:43.979> if 00:01:44.059 --> 00:01:44.069 align:start position:0% of the architecture so you know if 00:01:44.069 --> 00:01:45.650 align:start position:0% of the architecture so you know if there's<00:01:44.369> like<00:01:44.550> if<00:01:44.670> we<00:01:44.759> prove<00:01:45.000> that<00:01:45.149> its 00:01:45.650 --> 00:01:45.660 align:start position:0% there's like if we prove that its 00:01:45.660 --> 00:01:47.540 align:start position:0% there's like if we prove that its architecture<00:01:46.050> has<00:01:46.200> a<00:01:46.229> property<00:01:46.649> then<00:01:46.950> any<00:01:47.280> of 00:01:47.540 --> 00:01:47.550 align:start position:0% architecture has a property then any of 00:01:47.550 --> 00:01:49.400 align:start position:0% architecture has a property then any of the<00:01:47.640> many<00:01:47.819> ways<00:01:48.000> it<00:01:48.539> can<00:01:48.630> be<00:01:48.750> implemented<00:01:49.080> will 00:01:49.400 --> 00:01:49.410 align:start position:0% the many ways it can be implemented will 00:01:49.410 --> 00:01:51.770 align:start position:0% the many ways it can be implemented will benefit<00:01:49.830> from<00:01:49.920> that<00:01:50.039> property<00:01:50.250> and<00:01:50.610> so<00:01:51.390> you 00:01:51.770 --> 00:01:51.780 align:start position:0% benefit from that property and so you 00:01:51.780 --> 00:01:53.359 align:start position:0% benefit from that property and so you know<00:01:51.869> the<00:01:52.229> CBC<00:01:52.530> Casper<00:01:52.800> research<00:01:53.069> doesn't 00:01:53.359 --> 00:01:53.369 align:start position:0% know the CBC Casper research doesn't 00:01:53.369 --> 00:01:55.430 align:start position:0% know the CBC Casper research doesn't produce<00:01:53.580> complete<00:01:54.330> protocol<00:01:54.780> specifications 00:01:55.430 --> 00:01:55.440 align:start position:0% produce complete protocol specifications 00:01:55.440 --> 00:01:57.169 align:start position:0% produce complete protocol specifications it<00:01:55.649> produces<00:01:56.489> architecture<00:01:57.060> level 00:01:57.169 --> 00:01:57.179 align:start position:0% it produces architecture level 00:01:57.179 --> 00:01:59.600 align:start position:0% it produces architecture level specifications<00:01:57.929> which<00:01:58.470> are<00:01:58.679> which<00:01:59.160> is<00:01:59.280> for 00:01:59.600 --> 00:01:59.610 align:start position:0% specifications which are which is for 00:01:59.610 --> 00:02:00.529 align:start position:0% specifications which are which is for which<00:01:59.700> it's<00:01:59.849> guaranteed<00:02:00.209> that<00:02:00.360> any 00:02:00.529 --> 00:02:00.539 align:start position:0% which it's guaranteed that any 00:02:00.539 --> 00:02:01.729 align:start position:0% which it's guaranteed that any implementation<00:02:00.810> that<00:02:01.289> matches<00:02:01.619> the 00:02:01.729 --> 00:02:01.739 align:start position:0% implementation that matches the 00:02:01.739 --> 00:02:05.630 align:start position:0% implementation that matches the architecture<00:02:02.220> will<00:02:02.910> benefit<00:02:03.569> from<00:02:04.039> the<00:02:05.039> from 00:02:05.630 --> 00:02:05.640 align:start position:0% architecture will benefit from the from 00:02:05.640 --> 00:02:07.969 align:start position:0% architecture will benefit from the from from<00:02:06.000> from<00:02:06.030> the<00:02:06.509> men<00:02:07.050> from<00:02:07.349> the<00:02:07.500> features<00:02:07.830> or 00:02:07.969 --> 00:02:07.979 align:start position:0% from from the men from the features or 00:02:07.979 --> 00:02:08.660 align:start position:0% from from the men from the features or the 00:02:08.660 --> 00:02:08.670 align:start position:0% the 00:02:08.670 --> 00:02:15.410 align:start position:0% the these<00:02:08.940> protocols<00:02:09.649> they<00:02:10.649> are<00:02:13.880> you<00:02:14.880> know<00:02:14.970> we<00:02:15.090> are 00:02:15.410 --> 00:02:15.420 align:start position:0% these protocols they are you know we are 00:02:15.420 --> 00:02:19.670 align:start position:0% these protocols they are you know we are gonna<00:02:17.510> so<00:02:18.510> we're<00:02:18.780> kind<00:02:18.959> of<00:02:18.989> independent<00:02:19.500> from 00:02:19.670 --> 00:02:19.680 align:start position:0% gonna so we're kind of independent from 00:02:19.680 --> 00:02:21.080 align:start position:0% gonna so we're kind of independent from the<00:02:19.830> engineering<00:02:20.250> effort<00:02:20.550> so<00:02:20.700> if<00:02:20.790> we<00:02:20.849> ended 00:02:21.080 --> 00:02:21.090 align:start position:0% the engineering effort so if we ended 00:02:21.090 --> 00:02:23.089 align:start position:0% the engineering effort so if we ended architecture<00:02:21.630> and<00:02:21.930> then<00:02:22.080> engineering<00:02:22.709> and<00:02:23.010> it 00:02:23.089 --> 00:02:23.099 align:start position:0% architecture and then engineering and it 00:02:23.099 --> 00:02:28.520 align:start position:0% architecture and then engineering and it happens<00:02:23.340> after<00:02:25.970> but<00:02:26.970> you<00:02:27.660> know<00:02:27.780> doesn't<00:02:28.410> mean 00:02:28.520 --> 00:02:28.530 align:start position:0% happens after but you know doesn't mean 00:02:28.530 --> 00:02:30.440 align:start position:0% happens after but you know doesn't mean we<00:02:28.739> don't<00:02:28.950> provide<00:02:29.370> support<00:02:29.880> to<00:02:29.910> software 00:02:30.440 --> 00:02:30.450 align:start position:0% we don't provide support to software 00:02:30.450 --> 00:02:31.940 align:start position:0% we don't provide support to software developers<00:02:30.900> and<00:02:30.989> help<00:02:31.200> them<00:02:31.350> interpret<00:02:31.680> the 00:02:31.940 --> 00:02:31.950 align:start position:0% developers and help them interpret the 00:02:31.950 --> 00:02:33.920 align:start position:0% developers and help them interpret the architecture<00:02:32.520> or<00:02:32.550> you<00:02:33.360> know<00:02:33.450> we're<00:02:33.810> gonna 00:02:33.920 --> 00:02:33.930 align:start position:0% architecture or you know we're gonna 00:02:33.930 --> 00:02:36.080 align:start position:0% architecture or you know we're gonna provide<00:02:34.170> support<00:02:34.650> even<00:02:34.860> though<00:02:35.100> it's<00:02:35.580> not<00:02:35.790> the 00:02:36.080 --> 00:02:36.090 align:start position:0% provide support even though it's not the 00:02:36.090 --> 00:02:39.170 align:start position:0% provide support even though it's not the roadmap<00:02:36.989> to<00:02:37.310> implement<00:02:38.310> it<00:02:38.459> if<00:02:38.760> the<00:02:38.880> roadmap 00:02:39.170 --> 00:02:39.180 align:start position:0% roadmap to implement it if the roadmap 00:02:39.180 --> 00:02:40.640 align:start position:0% roadmap to implement it if the roadmap is<00:02:39.300> to<00:02:39.420> come<00:02:39.569> up<00:02:39.660> with<00:02:39.750> the<00:02:39.870> architectures<00:02:40.380> and 00:02:40.640 --> 00:02:40.650 align:start position:0% is to come up with the architectures and 00:02:40.650 --> 00:02:44.509 align:start position:0% is to come up with the architectures and then<00:02:40.950> to<00:02:41.730> do<00:02:42.269> the<00:02:42.450> research<00:02:43.160> it's<00:02:44.160> a<00:02:44.250> research 00:02:44.509 --> 00:02:44.519 align:start position:0% then to do the research it's a research 00:02:44.519 --> 00:02:46.670 align:start position:0% then to do the research it's a research roadmap<00:02:44.970> it's<00:02:45.690> all<00:02:45.780> about<00:02:45.959> building<00:02:46.200> correct 00:02:46.670 --> 00:02:46.680 align:start position:0% roadmap it's all about building correct 00:02:46.680 --> 00:02:48.979 align:start position:0% roadmap it's all about building correct by<00:02:46.769> construction<00:02:47.160> consensus<00:02:47.670> verticals<00:02:48.090> we 00:02:48.979 --> 00:02:48.989 align:start position:0% by construction consensus verticals we 00:02:48.989 --> 00:02:50.990 align:start position:0% by construction consensus verticals we correct<00:02:49.890> by<00:02:49.980> construction<00:02:50.430> engineering<00:02:50.760> is 00:02:50.990 --> 00:02:51.000 align:start position:0% correct by construction engineering is 00:02:51.000 --> 00:02:53.840 align:start position:0% correct by construction engineering is about<00:02:51.620> designing<00:02:52.620> your<00:02:52.920> systems<00:02:53.430> in<00:02:53.670> a<00:02:53.730> way 00:02:53.840 --> 00:02:53.850 align:start position:0% about designing your systems in a way 00:02:53.850 --> 00:02:55.789 align:start position:0% about designing your systems in a way that<00:02:54.030> is<00:02:54.120> guaranteed<00:02:54.690> by<00:02:55.019> the<00:02:55.049> process<00:02:55.650> you 00:02:55.789 --> 00:02:55.799 align:start position:0% that is guaranteed by the process you 00:02:55.799 --> 00:02:58.430 align:start position:0% that is guaranteed by the process you design<00:02:56.100> them<00:02:56.250> to<00:02:56.580> be<00:02:56.670> correct<00:02:56.970> it's<00:02:57.930> it's 00:02:58.430 --> 00:02:58.440 align:start position:0% design them to be correct it's it's 00:02:58.440 --> 00:03:02.960 align:start position:0% design them to be correct it's it's about<00:02:58.709> not<00:02:59.370> the<00:03:00.890> correctness<00:03:01.890> it's<00:03:02.580> about<00:03:02.819> the 00:03:02.960 --> 00:03:02.970 align:start position:0% about not the correctness it's about the 00:03:02.970 --> 00:03:06.020 align:start position:0% about not the correctness it's about the process<00:03:03.540> that<00:03:03.750> is<00:03:04.110> used<00:03:04.530> to<00:03:04.769> just<00:03:05.280> to<00:03:05.730> just<00:03:05.970> to 00:03:06.020 --> 00:03:06.030 align:start position:0% process that is used to just to just to 00:03:06.030 --> 00:03:08.930 align:start position:0% process that is used to just to just to develop<00:03:06.660> these<00:03:06.750> protocols<00:03:07.130> so<00:03:08.130> we<00:03:08.610> really 00:03:08.930 --> 00:03:08.940 align:start position:0% develop these protocols so we really 00:03:08.940 --> 00:03:10.910 align:start position:0% develop these protocols so we really formally<00:03:09.750> state<00:03:09.989> the<00:03:10.140> design<00:03:10.350> requirements 00:03:10.910 --> 00:03:10.920 align:start position:0% formally state the design requirements 00:03:10.920 --> 00:03:15.610 align:start position:0% formally state the design requirements and<00:03:11.239> abstractly<00:03:12.239> state<00:03:12.569> protocol<00:03:13.200> statements 00:03:15.610 --> 00:03:15.620 align:start position:0% and abstractly state protocol statements 00:03:15.620 --> 00:03:19.640 align:start position:0% and abstractly state protocol statements and<00:03:16.850> then<00:03:17.850> we<00:03:18.000> refine<00:03:18.690> them<00:03:18.959> in<00:03:19.260> order<00:03:19.530> to 00:03:19.640 --> 00:03:19.650 align:start position:0% and then we refine them in order to 00:03:19.650 --> 00:03:21.560 align:start position:0% and then we refine them in order to derive<00:03:19.950> from<00:03:20.280> the<00:03:20.489> problem<00:03:21.000> statements<00:03:21.420> a 00:03:21.560 --> 00:03:21.570 align:start position:0% derive from the problem statements a 00:03:21.570 --> 00:03:23.150 align:start position:0% derive from the problem statements a solution<00:03:22.200> to<00:03:22.350> the<00:03:22.440> problem<00:03:22.799> that<00:03:22.920> is 00:03:23.150 --> 00:03:23.160 align:start position:0% solution to the problem that is 00:03:23.160 --> 00:03:24.650 align:start position:0% solution to the problem that is guaranteed<00:03:23.370> by<00:03:23.940> the<00:03:24.000> way<00:03:24.299> that<00:03:24.510> it<00:03:24.600> was 00:03:24.650 --> 00:03:24.660 align:start position:0% guaranteed by the way that it was 00:03:24.660 --> 00:03:28.580 align:start position:0% guaranteed by the way that it was derived<00:03:24.989> to<00:03:25.200> be<00:03:25.320> correct<00:03:26.359> and<00:03:27.359> so<00:03:27.630> you<00:03:27.989> know<00:03:28.109> we 00:03:28.580 --> 00:03:28.590 align:start position:0% derived to be correct and so you know we 00:03:28.590 --> 00:03:30.920 align:start position:0% derived to be correct and so you know we state<00:03:29.310> the<00:03:29.340> design<00:03:29.640> requirements<00:03:30.239> and<00:03:30.420> then 00:03:30.920 --> 00:03:30.930 align:start position:0% state the design requirements and then 00:03:30.930 --> 00:03:32.539 align:start position:0% state the design requirements and then we<00:03:31.049> kind<00:03:31.230> of<00:03:31.320> will<00:03:31.739> derive<00:03:32.040> a<00:03:32.100> solution<00:03:32.459> to 00:03:32.539 --> 00:03:32.549 align:start position:0% we kind of will derive a solution to 00:03:32.549 --> 00:03:33.830 align:start position:0% we kind of will derive a solution to satisfy<00:03:32.820> them<00:03:32.970> directly<00:03:33.299> from<00:03:33.450> the<00:03:33.600> design 00:03:33.830 --> 00:03:33.840 align:start position:0% satisfy them directly from the design 00:03:33.840 --> 00:03:35.780 align:start position:0% satisfy them directly from the design requirements<00:03:34.410> which<00:03:35.040> are<00:03:35.190> in<00:03:35.400> terms<00:03:35.609> of 00:03:35.780 --> 00:03:35.790 align:start position:0% requirements which are in terms of 00:03:35.790 --> 00:03:38.990 align:start position:0% requirements which are in terms of abstract<00:03:36.030> protocol<00:03:36.600> specifications<00:03:37.640> so<00:03:38.640> and 00:03:38.990 --> 00:03:39.000 align:start position:0% abstract protocol specifications so and 00:03:39.000 --> 00:03:40.550 align:start position:0% abstract protocol specifications so and specifically<00:03:39.959> we're<00:03:40.140> interested<00:03:40.410> not<00:03:40.500> just 00:03:40.550 --> 00:03:40.560 align:start position:0% specifically we're interested not just 00:03:40.560 --> 00:03:42.380 align:start position:0% specifically we're interested not just any<00:03:40.799> cuz<00:03:40.980> it's<00:03:41.100> protocols<00:03:41.459> we<00:03:41.609> want<00:03:41.820> scaleable 00:03:42.380 --> 00:03:42.390 align:start position:0% any cuz it's protocols we want scaleable 00:03:42.390 --> 00:03:43.640 align:start position:0% any cuz it's protocols we want scaleable probes<00:03:42.540> take<00:03:42.750> this<00:03:42.900> protocol<00:03:43.320> to<00:03:43.380> have<00:03:43.560> the 00:03:43.640 --> 00:03:43.650 align:start position:0% probes take this protocol to have the 00:03:43.650 --> 00:03:45.410 align:start position:0% probes take this protocol to have the same<00:03:43.859> network<00:03:44.100> overhead<00:03:44.430> as<00:03:44.730> Nakamoto 00:03:45.410 --> 00:03:45.420 align:start position:0% same network overhead as Nakamoto 00:03:45.420 --> 00:03:48.140 align:start position:0% same network overhead as Nakamoto consensus<00:03:45.980> you<00:03:46.980> know<00:03:47.100> we<00:03:47.430> want<00:03:47.609> to<00:03:47.700> be<00:03:47.790> able<00:03:47.880> to 00:03:48.140 --> 00:03:48.150 align:start position:0% consensus you know we want to be able to 00:03:48.150 --> 00:03:50.360 align:start position:0% consensus you know we want to be able to have<00:03:49.019> lock<00:03:49.470> chains<00:03:49.769> that<00:03:49.920> work<00:03:50.100> on<00:03:50.280> the 00:03:50.360 --> 00:03:50.370 align:start position:0% have lock chains that work on the 00:03:50.370 --> 00:03:52.370 align:start position:0% have lock chains that work on the internet<00:03:50.700> scale<00:03:50.910> that<00:03:51.180> don't<00:03:51.329> have<00:03:51.480> crazy 00:03:52.370 --> 00:03:52.380 align:start position:0% internet scale that don't have crazy 00:03:52.380 --> 00:03:53.690 align:start position:0% internet scale that don't have crazy overhead<00:03:52.829> like<00:03:52.980> a<00:03:53.010> traditional<00:03:53.370> consensus 00:03:53.690 --> 00:03:53.700 align:start position:0% overhead like a traditional consensus 00:03:53.700 --> 00:03:56.599 align:start position:0% overhead like a traditional consensus protocol<00:03:54.109> and<00:03:55.109> but<00:03:56.069> I<00:03:56.100> actually<00:03:56.310> have<00:03:56.549> the 00:03:56.599 --> 00:03:56.609 align:start position:0% protocol and but I actually have the 00:03:56.609 --> 00:03:58.160 align:start position:0% protocol and but I actually have the same<00:03:56.790> overhead<00:03:57.120> as<00:03:57.209> Nakamoto<00:03:57.569> consensus<00:03:58.019> or 00:03:58.160 --> 00:03:58.170 align:start position:0% same overhead as Nakamoto consensus or 00:03:58.170 --> 00:04:00.080 align:start position:0% same overhead as Nakamoto consensus or comparable<00:03:58.650> to<00:03:59.069> the<00:03:59.220> overhead<00:03:59.459> of<00:03:59.519> current 00:04:00.080 --> 00:04:00.090 align:start position:0% comparable to the overhead of current 00:04:00.090 --> 00:04:02.599 align:start position:0% comparable to the overhead of current aetherium<00:04:00.859> so<00:04:01.859> basically<00:04:02.130> we<00:04:02.280> want<00:04:02.459> to<00:04:02.549> be 00:04:02.599 --> 00:04:02.609 align:start position:0% aetherium so basically we want to be 00:04:02.609 --> 00:04:04.069 align:start position:0% aetherium so basically we want to be able<00:04:02.670> to<00:04:02.819> make<00:04:02.910> to<00:04:03.450> meet<00:04:03.569> all<00:04:03.720> the<00:04:03.840> normal 00:04:04.069 --> 00:04:04.079 align:start position:0% able to make to meet all the normal 00:04:04.079 --> 00:04:05.210 align:start position:0% able to make to meet all the normal requirements<00:04:04.650> all<00:04:04.739> the<00:04:04.859> traditional 00:04:05.210 --> 00:04:05.220 align:start position:0% requirements all the traditional 00:04:05.220 --> 00:04:06.650 align:start position:0% requirements all the traditional requirements<00:04:05.459> of<00:04:05.880> a<00:04:06.000> consensus<00:04:06.329> protocol 00:04:06.650 --> 00:04:06.660 align:start position:0% requirements of a consensus protocol 00:04:06.660 --> 00:04:08.509 align:start position:0% requirements of a consensus protocol like<00:04:07.260> safety<00:04:07.590> and<00:04:07.889> on<00:04:07.950> triviality<00:04:08.489> and 00:04:08.509 --> 00:04:08.519 align:start position:0% like safety and on triviality and 00:04:08.519 --> 00:04:08.990 align:start position:0% like safety and on triviality and liveness 00:04:08.990 --> 00:04:09.000 align:start position:0% liveness 00:04:09.000 --> 00:04:11.360 align:start position:0% liveness and<00:04:09.690> also<00:04:09.930> a<00:04:09.959> bunch<00:04:10.139> of<00:04:10.260> other<00:04:10.410> requirements 00:04:11.360 --> 00:04:11.370 align:start position:0% and also a bunch of other requirements 00:04:11.370 --> 00:04:12.920 align:start position:0% and also a bunch of other requirements like<00:04:11.489> for<00:04:11.700> example<00:04:11.760> being<00:04:12.329> able<00:04:12.420> to<00:04:12.510> make<00:04:12.750> this 00:04:12.920 --> 00:04:12.930 align:start position:0% like for example being able to make this 00:04:12.930 --> 00:04:16.940 align:start position:0% like for example being able to make this ideal<00:04:14.810> theoretically<00:04:15.810> optimal<00:04:16.229> overhead 00:04:16.940 --> 00:04:16.950 align:start position:0% ideal theoretically optimal overhead 00:04:16.950 --> 00:04:18.649 align:start position:0% ideal theoretically optimal overhead trade-off<00:04:17.280> and<00:04:17.909> also<00:04:18.150> we're<00:04:18.299> interested<00:04:18.630> in 00:04:18.649 --> 00:04:18.659 align:start position:0% trade-off and also we're interested in 00:04:18.659 --> 00:04:19.819 align:start position:0% trade-off and also we're interested in scalability 00:04:19.819 --> 00:04:19.829 align:start position:0% scalability 00:04:19.829 --> 00:04:22.480 align:start position:0% scalability in<00:04:20.160> you-know-who<00:04:20.910> starting<00:04:21.449> and<00:04:21.600> basically 00:04:22.480 --> 00:04:22.490 align:start position:0% in you-know-who starting and basically 00:04:22.490 --> 00:04:24.680 align:start position:0% in you-know-who starting and basically which<00:04:23.490> we<00:04:23.610> understand<00:04:24.000> entirely<00:04:24.330> inside<00:04:24.630> a 00:04:24.680 --> 00:04:24.690 align:start position:0% which we understand entirely inside a 00:04:24.690 --> 00:04:27.260 align:start position:0% which we understand entirely inside a consensus<00:04:25.080> protocol<00:04:25.290> Fremont 00:04:27.260 --> 00:04:27.270 align:start position:0% consensus protocol Fremont 00:04:27.270 --> 00:04:29.270 align:start position:0% consensus protocol Fremont where<00:04:28.080> you<00:04:28.320> know<00:04:28.410> if<00:04:28.590> you<00:04:28.919> went<00:04:29.100> to<00:04:29.160> the 00:04:29.270 --> 00:04:29.280 align:start position:0% where you know if you went to the 00:04:29.280 --> 00:04:32.000 align:start position:0% where you know if you went to the sharding<00:04:29.610> workshop<00:04:30.270> yesterday<00:04:30.800> that<00:04:31.800> was<00:04:31.889> all 00:04:32.000 --> 00:04:32.010 align:start position:0% sharding workshop yesterday that was all 00:04:32.010 --> 00:04:32.570 align:start position:0% sharding workshop yesterday that was all about<00:04:32.220> that 00:04:32.570 --> 00:04:32.580 align:start position:0% about that 00:04:32.580 --> 00:04:35.230 align:start position:0% about that so<00:04:33.030> I'm<00:04:33.120> not<00:04:33.240> gonna<00:04:33.389> really<00:04:33.750> touch<00:04:33.990> on<00:04:34.110> it<00:04:34.260> now 00:04:35.230 --> 00:04:35.240 align:start position:0% so I'm not gonna really touch on it now 00:04:35.240 --> 00:04:38.120 align:start position:0% so I'm not gonna really touch on it now so<00:04:36.240> we<00:04:36.510> have<00:04:36.690> a<00:04:36.720> really<00:04:37.050> deeply<00:04:37.590> formalistic 00:04:38.120 --> 00:04:38.130 align:start position:0% so we have a really deeply formalistic 00:04:38.130 --> 00:04:41.710 align:start position:0% so we have a really deeply formalistic approach<00:04:38.430> to<00:04:39.120> protocol<00:04:39.630> design<00:04:39.930> we<00:04:40.620> are 00:04:41.710 --> 00:04:41.720 align:start position:0% approach to protocol design we are 00:04:41.720 --> 00:04:44.110 align:start position:0% approach to protocol design we are formal<00:04:42.720> from<00:04:42.900> the<00:04:43.020> very<00:04:43.229> start<00:04:43.350> we<00:04:43.800> never 00:04:44.110 --> 00:04:44.120 align:start position:0% formal from the very start we never 00:04:44.120 --> 00:04:48.530 align:start position:0% formal from the very start we never engage<00:04:45.120> in<00:04:46.130> trial<00:04:47.130> and<00:04:47.280> error<00:04:47.610> in<00:04:48.060> the<00:04:48.150> normal 00:04:48.530 --> 00:04:48.540 align:start position:0% engage in trial and error in the normal 00:04:48.540 --> 00:04:51.710 align:start position:0% engage in trial and error in the normal kind<00:04:48.870> of<00:04:49.490> development<00:04:50.490> fashion<00:04:50.880> we<00:04:51.270> don't 00:04:51.710 --> 00:04:51.720 align:start position:0% kind of development fashion we don't 00:04:51.720 --> 00:04:53.659 align:start position:0% kind of development fashion we don't implement<00:04:52.080> stuff<00:04:52.470> until<00:04:52.800> we<00:04:52.979> know<00:04:53.250> for<00:04:53.639> sure 00:04:53.659 --> 00:04:53.669 align:start position:0% implement stuff until we know for sure 00:04:53.669 --> 00:04:57.010 align:start position:0% implement stuff until we know for sure that<00:04:54.600> it's<00:04:54.810> correct<00:04:55.010> we<00:04:56.010> do<00:04:56.310> a<00:04:56.340> lot<00:04:56.580> of<00:04:56.610> math 00:04:57.010 --> 00:04:57.020 align:start position:0% that it's correct we do a lot of math 00:04:57.020 --> 00:04:59.180 align:start position:0% that it's correct we do a lot of math before<00:04:58.020> there's<00:04:58.500> a<00:04:58.530> single<00:04:58.860> line<00:04:59.039> of<00:04:59.070> code 00:04:59.180 --> 00:04:59.190 align:start position:0% before there's a single line of code 00:04:59.190 --> 00:05:01.430 align:start position:0% before there's a single line of code there's<00:04:59.910> ton<00:05:00.180> of<00:05:00.210> math<00:05:00.479> before<00:05:01.169> there's<00:05:01.320> a 00:05:01.430 --> 00:05:01.440 align:start position:0% there's ton of math before there's a 00:05:01.440 --> 00:05:04.040 align:start position:0% there's ton of math before there's a single<00:05:01.770> line<00:05:01.860> of<00:05:01.889> code<00:05:02.270> it's<00:05:03.270> a<00:05:03.419> deeply<00:05:03.690> deeply 00:05:04.040 --> 00:05:04.050 align:start position:0% single line of code it's a deeply deeply 00:05:04.050 --> 00:05:06.020 align:start position:0% single line of code it's a deeply deeply formalistic<00:05:04.800> process<00:05:05.280> and<00:05:05.490> it<00:05:05.550> takes<00:05:05.699> quite<00:05:05.910> a 00:05:06.020 --> 00:05:06.030 align:start position:0% formalistic process and it takes quite a 00:05:06.030 --> 00:05:07.790 align:start position:0% formalistic process and it takes quite a lot<00:05:06.180> of<00:05:06.270> time<00:05:06.419> to<00:05:07.169> produce<00:05:07.260> a<00:05:07.470> specification 00:05:07.790 --> 00:05:07.800 align:start position:0% lot of time to produce a specification 00:05:07.800 --> 00:05:09.020 align:start position:0% lot of time to produce a specification this<00:05:08.130> way<00:05:08.250> especially<00:05:08.370> if<00:05:08.639> you<00:05:08.699> mean<00:05:08.850> like<00:05:09.000> a 00:05:09.020 --> 00:05:09.030 align:start position:0% this way especially if you mean like a 00:05:09.030 --> 00:05:11.750 align:start position:0% this way especially if you mean like a complete<00:05:09.539> specification<00:05:09.889> but<00:05:10.889> it's 00:05:11.750 --> 00:05:11.760 align:start position:0% complete specification but it's 00:05:11.760 --> 00:05:13.490 align:start position:0% complete specification but it's guaranteed<00:05:12.300> to<00:05:12.419> be<00:05:12.479> correct<00:05:12.510> because<00:05:13.139> of<00:05:13.410> the 00:05:13.490 --> 00:05:13.500 align:start position:0% guaranteed to be correct because of the 00:05:13.500 --> 00:05:16.100 align:start position:0% guaranteed to be correct because of the process<00:05:14.010> by<00:05:14.130> which<00:05:14.160> it<00:05:14.310> was<00:05:14.460> derived<00:05:14.720> it's<00:05:15.720> you 00:05:16.100 --> 00:05:16.110 align:start position:0% process by which it was derived it's you 00:05:16.110 --> 00:05:17.900 align:start position:0% process by which it was derived it's you know<00:05:16.199> it's<00:05:16.590> correct<00:05:17.130> by<00:05:17.310> construction 00:05:17.900 --> 00:05:17.910 align:start position:0% know it's correct by construction 00:05:17.910 --> 00:05:20.510 align:start position:0% know it's correct by construction process<00:05:18.660> and<00:05:19.590> it's<00:05:20.010> also<00:05:20.100> given<00:05:20.340> to<00:05:20.400> you<00:05:20.460> to 00:05:20.510 --> 00:05:20.520 align:start position:0% process and it's also given to you to 00:05:20.520 --> 00:05:22.460 align:start position:0% process and it's also given to you to have<00:05:20.639> a<00:05:20.669> certain<00:05:20.850> aesthetic<00:05:21.240> appeal<00:05:22.050> that<00:05:22.320> is 00:05:22.460 --> 00:05:22.470 align:start position:0% have a certain aesthetic appeal that is 00:05:22.470 --> 00:05:24.890 align:start position:0% have a certain aesthetic appeal that is like<00:05:22.680> common<00:05:23.520> in<00:05:23.610> mathematics<00:05:24.180> where<00:05:24.720> you 00:05:24.890 --> 00:05:24.900 align:start position:0% like common in mathematics where you 00:05:24.900 --> 00:05:26.719 align:start position:0% like common in mathematics where you kind<00:05:25.139> of<00:05:25.169> only<00:05:25.500> make<00:05:25.650> the<00:05:25.800> minimum<00:05:26.250> most 00:05:26.719 --> 00:05:26.729 align:start position:0% kind of only make the minimum most 00:05:26.729 --> 00:05:28.700 align:start position:0% kind of only make the minimum most natural<00:05:27.180> choices<00:05:27.479> and<00:05:27.840> nothing<00:05:28.169> more<00:05:28.349> and 00:05:28.700 --> 00:05:28.710 align:start position:0% natural choices and nothing more and 00:05:28.710 --> 00:05:30.409 align:start position:0% natural choices and nothing more and everything<00:05:29.400> is<00:05:29.520> kind<00:05:29.639> of<00:05:29.760> natural<00:05:30.240> and 00:05:30.409 --> 00:05:30.419 align:start position:0% everything is kind of natural and 00:05:30.419 --> 00:05:32.210 align:start position:0% everything is kind of natural and elegant<00:05:30.900> and<00:05:31.020> everything<00:05:31.320> is<00:05:31.440> symmetric<00:05:31.979> and 00:05:32.210 --> 00:05:32.220 align:start position:0% elegant and everything is symmetric and 00:05:32.220 --> 00:05:35.450 align:start position:0% elegant and everything is symmetric and you<00:05:32.580> know<00:05:32.700> it<00:05:32.789> has<00:05:32.970> like<00:05:33.240> this<00:05:33.690> nice<00:05:34.020> math<00:05:34.460> math 00:05:35.450 --> 00:05:35.460 align:start position:0% you know it has like this nice math math 00:05:35.460 --> 00:05:37.070 align:start position:0% you know it has like this nice math math feeling<00:05:35.940> that<00:05:36.090> you<00:05:36.180> get<00:05:36.300> from<00:05:36.360> looking<00:05:36.690> at<00:05:36.900> any 00:05:37.070 --> 00:05:37.080 align:start position:0% feeling that you get from looking at any 00:05:37.080 --> 00:05:42.170 align:start position:0% feeling that you get from looking at any well<00:05:37.860> any<00:05:38.160> good<00:05:38.610> field<00:05:38.910> of<00:05:39.060> math<00:05:40.729> and<00:05:41.729> and<00:05:42.000> that 00:05:42.170 --> 00:05:42.180 align:start position:0% well any good field of math and and that 00:05:42.180 --> 00:05:43.400 align:start position:0% well any good field of math and and that is<00:05:42.330> like<00:05:42.479> one<00:05:42.599> of<00:05:42.660> the<00:05:42.720> big<00:05:42.870> appeal<00:05:43.110> to<00:05:43.260> think 00:05:43.400 --> 00:05:43.410 align:start position:0% is like one of the big appeal to think 00:05:43.410 --> 00:05:45.680 align:start position:0% is like one of the big appeal to think of<00:05:43.590> the<00:05:43.770> road<00:05:43.919> map<00:05:44.070> is<00:05:44.280> that<00:05:44.479> it's<00:05:45.479> the 00:05:45.680 --> 00:05:45.690 align:start position:0% of the road map is that it's the 00:05:45.690 --> 00:05:47.480 align:start position:0% of the road map is that it's the aesthetic<00:05:46.349> appeal<00:05:46.650> is<00:05:46.830> very<00:05:47.070> very<00:05:47.310> high 00:05:47.480 --> 00:05:47.490 align:start position:0% aesthetic appeal is very very high 00:05:47.490 --> 00:05:50.270 align:start position:0% aesthetic appeal is very very high because<00:05:47.789> everything<00:05:48.270> is<00:05:48.419> like<00:05:49.020> derived<00:05:50.010> from 00:05:50.270 --> 00:05:50.280 align:start position:0% because everything is like derived from 00:05:50.280 --> 00:05:51.560 align:start position:0% because everything is like derived from math<00:05:50.520> objects<00:05:50.970> in<00:05:51.030> a<00:05:51.060> way<00:05:51.180> that's<00:05:51.389> very 00:05:51.560 --> 00:05:51.570 align:start position:0% math objects in a way that's very 00:05:51.570 --> 00:05:53.990 align:start position:0% math objects in a way that's very careful<00:05:52.020> and<00:05:52.289> it<00:05:52.740> doesn't<00:05:53.070> involve<00:05:53.310> weird 00:05:53.990 --> 00:05:54.000 align:start position:0% careful and it doesn't involve weird 00:05:54.000 --> 00:05:56.089 align:start position:0% careful and it doesn't involve weird arbitrary<00:05:54.389> choices<00:05:54.810> except<00:05:55.800> for<00:05:55.919> to<00:05:55.979> the 00:05:56.089 --> 00:05:56.099 align:start position:0% arbitrary choices except for to the 00:05:56.099 --> 00:06:00.920 align:start position:0% arbitrary choices except for to the minimum<00:05:56.610> possible<00:05:59.330> so<00:06:00.330> that's<00:06:00.479> the<00:06:00.570> basic 00:06:00.920 --> 00:06:00.930 align:start position:0% minimum possible so that's the basic 00:06:00.930 --> 00:06:02.300 align:start position:0% minimum possible so that's the basic that's<00:06:01.169> the<00:06:01.260> basic<00:06:01.560> idea<00:06:01.620> like<00:06:01.919> what<00:06:02.099> it<00:06:02.220> is 00:06:02.300 --> 00:06:02.310 align:start position:0% that's the basic idea like what it is 00:06:02.310 --> 00:06:03.830 align:start position:0% that's the basic idea like what it is the<00:06:02.520> research<00:06:02.760> roadmap<00:06:03.150> that<00:06:03.330> doesn't<00:06:03.690> tell 00:06:03.830 --> 00:06:03.840 align:start position:0% the research roadmap that doesn't tell 00:06:03.840 --> 00:06:05.450 align:start position:0% the research roadmap that doesn't tell you<00:06:03.930> too<00:06:04.050> much<00:06:04.199> but<00:06:04.590> before<00:06:04.830> I<00:06:04.860> go<00:06:05.039> into<00:06:05.250> the 00:06:05.450 --> 00:06:05.460 align:start position:0% you too much but before I go into the 00:06:05.460 --> 00:06:06.800 align:start position:0% you too much but before I go into the items<00:06:06.090> of<00:06:06.180> the<00:06:06.240> road<00:06:06.360> map<00:06:06.479> we're<00:06:06.630> going<00:06:06.750> to 00:06:06.800 --> 00:06:06.810 align:start position:0% items of the road map we're going to 00:06:06.810 --> 00:06:09.260 align:start position:0% items of the road map we're going to talk<00:06:06.930> about<00:06:07.310> the<00:06:08.310> relationship<00:06:08.820> between<00:06:08.849> the 00:06:09.260 --> 00:06:09.270 align:start position:0% talk about the relationship between the 00:06:09.270 --> 00:06:10.850 align:start position:0% talk about the relationship between the CDC<00:06:09.630> Casper<00:06:09.960> roadmap<00:06:10.260> and<00:06:10.380> the<00:06:10.560> etherion 00:06:10.850 --> 00:06:10.860 align:start position:0% CDC Casper roadmap and the etherion 00:06:10.860 --> 00:06:13.250 align:start position:0% CDC Casper roadmap and the etherion roadmaps<00:06:11.419> so<00:06:12.419> in<00:06:12.570> some<00:06:12.720> ways<00:06:12.870> were<00:06:12.960> completely 00:06:13.250 --> 00:06:13.260 align:start position:0% roadmaps so in some ways were completely 00:06:13.260 --> 00:06:15.500 align:start position:0% roadmaps so in some ways were completely independent<00:06:13.770> of<00:06:13.919> the<00:06:14.250> theorem<00:06:14.580> road<00:06:14.699> maps<00:06:14.880> you 00:06:15.500 --> 00:06:15.510 align:start position:0% independent of the theorem road maps you 00:06:15.510 --> 00:06:16.670 align:start position:0% independent of the theorem road maps you know<00:06:15.599> we're<00:06:15.780> a<00:06:15.810> research<00:06:16.169> road<00:06:16.440> map<00:06:16.560> the 00:06:16.670 --> 00:06:16.680 align:start position:0% know we're a research road map the 00:06:16.680 --> 00:06:18.770 align:start position:0% know we're a research road map the theorem<00:06:16.949> the<00:06:17.039> road<00:06:17.520> maps<00:06:17.699> are<00:06:17.849> a<00:06:18.180> real<00:06:18.630> mess 00:06:18.770 --> 00:06:18.780 align:start position:0% theorem the road maps are a real mess 00:06:18.780 --> 00:06:21.760 align:start position:0% theorem the road maps are a real mess for<00:06:18.960> deployment<00:06:19.620> on<00:06:19.710> a<00:06:19.740> theory<00:06:19.949> maintenance 00:06:21.760 --> 00:06:21.770 align:start position:0% for deployment on a theory maintenance 00:06:21.770 --> 00:06:24.710 align:start position:0% for deployment on a theory maintenance but<00:06:22.770> you<00:06:23.099> know<00:06:23.190> some<00:06:23.520> ways<00:06:23.729> you<00:06:23.940> know<00:06:23.970> you<00:06:24.630> know 00:06:24.710 --> 00:06:24.720 align:start position:0% but you know some ways you know you know 00:06:24.720 --> 00:06:26.540 align:start position:0% but you know some ways you know you know CBC<00:06:25.139> Casper<00:06:25.380> Research<00:06:25.620> has<00:06:25.800> you<00:06:26.280> know<00:06:26.370> made 00:06:26.540 --> 00:06:26.550 align:start position:0% CBC Casper Research has you know made 00:06:26.550 --> 00:06:34.580 align:start position:0% CBC Casper Research has you know made its<00:06:26.729> way<00:06:26.880> into<00:06:26.910> aetherium<00:06:27.419> 2.0 00:06:34.580 --> 00:06:34.590 align:start position:0% 00:06:34.590 --> 00:06:38.950 align:start position:0% and<00:06:35.600> maybe<00:06:36.600> it'll<00:06:37.080> make<00:06:37.230> its<00:06:37.350> way<00:06:37.440> into<00:06:37.590> 33.0 00:06:38.950 --> 00:06:38.960 align:start position:0% and maybe it'll make its way into 33.0 00:06:38.960 --> 00:06:41.240 align:start position:0% and maybe it'll make its way into 33.0 question<00:06:39.960> mark<00:06:40.170> because<00:06:40.650> it's<00:06:40.980> not<00:06:41.100> really 00:06:41.240 --> 00:06:41.250 align:start position:0% question mark because it's not really 00:06:41.250 --> 00:06:45.620 align:start position:0% question mark because it's not really clear<00:06:41.340> yet<00:06:41.610> what<00:06:41.730> if<00:06:41.970> they're<00:06:42.120> in<00:06:42.150> 3.0<00:06:42.630> is<00:06:44.630> one 00:06:45.620 --> 00:06:45.630 align:start position:0% clear yet what if they're in 3.0 is one 00:06:45.630 --> 00:06:46.850 align:start position:0% clear yet what if they're in 3.0 is one of<00:06:45.780> the<00:06:45.870> things<00:06:46.080> that<00:06:46.290> is<00:06:46.380> probably<00:06:46.650> the<00:06:46.710> most 00:06:46.850 --> 00:06:46.860 align:start position:0% of the things that is probably the most 00:06:46.860 --> 00:06:48.740 align:start position:0% of the things that is probably the most painless<00:06:47.280> that<00:06:47.850> came<00:06:48.060> out<00:06:48.180> Susie<00:06:48.510> Casper 00:06:48.740 --> 00:06:48.750 align:start position:0% painless that came out Susie Casper 00:06:48.750 --> 00:06:50.120 align:start position:0% painless that came out Susie Casper research<00:06:49.050> is<00:06:49.200> the<00:06:49.410> latest<00:06:49.740> message<00:06:49.890> driven 00:06:50.120 --> 00:06:50.130 align:start position:0% research is the latest message driven 00:06:50.130 --> 00:06:52.400 align:start position:0% research is the latest message driven ghost<00:06:50.970> poor<00:06:51.450> choice<00:06:51.660> rule<00:06:51.870> that<00:06:52.080> is<00:06:52.200> featured 00:06:52.400 --> 00:06:52.410 align:start position:0% ghost poor choice rule that is featured 00:06:52.410 --> 00:06:54.590 align:start position:0% ghost poor choice rule that is featured in<00:06:52.650> the<00:06:52.860> you<00:06:53.070> can<00:06:53.190> chain 00:06:54.590 --> 00:06:54.600 align:start position:0% in the you can chain 00:06:54.600 --> 00:06:57.020 align:start position:0% in the you can chain another<00:06:55.500> thing<00:06:55.740> is<00:06:55.980> south<00:06:56.310> canara<00:06:56.460> puzzle<00:06:56.910> to 00:06:57.020 --> 00:06:57.030 align:start position:0% another thing is south canara puzzle to 00:06:57.030 --> 00:07:00.290 align:start position:0% another thing is south canara puzzle to add<00:06:57.330> the<00:06:57.930> CBC<00:06:58.350> Casper<00:06:58.650> finality<00:06:59.150> mechanism<00:07:00.150> to 00:07:00.290 --> 00:07:00.300 align:start position:0% add the CBC Casper finality mechanism to 00:07:00.300 --> 00:07:05.060 align:start position:0% add the CBC Casper finality mechanism to the<00:07:00.330> beacon<00:07:00.690> chain<00:07:01.910> so<00:07:02.910> somehow<00:07:03.530> the<00:07:04.530> CBC<00:07:04.920> cast 00:07:05.060 --> 00:07:05.070 align:start position:0% the beacon chain so somehow the CBC cast 00:07:05.070 --> 00:07:06.590 align:start position:0% the beacon chain so somehow the CBC cast for<00:07:05.190> research<00:07:05.430> flow<00:07:05.880> if<00:07:06.120> when<00:07:06.270> the<00:07:06.360> research 00:07:06.590 --> 00:07:06.600 align:start position:0% for research flow if when the research 00:07:06.600 --> 00:07:09.320 align:start position:0% for research flow if when the research roadmap<00:07:06.900> closed<00:07:07.170> into<00:07:07.590> 30<00:07:07.950> 2.0<00:07:08.490> research<00:07:09.060> at 00:07:09.320 --> 00:07:09.330 align:start position:0% roadmap closed into 30 2.0 research at 00:07:09.330 --> 00:07:13.760 align:start position:0% roadmap closed into 30 2.0 research at least<00:07:09.390> a<00:07:09.600> little<00:07:09.690> bit<00:07:11.000> in<00:07:12.000> some<00:07:12.330> ways<00:07:12.680> you<00:07:13.680> know 00:07:13.760 --> 00:07:13.770 align:start position:0% least a little bit in some ways you know 00:07:13.770 --> 00:07:14.780 align:start position:0% least a little bit in some ways you know so<00:07:13.860> in<00:07:13.950> some<00:07:14.070> ways<00:07:14.220> actually<00:07:14.310> the<00:07:14.520> theorem 00:07:14.780 --> 00:07:14.790 align:start position:0% so in some ways actually the theorem 00:07:14.790 --> 00:07:15.890 align:start position:0% so in some ways actually the theorem roadmaps<00:07:15.060> are<00:07:15.120> not<00:07:15.270> really<00:07:15.450> independent<00:07:15.600> of 00:07:15.890 --> 00:07:15.900 align:start position:0% roadmaps are not really independent of 00:07:15.900 --> 00:07:18.230 align:start position:0% roadmaps are not really independent of the<00:07:16.140> CBC<00:07:16.590> Casper<00:07:16.920> roadmap<00:07:17.310> at<00:07:17.700> least<00:07:17.940> as<00:07:18.090> long 00:07:18.230 --> 00:07:18.240 align:start position:0% the CBC Casper roadmap at least as long 00:07:18.240 --> 00:07:20.060 align:start position:0% the CBC Casper roadmap at least as long as<00:07:18.390> we<00:07:18.510> continue<00:07:18.840> to<00:07:18.930> produce<00:07:19.050> stuff<00:07:19.440> that 00:07:20.060 --> 00:07:20.070 align:start position:0% as we continue to produce stuff that 00:07:20.070 --> 00:07:23.090 align:start position:0% as we continue to produce stuff that they<00:07:20.220> want<00:07:20.370> to<00:07:20.730> implement<00:07:21.180> and<00:07:21.980> you<00:07:22.980> know 00:07:23.090 --> 00:07:23.100 align:start position:0% they want to implement and you know 00:07:23.100 --> 00:07:24.860 align:start position:0% they want to implement and you know that's<00:07:24.000> our<00:07:24.120> goal<00:07:24.270> we<00:07:24.570> want<00:07:24.750> to<00:07:24.780> build 00:07:24.860 --> 00:07:24.870 align:start position:0% that's our goal we want to build 00:07:24.870 --> 00:07:26.180 align:start position:0% that's our goal we want to build protocols<00:07:25.350> people<00:07:25.590> really<00:07:26.010> want<00:07:26.160> to 00:07:26.180 --> 00:07:26.190 align:start position:0% protocols people really want to 00:07:26.190 --> 00:07:27.650 align:start position:0% protocols people really want to implement<00:07:26.430> because<00:07:26.910> of<00:07:27.060> their<00:07:27.240> simplicity 00:07:27.650 --> 00:07:27.660 align:start position:0% implement because of their simplicity 00:07:27.660 --> 00:07:32.120 align:start position:0% implement because of their simplicity elegance<00:07:28.140> utility<00:07:28.920> properties<00:07:29.400> etc<00:07:31.010> so<00:07:32.010> we 00:07:32.120 --> 00:07:32.130 align:start position:0% elegance utility properties etc so we 00:07:32.130 --> 00:07:34.820 align:start position:0% elegance utility properties etc so we have<00:07:32.810> but<00:07:33.810> the<00:07:33.930> theorem<00:07:34.170> roadmaps<00:07:34.440> are<00:07:34.530> not<00:07:34.680> in 00:07:34.820 --> 00:07:34.830 align:start position:0% have but the theorem roadmaps are not in 00:07:34.830 --> 00:07:36.290 align:start position:0% have but the theorem roadmaps are not in any<00:07:34.950> way<00:07:35.070> blocked<00:07:35.310> on<00:07:35.520> the<00:07:35.670> CBC<00:07:35.940> Casper 00:07:36.290 --> 00:07:36.300 align:start position:0% any way blocked on the CBC Casper 00:07:36.300 --> 00:07:38.540 align:start position:0% any way blocked on the CBC Casper roadmaps<00:07:36.660> you<00:07:37.260> know<00:07:37.350> there's<00:07:37.530> there's<00:07:38.190> no<00:07:38.310> no 00:07:38.540 --> 00:07:38.550 align:start position:0% roadmaps you know there's there's no no 00:07:38.550 --> 00:07:40.040 align:start position:0% roadmaps you know there's there's no no one's<00:07:38.760> waiting<00:07:38.970> for<00:07:39.450> us<00:07:39.510> to<00:07:39.660> finish<00:07:39.750> our 00:07:40.040 --> 00:07:40.050 align:start position:0% one's waiting for us to finish our 00:07:40.050 --> 00:07:42.640 align:start position:0% one's waiting for us to finish our research<00:07:40.350> before<00:07:40.980> implementing<00:07:41.940> protocols 00:07:42.640 --> 00:07:42.650 align:start position:0% research before implementing protocols 00:07:42.650 --> 00:07:45.290 align:start position:0% research before implementing protocols so<00:07:43.650> they're<00:07:43.830> they're<00:07:44.100> really<00:07:44.370> they're<00:07:44.910> really 00:07:45.290 --> 00:07:45.300 align:start position:0% so they're they're really they're really 00:07:45.300 --> 00:07:48.400 align:start position:0% so they're they're really they're really are<00:07:45.450> in<00:07:45.570> some<00:07:45.600> ways<00:07:45.840> very<00:07:45.870> independent<00:07:46.470> of<00:07:46.560> us 00:07:48.400 --> 00:07:48.410 align:start position:0% are in some ways very independent of us 00:07:48.410 --> 00:07:50.360 align:start position:0% are in some ways very independent of us great<00:07:49.410> so<00:07:49.680> now<00:07:49.800> I'm<00:07:49.920> going<00:07:50.010> to<00:07:50.070> talk<00:07:50.310> about 00:07:50.360 --> 00:07:50.370 align:start position:0% great so now I'm going to talk about 00:07:50.370 --> 00:07:52.580 align:start position:0% great so now I'm going to talk about Phoebe<00:07:50.820> see<00:07:51.000> Casper<00:07:51.210> the<00:07:51.750> CBC<00:07:52.050> Casper<00:07:52.320> roadmap 00:07:52.580 --> 00:07:52.590 align:start position:0% Phoebe see Casper the CBC Casper roadmap 00:07:52.590 --> 00:07:54.080 align:start position:0% Phoebe see Casper the CBC Casper roadmap in<00:07:52.710> terms<00:07:52.890> of<00:07:53.040> you<00:07:53.430> know<00:07:53.460> what<00:07:53.670> have<00:07:53.790> actually 00:07:54.080 --> 00:07:54.090 align:start position:0% in terms of you know what have actually 00:07:54.090 --> 00:07:55.340 align:start position:0% in terms of you know what have actually we<00:07:54.180> done<00:07:54.330> so<00:07:55.080> far 00:07:55.340 --> 00:07:55.350 align:start position:0% we done so far 00:07:55.350 --> 00:07:57.050 align:start position:0% we done so far and<00:07:55.560> you<00:07:56.160> know<00:07:56.250> what<00:07:56.370> are<00:07:56.430> we<00:07:56.490> gonna<00:07:56.610> do<00:07:56.820> in<00:07:56.970> the 00:07:57.050 --> 00:07:57.060 align:start position:0% and you know what are we gonna do in the 00:07:57.060 --> 00:07:59.450 align:start position:0% and you know what are we gonna do in the future<00:07:57.500> before<00:07:58.500> I<00:07:58.680> start<00:07:59.040> I'm<00:07:59.190> just<00:07:59.220> gonna 00:07:59.450 --> 00:07:59.460 align:start position:0% future before I start I'm just gonna 00:07:59.460 --> 00:08:03.230 align:start position:0% future before I start I'm just gonna mention<00:07:59.610> that<00:08:00.020> the<00:08:01.020> CBC<00:08:01.440> the<00:08:01.920> Casper<00:08:02.910> research 00:08:03.230 --> 00:08:03.240 align:start position:0% mention that the CBC the Casper research 00:08:03.240 --> 00:08:05.630 align:start position:0% mention that the CBC the Casper research started<00:08:03.660> before<00:08:03.810> the<00:08:04.350> split<00:08:04.920> between<00:08:05.100> CBC 00:08:05.630 --> 00:08:05.640 align:start position:0% started before the split between CBC 00:08:05.640 --> 00:08:08.570 align:start position:0% started before the split between CBC Casper<00:08:06.000> and<00:08:06.240> Casper<00:08:06.570> FFG<00:08:07.130> Pass<00:08:08.130> Pro<00:08:08.310> research 00:08:08.570 --> 00:08:08.580 align:start position:0% Casper and Casper FFG Pass Pro research 00:08:08.580 --> 00:08:10.400 align:start position:0% Casper and Casper FFG Pass Pro research started<00:08:08.940> off<00:08:09.030> as<00:08:09.120> pre<00:08:09.270> mistake<00:08:09.570> research<00:08:09.900> into 00:08:10.400 --> 00:08:10.410 align:start position:0% started off as pre mistake research into 00:08:10.410 --> 00:08:12.740 align:start position:0% started off as pre mistake research into you<00:08:11.070> know<00:08:11.160> economically<00:08:11.820> secure<00:08:12.240> for<00:08:12.450> mistake 00:08:12.740 --> 00:08:12.750 align:start position:0% you know economically secure for mistake 00:08:12.750 --> 00:08:14.510 align:start position:0% you know economically secure for mistake where<00:08:12.960> we<00:08:13.020> can<00:08:13.140> have<00:08:13.260> like<00:08:13.380> a<00:08:13.500> equilibrium<00:08:14.190> to 00:08:14.510 --> 00:08:14.520 align:start position:0% where we can have like a equilibrium to 00:08:14.520 --> 00:08:16.040 align:start position:0% where we can have like a equilibrium to follow<00:08:14.730> the<00:08:14.850> protocol<00:08:15.060> that's<00:08:15.450> really<00:08:15.690> robust 00:08:16.040 --> 00:08:16.050 align:start position:0% follow the protocol that's really robust 00:08:16.050 --> 00:08:17.810 align:start position:0% follow the protocol that's really robust where<00:08:16.590> we<00:08:16.710> have<00:08:16.830> where<00:08:16.980> we<00:08:17.100> use<00:08:17.430> security 00:08:17.810 --> 00:08:17.820 align:start position:0% where we have where we use security 00:08:17.820 --> 00:08:20.930 align:start position:0% where we have where we use security deposit<00:08:18.420> in<00:08:18.570> order<00:08:18.780> to<00:08:18.900> make<00:08:19.850> equilibrium<00:08:20.850> as 00:08:20.930 --> 00:08:20.940 align:start position:0% deposit in order to make equilibrium as 00:08:20.940 --> 00:08:22.190 align:start position:0% deposit in order to make equilibrium as robust<00:08:21.240> as<00:08:21.390> possible<00:08:21.810> so<00:08:21.930> we<00:08:21.990> can<00:08:22.080> have 00:08:22.190 --> 00:08:22.200 align:start position:0% robust as possible so we can have 00:08:22.200 --> 00:08:25.730 align:start position:0% robust as possible so we can have penalties<00:08:22.680> to<00:08:24.200> make<00:08:25.200> it<00:08:25.350> to<00:08:25.470> that<00:08:25.590> that 00:08:25.730 --> 00:08:25.740 align:start position:0% penalties to make it to that that 00:08:25.740 --> 00:08:26.870 align:start position:0% penalties to make it to that that equilibrium<00:08:26.160> is<00:08:26.220> not<00:08:26.250> just<00:08:26.460> an<00:08:26.520> epsilon 00:08:26.870 --> 00:08:26.880 align:start position:0% equilibrium is not just an epsilon 00:08:26.880 --> 00:08:29.900 align:start position:0% equilibrium is not just an epsilon equilibrium<00:08:27.450> but<00:08:28.050> like<00:08:28.170> a<00:08:28.200> a<00:08:28.620> very<00:08:29.520> robust 00:08:29.900 --> 00:08:29.910 align:start position:0% equilibrium but like a a very robust 00:08:29.910 --> 00:08:31.760 align:start position:0% equilibrium but like a a very robust equilibrium<00:08:30.420> and<00:08:30.690> then<00:08:31.260> basically<00:08:31.620> what 00:08:31.760 --> 00:08:31.770 align:start position:0% equilibrium and then basically what 00:08:31.770 --> 00:08:34.520 align:start position:0% equilibrium and then basically what happens<00:08:32.070> is<00:08:32.660> at<00:08:33.660> some<00:08:33.840> point<00:08:33.870> after<00:08:34.200> you<00:08:34.410> do 00:08:34.520 --> 00:08:34.530 align:start position:0% happens is at some point after you do 00:08:34.530 --> 00:08:35.840 align:start position:0% happens is at some point after you do the<00:08:34.650> incentivization<00:08:35.220> research<00:08:35.520> you<00:08:35.610> realize 00:08:35.840 --> 00:08:35.850 align:start position:0% the incentivization research you realize 00:08:35.850 --> 00:08:37.010 align:start position:0% the incentivization research you realize you<00:08:35.940> have<00:08:36.030> to<00:08:36.060> have<00:08:36.210> some<00:08:36.330> specific<00:08:36.570> thing 00:08:37.010 --> 00:08:37.020 align:start position:0% you have to have some specific thing 00:08:37.020 --> 00:08:38.870 align:start position:0% you have to have some specific thing you're<00:08:37.170> telling<00:08:37.470> them<00:08:37.590> to<00:08:38.220> that<00:08:38.610> you<00:08:38.670> want<00:08:38.820> to 00:08:38.870 --> 00:08:38.880 align:start position:0% you're telling them to that you want to 00:08:38.880 --> 00:08:40.640 align:start position:0% you're telling them to that you want to incentivize<00:08:39.240> like<00:08:39.480> a<00:08:39.540> specific<00:08:39.750> protocol<00:08:40.410> and 00:08:40.640 --> 00:08:40.650 align:start position:0% incentivize like a specific protocol and 00:08:40.650 --> 00:08:43.370 align:start position:0% incentivize like a specific protocol and so<00:08:41.430> the<00:08:42.090> CBC<00:08:42.450> Casper<00:08:42.720> roadmap<00:08:43.080> really 00:08:43.370 --> 00:08:43.380 align:start position:0% so the CBC Casper roadmap really 00:08:43.380 --> 00:08:45.980 align:start position:0% so the CBC Casper roadmap really represents<00:08:43.890> the<00:08:44.040> distributed<00:08:44.940> systems 00:08:45.980 --> 00:08:45.990 align:start position:0% represents the distributed systems 00:08:45.990 --> 00:08:49.700 align:start position:0% represents the distributed systems that<00:08:47.330> is<00:08:48.330> going<00:08:48.690> to<00:08:48.750> be<00:08:48.840> incentivized<00:08:49.380> Dhruva 00:08:49.700 --> 00:08:49.710 align:start position:0% that is going to be incentivized Dhruva 00:08:49.710 --> 00:08:51.350 align:start position:0% that is going to be incentivized Dhruva state<00:08:49.920> it<00:08:50.250> doesn't<00:08:50.550> represent<00:08:50.640> prove<00:08:51.060> a<00:08:51.150> stake 00:08:51.350 --> 00:08:51.360 align:start position:0% state it doesn't represent prove a stake 00:08:51.360 --> 00:08:53.210 align:start position:0% state it doesn't represent prove a stake research<00:08:51.720> it<00:08:51.930> just<00:08:52.080> represents<00:08:52.230> consensus 00:08:53.210 --> 00:08:53.220 align:start position:0% research it just represents consensus 00:08:53.220 --> 00:08:54.620 align:start position:0% research it just represents consensus protocol<00:08:53.550> research<00:08:53.910> like<00:08:54.120> distributed 00:08:54.620 --> 00:08:54.630 align:start position:0% protocol research like distributed 00:08:54.630 --> 00:08:56.840 align:start position:0% protocol research like distributed systems<00:08:54.930> research<00:08:55.260> although<00:08:55.680> absolutely<00:08:56.460> the 00:08:56.840 --> 00:08:56.850 align:start position:0% systems research although absolutely the 00:08:56.850 --> 00:08:58.880 align:start position:0% systems research although absolutely the product<00:08:57.180> requirements<00:08:57.750> in<00:08:57.900> cbc<00:08:58.410> Casper<00:08:58.710> are 00:08:58.880 --> 00:08:58.890 align:start position:0% product requirements in cbc Casper are 00:08:58.890 --> 00:09:00.590 align:start position:0% product requirements in cbc Casper are driven<00:08:59.280> entirely<00:08:59.700> and<00:08:59.970> determined<00:09:00.390> entirely 00:09:00.590 --> 00:09:00.600 align:start position:0% driven entirely and determined entirely 00:09:00.600 --> 00:09:02.210 align:start position:0% driven entirely and determined entirely by<00:09:00.750> the<00:09:00.900> approve<00:09:01.380> the<00:09:01.470> state<00:09:01.620> research<00:09:01.950> became 00:09:02.210 --> 00:09:02.220 align:start position:0% by the approve the state research became 00:09:02.220 --> 00:09:04.280 align:start position:0% by the approve the state research became before<00:09:02.520> so<00:09:03.180> approve<00:09:03.480> snake<00:09:03.660> research<00:09:04.050> and 00:09:04.280 --> 00:09:04.290 align:start position:0% before so approve snake research and 00:09:04.290 --> 00:09:05.630 align:start position:0% before so approve snake research and then<00:09:04.740> distribute<00:09:05.100> the<00:09:05.160> system<00:09:05.400> research 00:09:05.630 --> 00:09:05.640 align:start position:0% then distribute the system research 00:09:05.640 --> 00:09:06.800 align:start position:0% then distribute the system research rabbit<00:09:05.910> Alec<00:09:06.120> and<00:09:06.210> I<00:09:06.270> split<00:09:06.540> off<00:09:06.660> into 00:09:06.800 --> 00:09:06.810 align:start position:0% rabbit Alec and I split off into 00:09:06.810 --> 00:09:09.530 align:start position:0% rabbit Alec and I split off into different<00:09:07.170> protocols<00:09:07.950> the<00:09:08.640> caste<00:09:09.060> graph<00:09:09.270> of<00:09:09.390> G 00:09:09.530 --> 00:09:09.540 align:start position:0% different protocols the caste graph of G 00:09:09.540 --> 00:09:12.710 align:start position:0% different protocols the caste graph of G versus<00:09:09.840> Casper<00:09:10.200> CBC<00:09:10.760> and<00:09:11.760> so<00:09:12.420> this<00:09:12.570> is<00:09:12.630> gonna 00:09:12.710 --> 00:09:12.720 align:start position:0% versus Casper CBC and so this is gonna 00:09:12.720 --> 00:09:14.810 align:start position:0% versus Casper CBC and so this is gonna be<00:09:12.810> about<00:09:13.110> distributed<00:09:13.680> systems<00:09:14.070> this<00:09:14.640> is<00:09:14.760> a 00:09:14.810 --> 00:09:14.820 align:start position:0% be about distributed systems this is a 00:09:14.820 --> 00:09:16.580 align:start position:0% be about distributed systems this is a distributed<00:09:15.690> systems<00:09:15.990> roadmap<00:09:16.350> you're<00:09:16.470> not 00:09:16.580 --> 00:09:16.590 align:start position:0% distributed systems roadmap you're not 00:09:16.590 --> 00:09:17.510 align:start position:0% distributed systems roadmap you're not going<00:09:16.710> to<00:09:16.770> see<00:09:16.830> anything<00:09:17.040> about<00:09:17.370> we're 00:09:17.510 --> 00:09:17.520 align:start position:0% going to see anything about we're 00:09:17.520 --> 00:09:19.040 align:start position:0% going to see anything about we're mistaken<00:09:17.850> incentives<00:09:18.180> here<00:09:18.330> not<00:09:18.840> because 00:09:19.040 --> 00:09:19.050 align:start position:0% mistaken incentives here not because 00:09:19.050 --> 00:09:21.440 align:start position:0% mistaken incentives here not because it's<00:09:19.200> not<00:09:19.320> in<00:09:19.560> like<00:09:19.770> some<00:09:20.490> other<00:09:20.760> roadmap 00:09:21.440 --> 00:09:21.450 align:start position:0% it's not in like some other roadmap 00:09:21.450 --> 00:09:23.230 align:start position:0% it's not in like some other roadmap it's<00:09:21.930> just<00:09:22.050> that<00:09:22.140> CBC<00:09:22.560> Casper<00:09:22.950> is 00:09:23.230 --> 00:09:23.240 align:start position:0% it's just that CBC Casper is 00:09:23.240 --> 00:09:25.070 align:start position:0% it's just that CBC Casper is specifically<00:09:24.240> a<00:09:24.360> distributed<00:09:24.780> systems 00:09:25.070 --> 00:09:25.080 align:start position:0% specifically a distributed systems 00:09:25.080 --> 00:09:28.190 align:start position:0% specifically a distributed systems program<00:09:26.390> so<00:09:27.390> basically<00:09:27.600> what<00:09:27.840> is<00:09:27.960> the<00:09:27.990> road 00:09:28.190 --> 00:09:28.200 align:start position:0% program so basically what is the road 00:09:28.200 --> 00:09:29.720 align:start position:0% program so basically what is the road map<00:09:28.350> well<00:09:28.500> any<00:09:28.650> road<00:09:28.890> map<00:09:29.070> is<00:09:29.220> basically 00:09:29.720 --> 00:09:29.730 align:start position:0% map well any road map is basically 00:09:29.730 --> 00:09:31.040 align:start position:0% map well any road map is basically everything<00:09:30.360> you've<00:09:30.480> done<00:09:30.630> already<00:09:30.930> and 00:09:31.040 --> 00:09:31.050 align:start position:0% everything you've done already and 00:09:31.050 --> 00:09:32.210 align:start position:0% everything you've done already and everything<00:09:31.380> you're<00:09:31.470> planning<00:09:31.770> to<00:09:31.890> do<00:09:32.010> in<00:09:32.160> the 00:09:32.210 --> 00:09:32.220 align:start position:0% everything you're planning to do in the 00:09:32.220 --> 00:09:33.490 align:start position:0% everything you're planning to do in the future 00:09:33.490 --> 00:09:33.500 align:start position:0% future 00:09:33.500 --> 00:09:38.390 align:start position:0% future it's<00:09:34.500> kind<00:09:34.680> of<00:09:34.710> like<00:09:34.860> a<00:09:36.500> map<00:09:37.500> though<00:09:37.860> like<00:09:38.130> over 00:09:38.390 --> 00:09:38.400 align:start position:0% it's kind of like a map though like over 00:09:38.400 --> 00:09:39.560 align:start position:0% it's kind of like a map though like over time<00:09:38.640> you<00:09:39.000> know<00:09:39.060> what<00:09:39.240> you're<00:09:39.330> supposed<00:09:39.540> to 00:09:39.560 --> 00:09:39.570 align:start position:0% time you know what you're supposed to 00:09:39.570 --> 00:09:43.370 align:start position:0% time you know what you're supposed to accomplish<00:09:39.990> to<00:09:40.140> get<00:09:40.290> to<00:09:40.410> your<00:09:40.560> goals<00:09:41.180> and<00:09:42.380> so 00:09:43.370 --> 00:09:43.380 align:start position:0% accomplish to get to your goals and so 00:09:43.380 --> 00:09:44.510 align:start position:0% accomplish to get to your goals and so I'm<00:09:43.470> gonna<00:09:43.590> talk<00:09:43.770> about<00:09:43.920> all<00:09:44.100> the<00:09:44.160> past<00:09:44.340> work 00:09:44.510 --> 00:09:44.520 align:start position:0% I'm gonna talk about all the past work 00:09:44.520 --> 00:09:47.210 align:start position:0% I'm gonna talk about all the past work that<00:09:44.700> we've<00:09:44.790> done<00:09:45.650> this<00:09:46.650> is<00:09:46.800> this<00:09:46.890> is<00:09:47.040> going<00:09:47.130> to 00:09:47.210 --> 00:09:47.220 align:start position:0% that we've done this is this is going to 00:09:47.220 --> 00:09:49.370 align:start position:0% that we've done this is this is going to be<00:09:47.340> the<00:09:47.850> milestones<00:09:48.720> like<00:09:48.930> important 00:09:49.370 --> 00:09:49.380 align:start position:0% be the milestones like important 00:09:49.380 --> 00:09:50.840 align:start position:0% be the milestones like important milestones<00:09:49.740> there's<00:09:50.010> lots<00:09:50.220> of<00:09:50.340> struggling 00:09:50.840 --> 00:09:50.850 align:start position:0% milestones there's lots of struggling 00:09:50.850 --> 00:09:52.610 align:start position:0% milestones there's lots of struggling behind<00:09:51.180> the<00:09:51.270> scenes<00:09:51.510> that<00:09:51.750> isn't<00:09:52.110> listed<00:09:52.200> here 00:09:52.610 --> 00:09:52.620 align:start position:0% behind the scenes that isn't listed here 00:09:52.620 --> 00:09:55.430 align:start position:0% behind the scenes that isn't listed here lots<00:09:53.160> of<00:09:53.280> just<00:09:54.060> a<00:09:54.150> ton<00:09:54.390> of<00:09:54.420> work<00:09:54.750> that<00:09:54.780> isn't<00:09:55.350> in 00:09:55.430 --> 00:09:55.440 align:start position:0% lots of just a ton of work that isn't in 00:09:55.440 --> 00:09:57.950 align:start position:0% lots of just a ton of work that isn't in here<00:09:55.650> because<00:09:56.160> you<00:09:56.940> know<00:09:57.030> just<00:09:57.060> not<00:09:57.660> a<00:09:57.690> little 00:09:57.950 --> 00:09:57.960 align:start position:0% here because you know just not a little 00:09:57.960 --> 00:10:00.470 align:start position:0% here because you know just not a little work<00:09:58.080> ends<00:09:58.590> up<00:09:58.680> leading<00:09:59.250> to<00:09:59.400> a<00:09:59.760> milestone<00:10:00.030> that 00:10:00.470 --> 00:10:00.480 align:start position:0% work ends up leading to a milestone that 00:10:00.480 --> 00:10:03.080 align:start position:0% work ends up leading to a milestone that is<00:10:00.570> like<00:10:00.720> especially<00:10:01.200> in<00:10:01.500> research<00:10:01.940> that<00:10:02.940> is 00:10:03.080 --> 00:10:03.090 align:start position:0% is like especially in research that is 00:10:03.090 --> 00:10:04.640 align:start position:0% is like especially in research that is like<00:10:03.330> something<00:10:04.050> that<00:10:04.230> you<00:10:04.320> can<00:10:04.470> present 00:10:04.640 --> 00:10:04.650 align:start position:0% like something that you can present 00:10:04.650 --> 00:10:08.180 align:start position:0% like something that you can present right<00:10:05.070> so<00:10:05.850> the<00:10:06.390> first<00:10:06.930> the<00:10:07.320> first<00:10:07.620> thing<00:10:08.160> that 00:10:08.180 --> 00:10:08.190 align:start position:0% right so the first the first thing that 00:10:08.190 --> 00:10:09.860 align:start position:0% right so the first the first thing that really<00:10:08.370> kicked<00:10:08.730> off<00:10:08.850> CDC<00:10:09.270> Casper<00:10:09.570> research 00:10:09.860 --> 00:10:09.870 align:start position:0% really kicked off CDC Casper research 00:10:09.870 --> 00:10:13.910 align:start position:0% really kicked off CDC Casper research was<00:10:10.680> well<00:10:11.340> beyond<00:10:12.300> just<00:10:12.420> me<00:10:12.840> hearing<00:10:13.650> about 00:10:13.910 --> 00:10:13.920 align:start position:0% was well beyond just me hearing about 00:10:13.920 --> 00:10:17.870 align:start position:0% was well beyond just me hearing about and<00:10:14.070> I'm<00:10:14.130> learning<00:10:14.250> about<00:10:15.170> CB<00:10:16.170> CBC<00:10:16.880> protocol 00:10:17.870 --> 00:10:17.880 align:start position:0% and I'm learning about CB CBC protocol 00:10:17.880 --> 00:10:19.880 align:start position:0% and I'm learning about CB CBC protocol design<00:10:18.120> is<00:10:18.300> the<00:10:18.780> CBC<00:10:19.020> Casper<00:10:19.380> message<00:10:19.650> type 00:10:19.880 --> 00:10:19.890 align:start position:0% design is the CBC Casper message type 00:10:19.890 --> 00:10:21.770 align:start position:0% design is the CBC Casper message type this<00:10:20.610> is<00:10:20.700> something<00:10:21.000> Greg<00:10:21.210> Meredith<00:10:21.570> and<00:10:21.720> I 00:10:21.770 --> 00:10:21.780 align:start position:0% this is something Greg Meredith and I 00:10:21.780 --> 00:10:25.190 align:start position:0% this is something Greg Meredith and I came<00:10:22.080> up<00:10:22.230> with<00:10:22.260> in<00:10:22.680> August<00:10:23.160> 2016<00:10:24.090> when<00:10:24.990> we<00:10:25.110> were 00:10:25.190 --> 00:10:25.200 align:start position:0% came up with in August 2016 when we were 00:10:25.200 --> 00:10:27.170 align:start position:0% came up with in August 2016 when we were trying<00:10:25.410> to<00:10:25.620> come<00:10:25.980> up<00:10:26.130> with<00:10:26.280> you<00:10:26.850> know<00:10:26.880> just<00:10:27.060> the 00:10:27.170 --> 00:10:27.180 align:start position:0% trying to come up with you know just the 00:10:27.180 --> 00:10:28.640 align:start position:0% trying to come up with you know just the preliminary<00:10:27.360> infrastructure<00:10:28.140> so<00:10:28.470> that<00:10:28.590> we 00:10:28.640 --> 00:10:28.650 align:start position:0% preliminary infrastructure so that we 00:10:28.650 --> 00:10:31.750 align:start position:0% preliminary infrastructure so that we can<00:10:28.770> state<00:10:29.130> a<00:10:29.400> CBC<00:10:29.940> consensus<00:10:30.900> problem<00:10:31.260> in 00:10:31.750 --> 00:10:31.760 align:start position:0% can state a CBC consensus problem in 00:10:31.760 --> 00:10:37.310 align:start position:0% can state a CBC consensus problem in August<00:10:32.760> just<00:10:33.510> month<00:10:34.260> later<00:10:35.690> came<00:10:36.690> up<00:10:36.840> with<00:10:37.080> for 00:10:37.310 --> 00:10:37.320 align:start position:0% August just month later came up with for 00:10:37.320 --> 00:10:40.250 align:start position:0% August just month later came up with for the<00:10:37.350> first<00:10:37.590> time<00:10:37.830> this<00:10:38.430> safe<00:10:39.180> and<00:10:39.390> non-trivial 00:10:40.250 --> 00:10:40.260 align:start position:0% the first time this safe and non-trivial 00:10:40.260 --> 00:10:41.870 align:start position:0% the first time this safe and non-trivial binary<00:10:40.710> consensus<00:10:41.100> protocol<00:10:41.460> which<00:10:41.790> I 00:10:41.870 --> 00:10:41.880 align:start position:0% binary consensus protocol which I 00:10:41.880 --> 00:10:43.730 align:start position:0% binary consensus protocol which I presented<00:10:42.180> at<00:10:42.750> DEFCON<00:10:43.110> in<00:10:43.260> Shanghai<00:10:43.530> in 00:10:43.730 --> 00:10:43.740 align:start position:0% presented at DEFCON in Shanghai in 00:10:43.740 --> 00:10:49.820 align:start position:0% presented at DEFCON in Shanghai in Shanghai<00:10:45.440> it<00:10:47.210> you<00:10:48.210> know<00:10:48.300> use<00:10:48.510> this<00:10:48.720> idea<00:10:49.200> of<00:10:49.410> an 00:10:49.820 --> 00:10:49.830 align:start position:0% Shanghai it you know use this idea of an 00:10:49.830 --> 00:10:53.320 align:start position:0% Shanghai it you know use this idea of an ideal<00:10:49.920> adversary<00:10:50.700> to<00:10:51.330> argue<00:10:51.780> about<00:10:52.250> security 00:10:53.320 --> 00:10:53.330 align:start position:0% ideal adversary to argue about security 00:10:53.330 --> 00:10:55.579 align:start position:0% ideal adversary to argue about security which<00:10:54.330> you<00:10:54.450> now<00:10:54.570> we<00:10:54.630> replace<00:10:55.170> with<00:10:55.290> this<00:10:55.410> idea 00:10:55.579 --> 00:10:55.589 align:start position:0% which you now we replace with this idea 00:10:55.589 --> 00:10:57.800 align:start position:0% which you now we replace with this idea of<00:10:55.710> safety<00:10:55.920> Oracle 00:10:57.800 --> 00:10:57.810 align:start position:0% of safety Oracle 00:10:57.810 --> 00:10:59.300 align:start position:0% of safety Oracle and<00:10:57.930> but<00:10:58.380> but<00:10:58.650> it<00:10:58.770> was<00:10:58.890> like<00:10:59.040> you<00:10:59.130> know<00:10:59.220> the 00:10:59.300 --> 00:10:59.310 align:start position:0% and but but it was like you know the 00:10:59.310 --> 00:11:01.250 align:start position:0% and but but it was like you know the real<00:10:59.700> milestone<00:11:00.210> like<00:11:00.450> a<00:11:00.570> safe<00:11:00.870> non-trivial 00:11:01.250 --> 00:11:01.260 align:start position:0% real milestone like a safe non-trivial 00:11:01.260 --> 00:11:03.860 align:start position:0% real milestone like a safe non-trivial it<00:11:02.010> says<00:11:02.160> this<00:11:02.279> vertical<00:11:02.640> he's<00:11:03.480> like<00:11:03.630> a<00:11:03.720> real 00:11:03.860 --> 00:11:03.870 align:start position:0% it says this vertical he's like a real 00:11:03.870 --> 00:11:08.600 align:start position:0% it says this vertical he's like a real real<00:11:04.380> my<00:11:04.560> real<00:11:04.890> muscle<00:11:05.690> June<00:11:06.690> 2017<00:11:07.410> so<00:11:08.310> a 00:11:08.600 --> 00:11:08.610 align:start position:0% real my real muscle June 2017 so a 00:11:08.610 --> 00:11:10.340 align:start position:0% real my real muscle June 2017 so a couple<00:11:09.540> a<00:11:09.570> few<00:11:09.750> months<00:11:10.050> later 00:11:10.340 --> 00:11:10.350 align:start position:0% couple a few months later 00:11:10.350 --> 00:11:12.470 align:start position:0% couple a few months later lmd<00:11:10.920> ghost<00:11:11.160> was<00:11:11.370> first<00:11:11.670> specified<00:11:12.120> this 00:11:12.470 --> 00:11:12.480 align:start position:0% lmd ghost was first specified this 00:11:12.480 --> 00:11:17.000 align:start position:0% lmd ghost was first specified this happened<00:11:13.970> when<00:11:14.970> Karla<00:11:15.570> who<00:11:16.080> just<00:11:16.260> spoke<00:11:16.529> asked 00:11:17.000 --> 00:11:17.010 align:start position:0% happened when Karla who just spoke asked 00:11:17.010 --> 00:11:18.950 align:start position:0% happened when Karla who just spoke asked me<00:11:17.160> how<00:11:17.880> we're<00:11:18.089> ever<00:11:18.240> going<00:11:18.420> to<00:11:18.480> turn<00:11:18.660> from 00:11:18.950 --> 00:11:18.960 align:start position:0% me how we're ever going to turn from 00:11:18.960 --> 00:11:21.470 align:start position:0% me how we're ever going to turn from binary<00:11:19.140> consensus<00:11:19.830> to<00:11:20.070> watching<00:11:20.550> consensus 00:11:21.470 --> 00:11:21.480 align:start position:0% binary consensus to watching consensus 00:11:21.480 --> 00:11:22.850 align:start position:0% binary consensus to watching consensus he<00:11:21.900> was<00:11:22.020> like<00:11:22.110> frustrated<00:11:22.620> and<00:11:22.680> concerned 00:11:22.850 --> 00:11:22.860 align:start position:0% he was like frustrated and concerned 00:11:22.860 --> 00:11:24.350 align:start position:0% he was like frustrated and concerned Carl<00:11:23.430> and<00:11:23.520> I<00:11:23.550> were<00:11:23.610> working<00:11:23.820> together<00:11:24.000> at<00:11:24.270> the 00:11:24.350 --> 00:11:24.360 align:start position:0% Carl and I were working together at the 00:11:24.360 --> 00:11:25.610 align:start position:0% Carl and I were working together at the time<00:11:24.510> on<00:11:24.660> this<00:11:24.750> on<00:11:24.960> the<00:11:25.080> binary<00:11:25.260> extension 00:11:25.610 --> 00:11:25.620 align:start position:0% time on this on the binary extension 00:11:25.620 --> 00:11:27.920 align:start position:0% time on this on the binary extension protocol<00:11:25.950> and<00:11:26.310> I<00:11:27.150> was<00:11:27.270> like<00:11:27.360> I<00:11:27.390> just<00:11:27.660> gave<00:11:27.750> it<00:11:27.870> a 00:11:27.920 --> 00:11:27.930 align:start position:0% protocol and I was like I just gave it a 00:11:27.930 --> 00:11:32.810 align:start position:0% protocol and I was like I just gave it a try<00:11:28.080> and<00:11:28.200> somehow<00:11:28.670> oh<00:11:31.100> sorry<00:11:32.100> I'm<00:11:32.520> looking 00:11:32.810 --> 00:11:32.820 align:start position:0% try and somehow oh sorry I'm looking 00:11:32.820 --> 00:11:36.200 align:start position:0% try and somehow oh sorry I'm looking over<00:11:32.910> here<00:11:33.029> at<00:11:33.300> the<00:11:33.390> next<00:11:33.660> slide<00:11:33.750> so<00:11:35.210> actually 00:11:36.200 --> 00:11:36.210 align:start position:0% over here at the next slide so actually 00:11:36.210 --> 00:11:39.200 align:start position:0% over here at the next slide so actually before<00:11:36.330> the<00:11:37.260> before<00:11:38.190> the<00:11:38.460> for<00:11:38.910> choice<00:11:39.060> rule 00:11:39.200 --> 00:11:39.210 align:start position:0% before the before the for choice rule 00:11:39.210 --> 00:11:41.060 align:start position:0% before the before the for choice rule came<00:11:39.360> up<00:11:39.540> yo'ii<00:11:40.140> she<00:11:40.440> did<00:11:40.620> a<00:11:40.650> formal 00:11:41.060 --> 00:11:41.070 align:start position:0% came up yo'ii she did a formal 00:11:41.070 --> 00:11:42.350 align:start position:0% came up yo'ii she did a formal verification<00:11:41.279> of<00:11:41.670> the<00:11:41.790> safety<00:11:41.970> of<00:11:42.120> the<00:11:42.210> binary 00:11:42.350 --> 00:11:42.360 align:start position:0% verification of the safety of the binary 00:11:42.360 --> 00:11:46.220 align:start position:0% verification of the safety of the binary consensus<00:11:42.810> protocol<00:11:43.700> in<00:11:44.700> March<00:11:45.390> 2017<00:11:45.779> and 00:11:46.220 --> 00:11:46.230 align:start position:0% consensus protocol in March 2017 and 00:11:46.230 --> 00:11:47.840 align:start position:0% consensus protocol in March 2017 and then<00:11:46.680> in<00:11:46.800> June<00:11:47.040> the<00:11:47.220> latest<00:11:47.460> message<00:11:47.700> driven 00:11:47.840 --> 00:11:47.850 align:start position:0% then in June the latest message driven 00:11:47.850 --> 00:11:50.870 align:start position:0% then in June the latest message driven ghost<00:11:49.040> made<00:11:50.040> his<00:11:50.160> first<00:11:50.370> appearance<00:11:50.490> as<00:11:50.850> a 00:11:50.870 --> 00:11:50.880 align:start position:0% ghost made his first appearance as a 00:11:50.880 --> 00:11:53.300 align:start position:0% ghost made his first appearance as a specification<00:11:51.620> you<00:11:52.620> know<00:11:52.710> when<00:11:52.890> Carl<00:11:53.160> asked 00:11:53.300 --> 00:11:53.310 align:start position:0% specification you know when Carl asked 00:11:53.310 --> 00:11:54.800 align:start position:0% specification you know when Carl asked me<00:11:53.400> this<00:11:53.490> question<00:11:53.550> I<00:11:53.940> know<00:11:54.120> and<00:11:54.360> I<00:11:54.480> went<00:11:54.600> and 00:11:54.800 --> 00:11:54.810 align:start position:0% me this question I know and I went and 00:11:54.810 --> 00:11:56.240 align:start position:0% me this question I know and I went and adapted<00:11:55.170> the<00:11:55.230> binary<00:11:55.529> cousins<00:11:55.740> protocol<00:11:56.100> to 00:11:56.240 --> 00:11:56.250 align:start position:0% adapted the binary cousins protocol to 00:11:56.250 --> 00:11:57.980 align:start position:0% adapted the binary cousins protocol to the<00:11:56.279> latest<00:11:56.790> message<00:11:56.970> urban<00:11:57.300> ghost<00:11:57.600> Protocol 00:11:57.980 --> 00:11:57.990 align:start position:0% the latest message urban ghost Protocol 00:11:57.990 --> 00:12:01.490 align:start position:0% the latest message urban ghost Protocol with<00:11:58.410> very<00:11:58.650> very<00:11:58.860> minor<00:11:59.040> change<00:11:59.900> then<00:12:00.900> in<00:12:01.260> July 00:12:01.490 --> 00:12:01.500 align:start position:0% with very very minor change then in July 00:12:01.500 --> 00:12:04.520 align:start position:0% with very very minor change then in July 2017<00:12:02.220> at<00:12:02.370> the<00:12:02.400> ic3<00:12:02.760> therian<00:12:03.480> boot<00:12:03.630> camp<00:12:03.870> the 00:12:04.520 --> 00:12:04.530 align:start position:0% 2017 at the ic3 therian boot camp the 00:12:04.530 --> 00:12:07.910 align:start position:0% 2017 at the ic3 therian boot camp the LNG<00:12:04.980> ghost<00:12:05.280> was<00:12:05.580> first<00:12:06.120> implemented<00:12:06.720> I<00:12:07.080> worked 00:12:07.910 --> 00:12:07.920 align:start position:0% LNG ghost was first implemented I worked 00:12:07.920 --> 00:12:10.130 align:start position:0% LNG ghost was first implemented I worked together<00:12:08.070> with<00:12:08.400> John<00:12:08.880> levy<00:12:09.089> to<00:12:09.360> implement<00:12:10.020> it 00:12:10.130 --> 00:12:10.140 align:start position:0% together with John levy to implement it 00:12:10.140 --> 00:12:12.440 align:start position:0% together with John levy to implement it I<00:12:10.380> did<00:12:11.070> most<00:12:11.250> of<00:12:11.339> the<00:12:11.430> work<00:12:11.460> but<00:12:11.640> he<00:12:12.120> was 00:12:12.440 --> 00:12:12.450 align:start position:0% I did most of the work but he was 00:12:12.450 --> 00:12:16.820 align:start position:0% I did most of the work but he was definitely<00:12:12.930> there<00:12:13.080> and<00:12:13.140> contributing<00:12:15.830> in 00:12:16.820 --> 00:12:16.830 align:start position:0% definitely there and contributing in 00:12:16.830 --> 00:12:19.340 align:start position:0% definitely there and contributing in November<00:12:17.760> 2017<00:12:18.270> we<00:12:18.540> came<00:12:18.780> up<00:12:18.870> with<00:12:18.990> our<00:12:19.020> first 00:12:19.340 --> 00:12:19.350 align:start position:0% November 2017 we came up with our first 00:12:19.350 --> 00:12:21.320 align:start position:0% November 2017 we came up with our first atomic<00:12:19.620> cross<00:12:19.980> charred<00:12:20.310> pork<00:12:21.180> choice 00:12:21.320 --> 00:12:21.330 align:start position:0% atomic cross charred pork choice 00:12:21.330 --> 00:12:23.530 align:start position:0% atomic cross charred pork choice proposal<00:12:21.900> that<00:12:21.990> guarantees<00:12:22.470> that<00:12:22.500> you<00:12:23.190> know 00:12:23.530 --> 00:12:23.540 align:start position:0% proposal that guarantees that you know 00:12:23.540 --> 00:12:28.250 align:start position:0% proposal that guarantees that you know cross<00:12:24.540> our<00:12:24.720> communications<00:12:25.290> our<00:12:26.570> our<00:12:27.570> our 00:12:28.250 --> 00:12:28.260 align:start position:0% cross our communications our our our 00:12:28.260 --> 00:12:30.170 align:start position:0% cross our communications our our our atomic<00:12:28.890> it's<00:12:29.520> like<00:12:29.640> super<00:12:29.880> important 00:12:30.170 --> 00:12:30.180 align:start position:0% atomic it's like super important 00:12:30.180 --> 00:12:34.420 align:start position:0% atomic it's like super important property<00:12:30.560> and<00:12:31.610> this<00:12:32.610> was<00:12:32.730> actually<00:12:32.820> the<00:12:32.970> first 00:12:34.420 --> 00:12:34.430 align:start position:0% property and this was actually the first 00:12:34.430 --> 00:12:37.340 align:start position:0% property and this was actually the first charting<00:12:35.430> solution<00:12:35.850> that<00:12:36.089> ever<00:12:36.810> came<00:12:37.200> across 00:12:37.340 --> 00:12:37.350 align:start position:0% charting solution that ever came across 00:12:37.350 --> 00:12:39.440 align:start position:0% charting solution that ever came across the<00:12:37.650> UC<00:12:37.770> Kasper<00:12:38.130> research<00:12:38.430> is<00:12:38.640> this<00:12:39.150> atomic 00:12:39.440 --> 00:12:39.450 align:start position:0% the UC Kasper research is this atomic 00:12:39.450 --> 00:12:41.870 align:start position:0% the UC Kasper research is this atomic cross<00:12:39.780> yard<00:12:40.190> solution<00:12:41.190> with<00:12:41.310> merge<00:12:41.610> blocks 00:12:41.870 --> 00:12:41.880 align:start position:0% cross yard solution with merge blocks 00:12:41.880 --> 00:12:43.220 align:start position:0% cross yard solution with merge blocks which<00:12:42.060> are<00:12:42.150> blocks<00:12:42.390> that<00:12:42.570> exist<00:12:42.930> on<00:12:43.080> two 00:12:43.220 --> 00:12:43.230 align:start position:0% which are blocks that exist on two 00:12:43.230 --> 00:12:44.870 align:start position:0% which are blocks that exist on two chains<00:12:43.470> it<00:12:43.620> wants<00:12:43.890> in<00:12:43.980> there<00:12:44.130> and<00:12:44.339> the<00:12:44.459> chains 00:12:44.870 --> 00:12:44.880 align:start position:0% chains it wants in there and the chains 00:12:44.880 --> 00:12:46.730 align:start position:0% chains it wants in there and the chains of<00:12:45.089> both<00:12:45.240> both<00:12:45.570> of<00:12:45.630> them<00:12:45.900> so<00:12:46.500> they<00:12:46.589> have<00:12:46.680> the 00:12:46.730 --> 00:12:46.740 align:start position:0% of both both of them so they have the 00:12:46.740 --> 00:12:48.290 align:start position:0% of both both of them so they have the kind<00:12:46.860> of<00:12:46.950> synchronized<00:12:47.310> exactly<00:12:48.060> at<00:12:48.150> that 00:12:48.290 --> 00:12:48.300 align:start position:0% kind of synchronized exactly at that 00:12:48.300 --> 00:12:55.329 align:start position:0% kind of synchronized exactly at that height<00:12:48.510> and<00:12:49.850> later<00:12:51.470> quite<00:12:52.470> quite<00:12:53.280> a<00:12:53.310> lot<00:12:53.490> later 00:12:55.329 --> 00:12:55.339 align:start position:0% height and later quite quite a lot later 00:12:55.339 --> 00:12:59.740 align:start position:0% height and later quite quite a lot later we<00:12:56.339> came<00:12:56.490> up<00:12:56.640> with<00:12:56.760> the<00:12:57.000> cross<00:12:57.810> shard<00:12:58.080> message 00:12:59.740 --> 00:12:59.750 align:start position:0% we came up with the cross shard message 00:12:59.750 --> 00:13:05.329 align:start position:0% we came up with the cross shard message model<00:13:00.750> which<00:13:01.910> which<00:13:02.910> has<00:13:04.010> the<00:13:05.010> ability<00:13:05.100> to 00:13:05.329 --> 00:13:05.339 align:start position:0% model which which has the ability to 00:13:05.339 --> 00:13:06.380 align:start position:0% model which which has the ability to send<00:13:05.580> a<00:13:05.640> message<00:13:05.910> and<00:13:06.060> not<00:13:06.150> have<00:13:06.270> it<00:13:06.300> be 00:13:06.380 --> 00:13:06.390 align:start position:0% send a message and not have it be 00:13:06.390 --> 00:13:07.790 align:start position:0% send a message and not have it be received<00:13:06.630> right<00:13:06.810> away<00:13:06.990> but<00:13:07.200> have<00:13:07.380> we<00:13:07.500> received 00:13:07.790 --> 00:13:07.800 align:start position:0% received right away but have we received 00:13:07.800 --> 00:13:10.640 align:start position:0% received right away but have we received just<00:13:07.830> in<00:13:08.010> some<00:13:08.160> time<00:13:08.690> you<00:13:09.690> know<00:13:09.720> and<00:13:10.020> this<00:13:10.350> is 00:13:10.640 --> 00:13:10.650 align:start position:0% just in some time you know and this is 00:13:10.650 --> 00:13:11.480 align:start position:0% just in some time you know and this is much<00:13:10.890> more 00:13:11.480 --> 00:13:11.490 align:start position:0% much more 00:13:11.490 --> 00:13:14.059 align:start position:0% much more friendly<00:13:12.149> to<00:13:12.449> prevent<00:13:12.990> or<00:13:13.529> blossoming 00:13:14.059 --> 00:13:14.069 align:start position:0% friendly to prevent or blossoming 00:13:14.069 --> 00:13:16.249 align:start position:0% friendly to prevent or blossoming orphaned<00:13:14.490> it's<00:13:14.999> it's<00:13:15.329> a<00:13:15.509> much<00:13:15.749> more<00:13:15.899> realistic 00:13:16.249 --> 00:13:16.259 align:start position:0% orphaned it's it's a much more realistic 00:13:16.259 --> 00:13:18.949 align:start position:0% orphaned it's it's a much more realistic cross<00:13:17.129> communication<00:13:17.639> model<00:13:18.029> and<00:13:18.209> still<00:13:18.779> we 00:13:18.949 --> 00:13:18.959 align:start position:0% cross communication model and still we 00:13:18.959 --> 00:13:20.989 align:start position:0% cross communication model and still we have<00:13:19.139> atomicity<00:13:19.740> although<00:13:20.639> a<00:13:20.670> slightly 00:13:20.989 --> 00:13:20.999 align:start position:0% have atomicity although a slightly 00:13:20.999 --> 00:13:23.030 align:start position:0% have atomicity although a slightly different<00:13:21.179> notion<00:13:21.629> it's<00:13:22.079> more<00:13:22.230> like<00:13:22.439> a<00:13:22.709> de 00:13:23.030 --> 00:13:23.040 align:start position:0% different notion it's more like a de 00:13:23.040 --> 00:13:25.040 align:start position:0% different notion it's more like a de missing<00:13:23.339> a<00:13:23.429> finality<00:13:23.790> then<00:13:24.449> Adam<00:13:24.779> is<00:13:24.869> City 00:13:25.040 --> 00:13:25.050 align:start position:0% missing a finality then Adam is City 00:13:25.050 --> 00:13:26.449 align:start position:0% missing a finality then Adam is City just<00:13:25.199> in<00:13:25.319> the<00:13:25.439> fourth<00:13:25.619> choice<00:13:25.740> rule<00:13:26.009> the<00:13:26.369> way 00:13:26.449 --> 00:13:26.459 align:start position:0% just in the fourth choice rule the way 00:13:26.459 --> 00:13:27.799 align:start position:0% just in the fourth choice rule the way that<00:13:26.610> the<00:13:26.699> merge<00:13:26.850> block<00:13:27.089> will<00:13:27.389> the<00:13:27.660> merge 00:13:27.799 --> 00:13:27.809 align:start position:0% that the merge block will the merge 00:13:27.809 --> 00:13:29.329 align:start position:0% that the merge block will the merge blocking<00:13:28.139> any<00:13:28.619> portraits<00:13:29.069> will<00:13:29.189> at<00:13:29.249> any 00:13:29.329 --> 00:13:29.339 align:start position:0% blocking any portraits will at any 00:13:29.339 --> 00:13:30.919 align:start position:0% blocking any portraits will at any moment<00:13:29.699> you<00:13:29.819> have<00:13:29.939> this<00:13:30.029> atomicity<00:13:30.509> property 00:13:30.919 --> 00:13:30.929 align:start position:0% moment you have this atomicity property 00:13:30.929 --> 00:13:33.379 align:start position:0% moment you have this atomicity property with<00:13:31.499> this<00:13:31.679> one<00:13:31.860> isn't<00:13:32.459> there's<00:13:32.579> a<00:13:32.639> time<00:13:33.059> when 00:13:33.379 --> 00:13:33.389 align:start position:0% with this one isn't there's a time when 00:13:33.389 --> 00:13:34.850 align:start position:0% with this one isn't there's a time when you<00:13:33.420> just<00:13:33.600> went<00:13:33.809> sent<00:13:34.079> but<00:13:34.259> not<00:13:34.379> yet<00:13:34.559> received 00:13:34.850 --> 00:13:34.860 align:start position:0% you just went sent but not yet received 00:13:34.860 --> 00:13:36.319 align:start position:0% you just went sent but not yet received where<00:13:35.220> the<00:13:35.399> atomicity<00:13:35.699> is<00:13:35.879> not<00:13:35.999> really<00:13:36.149> there 00:13:36.319 --> 00:13:36.329 align:start position:0% where the atomicity is not really there 00:13:36.329 --> 00:13:38.119 align:start position:0% where the atomicity is not really there but<00:13:36.779> at<00:13:36.899> finality<00:13:37.410> it's<00:13:37.559> guaranteed<00:13:37.800> to<00:13:37.980> be 00:13:38.119 --> 00:13:38.129 align:start position:0% but at finality it's guaranteed to be 00:13:38.129 --> 00:13:40.369 align:start position:0% but at finality it's guaranteed to be there<00:13:38.339> like<00:13:38.490> you<00:13:38.579> can<00:13:38.699> ever<00:13:38.790> finalize<00:13:39.379> ascend 00:13:40.369 --> 00:13:40.379 align:start position:0% there like you can ever finalize ascend 00:13:40.379 --> 00:13:42.139 align:start position:0% there like you can ever finalize ascend without<00:13:40.619> the<00:13:40.740> receive<00:13:41.069> being<00:13:41.850> eventually 00:13:42.139 --> 00:13:42.149 align:start position:0% without the receive being eventually 00:13:42.149 --> 00:13:44.480 align:start position:0% without the receive being eventually finalized<00:13:42.540> you<00:13:42.689> can<00:13:42.779> never<00:13:43.100> you<00:13:44.100> know<00:13:44.220> have<00:13:44.459> a 00:13:44.480 --> 00:13:44.490 align:start position:0% finalized you can never you know have a 00:13:44.490 --> 00:13:46.850 align:start position:0% finalized you can never you know have a finalized<00:13:45.240> not<00:13:45.509> sent<00:13:45.839> and<00:13:46.110> a<00:13:46.529> finalized 00:13:46.850 --> 00:13:46.860 align:start position:0% finalized not sent and a finalized 00:13:46.860 --> 00:13:48.470 align:start position:0% finalized not sent and a finalized receipt<00:13:47.189> it<00:13:47.490> would<00:13:47.610> just<00:13:47.730> be<00:13:47.819> a<00:13:47.850> violation<00:13:48.240> of 00:13:48.470 --> 00:13:48.480 align:start position:0% receipt it would just be a violation of 00:13:48.480 --> 00:13:49.939 align:start position:0% receipt it would just be a violation of the<00:13:48.540> protocol<00:13:48.869> there<00:13:49.050> that<00:13:49.170> kind<00:13:49.350> of<00:13:49.379> I<00:13:49.709> mean 00:13:49.939 --> 00:13:49.949 align:start position:0% the protocol there that kind of I mean 00:13:49.949 --> 00:13:50.989 align:start position:0% the protocol there that kind of I mean the<00:13:50.129> protocol<00:13:50.399> guarantees<00:13:50.730> it<00:13:50.850> that<00:13:50.939> won't 00:13:50.989 --> 00:13:50.999 align:start position:0% the protocol guarantees it that won't 00:13:50.999 --> 00:13:52.699 align:start position:0% the protocol guarantees it that won't happen<00:13:51.179> so<00:13:51.869> like<00:13:52.050> if<00:13:52.319> you<00:13:52.410> follow<00:13:52.619> the 00:13:52.699 --> 00:13:52.709 align:start position:0% happen so like if you follow the 00:13:52.709 --> 00:13:55.600 align:start position:0% happen so like if you follow the protocol<00:13:52.860> that<00:13:53.279> that's<00:13:53.519> just<00:13:53.639> impossible<00:13:54.350> in 00:13:55.600 --> 00:13:55.610 align:start position:0% protocol that that's just impossible in 00:13:55.610 --> 00:13:58.400 align:start position:0% protocol that that's just impossible in August<00:13:56.610> of<00:13:56.730> 2018<00:13:57.240> we<00:13:57.449> came<00:13:57.869> up<00:13:57.990> with<00:13:58.050> the<00:13:58.139> first 00:13:58.400 --> 00:13:58.410 align:start position:0% August of 2018 we came up with the first 00:13:58.410 --> 00:14:01.150 align:start position:0% August of 2018 we came up with the first correct<00:13:58.860> and<00:13:59.040> complete<00:13:59.189> safety<00:14:00.179> Oracle 00:14:01.150 --> 00:14:01.160 align:start position:0% correct and complete safety Oracle 00:14:01.160 --> 00:14:03.199 align:start position:0% correct and complete safety Oracle decision<00:14:02.160> detector<00:14:02.610> and<00:14:02.879> this<00:14:02.970> is<00:14:03.119> an 00:14:03.199 --> 00:14:03.209 align:start position:0% decision detector and this is an 00:14:03.209 --> 00:14:08.650 align:start position:0% decision detector and this is an experience<00:14:03.779> inferred<00:14:04.769> like<00:14:05.730> math<00:14:06.269> Olympics 00:14:08.650 --> 00:14:08.660 align:start position:0% experience inferred like math Olympics 00:14:08.660 --> 00:14:10.549 align:start position:0% experience inferred like math Olympics workshop<00:14:09.660> I<00:14:09.749> don't<00:14:09.899> really<00:14:10.050> know<00:14:10.170> what<00:14:10.319> I 00:14:10.549 --> 00:14:10.559 align:start position:0% workshop I don't really know what I 00:14:10.559 --> 00:14:11.679 align:start position:0% workshop I don't really know what I don't<00:14:10.709> know<00:14:10.829> remember<00:14:11.100> what<00:14:11.189> it's<00:14:11.309> called 00:14:11.679 --> 00:14:11.689 align:start position:0% don't know remember what it's called 00:14:11.689 --> 00:14:15.019 align:start position:0% don't know remember what it's called Greg<00:14:12.689> price<00:14:12.990> came<00:14:13.199> up<00:14:13.379> with<00:14:13.499> this<00:14:13.759> who<00:14:14.759> isn't 00:14:15.019 --> 00:14:15.029 align:start position:0% Greg price came up with this who isn't 00:14:15.029 --> 00:14:16.910 align:start position:0% Greg price came up with this who isn't in<00:14:15.240> in<00:14:15.540> the<00:14:15.660> community<00:14:16.079> but<00:14:16.199> he's<00:14:16.410> you<00:14:16.709> know<00:14:16.769> he 00:14:16.910 --> 00:14:16.920 align:start position:0% in in the community but he's you know he 00:14:16.920 --> 00:14:19.309 align:start position:0% in in the community but he's you know he comes<00:14:17.279> to<00:14:17.399> these<00:14:17.519> a<00:14:17.689> hackathon<00:14:18.689> kind<00:14:18.990> of<00:14:19.079> like 00:14:19.309 --> 00:14:19.319 align:start position:0% comes to these a hackathon kind of like 00:14:19.319 --> 00:14:21.859 align:start position:0% comes to these a hackathon kind of like you're<00:14:19.439> not<00:14:19.589> hacking<00:14:19.829> events<00:14:20.360> and<00:14:21.360> we<00:14:21.689> have<00:14:21.720> a 00:14:21.859 --> 00:14:21.869 align:start position:0% you're not hacking events and we have a 00:14:21.869 --> 00:14:24.049 align:start position:0% you're not hacking events and we have a long<00:14:22.110> history<00:14:22.350> of<00:14:22.589> struggling<00:14:23.069> for<00:14:23.790> a<00:14:23.819> very 00:14:24.049 --> 00:14:24.059 align:start position:0% long history of struggling for a very 00:14:24.059 --> 00:14:26.179 align:start position:0% long history of struggling for a very long<00:14:24.299> time<00:14:24.329> before<00:14:24.929> this<00:14:25.470> Vista<00:14:25.889> this<00:14:26.009> one 00:14:26.179 --> 00:14:26.189 align:start position:0% long time before this Vista this one 00:14:26.189 --> 00:14:27.949 align:start position:0% long time before this Vista this one specification<00:14:26.610> for<00:14:27.149> detecting<00:14:27.569> safety 00:14:27.949 --> 00:14:27.959 align:start position:0% specification for detecting safety 00:14:27.959 --> 00:14:30.379 align:start position:0% specification for detecting safety especially<00:14:28.860> because<00:14:29.249> especially<00:14:30.149> in<00:14:30.329> the 00:14:30.379 --> 00:14:30.389 align:start position:0% especially because especially in the 00:14:30.389 --> 00:14:31.900 align:start position:0% especially because especially in the cases<00:14:30.569> of<00:14:30.720> all<00:14:30.990> the<00:14:31.230> cases<00:14:31.350> of 00:14:31.900 --> 00:14:31.910 align:start position:0% cases of all the cases of 00:14:31.910 --> 00:14:34.939 align:start position:0% cases of all the cases of equivocations<00:14:32.910> you<00:14:33.449> know<00:14:33.569> of<00:14:33.779> like<00:14:34.350> who<00:14:34.679> sees 00:14:34.939 --> 00:14:34.949 align:start position:0% equivocations you know of like who sees 00:14:34.949 --> 00:14:36.919 align:start position:0% equivocations you know of like who sees white<00:14:35.490> equivocations<00:14:36.149> it<00:14:36.509> gets<00:14:36.660> complicated 00:14:36.919 --> 00:14:36.929 align:start position:0% white equivocations it gets complicated 00:14:36.929 --> 00:14:38.480 align:start position:0% white equivocations it gets complicated one<00:14:37.230> different<00:14:37.649> validator<00:14:38.009> see<00:14:38.189> different 00:14:38.480 --> 00:14:38.490 align:start position:0% one different validator see different 00:14:38.490 --> 00:14:40.160 align:start position:0% one different validator see different equivocations<00:14:39.119> and<00:14:39.299> when<00:14:39.779> you<00:14:39.929> have<00:14:40.049> to 00:14:40.160 --> 00:14:40.170 align:start position:0% equivocations and when you have to 00:14:40.170 --> 00:14:42.439 align:start position:0% equivocations and when you have to reason<00:14:40.499> about<00:14:40.679> the<00:14:40.889> proof<00:14:41.100> while<00:14:42.089> they're 00:14:42.439 --> 00:14:42.449 align:start position:0% reason about the proof while they're 00:14:42.449 --> 00:14:44.600 align:start position:0% reason about the proof while they're equivocating<00:14:43.079> so<00:14:43.709> it<00:14:43.889> turns<00:14:44.100> out<00:14:44.189> this<00:14:44.459> was 00:14:44.600 --> 00:14:44.610 align:start position:0% equivocating so it turns out this was 00:14:44.610 --> 00:14:46.069 align:start position:0% equivocating so it turns out this was this<00:14:44.790> was<00:14:44.910> a<00:14:45.059> really<00:14:45.269> challenging<00:14:45.420> thing<00:14:45.720> and 00:14:46.069 --> 00:14:46.079 align:start position:0% this was a really challenging thing and 00:14:46.079 --> 00:14:47.840 align:start position:0% this was a really challenging thing and we<00:14:46.470> had<00:14:46.559> a<00:14:46.589> real<00:14:46.769> professional<00:14:47.309> mathematician 00:14:47.840 --> 00:14:47.850 align:start position:0% we had a real professional mathematician 00:14:47.850 --> 00:14:52.009 align:start position:0% we had a real professional mathematician like<00:14:48.149> math<00:14:48.540> olympian<00:14:48.990> solve<00:14:49.350> it<00:14:51.019> September 00:14:52.009 --> 00:14:52.019 align:start position:0% like math olympian solve it September 00:14:52.019 --> 00:14:53.660 align:start position:0% like math olympian solve it September 2018<00:14:52.410> we<00:14:52.589> did<00:14:52.709> the<00:14:52.799> first<00:14:52.889> implementation<00:14:53.369> of 00:14:53.660 --> 00:14:53.670 align:start position:0% 2018 we did the first implementation of 00:14:53.670 --> 00:14:56.929 align:start position:0% 2018 we did the first implementation of the<00:14:53.910> cross<00:14:54.389> guard<00:14:54.600> message<00:14:55.579> system<00:14:56.579> and 00:14:56.929 --> 00:14:56.939 align:start position:0% the cross guard message system and 00:14:56.939 --> 00:14:58.970 align:start position:0% the cross guard message system and here's<00:14:57.869> this<00:14:58.049> gift<00:14:58.350> that<00:14:58.529> we<00:14:58.619> have<00:14:58.799> it's 00:14:58.970 --> 00:14:58.980 align:start position:0% here's this gift that we have it's 00:14:58.980 --> 00:15:00.739 align:start position:0% here's this gift that we have it's really<00:14:59.189> beautiful<00:14:59.579> of<00:14:59.759> the<00:15:00.240> system<00:15:00.569> and 00:15:00.739 --> 00:15:00.749 align:start position:0% really beautiful of the system and 00:15:00.749 --> 00:15:02.569 align:start position:0% really beautiful of the system and basically<00:15:01.559> what's<00:15:01.799> happening<00:15:02.129> in<00:15:02.220> the<00:15:02.279> bottom 00:15:02.569 --> 00:15:02.579 align:start position:0% basically what's happening in the bottom 00:15:02.579 --> 00:15:03.949 align:start position:0% basically what's happening in the bottom is<00:15:02.730> that<00:15:02.910> blocks<00:15:03.179> are<00:15:03.329> being<00:15:03.449> orphaned<00:15:03.839> in 00:15:03.949 --> 00:15:03.959 align:start position:0% is that blocks are being orphaned in 00:15:03.959 --> 00:15:05.419 align:start position:0% is that blocks are being orphaned in order<00:15:04.139> to<00:15:04.230> guarantee<00:15:04.410> the<00:15:04.860> out<00:15:05.040> of<00:15:05.160> Missa<00:15:05.309> tee 00:15:05.419 --> 00:15:05.429 align:start position:0% order to guarantee the out of Missa tee 00:15:05.429 --> 00:15:07.669 align:start position:0% order to guarantee the out of Missa tee of<00:15:05.639> these<00:15:06.389> communications<00:15:07.019> between<00:15:07.259> the<00:15:07.410> two 00:15:07.669 --> 00:15:07.679 align:start position:0% of these communications between the two 00:15:07.679 --> 00:15:12.519 align:start position:0% of these communications between the two charts<00:15:09.350> in<00:15:10.350> October<00:15:11.069> 2018<00:15:11.429> we<00:15:11.670> did<00:15:11.819> our<00:15:11.910> first 00:15:12.519 --> 00:15:12.529 align:start position:0% charts in October 2018 we did our first 00:15:12.529 --> 00:15:15.379 align:start position:0% charts in October 2018 we did our first specification<00:15:13.529> of<00:15:13.790> very<00:15:14.790> for<00:15:14.910> implementation 00:15:15.379 --> 00:15:15.389 align:start position:0% specification of very for implementation 00:15:15.389 --> 00:15:16.970 align:start position:0% specification of very for implementation I<00:15:15.720> don't<00:15:16.230> know<00:15:16.290> when<00:15:16.410> the<00:15:16.470> specification 00:15:16.970 --> 00:15:16.980 align:start position:0% I don't know when the specification 00:15:16.980 --> 00:15:19.160 align:start position:0% I don't know when the specification happened<00:15:17.249> I<00:15:17.309> guess<00:15:17.459> of<00:15:18.420> the<00:15:18.480> multi-level 00:15:19.160 --> 00:15:19.170 align:start position:0% happened I guess of the multi-level 00:15:19.170 --> 00:15:21.019 align:start position:0% happened I guess of the multi-level chart<00:15:19.410> hierarchy<00:15:19.829> with<00:15:20.069> message<00:15:20.579> routing<00:15:20.939> and 00:15:21.019 --> 00:15:21.029 align:start position:0% chart hierarchy with message routing and 00:15:21.029 --> 00:15:22.669 align:start position:0% chart hierarchy with message routing and shard<00:15:21.299> balancing<00:15:21.689> so<00:15:22.049> this<00:15:22.169> is<00:15:22.259> like<00:15:22.410> taking 00:15:22.669 --> 00:15:22.679 align:start position:0% shard balancing so this is like taking 00:15:22.679 --> 00:15:23.560 align:start position:0% shard balancing so this is like taking it<00:15:22.769> to<00:15:22.829> the<00:15:22.919> next<00:15:22.949> level 00:15:23.560 --> 00:15:23.570 align:start position:0% it to the next level 00:15:23.570 --> 00:15:25.180 align:start position:0% it to the next level having<00:15:24.020> two<00:15:24.170> shards<00:15:24.560> that<00:15:24.650> communicate<00:15:25.160> a 00:15:25.180 --> 00:15:25.190 align:start position:0% having two shards that communicate a 00:15:25.190 --> 00:15:27.130 align:start position:0% having two shards that communicate a little<00:15:25.460> bit<00:15:25.580> in<00:15:26.000> between<00:15:26.090> them<00:15:26.450> we<00:15:26.900> want<00:15:27.050> to 00:15:27.130 --> 00:15:27.140 align:start position:0% little bit in between them we want to 00:15:27.140 --> 00:15:30.520 align:start position:0% little bit in between them we want to have<00:15:27.260> many<00:15:27.950> shards<00:15:28.280> that<00:15:28.750> do<00:15:29.750> routing<00:15:29.960> and<00:15:30.320> we 00:15:30.520 --> 00:15:30.530 align:start position:0% have many shards that do routing and we 00:15:30.530 --> 00:15:32.260 align:start position:0% have many shards that do routing and we want<00:15:30.680> to<00:15:30.770> have<00:15:31.010> a<00:15:31.070> fixed<00:15:31.400> shard<00:15:31.610> hierarchy<00:15:32.090> we 00:15:32.260 --> 00:15:32.270 align:start position:0% want to have a fixed shard hierarchy we 00:15:32.270 --> 00:15:33.760 align:start position:0% want to have a fixed shard hierarchy we want<00:15:32.480> to<00:15:32.540> have<00:15:32.660> a<00:15:32.690> the<00:15:33.140> ability<00:15:33.410> to<00:15:33.440> change 00:15:33.760 --> 00:15:33.770 align:start position:0% want to have a the ability to change 00:15:33.770 --> 00:15:35.800 align:start position:0% want to have a the ability to change charts<00:15:34.160> this<00:15:34.790> is<00:15:34.850> an<00:15:34.910> example<00:15:35.240> of<00:15:35.330> a<00:15:35.390> 2<00:15:35.540> shard 00:15:35.800 --> 00:15:35.810 align:start position:0% charts this is an example of a 2 shard 00:15:35.810 --> 00:15:37.630 align:start position:0% charts this is an example of a 2 shard system<00:15:36.140> with<00:15:36.320> a<00:15:36.350> root<00:15:36.620> shard<00:15:36.890> and<00:15:37.070> the<00:15:37.130> child 00:15:37.630 --> 00:15:37.640 align:start position:0% system with a root shard and the child 00:15:37.640 --> 00:15:39.670 align:start position:0% system with a root shard and the child shard<00:15:37.940> changing<00:15:38.540> positions<00:15:38.870> in<00:15:39.410> some<00:15:39.590> way 00:15:39.670 --> 00:15:39.680 align:start position:0% shard changing positions in some way 00:15:39.680 --> 00:15:40.870 align:start position:0% shard changing positions in some way there's<00:15:39.860> no<00:15:39.920> such<00:15:40.070> thing<00:15:40.280> as<00:15:40.310> a 00:15:40.870 --> 00:15:40.880 align:start position:0% there's no such thing as a 00:15:40.880 --> 00:15:42.250 align:start position:0% there's no such thing as a child<00:15:40.940> starter<00:15:41.390> anymore<00:15:41.660> there's<00:15:41.840> only<00:15:41.960> route 00:15:42.250 --> 00:15:42.260 align:start position:0% child starter anymore there's only route 00:15:42.260 --> 00:15:44.590 align:start position:0% child starter anymore there's only route blocks<00:15:42.560> in<00:15:42.770> the<00:15:42.890> and<00:15:43.070> child<00:15:43.850> blocks<00:15:44.090> at<00:15:44.540> every 00:15:44.590 --> 00:15:44.600 align:start position:0% blocks in the and child blocks at every 00:15:44.600 --> 00:15:46.270 align:start position:0% blocks in the and child blocks at every moment<00:15:44.960> in<00:15:45.140> the<00:15:45.260> fourth<00:15:45.470> choice<00:15:45.590> rule<00:15:45.860> maybe 00:15:46.270 --> 00:15:46.280 align:start position:0% moment in the fourth choice rule maybe 00:15:46.280 --> 00:15:48.400 align:start position:0% moment in the fourth choice rule maybe one<00:15:46.520> of<00:15:46.550> them<00:15:46.700> is<00:15:46.730> the<00:15:46.910> root<00:15:47.090> but<00:15:48.020> it<00:15:48.140> may<00:15:48.230> be<00:15:48.260> at 00:15:48.400 --> 00:15:48.410 align:start position:0% one of them is the root but it may be at 00:15:48.410 --> 00:15:49.660 align:start position:0% one of them is the root but it may be at some<00:15:48.530> moments<00:15:48.860> there's<00:15:49.040> both<00:15:49.340> of<00:15:49.490> them<00:15:49.580> are 00:15:49.660 --> 00:15:49.670 align:start position:0% some moments there's both of them are 00:15:49.670 --> 00:15:50.650 align:start position:0% some moments there's both of them are the<00:15:49.730> root<00:15:49.850> like<00:15:50.030> you<00:15:50.090> see<00:15:50.210> when<00:15:50.330> they're<00:15:50.420> when 00:15:50.650 --> 00:15:50.660 align:start position:0% the root like you see when they're when 00:15:50.660 --> 00:15:51.580 align:start position:0% the root like you see when they're when they're<00:15:50.810> when<00:15:51.050> they're<00:15:51.080> sideways<00:15:51.440> like<00:15:51.530> that 00:15:51.580 --> 00:15:51.590 align:start position:0% they're when they're sideways like that 00:15:51.590 --> 00:15:53.440 align:start position:0% they're when they're sideways like that that's<00:15:51.950> like<00:15:52.100> at<00:15:52.250> the<00:15:52.370> moment<00:15:52.490> that<00:15:53.120> moment<00:15:53.390> in 00:15:53.440 --> 00:15:53.450 align:start position:0% that's like at the moment that moment in 00:15:53.450 --> 00:15:54.850 align:start position:0% that's like at the moment that moment in the<00:15:53.480> fork<00:15:53.690> choice<00:15:53.870> the<00:15:54.140> parent<00:15:54.440> has<00:15:54.530> said<00:15:54.680> look 00:15:54.850 --> 00:15:54.860 align:start position:0% the fork choice the parent has said look 00:15:54.860 --> 00:15:57.640 align:start position:0% the fork choice the parent has said look I'm<00:15:55.040> not<00:15:55.400> the<00:15:55.970> root<00:15:56.150> anymore<00:15:56.390> and<00:15:56.900> then<00:15:57.560> the 00:15:57.640 --> 00:15:57.650 align:start position:0% I'm not the root anymore and then the 00:15:57.650 --> 00:15:59.410 align:start position:0% I'm not the root anymore and then the child<00:15:57.860> hadn't<00:15:58.130> picked<00:15:58.430> that<00:15:58.490> up<00:15:58.550> yet<00:15:58.790> and<00:15:59.090> so 00:15:59.410 --> 00:15:59.420 align:start position:0% child hadn't picked that up yet and so 00:15:59.420 --> 00:16:00.460 align:start position:0% child hadn't picked that up yet and so they're<00:15:59.570> both<00:15:59.660> they're<00:16:00.050> both<00:16:00.080> the<00:16:00.290> children 00:16:00.460 --> 00:16:00.470 align:start position:0% they're both they're both the children 00:16:00.470 --> 00:16:02.080 align:start position:0% they're both they're both the children actually<00:16:00.980> there<00:16:01.220> is<00:16:01.310> no<00:16:01.460> root<00:16:01.670> for<00:16:01.850> that<00:16:01.880> one 00:16:02.080 --> 00:16:02.090 align:start position:0% actually there is no root for that one 00:16:02.090 --> 00:16:03.820 align:start position:0% actually there is no root for that one moment<00:16:02.350> but<00:16:03.350> then<00:16:03.470> when<00:16:03.620> the<00:16:03.680> child 00:16:03.820 --> 00:16:03.830 align:start position:0% moment but then when the child 00:16:03.830 --> 00:16:04.900 align:start position:0% moment but then when the child eventually<00:16:04.220> receives<00:16:04.460> that<00:16:04.550> message<00:16:04.610> that 00:16:04.900 --> 00:16:04.910 align:start position:0% eventually receives that message that 00:16:04.910 --> 00:16:07.300 align:start position:0% eventually receives that message that they<00:16:05.000> have<00:16:05.120> to<00:16:05.270> do<00:16:05.860> because<00:16:06.860> of<00:16:06.950> the<00:16:07.040> nature<00:16:07.280> of 00:16:07.300 --> 00:16:07.310 align:start position:0% they have to do because of the nature of 00:16:07.310 --> 00:16:09.970 align:start position:0% they have to do because of the nature of the<00:16:07.400> fork<00:16:07.580> choice<00:16:07.730> rule<00:16:08.470> you<00:16:09.470> know<00:16:09.560> the<00:16:09.770> child 00:16:09.970 --> 00:16:09.980 align:start position:0% the fork choice rule you know the child 00:16:09.980 --> 00:16:13.510 align:start position:0% the fork choice rule you know the child becomes<00:16:10.190> the<00:16:10.310> parent<00:16:10.630> and<00:16:11.630> then<00:16:12.020> and<00:16:12.350> and<00:16:12.830> with 00:16:13.510 --> 00:16:13.520 align:start position:0% becomes the parent and then and and with 00:16:13.520 --> 00:16:15.040 align:start position:0% becomes the parent and then and and with single<00:16:14.090> message<00:16:14.330> hops<00:16:14.510> like<00:16:14.630> this<00:16:14.810> that<00:16:14.960> are 00:16:15.040 --> 00:16:15.050 align:start position:0% single message hops like this that are 00:16:15.050 --> 00:16:16.840 align:start position:0% single message hops like this that are atomic<00:16:15.290> you<00:16:15.500> can<00:16:15.620> implement<00:16:15.770> Rabi<00:16:16.070> though 00:16:16.840 --> 00:16:16.850 align:start position:0% atomic you can implement Rabi though 00:16:16.850 --> 00:16:18.340 align:start position:0% atomic you can implement Rabi though it's<00:16:16.940> guarantees<00:16:17.330> with<00:16:17.780> the<00:16:17.870> same<00:16:17.990> atomicity 00:16:18.340 --> 00:16:18.350 align:start position:0% it's guarantees with the same atomicity 00:16:18.350 --> 00:16:20.140 align:start position:0% it's guarantees with the same atomicity property<00:16:18.770> that<00:16:19.100> we<00:16:19.190> can<00:16:19.310> go<00:16:19.460> from<00:16:19.640> one<00:16:19.850> shard 00:16:20.140 --> 00:16:20.150 align:start position:0% property that we can go from one shard 00:16:20.150 --> 00:16:22.150 align:start position:0% property that we can go from one shard to<00:16:20.330> another<00:16:20.600> through<00:16:21.230> any<00:16:21.680> number<00:16:21.890> of<00:16:21.980> stars 00:16:22.150 --> 00:16:22.160 align:start position:0% to another through any number of stars 00:16:22.160 --> 00:16:24.190 align:start position:0% to another through any number of stars this<00:16:22.520> uses<00:16:22.850> routing<00:16:23.240> protocol<00:16:23.660> as<00:16:23.870> is<00:16:24.050> used 00:16:24.190 --> 00:16:24.200 align:start position:0% this uses routing protocol as is used 00:16:24.200 --> 00:16:26.470 align:start position:0% this uses routing protocol as is used like<00:16:24.320> a<00:16:24.440> routing<00:16:24.770> routing<00:16:25.010> table<00:16:25.520> system<00:16:25.880> that 00:16:26.470 --> 00:16:26.480 align:start position:0% like a routing routing table system that 00:16:26.480 --> 00:16:28.090 align:start position:0% like a routing routing table system that and<00:16:26.630> this<00:16:26.780> is<00:16:26.930> the<00:16:27.050> tables<00:16:27.350> get<00:16:27.470> updated<00:16:27.830> as 00:16:28.090 --> 00:16:28.100 align:start position:0% and this is the tables get updated as 00:16:28.100 --> 00:16:30.190 align:start position:0% and this is the tables get updated as the<00:16:28.310> chars<00:16:28.520> change<00:16:28.940> position<00:16:29.420> I<00:16:29.600> mean<00:16:29.990> if<00:16:30.140> the 00:16:30.190 --> 00:16:30.200 align:start position:0% the chars change position I mean if the 00:16:30.200 --> 00:16:31.900 align:start position:0% the chars change position I mean if the stars<00:16:30.380> are<00:16:30.440> a<00:16:30.530> fixed<00:16:30.710> position<00:16:30.830> you<00:16:31.550> kind<00:16:31.880> of 00:16:31.900 --> 00:16:31.910 align:start position:0% stars are a fixed position you kind of 00:16:31.910 --> 00:16:34.060 align:start position:0% stars are a fixed position you kind of have<00:16:32.090> static<00:16:32.510> routing<00:16:32.690> tables<00:16:33.110> you<00:16:33.740> have<00:16:33.770> just 00:16:34.060 --> 00:16:34.070 align:start position:0% have static routing tables you have just 00:16:34.070 --> 00:16:35.470 align:start position:0% have static routing tables you have just do<00:16:34.220> source<00:16:34.520> routing<00:16:34.760> calculate<00:16:35.300> from<00:16:35.420> the 00:16:35.470 --> 00:16:35.480 align:start position:0% do source routing calculate from the 00:16:35.480 --> 00:16:36.850 align:start position:0% do source routing calculate from the source<00:16:35.690> exactly<00:16:36.140> what<00:16:36.230> the<00:16:36.320> routes<00:16:36.470> gonna<00:16:36.650> be 00:16:36.850 --> 00:16:36.860 align:start position:0% source exactly what the routes gonna be 00:16:36.860 --> 00:16:38.980 align:start position:0% source exactly what the routes gonna be but<00:16:37.520> because<00:16:37.820> the<00:16:37.940> charts<00:16:38.360> are<00:16:38.480> moving<00:16:38.840> and 00:16:38.980 --> 00:16:38.990 align:start position:0% but because the charts are moving and 00:16:38.990 --> 00:16:40.150 align:start position:0% but because the charts are moving and the<00:16:39.080> shards<00:16:39.320> over<00:16:39.410> here<00:16:39.560> may<00:16:39.650> not<00:16:39.770> know<00:16:39.920> about 00:16:40.150 --> 00:16:40.160 align:start position:0% the shards over here may not know about 00:16:40.160 --> 00:16:41.620 align:start position:0% the shards over here may not know about the<00:16:40.280> changes<00:16:40.760> in<00:16:40.880> the<00:16:41.000> shard<00:16:41.210> shape<00:16:41.420> over 00:16:41.620 --> 00:16:41.630 align:start position:0% the changes in the shard shape over 00:16:41.630 --> 00:16:43.300 align:start position:0% the changes in the shard shape over there<00:16:41.780> we<00:16:42.230> need<00:16:42.320> to<00:16:42.380> have<00:16:42.530> a<00:16:42.560> dynamic<00:16:42.920> routing 00:16:43.300 --> 00:16:43.310 align:start position:0% there we need to have a dynamic routing 00:16:43.310 --> 00:16:47.380 align:start position:0% there we need to have a dynamic routing table<00:16:43.790> system<00:16:43.970> in<00:16:44.300> this<00:16:44.630> in<00:16:44.810> this<00:16:44.930> solution<00:16:46.390> in 00:16:47.380 --> 00:16:47.390 align:start position:0% table system in this in this solution in 00:16:47.390 --> 00:16:50.890 align:start position:0% table system in this in this solution in November<00:16:48.260> 2018<00:16:48.710> at<00:16:49.130> last<00:16:50.030> DEFCON<00:16:50.450> III 00:16:50.890 --> 00:16:50.900 align:start position:0% November 2018 at last DEFCON III 00:16:50.900 --> 00:16:53.170 align:start position:0% November 2018 at last DEFCON III released<00:16:51.260> this<00:16:51.590> minimal<00:16:52.340> CBC<00:16:52.760> Casper 00:16:53.170 --> 00:16:53.180 align:start position:0% released this minimal CBC Casper 00:16:53.180 --> 00:16:56.380 align:start position:0% released this minimal CBC Casper protocol<00:16:53.780> paper<00:16:54.020> which<00:16:55.390> described 00:16:56.380 --> 00:16:56.390 align:start position:0% protocol paper which described 00:16:56.390 --> 00:16:57.760 align:start position:0% protocol paper which described abstractly<00:16:56.900> a<00:16:56.990> family<00:16:57.320> of<00:16:57.410> consensus 00:16:57.760 --> 00:16:57.770 align:start position:0% abstractly a family of consensus 00:16:57.770 --> 00:17:00.940 align:start position:0% abstractly a family of consensus protocols<00:16:58.160> of<00:16:58.490> really<00:16:59.090> really<00:16:59.270> formally<00:16:59.950> and 00:17:00.940 --> 00:17:00.950 align:start position:0% protocols of really really formally and 00:17:00.950 --> 00:17:03.370 align:start position:0% protocols of really really formally and this<00:17:01.520> is<00:17:01.610> kind<00:17:01.790> of<00:17:01.880> represented<00:17:02.870> a<00:17:03.050> very 00:17:03.370 --> 00:17:03.380 align:start position:0% this is kind of represented a very 00:17:03.380 --> 00:17:05.890 align:start position:0% this is kind of represented a very general<00:17:03.710> abstraction<00:17:04.310> of<00:17:04.430> what<00:17:05.270> we<00:17:05.720> had<00:17:05.870> done 00:17:05.890 --> 00:17:05.900 align:start position:0% general abstraction of what we had done 00:17:05.900 --> 00:17:07.329 align:start position:0% general abstraction of what we had done before<00:17:06.320> with<00:17:06.470> like<00:17:06.560> the<00:17:06.650> binary<00:17:06.949> consensus 00:17:07.329 --> 00:17:07.339 align:start position:0% before with like the binary consensus 00:17:07.339 --> 00:17:09.189 align:start position:0% before with like the binary consensus protocol<00:17:07.699> or<00:17:07.820> the<00:17:07.850> watching<00:17:08.180> as<00:17:08.300> per<00:17:08.510> core<00:17:08.720> we 00:17:09.189 --> 00:17:09.199 align:start position:0% protocol or the watching as per core we 00:17:09.199 --> 00:17:10.090 align:start position:0% protocol or the watching as per core we had<00:17:09.290> a<00:17:09.320> whole<00:17:09.470> bunch<00:17:09.500> of<00:17:09.650> other<00:17:09.770> ones<00:17:09.920> I<00:17:10.010> got 00:17:10.090 --> 00:17:10.100 align:start position:0% had a whole bunch of other ones I got 00:17:10.100 --> 00:17:14.319 align:start position:0% had a whole bunch of other ones I got integer<00:17:10.490> consensus<00:17:10.880> protocol<00:17:12.250> and<00:17:13.250> and<00:17:14.000> this 00:17:14.319 --> 00:17:14.329 align:start position:0% integer consensus protocol and and this 00:17:14.329 --> 00:17:15.550 align:start position:0% integer consensus protocol and and this kind<00:17:14.510> of<00:17:14.570> really<00:17:14.750> abstracted<00:17:15.260> them<00:17:15.380> and 00:17:15.550 --> 00:17:15.560 align:start position:0% kind of really abstracted them and 00:17:15.560 --> 00:17:17.470 align:start position:0% kind of really abstracted them and formalized<00:17:16.189> it<00:17:16.370> in<00:17:16.550> a<00:17:16.670> way<00:17:16.790> and<00:17:17.000> wrote<00:17:17.270> and 00:17:17.470 --> 00:17:17.480 align:start position:0% formalized it in a way and wrote and 00:17:17.480 --> 00:17:18.730 align:start position:0% formalized it in a way and wrote and when<00:17:17.570> we<00:17:17.660> wrote<00:17:17.780> the<00:17:17.900> proofs<00:17:18.140> down<00:17:18.410> in 00:17:18.730 --> 00:17:18.740 align:start position:0% when we wrote the proofs down in 00:17:18.740 --> 00:17:22.030 align:start position:0% when we wrote the proofs down in incredible<00:17:19.310> detail<00:17:20.560> it's<00:17:21.560> way<00:17:21.740> too<00:17:21.800> much 00:17:22.030 --> 00:17:22.040 align:start position:0% incredible detail it's way too much 00:17:22.040 --> 00:17:26.679 align:start position:0% incredible detail it's way too much detail<00:17:22.720> and<00:17:23.720> then<00:17:25.120> next<00:17:26.120> month<00:17:26.300> we<00:17:26.510> had<00:17:26.600> the 00:17:26.679 --> 00:17:26.689 align:start position:0% detail and then next month we had the 00:17:26.689 --> 00:17:28.390 align:start position:0% detail and then next month we had the first<00:17:26.839> formal<00:17:27.260> CBC<00:17:27.680> Kasper<00:17:28.010> light<00:17:28.160> client 00:17:28.390 --> 00:17:28.400 align:start position:0% first formal CBC Kasper light client 00:17:28.400 --> 00:17:31.630 align:start position:0% first formal CBC Kasper light client specification<00:17:29.620> which<00:17:30.620> won't<00:17:31.310> see<00:17:31.520> the<00:17:31.610> light 00:17:31.630 --> 00:17:31.640 align:start position:0% specification which won't see the light 00:17:31.640 --> 00:17:35.170 align:start position:0% specification which won't see the light of<00:17:31.850> day<00:17:31.940> until<00:17:32.150> today<00:17:32.540> actually<00:17:32.800> and<00:17:34.060> this<00:17:35.060> is 00:17:35.170 --> 00:17:35.180 align:start position:0% of day until today actually and this is 00:17:35.180 --> 00:17:35.560 align:start position:0% of day until today actually and this is kind<00:17:35.360> of 00:17:35.560 --> 00:17:35.570 align:start position:0% kind of 00:17:35.570 --> 00:17:37.330 align:start position:0% kind of because<00:17:35.809> originally<00:17:36.409> the<00:17:36.590> CDC<00:17:37.070> Casper 00:17:37.330 --> 00:17:37.340 align:start position:0% because originally the CDC Casper 00:17:37.340 --> 00:17:41.019 align:start position:0% because originally the CDC Casper specification<00:17:38.090> it<00:17:38.470> has<00:17:39.610> message<00:17:40.610> nesting 00:17:41.019 --> 00:17:41.029 align:start position:0% specification it has message nesting 00:17:41.029 --> 00:17:42.999 align:start position:0% specification it has message nesting instead<00:17:41.299> of<00:17:41.389> message<00:17:41.630> linking<00:17:42.049> and<00:17:42.259> so<00:17:42.740> the 00:17:42.999 --> 00:17:43.009 align:start position:0% instead of message linking and so the 00:17:43.009 --> 00:17:45.100 align:start position:0% instead of message linking and so the messages<00:17:43.399> just<00:17:43.549> get<00:17:43.730> really<00:17:43.909> big<00:17:44.179> and<00:17:44.720> that's 00:17:45.100 --> 00:17:45.110 align:start position:0% messages just get really big and that's 00:17:45.110 --> 00:17:46.269 align:start position:0% messages just get really big and that's not<00:17:45.289> really<00:17:45.529> practical<00:17:45.649> you<00:17:45.980> all<00:17:46.039> don't<00:17:46.130> like 00:17:46.269 --> 00:17:46.279 align:start position:0% not really practical you all don't like 00:17:46.279 --> 00:17:47.799 align:start position:0% not really practical you all don't like to<00:17:46.370> see<00:17:46.490> that<00:17:46.669> even<00:17:46.970> though<00:17:47.090> than<00:17:47.539> the<00:17:47.600> point 00:17:47.799 --> 00:17:47.809 align:start position:0% to see that even though than the point 00:17:47.809 --> 00:17:49.629 align:start position:0% to see that even though than the point of<00:17:47.899> view<00:17:47.960> of<00:17:48.019> like<00:17:48.289> the<00:17:48.470> semantics<00:17:49.100> in<00:17:49.429> the 00:17:49.629 --> 00:17:49.639 align:start position:0% of view of like the semantics in the 00:17:49.639 --> 00:17:51.430 align:start position:0% of view of like the semantics in the math<00:17:49.789> like<00:17:50.029> it's<00:17:50.210> still<00:17:50.419> a<00:17:50.450> non-trivial<00:17:50.960> save 00:17:51.430 --> 00:17:51.440 align:start position:0% math like it's still a non-trivial save 00:17:51.440 --> 00:17:55.269 align:start position:0% math like it's still a non-trivial save whatever<00:17:52.159> consensus<00:17:52.549> protocol<00:17:53.679> so<00:17:54.679> we<00:17:55.130> have<00:17:55.250> a 00:17:55.269 --> 00:17:55.279 align:start position:0% whatever consensus protocol so we have a 00:17:55.279 --> 00:17:57.009 align:start position:0% whatever consensus protocol so we have a like<00:17:55.460> client<00:17:55.820> specification<00:17:56.389> as<00:17:56.539> of<00:17:56.659> November 00:17:57.009 --> 00:17:57.019 align:start position:0% like client specification as of November 00:17:57.019 --> 00:18:02.379 align:start position:0% like client specification as of November 28<00:17:57.320> 28<00:17:57.740> 20<00:17:58.309> 18<00:17:58.779> over<00:17:59.779> 20<00:18:00.049> February<00:18:00.950> 20<00:18:01.370> 19<00:18:01.789> one 00:18:02.379 --> 00:18:02.389 align:start position:0% 28 28 20 18 over 20 February 20 19 one 00:18:02.389 --> 00:18:06.519 align:start position:0% 28 28 20 18 over 20 February 20 19 one of<00:18:02.509> these<00:18:03.909> etherium<00:18:04.909> stanford<00:18:05.630> math<00:18:06.230> will 00:18:06.519 --> 00:18:06.529 align:start position:0% of these etherium stanford math will 00:18:06.529 --> 00:18:09.220 align:start position:0% of these etherium stanford math will impact<00:18:07.070> things<00:18:07.669> I<00:18:08.000> wish<00:18:08.870> I<00:18:08.929> knew<00:18:09.019> what<00:18:09.049> they 00:18:09.220 --> 00:18:09.230 align:start position:0% impact things I wish I knew what they 00:18:09.230 --> 00:18:12.399 align:start position:0% impact things I wish I knew what they were<00:18:09.320> called<00:18:10.480> we<00:18:11.480> came<00:18:11.659> out<00:18:11.809> with<00:18:12.110> Daniel 00:18:12.399 --> 00:18:12.409 align:start position:0% were called we came out with Daniel 00:18:12.409 --> 00:18:14.230 align:start position:0% were called we came out with Daniel Caine<00:18:12.679> with<00:18:13.279> working<00:18:13.580> with<00:18:13.669> Greg<00:18:13.820> price<00:18:14.059> who 00:18:14.230 --> 00:18:14.240 align:start position:0% Caine with working with Greg price who 00:18:14.240 --> 00:18:15.700 align:start position:0% Caine with working with Greg price who came<00:18:14.389> up<00:18:14.509> with<00:18:14.539> the<00:18:14.720> original<00:18:14.809> complete 00:18:15.700 --> 00:18:15.710 align:start position:0% came up with the original complete 00:18:15.710 --> 00:18:18.100 align:start position:0% came up with the original complete correct<00:18:16.070> safety<00:18:16.759> detector<00:18:17.210> decision 00:18:18.100 --> 00:18:18.110 align:start position:0% correct safety detector decision 00:18:18.110 --> 00:18:21.460 align:start position:0% correct safety detector decision detector<00:18:19.450> came<00:18:20.450> up<00:18:20.539> with<00:18:20.659> an<00:18:21.110> efficient 00:18:21.460 --> 00:18:21.470 align:start position:0% detector came up with an efficient 00:18:21.470 --> 00:18:24.549 align:start position:0% detector came up with an efficient Oracle<00:18:22.129> making<00:18:22.730> decisions<00:18:23.259> which<00:18:24.259> is<00:18:24.350> a<00:18:24.379> big 00:18:24.549 --> 00:18:24.559 align:start position:0% Oracle making decisions which is a big 00:18:24.559 --> 00:18:26.230 align:start position:0% Oracle making decisions which is a big deal<00:18:24.679> because<00:18:24.830> that<00:18:25.429> other<00:18:25.549> one<00:18:25.759> is 00:18:26.230 --> 00:18:26.240 align:start position:0% deal because that other one is 00:18:26.240 --> 00:18:28.389 align:start position:0% deal because that other one is computationally<00:18:26.809> quite<00:18:26.899> inefficient<00:18:27.399> and 00:18:28.389 --> 00:18:28.399 align:start position:0% computationally quite inefficient and 00:18:28.399 --> 00:18:29.649 align:start position:0% computationally quite inefficient and this<00:18:28.519> is<00:18:28.669> also<00:18:28.789> like<00:18:29.000> yeah<00:18:29.149> quite<00:18:29.389> heavy 00:18:29.649 --> 00:18:29.659 align:start position:0% this is also like yeah quite heavy 00:18:29.659 --> 00:18:34.269 align:start position:0% this is also like yeah quite heavy lifting<00:18:29.960> that<00:18:30.259> was<00:18:30.409> done<00:18:31.840> in<00:18:32.840> May<00:18:33.350> 2019<00:18:34.039> the 00:18:34.269 --> 00:18:34.279 align:start position:0% lifting that was done in May 2019 the 00:18:34.279 --> 00:18:36.909 align:start position:0% lifting that was done in May 2019 the first<00:18:34.639> to<00:18:35.000> live<00:18:35.659> in<00:18:35.779> strategies<00:18:36.169> based<00:18:36.529> on<00:18:36.830> the 00:18:36.909 --> 00:18:36.919 align:start position:0% first to live in strategies based on the 00:18:36.919 --> 00:18:39.789 align:start position:0% first to live in strategies based on the leaders<00:18:37.190> for<00:18:37.639> CBC<00:18:38.000> Casper<00:18:38.330> were<00:18:38.480> specified<00:18:38.929> by 00:18:39.789 --> 00:18:39.799 align:start position:0% leaders for CBC Casper were specified by 00:18:39.799 --> 00:18:42.779 align:start position:0% leaders for CBC Casper were specified by researchers<00:18:40.700> at<00:18:41.360> the<00:18:41.570> Casper<00:18:41.840> labs<00:18:42.019> team 00:18:42.779 --> 00:18:42.789 align:start position:0% researchers at the Casper labs team 00:18:42.789 --> 00:18:45.159 align:start position:0% researchers at the Casper labs team actually<00:18:43.789> Daniel<00:18:43.970> Cain<00:18:44.269> who<00:18:44.539> was<00:18:44.570> on<00:18:44.779> contract 00:18:45.159 --> 00:18:45.169 align:start position:0% actually Daniel Cain who was on contract 00:18:45.169 --> 00:18:48.909 align:start position:0% actually Daniel Cain who was on contract with<00:18:45.320> them<00:18:45.470> and<00:18:45.789> andreas<00:18:46.789> Bechtler<00:18:47.799> did<00:18:48.799> they 00:18:48.909 --> 00:18:48.919 align:start position:0% with them and andreas Bechtler did they 00:18:48.919 --> 00:18:50.619 align:start position:0% with them and andreas Bechtler did they were<00:18:49.070> both<00:18:49.220> produced<00:18:49.639> in<00:18:49.879> almost<00:18:50.240> immediate 00:18:50.619 --> 00:18:50.629 align:start position:0% were both produced in almost immediate 00:18:50.629 --> 00:18:52.060 align:start position:0% were both produced in almost immediate sequence<00:18:51.019> like<00:18:51.169> within<00:18:51.379> like<00:18:51.559> a<00:18:51.590> week<00:18:51.679> of<00:18:51.919> each 00:18:52.060 --> 00:18:52.070 align:start position:0% sequence like within like a week of each 00:18:52.070 --> 00:18:54.940 align:start position:0% sequence like within like a week of each other<00:18:52.159> as<00:18:52.730> like<00:18:52.879> a<00:18:52.909> leader<00:18:53.149> based<00:18:53.799> CDC<00:18:54.799> has 00:18:54.940 --> 00:18:54.950 align:start position:0% other as like a leader based CDC has 00:18:54.950 --> 00:18:56.190 align:start position:0% other as like a leader based CDC has provided<00:18:55.159> a<00:18:55.340> strategy<00:18:55.730> where<00:18:55.879> leader 00:18:56.190 --> 00:18:56.200 align:start position:0% provided a strategy where leader 00:18:56.200 --> 00:18:57.999 align:start position:0% provided a strategy where leader synchronizes<00:18:57.200> everyone<00:18:57.559> and<00:18:57.679> guarantees 00:18:57.999 --> 00:18:58.009 align:start position:0% synchronizes everyone and guarantees 00:18:58.009 --> 00:18:59.470 align:start position:0% synchronizes everyone and guarantees that<00:18:58.039> they<00:18:58.279> go<00:18:58.399> through<00:18:58.580> the<00:18:58.700> same<00:18:58.850> states<00:18:59.179> in 00:18:59.470 --> 00:18:59.480 align:start position:0% that they go through the same states in 00:18:59.480 --> 00:19:03.999 align:start position:0% that they go through the same states in order<00:19:00.139> to<00:19:00.289> make<00:19:00.409> decisions<00:19:02.500> also<00:19:03.500> the<00:19:03.830> same 00:19:03.999 --> 00:19:04.009 align:start position:0% order to make decisions also the same 00:19:04.009 --> 00:19:08.350 align:start position:0% order to make decisions also the same month<00:19:04.220> but<00:19:04.779> towards<00:19:05.779> the<00:19:05.840> end<00:19:06.519> I<00:19:07.519> came<00:19:08.059> up<00:19:08.179> with 00:19:08.350 --> 00:19:08.360 align:start position:0% month but towards the end I came up with 00:19:08.360 --> 00:19:10.539 align:start position:0% month but towards the end I came up with the<00:19:08.779> first<00:19:09.740> line<00:19:09.980> of<00:19:10.070> strategy<00:19:10.340> based<00:19:10.490> on 00:19:10.539 --> 00:19:10.549 align:start position:0% the first line of strategy based on 00:19:10.549 --> 00:19:13.289 align:start position:0% the first line of strategy based on fault<00:19:10.789> rejection<00:19:11.090> for<00:19:11.389> CBC<00:19:11.659> Casper<00:19:12.019> which<00:19:12.889> is 00:19:13.289 --> 00:19:13.299 align:start position:0% fault rejection for CBC Casper which is 00:19:13.299 --> 00:19:15.340 align:start position:0% fault rejection for CBC Casper which is quite<00:19:14.299> a<00:19:14.330> different<00:19:14.419> strategy<00:19:14.779> has<00:19:15.139> to<00:19:15.230> do 00:19:15.340 --> 00:19:15.350 align:start position:0% quite a different strategy has to do 00:19:15.350 --> 00:19:17.289 align:start position:0% quite a different strategy has to do with<00:19:15.500> you<00:19:15.860> know<00:19:15.950> validators<00:19:16.460> detecting 00:19:17.289 --> 00:19:17.299 align:start position:0% with you know validators detecting 00:19:17.299 --> 00:19:19.990 align:start position:0% with you know validators detecting whether<00:19:18.080> each<00:19:18.350> other<00:19:18.559> are<00:19:18.740> faulty<00:19:19.100> and<00:19:19.309> using 00:19:19.990 --> 00:19:20.000 align:start position:0% whether each other are faulty and using 00:19:20.000 --> 00:19:21.519 align:start position:0% whether each other are faulty and using information<00:19:20.480> about<00:19:20.659> the<00:19:20.750> faults<00:19:21.049> in<00:19:21.169> order<00:19:21.379> to 00:19:21.519 --> 00:19:21.529 align:start position:0% information about the faults in order to 00:19:21.529 --> 00:19:25.299 align:start position:0% information about the faults in order to come<00:19:22.309> up<00:19:22.340> with<00:19:22.519> a<00:19:22.580> alignment<00:19:23.240> strategy<00:19:24.309> then 00:19:25.299 --> 00:19:25.309 align:start position:0% come up with a alignment strategy then 00:19:25.309 --> 00:19:28.119 align:start position:0% come up with a alignment strategy then the<00:19:25.730> IC<00:19:26.059> 3<00:19:26.269> during<00:19:26.779> bootcamp<00:19:26.990> in<00:19:27.289> 2019<00:19:27.830> we<00:19:27.980> came 00:19:28.119 --> 00:19:28.129 align:start position:0% the IC 3 during bootcamp in 2019 we came 00:19:28.129 --> 00:19:30.159 align:start position:0% the IC 3 during bootcamp in 2019 we came up<00:19:28.279> with<00:19:28.429> and<00:19:28.759> did<00:19:28.940> oh<00:19:29.149> I<00:19:29.299> forgot 00:19:30.159 --> 00:19:30.169 align:start position:0% up with and did oh I forgot 00:19:30.169 --> 00:19:31.659 align:start position:0% up with and did oh I forgot I<00:19:30.200> remember<00:19:30.919> now<00:19:31.039> sorry<00:19:31.340> I<00:19:31.399> should<00:19:31.639> have 00:19:31.659 --> 00:19:31.669 align:start position:0% I remember now sorry I should have 00:19:31.669 --> 00:19:33.519 align:start position:0% I remember now sorry I should have mentioned<00:19:31.759> so<00:19:32.360> the<00:19:32.480> sharding<00:19:32.960> specification 00:19:33.519 --> 00:19:33.529 align:start position:0% mentioned so the sharding specification 00:19:33.529 --> 00:19:35.560 align:start position:0% mentioned so the sharding specification for<00:19:33.679> the<00:19:33.830> cross<00:19:34.009> hard<00:19:34.190> messages<00:19:34.580> was<00:19:35.360> at<00:19:35.450> the 00:19:35.560 --> 00:19:35.570 align:start position:0% for the cross hard messages was at the 00:19:35.570 --> 00:19:37.289 align:start position:0% for the cross hard messages was at the 2018 00:19:37.289 --> 00:19:37.299 align:start position:0% 2018 00:19:37.299 --> 00:19:40.029 align:start position:0% 2018 2018<00:19:38.299> IC<00:19:38.570> 3<00:19:38.690> etherion<00:19:39.019> bootcamp<00:19:39.379> and<00:19:39.649> this<00:19:39.919> is 00:19:40.029 --> 00:19:40.039 align:start position:0% 2018 IC 3 etherion bootcamp and this is 00:19:40.039 --> 00:19:41.980 align:start position:0% 2018 IC 3 etherion bootcamp and this is where<00:19:40.159> Aditya<00:19:40.549> came<00:19:40.909> on<00:19:41.059> to<00:19:41.179> the<00:19:41.269> CBC<00:19:41.509> casper 00:19:41.980 --> 00:19:41.990 align:start position:0% where Aditya came on to the CBC casper 00:19:41.990 --> 00:19:43.750 align:start position:0% where Aditya came on to the CBC casper team<00:19:42.500> and<00:19:42.830> like<00:19:43.070> immediately<00:19:43.460> started 00:19:43.750 --> 00:19:43.760 align:start position:0% team and like immediately started 00:19:43.760 --> 00:19:45.220 align:start position:0% team and like immediately started writing<00:19:43.970> proofs<00:19:44.210> and<00:19:44.419> he<00:19:44.809> really<00:19:44.990> helped<00:19:45.139> with 00:19:45.220 --> 00:19:45.230 align:start position:0% writing proofs and he really helped with 00:19:45.230 --> 00:19:47.000 align:start position:0% writing proofs and he really helped with the<00:19:45.440> charting<00:19:46.039> stuff<00:19:46.220> who's<00:19:46.580> been<00:19:46.730> helping 00:19:47.000 --> 00:19:47.010 align:start position:0% the charting stuff who's been helping 00:19:47.010 --> 00:19:50.000 align:start position:0% the charting stuff who's been helping with<00:19:47.100> it<00:19:47.190> ever<00:19:47.310> since<00:19:48.330> so<00:19:49.080> and<00:19:49.680> then<00:19:49.860> the 00:19:50.000 --> 00:19:50.010 align:start position:0% with it ever since so and then the 00:19:50.010 --> 00:19:51.440 align:start position:0% with it ever since so and then the implementation<00:19:50.160> happen<00:19:50.700> obviously<00:19:51.000> after 00:19:51.440 --> 00:19:51.450 align:start position:0% implementation happen obviously after 00:19:51.450 --> 00:19:53.150 align:start position:0% implementation happen obviously after the<00:19:51.660> specification<00:19:52.290> and<00:19:52.470> that<00:19:52.950> was<00:19:53.070> I<00:19:53.130> guess 00:19:53.150 --> 00:19:53.160 align:start position:0% the specification and that was I guess 00:19:53.160 --> 00:19:54.710 align:start position:0% the specification and that was I guess I'd<00:19:53.400> like<00:19:53.430> June<00:19:53.700> 2018<00:19:54.150> or<00:19:54.450> something<00:19:54.660> like 00:19:54.710 --> 00:19:54.720 align:start position:0% I'd like June 2018 or something like 00:19:54.720 --> 00:19:57.170 align:start position:0% I'd like June 2018 or something like that<00:19:54.780> so<00:19:55.500> now<00:19:55.680> June<00:19:56.100> 2019<00:19:56.580> we<00:19:56.790> came<00:19:56.910> up<00:19:57.060> with 00:19:57.170 --> 00:19:57.180 align:start position:0% that so now June 2019 we came up with 00:19:57.180 --> 00:19:58.850 align:start position:0% that so now June 2019 we came up with like<00:19:57.270> me<00:19:57.390> efficient<00:19:57.810> efficient<00:19:58.440> algorithms 00:19:58.850 --> 00:19:58.860 align:start position:0% like me efficient efficient algorithms 00:19:58.860 --> 00:20:01.940 align:start position:0% like me efficient efficient algorithms for<00:19:58.980> L&D<00:19:59.700> coast<00:20:00.290> updating<00:20:01.290> the<00:20:01.470> safety 00:20:01.940 --> 00:20:01.950 align:start position:0% for L&D coast updating the safety 00:20:01.950 --> 00:20:04.730 align:start position:0% for L&D coast updating the safety detector<00:20:02.400> and<00:20:03.180> you<00:20:03.630> know<00:20:03.720> other<00:20:03.960> other<00:20:04.290> kind 00:20:04.730 --> 00:20:04.740 align:start position:0% detector and you know other other kind 00:20:04.740 --> 00:20:06.530 align:start position:0% detector and you know other other kind of<00:20:04.830> efficiency<00:20:05.220> stuff<00:20:05.670> to<00:20:06.030> do<00:20:06.150> with<00:20:06.300> with 00:20:06.530 --> 00:20:06.540 align:start position:0% of efficiency stuff to do with with 00:20:06.540 --> 00:20:11.840 align:start position:0% of efficiency stuff to do with with Casper<00:20:06.870> in<00:20:07.610> july<00:20:08.630> 2019<00:20:10.220> sebastian<00:20:11.220> zany<00:20:11.550> came 00:20:11.840 --> 00:20:11.850 align:start position:0% Casper in july 2019 sebastian zany came 00:20:11.850 --> 00:20:13.040 align:start position:0% Casper in july 2019 sebastian zany came up<00:20:11.970> with<00:20:12.150> the<00:20:12.210> first<00:20:12.390> asynchronous 00:20:13.040 --> 00:20:13.050 align:start position:0% up with the first asynchronous 00:20:13.050 --> 00:20:15.020 align:start position:0% up with the first asynchronous probabilistic<00:20:13.440> liveness<00:20:13.830> strategy<00:20:14.430> for<00:20:14.730> CBC 00:20:15.020 --> 00:20:15.030 align:start position:0% probabilistic liveness strategy for CBC 00:20:15.030 --> 00:20:20.000 align:start position:0% probabilistic liveness strategy for CBC Kasper<00:20:16.640> which<00:20:17.640> is<00:20:18.470> you<00:20:19.470> know<00:20:19.560> it's 00:20:20.000 --> 00:20:20.010 align:start position:0% Kasper which is you know it's 00:20:20.010 --> 00:20:22.340 align:start position:0% Kasper which is you know it's probabilistic<00:20:20.580> and<00:20:21.090> then<00:20:21.570> it<00:20:21.750> uses<00:20:21.900> a<00:20:22.020> common 00:20:22.340 --> 00:20:22.350 align:start position:0% probabilistic and then it uses a common 00:20:22.350 --> 00:20:23.840 align:start position:0% probabilistic and then it uses a common calling<00:20:22.590> model<00:20:22.920> or<00:20:23.190> basically<00:20:23.490> everyone's 00:20:23.840 --> 00:20:23.850 align:start position:0% calling model or basically everyone's 00:20:23.850 --> 00:20:25.250 align:start position:0% calling model or basically everyone's flipping<00:20:24.000> coins<00:20:24.390> and<00:20:24.660> then<00:20:24.810> eventually<00:20:25.050> they 00:20:25.250 --> 00:20:25.260 align:start position:0% flipping coins and then eventually they 00:20:25.260 --> 00:20:26.420 align:start position:0% flipping coins and then eventually they all<00:20:25.350> float<00:20:25.500> the<00:20:25.590> same<00:20:25.740> coin<00:20:25.920> and<00:20:26.130> ends<00:20:26.340> up 00:20:26.420 --> 00:20:26.430 align:start position:0% all float the same coin and ends up 00:20:26.430 --> 00:20:32.420 align:start position:0% all float the same coin and ends up being<00:20:26.460> live<00:20:30.200> the<00:20:31.200> first<00:20:31.500> partial<00:20:31.830> synchrony 00:20:32.420 --> 00:20:32.430 align:start position:0% being live the first partial synchrony 00:20:32.430 --> 00:20:34.250 align:start position:0% being live the first partial synchrony thing<00:20:32.970> first<00:20:33.570> of<00:20:33.600> all<00:20:33.690> first<00:20:34.050> partial 00:20:34.250 --> 00:20:34.260 align:start position:0% thing first of all first partial 00:20:34.260 --> 00:20:36.740 align:start position:0% thing first of all first partial synchrony<00:20:34.650> specification<00:20:35.190> for<00:20:35.280> CBC<00:20:35.520> Kasper<00:20:35.910> I 00:20:36.740 --> 00:20:36.750 align:start position:0% synchrony specification for CBC Kasper I 00:20:36.750 --> 00:20:40.130 align:start position:0% synchrony specification for CBC Kasper I came<00:20:37.050> up<00:20:37.140> with<00:20:37.170> in<00:20:37.320> july<00:20:37.800> 2019<00:20:38.450> and<00:20:39.450> and<00:20:39.990> this 00:20:40.130 --> 00:20:40.140 align:start position:0% came up with in july 2019 and and this 00:20:40.140 --> 00:20:42.920 align:start position:0% came up with in july 2019 and and this was<00:20:40.730> also<00:20:41.730> based<00:20:41.940> on<00:20:42.060> fault<00:20:42.300> detection<00:20:42.420> but 00:20:42.920 --> 00:20:42.930 align:start position:0% was also based on fault detection but 00:20:42.930 --> 00:20:44.300 align:start position:0% was also based on fault detection but now<00:20:43.080> instead<00:20:43.320> of<00:20:43.500> faults<00:20:43.830> being<00:20:44.010> perfectly 00:20:44.300 --> 00:20:44.310 align:start position:0% now instead of faults being perfectly 00:20:44.310 --> 00:20:45.950 align:start position:0% now instead of faults being perfectly reliably<00:20:44.790> detectable<00:20:45.330> as<00:20:45.480> in<00:20:45.600> synchrony 00:20:45.950 --> 00:20:45.960 align:start position:0% reliably detectable as in synchrony 00:20:45.960 --> 00:20:48.110 align:start position:0% reliably detectable as in synchrony they're<00:20:46.410> not<00:20:46.680> and<00:20:46.980> so<00:20:47.190> it's<00:20:47.490> quite<00:20:47.820> a<00:20:47.880> lot<00:20:48.030> more 00:20:48.110 --> 00:20:48.120 align:start position:0% they're not and so it's quite a lot more 00:20:48.120 --> 00:20:52.070 align:start position:0% they're not and so it's quite a lot more complicated<00:20:48.660> and<00:20:49.160> then<00:20:50.160> the<00:20:50.700> oh<00:20:51.540> we<00:20:51.840> got<00:20:51.960> the 00:20:52.070 --> 00:20:52.080 align:start position:0% complicated and then the oh we got the 00:20:52.080 --> 00:20:56.390 align:start position:0% complicated and then the oh we got the first<00:20:52.430> formal<00:20:53.430> verification<00:20:53.580> of<00:20:55.280> safety<00:20:56.280> and 00:20:56.390 --> 00:20:56.400 align:start position:0% first formal verification of safety and 00:20:56.400 --> 00:20:58.880 align:start position:0% first formal verification of safety and on<00:20:56.490> triviality<00:20:57.000> of<00:20:57.030> the<00:20:57.360> full<00:20:57.720> and<00:20:58.020> light 00:20:58.880 --> 00:20:58.890 align:start position:0% on triviality of the full and light 00:20:58.890 --> 00:21:01.820 align:start position:0% on triviality of the full and light client<00:20:59.250> for<00:20:59.370> the<00:20:59.430> abstract<00:20:59.820> one<00:21:00.530> this<00:21:01.530> is<00:21:01.680> done 00:21:01.820 --> 00:21:01.830 align:start position:0% client for the abstract one this is done 00:21:01.830 --> 00:21:05.810 align:start position:0% client for the abstract one this is done by<00:21:01.980> runtime<00:21:02.310> verification<00:21:03.470> loading<00:21:04.470> a<00:21:05.430> bunch 00:21:05.810 --> 00:21:05.820 align:start position:0% by runtime verification loading a bunch 00:21:05.820 --> 00:21:07.520 align:start position:0% by runtime verification loading a bunch of<00:21:05.910> people<00:21:06.120> who<00:21:06.180> you're<00:21:06.270> gonna<00:21:06.390> see<00:21:07.140> listed 00:21:07.520 --> 00:21:07.530 align:start position:0% of people who you're gonna see listed 00:21:07.530 --> 00:21:10.160 align:start position:0% of people who you're gonna see listed later<00:21:07.740> so<00:21:07.980> I<00:21:08.010> don't<00:21:08.220> know<00:21:08.970> just<00:21:09.480> a<00:21:09.540> little<00:21:09.960> time 00:21:10.160 --> 00:21:10.170 align:start position:0% later so I don't know just a little time 00:21:10.170 --> 00:21:14.240 align:start position:0% later so I don't know just a little time here<00:21:10.580> the<00:21:11.580> we<00:21:12.570> also<00:21:12.690> had<00:21:13.020> the<00:21:13.380> same<00:21:13.560> same<00:21:14.040> and 00:21:14.240 --> 00:21:14.250 align:start position:0% here the we also had the same same and 00:21:14.250 --> 00:21:15.560 align:start position:0% here the we also had the same same and same<00:21:14.370> month<00:21:14.610> of<00:21:14.850> first<00:21:15.150> formal<00:21:15.420> verification 00:21:15.560 --> 00:21:15.570 align:start position:0% same month of first formal verification 00:21:15.570 --> 00:21:20.000 align:start position:0% same month of first formal verification of<00:21:16.310> efficient<00:21:17.780> safety<00:21:18.780> safety<00:21:19.500> Oracle 00:21:20.000 --> 00:21:20.010 align:start position:0% of efficient safety safety Oracle 00:21:20.010 --> 00:21:21.890 align:start position:0% of efficient safety safety Oracle detection<00:21:20.400> by<00:21:20.520> Maria<00:21:20.820> Nakamura<00:21:21.390> who<00:21:21.540> was<00:21:21.660> here 00:21:21.890 --> 00:21:21.900 align:start position:0% detection by Maria Nakamura who was here 00:21:21.900 --> 00:21:26.540 align:start position:0% detection by Maria Nakamura who was here also<00:21:22.490> and<00:21:24.620> also<00:21:25.620> we<00:21:25.770> had<00:21:25.950> in<00:21:26.070> the<00:21:26.130> same<00:21:26.310> month 00:21:26.540 --> 00:21:26.550 align:start position:0% also and also we had in the same month 00:21:26.550 --> 00:21:29.030 align:start position:0% also and also we had in the same month the<00:21:27.360> first<00:21:28.230> partially<00:21:28.650> synchronous 00:21:29.030 --> 00:21:29.040 align:start position:0% the first partially synchronous 00:21:29.040 --> 00:21:31.120 align:start position:0% the first partially synchronous specifications<00:21:29.670> for<00:21:29.880> the<00:21:30.180> leader<00:21:30.540> protocols 00:21:31.120 --> 00:21:31.130 align:start position:0% specifications for the leader protocols 00:21:31.130 --> 00:21:35.860 align:start position:0% specifications for the leader protocols that<00:21:32.130> Daniel<00:21:32.460> came<00:21:32.670> basically<00:21:33.660> pioneered<00:21:34.760> and 00:21:35.860 --> 00:21:35.870 align:start position:0% that Daniel came basically pioneered and 00:21:35.870 --> 00:21:38.540 align:start position:0% that Daniel came basically pioneered and that's<00:21:36.870> kind<00:21:37.260> of<00:21:37.320> all<00:21:37.470> the<00:21:37.740> major<00:21:37.950> roadmaps 00:21:38.540 --> 00:21:38.550 align:start position:0% that's kind of all the major roadmaps 00:21:38.550 --> 00:21:40.940 align:start position:0% that's kind of all the major roadmaps maybe<00:21:39.270> even<00:21:39.540> milestones<00:21:40.230> on<00:21:40.320> the<00:21:40.410> roadmap<00:21:40.560> and 00:21:40.940 --> 00:21:40.950 align:start position:0% maybe even milestones on the roadmap and 00:21:40.950 --> 00:21:44.200 align:start position:0% maybe even milestones on the roadmap and maybe<00:21:41.310> if<00:21:41.700> not<00:21:42.000> all<00:21:42.150> almost<00:21:42.450> all<00:21:42.750> until<00:21:43.590> today 00:21:44.200 --> 00:21:44.210 align:start position:0% maybe if not all almost all until today 00:21:44.210 --> 00:21:47.270 align:start position:0% maybe if not all almost all until today but<00:21:45.210> we<00:21:45.270> have<00:21:45.300> a<00:21:45.420> lot<00:21:45.570> of<00:21:45.600> future<00:21:45.930> work<00:21:46.160> we<00:21:47.160> have 00:21:47.270 --> 00:21:47.280 align:start position:0% but we have a lot of future work we have 00:21:47.280 --> 00:21:48.800 align:start position:0% but we have a lot of future work we have to<00:21:47.370> continue<00:21:48.000> a<00:21:48.030> lot<00:21:48.240> of<00:21:48.360> stuff<00:21:48.510> that<00:21:48.540> we<00:21:48.720> were 00:21:48.800 --> 00:21:48.810 align:start position:0% to continue a lot of stuff that we were 00:21:48.810 --> 00:21:50.390 align:start position:0% to continue a lot of stuff that we were doing<00:21:48.840> a<00:21:49.320> lot<00:21:49.470> of<00:21:49.590> stuff<00:21:49.710> that<00:21:49.830> we've<00:21:49.950> done<00:21:50.130> you 00:21:50.390 --> 00:21:50.400 align:start position:0% doing a lot of stuff that we've done you 00:21:50.400 --> 00:21:51.530 align:start position:0% doing a lot of stuff that we've done you may<00:21:50.580> be<00:21:50.640> to<00:21:50.790> notice<00:21:51.060> that<00:21:51.180> I<00:21:51.240> haven't 00:21:51.530 --> 00:21:51.540 align:start position:0% may be to notice that I haven't 00:21:51.540 --> 00:21:53.480 align:start position:0% may be to notice that I haven't published<00:21:51.660> in<00:21:52.080> you<00:21:52.740> know<00:21:52.830> you<00:21:52.890> haven't<00:21:53.130> seen 00:21:53.480 --> 00:21:53.490 align:start position:0% published in you know you haven't seen 00:21:53.490 --> 00:21:56.360 align:start position:0% published in you know you haven't seen yet<00:21:53.990> so<00:21:54.990> we<00:21:55.080> need<00:21:55.110> to<00:21:55.320> you<00:21:55.590> know<00:21:55.680> means<00:21:56.130> some 00:21:56.360 --> 00:21:56.370 align:start position:0% yet so we need to you know means some 00:21:56.370 --> 00:21:57.350 align:start position:0% yet so we need to you know means some some<00:21:56.700> of<00:21:56.760> this<00:21:56.820> stuff<00:21:57.000> needs<00:21:57.270> to<00:21:57.300> be 00:21:57.350 --> 00:21:57.360 align:start position:0% some of this stuff needs to be 00:21:57.360 --> 00:21:59.630 align:start position:0% some of this stuff needs to be formalized<00:21:57.870> that's<00:21:58.380> abstracted<00:21:59.130> verified 00:21:59.630 --> 00:21:59.640 align:start position:0% formalized that's abstracted verified 00:21:59.640 --> 00:22:00.260 align:start position:0% formalized that's abstracted verified you 00:22:00.260 --> 00:22:00.270 align:start position:0% you 00:22:00.270 --> 00:22:02.290 align:start position:0% you it's<00:22:00.450> not<00:22:00.600> really<00:22:00.929> clear<00:22:00.960> if<00:22:01.410> all<00:22:01.559> of<00:22:01.650> this<00:22:01.770> is 00:22:02.290 --> 00:22:02.300 align:start position:0% it's not really clear if all of this is 00:22:02.300 --> 00:22:05.930 align:start position:0% it's not really clear if all of this is you<00:22:03.300> know<00:22:03.390> like<00:22:04.290> we<00:22:04.710> haven't<00:22:04.950> really<00:22:05.190> done<00:22:05.400> the 00:22:05.930 --> 00:22:05.940 align:start position:0% you know like we haven't really done the 00:22:05.940 --> 00:22:08.330 align:start position:0% you know like we haven't really done the kinds<00:22:06.450> of<00:22:06.510> verification<00:22:07.230> that<00:22:07.350> we<00:22:07.440> love<00:22:07.740> to 00:22:08.330 --> 00:22:08.340 align:start position:0% kinds of verification that we love to 00:22:08.340 --> 00:22:10.460 align:start position:0% kinds of verification that we love to have<00:22:08.520> we're<00:22:09.480> like<00:22:09.750> you're<00:22:09.990> paranoid 00:22:10.460 --> 00:22:10.470 align:start position:0% have we're like you're paranoid 00:22:10.470 --> 00:22:12.230 align:start position:0% have we're like you're paranoid absolutely<00:22:11.070> sure<00:22:11.280> under<00:22:11.580> any<00:22:11.730> circumstance 00:22:12.230 --> 00:22:12.240 align:start position:0% absolutely sure under any circumstance 00:22:12.240 --> 00:22:14.390 align:start position:0% absolutely sure under any circumstance that<00:22:12.330> it's<00:22:12.540> correct<00:22:12.840> with<00:22:13.230> all<00:22:13.380> of<00:22:13.470> it<00:22:13.590> we<00:22:14.250> also 00:22:14.390 --> 00:22:14.400 align:start position:0% that it's correct with all of it we also 00:22:14.400 --> 00:22:17.630 align:start position:0% that it's correct with all of it we also have<00:22:14.640> to<00:22:14.850> you<00:22:15.120> know<00:22:15.740> abstract<00:22:16.740> it<00:22:16.980> and<00:22:17.160> so<00:22:17.490> you 00:22:17.630 --> 00:22:17.640 align:start position:0% have to you know abstract it and so you 00:22:17.640 --> 00:22:19.190 align:start position:0% have to you know abstract it and so you have<00:22:17.790> like<00:22:17.970> the<00:22:18.000> results<00:22:18.630> that<00:22:18.720> we<00:22:18.809> have<00:22:18.960> in 00:22:19.190 --> 00:22:19.200 align:start position:0% have like the results that we have in 00:22:19.200 --> 00:22:21.260 align:start position:0% have like the results that we have in the<00:22:19.260> most<00:22:19.410> general<00:22:19.800> terms<00:22:19.980> possible<00:22:20.309> so<00:22:21.090> that 00:22:21.260 --> 00:22:21.270 align:start position:0% the most general terms possible so that 00:22:21.270 --> 00:22:22.880 align:start position:0% the most general terms possible so that where<00:22:21.450> they're<00:22:21.630> as<00:22:21.720> useful<00:22:21.900> as<00:22:22.110> possible<00:22:22.470> for 00:22:22.880 --> 00:22:22.890 align:start position:0% where they're as useful as possible for 00:22:22.890 --> 00:22:25.130 align:start position:0% where they're as useful as possible for providing<00:22:23.490> the<00:22:23.580> most<00:22:23.670> general<00:22:24.300> architecture 00:22:25.130 --> 00:22:25.140 align:start position:0% providing the most general architecture 00:22:25.140 --> 00:22:26.540 align:start position:0% providing the most general architecture in<00:22:25.230> Beckman<00:22:25.530> which<00:22:26.070> which<00:22:26.280> basically 00:22:26.540 --> 00:22:26.550 align:start position:0% in Beckman which which basically 00:22:26.550 --> 00:22:27.740 align:start position:0% in Beckman which which basically provides<00:22:26.880> the<00:22:26.970> guarantees<00:22:27.300> the<00:22:27.540> most 00:22:27.740 --> 00:22:27.750 align:start position:0% provides the guarantees the most 00:22:27.750 --> 00:22:30.680 align:start position:0% provides the guarantees the most possible<00:22:28.200> implementations<00:22:29.450> and<00:22:30.450> we<00:22:30.540> also 00:22:30.680 --> 00:22:30.690 align:start position:0% possible implementations and we also 00:22:30.690 --> 00:22:32.180 align:start position:0% possible implementations and we also have<00:22:30.809> to<00:22:30.900> do<00:22:31.020> a<00:22:31.260> lot<00:22:31.440> of<00:22:31.530> documentation<00:22:31.980> and 00:22:32.180 --> 00:22:32.190 align:start position:0% have to do a lot of documentation and 00:22:32.190 --> 00:22:35.990 align:start position:0% have to do a lot of documentation and peer<00:22:32.400> review<00:22:32.580> of<00:22:32.610> past<00:22:33.179> work<00:22:34.280> you<00:22:35.280> know<00:22:35.370> you 00:22:35.990 --> 00:22:36.000 align:start position:0% peer review of past work you know you 00:22:36.000 --> 00:22:38.090 align:start position:0% peer review of past work you know you know<00:22:36.120> I<00:22:36.300> claim<00:22:36.660> we've<00:22:37.200> done<00:22:37.440> but<00:22:37.860> you<00:22:38.010> guys 00:22:38.090 --> 00:22:38.100 align:start position:0% know I claim we've done but you guys 00:22:38.100 --> 00:22:40.810 align:start position:0% know I claim we've done but you guys can't<00:22:38.370> really<00:22:38.580> tell<00:22:39.020> at<00:22:40.020> this<00:22:40.170> point<00:22:40.440> really 00:22:40.810 --> 00:22:40.820 align:start position:0% can't really tell at this point really 00:22:40.820 --> 00:22:45.380 align:start position:0% can't really tell at this point really not<00:22:41.820> that<00:22:41.970> much<00:22:43.730> here's<00:22:44.730> some<00:22:44.880> more<00:22:44.970> past<00:22:45.210> work 00:22:45.380 --> 00:22:45.390 align:start position:0% not that much here's some more past work 00:22:45.390 --> 00:22:47.169 align:start position:0% not that much here's some more past work you<00:22:45.600> know<00:22:45.690> validator<00:22:46.559> rotation 00:22:47.169 --> 00:22:47.179 align:start position:0% you know validator rotation 00:22:47.179 --> 00:22:49.520 align:start position:0% you know validator rotation load-balancing<00:22:48.200> charting<00:22:49.200> client 00:22:49.520 --> 00:22:49.530 align:start position:0% load-balancing charting client 00:22:49.530 --> 00:22:50.600 align:start position:0% load-balancing charting client strategies<00:22:49.980> these<00:22:50.250> are<00:22:50.340> these<00:22:50.460> are<00:22:50.580> things 00:22:50.600 --> 00:22:50.610 align:start position:0% strategies these are these are things 00:22:50.610 --> 00:22:53.570 align:start position:0% strategies these are these are things that<00:22:50.850> are<00:22:51.600> not<00:22:52.200> done<00:22:52.410> but<00:22:53.280> which<00:22:53.429> are 00:22:53.570 --> 00:22:53.580 align:start position:0% that are not done but which are 00:22:53.580 --> 00:22:55.940 align:start position:0% that are not done but which are necessary<00:22:53.790> for<00:22:54.150> the<00:22:54.650> scalable<00:22:55.650> proof<00:22:55.800> of 00:22:55.940 --> 00:22:55.950 align:start position:0% necessary for the scalable proof of 00:22:55.950 --> 00:22:57.470 align:start position:0% necessary for the scalable proof of steak<00:22:56.160> or<00:22:56.370> scalable<00:22:56.790> distributed<00:22:56.910> system 00:22:57.470 --> 00:22:57.480 align:start position:0% steak or scalable distributed system 00:22:57.480 --> 00:23:02.270 align:start position:0% steak or scalable distributed system think<00:22:58.940> you<00:22:59.940> know<00:23:00.030> also<00:23:00.210> is<00:23:00.630> and<00:23:01.410> you<00:23:01.920> know<00:23:02.040> I 00:23:02.270 --> 00:23:02.280 align:start position:0% think you know also is and you know I 00:23:02.280 --> 00:23:04.070 align:start position:0% think you know also is and you know I would<00:23:02.460> say<00:23:02.580> that<00:23:02.700> we<00:23:02.790> have<00:23:03.000> we<00:23:03.330> have<00:23:03.360> I<00:23:03.750> mean<00:23:03.870> we 00:23:04.070 --> 00:23:04.080 align:start position:0% would say that we have we have I mean we 00:23:04.080 --> 00:23:06.470 align:start position:0% would say that we have we have I mean we have<00:23:04.230> solutions<00:23:05.130> to<00:23:05.250> some<00:23:05.610> extent<00:23:06.059> but<00:23:06.270> it's 00:23:06.470 --> 00:23:06.480 align:start position:0% have solutions to some extent but it's 00:23:06.480 --> 00:23:10.220 align:start position:0% have solutions to some extent but it's not<00:23:06.750> fully<00:23:08.210> you<00:23:09.210> know<00:23:09.240> at<00:23:09.660> the<00:23:09.809> level<00:23:10.080> of 00:23:10.220 --> 00:23:10.230 align:start position:0% not fully you know at the level of 00:23:10.230 --> 00:23:12.650 align:start position:0% not fully you know at the level of formality<00:23:10.700> completeness<00:23:11.700> etc<00:23:12.420> that<00:23:12.570> were 00:23:12.650 --> 00:23:12.660 align:start position:0% formality completeness etc that were 00:23:12.660 --> 00:23:17.030 align:start position:0% formality completeness etc that were used<00:23:12.870> to<00:23:12.960> in<00:23:13.140> that<00:23:13.290> we<00:23:13.380> expect<00:23:15.679> we<00:23:16.679> also<00:23:16.860> have 00:23:17.030 --> 00:23:17.040 align:start position:0% used to in that we expect we also have 00:23:17.040 --> 00:23:19.730 align:start position:0% used to in that we expect we also have like<00:23:17.280> just<00:23:17.700> future<00:23:17.940> work<00:23:18.240> that<00:23:18.540> is<00:23:18.870> just 00:23:19.730 --> 00:23:19.740 align:start position:0% like just future work that is just 00:23:19.740 --> 00:23:21.640 align:start position:0% like just future work that is just hasn't<00:23:20.040> really<00:23:20.190> been<00:23:20.309> started<00:23:20.670> that<00:23:20.790> much<00:23:20.970> yet 00:23:21.640 --> 00:23:21.650 align:start position:0% hasn't really been started that much yet 00:23:21.650 --> 00:23:24.260 align:start position:0% hasn't really been started that much yet abstraction<00:23:22.650> all<00:23:23.220> the<00:23:23.340> liveness<00:23:23.520> stuff<00:23:23.880> you 00:23:24.260 --> 00:23:24.270 align:start position:0% abstraction all the liveness stuff you 00:23:24.270 --> 00:23:25.100 align:start position:0% abstraction all the liveness stuff you know<00:23:24.360> right<00:23:24.510> now<00:23:24.600> we<00:23:24.660> have<00:23:24.780> like<00:23:24.870> a<00:23:24.900> few 00:23:25.100 --> 00:23:25.110 align:start position:0% know right now we have like a few 00:23:25.110 --> 00:23:26.840 align:start position:0% know right now we have like a few specific<00:23:25.290> live<00:23:25.650> protocols<00:23:26.100> we<00:23:26.640> don't<00:23:26.760> really 00:23:26.840 --> 00:23:26.850 align:start position:0% specific live protocols we don't really 00:23:26.850 --> 00:23:28.280 align:start position:0% specific live protocols we don't really have<00:23:27.030> that<00:23:27.059> much<00:23:27.330> of<00:23:27.510> general<00:23:27.780> infrastructure 00:23:28.280 --> 00:23:28.290 align:start position:0% have that much of general infrastructure 00:23:28.290 --> 00:23:29.780 align:start position:0% have that much of general infrastructure for<00:23:28.500> generating<00:23:28.860> live<00:23:29.070> consensus<00:23:29.460> protocols 00:23:29.780 --> 00:23:29.790 align:start position:0% for generating live consensus protocols 00:23:29.790 --> 00:23:31.700 align:start position:0% for generating live consensus protocols but<00:23:30.600> we'd<00:23:30.720> like<00:23:30.840> to<00:23:30.900> abstract<00:23:31.230> all<00:23:31.500> of<00:23:31.620> our 00:23:31.700 --> 00:23:31.710 align:start position:0% but we'd like to abstract all of our 00:23:31.710 --> 00:23:33.770 align:start position:0% but we'd like to abstract all of our liveness<00:23:31.950> research<00:23:32.700> so<00:23:33.030> we<00:23:33.179> could<00:23:33.300> have<00:23:33.420> the 00:23:33.770 --> 00:23:33.780 align:start position:0% liveness research so we could have the 00:23:33.780 --> 00:23:36.410 align:start position:0% liveness research so we could have the most<00:23:33.929> general<00:23:34.230> in<00:23:34.440> structure<00:23:34.800> possible<00:23:35.420> we 00:23:36.410 --> 00:23:36.420 align:start position:0% most general in structure possible we 00:23:36.420 --> 00:23:37.460 align:start position:0% most general in structure possible we have<00:23:36.450> to<00:23:36.570> verify<00:23:36.809> all<00:23:37.110> of<00:23:37.200> our<00:23:37.320> liveness 00:23:37.460 --> 00:23:37.470 align:start position:0% have to verify all of our liveness 00:23:37.470 --> 00:23:38.000 align:start position:0% have to verify all of our liveness proofs 00:23:38.000 --> 00:23:38.010 align:start position:0% proofs 00:23:38.010 --> 00:23:40.640 align:start position:0% proofs you<00:23:38.429> know<00:23:38.550> both<00:23:38.910> by<00:23:39.179> hand<00:23:39.510> and<00:23:39.780> formally<00:23:40.350> to 00:23:40.640 --> 00:23:40.650 align:start position:0% you know both by hand and formally to 00:23:40.650 --> 00:23:43.040 align:start position:0% you know both by hand and formally to the<00:23:40.679> much<00:23:41.580> bigger<00:23:41.850> and<00:23:42.059> more<00:23:42.150> extent<00:23:42.809> than<00:23:42.960> we 00:23:43.040 --> 00:23:43.050 align:start position:0% the much bigger and more extent than we 00:23:43.050 --> 00:23:45.110 align:start position:0% the much bigger and more extent than we have<00:23:43.200> already<00:23:43.460> and<00:23:44.460> we<00:23:44.550> want<00:23:44.730> to<00:23:44.850> talk<00:23:44.970> about 00:23:45.110 --> 00:23:45.120 align:start position:0% have already and we want to talk about 00:23:45.120 --> 00:23:46.250 align:start position:0% have already and we want to talk about performance<00:23:45.450> you<00:23:45.720> know<00:23:45.780> we<00:23:45.900> mentioned 00:23:46.250 --> 00:23:46.260 align:start position:0% performance you know we mentioned 00:23:46.260 --> 00:23:48.200 align:start position:0% performance you know we mentioned earlier<00:23:46.679> that<00:23:46.950> like<00:23:47.070> we<00:23:47.700> want<00:23:47.880> to<00:23:47.940> have<00:23:48.120> the 00:23:48.200 --> 00:23:48.210 align:start position:0% earlier that like we want to have the 00:23:48.210 --> 00:23:50.000 align:start position:0% earlier that like we want to have the same<00:23:48.420> network<00:23:48.960> overhead<00:23:49.260> as<00:23:49.559> nakamoto 00:23:50.000 --> 00:23:50.010 align:start position:0% same network overhead as nakamoto 00:23:50.010 --> 00:23:52.640 align:start position:0% same network overhead as nakamoto consensus<00:23:50.520> and<00:23:51.000> you<00:23:51.720> know<00:23:51.809> there's<00:23:52.410> there's 00:23:52.640 --> 00:23:52.650 align:start position:0% consensus and you know there's there's 00:23:52.650 --> 00:23:54.440 align:start position:0% consensus and you know there's there's all<00:23:52.740> sorts<00:23:52.950> of<00:23:52.980> other<00:23:53.300> considerations<00:23:54.300> for 00:23:54.440 --> 00:23:54.450 align:start position:0% all sorts of other considerations for 00:23:54.450 --> 00:23:56.060 align:start position:0% all sorts of other considerations for performance<00:23:54.929> like<00:23:55.170> for<00:23:55.320> example<00:23:55.380> the<00:23:55.710> latency 00:23:56.060 --> 00:23:56.070 align:start position:0% performance like for example the latency 00:23:56.070 --> 00:23:58.520 align:start position:0% performance like for example the latency to<00:23:56.100> finality<00:23:56.670> the<00:23:57.000> latency<00:23:57.480> to<00:23:57.720> inclusion<00:23:58.440> in 00:23:58.520 --> 00:23:58.530 align:start position:0% to finality the latency to inclusion in 00:23:58.530 --> 00:23:59.419 align:start position:0% to finality the latency to inclusion in the<00:23:58.590> first<00:23:58.770> block<00:23:59.010> which<00:23:59.190> under<00:23:59.400> normal 00:23:59.419 --> 00:23:59.429 align:start position:0% the first block which under normal 00:23:59.429 --> 00:24:03.140 align:start position:0% the first block which under normal execution<00:24:00.330> is<00:24:00.510> later<00:24:01.080> finalized<00:24:02.030> you<00:24:03.030> know 00:24:03.140 --> 00:24:03.150 align:start position:0% execution is later finalized you know 00:24:03.150 --> 00:24:05.780 align:start position:0% execution is later finalized you know the<00:24:03.270> number<00:24:03.510> of<00:24:03.750> like<00:24:04.140> operations<00:24:05.100> per<00:24:05.370> second 00:24:05.780 --> 00:24:05.790 align:start position:0% the number of like operations per second 00:24:05.790 --> 00:24:07.010 align:start position:0% the number of like operations per second that<00:24:06.030> you<00:24:06.120> need<00:24:06.240> to<00:24:06.330> do<00:24:06.450> like<00:24:06.480> in<00:24:06.780> terms<00:24:06.929> of 00:24:07.010 --> 00:24:07.020 align:start position:0% that you need to do like in terms of 00:24:07.020 --> 00:24:09.710 align:start position:0% that you need to do like in terms of signature<00:24:07.500> verification<00:24:07.730> and<00:24:08.730> like<00:24:09.030> compute 00:24:09.710 --> 00:24:09.720 align:start position:0% signature verification and like compute 00:24:09.720 --> 00:24:12.500 align:start position:0% signature verification and like compute there's<00:24:10.410> as<00:24:10.740> well<00:24:10.980> as<00:24:11.130> like<00:24:11.280> the<00:24:11.460> the<00:24:11.940> overhead 00:24:12.500 --> 00:24:12.510 align:start position:0% there's as well as like the the overhead 00:24:12.510 --> 00:24:13.020 align:start position:0% there's as well as like the the overhead the 00:24:13.020 --> 00:24:13.030 align:start position:0% the 00:24:13.030 --> 00:24:14.190 align:start position:0% the message<00:24:13.240> overhead<00:24:13.540> which<00:24:13.720> is<00:24:13.840> kind<00:24:14.020> of<00:24:14.050> what<00:24:14.170> I 00:24:14.190 --> 00:24:14.200 align:start position:0% message overhead which is kind of what I 00:24:14.200 --> 00:24:15.300 align:start position:0% message overhead which is kind of what I was<00:24:14.290> referring<00:24:14.560> to<00:24:14.680> and<00:24:14.890> I'm<00:24:14.950> thinking<00:24:15.160> about 00:24:15.300 --> 00:24:15.310 align:start position:0% was referring to and I'm thinking about 00:24:15.310 --> 00:24:17.010 align:start position:0% was referring to and I'm thinking about the<00:24:15.580> overhead<00:24:15.880> of<00:24:15.910> Nakamoto<00:24:16.330> consensus<00:24:16.840> I 00:24:17.010 --> 00:24:17.020 align:start position:0% the overhead of Nakamoto consensus I 00:24:17.020 --> 00:24:18.660 align:start position:0% the overhead of Nakamoto consensus I wasn't<00:24:17.560> about<00:24:17.680> mining<00:24:18.070> there's<00:24:18.430> thing<00:24:18.580> about 00:24:18.660 --> 00:24:18.670 align:start position:0% wasn't about mining there's thing about 00:24:18.670 --> 00:24:19.980 align:start position:0% wasn't about mining there's thing about the<00:24:18.790> clients<00:24:19.210> and<00:24:19.330> how<00:24:19.570> they<00:24:19.660> just<00:24:19.810> have<00:24:19.900> to 00:24:19.980 --> 00:24:19.990 align:start position:0% the clients and how they just have to 00:24:19.990 --> 00:24:22.080 align:start position:0% the clients and how they just have to download<00:24:20.170> like<00:24:20.440> one<00:24:20.620> header<00:24:21.370> per<00:24:21.610> block<00:24:21.850> or 00:24:22.080 --> 00:24:22.090 align:start position:0% download like one header per block or 00:24:22.090 --> 00:24:25.620 align:start position:0% download like one header per block or very<00:24:22.330> little<00:24:22.570> information<00:24:24.150> you<00:24:25.150> know<00:24:25.210> we<00:24:25.540> have 00:24:25.620 --> 00:24:25.630 align:start position:0% very little information you know we have 00:24:25.630 --> 00:24:27.390 align:start position:0% very little information you know we have Club<00:24:25.870> we<00:24:26.020> have<00:24:26.140> a<00:24:26.170> CBC<00:24:26.770> Casper<00:24:27.070> we<00:24:27.220> have<00:24:27.310> this 00:24:27.390 --> 00:24:27.400 align:start position:0% Club we have a CBC Casper we have this 00:24:27.400 --> 00:24:28.770 align:start position:0% Club we have a CBC Casper we have this requirement<00:24:27.670> that<00:24:28.060> it<00:24:28.270> at<00:24:28.480> the<00:24:28.540> protocol 00:24:28.770 --> 00:24:28.780 align:start position:0% requirement that it at the protocol 00:24:28.780 --> 00:24:29.910 align:start position:0% requirement that it at the protocol fault<00:24:29.080> that<00:24:29.350> the<00:24:29.440> fault<00:24:29.800> tolerance 00:24:29.910 --> 00:24:29.920 align:start position:0% fault that the fault tolerance 00:24:29.920 --> 00:24:31.950 align:start position:0% fault that the fault tolerance thresholds<00:24:30.490> of<00:24:30.520> the<00:24:30.610> protocol<00:24:30.970> are<00:24:31.420> not<00:24:31.690> in 00:24:31.950 --> 00:24:31.960 align:start position:0% thresholds of the protocol are not in 00:24:31.960 --> 00:24:34.320 align:start position:0% thresholds of the protocol are not in the<00:24:32.230> consensus<00:24:32.560> protocol<00:24:32.920> but<00:24:33.730> their<00:24:33.880> client 00:24:34.320 --> 00:24:34.330 align:start position:0% the consensus protocol but their client 00:24:34.330 --> 00:24:36.240 align:start position:0% the consensus protocol but their client and<00:24:34.450> validator<00:24:35.020> side<00:24:35.260> and<00:24:35.560> so<00:24:36.040> we<00:24:36.100> have<00:24:36.190> to 00:24:36.240 --> 00:24:36.250 align:start position:0% and validator side and so we have to 00:24:36.250 --> 00:24:38.430 align:start position:0% and validator side and so we have to give<00:24:36.400> strategies<00:24:36.910> for<00:24:37.180> clients<00:24:37.540> or<00:24:38.080> give<00:24:38.290> at 00:24:38.430 --> 00:24:38.440 align:start position:0% give strategies for clients or give at 00:24:38.440 --> 00:24:39.840 align:start position:0% give strategies for clients or give at least<00:24:38.470> some<00:24:38.710> best<00:24:38.890> practices<00:24:39.280> for<00:24:39.460> clients 00:24:39.840 --> 00:24:39.850 align:start position:0% least some best practices for clients 00:24:39.850 --> 00:24:42.390 align:start position:0% least some best practices for clients for<00:24:40.300> choosing<00:24:40.570> these<00:24:40.840> thresholds<00:24:41.710> because 00:24:42.390 --> 00:24:42.400 align:start position:0% for choosing these thresholds because 00:24:42.400 --> 00:24:43.680 align:start position:0% for choosing these thresholds because not<00:24:42.580> all<00:24:42.790> thresholds<00:24:43.300> are<00:24:43.360> going<00:24:43.480> to<00:24:43.540> be 00:24:43.680 --> 00:24:43.690 align:start position:0% not all thresholds are going to be 00:24:43.690 --> 00:24:48.660 align:start position:0% not all thresholds are going to be equally<00:24:44.320> good<00:24:45.000> or<00:24:46.000> equally<00:24:46.330> useful<00:24:47.370> so<00:24:48.370> you 00:24:48.660 --> 00:24:48.670 align:start position:0% equally good or equally useful so you 00:24:48.670 --> 00:24:50.220 align:start position:0% equally good or equally useful so you know<00:24:48.760> this<00:24:49.120> is<00:24:49.240> like<00:24:49.390> Anna<00:24:49.600> just<00:24:49.930> a<00:24:50.050> whole 00:24:50.220 --> 00:24:50.230 align:start position:0% know this is like Anna just a whole 00:24:50.230 --> 00:24:51.630 align:start position:0% know this is like Anna just a whole bunch<00:24:50.350> of<00:24:50.500> stuff<00:24:51.100> that<00:24:51.130> needs<00:24:51.370> to<00:24:51.430> be<00:24:51.460> done 00:24:51.630 --> 00:24:51.640 align:start position:0% bunch of stuff that needs to be done 00:24:51.640 --> 00:24:52.920 align:start position:0% bunch of stuff that needs to be done there's<00:24:51.880> probably<00:24:52.240> more<00:24:52.450> future<00:24:52.750> work<00:24:52.900> that 00:24:52.920 --> 00:24:52.930 align:start position:0% there's probably more future work that 00:24:52.930 --> 00:24:56.820 align:start position:0% there's probably more future work that isn't<00:24:53.650> listed<00:24:53.800> here<00:24:54.100> but<00:24:54.840> but<00:24:55.840> but<00:24:56.200> if<00:24:56.380> this<00:24:56.560> if 00:24:56.820 --> 00:24:56.830 align:start position:0% isn't listed here but but but if this if 00:24:56.830 --> 00:24:59.160 align:start position:0% isn't listed here but but but if this if this<00:24:56.920> is<00:24:56.980> all<00:24:57.190> done<00:24:57.370> then<00:24:58.060> and<00:24:58.510> all<00:24:58.870> the<00:24:58.990> stuff 00:24:59.160 --> 00:24:59.170 align:start position:0% this is all done then and all the stuff 00:24:59.170 --> 00:25:00.360 align:start position:0% this is all done then and all the stuff that<00:24:59.260> we've<00:24:59.350> already<00:24:59.440> claimed<00:24:59.800> is<00:25:00.040> done<00:25:00.190> so 00:25:00.360 --> 00:25:00.370 align:start position:0% that we've already claimed is done so 00:25:00.370 --> 00:25:01.920 align:start position:0% that we've already claimed is done so far<00:25:00.580> as<00:25:00.730> done<00:25:00.910> thank<00:25:01.480> you<00:25:01.630> we're<00:25:01.750> pretty 00:25:01.920 --> 00:25:01.930 align:start position:0% far as done thank you we're pretty 00:25:01.930 --> 00:25:05.070 align:start position:0% far as done thank you we're pretty pretty<00:25:02.580> close<00:25:03.580> to<00:25:03.820> having<00:25:04.000> a<00:25:04.210> scalable 00:25:05.070 --> 00:25:05.080 align:start position:0% pretty close to having a scalable 00:25:05.080 --> 00:25:08.930 align:start position:0% pretty close to having a scalable distributed<00:25:06.660> consensus<00:25:07.660> protocol<00:25:08.110> that<00:25:08.320> has 00:25:08.930 --> 00:25:08.940 align:start position:0% distributed consensus protocol that has 00:25:08.940 --> 00:25:11.760 align:start position:0% distributed consensus protocol that has all<00:25:09.940> of<00:25:10.000> the<00:25:10.240> security<00:25:10.840> and<00:25:11.110> overhead 00:25:11.760 --> 00:25:11.770 align:start position:0% all of the security and overhead 00:25:11.770 --> 00:25:14.940 align:start position:0% all of the security and overhead properties<00:25:12.190> that<00:25:12.280> we<00:25:12.370> want<00:25:13.200> and<00:25:14.200> also<00:25:14.800> of 00:25:14.940 --> 00:25:14.950 align:start position:0% properties that we want and also of 00:25:14.950 --> 00:25:17.700 align:start position:0% properties that we want and also of libels<00:25:15.630> which<00:25:16.630> is<00:25:16.750> super<00:25:17.110> important<00:25:17.380> property 00:25:17.700 --> 00:25:17.710 align:start position:0% libels which is super important property 00:25:17.710 --> 00:25:20.670 align:start position:0% libels which is super important property that<00:25:18.030> is<00:25:19.030> shockingly<00:25:19.900> difficult<00:25:20.350> to<00:25:20.440> provide 00:25:20.670 --> 00:25:20.680 align:start position:0% that is shockingly difficult to provide 00:25:20.680 --> 00:25:24.870 align:start position:0% that is shockingly difficult to provide basically<00:25:21.610> have<00:25:21.760> to<00:25:21.850> prove<00:25:22.090> that<00:25:23.640> if<00:25:24.640> you 00:25:24.870 --> 00:25:24.880 align:start position:0% basically have to prove that if you 00:25:24.880 --> 00:25:27.120 align:start position:0% basically have to prove that if you exhaust<00:25:25.810> you<00:25:26.260> basically<00:25:26.530> have<00:25:26.770> to<00:25:26.860> prove<00:25:27.040> that 00:25:27.120 --> 00:25:27.130 align:start position:0% exhaust you basically have to prove that 00:25:27.130 --> 00:25:28.650 align:start position:0% exhaust you basically have to prove that there<00:25:27.280> is<00:25:27.400> no<00:25:27.610> way<00:25:27.760> to<00:25:27.820> execute<00:25:28.090> the<00:25:28.270> protocol 00:25:28.650 --> 00:25:28.660 align:start position:0% there is no way to execute the protocol 00:25:28.660 --> 00:25:29.640 align:start position:0% there is no way to execute the protocol that<00:25:28.840> doesn't<00:25:29.020> eventually<00:25:29.350> lead<00:25:29.500> to<00:25:29.530> the 00:25:29.640 --> 00:25:29.650 align:start position:0% that doesn't eventually lead to the 00:25:29.650 --> 00:25:31.110 align:start position:0% that doesn't eventually lead to the decision<00:25:30.070> easily<00:25:30.610> you<00:25:30.760> have<00:25:30.790> to<00:25:30.910> kind<00:25:31.060> of 00:25:31.110 --> 00:25:31.120 align:start position:0% decision easily you have to kind of 00:25:31.120 --> 00:25:32.850 align:start position:0% decision easily you have to kind of exhaust<00:25:31.480> every<00:25:31.960> single<00:25:32.290> possible<00:25:32.650> state 00:25:32.850 --> 00:25:32.860 align:start position:0% exhaust every single possible state 00:25:32.860 --> 00:25:34.710 align:start position:0% exhaust every single possible state transition<00:25:33.280> to<00:25:33.460> the<00:25:33.550> protocol<00:25:33.940> until<00:25:34.570> you're 00:25:34.710 --> 00:25:34.720 align:start position:0% transition to the protocol until you're 00:25:34.720 --> 00:25:37.200 align:start position:0% transition to the protocol until you're forced<00:25:35.230> to<00:25:35.590> make<00:25:35.890> it<00:25:35.920> to<00:25:36.190> make<00:25:36.310> a<00:25:36.340> decision<00:25:36.520> and 00:25:37.200 --> 00:25:37.210 align:start position:0% forced to make it to make a decision and 00:25:37.210 --> 00:25:38.970 align:start position:0% forced to make it to make a decision and that<00:25:37.540> turns<00:25:37.720> out<00:25:37.810> to<00:25:37.870> be<00:25:38.110> quite<00:25:38.620> a<00:25:38.740> difficult 00:25:38.970 --> 00:25:38.980 align:start position:0% that turns out to be quite a difficult 00:25:38.980 --> 00:25:43.710 align:start position:0% that turns out to be quite a difficult thing<00:25:39.370> to<00:25:39.610> argue<00:25:40.260> so<00:25:41.260> we<00:25:41.650> have<00:25:41.910> some<00:25:42.910> announces 00:25:43.710 --> 00:25:43.720 align:start position:0% thing to argue so we have some announces 00:25:43.720 --> 00:25:47.070 align:start position:0% thing to argue so we have some announces announcements<00:25:44.410> and<00:25:44.530> resources<00:25:44.980> to<00:25:45.100> share<00:25:46.080> so 00:25:47.070 --> 00:25:47.080 align:start position:0% announcements and resources to share so 00:25:47.080 --> 00:25:48.420 align:start position:0% announcements and resources to share so we're<00:25:47.710> collaborating<00:25:48.070> with<00:25:48.190> runtime 00:25:48.420 --> 00:25:48.430 align:start position:0% we're collaborating with runtime 00:25:48.430 --> 00:25:50.880 align:start position:0% we're collaborating with runtime verification<00:25:49.030> to<00:25:49.330> abstract<00:25:49.960> and<00:25:50.230> verify<00:25:50.620> our 00:25:50.880 --> 00:25:50.890 align:start position:0% verification to abstract and verify our 00:25:50.890 --> 00:25:53.820 align:start position:0% verification to abstract and verify our protocols<00:25:52.290> it's<00:25:53.290> pretty<00:25:53.530> exciting 00:25:53.820 --> 00:25:53.830 align:start position:0% protocols it's pretty exciting 00:25:53.830 --> 00:25:56.130 align:start position:0% protocols it's pretty exciting collaboration<00:25:54.700> and<00:25:54.970> you<00:25:55.900> know<00:25:55.990> they're 00:25:56.130 --> 00:25:56.140 align:start position:0% collaboration and you know they're 00:25:56.140 --> 00:25:59.130 align:start position:0% collaboration and you know they're really<00:25:56.380> amazing<00:25:56.830> and<00:25:57.190> at<00:25:57.310> this<00:25:57.460> work<00:25:58.140> they 00:25:59.130 --> 00:25:59.140 align:start position:0% really amazing and at this work they 00:25:59.140 --> 00:26:01.860 align:start position:0% really amazing and at this work they have<00:25:59.440> a<00:25:59.470> paper<00:25:59.800> that's<00:26:00.220> being<00:26:01.180> released<00:26:01.360> right 00:26:01.860 --> 00:26:01.870 align:start position:0% have a paper that's being released right 00:26:01.870 --> 00:26:05.610 align:start position:0% have a paper that's being released right now<00:26:02.520> and<00:26:03.520> and<00:26:04.510> here<00:26:04.750> you<00:26:04.900> see<00:26:05.110> that<00:26:05.230> the<00:26:05.410> main 00:26:05.610 --> 00:26:05.620 align:start position:0% now and and here you see that the main 00:26:05.620 --> 00:26:07.740 align:start position:0% now and and here you see that the main contributors<00:26:06.280> on<00:26:06.400> the<00:26:06.490> CVC<00:26:06.820> on<00:26:07.000> the<00:26:07.180> and 00:26:07.740 --> 00:26:07.750 align:start position:0% contributors on the CVC on the and 00:26:07.750 --> 00:26:10.080 align:start position:0% contributors on the CVC on the and runtime<00:26:07.960> verification<00:26:08.560> on<00:26:09.550> this<00:26:09.790> research 00:26:10.080 --> 00:26:10.090 align:start position:0% runtime verification on this research 00:26:10.090 --> 00:26:11.700 align:start position:0% runtime verification on this research and<00:26:10.570> they<00:26:10.690> they<00:26:11.020> basically<00:26:11.200> did<00:26:11.440> a<00:26:11.470> mission 00:26:11.700 --> 00:26:11.710 align:start position:0% and they they basically did a mission 00:26:11.710 --> 00:26:14.760 align:start position:0% and they they basically did a mission she<00:26:11.770> a<00:26:11.800> proof<00:26:12.370> in<00:26:12.580> talk<00:26:13.270> of<00:26:13.480> the<00:26:14.230> safety<00:26:14.470> and<00:26:14.680> on 00:26:14.760 --> 00:26:14.770 align:start position:0% she a proof in talk of the safety and on 00:26:14.770 --> 00:26:18.890 align:start position:0% she a proof in talk of the safety and on triviality<00:26:15.220> properties<00:26:15.640> of<00:26:15.820> the<00:26:17.580> abstract 00:26:18.890 --> 00:26:18.900 align:start position:0% triviality properties of the abstract 00:26:18.900 --> 00:26:21.750 align:start position:0% triviality properties of the abstract consensus<00:26:19.900> protocol<00:26:20.320> for<00:26:21.220> the<00:26:21.310> full<00:26:21.460> node<00:26:21.640> and 00:26:21.750 --> 00:26:21.760 align:start position:0% consensus protocol for the full node and 00:26:21.760 --> 00:26:26.529 align:start position:0% consensus protocol for the full node and the<00:26:21.820> light<00:26:21.970> node<00:26:22.150> and<00:26:22.620> here<00:26:23.620> is<00:26:23.860> the<00:26:24.280> paper 00:26:26.529 --> 00:26:26.539 align:start position:0% 00:26:26.539 --> 00:26:28.390 align:start position:0% give<00:26:27.260> you<00:26:27.380> a<00:26:27.470> moment<00:26:27.799> if<00:26:27.919> you<00:26:28.010> want<00:26:28.160> to<00:26:28.220> take<00:26:28.340> a 00:26:28.390 --> 00:26:28.400 align:start position:0% give you a moment if you want to take a 00:26:28.400 --> 00:26:32.710 align:start position:0% give you a moment if you want to take a photo<00:26:28.580> of<00:26:28.640> that<00:26:30.850> there<00:26:31.850> it<00:26:32.000> is<00:26:32.090> this<00:26:32.539> is<00:26:32.600> the 00:26:32.710 --> 00:26:32.720 align:start position:0% photo of that there it is this is the 00:26:32.720 --> 00:26:34.120 align:start position:0% photo of that there it is this is the paper 00:26:34.120 --> 00:26:34.130 align:start position:0% paper 00:26:34.130 --> 00:26:36.789 align:start position:0% paper this<00:26:34.580> is<00:26:35.270> proofs<00:26:35.570> it<00:26:35.960> goes<00:26:36.380> in<00:26:36.530> detail 00:26:36.789 --> 00:26:36.799 align:start position:0% this is proofs it goes in detail 00:26:36.799 --> 00:26:38.860 align:start position:0% this is proofs it goes in detail about<00:26:36.980> the<00:26:37.309> form<00:26:37.549> of<00:26:37.640> verification<00:26:37.760> of<00:26:38.299> these 00:26:38.860 --> 00:26:38.870 align:start position:0% about the form of verification of these 00:26:38.870 --> 00:26:40.810 align:start position:0% about the form of verification of these light<00:26:39.169> and<00:26:39.410> Pope<00:26:39.710> client<00:26:40.309> protocols<00:26:40.669> these 00:26:40.810 --> 00:26:40.820 align:start position:0% light and Pope client protocols these 00:26:40.820 --> 00:26:42.430 align:start position:0% light and Pope client protocols these they're<00:26:41.030> abstract<00:26:41.450> they<00:26:41.870> only<00:26:42.020> have<00:26:42.169> safety 00:26:42.430 --> 00:26:42.440 align:start position:0% they're abstract they only have safety 00:26:42.440 --> 00:26:43.870 align:start position:0% they're abstract they only have safety and<00:26:42.559> on<00:26:42.620> triviality<00:26:43.070> they're<00:26:43.220> not<00:26:43.370> live<00:26:43.580> at 00:26:43.870 --> 00:26:43.880 align:start position:0% and on triviality they're not live at 00:26:43.880 --> 00:26:47.289 align:start position:0% and on triviality they're not live at this<00:26:44.059> level<00:26:44.750> of<00:26:44.900> specification<00:26:46.179> anyone<00:26:47.179> will 00:26:47.289 --> 00:26:47.299 align:start position:0% this level of specification anyone will 00:26:47.299 --> 00:26:48.970 align:start position:0% this level of specification anyone will check<00:26:47.510> out<00:26:47.600> the<00:26:47.809> proofs<00:26:48.049> here<00:26:48.230> this<00:26:48.860> is 00:26:48.970 --> 00:26:48.980 align:start position:0% check out the proofs here this is 00:26:48.980 --> 00:26:50.590 align:start position:0% check out the proofs here this is like<00:26:49.100> a<00:26:49.130> github<00:26:49.340> link<00:26:49.520> to<00:26:49.789> the<00:26:49.880> actual<00:26:50.030> proofs 00:26:50.590 --> 00:26:50.600 align:start position:0% like a github link to the actual proofs 00:26:50.600 --> 00:26:55.210 align:start position:0% like a github link to the actual proofs if<00:26:51.110> you're<00:26:51.320> interested<00:26:51.650> in<00:26:51.710> that<00:26:54.220> Ryo 00:26:55.210 --> 00:26:55.220 align:start position:0% if you're interested in that Ryo 00:26:55.220 --> 00:26:57.789 align:start position:0% if you're interested in that Ryo Nakamura<00:26:55.700> like<00:26:56.240> I<00:26:56.360> mentioned<00:26:56.720> had<00:26:56.900> has<00:26:57.770> a 00:26:57.789 --> 00:26:57.799 align:start position:0% Nakamura like I mentioned had has a 00:26:57.799 --> 00:27:00.789 align:start position:0% Nakamura like I mentioned had has a formal<00:26:58.549> verification<00:26:58.700> of<00:26:59.240> the<00:26:59.799> decision 00:27:00.789 --> 00:27:00.799 align:start position:0% formal verification of the decision 00:27:00.799 --> 00:27:05.169 align:start position:0% formal verification of the decision detector<00:27:01.840> III<00:27:02.840> didn't<00:27:03.289> make<00:27:03.409> a<00:27:03.909> QR<00:27:04.909> code<00:27:05.059> for 00:27:05.169 --> 00:27:05.179 align:start position:0% detector III didn't make a QR code for 00:27:05.179 --> 00:27:06.549 align:start position:0% detector III didn't make a QR code for this<00:27:05.299> that's<00:27:05.510> kind<00:27:05.659> of<00:27:05.690> dumb<00:27:05.840> I'm<00:27:05.990> sorry<00:27:06.200> go 00:27:06.549 --> 00:27:06.559 align:start position:0% this that's kind of dumb I'm sorry go 00:27:06.559 --> 00:27:08.200 align:start position:0% this that's kind of dumb I'm sorry go check<00:27:06.740> him<00:27:06.830> out<00:27:06.890> on<00:27:07.010> Twitter<00:27:07.250> look<00:27:07.940> for<00:27:08.120> this 00:27:08.200 --> 00:27:08.210 align:start position:0% check him out on Twitter look for this 00:27:08.210 --> 00:27:11.770 align:start position:0% check him out on Twitter look for this tweet<00:27:08.480> click<00:27:09.140> on<00:27:09.260> that<00:27:09.350> link<00:27:10.480> maybe<00:27:11.480> see<00:27:11.630> him 00:27:11.770 --> 00:27:11.780 align:start position:0% tweet click on that link maybe see him 00:27:11.780 --> 00:27:13.480 align:start position:0% tweet click on that link maybe see him after<00:27:11.900> and<00:27:12.200> get<00:27:12.289> it<00:27:12.409> get<00:27:12.620> it<00:27:12.650> from<00:27:12.799> him<00:27:13.010> sorry 00:27:13.480 --> 00:27:13.490 align:start position:0% after and get it get it from him sorry 00:27:13.490 --> 00:27:14.710 align:start position:0% after and get it get it from him sorry about<00:27:13.610> the<00:27:13.789> lack<00:27:14.000> of<00:27:14.030> QR<00:27:14.299> code<00:27:14.419> I<00:27:14.510> don't<00:27:14.659> know 00:27:14.710 --> 00:27:14.720 align:start position:0% about the lack of QR code I don't know 00:27:14.720 --> 00:27:15.419 align:start position:0% about the lack of QR code I don't know what<00:27:14.809> happened 00:27:15.419 --> 00:27:15.429 align:start position:0% what happened 00:27:15.429 --> 00:27:17.799 align:start position:0% what happened Kasper<00:27:16.429> labs<00:27:16.610> is<00:27:16.820> implementing<00:27:17.299> the<00:27:17.390> CBC<00:27:17.690> a 00:27:17.799 --> 00:27:17.809 align:start position:0% Kasper labs is implementing the CBC a 00:27:17.809 --> 00:27:21.340 align:start position:0% Kasper labs is implementing the CBC a CBC<00:27:18.140> Kasper<00:27:18.440> blockchain<00:27:19.159> for<00:27:20.150> production<00:27:20.840> you 00:27:21.340 --> 00:27:21.350 align:start position:0% CBC Kasper blockchain for production you 00:27:21.350 --> 00:27:22.630 align:start position:0% CBC Kasper blockchain for production you know<00:27:21.440> quite<00:27:21.799> different<00:27:22.130> than<00:27:22.220> a<00:27:22.280> research 00:27:22.630 --> 00:27:22.640 align:start position:0% know quite different than a research 00:27:22.640 --> 00:27:25.539 align:start position:0% know quite different than a research roadmap<00:27:23.470> and<00:27:24.470> they've<00:27:24.740> you<00:27:25.309> know<00:27:25.370> they<00:27:25.429> have 00:27:25.539 --> 00:27:25.549 align:start position:0% roadmap and they've you know they have 00:27:25.549 --> 00:27:27.399 align:start position:0% roadmap and they've you know they have like<00:27:25.580> a<00:27:25.730> github<00:27:26.150> that<00:27:26.600> you<00:27:26.720> can<00:27:26.840> follow<00:27:27.049> and<00:27:27.320> is 00:27:27.399 --> 00:27:27.409 align:start position:0% like a github that you can follow and is 00:27:27.409 --> 00:27:30.399 align:start position:0% like a github that you can follow and is quite<00:27:27.980> active<00:27:28.340> and<00:27:28.549> they<00:27:29.299> they<00:27:29.929> came<00:27:30.049> up<00:27:30.230> with 00:27:30.399 --> 00:27:30.409 align:start position:0% quite active and they they came up with 00:27:30.409 --> 00:27:33.720 align:start position:0% quite active and they they came up with this<00:27:30.500> paper<00:27:30.740> which<00:27:31.010> also<00:27:31.309> released<00:27:31.669> today<00:27:32.049> is 00:27:33.720 --> 00:27:33.730 align:start position:0% this paper which also released today is 00:27:33.730 --> 00:27:35.890 align:start position:0% this paper which also released today is gives<00:27:34.730> this<00:27:35.000> leader<00:27:35.360> based<00:27:35.630> liveness 00:27:35.890 --> 00:27:35.900 align:start position:0% gives this leader based liveness 00:27:35.900 --> 00:27:38.620 align:start position:0% gives this leader based liveness strategy<00:27:36.500> for<00:27:37.429> partial<00:27:38.210> synchronous 00:27:38.620 --> 00:27:38.630 align:start position:0% strategy for partial synchronous 00:27:38.630 --> 00:27:42.370 align:start position:0% strategy for partial synchronous networks<00:27:39.610> and<00:27:40.929> you<00:27:41.929> know<00:27:42.020> it's<00:27:42.169> it's 00:27:42.370 --> 00:27:42.380 align:start position:0% networks and you know it's it's 00:27:42.380 --> 00:27:44.919 align:start position:0% networks and you know it's it's basically<00:27:42.850> it<00:27:43.850> gives<00:27:44.240> I<00:27:44.539> think<00:27:44.750> both 00:27:44.919 --> 00:27:44.929 align:start position:0% basically it gives I think both 00:27:44.929 --> 00:27:46.149 align:start position:0% basically it gives I think both alignment<00:27:45.289> strategy<00:27:45.590> and<00:27:45.740> the<00:27:45.890> finality 00:27:46.149 --> 00:27:46.159 align:start position:0% alignment strategy and the finality 00:27:46.159 --> 00:27:51.279 align:start position:0% alignment strategy and the finality criteria<00:27:47.350> and<00:27:48.760> here<00:27:49.760> is<00:27:49.940> the<00:27:50.179> QR<00:27:50.539> code<00:27:50.870> the<00:27:51.049> QR 00:27:51.279 --> 00:27:51.289 align:start position:0% criteria and here is the QR code the QR 00:27:51.289 --> 00:28:00.550 align:start position:0% criteria and here is the QR code the QR code<00:27:51.500> for<00:27:51.679> that<00:27:51.830> paper 00:28:00.550 --> 00:28:00.560 align:start position:0% 00:28:00.560 --> 00:28:02.680 align:start position:0% the<00:28:01.430> theorem<00:28:01.610> foundation<00:28:02.120> continues<00:28:02.420> to 00:28:02.680 --> 00:28:02.690 align:start position:0% the theorem foundation continues to 00:28:02.690 --> 00:28:05.050 align:start position:0% the theorem foundation continues to support<00:28:02.990> our<00:28:03.140> work<00:28:03.610> sometimes<00:28:04.610> I<00:28:04.670> have<00:28:04.790> to<00:28:04.880> say 00:28:05.050 --> 00:28:05.060 align:start position:0% support our work sometimes I have to say 00:28:05.060 --> 00:28:07.900 align:start position:0% support our work sometimes I have to say this<00:28:05.210> people<00:28:05.390> get<00:28:05.600> confused<00:28:06.160> you<00:28:07.160> know<00:28:07.280> still 00:28:07.900 --> 00:28:07.910 align:start position:0% this people get confused you know still 00:28:07.910 --> 00:28:09.820 align:start position:0% this people get confused you know still very<00:28:07.940> much<00:28:08.300> being<00:28:09.020> supported<00:28:09.440> by<00:28:09.470> the<00:28:09.560> theorem 00:28:09.820 --> 00:28:09.830 align:start position:0% very much being supported by the theorem 00:28:09.830 --> 00:28:12.490 align:start position:0% very much being supported by the theorem foundation<00:28:10.280> in<00:28:10.400> our<00:28:10.490> research<00:28:10.760> both<00:28:11.500> directly 00:28:12.490 --> 00:28:12.500 align:start position:0% foundation in our research both directly 00:28:12.500 --> 00:28:16.120 align:start position:0% foundation in our research both directly and<00:28:12.620> indirectly<00:28:12.950> through<00:28:13.280> grants<00:28:14.560> I<00:28:15.560> have<00:28:16.100> a 00:28:16.120 --> 00:28:16.130 align:start position:0% and indirectly through grants I have a 00:28:16.130 --> 00:28:17.740 align:start position:0% and indirectly through grants I have a paper<00:28:16.370> which<00:28:16.700> I<00:28:16.940> was<00:28:17.150> planning<00:28:17.450> on<00:28:17.510> enough 00:28:17.740 --> 00:28:17.750 align:start position:0% paper which I was planning on enough 00:28:17.750 --> 00:28:19.420 align:start position:0% paper which I was planning on enough releasing<00:28:18.650> today<00:28:18.770> but<00:28:19.070> which<00:28:19.160> unfortunately 00:28:19.420 --> 00:28:19.430 align:start position:0% releasing today but which unfortunately 00:28:19.430 --> 00:28:22.540 align:start position:0% releasing today but which unfortunately I<00:28:20.030> haven't<00:28:20.450> been<00:28:20.870> able<00:28:20.990> to<00:28:21.140> finish<00:28:21.380> but<00:28:22.160> I've 00:28:22.540 --> 00:28:22.550 align:start position:0% I haven't been able to finish but I've 00:28:22.550 --> 00:28:24.670 align:start position:0% I haven't been able to finish but I've broke<00:28:23.330> my<00:28:23.360> back<00:28:23.570> trying<00:28:23.750> and<00:28:24.140> I'm<00:28:24.350> gonna<00:28:24.440> try 00:28:24.670 --> 00:28:24.680 align:start position:0% broke my back trying and I'm gonna try 00:28:24.680 --> 00:28:26.770 align:start position:0% broke my back trying and I'm gonna try to<00:28:24.740> finish<00:28:24.890> it<00:28:25.010> super<00:28:25.310> soon<00:28:25.490> for<00:28:26.390> all<00:28:26.510> of<00:28:26.630> you 00:28:26.770 --> 00:28:26.780 align:start position:0% to finish it super soon for all of you 00:28:26.780 --> 00:28:31.870 align:start position:0% to finish it super soon for all of you to<00:28:26.990> see<00:28:27.290> and<00:28:28.060> this<00:28:29.060> is<00:28:29.500> basically<00:28:30.500> a<00:28:30.880> abstract 00:28:31.870 --> 00:28:31.880 align:start position:0% to see and this is basically a abstract 00:28:31.880 --> 00:28:34.660 align:start position:0% to see and this is basically a abstract kind<00:28:32.780> of<00:28:32.840> similar<00:28:33.560> to<00:28:33.800> the<00:28:33.890> minimum<00:28:34.190> consensus 00:28:34.660 --> 00:28:34.670 align:start position:0% kind of similar to the minimum consensus 00:28:34.670 --> 00:28:36.970 align:start position:0% kind of similar to the minimum consensus for<00:28:35.060> paper<00:28:35.480> style<00:28:35.840> but<00:28:36.380> which<00:28:36.470> also<00:28:36.680> has 00:28:36.970 --> 00:28:36.980 align:start position:0% for paper style but which also has 00:28:36.980 --> 00:28:39.070 align:start position:0% for paper style but which also has liveness<00:28:37.700> properties<00:28:38.210> in<00:28:38.510> a<00:28:38.660> synchronous 00:28:39.070 --> 00:28:39.080 align:start position:0% liveness properties in a synchronous 00:28:39.080 --> 00:28:41.980 align:start position:0% liveness properties in a synchronous network<00:28:39.380> it's<00:28:39.890> a<00:28:40.040> it's<00:28:40.220> really<00:28:40.340> really<00:28:40.930> it's<00:28:41.930> a 00:28:41.980 --> 00:28:41.990 align:start position:0% network it's a it's really really it's a 00:28:41.990 --> 00:28:44.050 align:start position:0% network it's a it's really really it's a creates<00:28:42.200> quite<00:28:42.320> a<00:28:42.380> cool<00:28:42.560> paper<00:28:42.710> it<00:28:43.280> does<00:28:43.820> it 00:28:44.050 --> 00:28:44.060 align:start position:0% creates quite a cool paper it does it 00:28:44.060 --> 00:28:48.400 align:start position:0% creates quite a cool paper it does it gives<00:28:44.180> formal<00:28:44.600> problem<00:28:45.380> statements<00:28:47.410> absences 00:28:48.400 --> 00:28:48.410 align:start position:0% gives formal problem statements absences 00:28:48.410 --> 00:28:50.050 align:start position:0% gives formal problem statements absences problem<00:28:48.830> and<00:28:49.010> goes<00:28:49.460> through<00:28:49.670> the<00:28:49.790> correct<00:28:49.970> by 00:28:50.050 --> 00:28:50.060 align:start position:0% problem and goes through the correct by 00:28:50.060 --> 00:28:53.320 align:start position:0% problem and goes through the correct by construction<00:28:50.390> process<00:28:50.900> to<00:28:51.820> show<00:28:52.820> kind<00:28:53.120> of<00:28:53.150> how 00:28:53.320 --> 00:28:53.330 align:start position:0% construction process to show kind of how 00:28:53.330 --> 00:28:55.750 align:start position:0% construction process to show kind of how the<00:28:54.320> protocol<00:28:54.830> can<00:28:54.860> be<00:28:55.010> derived<00:28:55.280> from<00:28:55.580> the 00:28:55.750 --> 00:28:55.760 align:start position:0% the protocol can be derived from the 00:28:55.760 --> 00:28:57.700 align:start position:0% the protocol can be derived from the problem<00:28:56.030> statements<00:28:56.420> in<00:28:56.690> a<00:28:57.290> way<00:28:57.410> that<00:28:57.590> is 00:28:57.700 --> 00:28:57.710 align:start position:0% problem statements in a way that is 00:28:57.710 --> 00:28:59.170 align:start position:0% problem statements in a way that is guaranteed<00:28:58.130> to<00:28:58.160> be<00:28:58.250> correct<00:28:58.370> and<00:28:58.880> and<00:28:59.090> they 00:28:59.170 --> 00:28:59.180 align:start position:0% guaranteed to be correct and and they 00:28:59.180 --> 00:29:01.570 align:start position:0% guaranteed to be correct and and they kind<00:28:59.390> of<00:28:59.420> justifies<00:29:00.410> a<00:29:00.440> lot<00:29:00.770> of<00:29:00.890> the<00:29:01.010> like<00:29:01.460> the 00:29:01.570 --> 00:29:01.580 align:start position:0% kind of justifies a lot of the like the 00:29:01.580 --> 00:29:03.520 align:start position:0% kind of justifies a lot of the like the minimal<00:29:01.850> CDC<00:29:02.150> Kasper<00:29:02.510> paper<00:29:02.750> and<00:29:03.020> this<00:29:03.380> one 00:29:03.520 --> 00:29:03.530 align:start position:0% minimal CDC Kasper paper and this one 00:29:03.530 --> 00:29:05.700 align:start position:0% minimal CDC Kasper paper and this one with<00:29:03.680> the<00:29:03.800> liveness 00:29:05.700 --> 00:29:05.710 align:start position:0% with the liveness 00:29:05.710 --> 00:29:09.430 align:start position:0% with the liveness so<00:29:06.710> finally<00:29:07.640> you<00:29:08.360> know<00:29:08.450> right<00:29:08.720> after<00:29:08.870> this<00:29:09.140> I'm 00:29:09.430 --> 00:29:09.440 align:start position:0% so finally you know right after this I'm 00:29:09.440 --> 00:29:11.410 align:start position:0% so finally you know right after this I'm hoping<00:29:09.800> we<00:29:10.010> will<00:29:10.190> or<00:29:10.580> some<00:29:10.910> of<00:29:11.060> us<00:29:11.210> you<00:29:11.360> know 00:29:11.410 --> 00:29:11.420 align:start position:0% hoping we will or some of us you know 00:29:11.420 --> 00:29:13.720 align:start position:0% hoping we will or some of us you know anyone<00:29:11.810> who's<00:29:12.070> contributed<00:29:13.070> to<00:29:13.130> CBC<00:29:13.340> Kasper 00:29:13.720 --> 00:29:13.730 align:start position:0% anyone who's contributed to CBC Kasper 00:29:13.730 --> 00:29:16.480 align:start position:0% anyone who's contributed to CBC Kasper research<00:29:14.080> will<00:29:15.080> hopefully<00:29:15.770> meet<00:29:16.070> us<00:29:16.190> right<00:29:16.280> up 00:29:16.480 --> 00:29:16.490 align:start position:0% research will hopefully meet us right up 00:29:16.490 --> 00:29:18.240 align:start position:0% research will hopefully meet us right up here<00:29:16.760> and<00:29:16.910> we'll<00:29:17.690> have<00:29:17.810> like<00:29:17.990> a<00:29:18.020> little 00:29:18.240 --> 00:29:18.250 align:start position:0% here and we'll have like a little 00:29:18.250 --> 00:29:21.220 align:start position:0% here and we'll have like a little conversation<00:29:19.250> about<00:29:19.790> Susie<00:29:20.660> Kasper<00:29:20.960> research 00:29:21.220 --> 00:29:21.230 align:start position:0% conversation about Susie Kasper research 00:29:21.230 --> 00:29:22.390 align:start position:0% conversation about Susie Kasper research if<00:29:21.320> you<00:29:21.350> have<00:29:21.560> you<00:29:21.620> have<00:29:21.680> any<00:29:21.860> questions<00:29:22.220> that 00:29:22.390 --> 00:29:22.400 align:start position:0% if you have you have any questions that 00:29:22.400 --> 00:29:25.180 align:start position:0% if you have you have any questions that you<00:29:22.490> want<00:29:22.580> answered<00:29:23.710> please<00:29:24.710> come<00:29:24.920> and<00:29:25.040> talk 00:29:25.180 --> 00:29:25.190 align:start position:0% you want answered please come and talk 00:29:25.190 --> 00:29:27.520 align:start position:0% you want answered please come and talk to<00:29:25.250> us<00:29:25.400> hopefully<00:29:26.120> it<00:29:26.960> won't<00:29:27.080> be<00:29:27.170> just<00:29:27.320> me<00:29:27.500> and 00:29:27.520 --> 00:29:27.530 align:start position:0% to us hopefully it won't be just me and 00:29:27.530 --> 00:29:30.070 align:start position:0% to us hopefully it won't be just me and other<00:29:27.800> researchers<00:29:28.160> will<00:29:28.310> come<00:29:28.430> to<00:29:28.600> but<00:29:29.600> you 00:29:30.070 --> 00:29:30.080 align:start position:0% other researchers will come to but you 00:29:30.080 --> 00:29:32.110 align:start position:0% other researchers will come to but you know<00:29:30.170> it's<00:29:30.440> tough<00:29:30.590> to<00:29:30.650> them<00:29:30.880> we're<00:29:31.880> gonna<00:29:31.970> do 00:29:32.110 --> 00:29:32.120 align:start position:0% know it's tough to them we're gonna do 00:29:32.120 --> 00:29:35.140 align:start position:0% know it's tough to them we're gonna do an<00:29:32.210> asking<00:29:32.570> anything<00:29:32.780> on<00:29:33.140> online<00:29:33.380> soon<00:29:34.120> also<00:29:35.120> I 00:29:35.140 --> 00:29:35.150 align:start position:0% an asking anything on online soon also I 00:29:35.150 --> 00:29:38.950 align:start position:0% an asking anything on online soon also I have<00:29:35.510> t-shirts<00:29:36.370> limited-edition<00:29:37.960> t-shirts 00:29:38.950 --> 00:29:38.960 align:start position:0% have t-shirts limited-edition t-shirts 00:29:38.960 --> 00:29:40.810 align:start position:0% have t-shirts limited-edition t-shirts that<00:29:39.200> I'm<00:29:39.320> giving<00:29:39.620> away<00:29:39.710> not<00:29:40.280> to<00:29:40.430> everyone 00:29:40.810 --> 00:29:40.820 align:start position:0% that I'm giving away not to everyone 00:29:40.820 --> 00:29:43.090 align:start position:0% that I'm giving away not to everyone please<00:29:41.440> first<00:29:42.440> I<00:29:42.590> have<00:29:42.710> to<00:29:42.800> give<00:29:42.890> away<00:29:43.040> two 00:29:43.090 --> 00:29:43.100 align:start position:0% please first I have to give away two 00:29:43.100 --> 00:29:44.620 align:start position:0% please first I have to give away two contributors<00:29:43.460> so<00:29:44.180> I<00:29:44.210> know<00:29:44.330> there's<00:29:44.450> some<00:29:44.540> of 00:29:44.620 --> 00:29:44.630 align:start position:0% contributors so I know there's some of 00:29:44.630 --> 00:29:46.150 align:start position:0% contributors so I know there's some of you<00:29:44.720> here<00:29:44.930> give<00:29:45.530> it<00:29:45.560> away<00:29:45.650> to<00:29:45.740> contributors 00:29:46.150 --> 00:29:46.160 align:start position:0% you here give it away to contributors 00:29:46.160 --> 00:29:47.590 align:start position:0% you here give it away to contributors first<00:29:46.370> and<00:29:46.580> then<00:29:46.730> I'll<00:29:46.910> and<00:29:47.210> then<00:29:47.240> I'll<00:29:47.450> do 00:29:47.590 --> 00:29:47.600 align:start position:0% first and then I'll and then I'll do 00:29:47.600 --> 00:29:50.410 align:start position:0% first and then I'll and then I'll do first-come<00:29:48.320> first-serve<00:29:48.650> after<00:29:49.270> so<00:29:50.270> the 00:29:50.410 --> 00:29:50.420 align:start position:0% first-come first-serve after so the 00:29:50.420 --> 00:29:51.640 align:start position:0% first-come first-serve after so the first-come<00:29:50.720> first-served<00:29:51.110> will<00:29:51.200> be<00:29:51.320> tomorrow 00:29:51.640 --> 00:29:51.650 align:start position:0% first-come first-served will be tomorrow 00:29:51.650 --> 00:29:53.200 align:start position:0% first-come first-served will be tomorrow but<00:29:52.190> for<00:29:52.250> now<00:29:52.460> if<00:29:52.580> you're<00:29:52.700> a<00:29:52.730> contributor<00:29:53.120> and 00:29:53.200 --> 00:29:53.210 align:start position:0% but for now if you're a contributor and 00:29:53.210 --> 00:29:56.200 align:start position:0% but for now if you're a contributor and you<00:29:53.300> want<00:29:53.450> a<00:29:53.480> shirt<00:29:53.720> come<00:29:54.170> get<00:29:54.320> it<00:29:55.180> thank<00:29:56.180> you 00:29:56.200 --> 00:29:56.210 align:start position:0% you want a shirt come get it thank you 00:29:56.210 --> 00:29:59.810 align:start position:0% you want a shirt come get it thank you so<00:29:56.270> much<00:29:56.510> really<00:29:57.470> appreciate 00:29:59.810 --> 00:29:59.820 align:start position:0% so much really appreciate 00:29:59.820 --> 00:30:08.419 align:start position:0% so much really appreciate you 00:30:08.419 --> 00:30:08.429 align:start position:0% 00:30:08.429 --> 00:30:10.490 align:start position:0% you