WEBVTT
Kind: captions
Language: en

00:00:00.089 --> 00:00:03.050 align:start position:0%
 
I<00:00:00.120><c> explained</c><00:00:00.960><c> what</c><00:00:01.260><c> foot</c><00:00:01.740><c> proofs</c><00:00:02.010><c> are</c><00:00:02.280><c> I'm</c>

00:00:03.050 --> 00:00:03.060 align:start position:0%
I explained what foot proofs are I'm
 

00:00:03.060 --> 00:00:05.450 align:start position:0%
I explained what foot proofs are I'm
gonna<00:00:03.300><c> motivate</c><00:00:03.870><c> why</c><00:00:04.410><c> we</c><00:00:04.890><c> actually</c><00:00:05.040><c> need</c><00:00:05.310><c> them</c>

00:00:05.450 --> 00:00:05.460 align:start position:0%
gonna motivate why we actually need them
 

00:00:05.460 --> 00:00:07.249 align:start position:0%
gonna motivate why we actually need them
and<00:00:05.700><c> what</c><00:00:06.029><c> is</c><00:00:06.150><c> the</c><00:00:06.270><c> problem</c><00:00:06.509><c> that</c><00:00:06.870><c> we're</c>

00:00:07.249 --> 00:00:07.259 align:start position:0%
and what is the problem that we're
 

00:00:07.259 --> 00:00:10.730 align:start position:0%
and what is the problem that we're
trying<00:00:07.290><c> to</c><00:00:07.529><c> solve</c><00:00:07.740><c> so</c><00:00:08.700><c> as</c><00:00:09.389><c> we</c><00:00:09.630><c> all</c><00:00:09.660><c> know</c><00:00:09.929><c> at</c><00:00:10.230><c> the</c>

00:00:10.730 --> 00:00:10.740 align:start position:0%
trying to solve so as we all know at the
 

00:00:10.740 --> 00:00:12.470 align:start position:0%
trying to solve so as we all know at the
moment<00:00:11.130><c> there's</c><00:00:11.400><c> a</c><00:00:11.460><c> really</c><00:00:11.730><c> huge</c><00:00:11.940><c> trade</c><00:00:12.330><c> off</c>

00:00:12.470 --> 00:00:12.480 align:start position:0%
moment there's a really huge trade off
 

00:00:12.480 --> 00:00:14.900 align:start position:0%
moment there's a really huge trade off
or<00:00:13.009><c> it's</c><00:00:14.009><c> thought</c><00:00:14.250><c> to</c><00:00:14.280><c> be</c><00:00:14.429><c> there's</c><00:00:14.639><c> a</c><00:00:14.730><c> huge</c>

00:00:14.900 --> 00:00:14.910 align:start position:0%
or it's thought to be there's a huge
 

00:00:14.910 --> 00:00:16.670 align:start position:0%
or it's thought to be there's a huge
trade<00:00:15.150><c> off</c><00:00:15.299><c> between</c><00:00:15.599><c> how</c><00:00:16.470><c> much</c>

00:00:16.670 --> 00:00:16.680 align:start position:0%
trade off between how much
 

00:00:16.680 --> 00:00:18.950 align:start position:0%
trade off between how much
decentralization<00:00:17.430><c> that</c><00:00:18.420><c> your</c><00:00:18.539><c> blockchain</c>

00:00:18.950 --> 00:00:18.960 align:start position:0%
decentralization that your blockchain
 

00:00:18.960 --> 00:00:21.380 align:start position:0%
decentralization that your blockchain
system<00:00:19.289><c> has</c><00:00:19.500><c> and</c><00:00:19.800><c> how</c><00:00:20.490><c> much</c><00:00:20.670><c> Unchained</c>

00:00:21.380 --> 00:00:21.390 align:start position:0%
system has and how much Unchained
 

00:00:21.390 --> 00:00:24.140 align:start position:0%
system has and how much Unchained
throughput<00:00:21.779><c> you</c><00:00:21.869><c> can</c><00:00:21.990><c> get</c><00:00:22.170><c> and</c><00:00:23.150><c> effectively</c>

00:00:24.140 --> 00:00:24.150 align:start position:0%
throughput you can get and effectively
 

00:00:24.150 --> 00:00:27.050 align:start position:0%
throughput you can get and effectively
the<00:00:25.080><c> argument</c><00:00:25.529><c> goes</c><00:00:25.710><c> that</c><00:00:26.039><c> the</c><00:00:26.490><c> more</c><00:00:26.760><c> the</c>

00:00:27.050 --> 00:00:27.060 align:start position:0%
the argument goes that the more the
 

00:00:27.060 --> 00:00:28.429 align:start position:0%
the argument goes that the more the
bigger<00:00:27.210><c> the</c><00:00:27.330><c> block</c><00:00:27.539><c> size</c><00:00:27.810><c> the</c><00:00:28.140><c> bigger</c><00:00:28.320><c> the</c>

00:00:28.429 --> 00:00:28.439 align:start position:0%
bigger the block size the bigger the
 

00:00:28.439 --> 00:00:30.980 align:start position:0%
bigger the block size the bigger the
blockchain<00:00:28.970><c> the</c><00:00:29.970><c> more</c><00:00:30.210><c> expensive</c><00:00:30.570><c> it</c><00:00:30.840><c> is</c><00:00:30.869><c> to</c>

00:00:30.980 --> 00:00:30.990 align:start position:0%
blockchain the more expensive it is to
 

00:00:30.990 --> 00:00:33.080 align:start position:0%
blockchain the more expensive it is to
run<00:00:31.170><c> a</c><00:00:31.199><c> full</c><00:00:31.380><c> node</c><00:00:31.619><c> and</c><00:00:31.890><c> so</c><00:00:32.550><c> everyone</c><00:00:33.000><c> will</c>

00:00:33.080 --> 00:00:33.090 align:start position:0%
run a full node and so everyone will
 

00:00:33.090 --> 00:00:34.700 align:start position:0%
run a full node and so everyone will
have<00:00:33.180><c> to</c><00:00:33.300><c> run</c><00:00:33.420><c> a</c><00:00:33.450><c> like</c><00:00:33.630><c> client</c><00:00:34.020><c> instead</c><00:00:34.380><c> and</c>

00:00:34.700 --> 00:00:34.710 align:start position:0%
have to run a like client instead and
 

00:00:34.710 --> 00:00:37.430 align:start position:0%
have to run a like client instead and
the<00:00:35.700><c> problem</c><00:00:36.090><c> with</c><00:00:36.180><c> like</c><00:00:36.360><c> clients</c><00:00:36.930><c> is</c><00:00:37.110><c> that</c>

00:00:37.430 --> 00:00:37.440 align:start position:0%
the problem with like clients is that
 

00:00:37.440 --> 00:00:41.600 align:start position:0%
the problem with like clients is that
they<00:00:37.980><c> accept</c><00:00:38.730><c> blocks</c><00:00:39.059><c> that</c><00:00:39.629><c> are</c><00:00:39.690><c> invalid</c><00:00:40.610><c> so</c>

00:00:41.600 --> 00:00:41.610 align:start position:0%
they accept blocks that are invalid so
 

00:00:41.610 --> 00:00:43.490 align:start position:0%
they accept blocks that are invalid so
if<00:00:41.790><c> a</c><00:00:41.879><c> block</c><00:00:42.090><c> contains</c><00:00:42.510><c> invalid</c><00:00:42.960><c> transactions</c>

00:00:43.490 --> 00:00:43.500 align:start position:0%
if a block contains invalid transactions
 

00:00:43.500 --> 00:00:46.580 align:start position:0%
if a block contains invalid transactions
and<00:00:44.059><c> they</c><00:00:45.059><c> will</c><00:00:45.420><c> happily</c><00:00:45.780><c> accept</c><00:00:45.989><c> that</c><00:00:46.320><c> block</c>

00:00:46.580 --> 00:00:46.590 align:start position:0%
and they will happily accept that block
 

00:00:46.590 --> 00:00:49.850 align:start position:0%
and they will happily accept that block
if<00:00:47.190><c> the</c><00:00:47.670><c> majority</c><00:00:47.820><c> of</c><00:00:48.239><c> the</c><00:00:48.390><c> consensus</c><00:00:49.050><c> has</c>

00:00:49.850 --> 00:00:49.860 align:start position:0%
if the majority of the consensus has
 

00:00:49.860 --> 00:00:53.060 align:start position:0%
if the majority of the consensus has
actually<00:00:50.420><c> sort</c><00:00:51.420><c> of</c><00:00:51.539><c> gain</c><00:00:52.260><c> consensus</c><00:00:52.800><c> on</c><00:00:52.920><c> that</c>

00:00:53.060 --> 00:00:53.070 align:start position:0%
actually sort of gain consensus on that
 

00:00:53.070 --> 00:00:55.100 align:start position:0%
actually sort of gain consensus on that
block<00:00:53.280><c> so</c><00:00:53.640><c> for</c><00:00:53.850><c> example</c><00:00:54.210><c> if</c><00:00:54.390><c> there's</c><00:00:54.629><c> a</c><00:00:54.690><c> 51%</c>

00:00:55.100 --> 00:00:55.110 align:start position:0%
block so for example if there's a 51%
 

00:00:55.110 --> 00:00:58.700 align:start position:0%
block so for example if there's a 51%
attack<00:00:56.149><c> then</c><00:00:57.149><c> you</c><00:00:58.140><c> could</c><00:00:58.260><c> trick</c><00:00:58.440><c> a</c><00:00:58.469><c> light</c>

00:00:58.700 --> 00:00:58.710 align:start position:0%
attack then you could trick a light
 

00:00:58.710 --> 00:01:00.979 align:start position:0%
attack then you could trick a light
client<00:00:59.100><c> into</c><00:00:59.520><c> accepting</c><00:01:00.030><c> blocks</c><00:01:00.329><c> that</c>

00:01:00.979 --> 00:01:00.989 align:start position:0%
client into accepting blocks that
 

00:01:00.989 --> 00:01:02.599 align:start position:0%
client into accepting blocks that
effectively<00:01:01.379><c> generate</c><00:01:01.800><c> money</c><00:01:02.010><c> out</c><00:01:02.160><c> of</c><00:01:02.190><c> tener</c>

00:01:02.599 --> 00:01:02.609 align:start position:0%
effectively generate money out of tener
 

00:01:02.609 --> 00:01:04.939 align:start position:0%
effectively generate money out of tener
or<00:01:03.180><c> double</c><00:01:03.539><c> spend</c><00:01:03.780><c> and</c><00:01:03.989><c> or</c><00:01:04.470><c> break</c><00:01:04.769><c> the</c>

00:01:04.939 --> 00:01:04.949 align:start position:0%
or double spend and or break the
 

00:01:04.949 --> 00:01:06.980 align:start position:0%
or double spend and or break the
protocol<00:01:05.309><c> rules</c><00:01:05.549><c> and</c><00:01:05.790><c> so</c><00:01:06.299><c> on</c><00:01:06.450><c> and</c><00:01:06.600><c> so</c><00:01:06.720><c> forth</c>

00:01:06.980 --> 00:01:06.990 align:start position:0%
protocol rules and so on and so forth
 

00:01:06.990 --> 00:01:09.170 align:start position:0%
protocol rules and so on and so forth
because<00:01:07.530><c> they</c><00:01:07.830><c> effectively</c><00:01:08.250><c> a</c><00:01:08.340><c> Jew</c><00:01:08.610><c> assume</c>

00:01:09.170 --> 00:01:09.180 align:start position:0%
because they effectively a Jew assume
 

00:01:09.180 --> 00:01:11.450 align:start position:0%
because they effectively a Jew assume
that<00:01:09.840><c> the</c><00:01:09.930><c> majority</c><00:01:10.020><c> of</c><00:01:10.470><c> the</c><00:01:10.680><c> consensus</c><00:01:11.250><c> is</c>

00:01:11.450 --> 00:01:11.460 align:start position:0%
that the majority of the consensus is
 

00:01:11.460 --> 00:01:13.399 align:start position:0%
that the majority of the consensus is
honest<00:01:11.880><c> which</c><00:01:12.450><c> is</c><00:01:12.570><c> a</c><00:01:12.600><c> really</c><00:01:12.810><c> bad</c><00:01:12.930><c> assumption</c>

00:01:13.399 --> 00:01:13.409 align:start position:0%
honest which is a really bad assumption
 

00:01:13.409 --> 00:01:15.440 align:start position:0%
honest which is a really bad assumption
though<00:01:13.590><c> should</c><00:01:14.340><c> we</c><00:01:14.700><c> should</c><00:01:14.760><c> we</c><00:01:14.880><c> should</c><00:01:15.090><c> try</c><00:01:15.390><c> to</c>

00:01:15.440 --> 00:01:15.450 align:start position:0%
though should we should we should try to
 

00:01:15.450 --> 00:01:18.260 align:start position:0%
though should we should we should try to
eliminate<00:01:16.520><c> so</c><00:01:17.520><c> the</c><00:01:17.610><c> big</c><00:01:17.759><c> question</c><00:01:17.880><c> that</c><00:01:18.150><c> we</c>

00:01:18.260 --> 00:01:18.270 align:start position:0%
eliminate so the big question that we
 

00:01:18.270 --> 00:01:20.899 align:start position:0%
eliminate so the big question that we
might<00:01:18.450><c> want</c><00:01:18.600><c> to</c><00:01:18.630><c> ask</c><00:01:18.780><c> ourselves</c><00:01:19.049><c> is</c><00:01:19.590><c> how</c><00:01:20.340><c> could</c>

00:01:20.899 --> 00:01:20.909 align:start position:0%
might want to ask ourselves is how could
 

00:01:20.909 --> 00:01:23.270 align:start position:0%
might want to ask ourselves is how could
we<00:01:21.090><c> actually</c><00:01:21.450><c> make</c><00:01:21.630><c> it</c><00:01:21.659><c> possible</c><00:01:21.810><c> for</c><00:01:22.590><c> like</c>

00:01:23.270 --> 00:01:23.280 align:start position:0%
we actually make it possible for like
 

00:01:23.280 --> 00:01:25.820 align:start position:0%
we actually make it possible for like
clients<00:01:23.850><c> to</c><00:01:24.119><c> reject</c><00:01:24.720><c> these</c><00:01:25.049><c> invalid</c><00:01:25.560><c> blocks</c>

00:01:25.820 --> 00:01:25.830 align:start position:0%
clients to reject these invalid blocks
 

00:01:25.830 --> 00:01:28.490 align:start position:0%
clients to reject these invalid blocks
just<00:01:26.130><c> like</c><00:01:26.880><c> full</c><00:01:27.150><c> nodes</c><00:01:27.360><c> do</c><00:01:27.540><c> because</c><00:01:28.140><c> if</c><00:01:28.259><c> full</c>

00:01:28.490 --> 00:01:28.500 align:start position:0%
just like full nodes do because if full
 

00:01:28.500 --> 00:01:30.109 align:start position:0%
just like full nodes do because if full
node<00:01:28.710><c> receives</c><00:01:28.890><c> an</c><00:01:29.189><c> invalid</c><00:01:29.549><c> block</c><00:01:29.729><c> they</c><00:01:29.970><c> will</c>

00:01:30.109 --> 00:01:30.119 align:start position:0%
node receives an invalid block they will
 

00:01:30.119 --> 00:01:32.060 align:start position:0%
node receives an invalid block they will
reject<00:01:30.390><c> it</c><00:01:30.570><c> so</c><00:01:31.110><c> how</c><00:01:31.259><c> can</c><00:01:31.320><c> we</c><00:01:31.500><c> make</c><00:01:31.650><c> a</c><00:01:31.860><c> light</c>

00:01:32.060 --> 00:01:32.070 align:start position:0%
reject it so how can we make a light
 

00:01:32.070 --> 00:01:34.249 align:start position:0%
reject it so how can we make a light
client<00:01:32.430><c> do</c><00:01:32.700><c> the</c><00:01:32.820><c> same</c><00:01:33.000><c> thing</c><00:01:33.270><c> so</c><00:01:33.869><c> that</c><00:01:34.079><c> they</c>

00:01:34.249 --> 00:01:34.259 align:start position:0%
client do the same thing so that they
 

00:01:34.259 --> 00:01:38.149 align:start position:0%
client do the same thing so that they
two<00:01:34.820><c> don't</c><00:01:35.820><c> have</c><00:01:35.909><c> to</c><00:01:36.210><c> trust</c><00:01:36.479><c> the</c><00:01:37.439><c> miners</c><00:01:37.979><c> and</c>

00:01:38.149 --> 00:01:38.159 align:start position:0%
two don't have to trust the miners and
 

00:01:38.159 --> 00:01:39.920 align:start position:0%
two don't have to trust the miners and
they<00:01:38.310><c> don't</c><00:01:38.460><c> have</c><00:01:38.549><c> to</c><00:01:38.670><c> assume</c><00:01:39.090><c> that</c><00:01:39.390><c> the</c>

00:01:39.920 --> 00:01:39.930 align:start position:0%
they don't have to assume that the
 

00:01:39.930 --> 00:01:43.219 align:start position:0%
they don't have to assume that the
majority<00:01:40.229><c> of</c><00:01:40.500><c> the</c><00:01:40.740><c> consensus</c><00:01:41.280><c> is</c><00:01:41.430><c> honest</c><00:01:42.229><c> so</c>

00:01:43.219 --> 00:01:43.229 align:start position:0%
majority of the consensus is honest so
 

00:01:43.229 --> 00:01:45.260 align:start position:0%
majority of the consensus is honest so
the<00:01:43.710><c> solution</c><00:01:44.100><c> to</c><00:01:44.130><c> this</c><00:01:44.220><c> is</c><00:01:44.729><c> that</c><00:01:45.000><c> we</c><00:01:45.060><c> could</c>

00:01:45.260 --> 00:01:45.270 align:start position:0%
the solution to this is that we could
 

00:01:45.270 --> 00:01:47.830 align:start position:0%
the solution to this is that we could
use<00:01:45.450><c> fraud</c><00:01:45.810><c> and</c><00:01:46.079><c> data</c><00:01:46.590><c> availability</c><00:01:47.100><c> proofs</c>

00:01:47.830 --> 00:01:47.840 align:start position:0%
use fraud and data availability proofs
 

00:01:47.840 --> 00:01:50.090 align:start position:0%
use fraud and data availability proofs
and<00:01:48.840><c> this</c><00:01:49.140><c> is</c><00:01:49.259><c> what</c><00:01:49.799><c> I'm</c><00:01:49.860><c> going</c><00:01:49.979><c> to</c><00:01:50.009><c> be</c>

00:01:50.090 --> 00:01:50.100 align:start position:0%
and this is what I'm going to be
 

00:01:50.100 --> 00:01:52.219 align:start position:0%
and this is what I'm going to be
presenting<00:01:50.790><c> today</c><00:01:50.909><c> is</c><00:01:51.270><c> based</c><00:01:51.659><c> on</c><00:01:51.930><c> a</c><00:01:51.960><c> paper</c>

00:01:52.219 --> 00:01:52.229 align:start position:0%
presenting today is based on a paper
 

00:01:52.229 --> 00:01:55.460 align:start position:0%
presenting today is based on a paper
that<00:01:53.009><c> we</c><00:01:53.610><c> released</c><00:01:54.240><c> last</c><00:01:54.540><c> month</c><00:01:54.899><c> and</c><00:01:55.229><c> this</c><00:01:55.350><c> is</c>

00:01:55.460 --> 00:01:55.470 align:start position:0%
that we released last month and this is
 

00:01:55.470 --> 00:01:57.350 align:start position:0%
that we released last month and this is
a<00:01:55.500><c> joint</c><00:01:55.740><c> work</c><00:01:55.920><c> with</c><00:01:56.070><c> Albert</c><00:01:56.670><c> vary</c><00:01:56.880><c> from</c><00:01:57.000><c> UCL</c>

00:01:57.350 --> 00:01:57.360 align:start position:0%
a joint work with Albert vary from UCL
 

00:01:57.360 --> 00:02:00.319 align:start position:0%
a joint work with Albert vary from UCL
and<00:01:57.540><c> Vitalik</c><00:01:58.049><c> from</c><00:01:58.530><c> a</c><00:01:58.619><c> Syrian</c><00:01:58.920><c> research</c><00:01:59.329><c> we</c>

00:02:00.319 --> 00:02:00.329 align:start position:0%
and Vitalik from a Syrian research we
 

00:02:00.329 --> 00:02:01.880 align:start position:0%
and Vitalik from a Syrian research we
also<00:02:00.360><c> have</c><00:02:00.689><c> the</c><00:02:00.810><c> link</c><00:02:01.200><c> is</c><00:02:01.350><c> on</c><00:02:01.409><c> the</c><00:02:01.530><c> screen</c><00:02:01.680><c> and</c>

00:02:01.880 --> 00:02:01.890 align:start position:0%
also have the link is on the screen and
 

00:02:01.890 --> 00:02:05.330 align:start position:0%
also have the link is on the screen and
also<00:02:02.460><c> we</c><00:02:02.670><c> have</c><00:02:02.790><c> code</c><00:02:03.000><c> as</c><00:02:03.180><c> well</c><00:02:04.009><c> so</c><00:02:05.009><c> the</c><00:02:05.100><c> basic</c>

00:02:05.330 --> 00:02:05.340 align:start position:0%
also we have code as well so the basic
 

00:02:05.340 --> 00:02:08.660 align:start position:0%
also we have code as well so the basic
idea<00:02:05.460><c> of</c><00:02:05.759><c> food</c><00:02:06.000><c> proofs</c><00:02:06.409><c> is</c><00:02:07.409><c> effectively</c><00:02:07.920><c> that</c>

00:02:08.660 --> 00:02:08.670 align:start position:0%
idea of food proofs is effectively that
 

00:02:08.670 --> 00:02:11.059 align:start position:0%
idea of food proofs is effectively that
you<00:02:09.479><c> have</c><00:02:09.629><c> like</c><00:02:09.840><c> clients</c><00:02:10.319><c> and</c><00:02:10.500><c> you</c><00:02:10.800><c> have</c><00:02:10.920><c> full</c>

00:02:11.059 --> 00:02:11.069 align:start position:0%
you have like clients and you have full
 

00:02:11.069 --> 00:02:13.850 align:start position:0%
you have like clients and you have full
nodes<00:02:11.310><c> and</c><00:02:11.610><c> like</c><00:02:12.330><c> clients</c><00:02:12.750><c> only</c><00:02:13.020><c> download</c>

00:02:13.850 --> 00:02:13.860 align:start position:0%
nodes and like clients only download
 

00:02:13.860 --> 00:02:16.550 align:start position:0%
nodes and like clients only download
headers<00:02:14.220><c> and</c><00:02:14.520><c> fullness</c><00:02:14.970><c> also</c><00:02:15.600><c> download</c><00:02:16.020><c> the</c>

00:02:16.550 --> 00:02:16.560 align:start position:0%
headers and fullness also download the
 

00:02:16.560 --> 00:02:18.140 align:start position:0%
headers and fullness also download the
entire<00:02:16.860><c> block</c><00:02:17.130><c> including</c><00:02:17.430><c> the</c><00:02:17.700><c> transaction</c>

00:02:18.140 --> 00:02:18.150 align:start position:0%
entire block including the transaction
 

00:02:18.150 --> 00:02:21.230 align:start position:0%
entire block including the transaction
there<00:02:18.300><c> and</c><00:02:18.660><c> if</c><00:02:19.560><c> a</c><00:02:19.710><c> full</c><00:02:19.950><c> mode</c><00:02:20.160><c> detects</c><00:02:20.970><c> that</c>

00:02:21.230 --> 00:02:21.240 align:start position:0%
there and if a full mode detects that
 

00:02:21.240 --> 00:02:23.240 align:start position:0%
there and if a full mode detects that
there<00:02:21.810><c> is</c><00:02:21.930><c> some</c><00:02:22.080><c> invalid</c><00:02:22.470><c> transaction</c><00:02:23.130><c> in</c>

00:02:23.240 --> 00:02:23.250 align:start position:0%
there is some invalid transaction in
 

00:02:23.250 --> 00:02:24.830 align:start position:0%
there is some invalid transaction in
that<00:02:23.400><c> block</c><00:02:23.610><c> then</c><00:02:24.210><c> they</c><00:02:24.360><c> will</c><00:02:24.480><c> effectively</c>

00:02:24.830 --> 00:02:24.840 align:start position:0%
that block then they will effectively
 

00:02:24.840 --> 00:02:26.900 align:start position:0%
that block then they will effectively
send<00:02:25.260><c> send</c><00:02:25.680><c> that</c><00:02:25.830><c> likely</c><00:02:26.190><c> and</c><00:02:26.370><c> a</c><00:02:26.490><c> compact</c>

00:02:26.900 --> 00:02:26.910 align:start position:0%
send send that likely and a compact
 

00:02:26.910 --> 00:02:30.380 align:start position:0%
send send that likely and a compact
proof<00:02:27.380><c> that</c><00:02:28.380><c> that</c><00:02:28.590><c> block</c><00:02:28.920><c> contains</c><00:02:29.550><c> invalid</c>

00:02:30.380 --> 00:02:30.390 align:start position:0%
proof that that block contains invalid
 

00:02:30.390 --> 00:02:32.720 align:start position:0%
proof that that block contains invalid
transaction<00:02:30.930><c> and</c><00:02:31.170><c> that</c><00:02:32.040><c> the</c><00:02:32.250><c> size</c><00:02:32.460><c> of</c><00:02:32.610><c> that</c>

00:02:32.720 --> 00:02:32.730 align:start position:0%
transaction and that the size of that
 

00:02:32.730 --> 00:02:35.360 align:start position:0%
transaction and that the size of that
proof<00:02:33.030><c> should</c><00:02:33.930><c> be</c><00:02:34.110><c> significantly</c><00:02:34.770><c> lower</c><00:02:35.010><c> than</c>

00:02:35.360 --> 00:02:35.370 align:start position:0%
proof should be significantly lower than
 

00:02:35.370 --> 00:02:39.710 align:start position:0%
proof should be significantly lower than
the<00:02:35.790><c> size</c><00:02:36.030><c> of</c><00:02:36.180><c> that</c><00:02:36.300><c> block</c><00:02:37.280><c> so</c><00:02:38.300><c> the</c><00:02:39.300><c> big</c><00:02:39.480><c> the</c>

00:02:39.710 --> 00:02:39.720 align:start position:0%
the size of that block so the big the
 

00:02:39.720 --> 00:02:41.449 align:start position:0%
the size of that block so the big the
original<00:02:40.140><c> Bitcoin</c><00:02:40.530><c> white</c><00:02:40.770><c> paper</c><00:02:41.040><c> actually</c>

00:02:41.449 --> 00:02:41.459 align:start position:0%
original Bitcoin white paper actually
 

00:02:41.459 --> 00:02:44.630 align:start position:0%
original Bitcoin white paper actually
and<00:02:42.500><c> briefly</c><00:02:43.500><c> mentions</c><00:02:43.950><c> a</c><00:02:44.070><c> concept</c><00:02:44.400><c> like</c><00:02:44.520><c> this</c>

00:02:44.630 --> 00:02:44.640 align:start position:0%
and briefly mentions a concept like this
 

00:02:44.640 --> 00:02:46.550 align:start position:0%
and briefly mentions a concept like this
called<00:02:45.240><c> alerts</c>

00:02:46.550 --> 00:02:46.560 align:start position:0%
called alerts
 

00:02:46.560 --> 00:02:50.390 align:start position:0%
called alerts
I<00:02:46.590><c> wished</c><00:02:47.150><c> in</c><00:02:48.150><c> a</c><00:02:48.420><c> single</c><00:02:48.720><c> sentence</c><00:02:49.080><c> and</c><00:02:49.440><c> the</c>

00:02:50.390 --> 00:02:50.400 align:start position:0%
I wished in a single sentence and the
 

00:02:50.400 --> 00:02:52.729 align:start position:0%
I wished in a single sentence and the
idea<00:02:50.700><c> of</c><00:02:50.880><c> alerts</c><00:02:51.240><c> as</c><00:02:51.750><c> Satoshi</c><00:02:52.140><c> proposed</c><00:02:52.560><c> them</c>

00:02:52.729 --> 00:02:52.739 align:start position:0%
idea of alerts as Satoshi proposed them
 

00:02:52.739 --> 00:02:55.820 align:start position:0%
idea of alerts as Satoshi proposed them
was<00:02:52.980><c> that</c><00:02:53.160><c> a</c><00:02:53.420><c> full</c><00:02:54.420><c> mode</c><00:02:54.660><c> could</c><00:02:55.080><c> send</c><00:02:55.440><c> a</c><00:02:55.620><c> light</c>

00:02:55.820 --> 00:02:55.830 align:start position:0%
was that a full mode could send a light
 

00:02:55.830 --> 00:02:58.790 align:start position:0%
was that a full mode could send a light
client<00:02:56.280><c> a</c><00:02:56.400><c> message</c><00:02:56.760><c> to</c><00:02:57.540><c> alert</c><00:02:57.810><c> them</c><00:02:58.050><c> that</c><00:02:58.260><c> the</c>

00:02:58.790 --> 00:02:58.800 align:start position:0%
client a message to alert them that the
 

00:02:58.800 --> 00:03:00.680 align:start position:0%
client a message to alert them that the
block<00:02:59.010><c> is</c><00:02:59.040><c> invalid</c><00:02:59.580><c> and</c><00:02:59.730><c> that</c><00:03:00.239><c> would</c><00:03:00.420><c> cause</c>

00:03:00.680 --> 00:03:00.690 align:start position:0%
block is invalid and that would cause
 

00:03:00.690 --> 00:03:02.900 align:start position:0%
block is invalid and that would cause
the<00:03:00.930><c> light</c><00:03:01.080><c> client</c><00:03:01.470><c> to</c><00:03:01.830><c> have</c><00:03:02.430><c> to</c><00:03:02.610><c> redownload</c>

00:03:02.900 --> 00:03:02.910 align:start position:0%
the light client to have to redownload
 

00:03:02.910 --> 00:03:05.570 align:start position:0%
the light client to have to redownload
the<00:03:03.360><c> block</c><00:03:03.600><c> and</c><00:03:03.950><c> validate</c><00:03:04.950><c> that</c><00:03:04.980><c> block</c><00:03:05.280><c> again</c>

00:03:05.570 --> 00:03:05.580 align:start position:0%
the block and validate that block again
 

00:03:05.580 --> 00:03:07.820 align:start position:0%
the block and validate that block again
but<00:03:06.420><c> the</c><00:03:06.510><c> problem</c><00:03:06.810><c> with</c><00:03:06.930><c> is</c><00:03:07.110><c> with</c><00:03:07.500><c> this</c><00:03:07.620><c> is</c>

00:03:07.820 --> 00:03:07.830 align:start position:0%
but the problem with is with this is
 

00:03:07.830 --> 00:03:10.370 align:start position:0%
but the problem with is with this is
that<00:03:08.010><c> as</c><00:03:08.190><c> a</c><00:03:08.220><c> full</c><00:03:08.489><c> node</c><00:03:08.700><c> I</c><00:03:09.030><c> could</c><00:03:09.690><c> just</c><00:03:09.870><c> lie</c><00:03:10.080><c> to</c>

00:03:10.370 --> 00:03:10.380 align:start position:0%
that as a full node I could just lie to
 

00:03:10.380 --> 00:03:12.080 align:start position:0%
that as a full node I could just lie to
all<00:03:10.709><c> the</c><00:03:10.830><c> light</c><00:03:10.950><c> clients</c><00:03:11.400><c> and</c><00:03:11.550><c> say</c><00:03:11.760><c> all</c><00:03:11.970><c> the</c>

00:03:12.080 --> 00:03:12.090 align:start position:0%
all the light clients and say all the
 

00:03:12.090 --> 00:03:14.210 align:start position:0%
all the light clients and say all the
blocks<00:03:12.300><c> are</c><00:03:12.450><c> invalid</c><00:03:12.840><c> and</c><00:03:12.959><c> so</c><00:03:13.530><c> effectively</c>

00:03:14.210 --> 00:03:14.220 align:start position:0%
blocks are invalid and so effectively
 

00:03:14.220 --> 00:03:15.800 align:start position:0%
blocks are invalid and so effectively
the<00:03:14.550><c> were</c><00:03:14.670><c> in</c><00:03:14.820><c> the</c><00:03:14.970><c> worst</c><00:03:15.120><c> case</c><00:03:15.300><c> scenario</c><00:03:15.750><c> the</c>

00:03:15.800 --> 00:03:15.810 align:start position:0%
the were in the worst case scenario the
 

00:03:15.810 --> 00:03:18.740 align:start position:0%
the were in the worst case scenario the
efficiency<00:03:16.470><c> of</c><00:03:16.500><c> the</c><00:03:16.680><c> system</c><00:03:17.570><c> for</c><00:03:18.570><c> lack</c>

00:03:18.740 --> 00:03:18.750 align:start position:0%
efficiency of the system for lack
 

00:03:18.750 --> 00:03:21.289 align:start position:0%
efficiency of the system for lack
clients<00:03:19.290><c> is</c><00:03:19.680><c> no</c><00:03:20.190><c> better</c><00:03:20.459><c> than</c><00:03:21.030><c> downloading</c>

00:03:21.289 --> 00:03:21.299 align:start position:0%
clients is no better than downloading
 

00:03:21.299 --> 00:03:23.690 align:start position:0%
clients is no better than downloading
the<00:03:21.750><c> whole</c><00:03:21.870><c> block</c><00:03:22.080><c> chain</c><00:03:22.290><c> again</c><00:03:22.440><c> so</c><00:03:23.040><c> it</c><00:03:23.370><c> boils</c>

00:03:23.690 --> 00:03:23.700 align:start position:0%
the whole block chain again so it boils
 

00:03:23.700 --> 00:03:25.550 align:start position:0%
the whole block chain again so it boils
down<00:03:23.730><c> to</c><00:03:23.880><c> running</c><00:03:24.209><c> a</c><00:03:24.239><c> full</c><00:03:24.420><c> mode</c><00:03:24.540><c> again</c><00:03:24.810><c> so</c><00:03:25.320><c> it</c>

00:03:25.550 --> 00:03:25.560 align:start position:0%
down to running a full mode again so it
 

00:03:25.560 --> 00:03:31.190 align:start position:0%
down to running a full mode again so it
doesn't<00:03:25.830><c> really</c><00:03:25.950><c> work</c><00:03:29.030><c> also</c><00:03:30.030><c> has</c><00:03:30.930><c> been</c><00:03:31.080><c> some</c>

00:03:31.190 --> 00:03:31.200 align:start position:0%
doesn't really work also has been some
 

00:03:31.200 --> 00:03:34.699 align:start position:0%
doesn't really work also has been some
discussions<00:03:31.650><c> in</c><00:03:32.780><c> the</c><00:03:33.780><c> Bitcoin</c><00:03:33.959><c> space</c><00:03:34.260><c> about</c>

00:03:34.699 --> 00:03:34.709 align:start position:0%
discussions in the Bitcoin space about
 

00:03:34.709 --> 00:03:36.740 align:start position:0%
discussions in the Bitcoin space about
having<00:03:35.010><c> compact</c><00:03:35.670><c> for</c><00:03:35.880><c> troops</c><00:03:36.180><c> which</c><00:03:36.540><c> is</c><00:03:36.630><c> what</c>

00:03:36.740 --> 00:03:36.750 align:start position:0%
having compact for troops which is what
 

00:03:36.750 --> 00:03:38.330 align:start position:0%
having compact for troops which is what
I<00:03:36.780><c> just</c><00:03:36.989><c> discussed</c><00:03:37.320><c> but</c><00:03:37.920><c> some</c><00:03:38.100><c> of</c><00:03:38.220><c> these</c>

00:03:38.330 --> 00:03:38.340 align:start position:0%
I just discussed but some of these
 

00:03:38.340 --> 00:03:41.420 align:start position:0%
I just discussed but some of these
earlier<00:03:38.700><c> proposals</c><00:03:39.360><c> they</c><00:03:40.230><c> propose</c><00:03:41.130><c> a</c>

00:03:41.420 --> 00:03:41.430 align:start position:0%
earlier proposals they propose a
 

00:03:41.430 --> 00:03:44.330 align:start position:0%
earlier proposals they propose a
different<00:03:41.640><c> fraud</c><00:03:42.540><c> proof</c><00:03:42.840><c> for</c><00:03:43.680><c> every</c><00:03:43.980><c> single</c>

00:03:44.330 --> 00:03:44.340 align:start position:0%
different fraud proof for every single
 

00:03:44.340 --> 00:03:47.030 align:start position:0%
different fraud proof for every single
way<00:03:44.459><c> to</c><00:03:44.519><c> violate</c><00:03:45.330><c> the</c><00:03:45.690><c> rules</c><00:03:46.320><c> of</c><00:03:46.560><c> the</c><00:03:46.620><c> protocol</c>

00:03:47.030 --> 00:03:47.040 align:start position:0%
way to violate the rules of the protocol
 

00:03:47.040 --> 00:03:48.680 align:start position:0%
way to violate the rules of the protocol
so<00:03:47.549><c> for</c><00:03:47.730><c> example</c><00:03:48.090><c> you</c><00:03:48.150><c> might</c><00:03:48.269><c> have</c><00:03:48.420><c> one</c><00:03:48.660><c> for</c>

00:03:48.680 --> 00:03:48.690 align:start position:0%
so for example you might have one for
 

00:03:48.690 --> 00:03:50.840 align:start position:0%
so for example you might have one for
three<00:03:49.170><c> for</c><00:03:49.350><c> double</c><00:03:49.590><c> spends</c><00:03:49.830><c> one</c><00:03:50.250><c> for</c><00:03:50.580><c> proof</c>

00:03:50.840 --> 00:03:50.850 align:start position:0%
three for double spends one for proof
 

00:03:50.850 --> 00:03:53.420 align:start position:0%
three for double spends one for proof
for<00:03:51.209><c> utx</c><00:03:51.930><c> is</c><00:03:52.080><c> no</c><00:03:52.170><c> existing</c><00:03:52.650><c> and</c><00:03:52.860><c> so</c><00:03:53.010><c> on</c><00:03:53.160><c> and</c><00:03:53.280><c> so</c>

00:03:53.420 --> 00:03:53.430 align:start position:0%
for utx is no existing and so on and so
 

00:03:53.430 --> 00:03:55.850 align:start position:0%
for utx is no existing and so on and so
forth<00:03:53.730><c> so</c><00:03:54.480><c> what</c><00:03:54.660><c> we</c><00:03:54.750><c> can</c><00:03:54.870><c> do</c><00:03:54.989><c> here</c><00:03:55.260><c> and</c><00:03:55.620><c> what</c>

00:03:55.850 --> 00:03:55.860 align:start position:0%
forth so what we can do here and what
 

00:03:55.860 --> 00:03:57.289 align:start position:0%
forth so what we can do here and what
we're<00:03:55.980><c> going</c><00:03:56.070><c> to</c><00:03:56.130><c> do</c><00:03:56.250><c> here</c><00:03:56.489><c> is</c><00:03:56.730><c> simplify</c>

00:03:57.289 --> 00:03:57.299 align:start position:0%
we're going to do here is simplify
 

00:03:57.299 --> 00:03:59.840 align:start position:0%
we're going to do here is simplify
everything<00:03:57.680><c> so</c><00:03:58.680><c> that</c><00:03:58.830><c> you</c><00:03:58.920><c> only</c><00:03:59.100><c> need</c><00:03:59.340><c> one</c><00:03:59.580><c> for</c>

00:03:59.840 --> 00:03:59.850 align:start position:0%
everything so that you only need one for
 

00:03:59.850 --> 00:04:04.100 align:start position:0%
everything so that you only need one for
proof<00:04:00.090><c> and</c><00:04:02.000><c> to</c><00:04:03.000><c> understand</c><00:04:03.390><c> how</c><00:04:03.630><c> this</c><00:04:03.930><c> could</c>

00:04:04.100 --> 00:04:04.110 align:start position:0%
proof and to understand how this could
 

00:04:04.110 --> 00:04:06.460 align:start position:0%
proof and to understand how this could
work<00:04:04.140><c> is</c><00:04:04.560><c> we</c><00:04:05.190><c> have</c><00:04:05.280><c> to</c><00:04:05.400><c> remind</c><00:04:05.610><c> ourselves</c><00:04:05.820><c> that</c>

00:04:06.460 --> 00:04:06.470 align:start position:0%
work is we have to remind ourselves that
 

00:04:06.470 --> 00:04:08.960 align:start position:0%
work is we have to remind ourselves that
we<00:04:07.470><c> could</c><00:04:07.650><c> generalize</c><00:04:08.070><c> the</c><00:04:08.280><c> blockchain</c><00:04:08.489><c> as</c><00:04:08.910><c> a</c>

00:04:08.960 --> 00:04:08.970 align:start position:0%
we could generalize the blockchain as a
 

00:04:08.970 --> 00:04:11.330 align:start position:0%
we could generalize the blockchain as a
state-transition<00:04:09.330><c> system</c><00:04:10.110><c> which</c><00:04:10.950><c> is</c><00:04:11.100><c> what</c>

00:04:11.330 --> 00:04:11.340 align:start position:0%
state-transition system which is what
 

00:04:11.340 --> 00:04:14.960 align:start position:0%
state-transition system which is what
aetherium<00:04:11.670><c> actually</c><00:04:12.090><c> does</c><00:04:13.459><c> so</c><00:04:14.459><c> effectively</c>

00:04:14.960 --> 00:04:14.970 align:start position:0%
aetherium actually does so effectively
 

00:04:14.970 --> 00:04:18.080 align:start position:0%
aetherium actually does so effectively
you<00:04:15.090><c> have</c><00:04:15.209><c> a</c><00:04:15.239><c> transition</c><00:04:15.690><c> function</c><00:04:16.940><c> you</c><00:04:17.940><c> have</c>

00:04:18.080 --> 00:04:18.090 align:start position:0%
you have a transition function you have
 

00:04:18.090 --> 00:04:20.900 align:start position:0%
you have a transition function you have
that<00:04:18.570><c> takes</c><00:04:18.780><c> in</c><00:04:18.959><c> as</c><00:04:19.200><c> input</c><00:04:19.410><c> the</c><00:04:19.680><c> state</c><00:04:19.919><c> of</c><00:04:20.220><c> the</c>

00:04:20.900 --> 00:04:20.910 align:start position:0%
that takes in as input the state of the
 

00:04:20.910 --> 00:04:23.390 align:start position:0%
that takes in as input the state of the
blockchain<00:04:21.150><c> and</c><00:04:21.540><c> some</c><00:04:21.989><c> transaction</c><00:04:22.560><c> and</c><00:04:22.800><c> then</c>

00:04:23.390 --> 00:04:23.400 align:start position:0%
blockchain and some transaction and then
 

00:04:23.400 --> 00:04:26.420 align:start position:0%
blockchain and some transaction and then
every<00:04:23.760><c> transaction</c><00:04:24.770><c> modifies</c><00:04:25.770><c> the</c><00:04:26.010><c> state</c><00:04:26.250><c> of</c>

00:04:26.420 --> 00:04:26.430 align:start position:0%
every transaction modifies the state of
 

00:04:26.430 --> 00:04:27.090 align:start position:0%
every transaction modifies the state of
the<00:04:26.520><c> blockchain</c>

00:04:27.090 --> 00:04:27.100 align:start position:0%
the blockchain
 

00:04:27.100 --> 00:04:30.090 align:start position:0%
the blockchain
in<00:04:27.160><c> some</c><00:04:27.340><c> way</c><00:04:27.550><c> and</c><00:04:27.820><c> then</c><00:04:28.690><c> so</c><00:04:29.230><c> between</c><00:04:29.620><c> block</c><00:04:29.860><c> X</c>

00:04:30.090 --> 00:04:30.100 align:start position:0%
in some way and then so between block X
 

00:04:30.100 --> 00:04:31.860 align:start position:0%
in some way and then so between block X
I'm<00:04:30.370><c> block</c><00:04:30.580><c> X</c><00:04:30.820><c> plus</c><00:04:31.030><c> 1</c><00:04:31.240><c> you</c><00:04:31.420><c> have</c><00:04:31.540><c> a</c><00:04:31.570><c> number</c><00:04:31.720><c> of</c>

00:04:31.860 --> 00:04:31.870 align:start position:0%
I'm block X plus 1 you have a number of
 

00:04:31.870 --> 00:04:33.420 align:start position:0%
I'm block X plus 1 you have a number of
transactions<00:04:32.410><c> and</c><00:04:32.650><c> they</c><00:04:32.770><c> modify</c><00:04:33.130><c> the</c><00:04:33.190><c> state</c>

00:04:33.420 --> 00:04:33.430 align:start position:0%
transactions and they modify the state
 

00:04:33.430 --> 00:04:35.550 align:start position:0%
transactions and they modify the state
in<00:04:33.550><c> some</c><00:04:33.700><c> way</c><00:04:33.880><c> and</c><00:04:34.210><c> in</c><00:04:35.020><c> between</c><00:04:35.380><c> those</c>

00:04:35.550 --> 00:04:35.560 align:start position:0%
in some way and in between those
 

00:04:35.560 --> 00:04:37.170 align:start position:0%
in some way and in between those
transactions<00:04:36.250><c> if</c><00:04:36.490><c> you</c><00:04:36.700><c> apply</c><00:04:36.970><c> those</c>

00:04:37.170 --> 00:04:37.180 align:start position:0%
transactions if you apply those
 

00:04:37.180 --> 00:04:39.570 align:start position:0%
transactions if you apply those
transactions<00:04:37.810><c> sequentially</c><00:04:38.770><c> you</c><00:04:39.220><c> have</c><00:04:39.370><c> many</c>

00:04:39.570 --> 00:04:39.580 align:start position:0%
transactions sequentially you have many
 

00:04:39.580 --> 00:04:41.820 align:start position:0%
transactions sequentially you have many
intermediate<00:04:40.270><c> states</c><00:04:40.540><c> as</c><00:04:40.810><c> you</c><00:04:41.140><c> can</c><00:04:41.290><c> see</c><00:04:41.440><c> in</c>

00:04:41.820 --> 00:04:41.830 align:start position:0%
intermediate states as you can see in
 

00:04:41.830 --> 00:04:46.760 align:start position:0%
intermediate states as you can see in
the<00:04:41.920><c> diagram</c><00:04:43.080><c> so</c><00:04:44.080><c> what</c><00:04:44.530><c> happens</c><00:04:44.860><c> if</c><00:04:45.390><c> there's</c><00:04:46.390><c> a</c>

00:04:46.760 --> 00:04:46.770 align:start position:0%
the diagram so what happens if there's a
 

00:04:46.770 --> 00:04:49.320 align:start position:0%
the diagram so what happens if there's a
one<00:04:47.770><c> transaction</c><00:04:48.190><c> is</c><00:04:48.520><c> included</c><00:04:48.910><c> in</c><00:04:49.030><c> the</c><00:04:49.120><c> in</c>

00:04:49.320 --> 00:04:49.330 align:start position:0%
one transaction is included in the in
 

00:04:49.330 --> 00:04:51.630 align:start position:0%
one transaction is included in the in
the<00:04:49.450><c> block</c><00:04:49.660><c> that</c><00:04:50.350><c> has</c><00:04:50.530><c> an</c><00:04:50.650><c> invalid</c><00:04:51.220><c> that</c><00:04:51.490><c> is</c>

00:04:51.630 --> 00:04:51.640 align:start position:0%
the block that has an invalid that is
 

00:04:51.640 --> 00:04:54.120 align:start position:0%
the block that has an invalid that is
invalid<00:04:52.120><c> and</c><00:04:52.410><c> modifies</c><00:04:53.410><c> the</c><00:04:53.650><c> state</c><00:04:53.890><c> an</c>

00:04:54.120 --> 00:04:54.130 align:start position:0%
invalid and modifies the state an
 

00:04:54.130 --> 00:04:57.210 align:start position:0%
invalid and modifies the state an
invalid<00:04:54.610><c> way</c><00:04:54.790><c> that</c><00:04:55.780><c> is</c><00:04:56.020><c> illegal</c><00:04:56.710><c> or</c><00:04:57.040><c> not</c>

00:04:57.210 --> 00:04:57.220 align:start position:0%
invalid way that is illegal or not
 

00:04:57.220 --> 00:05:01.200 align:start position:0%
invalid way that is illegal or not
allowed<00:04:58.350><c> so</c><00:04:59.350><c> if</c><00:04:59.590><c> this</c><00:04:59.740><c> is</c><00:04:59.860><c> 50</c><00:05:00.100><c> 51</c><00:05:00.790><c> percent</c>

00:05:01.200 --> 00:05:01.210 align:start position:0%
allowed so if this is 50 51 percent
 

00:05:01.210 --> 00:05:03.150 align:start position:0%
allowed so if this is 50 51 percent
attack<00:05:01.450><c> the</c><00:05:02.110><c> minor</c><00:05:02.350><c> could</c><00:05:02.590><c> do</c><00:05:02.710><c> this</c><00:05:02.860><c> and</c>

00:05:03.150 --> 00:05:03.160 align:start position:0%
attack the minor could do this and
 

00:05:03.160 --> 00:05:05.460 align:start position:0%
attack the minor could do this and
insert<00:05:03.520><c> this</c><00:05:03.850><c> malicious</c><00:05:04.300><c> block</c><00:05:04.540><c> into</c><00:05:05.440><c> the</c>

00:05:05.460 --> 00:05:05.470 align:start position:0%
insert this malicious block into the
 

00:05:05.470 --> 00:05:07.560 align:start position:0%
insert this malicious block into the
chain<00:05:05.770><c> and</c><00:05:05.980><c> like</c><00:05:06.220><c> clients</c><00:05:06.760><c> I'm</c><00:05:07.060><c> sorry</c>

00:05:07.560 --> 00:05:07.570 align:start position:0%
chain and like clients I'm sorry
 

00:05:07.570 --> 00:05:09.150 align:start position:0%
chain and like clients I'm sorry
malicious<00:05:07.930><c> transaction</c><00:05:08.380><c> into</c><00:05:08.620><c> the</c><00:05:08.710><c> chain</c><00:05:08.920><c> and</c>

00:05:09.150 --> 00:05:09.160 align:start position:0%
malicious transaction into the chain and
 

00:05:09.160 --> 00:05:12.450 align:start position:0%
malicious transaction into the chain and
light<00:05:09.790><c> clients</c><00:05:10.150><c> would</c><00:05:10.270><c> happily</c><00:05:10.540><c> accept</c><00:05:10.960><c> it</c><00:05:11.460><c> so</c>

00:05:12.450 --> 00:05:12.460 align:start position:0%
light clients would happily accept it so
 

00:05:12.460 --> 00:05:14.310 align:start position:0%
light clients would happily accept it so
we<00:05:12.550><c> need</c><00:05:12.670><c> a</c><00:05:12.700><c> way</c><00:05:12.760><c> to</c><00:05:12.880><c> prove</c><00:05:13.420><c> we</c><00:05:13.990><c> need</c><00:05:14.110><c> a</c><00:05:14.140><c> way</c><00:05:14.290><c> for</c>

00:05:14.310 --> 00:05:14.320 align:start position:0%
we need a way to prove we need a way for
 

00:05:14.320 --> 00:05:16.620 align:start position:0%
we need a way to prove we need a way for
full<00:05:14.950><c> nerves</c><00:05:15.160><c> to</c><00:05:15.370><c> prove</c><00:05:15.640><c> that</c><00:05:16.270><c> this</c><00:05:16.450><c> has</c>

00:05:16.620 --> 00:05:16.630 align:start position:0%
full nerves to prove that this has
 

00:05:16.630 --> 00:05:18.570 align:start position:0%
full nerves to prove that this has
happened<00:05:16.810><c> so</c><00:05:17.440><c> that</c><00:05:17.470><c> so</c><00:05:17.890><c> that</c><00:05:18.010><c> light</c><00:05:18.160><c> clients</c>

00:05:18.570 --> 00:05:18.580 align:start position:0%
happened so that so that light clients
 

00:05:18.580 --> 00:05:20.700 align:start position:0%
happened so that so that light clients
can<00:05:18.670><c> reject</c><00:05:18.970><c> the</c><00:05:19.060><c> block</c><00:05:19.300><c> as</c><00:05:19.420><c> well</c><00:05:19.450><c> and</c><00:05:19.840><c> we</c><00:05:20.590><c> need</c>

00:05:20.700 --> 00:05:20.710 align:start position:0%
can reject the block as well and we need
 

00:05:20.710 --> 00:05:25.860 align:start position:0%
can reject the block as well and we need
to<00:05:20.800><c> do</c><00:05:20.860><c> this</c><00:05:21.040><c> in</c><00:05:21.220><c> a</c><00:05:21.280><c> compact</c><00:05:21.640><c> way</c><00:05:22.590><c> so</c><00:05:24.780><c> to</c><00:05:25.780><c> do</c>

00:05:25.860 --> 00:05:25.870 align:start position:0%
to do this in a compact way so to do
 

00:05:25.870 --> 00:05:29.970 align:start position:0%
to do this in a compact way so to do
this<00:05:25.990><c> we</c><00:05:26.200><c> needed</c><00:05:26.380><c> some</c><00:05:26.590><c> way</c><00:05:26.620><c> to</c><00:05:28.650><c> commit</c><00:05:29.650><c> to</c><00:05:29.890><c> the</c>

00:05:29.970 --> 00:05:29.980 align:start position:0%
this we needed some way to commit to the
 

00:05:29.980 --> 00:05:33.120 align:start position:0%
this we needed some way to commit to the
state<00:05:30.220><c> of</c><00:05:30.550><c> the</c><00:05:30.700><c> block</c><00:05:30.880><c> chain</c><00:05:31.060><c> in</c><00:05:31.960><c> the</c><00:05:32.230><c> in</c><00:05:32.500><c> in</c>

00:05:33.120 --> 00:05:33.130 align:start position:0%
state of the block chain in the in in
 

00:05:33.130 --> 00:05:35.580 align:start position:0%
state of the block chain in the in in
the<00:05:33.250><c> block</c><00:05:33.700><c> headers</c><00:05:33.970><c> so</c><00:05:34.300><c> at</c><00:05:34.930><c> the</c><00:05:35.080><c> moment</c><00:05:35.440><c> a</c>

00:05:35.580 --> 00:05:35.590 align:start position:0%
the block headers so at the moment a
 

00:05:35.590 --> 00:05:38.310 align:start position:0%
the block headers so at the moment a
theorem<00:05:35.950><c> uses</c><00:05:36.310><c> petrushka</c><00:05:37.270><c> Sri</c><00:05:37.570><c> to</c>

00:05:38.310 --> 00:05:38.320 align:start position:0%
theorem uses petrushka Sri to
 

00:05:38.320 --> 00:05:40.140 align:start position:0%
theorem uses petrushka Sri to
effectively<00:05:38.860><c> represent</c><00:05:39.430><c> the</c><00:05:39.550><c> entire</c><00:05:39.820><c> state</c>

00:05:40.140 --> 00:05:40.150 align:start position:0%
effectively represent the entire state
 

00:05:40.150 --> 00:05:43.320 align:start position:0%
effectively represent the entire state
of<00:05:40.240><c> the</c><00:05:40.330><c> blockchain</c><00:05:40.540><c> in</c><00:05:41.050><c> a</c><00:05:41.170><c> single</c><00:05:41.560><c> route</c><00:05:42.330><c> and</c>

00:05:43.320 --> 00:05:43.330 align:start position:0%
of the blockchain in a single route and
 

00:05:43.330 --> 00:05:45.270 align:start position:0%
of the blockchain in a single route and
you<00:05:43.810><c> can</c><00:05:44.110><c> effectively</c><00:05:44.350><c> represent</c><00:05:44.950><c> the</c><00:05:45.010><c> entire</c>

00:05:45.270 --> 00:05:45.280 align:start position:0%
you can effectively represent the entire
 

00:05:45.280 --> 00:05:46.680 align:start position:0%
you can effectively represent the entire
state<00:05:45.550><c> of</c><00:05:45.670><c> the</c><00:05:45.760><c> blockchain</c><00:05:45.970><c> as</c><00:05:46.240><c> a</c><00:05:46.270><c> key</c><00:05:46.450><c> value</c>

00:05:46.680 --> 00:05:46.690 align:start position:0%
state of the blockchain as a key value
 

00:05:46.690 --> 00:05:49.080 align:start position:0%
state of the blockchain as a key value
store<00:05:46.930><c> ie</c><00:05:47.560><c> the</c><00:05:47.980><c> accounts</c><00:05:48.760><c> in</c><00:05:48.820><c> the</c><00:05:48.910><c> blockchain</c>

00:05:49.080 --> 00:05:49.090 align:start position:0%
store ie the accounts in the blockchain
 

00:05:49.090 --> 00:05:52.620 align:start position:0%
store ie the accounts in the blockchain
and<00:05:49.240><c> values</c><00:05:49.720><c> but</c><00:05:50.500><c> recently</c><00:05:50.950><c> and</c><00:05:51.480><c> one</c><00:05:52.480><c> of</c><00:05:52.570><c> the</c>

00:05:52.620 --> 00:05:52.630 align:start position:0%
and values but recently and one of the
 

00:05:52.630 --> 00:05:54.690 align:start position:0%
and values but recently and one of the
proposed<00:05:52.930><c> changes</c><00:05:53.260><c> in</c><00:05:53.320><c> certain</c><00:05:53.560><c> serenity</c><00:05:54.070><c> is</c>

00:05:54.690 --> 00:05:54.700 align:start position:0%
proposed changes in certain serenity is
 

00:05:54.700 --> 00:05:56.880 align:start position:0%
proposed changes in certain serenity is
to<00:05:55.120><c> actually</c><00:05:55.510><c> change</c><00:05:56.200><c> this</c><00:05:56.410><c> structure</c><00:05:56.860><c> to</c>

00:05:56.880 --> 00:05:56.890 align:start position:0%
to actually change this structure to
 

00:05:56.890 --> 00:05:58.680 align:start position:0%
to actually change this structure to
something<00:05:57.670><c> a</c><00:05:57.850><c> much</c><00:05:58.030><c> simpler</c><00:05:58.390><c> structure</c>

00:05:58.680 --> 00:05:58.690 align:start position:0%
something a much simpler structure
 

00:05:58.690 --> 00:06:01.410 align:start position:0%
something a much simpler structure
called<00:05:59.110><c> the</c><00:05:59.170><c> sparse</c><00:05:59.470><c> Merkle</c><00:05:59.830><c> tree</c><00:06:00.270><c> which</c><00:06:01.270><c> is</c><00:06:01.390><c> a</c>

00:06:01.410 --> 00:06:01.420 align:start position:0%
called the sparse Merkle tree which is a
 

00:06:01.420 --> 00:06:04.530 align:start position:0%
called the sparse Merkle tree which is a
much<00:06:01.600><c> simpler</c><00:06:02.250><c> way</c><00:06:03.250><c> to</c><00:06:03.280><c> actually</c><00:06:03.760><c> store</c><00:06:04.420><c> the</c>

00:06:04.530 --> 00:06:04.540 align:start position:0%
much simpler way to actually store the
 

00:06:04.540 --> 00:06:06.330 align:start position:0%
much simpler way to actually store the
entire<00:06:04.630><c> represent</c><00:06:05.290><c> the</c><00:06:05.350><c> entire</c><00:06:05.590><c> state</c><00:06:05.920><c> as</c><00:06:06.190><c> a</c>

00:06:06.330 --> 00:06:06.340 align:start position:0%
entire represent the entire state as a
 

00:06:06.340 --> 00:06:08.460 align:start position:0%
entire represent the entire state as a
single<00:06:06.640><c> metal</c><00:06:06.820><c> rule</c><00:06:07.090><c> and</c><00:06:07.330><c> the</c><00:06:07.780><c> basic</c><00:06:08.080><c> idea</c><00:06:08.380><c> of</c>

00:06:08.460 --> 00:06:08.470 align:start position:0%
single metal rule and the basic idea of
 

00:06:08.470 --> 00:06:10.740 align:start position:0%
single metal rule and the basic idea of
response<00:06:08.830><c> memory</c><00:06:09.010><c> is</c><00:06:09.730><c> that</c><00:06:10.180><c> it's</c><00:06:10.330><c> basically</c><00:06:10.540><c> a</c>

00:06:10.740 --> 00:06:10.750 align:start position:0%
response memory is that it's basically a
 

00:06:10.750 --> 00:06:12.420 align:start position:0%
response memory is that it's basically a
normal<00:06:11.080><c> map</c><00:06:11.200><c> with</c><00:06:11.380><c> tree</c><00:06:11.590><c> but</c><00:06:12.220><c> with</c><00:06:12.340><c> an</c>

00:06:12.420 --> 00:06:12.430 align:start position:0%
normal map with tree but with an
 

00:06:12.430 --> 00:06:15.810 align:start position:0%
normal map with tree but with an
insanely<00:06:12.820><c> large</c><00:06:13.090><c> number</c><00:06:13.630><c> of</c><00:06:13.810><c> leaves</c><00:06:14.440><c> so</c><00:06:15.250><c> if</c>

00:06:15.810 --> 00:06:15.820 align:start position:0%
insanely large number of leaves so if
 

00:06:15.820 --> 00:06:17.340 align:start position:0%
insanely large number of leaves so if
you<00:06:16.150><c> want</c><00:06:16.300><c> it</c><00:06:16.450><c> for</c><00:06:16.480><c> example</c><00:06:16.900><c> to</c><00:06:17.110><c> represent</c>

00:06:17.340 --> 00:06:17.350 align:start position:0%
you want it for example to represent
 

00:06:17.350 --> 00:06:20.340 align:start position:0%
you want it for example to represent
every<00:06:17.920><c> single</c><00:06:18.250><c> possible</c><00:06:18.610><c> sha-256</c><00:06:19.480><c> hash</c><00:06:19.540><c> then</c>

00:06:20.340 --> 00:06:20.350 align:start position:0%
every single possible sha-256 hash then
 

00:06:20.350 --> 00:06:22.950 align:start position:0%
every single possible sha-256 hash then
the<00:06:20.500><c> size</c><00:06:20.770><c> of</c><00:06:21.040><c> your</c><00:06:21.250><c> Merkle</c><00:06:21.730><c> tree</c><00:06:21.970><c> would</c><00:06:22.780><c> have</c>

00:06:22.950 --> 00:06:22.960 align:start position:0%
the size of your Merkle tree would have
 

00:06:22.960 --> 00:06:25.890 align:start position:0%
the size of your Merkle tree would have
it<00:06:23.770><c> would</c><00:06:23.890><c> have</c><00:06:24.130><c> 2</c><00:06:24.490><c> to</c><00:06:24.640><c> the</c><00:06:24.730><c> power</c><00:06:24.910><c> of</c><00:06:25.150><c> 256</c>

00:06:25.890 --> 00:06:25.900 align:start position:0%
it would have 2 to the power of 256
 

00:06:25.900 --> 00:06:28.710 align:start position:0%
it would have 2 to the power of 256
leaves<00:06:26.350><c> and</c><00:06:26.950><c> you</c><00:06:27.820><c> might</c><00:06:27.940><c> be</c><00:06:28.060><c> asking</c><00:06:28.330><c> how</c><00:06:28.510><c> is</c><00:06:28.570><c> it</c>

00:06:28.710 --> 00:06:28.720 align:start position:0%
leaves and you might be asking how is it
 

00:06:28.720 --> 00:06:30.120 align:start position:0%
leaves and you might be asking how is it
even<00:06:28.900><c> possible</c><00:06:28.930><c> to</c><00:06:29.290><c> actually</c><00:06:29.530><c> compute</c><00:06:30.070><c> this</c>

00:06:30.120 --> 00:06:30.130 align:start position:0%
even possible to actually compute this
 

00:06:30.130 --> 00:06:32.550 align:start position:0%
even possible to actually compute this
macro<00:06:30.460><c> tree</c><00:06:30.640><c> and</c><00:06:30.820><c> actually</c><00:06:31.750><c> there's</c><00:06:32.380><c> some</c>

00:06:32.550 --> 00:06:32.560 align:start position:0%
macro tree and actually there's some
 

00:06:32.560 --> 00:06:34.740 align:start position:0%
macro tree and actually there's some
neat<00:06:32.740><c> tricks</c><00:06:32.770><c> that</c><00:06:33.250><c> you</c><00:06:33.310><c> can</c><00:06:33.430><c> do</c><00:06:33.640><c> such</c><00:06:34.390><c> as</c><00:06:34.570><c> for</c>

00:06:34.740 --> 00:06:34.750 align:start position:0%
neat tricks that you can do such as for
 

00:06:34.750 --> 00:06:36.990 align:start position:0%
neat tricks that you can do such as for
example<00:06:34.780><c> and</c><00:06:35.350><c> if</c><00:06:36.160><c> you</c><00:06:36.340><c> consider</c><00:06:36.520><c> the</c><00:06:36.790><c> fact</c>

00:06:36.990 --> 00:06:37.000 align:start position:0%
example and if you consider the fact
 

00:06:37.000 --> 00:06:38.460 align:start position:0%
example and if you consider the fact
that<00:06:37.150><c> most</c><00:06:37.510><c> of</c><00:06:37.720><c> the</c><00:06:37.870><c> leaves</c><00:06:38.080><c> in</c><00:06:38.290><c> this</c><00:06:38.410><c> tree</c>

00:06:38.460 --> 00:06:38.470 align:start position:0%
that most of the leaves in this tree
 

00:06:38.470 --> 00:06:40.380 align:start position:0%
that most of the leaves in this tree
will<00:06:39.220><c> be</c><00:06:39.370><c> empty</c>

00:06:40.380 --> 00:06:40.390 align:start position:0%
will be empty
 

00:06:40.390 --> 00:06:42.710 align:start position:0%
will be empty
No<00:06:40.630><c> we'll</c><00:06:40.870><c> have</c><00:06:40.990><c> a</c><00:06:41.020><c> zero</c><00:06:41.290><c> or</c><00:06:41.560><c> default</c><00:06:41.860><c> value</c>

00:06:42.710 --> 00:06:42.720 align:start position:0%
No we'll have a zero or default value
 

00:06:42.720 --> 00:06:46.500 align:start position:0%
No we'll have a zero or default value
then<00:06:43.720><c> then</c><00:06:44.650><c> you</c><00:06:44.950><c> can</c><00:06:45.070><c> effectively</c><00:06:45.510><c> assume</c>

00:06:46.500 --> 00:06:46.510 align:start position:0%
then then you can effectively assume
 

00:06:46.510 --> 00:06:49.730 align:start position:0%
then then you can effectively assume
that<00:06:47.140><c> the</c><00:06:47.260><c> vast</c><00:06:47.500><c> majority</c><00:06:47.620><c> of</c><00:06:48.400><c> the</c>

00:06:49.730 --> 00:06:49.740 align:start position:0%
that the vast majority of the
 

00:06:49.740 --> 00:06:52.320 align:start position:0%
that the vast majority of the
intermediate<00:06:50.740><c> nodes</c><00:06:51.040><c> in</c><00:06:51.340><c> this</c><00:06:51.460><c> tree</c><00:06:51.520><c> will</c>

00:06:52.320 --> 00:06:52.330 align:start position:0%
intermediate nodes in this tree will
 

00:06:52.330 --> 00:06:54.330 align:start position:0%
intermediate nodes in this tree will
have<00:06:52.360><c> the</c><00:06:52.660><c> same</c><00:06:52.810><c> value</c><00:06:53.020><c> so</c><00:06:53.860><c> you</c><00:06:53.920><c> don't</c><00:06:54.100><c> have</c><00:06:54.160><c> to</c>

00:06:54.330 --> 00:06:54.340 align:start position:0%
have the same value so you don't have to
 

00:06:54.340 --> 00:06:55.800 align:start position:0%
have the same value so you don't have to
come<00:06:54.490><c> you</c><00:06:54.670><c> don't</c><00:06:54.790><c> have</c><00:06:54.880><c> to</c><00:06:54.970><c> recompute</c><00:06:55.450><c> every</c>

00:06:55.800 --> 00:06:55.810 align:start position:0%
come you don't have to recompute every
 

00:06:55.810 --> 00:06:58.110 align:start position:0%
come you don't have to recompute every
single<00:06:56.140><c> node</c><00:06:56.650><c> in</c><00:06:56.860><c> the</c><00:06:56.950><c> tree</c><00:06:56.980><c> you</c><00:06:57.400><c> can</c><00:06:57.940><c> just</c>

00:06:58.110 --> 00:06:58.120 align:start position:0%
single node in the tree you can just
 

00:06:58.120 --> 00:06:59.550 align:start position:0%
single node in the tree you can just
because<00:06:58.660><c> you</c><00:06:58.780><c> know</c><00:06:58.930><c> that</c><00:06:59.140><c> the</c><00:06:59.260><c> vast</c><00:06:59.440><c> majority</c>

00:06:59.550 --> 00:06:59.560 align:start position:0%
because you know that the vast majority
 

00:06:59.560 --> 00:07:02.610 align:start position:0%
because you know that the vast majority
of<00:07:00.010><c> these</c><00:07:00.370><c> nodes</c><00:07:00.670><c> only</c><00:07:01.450><c> contain</c><00:07:01.810><c> children</c>

00:07:02.610 --> 00:07:02.620 align:start position:0%
of these nodes only contain children
 

00:07:02.620 --> 00:07:06.270 align:start position:0%
of these nodes only contain children
with<00:07:03.070><c> zero</c><00:07:03.580><c> values</c><00:07:04.000><c> so</c><00:07:04.890><c> effectively</c><00:07:05.890><c> it</c><00:07:06.220><c> is</c>

00:07:06.270 --> 00:07:06.280 align:start position:0%
with zero values so effectively it is
 

00:07:06.280 --> 00:07:08.520 align:start position:0%
with zero values so effectively it is
pretty<00:07:06.730><c> much</c><00:07:06.850><c> as</c><00:07:07.030><c> efficient</c><00:07:07.480><c> as</c><00:07:07.660><c> a</c><00:07:08.080><c> standard</c>

00:07:08.520 --> 00:07:08.530 align:start position:0%
pretty much as efficient as a standard
 

00:07:08.530 --> 00:07:12.870 align:start position:0%
pretty much as efficient as a standard
map<00:07:08.740><c> will</c><00:07:08.920><c> be</c><00:07:08.950><c> and</c><00:07:10.350><c> so</c><00:07:11.350><c> if</c><00:07:11.620><c> we</c><00:07:11.800><c> do</c><00:07:11.950><c> this</c><00:07:12.100><c> then</c><00:07:12.550><c> we</c>

00:07:12.870 --> 00:07:12.880 align:start position:0%
map will be and so if we do this then we
 

00:07:12.880 --> 00:07:15.270 align:start position:0%
map will be and so if we do this then we
could<00:07:13.060><c> effectively</c><00:07:13.650><c> do</c><00:07:14.650><c> this</c><00:07:14.770><c> concept</c><00:07:15.160><c> called</c>

00:07:15.270 --> 00:07:15.280 align:start position:0%
could effectively do this concept called
 

00:07:15.280 --> 00:07:18.720 align:start position:0%
could effectively do this concept called
stateless<00:07:15.580><c> or</c><00:07:15.910><c> clients</c><00:07:16.300><c> so</c><00:07:16.930><c> and</c><00:07:17.610><c> instead</c><00:07:18.610><c> of</c>

00:07:18.720 --> 00:07:18.730 align:start position:0%
stateless or clients so and instead of
 

00:07:18.730 --> 00:07:20.730 align:start position:0%
stateless or clients so and instead of
imagining<00:07:19.150><c> the</c><00:07:19.480><c> blockchain</c><00:07:19.690><c> as</c><00:07:20.020><c> a</c><00:07:20.050><c> state</c>

00:07:20.730 --> 00:07:20.740 align:start position:0%
imagining the blockchain as a state
 

00:07:20.740 --> 00:07:22.740 align:start position:0%
imagining the blockchain as a state
transit<00:07:21.100><c> state</c><00:07:21.850><c> transition</c><00:07:22.360><c> system</c>

00:07:22.740 --> 00:07:22.750 align:start position:0%
transit state transition system
 

00:07:22.750 --> 00:07:25.920 align:start position:0%
transit state transition system
imagine<00:07:23.590><c> the</c><00:07:23.680><c> blockchain</c><00:07:23.890><c> as</c><00:07:24.550><c> a</c><00:07:25.060><c> State</c><00:07:25.540><c> Route</c>

00:07:25.920 --> 00:07:25.930 align:start position:0%
imagine the blockchain as a State Route
 

00:07:25.930 --> 00:07:28.230 align:start position:0%
imagine the blockchain as a State Route
transition<00:07:26.590><c> system</c><00:07:26.920><c> because</c><00:07:27.550><c> if</c><00:07:27.730><c> we</c><00:07:27.850><c> use</c><00:07:27.880><c> this</c>

00:07:28.230 --> 00:07:28.240 align:start position:0%
transition system because if we use this
 

00:07:28.240 --> 00:07:30.150 align:start position:0%
transition system because if we use this
map<00:07:28.480><c> called</c><00:07:28.660><c> if</c><00:07:28.870><c> you</c><00:07:29.170><c> use</c><00:07:29.350><c> this</c><00:07:29.530><c> bus</c><00:07:29.770><c> Merkle</c>

00:07:30.150 --> 00:07:30.160 align:start position:0%
map called if you use this bus Merkle
 

00:07:30.160 --> 00:07:32.610 align:start position:0%
map called if you use this bus Merkle
tree<00:07:30.340><c> to</c><00:07:31.150><c> represent</c><00:07:31.570><c> the</c><00:07:32.050><c> state</c><00:07:32.350><c> of</c><00:07:32.530><c> the</c>

00:07:32.610 --> 00:07:32.620 align:start position:0%
tree to represent the state of the
 

00:07:32.620 --> 00:07:34.680 align:start position:0%
tree to represent the state of the
entire<00:07:32.770><c> blockchain</c><00:07:33.370><c> as</c><00:07:33.580><c> a</c><00:07:33.880><c> single</c><00:07:34.390><c> merkel</c>

00:07:34.680 --> 00:07:34.690 align:start position:0%
entire blockchain as a single merkel
 

00:07:34.690 --> 00:07:36.990 align:start position:0%
entire blockchain as a single merkel
root<00:07:34.810><c> and</c><00:07:35.080><c> you</c><00:07:35.950><c> include</c><00:07:36.280><c> this</c><00:07:36.430><c> medical</c><00:07:36.850><c> route</c>

00:07:36.990 --> 00:07:37.000 align:start position:0%
root and you include this medical route
 

00:07:37.000 --> 00:07:38.460 align:start position:0%
root and you include this medical route
in<00:07:37.270><c> every</c><00:07:37.570><c> block</c><00:07:37.720><c> header</c><00:07:37.900><c> which</c><00:07:38.200><c> is</c><00:07:38.230><c> what</c><00:07:38.440><c> a</c>

00:07:38.460 --> 00:07:38.470 align:start position:0%
in every block header which is what a
 

00:07:38.470 --> 00:07:40.410 align:start position:0%
in every block header which is what a
theorem<00:07:38.740><c> is</c><00:07:38.830><c> doing</c><00:07:39.040><c> right</c><00:07:39.160><c> now</c><00:07:39.360><c> using</c><00:07:40.360><c> a</c>

00:07:40.410 --> 00:07:40.420 align:start position:0%
theorem is doing right now using a
 

00:07:40.420 --> 00:07:43.590 align:start position:0%
theorem is doing right now using a
patrasche<00:07:41.050><c> we</c><00:07:41.970><c> then</c><00:07:42.970><c> you</c><00:07:43.090><c> could</c><00:07:43.210><c> also</c><00:07:43.360><c> imagine</c>

00:07:43.590 --> 00:07:43.600 align:start position:0%
patrasche we then you could also imagine
 

00:07:43.600 --> 00:07:46.520 align:start position:0%
patrasche we then you could also imagine
that<00:07:43.930><c> there</c><00:07:44.200><c> are</c><00:07:44.320><c> many</c><00:07:44.500><c> intermediate</c><00:07:45.310><c> routes</c>

00:07:46.520 --> 00:07:46.530 align:start position:0%
that there are many intermediate routes
 

00:07:46.530 --> 00:07:49.740 align:start position:0%
that there are many intermediate routes
between<00:07:47.530><c> block</c><00:07:48.070><c> X</c><00:07:48.310><c> and</c><00:07:48.640><c> block</c><00:07:48.910><c> X</c><00:07:49.120><c> plus</c><00:07:49.330><c> one</c><00:07:49.540><c> or</c>

00:07:49.740 --> 00:07:49.750 align:start position:0%
between block X and block X plus one or
 

00:07:49.750 --> 00:07:54.030 align:start position:0%
between block X and block X plus one or
the<00:07:50.260><c> previous</c><00:07:50.620><c> and</c><00:07:50.890><c> next</c><00:07:50.920><c> books</c><00:07:51.310><c> and</c><00:07:52.050><c> so</c><00:07:53.050><c> if</c>

00:07:54.030 --> 00:07:54.040 align:start position:0%
the previous and next books and so if
 

00:07:54.040 --> 00:07:55.800 align:start position:0%
the previous and next books and so if
you<00:07:54.280><c> effectively</c><00:07:54.700><c> have</c><00:07:54.790><c> this</c><00:07:55.090><c> execution</c>

00:07:55.800 --> 00:07:55.810 align:start position:0%
you effectively have this execution
 

00:07:55.810 --> 00:07:58.830 align:start position:0%
you effectively have this execution
trace<00:07:56.280><c> between</c><00:07:57.280><c> every</c><00:07:57.640><c> for</c><00:07:58.420><c> every</c><00:07:58.450><c> single</c>

00:07:58.830 --> 00:07:58.840 align:start position:0%
trace between every for every single
 

00:07:58.840 --> 00:08:01.830 align:start position:0%
trace between every for every single
transaction<00:07:59.110><c> in</c><00:07:59.650><c> a</c><00:08:00.010><c> block</c><00:08:00.250><c> and</c><00:08:00.490><c> so</c><00:08:01.390><c> what</c><00:08:01.750><c> you</c>

00:08:01.830 --> 00:08:01.840 align:start position:0%
transaction in a block and so what you
 

00:08:01.840 --> 00:08:04.710 align:start position:0%
transaction in a block and so what you
can<00:08:01.990><c> do</c><00:08:02.170><c> is</c><00:08:02.440><c> you</c><00:08:02.620><c> can</c><00:08:02.760><c> not</c><00:08:03.760><c> just</c><00:08:04.000><c> include</c><00:08:04.420><c> the</c>

00:08:04.710 --> 00:08:04.720 align:start position:0%
can do is you can not just include the
 

00:08:04.720 --> 00:08:06.960 align:start position:0%
can do is you can not just include the
final<00:08:05.140><c> state</c><00:08:05.350><c> food</c><00:08:05.620><c> in</c><00:08:05.830><c> the</c><00:08:05.920><c> block</c><00:08:06.070><c> header</c><00:08:06.280><c> you</c>

00:08:06.960 --> 00:08:06.970 align:start position:0%
final state food in the block header you
 

00:08:06.970 --> 00:08:10.380 align:start position:0%
final state food in the block header you
can<00:08:07.120><c> also</c><00:08:07.300><c> include</c><00:08:08.520><c> the</c><00:08:09.520><c> intermediate</c><00:08:10.120><c> state</c>

00:08:10.380 --> 00:08:10.390 align:start position:0%
can also include the intermediate state
 

00:08:10.390 --> 00:08:13.080 align:start position:0%
can also include the intermediate state
foods<00:08:10.600><c> in</c><00:08:10.990><c> the</c><00:08:11.620><c> block</c><00:08:11.770><c> header</c><00:08:11.980><c> so</c><00:08:12.580><c> for</c><00:08:12.760><c> example</c>

00:08:13.080 --> 00:08:13.090 align:start position:0%
foods in the block header so for example
 

00:08:13.090 --> 00:08:15.360 align:start position:0%
foods in the block header so for example
if<00:08:13.210><c> you</c><00:08:13.300><c> wanted</c><00:08:13.540><c> to</c><00:08:13.690><c> you</c><00:08:13.900><c> could</c><00:08:13.990><c> include</c><00:08:14.410><c> after</c>

00:08:15.360 --> 00:08:15.370 align:start position:0%
if you wanted to you could include after
 

00:08:15.370 --> 00:08:17.010 align:start position:0%
if you wanted to you could include after
every<00:08:15.580><c> single</c><00:08:15.730><c> transaction</c><00:08:16.180><c> you</c><00:08:16.870><c> could</c>

00:08:17.010 --> 00:08:17.020 align:start position:0%
every single transaction you could
 

00:08:17.020 --> 00:08:19.410 align:start position:0%
every single transaction you could
include<00:08:17.290><c> the</c><00:08:17.620><c> new</c><00:08:17.830><c> state</c><00:08:18.400><c> route</c><00:08:18.670><c> which</c><00:08:18.940><c> is</c><00:08:19.090><c> the</c>

00:08:19.410 --> 00:08:19.420 align:start position:0%
include the new state route which is the
 

00:08:19.420 --> 00:08:22.650 align:start position:0%
include the new state route which is the
newest<00:08:19.660><c> 80</c><00:08:19.930><c> 80</c><00:08:20.620><c> bytes</c><00:08:20.890><c> state</c><00:08:21.130><c> route</c><00:08:21.340><c> or</c><00:08:22.210><c> you</c>

00:08:22.650 --> 00:08:22.660 align:start position:0%
newest 80 80 bytes state route or you
 

00:08:22.660 --> 00:08:24.540 align:start position:0%
newest 80 80 bytes state route or you
could<00:08:22.810><c> do</c><00:08:22.930><c> after</c><00:08:23.320><c> every</c><00:08:23.650><c> few</c><00:08:23.980><c> transactions</c>

00:08:24.540 --> 00:08:24.550 align:start position:0%
could do after every few transactions
 

00:08:24.550 --> 00:08:26.640 align:start position:0%
could do after every few transactions
it's<00:08:25.240><c> basically</c><00:08:25.540><c> a</c><00:08:25.630><c> trade-off</c><00:08:25.900><c> between</c><00:08:26.050><c> how</c>

00:08:26.640 --> 00:08:26.650 align:start position:0%
it's basically a trade-off between how
 

00:08:26.650 --> 00:08:29.850 align:start position:0%
it's basically a trade-off between how
big<00:08:27.160><c> the</c><00:08:27.310><c> for</c><00:08:27.490><c> proof</c><00:08:27.700><c> is</c><00:08:27.850><c> and</c><00:08:28.180><c> how</c><00:08:29.140><c> much</c><00:08:29.290><c> extra</c>

00:08:29.850 --> 00:08:29.860 align:start position:0%
big the for proof is and how much extra
 

00:08:29.860 --> 00:08:31.800 align:start position:0%
big the for proof is and how much extra
unchained<00:08:30.280><c> there</c><00:08:30.490><c> that</c><00:08:31.180><c> you</c><00:08:31.360><c> that</c><00:08:31.720><c> you</c><00:08:31.780><c> want</c>

00:08:31.800 --> 00:08:31.810 align:start position:0%
unchained there that you that you want
 

00:08:31.810 --> 00:08:35.790 align:start position:0%
unchained there that you that you want
to<00:08:32.020><c> put</c><00:08:32.140><c> in</c><00:08:32.260><c> chain</c><00:08:32.610><c> so</c><00:08:33.610><c> if</c><00:08:33.820><c> you</c><00:08:33.880><c> want</c><00:08:34.030><c> so</c><00:08:34.800><c> so</c>

00:08:35.790 --> 00:08:35.800 align:start position:0%
to put in chain so if you want so so
 

00:08:35.800 --> 00:08:37.230 align:start position:0%
to put in chain so if you want so so
then<00:08:36.010><c> you</c><00:08:36.160><c> could</c><00:08:36.310><c> easily</c><00:08:36.520><c> generate</c><00:08:36.970><c> a</c><00:08:37.000><c> full</c>

00:08:37.230 --> 00:08:37.240 align:start position:0%
then you could easily generate a full
 

00:08:37.240 --> 00:08:39.600 align:start position:0%
then you could easily generate a full
proof<00:08:37.650><c> if</c><00:08:38.650><c> you</c><00:08:38.770><c> have</c><00:08:38.890><c> this</c><00:08:39.040><c> intermediate</c>

00:08:39.600 --> 00:08:39.610 align:start position:0%
proof if you have this intermediate
 

00:08:39.610 --> 00:08:43.260 align:start position:0%
proof if you have this intermediate
state<00:08:39.820><c> routes</c><00:08:40.090><c> in</c><00:08:40.570><c> the</c><00:08:40.600><c> blocks</c><00:08:42.270><c> effectively</c>

00:08:43.260 --> 00:08:43.270 align:start position:0%
state routes in the blocks effectively
 

00:08:43.270 --> 00:08:45.960 align:start position:0%
state routes in the blocks effectively
the<00:08:43.750><c> fourth</c><00:08:44.020><c> proof</c><00:08:44.260><c> would</c><00:08:44.440><c> consist</c><00:08:44.800><c> of</c><00:08:44.970><c> the</c>

00:08:45.960 --> 00:08:45.970 align:start position:0%
the fourth proof would consist of the
 

00:08:45.970 --> 00:08:48.030 align:start position:0%
the fourth proof would consist of the
pre<00:08:46.180><c> state</c><00:08:46.420><c> routes</c><00:08:46.750><c> of</c><00:08:46.960><c> a</c><00:08:47.110><c> transaction</c><00:08:47.440><c> the</c>

00:08:48.030 --> 00:08:48.040 align:start position:0%
pre state routes of a transaction the
 

00:08:48.040 --> 00:08:51.080 align:start position:0%
pre state routes of a transaction the
post<00:08:48.670><c> State</c><00:08:48.880><c> Route</c><00:08:49.320><c> transaction</c><00:08:50.320><c> itself</c><00:08:50.590><c> and</c>

00:08:51.080 --> 00:08:51.090 align:start position:0%
post State Route transaction itself and
 

00:08:51.090 --> 00:08:53.879 align:start position:0%
post State Route transaction itself and
also<00:08:52.090><c> the</c><00:08:52.270><c> witnesses</c><00:08:52.690><c> of</c><00:08:52.720><c> that</c><00:08:52.900><c> transaction</c>

00:08:53.879 --> 00:08:53.889 align:start position:0%
also the witnesses of that transaction
 

00:08:53.889 --> 00:08:55.470 align:start position:0%
also the witnesses of that transaction
then<00:08:54.040><c> the</c><00:08:54.129><c> witnesses</c><00:08:54.519><c> of</c><00:08:54.549><c> a</c><00:08:54.699><c> transaction</c><00:08:55.029><c> are</c>

00:08:55.470 --> 00:08:55.480 align:start position:0%
then the witnesses of a transaction are
 

00:08:55.480 --> 00:08:59.579 align:start position:0%
then the witnesses of a transaction are
simply<00:08:56.019><c> all</c><00:08:56.619><c> the</c><00:08:57.189><c> Merkel</c><00:08:57.549><c> proofs</c><00:08:57.850><c> of</c><00:08:58.410><c> all</c><00:08:59.410><c> of</c>

00:08:59.579 --> 00:08:59.589 align:start position:0%
simply all the Merkel proofs of all of
 

00:08:59.589 --> 00:09:03.150 align:start position:0%
simply all the Merkel proofs of all of
the<00:08:59.739><c> state</c><00:09:00.119><c> keys</c><00:09:01.230><c> that</c><00:09:02.230><c> a</c><00:09:02.499><c> transaction</c>

00:09:03.150 --> 00:09:03.160 align:start position:0%
the state keys that a transaction
 

00:09:03.160 --> 00:09:07.220 align:start position:0%
the state keys that a transaction
accesses<00:09:03.879><c> in</c><00:09:04.209><c> the</c><00:09:04.720><c> state</c><00:09:05.429><c> Merkle</c><00:09:06.429><c> tree</c><00:09:06.819><c> and</c>

00:09:07.220 --> 00:09:07.230 align:start position:0%
accesses in the state Merkle tree and
 

00:09:07.230 --> 00:09:09.479 align:start position:0%
accesses in the state Merkle tree and
then<00:09:08.230><c> you</c><00:09:08.259><c> will</c><00:09:08.410><c> also</c><00:09:08.559><c> need</c><00:09:08.769><c> the</c><00:09:08.829><c> malko</c><00:09:09.189><c> proofs</c>

00:09:09.479 --> 00:09:09.489 align:start position:0%
then you will also need the malko proofs
 

00:09:09.489 --> 00:09:11.340 align:start position:0%
then you will also need the malko proofs
for<00:09:09.670><c> the</c><00:09:09.759><c> transaction</c><00:09:10.179><c> itself</c><00:09:10.299><c> and</c><00:09:10.749><c> the</c><00:09:11.139><c> free</c>

00:09:11.340 --> 00:09:11.350 align:start position:0%
for the transaction itself and the free
 

00:09:11.350 --> 00:09:13.949 align:start position:0%
for the transaction itself and the free
and<00:09:11.589><c> post</c><00:09:11.980><c> a</c><00:09:12.160><c> tweet</c><00:09:12.389><c> so</c><00:09:13.389><c> then</c><00:09:13.540><c> this</c><00:09:13.720><c> is</c><00:09:13.839><c> what</c>

00:09:13.949 --> 00:09:13.959 align:start position:0%
and post a tweet so then this is what
 

00:09:13.959 --> 00:09:16.199 align:start position:0%
and post a tweet so then this is what
effectively<00:09:14.470><c> what</c><00:09:15.189><c> the</c><00:09:15.309><c> fourth</c><00:09:15.549><c> proof</c><00:09:15.790><c> would</c>

00:09:16.199 --> 00:09:16.209 align:start position:0%
effectively what the fourth proof would
 

00:09:16.209 --> 00:09:21.809 align:start position:0%
effectively what the fourth proof would
look<00:09:16.389><c> like</c><00:09:17.369><c> and</c><00:09:18.629><c> so</c><00:09:19.799><c> that's</c><00:09:20.799><c> all</c><00:09:20.949><c> good</c><00:09:21.309><c> so</c><00:09:21.579><c> now</c>

00:09:21.809 --> 00:09:21.819 align:start position:0%
look like and so that's all good so now
 

00:09:21.819 --> 00:09:24.539 align:start position:0%
look like and so that's all good so now
we<00:09:21.879><c> have</c><00:09:22.089><c> a</c><00:09:22.119><c> working</c><00:09:23.009><c> unified</c><00:09:24.009><c> foolproof</c>

00:09:24.539 --> 00:09:24.549 align:start position:0%
we have a working unified foolproof
 

00:09:24.549 --> 00:09:26.849 align:start position:0%
we have a working unified foolproof
system<00:09:24.819><c> that</c><00:09:25.299><c> only</c><00:09:25.480><c> requires</c><00:09:25.899><c> one</c><00:09:26.079><c> single</c><00:09:26.679><c> for</c>

00:09:26.849 --> 00:09:26.859 align:start position:0%
system that only requires one single for
 

00:09:26.859 --> 00:09:28.829 align:start position:0%
system that only requires one single for
proof<00:09:27.100><c> rather</c><00:09:27.819><c> than</c><00:09:28.089><c> many</c><00:09:28.329><c> different</c><00:09:28.689><c> for</c>

00:09:28.829 --> 00:09:28.839 align:start position:0%
proof rather than many different for
 

00:09:28.839 --> 00:09:30.509 align:start position:0%
proof rather than many different for
proofs<00:09:29.139><c> like</c><00:09:29.410><c> some</c><00:09:29.769><c> of</c><00:09:29.859><c> the</c><00:09:29.919><c> earlier</c><00:09:30.160><c> ideas</c>

00:09:30.509 --> 00:09:30.519 align:start position:0%
proofs like some of the earlier ideas
 

00:09:30.519 --> 00:09:34.249 align:start position:0%
proofs like some of the earlier ideas
were<00:09:31.359><c> proposing</c><00:09:32.220><c> but</c><00:09:33.220><c> the</c><00:09:33.369><c> problem</c><00:09:33.699><c> with</c><00:09:33.910><c> this</c>

00:09:34.249 --> 00:09:34.259 align:start position:0%
were proposing but the problem with this
 

00:09:34.259 --> 00:09:36.559 align:start position:0%
were proposing but the problem with this
the<00:09:35.259><c> biggest</c><00:09:35.739><c> problem</c><00:09:35.980><c> with</c><00:09:36.069><c> this</c><00:09:36.220><c> is</c>

00:09:36.559 --> 00:09:36.569 align:start position:0%
the biggest problem with this is
 

00:09:36.569 --> 00:09:38.579 align:start position:0%
the biggest problem with this is
something<00:09:37.569><c> called</c><00:09:37.899><c> the</c><00:09:37.989><c> data</c><00:09:38.109><c> availability</c>

00:09:38.579 --> 00:09:38.589 align:start position:0%
something called the data availability
 

00:09:38.589 --> 00:09:41.129 align:start position:0%
something called the data availability
problem<00:09:38.919><c> and</c><00:09:39.449><c> the</c><00:09:40.449><c> data</c><00:09:40.629><c> availability</c>

00:09:41.129 --> 00:09:41.139 align:start position:0%
problem and the data availability
 

00:09:41.139 --> 00:09:45.049 align:start position:0%
problem and the data availability
problem<00:09:41.579><c> it</c><00:09:42.579><c> effectively</c><00:09:43.029><c> says</c><00:09:43.269><c> that</c><00:09:43.709><c> okay</c><00:09:44.709><c> so</c>

00:09:45.049 --> 00:09:45.059 align:start position:0%
problem it effectively says that okay so
 

00:09:45.059 --> 00:09:48.749 align:start position:0%
problem it effectively says that okay so
what<00:09:46.059><c> if</c><00:09:46.149><c> a</c><00:09:46.269><c> miner</c><00:09:46.509><c> only</c><00:09:47.439><c> distributes</c><00:09:48.009><c> the</c>

00:09:48.749 --> 00:09:48.759 align:start position:0%
what if a miner only distributes the
 

00:09:48.759 --> 00:09:51.780 align:start position:0%
what if a miner only distributes the
block<00:09:48.999><c> headers</c><00:09:49.359><c> to</c><00:09:49.689><c> the</c><00:09:50.290><c> like</c><00:09:50.410><c> clients</c><00:09:50.859><c> so</c>

00:09:51.780 --> 00:09:51.790 align:start position:0%
block headers to the like clients so
 

00:09:51.790 --> 00:09:53.249 align:start position:0%
block headers to the like clients so
like<00:09:52.299><c> clients</c><00:09:52.720><c> or</c><00:09:52.839><c> you</c><00:09:52.929><c> know</c><00:09:53.019><c> the</c><00:09:53.109><c> block</c>

00:09:53.249 --> 00:09:53.259 align:start position:0%
like clients or you know the block
 

00:09:53.259 --> 00:09:56.249 align:start position:0%
like clients or you know the block
headers<00:09:53.559><c> but</c><00:09:54.249><c> what</c><00:09:54.399><c> if</c><00:09:54.549><c> no</c><00:09:54.759><c> one</c><00:09:54.790><c> knows</c><00:09:55.689><c> the</c>

00:09:56.249 --> 00:09:56.259 align:start position:0%
headers but what if no one knows the
 

00:09:56.259 --> 00:09:59.579 align:start position:0%
headers but what if no one knows the
actual<00:09:56.519><c> transaction</c><00:09:57.519><c> data</c><00:09:57.850><c> of</c><00:09:58.119><c> the</c><00:09:58.239><c> book</c><00:09:58.589><c> so</c>

00:09:59.579 --> 00:09:59.589 align:start position:0%
actual transaction data of the book so
 

00:09:59.589 --> 00:10:01.799 align:start position:0%
actual transaction data of the book so
just<00:10:00.309><c> because</c><00:10:00.519><c> in</c><00:10:00.639><c> the</c><00:10:00.790><c> merkel</c><00:10:01.119><c> route</c><00:10:01.299><c> for</c><00:10:01.749><c> the</c>

00:10:01.799 --> 00:10:01.809 align:start position:0%
just because in the merkel route for the
 

00:10:01.809 --> 00:10:03.840 align:start position:0%
just because in the merkel route for the
transactions<00:10:02.319><c> doesn't</c><00:10:03.189><c> mean</c><00:10:03.279><c> you</c><00:10:03.369><c> know</c><00:10:03.519><c> what</c>

00:10:03.840 --> 00:10:03.850 align:start position:0%
transactions doesn't mean you know what
 

00:10:03.850 --> 00:10:07.919 align:start position:0%
transactions doesn't mean you know what
the<00:10:04.720><c> data</c><00:10:04.899><c> behind</c><00:10:05.139><c> that</c><00:10:05.319><c> my</c><00:10:05.529><c> fluid</c><00:10:05.860><c> is</c><00:10:06.209><c> so</c><00:10:07.209><c> if</c><00:10:07.779><c> a</c>

00:10:07.919 --> 00:10:07.929 align:start position:0%
the data behind that my fluid is so if a
 

00:10:07.929 --> 00:10:11.850 align:start position:0%
the data behind that my fluid is so if a
miner<00:10:08.139><c> does</c><00:10:08.350><c> this</c><00:10:08.529><c> then</c><00:10:09.399><c> that</c><00:10:09.429><c> means</c><00:10:09.819><c> a</c><00:10:10.860><c> full</c>

00:10:11.850 --> 00:10:11.860 align:start position:0%
miner does this then that means a full
 

00:10:11.860 --> 00:10:13.919 align:start position:0%
miner does this then that means a full
node<00:10:12.069><c> wouldn't</c><00:10:12.489><c> be</c><00:10:12.549><c> able</c><00:10:12.639><c> to</c><00:10:12.999><c> generate</c><00:10:13.269><c> afford</c>

00:10:13.919 --> 00:10:13.929 align:start position:0%
node wouldn't be able to generate afford
 

00:10:13.929 --> 00:10:15.239 align:start position:0%
node wouldn't be able to generate afford
proof<00:10:14.110><c> because</c><00:10:14.379><c> they</c><00:10:14.589><c> simply</c><00:10:14.889><c> would</c><00:10:15.009><c> not</c><00:10:15.040><c> have</c>

00:10:15.239 --> 00:10:15.249 align:start position:0%
proof because they simply would not have
 

00:10:15.249 --> 00:10:16.590 align:start position:0%
proof because they simply would not have
the<00:10:15.399><c> data</c><00:10:15.579><c> for</c><00:10:15.790><c> that</c><00:10:15.819><c> they</c><00:10:16.269><c> would</c><00:10:16.389><c> not</c><00:10:16.480><c> have</c>

00:10:16.590 --> 00:10:16.600 align:start position:0%
the data for that they would not have
 

00:10:16.600 --> 00:10:18.960 align:start position:0%
the data for that they would not have
the<00:10:16.689><c> data</c><00:10:16.809><c> to</c><00:10:17.079><c> generate</c><00:10:17.230><c> that</c><00:10:17.529><c> for</c><00:10:17.709><c> proof</c><00:10:17.970><c> so</c>

00:10:18.960 --> 00:10:18.970 align:start position:0%
the data to generate that for proof so
 

00:10:18.970 --> 00:10:21.030 align:start position:0%
the data to generate that for proof so
so<00:10:19.449><c> we</c><00:10:19.600><c> need</c><00:10:19.749><c> a</c><00:10:19.779><c> way</c><00:10:19.929><c> somehow</c><00:10:20.290><c> to</c><00:10:20.410><c> guarantee</c>

00:10:21.030 --> 00:10:21.040 align:start position:0%
so we need a way somehow to guarantee
 

00:10:21.040 --> 00:10:24.179 align:start position:0%
so we need a way somehow to guarantee
the<00:10:21.279><c> data</c><00:10:21.910><c> availability</c><00:10:22.329><c> or</c><00:10:22.919><c> availability</c><00:10:23.919><c> of</c>

00:10:24.179 --> 00:10:24.189 align:start position:0%
the data availability or availability of
 

00:10:24.189 --> 00:10:28.019 align:start position:0%
the data availability or availability of
the<00:10:24.249><c> data</c><00:10:24.399><c> in</c><00:10:24.850><c> the</c><00:10:25.179><c> blockchain</c><00:10:25.419><c> and</c>

00:10:28.019 --> 00:10:28.029 align:start position:0%
 
 

00:10:28.029 --> 00:10:30.059 align:start position:0%
 
Vitalik<00:10:28.779><c> proposed</c><00:10:29.110><c> neat</c><00:10:29.589><c> way</c><00:10:29.799><c> to</c><00:10:29.829><c> do</c><00:10:30.009><c> this</c>

00:10:30.059 --> 00:10:30.069 align:start position:0%
Vitalik proposed neat way to do this
 

00:10:30.069 --> 00:10:33.509 align:start position:0%
Vitalik proposed neat way to do this
called<00:10:30.610><c> an</c><00:10:31.110><c> array</c><00:10:32.110><c> using</c><00:10:32.679><c> array</c><00:10:32.889><c> geocoding</c>

00:10:33.509 --> 00:10:33.519 align:start position:0%
called an array using array geocoding
 

00:10:33.519 --> 00:10:36.720 align:start position:0%
called an array using array geocoding
and<00:10:33.899><c> the</c><00:10:34.899><c> the</c><00:10:35.350><c> idea</c><00:10:35.679><c> of</c><00:10:35.829><c> region</c><00:10:36.220><c> coding</c><00:10:36.399><c> is</c>

00:10:36.720 --> 00:10:36.730 align:start position:0%
and the the idea of region coding is
 

00:10:36.730 --> 00:10:38.909 align:start position:0%
and the the idea of region coding is
that<00:10:37.029><c> let's</c><00:10:37.869><c> suppose</c><00:10:38.110><c> that</c><00:10:38.169><c> you</c><00:10:38.559><c> have</c><00:10:38.709><c> some</c>

00:10:38.909 --> 00:10:38.919 align:start position:0%
that let's suppose that you have some
 

00:10:38.919 --> 00:10:44.340 align:start position:0%
that let's suppose that you have some
data<00:10:39.129><c> that</c><00:10:39.519><c> is</c><00:10:40.209><c> X</c><00:10:40.679><c> pieces</c><00:10:41.679><c> long</c><00:10:43.019><c> what</c><00:10:44.019><c> you</c><00:10:44.139><c> can</c>

00:10:44.340 --> 00:10:44.350 align:start position:0%
data that is X pieces long what you can
 

00:10:44.350 --> 00:10:47.850 align:start position:0%
data that is X pieces long what you can
do<00:10:44.559><c> is</c><00:10:44.889><c> you</c><00:10:45.100><c> can</c><00:10:45.220><c> blow</c><00:10:45.519><c> up</c><00:10:45.699><c> that</c><00:10:45.879><c> data</c><00:10:46.059><c> to</c><00:10:47.049><c> two</c><00:10:47.619><c> x</c>

00:10:47.850 --> 00:10:47.860 align:start position:0%
do is you can blow up that data to two x
 

00:10:47.860 --> 00:10:52.049 align:start position:0%
do is you can blow up that data to two x
pieces<00:10:48.429><c> long</c><00:10:48.610><c> and</c><00:10:49.379><c> then</c><00:10:50.379><c> if</c><00:10:50.769><c> you</c><00:10:51.220><c> lose</c><00:10:51.429><c> any</c><00:10:51.730><c> X</c>

00:10:52.049 --> 00:10:52.059 align:start position:0%
pieces long and then if you lose any X
 

00:10:52.059 --> 00:10:54.479 align:start position:0%
pieces long and then if you lose any X
pieces<00:10:52.569><c> in</c><00:10:52.689><c> that</c><00:10:52.809><c> data</c><00:10:53.019><c> you</c><00:10:53.769><c> can</c><00:10:53.949><c> recover</c><00:10:54.220><c> the</c>

00:10:54.479 --> 00:10:54.489 align:start position:0%
pieces in that data you can recover the
 

00:10:54.489 --> 00:10:57.409 align:start position:0%
pieces in that data you can recover the
entire<00:10:54.639><c> data</c><00:10:55.179><c> from</c><00:10:55.899><c> any</c><00:10:56.139><c> of</c><00:10:56.350><c> those</c><00:10:56.529><c> X</c><00:10:56.769><c> pieces</c>

00:10:57.409 --> 00:10:57.419 align:start position:0%
entire data from any of those X pieces
 

00:10:57.419 --> 00:11:01.079 align:start position:0%
entire data from any of those X pieces
so<00:10:58.769><c> what</c><00:10:59.769><c> that</c><00:10:59.919><c> effectively</c><00:11:00.309><c> means</c><00:11:00.759><c> is</c><00:11:01.059><c> that</c>

00:11:01.079 --> 00:11:01.089 align:start position:0%
so what that effectively means is that
 

00:11:01.089 --> 00:11:04.739 align:start position:0%
so what that effectively means is that
this<00:11:01.359><c> no</c><00:11:01.600><c> longer</c><00:11:01.869><c> becomes</c><00:11:02.230><c> a</c><00:11:03.239><c> 100%</c><00:11:04.239><c> data</c>

00:11:04.739 --> 00:11:04.749 align:start position:0%
this no longer becomes a 100% data
 

00:11:04.749 --> 00:11:06.400 align:start position:0%
this no longer becomes a 100% data
availability<00:11:05.259><c> problem</c>

00:11:06.400 --> 00:11:06.410 align:start position:0%
availability problem
 

00:11:06.410 --> 00:11:09.009 align:start position:0%
availability problem
it<00:11:06.709><c> only</c><00:11:07.009><c> becomes</c><00:11:07.370><c> a</c><00:11:07.579><c> 50%</c><00:11:08.209><c> if</c><00:11:08.360><c> they</c><00:11:08.509><c> develop</c><00:11:08.959><c> a</c>

00:11:09.009 --> 00:11:09.019 align:start position:0%
it only becomes a 50% if they develop a
 

00:11:09.019 --> 00:11:11.170 align:start position:0%
it only becomes a 50% if they develop a
problem<00:11:09.259><c> because</c><00:11:09.949><c> you</c><00:11:10.220><c> can</c><00:11:10.370><c> recover</c><00:11:10.610><c> 100%</c>

00:11:11.170 --> 00:11:11.180 align:start position:0%
problem because you can recover 100%
 

00:11:11.180 --> 00:11:16.990 align:start position:0%
problem because you can recover 100%
data<00:11:12.430><c> just</c><00:11:13.430><c> from</c><00:11:13.670><c> 50%</c><00:11:14.060><c> of</c><00:11:14.360><c> their</c><00:11:15.430><c> so</c><00:11:16.430><c> what</c><00:11:16.910><c> that</c>

00:11:16.990 --> 00:11:17.000 align:start position:0%
data just from 50% of their so what that
 

00:11:17.000 --> 00:11:19.569 align:start position:0%
data just from 50% of their so what that
means<00:11:17.240><c> is</c><00:11:17.660><c> that</c><00:11:17.720><c> miners</c><00:11:18.230><c> if</c><00:11:18.560><c> they</c><00:11:19.250><c> wanted</c><00:11:19.519><c> to</c>

00:11:19.569 --> 00:11:19.579 align:start position:0%
means is that miners if they wanted to
 

00:11:19.579 --> 00:11:21.730 align:start position:0%
means is that miners if they wanted to
hide<00:11:19.790><c> a</c><00:11:20.089><c> single</c><00:11:20.480><c> even</c><00:11:20.629><c> a</c><00:11:20.810><c> single</c><00:11:21.019><c> bit</c><00:11:21.379><c> or</c>

00:11:21.730 --> 00:11:21.740 align:start position:0%
hide a single even a single bit or
 

00:11:21.740 --> 00:11:24.429 align:start position:0%
hide a single even a single bit or
single<00:11:22.160><c> byte</c><00:11:22.370><c> in</c><00:11:22.699><c> data</c><00:11:23.000><c> they</c><00:11:23.990><c> will</c><00:11:24.139><c> have</c><00:11:24.290><c> to</c>

00:11:24.429 --> 00:11:24.439 align:start position:0%
single byte in data they will have to
 

00:11:24.439 --> 00:11:27.069 align:start position:0%
single byte in data they will have to
hide<00:11:24.649><c> at</c><00:11:24.980><c> least</c><00:11:25.250><c> 50%</c><00:11:25.730><c> over</c><00:11:26.300><c> there</c><00:11:26.480><c> or</c><00:11:26.779><c> not</c>

00:11:27.069 --> 00:11:27.079 align:start position:0%
hide at least 50% over there or not
 

00:11:27.079 --> 00:11:31.869 align:start position:0%
hide at least 50% over there or not
release<00:11:27.410><c> 50%</c><00:11:28.069><c> of</c><00:11:28.189><c> that</c><00:11:28.220><c> they</c><00:11:28.430><c> are</c><00:11:29.199><c> so</c><00:11:30.790><c> what</c><00:11:31.790><c> we</c>

00:11:31.869 --> 00:11:31.879 align:start position:0%
release 50% of that they are so what we
 

00:11:31.879 --> 00:11:33.129 align:start position:0%
release 50% of that they are so what we
can<00:11:32.000><c> do</c><00:11:32.120><c> with</c><00:11:32.269><c> this</c><00:11:32.360><c> is</c><00:11:32.540><c> we</c><00:11:32.660><c> can</c><00:11:32.810><c> require</c>

00:11:33.129 --> 00:11:33.139 align:start position:0%
can do with this is we can require
 

00:11:33.139 --> 00:11:36.579 align:start position:0%
can do with this is we can require
miners<00:11:33.740><c> to</c><00:11:33.980><c> commit</c><00:11:34.370><c> to</c><00:11:34.850><c> the</c><00:11:35.720><c> medical</c><00:11:36.110><c> route</c><00:11:36.290><c> of</c>

00:11:36.579 --> 00:11:36.589 align:start position:0%
miners to commit to the medical route of
 

00:11:36.589 --> 00:11:39.879 align:start position:0%
miners to commit to the medical route of
the<00:11:37.279><c> of</c><00:11:37.670><c> this</c><00:11:38.240><c> blown</c><00:11:38.540><c> up</c><00:11:38.779><c> or</c><00:11:39.050><c> a</c><00:11:39.529><c> coded</c>

00:11:39.879 --> 00:11:39.889 align:start position:0%
the of this blown up or a coded
 

00:11:39.889 --> 00:11:42.069 align:start position:0%
the of this blown up or a coded
version<00:11:40.100><c> of</c><00:11:40.550><c> the</c><00:11:40.790><c> blood</c><00:11:40.970><c> layer</c><00:11:41.149><c> that</c><00:11:41.839><c> is</c>

00:11:42.069 --> 00:11:42.079 align:start position:0%
version of the blood layer that is
 

00:11:42.079 --> 00:11:45.249 align:start position:0%
version of the blood layer that is
extended<00:11:42.649><c> to</c><00:11:42.949><c> X</c><00:11:43.300><c> pieces</c><00:11:44.300><c> instead</c><00:11:44.569><c> of</c><00:11:44.689><c> X</c><00:11:44.899><c> pieces</c>

00:11:45.249 --> 00:11:45.259 align:start position:0%
extended to X pieces instead of X pieces
 

00:11:45.259 --> 00:11:48.280 align:start position:0%
extended to X pieces instead of X pieces
and<00:11:45.610><c> then</c><00:11:46.839><c> clients</c><00:11:47.839><c> could</c><00:11:48.019><c> use</c><00:11:48.199><c> this</c>

00:11:48.280 --> 00:11:48.290 align:start position:0%
and then clients could use this
 

00:11:48.290 --> 00:11:50.829 align:start position:0%
and then clients could use this
construction<00:11:48.620><c> to</c><00:11:49.250><c> have</c><00:11:49.639><c> a</c><00:11:50.000><c> guarantee</c><00:11:50.689><c> that</c>

00:11:50.829 --> 00:11:50.839 align:start position:0%
construction to have a guarantee that
 

00:11:50.839 --> 00:11:54.129 align:start position:0%
construction to have a guarantee that
the<00:11:51.290><c> data</c><00:11:51.470><c> is</c><00:11:51.649><c> available</c><00:11:51.680><c> and</c><00:11:52.220><c> so</c><00:11:53.110><c> what</c><00:11:54.110><c> I</c>

00:11:54.129 --> 00:11:54.139 align:start position:0%
the data is available and so what I
 

00:11:54.139 --> 00:11:56.170 align:start position:0%
the data is available and so what I
could<00:11:54.230><c> do</c><00:11:54.470><c> is</c><00:11:54.769><c> they</c><00:11:54.920><c> could</c><00:11:54.949><c> randomly</c><00:11:55.399><c> sample</c>

00:11:56.170 --> 00:11:56.180 align:start position:0%
could do is they could randomly sample
 

00:11:56.180 --> 00:11:59.410 align:start position:0%
could do is they could randomly sample
different<00:11:57.170><c> pieces</c><00:11:57.980><c> of</c><00:11:58.189><c> that</c><00:11:58.430><c> block</c><00:11:58.819><c> of</c><00:11:59.000><c> the</c>

00:11:59.410 --> 00:11:59.420 align:start position:0%
different pieces of that block of the
 

00:11:59.420 --> 00:12:03.189 align:start position:0%
different pieces of that block of the
original<00:11:59.959><c> block</c><00:12:00.319><c> and</c><00:12:00.579><c> if</c><00:12:01.579><c> we</c><00:12:01.850><c> can</c><00:12:01.970><c> assume</c><00:12:02.389><c> if</c>

00:12:03.189 --> 00:12:03.199 align:start position:0%
original block and if we can assume if
 

00:12:03.199 --> 00:12:06.460 align:start position:0%
original block and if we can assume if
we<00:12:03.439><c> assume</c><00:12:03.829><c> that</c><00:12:03.860><c> the</c><00:12:04.819><c> miner</c><00:12:05.089><c> is</c><00:12:05.660><c> trying</c><00:12:06.230><c> to</c><00:12:06.379><c> do</c>

00:12:06.460 --> 00:12:06.470 align:start position:0%
we assume that the miner is trying to do
 

00:12:06.470 --> 00:12:09.400 align:start position:0%
we assume that the miner is trying to do
this<00:12:06.529><c> attack</c><00:12:06.860><c> and</c><00:12:07.129><c> has</c><00:12:07.490><c> hidden</c><00:12:08.050><c> 50%</c><00:12:09.050><c> of</c><00:12:09.199><c> their</c>

00:12:09.400 --> 00:12:09.410 align:start position:0%
this attack and has hidden 50% of their
 

00:12:09.410 --> 00:12:12.460 align:start position:0%
this attack and has hidden 50% of their
then<00:12:10.310><c> there</c><00:12:10.490><c> is</c><00:12:10.579><c> a</c><00:12:10.610><c> 50%</c><00:12:11.209><c> chance</c><00:12:11.269><c> in</c><00:12:11.870><c> the</c><00:12:12.290><c> first</c>

00:12:12.460 --> 00:12:12.470 align:start position:0%
then there is a 50% chance in the first
 

00:12:12.470 --> 00:12:17.620 align:start position:0%
then there is a 50% chance in the first
sample<00:12:13.009><c> that</c><00:12:14.000><c> you</c><00:12:14.300><c> will</c><00:12:14.449><c> end</c><00:12:14.689><c> up</c><00:12:14.930><c> in</c><00:12:15.199><c> a</c><00:12:16.509><c> part</c><00:12:17.509><c> of</c>

00:12:17.620 --> 00:12:17.630 align:start position:0%
sample that you will end up in a part of
 

00:12:17.630 --> 00:12:20.800 align:start position:0%
sample that you will end up in a part of
the<00:12:17.839><c> block</c><00:12:18.290><c> that</c><00:12:18.680><c> is</c><00:12:18.740><c> unavailable</c><00:12:19.370><c> and</c><00:12:19.759><c> so</c><00:12:20.540><c> if</c>

00:12:20.800 --> 00:12:20.810 align:start position:0%
the block that is unavailable and so if
 

00:12:20.810 --> 00:12:22.420 align:start position:0%
the block that is unavailable and so if
you<00:12:20.990><c> sample</c><00:12:21.230><c> a</c><00:12:21.439><c> part</c><00:12:21.740><c> of</c><00:12:21.800><c> the</c><00:12:21.889><c> block</c><00:12:22.069><c> that</c><00:12:22.370><c> is</c>

00:12:22.420 --> 00:12:22.430 align:start position:0%
you sample a part of the block that is
 

00:12:22.430 --> 00:12:25.179 align:start position:0%
you sample a part of the block that is
unavailable<00:12:22.970><c> ie</c><00:12:23.509><c> you</c><00:12:24.139><c> request</c><00:12:24.560><c> from</c><00:12:24.769><c> network</c>

00:12:25.179 --> 00:12:25.189 align:start position:0%
unavailable ie you request from network
 

00:12:25.189 --> 00:12:27.129 align:start position:0%
unavailable ie you request from network
to<00:12:25.399><c> give</c><00:12:25.610><c> you</c><00:12:25.819><c> the</c><00:12:26.420><c> part</c><00:12:26.630><c> of</c><00:12:26.720><c> the</c><00:12:26.839><c> block</c><00:12:27.019><c> that</c>

00:12:27.129 --> 00:12:27.139 align:start position:0%
to give you the part of the block that
 

00:12:27.139 --> 00:12:29.050 align:start position:0%
to give you the part of the block that
is<00:12:27.199><c> available</c><00:12:27.829><c> and</c><00:12:28.399><c> you</c><00:12:28.430><c> don't</c><00:12:28.759><c> receive</c><00:12:29.029><c> a</c>

00:12:29.050 --> 00:12:29.060 align:start position:0%
is available and you don't receive a
 

00:12:29.060 --> 00:12:31.360 align:start position:0%
is available and you don't receive a
response<00:12:29.529><c> then</c><00:12:30.529><c> you</c><00:12:30.649><c> would</c><00:12:30.800><c> then</c><00:12:31.040><c> you</c><00:12:31.189><c> don't</c>

00:12:31.360 --> 00:12:31.370 align:start position:0%
response then you would then you don't
 

00:12:31.370 --> 00:12:34.059 align:start position:0%
response then you would then you don't
accept<00:12:31.670><c> that</c><00:12:31.850><c> block</c><00:12:32.089><c> because</c><00:12:32.959><c> because</c><00:12:33.920><c> you</c>

00:12:34.059 --> 00:12:34.069 align:start position:0%
accept that block because because you
 

00:12:34.069 --> 00:12:37.329 align:start position:0%
accept that block because because you
think<00:12:34.399><c> you</c><00:12:34.550><c> might</c><00:12:34.689><c> because</c><00:12:35.689><c> because</c><00:12:36.339><c> you</c>

00:12:37.329 --> 00:12:37.339 align:start position:0%
think you might because because you
 

00:12:37.339 --> 00:12:38.710 align:start position:0%
think you might because because you
haven't<00:12:37.610><c> received</c><00:12:37.910><c> the</c><00:12:38.149><c> response</c><00:12:38.329><c> to</c><00:12:38.689><c> your</c>

00:12:38.710 --> 00:12:38.720 align:start position:0%
haven't received the response to your
 

00:12:38.720 --> 00:12:42.009 align:start position:0%
haven't received the response to your
sample<00:12:39.139><c> and</c><00:12:39.610><c> so</c><00:12:40.610><c> if</c><00:12:40.880><c> you</c><00:12:41.029><c> keep</c><00:12:41.540><c> doing</c><00:12:41.750><c> more</c>

00:12:42.009 --> 00:12:42.019 align:start position:0%
sample and so if you keep doing more
 

00:12:42.019 --> 00:12:43.689 align:start position:0%
sample and so if you keep doing more
samples<00:12:42.470><c> you</c><00:12:42.920><c> can</c><00:12:43.069><c> get</c><00:12:43.220><c> a</c><00:12:43.250><c> very</c><00:12:43.459><c> high</c>

00:12:43.689 --> 00:12:43.699 align:start position:0%
samples you can get a very high
 

00:12:43.699 --> 00:12:46.960 align:start position:0%
samples you can get a very high
probability<00:12:43.910><c> guarantee</c><00:12:44.689><c> and</c><00:12:45.069><c> that</c><00:12:46.069><c> the</c><00:12:46.759><c> block</c>

00:12:46.960 --> 00:12:46.970 align:start position:0%
probability guarantee and that the block
 

00:12:46.970 --> 00:12:50.139 align:start position:0%
probability guarantee and that the block
is<00:12:47.149><c> actually</c><00:12:47.389><c> available</c><00:12:47.750><c> because</c><00:12:48.649><c> so</c><00:12:49.579><c> there's</c>

00:12:50.139 --> 00:12:50.149 align:start position:0%
is actually available because so there's
 

00:12:50.149 --> 00:12:52.179 align:start position:0%
is actually available because so there's
an<00:12:50.360><c> there's</c><00:12:50.389><c> there</c><00:12:50.870><c> would</c><00:12:50.959><c> be</c><00:12:50.990><c> a</c><00:12:51.110><c> 1</c><00:12:51.470><c> minus</c><00:12:51.860><c> 2</c><00:12:52.069><c> to</c>

00:12:52.179 --> 00:12:52.189 align:start position:0%
an there's there would be a 1 minus 2 to
 

00:12:52.189 --> 00:12:55.120 align:start position:0%
an there's there would be a 1 minus 2 to
the<00:12:52.250><c> power</c><00:12:52.399><c> of</c><00:12:52.699><c> minus</c><00:12:53.209><c> s</c><00:12:53.389><c> chance</c><00:12:53.689><c> of</c><00:12:54.199><c> landing</c>

00:12:55.120 --> 00:12:55.130 align:start position:0%
the power of minus s chance of landing
 

00:12:55.130 --> 00:12:59.110 align:start position:0%
the power of minus s chance of landing
on<00:12:55.759><c> an</c><00:12:56.360><c> unavailable</c><00:12:56.959><c> block</c><00:12:57.259><c> if</c><00:12:57.670><c> the</c><00:12:58.670><c> block</c><00:12:58.880><c> is</c>

00:12:59.110 --> 00:12:59.120 align:start position:0%
on an unavailable block if the block is
 

00:12:59.120 --> 00:13:02.650 align:start position:0%
on an unavailable block if the block is
largely<00:12:59.420><c> or</c><00:13:00.110><c> 50%</c><00:13:00.410><c> unavailable</c><00:13:01.300><c> so</c><00:13:02.300><c> and</c><00:13:02.509><c> if</c><00:13:02.569><c> you</c>

00:13:02.650 --> 00:13:02.660 align:start position:0%
largely or 50% unavailable so and if you
 

00:13:02.660 --> 00:13:03.639 align:start position:0%
largely or 50% unavailable so and if you
don't<00:13:02.809><c> and</c><00:13:03.019><c> again</c><00:13:03.230><c> if</c><00:13:03.350><c> you</c><00:13:03.410><c> learned</c>

00:13:03.639 --> 00:13:03.649 align:start position:0%
don't and again if you learned
 

00:13:03.649 --> 00:13:05.650 align:start position:0%
don't and again if you learned
unavailable<00:13:04.370><c> block</c><00:13:04.550><c> you</c><00:13:05.269><c> don't</c><00:13:05.420><c> receive</c><00:13:05.629><c> a</c>

00:13:05.650 --> 00:13:05.660 align:start position:0%
unavailable block you don't receive a
 

00:13:05.660 --> 00:13:07.569 align:start position:0%
unavailable block you don't receive a
response<00:13:05.899><c> and</c><00:13:06.379><c> then</c><00:13:06.980><c> you</c><00:13:07.100><c> don't</c><00:13:07.250><c> accept</c><00:13:07.430><c> the</c>

00:13:07.569 --> 00:13:07.579 align:start position:0%
response and then you don't accept the
 

00:13:07.579 --> 00:13:13.569 align:start position:0%
response and then you don't accept the
block<00:13:08.470><c> problem</c><00:13:09.470><c> with</c><00:13:09.559><c> this</c><00:13:11.410><c> tied</c><00:13:12.410><c> to</c><00:13:12.559><c> this</c><00:13:12.649><c> is</c>

00:13:13.569 --> 00:13:13.579 align:start position:0%
block problem with this tied to this is
 

00:13:13.579 --> 00:13:15.759 align:start position:0%
block problem with this tied to this is
that<00:13:14.389><c> it's</c><00:13:14.870><c> not</c><00:13:14.990><c> a</c><00:13:15.019><c> problem</c><00:13:15.230><c> with</c><00:13:15.410><c> this</c><00:13:15.500><c> yet</c>

00:13:15.759 --> 00:13:15.769 align:start position:0%
that it's not a problem with this yet
 

00:13:15.769 --> 00:13:17.439 align:start position:0%
that it's not a problem with this yet
also<00:13:16.130><c> the</c><00:13:16.790><c> problem</c><00:13:17.000><c> of</c><00:13:17.029><c> this</c><00:13:17.149><c> is</c><00:13:17.240><c> in</c><00:13:17.329><c> this</c>

00:13:17.439 --> 00:13:17.449 align:start position:0%
also the problem of this is in this
 

00:13:17.449 --> 00:13:21.480 align:start position:0%
also the problem of this is in this
slide<00:13:17.689><c> but</c><00:13:17.899><c> just</c><00:13:18.800><c> as</c><00:13:19.040><c> I</c><00:13:19.189><c> noted</c><00:13:19.459><c> this</c><00:13:19.550><c> is</c>

00:13:21.480 --> 00:13:21.490 align:start position:0%
slide but just as I noted this is
 

00:13:21.490 --> 00:13:23.980 align:start position:0%
slide but just as I noted this is
for<00:13:22.490><c> this</c><00:13:22.580><c> to</c><00:13:22.760><c> work</c><00:13:22.910><c> you</c><00:13:22.970><c> need</c><00:13:23.420><c> a</c><00:13:23.480><c> sufficient</c>

00:13:23.980 --> 00:13:23.990 align:start position:0%
for this to work you need a sufficient
 

00:13:23.990 --> 00:13:27.880 align:start position:0%
for this to work you need a sufficient
number<00:13:24.350><c> of</c><00:13:24.380><c> light</c><00:13:24.770><c> clients</c><00:13:25.430><c> to</c><00:13:26.440><c> make</c><00:13:27.440><c> enough</c>

00:13:27.880 --> 00:13:27.890 align:start position:0%
number of light clients to make enough
 

00:13:27.890 --> 00:13:30.340 align:start position:0%
number of light clients to make enough
samples<00:13:28.430><c> to</c><00:13:28.700><c> be</c><00:13:28.790><c> able</c><00:13:28.910><c> to</c><00:13:29.060><c> reconstruct</c><00:13:29.540><c> the</c>

00:13:30.340 --> 00:13:30.350 align:start position:0%
samples to be able to reconstruct the
 

00:13:30.350 --> 00:13:32.560 align:start position:0%
samples to be able to reconstruct the
entire<00:13:30.500><c> data</c><00:13:30.920><c> so</c><00:13:31.670><c> for</c><00:13:31.820><c> example</c><00:13:32.180><c> like</c><00:13:32.300><c> if</c><00:13:32.480><c> you</c>

00:13:32.560 --> 00:13:32.570 align:start position:0%
entire data so for example like if you
 

00:13:32.570 --> 00:13:34.660 align:start position:0%
entire data so for example like if you
only<00:13:32.720><c> have</c><00:13:32.870><c> like</c><00:13:32.900><c> one</c><00:13:33.080><c> client</c><00:13:33.530><c> then</c><00:13:34.400><c> there's</c>

00:13:34.660 --> 00:13:34.670 align:start position:0%
only have like one client then there's
 

00:13:34.670 --> 00:13:36.190 align:start position:0%
only have like one client then there's
not<00:13:34.790><c> enough</c><00:13:34.970><c> clients</c><00:13:35.450><c> to</c><00:13:35.690><c> make</c><00:13:35.930><c> enough</c>

00:13:36.190 --> 00:13:36.200 align:start position:0%
not enough clients to make enough
 

00:13:36.200 --> 00:13:39.040 align:start position:0%
not enough clients to make enough
samples<00:13:36.620><c> for</c><00:13:36.920><c> 50%</c><00:13:37.520><c> to</c><00:13:37.820><c> sample</c><00:13:38.390><c> 50%</c><00:13:38.870><c> of</c><00:13:38.960><c> the</c>

00:13:39.040 --> 00:13:39.050 align:start position:0%
samples for 50% to sample 50% of the
 

00:13:39.050 --> 00:13:41.700 align:start position:0%
samples for 50% to sample 50% of the
blog<00:13:39.230><c> so</c><00:13:40.040><c> then</c><00:13:40.280><c> the</c><00:13:40.430><c> scheme</c><00:13:40.640><c> we</c><00:13:41.000><c> didn't</c><00:13:41.180><c> work</c>

00:13:41.700 --> 00:13:41.710 align:start position:0%
blog so then the scheme we didn't work
 

00:13:41.710 --> 00:13:45.300 align:start position:0%
blog so then the scheme we didn't work
now<00:13:42.710><c> there</c><00:13:42.860><c> are</c><00:13:43.040><c> ways</c><00:13:43.310><c> to</c><00:13:43.730><c> kind</c><00:13:43.970><c> of</c><00:13:44.090><c> and</c><00:13:45.050><c> also</c>

00:13:45.300 --> 00:13:45.310 align:start position:0%
now there are ways to kind of and also
 

00:13:45.310 --> 00:13:48.690 align:start position:0%
now there are ways to kind of and also
there<00:13:46.310><c> are</c><00:13:46.340><c> ways</c><00:13:46.640><c> to</c><00:13:46.670><c> get</c><00:13:46.940><c> around</c><00:13:47.300><c> this</c><00:13:47.630><c> or</c>

00:13:48.690 --> 00:13:48.700 align:start position:0%
there are ways to get around this or
 

00:13:48.700 --> 00:13:52.660 align:start position:0%
there are ways to get around this or
well<00:13:49.700><c> also</c><00:13:50.570><c> make</c><00:13:50.720><c> it</c><00:13:50.800><c> more</c><00:13:51.800><c> possible</c><00:13:52.040><c> so</c><00:13:52.460><c> that</c>

00:13:52.660 --> 00:13:52.670 align:start position:0%
well also make it more possible so that
 

00:13:52.670 --> 00:13:54.790 align:start position:0%
well also make it more possible so that
you<00:13:53.330><c> can't</c><00:13:53.600><c> fool</c><00:13:53.900><c> the</c><00:13:54.110><c> first</c><00:13:54.380><c> number</c><00:13:54.740><c> of</c>

00:13:54.790 --> 00:13:54.800 align:start position:0%
you can't fool the first number of
 

00:13:54.800 --> 00:13:57.220 align:start position:0%
you can't fool the first number of
clients<00:13:55.250><c> but</c><00:13:55.970><c> I'm</c><00:13:56.540><c> not</c><00:13:56.660><c> gonna</c><00:13:56.780><c> mention</c><00:13:56.930><c> it</c><00:13:57.140><c> in</c>

00:13:57.220 --> 00:13:57.230 align:start position:0%
clients but I'm not gonna mention it in
 

00:13:57.230 --> 00:13:59.350 align:start position:0%
clients but I'm not gonna mention it in
this<00:13:57.320><c> talk</c><00:13:57.500><c> it</c><00:13:57.980><c> will</c><00:13:58.070><c> be</c><00:13:58.130><c> in</c><00:13:58.310><c> the</c><00:13:58.460><c> it's</c><00:13:59.180><c> in</c><00:13:59.240><c> the</c>

00:13:59.350 --> 00:13:59.360 align:start position:0%
this talk it will be in the it's in the
 

00:13:59.360 --> 00:14:01.720 align:start position:0%
this talk it will be in the it's in the
full<00:13:59.510><c> version</c><00:13:59.540><c> of</c><00:13:59.810><c> the</c><00:13:59.900><c> paper</c><00:14:00.080><c> and</c><00:14:00.730><c> there's</c>

00:14:01.720 --> 00:14:01.730 align:start position:0%
full version of the paper and there's
 

00:14:01.730 --> 00:14:04.330 align:start position:0%
full version of the paper and there's
also<00:14:01.880><c> more</c><00:14:02.660><c> analysis</c><00:14:02.840><c> and</c><00:14:03.440><c> graphs</c><00:14:04.160><c> in</c><00:14:04.280><c> the</c>

00:14:04.330 --> 00:14:04.340 align:start position:0%
also more analysis and graphs in the
 

00:14:04.340 --> 00:14:05.830 align:start position:0%
also more analysis and graphs in the
papers<00:14:04.550><c> that</c><00:14:04.670><c> show</c><00:14:04.850><c> how</c><00:14:05.060><c> many</c><00:14:05.270><c> light</c><00:14:05.420><c> clients</c>

00:14:05.830 --> 00:14:05.840 align:start position:0%
papers that show how many light clients
 

00:14:05.840 --> 00:14:08.500 align:start position:0%
papers that show how many light clients
you<00:14:05.900><c> need</c><00:14:06.080><c> exactly</c><00:14:06.940><c> so</c><00:14:07.940><c> the</c><00:14:08.030><c> problem</c><00:14:08.330><c> with</c><00:14:08.450><c> the</c>

00:14:08.500 --> 00:14:08.510 align:start position:0%
you need exactly so the problem with the
 

00:14:08.510 --> 00:14:10.090 align:start position:0%
you need exactly so the problem with the
schema<00:14:08.750><c> I've</c><00:14:08.810><c> described</c><00:14:09.140><c> the</c><00:14:09.740><c> problem</c><00:14:10.010><c> with</c>

00:14:10.090 --> 00:14:10.100 align:start position:0%
schema I've described the problem with
 

00:14:10.100 --> 00:14:11.710 align:start position:0%
schema I've described the problem with
the<00:14:10.190><c> scheme</c><00:14:10.400><c> that</c><00:14:10.580><c> I've</c><00:14:10.640><c> described</c><00:14:11.060><c> so</c><00:14:11.240><c> far</c><00:14:11.270><c> is</c>

00:14:11.710 --> 00:14:11.720 align:start position:0%
the scheme that I've described so far is
 

00:14:11.720 --> 00:14:15.820 align:start position:0%
the scheme that I've described so far is
that<00:14:13.390><c> what</c><00:14:14.390><c> if</c><00:14:14.540><c> the</c><00:14:14.660><c> miner</c><00:14:14.870><c> actually</c>

00:14:15.820 --> 00:14:15.830 align:start position:0%
that what if the miner actually
 

00:14:15.830 --> 00:14:19.270 align:start position:0%
that what if the miner actually
incorrectly<00:14:16.610><c> applies</c><00:14:17.240><c> the</c><00:14:17.810><c> erasure</c><00:14:18.110><c> code</c><00:14:18.440><c> so</c>

00:14:19.270 --> 00:14:19.280 align:start position:0%
incorrectly applies the erasure code so
 

00:14:19.280 --> 00:14:21.640 align:start position:0%
incorrectly applies the erasure code so
what<00:14:19.460><c> if</c><00:14:19.610><c> they</c><00:14:19.760><c> just</c><00:14:20.420><c> insert</c><00:14:20.870><c> gibberish</c><00:14:21.350><c> in</c>

00:14:21.640 --> 00:14:21.650 align:start position:0%
what if they just insert gibberish in
 

00:14:21.650 --> 00:14:25.420 align:start position:0%
what if they just insert gibberish in
the<00:14:22.520><c> extended</c><00:14:23.150><c> part</c><00:14:23.390><c> of</c><00:14:23.510><c> the</c><00:14:23.570><c> data</c><00:14:23.810><c> right</c><00:14:24.500><c> so</c>

00:14:25.420 --> 00:14:25.430 align:start position:0%
the extended part of the data right so
 

00:14:25.430 --> 00:14:27.340 align:start position:0%
the extended part of the data right so
then<00:14:25.610><c> that's</c><00:14:26.510><c> not</c><00:14:26.750><c> that</c><00:14:26.930><c> wouldn't</c><00:14:27.170><c> be</c><00:14:27.230><c> useful</c>

00:14:27.340 --> 00:14:27.350 align:start position:0%
then that's not that wouldn't be useful
 

00:14:27.350 --> 00:14:29.230 align:start position:0%
then that's not that wouldn't be useful
to<00:14:27.620><c> anyone</c><00:14:27.890><c> because</c><00:14:28.040><c> then</c><00:14:28.460><c> if</c><00:14:28.700><c> you</c><00:14:28.820><c> actually</c>

00:14:29.230 --> 00:14:29.240 align:start position:0%
to anyone because then if you actually
 

00:14:29.240 --> 00:14:33.040 align:start position:0%
to anyone because then if you actually
lose<00:14:29.510><c> 50%</c><00:14:30.440><c> of</c><00:14:30.800><c> the</c><00:14:30.950><c> blog</c><00:14:31.210><c> then</c><00:14:32.210><c> that</c><00:14:32.570><c> gibberish</c>

00:14:33.040 --> 00:14:33.050 align:start position:0%
lose 50% of the blog then that gibberish
 

00:14:33.050 --> 00:14:34.630 align:start position:0%
lose 50% of the blog then that gibberish
data<00:14:33.410><c> is</c><00:14:33.710><c> not</c><00:14:33.890><c> going</c><00:14:34.070><c> to</c><00:14:34.130><c> help</c><00:14:34.220><c> you</c><00:14:34.490><c> to</c>

00:14:34.630 --> 00:14:34.640 align:start position:0%
data is not going to help you to
 

00:14:34.640 --> 00:14:38.260 align:start position:0%
data is not going to help you to
reconstruct<00:14:35.210><c> the</c><00:14:35.300><c> entire</c><00:14:35.570><c> block</c><00:14:36.310><c> so</c><00:14:37.310><c> if</c><00:14:38.120><c> you</c>

00:14:38.260 --> 00:14:38.270 align:start position:0%
reconstruct the entire block so if you
 

00:14:38.270 --> 00:14:40.240 align:start position:0%
reconstruct the entire block so if you
wanted<00:14:38.480><c> to</c><00:14:38.600><c> prove</c><00:14:38.810><c> to</c><00:14:38.870><c> prove</c><00:14:39.560><c> this</c><00:14:39.830><c> to</c><00:14:40.040><c> lack</c>

00:14:40.240 --> 00:14:40.250 align:start position:0%
wanted to prove to prove this to lack
 

00:14:40.250 --> 00:14:42.640 align:start position:0%
wanted to prove to prove this to lack
clients<00:14:40.700><c> then</c><00:14:41.690><c> you</c><00:14:41.720><c> would</c><00:14:41.930><c> basically</c><00:14:42.020><c> have</c><00:14:42.350><c> to</c>

00:14:42.640 --> 00:14:42.650 align:start position:0%
clients then you would basically have to
 

00:14:42.650 --> 00:14:44.740 align:start position:0%
clients then you would basically have to
give<00:14:42.800><c> them</c><00:14:43.070><c> the</c><00:14:43.250><c> entire</c><00:14:43.580><c> original</c><00:14:43.910><c> data</c><00:14:44.270><c> and</c>

00:14:44.740 --> 00:14:44.750 align:start position:0%
give them the entire original data and
 

00:14:44.750 --> 00:14:47.350 align:start position:0%
give them the entire original data and
then<00:14:45.290><c> they</c><00:14:45.410><c> would</c><00:14:45.530><c> have</c><00:14:45.560><c> to</c><00:14:46.060><c> recompute</c><00:14:47.060><c> area</c>

00:14:47.350 --> 00:14:47.360 align:start position:0%
then they would have to recompute area
 

00:14:47.360 --> 00:14:49.450 align:start position:0%
then they would have to recompute area
code<00:14:47.600><c> themselves</c><00:14:48.170><c> to</c><00:14:48.620><c> check</c><00:14:48.860><c> that</c><00:14:49.040><c> is</c><00:14:49.130><c> correct</c>

00:14:49.450 --> 00:14:49.460 align:start position:0%
code themselves to check that is correct
 

00:14:49.460 --> 00:14:51.400 align:start position:0%
code themselves to check that is correct
and<00:14:49.790><c> this</c><00:14:50.360><c> is</c><00:14:50.450><c> going</c><00:14:50.690><c> back</c><00:14:50.840><c> to</c><00:14:51.050><c> square</c><00:14:51.200><c> one</c>

00:14:51.400 --> 00:14:51.410 align:start position:0%
and this is going back to square one
 

00:14:51.410 --> 00:14:55.360 align:start position:0%
and this is going back to square one
because<00:14:51.830><c> you</c><00:14:52.010><c> need</c><00:14:52.250><c> the</c><00:14:52.850><c> entire</c><00:14:53.120><c> block</c><00:14:53.480><c> to</c><00:14:54.470><c> do</c>

00:14:55.360 --> 00:14:55.370 align:start position:0%
because you need the entire block to do
 

00:14:55.370 --> 00:14:57.910 align:start position:0%
because you need the entire block to do
this<00:14:55.520><c> check</c><00:14:55.790><c> so</c><00:14:56.240><c> the</c><00:14:57.050><c> full</c><00:14:57.290><c> proof</c><00:14:57.560><c> it</c><00:14:57.770><c> could</c>

00:14:57.910 --> 00:14:57.920 align:start position:0%
this check so the full proof it could
 

00:14:57.920 --> 00:14:59.830 align:start position:0%
this check so the full proof it could
will<00:14:58.430><c> be</c><00:14:58.520><c> equivalent</c><00:14:59.000><c> to</c><00:14:59.060><c> the</c><00:14:59.180><c> size</c><00:14:59.420><c> of</c><00:14:59.660><c> the</c>

00:14:59.830 --> 00:14:59.840 align:start position:0%
will be equivalent to the size of the
 

00:14:59.840 --> 00:15:01.930 align:start position:0%
will be equivalent to the size of the
block<00:15:00.080><c> itself</c><00:15:00.380><c> and</c><00:15:00.800><c> that's</c><00:15:01.700><c> what</c><00:15:01.820><c> we're</c>

00:15:01.930 --> 00:15:01.940 align:start position:0%
block itself and that's what we're
 

00:15:01.940 --> 00:15:03.880 align:start position:0%
block itself and that's what we're
trying<00:15:02.060><c> to</c><00:15:02.210><c> avoid</c><00:15:02.450><c> in</c><00:15:02.600><c> the</c><00:15:02.630><c> first</c><00:15:02.900><c> place</c><00:15:03.080><c> so</c>

00:15:03.880 --> 00:15:03.890 align:start position:0%
trying to avoid in the first place so
 

00:15:03.890 --> 00:15:05.380 align:start position:0%
trying to avoid in the first place so
the<00:15:03.980><c> way</c><00:15:04.070><c> to</c><00:15:04.100><c> fix</c><00:15:04.340><c> this</c><00:15:04.610><c> is</c><00:15:04.880><c> that</c><00:15:05.090><c> you</c><00:15:05.210><c> could</c>

00:15:05.380 --> 00:15:05.390 align:start position:0%
the way to fix this is that you could
 

00:15:05.390 --> 00:15:09.010 align:start position:0%
the way to fix this is that you could
use<00:15:05.420><c> a</c><00:15:06.340><c> multi-dimensional</c><00:15:07.340><c> array</c><00:15:08.020><c> geocoding</c>

00:15:09.010 --> 00:15:09.020 align:start position:0%
use a multi-dimensional array geocoding
 

00:15:09.020 --> 00:15:12.310 align:start position:0%
use a multi-dimensional array geocoding
and<00:15:09.550><c> the</c><00:15:10.550><c> idea</c><00:15:10.790><c> of</c><00:15:10.910><c> multi-dimensional</c><00:15:11.780><c> image</c>

00:15:12.310 --> 00:15:12.320 align:start position:0%
and the idea of multi-dimensional image
 

00:15:12.320 --> 00:15:16.360 align:start position:0%
and the idea of multi-dimensional image
coding<00:15:12.620><c> is</c><00:15:12.950><c> that</c><00:15:13.850><c> you</c><00:15:14.030><c> have</c><00:15:14.950><c> you</c><00:15:15.950><c> basically</c>

00:15:16.360 --> 00:15:16.370 align:start position:0%
coding is that you have you basically
 

00:15:16.370 --> 00:15:19.270 align:start position:0%
coding is that you have you basically
arranged<00:15:16.820><c> your</c><00:15:17.270><c> block</c><00:15:17.810><c> data</c><00:15:17.990><c> into</c><00:15:18.890><c> a</c><00:15:18.920><c> square</c>

00:15:19.270 --> 00:15:19.280 align:start position:0%
arranged your block data into a square
 

00:15:19.280 --> 00:15:21.310 align:start position:0%
arranged your block data into a square
so<00:15:19.940><c> you</c><00:15:20.000><c> cut</c><00:15:20.270><c> it</c><00:15:20.390><c> up</c><00:15:20.480><c> into</c><00:15:20.750><c> a</c><00:15:20.870><c> number</c><00:15:21.080><c> of</c><00:15:21.140><c> pieces</c>

00:15:21.310 --> 00:15:21.320 align:start position:0%
so you cut it up into a number of pieces
 

00:15:21.320 --> 00:15:23.770 align:start position:0%
so you cut it up into a number of pieces
and<00:15:21.740><c> the</c><00:15:22.220><c> you</c><00:15:22.550><c> arrange</c><00:15:22.820><c> those</c><00:15:23.060><c> pieces</c><00:15:23.360><c> in</c>

00:15:23.770 --> 00:15:23.780 align:start position:0%
and the you arrange those pieces in
 

00:15:23.780 --> 00:15:26.890 align:start position:0%
and the you arrange those pieces in
interior<00:15:24.440><c> Square</c><00:15:24.830><c> and</c><00:15:25.390><c> then</c><00:15:26.390><c> you</c><00:15:26.540><c> apply</c><00:15:26.840><c> the</c>

00:15:26.890 --> 00:15:26.900 align:start position:0%
interior Square and then you apply the
 

00:15:26.900 --> 00:15:30.220 align:start position:0%
interior Square and then you apply the
erasure<00:15:27.260><c> coding</c><00:15:27.770><c> one</c><00:15:28.550><c> by</c><00:15:28.760><c> one</c><00:15:29.000><c> on</c><00:15:29.240><c> each</c><00:15:29.900><c> row</c>

00:15:30.220 --> 00:15:30.230 align:start position:0%
erasure coding one by one on each row
 

00:15:30.230 --> 00:15:33.040 align:start position:0%
erasure coding one by one on each row
and<00:15:30.500><c> column</c><00:15:30.560><c> of</c><00:15:31.160><c> this</c><00:15:31.790><c> Square</c><00:15:32.090><c> until</c><00:15:32.810><c> you</c><00:15:32.900><c> can</c>

00:15:33.040 --> 00:15:33.050 align:start position:0%
and column of this Square until you can
 

00:15:33.050 --> 00:15:33.710 align:start position:0%
and column of this Square until you can
extend

00:15:33.710 --> 00:15:33.720 align:start position:0%
extend
 

00:15:33.720 --> 00:15:38.570 align:start position:0%
extend
into<00:15:34.140><c> a</c><00:15:34.170><c> bigger</c><00:15:34.410><c> square</c><00:15:34.740><c> and</c><00:15:35.960><c> so</c><00:15:37.250><c> if</c><00:15:38.250><c> one</c><00:15:38.550><c> of</c>

00:15:38.570 --> 00:15:38.580 align:start position:0%
into a bigger square and so if one of
 

00:15:38.580 --> 00:15:40.340 align:start position:0%
into a bigger square and so if one of
these<00:15:38.820><c> rows</c><00:15:39.030><c> and</c><00:15:39.240><c> columns</c><00:15:39.570><c> were</c><00:15:39.780><c> incorrectly</c>

00:15:40.340 --> 00:15:40.350 align:start position:0%
these rows and columns were incorrectly
 

00:15:40.350 --> 00:15:43.400 align:start position:0%
these rows and columns were incorrectly
extended<00:15:41.040><c> then</c><00:15:42.030><c> the</c><00:15:42.420><c> size</c><00:15:42.660><c> of</c><00:15:42.810><c> the</c><00:15:42.900><c> foot</c><00:15:43.110><c> proof</c>

00:15:43.400 --> 00:15:43.410 align:start position:0%
extended then the size of the foot proof
 

00:15:43.410 --> 00:15:45.260 align:start position:0%
extended then the size of the foot proof
would<00:15:43.680><c> be</c><00:15:43.800><c> limited</c><00:15:44.250><c> to</c><00:15:44.460><c> a</c><00:15:44.490><c> single</c><00:15:44.760><c> row</c><00:15:45.090><c> or</c>

00:15:45.260 --> 00:15:45.270 align:start position:0%
would be limited to a single row or
 

00:15:45.270 --> 00:15:48.170 align:start position:0%
would be limited to a single row or
column<00:15:45.350><c> because</c><00:15:46.350><c> only</c><00:15:46.620><c> the</c><00:15:47.580><c> lifelines</c><00:15:47.970><c> would</c>

00:15:48.170 --> 00:15:48.180 align:start position:0%
column because only the lifelines would
 

00:15:48.180 --> 00:15:52.460 align:start position:0%
column because only the lifelines would
only<00:15:48.390><c> have</c><00:15:48.900><c> to</c><00:15:49.490><c> make</c><00:15:50.490><c> these</c><00:15:51.390><c> proofs</c><00:15:51.750><c> at</c><00:15:52.020><c> one</c><00:15:52.260><c> or</c>

00:15:52.460 --> 00:15:52.470 align:start position:0%
only have to make these proofs at one or
 

00:15:52.470 --> 00:15:54.710 align:start position:0%
only have to make these proofs at one or
one<00:15:52.890><c> row</c><00:15:53.070><c> or</c><00:15:53.100><c> column</c><00:15:53.250><c> is</c><00:15:53.730><c> incorrectly</c>

00:15:54.710 --> 00:15:54.720 align:start position:0%
one row or column is incorrectly
 

00:15:54.720 --> 00:15:57.440 align:start position:0%
one row or column is incorrectly
computed<00:15:55.350><c> to</c><00:15:55.980><c> be</c><00:15:56.100><c> able</c><00:15:56.190><c> to</c><00:15:56.460><c> know</c><00:15:56.580><c> that</c><00:15:56.610><c> the</c>

00:15:57.440 --> 00:15:57.450 align:start position:0%
computed to be able to know that the
 

00:15:57.450 --> 00:16:00.530 align:start position:0%
computed to be able to know that the
block<00:15:58.170><c> is</c><00:15:58.320><c> invalid</c><00:15:58.710><c> and</c><00:15:59.000><c> this</c><00:16:00.000><c> is</c><00:16:00.090><c> much</c><00:16:00.300><c> better</c>

00:16:00.530 --> 00:16:00.540 align:start position:0%
block is invalid and this is much better
 

00:16:00.540 --> 00:16:05.120 align:start position:0%
block is invalid and this is much better
because<00:16:00.750><c> this</c><00:16:01.050><c> has</c><00:16:01.230><c> efficiency</c><00:16:01.800><c> of</c><00:16:02.190><c> a</c><00:16:04.130><c> square</c>

00:16:05.120 --> 00:16:05.130 align:start position:0%
because this has efficiency of a square
 

00:16:05.130 --> 00:16:06.680 align:start position:0%
because this has efficiency of a square
root<00:16:05.310><c> of</c><00:16:05.460><c> the</c><00:16:05.580><c> block</c><00:16:05.760><c> size</c><00:16:05.970><c> rather</c><00:16:06.330><c> than</c><00:16:06.570><c> a</c>

00:16:06.680 --> 00:16:06.690 align:start position:0%
root of the block size rather than a
 

00:16:06.690 --> 00:16:11.480 align:start position:0%
root of the block size rather than a
block<00:16:07.290><c> size</c><00:16:08.060><c> and</c><00:16:09.590><c> with</c><00:16:10.590><c> muscle</c><00:16:10.980><c> damage</c><00:16:11.010><c> with</c>

00:16:11.480 --> 00:16:11.490 align:start position:0%
block size and with muscle damage with
 

00:16:11.490 --> 00:16:14.330 align:start position:0%
block size and with muscle damage with
this<00:16:11.640><c> 2d</c><00:16:11.880><c> coding</c><00:16:12.510><c> scheme</c><00:16:12.750><c> so</c><00:16:13.050><c> you</c><00:16:13.110><c> can</c><00:16:13.350><c> so</c><00:16:13.860><c> in</c>

00:16:14.330 --> 00:16:14.340 align:start position:0%
this 2d coding scheme so you can so in
 

00:16:14.340 --> 00:16:15.500 align:start position:0%
this 2d coding scheme so you can so in
the<00:16:14.490><c> example</c><00:16:14.850><c> here</c><00:16:14.880><c> I'm</c><00:16:15.060><c> using</c><00:16:15.240><c> two</c>

00:16:15.500 --> 00:16:15.510 align:start position:0%
the example here I'm using two
 

00:16:15.510 --> 00:16:17.360 align:start position:0%
the example here I'm using two
dimensional<00:16:15.660><c> encoding</c><00:16:16.410><c> but</c><00:16:16.920><c> you</c><00:16:17.040><c> could</c><00:16:17.190><c> go</c>

00:16:17.360 --> 00:16:17.370 align:start position:0%
dimensional encoding but you could go
 

00:16:17.370 --> 00:16:18.710 align:start position:0%
dimensional encoding but you could go
higher<00:16:17.580><c> you</c><00:16:17.760><c> could</c><00:16:17.910><c> use</c><00:16:18.090><c> higher</c><00:16:18.270><c> dimensions</c>

00:16:18.710 --> 00:16:18.720 align:start position:0%
higher you could use higher dimensions
 

00:16:18.720 --> 00:16:20.660 align:start position:0%
higher you could use higher dimensions
if<00:16:18.810><c> you</c><00:16:18.870><c> wanted</c><00:16:19.140><c> to</c><00:16:19.310><c> although</c><00:16:20.310><c> personally</c><00:16:20.490><c> I</c>

00:16:20.660 --> 00:16:20.670 align:start position:0%
if you wanted to although personally I
 

00:16:20.670 --> 00:16:22.070 align:start position:0%
if you wanted to although personally I
don't<00:16:20.730><c> think</c><00:16:20.880><c> it's</c><00:16:21.180><c> worth</c><00:16:21.360><c> it</c><00:16:21.510><c> because</c><00:16:21.750><c> there</c>

00:16:22.070 --> 00:16:22.080 align:start position:0%
don't think it's worth it because there
 

00:16:22.080 --> 00:16:24.910 align:start position:0%
don't think it's worth it because there
are<00:16:22.110><c> other</c><00:16:22.320><c> trade-offs</c><00:16:22.770><c> so</c><00:16:23.060><c> with</c><00:16:24.060><c> this</c><00:16:24.240><c> scheme</c>

00:16:24.910 --> 00:16:24.920 align:start position:0%
are other trade-offs so with this scheme
 

00:16:24.920 --> 00:16:29.120 align:start position:0%
are other trade-offs so with this scheme
you<00:16:25.920><c> a</c><00:16:26.220><c> minor</c><00:16:26.520><c> would</c><00:16:26.760><c> have</c><00:16:26.940><c> to</c><00:16:27.150><c> hide</c><00:16:27.950><c> 25%</c><00:16:28.950><c> of</c>

00:16:29.120 --> 00:16:29.130 align:start position:0%
you a minor would have to hide 25% of
 

00:16:29.130 --> 00:16:34.060 align:start position:0%
you a minor would have to hide 25% of
the<00:16:29.340><c> data</c><00:16:29.570><c> to</c><00:16:30.570><c> hide</c><00:16:31.530><c> the</c><00:16:31.680><c> whole</c><00:16:31.830><c> square</c><00:16:32.960><c> so</c>

00:16:34.060 --> 00:16:34.070 align:start position:0%
the data to hide the whole square so
 

00:16:34.070 --> 00:16:39.200 align:start position:0%
the data to hide the whole square so
here's<00:16:35.070><c> a</c><00:16:35.160><c> graph</c><00:16:35.370><c> showing</c><00:16:37.100><c> given</c><00:16:38.100><c> a</c><00:16:38.400><c> light</c>

00:16:39.200 --> 00:16:39.210 align:start position:0%
here's a graph showing given a light
 

00:16:39.210 --> 00:16:43.070 align:start position:0%
here's a graph showing given a light
client<00:16:39.660><c> that</c><00:16:40.260><c> makes</c><00:16:40.560><c> s</c><00:16:40.950><c> samples</c><00:16:41.780><c> what</c><00:16:42.780><c> is</c><00:16:42.930><c> the</c>

00:16:43.070 --> 00:16:43.080 align:start position:0%
client that makes s samples what is the
 

00:16:43.080 --> 00:16:46.430 align:start position:0%
client that makes s samples what is the
probability<00:16:43.470><c> that</c><00:16:43.920><c> they</c><00:16:44.430><c> will</c><00:16:44.610><c> land</c><00:16:44.880><c> on</c><00:16:45.440><c> an</c>

00:16:46.430 --> 00:16:46.440 align:start position:0%
probability that they will land on an
 

00:16:46.440 --> 00:16:48.530 align:start position:0%
probability that they will land on an
unavailable<00:16:47.070><c> part</c><00:16:47.850><c> of</c><00:16:47.970><c> the</c><00:16:48.090><c> block</c>

00:16:48.530 --> 00:16:48.540 align:start position:0%
unavailable part of the block
 

00:16:48.540 --> 00:16:52.340 align:start position:0%
unavailable part of the block
if<00:16:48.830><c> the</c><00:16:49.830><c> miner</c><00:16:50.040><c> has</c><00:16:50.730><c> hidden</c><00:16:51.110><c> 25%</c><00:16:52.110><c> of</c><00:16:52.260><c> the</c>

00:16:52.340 --> 00:16:52.350 align:start position:0%
if the miner has hidden 25% of the
 

00:16:52.350 --> 00:16:54.080 align:start position:0%
if the miner has hidden 25% of the
square<00:16:52.590><c> the</c><00:16:53.580><c> height</c><00:16:53.700><c> and</c><00:16:53.850><c> the</c><00:16:53.910><c> higher</c><00:16:54.060><c> the</c>

00:16:54.080 --> 00:16:54.090 align:start position:0%
square the height and the higher the
 

00:16:54.090 --> 00:16:55.880 align:start position:0%
square the height and the higher the
probability<00:16:54.410><c> than</c><00:16:55.410><c> the</c><00:16:55.530><c> higher</c><00:16:55.740><c> the</c>

00:16:55.880 --> 00:16:55.890 align:start position:0%
probability than the higher the
 

00:16:55.890 --> 00:16:59.450 align:start position:0%
probability than the higher the
probability<00:16:56.040><c> of</c><00:16:56.690><c> a</c><00:16:57.690><c> light</c><00:16:58.590><c> client</c><00:16:59.010><c> detecting</c>

00:16:59.450 --> 00:16:59.460 align:start position:0%
probability of a light client detecting
 

00:16:59.460 --> 00:17:02.150 align:start position:0%
probability of a light client detecting
that<00:16:59.850><c> block</c><00:17:00.210><c> is</c><00:17:00.450><c> not</c><00:17:00.690><c> available</c><00:17:01.260><c> so</c><00:17:01.470><c> we</c><00:17:01.980><c> won't</c>

00:17:02.150 --> 00:17:02.160 align:start position:0%
that block is not available so we won't
 

00:17:02.160 --> 00:17:04.550 align:start position:0%
that block is not available so we won't
probably<00:17:02.370><c> be</c><00:17:02.700><c> high</c><00:17:02.910><c> and</c><00:17:03.510><c> you</c><00:17:04.020><c> can</c><00:17:04.170><c> see</c><00:17:04.199><c> here</c>

00:17:04.550 --> 00:17:04.560 align:start position:0%
probably be high and you can see here
 

00:17:04.560 --> 00:17:07.160 align:start position:0%
probably be high and you can see here
that<00:17:04.760><c> if</c><00:17:05.760><c> you</c><00:17:05.910><c> do</c><00:17:06.060><c> say</c><00:17:06.270><c> if</c><00:17:06.540><c> he</c><00:17:06.660><c> after</c><00:17:06.990><c> three</c>

00:17:07.160 --> 00:17:07.170 align:start position:0%
that if you do say if he after three
 

00:17:07.170 --> 00:17:09.679 align:start position:0%
that if you do say if he after three
samples<00:17:07.620><c> the</c><00:17:08.220><c> probability</c><00:17:09.150><c> is</c><00:17:09.209><c> about</c><00:17:09.390><c> sixty</c>

00:17:09.679 --> 00:17:09.689 align:start position:0%
samples the probability is about sixty
 

00:17:09.689 --> 00:17:12.650 align:start position:0%
samples the probability is about sixty
percent<00:17:10.189><c> for</c><00:17:11.189><c> 15</c><00:17:11.250><c> samples</c><00:17:11.939><c> the</c><00:17:12.180><c> probability</c>

00:17:12.650 --> 00:17:12.660 align:start position:0%
percent for 15 samples the probability
 

00:17:12.660 --> 00:17:15.770 align:start position:0%
percent for 15 samples the probability
is<00:17:12.810><c> about</c><00:17:13.020><c> 99%</c><00:17:13.579><c> so</c><00:17:14.579><c> so</c><00:17:14.970><c> you</c><00:17:15.030><c> can</c><00:17:15.240><c> get</c><00:17:15.420><c> you</c><00:17:15.630><c> can</c>

00:17:15.770 --> 00:17:15.780 align:start position:0%
is about 99% so so you can get you can
 

00:17:15.780 --> 00:17:17.090 align:start position:0%
is about 99% so so you can get you can
get<00:17:15.930><c> very</c><00:17:16.110><c> high</c><00:17:16.170><c> probabilities</c>

00:17:17.090 --> 00:17:17.100 align:start position:0%
get very high probabilities
 

00:17:17.100 --> 00:17:20.290 align:start position:0%
get very high probabilities
just<00:17:17.610><c> from</c><00:17:17.819><c> a</c><00:17:17.990><c> reasonable</c><00:17:18.990><c> number</c><00:17:19.620><c> of</c><00:17:19.650><c> samples</c>

00:17:20.290 --> 00:17:20.300 align:start position:0%
just from a reasonable number of samples
 

00:17:20.300 --> 00:17:23.960 align:start position:0%
just from a reasonable number of samples
so<00:17:21.300><c> some</c><00:17:21.780><c> people</c><00:17:22.050><c> might</c><00:17:22.199><c> consider</c><00:17:22.500><c> that</c><00:17:22.970><c> 99</c>

00:17:23.960 --> 00:17:23.970 align:start position:0%
so some people might consider that 99
 

00:17:23.970 --> 00:17:25.880 align:start position:0%
so some people might consider that 99
percent<00:17:24.270><c> is</c><00:17:24.329><c> too</c><00:17:24.839><c> low</c><00:17:24.990><c> it's</c><00:17:25.530><c> like</c><00:17:25.650><c> if</c><00:17:25.800><c> you</c>

00:17:25.880 --> 00:17:25.890 align:start position:0%
percent is too low it's like if you
 

00:17:25.890 --> 00:17:29.090 align:start position:0%
percent is too low it's like if you
wanted<00:17:26.160><c> 99.99%</c><00:17:27.199><c> you</c><00:17:28.199><c> would</c><00:17:28.350><c> need</c><00:17:28.439><c> say</c><00:17:28.650><c> samples</c>

00:17:29.090 --> 00:17:29.100 align:start position:0%
wanted 99.99% you would need say samples
 

00:17:29.100 --> 00:17:32.330 align:start position:0%
wanted 99.99% you would need say samples
but<00:17:29.970><c> I</c><00:17:30.470><c> think</c><00:17:31.470><c> nine</c><00:17:31.590><c> nine</c><00:17:31.770><c> percent</c><00:17:31.890><c> is</c>

00:17:32.330 --> 00:17:32.340 align:start position:0%
but I think nine nine percent is
 

00:17:32.340 --> 00:17:34.310 align:start position:0%
but I think nine nine percent is
reasonable<00:17:32.880><c> because</c><00:17:33.080><c> what</c><00:17:34.080><c> that</c><00:17:34.200><c> would</c>

00:17:34.310 --> 00:17:34.320 align:start position:0%
reasonable because what that would
 

00:17:34.320 --> 00:17:36.020 align:start position:0%
reasonable because what that would
basically<00:17:34.500><c> mean</c><00:17:34.800><c> is</c><00:17:35.010><c> that</c><00:17:35.220><c> if</c><00:17:35.460><c> you</c><00:17:35.850><c> are</c><00:17:36.000><c> a</c>

00:17:36.020 --> 00:17:36.030 align:start position:0%
basically mean is that if you are a
 

00:17:36.030 --> 00:17:38.030 align:start position:0%
basically mean is that if you are a
minor<00:17:36.390><c> and</c><00:17:36.720><c> you</c><00:17:36.780><c> wanted</c><00:17:37.080><c> to</c><00:17:37.230><c> do</c><00:17:37.350><c> this</c><00:17:37.470><c> attack</c>

00:17:38.030 --> 00:17:38.040 align:start position:0%
minor and you wanted to do this attack
 

00:17:38.040 --> 00:17:40.550 align:start position:0%
minor and you wanted to do this attack
against<00:17:38.640><c> someone</c><00:17:38.940><c> you</c><00:17:39.870><c> would</c><00:17:39.990><c> effectively</c><00:17:40.350><c> on</c>

00:17:40.550 --> 00:17:40.560 align:start position:0%
against someone you would effectively on
 

00:17:40.560 --> 00:17:43.760 align:start position:0%
against someone you would effectively on
average<00:17:40.950><c> need</c><00:17:41.490><c> to</c><00:17:41.670><c> mind</c><00:17:42.060><c> about</c><00:17:42.360><c> 100</c><00:17:42.780><c> blocks</c><00:17:42.990><c> in</c>

00:17:43.760 --> 00:17:43.770 align:start position:0%
average need to mind about 100 blocks in
 

00:17:43.770 --> 00:17:45.950 align:start position:0%
average need to mind about 100 blocks in
order<00:17:44.220><c> to</c><00:17:44.490><c> get</c><00:17:44.670><c> a</c><00:17:44.700><c> chance</c><00:17:45.060><c> of</c><00:17:45.390><c> mining</c><00:17:45.810><c> of</c>

00:17:45.950 --> 00:17:45.960 align:start position:0%
order to get a chance of mining of
 

00:17:45.960 --> 00:17:47.549 align:start position:0%
order to get a chance of mining of
fooling<00:17:46.470><c> the</c><00:17:46.590><c> like</c><00:17:46.710><c> lion</c><00:17:46.950><c> that</c><00:17:47.160><c> you</c><00:17:47.220><c> want</c><00:17:47.340><c> to</c>

00:17:47.549 --> 00:17:47.559 align:start position:0%
fooling the like lion that you want to
 

00:17:47.559 --> 00:17:50.129 align:start position:0%
fooling the like lion that you want to
or<00:17:47.620><c> to</c><00:17:48.490><c> block</c><00:17:48.759><c> into</c><00:17:49.090><c> thinking</c><00:17:49.690><c> that</c><00:17:49.720><c> block</c><00:17:50.019><c> is</c>

00:17:50.129 --> 00:17:50.139 align:start position:0%
or to block into thinking that block is
 

00:17:50.139 --> 00:17:52.080 align:start position:0%
or to block into thinking that block is
available<00:17:50.529><c> when</c><00:17:50.769><c> it's</c><00:17:50.889><c> not</c><00:17:51.039><c> so</c><00:17:51.909><c> that</c>

00:17:52.080 --> 00:17:52.090 align:start position:0%
available when it's not so that
 

00:17:52.090 --> 00:17:54.690 align:start position:0%
available when it's not so that
increases<00:17:52.389><c> the</c><00:17:52.570><c> cost</c><00:17:52.779><c> of</c><00:17:52.929><c> the</c><00:17:53.019><c> attack</c><00:17:53.700><c> 100x</c>

00:17:54.690 --> 00:17:54.700 align:start position:0%
increases the cost of the attack 100x
 

00:17:54.700 --> 00:17:57.899 align:start position:0%
increases the cost of the attack 100x
which<00:17:55.570><c> which</c><00:17:56.019><c> i</c><00:17:56.139><c> think</c><00:17:56.200><c> is</c><00:17:56.440><c> quite</c><00:17:56.879><c> make</c><00:17:57.879><c> it</c>

00:17:57.899 --> 00:17:57.909 align:start position:0%
which which i think is quite make it
 

00:17:57.909 --> 00:18:01.889 align:start position:0%
which which i think is quite make it
unreasonably<00:17:58.509><c> expensive</c><00:18:00.450><c> yeah</c><00:18:01.450><c> we</c><00:18:01.570><c> have</c><00:18:01.690><c> some</c>

00:18:01.889 --> 00:18:01.899 align:start position:0%
unreasonably expensive yeah we have some
 

00:18:01.899 --> 00:18:03.119 align:start position:0%
unreasonably expensive yeah we have some
performance<00:18:02.320><c> measurements</c><00:18:02.769><c> I'm</c><00:18:02.889><c> not</c><00:18:03.009><c> going</c>

00:18:03.119 --> 00:18:03.129 align:start position:0%
performance measurements I'm not going
 

00:18:03.129 --> 00:18:04.499 align:start position:0%
performance measurements I'm not going
to<00:18:03.190><c> go</c><00:18:03.249><c> into</c><00:18:03.730><c> details</c><00:18:04.120><c> to</c><00:18:04.210><c> them</c><00:18:04.330><c> because</c><00:18:04.480><c> I</c>

00:18:04.499 --> 00:18:04.509 align:start position:0%
to go into details to them because I
 

00:18:04.509 --> 00:18:06.899 align:start position:0%
to go into details to them because I
want<00:18:04.659><c> to</c><00:18:04.749><c> take</c><00:18:04.870><c> questions</c><00:18:05.340><c> but</c><00:18:06.340><c> everything</c><00:18:06.730><c> is</c>

00:18:06.899 --> 00:18:06.909 align:start position:0%
want to take questions but everything is
 

00:18:06.909 --> 00:18:09.930 align:start position:0%
want to take questions but everything is
quite<00:18:07.090><c> efficient</c><00:18:07.450><c> so</c><00:18:08.159><c> this</c><00:18:09.159><c> parameter</c><00:18:09.460><c> is</c><00:18:09.669><c> I'm</c>

00:18:09.930 --> 00:18:09.940 align:start position:0%
quite efficient so this parameter is I'm
 

00:18:09.940 --> 00:18:11.100 align:start position:0%
quite efficient so this parameter is I'm
assuming<00:18:10.480><c> that</c><00:18:10.600><c> you</c><00:18:10.690><c> have</c><00:18:10.809><c> an</c><00:18:10.899><c> intermediate</c>

00:18:11.100 --> 00:18:11.110 align:start position:0%
assuming that you have an intermediate
 

00:18:11.110 --> 00:18:14.149 align:start position:0%
assuming that you have an intermediate
state<00:18:11.559><c> route</c><00:18:11.799><c> after</c><00:18:12.039><c> every</c><00:18:12.999><c> ten</c><00:18:13.389><c> transactions</c>

00:18:14.149 --> 00:18:14.159 align:start position:0%
state route after every ten transactions
 

00:18:14.159 --> 00:18:18.149 align:start position:0%
state route after every ten transactions
so<00:18:15.159><c> the</c><00:18:15.279><c> slides</c><00:18:15.519><c> of</c><00:18:15.639><c> the</c><00:18:15.730><c> for</c><00:18:15.909><c> proof</c><00:18:16.980><c> the</c><00:18:17.980><c> state</c>

00:18:18.149 --> 00:18:18.159 align:start position:0%
so the slides of the for proof the state
 

00:18:18.159 --> 00:18:21.139 align:start position:0%
so the slides of the for proof the state
for<00:18:18.370><c> proof</c><00:18:18.629><c> will</c><00:18:19.629><c> be</c><00:18:19.749><c> about</c><00:18:19.899><c> 14</c><00:18:20.259><c> kilobytes</c>

00:18:21.139 --> 00:18:21.149 align:start position:0%
for proof will be about 14 kilobytes
 

00:18:21.149 --> 00:18:23.519 align:start position:0%
for proof will be about 14 kilobytes
everything<00:18:22.149><c> is</c><00:18:22.419><c> less</c><00:18:22.899><c> than</c><00:18:23.110><c> a</c><00:18:23.139><c> few</c><00:18:23.320><c> kilobytes</c>

00:18:23.519 --> 00:18:23.529 align:start position:0%
everything is less than a few kilobytes
 

00:18:23.529 --> 00:18:26.129 align:start position:0%
everything is less than a few kilobytes
basically<00:18:24.100><c> and</c><00:18:24.399><c> the</c><00:18:25.330><c> biggest</c><00:18:25.629><c> trader</c><00:18:25.840><c> of</c><00:18:25.960><c> them</c>

00:18:26.129 --> 00:18:26.139 align:start position:0%
basically and the biggest trader of them
 

00:18:26.139 --> 00:18:29.100 align:start position:0%
basically and the biggest trader of them
is<00:18:26.409><c> that</c><00:18:26.679><c> if</c><00:18:27.669><c> you're</c><00:18:27.909><c> like</c><00:18:28.090><c> client</c><00:18:28.509><c> that</c><00:18:28.809><c> wants</c>

00:18:29.100 --> 00:18:29.110 align:start position:0%
is that if you're like client that wants
 

00:18:29.110 --> 00:18:32.129 align:start position:0%
is that if you're like client that wants
to<00:18:29.289><c> have</c><00:18:30.009><c> to</c><00:18:30.419><c> have</c><00:18:31.419><c> a</c><00:18:31.450><c> guarantee</c><00:18:31.840><c> that</c><00:18:32.049><c> the</c>

00:18:32.129 --> 00:18:32.139 align:start position:0%
to have to have a guarantee that the
 

00:18:32.139 --> 00:18:35.060 align:start position:0%
to have to have a guarantee that the
data's<00:18:32.679><c> available</c><00:18:33.269><c> then</c><00:18:34.269><c> you</c><00:18:34.419><c> also</c><00:18:34.600><c> have</c><00:18:34.929><c> to</c>

00:18:35.060 --> 00:18:35.070 align:start position:0%
data's available then you also have to
 

00:18:35.070 --> 00:18:37.769 align:start position:0%
data's available then you also have to
actually<00:18:36.070><c> download</c><00:18:36.759><c> something</c><00:18:37.480><c> called</c><00:18:37.720><c> the</c>

00:18:37.769 --> 00:18:37.779 align:start position:0%
actually download something called the
 

00:18:37.779 --> 00:18:40.440 align:start position:0%
actually download something called the
access<00:18:38.139><c> routes</c><00:18:38.350><c> we</c><00:18:39.190><c> are</c><00:18:39.340><c> basically</c><00:18:39.700><c> every</c>

00:18:40.440 --> 00:18:40.450 align:start position:0%
access routes we are basically every
 

00:18:40.450 --> 00:18:43.230 align:start position:0%
access routes we are basically every
single<00:18:40.809><c> row</c><00:18:40.960><c> and</c><00:18:41.409><c> column</c><00:18:41.740><c> in</c><00:18:41.950><c> this</c><00:18:42.759><c> in</c><00:18:43.119><c> this</c>

00:18:43.230 --> 00:18:43.240 align:start position:0%
single row and column in this in this
 

00:18:43.240 --> 00:18:45.509 align:start position:0%
single row and column in this in this
square<00:18:43.539><c> has</c><00:18:44.139><c> its</c><00:18:44.379><c> own</c><00:18:44.529><c> medical</c><00:18:44.980><c> route</c><00:18:45.159><c> that</c>

00:18:45.509 --> 00:18:45.519 align:start position:0%
square has its own medical route that
 

00:18:45.519 --> 00:18:47.749 align:start position:0%
square has its own medical route that
you<00:18:45.580><c> have</c><00:18:45.700><c> to</c><00:18:45.820><c> download</c><00:18:46.149><c> and</c><00:18:46.419><c> that</c><00:18:46.710><c> does</c>

00:18:47.749 --> 00:18:47.759 align:start position:0%
you have to download and that does
 

00:18:47.759 --> 00:18:52.440 align:start position:0%
you have to download and that does
increase<00:18:48.759><c> the</c><00:18:49.179><c> header</c><00:18:49.360><c> by</c><00:18:50.169><c> about</c><00:18:50.440><c> 10x</c><00:18:51.330><c> but</c><00:18:52.330><c> you</c>

00:18:52.440 --> 00:18:52.450 align:start position:0%
increase the header by about 10x but you
 

00:18:52.450 --> 00:18:53.759 align:start position:0%
increase the header by about 10x but you
don't<00:18:52.600><c> have</c><00:18:52.659><c> to</c><00:18:52.749><c> do</c><00:18:52.899><c> this</c><00:18:53.019><c> if</c><00:18:53.259><c> you</c><00:18:53.350><c> do</c><00:18:53.499><c> want</c><00:18:53.679><c> the</c>

00:18:53.759 --> 00:18:53.769 align:start position:0%
don't have to do this if you do want the
 

00:18:53.769 --> 00:18:55.169 align:start position:0%
don't have to do this if you do want the
data<00:18:53.919><c> availability</c><00:18:54.340><c> guarantees</c><00:18:54.549><c> you</c><00:18:55.029><c> can</c>

00:18:55.169 --> 00:18:55.179 align:start position:0%
data availability guarantees you can
 

00:18:55.179 --> 00:18:57.330 align:start position:0%
data availability guarantees you can
still<00:18:55.419><c> run</c><00:18:55.600><c> like</c><00:18:55.899><c> superlight</c><00:18:56.379><c> clients</c><00:18:56.860><c> which</c>

00:18:57.330 --> 00:18:57.340 align:start position:0%
still run like superlight clients which
 

00:18:57.340 --> 00:19:00.299 align:start position:0%
still run like superlight clients which
have<00:18:57.519><c> no</c><00:18:58.049><c> guarantees</c><00:18:59.049><c> but</c><00:18:59.679><c> I</c><00:18:59.740><c> think</c><00:19:00.129><c> like</c><00:19:00.249><c> I</c>

00:19:00.299 --> 00:19:00.309 align:start position:0%
have no guarantees but I think like I
 

00:19:00.309 --> 00:19:04.879 align:start position:0%
have no guarantees but I think like I
think<00:19:00.580><c> this</c><00:19:00.940><c> is</c><00:19:01.029><c> quite</c><00:19:01.149><c> reasonable</c><00:19:01.499><c> trade-off</c>

00:19:04.879 --> 00:19:04.889 align:start position:0%
 
 

00:19:04.889 --> 00:19:08.359 align:start position:0%
 
and<00:19:05.889><c> in</c><00:19:06.129><c> terms</c><00:19:06.309><c> of</c><00:19:06.399><c> computation</c><00:19:06.879><c> it's</c><00:19:07.119><c> all</c>

00:19:08.359 --> 00:19:08.369 align:start position:0%
and in terms of computation it's all
 

00:19:08.369 --> 00:19:12.659 align:start position:0%
and in terms of computation it's all
it's<00:19:09.369><c> all</c><00:19:09.399><c> quite</c><00:19:09.700><c> efficient</c><00:19:10.659><c> the</c><00:19:11.669><c> generating</c>

00:19:12.659 --> 00:19:12.669 align:start position:0%
it's all quite efficient the generating
 

00:19:12.669 --> 00:19:15.419 align:start position:0%
it's all quite efficient the generating
the<00:19:12.850><c> state</c><00:19:13.029><c> for</c><00:19:13.240><c> proof</c><00:19:13.950><c> look</c><00:19:14.950><c> quite</c><00:19:15.159><c> expensive</c>

00:19:15.419 --> 00:19:15.429 align:start position:0%
the state for proof look quite expensive
 

00:19:15.429 --> 00:19:17.100 align:start position:0%
the state for proof look quite expensive
here<00:19:15.700><c> but</c><00:19:15.909><c> us</c><00:19:15.999><c> because</c><00:19:16.269><c> my</c><00:19:16.450><c> spouse</c><00:19:16.720><c> medical</c>

00:19:17.100 --> 00:19:17.110 align:start position:0%
here but us because my spouse medical
 

00:19:17.110 --> 00:19:20.539 align:start position:0%
here but us because my spouse medical
tree<00:19:17.289><c> implementation</c><00:19:17.610><c> is</c><00:19:18.610><c> quite</c><00:19:18.850><c> inefficient</c>

00:19:20.539 --> 00:19:20.549 align:start position:0%
tree implementation is quite inefficient
 

00:19:20.549 --> 00:19:23.399 align:start position:0%
tree implementation is quite inefficient
verifying<00:19:21.549><c> for</c><00:19:21.789><c> proofs</c><00:19:22.149><c> verifying</c><00:19:23.019><c> sample</c>

00:19:23.399 --> 00:19:23.409 align:start position:0%
verifying for proofs verifying sample
 

00:19:23.409 --> 00:19:24.960 align:start position:0%
verifying for proofs verifying sample
responses<00:19:23.799><c> verifying</c><00:19:24.279><c> availability</c><00:19:24.850><c> for</c>

00:19:24.960 --> 00:19:24.970 align:start position:0%
responses verifying availability for
 

00:19:24.970 --> 00:19:27.539 align:start position:0%
responses verifying availability for
proofs<00:19:25.269><c> or</c><00:19:25.509><c> all</c><00:19:25.659><c> in</c><00:19:26.110><c> Slab</c><00:19:26.889><c> many</c><00:19:27.100><c> second</c><00:19:27.369><c> times</c>

00:19:27.539 --> 00:19:27.549 align:start position:0%
proofs or all in Slab many second times
 

00:19:27.549 --> 00:19:31.680 align:start position:0%
proofs or all in Slab many second times
so<00:19:27.970><c> it's</c><00:19:28.840><c> all</c><00:19:29.019><c> PI</c><00:19:29.230><c> efficient</c><00:19:30.330><c> so</c><00:19:31.330><c> if</c><00:19:31.419><c> we</c><00:19:31.509><c> look</c>

00:19:31.680 --> 00:19:31.690 align:start position:0%
so it's all PI efficient so if we look
 

00:19:31.690 --> 00:19:33.869 align:start position:0%
so it's all PI efficient so if we look
at<00:19:31.749><c> the</c><00:19:31.840><c> paper</c><00:19:32.019><c> the</c><00:19:32.619><c> link</c><00:19:32.799><c> is</c><00:19:32.919><c> there</c><00:19:33.070><c> code</c><00:19:33.730><c> is</c>

00:19:33.869 --> 00:19:33.879 align:start position:0%
at the paper the link is there code is
 

00:19:33.879 --> 00:19:35.879 align:start position:0%
at the paper the link is there code is
codes<00:19:34.330><c> in</c><00:19:34.600><c> github</c><00:19:34.779><c> we</c><00:19:35.049><c> have</c><00:19:35.139><c> the</c><00:19:35.230><c> code</c><00:19:35.409><c> for</c><00:19:35.440><c> the</c>

00:19:35.879 --> 00:19:35.889 align:start position:0%
codes in github we have the code for the
 

00:19:35.889 --> 00:19:40.169 align:start position:0%
codes in github we have the code for the
date<00:19:36.879><c> availability</c><00:19:37.389><c> code</c><00:19:38.259><c> they</c><00:19:39.220><c> read</c><00:19:39.369><c> using</c><00:19:40.090><c> a</c>

00:19:40.169 --> 00:19:40.179 align:start position:0%
date availability code they read using a
 

00:19:40.179 --> 00:19:42.330 align:start position:0%
date availability code they read using a
rigid<00:19:40.299><c> coding</c><00:19:40.690><c> also</c><00:19:41.499><c> a</c><00:19:41.649><c> sparse</c><00:19:41.919><c> metallurgy</c>

00:19:42.330 --> 00:19:42.340 align:start position:0%
rigid coding also a sparse metallurgy
 

00:19:42.340 --> 00:19:43.710 align:start position:0%
rigid coding also a sparse metallurgy
implementation<00:19:42.759><c> and</c><00:19:42.879><c> go</c><00:19:42.999><c> and</c><00:19:43.240><c> a</c><00:19:43.299><c> prototype</c>

00:19:43.710 --> 00:19:43.720 align:start position:0%
implementation and go and a prototype
 

00:19:43.720 --> 00:19:45.810 align:start position:0%
implementation and go and a prototype
for<00:19:43.960><c> the</c><00:19:44.019><c> full</c><00:19:44.200><c> proofs</c><00:19:44.379><c> itself</c><00:19:44.740><c> thank</c><00:19:45.700><c> you</c>

00:19:45.810 --> 00:19:45.820 align:start position:0%
for the full proofs itself thank you
 

00:19:45.820 --> 00:19:55.120 align:start position:0%
for the full proofs itself thank you
I'll<00:19:45.940><c> take</c><00:19:45.970><c> some</c><00:19:46.299><c> questions</c><00:19:46.450><c> now</c>

00:19:55.120 --> 00:19:55.130 align:start position:0%
 
 

00:19:55.130 --> 00:19:56.860 align:start position:0%
 
the<00:19:55.550><c> reason</c><00:19:55.790><c> for</c><00:19:55.820><c> not</c><00:19:55.970><c> adding</c><00:19:56.660><c> another</c>

00:19:56.860 --> 00:19:56.870 align:start position:0%
the reason for not adding another
 

00:19:56.870 --> 00:19:58.390 align:start position:0%
the reason for not adding another
dimension<00:19:57.320><c> is</c><00:19:57.470><c> just</c><00:19:57.500><c> simply</c><00:19:57.860><c> is</c><00:19:58.040><c> just</c><00:19:58.250><c> the</c>

00:19:58.390 --> 00:19:58.400 align:start position:0%
dimension is just simply is just the
 

00:19:58.400 --> 00:20:01.120 align:start position:0%
dimension is just simply is just the
right<00:19:58.820><c> amount</c><00:19:59.420><c> that</c><00:19:59.630><c> they</c><00:19:59.780><c> can</c><00:19:59.920><c> the</c><00:20:00.920><c> minor</c>

00:20:01.120 --> 00:20:01.130 align:start position:0%
right amount that they can the minor
 

00:20:01.130 --> 00:20:03.970 align:start position:0%
right amount that they can the minor
needs<00:20:01.400><c> to</c><00:20:01.550><c> fake</c><00:20:01.870><c> so</c><00:20:02.870><c> actually</c><00:20:03.290><c> if</c><00:20:03.440><c> you</c><00:20:03.560><c> if</c><00:20:03.590><c> you</c>

00:20:03.970 --> 00:20:03.980 align:start position:0%
needs to fake so actually if you if you
 

00:20:03.980 --> 00:20:07.060 align:start position:0%
needs to fake so actually if you if you
add<00:20:04.130><c> more</c><00:20:04.820><c> dimensions</c><00:20:05.330><c> the</c><00:20:05.990><c> minor</c><00:20:06.260><c> it</c><00:20:06.860><c> makes</c>

00:20:07.060 --> 00:20:07.070 align:start position:0%
add more dimensions the minor it makes
 

00:20:07.070 --> 00:20:09.790 align:start position:0%
add more dimensions the minor it makes
it<00:20:07.220><c> worse</c><00:20:07.840><c> from</c><00:20:08.840><c> a</c><00:20:08.870><c> mystic</c><00:20:09.350><c> perspective</c>

00:20:09.790 --> 00:20:09.800 align:start position:0%
it worse from a mystic perspective
 

00:20:09.800 --> 00:20:12.340 align:start position:0%
it worse from a mystic perspective
because<00:20:10.040><c> the</c><00:20:10.310><c> minor</c><00:20:10.550><c> has</c><00:20:11.000><c> to</c><00:20:11.150><c> hide</c><00:20:11.330><c> less</c><00:20:11.660><c> but</c>

00:20:12.340 --> 00:20:12.350 align:start position:0%
because the minor has to hide less but
 

00:20:12.350 --> 00:20:15.220 align:start position:0%
because the minor has to hide less but
of<00:20:12.500><c> the</c><00:20:12.650><c> pieces</c><00:20:13.280><c> of</c><00:20:13.490><c> block</c><00:20:13.760><c> block</c><00:20:14.570><c> it's</c><00:20:15.080><c> like</c>

00:20:15.220 --> 00:20:15.230 align:start position:0%
of the pieces of block block it's like
 

00:20:15.230 --> 00:20:17.440 align:start position:0%
of the pieces of block block it's like
with<00:20:15.890><c> the</c><00:20:16.010><c> one</c><00:20:16.160><c> dimensional</c><00:20:16.670><c> scheme</c><00:20:16.970><c> you</c><00:20:17.420><c> have</c>

00:20:17.440 --> 00:20:17.450 align:start position:0%
with the one dimensional scheme you have
 

00:20:17.450 --> 00:20:19.630 align:start position:0%
with the one dimensional scheme you have
to<00:20:17.630><c> hide</c><00:20:17.780><c> 50%</c><00:20:18.320><c> with</c><00:20:18.950><c> the</c><00:20:19.070><c> two</c><00:20:19.250><c> dimensional</c>

00:20:19.630 --> 00:20:19.640 align:start position:0%
to hide 50% with the two dimensional
 

00:20:19.640 --> 00:20:21.460 align:start position:0%
to hide 50% with the two dimensional
scheme<00:20:19.910><c> you</c><00:20:20.060><c> only</c><00:20:20.180><c> have</c><00:20:20.300><c> to</c><00:20:20.390><c> hide</c><00:20:20.510><c> 25%</c><00:20:21.140><c> with</c><00:20:21.410><c> a</c>

00:20:21.460 --> 00:20:21.470 align:start position:0%
scheme you only have to hide 25% with a
 

00:20:21.470 --> 00:20:23.350 align:start position:0%
scheme you only have to hide 25% with a
few<00:20:21.590><c> dimensional</c><00:20:22.040><c> scheme</c><00:20:22.280><c> you</c><00:20:22.880><c> have</c><00:20:22.940><c> to</c><00:20:23.180><c> hire</c>

00:20:23.350 --> 00:20:23.360 align:start position:0%
few dimensional scheme you have to hire
 

00:20:23.360 --> 00:20:27.100 align:start position:0%
few dimensional scheme you have to hire
12.5%<00:20:24.050><c> so</c><00:20:24.980><c> that</c><00:20:25.850><c> means</c><00:20:26.030><c> that</c><00:20:26.270><c> that</c><00:20:26.600><c> means</c><00:20:26.810><c> you</c>

00:20:27.100 --> 00:20:27.110 align:start position:0%
12.5% so that means that that means you
 

00:20:27.110 --> 00:20:28.600 align:start position:0%
12.5% so that means that that means you
have<00:20:27.140><c> to</c><00:20:27.350><c> sample</c><00:20:27.500><c> more</c><00:20:27.830><c> slices</c><00:20:28.250><c> to</c><00:20:28.400><c> get</c><00:20:28.550><c> the</c>

00:20:28.600 --> 00:20:28.610 align:start position:0%
have to sample more slices to get the
 

00:20:28.610 --> 00:20:30.940 align:start position:0%
have to sample more slices to get the
same<00:20:28.790><c> sample</c><00:20:29.750><c> more</c><00:20:29.900><c> pieces</c><00:20:30.440><c> to</c><00:20:30.560><c> get</c><00:20:30.680><c> the</c><00:20:30.770><c> same</c>

00:20:30.940 --> 00:20:30.950 align:start position:0%
same sample more pieces to get the same
 

00:20:30.950 --> 00:20:33.970 align:start position:0%
same sample more pieces to get the same
guarantee<00:20:31.760><c> bility</c><00:20:32.450><c> of</c><00:20:32.510><c> guarantees</c><00:20:32.870><c> and</c><00:20:33.500><c> also</c>

00:20:33.970 --> 00:20:33.980 align:start position:0%
guarantee bility of guarantees and also
 

00:20:33.980 --> 00:20:35.170 align:start position:0%
guarantee bility of guarantees and also
the<00:20:34.070><c> other</c><00:20:34.190><c> problem</c><00:20:34.520><c> with</c><00:20:34.670><c> having</c><00:20:34.820><c> higher</c>

00:20:35.170 --> 00:20:35.180 align:start position:0%
the other problem with having higher
 

00:20:35.180 --> 00:20:38.080 align:start position:0%
the other problem with having higher
dimensions<00:20:35.660><c> is</c><00:20:35.900><c> that</c><00:20:36.620><c> it</c><00:20:37.090><c> dramatically</c>

00:20:38.080 --> 00:20:38.090 align:start position:0%
dimensions is that it dramatically
 

00:20:38.090 --> 00:20:40.720 align:start position:0%
dimensions is that it dramatically
increases<00:20:38.300><c> the</c><00:20:38.780><c> number</c><00:20:39.290><c> of</c><00:20:39.320><c> milk</c><00:20:39.740><c> routes</c><00:20:40.040><c> that</c>

00:20:40.720 --> 00:20:40.730 align:start position:0%
increases the number of milk routes that
 

00:20:40.730 --> 00:20:43.000 align:start position:0%
increases the number of milk routes that
my<00:20:41.330><c> client</c><00:20:41.660><c> has</c><00:20:41.750><c> download</c><00:20:42.140><c> so</c><00:20:42.710><c> I</c><00:20:42.770><c> don't</c><00:20:42.950><c> really</c>

00:20:43.000 --> 00:20:43.010 align:start position:0%
my client has download so I don't really
 

00:20:43.010 --> 00:20:44.110 align:start position:0%
my client has download so I don't really
think<00:20:43.130><c> it's</c><00:20:43.400><c> worth</c><00:20:43.550><c> it</c><00:20:43.730><c> unless</c><00:20:43.820><c> you</c><00:20:44.000><c> have</c>

00:20:44.110 --> 00:20:44.120 align:start position:0%
think it's worth it unless you have
 

00:20:44.120 --> 00:20:47.530 align:start position:0%
think it's worth it unless you have
insanely<00:20:44.480><c> large</c><00:20:44.810><c> block</c><00:20:45.140><c> size</c><00:20:45.320><c> I</c><00:20:45.760><c> like</c><00:20:46.760><c> incent</c>

00:20:47.530 --> 00:20:47.540 align:start position:0%
insanely large block size I like incent
 

00:20:47.540 --> 00:20:50.970 align:start position:0%
insanely large block size I like incent
insanely<00:20:47.870><c> large</c><00:20:48.080><c> intervals</c><00:20:48.770><c> between</c><00:20:48.950><c> blocks</c>

00:20:50.970 --> 00:20:50.980 align:start position:0%
insanely large intervals between blocks
 

00:20:50.980 --> 00:20:56.770 align:start position:0%
insanely large intervals between blocks
yes<00:20:52.420><c> so</c><00:20:53.420><c> this</c><00:20:54.080><c> scheme</c><00:20:54.770><c> be</c><00:20:55.250><c> used</c><00:20:56.030><c> in</c><00:20:56.660><c> the</c>

00:20:56.770 --> 00:20:56.780 align:start position:0%
yes so this scheme be used in the
 

00:20:56.780 --> 00:21:01.290 align:start position:0%
yes so this scheme be used in the
context<00:20:57.230><c> of</c><00:20:57.350><c> plasma</c><00:20:58.280><c> to</c><00:20:58.430><c> force</c><00:20:59.300><c> essentially</c>

00:21:01.290 --> 00:21:01.300 align:start position:0%
context of plasma to force essentially
 

00:21:01.300 --> 00:21:03.640 align:start position:0%
context of plasma to force essentially
operating<00:21:02.300><c> party</c><00:21:02.750><c> to</c><00:21:02.960><c> essentially</c><00:21:03.470><c> like</c>

00:21:03.640 --> 00:21:03.650 align:start position:0%
operating party to essentially like
 

00:21:03.650 --> 00:21:05.530 align:start position:0%
operating party to essentially like
either<00:21:04.100><c> they</c><00:21:04.400><c> provide</c><00:21:04.730><c> the</c><00:21:04.850><c> proof</c><00:21:05.030><c> or</c><00:21:05.300><c> they</c>

00:21:05.530 --> 00:21:05.540 align:start position:0%
either they provide the proof or they
 

00:21:05.540 --> 00:21:08.350 align:start position:0%
either they provide the proof or they
get<00:21:05.660><c> slashed</c><00:21:06.790><c> because</c><00:21:07.790><c> as</c><00:21:07.970><c> far</c><00:21:08.150><c> as</c><00:21:08.270><c> I'm</c>

00:21:08.350 --> 00:21:08.360 align:start position:0%
get slashed because as far as I'm
 

00:21:08.360 --> 00:21:10.750 align:start position:0%
get slashed because as far as I'm
concerned<00:21:08.720><c> this</c><00:21:09.320><c> allows</c><00:21:09.800><c> somebody</c><00:21:10.070><c> just</c><00:21:10.520><c> you</c>

00:21:10.750 --> 00:21:10.760 align:start position:0%
concerned this allows somebody just you
 

00:21:10.760 --> 00:21:19.390 align:start position:0%
concerned this allows somebody just you
cannot<00:21:11.180><c> know</c><00:21:11.360><c> if</c><00:21:11.510><c> they</c><00:21:18.010><c> so</c><00:21:19.010><c> I'm</c><00:21:19.100><c> not</c><00:21:19.190><c> an</c><00:21:19.340><c> expert</c>

00:21:19.390 --> 00:21:19.400 align:start position:0%
cannot know if they so I'm not an expert
 

00:21:19.400 --> 00:21:21.040 align:start position:0%
cannot know if they so I'm not an expert
on<00:21:19.670><c> plasma</c><00:21:20.090><c> but</c><00:21:20.300><c> there</c><00:21:20.420><c> was</c><00:21:20.510><c> a</c><00:21:20.630><c> threat</c><00:21:20.900><c> on</c><00:21:21.020><c> my</c>

00:21:21.040 --> 00:21:21.050 align:start position:0%
on plasma but there was a threat on my
 

00:21:21.050 --> 00:21:22.660 align:start position:0%
on plasma but there was a threat on my
theorem<00:21:21.380><c> research</c><00:21:21.680><c> to</c><00:21:21.920><c> ask</c><00:21:22.100><c> that</c><00:21:22.280><c> question</c>

00:21:22.660 --> 00:21:22.670 align:start position:0%
theorem research to ask that question
 

00:21:22.670 --> 00:21:26.020 align:start position:0%
theorem research to ask that question
and<00:21:22.880><c> a</c><00:21:23.630><c> response</c><00:21:24.230><c> was</c><00:21:24.860><c> from</c><00:21:24.980><c> metallic</c><00:21:25.760><c> said</c>

00:21:26.020 --> 00:21:26.030 align:start position:0%
and a response was from metallic said
 

00:21:26.030 --> 00:21:27.400 align:start position:0%
and a response was from metallic said
that<00:21:26.240><c> it</c><00:21:26.420><c> would</c><00:21:26.510><c> be</c><00:21:26.600><c> quite</c><00:21:26.720><c> reasonable</c><00:21:26.930><c> to</c><00:21:27.200><c> do</c>

00:21:27.400 --> 00:21:27.410 align:start position:0%
that it would be quite reasonable to do
 

00:21:27.410 --> 00:21:33.270 align:start position:0%
that it would be quite reasonable to do
that<00:21:27.590><c> it's</c><00:21:28.010><c> like</c><00:21:28.130><c> if</c><00:21:28.310><c> you</c><00:21:28.400><c> wanted</c><00:21:28.730><c> to</c><00:21:30.640><c> sorry</c>

00:21:33.270 --> 00:21:33.280 align:start position:0%
that it's like if you wanted to sorry
 

00:21:33.280 --> 00:21:36.820 align:start position:0%
that it's like if you wanted to sorry
yeah<00:21:34.280><c> we</c><00:21:34.430><c> deposit</c><00:21:35.270><c> I</c><00:21:36.170><c> think</c><00:21:36.470><c> would</c><00:21:36.590><c> be</c><00:21:36.620><c> quite</c>

00:21:36.820 --> 00:21:36.830 align:start position:0%
yeah we deposit I think would be quite
 

00:21:36.830 --> 00:21:39.670 align:start position:0%
yeah we deposit I think would be quite
reasonable<00:21:37.010><c> to</c><00:21:38.000><c> do</c><00:21:38.120><c> that</c><00:21:38.270><c> and</c><00:21:38.450><c> if</c><00:21:39.200><c> you</c><00:21:39.380><c> wanted</c>

00:21:39.670 --> 00:21:39.680 align:start position:0%
reasonable to do that and if you wanted
 

00:21:39.680 --> 00:21:43.930 align:start position:0%
reasonable to do that and if you wanted
to<00:21:39.740><c> make</c><00:21:40.310><c> the</c><00:21:40.970><c> plasma</c><00:21:41.330><c> operators</c><00:21:42.940><c> evasion</c>

00:21:43.930 --> 00:21:43.940 align:start position:0%
to make the plasma operators evasion
 

00:21:43.940 --> 00:21:45.220 align:start position:0%
to make the plasma operators evasion
code<00:21:44.060><c> dead</c><00:21:44.240><c> blocks</c><00:21:44.450><c> and</c><00:21:44.720><c> then</c><00:21:44.900><c> make</c><00:21:45.080><c> the</c>

00:21:45.220 --> 00:21:45.230 align:start position:0%
code dead blocks and then make the
 

00:21:45.230 --> 00:21:48.610 align:start position:0%
code dead blocks and then make the
clients<00:21:45.890><c> have</c><00:21:46.520><c> to</c><00:21:46.730><c> do</c><00:21:46.880><c> have</c><00:21:47.150><c> to</c><00:21:47.360><c> do</c><00:21:48.050><c> samples</c>

00:21:48.610 --> 00:21:48.620 align:start position:0%
clients have to do have to do samples
 

00:21:48.620 --> 00:21:50.110 align:start position:0%
clients have to do have to do samples
and<00:21:48.920><c> maybe</c><00:21:49.130><c> you</c><00:21:49.280><c> could</c><00:21:49.400><c> even</c><00:21:49.430><c> actually</c><00:21:50.000><c> make</c>

00:21:50.110 --> 00:21:50.120 align:start position:0%
and maybe you could even actually make
 

00:21:50.120 --> 00:21:52.510 align:start position:0%
and maybe you could even actually make
it<00:21:50.240><c> on</c><00:21:50.330><c> the</c><00:21:50.390><c> main</c><00:21:50.540><c> chain</c><00:21:50.810><c> they</c><00:21:51.380><c> have</c><00:21:51.590><c> that</c><00:21:52.010><c> yeah</c>

00:21:52.510 --> 00:21:52.520 align:start position:0%
it on the main chain they have that yeah
 

00:21:52.520 --> 00:21:54.570 align:start position:0%
it on the main chain they have that yeah
after<00:21:52.790><c> some</c><00:21:52.970><c> amount</c><00:21:53.060><c> of</c><00:21:53.240><c> time</c><00:21:53.450><c> or</c><00:21:53.690><c> some</c><00:21:54.050><c> delay</c>

00:21:54.570 --> 00:21:54.580 align:start position:0%
after some amount of time or some delay
 

00:21:54.580 --> 00:21:57.280 align:start position:0%
after some amount of time or some delay
you<00:21:55.580><c> have</c><00:21:55.730><c> the</c><00:21:56.210><c> main</c><00:21:56.360><c> chain</c><00:21:56.570><c> sample</c><00:21:56.990><c> some</c><00:21:57.170><c> of</c>

00:21:57.280 --> 00:21:57.290 align:start position:0%
you have the main chain sample some of
 

00:21:57.290 --> 00:22:04.080 align:start position:0%
you have the main chain sample some of
the<00:21:58.210><c> pieces</c><00:21:59.210><c> as</c><00:21:59.780><c> well</c><00:21:59.990><c> for</c><00:22:00.230><c> extra</c><00:22:00.410><c> security</c>

00:22:04.080 --> 00:22:04.090 align:start position:0%
 
 

00:22:04.090 --> 00:22:09.700 align:start position:0%
 
yeah<00:22:08.140><c> yeah</c><00:22:09.140><c> I</c><00:22:09.170><c> think</c><00:22:09.320><c> would</c><00:22:09.470><c> be</c><00:22:09.560><c> quite</c>

00:22:09.700 --> 00:22:09.710 align:start position:0%
yeah yeah I think would be quite
 

00:22:09.710 --> 00:22:20.740 align:start position:0%
yeah yeah I think would be quite
reasonable<00:22:12.100><c> question</c><00:22:16.000><c> yes</c><00:22:17.290><c> works</c><00:22:18.290><c> so</c><00:22:19.720><c> so</c><00:22:20.720><c> I</c>

00:22:20.740 --> 00:22:20.750 align:start position:0%
reasonable question yes works so so I
 

00:22:20.750 --> 00:22:25.150 align:start position:0%
reasonable question yes works so so I
just<00:22:21.080><c> wondering</c><00:22:22.040><c> if</c><00:22:22.730><c> you</c><00:22:23.270><c> change</c><00:22:23.840><c> one</c><00:22:24.710><c> entry</c>

00:22:25.150 --> 00:22:25.160 align:start position:0%
just wondering if you change one entry
 

00:22:25.160 --> 00:22:29.080 align:start position:0%
just wondering if you change one entry
in<00:22:25.400><c> the</c><00:22:26.000><c> state</c><00:22:26.450><c> then</c><00:22:26.930><c> how</c><00:22:27.260><c> big</c><00:22:27.590><c> part</c><00:22:27.830><c> of</c><00:22:28.070><c> the</c><00:22:28.400><c> of</c>

00:22:29.080 --> 00:22:29.090 align:start position:0%
in the state then how big part of the of
 

00:22:29.090 --> 00:22:32.890 align:start position:0%
in the state then how big part of the of
the<00:22:29.600><c> racial</c><00:22:30.110><c> coding</c><00:22:31.150><c> data</c><00:22:32.150><c> structure</c><00:22:32.720><c> will</c>

00:22:32.890 --> 00:22:32.900 align:start position:0%
the racial coding data structure will
 

00:22:32.900 --> 00:22:35.410 align:start position:0%
the racial coding data structure will
change<00:22:33.230><c> so</c><00:22:33.500><c> how</c><00:22:33.710><c> does</c><00:22:33.770><c> do</c><00:22:34.460><c> changes</c><00:22:35.030><c> like</c>

00:22:35.410 --> 00:22:35.420 align:start position:0%
change so how does do changes like
 

00:22:35.420 --> 00:22:40.060 align:start position:0%
change so how does do changes like
propagate<00:22:36.700><c> so</c><00:22:37.700><c> how</c><00:22:37.880><c> so</c><00:22:38.270><c> what</c><00:22:38.450><c> happens</c><00:22:38.860><c> if</c><00:22:39.860><c> you</c>

00:22:40.060 --> 00:22:40.070 align:start position:0%
propagate so how so what happens if you
 

00:22:40.070 --> 00:22:46.900 align:start position:0%
propagate so how so what happens if you
changed<00:22:40.550><c> the</c><00:22:40.700><c> structure</c><00:22:41.600><c> of</c><00:22:41.870><c> the</c><00:22:42.470><c> state</c><00:22:45.910><c> okay</c>

00:22:46.900 --> 00:22:46.910 align:start position:0%
changed the structure of the state okay
 

00:22:46.910 --> 00:22:53.260 align:start position:0%
changed the structure of the state okay
so<00:22:48.850><c> so</c><00:22:49.850><c> our</c><00:22:50.270><c> data</c><00:22:50.540><c> structures</c><00:22:51.080><c> are</c><00:22:51.890><c> based</c><00:22:52.270><c> on</c>

00:22:53.260 --> 00:22:53.270 align:start position:0%
so so our data structures are based on
 

00:22:53.270 --> 00:22:55.990 align:start position:0%
so so our data structures are based on
like<00:22:54.200><c> three</c><00:22:54.470><c> hushing</c><00:22:54.800><c> which</c><00:22:54.950><c> means</c><00:22:55.190><c> we</c><00:22:55.370><c> we</c>

00:22:55.990 --> 00:22:56.000 align:start position:0%
like three hushing which means we we
 

00:22:56.000 --> 00:22:59.950 align:start position:0%
like three hushing which means we we
just<00:22:56.240><c> change</c><00:22:57.080><c> a</c><00:22:57.230><c> few</c><00:22:57.470><c> entries</c><00:22:58.040><c> but</c><00:22:58.250><c> each</c><00:22:58.960><c> state</c>

00:22:59.950 --> 00:22:59.960 align:start position:0%
just change a few entries but each state
 

00:22:59.960 --> 00:23:03.160 align:start position:0%
just change a few entries but each state
right<00:23:00.230><c> just</c><00:23:00.680><c> changes</c><00:23:01.550><c> as</c><00:23:01.730><c> a</c><00:23:01.760><c> single</c><00:23:02.360><c> entry</c><00:23:02.720><c> and</c>

00:23:03.160 --> 00:23:03.170 align:start position:0%
right just changes as a single entry and
 

00:23:03.170 --> 00:23:06.610 align:start position:0%
right just changes as a single entry and
the<00:23:03.440><c> logarithmic</c><00:23:03.920><c> number</c><00:23:04.220><c> of</c><00:23:05.620><c> intermediate</c>

00:23:06.610 --> 00:23:06.620 align:start position:0%
the logarithmic number of intermediate
 

00:23:06.620 --> 00:23:10.300 align:start position:0%
the logarithmic number of intermediate
try<00:23:06.830><c> nodes</c><00:23:07.070><c> so</c><00:23:08.290><c> how</c><00:23:09.290><c> much</c><00:23:09.440><c> data</c><00:23:09.710><c> will</c><00:23:10.010><c> change</c>

00:23:10.300 --> 00:23:10.310 align:start position:0%
try nodes so how much data will change
 

00:23:10.310 --> 00:23:12.880 align:start position:0%
try nodes so how much data will change
in<00:23:10.520><c> the</c><00:23:10.610><c> racial</c><00:23:10.970><c> code</c><00:23:11.330><c> after</c><00:23:11.780><c> each</c><00:23:12.050><c> state</c>

00:23:12.880 --> 00:23:12.890 align:start position:0%
in the racial code after each state
 

00:23:12.890 --> 00:23:19.470 align:start position:0%
in the racial code after each state
right<00:23:14.110><c> okay</c><00:23:15.110><c> so</c><00:23:15.170><c> let's</c><00:23:15.620><c> go</c><00:23:15.860><c> back</c><00:23:17.770><c> so</c><00:23:18.770><c> this</c><00:23:18.920><c> is</c>

00:23:19.470 --> 00:23:19.480 align:start position:0%
right okay so let's go back so this is
 

00:23:19.480 --> 00:23:22.660 align:start position:0%
right okay so let's go back so this is
version<00:23:20.480><c> of</c><00:23:20.660><c> the</c><00:23:20.750><c> transaction</c><00:23:21.260><c> there</c><00:23:21.410><c> so</c><00:23:22.370><c> what</c>

00:23:22.660 --> 00:23:22.670 align:start position:0%
version of the transaction there so what
 

00:23:22.670 --> 00:23:26.010 align:start position:0%
version of the transaction there so what
you're<00:23:22.760><c> asking</c><00:23:22.880><c> is</c><00:23:23.240><c> if</c><00:23:23.780><c> you</c><00:23:24.470><c> change</c><00:23:24.740><c> a</c><00:23:25.160><c> single</c>

00:23:26.010 --> 00:23:26.020 align:start position:0%
you're asking is if you change a single
 

00:23:26.020 --> 00:23:28.870 align:start position:0%
you're asking is if you change a single
transaction<00:23:27.020><c> how</c><00:23:28.010><c> much</c><00:23:28.220><c> of</c><00:23:28.370><c> the</c><00:23:28.460><c> erasure</c><00:23:28.610><c> code</c>

00:23:28.870 --> 00:23:28.880 align:start position:0%
transaction how much of the erasure code
 

00:23:28.880 --> 00:23:32.440 align:start position:0%
transaction how much of the erasure code
would<00:23:29.060><c> change</c><00:23:31.000><c> well</c><00:23:32.000><c> first</c><00:23:32.210><c> of</c><00:23:32.270><c> all</c><00:23:32.330><c> I'm</c><00:23:32.420><c> not</c>

00:23:32.440 --> 00:23:32.450 align:start position:0%
would change well first of all I'm not
 

00:23:32.450 --> 00:23:34.870 align:start position:0%
would change well first of all I'm not
sure<00:23:32.570><c> why</c><00:23:32.840><c> it</c><00:23:32.900><c> would</c><00:23:33.080><c> matter</c><00:23:33.230><c> because</c><00:23:33.880><c> that</c>

00:23:34.870 --> 00:23:34.880 align:start position:0%
sure why it would matter because that
 

00:23:34.880 --> 00:23:36.070 align:start position:0%
sure why it would matter because that
would<00:23:35.030><c> change</c><00:23:35.060><c> the</c><00:23:35.390><c> medical</c><00:23:35.630><c> roots</c><00:23:35.870><c> as</c><00:23:36.050><c> well</c>

00:23:36.070 --> 00:23:36.080 align:start position:0%
would change the medical roots as well
 

00:23:36.080 --> 00:23:38.020 align:start position:0%
would change the medical roots as well
so<00:23:36.350><c> so</c><00:23:37.220><c> I</c><00:23:37.400><c> don't</c><00:23:37.430><c> think</c><00:23:37.640><c> there's</c><00:23:37.820><c> a</c><00:23:37.880><c> specific</c>

00:23:38.020 --> 00:23:38.030 align:start position:0%
so so I don't think there's a specific
 

00:23:38.030 --> 00:23:42.250 align:start position:0%
so so I don't think there's a specific
attack<00:23:38.360><c> he</c><00:23:38.630><c> can</c><00:23:38.750><c> be</c><00:23:38.870><c> from</c><00:23:39.050><c> that</c><00:23:41.020><c> but</c><00:23:42.020><c> it</c><00:23:42.140><c> would</c>

00:23:42.250 --> 00:23:42.260 align:start position:0%
attack he can be from that but it would
 

00:23:42.260 --> 00:23:45.670 align:start position:0%
attack he can be from that but it would
actually<00:23:42.710><c> change</c><00:23:44.230><c> it</c><00:23:45.230><c> would</c><00:23:45.380><c> change</c><00:23:45.560><c> a</c>

00:23:45.670 --> 00:23:45.680 align:start position:0%
actually change it would change a
 

00:23:45.680 --> 00:23:46.930 align:start position:0%
actually change it would change a
significant<00:23:46.250><c> portion</c><00:23:46.430><c> it</c><00:23:46.700><c> wouldn't</c><00:23:46.910><c> change</c>

00:23:46.930 --> 00:23:46.940 align:start position:0%
significant portion it wouldn't change
 

00:23:46.940 --> 00:23:48.460 align:start position:0%
significant portion it wouldn't change
the<00:23:47.210><c> entire</c><00:23:47.420><c> original</c><00:23:47.660><c> code</c><00:23:47.900><c> I</c><00:23:48.050><c> think</c><00:23:48.260><c> at</c>

00:23:48.460 --> 00:23:48.470 align:start position:0%
the entire original code I think at
 

00:23:48.470 --> 00:23:51.220 align:start position:0%
the entire original code I think at
least<00:23:48.760><c> yeah</c><00:23:49.760><c> it</c><00:23:50.180><c> wouldn't</c><00:23:50.420><c> change</c><00:23:50.480><c> the</c><00:23:50.750><c> entire</c>

00:23:51.220 --> 00:23:51.230 align:start position:0%
least yeah it wouldn't change the entire
 

00:23:51.230 --> 00:23:52.570 align:start position:0%
least yeah it wouldn't change the entire
ridgid<00:23:51.620><c> code</c><00:23:51.740><c> but</c><00:23:51.950><c> I</c><00:23:51.980><c> would</c><00:23:52.100><c> say</c><00:23:52.280><c> it</c><00:23:52.460><c> would</c>

00:23:52.570 --> 00:23:52.580 align:start position:0%
ridgid code but I would say it would
 

00:23:52.580 --> 00:23:55.060 align:start position:0%
ridgid code but I would say it would
change<00:23:52.880><c> a</c><00:23:53.200><c> significant</c><00:23:54.200><c> portion</c><00:23:54.320><c> of</c><00:23:54.590><c> it</c><00:23:54.710><c> so</c><00:23:54.740><c> it</c>

00:23:55.060 --> 00:23:55.070 align:start position:0%
change a significant portion of it so it
 

00:23:55.070 --> 00:23:57.490 align:start position:0%
change a significant portion of it so it
would<00:23:55.190><c> change</c><00:23:55.490><c> at</c><00:23:56.480><c> least</c><00:23:56.750><c> for</c><00:23:57.020><c> example</c><00:23:57.350><c> the</c>

00:23:57.490 --> 00:23:57.500 align:start position:0%
would change at least for example the
 

00:23:57.500 --> 00:24:00.520 align:start position:0%
would change at least for example the
entire<00:23:58.120><c> fourth</c><00:23:59.120><c> quadrants</c><00:23:59.690><c> of</c><00:23:59.810><c> the</c><00:23:59.870><c> of</c><00:24:00.380><c> the</c>

00:24:00.520 --> 00:24:00.530 align:start position:0%
entire fourth quadrants of the of the
 

00:24:00.530 --> 00:24:01.740 align:start position:0%
entire fourth quadrants of the of the
square

00:24:01.740 --> 00:24:01.750 align:start position:0%
square
 

00:24:01.750 --> 00:24:03.460 align:start position:0%
square
all<00:24:02.750><c> right</c><00:24:02.840><c> doesn't</c><00:24:02.960><c> really</c><00:24:03.140><c> matter</c><00:24:03.290><c> because</c>

00:24:03.460 --> 00:24:03.470 align:start position:0%
all right doesn't really matter because
 

00:24:03.470 --> 00:24:05.080 align:start position:0%
all right doesn't really matter because
that<00:24:03.770><c> would</c><00:24:03.920><c> we</c><00:24:04.190><c> also</c><00:24:04.370><c> change</c><00:24:04.670><c> the</c><00:24:04.790><c> medical</c>

00:24:05.080 --> 00:24:05.090 align:start position:0%
that would we also change the medical
 

00:24:05.090 --> 00:24:07.320 align:start position:0%
that would we also change the medical
roots<00:24:05.240><c> of</c><00:24:05.480><c> the</c><00:24:05.600><c> rows</c><00:24:05.780><c> and</c><00:24:05.960><c> columns</c>

00:24:07.320 --> 00:24:07.330 align:start position:0%
roots of the rows and columns
 

00:24:07.330 --> 00:24:13.840 align:start position:0%
roots of the rows and columns
do<00:24:08.330><c> you</c><00:24:08.390><c> write</c><00:24:08.740><c> here</c><00:24:09.740><c> do</c><00:24:10.160><c> you</c><00:24:10.250><c> write</c>

00:24:13.840 --> 00:24:13.850 align:start position:0%
 
 

00:24:13.850 --> 00:24:16.670 align:start position:0%
 
hello<00:24:14.850><c> I</c><00:24:15.480><c> was</c><00:24:15.870><c> wondering</c><00:24:16.260><c> if</c><00:24:16.350><c> you</c><00:24:16.650><c> guys</c>

00:24:16.670 --> 00:24:16.680 align:start position:0%
hello I was wondering if you guys
 

00:24:16.680 --> 00:24:19.310 align:start position:0%
hello I was wondering if you guys
explored<00:24:17.520><c> more</c><00:24:17.850><c> succinct</c><00:24:18.480><c> ways</c><00:24:18.960><c> of</c>

00:24:19.310 --> 00:24:19.320 align:start position:0%
explored more succinct ways of
 

00:24:19.320 --> 00:24:21.380 align:start position:0%
explored more succinct ways of
generating<00:24:19.710><c> about</c><00:24:20.400><c> verifying</c><00:24:20.970><c> the</c><00:24:21.180><c> proof</c>

00:24:21.380 --> 00:24:21.390 align:start position:0%
generating about verifying the proof
 

00:24:21.390 --> 00:24:23.360 align:start position:0%
generating about verifying the proof
seems<00:24:22.020><c> to</c><00:24:22.170><c> me</c><00:24:22.290><c> that</c><00:24:22.320><c> it</c><00:24:22.560><c> could</c><00:24:22.770><c> allow</c><00:24:23.010><c> you</c><00:24:23.070><c> to</c>

00:24:23.360 --> 00:24:23.370 align:start position:0%
seems to me that it could allow you to
 

00:24:23.370 --> 00:24:29.480 align:start position:0%
seems to me that it could allow you to
go<00:24:23.640><c> to</c><00:24:23.670><c> a</c><00:24:23.880><c> higher</c><00:24:24.030><c> dimensional</c><00:24:26.600><c> yeah</c><00:24:27.600><c> and</c><00:24:28.530><c> have</c>

00:24:29.480 --> 00:24:29.490 align:start position:0%
go to a higher dimensional yeah and have
 

00:24:29.490 --> 00:24:33.130 align:start position:0%
go to a higher dimensional yeah and have
some<00:24:29.700><c> blog</c><00:24:29.910><c> posts</c><00:24:29.940><c> on</c><00:24:30.660><c> using</c><00:24:31.650><c> things</c><00:24:32.070><c> like</c>

00:24:33.130 --> 00:24:33.140 align:start position:0%
some blog posts on using things like
 

00:24:33.140 --> 00:24:36.230 align:start position:0%
some blog posts on using things like
proximity<00:24:34.140><c> to</c><00:24:34.560><c> make</c><00:24:34.740><c> it</c><00:24:34.890><c> possible</c><00:24:35.100><c> to</c><00:24:35.430><c> verify</c>

00:24:36.230 --> 00:24:36.240 align:start position:0%
proximity to make it possible to verify
 

00:24:36.240 --> 00:24:39.470 align:start position:0%
proximity to make it possible to verify
that<00:24:36.600><c> the</c><00:24:37.230><c> erasure</c><00:24:37.650><c> code</c><00:24:37.980><c> was</c><00:24:38.790><c> constructed</c>

00:24:39.470 --> 00:24:39.480 align:start position:0%
that the erasure code was constructed
 

00:24:39.480 --> 00:24:43.040 align:start position:0%
that the erasure code was constructed
correctly<00:24:39.990><c> without</c><00:24:40.890><c> having</c><00:24:41.550><c> to</c><00:24:41.790><c> rely</c><00:24:42.570><c> on</c><00:24:42.690><c> for</c>

00:24:43.040 --> 00:24:43.050 align:start position:0%
correctly without having to rely on for
 

00:24:43.050 --> 00:24:45.770 align:start position:0%
correctly without having to rely on for
proofs<00:24:43.410><c> and</c><00:24:44.280><c> so</c><00:24:44.580><c> this</c><00:24:45.030><c> is</c><00:24:45.180><c> like</c><00:24:45.360><c> something</c>

00:24:45.770 --> 00:24:45.780 align:start position:0%
proofs and so this is like something
 

00:24:45.780 --> 00:24:51.530 align:start position:0%
proofs and so this is like something
completely<00:24:46.140><c> different</c><00:24:48.830><c> like</c><00:24:50.270><c> this</c><00:24:51.270><c> would</c><00:24:51.420><c> be</c>

00:24:51.530 --> 00:24:51.540 align:start position:0%
completely different like this would be
 

00:24:51.540 --> 00:24:53.180 align:start position:0%
completely different like this would be
like<00:24:51.660><c> if</c><00:24:52.470><c> you</c><00:24:52.590><c> wanted</c><00:24:52.800><c> to</c><00:24:52.920><c> completely</c>

00:24:53.180 --> 00:24:53.190 align:start position:0%
like if you wanted to completely
 

00:24:53.190 --> 00:24:54.260 align:start position:0%
like if you wanted to completely
eliminate<00:24:53.340><c> four</c><00:24:53.850><c> proofs</c>

00:24:54.260 --> 00:24:54.270 align:start position:0%
eliminate four proofs
 

00:24:54.270 --> 00:24:56.090 align:start position:0%
eliminate four proofs
then<00:24:54.870><c> you</c><00:24:55.050><c> would</c><00:24:55.170><c> need</c><00:24:55.320><c> a</c><00:24:55.380><c> way</c><00:24:55.560><c> for</c><00:24:55.710><c> like</c>

00:24:56.090 --> 00:24:56.100 align:start position:0%
then you would need a way for like
 

00:24:56.100 --> 00:24:58.600 align:start position:0%
then you would need a way for like
clients<00:24:56.550><c> to</c><00:24:56.700><c> succeed</c><00:24:57.060><c> me</c><00:24:57.240><c> verify</c><00:24:57.630><c> that</c><00:24:58.320><c> the</c>

00:24:58.600 --> 00:24:58.610 align:start position:0%
clients to succeed me verify that the
 

00:24:58.610 --> 00:25:00.890 align:start position:0%
clients to succeed me verify that the
state<00:24:59.610><c> transitions</c><00:25:00.090><c> in</c><00:25:00.330><c> the</c><00:25:00.450><c> block</c><00:25:00.660><c> were</c>

00:25:00.890 --> 00:25:00.900 align:start position:0%
state transitions in the block were
 

00:25:00.900 --> 00:25:03.770 align:start position:0%
state transitions in the block were
valid<00:25:01.230><c> and</c><00:25:01.410><c> also</c><00:25:02.040><c> successfully</c><00:25:02.610><c> verify</c><00:25:03.000><c> that</c>

00:25:03.770 --> 00:25:03.780 align:start position:0%
valid and also successfully verify that
 

00:25:03.780 --> 00:25:05.450 align:start position:0%
valid and also successfully verify that
the<00:25:04.230><c> erasure</c><00:25:04.560><c> code</c><00:25:04.800><c> was</c><00:25:04.980><c> constructed</c>

00:25:05.450 --> 00:25:05.460 align:start position:0%
the erasure code was constructed
 

00:25:05.460 --> 00:25:07.550 align:start position:0%
the erasure code was constructed
correctly<00:25:05.580><c> and</c><00:25:06.180><c> there</c><00:25:06.660><c> are</c><00:25:06.810><c> some</c><00:25:07.140><c> ideas</c><00:25:07.290><c> that</c>

00:25:07.550 --> 00:25:07.560 align:start position:0%
correctly and there are some ideas that
 

00:25:07.560 --> 00:25:10.790 align:start position:0%
correctly and there are some ideas that
I<00:25:07.710><c> had</c><00:25:07.830><c> to</c><00:25:07.920><c> do</c><00:25:08.040><c> that</c><00:25:08.160><c> and</c><00:25:08.390><c> explore</c><00:25:09.650><c> but</c><00:25:10.650><c> there</c>

00:25:10.790 --> 00:25:10.800 align:start position:0%
I had to do that and explore but there
 

00:25:10.800 --> 00:25:12.260 align:start position:0%
I had to do that and explore but there
are<00:25:10.890><c> currently</c><00:25:11.220><c> some</c><00:25:11.610><c> trade-offs</c><00:25:11.970><c> something</c>

00:25:12.260 --> 00:25:12.270 align:start position:0%
are currently some trade-offs something
 

00:25:12.270 --> 00:25:14.710 align:start position:0%
are currently some trade-offs something
be<00:25:12.510><c> ironed</c><00:25:12.780><c> out</c><00:25:12.870><c> if</c><00:25:13.530><c> I</c><00:25:13.650><c> recall</c><00:25:13.800><c> correctly</c><00:25:14.040><c> and</c>

00:25:14.710 --> 00:25:14.720 align:start position:0%
be ironed out if I recall correctly and
 

00:25:14.720 --> 00:25:17.960 align:start position:0%
be ironed out if I recall correctly and
one<00:25:15.720><c> of</c><00:25:15.810><c> the</c><00:25:15.900><c> ideas</c><00:25:16.170><c> had</c><00:25:16.830><c> the</c><00:25:17.070><c> drawback</c><00:25:17.940><c> of</c>

00:25:17.960 --> 00:25:17.970 align:start position:0%
one of the ideas had the drawback of
 

00:25:17.970 --> 00:25:21.890 align:start position:0%
one of the ideas had the drawback of
potentially<00:25:18.630><c> requiring</c><00:25:19.530><c> medical</c><00:25:20.900><c> making</c>

00:25:21.890 --> 00:25:21.900 align:start position:0%
potentially requiring medical making
 

00:25:21.900 --> 00:25:23.150 align:start position:0%
potentially requiring medical making
Michael<00:25:22.080><c> branches</c><00:25:22.470><c> a</c><00:25:22.500><c> hundred</c><00:25:22.770><c> times</c><00:25:22.950><c> bigger</c>

00:25:23.150 --> 00:25:23.160 align:start position:0%
Michael branches a hundred times bigger
 

00:25:23.160 --> 00:25:25.580 align:start position:0%
Michael branches a hundred times bigger
in<00:25:24.060><c> the</c><00:25:24.180><c> worst</c><00:25:24.360><c> case</c><00:25:24.510><c> scenario</c><00:25:24.840><c> but</c><00:25:25.440><c> it's</c>

00:25:25.580 --> 00:25:25.590 align:start position:0%
in the worst case scenario but it's
 

00:25:25.590 --> 00:25:27.080 align:start position:0%
in the worst case scenario but it's
definitely<00:25:25.710><c> something</c><00:25:26.610><c> that</c><00:25:26.640><c> people</c><00:25:26.790><c> are</c>

00:25:27.080 --> 00:25:27.090 align:start position:0%
definitely something that people are
 

00:25:27.090 --> 00:25:28.120 align:start position:0%
definitely something that people are
looking<00:25:27.210><c> into</c>

00:25:28.120 --> 00:25:28.130 align:start position:0%
looking into
 

00:25:28.130 --> 00:25:29.840 align:start position:0%
looking into
excuse<00:25:29.130><c> me</c><00:25:29.190><c> stuff</c><00:25:29.400><c> another</c><00:25:29.550><c> round</c><00:25:29.790><c> of</c>

00:25:29.840 --> 00:25:29.850 align:start position:0%
excuse me stuff another round of
 

00:25:29.850 --> 00:25:41.000 align:start position:0%
excuse me stuff another round of
applause<00:25:30.060><c> please</c>

00:25:41.000 --> 00:25:41.010 align:start position:0%
 
 

00:25:41.010 --> 00:25:43.070 align:start position:0%
 
you