WEBVTT
Kind: captions
Language: en

00:00:00.000 --> 00:00:04.350 align:start position:0%
 
foreign

00:00:04.350 --> 00:00:04.360 align:start position:0%
 
 

00:00:04.360 --> 00:00:13.690 align:start position:0%
 
[Music]

00:00:13.690 --> 00:00:13.700 align:start position:0%
 
 

00:00:13.700 --> 00:00:16.129 align:start position:0%
 
and<00:00:14.700><c> this</c><00:00:14.820><c> is</c><00:00:14.940><c> John</c><00:00:15.179><c> and</c><00:00:15.719><c> we're</c><00:00:15.900><c> going</c><00:00:16.020><c> to</c><00:00:16.080><c> be</c>

00:00:16.129 --> 00:00:16.139 align:start position:0%
and this is John and we're going to be
 

00:00:16.139 --> 00:00:17.630 align:start position:0%
and this is John and we're going to be
talking<00:00:16.320><c> about</c><00:00:16.500><c> succinct</c><00:00:16.980><c> verification</c><00:00:17.400><c> of</c>

00:00:17.630 --> 00:00:17.640 align:start position:0%
talking about succinct verification of
 

00:00:17.640 --> 00:00:19.550 align:start position:0%
talking about succinct verification of
consensus<00:00:18.119><c> as</c>

00:00:19.550 --> 00:00:19.560 align:start position:0%
consensus as
 

00:00:19.560 --> 00:00:22.070 align:start position:0%
consensus as
um<00:00:19.680><c> and</c><00:00:20.039><c> we're</c><00:00:20.220><c> part</c><00:00:20.400><c> of</c><00:00:20.520><c> succinct</c><00:00:20.939><c> labs</c>

00:00:22.070 --> 00:00:22.080 align:start position:0%
um and we're part of succinct labs
 

00:00:22.080 --> 00:00:24.109 align:start position:0%
um and we're part of succinct labs
okay<00:00:22.500><c> so</c><00:00:22.800><c> let's</c><00:00:23.039><c> just</c><00:00:23.220><c> start</c><00:00:23.400><c> with</c><00:00:23.699><c> the</c><00:00:23.820><c> super</c>

00:00:24.109 --> 00:00:24.119 align:start position:0%
okay so let's just start with the super
 

00:00:24.119 --> 00:00:25.849 align:start position:0%
okay so let's just start with the super
high<00:00:24.359><c> overview</c><00:00:24.840><c> of</c><00:00:25.019><c> the</c><00:00:25.199><c> multi-chain</c><00:00:25.680><c> and</c>

00:00:25.849 --> 00:00:25.859 align:start position:0%
high overview of the multi-chain and
 

00:00:25.859 --> 00:00:28.250 align:start position:0%
high overview of the multi-chain and
costume<00:00:26.279><c> landscape</c><00:00:26.820><c> so</c><00:00:27.599><c> in</c><00:00:27.840><c> the</c><00:00:27.960><c> past</c><00:00:28.080><c> few</c>

00:00:28.250 --> 00:00:28.260 align:start position:0%
costume landscape so in the past few
 

00:00:28.260 --> 00:00:30.410 align:start position:0%
costume landscape so in the past few
years<00:00:28.500><c> a</c><00:00:28.800><c> bunch</c><00:00:28.920><c> of</c><00:00:29.039><c> different</c><00:00:29.160><c> l1s</c><00:00:29.820><c> and</c><00:00:29.880><c> l2s</c>

00:00:30.410 --> 00:00:30.420 align:start position:0%
years a bunch of different l1s and l2s
 

00:00:30.420 --> 00:00:33.229 align:start position:0%
years a bunch of different l1s and l2s
and<00:00:30.539><c> app</c><00:00:30.660><c> chains</c><00:00:31.080><c> have</c><00:00:31.260><c> come</c><00:00:31.500><c> online</c><00:00:32.000><c> and</c><00:00:33.000><c> they</c>

00:00:33.229 --> 00:00:33.239 align:start position:0%
and app chains have come online and they
 

00:00:33.239 --> 00:00:34.790 align:start position:0%
and app chains have come online and they
all<00:00:33.540><c> lie</c><00:00:33.840><c> on</c><00:00:33.960><c> very</c><00:00:34.079><c> different</c><00:00:34.200><c> points</c><00:00:34.559><c> of</c><00:00:34.680><c> the</c>

00:00:34.790 --> 00:00:34.800 align:start position:0%
all lie on very different points of the
 

00:00:34.800 --> 00:00:35.690 align:start position:0%
all lie on very different points of the
trade-off<00:00:35.040><c> curve</c><00:00:35.280><c> in</c><00:00:35.460><c> terms</c><00:00:35.640><c> of</c>

00:00:35.690 --> 00:00:35.700 align:start position:0%
trade-off curve in terms of
 

00:00:35.700 --> 00:00:38.330 align:start position:0%
trade-off curve in terms of
decentralization<00:00:36.300><c> security</c><00:00:37.340><c> transaction</c>

00:00:38.330 --> 00:00:38.340 align:start position:0%
decentralization security transaction
 

00:00:38.340 --> 00:00:40.369 align:start position:0%
decentralization security transaction
cost<00:00:39.000><c> and</c><00:00:39.239><c> throughput</c>

00:00:40.369 --> 00:00:40.379 align:start position:0%
cost and throughput
 

00:00:40.379 --> 00:00:42.110 align:start position:0%
cost and throughput
but<00:00:41.100><c> basically</c><00:00:41.520><c> as</c><00:00:41.700><c> the</c><00:00:41.879><c> number</c><00:00:42.000><c> of</c>

00:00:42.110 --> 00:00:42.120 align:start position:0%
but basically as the number of
 

00:00:42.120 --> 00:00:44.690 align:start position:0%
but basically as the number of
applications<00:00:42.660><c> on</c><00:00:43.620><c> these</c><00:00:43.860><c> different</c><00:00:43.980><c> l1s</c><00:00:44.640><c> and</c>

00:00:44.690 --> 00:00:44.700 align:start position:0%
applications on these different l1s and
 

00:00:44.700 --> 00:00:47.630 align:start position:0%
applications on these different l1s and
l2s<00:00:45.239><c> has</c><00:00:45.420><c> increased</c><00:00:45.899><c> uh</c><00:00:46.800><c> it's</c><00:00:47.040><c> important</c><00:00:47.280><c> that</c>

00:00:47.630 --> 00:00:47.640 align:start position:0%
l2s has increased uh it's important that
 

00:00:47.640 --> 00:00:49.490 align:start position:0%
l2s has increased uh it's important that
users<00:00:47.940><c> are</c><00:00:48.059><c> able</c><00:00:48.300><c> to</c><00:00:48.420><c> interact</c><00:00:48.840><c> between</c><00:00:49.140><c> these</c>

00:00:49.490 --> 00:00:49.500 align:start position:0%
users are able to interact between these
 

00:00:49.500 --> 00:00:51.110 align:start position:0%
users are able to interact between these
different<00:00:49.620><c> applications</c><00:00:50.100><c> and</c><00:00:50.820><c> in</c><00:00:51.000><c> this</c>

00:00:51.110 --> 00:00:51.120 align:start position:0%
different applications and in this
 

00:00:51.120 --> 00:00:53.090 align:start position:0%
different applications and in this
future<00:00:51.360><c> in</c><00:00:51.840><c> the</c><00:00:51.960><c> multi-chain</c><00:00:52.320><c> future</c><00:00:52.559><c> Bridges</c>

00:00:53.090 --> 00:00:53.100 align:start position:0%
future in the multi-chain future Bridges
 

00:00:53.100 --> 00:00:55.010 align:start position:0%
future in the multi-chain future Bridges
have<00:00:53.280><c> become</c><00:00:53.520><c> critical</c><00:00:53.879><c> infrastructure</c><00:00:54.539><c> to</c>

00:00:55.010 --> 00:00:55.020 align:start position:0%
have become critical infrastructure to
 

00:00:55.020 --> 00:00:56.869 align:start position:0%
have become critical infrastructure to
make<00:00:55.140><c> blockchains</c><00:00:55.739><c> interoperable</c><00:00:56.280><c> it's</c>

00:00:56.869 --> 00:00:56.879 align:start position:0%
make blockchains interoperable it's
 

00:00:56.879 --> 00:00:59.029 align:start position:0%
make blockchains interoperable it's
really<00:00:57.059><c> important</c><00:00:57.360><c> that</c><00:00:57.660><c> users</c><00:00:58.079><c> funds</c><00:00:58.739><c> and</c>

00:00:59.029 --> 00:00:59.039 align:start position:0%
really important that users funds and
 

00:00:59.039 --> 00:01:00.950 align:start position:0%
really important that users funds and
assets<00:00:59.460><c> are</c><00:00:59.699><c> not</c><00:00:59.820><c> siled</c><00:01:00.239><c> in</c><00:01:00.360><c> one</c><00:01:00.539><c> ecosystem</c>

00:01:00.950 --> 00:01:00.960 align:start position:0%
assets are not siled in one ecosystem
 

00:01:00.960 --> 00:01:02.389 align:start position:0%
assets are not siled in one ecosystem
and<00:01:01.260><c> they</c><00:01:01.379><c> can</c><00:01:01.559><c> interact</c><00:01:01.860><c> with</c><00:01:02.039><c> all</c><00:01:02.280><c> the</c>

00:01:02.389 --> 00:01:02.399 align:start position:0%
and they can interact with all the
 

00:01:02.399 --> 00:01:03.650 align:start position:0%
and they can interact with all the
applications<00:01:02.760><c> that</c><00:01:03.059><c> they</c><00:01:03.180><c> want</c><00:01:03.300><c> to</c><00:01:03.420><c> interact</c>

00:01:03.650 --> 00:01:03.660 align:start position:0%
applications that they want to interact
 

00:01:03.660 --> 00:01:05.630 align:start position:0%
applications that they want to interact
with<00:01:03.780><c> in</c><00:01:04.379><c> a</c><00:01:04.500><c> seamless</c><00:01:04.799><c> manner</c><00:01:05.100><c> for</c><00:01:05.400><c> the</c><00:01:05.519><c> best</c>

00:01:05.630 --> 00:01:05.640 align:start position:0%
with in a seamless manner for the best
 

00:01:05.640 --> 00:01:07.910 align:start position:0%
with in a seamless manner for the best
user<00:01:06.000><c> experience</c>

00:01:07.910 --> 00:01:07.920 align:start position:0%
user experience
 

00:01:07.920 --> 00:01:10.370 align:start position:0%
user experience
so<00:01:08.340><c> bridges</c><00:01:08.760><c> are</c><00:01:08.880><c> really</c><00:01:09.060><c> important</c>

00:01:10.370 --> 00:01:10.380 align:start position:0%
so bridges are really important
 

00:01:10.380 --> 00:01:11.990 align:start position:0%
so bridges are really important
um<00:01:10.439><c> and</c><00:01:10.680><c> so</c><00:01:10.860><c> let's</c><00:01:11.159><c> talk</c><00:01:11.460><c> a</c><00:01:11.580><c> little</c><00:01:11.700><c> bit</c><00:01:11.820><c> about</c>

00:01:11.990 --> 00:01:12.000 align:start position:0%
um and so let's talk a little bit about
 

00:01:12.000 --> 00:01:14.210 align:start position:0%
um and so let's talk a little bit about
what<00:01:12.240><c> Bridges</c><00:01:12.540><c> look</c><00:01:12.720><c> like</c><00:01:12.900><c> today</c><00:01:13.140><c> so</c><00:01:13.920><c> today</c>

00:01:14.210 --> 00:01:14.220 align:start position:0%
what Bridges look like today so today
 

00:01:14.220 --> 00:01:16.370 align:start position:0%
what Bridges look like today so today
most<00:01:14.580><c> L1</c><00:01:15.000><c> bridges</c><00:01:15.479><c> are</c><00:01:15.900><c> built</c><00:01:16.200><c> with</c>

00:01:16.370 --> 00:01:16.380 align:start position:0%
most L1 bridges are built with
 

00:01:16.380 --> 00:01:19.070 align:start position:0%
most L1 bridges are built with
multi-cigs<00:01:17.159><c> or</c><00:01:17.340><c> off-chain</c><00:01:17.700><c> oracles</c><00:01:18.240><c> and</c><00:01:18.960><c> so</c>

00:01:19.070 --> 00:01:19.080 align:start position:0%
multi-cigs or off-chain oracles and so
 

00:01:19.080 --> 00:01:20.510 align:start position:0%
multi-cigs or off-chain oracles and so
the<00:01:19.200><c> high</c><00:01:19.320><c> level</c><00:01:19.500><c> design</c><00:01:19.799><c> is</c><00:01:20.100><c> you</c><00:01:20.280><c> have</c><00:01:20.340><c> a</c>

00:01:20.510 --> 00:01:20.520 align:start position:0%
the high level design is you have a
 

00:01:20.520 --> 00:01:22.190 align:start position:0%
the high level design is you have a
multi-sig<00:01:20.939><c> run</c><00:01:21.180><c> by</c><00:01:21.299><c> a</c><00:01:21.479><c> centralized</c><00:01:21.840><c> entity</c>

00:01:22.190 --> 00:01:22.200 align:start position:0%
multi-sig run by a centralized entity
 

00:01:22.200 --> 00:01:24.530 align:start position:0%
multi-sig run by a centralized entity
that<00:01:22.860><c> watches</c><00:01:23.280><c> for</c><00:01:23.460><c> deposits</c><00:01:24.060><c> on</c><00:01:24.180><c> one</c><00:01:24.360><c> chain</c>

00:01:24.530 --> 00:01:24.540 align:start position:0%
that watches for deposits on one chain
 

00:01:24.540 --> 00:01:26.570 align:start position:0%
that watches for deposits on one chain
and<00:01:25.380><c> then</c><00:01:25.439><c> we'll</c><00:01:25.560><c> sign</c><00:01:25.740><c> off</c><00:01:25.920><c> on</c><00:01:26.040><c> withdrawals</c>

00:01:26.570 --> 00:01:26.580 align:start position:0%
and then we'll sign off on withdrawals
 

00:01:26.580 --> 00:01:27.770 align:start position:0%
and then we'll sign off on withdrawals
on<00:01:26.700><c> another</c><00:01:26.880><c> chain</c>

00:01:27.770 --> 00:01:27.780 align:start position:0%
on another chain
 

00:01:27.780 --> 00:01:29.929 align:start position:0%
on another chain
and<00:01:28.560><c> these</c><00:01:28.920><c> multi-sig</c><00:01:29.400><c> designs</c><00:01:29.759><c> are</c>

00:01:29.929 --> 00:01:29.939 align:start position:0%
and these multi-sig designs are
 

00:01:29.939 --> 00:01:31.190 align:start position:0%
and these multi-sig designs are
generally<00:01:30.180><c> pretty</c><00:01:30.420><c> bad</c><00:01:30.659><c> for</c><00:01:30.900><c> a</c><00:01:31.020><c> lot</c><00:01:31.080><c> of</c>

00:01:31.190 --> 00:01:31.200 align:start position:0%
generally pretty bad for a lot of
 

00:01:31.200 --> 00:01:33.830 align:start position:0%
generally pretty bad for a lot of
reasons<00:01:31.619><c> so</c><00:01:32.159><c> they're</c><00:01:32.880><c> you</c><00:01:33.240><c> know</c><00:01:33.360><c> sensorable</c>

00:01:33.830 --> 00:01:33.840 align:start position:0%
reasons so they're you know sensorable
 

00:01:33.840 --> 00:01:35.690 align:start position:0%
reasons so they're you know sensorable
they're<00:01:34.320><c> not</c><00:01:34.439><c> permissionless</c><00:01:34.979><c> they're</c><00:01:35.579><c> very</c>

00:01:35.690 --> 00:01:35.700 align:start position:0%
they're not permissionless they're very
 

00:01:35.700 --> 00:01:37.910 align:start position:0%
they're not permissionless they're very
centralized<00:01:36.360><c> and</c><00:01:37.140><c> they're</c><00:01:37.320><c> actually</c><00:01:37.500><c> you</c>

00:01:37.910 --> 00:01:37.920 align:start position:0%
centralized and they're actually you
 

00:01:37.920 --> 00:01:39.770 align:start position:0%
centralized and they're actually you
know<00:01:37.979><c> empirically</c><00:01:38.520><c> have</c><00:01:38.880><c> been</c><00:01:39.060><c> very</c><00:01:39.299><c> insecure</c>

00:01:39.770 --> 00:01:39.780 align:start position:0%
know empirically have been very insecure
 

00:01:39.780 --> 00:01:41.749 align:start position:0%
know empirically have been very insecure
and<00:01:40.079><c> there's</c><00:01:40.259><c> been</c><00:01:40.500><c> many</c><00:01:40.740><c> such</c><00:01:41.040><c> Bridge</c><00:01:41.280><c> hacks</c>

00:01:41.749 --> 00:01:41.759 align:start position:0%
and there's been many such Bridge hacks
 

00:01:41.759 --> 00:01:44.330 align:start position:0%
and there's been many such Bridge hacks
uh<00:01:42.479><c> and</c><00:01:42.720><c> I</c><00:01:43.140><c> would</c><00:01:43.200><c> argue</c><00:01:43.500><c> that</c><00:01:43.860><c> these</c><00:01:44.220><c> Bridge</c>

00:01:44.330 --> 00:01:44.340 align:start position:0%
uh and I would argue that these Bridge
 

00:01:44.340 --> 00:01:46.370 align:start position:0%
uh and I would argue that these Bridge
hacks<00:01:44.820><c> are</c><00:01:45.000><c> not</c><00:01:45.180><c> only</c><00:01:45.299><c> bad</c><00:01:45.659><c> for</c><00:01:45.960><c> the</c><00:01:46.079><c> users</c>

00:01:46.370 --> 00:01:46.380 align:start position:0%
hacks are not only bad for the users
 

00:01:46.380 --> 00:01:48.289 align:start position:0%
hacks are not only bad for the users
who've<00:01:46.740><c> lost</c><00:01:46.860><c> billions</c><00:01:47.400><c> of</c><00:01:47.520><c> dollars</c><00:01:47.700><c> of</c><00:01:47.939><c> funds</c>

00:01:48.289 --> 00:01:48.299 align:start position:0%
who've lost billions of dollars of funds
 

00:01:48.299 --> 00:01:49.969 align:start position:0%
who've lost billions of dollars of funds
but<00:01:48.659><c> they're</c><00:01:48.840><c> actually</c><00:01:49.020><c> broadly</c><00:01:49.380><c> bad</c><00:01:49.619><c> for</c><00:01:49.799><c> the</c>

00:01:49.969 --> 00:01:49.979 align:start position:0%
but they're actually broadly bad for the
 

00:01:49.979 --> 00:01:52.130 align:start position:0%
but they're actually broadly bad for the
entire<00:01:50.220><c> space</c><00:01:50.579><c> it</c><00:01:51.299><c> reduces</c><00:01:51.659><c> The</c><00:01:51.840><c> credibility</c>

00:01:52.130 --> 00:01:52.140 align:start position:0%
entire space it reduces The credibility
 

00:01:52.140 --> 00:01:53.870 align:start position:0%
entire space it reduces The credibility
of<00:01:52.380><c> the</c><00:01:52.500><c> entire</c><00:01:52.740><c> space</c><00:01:53.040><c> and</c><00:01:53.340><c> then</c><00:01:53.460><c> leads</c><00:01:53.759><c> to</c>

00:01:53.870 --> 00:01:53.880 align:start position:0%
of the entire space and then leads to
 

00:01:53.880 --> 00:01:55.670 align:start position:0%
of the entire space and then leads to
severe<00:01:54.299><c> Downstream</c><00:01:54.780><c> consequences</c><00:01:55.259><c> like</c>

00:01:55.670 --> 00:01:55.680 align:start position:0%
severe Downstream consequences like
 

00:01:55.680 --> 00:01:57.710 align:start position:0%
severe Downstream consequences like
regulation

00:01:57.710 --> 00:01:57.720 align:start position:0%
regulation
 

00:01:57.720 --> 00:02:00.230 align:start position:0%
regulation
okay<00:01:58.259><c> so</c><00:01:58.920><c> that's</c><00:01:59.460><c> kind</c><00:01:59.640><c> of</c><00:01:59.700><c> like</c><00:01:59.820><c> an</c><00:01:59.939><c> overview</c>

00:02:00.230 --> 00:02:00.240 align:start position:0%
okay so that's kind of like an overview
 

00:02:00.240 --> 00:02:01.910 align:start position:0%
okay so that's kind of like an overview
of<00:02:00.360><c> the</c><00:02:00.479><c> current</c><00:02:00.600><c> problem</c><00:02:00.960><c> and</c><00:02:01.619><c> so</c><00:02:01.740><c> let's</c>

00:02:01.910 --> 00:02:01.920 align:start position:0%
of the current problem and so let's
 

00:02:01.920 --> 00:02:04.190 align:start position:0%
of the current problem and so let's
start<00:02:02.100><c> talking</c><00:02:02.340><c> about</c><00:02:02.520><c> Solutions</c><00:02:03.180><c> so</c><00:02:03.780><c> what</c>

00:02:04.190 --> 00:02:04.200 align:start position:0%
start talking about Solutions so what
 

00:02:04.200 --> 00:02:05.870 align:start position:0%
start talking about Solutions so what
does<00:02:04.380><c> a</c><00:02:04.560><c> maximally</c><00:02:04.920><c> secure</c><00:02:05.340><c> and</c><00:02:05.640><c> Trust</c>

00:02:05.870 --> 00:02:05.880 align:start position:0%
does a maximally secure and Trust
 

00:02:05.880 --> 00:02:09.169 align:start position:0%
does a maximally secure and Trust
minimized<00:02:06.360><c> bridge</c><00:02:06.540><c> look</c><00:02:07.020><c> like</c><00:02:07.140><c> between</c><00:02:07.500><c> l1s</c>

00:02:09.169 --> 00:02:09.179 align:start position:0%
minimized bridge look like between l1s
 

00:02:09.179 --> 00:02:11.449 align:start position:0%
minimized bridge look like between l1s
well<00:02:09.840><c> we</c><00:02:10.140><c> already</c><00:02:10.319><c> have</c><00:02:10.560><c> a</c><00:02:10.739><c> mechanism</c><00:02:11.099><c> for</c><00:02:11.340><c> a</c>

00:02:11.449 --> 00:02:11.459 align:start position:0%
well we already have a mechanism for a
 

00:02:11.459 --> 00:02:13.610 align:start position:0%
well we already have a mechanism for a
decentralized<00:02:12.060><c> group</c><00:02:12.300><c> of</c><00:02:12.420><c> people</c><00:02:12.720><c> to</c><00:02:13.200><c> come</c><00:02:13.500><c> to</c>

00:02:13.610 --> 00:02:13.620 align:start position:0%
decentralized group of people to come to
 

00:02:13.620 --> 00:02:15.350 align:start position:0%
decentralized group of people to come to
agreement<00:02:13.980><c> on</c><00:02:14.280><c> the</c><00:02:14.400><c> state</c><00:02:14.580><c> of</c><00:02:14.760><c> a</c><00:02:14.879><c> chain</c><00:02:15.000><c> that's</c>

00:02:15.350 --> 00:02:15.360 align:start position:0%
agreement on the state of a chain that's
 

00:02:15.360 --> 00:02:17.869 align:start position:0%
agreement on the state of a chain that's
called<00:02:15.540><c> the</c><00:02:15.720><c> consensus</c><00:02:16.200><c> protocol</c><00:02:16.560><c> and</c><00:02:17.400><c> so</c><00:02:17.580><c> the</c>

00:02:17.869 --> 00:02:17.879 align:start position:0%
called the consensus protocol and so the
 

00:02:17.879 --> 00:02:19.670 align:start position:0%
called the consensus protocol and so the
key<00:02:18.000><c> idea</c><00:02:18.300><c> here</c><00:02:18.480><c> very</c><00:02:18.780><c> simply</c><00:02:19.080><c> is</c><00:02:19.319><c> that</c><00:02:19.500><c> bridge</c>

00:02:19.670 --> 00:02:19.680 align:start position:0%
key idea here very simply is that bridge
 

00:02:19.680 --> 00:02:21.530 align:start position:0%
key idea here very simply is that bridge
security<00:02:19.980><c> should</c><00:02:20.459><c> be</c><00:02:20.580><c> based</c><00:02:21.060><c> on</c><00:02:21.180><c> the</c><00:02:21.360><c> same</c>

00:02:21.530 --> 00:02:21.540 align:start position:0%
security should be based on the same
 

00:02:21.540 --> 00:02:23.690 align:start position:0%
security should be based on the same
mechanisms<00:02:22.200><c> that</c><00:02:22.680><c> validators</c><00:02:23.160><c> already</c><00:02:23.459><c> use</c>

00:02:23.690 --> 00:02:23.700 align:start position:0%
mechanisms that validators already use
 

00:02:23.700 --> 00:02:25.729 align:start position:0%
mechanisms that validators already use
to<00:02:23.879><c> agree</c><00:02:24.000><c> on</c><00:02:24.360><c> state</c><00:02:24.599><c> which</c><00:02:25.140><c> is</c><00:02:25.260><c> verification</c>

00:02:25.729 --> 00:02:25.739 align:start position:0%
to agree on state which is verification
 

00:02:25.739 --> 00:02:27.110 align:start position:0%
to agree on state which is verification
of<00:02:26.040><c> consensus</c>

00:02:27.110 --> 00:02:27.120 align:start position:0%
of consensus
 

00:02:27.120 --> 00:02:29.270 align:start position:0%
of consensus
so<00:02:27.660><c> if</c><00:02:28.080><c> you're</c><00:02:28.140><c> able</c><00:02:28.440><c> to</c><00:02:28.620><c> verify</c><00:02:28.980><c> the</c>

00:02:29.270 --> 00:02:29.280 align:start position:0%
so if you're able to verify the
 

00:02:29.280 --> 00:02:31.430 align:start position:0%
so if you're able to verify the
consensus<00:02:29.819><c> of</c><00:02:30.180><c> a</c><00:02:30.360><c> source</c><00:02:30.660><c> chain</c><00:02:30.780><c> in</c><00:02:31.319><c> the</c>

00:02:31.430 --> 00:02:31.440 align:start position:0%
consensus of a source chain in the
 

00:02:31.440 --> 00:02:33.410 align:start position:0%
consensus of a source chain in the
execution<00:02:31.800><c> layer</c><00:02:32.160><c> of</c><00:02:32.280><c> our</c><00:02:32.340><c> Target</c><00:02:32.520><c> chain</c><00:02:32.819><c> then</c>

00:02:33.410 --> 00:02:33.420 align:start position:0%
execution layer of our Target chain then
 

00:02:33.420 --> 00:02:35.390 align:start position:0%
execution layer of our Target chain then
in<00:02:33.720><c> a</c><00:02:33.840><c> trust</c><00:02:34.020><c> minimized</c><00:02:34.560><c> way</c><00:02:34.680><c> you</c><00:02:35.099><c> can</c><00:02:35.220><c> know</c>

00:02:35.390 --> 00:02:35.400 align:start position:0%
in a trust minimized way you can know
 

00:02:35.400 --> 00:02:37.369 align:start position:0%
in a trust minimized way you can know
the<00:02:35.640><c> state</c><00:02:35.819><c> of</c><00:02:35.940><c> the</c><00:02:36.120><c> source</c><00:02:36.420><c> chain</c><00:02:36.599><c> without</c>

00:02:37.369 --> 00:02:37.379 align:start position:0%
the state of the source chain without
 

00:02:37.379 --> 00:02:39.290 align:start position:0%
the state of the source chain without
having<00:02:37.680><c> a</c><00:02:37.920><c> centralized</c><00:02:38.400><c> intermediary</c><00:02:38.879><c> like</c><00:02:39.120><c> a</c>

00:02:39.290 --> 00:02:39.300 align:start position:0%
having a centralized intermediary like a
 

00:02:39.300 --> 00:02:41.449 align:start position:0%
having a centralized intermediary like a
multi-sig<00:02:39.780><c> that</c><00:02:40.260><c> has</c><00:02:40.440><c> to</c><00:02:40.620><c> sign</c><00:02:40.800><c> off</c><00:02:41.040><c> on</c><00:02:41.280><c> what</c>

00:02:41.449 --> 00:02:41.459 align:start position:0%
multi-sig that has to sign off on what
 

00:02:41.459 --> 00:02:44.949 align:start position:0%
multi-sig that has to sign off on what
the<00:02:41.580><c> state</c><00:02:41.640><c> of</c><00:02:41.819><c> a</c><00:02:41.879><c> source</c><00:02:42.180><c> chain</c><00:02:42.300><c> looks</c><00:02:42.660><c> like</c>

00:02:44.949 --> 00:02:44.959 align:start position:0%
 
 

00:02:44.959 --> 00:02:47.869 align:start position:0%
 
so<00:02:45.959><c> now</c><00:02:46.080><c> that</c><00:02:46.500><c> Uma</c><00:02:46.680><c> has</c><00:02:46.800><c> painted</c><00:02:47.040><c> a</c><00:02:47.220><c> picture</c><00:02:47.340><c> of</c>

00:02:47.869 --> 00:02:47.879 align:start position:0%
so now that Uma has painted a picture of
 

00:02:47.879 --> 00:02:51.110 align:start position:0%
so now that Uma has painted a picture of
why<00:02:48.180><c> these</c><00:02:48.800><c> proof-based</c><00:02:49.800><c> uh</c><00:02:50.459><c> proof</c><00:02:51.060><c> of</c>

00:02:51.110 --> 00:02:51.120 align:start position:0%
why these proof-based uh proof of
 

00:02:51.120 --> 00:02:52.670 align:start position:0%
why these proof-based uh proof of
consensus<00:02:51.540><c> based</c><00:02:51.900><c> Bridges</c><00:02:52.140><c> make</c><00:02:52.319><c> a</c><00:02:52.500><c> lot</c><00:02:52.620><c> of</c>

00:02:52.670 --> 00:02:52.680 align:start position:0%
consensus based Bridges make a lot of
 

00:02:52.680 --> 00:02:54.589 align:start position:0%
consensus based Bridges make a lot of
sense<00:02:52.860><c> let's</c><00:02:53.580><c> think</c><00:02:53.879><c> from</c><00:02:54.239><c> a</c><00:02:54.300><c> high</c><00:02:54.420><c> level</c>

00:02:54.589 --> 00:02:54.599 align:start position:0%
sense let's think from a high level
 

00:02:54.599 --> 00:02:56.089 align:start position:0%
sense let's think from a high level
overview<00:02:54.959><c> what</c><00:02:55.319><c> implementing</c><00:02:55.800><c> the</c><00:02:55.920><c> system</c>

00:02:56.089 --> 00:02:56.099 align:start position:0%
overview what implementing the system
 

00:02:56.099 --> 00:02:58.550 align:start position:0%
overview what implementing the system
end<00:02:56.459><c> to</c><00:02:56.580><c> end</c><00:02:56.760><c> might</c><00:02:56.879><c> look</c><00:02:57.060><c> like</c><00:02:57.180><c> so</c><00:02:58.140><c> it</c><00:02:58.379><c> means</c>

00:02:58.550 --> 00:02:58.560 align:start position:0%
end to end might look like so it means
 

00:02:58.560 --> 00:02:59.750 align:start position:0%
end to end might look like so it means
that<00:02:58.620><c> we</c><00:02:58.800><c> have</c><00:02:58.920><c> some</c><00:02:59.040><c> blockchain</c><00:02:59.459><c> like</c>

00:02:59.750 --> 00:02:59.760 align:start position:0%
that we have some blockchain like
 

00:02:59.760 --> 00:03:01.729 align:start position:0%
that we have some blockchain like
ethereum<00:03:00.300><c> and</c><00:03:00.840><c> over</c><00:03:01.019><c> the</c><00:03:01.200><c> course</c><00:03:01.319><c> of</c><00:03:01.440><c> its</c>

00:03:01.729 --> 00:03:01.739 align:start position:0%
ethereum and over the course of its
 

00:03:01.739 --> 00:03:03.350 align:start position:0%
ethereum and over the course of its
lifetime<00:03:02.040><c> it's</c><00:03:02.459><c> naturally</c><00:03:02.819><c> producing</c>

00:03:03.350 --> 00:03:03.360 align:start position:0%
lifetime it's naturally producing
 

00:03:03.360 --> 00:03:05.570 align:start position:0%
lifetime it's naturally producing
information<00:03:03.660><c> about</c><00:03:04.019><c> its</c><00:03:04.260><c> consensus</c><00:03:04.739><c> such</c><00:03:05.400><c> as</c>

00:03:05.570 --> 00:03:05.580 align:start position:0%
information about its consensus such as
 

00:03:05.580 --> 00:03:07.270 align:start position:0%
information about its consensus such as
block<00:03:05.819><c> headers</c><00:03:06.180><c> validator</c><00:03:06.720><c> signatures</c>

00:03:07.270 --> 00:03:07.280 align:start position:0%
block headers validator signatures
 

00:03:07.280 --> 00:03:09.290 align:start position:0%
block headers validator signatures
attestations<00:03:08.280><c> and</c><00:03:08.700><c> other</c><00:03:08.879><c> important</c>

00:03:09.290 --> 00:03:09.300 align:start position:0%
attestations and other important
 

00:03:09.300 --> 00:03:10.790 align:start position:0%
attestations and other important
metadata

00:03:10.790 --> 00:03:10.800 align:start position:0%
metadata
 

00:03:10.800 --> 00:03:12.830 align:start position:0%
metadata
and<00:03:11.400><c> normally</c><00:03:11.700><c> the</c><00:03:11.940><c> peer-to-peer</c><00:03:12.480><c> network</c><00:03:12.659><c> of</c>

00:03:12.830 --> 00:03:12.840 align:start position:0%
and normally the peer-to-peer network of
 

00:03:12.840 --> 00:03:14.750 align:start position:0%
and normally the peer-to-peer network of
ethereum<00:03:13.260><c> would</c><00:03:13.560><c> broadcast</c><00:03:13.800><c> and</c><00:03:14.220><c> gossip</c><00:03:14.580><c> this</c>

00:03:14.750 --> 00:03:14.760 align:start position:0%
ethereum would broadcast and gossip this
 

00:03:14.760 --> 00:03:16.430 align:start position:0%
ethereum would broadcast and gossip this
information<00:03:14.940><c> to</c><00:03:15.540><c> all</c><00:03:15.780><c> the</c><00:03:15.900><c> other</c><00:03:16.019><c> honest</c>

00:03:16.430 --> 00:03:16.440 align:start position:0%
information to all the other honest
 

00:03:16.440 --> 00:03:18.410 align:start position:0%
information to all the other honest
validators<00:03:16.980><c> and</c><00:03:17.519><c> these</c><00:03:17.640><c> validators</c><00:03:18.120><c> will</c>

00:03:18.410 --> 00:03:18.420 align:start position:0%
validators and these validators will
 

00:03:18.420 --> 00:03:20.869 align:start position:0%
validators and these validators will
also<00:03:18.780><c> verify</c><00:03:19.200><c> the</c><00:03:19.319><c> consensus</c><00:03:19.680><c> algorithm</c><00:03:20.400><c> but</c>

00:03:20.869 --> 00:03:20.879 align:start position:0%
also verify the consensus algorithm but
 

00:03:20.879 --> 00:03:22.430 align:start position:0%
also verify the consensus algorithm but
what<00:03:21.060><c> if</c><00:03:21.180><c> instead</c><00:03:21.480><c> of</c><00:03:21.659><c> just</c><00:03:21.900><c> broadcasting</c>

00:03:22.430 --> 00:03:22.440 align:start position:0%
what if instead of just broadcasting
 

00:03:22.440 --> 00:03:23.750 align:start position:0%
what if instead of just broadcasting
this<00:03:22.620><c> information</c><00:03:22.800><c> to</c><00:03:23.280><c> other</c><00:03:23.459><c> honest</c>

00:03:23.750 --> 00:03:23.760 align:start position:0%
this information to other honest
 

00:03:23.760 --> 00:03:25.729 align:start position:0%
this information to other honest
validators<00:03:24.300><c> we</c><00:03:24.959><c> broadcast</c><00:03:25.140><c> this</c><00:03:25.500><c> information</c>

00:03:25.729 --> 00:03:25.739 align:start position:0%
validators we broadcast this information
 

00:03:25.739 --> 00:03:28.190 align:start position:0%
validators we broadcast this information
to<00:03:26.159><c> a</c><00:03:26.340><c> Smart</c><00:03:26.519><c> contract</c><00:03:27.000><c> on</c><00:03:27.659><c> the</c><00:03:27.780><c> execution</c>

00:03:28.190 --> 00:03:28.200 align:start position:0%
to a Smart contract on the execution
 

00:03:28.200 --> 00:03:29.930 align:start position:0%
to a Smart contract on the execution
layer<00:03:28.560><c> of</c><00:03:28.739><c> another</c><00:03:28.920><c> chain</c><00:03:29.220><c> which</c><00:03:29.760><c> will</c>

00:03:29.930 --> 00:03:29.940 align:start position:0%
layer of another chain which will
 

00:03:29.940 --> 00:03:31.850 align:start position:0%
layer of another chain which will
re-implement<00:03:30.540><c> the</c><00:03:30.959><c> honest</c><00:03:31.200><c> validator's</c>

00:03:31.850 --> 00:03:31.860 align:start position:0%
re-implement the honest validator's
 

00:03:31.860 --> 00:03:34.190 align:start position:0%
re-implement the honest validator's
logic

00:03:34.190 --> 00:03:34.200 align:start position:0%
 
 

00:03:34.200 --> 00:03:36.410 align:start position:0%
 
the<00:03:34.680><c> reason</c><00:03:34.800><c> why</c><00:03:35.099><c> this</c><00:03:35.340><c> is</c><00:03:35.459><c> so</c><00:03:35.640><c> powerful</c><00:03:35.940><c> is</c>

00:03:36.410 --> 00:03:36.420 align:start position:0%
the reason why this is so powerful is
 

00:03:36.420 --> 00:03:38.149 align:start position:0%
the reason why this is so powerful is
that<00:03:36.599><c> if</c><00:03:36.720><c> we</c><00:03:36.840><c> can</c><00:03:37.019><c> verify</c><00:03:37.440><c> the</c><00:03:37.739><c> consensus</c>

00:03:38.149 --> 00:03:38.159 align:start position:0%
that if we can verify the consensus
 

00:03:38.159 --> 00:03:40.729 align:start position:0%
that if we can verify the consensus
algorithm<00:03:38.760><c> in</c><00:03:39.180><c> a</c><00:03:39.360><c> smart</c><00:03:39.480><c> contract</c><00:03:39.900><c> that</c><00:03:40.500><c> means</c>

00:03:40.729 --> 00:03:40.739 align:start position:0%
algorithm in a smart contract that means
 

00:03:40.739 --> 00:03:42.470 align:start position:0%
algorithm in a smart contract that means
we<00:03:40.860><c> can</c><00:03:40.980><c> essentially</c><00:03:41.280><c> run</c><00:03:41.519><c> a</c><00:03:41.819><c> like</c><00:03:41.940><c> client</c><00:03:42.299><c> on</c>

00:03:42.470 --> 00:03:42.480 align:start position:0%
we can essentially run a like client on
 

00:03:42.480 --> 00:03:45.170 align:start position:0%
we can essentially run a like client on
chain<00:03:42.720><c> and</c><00:03:43.560><c> this</c><00:03:43.680><c> means</c><00:03:43.980><c> that</c><00:03:44.099><c> essentially</c><00:03:44.819><c> we</c>

00:03:45.170 --> 00:03:45.180 align:start position:0%
chain and this means that essentially we
 

00:03:45.180 --> 00:03:47.750 align:start position:0%
chain and this means that essentially we
can<00:03:45.299><c> trustlessly</c><00:03:45.840><c> access</c><00:03:46.200><c> any</c><00:03:46.980><c> state</c><00:03:47.280><c> from</c>

00:03:47.750 --> 00:03:47.760 align:start position:0%
can trustlessly access any state from
 

00:03:47.760 --> 00:03:50.149 align:start position:0%
can trustlessly access any state from
The<00:03:47.879><c> Source</c><00:03:48.180><c> Chain</c><00:03:48.299><c> by</c><00:03:49.140><c> simply</c><00:03:49.620><c> providing</c><00:03:50.040><c> a</c>

00:03:50.149 --> 00:03:50.159 align:start position:0%
The Source Chain by simply providing a
 

00:03:50.159 --> 00:03:52.430 align:start position:0%
The Source Chain by simply providing a
Merkle<00:03:50.519><c> proof</c><00:03:50.819><c> proves</c><00:03:51.720><c> the</c><00:03:51.900><c> inclusion</c><00:03:52.260><c> of</c>

00:03:52.430 --> 00:03:52.440 align:start position:0%
Merkle proof proves the inclusion of
 

00:03:52.440 --> 00:03:54.770 align:start position:0%
Merkle proof proves the inclusion of
some<00:03:52.620><c> sort</c><00:03:52.799><c> of</c><00:03:52.920><c> data</c><00:03:53.640><c> and</c><00:03:54.180><c> inside</c><00:03:54.360><c> these</c><00:03:54.659><c> block</c>

00:03:54.770 --> 00:03:54.780 align:start position:0%
some sort of data and inside these block
 

00:03:54.780 --> 00:03:56.750 align:start position:0%
some sort of data and inside these block
headers<00:03:55.200><c> we</c><00:03:55.440><c> have</c><00:03:55.560><c> access</c><00:03:55.799><c> to</c><00:03:56.280><c> basically</c>

00:03:56.750 --> 00:03:56.760 align:start position:0%
headers we have access to basically
 

00:03:56.760 --> 00:03:59.149 align:start position:0%
headers we have access to basically
commitments<00:03:57.360><c> to</c><00:03:57.599><c> the</c><00:03:57.780><c> entire</c><00:03:58.080><c> state</c><00:03:58.379><c> of</c><00:03:58.980><c> the</c>

00:03:59.149 --> 00:03:59.159 align:start position:0%
commitments to the entire state of the
 

00:03:59.159 --> 00:04:00.830 align:start position:0%
commitments to the entire state of the
source<00:03:59.400><c> chain</c><00:03:59.580><c> such</c><00:03:59.940><c> as</c><00:04:00.060><c> like</c><00:04:00.360><c> you</c><00:04:00.540><c> know</c><00:04:00.659><c> how</c>

00:04:00.830 --> 00:04:00.840 align:start position:0%
source chain such as like you know how
 

00:04:00.840 --> 00:04:02.630 align:start position:0%
source chain such as like you know how
much<00:04:00.900><c> eth</c><00:04:01.140><c> I</c><00:04:01.319><c> have</c><00:04:01.379><c> in</c><00:04:01.560><c> my</c><00:04:01.620><c> wallet</c>

00:04:02.630 --> 00:04:02.640 align:start position:0%
much eth I have in my wallet
 

00:04:02.640 --> 00:04:04.070 align:start position:0%
much eth I have in my wallet
um what<00:04:02.879><c> transactions</c><00:04:03.360><c> were</c><00:04:03.480><c> sent</c><00:04:03.720><c> in</c><00:04:03.900><c> the</c>

00:04:04.070 --> 00:04:04.080 align:start position:0%
um what transactions were sent in the
 

00:04:04.080 --> 00:04:05.750 align:start position:0%
um what transactions were sent in the
past<00:04:04.200><c> and</c><00:04:04.620><c> what</c><00:04:04.799><c> events</c><00:04:05.099><c> were</c><00:04:05.220><c> emitted</c><00:04:05.640><c> in</c>

00:04:05.750 --> 00:04:05.760 align:start position:0%
past and what events were emitted in
 

00:04:05.760 --> 00:04:07.430 align:start position:0%
past and what events were emitted in
contracts<00:04:06.239><c> and</c><00:04:06.720><c> essentially</c><00:04:07.019><c> we</c><00:04:07.200><c> can</c><00:04:07.319><c> access</c>

00:04:07.430 --> 00:04:07.440 align:start position:0%
contracts and essentially we can access
 

00:04:07.440 --> 00:04:09.470 align:start position:0%
contracts and essentially we can access
all<00:04:07.860><c> this</c><00:04:08.040><c> state</c><00:04:08.220><c> with</c><00:04:08.519><c> just</c><00:04:08.760><c> a</c><00:04:08.879><c> simple</c><00:04:09.000><c> Merkel</c>

00:04:09.470 --> 00:04:09.480 align:start position:0%
all this state with just a simple Merkel
 

00:04:09.480 --> 00:04:10.610 align:start position:0%
all this state with just a simple Merkel
proof<00:04:09.720><c> If</c><00:04:09.840><c> we</c><00:04:09.959><c> have</c><00:04:10.140><c> this</c><00:04:10.200><c> like</c><00:04:10.319><c> client</c>

00:04:10.610 --> 00:04:10.620 align:start position:0%
proof If we have this like client
 

00:04:10.620 --> 00:04:13.250 align:start position:0%
proof If we have this like client
running<00:04:10.860><c> on</c><00:04:11.040><c> chain</c>

00:04:13.250 --> 00:04:13.260 align:start position:0%
 
 

00:04:13.260 --> 00:04:14.990 align:start position:0%
 
so<00:04:13.620><c> the</c><00:04:13.739><c> question</c><00:04:13.860><c> is</c><00:04:14.099><c> why</c><00:04:14.400><c> hasn't</c><00:04:14.700><c> anyone</c>

00:04:14.990 --> 00:04:15.000 align:start position:0%
so the question is why hasn't anyone
 

00:04:15.000 --> 00:04:17.150 align:start position:0%
so the question is why hasn't anyone
done<00:04:15.180><c> this</c><00:04:15.360><c> before</c><00:04:15.540><c> and</c><00:04:16.440><c> the</c><00:04:16.680><c> big</c><00:04:16.859><c> problem</c>

00:04:17.150 --> 00:04:17.160 align:start position:0%
done this before and the big problem
 

00:04:17.160 --> 00:04:18.710 align:start position:0%
done this before and the big problem
especially<00:04:17.639><c> with</c><00:04:17.880><c> these</c><00:04:18.060><c> proof</c><00:04:18.359><c> of</c><00:04:18.419><c> stake</c>

00:04:18.710 --> 00:04:18.720 align:start position:0%
especially with these proof of stake
 

00:04:18.720 --> 00:04:20.810 align:start position:0%
especially with these proof of stake
based<00:04:19.019><c> blockchains</c><00:04:19.620><c> is</c><00:04:20.040><c> that</c><00:04:20.220><c> verifying</c><00:04:20.699><c> the</c>

00:04:20.810 --> 00:04:20.820 align:start position:0%
based blockchains is that verifying the
 

00:04:20.820 --> 00:04:22.790 align:start position:0%
based blockchains is that verifying the
consensus<00:04:21.239><c> algorithm</c><00:04:21.720><c> is</c><00:04:22.079><c> really</c><00:04:22.260><c> expensive</c>

00:04:22.790 --> 00:04:22.800 align:start position:0%
consensus algorithm is really expensive
 

00:04:22.800 --> 00:04:25.310 align:start position:0%
consensus algorithm is really expensive
and<00:04:23.759><c> in</c><00:04:24.000><c> particular</c><00:04:24.300><c> with</c><00:04:24.479><c> ethereum</c><00:04:25.020><c> the</c>

00:04:25.310 --> 00:04:25.320 align:start position:0%
and in particular with ethereum the
 

00:04:25.320 --> 00:04:26.930 align:start position:0%
and in particular with ethereum the
challenge<00:04:25.440><c> is</c><00:04:25.680><c> that</c><00:04:26.040><c> the</c><00:04:26.160><c> validator</c><00:04:26.520><c> set</c><00:04:26.759><c> is</c>

00:04:26.930 --> 00:04:26.940 align:start position:0%
challenge is that the validator set is
 

00:04:26.940 --> 00:04:29.330 align:start position:0%
challenge is that the validator set is
so<00:04:27.060><c> large</c><00:04:27.240><c> there's</c><00:04:27.780><c> over</c><00:04:28.080><c> 400</c><00:04:28.680><c> 000</c><00:04:28.800><c> validators</c>

00:04:29.330 --> 00:04:29.340 align:start position:0%
so large there's over 400 000 validators
 

00:04:29.340 --> 00:04:31.430 align:start position:0%
so large there's over 400 000 validators
and<00:04:30.000><c> to</c><00:04:30.180><c> run</c><00:04:30.360><c> this</c><00:04:30.720><c> verification</c><00:04:31.139><c> of</c>

00:04:31.430 --> 00:04:31.440 align:start position:0%
and to run this verification of
 

00:04:31.440 --> 00:04:33.530 align:start position:0%
and to run this verification of
consensus<00:04:31.979><c> you</c><00:04:32.340><c> have</c><00:04:32.520><c> to</c><00:04:32.639><c> keep</c><00:04:32.759><c> track</c><00:04:33.000><c> of</c><00:04:33.300><c> all</c>

00:04:33.530 --> 00:04:33.540 align:start position:0%
consensus you have to keep track of all
 

00:04:33.540 --> 00:04:36.290 align:start position:0%
consensus you have to keep track of all
400<00:04:34.080><c> 000</c><00:04:34.139><c> validators</c><00:04:34.680><c> their</c><00:04:35.220><c> public</c><00:04:35.460><c> Keys</c><00:04:35.880><c> how</c>

00:04:36.290 --> 00:04:36.300 align:start position:0%
400 000 validators their public Keys how
 

00:04:36.300 --> 00:04:38.270 align:start position:0%
400 000 validators their public Keys how
much<00:04:36.419><c> they've</c><00:04:36.720><c> staked</c><00:04:37.080><c> whether</c><00:04:37.500><c> some</c><00:04:38.160><c> new</c>

00:04:38.270 --> 00:04:38.280 align:start position:0%
much they've staked whether some new
 

00:04:38.280 --> 00:04:40.189 align:start position:0%
much they've staked whether some new
validators<00:04:38.699><c> have</c><00:04:38.940><c> came</c><00:04:39.060><c> in</c><00:04:39.240><c> whether</c><00:04:39.540><c> old</c>

00:04:40.189 --> 00:04:40.199 align:start position:0%
validators have came in whether old
 

00:04:40.199 --> 00:04:42.530 align:start position:0%
validators have came in whether old
Auditors<00:04:40.680><c> have</c><00:04:40.860><c> unbought</c><00:04:41.520><c> in</c><00:04:41.699><c> their</c><00:04:41.880><c> stake</c>

00:04:42.530 --> 00:04:42.540 align:start position:0%
Auditors have unbought in their stake
 

00:04:42.540 --> 00:04:44.090 align:start position:0%
Auditors have unbought in their stake
and<00:04:42.960><c> this</c><00:04:43.139><c> is</c><00:04:43.259><c> quite</c><00:04:43.440><c> difficult</c><00:04:43.680><c> to</c><00:04:43.860><c> implement</c>

00:04:44.090 --> 00:04:44.100 align:start position:0%
and this is quite difficult to implement
 

00:04:44.100 --> 00:04:46.129 align:start position:0%
and this is quite difficult to implement
a<00:04:44.280><c> contract</c><00:04:44.580><c> in</c><00:04:44.820><c> a</c><00:04:44.940><c> gas</c><00:04:45.060><c> efficient</c><00:04:45.419><c> way</c>

00:04:46.129 --> 00:04:46.139 align:start position:0%
a contract in a gas efficient way
 

00:04:46.139 --> 00:04:49.070 align:start position:0%
a contract in a gas efficient way
the<00:04:46.680><c> second</c><00:04:46.800><c> problem</c><00:04:47.100><c> is</c><00:04:47.639><c> that</c><00:04:47.940><c> the</c><00:04:48.660><c> signature</c>

00:04:49.070 --> 00:04:49.080 align:start position:0%
the second problem is that the signature
 

00:04:49.080 --> 00:04:51.469 align:start position:0%
the second problem is that the signature
scheme<00:04:49.440><c> used</c><00:04:49.680><c> by</c><00:04:49.979><c> ethereums</c><00:04:50.699><c> to</c><00:04:50.820><c> Beacon</c><00:04:51.300><c> chain</c>

00:04:51.469 --> 00:04:51.479 align:start position:0%
scheme used by ethereums to Beacon chain
 

00:04:51.479 --> 00:04:53.810 align:start position:0%
scheme used by ethereums to Beacon chain
is<00:04:52.020><c> the</c><00:04:52.139><c> signature</c><00:04:52.500><c> schemina</c><00:04:52.800><c> as</c><00:04:52.979><c> BLS</c><00:04:53.460><c> and</c>

00:04:53.810 --> 00:04:53.820 align:start position:0%
is the signature schemina as BLS and
 

00:04:53.820 --> 00:04:55.610 align:start position:0%
is the signature schemina as BLS and
unfortunately<00:04:54.240><c> the</c><00:04:54.479><c> elliptic</c><00:04:54.900><c> curve</c><00:04:55.259><c> needed</c>

00:04:55.610 --> 00:04:55.620 align:start position:0%
unfortunately the elliptic curve needed
 

00:04:55.620 --> 00:04:57.110 align:start position:0%
unfortunately the elliptic curve needed
to<00:04:55.740><c> compute</c><00:04:55.979><c> the</c><00:04:56.100><c> signature</c><00:04:56.580><c> is</c><00:04:56.940><c> not</c>

00:04:57.110 --> 00:04:57.120 align:start position:0%
to compute the signature is not
 

00:04:57.120 --> 00:04:58.610 align:start position:0%
to compute the signature is not
currently<00:04:57.360><c> supported</c><00:04:57.780><c> by</c><00:04:58.020><c> the</c><00:04:58.199><c> execution</c>

00:04:58.610 --> 00:04:58.620 align:start position:0%
currently supported by the execution
 

00:04:58.620 --> 00:05:02.450 align:start position:0%
currently supported by the execution
layer<00:04:58.979><c> on</c><00:04:59.220><c> many</c><00:04:59.340><c> evm</c><00:04:59.880><c> blockchains</c>

00:05:02.450 --> 00:05:02.460 align:start position:0%
layer on many evm blockchains
 

00:05:02.460 --> 00:05:03.590 align:start position:0%
layer on many evm blockchains
so

00:05:03.590 --> 00:05:03.600 align:start position:0%
so
 

00:05:03.600 --> 00:05:05.450 align:start position:0%
so
even<00:05:03.960><c> outside</c><00:05:04.320><c> the</c><00:05:04.680><c> context</c><00:05:04.919><c> where</c><00:05:05.160><c> we</c><00:05:05.340><c> want</c>

00:05:05.450 --> 00:05:05.460 align:start position:0%
even outside the context where we want
 

00:05:05.460 --> 00:05:07.550 align:start position:0%
even outside the context where we want
to<00:05:05.580><c> do</c><00:05:05.699><c> this</c><00:05:05.820><c> in</c><00:05:05.940><c> a</c><00:05:06.120><c> smart</c><00:05:06.240><c> contract</c><00:05:06.660><c> basically</c>

00:05:07.550 --> 00:05:07.560 align:start position:0%
to do this in a smart contract basically
 

00:05:07.560 --> 00:05:09.409 align:start position:0%
to do this in a smart contract basically
running<00:05:07.800><c> a</c><00:05:08.040><c> like</c><00:05:08.160><c> client</c><00:05:08.520><c> from</c><00:05:08.699><c> for</c><00:05:09.060><c> a</c><00:05:09.240><c> proof</c>

00:05:09.409 --> 00:05:09.419 align:start position:0%
running a like client from for a proof
 

00:05:09.419 --> 00:05:11.030 align:start position:0%
running a like client from for a proof
of<00:05:09.540><c> stake</c><00:05:09.720><c> blockchain</c><00:05:10.080><c> like</c><00:05:10.259><c> ethereum</c><00:05:10.800><c> is</c>

00:05:11.030 --> 00:05:11.040 align:start position:0%
of stake blockchain like ethereum is
 

00:05:11.040 --> 00:05:12.890 align:start position:0%
of stake blockchain like ethereum is
just<00:05:11.220><c> ridiculously</c><00:05:11.759><c> expensive</c><00:05:12.180><c> even</c><00:05:12.419><c> on</c><00:05:12.720><c> like</c>

00:05:12.890 --> 00:05:12.900 align:start position:0%
just ridiculously expensive even on like
 

00:05:12.900 --> 00:05:14.390 align:start position:0%
just ridiculously expensive even on like
consumer<00:05:13.440><c> Hardware</c><00:05:13.560><c> like</c><00:05:13.860><c> iPhones</c><00:05:14.220><c> or</c>

00:05:14.390 --> 00:05:14.400 align:start position:0%
consumer Hardware like iPhones or
 

00:05:14.400 --> 00:05:17.450 align:start position:0%
consumer Hardware like iPhones or
laptops<00:05:14.940><c> which</c><00:05:15.600><c> is</c><00:05:15.720><c> why</c><00:05:16.139><c> the</c><00:05:16.680><c> consensus</c><00:05:17.040><c> folks</c>

00:05:17.450 --> 00:05:17.460 align:start position:0%
laptops which is why the consensus folks
 

00:05:17.460 --> 00:05:19.370 align:start position:0%
laptops which is why the consensus folks
essentially<00:05:18.000><c> implemented</c><00:05:18.479><c> a</c><00:05:18.960><c> specific</c>

00:05:19.370 --> 00:05:19.380 align:start position:0%
essentially implemented a specific
 

00:05:19.380 --> 00:05:22.010 align:start position:0%
essentially implemented a specific
consensus<00:05:20.040><c> algorithm</c><00:05:20.460><c> for</c><00:05:20.759><c> like</c><00:05:20.940><c> clients</c><00:05:21.479><c> and</c>

00:05:22.010 --> 00:05:22.020 align:start position:0%
consensus algorithm for like clients and
 

00:05:22.020 --> 00:05:23.689 align:start position:0%
consensus algorithm for like clients and
this<00:05:22.440><c> protocol</c><00:05:22.800><c> is</c><00:05:22.919><c> known</c><00:05:23.100><c> as</c><00:05:23.220><c> the</c><00:05:23.400><c> sync</c>

00:05:23.689 --> 00:05:23.699 align:start position:0%
this protocol is known as the sync
 

00:05:23.699 --> 00:05:24.770 align:start position:0%
this protocol is known as the sync
committee

00:05:24.770 --> 00:05:24.780 align:start position:0%
committee
 

00:05:24.780 --> 00:05:26.629 align:start position:0%
committee
so<00:05:25.320><c> essentially</c><00:05:25.680><c> instead</c><00:05:26.160><c> of</c><00:05:26.220><c> verifying</c>

00:05:26.629 --> 00:05:26.639 align:start position:0%
so essentially instead of verifying
 

00:05:26.639 --> 00:05:29.510 align:start position:0%
so essentially instead of verifying
consensus<00:05:27.180><c> against</c><00:05:27.479><c> 400</c><00:05:28.259><c> 000</c><00:05:28.380><c> validators</c><00:05:28.919><c> the</c>

00:05:29.510 --> 00:05:29.520 align:start position:0%
consensus against 400 000 validators the
 

00:05:29.520 --> 00:05:31.070 align:start position:0%
consensus against 400 000 validators the
sync<00:05:29.880><c> committee</c><00:05:30.060><c> reduces</c><00:05:30.419><c> this</c><00:05:30.600><c> problem</c><00:05:30.780><c> down</c>

00:05:31.070 --> 00:05:31.080 align:start position:0%
sync committee reduces this problem down
 

00:05:31.080 --> 00:05:33.350 align:start position:0%
sync committee reduces this problem down
to<00:05:31.440><c> listening</c><00:05:31.860><c> to</c><00:05:31.979><c> the</c><00:05:32.160><c> signatures</c><00:05:32.580><c> of</c><00:05:32.759><c> 512</c>

00:05:33.350 --> 00:05:33.360 align:start position:0%
to listening to the signatures of 512
 

00:05:33.360 --> 00:05:34.969 align:start position:0%
to listening to the signatures of 512
validators<00:05:33.840><c> which</c><00:05:34.080><c> are</c><00:05:34.259><c> randomly</c><00:05:34.560><c> chosen</c>

00:05:34.969 --> 00:05:34.979 align:start position:0%
validators which are randomly chosen
 

00:05:34.979 --> 00:05:36.469 align:start position:0%
validators which are randomly chosen
every<00:05:35.280><c> 27</c><00:05:35.639><c> hours</c>

00:05:36.469 --> 00:05:36.479 align:start position:0%
every 27 hours
 

00:05:36.479 --> 00:05:38.390 align:start position:0%
every 27 hours
and<00:05:36.840><c> it</c><00:05:36.960><c> works</c><00:05:37.259><c> exactly</c><00:05:37.560><c> as</c><00:05:37.800><c> how</c><00:05:38.100><c> you'd</c>

00:05:38.390 --> 00:05:38.400 align:start position:0%
and it works exactly as how you'd
 

00:05:38.400 --> 00:05:40.310 align:start position:0%
and it works exactly as how you'd
imagine<00:05:38.539><c> essentially</c><00:05:39.539><c> these</c><00:05:39.900><c> validators</c>

00:05:40.310 --> 00:05:40.320 align:start position:0%
imagine essentially these validators
 

00:05:40.320 --> 00:05:42.170 align:start position:0%
imagine essentially these validators
will<00:05:40.560><c> sign</c><00:05:40.740><c> every</c><00:05:40.979><c> block</c><00:05:41.280><c> and</c><00:05:41.940><c> if</c><00:05:42.060><c> enough</c>

00:05:42.170 --> 00:05:42.180 align:start position:0%
will sign every block and if enough
 

00:05:42.180 --> 00:05:43.610 align:start position:0%
will sign every block and if enough
values<00:05:42.660><c> sign</c><00:05:42.840><c> up</c><00:05:42.960><c> from</c><00:05:43.080><c> the</c><00:05:43.139><c> Block</c><00:05:43.320><c> you</c><00:05:43.560><c> know</c>

00:05:43.610 --> 00:05:43.620 align:start position:0%
values sign up from the Block you know
 

00:05:43.620 --> 00:05:45.590 align:start position:0%
values sign up from the Block you know
the<00:05:43.800><c> block</c><00:05:43.919><c> is</c><00:05:44.220><c> Justified</c><00:05:44.580><c> and</c><00:05:45.180><c> after</c><00:05:45.300><c> some</c>

00:05:45.590 --> 00:05:45.600 align:start position:0%
the block is Justified and after some
 

00:05:45.600 --> 00:05:47.330 align:start position:0%
the block is Justified and after some
finalization<00:05:46.199><c> rules</c><00:05:46.560><c> the</c><00:05:46.800><c> block</c><00:05:46.919><c> is</c><00:05:47.100><c> also</c>

00:05:47.330 --> 00:05:47.340 align:start position:0%
finalization rules the block is also
 

00:05:47.340 --> 00:05:49.070 align:start position:0%
finalization rules the block is also
considered<00:05:47.699><c> finalized</c>

00:05:49.070 --> 00:05:49.080 align:start position:0%
considered finalized
 

00:05:49.080 --> 00:05:50.990 align:start position:0%
considered finalized
and<00:05:49.680><c> obviously</c><00:05:49.979><c> at</c><00:05:50.220><c> the</c><00:05:50.340><c> cost</c><00:05:50.460><c> of</c><00:05:50.639><c> being</c><00:05:50.820><c> much</c>

00:05:50.990 --> 00:05:51.000 align:start position:0%
and obviously at the cost of being much
 

00:05:51.000 --> 00:05:54.230 align:start position:0%
and obviously at the cost of being much
cheaper<00:05:51.240><c> to</c><00:05:51.360><c> verify</c><00:05:51.860><c> the</c><00:05:52.860><c> sync</c><00:05:53.160><c> committee</c><00:05:53.520><c> uh</c>

00:05:54.230 --> 00:05:54.240 align:start position:0%
cheaper to verify the sync committee uh
 

00:05:54.240 --> 00:05:55.790 align:start position:0%
cheaper to verify the sync committee uh
sync<00:05:54.840><c> committee</c><00:05:55.020><c> provides</c><00:05:55.259><c> much</c><00:05:55.440><c> weaker</c>

00:05:55.790 --> 00:05:55.800 align:start position:0%
sync committee provides much weaker
 

00:05:55.800 --> 00:05:57.409 align:start position:0%
sync committee provides much weaker
security<00:05:55.919><c> guarantees</c><00:05:56.520><c> and</c><00:05:56.820><c> it</c><00:05:56.940><c> requires</c><00:05:57.300><c> a</c>

00:05:57.409 --> 00:05:57.419 align:start position:0%
security guarantees and it requires a
 

00:05:57.419 --> 00:05:59.450 align:start position:0%
security guarantees and it requires a
two-thirds<00:05:57.900><c> honesty</c><00:05:58.259><c> assumption</c>

00:05:59.450 --> 00:05:59.460 align:start position:0%
two-thirds honesty assumption
 

00:05:59.460 --> 00:06:02.029 align:start position:0%
two-thirds honesty assumption
however<00:06:00.180><c> we</c><00:06:00.720><c> originally</c><00:06:01.199><c> explored</c><00:06:01.680><c> the</c>

00:06:02.029 --> 00:06:02.039 align:start position:0%
however we originally explored the
 

00:06:02.039 --> 00:06:04.129 align:start position:0%
however we originally explored the
possibility<00:06:02.460><c> of</c><00:06:03.180><c> verifying</c><00:06:03.720><c> this</c><00:06:04.020><c> like</c>

00:06:04.129 --> 00:06:04.139 align:start position:0%
possibility of verifying this like
 

00:06:04.139 --> 00:06:05.810 align:start position:0%
possibility of verifying this like
client<00:06:04.500><c> protocol</c><00:06:04.740><c> on</c><00:06:05.039><c> chain</c><00:06:05.220><c> and</c><00:06:05.520><c> what</c><00:06:05.699><c> we</c>

00:06:05.810 --> 00:06:05.820 align:start position:0%
client protocol on chain and what we
 

00:06:05.820 --> 00:06:07.490 align:start position:0%
client protocol on chain and what we
found<00:06:05.940><c> is</c><00:06:06.180><c> that</c><00:06:06.360><c> even</c><00:06:06.600><c> in</c><00:06:07.020><c> this</c><00:06:07.080><c> scenario</c>

00:06:07.490 --> 00:06:07.500 align:start position:0%
found is that even in this scenario
 

00:06:07.500 --> 00:06:09.230 align:start position:0%
found is that even in this scenario
where<00:06:07.800><c> there's</c><00:06:07.919><c> only</c><00:06:08.100><c> 500</c><00:06:08.460><c> to</c><00:06:08.639><c> validators</c>

00:06:09.230 --> 00:06:09.240 align:start position:0%
where there's only 500 to validators
 

00:06:09.240 --> 00:06:11.150 align:start position:0%
where there's only 500 to validators
actually<00:06:09.840><c> verifying</c><00:06:10.380><c> this</c><00:06:10.500><c> consensus</c><00:06:10.919><c> on</c>

00:06:11.150 --> 00:06:11.160 align:start position:0%
actually verifying this consensus on
 

00:06:11.160 --> 00:06:13.430 align:start position:0%
actually verifying this consensus on
chain<00:06:11.340><c> is</c><00:06:11.580><c> still</c><00:06:11.699><c> too</c><00:06:11.820><c> expensive</c>

00:06:13.430 --> 00:06:13.440 align:start position:0%
chain is still too expensive
 

00:06:13.440 --> 00:06:15.350 align:start position:0%
chain is still too expensive
so<00:06:13.800><c> as</c><00:06:13.979><c> do</c><00:06:14.160><c> concrete</c><00:06:14.520><c> reasons</c><00:06:14.820><c> why</c><00:06:15.000><c> it's</c><00:06:15.180><c> too</c>

00:06:15.350 --> 00:06:15.360 align:start position:0%
so as do concrete reasons why it's too
 

00:06:15.360 --> 00:06:16.430 align:start position:0%
so as do concrete reasons why it's too
expensive

00:06:16.430 --> 00:06:16.440 align:start position:0%
expensive
 

00:06:16.440 --> 00:06:17.930 align:start position:0%
expensive
it<00:06:16.800><c> has</c><00:06:16.919><c> to</c><00:06:17.039><c> do</c><00:06:17.100><c> with</c><00:06:17.220><c> the</c><00:06:17.460><c> fact</c><00:06:17.520><c> that</c><00:06:17.759><c> you</c>

00:06:17.930 --> 00:06:17.940 align:start position:0%
it has to do with the fact that you
 

00:06:17.940 --> 00:06:19.850 align:start position:0%
it has to do with the fact that you
still<00:06:18.060><c> have</c><00:06:18.240><c> to</c><00:06:18.360><c> store</c><00:06:18.539><c> 512</c><00:06:19.380><c> of</c><00:06:19.500><c> these</c><00:06:19.680><c> public</c>

00:06:19.850 --> 00:06:19.860 align:start position:0%
still have to store 512 of these public
 

00:06:19.860 --> 00:06:22.189 align:start position:0%
still have to store 512 of these public
keys<00:06:20.280><c> on</c><00:06:20.460><c> chain</c><00:06:20.699><c> and</c><00:06:21.479><c> you</c><00:06:21.660><c> have</c><00:06:21.720><c> to</c><00:06:21.840><c> rotate</c>

00:06:22.189 --> 00:06:22.199 align:start position:0%
keys on chain and you have to rotate
 

00:06:22.199 --> 00:06:24.770 align:start position:0%
keys on chain and you have to rotate
them<00:06:22.380><c> every</c><00:06:22.680><c> 27</c><00:06:23.100><c> hours</c><00:06:23.400><c> and</c><00:06:24.060><c> storing</c><00:06:24.479><c> a</c><00:06:24.600><c> state</c>

00:06:24.770 --> 00:06:24.780 align:start position:0%
them every 27 hours and storing a state
 

00:06:24.780 --> 00:06:26.629 align:start position:0%
them every 27 hours and storing a state
on<00:06:24.960><c> chain</c><00:06:25.139><c> is</c><00:06:25.319><c> still</c><00:06:25.440><c> very</c><00:06:25.620><c> expensive</c>

00:06:26.629 --> 00:06:26.639 align:start position:0%
on chain is still very expensive
 

00:06:26.639 --> 00:06:29.990 align:start position:0%
on chain is still very expensive
furthermore<00:06:27.740><c> like</c><00:06:28.740><c> I</c><00:06:28.860><c> said</c><00:06:28.979><c> before</c><00:06:29.160><c> the</c>

00:06:29.990 --> 00:06:30.000 align:start position:0%
furthermore like I said before the
 

00:06:30.000 --> 00:06:31.550 align:start position:0%
furthermore like I said before the
current<00:06:30.120><c> evm</c><00:06:30.720><c> doesn't</c><00:06:31.020><c> support</c><00:06:31.319><c> a</c>

00:06:31.550 --> 00:06:31.560 align:start position:0%
current evm doesn't support a
 

00:06:31.560 --> 00:06:33.409 align:start position:0%
current evm doesn't support a
pre-compiles<00:06:32.220><c> for</c><00:06:32.400><c> the</c><00:06:32.580><c> specific</c><00:06:32.819><c> elliptic</c>

00:06:33.409 --> 00:06:33.419 align:start position:0%
pre-compiles for the specific elliptic
 

00:06:33.419 --> 00:06:35.210 align:start position:0%
pre-compiles for the specific elliptic
curve<00:06:33.780><c> you</c><00:06:34.199><c> needed</c><00:06:34.560><c> to</c><00:06:34.680><c> verify</c><00:06:34.979><c> these</c>

00:06:35.210 --> 00:06:35.220 align:start position:0%
curve you needed to verify these
 

00:06:35.220 --> 00:06:36.770 align:start position:0%
curve you needed to verify these
signature<00:06:35.580><c> schemes</c><00:06:35.940><c> which</c><00:06:36.300><c> means</c><00:06:36.539><c> that</c><00:06:36.660><c> we</c>

00:06:36.770 --> 00:06:36.780 align:start position:0%
signature schemes which means that we
 

00:06:36.780 --> 00:06:38.629 align:start position:0%
signature schemes which means that we
have<00:06:36.900><c> to</c><00:06:37.020><c> implement</c><00:06:37.380><c> you</c><00:06:37.740><c> know</c><00:06:37.860><c> this</c><00:06:38.400><c> this</c>

00:06:38.629 --> 00:06:38.639 align:start position:0%
have to implement you know this this
 

00:06:38.639 --> 00:06:40.670 align:start position:0%
have to implement you know this this
elliptic<00:06:39.060><c> curve</c><00:06:39.300><c> natively</c><00:06:39.660><c> in</c><00:06:39.780><c> solidity</c><00:06:40.199><c> and</c>

00:06:40.670 --> 00:06:40.680 align:start position:0%
elliptic curve natively in solidity and
 

00:06:40.680 --> 00:06:42.110 align:start position:0%
elliptic curve natively in solidity and
in<00:06:40.860><c> terms</c><00:06:41.039><c> of</c><00:06:41.100><c> gas</c><00:06:41.280><c> costs</c><00:06:41.639><c> this</c><00:06:41.759><c> is</c><00:06:41.880><c> also</c>

00:06:42.110 --> 00:06:42.120 align:start position:0%
in terms of gas costs this is also
 

00:06:42.120 --> 00:06:45.110 align:start position:0%
in terms of gas costs this is also
probably<00:06:42.300><c> expensive</c>

00:06:45.110 --> 00:06:45.120 align:start position:0%
 
 

00:06:45.120 --> 00:06:48.409 align:start position:0%
 
so<00:06:45.780><c> our</c><00:06:46.080><c> key</c><00:06:46.319><c> Insight</c><00:06:46.680><c> basically</c><00:06:47.160><c> is</c><00:06:47.580><c> you</c><00:06:47.759><c> know</c>

00:06:48.409 --> 00:06:48.419 align:start position:0%
so our key Insight basically is you know
 

00:06:48.419 --> 00:06:50.029 align:start position:0%
so our key Insight basically is you know
you<00:06:48.840><c> know</c><00:06:48.960><c> to</c><00:06:49.199><c> implement</c><00:06:49.620><c> the</c><00:06:49.800><c> honest</c>

00:06:50.029 --> 00:06:50.039 align:start position:0%
you know to implement the honest
 

00:06:50.039 --> 00:06:51.890 align:start position:0%
you know to implement the honest
validators<00:06:50.400><c> Logic</c><00:06:50.819><c> on</c><00:06:50.940><c> chain</c><00:06:51.120><c> is</c><00:06:51.360><c> obviously</c><00:06:51.720><c> a</c>

00:06:51.890 --> 00:06:51.900 align:start position:0%
validators Logic on chain is obviously a
 

00:06:51.900 --> 00:06:54.050 align:start position:0%
validators Logic on chain is obviously a
super<00:06:52.020><c> competition</c><00:06:52.440><c> expensive</c><00:06:53.039><c> task</c><00:06:53.340><c> but</c>

00:06:54.050 --> 00:06:54.060 align:start position:0%
super competition expensive task but
 

00:06:54.060 --> 00:06:55.730 align:start position:0%
super competition expensive task but
what<00:06:54.240><c> we</c><00:06:54.419><c> have</c><00:06:54.539><c> available</c><00:06:54.780><c> to</c><00:06:55.139><c> us</c><00:06:55.259><c> is</c><00:06:55.500><c> the</c>

00:06:55.730 --> 00:06:55.740 align:start position:0%
what we have available to us is the
 

00:06:55.740 --> 00:06:57.650 align:start position:0%
what we have available to us is the
power<00:06:55.919><c> of</c><00:06:56.160><c> zero</c><00:06:56.520><c> knowledge</c><00:06:56.699><c> proofs</c><00:06:57.060><c> which</c>

00:06:57.650 --> 00:06:57.660 align:start position:0%
power of zero knowledge proofs which
 

00:06:57.660 --> 00:06:58.790 align:start position:0%
power of zero knowledge proofs which
have<00:06:57.900><c> this</c><00:06:58.080><c> magical</c><00:06:58.380><c> property</c><00:06:58.680><c> of</c>

00:06:58.790 --> 00:06:58.800 align:start position:0%
have this magical property of
 

00:06:58.800 --> 00:07:00.290 align:start position:0%
have this magical property of
succinctness<00:06:59.340><c> which</c><00:06:59.639><c> basically</c><00:06:59.880><c> means</c><00:07:00.180><c> that</c>

00:07:00.290 --> 00:07:00.300 align:start position:0%
succinctness which basically means that
 

00:07:00.300 --> 00:07:02.809 align:start position:0%
succinctness which basically means that
for<00:07:00.539><c> any</c><00:07:00.840><c> arbitrary</c><00:07:01.259><c> long</c><00:07:01.500><c> computation</c><00:07:02.220><c> we</c>

00:07:02.809 --> 00:07:02.819 align:start position:0%
for any arbitrary long computation we
 

00:07:02.819 --> 00:07:04.670 align:start position:0%
for any arbitrary long computation we
can<00:07:03.000><c> generate</c><00:07:03.300><c> a</c><00:07:03.539><c> succinct</c><00:07:03.900><c> proof</c><00:07:04.319><c> which</c><00:07:04.500><c> can</c>

00:07:04.670 --> 00:07:04.680 align:start position:0%
can generate a succinct proof which can
 

00:07:04.680 --> 00:07:06.409 align:start position:0%
can generate a succinct proof which can
be<00:07:04.800><c> verified</c><00:07:05.039><c> on</c><00:07:05.280><c> chain</c>

00:07:06.409 --> 00:07:06.419 align:start position:0%
be verified on chain
 

00:07:06.419 --> 00:07:08.450 align:start position:0%
be verified on chain
so<00:07:06.840><c> essentially</c><00:07:07.259><c> you</c><00:07:07.800><c> know</c><00:07:07.919><c> the</c><00:07:08.100><c> code</c><00:07:08.220><c> in</c>

00:07:08.450 --> 00:07:08.460 align:start position:0%
so essentially you know the code in
 

00:07:08.460 --> 00:07:09.710 align:start position:0%
so essentially you know the code in
solidity<00:07:08.880><c> is</c><00:07:09.000><c> going</c><00:07:09.120><c> to</c><00:07:09.180><c> look</c><00:07:09.300><c> something</c><00:07:09.479><c> like</c>

00:07:09.710 --> 00:07:09.720 align:start position:0%
solidity is going to look something like
 

00:07:09.720 --> 00:07:11.270 align:start position:0%
solidity is going to look something like
this<00:07:09.840><c> where</c><00:07:10.139><c> we</c><00:07:10.319><c> have</c><00:07:10.500><c> some</c><00:07:10.680><c> function</c><00:07:10.979><c> that</c>

00:07:11.270 --> 00:07:11.280 align:start position:0%
this where we have some function that
 

00:07:11.280 --> 00:07:13.070 align:start position:0%
this where we have some function that
validates<00:07:11.699><c> a</c><00:07:11.880><c> new</c><00:07:11.940><c> block</c><00:07:12.180><c> and</c><00:07:12.840><c> you</c><00:07:12.960><c> know</c>

00:07:13.070 --> 00:07:13.080 align:start position:0%
validates a new block and you know
 

00:07:13.080 --> 00:07:14.510 align:start position:0%
validates a new block and you know
obviously<00:07:13.440><c> you</c><00:07:13.620><c> have</c><00:07:13.740><c> some</c><00:07:13.860><c> pre-processing</c>

00:07:14.510 --> 00:07:14.520 align:start position:0%
obviously you have some pre-processing
 

00:07:14.520 --> 00:07:16.430 align:start position:0%
obviously you have some pre-processing
step<00:07:14.759><c> you</c><00:07:15.240><c> have</c><00:07:15.360><c> some</c><00:07:15.539><c> step</c><00:07:15.720><c> to</c><00:07:15.900><c> verify</c><00:07:16.259><c> that</c>

00:07:16.430 --> 00:07:16.440 align:start position:0%
step you have some step to verify that
 

00:07:16.440 --> 00:07:17.870 align:start position:0%
step you have some step to verify that
the<00:07:16.560><c> current</c><00:07:16.680><c> validator</c><00:07:17.100><c> set</c><00:07:17.340><c> is</c><00:07:17.520><c> valid</c><00:07:17.759><c> and</c>

00:07:17.870 --> 00:07:17.880 align:start position:0%
the current validator set is valid and
 

00:07:17.880 --> 00:07:19.550 align:start position:0%
the current validator set is valid and
that<00:07:18.060><c> we</c><00:07:18.180><c> rotate</c><00:07:18.539><c> the</c><00:07:18.660><c> stakes</c><00:07:18.900><c> and</c><00:07:19.259><c> whatnot</c>

00:07:19.550 --> 00:07:19.560 align:start position:0%
that we rotate the stakes and whatnot
 

00:07:19.560 --> 00:07:21.230 align:start position:0%
that we rotate the stakes and whatnot
and<00:07:20.039><c> then</c><00:07:20.099><c> finally</c><00:07:20.400><c> of</c><00:07:20.699><c> course</c><00:07:20.819><c> we</c><00:07:21.000><c> have</c><00:07:21.120><c> to</c>

00:07:21.230 --> 00:07:21.240 align:start position:0%
and then finally of course we have to
 

00:07:21.240 --> 00:07:24.110 align:start position:0%
and then finally of course we have to
verify<00:07:21.720><c> this</c><00:07:22.319><c> be</c><00:07:22.500><c> these</c><00:07:22.800><c> BLS</c><00:07:23.160><c> signatures</c>

00:07:24.110 --> 00:07:24.120 align:start position:0%
verify this be these BLS signatures
 

00:07:24.120 --> 00:07:26.390 align:start position:0%
verify this be these BLS signatures
and<00:07:24.660><c> as</c><00:07:24.840><c> I've</c><00:07:25.080><c> mentioned</c><00:07:25.680><c> in</c><00:07:26.099><c> these</c><00:07:26.280><c> previous</c>

00:07:26.390 --> 00:07:26.400 align:start position:0%
and as I've mentioned in these previous
 

00:07:26.400 --> 00:07:28.189 align:start position:0%
and as I've mentioned in these previous
slides<00:07:26.819><c> I've</c><00:07:27.360><c> talked</c><00:07:27.599><c> a</c><00:07:27.660><c> lot</c><00:07:27.780><c> about</c><00:07:27.900><c> how</c>

00:07:28.189 --> 00:07:28.199 align:start position:0%
slides I've talked a lot about how
 

00:07:28.199 --> 00:07:29.330 align:start position:0%
slides I've talked a lot about how
verifying<00:07:28.620><c> the</c><00:07:28.680><c> vouchers</c><00:07:28.979><c> that</c><00:07:29.160><c> and</c>

00:07:29.330 --> 00:07:29.340 align:start position:0%
verifying the vouchers that and
 

00:07:29.340 --> 00:07:30.529 align:start position:0%
verifying the vouchers that and
verifying<00:07:29.580><c> these</c><00:07:29.699><c> BL</c><00:07:29.819><c> signatures</c><00:07:30.300><c> is</c><00:07:30.419><c> quite</c>

00:07:30.529 --> 00:07:30.539 align:start position:0%
verifying these BL signatures is quite
 

00:07:30.539 --> 00:07:32.749 align:start position:0%
verifying these BL signatures is quite
expensive<00:07:31.020><c> but</c><00:07:31.620><c> what</c><00:07:31.800><c> we</c><00:07:31.919><c> can</c><00:07:32.099><c> do</c><00:07:32.220><c> is</c><00:07:32.520><c> we</c><00:07:32.699><c> can</c>

00:07:32.749 --> 00:07:32.759 align:start position:0%
expensive but what we can do is we can
 

00:07:32.759 --> 00:07:35.450 align:start position:0%
expensive but what we can do is we can
just<00:07:32.940><c> compute</c><00:07:33.360><c> a</c><00:07:33.479><c> ZK</c><00:07:33.780><c> proof</c><00:07:34.259><c> that</c><00:07:34.860><c> does</c><00:07:35.039><c> these</c>

00:07:35.450 --> 00:07:35.460 align:start position:0%
just compute a ZK proof that does these
 

00:07:35.460 --> 00:07:37.790 align:start position:0%
just compute a ZK proof that does these
two<00:07:35.580><c> expensive</c><00:07:36.120><c> operations</c><00:07:36.479><c> off</c><00:07:36.840><c> chain</c><00:07:37.139><c> and</c>

00:07:37.790 --> 00:07:37.800 align:start position:0%
two expensive operations off chain and
 

00:07:37.800 --> 00:07:39.469 align:start position:0%
two expensive operations off chain and
instead<00:07:38.039><c> on</c><00:07:38.220><c> chain</c><00:07:38.400><c> we</c><00:07:38.699><c> just</c><00:07:38.880><c> implement</c><00:07:39.180><c> the</c>

00:07:39.469 --> 00:07:39.479 align:start position:0%
instead on chain we just implement the
 

00:07:39.479 --> 00:07:41.210 align:start position:0%
instead on chain we just implement the
same<00:07:39.660><c> function</c><00:07:40.020><c> but</c><00:07:40.259><c> we</c><00:07:40.440><c> swap</c><00:07:40.740><c> out</c><00:07:40.860><c> these</c><00:07:41.099><c> two</c>

00:07:41.210 --> 00:07:41.220 align:start position:0%
same function but we swap out these two
 

00:07:41.220 --> 00:07:42.650 align:start position:0%
same function but we swap out these two
expensive<00:07:41.639><c> Parts</c><00:07:41.819><c> with</c><00:07:42.360><c> just</c><00:07:42.539><c> the</c>

00:07:42.650 --> 00:07:42.660 align:start position:0%
expensive Parts with just the
 

00:07:42.660 --> 00:07:44.390 align:start position:0%
expensive Parts with just the
verification<00:07:43.080><c> of</c><00:07:43.319><c> this</c><00:07:43.440><c> narc</c><00:07:43.860><c> which</c><00:07:44.160><c> will</c>

00:07:44.390 --> 00:07:44.400 align:start position:0%
verification of this narc which will
 

00:07:44.400 --> 00:07:46.790 align:start position:0%
verification of this narc which will
verifiably<00:07:45.300><c> prove</c><00:07:45.660><c> that</c><00:07:45.900><c> we</c><00:07:46.199><c> computed</c><00:07:46.620><c> those</c>

00:07:46.790 --> 00:07:46.800 align:start position:0%
verifiably prove that we computed those
 

00:07:46.800 --> 00:07:48.170 align:start position:0%
verifiably prove that we computed those
things<00:07:46.919><c> correctly</c>

00:07:48.170 --> 00:07:48.180 align:start position:0%
things correctly
 

00:07:48.180 --> 00:07:49.550 align:start position:0%
things correctly
and<00:07:48.479><c> I</c><00:07:48.599><c> think</c><00:07:48.720><c> this</c><00:07:48.840><c> is</c><00:07:48.960><c> really</c><00:07:49.139><c> exciting</c>

00:07:49.550 --> 00:07:49.560 align:start position:0%
and I think this is really exciting
 

00:07:49.560 --> 00:07:51.950 align:start position:0%
and I think this is really exciting
because<00:07:49.919><c> this</c><00:07:50.639><c> is</c><00:07:50.759><c> just</c><00:07:51.000><c> this</c><00:07:51.300><c> is</c><00:07:51.479><c> a</c><00:07:51.660><c> framework</c>

00:07:51.950 --> 00:07:51.960 align:start position:0%
because this is just this is a framework
 

00:07:51.960 --> 00:07:54.110 align:start position:0%
because this is just this is a framework
that<00:07:52.259><c> generalizes</c><00:07:52.860><c> outside</c><00:07:53.220><c> of</c><00:07:53.759><c> like</c><00:07:53.940><c> this</c>

00:07:54.110 --> 00:07:54.120 align:start position:0%
that generalizes outside of like this
 

00:07:54.120 --> 00:07:55.670 align:start position:0%
that generalizes outside of like this
ethereum<00:07:54.419><c> sync</c><00:07:54.780><c> committee</c><00:07:55.080><c> and</c><00:07:55.440><c> can</c><00:07:55.560><c> be</c>

00:07:55.670 --> 00:07:55.680 align:start position:0%
ethereum sync committee and can be
 

00:07:55.680 --> 00:07:57.170 align:start position:0%
ethereum sync committee and can be
generalized<00:07:56.099><c> to</c><00:07:56.220><c> other</c><00:07:56.400><c> blockchains</c><00:07:57.060><c> to</c>

00:07:57.170 --> 00:07:57.180 align:start position:0%
generalized to other blockchains to
 

00:07:57.180 --> 00:07:59.450 align:start position:0%
generalized to other blockchains to
basically<00:07:57.479><c> make</c><00:07:57.720><c> it</c><00:07:57.960><c> very</c><00:07:58.500><c> easy</c><00:07:58.800><c> to</c><00:07:59.160><c> verify</c>

00:07:59.450 --> 00:07:59.460 align:start position:0%
basically make it very easy to verify
 

00:07:59.460 --> 00:08:01.610 align:start position:0%
basically make it very easy to verify
the<00:07:59.639><c> consensus</c><00:08:00.120><c> algorithm</c><00:08:00.599><c> in</c><00:08:00.840><c> the</c><00:08:01.020><c> state</c><00:08:01.139><c> of</c>

00:08:01.610 --> 00:08:01.620 align:start position:0%
the consensus algorithm in the state of
 

00:08:01.620 --> 00:08:03.589 align:start position:0%
the consensus algorithm in the state of
other<00:08:01.740><c> blockchains</c><00:08:02.400><c> in</c><00:08:02.580><c> any</c><00:08:02.759><c> execution</c><00:08:03.180><c> layer</c>

00:08:03.589 --> 00:08:03.599 align:start position:0%
other blockchains in any execution layer
 

00:08:03.599 --> 00:08:05.990 align:start position:0%
other blockchains in any execution layer
that<00:08:04.020><c> supports</c><00:08:04.319><c> the</c><00:08:04.500><c> opcode</c><00:08:04.979><c> for</c><00:08:05.220><c> verifying</c>

00:08:05.990 --> 00:08:06.000 align:start position:0%
that supports the opcode for verifying
 

00:08:06.000 --> 00:08:07.189 align:start position:0%
that supports the opcode for verifying
ZK<00:08:06.240><c> proofs</c>

00:08:07.189 --> 00:08:07.199 align:start position:0%
ZK proofs
 

00:08:07.199 --> 00:08:09.650 align:start position:0%
ZK proofs
and<00:08:07.680><c> I</c><00:08:07.800><c> think</c><00:08:07.919><c> in</c><00:08:08.160><c> the</c><00:08:08.280><c> same</c><00:08:08.400><c> way</c><00:08:08.639><c> that</c><00:08:09.000><c> ZK</c><00:08:09.419><c> is</c>

00:08:09.650 --> 00:08:09.660 align:start position:0%
and I think in the same way that ZK is
 

00:08:09.660 --> 00:08:11.930 align:start position:0%
and I think in the same way that ZK is
being<00:08:10.020><c> used</c><00:08:10.199><c> to</c><00:08:10.440><c> scale</c><00:08:10.740><c> like</c><00:08:11.160><c> the</c><00:08:11.580><c> throughput</c>

00:08:11.930 --> 00:08:11.940 align:start position:0%
being used to scale like the throughput
 

00:08:11.940 --> 00:08:13.249 align:start position:0%
being used to scale like the throughput
of<00:08:12.060><c> blockchains</c>

00:08:13.249 --> 00:08:13.259 align:start position:0%
of blockchains
 

00:08:13.259 --> 00:08:14.270 align:start position:0%
of blockchains
um this<00:08:13.440><c> is</c><00:08:13.500><c> really</c><00:08:13.680><c> exciting</c><00:08:13.979><c> because</c><00:08:14.099><c> it's</c>

00:08:14.270 --> 00:08:14.280 align:start position:0%
um this is really exciting because it's
 

00:08:14.280 --> 00:08:15.409 align:start position:0%
um this is really exciting because it's
showing<00:08:14.460><c> that</c><00:08:14.580><c> we</c><00:08:14.699><c> can</c><00:08:14.819><c> now</c><00:08:14.940><c> scale</c><00:08:15.240><c> the</c>

00:08:15.409 --> 00:08:15.419 align:start position:0%
showing that we can now scale the
 

00:08:15.419 --> 00:08:17.210 align:start position:0%
showing that we can now scale the
verification<00:08:15.960><c> of</c><00:08:16.620><c> these</c><00:08:16.800><c> consensus</c>

00:08:17.210 --> 00:08:17.220 align:start position:0%
verification of these consensus
 

00:08:17.220 --> 00:08:19.189 align:start position:0%
verification of these consensus
algorithms

00:08:19.189 --> 00:08:19.199 align:start position:0%
algorithms
 

00:08:19.199 --> 00:08:21.469 align:start position:0%
algorithms
and<00:08:19.800><c> yeah</c><00:08:20.099><c> for</c><00:08:20.460><c> these</c><00:08:20.639><c> reasons</c><00:08:20.940><c> we're</c><00:08:21.180><c> trying</c>

00:08:21.469 --> 00:08:21.479 align:start position:0%
and yeah for these reasons we're trying
 

00:08:21.479 --> 00:08:22.909 align:start position:0%
and yeah for these reasons we're trying
to<00:08:21.660><c> coin</c><00:08:22.199><c> this</c><00:08:22.319><c> term</c><00:08:22.440><c> called</c><00:08:22.560><c> proof</c><00:08:22.860><c> of</c>

00:08:22.909 --> 00:08:22.919 align:start position:0%
to coin this term called proof of
 

00:08:22.919 --> 00:08:24.650 align:start position:0%
to coin this term called proof of
consensus<00:08:23.460><c> we're</c><00:08:23.940><c> essentially</c><00:08:24.360><c> trying</c><00:08:24.539><c> to</c>

00:08:24.650 --> 00:08:24.660 align:start position:0%
consensus we're essentially trying to
 

00:08:24.660 --> 00:08:27.350 align:start position:0%
consensus we're essentially trying to
build<00:08:24.900><c> these</c><00:08:25.319><c> Bridges</c><00:08:25.680><c> which</c><00:08:26.160><c> use</c><00:08:26.400><c> ZK</c><00:08:26.819><c> snarks</c>

00:08:27.350 --> 00:08:27.360 align:start position:0%
build these Bridges which use ZK snarks
 

00:08:27.360 --> 00:08:28.909 align:start position:0%
build these Bridges which use ZK snarks
to<00:08:27.479><c> generate</c><00:08:27.720><c> a</c><00:08:27.840><c> validity</c><00:08:28.199><c> proof</c><00:08:28.560><c> of</c><00:08:28.800><c> the</c>

00:08:28.909 --> 00:08:28.919 align:start position:0%
to generate a validity proof of the
 

00:08:28.919 --> 00:08:31.670 align:start position:0%
to generate a validity proof of the
state<00:08:29.039><c> of</c><00:08:29.280><c> some</c><00:08:29.460><c> blockchain</c>

00:08:31.670 --> 00:08:31.680 align:start position:0%
state of some blockchain
 

00:08:31.680 --> 00:08:33.350 align:start position:0%
state of some blockchain
and<00:08:32.039><c> yeah</c><00:08:32.159><c> we</c><00:08:32.399><c> believe</c><00:08:32.580><c> that</c><00:08:32.880><c> these</c><00:08:33.240><c> things</c>

00:08:33.350 --> 00:08:33.360 align:start position:0%
and yeah we believe that these things
 

00:08:33.360 --> 00:08:35.089 align:start position:0%
and yeah we believe that these things
these<00:08:34.020><c> things</c><00:08:34.200><c> called</c><00:08:34.440><c> succinct</c><00:08:34.979><c> line</c>

00:08:35.089 --> 00:08:35.099 align:start position:0%
these things called succinct line
 

00:08:35.099 --> 00:08:37.070 align:start position:0%
these things called succinct line
clients<00:08:35.520><c> will</c><00:08:35.640><c> be</c><00:08:35.820><c> sort</c><00:08:35.940><c> of</c><00:08:36.060><c> the</c><00:08:36.180><c> end</c><00:08:36.360><c> game</c><00:08:36.599><c> for</c>

00:08:37.070 --> 00:08:37.080 align:start position:0%
clients will be sort of the end game for
 

00:08:37.080 --> 00:08:38.630 align:start position:0%
clients will be sort of the end game for
cross-chain<00:08:37.560><c> interoperability</c><00:08:38.219><c> between</c>

00:08:38.630 --> 00:08:38.640 align:start position:0%
cross-chain interoperability between
 

00:08:38.640 --> 00:08:42.170 align:start position:0%
cross-chain interoperability between
many<00:08:39.539><c> different</c><00:08:39.719><c> ecosystems</c>

00:08:42.170 --> 00:08:42.180 align:start position:0%
many different ecosystems
 

00:08:42.180 --> 00:08:43.909 align:start position:0%
many different ecosystems
okay<00:08:42.719><c> so</c><00:08:43.020><c> John</c><00:08:43.200><c> gave</c><00:08:43.500><c> a</c><00:08:43.620><c> really</c><00:08:43.740><c> great</c>

00:08:43.909 --> 00:08:43.919 align:start position:0%
okay so John gave a really great
 

00:08:43.919 --> 00:08:45.590 align:start position:0%
okay so John gave a really great
overview<00:08:44.399><c> of</c><00:08:44.820><c> you</c><00:08:45.060><c> know</c><00:08:45.180><c> how</c><00:08:45.300><c> we're</c><00:08:45.480><c> going</c><00:08:45.600><c> to</c>

00:08:45.590 --> 00:08:45.600 align:start position:0%
overview of you know how we're going to
 

00:08:45.600 --> 00:08:47.150 align:start position:0%
overview of you know how we're going to
use<00:08:45.720><c> snarks</c><00:08:46.320><c> to</c><00:08:46.380><c> make</c><00:08:46.500><c> these</c><00:08:46.620><c> succinct</c><00:08:46.980><c> like</c>

00:08:47.150 --> 00:08:47.160 align:start position:0%
use snarks to make these succinct like
 

00:08:47.160 --> 00:08:49.190 align:start position:0%
use snarks to make these succinct like
clients<00:08:47.580><c> so</c><00:08:47.880><c> now</c><00:08:48.060><c> I'll</c><00:08:48.300><c> talk</c><00:08:48.540><c> more</c><00:08:48.839><c> about</c><00:08:48.959><c> the</c>

00:08:49.190 --> 00:08:49.200 align:start position:0%
clients so now I'll talk more about the
 

00:08:49.200 --> 00:08:50.990 align:start position:0%
clients so now I'll talk more about the
details<00:08:49.560><c> of</c><00:08:49.740><c> how</c><00:08:49.920><c> we</c><00:08:50.040><c> did</c><00:08:50.220><c> this</c><00:08:50.399><c> for</c><00:08:50.820><c> the</c>

00:08:50.990 --> 00:08:51.000 align:start position:0%
details of how we did this for the
 

00:08:51.000 --> 00:08:52.970 align:start position:0%
details of how we did this for the
ethereum<00:08:51.360><c> sync</c><00:08:51.660><c> committee</c><00:08:51.899><c> so</c><00:08:52.500><c> as</c><00:08:52.740><c> John</c>

00:08:52.970 --> 00:08:52.980 align:start position:0%
ethereum sync committee so as John
 

00:08:52.980 --> 00:08:54.470 align:start position:0%
ethereum sync committee so as John
mentioned<00:08:53.279><c> the</c><00:08:53.459><c> sync</c><00:08:53.760><c> committee</c><00:08:54.060><c> does</c><00:08:54.300><c> two</c>

00:08:54.470 --> 00:08:54.480 align:start position:0%
mentioned the sync committee does two
 

00:08:54.480 --> 00:08:55.970 align:start position:0%
mentioned the sync committee does two
things<00:08:54.660><c> one</c><00:08:55.080><c> is</c><00:08:55.200><c> for</c><00:08:55.440><c> every</c><00:08:55.620><c> single</c><00:08:55.860><c> block</c>

00:08:55.970 --> 00:08:55.980 align:start position:0%
things one is for every single block
 

00:08:55.980 --> 00:08:58.490 align:start position:0%
things one is for every single block
header<00:08:56.399><c> the</c><00:08:56.580><c> 512</c><00:08:57.120><c> validators</c><00:08:57.600><c> will</c><00:08:58.080><c> sign</c><00:08:58.320><c> that</c>

00:08:58.490 --> 00:08:58.500 align:start position:0%
header the 512 validators will sign that
 

00:08:58.500 --> 00:09:00.170 align:start position:0%
header the 512 validators will sign that
header<00:08:58.800><c> and</c><00:08:59.220><c> they'll</c><00:08:59.399><c> produce</c><00:08:59.700><c> an</c><00:08:59.880><c> aggregate</c>

00:09:00.170 --> 00:09:00.180 align:start position:0%
header and they'll produce an aggregate
 

00:09:00.180 --> 00:09:02.389 align:start position:0%
header and they'll produce an aggregate
BLS<00:09:00.660><c> signature</c><00:09:01.080><c> of</c><00:09:01.680><c> the</c><00:09:01.860><c> particular</c><00:09:02.160><c> block</c>

00:09:02.389 --> 00:09:02.399 align:start position:0%
BLS signature of the particular block
 

00:09:02.399 --> 00:09:04.190 align:start position:0%
BLS signature of the particular block
header<00:09:02.820><c> and</c><00:09:03.480><c> then</c><00:09:03.540><c> the</c><00:09:03.660><c> other</c><00:09:03.779><c> thing</c><00:09:03.959><c> they'll</c>

00:09:04.190 --> 00:09:04.200 align:start position:0%
header and then the other thing they'll
 

00:09:04.200 --> 00:09:05.930 align:start position:0%
header and then the other thing they'll
do<00:09:04.380><c> is</c><00:09:04.800><c> they</c><00:09:04.920><c> have</c><00:09:05.100><c> to</c><00:09:05.220><c> sign</c><00:09:05.339><c> off</c><00:09:05.519><c> on</c><00:09:05.700><c> the</c><00:09:05.820><c> new</c>

00:09:05.930 --> 00:09:05.940 align:start position:0%
do is they have to sign off on the new
 

00:09:05.940 --> 00:09:07.370 align:start position:0%
do is they have to sign off on the new
sync<00:09:06.240><c> committee</c><00:09:06.480><c> that</c><00:09:06.600><c> gets</c><00:09:06.839><c> rotated</c><00:09:07.140><c> every</c>

00:09:07.370 --> 00:09:07.380 align:start position:0%
sync committee that gets rotated every
 

00:09:07.380 --> 00:09:09.410 align:start position:0%
sync committee that gets rotated every
27<00:09:07.800><c> hours</c><00:09:08.040><c> and</c><00:09:08.519><c> it's</c><00:09:08.640><c> really</c><00:09:08.820><c> important</c><00:09:09.180><c> the</c>

00:09:09.410 --> 00:09:09.420 align:start position:0%
27 hours and it's really important the
 

00:09:09.420 --> 00:09:10.730 align:start position:0%
27 hours and it's really important the
validators<00:09:09.839><c> in</c><00:09:10.019><c> the</c><00:09:10.140><c> sync</c><00:09:10.380><c> committee</c><00:09:10.620><c> get</c>

00:09:10.730 --> 00:09:10.740 align:start position:0%
validators in the sync committee get
 

00:09:10.740 --> 00:09:12.710 align:start position:0%
validators in the sync committee get
rotated<00:09:11.100><c> every</c><00:09:11.700><c> so</c><00:09:11.940><c> often</c><00:09:12.180><c> for</c><00:09:12.360><c> like</c><00:09:12.540><c> security</c>

00:09:12.710 --> 00:09:12.720 align:start position:0%
rotated every so often for like security
 

00:09:12.720 --> 00:09:14.690 align:start position:0%
rotated every so often for like security
reasons<00:09:13.320><c> and</c><00:09:13.500><c> like</c><00:09:13.620><c> making</c><00:09:13.800><c> making</c><00:09:14.220><c> sure</c><00:09:14.459><c> that</c>

00:09:14.690 --> 00:09:14.700 align:start position:0%
reasons and like making making sure that
 

00:09:14.700 --> 00:09:17.570 align:start position:0%
reasons and like making making sure that
set<00:09:14.880><c> is</c><00:09:15.060><c> decentralized</c><00:09:16.019><c> ETC</c><00:09:16.200><c> so</c><00:09:17.160><c> we</c><00:09:17.459><c> actually</c>

00:09:17.570 --> 00:09:17.580 align:start position:0%
set is decentralized ETC so we actually
 

00:09:17.580 --> 00:09:20.210 align:start position:0%
set is decentralized ETC so we actually
have<00:09:17.880><c> two</c><00:09:18.180><c> different</c><00:09:18.360><c> snarks</c><00:09:19.019><c> so</c><00:09:19.560><c> one</c><00:09:19.800><c> snark</c>

00:09:20.210 --> 00:09:20.220 align:start position:0%
have two different snarks so one snark
 

00:09:20.220 --> 00:09:22.430 align:start position:0%
have two different snarks so one snark
verifies<00:09:20.760><c> an</c><00:09:20.940><c> aggregate</c><00:09:21.300><c> BLS</c><00:09:21.660><c> signature</c><00:09:22.080><c> of</c><00:09:22.320><c> a</c>

00:09:22.430 --> 00:09:22.440 align:start position:0%
verifies an aggregate BLS signature of a
 

00:09:22.440 --> 00:09:23.870 align:start position:0%
verifies an aggregate BLS signature of a
particular<00:09:22.680><c> block</c><00:09:22.920><c> header</c><00:09:23.339><c> and</c><00:09:23.580><c> make</c><00:09:23.700><c> sure</c>

00:09:23.870 --> 00:09:23.880 align:start position:0%
particular block header and make sure
 

00:09:23.880 --> 00:09:25.850 align:start position:0%
particular block header and make sure
that<00:09:24.060><c> like</c><00:09:24.240><c> the</c><00:09:24.480><c> signature</c><00:09:24.899><c> is</c><00:09:25.080><c> coming</c><00:09:25.320><c> from</c>

00:09:25.850 --> 00:09:25.860 align:start position:0%
that like the signature is coming from
 

00:09:25.860 --> 00:09:27.230 align:start position:0%
that like the signature is coming from
the<00:09:26.040><c> set</c><00:09:26.160><c> of</c><00:09:26.279><c> validators</c><00:09:26.700><c> in</c><00:09:26.880><c> the</c><00:09:27.000><c> sync</c>

00:09:27.230 --> 00:09:27.240 align:start position:0%
the set of validators in the sync
 

00:09:27.240 --> 00:09:29.030 align:start position:0%
the set of validators in the sync
committee<00:09:27.480><c> so</c><00:09:27.959><c> every</c><00:09:28.140><c> block</c><00:09:28.320><c> header</c><00:09:28.740><c> that</c><00:09:28.860><c> we</c>

00:09:29.030 --> 00:09:29.040 align:start position:0%
committee so every block header that we
 

00:09:29.040 --> 00:09:31.550 align:start position:0%
committee so every block header that we
want<00:09:29.220><c> to</c><00:09:29.640><c> have</c><00:09:29.940><c> accessible</c><00:09:30.720><c> in</c><00:09:31.080><c> the</c><00:09:31.200><c> execution</c>

00:09:31.550 --> 00:09:31.560 align:start position:0%
want to have accessible in the execution
 

00:09:31.560 --> 00:09:34.130 align:start position:0%
want to have accessible in the execution
layer<00:09:31.980><c> of</c><00:09:32.160><c> the</c><00:09:32.279><c> other</c><00:09:32.399><c> chain</c><00:09:32.700><c> uh</c><00:09:33.540><c> we</c><00:09:33.839><c> need</c><00:09:33.959><c> to</c>

00:09:34.130 --> 00:09:34.140 align:start position:0%
layer of the other chain uh we need to
 

00:09:34.140 --> 00:09:36.230 align:start position:0%
layer of the other chain uh we need to
generate<00:09:34.500><c> a</c><00:09:34.620><c> proof</c><00:09:34.920><c> that</c><00:09:35.279><c> this</c><00:09:35.459><c> BLS</c><00:09:35.880><c> signature</c>

00:09:36.230 --> 00:09:36.240 align:start position:0%
generate a proof that this BLS signature
 

00:09:36.240 --> 00:09:38.990 align:start position:0%
generate a proof that this BLS signature
was<00:09:36.420><c> like</c><00:09:36.660><c> actually</c><00:09:37.140><c> verified</c><00:09:37.920><c> for</c><00:09:38.820><c> that</c>

00:09:38.990 --> 00:09:39.000 align:start position:0%
was like actually verified for that
 

00:09:39.000 --> 00:09:40.430 align:start position:0%
was like actually verified for that
header<00:09:39.300><c> and</c><00:09:39.540><c> we</c><00:09:39.660><c> have</c><00:09:39.779><c> to</c><00:09:39.899><c> send</c><00:09:40.019><c> that</c><00:09:40.140><c> to</c><00:09:40.320><c> the</c>

00:09:40.430 --> 00:09:40.440 align:start position:0%
header and we have to send that to the
 

00:09:40.440 --> 00:09:41.690 align:start position:0%
header and we have to send that to the
like<00:09:40.560><c> client</c><00:09:40.920><c> contract</c><00:09:41.279><c> on</c><00:09:41.519><c> the</c><00:09:41.640><c> different</c>

00:09:41.690 --> 00:09:41.700 align:start position:0%
like client contract on the different
 

00:09:41.700 --> 00:09:44.690 align:start position:0%
like client contract on the different
chain<00:09:42.360><c> and</c><00:09:42.899><c> then</c><00:09:43.080><c> once</c><00:09:43.440><c> every</c><00:09:43.560><c> 27</c><00:09:44.040><c> hours</c><00:09:44.279><c> we</c>

00:09:44.690 --> 00:09:44.700 align:start position:0%
chain and then once every 27 hours we
 

00:09:44.700 --> 00:09:46.490 align:start position:0%
chain and then once every 27 hours we
have<00:09:44.820><c> to</c><00:09:45.060><c> generate</c><00:09:45.600><c> another</c><00:09:45.779><c> proof</c><00:09:46.200><c> that</c><00:09:46.380><c> will</c>

00:09:46.490 --> 00:09:46.500 align:start position:0%
have to generate another proof that will
 

00:09:46.500 --> 00:09:48.290 align:start position:0%
have to generate another proof that will
update<00:09:46.800><c> the</c><00:09:46.980><c> sync</c><00:09:47.220><c> committee</c><00:09:47.519><c> validators</c><00:09:47.940><c> and</c>

00:09:48.290 --> 00:09:48.300 align:start position:0%
update the sync committee validators and
 

00:09:48.300 --> 00:09:50.030 align:start position:0%
update the sync committee validators and
set<00:09:48.540><c> the</c><00:09:48.779><c> new</c><00:09:48.899><c> validator</c><00:09:49.380><c> set</c><00:09:49.620><c> that</c><00:09:49.860><c> we're</c>

00:09:50.030 --> 00:09:50.040 align:start position:0%
set the new validator set that we're
 

00:09:50.040 --> 00:09:52.009 align:start position:0%
set the new validator set that we're
going<00:09:50.160><c> to</c><00:09:50.279><c> verify</c><00:09:50.640><c> against</c><00:09:50.880><c> so</c><00:09:51.660><c> we</c><00:09:51.779><c> have</c><00:09:51.899><c> two</c>

00:09:52.009 --> 00:09:52.019 align:start position:0%
going to verify against so we have two
 

00:09:52.019 --> 00:09:53.930 align:start position:0%
going to verify against so we have two
different<00:09:52.140><c> snarks</c>

00:09:53.930 --> 00:09:53.940 align:start position:0%
different snarks
 

00:09:53.940 --> 00:09:55.970 align:start position:0%
different snarks
so<00:09:54.420><c> without</c><00:09:54.660><c> going</c><00:09:54.959><c> into</c><00:09:55.080><c> too</c><00:09:55.380><c> much</c><00:09:55.560><c> detail</c>

00:09:55.970 --> 00:09:55.980 align:start position:0%
so without going into too much detail
 

00:09:55.980 --> 00:09:57.470 align:start position:0%
so without going into too much detail
but<00:09:56.580><c> to</c><00:09:56.700><c> kind</c><00:09:56.820><c> of</c><00:09:56.940><c> cover</c><00:09:57.060><c> some</c><00:09:57.300><c> of</c><00:09:57.420><c> the</c>

00:09:57.470 --> 00:09:57.480 align:start position:0%
but to kind of cover some of the
 

00:09:57.480 --> 00:10:00.290 align:start position:0%
but to kind of cover some of the
Primitives<00:09:57.839><c> that</c><00:09:58.080><c> we</c><00:09:58.200><c> had</c><00:09:58.320><c> to</c><00:09:58.500><c> build</c><00:09:59.000><c> uh</c><00:10:00.000><c> to</c>

00:10:00.290 --> 00:10:00.300 align:start position:0%
Primitives that we had to build uh to
 

00:10:00.300 --> 00:10:01.850 align:start position:0%
Primitives that we had to build uh to
produce<00:10:00.779><c> those</c><00:10:00.959><c> snarks</c><00:10:01.380><c> that</c><00:10:01.440><c> I</c><00:10:01.500><c> mentioned</c><00:10:01.740><c> on</c>

00:10:01.850 --> 00:10:01.860 align:start position:0%
produce those snarks that I mentioned on
 

00:10:01.860 --> 00:10:04.430 align:start position:0%
produce those snarks that I mentioned on
the<00:10:01.980><c> previous</c><00:10:02.100><c> slide</c><00:10:02.519><c> we</c><00:10:03.480><c> used</c><00:10:03.600><c> a</c><00:10:04.019><c> program</c>

00:10:04.430 --> 00:10:04.440 align:start position:0%
the previous slide we used a program
 

00:10:04.440 --> 00:10:06.410 align:start position:0%
the previous slide we used a program
called<00:10:04.800><c> cross</c><00:10:05.040><c> 16</c><00:10:05.339><c> and</c><00:10:05.940><c> we</c><00:10:06.060><c> used</c><00:10:06.180><c> the</c>

00:10:06.410 --> 00:10:06.420 align:start position:0%
called cross 16 and we used the
 

00:10:06.420 --> 00:10:08.690 align:start position:0%
called cross 16 and we used the
programming<00:10:06.779><c> language</c><00:10:06.899><c> circom</c><00:10:07.560><c> invented</c><00:10:08.519><c> by</c>

00:10:08.690 --> 00:10:08.700 align:start position:0%
programming language circom invented by
 

00:10:08.700 --> 00:10:11.269 align:start position:0%
programming language circom invented by
Jordy<00:10:09.180><c> and</c><00:10:09.300><c> his</c><00:10:09.420><c> team</c><00:10:09.540><c> at</c><00:10:09.660><c> item</c><00:10:09.959><c> three</c><00:10:10.140><c> and</c><00:10:11.100><c> so</c>

00:10:11.269 --> 00:10:11.279 align:start position:0%
Jordy and his team at item three and so
 

00:10:11.279 --> 00:10:13.310 align:start position:0%
Jordy and his team at item three and so
our<00:10:11.760><c> suite</c><00:10:12.060><c> of</c><00:10:12.180><c> circuits</c><00:10:12.660><c> was</c><00:10:13.140><c> pretty</c>

00:10:13.310 --> 00:10:13.320 align:start position:0%
our suite of circuits was pretty
 

00:10:13.320 --> 00:10:15.350 align:start position:0%
our suite of circuits was pretty
complicated<00:10:13.800><c> and</c><00:10:14.339><c> resulted</c><00:10:14.760><c> in</c><00:10:14.880><c> over</c><00:10:15.120><c> 70</c>

00:10:15.350 --> 00:10:15.360 align:start position:0%
complicated and resulted in over 70
 

00:10:15.360 --> 00:10:17.810 align:start position:0%
complicated and resulted in over 70
million<00:10:15.720><c> constraints</c><00:10:16.260><c> which</c><00:10:16.680><c> is</c><00:10:16.920><c> one</c><00:10:17.580><c> of</c><00:10:17.700><c> the</c>

00:10:17.810 --> 00:10:17.820 align:start position:0%
million constraints which is one of the
 

00:10:17.820 --> 00:10:20.150 align:start position:0%
million constraints which is one of the
largest<00:10:18.120><c> circuits</c><00:10:18.839><c> that</c><00:10:18.959><c> we've</c><00:10:19.200><c> heard</c><00:10:19.440><c> of</c><00:10:19.620><c> uh</c>

00:10:20.150 --> 00:10:20.160 align:start position:0%
largest circuits that we've heard of uh
 

00:10:20.160 --> 00:10:22.790 align:start position:0%
largest circuits that we've heard of uh
being<00:10:20.399><c> used</c><00:10:20.580><c> at</c><00:10:21.480><c> least</c><00:10:21.600><c> in</c><00:10:21.779><c> surcom</c><00:10:22.140><c> and</c><00:10:22.680><c> so</c>

00:10:22.790 --> 00:10:22.800 align:start position:0%
being used at least in surcom and so
 

00:10:22.800 --> 00:10:23.930 align:start position:0%
being used at least in surcom and so
some<00:10:22.980><c> of</c><00:10:23.040><c> the</c><00:10:23.100><c> Primitives</c><00:10:23.399><c> we</c><00:10:23.580><c> had</c><00:10:23.700><c> to</c><00:10:23.820><c> build</c>

00:10:23.930 --> 00:10:23.940 align:start position:0%
some of the Primitives we had to build
 

00:10:23.940 --> 00:10:26.210 align:start position:0%
some of the Primitives we had to build
were<00:10:24.420><c> a</c><00:10:24.899><c> public</c><00:10:25.080><c> key</c><00:10:25.320><c> Edition</c><00:10:25.500><c> and</c><00:10:25.860><c> aggregate</c>

00:10:26.210 --> 00:10:26.220 align:start position:0%
were a public key Edition and aggregate
 

00:10:26.220 --> 00:10:28.009 align:start position:0%
were a public key Edition and aggregate
verification<00:10:26.700><c> so</c><00:10:27.120><c> you</c><00:10:27.300><c> basically</c><00:10:27.600><c> have</c><00:10:27.839><c> to</c>

00:10:28.009 --> 00:10:28.019 align:start position:0%
verification so you basically have to
 

00:10:28.019 --> 00:10:29.870 align:start position:0%
verification so you basically have to
add<00:10:28.380><c> up</c><00:10:28.500><c> all</c><00:10:28.680><c> the</c><00:10:28.800><c> validator</c><00:10:29.100><c> public</c><00:10:29.399><c> keys</c><00:10:29.760><c> to</c>

00:10:29.870 --> 00:10:29.880 align:start position:0%
add up all the validator public keys to
 

00:10:29.880 --> 00:10:31.790 align:start position:0%
add up all the validator public keys to
produce<00:10:30.120><c> an</c><00:10:30.300><c> aggregate</c><00:10:30.660><c> public</c><00:10:30.839><c> key</c>

00:10:31.790 --> 00:10:31.800 align:start position:0%
produce an aggregate public key
 

00:10:31.800 --> 00:10:34.190 align:start position:0%
produce an aggregate public key
we<00:10:32.279><c> also</c><00:10:32.519><c> had</c><00:10:32.640><c> to</c><00:10:32.760><c> implement</c><00:10:33.000><c> verification</c><00:10:33.660><c> of</c>

00:10:34.190 --> 00:10:34.200 align:start position:0%
we also had to implement verification of
 

00:10:34.200 --> 00:10:35.750 align:start position:0%
we also had to implement verification of
the<00:10:34.440><c> block</c><00:10:34.500><c> headers</c><00:10:34.920><c> so</c><00:10:35.100><c> this</c><00:10:35.279><c> involved</c>

00:10:35.750 --> 00:10:35.760 align:start position:0%
the block headers so this involved
 

00:10:35.760 --> 00:10:38.329 align:start position:0%
the block headers so this involved
implementing<00:10:36.660><c> pairing</c><00:10:37.019><c> in</c><00:10:37.200><c> a</c><00:10:37.320><c> snark</c><00:10:37.560><c> and</c><00:10:38.220><c> then</c>

00:10:38.329 --> 00:10:38.339 align:start position:0%
implementing pairing in a snark and then
 

00:10:38.339 --> 00:10:40.430 align:start position:0%
implementing pairing in a snark and then
having<00:10:39.180><c> the</c><00:10:39.360><c> pairing</c><00:10:39.720><c> check</c><00:10:39.899><c> the</c><00:10:40.080><c> BLS</c>

00:10:40.430 --> 00:10:40.440 align:start position:0%
having the pairing check the BLS
 

00:10:40.440 --> 00:10:42.470 align:start position:0%
having the pairing check the BLS
signature<00:10:40.860><c> which</c><00:10:41.160><c> we</c><00:10:41.459><c> other</c><00:10:42.000><c> collaborators</c>

00:10:42.470 --> 00:10:42.480 align:start position:0%
signature which we other collaborators
 

00:10:42.480 --> 00:10:44.329 align:start position:0%
signature which we other collaborators
at<00:10:42.720><c> Xerox</c><00:10:43.019><c> Park</c><00:10:43.260><c> Yi</c><00:10:43.680><c> and</c><00:10:43.800><c> Jonathan</c><00:10:44.160><c> and</c>

00:10:44.329 --> 00:10:44.339 align:start position:0%
at Xerox Park Yi and Jonathan and
 

00:10:44.339 --> 00:10:46.430 align:start position:0%
at Xerox Park Yi and Jonathan and
Vincent<00:10:44.700><c> uh</c><00:10:45.240><c> worked</c><00:10:45.540><c> on</c>

00:10:46.430 --> 00:10:46.440 align:start position:0%
Vincent uh worked on
 

00:10:46.440 --> 00:10:48.170 align:start position:0%
Vincent uh worked on
and<00:10:46.680><c> then</c><00:10:46.860><c> we</c><00:10:47.100><c> also</c><00:10:47.279><c> have</c><00:10:47.399><c> to</c><00:10:47.519><c> implement</c><00:10:47.820><c> uh</c>

00:10:48.170 --> 00:10:48.180 align:start position:0%
and then we also have to implement uh
 

00:10:48.180 --> 00:10:49.910 align:start position:0%
and then we also have to implement uh
serialization<00:10:48.720><c> methods</c><00:10:49.200><c> to</c><00:10:49.440><c> basically</c><00:10:49.740><c> check</c>

00:10:49.910 --> 00:10:49.920 align:start position:0%
serialization methods to basically check
 

00:10:49.920 --> 00:10:51.410 align:start position:0%
serialization methods to basically check
that<00:10:50.220><c> these</c><00:10:50.459><c> public</c><00:10:50.579><c> keys</c><00:10:51.060><c> are</c><00:10:51.180><c> actually</c>

00:10:51.410 --> 00:10:51.420 align:start position:0%
that these public keys are actually
 

00:10:51.420 --> 00:10:53.269 align:start position:0%
that these public keys are actually
being<00:10:51.839><c> are</c><00:10:52.380><c> actually</c><00:10:52.560><c> like</c><00:10:52.800><c> the</c><00:10:52.980><c> correct</c>

00:10:53.269 --> 00:10:53.279 align:start position:0%
being are actually like the correct
 

00:10:53.279 --> 00:10:55.850 align:start position:0%
being are actually like the correct
public<00:10:53.459><c> keys</c><00:10:53.940><c> so</c><00:10:54.240><c> we</c><00:10:54.360><c> implement</c><00:10:54.899><c> the</c><00:10:55.440><c> SSD</c>

00:10:55.850 --> 00:10:55.860 align:start position:0%
public keys so we implement the SSD
 

00:10:55.860 --> 00:10:58.490 align:start position:0%
public keys so we implement the SSD
serialization<00:10:56.399><c> that</c><00:10:56.820><c> two</c><00:10:57.240><c> uses</c><00:10:57.600><c> which</c><00:10:57.899><c> is</c><00:10:58.079><c> a</c>

00:10:58.490 --> 00:10:58.500 align:start position:0%
serialization that two uses which is a
 

00:10:58.500 --> 00:11:00.650 align:start position:0%
serialization that two uses which is a
Shaw<00:10:58.740><c> hash</c><00:10:59.100><c> function</c><00:10:59.399><c> basically</c><00:10:59.880><c> and</c><00:11:00.420><c> then</c><00:11:00.480><c> we</c>

00:11:00.650 --> 00:11:00.660 align:start position:0%
Shaw hash function basically and then we
 

00:11:00.660 --> 00:11:01.850 align:start position:0%
Shaw hash function basically and then we
also<00:11:00.839><c> had</c><00:11:00.899><c> to</c><00:11:01.079><c> implement</c><00:11:01.320><c> Poseidon</c>

00:11:01.850 --> 00:11:01.860 align:start position:0%
also had to implement Poseidon
 

00:11:01.860 --> 00:11:03.530 align:start position:0%
also had to implement Poseidon
commitments<00:11:02.399><c> to</c><00:11:02.519><c> a</c><00:11:02.640><c> vector</c><00:11:02.880><c> of</c><00:11:03.000><c> public</c><00:11:03.120><c> Keys</c>

00:11:03.530 --> 00:11:03.540 align:start position:0%
commitments to a vector of public Keys
 

00:11:03.540 --> 00:11:06.949 align:start position:0%
commitments to a vector of public Keys
which<00:11:03.660><c> is</c><00:11:03.779><c> a</c><00:11:03.959><c> snark-friendly</c><00:11:04.560><c> hash</c><00:11:04.740><c> function</c>

00:11:06.949 --> 00:11:06.959 align:start position:0%
which is a snark-friendly hash function
 

00:11:06.959 --> 00:11:09.410 align:start position:0%
which is a snark-friendly hash function
and<00:11:07.920><c> there's</c><00:11:08.160><c> one</c><00:11:08.399><c> trick</c><00:11:08.700><c> that</c><00:11:08.880><c> we</c><00:11:09.000><c> use</c><00:11:09.120><c> that</c>

00:11:09.410 --> 00:11:09.420 align:start position:0%
and there's one trick that we use that
 

00:11:09.420 --> 00:11:11.329 align:start position:0%
and there's one trick that we use that
actually<00:11:09.600><c> helped</c><00:11:10.019><c> us</c><00:11:10.079><c> significantly</c><00:11:10.680><c> save</c><00:11:11.040><c> on</c>

00:11:11.329 --> 00:11:11.339 align:start position:0%
actually helped us significantly save on
 

00:11:11.339 --> 00:11:13.370 align:start position:0%
actually helped us significantly save on
gas<00:11:11.519><c> costs</c><00:11:11.880><c> of</c><00:11:12.000><c> storing</c><00:11:12.360><c> public</c><00:11:12.480><c> keys</c><00:11:12.959><c> so</c><00:11:13.140><c> I'll</c>

00:11:13.370 --> 00:11:13.380 align:start position:0%
gas costs of storing public keys so I'll
 

00:11:13.380 --> 00:11:14.630 align:start position:0%
gas costs of storing public keys so I'll
go<00:11:13.620><c> into</c><00:11:13.740><c> that</c><00:11:13.980><c> a</c><00:11:14.100><c> little</c><00:11:14.160><c> bit</c><00:11:14.279><c> because</c><00:11:14.459><c> I</c>

00:11:14.630 --> 00:11:14.640 align:start position:0%
go into that a little bit because I
 

00:11:14.640 --> 00:11:16.850 align:start position:0%
go into that a little bit because I
think<00:11:14.760><c> it's</c><00:11:14.880><c> pretty</c><00:11:15.120><c> interesting</c><00:11:15.480><c> so</c><00:11:16.440><c> at</c><00:11:16.680><c> a</c>

00:11:16.850 --> 00:11:16.860 align:start position:0%
think it's pretty interesting so at a
 

00:11:16.860 --> 00:11:18.769 align:start position:0%
think it's pretty interesting so at a
high<00:11:16.920><c> level</c><00:11:17.040><c> snarks</c><00:11:17.700><c> have</c><00:11:17.820><c> public</c><00:11:18.240><c> and</c>

00:11:18.769 --> 00:11:18.779 align:start position:0%
high level snarks have public and
 

00:11:18.779 --> 00:11:20.990 align:start position:0%
high level snarks have public and
private<00:11:19.140><c> inputs</c><00:11:19.620><c> so</c><00:11:20.100><c> the</c><00:11:20.339><c> public</c><00:11:20.399><c> inputs</c><00:11:20.880><c> are</c>

00:11:20.990 --> 00:11:21.000 align:start position:0%
private inputs so the public inputs are
 

00:11:21.000 --> 00:11:23.030 align:start position:0%
private inputs so the public inputs are
in<00:11:21.180><c> red</c><00:11:21.300><c> because</c><00:11:21.660><c> they're</c><00:11:21.959><c> bad</c><00:11:22.200><c> because</c><00:11:22.560><c> if</c><00:11:22.860><c> we</c>

00:11:23.030 --> 00:11:23.040 align:start position:0%
in red because they're bad because if we
 

00:11:23.040 --> 00:11:25.250 align:start position:0%
in red because they're bad because if we
have<00:11:23.220><c> to</c><00:11:23.399><c> if</c><00:11:23.880><c> we</c><00:11:24.060><c> have</c><00:11:24.180><c> to</c><00:11:24.300><c> verify</c><00:11:24.660><c> a</c><00:11:24.779><c> proof</c><00:11:25.140><c> on</c>

00:11:25.250 --> 00:11:25.260 align:start position:0%
have to if we have to verify a proof on
 

00:11:25.260 --> 00:11:27.470 align:start position:0%
have to if we have to verify a proof on
chain<00:11:25.500><c> then</c><00:11:26.160><c> the</c><00:11:26.519><c> public</c><00:11:26.640><c> inputs</c><00:11:27.120><c> means</c><00:11:27.360><c> we</c>

00:11:27.470 --> 00:11:27.480 align:start position:0%
chain then the public inputs means we
 

00:11:27.480 --> 00:11:28.910 align:start position:0%
chain then the public inputs means we
also<00:11:27.720><c> have</c><00:11:27.839><c> to</c><00:11:27.959><c> put</c><00:11:28.079><c> that</c><00:11:28.200><c> data</c><00:11:28.560><c> on</c><00:11:28.680><c> chain</c>

00:11:28.910 --> 00:11:28.920 align:start position:0%
also have to put that data on chain
 

00:11:28.920 --> 00:11:31.190 align:start position:0%
also have to put that data on chain
which<00:11:29.279><c> is</c><00:11:29.399><c> expensive</c><00:11:29.940><c> private</c><00:11:30.600><c> inputs</c><00:11:31.019><c> are</c>

00:11:31.190 --> 00:11:31.200 align:start position:0%
which is expensive private inputs are
 

00:11:31.200 --> 00:11:32.449 align:start position:0%
which is expensive private inputs are
transparent<00:11:31.680><c> like</c><00:11:31.860><c> we</c><00:11:31.980><c> don't</c><00:11:32.040><c> need</c><00:11:32.220><c> to</c><00:11:32.339><c> put</c>

00:11:32.449 --> 00:11:32.459 align:start position:0%
transparent like we don't need to put
 

00:11:32.459 --> 00:11:33.889 align:start position:0%
transparent like we don't need to put
them<00:11:32.579><c> on</c><00:11:32.700><c> chain</c><00:11:32.880><c> when</c><00:11:33.180><c> we're</c><00:11:33.300><c> verifying</c><00:11:33.779><c> this</c>

00:11:33.889 --> 00:11:33.899 align:start position:0%
them on chain when we're verifying this
 

00:11:33.899 --> 00:11:36.829 align:start position:0%
them on chain when we're verifying this
proof<00:11:34.740><c> so</c><00:11:35.339><c> if</c><00:11:35.820><c> we</c><00:11:36.060><c> were</c><00:11:36.180><c> to</c><00:11:36.300><c> implement</c><00:11:36.660><c> the</c>

00:11:36.829 --> 00:11:36.839 align:start position:0%
proof so if we were to implement the
 

00:11:36.839 --> 00:11:39.650 align:start position:0%
proof so if we were to implement the
verification<00:11:37.320><c> snark</c><00:11:37.920><c> we</c><00:11:38.880><c> would</c><00:11:39.000><c> have</c><00:11:39.240><c> all</c><00:11:39.540><c> the</c>

00:11:39.650 --> 00:11:39.660 align:start position:0%
verification snark we would have all the
 

00:11:39.660 --> 00:11:41.810 align:start position:0%
verification snark we would have all the
public<00:11:39.839><c> Keys</c><00:11:40.260><c> as</c><00:11:40.440><c> a</c><00:11:40.620><c> public</c><00:11:40.800><c> input</c><00:11:41.220><c> because</c><00:11:41.579><c> we</c>

00:11:41.810 --> 00:11:41.820 align:start position:0%
public Keys as a public input because we
 

00:11:41.820 --> 00:11:43.190 align:start position:0%
public Keys as a public input because we
need<00:11:41.940><c> to</c><00:11:42.060><c> make</c><00:11:42.180><c> sure</c><00:11:42.360><c> the</c><00:11:42.600><c> public</c><00:11:42.779><c> Keys</c>

00:11:43.190 --> 00:11:43.200 align:start position:0%
need to make sure the public Keys
 

00:11:43.200 --> 00:11:46.150 align:start position:0%
need to make sure the public Keys
correspond<00:11:43.680><c> to</c><00:11:43.920><c> the</c><00:11:44.339><c> correct</c><00:11:44.940><c> validator</c><00:11:45.360><c> set</c>

00:11:46.150 --> 00:11:46.160 align:start position:0%
correspond to the correct validator set
 

00:11:46.160 --> 00:11:48.290 align:start position:0%
correspond to the correct validator set
unfortunately<00:11:47.160><c> storing</c><00:11:47.760><c> public</c><00:11:47.880><c> keys</c><00:11:48.240><c> on</c>

00:11:48.290 --> 00:11:48.300 align:start position:0%
unfortunately storing public keys on
 

00:11:48.300 --> 00:11:50.150 align:start position:0%
unfortunately storing public keys on
chain<00:11:48.480><c> is</c><00:11:48.660><c> really</c><00:11:48.839><c> expensive</c><00:11:49.260><c> so</c><00:11:49.740><c> our</c><00:11:49.860><c> idea</c>

00:11:50.150 --> 00:11:50.160 align:start position:0%
chain is really expensive so our idea
 

00:11:50.160 --> 00:11:52.250 align:start position:0%
chain is really expensive so our idea
was<00:11:50.339><c> we</c><00:11:50.579><c> could</c><00:11:50.700><c> store</c><00:11:50.940><c> to</c><00:11:51.540><c> the</c><00:11:51.779><c> public</c><00:11:51.839><c> Keys</c>

00:11:52.250 --> 00:11:52.260 align:start position:0%
was we could store to the public Keys
 

00:11:52.260 --> 00:11:54.889 align:start position:0%
was we could store to the public Keys
instead<00:11:52.620><c> so</c><00:11:52.920><c> we</c><00:11:53.100><c> can</c><00:11:53.220><c> store</c><00:11:53.519><c> the</c><00:11:54.420><c> public</c><00:11:54.480><c> Keys</c>

00:11:54.889 --> 00:11:54.899 align:start position:0%
instead so we can store the public Keys
 

00:11:54.899 --> 00:11:56.930 align:start position:0%
instead so we can store the public Keys
as<00:11:55.079><c> a</c><00:11:55.200><c> private</c><00:11:55.440><c> input</c><00:11:55.740><c> in</c><00:11:56.040><c> the</c><00:11:56.160><c> snark</c><00:11:56.459><c> as</c><00:11:56.820><c> you</c>

00:11:56.930 --> 00:11:56.940 align:start position:0%
as a private input in the snark as you
 

00:11:56.940 --> 00:11:59.090 align:start position:0%
as a private input in the snark as you
can<00:11:57.060><c> see</c><00:11:57.180><c> here</c><00:11:57.420><c> it</c><00:11:57.660><c> turns</c><00:11:58.079><c> into</c><00:11:58.200><c> green</c><00:11:58.500><c> and</c>

00:11:59.090 --> 00:11:59.100 align:start position:0%
can see here it turns into green and
 

00:11:59.100 --> 00:12:00.410 align:start position:0%
can see here it turns into green and
then<00:11:59.160><c> the</c><00:11:59.399><c> public</c><00:11:59.519><c> input</c><00:11:59.940><c> becomes</c><00:12:00.240><c> this</c>

00:12:00.410 --> 00:12:00.420 align:start position:0%
then the public input becomes this
 

00:12:00.420 --> 00:12:01.850 align:start position:0%
then the public input becomes this
commitment<00:12:00.779><c> which</c><00:12:01.079><c> is</c><00:12:01.200><c> basically</c><00:12:01.500><c> like</c><00:12:01.680><c> a</c>

00:12:01.850 --> 00:12:01.860 align:start position:0%
commitment which is basically like a
 

00:12:01.860 --> 00:12:02.870 align:start position:0%
commitment which is basically like a
hash<00:12:02.040><c> of</c><00:12:02.220><c> the</c>

00:12:02.870 --> 00:12:02.880 align:start position:0%
hash of the
 

00:12:02.880 --> 00:12:05.569 align:start position:0%
hash of the
public<00:12:03.420><c> keys</c><00:12:03.959><c> and</c><00:12:04.260><c> it's</c><00:12:04.440><c> like</c><00:12:04.560><c> much</c><00:12:04.740><c> shorter</c>

00:12:05.569 --> 00:12:05.579 align:start position:0%
public keys and it's like much shorter
 

00:12:05.579 --> 00:12:07.370 align:start position:0%
public keys and it's like much shorter
but<00:12:06.060><c> then</c><00:12:06.180><c> the</c><00:12:06.360><c> question</c><00:12:06.480><c> is</c><00:12:06.720><c> how</c><00:12:07.140><c> do</c><00:12:07.260><c> we</c>

00:12:07.370 --> 00:12:07.380 align:start position:0%
but then the question is how do we
 

00:12:07.380 --> 00:12:08.630 align:start position:0%
but then the question is how do we
update<00:12:07.620><c> the</c><00:12:07.800><c> commitment</c><00:12:08.040><c> once</c><00:12:08.339><c> the</c><00:12:08.399><c> committee</c>

00:12:08.630 --> 00:12:08.640 align:start position:0%
update the commitment once the committee
 

00:12:08.640 --> 00:12:10.190 align:start position:0%
update the commitment once the committee
rotates

00:12:10.190 --> 00:12:10.200 align:start position:0%
rotates
 

00:12:10.200 --> 00:12:12.889 align:start position:0%
rotates
so<00:12:10.740><c> one</c><00:12:11.100><c> idea</c><00:12:11.399><c> is</c><00:12:11.700><c> that</c><00:12:11.940><c> when</c><00:12:12.360><c> the</c><00:12:12.779><c> current</c>

00:12:12.889 --> 00:12:12.899 align:start position:0%
so one idea is that when the current
 

00:12:12.899 --> 00:12:14.930 align:start position:0%
so one idea is that when the current
sync<00:12:13.260><c> committee</c><00:12:13.560><c> is</c><00:12:13.740><c> signing</c><00:12:14.220><c> the</c><00:12:14.579><c> rotation</c>

00:12:14.930 --> 00:12:14.940 align:start position:0%
sync committee is signing the rotation
 

00:12:14.940 --> 00:12:16.670 align:start position:0%
sync committee is signing the rotation
of<00:12:15.120><c> the</c><00:12:15.240><c> new</c><00:12:15.300><c> sync</c><00:12:15.720><c> committee</c><00:12:16.019><c> they</c><00:12:16.380><c> basically</c>

00:12:16.670 --> 00:12:16.680 align:start position:0%
of the new sync committee they basically
 

00:12:16.680 --> 00:12:18.829 align:start position:0%
of the new sync committee they basically
sign<00:12:16.980><c> an</c><00:12:17.220><c> SSD</c><00:12:17.760><c> which</c><00:12:18.060><c> is</c><00:12:18.180><c> this</c><00:12:18.360><c> eth2</c>

00:12:18.829 --> 00:12:18.839 align:start position:0%
sign an SSD which is this eth2
 

00:12:18.839 --> 00:12:21.350 align:start position:0%
sign an SSD which is this eth2
serialization<00:12:19.380><c> they</c><00:12:19.740><c> use</c><00:12:19.920><c> of</c><00:12:20.760><c> the</c><00:12:21.000><c> new</c><00:12:21.120><c> public</c>

00:12:21.350 --> 00:12:21.360 align:start position:0%
serialization they use of the new public
 

00:12:21.360 --> 00:12:24.050 align:start position:0%
serialization they use of the new public
keys<00:12:21.899><c> and</c><00:12:22.380><c> so</c><00:12:22.560><c> we</c><00:12:22.800><c> could</c><00:12:22.920><c> just</c><00:12:23.100><c> use</c><00:12:23.279><c> this</c><00:12:23.519><c> SSD</c>

00:12:24.050 --> 00:12:24.060 align:start position:0%
keys and so we could just use this SSD
 

00:12:24.060 --> 00:12:25.850 align:start position:0%
keys and so we could just use this SSD
serialization<00:12:24.600><c> of</c><00:12:24.779><c> the</c><00:12:24.899><c> new</c><00:12:25.019><c> public</c><00:12:25.200><c> Keys</c><00:12:25.620><c> as</c>

00:12:25.850 --> 00:12:25.860 align:start position:0%
serialization of the new public Keys as
 

00:12:25.860 --> 00:12:26.990 align:start position:0%
serialization of the new public Keys as
the<00:12:26.040><c> commitment</c>

00:12:26.990 --> 00:12:27.000 align:start position:0%
the commitment
 

00:12:27.000 --> 00:12:29.090 align:start position:0%
the commitment
but<00:12:27.360><c> the</c><00:12:27.480><c> problem</c><00:12:27.600><c> is</c><00:12:27.779><c> ssds</c><00:12:28.500><c> really</c><00:12:28.740><c> snark</c>

00:12:29.090 --> 00:12:29.100 align:start position:0%
but the problem is ssds really snark
 

00:12:29.100 --> 00:12:31.730 align:start position:0%
but the problem is ssds really snark
unfriendly<00:12:29.820><c> uh</c><00:12:30.540><c> because</c><00:12:30.660><c> it's</c><00:12:31.079><c> a</c><00:12:31.260><c> bunch</c><00:12:31.560><c> of</c>

00:12:31.730 --> 00:12:31.740 align:start position:0%
unfriendly uh because it's a bunch of
 

00:12:31.740 --> 00:12:33.889 align:start position:0%
unfriendly uh because it's a bunch of
Shaw<00:12:31.920><c> hashes</c><00:12:32.399><c> so</c><00:12:32.820><c> it's</c><00:12:32.940><c> really</c><00:12:33.180><c> expensive</c><00:12:33.600><c> to</c>

00:12:33.889 --> 00:12:33.899 align:start position:0%
Shaw hashes so it's really expensive to
 

00:12:33.899 --> 00:12:35.449 align:start position:0%
Shaw hashes so it's really expensive to
compute<00:12:34.260><c> in</c><00:12:34.560><c> every</c><00:12:34.740><c> header</c><00:12:35.040><c> verification</c>

00:12:35.449 --> 00:12:35.459 align:start position:0%
compute in every header verification
 

00:12:35.459 --> 00:12:39.470 align:start position:0%
compute in every header verification
snark<00:12:36.000><c> and</c><00:12:36.959><c> so</c><00:12:37.200><c> what</c><00:12:37.740><c> we</c><00:12:37.920><c> our</c><00:12:38.459><c> idea</c><00:12:38.760><c> was</c><00:12:39.060><c> what</c>

00:12:39.470 --> 00:12:39.480 align:start position:0%
snark and so what we our idea was what
 

00:12:39.480 --> 00:12:41.690 align:start position:0%
snark and so what we our idea was what
we<00:12:39.660><c> could</c><00:12:39.779><c> do</c><00:12:39.959><c> is</c><00:12:40.140><c> we</c><00:12:40.320><c> could</c><00:12:40.440><c> map</c><00:12:40.740><c> this</c><00:12:41.279><c> snark</c>

00:12:41.690 --> 00:12:41.700 align:start position:0%
we could do is we could map this snark
 

00:12:41.700 --> 00:12:44.150 align:start position:0%
we could do is we could map this snark
unfriendly<00:12:42.360><c> SSD</c><00:12:43.019><c> to</c><00:12:43.440><c> a</c><00:12:43.560><c> snark-friendly</c>

00:12:44.150 --> 00:12:44.160 align:start position:0%
unfriendly SSD to a snark-friendly
 

00:12:44.160 --> 00:12:46.190 align:start position:0%
unfriendly SSD to a snark-friendly
commitment<00:12:44.519><c> and</c><00:12:45.060><c> so</c><00:12:45.240><c> our</c><00:12:45.480><c> second</c><00:12:45.600><c> snark</c><00:12:46.019><c> that</c>

00:12:46.190 --> 00:12:46.200 align:start position:0%
commitment and so our second snark that
 

00:12:46.200 --> 00:12:47.990 align:start position:0%
commitment and so our second snark that
I<00:12:46.320><c> mentioned</c><00:12:46.560><c> below</c><00:12:46.920><c> for</c><00:12:47.100><c> the</c><00:12:47.279><c> sync</c><00:12:47.639><c> committee</c>

00:12:47.990 --> 00:12:48.000 align:start position:0%
I mentioned below for the sync committee
 

00:12:48.000 --> 00:12:50.870 align:start position:0%
I mentioned below for the sync committee
rotation<00:12:48.300><c> basically</c><00:12:49.200><c> Maps</c><00:12:49.920><c> it</c><00:12:50.220><c> takes</c><00:12:50.459><c> in</c><00:12:50.700><c> the</c>

00:12:50.870 --> 00:12:50.880 align:start position:0%
rotation basically Maps it takes in the
 

00:12:50.880 --> 00:12:53.530 align:start position:0%
rotation basically Maps it takes in the
public<00:12:51.060><c> keys</c><00:12:51.540><c> and</c><00:12:51.899><c> then</c><00:12:52.019><c> it</c><00:12:52.139><c> produces</c><00:12:52.560><c> the</c><00:12:52.860><c> SSD</c>

00:12:53.530 --> 00:12:53.540 align:start position:0%
public keys and then it produces the SSD
 

00:12:53.540 --> 00:12:55.790 align:start position:0%
public keys and then it produces the SSD
commitment<00:12:54.540><c> and</c><00:12:54.899><c> then</c><00:12:55.019><c> also</c><00:12:55.260><c> produces</c><00:12:55.620><c> a</c>

00:12:55.790 --> 00:12:55.800 align:start position:0%
commitment and then also produces a
 

00:12:55.800 --> 00:12:57.050 align:start position:0%
commitment and then also produces a
snark<00:12:56.040><c> friendly</c><00:12:56.339><c> commitment</c><00:12:56.639><c> called</c><00:12:56.940><c> a</c>

00:12:57.050 --> 00:12:57.060 align:start position:0%
snark friendly commitment called a
 

00:12:57.060 --> 00:12:58.790 align:start position:0%
snark friendly commitment called a
Poseidon<00:12:57.480><c> commitment</c><00:12:57.839><c> and</c><00:12:58.380><c> then</c><00:12:58.440><c> it</c><00:12:58.620><c> just</c>

00:12:58.790 --> 00:12:58.800 align:start position:0%
Poseidon commitment and then it just
 

00:12:58.800 --> 00:13:00.110 align:start position:0%
Poseidon commitment and then it just
asserts<00:12:59.160><c> that</c><00:12:59.279><c> those</c><00:12:59.459><c> two</c><00:12:59.639><c> things</c><00:12:59.760><c> are</c><00:12:59.940><c> the</c>

00:13:00.110 --> 00:13:00.120 align:start position:0%
asserts that those two things are the
 

00:13:00.120 --> 00:13:02.030 align:start position:0%
asserts that those two things are the
same<00:13:00.300><c> and</c><00:13:00.899><c> the</c><00:13:01.079><c> bottom</c><00:13:01.320><c> line</c><00:13:01.440><c> is</c><00:13:01.620><c> that</c><00:13:01.800><c> we</c><00:13:01.920><c> were</c>

00:13:02.030 --> 00:13:02.040 align:start position:0%
same and the bottom line is that we were
 

00:13:02.040 --> 00:13:03.650 align:start position:0%
same and the bottom line is that we were
able<00:13:02.279><c> to</c><00:13:02.399><c> save</c><00:13:02.639><c> around</c><00:13:02.940><c> 70</c><00:13:03.300><c> million</c>

00:13:03.650 --> 00:13:03.660 align:start position:0%
able to save around 70 million
 

00:13:03.660 --> 00:13:05.210 align:start position:0%
able to save around 70 million
constraints<00:13:04.079><c> in</c><00:13:04.320><c> our</c><00:13:04.440><c> header</c><00:13:04.740><c> verification</c>

00:13:05.210 --> 00:13:05.220 align:start position:0%
constraints in our header verification
 

00:13:05.220 --> 00:13:07.490 align:start position:0%
constraints in our header verification
snark<00:13:05.639><c> which</c><00:13:05.880><c> we</c><00:13:06.060><c> run</c><00:13:06.240><c> every</c><00:13:06.779><c> update</c><00:13:07.200><c> that</c><00:13:07.320><c> we</c>

00:13:07.490 --> 00:13:07.500 align:start position:0%
snark which we run every update that we
 

00:13:07.500 --> 00:13:09.410 align:start position:0%
snark which we run every update that we
want<00:13:07.680><c> which</c><00:13:08.279><c> is</c><00:13:08.399><c> like</c><00:13:08.579><c> a</c><00:13:08.700><c> huge</c><00:13:08.880><c> savings</c><00:13:09.180><c> in</c>

00:13:09.410 --> 00:13:09.420 align:start position:0%
want which is like a huge savings in
 

00:13:09.420 --> 00:13:11.870 align:start position:0%
want which is like a huge savings in
terms<00:13:09.600><c> of</c><00:13:09.660><c> proving</c><00:13:10.019><c> time</c>

00:13:11.870 --> 00:13:11.880 align:start position:0%
terms of proving time
 

00:13:11.880 --> 00:13:14.990 align:start position:0%
terms of proving time
and<00:13:12.420><c> just</c><00:13:12.600><c> for</c><00:13:12.779><c> some</c><00:13:12.899><c> benchmarks</c><00:13:13.500><c> so</c><00:13:13.800><c> our</c><00:13:14.639><c> sync</c>

00:13:14.990 --> 00:13:15.000 align:start position:0%
and just for some benchmarks so our sync
 

00:13:15.000 --> 00:13:17.030 align:start position:0%
and just for some benchmarks so our sync
committee<00:13:15.240><c> rotation</c><00:13:15.600><c> snark</c><00:13:16.019><c> has</c><00:13:16.500><c> the</c><00:13:16.680><c> SSD</c>

00:13:17.030 --> 00:13:17.040 align:start position:0%
committee rotation snark has the SSD
 

00:13:17.040 --> 00:13:19.009 align:start position:0%
committee rotation snark has the SSD
computation<00:13:17.579><c> so</c><00:13:17.880><c> that's</c><00:13:18.000><c> why</c><00:13:18.240><c> it</c><00:13:18.480><c> has</c><00:13:18.600><c> 68</c>

00:13:19.009 --> 00:13:19.019 align:start position:0%
computation so that's why it has 68
 

00:13:19.019 --> 00:13:20.509 align:start position:0%
computation so that's why it has 68
million<00:13:19.320><c> constraints</c><00:13:19.680><c> which</c><00:13:19.980><c> is</c><00:13:20.100><c> quite</c><00:13:20.220><c> a</c><00:13:20.399><c> lot</c>

00:13:20.509 --> 00:13:20.519 align:start position:0%
million constraints which is quite a lot
 

00:13:20.519 --> 00:13:23.569 align:start position:0%
million constraints which is quite a lot
uh<00:13:21.240><c> thankfully</c><00:13:21.600><c> the</c><00:13:21.779><c> proving</c><00:13:22.079><c> time</c><00:13:22.380><c> uh</c><00:13:23.100><c> is</c><00:13:23.339><c> not</c>

00:13:23.569 --> 00:13:23.579 align:start position:0%
uh thankfully the proving time uh is not
 

00:13:23.579 --> 00:13:25.129 align:start position:0%
uh thankfully the proving time uh is not
that<00:13:23.700><c> bad</c><00:13:23.880><c> it's</c><00:13:24.120><c> four</c><00:13:24.360><c> minutes</c><00:13:24.600><c> and</c><00:13:25.019><c> that's</c>

00:13:25.129 --> 00:13:25.139 align:start position:0%
that bad it's four minutes and that's
 

00:13:25.139 --> 00:13:27.650 align:start position:0%
that bad it's four minutes and that's
the<00:13:25.320><c> snark</c><00:13:25.620><c> we</c><00:13:25.800><c> run</c><00:13:25.980><c> every</c><00:13:26.160><c> 27</c><00:13:26.639><c> hours</c><00:13:26.880><c> and</c><00:13:27.600><c> then</c>

00:13:27.650 --> 00:13:27.660 align:start position:0%
the snark we run every 27 hours and then
 

00:13:27.660 --> 00:13:29.569 align:start position:0%
the snark we run every 27 hours and then
we<00:13:27.839><c> have</c><00:13:27.899><c> another</c><00:13:28.019><c> that's</c><00:13:28.980><c> verifying</c><00:13:29.519><c> the</c>

00:13:29.569 --> 00:13:29.579 align:start position:0%
we have another that's verifying the
 

00:13:29.579 --> 00:13:31.430 align:start position:0%
we have another that's verifying the
signed<00:13:29.940><c> header</c><00:13:30.180><c> that</c><00:13:30.420><c> has</c><00:13:30.600><c> around</c><00:13:30.839><c> 20</c><00:13:31.079><c> million</c>

00:13:31.430 --> 00:13:31.440 align:start position:0%
signed header that has around 20 million
 

00:13:31.440 --> 00:13:33.230 align:start position:0%
signed header that has around 20 million
constraints<00:13:31.860><c> and</c><00:13:32.160><c> it's</c><00:13:32.339><c> proving</c><00:13:32.700><c> times</c><00:13:32.820><c> also</c>

00:13:33.230 --> 00:13:33.240 align:start position:0%
constraints and it's proving times also
 

00:13:33.240 --> 00:13:36.370 align:start position:0%
constraints and it's proving times also
around<00:13:33.420><c> four</c><00:13:33.720><c> minutes</c>

00:13:36.370 --> 00:13:36.380 align:start position:0%
 
 

00:13:36.380 --> 00:13:38.870 align:start position:0%
 
yeah<00:13:37.380><c> so</c><00:13:37.560><c> everything</c><00:13:37.740><c> that</c><00:13:38.100><c> me</c><00:13:38.279><c> anduma</c><00:13:38.760><c> have</c>

00:13:38.870 --> 00:13:38.880 align:start position:0%
yeah so everything that me anduma have
 

00:13:38.880 --> 00:13:40.190 align:start position:0%
yeah so everything that me anduma have
we've<00:13:39.180><c> described</c><00:13:39.480><c> here</c><00:13:39.600><c> we</c><00:13:39.959><c> have</c><00:13:40.079><c> like</c>

00:13:40.190 --> 00:13:40.200 align:start position:0%
we've described here we have like
 

00:13:40.200 --> 00:13:42.170 align:start position:0%
we've described here we have like
working<00:13:40.440><c> prototypes</c><00:13:41.279><c> of</c><00:13:41.399><c> it</c><00:13:41.579><c> and</c><00:13:41.880><c> we</c><00:13:42.000><c> actually</c>

00:13:42.170 --> 00:13:42.180 align:start position:0%
working prototypes of it and we actually
 

00:13:42.180 --> 00:13:44.930 align:start position:0%
working prototypes of it and we actually
built<00:13:42.720><c> a</c><00:13:43.440><c> two-way</c><00:13:43.920><c> like</c><00:13:44.339><c> client</c><00:13:44.760><c> bridge</c>

00:13:44.930 --> 00:13:44.940 align:start position:0%
built a two-way like client bridge
 

00:13:44.940 --> 00:13:48.170 align:start position:0%
built a two-way like client bridge
between<00:13:45.540><c> gorily</c><00:13:46.440><c> and</c><00:13:46.920><c> gnosis</c><00:13:47.339><c> chain</c><00:13:47.639><c> which</c><00:13:48.000><c> is</c>

00:13:48.170 --> 00:13:48.180 align:start position:0%
between gorily and gnosis chain which is
 

00:13:48.180 --> 00:13:49.730 align:start position:0%
between gorily and gnosis chain which is
actually

00:13:49.730 --> 00:13:49.740 align:start position:0%
actually
 

00:13:49.740 --> 00:13:52.129 align:start position:0%
actually
um another<00:13:50.220><c> L1</c><00:13:50.700><c> which</c><00:13:51.120><c> implements</c><00:13:51.660><c> ethereum</c>

00:13:52.129 --> 00:13:52.139 align:start position:0%
um another L1 which implements ethereum
 

00:13:52.139 --> 00:13:53.569 align:start position:0%
um another L1 which implements ethereum
because<00:13:52.320><c> that's</c><00:13:52.500><c> exactly</c><00:13:52.860><c> so</c><00:13:53.100><c> we're</c><00:13:53.220><c> able</c><00:13:53.459><c> to</c>

00:13:53.569 --> 00:13:53.579 align:start position:0%
because that's exactly so we're able to
 

00:13:53.579 --> 00:13:56.750 align:start position:0%
because that's exactly so we're able to
reuse<00:13:53.880><c> many</c><00:13:54.240><c> of</c><00:13:54.360><c> our</c><00:13:54.540><c> circuits</c><00:13:55.220><c> so</c><00:13:56.220><c> we</c><00:13:56.459><c> have</c><00:13:56.579><c> a</c>

00:13:56.750 --> 00:13:56.760 align:start position:0%
reuse many of our circuits so we have a
 

00:13:56.760 --> 00:13:59.210 align:start position:0%
reuse many of our circuits so we have a
demo<00:13:57.120><c> demo</c><00:13:57.420><c> succinct</c><00:13:57.839><c> XYZ</c><00:13:58.320><c> and</c><00:13:58.680><c> fair</c><00:13:58.920><c> warning</c>

00:13:59.210 --> 00:13:59.220 align:start position:0%
demo demo succinct XYZ and fair warning
 

00:13:59.220 --> 00:14:00.889 align:start position:0%
demo demo succinct XYZ and fair warning
it's<00:13:59.339><c> in</c><00:13:59.519><c> beta</c><00:13:59.880><c> and</c><00:14:00.000><c> it</c><00:14:00.180><c> works</c><00:14:00.420><c> much</c><00:14:00.540><c> better</c><00:14:00.720><c> on</c>

00:14:00.889 --> 00:14:00.899 align:start position:0%
it's in beta and it works much better on
 

00:14:00.899 --> 00:14:03.290 align:start position:0%
it's in beta and it works much better on
your<00:14:01.079><c> laptop</c><00:14:01.519><c> but</c><00:14:02.519><c> here</c><00:14:02.760><c> we</c><00:14:03.060><c> have</c><00:14:03.120><c> some</c>

00:14:03.290 --> 00:14:03.300 align:start position:0%
your laptop but here we have some
 

00:14:03.300 --> 00:14:05.449 align:start position:0%
your laptop but here we have some
screenshots<00:14:03.720><c> of</c><00:14:04.380><c> like</c><00:14:04.560><c> what</c><00:14:04.740><c> it</c><00:14:04.860><c> can</c><00:14:04.980><c> do</c><00:14:05.100><c> so</c>

00:14:05.449 --> 00:14:05.459 align:start position:0%
screenshots of like what it can do so
 

00:14:05.459 --> 00:14:07.550 align:start position:0%
screenshots of like what it can do so
basically<00:14:05.940><c> you</c><00:14:06.300><c> know</c><00:14:06.420><c> you</c><00:14:07.139><c> choose</c><00:14:07.380><c> your</c>

00:14:07.550 --> 00:14:07.560 align:start position:0%
basically you know you choose your
 

00:14:07.560 --> 00:14:09.110 align:start position:0%
basically you know you choose your
networks<00:14:07.980><c> right</c><00:14:08.279><c> now</c><00:14:08.459><c> we</c><00:14:08.579><c> only</c><00:14:08.700><c> have</c><00:14:08.880><c> like</c><00:14:09.000><c> one</c>

00:14:09.110 --> 00:14:09.120 align:start position:0%
networks right now we only have like one
 

00:14:09.120 --> 00:14:10.790 align:start position:0%
networks right now we only have like one
pair<00:14:09.300><c> obviously</c><00:14:09.779><c> and</c><00:14:10.200><c> you</c><00:14:10.380><c> choose</c><00:14:10.680><c> your</c>

00:14:10.790 --> 00:14:10.800 align:start position:0%
pair obviously and you choose your
 

00:14:10.800 --> 00:14:12.590 align:start position:0%
pair obviously and you choose your
currency<00:14:11.100><c> and</c><00:14:11.820><c> yeah</c><00:14:11.940><c> you</c><00:14:12.180><c> can</c><00:14:12.240><c> just</c><00:14:12.360><c> Bridge</c>

00:14:12.590 --> 00:14:12.600 align:start position:0%
currency and yeah you can just Bridge
 

00:14:12.600 --> 00:14:15.170 align:start position:0%
currency and yeah you can just Bridge
the<00:14:13.079><c> tokens</c><00:14:13.380><c> you</c><00:14:14.160><c> send</c><00:14:14.399><c> a</c><00:14:14.760><c> deposit</c>

00:14:15.170 --> 00:14:15.180 align:start position:0%
the tokens you send a deposit
 

00:14:15.180 --> 00:14:16.250 align:start position:0%
the tokens you send a deposit
transaction

00:14:16.250 --> 00:14:16.260 align:start position:0%
transaction
 

00:14:16.260 --> 00:14:18.110 align:start position:0%
transaction
and<00:14:16.800><c> essentially</c><00:14:17.160><c> what's</c><00:14:17.459><c> going</c><00:14:17.700><c> on</c><00:14:17.820><c> behind</c>

00:14:18.110 --> 00:14:18.120 align:start position:0%
and essentially what's going on behind
 

00:14:18.120 --> 00:14:20.569 align:start position:0%
and essentially what's going on behind
the<00:14:18.240><c> scenes</c><00:14:18.540><c> here</c><00:14:18.660><c> is</c><00:14:19.200><c> quite</c><00:14:19.380><c> interesting</c><00:14:19.740><c> so</c>

00:14:20.569 --> 00:14:20.579 align:start position:0%
the scenes here is quite interesting so
 

00:14:20.579 --> 00:14:22.210 align:start position:0%
the scenes here is quite interesting so
when<00:14:20.880><c> you</c><00:14:21.000><c> make</c><00:14:21.180><c> your</c><00:14:21.420><c> deposit</c><00:14:21.839><c> transaction</c>

00:14:22.210 --> 00:14:22.220 align:start position:0%
when you make your deposit transaction
 

00:14:22.220 --> 00:14:25.069 align:start position:0%
when you make your deposit transaction
it<00:14:23.220><c> basically</c><00:14:23.459><c> stores</c><00:14:23.940><c> some</c><00:14:24.300><c> data</c><00:14:24.600><c> on</c><00:14:24.899><c> some</c>

00:14:25.069 --> 00:14:25.079 align:start position:0%
it basically stores some data on some
 

00:14:25.079 --> 00:14:27.470 align:start position:0%
it basically stores some data on some
contract<00:14:25.440><c> on</c><00:14:25.680><c> corally</c><00:14:26.519><c> that</c><00:14:27.000><c> indicates</c><00:14:27.300><c> that</c>

00:14:27.470 --> 00:14:27.480 align:start position:0%
contract on corally that indicates that
 

00:14:27.480 --> 00:14:29.449 align:start position:0%
contract on corally that indicates that
you've<00:14:27.600><c> made</c><00:14:27.720><c> a</c><00:14:27.899><c> deposit</c><00:14:28.320><c> and</c><00:14:29.040><c> what</c><00:14:29.220><c> you</c><00:14:29.339><c> have</c>

00:14:29.449 --> 00:14:29.459 align:start position:0%
you've made a deposit and what you have
 

00:14:29.459 --> 00:14:31.069 align:start position:0%
you've made a deposit and what you have
to<00:14:29.579><c> wait</c><00:14:29.700><c> for</c><00:14:29.940><c> is</c><00:14:30.300><c> essentially</c><00:14:30.600><c> for</c><00:14:30.779><c> the</c><00:14:30.959><c> like</c>

00:14:31.069 --> 00:14:31.079 align:start position:0%
to wait for is essentially for the like
 

00:14:31.079 --> 00:14:33.470 align:start position:0%
to wait for is essentially for the like
client<00:14:31.500><c> on</c><00:14:31.920><c> the</c><00:14:32.040><c> target</c><00:14:32.160><c> chain</c><00:14:32.459><c> gnosis</c><00:14:33.300><c> in</c>

00:14:33.470 --> 00:14:33.480 align:start position:0%
client on the target chain gnosis in
 

00:14:33.480 --> 00:14:35.389 align:start position:0%
client on the target chain gnosis in
this<00:14:33.600><c> case</c><00:14:33.720><c> to</c><00:14:34.260><c> be</c><00:14:34.380><c> updated</c><00:14:34.740><c> with</c><00:14:35.100><c> a</c><00:14:35.220><c> block</c>

00:14:35.389 --> 00:14:35.399 align:start position:0%
this case to be updated with a block
 

00:14:35.399 --> 00:14:37.190 align:start position:0%
this case to be updated with a block
header<00:14:35.820><c> that</c><00:14:36.060><c> can</c><00:14:36.180><c> now</c><00:14:36.360><c> reflect</c><00:14:36.779><c> your</c><00:14:37.079><c> new</c>

00:14:37.190 --> 00:14:37.200 align:start position:0%
header that can now reflect your new
 

00:14:37.200 --> 00:14:39.410 align:start position:0%
header that can now reflect your new
deposit<00:14:37.680><c> so</c><00:14:38.399><c> you're</c><00:14:38.700><c> going</c><00:14:38.820><c> to</c><00:14:39.000><c> wait</c><00:14:39.060><c> for</c><00:14:39.240><c> the</c>

00:14:39.410 --> 00:14:39.420 align:start position:0%
deposit so you're going to wait for the
 

00:14:39.420 --> 00:14:41.150 align:start position:0%
deposit so you're going to wait for the
finalization<00:14:39.959><c> of</c><00:14:40.199><c> an</c><00:14:40.320><c> ethereum</c><00:14:40.680><c> block</c><00:14:40.800><c> which</c>

00:14:41.150 --> 00:14:41.160 align:start position:0%
finalization of an ethereum block which
 

00:14:41.160 --> 00:14:43.009 align:start position:0%
finalization of an ethereum block which
is<00:14:41.279><c> around</c><00:14:41.399><c> 12</c><00:14:41.639><c> minutes</c><00:14:41.940><c> and</c><00:14:42.480><c> on</c><00:14:42.660><c> top</c><00:14:42.779><c> of</c><00:14:42.959><c> that</c>

00:14:43.009 --> 00:14:43.019 align:start position:0%
is around 12 minutes and on top of that
 

00:14:43.019 --> 00:14:43.970 align:start position:0%
is around 12 minutes and on top of that
you're<00:14:43.199><c> gonna</c><00:14:43.320><c> have</c><00:14:43.440><c> to</c><00:14:43.560><c> wait</c><00:14:43.680><c> for</c><00:14:43.860><c> our</c>

00:14:43.970 --> 00:14:43.980 align:start position:0%
you're gonna have to wait for our
 

00:14:43.980 --> 00:14:45.949 align:start position:0%
you're gonna have to wait for our
proving<00:14:44.339><c> time</c><00:14:44.519><c> which</c><00:14:44.760><c> is</c><00:14:44.880><c> right</c><00:14:45.060><c> now</c><00:14:45.180><c> is</c><00:14:45.360><c> three</c>

00:14:45.949 --> 00:14:45.959 align:start position:0%
proving time which is right now is three
 

00:14:45.959 --> 00:14:48.110 align:start position:0%
proving time which is right now is three
minutes<00:14:46.139><c> and</c><00:14:46.920><c> after</c><00:14:47.100><c> that</c><00:14:47.339><c> period</c><00:14:47.639><c> we</c><00:14:48.000><c> can</c>

00:14:48.110 --> 00:14:48.120 align:start position:0%
minutes and after that period we can
 

00:14:48.120 --> 00:14:49.850 align:start position:0%
minutes and after that period we can
send<00:14:48.300><c> a</c><00:14:48.480><c> transaction</c><00:14:48.779><c> to</c><00:14:49.079><c> the</c><00:14:49.199><c> like</c><00:14:49.320><c> client</c><00:14:49.620><c> to</c>

00:14:49.850 --> 00:14:49.860 align:start position:0%
send a transaction to the like client to
 

00:14:49.860 --> 00:14:52.129 align:start position:0%
send a transaction to the like client to
update<00:14:50.160><c> it</c><00:14:50.279><c> to</c><00:14:50.459><c> the</c><00:14:50.579><c> latest</c><00:14:50.699><c> block</c><00:14:51.000><c> header</c><00:14:51.420><c> and</c>

00:14:52.129 --> 00:14:52.139 align:start position:0%
update it to the latest block header and
 

00:14:52.139 --> 00:14:53.509 align:start position:0%
update it to the latest block header and
then<00:14:52.260><c> to</c><00:14:52.560><c> initiate</c><00:14:52.860><c> your</c><00:14:53.040><c> withdrawal</c>

00:14:53.509 --> 00:14:53.519 align:start position:0%
then to initiate your withdrawal
 

00:14:53.519 --> 00:14:55.430 align:start position:0%
then to initiate your withdrawal
transaction<00:14:54.300><c> essentially</c><00:14:55.019><c> you</c><00:14:55.199><c> have</c><00:14:55.320><c> to</c>

00:14:55.430 --> 00:14:55.440 align:start position:0%
transaction essentially you have to
 

00:14:55.440 --> 00:14:57.829 align:start position:0%
transaction essentially you have to
provide<00:14:55.680><c> a</c><00:14:55.860><c> Merkle</c><00:14:56.220><c> proof</c><00:14:56.579><c> proving</c><00:14:57.480><c> that</c><00:14:57.660><c> you</c>

00:14:57.829 --> 00:14:57.839 align:start position:0%
provide a Merkle proof proving that you
 

00:14:57.839 --> 00:15:01.009 align:start position:0%
provide a Merkle proof proving that you
made<00:14:57.959><c> a</c><00:14:58.139><c> deposit</c><00:14:58.620><c> on</c><00:14:59.220><c> Gorly</c><00:14:59.880><c> and</c><00:15:00.779><c> this</c>

00:15:01.009 --> 00:15:01.019 align:start position:0%
made a deposit on Gorly and this
 

00:15:01.019 --> 00:15:02.689 align:start position:0%
made a deposit on Gorly and this
basically<00:15:01.440><c> this</c><00:15:01.980><c> merkelproof</c><00:15:02.579><c> will</c>

00:15:02.689 --> 00:15:02.699 align:start position:0%
basically this merkelproof will
 

00:15:02.699 --> 00:15:04.250 align:start position:0%
basically this merkelproof will
essentially<00:15:03.000><c> unlock</c><00:15:03.180><c> funds</c><00:15:03.779><c> on</c><00:15:04.019><c> the</c><00:15:04.139><c> target</c>

00:15:04.250 --> 00:15:04.260 align:start position:0%
essentially unlock funds on the target
 

00:15:04.260 --> 00:15:05.930 align:start position:0%
essentially unlock funds on the target
chain

00:15:05.930 --> 00:15:05.940 align:start position:0%
chain
 

00:15:05.940 --> 00:15:07.910 align:start position:0%
chain
and<00:15:06.420><c> you</c><00:15:06.540><c> can</c><00:15:06.660><c> see</c><00:15:06.779><c> yeah</c><00:15:06.959><c> over</c><00:15:07.260><c> after</c><00:15:07.620><c> some</c>

00:15:07.910 --> 00:15:07.920 align:start position:0%
and you can see yeah over after some
 

00:15:07.920 --> 00:15:10.310 align:start position:0%
and you can see yeah over after some
time<00:15:08.100><c> like</c><00:15:08.339><c> the</c><00:15:08.639><c> top</c><00:15:09.060><c> emoji</c><00:15:09.959><c> becomes</c><00:15:10.260><c> like</c>

00:15:10.310 --> 00:15:10.320 align:start position:0%
time like the top emoji becomes like
 

00:15:10.320 --> 00:15:11.629 align:start position:0%
time like the top emoji becomes like
green<00:15:10.500><c> check</c><00:15:10.680><c> mark</c>

00:15:11.629 --> 00:15:11.639 align:start position:0%
green check mark
 

00:15:11.639 --> 00:15:13.610 align:start position:0%
green check mark
and<00:15:12.360><c> uh</c><00:15:12.600><c> yeah</c>

00:15:13.610 --> 00:15:13.620 align:start position:0%
and uh yeah
 

00:15:13.620 --> 00:15:15.470 align:start position:0%
and uh yeah
yeah so<00:15:13.920><c> yeah</c><00:15:14.160><c> to</c><00:15:14.339><c> zoom</c><00:15:14.639><c> out</c><00:15:14.699><c> a</c><00:15:14.880><c> bit</c><00:15:14.940><c> I</c><00:15:15.240><c> want</c><00:15:15.300><c> to</c>

00:15:15.470 --> 00:15:15.480 align:start position:0%
yeah so yeah to zoom out a bit I want to
 

00:15:15.480 --> 00:15:17.150 align:start position:0%
yeah so yeah to zoom out a bit I want to
take<00:15:15.660><c> some</c><00:15:15.839><c> time</c><00:15:16.019><c> to</c><00:15:16.260><c> compare</c><00:15:16.680><c> what</c><00:15:17.040><c> the</c>

00:15:17.150 --> 00:15:17.160 align:start position:0%
take some time to compare what the
 

00:15:17.160 --> 00:15:18.590 align:start position:0%
take some time to compare what the
trade-offs<00:15:17.639><c> are</c><00:15:17.760><c> between</c><00:15:18.060><c> you</c><00:15:18.360><c> know</c><00:15:18.420><c> this</c>

00:15:18.590 --> 00:15:18.600 align:start position:0%
trade-offs are between you know this
 

00:15:18.600 --> 00:15:20.150 align:start position:0%
trade-offs are between you know this
proof-based<00:15:19.199><c> bridge</c><00:15:19.320><c> versus</c><00:15:19.560><c> the</c><00:15:19.860><c> bridges</c>

00:15:20.150 --> 00:15:20.160 align:start position:0%
proof-based bridge versus the bridges
 

00:15:20.160 --> 00:15:21.710 align:start position:0%
proof-based bridge versus the bridges
that<00:15:20.339><c> exist</c><00:15:20.579><c> today</c><00:15:20.820><c> because</c><00:15:21.300><c> I</c><00:15:21.420><c> think</c><00:15:21.540><c> they</c>

00:15:21.710 --> 00:15:21.720 align:start position:0%
that exist today because I think they
 

00:15:21.720 --> 00:15:23.810 align:start position:0%
that exist today because I think they
very<00:15:21.899><c> much</c><00:15:22.560><c> um</c><00:15:22.680><c> exist</c><00:15:23.399><c> at</c><00:15:23.579><c> different</c>

00:15:23.810 --> 00:15:23.820 align:start position:0%
very much um exist at different
 

00:15:23.820 --> 00:15:25.009 align:start position:0%
very much um exist at different
trade-off<00:15:24.180><c> points</c><00:15:24.480><c> and</c><00:15:24.540><c> I</c><00:15:24.660><c> think</c><00:15:24.779><c> they</c><00:15:24.899><c> have</c>

00:15:25.009 --> 00:15:25.019 align:start position:0%
trade-off points and I think they have
 

00:15:25.019 --> 00:15:26.930 align:start position:0%
trade-off points and I think they have
different<00:15:25.139><c> use</c><00:15:25.440><c> cases</c><00:15:25.680><c> so</c><00:15:26.519><c> with</c><00:15:26.699><c> these</c>

00:15:26.930 --> 00:15:26.940 align:start position:0%
different use cases so with these
 

00:15:26.940 --> 00:15:28.490 align:start position:0%
different use cases so with these
proof-based<00:15:27.420><c> Bridges</c><00:15:27.720><c> you</c><00:15:27.959><c> know</c><00:15:28.019><c> obviously</c>

00:15:28.490 --> 00:15:28.500 align:start position:0%
proof-based Bridges you know obviously
 

00:15:28.500 --> 00:15:30.290 align:start position:0%
proof-based Bridges you know obviously
the<00:15:28.680><c> really</c><00:15:28.920><c> big</c><00:15:29.100><c> benefits</c><00:15:29.639><c> are</c><00:15:29.940><c> that</c><00:15:30.060><c> there's</c>

00:15:30.290 --> 00:15:30.300 align:start position:0%
the really big benefits are that there's
 

00:15:30.300 --> 00:15:32.569 align:start position:0%
the really big benefits are that there's
much<00:15:30.480><c> higher</c><00:15:30.839><c> security</c><00:15:31.019><c> guarantees</c><00:15:31.680><c> you</c><00:15:32.459><c> know</c>

00:15:32.569 --> 00:15:32.579 align:start position:0%
much higher security guarantees you know
 

00:15:32.579 --> 00:15:35.090 align:start position:0%
much higher security guarantees you know
assuming<00:15:33.420><c> that</c><00:15:33.540><c> the</c><00:15:33.720><c> ZK</c><00:15:34.079><c> uh</c><00:15:34.620><c> Stark</c><00:15:34.920><c> security</c>

00:15:35.090 --> 00:15:35.100 align:start position:0%
assuming that the ZK uh Stark security
 

00:15:35.100 --> 00:15:37.430 align:start position:0%
assuming that the ZK uh Stark security
is<00:15:35.459><c> fine</c><00:15:35.880><c> essentially</c><00:15:36.720><c> you're</c><00:15:36.959><c> able</c><00:15:37.199><c> to</c>

00:15:37.430 --> 00:15:37.440 align:start position:0%
is fine essentially you're able to
 

00:15:37.440 --> 00:15:39.949 align:start position:0%
is fine essentially you're able to
borrow<00:15:37.680><c> security</c><00:15:38.100><c> directly</c><00:15:39.060><c> from</c><00:15:39.480><c> the</c><00:15:39.720><c> source</c>

00:15:39.949 --> 00:15:39.959 align:start position:0%
borrow security directly from the source
 

00:15:39.959 --> 00:15:41.150 align:start position:0%
borrow security directly from the source
chain<00:15:40.079><c> which</c><00:15:40.380><c> I</c><00:15:40.500><c> think</c><00:15:40.560><c> is</c><00:15:40.680><c> something</c><00:15:40.920><c> really</c>

00:15:41.150 --> 00:15:41.160 align:start position:0%
chain which I think is something really
 

00:15:41.160 --> 00:15:43.129 align:start position:0%
chain which I think is something really
powerful<00:15:41.579><c> and</c><00:15:42.240><c> that</c><00:15:42.420><c> many</c><00:15:42.600><c> of</c><00:15:42.720><c> the</c><00:15:42.839><c> existing</c>

00:15:43.129 --> 00:15:43.139 align:start position:0%
powerful and that many of the existing
 

00:15:43.139 --> 00:15:44.750 align:start position:0%
powerful and that many of the existing
methods<00:15:43.560><c> don't</c><00:15:43.680><c> have</c><00:15:43.860><c> at</c><00:15:43.980><c> all</c>

00:15:44.750 --> 00:15:44.760 align:start position:0%
methods don't have at all
 

00:15:44.760 --> 00:15:46.970 align:start position:0%
methods don't have at all
another<00:15:45.360><c> property</c><00:15:45.839><c> is</c><00:15:46.139><c> that</c><00:15:46.380><c> because</c><00:15:46.680><c> we</c>

00:15:46.970 --> 00:15:46.980 align:start position:0%
another property is that because we
 

00:15:46.980 --> 00:15:48.170 align:start position:0%
another property is that because we
don't<00:15:47.100><c> have</c><00:15:47.279><c> any</c><00:15:47.519><c> additional</c><00:15:47.880><c> trust</c>

00:15:48.170 --> 00:15:48.180 align:start position:0%
don't have any additional trust
 

00:15:48.180 --> 00:15:50.509 align:start position:0%
don't have any additional trust
assumptions<00:15:48.660><c> besides</c><00:15:49.560><c> trusting</c><00:15:49.980><c> the</c><00:15:50.040><c> l1's</c>

00:15:50.509 --> 00:15:50.519 align:start position:0%
assumptions besides trusting the l1's
 

00:15:50.519 --> 00:15:51.949 align:start position:0%
assumptions besides trusting the l1's
validators

00:15:51.949 --> 00:15:51.959 align:start position:0%
validators
 

00:15:51.959 --> 00:15:53.810 align:start position:0%
validators
um this<00:15:52.560><c> this</c><00:15:52.800><c> protocol</c><00:15:53.160><c> can</c><00:15:53.519><c> be</c><00:15:53.639><c> very</c>

00:15:53.810 --> 00:15:53.820 align:start position:0%
um this this protocol can be very
 

00:15:53.820 --> 00:15:55.490 align:start position:0%
um this this protocol can be very
permissionless<00:15:54.360><c> and</c><00:15:54.600><c> censorship</c><00:15:54.959><c> resistant</c>

00:15:55.490 --> 00:15:55.500 align:start position:0%
permissionless and censorship resistant
 

00:15:55.500 --> 00:15:57.470 align:start position:0%
permissionless and censorship resistant
because<00:15:55.740><c> theoretically</c><00:15:56.339><c> anyone</c><00:15:57.180><c> can</c><00:15:57.360><c> be</c>

00:15:57.470 --> 00:15:57.480 align:start position:0%
because theoretically anyone can be
 

00:15:57.480 --> 00:15:58.910 align:start position:0%
because theoretically anyone can be
running<00:15:57.600><c> the</c><00:15:57.899><c> operator</c><00:15:58.199><c> that</c><00:15:58.500><c> generates</c><00:15:58.800><c> the</c>

00:15:58.910 --> 00:15:58.920 align:start position:0%
running the operator that generates the
 

00:15:58.920 --> 00:16:00.769 align:start position:0%
running the operator that generates the
proofs<00:15:59.220><c> and</c><00:15:59.579><c> anyone</c><00:15:59.940><c> can</c><00:16:00.120><c> be</c><00:16:00.240><c> updating</c><00:16:00.600><c> the</c>

00:16:00.769 --> 00:16:00.779 align:start position:0%
proofs and anyone can be updating the
 

00:16:00.779 --> 00:16:02.269 align:start position:0%
proofs and anyone can be updating the
like<00:16:00.959><c> clients</c>

00:16:02.269 --> 00:16:02.279 align:start position:0%
like clients
 

00:16:02.279 --> 00:16:04.250 align:start position:0%
like clients
and<00:16:02.699><c> yeah</c><00:16:02.880><c> for</c><00:16:03.180><c> these</c><00:16:03.300><c> reasons</c><00:16:03.660><c> it's</c><00:16:04.079><c> much</c>

00:16:04.250 --> 00:16:04.260 align:start position:0%
and yeah for these reasons it's much
 

00:16:04.260 --> 00:16:06.290 align:start position:0%
and yeah for these reasons it's much
more<00:16:04.380><c> permissive</c><00:16:04.740><c> than</c><00:16:04.920><c> jcentralized</c><00:16:05.699><c> now</c>

00:16:06.290 --> 00:16:06.300 align:start position:0%
more permissive than jcentralized now
 

00:16:06.300 --> 00:16:08.329 align:start position:0%
more permissive than jcentralized now
the<00:16:06.600><c> cons</c><00:16:06.720><c> are</c><00:16:07.019><c> I</c><00:16:07.380><c> think</c><00:16:07.500><c> you</c><00:16:07.920><c> might</c><00:16:08.040><c> imagine</c>

00:16:08.329 --> 00:16:08.339 align:start position:0%
the cons are I think you might imagine
 

00:16:08.339 --> 00:16:10.790 align:start position:0%
the cons are I think you might imagine
is<00:16:08.639><c> that</c><00:16:08.820><c> you</c><00:16:08.940><c> know</c><00:16:09.060><c> verifying</c><00:16:09.720><c> this</c><00:16:10.019><c> ZK</c><00:16:10.440><c> snark</c>

00:16:10.790 --> 00:16:10.800 align:start position:0%
is that you know verifying this ZK snark
 

00:16:10.800 --> 00:16:12.829 align:start position:0%
is that you know verifying this ZK snark
proof<00:16:11.160><c> is</c><00:16:11.880><c> much</c><00:16:12.120><c> more</c><00:16:12.240><c> expensive</c><00:16:12.660><c> than</c>

00:16:12.829 --> 00:16:12.839 align:start position:0%
proof is much more expensive than
 

00:16:12.839 --> 00:16:14.449 align:start position:0%
proof is much more expensive than
verifying<00:16:13.320><c> you</c><00:16:13.440><c> know</c><00:16:13.560><c> a</c><00:16:13.680><c> threshold</c><00:16:13.980><c> signature</c>

00:16:14.449 --> 00:16:14.459 align:start position:0%
verifying you know a threshold signature
 

00:16:14.459 --> 00:16:16.370 align:start position:0%
verifying you know a threshold signature
scheme<00:16:14.699><c> that</c><00:16:14.820><c> a</c><00:16:14.940><c> multi-sigma</c><00:16:15.420><c> implement</c><00:16:15.779><c> but</c>

00:16:16.370 --> 00:16:16.380 align:start position:0%
scheme that a multi-sigma implement but
 

00:16:16.380 --> 00:16:18.170 align:start position:0%
scheme that a multi-sigma implement but
thankfully<00:16:16.740><c> with</c><00:16:16.920><c> like</c><00:16:17.100><c> graph</c><00:16:17.399><c> 16</c><00:16:17.639><c> and</c><00:16:18.000><c> stuff</c>

00:16:18.170 --> 00:16:18.180 align:start position:0%
thankfully with like graph 16 and stuff
 

00:16:18.180 --> 00:16:19.910 align:start position:0%
thankfully with like graph 16 and stuff
we<00:16:18.600><c> expect</c><00:16:18.779><c> that</c><00:16:19.079><c> the</c><00:16:19.260><c> verification</c><00:16:19.620><c> cost</c>

00:16:19.910 --> 00:16:19.920 align:start position:0%
we expect that the verification cost
 

00:16:19.920 --> 00:16:22.910 align:start position:0%
we expect that the verification cost
will<00:16:20.160><c> be</c><00:16:20.399><c> around</c><00:16:20.519><c> 300K</c><00:16:21.420><c> gas</c><00:16:21.660><c> and</c><00:16:22.560><c> obviously</c>

00:16:22.910 --> 00:16:22.920 align:start position:0%
will be around 300K gas and obviously
 

00:16:22.920 --> 00:16:24.710 align:start position:0%
will be around 300K gas and obviously
another<00:16:23.160><c> con</c><00:16:23.459><c> is</c><00:16:23.760><c> that</c><00:16:23.880><c> you</c><00:16:24.060><c> have</c><00:16:24.300><c> to</c><00:16:24.360><c> wait</c><00:16:24.480><c> for</c>

00:16:24.710 --> 00:16:24.720 align:start position:0%
another con is that you have to wait for
 

00:16:24.720 --> 00:16:26.810 align:start position:0%
another con is that you have to wait for
the<00:16:24.899><c> proof</c><00:16:25.139><c> generation</c><00:16:25.500><c> time</c><00:16:25.860><c> and</c><00:16:26.459><c> in</c><00:16:26.699><c> our</c>

00:16:26.810 --> 00:16:26.820 align:start position:0%
the proof generation time and in our
 

00:16:26.820 --> 00:16:28.189 align:start position:0%
the proof generation time and in our
case<00:16:26.940><c> you</c><00:16:27.300><c> know</c><00:16:27.360><c> our</c><00:16:27.540><c> circuits</c><00:16:27.899><c> we</c><00:16:28.079><c> didn't</c>

00:16:28.189 --> 00:16:28.199 align:start position:0%
case you know our circuits we didn't
 

00:16:28.199 --> 00:16:29.930 align:start position:0%
case you know our circuits we didn't
spend<00:16:28.380><c> that</c><00:16:28.560><c> much</c><00:16:28.620><c> time</c><00:16:28.740><c> optimizing</c><00:16:29.339><c> them</c><00:16:29.519><c> but</c>

00:16:29.930 --> 00:16:29.940 align:start position:0%
spend that much time optimizing them but
 

00:16:29.940 --> 00:16:30.949 align:start position:0%
spend that much time optimizing them but
you<00:16:30.180><c> know</c><00:16:30.240><c> right</c><00:16:30.360><c> now</c><00:16:30.480><c> it's</c><00:16:30.600><c> three</c><00:16:30.779><c> minutes</c>

00:16:30.949 --> 00:16:30.959 align:start position:0%
you know right now it's three minutes
 

00:16:30.959 --> 00:16:32.689 align:start position:0%
you know right now it's three minutes
and<00:16:31.320><c> I</c><00:16:31.440><c> think</c><00:16:31.560><c> in</c><00:16:31.680><c> the</c><00:16:31.800><c> context</c><00:16:32.040><c> of</c><00:16:32.220><c> ethereum</c>

00:16:32.689 --> 00:16:32.699 align:start position:0%
and I think in the context of ethereum
 

00:16:32.699 --> 00:16:34.370 align:start position:0%
and I think in the context of ethereum
this<00:16:32.940><c> is</c><00:16:33.060><c> okay</c><00:16:33.180><c> because</c><00:16:33.600><c> the</c><00:16:33.899><c> finalization</c>

00:16:34.370 --> 00:16:34.380 align:start position:0%
this is okay because the finalization
 

00:16:34.380 --> 00:16:36.470 align:start position:0%
this is okay because the finalization
period<00:16:34.800><c> is</c><00:16:34.920><c> already</c><00:16:35.100><c> so</c><00:16:35.339><c> long</c><00:16:35.579><c> but</c><00:16:36.060><c> for</c><00:16:36.240><c> other</c>

00:16:36.470 --> 00:16:36.480 align:start position:0%
period is already so long but for other
 

00:16:36.480 --> 00:16:38.269 align:start position:0%
period is already so long but for other
consensus<00:16:37.019><c> protocols</c><00:16:37.620><c> you</c><00:16:37.860><c> know</c><00:16:37.920><c> you</c><00:16:38.160><c> might</c>

00:16:38.269 --> 00:16:38.279 align:start position:0%
consensus protocols you know you might
 

00:16:38.279 --> 00:16:40.430 align:start position:0%
consensus protocols you know you might
want<00:16:38.399><c> to</c><00:16:38.519><c> have</c><00:16:38.639><c> a</c><00:16:38.880><c> much</c><00:16:39.000><c> faster</c><00:16:39.480><c> proving</c><00:16:39.959><c> uh</c>

00:16:40.430 --> 00:16:40.440 align:start position:0%
want to have a much faster proving uh
 

00:16:40.440 --> 00:16:42.110 align:start position:0%
want to have a much faster proving uh
proving<00:16:40.980><c> time</c><00:16:41.160><c> and</c><00:16:41.579><c> that's</c><00:16:41.699><c> something</c><00:16:41.880><c> you</c>

00:16:42.110 --> 00:16:42.120 align:start position:0%
proving time and that's something you
 

00:16:42.120 --> 00:16:43.430 align:start position:0%
proving time and that's something you
could<00:16:42.240><c> probably</c><00:16:42.360><c> fix</c><00:16:42.600><c> by</c><00:16:42.959><c> using</c><00:16:43.259><c> your</c>

00:16:43.430 --> 00:16:43.440 align:start position:0%
could probably fix by using your
 

00:16:43.440 --> 00:16:45.889 align:start position:0%
could probably fix by using your
generation<00:16:43.800><c> improving</c><00:16:44.279><c> systems</c><00:16:44.639><c> and</c><00:16:45.420><c> many</c><00:16:45.779><c> of</c>

00:16:45.889 --> 00:16:45.899 align:start position:0%
generation improving systems and many of
 

00:16:45.899 --> 00:16:47.569 align:start position:0%
generation improving systems and many of
the<00:16:46.079><c> techniques</c><00:16:46.440><c> that</c><00:16:46.560><c> a</c><00:16:46.740><c> lot</c><00:16:46.860><c> of</c><00:16:46.920><c> the</c><00:16:46.980><c> zkv</c><00:16:47.399><c> and</c>

00:16:47.569 --> 00:16:47.579 align:start position:0%
the techniques that a lot of the zkv and
 

00:16:47.579 --> 00:16:49.550 align:start position:0%
the techniques that a lot of the zkv and
people<00:16:47.639><c> are</c><00:16:47.820><c> exploring</c><00:16:48.120><c> actually</c>

00:16:49.550 --> 00:16:49.560 align:start position:0%
people are exploring actually
 

00:16:49.560 --> 00:16:52.129 align:start position:0%
people are exploring actually
furthermore<00:16:50.399><c> another</c><00:16:50.820><c> challenge</c><00:16:51.180><c> with</c><00:16:51.660><c> this</c>

00:16:52.129 --> 00:16:52.139 align:start position:0%
furthermore another challenge with this
 

00:16:52.139 --> 00:16:53.689 align:start position:0%
furthermore another challenge with this
approach<00:16:52.380><c> compared</c><00:16:52.740><c> to</c><00:16:52.800><c> multi-sync</c><00:16:53.399><c> approach</c>

00:16:53.689 --> 00:16:53.699 align:start position:0%
approach compared to multi-sync approach
 

00:16:53.699 --> 00:16:55.970 align:start position:0%
approach compared to multi-sync approach
is<00:16:54.180><c> that</c><00:16:54.360><c> for</c><00:16:54.660><c> every</c><00:16:54.899><c> new</c><00:16:55.139><c> chain</c><00:16:55.440><c> you</c><00:16:55.740><c> want</c><00:16:55.860><c> to</c>

00:16:55.970 --> 00:16:55.980 align:start position:0%
is that for every new chain you want to
 

00:16:55.980 --> 00:16:58.129 align:start position:0%
is that for every new chain you want to
adopt<00:16:56.339><c> or</c><00:16:56.459><c> a</c><00:16:56.639><c> new</c><00:16:56.699><c> L1</c><00:16:57.060><c> or</c><00:16:57.420><c> even</c><00:16:57.540><c> when</c><00:16:57.839><c> a</c>

00:16:58.129 --> 00:16:58.139 align:start position:0%
adopt or a new L1 or even when a
 

00:16:58.139 --> 00:16:59.930 align:start position:0%
adopt or a new L1 or even when a
consensus<00:16:58.500><c> algorithm</c><00:16:58.920><c> on</c><00:16:59.100><c> ethereum</c><00:16:59.519><c> changes</c>

00:16:59.930 --> 00:16:59.940 align:start position:0%
consensus algorithm on ethereum changes
 

00:16:59.940 --> 00:17:03.290 align:start position:0%
consensus algorithm on ethereum changes
you<00:17:00.660><c> sort</c><00:17:00.839><c> of</c><00:17:00.959><c> have</c><00:17:01.139><c> to</c><00:17:01.500><c> rebuild</c><00:17:02.100><c> the</c><00:17:02.940><c> circuit</c>

00:17:03.290 --> 00:17:03.300 align:start position:0%
you sort of have to rebuild the circuit
 

00:17:03.300 --> 00:17:05.169 align:start position:0%
you sort of have to rebuild the circuit
and<00:17:03.660><c> you</c><00:17:03.720><c> have</c><00:17:03.779><c> to</c><00:17:03.899><c> like</c><00:17:04.020><c> kind</c><00:17:04.199><c> of</c><00:17:04.380><c> hand</c><00:17:04.679><c> design</c>

00:17:05.169 --> 00:17:05.179 align:start position:0%
and you have to like kind of hand design
 

00:17:05.179 --> 00:17:07.549 align:start position:0%
and you have to like kind of hand design
these<00:17:06.179><c> snarks</c><00:17:06.720><c> to</c><00:17:06.839><c> verify</c><00:17:07.140><c> the</c><00:17:07.260><c> consensus</c>

00:17:07.549 --> 00:17:07.559 align:start position:0%
these snarks to verify the consensus
 

00:17:07.559 --> 00:17:09.049 align:start position:0%
these snarks to verify the consensus
algorithm<00:17:08.040><c> and</c><00:17:08.400><c> I</c><00:17:08.520><c> think</c><00:17:08.640><c> from</c><00:17:08.819><c> the</c>

00:17:09.049 --> 00:17:09.059 align:start position:0%
algorithm and I think from the
 

00:17:09.059 --> 00:17:11.090 align:start position:0%
algorithm and I think from the
developer's<00:17:09.660><c> perspective</c><00:17:10.020><c> this</c><00:17:10.740><c> can</c><00:17:10.919><c> mean</c>

00:17:11.090 --> 00:17:11.100 align:start position:0%
developer's perspective this can mean
 

00:17:11.100 --> 00:17:12.650 align:start position:0%
developer's perspective this can mean
that<00:17:11.280><c> onboarding</c><00:17:11.819><c> new</c><00:17:11.939><c> chains</c><00:17:12.299><c> can</c><00:17:12.419><c> be</c><00:17:12.540><c> quite</c>

00:17:12.650 --> 00:17:12.660 align:start position:0%
that onboarding new chains can be quite
 

00:17:12.660 --> 00:17:14.750 align:start position:0%
that onboarding new chains can be quite
difficult

00:17:14.750 --> 00:17:14.760 align:start position:0%
difficult
 

00:17:14.760 --> 00:17:17.449 align:start position:0%
difficult
so<00:17:15.179><c> in</c><00:17:15.299><c> terms</c><00:17:15.480><c> of</c><00:17:15.540><c> our</c><00:17:15.720><c> roadmap</c><00:17:16.220><c> we're</c><00:17:17.220><c> trying</c>

00:17:17.449 --> 00:17:17.459 align:start position:0%
so in terms of our roadmap we're trying
 

00:17:17.459 --> 00:17:18.949 align:start position:0%
so in terms of our roadmap we're trying
to<00:17:17.640><c> take</c><00:17:17.760><c> what</c><00:17:18.120><c> we</c><00:17:18.240><c> currently</c><00:17:18.600><c> built</c><00:17:18.839><c> for</c>

00:17:18.949 --> 00:17:18.959 align:start position:0%
to take what we currently built for
 

00:17:18.959 --> 00:17:20.870 align:start position:0%
to take what we currently built for
ethereum<00:17:19.319><c> to</c><00:17:19.500><c> production</c><00:17:19.799><c> and</c><00:17:20.459><c> I</c><00:17:20.579><c> think</c><00:17:20.699><c> our</c>

00:17:20.870 --> 00:17:20.880 align:start position:0%
ethereum to production and I think our
 

00:17:20.880 --> 00:17:22.549 align:start position:0%
ethereum to production and I think our
end<00:17:21.059><c> goal</c><00:17:21.419><c> is</c><00:17:21.600><c> essentially</c><00:17:21.900><c> to</c><00:17:22.079><c> be</c><00:17:22.199><c> this</c><00:17:22.380><c> like</c>

00:17:22.549 --> 00:17:22.559 align:start position:0%
end goal is essentially to be this like
 

00:17:22.559 --> 00:17:24.409 align:start position:0%
end goal is essentially to be this like
trust<00:17:22.919><c> minimized</c><00:17:23.459><c> entropy</c><00:17:24.000><c> layer</c><00:17:24.299><c> for</c>

00:17:24.409 --> 00:17:24.419 align:start position:0%
trust minimized entropy layer for
 

00:17:24.419 --> 00:17:26.990 align:start position:0%
trust minimized entropy layer for
ethereum<00:17:24.900><c> and</c><00:17:25.439><c> other</c><00:17:26.040><c> decentralized</c><00:17:26.699><c> palette</c>

00:17:26.990 --> 00:17:27.000 align:start position:0%
ethereum and other decentralized palette
 

00:17:27.000 --> 00:17:28.850 align:start position:0%
ethereum and other decentralized palette
forms<00:17:27.299><c> and</c><00:17:27.480><c> we</c><00:17:27.600><c> want</c><00:17:27.720><c> this</c><00:17:27.959><c> to</c><00:17:28.140><c> all</c><00:17:28.319><c> be</c><00:17:28.500><c> powered</c>

00:17:28.850 --> 00:17:28.860 align:start position:0%
forms and we want this to all be powered
 

00:17:28.860 --> 00:17:31.010 align:start position:0%
forms and we want this to all be powered
by<00:17:29.040><c> proof</c><00:17:29.340><c> of</c><00:17:29.400><c> consensus</c><00:17:29.940><c> and</c><00:17:30.419><c> adopting</c><00:17:30.780><c> these</c>

00:17:31.010 --> 00:17:31.020 align:start position:0%
by proof of consensus and adopting these
 

00:17:31.020 --> 00:17:32.510 align:start position:0%
by proof of consensus and adopting these
values<00:17:31.320><c> of</c><00:17:31.500><c> decentralization</c><00:17:32.160><c> and</c>

00:17:32.510 --> 00:17:32.520 align:start position:0%
values of decentralization and
 

00:17:32.520 --> 00:17:34.070 align:start position:0%
values of decentralization and
permissionlessness

00:17:34.070 --> 00:17:34.080 align:start position:0%
permissionlessness
 

00:17:34.080 --> 00:17:36.289 align:start position:0%
permissionlessness
and<00:17:34.679><c> I</c><00:17:34.860><c> think</c><00:17:34.980><c> in</c><00:17:35.400><c> the</c><00:17:35.460><c> future</c><00:17:35.580><c> the</c><00:17:36.000><c> two</c><00:17:36.120><c> things</c>

00:17:36.289 --> 00:17:36.299 align:start position:0%
and I think in the future the two things
 

00:17:36.299 --> 00:17:37.730 align:start position:0%
and I think in the future the two things
we're<00:17:36.480><c> really</c><00:17:36.600><c> excited</c><00:17:36.900><c> about</c><00:17:37.080><c> is</c><00:17:37.500><c> building</c>

00:17:37.730 --> 00:17:37.740 align:start position:0%
we're really excited about is building
 

00:17:37.740 --> 00:17:39.590 align:start position:0%
we're really excited about is building
these<00:17:38.100><c> succinct</c><00:17:38.460><c> line</c><00:17:38.640><c> Titans</c><00:17:39.179><c> for</c><00:17:39.480><c> other</c>

00:17:39.590 --> 00:17:39.600 align:start position:0%
these succinct line Titans for other
 

00:17:39.600 --> 00:17:41.990 align:start position:0%
these succinct line Titans for other
blockchain<00:17:40.140><c> ecosystems</c><00:17:40.860><c> and</c><00:17:41.280><c> also</c><00:17:41.520><c> exploring</c>

00:17:41.990 --> 00:17:42.000 align:start position:0%
blockchain ecosystems and also exploring
 

00:17:42.000 --> 00:17:43.669 align:start position:0%
blockchain ecosystems and also exploring
these<00:17:42.240><c> new</c><00:17:42.360><c> approving</c><00:17:42.840><c> systems</c><00:17:43.200><c> to</c><00:17:43.500><c> decrease</c>

00:17:43.669 --> 00:17:43.679 align:start position:0%
these new approving systems to decrease
 

00:17:43.679 --> 00:17:46.789 align:start position:0%
these new approving systems to decrease
the<00:17:43.919><c> proving</c><00:17:44.220><c> time</c><00:17:44.400><c> significantly</c>

00:17:46.789 --> 00:17:46.799 align:start position:0%
the proving time significantly
 

00:17:46.799 --> 00:17:48.529 align:start position:0%
the proving time significantly
and<00:17:47.160><c> yeah</c><00:17:47.280><c> finally</c><00:17:47.580><c> we</c><00:17:47.820><c> wanted</c><00:17:47.940><c> to</c><00:17:48.059><c> give</c><00:17:48.179><c> a</c><00:17:48.360><c> big</c>

00:17:48.529 --> 00:17:48.539 align:start position:0%
and yeah finally we wanted to give a big
 

00:17:48.539 --> 00:17:50.690 align:start position:0%
and yeah finally we wanted to give a big
shout<00:17:48.780><c> out</c><00:17:48.900><c> to</c><00:17:49.260><c> gnosis</c><00:17:49.740><c> Dao</c><00:17:50.160><c> who</c><00:17:50.340><c> originally</c>

00:17:50.690 --> 00:17:50.700 align:start position:0%
shout out to gnosis Dao who originally
 

00:17:50.700 --> 00:17:52.789 align:start position:0%
shout out to gnosis Dao who originally
funded<00:17:51.059><c> this</c><00:17:51.240><c> work</c><00:17:51.419><c> and</c><00:17:51.720><c> super</c><00:17:52.320><c> um</c><00:17:52.320><c> were</c><00:17:52.559><c> super</c>

00:17:52.789 --> 00:17:52.799 align:start position:0%
funded this work and super um were super
 

00:17:52.799 --> 00:17:55.730 align:start position:0%
funded this work and super um were super
helpful<00:17:53.220><c> and</c><00:17:53.820><c> also</c><00:17:54.000><c> Xerox</c><00:17:54.419><c> Park</c><00:17:55.020><c> um</c><00:17:55.140><c> where</c><00:17:55.559><c> we</c>

00:17:55.730 --> 00:17:55.740 align:start position:0%
helpful and also Xerox Park um where we
 

00:17:55.740 --> 00:17:57.350 align:start position:0%
helpful and also Xerox Park um where we
worked<00:17:56.100><c> uh</c><00:17:56.460><c> for</c><00:17:56.700><c> the</c><00:17:56.820><c> summer</c><00:17:56.940><c> and</c><00:17:57.179><c> the</c>

00:17:57.350 --> 00:17:57.360 align:start position:0%
worked uh for the summer and the
 

00:17:57.360 --> 00:17:58.850 align:start position:0%
worked uh for the summer and the
community<00:17:57.539><c> provide</c><00:17:58.200><c> us</c><00:17:58.320><c> a</c><00:17:58.500><c> lot</c><00:17:58.559><c> of</c><00:17:58.679><c> support</c>

00:17:58.850 --> 00:17:58.860 align:start position:0%
community provide us a lot of support
 

00:17:58.860 --> 00:18:04.330 align:start position:0%
community provide us a lot of support
and<00:17:59.340><c> help</c>

00:18:04.330 --> 00:18:04.340 align:start position:0%
 
 

00:18:04.340 --> 00:18:07.340 align:start position:0%
 
thank<00:18:05.340><c> you</c>