WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:13.270 align:start position:0% [Music] 00:00:13.270 --> 00:00:13.280 align:start position:0% 00:00:13.280 --> 00:00:17.029 align:start position:0% hello<00:00:13.799> uh<00:00:13.920> can<00:00:14.040> you<00:00:14.200> all<00:00:14.440> hear<00:00:14.639> me<00:00:15.200> okay<00:00:15.799> uh<00:00:16.119> I'm 00:00:17.029 --> 00:00:17.039 align:start position:0% hello uh can you all hear me okay uh I'm 00:00:17.039 --> 00:00:18.950 align:start position:0% hello uh can you all hear me okay uh I'm Gabriel<00:00:18.039> and<00:00:18.199> today<00:00:18.439> we're<00:00:18.600> going<00:00:18.720> to<00:00:18.800> be 00:00:18.950 --> 00:00:18.960 align:start position:0% Gabriel and today we're going to be 00:00:18.960 --> 00:00:20.390 align:start position:0% Gabriel and today we're going to be talking<00:00:19.240> fraud<00:00:19.600> proofs<00:00:19.920> you<00:00:20.000> know<00:00:20.160> like 00:00:20.390 --> 00:00:20.400 align:start position:0% talking fraud proofs you know like 00:00:20.400 --> 00:00:22.710 align:start position:0% talking fraud proofs you know like another<00:00:20.760> session<00:00:21.080> about<00:00:21.240> fraud<00:00:21.560> proofs<00:00:22.480> uh<00:00:22.600> we 00:00:22.710 --> 00:00:22.720 align:start position:0% another session about fraud proofs uh we 00:00:22.720 --> 00:00:25.470 align:start position:0% another session about fraud proofs uh we will<00:00:22.920> present<00:00:23.240> a<00:00:23.400> new<00:00:23.599> technique<00:00:24.439> uh<00:00:24.680> that 00:00:25.470 --> 00:00:25.480 align:start position:0% will present a new technique uh that 00:00:25.480 --> 00:00:27.189 align:start position:0% will present a new technique uh that we've<00:00:25.800> just<00:00:26.039> published<00:00:26.519> in<00:00:26.640> fact<00:00:26.920> so<00:00:27.039> it's 00:00:27.189 --> 00:00:27.199 align:start position:0% we've just published in fact so it's 00:00:27.199 --> 00:00:28.630 align:start position:0% we've just published in fact so it's been<00:00:27.320> in<00:00:27.400> the<00:00:27.519> oven<00:00:27.720> for<00:00:28.000> quite<00:00:28.160> a<00:00:28.279> while<00:00:28.519> and 00:00:28.630 --> 00:00:28.640 align:start position:0% been in the oven for quite a while and 00:00:28.640 --> 00:00:30.990 align:start position:0% been in the oven for quite a while and I'm<00:00:28.800> quite<00:00:29.000> excited<00:00:29.359> to<00:00:29.480> show<00:00:29.640> it<00:00:29.759> to<00:00:30.199> you<00:00:30.320> all 00:00:30.990 --> 00:00:31.000 align:start position:0% I'm quite excited to show it to you all 00:00:31.000 --> 00:00:32.950 align:start position:0% I'm quite excited to show it to you all but<00:00:31.119> the<00:00:31.279> bottom<00:00:31.599> line<00:00:31.800> is<00:00:31.960> that<00:00:32.200> we<00:00:32.399> weren't 00:00:32.950 --> 00:00:32.960 align:start position:0% but the bottom line is that we weren't 00:00:32.960 --> 00:00:36.110 align:start position:0% but the bottom line is that we weren't quite<00:00:33.719> happy<00:00:34.719> uh<00:00:34.960> on<00:00:35.320> the<00:00:35.520> current<00:00:35.840> set<00:00:36.000> of 00:00:36.110 --> 00:00:36.120 align:start position:0% quite happy uh on the current set of 00:00:36.120 --> 00:00:38.069 align:start position:0% quite happy uh on the current set of fraud<00:00:36.399> proof<00:00:36.680> so<00:00:36.800> we<00:00:36.960> created<00:00:37.399> a<00:00:37.520> new 00:00:38.069 --> 00:00:38.079 align:start position:0% fraud proof so we created a new 00:00:38.079 --> 00:00:40.069 align:start position:0% fraud proof so we created a new algorithm<00:00:39.079> uh<00:00:39.200> so<00:00:39.320> first<00:00:39.520> I<00:00:39.640> like<00:00:39.760> to<00:00:39.879> thank 00:00:40.069 --> 00:00:40.079 align:start position:0% algorithm uh so first I like to thank 00:00:40.079 --> 00:00:42.029 align:start position:0% algorithm uh so first I like to thank caresia<00:00:40.559> for<00:00:40.680> all<00:00:40.760> the<00:00:40.879> grants<00:00:41.280> provided<00:00:41.879> and 00:00:42.029 --> 00:00:42.039 align:start position:0% caresia for all the grants provided and 00:00:42.039 --> 00:00:44.069 align:start position:0% caresia for all the grants provided and also<00:00:42.320> my<00:00:42.520> co-authors<00:00:43.160> austo<00:00:43.640> who<00:00:43.719> is<00:00:43.800> here<00:00:43.920> on 00:00:44.069 --> 00:00:44.079 align:start position:0% also my co-authors austo who is here on 00:00:44.079 --> 00:00:46.830 align:start position:0% also my co-authors austo who is here on the<00:00:44.160> audience<00:00:45.039> and<00:00:45.200> Diego<00:00:46.160> uh<00:00:46.239> so<00:00:46.520> thank<00:00:46.680> you 00:00:46.830 --> 00:00:46.840 align:start position:0% the audience and Diego uh so thank you 00:00:46.840 --> 00:00:49.029 align:start position:0% the audience and Diego uh so thank you all<00:00:47.600> and<00:00:47.719> also<00:00:47.920> to<00:00:48.039> all<00:00:48.160> the<00:00:48.280> organizers<00:00:48.879> of 00:00:49.029 --> 00:00:49.039 align:start position:0% all and also to all the organizers of 00:00:49.039 --> 00:00:51.630 align:start position:0% all and also to all the organizers of this<00:00:49.199> amazing<00:00:49.600> event<00:00:50.559> um<00:00:50.920> yeah<00:00:51.120> so<00:00:51.320> first<00:00:51.559> I 00:00:51.630 --> 00:00:51.640 align:start position:0% this amazing event um yeah so first I 00:00:51.640 --> 00:00:53.950 align:start position:0% this amazing event um yeah so first I want<00:00:51.760> to<00:00:51.960> get<00:00:52.160> this<00:00:52.359> question<00:00:52.800> out<00:00:52.960> of<00:00:53.120> the<00:00:53.280> way 00:00:53.950 --> 00:00:53.960 align:start position:0% want to get this question out of the way 00:00:53.960 --> 00:00:57.510 align:start position:0% want to get this question out of the way the<00:00:54.120> Zeki<00:00:54.760> question<00:00:55.760> uh<00:00:56.039> it<00:00:56.239> may<00:00:56.480> feel<00:00:56.920> that 00:00:57.510 --> 00:00:57.520 align:start position:0% the Zeki question uh it may feel that 00:00:57.520 --> 00:00:59.189 align:start position:0% the Zeki question uh it may feel that when<00:00:57.640> we're<00:00:57.879> talking<00:00:58.160> about<00:00:58.359> fraud<00:00:58.719> proofs 00:00:59.189 --> 00:00:59.199 align:start position:0% when we're talking about fraud proofs 00:00:59.199 --> 00:01:01.630 align:start position:0% when we're talking about fraud proofs that<00:00:59.320> we're<00:00:59.480> trying<00:00:59.680> to<00:01:00.039> figure<00:01:00.320> out<00:01:01.079> the<00:01:01.280> best 00:01:01.630 --> 00:01:01.640 align:start position:0% that we're trying to figure out the best 00:01:01.640 --> 00:01:05.030 align:start position:0% that we're trying to figure out the best grass<00:01:02.640> to<00:01:02.840> feed<00:01:03.120> our<00:01:03.600> horses<00:01:04.600> uh<00:01:04.760> and<00:01:04.839> I<00:01:04.920> want 00:01:05.030 --> 00:01:05.040 align:start position:0% grass to feed our horses uh and I want 00:01:05.040 --> 00:01:06.590 align:start position:0% grass to feed our horses uh and I want to<00:01:05.239> push<00:01:05.479> back<00:01:05.680> against<00:01:05.920> that<00:01:06.119> notion<00:01:06.439> you 00:01:06.590 --> 00:01:06.600 align:start position:0% to push back against that notion you 00:01:06.600 --> 00:01:08.670 align:start position:0% to push back against that notion you know<00:01:06.840> because<00:01:07.680> there<00:01:07.799> are<00:01:07.960> no<00:01:08.080> silver<00:01:08.360> bullets 00:01:08.670 --> 00:01:08.680 align:start position:0% know because there are no silver bullets 00:01:08.680 --> 00:01:11.310 align:start position:0% know because there are no silver bullets you<00:01:08.759> know<00:01:08.920> ZK<00:01:09.240> is<00:01:09.360> not<00:01:09.880> panaca<00:01:10.880> uh<00:01:11.040> when<00:01:11.159> you 00:01:11.310 --> 00:01:11.320 align:start position:0% you know ZK is not panaca uh when you 00:01:11.320 --> 00:01:12.830 align:start position:0% you know ZK is not panaca uh when you compare<00:01:11.640> them<00:01:11.799> with<00:01:11.960> front<00:01:12.240> proofs<00:01:12.520> there's<00:01:12.680> a 00:01:12.830 --> 00:01:12.840 align:start position:0% compare them with front proofs there's a 00:01:12.840 --> 00:01:16.109 align:start position:0% compare them with front proofs there's a sharp<00:01:13.200> contrast<00:01:13.640> in<00:01:13.840> throughput<00:01:14.479> and<00:01:15.119> costs 00:01:16.109 --> 00:01:16.119 align:start position:0% sharp contrast in throughput and costs 00:01:16.119 --> 00:01:18.310 align:start position:0% sharp contrast in throughput and costs uh<00:01:16.280> which<00:01:16.439> means<00:01:16.840> that<00:01:17.320> depending<00:01:17.680> on<00:01:17.799> the 00:01:18.310 --> 00:01:18.320 align:start position:0% uh which means that depending on the 00:01:18.320 --> 00:01:21.030 align:start position:0% uh which means that depending on the application<00:01:19.320> you're<00:01:19.520> going<00:01:19.640> to<00:01:19.799> prefer<00:01:20.720> the 00:01:21.030 --> 00:01:21.040 align:start position:0% application you're going to prefer the 00:01:21.040 --> 00:01:22.350 align:start position:0% application you're going to prefer the different<00:01:21.360> algorithms<00:01:21.920> you<00:01:22.040> know<00:01:22.159> there 00:01:22.350 --> 00:01:22.360 align:start position:0% different algorithms you know there 00:01:22.360 --> 00:01:23.670 align:start position:0% different algorithms you know there going<00:01:22.439> to<00:01:22.560> be<00:01:22.680> trade-offs<00:01:23.200> in<00:01:23.320> the<00:01:23.439> end 00:01:23.670 --> 00:01:23.680 align:start position:0% going to be trade-offs in the end 00:01:23.680 --> 00:01:25.429 align:start position:0% going to be trade-offs in the end there's<00:01:23.960> no<00:01:24.079> silver<00:01:24.400> bullets<00:01:25.079> that's<00:01:25.320> the 00:01:25.429 --> 00:01:25.439 align:start position:0% there's no silver bullets that's the 00:01:25.439 --> 00:01:28.030 align:start position:0% there's no silver bullets that's the point<00:01:25.720> I<00:01:25.799> wanted<00:01:26.079> to<00:01:26.280> get<00:01:26.560> across<00:01:27.520> so<00:01:27.720> now 00:01:28.030 --> 00:01:28.040 align:start position:0% point I wanted to get across so now 00:01:28.040 --> 00:01:31.350 align:start position:0% point I wanted to get across so now let's<00:01:28.280> focus<00:01:28.799> on<00:01:29.000> fraud<00:01:29.400> proofs 00:01:31.350 --> 00:01:31.360 align:start position:0% let's focus on fraud proofs 00:01:31.360 --> 00:01:33.789 align:start position:0% let's focus on fraud proofs yeah<00:01:32.360> the<00:01:32.520> agenda<00:01:32.840> today<00:01:33.159> is<00:01:33.320> that<00:01:33.520> they're 00:01:33.789 --> 00:01:33.799 align:start position:0% yeah the agenda today is that they're 00:01:33.799 --> 00:01:35.630 align:start position:0% yeah the agenda today is that they're actually<00:01:34.040> quite<00:01:34.240> hard<00:01:34.439> to<00:01:34.640> get<00:01:35.280> I<00:01:35.399> hope<00:01:35.520> you 00:01:35.630 --> 00:01:35.640 align:start position:0% actually quite hard to get I hope you 00:01:35.640 --> 00:01:38.749 align:start position:0% actually quite hard to get I hope you got<00:01:35.840> that<00:01:36.000> notion<00:01:36.280> from<00:01:36.479> Lucas<00:01:37.240> St<00:01:38.240> uh<00:01:38.479> all<00:01:38.640> the 00:01:38.749 --> 00:01:38.759 align:start position:0% got that notion from Lucas St uh all the 00:01:38.759 --> 00:01:40.630 align:start position:0% got that notion from Lucas St uh all the previous<00:01:39.079> attempts<00:01:39.439> were<00:01:39.640> either<00:01:39.960> unsafe 00:01:40.630 --> 00:01:40.640 align:start position:0% previous attempts were either unsafe 00:01:40.640 --> 00:01:43.670 align:start position:0% previous attempts were either unsafe centralized<00:01:41.280> or<00:01:41.439> slow<00:01:42.320> and<00:01:42.520> Dave<00:01:42.799> is 00:01:43.670 --> 00:01:43.680 align:start position:0% centralized or slow and Dave is 00:01:43.680 --> 00:01:46.590 align:start position:0% centralized or slow and Dave is not<00:01:44.680> yeah<00:01:44.960> so<00:01:45.240> fraud<00:01:45.560> proofs<00:01:45.799> are<00:01:45.960> in<00:01:46.040> a<00:01:46.200> diff 00:01:46.590 --> 00:01:46.600 align:start position:0% not yeah so fraud proofs are in a diff 00:01:46.600 --> 00:01:48.950 align:start position:0% not yeah so fraud proofs are in a diff uh<00:01:46.960> difficult<00:01:47.200> position<00:01:47.640> right<00:01:47.840> now<00:01:48.680> so<00:01:48.840> we 00:01:48.950 --> 00:01:48.960 align:start position:0% uh difficult position right now so we 00:01:48.960 --> 00:01:50.350 align:start position:0% uh difficult position right now so we have<00:01:49.119> the<00:01:49.280> pressure<00:01:49.680> you<00:01:49.799> know<00:01:49.960> on<00:01:50.040> the<00:01:50.200> top 00:01:50.350 --> 00:01:50.360 align:start position:0% have the pressure you know on the top 00:01:50.360 --> 00:01:52.429 align:start position:0% have the pressure you know on the top there's<00:01:50.600> vitalic<00:01:51.000> Suite<00:01:52.000> essentially 00:01:52.429 --> 00:01:52.439 align:start position:0% there's vitalic Suite essentially 00:01:52.439 --> 00:01:55.109 align:start position:0% there's vitalic Suite essentially calling<00:01:52.719> for<00:01:53.040> stricter<00:01:53.640> standards<00:01:54.640> but<00:01:54.880> if<00:01:55.000> we 00:01:55.109 --> 00:01:55.119 align:start position:0% calling for stricter standards but if we 00:01:55.119 --> 00:01:57.749 align:start position:0% calling for stricter standards but if we look<00:01:55.280> at<00:01:55.399> L2<00:01:55.840> beat<00:01:56.360> we<00:01:56.479> don't<00:01:56.680> see<00:01:56.880> full<00:01:57.200> pizzas 00:01:57.749 --> 00:01:57.759 align:start position:0% look at L2 beat we don't see full pizzas 00:01:57.759 --> 00:02:00.389 align:start position:0% look at L2 beat we don't see full pizzas right<00:01:57.960> so<00:01:58.119> we<00:01:58.240> have<00:01:58.479> the<00:01:59.200> pressure<00:02:00.079> but<00:02:00.280> we 00:02:00.389 --> 00:02:00.399 align:start position:0% right so we have the pressure but we 00:02:00.399 --> 00:02:02.670 align:start position:0% right so we have the pressure but we don't<00:02:00.680> have<00:02:01.039> implementations<00:02:01.719> coming<00:02:02.560> and 00:02:02.670 --> 00:02:02.680 align:start position:0% don't have implementations coming and 00:02:02.680 --> 00:02:04.429 align:start position:0% don't have implementations coming and the<00:02:02.840> reason<00:02:03.159> for<00:02:03.399> that<00:02:03.759> is<00:02:03.920> because<00:02:04.159> it's 00:02:04.429 --> 00:02:04.439 align:start position:0% the reason for that is because it's 00:02:04.439 --> 00:02:06.510 align:start position:0% the reason for that is because it's actually<00:02:04.759> quite<00:02:04.920> hard<00:02:05.119> to<00:02:05.320> get<00:02:05.479> fraud<00:02:05.840> proofs 00:02:06.510 --> 00:02:06.520 align:start position:0% actually quite hard to get fraud proofs 00:02:06.520 --> 00:02:09.109 align:start position:0% actually quite hard to get fraud proofs right<00:02:07.399> and<00:02:07.560> by<00:02:07.880> right<00:02:08.280> I<00:02:08.360> mean<00:02:08.599> essentially 00:02:09.109 --> 00:02:09.119 align:start position:0% right and by right I mean essentially 00:02:09.119 --> 00:02:11.510 align:start position:0% right and by right I mean essentially three<00:02:09.360> properties<00:02:09.840> the<00:02:09.959> first<00:02:10.200> who<00:02:10.399> are<00:02:10.599> there 00:02:11.510 --> 00:02:11.520 align:start position:0% three properties the first who are there 00:02:11.520 --> 00:02:13.869 align:start position:0% three properties the first who are there um<00:02:11.840> I<00:02:11.920> want<00:02:12.319> you<00:02:12.840> to<00:02:13.000> be<00:02:13.160> able<00:02:13.360> to<00:02:13.520> become<00:02:13.720> a 00:02:13.869 --> 00:02:13.879 align:start position:0% um I want you to be able to become a 00:02:13.879 --> 00:02:16.630 align:start position:0% um I want you to be able to become a validator<00:02:14.879> I<00:02:15.000> want<00:02:15.319> you<00:02:15.519> to<00:02:15.640> be<00:02:15.800> able<00:02:16.080> to<00:02:16.360> go 00:02:16.630 --> 00:02:16.640 align:start position:0% validator I want you to be able to go 00:02:16.640 --> 00:02:19.670 align:start position:0% validator I want you to be able to go there<00:02:17.519> without<00:02:17.840> a<00:02:18.239> supercomputer<00:02:19.239> without 00:02:19.670 --> 00:02:19.680 align:start position:0% there without a supercomputer without 00:02:19.680 --> 00:02:22.830 align:start position:0% there without a supercomputer without huge<00:02:20.000> ons<00:02:20.879> and<00:02:21.080> be<00:02:21.280> able<00:02:21.640> to<00:02:21.879> participate<00:02:22.720> in 00:02:22.830 --> 00:02:22.840 align:start position:0% huge ons and be able to participate in 00:02:22.840 --> 00:02:25.949 align:start position:0% huge ons and be able to participate in the<00:02:23.000> consensus<00:02:23.599> in<00:02:23.760> the<00:02:24.680> protocol<00:02:25.680> and<00:02:25.800> the 00:02:25.949 --> 00:02:25.959 align:start position:0% the consensus in the protocol and the 00:02:25.959 --> 00:02:27.990 align:start position:0% the consensus in the protocol and the second<00:02:26.319> property<00:02:26.840> is<00:02:26.959> that<00:02:27.239> I<00:02:27.360> want<00:02:27.640> that<00:02:27.800> you 00:02:27.990 --> 00:02:28.000 align:start position:0% second property is that I want that you 00:02:28.000 --> 00:02:30.229 align:start position:0% second property is that I want that you be<00:02:28.200> able<00:02:28.400> to<00:02:28.599> defeat<00:02:29.000> anyone<00:02:29.440> by<00:02:29.560> yourself 00:02:30.229 --> 00:02:30.239 align:start position:0% be able to defeat anyone by yourself 00:02:30.239 --> 00:02:32.030 align:start position:0% be able to defeat anyone by yourself even<00:02:30.440> if<00:02:30.560> you're<00:02:30.760> facing<00:02:31.239> against<00:02:31.519> a<00:02:31.640> nation 00:02:32.030 --> 00:02:32.040 align:start position:0% even if you're facing against a nation 00:02:32.040 --> 00:02:35.390 align:start position:0% even if you're facing against a nation state<00:02:32.920> so<00:02:33.120> if<00:02:33.239> you<00:02:33.400> get<00:02:33.680> those<00:02:33.840> two<00:02:34.400> properties 00:02:35.390 --> 00:02:35.400 align:start position:0% state so if you get those two properties 00:02:35.400 --> 00:02:37.550 align:start position:0% state so if you get those two properties to<00:02:35.680> defend<00:02:36.040> an<00:02:36.200> optimistic<00:02:36.680> roll<00:02:36.959> up<00:02:37.319> all<00:02:37.440> you 00:02:37.550 --> 00:02:37.560 align:start position:0% to defend an optimistic roll up all you 00:02:37.560 --> 00:02:39.350 align:start position:0% to defend an optimistic roll up all you have<00:02:37.680> to<00:02:37.800> do<00:02:37.959> is<00:02:38.040> set<00:02:38.239> up<00:02:38.360> a<00:02:38.480> note<00:02:38.840> on<00:02:39.000> your<00:02:39.120> own 00:02:39.350 --> 00:02:39.360 align:start position:0% have to do is set up a note on your own 00:02:39.360 --> 00:02:40.630 align:start position:0% have to do is set up a note on your own infrastructure<00:02:40.120> you<00:02:40.200> don't<00:02:40.360> need<00:02:40.480> to 00:02:40.630 --> 00:02:40.640 align:start position:0% infrastructure you don't need to 00:02:40.640 --> 00:02:43.030 align:start position:0% infrastructure you don't need to delegate<00:02:41.080> trust<00:02:41.440> to<00:02:41.599> anybody<00:02:42.000> else<00:02:42.760> we 00:02:43.030 --> 00:02:43.040 align:start position:0% delegate trust to anybody else we 00:02:43.040 --> 00:02:46.229 align:start position:0% delegate trust to anybody else we inherit<00:02:43.720> the<00:02:43.920> security<00:02:44.480> of<00:02:44.599> the<00:02:44.760> base<00:02:45.239> layer 00:02:46.229 --> 00:02:46.239 align:start position:0% inherit the security of the base layer 00:02:46.239 --> 00:02:49.229 align:start position:0% inherit the security of the base layer uh<00:02:46.360> so<00:02:46.720> those<00:02:46.879> are<00:02:47.120> like<00:02:47.280> the<00:02:47.480> two<00:02:47.920> like<00:02:48.920> uh 00:02:49.229 --> 00:02:49.239 align:start position:0% uh so those are like the two like uh 00:02:49.239 --> 00:02:51.509 align:start position:0% uh so those are like the two like uh oneof<00:02:49.640> end<00:02:49.879> property<00:02:50.280> and<00:02:50.440> we<00:02:50.560> want<00:02:50.720> it<00:02:50.840> to<00:02:50.959> be 00:02:51.509 --> 00:02:51.519 align:start position:0% oneof end property and we want it to be 00:02:51.519 --> 00:02:53.470 align:start position:0% oneof end property and we want it to be decentralized<00:02:52.519> uh<00:02:52.640> and<00:02:52.800> the<00:02:52.959> next<00:02:53.159> one<00:02:53.360> is 00:02:53.470 --> 00:02:53.480 align:start position:0% decentralized uh and the next one is 00:02:53.480 --> 00:02:55.309 align:start position:0% decentralized uh and the next one is that<00:02:53.640> we<00:02:53.800> want<00:02:54.080> settlement<00:02:54.560> to<00:02:54.800> happen 00:02:55.309 --> 00:02:55.319 align:start position:0% that we want settlement to happen 00:02:55.319 --> 00:02:57.470 align:start position:0% that we want settlement to happen without<00:02:55.680> large<00:02:56.000> delays<00:02:56.440> we<00:02:56.560> want<00:02:57.080> settlement 00:02:57.470 --> 00:02:57.480 align:start position:0% without large delays we want settlement 00:02:57.480 --> 00:03:00.470 align:start position:0% without large delays we want settlement to<00:02:57.680> happen<00:02:58.040> quickly<00:02:59.040> so<00:02:59.280> let<00:02:59.440> me<00:02:59.560> run 00:03:00.470 --> 00:03:00.480 align:start position:0% to happen quickly so let me run 00:03:00.480 --> 00:03:02.270 align:start position:0% to happen quickly so let me run all<00:03:00.599> the<00:03:00.720> three<00:03:00.920> of<00:03:01.000> them<00:03:01.319> together<00:03:01.920> uh<00:03:02.080> they 00:03:02.270 --> 00:03:02.280 align:start position:0% all the three of them together uh they 00:03:02.280 --> 00:03:04.830 align:start position:0% all the three of them together uh they kind<00:03:02.440> of<00:03:02.599> look<00:03:02.920> like<00:03:03.239> this<00:03:03.959> you<00:03:04.120> know 00:03:04.830 --> 00:03:04.840 align:start position:0% kind of look like this you know 00:03:04.840 --> 00:03:06.589 align:start position:0% kind of look like this you know decentralization<00:03:05.840> I<00:03:05.920> want<00:03:06.080> you<00:03:06.200> to<00:03:06.319> be<00:03:06.400> able 00:03:06.589 --> 00:03:06.599 align:start position:0% decentralization I want you to be able 00:03:06.599 --> 00:03:08.990 align:start position:0% decentralization I want you to be able to<00:03:06.879> participate<00:03:07.879> without<00:03:08.200> a<00:03:08.280> supercomputer 00:03:08.990 --> 00:03:09.000 align:start position:0% to participate without a supercomputer 00:03:09.000 --> 00:03:11.390 align:start position:0% to participate without a supercomputer or<00:03:09.239> huge<00:03:09.560> bonds<00:03:10.560> there<00:03:10.640> is<00:03:10.799> security<00:03:11.280> which 00:03:11.390 --> 00:03:11.400 align:start position:0% or huge bonds there is security which 00:03:11.400 --> 00:03:13.430 align:start position:0% or huge bonds there is security which means<00:03:11.599> that<00:03:11.760> tvl<00:03:12.200> cannot<00:03:12.480> be<00:03:12.640> stolen<00:03:13.120> even<00:03:13.319> if 00:03:13.430 --> 00:03:13.440 align:start position:0% means that tvl cannot be stolen even if 00:03:13.440 --> 00:03:15.710 align:start position:0% means that tvl cannot be stolen even if you're<00:03:13.599> facing<00:03:13.920> against<00:03:14.159> this<00:03:14.360> nation<00:03:14.720> state 00:03:15.710 --> 00:03:15.720 align:start position:0% you're facing against this nation state 00:03:15.720 --> 00:03:18.630 align:start position:0% you're facing against this nation state uh<00:03:16.000> and<00:03:16.400> liess<00:03:17.159> no<00:03:17.319> large<00:03:17.599> delays<00:03:18.440> and<00:03:18.519> you 00:03:18.630 --> 00:03:18.640 align:start position:0% uh and liess no large delays and you 00:03:18.640 --> 00:03:20.229 align:start position:0% uh and liess no large delays and you might<00:03:18.840> be<00:03:19.000> getting<00:03:19.319> some<00:03:19.519> flashbacks<00:03:20.159> you 00:03:20.229 --> 00:03:20.239 align:start position:0% might be getting some flashbacks you 00:03:20.239 --> 00:03:22.149 align:start position:0% might be getting some flashbacks you know<00:03:20.440> like<00:03:20.560> some<00:03:20.720> PTSD<00:03:21.400> like<00:03:21.560> oh<00:03:21.720> no<00:03:21.920> do<00:03:22.040> we 00:03:22.149 --> 00:03:22.159 align:start position:0% know like some PTSD like oh no do we 00:03:22.159 --> 00:03:24.710 align:start position:0% know like some PTSD like oh no do we have<00:03:22.280> another<00:03:22.720> trma<00:03:23.720> and<00:03:24.040> yeah<00:03:24.239> kind<00:03:24.400> of<00:03:24.599> you 00:03:24.710 --> 00:03:24.720 align:start position:0% have another trma and yeah kind of you 00:03:24.720 --> 00:03:26.509 align:start position:0% have another trma and yeah kind of you know<00:03:24.879> it's<00:03:25.080> actually<00:03:25.599> quite<00:03:25.799> hard<00:03:26.040> to<00:03:26.200> get<00:03:26.360> the 00:03:26.509 --> 00:03:26.519 align:start position:0% know it's actually quite hard to get the 00:03:26.519 --> 00:03:29.149 align:start position:0% know it's actually quite hard to get the three<00:03:26.680> of<00:03:26.840> them<00:03:27.080> at<00:03:27.239> the<00:03:27.360> same<00:03:27.760> time<00:03:28.760> uh<00:03:29.000> and 00:03:29.149 --> 00:03:29.159 align:start position:0% three of them at the same time uh and 00:03:29.159 --> 00:03:31.750 align:start position:0% three of them at the same time uh and you<00:03:29.280> can<00:03:29.480> always<00:03:29.920> naively<00:03:30.840> go<00:03:31.200> from<00:03:31.480> one 00:03:31.750 --> 00:03:31.760 align:start position:0% you can always naively go from one 00:03:31.760 --> 00:03:35.390 align:start position:0% you can always naively go from one vertex<00:03:32.239> to<00:03:32.400> the<00:03:32.560> other<00:03:33.560> um<00:03:34.560> but<00:03:34.720> you<00:03:34.920> sacrifice 00:03:35.390 --> 00:03:35.400 align:start position:0% vertex to the other um but you sacrifice 00:03:35.400 --> 00:03:36.710 align:start position:0% vertex to the other um but you sacrifice one<00:03:35.519> to<00:03:35.680> gain<00:03:35.879> the<00:03:35.959> other<00:03:36.120> you<00:03:36.200> know<00:03:36.319> so<00:03:36.560> you 00:03:36.710 --> 00:03:36.720 align:start position:0% one to gain the other you know so you 00:03:36.720 --> 00:03:38.550 align:start position:0% one to gain the other you know so you can<00:03:36.920> take<00:03:37.080> this<00:03:37.239> straight<00:03:37.519> off<00:03:38.080> so<00:03:38.200> it<00:03:38.319> does 00:03:38.550 --> 00:03:38.560 align:start position:0% can take this straight off so it does 00:03:38.560 --> 00:03:40.350 align:start position:0% can take this straight off so it does look<00:03:38.760> like<00:03:38.920> a<00:03:39.120> a<00:03:39.280> real 00:03:40.350 --> 00:03:40.360 align:start position:0% look like a a real 00:03:40.360 --> 00:03:42.789 align:start position:0% look like a a real trma<00:03:41.360> and<00:03:41.439> the<00:03:41.599> reason<00:03:41.840> for<00:03:42.040> that<00:03:42.239> is<00:03:42.360> Cil 00:03:42.789 --> 00:03:42.799 align:start position:0% trma and the reason for that is Cil 00:03:42.799 --> 00:03:44.910 align:start position:0% trma and the reason for that is Cil attacks<00:03:43.560> uh<00:03:43.680> I<00:03:43.760> will<00:03:43.959> zoom<00:03:44.200> in<00:03:44.360> on<00:03:44.560> only<00:03:44.760> the 00:03:44.910 --> 00:03:44.920 align:start position:0% attacks uh I will zoom in on only the 00:03:44.920 --> 00:03:46.589 align:start position:0% attacks uh I will zoom in on only the first<00:03:45.120> one<00:03:45.319> which<00:03:45.439> is<00:03:45.599> resource<00:03:46.120> exhaustion 00:03:46.589 --> 00:03:46.599 align:start position:0% first one which is resource exhaustion 00:03:46.599 --> 00:03:48.869 align:start position:0% first one which is resource exhaustion attacks<00:03:47.319> it's<00:03:47.439> like<00:03:47.560> a<00:03:47.720> Spam<00:03:48.120> attack<00:03:48.720> where 00:03:48.869 --> 00:03:48.879 align:start position:0% attacks it's like a Spam attack where 00:03:48.879 --> 00:03:51.309 align:start position:0% attacks it's like a Spam attack where you<00:03:49.000> create<00:03:49.400> like<00:03:49.519> a<00:03:49.720> huge<00:03:50.000> number<00:03:50.239> of<00:03:50.360> sibbles 00:03:51.309 --> 00:03:51.319 align:start position:0% you create like a huge number of sibbles 00:03:51.319 --> 00:03:53.509 align:start position:0% you create like a huge number of sibbles and<00:03:51.400> you<00:03:51.599> just<00:03:51.799> drain<00:03:52.280> the<00:03:52.439> funds<00:03:52.879> of<00:03:53.040> the<00:03:53.200> Hest 00:03:53.509 --> 00:03:53.519 align:start position:0% and you just drain the funds of the Hest 00:03:53.519 --> 00:03:55.390 align:start position:0% and you just drain the funds of the Hest validator<00:03:54.239> until<00:03:54.519> they<00:03:54.640> can<00:03:54.840> no<00:03:55.000> longer 00:03:55.390 --> 00:03:55.400 align:start position:0% validator until they can no longer 00:03:55.400 --> 00:03:56.910 align:start position:0% validator until they can no longer participate<00:03:55.879> in<00:03:56.000> the<00:03:56.159> game<00:03:56.439> and<00:03:56.560> then<00:03:56.640> you<00:03:56.760> can 00:03:56.910 --> 00:03:56.920 align:start position:0% participate in the game and then you can 00:03:56.920 --> 00:03:59.990 align:start position:0% participate in the game and then you can steal<00:03:57.239> the<00:03:57.599> tvl<00:03:58.599> uh<00:03:58.720> so<00:03:58.879> this<00:03:59.000> is<00:03:59.079> a<00:03:59.200> Cil<00:03:59.519> attack 00:03:59.990 --> 00:04:00.000 align:start position:0% steal the tvl uh so this is a Cil attack 00:04:00.000 --> 00:04:01.589 align:start position:0% steal the tvl uh so this is a Cil attack that<00:04:00.159> targets<00:04:00.599> the<00:04:00.760> security<00:04:01.319> of<00:04:01.480> the 00:04:01.589 --> 00:04:01.599 align:start position:0% that targets the security of the 00:04:01.599 --> 00:04:04.910 align:start position:0% that targets the security of the algorithm<00:04:02.560> and<00:04:02.680> there<00:04:02.799> are<00:04:03.079> mitigation<00:04:04.079> um 00:04:04.910 --> 00:04:04.920 align:start position:0% algorithm and there are mitigation um 00:04:04.920 --> 00:04:07.350 align:start position:0% algorithm and there are mitigation um strategies<00:04:05.640> but<00:04:05.799> they<00:04:06.000> end<00:04:06.200> up<00:04:06.480> restricting 00:04:07.350 --> 00:04:07.360 align:start position:0% strategies but they end up restricting 00:04:07.360 --> 00:04:10.470 align:start position:0% strategies but they end up restricting participation<00:04:08.360> and<00:04:08.599> thus<00:04:08.959> harming 00:04:10.470 --> 00:04:10.480 align:start position:0% participation and thus harming 00:04:10.480 --> 00:04:12.270 align:start position:0% participation and thus harming decentralization<00:04:11.480> uh<00:04:11.560> so<00:04:11.720> there<00:04:11.840> are<00:04:12.000> three 00:04:12.270 --> 00:04:12.280 align:start position:0% decentralization uh so there are three 00:04:12.280 --> 00:04:14.309 align:start position:0% decentralization uh so there are three main<00:04:13.040> uh<00:04:13.159> solutions<00:04:13.599> that<00:04:13.799> we<00:04:13.920> will<00:04:14.120> talk 00:04:14.309 --> 00:04:14.319 align:start position:0% main uh solutions that we will talk 00:04:14.319 --> 00:04:16.189 align:start position:0% main uh solutions that we will talk today<00:04:14.799> there<00:04:14.920> are<00:04:15.079> several<00:04:15.400> others<00:04:15.840> but<00:04:16.000> we'll 00:04:16.189 --> 00:04:16.199 align:start position:0% today there are several others but we'll 00:04:16.199 --> 00:04:18.789 align:start position:0% today there are several others but we'll talk<00:04:16.400> about<00:04:16.680> these<00:04:16.880> two<00:04:17.799> the<00:04:17.959> first<00:04:18.199> two<00:04:18.440> is<00:04:18.600> by 00:04:18.789 --> 00:04:18.799 align:start position:0% talk about these two the first two is by 00:04:18.799 --> 00:04:21.229 align:start position:0% talk about these two the first two is by optimism<00:04:19.440> optimism<00:04:19.959> fault<00:04:20.359> proof<00:04:20.919> uh<00:04:21.000> there's 00:04:21.229 --> 00:04:21.239 align:start position:0% optimism optimism fault proof uh there's 00:04:21.239 --> 00:04:24.790 align:start position:0% optimism optimism fault proof uh there's also<00:04:21.479> arbitrum<00:04:22.520> bold<00:04:23.520> and<00:04:23.880> our<00:04:24.160> own 00:04:24.790 --> 00:04:24.800 align:start position:0% also arbitrum bold and our own 00:04:24.800 --> 00:04:27.150 align:start position:0% also arbitrum bold and our own permissionless<00:04:25.520> referee<00:04:26.000> tournaments<00:04:26.680> PRT 00:04:27.150 --> 00:04:27.160 align:start position:0% permissionless referee tournaments PRT 00:04:27.160 --> 00:04:29.029 align:start position:0% permissionless referee tournaments PRT for<00:04:27.400> short<00:04:27.800> this<00:04:27.919> is<00:04:28.040> the<00:04:28.199> previous<00:04:28.520> algorithm 00:04:29.029 --> 00:04:29.039 align:start position:0% for short this is the previous algorithm 00:04:29.039 --> 00:04:31.070 align:start position:0% for short this is the previous algorithm we<00:04:29.199> did<00:04:29.840> that<00:04:29.960> was<00:04:30.120> our<00:04:30.320> first<00:04:30.600> attempt<00:04:30.960> at 00:04:31.070 --> 00:04:31.080 align:start position:0% we did that was our first attempt at 00:04:31.080 --> 00:04:33.909 align:start position:0% we did that was our first attempt at cracking<00:04:31.880> this<00:04:32.880> uh<00:04:33.039> and<00:04:33.160> I<00:04:33.280> want<00:04:33.400> to<00:04:33.600> highlight 00:04:33.909 --> 00:04:33.919 align:start position:0% cracking this uh and I want to highlight 00:04:33.919 --> 00:04:36.870 align:start position:0% cracking this uh and I want to highlight the<00:04:34.080> very<00:04:34.240> important<00:04:34.680> fact<00:04:35.160> that<00:04:35.600> the<00:04:35.880> top<00:04:36.520> two 00:04:36.870 --> 00:04:36.880 align:start position:0% the very important fact that the top two 00:04:36.880 --> 00:04:39.670 align:start position:0% the very important fact that the top two you<00:04:36.960> know<00:04:37.120> the<00:04:37.240> first<00:04:37.720> two<00:04:38.720> uh<00:04:38.880> if<00:04:39.000> you<00:04:39.240> look<00:04:39.560> at 00:04:39.670 --> 00:04:39.680 align:start position:0% you know the first two uh if you look at 00:04:39.680 --> 00:04:42.749 align:start position:0% you know the first two uh if you look at the<00:04:39.880> tvl<00:04:40.479> Distribution<00:04:41.039> on<00:04:41.199> L2<00:04:41.600> beat<00:04:42.479> pretty 00:04:42.749 --> 00:04:42.759 align:start position:0% the tvl Distribution on L2 beat pretty 00:04:42.759 --> 00:04:45.469 align:start position:0% the tvl Distribution on L2 beat pretty much<00:04:43.080> most<00:04:43.320> of<00:04:43.520> it<00:04:44.120> is<00:04:44.280> being<00:04:44.600> protected<00:04:45.320> by 00:04:45.469 --> 00:04:45.479 align:start position:0% much most of it is being protected by 00:04:45.479 --> 00:04:47.189 align:start position:0% much most of it is being protected by those<00:04:45.759> first<00:04:46.039> two<00:04:46.240> you<00:04:46.360> know<00:04:46.520> it's<00:04:46.680> either<00:04:46.880> an 00:04:47.189 --> 00:04:47.199 align:start position:0% those first two you know it's either an 00:04:47.199 --> 00:04:50.189 align:start position:0% those first two you know it's either an OP<00:04:47.560> chain<00:04:47.960> or<00:04:48.160> an<00:04:48.320> arbitrum<00:04:48.800> chain<00:04:49.639> so<00:04:49.960> we<00:04:50.039> need 00:04:50.189 --> 00:04:50.199 align:start position:0% OP chain or an arbitrum chain so we need 00:04:50.199 --> 00:04:52.029 align:start position:0% OP chain or an arbitrum chain so we need to<00:04:50.360> keep<00:04:50.520> this<00:04:50.680> in<00:04:50.840> mind<00:04:51.360> because<00:04:51.600> we<00:04:51.680> need<00:04:51.840> to 00:04:52.029 --> 00:04:52.039 align:start position:0% to keep this in mind because we need to 00:04:52.039 --> 00:04:54.469 align:start position:0% to keep this in mind because we need to take<00:04:52.919> the<00:04:53.080> analysis<00:04:53.520> of<00:04:53.720> these<00:04:53.840> algorithms 00:04:54.469 --> 00:04:54.479 align:start position:0% take the analysis of these algorithms 00:04:54.479 --> 00:04:57.110 align:start position:0% take the analysis of these algorithms quite<00:04:55.120> seriously<00:04:56.120> uh<00:04:56.240> so<00:04:56.400> this<00:04:56.479> is<00:04:56.600> the<00:04:56.759> sneak 00:04:57.110 --> 00:04:57.120 align:start position:0% quite seriously uh so this is the sneak 00:04:57.120 --> 00:04:59.790 align:start position:0% quite seriously uh so this is the sneak peek<00:04:57.880> comparison<00:04:58.560> between<00:04:59.039> you<00:04:59.160> know<00:04:59.400> those 00:04:59.790 --> 00:04:59.800 align:start position:0% peek comparison between you know those 00:04:59.800 --> 00:05:01.469 align:start position:0% peek comparison between you know those three<00:05:00.240> and<00:05:00.400> the<00:05:00.520> one<00:05:00.680> we're<00:05:00.800> going<00:05:00.919> to<00:05:01.039> present 00:05:01.469 --> 00:05:01.479 align:start position:0% three and the one we're going to present 00:05:01.479 --> 00:05:04.390 align:start position:0% three and the one we're going to present today<00:05:02.479> and<00:05:02.680> the<00:05:02.840> columns<00:05:03.360> they<00:05:03.560> map<00:05:04.039> directly 00:05:04.390 --> 00:05:04.400 align:start position:0% today and the columns they map directly 00:05:04.400 --> 00:05:07.270 align:start position:0% today and the columns they map directly to<00:05:04.639> those<00:05:04.800> three<00:05:05.280> properties<00:05:06.280> so<00:05:06.680> for<00:05:06.880> example 00:05:07.270 --> 00:05:07.280 align:start position:0% to those three properties so for example 00:05:07.280 --> 00:05:10.710 align:start position:0% to those three properties so for example bonds<00:05:07.919> uh<00:05:08.039> if<00:05:08.120> you<00:05:08.280> look<00:05:08.440> at<00:05:08.600> bold<00:05:09.160> you<00:05:09.320> need 00:05:10.710 --> 00:05:10.720 align:start position:0% bonds uh if you look at bold you need 00:05:10.720 --> 00:05:13.909 align:start position:0% bonds uh if you look at bold you need 3,600<00:05:11.720> eth<00:05:12.639> to<00:05:12.840> become<00:05:13.039> a<00:05:13.199> validator<00:05:13.720> so<00:05:13.840> it's 00:05:13.909 --> 00:05:13.919 align:start position:0% 3,600 eth to become a validator so it's 00:05:13.919 --> 00:05:17.070 align:start position:0% 3,600 eth to become a validator so it's a<00:05:14.080> very<00:05:14.280> high<00:05:14.520> Bond<00:05:15.199> uh<00:05:15.560> value<00:05:16.560> and<00:05:16.680> this<00:05:16.840> has<00:05:16.960> a 00:05:17.070 --> 00:05:17.080 align:start position:0% a very high Bond uh value and this has a 00:05:17.080 --> 00:05:19.309 align:start position:0% a very high Bond uh value and this has a centralization<00:05:17.880> effect<00:05:18.280> so<00:05:18.479> the<00:05:18.600> bond<00:05:18.880> colum 00:05:19.309 --> 00:05:19.319 align:start position:0% centralization effect so the bond colum 00:05:19.319 --> 00:05:21.749 align:start position:0% centralization effect so the bond colum is<00:05:19.440> related<00:05:19.759> to<00:05:20.440> centralization 00:05:21.749 --> 00:05:21.759 align:start position:0% is related to centralization 00:05:21.759 --> 00:05:24.350 align:start position:0% is related to centralization decentralization<00:05:22.759> now<00:05:23.080> expenses<00:05:23.800> oh<00:05:24.000> just<00:05:24.120> to 00:05:24.350 --> 00:05:24.360 align:start position:0% decentralization now expenses oh just to 00:05:24.360 --> 00:05:26.270 align:start position:0% decentralization now expenses oh just to you<00:05:24.479> know<00:05:24.680> highlight<00:05:25.120> this<00:05:25.440> uh<00:05:25.639> this<00:05:25.720> is<00:05:25.840> a<00:05:26.039> 1 00:05:26.270 --> 00:05:26.280 align:start position:0% you know highlight this uh this is a 1 00:05:26.280 --> 00:05:28.749 align:start position:0% you know highlight this uh this is a 1 million<00:05:26.680> ether<00:05:27.080> attack<00:05:27.600> scenario<00:05:28.440> so<00:05:28.600> we 00:05:28.749 --> 00:05:28.759 align:start position:0% million ether attack scenario so we 00:05:28.759 --> 00:05:30.590 align:start position:0% million ether attack scenario so we assume<00:05:29.160> that<00:05:29.280> the<00:05:29.680> adversary<00:05:30.080> is<00:05:30.199> willing<00:05:30.440> to 00:05:30.590 --> 00:05:30.600 align:start position:0% assume that the adversary is willing to 00:05:30.600 --> 00:05:33.309 align:start position:0% assume that the adversary is willing to burn<00:05:30.960> that<00:05:31.120> amount<00:05:31.360> of<00:05:31.520> money<00:05:32.520> uh<00:05:32.919> in<00:05:33.080> that 00:05:33.309 --> 00:05:33.319 align:start position:0% burn that amount of money uh in that 00:05:33.319 --> 00:05:38.350 align:start position:0% burn that amount of money uh in that case<00:05:34.280> uh<00:05:35.080> if<00:05:35.280> it's<00:05:35.479> a<00:05:35.800> op<00:05:36.720> uh<00:05:36.800> fault<00:05:37.199> proof<00:05:38.160> the 00:05:38.350 --> 00:05:38.360 align:start position:0% case uh if it's a op uh fault proof the 00:05:38.360 --> 00:05:41.070 align:start position:0% case uh if it's a op uh fault proof the defender<00:05:38.919> has<00:05:39.080> to<00:05:39.280> match<00:05:39.720> those<00:05:39.960> funds<00:05:40.639> so<00:05:40.960> if 00:05:41.070 --> 00:05:41.080 align:start position:0% defender has to match those funds so if 00:05:41.080 --> 00:05:43.350 align:start position:0% defender has to match those funds so if you<00:05:41.199> don't<00:05:41.479> have<00:05:41.680> also<00:05:42.039> 1<00:05:42.199> million<00:05:42.520> ether<00:05:43.240> you 00:05:43.350 --> 00:05:43.360 align:start position:0% you don't have also 1 million ether you 00:05:43.360 --> 00:05:45.350 align:start position:0% you don't have also 1 million ether you will<00:05:43.560> lose<00:05:43.800> the<00:05:43.960> tvl<00:05:44.560> so<00:05:44.759> that<00:05:44.960> colume 00:05:45.350 --> 00:05:45.360 align:start position:0% will lose the tvl so that colume 00:05:45.360 --> 00:05:48.110 align:start position:0% will lose the tvl so that colume expenses<00:05:45.919> maps<00:05:46.280> to<00:05:46.520> security<00:05:47.479> and<00:05:47.600> finally<00:05:47.960> we 00:05:48.110 --> 00:05:48.120 align:start position:0% expenses maps to security and finally we 00:05:48.120 --> 00:05:50.670 align:start position:0% expenses maps to security and finally we have<00:05:48.280> delay<00:05:49.000> uh<00:05:49.120> if<00:05:49.199> you<00:05:49.319> look<00:05:49.479> at<00:05:49.600> our<00:05:49.759> own<00:05:50.560> if 00:05:50.670 --> 00:05:50.680 align:start position:0% have delay uh if you look at our own if 00:05:50.680 --> 00:05:52.150 align:start position:0% have delay uh if you look at our own if there's<00:05:50.960> this<00:05:51.120> 1<00:05:51.319> million<00:05:51.600> ether<00:05:51.919> attack 00:05:52.150 --> 00:05:52.160 align:start position:0% there's this 1 million ether attack 00:05:52.160 --> 00:05:53.830 align:start position:0% there's this 1 million ether attack civil<00:05:52.520> attack 00:05:53.830 --> 00:05:53.840 align:start position:0% civil attack 00:05:53.840 --> 00:05:56.670 align:start position:0% civil attack um<00:05:54.840> you<00:05:55.039> get<00:05:55.240> 20<00:05:55.520> weeks<00:05:55.759> delay<00:05:56.120> which<00:05:56.240> is<00:05:56.400> also 00:05:56.670 --> 00:05:56.680 align:start position:0% um you get 20 weeks delay which is also 00:05:56.680 --> 00:05:58.590 align:start position:0% um you get 20 weeks delay which is also quite<00:05:56.919> high<00:05:57.199> so<00:05:57.360> you<00:05:57.479> know<00:05:57.880> none<00:05:58.080> of<00:05:58.199> the<00:05:58.360> three 00:05:58.590 --> 00:05:58.600 align:start position:0% quite high so you know none of the three 00:05:58.600 --> 00:06:00.230 align:start position:0% quite high so you know none of the three we<00:05:58.720> feel<00:05:58.919> are<00:05:59.080> quite<00:05:59.280> adequate 00:06:00.230 --> 00:06:00.240 align:start position:0% we feel are quite adequate 00:06:00.240 --> 00:06:01.710 align:start position:0% we feel are quite adequate and<00:06:00.360> today<00:06:00.600> we<00:06:00.680> will<00:06:00.880> present<00:06:01.240> Dave<00:06:01.520> which<00:06:01.600> is 00:06:01.710 --> 00:06:01.720 align:start position:0% and today we will present Dave which is 00:06:01.720 --> 00:06:03.990 align:start position:0% and today we will present Dave which is on<00:06:01.880> the<00:06:02.039> bottom<00:06:02.880> which<00:06:03.199> strikes<00:06:03.639> a<00:06:03.800> good 00:06:03.990 --> 00:06:04.000 align:start position:0% on the bottom which strikes a good 00:06:04.000 --> 00:06:06.150 align:start position:0% on the bottom which strikes a good balance<00:06:04.360> across<00:06:04.840> all<00:06:05.160> three<00:06:05.440> of 00:06:06.150 --> 00:06:06.160 align:start position:0% balance across all three of 00:06:06.160 --> 00:06:10.230 align:start position:0% balance across all three of them<00:06:07.280> cool<00:06:08.280> so<00:06:08.639> let's<00:06:09.000> talk<00:06:09.360> about<00:06:09.639> some<00:06:09.880> basic 00:06:10.230 --> 00:06:10.240 align:start position:0% them cool so let's talk about some basic 00:06:10.240 --> 00:06:12.870 align:start position:0% them cool so let's talk about some basic concepts<00:06:10.720> of<00:06:11.240> fraud 00:06:12.870 --> 00:06:12.880 align:start position:0% concepts of fraud 00:06:12.880 --> 00:06:16.390 align:start position:0% concepts of fraud proofs<00:06:13.880> uh<00:06:14.360> okay<00:06:14.599> so<00:06:14.840> first<00:06:15.080> our<00:06:15.280> threat<00:06:15.639> model 00:06:16.390 --> 00:06:16.400 align:start position:0% proofs uh okay so first our threat model 00:06:16.400 --> 00:06:19.029 align:start position:0% proofs uh okay so first our threat model uh<00:06:16.520> we<00:06:16.680> assume<00:06:17.080> that<00:06:17.199> the<00:06:17.319> layer<00:06:17.639> one<00:06:18.039> works 00:06:19.029 --> 00:06:19.039 align:start position:0% uh we assume that the layer one works 00:06:19.039 --> 00:06:20.830 align:start position:0% uh we assume that the layer one works however<00:06:19.440> we<00:06:19.599> also<00:06:19.880> assume<00:06:20.240> that<00:06:20.360> it<00:06:20.520> can<00:06:20.680> be 00:06:20.830 --> 00:06:20.840 align:start position:0% however we also assume that it can be 00:06:20.840 --> 00:06:23.629 align:start position:0% however we also assume that it can be censored<00:06:21.360> for<00:06:21.720> up<00:06:21.919> to<00:06:22.120> one<00:06:22.400> week<00:06:23.160> so<00:06:23.400> think 00:06:23.629 --> 00:06:23.639 align:start position:0% censored for up to one week so think 00:06:23.639 --> 00:06:25.710 align:start position:0% censored for up to one week so think like<00:06:23.880> a<00:06:24.280> censorship<00:06:24.919> budget<00:06:25.440> that<00:06:25.560> the 00:06:25.710 --> 00:06:25.720 align:start position:0% like a censorship budget that the 00:06:25.720 --> 00:06:28.430 align:start position:0% like a censorship budget that the adversary<00:06:26.319> has<00:06:26.960> and<00:06:27.120> they<00:06:27.240> can<00:06:27.520> spend<00:06:27.880> it<00:06:28.160> at 00:06:28.430 --> 00:06:28.440 align:start position:0% adversary has and they can spend it at 00:06:28.440 --> 00:06:31.189 align:start position:0% adversary has and they can spend it at will<00:06:29.400> and<00:06:29.639> we<00:06:29.759> also<00:06:29.960> assume<00:06:30.280> there<00:06:30.400> is<00:06:30.560> one<00:06:30.759> ons 00:06:31.189 --> 00:06:31.199 align:start position:0% will and we also assume there is one ons 00:06:31.199 --> 00:06:33.110 align:start position:0% will and we also assume there is one ons validator<00:06:32.039> which<00:06:32.440> we're<00:06:32.599> going<00:06:32.720> to<00:06:32.840> say<00:06:32.960> it's 00:06:33.110 --> 00:06:33.120 align:start position:0% validator which we're going to say it's 00:06:33.120 --> 00:06:36.070 align:start position:0% validator which we're going to say it's Willie<00:06:34.120> And<00:06:34.280> Willie<00:06:34.639> has<00:06:34.759> a<00:06:34.960> laptop<00:06:35.759> a<00:06:35.840> few 00:06:36.070 --> 00:06:36.080 align:start position:0% Willie And Willie has a laptop a few 00:06:36.080 --> 00:06:39.550 align:start position:0% Willie And Willie has a laptop a few ether<00:06:36.560> and<00:06:36.960> values<00:06:37.960> uh<00:06:38.120> hard 00:06:39.550 --> 00:06:39.560 align:start position:0% ether and values uh hard 00:06:39.560 --> 00:06:42.350 align:start position:0% ether and values uh hard values<00:06:40.560> so<00:06:40.720> we<00:06:40.880> begin<00:06:41.240> with<00:06:41.400> the<00:06:41.599> basic 00:06:42.350 --> 00:06:42.360 align:start position:0% values so we begin with the basic 00:06:42.360 --> 00:06:45.230 align:start position:0% values so we begin with the basic primitive<00:06:42.919> which<00:06:43.039> is<00:06:43.160> a<00:06:43.400> pairwise<00:06:44.240> reputation 00:06:45.230 --> 00:06:45.240 align:start position:0% primitive which is a pairwise reputation 00:06:45.240 --> 00:06:47.670 align:start position:0% primitive which is a pairwise reputation so<00:06:45.479> the<00:06:45.639> goal<00:06:45.960> is<00:06:46.120> that<00:06:46.440> well<00:06:46.599> you<00:06:46.800> have<00:06:47.360> uh<00:06:47.479> two 00:06:47.670 --> 00:06:47.680 align:start position:0% so the goal is that well you have uh two 00:06:47.680 --> 00:06:50.029 align:start position:0% so the goal is that well you have uh two players<00:06:48.039> we<00:06:48.160> have<00:06:48.520> Willie<00:06:49.400> the 00:06:50.029 --> 00:06:50.039 align:start position:0% players we have Willie the 00:06:50.039 --> 00:06:52.510 align:start position:0% players we have Willie the adversary<00:06:51.039> and<00:06:51.360> the<00:06:51.479> blockchain<00:06:52.000> acting<00:06:52.280> as<00:06:52.360> a 00:06:52.510 --> 00:06:52.520 align:start position:0% adversary and the blockchain acting as a 00:06:52.520 --> 00:06:54.629 align:start position:0% adversary and the blockchain acting as a referee<00:06:52.880> in<00:06:52.960> the<00:06:53.080> middle<00:06:53.840> and<00:06:54.039> those<00:06:54.240> two<00:06:54.479> will 00:06:54.629 --> 00:06:54.639 align:start position:0% referee in the middle and those two will 00:06:54.639 --> 00:06:56.670 align:start position:0% referee in the middle and those two will engage<00:06:54.919> in<00:06:55.039> a<00:06:55.199> dispute<00:06:55.919> to<00:06:56.160> prove<00:06:56.440> that<00:06:56.560> the 00:06:56.670 --> 00:06:56.680 align:start position:0% engage in a dispute to prove that the 00:06:56.680 --> 00:06:59.670 align:start position:0% engage in a dispute to prove that the other<00:06:57.000> is<00:06:57.560> wrong<00:06:58.560> uh<00:06:58.759> and<00:06:58.879> they<00:06:59.039> want<00:06:59.199> to<00:06:59.599> in 00:06:59.670 --> 00:06:59.680 align:start position:0% other is wrong uh and they want to in 00:06:59.680 --> 00:07:01.309 align:start position:0% other is wrong uh and they want to in the<00:06:59.759> end<00:07:00.039> the<00:07:00.240> the<00:07:00.360> goal<00:07:00.560> is<00:07:00.680> to<00:07:00.840> prove<00:07:01.120> the 00:07:01.309 --> 00:07:01.319 align:start position:0% the end the the goal is to prove the 00:07:01.319 --> 00:07:03.950 align:start position:0% the end the the goal is to prove the result<00:07:01.680> of<00:07:01.800> a<00:07:02.039> program<00:07:02.639> to<00:07:02.840> the<00:07:03.039> referee<00:07:03.879> and 00:07:03.950 --> 00:07:03.960 align:start position:0% result of a program to the referee and 00:07:03.960 --> 00:07:04.990 align:start position:0% result of a program to the referee and it's<00:07:04.120> interesting<00:07:04.520> because<00:07:04.680> they<00:07:04.840> don't 00:07:04.990 --> 00:07:05.000 align:start position:0% it's interesting because they don't 00:07:05.000 --> 00:07:07.029 align:start position:0% it's interesting because they don't prove<00:07:05.199> the<00:07:05.319> correct<00:07:05.680> result<00:07:06.039> directly<00:07:06.879> they 00:07:07.029 --> 00:07:07.039 align:start position:0% prove the correct result directly they 00:07:07.039 --> 00:07:09.070 align:start position:0% prove the correct result directly they prove<00:07:07.280> that<00:07:07.400> the<00:07:07.560> other<00:07:07.919> is<00:07:08.160> incorrect<00:07:08.919> and 00:07:09.070 --> 00:07:09.080 align:start position:0% prove that the other is incorrect and 00:07:09.080 --> 00:07:10.790 align:start position:0% prove that the other is incorrect and since<00:07:09.280> we<00:07:09.440> assume<00:07:09.759> will<00:07:10.080> is<00:07:10.240> there<00:07:10.440> he's<00:07:10.680> the 00:07:10.790 --> 00:07:10.800 align:start position:0% since we assume will is there he's the 00:07:10.800 --> 00:07:12.150 align:start position:0% since we assume will is there he's the one<00:07:10.960> who's<00:07:11.160> going<00:07:11.319> to<00:07:11.440> enforce<00:07:11.759> the<00:07:11.919> right 00:07:12.150 --> 00:07:12.160 align:start position:0% one who's going to enforce the right 00:07:12.160 --> 00:07:14.070 align:start position:0% one who's going to enforce the right result<00:07:12.919> because<00:07:13.120> he's<00:07:13.319> the<00:07:13.400> honest<00:07:13.759> one<00:07:13.960> you 00:07:14.070 --> 00:07:14.080 align:start position:0% result because he's the honest one you 00:07:14.080 --> 00:07:16.749 align:start position:0% result because he's the honest one you know<00:07:14.800> uh<00:07:15.800> yeah<00:07:15.960> so<00:07:16.120> they're<00:07:16.240> going<00:07:16.360> to<00:07:16.479> fight 00:07:16.749 --> 00:07:16.759 align:start position:0% know uh yeah so they're going to fight 00:07:16.759 --> 00:07:19.150 align:start position:0% know uh yeah so they're going to fight to<00:07:16.879> prove<00:07:17.160> the<00:07:17.319> correct<00:07:17.680> result<00:07:18.160> of<00:07:18.319> a<00:07:18.560> program 00:07:19.150 --> 00:07:19.160 align:start position:0% to prove the correct result of a program 00:07:19.160 --> 00:07:20.749 align:start position:0% to prove the correct result of a program now<00:07:19.400> what<00:07:19.520> do<00:07:19.599> we<00:07:19.720> mean<00:07:19.960> by 00:07:20.749 --> 00:07:20.759 align:start position:0% now what do we mean by 00:07:20.759 --> 00:07:23.589 align:start position:0% now what do we mean by program<00:07:21.759> the<00:07:21.919> computation<00:07:22.479> model<00:07:23.160> has<00:07:23.400> an 00:07:23.589 --> 00:07:23.599 align:start position:0% program the computation model has an 00:07:23.599 --> 00:07:25.749 align:start position:0% program the computation model has an initial<00:07:24.000> State<00:07:24.720> and<00:07:24.879> a<00:07:25.039> state<00:07:25.280> transition 00:07:25.749 --> 00:07:25.759 align:start position:0% initial State and a state transition 00:07:25.759 --> 00:07:28.469 align:start position:0% initial State and a state transition function<00:07:26.280> agreed<00:07:26.680> by<00:07:26.960> everyone<00:07:27.960> and<00:07:28.120> then<00:07:28.280> we 00:07:28.469 --> 00:07:28.479 align:start position:0% function agreed by everyone and then we 00:07:28.479 --> 00:07:30.469 align:start position:0% function agreed by everyone and then we apply<00:07:28.879> the<00:07:29.000> state<00:07:29.160> transition<00:07:29.759> function<00:07:30.280> over 00:07:30.469 --> 00:07:30.479 align:start position:0% apply the state transition function over 00:07:30.479 --> 00:07:32.749 align:start position:0% apply the state transition function over and<00:07:30.680> over<00:07:30.960> the<00:07:31.080> initial<00:07:31.479> State<00:07:32.039> until<00:07:32.360> we<00:07:32.520> get 00:07:32.749 --> 00:07:32.759 align:start position:0% and over the initial State until we get 00:07:32.759 --> 00:07:35.070 align:start position:0% and over the initial State until we get the<00:07:32.919> final<00:07:33.240> State<00:07:33.759> and<00:07:33.960> that<00:07:34.120> final<00:07:34.479> state<00:07:34.919> is 00:07:35.070 --> 00:07:35.080 align:start position:0% the final State and that final state is 00:07:35.080 --> 00:07:38.150 align:start position:0% the final State and that final state is the<00:07:35.280> result<00:07:35.720> of<00:07:35.919> the<00:07:36.120> program<00:07:37.039> that's<00:07:37.319> what<00:07:37.960> we 00:07:38.150 --> 00:07:38.160 align:start position:0% the result of the program that's what we 00:07:38.160 --> 00:07:40.430 align:start position:0% the result of the program that's what we are<00:07:38.400> trying<00:07:38.680> to<00:07:38.840> prove<00:07:39.080> to<00:07:39.240> the<00:07:39.440> blockchain 00:07:40.430 --> 00:07:40.440 align:start position:0% are trying to prove to the blockchain 00:07:40.440 --> 00:07:42.469 align:start position:0% are trying to prove to the blockchain and<00:07:40.599> the<00:07:40.720> intuition<00:07:41.400> of<00:07:41.520> a<00:07:41.680> reputation<00:07:42.240> game 00:07:42.469 --> 00:07:42.479 align:start position:0% and the intuition of a reputation game 00:07:42.479 --> 00:07:44.749 align:start position:0% and the intuition of a reputation game is<00:07:42.599> that<00:07:42.840> first<00:07:43.080> we're<00:07:43.280> going<00:07:43.440> to<00:07:43.599> perform<00:07:44.560> a 00:07:44.749 --> 00:07:44.759 align:start position:0% is that first we're going to perform a 00:07:44.759 --> 00:07:47.589 align:start position:0% is that first we're going to perform a binary<00:07:45.280> search<00:07:46.280> on<00:07:46.599> this<00:07:46.840> computation<00:07:47.479> and 00:07:47.589 --> 00:07:47.599 align:start position:0% binary search on this computation and 00:07:47.599 --> 00:07:50.309 align:start position:0% binary search on this computation and try<00:07:47.840> to<00:07:48.120> pinpoint<00:07:49.039> the<00:07:49.280> exact<00:07:49.840> State 00:07:50.309 --> 00:07:50.319 align:start position:0% try to pinpoint the exact State 00:07:50.319 --> 00:07:53.070 align:start position:0% try to pinpoint the exact State transition<00:07:50.960> that<00:07:51.120> they<00:07:51.400> first<00:07:51.840> disagreed<00:07:52.400> on 00:07:53.070 --> 00:07:53.080 align:start position:0% transition that they first disagreed on 00:07:53.080 --> 00:07:54.430 align:start position:0% transition that they first disagreed on because<00:07:53.360> if<00:07:53.560> they<00:07:53.680> agree<00:07:54.000> before<00:07:54.280> and 00:07:54.430 --> 00:07:54.440 align:start position:0% because if they agree before and 00:07:54.440 --> 00:07:56.670 align:start position:0% because if they agree before and disagree<00:07:54.879> after<00:07:55.599> somewhere<00:07:55.960> in<00:07:56.080> the<00:07:56.199> middle 00:07:56.670 --> 00:07:56.680 align:start position:0% disagree after somewhere in the middle 00:07:56.680 --> 00:07:59.629 align:start position:0% disagree after somewhere in the middle they<00:07:57.000> start<00:07:57.759> started<00:07:58.319> disagreeing<00:07:59.240> and<00:07:59.520> we 00:07:59.629 --> 00:07:59.639 align:start position:0% they start started disagreeing and we 00:07:59.639 --> 00:08:02.189 align:start position:0% they start started disagreeing and we want<00:07:59.759> to<00:07:59.960> pinpoint<00:08:00.479> exactly<00:08:00.960> that<00:08:01.479> and<00:08:01.680> once 00:08:02.189 --> 00:08:02.199 align:start position:0% want to pinpoint exactly that and once 00:08:02.199 --> 00:08:05.029 align:start position:0% want to pinpoint exactly that and once you<00:08:02.400> find<00:08:02.720> that<00:08:03.120> Divergence<00:08:04.120> you<00:08:04.240> can<00:08:04.560> execute 00:08:05.029 --> 00:08:05.039 align:start position:0% you find that Divergence you can execute 00:08:05.039 --> 00:08:07.110 align:start position:0% you find that Divergence you can execute a<00:08:05.240> single<00:08:05.840> state<00:08:06.199> transition<00:08:06.680> function<00:08:07.000> you 00:08:07.110 --> 00:08:07.120 align:start position:0% a single state transition function you 00:08:07.120 --> 00:08:08.909 align:start position:0% a single state transition function you know<00:08:07.240> the<00:08:07.360> refere<00:08:07.800> the<00:08:07.919> blockchain<00:08:08.759> and 00:08:08.909 --> 00:08:08.919 align:start position:0% know the refere the blockchain and 00:08:08.919 --> 00:08:10.550 align:start position:0% know the refere the blockchain and figure<00:08:09.159> out<00:08:09.360> who's<00:08:09.560> lying<00:08:09.879> and<00:08:10.039> eliminate 00:08:10.550 --> 00:08:10.560 align:start position:0% figure out who's lying and eliminate 00:08:10.560 --> 00:08:13.029 align:start position:0% figure out who's lying and eliminate this<00:08:11.000> liar<00:08:12.000> uh<00:08:12.120> so<00:08:12.319> this<00:08:12.440> is<00:08:12.560> the<00:08:12.720> basic 00:08:13.029 --> 00:08:13.039 align:start position:0% this liar uh so this is the basic 00:08:13.039 --> 00:08:14.950 align:start position:0% this liar uh so this is the basic intuition<00:08:13.680> but<00:08:13.960> we're<00:08:14.159> going<00:08:14.360> to<00:08:14.599> make<00:08:14.759> a 00:08:14.950 --> 00:08:14.960 align:start position:0% intuition but we're going to make a 00:08:14.960 --> 00:08:17.670 align:start position:0% intuition but we're going to make a slight<00:08:15.240> change<00:08:15.560> to<00:08:15.879> this<00:08:16.879> uh<00:08:17.000> so<00:08:17.240> instead<00:08:17.479> of 00:08:17.670 --> 00:08:17.680 align:start position:0% slight change to this uh so instead of 00:08:17.680 --> 00:08:19.550 align:start position:0% slight change to this uh so instead of committing<00:08:18.120> just<00:08:18.280> to<00:08:18.400> the<00:08:18.520> final<00:08:18.840> state<00:08:19.280> which 00:08:19.550 --> 00:08:19.560 align:start position:0% committing just to the final state which 00:08:19.560 --> 00:08:21.749 align:start position:0% committing just to the final state which is<00:08:19.800> really<00:08:20.039> what<00:08:20.159> we're<00:08:20.360> interested<00:08:20.800> about<00:08:21.599> we 00:08:21.749 --> 00:08:21.759 align:start position:0% is really what we're interested about we 00:08:21.759 --> 00:08:24.869 align:start position:0% is really what we're interested about we are<00:08:22.039> going<00:08:22.879> instead<00:08:23.879> to<00:08:24.080> make<00:08:24.199> a<00:08:24.360> commitment 00:08:24.869 --> 00:08:24.879 align:start position:0% are going instead to make a commitment 00:08:24.879 --> 00:08:26.950 align:start position:0% are going instead to make a commitment on<00:08:25.120> the<00:08:25.319> whole<00:08:25.639> history<00:08:25.960> of<00:08:26.120> the<00:08:26.280> computation 00:08:26.950 --> 00:08:26.960 align:start position:0% on the whole history of the computation 00:08:26.960 --> 00:08:28.830 align:start position:0% on the whole history of the computation so<00:08:27.120> we<00:08:27.240> have<00:08:27.440> all<00:08:27.599> these<00:08:27.800> transient<00:08:28.400> States 00:08:28.830 --> 00:08:28.840 align:start position:0% so we have all these transient States 00:08:28.840 --> 00:08:30.510 align:start position:0% so we have all these transient States and<00:08:28.960> we're<00:08:29.080> going<00:08:29.199> to<00:08:29.520> commit<00:08:29.800> to<00:08:30.080> that<00:08:30.400> so 00:08:30.510 --> 00:08:30.520 align:start position:0% and we're going to commit to that so 00:08:30.520 --> 00:08:33.110 align:start position:0% and we're going to commit to that so it's<00:08:30.680> like<00:08:30.800> a<00:08:30.919> Merk<00:08:31.400> tree<00:08:32.200> where<00:08:32.360> the<00:08:32.560> leaves 00:08:33.110 --> 00:08:33.120 align:start position:0% it's like a Merk tree where the leaves 00:08:33.120 --> 00:08:35.709 align:start position:0% it's like a Merk tree where the leaves are<00:08:33.360> all<00:08:33.519> the<00:08:33.680> transient<00:08:34.240> States<00:08:34.880> we<00:08:35.039> meriz 00:08:35.709 --> 00:08:35.719 align:start position:0% are all the transient States we meriz 00:08:35.719 --> 00:08:38.430 align:start position:0% are all the transient States we meriz that<00:08:36.320> we<00:08:36.479> get<00:08:36.640> the<00:08:36.760> claim<00:08:37.479> so<00:08:37.599> we<00:08:37.800> turn<00:08:38.240> the 00:08:38.430 --> 00:08:38.440 align:start position:0% that we get the claim so we turn the 00:08:38.440 --> 00:08:41.310 align:start position:0% that we get the claim so we turn the dispute<00:08:39.279> not<00:08:39.680> just<00:08:39.839> on<00:08:40.000> the<00:08:40.159> final<00:08:40.479> state<00:08:41.159> but 00:08:41.310 --> 00:08:41.320 align:start position:0% dispute not just on the final state but 00:08:41.320 --> 00:08:43.350 align:start position:0% dispute not just on the final state but also<00:08:41.560> on<00:08:41.680> the<00:08:41.880> history<00:08:42.599> and<00:08:42.719> this<00:08:42.880> change<00:08:43.120> is 00:08:43.350 --> 00:08:43.360 align:start position:0% also on the history and this change is 00:08:43.360 --> 00:08:45.790 align:start position:0% also on the history and this change is important<00:08:44.360> because<00:08:44.839> we<00:08:45.040> remove<00:08:45.640> the 00:08:45.790 --> 00:08:45.800 align:start position:0% important because we remove the 00:08:45.800 --> 00:08:47.710 align:start position:0% important because we remove the possibility<00:08:46.320> of<00:08:46.480> false<00:08:46.760> flag<00:08:47.120> attacks<00:08:47.600> which 00:08:47.710 --> 00:08:47.720 align:start position:0% possibility of false flag attacks which 00:08:47.720 --> 00:08:49.070 align:start position:0% possibility of false flag attacks which are<00:08:47.880> quite<00:08:48.080> annoying<00:08:48.399> you<00:08:48.519> know<00:08:48.640> so<00:08:48.800> we<00:08:48.880> can 00:08:49.070 --> 00:08:49.080 align:start position:0% are quite annoying you know so we can 00:08:49.080 --> 00:08:52.230 align:start position:0% are quite annoying you know so we can join<00:08:50.000> a<00:08:50.240> s<00:08:51.040> claims<00:08:51.360> that<00:08:51.480> are<00:08:51.680> the<00:08:51.800> same 00:08:52.230 --> 00:08:52.240 align:start position:0% join a s claims that are the same 00:08:52.240 --> 00:08:53.949 align:start position:0% join a s claims that are the same together<00:08:52.480> on<00:08:52.640> the<00:08:52.760> same<00:08:52.920> team<00:08:53.680> and<00:08:53.800> this 00:08:53.949 --> 00:08:53.959 align:start position:0% together on the same team and this 00:08:53.959 --> 00:08:55.710 align:start position:0% together on the same team and this enables<00:08:54.519> a<00:08:54.640> whole<00:08:54.800> bunch<00:08:54.959> of<00:08:55.120> algorithms 00:08:55.710 --> 00:08:55.720 align:start position:0% enables a whole bunch of algorithms 00:08:55.720 --> 00:08:57.710 align:start position:0% enables a whole bunch of algorithms including<00:08:56.160> PRT<00:08:56.800> because<00:08:57.000> we<00:08:57.120> introduce<00:08:57.560> this 00:08:57.710 --> 00:08:57.720 align:start position:0% including PRT because we introduce this 00:08:57.720 --> 00:09:00.069 align:start position:0% including PRT because we introduce this technique<00:08:58.040> on<00:08:58.279> PRT<00:08:59.279> and<00:08:59.440> and<00:08:59.640> Dave<00:08:59.959> which 00:09:00.069 --> 00:09:00.079 align:start position:0% technique on PRT and and Dave which 00:09:00.079 --> 00:09:03.230 align:start position:0% technique on PRT and and Dave which we're<00:09:00.240> going<00:09:00.399> to<00:09:00.600> present 00:09:03.230 --> 00:09:03.240 align:start position:0% 00:09:03.240 --> 00:09:05.310 align:start position:0% today<00:09:04.240> now<00:09:04.519> the 00:09:05.310 --> 00:09:05.320 align:start position:0% today now the 00:09:05.320 --> 00:09:07.790 align:start position:0% today now the final<00:09:06.320> piece<00:09:06.959> to<00:09:07.160> get<00:09:07.320> all<00:09:07.519> like<00:09:07.680> The 00:09:07.790 --> 00:09:07.800 align:start position:0% final piece to get all like The 00:09:07.800 --> 00:09:10.269 align:start position:0% final piece to get all like The Primitives<00:09:08.720> is<00:09:08.959> deadlines<00:09:09.800> because<00:09:10.000> it's<00:09:10.120> an 00:09:10.269 --> 00:09:10.279 align:start position:0% Primitives is deadlines because it's an 00:09:10.279 --> 00:09:12.870 align:start position:0% Primitives is deadlines because it's an interactive<00:09:10.760> protocol<00:09:11.279> so<00:09:11.519> players<00:09:12.000> acting 00:09:12.870 --> 00:09:12.880 align:start position:0% interactive protocol so players acting 00:09:12.880 --> 00:09:15.550 align:start position:0% interactive protocol so players acting turns<00:09:13.880> uh<00:09:14.000> and<00:09:14.200> if<00:09:14.320> they<00:09:14.519> refuse<00:09:14.920> to<00:09:15.120> act<00:09:15.440> we 00:09:15.550 --> 00:09:15.560 align:start position:0% turns uh and if they refuse to act we 00:09:15.560 --> 00:09:17.750 align:start position:0% turns uh and if they refuse to act we need<00:09:15.720> to<00:09:15.839> do<00:09:16.079> something<00:09:16.600> so<00:09:16.760> we<00:09:16.880> need<00:09:17.000> to<00:09:17.160> set 00:09:17.750 --> 00:09:17.760 align:start position:0% need to do something so we need to set 00:09:17.760 --> 00:09:20.350 align:start position:0% need to do something so we need to set deadlines<00:09:18.760> to<00:09:19.120> eliminate<00:09:19.680> players<00:09:20.040> who<00:09:20.160> are 00:09:20.350 --> 00:09:20.360 align:start position:0% deadlines to eliminate players who are 00:09:20.360 --> 00:09:21.670 align:start position:0% deadlines to eliminate players who are not 00:09:21.670 --> 00:09:21.680 align:start position:0% not 00:09:21.680 --> 00:09:24.030 align:start position:0% not cooperating<00:09:22.680> but<00:09:22.880> remember<00:09:23.560> we<00:09:23.680> have<00:09:23.880> the 00:09:24.030 --> 00:09:24.040 align:start position:0% cooperating but remember we have the 00:09:24.040 --> 00:09:26.949 align:start position:0% cooperating but remember we have the onewe<00:09:24.560> censorship<00:09:25.200> in<00:09:25.320> our<00:09:25.519> threat<00:09:25.880> model<00:09:26.640> so 00:09:26.949 --> 00:09:26.959 align:start position:0% onewe censorship in our threat model so 00:09:26.959 --> 00:09:29.990 align:start position:0% onewe censorship in our threat model so naively<00:09:27.720> we<00:09:27.839> would<00:09:28.040> have<00:09:28.200> to<00:09:28.399> set<00:09:28.800> a<00:09:28.959> one<00:09:29.440> week 00:09:29.990 --> 00:09:30.000 align:start position:0% naively we would have to set a one week 00:09:30.000 --> 00:09:32.030 align:start position:0% naively we would have to set a one week for<00:09:30.399> each<00:09:30.839> interaction<00:09:31.519> which<00:09:31.680> would<00:09:31.839> kill 00:09:32.030 --> 00:09:32.040 align:start position:0% for each interaction which would kill 00:09:32.040 --> 00:09:33.990 align:start position:0% for each interaction which would kill the<00:09:32.160> liveness<00:09:32.600> of<00:09:32.800> any 00:09:33.990 --> 00:09:34.000 align:start position:0% the liveness of any 00:09:34.000 --> 00:09:36.829 align:start position:0% the liveness of any protocol<00:09:35.000> so<00:09:35.279> what<00:09:35.440> we<00:09:35.640> instead<00:09:36.079> do<00:09:36.519> this<00:09:36.600> is<00:09:36.680> a 00:09:36.829 --> 00:09:36.839 align:start position:0% protocol so what we instead do this is a 00:09:36.839 --> 00:09:38.790 align:start position:0% protocol so what we instead do this is a technique<00:09:37.240> that<00:09:37.519> many<00:09:37.760> protocols<00:09:38.200> use<00:09:38.560> is 00:09:38.790 --> 00:09:38.800 align:start position:0% technique that many protocols use is 00:09:38.800 --> 00:09:40.870 align:start position:0% technique that many protocols use is something<00:09:39.079> like<00:09:39.200> a<00:09:39.320> chess<00:09:39.640> clock<00:09:40.560> so<00:09:40.760> this 00:09:40.870 --> 00:09:40.880 align:start position:0% something like a chess clock so this 00:09:40.880 --> 00:09:42.750 align:start position:0% something like a chess clock so this allows<00:09:41.160> you<00:09:41.279> to<00:09:41.519> amortize<00:09:42.079> this<00:09:42.240> one<00:09:42.440> week 00:09:42.750 --> 00:09:42.760 align:start position:0% allows you to amortize this one week 00:09:42.760 --> 00:09:45.430 align:start position:0% allows you to amortize this one week across<00:09:43.240> many<00:09:43.920> interactions<00:09:44.920> instead<00:09:45.240> of 00:09:45.430 --> 00:09:45.440 align:start position:0% across many interactions instead of 00:09:45.440 --> 00:09:47.150 align:start position:0% across many interactions instead of having<00:09:45.640> to<00:09:45.800> pay<00:09:46.040> it<00:09:46.160> for<00:09:46.519> every<00:09:46.800> single 00:09:47.150 --> 00:09:47.160 align:start position:0% having to pay it for every single 00:09:47.160 --> 00:09:49.710 align:start position:0% having to pay it for every single interaction<00:09:47.720> so<00:09:48.079> you<00:09:48.200> turn<00:09:48.560> from<00:09:48.880> like<00:09:49.560> the 00:09:49.710 --> 00:09:49.720 align:start position:0% interaction so you turn from like the 00:09:49.720 --> 00:09:52.430 align:start position:0% interaction so you turn from like the sday<00:09:50.240> multiplying<00:09:51.000> each<00:09:51.240> interaction<00:09:52.120> for<00:09:52.360> it 00:09:52.430 --> 00:09:52.440 align:start position:0% sday multiplying each interaction for it 00:09:52.440 --> 00:09:55.389 align:start position:0% sday multiplying each interaction for it to<00:09:52.560> being<00:09:52.760> like<00:09:52.880> an<00:09:53.200> additive<00:09:54.200> uh<00:09:54.680> part<00:09:54.880> of<00:09:55.000> the 00:09:55.389 --> 00:09:55.399 align:start position:0% to being like an additive uh part of the 00:09:55.399 --> 00:09:58.389 align:start position:0% to being like an additive uh part of the expression<00:09:56.399> and<00:09:56.560> then<00:09:57.320> you<00:09:57.519> only<00:09:57.760> need<00:09:57.959> to<00:09:58.200> pay 00:09:58.389 --> 00:09:58.399 align:start position:0% expression and then you only need to pay 00:09:58.399 --> 00:10:00.069 align:start position:0% expression and then you only need to pay for<00:09:58.600> each<00:09:58.800> interaction<00:09:59.399> the<00:09:59.480> real<00:09:59.720> time<00:09:59.920> of 00:10:00.069 --> 00:10:00.079 align:start position:0% for each interaction the real time of 00:10:00.079 --> 00:10:01.790 align:start position:0% for each interaction the real time of that<00:10:00.240> interaction<00:10:00.959> in<00:10:01.079> the<00:10:01.240> absence<00:10:01.600> of 00:10:01.790 --> 00:10:01.800 align:start position:0% that interaction in the absence of 00:10:01.800 --> 00:10:03.870 align:start position:0% that interaction in the absence of censorship<00:10:02.800> because<00:10:03.000> an<00:10:03.160> interaction<00:10:03.600> is 00:10:03.870 --> 00:10:03.880 align:start position:0% censorship because an interaction is 00:10:03.880 --> 00:10:06.230 align:start position:0% censorship because an interaction is quite<00:10:04.160> fast<00:10:04.480> you<00:10:04.600> know<00:10:04.760> it's<00:10:04.920> like<00:10:05.120> 5<00:10:05.360> minutes 00:10:06.230 --> 00:10:06.240 align:start position:0% quite fast you know it's like 5 minutes 00:10:06.240 --> 00:10:08.350 align:start position:0% quite fast you know it's like 5 minutes uh<00:10:06.399> and<00:10:06.560> we<00:10:06.680> don't<00:10:06.800> want<00:10:06.920> to<00:10:07.120> play<00:10:07.560> pay<00:10:07.959> on<00:10:08.200> top 00:10:08.350 --> 00:10:08.360 align:start position:0% uh and we don't want to play pay on top 00:10:08.360 --> 00:10:10.910 align:start position:0% uh and we don't want to play pay on top of<00:10:08.519> that<00:10:08.720> five<00:10:08.920> minutes<00:10:09.640> seven<00:10:10.040> days<00:10:10.640> so<00:10:10.800> we 00:10:10.910 --> 00:10:10.920 align:start position:0% of that five minutes seven days so we 00:10:10.920 --> 00:10:13.350 align:start position:0% of that five minutes seven days so we use<00:10:11.079> the<00:10:11.200> chess<00:10:11.480> clock<00:10:11.720> to<00:10:11.880> amortize 00:10:13.350 --> 00:10:13.360 align:start position:0% use the chess clock to amortize 00:10:13.360 --> 00:10:16.230 align:start position:0% use the chess clock to amortize that<00:10:14.360> now<00:10:14.800> let's<00:10:15.040> generalize<00:10:15.720> this<00:10:15.920> this<00:10:16.040> is<00:10:16.120> a 00:10:16.230 --> 00:10:16.240 align:start position:0% that now let's generalize this this is a 00:10:16.240 --> 00:10:18.430 align:start position:0% that now let's generalize this this is a pawise<00:10:16.760> reputation<00:10:17.320> first<00:10:17.800> now<00:10:17.959> let's<00:10:18.160> do<00:10:18.320> a 00:10:18.430 --> 00:10:18.440 align:start position:0% pawise reputation first now let's do a 00:10:18.440 --> 00:10:20.150 align:start position:0% pawise reputation first now let's do a multiparty 00:10:20.150 --> 00:10:20.160 align:start position:0% multiparty 00:10:20.160 --> 00:10:23.150 align:start position:0% multiparty reputation<00:10:21.160> and<00:10:21.360> there<00:10:21.519> are<00:10:21.959> two<00:10:22.560> high<00:10:22.760> level 00:10:23.150 --> 00:10:23.160 align:start position:0% reputation and there are two high level 00:10:23.160 --> 00:10:25.910 align:start position:0% reputation and there are two high level approaches<00:10:24.160> one<00:10:24.560> is<00:10:24.800> the<00:10:24.959> parallel<00:10:25.440> approach 00:10:25.910 --> 00:10:25.920 align:start position:0% approaches one is the parallel approach 00:10:25.920 --> 00:10:30.389 align:start position:0% approaches one is the parallel approach which<00:10:26.279> is<00:10:27.279> more<00:10:28.120> like<00:10:28.360> what<00:10:28.560> bold<00:10:28.920> uses 00:10:30.389 --> 00:10:30.399 align:start position:0% which is more like what bold uses 00:10:30.399 --> 00:10:32.110 align:start position:0% which is more like what bold uses uh<00:10:30.560> and<00:10:30.839> the<00:10:31.000> good<00:10:31.200> part<00:10:31.360> of<00:10:31.519> it<00:10:31.680> is<00:10:31.839> that<00:10:32.000> it 00:10:32.110 --> 00:10:32.120 align:start position:0% uh and the good part of it is that it 00:10:32.120 --> 00:10:36.350 align:start position:0% uh and the good part of it is that it finishes<00:10:32.839> fast<00:10:33.839> so<00:10:34.040> we<00:10:34.200> have<00:10:34.480> Willie<00:10:35.360> engaging 00:10:36.350 --> 00:10:36.360 align:start position:0% finishes fast so we have Willie engaging 00:10:36.360 --> 00:10:38.990 align:start position:0% finishes fast so we have Willie engaging every<00:10:36.600> other<00:10:36.880> claim<00:10:37.760> in<00:10:38.000> parallel<00:10:38.720> at<00:10:38.880> the 00:10:38.990 --> 00:10:39.000 align:start position:0% every other claim in parallel at the 00:10:39.000 --> 00:10:41.110 align:start position:0% every other claim in parallel at the same<00:10:39.279> time<00:10:40.200> but<00:10:40.320> the<00:10:40.480> problem<00:10:40.720> is<00:10:40.839> that<00:10:41.000> we 00:10:41.110 --> 00:10:41.120 align:start position:0% same time but the problem is that we 00:10:41.120 --> 00:10:43.590 align:start position:0% same time but the problem is that we incurred<00:10:41.440> a<00:10:41.560> chance<00:10:41.920> of<00:10:42.160> overwhelming<00:10:42.920> Willie 00:10:43.590 --> 00:10:43.600 align:start position:0% incurred a chance of overwhelming Willie 00:10:43.600 --> 00:10:45.069 align:start position:0% incurred a chance of overwhelming Willie right<00:10:43.760> so<00:10:43.959> imagine<00:10:44.279> that<00:10:44.440> instead<00:10:44.680> of<00:10:44.839> only 00:10:45.069 --> 00:10:45.079 align:start position:0% right so imagine that instead of only 00:10:45.079 --> 00:10:47.870 align:start position:0% right so imagine that instead of only five<00:10:45.880> we<00:10:46.000> had<00:10:46.160> like<00:10:46.320> one<00:10:46.480> million<00:10:46.760> sibl<00:10:47.680> would 00:10:47.870 --> 00:10:47.880 align:start position:0% five we had like one million sibl would 00:10:47.880 --> 00:10:49.870 align:start position:0% five we had like one million sibl would have<00:10:48.279> Willie<00:10:48.680> trying<00:10:48.959> to<00:10:49.079> fight<00:10:49.360> everybody<00:10:49.760> at 00:10:49.870 --> 00:10:49.880 align:start position:0% have Willie trying to fight everybody at 00:10:49.880 --> 00:10:51.829 align:start position:0% have Willie trying to fight everybody at the<00:10:50.000> same<00:10:50.240> time<00:10:51.240> and<00:10:51.360> he<00:10:51.519> could<00:10:51.680> get 00:10:51.829 --> 00:10:51.839 align:start position:0% the same time and he could get 00:10:51.839 --> 00:10:55.509 align:start position:0% the same time and he could get overwhelmed<00:10:52.760> and<00:10:52.920> lose<00:10:53.560> and<00:10:53.720> lose<00:10:53.959> a<00:10:54.360> tvl<00:10:55.360> so 00:10:55.509 --> 00:10:55.519 align:start position:0% overwhelmed and lose and lose a tvl so 00:10:55.519 --> 00:10:57.629 align:start position:0% overwhelmed and lose and lose a tvl so we<00:10:55.680> have<00:10:55.839> this<00:10:56.000> you<00:10:56.120> know<00:10:56.320> oh<00:10:56.519> it's<00:10:56.760> fast<00:10:57.440> but 00:10:57.629 --> 00:10:57.639 align:start position:0% we have this you know oh it's fast but 00:10:57.639 --> 00:11:00.069 align:start position:0% we have this you know oh it's fast but it<00:10:57.760> might<00:10:58.000> overwhelm<00:10:58.639> Willie 00:11:00.069 --> 00:11:00.079 align:start position:0% it might overwhelm Willie 00:11:00.079 --> 00:11:01.949 align:start position:0% it might overwhelm Willie and<00:11:00.240> we<00:11:00.360> can<00:11:00.600> mitigate<00:11:01.079> that<00:11:01.320> by<00:11:01.519> increasing 00:11:01.949 --> 00:11:01.959 align:start position:0% and we can mitigate that by increasing 00:11:01.959 --> 00:11:04.310 align:start position:0% and we can mitigate that by increasing bonds<00:11:02.399> but<00:11:02.519> then<00:11:02.639> we<00:11:02.760> start<00:11:03.040> centralizing<00:11:03.680> the 00:11:04.310 --> 00:11:04.320 align:start position:0% bonds but then we start centralizing the 00:11:04.320 --> 00:11:06.750 align:start position:0% bonds but then we start centralizing the algorithm<00:11:05.320> uh<00:11:05.440> with<00:11:05.680> PR2<00:11:06.240> which<00:11:06.360> is<00:11:06.480> our 00:11:06.750 --> 00:11:06.760 align:start position:0% algorithm uh with PR2 which is our 00:11:06.760 --> 00:11:08.590 align:start position:0% algorithm uh with PR2 which is our previous<00:11:07.040> algorithm<00:11:07.680> we<00:11:07.800> went<00:11:08.000> a<00:11:08.160> different 00:11:08.590 --> 00:11:08.600 align:start position:0% previous algorithm we went a different 00:11:08.600 --> 00:11:11.670 align:start position:0% previous algorithm we went a different route<00:11:09.600> uh<00:11:09.760> we<00:11:09.880> use<00:11:10.360> this<00:11:10.639> tournament<00:11:11.279> idea 00:11:11.670 --> 00:11:11.680 align:start position:0% route uh we use this tournament idea 00:11:11.680 --> 00:11:13.230 align:start position:0% route uh we use this tournament idea right<00:11:11.800> so<00:11:11.959> we<00:11:12.079> put<00:11:12.240> sybl<00:11:12.600> to<00:11:12.760> fight<00:11:13.000> against 00:11:13.230 --> 00:11:13.240 align:start position:0% right so we put sybl to fight against 00:11:13.240 --> 00:11:15.670 align:start position:0% right so we put sybl to fight against other<00:11:13.600> cbbls<00:11:14.600> so<00:11:14.760> the<00:11:14.880> number<00:11:15.120> of<00:11:15.279> round<00:11:15.519> is 00:11:15.670 --> 00:11:15.680 align:start position:0% other cbbls so the number of round is 00:11:15.680 --> 00:11:18.069 align:start position:0% other cbbls so the number of round is logarithmic<00:11:16.560> the<00:11:16.760> expenses<00:11:17.200> are<00:11:17.360> logarithmic 00:11:18.069 --> 00:11:18.079 align:start position:0% logarithmic the expenses are logarithmic 00:11:18.079 --> 00:11:20.470 align:start position:0% logarithmic the expenses are logarithmic and<00:11:18.200> the<00:11:18.360> delay<00:11:18.720> is<00:11:18.959> logarithmic<00:11:19.959> so<00:11:20.160> this<00:11:20.320> all 00:11:20.470 --> 00:11:20.480 align:start position:0% and the delay is logarithmic so this all 00:11:20.480 --> 00:11:23.110 align:start position:0% and the delay is logarithmic so this all means<00:11:21.160> exponential<00:11:21.800> Advantage<00:11:22.600> willly<00:11:23.000> has 00:11:23.110 --> 00:11:23.120 align:start position:0% means exponential Advantage willly has 00:11:23.120 --> 00:11:26.710 align:start position:0% means exponential Advantage willly has an<00:11:23.279> exponential<00:11:23.839> advantage<00:11:24.320> on<00:11:24.560> delay<00:11:25.560> and 00:11:26.710 --> 00:11:26.720 align:start position:0% an exponential advantage on delay and 00:11:26.720 --> 00:11:30.150 align:start position:0% an exponential advantage on delay and resources<00:11:27.720> but<00:11:28.600> each<00:11:28.880> round<00:11:29.360> takes<00:11:29.560> a<00:11:29.720> week 00:11:30.150 --> 00:11:30.160 align:start position:0% resources but each round takes a week 00:11:30.160 --> 00:11:31.710 align:start position:0% resources but each round takes a week because<00:11:30.399> of<00:11:30.519> the<00:11:30.639> censorship<00:11:31.120> you<00:11:31.240> know<00:11:31.360> even 00:11:31.710 --> 00:11:31.720 align:start position:0% because of the censorship you know even 00:11:31.720 --> 00:11:35.350 align:start position:0% because of the censorship you know even amortising<00:11:32.720> the<00:11:32.880> week<00:11:33.160> across<00:11:33.519> a<00:11:34.040> match<00:11:35.040> every 00:11:35.350 --> 00:11:35.360 align:start position:0% amortising the week across a match every 00:11:35.360 --> 00:11:37.590 align:start position:0% amortising the week across a match every match<00:11:35.760> every<00:11:36.040> round<00:11:36.440> still<00:11:36.839> has<00:11:37.000> to<00:11:37.279> last<00:11:37.480> at 00:11:37.590 --> 00:11:37.600 align:start position:0% match every round still has to last at 00:11:37.600 --> 00:11:40.750 align:start position:0% match every round still has to last at least<00:11:37.800> a<00:11:38.120> week<00:11:39.120> so<00:11:39.360> if<00:11:39.480> we<00:11:39.680> imagine<00:11:40.200> this<00:11:40.440> the 00:11:40.750 --> 00:11:40.760 align:start position:0% least a week so if we imagine this the 00:11:40.760 --> 00:11:43.550 align:start position:0% least a week so if we imagine this the analogous<00:11:41.760> uh<00:11:42.040> of<00:11:42.279> 1<00:11:42.480> million<00:11:42.760> sibles<00:11:43.240> here 00:11:43.550 --> 00:11:43.560 align:start position:0% analogous uh of 1 million sibles here 00:11:43.560 --> 00:11:46.069 align:start position:0% analogous uh of 1 million sibles here there<00:11:43.680> will<00:11:43.920> be<00:11:44.200> 20<00:11:44.639> rounds<00:11:45.440> so<00:11:45.600> it<00:11:45.720> will<00:11:45.880> take 00:11:46.069 --> 00:11:46.079 align:start position:0% there will be 20 rounds so it will take 00:11:46.079 --> 00:11:50.550 align:start position:0% there will be 20 rounds so it will take 20<00:11:46.720> weeks<00:11:47.720> which<00:11:47.839> is<00:11:48.079> high<00:11:48.360> you<00:11:48.480> know<00:11:49.440> uh<00:11:49.959> but 00:11:50.550 --> 00:11:50.560 align:start position:0% 20 weeks which is high you know uh but 00:11:50.560 --> 00:11:52.710 align:start position:0% 20 weeks which is high you know uh but matches<00:11:51.040> only<00:11:51.279> take<00:11:51.519> two<00:11:51.760> hours<00:11:52.200> in<00:11:52.399> practice 00:11:52.710 --> 00:11:52.720 align:start position:0% matches only take two hours in practice 00:11:52.720 --> 00:11:54.629 align:start position:0% matches only take two hours in practice you<00:11:52.839> know<00:11:52.959> in<00:11:53.079> the<00:11:53.279> absence<00:11:53.560> of<00:11:53.720> censorship 00:11:54.629 --> 00:11:54.639 align:start position:0% you know in the absence of censorship 00:11:54.639 --> 00:11:57.069 align:start position:0% you know in the absence of censorship they<00:11:54.800> would<00:11:55.040> take<00:11:55.240> two<00:11:55.480> hours<00:11:56.360> but<00:11:56.560> because 00:11:57.069 --> 00:11:57.079 align:start position:0% they would take two hours but because 00:11:57.079 --> 00:11:58.870 align:start position:0% they would take two hours but because there<00:11:57.320> could<00:11:57.519> be<00:11:57.680> censorship<00:11:58.279> we<00:11:58.399> need<00:11:58.560> to<00:11:58.720> add 00:11:58.870 --> 00:11:58.880 align:start position:0% there could be censorship we need to add 00:11:58.880 --> 00:11:59.829 align:start position:0% there could be censorship we need to add the<00:11:59.000> week 00:11:59.829 --> 00:11:59.839 align:start position:0% the week 00:11:59.839 --> 00:12:03.470 align:start position:0% the week so<00:12:00.279> we<00:12:00.440> were<00:12:00.639> thinking<00:12:01.600> oh<00:12:02.600> why<00:12:02.760> don't<00:12:02.959> we<00:12:03.200> try 00:12:03.470 --> 00:12:03.480 align:start position:0% so we were thinking oh why don't we try 00:12:03.480 --> 00:12:06.949 align:start position:0% so we were thinking oh why don't we try to<00:12:03.920> amortize<00:12:04.920> this<00:12:05.120> one<00:12:05.440> week<00:12:06.360> not<00:12:06.600> only 00:12:06.949 --> 00:12:06.959 align:start position:0% to amortize this one week not only 00:12:06.959 --> 00:12:09.310 align:start position:0% to amortize this one week not only inside<00:12:07.320> a<00:12:07.480> single<00:12:07.760> round<00:12:08.240> but<00:12:08.480> across<00:12:09.160> the 00:12:09.310 --> 00:12:09.320 align:start position:0% inside a single round but across the 00:12:09.320 --> 00:12:12.870 align:start position:0% inside a single round but across the entire<00:12:10.200> dispute<00:12:11.200> so<00:12:11.519> this<00:12:11.680> is<00:12:12.000> what<00:12:12.399> we'll<00:12:12.680> try 00:12:12.870 --> 00:12:12.880 align:start position:0% entire dispute so this is what we'll try 00:12:12.880 --> 00:12:15.189 align:start position:0% entire dispute so this is what we'll try to<00:12:13.000> do<00:12:13.199> so<00:12:13.360> what<00:12:13.480> I<00:12:13.720> present<00:12:14.079> now<00:12:14.839> is<00:12:14.959> an 00:12:15.189 --> 00:12:15.199 align:start position:0% to do so what I present now is an 00:12:15.199 --> 00:12:17.910 align:start position:0% to do so what I present now is an attempt<00:12:15.880> to<00:12:16.160> accomplish 00:12:17.910 --> 00:12:17.920 align:start position:0% attempt to accomplish 00:12:17.920 --> 00:12:20.990 align:start position:0% attempt to accomplish that<00:12:18.920> okay<00:12:19.120> so<00:12:20.000> the<00:12:20.120> algorithm<00:12:20.600> is<00:12:20.720> called 00:12:20.990 --> 00:12:21.000 align:start position:0% that okay so the algorithm is called 00:12:21.000 --> 00:12:24.990 align:start position:0% that okay so the algorithm is called Dave<00:12:21.560> uh<00:12:21.680> and<00:12:21.760> it's<00:12:21.959> just 00:12:24.990 --> 00:12:25.000 align:start position:0% 00:12:25.000 --> 00:12:27.110 align:start position:0% Dave<00:12:26.000> it's<00:12:26.160> not<00:12:26.320> an 00:12:27.110 --> 00:12:27.120 align:start position:0% Dave it's not an 00:12:27.120 --> 00:12:29.710 align:start position:0% Dave it's not an acronym<00:12:28.120> uh<00:12:28.240> it's<00:12:28.440> based<00:12:28.639> on<00:12:28.760> the<00:12:28.920> D<00:12:29.320> versus 00:12:29.710 --> 00:12:29.720 align:start position:0% acronym uh it's based on the D versus 00:12:29.720 --> 00:12:30.829 align:start position:0% acronym uh it's based on the D versus Goliath 00:12:30.829 --> 00:12:30.839 align:start position:0% Goliath 00:12:30.839 --> 00:12:35.750 align:start position:0% Goliath archetype<00:12:31.839> uh<00:12:32.399> because<00:12:33.399> anyway<00:12:34.480> um<00:12:35.480> so<00:12:35.639> the 00:12:35.750 --> 00:12:35.760 align:start position:0% archetype uh because anyway um so the 00:12:35.760 --> 00:12:37.990 align:start position:0% archetype uh because anyway um so the first<00:12:35.959> change<00:12:36.199> we<00:12:36.399> make<00:12:37.000> uh<00:12:37.120> is<00:12:37.240> we<00:12:37.399> change<00:12:37.839> the 00:12:37.990 --> 00:12:38.000 align:start position:0% first change we make uh is we change the 00:12:38.000 --> 00:12:40.110 align:start position:0% first change we make uh is we change the tournament<00:12:38.399> to<00:12:38.519> a<00:12:38.680> repage 00:12:40.110 --> 00:12:40.120 align:start position:0% tournament to a repage 00:12:40.120 --> 00:12:42.310 align:start position:0% tournament to a repage tournament<00:12:41.120> this<00:12:41.240> is<00:12:41.320> a<00:12:41.480> fancy<00:12:41.800> name<00:12:42.040> just<00:12:42.199> to 00:12:42.310 --> 00:12:42.320 align:start position:0% tournament this is a fancy name just to 00:12:42.320 --> 00:12:44.670 align:start position:0% tournament this is a fancy name just to mean<00:12:42.720> matches<00:12:43.040> are<00:12:43.279> not<00:12:43.600> eliminatory<00:12:44.519> you 00:12:44.670 --> 00:12:44.680 align:start position:0% mean matches are not eliminatory you 00:12:44.680 --> 00:12:48.110 align:start position:0% mean matches are not eliminatory you don't<00:12:45.199> eliminate<00:12:46.199> um<00:12:46.800> a<00:12:47.000> claim<00:12:47.519> as<00:12:47.600> soon<00:12:47.800> as<00:12:47.959> it 00:12:48.110 --> 00:12:48.120 align:start position:0% don't eliminate um a claim as soon as it 00:12:48.120 --> 00:12:50.470 align:start position:0% don't eliminate um a claim as soon as it loses<00:12:49.000> you<00:12:49.199> give<00:12:49.320> it<00:12:49.440> a<00:12:49.600> while<00:12:50.000> you<00:12:50.120> know<00:12:50.320> it 00:12:50.470 --> 00:12:50.480 align:start position:0% loses you give it a while you know it 00:12:50.480 --> 00:12:52.750 align:start position:0% loses you give it a while you know it has<00:12:50.639> to<00:12:50.800> lose<00:12:51.160> multiple<00:12:51.680> times<00:12:52.079> before<00:12:52.399> it's 00:12:52.750 --> 00:12:52.760 align:start position:0% has to lose multiple times before it's 00:12:52.760 --> 00:12:55.310 align:start position:0% has to lose multiple times before it's finally<00:12:53.360> eliminated<00:12:54.360> so<00:12:54.560> this<00:12:54.639> is<00:12:54.760> what<00:12:54.920> repes 00:12:55.310 --> 00:12:55.320 align:start position:0% finally eliminated so this is what repes 00:12:55.320 --> 00:12:57.910 align:start position:0% finally eliminated so this is what repes Char<00:12:55.519> means<00:12:56.199> now<00:12:56.440> don't<00:12:56.639> try<00:12:56.880> to<00:12:57.040> think<00:12:57.279> about 00:12:57.910 --> 00:12:57.920 align:start position:0% Char means now don't try to think about 00:12:57.920 --> 00:12:59.870 align:start position:0% Char means now don't try to think about how<00:12:58.120> long<00:12:58.399> this<00:12:58.519> will<00:12:58.760> take<00:12:59.199> forget<00:12:59.519> that 00:12:59.870 --> 00:12:59.880 align:start position:0% how long this will take forget that 00:12:59.880 --> 00:13:02.629 align:start position:0% how long this will take forget that let's<00:13:00.160> just<00:13:00.519> think<00:13:00.720> on<00:13:00.920> the<00:13:01.160> soundness<00:13:01.760> of<00:13:01.920> it 00:13:02.629 --> 00:13:02.639 align:start position:0% let's just think on the soundness of it 00:13:02.639 --> 00:13:05.430 align:start position:0% let's just think on the soundness of it I<00:13:02.760> want<00:13:03.279> on<00:13:03.480> this<00:13:03.639> slide<00:13:04.560> to<00:13:04.800> convince<00:13:05.199> you 00:13:05.430 --> 00:13:05.440 align:start position:0% I want on this slide to convince you 00:13:05.440 --> 00:13:07.790 align:start position:0% I want on this slide to convince you that<00:13:05.680> Willie<00:13:06.199> won't<00:13:06.680> lose<00:13:07.320> and<00:13:07.480> he<00:13:07.600> will 00:13:07.790 --> 00:13:07.800 align:start position:0% that Willie won't lose and he will 00:13:07.800 --> 00:13:10.069 align:start position:0% that Willie won't lose and he will defeat<00:13:08.199> everybody<00:13:08.720> let's<00:13:08.959> think<00:13:09.160> about<00:13:09.360> time 00:13:10.069 --> 00:13:10.079 align:start position:0% defeat everybody let's think about time 00:13:10.079 --> 00:13:13.629 align:start position:0% defeat everybody let's think about time later<00:13:11.079> um<00:13:12.079> yeah<00:13:12.199> so<00:13:12.399> imagine<00:13:12.880> that<00:13:13.320> we<00:13:13.480> have 00:13:13.629 --> 00:13:13.639 align:start position:0% later um yeah so imagine that we have 00:13:13.639 --> 00:13:16.230 align:start position:0% later um yeah so imagine that we have the<00:13:13.800> censorship<00:13:14.279> of<00:13:14.399> one<00:13:14.600> week<00:13:15.320> but<00:13:15.600> we<00:13:15.839> reduce 00:13:16.230 --> 00:13:16.240 align:start position:0% the censorship of one week but we reduce 00:13:16.240 --> 00:13:18.910 align:start position:0% the censorship of one week but we reduce the<00:13:16.360> rounds<00:13:16.760> the<00:13:16.880> matches<00:13:17.279> to<00:13:17.519> one<00:13:17.800> day<00:13:18.440> so 00:13:18.910 --> 00:13:18.920 align:start position:0% the rounds the matches to one day so 00:13:18.920 --> 00:13:22.430 align:start position:0% the rounds the matches to one day so every<00:13:19.639> one<00:13:20.199> day<00:13:21.079> they<00:13:21.360> rematches<00:13:22.040> everybody 00:13:22.430 --> 00:13:22.440 align:start position:0% every one day they rematches everybody 00:13:22.440 --> 00:13:25.269 align:start position:0% every one day they rematches everybody including<00:13:23.040> Willie<00:13:24.040> uh<00:13:24.160> and<00:13:24.279> then<00:13:24.440> they<00:13:24.639> fight 00:13:25.269 --> 00:13:25.279 align:start position:0% including Willie uh and then they fight 00:13:25.279 --> 00:13:27.550 align:start position:0% including Willie uh and then they fight the<00:13:25.440> next<00:13:25.680> day<00:13:25.880> rematches<00:13:26.440> everybody<00:13:26.920> again 00:13:27.550 --> 00:13:27.560 align:start position:0% the next day rematches everybody again 00:13:27.560 --> 00:13:30.189 align:start position:0% the next day rematches everybody again and<00:13:27.760> so<00:13:28.000> on<00:13:28.880> when<00:13:29.240> know<00:13:29.440> that<00:13:29.600> Willie<00:13:29.959> can't 00:13:30.189 --> 00:13:30.199 align:start position:0% and so on when know that Willie can't 00:13:30.199 --> 00:13:33.150 align:start position:0% and so on when know that Willie can't lose<00:13:31.120> unless<00:13:31.480> there's<00:13:31.760> censorship<00:13:32.760> but<00:13:32.959> even 00:13:33.150 --> 00:13:33.160 align:start position:0% lose unless there's censorship but even 00:13:33.160 --> 00:13:34.910 align:start position:0% lose unless there's censorship but even if<00:13:33.320> there's<00:13:33.600> censorship<00:13:34.320> we<00:13:34.480> know<00:13:34.720> that 00:13:34.910 --> 00:13:34.920 align:start position:0% if there's censorship we know that 00:13:34.920 --> 00:13:37.629 align:start position:0% if there's censorship we know that Willie<00:13:35.399> can't<00:13:35.639> lose<00:13:36.000> more<00:13:36.199> than<00:13:36.399> seven<00:13:36.760> times 00:13:37.629 --> 00:13:37.639 align:start position:0% Willie can't lose more than seven times 00:13:37.639 --> 00:13:40.269 align:start position:0% Willie can't lose more than seven times because<00:13:37.920> the<00:13:38.079> budget<00:13:38.480> is<00:13:38.639> only<00:13:38.880> seven<00:13:39.240> days<00:13:39.920> so 00:13:40.269 --> 00:13:40.279 align:start position:0% because the budget is only seven days so 00:13:40.279 --> 00:13:43.230 align:start position:0% because the budget is only seven days so it's<00:13:40.440> like<00:13:40.639> Willie<00:13:40.959> has<00:13:41.160> age<00:13:41.639> hit<00:13:41.880> eight<00:13:42.399> hit 00:13:43.230 --> 00:13:43.240 align:start position:0% it's like Willie has age hit eight hit 00:13:43.240 --> 00:13:46.110 align:start position:0% it's like Willie has age hit eight hit points<00:13:44.240> but<00:13:44.639> the<00:13:44.800> adversary<00:13:45.440> has<00:13:45.600> only<00:13:45.839> seven 00:13:46.110 --> 00:13:46.120 align:start position:0% points but the adversary has only seven 00:13:46.120 --> 00:13:48.710 align:start position:0% points but the adversary has only seven bullets<00:13:46.839> so<00:13:47.040> the<00:13:47.199> best<00:13:47.399> the<00:13:47.560> adversary<00:13:48.040> can<00:13:48.199> do 00:13:48.710 --> 00:13:48.720 align:start position:0% bullets so the best the adversary can do 00:13:48.720 --> 00:13:51.870 align:start position:0% bullets so the best the adversary can do is<00:13:49.000> spend<00:13:49.360> his<00:13:49.639> whole<00:13:50.360> budget<00:13:51.360> and<00:13:51.519> force 00:13:51.870 --> 00:13:51.880 align:start position:0% is spend his whole budget and force 00:13:51.880 --> 00:13:54.310 align:start position:0% is spend his whole budget and force Willie<00:13:52.160> to<00:13:52.320> lose<00:13:52.680> seven<00:13:53.120> hit<00:13:53.320> points<00:13:53.959> and<00:13:54.079> then 00:13:54.310 --> 00:13:54.320 align:start position:0% Willie to lose seven hit points and then 00:13:54.320 --> 00:13:56.430 align:start position:0% Willie to lose seven hit points and then he's<00:13:54.519> out<00:13:54.680> of<00:13:54.839> budget<00:13:55.519> and<00:13:55.639> now<00:13:55.839> will<00:13:56.120> is<00:13:56.240> very 00:13:56.430 --> 00:13:56.440 align:start position:0% he's out of budget and now will is very 00:13:56.440 --> 00:13:58.069 align:start position:0% he's out of budget and now will is very angry<00:13:56.800> indeed<00:13:57.240> and<00:13:57.320> he<00:13:57.480> going<00:13:57.639> to<00:13:57.800> kill 00:13:58.069 --> 00:13:58.079 align:start position:0% angry indeed and he going to kill 00:13:58.079 --> 00:14:00.389 align:start position:0% angry indeed and he going to kill everybody<00:13:58.440> else 00:14:00.389 --> 00:14:00.399 align:start position:0% everybody else 00:14:00.399 --> 00:14:02.110 align:start position:0% everybody else now<00:14:00.560> this<00:14:00.720> may<00:14:00.880> seem<00:14:01.079> a<00:14:01.199> bit<00:14:01.440> abstract<00:14:01.920> so 00:14:02.110 --> 00:14:02.120 align:start position:0% now this may seem a bit abstract so 00:14:02.120 --> 00:14:04.509 align:start position:0% now this may seem a bit abstract so let's<00:14:02.720> get<00:14:02.839> it<00:14:03.000> more<00:14:03.240> concrete<00:14:04.000> so<00:14:04.199> this<00:14:04.279> is<00:14:04.360> a 00:14:04.509 --> 00:14:04.519 align:start position:0% let's get it more concrete so this is a 00:14:04.519 --> 00:14:06.110 align:start position:0% let's get it more concrete so this is a different<00:14:04.800> example<00:14:05.160> the<00:14:05.279> previous<00:14:05.600> one<00:14:05.880> was 00:14:06.110 --> 00:14:06.120 align:start position:0% different example the previous one was 00:14:06.120 --> 00:14:08.389 align:start position:0% different example the previous one was with<00:14:06.440> eight<00:14:06.680> hit<00:14:06.880> points<00:14:07.320> this<00:14:07.440> one<00:14:07.639> is<00:14:07.880> just 00:14:08.389 --> 00:14:08.399 align:start position:0% with eight hit points this one is just 00:14:08.399 --> 00:14:10.910 align:start position:0% with eight hit points this one is just three<00:14:09.399> uh<00:14:09.519> the<00:14:09.639> optimal<00:14:10.079> value<00:14:10.320> is<00:14:10.480> more<00:14:10.720> like 00:14:10.910 --> 00:14:10.920 align:start position:0% three uh the optimal value is more like 00:14:10.920 --> 00:14:13.069 align:start position:0% three uh the optimal value is more like 21<00:14:11.680> you<00:14:11.800> know<00:14:12.160> but<00:14:12.440> it's<00:14:12.639> it's<00:14:12.759> hard<00:14:12.920> to 00:14:13.069 --> 00:14:13.079 align:start position:0% 21 you know but it's it's hard to 00:14:13.079 --> 00:14:15.150 align:start position:0% 21 you know but it's it's hard to visualize<00:14:13.639> that<00:14:13.959> so<00:14:14.079> let's<00:14:14.279> go<00:14:14.399> with<00:14:14.560> three 00:14:15.150 --> 00:14:15.160 align:start position:0% visualize that so let's go with three 00:14:15.160 --> 00:14:17.990 align:start position:0% visualize that so let's go with three first<00:14:16.160> uh<00:14:16.480> yeah<00:14:16.639> so<00:14:16.839> everybody<00:14:17.560> everybody's 00:14:17.990 --> 00:14:18.000 align:start position:0% first uh yeah so everybody everybody's 00:14:18.000 --> 00:14:19.749 align:start position:0% first uh yeah so everybody everybody's on<00:14:18.160> the<00:14:18.279> same<00:14:18.480> bucket<00:14:18.920> in<00:14:19.040> the<00:14:19.160> beginning 00:14:19.749 --> 00:14:19.759 align:start position:0% on the same bucket in the beginning 00:14:19.759 --> 00:14:22.509 align:start position:0% on the same bucket in the beginning everyone<00:14:20.120> has<00:14:20.279> three<00:14:20.560> HP<00:14:21.399> and<00:14:21.560> the<00:14:22.160> uh<00:14:22.320> white 00:14:22.509 --> 00:14:22.519 align:start position:0% everyone has three HP and the uh white 00:14:22.519 --> 00:14:26.069 align:start position:0% everyone has three HP and the uh white arrows<00:14:23.279> point<00:14:23.720> to<00:14:24.000> the<00:14:24.839> matchmaking<00:14:25.839> so 00:14:26.069 --> 00:14:26.079 align:start position:0% arrows point to the matchmaking so 00:14:26.079 --> 00:14:29.350 align:start position:0% arrows point to the matchmaking so Willie<00:14:26.399> is<00:14:26.519> spared<00:14:27.040> against<00:14:27.800> red 00:14:29.350 --> 00:14:29.360 align:start position:0% Willie is spared against red 00:14:29.360 --> 00:14:33.230 align:start position:0% Willie is spared against red and<00:14:29.560> green<00:14:29.880> is<00:14:30.000> spared<00:14:30.519> against<00:14:31.519> gray<00:14:32.519> so<00:14:33.000> red 00:14:33.230 --> 00:14:33.240 align:start position:0% and green is spared against gray so red 00:14:33.240 --> 00:14:36.310 align:start position:0% and green is spared against gray so red and<00:14:33.399> green<00:14:33.720> lose<00:14:34.160> so<00:14:34.399> they're<00:14:35.120> demoted<00:14:36.120> then 00:14:36.310 --> 00:14:36.320 align:start position:0% and green lose so they're demoted then 00:14:36.320 --> 00:14:38.389 align:start position:0% and green lose so they're demoted then we<00:14:36.560> rematch<00:14:36.959> again<00:14:37.360> now<00:14:37.600> this<00:14:37.759> time<00:14:37.959> Willie<00:14:38.240> is 00:14:38.389 --> 00:14:38.399 align:start position:0% we rematch again now this time Willie is 00:14:38.399 --> 00:14:42.030 align:start position:0% we rematch again now this time Willie is against<00:14:38.720> gray<00:14:39.440> red<00:14:39.720> is<00:14:39.959> against<00:14:40.800> Green<00:14:41.800> so 00:14:42.030 --> 00:14:42.040 align:start position:0% against gray red is against Green so 00:14:42.040 --> 00:14:44.710 align:start position:0% against gray red is against Green so green<00:14:42.360> loses<00:14:43.240> gray<00:14:43.560> loses<00:14:44.240> and<00:14:44.360> he<00:14:44.480> keeps 00:14:44.710 --> 00:14:44.720 align:start position:0% green loses gray loses and he keeps 00:14:44.720 --> 00:14:46.949 align:start position:0% green loses gray loses and he keeps going<00:14:44.920> like<00:14:45.160> this<00:14:45.320> you<00:14:45.399> know<00:14:45.600> this<00:14:45.839> logic<00:14:46.839> uh 00:14:46.949 --> 00:14:46.959 align:start position:0% going like this you know this logic uh 00:14:46.959 --> 00:14:50.829 align:start position:0% going like this you know this logic uh of<00:14:47.199> bearing<00:14:48.000> whoever<00:14:48.360> loses<00:14:49.079> gets<00:14:49.720> demoted<00:14:50.720> uh 00:14:50.829 --> 00:14:50.839 align:start position:0% of bearing whoever loses gets demoted uh 00:14:50.839 --> 00:14:53.990 align:start position:0% of bearing whoever loses gets demoted uh and<00:14:51.320> eventually<00:14:52.320> Willie<00:14:52.639> wins<00:14:53.000> you<00:14:53.160> know<00:14:53.360> he 00:14:53.990 --> 00:14:54.000 align:start position:0% and eventually Willie wins you know he 00:14:54.000 --> 00:14:54.910 align:start position:0% and eventually Willie wins you know he kills 00:14:54.910 --> 00:14:54.920 align:start position:0% kills 00:14:54.920 --> 00:14:57.310 align:start position:0% kills everyone<00:14:55.920> uh<00:14:56.199> but<00:14:56.320> on<00:14:56.519> this<00:14:56.680> example<00:14:57.040> note 00:14:57.310 --> 00:14:57.320 align:start position:0% everyone uh but on this example note 00:14:57.320 --> 00:14:59.189 align:start position:0% everyone uh but on this example note that<00:14:57.680> we<00:14:57.800> assume<00:14:58.040> there's<00:14:58.240> no<00:14:58.440> censorship<00:14:59.040> so 00:14:59.189 --> 00:14:59.199 align:start position:0% that we assume there's no censorship so 00:14:59.199 --> 00:15:01.069 align:start position:0% that we assume there's no censorship so will<00:14:59.519> didn't<00:14:59.720> lose<00:14:59.959> any<00:15:00.120> hearts<00:15:00.759> he<00:15:00.920> could 00:15:01.069 --> 00:15:01.079 align:start position:0% will didn't lose any hearts he could 00:15:01.079 --> 00:15:03.389 align:start position:0% will didn't lose any hearts he could have<00:15:01.199> lost<00:15:01.720> Hearts<00:15:02.480> uh<00:15:02.600> but<00:15:02.720> it's<00:15:02.959> you<00:15:03.079> know<00:15:03.240> it 00:15:03.389 --> 00:15:03.399 align:start position:0% have lost Hearts uh but it's you know it 00:15:03.399 --> 00:15:05.870 align:start position:0% have lost Hearts uh but it's you know it would<00:15:03.600> take<00:15:04.040> more<00:15:05.040> images<00:15:05.360> to<00:15:05.480> do<00:15:05.639> that<00:15:05.800> so 00:15:05.870 --> 00:15:05.880 align:start position:0% would take more images to do that so 00:15:05.880 --> 00:15:07.110 align:start position:0% would take more images to do that so we're<00:15:06.120> just<00:15:06.279> assuming<00:15:06.720> that<00:15:06.839> you<00:15:06.920> know 00:15:07.110 --> 00:15:07.120 align:start position:0% we're just assuming that you know 00:15:07.120 --> 00:15:09.189 align:start position:0% we're just assuming that you know there's<00:15:07.279> no<00:15:07.480> censorship<00:15:08.440> for<00:15:08.680> this<00:15:08.839> figure 00:15:09.189 --> 00:15:09.199 align:start position:0% there's no censorship for this figure 00:15:09.199 --> 00:15:10.829 align:start position:0% there's no censorship for this figure but<00:15:09.360> there<00:15:09.519> could<00:15:09.720> be<00:15:10.160> uh<00:15:10.240> so<00:15:10.440> Willie<00:15:10.680> could 00:15:10.829 --> 00:15:10.839 align:start position:0% but there could be uh so Willie could 00:15:10.839 --> 00:15:14.829 align:start position:0% but there could be uh so Willie could lose<00:15:11.079> two<00:15:11.320> rounds<00:15:12.040> but<00:15:12.199> not<00:15:12.360> the<00:15:12.519> third 00:15:14.829 --> 00:15:14.839 align:start position:0% 00:15:14.839 --> 00:15:17.990 align:start position:0% one<00:15:15.839> but<00:15:16.120> we<00:15:16.320> didn't<00:15:16.880> talk<00:15:17.160> about<00:15:17.560> how<00:15:17.800> this 00:15:17.990 --> 00:15:18.000 align:start position:0% one but we didn't talk about how this 00:15:18.000 --> 00:15:21.030 align:start position:0% one but we didn't talk about how this matchmaking<00:15:18.600> is<00:15:19.120> done<00:15:20.120> uh<00:15:20.320> and<00:15:20.480> this<00:15:20.600> is<00:15:20.839> quite 00:15:21.030 --> 00:15:21.040 align:start position:0% matchmaking is done uh and this is quite 00:15:21.040 --> 00:15:22.629 align:start position:0% matchmaking is done uh and this is quite delicate<00:15:21.440> in<00:15:21.560> fact<00:15:21.759> this<00:15:21.880> is<00:15:22.040> at<00:15:22.160> the<00:15:22.279> heart<00:15:22.440> of 00:15:22.629 --> 00:15:22.639 align:start position:0% delicate in fact this is at the heart of 00:15:22.639 --> 00:15:24.670 align:start position:0% delicate in fact this is at the heart of Dave<00:15:22.880> the<00:15:23.079> matchmaking<00:15:24.040> we<00:15:24.199> can't<00:15:24.399> do<00:15:24.519> it 00:15:24.670 --> 00:15:24.680 align:start position:0% Dave the matchmaking we can't do it 00:15:24.680 --> 00:15:27.710 align:start position:0% Dave the matchmaking we can't do it randomly<00:15:25.399> we<00:15:25.519> cannot<00:15:25.920> do<00:15:26.240> this<00:15:27.240> uh 00:15:27.710 --> 00:15:27.720 align:start position:0% randomly we cannot do this uh 00:15:27.720 --> 00:15:29.509 align:start position:0% randomly we cannot do this uh adversarially<00:15:28.720> bus 00:15:29.509 --> 00:15:29.519 align:start position:0% adversarially bus 00:15:29.519 --> 00:15:31.150 align:start position:0% adversarially bus you<00:15:29.680> know<00:15:29.959> it<00:15:30.160> has<00:15:30.279> to<00:15:30.399> be<00:15:30.519> done<00:15:30.639> in<00:15:30.759> a<00:15:30.920> very 00:15:31.150 --> 00:15:31.160 align:start position:0% you know it has to be done in a very 00:15:31.160 --> 00:15:33.590 align:start position:0% you know it has to be done in a very specific<00:15:31.600> way<00:15:32.160> which<00:15:32.319> is<00:15:32.560> we<00:15:32.680> need<00:15:32.880> to<00:15:33.000> do 00:15:33.590 --> 00:15:33.600 align:start position:0% specific way which is we need to do 00:15:33.600 --> 00:15:36.470 align:start position:0% specific way which is we need to do matchmaking<00:15:34.600> by<00:15:34.959> hit<00:15:35.240> point<00:15:35.759> so<00:15:35.959> we<00:15:36.079> want<00:15:36.279> to 00:15:36.470 --> 00:15:36.480 align:start position:0% matchmaking by hit point so we want to 00:15:36.480 --> 00:15:38.269 align:start position:0% matchmaking by hit point so we want to match<00:15:36.720> the<00:15:36.880> same<00:15:37.160> hit<00:15:37.360> point<00:15:37.560> with<00:15:37.800> same<00:15:38.040> hit 00:15:38.269 --> 00:15:38.279 align:start position:0% match the same hit point with same hit 00:15:38.279 --> 00:15:41.150 align:start position:0% match the same hit point with same hit point<00:15:38.920> or<00:15:39.199> at<00:15:39.360> least<00:15:39.720> as<00:15:39.880> close<00:15:40.199> as<00:15:40.399> possible 00:15:41.150 --> 00:15:41.160 align:start position:0% point or at least as close as possible 00:15:41.160 --> 00:15:42.550 align:start position:0% point or at least as close as possible so<00:15:41.319> looking<00:15:41.639> back<00:15:41.759> it's<00:15:41.920> the<00:15:42.040> same<00:15:42.199> image<00:15:42.480> you 00:15:42.550 --> 00:15:42.560 align:start position:0% so looking back it's the same image you 00:15:42.560 --> 00:15:44.949 align:start position:0% so looking back it's the same image you know<00:15:42.759> we<00:15:42.880> did<00:15:43.160> the<00:15:43.360> correct<00:15:43.759> matchmaking<00:15:44.720> so 00:15:44.949 --> 00:15:44.959 align:start position:0% know we did the correct matchmaking so 00:15:44.959 --> 00:15:47.749 align:start position:0% know we did the correct matchmaking so on<00:15:45.120> the<00:15:45.360> second<00:15:45.720> round<00:15:46.360> Dave<00:15:46.720> is<00:15:46.920> matched<00:15:47.519> not 00:15:47.749 --> 00:15:47.759 align:start position:0% on the second round Dave is matched not 00:15:47.759 --> 00:15:49.710 align:start position:0% on the second round Dave is matched not Dave<00:15:48.000> Willie<00:15:48.360> Willie<00:15:48.680> is<00:15:48.759> matched<00:15:49.199> against 00:15:49.710 --> 00:15:49.720 align:start position:0% Dave Willie Willie is matched against 00:15:49.720 --> 00:15:52.030 align:start position:0% Dave Willie Willie is matched against the<00:15:49.880> gray<00:15:50.160> one<00:15:50.959> he's<00:15:51.120> not<00:15:51.279> matched<00:15:51.600> against 00:15:52.030 --> 00:15:52.040 align:start position:0% the gray one he's not matched against 00:15:52.040 --> 00:15:55.949 align:start position:0% the gray one he's not matched against red<00:15:52.319> or<00:15:52.560> green<00:15:53.360> has<00:15:53.480> to<00:15:53.600> be<00:15:53.720> matched<00:15:54.279> with<00:15:54.959> gray 00:15:55.949 --> 00:15:55.959 align:start position:0% red or green has to be matched with gray 00:15:55.959 --> 00:15:57.509 align:start position:0% red or green has to be matched with gray third<00:15:56.240> round<00:15:56.480> is<00:15:56.639> not<00:15:56.839> possible<00:15:57.120> to<00:15:57.240> do<00:15:57.360> a 00:15:57.509 --> 00:15:57.519 align:start position:0% third round is not possible to do a 00:15:57.519 --> 00:16:00.389 align:start position:0% third round is not possible to do a perfect<00:15:58.079> pairing<00:15:58.759> uh<00:15:59.000> so<00:15:59.160> we<00:15:59.279> do<00:15:59.440> our<00:15:59.680> best<00:16:00.240> and 00:16:00.389 --> 00:16:00.399 align:start position:0% perfect pairing uh so we do our best and 00:16:00.399 --> 00:16:03.069 align:start position:0% perfect pairing uh so we do our best and our<00:16:00.600> best<00:16:00.839> would<00:16:01.000> be<00:16:01.160> either<00:16:01.399> gray<00:16:01.680> or<00:16:01.959> red<00:16:02.959> and 00:16:03.069 --> 00:16:03.079 align:start position:0% our best would be either gray or red and 00:16:03.079 --> 00:16:05.550 align:start position:0% our best would be either gray or red and so<00:16:03.279> on<00:16:03.480> so<00:16:03.759> like<00:16:04.079> abstractly<00:16:04.639> it's<00:16:04.839> like<00:16:05.160> as<00:16:05.319> if 00:16:05.550 --> 00:16:05.560 align:start position:0% so on so like abstractly it's like as if 00:16:05.560 --> 00:16:09.430 align:start position:0% so on so like abstractly it's like as if we<00:16:06.199> sorted<00:16:07.199> every<00:16:07.560> Claim<00:16:08.079> by<00:16:08.319> hit<00:16:08.600> point 00:16:09.430 --> 00:16:09.440 align:start position:0% we sorted every Claim by hit point 00:16:09.440 --> 00:16:12.069 align:start position:0% we sorted every Claim by hit point highest<00:16:09.759> to<00:16:09.959> lowest<00:16:10.880> and<00:16:11.000> then<00:16:11.199> we<00:16:11.399> match<00:16:11.720> them 00:16:12.069 --> 00:16:12.079 align:start position:0% highest to lowest and then we match them 00:16:12.079 --> 00:16:14.629 align:start position:0% highest to lowest and then we match them left<00:16:12.600> to 00:16:14.629 --> 00:16:14.639 align:start position:0% left to 00:16:14.639 --> 00:16:17.069 align:start position:0% left to right<00:16:15.639> yeah<00:16:15.759> and<00:16:15.920> when<00:16:16.040> we<00:16:16.160> do<00:16:16.399> that<00:16:16.880> we 00:16:17.069 --> 00:16:17.079 align:start position:0% right yeah and when we do that we 00:16:17.079 --> 00:16:18.629 align:start position:0% right yeah and when we do that we actually<00:16:17.360> get<00:16:17.600> exactly<00:16:17.959> what<00:16:18.120> we<00:16:18.240> wanted<00:16:18.519> you 00:16:18.629 --> 00:16:18.639 align:start position:0% actually get exactly what we wanted you 00:16:18.639 --> 00:16:20.870 align:start position:0% actually get exactly what we wanted you know<00:16:18.800> if<00:16:18.920> it<00:16:19.079> was<00:16:19.319> random<00:16:20.319> uh<00:16:20.440> there<00:16:20.560> will<00:16:20.720> be 00:16:20.870 --> 00:16:20.880 align:start position:0% know if it was random uh there will be 00:16:20.880 --> 00:16:25.350 align:start position:0% know if it was random uh there will be no<00:16:21.560> um<00:16:22.480> uh<00:16:22.600> improvements<00:16:23.319> over<00:16:23.920> PRT<00:16:24.920> but<00:16:25.120> if<00:16:25.240> we 00:16:25.350 --> 00:16:25.360 align:start position:0% no um uh improvements over PRT but if we 00:16:25.360 --> 00:16:27.870 align:start position:0% no um uh improvements over PRT but if we do<00:16:25.519> the<00:16:25.639> rematching<00:16:26.600> with<00:16:26.800> similar<00:16:27.160> HP<00:16:27.720> we 00:16:27.870 --> 00:16:27.880 align:start position:0% do the rematching with similar HP we 00:16:27.880 --> 00:16:29.910 align:start position:0% do the rematching with similar HP we actually<00:16:28.160> dilute<00:16:28.639> the<00:16:28.720> set<00:16:28.920> 7<00:16:29.199> Days<00:16:29.519> across 00:16:29.910 --> 00:16:29.920 align:start position:0% actually dilute the set 7 Days across 00:16:29.920 --> 00:16:31.870 align:start position:0% actually dilute the set 7 Days across the<00:16:30.040> whole<00:16:30.279> dispute<00:16:30.880> we<00:16:31.000> get<00:16:31.240> exactly<00:16:31.600> what<00:16:31.759> we 00:16:31.870 --> 00:16:31.880 align:start position:0% the whole dispute we get exactly what we 00:16:31.880 --> 00:16:33.710 align:start position:0% the whole dispute we get exactly what we wanted<00:16:32.519> there's<00:16:32.759> some<00:16:32.959> constants<00:16:33.440> there<00:16:33.600> you 00:16:33.710 --> 00:16:33.720 align:start position:0% wanted there's some constants there you 00:16:33.720 --> 00:16:35.189 align:start position:0% wanted there's some constants there you know<00:16:33.880> that's<00:16:34.040> why<00:16:34.160> I<00:16:34.279> said<00:16:34.519> proportional<00:16:35.040> it's 00:16:35.189 --> 00:16:35.199 align:start position:0% know that's why I said proportional it's 00:16:35.199 --> 00:16:38.230 align:start position:0% know that's why I said proportional it's not<00:16:35.440> exactly<00:16:35.959> that<00:16:36.680> but<00:16:36.959> the<00:16:37.120> idea<00:16:37.639> is<00:16:37.880> really 00:16:38.230 --> 00:16:38.240 align:start position:0% not exactly that but the idea is really 00:16:38.240 --> 00:16:41.470 align:start position:0% not exactly that but the idea is really we<00:16:38.360> are<00:16:38.759> amortizing<00:16:39.480> seven<00:16:39.880> days<00:16:40.399> across<00:16:41.360> the 00:16:41.470 --> 00:16:41.480 align:start position:0% we are amortizing seven days across the 00:16:41.480 --> 00:16:43.870 align:start position:0% we are amortizing seven days across the whole<00:16:41.759> dispute<00:16:42.560> and<00:16:42.680> we're<00:16:42.920> only<00:16:43.240> playing 00:16:43.870 --> 00:16:43.880 align:start position:0% whole dispute and we're only playing 00:16:43.880 --> 00:16:46.430 align:start position:0% whole dispute and we're only playing paying<00:16:44.399> one<00:16:44.639> day<00:16:45.199> in<00:16:45.360> that<00:16:45.519> 7-Day<00:16:46.000> example<00:16:46.319> you 00:16:46.430 --> 00:16:46.440 align:start position:0% paying one day in that 7-Day example you 00:16:46.440 --> 00:16:48.949 align:start position:0% paying one day in that 7-Day example you know<00:16:46.560> that<00:16:46.680> I<00:16:46.800> gave<00:16:47.279> earlier<00:16:48.279> uh<00:16:48.600> times 00:16:48.949 --> 00:16:48.959 align:start position:0% know that I gave earlier uh times 00:16:48.959 --> 00:16:50.350 align:start position:0% know that I gave earlier uh times logarithmic<00:16:49.600> of 00:16:50.350 --> 00:16:50.360 align:start position:0% logarithmic of 00:16:50.360 --> 00:16:53.269 align:start position:0% logarithmic of sios<00:16:51.360> uh<00:16:51.480> I<00:16:51.519> mean<00:16:51.680> the<00:16:51.800> real<00:16:52.160> values<00:16:53.000> uh<00:16:53.120> is 00:16:53.269 --> 00:16:53.279 align:start position:0% sios uh I mean the real values uh is 00:16:53.279 --> 00:16:54.710 align:start position:0% sios uh I mean the real values uh is actually<00:16:53.480> more<00:16:53.759> like<00:16:53.920> 10<00:16:54.160> hours<00:16:54.480> you<00:16:54.600> know 00:16:54.710 --> 00:16:54.720 align:start position:0% actually more like 10 hours you know 00:16:54.720 --> 00:16:56.910 align:start position:0% actually more like 10 hours you know then<00:16:54.880> there's<00:16:55.040> a<00:16:55.240> constant<00:16:56.079> we<00:16:56.240> go<00:16:56.440> on<00:16:56.639> all<00:16:56.800> of 00:16:56.910 --> 00:16:56.920 align:start position:0% then there's a constant we go on all of 00:16:56.920 --> 00:16:58.230 align:start position:0% then there's a constant we go on all of that<00:16:57.079> with<00:16:57.199> a<00:16:57.319> lot<00:16:57.440> more<00:16:57.600> nuance<00:16:58.079> and 00:16:58.230 --> 00:16:58.240 align:start position:0% that with a lot more nuance and 00:16:58.240 --> 00:16:59.829 align:start position:0% that with a lot more nuance and discussions<00:16:58.639> on<00:16:58.920> the<00:16:59.040> paper<00:16:59.279> so<00:16:59.399> we<00:16:59.519> can<00:16:59.680> check 00:16:59.829 --> 00:16:59.839 align:start position:0% discussions on the paper so we can check 00:16:59.839 --> 00:17:00.590 align:start position:0% discussions on the paper so we can check it 00:17:00.590 --> 00:17:00.600 align:start position:0% it 00:17:00.600 --> 00:17:02.949 align:start position:0% it out<00:17:01.600> uh<00:17:01.959> yeah<00:17:02.079> so<00:17:02.279> this<00:17:02.399> finishes<00:17:02.759> the 00:17:02.949 --> 00:17:02.959 align:start position:0% out uh yeah so this finishes the 00:17:02.959 --> 00:17:04.990 align:start position:0% out uh yeah so this finishes the description<00:17:03.399> of<00:17:03.560> Dave<00:17:03.880> so<00:17:04.000> it's<00:17:04.079> a<00:17:04.199> repage 00:17:04.990 --> 00:17:05.000 align:start position:0% description of Dave so it's a repage 00:17:05.000 --> 00:17:07.309 align:start position:0% description of Dave so it's a repage tournament<00:17:06.000> where<00:17:06.199> we<00:17:06.360> do<00:17:06.520> the<00:17:06.679> match<00:17:06.959> making 00:17:07.309 --> 00:17:07.319 align:start position:0% tournament where we do the match making 00:17:07.319 --> 00:17:10.110 align:start position:0% tournament where we do the match making with<00:17:07.559> similar<00:17:08.039> HP<00:17:09.039> and<00:17:09.199> when<00:17:09.319> we<00:17:09.480> do<00:17:09.679> that<00:17:09.919> we 00:17:10.110 --> 00:17:10.120 align:start position:0% with similar HP and when we do that we 00:17:10.120 --> 00:17:12.750 align:start position:0% with similar HP and when we do that we amortise<00:17:10.640> the<00:17:10.799> seven<00:17:11.079> days<00:17:11.760> across<00:17:12.319> the<00:17:12.439> whole 00:17:12.750 --> 00:17:12.760 align:start position:0% amortise the seven days across the whole 00:17:12.760 --> 00:17:15.829 align:start position:0% amortise the seven days across the whole dispute<00:17:13.679> instead<00:17:14.000> of<00:17:14.199> over<00:17:14.520> a<00:17:14.679> single 00:17:15.829 --> 00:17:15.839 align:start position:0% dispute instead of over a single 00:17:15.839 --> 00:17:18.870 align:start position:0% dispute instead of over a single round<00:17:16.839> uh<00:17:16.959> so<00:17:17.319> concluding<00:17:17.959> you<00:17:18.120> can<00:17:18.280> be<00:17:18.439> with 00:17:18.870 --> 00:17:18.880 align:start position:0% round uh so concluding you can be with 00:17:18.880 --> 00:17:20.870 align:start position:0% round uh so concluding you can be with you<00:17:19.000> only<00:17:19.160> need<00:17:19.360> a<00:17:19.520> laptop<00:17:20.079> and<00:17:20.280> about<00:17:20.520> a<00:17:20.640> three 00:17:20.870 --> 00:17:20.880 align:start position:0% you only need a laptop and about a three 00:17:20.880 --> 00:17:24.549 align:start position:0% you only need a laptop and about a three e<00:17:21.160> collat<00:17:21.600> room<00:17:22.559> you<00:17:22.679> can<00:17:22.919> defeat<00:17:23.559> anyone 00:17:24.549 --> 00:17:24.559 align:start position:0% e collat room you can defeat anyone 00:17:24.559 --> 00:17:25.870 align:start position:0% e collat room you can defeat anyone because<00:17:24.839> you<00:17:25.000> have<00:17:25.160> this<00:17:25.360> exponential 00:17:25.870 --> 00:17:25.880 align:start position:0% because you have this exponential 00:17:25.880 --> 00:17:28.630 align:start position:0% because you have this exponential Advantage<00:17:26.760> so<00:17:27.000> this<00:17:27.199> means<00:17:27.640> that<00:17:28.000> a<00:17:28.160> rollup 00:17:28.630 --> 00:17:28.640 align:start position:0% Advantage so this means that a rollup 00:17:28.640 --> 00:17:32.070 align:start position:0% Advantage so this means that a rollup that<00:17:28.919> uses<00:17:29.280> Dave<00:17:30.039> inherits<00:17:30.559> the<00:17:30.760> security<00:17:31.200> of 00:17:32.070 --> 00:17:32.080 align:start position:0% that uses Dave inherits the security of 00:17:32.080 --> 00:17:36.549 align:start position:0% that uses Dave inherits the security of L1<00:17:33.080> and<00:17:33.640> for<00:17:33.919> any<00:17:34.200> realistic<00:17:34.760> Cil<00:17:35.559> attacks 00:17:36.549 --> 00:17:36.559 align:start position:0% L1 and for any realistic Cil attacks 00:17:36.559 --> 00:17:38.870 align:start position:0% L1 and for any realistic Cil attacks it's<00:17:36.760> going<00:17:36.919> to<00:17:37.120> take<00:17:37.720> no<00:17:37.960> more<00:17:38.200> than<00:17:38.559> four 00:17:38.870 --> 00:17:38.880 align:start position:0% it's going to take no more than four 00:17:38.880 --> 00:17:42.029 align:start position:0% it's going to take no more than four weeks<00:17:39.640> it's<00:17:39.799> going<00:17:39.919> to<00:17:40.000> be<00:17:40.240> within<00:17:40.640> four<00:17:41.039> weeks 00:17:42.029 --> 00:17:42.039 align:start position:0% weeks it's going to be within four weeks 00:17:42.039 --> 00:17:43.990 align:start position:0% weeks it's going to be within four weeks and<00:17:42.240> thus<00:17:42.480> Dave<00:17:42.799> triumphed<00:17:43.280> over<00:17:43.440> the<00:17:43.600> sibbles 00:17:43.990 --> 00:17:44.000 align:start position:0% and thus Dave triumphed over the sibbles 00:17:44.000 --> 00:17:46.350 align:start position:0% and thus Dave triumphed over the sibbles with<00:17:44.120> a<00:17:44.240> laptop<00:17:44.640> and<00:17:44.799> a<00:17:44.960> small<00:17:45.160> collector<00:17:46.160> but 00:17:46.350 --> 00:17:46.360 align:start position:0% with a laptop and a small collector but 00:17:46.360 --> 00:17:48.510 align:start position:0% with a laptop and a small collector but Dave<00:17:46.600> had<00:17:46.720> no<00:17:46.880> supercomputers<00:17:47.559> on<00:17:47.760> his 00:17:48.510 --> 00:17:48.520 align:start position:0% Dave had no supercomputers on his 00:17:48.520 --> 00:17:51.510 align:start position:0% Dave had no supercomputers on his hands<00:17:49.520> and<00:17:49.679> we<00:17:49.880> get<00:17:50.360> those<00:17:50.640> results<00:17:51.320> yeah 00:17:51.510 --> 00:17:51.520 align:start position:0% hands and we get those results yeah 00:17:51.520 --> 00:17:53.549 align:start position:0% hands and we get those results yeah that's<00:17:51.640> all<00:17:51.799> I<00:17:51.919> had<00:17:52.039> to<00:17:52.320> present<00:17:52.559> to<00:17:52.679> you<00:17:52.799> today 00:17:53.549 --> 00:17:53.559 align:start position:0% that's all I had to present to you today 00:17:53.559 --> 00:17:55.500 align:start position:0% that's all I had to present to you today thank<00:17:53.679> you<00:17:53.840> very<00:17:54.000> much<00:17:54.160> for<00:17:54.360> coming 00:17:55.500 --> 00:17:55.510 align:start position:0% thank you very much for coming 00:17:55.510 --> 00:18:06.270 align:start position:0% thank you very much for coming [Applause] 00:18:06.270 --> 00:18:06.280 align:start position:0% 00:18:06.280 --> 00:18:09.310 align:start position:0% great<00:18:06.520> talk<00:18:07.039> uh<00:18:07.200> love<00:18:07.400> the<00:18:07.480> name<00:18:07.880> Dave<00:18:08.880> um 00:18:09.310 --> 00:18:09.320 align:start position:0% great talk uh love the name Dave um 00:18:09.320 --> 00:18:11.270 align:start position:0% great talk uh love the name Dave um thank<00:18:09.480> you<00:18:10.120> it's<00:18:10.320> got<00:18:10.440> a<00:18:10.520> few<00:18:10.720> few<00:18:10.919> Q&A 00:18:11.270 --> 00:18:11.280 align:start position:0% thank you it's got a few few Q&A 00:18:11.280 --> 00:18:12.470 align:start position:0% thank you it's got a few few Q&A questions<00:18:11.559> you<00:18:11.640> can<00:18:11.760> still<00:18:11.960> add<00:18:12.159> some<00:18:12.280> of<00:18:12.360> the 00:18:12.470 --> 00:18:12.480 align:start position:0% questions you can still add some of the 00:18:12.480 --> 00:18:14.149 align:start position:0% questions you can still add some of the questions<00:18:13.159> um<00:18:13.400> while<00:18:13.559> we're<00:18:13.799> going<00:18:14.000> through 00:18:14.149 --> 00:18:14.159 align:start position:0% questions um while we're going through 00:18:14.159 --> 00:18:16.070 align:start position:0% questions um while we're going through some<00:18:14.280> of<00:18:14.400> these<00:18:14.520> and<00:18:14.640> up<00:18:14.880> vote<00:18:15.080> them<00:18:15.840> uh<00:18:15.960> but 00:18:16.070 --> 00:18:16.080 align:start position:0% some of these and up vote them uh but 00:18:16.080 --> 00:18:17.669 align:start position:0% some of these and up vote them uh but the<00:18:16.200> first<00:18:16.440> question<00:18:16.760> is<00:18:17.000> is<00:18:17.080> a<00:18:17.280> one<00:18:17.440> that<00:18:17.559> I've 00:18:17.669 --> 00:18:17.679 align:start position:0% the first question is is a one that I've 00:18:17.679 --> 00:18:19.549 align:start position:0% the first question is is a one that I've been<00:18:17.799> thinking<00:18:18.120> too<00:18:18.919> um<00:18:19.120> what<00:18:19.240> if<00:18:19.360> there's 00:18:19.549 --> 00:18:19.559 align:start position:0% been thinking too um what if there's 00:18:19.559 --> 00:18:21.630 align:start position:0% been thinking too um what if there's multiple<00:18:20.039> Willies<00:18:20.480> defending<00:18:21.280> won't<00:18:21.520> they 00:18:21.630 --> 00:18:21.640 align:start position:0% multiple Willies defending won't they 00:18:21.640 --> 00:18:23.149 align:start position:0% multiple Willies defending won't they eliminate<00:18:22.080> each<00:18:22.200> other<00:18:22.600> yeah<00:18:22.799> so<00:18:22.919> that's<00:18:23.039> a 00:18:23.149 --> 00:18:23.159 align:start position:0% eliminate each other yeah so that's a 00:18:23.159 --> 00:18:25.549 align:start position:0% eliminate each other yeah so that's a good<00:18:23.400> question<00:18:23.840> uh<00:18:23.960> when<00:18:24.120> we<00:18:24.320> did<00:18:24.799> the 00:18:25.549 --> 00:18:25.559 align:start position:0% good question uh when we did the 00:18:25.559 --> 00:18:27.110 align:start position:0% good question uh when we did the computation<00:18:26.240> hash<00:18:26.600> which<00:18:26.720> is<00:18:26.919> that 00:18:27.110 --> 00:18:27.120 align:start position:0% computation hash which is that 00:18:27.120 --> 00:18:29.149 align:start position:0% computation hash which is that commitment<00:18:27.960> it<00:18:28.080> means<00:18:28.320> that<00:18:28.799> everybody 00:18:29.149 --> 00:18:29.159 align:start position:0% commitment it means that everybody 00:18:29.159 --> 00:18:30.830 align:start position:0% commitment it means that everybody that's<00:18:29.440> honest<00:18:29.880> is<00:18:30.000> going<00:18:30.120> to<00:18:30.240> be<00:18:30.360> on<00:18:30.480> the<00:18:30.600> same 00:18:30.830 --> 00:18:30.840 align:start position:0% that's honest is going to be on the same 00:18:30.840 --> 00:18:32.750 align:start position:0% that's honest is going to be on the same team<00:18:31.480> so<00:18:31.640> if<00:18:31.760> there<00:18:31.840> are<00:18:31.960> many<00:18:32.200> Willies<00:18:32.640> they 00:18:32.750 --> 00:18:32.760 align:start position:0% team so if there are many Willies they 00:18:32.760 --> 00:18:35.710 align:start position:0% team so if there are many Willies they will<00:18:33.039> fight<00:18:33.760> together<00:18:34.400> against<00:18:34.760> the<00:18:34.919> sibl<00:18:35.480> not 00:18:35.710 --> 00:18:35.720 align:start position:0% will fight together against the sibl not 00:18:35.720 --> 00:18:37.990 align:start position:0% will fight together against the sibl not against<00:18:36.000> each<00:18:36.200> other<00:18:36.840> because<00:18:37.080> the<00:18:37.280> claim<00:18:37.840> the 00:18:37.990 --> 00:18:38.000 align:start position:0% against each other because the claim the 00:18:38.000 --> 00:18:40.430 align:start position:0% against each other because the claim the same<00:18:38.320> thing<00:18:38.960> so<00:18:39.159> we<00:18:39.280> have<00:18:39.480> this<00:18:39.720> uniqueness<00:18:40.280> of 00:18:40.430 --> 00:18:40.440 align:start position:0% same thing so we have this uniqueness of 00:18:40.440 --> 00:18:42.430 align:start position:0% same thing so we have this uniqueness of claims<00:18:40.880> when<00:18:41.000> we<00:18:41.120> do<00:18:41.280> the<00:18:41.440> computation<00:18:42.039> hash 00:18:42.430 --> 00:18:42.440 align:start position:0% claims when we do the computation hash 00:18:42.440 --> 00:18:44.870 align:start position:0% claims when we do the computation hash and<00:18:42.600> we<00:18:42.760> allow<00:18:43.320> all<00:18:43.520> the<00:18:43.640> honest<00:18:44.000> validators 00:18:44.870 --> 00:18:44.880 align:start position:0% and we allow all the honest validators 00:18:44.880 --> 00:18:47.870 align:start position:0% and we allow all the honest validators to<00:18:45.039> join<00:18:45.400> teams<00:18:46.400> so<00:18:46.679> we<00:18:46.880> consider<00:18:47.360> this<00:18:47.520> single 00:18:47.870 --> 00:18:47.880 align:start position:0% to join teams so we consider this single 00:18:47.880 --> 00:18:49.950 align:start position:0% to join teams so we consider this single ton<00:18:48.159> hero<00:18:48.559> know<00:18:48.679> it's<00:18:48.919> just<00:18:49.200> Willie<00:18:49.640> but<00:18:49.760> in 00:18:49.950 --> 00:18:49.960 align:start position:0% ton hero know it's just Willie but in 00:18:49.960 --> 00:18:51.950 align:start position:0% ton hero know it's just Willie but in practice<00:18:50.480> there<00:18:50.679> going<00:18:50.760> to<00:18:50.840> be<00:18:51.000> many<00:18:51.200> Willies 00:18:51.950 --> 00:18:51.960 align:start position:0% practice there going to be many Willies 00:18:51.960 --> 00:18:53.830 align:start position:0% practice there going to be many Willies and<00:18:52.120> they<00:18:52.320> all<00:18:52.559> fight<00:18:53.039> together<00:18:53.400> pushing<00:18:53.720> in 00:18:53.830 --> 00:18:53.840 align:start position:0% and they all fight together pushing in 00:18:53.840 --> 00:18:55.669 align:start position:0% and they all fight together pushing in the<00:18:53.960> same 00:18:55.669 --> 00:18:55.679 align:start position:0% the same 00:18:55.679 --> 00:18:58.830 align:start position:0% the same direction<00:18:56.679> cool<00:18:57.600> uh<00:18:57.799> next<00:18:58.000> question<00:18:58.280> is<00:18:58.440> about 00:18:58.830 --> 00:18:58.840 align:start position:0% direction cool uh next question is about 00:18:58.840 --> 00:19:00.710 align:start position:0% direction cool uh next question is about your<00:18:58.960> censorship<00:18:59.440> model<00:19:00.000> is<00:19:00.120> your<00:19:00.280> censorship 00:19:00.710 --> 00:19:00.720 align:start position:0% your censorship model is your censorship 00:19:00.720 --> 00:19:02.909 align:start position:0% your censorship model is your censorship model<00:19:01.000> hard<00:19:01.280> censorship<00:19:02.200> and<00:19:02.320> do<00:19:02.520> inclusion 00:19:02.909 --> 00:19:02.919 align:start position:0% model hard censorship and do inclusion 00:19:02.919 --> 00:19:05.270 align:start position:0% model hard censorship and do inclusion lists<00:19:03.320> improve<00:19:03.799> these<00:19:04.039> things<00:19:04.720> yeah<00:19:04.919> so<00:19:05.159> the 00:19:05.270 --> 00:19:05.280 align:start position:0% lists improve these things yeah so the 00:19:05.280 --> 00:19:06.870 align:start position:0% lists improve these things yeah so the inclusion<00:19:05.679> lists<00:19:05.960> I<00:19:06.039> don't<00:19:06.159> think<00:19:06.360> they<00:19:06.520> help 00:19:06.870 --> 00:19:06.880 align:start position:0% inclusion lists I don't think they help 00:19:06.880 --> 00:19:08.750 align:start position:0% inclusion lists I don't think they help exactly<00:19:07.200> on<00:19:07.360> that<00:19:07.840> uh<00:19:07.919> so<00:19:08.120> the<00:19:08.240> censorship 00:19:08.750 --> 00:19:08.760 align:start position:0% exactly on that uh so the censorship 00:19:08.760 --> 00:19:10.909 align:start position:0% exactly on that uh so the censorship model<00:19:09.039> you<00:19:09.159> know<00:19:09.280> luk<00:19:09.640> um<00:19:09.840> gave<00:19:10.000> a<00:19:10.120> very<00:19:10.360> good 00:19:10.909 --> 00:19:10.919 align:start position:0% model you know luk um gave a very good 00:19:10.919 --> 00:19:14.510 align:start position:0% model you know luk um gave a very good uh<00:19:11.039> intuition<00:19:11.480> of<00:19:11.600> it<00:19:11.840> is<00:19:12.480> that<00:19:13.480> 7<00:19:13.880> days<00:19:14.200> is<00:19:14.360> the 00:19:14.510 --> 00:19:14.520 align:start position:0% uh intuition of it is that 7 days is the 00:19:14.520 --> 00:19:17.710 align:start position:0% uh intuition of it is that 7 days is the time<00:19:14.840> we<00:19:15.000> can<00:19:15.760> try<00:19:16.000> to<00:19:16.159> organize<00:19:16.559> a<00:19:16.679> hard<00:19:16.880> Fork 00:19:17.710 --> 00:19:17.720 align:start position:0% time we can try to organize a hard Fork 00:19:17.720 --> 00:19:19.710 align:start position:0% time we can try to organize a hard Fork so<00:19:17.960> Suppose<00:19:18.280> there<00:19:18.400> is<00:19:18.520> hard<00:19:18.799> censorship<00:19:19.480> my 00:19:19.710 --> 00:19:19.720 align:start position:0% so Suppose there is hard censorship my 00:19:19.720 --> 00:19:21.390 align:start position:0% so Suppose there is hard censorship my transactions<00:19:20.320> are<00:19:20.559> not<00:19:20.799> getting<00:19:21.080> to<00:19:21.280> the 00:19:21.390 --> 00:19:21.400 align:start position:0% transactions are not getting to the 00:19:21.400 --> 00:19:23.470 align:start position:0% transactions are not getting to the blockchain<00:19:22.400> so<00:19:22.640> what's<00:19:22.880> going<00:19:22.960> to<00:19:23.080> happen<00:19:23.320> is 00:19:23.470 --> 00:19:23.480 align:start position:0% blockchain so what's going to happen is 00:19:23.480 --> 00:19:24.870 align:start position:0% blockchain so what's going to happen is that<00:19:23.600> you<00:19:23.720> know<00:19:24.120> Twitter's<00:19:24.520> going<00:19:24.600> to<00:19:24.720> catch 00:19:24.870 --> 00:19:24.880 align:start position:0% that you know Twitter's going to catch 00:19:24.880 --> 00:19:26.470 align:start position:0% that you know Twitter's going to catch on<00:19:25.039> fire<00:19:25.320> I'm<00:19:25.400> going<00:19:25.520> to<00:19:25.600> scream<00:19:25.840> to<00:19:26.000> everybody 00:19:26.470 --> 00:19:26.480 align:start position:0% on fire I'm going to scream to everybody 00:19:26.480 --> 00:19:28.470 align:start position:0% on fire I'm going to scream to everybody look<00:19:26.720> I'm<00:19:26.840> being<00:19:27.080> sensored<00:19:27.600> for<00:19:27.840> already<00:19:28.159> 4 00:19:28.470 --> 00:19:28.480 align:start position:0% look I'm being sensored for already 4 00:19:28.480 --> 00:19:31.870 align:start position:0% look I'm being sensored for already 4 days<00:19:28.799> is<00:19:29.720> everybody's<00:19:30.280> going<00:19:30.360> to<00:19:30.640> get<00:19:31.400> uh<00:19:31.760> you 00:19:31.870 --> 00:19:31.880 align:start position:0% days is everybody's going to get uh you 00:19:31.880 --> 00:19:33.789 align:start position:0% days is everybody's going to get uh you know<00:19:32.080> iffy<00:19:32.400> about<00:19:32.679> this<00:19:32.880> and<00:19:33.080> we<00:19:33.200> are<00:19:33.320> going<00:19:33.480> to 00:19:33.789 --> 00:19:33.799 align:start position:0% know iffy about this and we are going to 00:19:33.799 --> 00:19:34.710 align:start position:0% know iffy about this and we are going to together 00:19:34.710 --> 00:19:34.720 align:start position:0% together 00:19:34.720 --> 00:19:37.350 align:start position:0% together organize<00:19:35.720> uh<00:19:36.400> like<00:19:36.520> a<00:19:36.679> hard<00:19:36.919> work<00:19:37.159> or 00:19:37.350 --> 00:19:37.360 align:start position:0% organize uh like a hard work or 00:19:37.360 --> 00:19:40.270 align:start position:0% organize uh like a hard work or something<00:19:37.919> to<00:19:38.200> fix<00:19:38.600> this<00:19:39.480> so<00:19:39.720> the<00:19:39.840> point<00:19:40.080> is 00:19:40.270 --> 00:19:40.280 align:start position:0% something to fix this so the point is 00:19:40.280 --> 00:19:42.510 align:start position:0% something to fix this so the point is not<00:19:40.640> that<00:19:41.000> there<00:19:41.240> can't<00:19:41.520> be<00:19:41.760> a<00:19:41.880> 7-Day 00:19:42.510 --> 00:19:42.520 align:start position:0% not that there can't be a 7-Day 00:19:42.520 --> 00:19:44.830 align:start position:0% not that there can't be a 7-Day censorship<00:19:43.520> it<00:19:43.640> is<00:19:43.799> that<00:19:44.080> if<00:19:44.320> there<00:19:44.480> is<00:19:44.679> a 00:19:44.830 --> 00:19:44.840 align:start position:0% censorship it is that if there is a 00:19:44.840 --> 00:19:48.270 align:start position:0% censorship it is that if there is a seven<00:19:45.400> week<00:19:46.159> censorship<00:19:47.159> the<00:19:47.360> Ean<00:19:47.880> Community 00:19:48.270 --> 00:19:48.280 align:start position:0% seven week censorship the Ean Community 00:19:48.280 --> 00:19:50.430 align:start position:0% seven week censorship the Ean Community will<00:19:48.679> together<00:19:49.000> realize<00:19:49.760> and<00:19:49.919> say<00:19:50.159> that<00:19:50.320> this 00:19:50.430 --> 00:19:50.440 align:start position:0% will together realize and say that this 00:19:50.440 --> 00:19:52.990 align:start position:0% will together realize and say that this is<00:19:50.559> a<00:19:50.799> problem<00:19:51.320> and<00:19:51.440> then<00:19:51.600> hard<00:19:51.880> Fork<00:19:52.200> away<00:19:52.880> and 00:19:52.990 --> 00:19:53.000 align:start position:0% is a problem and then hard Fork away and 00:19:53.000 --> 00:19:55.470 align:start position:0% is a problem and then hard Fork away and if<00:19:53.120> we<00:19:53.320> put<00:19:53.520> like<00:19:53.640> a<00:19:53.799> one-<00:19:54.000> day<00:19:54.360> censorship<00:19:55.360> I 00:19:55.470 --> 00:19:55.480 align:start position:0% if we put like a one- day censorship I 00:19:55.480 --> 00:19:58.710 align:start position:0% if we put like a one- day censorship I would<00:19:55.720> convince<00:19:56.240> nobody<00:19:57.240> seven<00:19:57.640> days<00:19:58.320> it's 00:19:58.710 --> 00:19:58.720 align:start position:0% would convince nobody seven days it's 00:19:58.720 --> 00:20:01.149 align:start position:0% would convince nobody seven days it's the<00:19:58.799> threshold<00:19:59.240> that<00:19:59.360> we<00:19:59.840> consider<00:20:00.840> to<00:20:01.000> be 00:20:01.149 --> 00:20:01.159 align:start position:0% the threshold that we consider to be 00:20:01.159 --> 00:20:02.310 align:start position:0% the threshold that we consider to be easy<00:20:01.400> to 00:20:02.310 --> 00:20:02.320 align:start position:0% easy to 00:20:02.320 --> 00:20:05.909 align:start position:0% easy to convince<00:20:03.320> cool<00:20:04.200> uh<00:20:04.360> the<00:20:04.480> next<00:20:04.760> question<00:20:05.720> what 00:20:05.909 --> 00:20:05.919 align:start position:0% convince cool uh the next question what 00:20:05.919 --> 00:20:08.230 align:start position:0% convince cool uh the next question what happens<00:20:06.200> to<00:20:06.360> levels<00:20:06.679> in<00:20:06.760> the<00:20:06.840> current<00:20:07.120> PRT<00:20:08.120> uh 00:20:08.230 --> 00:20:08.240 align:start position:0% happens to levels in the current PRT uh 00:20:08.240 --> 00:20:09.950 align:start position:0% happens to levels in the current PRT uh will<00:20:08.400> your<00:20:08.559> plans<00:20:08.880> be<00:20:09.080> to<00:20:09.240> eliminate<00:20:09.640> it<00:20:09.760> with 00:20:09.950 --> 00:20:09.960 align:start position:0% will your plans be to eliminate it with 00:20:09.960 --> 00:20:13.590 align:start position:0% will your plans be to eliminate it with ZK<00:20:10.840> yeah<00:20:11.120> exactly<00:20:11.520> so<00:20:11.760> PRT<00:20:12.679> uh<00:20:13.039> if<00:20:13.120> you<00:20:13.280> look<00:20:13.480> at 00:20:13.590 --> 00:20:13.600 align:start position:0% ZK yeah exactly so PRT uh if you look at 00:20:13.600 --> 00:20:15.470 align:start position:0% ZK yeah exactly so PRT uh if you look at our<00:20:13.799> current<00:20:14.080> implementation<00:20:15.039> we<00:20:15.120> are<00:20:15.240> doing 00:20:15.470 --> 00:20:15.480 align:start position:0% our current implementation we are doing 00:20:15.480 --> 00:20:17.789 align:start position:0% our current implementation we are doing it<00:20:15.600> with<00:20:15.760> three<00:20:16.000> levels<00:20:16.960> uh<00:20:17.080> we<00:20:17.240> think<00:20:17.600> with 00:20:17.789 --> 00:20:17.799 align:start position:0% it with three levels uh we think with 00:20:17.799 --> 00:20:19.590 align:start position:0% it with three levels uh we think with some<00:20:18.080> really<00:20:18.320> good<00:20:18.520> engineering<00:20:19.080> effort<00:20:19.480> we 00:20:19.590 --> 00:20:19.600 align:start position:0% some really good engineering effort we 00:20:19.600 --> 00:20:22.669 align:start position:0% some really good engineering effort we can<00:20:19.760> do<00:20:19.880> it<00:20:20.000> in<00:20:20.559> two<00:20:21.559> uh<00:20:21.760> we<00:20:21.880> want<00:20:22.080> to<00:20:22.200> do<00:20:22.360> it<00:20:22.480> in 00:20:22.669 --> 00:20:22.679 align:start position:0% can do it in two uh we want to do it in 00:20:22.679 --> 00:20:25.590 align:start position:0% can do it in two uh we want to do it in one<00:20:23.280> using<00:20:23.640> ZK<00:20:24.200> exactly<00:20:24.640> that<00:20:25.080> and<00:20:25.200> this<00:20:25.320> is<00:20:25.440> a 00:20:25.590 --> 00:20:25.600 align:start position:0% one using ZK exactly that and this is a 00:20:25.600 --> 00:20:27.669 align:start position:0% one using ZK exactly that and this is a prerequisite<00:20:26.200> of<00:20:26.400> Dave<00:20:26.720> so<00:20:26.919> Dave<00:20:27.240> already 00:20:27.669 --> 00:20:27.679 align:start position:0% prerequisite of Dave so Dave already 00:20:27.679 --> 00:20:29.830 align:start position:0% prerequisite of Dave so Dave already assumes<00:20:28.159> that<00:20:28.360> we<00:20:28.720> manage<00:20:28.960> to<00:20:29.120> reduce<00:20:29.520> this<00:20:29.679> to 00:20:29.830 --> 00:20:29.840 align:start position:0% assumes that we manage to reduce this to 00:20:29.840 --> 00:20:32.110 align:start position:0% assumes that we manage to reduce this to one 00:20:32.110 --> 00:20:32.120 align:start position:0% 00:20:32.120 --> 00:20:35.070 align:start position:0% level<00:20:33.120> cool<00:20:33.600> so<00:20:34.080> what<00:20:34.159> happens<00:20:34.440> if<00:20:34.520> you<00:20:34.679> mix 00:20:35.070 --> 00:20:35.080 align:start position:0% level cool so what happens if you mix 00:20:35.080 --> 00:20:36.630 align:start position:0% level cool so what happens if you mix algorithms<00:20:35.679> together<00:20:35.960> would<00:20:36.080> that<00:20:36.240> increase 00:20:36.630 --> 00:20:36.640 align:start position:0% algorithms together would that increase 00:20:36.640 --> 00:20:39.470 align:start position:0% algorithms together would that increase security<00:20:37.240> do<00:20:37.360> you<00:20:37.480> see<00:20:37.679> it<00:20:37.840> working<00:20:38.840> yeah<00:20:39.080> so 00:20:39.470 --> 00:20:39.480 align:start position:0% security do you see it working yeah so 00:20:39.480 --> 00:20:41.750 align:start position:0% security do you see it working yeah so uh<00:20:39.600> there<00:20:39.679> are<00:20:39.799> two<00:20:40.000> ways<00:20:40.159> to<00:20:40.360> mix<00:20:40.799> algorithms 00:20:41.750 --> 00:20:41.760 align:start position:0% uh there are two ways to mix algorithms 00:20:41.760 --> 00:20:44.110 align:start position:0% uh there are two ways to mix algorithms uh<00:20:41.960> one<00:20:42.120> of<00:20:42.280> them<00:20:42.679> is<00:20:43.080> to<00:20:43.280> improve<00:20:43.600> liveness 00:20:44.110 --> 00:20:44.120 align:start position:0% uh one of them is to improve liveness 00:20:44.120 --> 00:20:46.110 align:start position:0% uh one of them is to improve liveness actually<00:20:44.880> so 00:20:46.110 --> 00:20:46.120 align:start position:0% actually so 00:20:46.120 --> 00:20:49.110 align:start position:0% actually so PRT<00:20:47.120> finishes<00:20:47.840> faster<00:20:48.360> if<00:20:48.520> there<00:20:48.640> are<00:20:48.919> very 00:20:49.110 --> 00:20:49.120 align:start position:0% PRT finishes faster if there are very 00:20:49.120 --> 00:20:51.870 align:start position:0% PRT finishes faster if there are very few<00:20:49.400> number<00:20:49.640> of<00:20:49.760> sybl<00:20:50.559> so<00:20:50.760> what<00:20:50.919> we<00:20:51.080> could<00:20:51.280> do 00:20:51.870 --> 00:20:51.880 align:start position:0% few number of sybl so what we could do 00:20:51.880 --> 00:20:54.669 align:start position:0% few number of sybl so what we could do is<00:20:52.039> launch<00:20:52.360> PRT<00:20:53.120> in<00:20:53.320> parallel<00:20:53.760> with<00:20:53.960> Dave<00:20:54.559> if 00:20:54.669 --> 00:20:54.679 align:start position:0% is launch PRT in parallel with Dave if 00:20:54.679 --> 00:20:57.270 align:start position:0% is launch PRT in parallel with Dave if there<00:20:54.799> are<00:20:54.960> no<00:20:55.360> like<00:20:55.600> very<00:20:55.760> few<00:20:55.960> sibl<00:20:56.880> PRT 00:20:57.270 --> 00:20:57.280 align:start position:0% there are no like very few sibl PRT 00:20:57.280 --> 00:20:59.350 align:start position:0% there are no like very few sibl PRT finishes<00:20:57.799> first<00:20:58.720> if<00:20:58.840> there<00:20:58.960> are<00:20:59.039> a<00:20:59.120> lot<00:20:59.280> of 00:20:59.350 --> 00:20:59.360 align:start position:0% finishes first if there are a lot of 00:20:59.360 --> 00:21:02.390 align:start position:0% finishes first if there are a lot of sibl<00:21:00.320> they<00:21:00.640> finishes<00:21:01.120> first<00:21:01.720> so<00:21:01.919> then<00:21:02.039> we<00:21:02.200> take 00:21:02.390 --> 00:21:02.400 align:start position:0% sibl they finishes first so then we take 00:21:02.400 --> 00:21:04.070 align:start position:0% sibl they finishes first so then we take whoever<00:21:02.799> answers<00:21:03.240> first<00:21:03.520> so<00:21:03.679> this<00:21:03.799> is<00:21:03.880> an 00:21:04.070 --> 00:21:04.080 align:start position:0% whoever answers first so this is an 00:21:04.080 --> 00:21:07.310 align:start position:0% whoever answers first so this is an approach<00:21:04.960> to<00:21:05.240> improve<00:21:05.760> on<00:21:06.120> liveness<00:21:06.919> now<00:21:07.159> to 00:21:07.310 --> 00:21:07.320 align:start position:0% approach to improve on liveness now to 00:21:07.320 --> 00:21:10.310 align:start position:0% approach to improve on liveness now to improve<00:21:07.640> on<00:21:07.880> security<00:21:08.720> we<00:21:08.880> can<00:21:09.080> also<00:21:09.320> mix<00:21:09.640> them 00:21:10.310 --> 00:21:10.320 align:start position:0% improve on security we can also mix them 00:21:10.320 --> 00:21:13.669 align:start position:0% improve on security we can also mix them with<00:21:10.520> the<00:21:11.120> goal<00:21:12.120> of<00:21:12.720> uh<00:21:12.840> you<00:21:12.919> know<00:21:13.159> reducing 00:21:13.669 --> 00:21:13.679 align:start position:0% with the goal of uh you know reducing 00:21:13.679 --> 00:21:17.070 align:start position:0% with the goal of uh you know reducing the<00:21:13.880> risk<00:21:14.240> of<00:21:14.559> bug<00:21:15.400> so<00:21:15.600> we<00:21:15.760> could<00:21:16.000> have<00:21:16.279> like<00:21:16.520> a 00:21:17.070 --> 00:21:17.080 align:start position:0% the risk of bug so we could have like a 00:21:17.080 --> 00:21:20.789 align:start position:0% the risk of bug so we could have like a a<00:21:17.400> Consortium<00:21:18.400> like<00:21:18.640> a<00:21:19.159> quorum<00:21:20.159> of<00:21:20.480> four 00:21:20.789 --> 00:21:20.799 align:start position:0% a Consortium like a quorum of four 00:21:20.799 --> 00:21:23.950 align:start position:0% a Consortium like a quorum of four members<00:21:21.640> one<00:21:21.880> member<00:21:22.200> could<00:21:22.400> be<00:21:22.640> PRT<00:21:23.600> but 00:21:23.950 --> 00:21:23.960 align:start position:0% members one member could be PRT but 00:21:23.960 --> 00:21:26.750 align:start position:0% members one member could be PRT but permissioned<00:21:24.960> so<00:21:25.240> permissioned<00:21:25.840> PRT<00:21:26.400> has<00:21:26.559> no 00:21:26.750 --> 00:21:26.760 align:start position:0% permissioned so permissioned PRT has no 00:21:26.760 --> 00:21:28.590 align:start position:0% permissioned so permissioned PRT has no problems<00:21:27.120> of<00:21:27.279> liveness<00:21:27.679> so<00:21:27.799> we<00:21:27.919> could<00:21:28.120> have 00:21:28.590 --> 00:21:28.600 align:start position:0% problems of liveness so we could have 00:21:28.600 --> 00:21:30.669 align:start position:0% problems of liveness so we could have that<00:21:28.799> one<00:21:28.919> of<00:21:29.039> the<00:21:29.120> members<00:21:29.440> in<00:21:29.559> the<00:21:29.679> Forum 00:21:30.669 --> 00:21:30.679 align:start position:0% that one of the members in the Forum 00:21:30.679 --> 00:21:32.110 align:start position:0% that one of the members in the Forum then<00:21:30.880> we<00:21:31.000> could<00:21:31.200> have<00:21:31.400> Dave<00:21:31.679> as<00:21:31.840> another 00:21:32.110 --> 00:21:32.120 align:start position:0% then we could have Dave as another 00:21:32.120 --> 00:21:34.390 align:start position:0% then we could have Dave as another member<00:21:32.360> in<00:21:32.480> the<00:21:32.600> Forum<00:21:33.559> then<00:21:33.720> we<00:21:33.840> could<00:21:34.039> have<00:21:34.320> I 00:21:34.390 --> 00:21:34.400 align:start position:0% member in the Forum then we could have I 00:21:34.400 --> 00:21:38.269 align:start position:0% member in the Forum then we could have I don't<00:21:34.600> know<00:21:35.159> a<00:21:35.400> te<00:21:36.279> or<00:21:36.679> a<00:21:36.840> quarum<00:21:37.240> of<00:21:37.440> T<00:21:38.159> and 00:21:38.269 --> 00:21:38.279 align:start position:0% don't know a te or a quarum of T and 00:21:38.279 --> 00:21:40.350 align:start position:0% don't know a te or a quarum of T and then<00:21:38.400> we<00:21:38.480> could<00:21:38.640> have<00:21:38.840> a<00:21:39.000> a<00:21:39.120> multisig<00:21:39.799> you<00:21:39.919> know 00:21:40.350 --> 00:21:40.360 align:start position:0% then we could have a a multisig you know 00:21:40.360 --> 00:21:42.789 align:start position:0% then we could have a a multisig you know so<00:21:40.600> if<00:21:40.720> we<00:21:40.880> have<00:21:41.039> this<00:21:41.200> Quorum<00:21:41.640> of<00:21:41.799> like 00:21:42.789 --> 00:21:42.799 align:start position:0% so if we have this Quorum of like 00:21:42.799 --> 00:21:46.950 align:start position:0% so if we have this Quorum of like many<00:21:44.159> um<00:21:45.159> you<00:21:45.279> know<00:21:45.600> it<00:21:45.799> it<00:21:45.919> would<00:21:46.200> take<00:21:46.679> a<00:21:46.799> lot 00:21:46.950 --> 00:21:46.960 align:start position:0% many um you know it it would take a lot 00:21:46.960 --> 00:21:48.830 align:start position:0% many um you know it it would take a lot of<00:21:47.159> effort<00:21:47.480> to<00:21:47.640> try<00:21:47.840> to<00:21:48.000> corrupt<00:21:48.360> all<00:21:48.480> of<00:21:48.640> them 00:21:48.830 --> 00:21:48.840 align:start position:0% of effort to try to corrupt all of them 00:21:48.840 --> 00:21:51.510 align:start position:0% of effort to try to corrupt all of them at<00:21:48.960> the<00:21:49.080> same<00:21:49.320> time<00:21:49.520> so<00:21:49.679> we<00:21:49.880> reduce<00:21:50.240> the<00:21:50.520> risk 00:21:51.510 --> 00:21:51.520 align:start position:0% at the same time so we reduce the risk 00:21:51.520 --> 00:21:53.029 align:start position:0% at the same time so we reduce the risk uh<00:21:51.679> by<00:21:51.919> reducing<00:21:52.360> you<00:21:52.440> know<00:21:52.600> the<00:21:52.720> chance<00:21:52.919> of 00:21:53.029 --> 00:21:53.039 align:start position:0% uh by reducing you know the chance of 00:21:53.039 --> 00:21:54.909 align:start position:0% uh by reducing you know the chance of there<00:21:53.200> being<00:21:53.400> a<00:21:53.559> bug<00:21:54.240> so<00:21:54.480> that's<00:21:54.679> how<00:21:54.799> you 00:21:54.909 --> 00:21:54.919 align:start position:0% there being a bug so that's how you 00:21:54.919 --> 00:21:56.350 align:start position:0% there being a bug so that's how you could<00:21:55.080> mix 00:21:56.350 --> 00:21:56.360 align:start position:0% could mix 00:21:56.360 --> 00:21:59.950 align:start position:0% could mix protocols<00:21:57.360> cool<00:21:58.080> so<00:21:58.679> um<00:21:59.000> what<00:21:59.159> if<00:21:59.400> the<00:21:59.559> goal<00:21:59.799> is 00:21:59.950 --> 00:21:59.960 align:start position:0% protocols cool so um what if the goal is 00:21:59.960 --> 00:22:02.350 align:start position:0% protocols cool so um what if the goal is not<00:22:00.200> to<00:22:01.159> disrupt<00:22:01.559> the<00:22:01.679> chain<00:22:01.919> but<00:22:02.080> just<00:22:02.200> to 00:22:02.350 --> 00:22:02.360 align:start position:0% not to disrupt the chain but just to 00:22:02.360 --> 00:22:04.590 align:start position:0% not to disrupt the chain but just to delay<00:22:02.679> the<00:22:02.799> chain<00:22:03.200> yeah<00:22:03.480> how<00:22:04.080> large<00:22:04.320> would<00:22:04.480> the 00:22:04.590 --> 00:22:04.600 align:start position:0% delay the chain yeah how large would the 00:22:04.600 --> 00:22:06.070 align:start position:0% delay the chain yeah how large would the cost<00:22:04.799> be<00:22:04.919> if<00:22:05.000> the<00:22:05.120> attack<00:22:05.400> presuming<00:22:05.760> the<00:22:05.880> only 00:22:06.070 --> 00:22:06.080 align:start position:0% cost be if the attack presuming the only 00:22:06.080 --> 00:22:08.750 align:start position:0% cost be if the attack presuming the only goal<00:22:06.279> is<00:22:06.400> to<00:22:06.600> delay<00:22:06.960> by<00:22:07.120> four<00:22:07.400> weeks<00:22:08.200> so<00:22:08.559> if<00:22:08.640> you 00:22:08.750 --> 00:22:08.760 align:start position:0% goal is to delay by four weeks so if you 00:22:08.760 --> 00:22:11.110 align:start position:0% goal is to delay by four weeks so if you want<00:22:08.919> to<00:22:09.080> delay<00:22:09.440> by<00:22:09.640> four<00:22:09.919> weeks<00:22:10.480> I<00:22:10.640> think<00:22:10.880> you 00:22:11.110 --> 00:22:11.120 align:start position:0% want to delay by four weeks I think you 00:22:11.120 --> 00:22:13.149 align:start position:0% want to delay by four weeks I think you need<00:22:11.559> more<00:22:11.760> than10<00:22:12.159> billion<00:22:12.760> or<00:22:12.919> something 00:22:13.149 --> 00:22:13.159 align:start position:0% need more than10 billion or something 00:22:13.159 --> 00:22:14.710 align:start position:0% need more than10 billion or something you<00:22:13.240> know<00:22:13.360> we<00:22:13.440> have<00:22:13.559> to<00:22:13.679> burn<00:22:13.919> the<00:22:14.080> GDP<00:22:14.559> of 00:22:14.710 --> 00:22:14.720 align:start position:0% you know we have to burn the GDP of 00:22:14.720 --> 00:22:17.230 align:start position:0% you know we have to burn the GDP of Japan<00:22:15.320> it's<00:22:15.520> crazy<00:22:15.919> you<00:22:16.039> know<00:22:16.520> we<00:22:16.960> sometimes 00:22:17.230 --> 00:22:17.240 align:start position:0% Japan it's crazy you know we sometimes 00:22:17.240 --> 00:22:20.590 align:start position:0% Japan it's crazy you know we sometimes lose<00:22:17.880> sight<00:22:18.880> of<00:22:19.200> like<00:22:19.520> exponential<00:22:20.320> or 00:22:20.590 --> 00:22:20.600 align:start position:0% lose sight of like exponential or 00:22:20.600 --> 00:22:23.830 align:start position:0% lose sight of like exponential or logarithmic<00:22:21.600> uh<00:22:22.559> so<00:22:23.039> really<00:22:23.279> if<00:22:23.360> you<00:22:23.520> burn 00:22:23.830 --> 00:22:23.840 align:start position:0% logarithmic uh so really if you burn 00:22:23.840 --> 00:22:25.510 align:start position:0% logarithmic uh so really if you burn like<00:22:24.000> trillions<00:22:24.440> you<00:22:24.559> can't<00:22:24.760> even<00:22:25.159> fit<00:22:25.400> that 00:22:25.510 --> 00:22:25.520 align:start position:0% like trillions you can't even fit that 00:22:25.520 --> 00:22:27.950 align:start position:0% like trillions you can't even fit that on<00:22:25.640> the<00:22:25.760> blockchain<00:22:26.720> then<00:22:27.000> you<00:22:27.440> you<00:22:27.640> couldn't 00:22:27.950 --> 00:22:27.960 align:start position:0% on the blockchain then you you couldn't 00:22:27.960 --> 00:22:32.630 align:start position:0% on the blockchain then you you couldn't really<00:22:28.200> push<00:22:28.720> pass<00:22:29.000> like<00:22:29.159> this<00:22:29.360> four<00:22:29.520> or<00:22:29.720> five 00:22:32.630 --> 00:22:32.640 align:start position:0% 00:22:32.640 --> 00:22:37.269 align:start position:0% weeks<00:22:33.640> uh<00:22:33.760> the<00:22:33.919> next<00:22:34.159> one<00:22:35.159> ASM<00:22:35.520> totically<00:22:36.279> is 00:22:37.269 --> 00:22:37.279 align:start position:0% weeks uh the next one ASM totically is 00:22:37.279 --> 00:22:39.470 align:start position:0% weeks uh the next one ASM totically is um<00:22:37.880> is<00:22:37.960> it<00:22:38.159> still<00:22:38.400> logarith<00:22:38.799> Matic<00:22:39.039> delay 00:22:39.470 --> 00:22:39.480 align:start position:0% um is it still logarith Matic delay 00:22:39.480 --> 00:22:41.430 align:start position:0% um is it still logarith Matic delay right<00:22:39.880> yeah<00:22:40.080> exactly<00:22:40.679> what<00:22:40.799> we<00:22:40.960> did<00:22:41.120> is<00:22:41.279> we 00:22:41.430 --> 00:22:41.440 align:start position:0% right yeah exactly what we did is we 00:22:41.440 --> 00:22:43.750 align:start position:0% right yeah exactly what we did is we reduced<00:22:41.880> the<00:22:42.080> constant<00:22:42.440> multiplying<00:22:43.080> it<00:22:43.320> by 00:22:43.750 --> 00:22:43.760 align:start position:0% reduced the constant multiplying it by 00:22:43.760 --> 00:22:46.110 align:start position:0% reduced the constant multiplying it by about<00:22:44.039> one<00:22:44.240> order<00:22:44.520> of 00:22:46.110 --> 00:22:46.120 align:start position:0% about one order of 00:22:46.120 --> 00:22:48.630 align:start position:0% about one order of magnitude<00:22:47.120> okay<00:22:47.960> um<00:22:48.080> you<00:22:48.200> have<00:22:48.320> multiple 00:22:48.630 --> 00:22:48.640 align:start position:0% magnitude okay um you have multiple 00:22:48.640 --> 00:22:50.269 align:start position:0% magnitude okay um you have multiple Willies<00:22:48.960> that<00:22:49.039> are<00:22:49.240> good<00:22:49.480> but<00:22:49.600> then<00:22:49.720> I<00:22:49.919> decide 00:22:50.269 --> 00:22:50.279 align:start position:0% Willies that are good but then I decide 00:22:50.279 --> 00:22:54.990 align:start position:0% Willies that are good but then I decide to<00:22:50.520> go<00:22:51.080> bad<00:22:51.960> they<00:22:52.159> can't<00:22:52.760> because<00:22:53.840> um<00:22:54.840> they 00:22:54.990 --> 00:22:55.000 align:start position:0% to go bad they can't because um they 00:22:55.000 --> 00:22:56.990 align:start position:0% to go bad they can't because um they when<00:22:55.159> they<00:22:55.279> do<00:22:55.400> a<00:22:55.559> bisection<00:22:56.360> they<00:22:56.520> need<00:22:56.799> to 00:22:56.990 --> 00:22:57.000 align:start position:0% when they do a bisection they need to 00:22:57.000 --> 00:22:58.830 align:start position:0% when they do a bisection they need to provide<00:22:57.240> the<00:22:57.360> merco<00:22:57.760> proof<00:22:58.039> and<00:22:58.120> the<00:22:58.200> proof 00:22:58.830 --> 00:22:58.840 align:start position:0% provide the merco proof and the proof 00:22:58.840 --> 00:23:01.830 align:start position:0% provide the merco proof and the proof w't<00:22:59.279> won't<00:22:59.880> just<00:23:00.120> match<00:23:00.679> yeah<00:23:01.080> will<00:23:01.400> just<00:23:01.559> not 00:23:01.830 --> 00:23:01.840 align:start position:0% w't won't just match yeah will just not 00:23:01.840 --> 00:23:04.269 align:start position:0% w't won't just match yeah will just not match<00:23:02.760> cool<00:23:03.080> all<00:23:03.200> right<00:23:03.600> everyone<00:23:03.960> clap<00:23:04.200> your 00:23:04.269 --> 00:23:04.279 align:start position:0% match cool all right everyone clap your 00:23:04.279 --> 00:23:05.870 align:start position:0% match cool all right everyone clap your hands<00:23:04.480> for<00:23:04.640> Gabriel<00:23:05.000> and<00:23:05.120> thank<00:23:05.279> him<00:23:05.400> for<00:23:05.640> his 00:23:05.870 --> 00:23:05.880 align:start position:0% hands for Gabriel and thank him for his 00:23:05.880 --> 00:23:07.190 align:start position:0% hands for Gabriel and thank him for his time<00:23:06.039> he<00:23:06.159> spent 00:23:07.190 --> 00:23:07.200 align:start position:0% time he spent 00:23:07.200 --> 00:23:13.080 align:start position:0% time he spent on<00:23:08.200> the<00:23:08.400> next<00:23:08.720> session<00:23:09.159> will<00:23:09.400> be<00:23:09.760> at<00:23:10.080> 11:30