WEBVTT
Kind: captions
Language: en

00:00:02.130 --> 00:00:05.550 align:start position:0%
 
[Music]

00:00:05.550 --> 00:00:05.560 align:start position:0%
[Music]
 

00:00:05.560 --> 00:00:07.829 align:start position:0%
[Music]
all<00:00:05.759><c> right</c><00:00:06.680><c> thanks</c><00:00:06.879><c> for</c><00:00:07.040><c> coming</c><00:00:07.359><c> everyone</c><00:00:07.759><c> I</c>

00:00:07.829 --> 00:00:07.839 align:start position:0%
all right thanks for coming everyone I
 

00:00:07.839 --> 00:00:10.629 align:start position:0%
all right thanks for coming everyone I
know<00:00:08.040><c> it's</c><00:00:08.200><c> kind</c><00:00:08.320><c> of</c><00:00:08.440><c> early</c><00:00:09.240><c> so</c><00:00:09.880><c> this</c><00:00:10.120><c> is</c><00:00:10.480><c> a</c>

00:00:10.629 --> 00:00:10.639 align:start position:0%
know it's kind of early so this is a
 

00:00:10.639 --> 00:00:12.430 align:start position:0%
know it's kind of early so this is a
lightning<00:00:11.080><c> talk</c><00:00:11.360><c> on</c><00:00:11.559><c> based</c><00:00:11.880><c> Roll-Ups</c><00:00:12.280><c> and</c>

00:00:12.430 --> 00:00:12.440 align:start position:0%
lightning talk on based Roll-Ups and
 

00:00:12.440 --> 00:00:13.910 align:start position:0%
lightning talk on based Roll-Ups and
pre-ms

00:00:13.910 --> 00:00:13.920 align:start position:0%
pre-ms
 

00:00:13.920 --> 00:00:16.189 align:start position:0%
pre-ms
and<00:00:14.920><c> as</c><00:00:15.000><c> you</c><00:00:15.160><c> know</c><00:00:15.360><c> these</c><00:00:15.519><c> lightning</c><00:00:15.839><c> talks</c>

00:00:16.189 --> 00:00:16.199 align:start position:0%
and as you know these lightning talks
 

00:00:16.199 --> 00:00:18.830 align:start position:0%
and as you know these lightning talks
are<00:00:16.680><c> extremely</c><00:00:17.400><c> quick</c><00:00:17.800><c> so</c><00:00:18.320><c> this</c><00:00:18.439><c> isn't</c><00:00:18.720><c> going</c>

00:00:18.830 --> 00:00:18.840 align:start position:0%
are extremely quick so this isn't going
 

00:00:18.840 --> 00:00:20.150 align:start position:0%
are extremely quick so this isn't going
to<00:00:19.000><c> answer</c><00:00:19.279><c> all</c><00:00:19.400><c> of</c><00:00:19.520><c> the</c><00:00:19.640><c> questions</c><00:00:20.039><c> it's</c>

00:00:20.150 --> 00:00:20.160 align:start position:0%
to answer all of the questions it's
 

00:00:20.160 --> 00:00:21.429 align:start position:0%
to answer all of the questions it's
really<00:00:20.400><c> going</c><00:00:20.560><c> to</c><00:00:20.720><c> try</c><00:00:20.880><c> and</c><00:00:21.000><c> lay</c><00:00:21.240><c> the</c>

00:00:21.429 --> 00:00:21.439 align:start position:0%
really going to try and lay the
 

00:00:21.439 --> 00:00:24.189 align:start position:0%
really going to try and lay the
foundation<00:00:22.439><c> and</c><00:00:22.640><c> motivation</c><00:00:23.240><c> for</c><00:00:23.560><c> why</c><00:00:24.039><c> um</c>

00:00:24.189 --> 00:00:24.199 align:start position:0%
foundation and motivation for why um
 

00:00:24.199 --> 00:00:27.349 align:start position:0%
foundation and motivation for why um
different<00:00:24.439><c> teams</c><00:00:24.680><c> are</c><00:00:24.840><c> working</c><00:00:25.119><c> on</c><00:00:25.359><c> this</c><00:00:26.320><c> so</c><00:00:27.160><c> I</c>

00:00:27.349 --> 00:00:27.359 align:start position:0%
different teams are working on this so I
 

00:00:27.359 --> 00:00:28.910 align:start position:0%
different teams are working on this so I
I<00:00:27.400><c> would</c><00:00:27.519><c> want</c><00:00:27.640><c> to</c><00:00:27.800><c> start</c><00:00:28.039><c> with</c><00:00:28.240><c> like</c><00:00:28.599><c> what</c><00:00:28.720><c> is</c>

00:00:28.910 --> 00:00:28.920 align:start position:0%
I would want to start with like what is
 

00:00:28.920 --> 00:00:30.710 align:start position:0%
I would want to start with like what is
the<00:00:29.039><c> big</c><00:00:29.240><c> motivation</c><00:00:29.759><c> here</c>

00:00:30.710 --> 00:00:30.720 align:start position:0%
the big motivation here
 

00:00:30.720 --> 00:00:32.830 align:start position:0%
the big motivation here
um<00:00:30.880><c> and</c><00:00:31.279><c> the</c><00:00:31.439><c> big</c><00:00:31.759><c> goal</c><00:00:32.239><c> of</c><00:00:32.399><c> these</c><00:00:32.559><c> based</c>

00:00:32.830 --> 00:00:32.840 align:start position:0%
um and the big goal of these based
 

00:00:32.840 --> 00:00:34.990 align:start position:0%
um and the big goal of these based
rollups<00:00:33.360><c> really</c><00:00:33.600><c> is</c><00:00:33.719><c> to</c><00:00:34.000><c> help</c><00:00:34.399><c> solve</c><00:00:34.840><c> this</c>

00:00:34.990 --> 00:00:35.000 align:start position:0%
rollups really is to help solve this
 

00:00:35.000 --> 00:00:36.709 align:start position:0%
rollups really is to help solve this
fragmentation<00:00:35.800><c> issue</c><00:00:36.120><c> we're</c><00:00:36.280><c> starting</c><00:00:36.559><c> to</c>

00:00:36.709 --> 00:00:36.719 align:start position:0%
fragmentation issue we're starting to
 

00:00:36.719 --> 00:00:39.670 align:start position:0%
fragmentation issue we're starting to
see<00:00:37.120><c> in</c><00:00:37.280><c> the</c><00:00:37.399><c> L2</c><00:00:37.960><c> space</c><00:00:38.640><c> and</c><00:00:38.760><c> to</c><00:00:39.000><c> restore</c><00:00:39.399><c> some</c>

00:00:39.670 --> 00:00:39.680 align:start position:0%
see in the L2 space and to restore some
 

00:00:39.680 --> 00:00:42.709 align:start position:0%
see in the L2 space and to restore some
value<00:00:40.039><c> capture</c><00:00:40.480><c> back</c><00:00:40.600><c> to</c><00:00:40.760><c> the</c><00:00:40.879><c> base</c><00:00:41.360><c> layer</c><00:00:42.360><c> so</c>

00:00:42.709 --> 00:00:42.719 align:start position:0%
value capture back to the base layer so
 

00:00:42.719 --> 00:00:45.790 align:start position:0%
value capture back to the base layer so
how<00:00:42.879><c> did</c><00:00:43.039><c> we</c><00:00:43.200><c> get</c><00:00:43.480><c> here</c><00:00:44.440><c> well</c><00:00:45.239><c> ethereum</c><00:00:45.680><c> is</c>

00:00:45.790 --> 00:00:45.800 align:start position:0%
how did we get here well ethereum is
 

00:00:45.800 --> 00:00:47.750 align:start position:0%
how did we get here well ethereum is
always<00:00:46.039><c> in</c><00:00:46.160><c> this</c><00:00:46.320><c> tricky</c><00:00:46.719><c> position</c><00:00:47.520><c> um</c><00:00:47.640><c> the</c>

00:00:47.750 --> 00:00:47.760 align:start position:0%
always in this tricky position um the
 

00:00:47.760 --> 00:00:49.830 align:start position:0%
always in this tricky position um the
goalposts<00:00:48.360><c> always</c><00:00:48.600><c> move</c><00:00:49.199><c> gas</c><00:00:49.440><c> was</c><00:00:49.600><c> too</c>

00:00:49.830 --> 00:00:49.840 align:start position:0%
goalposts always move gas was too
 

00:00:49.840 --> 00:00:52.229 align:start position:0%
goalposts always move gas was too
expensive<00:00:50.760><c> we</c><00:00:50.920><c> created</c><00:00:51.280><c> this</c><00:00:51.440><c> rollup</c><00:00:51.840><c> Centric</c>

00:00:52.229 --> 00:00:52.239 align:start position:0%
expensive we created this rollup Centric
 

00:00:52.239 --> 00:00:55.430 align:start position:0%
expensive we created this rollup Centric
road<00:00:52.520><c> map</c><00:00:53.280><c> we</c><00:00:53.559><c> succeeded</c><00:00:54.480><c> in</c><00:00:54.719><c> offloading</c><00:00:55.320><c> all</c>

00:00:55.430 --> 00:00:55.440 align:start position:0%
road map we succeeded in offloading all
 

00:00:55.440 --> 00:00:58.590 align:start position:0%
road map we succeeded in offloading all
of<00:00:55.559><c> this</c><00:00:56.000><c> execution</c><00:00:57.000><c> things</c><00:00:57.239><c> got</c><00:00:57.440><c> cheaper</c><00:00:58.039><c> TPS</c>

00:00:58.590 --> 00:00:58.600 align:start position:0%
of this execution things got cheaper TPS
 

00:00:58.600 --> 00:01:03.470 align:start position:0%
of this execution things got cheaper TPS
increased<00:00:59.519><c> but</c><00:01:00.039><c> eth</c><00:01:00.320><c> is</c><00:01:00.519><c> dead</c><00:01:01.879><c> so</c><00:01:02.879><c> we</c><00:01:03.079><c> really</c>

00:01:03.470 --> 00:01:03.480 align:start position:0%
increased but eth is dead so we really
 

00:01:03.480 --> 00:01:05.109 align:start position:0%
increased but eth is dead so we really
want<00:01:03.640><c> to</c><00:01:03.800><c> try</c><00:01:03.960><c> and</c><00:01:04.320><c> address</c><00:01:04.640><c> some</c><00:01:04.760><c> of</c><00:01:04.920><c> these</c>

00:01:05.109 --> 00:01:05.119 align:start position:0%
want to try and address some of these
 

00:01:05.119 --> 00:01:07.749 align:start position:0%
want to try and address some of these
problems<00:01:05.479><c> headon</c><00:01:06.439><c> and</c><00:01:06.960><c> the</c><00:01:07.119><c> big</c><00:01:07.360><c> focus</c><00:01:07.640><c> of</c>

00:01:07.749 --> 00:01:07.759 align:start position:0%
problems headon and the big focus of
 

00:01:07.759 --> 00:01:09.910 align:start position:0%
problems headon and the big focus of
this<00:01:07.960><c> talk</c><00:01:08.159><c> is</c><00:01:08.320><c> around</c><00:01:08.640><c> fragmentation</c><00:01:09.640><c> So</c>

00:01:09.910 --> 00:01:09.920 align:start position:0%
this talk is around fragmentation So
 

00:01:09.920 --> 00:01:12.789 align:start position:0%
this talk is around fragmentation So
currently<00:01:10.520><c> these</c><00:01:10.759><c> l2s</c><00:01:11.759><c> aren't</c><00:01:12.080><c> interoperable</c>

00:01:12.789 --> 00:01:12.799 align:start position:0%
currently these l2s aren't interoperable
 

00:01:12.799 --> 00:01:15.149 align:start position:0%
currently these l2s aren't interoperable
with<00:01:12.920><c> each</c><00:01:13.080><c> other</c><00:01:13.799><c> they</c><00:01:14.119><c> fragment</c><00:01:14.600><c> liquidity</c>

00:01:15.149 --> 00:01:15.159 align:start position:0%
with each other they fragment liquidity
 

00:01:15.159 --> 00:01:17.550 align:start position:0%
with each other they fragment liquidity
they<00:01:15.320><c> fragment</c><00:01:15.720><c> users</c><00:01:16.640><c> they</c><00:01:16.799><c> also</c><00:01:17.040><c> fragment</c>

00:01:17.550 --> 00:01:17.560 align:start position:0%
they fragment users they also fragment
 

00:01:17.560 --> 00:01:19.830 align:start position:0%
they fragment users they also fragment
developers<00:01:18.360><c> you</c><00:01:18.560><c> have</c><00:01:18.680><c> to</c><00:01:18.960><c> pick</c><00:01:19.320><c> a</c><00:01:19.439><c> winning</c>

00:01:19.830 --> 00:01:19.840 align:start position:0%
developers you have to pick a winning
 

00:01:19.840 --> 00:01:22.310 align:start position:0%
developers you have to pick a winning
ecosystem<00:01:20.560><c> to</c><00:01:20.759><c> deploy</c><00:01:21.159><c> on</c><00:01:21.439><c> or</c><00:01:21.640><c> deploy</c><00:01:22.000><c> across</c>

00:01:22.310 --> 00:01:22.320 align:start position:0%
ecosystem to deploy on or deploy across
 

00:01:22.320 --> 00:01:24.630 align:start position:0%
ecosystem to deploy on or deploy across
many<00:01:23.040><c> which</c><00:01:23.159><c> starts</c><00:01:23.479><c> to</c><00:01:23.600><c> spread</c><00:01:23.960><c> your</c>

00:01:24.630 --> 00:01:24.640 align:start position:0%
many which starts to spread your
 

00:01:24.640 --> 00:01:27.590 align:start position:0%
many which starts to spread your
resources<00:01:25.640><c> and</c><00:01:26.439><c> what</c><00:01:26.600><c> we're</c><00:01:26.840><c> really</c><00:01:27.079><c> seeing</c>

00:01:27.590 --> 00:01:27.600 align:start position:0%
resources and what we're really seeing
 

00:01:27.600 --> 00:01:30.230 align:start position:0%
resources and what we're really seeing
is<00:01:27.880><c> this</c><00:01:28.439><c> kind</c><00:01:28.560><c> of</c><00:01:28.960><c> convergence</c><00:01:29.520><c> on</c><00:01:30.000><c> what</c><00:01:30.119><c> I'm</c>

00:01:30.230 --> 00:01:30.240 align:start position:0%
is this kind of convergence on what I'm
 

00:01:30.240 --> 00:01:31.950 align:start position:0%
is this kind of convergence on what I'm
calling<00:01:30.600><c> intraop</c><00:01:31.479><c> you</c><00:01:31.680><c> have</c>

00:01:31.950 --> 00:01:31.960 align:start position:0%
calling intraop you have
 

00:01:31.960 --> 00:01:34.190 align:start position:0%
calling intraop you have
interoperability<00:01:32.920><c> within</c><00:01:33.240><c> your</c><00:01:33.520><c> ecosystem</c>

00:01:34.190 --> 00:01:34.200 align:start position:0%
interoperability within your ecosystem
 

00:01:34.200 --> 00:01:35.789 align:start position:0%
interoperability within your ecosystem
but<00:01:34.360><c> not</c><00:01:34.640><c> across</c><00:01:35.079><c> these</c>

00:01:35.789 --> 00:01:35.799 align:start position:0%
but not across these
 

00:01:35.799 --> 00:01:38.429 align:start position:0%
but not across these
ecosystems<00:01:36.799><c> so</c><00:01:37.479><c> how</c><00:01:37.560><c> do</c><00:01:37.720><c> we</c><00:01:38.000><c> fix</c><00:01:38.320><c> this</c>

00:01:38.429 --> 00:01:38.439 align:start position:0%
ecosystems so how do we fix this
 

00:01:38.439 --> 00:01:41.429 align:start position:0%
ecosystems so how do we fix this
fragmentation<00:01:39.240><c> problem</c><00:01:40.079><c> well</c><00:01:40.799><c> one</c><00:01:41.119><c> easy</c>

00:01:41.429 --> 00:01:41.439 align:start position:0%
fragmentation problem well one easy
 

00:01:41.439 --> 00:01:43.590 align:start position:0%
fragmentation problem well one easy
solution<00:01:42.159><c> is</c><00:01:42.320><c> that</c><00:01:42.479><c> we</c><00:01:42.640><c> just</c><00:01:42.840><c> agree</c><00:01:43.159><c> on</c><00:01:43.360><c> one</c>

00:01:43.590 --> 00:01:43.600 align:start position:0%
solution is that we just agree on one
 

00:01:43.600 --> 00:01:46.550 align:start position:0%
solution is that we just agree on one
entity<00:01:44.200><c> to</c><00:01:44.399><c> sequence</c><00:01:44.920><c> all</c><00:01:45.040><c> of</c><00:01:45.159><c> these</c><00:01:45.560><c> rollups</c>

00:01:46.550 --> 00:01:46.560 align:start position:0%
entity to sequence all of these rollups
 

00:01:46.560 --> 00:01:49.709 align:start position:0%
entity to sequence all of these rollups
and<00:01:47.240><c> that</c><00:01:47.360><c> sounds</c><00:01:47.719><c> pretty</c><00:01:48.040><c> centralizing</c><00:01:48.960><c> so</c>

00:01:49.709 --> 00:01:49.719 align:start position:0%
and that sounds pretty centralizing so
 

00:01:49.719 --> 00:01:52.149 align:start position:0%
and that sounds pretty centralizing so
can<00:01:49.920><c> we</c><00:01:50.079><c> do</c><00:01:50.320><c> this</c><00:01:50.719><c> in</c><00:01:51.040><c> a</c><00:01:51.240><c> way</c><00:01:51.439><c> that</c><00:01:51.600><c> preserves</c><00:01:52.079><c> a</c>

00:01:52.149 --> 00:01:52.159 align:start position:0%
can we do this in a way that preserves a
 

00:01:52.159 --> 00:01:54.630 align:start position:0%
can we do this in a way that preserves a
lot<00:01:52.280><c> of</c><00:01:52.360><c> the</c><00:01:52.479><c> values</c><00:01:52.799><c> that</c><00:01:52.920><c> we</c><00:01:53.040><c> care</c><00:01:53.399><c> about</c><00:01:54.399><c> so</c>

00:01:54.630 --> 00:01:54.640 align:start position:0%
lot of the values that we care about so
 

00:01:54.640 --> 00:01:58.029 align:start position:0%
lot of the values that we care about so
enter<00:01:54.960><c> based</c><00:01:55.360><c> rollups</c><00:01:56.360><c> the</c><00:01:56.560><c> idea</c><00:01:56.960><c> here</c><00:01:57.759><c> um</c>

00:01:58.029 --> 00:01:58.039 align:start position:0%
enter based rollups the idea here um
 

00:01:58.039 --> 00:02:00.350 align:start position:0%
enter based rollups the idea here um
this<00:01:58.159><c> is</c><00:01:58.280><c> a</c><00:01:58.399><c> quote</c><00:01:58.640><c> from</c><00:01:58.799><c> Justin's</c><00:01:59.320><c> paper</c>

00:02:00.350 --> 00:02:00.360 align:start position:0%
this is a quote from Justin's paper
 

00:02:00.360 --> 00:02:03.510 align:start position:0%
this is a quote from Justin's paper
um<00:02:00.560><c> the</c><00:02:00.680><c> tldr</c><00:02:01.439><c> here</c><00:02:01.640><c> is</c><00:02:02.159><c> it's</c><00:02:02.280><c> a</c><00:02:02.439><c> based</c><00:02:02.680><c> rollup</c>

00:02:03.510 --> 00:02:03.520 align:start position:0%
um the tldr here is it's a based rollup
 

00:02:03.520 --> 00:02:06.350 align:start position:0%
um the tldr here is it's a based rollup
when<00:02:03.759><c> it's</c><00:02:04.000><c> sequenced</c><00:02:04.719><c> by</c><00:02:05.039><c> ethereum</c>

00:02:06.350 --> 00:02:06.360 align:start position:0%
when it's sequenced by ethereum
 

00:02:06.360 --> 00:02:09.869 align:start position:0%
when it's sequenced by ethereum
validators<00:02:07.360><c> so</c><00:02:07.880><c> in</c><00:02:08.080><c> this</c><00:02:08.399><c> picture</c><00:02:09.399><c> on</c><00:02:09.599><c> the</c>

00:02:09.869 --> 00:02:09.879 align:start position:0%
validators so in this picture on the
 

00:02:09.879 --> 00:02:12.589 align:start position:0%
validators so in this picture on the
left<00:02:10.160><c> hand</c><00:02:10.399><c> side</c><00:02:10.679><c> here</c><00:02:10.920><c> we</c><00:02:11.160><c> have</c><00:02:12.000><c> centralized</c>

00:02:12.589 --> 00:02:12.599 align:start position:0%
left hand side here we have centralized
 

00:02:12.599 --> 00:02:14.630 align:start position:0%
left hand side here we have centralized
sequencing<00:02:13.440><c> the</c><00:02:13.599><c> idea</c><00:02:13.920><c> is</c><00:02:14.160><c> you</c><00:02:14.319><c> have</c><00:02:14.480><c> these</c>

00:02:14.630 --> 00:02:14.640 align:start position:0%
sequencing the idea is you have these
 

00:02:14.640 --> 00:02:16.470 align:start position:0%
sequencing the idea is you have these
unordered<00:02:15.120><c> transactions</c><00:02:15.879><c> a</c><00:02:16.000><c> centralized</c>

00:02:16.470 --> 00:02:16.480 align:start position:0%
unordered transactions a centralized
 

00:02:16.480 --> 00:02:19.229 align:start position:0%
unordered transactions a centralized
sequencer<00:02:17.160><c> job</c><00:02:17.400><c> is</c><00:02:17.560><c> to</c><00:02:17.840><c> order</c><00:02:18.239><c> them</c><00:02:18.840><c> for</c><00:02:19.080><c> the</c>

00:02:19.229 --> 00:02:19.239 align:start position:0%
sequencer job is to order them for the
 

00:02:19.239 --> 00:02:21.550 align:start position:0%
sequencer job is to order them for the
rollup<00:02:20.160><c> um</c><00:02:20.360><c> these</c><00:02:20.599><c> little</c><00:02:20.879><c> squiggly</c><00:02:21.400><c> things</c>

00:02:21.550 --> 00:02:21.560 align:start position:0%
rollup um these little squiggly things
 

00:02:21.560 --> 00:02:24.270 align:start position:0%
rollup um these little squiggly things
are<00:02:21.680><c> the</c><00:02:21.800><c> Roll-Ups</c><00:02:22.120><c> at</c><00:02:22.239><c> the</c><00:02:22.360><c> bottom</c><00:02:22.640><c> here</c><00:02:23.480><c> okay</c>

00:02:24.270 --> 00:02:24.280 align:start position:0%
are the Roll-Ups at the bottom here okay
 

00:02:24.280 --> 00:02:26.710 align:start position:0%
are the Roll-Ups at the bottom here okay
as<00:02:24.400><c> we</c><00:02:24.599><c> move</c><00:02:24.840><c> to</c><00:02:25.040><c> the</c><00:02:25.200><c> right</c><00:02:25.760><c> we're</c><00:02:26.080><c> increasing</c>

00:02:26.710 --> 00:02:26.720 align:start position:0%
as we move to the right we're increasing
 

00:02:26.720 --> 00:02:28.910 align:start position:0%
as we move to the right we're increasing
in<00:02:27.040><c> decentralization</c><00:02:28.040><c> and</c><00:02:28.160><c> we're</c><00:02:28.400><c> unlocking</c>

00:02:28.910 --> 00:02:28.920 align:start position:0%
in decentralization and we're unlocking
 

00:02:28.920 --> 00:02:30.710 align:start position:0%
in decentralization and we're unlocking
interoperability

00:02:30.710 --> 00:02:30.720 align:start position:0%
interoperability
 

00:02:30.720 --> 00:02:33.309 align:start position:0%
interoperability
so<00:02:31.720><c> with</c><00:02:31.879><c> shared</c><00:02:32.280><c> sequencing</c><00:02:32.920><c> you</c><00:02:33.080><c> have</c>

00:02:33.309 --> 00:02:33.319 align:start position:0%
so with shared sequencing you have
 

00:02:33.319 --> 00:02:36.470 align:start position:0%
so with shared sequencing you have
multiple<00:02:33.800><c> parties</c><00:02:34.440><c> that</c><00:02:34.560><c> are</c><00:02:34.800><c> all</c><00:02:35.560><c> agreeing</c>

00:02:36.470 --> 00:02:36.480 align:start position:0%
multiple parties that are all agreeing
 

00:02:36.480 --> 00:02:38.509 align:start position:0%
multiple parties that are all agreeing
According<00:02:36.840><c> to</c><00:02:37.040><c> some</c><00:02:37.319><c> leader</c><00:02:37.720><c> election</c>

00:02:38.509 --> 00:02:38.519 align:start position:0%
According to some leader election
 

00:02:38.519 --> 00:02:42.149 align:start position:0%
According to some leader election
mechanism<00:02:39.519><c> on</c><00:02:39.840><c> who</c><00:02:40.239><c> has</c><00:02:41.040><c> the</c><00:02:41.239><c> ability</c><00:02:41.640><c> to</c>

00:02:42.149 --> 00:02:42.159 align:start position:0%
mechanism on who has the ability to
 

00:02:42.159 --> 00:02:43.790 align:start position:0%
mechanism on who has the ability to
sequence<00:02:42.720><c> all</c><00:02:42.879><c> of</c><00:02:43.000><c> the</c>

00:02:43.790 --> 00:02:43.800 align:start position:0%
sequence all of the
 

00:02:43.800 --> 00:02:46.350 align:start position:0%
sequence all of the
rollups<00:02:44.800><c> and</c><00:02:45.080><c> as</c><00:02:45.200><c> we</c><00:02:45.400><c> move</c><00:02:45.879><c> all</c><00:02:46.000><c> the</c><00:02:46.080><c> way</c><00:02:46.239><c> to</c>

00:02:46.350 --> 00:02:46.360 align:start position:0%
rollups and as we move all the way to
 

00:02:46.360 --> 00:02:48.830 align:start position:0%
rollups and as we move all the way to
the<00:02:46.560><c> right</c><00:02:47.080><c> we</c><00:02:47.239><c> enter</c><00:02:47.680><c> this</c><00:02:47.879><c> based</c><00:02:48.280><c> sequencing</c>

00:02:48.830 --> 00:02:48.840 align:start position:0%
the right we enter this based sequencing
 

00:02:48.840 --> 00:02:51.550 align:start position:0%
the right we enter this based sequencing
mode<00:02:49.560><c> the</c><00:02:49.760><c> idea</c><00:02:50.120><c> is</c><00:02:50.319><c> that</c><00:02:50.760><c> the</c><00:02:50.959><c> transactions</c>

00:02:51.550 --> 00:02:51.560 align:start position:0%
mode the idea is that the transactions
 

00:02:51.560 --> 00:02:54.350 align:start position:0%
mode the idea is that the transactions
for<00:02:51.800><c> these</c><00:02:51.920><c> l2s</c><00:02:52.519><c> will</c><00:02:52.680><c> be</c><00:02:52.840><c> sequenced</c><00:02:53.720><c> directly</c>

00:02:54.350 --> 00:02:54.360 align:start position:0%
for these l2s will be sequenced directly
 

00:02:54.360 --> 00:02:55.710 align:start position:0%
for these l2s will be sequenced directly
by<00:02:54.599><c> ethereum</c>

00:02:55.710 --> 00:02:55.720 align:start position:0%
by ethereum
 

00:02:55.720 --> 00:02:58.390 align:start position:0%
by ethereum
validators<00:02:56.720><c> and</c><00:02:57.360><c> how</c><00:02:57.519><c> does</c><00:02:57.720><c> this</c><00:02:57.959><c> help</c><00:02:58.280><c> how</c>

00:02:58.390 --> 00:02:58.400 align:start position:0%
validators and how does this help how
 

00:02:58.400 --> 00:03:00.509 align:start position:0%
validators and how does this help how
does<00:02:58.560><c> this</c><00:02:58.720><c> unlock</c><00:02:59.080><c> interoperability</c>

00:03:00.509 --> 00:03:00.519 align:start position:0%
does this unlock interoperability
 

00:03:00.519 --> 00:03:03.670 align:start position:0%
does this unlock interoperability
the<00:03:00.680><c> idea</c><00:03:01.120><c> is</c><00:03:01.519><c> that</c><00:03:02.519><c> we</c><00:03:02.800><c> have</c><00:03:03.080><c> these</c><00:03:03.360><c> right</c>

00:03:03.670 --> 00:03:03.680 align:start position:0%
the idea is that we have these right
 

00:03:03.680 --> 00:03:07.670 align:start position:0%
the idea is that we have these right
locks<00:03:04.480><c> over</c><00:03:05.040><c> L2</c><00:03:05.720><c> State</c><00:03:06.720><c> when</c><00:03:06.920><c> an</c><00:03:07.080><c> ethereum</c>

00:03:07.670 --> 00:03:07.680 align:start position:0%
locks over L2 State when an ethereum
 

00:03:07.680 --> 00:03:09.630 align:start position:0%
locks over L2 State when an ethereum
validator<00:03:08.239><c> is</c><00:03:08.360><c> going</c><00:03:08.519><c> to</c><00:03:08.720><c> propose</c><00:03:09.040><c> a</c><00:03:09.159><c> block</c>

00:03:09.630 --> 00:03:09.640 align:start position:0%
validator is going to propose a block
 

00:03:09.640 --> 00:03:11.430 align:start position:0%
validator is going to propose a block
they<00:03:09.799><c> have</c><00:03:09.959><c> a</c><00:03:10.120><c> right</c><00:03:10.360><c> lock</c><00:03:10.680><c> over</c><00:03:10.920><c> the</c><00:03:11.080><c> entire</c>

00:03:11.430 --> 00:03:11.440 align:start position:0%
they have a right lock over the entire
 

00:03:11.440 --> 00:03:14.949 align:start position:0%
they have a right lock over the entire
L1<00:03:11.920><c> block</c><00:03:12.760><c> and</c><00:03:13.120><c> all</c><00:03:13.280><c> of</c><00:03:13.480><c> the</c><00:03:13.959><c> L2</c><00:03:14.440><c> blocks</c><00:03:14.840><c> that</c>

00:03:14.949 --> 00:03:14.959 align:start position:0%
L1 block and all of the L2 blocks that
 

00:03:14.959 --> 00:03:18.949 align:start position:0%
L1 block and all of the L2 blocks that
are<00:03:15.120><c> going</c><00:03:15.239><c> to</c><00:03:15.400><c> be</c><00:03:16.159><c> included</c><00:03:17.159><c> and</c><00:03:17.799><c> when</c><00:03:18.319><c> we</c>

00:03:18.949 --> 00:03:18.959 align:start position:0%
are going to be included and when we
 

00:03:18.959 --> 00:03:21.470 align:start position:0%
are going to be included and when we
have<00:03:19.560><c> a</c><00:03:19.720><c> bunch</c><00:03:19.959><c> of</c><00:03:20.159><c> rollups</c><00:03:20.879><c> that</c><00:03:21.000><c> are</c><00:03:21.200><c> all</c>

00:03:21.470 --> 00:03:21.480 align:start position:0%
have a bunch of rollups that are all
 

00:03:21.480 --> 00:03:23.550 align:start position:0%
have a bunch of rollups that are all
agreeing<00:03:21.920><c> to</c><00:03:22.040><c> be</c><00:03:22.200><c> sequenced</c><00:03:22.799><c> by</c><00:03:23.040><c> this</c>

00:03:23.550 --> 00:03:23.560 align:start position:0%
agreeing to be sequenced by this
 

00:03:23.560 --> 00:03:26.030 align:start position:0%
agreeing to be sequenced by this
validator<00:03:24.560><c> it</c><00:03:24.720><c> unlocks</c><00:03:25.239><c> this</c><00:03:25.440><c> ability</c><00:03:25.840><c> for</c>

00:03:26.030 --> 00:03:26.040 align:start position:0%
validator it unlocks this ability for
 

00:03:26.040 --> 00:03:28.869 align:start position:0%
validator it unlocks this ability for
you<00:03:26.200><c> to</c><00:03:26.400><c> start</c><00:03:27.040><c> passing</c><00:03:27.440><c> messages</c><00:03:28.159><c> across</c>

00:03:28.869 --> 00:03:28.879 align:start position:0%
you to start passing messages across
 

00:03:28.879 --> 00:03:30.670 align:start position:0%
you to start passing messages across
these<00:03:29.040><c> rollups</c><00:03:29.879><c> we</c><00:03:30.000><c> don't</c><00:03:30.200><c> need</c><00:03:30.480><c> these</c>

00:03:30.670 --> 00:03:30.680 align:start position:0%
these rollups we don't need these
 

00:03:30.680 --> 00:03:33.309 align:start position:0%
these rollups we don't need these
Bridges<00:03:31.360><c> we're</c><00:03:31.560><c> able</c><00:03:31.799><c> to</c><00:03:31.920><c> do</c><00:03:32.159><c> these</c><00:03:32.360><c> more</c>

00:03:33.309 --> 00:03:33.319 align:start position:0%
Bridges we're able to do these more
 

00:03:33.319 --> 00:03:35.990 align:start position:0%
Bridges we're able to do these more
seamlessly<00:03:34.319><c> so</c><00:03:35.040><c> this</c><00:03:35.239><c> has</c>

00:03:35.990 --> 00:03:36.000 align:start position:0%
seamlessly so this has
 

00:03:36.000 --> 00:03:38.149 align:start position:0%
seamlessly so this has
limitations<00:03:37.000><c> um</c><00:03:37.200><c> one</c><00:03:37.319><c> of</c><00:03:37.439><c> the</c><00:03:37.560><c> big</c><00:03:37.879><c> issues</c>

00:03:38.149 --> 00:03:38.159 align:start position:0%
limitations um one of the big issues
 

00:03:38.159 --> 00:03:40.830 align:start position:0%
limitations um one of the big issues
with<00:03:38.319><c> based</c><00:03:38.560><c> Roll-Ups</c><00:03:39.159><c> is</c><00:03:39.319><c> that</c><00:03:39.519><c> they</c><00:03:39.760><c> have</c><00:03:40.640><c> um</c>

00:03:40.830 --> 00:03:40.840 align:start position:0%
with based Roll-Ups is that they have um
 

00:03:40.840 --> 00:03:43.550 align:start position:0%
with based Roll-Ups is that they have um
really<00:03:41.480><c> 12C</c><00:03:42.040><c> block</c><00:03:42.360><c> times</c><00:03:42.920><c> a</c><00:03:43.040><c> lot</c><00:03:43.159><c> of</c><00:03:43.280><c> users</c>

00:03:43.550 --> 00:03:43.560 align:start position:0%
really 12C block times a lot of users
 

00:03:43.560 --> 00:03:45.550 align:start position:0%
really 12C block times a lot of users
want<00:03:43.680><c> to</c><00:03:43.799><c> come</c><00:03:43.920><c> to</c><00:03:44.080><c> l2s</c><00:03:44.680><c> because</c><00:03:45.000><c> they</c><00:03:45.400><c> they</c>

00:03:45.550 --> 00:03:45.560 align:start position:0%
want to come to l2s because they they
 

00:03:45.560 --> 00:03:48.229 align:start position:0%
want to come to l2s because they they
care<00:03:45.840><c> about</c><00:03:46.120><c> that</c><00:03:46.239><c> snapy</c><00:03:46.760><c> ux</c><00:03:47.239><c> those</c><00:03:47.480><c> instant</c>

00:03:48.229 --> 00:03:48.239 align:start position:0%
care about that snapy ux those instant
 

00:03:48.239 --> 00:03:51.630 align:start position:0%
care about that snapy ux those instant
transactions<00:03:49.239><c> we</c><00:03:49.360><c> can</c><00:03:49.599><c> always</c><00:03:50.599><c> reduce</c><00:03:51.120><c> the</c><00:03:51.239><c> L1</c>

00:03:51.630 --> 00:03:51.640 align:start position:0%
transactions we can always reduce the L1
 

00:03:51.640 --> 00:03:54.149 align:start position:0%
transactions we can always reduce the L1
block<00:03:51.920><c> times</c><00:03:52.360><c> but</c><00:03:52.560><c> that's</c><00:03:53.079><c> a</c><00:03:53.280><c> very</c><00:03:53.560><c> long</c>

00:03:54.149 --> 00:03:54.159 align:start position:0%
block times but that's a very long
 

00:03:54.159 --> 00:03:56.229 align:start position:0%
block times but that's a very long
arduous<00:03:54.720><c> process</c><00:03:55.360><c> that</c><00:03:55.560><c> has</c><00:03:55.840><c> a</c><00:03:55.959><c> lot</c><00:03:56.079><c> of</c>

00:03:56.229 --> 00:03:56.239 align:start position:0%
arduous process that has a lot of
 

00:03:56.239 --> 00:03:59.830 align:start position:0%
arduous process that has a lot of
unknowns<00:03:56.720><c> and</c><00:03:56.920><c> centralization</c><00:03:57.799><c> vectors</c><00:03:58.799><c> so</c>

00:03:59.830 --> 00:03:59.840 align:start position:0%
unknowns and centralization vectors so
 

00:03:59.840 --> 00:04:02.309 align:start position:0%
unknowns and centralization vectors so
proms<00:04:00.760><c> this</c><00:04:00.879><c> is</c><00:04:01.040><c> another</c><00:04:01.319><c> one</c><00:04:01.400><c> of</c><00:04:01.599><c> these</c><00:04:02.200><c> um</c>

00:04:02.309 --> 00:04:02.319 align:start position:0%
proms this is another one of these um
 

00:04:02.319 --> 00:04:04.670 align:start position:0%
proms this is another one of these um
new<00:04:02.680><c> terms</c><00:04:03.680><c> that</c><00:04:03.840><c> stands</c><00:04:04.079><c> for</c><00:04:04.280><c> pre-</c>

00:04:04.670 --> 00:04:04.680 align:start position:0%
new terms that stands for pre-
 

00:04:04.680 --> 00:04:07.470 align:start position:0%
new terms that stands for pre-
confirmations<00:04:05.680><c> a</c><00:04:05.840><c> pre-com</c><00:04:06.439><c> is</c><00:04:06.760><c> a</c><00:04:06.959><c> commitment</c>

00:04:07.470 --> 00:04:07.480 align:start position:0%
confirmations a pre-com is a commitment
 

00:04:07.480 --> 00:04:10.910 align:start position:0%
confirmations a pre-com is a commitment
made<00:04:07.920><c> by</c><00:04:08.079><c> these</c><00:04:08.400><c> validators</c><00:04:09.400><c> um</c><00:04:09.519><c> to</c><00:04:09.920><c> users</c>

00:04:10.910 --> 00:04:10.920 align:start position:0%
made by these validators um to users
 

00:04:10.920 --> 00:04:13.670 align:start position:0%
made by these validators um to users
about<00:04:11.480><c> doing</c><00:04:11.879><c> something</c><00:04:12.319><c> related</c><00:04:12.680><c> to</c><00:04:13.280><c> block</c>

00:04:13.670 --> 00:04:13.680 align:start position:0%
about doing something related to block
 

00:04:13.680 --> 00:04:16.550 align:start position:0%
about doing something related to block
proposals<00:04:14.680><c> so</c><00:04:15.040><c> this</c><00:04:15.200><c> could</c><00:04:15.360><c> mean</c><00:04:16.120><c> I'm</c><00:04:16.320><c> giving</c>

00:04:16.550 --> 00:04:16.560 align:start position:0%
proposals so this could mean I'm giving
 

00:04:16.560 --> 00:04:18.909 align:start position:0%
proposals so this could mean I'm giving
a<00:04:16.840><c> guarantee</c><00:04:17.280><c> to</c><00:04:17.440><c> a</c><00:04:17.560><c> user</c><00:04:18.120><c> that</c><00:04:18.239><c> I'll</c><00:04:18.519><c> include</c>

00:04:18.909 --> 00:04:18.919 align:start position:0%
a guarantee to a user that I'll include
 

00:04:18.919 --> 00:04:21.110 align:start position:0%
a guarantee to a user that I'll include
their<00:04:19.120><c> transaction</c><00:04:19.799><c> when</c><00:04:19.959><c> it's</c><00:04:20.160><c> my</c><00:04:20.359><c> turn</c><00:04:20.880><c> to</c>

00:04:21.110 --> 00:04:21.120 align:start position:0%
their transaction when it's my turn to
 

00:04:21.120 --> 00:04:23.390 align:start position:0%
their transaction when it's my turn to
propose<00:04:21.479><c> the</c><00:04:21.639><c> block</c><00:04:22.400><c> or</c><00:04:22.560><c> I</c><00:04:22.639><c> can</c><00:04:22.840><c> even</c><00:04:23.040><c> give</c><00:04:23.160><c> a</c>

00:04:23.390 --> 00:04:23.400 align:start position:0%
propose the block or I can even give a
 

00:04:23.400 --> 00:04:26.270 align:start position:0%
propose the block or I can even give a
stronger<00:04:23.759><c> guarantee</c><00:04:24.400><c> like</c><00:04:24.880><c> this</c><00:04:25.040><c> will</c><00:04:25.240><c> be</c><00:04:25.720><c> the</c>

00:04:26.270 --> 00:04:26.280 align:start position:0%
stronger guarantee like this will be the
 

00:04:26.280 --> 00:04:29.390 align:start position:0%
stronger guarantee like this will be the
state<00:04:27.000><c> after</c><00:04:27.320><c> executing</c><00:04:27.840><c> your</c><00:04:28.400><c> transaction</c>

00:04:29.390 --> 00:04:29.400 align:start position:0%
state after executing your transaction
 

00:04:29.400 --> 00:04:31.469 align:start position:0%
state after executing your transaction
and<00:04:29.600><c> if</c><00:04:29.720><c> if</c><00:04:29.840><c> I</c><00:04:29.960><c> break</c><00:04:30.240><c> my</c><00:04:30.440><c> promise</c><00:04:30.880><c> as</c><00:04:31.039><c> the</c>

00:04:31.469 --> 00:04:31.479 align:start position:0%
and if if I break my promise as the
 

00:04:31.479 --> 00:04:36.350 align:start position:0%
and if if I break my promise as the
preuner<00:04:32.479><c> then</c><00:04:32.919><c> I</c><00:04:33.039><c> can</c><00:04:33.240><c> get</c><00:04:33.400><c> slashed</c><00:04:34.360><c> um</c><00:04:34.759><c> on</c><00:04:35.759><c> um</c>

00:04:36.350 --> 00:04:36.360 align:start position:0%
preuner then I can get slashed um on um
 

00:04:36.360 --> 00:04:37.749 align:start position:0%
preuner then I can get slashed um on um
various

00:04:37.749 --> 00:04:37.759 align:start position:0%
various
 

00:04:37.759 --> 00:04:40.590 align:start position:0%
various
means<00:04:38.759><c> so</c><00:04:39.199><c> to</c><00:04:39.560><c> kind</c><00:04:39.639><c> of</c><00:04:39.800><c> wrap</c><00:04:40.120><c> this</c><00:04:40.240><c> up</c><00:04:40.479><c> like</c>

00:04:40.590 --> 00:04:40.600 align:start position:0%
means so to kind of wrap this up like
 

00:04:40.600 --> 00:04:42.390 align:start position:0%
means so to kind of wrap this up like
how<00:04:40.759><c> does</c><00:04:40.919><c> this</c><00:04:41.039><c> all</c><00:04:41.240><c> come</c><00:04:41.520><c> together</c><00:04:42.000><c> so</c><00:04:42.280><c> the</c>

00:04:42.390 --> 00:04:42.400 align:start position:0%
how does this all come together so the
 

00:04:42.400 --> 00:04:44.629 align:start position:0%
how does this all come together so the
user<00:04:42.919><c> over</c><00:04:43.199><c> here</c><00:04:43.800><c> would</c><00:04:43.960><c> be</c><00:04:44.080><c> able</c><00:04:44.280><c> to</c><00:04:44.400><c> send</c>

00:04:44.629 --> 00:04:44.639 align:start position:0%
user over here would be able to send
 

00:04:44.639 --> 00:04:46.270 align:start position:0%
user over here would be able to send
their<00:04:44.759><c> rollup</c><00:04:45.160><c> transactions</c><00:04:45.960><c> to</c><00:04:46.120><c> be</c>

00:04:46.270 --> 00:04:46.280 align:start position:0%
their rollup transactions to be
 

00:04:46.280 --> 00:04:50.270 align:start position:0%
their rollup transactions to be
sequenced<00:04:46.960><c> by</c><00:04:47.479><c> an</c><00:04:47.639><c> ethereum</c><00:04:48.639><c> validator</c><00:04:49.639><c> they</c>

00:04:50.270 --> 00:04:50.280 align:start position:0%
sequenced by an ethereum validator they
 

00:04:50.280 --> 00:04:52.310 align:start position:0%
sequenced by an ethereum validator they
in<00:04:50.680><c> response</c><00:04:51.520><c> give</c><00:04:51.840><c> back</c><00:04:52.120><c> this</c>

00:04:52.310 --> 00:04:52.320 align:start position:0%
in response give back this
 

00:04:52.320 --> 00:04:53.670 align:start position:0%
in response give back this
pre-confirmation

00:04:53.670 --> 00:04:53.680 align:start position:0%
pre-confirmation
 

00:04:53.680 --> 00:04:55.990 align:start position:0%
pre-confirmation
signature<00:04:54.680><c> um</c><00:04:54.840><c> which</c><00:04:54.960><c> is</c><00:04:55.160><c> like</c><00:04:55.320><c> this</c><00:04:55.520><c> receipt</c>

00:04:55.990 --> 00:04:56.000 align:start position:0%
signature um which is like this receipt
 

00:04:56.000 --> 00:04:58.189 align:start position:0%
signature um which is like this receipt
for<00:04:56.240><c> the</c><00:04:56.360><c> users</c><00:04:57.039><c> guaranteeing</c><00:04:57.759><c> that</c><00:04:57.960><c> their</c>

00:04:58.189 --> 00:04:58.199 align:start position:0%
for the users guaranteeing that their
 

00:04:58.199 --> 00:05:00.790 align:start position:0%
for the users guaranteeing that their
transaction<00:04:58.759><c> will</c><00:04:58.919><c> be</c><00:04:59.360><c> in</c><00:04:59.680><c> included</c><00:05:00.199><c> or</c><00:05:00.560><c> it'll</c>

00:05:00.790 --> 00:05:00.800 align:start position:0%
transaction will be in included or it'll
 

00:05:00.800 --> 00:05:04.749 align:start position:0%
transaction will be in included or it'll
be<00:05:01.160><c> executed</c><00:05:02.160><c> um</c><00:05:02.360><c> inside</c><00:05:02.680><c> of</c><00:05:02.800><c> the</c><00:05:03.000><c> rollup</c><00:05:04.000><c> and</c>

00:05:04.749 --> 00:05:04.759 align:start position:0%
be executed um inside of the rollup and
 

00:05:04.759 --> 00:05:07.790 align:start position:0%
be executed um inside of the rollup and
if<00:05:05.039><c> the</c><00:05:05.320><c> validator</c><00:05:05.880><c> does</c><00:05:06.120><c> break</c><00:05:06.400><c> this</c><00:05:06.800><c> promise</c>

00:05:07.790 --> 00:05:07.800 align:start position:0%
if the validator does break this promise
 

00:05:07.800 --> 00:05:09.909 align:start position:0%
if the validator does break this promise
they<00:05:07.919><c> can</c><00:05:08.680><c> be</c><00:05:08.840><c> slashed</c><00:05:09.360><c> by</c><00:05:09.479><c> submitting</c>

00:05:09.909 --> 00:05:09.919 align:start position:0%
they can be slashed by submitting
 

00:05:09.919 --> 00:05:12.909 align:start position:0%
they can be slashed by submitting
evidence<00:05:10.240><c> to</c><00:05:10.400><c> the</c><00:05:10.520><c> slashing</c><00:05:11.240><c> contract</c><00:05:12.240><c> and</c>

00:05:12.909 --> 00:05:12.919 align:start position:0%
evidence to the slashing contract and
 

00:05:12.919 --> 00:05:15.150 align:start position:0%
evidence to the slashing contract and
what<00:05:13.080><c> does</c><00:05:13.280><c> this</c><00:05:13.479><c> enable</c><00:05:14.120><c> well</c><00:05:14.560><c> it</c><00:05:14.680><c> solves</c><00:05:15.080><c> a</c>

00:05:15.150 --> 00:05:15.160 align:start position:0%
what does this enable well it solves a
 

00:05:15.160 --> 00:05:16.990 align:start position:0%
what does this enable well it solves a
lot<00:05:15.320><c> of</c><00:05:15.440><c> these</c><00:05:15.680><c> ux</c><00:05:16.080><c> problems</c><00:05:16.600><c> and</c><00:05:16.720><c> when</c><00:05:16.880><c> we</c>

00:05:16.990 --> 00:05:17.000 align:start position:0%
lot of these ux problems and when we
 

00:05:17.000 --> 00:05:20.510 align:start position:0%
lot of these ux problems and when we
start<00:05:17.240><c> to</c><00:05:17.400><c> enter</c><00:05:17.919><c> this</c><00:05:18.680><c> like</c><00:05:19.520><c> execution</c><00:05:20.160><c> prec</c>

00:05:20.510 --> 00:05:20.520 align:start position:0%
start to enter this like execution prec
 

00:05:20.520 --> 00:05:23.309 align:start position:0%
start to enter this like execution prec
comps<00:05:21.240><c> we</c><00:05:21.680><c> we</c><00:05:21.919><c> really</c><00:05:22.280><c> make</c><00:05:22.440><c> it</c><00:05:22.600><c> to</c><00:05:22.800><c> a</c><00:05:23.080><c> place</c>

00:05:23.309 --> 00:05:23.319 align:start position:0%
comps we we really make it to a place
 

00:05:23.319 --> 00:05:26.029 align:start position:0%
comps we we really make it to a place
where<00:05:23.479><c> we</c><00:05:23.680><c> can</c><00:05:23.919><c> actually</c><00:05:24.880><c> outperform</c><00:05:25.880><c> um</c>

00:05:26.029 --> 00:05:26.039 align:start position:0%
where we can actually outperform um
 

00:05:26.039 --> 00:05:28.430 align:start position:0%
where we can actually outperform um
these<00:05:26.199><c> alt</c><00:05:26.479><c> l1s</c><00:05:27.319><c> by</c><00:05:27.479><c> giving</c><00:05:27.840><c> these</c><00:05:28.080><c> very</c>

00:05:28.430 --> 00:05:28.440 align:start position:0%
these alt l1s by giving these very
 

00:05:28.440 --> 00:05:30.950 align:start position:0%
these alt l1s by giving these very
instant<00:05:28.919><c> transactions</c><00:05:29.720><c> back</c><00:05:29.840><c> to</c><00:05:29.960><c> users</c><00:05:30.800><c> and</c>

00:05:30.950 --> 00:05:30.960 align:start position:0%
instant transactions back to users and
 

00:05:30.960 --> 00:05:33.270 align:start position:0%
instant transactions back to users and
this<00:05:31.160><c> all</c><00:05:31.440><c> comes</c><00:05:31.800><c> without</c><00:05:32.160><c> modifications</c><00:05:33.039><c> to</c>

00:05:33.270 --> 00:05:33.280 align:start position:0%
this all comes without modifications to
 

00:05:33.280 --> 00:05:37.390 align:start position:0%
this all comes without modifications to
the<00:05:33.400><c> Bas</c><00:05:33.840><c> layer</c><00:05:34.840><c> so</c><00:05:35.720><c> hopefully</c><00:05:36.479><c> this</c><00:05:37.120><c> maybe</c>

00:05:37.390 --> 00:05:37.400 align:start position:0%
the Bas layer so hopefully this maybe
 

00:05:37.400 --> 00:05:39.990 align:start position:0%
the Bas layer so hopefully this maybe
peaked<00:05:37.919><c> people's</c><00:05:38.360><c> interest</c><00:05:38.759><c> on</c><00:05:39.039><c> this</c><00:05:39.280><c> topic</c>

00:05:39.990 --> 00:05:40.000 align:start position:0%
peaked people's interest on this topic
 

00:05:40.000 --> 00:05:42.150 align:start position:0%
peaked people's interest on this topic
um<00:05:40.199><c> but</c><00:05:40.680><c> of</c><00:05:40.800><c> course</c><00:05:41.080><c> in</c><00:05:41.240><c> a</c><00:05:41.479><c> in</c><00:05:41.560><c> a</c><00:05:41.759><c> five</c><00:05:41.919><c> minute</c>

00:05:42.150 --> 00:05:42.160 align:start position:0%
um but of course in a in a five minute
 

00:05:42.160 --> 00:05:44.189 align:start position:0%
um but of course in a in a five minute
lightning<00:05:42.479><c> talk</c><00:05:42.919><c> that's</c><00:05:43.360><c> uh</c><00:05:43.720><c> there's</c><00:05:43.960><c> still</c>

00:05:44.189 --> 00:05:44.199 align:start position:0%
lightning talk that's uh there's still
 

00:05:44.199 --> 00:05:46.510 align:start position:0%
lightning talk that's uh there's still
many<00:05:44.520><c> many</c><00:05:44.759><c> things</c><00:05:44.919><c> to</c><00:05:45.039><c> be</c><00:05:45.240><c> explored</c><00:05:45.800><c> so</c><00:05:46.360><c> thank</c>

00:05:46.510 --> 00:05:46.520 align:start position:0%
many many things to be explored so thank
 

00:05:46.520 --> 00:05:50.260 align:start position:0%
many many things to be explored so thank
you<00:05:46.639><c> all</c><00:05:46.800><c> for</c>

00:05:50.260 --> 00:05:50.270 align:start position:0%
 
 

00:05:50.270 --> 00:05:56.510 align:start position:0%
 
[Music]

00:05:56.510 --> 00:05:56.520 align:start position:0%
 
 

00:05:56.520 --> 00:05:58.749 align:start position:0%
 
joining<00:05:57.520><c> okay</c><00:05:57.759><c> yeah</c><00:05:58.120><c> we</c><00:05:58.240><c> have</c><00:05:58.400><c> a</c><00:05:58.520><c> few</c>

00:05:58.749 --> 00:05:58.759 align:start position:0%
joining okay yeah we have a few
 

00:05:58.759 --> 00:06:01.189 align:start position:0%
joining okay yeah we have a few
questions<00:05:59.440><c> um</c>

00:06:01.189 --> 00:06:01.199 align:start position:0%
questions um
 

00:06:01.199 --> 00:06:02.550 align:start position:0%
questions um
right<00:06:01.400><c> yeah</c><00:06:01.520><c> so</c><00:06:01.720><c> the</c><00:06:01.880><c> the</c><00:06:02.000><c> first</c><00:06:02.240><c> question</c>

00:06:02.550 --> 00:06:02.560 align:start position:0%
right yeah so the the first question
 

00:06:02.560 --> 00:06:04.950 align:start position:0%
right yeah so the the first question
here<00:06:02.759><c> how</c><00:06:02.880><c> does</c><00:06:03.039><c> this</c><00:06:03.199><c> notion</c><00:06:03.680><c> scale</c><00:06:04.680><c> um</c><00:06:04.840><c> if</c>

00:06:04.950 --> 00:06:04.960 align:start position:0%
here how does this notion scale um if
 

00:06:04.960 --> 00:06:07.110 align:start position:0%
here how does this notion scale um if
they<00:06:05.120><c> need</c><00:06:05.319><c> to</c><00:06:06.039><c> validate</c><00:06:06.400><c> all</c><00:06:06.560><c> of</c><00:06:06.639><c> the</c><00:06:06.720><c> L2</c>

00:06:07.110 --> 00:06:07.120 align:start position:0%
they need to validate all of the L2
 

00:06:07.120 --> 00:06:09.150 align:start position:0%
they need to validate all of the L2
transactions<00:06:07.880><c> so</c><00:06:08.160><c> this</c><00:06:08.240><c> is</c><00:06:08.360><c> a</c><00:06:08.520><c> great</c><00:06:08.759><c> question</c>

00:06:09.150 --> 00:06:09.160 align:start position:0%
transactions so this is a great question
 

00:06:09.160 --> 00:06:11.230 align:start position:0%
transactions so this is a great question
so<00:06:09.759><c> I</c><00:06:09.840><c> think</c><00:06:10.039><c> there's</c><00:06:10.400><c> kind</c><00:06:10.520><c> of</c><00:06:10.720><c> Two</c><00:06:11.039><c> Two</c>

00:06:11.230 --> 00:06:11.240 align:start position:0%
so I think there's kind of Two Two
 

00:06:11.240 --> 00:06:13.589 align:start position:0%
so I think there's kind of Two Two
Worlds<00:06:11.680><c> here</c><00:06:11.919><c> like</c><00:06:12.120><c> one</c><00:06:12.360><c> is</c><00:06:12.919><c> sequencing</c>

00:06:13.589 --> 00:06:13.599 align:start position:0%
Worlds here like one is sequencing
 

00:06:13.599 --> 00:06:16.150 align:start position:0%
Worlds here like one is sequencing
itself<00:06:14.199><c> doesn't</c><00:06:14.560><c> imply</c><00:06:15.039><c> execution</c><00:06:15.840><c> so</c><00:06:16.039><c> it</c>

00:06:16.150 --> 00:06:16.160 align:start position:0%
itself doesn't imply execution so it
 

00:06:16.160 --> 00:06:18.749 align:start position:0%
itself doesn't imply execution so it
doesn't<00:06:16.520><c> have</c><00:06:16.639><c> to</c><00:06:17.240><c> take</c><00:06:17.400><c> on</c><00:06:17.720><c> all</c><00:06:17.880><c> of</c><00:06:18.000><c> the</c><00:06:18.160><c> load</c>

00:06:18.749 --> 00:06:18.759 align:start position:0%
doesn't have to take on all of the load
 

00:06:18.759 --> 00:06:21.110 align:start position:0%
doesn't have to take on all of the load
but<00:06:19.479><c> realistically</c><00:06:20.479><c> there's</c><00:06:20.840><c> different</c>

00:06:21.110 --> 00:06:21.120 align:start position:0%
but realistically there's different
 

00:06:21.120 --> 00:06:23.270 align:start position:0%
but realistically there's different
implementations<00:06:21.880><c> of</c><00:06:22.120><c> these</c><00:06:22.520><c> um</c><00:06:22.639><c> pre-com</c>

00:06:23.270 --> 00:06:23.280 align:start position:0%
implementations of these um pre-com
 

00:06:23.280 --> 00:06:25.510 align:start position:0%
implementations of these um pre-com
protocols<00:06:23.759><c> being</c><00:06:23.960><c> built</c><00:06:24.840><c> some</c><00:06:25.000><c> of</c><00:06:25.199><c> them</c>

00:06:25.510 --> 00:06:25.520 align:start position:0%
protocols being built some of them
 

00:06:25.520 --> 00:06:29.150 align:start position:0%
protocols being built some of them
offload<00:06:26.240><c> this</c><00:06:26.400><c> duty</c><00:06:27.199><c> to</c><00:06:27.919><c> um</c><00:06:28.160><c> these</c><00:06:28.639><c> kind</c><00:06:28.800><c> of</c>

00:06:29.150 --> 00:06:29.160 align:start position:0%
offload this duty to um these kind of
 

00:06:29.160 --> 00:06:30.909 align:start position:0%
offload this duty to um these kind of
Gateway<00:06:29.800><c> is</c><00:06:29.919><c> what</c><00:06:30.000><c> they're</c><00:06:30.199><c> called</c><00:06:30.560><c> similar</c>

00:06:30.909 --> 00:06:30.919 align:start position:0%
Gateway is what they're called similar
 

00:06:30.919 --> 00:06:34.670 align:start position:0%
Gateway is what they're called similar
to<00:06:31.120><c> the</c><00:06:31.400><c> PBS</c><00:06:31.880><c> pipeline</c><00:06:32.280><c> we</c><00:06:32.400><c> see</c>

00:06:34.670 --> 00:06:34.680 align:start position:0%
 
 

00:06:34.680 --> 00:06:36.950 align:start position:0%
 
today<00:06:35.680><c> um</c><00:06:35.919><c> second</c><00:06:36.240><c> question</c>

00:06:36.950 --> 00:06:36.960 align:start position:0%
today um second question
 

00:06:36.960 --> 00:06:39.070 align:start position:0%
today um second question
pre-confirmation<00:06:37.440><c> Services</c><00:06:38.319><c> seem</c><00:06:38.560><c> to</c><00:06:38.680><c> be</c><00:06:38.960><c> the</c>

00:06:39.070 --> 00:06:39.080 align:start position:0%
pre-confirmation Services seem to be the
 

00:06:39.080 --> 00:06:41.550 align:start position:0%
pre-confirmation Services seem to be the
biggest<00:06:39.360><c> layer</c><00:06:39.599><c> of</c><00:06:39.759><c> complexity</c><00:06:40.280><c> for</c><00:06:40.440><c> me</c><00:06:41.360><c> um</c>

00:06:41.550 --> 00:06:41.560 align:start position:0%
biggest layer of complexity for me um
 

00:06:41.560 --> 00:06:43.110 align:start position:0%
biggest layer of complexity for me um
these<00:06:41.720><c> pre-comp</c><00:06:42.199><c> networks</c><00:06:42.599><c> will</c><00:06:42.800><c> likely</c>

00:06:43.110 --> 00:06:43.120 align:start position:0%
these pre-comp networks will likely
 

00:06:43.120 --> 00:06:44.830 align:start position:0%
these pre-comp networks will likely
require<00:06:43.520><c> consensus</c><00:06:44.120><c> is</c><00:06:44.240><c> this</c><00:06:44.400><c> the</c><00:06:44.520><c> biggest</c>

00:06:44.830 --> 00:06:44.840 align:start position:0%
require consensus is this the biggest
 

00:06:44.840 --> 00:06:48.230 align:start position:0%
require consensus is this the biggest
drawback<00:06:46.080><c> so</c><00:06:47.080><c> definitely</c><00:06:47.560><c> over</c><00:06:47.759><c> the</c><00:06:47.960><c> past</c>

00:06:48.230 --> 00:06:48.240 align:start position:0%
drawback so definitely over the past
 

00:06:48.240 --> 00:06:51.469 align:start position:0%
drawback so definitely over the past
year<00:06:49.120><c> like</c><00:06:50.120><c> it's</c><00:06:50.360><c> been</c><00:06:50.639><c> it</c><00:06:50.759><c> started</c><00:06:51.120><c> from</c><00:06:51.319><c> this</c>

00:06:51.469 --> 00:06:51.479 align:start position:0%
year like it's been it started from this
 

00:06:51.479 --> 00:06:54.309 align:start position:0%
year like it's been it started from this
like<00:06:51.680><c> very</c><00:06:52.160><c> dark</c><00:06:52.400><c> Forest</c><00:06:52.840><c> unknown</c><00:06:53.400><c> and</c><00:06:54.039><c> over</c>

00:06:54.309 --> 00:06:54.319 align:start position:0%
like very dark Forest unknown and over
 

00:06:54.319 --> 00:06:57.110 align:start position:0%
like very dark Forest unknown and over
time<00:06:54.599><c> we've</c><00:06:54.840><c> started</c><00:06:55.120><c> to</c><00:06:55.680><c> untangle</c><00:06:56.240><c> it</c><00:06:56.680><c> and</c>

00:06:57.110 --> 00:06:57.120 align:start position:0%
time we've started to untangle it and
 

00:06:57.120 --> 00:06:58.950 align:start position:0%
time we've started to untangle it and
some<00:06:57.240><c> of</c><00:06:57.400><c> the</c><00:06:57.560><c> bigger</c><00:06:58.080><c> questions</c><00:06:58.440><c> are</c><00:06:58.680><c> now</c>

00:06:58.950 --> 00:06:58.960 align:start position:0%
some of the bigger questions are now
 

00:06:58.960 --> 00:07:01.430 align:start position:0%
some of the bigger questions are now
just<00:06:59.120><c> around</c><00:06:59.599><c> pricing</c><00:07:00.280><c> but</c><00:07:00.520><c> really</c><00:07:01.039><c> you</c><00:07:01.199><c> don't</c>

00:07:01.430 --> 00:07:01.440 align:start position:0%
just around pricing but really you don't
 

00:07:01.440 --> 00:07:04.110 align:start position:0%
just around pricing but really you don't
need<00:07:01.800><c> an</c><00:07:02.039><c> actual</c><00:07:02.520><c> consensus</c><00:07:03.160><c> protocol</c><00:07:03.879><c> to</c>

00:07:04.110 --> 00:07:04.120 align:start position:0%
need an actual consensus protocol to
 

00:07:04.120 --> 00:07:06.189 align:start position:0%
need an actual consensus protocol to
build<00:07:04.440><c> this</c><00:07:05.120><c> um</c><00:07:05.400><c> you're</c><00:07:05.639><c> able</c><00:07:05.840><c> to</c><00:07:06.039><c> just</c>

00:07:06.189 --> 00:07:06.199 align:start position:0%
build this um you're able to just
 

00:07:06.199 --> 00:07:08.589 align:start position:0%
build this um you're able to just
broadcast<00:07:07.120><c> like</c><00:07:07.599><c> these</c><00:07:07.800><c> messages</c><00:07:08.240><c> directly</c>

00:07:08.589 --> 00:07:08.599 align:start position:0%
broadcast like these messages directly
 

00:07:08.599 --> 00:07:10.629 align:start position:0%
broadcast like these messages directly
to<00:07:08.720><c> the</c><00:07:08.840><c> users</c><00:07:09.280><c> and</c><00:07:09.520><c> if</c><00:07:09.639><c> the</c><00:07:09.759><c> user</c><00:07:10.520><c> like</c>

00:07:10.629 --> 00:07:10.639 align:start position:0%
to the users and if the user like
 

00:07:10.639 --> 00:07:11.749 align:start position:0%
to the users and if the user like
doesn't<00:07:10.960><c> get</c><00:07:11.080><c> their</c><00:07:11.240><c> pre-confirmation</c>

00:07:11.749 --> 00:07:11.759 align:start position:0%
doesn't get their pre-confirmation
 

00:07:11.759 --> 00:07:14.350 align:start position:0%
doesn't get their pre-confirmation
they're<00:07:12.240><c> able</c><00:07:12.440><c> to</c><00:07:12.639><c> go</c><00:07:12.759><c> and</c>

00:07:14.350 --> 00:07:14.360 align:start position:0%
they're able to go and
 

00:07:14.360 --> 00:07:17.550 align:start position:0%
they're able to go and
slash<00:07:15.360><c> okay</c><00:07:15.599><c> maybe</c><00:07:16.000><c> one</c><00:07:16.280><c> last</c><00:07:16.720><c> question</c><00:07:17.319><c> why</c>

00:07:17.550 --> 00:07:17.560 align:start position:0%
slash okay maybe one last question why
 

00:07:17.560 --> 00:07:20.629 align:start position:0%
slash okay maybe one last question why
is<00:07:18.400><c> Spire</c><00:07:18.840><c> better</c><00:07:19.120><c> than</c><00:07:19.360><c> puffer</c><00:07:20.039><c> why</c><00:07:20.160><c> is</c><00:07:20.319><c> Spire</c>

00:07:20.629 --> 00:07:20.639 align:start position:0%
is Spire better than puffer why is Spire
 

00:07:20.639 --> 00:07:23.550 align:start position:0%
is Spire better than puffer why is Spire
better<00:07:20.840><c> than</c><00:07:21.000><c> puffer</c><00:07:21.879><c> well</c><00:07:22.879><c> um</c><00:07:23.120><c> we're</c><00:07:23.280><c> all</c>

00:07:23.550 --> 00:07:23.560 align:start position:0%
better than puffer well um we're all
 

00:07:23.560 --> 00:07:31.390 align:start position:0%
better than puffer well um we're all
here<00:07:23.919><c> building</c><00:07:24.360><c> based</c><00:07:24.639><c> rollups</c><00:07:25.199><c> so</c><00:07:26.080><c> um</c>

00:07:31.390 --> 00:07:31.400 align:start position:0%
 
 

00:07:31.400 --> 00:07:34.350 align:start position:0%
 
yeah<00:07:32.400><c> I</c><00:07:32.560><c> I</c><00:07:32.960><c> understand</c><00:07:33.520><c> so</c><00:07:33.800><c> everyone</c><00:07:34.199><c> has</c>

00:07:34.350 --> 00:07:34.360 align:start position:0%
yeah I I understand so everyone has
 

00:07:34.360 --> 00:07:36.550 align:start position:0%
yeah I I understand so everyone has
their<00:07:34.560><c> own</c><00:07:34.800><c> vision</c><00:07:35.160><c> for</c><00:07:35.400><c> the</c><00:07:35.560><c> best</c><00:07:35.879><c> approach</c>

00:07:36.550 --> 00:07:36.560 align:start position:0%
their own vision for the best approach
 

00:07:36.560 --> 00:07:40.790 align:start position:0%
their own vision for the best approach
thank<00:07:36.720><c> you</c><00:07:36.879><c> very</c><00:07:37.080><c> much</c><00:07:38.440><c> so</c><00:07:39.440><c> thank</c><00:07:39.599><c> you</c><00:07:40.160><c> please</c>

00:07:40.790 --> 00:07:40.800 align:start position:0%
thank you very much so thank you please
 

00:07:40.800 --> 00:07:45.000 align:start position:0%
thank you very much so thank you please
give<00:07:40.919><c> a</c><00:07:41.080><c> round</c><00:07:41.280><c> of</c><00:07:41.440><c> applause</c><00:07:41.720><c> to</c><00:07:41.800><c> our</c><00:07:42.000><c> speaker</c>