WEBVTT
Kind: captions
Language: en

00:00:00.000 --> 00:00:04.280 align:start position:0%
 
hi<00:00:00.780><c> I'm</c><00:00:01.350><c> Frankie</c><00:00:01.979><c> from</c><00:00:02.520><c> the</c><00:00:02.669><c> IRD</c><00:00:02.879><c> group</c><00:00:03.300><c> or</c><00:00:03.870><c> Rd</c>

00:00:04.280 --> 00:00:04.290 align:start position:0%
hi I'm Frankie from the IRD group or Rd
 

00:00:04.290 --> 00:00:05.749 align:start position:0%
hi I'm Frankie from the IRD group or Rd
group<00:00:04.470><c> of</c><00:00:04.620><c> your</c><00:00:04.799><c> friendly</c><00:00:05.100><c> extension</c><00:00:05.580><c> meta</c>

00:00:05.749 --> 00:00:05.759 align:start position:0%
group of your friendly extension meta
 

00:00:05.759 --> 00:00:07.880 align:start position:0%
group of your friendly extension meta
mask<00:00:06.000><c> today</c><00:00:06.690><c> we're</c><00:00:06.990><c> going</c><00:00:07.109><c> to</c><00:00:07.290><c> present</c><00:00:07.710><c> to</c><00:00:07.859><c> you</c>

00:00:07.880 --> 00:00:07.890 align:start position:0%
mask today we're going to present to you
 

00:00:07.890 --> 00:00:10.310 align:start position:0%
mask today we're going to present to you
our<00:00:08.010><c> vision</c><00:00:08.580><c> for</c><00:00:09.059><c> a</c><00:00:09.090><c> network</c><00:00:09.389><c> of</c><00:00:09.750><c> a</c><00:00:09.960><c> cerium</c>

00:00:10.310 --> 00:00:10.320 align:start position:0%
our vision for a network of a cerium
 

00:00:10.320 --> 00:00:13.789 align:start position:0%
our vision for a network of a cerium
like<00:00:10.530><c> clients</c><00:00:12.049><c> you</c><00:00:13.049><c> may</c><00:00:13.200><c> know</c><00:00:13.380><c> some</c><00:00:13.410><c> of</c><00:00:13.710><c> us</c>

00:00:13.789 --> 00:00:13.799 align:start position:0%
like clients you may know some of us
 

00:00:13.799 --> 00:00:15.379 align:start position:0%
like clients you may know some of us
from<00:00:13.980><c> other</c><00:00:14.219><c> projects</c><00:00:14.790><c> in</c><00:00:14.910><c> the</c><00:00:14.940><c> decentralized</c>

00:00:15.379 --> 00:00:15.389 align:start position:0%
from other projects in the decentralized
 

00:00:15.389 --> 00:00:18.050 align:start position:0%
from other projects in the decentralized
space<00:00:15.929><c> we've</c><00:00:16.650><c> been</c><00:00:16.800><c> involved</c><00:00:17.310><c> in</c><00:00:17.490><c> in</c><00:00:17.760><c> Fira</c>

00:00:18.050 --> 00:00:18.060 align:start position:0%
space we've been involved in in Fira
 

00:00:18.060 --> 00:00:22.820 align:start position:0%
space we've been involved in in Fira
meta<00:00:18.480><c> mask</c><00:00:18.690><c> ipfs</c><00:00:19.439><c> live</c><00:00:19.770><c> p2p</c><00:00:20.990><c> so</c><00:00:21.990><c> I'm</c><00:00:22.260><c> sure</c><00:00:22.500><c> some</c>

00:00:22.820 --> 00:00:22.830 align:start position:0%
meta mask ipfs live p2p so I'm sure some
 

00:00:22.830 --> 00:00:24.200 align:start position:0%
meta mask ipfs live p2p so I'm sure some
of<00:00:22.859><c> you</c><00:00:23.039><c> are</c><00:00:23.160><c> wondering</c><00:00:23.279><c> how</c><00:00:23.580><c> long</c><00:00:23.730><c> does</c><00:00:24.150><c> it</c>

00:00:24.200 --> 00:00:24.210 align:start position:0%
of you are wondering how long does it
 

00:00:24.210 --> 00:00:26.779 align:start position:0%
of you are wondering how long does it
take<00:00:24.510><c> to</c><00:00:24.660><c> sink</c><00:00:24.840><c> a</c><00:00:24.990><c> full</c><00:00:25.199><c> a</c><00:00:25.230><c> cerium</c><00:00:25.800><c> node</c><00:00:26.010><c> great</c>

00:00:26.779 --> 00:00:26.789 align:start position:0%
take to sink a full a cerium node great
 

00:00:26.789 --> 00:00:29.060 align:start position:0%
take to sink a full a cerium node great
question<00:00:27.420><c> in</c><00:00:27.810><c> our</c><00:00:28.320><c> experience</c><00:00:28.859><c> it</c><00:00:28.980><c> takes</c>

00:00:29.060 --> 00:00:29.070 align:start position:0%
question in our experience it takes
 

00:00:29.070 --> 00:00:31.009 align:start position:0%
question in our experience it takes
anywhere<00:00:29.400><c> from</c><00:00:29.550><c> a</c><00:00:29.789><c> couple</c><00:00:29.970><c> hours</c><00:00:30.449><c> to</c><00:00:30.779><c> well</c>

00:00:31.009 --> 00:00:31.019 align:start position:0%
anywhere from a couple hours to well
 

00:00:31.019 --> 00:00:32.870 align:start position:0%
anywhere from a couple hours to well
over<00:00:31.050><c> a</c><00:00:31.380><c> week</c><00:00:31.590><c> to</c><00:00:31.650><c> sink</c><00:00:32.160><c> a</c><00:00:32.219><c> full</c><00:00:32.399><c> node</c><00:00:32.610><c> from</c>

00:00:32.870 --> 00:00:32.880 align:start position:0%
over a week to sink a full node from
 

00:00:32.880 --> 00:00:34.910 align:start position:0%
over a week to sink a full node from
scratch<00:00:33.230><c> aetherium</c><00:00:34.230><c> notes</c><00:00:34.500><c> are</c><00:00:34.649><c> becoming</c>

00:00:34.910 --> 00:00:34.920 align:start position:0%
scratch aetherium notes are becoming
 

00:00:34.920 --> 00:00:37.490 align:start position:0%
scratch aetherium notes are becoming
more<00:00:35.219><c> resource</c><00:00:35.790><c> intensive</c><00:00:35.969><c> at</c><00:00:36.840><c> full</c><00:00:37.230><c> node</c>

00:00:37.490 --> 00:00:37.500 align:start position:0%
more resource intensive at full node
 

00:00:37.500 --> 00:00:41.270 align:start position:0%
more resource intensive at full node
uses<00:00:38.690><c> gigabytes</c><00:00:39.690><c> of</c><00:00:39.899><c> storage</c><00:00:40.050><c> it</c><00:00:40.739><c> uses</c>

00:00:41.270 --> 00:00:41.280 align:start position:0%
uses gigabytes of storage it uses
 

00:00:41.280 --> 00:00:43.700 align:start position:0%
uses gigabytes of storage it uses
significant<00:00:41.940><c> amounts</c><00:00:42.420><c> of</c><00:00:42.450><c> i/o</c><00:00:42.809><c> so</c><00:00:43.290><c> much</c><00:00:43.500><c> so</c>

00:00:43.700 --> 00:00:43.710 align:start position:0%
significant amounts of i/o so much so
 

00:00:43.710 --> 00:00:45.619 align:start position:0%
significant amounts of i/o so much so
that<00:00:43.739><c> it</c><00:00:43.980><c> requires</c><00:00:44.340><c> an</c><00:00:44.610><c> SSD</c><00:00:45.030><c> at</c><00:00:45.270><c> the</c><00:00:45.420><c> very</c>

00:00:45.619 --> 00:00:45.629 align:start position:0%
that it requires an SSD at the very
 

00:00:45.629 --> 00:00:48.200 align:start position:0%
that it requires an SSD at the very
least<00:00:45.899><c> also</c><00:00:46.550><c> synchronizing</c><00:00:47.550><c> state</c><00:00:47.789><c> takes</c><00:00:48.090><c> a</c>

00:00:48.200 --> 00:00:48.210 align:start position:0%
least also synchronizing state takes a
 

00:00:48.210 --> 00:00:50.270 align:start position:0%
least also synchronizing state takes a
long<00:00:48.480><c> time</c><00:00:48.510><c> to</c><00:00:48.840><c> network</c><00:00:49.289><c> issues</c><00:00:49.800><c> and</c><00:00:50.010><c> having</c>

00:00:50.270 --> 00:00:50.280 align:start position:0%
long time to network issues and having
 

00:00:50.280 --> 00:00:52.670 align:start position:0%
long time to network issues and having
to<00:00:50.460><c> process</c><00:00:50.640><c> every</c><00:00:51.239><c> block</c><00:00:51.480><c> to</c><00:00:52.140><c> reconstruct</c>

00:00:52.670 --> 00:00:52.680 align:start position:0%
to process every block to reconstruct
 

00:00:52.680 --> 00:00:54.889 align:start position:0%
to process every block to reconstruct
the<00:00:52.800><c> state</c><00:00:53.039><c> this</c><00:00:53.550><c> and</c><00:00:53.940><c> other</c><00:00:54.180><c> issues</c><00:00:54.390><c> is</c>

00:00:54.889 --> 00:00:54.899 align:start position:0%
the state this and other issues is
 

00:00:54.899 --> 00:00:56.779 align:start position:0%
the state this and other issues is
forcing<00:00:55.320><c> users</c><00:00:55.440><c> to</c><00:00:55.770><c> rely</c><00:00:56.039><c> on</c><00:00:56.070><c> centralized</c>

00:00:56.779 --> 00:00:56.789 align:start position:0%
forcing users to rely on centralized
 

00:00:56.789 --> 00:01:00.319 align:start position:0%
forcing users to rely on centralized
infrastructure<00:00:58.370><c> what</c><00:00:59.370><c> about</c><00:00:59.550><c> light</c><00:00:59.789><c> clients</c>

00:01:00.319 --> 00:01:00.329 align:start position:0%
infrastructure what about light clients
 

00:01:00.329 --> 00:01:02.510 align:start position:0%
infrastructure what about light clients
you<00:01:00.449><c> must</c><00:01:00.629><c> be</c><00:01:00.809><c> asking</c><00:01:01.010><c> current</c><00:01:02.010><c> light</c><00:01:02.160><c> client</c>

00:01:02.510 --> 00:01:02.520 align:start position:0%
you must be asking current light client
 

00:01:02.520 --> 00:01:04.670 align:start position:0%
you must be asking current light client
implementations<00:01:03.359><c> provide</c><00:01:03.690><c> solutions</c><00:01:04.530><c> to</c>

00:01:04.670 --> 00:01:04.680 align:start position:0%
implementations provide solutions to
 

00:01:04.680 --> 00:01:06.250 align:start position:0%
implementations provide solutions to
some<00:01:04.860><c> of</c><00:01:04.890><c> these</c><00:01:05.070><c> challenges</c><00:01:05.610><c> but</c><00:01:05.820><c> it's</c><00:01:05.970><c> also</c>

00:01:06.250 --> 00:01:06.260 align:start position:0%
some of these challenges but it's also
 

00:01:06.260 --> 00:01:09.469 align:start position:0%
some of these challenges but it's also
introduces<00:01:07.260><c> its</c><00:01:07.439><c> own</c><00:01:07.650><c> limitations</c><00:01:08.479><c> relying</c>

00:01:09.469 --> 00:01:09.479 align:start position:0%
introduces its own limitations relying
 

00:01:09.479 --> 00:01:12.080 align:start position:0%
introduces its own limitations relying
on<00:01:09.689><c> good</c><00:01:10.140><c> nodes</c><00:01:10.439><c> for</c><00:01:10.680><c> most</c><00:01:10.890><c> of</c><00:01:11.070><c> its</c><00:01:11.189><c> data</c><00:01:11.460><c> like</c>

00:01:12.080 --> 00:01:12.090 align:start position:0%
on good nodes for most of its data like
 

00:01:12.090 --> 00:01:14.149 align:start position:0%
on good nodes for most of its data like
clients<00:01:12.570><c> are</c><00:01:12.689><c> leechers</c><00:01:13.380><c> in</c><00:01:13.710><c> a</c><00:01:13.890><c> peer-to-peer</c>

00:01:14.149 --> 00:01:14.159 align:start position:0%
clients are leechers in a peer-to-peer
 

00:01:14.159 --> 00:01:17.859 align:start position:0%
clients are leechers in a peer-to-peer
network<00:01:14.280><c> sense</c><00:01:15.180><c> they</c><00:01:15.630><c> don't</c><00:01:15.720><c> cede</c><00:01:16.170><c> any</c><00:01:16.470><c> data</c>

00:01:17.859 --> 00:01:17.869 align:start position:0%
network sense they don't cede any data
 

00:01:17.869 --> 00:01:20.810 align:start position:0%
network sense they don't cede any data
the<00:01:18.869><c> required</c><00:01:19.259><c> syncing</c><00:01:19.680><c> state</c><00:01:19.950><c> before</c>

00:01:20.810 --> 00:01:20.820 align:start position:0%
the required syncing state before
 

00:01:20.820 --> 00:01:23.300 align:start position:0%
the required syncing state before
becoming<00:01:21.150><c> usable</c><00:01:21.479><c> this</c><00:01:22.380><c> isn't</c><00:01:22.770><c> as</c><00:01:22.950><c> resource</c>

00:01:23.300 --> 00:01:23.310 align:start position:0%
becoming usable this isn't as resource
 

00:01:23.310 --> 00:01:25.520 align:start position:0%
becoming usable this isn't as resource
intensive<00:01:23.939><c> as</c><00:01:24.119><c> syncing</c><00:01:24.479><c> a</c><00:01:24.570><c> full</c><00:01:24.780><c> node</c><00:01:25.049><c> but</c>

00:01:25.520 --> 00:01:25.530 align:start position:0%
intensive as syncing a full node but
 

00:01:25.530 --> 00:01:27.469 align:start position:0%
intensive as syncing a full node but
it's<00:01:25.680><c> still</c><00:01:25.890><c> an</c><00:01:26.040><c> important</c><00:01:26.520><c> limitation</c><00:01:27.180><c> that</c>

00:01:27.469 --> 00:01:27.479 align:start position:0%
it's still an important limitation that
 

00:01:27.479 --> 00:01:30.710 align:start position:0%
it's still an important limitation that
regular<00:01:28.049><c> users</c><00:01:28.409><c> aren't</c><00:01:28.650><c> necessarily</c><00:01:29.720><c> willing</c>

00:01:30.710 --> 00:01:30.720 align:start position:0%
regular users aren't necessarily willing
 

00:01:30.720 --> 00:01:34.399 align:start position:0%
regular users aren't necessarily willing
to<00:01:30.990><c> bear</c><00:01:31.670><c> imagine</c><00:01:32.670><c> a</c><00:01:32.759><c> user</c><00:01:32.970><c> having</c><00:01:33.509><c> to</c><00:01:34.110><c> wait</c>

00:01:34.399 --> 00:01:34.409 align:start position:0%
to bear imagine a user having to wait
 

00:01:34.409 --> 00:01:36.679 align:start position:0%
to bear imagine a user having to wait
minutes<00:01:34.920><c> before</c><00:01:35.340><c> using</c><00:01:35.490><c> her</c><00:01:35.759><c> favorite</c><00:01:36.119><c> def</c><00:01:36.360><c> in</c>

00:01:36.679 --> 00:01:36.689 align:start position:0%
minutes before using her favorite def in
 

00:01:36.689 --> 00:01:39.590 align:start position:0%
minutes before using her favorite def in
a<00:01:37.470><c> time</c><00:01:37.710><c> where</c><00:01:37.950><c> webpage</c><00:01:38.430><c> loads</c><00:01:38.880><c> are</c><00:01:39.210><c> measured</c>

00:01:39.590 --> 00:01:39.600 align:start position:0%
a time where webpage loads are measured
 

00:01:39.600 --> 00:01:41.780 align:start position:0%
a time where webpage loads are measured
in<00:01:39.750><c> milliseconds</c><00:01:40.530><c> this</c><00:01:40.829><c> is</c><00:01:41.009><c> not</c><00:01:41.250><c> acceptable</c>

00:01:41.780 --> 00:01:41.790 align:start position:0%
in milliseconds this is not acceptable
 

00:01:41.790 --> 00:01:45.200 align:start position:0%
in milliseconds this is not acceptable
UX<00:01:42.270><c> on</c><00:01:43.229><c> top</c><00:01:43.740><c> of</c><00:01:43.890><c> that</c><00:01:43.979><c> def</c><00:01:44.220><c> beauty</c><00:01:44.549><c> relies</c><00:01:45.180><c> on</c>

00:01:45.200 --> 00:01:45.210 align:start position:0%
UX on top of that def beauty relies on
 

00:01:45.210 --> 00:01:48.170 align:start position:0%
UX on top of that def beauty relies on
UDP<00:01:45.990><c> and</c><00:01:46.320><c> TCP</c><00:01:46.860><c> for</c><00:01:47.100><c> data</c><00:01:47.310><c> transfer</c><00:01:47.790><c> and</c><00:01:47.820><c> note</c>

00:01:48.170 --> 00:01:48.180 align:start position:0%
UDP and TCP for data transfer and note
 

00:01:48.180 --> 00:01:51.469 align:start position:0%
UDP and TCP for data transfer and note
discovery<00:01:48.780><c> which</c><00:01:50.090><c> makes</c><00:01:51.090><c> it</c><00:01:51.299><c> inherently</c>

00:01:51.469 --> 00:01:51.479 align:start position:0%
discovery which makes it inherently
 

00:01:51.479 --> 00:01:55.609 align:start position:0%
discovery which makes it inherently
incompatible<00:01:52.290><c> with</c><00:01:52.829><c> the</c><00:01:52.950><c> browser</c><00:01:54.619><c> madam</c>

00:01:55.609 --> 00:01:55.619 align:start position:0%
incompatible with the browser madam
 

00:01:55.619 --> 00:01:57.139 align:start position:0%
incompatible with the browser madam
asked<00:01:55.799><c> is</c><00:01:56.009><c> an</c><00:01:56.159><c> important</c><00:01:56.640><c> part</c><00:01:56.939><c> of</c><00:01:57.060><c> the</c>

00:01:57.139 --> 00:01:57.149 align:start position:0%
asked is an important part of the
 

00:01:57.149 --> 00:01:59.899 align:start position:0%
asked is an important part of the
ecosystem<00:01:57.450><c> it's</c><00:01:58.320><c> responsible</c><00:01:58.950><c> for</c><00:01:59.009><c> helping</c>

00:01:59.899 --> 00:01:59.909 align:start position:0%
ecosystem it's responsible for helping
 

00:01:59.909 --> 00:02:04.370 align:start position:0%
ecosystem it's responsible for helping
drive<00:02:00.390><c> the</c><00:02:00.420><c> adoption</c><00:02:00.750><c> with</c><00:02:01.380><c> cerium</c><00:02:03.380><c> users</c>

00:02:04.370 --> 00:02:04.380 align:start position:0%
drive the adoption with cerium users
 

00:02:04.380 --> 00:02:06.499 align:start position:0%
drive the adoption with cerium users
rely<00:02:04.530><c> on</c><00:02:04.649><c> meta</c><00:02:04.979><c> masks</c><00:02:05.219><c> to</c><00:02:05.729><c> interact</c><00:02:06.210><c> with</c><00:02:06.360><c> the</c>

00:02:06.499 --> 00:02:06.509 align:start position:0%
rely on meta masks to interact with the
 

00:02:06.509 --> 00:02:08.600 align:start position:0%
rely on meta masks to interact with the
etherium<00:02:06.899><c> blockchain</c><00:02:07.380><c> from</c><00:02:07.649><c> gaps</c><00:02:07.890><c> to</c><00:02:08.160><c> tokens</c>

00:02:08.600 --> 00:02:08.610 align:start position:0%
etherium blockchain from gaps to tokens
 

00:02:08.610 --> 00:02:12.530 align:start position:0%
etherium blockchain from gaps to tokens
to<00:02:09.390><c> transferring</c><00:02:09.869><c> ether</c><00:02:10.200><c> directly</c><00:02:11.270><c> but</c><00:02:12.270><c> meta</c>

00:02:12.530 --> 00:02:12.540 align:start position:0%
to transferring ether directly but meta
 

00:02:12.540 --> 00:02:13.420 align:start position:0%
to transferring ether directly but meta
masks<00:02:12.750><c> as</c><00:02:13.020><c> well</c>

00:02:13.420 --> 00:02:13.430 align:start position:0%
masks as well
 

00:02:13.430 --> 00:02:16.630 align:start position:0%
masks as well
other<00:02:13.819><c> similar</c><00:02:14.299><c> tools</c><00:02:15.079><c> rely</c><00:02:15.739><c> heavily</c><00:02:16.159><c> on</c>

00:02:16.630 --> 00:02:16.640 align:start position:0%
other similar tools rely heavily on
 

00:02:16.640 --> 00:02:19.059 align:start position:0%
other similar tools rely heavily on
centralized<00:02:17.569><c> infrastructure</c><00:02:18.260><c> such</c><00:02:19.040><c> as</c>

00:02:19.059 --> 00:02:19.069 align:start position:0%
centralized infrastructure such as
 

00:02:19.069 --> 00:02:20.979 align:start position:0%
centralized infrastructure such as
things<00:02:19.400><c> like</c><00:02:19.549><c> inferior</c><00:02:20.090><c> and</c><00:02:20.299><c> other</c><00:02:20.510><c> other</c>

00:02:20.979 --> 00:02:20.989 align:start position:0%
things like inferior and other other
 

00:02:20.989 --> 00:02:24.539 align:start position:0%
things like inferior and other other
services<00:02:21.549><c> this</c><00:02:22.549><c> was</c><00:02:22.730><c> instrumental</c><00:02:23.530><c> for</c>

00:02:24.539 --> 00:02:24.549 align:start position:0%
services this was instrumental for
 

00:02:24.549 --> 00:02:27.699 align:start position:0%
services this was instrumental for
bootstrapping<00:02:25.549><c> the</c><00:02:25.819><c> Assyrian</c><00:02:26.360><c> ecosystem</c><00:02:27.140><c> but</c>

00:02:27.699 --> 00:02:27.709 align:start position:0%
bootstrapping the Assyrian ecosystem but
 

00:02:27.709 --> 00:02:29.229 align:start position:0%
bootstrapping the Assyrian ecosystem but
this<00:02:27.860><c> breaks</c><00:02:28.220><c> the</c><00:02:28.610><c> premise</c><00:02:29.090><c> of</c>

00:02:29.229 --> 00:02:29.239 align:start position:0%
this breaks the premise of
 

00:02:29.239 --> 00:02:31.270 align:start position:0%
this breaks the premise of
decentralization<00:02:30.049><c> and</c><00:02:30.470><c> now</c><00:02:30.680><c> we</c><00:02:30.739><c> need</c><00:02:31.040><c> to</c><00:02:31.159><c> do</c>

00:02:31.270 --> 00:02:31.280 align:start position:0%
decentralization and now we need to do
 

00:02:31.280 --> 00:02:31.780 align:start position:0%
decentralization and now we need to do
better

00:02:31.780 --> 00:02:31.790 align:start position:0%
better
 

00:02:31.790 --> 00:02:33.880 align:start position:0%
better
the<00:02:32.359><c> problem</c><00:02:32.780><c> is</c><00:02:32.930><c> building</c><00:02:33.349><c> decentralized</c>

00:02:33.880 --> 00:02:33.890 align:start position:0%
the problem is building decentralized
 

00:02:33.890 --> 00:02:35.250 align:start position:0%
the problem is building decentralized
client<00:02:34.280><c> that</c><00:02:34.430><c> has</c><00:02:34.579><c> the</c><00:02:34.730><c> same</c><00:02:34.970><c> performance</c>

00:02:35.250 --> 00:02:35.260 align:start position:0%
client that has the same performance
 

00:02:35.260 --> 00:02:37.149 align:start position:0%
client that has the same performance
characteristics<00:02:36.260><c> that</c><00:02:36.500><c> centralized</c>

00:02:37.149 --> 00:02:37.159 align:start position:0%
characteristics that centralized
 

00:02:37.159 --> 00:02:40.990 align:start position:0%
characteristics that centralized
infrastructure<00:02:37.819><c> offers</c><00:02:39.519><c> so</c><00:02:40.519><c> what</c><00:02:40.730><c> are</c><00:02:40.970><c> our</c>

00:02:40.990 --> 00:02:41.000 align:start position:0%
infrastructure offers so what are our
 

00:02:41.000 --> 00:02:44.710 align:start position:0%
infrastructure offers so what are our
like<00:02:41.510><c> client</c><00:02:41.870><c> requirements</c><00:02:43.299><c> we</c><00:02:44.299><c> need</c><00:02:44.329><c> a</c><00:02:44.450><c> light</c>

00:02:44.710 --> 00:02:44.720 align:start position:0%
like client requirements we need a light
 

00:02:44.720 --> 00:02:46.930 align:start position:0%
like client requirements we need a light
client<00:02:45.079><c> that</c><00:02:45.140><c> is</c><00:02:45.290><c> fast</c><00:02:45.680><c> ready</c><00:02:46.400><c> to</c><00:02:46.579><c> use</c><00:02:46.760><c> in</c>

00:02:46.930 --> 00:02:46.940 align:start position:0%
client that is fast ready to use in
 

00:02:46.940 --> 00:02:49.360 align:start position:0%
client that is fast ready to use in
seconds<00:02:47.480><c> seeds</c><00:02:47.989><c> it's</c><00:02:48.200><c> data</c><00:02:48.470><c> to</c><00:02:48.709><c> other</c><00:02:48.859><c> peers</c>

00:02:49.360 --> 00:02:49.370 align:start position:0%
seconds seeds it's data to other peers
 

00:02:49.370 --> 00:02:51.640 align:start position:0%
seconds seeds it's data to other peers
so<00:02:49.639><c> that</c><00:02:49.700><c> it's</c><00:02:49.970><c> not</c><00:02:50.180><c> also</c><00:02:50.750><c> relying</c><00:02:51.409><c> on</c>

00:02:51.640 --> 00:02:51.650 align:start position:0%
so that it's not also relying on
 

00:02:51.650 --> 00:02:54.309 align:start position:0%
so that it's not also relying on
centralized<00:02:52.220><c> infrastructure</c><00:02:52.900><c> has</c><00:02:53.900><c> native</c>

00:02:54.309 --> 00:02:54.319 align:start position:0%
centralized infrastructure has native
 

00:02:54.319 --> 00:02:56.589 align:start position:0%
centralized infrastructure has native
brand<00:02:54.859><c> has</c><00:02:55.129><c> native</c><00:02:55.340><c> browser</c><00:02:55.700><c> support</c><00:02:56.450><c> of</c>

00:02:56.589 --> 00:02:56.599 align:start position:0%
brand has native browser support of
 

00:02:56.599 --> 00:03:01.660 align:start position:0%
brand has native browser support of
course<00:02:56.840><c> because</c><00:02:57.349><c> we're</c><00:02:57.769><c> meta</c><00:02:57.950><c> masks</c><00:03:00.250><c> so</c><00:03:01.250><c> now</c>

00:03:01.660 --> 00:03:01.670 align:start position:0%
course because we're meta masks so now
 

00:03:01.670 --> 00:03:03.399 align:start position:0%
course because we're meta masks so now
I'd<00:03:01.819><c> like</c><00:03:01.849><c> to</c><00:03:02.060><c> bring</c><00:03:02.299><c> on</c><00:03:02.480><c> Deema</c><00:03:02.750><c> to</c><00:03:03.079><c> talk</c><00:03:03.260><c> about</c>

00:03:03.399 --> 00:03:03.409 align:start position:0%
I'd like to bring on Deema to talk about
 

00:03:03.409 --> 00:03:04.360 align:start position:0%
I'd like to bring on Deema to talk about
our<00:03:03.650><c> solution</c>

00:03:04.360 --> 00:03:04.370 align:start position:0%
our solution
 

00:03:04.370 --> 00:03:17.740 align:start position:0%
our solution
mr.<00:03:04.700><c> kala</c><00:03:10.659><c> thank</c><00:03:11.659><c> you</c><00:03:16.180><c> most</c><00:03:17.180><c> Akali</c><00:03:17.569><c> it's</c><00:03:17.660><c> a</c>

00:03:17.740 --> 00:03:17.750 align:start position:0%
mr. kala thank you most Akali it's a
 

00:03:17.750 --> 00:03:21.150 align:start position:0%
mr. kala thank you most Akali it's a
light<00:03:17.930><c> client</c><00:03:18.410><c> for</c><00:03:18.650><c> the</c><00:03:18.739><c> browser</c><00:03:19.250><c> and</c><00:03:19.609><c> more</c>

00:03:21.150 --> 00:03:21.160 align:start position:0%
light client for the browser and more
 

00:03:21.160 --> 00:03:23.619 align:start position:0%
light client for the browser and more
it's<00:03:22.160><c> a</c><00:03:22.280><c> way</c><00:03:22.430><c> of</c><00:03:22.459><c> partitioning</c><00:03:22.879><c> the</c><00:03:23.299><c> Merkel</c>

00:03:23.619 --> 00:03:23.629 align:start position:0%
it's a way of partitioning the Merkel
 

00:03:23.629 --> 00:03:26.470 align:start position:0%
it's a way of partitioning the Merkel
tree<00:03:23.840><c> in</c><00:03:24.079><c> two</c><00:03:24.260><c> convenient</c><00:03:25.010><c> units</c><00:03:25.489><c> we</c><00:03:26.299><c> call</c>

00:03:26.470 --> 00:03:26.480 align:start position:0%
tree in two convenient units we call
 

00:03:26.480 --> 00:03:29.830 align:start position:0%
tree in two convenient units we call
slices<00:03:27.849><c> it's</c><00:03:28.849><c> a</c><00:03:28.970><c> network</c><00:03:29.239><c> of</c><00:03:29.359><c> browser-based</c>

00:03:29.830 --> 00:03:29.840 align:start position:0%
slices it's a network of browser-based
 

00:03:29.840 --> 00:03:31.869 align:start position:0%
slices it's a network of browser-based
peer-to-peer<00:03:30.530><c> nodes</c><00:03:31.040><c> that</c><00:03:31.250><c> help</c><00:03:31.549><c> find</c>

00:03:31.869 --> 00:03:31.879 align:start position:0%
peer-to-peer nodes that help find
 

00:03:31.879 --> 00:03:36.039 align:start position:0%
peer-to-peer nodes that help find
industry<00:03:32.359><c> with</c><00:03:32.629><c> slices</c><00:03:34.510><c> and</c><00:03:35.510><c> it's</c><00:03:35.690><c> a</c><00:03:35.750><c> network</c>

00:03:36.039 --> 00:03:36.049 align:start position:0%
industry with slices and it's a network
 

00:03:36.049 --> 00:03:38.140 align:start position:0%
industry with slices and it's a network
of<00:03:36.139><c> full</c><00:03:36.409><c> nodes</c><00:03:36.650><c> that</c><00:03:36.919><c> provide</c><00:03:37.250><c> the</c><00:03:37.370><c> slices</c><00:03:37.849><c> to</c>

00:03:38.140 --> 00:03:38.150 align:start position:0%
of full nodes that provide the slices to
 

00:03:38.150 --> 00:03:40.680 align:start position:0%
of full nodes that provide the slices to
delight<00:03:38.419><c> client</c><00:03:38.840><c> peers</c><00:03:39.139><c> right</c><00:03:40.040><c> now</c>

00:03:40.680 --> 00:03:40.690 align:start position:0%
delight client peers right now
 

00:03:40.690 --> 00:03:43.089 align:start position:0%
delight client peers right now
these<00:03:41.690><c> are</c><00:03:41.840><c> dedicated</c><00:03:42.290><c> notes</c><00:03:42.500><c> but</c><00:03:42.919><c> in</c><00:03:43.040><c> the</c>

00:03:43.089 --> 00:03:43.099 align:start position:0%
these are dedicated notes but in the
 

00:03:43.099 --> 00:03:44.949 align:start position:0%
these are dedicated notes but in the
future<00:03:43.400><c> we're</c><00:03:44.239><c> hoping</c><00:03:44.419><c> to</c><00:03:44.629><c> get</c><00:03:44.750><c> this</c>

00:03:44.949 --> 00:03:44.959 align:start position:0%
future we're hoping to get this
 

00:03:44.959 --> 00:03:47.770 align:start position:0%
future we're hoping to get this
functionality<00:03:45.379><c> to</c><00:03:46.090><c> become</c><00:03:47.090><c> part</c><00:03:47.359><c> of</c><00:03:47.479><c> the</c><00:03:47.599><c> full</c>

00:03:47.770 --> 00:03:47.780 align:start position:0%
functionality to become part of the full
 

00:03:47.780 --> 00:03:53.949 align:start position:0%
functionality to become part of the full
clients<00:03:48.169><c> stay</c><00:03:48.889><c> tuned</c><00:03:49.069><c> for</c><00:03:49.220><c> any</c><00:03:49.430><c> IP</c><00:03:52.540><c> so</c><00:03:53.540><c> slices</c>

00:03:53.949 --> 00:03:53.959 align:start position:0%
clients stay tuned for any IP so slices
 

00:03:53.959 --> 00:03:57.369 align:start position:0%
clients stay tuned for any IP so slices
what<00:03:54.440><c> are</c><00:03:54.560><c> they</c><00:03:55.810><c> they're</c><00:03:56.810><c> convenient</c>

00:03:57.369 --> 00:03:57.379 align:start position:0%
what are they they're convenient
 

00:03:57.379 --> 00:04:00.430 align:start position:0%
what are they they're convenient
portions<00:03:58.040><c> of</c><00:03:58.159><c> the</c><00:03:58.280><c> GM</c><00:03:58.549><c> Merkel</c><00:03:58.970><c> cream</c><00:03:59.440><c> the</c>

00:04:00.430 --> 00:04:00.440 align:start position:0%
portions of the GM Merkel cream the
 

00:04:00.440 --> 00:04:02.949 align:start position:0%
portions of the GM Merkel cream the
compose<00:04:00.709><c> of</c><00:04:00.739><c> the</c><00:04:01.010><c> stem</c><00:04:01.280><c> which</c><00:04:02.120><c> are</c><00:04:02.269><c> the</c><00:04:02.389><c> nodes</c>

00:04:02.949 --> 00:04:02.959 align:start position:0%
compose of the stem which are the nodes
 

00:04:02.959 --> 00:04:04.629 align:start position:0%
compose of the stem which are the nodes
traverse<00:04:03.470><c> to</c><00:04:03.709><c> reach</c><00:04:03.949><c> the</c><00:04:04.129><c> beginning</c><00:04:04.250><c> of</c><00:04:04.549><c> the</c>

00:04:04.629 --> 00:04:04.639 align:start position:0%
traverse to reach the beginning of the
 

00:04:04.639 --> 00:04:08.349 align:start position:0%
traverse to reach the beginning of the
slice<00:04:04.849><c> we</c><00:04:05.750><c> call</c><00:04:05.930><c> it</c><00:04:06.019><c> the</c><00:04:06.139><c> head</c><00:04:07.060><c> the</c><00:04:08.060><c> miracle</c>

00:04:08.349 --> 00:04:08.359 align:start position:0%
slice we call it the head the miracle
 

00:04:08.359 --> 00:04:10.539 align:start position:0%
slice we call it the head the miracle
tree<00:04:08.510><c> nodes</c><00:04:08.780><c> leaf</c><00:04:09.590><c> nodes</c><00:04:09.889><c> which</c><00:04:10.220><c> contain</c>

00:04:10.539 --> 00:04:10.549 align:start position:0%
tree nodes leaf nodes which contain
 

00:04:10.549 --> 00:04:15.099 align:start position:0%
tree nodes leaf nodes which contain
accounts<00:04:10.579><c> and</c><00:04:12.190><c> branch</c><00:04:13.190><c> nodes</c><00:04:13.549><c> and</c><00:04:14.120><c> for</c>

00:04:15.099 --> 00:04:15.109 align:start position:0%
accounts and branch nodes and for
 

00:04:15.109 --> 00:04:17.110 align:start position:0%
accounts and branch nodes and for
convenience<00:04:15.349><c> we</c><00:04:15.859><c> also</c><00:04:16.010><c> pack</c><00:04:16.340><c> the</c><00:04:16.519><c> EVM</c><00:04:16.909><c> code</c>

00:04:17.110 --> 00:04:17.120 align:start position:0%
convenience we also pack the EVM code
 

00:04:17.120 --> 00:04:18.670 align:start position:0%
convenience we also pack the EVM code
and<00:04:17.359><c> storage</c><00:04:17.750><c> route</c><00:04:17.989><c> for</c><00:04:18.260><c> each</c><00:04:18.349><c> smart</c>

00:04:18.670 --> 00:04:18.680 align:start position:0%
and storage route for each smart
 

00:04:18.680 --> 00:04:25.070 align:start position:0%
and storage route for each smart
contract<00:04:19.099><c> account</c>

00:04:25.070 --> 00:04:25.080 align:start position:0%
 
 

00:04:25.080 --> 00:04:29.610 align:start position:0%
 
how<00:04:26.080><c> do</c><00:04:26.140><c> we</c><00:04:26.320><c> identify</c><00:04:26.350><c> a</c><00:04:26.860><c> slice</c><00:04:28.320><c> we</c><00:04:29.320><c> use</c><00:04:29.470><c> the</c>

00:04:29.610 --> 00:04:29.620 align:start position:0%
how do we identify a slice we use the
 

00:04:29.620 --> 00:04:32.820 align:start position:0%
how do we identify a slice we use the
pad<00:04:29.830><c> which</c><00:04:30.460><c> is</c><00:04:30.610><c> an</c><00:04:30.730><c> offset</c><00:04:31.120><c> into</c><00:04:31.570><c> the</c><00:04:31.690><c> tree</c><00:04:31.930><c> the</c>

00:04:32.820 --> 00:04:32.830 align:start position:0%
pad which is an offset into the tree the
 

00:04:32.830 --> 00:04:34.560 align:start position:0%
pad which is an offset into the tree the
first<00:04:33.100><c> four</c><00:04:33.280><c> nibbles</c><00:04:33.640><c> of</c><00:04:33.880><c> an</c><00:04:34.060><c> address</c><00:04:34.240><c> or</c>

00:04:34.560 --> 00:04:34.570 align:start position:0%
first four nibbles of an address or
 

00:04:34.570 --> 00:04:38.430 align:start position:0%
first four nibbles of an address or
storage<00:04:34.930><c> key</c><00:04:35.970><c> the</c><00:04:36.970><c> depth</c><00:04:37.180><c> of</c><00:04:37.330><c> the</c><00:04:37.450><c> slice</c><00:04:37.660><c> which</c>

00:04:38.430 --> 00:04:38.440 align:start position:0%
storage key the depth of the slice which
 

00:04:38.440 --> 00:04:40.260 align:start position:0%
storage key the depth of the slice which
tells<00:04:38.710><c> us</c><00:04:38.890><c> how</c><00:04:39.070><c> many</c><00:04:39.130><c> levels</c><00:04:39.580><c> will</c><00:04:39.970><c> descend</c>

00:04:40.260 --> 00:04:40.270 align:start position:0%
tells us how many levels will descend
 

00:04:40.270 --> 00:04:44.370 align:start position:0%
tells us how many levels will descend
from<00:04:40.360><c> the</c><00:04:40.660><c> head</c><00:04:42.510><c> the</c><00:04:43.510><c> state</c><00:04:43.750><c> or</c><00:04:43.960><c> storage</c>

00:04:44.370 --> 00:04:44.380 align:start position:0%
from the head the state or storage
 

00:04:44.380 --> 00:04:46.470 align:start position:0%
from the head the state or storage
fruits<00:04:44.650><c> telling</c><00:04:45.460><c> us</c><00:04:45.580><c> which</c><00:04:45.790><c> block</c><00:04:46.060><c> the</c><00:04:46.270><c> slice</c>

00:04:46.470 --> 00:04:46.480 align:start position:0%
fruits telling us which block the slice
 

00:04:46.480 --> 00:04:53.310 align:start position:0%
fruits telling us which block the slice
belongs<00:04:46.900><c> to</c><00:04:51.600><c> now</c><00:04:52.600><c> what's</c><00:04:52.810><c> the</c><00:04:52.990><c> kitchenette</c>

00:04:53.310 --> 00:04:53.320 align:start position:0%
belongs to now what's the kitchenette
 

00:04:53.320 --> 00:04:56.490 align:start position:0%
belongs to now what's the kitchenette
Network<00:04:54.660><c> kitchenette</c><00:04:55.660><c> is</c><00:04:55.840><c> a</c><00:04:55.900><c> network</c><00:04:56.350><c> of</c>

00:04:56.490 --> 00:04:56.500 align:start position:0%
Network kitchenette is a network of
 

00:04:56.500 --> 00:04:58.440 align:start position:0%
Network kitchenette is a network of
peer-to-peer<00:04:56.800><c> nodes</c><00:04:57.280><c> that</c><00:04:57.640><c> collaborate</c><00:04:58.300><c> in</c>

00:04:58.440 --> 00:04:58.450 align:start position:0%
peer-to-peer nodes that collaborate in
 

00:04:58.450 --> 00:05:01.890 align:start position:0%
peer-to-peer nodes that collaborate in
distributing<00:04:58.960><c> slices</c><00:05:00.180><c> we're</c><00:05:01.180><c> using</c><00:05:01.390><c> Lippe</c><00:05:01.780><c> to</c>

00:05:01.890 --> 00:05:01.900 align:start position:0%
distributing slices we're using Lippe to
 

00:05:01.900 --> 00:05:04.620 align:start position:0%
distributing slices we're using Lippe to
be<00:05:02.050><c> a</c><00:05:02.430><c> modular</c><00:05:03.430><c> peer-to-peer</c><00:05:03.850><c> network</c><00:05:04.390><c> stack</c>

00:05:04.620 --> 00:05:04.630 align:start position:0%
be a modular peer-to-peer network stack
 

00:05:04.630 --> 00:05:07.650 align:start position:0%
be a modular peer-to-peer network stack
with<00:05:04.990><c> native</c><00:05:05.350><c> browser</c><00:05:05.740><c> support</c><00:05:06.450><c> it</c><00:05:07.450><c> allows</c>

00:05:07.650 --> 00:05:07.660 align:start position:0%
with native browser support it allows
 

00:05:07.660 --> 00:05:09.540 align:start position:0%
with native browser support it allows
using<00:05:07.960><c> a</c><00:05:08.140><c> variety</c><00:05:08.350><c> of</c><00:05:08.530><c> mechanisms</c><00:05:08.740><c> from</c>

00:05:09.540 --> 00:05:09.550 align:start position:0%
using a variety of mechanisms from
 

00:05:09.550 --> 00:05:12.030 align:start position:0%
using a variety of mechanisms from
hybrid<00:05:09.820><c> to</c><00:05:10.240><c> full</c><00:05:10.420><c> distribute</c><00:05:10.870><c> it</c><00:05:10.990><c> to</c><00:05:11.740><c> create</c><00:05:11.950><c> a</c>

00:05:12.030 --> 00:05:12.040 align:start position:0%
hybrid to full distribute it to create a
 

00:05:12.040 --> 00:05:15.390 align:start position:0%
hybrid to full distribute it to create a
peer-to-peer<00:05:12.370><c> browser-based</c><00:05:13.350><c> network</c><00:05:14.400><c> and</c>

00:05:15.390 --> 00:05:15.400 align:start position:0%
peer-to-peer browser-based network and
 

00:05:15.400 --> 00:05:17.670 align:start position:0%
peer-to-peer browser-based network and
not<00:05:15.580><c> only</c><00:05:15.730><c> that</c><00:05:15.900><c> it</c><00:05:16.900><c> also</c><00:05:17.050><c> enables</c><00:05:17.560><c> the</c>

00:05:17.670 --> 00:05:17.680 align:start position:0%
not only that it also enables the
 

00:05:17.680 --> 00:05:19.410 align:start position:0%
not only that it also enables the
diversity<00:05:18.250><c> of</c><00:05:18.280><c> devices</c><00:05:18.790><c> to</c><00:05:18.820><c> connect</c><00:05:19.210><c> to</c><00:05:19.300><c> this</c>

00:05:19.410 --> 00:05:19.420 align:start position:0%
diversity of devices to connect to this
 

00:05:19.420 --> 00:05:22.650 align:start position:0%
diversity of devices to connect to this
network<00:05:19.710><c> from</c><00:05:20.710><c> high-performance</c><00:05:21.430><c> servers</c><00:05:21.660><c> to</c>

00:05:22.650 --> 00:05:22.660 align:start position:0%
network from high-performance servers to
 

00:05:22.660 --> 00:05:27.870 align:start position:0%
network from high-performance servers to
low<00:05:22.810><c> resource</c><00:05:23.140><c> devices</c><00:05:23.680><c> think</c><00:05:24.640><c> iot</c><00:05:26.880><c> we're</c>

00:05:27.870 --> 00:05:27.880 align:start position:0%
low resource devices think iot we're
 

00:05:27.880 --> 00:05:30.060 align:start position:0%
low resource devices think iot we're
also<00:05:28.060><c> using</c><00:05:28.420><c> pops</c><00:05:29.050><c> up</c><00:05:29.260><c> for</c><00:05:29.530><c> new</c><00:05:29.650><c> real-time</c>

00:05:30.060 --> 00:05:30.070 align:start position:0%
also using pops up for new real-time
 

00:05:30.070 --> 00:05:31.920 align:start position:0%
also using pops up for new real-time
data<00:05:30.370><c> propagation</c><00:05:31.030><c> in</c><00:05:31.450><c> the</c><00:05:31.600><c> kitchenette</c>

00:05:31.920 --> 00:05:31.930 align:start position:0%
data propagation in the kitchenette
 

00:05:31.930 --> 00:05:35.040 align:start position:0%
data propagation in the kitchenette
Network<00:05:32.790><c> we've</c><00:05:33.790><c> been</c><00:05:33.910><c> using</c><00:05:34.090><c> Li</c><00:05:34.360><c> p2p</c><00:05:34.750><c> floods</c>

00:05:35.040 --> 00:05:35.050 align:start position:0%
Network we've been using Li p2p floods
 

00:05:35.050 --> 00:05:38.250 align:start position:0%
Network we've been using Li p2p floods
up<00:05:35.260><c> for</c><00:05:35.530><c> internal</c><00:05:35.950><c> prototyping</c><00:05:37.110><c> but</c><00:05:38.110><c> we're</c>

00:05:38.250 --> 00:05:38.260 align:start position:0%
up for internal prototyping but we're
 

00:05:38.260 --> 00:05:40.020 align:start position:0%
up for internal prototyping but we're
exploring<00:05:38.680><c> more</c><00:05:38.980><c> efficient</c><00:05:39.430><c> alternatives</c>

00:05:40.020 --> 00:05:40.030 align:start position:0%
exploring more efficient alternatives
 

00:05:40.030 --> 00:05:45.000 align:start position:0%
exploring more efficient alternatives
such<00:05:40.630><c> as</c><00:05:41.280><c> episod</c><00:05:42.780><c> gossip</c><00:05:43.780><c> table</c><00:05:43.990><c> both</c><00:05:44.800><c> from</c>

00:05:45.000 --> 00:05:45.010 align:start position:0%
such as episod gossip table both from
 

00:05:45.010 --> 00:05:48.870 align:start position:0%
such as episod gossip table both from
Luigi<00:05:45.430><c> as</c><00:05:45.520><c> well</c><00:05:46.650><c> epidemic</c><00:05:47.650><c> registries</c><00:05:48.250><c> and</c>

00:05:48.870 --> 00:05:48.880 align:start position:0%
Luigi as well epidemic registries and
 

00:05:48.880 --> 00:05:54.900 align:start position:0%
Luigi as well epidemic registries and
other<00:05:49.090><c> and</c><00:05:49.390><c> orders</c><00:05:53.100><c> so</c><00:05:54.100><c> how</c><00:05:54.340><c> those</c><00:05:54.580><c> data</c>

00:05:54.900 --> 00:05:54.910 align:start position:0%
other and orders so how those data
 

00:05:54.910 --> 00:05:56.580 align:start position:0%
other and orders so how those data
propagation<00:05:55.600><c> works</c><00:05:55.930><c> in</c><00:05:56.170><c> the</c><00:05:56.230><c> kids</c><00:05:56.410><c> net</c>

00:05:56.580 --> 00:05:56.590 align:start position:0%
propagation works in the kids net
 

00:05:56.590 --> 00:06:01.080 align:start position:0%
propagation works in the kids net
network<00:05:58.470><c> each</c><00:05:59.470><c> peer</c><00:05:59.830><c> in</c><00:05:59.920><c> the</c><00:06:00.010><c> network</c><00:06:00.370><c> tracks</c>

00:06:01.080 --> 00:06:01.090 align:start position:0%
network each peer in the network tracks
 

00:06:01.090 --> 00:06:03.600 align:start position:0%
network each peer in the network tracks
a<00:06:01.300><c> subset</c><00:06:01.750><c> of</c><00:06:01.780><c> slices</c><00:06:02.350><c> and</c><00:06:02.530><c> also</c><00:06:03.070><c> seats</c><00:06:03.370><c> them</c>

00:06:03.600 --> 00:06:03.610 align:start position:0%
a subset of slices and also seats them
 

00:06:03.610 --> 00:06:07.140 align:start position:0%
a subset of slices and also seats them
to<00:06:03.760><c> other</c><00:06:03.880><c> peers</c><00:06:05.040><c> this</c><00:06:06.040><c> is</c><00:06:06.190><c> crucial</c><00:06:06.460><c> to</c><00:06:06.670><c> enable</c>

00:06:07.140 --> 00:06:07.150 align:start position:0%
to other peers this is crucial to enable
 

00:06:07.150 --> 00:06:09.690 align:start position:0%
to other peers this is crucial to enable
data<00:06:07.570><c> availability</c><00:06:08.140><c> across</c><00:06:09.040><c> flight</c><00:06:09.400><c> nodes</c>

00:06:09.690 --> 00:06:09.700 align:start position:0%
data availability across flight nodes
 

00:06:09.700 --> 00:06:13.770 align:start position:0%
data availability across flight nodes
and<00:06:10.620><c> this</c><00:06:11.620><c> also</c><00:06:11.920><c> reduces</c><00:06:12.220><c> reliance</c><00:06:13.150><c> on</c><00:06:13.330><c> full</c>

00:06:13.770 --> 00:06:13.780 align:start position:0%
and this also reduces reliance on full
 

00:06:13.780 --> 00:06:18.870 align:start position:0%
and this also reduces reliance on full
interim<00:06:14.350><c> nodes</c><00:06:17.010><c> we</c><00:06:18.010><c> use</c><00:06:18.160><c> a</c><00:06:18.190><c> combination</c><00:06:18.460><c> of</c>

00:06:18.870 --> 00:06:18.880 align:start position:0%
interim nodes we use a combination of
 

00:06:18.880 --> 00:06:21.720 align:start position:0%
interim nodes we use a combination of
parameters<00:06:19.060><c> to</c><00:06:19.960><c> determine</c><00:06:20.440><c> which</c><00:06:20.920><c> slice</c><00:06:21.250><c> the</c>

00:06:21.720 --> 00:06:21.730 align:start position:0%
parameters to determine which slice the
 

00:06:21.730 --> 00:06:26.730 align:start position:0%
parameters to determine which slice the
peer<00:06:21.940><c> Strachan</c><00:06:23.490><c> the</c><00:06:24.490><c> users</c><00:06:24.820><c> account</c><00:06:25.290><c> taps</c><00:06:26.290><c> and</c>

00:06:26.730 --> 00:06:26.740 align:start position:0%
peer Strachan the users account taps and
 

00:06:26.740 --> 00:06:29.180 align:start position:0%
peer Strachan the users account taps and
tokens<00:06:27.160><c> to</c><00:06:27.310><c> the</c><00:06:27.340><c> user</c><00:06:27.550><c> interacts</c><00:06:28.270><c> with</c><00:06:28.360><c> and</c>

00:06:29.180 --> 00:06:29.190 align:start position:0%
tokens to the user interacts with and
 

00:06:29.190 --> 00:06:32.130 align:start position:0%
tokens to the user interacts with and
also<00:06:30.190><c> arbitrary</c><00:06:30.880><c> slices</c><00:06:31.390><c> the</c><00:06:31.510><c> decline</c><00:06:31.840><c> gets</c>

00:06:32.130 --> 00:06:32.140 align:start position:0%
also arbitrary slices the decline gets
 

00:06:32.140 --> 00:06:34.200 align:start position:0%
also arbitrary slices the decline gets
assigned<00:06:32.560><c> based</c><00:06:33.310><c> on</c><00:06:33.580><c> a</c><00:06:33.700><c> notion</c><00:06:33.970><c> of</c>

00:06:34.200 --> 00:06:34.210 align:start position:0%
assigned based on a notion of
 

00:06:34.210 --> 00:06:36.330 align:start position:0%
assigned based on a notion of
cryptographic<00:06:34.600><c> distance</c><00:06:35.260><c> of</c><00:06:35.440><c> the</c><00:06:35.740><c> peers</c><00:06:36.070><c> hash</c>

00:06:36.330 --> 00:06:36.340 align:start position:0%
cryptographic distance of the peers hash
 

00:06:36.340 --> 00:06:40.640 align:start position:0%
cryptographic distance of the peers hash
and<00:06:36.610><c> the</c><00:06:36.790><c> slice</c><00:06:37.000><c> hash</c>

00:06:40.640 --> 00:06:40.650 align:start position:0%
 
 

00:06:40.650 --> 00:06:45.360 align:start position:0%
 
so<00:06:41.650><c> how</c><00:06:41.949><c> secure</c><00:06:42.430><c> is</c><00:06:42.580><c> this</c><00:06:43.860><c> when</c><00:06:44.860><c> creating</c><00:06:45.129><c> the</c>

00:06:45.360 --> 00:06:45.370 align:start position:0%
so how secure is this when creating the
 

00:06:45.370 --> 00:06:48.629 align:start position:0%
so how secure is this when creating the
state<00:06:45.639><c> the</c><00:06:46.539><c> key</c><00:06:46.780><c> is</c><00:06:47.080><c> to</c><00:06:47.979><c> know</c><00:06:48.129><c> what's</c><00:06:48.490><c> the</c>

00:06:48.629 --> 00:06:48.639 align:start position:0%
state the key is to know what's the
 

00:06:48.639 --> 00:06:51.869 align:start position:0%
state the key is to know what's the
canonical<00:06:48.879><c> block</c><00:06:49.330><c> 3</c><00:06:49.569><c> header</c><00:06:50.430><c> it's</c><00:06:51.430><c> a</c><00:06:51.520><c> critical</c>

00:06:51.869 --> 00:06:51.879 align:start position:0%
canonical block 3 header it's a critical
 

00:06:51.879 --> 00:06:54.240 align:start position:0%
canonical block 3 header it's a critical
operation<00:06:52.379><c> but</c><00:06:53.379><c> it's</c><00:06:53.500><c> not</c><00:06:53.650><c> necessarily</c><00:06:54.039><c> a</c>

00:06:54.240 --> 00:06:54.250 align:start position:0%
operation but it's not necessarily a
 

00:06:54.250 --> 00:06:57.149 align:start position:0%
operation but it's not necessarily a
very<00:06:54.490><c> intensive</c><00:06:55.030><c> one</c><00:06:55.650><c> resource</c><00:06:56.650><c> intense</c><00:06:56.979><c> one</c>

00:06:57.149 --> 00:06:57.159 align:start position:0%
very intensive one resource intense one
 

00:06:57.159 --> 00:07:00.570 align:start position:0%
very intensive one resource intense one
sir<00:06:58.800><c> there</c><00:06:59.800><c> are</c><00:06:59.830><c> several</c><00:07:00.099><c> ways</c><00:07:00.340><c> to</c><00:07:00.400><c> accomplish</c>

00:07:00.570 --> 00:07:00.580 align:start position:0%
sir there are several ways to accomplish
 

00:07:00.580 --> 00:07:03.839 align:start position:0%
sir there are several ways to accomplish
that<00:07:01.020><c> we</c><00:07:02.020><c> can</c><00:07:02.169><c> ask</c><00:07:02.319><c> a</c><00:07:02.440><c> bootstrap</c><00:07:02.830><c> note</c><00:07:03.069><c> for</c><00:07:03.819><c> a</c>

00:07:03.839 --> 00:07:03.849 align:start position:0%
that we can ask a bootstrap note for a
 

00:07:03.849 --> 00:07:06.629 align:start position:0%
that we can ask a bootstrap note for a
canonical<00:07:04.060><c> block</c><00:07:04.479><c> header</c><00:07:04.720><c> for</c><00:07:05.169><c> example</c><00:07:05.639><c> pica</c>

00:07:06.629 --> 00:07:06.639 align:start position:0%
canonical block header for example pica
 

00:07:06.639 --> 00:07:08.159 align:start position:0%
canonical block header for example pica
number<00:07:06.940><c> five</c><00:07:07.240><c> five</c><00:07:07.690><c> million</c><00:07:08.020><c> nine</c><00:07:08.139><c> hundred</c>

00:07:08.159 --> 00:07:08.169 align:start position:0%
number five five million nine hundred
 

00:07:08.169 --> 00:07:10.050 align:start position:0%
number five five million nine hundred
thousand<00:07:08.800><c> or</c><00:07:08.919><c> something</c><00:07:09.069><c> and</c><00:07:09.400><c> then</c><00:07:09.759><c> start</c>

00:07:10.050 --> 00:07:10.060 align:start position:0%
thousand or something and then start
 

00:07:10.060 --> 00:07:14.339 align:start position:0%
thousand or something and then start
sinking<00:07:10.389><c> from</c><00:07:10.509><c> there</c><00:07:11.159><c> or</c><00:07:13.050><c> just</c><00:07:14.050><c> receive</c><00:07:14.319><c> the</c>

00:07:14.339 --> 00:07:14.349 align:start position:0%
sinking from there or just receive the
 

00:07:14.349 --> 00:07:16.320 align:start position:0%
sinking from there or just receive the
block<00:07:14.590><c> headers</c><00:07:14.889><c> verifying</c><00:07:15.729><c> the</c><00:07:15.880><c> number</c><00:07:16.150><c> and</c>

00:07:16.320 --> 00:07:16.330 align:start position:0%
block headers verifying the number and
 

00:07:16.330 --> 00:07:18.089 align:start position:0%
block headers verifying the number and
the<00:07:16.479><c> seal</c><00:07:16.659><c> of</c><00:07:16.690><c> course</c><00:07:16.990><c> and</c><00:07:17.229><c> then</c><00:07:17.590><c> ask</c><00:07:17.770><c> for</c><00:07:17.949><c> its</c>

00:07:18.089 --> 00:07:18.099 align:start position:0%
the seal of course and then ask for its
 

00:07:18.099 --> 00:07:20.279 align:start position:0%
the seal of course and then ask for its
parent<00:07:18.400><c> and</c><00:07:18.610><c> a</c><00:07:18.729><c> parent</c><00:07:18.970><c> of</c><00:07:19.060><c> its</c><00:07:19.180><c> parent</c><00:07:19.479><c> so</c><00:07:20.139><c> on</c>

00:07:20.279 --> 00:07:20.289 align:start position:0%
parent and a parent of its parent so on
 

00:07:20.289 --> 00:07:22.020 align:start position:0%
parent and a parent of its parent so on
and<00:07:20.409><c> so</c><00:07:20.500><c> forth</c><00:07:20.740><c> until</c><00:07:20.919><c> you</c><00:07:21.159><c> reach</c><00:07:21.430><c> at</c><00:07:21.580><c> frosted</c>

00:07:22.020 --> 00:07:22.030 align:start position:0%
and so forth until you reach at frosted
 

00:07:22.030 --> 00:07:25.800 align:start position:0%
and so forth until you reach at frosted
point<00:07:22.919><c> or</c><00:07:23.919><c> you</c><00:07:24.550><c> can</c><00:07:24.699><c> subscribe</c><00:07:25.270><c> to</c><00:07:25.300><c> some</c><00:07:25.690><c> of</c>

00:07:25.800 --> 00:07:25.810 align:start position:0%
point or you can subscribe to some of
 

00:07:25.810 --> 00:07:29.430 align:start position:0%
point or you can subscribe to some of
the<00:07:25.930><c> network</c><00:07:26.289><c> to</c><00:07:27.190><c> some</c><00:07:27.340><c> network</c><00:07:27.639><c> of</c><00:07:27.759><c> trust</c><00:07:28.440><c> not</c>

00:07:29.430 --> 00:07:29.440 align:start position:0%
the network to some network of trust not
 

00:07:29.440 --> 00:07:33.420 align:start position:0%
the network to some network of trust not
my<00:07:29.620><c> favorite</c><00:07:30.099><c> one</c><00:07:30.900><c> or</c><00:07:31.900><c> you</c><00:07:32.800><c> can</c><00:07:32.919><c> always</c><00:07:33.069><c> run</c>

00:07:33.420 --> 00:07:33.430 align:start position:0%
my favorite one or you can always run
 

00:07:33.430 --> 00:07:35.550 align:start position:0%
my favorite one or you can always run
your<00:07:33.460><c> own</c><00:07:33.639><c> note</c><00:07:33.940><c> and</c><00:07:34.270><c> request</c><00:07:34.900><c> data</c><00:07:35.110><c> over</c>

00:07:35.550 --> 00:07:35.560 align:start position:0%
your own note and request data over
 

00:07:35.560 --> 00:07:43.020 align:start position:0%
your own note and request data over
every<00:07:35.800><c> see</c><00:07:36.300><c> that's</c><00:07:37.300><c> a</c><00:07:37.389><c> job</c><00:07:41.490><c> we</c><00:07:42.490><c> maintaining</c>

00:07:43.020 --> 00:07:43.030 align:start position:0%
every see that's a job we maintaining
 

00:07:43.030 --> 00:07:45.300 align:start position:0%
every see that's a job we maintaining
the<00:07:43.300><c> security</c><00:07:43.810><c> guarantees</c><00:07:44.199><c> provided</c><00:07:44.830><c> by</c>

00:07:45.300 --> 00:07:45.310 align:start position:0%
the security guarantees provided by
 

00:07:45.310 --> 00:07:49.320 align:start position:0%
the security guarantees provided by
Merkle<00:07:45.789><c> trees</c><00:07:47.190><c> slices</c><00:07:48.190><c> contain</c><00:07:48.520><c> all</c><00:07:48.789><c> the</c>

00:07:49.320 --> 00:07:49.330 align:start position:0%
Merkle trees slices contain all the
 

00:07:49.330 --> 00:07:51.209 align:start position:0%
Merkle trees slices contain all the
required<00:07:49.690><c> information</c><00:07:49.840><c> to</c><00:07:50.800><c> perform</c>

00:07:51.209 --> 00:07:51.219 align:start position:0%
required information to perform
 

00:07:51.219 --> 00:07:57.540 align:start position:0%
required information to perform
cryptographic<00:07:51.819><c> verification</c><00:07:55.620><c> so</c><00:07:56.620><c> what</c><00:07:57.460><c> are</c>

00:07:57.540 --> 00:07:57.550 align:start position:0%
cryptographic verification so what are
 

00:07:57.550 --> 00:08:02.010 align:start position:0%
cryptographic verification so what are
the<00:07:57.639><c> takeaways</c><00:07:59.279><c> we</c><00:08:00.279><c> have</c><00:08:00.430><c> slices</c><00:08:01.029><c> which</c><00:08:01.870><c> are</c>

00:08:02.010 --> 00:08:02.020 align:start position:0%
the takeaways we have slices which are
 

00:08:02.020 --> 00:08:04.279 align:start position:0%
the takeaways we have slices which are
convenient<00:08:02.590><c> but</c><00:08:02.789><c> conveniently</c><00:08:03.789><c> packed</c>

00:08:04.279 --> 00:08:04.289 align:start position:0%
convenient but conveniently packed
 

00:08:04.289 --> 00:08:08.909 align:start position:0%
convenient but conveniently packed
Merkle's<00:08:05.289><c> of</c><00:08:05.440><c> trees</c><00:08:05.680><c> that</c><00:08:06.130><c> contain</c><00:08:06.460><c> state</c><00:08:07.919><c> we</c>

00:08:08.909 --> 00:08:08.919 align:start position:0%
Merkle's of trees that contain state we
 

00:08:08.919 --> 00:08:10.950 align:start position:0%
Merkle's of trees that contain state we
had<00:08:09.099><c> we</c><00:08:09.819><c> have</c><00:08:10.000><c> kids</c><00:08:10.270><c> Annette</c><00:08:10.539><c> which</c><00:08:10.779><c> is</c><00:08:10.930><c> a</c>

00:08:10.950 --> 00:08:10.960 align:start position:0%
had we have kids Annette which is a
 

00:08:10.960 --> 00:08:12.930 align:start position:0%
had we have kids Annette which is a
peer-to-peer<00:08:11.380><c> network</c><00:08:12.039><c> of</c><00:08:12.190><c> flight</c><00:08:12.430><c> clients</c>

00:08:12.930 --> 00:08:12.940 align:start position:0%
peer-to-peer network of flight clients
 

00:08:12.940 --> 00:08:17.070 align:start position:0%
peer-to-peer network of flight clients
sitting<00:08:13.479><c> slices</c><00:08:14.080><c> and</c><00:08:15.419><c> we</c><00:08:16.419><c> have</c><00:08:16.569><c> full</c><00:08:16.810><c> nodes</c>

00:08:17.070 --> 00:08:17.080 align:start position:0%
sitting slices and we have full nodes
 

00:08:17.080 --> 00:08:19.409 align:start position:0%
sitting slices and we have full nodes
each<00:08:17.560><c> young</c><00:08:17.800><c> clients</c><00:08:18.310><c> synchronizing</c><00:08:19.060><c> state</c>

00:08:19.409 --> 00:08:19.419 align:start position:0%
each young clients synchronizing state
 

00:08:19.419 --> 00:08:23.180 align:start position:0%
each young clients synchronizing state
making<00:08:19.900><c> slices</c><00:08:20.529><c> available</c><00:08:21.190><c> for</c><00:08:21.550><c> kids</c><00:08:21.729><c> Annette</c>

00:08:23.180 --> 00:08:23.190 align:start position:0%
making slices available for kids Annette
 

00:08:23.190 --> 00:08:33.839 align:start position:0%
making slices available for kids Annette
thank<00:08:24.190><c> you</c>

00:08:33.839 --> 00:08:33.849 align:start position:0%
 
 

00:08:33.849 --> 00:08:35.909 align:start position:0%
 
you