WEBVTT
Kind: captions
Language: en

00:00:00.780 --> 00:00:02.629 align:start position:0%
 
this<00:00:01.110><c> project</c><00:00:01.469><c> has</c><00:00:01.560><c> been</c><00:00:01.589><c> going</c><00:00:01.770><c> for</c><00:00:02.250><c> a</c><00:00:02.429><c> little</c>

00:00:02.629 --> 00:00:02.639 align:start position:0%
this project has been going for a little
 

00:00:02.639 --> 00:00:05.150 align:start position:0%
this project has been going for a little
bit<00:00:02.820><c> less</c><00:00:02.939><c> than</c><00:00:03.090><c> a</c><00:00:03.179><c> year</c><00:00:03.540><c> and</c><00:00:03.959><c> it</c><00:00:04.650><c> started</c><00:00:04.980><c> as</c><00:00:05.130><c> a</c>

00:00:05.150 --> 00:00:05.160 align:start position:0%
bit less than a year and it started as a
 

00:00:05.160 --> 00:00:08.000 align:start position:0%
bit less than a year and it started as a
little<00:00:06.029><c> curiosity</c><00:00:06.720><c> but</c><00:00:07.140><c> then</c><00:00:07.379><c> it</c><00:00:07.710><c> sort</c><00:00:07.890><c> of</c>

00:00:08.000 --> 00:00:08.010 align:start position:0%
little curiosity but then it sort of
 

00:00:08.010 --> 00:00:10.790 align:start position:0%
little curiosity but then it sort of
meandered<00:00:08.970><c> into</c><00:00:09.300><c> all</c><00:00:09.960><c> sorts</c><00:00:10.230><c> of</c><00:00:10.260><c> rabbit</c><00:00:10.559><c> holes</c>

00:00:10.790 --> 00:00:10.800 align:start position:0%
meandered into all sorts of rabbit holes
 

00:00:10.800 --> 00:00:13.730 align:start position:0%
meandered into all sorts of rabbit holes
and<00:00:11.809><c> currently</c><00:00:12.809><c> it's</c><00:00:12.990><c> been</c><00:00:13.139><c> supported</c><00:00:13.469><c> by</c>

00:00:13.730 --> 00:00:13.740 align:start position:0%
and currently it's been supported by
 

00:00:13.740 --> 00:00:15.650 align:start position:0%
and currently it's been supported by
three<00:00:13.980><c> different</c><00:00:14.190><c> organizations</c><00:00:14.700><c> it's</c><00:00:15.570><c> a</c>

00:00:15.650 --> 00:00:15.660 align:start position:0%
three different organizations it's a
 

00:00:15.660 --> 00:00:17.330 align:start position:0%
three different organizations it's a
theorem<00:00:16.170><c> Foundation</c><00:00:16.619><c> and</c><00:00:16.770><c> form</c><00:00:16.920><c> of</c><00:00:17.039><c> grants</c>

00:00:17.330 --> 00:00:17.340 align:start position:0%
theorem Foundation and form of grants
 

00:00:17.340 --> 00:00:22.340 align:start position:0%
theorem Foundation and form of grants
and<00:00:17.670><c> also</c><00:00:18.270><c> buy</c><00:00:18.720><c> in</c><00:00:18.869><c> fewer</c><00:00:20.900><c> buy-in</c><00:00:21.900><c> contracts</c>

00:00:22.340 --> 00:00:22.350 align:start position:0%
and also buy in fewer buy-in contracts
 

00:00:22.350 --> 00:00:23.810 align:start position:0%
and also buy in fewer buy-in contracts
with<00:00:22.500><c> me</c><00:00:22.619><c> an</c><00:00:22.680><c> interchange</c><00:00:23.220><c> foundation</c><00:00:23.730><c> as</c>

00:00:23.810 --> 00:00:23.820 align:start position:0%
with me an interchange foundation as
 

00:00:23.820 --> 00:00:25.340 align:start position:0%
with me an interchange foundation as
well<00:00:24.000><c> you</c><00:00:24.150><c> probably</c><00:00:24.449><c> know</c><00:00:24.660><c> about</c><00:00:24.779><c> interchange</c>

00:00:25.340 --> 00:00:25.350 align:start position:0%
well you probably know about interchange
 

00:00:25.350 --> 00:00:29.779 align:start position:0%
well you probably know about interchange
foundation<00:00:25.859><c> by</c><00:00:26.039><c> a</c><00:00:26.340><c> cosmos</c><00:00:27.210><c> product</c><00:00:28.429><c> so</c><00:00:29.429><c> let's</c>

00:00:29.779 --> 00:00:29.789 align:start position:0%
foundation by a cosmos product so let's
 

00:00:29.789 --> 00:00:32.269 align:start position:0%
foundation by a cosmos product so let's
start<00:00:30.349><c> so</c><00:00:31.349><c> I'm</c><00:00:31.529><c> going</c><00:00:31.710><c> to</c><00:00:31.800><c> skip</c><00:00:32.040><c> all</c><00:00:32.130><c> the</c>

00:00:32.269 --> 00:00:32.279 align:start position:0%
start so I'm going to skip all the
 

00:00:32.279 --> 00:00:34.069 align:start position:0%
start so I'm going to skip all the
slides<00:00:32.520><c> that</c><00:00:32.669><c> I</c><00:00:32.969><c> had</c><00:00:33.120><c> before</c><00:00:33.270><c> because</c><00:00:33.809><c> you've</c>

00:00:34.069 --> 00:00:34.079 align:start position:0%
slides that I had before because you've
 

00:00:34.079 --> 00:00:35.479 align:start position:0%
slides that I had before because you've
probably<00:00:34.200><c> seen</c><00:00:34.500><c> them</c><00:00:34.649><c> so</c><00:00:35.160><c> we</c><00:00:35.250><c> start</c><00:00:35.460><c> right</c>

00:00:35.479 --> 00:00:35.489 align:start position:0%
probably seen them so we start right
 

00:00:35.489 --> 00:00:37.040 align:start position:0%
probably seen them so we start right
from<00:00:35.640><c> the</c><00:00:35.850><c> meet</c><00:00:36.090><c> about</c><00:00:36.510><c> what</c><00:00:36.809><c> is</c><00:00:36.930><c> the</c>

00:00:37.040 --> 00:00:37.050 align:start position:0%
from the meet about what is the
 

00:00:37.050 --> 00:00:39.319 align:start position:0%
from the meet about what is the
difference<00:00:37.350><c> between</c><00:00:37.410><c> the</c><00:00:38.340><c> gas</c><00:00:38.820><c> and</c><00:00:38.850><c> turbid</c>

00:00:39.319 --> 00:00:39.329 align:start position:0%
difference between the gas and turbid
 

00:00:39.329 --> 00:00:41.869 align:start position:0%
difference between the gas and turbid
gas<00:00:39.480><c> and</c><00:00:39.750><c> so</c><00:00:40.500><c> on</c><00:00:40.860><c> the</c><00:00:41.010><c> slide</c><00:00:41.129><c> you</c><00:00:41.370><c> could</c><00:00:41.520><c> see</c><00:00:41.700><c> on</c>

00:00:41.869 --> 00:00:41.879 align:start position:0%
gas and so on the slide you could see on
 

00:00:41.879 --> 00:00:43.340 align:start position:0%
gas and so on the slide you could see on
the<00:00:42.030><c> left</c><00:00:42.480><c> hand</c><00:00:42.629><c> side</c><00:00:42.840><c> you</c><00:00:42.989><c> could</c><00:00:43.140><c> see</c><00:00:43.320><c> like</c>

00:00:43.340 --> 00:00:43.350 align:start position:0%
the left hand side you could see like
 

00:00:43.350 --> 00:00:46.549 align:start position:0%
the left hand side you could see like
the<00:00:43.530><c> in</c><00:00:44.309><c> the</c><00:00:44.460><c> cerium</c><00:00:44.879><c> the</c><00:00:45.120><c> this</c><00:00:45.480><c> the</c><00:00:45.870><c> state</c><00:00:46.289><c> of</c>

00:00:46.549 --> 00:00:46.559 align:start position:0%
the in the cerium the this the state of
 

00:00:46.559 --> 00:00:49.729 align:start position:0%
the in the cerium the this the state of
accounts<00:00:47.129><c> and</c><00:00:47.309><c> the</c><00:00:48.270><c> contracts</c><00:00:48.960><c> and</c><00:00:49.110><c> their</c>

00:00:49.729 --> 00:00:49.739 align:start position:0%
accounts and the contracts and their
 

00:00:49.739 --> 00:00:51.560 align:start position:0%
accounts and the contracts and their
storage<00:00:50.160><c> is</c><00:00:50.309><c> modeled</c><00:00:50.700><c> as</c><00:00:50.820><c> the</c><00:00:50.940><c> Petruchio</c><00:00:51.390><c> tree</c>

00:00:51.560 --> 00:00:51.570 align:start position:0%
storage is modeled as the Petruchio tree
 

00:00:51.570 --> 00:00:53.779 align:start position:0%
storage is modeled as the Petruchio tree
which<00:00:52.050><c> is</c><00:00:52.079><c> essentially</c><00:00:52.649><c> a</c><00:00:52.800><c> radix</c><00:00:53.250><c> tree</c><00:00:53.579><c> of</c>

00:00:53.779 --> 00:00:53.789 align:start position:0%
which is essentially a radix tree of
 

00:00:53.789 --> 00:00:57.049 align:start position:0%
which is essentially a radix tree of
radix<00:00:54.449><c> 16</c><00:00:54.960><c> with</c><00:00:55.590><c> some</c><00:00:55.860><c> refinements</c><00:00:56.699><c> to</c><00:00:56.910><c> be</c>

00:00:57.049 --> 00:00:57.059 align:start position:0%
radix 16 with some refinements to be
 

00:00:57.059 --> 00:01:00.500 align:start position:0%
radix 16 with some refinements to be
able<00:00:57.149><c> to</c><00:00:57.329><c> get</c><00:00:57.719><c> rid</c><00:00:57.870><c> of</c><00:00:57.989><c> some</c><00:00:58.199><c> some</c><00:00:59.300><c> waste</c><00:01:00.300><c> of</c>

00:01:00.500 --> 00:01:00.510 align:start position:0%
able to get rid of some some waste of
 

00:01:00.510 --> 00:01:03.680 align:start position:0%
able to get rid of some some waste of
waste<00:01:01.109><c> of</c><00:01:01.289><c> space</c><00:01:01.469><c> and</c><00:01:01.850><c> when</c><00:01:02.850><c> you're</c><00:01:03.149><c> more</c><00:01:03.570><c> do</c>

00:01:03.680 --> 00:01:03.690 align:start position:0%
waste of space and when you're more do
 

00:01:03.690 --> 00:01:05.570 align:start position:0%
waste of space and when you're more do
it<00:01:03.809><c> like</c><00:01:03.989><c> that</c><00:01:04.170><c> and</c><00:01:04.409><c> you</c><00:01:04.470><c> want</c><00:01:04.650><c> to</c><00:01:04.830><c> persist</c><00:01:05.369><c> it</c>

00:01:05.570 --> 00:01:05.580 align:start position:0%
it like that and you want to persist it
 

00:01:05.580 --> 00:01:07.730 align:start position:0%
it like that and you want to persist it
and<00:01:05.700><c> then</c><00:01:05.790><c> database</c><00:01:06.180><c> the</c><00:01:06.689><c> persistence</c><00:01:07.470><c> you</c>

00:01:07.730 --> 00:01:07.740 align:start position:0%
and then database the persistence you
 

00:01:07.740 --> 00:01:09.560 align:start position:0%
and then database the persistence you
looks<00:01:07.979><c> like</c><00:01:08.189><c> on</c><00:01:08.340><c> the</c><00:01:08.700><c> right</c><00:01:08.850><c> hand</c><00:01:09.090><c> side</c><00:01:09.299><c> which</c>

00:01:09.560 --> 00:01:09.570 align:start position:0%
looks like on the right hand side which
 

00:01:09.570 --> 00:01:12.080 align:start position:0%
looks like on the right hand side which
is<00:01:09.600><c> the</c><00:01:09.900><c> key</c><00:01:10.140><c> of</c><00:01:10.350><c> the</c><00:01:10.650><c> so</c><00:01:11.369><c> it</c><00:01:11.640><c> basically</c><00:01:12.000><c> the</c>

00:01:12.080 --> 00:01:12.090 align:start position:0%
is the key of the so it basically the
 

00:01:12.090 --> 00:01:13.760 align:start position:0%
is the key of the so it basically the
whole<00:01:12.299><c> structure</c><00:01:12.600><c> every</c><00:01:13.170><c> node</c><00:01:13.380><c> in</c><00:01:13.590><c> its</c>

00:01:13.760 --> 00:01:13.770 align:start position:0%
whole structure every node in its
 

00:01:13.770 --> 00:01:16.190 align:start position:0%
whole structure every node in its
patricia<00:01:14.100><c> tree</c><00:01:14.369><c> is</c><00:01:14.520><c> split</c><00:01:14.850><c> and</c><00:01:15.030><c> is</c><00:01:15.540><c> one</c><00:01:15.810><c> record</c>

00:01:16.190 --> 00:01:16.200 align:start position:0%
patricia tree is split and is one record
 

00:01:16.200 --> 00:01:18.469 align:start position:0%
patricia tree is split and is one record
in<00:01:16.290><c> a</c><00:01:16.380><c> database</c><00:01:16.680><c> and</c><00:01:17.130><c> for</c><00:01:17.880><c> that</c><00:01:17.939><c> record</c><00:01:18.180><c> the</c>

00:01:18.469 --> 00:01:18.479 align:start position:0%
in a database and for that record the
 

00:01:18.479 --> 00:01:21.560 align:start position:0%
in a database and for that record the
key<00:01:18.659><c> is</c><00:01:18.810><c> the</c><00:01:18.990><c> the</c><00:01:19.290><c> hash</c><00:01:19.920><c> of</c><00:01:20.159><c> the</c><00:01:20.570><c> civilization</c>

00:01:21.560 --> 00:01:21.570 align:start position:0%
key is the the hash of the civilization
 

00:01:21.570 --> 00:01:22.880 align:start position:0%
key is the the hash of the civilization
of<00:01:21.810><c> this</c><00:01:21.960><c> node</c><00:01:22.140><c> and</c><00:01:22.350><c> the</c><00:01:22.409><c> value</c><00:01:22.710><c> is</c><00:01:22.860><c> the</c>

00:01:22.880 --> 00:01:22.890 align:start position:0%
of this node and the value is the
 

00:01:22.890 --> 00:01:25.219 align:start position:0%
of this node and the value is the
serialization<00:01:23.490><c> itself</c><00:01:24.030><c> what</c><00:01:24.570><c> it</c><00:01:24.689><c> allows</c><00:01:24.930><c> us</c>

00:01:25.219 --> 00:01:25.229 align:start position:0%
serialization itself what it allows us
 

00:01:25.229 --> 00:01:29.990 align:start position:0%
serialization itself what it allows us
to<00:01:25.380><c> do</c><00:01:25.590><c> is</c><00:01:26.659><c> let's</c><00:01:27.659><c> pretend</c><00:01:28.049><c> that</c><00:01:28.200><c> we</c><00:01:28.759><c> we</c><00:01:29.759><c> do</c><00:01:29.880><c> not</c>

00:01:29.990 --> 00:01:30.000 align:start position:0%
to do is let's pretend that we we do not
 

00:01:30.000 --> 00:01:32.510 align:start position:0%
to do is let's pretend that we we do not
have<00:01:30.240><c> that</c><00:01:30.479><c> pink</c><00:01:30.840><c> node</c><00:01:31.140><c> in</c><00:01:31.409><c> the</c><00:01:31.500><c> top</c><00:01:31.710><c> like</c><00:01:32.280><c> the</c>

00:01:32.510 --> 00:01:32.520 align:start position:0%
have that pink node in the top like the
 

00:01:32.520 --> 00:01:34.969 align:start position:0%
have that pink node in the top like the
diamond<00:01:32.850><c> pink</c><00:01:33.119><c> node</c><00:01:33.390><c> and</c><00:01:33.659><c> instead</c><00:01:34.439><c> we</c><00:01:34.680><c> we</c>

00:01:34.969 --> 00:01:34.979 align:start position:0%
diamond pink node and instead we we
 

00:01:34.979 --> 00:01:37.940 align:start position:0%
diamond pink node and instead we we
simply<00:01:35.340><c> have</c><00:01:35.610><c> a</c><00:01:36.240><c> hash</c><00:01:36.780><c> which</c><00:01:37.290><c> is</c><00:01:37.439><c> which</c><00:01:37.860><c> you</c>

00:01:37.940 --> 00:01:37.950 align:start position:0%
simply have a hash which is which you
 

00:01:37.950 --> 00:01:40.550 align:start position:0%
simply have a hash which is which you
could<00:01:38.100><c> see</c><00:01:38.280><c> that</c><00:01:38.400><c> there's</c><00:01:38.610><c> a</c><00:01:38.670><c> little</c><00:01:39.380><c> dark</c><00:01:40.380><c> and</c>

00:01:40.550 --> 00:01:40.560 align:start position:0%
could see that there's a little dark and
 

00:01:40.560 --> 00:01:43.429 align:start position:0%
could see that there's a little dark and
dark<00:01:40.979><c> rectangle</c><00:01:41.939><c> so</c><00:01:42.540><c> what</c><00:01:42.930><c> we</c><00:01:43.049><c> could</c><00:01:43.200><c> do</c><00:01:43.320><c> is</c>

00:01:43.429 --> 00:01:43.439 align:start position:0%
dark rectangle so what we could do is
 

00:01:43.439 --> 00:01:44.990 align:start position:0%
dark rectangle so what we could do is
that<00:01:43.619><c> we</c><00:01:43.770><c> could</c><00:01:43.920><c> take</c><00:01:44.130><c> that</c><00:01:44.340><c> hash</c><00:01:44.579><c> and</c><00:01:44.820><c> then</c>

00:01:44.990 --> 00:01:45.000 align:start position:0%
that we could take that hash and then
 

00:01:45.000 --> 00:01:46.999 align:start position:0%
that we could take that hash and then
use<00:01:45.180><c> it</c><00:01:45.210><c> as</c><00:01:45.450><c> the</c><00:01:45.689><c> key</c><00:01:46.170><c> in</c><00:01:46.439><c> the</c><00:01:46.530><c> database</c><00:01:46.890><c> and</c>

00:01:46.999 --> 00:01:47.009 align:start position:0%
use it as the key in the database and
 

00:01:47.009 --> 00:01:49.999 align:start position:0%
use it as the key in the database and
look<00:01:47.159><c> up</c><00:01:47.310><c> the</c><00:01:48.530><c> serialization</c><00:01:49.530><c> of</c><00:01:49.619><c> that</c><00:01:49.799><c> pink</c>

00:01:49.999 --> 00:01:50.009 align:start position:0%
look up the serialization of that pink
 

00:01:50.009 --> 00:01:52.370 align:start position:0%
look up the serialization of that pink
node<00:01:50.250><c> and</c><00:01:50.729><c> reconstruct</c><00:01:51.299><c> it</c><00:01:51.450><c> and</c><00:01:51.659><c> then</c><00:01:51.869><c> plug</c><00:01:52.259><c> it</c>

00:01:52.370 --> 00:01:52.380 align:start position:0%
node and reconstruct it and then plug it
 

00:01:52.380 --> 00:01:54.649 align:start position:0%
node and reconstruct it and then plug it
into<00:01:52.500><c> the</c><00:01:52.680><c> tree</c><00:01:52.890><c> so</c><00:01:53.490><c> that's</c><00:01:53.610><c> how</c><00:01:53.820><c> basically</c>

00:01:54.649 --> 00:01:54.659 align:start position:0%
into the tree so that's how basically
 

00:01:54.659 --> 00:01:57.020 align:start position:0%
into the tree so that's how basically
pretty<00:01:55.590><c> much</c><00:01:55.680><c> all</c><00:01:55.950><c> the</c><00:01:56.040><c> clients</c><00:01:56.340><c> do</c><00:01:56.490><c> that</c><00:01:56.670><c> as</c>

00:01:57.020 --> 00:01:57.030 align:start position:0%
pretty much all the clients do that as
 

00:01:57.030 --> 00:02:00.649 align:start position:0%
pretty much all the clients do that as
far<00:01:57.299><c> as</c><00:01:57.329><c> I</c><00:01:57.570><c> know</c><00:01:57.799><c> and</c><00:01:58.799><c> so</c><00:01:59.310><c> the</c><00:01:59.490><c> the</c><00:01:59.969><c> problem</c>

00:02:00.649 --> 00:02:00.659 align:start position:0%
far as I know and so the the problem
 

00:02:00.659 --> 00:02:02.209 align:start position:0%
far as I know and so the the problem
that<00:02:00.750><c> so</c><00:02:01.229><c> that</c><00:02:01.409><c> was</c><00:02:01.560><c> when</c><00:02:01.680><c> I</c><00:02:01.710><c> first</c><00:02:02.009><c> saw</c><00:02:02.189><c> it</c>

00:02:02.209 --> 00:02:02.219 align:start position:0%
that so that was when I first saw it
 

00:02:02.219 --> 00:02:05.359 align:start position:0%
that so that was when I first saw it
actually<00:02:02.490><c> I</c><00:02:03.000><c> I</c><00:02:03.960><c> was</c><00:02:04.409><c> a</c><00:02:04.439><c> bit</c><00:02:04.829><c> surprised</c><00:02:05.159><c> because</c>

00:02:05.359 --> 00:02:05.369 align:start position:0%
actually I I was a bit surprised because
 

00:02:05.369 --> 00:02:07.819 align:start position:0%
actually I I was a bit surprised because
for<00:02:06.360><c> me</c><00:02:06.509><c> it</c><00:02:06.689><c> wasn't</c><00:02:06.899><c> it</c><00:02:07.200><c> wouldn't</c><00:02:07.409><c> be</c><00:02:07.590><c> how</c><00:02:07.799><c> I</c>

00:02:07.819 --> 00:02:07.829 align:start position:0%
for me it wasn't it wouldn't be how I
 

00:02:07.829 --> 00:02:10.309 align:start position:0%
for me it wasn't it wouldn't be how I
would<00:02:08.340><c> do</c><00:02:08.489><c> it</c><00:02:08.640><c> and</c><00:02:08.910><c> that's</c><00:02:09.840><c> why</c><00:02:10.050><c> I</c><00:02:10.080><c> actually</c>

00:02:10.309 --> 00:02:10.319 align:start position:0%
would do it and that's why I actually
 

00:02:10.319 --> 00:02:12.380 align:start position:0%
would do it and that's why I actually
started<00:02:10.500><c> on</c><00:02:10.920><c> this</c><00:02:11.069><c> process</c><00:02:11.760><c> because</c><00:02:12.090><c> whenever</c>

00:02:12.380 --> 00:02:12.390 align:start position:0%
started on this process because whenever
 

00:02:12.390 --> 00:02:13.850 align:start position:0%
started on this process because whenever
I<00:02:12.450><c> see</c><00:02:12.629><c> something</c><00:02:12.840><c> which</c><00:02:13.110><c> doesn't</c><00:02:13.470><c> look</c><00:02:13.590><c> like</c>

00:02:13.850 --> 00:02:13.860 align:start position:0%
I see something which doesn't look like
 

00:02:13.860 --> 00:02:16.370 align:start position:0%
I see something which doesn't look like
I<00:02:13.890><c> expected</c><00:02:14.490><c> this</c><00:02:14.820><c> is</c><00:02:14.970><c> where</c><00:02:15.180><c> you</c><00:02:15.390><c> so</c><00:02:16.080><c> I</c><00:02:16.110><c> didn't</c>

00:02:16.370 --> 00:02:16.380 align:start position:0%
I expected this is where you so I didn't
 

00:02:16.380 --> 00:02:18.560 align:start position:0%
I expected this is where you so I didn't
expect<00:02:16.650><c> to</c><00:02:16.710><c> see</c><00:02:16.920><c> that</c><00:02:16.950><c> but</c><00:02:17.580><c> probably</c><00:02:18.180><c> it</c><00:02:18.450><c> was</c>

00:02:18.560 --> 00:02:18.570 align:start position:0%
expect to see that but probably it was
 

00:02:18.570 --> 00:02:21.080 align:start position:0%
expect to see that but probably it was
very<00:02:18.840><c> natural</c><00:02:19.710><c> for</c><00:02:19.830><c> other</c><00:02:19.980><c> people</c><00:02:20.310><c> so</c><00:02:20.520><c> the</c>

00:02:21.080 --> 00:02:21.090 align:start position:0%
very natural for other people so the
 

00:02:21.090 --> 00:02:22.700 align:start position:0%
very natural for other people so the
main<00:02:21.540><c> problem</c><00:02:21.870><c> here</c><00:02:21.900><c> that</c><00:02:22.140><c> I</c><00:02:22.290><c> saw</c><00:02:22.560><c> is</c><00:02:22.680><c> that</c>

00:02:22.700 --> 00:02:22.710 align:start position:0%
main problem here that I saw is that
 

00:02:22.710 --> 00:02:24.680 align:start position:0%
main problem here that I saw is that
let's<00:02:23.430><c> say</c><00:02:23.550><c> that</c><00:02:23.670><c> when</c><00:02:23.880><c> you</c><00:02:24.000><c> when</c><00:02:24.360><c> you</c><00:02:24.480><c> were</c>

00:02:24.680 --> 00:02:24.690 align:start position:0%
let's say that when you when you were
 

00:02:24.690 --> 00:02:28.040 align:start position:0%
let's say that when you when you were
only<00:02:25.560><c> have</c><00:02:25.830><c> a</c><00:02:25.860><c> root</c><00:02:26.180><c> and</c><00:02:27.180><c> nothing</c><00:02:27.570><c> else</c><00:02:27.750><c> in</c><00:02:27.960><c> the</c>

00:02:28.040 --> 00:02:28.050 align:start position:0%
only have a root and nothing else in the
 

00:02:28.050 --> 00:02:30.170 align:start position:0%
only have a root and nothing else in the
memory<00:02:28.410><c> and</c><00:02:28.590><c> then</c><00:02:28.680><c> you</c><00:02:28.800><c> want</c><00:02:29.280><c> to</c><00:02:29.340><c> fetch</c><00:02:29.850><c> that</c>

00:02:30.170 --> 00:02:30.180 align:start position:0%
memory and then you want to fetch that
 

00:02:30.180 --> 00:02:33.170 align:start position:0%
memory and then you want to fetch that
let's<00:02:30.450><c> say</c><00:02:30.570><c> element</c><00:02:30.960><c> v5</c><00:02:31.530><c> which</c><00:02:31.800><c> is</c><00:02:31.920><c> the</c><00:02:32.180><c> purple</c>

00:02:33.170 --> 00:02:33.180 align:start position:0%
let's say element v5 which is the purple
 

00:02:33.180 --> 00:02:35.750 align:start position:0%
let's say element v5 which is the purple
diamond<00:02:33.990><c> in</c><00:02:34.350><c> that</c><00:02:34.380><c> on</c><00:02:34.680><c> the</c><00:02:35.010><c> bottom</c><00:02:35.310><c> right</c><00:02:35.520><c> you</c>

00:02:35.750 --> 00:02:35.760 align:start position:0%
diamond in that on the bottom right you
 

00:02:35.760 --> 00:02:38.840 align:start position:0%
diamond in that on the bottom right you
actually<00:02:36.510><c> have</c><00:02:36.870><c> to</c><00:02:37.050><c> do</c><00:02:37.260><c> one</c><00:02:37.950><c> two</c><00:02:38.370><c> three</c>

00:02:38.840 --> 00:02:38.850 align:start position:0%
actually have to do one two three
 

00:02:38.850 --> 00:02:40.880 align:start position:0%
actually have to do one two three
lookups<00:02:39.570><c> to</c><00:02:39.660><c> the</c><00:02:39.810><c> database</c><00:02:40.170><c> and</c><00:02:40.320><c> the</c><00:02:40.620><c> reason</c>

00:02:40.880 --> 00:02:40.890 align:start position:0%
lookups to the database and the reason
 

00:02:40.890 --> 00:02:43.640 align:start position:0%
lookups to the database and the reason
for<00:02:40.920><c> that</c><00:02:41.160><c> is</c><00:02:41.310><c> because</c><00:02:41.340><c> in</c><00:02:42.060><c> order</c><00:02:42.209><c> to</c><00:02:42.650><c> retrieve</c>

00:02:43.640 --> 00:02:43.650 align:start position:0%
for that is because in order to retrieve
 

00:02:43.650 --> 00:02:46.520 align:start position:0%
for that is because in order to retrieve
the<00:02:44.570><c> diamonds</c><00:02:45.570><c> you</c><00:02:45.660><c> have</c><00:02:45.690><c> to</c><00:02:45.959><c> first</c><00:02:46.140><c> retrieve</c>

00:02:46.520 --> 00:02:46.530 align:start position:0%
the diamonds you have to first retrieve
 

00:02:46.530 --> 00:02:47.840 align:start position:0%
the diamonds you have to first retrieve
the<00:02:46.680><c> element</c><00:02:47.100><c> before</c><00:02:47.220><c> that</c><00:02:47.490><c> because</c><00:02:47.760><c> it</c>

00:02:47.840 --> 00:02:47.850 align:start position:0%
the element before that because it
 

00:02:47.850 --> 00:02:50.480 align:start position:0%
the element before that because it
contains<00:02:48.240><c> its</c><00:02:48.540><c> hash</c><00:02:48.750><c> so</c><00:02:49.320><c> an</c><00:02:49.530><c> end</c><00:02:49.709><c> so</c><00:02:49.980><c> vice</c>

00:02:50.480 --> 00:02:50.490 align:start position:0%
contains its hash so an end so vice
 

00:02:50.490 --> 00:02:52.940 align:start position:0%
contains its hash so an end so vice
versa<00:02:50.760><c> so</c><00:02:51.060><c> you</c><00:02:51.150><c> have</c><00:02:51.300><c> to</c><00:02:51.420><c> do</c><00:02:51.570><c> three</c><00:02:52.260><c> sequential</c>

00:02:52.940 --> 00:02:52.950 align:start position:0%
versa so you have to do three sequential
 

00:02:52.950 --> 00:02:54.770 align:start position:0%
versa so you have to do three sequential
lookups<00:02:53.400><c> to</c><00:02:53.489><c> the</c><00:02:53.580><c> database</c><00:02:53.970><c> you</c><00:02:54.570><c> cannot</c>

00:02:54.770 --> 00:02:54.780 align:start position:0%
lookups to the database you cannot
 

00:02:54.780 --> 00:02:56.390 align:start position:0%
lookups to the database you cannot
paralyze<00:02:55.230><c> them</c><00:02:55.410><c> because</c><00:02:55.680><c> you</c><00:02:55.800><c> there's</c><00:02:56.100><c> a</c><00:02:56.190><c> data</c>

00:02:56.390 --> 00:02:56.400 align:start position:0%
paralyze them because you there's a data
 

00:02:56.400 --> 00:03:01.370 align:start position:0%
paralyze them because you there's a data
dependency<00:02:56.970><c> there</c><00:02:57.590><c> so</c><00:02:58.590><c> that</c><00:02:59.840><c> gave</c><00:03:00.840><c> me</c><00:03:00.900><c> the</c>

00:03:01.370 --> 00:03:01.380 align:start position:0%
dependency there so that gave me the
 

00:03:01.380 --> 00:03:05.960 align:start position:0%
dependency there so that gave me the
idea<00:03:01.530><c> of</c><00:03:03.260><c> not</c><00:03:04.260><c> doing</c><00:03:04.470><c> that</c><00:03:04.650><c> so</c><00:03:04.830><c> basically</c><00:03:05.790><c> that</c>

00:03:05.960 --> 00:03:05.970 align:start position:0%
idea of not doing that so basically that
 

00:03:05.970 --> 00:03:07.340 align:start position:0%
idea of not doing that so basically that
you<00:03:06.090><c> see</c><00:03:06.270><c> in</c><00:03:06.390><c> the</c><00:03:06.450><c> red</c><00:03:06.600><c> matters</c><00:03:06.840><c> depth</c><00:03:07.140><c> should</c>

00:03:07.340 --> 00:03:07.350 align:start position:0%
you see in the red matters depth should
 

00:03:07.350 --> 00:03:09.949 align:start position:0%
you see in the red matters depth should
not<00:03:07.500><c> matter</c><00:03:07.650><c> it</c><00:03:08.370><c> means</c><00:03:08.670><c> that</c><00:03:08.910><c> how</c><00:03:09.360><c> can</c><00:03:09.630><c> we</c><00:03:09.750><c> do</c>

00:03:09.949 --> 00:03:09.959 align:start position:0%
not matter it means that how can we do
 

00:03:09.959 --> 00:03:12.350 align:start position:0%
not matter it means that how can we do
that<00:03:10.110><c> without</c><00:03:10.260><c> doing</c><00:03:11.040><c> three</c><00:03:11.280><c> lookups</c><00:03:11.640><c> or</c><00:03:11.940><c> five</c>

00:03:12.350 --> 00:03:12.360 align:start position:0%
that without doing three lookups or five
 

00:03:12.360 --> 00:03:13.970 align:start position:0%
that without doing three lookups or five
lookups<00:03:12.750><c> so</c><00:03:12.900><c> seven</c><00:03:13.200><c> would</c><00:03:13.380><c> lookups</c><00:03:13.739><c> or</c>

00:03:13.970 --> 00:03:13.980 align:start position:0%
lookups so seven would lookups or
 

00:03:13.980 --> 00:03:15.530 align:start position:0%
lookups so seven would lookups or
whatever<00:03:14.370><c> I</c><00:03:14.459><c> think</c><00:03:14.550><c> at</c><00:03:14.850><c> the</c><00:03:14.940><c> moment</c><00:03:15.030><c> an</c>

00:03:15.530 --> 00:03:15.540 align:start position:0%
whatever I think at the moment an
 

00:03:15.540 --> 00:03:17.930 align:start position:0%
whatever I think at the moment an
average<00:03:15.840><c> will</c><00:03:15.989><c> be</c><00:03:16.020><c> eight</c><00:03:16.590><c> or</c><00:03:16.890><c> nine</c><00:03:17.400><c> lookups</c><00:03:17.790><c> if</c>

00:03:17.930 --> 00:03:17.940 align:start position:0%
average will be eight or nine lookups if
 

00:03:17.940 --> 00:03:20.210 align:start position:0%
average will be eight or nine lookups if
you<00:03:18.030><c> don't</c><00:03:18.239><c> go</c><00:03:18.450><c> through</c><00:03:18.720><c> from</c><00:03:19.019><c> the</c><00:03:19.110><c> root</c><00:03:19.230><c> so</c>

00:03:20.210 --> 00:03:20.220 align:start position:0%
you don't go through from the root so
 

00:03:20.220 --> 00:03:22.880 align:start position:0%
you don't go through from the root so
what<00:03:20.700><c> I</c><00:03:20.730><c> try</c><00:03:21.390><c> to</c><00:03:21.420><c> do</c><00:03:21.720><c> is</c><00:03:21.840><c> that</c><00:03:21.870><c> okay</c><00:03:22.440><c> let's</c><00:03:22.650><c> just</c>

00:03:22.880 --> 00:03:22.890 align:start position:0%
what I try to do is that okay let's just
 

00:03:22.890 --> 00:03:24.740 align:start position:0%
what I try to do is that okay let's just
put<00:03:23.190><c> them</c><00:03:23.370><c> in</c><00:03:23.489><c> a</c><00:03:23.519><c> database</c><00:03:23.850><c> as</c><00:03:24.120><c> I</c><00:03:24.450><c> would</c><00:03:24.630><c> expect</c>

00:03:24.740 --> 00:03:24.750 align:start position:0%
put them in a database as I would expect
 

00:03:24.750 --> 00:03:27.979 align:start position:0%
put them in a database as I would expect
it<00:03:25.230><c> to</c><00:03:25.260><c> be</c><00:03:25.430><c> like</c><00:03:26.430><c> you've</c><00:03:27.180><c> got</c><00:03:27.360><c> the</c><00:03:27.450><c> key</c><00:03:27.690><c> which</c>

00:03:27.979 --> 00:03:27.989 align:start position:0%
it to be like you've got the key which
 

00:03:27.989 --> 00:03:30.860 align:start position:0%
it to be like you've got the key which
is<00:03:28.170><c> the</c><00:03:28.549><c> which</c><00:03:29.549><c> is</c><00:03:29.700><c> the</c><00:03:29.850><c> actual</c><00:03:30.150><c> key</c><00:03:30.420><c> of</c><00:03:30.630><c> the</c>

00:03:30.860 --> 00:03:30.870 align:start position:0%
is the which is the actual key of the
 

00:03:30.870 --> 00:03:32.660 align:start position:0%
is the which is the actual key of the
value<00:03:31.170><c> that</c><00:03:31.290><c> you</c><00:03:31.440><c> want</c><00:03:31.620><c> to</c><00:03:31.709><c> store</c><00:03:31.950><c> and</c><00:03:32.160><c> the</c>

00:03:32.660 --> 00:03:32.670 align:start position:0%
value that you want to store and the
 

00:03:32.670 --> 00:03:34.220 align:start position:0%
value that you want to store and the
value<00:03:32.970><c> is</c><00:03:33.090><c> the</c><00:03:33.209><c> actual</c><00:03:33.360><c> value</c><00:03:33.690><c> that</c><00:03:33.959><c> you</c><00:03:34.049><c> want</c>

00:03:34.220 --> 00:03:34.230 align:start position:0%
value is the actual value that you want
 

00:03:34.230 --> 00:03:36.350 align:start position:0%
value is the actual value that you want
to<00:03:34.290><c> store</c><00:03:34.500><c> and</c><00:03:35.160><c> if</c><00:03:35.640><c> it's</c><00:03:35.910><c> a</c><00:03:36.030><c> history</c>

00:03:36.350 --> 00:03:36.360 align:start position:0%
to store and if it's a history
 

00:03:36.360 --> 00:03:37.940 align:start position:0%
to store and if it's a history
historical<00:03:36.840><c> value</c><00:03:37.110><c> then</c><00:03:37.230><c> we</c><00:03:37.380><c> can</c><00:03:37.410><c> we're</c><00:03:37.830><c> gonna</c>

00:03:37.940 --> 00:03:37.950 align:start position:0%
historical value then we can we're gonna
 

00:03:37.950 --> 00:03:41.870 align:start position:0%
historical value then we can we're gonna
append<00:03:38.730><c> some</c><00:03:39.150><c> kind</c><00:03:39.360><c> of</c><00:03:39.510><c> block</c><00:03:40.260><c> number</c><00:03:41.010><c> encoded</c>

00:03:41.870 --> 00:03:41.880 align:start position:0%
append some kind of block number encoded
 

00:03:41.880 --> 00:03:44.180 align:start position:0%
append some kind of block number encoded
in<00:03:42.000><c> some</c><00:03:42.239><c> way</c><00:03:42.540><c> to</c><00:03:42.600><c> the</c><00:03:42.959><c> key</c><00:03:43.200><c> just</c><00:03:43.920><c> for</c>

00:03:44.180 --> 00:03:44.190 align:start position:0%
in some way to the key just for
 

00:03:44.190 --> 00:03:49.220 align:start position:0%
in some way to the key just for
simplicity<00:03:44.970><c> and</c><00:03:45.620><c> the</c><00:03:47.269><c> the</c><00:03:48.269><c> main</c><00:03:48.600><c> problem</c><00:03:48.959><c> here</c>

00:03:49.220 --> 00:03:49.230 align:start position:0%
simplicity and the the main problem here
 

00:03:49.230 --> 00:03:51.199 align:start position:0%
simplicity and the the main problem here
is<00:03:49.290><c> that</c><00:03:49.350><c> how</c><00:03:49.799><c> we're</c><00:03:50.010><c> going</c><00:03:50.160><c> to</c><00:03:50.280><c> compute</c><00:03:51.090><c> the</c>

00:03:51.199 --> 00:03:51.209 align:start position:0%
is that how we're going to compute the
 

00:03:51.209 --> 00:03:52.940 align:start position:0%
is that how we're going to compute the
oracle<00:03:51.570><c> hash</c><00:03:51.720><c> of</c><00:03:51.900><c> that</c><00:03:52.049><c> and</c><00:03:52.260><c> i</c><00:03:52.709><c> think</c>

00:03:52.940 --> 00:03:52.950 align:start position:0%
oracle hash of that and i think
 

00:03:52.950 --> 00:03:55.759 align:start position:0%
oracle hash of that and i think
initially<00:03:53.400><c> when</c><00:03:53.760><c> the</c><00:03:54.570><c> first</c><00:03:55.230><c> clients</c><00:03:55.650><c> had</c>

00:03:55.759 --> 00:03:55.769 align:start position:0%
initially when the first clients had
 

00:03:55.769 --> 00:03:57.560 align:start position:0%
initially when the first clients had
been<00:03:55.890><c> produced</c><00:03:56.250><c> the</c><00:03:56.730><c> assumption</c><00:03:57.150><c> was</c><00:03:57.269><c> that</c><00:03:57.330><c> oh</c>

00:03:57.560 --> 00:03:57.570 align:start position:0%
been produced the assumption was that oh
 

00:03:57.570 --> 00:03:59.420 align:start position:0%
been produced the assumption was that oh
that's<00:03:57.810><c> going</c><00:03:58.019><c> to</c><00:03:58.080><c> be</c><00:03:58.200><c> super</c><00:03:58.560><c> expensive</c><00:03:58.830><c> to</c>

00:03:59.420 --> 00:03:59.430 align:start position:0%
that's going to be super expensive to
 

00:03:59.430 --> 00:04:01.640 align:start position:0%
that's going to be super expensive to
actually<00:04:00.269><c> have</c><00:04:00.450><c> this</c><00:04:00.570><c> flat</c><00:04:00.870><c> representation</c>

00:04:01.640 --> 00:04:01.650 align:start position:0%
actually have this flat representation
 

00:04:01.650 --> 00:04:03.350 align:start position:0%
actually have this flat representation
and<00:04:01.860><c> then</c><00:04:02.160><c> should</c><00:04:02.340><c> build</c><00:04:02.610><c> a</c><00:04:02.700><c> whole</c><00:04:02.850><c> tree</c><00:04:03.120><c> and</c>

00:04:03.350 --> 00:04:03.360 align:start position:0%
and then should build a whole tree and
 

00:04:03.360 --> 00:04:05.660 align:start position:0%
and then should build a whole tree and
then<00:04:04.049><c> everybody</c><00:04:04.650><c> decided</c><00:04:04.709><c> to</c><00:04:05.100><c> go</c><00:04:05.220><c> okay</c><00:04:05.489><c> let's</c>

00:04:05.660 --> 00:04:05.670 align:start position:0%
then everybody decided to go okay let's
 

00:04:05.670 --> 00:04:07.970 align:start position:0%
then everybody decided to go okay let's
do<00:04:05.880><c> the</c><00:04:06.030><c> list</c><00:04:06.570><c> blue</c><00:04:07.049><c> Patricia</c><00:04:07.470><c> tree</c><00:04:07.680><c> in</c><00:04:07.739><c> a</c>

00:04:07.970 --> 00:04:07.980 align:start position:0%
do the list blue Patricia tree in a
 

00:04:07.980 --> 00:04:09.680 align:start position:0%
do the list blue Patricia tree in a
database<00:04:08.250><c> but</c><00:04:08.970><c> then</c><00:04:09.120><c> I</c><00:04:09.180><c> said</c><00:04:09.239><c> well</c><00:04:09.510><c> why</c><00:04:09.660><c> not</c>

00:04:09.680 --> 00:04:09.690 align:start position:0%
database but then I said well why not
 

00:04:09.690 --> 00:04:11.449 align:start position:0%
database but then I said well why not
good<00:04:10.079><c> to</c><00:04:10.170><c> try</c><00:04:10.380><c> and</c><00:04:10.560><c> then</c><00:04:10.709><c> I</c><00:04:10.829><c> try</c><00:04:11.070><c> that</c><00:04:11.280><c> and</c>

00:04:11.449 --> 00:04:11.459 align:start position:0%
good to try and then I try that and
 

00:04:11.459 --> 00:04:13.910 align:start position:0%
good to try and then I try that and
actually<00:04:11.820><c> turned</c><00:04:12.180><c> out</c><00:04:12.390><c> that</c><00:04:12.570><c> you</c><00:04:12.780><c> can</c><00:04:13.530><c> do</c>

00:04:13.910 --> 00:04:13.920 align:start position:0%
actually turned out that you can do
 

00:04:13.920 --> 00:04:16.340 align:start position:0%
actually turned out that you can do
things<00:04:14.160><c> much</c><00:04:14.489><c> well</c><00:04:15.239><c> in</c><00:04:15.450><c> a</c><00:04:15.690><c> lot</c><00:04:15.780><c> of</c><00:04:15.840><c> cases</c><00:04:16.109><c> much</c>

00:04:16.340 --> 00:04:16.350 align:start position:0%
things much well in a lot of cases much
 

00:04:16.350 --> 00:04:18.830 align:start position:0%
things much well in a lot of cases much
faster<00:04:16.739><c> if</c><00:04:16.919><c> you</c><00:04:17.070><c> simply</c><00:04:17.489><c> rebuilt</c><00:04:17.850><c> the</c><00:04:18.090><c> the</c>

00:04:18.830 --> 00:04:18.840 align:start position:0%
faster if you simply rebuilt the the
 

00:04:18.840 --> 00:04:21.949 align:start position:0%
faster if you simply rebuilt the the
hash<00:04:19.079><c> tree</c><00:04:19.530><c> on</c><00:04:19.739><c> the</c><00:04:20.040><c> on</c><00:04:20.549><c> the</c><00:04:20.790><c> fly</c><00:04:21.000><c> and</c><00:04:21.510><c> you</c><00:04:21.570><c> use</c>

00:04:21.949 --> 00:04:21.959 align:start position:0%
hash tree on the on the fly and you use
 

00:04:21.959 --> 00:04:23.750 align:start position:0%
hash tree on the on the fly and you use
some<00:04:22.140><c> caching</c><00:04:22.440><c> and</c><00:04:22.680><c> stuff</c><00:04:22.860><c> like</c><00:04:22.950><c> this</c><00:04:23.010><c> so</c><00:04:23.520><c> the</c>

00:04:23.750 --> 00:04:23.760 align:start position:0%
some caching and stuff like this so the
 

00:04:23.760 --> 00:04:25.850 align:start position:0%
some caching and stuff like this so the
way<00:04:23.880><c> it</c><00:04:23.970><c> looks</c><00:04:24.150><c> like</c><00:04:24.330><c> in</c><00:04:24.870><c> imagine</c><00:04:25.590><c> that</c><00:04:25.740><c> we</c>

00:04:25.850 --> 00:04:25.860 align:start position:0%
way it looks like in imagine that we
 

00:04:25.860 --> 00:04:26.160 align:start position:0%
way it looks like in imagine that we
need<00:04:26.010><c> to</c>

00:04:26.160 --> 00:04:26.170 align:start position:0%
need to
 

00:04:26.170 --> 00:04:28.230 align:start position:0%
need to
[Music]

00:04:28.230 --> 00:04:28.240 align:start position:0%
[Music]
 

00:04:28.240 --> 00:04:34.060 align:start position:0%
[Music]
to<00:04:29.240><c> get</c><00:04:29.450><c> the</c><00:04:29.750><c> to</c><00:04:30.080><c> this</c><00:04:30.200><c> pink</c><00:04:30.860><c> diamond</c><00:04:31.490><c> now</c><00:04:33.070><c> with</c>

00:04:34.060 --> 00:04:34.070 align:start position:0%
to get the to this pink diamond now with
 

00:04:34.070 --> 00:04:35.860 align:start position:0%
to get the to this pink diamond now with
the<00:04:34.280><c> pink</c><00:04:34.460><c> then</c><00:04:34.639><c> we</c><00:04:34.669><c> just</c><00:04:34.940><c> we</c><00:04:35.450><c> just</c><00:04:35.480><c> simply</c>

00:04:35.860 --> 00:04:35.870 align:start position:0%
the pink then we just we just simply
 

00:04:35.870 --> 00:04:38.020 align:start position:0%
the pink then we just we just simply
fetch<00:04:36.050><c> it</c><00:04:36.200><c> but</c><00:04:36.590><c> actually</c><00:04:36.980><c> let's</c><00:04:37.340><c> meet</c><00:04:37.550><c> let's</c>

00:04:38.020 --> 00:04:38.030 align:start position:0%
fetch it but actually let's meet let's
 

00:04:38.030 --> 00:04:40.060 align:start position:0%
fetch it but actually let's meet let's
say<00:04:38.210><c> that</c><00:04:38.330><c> we</c><00:04:38.480><c> want</c><00:04:38.690><c> to</c><00:04:38.750><c> compute</c><00:04:39.050><c> the</c><00:04:39.169><c> hash</c><00:04:39.770><c> of</c>

00:04:40.060 --> 00:04:40.070 align:start position:0%
say that we want to compute the hash of
 

00:04:40.070 --> 00:04:43.659 align:start position:0%
say that we want to compute the hash of
that<00:04:40.160><c> the</c><00:04:40.790><c> oval</c><00:04:41.500><c> that</c><00:04:42.500><c> our</c><00:04:42.680><c> thing</c><00:04:42.980><c> so</c><00:04:43.460><c> in</c><00:04:43.550><c> this</c>

00:04:43.659 --> 00:04:43.669 align:start position:0%
that the oval that our thing so in this
 

00:04:43.669 --> 00:04:45.790 align:start position:0%
that the oval that our thing so in this
case<00:04:43.850><c> we</c><00:04:44.120><c> do</c><00:04:44.270><c> a</c><00:04:44.300><c> range</c><00:04:44.630><c> query</c><00:04:45.020><c> which</c><00:04:45.590><c> will</c>

00:04:45.790 --> 00:04:45.800 align:start position:0%
case we do a range query which will
 

00:04:45.800 --> 00:04:48.159 align:start position:0%
case we do a range query which will
fetch<00:04:45.980><c> us</c><00:04:46.160><c> all</c><00:04:46.370><c> the</c><00:04:46.520><c> keys</c><00:04:46.760><c> and</c><00:04:46.790><c> valleys</c><00:04:47.450><c> which</c>

00:04:48.159 --> 00:04:48.169 align:start position:0%
fetch us all the keys and valleys which
 

00:04:48.169 --> 00:04:50.440 align:start position:0%
fetch us all the keys and valleys which
starts<00:04:48.500><c> with</c><00:04:48.620><c> 1</c><00:04:48.830><c> which</c><00:04:49.070><c> is</c><00:04:49.220><c> the</c><00:04:49.450><c> actually</c>

00:04:50.440 --> 00:04:50.450 align:start position:0%
starts with 1 which is the actually
 

00:04:50.450 --> 00:04:51.970 align:start position:0%
starts with 1 which is the actually
might<00:04:50.600><c> be</c><00:04:50.720><c> maybe</c><00:04:51.050><c> the</c><00:04:51.410><c> pictures</c><00:04:51.740><c> might</c><00:04:51.860><c> be</c>

00:04:51.970 --> 00:04:51.980 align:start position:0%
might be maybe the pictures might be
 

00:04:51.980 --> 00:04:54.550 align:start position:0%
might be maybe the pictures might be
wrong<00:04:52.100><c> but</c><00:04:52.460><c> anyway</c><00:04:52.550><c> so</c><00:04:53.180><c> you</c><00:04:53.960><c> probably</c><00:04:54.260><c> get</c><00:04:54.440><c> the</c>

00:04:54.550 --> 00:04:54.560 align:start position:0%
wrong but anyway so you probably get the
 

00:04:54.560 --> 00:04:56.260 align:start position:0%
wrong but anyway so you probably get the
idea<00:04:54.590><c> so</c><00:04:54.919><c> we</c><00:04:55.160><c> get</c><00:04:55.310><c> the</c><00:04:55.460><c> range</c><00:04:55.669><c> of</c><00:04:55.850><c> keys</c><00:04:56.090><c> and</c>

00:04:56.260 --> 00:04:56.270 align:start position:0%
idea so we get the range of keys and
 

00:04:56.270 --> 00:04:59.110 align:start position:0%
idea so we get the range of keys and
valleys<00:04:56.630><c> and</c><00:04:56.810><c> then</c><00:04:57.139><c> we</c><00:04:57.500><c> apply</c><00:04:58.430><c> our</c><00:04:58.730><c> merkel</c>

00:04:59.110 --> 00:04:59.120 align:start position:0%
valleys and then we apply our merkel
 

00:04:59.120 --> 00:05:01.330 align:start position:0%
valleys and then we apply our merkel
ization<00:04:59.360><c> to</c><00:04:59.630><c> them</c><00:04:59.750><c> and</c><00:04:59.930><c> we</c><00:05:00.050><c> get</c><00:05:00.169><c> the</c><00:05:00.380><c> hash</c><00:05:00.740><c> the</c>

00:05:01.330 --> 00:05:01.340 align:start position:0%
ization to them and we get the hash the
 

00:05:01.340 --> 00:05:03.730 align:start position:0%
ization to them and we get the hash the
it<00:05:02.270><c> only</c><00:05:02.570><c> kind</c><00:05:02.750><c> of</c><00:05:02.810><c> works</c><00:05:03.020><c> for</c><00:05:03.229><c> this</c><00:05:03.290><c> for</c><00:05:03.650><c> the</c>

00:05:03.730 --> 00:05:03.740 align:start position:0%
it only kind of works for this for the
 

00:05:03.740 --> 00:05:07.450 align:start position:0%
it only kind of works for this for the
current<00:05:04.040><c> state</c><00:05:04.510><c> and</c><00:05:05.510><c> if</c><00:05:06.440><c> you</c><00:05:06.620><c> want</c><00:05:06.800><c> to</c><00:05:06.950><c> compute</c>

00:05:07.450 --> 00:05:07.460 align:start position:0%
current state and if you want to compute
 

00:05:07.460 --> 00:05:08.920 align:start position:0%
current state and if you want to compute
the<00:05:07.580><c> miracle</c><00:05:07.940><c> hashes</c><00:05:08.240><c> of</c><00:05:08.360><c> the</c><00:05:08.450><c> current</c><00:05:08.690><c> state</c>

00:05:08.920 --> 00:05:08.930 align:start position:0%
the miracle hashes of the current state
 

00:05:08.930 --> 00:05:11.740 align:start position:0%
the miracle hashes of the current state
but<00:05:09.470><c> for</c><00:05:09.650><c> historical</c><00:05:10.160><c> state</c><00:05:10.400><c> it's</c><00:05:10.700><c> it's</c><00:05:11.630><c> a</c>

00:05:11.740 --> 00:05:11.750 align:start position:0%
but for historical state it's it's a
 

00:05:11.750 --> 00:05:13.240 align:start position:0%
but for historical state it's it's a
kind<00:05:12.110><c> of</c><00:05:12.169><c> a</c><00:05:12.260><c> lot</c><00:05:12.410><c> of</c><00:05:12.530><c> work</c><00:05:12.680><c> because</c><00:05:12.979><c> you</c><00:05:13.070><c> don't</c>

00:05:13.240 --> 00:05:13.250 align:start position:0%
kind of a lot of work because you don't
 

00:05:13.250 --> 00:05:14.890 align:start position:0%
kind of a lot of work because you don't
usually<00:05:13.460><c> store</c><00:05:13.970><c> the</c><00:05:14.120><c> historical</c><00:05:14.600><c> state</c><00:05:14.780><c> in</c>

00:05:14.890 --> 00:05:14.900 align:start position:0%
usually store the historical state in
 

00:05:14.900 --> 00:05:17.980 align:start position:0%
usually store the historical state in
your<00:05:15.020><c> cache</c><00:05:15.260><c> but</c><00:05:15.919><c> it</c><00:05:16.910><c> works</c><00:05:17.300><c> reasonably</c><00:05:17.900><c> well</c>

00:05:17.980 --> 00:05:17.990 align:start position:0%
your cache but it works reasonably well
 

00:05:17.990 --> 00:05:20.860 align:start position:0%
your cache but it works reasonably well
for<00:05:18.200><c> for</c><00:05:19.190><c> the</c><00:05:19.340><c> RPC</c><00:05:19.850><c> queries</c><00:05:20.240><c> that</c><00:05:20.360><c> are</c><00:05:20.479><c> tested</c>

00:05:20.860 --> 00:05:20.870 align:start position:0%
for for the RPC queries that are tested
 

00:05:20.870 --> 00:05:24.190 align:start position:0%
for for the RPC queries that are tested
so<00:05:21.650><c> let's</c><00:05:21.830><c> go</c><00:05:22.130><c> so</c><00:05:22.460><c> so</c><00:05:23.120><c> as</c><00:05:23.389><c> I</c><00:05:23.570><c> mentioned</c><00:05:23.990><c> that</c><00:05:24.050><c> in</c>

00:05:24.190 --> 00:05:24.200 align:start position:0%
so let's go so so as I mentioned that in
 

00:05:24.200 --> 00:05:25.480 align:start position:0%
so let's go so so as I mentioned that in
fewer<00:05:24.440><c> has</c><00:05:24.590><c> been</c><00:05:24.770><c> supporting</c><00:05:25.250><c> this</c><00:05:25.310><c> project</c>

00:05:25.480 --> 00:05:25.490 align:start position:0%
fewer has been supporting this project
 

00:05:25.490 --> 00:05:27.909 align:start position:0%
fewer has been supporting this project
for<00:05:26.300><c> for</c><00:05:26.690><c> some</c><00:05:26.840><c> time</c><00:05:27.050><c> and</c><00:05:27.290><c> one</c><00:05:27.500><c> of</c><00:05:27.620><c> the</c><00:05:27.710><c> things</c>

00:05:27.909 --> 00:05:27.919 align:start position:0%
for for some time and one of the things
 

00:05:27.919 --> 00:05:30.100 align:start position:0%
for for some time and one of the things
we<00:05:28.160><c> did</c><00:05:28.310><c> is</c><00:05:28.460><c> that</c><00:05:28.639><c> instead</c><00:05:29.389><c> of</c><00:05:29.450><c> me</c><00:05:29.870><c> only</c>

00:05:30.100 --> 00:05:30.110 align:start position:0%
we did is that instead of me only
 

00:05:30.110 --> 00:05:32.200 align:start position:0%
we did is that instead of me only
running<00:05:30.380><c> the</c><00:05:30.800><c> surrogates</c><00:05:31.370><c> on</c><00:05:31.520><c> my</c><00:05:31.669><c> machines</c><00:05:32.030><c> or</c>

00:05:32.200 --> 00:05:32.210 align:start position:0%
running the surrogates on my machines or
 

00:05:32.210 --> 00:05:33.790 align:start position:0%
running the surrogates on my machines or
some<00:05:32.479><c> cloud</c><00:05:32.660><c> machines</c><00:05:33.020><c> they</c><00:05:33.169><c> try</c><00:05:33.350><c> to</c><00:05:33.410><c> run</c><00:05:33.680><c> it</c>

00:05:33.790 --> 00:05:33.800 align:start position:0%
some cloud machines they try to run it
 

00:05:33.800 --> 00:05:36.130 align:start position:0%
some cloud machines they try to run it
out<00:05:34.190><c> of</c><00:05:34.490><c> the</c><00:05:34.760><c> source</c><00:05:34.970><c> code</c><00:05:35.210><c> and</c><00:05:35.390><c> this</c><00:05:35.840><c> is</c><00:05:35.960><c> what</c>

00:05:36.130 --> 00:05:36.140 align:start position:0%
out of the source code and this is what
 

00:05:36.140 --> 00:05:38.620 align:start position:0%
out of the source code and this is what
happened<00:05:36.530><c> and</c><00:05:36.710><c> I</c><00:05:37.700><c> was</c><00:05:37.850><c> kind</c><00:05:38.090><c> of</c><00:05:38.120><c> pleasantly</c>

00:05:38.620 --> 00:05:38.630 align:start position:0%
happened and I was kind of pleasantly
 

00:05:38.630 --> 00:05:40.270 align:start position:0%
happened and I was kind of pleasantly
surprised<00:05:38.990><c> because</c><00:05:39.169><c> I</c><00:05:39.350><c> must</c><00:05:40.010><c> have</c><00:05:40.160><c> been</c>

00:05:40.270 --> 00:05:40.280 align:start position:0%
surprised because I must have been
 

00:05:40.280 --> 00:05:41.800 align:start position:0%
surprised because I must have been
running<00:05:40.430><c> it</c><00:05:40.729><c> on</c><00:05:40.820><c> a</c><00:05:40.850><c> really</c><00:05:41.120><c> bad</c><00:05:41.390><c> machines</c>

00:05:41.800 --> 00:05:41.810 align:start position:0%
running it on a really bad machines
 

00:05:41.810 --> 00:05:45.400 align:start position:0%
running it on a really bad machines
before<00:05:42.020><c> so</c><00:05:42.890><c> now</c><00:05:43.039><c> I</c><00:05:43.370><c> usually</c><00:05:43.760><c> got</c><00:05:44.120><c> two</c><00:05:45.050><c> weeks</c><00:05:45.260><c> to</c>

00:05:45.400 --> 00:05:45.410 align:start position:0%
before so now I usually got two weeks to
 

00:05:45.410 --> 00:05:47.529 align:start position:0%
before so now I usually got two weeks to
sync<00:05:45.650><c> it</c><00:05:45.770><c> but</c><00:05:45.979><c> this</c><00:05:46.400><c> was</c><00:05:46.640><c> actually</c><00:05:46.910><c> synced</c><00:05:47.419><c> in</c>

00:05:47.529 --> 00:05:47.539 align:start position:0%
sync it but this was actually synced in
 

00:05:47.539 --> 00:05:50.170 align:start position:0%
sync it but this was actually synced in
about<00:05:47.750><c> six</c><00:05:48.110><c> and</c><00:05:48.289><c> a</c><00:05:48.320><c> half</c><00:05:48.350><c> days</c><00:05:48.530><c> yeah</c><00:05:49.460><c> six</c><00:05:50.000><c> and</c><00:05:50.150><c> a</c>

00:05:50.170 --> 00:05:50.180 align:start position:0%
about six and a half days yeah six and a
 

00:05:50.180 --> 00:05:53.980 align:start position:0%
about six and a half days yeah six and a
half<00:05:50.210><c> days</c><00:05:50.300><c> and</c><00:05:50.870><c> the</c><00:05:51.800><c> this</c><00:05:52.070><c> -</c><00:05:52.760><c> the</c><00:05:53.090><c> pretty</c>

00:05:53.980 --> 00:05:53.990 align:start position:0%
half days and the this - the pretty
 

00:05:53.990 --> 00:05:57.010 align:start position:0%
half days and the this - the pretty
recent<00:05:54.380><c> block</c><00:05:54.590><c> and</c><00:05:55.039><c> the</c><00:05:55.729><c> it's</c><00:05:56.419><c> archive</c><00:05:56.810><c> node</c>

00:05:57.010 --> 00:05:57.020 align:start position:0%
recent block and the it's archive node
 

00:05:57.020 --> 00:05:59.409 align:start position:0%
recent block and the it's archive node
actually<00:05:57.410><c> so</c><00:05:57.560><c> it</c><00:05:57.680><c> has</c><00:05:57.830><c> a</c><00:05:57.860><c> full</c><00:05:58.419><c> unrolled</c>

00:05:59.409 --> 00:05:59.419 align:start position:0%
actually so it has a full unrolled
 

00:05:59.419 --> 00:06:02.770 align:start position:0%
actually so it has a full unrolled
history<00:05:59.780><c> and</c><00:06:00.380><c> it</c><00:06:00.500><c> only</c><00:06:00.620><c> was</c><00:06:01.430><c> what</c><00:06:01.880><c> two</c><00:06:02.389><c> hundred</c>

00:06:02.770 --> 00:06:02.780 align:start position:0%
history and it only was what two hundred
 

00:06:02.780 --> 00:06:05.200 align:start position:0%
history and it only was what two hundred
two<00:06:03.560><c> hundred</c><00:06:03.590><c> fifty</c><00:06:04.160><c> something</c><00:06:04.400><c> gigabytes</c>

00:06:05.200 --> 00:06:05.210 align:start position:0%
two hundred fifty something gigabytes
 

00:06:05.210 --> 00:06:07.690 align:start position:0%
two hundred fifty something gigabytes
which<00:06:06.139><c> was</c><00:06:06.350><c> cool</c><00:06:06.530><c> because</c><00:06:06.919><c> it</c><00:06:07.160><c> probably</c><00:06:07.340><c> six</c>

00:06:07.690 --> 00:06:07.700 align:start position:0%
which was cool because it probably six
 

00:06:07.700 --> 00:06:11.670 align:start position:0%
which was cool because it probably six
times<00:06:08.289><c> less</c><00:06:09.289><c> than</c><00:06:09.470><c> you</c><00:06:10.310><c> would</c><00:06:10.400><c> normally</c><00:06:10.789><c> get</c>

00:06:11.670 --> 00:06:11.680 align:start position:0%
times less than you would normally get
 

00:06:11.680 --> 00:06:14.290 align:start position:0%
times less than you would normally get
and<00:06:12.680><c> just</c><00:06:13.039><c> as</c><00:06:13.160><c> an</c><00:06:13.280><c> interesting</c><00:06:13.580><c> thing</c><00:06:14.000><c> that</c>

00:06:14.290 --> 00:06:14.300 align:start position:0%
and just as an interesting thing that
 

00:06:14.300 --> 00:06:16.719 align:start position:0%
and just as an interesting thing that
the<00:06:14.810><c> memory</c><00:06:15.139><c> profile</c><00:06:15.560><c> so</c><00:06:15.800><c> the</c><00:06:15.979><c> what</c><00:06:16.460><c> you</c><00:06:16.580><c> can</c>

00:06:16.719 --> 00:06:16.729 align:start position:0%
the memory profile so the what you can
 

00:06:16.729 --> 00:06:18.640 align:start position:0%
the memory profile so the what you can
see<00:06:16.910><c> here</c><00:06:17.150><c> is</c><00:06:17.210><c> that</c><00:06:17.240><c> the</c><00:06:17.720><c> yellow</c><00:06:18.050><c> oscillating</c>

00:06:18.640 --> 00:06:18.650 align:start position:0%
see here is that the yellow oscillating
 

00:06:18.650 --> 00:06:21.040 align:start position:0%
see here is that the yellow oscillating
bit<00:06:18.800><c> is</c><00:06:18.979><c> that</c><00:06:19.030><c> it's</c><00:06:20.030><c> obviously</c><00:06:20.479><c> go</c><00:06:20.720><c> it</c><00:06:20.900><c> has</c><00:06:21.020><c> a</c>

00:06:21.040 --> 00:06:21.050 align:start position:0%
bit is that it's obviously go it has a
 

00:06:21.050 --> 00:06:22.450 align:start position:0%
bit is that it's obviously go it has a
garbage<00:06:21.260><c> collection</c><00:06:21.800><c> and</c><00:06:21.860><c> that's</c><00:06:22.039><c> why</c><00:06:22.190><c> it's</c>

00:06:22.450 --> 00:06:22.460 align:start position:0%
garbage collection and that's why it's
 

00:06:22.460 --> 00:06:25.420 align:start position:0%
garbage collection and that's why it's
oscillating<00:06:23.060><c> so</c><00:06:23.240><c> much</c><00:06:23.389><c> that</c><00:06:23.979><c> it's</c><00:06:24.979><c> basically</c>

00:06:25.420 --> 00:06:25.430 align:start position:0%
oscillating so much that it's basically
 

00:06:25.430 --> 00:06:28.600 align:start position:0%
oscillating so much that it's basically
allocated<00:06:25.970><c> heap</c><00:06:26.180><c> which</c><00:06:26.630><c> goes</c><00:06:26.900><c> into</c><00:06:27.370><c> 13</c><00:06:28.370><c> gig</c>

00:06:28.600 --> 00:06:28.610 align:start position:0%
allocated heap which goes into 13 gig
 

00:06:28.610 --> 00:06:30.610 align:start position:0%
allocated heap which goes into 13 gig
maximum<00:06:29.090><c> and</c><00:06:29.270><c> you</c><00:06:29.300><c> can</c><00:06:29.810><c> see</c><00:06:29.960><c> the</c><00:06:30.080><c> spike</c><00:06:30.320><c> about</c>

00:06:30.610 --> 00:06:30.620 align:start position:0%
maximum and you can see the spike about
 

00:06:30.620 --> 00:06:33.070 align:start position:0%
maximum and you can see the spike about
the<00:06:30.830><c> the</c><00:06:31.250><c> spam</c><00:06:31.490><c> attacks</c><00:06:31.820><c> where</c><00:06:32.090><c> it</c><00:06:32.630><c> was</c><00:06:32.810><c> a</c><00:06:32.840><c> big</c>

00:06:33.070 --> 00:06:33.080 align:start position:0%
the the spam attacks where it was a big
 

00:06:33.080 --> 00:06:35.080 align:start position:0%
the the spam attacks where it was a big
load<00:06:33.289><c> and</c><00:06:33.530><c> the</c><00:06:33.919><c> green</c><00:06:34.130><c> bit</c><00:06:34.400><c> is</c><00:06:34.550><c> there</c><00:06:34.760><c> is</c><00:06:35.060><c> a</c>

00:06:35.080 --> 00:06:35.090 align:start position:0%
load and the green bit is there is a
 

00:06:35.090 --> 00:06:36.730 align:start position:0%
load and the green bit is there is a
number<00:06:35.330><c> of</c><00:06:35.539><c> nodes</c><00:06:35.690><c> so</c><00:06:35.930><c> what</c><00:06:36.140><c> Troopergate</c><00:06:36.530><c> does</c>

00:06:36.730 --> 00:06:36.740 align:start position:0%
number of nodes so what Troopergate does
 

00:06:36.740 --> 00:06:38.020 align:start position:0%
number of nodes so what Troopergate does
actually<00:06:36.979><c> one</c><00:06:37.430><c> of</c><00:06:37.460><c> the</c><00:06:37.610><c> things</c><00:06:37.789><c> it</c><00:06:37.909><c> does</c>

00:06:38.020 --> 00:06:38.030 align:start position:0%
actually one of the things it does
 

00:06:38.030 --> 00:06:40.370 align:start position:0%
actually one of the things it does
differently<00:06:38.450><c> as</c><00:06:38.570><c> well</c><00:06:38.780><c> is</c><00:06:39.169><c> that</c><00:06:39.650><c> you</c>

00:06:40.370 --> 00:06:40.380 align:start position:0%
differently as well is that you
 

00:06:40.380 --> 00:06:42.500 align:start position:0%
differently as well is that you
limit<00:06:40.680><c> number</c><00:06:40.830><c> of</c><00:06:40.980><c> nodes</c><00:06:41.220><c> at</c><00:06:41.430><c> use</c><00:06:41.730><c> of</c><00:06:41.760><c> the</c><00:06:42.360><c> of</c>

00:06:42.500 --> 00:06:42.510 align:start position:0%
limit number of nodes at use of the of
 

00:06:42.510 --> 00:06:44.090 align:start position:0%
limit number of nodes at use of the of
the<00:06:42.660><c> tree</c><00:06:42.840><c> you</c><00:06:42.960><c> can</c><00:06:43.110><c> store</c><00:06:43.380><c> in</c><00:06:43.500><c> a</c><00:06:43.590><c> cache</c><00:06:43.800><c> and</c>

00:06:44.090 --> 00:06:44.100 align:start position:0%
the tree you can store in a cache and
 

00:06:44.100 --> 00:06:46.820 align:start position:0%
the tree you can store in a cache and
that<00:06:44.550><c> might</c><00:06:45.360><c> allow</c><00:06:45.660><c> you</c><00:06:45.720><c> so</c><00:06:46.290><c> my</c><00:06:46.410><c> hope</c><00:06:46.590><c> was</c><00:06:46.770><c> that</c>

00:06:46.820 --> 00:06:46.830 align:start position:0%
that might allow you so my hope was that
 

00:06:46.830 --> 00:06:50.120 align:start position:0%
that might allow you so my hope was that
you<00:06:47.340><c> can</c><00:06:47.520><c> use</c><00:06:47.670><c> it</c><00:06:47.880><c> to</c><00:06:48.030><c> calibrate</c><00:06:48.420><c> the</c><00:06:48.800><c> the</c><00:06:49.800><c> heap</c>

00:06:50.120 --> 00:06:50.130 align:start position:0%
you can use it to calibrate the the heap
 

00:06:50.130 --> 00:06:52.310 align:start position:0%
you can use it to calibrate the the heap
space<00:06:50.400><c> but</c><00:06:50.640><c> you</c><00:06:51.120><c> know</c><00:06:51.240><c> I</c><00:06:51.270><c> think</c><00:06:51.420><c> it</c><00:06:52.140><c> might</c>

00:06:52.310 --> 00:06:52.320 align:start position:0%
space but you know I think it might
 

00:06:52.320 --> 00:06:54.260 align:start position:0%
space but you know I think it might
still<00:06:52.560><c> be</c><00:06:52.590><c> considered</c><00:06:53.460><c> constantly</c>

00:06:54.260 --> 00:06:54.270 align:start position:0%
still be considered constantly
 

00:06:54.270 --> 00:06:56.960 align:start position:0%
still be considered constantly
increasing<00:06:54.780><c> so</c><00:06:55.560><c> now</c><00:06:55.830><c> what</c><00:06:56.010><c> I</c><00:06:56.040><c> so</c><00:06:56.520><c> now</c><00:06:56.700><c> look</c><00:06:56.850><c> at</c>

00:06:56.960 --> 00:06:56.970 align:start position:0%
increasing so now what I so now look at
 

00:06:56.970 --> 00:07:00.140 align:start position:0%
increasing so now what I so now look at
the<00:06:57.150><c> these</c><00:06:57.660><c> graph</c><00:06:58.530><c> so</c><00:06:59.130><c> what</c><00:06:59.520><c> you</c><00:06:59.640><c> can</c><00:06:59.790><c> see</c><00:06:59.910><c> this</c>

00:07:00.140 --> 00:07:00.150 align:start position:0%
the these graph so what you can see this
 

00:07:00.150 --> 00:07:03.290 align:start position:0%
the these graph so what you can see this
is<00:07:00.300><c> the</c><00:07:00.530><c> recent</c><00:07:01.530><c> well</c><00:07:02.070><c> quite</c><00:07:02.370><c> recent</c><00:07:02.760><c> maybe</c>

00:07:03.290 --> 00:07:03.300 align:start position:0%
is the recent well quite recent maybe
 

00:07:03.300 --> 00:07:06.920 align:start position:0%
is the recent well quite recent maybe
one<00:07:03.510><c> month</c><00:07:03.630><c> old</c><00:07:04.130><c> graph</c><00:07:05.130><c> and</c><00:07:05.910><c> this</c><00:07:06.600><c> is</c><00:07:06.720><c> where</c>

00:07:06.920 --> 00:07:06.930 align:start position:0%
one month old graph and this is where
 

00:07:06.930 --> 00:07:08.630 align:start position:0%
one month old graph and this is where
the<00:07:07.110><c> they</c><00:07:07.320><c> actually</c><00:07:07.650><c> the</c><00:07:07.890><c> cost</c><00:07:08.160><c> of</c><00:07:08.370><c> storage</c>

00:07:08.630 --> 00:07:08.640 align:start position:0%
the they actually the cost of storage
 

00:07:08.640 --> 00:07:11.030 align:start position:0%
the they actually the cost of storage
comes<00:07:08.910><c> from</c><00:07:09.120><c> most</c><00:07:09.690><c> of</c><00:07:09.870><c> it</c><00:07:09.990><c> is</c><00:07:10.170><c> now</c><00:07:10.320><c> blog</c><00:07:10.710><c> bodies</c>

00:07:11.030 --> 00:07:11.040 align:start position:0%
comes from most of it is now blog bodies
 

00:07:11.040 --> 00:07:13.220 align:start position:0%
comes from most of it is now blog bodies
which<00:07:11.370><c> is</c><00:07:11.550><c> the</c><00:07:11.760><c> essentially</c><00:07:12.600><c> this</c><00:07:12.750><c> is</c><00:07:12.810><c> all</c><00:07:13.080><c> the</c>

00:07:13.220 --> 00:07:13.230 align:start position:0%
which is the essentially this is all the
 

00:07:13.230 --> 00:07:15.140 align:start position:0%
which is the essentially this is all the
blocks<00:07:13.440><c> combined</c><00:07:13.980><c> for</c><00:07:14.490><c> like</c><00:07:14.670><c> six</c><00:07:14.940><c> million</c>

00:07:15.140 --> 00:07:15.150 align:start position:0%
blocks combined for like six million
 

00:07:15.150 --> 00:07:17.690 align:start position:0%
blocks combined for like six million
books<00:07:15.510><c> and</c><00:07:15.720><c> then</c><00:07:16.470><c> the</c><00:07:16.650><c> the</c><00:07:16.920><c> second</c><00:07:17.370><c> biggest</c>

00:07:17.690 --> 00:07:17.700 align:start position:0%
books and then the the second biggest
 

00:07:17.700 --> 00:07:20.000 align:start position:0%
books and then the the second biggest
structure<00:07:18.480><c> is</c><00:07:18.600><c> the</c><00:07:18.750><c> code</c><00:07:18.930><c> block</c><00:07:19.260><c> this</c><00:07:19.680><c> is</c><00:07:19.740><c> like</c>

00:07:20.000 --> 00:07:20.010 align:start position:0%
structure is the code block this is like
 

00:07:20.010 --> 00:07:22.520 align:start position:0%
structure is the code block this is like
a<00:07:20.040><c> gray</c><00:07:20.340><c> one</c><00:07:20.550><c> block</c><00:07:21.210><c> number</c><00:07:21.630><c> two</c><00:07:21.930><c> changed</c><00:07:22.320><c> keys</c>

00:07:22.520 --> 00:07:22.530 align:start position:0%
a gray one block number two changed keys
 

00:07:22.530 --> 00:07:24.080 align:start position:0%
a gray one block number two changed keys
this<00:07:22.950><c> is</c><00:07:23.010><c> the</c><00:07:23.220><c> structure</c><00:07:23.460><c> which</c><00:07:23.760><c> is</c><00:07:23.940><c> a</c>

00:07:24.080 --> 00:07:24.090 align:start position:0%
this is the structure which is a
 

00:07:24.090 --> 00:07:26.060 align:start position:0%
this is the structure which is a
specific<00:07:25.020><c> to</c><00:07:25.140><c> through</c><00:07:25.320><c> bagasse</c><00:07:25.620><c> and</c><00:07:25.830><c> it</c>

00:07:26.060 --> 00:07:26.070 align:start position:0%
specific to through bagasse and it
 

00:07:26.070 --> 00:07:29.270 align:start position:0%
specific to through bagasse and it
allows<00:07:26.370><c> it</c><00:07:26.640><c> to</c><00:07:26.930><c> to</c><00:07:27.930><c> know</c><00:07:28.080><c> which</c><00:07:28.350><c> accounts</c><00:07:29.160><c> and</c>

00:07:29.270 --> 00:07:29.280 align:start position:0%
allows it to to know which accounts and
 

00:07:29.280 --> 00:07:31.550 align:start position:0%
allows it to to know which accounts and
which<00:07:29.400><c> storage</c><00:07:29.700><c> indices</c><00:07:30.390><c> changed</c><00:07:31.260><c> at</c><00:07:31.380><c> which</c>

00:07:31.550 --> 00:07:31.560 align:start position:0%
which storage indices changed at which
 

00:07:31.560 --> 00:07:34.310 align:start position:0%
which storage indices changed at which
block<00:07:31.860><c> and</c><00:07:32.160><c> why</c><00:07:32.940><c> do</c><00:07:33.330><c> we</c><00:07:33.450><c> need</c><00:07:33.570><c> this</c><00:07:33.780><c> is</c><00:07:33.990><c> because</c>

00:07:34.310 --> 00:07:34.320 align:start position:0%
block and why do we need this is because
 

00:07:34.320 --> 00:07:37.400 align:start position:0%
block and why do we need this is because
it<00:07:34.440><c> allows</c><00:07:34.890><c> us</c><00:07:34.920><c> to</c><00:07:35.100><c> do</c><00:07:35.630><c> to</c><00:07:36.630><c> rewind</c><00:07:37.020><c> the</c><00:07:37.200><c> state</c>

00:07:37.400 --> 00:07:37.410 align:start position:0%
it allows us to do to rewind the state
 

00:07:37.410 --> 00:07:40.190 align:start position:0%
it allows us to do to rewind the state
quickly<00:07:37.860><c> so</c><00:07:38.430><c> in</c><00:07:38.850><c> a</c><00:07:38.940><c> situation</c><00:07:39.090><c> where</c><00:07:39.630><c> let's</c>

00:07:40.190 --> 00:07:40.200 align:start position:0%
quickly so in a situation where let's
 

00:07:40.200 --> 00:07:42.290 align:start position:0%
quickly so in a situation where let's
say<00:07:40.380><c> that</c><00:07:40.620><c> we've</c><00:07:40.800><c> been</c><00:07:40.980><c> like</c><00:07:41.700><c> sinking</c><00:07:42.150><c> to</c><00:07:42.270><c> the</c>

00:07:42.290 --> 00:07:42.300 align:start position:0%
say that we've been like sinking to the
 

00:07:42.300 --> 00:07:44.630 align:start position:0%
say that we've been like sinking to the
main<00:07:42.660><c> chain</c><00:07:42.990><c> and</c><00:07:43.320><c> then</c><00:07:43.560><c> we</c><00:07:44.070><c> suddenly</c><00:07:44.250><c> see</c>

00:07:44.630 --> 00:07:44.640 align:start position:0%
main chain and then we suddenly see
 

00:07:44.640 --> 00:07:47.240 align:start position:0%
main chain and then we suddenly see
rework<00:07:45.000><c> of</c><00:07:45.180><c> like</c><00:07:45.450><c> four</c><00:07:45.930><c> blocks</c><00:07:46.200><c> so</c><00:07:46.860><c> what</c><00:07:47.100><c> the</c>

00:07:47.240 --> 00:07:47.250 align:start position:0%
rework of like four blocks so what the
 

00:07:47.250 --> 00:07:48.830 align:start position:0%
rework of like four blocks so what the
to<00:07:47.400><c> Poquette</c><00:07:47.640><c> does</c><00:07:47.850><c> it</c><00:07:48.030><c> actually</c><00:07:48.450><c> it</c><00:07:48.540><c> looks</c><00:07:48.690><c> at</c>

00:07:48.830 --> 00:07:48.840 align:start position:0%
to Poquette does it actually it looks at
 

00:07:48.840 --> 00:07:51.350 align:start position:0%
to Poquette does it actually it looks at
this<00:07:49.130><c> mapping</c><00:07:50.130><c> and</c><00:07:50.280><c> figures</c><00:07:50.610><c> out</c><00:07:50.730><c> which</c><00:07:50.910><c> keys</c>

00:07:51.350 --> 00:07:51.360 align:start position:0%
this mapping and figures out which keys
 

00:07:51.360 --> 00:07:53.990 align:start position:0%
this mapping and figures out which keys
changed<00:07:51.750><c> in</c><00:07:51.900><c> this</c><00:07:52.050><c> four</c><00:07:52.260><c> blocks</c><00:07:52.670><c> then</c><00:07:53.670><c> picks</c>

00:07:53.990 --> 00:07:54.000 align:start position:0%
changed in this four blocks then picks
 

00:07:54.000 --> 00:07:55.700 align:start position:0%
changed in this four blocks then picks
up<00:07:54.150><c> the</c><00:07:54.210><c> values</c><00:07:54.690><c> which</c><00:07:54.900><c> were</c><00:07:55.110><c> before</c><00:07:55.560><c> these</c>

00:07:55.700 --> 00:07:55.710 align:start position:0%
up the values which were before these
 

00:07:55.710 --> 00:07:58.400 align:start position:0%
up the values which were before these
four<00:07:55.920><c> blocks</c><00:07:56.100><c> and</c><00:07:56.370><c> then</c><00:07:56.940><c> unwinds</c><00:07:57.840><c> the</c><00:07:57.900><c> the</c>

00:07:58.400 --> 00:07:58.410 align:start position:0%
four blocks and then unwinds the the
 

00:07:58.410 --> 00:08:00.140 align:start position:0%
four blocks and then unwinds the the
tree<00:07:58.620><c> in</c><00:07:58.800><c> the</c><00:07:58.860><c> hash</c><00:07:59.070><c> and</c><00:07:59.250><c> then</c><00:07:59.370><c> computes</c><00:07:59.730><c> a</c><00:07:59.820><c> new</c>

00:08:00.140 --> 00:08:00.150 align:start position:0%
tree in the hash and then computes a new
 

00:08:00.150 --> 00:08:02.480 align:start position:0%
tree in the hash and then computes a new
hash<00:08:00.300><c> and</c><00:08:00.510><c> then</c><00:08:00.960><c> reapply</c><00:08:01.320><c> is</c><00:08:01.470><c> the</c><00:08:01.710><c> the</c><00:08:02.040><c> state</c>

00:08:02.480 --> 00:08:02.490 align:start position:0%
hash and then reapply is the the state
 

00:08:02.490 --> 00:08:05.060 align:start position:0%
hash and then reapply is the the state
on<00:08:02.610><c> a</c><00:08:02.640><c> on</c><00:08:02.910><c> a</c><00:08:02.970><c> fork</c><00:08:03.300><c> on</c><00:08:03.510><c> and</c><00:08:03.840><c> out</c><00:08:03.960><c> of</c><00:08:04.110><c> work</c><00:08:04.260><c> and</c><00:08:04.560><c> so</c>

00:08:05.060 --> 00:08:05.070 align:start position:0%
on a on a fork on and out of work and so
 

00:08:05.070 --> 00:08:07.760 align:start position:0%
on a on a fork on and out of work and so
what<00:08:05.760><c> you</c><00:08:05.910><c> do</c><00:08:06.000><c> not</c><00:08:06.120><c> see</c><00:08:06.180><c> here</c><00:08:06.720><c> is</c><00:08:06.900><c> is</c><00:08:07.320><c> the</c>

00:08:07.760 --> 00:08:07.770 align:start position:0%
what you do not see here is is the
 

00:08:07.770 --> 00:08:10.550 align:start position:0%
what you do not see here is is the
receipts<00:08:08.130><c> you</c><00:08:08.670><c> can</c><00:08:08.820><c> have</c><00:08:09.030><c> them</c><00:08:09.240><c> there</c><00:08:09.560><c> they</c>

00:08:10.550 --> 00:08:10.560 align:start position:0%
receipts you can have them there they
 

00:08:10.560 --> 00:08:13.250 align:start position:0%
receipts you can have them there they
would<00:08:10.710><c> take</c><00:08:11.100><c> about</c><00:08:11.310><c> six</c><00:08:11.790><c> 70</c><00:08:12.360><c> to</c><00:08:12.480><c> 80</c><00:08:12.720><c> gigabytes</c>

00:08:13.250 --> 00:08:13.260 align:start position:0%
would take about six 70 to 80 gigabytes
 

00:08:13.260 --> 00:08:16.190 align:start position:0%
would take about six 70 to 80 gigabytes
of<00:08:13.530><c> all</c><00:08:13.920><c> receipts</c><00:08:14.250><c> from</c><00:08:14.460><c> the</c><00:08:14.580><c> beginning</c><00:08:15.060><c> and</c><00:08:15.300><c> I</c>

00:08:16.190 --> 00:08:16.200 align:start position:0%
of all receipts from the beginning and I
 

00:08:16.200 --> 00:08:17.930 align:start position:0%
of all receipts from the beginning and I
will<00:08:16.530><c> show</c><00:08:16.800><c> you</c><00:08:16.830><c> later</c><00:08:17.070><c> why</c><00:08:17.430><c> would</c><00:08:17.640><c> one</c><00:08:17.790><c> you</c>

00:08:17.930 --> 00:08:17.940 align:start position:0%
will show you later why would one you
 

00:08:17.940 --> 00:08:20.630 align:start position:0%
will show you later why would one you
want<00:08:18.120><c> to</c><00:08:18.240><c> do</c><00:08:18.360><c> that</c><00:08:18.620><c> but</c><00:08:19.620><c> the</c><00:08:20.100><c> interesting</c><00:08:20.460><c> bit</c>

00:08:20.630 --> 00:08:20.640 align:start position:0%
want to do that but the interesting bit
 

00:08:20.640 --> 00:08:22.250 align:start position:0%
want to do that but the interesting bit
to<00:08:20.730><c> note</c><00:08:20.910><c> is</c><00:08:21.060><c> that</c><00:08:21.090><c> lots</c><00:08:21.720><c> of</c><00:08:21.810><c> people</c><00:08:22.140><c> are</c>

00:08:22.250 --> 00:08:22.260 align:start position:0%
to note is that lots of people are
 

00:08:22.260 --> 00:08:24.470 align:start position:0%
to note is that lots of people are
confused<00:08:22.680><c> about</c><00:08:22.800><c> the</c><00:08:23.610><c> size</c><00:08:23.820><c> of</c><00:08:23.940><c> the</c><00:08:24.060><c> state</c><00:08:24.270><c> in</c>

00:08:24.470 --> 00:08:24.480 align:start position:0%
confused about the size of the state in
 

00:08:24.480 --> 00:08:26.540 align:start position:0%
confused about the size of the state in
the<00:08:24.570><c> theorem</c><00:08:24.900><c> and</c><00:08:25.080><c> in</c><00:08:26.040><c> the</c><00:08:26.160><c> reason</c><00:08:26.400><c> why</c>

00:08:26.540 --> 00:08:26.550 align:start position:0%
the theorem and in the reason why
 

00:08:26.550 --> 00:08:28.160 align:start position:0%
the theorem and in the reason why
they're<00:08:26.730><c> confused</c><00:08:27.120><c> is</c><00:08:27.210><c> because</c><00:08:27.510><c> different</c>

00:08:28.160 --> 00:08:28.170 align:start position:0%
they're confused is because different
 

00:08:28.170 --> 00:08:29.930 align:start position:0%
they're confused is because different
clients<00:08:28.680><c> toward</c><00:08:28.920><c> the</c><00:08:29.190><c> state</c><00:08:29.400><c> differently</c>

00:08:29.930 --> 00:08:29.940 align:start position:0%
clients toward the state differently
 

00:08:29.940 --> 00:08:32.930 align:start position:0%
clients toward the state differently
like<00:08:30.600><c> like</c><00:08:31.380><c> for</c><00:08:31.590><c> example</c><00:08:31.680><c> go</c><00:08:32.460><c> is</c><00:08:32.610><c> theorem</c>

00:08:32.930 --> 00:08:32.940 align:start position:0%
like like for example go is theorem
 

00:08:32.940 --> 00:08:35.839 align:start position:0%
like like for example go is theorem
current<00:08:33.660><c> state</c><00:08:34.160><c> representation</c><00:08:35.160><c> goes</c><00:08:35.640><c> here</c>

00:08:35.839 --> 00:08:35.849 align:start position:0%
current state representation goes here
 

00:08:35.849 --> 00:08:38.510 align:start position:0%
current state representation goes here
probably<00:08:36.240><c> like</c><00:08:36.479><c> 80</c><00:08:36.750><c> gigabytes</c><00:08:37.289><c> 92</c><00:08:37.830><c> bytes</c><00:08:38.070><c> in</c>

00:08:38.510 --> 00:08:38.520 align:start position:0%
probably like 80 gigabytes 92 bytes in
 

00:08:38.520 --> 00:08:39.860 align:start position:0%
probably like 80 gigabytes 92 bytes in
through<00:08:38.820><c> bagasse</c><00:08:39.120><c> is</c><00:08:39.270><c> probably</c><00:08:39.539><c> going</c><00:08:39.719><c> to</c><00:08:39.780><c> be</c>

00:08:39.860 --> 00:08:39.870 align:start position:0%
through bagasse is probably going to be
 

00:08:39.870 --> 00:08:42.830 align:start position:0%
through bagasse is probably going to be
about<00:08:40.050><c> 12</c><00:08:40.950><c> gigabytes</c><00:08:41.460><c> I</c><00:08:41.760><c> don't</c><00:08:42.300><c> know</c><00:08:42.419><c> how</c><00:08:42.660><c> it's</c>

00:08:42.830 --> 00:08:42.840 align:start position:0%
about 12 gigabytes I don't know how it's
 

00:08:42.840 --> 00:08:44.590 align:start position:0%
about 12 gigabytes I don't know how it's
going<00:08:42.990><c> to</c><00:08:43.050><c> be</c><00:08:43.140><c> in</c><00:08:43.200><c> parity</c><00:08:43.560><c> but</c><00:08:43.710><c> it's</c><00:08:44.130><c> a</c>

00:08:44.590 --> 00:08:44.600 align:start position:0%
going to be in parity but it's a
 

00:08:44.600 --> 00:08:46.940 align:start position:0%
going to be in parity but it's a
different<00:08:45.600><c> client</c><00:08:45.900><c> store</c><00:08:46.110><c> differently</c><00:08:46.740><c> and</c>

00:08:46.940 --> 00:08:46.950 align:start position:0%
different client store differently and
 

00:08:46.950 --> 00:08:49.010 align:start position:0%
different client store differently and
sometimes<00:08:47.850><c> people</c><00:08:48.030><c> confuse</c><00:08:48.360><c> the</c><00:08:48.600><c> current</c>

00:08:49.010 --> 00:08:49.020 align:start position:0%
sometimes people confuse the current
 

00:08:49.020 --> 00:08:51.380 align:start position:0%
sometimes people confuse the current
state<00:08:49.200><c> with</c><00:08:49.380><c> the</c><00:08:49.589><c> like</c><00:08:50.100><c> total</c><00:08:50.850><c> historical</c>

00:08:51.380 --> 00:08:51.390 align:start position:0%
state with the like total historical
 

00:08:51.390 --> 00:08:53.060 align:start position:0%
state with the like total historical
state<00:08:51.630><c> with</c><00:08:51.900><c> the</c><00:08:51.990><c> prune</c><00:08:52.230><c> historical</c><00:08:52.860><c> state</c>

00:08:53.060 --> 00:08:53.070 align:start position:0%
state with the prune historical state
 

00:08:53.070 --> 00:08:53.780 align:start position:0%
state with the prune historical state
that's<00:08:53.490><c> why</c>

00:08:53.780 --> 00:08:53.790 align:start position:0%
that's why
 

00:08:53.790 --> 00:08:55.340 align:start position:0%
that's why
is<00:08:53.970><c> but</c><00:08:54.480><c> what</c><00:08:54.660><c> you</c><00:08:54.690><c> can</c><00:08:54.900><c> see</c><00:08:55.050><c> from</c><00:08:55.230><c> this</c>

00:08:55.340 --> 00:08:55.350 align:start position:0%
is but what you can see from this
 

00:08:55.350 --> 00:08:57.800 align:start position:0%
is but what you can see from this
picture<00:08:55.530><c> on</c><00:08:56.190><c> the</c><00:08:56.580><c> very</c><00:08:56.760><c> top</c><00:08:57.300><c> you</c><00:08:57.510><c> can</c><00:08:57.660><c> see</c>

00:08:57.800 --> 00:08:57.810 align:start position:0%
picture on the very top you can see
 

00:08:57.810 --> 00:09:01.460 align:start position:0%
picture on the very top you can see
accounts<00:08:58.230><c> which</c><00:08:58.410><c> is</c><00:08:59.000><c> 3.89</c><00:09:00.000><c> gigabytes</c><00:09:00.570><c> this</c><00:09:01.200><c> is</c>

00:09:01.460 --> 00:09:01.470 align:start position:0%
accounts which is 3.89 gigabytes this is
 

00:09:01.470 --> 00:09:05.150 align:start position:0%
accounts which is 3.89 gigabytes this is
the<00:09:01.830><c> account</c><00:09:02.190><c> without</c><00:09:03.060><c> any</c><00:09:03.630><c> storage</c><00:09:04.320><c> items</c><00:09:04.500><c> is</c>

00:09:05.150 --> 00:09:05.160 align:start position:0%
the account without any storage items is
 

00:09:05.160 --> 00:09:08.750 align:start position:0%
the account without any storage items is
just<00:09:05.400><c> simply</c><00:09:05.580><c> balances</c><00:09:06.120><c> nonces</c><00:09:07.610><c> hashes</c><00:09:08.610><c> of</c>

00:09:08.750 --> 00:09:08.760 align:start position:0%
just simply balances nonces hashes of
 

00:09:08.760 --> 00:09:11.060 align:start position:0%
just simply balances nonces hashes of
the<00:09:08.880><c> of</c><00:09:09.090><c> the</c><00:09:09.300><c> of</c><00:09:09.480><c> the</c><00:09:09.660><c> storage</c><00:09:10.290><c> roots</c><00:09:10.560><c> and</c><00:09:10.800><c> the</c>

00:09:11.060 --> 00:09:11.070 align:start position:0%
the of the of the storage roots and the
 

00:09:11.070 --> 00:09:13.640 align:start position:0%
the of the of the storage roots and the
code<00:09:11.550><c> hashes</c><00:09:11.970><c> and</c><00:09:12.060><c> the</c><00:09:12.780><c> whole</c><00:09:12.960><c> no</c><00:09:13.350><c> it's</c><00:09:13.530><c> not</c>

00:09:13.640 --> 00:09:13.650 align:start position:0%
code hashes and the whole no it's not
 

00:09:13.650 --> 00:09:14.660 align:start position:0%
code hashes and the whole no it's not
the<00:09:13.740><c> whole</c><00:09:13.890><c> history</c><00:09:14.160><c> is</c><00:09:14.250><c> the</c><00:09:14.400><c> current</c>

00:09:14.660 --> 00:09:14.670 align:start position:0%
the whole history is the current
 

00:09:14.670 --> 00:09:16.520 align:start position:0%
the whole history is the current
accounts<00:09:15.000><c> so</c><00:09:15.540><c> the</c><00:09:15.660><c> history</c><00:09:15.930><c> of</c><00:09:16.110><c> accounts</c><00:09:16.470><c> you</c>

00:09:16.520 --> 00:09:16.530 align:start position:0%
accounts so the history of accounts you
 

00:09:16.530 --> 00:09:18.980 align:start position:0%
accounts so the history of accounts you
can<00:09:16.650><c> see</c><00:09:16.890><c> on</c><00:09:17.070><c> the</c><00:09:17.190><c> left</c><00:09:17.430><c> on</c><00:09:17.760><c> a</c><00:09:17.790><c> yellow</c><00:09:18.060><c> bit</c><00:09:18.390><c> so</c>

00:09:18.980 --> 00:09:18.990 align:start position:0%
can see on the left on a yellow bit so
 

00:09:18.990 --> 00:09:21.950 align:start position:0%
can see on the left on a yellow bit so
forty<00:09:19.290><c> four</c><00:09:19.470><c> gigabytes</c><00:09:19.890><c> then</c><00:09:20.520><c> the</c><00:09:20.880><c> storage</c><00:09:21.870><c> of</c>

00:09:21.950 --> 00:09:21.960 align:start position:0%
forty four gigabytes then the storage of
 

00:09:21.960 --> 00:09:23.300 align:start position:0%
forty four gigabytes then the storage of
the<00:09:22.020><c> contracts</c><00:09:22.560><c> the</c><00:09:22.800><c> current</c><00:09:23.100><c> the</c><00:09:23.280><c> current</c>

00:09:23.300 --> 00:09:23.310 align:start position:0%
the contracts the current the current
 

00:09:23.310 --> 00:09:26.360 align:start position:0%
the contracts the current the current
state<00:09:24.090><c> is</c><00:09:24.300><c> what</c><00:09:24.660><c> ten</c><00:09:25.020><c> gigabytes</c><00:09:25.470><c> you</c><00:09:26.040><c> can</c><00:09:26.220><c> see</c>

00:09:26.360 --> 00:09:26.370 align:start position:0%
state is what ten gigabytes you can see
 

00:09:26.370 --> 00:09:27.770 align:start position:0%
state is what ten gigabytes you can see
it<00:09:26.430><c> somewhere</c><00:09:26.760><c> down</c><00:09:27.330><c> the</c><00:09:27.450><c> middle</c>

00:09:27.770 --> 00:09:27.780 align:start position:0%
it somewhere down the middle
 

00:09:27.780 --> 00:09:31.340 align:start position:0%
it somewhere down the middle
the<00:09:28.080><c> purple</c><00:09:28.470><c> my</c><00:09:29.360><c> violet</c><00:09:30.360><c> bit</c><00:09:30.570><c> and</c><00:09:30.750><c> then</c><00:09:31.260><c> you</c>

00:09:31.340 --> 00:09:31.350 align:start position:0%
the purple my violet bit and then you
 

00:09:31.350 --> 00:09:33.350 align:start position:0%
the purple my violet bit and then you
can<00:09:31.380><c> see</c><00:09:31.650><c> the</c><00:09:31.740><c> history</c><00:09:31.890><c> of</c><00:09:32.130><c> its</c><00:09:32.430><c> it's</c><00:09:32.700><c> about</c><00:09:32.910><c> 20</c>

00:09:33.350 --> 00:09:33.360 align:start position:0%
can see the history of its it's about 20
 

00:09:33.360 --> 00:09:35.270 align:start position:0%
can see the history of its it's about 20
or<00:09:33.450><c> 60</c><00:09:33.750><c> gigabytes</c><00:09:34.020><c> so</c><00:09:34.530><c> you</c><00:09:34.620><c> can</c><00:09:34.890><c> see</c><00:09:35.070><c> that</c><00:09:35.220><c> the</c>

00:09:35.270 --> 00:09:35.280 align:start position:0%
or 60 gigabytes so you can see that the
 

00:09:35.280 --> 00:09:36.680 align:start position:0%
or 60 gigabytes so you can see that the
current<00:09:35.550><c> state</c><00:09:35.760><c> is</c><00:09:35.880><c> still</c><00:09:36.120><c> kind</c><00:09:36.360><c> of</c><00:09:36.450><c> about</c>

00:09:36.680 --> 00:09:36.690 align:start position:0%
current state is still kind of about
 

00:09:36.690 --> 00:09:41.480 align:start position:0%
current state is still kind of about
twelve<00:09:37.080><c> gigabytes</c><00:09:37.500><c> probably</c><00:09:38.270><c> now</c><00:09:39.980><c> so</c><00:09:40.980><c> this</c><00:09:41.370><c> is</c>

00:09:41.480 --> 00:09:41.490 align:start position:0%
twelve gigabytes probably now so this is
 

00:09:41.490 --> 00:09:42.770 align:start position:0%
twelve gigabytes probably now so this is
the<00:09:41.700><c> this</c><00:09:41.880><c> is</c><00:09:42.030><c> where</c><00:09:42.180><c> I'm</c><00:09:42.270><c> gonna</c><00:09:42.450><c> say</c><00:09:42.630><c> about</c>

00:09:42.770 --> 00:09:42.780 align:start position:0%
the this is where I'm gonna say about
 

00:09:42.780 --> 00:09:45.380 align:start position:0%
the this is where I'm gonna say about
receipts<00:09:43.320><c> because</c><00:09:43.530><c> I</c><00:09:43.890><c> haven't</c><00:09:44.790><c> tested</c><00:09:45.030><c> all</c>

00:09:45.380 --> 00:09:45.390 align:start position:0%
receipts because I haven't tested all
 

00:09:45.390 --> 00:09:49.520 align:start position:0%
receipts because I haven't tested all
old<00:09:46.200><c> entire</c><00:09:46.800><c> entire</c><00:09:47.750><c> set</c><00:09:48.750><c> of</c><00:09:48.780><c> our</c><00:09:48.990><c> pcs</c><00:09:49.350><c> and</c>

00:09:49.520 --> 00:09:49.530 align:start position:0%
old entire entire set of our pcs and
 

00:09:49.530 --> 00:09:51.560 align:start position:0%
old entire entire set of our pcs and
again<00:09:50.130><c> this</c><00:09:50.280><c> numbers</c><00:09:50.670><c> are</c><00:09:50.820><c> very</c><00:09:50.940><c> rough</c><00:09:51.300><c> I</c>

00:09:51.560 --> 00:09:51.570 align:start position:0%
again this numbers are very rough I
 

00:09:51.570 --> 00:09:53.960 align:start position:0%
again this numbers are very rough I
didn't<00:09:51.900><c> do</c><00:09:52.110><c> scientific</c><00:09:52.500><c> studies</c><00:09:52.860><c> on</c><00:09:53.310><c> this</c><00:09:53.460><c> but</c>

00:09:53.960 --> 00:09:53.970 align:start position:0%
didn't do scientific studies on this but
 

00:09:53.970 --> 00:09:55.610 align:start position:0%
didn't do scientific studies on this but
this<00:09:54.090><c> is</c><00:09:54.180><c> what</c><00:09:54.330><c> I</c><00:09:54.360><c> just</c><00:09:54.450><c> saw</c><00:09:54.750><c> there</c><00:09:54.930><c> after</c><00:09:55.470><c> very</c>

00:09:55.610 --> 00:09:55.620 align:start position:0%
this is what I just saw there after very
 

00:09:55.620 --> 00:09:56.120 align:start position:0%
this is what I just saw there after very
quick<00:09:55.800><c> running</c>

00:09:56.120 --> 00:09:56.130 align:start position:0%
quick running
 

00:09:56.130 --> 00:09:59.540 align:start position:0%
quick running
I<00:09:56.250><c> run</c><00:09:56.940><c> the</c><00:09:57.270><c> both</c><00:09:57.840><c> archive</c><00:09:58.590><c> gas</c><00:09:58.860><c> and</c><00:09:59.130><c> turbo</c><00:09:59.400><c> gas</c>

00:09:59.540 --> 00:09:59.550 align:start position:0%
I run the both archive gas and turbo gas
 

00:09:59.550 --> 00:10:01.640 align:start position:0%
I run the both archive gas and turbo gas
on<00:09:59.670><c> the</c><00:09:59.760><c> same</c><00:09:59.910><c> machine</c><00:10:00.240><c> and</c><00:10:00.500><c> obviously</c><00:10:01.500><c> there</c>

00:10:01.640 --> 00:10:01.650 align:start position:0%
on the same machine and obviously there
 

00:10:01.650 --> 00:10:03.650 align:start position:0%
on the same machine and obviously there
would<00:10:01.740><c> be</c><00:10:01.800><c> lots</c><00:10:02.070><c> of</c><00:10:02.160><c> noise</c><00:10:02.520><c> but</c><00:10:02.940><c> I</c><00:10:03.150><c> could</c><00:10:03.510><c> see</c>

00:10:03.650 --> 00:10:03.660 align:start position:0%
would be lots of noise but I could see
 

00:10:03.660 --> 00:10:05.720 align:start position:0%
would be lots of noise but I could see
through<00:10:03.840><c> this</c><00:10:03.990><c> noise</c><00:10:04.140><c> that</c><00:10:04.340><c> generally</c><00:10:05.340><c> the</c>

00:10:05.720 --> 00:10:05.730 align:start position:0%
through this noise that generally the
 

00:10:05.730 --> 00:10:07.430 align:start position:0%
through this noise that generally the
things<00:10:06.030><c> are</c><00:10:06.210><c> going</c><00:10:06.390><c> faster</c><00:10:06.780><c> except</c><00:10:07.140><c> for</c><00:10:07.350><c> the</c>

00:10:07.430 --> 00:10:07.440 align:start position:0%
things are going faster except for the
 

00:10:07.440 --> 00:10:10.280 align:start position:0%
things are going faster except for the
receipts<00:10:08.190><c> and</c><00:10:08.430><c> the</c><00:10:08.820><c> reason</c><00:10:09.120><c> that</c><00:10:09.270><c> for</c><00:10:09.480><c> that</c><00:10:10.140><c> is</c>

00:10:10.280 --> 00:10:10.290 align:start position:0%
receipts and the reason that for that is
 

00:10:10.290 --> 00:10:12.380 align:start position:0%
receipts and the reason that for that is
because<00:10:10.410><c> I</c><00:10:10.680><c> chose</c><00:10:10.950><c> to</c><00:10:11.010><c> prune</c><00:10:11.910><c> the</c><00:10:12.090><c> receipts</c>

00:10:12.380 --> 00:10:12.390 align:start position:0%
because I chose to prune the receipts
 

00:10:12.390 --> 00:10:14.360 align:start position:0%
because I chose to prune the receipts
from<00:10:12.570><c> the</c><00:10:12.750><c> database</c><00:10:13.230><c> and</c><00:10:13.500><c> instead</c><00:10:14.160><c> I</c><00:10:14.310><c> just</c>

00:10:14.360 --> 00:10:14.370 align:start position:0%
from the database and instead I just
 

00:10:14.370 --> 00:10:17.630 align:start position:0%
from the database and instead I just
recompute<00:10:15.210><c> them</c><00:10:15.390><c> so</c><00:10:15.840><c> when</c><00:10:16.400><c> somebody</c><00:10:17.400><c> asks</c><00:10:17.430><c> me</c>

00:10:17.630 --> 00:10:17.640 align:start position:0%
recompute them so when somebody asks me
 

00:10:17.640 --> 00:10:19.940 align:start position:0%
recompute them so when somebody asks me
for<00:10:17.820><c> receipt</c><00:10:18.090><c> I</c><00:10:18.270><c> just</c><00:10:18.840><c> go</c><00:10:19.020><c> to</c><00:10:19.050><c> the</c><00:10:19.320><c> state</c><00:10:19.560><c> where</c>

00:10:19.940 --> 00:10:19.950 align:start position:0%
for receipt I just go to the state where
 

00:10:19.950 --> 00:10:23.150 align:start position:0%
for receipt I just go to the state where
that<00:10:20.220><c> was</c><00:10:20.910><c> at</c><00:10:21.240><c> that</c><00:10:21.570><c> block</c><00:10:21.990><c> and</c><00:10:22.350><c> after</c><00:10:23.070><c> that</c>

00:10:23.150 --> 00:10:23.160 align:start position:0%
that was at that block and after that
 

00:10:23.160 --> 00:10:25.280 align:start position:0%
that was at that block and after that
transaction<00:10:23.670><c> just</c><00:10:23.910><c> really</c><00:10:24.840><c> execute</c><00:10:25.200><c> the</c>

00:10:25.280 --> 00:10:25.290 align:start position:0%
transaction just really execute the
 

00:10:25.290 --> 00:10:27.050 align:start position:0%
transaction just really execute the
transaction<00:10:25.500><c> produce</c><00:10:26.100><c> receipts</c><00:10:26.280><c> return</c><00:10:26.910><c> them</c>

00:10:27.050 --> 00:10:27.060 align:start position:0%
transaction produce receipts return them
 

00:10:27.060 --> 00:10:29.420 align:start position:0%
transaction produce receipts return them
it<00:10:27.450><c> turns</c><00:10:27.630><c> out</c><00:10:27.780><c> to</c><00:10:27.930><c> be</c><00:10:27.960><c> slower</c><00:10:28.380><c> actually</c><00:10:29.280><c> this</c>

00:10:29.420 --> 00:10:29.430 align:start position:0%
it turns out to be slower actually this
 

00:10:29.430 --> 00:10:31.100 align:start position:0%
it turns out to be slower actually this
might<00:10:29.670><c> be</c><00:10:29.820><c> not</c><00:10:29.970><c> ten</c><00:10:30.180><c> times</c><00:10:30.210><c> may</c><00:10:30.600><c> be</c><00:10:30.630><c> a</c><00:10:30.750><c> bit</c><00:10:30.930><c> more</c>

00:10:31.100 --> 00:10:31.110 align:start position:0%
might be not ten times may be a bit more
 

00:10:31.110 --> 00:10:33.380 align:start position:0%
might be not ten times may be a bit more
slower<00:10:31.380><c> but</c><00:10:32.310><c> somebody</c><00:10:32.730><c> tell</c><00:10:32.910><c> me</c><00:10:32.940><c> that</c><00:10:33.240><c> maybe</c>

00:10:33.380 --> 00:10:33.390 align:start position:0%
slower but somebody tell me that maybe
 

00:10:33.390 --> 00:10:35.090 align:start position:0%
slower but somebody tell me that maybe
you<00:10:33.570><c> just</c><00:10:33.690><c> need</c><00:10:33.870><c> to</c><00:10:33.990><c> be</c><00:10:34.080><c> a</c><00:10:34.110><c> flag</c><00:10:34.380><c> because</c><00:10:34.770><c> some</c>

00:10:35.090 --> 00:10:35.100 align:start position:0%
you just need to be a flag because some
 

00:10:35.100 --> 00:10:36.470 align:start position:0%
you just need to be a flag because some
people<00:10:35.370><c> the</c><00:10:35.700><c> only</c><00:10:35.850><c> thing</c><00:10:36.060><c> they</c><00:10:36.210><c> do</c><00:10:36.270><c> is</c>

00:10:36.470 --> 00:10:36.480 align:start position:0%
people the only thing they do is
 

00:10:36.480 --> 00:10:38.420 align:start position:0%
people the only thing they do is
actually<00:10:36.660><c> query</c><00:10:37.260><c> receipts</c><00:10:37.770><c> so</c><00:10:38.100><c> for</c><00:10:38.310><c> those</c>

00:10:38.420 --> 00:10:38.430 align:start position:0%
actually query receipts so for those
 

00:10:38.430 --> 00:10:40.190 align:start position:0%
actually query receipts so for those
people<00:10:38.790><c> they</c><00:10:38.970><c> might</c><00:10:39.120><c> be</c><00:10:39.270><c> able</c><00:10:39.390><c> to</c><00:10:39.600><c> might</c><00:10:39.990><c> want</c>

00:10:40.190 --> 00:10:40.200 align:start position:0%
people they might be able to might want
 

00:10:40.200 --> 00:10:43.220 align:start position:0%
people they might be able to might want
to<00:10:40.290><c> pay</c><00:10:40.410><c> 70</c><00:10:40.860><c> gigs</c><00:10:41.070><c> for</c><00:10:41.310><c> for</c><00:10:42.060><c> speed</c><00:10:42.420><c> of</c><00:10:42.510><c> that</c><00:10:42.660><c> RPC</c>

00:10:43.220 --> 00:10:43.230 align:start position:0%
to pay 70 gigs for for speed of that RPC
 

00:10:43.230 --> 00:10:45.890 align:start position:0%
to pay 70 gigs for for speed of that RPC
so<00:10:44.100><c> now</c><00:10:44.220><c> the</c><00:10:44.280><c> other</c><00:10:44.700><c> thing</c><00:10:44.880><c> I</c><00:10:45.000><c> didn't</c><00:10:45.420><c> quite</c>

00:10:45.890 --> 00:10:45.900 align:start position:0%
so now the other thing I didn't quite
 

00:10:45.900 --> 00:10:48.110 align:start position:0%
so now the other thing I didn't quite
recently<00:10:46.230><c> interpret</c><00:10:46.650><c> guess</c><00:10:46.740><c> is</c><00:10:46.890><c> they</c><00:10:47.070><c> I</c><00:10:47.730><c> have</c>

00:10:48.110 --> 00:10:48.120 align:start position:0%
recently interpret guess is they I have
 

00:10:48.120 --> 00:10:49.520 align:start position:0%
recently interpret guess is they I have
prepared<00:10:48.510><c> it</c><00:10:48.720><c> for</c><00:10:48.900><c> the</c><00:10:48.960><c> pruning</c><00:10:49.320><c> but</c><00:10:49.470><c> I</c>

00:10:49.520 --> 00:10:49.530 align:start position:0%
prepared it for the pruning but I
 

00:10:49.530 --> 00:10:51.140 align:start position:0%
prepared it for the pruning but I
haven't<00:10:49.800><c> implemented</c><00:10:50.190><c> pruning</c><00:10:50.640><c> yet</c><00:10:50.790><c> so</c><00:10:50.970><c> but</c><00:10:51.090><c> I</c>

00:10:51.140 --> 00:10:51.150 align:start position:0%
haven't implemented pruning yet so but I
 

00:10:51.150 --> 00:10:52.940 align:start position:0%
haven't implemented pruning yet so but I
made<00:10:51.360><c> sure</c><00:10:51.390><c> that</c><00:10:51.750><c> the</c><00:10:52.140><c> pruning</c><00:10:52.410><c> can</c><00:10:52.650><c> be</c><00:10:52.800><c> done</c>

00:10:52.940 --> 00:10:52.950 align:start position:0%
made sure that the pruning can be done
 

00:10:52.950 --> 00:10:55.130 align:start position:0%
made sure that the pruning can be done
pretty<00:10:53.430><c> faithfully</c><00:10:53.880><c> and</c><00:10:54.060><c> so</c><00:10:54.480><c> the</c><00:10:54.570><c> idea</c><00:10:54.840><c> here</c>

00:10:55.130 --> 00:10:55.140 align:start position:0%
pretty faithfully and so the idea here
 

00:10:55.140 --> 00:10:57.500 align:start position:0%
pretty faithfully and so the idea here
is<00:10:55.170><c> that</c><00:10:55.320><c> instead</c><00:10:55.800><c> of</c><00:10:56.130><c> so</c><00:10:56.940><c> what</c><00:10:57.090><c> you</c><00:10:57.180><c> could</c><00:10:57.330><c> see</c>

00:10:57.500 --> 00:10:57.510 align:start position:0%
is that instead of so what you could see
 

00:10:57.510 --> 00:11:00.320 align:start position:0%
is that instead of so what you could see
in<00:10:57.630><c> this</c><00:10:57.750><c> diagram</c><00:10:58.430><c> so</c><00:10:59.430><c> every</c><00:10:59.790><c> bubble</c><00:11:00.000><c> every</c>

00:11:00.320 --> 00:11:00.330 align:start position:0%
in this diagram so every bubble every
 

00:11:00.330 --> 00:11:02.300 align:start position:0%
in this diagram so every bubble every
little<00:11:00.930><c> circle</c><00:11:01.290><c> is</c><00:11:01.410><c> actually</c><00:11:01.710><c> a</c><00:11:01.740><c> record</c><00:11:02.100><c> in</c><00:11:02.220><c> a</c>

00:11:02.300 --> 00:11:02.310 align:start position:0%
little circle is actually a record in a
 

00:11:02.310 --> 00:11:06.380 align:start position:0%
little circle is actually a record in a
database<00:11:02.580><c> and</c><00:11:02.970><c> so</c><00:11:03.690><c> the</c><00:11:04.140><c> the</c><00:11:04.920><c> arrows</c><00:11:05.730><c> like</c><00:11:06.150><c> this</c>

00:11:06.380 --> 00:11:06.390 align:start position:0%
database and so the the arrows like this
 

00:11:06.390 --> 00:11:07.280 align:start position:0%
database and so the the arrows like this
thick<00:11:06.540><c> arrows</c><00:11:06.930><c> they</c>

00:11:07.280 --> 00:11:07.290 align:start position:0%
thick arrows they
 

00:11:07.290 --> 00:11:11.030 align:start position:0%
thick arrows they
they<00:11:07.529><c> represent</c><00:11:08.160><c> that</c><00:11:08.720><c> the</c><00:11:09.720><c> each</c><00:11:10.380><c> to</c><00:11:10.649><c> each</c><00:11:10.860><c> of</c>

00:11:11.030 --> 00:11:11.040 align:start position:0%
they represent that the each to each of
 

00:11:11.040 --> 00:11:12.650 align:start position:0%
they represent that the each to each of
these<00:11:11.160><c> circles</c><00:11:11.850><c> is</c><00:11:12.029><c> basically</c><00:11:12.509><c> a</c>

00:11:12.650 --> 00:11:12.660 align:start position:0%
these circles is basically a
 

00:11:12.660 --> 00:11:15.050 align:start position:0%
these circles is basically a
representation<00:11:13.139><c> of</c><00:11:13.589><c> the</c><00:11:14.250><c> state</c><00:11:14.430><c> for</c><00:11:14.910><c> that</c>

00:11:15.050 --> 00:11:15.060 align:start position:0%
representation of the state for that
 

00:11:15.060 --> 00:11:16.579 align:start position:0%
representation of the state for that
period<00:11:15.509><c> of</c><00:11:15.540><c> time</c><00:11:15.779><c> so</c><00:11:16.019><c> let's</c><00:11:16.199><c> say</c><00:11:16.320><c> that</c><00:11:16.350><c> the</c>

00:11:16.579 --> 00:11:16.589 align:start position:0%
period of time so let's say that the
 

00:11:16.589 --> 00:11:18.350 align:start position:0%
period of time so let's say that the
green<00:11:16.800><c> circle</c><00:11:17.190><c> on</c><00:11:17.279><c> the</c><00:11:17.370><c> right</c><00:11:17.399><c> is</c><00:11:17.910><c> the</c><00:11:18.089><c> current</c>

00:11:18.350 --> 00:11:18.360 align:start position:0%
green circle on the right is the current
 

00:11:18.360 --> 00:11:19.519 align:start position:0%
green circle on the right is the current
state<00:11:18.540><c> it</c><00:11:18.750><c> means</c><00:11:18.899><c> that</c><00:11:19.079><c> the</c><00:11:19.170><c> current</c><00:11:19.320><c> state</c>

00:11:19.519 --> 00:11:19.529 align:start position:0%
state it means that the current state
 

00:11:19.529 --> 00:11:22.430 align:start position:0%
state it means that the current state
has<00:11:19.680><c> been</c><00:11:19.860><c> for</c><00:11:20.399><c> that</c><00:11:20.519><c> like</c><00:11:21.120><c> if</c><00:11:21.570><c> you</c><00:11:21.660><c> look</c><00:11:22.290><c> at</c>

00:11:22.430 --> 00:11:22.440 align:start position:0%
has been for that like if you look at
 

00:11:22.440 --> 00:11:25.069 align:start position:0%
has been for that like if you look at
the<00:11:22.500><c> top</c><00:11:22.709><c> one</c><00:11:22.889><c> for</c><00:11:23.550><c> the</c><00:11:23.759><c> last</c><00:11:23.910><c> let's</c><00:11:24.630><c> say</c><00:11:24.690><c> seven</c>

00:11:25.069 --> 00:11:25.079 align:start position:0%
the top one for the last let's say seven
 

00:11:25.079 --> 00:11:27.050 align:start position:0%
the top one for the last let's say seven
blocks<00:11:25.319><c> or</c><00:11:25.680><c> eight</c><00:11:26.040><c> blocks</c><00:11:26.339><c> I</c><00:11:26.579><c> don't</c><00:11:26.759><c> see</c><00:11:26.940><c> it</c>

00:11:27.050 --> 00:11:27.060 align:start position:0%
blocks or eight blocks I don't see it
 

00:11:27.060 --> 00:11:29.540 align:start position:0%
blocks or eight blocks I don't see it
exactly<00:11:27.839><c> this</c><00:11:28.290><c> was</c><00:11:28.560><c> the</c><00:11:28.709><c> current</c><00:11:28.920><c> state</c><00:11:29.250><c> and</c>

00:11:29.540 --> 00:11:29.550 align:start position:0%
exactly this was the current state and
 

00:11:29.550 --> 00:11:31.309 align:start position:0%
exactly this was the current state and
it<00:11:29.880><c> hasn't</c><00:11:30.209><c> been</c><00:11:30.300><c> changed</c><00:11:30.660><c> for</c><00:11:30.839><c> seven</c><00:11:31.110><c> or</c>

00:11:31.309 --> 00:11:31.319 align:start position:0%
it hasn't been changed for seven or
 

00:11:31.319 --> 00:11:33.530 align:start position:0%
it hasn't been changed for seven or
eight<00:11:31.529><c> blocks</c><00:11:31.800><c> right</c><00:11:32.160><c> and</c><00:11:32.490><c> before</c><00:11:33.120><c> that</c><00:11:33.329><c> there</c>

00:11:33.530 --> 00:11:33.540 align:start position:0%
eight blocks right and before that there
 

00:11:33.540 --> 00:11:35.990 align:start position:0%
eight blocks right and before that there
was<00:11:33.660><c> this</c><00:11:33.779><c> yellow</c><00:11:34.170><c> bit</c><00:11:34.410><c> which</c><00:11:34.680><c> was</c><00:11:34.920><c> since</c><00:11:35.759><c> we</c>

00:11:35.990 --> 00:11:36.000 align:start position:0%
was this yellow bit which was since we
 

00:11:36.000 --> 00:11:38.600 align:start position:0%
was this yellow bit which was since we
know<00:11:36.180><c> and</c><00:11:36.449><c> and</c><00:11:37.199><c> so</c><00:11:37.350><c> on</c><00:11:37.380><c> so</c><00:11:37.889><c> the</c><00:11:38.040><c> red</c><00:11:38.250><c> bit</c><00:11:38.430><c> is</c>

00:11:38.600 --> 00:11:38.610 align:start position:0%
know and and so on so the red bit is
 

00:11:38.610 --> 00:11:40.579 align:start position:0%
know and and so on so the red bit is
where<00:11:39.120><c> something</c><00:11:39.930><c> gets</c><00:11:40.050><c> deleted</c>

00:11:40.579 --> 00:11:40.589 align:start position:0%
where something gets deleted
 

00:11:40.589 --> 00:11:42.110 align:start position:0%
where something gets deleted
for<00:11:40.949><c> example</c><00:11:41.339><c> the</c><00:11:41.459><c> account</c><00:11:41.670><c> gets</c><00:11:41.910><c> deleted</c>

00:11:42.110 --> 00:11:42.120 align:start position:0%
for example the account gets deleted
 

00:11:42.120 --> 00:11:44.569 align:start position:0%
for example the account gets deleted
then<00:11:42.449><c> I</c><00:11:42.720><c> mark</c><00:11:43.110><c> it</c><00:11:43.199><c> as</c><00:11:43.350><c> a</c><00:11:43.380><c> red</c><00:11:43.589><c> we</c><00:11:44.130><c> put</c><00:11:44.339><c> it</c><00:11:44.430><c> as</c><00:11:44.550><c> a</c>

00:11:44.569 --> 00:11:44.579 align:start position:0%
then I mark it as a red we put it as a
 

00:11:44.579 --> 00:11:46.220 align:start position:0%
then I mark it as a red we put it as a
record<00:11:44.880><c> as</c><00:11:45.000><c> well</c><00:11:45.180><c> and</c><00:11:45.360><c> also</c><00:11:45.870><c> that</c><00:11:45.990><c> you</c><00:11:46.079><c> could</c>

00:11:46.220 --> 00:11:46.230 align:start position:0%
record as well and also that you could
 

00:11:46.230 --> 00:11:48.590 align:start position:0%
record as well and also that you could
see<00:11:46.410><c> that</c><00:11:46.529><c> the</c><00:11:46.709><c> blank</c><00:11:46.949><c> blue</c><00:11:47.730><c> one</c><00:11:48.000><c> this</c><00:11:48.420><c> is</c>

00:11:48.590 --> 00:11:48.600 align:start position:0%
see that the blank blue one this is
 

00:11:48.600 --> 00:11:50.360 align:start position:0%
see that the blank blue one this is
where<00:11:48.779><c> something</c><00:11:49.139><c> just</c><00:11:49.380><c> first</c><00:11:49.589><c> been</c><00:11:49.860><c> created</c>

00:11:50.360 --> 00:11:50.370 align:start position:0%
where something just first been created
 

00:11:50.370 --> 00:11:53.030 align:start position:0%
where something just first been created
and<00:11:50.579><c> there</c><00:11:51.060><c> was</c><00:11:51.180><c> nothing</c><00:11:51.509><c> in</c><00:11:51.600><c> bits</c><00:11:52.019><c> before</c><00:11:52.230><c> so</c>

00:11:53.030 --> 00:11:53.040 align:start position:0%
and there was nothing in bits before so
 

00:11:53.040 --> 00:11:55.670 align:start position:0%
and there was nothing in bits before so
now<00:11:53.370><c> what</c><00:11:53.639><c> we</c><00:11:53.759><c> can</c><00:11:53.910><c> do</c><00:11:54.029><c> is</c><00:11:54.120><c> that</c><00:11:54.259><c> what</c><00:11:55.259><c> I</c><00:11:55.290><c> could</c>

00:11:55.670 --> 00:11:55.680 align:start position:0%
now what we can do is that what I could
 

00:11:55.680 --> 00:11:59.120 align:start position:0%
now what we can do is that what I could
reverse<00:11:56.069><c> diffs</c><00:11:56.750><c> instead</c><00:11:57.750><c> of</c><00:11:57.870><c> forward</c><00:11:58.350><c> ifs</c><00:11:58.529><c> and</c>

00:11:59.120 --> 00:11:59.130 align:start position:0%
reverse diffs instead of forward ifs and
 

00:11:59.130 --> 00:12:01.610 align:start position:0%
reverse diffs instead of forward ifs and
what<00:11:59.490><c> it</c><00:11:59.579><c> allows</c><00:11:59.819><c> you</c><00:11:59.970><c> to</c><00:12:00.120><c> do</c><00:12:00.240><c> is</c><00:12:00.389><c> this</c><00:12:00.600><c> so</c><00:12:01.470><c> if</c>

00:12:01.610 --> 00:12:01.620 align:start position:0%
what it allows you to do is this so if
 

00:12:01.620 --> 00:12:03.439 align:start position:0%
what it allows you to do is this so if
you<00:12:01.740><c> basically</c><00:12:02.160><c> chop</c><00:12:02.399><c> off</c><00:12:02.579><c> the</c><00:12:02.759><c> the</c><00:12:02.970><c> left</c><00:12:03.180><c> bit</c>

00:12:03.439 --> 00:12:03.449 align:start position:0%
you basically chop off the the left bit
 

00:12:03.449 --> 00:12:06.199 align:start position:0%
you basically chop off the the left bit
then<00:12:04.199><c> you</c><00:12:04.889><c> can</c><00:12:05.040><c> just</c><00:12:05.220><c> keep</c><00:12:05.339><c> running</c><00:12:05.670><c> your</c><00:12:05.819><c> your</c>

00:12:06.199 --> 00:12:06.209 align:start position:0%
then you can just keep running your your
 

00:12:06.209 --> 00:12:08.059 align:start position:0%
then you can just keep running your your
note<00:12:06.360><c> because</c><00:12:06.660><c> you</c><00:12:06.870><c> still</c><00:12:07.230><c> have</c><00:12:07.470><c> everything</c>

00:12:08.059 --> 00:12:08.069 align:start position:0%
note because you still have everything
 

00:12:08.069 --> 00:12:10.280 align:start position:0%
note because you still have everything
everything<00:12:08.730><c> is</c><00:12:08.850><c> still</c><00:12:08.970><c> consistent</c><00:12:09.300><c> so</c><00:12:10.259><c> you</c>

00:12:10.280 --> 00:12:10.290 align:start position:0%
everything is still consistent so you
 

00:12:10.290 --> 00:12:12.650 align:start position:0%
everything is still consistent so you
can<00:12:10.529><c> still</c><00:12:10.740><c> query</c><00:12:11.130><c> the</c><00:12:11.430><c> state</c><00:12:11.790><c> at</c><00:12:12.000><c> any</c><00:12:12.269><c> point</c>

00:12:12.650 --> 00:12:12.660 align:start position:0%
can still query the state at any point
 

00:12:12.660 --> 00:12:15.920 align:start position:0%
can still query the state at any point
that<00:12:13.050><c> you</c><00:12:13.230><c> have</c><00:12:13.560><c> a</c><00:12:13.589><c> history</c><00:12:14.069><c> for</c><00:12:14.329><c> if</c><00:12:15.329><c> you</c><00:12:15.540><c> if</c>

00:12:15.920 --> 00:12:15.930 align:start position:0%
that you have a history for if you if
 

00:12:15.930 --> 00:12:17.360 align:start position:0%
that you have a history for if you if
you<00:12:16.079><c> try</c><00:12:16.230><c> to</c><00:12:16.290><c> do</c><00:12:16.529><c> it</c><00:12:16.649><c> with</c><00:12:16.829><c> the</c><00:12:16.889><c> forward</c><00:12:17.220><c> this</c>

00:12:17.360 --> 00:12:17.370 align:start position:0%
you try to do it with the forward this
 

00:12:17.370 --> 00:12:20.960 align:start position:0%
you try to do it with the forward this
that<00:12:17.610><c> would</c><00:12:17.790><c> be</c><00:12:17.930><c> difficult</c><00:12:19.730><c> because</c><00:12:20.730><c> you</c>

00:12:20.960 --> 00:12:20.970 align:start position:0%
that would be difficult because you
 

00:12:20.970 --> 00:12:23.329 align:start position:0%
that would be difficult because you
would<00:12:21.149><c> have</c><00:12:21.180><c> to</c><00:12:21.630><c> when</c><00:12:22.170><c> you</c><00:12:22.290><c> chop</c><00:12:22.529><c> the</c><00:12:22.829><c> chop</c>

00:12:23.329 --> 00:12:23.339 align:start position:0%
would have to when you chop the chop
 

00:12:23.339 --> 00:12:25.250 align:start position:0%
would have to when you chop the chop
this<00:12:23.519><c> up</c><00:12:23.730><c> you</c><00:12:24.120><c> would</c><00:12:24.269><c> have</c><00:12:24.300><c> to</c><00:12:24.600><c> rebuild</c><00:12:24.990><c> the</c>

00:12:25.250 --> 00:12:25.260 align:start position:0%
this up you would have to rebuild the
 

00:12:25.260 --> 00:12:27.400 align:start position:0%
this up you would have to rebuild the
current<00:12:25.529><c> state</c><00:12:25.740><c> at</c><00:12:25.920><c> the</c><00:12:26.069><c> point</c><00:12:26.670><c> of</c><00:12:26.790><c> the</c><00:12:26.940><c> chop</c>

00:12:27.400 --> 00:12:27.410 align:start position:0%
current state at the point of the chop
 

00:12:27.410 --> 00:12:31.009 align:start position:0%
current state at the point of the chop
because<00:12:28.410><c> everything</c><00:12:28.860><c> is</c><00:12:29.010><c> Israel</c><00:12:29.730><c> is</c><00:12:30.019><c> relative</c>

00:12:31.009 --> 00:12:31.019 align:start position:0%
because everything is Israel is relative
 

00:12:31.019 --> 00:12:33.170 align:start position:0%
because everything is Israel is relative
to<00:12:31.050><c> the</c><00:12:31.260><c> to</c><00:12:31.800><c> the</c><00:12:31.949><c> previous</c><00:12:32.490><c> um</c><00:12:32.699><c> some</c><00:12:32.970><c> sort</c><00:12:33.089><c> of</c>

00:12:33.170 --> 00:12:33.180 align:start position:0%
to the to the previous um some sort of
 

00:12:33.180 --> 00:12:36.110 align:start position:0%
to the to the previous um some sort of
previous<00:12:33.569><c> snapshot</c><00:12:33.740><c> so</c><00:12:34.740><c> as</c><00:12:35.310><c> I</c><00:12:35.699><c> said</c><00:12:35.850><c> I</c><00:12:35.880><c> haven't</c>

00:12:36.110 --> 00:12:36.120 align:start position:0%
previous snapshot so as I said I haven't
 

00:12:36.120 --> 00:12:39.259 align:start position:0%
previous snapshot so as I said I haven't
implemented<00:12:36.480><c> yet</c><00:12:36.630><c> but</c><00:12:36.959><c> it's</c><00:12:37.199><c> trivial</c><00:12:38.269><c> now</c>

00:12:39.259 --> 00:12:39.269 align:start position:0%
implemented yet but it's trivial now
 

00:12:39.269 --> 00:12:41.870 align:start position:0%
implemented yet but it's trivial now
light<00:12:40.050><c> clients</c><00:12:40.589><c> I</c><00:12:40.740><c> mean</c><00:12:40.980><c> here</c><00:12:41.339><c> I'm</c><00:12:41.459><c> actually</c>

00:12:41.870 --> 00:12:41.880 align:start position:0%
light clients I mean here I'm actually
 

00:12:41.880 --> 00:12:43.730 align:start position:0%
light clients I mean here I'm actually
mean<00:12:42.029><c> light</c><00:12:42.240><c> server</c><00:12:42.540><c> and</c><00:12:42.870><c> at</c><00:12:43.319><c> the</c><00:12:43.410><c> moment</c><00:12:43.529><c> is</c>

00:12:43.730 --> 00:12:43.740 align:start position:0%
mean light server and at the moment is
 

00:12:43.740 --> 00:12:45.139 align:start position:0%
mean light server and at the moment is
not<00:12:43.860><c> implemented</c><00:12:44.220><c> and</c><00:12:44.579><c> the</c><00:12:44.639><c> reason</c><00:12:44.910><c> for</c><00:12:45.089><c> that</c>

00:12:45.139 --> 00:12:45.149 align:start position:0%
not implemented and the reason for that
 

00:12:45.149 --> 00:12:48.199 align:start position:0%
not implemented and the reason for that
is<00:12:45.690><c> because</c><00:12:46.260><c> I</c><00:12:46.740><c> simply</c><00:12:47.490><c> don't</c><00:12:47.670><c> store</c><00:12:48.029><c> any</c>

00:12:48.199 --> 00:12:48.209 align:start position:0%
is because I simply don't store any
 

00:12:48.209 --> 00:12:51.259 align:start position:0%
is because I simply don't store any
hashes<00:12:48.600><c> in</c><00:12:48.630><c> a</c><00:12:48.779><c> database</c><00:12:49.079><c> and</c><00:12:49.519><c> I</c><00:12:50.519><c> kind</c><00:12:51.000><c> of</c><00:12:51.060><c> do</c>

00:12:51.259 --> 00:12:51.269 align:start position:0%
hashes in a database and I kind of do
 

00:12:51.269 --> 00:12:53.240 align:start position:0%
hashes in a database and I kind of do
but<00:12:51.300><c> not</c><00:12:51.779><c> much</c><00:12:52.019><c> only</c><00:12:52.529><c> in</c><00:12:52.709><c> Oconee</c><00:12:52.949><c> for</c><00:12:53.189><c> the</c>

00:12:53.240 --> 00:12:53.250 align:start position:0%
but not much only in Oconee for the
 

00:12:53.250 --> 00:12:55.189 align:start position:0%
but not much only in Oconee for the
current<00:12:53.490><c> state</c><00:12:53.639><c> so</c><00:12:54.149><c> what</c><00:12:54.510><c> the</c><00:12:54.630><c> light</c><00:12:54.779><c> clients</c>

00:12:55.189 --> 00:12:55.199 align:start position:0%
current state so what the light clients
 

00:12:55.199 --> 00:12:57.050 align:start position:0%
current state so what the light clients
actually<00:12:55.529><c> need</c><00:12:55.709><c> you</c><00:12:56.339><c> could</c><00:12:56.490><c> see</c><00:12:56.670><c> on</c><00:12:56.819><c> a</c><00:12:56.850><c> lot</c>

00:12:57.050 --> 00:12:57.060 align:start position:0%
actually need you could see on a lot
 

00:12:57.060 --> 00:12:58.670 align:start position:0%
actually need you could see on a lot
right<00:12:57.240><c> hand</c><00:12:57.449><c> side</c><00:12:57.630><c> all</c><00:12:57.779><c> the</c><00:12:57.870><c> ticks</c><00:12:58.110><c> that</c><00:12:58.199><c> the</c>

00:12:58.670 --> 00:12:58.680 align:start position:0%
right hand side all the ticks that the
 

00:12:58.680 --> 00:13:00.980 align:start position:0%
right hand side all the ticks that the
last<00:12:59.040><c> two</c><00:12:59.250><c> protocol</c><00:12:59.670><c> needs</c><00:13:00.149><c> all</c><00:13:00.389><c> this</c><00:13:00.540><c> support</c>

00:13:00.980 --> 00:13:00.990 align:start position:0%
last two protocol needs all this support
 

00:13:00.990 --> 00:13:03.319 align:start position:0%
last two protocol needs all this support
all<00:13:01.199><c> these</c><00:13:01.350><c> things</c><00:13:01.680><c> and</c><00:13:02.250><c> the</c><00:13:02.819><c> ones</c><00:13:03.029><c> that</c><00:13:03.120><c> my</c>

00:13:03.319 --> 00:13:03.329 align:start position:0%
all these things and the ones that my
 

00:13:03.329 --> 00:13:05.210 align:start position:0%
all these things and the ones that my
accountant<00:13:03.899><c> currently</c><00:13:04.350><c> cannot</c><00:13:04.589><c> provide</c><00:13:04.949><c> is</c>

00:13:05.210 --> 00:13:05.220 align:start position:0%
accountant currently cannot provide is
 

00:13:05.220 --> 00:13:07.009 align:start position:0%
accountant currently cannot provide is
these<00:13:05.459><c> the</c><00:13:05.910><c> ones</c><00:13:06.089><c> which</c><00:13:06.269><c> I</c><00:13:06.449><c> pointed</c><00:13:06.660><c> with</c><00:13:06.990><c> a</c>

00:13:07.009 --> 00:13:07.019 align:start position:0%
these the ones which I pointed with a
 

00:13:07.019 --> 00:13:09.920 align:start position:0%
these the ones which I pointed with a
red<00:13:07.230><c> arrows</c><00:13:07.680><c> which</c><00:13:08.399><c> is</c><00:13:08.519><c> no</c><00:13:08.759><c> data</c><00:13:09.120><c> and</c><00:13:09.420><c> proofs</c>

00:13:09.920 --> 00:13:09.930 align:start position:0%
red arrows which is no data and proofs
 

00:13:09.930 --> 00:13:13.759 align:start position:0%
red arrows which is no data and proofs
all<00:13:10.350><c> right</c><00:13:10.500><c> so</c><00:13:11.870><c> no</c><00:13:12.870><c> data</c><00:13:13.170><c> will</c><00:13:13.439><c> be</c><00:13:13.560><c> very</c>

00:13:13.759 --> 00:13:13.769 align:start position:0%
all right so no data will be very
 

00:13:13.769 --> 00:13:15.319 align:start position:0%
all right so no data will be very
difficult<00:13:13.980><c> in</c><00:13:14.430><c> any</c><00:13:14.579><c> way</c><00:13:14.819><c> because</c><00:13:15.149><c> it's</c>

00:13:15.319 --> 00:13:15.329 align:start position:0%
difficult in any way because it's
 

00:13:15.329 --> 00:13:18.290 align:start position:0%
difficult in any way because it's
specific<00:13:15.870><c> to</c><00:13:15.980><c> it</c><00:13:16.980><c> turns</c><00:13:17.310><c> out</c><00:13:17.490><c> to</c><00:13:17.610><c> be</c><00:13:17.639><c> specific</c>

00:13:18.290 --> 00:13:18.300 align:start position:0%
specific to it turns out to be specific
 

00:13:18.300 --> 00:13:19.850 align:start position:0%
specific to it turns out to be specific
to<00:13:18.329><c> the</c><00:13:18.510><c> way</c><00:13:18.750><c> that</c><00:13:18.959><c> current</c><00:13:19.230><c> clients</c><00:13:19.560><c> store</c>

00:13:19.850 --> 00:13:19.860 align:start position:0%
to the way that current clients store
 

00:13:19.860 --> 00:13:21.660 align:start position:0%
to the way that current clients store
the<00:13:20.130><c> state</c><00:13:20.939><c> and</c><00:13:21.269><c> would</c><00:13:21.449><c> be</c>

00:13:21.660 --> 00:13:21.670 align:start position:0%
the state and would be
 

00:13:21.670 --> 00:13:23.250 align:start position:0%
the state and would be
very<00:13:21.850><c> difficult</c><00:13:22.090><c> for</c><00:13:22.450><c> me</c><00:13:22.570><c> to</c><00:13:22.600><c> implement</c><00:13:22.990><c> that</c>

00:13:23.250 --> 00:13:23.260 align:start position:0%
very difficult for me to implement that
 

00:13:23.260 --> 00:13:25.080 align:start position:0%
very difficult for me to implement that
because<00:13:23.590><c> it's</c><00:13:23.740><c> actually</c><00:13:23.890><c> you</c><00:13:24.490><c> cannot</c><00:13:24.760><c> come</c><00:13:25.060><c> up</c>

00:13:25.080 --> 00:13:25.090 align:start position:0%
because it's actually you cannot come up
 

00:13:25.090 --> 00:13:27.210 align:start position:0%
because it's actually you cannot come up
with<00:13:25.210><c> any</c><00:13:25.360><c> hash</c><00:13:25.780><c> in</c><00:13:26.140><c> history</c><00:13:26.770><c> or</c><00:13:27.010><c> in</c><00:13:27.160><c> the</c>

00:13:27.210 --> 00:13:27.220 align:start position:0%
with any hash in history or in the
 

00:13:27.220 --> 00:13:29.370 align:start position:0%
with any hash in history or in the
current<00:13:27.490><c> state</c><00:13:27.700><c> which</c><00:13:28.330><c> I</c><00:13:28.480><c> have</c><00:13:28.630><c> no</c><00:13:28.780><c> idea</c><00:13:29.110><c> where</c>

00:13:29.370 --> 00:13:29.380 align:start position:0%
current state which I have no idea where
 

00:13:29.380 --> 00:13:31.560 align:start position:0%
current state which I have no idea where
which<00:13:30.010><c> block</c><00:13:30.250><c> it</c><00:13:30.400><c> is</c><00:13:30.520><c> from</c><00:13:30.730><c> and</c><00:13:30.970><c> you're</c>

00:13:31.560 --> 00:13:31.570 align:start position:0%
which block it is from and you're
 

00:13:31.570 --> 00:13:33.810 align:start position:0%
which block it is from and you're
supposed<00:13:31.840><c> to</c><00:13:31.990><c> give</c><00:13:32.260><c> me</c><00:13:32.290><c> I</c><00:13:32.680><c> supposed</c><00:13:33.520><c> to</c><00:13:33.580><c> give</c>

00:13:33.810 --> 00:13:33.820 align:start position:0%
supposed to give me I supposed to give
 

00:13:33.820 --> 00:13:36.570 align:start position:0%
supposed to give me I supposed to give
you<00:13:33.970><c> the</c><00:13:34.320><c> the</c><00:13:35.320><c> note</c><00:13:35.530><c> for</c><00:13:35.800><c> that</c><00:13:35.920><c> and</c><00:13:36.250><c> I</c><00:13:36.340><c> don't</c>

00:13:36.570 --> 00:13:36.580 align:start position:0%
you the the note for that and I don't
 

00:13:36.580 --> 00:13:38.160 align:start position:0%
you the the note for that and I don't
have<00:13:36.820><c> idea</c><00:13:37.150><c> where</c><00:13:37.360><c> to</c><00:13:37.510><c> look</c><00:13:37.540><c> for</c><00:13:37.810><c> it</c><00:13:37.930><c> in</c><00:13:38.050><c> my</c>

00:13:38.160 --> 00:13:38.170 align:start position:0%
have idea where to look for it in my
 

00:13:38.170 --> 00:13:39.510 align:start position:0%
have idea where to look for it in my
database<00:13:38.500><c> because</c><00:13:38.920><c> my</c><00:13:39.040><c> database</c><00:13:39.490><c> is</c>

00:13:39.510 --> 00:13:39.520 align:start position:0%
database because my database is
 

00:13:39.520 --> 00:13:42.150 align:start position:0%
database because my database is
structured<00:13:40.150><c> by</c><00:13:40.300><c> the</c><00:13:40.360><c> blocks</c><00:13:40.600><c> the</c><00:13:41.530><c> get</c><00:13:41.860><c> proof</c>

00:13:42.150 --> 00:13:42.160 align:start position:0%
structured by the blocks the get proof
 

00:13:42.160 --> 00:13:44.460 align:start position:0%
structured by the blocks the get proof
is<00:13:42.430><c> more</c><00:13:42.640><c> is</c><00:13:42.790><c> easier</c><00:13:43.210><c> for</c><00:13:43.450><c> me</c><00:13:43.540><c> because</c><00:13:43.810><c> it</c><00:13:44.290><c> at</c>

00:13:44.460 --> 00:13:44.470 align:start position:0%
is more is easier for me because it at
 

00:13:44.470 --> 00:13:46.140 align:start position:0%
is more is easier for me because it at
least<00:13:44.620><c> it</c><00:13:44.800><c> tells</c><00:13:44.980><c> me</c><00:13:45.130><c> at</c><00:13:45.220><c> which</c><00:13:45.400><c> block</c><00:13:45.670><c> and</c><00:13:45.970><c> in</c>

00:13:46.140 --> 00:13:46.150 align:start position:0%
least it tells me at which block and in
 

00:13:46.150 --> 00:13:47.520 align:start position:0%
least it tells me at which block and in
which<00:13:46.270><c> account</c><00:13:46.600><c> you</c><00:13:46.810><c> look</c><00:13:46.930><c> for</c><00:13:47.170><c> so</c><00:13:47.380><c> I</c><00:13:47.410><c> can</c>

00:13:47.520 --> 00:13:47.530 align:start position:0%
which account you look for so I can
 

00:13:47.530 --> 00:13:49.740 align:start position:0%
which account you look for so I can
actually<00:13:48.040><c> find</c><00:13:48.280><c> it</c><00:13:48.460><c> so</c><00:13:48.940><c> it's</c><00:13:49.120><c> easier</c><00:13:49.540><c> to</c>

00:13:49.740 --> 00:13:49.750 align:start position:0%
actually find it so it's easier to
 

00:13:49.750 --> 00:13:53.010 align:start position:0%
actually find it so it's easier to
implement<00:13:49.960><c> that</c><00:13:50.520><c> and</c><00:13:51.520><c> maybe</c><00:13:51.790><c> I</c><00:13:52.420><c> know</c><00:13:52.660><c> that</c><00:13:52.930><c> the</c>

00:13:53.010 --> 00:13:53.020 align:start position:0%
implement that and maybe I know that the
 

00:13:53.020 --> 00:13:55.410 align:start position:0%
implement that and maybe I know that the
light<00:13:53.170><c> clients</c><00:13:53.530><c> can</c><00:13:53.680><c> ask</c><00:13:53.860><c> for</c><00:13:54.160><c> proofs</c><00:13:54.850><c> not</c><00:13:55.210><c> for</c>

00:13:55.410 --> 00:13:55.420 align:start position:0%
light clients can ask for proofs not for
 

00:13:55.420 --> 00:13:57.420 align:start position:0%
light clients can ask for proofs not for
the<00:13:55.480><c> current</c><00:13:55.750><c> state</c><00:13:55.840><c> but</c><00:13:56.140><c> but</c><00:13:56.710><c> for</c><00:13:56.920><c> for</c><00:13:57.220><c> some</c>

00:13:57.420 --> 00:13:57.430 align:start position:0%
the current state but but for for some
 

00:13:57.430 --> 00:14:00.090 align:start position:0%
the current state but but for for some
delayed<00:13:57.910><c> state</c><00:13:58.270><c> but</c><00:13:58.570><c> it</c><00:13:58.780><c> could</c><00:13:58.960><c> be</c><00:13:59.050><c> done</c><00:13:59.170><c> but</c>

00:14:00.090 --> 00:14:00.100 align:start position:0%
delayed state but it could be done but
 

00:14:00.100 --> 00:14:01.740 align:start position:0%
delayed state but it could be done but
and<00:14:00.640><c> the</c><00:14:00.850><c> and</c><00:14:01.060><c> then</c><00:14:01.180><c> there's</c><00:14:01.360><c> another</c><00:14:01.420><c> problem</c>

00:14:01.740 --> 00:14:01.750 align:start position:0%
and the and then there's another problem
 

00:14:01.750 --> 00:14:04.470 align:start position:0%
and the and then there's another problem
which<00:14:02.020><c> I</c><00:14:02.140><c> encountered</c><00:14:02.710><c> recently</c><00:14:03.040><c> I</c><00:14:03.520><c> call</c><00:14:04.360><c> it</c>

00:14:04.470 --> 00:14:04.480 align:start position:0%
which I encountered recently I call it
 

00:14:04.480 --> 00:14:06.960 align:start position:0%
which I encountered recently I call it
creates<00:14:04.810><c> a</c><00:14:04.990><c> revival</c><00:14:05.440><c> problem</c><00:14:05.800><c> and</c><00:14:06.160><c> it's</c><00:14:06.820><c> also</c>

00:14:06.960 --> 00:14:06.970 align:start position:0%
creates a revival problem and it's also
 

00:14:06.970 --> 00:14:09.720 align:start position:0%
creates a revival problem and it's also
actually<00:14:07.470><c> this</c><00:14:08.470><c> is</c><00:14:08.590><c> also</c><00:14:08.770><c> to</c><00:14:08.950><c> inform</c><00:14:09.580><c> people</c>

00:14:09.720 --> 00:14:09.730 align:start position:0%
actually this is also to inform people
 

00:14:09.730 --> 00:14:11.310 align:start position:0%
actually this is also to inform people
about<00:14:09.940><c> something</c><00:14:10.480><c> which</c><00:14:10.630><c> is</c><00:14:10.750><c> coming</c><00:14:10.960><c> up</c><00:14:11.170><c> in</c>

00:14:11.310 --> 00:14:11.320 align:start position:0%
about something which is coming up in
 

00:14:11.320 --> 00:14:13.680 align:start position:0%
about something which is coming up in
the<00:14:11.410><c> Constantinople</c><00:14:12.130><c> it</c><00:14:12.460><c> is</c><00:14:12.940><c> not</c><00:14:13.150><c> in</c><00:14:13.480><c> the</c><00:14:13.570><c> main</c>

00:14:13.680 --> 00:14:13.690 align:start position:0%
the Constantinople it is not in the main
 

00:14:13.690 --> 00:14:15.570 align:start position:0%
the Constantinople it is not in the main
idea<00:14:13.990><c> by</c><00:14:14.140><c> the</c><00:14:14.170><c> way</c><00:14:14.260><c> don't</c><00:14:14.560><c> get</c><00:14:14.800><c> scared</c><00:14:15.310><c> it's</c>

00:14:15.570 --> 00:14:15.580 align:start position:0%
idea by the way don't get scared it's
 

00:14:15.580 --> 00:14:19.290 align:start position:0%
idea by the way don't get scared it's
the<00:14:16.360><c> sir</c><00:14:17.230><c> great</c><00:14:17.680><c> show</c><00:14:17.860><c> up</c><00:14:17.980><c> code</c><00:14:18.300><c> essentially</c>

00:14:19.290 --> 00:14:19.300 align:start position:0%
the sir great show up code essentially
 

00:14:19.300 --> 00:14:22.460 align:start position:0%
the sir great show up code essentially
is<00:14:19.870><c> introduced</c><00:14:20.800><c> to</c><00:14:20.980><c> allow</c><00:14:21.390><c> efficient</c>

00:14:22.460 --> 00:14:22.470 align:start position:0%
is introduced to allow efficient
 

00:14:22.470 --> 00:14:25.770 align:start position:0%
is introduced to allow efficient
counterfactual<00:14:23.470><c> instantiation</c><00:14:24.010><c> and</c><00:14:24.340><c> in</c><00:14:25.330><c> the</c>

00:14:25.770 --> 00:14:25.780 align:start position:0%
counterfactual instantiation and in the
 

00:14:25.780 --> 00:14:27.870 align:start position:0%
counterfactual instantiation and in the
way<00:14:25.930><c> it</c><00:14:26.050><c> does</c><00:14:26.230><c> it</c><00:14:26.380><c> is</c><00:14:26.710><c> that</c><00:14:27.190><c> if</c><00:14:27.460><c> you</c><00:14:27.610><c> look</c><00:14:27.760><c> at</c>

00:14:27.870 --> 00:14:27.880 align:start position:0%
way it does it is that if you look at
 

00:14:27.880 --> 00:14:30.420 align:start position:0%
way it does it is that if you look at
the<00:14:27.970><c> formula</c><00:14:28.300><c> of</c><00:14:28.630><c> the</c><00:14:28.900><c> address</c><00:14:29.800><c> computation</c>

00:14:30.420 --> 00:14:30.430 align:start position:0%
the formula of the address computation
 

00:14:30.430 --> 00:14:32.370 align:start position:0%
the formula of the address computation
it<00:14:30.820><c> it</c><00:14:31.300><c> includes</c><00:14:31.600><c> address</c><00:14:32.140><c> which</c><00:14:32.350><c> is</c>

00:14:32.370 --> 00:14:32.380 align:start position:0%
it it includes address which is
 

00:14:32.380 --> 00:14:34.200 align:start position:0%
it it includes address which is
basically<00:14:32.800><c> the</c><00:14:33.040><c> creator</c><00:14:33.430><c> of</c><00:14:33.580><c> this</c><00:14:33.820><c> contract</c>

00:14:34.200 --> 00:14:34.210 align:start position:0%
basically the creator of this contract
 

00:14:34.210 --> 00:14:36.660 align:start position:0%
basically the creator of this contract
salt<00:14:34.900><c> which</c><00:14:35.170><c> could</c><00:14:35.380><c> be</c><00:14:35.500><c> chosen</c><00:14:35.740><c> at</c><00:14:36.040><c> at</c><00:14:36.460><c> will</c>

00:14:36.660 --> 00:14:36.670 align:start position:0%
salt which could be chosen at at will
 

00:14:36.670 --> 00:14:38.790 align:start position:0%
salt which could be chosen at at will
and<00:14:36.880><c> then</c><00:14:37.540><c> in</c><00:14:37.720><c> it</c><00:14:37.810><c> code</c><00:14:38.020><c> which</c><00:14:38.290><c> is</c><00:14:38.530><c> something</c>

00:14:38.790 --> 00:14:38.800 align:start position:0%
and then in it code which is something
 

00:14:38.800 --> 00:14:41.070 align:start position:0%
and then in it code which is something
which<00:14:39.130><c> will</c><00:14:39.370><c> be</c><00:14:39.400><c> executed</c><00:14:40.030><c> to</c><00:14:40.270><c> generate</c><00:14:40.870><c> the</c>

00:14:41.070 --> 00:14:41.080 align:start position:0%
which will be executed to generate the
 

00:14:41.080 --> 00:14:43.470 align:start position:0%
which will be executed to generate the
actual<00:14:41.230><c> deployed</c><00:14:41.710><c> code</c><00:14:41.920><c> so</c><00:14:42.610><c> that</c><00:14:42.850><c> means</c><00:14:43.270><c> that</c>

00:14:43.470 --> 00:14:43.480 align:start position:0%
actual deployed code so that means that
 

00:14:43.480 --> 00:14:45.150 align:start position:0%
actual deployed code so that means that
you<00:14:43.630><c> you</c><00:14:43.900><c> you</c><00:14:43.930><c> can</c><00:14:44.440><c> in</c><00:14:44.530><c> theory</c><00:14:44.740><c> and</c><00:14:45.070><c> in</c>

00:14:45.150 --> 00:14:45.160 align:start position:0%
you you you can in theory and in
 

00:14:45.160 --> 00:14:46.980 align:start position:0%
you you you can in theory and in
practice<00:14:45.210><c> recreate</c><00:14:46.210><c> the</c><00:14:46.330><c> contract</c><00:14:46.720><c> after</c>

00:14:46.980 --> 00:14:46.990 align:start position:0%
practice recreate the contract after
 

00:14:46.990 --> 00:14:48.390 align:start position:0%
practice recreate the contract after
they've<00:14:47.110><c> been</c><00:14:47.200><c> self</c><00:14:47.440><c> destructed</c><00:14:47.890><c> so</c><00:14:48.070><c> in</c><00:14:48.280><c> this</c>

00:14:48.390 --> 00:14:48.400 align:start position:0%
they've been self destructed so in this
 

00:14:48.400 --> 00:14:51.180 align:start position:0%
they've been self destructed so in this
diagram<00:14:48.670><c> the</c><00:14:49.600><c> big</c><00:14:49.750><c> circles</c><00:14:50.140><c> is</c><00:14:50.320><c> the</c><00:14:50.800><c> contract</c>

00:14:51.180 --> 00:14:51.190 align:start position:0%
diagram the big circles is the contract
 

00:14:51.190 --> 00:14:52.560 align:start position:0%
diagram the big circles is the contract
and<00:14:51.340><c> the</c><00:14:51.460><c> small</c><00:14:51.700><c> circles</c><00:14:52.090><c> is</c><00:14:52.210><c> the</c><00:14:52.330><c> storage</c>

00:14:52.560 --> 00:14:52.570 align:start position:0%
and the small circles is the storage
 

00:14:52.570 --> 00:14:54.360 align:start position:0%
and the small circles is the storage
items<00:14:52.960><c> of</c><00:14:53.080><c> the</c><00:14:53.170><c> contract</c><00:14:53.530><c> and</c><00:14:53.710><c> you</c><00:14:54.040><c> can</c><00:14:54.220><c> see</c>

00:14:54.360 --> 00:14:54.370 align:start position:0%
items of the contract and you can see
 

00:14:54.370 --> 00:14:56.280 align:start position:0%
items of the contract and you can see
that<00:14:54.550><c> how</c><00:14:54.940><c> contract</c><00:14:55.570><c> was</c><00:14:55.720><c> created</c><00:14:56.140><c> and</c>

00:14:56.280 --> 00:14:56.290 align:start position:0%
that how contract was created and
 

00:14:56.290 --> 00:14:57.720 align:start position:0%
that how contract was created and
storage<00:14:56.560><c> has</c><00:14:56.680><c> been</c><00:14:56.830><c> modified</c><00:14:57.070><c> blah</c><00:14:57.460><c> blah</c><00:14:57.580><c> blah</c>

00:14:57.720 --> 00:14:57.730 align:start position:0%
storage has been modified blah blah blah
 

00:14:57.730 --> 00:14:59.400 align:start position:0%
storage has been modified blah blah blah
and<00:14:57.940><c> then</c><00:14:58.330><c> we</c><00:14:58.540><c> go</c><00:14:58.660><c> to</c><00:14:58.720><c> the</c><00:14:58.870><c> point</c><00:14:59.050><c> where</c><00:14:59.260><c> he</c><00:14:59.320><c> got</c>

00:14:59.400 --> 00:14:59.410 align:start position:0%
and then we go to the point where he got
 

00:14:59.410 --> 00:15:01.050 align:start position:0%
and then we go to the point where he got
self<00:14:59.680><c> destructed</c><00:15:00.130><c> and</c><00:15:00.280><c> you</c><00:15:00.640><c> got</c><00:15:00.790><c> all</c><00:15:00.910><c> these</c>

00:15:01.050 --> 00:15:01.060 align:start position:0%
self destructed and you got all these
 

00:15:01.060 --> 00:15:04.350 align:start position:0%
self destructed and you got all these
red<00:15:01.240><c> things</c><00:15:01.270><c> and</c><00:15:01.990><c> then</c><00:15:02.440><c> later</c><00:15:02.770><c> on</c><00:15:02.950><c> in</c><00:15:03.370><c> like</c>

00:15:04.350 --> 00:15:04.360 align:start position:0%
red things and then later on in like
 

00:15:04.360 --> 00:15:05.670 align:start position:0%
red things and then later on in like
three<00:15:04.600><c> blocks</c><00:15:04.810><c> later</c><00:15:05.020><c> it's</c><00:15:05.260><c> been</c><00:15:05.350><c> recreated</c>

00:15:05.670 --> 00:15:05.680 align:start position:0%
three blocks later it's been recreated
 

00:15:05.680 --> 00:15:07.830 align:start position:0%
three blocks later it's been recreated
using<00:15:05.980><c> crate</c><00:15:06.460><c> to</c><00:15:06.670><c> with</c><00:15:07.150><c> the</c><00:15:07.240><c> same</c><00:15:07.390><c> code</c><00:15:07.660><c> or</c>

00:15:07.830 --> 00:15:07.840 align:start position:0%
using crate to with the same code or
 

00:15:07.840 --> 00:15:09.540 align:start position:0%
using crate to with the same code or
with<00:15:07.990><c> a</c><00:15:08.020><c> different</c><00:15:08.380><c> code</c><00:15:08.560><c> but</c><00:15:09.160><c> with</c><00:15:09.310><c> the</c><00:15:09.370><c> same</c>

00:15:09.540 --> 00:15:09.550 align:start position:0%
with a different code but with the same
 

00:15:09.550 --> 00:15:12.060 align:start position:0%
with a different code but with the same
init<00:15:09.790><c> code</c><00:15:09.970><c> and</c><00:15:10.180><c> then</c><00:15:10.810><c> after</c><00:15:11.080><c> that</c><00:15:11.200><c> you</c>

00:15:12.060 --> 00:15:12.070 align:start position:0%
init code and then after that you
 

00:15:12.070 --> 00:15:14.430 align:start position:0%
init code and then after that you
supposed<00:15:12.460><c> to</c><00:15:12.610><c> so</c><00:15:13.120><c> it's</c><00:15:13.480><c> assumed</c><00:15:13.840><c> that</c><00:15:13.960><c> now</c><00:15:14.200><c> at</c>

00:15:14.430 --> 00:15:14.440 align:start position:0%
supposed to so it's assumed that now at
 

00:15:14.440 --> 00:15:17.430 align:start position:0%
supposed to so it's assumed that now at
this<00:15:14.560><c> point</c><00:15:14.920><c> then</c><00:15:15.330><c> the</c><00:15:16.330><c> the</c><00:15:17.050><c> storage</c><00:15:17.350><c> is</c>

00:15:17.430 --> 00:15:17.440 align:start position:0%
this point then the the storage is
 

00:15:17.440 --> 00:15:19.350 align:start position:0%
this point then the the storage is
cleared<00:15:17.800><c> and</c><00:15:17.980><c> balance</c><00:15:18.490><c> is</c><00:15:18.610><c> cleared</c><00:15:18.910><c> so</c><00:15:19.210><c> this</c>

00:15:19.350 --> 00:15:19.360 align:start position:0%
cleared and balance is cleared so this
 

00:15:19.360 --> 00:15:21.390 align:start position:0%
cleared and balance is cleared so this
is<00:15:19.480><c> completely</c><00:15:19.810><c> empty</c><00:15:20.020><c> contract</c><00:15:20.530><c> and</c><00:15:20.890><c> now</c><00:15:21.340><c> you</c>

00:15:21.390 --> 00:15:21.400 align:start position:0%
is completely empty contract and now you
 

00:15:21.400 --> 00:15:23.610 align:start position:0%
is completely empty contract and now you
can<00:15:21.640><c> start</c><00:15:21.820><c> again</c><00:15:21.940><c> so</c><00:15:22.630><c> the</c><00:15:22.990><c> problem</c><00:15:23.290><c> for</c><00:15:23.320><c> super</c>

00:15:23.610 --> 00:15:23.620 align:start position:0%
can start again so the problem for super
 

00:15:23.620 --> 00:15:24.990 align:start position:0%
can start again so the problem for super
guest<00:15:23.770><c> is</c><00:15:23.920><c> that</c><00:15:24.070><c> because</c><00:15:24.370><c> it</c><00:15:24.490><c> doesn't</c><00:15:24.790><c> store</c>

00:15:24.990 --> 00:15:25.000 align:start position:0%
guest is that because it doesn't store
 

00:15:25.000 --> 00:15:27.420 align:start position:0%
guest is that because it doesn't store
the<00:15:25.210><c> state</c><00:15:25.900><c> as</c><00:15:26.080><c> a</c><00:15:26.110><c> tree</c><00:15:26.380><c> but</c><00:15:26.620><c> rather</c><00:15:26.860><c> in</c><00:15:27.160><c> this</c>

00:15:27.420 --> 00:15:27.430 align:start position:0%
the state as a tree but rather in this
 

00:15:27.430 --> 00:15:30.390 align:start position:0%
the state as a tree but rather in this
relational<00:15:27.970><c> way</c><00:15:28.120><c> it</c><00:15:28.780><c> has</c><00:15:29.140><c> to</c><00:15:29.290><c> either</c><00:15:29.500><c> insert</c>

00:15:30.390 --> 00:15:30.400 align:start position:0%
relational way it has to either insert
 

00:15:30.400 --> 00:15:32.190 align:start position:0%
relational way it has to either insert
all<00:15:30.640><c> these</c><00:15:30.790><c> red</c><00:15:31.030><c> bubbles</c><00:15:31.420><c> into</c><00:15:31.630><c> into</c><00:15:32.110><c> the</c>

00:15:32.190 --> 00:15:32.200 align:start position:0%
all these red bubbles into into the
 

00:15:32.200 --> 00:15:34.190 align:start position:0%
all these red bubbles into into the
database<00:15:32.530><c> which</c><00:15:32.740><c> could</c><00:15:32.950><c> be</c><00:15:33.100><c> in</c><00:15:33.490><c> millions</c>

00:15:34.190 --> 00:15:34.200 align:start position:0%
database which could be in millions
 

00:15:34.200 --> 00:15:35.860 align:start position:0%
database which could be in millions
potentially

00:15:35.860 --> 00:15:35.870 align:start position:0%
potentially
 

00:15:35.870 --> 00:15:38.500 align:start position:0%
potentially
at<00:15:35.990><c> the</c><00:15:36.470><c> point</c><00:15:36.710><c> of</c><00:15:36.830><c> self-destruction</c><00:15:37.180><c> or</c><00:15:38.180><c> it</c>

00:15:38.500 --> 00:15:38.510 align:start position:0%
at the point of self-destruction or it
 

00:15:38.510 --> 00:15:42.070 align:start position:0%
at the point of self-destruction or it
has<00:15:38.690><c> to</c><00:15:38.720><c> apply</c><00:15:39.170><c> much</c><00:15:39.580><c> more</c><00:15:40.580><c> more</c><00:15:41.029><c> in</c><00:15:41.510><c> nuanced</c>

00:15:42.070 --> 00:15:42.080 align:start position:0%
has to apply much more more in nuanced
 

00:15:42.080 --> 00:15:44.560 align:start position:0%
has to apply much more more in nuanced
way<00:15:42.710><c> when</c><00:15:43.040><c> you</c><00:15:43.190><c> actually</c><00:15:43.490><c> fetch</c><00:15:43.910><c> the</c><00:15:44.150><c> contract</c>

00:15:44.560 --> 00:15:44.570 align:start position:0%
way when you actually fetch the contract
 

00:15:44.570 --> 00:15:48.310 align:start position:0%
way when you actually fetch the contract
item<00:15:45.260><c> so</c><00:15:45.440><c> the</c><00:15:46.190><c> alternative</c><00:15:46.880><c> would</c><00:15:47.210><c> be</c><00:15:47.270><c> to</c><00:15:47.570><c> like</c>

00:15:48.310 --> 00:15:48.320 align:start position:0%
item so the alternative would be to like
 

00:15:48.320 --> 00:15:49.840 align:start position:0%
item so the alternative would be to like
whenever<00:15:48.920><c> anybody</c><00:15:49.339><c> asked</c><00:15:49.460><c> me</c><00:15:49.610><c> for</c><00:15:49.790><c> the</c>

00:15:49.840 --> 00:15:49.850 align:start position:0%
whenever anybody asked me for the
 

00:15:49.850 --> 00:15:51.579 align:start position:0%
whenever anybody asked me for the
contract<00:15:50.240><c> storage</c><00:15:50.540><c> I</c><00:15:50.720><c> would</c><00:15:50.900><c> have</c><00:15:51.080><c> to</c><00:15:51.260><c> also</c>

00:15:51.579 --> 00:15:51.589 align:start position:0%
contract storage I would have to also
 

00:15:51.589 --> 00:15:54.340 align:start position:0%
contract storage I would have to also
check<00:15:52.040><c> whether</c><00:15:52.700><c> the</c><00:15:52.910><c> contract</c><00:15:53.300><c> has</c><00:15:53.839><c> been</c><00:15:53.870><c> self</c>

00:15:54.340 --> 00:15:54.350 align:start position:0%
check whether the contract has been self
 

00:15:54.350 --> 00:15:55.810 align:start position:0%
check whether the contract has been self
destructed<00:15:54.830><c> in</c><00:15:54.890><c> the</c><00:15:54.950><c> past</c><00:15:55.160><c> and</c><00:15:55.430><c> when</c><00:15:55.610><c> there</c>

00:15:55.810 --> 00:15:55.820 align:start position:0%
destructed in the past and when there
 

00:15:55.820 --> 00:15:57.760 align:start position:0%
destructed in the past and when there
was<00:15:55.970><c> the</c><00:15:56.029><c> last</c><00:15:56.150><c> time</c><00:15:56.390><c> so</c><00:15:56.960><c> it's</c><00:15:57.080><c> more</c><00:15:57.260><c> searching</c>

00:15:57.760 --> 00:15:57.770 align:start position:0%
was the last time so it's more searching
 

00:15:57.770 --> 00:15:59.380 align:start position:0%
was the last time so it's more searching
I<00:15:57.860><c> can</c><00:15:58.010><c> implement</c><00:15:58.250><c> it</c><00:15:58.520><c> but</c><00:15:58.640><c> it's</c><00:15:58.850><c> kind</c><00:15:59.060><c> of</c><00:15:59.240><c> a</c>

00:15:59.380 --> 00:15:59.390 align:start position:0%
I can implement it but it's kind of a
 

00:15:59.390 --> 00:16:03.250 align:start position:0%
I can implement it but it's kind of a
bit<00:15:59.570><c> hustle</c><00:16:00.140><c> now</c><00:16:01.120><c> so</c><00:16:02.120><c> this</c><00:16:02.210><c> is</c><00:16:02.360><c> this</c><00:16:02.930><c> is</c><00:16:03.080><c> highly</c>

00:16:03.250 --> 00:16:03.260 align:start position:0%
bit hustle now so this is this is highly
 

00:16:03.260 --> 00:16:06.010 align:start position:0%
bit hustle now so this is this is highly
experimental<00:16:03.770><c> this</c><00:16:04.250><c> is</c><00:16:04.370><c> a</c><00:16:04.720><c> this</c><00:16:05.720><c> is</c><00:16:05.900><c> something</c>

00:16:06.010 --> 00:16:06.020 align:start position:0%
experimental this is a this is something
 

00:16:06.020 --> 00:16:08.050 align:start position:0%
experimental this is a this is something
that<00:16:06.230><c> I</c><00:16:06.380><c> came</c><00:16:07.220><c> up</c><00:16:07.279><c> with</c><00:16:07.580><c> when</c><00:16:07.730><c> I</c><00:16:07.760><c> was</c><00:16:07.940><c> thinking</c>

00:16:08.050 --> 00:16:08.060 align:start position:0%
that I came up with when I was thinking
 

00:16:08.060 --> 00:16:09.310 align:start position:0%
that I came up with when I was thinking
about<00:16:08.270><c> all</c><00:16:08.480><c> these</c><00:16:08.570><c> problems</c><00:16:08.930><c> that</c><00:16:09.080><c> with</c><00:16:09.260><c> the</c>

00:16:09.310 --> 00:16:09.320 align:start position:0%
about all these problems that with the
 

00:16:09.320 --> 00:16:11.590 align:start position:0%
about all these problems that with the
light<00:16:09.500><c> clients</c><00:16:09.980><c> and</c><00:16:10.160><c> with</c><00:16:10.279><c> the</c><00:16:10.460><c> with</c><00:16:11.390><c> the</c>

00:16:11.590 --> 00:16:11.600 align:start position:0%
light clients and with the with the
 

00:16:11.600 --> 00:16:13.720 align:start position:0%
light clients and with the with the
create<00:16:11.990><c> two</c><00:16:12.200><c> and</c><00:16:12.529><c> at</c><00:16:12.620><c> the</c><00:16:12.710><c> same</c><00:16:12.860><c> time</c><00:16:13.100><c> I</c><00:16:13.310><c> was</c><00:16:13.490><c> I</c>

00:16:13.720 --> 00:16:13.730 align:start position:0%
create two and at the same time I was I
 

00:16:13.730 --> 00:16:15.190 align:start position:0%
create two and at the same time I was I
was<00:16:13.850><c> working</c><00:16:14.029><c> with</c><00:16:14.270><c> the</c><00:16:14.360><c> ether</c><00:16:14.510><c> main</c><00:16:14.750><c> team</c><00:16:14.990><c> and</c>

00:16:15.190 --> 00:16:15.200 align:start position:0%
was working with the ether main team and
 

00:16:15.200 --> 00:16:17.500 align:start position:0%
was working with the ether main team and
they<00:16:15.710><c> basically</c><00:16:16.040><c> we</c><00:16:16.550><c> did</c><00:16:16.880><c> some</c><00:16:17.029><c> tests</c><00:16:17.270><c> with</c>

00:16:17.500 --> 00:16:17.510 align:start position:0%
they basically we did some tests with
 

00:16:17.510 --> 00:16:19.600 align:start position:0%
they basically we did some tests with
the<00:16:17.690><c> load-in</c><00:16:18.500><c> even</c><00:16:18.980><c> transaction</c><00:16:19.400><c> at</c><00:16:19.490><c> either</c>

00:16:19.600 --> 00:16:19.610 align:start position:0%
the load-in even transaction at either
 

00:16:19.610 --> 00:16:22.090 align:start position:0%
the load-in even transaction at either
mint<00:16:19.910><c> and</c><00:16:20.089><c> it</c><00:16:20.210><c> turns</c><00:16:20.390><c> out</c><00:16:20.570><c> to</c><00:16:21.080><c> be</c><00:16:21.110><c> a</c><00:16:21.500><c> bit</c><00:16:21.890><c> slow</c>

00:16:22.090 --> 00:16:22.100 align:start position:0%
mint and it turns out to be a bit slow
 

00:16:22.100 --> 00:16:24.070 align:start position:0%
mint and it turns out to be a bit slow
so<00:16:22.730><c> I</c><00:16:22.760><c> said</c><00:16:22.970><c> we</c><00:16:23.089><c> need</c><00:16:23.210><c> to</c><00:16:23.330><c> be</c><00:16:23.450><c> we</c><00:16:23.720><c> need</c><00:16:23.750><c> to</c><00:16:23.870><c> get</c>

00:16:24.070 --> 00:16:24.080 align:start position:0%
so I said we need to be we need to get
 

00:16:24.080 --> 00:16:27.400 align:start position:0%
so I said we need to be we need to get
faster<00:16:24.589><c> with</c><00:16:24.800><c> that</c><00:16:24.980><c> and</c><00:16:25.339><c> so</c><00:16:26.300><c> the</c><00:16:26.839><c> idea</c><00:16:27.200><c> is</c><00:16:27.380><c> to</c>

00:16:27.400 --> 00:16:27.410 align:start position:0%
faster with that and so the idea is to
 

00:16:27.410 --> 00:16:30.040 align:start position:0%
faster with that and so the idea is to
actually<00:16:27.800><c> create</c><00:16:28.730><c> a</c><00:16:28.760><c> specialized</c><00:16:29.630><c> database</c>

00:16:30.040 --> 00:16:30.050 align:start position:0%
actually create a specialized database
 

00:16:30.050 --> 00:16:33.519 align:start position:0%
actually create a specialized database
that<00:16:30.860><c> would</c><00:16:31.130><c> allow</c><00:16:31.430><c> these</c><00:16:32.420><c> few</c><00:16:32.690><c> desirable</c>

00:16:33.519 --> 00:16:33.529 align:start position:0%
that would allow these few desirable
 

00:16:33.529 --> 00:16:37.740 align:start position:0%
that would allow these few desirable
things<00:16:33.770><c> and</c><00:16:34.130><c> I</c><00:16:35.089><c> will</c><00:16:35.270><c> explain</c><00:16:35.690><c> why</c><00:16:36.020><c> they</c><00:16:36.470><c> are</c>

00:16:37.740 --> 00:16:37.750 align:start position:0%
things and I will explain why they are
 

00:16:37.750 --> 00:16:39.970 align:start position:0%
things and I will explain why they are
they<00:16:38.750><c> might</c><00:16:38.960><c> be</c><00:16:39.140><c> good</c><00:16:39.320><c> it's</c><00:16:39.740><c> still</c><00:16:39.800><c> very</c>

00:16:39.970 --> 00:16:39.980 align:start position:0%
they might be good it's still very
 

00:16:39.980 --> 00:16:42.430 align:start position:0%
they might be good it's still very
experimental<00:16:40.430><c> so</c><00:16:40.760><c> it's</c><00:16:41.120><c> it</c><00:16:41.420><c> could</c><00:16:41.630><c> also</c><00:16:41.870><c> it</c>

00:16:42.430 --> 00:16:42.440 align:start position:0%
experimental so it's it could also it
 

00:16:42.440 --> 00:16:44.260 align:start position:0%
experimental so it's it could also it
turned<00:16:43.190><c> out</c><00:16:43.310><c> to</c><00:16:43.520><c> be</c><00:16:43.550><c> a</c><00:16:43.640><c> different</c><00:16:44.089><c> way</c><00:16:44.209><c> so</c>

00:16:44.260 --> 00:16:44.270 align:start position:0%
turned out to be a different way so
 

00:16:44.270 --> 00:16:46.329 align:start position:0%
turned out to be a different way so
although<00:16:45.020><c> I</c><00:16:45.140><c> did</c><00:16:45.440><c> some</c><00:16:45.620><c> proof</c><00:16:45.800><c> of</c><00:16:45.860><c> concept</c><00:16:46.220><c> on</c>

00:16:46.329 --> 00:16:46.339 align:start position:0%
although I did some proof of concept on
 

00:16:46.339 --> 00:16:47.769 align:start position:0%
although I did some proof of concept on
this<00:16:46.430><c> I</c><00:16:46.580><c> will</c><00:16:46.730><c> tell</c><00:16:46.910><c> you</c><00:16:47.060><c> roughly</c><00:16:47.510><c> what</c><00:16:47.600><c> the</c>

00:16:47.769 --> 00:16:47.779 align:start position:0%
this I will tell you roughly what the
 

00:16:47.779 --> 00:16:51.040 align:start position:0%
this I will tell you roughly what the
results<00:16:48.290><c> were</c><00:16:48.410><c> so</c><00:16:48.920><c> let's</c><00:16:49.100><c> get</c><00:16:49.250><c> into</c><00:16:49.610><c> them</c><00:16:50.050><c> the</c>

00:16:51.040 --> 00:16:51.050 align:start position:0%
results were so let's get into them the
 

00:16:51.050 --> 00:16:54.430 align:start position:0%
results were so let's get into them the
details<00:16:51.290><c> of</c><00:16:51.650><c> that</c><00:16:51.800><c> so</c><00:16:52.490><c> as</c><00:16:53.180><c> you</c><00:16:53.420><c> know</c><00:16:53.630><c> again</c><00:16:54.170><c> as</c>

00:16:54.430 --> 00:16:54.440 align:start position:0%
details of that so as you know again as
 

00:16:54.440 --> 00:16:56.079 align:start position:0%
details of that so as you know again as
I<00:16:54.620><c> told</c><00:16:54.770><c> you</c><00:16:54.980><c> before</c><00:16:55.100><c> as</c><00:16:55.370><c> well</c><00:16:55.520><c> the</c><00:16:55.760><c> the</c>

00:16:56.079 --> 00:16:56.089 align:start position:0%
I told you before as well the the
 

00:16:56.089 --> 00:16:58.090 align:start position:0%
I told you before as well the the
theorem<00:16:56.839><c> currently</c><00:16:57.230><c> uses</c><00:16:57.470><c> petruchio</c><00:16:57.890><c> tree</c>

00:16:58.090 --> 00:16:58.100 align:start position:0%
theorem currently uses petruchio tree
 

00:16:58.100 --> 00:17:01.630 align:start position:0%
theorem currently uses petruchio tree
for<00:16:58.820><c> miracle</c><00:16:59.180><c> ization</c><00:16:59.420><c> but</c><00:17:00.140><c> also</c><00:17:00.400><c> it's</c><00:17:01.400><c> it's</c>

00:17:01.630 --> 00:17:01.640 align:start position:0%
for miracle ization but also it's it's
 

00:17:01.640 --> 00:17:04.929 align:start position:0%
for miracle ization but also it's it's
it's<00:17:02.500><c> before</c><00:17:03.500><c> inserting</c><00:17:03.890><c> every</c><00:17:04.280><c> anything</c><00:17:04.699><c> in</c>

00:17:04.929 --> 00:17:04.939 align:start position:0%
it's before inserting every anything in
 

00:17:04.939 --> 00:17:06.640 align:start position:0%
it's before inserting every anything in
the<00:17:05.000><c> pituitary</c><00:17:05.270><c> it</c><00:17:05.750><c> also</c><00:17:05.929><c> applies</c><00:17:06.319><c> the</c><00:17:06.500><c> hash</c>

00:17:06.640 --> 00:17:06.650 align:start position:0%
the pituitary it also applies the hash
 

00:17:06.650 --> 00:17:09.220 align:start position:0%
the pituitary it also applies the hash
function<00:17:06.829><c> to</c><00:17:07.189><c> the</c><00:17:07.309><c> key</c><00:17:07.630><c> so</c><00:17:08.630><c> the</c><00:17:08.809><c> keys</c><00:17:08.990><c> are</c><00:17:09.020><c> not</c>

00:17:09.220 --> 00:17:09.230 align:start position:0%
function to the key so the keys are not
 

00:17:09.230 --> 00:17:11.380 align:start position:0%
function to the key so the keys are not
just<00:17:09.470><c> inserted</c><00:17:09.860><c> as</c><00:17:09.980><c> they</c><00:17:10.130><c> are</c><00:17:10.309><c> and</c><00:17:10.699><c> this</c><00:17:11.240><c> is</c>

00:17:11.380 --> 00:17:11.390 align:start position:0%
just inserted as they are and this is
 

00:17:11.390 --> 00:17:15.490 align:start position:0%
just inserted as they are and this is
because<00:17:11.720><c> in</c><00:17:11.990><c> beckon</c><00:17:12.620><c> mm</c><00:17:13.220><c> whenever</c><00:17:13.720><c> 15</c><00:17:14.720><c> I</c><00:17:15.290><c> think</c>

00:17:15.490 --> 00:17:15.500 align:start position:0%
because in beckon mm whenever 15 I think
 

00:17:15.500 --> 00:17:17.620 align:start position:0%
because in beckon mm whenever 15 I think
when<00:17:15.829><c> when</c><00:17:16.490><c> there</c><00:17:16.730><c> was</c><00:17:16.819><c> a</c><00:17:16.850><c> security</c><00:17:17.120><c> audit</c><00:17:17.510><c> of</c>

00:17:17.620 --> 00:17:17.630 align:start position:0%
when when there was a security audit of
 

00:17:17.630 --> 00:17:19.870 align:start position:0%
when when there was a security audit of
a<00:17:17.720><c> serum</c><00:17:18.079><c> something</c><00:17:18.500><c> pointed</c><00:17:19.309><c> out</c><00:17:19.400><c> by</c><00:17:19.550><c> Andrew</c>

00:17:19.870 --> 00:17:19.880 align:start position:0%
a serum something pointed out by Andrew
 

00:17:19.880 --> 00:17:22.870 align:start position:0%
a serum something pointed out by Andrew
Miller<00:17:20.290><c> that</c><00:17:21.290><c> you</c><00:17:21.589><c> could</c><00:17:21.770><c> actually</c><00:17:21.949><c> create</c><00:17:22.850><c> a</c>

00:17:22.870 --> 00:17:22.880 align:start position:0%
Miller that you could actually create a
 

00:17:22.880 --> 00:17:26.679 align:start position:0%
Miller that you could actually create a
very<00:17:23.559><c> very</c><00:17:24.559><c> long</c><00:17:24.860><c> branches</c><00:17:25.610><c> in</c><00:17:25.760><c> that</c><00:17:25.910><c> tree</c>

00:17:26.679 --> 00:17:26.689 align:start position:0%
very very long branches in that tree
 

00:17:26.689 --> 00:17:28.630 align:start position:0%
very very long branches in that tree
but<00:17:27.439><c> attacker</c><00:17:27.829><c> could</c><00:17:28.040><c> do</c><00:17:28.220><c> that</c><00:17:28.339><c> and</c><00:17:28.550><c> I'm</c>

00:17:28.630 --> 00:17:28.640 align:start position:0%
but attacker could do that and I'm
 

00:17:28.640 --> 00:17:30.220 align:start position:0%
but attacker could do that and I'm
basically<00:17:29.270><c> introduced</c><00:17:29.630><c> some</c><00:17:29.780><c> some</c><00:17:30.050><c> bad</c>

00:17:30.220 --> 00:17:30.230 align:start position:0%
basically introduced some some bad
 

00:17:30.230 --> 00:17:30.700 align:start position:0%
basically introduced some some bad
things

00:17:30.700 --> 00:17:30.710 align:start position:0%
things
 

00:17:30.710 --> 00:17:32.890 align:start position:0%
things
so<00:17:31.190><c> as</c><00:17:31.670><c> the</c><00:17:31.880><c> mitigation</c><00:17:32.450><c> it</c><00:17:32.600><c> has</c><00:17:32.750><c> been</c>

00:17:32.890 --> 00:17:32.900 align:start position:0%
so as the mitigation it has been
 

00:17:32.900 --> 00:17:34.900 align:start position:0%
so as the mitigation it has been
suggested<00:17:33.050><c> to</c><00:17:33.500><c> hush</c><00:17:33.830><c> all</c><00:17:34.100><c> the</c><00:17:34.250><c> keys</c><00:17:34.490><c> before</c>

00:17:34.900 --> 00:17:34.910 align:start position:0%
suggested to hush all the keys before
 

00:17:34.910 --> 00:17:36.640 align:start position:0%
suggested to hush all the keys before
inserting<00:17:35.360><c> them</c><00:17:35.660><c> into</c><00:17:35.750><c> the</c><00:17:35.990><c> patricia</c><00:17:36.410><c> tree</c>

00:17:36.640 --> 00:17:36.650 align:start position:0%
inserting them into the patricia tree
 

00:17:36.650 --> 00:17:39.850 align:start position:0%
inserting them into the patricia tree
and<00:17:36.980><c> the</c><00:17:37.850><c> idea</c><00:17:38.809><c> is</c><00:17:38.900><c> that</c><00:17:38.929><c> it</c><00:17:39.200><c> would</c><00:17:39.470><c> kind</c><00:17:39.770><c> of</c>

00:17:39.850 --> 00:17:39.860 align:start position:0%
and the idea is that it would kind of
 

00:17:39.860 --> 00:17:42.850 align:start position:0%
and the idea is that it would kind of
balance<00:17:40.130><c> them</c><00:17:40.309><c> out</c><00:17:40.429><c> there</c><00:17:41.300><c> is</c><00:17:41.420><c> a</c><00:17:41.590><c> it</c><00:17:42.590><c> still</c>

00:17:42.850 --> 00:17:42.860 align:start position:0%
balance them out there is a it still
 

00:17:42.860 --> 00:17:44.320 align:start position:0%
balance them out there is a it still
doesn't<00:17:43.100><c> completely</c><00:17:43.550><c> solve</c><00:17:43.730><c> the</c><00:17:43.820><c> problem</c><00:17:44.120><c> but</c>

00:17:44.320 --> 00:17:44.330 align:start position:0%
doesn't completely solve the problem but
 

00:17:44.330 --> 00:17:45.970 align:start position:0%
doesn't completely solve the problem but
we're<00:17:44.570><c> not</c><00:17:44.780><c> going</c><00:17:44.960><c> to</c><00:17:45.050><c> touch</c><00:17:45.320><c> it</c><00:17:45.350><c> right</c><00:17:45.530><c> now</c>

00:17:45.970 --> 00:17:45.980 align:start position:0%
we're not going to touch it right now
 

00:17:45.980 --> 00:17:49.030 align:start position:0%
we're not going to touch it right now
so<00:17:46.580><c> for</c><00:17:47.030><c> the</c><00:17:47.120><c> serum</c><00:17:47.390><c> 2.0</c><00:17:48.290><c> for</c><00:17:48.500><c> example</c><00:17:48.860><c> there's</c>

00:17:49.030 --> 00:17:49.040 align:start position:0%
so for the serum 2.0 for example there's
 

00:17:49.040 --> 00:17:49.690 align:start position:0%
so for the serum 2.0 for example there's
also

00:17:49.690 --> 00:17:49.700 align:start position:0%
also
 

00:17:49.700 --> 00:17:51.610 align:start position:0%
also
of<00:17:50.120><c> sparse</c><00:17:50.570><c> miracle</c><00:17:50.930><c> tree</c><00:17:51.110><c> which</c><00:17:51.590><c> is</c>

00:17:51.610 --> 00:17:51.620 align:start position:0%
of sparse miracle tree which is
 

00:17:51.620 --> 00:17:53.740 align:start position:0%
of sparse miracle tree which is
essentially<00:17:52.370><c> also</c><00:17:52.580><c> radix</c><00:17:53.090><c> tree</c><00:17:53.360><c> but</c><00:17:53.570><c> with</c><00:17:53.720><c> a</c>

00:17:53.740 --> 00:17:53.750 align:start position:0%
essentially also radix tree but with a
 

00:17:53.750 --> 00:17:55.810 align:start position:0%
essentially also radix tree but with a
different<00:17:54.080><c> radix</c><00:17:54.350><c> instead</c><00:17:54.890><c> of</c><00:17:54.980><c> radix</c><00:17:55.250><c> 16</c><00:17:55.670><c> they</c>

00:17:55.810 --> 00:17:55.820 align:start position:0%
different radix instead of radix 16 they
 

00:17:55.820 --> 00:17:58.570 align:start position:0%
different radix instead of radix 16 they
use<00:17:55.970><c> radix</c><00:17:56.330><c> 2</c><00:17:56.810><c> and</c><00:17:57.050><c> but</c><00:17:57.920><c> the</c><00:17:58.010><c> idea</c><00:17:58.280><c> is</c><00:17:58.370><c> very</c>

00:17:58.570 --> 00:17:58.580 align:start position:0%
use radix 2 and but the idea is very
 

00:17:58.580 --> 00:18:01.210 align:start position:0%
use radix 2 and but the idea is very
similar<00:17:58.910><c> and</c><00:17:59.530><c> for</c><00:18:00.530><c> the</c><00:18:00.620><c> same</c><00:18:00.800><c> exact</c><00:18:01.130><c> reason</c>

00:18:01.210 --> 00:18:01.220 align:start position:0%
similar and for the same exact reason
 

00:18:01.220 --> 00:18:04.660 align:start position:0%
similar and for the same exact reason
the<00:18:01.940><c> keys</c><00:18:02.210><c> will</c><00:18:02.420><c> have</c><00:18:02.570><c> to</c><00:18:02.690><c> be</c><00:18:02.810><c> hashed</c><00:18:03.020><c> and</c><00:18:03.670><c> the</c>

00:18:04.660 --> 00:18:04.670 align:start position:0%
the keys will have to be hashed and the
 

00:18:04.670 --> 00:18:06.340 align:start position:0%
the keys will have to be hashed and the
reason<00:18:04.910><c> I</c><00:18:05.000><c> don't</c><00:18:05.300><c> like</c><00:18:05.480><c> the</c><00:18:05.630><c> hash</c><00:18:05.810><c> keys</c><00:18:06.140><c> is</c>

00:18:06.340 --> 00:18:06.350 align:start position:0%
reason I don't like the hash keys is
 

00:18:06.350 --> 00:18:10.000 align:start position:0%
reason I don't like the hash keys is
firstly<00:18:06.740><c> because</c><00:18:07.190><c> I</c><00:18:07.430><c> believe</c><00:18:08.000><c> that</c><00:18:08.030><c> the</c><00:18:09.010><c> the</c>

00:18:10.000 --> 00:18:10.010 align:start position:0%
firstly because I believe that the the
 

00:18:10.010 --> 00:18:11.770 align:start position:0%
firstly because I believe that the the
problem<00:18:10.340><c> pointed</c><00:18:10.670><c> out</c><00:18:10.760><c> insecurity</c><00:18:11.330><c> or</c><00:18:11.450><c> it</c><00:18:11.600><c> has</c>

00:18:11.770 --> 00:18:11.780 align:start position:0%
problem pointed out insecurity or it has
 

00:18:11.780 --> 00:18:13.930 align:start position:0%
problem pointed out insecurity or it has
not<00:18:11.960><c> been</c><00:18:12.050><c> completely</c><00:18:12.440><c> resolved</c><00:18:12.950><c> and</c><00:18:13.130><c> it</c><00:18:13.760><c> will</c>

00:18:13.930 --> 00:18:13.940 align:start position:0%
not been completely resolved and it will
 

00:18:13.940 --> 00:18:16.570 align:start position:0%
not been completely resolved and it will
keep<00:18:14.600><c> persisting</c><00:18:14.990><c> if</c><00:18:15.410><c> we</c><00:18:15.650><c> stick</c><00:18:16.400><c> with</c><00:18:16.430><c> a</c>

00:18:16.570 --> 00:18:16.580 align:start position:0%
keep persisting if we stick with a
 

00:18:16.580 --> 00:18:19.090 align:start position:0%
keep persisting if we stick with a
sparse<00:18:16.880><c> Merkle</c><00:18:17.210><c> trees</c><00:18:17.390><c> and</c><00:18:17.690><c> also</c><00:18:18.140><c> you</c><00:18:18.890><c> also</c>

00:18:19.090 --> 00:18:19.100 align:start position:0%
sparse Merkle trees and also you also
 

00:18:19.100 --> 00:18:21.250 align:start position:0%
sparse Merkle trees and also you also
have<00:18:19.400><c> to</c><00:18:19.550><c> keep</c><00:18:19.670><c> pre</c><00:18:19.910><c> images</c><00:18:20.210><c> so</c><00:18:20.540><c> to</c><00:18:20.600><c> be</c><00:18:20.930><c> able</c><00:18:21.140><c> to</c>

00:18:21.250 --> 00:18:21.260 align:start position:0%
have to keep pre images so to be able to
 

00:18:21.260 --> 00:18:23.080 align:start position:0%
have to keep pre images so to be able to
each<00:18:21.380><c> rate</c><00:18:21.650><c> through</c><00:18:21.860><c> the</c><00:18:21.980><c> state</c><00:18:22.220><c> and</c><00:18:22.460><c> the</c>

00:18:23.080 --> 00:18:23.090 align:start position:0%
each rate through the state and the
 

00:18:23.090 --> 00:18:24.760 align:start position:0%
each rate through the state and the
perimeters<00:18:23.630><c> are</c><00:18:23.810><c> not</c><00:18:23.990><c> really</c><00:18:24.350><c> heavy</c><00:18:24.590><c> at</c><00:18:24.710><c> the</c>

00:18:24.760 --> 00:18:24.770 align:start position:0%
perimeters are not really heavy at the
 

00:18:24.770 --> 00:18:26.920 align:start position:0%
perimeters are not really heavy at the
moment<00:18:25.100><c> but</c><00:18:25.190><c> in</c><00:18:25.640><c> I</c><00:18:26.000><c> just</c><00:18:26.180><c> chopped</c><00:18:26.480><c> a</c><00:18:26.630><c> bit</c><00:18:26.780><c> out</c>

00:18:26.920 --> 00:18:26.930 align:start position:0%
moment but in I just chopped a bit out
 

00:18:26.930 --> 00:18:31.300 align:start position:0%
moment but in I just chopped a bit out
of<00:18:26.960><c> the</c><00:18:27.170><c> diagram</c><00:18:27.500><c> it's</c><00:18:27.650><c> but</c><00:18:28.220><c> 15</c><00:18:29.180><c> gigs</c><00:18:30.130><c> so</c><00:18:31.130><c> what</c>

00:18:31.300 --> 00:18:31.310 align:start position:0%
of the diagram it's but 15 gigs so what
 

00:18:31.310 --> 00:18:33.910 align:start position:0%
of the diagram it's but 15 gigs so what
have<00:18:31.430><c> been</c><00:18:31.550><c> experimenting</c><00:18:32.300><c> with</c><00:18:32.770><c> and</c><00:18:33.770><c> of</c>

00:18:33.910 --> 00:18:33.920 align:start position:0%
have been experimenting with and of
 

00:18:33.920 --> 00:18:36.280 align:start position:0%
have been experimenting with and of
course<00:18:34.130><c> it's</c><00:18:34.310><c> it's</c><00:18:34.490><c> been</c><00:18:34.760><c> it's</c><00:18:34.790><c> been</c><00:18:35.120><c> a</c><00:18:35.290><c> it's</c>

00:18:36.280 --> 00:18:36.290 align:start position:0%
course it's it's been it's been a it's
 

00:18:36.290 --> 00:18:39.780 align:start position:0%
course it's it's been it's been a it's
been<00:18:36.470><c> inspired</c><00:18:36.860><c> by</c><00:18:36.950><c> the</c><00:18:37.100><c> by</c><00:18:37.610><c> the</c><00:18:37.670><c> fact</c><00:18:37.940><c> that</c>

00:18:39.780 --> 00:18:39.790 align:start position:0%
been inspired by the by the fact that
 

00:18:39.790 --> 00:18:43.600 align:start position:0%
been inspired by the by the fact that
that<00:18:40.790><c> that</c><00:18:41.480><c> either</c><00:18:42.080><c> mint</c><00:18:42.440><c> uses</c><00:18:42.770><c> the</c><00:18:42.950><c> AVL</c><00:18:43.370><c> trees</c>

00:18:43.600 --> 00:18:43.610 align:start position:0%
that that either mint uses the AVL trees
 

00:18:43.610 --> 00:18:45.700 align:start position:0%
that that either mint uses the AVL trees
looking<00:18:44.210><c> at</c><00:18:44.300><c> the</c><00:18:44.390><c> balance</c><00:18:44.510><c> in</c><00:18:44.780><c> trees</c><00:18:44.960><c> and</c><00:18:44.990><c> the</c>

00:18:45.700 --> 00:18:45.710 align:start position:0%
looking at the balance in trees and the
 

00:18:45.710 --> 00:18:47.860 align:start position:0%
looking at the balance in trees and the
main<00:18:45.860><c> objection</c><00:18:46.310><c> to</c><00:18:46.460><c> balance</c><00:18:46.700><c> in</c><00:18:46.820><c> trees</c><00:18:47.000><c> was</c>

00:18:47.860 --> 00:18:47.870 align:start position:0%
main objection to balance in trees was
 

00:18:47.870 --> 00:18:50.470 align:start position:0%
main objection to balance in trees was
that<00:18:48.400><c> the</c><00:18:49.400><c> order</c><00:18:49.730><c> of</c><00:18:49.850><c> insertion</c><00:18:50.090><c> and</c><00:18:50.450><c> deletion</c>

00:18:50.470 --> 00:18:50.480 align:start position:0%
that the order of insertion and deletion
 

00:18:50.480 --> 00:18:53.950 align:start position:0%
that the order of insertion and deletion
actually<00:18:51.080><c> matters</c><00:18:52.390><c> and</c><00:18:53.390><c> I've</c><00:18:53.510><c> been</c><00:18:53.720><c> looking</c>

00:18:53.950 --> 00:18:53.960 align:start position:0%
actually matters and I've been looking
 

00:18:53.960 --> 00:18:55.870 align:start position:0%
actually matters and I've been looking
at<00:18:54.200><c> not</c><00:18:54.380><c> only</c><00:18:54.410><c> AVL</c><00:18:55.010><c> trees</c><00:18:55.250><c> but</c><00:18:55.430><c> also</c><00:18:55.460><c> the</c><00:18:55.790><c> well</c>

00:18:55.870 --> 00:18:55.880 align:start position:0%
at not only AVL trees but also the well
 

00:18:55.880 --> 00:18:57.340 align:start position:0%
at not only AVL trees but also the well
weight<00:18:56.270><c> balance</c><00:18:56.600><c> tree</c><00:18:56.750><c> is</c><00:18:56.810><c> actually</c><00:18:56.990><c> really</c>

00:18:57.340 --> 00:18:57.350 align:start position:0%
weight balance tree is actually really
 

00:18:57.350 --> 00:18:59.470 align:start position:0%
weight balance tree is actually really
little<00:18:57.800><c> known</c><00:18:57.980><c> about</c><00:18:58.010><c> them</c><00:18:58.490><c> but</c><00:18:59.000><c> these</c><00:18:59.330><c> are</c>

00:18:59.470 --> 00:18:59.480 align:start position:0%
little known about them but these are
 

00:18:59.480 --> 00:19:00.640 align:start position:0%
little known about them but these are
the<00:18:59.570><c> structures</c><00:18:59.900><c> which</c><00:19:00.050><c> are</c><00:19:00.170><c> really</c><00:19:00.290><c> good</c><00:19:00.470><c> for</c>

00:19:00.640 --> 00:19:00.650 align:start position:0%
the structures which are really good for
 

00:19:00.650 --> 00:19:02.710 align:start position:0%
the structures which are really good for
functional<00:19:01.160><c> languages</c><00:19:01.520><c> for</c><00:19:01.760><c> some</c><00:19:02.030><c> reason</c><00:19:02.270><c> so</c>

00:19:02.710 --> 00:19:02.720 align:start position:0%
functional languages for some reason so
 

00:19:02.720 --> 00:19:04.240 align:start position:0%
functional languages for some reason so
actually<00:19:03.020><c> what</c><00:19:03.170><c> the</c><00:19:03.470><c> idea</c><00:19:03.740><c> is</c><00:19:03.800><c> that</c><00:19:03.950><c> ok</c><00:19:04.220><c> let's</c>

00:19:04.240 --> 00:19:04.250 align:start position:0%
actually what the idea is that ok let's
 

00:19:04.250 --> 00:19:06.430 align:start position:0%
actually what the idea is that ok let's
try<00:19:05.000><c> to</c><00:19:05.060><c> encode</c><00:19:05.450><c> the</c><00:19:05.660><c> structure</c><00:19:06.110><c> of</c><00:19:06.290><c> the</c>

00:19:06.430 --> 00:19:06.440 align:start position:0%
try to encode the structure of the
 

00:19:06.440 --> 00:19:08.350 align:start position:0%
try to encode the structure of the
industries<00:19:06.860><c> of</c><00:19:06.980><c> string</c><00:19:07.190><c> a</c><00:19:07.280><c> bit</c><00:19:07.460><c> so</c><00:19:08.090><c> this</c><00:19:08.210><c> is</c>

00:19:08.350 --> 00:19:08.360 align:start position:0%
industries of string a bit so this is
 

00:19:08.360 --> 00:19:09.640 align:start position:0%
industries of string a bit so this is
actually<00:19:08.750><c> you're</c><00:19:09.020><c> probably</c><00:19:09.200><c> going</c><00:19:09.440><c> to</c><00:19:09.500><c> look</c>

00:19:09.640 --> 00:19:09.650 align:start position:0%
actually you're probably going to look
 

00:19:09.650 --> 00:19:11.800 align:start position:0%
actually you're probably going to look
at<00:19:09.740><c> the</c><00:19:09.830><c> slides</c><00:19:10.040><c> later</c><00:19:10.250><c> but</c><00:19:10.550><c> so</c><00:19:11.060><c> this</c><00:19:11.450><c> is</c><00:19:11.600><c> to</c>

00:19:11.800 --> 00:19:11.810 align:start position:0%
at the slides later but so this is to
 

00:19:11.810 --> 00:19:14.890 align:start position:0%
at the slides later but so this is to
demonstrate<00:19:11.960><c> you</c><00:19:12.440><c> that</c><00:19:12.650><c> you</c><00:19:13.160><c> can</c><00:19:13.340><c> encode</c><00:19:13.900><c> the</c>

00:19:14.890 --> 00:19:14.900 align:start position:0%
demonstrate you that you can encode the
 

00:19:14.900 --> 00:19:17.230 align:start position:0%
demonstrate you that you can encode the
any<00:19:15.230><c> any</c><00:19:15.560><c> binary</c><00:19:15.800><c> tree</c><00:19:16.190><c> in</c><00:19:16.400><c> fact</c><00:19:16.700><c> into</c><00:19:17.120><c> the</c>

00:19:17.230 --> 00:19:17.240 align:start position:0%
any any binary tree in fact into the
 

00:19:17.240 --> 00:19:19.870 align:start position:0%
any any binary tree in fact into the
string<00:19:17.480><c> of</c><00:19:17.600><c> bits</c><00:19:17.780><c> with</c><00:19:18.530><c> the</c><00:19:18.560><c> cost</c><00:19:19.190><c> of</c><00:19:19.400><c> at</c><00:19:19.640><c> most</c>

00:19:19.870 --> 00:19:19.880 align:start position:0%
string of bits with the cost of at most
 

00:19:19.880 --> 00:19:22.420 align:start position:0%
string of bits with the cost of at most
2<00:19:20.240><c> bits</c><00:19:20.480><c> per</c><00:19:20.720><c> item</c><00:19:20.990><c> and</c><00:19:21.320><c> then</c><00:19:21.830><c> decode</c><00:19:22.220><c> them</c>

00:19:22.420 --> 00:19:22.430 align:start position:0%
2 bits per item and then decode them
 

00:19:22.430 --> 00:19:24.100 align:start position:0%
2 bits per item and then decode them
with<00:19:22.580><c> a</c><00:19:22.610><c> very</c><00:19:22.820><c> simple</c><00:19:23.150><c> state</c><00:19:23.450><c> machine</c><00:19:23.480><c> as</c><00:19:23.960><c> I</c>

00:19:24.100 --> 00:19:24.110 align:start position:0%
with a very simple state machine as I
 

00:19:24.110 --> 00:19:27.700 align:start position:0%
with a very simple state machine as I
provide<00:19:24.770><c> here</c><00:19:25.150><c> so</c><00:19:26.150><c> the</c><00:19:26.300><c> coding</c><00:19:26.720><c> allows</c><00:19:27.020><c> you</c><00:19:27.230><c> to</c>

00:19:27.700 --> 00:19:27.710 align:start position:0%
provide here so the coding allows you to
 

00:19:27.710 --> 00:19:28.840 align:start position:0%
provide here so the coding allows you to
either<00:19:27.860><c> rebuild</c><00:19:28.250><c> the</c><00:19:28.340><c> whole</c><00:19:28.490><c> tree</c><00:19:28.700><c> or</c>

00:19:28.840 --> 00:19:28.850 align:start position:0%
either rebuild the whole tree or
 

00:19:28.850 --> 00:19:31.420 align:start position:0%
either rebuild the whole tree or
actually<00:19:29.180><c> compute</c><00:19:29.870><c> Merkel</c><00:19:30.200><c> cash</c><00:19:30.430><c> efficiently</c>

00:19:31.420 --> 00:19:31.430 align:start position:0%
actually compute Merkel cash efficiently
 

00:19:31.430 --> 00:19:32.980 align:start position:0%
actually compute Merkel cash efficiently
and<00:19:31.580><c> then</c><00:19:32.030><c> what</c><00:19:32.210><c> you</c><00:19:32.330><c> do</c><00:19:32.450><c> next</c><00:19:32.630><c> is</c><00:19:32.810><c> that</c><00:19:32.840><c> you</c>

00:19:32.980 --> 00:19:32.990 align:start position:0%
and then what you do next is that you
 

00:19:32.990 --> 00:19:35.560 align:start position:0%
and then what you do next is that you
have<00:19:33.350><c> this</c><00:19:33.500><c> huge</c><00:19:34.040><c> tree</c><00:19:34.400><c> which</c><00:19:34.940><c> is</c><00:19:34.970><c> balanced</c>

00:19:35.560 --> 00:19:35.570 align:start position:0%
have this huge tree which is balanced
 

00:19:35.570 --> 00:19:38.440 align:start position:0%
have this huge tree which is balanced
and<00:19:35.750><c> you</c><00:19:36.350><c> would</c><00:19:36.590><c> nor</c><00:19:36.800><c> close</c><00:19:37.130><c> it</c><00:19:37.420><c> according</c><00:19:38.420><c> to</c>

00:19:38.440 --> 00:19:38.450 align:start position:0%
and you would nor close it according to
 

00:19:38.450 --> 00:19:40.210 align:start position:0%
and you would nor close it according to
this<00:19:38.660><c> huge</c><00:19:38.900><c> tree</c><00:19:39.110><c> and</c><00:19:39.260><c> then</c><00:19:39.710><c> in</c><00:19:39.920><c> order</c><00:19:40.010><c> to</c>

00:19:40.210 --> 00:19:40.220 align:start position:0%
this huge tree and then in order to
 

00:19:40.220 --> 00:19:41.500 align:start position:0%
this huge tree and then in order to
efficiently<00:19:40.520><c> store</c><00:19:40.820><c> it</c><00:19:40.880><c> and</c><00:19:40.970><c> database</c><00:19:41.360><c> you</c>

00:19:41.500 --> 00:19:41.510 align:start position:0%
efficiently store it and database you
 

00:19:41.510 --> 00:19:43.690 align:start position:0%
efficiently store it and database you
split<00:19:41.840><c> in</c><00:19:41.960><c> two</c><00:19:42.110><c> pages</c><00:19:42.290><c> of</c><00:19:42.650><c> the</c><00:19:42.920><c> fixed</c><00:19:43.220><c> size</c><00:19:43.400><c> and</c>

00:19:43.690 --> 00:19:43.700 align:start position:0%
split in two pages of the fixed size and
 

00:19:43.700 --> 00:19:45.490 align:start position:0%
split in two pages of the fixed size and
this<00:19:44.120><c> is</c><00:19:44.240><c> kind</c><00:19:44.450><c> of</c><00:19:44.510><c> the</c><00:19:44.660><c> schematics</c><00:19:45.170><c> of</c><00:19:45.320><c> how</c>

00:19:45.490 --> 00:19:45.500 align:start position:0%
this is kind of the schematics of how
 

00:19:45.500 --> 00:19:48.010 align:start position:0%
this is kind of the schematics of how
you<00:19:45.560><c> would</c><00:19:45.830><c> do</c><00:19:45.980><c> it</c><00:19:46.390><c> then</c><00:19:47.390><c> after</c><00:19:47.720><c> you</c><00:19:47.810><c> do</c><00:19:47.990><c> that</c>

00:19:48.010 --> 00:19:48.020 align:start position:0%
you would do it then after you do that
 

00:19:48.020 --> 00:19:50.020 align:start position:0%
you would do it then after you do that
you<00:19:48.290><c> encode</c><00:19:48.620><c> them</c><00:19:48.890><c> in</c><00:19:49.010><c> the</c><00:19:49.100><c> pages</c><00:19:49.310><c> and</c><00:19:49.730><c> this</c><00:19:49.910><c> is</c>

00:19:50.020 --> 00:19:50.030 align:start position:0%
you encode them in the pages and this is
 

00:19:50.030 --> 00:19:51.520 align:start position:0%
you encode them in the pages and this is
the<00:19:50.150><c> structure</c><00:19:50.510><c> of</c><00:19:50.540><c> the</c><00:19:50.690><c> page</c><00:19:50.870><c> I'm</c><00:19:51.050><c> using</c><00:19:51.290><c> and</c>

00:19:51.520 --> 00:19:51.530 align:start position:0%
the structure of the page I'm using and
 

00:19:51.530 --> 00:19:53.230 align:start position:0%
the structure of the page I'm using and
proof<00:19:51.950><c> of</c><00:19:52.070><c> concept</c><00:19:52.460><c> it's</c><00:19:52.880><c> called</c><00:19:53.090><c> like</c>

00:19:53.230 --> 00:19:53.240 align:start position:0%
proof of concept it's called like
 

00:19:53.240 --> 00:19:55.720 align:start position:0%
proof of concept it's called like
different<00:19:53.720><c> elements</c><00:19:54.440><c> in</c><00:19:54.530><c> that</c><00:19:54.650><c> and</c><00:19:54.860><c> what</c><00:19:55.610><c> is</c>

00:19:55.720 --> 00:19:55.730 align:start position:0%
different elements in that and what is
 

00:19:55.730 --> 00:19:57.250 align:start position:0%
different elements in that and what is
interesting<00:19:55.940><c> here</c><00:19:56.270><c> is</c><00:19:56.330><c> the</c><00:19:56.420><c> page</c><00:19:56.600><c> pointer</c><00:19:57.110><c> so</c>

00:19:57.250 --> 00:19:57.260 align:start position:0%
interesting here is the page pointer so
 

00:19:57.260 --> 00:19:59.410 align:start position:0%
interesting here is the page pointer so
there's<00:19:57.440><c> two</c><00:19:57.920><c> elements</c><00:19:58.280><c> stored</c><00:19:58.490><c> in</c><00:19:58.730><c> a</c><00:19:59.030><c> pages</c>

00:19:59.410 --> 00:19:59.420 align:start position:0%
there's two elements stored in a pages
 

00:19:59.420 --> 00:20:01.810 align:start position:0%
there's two elements stored in a pages
that<00:19:59.570><c> the</c><00:19:59.840><c> the</c><00:20:00.080><c> values</c><00:20:00.470><c> you</c><00:20:00.980><c> can</c><00:20:01.100><c> see</c><00:20:01.160><c> that</c><00:20:01.400><c> FP</c>

00:20:01.810 --> 00:20:01.820 align:start position:0%
that the the values you can see that FP
 

00:20:01.820 --> 00:20:02.760 align:start position:0%
that the the values you can see that FP
there<00:20:02.060><c> and</c><00:20:02.270><c> is</c>

00:20:02.760 --> 00:20:02.770 align:start position:0%
there and is
 

00:20:02.770 --> 00:20:04.440 align:start position:0%
there and is
circle<00:20:03.250><c> with</c><00:20:03.340><c> the</c><00:20:03.430><c> arrows</c><00:20:03.760><c> are</c><00:20:03.940><c> the</c><00:20:04.030><c> pointers</c>

00:20:04.440 --> 00:20:04.450 align:start position:0%
circle with the arrows are the pointers
 

00:20:04.450 --> 00:20:06.510 align:start position:0%
circle with the arrows are the pointers
and<00:20:04.720><c> so</c><00:20:05.320><c> then</c><00:20:05.470><c> after</c><00:20:05.830><c> that</c><00:20:05.860><c> you</c><00:20:06.190><c> can</c><00:20:06.220><c> actually</c>

00:20:06.510 --> 00:20:06.520 align:start position:0%
and so then after that you can actually
 

00:20:06.520 --> 00:20:11.010 align:start position:0%
and so then after that you can actually
add<00:20:06.790><c> the</c><00:20:06.940><c> history</c><00:20:07.330><c> so</c><00:20:08.760><c> so</c><00:20:09.760><c> the</c><00:20:09.910><c> main</c><00:20:10.120><c> so</c><00:20:10.840><c> let's</c>

00:20:11.010 --> 00:20:11.020 align:start position:0%
add the history so so the main so let's
 

00:20:11.020 --> 00:20:14.220 align:start position:0%
add the history so so the main so let's
let's<00:20:11.440><c> talk</c><00:20:11.590><c> about</c><00:20:11.650><c> this</c><00:20:11.860><c> so</c><00:20:12.750><c> first</c><00:20:13.750><c> of</c><00:20:13.900><c> all</c><00:20:14.020><c> in</c>

00:20:14.220 --> 00:20:14.230 align:start position:0%
let's talk about this so first of all in
 

00:20:14.230 --> 00:20:15.950 align:start position:0%
let's talk about this so first of all in
order<00:20:14.350><c> to</c><00:20:14.560><c> explain</c><00:20:14.860><c> Morrison</c><00:20:15.370><c> in</c><00:20:15.550><c> a</c><00:20:15.670><c> short</c>

00:20:15.950 --> 00:20:15.960 align:start position:0%
order to explain Morrison in a short
 

00:20:15.960 --> 00:20:18.510 align:start position:0%
order to explain Morrison in a short
sentence<00:20:16.960><c> is</c><00:20:17.110><c> that</c><00:20:17.290><c> the</c><00:20:17.740><c> main</c><00:20:17.890><c> idea</c><00:20:18.280><c> is</c><00:20:18.340><c> that</c>

00:20:18.510 --> 00:20:18.520 align:start position:0%
sentence is that the main idea is that
 

00:20:18.520 --> 00:20:20.040 align:start position:0%
sentence is that the main idea is that
you<00:20:18.640><c> use</c><00:20:18.790><c> the</c><00:20:18.940><c> same</c><00:20:18.970><c> structure</c><00:20:19.600><c> for</c><00:20:19.990><c> the</c>

00:20:20.040 --> 00:20:20.050 align:start position:0%
you use the same structure for the
 

00:20:20.050 --> 00:20:22.950 align:start position:0%
you use the same structure for the
database<00:20:20.440><c> index</c><00:20:20.890><c> as</c><00:20:21.360><c> us</c><00:20:22.360><c> the</c><00:20:22.480><c> structure</c><00:20:22.750><c> that</c>

00:20:22.950 --> 00:20:22.960 align:start position:0%
database index as us the structure that
 

00:20:22.960 --> 00:20:25.560 align:start position:0%
database index as us the structure that
you<00:20:23.080><c> use</c><00:20:23.230><c> for</c><00:20:23.410><c> miracle</c><00:20:23.740><c> ization</c><00:20:24.360><c> so</c><00:20:25.360><c> it's</c><00:20:25.480><c> the</c>

00:20:25.560 --> 00:20:25.570 align:start position:0%
you use for miracle ization so it's the
 

00:20:25.570 --> 00:20:27.540 align:start position:0%
you use for miracle ization so it's the
same<00:20:25.780><c> so</c><00:20:26.440><c> that</c><00:20:26.470><c> means</c><00:20:26.620><c> that</c><00:20:26.980><c> whenever</c><00:20:27.190><c> you</c>

00:20:27.540 --> 00:20:27.550 align:start position:0%
same so that means that whenever you
 

00:20:27.550 --> 00:20:29.340 align:start position:0%
same so that means that whenever you
actually<00:20:27.880><c> commit</c><00:20:28.450><c> something</c><00:20:28.690><c> into</c><00:20:28.990><c> database</c>

00:20:29.340 --> 00:20:29.350 align:start position:0%
actually commit something into database
 

00:20:29.350 --> 00:20:31.620 align:start position:0%
actually commit something into database
it<00:20:29.560><c> doesn't</c><00:20:29.950><c> move</c><00:20:30.160><c> anymore</c><00:20:30.490><c> because</c><00:20:31.180><c> it's</c><00:20:31.510><c> an</c>

00:20:31.620 --> 00:20:31.630 align:start position:0%
it doesn't move anymore because it's an
 

00:20:31.630 --> 00:20:33.570 align:start position:0%
it doesn't move anymore because it's an
exactly<00:20:32.020><c> the</c><00:20:32.140><c> same</c><00:20:32.320><c> point</c><00:20:32.500><c> in</c><00:20:32.620><c> exactly</c><00:20:33.430><c> the</c>

00:20:33.570 --> 00:20:33.580 align:start position:0%
exactly the same point in exactly the
 

00:20:33.580 --> 00:20:34.590 align:start position:0%
exactly the same point in exactly the
place<00:20:33.670><c> where</c><00:20:33.970><c> it's</c><00:20:34.120><c> supposed</c><00:20:34.210><c> to</c><00:20:34.540><c> be</c>

00:20:34.590 --> 00:20:34.600 align:start position:0%
place where it's supposed to be
 

00:20:34.600 --> 00:20:36.720 align:start position:0%
place where it's supposed to be
according<00:20:35.350><c> to</c><00:20:35.680><c> the</c><00:20:35.830><c> to</c><00:20:36.130><c> the</c><00:20:36.250><c> index</c><00:20:36.520><c> of</c><00:20:36.640><c> the</c>

00:20:36.720 --> 00:20:36.730 align:start position:0%
according to the to the index of the
 

00:20:36.730 --> 00:20:38.340 align:start position:0%
according to the to the index of the
database<00:20:37.060><c> which</c><00:20:37.570><c> means</c><00:20:37.780><c> that</c><00:20:37.900><c> write</c>

00:20:38.340 --> 00:20:38.350 align:start position:0%
database which means that write
 

00:20:38.350 --> 00:20:41.340 align:start position:0%
database which means that write
amplification<00:20:38.740><c> equals</c><00:20:39.810><c> the</c><00:20:40.810><c> basically</c><00:20:41.110><c> write</c>

00:20:41.340 --> 00:20:41.350 align:start position:0%
amplification equals the basically write
 

00:20:41.350 --> 00:20:44.340 align:start position:0%
amplification equals the basically write
amplification<00:20:41.740><c> does</c><00:20:42.160><c> not</c><00:20:42.400><c> happen</c><00:20:42.760><c> and</c><00:20:43.170><c> so</c><00:20:44.170><c> the</c>

00:20:44.340 --> 00:20:44.350 align:start position:0%
amplification does not happen and so the
 

00:20:44.350 --> 00:20:47.670 align:start position:0%
amplification does not happen and so the
database<00:20:44.620><c> just</c><00:20:45.610><c> grows</c><00:20:45.940><c> it</c><00:20:46.750><c> doesn't</c><00:20:47.200><c> keep</c>

00:20:47.670 --> 00:20:47.680 align:start position:0%
database just grows it doesn't keep
 

00:20:47.680 --> 00:20:49.710 align:start position:0%
database just grows it doesn't keep
three<00:20:47.980><c> writing</c><00:20:48.400><c> things</c><00:20:48.820><c> on</c><00:20:49.120><c> it</c><00:20:49.360><c> if</c><00:20:49.480><c> it's</c><00:20:49.660><c> just</c>

00:20:49.710 --> 00:20:49.720 align:start position:0%
three writing things on it if it's just
 

00:20:49.720 --> 00:20:51.870 align:start position:0%
three writing things on it if it's just
simply<00:20:50.080><c> adds</c><00:20:50.230><c> thing</c><00:20:50.530><c> which</c><00:20:51.070><c> is</c><00:20:51.220><c> has</c><00:20:51.550><c> some</c><00:20:51.760><c> nice</c>

00:20:51.870 --> 00:20:51.880 align:start position:0%
simply adds thing which is has some nice
 

00:20:51.880 --> 00:20:55.050 align:start position:0%
simply adds thing which is has some nice
properties<00:20:52.020><c> so</c><00:20:53.020><c> at</c><00:20:53.140><c> the</c><00:20:53.260><c> moment</c><00:20:53.880><c> with</c><00:20:54.880><c> my</c>

00:20:55.050 --> 00:20:55.060 align:start position:0%
properties so at the moment with my
 

00:20:55.060 --> 00:20:58.020 align:start position:0%
properties so at the moment with my
proof<00:20:55.300><c> of</c><00:20:55.830><c> concept</c><00:20:56.830><c> which</c><00:20:57.400><c> I've</c><00:20:57.580><c> been</c><00:20:57.610><c> running</c>

00:20:58.020 --> 00:20:58.030 align:start position:0%
proof of concept which I've been running
 

00:20:58.030 --> 00:21:00.030 align:start position:0%
proof of concept which I've been running
I<00:20:58.180><c> was</c><00:20:58.930><c> comparing</c><00:20:59.350><c> with</c><00:20:59.440><c> Troopergate</c><00:20:59.860><c> which</c>

00:21:00.030 --> 00:21:00.040 align:start position:0%
I was comparing with Troopergate which
 

00:21:00.040 --> 00:21:04.500 align:start position:0%
I was comparing with Troopergate which
is<00:21:00.160><c> also</c><00:21:00.340><c> quite</c><00:21:01.110><c> already</c><00:21:02.110><c> high</c><00:21:02.320><c> bar</c><00:21:03.090><c> so</c><00:21:04.090><c> the</c>

00:21:04.500 --> 00:21:04.510 align:start position:0%
is also quite already high bar so the
 

00:21:04.510 --> 00:21:07.320 align:start position:0%
is also quite already high bar so the
right<00:21:04.750><c> hand</c><00:21:04.890><c> so</c><00:21:05.890><c> the</c><00:21:06.070><c> the</c><00:21:06.580><c> right</c><00:21:06.760><c> efficiency</c>

00:21:07.320 --> 00:21:07.330 align:start position:0%
right hand so the the right efficiency
 

00:21:07.330 --> 00:21:11.250 align:start position:0%
right hand so the the right efficiency
has<00:21:07.510><c> been</c><00:21:07.780><c> about</c><00:21:08.650><c> seven</c><00:21:09.040><c> times</c><00:21:09.900><c> better</c><00:21:10.900><c> than</c>

00:21:11.250 --> 00:21:11.260 align:start position:0%
has been about seven times better than
 

00:21:11.260 --> 00:21:14.580 align:start position:0%
has been about seven times better than
in<00:21:11.560><c> turbo</c><00:21:11.950><c> gas</c><00:21:12.130><c> so</c><00:21:12.520><c> it</c><00:21:12.910><c> means</c><00:21:13.270><c> that</c><00:21:13.590><c> it</c>

00:21:14.580 --> 00:21:14.590 align:start position:0%
in turbo gas so it means that it
 

00:21:14.590 --> 00:21:17.300 align:start position:0%
in turbo gas so it means that it
actually<00:21:14.890><c> has</c><00:21:15.190><c> said</c><00:21:15.790><c> seven</c><00:21:16.120><c> times</c><00:21:16.330><c> less</c><00:21:16.570><c> IO</c>

00:21:17.300 --> 00:21:17.310 align:start position:0%
actually has said seven times less IO
 

00:21:17.310 --> 00:21:19.350 align:start position:0%
actually has said seven times less IO
unfortunately<00:21:18.310><c> the</c><00:21:18.490><c> space</c><00:21:18.700><c> efficiency</c><00:21:19.270><c> has</c>

00:21:19.350 --> 00:21:19.360 align:start position:0%
unfortunately the space efficiency has
 

00:21:19.360 --> 00:21:21.540 align:start position:0%
unfortunately the space efficiency has
decreased<00:21:19.840><c> compared</c><00:21:20.830><c> to</c><00:21:20.950><c> too</c><00:21:21.070><c> big</c><00:21:21.250><c> if</c><00:21:21.370><c> it's</c>

00:21:21.540 --> 00:21:21.550 align:start position:0%
decreased compared to too big if it's
 

00:21:21.550 --> 00:21:24.720 align:start position:0%
decreased compared to too big if it's
about<00:21:21.730><c> four</c><00:21:22.060><c> times</c><00:21:22.270><c> less</c><00:21:22.570><c> space</c><00:21:23.320><c> efficient</c><00:21:23.770><c> in</c>

00:21:24.720 --> 00:21:24.730 align:start position:0%
about four times less space efficient in
 

00:21:24.730 --> 00:21:27.000 align:start position:0%
about four times less space efficient in
the<00:21:24.820><c> current</c><00:21:25.120><c> numbers</c><00:21:25.360><c> but</c><00:21:26.080><c> I</c><00:21:26.140><c> have</c><00:21:26.530><c> a</c><00:21:26.560><c> some</c>

00:21:27.000 --> 00:21:27.010 align:start position:0%
the current numbers but I have a some
 

00:21:27.010 --> 00:21:30.090 align:start position:0%
the current numbers but I have a some
some<00:21:27.760><c> I</c><00:21:28.210><c> know</c><00:21:28.960><c> some</c><00:21:29.470><c> ways</c><00:21:29.650><c> how</c><00:21:29.860><c> you</c><00:21:29.890><c> can</c>

00:21:30.090 --> 00:21:30.100 align:start position:0%
some I know some ways how you can
 

00:21:30.100 --> 00:21:32.580 align:start position:0%
some I know some ways how you can
improve<00:21:30.460><c> that</c><00:21:30.760><c> access</c><00:21:31.630><c> efficiency</c><00:21:32.140><c> are</c><00:21:32.290><c> only</c>

00:21:32.580 --> 00:21:32.590 align:start position:0%
improve that access efficiency are only
 

00:21:32.590 --> 00:21:36.420 align:start position:0%
improve that access efficiency are only
superficially<00:21:33.250><c> tested</c><00:21:33.640><c> that</c><00:21:33.730><c> so</c><00:21:34.390><c> and</c><00:21:35.020><c> so</c><00:21:35.430><c> well</c>

00:21:36.420 --> 00:21:36.430 align:start position:0%
superficially tested that so and so well
 

00:21:36.430 --> 00:21:38.870 align:start position:0%
superficially tested that so and so well
this<00:21:36.910><c> to</c><00:21:37.630><c> put</c><00:21:37.960><c> it</c><00:21:38.050><c> in</c><00:21:38.140><c> a</c><00:21:38.200><c> perspective</c><00:21:38.410><c> is</c><00:21:38.800><c> that</c>

00:21:38.870 --> 00:21:38.880 align:start position:0%
this to put it in a perspective is that
 

00:21:38.880 --> 00:21:40.980 align:start position:0%
this to put it in a perspective is that
people<00:21:39.880><c> usually</c><00:21:40.000><c> talk</c><00:21:40.300><c> about</c><00:21:40.540><c> the</c><00:21:40.630><c> trade-off</c>

00:21:40.980 --> 00:21:40.990 align:start position:0%
people usually talk about the trade-off
 

00:21:40.990 --> 00:21:42.810 align:start position:0%
people usually talk about the trade-off
of<00:21:41.080><c> three</c><00:21:41.290><c> things</c><00:21:41.530><c> and</c><00:21:41.770><c> database</c><00:21:42.250><c> is</c><00:21:42.430><c> update</c>

00:21:42.810 --> 00:21:42.820 align:start position:0%
of three things and database is update
 

00:21:42.820 --> 00:21:44.460 align:start position:0%
of three things and database is update
efficiency<00:21:43.300><c> space</c><00:21:43.510><c> efficiency</c><00:21:43.930><c> and</c><00:21:44.200><c> access</c>

00:21:44.460 --> 00:21:44.470 align:start position:0%
efficiency space efficiency and access
 

00:21:44.470 --> 00:21:46.500 align:start position:0%
efficiency space efficiency and access
efficiency<00:21:44.980><c> and</c><00:21:45.850><c> you</c><00:21:45.940><c> can</c><00:21:46.120><c> see</c><00:21:46.240><c> that</c><00:21:46.390><c> you</c>

00:21:46.500 --> 00:21:46.510 align:start position:0%
efficiency and you can see that you
 

00:21:46.510 --> 00:21:48.000 align:start position:0%
efficiency and you can see that you
really<00:21:46.540><c> want</c><00:21:46.930><c> to</c><00:21:47.020><c> be</c><00:21:47.140><c> inside</c><00:21:47.620><c> this</c><00:21:47.800><c> triangle</c>

00:21:48.000 --> 00:21:48.010 align:start position:0%
really want to be inside this triangle
 

00:21:48.010 --> 00:21:50.310 align:start position:0%
really want to be inside this triangle
on<00:21:48.340><c> that</c><00:21:48.460><c> plane</c><00:21:48.700><c> but</c><00:21:49.360><c> you</c><00:21:49.390><c> don't</c><00:21:49.660><c> you</c><00:21:49.960><c> never</c>

00:21:50.310 --> 00:21:50.320 align:start position:0%
on that plane but you don't you never
 

00:21:50.320 --> 00:21:51.630 align:start position:0%
on that plane but you don't you never
really<00:21:50.620><c> know</c><00:21:50.740><c> whether</c><00:21:51.010><c> you're</c><00:21:51.220><c> above</c><00:21:51.580><c> that</c>

00:21:51.630 --> 00:21:51.640 align:start position:0%
really know whether you're above that
 

00:21:51.640 --> 00:21:53.190 align:start position:0%
really know whether you're above that
triangle<00:21:52.270><c> which</c><00:21:52.390><c> means</c><00:21:52.420><c> that</c><00:21:52.720><c> you're</c><00:21:52.900><c> you</c>

00:21:53.190 --> 00:21:53.200 align:start position:0%
triangle which means that you're you
 

00:21:53.200 --> 00:21:54.750 align:start position:0%
triangle which means that you're you
don't<00:21:53.380><c> actually</c><00:21:53.530><c> have</c><00:21:53.830><c> an</c><00:21:53.980><c> efficient</c><00:21:54.400><c> rate</c><00:21:54.610><c> of</c>

00:21:54.750 --> 00:21:54.760 align:start position:0%
don't actually have an efficient rate of
 

00:21:54.760 --> 00:21:56.760 align:start position:0%
don't actually have an efficient rate of
optimal<00:21:55.480><c> trade-off</c><00:21:55.780><c> or</c><00:21:55.960><c> you're</c><00:21:56.140><c> in</c><00:21:56.500><c> a</c>

00:21:56.760 --> 00:21:56.770 align:start position:0%
optimal trade-off or you're in a
 

00:21:56.770 --> 00:21:58.830 align:start position:0%
optimal trade-off or you're in a
triangle<00:21:57.550><c> so</c><00:21:58.090><c> what</c><00:21:58.240><c> I'm</c><00:21:58.330><c> trying</c><00:21:58.450><c> to</c><00:21:58.630><c> do</c><00:21:58.750><c> is</c>

00:21:58.830 --> 00:21:58.840 align:start position:0%
triangle so what I'm trying to do is
 

00:21:58.840 --> 00:22:01.200 align:start position:0%
triangle so what I'm trying to do is
that<00:21:58.960><c> I</c><00:21:59.140><c> put</c><00:21:59.290><c> it</c><00:21:59.980><c> that</c><00:22:00.100><c> none</c><00:22:00.460><c> up</c><00:22:00.580><c> to</c><00:22:00.730><c> my</c><00:22:00.820><c> systems</c>

00:22:01.200 --> 00:22:01.210 align:start position:0%
that I put it that none up to my systems
 

00:22:01.210 --> 00:22:03.120 align:start position:0%
that I put it that none up to my systems
are<00:22:01.420><c> already</c><00:22:01.570><c> above</c><00:22:02.080><c> actually</c><00:22:02.590><c> above</c><00:22:03.010><c> the</c>

00:22:03.120 --> 00:22:03.130 align:start position:0%
are already above actually above the
 

00:22:03.130 --> 00:22:04.790 align:start position:0%
are already above actually above the
triangle<00:22:03.580><c> so</c><00:22:03.730><c> they're</c><00:22:03.880><c> not</c><00:22:04.000><c> really</c>

00:22:04.790 --> 00:22:04.800 align:start position:0%
triangle so they're not really
 

00:22:04.800 --> 00:22:07.880 align:start position:0%
triangle so they're not really
exercising<00:22:05.800><c> trade-offs</c><00:22:06.310><c> at</c><00:22:07.030><c> all</c><00:22:07.240><c> so</c><00:22:07.600><c> they're</c>

00:22:07.880 --> 00:22:07.890 align:start position:0%
exercising trade-offs at all so they're
 

00:22:07.890 --> 00:22:10.920 align:start position:0%
exercising trade-offs at all so they're
inefficient<00:22:08.890><c> in</c><00:22:09.160><c> any</c><00:22:09.400><c> way</c><00:22:09.670><c> in</c><00:22:10.510><c> any</c><00:22:10.660><c> possible</c>

00:22:10.920 --> 00:22:10.930 align:start position:0%
inefficient in any way in any possible
 

00:22:10.930 --> 00:22:12.600 align:start position:0%
inefficient in any way in any possible
way<00:22:11.140><c> but</c><00:22:11.440><c> what</c><00:22:11.770><c> I'm</c><00:22:11.860><c> trying</c><00:22:12.010><c> to</c><00:22:12.160><c> do</c><00:22:12.310><c> now</c><00:22:12.460><c> is</c>

00:22:12.600 --> 00:22:12.610 align:start position:0%
way but what I'm trying to do now is
 

00:22:12.610 --> 00:22:14.820 align:start position:0%
way but what I'm trying to do now is
that<00:22:12.730><c> trying</c><00:22:13.180><c> to</c><00:22:13.240><c> hopefully</c><00:22:13.870><c> I</c><00:22:14.230><c> am</c><00:22:14.500><c> inside</c><00:22:14.770><c> the</c>

00:22:14.820 --> 00:22:14.830 align:start position:0%
that trying to hopefully I am inside the
 

00:22:14.830 --> 00:22:16.360 align:start position:0%
that trying to hopefully I am inside the
triangle<00:22:15.100><c> already</c><00:22:15.550><c> and</c><00:22:15.790><c> trying</c>

00:22:16.360 --> 00:22:16.370 align:start position:0%
triangle already and trying
 

00:22:16.370 --> 00:22:20.049 align:start position:0%
triangle already and trying
navigating<00:22:17.290><c> between</c><00:22:18.290><c> them</c><00:22:18.710><c> so</c><00:22:18.950><c> I'm</c><00:22:19.370><c> gonna</c><00:22:19.550><c> if</c>

00:22:20.049 --> 00:22:20.059 align:start position:0%
navigating between them so I'm gonna if
 

00:22:20.059 --> 00:22:21.549 align:start position:0%
navigating between them so I'm gonna if
it's<00:22:20.240><c> any</c><00:22:20.450><c> time</c><00:22:20.690><c> I'm</c><00:22:21.020><c> gonna</c><00:22:21.170><c> take</c><00:22:21.380><c> any</c>

00:22:21.549 --> 00:22:21.559 align:start position:0%
it's any time I'm gonna take any
 

00:22:21.559 --> 00:22:23.920 align:start position:0%
it's any time I'm gonna take any
questions<00:22:21.920><c> any</c><00:22:22.370><c> time</c><00:22:22.580><c> for</c><00:22:22.790><c> questions</c><00:22:23.120><c> or</c><00:22:23.300><c> yes</c>

00:22:23.920 --> 00:22:23.930 align:start position:0%
questions any time for questions or yes
 

00:22:23.930 --> 00:22:26.500 align:start position:0%
questions any time for questions or yes
yep<00:22:24.380><c> there's</c><00:22:25.370><c> some</c><00:22:25.520><c> time</c><00:22:25.670><c> for</c><00:22:25.820><c> questions</c><00:22:26.390><c> yeah</c>

00:22:26.500 --> 00:22:26.510 align:start position:0%
yep there's some time for questions yeah
 

00:22:26.510 --> 00:22:35.950 align:start position:0%
yep there's some time for questions yeah
I<00:22:26.540><c> sorry</c><00:22:26.930><c> I</c><00:22:27.020><c> rushed</c><00:22:34.540><c> so</c><00:22:35.540><c> just</c><00:22:35.750><c> that</c><00:22:35.870><c> I</c>

00:22:35.950 --> 00:22:35.960 align:start position:0%
I sorry I rushed so just that I
 

00:22:35.960 --> 00:22:38.890 align:start position:0%
I sorry I rushed so just that I
understand<00:22:36.410><c> it</c><00:22:36.559><c> this</c><00:22:36.860><c> 200</c><00:22:37.520><c> gigabytes</c><00:22:38.120><c> or</c><00:22:38.390><c> 200</c>

00:22:38.890 --> 00:22:38.900 align:start position:0%
understand it this 200 gigabytes or 200
 

00:22:38.900 --> 00:22:40.990 align:start position:0%
understand it this 200 gigabytes or 200
plus<00:22:39.140><c> 70</c><00:22:39.559><c> for</c><00:22:39.740><c> the</c><00:22:39.770><c> receipts</c><00:22:40.130><c> that's</c><00:22:40.430><c> actually</c>

00:22:40.990 --> 00:22:41.000 align:start position:0%
plus 70 for the receipts that's actually
 

00:22:41.000 --> 00:22:42.730 align:start position:0%
plus 70 for the receipts that's actually
an<00:22:41.270><c> archive</c><00:22:41.660><c> not</c><00:22:41.840><c> right</c><00:22:42.020><c> yes</c><00:22:42.170><c> sir</c><00:22:42.380><c> Connaught</c>

00:22:42.730 --> 00:22:42.740 align:start position:0%
an archive not right yes sir Connaught
 

00:22:42.740 --> 00:22:43.540 align:start position:0%
an archive not right yes sir Connaught
nice

00:22:43.540 --> 00:22:43.550 align:start position:0%
nice
 

00:22:43.550 --> 00:22:46.660 align:start position:0%
nice
yeah<00:22:44.090><c> and</c><00:22:44.300><c> it</c><00:22:44.390><c> can</c><00:22:44.600><c> it</c><00:22:44.930><c> can</c><00:22:45.370><c> fetch</c><00:22:46.370><c> you</c><00:22:46.490><c> any</c>

00:22:46.660 --> 00:22:46.670 align:start position:0%
yeah and it can it can fetch you any
 

00:22:46.670 --> 00:22:48.880 align:start position:0%
yeah and it can it can fetch you any
data<00:22:46.940><c> for</c><00:22:47.210><c> the</c><00:22:47.330><c> entire</c><00:22:47.690><c> history</c><00:22:47.900><c> through</c><00:22:48.650><c> any</c>

00:22:48.880 --> 00:22:48.890 align:start position:0%
data for the entire history through any
 

00:22:48.890 --> 00:22:57.669 align:start position:0%
data for the entire history through any
RPC<00:22:49.429><c> queries</c><00:22:55.450><c> can</c><00:22:56.450><c> you</c><00:22:56.570><c> talk</c><00:22:56.780><c> more</c><00:22:57.020><c> about</c><00:22:57.080><c> this</c>

00:22:57.669 --> 00:22:57.679 align:start position:0%
RPC queries can you talk more about this
 

00:22:57.679 --> 00:23:01.960 align:start position:0%
RPC queries can you talk more about this
range<00:22:58.040><c> request</c><00:22:58.520><c> Oh</c><00:22:59.740><c> range</c><00:23:00.740><c> request</c><00:23:01.100><c> it's</c><00:23:01.610><c> it's</c>

00:23:01.960 --> 00:23:01.970 align:start position:0%
range request Oh range request it's it's
 

00:23:01.970 --> 00:23:08.049 align:start position:0%
range request Oh range request it's it's
it's<00:23:02.270><c> it's</c><00:23:02.510><c> basically</c><00:23:06.309><c> so</c><00:23:07.309><c> range</c><00:23:07.640><c> of</c><00:23:07.760><c> quest</c><00:23:07.940><c> is</c>

00:23:08.049 --> 00:23:08.059 align:start position:0%
it's it's basically so range of quest is
 

00:23:08.059 --> 00:23:10.330 align:start position:0%
it's it's basically so range of quest is
quite<00:23:08.240><c> simple</c><00:23:08.660><c> because</c><00:23:08.980><c> essentially</c><00:23:09.980><c> you</c>

00:23:10.330 --> 00:23:10.340 align:start position:0%
quite simple because essentially you
 

00:23:10.340 --> 00:23:13.330 align:start position:0%
quite simple because essentially you
were<00:23:11.110><c> in</c><00:23:12.110><c> most</c><00:23:12.320><c> of</c><00:23:12.500><c> these</c><00:23:12.590><c> key</c><00:23:12.800><c> value</c><00:23:13.070><c> stores</c>

00:23:13.330 --> 00:23:13.340 align:start position:0%
were in most of these key value stores
 

00:23:13.340 --> 00:23:15.940 align:start position:0%
were in most of these key value stores
what<00:23:14.330><c> you</c><00:23:14.450><c> can</c><00:23:14.600><c> do</c><00:23:14.690><c> you</c><00:23:14.809><c> can</c><00:23:14.960><c> open</c><00:23:15.500><c> a</c><00:23:15.590><c> course</c><00:23:15.800><c> or</c>

00:23:15.940 --> 00:23:15.950 align:start position:0%
what you can do you can open a course or
 

00:23:15.950 --> 00:23:18.370 align:start position:0%
what you can do you can open a course or
at<00:23:16.460><c> a</c><00:23:16.520><c> certain</c><00:23:16.910><c> you</c><00:23:17.090><c> can</c><00:23:17.300><c> you</c><00:23:17.690><c> can</c><00:23:17.840><c> seek</c><00:23:18.110><c> to</c><00:23:18.140><c> the</c>

00:23:18.370 --> 00:23:18.380 align:start position:0%
at a certain you can you can seek to the
 

00:23:18.380 --> 00:23:20.200 align:start position:0%
at a certain you can you can seek to the
certain<00:23:18.740><c> key</c><00:23:19.340><c> for</c><00:23:19.580><c> example</c><00:23:19.910><c> in</c><00:23:19.970><c> this</c><00:23:20.030><c> case</c>

00:23:20.200 --> 00:23:20.210 align:start position:0%
certain key for example in this case
 

00:23:20.210 --> 00:23:22.780 align:start position:0%
certain key for example in this case
will<00:23:20.450><c> be</c><00:23:20.480><c> one</c><00:23:20.990><c> with</c><00:23:21.590><c> the</c><00:23:21.710><c> sum</c><00:23:21.890><c> 0</c><00:23:22.160><c> 0</c><00:23:22.429><c> 0</c><00:23:22.670><c> 0</c>

00:23:22.780 --> 00:23:22.790 align:start position:0%
will be one with the sum 0 0 0 0
 

00:23:22.790 --> 00:23:24.970 align:start position:0%
will be one with the sum 0 0 0 0
whatever<00:23:23.630><c> the</c><00:23:23.809><c> first</c><00:23:23.990><c> key</c><00:23:24.260><c> is</c><00:23:24.440><c> to</c><00:23:24.650><c> start</c><00:23:24.860><c> with</c>

00:23:24.970 --> 00:23:24.980 align:start position:0%
whatever the first key is to start with
 

00:23:24.980 --> 00:23:26.830 align:start position:0%
whatever the first key is to start with
1<00:23:25.130><c> and</c><00:23:25.280><c> then</c><00:23:25.370><c> you</c><00:23:25.790><c> just</c><00:23:26.000><c> use</c><00:23:26.179><c> that</c><00:23:26.330><c> iterator</c><00:23:26.750><c> to</c>

00:23:26.830 --> 00:23:26.840 align:start position:0%
1 and then you just use that iterator to
 

00:23:26.840 --> 00:23:29.350 align:start position:0%
1 and then you just use that iterator to
iterate<00:23:27.320><c> through</c><00:23:27.350><c> them</c><00:23:27.679><c> until</c><00:23:28.010><c> you</c><00:23:28.190><c> see</c><00:23:28.429><c> 2</c><00:23:29.179><c> in</c>

00:23:29.350 --> 00:23:29.360 align:start position:0%
iterate through them until you see 2 in
 

00:23:29.360 --> 00:23:30.730 align:start position:0%
iterate through them until you see 2 in
the<00:23:30.020><c> first</c><00:23:30.200><c> position</c>

00:23:30.730 --> 00:23:30.740 align:start position:0%
the first position
 

00:23:30.740 --> 00:23:33.310 align:start position:0%
the first position
that's<00:23:31.610><c> it</c><00:23:32.000><c> range</c><00:23:32.210><c> query</c><00:23:32.510><c> it's</c><00:23:32.960><c> not</c><00:23:33.080><c> like</c><00:23:33.230><c> a</c>

00:23:33.310 --> 00:23:33.320 align:start position:0%
that's it range query it's not like a
 

00:23:33.320 --> 00:23:34.540 align:start position:0%
that's it range query it's not like a
square<00:23:33.620><c> but</c><00:23:33.830><c> it's</c><00:23:34.220><c> still</c><00:23:34.370><c> possible</c>

00:23:34.540 --> 00:23:34.550 align:start position:0%
square but it's still possible
 

00:23:34.550 --> 00:23:37.540 align:start position:0%
square but it's still possible
efficiently<00:23:35.980><c> Alexa</c><00:23:36.980><c> can</c><00:23:37.070><c> you</c><00:23:37.190><c> talk</c><00:23:37.400><c> a</c><00:23:37.429><c> little</c>

00:23:37.540 --> 00:23:37.550 align:start position:0%
efficiently Alexa can you talk a little
 

00:23:37.550 --> 00:23:40.990 align:start position:0%
efficiently Alexa can you talk a little
bit<00:23:37.820><c> more</c><00:23:38.330><c> about</c><00:23:38.600><c> your</c><00:23:39.530><c> experiment</c><00:23:40.370><c> with</c><00:23:40.490><c> you</c>

00:23:40.990 --> 00:23:41.000 align:start position:0%
bit more about your experiment with you
 

00:23:41.000 --> 00:23:43.480 align:start position:0%
bit more about your experiment with you
Thurman<00:23:41.330><c> and</c><00:23:41.360><c> why</c><00:23:41.720><c> oh</c><00:23:42.080><c> yes</c><00:23:42.770><c> I</c><00:23:43.010><c> forgot</c><00:23:43.309><c> about</c>

00:23:43.480 --> 00:23:43.490 align:start position:0%
Thurman and why oh yes I forgot about
 

00:23:43.490 --> 00:23:46.060 align:start position:0%
Thurman and why oh yes I forgot about
that<00:23:43.640><c> sorry</c><00:23:44.270><c> so</c><00:23:44.750><c> the</c><00:23:45.020><c> ether</c><00:23:45.290><c> main</c><00:23:45.470><c> experiment</c>

00:23:46.060 --> 00:23:46.070 align:start position:0%
that sorry so the ether main experiment
 

00:23:46.070 --> 00:23:48.400 align:start position:0%
that sorry so the ether main experiment
is<00:23:46.160><c> interesting</c><00:23:46.760><c> for</c><00:23:46.880><c> me</c><00:23:47.000><c> because</c><00:23:47.360><c> at</c><00:23:48.260><c> the</c>

00:23:48.400 --> 00:23:48.410 align:start position:0%
is interesting for me because at the
 

00:23:48.410 --> 00:23:51.220 align:start position:0%
is interesting for me because at the
moment<00:23:48.440><c> when</c><00:23:48.950><c> I</c><00:23:49.030><c> only</c><00:23:50.030><c> try</c><00:23:50.390><c> to</c><00:23:50.420><c> optimize</c><00:23:50.990><c> the</c>

00:23:51.220 --> 00:23:51.230 align:start position:0%
moment when I only try to optimize the
 

00:23:51.230 --> 00:23:54.100 align:start position:0%
moment when I only try to optimize the
surrogate<00:23:51.890><c> and</c><00:23:52.330><c> there</c><00:23:53.330><c> is</c><00:23:53.420><c> a</c><00:23:53.450><c> Patricia</c><00:23:53.809><c> tree</c>

00:23:54.100 --> 00:23:54.110 align:start position:0%
surrogate and there is a Patricia tree
 

00:23:54.110 --> 00:23:56.320 align:start position:0%
surrogate and there is a Patricia tree
which<00:23:54.470><c> already</c><00:23:54.679><c> I</c><00:23:55.280><c> said</c><00:23:55.850><c> that</c><00:23:55.940><c> I</c><00:23:55.970><c> don't</c><00:23:56.210><c> like</c>

00:23:56.320 --> 00:23:56.330 align:start position:0%
which already I said that I don't like
 

00:23:56.330 --> 00:23:59.530 align:start position:0%
which already I said that I don't like
it<00:23:56.480><c> very</c><00:23:56.510><c> much</c><00:23:56.690><c> but</c><00:23:57.670><c> and</c><00:23:58.670><c> it's</c><00:23:58.820><c> it's</c><00:23:59.059><c> encoded</c>

00:23:59.530 --> 00:23:59.540 align:start position:0%
it very much but and it's it's encoded
 

00:23:59.540 --> 00:24:01.720 align:start position:0%
it very much but and it's it's encoded
in<00:23:59.690><c> a</c><00:23:59.750><c> yellow</c><00:23:59.960><c> paper</c><00:24:00.200><c> but</c><00:24:00.860><c> what</c><00:24:01.130><c> I</c><00:24:01.160><c> want</c><00:24:01.640><c> to</c>

00:24:01.720 --> 00:24:01.730 align:start position:0%
in a yellow paper but what I want to
 

00:24:01.730 --> 00:24:03.880 align:start position:0%
in a yellow paper but what I want to
kind<00:24:02.120><c> of</c><00:24:02.240><c> look</c><00:24:02.390><c> behind</c><00:24:02.900><c> beyond</c><00:24:03.530><c> the</c><00:24:03.650><c> yellow</c>

00:24:03.880 --> 00:24:03.890 align:start position:0%
kind of look behind beyond the yellow
 

00:24:03.890 --> 00:24:06.790 align:start position:0%
kind of look behind beyond the yellow
paper<00:24:04.100><c> maybe</c><00:24:04.820><c> because</c><00:24:05.410><c> because</c><00:24:06.410><c> it's</c><00:24:06.590><c> cool</c>

00:24:06.790 --> 00:24:06.800 align:start position:0%
paper maybe because because it's cool
 

00:24:06.800 --> 00:24:08.830 align:start position:0%
paper maybe because because it's cool
because<00:24:07.010><c> because</c><00:24:07.490><c> I</c><00:24:07.580><c> want</c><00:24:07.790><c> to</c><00:24:07.910><c> search</c><00:24:08.600><c> for</c>

00:24:08.830 --> 00:24:08.840 align:start position:0%
because because I want to search for
 

00:24:08.840 --> 00:24:10.750 align:start position:0%
because because I want to search for
different<00:24:09.380><c> structures</c><00:24:09.890><c> maybe</c><00:24:10.400><c> because</c>

00:24:10.750 --> 00:24:10.760 align:start position:0%
different structures maybe because
 

00:24:10.760 --> 00:24:12.220 align:start position:0%
different structures maybe because
they're<00:24:10.880><c> going</c><00:24:11.000><c> to</c><00:24:11.059><c> be</c><00:24:11.120><c> used</c><00:24:11.300><c> in</c><00:24:11.450><c> East</c><00:24:11.750><c> Point</c><00:24:11.960><c> 2</c>

00:24:12.220 --> 00:24:12.230 align:start position:0%
they're going to be used in East Point 2
 

00:24:12.230 --> 00:24:16.540 align:start position:0%
they're going to be used in East Point 2
to<00:24:12.679><c> point</c><00:24:12.830><c> or</c><00:24:13.100><c> because</c><00:24:14.059><c> a</c><00:24:14.650><c> you</c><00:24:15.650><c> know</c><00:24:15.740><c> we</c><00:24:16.280><c> might</c>

00:24:16.540 --> 00:24:16.550 align:start position:0%
to point or because a you know we might
 

00:24:16.550 --> 00:24:18.190 align:start position:0%
to point or because a you know we might
be<00:24:16.670><c> able</c><00:24:16.790><c> to</c><00:24:16.940><c> be</c><00:24:17.120><c> able</c><00:24:17.179><c> to</c><00:24:17.420><c> create</c><00:24:17.630><c> something</c>

00:24:18.190 --> 00:24:18.200 align:start position:0%
be able to be able to create something
 

00:24:18.200 --> 00:24:19.810 align:start position:0%
be able to be able to create something
more<00:24:18.470><c> efficient</c><00:24:18.830><c> in</c><00:24:18.920><c> either</c><00:24:19.160><c> maned</c><00:24:19.429><c> and</c><00:24:19.730><c> then</c>

00:24:19.810 --> 00:24:19.820 align:start position:0%
more efficient in either maned and then
 

00:24:19.820 --> 00:24:22.000 align:start position:0%
more efficient in either maned and then
we<00:24:20.360><c> could</c><00:24:20.540><c> just</c><00:24:20.570><c> transplant</c><00:24:21.500><c> the</c><00:24:21.650><c> same</c><00:24:21.860><c> so</c>

00:24:22.000 --> 00:24:22.010 align:start position:0%
we could just transplant the same so
 

00:24:22.010 --> 00:24:24.820 align:start position:0%
we could just transplant the same so
they<00:24:22.160><c> cerium</c><00:24:22.780><c> it's</c><00:24:23.780><c> probably</c><00:24:24.350><c> good</c><00:24:24.800><c> for</c>

00:24:24.820 --> 00:24:24.830 align:start position:0%
they cerium it's probably good for
 

00:24:24.830 --> 00:24:26.290 align:start position:0%
they cerium it's probably good for
experimentation<00:24:25.429><c> I</c><00:24:25.670><c> also</c><00:24:25.820><c> quite</c><00:24:26.120><c> like</c>

00:24:26.290 --> 00:24:26.300 align:start position:0%
experimentation I also quite like
 

00:24:26.300 --> 00:24:28.120 align:start position:0%
experimentation I also quite like
working<00:24:26.540><c> with</c><00:24:26.929><c> the</c><00:24:27.050><c> either</c><00:24:27.470><c> main</c><00:24:27.679><c> team</c><00:24:27.890><c> so</c>

00:24:28.120 --> 00:24:28.130 align:start position:0%
working with the either main team so
 

00:24:28.130 --> 00:24:28.770 align:start position:0%
working with the either main team so
there

00:24:28.770 --> 00:24:28.780 align:start position:0%
there
 

00:24:28.780 --> 00:24:33.810 align:start position:0%
there
so<00:24:29.530><c> yeah</c><00:24:29.650><c> it's</c><00:24:29.830><c> that's</c><00:24:30.730><c> the</c><00:24:30.850><c> reason</c><00:24:32.730><c> is</c><00:24:33.730><c> there</c>

00:24:33.810 --> 00:24:33.820 align:start position:0%
so yeah it's that's the reason is there
 

00:24:33.820 --> 00:24:35.850 align:start position:0%
so yeah it's that's the reason is there
any<00:24:33.970><c> like</c><00:24:34.240><c> performance</c><00:24:35.050><c> difference</c><00:24:35.530><c> when</c>

00:24:35.850 --> 00:24:35.860 align:start position:0%
any like performance difference when
 

00:24:35.860 --> 00:24:38.790 align:start position:0%
any like performance difference when
you're<00:24:35.980><c> doing</c><00:24:36.370><c> verses</c><00:24:37.270><c> intermittent</c><00:24:38.170><c> or</c><00:24:38.590><c> very</c>

00:24:38.790 --> 00:24:38.800 align:start position:0%
you're doing verses intermittent or very
 

00:24:38.800 --> 00:24:41.100 align:start position:0%
you're doing verses intermittent or very
early<00:24:39.070><c> stages</c><00:24:39.310><c> and</c><00:24:39.640><c> the</c><00:24:39.970><c> whole</c><00:24:40.660><c> reason</c><00:24:40.960><c> why</c><00:24:41.080><c> I</c>

00:24:41.100 --> 00:24:41.110 align:start position:0%
early stages and the whole reason why I
 

00:24:41.110 --> 00:24:43.260 align:start position:0%
early stages and the whole reason why I
started<00:24:41.530><c> to</c><00:24:41.830><c> do</c><00:24:42.430><c> this</c><00:24:42.610><c> Morris</c><00:24:42.940><c> thing</c><00:24:43.150><c> is</c>

00:24:43.260 --> 00:24:43.270 align:start position:0%
started to do this Morris thing is
 

00:24:43.270 --> 00:24:45.360 align:start position:0%
started to do this Morris thing is
because<00:24:43.570><c> the</c><00:24:44.170><c> first</c><00:24:44.440><c> performance</c><00:24:44.950><c> tests</c><00:24:45.250><c> were</c>

00:24:45.360 --> 00:24:45.370 align:start position:0%
because the first performance tests were
 

00:24:45.370 --> 00:24:48.780 align:start position:0%
because the first performance tests were
not<00:24:45.580><c> satisfactory</c><00:24:46.510><c> to</c><00:24:46.660><c> me</c><00:24:46.690><c> so</c><00:24:47.470><c> I</c><00:24:47.710><c> wanted</c><00:24:48.400><c> that</c>

00:24:48.780 --> 00:24:48.790 align:start position:0%
not satisfactory to me so I wanted that
 

00:24:48.790 --> 00:24:53.640 align:start position:0%
not satisfactory to me so I wanted that
to<00:24:48.940><c> be</c><00:24:48.970><c> faster</c><00:24:51.510><c> we</c><00:24:52.510><c> probably</c><00:24:52.690><c> have</c><00:24:52.870><c> time</c><00:24:53.590><c> for</c>

00:24:53.640 --> 00:24:53.650 align:start position:0%
to be faster we probably have time for
 

00:24:53.650 --> 00:24:54.570 align:start position:0%
to be faster we probably have time for
one<00:24:53.920><c> more</c><00:24:53.950><c> question</c>

00:24:54.570 --> 00:24:54.580 align:start position:0%
one more question
 

00:24:54.580 --> 00:24:58.110 align:start position:0%
one more question
yeah<00:24:56.310><c> first</c><00:24:57.310><c> of</c><00:24:57.430><c> all</c><00:24:57.520><c> I</c><00:24:57.550><c> just</c><00:24:57.640><c> wanted</c><00:24:57.940><c> to</c><00:24:58.030><c> ask</c>

00:24:58.110 --> 00:24:58.120 align:start position:0%
yeah first of all I just wanted to ask
 

00:24:58.120 --> 00:25:00.000 align:start position:0%
yeah first of all I just wanted to ask
do<00:24:58.270><c> you</c><00:24:58.330><c> realize</c><00:24:58.810><c> how</c><00:24:58.990><c> amazing</c><00:24:59.230><c> you</c><00:24:59.620><c> are</c>

00:25:00.000 --> 00:25:00.010 align:start position:0%
do you realize how amazing you are
 

00:25:00.010 --> 00:25:15.030 align:start position:0%
do you realize how amazing you are
oh<00:25:00.040><c> thanks</c><00:25:12.480><c> how</c><00:25:13.480><c> you</c><00:25:13.540><c> come</c><00:25:14.080><c> from</c><00:25:14.290><c> one</c><00:25:14.740><c> point</c>

00:25:15.030 --> 00:25:15.040 align:start position:0%
oh thanks how you come from one point
 

00:25:15.040 --> 00:25:18.750 align:start position:0%
oh thanks how you come from one point
three<00:25:15.430><c> terabytes</c><00:25:16.180><c> to</c><00:25:16.980><c> 250</c><00:25:17.980><c> gigabytes</c><00:25:18.520><c> with</c>

00:25:18.750 --> 00:25:18.760 align:start position:0%
three terabytes to 250 gigabytes with
 

00:25:18.760 --> 00:25:20.490 align:start position:0%
three terabytes to 250 gigabytes with
the<00:25:18.880><c> same</c><00:25:19.150><c> it</c><00:25:19.750><c> feels</c><00:25:19.960><c> like</c><00:25:20.140><c> the</c><00:25:20.260><c> same</c>

00:25:20.490 --> 00:25:20.500 align:start position:0%
the same it feels like the same
 

00:25:20.500 --> 00:25:23.070 align:start position:0%
the same it feels like the same
performance<00:25:21.030><c> but</c><00:25:22.030><c> a</c><00:25:22.060><c> very</c><00:25:22.390><c> significant</c>

00:25:23.070 --> 00:25:23.080 align:start position:0%
performance but a very significant
 

00:25:23.080 --> 00:25:27.840 align:start position:0%
performance but a very significant
decrease<00:25:23.560><c> in</c><00:25:23.590><c> the</c><00:25:23.770><c> size</c><00:25:25.380><c> well</c><00:25:26.380><c> there</c><00:25:27.070><c> it</c><00:25:27.280><c> comes</c>

00:25:27.840 --> 00:25:27.850 align:start position:0%
decrease in the size well there it comes
 

00:25:27.850 --> 00:25:29.820 align:start position:0%
decrease in the size well there it comes
from<00:25:28.120><c> two</c><00:25:28.300><c> things</c><00:25:28.840><c> first</c><00:25:29.290><c> of</c><00:25:29.440><c> all</c><00:25:29.530><c> I</c><00:25:29.710><c> don't</c>

00:25:29.820 --> 00:25:29.830 align:start position:0%
from two things first of all I don't
 

00:25:29.830 --> 00:25:31.850 align:start position:0%
from two things first of all I don't
store<00:25:30.190><c> any</c><00:25:30.340><c> hashes</c><00:25:30.760><c> and</c><00:25:30.790><c> the</c><00:25:31.060><c> hashes</c><00:25:31.480><c> are</c>

00:25:31.850 --> 00:25:31.860 align:start position:0%
store any hashes and the hashes are
 

00:25:31.860 --> 00:25:34.200 align:start position:0%
store any hashes and the hashes are
probably<00:25:32.860><c> one</c><00:25:33.070><c> of</c><00:25:33.100><c> the</c><00:25:33.340><c> biggest</c><00:25:33.520><c> contributor</c>

00:25:34.200 --> 00:25:34.210 align:start position:0%
probably one of the biggest contributor
 

00:25:34.210 --> 00:25:36.570 align:start position:0%
probably one of the biggest contributor
to<00:25:34.390><c> the</c><00:25:34.540><c> to</c><00:25:34.840><c> the</c><00:25:34.930><c> space</c><00:25:35.170><c> in</c><00:25:35.440><c> in</c><00:25:35.770><c> existing</c>

00:25:36.570 --> 00:25:36.580 align:start position:0%
to the to the space in in existing
 

00:25:36.580 --> 00:25:40.860 align:start position:0%
to the to the space in in existing
clients<00:25:36.910><c> and</c><00:25:37.000><c> secondly</c><00:25:38.160><c> the</c><00:25:39.720><c> the</c><00:25:40.720><c> tree</c>

00:25:40.860 --> 00:25:40.870 align:start position:0%
clients and secondly the the tree
 

00:25:40.870 --> 00:25:42.930 align:start position:0%
clients and secondly the the tree
structure<00:25:41.140><c> when</c><00:25:42.130><c> you</c><00:25:42.160><c> were</c><00:25:42.400><c> model</c><00:25:42.760><c> the</c>

00:25:42.930 --> 00:25:42.940 align:start position:0%
structure when you were model the
 

00:25:42.940 --> 00:25:45.210 align:start position:0%
structure when you were model the
history<00:25:43.600><c> of</c><00:25:43.780><c> tree</c><00:25:43.930><c> structure</c><00:25:44.170><c> it</c><00:25:44.590><c> repeats</c><00:25:45.070><c> a</c>

00:25:45.210 --> 00:25:45.220 align:start position:0%
history of tree structure it repeats a
 

00:25:45.220 --> 00:25:47.400 align:start position:0%
history of tree structure it repeats a
lot<00:25:45.370><c> of</c><00:25:45.520><c> the</c><00:25:45.760><c> elements</c><00:25:46.270><c> on</c><00:25:46.420><c> closer</c><00:25:47.050><c> to</c><00:25:47.290><c> the</c>

00:25:47.400 --> 00:25:47.410 align:start position:0%
lot of the elements on closer to the
 

00:25:47.410 --> 00:25:49.320 align:start position:0%
lot of the elements on closer to the
root<00:25:47.560><c> when</c><00:25:47.800><c> you</c><00:25:47.920><c> create</c><00:25:48.190><c> a</c><00:25:48.220><c> new</c><00:25:48.430><c> version</c><00:25:48.640><c> so</c>

00:25:49.320 --> 00:25:49.330 align:start position:0%
root when you create a new version so
 

00:25:49.330 --> 00:25:50.850 align:start position:0%
root when you create a new version so
that<00:25:49.360><c> repetition</c><00:25:49.630><c> also</c><00:25:50.260><c> that</c><00:25:50.560><c> it</c><00:25:50.710><c> also</c>

00:25:50.850 --> 00:25:50.860 align:start position:0%
that repetition also that it also
 

00:25:50.860 --> 00:25:53.430 align:start position:0%
that repetition also that it also
contributes<00:25:51.430><c> to</c><00:25:51.520><c> the</c><00:25:51.940><c> might</c><00:25:52.120><c> to</c><00:25:52.420><c> the</c><00:25:52.720><c> Moores</c>

00:25:53.430 --> 00:25:53.440 align:start position:0%
contributes to the might to the Moores
 

00:25:53.440 --> 00:25:55.050 align:start position:0%
contributes to the might to the Moores
being<00:25:53.830><c> less</c><00:25:54.040><c> space</c><00:25:54.250><c> efficient</c><00:25:54.700><c> because</c><00:25:54.790><c> it's</c>

00:25:55.050 --> 00:25:55.060 align:start position:0%
being less space efficient because it's
 

00:25:55.060 --> 00:25:58.710 align:start position:0%
being less space efficient because it's
also<00:25:55.180><c> tree</c><00:25:55.450><c> based</c><00:25:55.690><c> so</c><00:25:56.530><c> and</c><00:25:57.390><c> that's</c><00:25:58.390><c> basically</c>

00:25:58.710 --> 00:25:58.720 align:start position:0%
also tree based so and that's basically
 

00:25:58.720 --> 00:26:00.840 align:start position:0%
also tree based so and that's basically
two<00:25:58.930><c> reasons</c><00:25:59.080><c> and</c><00:25:59.530><c> if</c><00:26:00.130><c> you</c><00:26:00.220><c> remove</c><00:26:00.460><c> these</c><00:26:00.640><c> two</c>

00:26:00.840 --> 00:26:00.850 align:start position:0%
two reasons and if you remove these two
 

00:26:00.850 --> 00:26:02.190 align:start position:0%
two reasons and if you remove these two
things<00:26:01.060><c> that</c><00:26:01.180><c> becomes</c><00:26:01.630><c> a</c><00:26:01.720><c> super</c>

00:26:02.190 --> 00:26:02.200 align:start position:0%
things that becomes a super
 

00:26:02.200 --> 00:26:06.570 align:start position:0%
things that becomes a super
space-efficient<00:26:04.920><c> all</c><00:26:05.920><c> right</c><00:26:06.070><c> well</c><00:26:06.250><c> thank</c><00:26:06.490><c> you</c>

00:26:06.570 --> 00:26:06.580 align:start position:0%
space-efficient all right well thank you
 

00:26:06.580 --> 00:26:07.110 align:start position:0%
space-efficient all right well thank you
very<00:26:06.610><c> much</c>

00:26:07.110 --> 00:26:07.120 align:start position:0%
very much
 

00:26:07.120 --> 00:26:08.790 align:start position:0%
very much
alexei<00:26:07.450><c> thank</c><00:26:07.690><c> you</c><00:26:07.750><c> for</c><00:26:07.900><c> coming</c><00:26:08.140><c> great</c>

00:26:08.790 --> 00:26:08.800 align:start position:0%
alexei thank you for coming great
 

00:26:08.800 --> 00:26:19.620 align:start position:0%
alexei thank you for coming great
[Applause]

00:26:19.620 --> 00:26:19.630 align:start position:0%
 
 

00:26:19.630 --> 00:26:21.690 align:start position:0%
 
you