WEBVTT
Kind: captions
Language: en

00:00:01.160 --> 00:00:06.690 align:start position:0%
 
[Music]

00:00:06.690 --> 00:00:06.700 align:start position:0%
 
 

00:00:06.700 --> 00:00:09.990 align:start position:0%
 
[Music]

00:00:09.990 --> 00:00:10.000 align:start position:0%
[Music]
 

00:00:10.000 --> 00:00:11.430 align:start position:0%
[Music]
awesome<00:00:10.320><c> it's</c><00:00:10.480><c> great</c><00:00:10.639><c> to</c><00:00:10.719><c> see</c><00:00:10.880><c> everyone</c><00:00:11.080><c> at</c>

00:00:11.430 --> 00:00:11.440 align:start position:0%
awesome it's great to see everyone at
 

00:00:11.440 --> 00:00:14.749 align:start position:0%
awesome it's great to see everyone at
Devcon<00:00:12.440><c> um</c><00:00:12.759><c> thank</c><00:00:12.920><c> you</c><00:00:13.040><c> all</c><00:00:13.200><c> for</c><00:00:13.400><c> coming</c><00:00:14.280><c> today</c>

00:00:14.749 --> 00:00:14.759 align:start position:0%
Devcon um thank you all for coming today
 

00:00:14.759 --> 00:00:16.230 align:start position:0%
Devcon um thank you all for coming today
I'm<00:00:14.920><c> going</c><00:00:15.080><c> to</c><00:00:15.200><c> be</c><00:00:15.360><c> talking</c><00:00:15.799><c> about</c>

00:00:16.230 --> 00:00:16.240 align:start position:0%
I'm going to be talking about
 

00:00:16.240 --> 00:00:19.590 align:start position:0%
I'm going to be talking about
programmable<00:00:16.960><c> cryptography</c><00:00:17.960><c> and</c><00:00:18.600><c> ethereum</c>

00:00:19.590 --> 00:00:19.600 align:start position:0%
programmable cryptography and ethereum
 

00:00:19.600 --> 00:00:21.870 align:start position:0%
programmable cryptography and ethereum
as<00:00:19.800><c> a</c><00:00:19.960><c> quick</c><00:00:20.199><c> introduction</c><00:00:20.960><c> I'm</c><00:00:21.160><c> gub</c><00:00:21.400><c> sheep</c>

00:00:21.870 --> 00:00:21.880 align:start position:0%
as a quick introduction I'm gub sheep
 

00:00:21.880 --> 00:00:24.310 align:start position:0%
as a quick introduction I'm gub sheep
I'm<00:00:21.960><c> one</c><00:00:22.080><c> of</c><00:00:22.160><c> the</c><00:00:22.279><c> co-founders</c><00:00:22.920><c> of</c><00:00:23.080><c> zerox</c><00:00:23.640><c> Park</c>

00:00:24.310 --> 00:00:24.320 align:start position:0%
I'm one of the co-founders of zerox Park
 

00:00:24.320 --> 00:00:26.269 align:start position:0%
I'm one of the co-founders of zerox Park
we're<00:00:24.519><c> an</c><00:00:24.680><c> organization</c><00:00:25.599><c> that</c><00:00:25.760><c> emerged</c><00:00:26.199><c> out</c>

00:00:26.269 --> 00:00:26.279 align:start position:0%
we're an organization that emerged out
 

00:00:26.279 --> 00:00:28.589 align:start position:0%
we're an organization that emerged out
of<00:00:26.400><c> the</c><00:00:26.599><c> ethereum</c><00:00:27.199><c> ecosystem</c><00:00:27.960><c> about</c><00:00:28.199><c> 3</c><00:00:28.400><c> years</c>

00:00:28.589 --> 00:00:28.599 align:start position:0%
of the ethereum ecosystem about 3 years
 

00:00:28.599 --> 00:00:30.870 align:start position:0%
of the ethereum ecosystem about 3 years
ago<00:00:29.400><c> and</c><00:00:29.519><c> since</c><00:00:29.679><c> we</c><00:00:30.039><c> first</c><00:00:30.199><c> coined</c><00:00:30.560><c> the</c><00:00:30.640><c> term</c>

00:00:30.870 --> 00:00:30.880 align:start position:0%
ago and since we first coined the term
 

00:00:30.880 --> 00:00:33.670 align:start position:0%
ago and since we first coined the term
programmable<00:00:31.400><c> cryptography</c><00:00:32.239><c> in</c><00:00:32.480><c> 2022</c><00:00:33.480><c> we've</c>

00:00:33.670 --> 00:00:33.680 align:start position:0%
programmable cryptography in 2022 we've
 

00:00:33.680 --> 00:00:35.229 align:start position:0%
programmable cryptography in 2022 we've
been<00:00:33.840><c> working</c><00:00:34.360><c> to</c><00:00:34.760><c> accelerate</c><00:00:35.160><c> the</c>

00:00:35.229 --> 00:00:35.239 align:start position:0%
been working to accelerate the
 

00:00:35.239 --> 00:00:37.150 align:start position:0%
been working to accelerate the
development<00:00:35.680><c> of</c><00:00:35.800><c> the</c><00:00:35.879><c> field</c><00:00:36.640><c> from</c><00:00:36.960><c> a</c>

00:00:37.150 --> 00:00:37.160 align:start position:0%
development of the field from a
 

00:00:37.160 --> 00:00:39.350 align:start position:0%
development of the field from a
technical<00:00:37.840><c> ecosystem</c><00:00:38.480><c> and</c><00:00:38.640><c> conceptual</c>

00:00:39.350 --> 00:00:39.360 align:start position:0%
technical ecosystem and conceptual
 

00:00:39.360 --> 00:00:41.150 align:start position:0%
technical ecosystem and conceptual
perspective<00:00:40.360><c> our</c><00:00:40.559><c> goal</c><00:00:40.760><c> is</c><00:00:40.879><c> to</c><00:00:41.000><c> take</c>

00:00:41.150 --> 00:00:41.160 align:start position:0%
perspective our goal is to take
 

00:00:41.160 --> 00:00:42.670 align:start position:0%
perspective our goal is to take
programmable<00:00:41.680><c> cryptography</c><00:00:42.239><c> from</c><00:00:42.360><c> research</c>

00:00:42.670 --> 00:00:42.680 align:start position:0%
programmable cryptography from research
 

00:00:42.680 --> 00:00:44.830 align:start position:0%
programmable cryptography from research
to<00:00:42.879><c> production</c><00:00:43.640><c> and</c><00:00:43.760><c> to</c><00:00:43.879><c> harness</c><00:00:44.239><c> its</c><00:00:44.440><c> powers</c>

00:00:44.830 --> 00:00:44.840 align:start position:0%
to production and to harness its powers
 

00:00:44.840 --> 00:00:47.150 align:start position:0%
to production and to harness its powers
for<00:00:45.000><c> a</c><00:00:45.120><c> new</c><00:00:45.239><c> Digital</c>

00:00:47.150 --> 00:00:47.160 align:start position:0%
for a new Digital
 

00:00:47.160 --> 00:00:49.790 align:start position:0%
for a new Digital
Universe<00:00:48.160><c> a</c><00:00:48.320><c> lot</c><00:00:48.440><c> of</c><00:00:48.640><c> this</c><00:00:48.879><c> talk</c><00:00:49.280><c> will</c><00:00:49.480><c> center</c>

00:00:49.790 --> 00:00:49.800 align:start position:0%
Universe a lot of this talk will center
 

00:00:49.800 --> 00:00:51.990 align:start position:0%
Universe a lot of this talk will center
around<00:00:50.000><c> the</c><00:00:50.120><c> following</c><00:00:50.520><c> question</c><00:00:51.399><c> how</c><00:00:51.559><c> do</c><00:00:51.760><c> we</c>

00:00:51.990 --> 00:00:52.000 align:start position:0%
around the following question how do we
 

00:00:52.000 --> 00:00:55.389 align:start position:0%
around the following question how do we
compute<00:00:52.600><c> together</c><00:00:53.559><c> specifically</c><00:00:54.559><c> how</c><00:00:54.680><c> do</c><00:00:54.960><c> we</c>

00:00:55.389 --> 00:00:55.399 align:start position:0%
compute together specifically how do we
 

00:00:55.399 --> 00:00:57.950 align:start position:0%
compute together specifically how do we
as<00:00:55.520><c> in</c><00:00:55.800><c> a</c><00:00:55.920><c> group</c><00:00:56.120><c> of</c><00:00:56.320><c> multiple</c><00:00:56.800><c> people</c><00:00:57.440><c> perform</c>

00:00:57.950 --> 00:00:57.960 align:start position:0%
as in a group of multiple people perform
 

00:00:57.960 --> 00:01:00.470 align:start position:0%
as in a group of multiple people perform
a<00:00:58.160><c> computation</c><00:00:58.719><c> or</c><00:00:58.960><c> execute</c><00:00:59.359><c> a</c><00:00:59.480><c> program</c>

00:01:00.470 --> 00:01:00.480 align:start position:0%
a computation or execute a program
 

00:01:00.480 --> 00:01:02.709 align:start position:0%
a computation or execute a program
together<00:01:01.480><c> now</c><00:01:01.600><c> to</c><00:01:01.760><c> give</c><00:01:01.920><c> some</c><00:01:02.160><c> context</c><00:01:02.559><c> on</c>

00:01:02.709 --> 00:01:02.719 align:start position:0%
together now to give some context on
 

00:01:02.719 --> 00:01:04.469 align:start position:0%
together now to give some context on
this<00:01:02.920><c> question</c><00:01:03.519><c> I</c><00:01:03.600><c> want</c><00:01:03.760><c> to</c><00:01:03.920><c> take</c><00:01:04.080><c> us</c><00:01:04.280><c> back</c>

00:01:04.469 --> 00:01:04.479 align:start position:0%
this question I want to take us back
 

00:01:04.479 --> 00:01:06.230 align:start position:0%
this question I want to take us back
about<00:01:04.680><c> 30</c><00:01:04.960><c> or</c><00:01:05.080><c> 40</c><00:01:05.400><c> years</c><00:01:05.640><c> to</c><00:01:05.760><c> the</c><00:01:05.880><c> earliest</c>

00:01:06.230 --> 00:01:06.240 align:start position:0%
about 30 or 40 years to the earliest
 

00:01:06.240 --> 00:01:08.390 align:start position:0%
about 30 or 40 years to the earliest
days<00:01:06.439><c> of</c><00:01:06.520><c> the</c><00:01:06.640><c> internet</c><00:01:07.479><c> in</c><00:01:07.600><c> the</c><00:01:07.720><c> beginning</c>

00:01:08.390 --> 00:01:08.400 align:start position:0%
days of the internet in the beginning
 

00:01:08.400 --> 00:01:10.550 align:start position:0%
days of the internet in the beginning
the<00:01:08.560><c> internet</c><00:01:09.080><c> was</c><00:01:09.240><c> a</c><00:01:09.400><c> peer-to-peer</c><00:01:09.840><c> Network</c>

00:01:10.550 --> 00:01:10.560 align:start position:0%
the internet was a peer-to-peer Network
 

00:01:10.560 --> 00:01:12.830 align:start position:0%
the internet was a peer-to-peer Network
for<00:01:11.000><c> essentially</c><00:01:11.759><c> transmitting</c><00:01:12.400><c> bits</c>

00:01:12.830 --> 00:01:12.840 align:start position:0%
for essentially transmitting bits
 

00:01:12.840 --> 00:01:15.390 align:start position:0%
for essentially transmitting bits
between<00:01:13.280><c> equal</c><00:01:13.640><c> peers</c><00:01:14.640><c> this</c><00:01:14.799><c> means</c><00:01:15.159><c> that</c><00:01:15.280><c> you</c>

00:01:15.390 --> 00:01:15.400 align:start position:0%
between equal peers this means that you
 

00:01:15.400 --> 00:01:17.749 align:start position:0%
between equal peers this means that you
could<00:01:15.560><c> do</c><00:01:15.759><c> things</c><00:01:16.280><c> like</c><00:01:16.759><c> send</c><00:01:17.040><c> a</c><00:01:17.240><c> document</c><00:01:17.600><c> to</c>

00:01:17.749 --> 00:01:17.759 align:start position:0%
could do things like send a document to
 

00:01:17.759 --> 00:01:19.950 align:start position:0%
could do things like send a document to
another<00:01:18.040><c> IP</c><00:01:18.360><c> address</c><00:01:18.840><c> using</c><00:01:19.159><c> protocols</c><00:01:19.759><c> like</c>

00:01:19.950 --> 00:01:19.960 align:start position:0%
another IP address using protocols like
 

00:01:19.960 --> 00:01:23.789 align:start position:0%
another IP address using protocols like
FTP<00:01:20.799><c> or</c><00:01:21.439><c> SMTP</c><00:01:22.439><c> at</c><00:01:22.600><c> this</c><00:01:22.799><c> point</c><00:01:23.240><c> there</c><00:01:23.360><c> was</c><00:01:23.560><c> not</c>

00:01:23.789 --> 00:01:23.799 align:start position:0%
FTP or SMTP at this point there was not
 

00:01:23.799 --> 00:01:26.149 align:start position:0%
FTP or SMTP at this point there was not
yet<00:01:24.159><c> any</c><00:01:24.400><c> notion</c><00:01:24.759><c> of</c><00:01:25.119><c> you</c><00:01:25.240><c> know</c><00:01:25.439><c> web</c><00:01:25.640><c> servers</c>

00:01:26.149 --> 00:01:26.159 align:start position:0%
yet any notion of you know web servers
 

00:01:26.159 --> 00:01:27.469 align:start position:0%
yet any notion of you know web servers
as<00:01:26.280><c> we</c><00:01:26.400><c> traditionally</c><00:01:26.880><c> think</c><00:01:27.079><c> about</c><00:01:27.280><c> them</c>

00:01:27.469 --> 00:01:27.479 align:start position:0%
as we traditionally think about them
 

00:01:27.479 --> 00:01:31.030 align:start position:0%
as we traditionally think about them
today<00:01:28.400><c> or</c><00:01:28.560><c> the</c><00:01:28.720><c> client</c><00:01:29.000><c> server</c><00:01:29.320><c> model</c><00:01:30.320><c> rather</c>

00:01:31.030 --> 00:01:31.040 align:start position:0%
today or the client server model rather
 

00:01:31.040 --> 00:01:32.630 align:start position:0%
today or the client server model rather
the<00:01:31.159><c> internet</c><00:01:31.799><c> instead</c><00:01:32.079><c> of</c><00:01:32.159><c> being</c><00:01:32.320><c> an</c><00:01:32.439><c> answer</c>

00:01:32.630 --> 00:01:32.640 align:start position:0%
the internet instead of being an answer
 

00:01:32.640 --> 00:01:34.149 align:start position:0%
the internet instead of being an answer
to<00:01:32.799><c> the</c><00:01:32.880><c> question</c><00:01:33.119><c> of</c><00:01:33.280><c> how</c><00:01:33.360><c> do</c><00:01:33.520><c> we</c><00:01:33.680><c> compute</c>

00:01:34.149 --> 00:01:34.159 align:start position:0%
to the question of how do we compute
 

00:01:34.159 --> 00:01:35.590 align:start position:0%
to the question of how do we compute
together<00:01:34.680><c> was</c><00:01:34.840><c> more</c><00:01:34.960><c> of</c><00:01:35.079><c> a</c><00:01:35.200><c> peer-to-peer</c>

00:01:35.590 --> 00:01:35.600 align:start position:0%
together was more of a peer-to-peer
 

00:01:35.600 --> 00:01:38.510 align:start position:0%
together was more of a peer-to-peer
Network<00:01:36.240><c> for</c><00:01:36.640><c> communicating</c><00:01:37.520><c> together</c><00:01:38.360><c> but</c>

00:01:38.510 --> 00:01:38.520 align:start position:0%
Network for communicating together but
 

00:01:38.520 --> 00:01:40.830 align:start position:0%
Network for communicating together but
Computing<00:01:38.920><c> is</c><00:01:39.079><c> something</c><00:01:39.560><c> much</c><00:01:39.759><c> more</c><00:01:39.960><c> than</c>

00:01:40.830 --> 00:01:40.840 align:start position:0%
Computing is something much more than
 

00:01:40.840 --> 00:01:43.870 align:start position:0%
Computing is something much more than
that<00:01:41.840><c> and</c><00:01:42.000><c> pretty</c><00:01:42.280><c> early</c><00:01:42.560><c> on</c><00:01:43.280><c> people</c><00:01:43.560><c> started</c>

00:01:43.870 --> 00:01:43.880 align:start position:0%
that and pretty early on people started
 

00:01:43.880 --> 00:01:46.069 align:start position:0%
that and pretty early on people started
to<00:01:44.119><c> realize</c><00:01:44.840><c> that</c><00:01:44.960><c> it's</c><00:01:45.159><c> useful</c><00:01:45.520><c> to</c><00:01:45.680><c> be</c><00:01:45.880><c> able</c>

00:01:46.069 --> 00:01:46.079 align:start position:0%
to realize that it's useful to be able
 

00:01:46.079 --> 00:01:47.670 align:start position:0%
to realize that it's useful to be able
to<00:01:46.159><c> do</c><00:01:46.320><c> more</c><00:01:46.520><c> than</c><00:01:46.680><c> just</c><00:01:46.799><c> send</c><00:01:47.119><c> data</c><00:01:47.360><c> back</c><00:01:47.479><c> and</c>

00:01:47.670 --> 00:01:47.680 align:start position:0%
to do more than just send data back and
 

00:01:47.680 --> 00:01:49.429 align:start position:0%
to do more than just send data back and
forth<00:01:48.399><c> it</c><00:01:48.479><c> would</c><00:01:48.600><c> be</c><00:01:48.680><c> useful</c><00:01:48.960><c> to</c><00:01:49.040><c> be</c><00:01:49.119><c> able</c><00:01:49.280><c> to</c>

00:01:49.429 --> 00:01:49.439 align:start position:0%
forth it would be useful to be able to
 

00:01:49.439 --> 00:01:51.389 align:start position:0%
forth it would be useful to be able to
run<00:01:49.880><c> programs</c><00:01:50.479><c> on</c><00:01:50.640><c> this</c><00:01:50.799><c> data</c><00:01:51.040><c> that's</c><00:01:51.200><c> being</c>

00:01:51.389 --> 00:01:51.399 align:start position:0%
run programs on this data that's being
 

00:01:51.399 --> 00:01:54.950 align:start position:0%
run programs on this data that's being
passed<00:01:51.680><c> around</c><00:01:51.920><c> on</c><00:01:52.040><c> the</c><00:01:52.640><c> internet</c><00:01:53.640><c> but</c><00:01:54.520><c> with</c>

00:01:54.950 --> 00:01:54.960 align:start position:0%
passed around on the internet but with
 

00:01:54.960 --> 00:01:56.830 align:start position:0%
passed around on the internet but with
the<00:01:55.520><c> existing</c><00:01:55.920><c> setup</c><00:01:56.240><c> of</c><00:01:56.360><c> the</c><00:01:56.439><c> internet</c><00:01:56.719><c> in</c>

00:01:56.830 --> 00:01:56.840 align:start position:0%
the existing setup of the internet in
 

00:01:56.840 --> 00:01:58.990 align:start position:0%
the existing setup of the internet in
the<00:01:56.920><c> early</c><00:01:57.159><c> days</c><00:01:57.320><c> there</c><00:01:57.439><c> was</c><00:01:57.560><c> a</c><00:01:57.920><c> problem</c><00:01:58.920><c> in</c>

00:01:58.990 --> 00:01:59.000 align:start position:0%
the early days there was a problem in
 

00:01:59.000 --> 00:02:01.230 align:start position:0%
the early days there was a problem in
the<00:01:59.159><c> days</c><00:01:59.320><c> of</c><00:01:59.439><c> the</c><00:01:59.520><c> early</c><00:01:59.960><c> internet</c><00:02:00.680><c> the</c><00:02:00.840><c> abil</c>

00:02:01.230 --> 00:02:01.240 align:start position:0%
the days of the early internet the abil
 

00:02:01.240 --> 00:02:03.149 align:start position:0%
the days of the early internet the abil
the<00:02:01.360><c> ability</c><00:02:01.680><c> to</c><00:02:01.880><c> compute</c><00:02:02.360><c> was</c><00:02:02.560><c> limited</c><00:02:02.920><c> to</c>

00:02:03.149 --> 00:02:03.159 align:start position:0%
the ability to compute was limited to
 

00:02:03.159 --> 00:02:04.830 align:start position:0%
the ability to compute was limited to
individual<00:02:03.640><c> machines</c><00:02:04.159><c> running</c><00:02:04.479><c> programs</c>

00:02:04.830 --> 00:02:04.840 align:start position:0%
individual machines running programs
 

00:02:04.840 --> 00:02:07.109 align:start position:0%
individual machines running programs
over<00:02:05.000><c> their</c><00:02:05.200><c> own</c><00:02:05.600><c> data</c><00:02:06.360><c> so</c><00:02:06.479><c> you</c><00:02:06.600><c> could</c><00:02:06.799><c> only</c>

00:02:07.109 --> 00:02:07.119 align:start position:0%
over their own data so you could only
 

00:02:07.119 --> 00:02:09.469 align:start position:0%
over their own data so you could only
run<00:02:07.360><c> a</c><00:02:07.560><c> program</c><00:02:08.239><c> over</c><00:02:08.640><c> data</c><00:02:08.920><c> that</c><00:02:09.039><c> lives</c>

00:02:09.469 --> 00:02:09.479 align:start position:0%
run a program over data that lives
 

00:02:09.479 --> 00:02:11.070 align:start position:0%
run a program over data that lives
physically<00:02:10.000><c> on</c><00:02:10.160><c> your</c><00:02:10.319><c> own</c><00:02:10.520><c> device</c><00:02:10.840><c> you</c><00:02:10.920><c> know</c>

00:02:11.070 --> 00:02:11.080 align:start position:0%
physically on your own device you know
 

00:02:11.080 --> 00:02:13.750 align:start position:0%
physically on your own device you know
that<00:02:11.200><c> makes</c><00:02:11.440><c> sense</c><00:02:12.040><c> so</c><00:02:12.239><c> most</c><00:02:12.599><c> apps</c><00:02:13.319><c> looked</c>

00:02:13.750 --> 00:02:13.760 align:start position:0%
that makes sense so most apps looked
 

00:02:13.760 --> 00:02:15.990 align:start position:0%
that makes sense so most apps looked
like<00:02:14.120><c> single</c><00:02:14.519><c> player</c><00:02:15.000><c> programs</c><00:02:15.480><c> imagine</c>

00:02:15.990 --> 00:02:16.000 align:start position:0%
like single player programs imagine
 

00:02:16.000 --> 00:02:17.830 align:start position:0%
like single player programs imagine
games<00:02:16.440><c> like</c><00:02:16.640><c> solitire</c><00:02:17.319><c> you</c><00:02:17.440><c> know</c><00:02:17.519><c> a</c><00:02:17.599><c> single</c>

00:02:17.830 --> 00:02:17.840 align:start position:0%
games like solitire you know a single
 

00:02:17.840 --> 00:02:19.390 align:start position:0%
games like solitire you know a single
player<00:02:18.080><c> game</c><00:02:18.360><c> or</c><00:02:18.640><c> something</c><00:02:18.879><c> like</c><00:02:19.000><c> Flappy</c>

00:02:19.390 --> 00:02:19.400 align:start position:0%
player game or something like Flappy
 

00:02:19.400 --> 00:02:23.150 align:start position:0%
player game or something like Flappy
Bird<00:02:20.319><c> um</c><00:02:21.000><c> or</c><00:02:21.239><c> tools</c><00:02:21.760><c> like</c><00:02:22.000><c> spreadsheets</c><00:02:22.920><c> or</c>

00:02:23.150 --> 00:02:23.160 align:start position:0%
Bird um or tools like spreadsheets or
 

00:02:23.160 --> 00:02:25.589 align:start position:0%
Bird um or tools like spreadsheets or
word<00:02:23.480><c> processors</c><00:02:24.120><c> or</c><00:02:24.319><c> photo</c><00:02:24.680><c> editing</c><00:02:25.120><c> tools</c>

00:02:25.589 --> 00:02:25.599 align:start position:0%
word processors or photo editing tools
 

00:02:25.599 --> 00:02:27.550 align:start position:0%
word processors or photo editing tools
or<00:02:26.000><c> a</c><00:02:26.160><c> calculator</c><00:02:26.680><c> that</c><00:02:26.800><c> just</c><00:02:26.959><c> runs</c><00:02:27.239><c> locally</c>

00:02:27.550 --> 00:02:27.560 align:start position:0%
or a calculator that just runs locally
 

00:02:27.560 --> 00:02:29.869 align:start position:0%
or a calculator that just runs locally
on<00:02:27.680><c> your</c><00:02:27.800><c> own</c><00:02:28.239><c> device</c><00:02:29.239><c> but</c><00:02:29.360><c> of</c><00:02:29.440><c> course</c><00:02:29.560><c> we</c><00:02:29.680><c> want</c>

00:02:29.869 --> 00:02:29.879 align:start position:0%
on your own device but of course we want
 

00:02:29.879 --> 00:02:31.589 align:start position:0%
on your own device but of course we want
wanted<00:02:30.040><c> to</c><00:02:30.160><c> do</c><00:02:30.280><c> more</c><00:02:30.720><c> you</c><00:02:30.800><c> know</c><00:02:30.959><c> we</c><00:02:31.080><c> wanted</c><00:02:31.319><c> to</c>

00:02:31.589 --> 00:02:31.599 align:start position:0%
wanted to do more you know we wanted to
 

00:02:31.599 --> 00:02:34.150 align:start position:0%
wanted to do more you know we wanted to
compute<00:02:32.400><c> together</c><00:02:33.120><c> and</c><00:02:33.239><c> to</c><00:02:33.360><c> have</c><00:02:33.519><c> services</c>

00:02:34.150 --> 00:02:34.160 align:start position:0%
compute together and to have services
 

00:02:34.160 --> 00:02:36.430 align:start position:0%
compute together and to have services
like<00:02:34.440><c> marketplaces</c><00:02:35.319><c> or</c><00:02:35.599><c> ride</c><00:02:35.840><c> sharing</c><00:02:36.200><c> apps</c>

00:02:36.430 --> 00:02:36.440 align:start position:0%
like marketplaces or ride sharing apps
 

00:02:36.440 --> 00:02:37.949 align:start position:0%
like marketplaces or ride sharing apps
or<00:02:36.640><c> social</c><00:02:36.959><c> networks</c><00:02:37.319><c> or</c><00:02:37.519><c> massively</c>

00:02:37.949 --> 00:02:37.959 align:start position:0%
or social networks or massively
 

00:02:37.959 --> 00:02:39.550 align:start position:0%
or social networks or massively
multiplayer<00:02:38.480><c> games</c><00:02:38.720><c> or</c><00:02:38.879><c> global</c><00:02:39.239><c> payment</c>

00:02:39.550 --> 00:02:39.560 align:start position:0%
multiplayer games or global payment
 

00:02:39.560 --> 00:02:42.509 align:start position:0%
multiplayer games or global payment
systems<00:02:39.920><c> or</c><00:02:40.080><c> dating</c><00:02:40.400><c> apps</c><00:02:40.680><c> or</c><00:02:41.120><c> all</c><00:02:41.319><c> sorts</c><00:02:41.560><c> of</c>

00:02:42.509 --> 00:02:42.519 align:start position:0%
systems or dating apps or all sorts of
 

00:02:42.519 --> 00:02:45.070 align:start position:0%
systems or dating apps or all sorts of
things<00:02:43.519><c> and</c><00:02:43.640><c> so</c><00:02:43.879><c> we</c><00:02:44.200><c> came</c><00:02:44.400><c> up</c><00:02:44.560><c> with</c><00:02:44.680><c> a</c><00:02:44.800><c> way</c><00:02:44.920><c> of</c>

00:02:45.070 --> 00:02:45.080 align:start position:0%
things and so we came up with a way of
 

00:02:45.080 --> 00:02:47.229 align:start position:0%
things and so we came up with a way of
sort<00:02:45.239><c> of</c><00:02:45.680><c> simulating</c><00:02:46.680><c> this</c><00:02:46.840><c> idea</c><00:02:47.080><c> of</c>

00:02:47.229 --> 00:02:47.239 align:start position:0%
sort of simulating this idea of
 

00:02:47.239 --> 00:02:49.350 align:start position:0%
sort of simulating this idea of
computing<00:02:47.840><c> together</c><00:02:48.440><c> while</c><00:02:48.640><c> in</c><00:02:48.840><c> reality</c><00:02:49.280><c> we</c>

00:02:49.350 --> 00:02:49.360 align:start position:0%
computing together while in reality we
 

00:02:49.360 --> 00:02:51.390 align:start position:0%
computing together while in reality we
were<00:02:49.720><c> actually</c><00:02:50.080><c> still</c><00:02:50.360><c> sticking</c><00:02:50.800><c> to</c><00:02:51.200><c> the</c>

00:02:51.390 --> 00:02:51.400 align:start position:0%
were actually still sticking to the
 

00:02:51.400 --> 00:02:54.270 align:start position:0%
were actually still sticking to the
single<00:02:51.800><c> player</c><00:02:52.200><c> compute</c><00:02:52.959><c> model</c><00:02:53.959><c> and</c><00:02:54.120><c> that</c>

00:02:54.270 --> 00:02:54.280 align:start position:0%
single player compute model and that
 

00:02:54.280 --> 00:02:56.149 align:start position:0%
single player compute model and that
first<00:02:54.519><c> solution</c><00:02:55.120><c> the</c><00:02:55.319><c> strategy</c><00:02:55.680><c> for</c><00:02:55.879><c> the</c><00:02:56.000><c> last</c>

00:02:56.149 --> 00:02:56.159 align:start position:0%
first solution the strategy for the last
 

00:02:56.159 --> 00:02:58.949 align:start position:0%
first solution the strategy for the last
30<00:02:56.480><c> years</c><00:02:57.040><c> has</c><00:02:57.200><c> to</c><00:02:57.599><c> has</c><00:02:57.720><c> been</c><00:02:57.920><c> to</c><00:02:58.159><c> pick</c><00:02:58.680><c> one</c>

00:02:58.949 --> 00:02:58.959 align:start position:0%
30 years has to has been to pick one
 

00:02:58.959 --> 00:03:00.910 align:start position:0%
30 years has to has been to pick one
very<00:02:59.200><c> important</c><00:02:59.560><c> note</c><00:03:00.159><c> like</c><00:03:00.319><c> Dave</c><00:03:00.640><c> over</c><00:03:00.800><c> here</c>

00:03:00.910 --> 00:03:00.920 align:start position:0%
very important note like Dave over here
 

00:03:00.920 --> 00:03:03.910 align:start position:0%
very important note like Dave over here
in<00:03:01.000><c> the</c><00:03:01.280><c> middle</c><00:03:02.280><c> and</c><00:03:02.440><c> to</c><00:03:02.599><c> promote</c><00:03:02.959><c> Dave</c><00:03:03.640><c> such</c>

00:03:03.910 --> 00:03:03.920 align:start position:0%
in the middle and to promote Dave such
 

00:03:03.920 --> 00:03:07.869 align:start position:0%
in the middle and to promote Dave such
that<00:03:04.159><c> we</c><00:03:04.400><c> all</c><00:03:04.799><c> give</c><00:03:05.280><c> Dave</c><00:03:06.200><c> uh</c><00:03:06.680><c> all</c><00:03:06.799><c> of</c><00:03:06.959><c> our</c><00:03:07.159><c> data</c>

00:03:07.869 --> 00:03:07.879 align:start position:0%
that we all give Dave uh all of our data
 

00:03:07.879 --> 00:03:09.589 align:start position:0%
that we all give Dave uh all of our data
and<00:03:07.959><c> now</c><00:03:08.159><c> Dave</c><00:03:08.480><c> can</c><00:03:08.640><c> basically</c><00:03:08.920><c> run</c><00:03:09.239><c> something</c>

00:03:09.589 --> 00:03:09.599 align:start position:0%
and now Dave can basically run something
 

00:03:09.599 --> 00:03:12.309 align:start position:0%
and now Dave can basically run something
like<00:03:09.760><c> the</c><00:03:09.920><c> Facebook</c><00:03:10.280><c> backend</c><00:03:11.040><c> as</c><00:03:11.239><c> if</c><00:03:11.519><c> it</c><00:03:11.720><c> was</c><00:03:12.120><c> a</c>

00:03:12.309 --> 00:03:12.319 align:start position:0%
like the Facebook backend as if it was a
 

00:03:12.319 --> 00:03:14.949 align:start position:0%
like the Facebook backend as if it was a
single<00:03:12.760><c> player</c><00:03:13.400><c> application</c><00:03:14.280><c> running</c><00:03:14.760><c> just</c>

00:03:14.949 --> 00:03:14.959 align:start position:0%
single player application running just
 

00:03:14.959 --> 00:03:16.949 align:start position:0%
single player application running just
on<00:03:15.200><c> Dave's</c><00:03:15.519><c> machine</c><00:03:16.360><c> so</c><00:03:16.519><c> this</c><00:03:16.640><c> has</c><00:03:16.760><c> been</c><00:03:16.840><c> the</c>

00:03:16.949 --> 00:03:16.959 align:start position:0%
on Dave's machine so this has been the
 

00:03:16.959 --> 00:03:18.430 align:start position:0%
on Dave's machine so this has been the
status<00:03:17.239><c> quo</c><00:03:17.480><c> for</c><00:03:17.599><c> many</c>

00:03:18.430 --> 00:03:18.440 align:start position:0%
status quo for many
 

00:03:18.440 --> 00:03:20.830 align:start position:0%
status quo for many
decades<00:03:19.440><c> and</c><00:03:20.159><c> uh</c><00:03:20.280><c> you</c><00:03:20.360><c> know</c><00:03:20.519><c> from</c><00:03:20.680><c> this</c>

00:03:20.830 --> 00:03:20.840 align:start position:0%
decades and uh you know from this
 

00:03:20.840 --> 00:03:23.309 align:start position:0%
decades and uh you know from this
example<00:03:21.159><c> we</c><00:03:21.239><c> can</c><00:03:21.319><c> sort</c><00:03:21.480><c> of</c><00:03:21.599><c> see</c><00:03:22.280><c> why</c><00:03:22.560><c> servers</c>

00:03:23.309 --> 00:03:23.319 align:start position:0%
example we can sort of see why servers
 

00:03:23.319 --> 00:03:24.750 align:start position:0%
example we can sort of see why servers
came<00:03:23.480><c> to</c><00:03:23.640><c> exist</c><00:03:23.920><c> in</c><00:03:24.000><c> the</c><00:03:24.120><c> first</c><00:03:24.319><c> place</c><00:03:24.560><c> web</c>

00:03:24.750 --> 00:03:24.760 align:start position:0%
came to exist in the first place web
 

00:03:24.760 --> 00:03:26.229 align:start position:0%
came to exist in the first place web
servers<00:03:25.360><c> do</c><00:03:25.560><c> several</c><00:03:25.879><c> things</c><00:03:26.080><c> that</c>

00:03:26.229 --> 00:03:26.239 align:start position:0%
servers do several things that
 

00:03:26.239 --> 00:03:28.350 align:start position:0%
servers do several things that
individuals<00:03:26.760><c> and</c><00:03:27.000><c> pure</c><00:03:27.319><c> peer-to-peer</c><00:03:27.720><c> inter</c>

00:03:28.350 --> 00:03:28.360 align:start position:0%
individuals and pure peer-to-peer inter
 

00:03:28.360 --> 00:03:29.949 align:start position:0%
individuals and pure peer-to-peer inter
uh<00:03:28.519><c> pure</c><00:03:28.799><c> peer-to-peer</c><00:03:29.159><c> Networks</c><00:03:29.799><c> like</c><00:03:29.879><c> the</c>

00:03:29.949 --> 00:03:29.959 align:start position:0%
uh pure peer-to-peer Networks like the
 

00:03:29.959 --> 00:03:32.429 align:start position:0%
uh pure peer-to-peer Networks like the
early<00:03:30.200><c> internet</c><00:03:30.840><c> can't</c><00:03:31.080><c> do</c><00:03:31.319><c> alone</c><00:03:32.200><c> web</c>

00:03:32.429 --> 00:03:32.439 align:start position:0%
early internet can't do alone web
 

00:03:32.439 --> 00:03:34.229 align:start position:0%
early internet can't do alone web
servers<00:03:32.840><c> allow</c><00:03:33.040><c> us</c><00:03:33.159><c> to</c><00:03:33.360><c> coordinate</c><00:03:33.799><c> on</c><00:03:34.120><c> and</c>

00:03:34.229 --> 00:03:34.239 align:start position:0%
servers allow us to coordinate on and
 

00:03:34.239 --> 00:03:36.190 align:start position:0%
servers allow us to coordinate on and
perform<00:03:34.680><c> computations</c><00:03:35.480><c> over</c><00:03:35.760><c> multiple</c>

00:03:36.190 --> 00:03:36.200 align:start position:0%
perform computations over multiple
 

00:03:36.200 --> 00:03:38.429 align:start position:0%
perform computations over multiple
people's<00:03:36.640><c> state</c><00:03:37.239><c> that</c><00:03:37.480><c> state</c><00:03:37.799><c> might</c><00:03:38.200><c> be</c>

00:03:38.429 --> 00:03:38.439 align:start position:0%
people's state that state might be
 

00:03:38.439 --> 00:03:40.350 align:start position:0%
people's state that state might be
private<00:03:38.799><c> to</c><00:03:39.000><c> some</c><00:03:39.360><c> particular</c><00:03:39.760><c> subset</c><00:03:40.239><c> it</c>

00:03:40.350 --> 00:03:40.360 align:start position:0%
private to some particular subset it
 

00:03:40.360 --> 00:03:42.470 align:start position:0%
private to some particular subset it
might<00:03:40.519><c> be</c><00:03:40.720><c> public</c><00:03:41.640><c> um</c><00:03:41.760><c> it</c><00:03:41.879><c> allows</c><00:03:42.159><c> us</c><00:03:42.280><c> to</c>

00:03:42.470 --> 00:03:42.480 align:start position:0%
might be public um it allows us to
 

00:03:42.480 --> 00:03:45.750 align:start position:0%
might be public um it allows us to
decide<00:03:43.280><c> which</c><00:03:43.799><c> state</c><00:03:44.200><c> is</c><00:03:44.400><c> canonical</c><00:03:45.319><c> and</c><00:03:45.519><c> web</c>

00:03:45.750 --> 00:03:45.760 align:start position:0%
decide which state is canonical and web
 

00:03:45.760 --> 00:03:47.470 align:start position:0%
decide which state is canonical and web
servers<00:03:46.040><c> also</c><00:03:46.280><c> provide</c><00:03:46.680><c> strong</c><00:03:46.879><c> uptime</c><00:03:47.280><c> and</c>

00:03:47.470 --> 00:03:47.480 align:start position:0%
servers also provide strong uptime and
 

00:03:47.480 --> 00:03:48.949 align:start position:0%
servers also provide strong uptime and
liveness<00:03:47.920><c> guarantees</c><00:03:48.599><c> that</c><00:03:48.720><c> don't</c>

00:03:48.949 --> 00:03:48.959 align:start position:0%
liveness guarantees that don't
 

00:03:48.959 --> 00:03:51.990 align:start position:0%
liveness guarantees that don't
necessarily<00:03:49.519><c> exist</c><00:03:49.840><c> in</c><00:03:49.959><c> a</c><00:03:50.080><c> peer-to-peer</c>

00:03:51.990 --> 00:03:52.000 align:start position:0%
necessarily exist in a peer-to-peer
 

00:03:52.000 --> 00:03:56.949 align:start position:0%
necessarily exist in a peer-to-peer
Network<00:03:53.319><c> so</c><00:03:54.599><c> um</c><00:03:55.599><c> this</c><00:03:55.799><c> has</c><00:03:55.959><c> taken</c><00:03:56.239><c> us</c><00:03:56.560><c> pretty</c>

00:03:56.949 --> 00:03:56.959 align:start position:0%
Network so um this has taken us pretty
 

00:03:56.959 --> 00:03:59.789 align:start position:0%
Network so um this has taken us pretty
far<00:03:57.920><c> but</c><00:03:58.840><c> uh</c><00:03:59.040><c> you</c><00:03:59.159><c> know</c><00:03:59.280><c> one</c><00:03:59.480><c> question</c>

00:03:59.789 --> 00:03:59.799 align:start position:0%
far but uh you know one question
 

00:03:59.799 --> 00:04:01.869 align:start position:0%
far but uh you know one question
question<00:04:00.079><c> is</c><00:04:00.439><c> is</c><00:04:00.680><c> can</c><00:04:00.840><c> we</c><00:04:01.000><c> do</c><00:04:01.159><c> better</c><00:04:01.519><c> right</c>

00:04:01.869 --> 00:04:01.879 align:start position:0%
question is is can we do better right
 

00:04:01.879 --> 00:04:03.550 align:start position:0%
question is is can we do better right
there's<00:04:02.120><c> been</c><00:04:02.239><c> a</c><00:04:02.360><c> lot</c><00:04:02.439><c> of</c><00:04:02.680><c> problems</c><00:04:03.120><c> that</c><00:04:03.319><c> have</c>

00:04:03.550 --> 00:04:03.560 align:start position:0%
there's been a lot of problems that have
 

00:04:03.560 --> 00:04:05.309 align:start position:0%
there's been a lot of problems that have
Arisen<00:04:04.040><c> as</c><00:04:04.120><c> a</c><00:04:04.319><c> result</c><00:04:04.760><c> of</c><00:04:04.879><c> this</c><00:04:05.040><c> being</c><00:04:05.239><c> the</c>

00:04:05.309 --> 00:04:05.319 align:start position:0%
Arisen as a result of this being the
 

00:04:05.319 --> 00:04:07.030 align:start position:0%
Arisen as a result of this being the
fundamental<00:04:05.799><c> architecture</c><00:04:06.560><c> and</c><00:04:06.680><c> in</c><00:04:06.799><c> fact</c>

00:04:07.030 --> 00:04:07.040 align:start position:0%
fundamental architecture and in fact
 

00:04:07.040 --> 00:04:09.110 align:start position:0%
fundamental architecture and in fact
these<00:04:07.280><c> problems</c><00:04:07.760><c> are</c><00:04:08.200><c> a</c><00:04:08.360><c> big</c><00:04:08.560><c> part</c><00:04:08.760><c> of</c><00:04:08.920><c> why</c>

00:04:09.110 --> 00:04:09.120 align:start position:0%
these problems are a big part of why
 

00:04:09.120 --> 00:04:11.470 align:start position:0%
these problems are a big part of why
many<00:04:09.319><c> of</c><00:04:09.480><c> us</c><00:04:09.680><c> today</c><00:04:09.959><c> are</c><00:04:10.159><c> in</c><00:04:10.360><c> this</c><00:04:10.560><c> room</c><00:04:11.400><c> you</c>

00:04:11.470 --> 00:04:11.480 align:start position:0%
many of us today are in this room you
 

00:04:11.480 --> 00:04:12.869 align:start position:0%
many of us today are in this room you
can<00:04:11.640><c> feel</c><00:04:11.799><c> free</c><00:04:12.000><c> to</c><00:04:12.079><c> choose</c><00:04:12.319><c> the</c><00:04:12.439><c> problems</c><00:04:12.720><c> you</c>

00:04:12.869 --> 00:04:12.879 align:start position:0%
can feel free to choose the problems you
 

00:04:12.879 --> 00:04:15.110 align:start position:0%
can feel free to choose the problems you
care<00:04:13.079><c> about</c><00:04:13.519><c> there's</c><00:04:13.720><c> all</c><00:04:13.879><c> sorts</c><00:04:14.079><c> of</c><00:04:14.280><c> things</c>

00:04:15.110 --> 00:04:15.120 align:start position:0%
care about there's all sorts of things
 

00:04:15.120 --> 00:04:17.550 align:start position:0%
care about there's all sorts of things
um<00:04:15.680><c> and</c><00:04:16.479><c> when</c><00:04:16.639><c> we</c><00:04:16.880><c> return</c><00:04:17.160><c> back</c><00:04:17.280><c> to</c><00:04:17.400><c> the</c>

00:04:17.550 --> 00:04:17.560 align:start position:0%
um and when we return back to the
 

00:04:17.560 --> 00:04:19.150 align:start position:0%
um and when we return back to the
question<00:04:17.840><c> then</c><00:04:18.000><c> of</c><00:04:18.160><c> how</c><00:04:18.280><c> do</c><00:04:18.440><c> we</c><00:04:18.639><c> compute</c>

00:04:19.150 --> 00:04:19.160 align:start position:0%
question then of how do we compute
 

00:04:19.160 --> 00:04:22.150 align:start position:0%
question then of how do we compute
together<00:04:20.160><c> we</c><00:04:20.320><c> have</c><00:04:20.440><c> to</c><00:04:20.639><c> ask</c><00:04:21.280><c> is</c><00:04:21.519><c> there</c><00:04:22.000><c> a</c>

00:04:22.150 --> 00:04:22.160 align:start position:0%
together we have to ask is there a
 

00:04:22.160 --> 00:04:24.189 align:start position:0%
together we have to ask is there a
better<00:04:22.440><c> way</c><00:04:22.639><c> that</c><00:04:22.759><c> we</c><00:04:22.880><c> could</c><00:04:23.040><c> go</c><00:04:23.240><c> about</c><00:04:23.560><c> this</c>

00:04:24.189 --> 00:04:24.199 align:start position:0%
better way that we could go about this
 

00:04:24.199 --> 00:04:26.990 align:start position:0%
better way that we could go about this
right<00:04:24.919><c> and</c><00:04:25.080><c> one</c><00:04:25.199><c> of</c><00:04:25.320><c> the</c><00:04:25.560><c> really</c><00:04:26.000><c> interesting</c>

00:04:26.990 --> 00:04:27.000 align:start position:0%
right and one of the really interesting
 

00:04:27.000 --> 00:04:29.749 align:start position:0%
right and one of the really interesting
discoveries<00:04:27.600><c> of</c><00:04:27.759><c> the</c><00:04:27.960><c> last</c><00:04:28.400><c> decade</c><00:04:29.400><c> is</c><00:04:29.560><c> that</c>

00:04:29.749 --> 00:04:29.759 align:start position:0%
discoveries of the last decade is that
 

00:04:29.759 --> 00:04:32.029 align:start position:0%
discoveries of the last decade is that
that<00:04:29.960><c> blockchains</c><00:04:30.880><c> cryptoeconomics</c><00:04:31.880><c> and</c>

00:04:32.029 --> 00:04:32.039 align:start position:0%
that blockchains cryptoeconomics and
 

00:04:32.039 --> 00:04:33.909 align:start position:0%
that blockchains cryptoeconomics and
ethereum<00:04:32.479><c> have</c><00:04:32.600><c> given</c><00:04:32.840><c> us</c><00:04:33.120><c> new</c><00:04:33.400><c> answers</c><00:04:33.720><c> to</c>

00:04:33.909 --> 00:04:33.919 align:start position:0%
ethereum have given us new answers to
 

00:04:33.919 --> 00:04:36.150 align:start position:0%
ethereum have given us new answers to
this<00:04:34.080><c> question</c><00:04:34.600><c> for</c><00:04:34.759><c> the</c><00:04:34.960><c> first</c><00:04:35.280><c> time</c><00:04:35.560><c> in</c>

00:04:36.150 --> 00:04:36.160 align:start position:0%
this question for the first time in
 

00:04:36.160 --> 00:04:39.830 align:start position:0%
this question for the first time in
decades<00:04:37.160><c> right</c><00:04:37.320><c> so</c><00:04:37.880><c> now</c><00:04:38.520><c> ethereum</c><00:04:39.400><c> allows</c><00:04:39.720><c> us</c>

00:04:39.830 --> 00:04:39.840 align:start position:0%
decades right so now ethereum allows us
 

00:04:39.840 --> 00:04:42.390 align:start position:0%
decades right so now ethereum allows us
to<00:04:40.039><c> run</c><00:04:40.320><c> a</c><00:04:40.479><c> single</c><00:04:40.840><c> computer</c><00:04:41.360><c> collectively</c><00:04:42.320><c> in</c>

00:04:42.390 --> 00:04:42.400 align:start position:0%
to run a single computer collectively in
 

00:04:42.400 --> 00:04:44.390 align:start position:0%
to run a single computer collectively in
a<00:04:42.600><c> way</c><00:04:42.759><c> that's</c><00:04:42.919><c> sort</c><00:04:43.080><c> of</c><00:04:43.320><c> very</c><00:04:43.639><c> different</c><00:04:44.280><c> than</c>

00:04:44.390 --> 00:04:44.400 align:start position:0%
a way that's sort of very different than
 

00:04:44.400 --> 00:04:46.430 align:start position:0%
a way that's sort of very different than
the<00:04:44.520><c> traditional</c><00:04:45.000><c> model</c><00:04:45.360><c> where</c><00:04:45.720><c> we</c><00:04:45.919><c> promote</c>

00:04:46.430 --> 00:04:46.440 align:start position:0%
the traditional model where we promote
 

00:04:46.440 --> 00:04:48.029 align:start position:0%
the traditional model where we promote
that<00:04:46.600><c> one</c><00:04:46.759><c> single</c><00:04:47.000><c> node</c><00:04:47.280><c> Dave</c><00:04:47.520><c> to</c><00:04:47.600><c> be</c><00:04:47.720><c> a</c><00:04:47.840><c> very</c>

00:04:48.029 --> 00:04:48.039 align:start position:0%
that one single node Dave to be a very
 

00:04:48.039 --> 00:04:49.510 align:start position:0%
that one single node Dave to be a very
important<00:04:48.560><c> node</c><00:04:48.840><c> that</c><00:04:48.919><c> we</c><00:04:49.039><c> give</c><00:04:49.199><c> all</c><00:04:49.280><c> of</c><00:04:49.360><c> our</c>

00:04:49.510 --> 00:04:49.520 align:start position:0%
important node that we give all of our
 

00:04:49.520 --> 00:04:51.270 align:start position:0%
important node that we give all of our
data

00:04:51.270 --> 00:04:51.280 align:start position:0%
data
 

00:04:51.280 --> 00:04:54.270 align:start position:0%
data
to<00:04:52.280><c> so</c><00:04:52.600><c> ethereum</c><00:04:53.160><c> has</c><00:04:53.560><c> given</c><00:04:53.880><c> us</c>

00:04:54.270 --> 00:04:54.280 align:start position:0%
to so ethereum has given us
 

00:04:54.280 --> 00:04:55.710 align:start position:0%
to so ethereum has given us
extraordinary<00:04:54.880><c> things</c><00:04:55.240><c> you</c><00:04:55.320><c> know</c><00:04:55.440><c> many</c><00:04:55.600><c> of</c>

00:04:55.710 --> 00:04:55.720 align:start position:0%
extraordinary things you know many of
 

00:04:55.720 --> 00:04:57.710 align:start position:0%
extraordinary things you know many of
which<00:04:55.880><c> we</c><00:04:55.960><c> saw</c><00:04:56.160><c> this</c><00:04:56.280><c> morning</c><00:04:57.240><c> because</c><00:04:57.560><c> we</c>

00:04:57.710 --> 00:04:57.720 align:start position:0%
which we saw this morning because we
 

00:04:57.720 --> 00:04:59.670 align:start position:0%
which we saw this morning because we
have<00:04:57.840><c> the</c><00:04:58.000><c> ability</c><00:04:58.400><c> to</c><00:04:58.639><c> have</c><00:04:58.840><c> decentralized</c>

00:04:59.670 --> 00:04:59.680 align:start position:0%
have the ability to have decentralized
 

00:04:59.680 --> 00:05:02.469 align:start position:0%
have the ability to have decentralized
consus<00:04:59.960><c> over</c><00:05:00.120><c> global</c><00:05:00.440><c> State</c><00:05:01.199><c> we</c><00:05:01.400><c> have</c><00:05:01.960><c> neutral</c>

00:05:02.469 --> 00:05:02.479 align:start position:0%
consus over global State we have neutral
 

00:05:02.479 --> 00:05:04.390 align:start position:0%
consus over global State we have neutral
and<00:05:02.600><c> autonomous</c><00:05:03.160><c> marketplaces</c><00:05:03.919><c> Financial</c>

00:05:04.390 --> 00:05:04.400 align:start position:0%
and autonomous marketplaces Financial
 

00:05:04.400 --> 00:05:06.110 align:start position:0%
and autonomous marketplaces Financial
derivatives<00:05:05.120><c> prediction</c><00:05:05.520><c> markets</c><00:05:05.880><c> we</c><00:05:05.960><c> have</c>

00:05:06.110 --> 00:05:06.120 align:start position:0%
derivatives prediction markets we have
 

00:05:06.120 --> 00:05:07.510 align:start position:0%
derivatives prediction markets we have
payment<00:05:06.400><c> systems</c><00:05:06.720><c> that</c><00:05:06.840><c> no</c><00:05:07.000><c> single</c><00:05:07.240><c> Authority</c>

00:05:07.510 --> 00:05:07.520 align:start position:0%
payment systems that no single Authority
 

00:05:07.520 --> 00:05:09.430 align:start position:0%
payment systems that no single Authority
controls<00:05:08.280><c> we</c><00:05:08.400><c> have</c><00:05:08.520><c> permissionless</c><00:05:09.039><c> identity</c>

00:05:09.430 --> 00:05:09.440 align:start position:0%
controls we have permissionless identity
 

00:05:09.440 --> 00:05:10.590 align:start position:0%
controls we have permissionless identity
Registries<00:05:09.919><c> spinning</c><00:05:10.240><c> up</c><00:05:10.400><c> we</c><00:05:10.479><c> have</c>

00:05:10.590 --> 00:05:10.600 align:start position:0%
Registries spinning up we have
 

00:05:10.600 --> 00:05:12.550 align:start position:0%
Registries spinning up we have
interoperable<00:05:11.240><c> and</c><00:05:11.400><c> composable</c>

00:05:12.550 --> 00:05:12.560 align:start position:0%
interoperable and composable
 

00:05:12.560 --> 00:05:16.230 align:start position:0%
interoperable and composable
games<00:05:13.560><c> um</c><00:05:14.000><c> but</c><00:05:14.320><c> we</c><00:05:14.600><c> also</c><00:05:15.000><c> can't</c><00:05:15.240><c> do</c><00:05:15.759><c> everything</c>

00:05:16.230 --> 00:05:16.240 align:start position:0%
games um but we also can't do everything
 

00:05:16.240 --> 00:05:18.270 align:start position:0%
games um but we also can't do everything
that<00:05:16.360><c> we</c><00:05:16.479><c> want</c><00:05:16.800><c> yet</c><00:05:17.000><c> in</c><00:05:17.160><c> fact</c><00:05:17.680><c> nearly</c>

00:05:18.270 --> 00:05:18.280 align:start position:0%
that we want yet in fact nearly
 

00:05:18.280 --> 00:05:20.309 align:start position:0%
that we want yet in fact nearly
everything<00:05:19.080><c> that</c><00:05:19.280><c> I</c><00:05:19.400><c> showed</c><00:05:19.720><c> on</c><00:05:19.840><c> the</c><00:05:20.000><c> previous</c>

00:05:20.309 --> 00:05:20.319 align:start position:0%
everything that I showed on the previous
 

00:05:20.319 --> 00:05:22.870 align:start position:0%
everything that I showed on the previous
slide<00:05:20.960><c> is</c><00:05:21.240><c> still</c><00:05:21.720><c> beyond</c><00:05:22.160><c> the</c><00:05:22.360><c> capabilities</c>

00:05:22.870 --> 00:05:22.880 align:start position:0%
slide is still beyond the capabilities
 

00:05:22.880 --> 00:05:25.230 align:start position:0%
slide is still beyond the capabilities
of<00:05:23.039><c> ethereum</c><00:05:23.479><c> alone</c><00:05:24.240><c> and</c><00:05:24.479><c> not</c><00:05:24.759><c> just</c><00:05:25.000><c> as</c><00:05:25.120><c> a</c>

00:05:25.230 --> 00:05:25.240 align:start position:0%
of ethereum alone and not just as a
 

00:05:25.240 --> 00:05:27.350 align:start position:0%
of ethereum alone and not just as a
result<00:05:25.520><c> of</c><00:05:25.720><c> performance</c><00:05:26.520><c> but</c><00:05:26.680><c> as</c><00:05:26.800><c> a</c><00:05:26.919><c> result</c><00:05:27.160><c> of</c>

00:05:27.350 --> 00:05:27.360 align:start position:0%
result of performance but as a result of
 

00:05:27.360 --> 00:05:29.189 align:start position:0%
result of performance but as a result of
fundamental<00:05:27.960><c> architecture</c><00:05:28.520><c> and</c><00:05:28.680><c> capability</c>

00:05:29.189 --> 00:05:29.199 align:start position:0%
fundamental architecture and capability
 

00:05:29.199 --> 00:05:31.790 align:start position:0%
fundamental architecture and capability
limitation

00:05:31.790 --> 00:05:31.800 align:start position:0%
 
 

00:05:31.800 --> 00:05:33.830 align:start position:0%
 
so<00:05:32.080><c> enter</c><00:05:32.400><c> programmable</c><00:05:32.880><c> cryptography</c>

00:05:33.830 --> 00:05:33.840 align:start position:0%
so enter programmable cryptography
 

00:05:33.840 --> 00:05:35.430 align:start position:0%
so enter programmable cryptography
programmable<00:05:34.440><c> cryptography</c><00:05:35.199><c> is</c><00:05:35.280><c> a</c>

00:05:35.430 --> 00:05:35.440 align:start position:0%
programmable cryptography is a
 

00:05:35.440 --> 00:05:37.270 align:start position:0%
programmable cryptography is a
technology<00:05:35.960><c> that</c><00:05:36.080><c> can</c><00:05:36.240><c> give</c><00:05:36.360><c> us</c><00:05:36.759><c> many</c><00:05:37.000><c> more</c>

00:05:37.270 --> 00:05:37.280 align:start position:0%
technology that can give us many more
 

00:05:37.280 --> 00:05:39.430 align:start position:0%
technology that can give us many more
answers<00:05:37.720><c> to</c><00:05:37.840><c> the</c><00:05:38.000><c> question</c><00:05:38.280><c> of</c><00:05:38.759><c> how</c><00:05:39.000><c> do</c><00:05:39.199><c> we</c>

00:05:39.430 --> 00:05:39.440 align:start position:0%
answers to the question of how do we
 

00:05:39.440 --> 00:05:41.830 align:start position:0%
answers to the question of how do we
compute<00:05:40.160><c> together</c><00:05:41.160><c> and</c><00:05:41.280><c> it</c><00:05:41.400><c> can</c><00:05:41.560><c> give</c><00:05:41.680><c> us</c>

00:05:41.830 --> 00:05:41.840 align:start position:0%
compute together and it can give us
 

00:05:41.840 --> 00:05:44.830 align:start position:0%
compute together and it can give us
these<00:05:42.000><c> answers</c><00:05:42.520><c> both</c><00:05:43.080><c> independently</c><00:05:44.080><c> and</c><00:05:44.360><c> in</c>

00:05:44.830 --> 00:05:44.840 align:start position:0%
these answers both independently and in
 

00:05:44.840 --> 00:05:46.790 align:start position:0%
these answers both independently and in
combination<00:05:45.840><c> with</c>

00:05:46.790 --> 00:05:46.800 align:start position:0%
combination with
 

00:05:46.800 --> 00:05:49.270 align:start position:0%
combination with
ethereum<00:05:47.800><c> so</c><00:05:48.039><c> what</c><00:05:48.160><c> is</c><00:05:48.360><c> programmable</c>

00:05:49.270 --> 00:05:49.280 align:start position:0%
ethereum so what is programmable
 

00:05:49.280 --> 00:05:51.150 align:start position:0%
ethereum so what is programmable
cryptography<00:05:50.280><c> for</c><00:05:50.479><c> those</c><00:05:50.639><c> of</c><00:05:50.720><c> you</c><00:05:50.840><c> who</c><00:05:50.960><c> aren't</c>

00:05:51.150 --> 00:05:51.160 align:start position:0%
cryptography for those of you who aren't
 

00:05:51.160 --> 00:05:52.990 align:start position:0%
cryptography for those of you who aren't
familiar<00:05:51.600><c> with</c><00:05:51.680><c> the</c><00:05:51.800><c> term</c><00:05:52.440><c> programmable</c>

00:05:52.990 --> 00:05:53.000 align:start position:0%
familiar with the term programmable
 

00:05:53.000 --> 00:05:54.909 align:start position:0%
familiar with the term programmable
cryptography<00:05:53.840><c> refers</c><00:05:54.160><c> to</c><00:05:54.319><c> a</c><00:05:54.520><c> second</c>

00:05:54.909 --> 00:05:54.919 align:start position:0%
cryptography refers to a second
 

00:05:54.919 --> 00:05:56.790 align:start position:0%
cryptography refers to a second
generation<00:05:55.400><c> of</c><00:05:55.560><c> cryptographic</c><00:05:56.120><c> Primitives</c>

00:05:56.790 --> 00:05:56.800 align:start position:0%
generation of cryptographic Primitives
 

00:05:56.800 --> 00:05:58.309 align:start position:0%
generation of cryptographic Primitives
that<00:05:56.880><c> have</c><00:05:57.039><c> started</c><00:05:57.319><c> to</c><00:05:57.479><c> emerge</c><00:05:57.840><c> and</c><00:05:58.000><c> become</c>

00:05:58.309 --> 00:05:58.319 align:start position:0%
that have started to emerge and become
 

00:05:58.319 --> 00:06:00.990 align:start position:0%
that have started to emerge and become
viable<00:05:58.759><c> in</c><00:05:58.880><c> the</c><00:05:59.039><c> past</c><00:05:59.199><c> two</c><00:05:59.360><c> to</c><00:05:59.680><c> 5</c><00:05:59.919><c> years</c><00:06:00.800><c> these</c>

00:06:00.990 --> 00:06:01.000 align:start position:0%
viable in the past two to 5 years these
 

00:06:01.000 --> 00:06:02.550 align:start position:0%
viable in the past two to 5 years these
include<00:06:01.400><c> Technologies</c><00:06:02.000><c> like</c><00:06:02.160><c> general</c>

00:06:02.550 --> 00:06:02.560 align:start position:0%
include Technologies like general
 

00:06:02.560 --> 00:06:04.189 align:start position:0%
include Technologies like general
purpose<00:06:02.840><c> zero</c><00:06:03.120><c> knowledge</c><00:06:03.440><c> proofs</c>

00:06:04.189 --> 00:06:04.199 align:start position:0%
purpose zero knowledge proofs
 

00:06:04.199 --> 00:06:06.029 align:start position:0%
purpose zero knowledge proofs
multi-party<00:06:04.880><c> computation</c><00:06:05.720><c> fully</c>

00:06:06.029 --> 00:06:06.039 align:start position:0%
multi-party computation fully
 

00:06:06.039 --> 00:06:07.710 align:start position:0%
multi-party computation fully
homomorphic<00:06:06.560><c> encryption</c><00:06:07.319><c> witness</c>

00:06:07.710 --> 00:06:07.720 align:start position:0%
homomorphic encryption witness
 

00:06:07.720 --> 00:06:09.230 align:start position:0%
homomorphic encryption witness
encryption<00:06:08.240><c> functional</c><00:06:08.639><c> encryption</c>

00:06:09.230 --> 00:06:09.240 align:start position:0%
encryption functional encryption
 

00:06:09.240 --> 00:06:12.110 align:start position:0%
encryption functional encryption
obfuscation<00:06:09.880><c> and</c><00:06:10.440><c> more</c><00:06:11.440><c> these</c><00:06:11.639><c> Advanced</c>

00:06:12.110 --> 00:06:12.120 align:start position:0%
obfuscation and more these Advanced
 

00:06:12.120 --> 00:06:14.830 align:start position:0%
obfuscation and more these Advanced
Technologies<00:06:13.039><c> are</c><00:06:13.199><c> the</c><00:06:13.280><c> ones</c><00:06:13.520><c> in</c><00:06:13.720><c> bold</c><00:06:14.199><c> here</c>

00:06:14.830 --> 00:06:14.840 align:start position:0%
Technologies are the ones in bold here
 

00:06:14.840 --> 00:06:16.270 align:start position:0%
Technologies are the ones in bold here
and<00:06:14.919><c> one</c><00:06:15.039><c> of</c><00:06:15.160><c> the</c><00:06:15.240><c> key</c><00:06:15.400><c> features</c><00:06:15.840><c> is</c><00:06:16.000><c> that</c><00:06:16.160><c> they</c>

00:06:16.270 --> 00:06:16.280 align:start position:0%
and one of the key features is that they
 

00:06:16.280 --> 00:06:18.230 align:start position:0%
and one of the key features is that they
share<00:06:16.599><c> sort</c><00:06:16.759><c> of</c><00:06:16.880><c> an</c><00:06:17.039><c> underlying</c><00:06:17.599><c> theoretical</c>

00:06:18.230 --> 00:06:18.240 align:start position:0%
share sort of an underlying theoretical
 

00:06:18.240 --> 00:06:21.230 align:start position:0%
share sort of an underlying theoretical
common<00:06:18.680><c> backbone</c><00:06:19.680><c> and</c><00:06:19.800><c> that</c><00:06:19.960><c> they</c><00:06:20.240><c> generalize</c>

00:06:21.230 --> 00:06:21.240 align:start position:0%
common backbone and that they generalize
 

00:06:21.240 --> 00:06:23.790 align:start position:0%
common backbone and that they generalize
familiar<00:06:22.080><c> generation</c><00:06:22.720><c> one</c><00:06:23.120><c> cryptographic</c>

00:06:23.790 --> 00:06:23.800 align:start position:0%
familiar generation one cryptographic
 

00:06:23.800 --> 00:06:25.710 align:start position:0%
familiar generation one cryptographic
Technologies<00:06:24.720><c> like</c><00:06:24.919><c> signatures</c><00:06:25.479><c> and</c>

00:06:25.710 --> 00:06:25.720 align:start position:0%
Technologies like signatures and
 

00:06:25.720 --> 00:06:27.790 align:start position:0%
Technologies like signatures and
encryption<00:06:26.720><c> so</c><00:06:26.880><c> you</c><00:06:26.960><c> can</c><00:06:27.080><c> sort</c><00:06:27.240><c> of</c><00:06:27.360><c> see</c><00:06:27.599><c> a</c><00:06:27.680><c> lot</c>

00:06:27.790 --> 00:06:27.800 align:start position:0%
encryption so you can sort of see a lot
 

00:06:27.800 --> 00:06:29.589 align:start position:0%
encryption so you can sort of see a lot
of<00:06:27.919><c> these</c><00:06:28.080><c> Technologies</c><00:06:28.960><c> in</c><00:06:29.039><c> the</c><00:06:29.120><c> shape</c><00:06:29.319><c> of</c><00:06:29.440><c> a</c>

00:06:29.589 --> 00:06:29.599 align:start position:0%
of these Technologies in the shape of a
 

00:06:29.599 --> 00:06:32.189 align:start position:0%
of these Technologies in the shape of a
detect<00:06:30.440><c> where</c><00:06:30.919><c> protocols</c><00:06:31.479><c> higher</c><00:06:31.759><c> up</c><00:06:31.919><c> on</c><00:06:32.039><c> the</c>

00:06:32.189 --> 00:06:32.199 align:start position:0%
detect where protocols higher up on the
 

00:06:32.199 --> 00:06:34.070 align:start position:0%
detect where protocols higher up on the
stack<00:06:32.639><c> generalize</c><00:06:33.280><c> things</c><00:06:33.520><c> lower</c><00:06:33.800><c> down</c><00:06:33.960><c> on</c>

00:06:34.070 --> 00:06:34.080 align:start position:0%
stack generalize things lower down on
 

00:06:34.080 --> 00:06:35.670 align:start position:0%
stack generalize things lower down on
the

00:06:35.670 --> 00:06:35.680 align:start position:0%
the
 

00:06:35.680 --> 00:06:38.350 align:start position:0%
the
stack<00:06:36.680><c> so</c><00:06:36.919><c> programmable</c><00:06:37.440><c> cryptography</c><00:06:38.039><c> moves</c>

00:06:38.350 --> 00:06:38.360 align:start position:0%
stack so programmable cryptography moves
 

00:06:38.360 --> 00:06:41.350 align:start position:0%
stack so programmable cryptography moves
us<00:06:38.560><c> from</c><00:06:38.720><c> a</c><00:06:38.880><c> world</c><00:06:39.599><c> where</c><00:06:40.199><c> we</c><00:06:40.440><c> have</c><00:06:40.759><c> proofs</c><00:06:41.120><c> for</c>

00:06:41.350 --> 00:06:41.360 align:start position:0%
us from a world where we have proofs for
 

00:06:41.360 --> 00:06:42.870 align:start position:0%
us from a world where we have proofs for
specific<00:06:41.800><c> functions</c><00:06:42.280><c> you</c><00:06:42.360><c> know</c><00:06:42.479><c> in</c><00:06:42.599><c> the</c><00:06:42.680><c> world</c>

00:06:42.870 --> 00:06:42.880 align:start position:0%
specific functions you know in the world
 

00:06:42.880 --> 00:06:44.510 align:start position:0%
specific functions you know in the world
of<00:06:43.080><c> generation</c><00:06:43.599><c> one</c><00:06:43.800><c> or</c><00:06:43.960><c> special</c><00:06:44.240><c> purpose</c>

00:06:44.510 --> 00:06:44.520 align:start position:0%
of generation one or special purpose
 

00:06:44.520 --> 00:06:46.670 align:start position:0%
of generation one or special purpose
cryptography<00:06:45.400><c> to</c><00:06:45.639><c> being</c><00:06:45.800><c> able</c><00:06:46.000><c> to</c><00:06:46.240><c> perform</c>

00:06:46.670 --> 00:06:46.680 align:start position:0%
cryptography to being able to perform
 

00:06:46.680 --> 00:06:48.510 align:start position:0%
cryptography to being able to perform
proofs<00:06:47.280><c> of</c><00:06:47.599><c> any</c><00:06:47.840><c> function</c><00:06:48.120><c> or</c><00:06:48.280><c> any</c>

00:06:48.510 --> 00:06:48.520 align:start position:0%
proofs of any function or any
 

00:06:48.520 --> 00:06:50.670 align:start position:0%
proofs of any function or any
computation<00:06:49.520><c> we</c><00:06:49.680><c> can</c><00:06:49.840><c> go</c><00:06:50.000><c> from</c><00:06:50.160><c> being</c><00:06:50.360><c> able</c><00:06:50.520><c> to</c>

00:06:50.670 --> 00:06:50.680 align:start position:0%
computation we can go from being able to
 

00:06:50.680 --> 00:06:52.830 align:start position:0%
computation we can go from being able to
verify<00:06:51.240><c> specific</c><00:06:51.759><c> claims</c><00:06:52.240><c> to</c><00:06:52.360><c> being</c><00:06:52.560><c> able</c><00:06:52.720><c> to</c>

00:06:52.830 --> 00:06:52.840 align:start position:0%
verify specific claims to being able to
 

00:06:52.840 --> 00:06:55.029 align:start position:0%
verify specific claims to being able to
verify<00:06:53.199><c> any</c><00:06:53.400><c> claim</c><00:06:54.120><c> and</c><00:06:54.240><c> in</c><00:06:54.360><c> general</c><00:06:54.639><c> we</c><00:06:54.759><c> move</c>

00:06:55.029 --> 00:06:55.039 align:start position:0%
verify any claim and in general we move
 

00:06:55.039 --> 00:06:56.710 align:start position:0%
verify any claim and in general we move
from<00:06:55.240><c> special</c><00:06:55.639><c> purpose</c><00:06:55.960><c> protocols</c><00:06:56.479><c> to</c>

00:06:56.710 --> 00:06:56.720 align:start position:0%
from special purpose protocols to
 

00:06:56.720 --> 00:06:59.909 align:start position:0%
from special purpose protocols to
general<00:06:57.160><c> purpose</c><00:06:57.840><c> cryptography</c><00:06:58.680><c> compilers</c>

00:06:59.909 --> 00:06:59.919 align:start position:0%
general purpose cryptography compilers
 

00:06:59.919 --> 00:07:01.950 align:start position:0%
general purpose cryptography compilers
to<00:07:00.080><c> make</c><00:07:00.199><c> a</c><00:07:00.319><c> hardware</c><00:07:00.720><c> analogy</c><00:07:01.479><c> this</c><00:07:01.599><c> is</c><00:07:01.759><c> sort</c>

00:07:01.950 --> 00:07:01.960 align:start position:0%
to make a hardware analogy this is sort
 

00:07:01.960 --> 00:07:03.670 align:start position:0%
to make a hardware analogy this is sort
of<00:07:02.160><c> like</c><00:07:02.319><c> the</c><00:07:02.479><c> transition</c><00:07:03.080><c> from</c><00:07:03.319><c> special</c>

00:07:03.670 --> 00:07:03.680 align:start position:0%
of like the transition from special
 

00:07:03.680 --> 00:07:05.629 align:start position:0%
of like the transition from special
purpose<00:07:04.000><c> Hardware</c><00:07:04.599><c> like</c><00:07:04.720><c> an</c><00:07:04.879><c> alarm</c><00:07:05.240><c> clock</c><00:07:05.520><c> or</c>

00:07:05.629 --> 00:07:05.639 align:start position:0%
purpose Hardware like an alarm clock or
 

00:07:05.639 --> 00:07:07.909 align:start position:0%
purpose Hardware like an alarm clock or
a<00:07:05.720><c> four</c><00:07:06.000><c> function</c><00:07:06.360><c> calculator</c><00:07:07.160><c> to</c><00:07:07.360><c> something</c>

00:07:07.909 --> 00:07:07.919 align:start position:0%
a four function calculator to something
 

00:07:07.919 --> 00:07:11.909 align:start position:0%
a four function calculator to something
like<00:07:08.240><c> a</c><00:07:08.440><c> CPU</c><00:07:09.280><c> which</c><00:07:09.400><c> is</c><00:07:09.560><c> generally</c>

00:07:11.909 --> 00:07:11.919 align:start position:0%
like a CPU which is generally
 

00:07:11.919 --> 00:07:13.950 align:start position:0%
like a CPU which is generally
programmable<00:07:12.919><c> what's</c><00:07:13.160><c> changed</c><00:07:13.440><c> in</c><00:07:13.560><c> the</c><00:07:13.720><c> last</c>

00:07:13.950 --> 00:07:13.960 align:start position:0%
programmable what's changed in the last
 

00:07:13.960 --> 00:07:16.070 align:start position:0%
programmable what's changed in the last
couple<00:07:14.160><c> of</c><00:07:14.360><c> years</c><00:07:14.840><c> to</c><00:07:15.039><c> make</c><00:07:15.319><c> this</c><00:07:15.599><c> an</c><00:07:15.720><c> area</c><00:07:15.960><c> of</c>

00:07:16.070 --> 00:07:16.080 align:start position:0%
couple of years to make this an area of
 

00:07:16.080 --> 00:07:18.350 align:start position:0%
couple of years to make this an area of
technology<00:07:16.599><c> to</c><00:07:16.800><c> focus</c><00:07:17.080><c> on</c><00:07:17.360><c> now</c><00:07:18.000><c> well</c><00:07:18.160><c> first</c>

00:07:18.350 --> 00:07:18.360 align:start position:0%
technology to focus on now well first
 

00:07:18.360 --> 00:07:19.790 align:start position:0%
technology to focus on now well first
off<00:07:18.520><c> there's</c><00:07:18.759><c> been</c><00:07:19.120><c> significant</c>

00:07:19.790 --> 00:07:19.800 align:start position:0%
off there's been significant
 

00:07:19.800 --> 00:07:21.710 align:start position:0%
off there's been significant
technological<00:07:20.560><c> advancements</c><00:07:21.240><c> over</c><00:07:21.440><c> the</c><00:07:21.560><c> past</c>

00:07:21.710 --> 00:07:21.720 align:start position:0%
technological advancements over the past
 

00:07:21.720 --> 00:07:23.350 align:start position:0%
technological advancements over the past
two<00:07:21.879><c> to</c><00:07:22.039><c> five</c><00:07:22.280><c> years</c><00:07:22.879><c> that</c><00:07:23.000><c> have</c><00:07:23.120><c> made</c>

00:07:23.350 --> 00:07:23.360 align:start position:0%
two to five years that have made
 

00:07:23.360 --> 00:07:24.909 align:start position:0%
two to five years that have made
programmable<00:07:23.960><c> cryptography</c><00:07:24.479><c> more</c>

00:07:24.909 --> 00:07:24.919 align:start position:0%
programmable cryptography more
 

00:07:24.919 --> 00:07:27.749 align:start position:0%
programmable cryptography more
approachable<00:07:25.919><c> on</c><00:07:26.039><c> the</c><00:07:26.199><c> theoretical</c><00:07:26.759><c> level</c>

00:07:27.749 --> 00:07:27.759 align:start position:0%
approachable on the theoretical level
 

00:07:27.759 --> 00:07:29.790 align:start position:0%
approachable on the theoretical level
every<00:07:28.120><c> item</c><00:07:28.520><c> on</c><00:07:28.680><c> that</c><00:07:28.840><c> previous</c><00:07:29.160><c> texure</c><00:07:29.680><c> that</c>

00:07:29.790 --> 00:07:29.800 align:start position:0%
every item on that previous texure that
 

00:07:29.800 --> 00:07:32.350 align:start position:0%
every item on that previous texure that
we<00:07:29.919><c> just</c><00:07:30.000><c> showed</c><00:07:30.280><c> up</c><00:07:30.520><c> here</c><00:07:31.080><c> is</c><00:07:31.479><c> sound</c><00:07:32.039><c> and</c><00:07:32.240><c> has</c>

00:07:32.350 --> 00:07:32.360 align:start position:0%
we just showed up here is sound and has
 

00:07:32.360 --> 00:07:33.990 align:start position:0%
we just showed up here is sound and has
a<00:07:32.479><c> theoretical</c><00:07:33.039><c> construction</c><00:07:33.759><c> that</c><00:07:33.879><c> is</c>

00:07:33.990 --> 00:07:34.000 align:start position:0%
a theoretical construction that is
 

00:07:34.000 --> 00:07:36.070 align:start position:0%
a theoretical construction that is
believed<00:07:34.319><c> to</c><00:07:34.400><c> be</c><00:07:34.560><c> secure</c><00:07:35.319><c> in</c><00:07:35.440><c> fact</c><00:07:35.720><c> candidate</c>

00:07:36.070 --> 00:07:36.080 align:start position:0%
believed to be secure in fact candidate
 

00:07:36.080 --> 00:07:38.230 align:start position:0%
believed to be secure in fact candidate
schemes<00:07:36.479><c> even</c><00:07:36.680><c> for</c><00:07:37.000><c> the</c><00:07:37.199><c> most</c><00:07:37.800><c> expensive</c>

00:07:38.230 --> 00:07:38.240 align:start position:0%
schemes even for the most expensive
 

00:07:38.240 --> 00:07:41.029 align:start position:0%
schemes even for the most expensive
protocols<00:07:38.720><c> like</c><00:07:38.879><c> obfuscation</c><00:07:39.879><c> may</c><00:07:40.199><c> even</c><00:07:40.440><c> be</c>

00:07:41.029 --> 00:07:41.039 align:start position:0%
protocols like obfuscation may even be
 

00:07:41.039 --> 00:07:43.430 align:start position:0%
protocols like obfuscation may even be
practical<00:07:42.039><c> on</c><00:07:42.160><c> the</c><00:07:42.280><c> engineering</c><00:07:42.800><c> level</c><00:07:43.280><c> some</c>

00:07:43.430 --> 00:07:43.440 align:start position:0%
practical on the engineering level some
 

00:07:43.440 --> 00:07:45.230 align:start position:0%
practical on the engineering level some
of<00:07:43.560><c> the</c><00:07:43.720><c> first</c><00:07:44.000><c> branches</c><00:07:44.520><c> of</c><00:07:44.720><c> programmable</c>

00:07:45.230 --> 00:07:45.240 align:start position:0%
of the first branches of programmable
 

00:07:45.240 --> 00:07:47.469 align:start position:0%
of the first branches of programmable
cryptography<00:07:46.159><c> like</c><00:07:46.560><c> general</c><00:07:46.919><c> purpose</c><00:07:47.199><c> zero</c>

00:07:47.469 --> 00:07:47.479 align:start position:0%
cryptography like general purpose zero
 

00:07:47.479 --> 00:07:49.589 align:start position:0%
cryptography like general purpose zero
knowledge<00:07:47.759><c> proofs</c><00:07:48.639><c> uh</c><00:07:48.800><c> have</c><00:07:49.039><c> become</c>

00:07:49.589 --> 00:07:49.599 align:start position:0%
knowledge proofs uh have become
 

00:07:49.599 --> 00:07:51.510 align:start position:0%
knowledge proofs uh have become
practical<00:07:50.039><c> for</c><00:07:50.280><c> developers</c><00:07:50.800><c> today</c><00:07:51.120><c> to</c><00:07:51.280><c> start</c>

00:07:51.510 --> 00:07:51.520 align:start position:0%
practical for developers today to start
 

00:07:51.520 --> 00:07:53.589 align:start position:0%
practical for developers today to start
using<00:07:52.280><c> even</c><00:07:52.520><c> developers</c><00:07:53.000><c> who</c><00:07:53.159><c> aren't</c>

00:07:53.589 --> 00:07:53.599 align:start position:0%
using even developers who aren't
 

00:07:53.599 --> 00:07:55.029 align:start position:0%
using even developers who aren't
cryptography

00:07:55.029 --> 00:07:55.039 align:start position:0%
cryptography
 

00:07:55.039 --> 00:07:56.909 align:start position:0%
cryptography
specialists<00:07:56.039><c> in</c><00:07:56.199><c> addition</c><00:07:56.560><c> to</c><00:07:56.759><c> the</c>

00:07:56.909 --> 00:07:56.919 align:start position:0%
specialists in addition to the
 

00:07:56.919 --> 00:07:58.510 align:start position:0%
specialists in addition to the
technology<00:07:57.560><c> advancements</c><00:07:58.080><c> there</c><00:07:58.159><c> have</c><00:07:58.360><c> also</c>

00:07:58.510 --> 00:07:58.520 align:start position:0%
technology advancements there have also
 

00:07:58.520 --> 00:08:00.950 align:start position:0%
technology advancements there have also
been<00:07:58.720><c> significant</c><00:07:59.639><c> conceptual</c><00:08:00.400><c> advances</c>

00:08:00.950 --> 00:08:00.960 align:start position:0%
been significant conceptual advances
 

00:08:00.960 --> 00:08:02.749 align:start position:0%
been significant conceptual advances
over<00:08:01.159><c> the</c><00:08:01.319><c> last</c><00:08:01.479><c> one</c><00:08:01.639><c> to</c><00:08:01.759><c> two</c><00:08:01.960><c> years</c><00:08:02.520><c> we've</c>

00:08:02.749 --> 00:08:02.759 align:start position:0%
over the last one to two years we've
 

00:08:02.759 --> 00:08:04.670 align:start position:0%
over the last one to two years we've
recognized<00:08:03.400><c> programmable</c><00:08:03.960><c> cryptography</c><00:08:04.520><c> for</c>

00:08:04.670 --> 00:08:04.680 align:start position:0%
recognized programmable cryptography for
 

00:08:04.680 --> 00:08:06.589 align:start position:0%
recognized programmable cryptography for
the<00:08:04.840><c> first</c><00:08:05.080><c> time</c><00:08:05.520><c> as</c><00:08:05.639><c> a</c><00:08:05.800><c> unified</c><00:08:06.240><c> set</c><00:08:06.400><c> of</c>

00:08:06.589 --> 00:08:06.599 align:start position:0%
the first time as a unified set of
 

00:08:06.599 --> 00:08:08.909 align:start position:0%
the first time as a unified set of
capabilities<00:08:07.479><c> with</c><00:08:07.599><c> a</c><00:08:07.720><c> common</c><00:08:08.039><c> foundation</c>

00:08:08.909 --> 00:08:08.919 align:start position:0%
capabilities with a common foundation
 

00:08:08.919 --> 00:08:10.270 align:start position:0%
capabilities with a common foundation
and<00:08:09.039><c> we've</c><00:08:09.240><c> started</c><00:08:09.479><c> to</c><00:08:09.879><c> understand</c><00:08:10.080><c> how</c><00:08:10.199><c> we</c>

00:08:10.270 --> 00:08:10.280 align:start position:0%
and we've started to understand how we
 

00:08:10.280 --> 00:08:12.189 align:start position:0%
and we've started to understand how we
can<00:08:10.479><c> Leverage</c><00:08:10.919><c> The</c><00:08:11.120><c> Power</c><00:08:11.479><c> of</c><00:08:11.680><c> programmable</c>

00:08:12.189 --> 00:08:12.199 align:start position:0%
can Leverage The Power of programmable
 

00:08:12.199 --> 00:08:14.149 align:start position:0%
can Leverage The Power of programmable
cryptography<00:08:13.000><c> to</c><00:08:13.120><c> build</c><00:08:13.440><c> powerful</c><00:08:13.840><c> systems</c>

00:08:14.149 --> 00:08:14.159 align:start position:0%
cryptography to build powerful systems
 

00:08:14.159 --> 00:08:16.749 align:start position:0%
cryptography to build powerful systems
that<00:08:14.280><c> were</c><00:08:14.440><c> not</c><00:08:14.680><c> possible</c><00:08:15.199><c> before</c><00:08:16.199><c> rather</c>

00:08:16.749 --> 00:08:16.759 align:start position:0%
that were not possible before rather
 

00:08:16.759 --> 00:08:19.350 align:start position:0%
that were not possible before rather
than<00:08:16.960><c> simply</c><00:08:17.319><c> seeing</c><00:08:17.680><c> things</c><00:08:17.960><c> like</c><00:08:18.120><c> ZK</c><00:08:18.520><c> snarks</c>

00:08:19.350 --> 00:08:19.360 align:start position:0%
than simply seeing things like ZK snarks
 

00:08:19.360 --> 00:08:21.510 align:start position:0%
than simply seeing things like ZK snarks
as<00:08:19.560><c> a</c><00:08:19.720><c> one-off</c><00:08:20.240><c> way</c><00:08:20.639><c> to</c><00:08:20.840><c> perform</c><00:08:21.120><c> a</c><00:08:21.240><c> certain</c>

00:08:21.510 --> 00:08:21.520 align:start position:0%
as a one-off way to perform a certain
 

00:08:21.520 --> 00:08:23.110 align:start position:0%
as a one-off way to perform a certain
kind<00:08:21.639><c> of</c><00:08:21.840><c> hack</c><00:08:22.080><c> to</c><00:08:22.199><c> be</c><00:08:22.280><c> able</c><00:08:22.440><c> to</c><00:08:22.560><c> introduce</c><00:08:22.960><c> a</c>

00:08:23.110 --> 00:08:23.120 align:start position:0%
kind of hack to be able to introduce a
 

00:08:23.120 --> 00:08:25.670 align:start position:0%
kind of hack to be able to introduce a
specific<00:08:23.599><c> kind</c><00:08:23.759><c> of</c><00:08:23.919><c> privacy</c><00:08:24.319><c> feature</c><00:08:25.039><c> onto</c><00:08:25.479><c> a</c>

00:08:25.670 --> 00:08:25.680 align:start position:0%
specific kind of privacy feature onto a
 

00:08:25.680 --> 00:08:27.670 align:start position:0%
specific kind of privacy feature onto a
specific<00:08:26.039><c> kind</c><00:08:26.159><c> of</c><00:08:26.479><c> blockchain</c><00:08:26.960><c> architecture</c>

00:08:27.670 --> 00:08:27.680 align:start position:0%
specific kind of blockchain architecture
 

00:08:27.680 --> 00:08:29.550 align:start position:0%
specific kind of blockchain architecture
we<00:08:27.800><c> sort</c><00:08:28.000><c> of</c><00:08:28.479><c> understand</c><00:08:28.720><c> how</c><00:08:28.879><c> to</c><00:08:29.039><c> use</c><00:08:29.280><c> the</c>

00:08:29.550 --> 00:08:29.560 align:start position:0%
we sort of understand how to use the
 

00:08:29.560 --> 00:08:32.870 align:start position:0%
we sort of understand how to use the
general<00:08:29.960><c> programmability</c><00:08:30.960><c> of</c><00:08:31.199><c> these</c><00:08:31.880><c> tools</c>

00:08:32.870 --> 00:08:32.880 align:start position:0%
general programmability of these tools
 

00:08:32.880 --> 00:08:34.149 align:start position:0%
general programmability of these tools
okay<00:08:33.000><c> so</c><00:08:33.120><c> let's</c><00:08:33.399><c> return</c><00:08:33.519><c> to</c><00:08:33.640><c> our</c><00:08:33.800><c> question</c><00:08:34.000><c> of</c>

00:08:34.149 --> 00:08:34.159 align:start position:0%
okay so let's return to our question of
 

00:08:34.159 --> 00:08:36.870 align:start position:0%
okay so let's return to our question of
how<00:08:34.320><c> do</c><00:08:34.479><c> we</c><00:08:34.719><c> compute</c><00:08:35.240><c> together</c><00:08:36.240><c> um</c><00:08:36.440><c> I</c><00:08:36.519><c> want</c><00:08:36.719><c> to</c>

00:08:36.870 --> 00:08:36.880 align:start position:0%
how do we compute together um I want to
 

00:08:36.880 --> 00:08:38.870 align:start position:0%
how do we compute together um I want to
think<00:08:37.080><c> about</c><00:08:37.360><c> this</c><00:08:37.560><c> phrase</c><00:08:38.120><c> multi-party</c>

00:08:38.870 --> 00:08:38.880 align:start position:0%
think about this phrase multi-party
 

00:08:38.880 --> 00:08:40.909 align:start position:0%
think about this phrase multi-party
programming<00:08:39.479><c> you</c><00:08:39.599><c> know</c><00:08:39.760><c> the</c><00:08:39.919><c> act</c><00:08:40.159><c> of</c><00:08:40.519><c> multiple</c>

00:08:40.909 --> 00:08:40.919 align:start position:0%
programming you know the act of multiple
 

00:08:40.919 --> 00:08:43.430 align:start position:0%
programming you know the act of multiple
people<00:08:41.159><c> coming</c><00:08:41.560><c> together</c><00:08:42.360><c> and</c><00:08:42.880><c> trying</c><00:08:43.159><c> to</c>

00:08:43.430 --> 00:08:43.440 align:start position:0%
people coming together and trying to
 

00:08:43.440 --> 00:08:45.710 align:start position:0%
people coming together and trying to
perform<00:08:43.760><c> some</c><00:08:43.959><c> computation</c><00:08:44.560><c> together</c><00:08:45.560><c> again</c>

00:08:45.710 --> 00:08:45.720 align:start position:0%
perform some computation together again
 

00:08:45.720 --> 00:08:46.949 align:start position:0%
perform some computation together again
this<00:08:45.839><c> has</c><00:08:45.959><c> been</c><00:08:46.040><c> the</c><00:08:46.160><c> strategy</c><00:08:46.519><c> for</c><00:08:46.640><c> the</c><00:08:46.760><c> last</c>

00:08:46.949 --> 00:08:46.959 align:start position:0%
this has been the strategy for the last
 

00:08:46.959 --> 00:08:49.030 align:start position:0%
this has been the strategy for the last
30<00:08:47.240><c> years</c><00:08:47.600><c> but</c><00:08:47.959><c> abstractly</c><00:08:48.519><c> from</c><00:08:48.720><c> first</c>

00:08:49.030 --> 00:08:49.040 align:start position:0%
30 years but abstractly from first
 

00:08:49.040 --> 00:08:50.990 align:start position:0%
30 years but abstractly from first
principles<00:08:49.480><c> if</c><00:08:49.600><c> you</c><00:08:49.760><c> think</c><00:08:49.959><c> about</c><00:08:50.200><c> this</c><00:08:50.360><c> idea</c>

00:08:50.990 --> 00:08:51.000 align:start position:0%
principles if you think about this idea
 

00:08:51.000 --> 00:08:52.550 align:start position:0%
principles if you think about this idea
of<00:08:51.360><c> multiple</c><00:08:51.760><c> people</c><00:08:51.959><c> coming</c><00:08:52.279><c> together</c><00:08:52.440><c> to</c>

00:08:52.550 --> 00:08:52.560 align:start position:0%
of multiple people coming together to
 

00:08:52.560 --> 00:08:54.870 align:start position:0%
of multiple people coming together to
run<00:08:52.720><c> a</c><00:08:52.920><c> program</c><00:08:53.839><c> you</c><00:08:54.000><c> might</c><00:08:54.160><c> abstractly</c><00:08:54.680><c> want</c>

00:08:54.870 --> 00:08:54.880 align:start position:0%
run a program you might abstractly want
 

00:08:54.880 --> 00:08:56.310 align:start position:0%
run a program you might abstractly want
something<00:08:55.200><c> that</c><00:08:55.320><c> looks</c><00:08:55.600><c> like</c><00:08:55.839><c> this</c><00:08:56.120><c> so</c><00:08:56.240><c> you</c>

00:08:56.310 --> 00:08:56.320 align:start position:0%
something that looks like this so you
 

00:08:56.320 --> 00:08:57.509 align:start position:0%
something that looks like this so you
have<00:08:56.440><c> some</c><00:08:56.600><c> sort</c><00:08:56.760><c> of</c><00:08:56.839><c> network</c><00:08:57.200><c> you</c><00:08:57.279><c> have</c><00:08:57.399><c> some</c>

00:08:57.509 --> 00:08:57.519 align:start position:0%
have some sort of network you have some
 

00:08:57.519 --> 00:08:58.829 align:start position:0%
have some sort of network you have some
sort<00:08:57.640><c> of</c><00:08:57.760><c> participants</c><00:08:58.160><c> in</c><00:08:58.279><c> the</c><00:08:58.360><c> network</c><00:08:58.720><c> that</c>

00:08:58.829 --> 00:08:58.839 align:start position:0%
sort of participants in the network that
 

00:08:58.839 --> 00:09:02.470 align:start position:0%
sort of participants in the network that
want<00:08:58.959><c> to</c><00:08:59.120><c> do</c><00:08:59.560><c> some</c><00:08:59.920><c> action</c><00:09:00.920><c> and</c><00:09:01.680><c> they</c><00:09:02.120><c> you</c><00:09:02.240><c> know</c>

00:09:02.470 --> 00:09:02.480 align:start position:0%
want to do some action and they you know
 

00:09:02.480 --> 00:09:04.230 align:start position:0%
want to do some action and they you know
gather<00:09:02.839><c> all</c><00:09:03.040><c> their</c><00:09:03.399><c> respective</c><00:09:03.839><c> data</c><00:09:04.079><c> that's</c>

00:09:04.230 --> 00:09:04.240 align:start position:0%
gather all their respective data that's
 

00:09:04.240 --> 00:09:06.509 align:start position:0%
gather all their respective data that's
relevant<00:09:04.519><c> to</c><00:09:04.640><c> the</c><00:09:05.240><c> computation</c><00:09:06.240><c> and</c><00:09:06.360><c> they</c>

00:09:06.509 --> 00:09:06.519 align:start position:0%
relevant to the computation and they
 

00:09:06.519 --> 00:09:07.910 align:start position:0%
relevant to the computation and they
produce<00:09:06.920><c> the</c><00:09:07.040><c> results</c><00:09:07.279><c> of</c><00:09:07.440><c> the</c><00:09:07.519><c> computation</c>

00:09:07.910 --> 00:09:07.920 align:start position:0%
produce the results of the computation
 

00:09:07.920 --> 00:09:09.350 align:start position:0%
produce the results of the computation
and<00:09:08.040><c> they</c><00:09:08.160><c> want</c><00:09:08.240><c> to</c><00:09:08.360><c> be</c><00:09:08.440><c> able</c><00:09:08.560><c> to</c><00:09:08.680><c> do</c><00:09:08.800><c> so</c><00:09:08.959><c> with</c>

00:09:09.350 --> 00:09:09.360 align:start position:0%
and they want to be able to do so with
 

00:09:09.360 --> 00:09:11.310 align:start position:0%
and they want to be able to do so with
privacy<00:09:09.839><c> Integrity</c><00:09:10.560><c> interoperability</c>

00:09:11.310 --> 00:09:11.320 align:start position:0%
privacy Integrity interoperability
 

00:09:11.320 --> 00:09:12.389 align:start position:0%
privacy Integrity interoperability
guarantees<00:09:11.760><c> and</c><00:09:11.880><c> for</c><00:09:12.000><c> this</c><00:09:12.120><c> to</c><00:09:12.200><c> be</c>

00:09:12.389 --> 00:09:12.399 align:start position:0%
guarantees and for this to be
 

00:09:12.399 --> 00:09:14.829 align:start position:0%
guarantees and for this to be
practically<00:09:13.200><c> feasible</c><00:09:14.200><c> so</c><00:09:14.360><c> let's</c><00:09:14.519><c> zoom</c><00:09:14.720><c> in</c>

00:09:14.829 --> 00:09:14.839 align:start position:0%
practically feasible so let's zoom in
 

00:09:14.839 --> 00:09:16.590 align:start position:0%
practically feasible so let's zoom in
and<00:09:14.959><c> look</c><00:09:15.079><c> at</c><00:09:15.160><c> the</c><00:09:15.279><c> anatomy</c><00:09:15.720><c> of</c><00:09:15.880><c> such</c><00:09:16.279><c> a</c>

00:09:16.590 --> 00:09:16.600 align:start position:0%
and look at the anatomy of such a
 

00:09:16.600 --> 00:09:19.269 align:start position:0%
and look at the anatomy of such a
program<00:09:17.560><c> the</c><00:09:17.720><c> general</c><00:09:18.120><c> pattern</c><00:09:18.560><c> here</c><00:09:19.120><c> is</c>

00:09:19.269 --> 00:09:19.279 align:start position:0%
program the general pattern here is
 

00:09:19.279 --> 00:09:20.829 align:start position:0%
program the general pattern here is
slightly<00:09:19.640><c> more</c><00:09:19.839><c> complex</c><00:09:20.240><c> than</c><00:09:20.360><c> this</c><00:09:20.480><c> diagram</c>

00:09:20.829 --> 00:09:20.839 align:start position:0%
slightly more complex than this diagram
 

00:09:20.839 --> 00:09:22.630 align:start position:0%
slightly more complex than this diagram
that<00:09:20.920><c> we're</c><00:09:21.079><c> zooming</c><00:09:21.360><c> in</c><00:09:21.480><c> on</c><00:09:21.640><c> but</c><00:09:21.760><c> not</c><00:09:21.959><c> by</c>

00:09:22.630 --> 00:09:22.640 align:start position:0%
that we're zooming in on but not by
 

00:09:22.640 --> 00:09:25.190 align:start position:0%
that we're zooming in on but not by
much<00:09:23.680><c> essentially</c><00:09:24.680><c> in</c><00:09:24.839><c> one</c><00:09:24.920><c> of</c><00:09:25.040><c> these</c>

00:09:25.190 --> 00:09:25.200 align:start position:0%
much essentially in one of these
 

00:09:25.200 --> 00:09:26.829 align:start position:0%
much essentially in one of these
multiparty<00:09:25.760><c> programs</c><00:09:26.160><c> there</c><00:09:26.279><c> might</c><00:09:26.440><c> be</c><00:09:26.600><c> three</c>

00:09:26.829 --> 00:09:26.839 align:start position:0%
multiparty programs there might be three
 

00:09:26.839 --> 00:09:28.389 align:start position:0%
multiparty programs there might be three
kinds<00:09:27.040><c> of</c><00:09:27.279><c> data</c><00:09:27.839><c> that</c><00:09:27.959><c> we</c><00:09:28.120><c> would</c><00:09:28.240><c> be</c>

00:09:28.389 --> 00:09:28.399 align:start position:0%
kinds of data that we would be
 

00:09:28.399 --> 00:09:30.790 align:start position:0%
kinds of data that we would be
interested<00:09:28.680><c> in</c><00:09:28.800><c> running</c><00:09:29.079><c> our</c><00:09:29.480><c> program</c><00:09:29.800><c> on</c>

00:09:30.790 --> 00:09:30.800 align:start position:0%
interested in running our program on
 

00:09:30.800 --> 00:09:32.790 align:start position:0%
interested in running our program on
there's<00:09:31.040><c> some</c><00:09:31.200><c> sort</c><00:09:31.399><c> of</c><00:09:31.800><c> global</c><00:09:32.200><c> public</c><00:09:32.560><c> data</c>

00:09:32.790 --> 00:09:32.800 align:start position:0%
there's some sort of global public data
 

00:09:32.800 --> 00:09:34.670 align:start position:0%
there's some sort of global public data
that<00:09:32.920><c> everybody</c><00:09:33.320><c> knows</c><00:09:34.200><c> and</c><00:09:34.320><c> then</c><00:09:34.440><c> there's</c>

00:09:34.670 --> 00:09:34.680 align:start position:0%
that everybody knows and then there's
 

00:09:34.680 --> 00:09:36.829 align:start position:0%
that everybody knows and then there's
data<00:09:34.920><c> that</c><00:09:35.120><c> might</c><00:09:35.360><c> belong</c><00:09:35.680><c> to</c><00:09:35.959><c> or</c><00:09:36.160><c> live</c><00:09:36.320><c> on</c><00:09:36.720><c> the</c>

00:09:36.829 --> 00:09:36.839 align:start position:0%
data that might belong to or live on the
 

00:09:36.839 --> 00:09:39.030 align:start position:0%
data that might belong to or live on the
machines<00:09:37.279><c> of</c><00:09:37.800><c> specific</c><00:09:38.160><c> participants</c><00:09:38.600><c> in</c><00:09:38.680><c> the</c>

00:09:39.030 --> 00:09:39.040 align:start position:0%
machines of specific participants in the
 

00:09:39.040 --> 00:09:40.910 align:start position:0%
machines of specific participants in the
computation<00:09:40.040><c> and</c><00:09:40.120><c> then</c><00:09:40.240><c> there</c><00:09:40.399><c> might</c><00:09:40.560><c> also</c><00:09:40.720><c> be</c>

00:09:40.910 --> 00:09:40.920 align:start position:0%
computation and then there might also be
 

00:09:40.920 --> 00:09:43.389 align:start position:0%
computation and then there might also be
data<00:09:41.160><c> that</c><00:09:41.360><c> only</c><00:09:41.680><c> the</c><00:09:41.880><c> program</c><00:09:42.399><c> knows</c><00:09:43.279><c> and</c>

00:09:43.389 --> 00:09:43.399 align:start position:0%
data that only the program knows and
 

00:09:43.399 --> 00:09:45.389 align:start position:0%
data that only the program knows and
we'd<00:09:43.600><c> like</c><00:09:43.720><c> to</c><00:09:43.839><c> be</c><00:09:43.959><c> able</c><00:09:44.160><c> to</c><00:09:44.360><c> run</c><00:09:44.880><c> some</c><00:09:45.079><c> kind</c><00:09:45.200><c> of</c>

00:09:45.389 --> 00:09:45.399 align:start position:0%
we'd like to be able to run some kind of
 

00:09:45.399 --> 00:09:46.949 align:start position:0%
we'd like to be able to run some kind of
program<00:09:45.720><c> over</c><00:09:45.880><c> all</c><00:09:46.040><c> three</c><00:09:46.240><c> types</c><00:09:46.440><c> of</c><00:09:46.600><c> data</c><00:09:46.800><c> to</c>

00:09:46.949 --> 00:09:46.959 align:start position:0%
program over all three types of data to
 

00:09:46.959 --> 00:09:49.430 align:start position:0%
program over all three types of data to
produce<00:09:47.240><c> an</c><00:09:47.640><c> output</c><00:09:48.640><c> now</c><00:09:48.800><c> ethereum</c><00:09:49.160><c> gets</c><00:09:49.320><c> us</c>

00:09:49.430 --> 00:09:49.440 align:start position:0%
produce an output now ethereum gets us
 

00:09:49.440 --> 00:09:51.269 align:start position:0%
produce an output now ethereum gets us
part<00:09:49.560><c> of</c><00:09:49.640><c> the</c><00:09:49.760><c> way</c><00:09:50.000><c> there</c><00:09:50.440><c> ethereum</c><00:09:50.880><c> allows</c><00:09:51.160><c> us</c>

00:09:51.269 --> 00:09:51.279 align:start position:0%
part of the way there ethereum allows us
 

00:09:51.279 --> 00:09:53.269 align:start position:0%
part of the way there ethereum allows us
to<00:09:51.399><c> collectively</c><00:09:52.000><c> run</c><00:09:52.440><c> a</c><00:09:52.560><c> world</c><00:09:52.880><c> computer</c>

00:09:53.269 --> 00:09:53.279 align:start position:0%
to collectively run a world computer
 

00:09:53.279 --> 00:09:55.790 align:start position:0%
to collectively run a world computer
that<00:09:53.440><c> takes</c><00:09:53.640><c> in</c><00:09:53.800><c> some</c><00:09:54.079><c> Global</c><00:09:54.560><c> public</c><00:09:54.880><c> State</c>

00:09:55.790 --> 00:09:55.800 align:start position:0%
that takes in some Global public State
 

00:09:55.800 --> 00:09:58.030 align:start position:0%
that takes in some Global public State
and<00:09:56.120><c> perform</c><00:09:56.399><c> a</c><00:09:56.600><c> verifiable</c><00:09:57.399><c> computation</c>

00:09:58.030 --> 00:09:58.040 align:start position:0%
and perform a verifiable computation
 

00:09:58.040 --> 00:10:01.829 align:start position:0%
and perform a verifiable computation
together<00:09:58.279><c> on</c><00:09:58.519><c> that</c><00:09:59.600><c> but</c><00:10:00.600><c> like</c><00:10:01.200><c> other</c>

00:10:01.829 --> 00:10:01.839 align:start position:0%
together on that but like other
 

00:10:01.839 --> 00:10:03.269 align:start position:0%
together on that but like other
peer-to-peer<00:10:02.200><c> systems</c><00:10:02.640><c> and</c><00:10:02.760><c> blockchains</c>

00:10:03.269 --> 00:10:03.279 align:start position:0%
peer-to-peer systems and blockchains
 

00:10:03.279 --> 00:10:05.230 align:start position:0%
peer-to-peer systems and blockchains
historically<00:10:04.120><c> full</c><00:10:04.519><c> multi-party</c>

00:10:05.230 --> 00:10:05.240 align:start position:0%
historically full multi-party
 

00:10:05.240 --> 00:10:07.150 align:start position:0%
historically full multi-party
programming<00:10:05.680><c> has</c><00:10:05.839><c> not</c><00:10:06.079><c> been</c><00:10:06.360><c> possible</c><00:10:06.920><c> with</c>

00:10:07.150 --> 00:10:07.160 align:start position:0%
programming has not been possible with
 

00:10:07.160 --> 00:10:09.030 align:start position:0%
programming has not been possible with
this<00:10:07.399><c> model</c><00:10:07.959><c> being</c><00:10:08.160><c> able</c><00:10:08.360><c> to</c><00:10:08.480><c> do</c><00:10:08.680><c> this</c><00:10:08.839><c> with</c>

00:10:09.030 --> 00:10:09.040 align:start position:0%
this model being able to do this with
 

00:10:09.040 --> 00:10:10.910 align:start position:0%
this model being able to do this with
all<00:10:09.200><c> of</c><00:10:09.399><c> those</c><00:10:09.640><c> different</c><00:10:09.920><c> kinds</c><00:10:10.120><c> of</c>

00:10:10.910 --> 00:10:10.920 align:start position:0%
all of those different kinds of
 

00:10:10.920 --> 00:10:13.110 align:start position:0%
all of those different kinds of
state<00:10:11.920><c> so</c><00:10:12.120><c> everything</c><00:10:12.399><c> I've</c><00:10:12.560><c> been</c><00:10:12.680><c> saying</c><00:10:12.920><c> so</c>

00:10:13.110 --> 00:10:13.120 align:start position:0%
state so everything I've been saying so
 

00:10:13.120 --> 00:10:14.790 align:start position:0%
state so everything I've been saying so
far<00:10:13.279><c> has</c><00:10:13.399><c> been</c><00:10:13.560><c> a</c><00:10:13.640><c> little</c><00:10:13.839><c> bit</c><00:10:14.160><c> abstract</c><00:10:14.640><c> and</c><00:10:14.720><c> I</c>

00:10:14.790 --> 00:10:14.800 align:start position:0%
far has been a little bit abstract and I
 

00:10:14.800 --> 00:10:16.509 align:start position:0%
far has been a little bit abstract and I
want<00:10:14.880><c> to</c><00:10:15.000><c> dig</c><00:10:15.160><c> into</c><00:10:15.360><c> a</c><00:10:15.519><c> specific</c>

00:10:16.509 --> 00:10:16.519 align:start position:0%
want to dig into a specific
 

00:10:16.519 --> 00:10:18.750 align:start position:0%
want to dig into a specific
example<00:10:17.519><c> lately</c><00:10:17.880><c> there's</c><00:10:18.079><c> been</c><00:10:18.200><c> a</c><00:10:18.360><c> lot</c><00:10:18.560><c> of</c>

00:10:18.750 --> 00:10:18.760 align:start position:0%
example lately there's been a lot of
 

00:10:18.760 --> 00:10:21.150 align:start position:0%
example lately there's been a lot of
interest<00:10:19.279><c> in</c><00:10:19.600><c> decentralized</c><00:10:20.440><c> social</c><00:10:20.760><c> media</c>

00:10:21.150 --> 00:10:21.160 align:start position:0%
interest in decentralized social media
 

00:10:21.160 --> 00:10:23.829 align:start position:0%
interest in decentralized social media
in<00:10:21.360><c> particular</c><00:10:22.240><c> we've</c><00:10:22.480><c> seen</c><00:10:23.200><c> uh</c><00:10:23.360><c> protocols</c>

00:10:23.829 --> 00:10:23.839 align:start position:0%
in particular we've seen uh protocols
 

00:10:23.839 --> 00:10:25.829 align:start position:0%
in particular we've seen uh protocols
and<00:10:24.000><c> applications</c><00:10:24.480><c> like</c><00:10:24.600><c> farcaster</c><00:10:25.320><c> blue</c><00:10:25.600><c> sky</c>

00:10:25.829 --> 00:10:25.839 align:start position:0%
and applications like farcaster blue sky
 

00:10:25.839 --> 00:10:28.069 align:start position:0%
and applications like farcaster blue sky
noer<00:10:26.279><c> and</c><00:10:26.440><c> mastedon</c><00:10:26.959><c> start</c><00:10:27.160><c> to</c><00:10:27.279><c> emerge</c><00:10:27.880><c> and</c>

00:10:28.069 --> 00:10:28.079 align:start position:0%
noer and mastedon start to emerge and
 

00:10:28.079 --> 00:10:30.870 align:start position:0%
noer and mastedon start to emerge and
communities<00:10:28.519><c> to</c><00:10:28.680><c> get</c><00:10:28.760><c> built</c><00:10:29.000><c> on</c><00:10:29.120><c> top</c><00:10:29.440><c> of</c><00:10:29.880><c> these</c>

00:10:30.870 --> 00:10:30.880 align:start position:0%
communities to get built on top of these
 

00:10:30.880 --> 00:10:32.829 align:start position:0%
communities to get built on top of these
um<00:10:31.640><c> one</c><00:10:31.839><c> thing</c><00:10:32.040><c> that's</c><00:10:32.240><c> really</c><00:10:32.440><c> interesting</c>

00:10:32.829 --> 00:10:32.839 align:start position:0%
um one thing that's really interesting
 

00:10:32.839 --> 00:10:35.350 align:start position:0%
um one thing that's really interesting
about<00:10:33.040><c> this</c><00:10:33.160><c> trend</c><00:10:33.440><c> to</c><00:10:33.640><c> me</c><00:10:34.279><c> and</c><00:10:34.480><c> one</c><00:10:34.800><c> pattern</c>

00:10:35.350 --> 00:10:35.360 align:start position:0%
about this trend to me and one pattern
 

00:10:35.360 --> 00:10:37.949 align:start position:0%
about this trend to me and one pattern
that<00:10:35.519><c> I've</c><00:10:35.720><c> observed</c><00:10:36.160><c> is</c><00:10:36.440><c> that</c><00:10:37.440><c> people</c><00:10:37.720><c> tend</c>

00:10:37.949 --> 00:10:37.959 align:start position:0%
that I've observed is that people tend
 

00:10:37.959 --> 00:10:40.230 align:start position:0%
that I've observed is that people tend
to<00:10:38.200><c> frame</c><00:10:38.639><c> the</c><00:10:38.880><c> problem</c><00:10:39.279><c> of</c><00:10:39.480><c> decentralized</c>

00:10:40.230 --> 00:10:40.240 align:start position:0%
to frame the problem of decentralized
 

00:10:40.240 --> 00:10:42.069 align:start position:0%
to frame the problem of decentralized
social<00:10:40.519><c> media</c><00:10:40.800><c> or</c><00:10:40.920><c> building</c><00:10:41.200><c> a</c><00:10:41.320><c> decentralized</c>

00:10:42.069 --> 00:10:42.079 align:start position:0%
social media or building a decentralized
 

00:10:42.079 --> 00:10:44.069 align:start position:0%
social media or building a decentralized
social<00:10:42.399><c> app</c><00:10:42.880><c> in</c><00:10:43.000><c> terms</c><00:10:43.279><c> of</c><00:10:43.519><c> building</c><00:10:43.839><c> a</c>

00:10:44.069 --> 00:10:44.079 align:start position:0%
social app in terms of building a
 

00:10:44.079 --> 00:10:45.990 align:start position:0%
social app in terms of building a
decentralized<00:10:44.839><c> Twitter</c><00:10:45.360><c> we</c><00:10:45.480><c> always</c><00:10:45.800><c> very</c>

00:10:45.990 --> 00:10:46.000 align:start position:0%
decentralized Twitter we always very
 

00:10:46.000 --> 00:10:48.710 align:start position:0%
decentralized Twitter we always very
specifically<00:10:46.360><c> use</c><00:10:46.600><c> Twitter</c><00:10:47.480><c> my</c><00:10:47.639><c> question</c><00:10:47.880><c> is</c>

00:10:48.710 --> 00:10:48.720 align:start position:0%
specifically use Twitter my question is
 

00:10:48.720 --> 00:10:49.829 align:start position:0%
specifically use Twitter my question is
why<00:10:49.079><c> do</c><00:10:49.240><c> we</c><00:10:49.360><c> always</c><00:10:49.560><c> talk</c><00:10:49.680><c> about</c>

00:10:49.829 --> 00:10:49.839 align:start position:0%
why do we always talk about
 

00:10:49.839 --> 00:10:51.430 align:start position:0%
why do we always talk about
decentralized<00:10:50.440><c> Twitter</c><00:10:50.800><c> why</c><00:10:50.920><c> don't</c><00:10:51.160><c> people</c>

00:10:51.430 --> 00:10:51.440 align:start position:0%
decentralized Twitter why don't people
 

00:10:51.440 --> 00:10:52.470 align:start position:0%
decentralized Twitter why don't people
talk<00:10:51.600><c> about</c><00:10:51.800><c> you</c><00:10:51.880><c> know</c><00:10:52.000><c> one</c><00:10:52.079><c> of</c><00:10:52.200><c> the</c><00:10:52.279><c> other</c>

00:10:52.470 --> 00:10:52.480 align:start position:0%
talk about you know one of the other
 

00:10:52.480 --> 00:10:54.030 align:start position:0%
talk about you know one of the other
social<00:10:52.720><c> medias</c><00:10:53.000><c> out</c><00:10:53.160><c> there</c><00:10:53.360><c> like</c><00:10:53.600><c> building</c>

00:10:54.030 --> 00:10:54.040 align:start position:0%
social medias out there like building
 

00:10:54.040 --> 00:10:55.389 align:start position:0%
social medias out there like building
decentralized

00:10:55.389 --> 00:10:55.399 align:start position:0%
decentralized
 

00:10:55.399 --> 00:10:57.069 align:start position:0%
decentralized
Facebook<00:10:56.399><c> you</c><00:10:56.519><c> know</c><00:10:56.680><c> there</c><00:10:56.800><c> could</c><00:10:56.959><c> be</c>

00:10:57.069 --> 00:10:57.079 align:start position:0%
Facebook you know there could be
 

00:10:57.079 --> 00:10:58.550 align:start position:0%
Facebook you know there could be
cultural<00:10:57.480><c> reasons</c><00:10:57.880><c> behind</c><00:10:58.120><c> this</c><00:10:58.320><c> maybe</c>

00:10:58.550 --> 00:10:58.560 align:start position:0%
cultural reasons behind this maybe
 

00:10:58.560 --> 00:11:00.550 align:start position:0%
cultural reasons behind this maybe
people<00:10:58.839><c> interested</c><00:10:59.399><c> in</c><00:10:59.600><c> in</c><00:10:59.760><c> decentralization</c>

00:11:00.550 --> 00:11:00.560 align:start position:0%
people interested in in decentralization
 

00:11:00.560 --> 00:11:02.710 align:start position:0%
people interested in in decentralization
tend<00:11:00.800><c> to</c><00:11:01.120><c> have</c><00:11:01.320><c> congregated</c><00:11:01.839><c> on</c><00:11:01.959><c> Twitter</c><00:11:02.600><c> um</c>

00:11:02.710 --> 00:11:02.720 align:start position:0%
tend to have congregated on Twitter um
 

00:11:02.720 --> 00:11:03.990 align:start position:0%
tend to have congregated on Twitter um
but<00:11:02.839><c> I</c><00:11:02.920><c> think</c><00:11:03.000><c> that</c><00:11:03.120><c> there's</c><00:11:03.320><c> also</c><00:11:03.480><c> a</c><00:11:03.639><c> deeper</c>

00:11:03.990 --> 00:11:04.000 align:start position:0%
but I think that there's also a deeper
 

00:11:04.000 --> 00:11:06.269 align:start position:0%
but I think that there's also a deeper
technical<00:11:04.399><c> reason</c><00:11:04.680><c> behind</c><00:11:04.920><c> this</c><00:11:05.079><c> as</c><00:11:05.240><c> well</c><00:11:06.160><c> and</c>

00:11:06.269 --> 00:11:06.279 align:start position:0%
technical reason behind this as well and
 

00:11:06.279 --> 00:11:07.590 align:start position:0%
technical reason behind this as well and
the<00:11:06.360><c> reason</c><00:11:06.600><c> for</c><00:11:06.760><c> that</c><00:11:06.880><c> is</c><00:11:07.000><c> that</c><00:11:07.120><c> the</c><00:11:07.279><c> state</c>

00:11:07.590 --> 00:11:07.600 align:start position:0%
the reason for that is that the state
 

00:11:07.600 --> 00:11:09.710 align:start position:0%
the reason for that is that the state
topology<00:11:08.160><c> of</c><00:11:08.360><c> Facebook</c><00:11:09.000><c> is</c><00:11:09.200><c> much</c><00:11:09.360><c> more</c>

00:11:09.710 --> 00:11:09.720 align:start position:0%
topology of Facebook is much more
 

00:11:09.720 --> 00:11:11.829 align:start position:0%
topology of Facebook is much more
complicated<00:11:10.600><c> than</c><00:11:10.760><c> the</c><00:11:10.920><c> simplified</c><00:11:11.440><c> model</c><00:11:11.720><c> of</c>

00:11:11.829 --> 00:11:11.839 align:start position:0%
complicated than the simplified model of
 

00:11:11.839 --> 00:11:14.110 align:start position:0%
complicated than the simplified model of
Twitter<00:11:12.240><c> you</c><00:11:12.360><c> know</c><00:11:12.519><c> in</c><00:11:12.680><c> Twitter</c><00:11:13.639><c> everyone</c><00:11:14.000><c> can</c>

00:11:14.110 --> 00:11:14.120 align:start position:0%
Twitter you know in Twitter everyone can
 

00:11:14.120 --> 00:11:16.030 align:start position:0%
Twitter you know in Twitter everyone can
see<00:11:14.399><c> everything</c><00:11:14.760><c> and</c><00:11:14.920><c> everyone</c><00:11:15.399><c> broadcasts</c>

00:11:16.030 --> 00:11:16.040 align:start position:0%
see everything and everyone broadcasts
 

00:11:16.040 --> 00:11:18.509 align:start position:0%
see everything and everyone broadcasts
every<00:11:16.279><c> post</c><00:11:16.519><c> to</c><00:11:16.680><c> everybody</c><00:11:17.079><c> else</c><00:11:18.000><c> so</c><00:11:18.240><c> now</c><00:11:18.399><c> you</c>

00:11:18.509 --> 00:11:18.519 align:start position:0%
every post to everybody else so now you
 

00:11:18.519 --> 00:11:20.150 align:start position:0%
every post to everybody else so now you
sort<00:11:18.680><c> of</c><00:11:18.800><c> need</c><00:11:18.920><c> to</c><00:11:19.079><c> reduce</c><00:11:19.480><c> this</c><00:11:19.639><c> down</c><00:11:19.800><c> to</c><00:11:20.000><c> some</c>

00:11:20.150 --> 00:11:20.160 align:start position:0%
sort of need to reduce this down to some
 

00:11:20.160 --> 00:11:22.670 align:start position:0%
sort of need to reduce this down to some
sort<00:11:20.320><c> of</c><00:11:20.440><c> decentralized</c><00:11:21.279><c> messaging</c><00:11:21.720><c> protocol</c>

00:11:22.670 --> 00:11:22.680 align:start position:0%
sort of decentralized messaging protocol
 

00:11:22.680 --> 00:11:24.670 align:start position:0%
sort of decentralized messaging protocol
you<00:11:22.800><c> know</c><00:11:22.920><c> in</c><00:11:23.200><c> essence</c><00:11:24.200><c> so</c><00:11:24.360><c> the</c><00:11:24.480><c> state</c>

00:11:24.670 --> 00:11:24.680 align:start position:0%
you know in essence so the state
 

00:11:24.680 --> 00:11:26.509 align:start position:0%
you know in essence so the state
topology<00:11:25.079><c> of</c><00:11:25.160><c> Twitter</c><00:11:25.440><c> might</c><00:11:25.560><c> look</c><00:11:25.760><c> something</c>

00:11:26.509 --> 00:11:26.519 align:start position:0%
topology of Twitter might look something
 

00:11:26.519 --> 00:11:27.990 align:start position:0%
topology of Twitter might look something
like<00:11:26.760><c> this</c><00:11:26.959><c> you</c><00:11:27.040><c> know</c><00:11:27.200><c> it's</c><00:11:27.360><c> a</c><00:11:27.519><c> it's</c><00:11:27.600><c> a</c><00:11:27.760><c> very</c>

00:11:27.990 --> 00:11:28.000 align:start position:0%
like this you know it's a it's a very
 

00:11:28.000 --> 00:11:29.629 align:start position:0%
like this you know it's a it's a very
homogeneous<00:11:28.560><c> simple</c><00:11:28.839><c> thing</c><00:11:28.959><c> to</c><00:11:29.079><c> read</c><00:11:29.320><c> Reon</c>

00:11:29.629 --> 00:11:29.639 align:start position:0%
homogeneous simple thing to read Reon
 

00:11:29.639 --> 00:11:31.790 align:start position:0%
homogeneous simple thing to read Reon
about<00:11:30.639><c> whereas</c><00:11:30.920><c> the</c><00:11:31.040><c> state</c><00:11:31.279><c> topology</c><00:11:31.720><c> of</c>

00:11:31.790 --> 00:11:31.800 align:start position:0%
about whereas the state topology of
 

00:11:31.800 --> 00:11:33.870 align:start position:0%
about whereas the state topology of
Facebook<00:11:32.120><c> is</c><00:11:32.279><c> much</c><00:11:32.440><c> more</c><00:11:32.680><c> complex</c><00:11:33.639><c> right</c><00:11:33.760><c> you</c>

00:11:33.870 --> 00:11:33.880 align:start position:0%
Facebook is much more complex right you
 

00:11:33.880 --> 00:11:34.990 align:start position:0%
Facebook is much more complex right you
might<00:11:34.079><c> have</c><00:11:34.240><c> things</c><00:11:34.440><c> like</c><00:11:34.600><c> friends</c><00:11:34.800><c> of</c>

00:11:34.990 --> 00:11:35.000 align:start position:0%
might have things like friends of
 

00:11:35.000 --> 00:11:36.710 align:start position:0%
might have things like friends of
friends<00:11:35.240><c> can</c><00:11:35.360><c> see</c><00:11:35.560><c> my</c><00:11:35.720><c> timeline</c><00:11:36.440><c> we</c><00:11:36.560><c> might</c>

00:11:36.710 --> 00:11:36.720 align:start position:0%
friends can see my timeline we might
 

00:11:36.720 --> 00:11:38.590 align:start position:0%
friends can see my timeline we might
have<00:11:36.920><c> private</c><00:11:37.200><c> groups</c><00:11:37.519><c> where</c><00:11:37.720><c> things</c><00:11:38.000><c> happen</c>

00:11:38.590 --> 00:11:38.600 align:start position:0%
have private groups where things happen
 

00:11:38.600 --> 00:11:39.629 align:start position:0%
have private groups where things happen
you<00:11:38.720><c> might</c><00:11:38.920><c> have</c><00:11:39.120><c> personalized</c>

00:11:39.629 --> 00:11:39.639 align:start position:0%
you might have personalized
 

00:11:39.639 --> 00:11:41.670 align:start position:0%
you might have personalized
recommendations<00:11:40.480><c> based</c><00:11:40.760><c> off</c><00:11:40.920><c> of</c><00:11:41.279><c> how</c><00:11:41.440><c> your</c>

00:11:41.670 --> 00:11:41.680 align:start position:0%
recommendations based off of how your
 

00:11:41.680 --> 00:11:42.990 align:start position:0%
recommendations based off of how your
history<00:11:41.959><c> intersects</c><00:11:42.399><c> with</c><00:11:42.519><c> other</c><00:11:42.639><c> people's</c>

00:11:42.990 --> 00:11:43.000 align:start position:0%
history intersects with other people's
 

00:11:43.000 --> 00:11:45.190 align:start position:0%
history intersects with other people's
history<00:11:43.360><c> or</c><00:11:43.800><c> apis</c><00:11:44.279><c> that</c><00:11:44.399><c> behave</c><00:11:44.680><c> differently</c>

00:11:45.190 --> 00:11:45.200 align:start position:0%
history or apis that behave differently
 

00:11:45.200 --> 00:11:47.350 align:start position:0%
history or apis that behave differently
depending<00:11:45.639><c> on</c><00:11:46.200><c> the</c><00:11:46.399><c> combination</c><00:11:46.880><c> of</c><00:11:47.040><c> multiple</c>

00:11:47.350 --> 00:11:47.360 align:start position:0%
depending on the combination of multiple
 

00:11:47.360 --> 00:11:49.230 align:start position:0%
depending on the combination of multiple
people's<00:11:47.680><c> settings</c><00:11:48.519><c> um</c><00:11:48.680><c> this</c><00:11:48.800><c> person's</c><00:11:49.120><c> a</c>

00:11:49.230 --> 00:11:49.240 align:start position:0%
people's settings um this person's a
 

00:11:49.240 --> 00:11:50.710 align:start position:0%
people's settings um this person's a
third<00:11:49.480><c> degree</c><00:11:49.760><c> connection</c><00:11:50.480><c> and</c><00:11:50.600><c> that</c>

00:11:50.710 --> 00:11:50.720 align:start position:0%
third degree connection and that
 

00:11:50.720 --> 00:11:52.629 align:start position:0%
third degree connection and that
influences<00:11:51.200><c> my</c><00:11:51.320><c> recommendation</c><00:11:51.920><c> somehow</c><00:11:52.279><c> etc</c>

00:11:52.629 --> 00:11:52.639 align:start position:0%
influences my recommendation somehow etc
 

00:11:52.639 --> 00:11:55.190 align:start position:0%
influences my recommendation somehow etc
etc<00:11:53.040><c> so</c><00:11:53.480><c> the</c><00:11:53.639><c> state</c><00:11:53.920><c> topology</c><00:11:54.360><c> of</c><00:11:54.519><c> Facebook</c>

00:11:55.190 --> 00:11:55.200 align:start position:0%
etc so the state topology of Facebook
 

00:11:55.200 --> 00:11:57.030 align:start position:0%
etc so the state topology of Facebook
looks<00:11:55.600><c> much</c><00:11:55.800><c> more</c>

00:11:57.030 --> 00:11:57.040 align:start position:0%
looks much more
 

00:11:57.040 --> 00:12:00.430 align:start position:0%
looks much more
complicated<00:11:58.040><c> and</c><00:11:58.560><c> in</c><00:11:58.680><c> the</c><00:11:58.839><c> general</c><00:11:59.519><c> case</c>

00:12:00.430 --> 00:12:00.440 align:start position:0%
complicated and in the general case
 

00:12:00.440 --> 00:12:03.030 align:start position:0%
complicated and in the general case
emulating<00:12:01.240><c> those</c><00:12:01.600><c> kinds</c><00:12:01.880><c> of</c><00:12:02.120><c> more</c><00:12:02.480><c> complex</c>

00:12:03.030 --> 00:12:03.040 align:start position:0%
emulating those kinds of more complex
 

00:12:03.040 --> 00:12:05.629 align:start position:0%
emulating those kinds of more complex
topologies<00:12:03.639><c> or</c><00:12:03.839><c> multi-party</c><00:12:04.639><c> programs</c><00:12:05.399><c> is</c>

00:12:05.629 --> 00:12:05.639 align:start position:0%
topologies or multi-party programs is
 

00:12:05.639 --> 00:12:07.790 align:start position:0%
topologies or multi-party programs is
impossible<00:12:06.160><c> to</c><00:12:06.320><c> achieve</c><00:12:07.200><c> empirically</c><00:12:07.680><c> with</c>

00:12:07.790 --> 00:12:07.800 align:start position:0%
impossible to achieve empirically with
 

00:12:07.800 --> 00:12:09.949 align:start position:0%
impossible to achieve empirically with
only<00:12:08.079><c> generation</c><00:12:08.519><c> one</c><00:12:08.800><c> cryptography</c><00:12:09.720><c> and</c>

00:12:09.949 --> 00:12:09.959 align:start position:0%
only generation one cryptography and
 

00:12:09.959 --> 00:12:14.189 align:start position:0%
only generation one cryptography and
even<00:12:10.399><c> some</c><00:12:10.639><c> forms</c><00:12:11.079><c> of</c>

00:12:14.189 --> 00:12:14.199 align:start position:0%
 
 

00:12:14.199 --> 00:12:16.189 align:start position:0%
 
consensus<00:12:15.199><c> another</c><00:12:15.440><c> issue</c><00:12:15.680><c> that</c><00:12:15.839><c> really</c>

00:12:16.189 --> 00:12:16.199 align:start position:0%
consensus another issue that really
 

00:12:16.199 --> 00:12:18.110 align:start position:0%
consensus another issue that really
shines<00:12:16.519><c> a</c><00:12:16.680><c> light</c><00:12:16.959><c> on</c><00:12:17.079><c> the</c><00:12:17.279><c> fundamental</c>

00:12:18.110 --> 00:12:18.120 align:start position:0%
shines a light on the fundamental
 

00:12:18.120 --> 00:12:19.910 align:start position:0%
shines a light on the fundamental
limitations<00:12:18.720><c> of</c><00:12:19.040><c> of</c><00:12:19.160><c> our</c><00:12:19.320><c> existing</c><00:12:19.639><c> tool</c>

00:12:19.910 --> 00:12:19.920 align:start position:0%
limitations of of our existing tool
 

00:12:19.920 --> 00:12:22.750 align:start position:0%
limitations of of our existing tool
Stacks<00:12:20.680><c> is</c><00:12:21.279><c> some</c><00:12:21.600><c> applications</c><00:12:22.279><c> have</c><00:12:22.519><c> what</c><00:12:22.639><c> we</c>

00:12:22.750 --> 00:12:22.760 align:start position:0%
Stacks is some applications have what we
 

00:12:22.760 --> 00:12:24.990 align:start position:0%
Stacks is some applications have what we
might<00:12:22.920><c> think</c><00:12:23.079><c> of</c><00:12:23.279><c> as</c><00:12:23.600><c> private</c><00:12:24.160><c> Global</c><00:12:24.600><c> state</c>

00:12:24.990 --> 00:12:25.000 align:start position:0%
might think of as private Global state
 

00:12:25.000 --> 00:12:26.470 align:start position:0%
might think of as private Global state
so<00:12:25.199><c> this</c><00:12:25.279><c> is</c><00:12:25.560><c> State</c><00:12:25.920><c> that's</c><00:12:26.120><c> part</c><00:12:26.240><c> of</c><00:12:26.360><c> the</c>

00:12:26.470 --> 00:12:26.480 align:start position:0%
so this is State that's part of the
 

00:12:26.480 --> 00:12:28.750 align:start position:0%
so this is State that's part of the
application<00:12:27.320><c> that</c><00:12:27.440><c> is</c><00:12:27.600><c> computed</c><00:12:28.079><c> on</c><00:12:28.480><c> and</c><00:12:28.600><c> is</c>

00:12:28.750 --> 00:12:28.760 align:start position:0%
application that is computed on and is
 

00:12:28.760 --> 00:12:30.189 align:start position:0%
application that is computed on and is
necessary<00:12:29.279><c> for</c><00:12:29.440><c> the</c><00:12:29.560><c> operation</c><00:12:29.920><c> of</c><00:12:30.040><c> the</c>

00:12:30.189 --> 00:12:30.199 align:start position:0%
necessary for the operation of the
 

00:12:30.199 --> 00:12:33.230 align:start position:0%
necessary for the operation of the
system<00:12:31.079><c> but</c><00:12:31.279><c> which</c><00:12:31.560><c> no</c><00:12:31.959><c> user</c><00:12:32.360><c> of</c><00:12:32.519><c> the</c><00:12:32.680><c> system</c>

00:12:33.230 --> 00:12:33.240 align:start position:0%
system but which no user of the system
 

00:12:33.240 --> 00:12:35.990 align:start position:0%
system but which no user of the system
knows<00:12:33.680><c> or</c><00:12:34.199><c> owns</c><00:12:35.199><c> so</c><00:12:35.320><c> you</c><00:12:35.399><c> can</c><00:12:35.519><c> imagine</c><00:12:35.839><c> having</c>

00:12:35.990 --> 00:12:36.000 align:start position:0%
knows or owns so you can imagine having
 

00:12:36.000 --> 00:12:39.590 align:start position:0%
knows or owns so you can imagine having
a<00:12:36.199><c> bit</c><00:12:36.839><c> in</c><00:12:37.480><c> this</c><00:12:38.360><c> system</c><00:12:38.800><c> that</c><00:12:39.279><c> doesn't</c>

00:12:39.590 --> 00:12:39.600 align:start position:0%
a bit in this system that doesn't
 

00:12:39.600 --> 00:12:40.790 align:start position:0%
a bit in this system that doesn't
actually<00:12:39.800><c> physically</c><00:12:40.120><c> live</c><00:12:40.279><c> on</c><00:12:40.399><c> anybody's</c>

00:12:40.790 --> 00:12:40.800 align:start position:0%
actually physically live on anybody's
 

00:12:40.800 --> 00:12:42.750 align:start position:0%
actually physically live on anybody's
computer<00:12:41.079><c> but</c><00:12:41.199><c> is</c><00:12:41.279><c> a</c><00:12:41.480><c> necessary</c><00:12:42.040><c> input</c><00:12:42.560><c> to</c>

00:12:42.750 --> 00:12:42.760 align:start position:0%
computer but is a necessary input to
 

00:12:42.760 --> 00:12:43.829 align:start position:0%
computer but is a necessary input to
some<00:12:42.880><c> of</c><00:12:43.000><c> the</c><00:12:43.120><c> computations</c><00:12:43.600><c> that</c><00:12:43.720><c> are</c>

00:12:43.829 --> 00:12:43.839 align:start position:0%
some of the computations that are
 

00:12:43.839 --> 00:12:46.189 align:start position:0%
some of the computations that are
running<00:12:44.680><c> you</c><00:12:44.800><c> know</c><00:12:44.880><c> in</c><00:12:44.959><c> a</c><00:12:45.160><c> social</c><00:12:45.399><c> media</c><00:12:46.040><c> you</c>

00:12:46.189 --> 00:12:46.199 align:start position:0%
running you know in a social media you
 

00:12:46.199 --> 00:12:48.550 align:start position:0%
running you know in a social media you
might<00:12:46.480><c> have</c><00:12:46.920><c> a</c><00:12:47.120><c> list</c><00:12:47.399><c> of</c><00:12:47.560><c> all</c><00:12:47.680><c> the</c><00:12:47.800><c> user</c><00:12:48.120><c> IDs</c>

00:12:48.550 --> 00:12:48.560 align:start position:0%
might have a list of all the user IDs
 

00:12:48.560 --> 00:12:50.629 align:start position:0%
might have a list of all the user IDs
that<00:12:48.720><c> have</c><00:12:48.880><c> been</c><00:12:49.320><c> reported</c><00:12:49.880><c> at</c><00:12:50.000><c> least</c><00:12:50.320><c> three</c>

00:12:50.629 --> 00:12:50.639 align:start position:0%
that have been reported at least three
 

00:12:50.639 --> 00:12:52.629 align:start position:0%
that have been reported at least three
times<00:12:51.000><c> for</c><00:12:51.360><c> bad</c><00:12:51.600><c> behavior</c><00:12:52.040><c> or</c><00:12:52.199><c> something</c><00:12:52.519><c> like</c>

00:12:52.629 --> 00:12:52.639 align:start position:0%
times for bad behavior or something like
 

00:12:52.639 --> 00:12:56.069 align:start position:0%
times for bad behavior or something like
the<00:12:52.760><c> naughty</c><00:12:53.320><c> list</c><00:12:54.320><c> and</c><00:12:54.959><c> one</c><00:12:55.120><c> of</c><00:12:55.320><c> the</c><00:12:55.680><c> issues</c>

00:12:56.069 --> 00:12:56.079 align:start position:0%
the naughty list and one of the issues
 

00:12:56.079 --> 00:12:57.470 align:start position:0%
the naughty list and one of the issues
here<00:12:56.320><c> is</c><00:12:56.519><c> well</c><00:12:56.639><c> if</c><00:12:56.720><c> you</c><00:12:56.800><c> try</c><00:12:56.959><c> to</c><00:12:57.040><c> emulate</c><00:12:57.399><c> this</c>

00:12:57.470 --> 00:12:57.480 align:start position:0%
here is well if you try to emulate this
 

00:12:57.480 --> 00:12:59.670 align:start position:0%
here is well if you try to emulate this
in<00:12:57.560><c> a</c><00:12:57.680><c> decentralized</c><00:12:58.320><c> fashion</c><00:12:58.800><c> and</c><00:12:59.240><c> nobody</c>

00:12:59.670 --> 00:12:59.680 align:start position:0%
in a decentralized fashion and nobody
 

00:12:59.680 --> 00:13:01.870 align:start position:0%
in a decentralized fashion and nobody
has<00:13:00.040><c> that</c><00:13:00.320><c> array</c><00:13:00.839><c> stored</c><00:13:01.240><c> locally</c><00:13:01.639><c> but</c><00:13:01.720><c> you</c>

00:13:01.870 --> 00:13:01.880 align:start position:0%
has that array stored locally but you
 

00:13:01.880 --> 00:13:03.150 align:start position:0%
has that array stored locally but you
still<00:13:02.079><c> want</c><00:13:02.240><c> to</c><00:13:02.360><c> be</c><00:13:02.480><c> able</c><00:13:02.639><c> to</c><00:13:02.800><c> perform</c>

00:13:03.150 --> 00:13:03.160 align:start position:0%
still want to be able to perform
 

00:13:03.160 --> 00:13:05.670 align:start position:0%
still want to be able to perform
computations<00:13:03.680><c> on</c><00:13:03.800><c> that</c><00:13:04.040><c> well</c><00:13:04.320><c> that</c><00:13:04.440><c> seems</c>

00:13:05.670 --> 00:13:05.680 align:start position:0%
computations on that well that seems
 

00:13:05.680 --> 00:13:08.670 align:start position:0%
computations on that well that seems
paradoxical<00:13:06.680><c> another</c><00:13:07.519><c> pretty</c><00:13:07.959><c> clear</c><00:13:08.320><c> example</c>

00:13:08.670 --> 00:13:08.680 align:start position:0%
paradoxical another pretty clear example
 

00:13:08.680 --> 00:13:10.949 align:start position:0%
paradoxical another pretty clear example
of<00:13:08.839><c> this</c><00:13:09.040><c> is</c><00:13:09.160><c> in</c><00:13:09.399><c> some</c><00:13:09.639><c> kinds</c><00:13:09.839><c> of</c><00:13:10.040><c> games</c><00:13:10.760><c> um</c><00:13:10.880><c> you</c>

00:13:10.949 --> 00:13:10.959 align:start position:0%
of this is in some kinds of games um you
 

00:13:10.959 --> 00:13:12.310 align:start position:0%
of this is in some kinds of games um you
might<00:13:11.120><c> have</c><00:13:11.279><c> strategy</c><00:13:11.720><c> games</c><00:13:11.959><c> where</c><00:13:12.120><c> there's</c>

00:13:12.310 --> 00:13:12.320 align:start position:0%
might have strategy games where there's
 

00:13:12.320 --> 00:13:14.310 align:start position:0%
might have strategy games where there's
multiple<00:13:12.680><c> players</c><00:13:13.320><c> each</c><00:13:13.519><c> player</c><00:13:13.800><c> can</c><00:13:13.959><c> see</c>

00:13:14.310 --> 00:13:14.320 align:start position:0%
multiple players each player can see
 

00:13:14.320 --> 00:13:17.470 align:start position:0%
multiple players each player can see
some<00:13:14.880><c> part</c><00:13:15.399><c> of</c><00:13:15.560><c> the</c><00:13:15.680><c> world</c><00:13:15.959><c> or</c><00:13:16.079><c> the</c><00:13:16.240><c> global</c><00:13:16.600><c> map</c>

00:13:17.470 --> 00:13:17.480 align:start position:0%
some part of the world or the global map
 

00:13:17.480 --> 00:13:18.829 align:start position:0%
some part of the world or the global map
but<00:13:17.639><c> there's</c><00:13:17.839><c> also</c><00:13:18.079><c> stuff</c><00:13:18.320><c> going</c><00:13:18.480><c> on</c><00:13:18.639><c> in</c><00:13:18.760><c> the</c>

00:13:18.829 --> 00:13:18.839 align:start position:0%
but there's also stuff going on in the
 

00:13:18.839 --> 00:13:20.949 align:start position:0%
but there's also stuff going on in the
fog<00:13:19.160><c> of</c><00:13:19.320><c> war</c><00:13:19.720><c> that</c><00:13:19.920><c> nobody</c><00:13:20.279><c> has</c><00:13:20.519><c> access</c><00:13:20.760><c> to</c>

00:13:20.949 --> 00:13:20.959 align:start position:0%
fog of war that nobody has access to
 

00:13:20.959 --> 00:13:22.829 align:start position:0%
fog of war that nobody has access to
maybe<00:13:21.199><c> NPCs</c><00:13:21.720><c> are</c><00:13:21.880><c> moving</c><00:13:22.199><c> around</c><00:13:22.480><c> or</c><00:13:22.639><c> some</c>

00:13:22.829 --> 00:13:22.839 align:start position:0%
maybe NPCs are moving around or some
 

00:13:22.839 --> 00:13:24.470 align:start position:0%
maybe NPCs are moving around or some
processes<00:13:23.240><c> are</c><00:13:23.399><c> running</c><00:13:24.000><c> and</c><00:13:24.079><c> so</c><00:13:24.240><c> these</c><00:13:24.360><c> are</c>

00:13:24.470 --> 00:13:24.480 align:start position:0%
processes are running and so these are
 

00:13:24.480 --> 00:13:26.670 align:start position:0%
processes are running and so these are
things<00:13:24.680><c> that</c><00:13:24.800><c> only</c><00:13:25.000><c> the</c><00:13:25.199><c> server</c><00:13:25.680><c> knows</c><00:13:26.480><c> but</c>

00:13:26.670 --> 00:13:26.680 align:start position:0%
things that only the server knows but
 

00:13:26.680 --> 00:13:28.910 align:start position:0%
things that only the server knows but
because<00:13:26.959><c> they</c><00:13:27.120><c> can</c><00:13:27.360><c> eventually</c><00:13:28.040><c> interact</c>

00:13:28.910 --> 00:13:28.920 align:start position:0%
because they can eventually interact
 

00:13:28.920 --> 00:13:31.509 align:start position:0%
because they can eventually interact
with<00:13:29.160><c> with</c><00:13:29.480><c> a</c><00:13:29.639><c> given</c><00:13:29.880><c> player</c><00:13:30.320><c> State</c><00:13:31.199><c> you</c><00:13:31.360><c> might</c>

00:13:31.509 --> 00:13:31.519 align:start position:0%
with with a given player State you might
 

00:13:31.519 --> 00:13:33.790 align:start position:0%
with with a given player State you might
need<00:13:31.680><c> to</c><00:13:31.880><c> ensure</c><00:13:32.560><c> that</c><00:13:32.760><c> somehow</c><00:13:33.320><c> this</c><00:13:33.519><c> state</c>

00:13:33.790 --> 00:13:33.800 align:start position:0%
need to ensure that somehow this state
 

00:13:33.800 --> 00:13:35.750 align:start position:0%
need to ensure that somehow this state
is<00:13:33.920><c> still</c><00:13:34.160><c> being</c><00:13:34.399><c> updated</c><00:13:34.800><c> and</c><00:13:35.000><c> operated</c><00:13:35.399><c> on</c>

00:13:35.750 --> 00:13:35.760 align:start position:0%
is still being updated and operated on
 

00:13:35.760 --> 00:13:37.430 align:start position:0%
is still being updated and operated on
in<00:13:35.880><c> a</c><00:13:36.000><c> consistent</c><00:13:36.440><c> way</c><00:13:36.800><c> despite</c><00:13:37.160><c> the</c><00:13:37.279><c> fact</c>

00:13:37.430 --> 00:13:37.440 align:start position:0%
in a consistent way despite the fact
 

00:13:37.440 --> 00:13:39.910 align:start position:0%
in a consistent way despite the fact
that<00:13:37.560><c> it</c><00:13:37.680><c> doesn't</c><00:13:38.160><c> actually</c><00:13:38.560><c> live</c>

00:13:39.910 --> 00:13:39.920 align:start position:0%
that it doesn't actually live
 

00:13:39.920 --> 00:13:42.389 align:start position:0%
that it doesn't actually live
anywhere<00:13:40.920><c> so</c><00:13:41.079><c> in</c><00:13:41.199><c> short</c><00:13:41.480><c> you</c><00:13:41.600><c> know</c><00:13:42.040><c> why</c><00:13:42.160><c> is</c><00:13:42.240><c> it</c>

00:13:42.389 --> 00:13:42.399 align:start position:0%
anywhere so in short you know why is it
 

00:13:42.399 --> 00:13:43.870 align:start position:0%
anywhere so in short you know why is it
hard<00:13:42.560><c> to</c><00:13:42.720><c> be</c><00:13:42.959><c> to</c><00:13:43.120><c> build</c><00:13:43.399><c> something</c><00:13:43.639><c> like</c><00:13:43.760><c> a</c>

00:13:43.870 --> 00:13:43.880 align:start position:0%
hard to be to build something like a
 

00:13:43.880 --> 00:13:45.670 align:start position:0%
hard to be to build something like a
decentralized<00:13:44.440><c> Facebook</c><00:13:45.079><c> well</c><00:13:45.240><c> first</c><00:13:45.440><c> off</c><00:13:45.560><c> if</c>

00:13:45.670 --> 00:13:45.680 align:start position:0%
decentralized Facebook well first off if
 

00:13:45.680 --> 00:13:47.310 align:start position:0%
decentralized Facebook well first off if
you<00:13:45.800><c> have</c><00:13:45.880><c> a</c><00:13:46.040><c> transparent</c><00:13:46.560><c> data</c><00:13:46.800><c> layer</c>

00:13:47.310 --> 00:13:47.320 align:start position:0%
you have a transparent data layer
 

00:13:47.320 --> 00:13:49.269 align:start position:0%
you have a transparent data layer
individuals<00:13:47.920><c> can't</c><00:13:48.199><c> really</c><00:13:48.560><c> have</c><00:13:48.760><c> their</c><00:13:48.920><c> own</c>

00:13:49.269 --> 00:13:49.279 align:start position:0%
individuals can't really have their own
 

00:13:49.279 --> 00:13:51.749 align:start position:0%
individuals can't really have their own
State<00:13:50.199><c> a</c><00:13:50.320><c> lot</c><00:13:50.440><c> of</c><00:13:50.560><c> decentralized</c><00:13:51.160><c> systems</c>

00:13:51.749 --> 00:13:51.759 align:start position:0%
State a lot of decentralized systems
 

00:13:51.759 --> 00:13:53.189 align:start position:0%
State a lot of decentralized systems
need<00:13:51.959><c> their</c><00:13:52.120><c> state</c><00:13:52.320><c> to</c><00:13:52.399><c> be</c><00:13:52.560><c> public</c><00:13:52.839><c> so</c><00:13:52.959><c> it</c><00:13:53.079><c> can</c>

00:13:53.189 --> 00:13:53.199 align:start position:0%
need their state to be public so it can
 

00:13:53.199 --> 00:13:55.990 align:start position:0%
need their state to be public so it can
be<00:13:53.680><c> verified</c><00:13:54.680><c> and</c><00:13:54.800><c> the</c><00:13:54.959><c> system</c><00:13:55.320><c> itself</c><00:13:55.720><c> might</c>

00:13:55.990 --> 00:13:56.000 align:start position:0%
be verified and the system itself might
 

00:13:56.000 --> 00:13:58.189 align:start position:0%
be verified and the system itself might
also<00:13:56.440><c> have</c><00:13:56.720><c> some</c><00:13:56.920><c> notion</c><00:13:57.199><c> of</c><00:13:57.399><c> global</c><00:13:57.839><c> private</c>

00:13:58.189 --> 00:13:58.199 align:start position:0%
also have some notion of global private
 

00:13:58.199 --> 00:14:00.269 align:start position:0%
also have some notion of global private
State<00:13:58.680><c> and</c><00:13:58.759><c> it</c><00:13:59.079><c> seems</c><00:13:59.360><c> almost</c><00:13:59.600><c> paradoxical</c><00:14:00.160><c> to</c>

00:14:00.269 --> 00:14:00.279 align:start position:0%
State and it seems almost paradoxical to
 

00:14:00.279 --> 00:14:01.829 align:start position:0%
State and it seems almost paradoxical to
imagine<00:14:00.600><c> a</c><00:14:00.720><c> system</c><00:14:01.000><c> made</c><00:14:01.160><c> up</c><00:14:01.320><c> of</c><00:14:01.399><c> a</c><00:14:01.519><c> bunch</c><00:14:01.720><c> of</c>

00:14:01.829 --> 00:14:01.839 align:start position:0%
imagine a system made up of a bunch of
 

00:14:01.839 --> 00:14:04.269 align:start position:0%
imagine a system made up of a bunch of
users<00:14:02.480><c> that's</c><00:14:02.680><c> performing</c><00:14:03.120><c> a</c><00:14:03.320><c> computation</c><00:14:04.120><c> on</c>

00:14:04.269 --> 00:14:04.279 align:start position:0%
users that's performing a computation on
 

00:14:04.279 --> 00:14:07.069 align:start position:0%
users that's performing a computation on
a<00:14:04.440><c> variable</c><00:14:04.920><c> that</c><00:14:05.120><c> no</c><00:14:05.399><c> single</c><00:14:05.800><c> person</c><00:14:06.399><c> owns</c><00:14:06.880><c> or</c>

00:14:07.069 --> 00:14:07.079 align:start position:0%
a variable that no single person owns or
 

00:14:07.079 --> 00:14:08.430 align:start position:0%
a variable that no single person owns or
can<00:14:07.279><c> read</c><00:14:07.519><c> or</c>

00:14:08.430 --> 00:14:08.440 align:start position:0%
can read or
 

00:14:08.440 --> 00:14:11.030 align:start position:0%
can read or
has<00:14:09.440><c> so</c><00:14:09.600><c> enter</c><00:14:09.880><c> programmable</c>

00:14:11.030 --> 00:14:11.040 align:start position:0%
has so enter programmable
 

00:14:11.040 --> 00:14:14.069 align:start position:0%
has so enter programmable
cryptography<00:14:12.040><c> programmable</c><00:14:13.079><c> cryptography</c>

00:14:14.069 --> 00:14:14.079 align:start position:0%
cryptography programmable cryptography
 

00:14:14.079 --> 00:14:16.230 align:start position:0%
cryptography programmable cryptography
has<00:14:14.279><c> the</c><00:14:14.440><c> ability</c><00:14:15.079><c> to</c><00:14:15.320><c> potentially</c><00:14:15.800><c> start</c><00:14:16.040><c> to</c>

00:14:16.230 --> 00:14:16.240 align:start position:0%
has the ability to potentially start to
 

00:14:16.240 --> 00:14:17.990 align:start position:0%
has the ability to potentially start to
emulate<00:14:16.639><c> some</c><00:14:16.759><c> of</c><00:14:16.920><c> these</c>

00:14:17.990 --> 00:14:18.000 align:start position:0%
emulate some of these
 

00:14:18.000 --> 00:14:20.509 align:start position:0%
emulate some of these
capabilities<00:14:19.000><c> if</c><00:14:19.120><c> we</c><00:14:19.279><c> break</c><00:14:19.600><c> down</c><00:14:20.240><c> what</c><00:14:20.399><c> we</c>

00:14:20.509 --> 00:14:20.519 align:start position:0%
capabilities if we break down what we
 

00:14:20.519 --> 00:14:22.670 align:start position:0%
capabilities if we break down what we
would<00:14:20.720><c> need</c><00:14:21.240><c> from</c><00:14:21.600><c> our</c><00:14:21.959><c> multi-party</c>

00:14:22.670 --> 00:14:22.680 align:start position:0%
would need from our multi-party
 

00:14:22.680 --> 00:14:24.990 align:start position:0%
would need from our multi-party
programming<00:14:23.279><c> model</c><00:14:24.279><c> we</c><00:14:24.399><c> can</c><00:14:24.560><c> write</c><00:14:24.720><c> down</c><00:14:24.880><c> a</c>

00:14:24.990 --> 00:14:25.000 align:start position:0%
programming model we can write down a
 

00:14:25.000 --> 00:14:26.430 align:start position:0%
programming model we can write down a
couple<00:14:25.240><c> of</c><00:14:25.440><c> things</c><00:14:25.680><c> that</c><00:14:25.839><c> we</c><00:14:25.959><c> would</c><00:14:26.120><c> need</c><00:14:26.279><c> to</c>

00:14:26.430 --> 00:14:26.440 align:start position:0%
couple of things that we would need to
 

00:14:26.440 --> 00:14:28.310 align:start position:0%
couple of things that we would need to
have<00:14:26.680><c> happen</c><00:14:26.959><c> in</c><00:14:27.040><c> order</c><00:14:27.279><c> to</c><00:14:27.399><c> be</c><00:14:27.519><c> able</c><00:14:27.759><c> to</c>

00:14:28.310 --> 00:14:28.320 align:start position:0%
have happen in order to be able to
 

00:14:28.320 --> 00:14:30.189 align:start position:0%
have happen in order to be able to
emulate<00:14:28.720><c> these</c><00:14:29.120><c> capabilities</c><00:14:29.680><c> in</c><00:14:29.800><c> their</c><00:14:29.959><c> full</c>

00:14:30.189 --> 00:14:30.199 align:start position:0%
emulate these capabilities in their full
 

00:14:30.199 --> 00:14:32.350 align:start position:0%
emulate these capabilities in their full
generality<00:14:31.199><c> we</c><00:14:31.320><c> would</c><00:14:31.480><c> need</c><00:14:31.720><c> verifiable</c>

00:14:32.350 --> 00:14:32.360 align:start position:0%
generality we would need verifiable
 

00:14:32.360 --> 00:14:34.829 align:start position:0%
generality we would need verifiable
computation<00:14:33.279><c> because</c><00:14:33.959><c> you</c><00:14:34.079><c> know</c><00:14:34.320><c> rather</c><00:14:34.600><c> than</c>

00:14:34.829 --> 00:14:34.839 align:start position:0%
computation because you know rather than
 

00:14:34.839 --> 00:14:37.150 align:start position:0%
computation because you know rather than
one<00:14:35.120><c> trusted</c><00:14:35.639><c> actor</c><00:14:35.920><c> running</c><00:14:36.199><c> the</c><00:14:36.360><c> program</c><00:14:36.959><c> we</c>

00:14:37.150 --> 00:14:37.160 align:start position:0%
one trusted actor running the program we
 

00:14:37.160 --> 00:14:38.550 align:start position:0%
one trusted actor running the program we
might<00:14:37.360><c> have</c><00:14:37.480><c> this</c><00:14:37.600><c> world</c><00:14:37.880><c> where</c><00:14:38.079><c> programs</c><00:14:38.440><c> can</c>

00:14:38.550 --> 00:14:38.560 align:start position:0%
might have this world where programs can
 

00:14:38.560 --> 00:14:39.990 align:start position:0%
might have this world where programs can
be<00:14:38.680><c> run</c><00:14:38.959><c> across</c><00:14:39.320><c> multiple</c><00:14:39.720><c> different</c>

00:14:39.990 --> 00:14:40.000 align:start position:0%
be run across multiple different
 

00:14:40.000 --> 00:14:42.110 align:start position:0%
be run across multiple different
computers<00:14:40.720><c> or</c><00:14:41.000><c> by</c><00:14:41.160><c> someone</c><00:14:41.519><c> who</c><00:14:41.759><c> you</c><00:14:41.880><c> don't</c>

00:14:42.110 --> 00:14:42.120 align:start position:0%
computers or by someone who you don't
 

00:14:42.120 --> 00:14:43.189 align:start position:0%
computers or by someone who you don't
even<00:14:42.279><c> know</c><00:14:42.519><c> and</c><00:14:42.600><c> you</c><00:14:42.720><c> don't</c><00:14:42.880><c> even</c><00:14:43.040><c> have</c><00:14:43.120><c> to</c>

00:14:43.189 --> 00:14:43.199 align:start position:0%
even know and you don't even have to
 

00:14:43.199 --> 00:14:45.269 align:start position:0%
even know and you don't even have to
care<00:14:43.360><c> about</c><00:14:43.480><c> who's</c><00:14:43.680><c> running</c><00:14:43.880><c> the</c><00:14:44.279><c> computation</c>

00:14:45.269 --> 00:14:45.279 align:start position:0%
care about who's running the computation
 

00:14:45.279 --> 00:14:47.269 align:start position:0%
care about who's running the computation
we'll<00:14:45.440><c> need</c><00:14:45.639><c> execution</c><00:14:46.040><c> on</c><00:14:46.240><c> private</c><00:14:46.560><c> State</c>

00:14:47.269 --> 00:14:47.279 align:start position:0%
we'll need execution on private State
 

00:14:47.279 --> 00:14:49.509 align:start position:0%
we'll need execution on private State
because<00:14:48.120><c> if</c><00:14:48.480><c> that</c><00:14:48.720><c> program</c><00:14:49.000><c> is</c><00:14:49.160><c> physically</c>

00:14:49.509 --> 00:14:49.519 align:start position:0%
because if that program is physically
 

00:14:49.519 --> 00:14:51.470 align:start position:0%
because if that program is physically
running<00:14:49.920><c> somewhere</c><00:14:50.839><c> it</c><00:14:50.959><c> has</c><00:14:51.079><c> to</c><00:14:51.160><c> be</c><00:14:51.279><c> running</c>

00:14:51.470 --> 00:14:51.480 align:start position:0%
running somewhere it has to be running
 

00:14:51.480 --> 00:14:52.749 align:start position:0%
running somewhere it has to be running
on<00:14:51.639><c> state</c><00:14:51.880><c> that</c><00:14:52.000><c> might</c><00:14:52.160><c> exist</c><00:14:52.360><c> in</c><00:14:52.480><c> some</c><00:14:52.600><c> other</c>

00:14:52.749 --> 00:14:52.759 align:start position:0%
on state that might exist in some other
 

00:14:52.759 --> 00:14:54.470 align:start position:0%
on state that might exist in some other
part<00:14:52.880><c> of</c><00:14:53.000><c> the</c><00:14:53.120><c> network</c><00:14:53.880><c> that</c><00:14:54.160><c> the</c><00:14:54.240><c> person</c>

00:14:54.470 --> 00:14:54.480 align:start position:0%
part of the network that the person
 

00:14:54.480 --> 00:14:55.749 align:start position:0%
part of the network that the person
who's<00:14:54.680><c> executing</c><00:14:55.079><c> the</c><00:14:55.199><c> code</c><00:14:55.440><c> doesn't</c>

00:14:55.749 --> 00:14:55.759 align:start position:0%
who's executing the code doesn't
 

00:14:55.759 --> 00:14:57.189 align:start position:0%
who's executing the code doesn't
actually<00:14:56.040><c> have</c><00:14:56.279><c> access</c><00:14:56.560><c> to</c><00:14:56.720><c> the</c><00:14:56.839><c> internal</c>

00:14:57.189 --> 00:14:57.199 align:start position:0%
actually have access to the internal
 

00:14:57.199 --> 00:14:59.910 align:start position:0%
actually have access to the internal
state<00:14:57.440><c> of</c><00:14:58.279><c> we</c><00:14:58.399><c> want</c><00:14:58.600><c> data</c><00:14:59.040><c> interoperability</c>

00:14:59.910 --> 00:14:59.920 align:start position:0%
state of we want data interoperability
 

00:14:59.920 --> 00:15:01.710 align:start position:0%
state of we want data interoperability
we<00:15:00.040><c> want</c><00:15:00.240><c> the</c><00:15:00.399><c> ability</c><00:15:00.800><c> for</c><00:15:01.320><c> you</c><00:15:01.440><c> know</c><00:15:01.600><c> the</c>

00:15:01.710 --> 00:15:01.720 align:start position:0%
we want the ability for you know the
 

00:15:01.720 --> 00:15:04.030 align:start position:0%
we want the ability for you know the
outputs<00:15:02.120><c> of</c><00:15:02.320><c> certain</c><00:15:02.800><c> programs</c><00:15:03.360><c> or</c><00:15:03.600><c> certain</c>

00:15:04.030 --> 00:15:04.040 align:start position:0%
outputs of certain programs or certain
 

00:15:04.040 --> 00:15:06.550 align:start position:0%
outputs of certain programs or certain
services<00:15:04.839><c> to</c><00:15:04.959><c> be</c><00:15:05.120><c> usable</c><00:15:05.519><c> in</c><00:15:05.680><c> other</c><00:15:05.880><c> ones</c><00:15:06.440><c> we</c>

00:15:06.550 --> 00:15:06.560 align:start position:0%
services to be usable in other ones we
 

00:15:06.560 --> 00:15:08.590 align:start position:0%
services to be usable in other ones we
want<00:15:06.880><c> consensus</c><00:15:07.800><c> so</c><00:15:07.920><c> that</c><00:15:08.079><c> everybody</c><00:15:08.440><c> can</c>

00:15:08.590 --> 00:15:08.600 align:start position:0%
want consensus so that everybody can
 

00:15:08.600 --> 00:15:10.430 align:start position:0%
want consensus so that everybody can
agree<00:15:08.880><c> on</c><00:15:08.959><c> the</c><00:15:09.120><c> canonical</c><00:15:09.600><c> program</c><00:15:10.079><c> State</c><00:15:10.320><c> or</c>

00:15:10.430 --> 00:15:10.440 align:start position:0%
agree on the canonical program State or
 

00:15:10.440 --> 00:15:11.829 align:start position:0%
agree on the canonical program State or
the<00:15:10.519><c> canonical</c><00:15:11.000><c> state</c><00:15:11.240><c> of</c><00:15:11.360><c> a</c><00:15:11.480><c> given</c>

00:15:11.829 --> 00:15:11.839 align:start position:0%
the canonical state of a given
 

00:15:11.839 --> 00:15:14.030 align:start position:0%
the canonical state of a given
multiplayer<00:15:12.480><c> service</c><00:15:13.360><c> and</c><00:15:13.480><c> we</c><00:15:13.600><c> want</c><00:15:13.800><c> non-</c>

00:15:14.030 --> 00:15:14.040 align:start position:0%
multiplayer service and we want non-
 

00:15:14.040 --> 00:15:15.629 align:start position:0%
multiplayer service and we want non-
interactivity<00:15:14.680><c> to</c><00:15:14.759><c> be</c><00:15:14.839><c> able</c><00:15:15.079><c> to</c><00:15:15.160><c> scale</c><00:15:15.480><c> to</c>

00:15:15.629 --> 00:15:15.639 align:start position:0%
interactivity to be able to scale to
 

00:15:15.639 --> 00:15:17.470 align:start position:0%
interactivity to be able to scale to
billions<00:15:16.000><c> of</c>

00:15:17.470 --> 00:15:17.480 align:start position:0%
billions of
 

00:15:17.480 --> 00:15:20.430 align:start position:0%
billions of
participants<00:15:18.480><c> a</c><00:15:18.600><c> lot</c><00:15:18.880><c> of</c><00:15:19.120><c> this</c><00:15:19.360><c> mental</c><00:15:19.720><c> model</c>

00:15:20.430 --> 00:15:20.440 align:start position:0%
participants a lot of this mental model
 

00:15:20.440 --> 00:15:22.710 align:start position:0%
participants a lot of this mental model
is<00:15:20.800><c> spiritually</c><00:15:21.320><c> very</c><00:15:21.480><c> similar</c><00:15:21.880><c> to</c><00:15:22.480><c> uh</c><00:15:22.560><c> what</c>

00:15:22.710 --> 00:15:22.720 align:start position:0%
is spiritually very similar to uh what
 

00:15:22.720 --> 00:15:24.230 align:start position:0%
is spiritually very similar to uh what
vital<00:15:23.120><c> discussed</c><00:15:23.440><c> in</c><00:15:23.600><c> one</c><00:15:23.720><c> of</c><00:15:23.839><c> his</c><00:15:23.959><c> recent</c>

00:15:24.230 --> 00:15:24.240 align:start position:0%
vital discussed in one of his recent
 

00:15:24.240 --> 00:15:26.310 align:start position:0%
vital discussed in one of his recent
blog<00:15:24.519><c> posts</c><00:15:25.199><c> uh</c><00:15:25.279><c> with</c><00:15:25.399><c> the</c><00:15:25.560><c> three</c><00:15:25.880><c> Egyptian</c>

00:15:26.310 --> 00:15:26.320 align:start position:0%
blog posts uh with the three Egyptian
 

00:15:26.320 --> 00:15:28.710 align:start position:0%
blog posts uh with the three Egyptian
God<00:15:26.720><c> protocols</c><00:15:27.720><c> looking</c><00:15:27.959><c> forward</c><00:15:28.319><c> to</c><00:15:28.440><c> the</c><00:15:28.560><c> far</c>

00:15:28.710 --> 00:15:28.720 align:start position:0%
God protocols looking forward to the far
 

00:15:28.720 --> 00:15:29.670 align:start position:0%
God protocols looking forward to the far
future<00:15:29.079><c> of</c>

00:15:29.670 --> 00:15:29.680 align:start position:0%
future of
 

00:15:29.680 --> 00:15:32.509 align:start position:0%
future of
ethereum<00:15:30.680><c> so</c><00:15:30.880><c> let's</c><00:15:31.079><c> take</c><00:15:31.319><c> a</c><00:15:31.560><c> a</c><00:15:31.720><c> quick</c><00:15:31.959><c> look</c><00:15:32.360><c> at</c>

00:15:32.509 --> 00:15:32.519 align:start position:0%
ethereum so let's take a a quick look at
 

00:15:32.519 --> 00:15:34.350 align:start position:0%
ethereum so let's take a a quick look at
each<00:15:32.680><c> of</c><00:15:32.839><c> these</c><00:15:33.000><c> in</c><00:15:33.160><c> succession</c><00:15:34.040><c> let's</c><00:15:34.240><c> look</c>

00:15:34.350 --> 00:15:34.360 align:start position:0%
each of these in succession let's look
 

00:15:34.360 --> 00:15:36.949 align:start position:0%
each of these in succession let's look
at<00:15:34.480><c> verifiable</c><00:15:35.360><c> computation</c><00:15:36.360><c> so</c><00:15:36.480><c> we</c><00:15:36.600><c> want</c><00:15:36.759><c> to</c>

00:15:36.949 --> 00:15:36.959 align:start position:0%
at verifiable computation so we want to
 

00:15:36.959 --> 00:15:38.829 align:start position:0%
at verifiable computation so we want to
live<00:15:37.079><c> in</c><00:15:37.199><c> a</c><00:15:37.319><c> world</c><00:15:37.920><c> where</c><00:15:38.079><c> we</c><00:15:38.199><c> can</c><00:15:38.399><c> execute</c>

00:15:38.829 --> 00:15:38.839 align:start position:0%
live in a world where we can execute
 

00:15:38.839 --> 00:15:40.590 align:start position:0%
live in a world where we can execute
programs<00:15:39.240><c> over</c><00:15:39.399><c> a</c><00:15:39.560><c> network</c><00:15:40.240><c> and</c><00:15:40.399><c> these</c>

00:15:40.590 --> 00:15:40.600 align:start position:0%
programs over a network and these
 

00:15:40.600 --> 00:15:42.069 align:start position:0%
programs over a network and these
programs<00:15:41.040><c> might</c><00:15:41.160><c> be</c><00:15:41.279><c> running</c><00:15:41.639><c> somewhere</c>

00:15:42.069 --> 00:15:42.079 align:start position:0%
programs might be running somewhere
 

00:15:42.079 --> 00:15:43.590 align:start position:0%
programs might be running somewhere
untrusted<00:15:42.720><c> they</c><00:15:42.839><c> might</c><00:15:42.959><c> be</c><00:15:43.079><c> running</c><00:15:43.360><c> in</c><00:15:43.440><c> a</c>

00:15:43.590 --> 00:15:43.600 align:start position:0%
untrusted they might be running in a
 

00:15:43.600 --> 00:15:45.629 align:start position:0%
untrusted they might be running in a
place<00:15:43.759><c> that</c><00:15:43.880><c> I</c><00:15:44.000><c> can't</c><00:15:44.160><c> determine</c><00:15:44.600><c> in</c><00:15:45.120><c> you</c><00:15:45.199><c> know</c>

00:15:45.629 --> 00:15:45.639 align:start position:0%
place that I can't determine in you know
 

00:15:45.639 --> 00:15:48.069 align:start position:0%
place that I can't determine in you know
in<00:15:45.800><c> advance</c><00:15:46.240><c> ahead</c><00:15:46.440><c> of</c><00:15:46.600><c> time</c><00:15:47.440><c> um</c><00:15:47.800><c> and</c><00:15:47.920><c> we</c>

00:15:48.069 --> 00:15:48.079 align:start position:0%
in advance ahead of time um and we
 

00:15:48.079 --> 00:15:49.590 align:start position:0%
in advance ahead of time um and we
somehow<00:15:48.440><c> want</c><00:15:48.600><c> to</c><00:15:48.720><c> still</c><00:15:48.959><c> know</c><00:15:49.199><c> that</c><00:15:49.360><c> that</c>

00:15:49.590 --> 00:15:49.600 align:start position:0%
somehow want to still know that that
 

00:15:49.600 --> 00:15:52.269 align:start position:0%
somehow want to still know that that
program<00:15:50.120><c> is</c><00:15:50.480><c> running</c><00:15:51.000><c> correctly</c><00:15:52.000><c> well</c><00:15:52.199><c> this</c>

00:15:52.269 --> 00:15:52.279 align:start position:0%
program is running correctly well this
 

00:15:52.279 --> 00:15:53.870 align:start position:0%
program is running correctly well this
is<00:15:52.399><c> the</c><00:15:52.480><c> sort</c><00:15:52.680><c> of</c><00:15:52.800><c> guarantee</c><00:15:53.319><c> that</c><00:15:53.480><c> general</c>

00:15:53.870 --> 00:15:53.880 align:start position:0%
is the sort of guarantee that general
 

00:15:53.880 --> 00:15:56.509 align:start position:0%
is the sort of guarantee that general
purpose<00:15:54.240><c> zkps</c><00:15:55.199><c> like</c><00:15:55.319><c> snarks</c><00:15:55.800><c> and</c><00:15:55.920><c> Starks</c><00:15:56.360><c> give</c>

00:15:56.509 --> 00:15:56.519 align:start position:0%
purpose zkps like snarks and Starks give
 

00:15:56.519 --> 00:15:59.230 align:start position:0%
purpose zkps like snarks and Starks give
us<00:15:57.399><c> and</c><00:15:57.519><c> we've</c><00:15:57.680><c> seen</c><00:15:57.959><c> phenomenal</c><00:15:58.480><c> progress</c><00:15:59.120><c> in</c>

00:15:59.230 --> 00:15:59.240 align:start position:0%
us and we've seen phenomenal progress in
 

00:15:59.240 --> 00:16:00.629 align:start position:0%
us and we've seen phenomenal progress in
this<00:15:59.399><c> domain</c><00:15:59.759><c> over</c><00:15:59.920><c> the</c><00:16:00.079><c> past</c><00:16:00.279><c> couple</c><00:16:00.480><c> of</c>

00:16:00.629 --> 00:16:00.639 align:start position:0%
this domain over the past couple of
 

00:16:00.639 --> 00:16:02.670 align:start position:0%
this domain over the past couple of
years<00:16:01.279><c> with</c><00:16:01.440><c> the</c><00:16:01.560><c> ability</c><00:16:01.880><c> to</c><00:16:02.079><c> even</c><00:16:02.319><c> run</c>

00:16:02.670 --> 00:16:02.680 align:start position:0%
years with the ability to even run
 

00:16:02.680 --> 00:16:05.550 align:start position:0%
years with the ability to even run
virtual<00:16:03.040><c> machines</c><00:16:03.519><c> performant</c><00:16:04.399><c> inside</c><00:16:05.079><c> of</c>

00:16:05.550 --> 00:16:05.560 align:start position:0%
virtual machines performant inside of
 

00:16:05.560 --> 00:16:07.949 align:start position:0%
virtual machines performant inside of
verifiable<00:16:06.120><c> ZK</c><00:16:06.440><c> snark</c>

00:16:07.949 --> 00:16:07.959 align:start position:0%
verifiable ZK snark
 

00:16:07.959 --> 00:16:10.069 align:start position:0%
verifiable ZK snark
protocols<00:16:08.959><c> in</c><00:16:09.079><c> terms</c><00:16:09.279><c> of</c><00:16:09.480><c> programming</c><00:16:09.880><c> on</c>

00:16:10.069 --> 00:16:10.079 align:start position:0%
protocols in terms of programming on
 

00:16:10.079 --> 00:16:12.230 align:start position:0%
protocols in terms of programming on
private<00:16:10.399><c> State</c><00:16:11.040><c> well</c><00:16:11.240><c> one</c><00:16:11.360><c> of</c><00:16:11.480><c> the</c><00:16:11.639><c> Dual</c>

00:16:12.230 --> 00:16:12.240 align:start position:0%
private State well one of the Dual
 

00:16:12.240 --> 00:16:15.350 align:start position:0%
private State well one of the Dual
problems<00:16:12.959><c> to</c><00:16:13.480><c> the</c><00:16:13.839><c> world</c><00:16:14.319><c> where</c><00:16:14.720><c> we</c><00:16:15.000><c> have</c>

00:16:15.350 --> 00:16:15.360 align:start position:0%
problems to the world where we have
 

00:16:15.360 --> 00:16:16.910 align:start position:0%
problems to the world where we have
multiple<00:16:15.839><c> actors</c><00:16:16.160><c> who</c><00:16:16.279><c> might</c><00:16:16.440><c> be</c><00:16:16.519><c> running</c><00:16:16.800><c> the</c>

00:16:16.910 --> 00:16:16.920 align:start position:0%
multiple actors who might be running the
 

00:16:16.920 --> 00:16:19.509 align:start position:0%
multiple actors who might be running the
program<00:16:17.600><c> is</c><00:16:17.800><c> that</c><00:16:18.639><c> if</c><00:16:18.800><c> those</c><00:16:19.000><c> actors</c><00:16:19.360><c> are</c>

00:16:19.509 --> 00:16:19.519 align:start position:0%
program is that if those actors are
 

00:16:19.519 --> 00:16:20.710 align:start position:0%
program is that if those actors are
running<00:16:19.800><c> the</c><00:16:19.959><c> program</c><00:16:20.279><c> they</c><00:16:20.440><c> might</c><00:16:20.560><c> be</c>

00:16:20.710 --> 00:16:20.720 align:start position:0%
running the program they might be
 

00:16:20.720 --> 00:16:22.430 align:start position:0%
running the program they might be
running<00:16:20.959><c> it</c><00:16:21.120><c> on</c><00:16:21.399><c> state</c><00:16:21.680><c> that</c><00:16:21.800><c> lives</c><00:16:22.079><c> elsewhere</c>

00:16:22.430 --> 00:16:22.440 align:start position:0%
running it on state that lives elsewhere
 

00:16:22.440 --> 00:16:25.389 align:start position:0%
running it on state that lives elsewhere
in<00:16:22.560><c> the</c><00:16:23.040><c> network</c><00:16:24.040><c> and</c><00:16:24.279><c> because</c><00:16:24.480><c> of</c><00:16:24.680><c> that</c><00:16:25.240><c> they</c>

00:16:25.389 --> 00:16:25.399 align:start position:0%
in the network and because of that they
 

00:16:25.399 --> 00:16:27.829 align:start position:0%
in the network and because of that they
need<00:16:25.560><c> to</c><00:16:25.759><c> be</c><00:16:25.880><c> able</c><00:16:26.120><c> to</c><00:16:26.360><c> execute</c><00:16:26.839><c> code</c><00:16:27.399><c> on</c><00:16:27.680><c> top</c>

00:16:27.829 --> 00:16:27.839 align:start position:0%
need to be able to execute code on top
 

00:16:27.839 --> 00:16:29.389 align:start position:0%
need to be able to execute code on top
of<00:16:28.040><c> state</c><00:16:28.279><c> that</c><00:16:28.440><c> they</c><00:16:28.519><c> don't</c><00:16:28.680><c> know</c><00:16:28.959><c> or</c><00:16:29.079><c> perhaps</c>

00:16:29.389 --> 00:16:29.399 align:start position:0%
of state that they don't know or perhaps
 

00:16:29.399 --> 00:16:30.430 align:start position:0%
of state that they don't know or perhaps
nobody

00:16:30.430 --> 00:16:30.440 align:start position:0%
nobody
 

00:16:30.440 --> 00:16:33.230 align:start position:0%
nobody
knows<00:16:31.440><c> so</c><00:16:31.920><c> this</c><00:16:32.240><c> is</c><00:16:32.440><c> something</c><00:16:32.920><c> that</c><00:16:33.040><c> is</c><00:16:33.160><c> at</c>

00:16:33.230 --> 00:16:33.240 align:start position:0%
knows so this is something that is at
 

00:16:33.240 --> 00:16:34.790 align:start position:0%
knows so this is something that is at
least<00:16:33.440><c> partially</c><00:16:33.759><c> solved</c><00:16:34.120><c> by</c><00:16:34.240><c> Technologies</c>

00:16:34.790 --> 00:16:34.800 align:start position:0%
least partially solved by Technologies
 

00:16:34.800 --> 00:16:36.870 align:start position:0%
least partially solved by Technologies
like<00:16:34.920><c> fully</c><00:16:35.199><c> homomorphic</c><00:16:35.880><c> encryption</c><00:16:36.680><c> and</c>

00:16:36.870 --> 00:16:36.880 align:start position:0%
like fully homomorphic encryption and
 

00:16:36.880 --> 00:16:38.430 align:start position:0%
like fully homomorphic encryption and
we've<00:16:37.120><c> started</c><00:16:37.399><c> to</c><00:16:37.519><c> see</c><00:16:37.800><c> the</c><00:16:37.920><c> first</c><00:16:38.160><c> tool</c>

00:16:38.430 --> 00:16:38.440 align:start position:0%
we've started to see the first tool
 

00:16:38.440 --> 00:16:40.670 align:start position:0%
we've started to see the first tool
Stacks<00:16:38.800><c> like</c><00:16:39.000><c> Phantom</c><00:16:39.319><c> Zone</c><00:16:39.560><c> or</c><00:16:39.680><c> open</c><00:16:39.920><c> if</c>

00:16:40.670 --> 00:16:40.680 align:start position:0%
Stacks like Phantom Zone or open if
 

00:16:40.680 --> 00:16:43.150 align:start position:0%
Stacks like Phantom Zone or open if
become<00:16:41.040><c> possible</c><00:16:41.319><c> for</c><00:16:41.480><c> developers</c><00:16:41.920><c> to</c><00:16:42.079><c> use</c><00:16:43.000><c> in</c>

00:16:43.150 --> 00:16:43.160 align:start position:0%
become possible for developers to use in
 

00:16:43.160 --> 00:16:45.590 align:start position:0%
become possible for developers to use in
fact<00:16:43.519><c> we</c><00:16:43.639><c> have</c><00:16:43.759><c> a</c><00:16:43.880><c> demonstration</c><00:16:44.880><c> of</c><00:16:45.000><c> a</c><00:16:45.160><c> game</c>

00:16:45.590 --> 00:16:45.600 align:start position:0%
fact we have a demonstration of a game
 

00:16:45.600 --> 00:16:47.509 align:start position:0%
fact we have a demonstration of a game
running<00:16:46.399><c> inside</c><00:16:46.759><c> of</c><00:16:47.000><c> this</c><00:16:47.120><c> sort</c><00:16:47.319><c> of</c>

00:16:47.509 --> 00:16:47.519 align:start position:0%
running inside of this sort of
 

00:16:47.519 --> 00:16:49.629 align:start position:0%
running inside of this sort of
hallucinated<00:16:48.199><c> server</c><00:16:48.600><c> downstairs</c><00:16:49.399><c> if</c><00:16:49.519><c> you</c>

00:16:49.629 --> 00:16:49.639 align:start position:0%
hallucinated server downstairs if you
 

00:16:49.639 --> 00:16:51.309 align:start position:0%
hallucinated server downstairs if you
check<00:16:49.800><c> out</c><00:16:49.959><c> the</c><00:16:50.040><c> Frog</c><00:16:50.360><c> Community</c><00:16:50.759><c> Hub</c><00:16:51.160><c> there's</c>

00:16:51.309 --> 00:16:51.319 align:start position:0%
check out the Frog Community Hub there's
 

00:16:51.319 --> 00:16:52.910 align:start position:0%
check out the Frog Community Hub there's
a<00:16:51.440><c> game</c><00:16:51.600><c> called</c><00:16:51.800><c> frog</c><00:16:52.120><c> Zone</c><00:16:52.399><c> where</c><00:16:52.519><c> there's</c><00:16:52.639><c> a</c>

00:16:52.910 --> 00:16:52.920 align:start position:0%
a game called frog Zone where there's a
 

00:16:52.920 --> 00:16:55.670 align:start position:0%
a game called frog Zone where there's a
back<00:16:53.079><c> end</c><00:16:53.800><c> that</c><00:16:54.079><c> holds</c><00:16:54.399><c> about</c><00:16:54.720><c> 500</c><00:16:55.279><c> bits</c><00:16:55.480><c> of</c>

00:16:55.670 --> 00:16:55.680 align:start position:0%
back end that holds about 500 bits of
 

00:16:55.680 --> 00:16:57.670 align:start position:0%
back end that holds about 500 bits of
game<00:16:55.959><c> State</c><00:16:56.560><c> that's</c><00:16:56.759><c> running</c><00:16:57.160><c> inside</c><00:16:57.440><c> of</c>

00:16:57.670 --> 00:16:57.680 align:start position:0%
game State that's running inside of
 

00:16:57.680 --> 00:16:59.030 align:start position:0%
game State that's running inside of
fully<00:16:57.959><c> homomorphic</c><00:16:58.440><c> encryption</c><00:16:58.720><c> that</c><00:16:58.959><c> you</c>

00:16:59.030 --> 00:16:59.040 align:start position:0%
fully homomorphic encryption that you
 

00:16:59.040 --> 00:17:00.150 align:start position:0%
fully homomorphic encryption that you
can

00:17:00.150 --> 00:17:00.160 align:start position:0%
can
 

00:17:00.160 --> 00:17:03.509 align:start position:0%
can
play<00:17:01.160><c> we</c><00:17:01.279><c> want</c><00:17:01.639><c> data</c><00:17:02.319><c> interoperability</c><00:17:03.319><c> we</c>

00:17:03.509 --> 00:17:03.519 align:start position:0%
play we want data interoperability we
 

00:17:03.519 --> 00:17:06.909 align:start position:0%
play we want data interoperability we
want<00:17:03.880><c> for</c><00:17:04.520><c> the</c><00:17:04.720><c> outputs</c><00:17:05.559><c> from</c><00:17:06.039><c> one</c><00:17:06.280><c> service</c><00:17:06.640><c> or</c>

00:17:06.909 --> 00:17:06.919 align:start position:0%
want for the outputs from one service or
 

00:17:06.919 --> 00:17:09.230 align:start position:0%
want for the outputs from one service or
computation<00:17:07.839><c> on</c><00:17:08.000><c> this</c><00:17:08.160><c> network</c><00:17:08.520><c> to</c><00:17:08.600><c> be</c><00:17:08.760><c> usable</c>

00:17:09.230 --> 00:17:09.240 align:start position:0%
computation on this network to be usable
 

00:17:09.240 --> 00:17:10.549 align:start position:0%
computation on this network to be usable
elsewhere<00:17:09.799><c> this</c><00:17:09.880><c> is</c><00:17:10.000><c> one</c><00:17:10.079><c> of</c><00:17:10.199><c> the</c><00:17:10.319><c> big</c>

00:17:10.549 --> 00:17:10.559 align:start position:0%
elsewhere this is one of the big
 

00:17:10.559 --> 00:17:13.069 align:start position:0%
elsewhere this is one of the big
problems<00:17:10.880><c> with</c><00:17:11.000><c> the</c><00:17:11.120><c> internet</c><00:17:11.679><c> today</c><00:17:12.679><c> and</c><00:17:12.799><c> for</c>

00:17:13.069 --> 00:17:13.079 align:start position:0%
problems with the internet today and for
 

00:17:13.079 --> 00:17:16.549 align:start position:0%
problems with the internet today and for
this<00:17:13.679><c> we've</c><00:17:14.319><c> seen</c><00:17:15.319><c> various</c><00:17:15.760><c> groups</c><00:17:16.240><c> projects</c>

00:17:16.549 --> 00:17:16.559 align:start position:0%
this we've seen various groups projects
 

00:17:16.559 --> 00:17:17.949 align:start position:0%
this we've seen various groups projects
and<00:17:16.720><c> companies</c><00:17:17.000><c> start</c><00:17:17.199><c> to</c><00:17:17.360><c> approach</c><00:17:17.640><c> the</c><00:17:17.720><c> idea</c>

00:17:17.949 --> 00:17:17.959 align:start position:0%
and companies start to approach the idea
 

00:17:17.959 --> 00:17:20.309 align:start position:0%
and companies start to approach the idea
of<00:17:18.079><c> proof</c><00:17:18.400><c> carrying</c><00:17:18.880><c> data</c><00:17:19.600><c> the</c><00:17:19.760><c> idea</c><00:17:20.039><c> that</c><00:17:20.199><c> I</c>

00:17:20.309 --> 00:17:20.319 align:start position:0%
of proof carrying data the idea that I
 

00:17:20.319 --> 00:17:21.949 align:start position:0%
of proof carrying data the idea that I
can<00:17:20.520><c> take</c><00:17:20.760><c> data</c><00:17:21.039><c> in</c><00:17:21.559><c> that</c><00:17:21.720><c> is</c>

00:17:21.949 --> 00:17:21.959 align:start position:0%
can take data in that is
 

00:17:21.959 --> 00:17:24.150 align:start position:0%
can take data in that is
cryptographically<00:17:22.640><c> verified</c><00:17:23.520><c> I</c><00:17:23.600><c> can</c><00:17:23.760><c> perform</c>

00:17:24.150 --> 00:17:24.160 align:start position:0%
cryptographically verified I can perform
 

00:17:24.160 --> 00:17:25.949 align:start position:0%
cryptographically verified I can perform
operations<00:17:24.559><c> or</c><00:17:24.720><c> run</c><00:17:24.959><c> programs</c><00:17:25.319><c> on</c><00:17:25.439><c> it</c><00:17:25.720><c> and</c><00:17:25.880><c> I</c>

00:17:25.949 --> 00:17:25.959 align:start position:0%
operations or run programs on it and I
 

00:17:25.959 --> 00:17:27.789 align:start position:0%
operations or run programs on it and I
can<00:17:26.160><c> get</c><00:17:26.439><c> an</c><00:17:26.600><c> output</c><00:17:27.120><c> that</c><00:17:27.240><c> is</c><00:17:27.439><c> just</c><00:17:27.600><c> as</c>

00:17:27.789 --> 00:17:27.799 align:start position:0%
can get an output that is just as
 

00:17:27.799 --> 00:17:30.510 align:start position:0%
can get an output that is just as
verifiable<00:17:28.520><c> and</c><00:17:29.280><c> inherits</c><00:17:30.240><c> the</c>

00:17:30.510 --> 00:17:30.520 align:start position:0%
verifiable and inherits the
 

00:17:30.520 --> 00:17:32.950 align:start position:0%
verifiable and inherits the
interpretability<00:17:31.520><c> and</c><00:17:31.640><c> the</c><00:17:31.960><c> verifiability</c>

00:17:32.950 --> 00:17:32.960 align:start position:0%
interpretability and the verifiability
 

00:17:32.960 --> 00:17:35.950 align:start position:0%
interpretability and the verifiability
of<00:17:33.240><c> the</c><00:17:33.400><c> inputs</c><00:17:34.080><c> to</c><00:17:34.720><c> that</c><00:17:34.880><c> transformation</c>

00:17:35.950 --> 00:17:35.960 align:start position:0%
of the inputs to that transformation
 

00:17:35.960 --> 00:17:38.350 align:start position:0%
of the inputs to that transformation
process<00:17:36.960><c> projects</c><00:17:37.240><c> like</c><00:17:37.400><c> ZK</c><00:17:37.720><c> email</c><00:17:38.000><c> TLS</c>

00:17:38.350 --> 00:17:38.360 align:start position:0%
process projects like ZK email TLS
 

00:17:38.360 --> 00:17:40.630 align:start position:0%
process projects like ZK email TLS
notary<00:17:38.720><c> zass</c><00:17:39.400><c> and</c><00:17:39.520><c> many</c><00:17:39.760><c> other</c><00:17:39.919><c> ZK</c><00:17:40.280><c> ID</c>

00:17:40.630 --> 00:17:40.640 align:start position:0%
notary zass and many other ZK ID
 

00:17:40.640 --> 00:17:42.590 align:start position:0%
notary zass and many other ZK ID
projects<00:17:41.240><c> are</c><00:17:41.440><c> starting</c><00:17:41.840><c> to</c><00:17:42.120><c> build</c><00:17:42.400><c> up</c>

00:17:42.590 --> 00:17:42.600 align:start position:0%
projects are starting to build up
 

00:17:42.600 --> 00:17:44.549 align:start position:0%
projects are starting to build up
towards<00:17:42.840><c> a</c><00:17:43.000><c> future</c><00:17:43.559><c> where</c><00:17:43.760><c> data</c><00:17:44.000><c> is</c><00:17:44.160><c> default</c>

00:17:44.549 --> 00:17:44.559 align:start position:0%
towards a future where data is default
 

00:17:44.559 --> 00:17:48.470 align:start position:0%
towards a future where data is default
interoperable<00:17:45.600><c> self-verifying</c><00:17:46.600><c> and</c>

00:17:48.470 --> 00:17:48.480 align:start position:0%
interoperable self-verifying and
 

00:17:48.480 --> 00:17:50.990 align:start position:0%
interoperable self-verifying and
self-describing<00:17:49.480><c> we</c><00:17:49.640><c> want</c><00:17:50.039><c> consensus</c><00:17:50.799><c> and</c>

00:17:50.990 --> 00:17:51.000 align:start position:0%
self-describing we want consensus and
 

00:17:51.000 --> 00:17:52.669 align:start position:0%
self-describing we want consensus and
data<00:17:51.320><c> availability</c><00:17:52.039><c> this</c><00:17:52.120><c> is</c><00:17:52.280><c> something</c><00:17:52.520><c> that</c>

00:17:52.669 --> 00:17:52.679 align:start position:0%
data availability this is something that
 

00:17:52.679 --> 00:17:54.310 align:start position:0%
data availability this is something that
actually<00:17:53.039><c> no</c><00:17:53.200><c> amount</c><00:17:53.400><c> of</c><00:17:53.559><c> cryptography</c><00:17:54.120><c> can</c>

00:17:54.310 --> 00:17:54.320 align:start position:0%
actually no amount of cryptography can
 

00:17:54.320 --> 00:17:56.750 align:start position:0%
actually no amount of cryptography can
give<00:17:54.520><c> us</c><00:17:55.440><c> but</c><00:17:55.799><c> we</c><00:17:55.960><c> want</c><00:17:56.080><c> to</c><00:17:56.240><c> make</c><00:17:56.360><c> sure</c><00:17:56.600><c> that</c>

00:17:56.750 --> 00:17:56.760 align:start position:0%
give us but we want to make sure that
 

00:17:56.760 --> 00:17:58.470 align:start position:0%
give us but we want to make sure that
even<00:17:56.960><c> if</c><00:17:57.080><c> a</c><00:17:57.280><c> program</c><00:17:57.679><c> is</c><00:17:57.799><c> being</c><00:17:58.000><c> run</c><00:17:58.240><c> somewhere</c>

00:17:58.470 --> 00:17:58.480 align:start position:0%
even if a program is being run somewhere
 

00:17:58.480 --> 00:18:00.470 align:start position:0%
even if a program is being run somewhere
even<00:17:58.640><c> if</c><00:17:58.720><c> it's</c><00:17:58.919><c> being</c><00:17:59.080><c> run</c><00:17:59.640><c> correctly</c><00:18:00.280><c> and</c>

00:18:00.470 --> 00:18:00.480 align:start position:0%
even if it's being run correctly and
 

00:18:00.480 --> 00:18:01.230 align:start position:0%
even if it's being run correctly and
with

00:18:01.230 --> 00:18:01.240 align:start position:0%
with
 

00:18:01.240 --> 00:18:03.310 align:start position:0%
with
confidentiality<00:18:02.240><c> and</c><00:18:02.440><c> it's</c><00:18:02.679><c> producing</c><00:18:03.159><c> some</c>

00:18:03.310 --> 00:18:03.320 align:start position:0%
confidentiality and it's producing some
 

00:18:03.320 --> 00:18:06.149 align:start position:0%
confidentiality and it's producing some
sort<00:18:03.480><c> of</c><00:18:03.720><c> outputs</c><00:18:04.720><c> we</c><00:18:04.880><c> want</c><00:18:05.120><c> everybody</c><00:18:05.520><c> for</c><00:18:05.840><c> be</c>

00:18:06.149 --> 00:18:06.159 align:start position:0%
sort of outputs we want everybody for be
 

00:18:06.159 --> 00:18:08.270 align:start position:0%
sort of outputs we want everybody for be
we<00:18:06.280><c> want</c><00:18:06.440><c> for</c><00:18:06.679><c> everybody</c><00:18:07.440><c> to</c><00:18:07.640><c> be</c><00:18:07.799><c> able</c><00:18:08.039><c> to</c>

00:18:08.270 --> 00:18:08.280 align:start position:0%
we want for everybody to be able to
 

00:18:08.280 --> 00:18:10.669 align:start position:0%
we want for everybody to be able to
retrieve<00:18:09.120><c> those</c><00:18:09.440><c> outputs</c><00:18:10.200><c> it's</c><00:18:10.320><c> not</c><00:18:10.480><c> enough</c>

00:18:10.669 --> 00:18:10.679 align:start position:0%
retrieve those outputs it's not enough
 

00:18:10.679 --> 00:18:11.870 align:start position:0%
retrieve those outputs it's not enough
to<00:18:10.799><c> just</c><00:18:10.960><c> know</c><00:18:11.159><c> that</c><00:18:11.280><c> something</c><00:18:11.520><c> was</c><00:18:11.679><c> done</c>

00:18:11.870 --> 00:18:11.880 align:start position:0%
to just know that something was done
 

00:18:11.880 --> 00:18:13.470 align:start position:0%
to just know that something was done
correctly<00:18:12.640><c> sometimes</c><00:18:12.840><c> there's</c><00:18:13.080><c> actual</c>

00:18:13.470 --> 00:18:13.480 align:start position:0%
correctly sometimes there's actual
 

00:18:13.480 --> 00:18:14.950 align:start position:0%
correctly sometimes there's actual
pieces<00:18:13.919><c> of</c><00:18:14.080><c> the</c><00:18:14.200><c> state</c><00:18:14.440><c> that</c><00:18:14.520><c> you</c><00:18:14.600><c> need</c><00:18:14.720><c> to</c><00:18:14.840><c> be</c>

00:18:14.950 --> 00:18:14.960 align:start position:0%
pieces of the state that you need to be
 

00:18:14.960 --> 00:18:17.110 align:start position:0%
pieces of the state that you need to be
able<00:18:15.080><c> to</c><00:18:15.640><c> retrieve</c><00:18:16.640><c> and</c><00:18:16.760><c> this</c><00:18:16.880><c> is</c><00:18:16.960><c> what</c>

00:18:17.110 --> 00:18:17.120 align:start position:0%
able to retrieve and this is what
 

00:18:17.120 --> 00:18:19.270 align:start position:0%
able to retrieve and this is what
blockchains<00:18:17.600><c> give</c><00:18:17.760><c> us</c><00:18:17.960><c> this</c><00:18:18.080><c> is</c><00:18:18.280><c> what</c><00:18:18.679><c> the</c><00:18:18.919><c> big</c>

00:18:19.270 --> 00:18:19.280 align:start position:0%
blockchains give us this is what the big
 

00:18:19.280 --> 00:18:21.110 align:start position:0%
blockchains give us this is what the big
innovation<00:18:20.000><c> in</c><00:18:20.200><c> cryptoeconomics</c><00:18:20.960><c> and</c>

00:18:21.110 --> 00:18:21.120 align:start position:0%
innovation in cryptoeconomics and
 

00:18:21.120 --> 00:18:23.470 align:start position:0%
innovation in cryptoeconomics and
consensus<00:18:21.679><c> over</c><00:18:21.880><c> the</c><00:18:22.080><c> past</c><00:18:22.520><c> decade</c><00:18:22.919><c> decade</c>

00:18:23.470 --> 00:18:23.480 align:start position:0%
consensus over the past decade decade
 

00:18:23.480 --> 00:18:24.909 align:start position:0%
consensus over the past decade decade
decade<00:18:23.760><c> and</c><00:18:23.880><c> a</c><00:18:24.000><c> half</c><00:18:24.159><c> have</c>

00:18:24.909 --> 00:18:24.919 align:start position:0%
decade and a half have
 

00:18:24.919 --> 00:18:27.149 align:start position:0%
decade and a half have
been<00:18:25.919><c> and</c><00:18:26.080><c> finally</c><00:18:26.480><c> we</c><00:18:26.600><c> want</c><00:18:26.720><c> to</c><00:18:26.799><c> be</c><00:18:26.880><c> able</c><00:18:27.039><c> to</c>

00:18:27.149 --> 00:18:27.159 align:start position:0%
been and finally we want to be able to
 

00:18:27.159 --> 00:18:30.149 align:start position:0%
been and finally we want to be able to
do<00:18:27.400><c> all</c><00:18:27.520><c> of</c><00:18:27.720><c> these</c><00:18:27.960><c> things</c><00:18:28.320><c> in</c><00:18:28.440><c> a</c><00:18:28.799><c> scalable</c><00:18:29.280><c> way</c>

00:18:30.149 --> 00:18:30.159 align:start position:0%
do all of these things in a scalable way
 

00:18:30.159 --> 00:18:32.070 align:start position:0%
do all of these things in a scalable way
many<00:18:30.400><c> of</c><00:18:30.520><c> our</c><00:18:30.760><c> strategies</c><00:18:31.320><c> today</c><00:18:31.840><c> for</c>

00:18:32.070 --> 00:18:32.080 align:start position:0%
many of our strategies today for
 

00:18:32.080 --> 00:18:34.149 align:start position:0%
many of our strategies today for
carrying<00:18:32.440><c> out</c><00:18:32.640><c> these</c><00:18:32.840><c> functions</c><00:18:33.640><c> rely</c><00:18:33.960><c> on</c>

00:18:34.149 --> 00:18:34.159 align:start position:0%
carrying out these functions rely on
 

00:18:34.159 --> 00:18:35.990 align:start position:0%
carrying out these functions rely on
these<00:18:34.320><c> very</c><00:18:34.559><c> interactive</c><00:18:35.080><c> protocols</c><00:18:35.760><c> where</c>

00:18:35.990 --> 00:18:36.000 align:start position:0%
these very interactive protocols where
 

00:18:36.000 --> 00:18:38.310 align:start position:0%
these very interactive protocols where
everyone<00:18:36.400><c> must</c><00:18:36.640><c> be</c><00:18:36.840><c> online</c><00:18:37.200><c> at</c><00:18:37.360><c> once</c><00:18:38.120><c> so</c>

00:18:38.310 --> 00:18:38.320 align:start position:0%
everyone must be online at once so
 

00:18:38.320 --> 00:18:40.510 align:start position:0%
everyone must be online at once so
imagine<00:18:38.600><c> a</c><00:18:38.760><c> world</c><00:18:39.600><c> where</c><00:18:39.760><c> we're</c><00:18:39.960><c> all</c>

00:18:40.510 --> 00:18:40.520 align:start position:0%
imagine a world where we're all
 

00:18:40.520 --> 00:18:42.950 align:start position:0%
imagine a world where we're all
emulating<00:18:41.159><c> the</c><00:18:41.320><c> execution</c><00:18:42.240><c> of</c><00:18:42.480><c> a</c><00:18:42.640><c> social</c>

00:18:42.950 --> 00:18:42.960 align:start position:0%
emulating the execution of a social
 

00:18:42.960 --> 00:18:44.750 align:start position:0%
emulating the execution of a social
media<00:18:43.280><c> backend</c><00:18:43.720><c> whether</c><00:18:43.919><c> that's</c><00:18:44.120><c> Twitter</c><00:18:44.480><c> or</c>

00:18:44.750 --> 00:18:44.760 align:start position:0%
media backend whether that's Twitter or
 

00:18:44.760 --> 00:18:47.070 align:start position:0%
media backend whether that's Twitter or
Facebook<00:18:45.280><c> or</c><00:18:45.799><c> whatever</c><00:18:46.120><c> social</c><00:18:46.400><c> media</c><00:18:46.679><c> you</c>

00:18:47.070 --> 00:18:47.080 align:start position:0%
Facebook or whatever social media you
 

00:18:47.080 --> 00:18:49.630 align:start position:0%
Facebook or whatever social media you
want<00:18:48.080><c> we</c><00:18:48.240><c> don't</c><00:18:48.520><c> want</c><00:18:48.760><c> to</c><00:18:48.919><c> have</c><00:18:49.000><c> to</c><00:18:49.159><c> require</c>

00:18:49.630 --> 00:18:49.640 align:start position:0%
want we don't want to have to require
 

00:18:49.640 --> 00:18:51.950 align:start position:0%
want we don't want to have to require
that<00:18:50.159><c> all</c><00:18:50.440><c> of</c><00:18:50.600><c> a</c><00:18:50.799><c> billion</c><00:18:51.240><c> people</c><00:18:51.480><c> or</c><00:18:51.640><c> billions</c>

00:18:51.950 --> 00:18:51.960 align:start position:0%
that all of a billion people or billions
 

00:18:51.960 --> 00:18:54.070 align:start position:0%
that all of a billion people or billions
of<00:18:52.120><c> people</c><00:18:52.320><c> are</c><00:18:52.480><c> online</c><00:18:52.919><c> all</c><00:18:53.039><c> the</c><00:18:53.200><c> time</c><00:18:53.679><c> to</c><00:18:53.840><c> do</c>

00:18:54.070 --> 00:18:54.080 align:start position:0%
of people are online all the time to do
 

00:18:54.080 --> 00:18:55.310 align:start position:0%
of people are online all the time to do
decryptions<00:18:54.600><c> or</c><00:18:54.760><c> various</c><00:18:55.039><c> kinds</c><00:18:55.200><c> of</c>

00:18:55.310 --> 00:18:55.320 align:start position:0%
decryptions or various kinds of
 

00:18:55.320 --> 00:18:57.310 align:start position:0%
decryptions or various kinds of
cryptographic<00:18:55.919><c> interactions</c><00:18:56.919><c> what</c><00:18:57.039><c> we'd</c>

00:18:57.310 --> 00:18:57.320 align:start position:0%
cryptographic interactions what we'd
 

00:18:57.320 --> 00:18:59.789 align:start position:0%
cryptographic interactions what we'd
like<00:18:57.600><c> is</c><00:18:57.720><c> for</c><00:18:58.039><c> only</c><00:18:58.320><c> the</c><00:18:58.480><c> inv</c><00:18:58.960><c> D</c><00:18:59.120><c> parties</c><00:18:59.640><c> in</c>

00:18:59.789 --> 00:18:59.799 align:start position:0%
like is for only the inv D parties in
 

00:18:59.799 --> 00:19:01.549 align:start position:0%
like is for only the inv D parties in
any<00:19:00.000><c> given</c><00:19:00.280><c> interaction</c><00:19:01.000><c> to</c><00:19:01.159><c> need</c><00:19:01.320><c> to</c><00:19:01.440><c> be</c>

00:19:01.549 --> 00:19:01.559 align:start position:0%
any given interaction to need to be
 

00:19:01.559 --> 00:19:03.870 align:start position:0%
any given interaction to need to be
online<00:19:01.880><c> to</c><00:19:02.159><c> participate</c><00:19:03.159><c> and</c><00:19:03.320><c> this</c><00:19:03.440><c> is</c><00:19:03.640><c> what</c>

00:19:03.870 --> 00:19:03.880 align:start position:0%
online to participate and this is what
 

00:19:03.880 --> 00:19:05.390 align:start position:0%
online to participate and this is what
the<00:19:04.000><c> most</c><00:19:04.240><c> advanced</c><00:19:04.679><c> branches</c><00:19:05.159><c> of</c><00:19:05.280><c> the</c>

00:19:05.390 --> 00:19:05.400 align:start position:0%
the most advanced branches of the
 

00:19:05.400 --> 00:19:07.350 align:start position:0%
the most advanced branches of the
programmable<00:19:05.880><c> cryptography</c><00:19:06.400><c> TCH</c><00:19:06.679><c> Tre</c><00:19:07.159><c> like</c>

00:19:07.350 --> 00:19:07.360 align:start position:0%
programmable cryptography TCH Tre like
 

00:19:07.360 --> 00:19:09.149 align:start position:0%
programmable cryptography TCH Tre like
obfuscation<00:19:08.120><c> or</c><00:19:08.280><c> functional</c><00:19:08.679><c> encryption</c><00:19:09.039><c> or</c>

00:19:09.149 --> 00:19:09.159 align:start position:0%
obfuscation or functional encryption or
 

00:19:09.159 --> 00:19:11.789 align:start position:0%
obfuscation or functional encryption or
witness<00:19:09.480><c> encryption</c><00:19:09.919><c> give</c>

00:19:11.789 --> 00:19:11.799 align:start position:0%
witness encryption give
 

00:19:11.799 --> 00:19:15.470 align:start position:0%
witness encryption give
us<00:19:12.799><c> as</c><00:19:13.000><c> of</c><00:19:13.520><c> about</c><00:19:14.080><c> three</c><00:19:14.280><c> or</c><00:19:14.440><c> four</c><00:19:14.679><c> years</c><00:19:14.919><c> ago</c>

00:19:15.470 --> 00:19:15.480 align:start position:0%
us as of about three or four years ago
 

00:19:15.480 --> 00:19:17.669 align:start position:0%
us as of about three or four years ago
obfuscation<00:19:16.080><c> and</c><00:19:16.280><c> functional</c><00:19:16.679><c> encryption</c>

00:19:17.669 --> 00:19:17.679 align:start position:0%
obfuscation and functional encryption
 

00:19:17.679 --> 00:19:20.830 align:start position:0%
obfuscation and functional encryption
are<00:19:17.880><c> known</c><00:19:18.360><c> to</c><00:19:18.720><c> actually</c><00:19:19.039><c> be</c><00:19:19.360><c> sound</c><00:19:20.360><c> um</c><00:19:20.559><c> so</c>

00:19:20.830 --> 00:19:20.840 align:start position:0%
are known to actually be sound um so
 

00:19:20.840 --> 00:19:22.870 align:start position:0%
are known to actually be sound um so
while<00:19:21.120><c> this</c><00:19:21.280><c> is</c><00:19:21.440><c> the</c><00:19:21.559><c> furthest</c><00:19:22.000><c> along</c><00:19:22.440><c> in</c><00:19:22.640><c> the</c>

00:19:22.870 --> 00:19:22.880 align:start position:0%
while this is the furthest along in the
 

00:19:22.880 --> 00:19:24.149 align:start position:0%
while this is the furthest along in the
tech<00:19:23.120><c> tree</c><00:19:23.440><c> that</c><00:19:23.559><c> we're</c><00:19:23.720><c> working</c><00:19:23.960><c> on</c>

00:19:24.149 --> 00:19:24.159 align:start position:0%
tech tree that we're working on
 

00:19:24.159 --> 00:19:27.110 align:start position:0%
tech tree that we're working on
advancing<00:19:24.919><c> we</c><00:19:25.080><c> know</c><00:19:25.280><c> that</c><00:19:25.440><c> it</c><00:19:25.559><c> is</c>

00:19:27.110 --> 00:19:27.120 align:start position:0%
advancing we know that it is
 

00:19:27.120 --> 00:19:30.350 align:start position:0%
advancing we know that it is
possible<00:19:28.120><c> so</c><00:19:28.280><c> to</c><00:19:28.360><c> summarize</c>

00:19:30.350 --> 00:19:30.360 align:start position:0%
possible so to summarize
 

00:19:30.360 --> 00:19:32.029 align:start position:0%
possible so to summarize
there's<00:19:30.559><c> a</c><00:19:30.679><c> couple</c><00:19:30.919><c> of</c><00:19:31.120><c> questions</c><00:19:31.799><c> that</c><00:19:31.919><c> we</c>

00:19:32.029 --> 00:19:32.039 align:start position:0%
there's a couple of questions that we
 

00:19:32.039 --> 00:19:34.789 align:start position:0%
there's a couple of questions that we
can<00:19:32.240><c> look</c><00:19:32.440><c> back</c><00:19:32.600><c> on</c><00:19:32.799><c> and</c><00:19:33.000><c> ask</c><00:19:33.760><c> one</c><00:19:34.000><c> is</c><00:19:34.480><c> what</c><00:19:34.640><c> can</c>

00:19:34.789 --> 00:19:34.799 align:start position:0%
can look back on and ask one is what can
 

00:19:34.799 --> 00:19:36.909 align:start position:0%
can look back on and ask one is what can
cryptography<00:19:35.400><c> do</c><00:19:35.640><c> that</c><00:19:35.799><c> ethereum</c><00:19:36.360><c> alone</c>

00:19:36.909 --> 00:19:36.919 align:start position:0%
cryptography do that ethereum alone
 

00:19:36.919 --> 00:19:38.029 align:start position:0%
cryptography do that ethereum alone
cannot

00:19:38.029 --> 00:19:38.039 align:start position:0%
cannot
 

00:19:38.039 --> 00:19:40.710 align:start position:0%
cannot
do<00:19:39.039><c> in</c><00:19:39.159><c> short</c><00:19:39.480><c> as</c><00:19:39.559><c> we've</c><00:19:39.760><c> seen</c><00:19:40.080><c> cryptography</c>

00:19:40.710 --> 00:19:40.720 align:start position:0%
do in short as we've seen cryptography
 

00:19:40.720 --> 00:19:42.789 align:start position:0%
do in short as we've seen cryptography
allows<00:19:41.000><c> us</c><00:19:41.159><c> to</c><00:19:41.280><c> build</c><00:19:41.559><c> Rich</c><00:19:41.880><c> applications</c>

00:19:42.789 --> 00:19:42.799 align:start position:0%
allows us to build Rich applications
 

00:19:42.799 --> 00:19:45.390 align:start position:0%
allows us to build Rich applications
with<00:19:43.120><c> complex</c><00:19:43.640><c> interoperable</c><00:19:44.320><c> state</c><00:19:45.280><c> it</c>

00:19:45.390 --> 00:19:45.400 align:start position:0%
with complex interoperable state it
 

00:19:45.400 --> 00:19:47.110 align:start position:0%
with complex interoperable state it
allows<00:19:45.679><c> us</c><00:19:45.760><c> to</c><00:19:45.919><c> answer</c><00:19:46.200><c> questions</c><00:19:46.559><c> like</c><00:19:46.919><c> how</c>

00:19:47.110 --> 00:19:47.120 align:start position:0%
allows us to answer questions like how
 

00:19:47.120 --> 00:19:48.549 align:start position:0%
allows us to answer questions like how
can<00:19:47.320><c> domains</c><00:19:47.679><c> that</c><00:19:47.799><c> use</c><00:19:48.039><c> different</c><00:19:48.320><c> data</c>

00:19:48.549 --> 00:19:48.559 align:start position:0%
can domains that use different data
 

00:19:48.559 --> 00:19:50.430 align:start position:0%
can domains that use different data
schemas<00:19:49.080><c> proof</c><00:19:49.360><c> systems</c><00:19:49.679><c> or</c><00:19:49.799><c> semantics</c><00:19:50.280><c> talk</c>

00:19:50.430 --> 00:19:50.440 align:start position:0%
schemas proof systems or semantics talk
 

00:19:50.440 --> 00:19:52.470 align:start position:0%
schemas proof systems or semantics talk
to<00:19:50.600><c> each</c><00:19:50.760><c> other</c><00:19:51.440><c> how</c><00:19:51.600><c> can</c><00:19:51.799><c> applications</c><00:19:52.240><c> hold</c>

00:19:52.470 --> 00:19:52.480 align:start position:0%
to each other how can applications hold
 

00:19:52.480 --> 00:19:54.430 align:start position:0%
to each other how can applications hold
state<00:19:52.760><c> with</c><00:19:52.960><c> complex</c><00:19:53.400><c> predicates</c><00:19:54.000><c> on</c><00:19:54.159><c> who</c><00:19:54.320><c> can</c>

00:19:54.430 --> 00:19:54.440 align:start position:0%
state with complex predicates on who can
 

00:19:54.440 --> 00:19:55.990 align:start position:0%
state with complex predicates on who can
see<00:19:54.679><c> it</c><00:19:54.960><c> who</c><00:19:55.080><c> can</c><00:19:55.200><c> read</c><00:19:55.360><c> it</c><00:19:55.480><c> who</c><00:19:55.600><c> can</c><00:19:55.720><c> write</c><00:19:55.880><c> to</c>

00:19:55.990 --> 00:19:56.000 align:start position:0%
see it who can read it who can write to
 

00:19:56.000 --> 00:19:57.870 align:start position:0%
see it who can read it who can write to
it<00:19:56.120><c> who</c><00:19:56.240><c> can</c><00:19:56.400><c> operate</c><00:19:56.679><c> on</c><00:19:56.799><c> it</c><00:19:57.280><c> and</c><00:19:57.440><c> how</c><00:19:57.600><c> can</c><00:19:57.720><c> an</c>

00:19:57.870 --> 00:19:57.880 align:start position:0%
it who can operate on it and how can an
 

00:19:57.880 --> 00:20:00.350 align:start position:0%
it who can operate on it and how can an
application<00:19:58.280><c> have</c><00:19:58.400><c> St</c><00:19:59.120><c> that</c><00:19:59.320><c> nobody</c>

00:20:00.350 --> 00:20:00.360 align:start position:0%
application have St that nobody
 

00:20:00.360 --> 00:20:03.230 align:start position:0%
application have St that nobody
knows<00:20:01.360><c> conversely</c><00:20:02.080><c> we</c><00:20:02.200><c> can</c><00:20:02.360><c> also</c><00:20:02.600><c> ask</c><00:20:03.120><c> what</c>

00:20:03.230 --> 00:20:03.240 align:start position:0%
knows conversely we can also ask what
 

00:20:03.240 --> 00:20:05.470 align:start position:0%
knows conversely we can also ask what
can<00:20:03.440><c> ethereum</c><00:20:04.039><c> do</c><00:20:04.520><c> that</c><00:20:04.760><c> no</c><00:20:05.039><c> amount</c><00:20:05.320><c> of</c>

00:20:05.470 --> 00:20:05.480 align:start position:0%
can ethereum do that no amount of
 

00:20:05.480 --> 00:20:07.669 align:start position:0%
can ethereum do that no amount of
cryptography<00:20:06.120><c> can</c><00:20:06.280><c> do</c><00:20:07.120><c> and</c><00:20:07.280><c> while</c><00:20:07.400><c> we're</c><00:20:07.559><c> just</c>

00:20:07.669 --> 00:20:07.679 align:start position:0%
cryptography can do and while we're just
 

00:20:07.679 --> 00:20:08.950 align:start position:0%
cryptography can do and while we're just
starting<00:20:07.960><c> to</c><00:20:08.360><c> understand</c><00:20:08.480><c> the</c><00:20:08.600><c> limits</c><00:20:08.840><c> and</c>

00:20:08.950 --> 00:20:08.960 align:start position:0%
starting to understand the limits and
 

00:20:08.960 --> 00:20:10.950 align:start position:0%
starting to understand the limits and
the<00:20:09.080><c> boundaries</c><00:20:09.480><c> of</c><00:20:09.640><c> these</c><00:20:09.840><c> Technologies</c><00:20:10.799><c> in</c>

00:20:10.950 --> 00:20:10.960 align:start position:0%
the boundaries of these Technologies in
 

00:20:10.960 --> 00:20:13.590 align:start position:0%
the boundaries of these Technologies in
short<00:20:11.520><c> we</c><00:20:11.640><c> might</c><00:20:11.840><c> say</c><00:20:12.080><c> that</c><00:20:12.480><c> blockchains</c><00:20:13.440><c> give</c>

00:20:13.590 --> 00:20:13.600 align:start position:0%
short we might say that blockchains give
 

00:20:13.600 --> 00:20:15.390 align:start position:0%
short we might say that blockchains give
us<00:20:13.880><c> things</c><00:20:14.120><c> like</c><00:20:14.320><c> consensus</c><00:20:15.120><c> data</c>

00:20:15.390 --> 00:20:15.400 align:start position:0%
us things like consensus data
 

00:20:15.400 --> 00:20:18.270 align:start position:0%
us things like consensus data
availability<00:20:16.080><c> and</c><00:20:16.520><c> ordering</c><00:20:17.520><c> a</c><00:20:17.640><c> ZK</c><00:20:18.039><c> proof</c>

00:20:18.270 --> 00:20:18.280 align:start position:0%
availability and ordering a ZK proof
 

00:20:18.280 --> 00:20:20.230 align:start position:0%
availability and ordering a ZK proof
allows<00:20:18.520><c> you</c><00:20:18.640><c> to</c><00:20:18.799><c> prove</c><00:20:19.440><c> any</c><00:20:19.720><c> fact</c><00:20:20.000><c> that</c><00:20:20.120><c> you</c>

00:20:20.230 --> 00:20:20.240 align:start position:0%
allows you to prove any fact that you
 

00:20:20.240 --> 00:20:22.909 align:start position:0%
allows you to prove any fact that you
want<00:20:20.679><c> about</c><00:20:20.960><c> a</c><00:20:21.159><c> hash</c><00:20:21.480><c> or</c><00:20:21.640><c> a</c><00:20:21.760><c> hash</c><00:20:22.000><c> pre-image</c><00:20:22.799><c> or</c>

00:20:22.909 --> 00:20:22.919 align:start position:0%
want about a hash or a hash pre-image or
 

00:20:22.919 --> 00:20:25.070 align:start position:0%
want about a hash or a hash pre-image or
a<00:20:23.039><c> public</c><00:20:23.360><c> key</c><00:20:23.919><c> but</c><00:20:24.120><c> how</c><00:20:24.240><c> do</c><00:20:24.360><c> we</c><00:20:24.520><c> decide</c><00:20:24.880><c> which</c>

00:20:25.070 --> 00:20:25.080 align:start position:0%
a public key but how do we decide which
 

00:20:25.080 --> 00:20:26.870 align:start position:0%
a public key but how do we decide which
hashes<00:20:25.400><c> and</c><00:20:25.559><c> public</c><00:20:25.799><c> keys</c><00:20:26.039><c> are</c><00:20:26.159><c> meaningful</c>

00:20:26.870 --> 00:20:26.880 align:start position:0%
hashes and public keys are meaningful
 

00:20:26.880 --> 00:20:29.870 align:start position:0%
hashes and public keys are meaningful
how<00:20:27.000><c> do</c><00:20:27.120><c> we</c><00:20:27.240><c> come</c><00:20:27.360><c> to</c><00:20:27.679><c> consensus</c><00:20:28.919><c> on</c><00:20:29.360><c> which</c><00:20:29.679><c> of</c>

00:20:29.870 --> 00:20:29.880 align:start position:0%
how do we come to consensus on which of
 

00:20:29.880 --> 00:20:32.390 align:start position:0%
how do we come to consensus on which of
these<00:20:30.080><c> hashes</c><00:20:30.880><c> actually</c><00:20:31.360><c> reflect</c><00:20:32.120><c> something</c>

00:20:32.390 --> 00:20:32.400 align:start position:0%
these hashes actually reflect something
 

00:20:32.400 --> 00:20:34.590 align:start position:0%
these hashes actually reflect something
that<00:20:32.520><c> we</c><00:20:32.640><c> care</c><00:20:32.840><c> about</c><00:20:33.000><c> in</c><00:20:33.080><c> the</c><00:20:33.360><c> world</c><00:20:34.360><c> how</c><00:20:34.480><c> can</c>

00:20:34.590 --> 00:20:34.600 align:start position:0%
that we care about in the world how can
 

00:20:34.600 --> 00:20:36.350 align:start position:0%
that we care about in the world how can
you<00:20:34.720><c> prove</c><00:20:34.960><c> that</c><00:20:35.080><c> something</c><00:20:35.440><c> didn't</c><00:20:35.880><c> happen</c>

00:20:36.350 --> 00:20:36.360 align:start position:0%
you prove that something didn't happen
 

00:20:36.360 --> 00:20:37.830 align:start position:0%
you prove that something didn't happen
you<00:20:36.559><c> can't</c><00:20:37.000><c> easily</c><00:20:37.360><c> do</c><00:20:37.559><c> this</c><00:20:37.679><c> with</c>

00:20:37.830 --> 00:20:37.840 align:start position:0%
you can't easily do this with
 

00:20:37.840 --> 00:20:39.310 align:start position:0%
you can't easily do this with
cryptography<00:20:38.440><c> except</c><00:20:38.640><c> in</c><00:20:38.760><c> very</c><00:20:39.000><c> special</c>

00:20:39.310 --> 00:20:39.320 align:start position:0%
cryptography except in very special
 

00:20:39.320 --> 00:20:41.750 align:start position:0%
cryptography except in very special
purpose<00:20:39.679><c> cases</c><00:20:40.320><c> or</c><00:20:40.520><c> how</c><00:20:40.679><c> can</c><00:20:40.799><c> you</c><00:20:40.960><c> determine</c>

00:20:41.750 --> 00:20:41.760 align:start position:0%
purpose cases or how can you determine
 

00:20:41.760 --> 00:20:43.669 align:start position:0%
purpose cases or how can you determine
which<00:20:41.919><c> of</c><00:20:42.120><c> two</c><00:20:42.600><c> cryptographically</c><00:20:43.320><c> sound</c>

00:20:43.669 --> 00:20:43.679 align:start position:0%
which of two cryptographically sound
 

00:20:43.679 --> 00:20:45.870 align:start position:0%
which of two cryptographically sound
operations<00:20:44.120><c> happen</c><00:20:44.440><c> first</c><00:20:45.120><c> or</c><00:20:45.280><c> that</c><00:20:45.520><c> data</c><00:20:45.760><c> has</c>

00:20:45.870 --> 00:20:45.880 align:start position:0%
operations happen first or that data has
 

00:20:45.880 --> 00:20:47.510 align:start position:0%
operations happen first or that data has
been<00:20:46.039><c> made</c><00:20:46.240><c> available</c><00:20:46.640><c> or</c><00:20:46.799><c> that</c><00:20:46.960><c> participants</c>

00:20:47.510 --> 00:20:47.520 align:start position:0%
been made available or that participants
 

00:20:47.520 --> 00:20:49.750 align:start position:0%
been made available or that participants
in<00:20:47.600><c> a</c><00:20:47.760><c> network</c><00:20:48.159><c> are</c><00:20:48.400><c> live</c><00:20:48.640><c> or</c><00:20:48.799><c> incentivized</c><00:20:49.600><c> to</c>

00:20:49.750 --> 00:20:49.760 align:start position:0%
in a network are live or incentivized to
 

00:20:49.760 --> 00:20:52.190 align:start position:0%
in a network are live or incentivized to
be<00:20:50.440><c> online</c><00:20:51.440><c> again</c><00:20:51.600><c> these</c><00:20:51.720><c> are</c><00:20:51.880><c> things</c><00:20:52.039><c> that</c>

00:20:52.190 --> 00:20:52.200 align:start position:0%
be online again these are things that
 

00:20:52.200 --> 00:20:53.870 align:start position:0%
be online again these are things that
pure<00:20:52.440><c> mathematics</c><00:20:53.000><c> and</c><00:20:53.159><c> pure</c><00:20:53.360><c> cryptography</c>

00:20:53.870 --> 00:20:53.880 align:start position:0%
pure mathematics and pure cryptography
 

00:20:53.880 --> 00:20:56.390 align:start position:0%
pure mathematics and pure cryptography
alone<00:20:54.159><c> cannot</c><00:20:54.480><c> do</c><00:20:55.120><c> but</c><00:20:55.280><c> blockchains</c><00:20:56.159><c> in</c>

00:20:56.390 --> 00:20:56.400 align:start position:0%
alone cannot do but blockchains in
 

00:20:56.400 --> 00:20:58.149 align:start position:0%
alone cannot do but blockchains in
Synergy<00:20:56.919><c> with</c><00:20:57.080><c> these</c><00:20:57.280><c> things</c><00:20:57.559><c> can</c><00:20:57.720><c> bring</c><00:20:58.000><c> as</c>

00:20:58.149 --> 00:20:58.159 align:start position:0%
Synergy with these things can bring as
 

00:20:58.159 --> 00:21:00.510 align:start position:0%
Synergy with these things can bring as
well<00:20:58.799><c> those</c><00:20:58.960><c> are</c><00:20:59.120><c> some</c><00:20:59.400><c> great</c><00:20:59.720><c> questions</c><00:21:00.240><c> gab</c>

00:21:00.510 --> 00:21:00.520 align:start position:0%
well those are some great questions gab
 

00:21:00.520 --> 00:21:02.190 align:start position:0%
well those are some great questions gab
sheep<00:21:00.919><c> and</c><00:21:01.159><c> I'm</c><00:21:01.280><c> sorry</c><00:21:01.480><c> to</c><00:21:01.640><c> cut</c><00:21:01.799><c> you</c><00:21:01.919><c> off</c><00:21:02.080><c> a</c>

00:21:02.190 --> 00:21:02.200 align:start position:0%
sheep and I'm sorry to cut you off a
 

00:21:02.200 --> 00:21:04.230 align:start position:0%
sheep and I'm sorry to cut you off a
little<00:21:02.400><c> bit</c><00:21:02.679><c> but</c><00:21:03.080><c> because</c><00:21:03.280><c> of</c><00:21:03.559><c> time</c><00:21:03.840><c> is</c><00:21:03.960><c> it</c><00:21:04.080><c> all</c>

00:21:04.230 --> 00:21:04.240 align:start position:0%
little bit but because of time is it all
 

00:21:04.240 --> 00:21:05.950 align:start position:0%
little bit but because of time is it all
right<00:21:04.400><c> if</c><00:21:04.520><c> we</c><00:21:04.640><c> can</c><00:21:04.840><c> move</c><00:21:05.039><c> on</c><00:21:05.159><c> to</c><00:21:05.320><c> the</c><00:21:05.480><c> Q&amp;A</c>

00:21:05.950 --> 00:21:05.960 align:start position:0%
right if we can move on to the Q&amp;A
 

00:21:05.960 --> 00:21:07.909 align:start position:0%
right if we can move on to the Q&amp;A
section<00:21:06.600><c> so</c><00:21:06.760><c> we</c><00:21:06.840><c> can</c><00:21:07.000><c> listen</c><00:21:07.240><c> to</c><00:21:07.400><c> a</c><00:21:07.520><c> bit</c><00:21:07.679><c> of</c><00:21:07.799><c> the</c>

00:21:07.909 --> 00:21:07.919 align:start position:0%
section so we can listen to a bit of the
 

00:21:07.919 --> 00:21:10.190 align:start position:0%
section so we can listen to a bit of the
questions<00:21:08.240><c> from</c><00:21:08.440><c> the</c><00:21:08.559><c> audience</c><00:21:09.280><c> for</c><00:21:09.440><c> sure</c>

00:21:10.190 --> 00:21:10.200 align:start position:0%
questions from the audience for sure
 

00:21:10.200 --> 00:21:12.750 align:start position:0%
questions from the audience for sure
yeah<00:21:10.440><c> so</c><00:21:10.880><c> to</c><00:21:11.039><c> sum</c><00:21:11.240><c> it</c><00:21:11.360><c> all</c><00:21:11.559><c> up</c><00:21:12.240><c> um</c><00:21:12.400><c> the</c><00:21:12.520><c> one</c>

00:21:12.750 --> 00:21:12.760 align:start position:0%
yeah so to sum it all up um the one
 

00:21:12.760 --> 00:21:14.070 align:start position:0%
yeah so to sum it all up um the one
challenge<00:21:13.120><c> that</c><00:21:13.240><c> I'll</c><00:21:13.400><c> give</c><00:21:13.520><c> to</c><00:21:13.640><c> everybody</c><00:21:13.960><c> is</c>

00:21:14.070 --> 00:21:14.080 align:start position:0%
challenge that I'll give to everybody is
 

00:21:14.080 --> 00:21:15.710 align:start position:0%
challenge that I'll give to everybody is
to<00:21:14.200><c> think</c><00:21:14.360><c> about</c><00:21:14.559><c> the</c><00:21:14.720><c> question</c><00:21:15.120><c> how</c><00:21:15.279><c> do</c><00:21:15.480><c> we</c>

00:21:15.710 --> 00:21:15.720 align:start position:0%
to think about the question how do we
 

00:21:15.720 --> 00:21:17.830 align:start position:0%
to think about the question how do we
compute<00:21:16.279><c> together</c><00:21:16.640><c> how</c><00:21:16.799><c> can</c><00:21:16.919><c> we</c><00:21:17.080><c> use</c><00:21:17.360><c> these</c>

00:21:17.830 --> 00:21:17.840 align:start position:0%
compute together how can we use these
 

00:21:17.840 --> 00:21:20.430 align:start position:0%
compute together how can we use these
Technologies<00:21:18.840><c> to</c><00:21:19.000><c> pull</c><00:21:19.200><c> forward</c><00:21:19.520><c> a</c><00:21:19.720><c> future</c>

00:21:20.430 --> 00:21:20.440 align:start position:0%
Technologies to pull forward a future
 

00:21:20.440 --> 00:21:23.029 align:start position:0%
Technologies to pull forward a future
where<00:21:21.000><c> multi-party</c><00:21:21.840><c> programming</c><00:21:22.760><c> actually</c>

00:21:23.029 --> 00:21:23.039 align:start position:0%
where multi-party programming actually
 

00:21:23.039 --> 00:21:24.830 align:start position:0%
where multi-party programming actually
reflects<00:21:23.440><c> the</c><00:21:23.559><c> natural</c><00:21:23.880><c> first</c><00:21:24.159><c> principles</c>

00:21:24.830 --> 00:21:24.840 align:start position:0%
reflects the natural first principles
 

00:21:24.840 --> 00:21:27.549 align:start position:0%
reflects the natural first principles
model<00:21:25.840><c> so</c><00:21:26.039><c> thank</c><00:21:26.200><c> you</c><00:21:26.400><c> everybody</c><00:21:27.000><c> and</c><00:21:27.240><c> we'll</c>

00:21:27.549 --> 00:21:27.559 align:start position:0%
model so thank you everybody and we'll
 

00:21:27.559 --> 00:21:31.149 align:start position:0%
model so thank you everybody and we'll
take<00:21:27.760><c> some</c><00:21:27.960><c> questions</c><00:21:28.320><c> now</c>

00:21:31.149 --> 00:21:31.159 align:start position:0%
 
 

00:21:31.159 --> 00:21:33.430 align:start position:0%
 
hello<00:21:31.440><c> hello</c><00:21:32.120><c> all</c><00:21:32.360><c> right</c><00:21:32.559><c> let's</c><00:21:32.760><c> hear</c><00:21:33.000><c> for</c><00:21:33.159><c> gub</c>

00:21:33.430 --> 00:21:33.440 align:start position:0%
hello hello all right let's hear for gub
 

00:21:33.440 --> 00:21:35.669 align:start position:0%
hello hello all right let's hear for gub
sheep<00:21:34.200><c> straight</c><00:21:34.520><c> away</c><00:21:34.760><c> our</c><00:21:35.000><c> first</c><00:21:35.279><c> question</c>

00:21:35.669 --> 00:21:35.679 align:start position:0%
sheep straight away our first question
 

00:21:35.679 --> 00:21:37.870 align:start position:0%
sheep straight away our first question
on<00:21:35.880><c> the</c><00:21:36.039><c> board</c><00:21:36.480><c> what</c><00:21:36.720><c> is</c><00:21:36.880><c> the</c><00:21:37.120><c> coolest</c><00:21:37.600><c> thing</c>

00:21:37.870 --> 00:21:37.880 align:start position:0%
on the board what is the coolest thing
 

00:21:37.880 --> 00:21:41.070 align:start position:0%
on the board what is the coolest thing
in<00:21:38.200><c> ZK</c><00:21:38.880><c> research</c><00:21:39.480><c> right</c><00:21:39.679><c> now</c><00:21:40.080><c> for</c><00:21:40.320><c> fast</c><00:21:40.679><c> client</c>

00:21:41.070 --> 00:21:41.080 align:start position:0%
in ZK research right now for fast client
 

00:21:41.080 --> 00:21:42.630 align:start position:0%
in ZK research right now for fast client
side

00:21:42.630 --> 00:21:42.640 align:start position:0%
side
 

00:21:42.640 --> 00:21:46.430 align:start position:0%
side
proving<00:21:43.640><c> yeah</c><00:21:43.919><c> so</c><00:21:44.480><c> I'm</c><00:21:45.080><c> extremely</c><00:21:45.760><c> interested</c>

00:21:46.430 --> 00:21:46.440 align:start position:0%
proving yeah so I'm extremely interested
 

00:21:46.440 --> 00:21:48.549 align:start position:0%
proving yeah so I'm extremely interested
in<00:21:46.760><c> some</c><00:21:47.039><c> of</c><00:21:47.200><c> the</c><00:21:47.480><c> projects</c><00:21:48.240><c> that</c><00:21:48.440><c> have</c>

00:21:48.549 --> 00:21:48.559 align:start position:0%
in some of the projects that have
 

00:21:48.559 --> 00:21:50.470 align:start position:0%
in some of the projects that have
started<00:21:48.840><c> to</c><00:21:49.120><c> really</c><00:21:49.400><c> take</c><00:21:49.799><c> client</c><00:21:50.279><c> side</c>

00:21:50.470 --> 00:21:50.480 align:start position:0%
started to really take client side
 

00:21:50.480 --> 00:21:52.789 align:start position:0%
started to really take client side
proving<00:21:50.960><c> seriously</c><00:21:51.559><c> I</c><00:21:51.640><c> think</c><00:21:51.919><c> that</c><00:21:52.440><c> because</c>

00:21:52.789 --> 00:21:52.799 align:start position:0%
proving seriously I think that because
 

00:21:52.799 --> 00:21:54.710 align:start position:0%
proving seriously I think that because
of<00:21:52.960><c> the</c><00:21:53.120><c> economic</c><00:21:53.600><c> incentives</c><00:21:54.279><c> of</c><00:21:54.480><c> things</c>

00:21:54.710 --> 00:21:54.720 align:start position:0%
of the economic incentives of things
 

00:21:54.720 --> 00:21:56.190 align:start position:0%
of the economic incentives of things
like<00:21:54.880><c> rollups</c><00:21:55.320><c> and</c><00:21:55.440><c> bridges</c><00:21:55.799><c> we've</c><00:21:55.919><c> seen</c><00:21:56.080><c> a</c>

00:21:56.190 --> 00:21:56.200 align:start position:0%
like rollups and bridges we've seen a
 

00:21:56.200 --> 00:21:58.909 align:start position:0%
like rollups and bridges we've seen a
lot<00:21:56.320><c> of</c><00:21:56.440><c> advances</c><00:21:57.320><c> on</c><00:21:57.880><c> making</c><00:21:58.240><c> Z</c><00:21:58.720><c> proof</c>

00:21:58.909 --> 00:21:58.919 align:start position:0%
lot of advances on making Z proof
 

00:21:58.919 --> 00:22:00.549 align:start position:0%
lot of advances on making Z proof
generation<00:21:59.360><c> very</c><00:21:59.600><c> efficient</c><00:22:00.000><c> on</c><00:22:00.240><c> big</c><00:22:00.400><c> and</c>

00:22:00.549 --> 00:22:00.559 align:start position:0%
generation very efficient on big and
 

00:22:00.559 --> 00:22:02.110 align:start position:0%
generation very efficient on big and
beefy<00:22:00.960><c> servers</c><00:22:01.559><c> you</c><00:22:01.640><c> know</c><00:22:01.799><c> things</c><00:22:02.000><c> like</c>

00:22:02.110 --> 00:22:02.120 align:start position:0%
beefy servers you know things like
 

00:22:02.120 --> 00:22:03.710 align:start position:0%
beefy servers you know things like
sequencers<00:22:02.720><c> or</c><00:22:02.880><c> or</c><00:22:03.000><c> block</c><00:22:03.240><c> producers</c><00:22:03.600><c> or</c>

00:22:03.710 --> 00:22:03.720 align:start position:0%
sequencers or or block producers or
 

00:22:03.720 --> 00:22:08.070 align:start position:0%
sequencers or or block producers or
things<00:22:03.919><c> like</c><00:22:04.080><c> that</c><00:22:04.880><c> um</c><00:22:05.880><c> because</c><00:22:06.840><c> of</c><00:22:07.760><c> the</c>

00:22:08.070 --> 00:22:08.080 align:start position:0%
things like that um because of the
 

00:22:08.080 --> 00:22:09.830 align:start position:0%
things like that um because of the
increased<00:22:08.520><c> focus</c><00:22:08.799><c> on</c><00:22:08.919><c> ZK</c><00:22:09.240><c> identity</c><00:22:09.600><c> by</c><00:22:09.720><c> the</c>

00:22:09.830 --> 00:22:09.840 align:start position:0%
increased focus on ZK identity by the
 

00:22:09.840 --> 00:22:11.390 align:start position:0%
increased focus on ZK identity by the
space<00:22:10.039><c> in</c><00:22:10.159><c> the</c><00:22:10.279><c> last</c><00:22:10.440><c> couple</c><00:22:10.640><c> of</c><00:22:10.799><c> years</c><00:22:11.240><c> we're</c>

00:22:11.390 --> 00:22:11.400 align:start position:0%
space in the last couple of years we're
 

00:22:11.400 --> 00:22:12.830 align:start position:0%
space in the last couple of years we're
starting<00:22:11.640><c> to</c><00:22:11.720><c> see</c><00:22:11.880><c> the</c><00:22:12.000><c> first</c><00:22:12.320><c> projects</c><00:22:12.679><c> from</c>

00:22:12.830 --> 00:22:12.840 align:start position:0%
starting to see the first projects from
 

00:22:12.840 --> 00:22:15.669 align:start position:0%
starting to see the first projects from
groups<00:22:13.120><c> like</c><00:22:13.279><c> Iden</c><00:22:13.640><c> 3</c><00:22:14.159><c> or</c><00:22:14.360><c> PSE</c><00:22:15.159><c> experimenting</c>

00:22:15.669 --> 00:22:15.679 align:start position:0%
groups like Iden 3 or PSE experimenting
 

00:22:15.679 --> 00:22:18.149 align:start position:0%
groups like Iden 3 or PSE experimenting
with<00:22:15.799><c> using</c><00:22:16.039><c> new</c><00:22:16.279><c> proof</c><00:22:16.679><c> systems</c><00:22:17.679><c> in</c><00:22:17.799><c> order</c><00:22:18.000><c> to</c>

00:22:18.149 --> 00:22:18.159 align:start position:0%
with using new proof systems in order to
 

00:22:18.159 --> 00:22:20.669 align:start position:0%
with using new proof systems in order to
build<00:22:19.000><c> fast</c><00:22:19.360><c> client</c><00:22:19.799><c> side</c><00:22:20.000><c> mobile</c><00:22:20.279><c> proving</c>

00:22:20.669 --> 00:22:20.679 align:start position:0%
build fast client side mobile proving
 

00:22:20.679 --> 00:22:23.149 align:start position:0%
build fast client side mobile proving
libraries<00:22:21.360><c> that</c><00:22:21.520><c> actually</c><00:22:21.720><c> run</c><00:22:22.000><c> natively</c><00:22:22.960><c> so</c>

00:22:23.149 --> 00:22:23.159 align:start position:0%
libraries that actually run natively so
 

00:22:23.159 --> 00:22:24.110 align:start position:0%
libraries that actually run natively so
I<00:22:23.240><c> think</c><00:22:23.360><c> that</c><00:22:23.440><c> there's</c><00:22:23.559><c> a</c><00:22:23.679><c> lot</c><00:22:23.760><c> of</c><00:22:23.880><c> lwh</c>

00:22:24.110 --> 00:22:24.120 align:start position:0%
I think that there's a lot of lwh
 

00:22:24.120 --> 00:22:27.110 align:start position:0%
I think that there's a lot of lwh
hanging<00:22:24.440><c> fruit</c><00:22:24.880><c> here</c><00:22:25.559><c> um</c><00:22:25.760><c> and</c><00:22:25.919><c> I</c><00:22:26.039><c> think</c><00:22:26.559><c> that</c>

00:22:27.110 --> 00:22:27.120 align:start position:0%
hanging fruit here um and I think that
 

00:22:27.120 --> 00:22:28.750 align:start position:0%
hanging fruit here um and I think that
uh<00:22:27.240><c> hopefully</c><00:22:27.679><c> one</c><00:22:27.799><c> of</c><00:22:27.919><c> these</c><00:22:28.039><c> teams</c><00:22:28.279><c> is</c><00:22:28.559><c> able</c>

00:22:28.750 --> 00:22:28.760 align:start position:0%
uh hopefully one of these teams is able
 

00:22:28.760 --> 00:22:31.350 align:start position:0%
uh hopefully one of these teams is able
to<00:22:29.440><c> uh</c><00:22:29.640><c> start</c><00:22:29.880><c> pulling</c><00:22:30.200><c> out</c><00:22:30.440><c> something</c><00:22:30.799><c> where</c>

00:22:31.350 --> 00:22:31.360 align:start position:0%
to uh start pulling out something where
 

00:22:31.360 --> 00:22:32.669 align:start position:0%
to uh start pulling out something where
someday<00:22:31.679><c> we</c><00:22:31.760><c> might</c><00:22:31.919><c> be</c><00:22:32.000><c> able</c><00:22:32.159><c> to</c><00:22:32.279><c> even</c><00:22:32.440><c> run</c><00:22:32.559><c> a</c>

00:22:32.669 --> 00:22:32.679 align:start position:0%
someday we might be able to even run a
 

00:22:32.679 --> 00:22:34.669 align:start position:0%
someday we might be able to even run a
zkv<00:22:33.440><c> on</c><00:22:33.520><c> the</c><00:22:33.640><c> phone</c><00:22:33.919><c> efficiently</c><00:22:34.480><c> I</c><00:22:34.559><c> think</c>

00:22:34.669 --> 00:22:34.679 align:start position:0%
zkv on the phone efficiently I think
 

00:22:34.679 --> 00:22:36.750 align:start position:0%
zkv on the phone efficiently I think
that<00:22:34.760><c> would</c><00:22:34.880><c> be</c><00:22:35.000><c> huge</c><00:22:35.159><c> for</c><00:22:35.279><c> the</c><00:22:35.440><c> space</c><00:22:36.000><c> and</c><00:22:36.440><c> um</c>

00:22:36.750 --> 00:22:36.760 align:start position:0%
that would be huge for the space and um
 

00:22:36.760 --> 00:22:38.710 align:start position:0%
that would be huge for the space and um
lots<00:22:36.960><c> of</c><00:22:37.120><c> research</c><00:22:37.440><c> needed</c><00:22:38.039><c> definitely</c><00:22:38.520><c> lots</c>

00:22:38.710 --> 00:22:38.720 align:start position:0%
lots of research needed definitely lots
 

00:22:38.720 --> 00:22:40.789 align:start position:0%
lots of research needed definitely lots
of<00:22:38.840><c> areas</c><00:22:39.200><c> for</c><00:22:39.480><c> experimenting</c><00:22:40.279><c> and</c><00:22:40.440><c> trying</c>

00:22:40.789 --> 00:22:40.799 align:start position:0%
of areas for experimenting and trying
 

00:22:40.799 --> 00:22:42.350 align:start position:0%
of areas for experimenting and trying
new<00:22:41.039><c> things</c><00:22:41.520><c> let's</c><00:22:41.679><c> go</c><00:22:41.799><c> to</c><00:22:41.960><c> the</c><00:22:42.080><c> second</c>

00:22:42.350 --> 00:22:42.360 align:start position:0%
new things let's go to the second
 

00:22:42.360 --> 00:22:43.669 align:start position:0%
new things let's go to the second
question<00:22:42.640><c> which</c><00:22:42.799><c> got</c><00:22:43.000><c> the</c><00:22:43.080><c> three</c><00:22:43.360><c> highest</c>

00:22:43.669 --> 00:22:43.679 align:start position:0%
question which got the three highest
 

00:22:43.679 --> 00:22:46.510 align:start position:0%
question which got the three highest
votes<00:22:44.320><c> will</c><00:22:44.679><c> this</c><00:22:44.919><c> enable</c><00:22:45.360><c> decentralized</c><00:22:46.039><c> llm</c>

00:22:46.510 --> 00:22:46.520 align:start position:0%
votes will this enable decentralized llm
 

00:22:46.520 --> 00:22:48.630 align:start position:0%
votes will this enable decentralized llm
into<00:22:46.919><c> inference</c><00:22:47.600><c> while</c><00:22:47.919><c> preserving</c><00:22:48.480><c> the</c>

00:22:48.630 --> 00:22:48.640 align:start position:0%
into inference while preserving the
 

00:22:48.640 --> 00:22:50.830 align:start position:0%
into inference while preserving the
privacy<00:22:48.960><c> of</c><00:22:49.080><c> user</c><00:22:49.400><c> prompts</c><00:22:50.039><c> if</c><00:22:50.200><c> so</c><00:22:50.480><c> how</c><00:22:50.640><c> far</c>

00:22:50.830 --> 00:22:50.840 align:start position:0%
privacy of user prompts if so how far
 

00:22:50.840 --> 00:22:52.710 align:start position:0%
privacy of user prompts if so how far
away<00:22:51.080><c> is</c><00:22:51.159><c> it</c><00:22:51.360><c> if</c><00:22:51.520><c> not</c><00:22:51.720><c> what</c><00:22:51.919><c> tech</c><00:22:52.120><c> do</c><00:22:52.240><c> we</c><00:22:52.480><c> still</c>

00:22:52.710 --> 00:22:52.720 align:start position:0%
away is it if not what tech do we still
 

00:22:52.720 --> 00:22:55.390 align:start position:0%
away is it if not what tech do we still
need<00:22:53.120><c> to</c><00:22:53.320><c> enable</c><00:22:53.799><c> this</c><00:22:54.799><c> yeah</c><00:22:55.000><c> this</c><00:22:55.080><c> is</c><00:22:55.200><c> a</c>

00:22:55.390 --> 00:22:55.400 align:start position:0%
need to enable this yeah this is a
 

00:22:55.400 --> 00:22:57.630 align:start position:0%
need to enable this yeah this is a
really<00:22:55.720><c> interesting</c><00:22:56.320><c> question</c><00:22:57.120><c> uh</c><00:22:57.279><c> I</c><00:22:57.360><c> think</c><00:22:57.520><c> a</c>

00:22:57.630 --> 00:22:57.640 align:start position:0%
really interesting question uh I think a
 

00:22:57.640 --> 00:22:59.430 align:start position:0%
really interesting question uh I think a
lot<00:22:57.799><c> of</c><00:22:57.919><c> folks</c><00:22:58.520><c> are</c><00:22:58.720><c> curious</c><00:22:59.080><c> about</c><00:22:59.240><c> what</c><00:22:59.360><c> the</c>

00:22:59.430 --> 00:22:59.440 align:start position:0%
lot of folks are curious about what the
 

00:22:59.440 --> 00:23:01.190 align:start position:0%
lot of folks are curious about what the
intersection<00:22:59.960><c> between</c><00:23:00.360><c> Technologies</c><00:23:01.039><c> like</c>

00:23:01.190 --> 00:23:01.200 align:start position:0%
intersection between Technologies like
 

00:23:01.200 --> 00:23:04.430 align:start position:0%
intersection between Technologies like
ZK<00:23:01.600><c> or</c><00:23:01.799><c> verif</c><00:23:02.640><c> verifiability</c><00:23:03.640><c> and</c><00:23:03.919><c> AI</c><00:23:04.279><c> is</c>

00:23:04.430 --> 00:23:04.440 align:start position:0%
ZK or verif verifiability and AI is
 

00:23:04.440 --> 00:23:07.149 align:start position:0%
ZK or verif verifiability and AI is
going<00:23:04.600><c> to</c><00:23:04.720><c> look</c><00:23:04.880><c> like</c><00:23:05.039><c> in</c><00:23:05.120><c> the</c><00:23:05.240><c> near</c><00:23:05.520><c> future</c><00:23:06.520><c> um</c>

00:23:07.149 --> 00:23:07.159 align:start position:0%
going to look like in the near future um
 

00:23:07.159 --> 00:23:10.070 align:start position:0%
going to look like in the near future um
in<00:23:07.520><c> general</c><00:23:08.520><c> I</c><00:23:08.840><c> am</c><00:23:09.200><c> I</c><00:23:09.320><c> have</c><00:23:09.440><c> two</c><00:23:09.600><c> minds</c><00:23:09.840><c> about</c>

00:23:10.070 --> 00:23:10.080 align:start position:0%
in general I am I have two minds about
 

00:23:10.080 --> 00:23:13.549 align:start position:0%
in general I am I have two minds about
this<00:23:10.440><c> I</c><00:23:10.600><c> think</c><00:23:11.120><c> that</c><00:23:12.120><c> trying</c><00:23:12.520><c> to</c><00:23:12.840><c> plug</c><00:23:13.120><c> in</c><00:23:13.320><c> our</c>

00:23:13.549 --> 00:23:13.559 align:start position:0%
this I think that trying to plug in our
 

00:23:13.559 --> 00:23:16.630 align:start position:0%
this I think that trying to plug in our
bleeding<00:23:14.120><c> edge</c><00:23:14.799><c> llms</c><00:23:15.640><c> or</c><00:23:15.840><c> bleeding</c><00:23:16.320><c> edge</c>

00:23:16.630 --> 00:23:16.640 align:start position:0%
bleeding edge llms or bleeding edge
 

00:23:16.640 --> 00:23:18.310 align:start position:0%
bleeding edge llms or bleeding edge
machine<00:23:16.919><c> learning</c><00:23:17.240><c> models</c><00:23:17.919><c> into</c>

00:23:18.310 --> 00:23:18.320 align:start position:0%
machine learning models into
 

00:23:18.320 --> 00:23:21.070 align:start position:0%
machine learning models into
programmable<00:23:19.120><c> cryptography</c><00:23:20.120><c> is</c><00:23:20.720><c> likely</c>

00:23:21.070 --> 00:23:21.080 align:start position:0%
programmable cryptography is likely
 

00:23:21.080 --> 00:23:23.590 align:start position:0%
programmable cryptography is likely
going<00:23:21.240><c> to</c><00:23:21.400><c> be</c><00:23:21.559><c> something</c><00:23:21.840><c> that</c><00:23:22.080><c> takes</c><00:23:23.080><c> uh</c><00:23:23.440><c> a</c>

00:23:23.590 --> 00:23:23.600 align:start position:0%
going to be something that takes uh a
 

00:23:23.600 --> 00:23:25.750 align:start position:0%
going to be something that takes uh a
lot<00:23:23.760><c> more</c><00:23:24.000><c> time</c><00:23:24.320><c> than</c><00:23:24.679><c> you</c><00:23:24.799><c> know</c><00:23:25.360><c> a</c><00:23:25.440><c> lot</c><00:23:25.559><c> of</c><00:23:25.640><c> the</c>

00:23:25.750 --> 00:23:25.760 align:start position:0%
lot more time than you know a lot of the
 

00:23:25.760 --> 00:23:26.950 align:start position:0%
lot more time than you know a lot of the
other<00:23:25.880><c> use</c><00:23:26.159><c> cases</c><00:23:26.360><c> that</c><00:23:26.480><c> we</c><00:23:26.600><c> might</c><00:23:26.799><c> have</c>

00:23:26.950 --> 00:23:26.960 align:start position:0%
other use cases that we might have
 

00:23:26.960 --> 00:23:28.710 align:start position:0%
other use cases that we might have
around<00:23:27.200><c> things</c><00:23:27.400><c> like</c><00:23:27.559><c> Identity</c><00:23:27.919><c> or</c><00:23:28.080><c> proof</c><00:23:28.600><c> in</c>

00:23:28.710 --> 00:23:28.720 align:start position:0%
around things like Identity or proof in
 

00:23:28.720 --> 00:23:31.110 align:start position:0%
around things like Identity or proof in
data<00:23:29.200><c> largely</c><00:23:29.600><c> because</c><00:23:29.880><c> AI</c><00:23:30.240><c> is</c><00:23:30.760><c> something</c>

00:23:31.110 --> 00:23:31.120 align:start position:0%
data largely because AI is something
 

00:23:31.120 --> 00:23:33.029 align:start position:0%
data largely because AI is something
that<00:23:31.480><c> will</c><00:23:31.720><c> eat</c><00:23:31.960><c> up</c><00:23:32.200><c> as</c><00:23:32.360><c> much</c><00:23:32.600><c> compute</c><00:23:32.960><c> as</c>

00:23:33.029 --> 00:23:33.039 align:start position:0%
that will eat up as much compute as
 

00:23:33.039 --> 00:23:34.630 align:start position:0%
that will eat up as much compute as
you're<00:23:33.200><c> willing</c><00:23:33.440><c> to</c><00:23:33.600><c> give</c><00:23:33.720><c> it</c><00:23:34.360><c> and</c><00:23:34.480><c> if</c>

00:23:34.630 --> 00:23:34.640 align:start position:0%
you're willing to give it and if
 

00:23:34.640 --> 00:23:36.149 align:start position:0%
you're willing to give it and if
programmable<00:23:35.120><c> cryptography</c><00:23:35.640><c> causes</c><00:23:35.919><c> you</c><00:23:36.000><c> to</c>

00:23:36.149 --> 00:23:36.159 align:start position:0%
programmable cryptography causes you to
 

00:23:36.159 --> 00:23:38.710 align:start position:0%
programmable cryptography causes you to
incur<00:23:36.480><c> like</c><00:23:36.559><c> a</c><00:23:36.720><c> 1,000x</c><00:23:37.559><c> overhead</c><00:23:38.400><c> then</c>

00:23:38.710 --> 00:23:38.720 align:start position:0%
incur like a 1,000x overhead then
 

00:23:38.720 --> 00:23:39.909 align:start position:0%
incur like a 1,000x overhead then
there's<00:23:38.919><c> many</c><00:23:39.080><c> use</c><00:23:39.360><c> cases</c><00:23:39.559><c> that</c><00:23:39.640><c> it's</c><00:23:39.760><c> just</c>

00:23:39.909 --> 00:23:39.919 align:start position:0%
there's many use cases that it's just
 

00:23:39.919 --> 00:23:42.669 align:start position:0%
there's many use cases that it's just
really<00:23:40.080><c> hard</c><00:23:40.279><c> to</c><00:23:40.520><c> to</c><00:23:40.720><c> justify</c><00:23:41.640><c> but</c><00:23:42.039><c> I</c><00:23:42.200><c> am</c><00:23:42.440><c> very</c>

00:23:42.669 --> 00:23:42.679 align:start position:0%
really hard to to justify but I am very
 

00:23:42.679 --> 00:23:45.029 align:start position:0%
really hard to to justify but I am very
interested<00:23:43.000><c> in</c><00:23:43.159><c> this</c><00:23:43.400><c> idea</c><00:23:44.039><c> that</c><00:23:44.480><c> perhaps</c><00:23:44.919><c> in</c>

00:23:45.029 --> 00:23:45.039 align:start position:0%
interested in this idea that perhaps in
 

00:23:45.039 --> 00:23:46.830 align:start position:0%
interested in this idea that perhaps in
the<00:23:45.200><c> future</c><00:23:45.679><c> where</c><00:23:46.080><c> a</c><00:23:46.200><c> lot</c><00:23:46.320><c> of</c><00:23:46.440><c> the</c><00:23:46.520><c> internet</c>

00:23:46.830 --> 00:23:46.840 align:start position:0%
the future where a lot of the internet
 

00:23:46.840 --> 00:23:48.510 align:start position:0%
the future where a lot of the internet
is<00:23:46.960><c> made</c><00:23:47.120><c> up</c><00:23:47.279><c> of</c><00:23:47.440><c> different</c><00:23:47.760><c> autonomous</c>

00:23:48.510 --> 00:23:48.520 align:start position:0%
is made up of different autonomous
 

00:23:48.520 --> 00:23:50.830 align:start position:0%
is made up of different autonomous
agents<00:23:48.919><c> or</c><00:23:49.080><c> machines</c><00:23:49.480><c> or</c><00:23:49.679><c> Bots</c><00:23:50.279><c> they</c><00:23:50.400><c> might</c><00:23:50.600><c> be</c>

00:23:50.830 --> 00:23:50.840 align:start position:0%
agents or machines or Bots they might be
 

00:23:50.840 --> 00:23:53.310 align:start position:0%
agents or machines or Bots they might be
speaking<00:23:51.400><c> in</c><00:23:51.640><c> cryptography</c><00:23:52.320><c> to</c><00:23:52.640><c> each</c><00:23:52.799><c> other</c>

00:23:53.310 --> 00:23:53.320 align:start position:0%
speaking in cryptography to each other
 

00:23:53.320 --> 00:23:55.950 align:start position:0%
speaking in cryptography to each other
so<00:23:53.559><c> how</c><00:23:53.760><c> Bots</c><00:23:54.159><c> might</c><00:23:54.360><c> make</c><00:23:54.640><c> sense</c><00:23:55.320><c> of</c><00:23:55.760><c> the</c>

00:23:55.950 --> 00:23:55.960 align:start position:0%
so how Bots might make sense of the
 

00:23:55.960 --> 00:23:58.070 align:start position:0%
so how Bots might make sense of the
semantic<00:23:56.520><c> contents</c><00:23:57.240><c> of</c><00:23:57.520><c> what</c><00:23:57.679><c> each</c><00:23:57.799><c> other</c><00:23:57.960><c> is</c>

00:23:58.070 --> 00:23:58.080 align:start position:0%
semantic contents of what each other is
 

00:23:58.080 --> 00:23:59.870 align:start position:0%
semantic contents of what each other is
saying<00:23:58.520><c> is</c><00:23:58.799><c> they</c><00:23:58.960><c> might</c><00:23:59.120><c> be</c><00:23:59.240><c> speaking</c><00:23:59.640><c> in</c>

00:23:59.870 --> 00:23:59.880 align:start position:0%
saying is they might be speaking in
 

00:23:59.880 --> 00:24:01.630 align:start position:0%
saying is they might be speaking in
proof<00:24:00.200><c> caring</c><00:24:00.480><c> data</c><00:24:00.679><c> sending</c><00:24:01.120><c> bits</c><00:24:01.440><c> of</c>

00:24:01.630 --> 00:24:01.640 align:start position:0%
proof caring data sending bits of
 

00:24:01.640 --> 00:24:03.789 align:start position:0%
proof caring data sending bits of
cryptographically<00:24:02.400><c> verifiable</c><00:24:03.039><c> things</c><00:24:03.679><c> you</c>

00:24:03.789 --> 00:24:03.799 align:start position:0%
cryptographically verifiable things you
 

00:24:03.799 --> 00:24:05.110 align:start position:0%
cryptographically verifiable things you
know<00:24:03.960><c> we</c><00:24:04.039><c> could</c><00:24:04.400><c> imagine</c><00:24:04.720><c> these</c><00:24:04.880><c> things</c>

00:24:05.110 --> 00:24:05.120 align:start position:0%
know we could imagine these things
 

00:24:05.120 --> 00:24:07.590 align:start position:0%
know we could imagine these things
combating<00:24:05.600><c> stuff</c><00:24:05.840><c> like</c><00:24:06.360><c> misinformation</c><00:24:07.360><c> or</c>

00:24:07.590 --> 00:24:07.600 align:start position:0%
combating stuff like misinformation or
 

00:24:07.600 --> 00:24:09.669 align:start position:0%
combating stuff like misinformation or
the<00:24:07.799><c> lack</c><00:24:08.200><c> of</c><00:24:08.600><c> interoperability</c><00:24:09.400><c> between</c>

00:24:09.669 --> 00:24:09.679 align:start position:0%
the lack of interoperability between
 

00:24:09.679 --> 00:24:11.269 align:start position:0%
the lack of interoperability between
different<00:24:09.919><c> Services</c><00:24:10.640><c> um</c><00:24:10.799><c> personally</c><00:24:11.120><c> I'm</c>

00:24:11.269 --> 00:24:11.279 align:start position:0%
different Services um personally I'm
 

00:24:11.279 --> 00:24:13.269 align:start position:0%
different Services um personally I'm
very<00:24:11.440><c> interested</c><00:24:11.799><c> in</c><00:24:12.000><c> that</c><00:24:12.760><c> interesting</c>

00:24:13.269 --> 00:24:13.279 align:start position:0%
very interested in that interesting
 

00:24:13.279 --> 00:24:14.990 align:start position:0%
very interested in that interesting
let's<00:24:13.480><c> go</c><00:24:13.600><c> on</c><00:24:13.760><c> we</c><00:24:13.919><c> got</c><00:24:14.159><c> time</c><00:24:14.320><c> for</c><00:24:14.559><c> maybe</c><00:24:14.760><c> one</c><00:24:14.880><c> or</c>

00:24:14.990 --> 00:24:15.000 align:start position:0%
let's go on we got time for maybe one or
 

00:24:15.000 --> 00:24:16.710 align:start position:0%
let's go on we got time for maybe one or
two<00:24:15.159><c> more</c><00:24:15.360><c> questions</c><00:24:16.120><c> why</c><00:24:16.360><c> haven't</c>

00:24:16.710 --> 00:24:16.720 align:start position:0%
two more questions why haven't
 

00:24:16.720 --> 00:24:18.789 align:start position:0%
two more questions why haven't
traditional<00:24:17.360><c> companies</c><00:24:17.919><c> invested</c><00:24:18.440><c> in</c><00:24:18.600><c> this</c>

00:24:18.789 --> 00:24:18.799 align:start position:0%
traditional companies invested in this
 

00:24:18.799 --> 00:24:20.750 align:start position:0%
traditional companies invested in this
area<00:24:19.039><c> of</c><00:24:19.159><c> research</c><00:24:19.559><c> why</c><00:24:19.679><c> do</c><00:24:19.760><c> you</c><00:24:19.880><c> think</c><00:24:20.080><c> G</c>

00:24:20.750 --> 00:24:20.760 align:start position:0%
area of research why do you think G
 

00:24:20.760 --> 00:24:24.590 align:start position:0%
area of research why do you think G
sheep<00:24:21.760><c> yeah</c><00:24:22.240><c> I</c><00:24:22.400><c> think</c><00:24:22.640><c> that</c><00:24:23.120><c> one</c><00:24:23.360><c> thing</c><00:24:23.600><c> which</c>

00:24:24.590 --> 00:24:24.600 align:start position:0%
sheep yeah I think that one thing which
 

00:24:24.600 --> 00:24:25.630 align:start position:0%
sheep yeah I think that one thing which
I<00:24:24.679><c> think</c><00:24:24.840><c> we'll</c><00:24:25.039><c> probably</c><00:24:25.320><c> also</c><00:24:25.480><c> be</c>

00:24:25.630 --> 00:24:25.640 align:start position:0%
I think we'll probably also be
 

00:24:25.640 --> 00:24:27.470 align:start position:0%
I think we'll probably also be
discussing<00:24:26.000><c> in</c><00:24:26.120><c> the</c><00:24:26.240><c> panel</c><00:24:26.559><c> following</c><00:24:27.039><c> this</c>

00:24:27.470 --> 00:24:27.480 align:start position:0%
discussing in the panel following this
 

00:24:27.480 --> 00:24:30.950 align:start position:0%
discussing in the panel following this
is<00:24:27.760><c> that</c><00:24:28.840><c> um</c><00:24:29.840><c> the</c><00:24:30.000><c> reality</c><00:24:30.440><c> is</c><00:24:30.600><c> that</c><00:24:30.760><c> the</c>

00:24:30.950 --> 00:24:30.960 align:start position:0%
is that um the reality is that the
 

00:24:30.960 --> 00:24:33.669 align:start position:0%
is that um the reality is that the
economic<00:24:31.480><c> incentive</c><00:24:32.000><c> over</c><00:24:32.200><c> the</c><00:24:32.399><c> last</c><00:24:32.720><c> 5</c><00:24:32.960><c> years</c>

00:24:33.669 --> 00:24:33.679 align:start position:0%
economic incentive over the last 5 years
 

00:24:33.679 --> 00:24:35.870 align:start position:0%
economic incentive over the last 5 years
has<00:24:33.880><c> driven</c><00:24:34.480><c> research</c><00:24:34.960><c> and</c><00:24:35.159><c> development</c>

00:24:35.870 --> 00:24:35.880 align:start position:0%
has driven research and development
 

00:24:35.880 --> 00:24:39.029 align:start position:0%
has driven research and development
largely<00:24:36.520><c> towards</c><00:24:37.200><c> use</c><00:24:37.600><c> cases</c><00:24:38.039><c> that</c><00:24:38.279><c> involve</c>

00:24:39.029 --> 00:24:39.039 align:start position:0%
largely towards use cases that involve
 

00:24:39.039 --> 00:24:41.350 align:start position:0%
largely towards use cases that involve
things<00:24:39.279><c> like</c><00:24:39.399><c> server</c><00:24:39.880><c> side</c><00:24:40.080><c> proving</c><00:24:40.919><c> and</c><00:24:41.200><c> with</c>

00:24:41.350 --> 00:24:41.360 align:start position:0%
things like server side proving and with
 

00:24:41.360 --> 00:24:43.269 align:start position:0%
things like server side proving and with
a<00:24:41.480><c> focus</c><00:24:41.720><c> on</c><00:24:41.919><c> verifiability</c><00:24:42.720><c> technology</c>

00:24:43.269 --> 00:24:43.279 align:start position:0%
a focus on verifiability technology
 

00:24:43.279 --> 00:24:45.350 align:start position:0%
a focus on verifiability technology
rather<00:24:43.480><c> than</c><00:24:43.679><c> confidentiality</c><00:24:44.520><c> technology</c>

00:24:45.350 --> 00:24:45.360 align:start position:0%
rather than confidentiality technology
 

00:24:45.360 --> 00:24:46.750 align:start position:0%
rather than confidentiality technology
in<00:24:45.520><c> particular</c><00:24:45.960><c> because</c><00:24:46.159><c> blockchains</c><00:24:46.640><c> have</c>

00:24:46.750 --> 00:24:46.760 align:start position:0%
in particular because blockchains have
 

00:24:46.760 --> 00:24:48.830 align:start position:0%
in particular because blockchains have
created<00:24:47.120><c> such</c><00:24:47.480><c> a</c><00:24:47.679><c> phenomenal</c><00:24:48.200><c> Financial</c>

00:24:48.830 --> 00:24:48.840 align:start position:0%
created such a phenomenal Financial
 

00:24:48.840 --> 00:24:51.430 align:start position:0%
created such a phenomenal Financial
incentive<00:24:49.360><c> to</c><00:24:49.640><c> actually</c><00:24:49.960><c> build</c><00:24:50.279><c> out</c><00:24:50.640><c> these</c>

00:24:51.430 --> 00:24:51.440 align:start position:0%
incentive to actually build out these
 

00:24:51.440 --> 00:24:53.549 align:start position:0%
incentive to actually build out these
businesses<00:24:52.440><c> a</c><00:24:52.559><c> lot</c><00:24:52.640><c> of</c><00:24:52.760><c> the</c><00:24:52.919><c> oxygen</c><00:24:53.320><c> in</c><00:24:53.440><c> the</c>

00:24:53.549 --> 00:24:53.559 align:start position:0%
businesses a lot of the oxygen in the
 

00:24:53.559 --> 00:24:55.870 align:start position:0%
businesses a lot of the oxygen in the
room<00:24:53.760><c> gets</c><00:24:53.960><c> sucked</c><00:24:54.320><c> in</c><00:24:54.520><c> that</c><00:24:54.720><c> direction</c><00:24:55.679><c> so</c>

00:24:55.870 --> 00:24:55.880 align:start position:0%
room gets sucked in that direction so
 

00:24:55.880 --> 00:24:57.669 align:start position:0%
room gets sucked in that direction so
what<00:24:56.000><c> we've</c><00:24:56.159><c> been</c><00:24:56.279><c> trying</c><00:24:56.480><c> to</c><00:24:56.640><c> do</c><00:24:57.080><c> at</c><00:24:57.200><c> zerx</c>

00:24:57.669 --> 00:24:57.679 align:start position:0%
what we've been trying to do at zerx
 

00:24:57.679 --> 00:24:59.389 align:start position:0%
what we've been trying to do at zerx
Park<00:24:57.880><c> and</c><00:24:58.039><c> and</c><00:24:58.120><c> a</c><00:24:58.559><c> a</c><00:24:58.640><c> couple</c><00:24:58.840><c> of</c><00:24:58.960><c> our</c><00:24:59.200><c> other</c>

00:24:59.389 --> 00:24:59.399 align:start position:0%
Park and and a a couple of our other
 

00:24:59.399 --> 00:25:01.990 align:start position:0%
Park and and a a couple of our other
partners<00:25:00.159><c> is</c><00:25:00.720><c> start</c><00:25:01.000><c> to</c><00:25:01.200><c> direct</c><00:25:01.559><c> attention</c>

00:25:01.990 --> 00:25:02.000 align:start position:0%
partners is start to direct attention
 

00:25:02.000 --> 00:25:04.149 align:start position:0%
partners is start to direct attention
towards<00:25:02.360><c> these</c><00:25:02.520><c> other</c><00:25:03.039><c> further</c><00:25:03.440><c> out</c>

00:25:04.149 --> 00:25:04.159 align:start position:0%
towards these other further out
 

00:25:04.159 --> 00:25:05.909 align:start position:0%
towards these other further out
potentially<00:25:04.640><c> more</c><00:25:04.840><c> speculative</c><00:25:05.360><c> use</c><00:25:05.600><c> cases</c>

00:25:05.909 --> 00:25:05.919 align:start position:0%
potentially more speculative use cases
 

00:25:05.919 --> 00:25:07.590 align:start position:0%
potentially more speculative use cases
use<00:25:06.120><c> cases</c><00:25:06.440><c> that</c><00:25:06.559><c> don't</c><00:25:06.760><c> have</c><00:25:06.919><c> as</c><00:25:07.240><c> strong</c><00:25:07.440><c> of</c>

00:25:07.590 --> 00:25:07.600 align:start position:0%
use cases that don't have as strong of
 

00:25:07.600 --> 00:25:09.350 align:start position:0%
use cases that don't have as strong of
an<00:25:07.760><c> immediate</c><00:25:08.240><c> financial</c><00:25:08.640><c> incentivization</c>

00:25:09.350 --> 00:25:09.360 align:start position:0%
an immediate financial incentivization
 

00:25:09.360 --> 00:25:11.190 align:start position:0%
an immediate financial incentivization
Loop<00:25:10.080><c> um</c><00:25:10.200><c> but</c><00:25:10.279><c> I</c><00:25:10.360><c> think</c><00:25:10.480><c> we're</c><00:25:10.600><c> going</c><00:25:10.679><c> to</c><00:25:11.000><c> see</c>

00:25:11.190 --> 00:25:11.200 align:start position:0%
Loop um but I think we're going to see
 

00:25:11.200 --> 00:25:13.029 align:start position:0%
Loop um but I think we're going to see
this<00:25:11.360><c> pattern</c><00:25:11.640><c> play</c><00:25:11.799><c> out</c><00:25:11.960><c> more</c><00:25:12.080><c> and</c><00:25:12.200><c> more</c><00:25:12.600><c> as</c>

00:25:13.029 --> 00:25:13.039 align:start position:0%
this pattern play out more and more as
 

00:25:13.039 --> 00:25:14.389 align:start position:0%
this pattern play out more and more as
these<00:25:13.200><c> use</c><00:25:13.480><c> cases</c><00:25:13.679><c> start</c><00:25:13.840><c> to</c><00:25:13.960><c> become</c><00:25:14.120><c> a</c>

00:25:14.389 --> 00:25:14.399 align:start position:0%
these use cases start to become a
 

00:25:14.399 --> 00:25:16.430 align:start position:0%
these use cases start to become a
reality<00:25:15.399><c> excellent</c><00:25:15.799><c> that's</c><00:25:15.919><c> all</c><00:25:16.039><c> the</c><00:25:16.159><c> time</c><00:25:16.320><c> we</c>

00:25:16.430 --> 00:25:16.440 align:start position:0%
reality excellent that's all the time we
 

00:25:16.440 --> 00:25:17.750 align:start position:0%
reality excellent that's all the time we
have<00:25:16.520><c> for</c><00:25:16.720><c> Q&amp;A</c><00:25:17.080><c> let's</c><00:25:17.240><c> give</c><00:25:17.360><c> our</c><00:25:17.480><c> speaker</c>

00:25:17.750 --> 00:25:17.760 align:start position:0%
have for Q&amp;A let's give our speaker
 

00:25:17.760 --> 00:25:19.960 align:start position:0%
have for Q&amp;A let's give our speaker
another