WEBVTT
Kind: captions
Language: en

00:00:04.380 --> 00:00:07.610 align:start position:0%
 
hello<00:00:05.220><c> my</c><00:00:05.759><c> name</c><00:00:05.910><c> is</c><00:00:05.939><c> Mikael</c><00:00:06.479><c> Kalinin</c><00:00:06.960><c> I'm</c><00:00:07.290><c> from</c>

00:00:07.610 --> 00:00:07.620 align:start position:0%
hello my name is Mikael Kalinin I'm from
 

00:00:07.620 --> 00:00:10.699 align:start position:0%
hello my name is Mikael Kalinin I'm from
harmony<00:00:08.040><c> team</c><00:00:08.450><c> first</c><00:00:09.450><c> of</c><00:00:09.600><c> all</c><00:00:09.780><c> I'd</c><00:00:10.170><c> like</c><00:00:10.410><c> to</c>

00:00:10.699 --> 00:00:10.709 align:start position:0%
harmony team first of all I'd like to
 

00:00:10.709 --> 00:00:13.220 align:start position:0%
harmony team first of all I'd like to
credit<00:00:11.160><c> alex</c><00:00:11.940><c> philosoph</c><00:00:12.449><c> who</c><00:00:12.750><c> has</c><00:00:12.990><c> been</c>

00:00:13.220 --> 00:00:13.230 align:start position:0%
credit alex philosoph who has been
 

00:00:13.230 --> 00:00:15.740 align:start position:0%
credit alex philosoph who has been
investigating<00:00:13.590><c> in</c><00:00:14.250><c> these</c><00:00:14.670><c> complexities</c><00:00:15.059><c> in</c>

00:00:15.740 --> 00:00:15.750 align:start position:0%
investigating in these complexities in
 

00:00:15.750 --> 00:00:22.280 align:start position:0%
investigating in these complexities in
aggregation<00:00:17.270><c> ok</c><00:00:18.270><c> let's</c><00:00:18.960><c> move</c><00:00:19.109><c> on</c><00:00:19.820><c> so</c><00:00:21.050><c> here</c><00:00:22.050><c> is</c>

00:00:22.280 --> 00:00:22.290 align:start position:0%
aggregation ok let's move on so here is
 

00:00:22.290 --> 00:00:28.640 align:start position:0%
aggregation ok let's move on so here is
the<00:00:24.500><c> we</c><00:00:25.500><c> have</c><00:00:25.650><c> a</c><00:00:26.630><c> station</c><00:00:27.630><c> votes</c><00:00:27.840><c> you</c><00:00:28.590><c> are</c>

00:00:28.640 --> 00:00:28.650 align:start position:0%
the we have a station votes you are
 

00:00:28.650 --> 00:00:32.359 align:start position:0%
the we have a station votes you are
already<00:00:29.369><c> familiar</c><00:00:29.670><c> with</c><00:00:30.030><c> them</c><00:00:31.369><c> from</c>

00:00:32.359 --> 00:00:32.369 align:start position:0%
already familiar with them from
 

00:00:32.369 --> 00:00:35.180 align:start position:0%
already familiar with them from
yesterday's<00:00:33.270><c> talks</c><00:00:33.600><c> about</c><00:00:34.170><c> beacon</c><00:00:34.949><c> chain</c>

00:00:35.180 --> 00:00:35.190 align:start position:0%
yesterday's talks about beacon chain
 

00:00:35.190 --> 00:00:39.739 align:start position:0%
yesterday's talks about beacon chain
technical<00:00:36.679><c> introduction</c><00:00:37.679><c> so</c><00:00:38.429><c> we</c><00:00:38.699><c> have</c><00:00:38.879><c> cross</c>

00:00:39.739 --> 00:00:39.749 align:start position:0%
technical introduction so we have cross
 

00:00:39.749 --> 00:00:41.090 align:start position:0%
technical introduction so we have cross
links<00:00:40.260><c> to</c><00:00:40.469><c> charts</c>

00:00:41.090 --> 00:00:41.100 align:start position:0%
links to charts
 

00:00:41.100 --> 00:00:44.360 align:start position:0%
links to charts
we<00:00:41.730><c> have</c><00:00:41.969><c> finality</c><00:00:42.949><c> checkpoints</c><00:00:43.949><c> and</c><00:00:44.069><c> we</c><00:00:44.219><c> have</c>

00:00:44.360 --> 00:00:44.370 align:start position:0%
we have finality checkpoints and we have
 

00:00:44.370 --> 00:00:47.959 align:start position:0%
we have finality checkpoints and we have
a<00:00:44.399><c> fork</c><00:00:44.879><c> choice</c><00:00:45.149><c> vote</c><00:00:45.809><c> as</c><00:00:46.109><c> well</c><00:00:46.530><c> so</c><00:00:47.460><c> the</c>

00:00:47.959 --> 00:00:47.969 align:start position:0%
a fork choice vote as well so the
 

00:00:47.969 --> 00:00:51.860 align:start position:0%
a fork choice vote as well so the
attestation<00:00:48.899><c> is</c><00:00:49.589><c> a</c><00:00:50.179><c> very</c><00:00:51.179><c> important</c><00:00:51.659><c> thing</c>

00:00:51.860 --> 00:00:51.870 align:start position:0%
attestation is a very important thing
 

00:00:51.870 --> 00:00:54.619 align:start position:0%
attestation is a very important thing
for<00:00:51.929><c> the</c><00:00:52.260><c> big</c><00:00:52.409><c> and</c><00:00:52.559><c> chain</c><00:00:52.800><c> this</c><00:00:53.550><c> is</c><00:00:53.789><c> how</c><00:00:53.999><c> we</c><00:00:54.479><c> can</c>

00:00:54.619 --> 00:00:54.629 align:start position:0%
for the big and chain this is how we can
 

00:00:54.629 --> 00:00:57.919 align:start position:0%
for the big and chain this is how we can
chain<00:00:54.870><c> makes</c><00:00:55.109><c> the</c><00:00:55.559><c> consensus</c><00:00:56.190><c> happen</c><00:00:56.929><c> let's</c>

00:00:57.919 --> 00:00:57.929 align:start position:0%
chain makes the consensus happen let's
 

00:00:57.929 --> 00:01:01.599 align:start position:0%
chain makes the consensus happen let's
see<00:00:58.079><c> how</c><00:00:58.350><c> it's</c><00:00:58.850><c> progressing</c><00:00:59.850><c> through</c><00:01:00.539><c> a</c><00:01:00.899><c> slot</c>

00:01:01.599 --> 00:01:01.609 align:start position:0%
see how it's progressing through a slot
 

00:01:01.609 --> 00:01:04.280 align:start position:0%
see how it's progressing through a slot
so<00:01:02.609><c> at</c><00:01:02.909><c> the</c><00:01:03.030><c> beginning</c><00:01:03.359><c> of</c><00:01:03.449><c> the</c><00:01:03.629><c> slot</c><00:01:03.899><c> a</c>

00:01:04.280 --> 00:01:04.290 align:start position:0%
so at the beginning of the slot a
 

00:01:04.290 --> 00:01:08.210 align:start position:0%
so at the beginning of the slot a
proposer<00:01:05.360><c> produces</c><00:01:06.360><c> a</c><00:01:06.390><c> block</c><00:01:06.690><c> and</c><00:01:07.040><c> send</c><00:01:08.040><c> it</c><00:01:08.190><c> to</c>

00:01:08.210 --> 00:01:08.220 align:start position:0%
proposer produces a block and send it to
 

00:01:08.220 --> 00:01:12.889 align:start position:0%
proposer produces a block and send it to
the<00:01:08.520><c> wire</c><00:01:09.289><c> so</c><00:01:10.289><c> all</c><00:01:10.950><c> the</c><00:01:11.340><c> daters</c><00:01:11.670><c> can</c><00:01:12.539><c> receive</c>

00:01:12.889 --> 00:01:12.899 align:start position:0%
the wire so all the daters can receive
 

00:01:12.899 --> 00:01:16.490 align:start position:0%
the wire so all the daters can receive
it<00:01:12.990><c> through</c><00:01:13.140><c> the</c><00:01:13.320><c> wire</c><00:01:14.539><c> in</c><00:01:15.539><c> the</c><00:01:15.840><c> middle</c><00:01:15.990><c> of</c><00:01:16.350><c> the</c>

00:01:16.490 --> 00:01:16.500 align:start position:0%
it through the wire in the middle of the
 

00:01:16.500 --> 00:01:19.459 align:start position:0%
it through the wire in the middle of the
slot<00:01:16.799><c> committees</c><00:01:17.670><c> start</c><00:01:18.570><c> to</c><00:01:18.719><c> produce</c><00:01:18.930><c> their</c>

00:01:19.459 --> 00:01:19.469 align:start position:0%
slot committees start to produce their
 

00:01:19.469 --> 00:01:22.999 align:start position:0%
slot committees start to produce their
other<00:01:19.770><c> stations</c><00:01:20.990><c> basically</c><00:01:21.990><c> this</c><00:01:22.530><c> could</c>

00:01:22.999 --> 00:01:23.009 align:start position:0%
other stations basically this could
 

00:01:23.009 --> 00:01:26.359 align:start position:0%
other stations basically this could
happen<00:01:23.250><c> not</c><00:01:23.820><c> in</c><00:01:24.180><c> the</c><00:01:24.390><c> middle</c><00:01:24.659><c> of</c><00:01:24.780><c> the</c><00:01:24.899><c> slot</c><00:01:25.369><c> one</c>

00:01:26.359 --> 00:01:26.369 align:start position:0%
happen not in the middle of the slot one
 

00:01:26.369 --> 00:01:28.219 align:start position:0%
happen not in the middle of the slot one
may<00:01:26.579><c> produce</c><00:01:26.939><c> at</c><00:01:27.299><c> the</c><00:01:27.329><c> station</c><00:01:27.780><c> upon</c><00:01:28.140><c> the</c>

00:01:28.219 --> 00:01:28.229 align:start position:0%
may produce at the station upon the
 

00:01:28.229 --> 00:01:30.170 align:start position:0%
may produce at the station upon the
receive<00:01:28.560><c> in</c><00:01:28.680><c> this</c><00:01:28.859><c> block</c><00:01:29.100><c> and</c><00:01:29.310><c> important</c><00:01:29.969><c> this</c>

00:01:30.170 --> 00:01:30.180 align:start position:0%
receive in this block and important this
 

00:01:30.180 --> 00:01:37.010 align:start position:0%
receive in this block and important this
to<00:01:30.539><c> its</c><00:01:30.810><c> chain</c><00:01:31.820><c> after</c><00:01:32.820><c> that</c><00:01:33.560><c> a</c><00:01:35.329><c> testers</c><00:01:36.329><c> should</c>

00:01:37.010 --> 00:01:37.020 align:start position:0%
to its chain after that a testers should
 

00:01:37.020 --> 00:01:40.130 align:start position:0%
to its chain after that a testers should
deliver<00:01:37.799><c> their</c><00:01:38.729><c> added</c><00:01:39.179><c> stations</c><00:01:39.630><c> to</c><00:01:39.869><c> the</c>

00:01:40.130 --> 00:01:40.140 align:start position:0%
deliver their added stations to the
 

00:01:40.140 --> 00:01:42.529 align:start position:0%
deliver their added stations to the
proposer<00:01:40.530><c> of</c><00:01:40.799><c> the</c><00:01:40.979><c> next</c><00:01:41.280><c> block</c><00:01:41.429><c> to</c><00:01:42.359><c> be</c>

00:01:42.529 --> 00:01:42.539 align:start position:0%
proposer of the next block to be
 

00:01:42.539 --> 00:01:44.870 align:start position:0%
proposer of the next block to be
included<00:01:42.990><c> on</c><00:01:43.109><c> chain</c><00:01:43.409><c> and</c><00:01:43.649><c> they</c><00:01:44.130><c> are</c><00:01:44.280><c> eager</c><00:01:44.549><c> to</c>

00:01:44.870 --> 00:01:44.880 align:start position:0%
included on chain and they are eager to
 

00:01:44.880 --> 00:01:49.550 align:start position:0%
included on chain and they are eager to
do<00:01:45.030><c> this</c><00:01:45.210><c> because</c><00:01:45.659><c> their</c><00:01:47.420><c> rewards</c><00:01:48.420><c> depend</c><00:01:49.380><c> on</c>

00:01:49.550 --> 00:01:49.560 align:start position:0%
do this because their rewards depend on
 

00:01:49.560 --> 00:01:53.539 align:start position:0%
do this because their rewards depend on
that<00:01:49.770><c> and</c><00:01:50.539><c> if</c><00:01:51.539><c> proposer</c><00:01:52.499><c> of</c><00:01:52.740><c> next</c><00:01:53.070><c> slot</c><00:01:53.249><c> for</c>

00:01:53.539 --> 00:01:53.549 align:start position:0%
that and if proposer of next slot for
 

00:01:53.549 --> 00:01:55.550 align:start position:0%
that and if proposer of next slot for
some<00:01:53.729><c> reason</c><00:01:54.060><c> fails</c><00:01:54.359><c> to</c><00:01:54.749><c> include</c><00:01:55.020><c> some</c><00:01:55.530><c> of</c>

00:01:55.550 --> 00:01:55.560 align:start position:0%
some reason fails to include some of
 

00:01:55.560 --> 00:02:00.080 align:start position:0%
some reason fails to include some of
those<00:01:55.890><c> SATA</c><00:01:56.189><c> stations</c><00:01:57.799><c> each</c><00:01:58.850><c> those</c><00:01:59.850><c> at</c><00:02:00.030><c> the</c>

00:02:00.080 --> 00:02:00.090 align:start position:0%
those SATA stations each those at the
 

00:02:00.090 --> 00:02:02.480 align:start position:0%
those SATA stations each those at the
station<00:02:00.479><c> should</c><00:02:00.719><c> be</c><00:02:00.929><c> delivered</c><00:02:01.890><c> to</c><00:02:02.100><c> proposer</c>

00:02:02.480 --> 00:02:02.490 align:start position:0%
station should be delivered to proposer
 

00:02:02.490 --> 00:02:05.389 align:start position:0%
station should be delivered to proposer
of<00:02:02.850><c> this</c><00:02:03.090><c> lot</c><00:02:03.299><c> of</c><00:02:03.479><c> after</c><00:02:04.259><c> the</c><00:02:04.380><c> next</c><00:02:04.649><c> one</c><00:02:04.859><c> and</c><00:02:05.100><c> so</c>

00:02:05.389 --> 00:02:05.399 align:start position:0%
of this lot of after the next one and so
 

00:02:05.399 --> 00:02:12.170 align:start position:0%
of this lot of after the next one and so
forth<00:02:05.729><c> up</c><00:02:06.090><c> to</c><00:02:06.740><c> 64</c><00:02:07.740><c> slots</c><00:02:08.069><c> ahead</c><00:02:10.550><c> okay</c><00:02:11.550><c> so</c><00:02:11.610><c> what</c>

00:02:12.170 --> 00:02:12.180 align:start position:0%
forth up to 64 slots ahead okay so what
 

00:02:12.180 --> 00:02:15.380 align:start position:0%
forth up to 64 slots ahead okay so what
proposer<00:02:12.780><c> does</c><00:02:13.440><c> with</c><00:02:13.830><c> those</c><00:02:14.070><c> stations</c><00:02:14.970><c> it</c>

00:02:15.380 --> 00:02:15.390 align:start position:0%
proposer does with those stations it
 

00:02:15.390 --> 00:02:17.570 align:start position:0%
proposer does with those stations it
aggregates<00:02:16.050><c> them</c>

00:02:17.570 --> 00:02:17.580 align:start position:0%
aggregates them
 

00:02:17.580 --> 00:02:21.070 align:start position:0%
aggregates them
and<00:02:17.960><c> includes</c><00:02:18.960><c> them</c><00:02:19.320><c> into</c><00:02:19.830><c> a</c><00:02:19.860><c> blog</c><00:02:20.160><c> body</c>

00:02:21.070 --> 00:02:21.080 align:start position:0%
and includes them into a blog body
 

00:02:21.080 --> 00:02:23.480 align:start position:0%
and includes them into a blog body
aggregation<00:02:22.080><c> reduces</c><00:02:22.740><c> verification</c>

00:02:23.480 --> 00:02:23.490 align:start position:0%
aggregation reduces verification
 

00:02:23.490 --> 00:02:28.330 align:start position:0%
aggregation reduces verification
complexity<00:02:24.240><c> and</c><00:02:25.280><c> it</c><00:02:26.280><c> means</c><00:02:26.550><c> that</c><00:02:26.940><c> instead</c><00:02:27.450><c> of</c>

00:02:28.330 --> 00:02:28.340 align:start position:0%
complexity and it means that instead of
 

00:02:28.340 --> 00:02:33.110 align:start position:0%
complexity and it means that instead of
verifying<00:02:29.780><c> hundreds</c><00:02:30.780><c> of</c><00:02:30.930><c> signatures</c><00:02:32.120><c> you</c>

00:02:33.110 --> 00:02:33.120 align:start position:0%
verifying hundreds of signatures you
 

00:02:33.120 --> 00:02:35.600 align:start position:0%
verifying hundreds of signatures you
should<00:02:33.690><c> in</c><00:02:33.990><c> the</c><00:02:34.530><c> best</c><00:02:34.710><c> case</c><00:02:35.010><c> you</c><00:02:35.400><c> should</c>

00:02:35.600 --> 00:02:35.610 align:start position:0%
should in the best case you should
 

00:02:35.610 --> 00:02:38.930 align:start position:0%
should in the best case you should
verify<00:02:36.080><c> only</c><00:02:37.080><c> one</c><00:02:37.650><c> signature</c><00:02:38.130><c> pin</c><00:02:38.550><c> very</c>

00:02:38.930 --> 00:02:38.940 align:start position:0%
verify only one signature pin very
 

00:02:38.940 --> 00:02:42.800 align:start position:0%
verify only one signature pin very
common<00:02:39.390><c> T</c><00:02:39.510><c> it</c><00:02:40.350><c> also</c><00:02:40.560><c> reduces</c><00:02:41.190><c> size</c><00:02:41.670><c> demand</c><00:02:42.450><c> on</c>

00:02:42.800 --> 00:02:42.810 align:start position:0%
common T it also reduces size demand on
 

00:02:42.810 --> 00:02:45.790 align:start position:0%
common T it also reduces size demand on
the<00:02:43.530><c> blog</c><00:02:43.800><c> body</c>

00:02:45.790 --> 00:02:45.800 align:start position:0%
the blog body
 

00:02:45.800 --> 00:02:51.080 align:start position:0%
the blog body
this<00:02:46.800><c> chart</c><00:02:47.190><c> shows</c><00:02:47.720><c> e</c><00:02:48.720><c> y</c><00:02:49.680><c> axis</c><00:02:50.280><c> is</c><00:02:50.460><c> megabytes</c>

00:02:51.080 --> 00:02:51.090 align:start position:0%
this chart shows e y axis is megabytes
 

00:02:51.090 --> 00:02:57.290 align:start position:0%
this chart shows e y axis is megabytes
of<00:02:51.300><c> data</c><00:02:51.510><c> and</c><00:02:52.760><c> x</c><00:02:53.900><c> axis</c><00:02:54.900><c> is</c><00:02:55.520><c> million</c><00:02:56.520><c> of</c><00:02:56.670><c> eath</c><00:02:56.940><c> at</c>

00:02:57.290 --> 00:02:57.300 align:start position:0%
of data and x axis is million of eath at
 

00:02:57.300 --> 00:02:58.070 align:start position:0%
of data and x axis is million of eath at
stake

00:02:58.070 --> 00:02:58.080 align:start position:0%
stake
 

00:02:58.080 --> 00:03:02.030 align:start position:0%
stake
so<00:02:58.680><c> this</c><00:02:59.040><c> green</c><00:02:59.670><c> line</c><00:02:59.970><c> is</c><00:03:00.810><c> the</c><00:03:01.410><c> aggregated</c>

00:03:02.030 --> 00:03:02.040 align:start position:0%
so this green line is the aggregated
 

00:03:02.040 --> 00:03:04.699 align:start position:0%
so this green line is the aggregated
case<00:03:02.280><c> and</c><00:03:02.670><c> orange</c><00:03:03.420><c> line</c><00:03:03.660><c> is</c><00:03:03.870><c> not</c><00:03:04.050><c> aggregated</c>

00:03:04.699 --> 00:03:04.709 align:start position:0%
case and orange line is not aggregated
 

00:03:04.709 --> 00:03:07.310 align:start position:0%
case and orange line is not aggregated
case<00:03:04.980><c> and</c><00:03:05.280><c> you</c><00:03:06.060><c> can</c><00:03:06.240><c> see</c><00:03:06.450><c> how</c><00:03:06.690><c> aggregation</c>

00:03:07.310 --> 00:03:07.320 align:start position:0%
case and you can see how aggregation
 

00:03:07.320 --> 00:03:11.360 align:start position:0%
case and you can see how aggregation
saves<00:03:07.590><c> our</c><00:03:07.830><c> lives</c><00:03:08.360><c> so</c><00:03:09.650><c> ok</c><00:03:10.650><c> let's</c><00:03:10.680><c> talk</c><00:03:11.220><c> about</c>

00:03:11.360 --> 00:03:11.370 align:start position:0%
saves our lives so ok let's talk about
 

00:03:11.370 --> 00:03:14.000 align:start position:0%
saves our lives so ok let's talk about
attestation<00:03:12.180><c> delivery</c><00:03:12.870><c> how</c><00:03:13.230><c> to</c><00:03:13.290><c> deliver</c>

00:03:14.000 --> 00:03:14.010 align:start position:0%
attestation delivery how to deliver
 

00:03:14.010 --> 00:03:17.090 align:start position:0%
attestation delivery how to deliver
those<00:03:14.760><c> at</c><00:03:14.970><c> the</c><00:03:15.090><c> stations</c><00:03:15.510><c> to</c><00:03:15.630><c> a</c><00:03:15.660><c> proposer</c><00:03:16.100><c> we</c>

00:03:17.090 --> 00:03:17.100 align:start position:0%
those at the stations to a proposer we
 

00:03:17.100 --> 00:03:20.750 align:start position:0%
those at the stations to a proposer we
might<00:03:17.280><c> probably</c><00:03:17.720><c> do</c><00:03:18.830><c> direct</c><00:03:19.830><c> delivery</c><00:03:19.980><c> just</c>

00:03:20.750 --> 00:03:20.760 align:start position:0%
might probably do direct delivery just
 

00:03:20.760 --> 00:03:24.699 align:start position:0%
might probably do direct delivery just
send<00:03:21.090><c> those</c><00:03:21.680><c> other</c><00:03:22.680><c> stations</c><00:03:23.220><c> directly</c><00:03:23.760><c> to</c>

00:03:24.699 --> 00:03:24.709 align:start position:0%
send those other stations directly to
 

00:03:24.709 --> 00:03:28.370 align:start position:0%
send those other stations directly to
let's<00:03:25.709><c> say</c><00:03:25.920><c> five</c><00:03:26.670><c> or</c><00:03:26.700><c> ten</c><00:03:27.269><c> proposers</c><00:03:27.989><c> of</c><00:03:28.260><c> the</c>

00:03:28.370 --> 00:03:28.380 align:start position:0%
let's say five or ten proposers of the
 

00:03:28.380 --> 00:03:30.440 align:start position:0%
let's say five or ten proposers of the
next<00:03:28.680><c> blocks</c><00:03:28.920><c> whatever</c><00:03:29.400><c> number</c><00:03:29.790><c> we</c><00:03:30.030><c> find</c>

00:03:30.440 --> 00:03:30.450 align:start position:0%
next blocks whatever number we find
 

00:03:30.450 --> 00:03:34.370 align:start position:0%
next blocks whatever number we find
reasonable<00:03:31.430><c> but</c><00:03:32.430><c> this</c><00:03:33.360><c> this</c><00:03:33.720><c> way</c><00:03:33.989><c> is</c><00:03:34.050><c> we're</c>

00:03:34.370 --> 00:03:34.380 align:start position:0%
reasonable but this this way is we're
 

00:03:34.380 --> 00:03:37.880 align:start position:0%
reasonable but this this way is we're
efficient<00:03:35.100><c> and</c><00:03:35.400><c> fast</c><00:03:36.330><c> but</c><00:03:37.170><c> in</c><00:03:37.410><c> that</c><00:03:37.560><c> case</c><00:03:37.830><c> we</c>

00:03:37.880 --> 00:03:37.890 align:start position:0%
efficient and fast but in that case we
 

00:03:37.890 --> 00:03:40.610 align:start position:0%
efficient and fast but in that case we
are<00:03:38.370><c> willing</c><00:03:38.760><c> proposal</c><00:03:39.420><c> rate</c><00:03:39.570><c> the</c><00:03:39.720><c> entity</c><00:03:40.110><c> it</c>

00:03:40.610 --> 00:03:40.620 align:start position:0%
are willing proposal rate the entity it
 

00:03:40.620 --> 00:03:46.160 align:start position:0%
are willing proposal rate the entity it
means<00:03:41.130><c> that</c><00:03:42.019><c> adversary</c><00:03:43.019><c> may</c><00:03:43.200><c> match</c><00:03:45.170><c> proposer</c>

00:03:46.160 --> 00:03:46.170 align:start position:0%
means that adversary may match proposer
 

00:03:46.170 --> 00:03:50.259 align:start position:0%
means that adversary may match proposer
public<00:03:46.920><c> key</c><00:03:47.190><c> and</c><00:03:47.570><c> its</c><00:03:48.570><c> network</c><00:03:48.780><c> ID</c><00:03:49.230><c> and</c>

00:03:50.259 --> 00:03:50.269 align:start position:0%
public key and its network ID and
 

00:03:50.269 --> 00:03:52.820 align:start position:0%
public key and its network ID and
organize<00:03:51.269><c> a</c><00:03:51.300><c> coordinated</c><00:03:52.110><c> attack</c><00:03:52.260><c> to</c><00:03:52.680><c> this</c>

00:03:52.820 --> 00:03:52.830 align:start position:0%
organize a coordinated attack to this
 

00:03:52.830 --> 00:03:55.670 align:start position:0%
organize a coordinated attack to this
particular<00:03:53.430><c> proposal</c><00:03:53.640><c> kick</c><00:03:54.390><c> them</c><00:03:54.630><c> off</c><00:03:54.810><c> of</c><00:03:55.200><c> the</c>

00:03:55.670 --> 00:03:55.680 align:start position:0%
particular proposal kick them off of the
 

00:03:55.680 --> 00:03:58.280 align:start position:0%
particular proposal kick them off of the
network<00:03:56.060><c> so</c><00:03:57.060><c> we're</c><00:03:57.300><c> not</c><00:03:57.510><c> doing</c><00:03:57.959><c> it</c><00:03:58.080><c> that</c><00:03:58.110><c> way</c>

00:03:58.280 --> 00:03:58.290 align:start position:0%
network so we're not doing it that way
 

00:03:58.290 --> 00:04:02.030 align:start position:0%
network so we're not doing it that way
instead<00:03:59.280><c> of</c><00:03:59.340><c> this</c><00:03:59.670><c> we're</c><00:04:00.030><c> using</c><00:04:00.709><c> p2p</c><00:04:01.709><c> overlay</c>

00:04:02.030 --> 00:04:02.040 align:start position:0%
instead of this we're using p2p overlay
 

00:04:02.040 --> 00:04:05.030 align:start position:0%
instead of this we're using p2p overlay
that<00:04:03.000><c> includes</c><00:04:03.480><c> all</c><00:04:03.750><c> other</c><00:04:03.810><c> daters</c><00:04:04.590><c> of</c><00:04:04.800><c> the</c>

00:04:05.030 --> 00:04:05.040 align:start position:0%
that includes all other daters of the
 

00:04:05.040 --> 00:04:07.040 align:start position:0%
that includes all other daters of the
beacon<00:04:05.340><c> chain</c><00:04:05.610><c> and</c><00:04:05.910><c> gossiping</c><00:04:06.870><c> the</c>

00:04:07.040 --> 00:04:07.050 align:start position:0%
beacon chain and gossiping the
 

00:04:07.050 --> 00:04:10.220 align:start position:0%
beacon chain and gossiping the
attestation<00:04:07.320><c> x'</c><00:04:07.769><c> through</c><00:04:08.610><c> this</c><00:04:08.910><c> overlay</c><00:04:09.540><c> so</c>

00:04:10.220 --> 00:04:10.230 align:start position:0%
attestation x' through this overlay so
 

00:04:10.230 --> 00:04:12.890 align:start position:0%
attestation x' through this overlay so
everybody<00:04:10.860><c> is</c><00:04:11.250><c> happy</c><00:04:11.570><c> everybody</c><00:04:12.570><c> all</c>

00:04:12.890 --> 00:04:12.900 align:start position:0%
everybody is happy everybody all
 

00:04:12.900 --> 00:04:13.990 align:start position:0%
everybody is happy everybody all
proposers

00:04:13.990 --> 00:04:14.000 align:start position:0%
proposers
 

00:04:14.000 --> 00:04:16.759 align:start position:0%
proposers
receiving<00:04:15.000><c> those</c><00:04:15.209><c> data</c><00:04:15.480><c> stations</c><00:04:16.260><c> nobody</c>

00:04:16.759 --> 00:04:16.769 align:start position:0%
receiving those data stations nobody
 

00:04:16.769 --> 00:04:19.940 align:start position:0%
receiving those data stations nobody
knows<00:04:17.040><c> who</c><00:04:17.430><c> are</c><00:04:17.609><c> proposers</c><00:04:18.440><c> who</c><00:04:19.440><c> proposers</c>

00:04:19.940 --> 00:04:19.950 align:start position:0%
knows who are proposers who proposers
 

00:04:19.950 --> 00:04:26.960 align:start position:0%
knows who are proposers who proposers
are<00:04:20.160><c> and</c><00:04:21.560><c> these</c><00:04:24.200><c> this</c><00:04:25.200><c> p2p</c><00:04:25.770><c> overlay</c><00:04:25.800><c> is</c><00:04:26.520><c> big</c>

00:04:26.960 --> 00:04:26.970 align:start position:0%
are and these this p2p overlay is big
 

00:04:26.970 --> 00:04:30.320 align:start position:0%
are and these this p2p overlay is big
enough<00:04:27.270><c> and</c><00:04:28.310><c> everybody</c><00:04:29.310><c> knows</c><00:04:29.550><c> that</c><00:04:29.789><c> there</c>

00:04:30.320 --> 00:04:30.330 align:start position:0%
enough and everybody knows that there
 

00:04:30.330 --> 00:04:31.460 align:start position:0%
enough and everybody knows that there
are<00:04:30.479><c> some</c><00:04:30.720><c> valid</c><00:04:30.930><c> errors</c>

00:04:31.460 --> 00:04:31.470 align:start position:0%
are some valid errors
 

00:04:31.470 --> 00:04:37.100 align:start position:0%
are some valid errors
in<00:04:31.530><c> it</c><00:04:31.710><c> but</c><00:04:32.070><c> it's</c><00:04:33.000><c> hard</c><00:04:33.300><c> to</c><00:04:35.480><c> to</c><00:04:36.480><c> organize</c><00:04:36.870><c> an</c>

00:04:37.100 --> 00:04:37.110 align:start position:0%
in it but it's hard to to organize an
 

00:04:37.110 --> 00:04:38.840 align:start position:0%
in it but it's hard to to organize an
attack<00:04:37.200><c> on</c><00:04:37.440><c> this</c><00:04:37.770><c> because</c><00:04:38.250><c> there</c><00:04:38.640><c> are</c><00:04:38.670><c> a</c><00:04:38.760><c> lot</c>

00:04:38.840 --> 00:04:38.850 align:start position:0%
attack on this because there are a lot
 

00:04:38.850 --> 00:04:42.320 align:start position:0%
attack on this because there are a lot
just<00:04:39.180><c> a</c><00:04:39.330><c> lot</c><00:04:39.480><c> of</c><00:04:39.510><c> notes</c><00:04:39.840><c> and</c><00:04:40.140><c> nobody</c><00:04:40.620><c> knows</c><00:04:41.330><c> who</c>

00:04:42.320 --> 00:04:42.330 align:start position:0%
just a lot of notes and nobody knows who
 

00:04:42.330 --> 00:04:44.180 align:start position:0%
just a lot of notes and nobody knows who
is<00:04:42.360><c> the</c><00:04:42.600><c> proposer</c><00:04:42.990><c> of</c><00:04:43.230><c> the</c><00:04:43.380><c> next</c><00:04:43.650><c> lot</c><00:04:43.830><c> or</c><00:04:44.040><c> who</c>

00:04:44.180 --> 00:04:44.190 align:start position:0%
is the proposer of the next lot or who
 

00:04:44.190 --> 00:04:46.310 align:start position:0%
is the proposer of the next lot or who
are<00:04:44.400><c> the</c><00:04:44.700><c> participants</c><00:04:45.210><c> of</c><00:04:45.780><c> the</c><00:04:45.900><c> committee</c>

00:04:46.310 --> 00:04:46.320 align:start position:0%
are the participants of the committee
 

00:04:46.320 --> 00:04:49.280 align:start position:0%
are the participants of the committee
internet<00:04:46.860><c> workers</c><00:04:47.280><c> network</c><00:04:48.290><c> because</c>

00:04:49.280 --> 00:04:49.290 align:start position:0%
internet workers network because
 

00:04:49.290 --> 00:04:53.810 align:start position:0%
internet workers network because
identity<00:04:49.830><c> is</c><00:04:49.980><c> not</c><00:04:50.190><c> reveal</c><00:04:51.440><c> that</c><00:04:52.440><c> gossiping</c><00:04:53.160><c> to</c>

00:04:53.810 --> 00:04:53.820 align:start position:0%
identity is not reveal that gossiping to
 

00:04:53.820 --> 00:04:57.920 align:start position:0%
identity is not reveal that gossiping to
everybody<00:04:55.790><c> gossiping</c><00:04:56.790><c> in</c><00:04:56.940><c> the</c><00:04:57.150><c> p2p</c><00:04:57.720><c> overlay</c>

00:04:57.920 --> 00:04:57.930 align:start position:0%
everybody gossiping in the p2p overlay
 

00:04:57.930 --> 00:05:04.850 align:start position:0%
everybody gossiping in the p2p overlay
is<00:04:58.650><c> prone</c><00:04:59.430><c> to</c><00:04:59.460><c> Byzantine</c><00:05:00.210><c> failures</c><00:05:00.840><c> and</c><00:05:03.860><c> to</c>

00:05:04.850 --> 00:05:04.860 align:start position:0%
is prone to Byzantine failures and to
 

00:05:04.860 --> 00:05:08.420 align:start position:0%
is prone to Byzantine failures and to
cope<00:05:05.340><c> with</c><00:05:05.610><c> Byzantine</c><00:05:05.880><c> failures</c><00:05:06.920><c> we</c><00:05:07.920><c> have</c><00:05:08.160><c> to</c>

00:05:08.420 --> 00:05:08.430 align:start position:0%
cope with Byzantine failures we have to
 

00:05:08.430 --> 00:05:14.140 align:start position:0%
cope with Byzantine failures we have to
keep<00:05:09.300><c> the</c><00:05:10.170><c> degree</c><00:05:10.560><c> of</c><00:05:10.590><c> the</c><00:05:10.950><c> p2p</c><00:05:11.580><c> mesh</c><00:05:12.240><c> on</c><00:05:12.630><c> a</c>

00:05:14.140 --> 00:05:14.150 align:start position:0%
keep the degree of the p2p mesh on a
 

00:05:14.150 --> 00:05:18.590 align:start position:0%
keep the degree of the p2p mesh on a
certain<00:05:15.150><c> level</c><00:05:15.480><c> and</c><00:05:16.250><c> it</c><00:05:17.250><c> brings</c><00:05:17.610><c> a</c><00:05:17.970><c> redundancy</c>

00:05:18.590 --> 00:05:18.600 align:start position:0%
certain level and it brings a redundancy
 

00:05:18.600 --> 00:05:21.950 align:start position:0%
certain level and it brings a redundancy
the<00:05:19.290><c> degree</c><00:05:19.680><c> is</c><00:05:19.890><c> the</c><00:05:20.190><c> parameter</c><00:05:20.730><c> that</c><00:05:21.030><c> is</c><00:05:21.630><c> just</c>

00:05:21.950 --> 00:05:21.960 align:start position:0%
the degree is the parameter that is just
 

00:05:21.960 --> 00:05:24.920 align:start position:0%
the degree is the parameter that is just
a<00:05:22.050><c> number</c><00:05:22.200><c> of</c><00:05:22.970><c> peers</c><00:05:23.970><c> that</c><00:05:24.360><c> your</c><00:05:24.570><c> peer</c><00:05:24.810><c> is</c>

00:05:24.920 --> 00:05:24.930 align:start position:0%
a number of peers that your peer is
 

00:05:24.930 --> 00:05:28.430 align:start position:0%
a number of peers that your peer is
connected<00:05:25.410><c> to</c><00:05:25.640><c> so</c><00:05:26.640><c> let's</c><00:05:27.210><c> say</c><00:05:27.390><c> your</c><00:05:28.110><c> peer</c><00:05:28.320><c> is</c>

00:05:28.430 --> 00:05:28.440 align:start position:0%
connected to so let's say your peer is
 

00:05:28.440 --> 00:05:32.300 align:start position:0%
connected to so let's say your peer is
connected<00:05:28.919><c> to</c><00:05:28.950><c> ten</c><00:05:29.580><c> peers</c><00:05:30.060><c> and</c><00:05:31.130><c> you</c><00:05:32.130><c> are</c>

00:05:32.300 --> 00:05:32.310 align:start position:0%
connected to ten peers and you are
 

00:05:32.310 --> 00:05:34.880 align:start position:0%
connected to ten peers and you are
receiving<00:05:32.990><c> the</c><00:05:33.990><c> air</c><00:05:34.169><c> to</c><00:05:34.290><c> stay</c><00:05:34.500><c> the</c><00:05:34.710><c> same</c>

00:05:34.880 --> 00:05:34.890 align:start position:0%
receiving the air to stay the same
 

00:05:34.890 --> 00:05:37.520 align:start position:0%
receiving the air to stay the same
attestation<00:05:35.340><c> message</c><00:05:35.940><c> from</c><00:05:36.240><c> five</c><00:05:37.020><c> of</c><00:05:37.050><c> them</c>

00:05:37.520 --> 00:05:37.530 align:start position:0%
attestation message from five of them
 

00:05:37.530 --> 00:05:41.870 align:start position:0%
attestation message from five of them
and<00:05:38.300><c> send</c><00:05:39.300><c> in</c><00:05:39.590><c> this</c><00:05:40.590><c> attestation</c><00:05:41.100><c> propagating</c>

00:05:41.870 --> 00:05:41.880 align:start position:0%
and send in this attestation propagating
 

00:05:41.880 --> 00:05:43.730 align:start position:0%
and send in this attestation propagating
this<00:05:42.000><c> attestation</c><00:05:42.450><c> message</c><00:05:43.020><c> to</c><00:05:43.260><c> the</c><00:05:43.590><c> other</c>

00:05:43.730 --> 00:05:43.740 align:start position:0%
this attestation message to the other
 

00:05:43.740 --> 00:05:46.250 align:start position:0%
this attestation message to the other
five<00:05:44.100><c> so</c><00:05:44.430><c> we</c><00:05:44.550><c> have</c><00:05:44.730><c> like</c><00:05:45.020><c> redundancy</c><00:05:46.020><c> by</c><00:05:46.230><c> a</c>

00:05:46.250 --> 00:05:46.260 align:start position:0%
five so we have like redundancy by a
 

00:05:46.260 --> 00:05:50.920 align:start position:0%
five so we have like redundancy by a
factor<00:05:46.680><c> of</c><00:05:46.710><c> five</c><00:05:47.040><c> and</c><00:05:48.560><c> this</c><00:05:49.669><c> redundancy</c><00:05:50.669><c> is</c>

00:05:50.920 --> 00:05:50.930 align:start position:0%
factor of five and this redundancy is
 

00:05:50.930 --> 00:05:56.620 align:start position:0%
factor of five and this redundancy is
about<00:05:52.130><c> inbound</c><00:05:53.130><c> and</c><00:05:53.490><c> outbound</c><00:05:53.810><c> traffic</c><00:05:54.810><c> and</c>

00:05:56.620 --> 00:05:56.630 align:start position:0%
about inbound and outbound traffic and
 

00:05:56.630 --> 00:06:00.880 align:start position:0%
about inbound and outbound traffic and
also<00:05:57.630><c> nodes</c><00:05:57.960><c> must</c><00:05:58.410><c> do</c><00:05:58.710><c> verification</c><00:05:59.750><c> to</c>

00:06:00.880 --> 00:06:00.890 align:start position:0%
also nodes must do verification to
 

00:06:00.890 --> 00:06:04.940 align:start position:0%
also nodes must do verification to
prevent<00:06:01.890><c> epidemic</c><00:06:02.760><c> attacks</c><00:06:03.229><c> where</c><00:06:04.229><c> the</c>

00:06:04.940 --> 00:06:04.950 align:start position:0%
prevent epidemic attacks where the
 

00:06:04.950 --> 00:06:07.610 align:start position:0%
prevent epidemic attacks where the
network<00:06:05.310><c> can</c><00:06:05.669><c> be</c><00:06:05.820><c> flooded</c><00:06:06.060><c> by</c><00:06:06.390><c> just</c><00:06:07.290><c> bad</c><00:06:07.470><c> at</c>

00:06:07.610 --> 00:06:07.620 align:start position:0%
network can be flooded by just bad at
 

00:06:07.620 --> 00:06:12.980 align:start position:0%
network can be flooded by just bad at
stations<00:06:08.240><c> invalid</c><00:06:09.240><c> and</c><00:06:10.820><c> this</c><00:06:11.820><c> brings</c><00:06:12.210><c> a</c><00:06:12.510><c> high</c>

00:06:12.980 --> 00:06:12.990 align:start position:0%
stations invalid and this brings a high
 

00:06:12.990 --> 00:06:17.180 align:start position:0%
stations invalid and this brings a high
demand<00:06:13.380><c> on</c><00:06:13.770><c> resources</c><00:06:14.370><c> at</c><00:06:14.610><c> scale</c><00:06:14.880><c> so</c><00:06:16.190><c> these</c>

00:06:17.180 --> 00:06:17.190 align:start position:0%
demand on resources at scale so these
 

00:06:17.190 --> 00:06:21.140 align:start position:0%
demand on resources at scale so these
numbers<00:06:17.430><c> are</c><00:06:17.910><c> a</c><00:06:17.970><c> factor</c><00:06:18.600><c> of</c><00:06:19.910><c> redundancy</c><00:06:20.910><c> in</c>

00:06:21.140 --> 00:06:21.150 align:start position:0%
numbers are a factor of redundancy in
 

00:06:21.150 --> 00:06:27.370 align:start position:0%
numbers are a factor of redundancy in
the<00:06:22.110><c> p2p</c><00:06:23.150><c> of</c><00:06:24.150><c> the</c><00:06:24.360><c> p2p</c><00:06:24.630><c> mesh</c><00:06:24.990><c> and</c><00:06:25.640><c> this</c><00:06:26.640><c> like</c>

00:06:27.370 --> 00:06:27.380 align:start position:0%
the p2p of the p2p mesh and this like
 

00:06:27.380 --> 00:06:31.360 align:start position:0%
the p2p of the p2p mesh and this like
triple<00:06:28.380><c> redundancy</c><00:06:28.890><c> is</c><00:06:29.070><c> a</c><00:06:29.130><c> blue</c><00:06:29.400><c> line</c><00:06:29.610><c> and</c><00:06:29.990><c> if</c>

00:06:31.360 --> 00:06:31.370 align:start position:0%
triple redundancy is a blue line and if
 

00:06:31.370 --> 00:06:34.670 align:start position:0%
triple redundancy is a blue line and if
probably<00:06:32.370><c> on</c><00:06:33.060><c> the</c><00:06:33.240><c> face</c><00:06:33.450><c> zero</c><00:06:33.690><c> we</c><00:06:33.930><c> are</c><00:06:33.990><c> okay</c><00:06:34.320><c> we</c>

00:06:34.670 --> 00:06:34.680 align:start position:0%
probably on the face zero we are okay we
 

00:06:34.680 --> 00:06:36.800 align:start position:0%
probably on the face zero we are okay we
are<00:06:34.800><c> here</c><00:06:35.220><c> where</c><00:06:35.490><c> is</c><00:06:35.640><c> it</c><00:06:35.850><c> ten</c><00:06:36.150><c> million</c><00:06:36.479><c> each</c>

00:06:36.800 --> 00:06:36.810 align:start position:0%
are here where is it ten million each
 

00:06:36.810 --> 00:06:39.440 align:start position:0%
are here where is it ten million each
what<00:06:37.650><c> are</c><00:06:37.770><c> the</c><00:06:37.860><c> 18</c><00:06:38.130><c> but</c><00:06:38.669><c> when</c><00:06:38.880><c> we</c><00:06:39.030><c> start</c><00:06:39.300><c> to</c>

00:06:39.440 --> 00:06:39.450 align:start position:0%
what are the 18 but when we start to
 

00:06:39.450 --> 00:06:42.110 align:start position:0%
what are the 18 but when we start to
approach<00:06:39.750><c> to</c><00:06:40.080><c> 50</c><00:06:40.560><c> million</c><00:06:40.890><c> eath</c><00:06:41.130><c> we</c><00:06:41.849><c> are</c>

00:06:42.110 --> 00:06:42.120 align:start position:0%
approach to 50 million eath we are
 

00:06:42.120 --> 00:06:44.820 align:start position:0%
approach to 50 million eath we are
having<00:06:43.080><c> like</c>

00:06:44.820 --> 00:06:44.830 align:start position:0%
having like
 

00:06:44.830 --> 00:06:48.969 align:start position:0%
having like
mmm<00:06:45.830><c> 50</c><00:06:46.759><c> megabits</c><00:06:47.509><c> per</c><00:06:47.629><c> second</c><00:06:48.199><c> as</c><00:06:48.379><c> a</c>

00:06:48.969 --> 00:06:48.979 align:start position:0%
mmm 50 megabits per second as a
 

00:06:48.979 --> 00:06:53.260 align:start position:0%
mmm 50 megabits per second as a
requirement<00:06:49.840><c> and</c><00:06:50.840><c> this</c><00:06:51.740><c> is</c><00:06:52.250><c> calculated</c><00:06:52.759><c> for</c>

00:06:53.260 --> 00:06:53.270 align:start position:0%
requirement and this is calculated for
 

00:06:53.270 --> 00:06:57.580 align:start position:0%
requirement and this is calculated for
60<00:06:53.689><c> seconds</c><00:06:53.960><c> per</c><00:06:54.050><c> slot</c><00:06:56.080><c> what</c><00:06:57.080><c> do</c><00:06:57.169><c> we</c><00:06:57.319><c> do</c><00:06:57.439><c> with</c>

00:06:57.580 --> 00:06:57.590 align:start position:0%
60 seconds per slot what do we do with
 

00:06:57.590 --> 00:07:02.080 align:start position:0%
60 seconds per slot what do we do with
this<00:06:58.960><c> instead</c><00:06:59.960><c> of</c><00:07:00.250><c> sending</c><00:07:01.250><c> single</c>

00:07:02.080 --> 00:07:02.090 align:start position:0%
this instead of sending single
 

00:07:02.090 --> 00:07:06.959 align:start position:0%
this instead of sending single
attestation<00:07:02.539><c> to</c><00:07:03.379><c> this</c><00:07:04.240><c> Peter</c><00:07:05.240><c> Pan</c><00:07:05.330><c> mesh</c><00:07:05.710><c> where</c>

00:07:06.959 --> 00:07:06.969 align:start position:0%
attestation to this Peter Pan mesh where
 

00:07:06.969 --> 00:07:10.749 align:start position:0%
attestation to this Peter Pan mesh where
we<00:07:07.969><c> want</c><00:07:08.210><c> to</c><00:07:08.500><c> partially</c><00:07:09.500><c> aggregate</c><00:07:10.099><c> them</c><00:07:10.370><c> in</c>

00:07:10.749 --> 00:07:10.759 align:start position:0%
we want to partially aggregate them in
 

00:07:10.759 --> 00:07:15.339 align:start position:0%
we want to partially aggregate them in
relatively<00:07:11.689><c> small</c><00:07:12.819><c> overlays</c><00:07:13.819><c> and</c><00:07:14.150><c> only</c><00:07:14.870><c> after</c>

00:07:15.339 --> 00:07:15.349 align:start position:0%
relatively small overlays and only after
 

00:07:15.349 --> 00:07:19.240 align:start position:0%
relatively small overlays and only after
that<00:07:15.530><c> send</c><00:07:16.400><c> it</c><00:07:16.580><c> to</c><00:07:16.729><c> the</c><00:07:17.830><c> to</c><00:07:18.830><c> the</c><00:07:18.949><c> beacon</c>

00:07:19.240 --> 00:07:19.250 align:start position:0%
that send it to the to the beacon
 

00:07:19.250 --> 00:07:23.499 align:start position:0%
that send it to the to the beacon
attestation<00:07:19.639><c> where</c><00:07:20.360><c> everybody</c><00:07:20.870><c> sign</c><00:07:21.199><c> to</c><00:07:22.509><c> this</c>

00:07:23.499 --> 00:07:23.509 align:start position:0%
attestation where everybody sign to this
 

00:07:23.509 --> 00:07:27.010 align:start position:0%
attestation where everybody sign to this
is<00:07:23.719><c> where</c><00:07:24.279><c> aggregate</c><00:07:25.279><c> and</c><00:07:25.490><c> overlays</c><00:07:26.020><c> comes</c>

00:07:27.010 --> 00:07:27.020 align:start position:0%
is where aggregate and overlays comes
 

00:07:27.020 --> 00:07:30.519 align:start position:0%
is where aggregate and overlays comes
into<00:07:27.529><c> play</c><00:07:27.740><c> so</c><00:07:28.419><c> what</c><00:07:29.419><c> options</c><00:07:29.599><c> do</c><00:07:29.960><c> we</c><00:07:30.020><c> have</c><00:07:30.080><c> for</c>

00:07:30.519 --> 00:07:30.529 align:start position:0%
into play so what options do we have for
 

00:07:30.529 --> 00:07:33.429 align:start position:0%
into play so what options do we have for
those<00:07:31.069><c> overlays</c><00:07:31.639><c> we</c><00:07:32.509><c> can</c><00:07:32.659><c> build</c><00:07:32.930><c> them</c><00:07:33.169><c> for</c>

00:07:33.429 --> 00:07:33.439 align:start position:0%
those overlays we can build them for
 

00:07:33.439 --> 00:07:37.420 align:start position:0%
those overlays we can build them for
each<00:07:33.650><c> people</c><00:07:34.069><c> because</c><00:07:34.870><c> we</c><00:07:35.870><c> know</c><00:07:36.430><c> what</c>

00:07:37.420 --> 00:07:37.430 align:start position:0%
each people because we know what
 

00:07:37.430 --> 00:07:41.800 align:start position:0%
each people because we know what
committees<00:07:37.879><c> are</c><00:07:38.240><c> in</c><00:07:38.569><c> each</c><00:07:39.050><c> chip</c><00:07:40.210><c> o-64</c><00:07:41.210><c> slot</c>

00:07:41.800 --> 00:07:41.810 align:start position:0%
committees are in each chip o-64 slot
 

00:07:41.810 --> 00:07:46.089 align:start position:0%
committees are in each chip o-64 slot
beforehand<00:07:42.939><c> it's</c><00:07:43.939><c> like</c><00:07:44.150><c> six</c><00:07:44.449><c> minutes</c><00:07:44.919><c> so</c><00:07:45.919><c> we</c>

00:07:46.089 --> 00:07:46.099 align:start position:0%
beforehand it's like six minutes so we
 

00:07:46.099 --> 00:07:49.360 align:start position:0%
beforehand it's like six minutes so we
could<00:07:46.279><c> probably</c><00:07:46.490><c> just</c><00:07:47.060><c> build</c><00:07:47.990><c> them</c><00:07:48.250><c> for</c><00:07:49.250><c> each</c>

00:07:49.360 --> 00:07:49.370 align:start position:0%
could probably just build them for each
 

00:07:49.370 --> 00:07:54.430 align:start position:0%
could probably just build them for each
Ipoh<00:07:50.830><c> or</c><00:07:51.860><c> there</c><00:07:52.400><c> is</c><00:07:52.520><c> another</c><00:07:52.819><c> option</c><00:07:53.150><c> and</c><00:07:53.659><c> to</c>

00:07:54.430 --> 00:07:54.440 align:start position:0%
Ipoh or there is another option and to
 

00:07:54.440 --> 00:07:58.089 align:start position:0%
Ipoh or there is another option and to
use<00:07:54.620><c> short</c><00:07:54.919><c> subnets</c><00:07:56.409><c> these</c><00:07:57.409><c> are</c><00:07:57.650><c> like</c><00:07:57.830><c> natural</c>

00:07:58.089 --> 00:07:58.099 align:start position:0%
use short subnets these are like natural
 

00:07:58.099 --> 00:08:03.999 align:start position:0%
use short subnets these are like natural
overlays<00:07:58.849><c> for</c><00:07:59.210><c> for</c><00:08:00.139><c> the</c><00:08:00.879><c> earth</c><00:08:01.879><c> 2.0</c><00:08:02.770><c> so</c><00:08:03.770><c> the</c>

00:08:03.999 --> 00:08:04.009 align:start position:0%
overlays for for the earth 2.0 so the
 

00:08:04.009 --> 00:08:08.350 align:start position:0%
overlays for for the earth 2.0 so the
requirements<00:08:04.699><c> are</c><00:08:04.909><c> to</c><00:08:05.210><c> the</c><00:08:05.810><c> overlay</c><00:08:06.319><c> are</c><00:08:07.360><c> like</c>

00:08:08.350 --> 00:08:08.360 align:start position:0%
requirements are to the overlay are like
 

00:08:08.360 --> 00:08:10.149 align:start position:0%
requirements are to the overlay are like
first<00:08:08.539><c> of</c><00:08:08.779><c> all</c><00:08:08.930><c> it</c><00:08:09.080><c> should</c><00:08:09.289><c> be</c><00:08:09.440><c> relatively</c>

00:08:10.149 --> 00:08:10.159 align:start position:0%
first of all it should be relatively
 

00:08:10.159 --> 00:08:13.059 align:start position:0%
first of all it should be relatively
small<00:08:10.400><c> and</c><00:08:10.729><c> efficient</c><00:08:11.300><c> enough</c><00:08:11.629><c> to</c><00:08:12.500><c> do</c><00:08:12.770><c> this</c>

00:08:13.059 --> 00:08:13.069 align:start position:0%
small and efficient enough to do this
 

00:08:13.069 --> 00:08:15.040 align:start position:0%
small and efficient enough to do this
partial<00:08:13.520><c> aggregation</c><00:08:14.120><c> in</c><00:08:14.240><c> the</c><00:08:14.300><c> fractions</c><00:08:14.810><c> of</c>

00:08:15.040 --> 00:08:15.050 align:start position:0%
partial aggregation in the fractions of
 

00:08:15.050 --> 00:08:17.800 align:start position:0%
partial aggregation in the fractions of
slot<00:08:15.409><c> because</c><00:08:16.250><c> we</c><00:08:16.460><c> need</c><00:08:16.669><c> to</c><00:08:16.849><c> send</c><00:08:17.150><c> those</c>

00:08:17.800 --> 00:08:17.810 align:start position:0%
slot because we need to send those
 

00:08:17.810 --> 00:08:20.890 align:start position:0%
slot because we need to send those
aggregates<00:08:18.289><c> to</c><00:08:18.939><c> that</c><00:08:19.939><c> be</c><00:08:20.150><c> to</c><00:08:20.210><c> be</c><00:08:20.419><c> matched</c><00:08:20.659><c> so</c>

00:08:20.890 --> 00:08:20.900 align:start position:0%
aggregates to that be to be matched so
 

00:08:20.900 --> 00:08:21.550 align:start position:0%
aggregates to that be to be matched so
it<00:08:21.020><c> takes</c>

00:08:21.550 --> 00:08:21.560 align:start position:0%
it takes
 

00:08:21.560 --> 00:08:25.719 align:start position:0%
it takes
we<00:08:22.370><c> are</c><00:08:22.639><c> very</c><00:08:23.000><c> restricted</c><00:08:23.599><c> in</c><00:08:23.839><c> time</c><00:08:24.520><c> so</c><00:08:25.520><c> it</c>

00:08:25.719 --> 00:08:25.729 align:start position:0%
we are very restricted in time so it
 

00:08:25.729 --> 00:08:28.809 align:start position:0%
we are very restricted in time so it
should<00:08:25.759><c> be</c><00:08:26.029><c> incentivized</c><00:08:26.810><c> a</c><00:08:27.819><c> the</c>

00:08:28.809 --> 00:08:28.819 align:start position:0%
should be incentivized a the
 

00:08:28.819 --> 00:08:30.670 align:start position:0%
should be incentivized a the
participants<00:08:29.509><c> of</c><00:08:29.599><c> this</c><00:08:29.750><c> overlay</c><00:08:30.229><c> should</c><00:08:30.529><c> be</c>

00:08:30.670 --> 00:08:30.680 align:start position:0%
participants of this overlay should be
 

00:08:30.680 --> 00:08:32.769 align:start position:0%
participants of this overlay should be
incentivized<00:08:31.310><c> to</c><00:08:31.460><c> do</c><00:08:31.789><c> the</c><00:08:32.000><c> aggregation</c><00:08:32.449><c> and</c>

00:08:32.769 --> 00:08:32.779 align:start position:0%
incentivized to do the aggregation and
 

00:08:32.779 --> 00:08:37.259 align:start position:0%
incentivized to do the aggregation and
the<00:08:33.529><c> only</c><00:08:33.829><c> one</c><00:08:34.010><c> who</c><00:08:34.279><c> are</c><00:08:34.430><c> incentivize</c><00:08:35.149><c> did</c><00:08:35.479><c> the</c>

00:08:37.259 --> 00:08:37.269 align:start position:0%
the only one who are incentivize did the
 

00:08:37.269 --> 00:08:39.550 align:start position:0%
the only one who are incentivize did the
committee's<00:08:38.269><c> that</c><00:08:38.300><c> produce</c><00:08:38.719><c> those</c><00:08:39.320><c> data</c>

00:08:39.550 --> 00:08:39.560 align:start position:0%
committee's that produce those data
 

00:08:39.560 --> 00:08:42.189 align:start position:0%
committee's that produce those data
stations<00:08:40.070><c> it</c><00:08:40.760><c> should</c><00:08:40.909><c> be</c><00:08:41.060><c> Byzantine</c><00:08:41.630><c> tolerant</c>

00:08:42.189 --> 00:08:42.199 align:start position:0%
stations it should be Byzantine tolerant
 

00:08:42.199 --> 00:08:44.740 align:start position:0%
stations it should be Byzantine tolerant
being<00:08:42.589><c> relatively</c><00:08:43.430><c> small</c><00:08:43.789><c> it</c><00:08:44.360><c> should</c><00:08:44.630><c> be</c>

00:08:44.740 --> 00:08:44.750 align:start position:0%
being relatively small it should be
 

00:08:44.750 --> 00:08:49.360 align:start position:0%
being relatively small it should be
tolerant<00:08:44.990><c> to</c><00:08:45.500><c> kind</c><00:08:45.860><c> of</c><00:08:45.980><c> see</c><00:08:46.250><c> bill</c><00:08:46.459><c> and</c><00:08:48.370><c> Eclipse</c>

00:08:49.360 --> 00:08:49.370 align:start position:0%
tolerant to kind of see bill and Eclipse
 

00:08:49.370 --> 00:08:53.160 align:start position:0%
tolerant to kind of see bill and Eclipse
attacks<00:08:49.820><c> and</c><00:08:50.690><c> if</c><00:08:51.440><c> we</c><00:08:51.620><c> want</c><00:08:51.829><c> to</c><00:08:51.920><c> build</c><00:08:52.190><c> the</c>

00:08:53.160 --> 00:08:53.170 align:start position:0%
attacks and if we want to build the
 

00:08:53.170 --> 00:08:56.470 align:start position:0%
attacks and if we want to build the
overlay<00:08:54.170><c> for</c><00:08:55.010><c> each</c><00:08:55.130><c> shaper</c><00:08:55.490><c> we</c><00:08:55.790><c> have</c><00:08:56.029><c> a</c><00:08:56.060><c> six</c>

00:08:56.470 --> 00:08:56.480 align:start position:0%
overlay for each shaper we have a six
 

00:08:56.480 --> 00:08:58.180 align:start position:0%
overlay for each shaper we have a six
point<00:08:56.720><c> five</c><00:08:56.899><c> minutes</c><00:08:57.440><c> to</c><00:08:57.829><c> do</c><00:08:57.949><c> the</c>

00:08:58.180 --> 00:08:58.190 align:start position:0%
point five minutes to do the
 

00:08:58.190 --> 00:09:02.620 align:start position:0%
point five minutes to do the
so<00:08:58.610><c> this</c><00:08:58.910><c> time</c><00:08:59.840><c> restriction</c><00:09:01.030><c> okay</c><00:09:02.030><c> so</c><00:09:02.090><c> para</c>

00:09:02.620 --> 00:09:02.630 align:start position:0%
so this time restriction okay so para
 

00:09:02.630 --> 00:09:07.210 align:start position:0%
so this time restriction okay so para
Baja<00:09:04.660><c> overlays</c><00:09:05.660><c> are</c><00:09:05.930><c> very</c><00:09:06.110><c> efficient</c><00:09:06.710><c> because</c>

00:09:07.210 --> 00:09:07.220 align:start position:0%
Baja overlays are very efficient because
 

00:09:07.220 --> 00:09:11.760 align:start position:0%
Baja overlays are very efficient because
you<00:09:07.400><c> can</c><00:09:07.670><c> build</c><00:09:08.920><c> this</c><00:09:09.920><c> overlay</c><00:09:10.640><c> with</c><00:09:11.450><c> whatever</c>

00:09:11.760 --> 00:09:11.770 align:start position:0%
you can build this overlay with whatever
 

00:09:11.770 --> 00:09:14.440 align:start position:0%
you can build this overlay with whatever
topology<00:09:12.770><c> and</c><00:09:13.100><c> properties</c><00:09:13.910><c> that</c><00:09:13.940><c> you</c><00:09:14.420><c> want</c>

00:09:14.440 --> 00:09:14.450 align:start position:0%
topology and properties that you want
 

00:09:14.450 --> 00:09:18.340 align:start position:0%
topology and properties that you want
and<00:09:15.130><c> it</c><00:09:16.130><c> could</c><00:09:16.340><c> be</c><00:09:16.550><c> after</c><00:09:16.880><c> that</c><00:09:17.330><c> leveraged</c><00:09:17.960><c> by</c>

00:09:18.340 --> 00:09:18.350 align:start position:0%
and it could be after that leveraged by
 

00:09:18.350 --> 00:09:21.790 align:start position:0%
and it could be after that leveraged by
your<00:09:18.650><c> aggregation</c><00:09:19.400><c> strategy</c><00:09:20.110><c> but</c><00:09:21.110><c> the</c>

00:09:21.790 --> 00:09:21.800 align:start position:0%
your aggregation strategy but the
 

00:09:21.800 --> 00:09:24.640 align:start position:0%
your aggregation strategy but the
drawback<00:09:22.280><c> of</c><00:09:22.310><c> that</c><00:09:22.700><c> is</c><00:09:22.940><c> that</c><00:09:23.450><c> you</c><00:09:24.410><c> need</c><00:09:24.590><c> a</c>

00:09:24.640 --> 00:09:24.650 align:start position:0%
drawback of that is that you need a
 

00:09:24.650 --> 00:09:28.240 align:start position:0%
drawback of that is that you need a
reliable<00:09:25.460><c> source</c><00:09:25.730><c> of</c><00:09:25.970><c> peers</c><00:09:26.650><c> within</c><00:09:27.650><c> a</c><00:09:27.920><c> small</c>

00:09:28.240 --> 00:09:28.250 align:start position:0%
reliable source of peers within a small
 

00:09:28.250 --> 00:09:32.500 align:start position:0%
reliable source of peers within a small
amount<00:09:28.550><c> of</c><00:09:28.790><c> time</c><00:09:29.120><c> and</c><00:09:30.280><c> the</c><00:09:31.280><c> topic</c><00:09:31.940><c> discovery</c>

00:09:32.500 --> 00:09:32.510 align:start position:0%
amount of time and the topic discovery
 

00:09:32.510 --> 00:09:36.460 align:start position:0%
amount of time and the topic discovery
will<00:09:33.020><c> probably</c><00:09:33.890><c> not</c><00:09:34.070><c> help</c><00:09:34.360><c> here</c><00:09:35.360><c> because</c><00:09:36.110><c> if</c>

00:09:36.460 --> 00:09:36.470 align:start position:0%
will probably not help here because if
 

00:09:36.470 --> 00:09:38.110 align:start position:0%
will probably not help here because if
you<00:09:36.620><c> don't</c><00:09:36.830><c> have</c><00:09:37.040><c> a</c><00:09:37.070><c> reliable</c><00:09:37.430><c> source</c><00:09:37.880><c> of</c>

00:09:38.110 --> 00:09:38.120 align:start position:0%
you don't have a reliable source of
 

00:09:38.120 --> 00:09:40.990 align:start position:0%
you don't have a reliable source of
peers<00:09:38.500><c> your</c><00:09:39.500><c> overlay</c><00:09:40.310><c> will</c><00:09:40.550><c> be</c><00:09:40.700><c> prone</c><00:09:40.970><c> to</c>

00:09:40.990 --> 00:09:41.000 align:start position:0%
peers your overlay will be prone to
 

00:09:41.000 --> 00:09:43.390 align:start position:0%
peers your overlay will be prone to
civil<00:09:41.540><c> and</c><00:09:41.720><c> eclipse</c><00:09:42.020><c> attacks</c><00:09:42.440><c> so</c><00:09:42.980><c> this</c><00:09:43.190><c> is</c>

00:09:43.390 --> 00:09:43.400 align:start position:0%
civil and eclipse attacks so this is
 

00:09:43.400 --> 00:09:46.180 align:start position:0%
civil and eclipse attacks so this is
very<00:09:43.840><c> difficult</c><00:09:44.840><c> part</c><00:09:45.170><c> of</c><00:09:45.410><c> building</c><00:09:46.010><c> this</c>

00:09:46.180 --> 00:09:46.190 align:start position:0%
very difficult part of building this
 

00:09:46.190 --> 00:09:49.990 align:start position:0%
very difficult part of building this
epoch<00:09:46.700><c> very</c><00:09:47.300><c> paja</c><00:09:47.780><c> overlay</c><00:09:48.560><c> we</c><00:09:49.280><c> can</c><00:09:49.490><c> use</c><00:09:49.670><c> short</c>

00:09:49.990 --> 00:09:50.000 align:start position:0%
epoch very paja overlay we can use short
 

00:09:50.000 --> 00:09:52.210 align:start position:0%
epoch very paja overlay we can use short
subnets<00:09:50.600><c> they</c><00:09:50.900><c> already</c><00:09:51.200><c> exist</c><00:09:51.740><c> they</c><00:09:52.040><c> are</c>

00:09:52.210 --> 00:09:52.220 align:start position:0%
subnets they already exist they are
 

00:09:52.220 --> 00:09:59.590 align:start position:0%
subnets they already exist they are
relatively<00:09:55.300><c> weak</c><00:09:56.300><c> and</c><00:09:56.680><c> they</c><00:09:57.680><c> are</c><00:09:57.740><c> like</c><00:09:58.600><c> more</c>

00:09:59.590 --> 00:09:59.600 align:start position:0%
relatively weak and they are like more
 

00:09:59.600 --> 00:10:04.120 align:start position:0%
relatively weak and they are like more
long<00:09:59.990><c> plain</c><00:10:01.270><c> network</c><00:10:02.270><c> units</c><00:10:02.780><c> and</c><00:10:03.050><c> the</c><00:10:03.470><c> hence</c>

00:10:04.120 --> 00:10:04.130 align:start position:0%
long plain network units and the hence
 

00:10:04.130 --> 00:10:07.080 align:start position:0%
long plain network units and the hence
they<00:10:04.490><c> are</c><00:10:04.520><c> resistant</c><00:10:05.210><c> to</c><00:10:05.290><c> kind</c><00:10:06.290><c> of</c><00:10:06.440><c> attacks</c>

00:10:07.080 --> 00:10:07.090 align:start position:0%
they are resistant to kind of attacks
 

00:10:07.090 --> 00:10:11.410 align:start position:0%
they are resistant to kind of attacks
like<00:10:08.090><c> Eclipse</c><00:10:08.570><c> and</c><00:10:08.780><c> civil</c><00:10:09.110><c> and</c><00:10:09.970><c> but</c><00:10:10.970><c> the</c>

00:10:11.410 --> 00:10:11.420 align:start position:0%
like Eclipse and civil and but the
 

00:10:11.420 --> 00:10:14.170 align:start position:0%
like Eclipse and civil and but the
problem<00:10:11.810><c> is</c><00:10:11.960><c> that</c><00:10:12.320><c> one</c><00:10:12.920><c> committee</c><00:10:13.490><c> is</c><00:10:13.760><c> spread</c>

00:10:14.170 --> 00:10:14.180 align:start position:0%
problem is that one committee is spread
 

00:10:14.180 --> 00:10:18.130 align:start position:0%
problem is that one committee is spread
across<00:10:14.450><c> all</c><00:10:14.870><c> the</c><00:10:15.710><c> shard</c><00:10:16.010><c> subnets</c><00:10:16.750><c> so</c><00:10:17.750><c> let's</c>

00:10:18.130 --> 00:10:18.140 align:start position:0%
across all the shard subnets so let's
 

00:10:18.140 --> 00:10:21.310 align:start position:0%
across all the shard subnets so let's
say<00:10:18.350><c> you</c><00:10:18.410><c> have</c><00:10:18.740><c> 10</c><00:10:18.980><c> peers</c><00:10:19.630><c> attend</c><00:10:20.630><c> validators</c>

00:10:21.310 --> 00:10:21.320 align:start position:0%
say you have 10 peers attend validators
 

00:10:21.320 --> 00:10:24.520 align:start position:0%
say you have 10 peers attend validators
of<00:10:21.650><c> one</c><00:10:22.400><c> committee</c><00:10:23.000><c> in</c><00:10:23.180><c> one</c><00:10:23.420><c> in</c><00:10:23.660><c> charge</c><00:10:24.020><c> subnet</c>

00:10:24.520 --> 00:10:24.530 align:start position:0%
of one committee in one in charge subnet
 

00:10:24.530 --> 00:10:27.100 align:start position:0%
of one committee in one in charge subnet
number<00:10:24.740><c> one</c><00:10:25.190><c> then</c><00:10:26.030><c> in</c><00:10:26.210><c> charge</c><00:10:26.420><c> subnet</c><00:10:26.870><c> number</c>

00:10:27.100 --> 00:10:27.110 align:start position:0%
number one then in charge subnet number
 

00:10:27.110 --> 00:10:28.690 align:start position:0%
number one then in charge subnet number
five<00:10:27.620><c> and</c><00:10:28.010><c> so</c><00:10:28.160><c> forth</c>

00:10:28.690 --> 00:10:28.700 align:start position:0%
five and so forth
 

00:10:28.700 --> 00:10:32.190 align:start position:0%
five and so forth
and<00:10:28.990><c> they</c><00:10:29.990><c> just</c><00:10:30.440><c> can't</c><00:10:30.770><c> talk</c><00:10:31.010><c> to</c><00:10:31.580><c> each</c><00:10:31.610><c> other</c>

00:10:32.190 --> 00:10:32.200 align:start position:0%
and they just can't talk to each other
 

00:10:32.200 --> 00:10:34.870 align:start position:0%
and they just can't talk to each other
that<00:10:33.200><c> is</c><00:10:33.410><c> the</c><00:10:33.590><c> problem</c><00:10:34.040><c> for</c><00:10:34.070><c> the</c><00:10:34.370><c> aggregation</c>

00:10:34.870 --> 00:10:34.880 align:start position:0%
that is the problem for the aggregation
 

00:10:34.880 --> 00:10:39.160 align:start position:0%
that is the problem for the aggregation
strategies<00:10:35.690><c> so</c><00:10:36.530><c> two</c><00:10:37.490><c> strategies</c><00:10:38.000><c> so</c><00:10:38.750><c> one</c><00:10:39.020><c> is</c>

00:10:39.160 --> 00:10:39.170 align:start position:0%
strategies so two strategies so one is
 

00:10:39.170 --> 00:10:42.190 align:start position:0%
strategies so two strategies so one is
coordinated<00:10:40.040><c> it's</c><00:10:40.700><c> like</c><00:10:40.970><c> handle</c><00:10:41.480><c> you</c>

00:10:42.190 --> 00:10:42.200 align:start position:0%
coordinated it's like handle you
 

00:10:42.200 --> 00:10:46.920 align:start position:0%
coordinated it's like handle you
probably<00:10:42.620><c> heard</c><00:10:42.980><c> about</c><00:10:43.130><c> that</c><00:10:43.960><c> it's</c><00:10:44.960><c> very</c><00:10:45.460><c> like</c>

00:10:46.920 --> 00:10:46.930 align:start position:0%
probably heard about that it's very like
 

00:10:46.930 --> 00:10:52.120 align:start position:0%
probably heard about that it's very like
optimal<00:10:48.250><c> so</c><00:10:49.250><c> you</c><00:10:50.089><c> can</c><00:10:50.330><c> get</c><00:10:50.690><c> clean</c><00:10:51.230><c> aggregates</c>

00:10:52.120 --> 00:10:52.130 align:start position:0%
optimal so you can get clean aggregates
 

00:10:52.130 --> 00:10:55.810 align:start position:0%
optimal so you can get clean aggregates
without<00:10:52.670><c> overlapping</c><00:10:53.770><c> with</c><00:10:54.770><c> lower</c><00:10:55.100><c> network</c>

00:10:55.810 --> 00:10:55.820 align:start position:0%
without overlapping with lower network
 

00:10:55.820 --> 00:10:59.520 align:start position:0%
without overlapping with lower network
demand<00:10:56.589><c> but</c><00:10:57.589><c> this</c><00:10:58.250><c> kind</c><00:10:58.580><c> of</c><00:10:58.760><c> strategies</c>

00:10:59.520 --> 00:10:59.530 align:start position:0%
demand but this kind of strategies
 

00:10:59.530 --> 00:11:02.829 align:start position:0%
demand but this kind of strategies
requires<00:11:00.530><c> those</c><00:11:00.980><c> overlays</c><00:11:01.610><c> to</c><00:11:01.670><c> be</c><00:11:02.030><c> built</c><00:11:02.270><c> very</c>

00:11:02.829 --> 00:11:02.839 align:start position:0%
requires those overlays to be built very
 

00:11:02.839 --> 00:11:07.260 align:start position:0%
requires those overlays to be built very
poor<00:11:03.260><c> and</c><00:11:04.150><c> we</c><00:11:05.150><c> have</c><00:11:05.360><c> this</c><00:11:05.630><c> difficulty</c><00:11:06.410><c> with</c>

00:11:07.260 --> 00:11:07.270 align:start position:0%
poor and we have this difficulty with
 

00:11:07.270 --> 00:11:10.210 align:start position:0%
poor and we have this difficulty with
reliable<00:11:08.270><c> source</c><00:11:08.600><c> of</c><00:11:08.870><c> peers</c><00:11:09.320><c> and</c><00:11:09.560><c> they</c><00:11:10.100><c> are</c>

00:11:10.210 --> 00:11:10.220 align:start position:0%
reliable source of peers and they are
 

00:11:10.220 --> 00:11:11.950 align:start position:0%
reliable source of peers and they are
not<00:11:10.580><c> be</c><00:11:10.910><c> to</c><00:11:11.030><c> be</c><00:11:11.180><c> friendly</c>

00:11:11.950 --> 00:11:11.960 align:start position:0%
not be to be friendly
 

00:11:11.960 --> 00:11:16.480 align:start position:0%
not be to be friendly
it<00:11:12.200><c> should</c><00:11:12.440><c> be</c><00:11:14.350><c> there</c><00:11:15.350><c> should</c><00:11:15.620><c> exist</c><00:11:15.770><c> direct</c>

00:11:16.480 --> 00:11:16.490 align:start position:0%
it should be there should exist direct
 

00:11:16.490 --> 00:11:19.900 align:start position:0%
it should be there should exist direct
connection<00:11:17.060><c> between</c><00:11:17.440><c> validators</c><00:11:18.440><c> and</c><00:11:18.910><c> that's</c>

00:11:19.900 --> 00:11:19.910 align:start position:0%
connection between validators and that's
 

00:11:19.910 --> 00:11:25.660 align:start position:0%
connection between validators and that's
why<00:11:20.710><c> we</c><00:11:21.710><c> have</c><00:11:21.950><c> let's</c><00:11:23.140><c> we</c><00:11:24.140><c> are</c><00:11:24.380><c> getting</c><00:11:25.250><c> back</c><00:11:25.430><c> to</c>

00:11:25.660 --> 00:11:25.670 align:start position:0%
why we have let's we are getting back to
 

00:11:25.670 --> 00:11:32.620 align:start position:0%
why we have let's we are getting back to
this<00:11:27.459><c> anonymity</c><00:11:28.459><c> problem</c><00:11:29.000><c> here</c><00:11:29.510><c> again</c><00:11:31.360><c> we</c><00:11:32.360><c> can</c>

00:11:32.620 --> 00:11:32.630 align:start position:0%
this anonymity problem here again we can
 

00:11:32.630 --> 00:11:38.650 align:start position:0%
this anonymity problem here again we can
use<00:11:32.660><c> chart</c><00:11:34.180><c> subnets</c><00:11:35.180><c> and</c><00:11:35.600><c> to</c><00:11:36.850><c> fire</c><00:11:37.850><c> a</c><00:11:38.120><c> gossip</c>

00:11:38.650 --> 00:11:38.660 align:start position:0%
use chart subnets and to fire a gossip
 

00:11:38.660 --> 00:11:43.269 align:start position:0%
use chart subnets and to fire a gossip
based<00:11:39.190><c> strategy</c><00:11:40.390><c> so</c><00:11:41.390><c> it's</c><00:11:41.870><c> just</c><00:11:42.160><c> you</c><00:11:43.160><c> know</c>

00:11:43.269 --> 00:11:43.279 align:start position:0%
based strategy so it's just you know
 

00:11:43.279 --> 00:11:47.560 align:start position:0%
based strategy so it's just you know
everything<00:11:43.880><c> is</c><00:11:44.209><c> ready</c><00:11:44.510><c> for</c><00:11:44.810><c> it</c><00:11:44.990><c> but</c><00:11:46.360><c> and</c><00:11:47.360><c> you</c>

00:11:47.560 --> 00:11:47.570 align:start position:0%
everything is ready for it but and you
 

00:11:47.570 --> 00:11:49.480 align:start position:0%
everything is ready for it but and you
can<00:11:47.630><c> send</c><00:11:48.050><c> messages</c><00:11:48.290><c> you</c><00:11:48.920><c> can</c><00:11:48.980><c> send</c><00:11:49.100><c> at</c><00:11:49.399><c> the</c>

00:11:49.480 --> 00:11:49.490 align:start position:0%
can send messages you can send at the
 

00:11:49.490 --> 00:11:52.510 align:start position:0%
can send messages you can send at the
station<00:11:49.850><c> within</c><00:11:50.180><c> one</c><00:11:50.360><c> subnet</c><00:11:50.980><c> make</c><00:11:51.980><c> those</c>

00:11:52.510 --> 00:11:52.520 align:start position:0%
station within one subnet make those
 

00:11:52.520 --> 00:11:57.940 align:start position:0%
station within one subnet make those
aggregates<00:11:55.149><c> and</c><00:11:56.230><c> yeah</c><00:11:57.230><c> well</c><00:11:57.380><c> the</c><00:11:57.440><c> dealers</c><00:11:57.709><c> of</c>

00:11:57.940 --> 00:11:57.950 align:start position:0%
aggregates and yeah well the dealers of
 

00:11:57.950 --> 00:11:59.710 align:start position:0%
aggregates and yeah well the dealers of
the<00:11:58.130><c> committee</c><00:11:58.610><c> that</c><00:11:58.820><c> produced</c><00:11:59.209><c> those</c><00:11:59.420><c> at</c><00:11:59.630><c> the</c>

00:11:59.710 --> 00:11:59.720 align:start position:0%
the committee that produced those at the
 

00:11:59.720 --> 00:12:02.650 align:start position:0%
the committee that produced those at the
stations<00:12:00.140><c> can</c><00:12:00.430><c> aggregate</c><00:12:01.430><c> them</c><00:12:01.700><c> but</c><00:12:02.300><c> it's</c>

00:12:02.650 --> 00:12:02.660 align:start position:0%
stations can aggregate them but it's
 

00:12:02.660 --> 00:12:04.720 align:start position:0%
stations can aggregate them but it's
requires<00:12:03.320><c> higher</c><00:12:03.680><c> Network</c><00:12:04.130><c> demand</c><00:12:04.490><c> because</c>

00:12:04.720 --> 00:12:04.730 align:start position:0%
requires higher Network demand because
 

00:12:04.730 --> 00:12:08.440 align:start position:0%
requires higher Network demand because
we're<00:12:04.910><c> working</c><00:12:05.570><c> in</c><00:12:05.839><c> a</c><00:12:05.959><c> p2p</c><00:12:06.459><c> mesh</c><00:12:07.459><c> and</c><00:12:07.790><c> it's</c><00:12:08.209><c> not</c>

00:12:08.440 --> 00:12:08.450 align:start position:0%
we're working in a p2p mesh and it's not
 

00:12:08.450 --> 00:12:11.019 align:start position:0%
we're working in a p2p mesh and it's not
that<00:12:08.690><c> advice</c><00:12:09.110><c> what</c><00:12:09.890><c> is</c><00:12:10.010><c> the</c><00:12:10.220><c> threshold</c><00:12:10.640><c> for</c>

00:12:11.019 --> 00:12:11.029 align:start position:0%
that advice what is the threshold for
 

00:12:11.029 --> 00:12:12.820 align:start position:0%
that advice what is the threshold for
the<00:12:11.180><c> aggregation</c><00:12:11.690><c> and</c><00:12:12.020><c> when</c><00:12:12.260><c> it's</c><00:12:12.500><c> ready</c><00:12:12.740><c> to</c>

00:12:12.820 --> 00:12:12.830 align:start position:0%
the aggregation and when it's ready to
 

00:12:12.830 --> 00:12:17.560 align:start position:0%
the aggregation and when it's ready to
be<00:12:13.100><c> sent</c><00:12:13.370><c> to</c><00:12:13.640><c> the</c><00:12:15.130><c> beacon</c><00:12:16.130><c> attestation</c><00:12:16.570><c> topic</c>

00:12:17.560 --> 00:12:17.570 align:start position:0%
be sent to the beacon attestation topic
 

00:12:17.570 --> 00:12:22.140 align:start position:0%
be sent to the beacon attestation topic
and<00:12:18.640><c> that's</c><00:12:19.640><c> probably</c><00:12:20.420><c> the</c><00:12:20.720><c> problem</c><00:12:20.900><c> here</c><00:12:21.410><c> and</c>

00:12:22.140 --> 00:12:22.150 align:start position:0%
and that's probably the problem here and
 

00:12:22.150 --> 00:12:25.180 align:start position:0%
and that's probably the problem here and
this<00:12:23.150><c> problem</c><00:12:23.420><c> is</c><00:12:23.630><c> amplified</c><00:12:24.200><c> by</c><00:12:24.230><c> spreading</c>

00:12:25.180 --> 00:12:25.190 align:start position:0%
this problem is amplified by spreading
 

00:12:25.190 --> 00:12:28.750 align:start position:0%
this problem is amplified by spreading
committee<00:12:25.790><c> occurs</c><00:12:26.300><c> different</c><00:12:26.810><c> chart</c><00:12:27.760><c> subnets</c>

00:12:28.750 --> 00:12:28.760 align:start position:0%
committee occurs different chart subnets
 

00:12:28.760 --> 00:12:30.990 align:start position:0%
committee occurs different chart subnets
because<00:12:29.330><c> you</c><00:12:29.630><c> don't</c><00:12:29.810><c> know</c><00:12:29.959><c> how</c><00:12:30.230><c> much</c><00:12:30.440><c> of</c><00:12:30.680><c> the</c>

00:12:30.990 --> 00:12:31.000 align:start position:0%
because you don't know how much of the
 

00:12:31.000 --> 00:12:33.850 align:start position:0%
because you don't know how much of the
participants<00:12:32.000><c> in</c><00:12:32.240><c> your</c><00:12:32.450><c> charts</c><00:12:32.870><c> net</c><00:12:33.170><c> so</c><00:12:33.830><c> you</c>

00:12:33.850 --> 00:12:33.860 align:start position:0%
participants in your charts net so you
 

00:12:33.860 --> 00:12:36.160 align:start position:0%
participants in your charts net so you
don't<00:12:34.160><c> know</c><00:12:34.339><c> how</c><00:12:34.610><c> big</c><00:12:34.910><c> aggregate</c><00:12:35.420><c> you</c><00:12:35.839><c> can</c>

00:12:36.160 --> 00:12:36.170 align:start position:0%
don't know how big aggregate you can
 

00:12:36.170 --> 00:12:39.790 align:start position:0%
don't know how big aggregate you can
combine<00:12:37.839><c> within</c><00:12:38.839><c> the</c><00:12:38.990><c> resources</c><00:12:39.529><c> that</c><00:12:39.680><c> you</c>

00:12:39.790 --> 00:12:39.800 align:start position:0%
combine within the resources that you
 

00:12:39.800 --> 00:12:44.829 align:start position:0%
combine within the resources that you
have<00:12:39.830><c> at</c><00:12:40.400><c> far</c><00:12:40.700><c> so</c><00:12:41.980><c> let's</c><00:12:42.980><c> summarize</c><00:12:43.339><c> that</c><00:12:44.089><c> we</c>

00:12:44.829 --> 00:12:44.839 align:start position:0%
have at far so let's summarize that we
 

00:12:44.839 --> 00:12:47.500 align:start position:0%
have at far so let's summarize that we
have<00:12:45.110><c> to</c><00:12:45.350><c> use</c><00:12:45.529><c> p2p</c><00:12:46.130><c> overlay</c><00:12:46.160><c> to</c><00:12:46.640><c> deliver</c><00:12:47.209><c> at</c><00:12:47.480><c> a</c>

00:12:47.500 --> 00:12:47.510 align:start position:0%
have to use p2p overlay to deliver at a
 

00:12:47.510 --> 00:12:50.650 align:start position:0%
have to use p2p overlay to deliver at a
station<00:12:48.080><c> to</c><00:12:48.260><c> proposer</c><00:12:48.709><c> and</c><00:12:49.160><c> it</c><00:12:49.850><c> scale</c><00:12:50.180><c> it</c><00:12:50.390><c> puts</c>

00:12:50.650 --> 00:12:50.660 align:start position:0%
station to proposer and it scale it puts
 

00:12:50.660 --> 00:12:55.960 align:start position:0%
station to proposer and it scale it puts
some<00:12:50.900><c> big</c><00:12:51.709><c> requirements</c><00:12:52.700><c> to</c><00:12:52.850><c> bandwidth</c><00:12:54.459><c> we</c><00:12:55.459><c> we</c>

00:12:55.960 --> 00:12:55.970 align:start position:0%
some big requirements to bandwidth we we
 

00:12:55.970 --> 00:12:58.449 align:start position:0%
some big requirements to bandwidth we we
are<00:12:56.180><c> considering</c><00:12:56.779><c> a</c><00:12:57.020><c> partial</c><00:12:57.529><c> aggregation</c><00:12:58.220><c> in</c>

00:12:58.449 --> 00:12:58.459 align:start position:0%
are considering a partial aggregation in
 

00:12:58.459 --> 00:13:02.620 align:start position:0%
are considering a partial aggregation in
a<00:12:58.990><c> smaller</c><00:13:00.370><c> overlays</c><00:13:01.370><c> is</c><00:13:01.610><c> a</c><00:13:01.640><c> solution</c><00:13:02.300><c> but</c><00:13:02.480><c> it</c>

00:13:02.620 --> 00:13:02.630 align:start position:0%
a smaller overlays is a solution but it
 

00:13:02.630 --> 00:13:05.949 align:start position:0%
a smaller overlays is a solution but it
have<00:13:02.930><c> a</c><00:13:03.230><c> number</c><00:13:03.829><c> of</c><00:13:04.010><c> complexities</c><00:13:04.750><c> there</c><00:13:05.750><c> is</c>

00:13:05.949 --> 00:13:05.959 align:start position:0%
have a number of complexities there is
 

00:13:05.959 --> 00:13:08.590 align:start position:0%
have a number of complexities there is
also<00:13:06.290><c> another</c><00:13:07.010><c> possible</c><00:13:07.700><c> solution</c><00:13:08.270><c> to</c><00:13:08.300><c> use</c>

00:13:08.590 --> 00:13:08.600 align:start position:0%
also another possible solution to use
 

00:13:08.600 --> 00:13:10.810 align:start position:0%
also another possible solution to use
onion<00:13:09.020><c> wrote</c><00:13:09.290><c> wrote</c><00:13:09.920><c> in</c><00:13:10.130><c> and</c><00:13:10.310><c> similar</c>

00:13:10.810 --> 00:13:10.820 align:start position:0%
onion wrote wrote in and similar
 

00:13:10.820 --> 00:13:15.190 align:start position:0%
onion wrote wrote in and similar
techniques<00:13:11.300><c> but</c><00:13:12.200><c> they</c><00:13:12.380><c> will</c><00:13:12.680><c> bring</c><00:13:13.870><c> their</c><00:13:14.870><c> own</c>

00:13:15.190 --> 00:13:15.200 align:start position:0%
techniques but they will bring their own
 

00:13:15.200 --> 00:13:18.370 align:start position:0%
techniques but they will bring their own
complexity<00:13:16.040><c> as</c><00:13:16.279><c> well</c><00:13:16.820><c> so</c><00:13:17.480><c> need</c><00:13:17.750><c> to</c><00:13:17.899><c> invest</c><00:13:18.230><c> it</c>

00:13:18.370 --> 00:13:18.380 align:start position:0%
complexity as well so need to invest it
 

00:13:18.380 --> 00:13:20.800 align:start position:0%
complexity as well so need to invest it
just<00:13:18.680><c> investigating</c><00:13:19.279><c> that</c><00:13:19.579><c> and</c><00:13:19.850><c> for</c><00:13:20.480><c> a</c><00:13:20.510><c> zero</c>

00:13:20.800 --> 00:13:20.810 align:start position:0%
just investigating that and for a zero
 

00:13:20.810 --> 00:13:23.290 align:start position:0%
just investigating that and for a zero
and<00:13:21.050><c> probably</c><00:13:21.589><c> for</c><00:13:21.829><c> his</c><00:13:21.950><c> one</c><00:13:22.220><c> is</c><00:13:22.430><c> not</c><00:13:22.640><c> affected</c>

00:13:23.290 --> 00:13:23.300 align:start position:0%
and probably for his one is not affected
 

00:13:23.300 --> 00:13:25.290 align:start position:0%
and probably for his one is not affected
because<00:13:23.600><c> it's</c><00:13:24.050><c> not</c>

00:13:25.290 --> 00:13:25.300 align:start position:0%
because it's not
 

00:13:25.300 --> 00:13:28.130 align:start position:0%
because it's not
it's<00:13:25.420><c> not</c><00:13:25.780><c> it's</c><00:13:26.050><c> not</c><00:13:26.110><c> expected</c><00:13:26.650><c> to</c><00:13:26.860><c> have</c><00:13:27.010><c> like</c>

00:13:28.130 --> 00:13:28.140 align:start position:0%
it's not it's not expected to have like
 

00:13:28.140 --> 00:13:33.600 align:start position:0%
it's not it's not expected to have like
big<00:13:29.140><c> amount</c><00:13:29.530><c> of</c><00:13:29.770><c> eath</c><00:13:30.480><c> validating</c><00:13:31.680><c> so</c><00:13:32.680><c> thank</c>

00:13:33.600 --> 00:13:33.610 align:start position:0%
big amount of eath validating so thank
 

00:13:33.610 --> 00:13:35.760 align:start position:0%
big amount of eath validating so thank
you<00:13:33.760><c> so</c><00:13:33.790><c> much</c><00:13:34.180><c> I'm</c><00:13:34.600><c> tom</c>

00:13:35.760 --> 00:13:35.770 align:start position:0%
you so much I'm tom
 

00:13:35.770 --> 00:13:48.130 align:start position:0%
you so much I'm tom
[Applause]

00:13:48.130 --> 00:13:48.140 align:start position:0%
 
 

00:13:48.140 --> 00:13:50.200 align:start position:0%
 
you