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:11.070 align:start position:0%
 
[Music]

00:00:11.070 --> 00:00:11.080 align:start position:0%
 
 

00:00:11.080 --> 00:00:13.870 align:start position:0%
 
great<00:00:11.719><c> uh</c><00:00:12.120><c> very</c><00:00:12.360><c> happy</c><00:00:12.599><c> to</c><00:00:12.719><c> be</c><00:00:12.920><c> here</c><00:00:13.160><c> everyone</c>

00:00:13.870 --> 00:00:13.880 align:start position:0%
great uh very happy to be here everyone
 

00:00:13.880 --> 00:00:16.830 align:start position:0%
great uh very happy to be here everyone
uh<00:00:14.040><c> once</c><00:00:14.280><c> again</c><00:00:14.599><c> I'm</c><00:00:14.799><c> Karen</c><00:00:15.120><c> scarbro</c><00:00:15.879><c> I</c><00:00:16.400><c> lead</c>

00:00:16.830 --> 00:00:16.840 align:start position:0%
uh once again I'm Karen scarbro I lead
 

00:00:16.840 --> 00:00:19.070 align:start position:0%
uh once again I'm Karen scarbro I lead
the<00:00:17.160><c> Enterprise</c><00:00:17.960><c> ethereum</c><00:00:18.439><c> alliance's</c>

00:00:19.070 --> 00:00:19.080 align:start position:0%
the Enterprise ethereum alliance's
 

00:00:19.080 --> 00:00:21.269 align:start position:0%
the Enterprise ethereum alliance's
executive<00:00:19.560><c> director</c><00:00:20.039><c> right</c><00:00:20.160><c> now</c><00:00:20.840><c> and</c><00:00:20.960><c> in</c><00:00:21.119><c> my</c>

00:00:21.269 --> 00:00:21.279 align:start position:0%
executive director right now and in my
 

00:00:21.279 --> 00:00:24.109 align:start position:0%
executive director right now and in my
day<00:00:21.560><c> job</c><00:00:22.160><c> I</c><00:00:22.320><c> work</c><00:00:22.560><c> for</c><00:00:23.080><c> Microsoft</c><00:00:23.640><c> so</c><00:00:23.760><c> I</c><00:00:23.840><c> have</c><00:00:23.920><c> a</c>

00:00:24.109 --> 00:00:24.119 align:start position:0%
day job I work for Microsoft so I have a
 

00:00:24.119 --> 00:00:26.429 align:start position:0%
day job I work for Microsoft so I have a
very<00:00:24.680><c> uh</c><00:00:24.840><c> good</c><00:00:25.080><c> hand</c><00:00:25.400><c> on</c><00:00:25.640><c> how</c><00:00:25.880><c> some</c><00:00:26.039><c> of</c><00:00:26.240><c> the</c>

00:00:26.429 --> 00:00:26.439 align:start position:0%
very uh good hand on how some of the
 

00:00:26.439 --> 00:00:28.910 align:start position:0%
very uh good hand on how some of the
largest<00:00:26.840><c> Enterprises</c><00:00:27.480><c> are</c><00:00:27.640><c> viewing</c><00:00:28.320><c> ethereum</c>

00:00:28.910 --> 00:00:28.920 align:start position:0%
largest Enterprises are viewing ethereum
 

00:00:28.920 --> 00:00:31.429 align:start position:0%
largest Enterprises are viewing ethereum
today<00:00:29.679><c> and</c><00:00:30.039><c> what</c><00:00:30.160><c> can</c><00:00:30.279><c> be</c><00:00:30.439><c> done</c><00:00:30.720><c> to</c><00:00:31.320><c> uh</c>

00:00:31.429 --> 00:00:31.439 align:start position:0%
today and what can be done to uh
 

00:00:31.439 --> 00:00:34.310 align:start position:0%
today and what can be done to uh
increase<00:00:31.960><c> ethereum</c><00:00:32.559><c> adoption</c><00:00:33.360><c> and</c><00:00:33.680><c> awareness</c>

00:00:34.310 --> 00:00:34.320 align:start position:0%
increase ethereum adoption and awareness
 

00:00:34.320 --> 00:00:37.470 align:start position:0%
increase ethereum adoption and awareness
in<00:00:34.440><c> the</c><00:00:34.719><c> community</c><00:00:35.719><c> so</c><00:00:36.399><c> I</c><00:00:36.960><c> definitely</c><00:00:37.320><c> think</c>

00:00:37.470 --> 00:00:37.480 align:start position:0%
in the community so I definitely think
 

00:00:37.480 --> 00:00:39.790 align:start position:0%
in the community so I definitely think
it's<00:00:37.600><c> worth</c><00:00:37.800><c> it</c><00:00:37.960><c> to</c><00:00:38.120><c> go</c><00:00:38.239><c> over</c><00:00:38.559><c> what</c><00:00:38.920><c> exactly</c><00:00:39.520><c> is</c>

00:00:39.790 --> 00:00:39.800 align:start position:0%
it's worth it to go over what exactly is
 

00:00:39.800 --> 00:00:42.470 align:start position:0%
it's worth it to go over what exactly is
the<00:00:40.039><c> Enterprise</c><00:00:40.640><c> ethereum</c><00:00:41.079><c> Alliance</c><00:00:41.680><c> and</c><00:00:42.200><c> uh</c>

00:00:42.470 --> 00:00:42.480 align:start position:0%
the Enterprise ethereum Alliance and uh
 

00:00:42.480 --> 00:00:44.790 align:start position:0%
the Enterprise ethereum Alliance and uh
if<00:00:42.800><c> you</c><00:00:43.320><c> haven't</c><00:00:43.600><c> heard</c><00:00:43.879><c> about</c><00:00:44.079><c> us</c><00:00:44.360><c> before</c><00:00:44.680><c> we</c>

00:00:44.790 --> 00:00:44.800 align:start position:0%
if you haven't heard about us before we
 

00:00:44.800 --> 00:00:47.630 align:start position:0%
if you haven't heard about us before we
were<00:00:45.079><c> actually</c><00:00:45.559><c> an</c><00:00:45.760><c> organization</c><00:00:46.680><c> started</c>

00:00:47.630 --> 00:00:47.640 align:start position:0%
were actually an organization started
 

00:00:47.640 --> 00:00:49.189 align:start position:0%
were actually an organization started
way<00:00:47.879><c> back</c><00:00:48.079><c> in</c>

00:00:49.189 --> 00:00:49.199 align:start position:0%
way back in
 

00:00:49.199 --> 00:00:52.630 align:start position:0%
way back in
2017<00:00:50.199><c> uh</c><00:00:50.399><c> at</c><00:00:50.600><c> that</c><00:00:50.879><c> time</c><00:00:51.480><c> a</c><00:00:51.600><c> lot</c><00:00:51.760><c> of</c><00:00:52.079><c> Enterprise</c>

00:00:52.630 --> 00:00:52.640 align:start position:0%
2017 uh at that time a lot of Enterprise
 

00:00:52.640 --> 00:00:54.389 align:start position:0%
2017 uh at that time a lot of Enterprise
use<00:00:52.960><c> cases</c><00:00:53.280><c> were</c><00:00:53.440><c> going</c><00:00:53.680><c> on</c><00:00:54.039><c> private</c>

00:00:54.389 --> 00:00:54.399 align:start position:0%
use cases were going on private
 

00:00:54.399 --> 00:00:56.110 align:start position:0%
use cases were going on private
blockchains<00:00:55.160><c> there</c><00:00:55.280><c> was</c><00:00:55.399><c> a</c><00:00:55.559><c> number</c><00:00:55.840><c> of</c>

00:00:56.110 --> 00:00:56.120 align:start position:0%
blockchains there was a number of
 

00:00:56.120 --> 00:00:57.990 align:start position:0%
blockchains there was a number of
standards<00:00:57.000><c> and</c><00:00:57.359><c> uh</c><00:00:57.480><c> technical</c>

00:00:57.990 --> 00:00:58.000 align:start position:0%
standards and uh technical
 

00:00:58.000 --> 00:00:59.509 align:start position:0%
standards and uh technical
specifications<00:00:58.879><c> that</c><00:00:59.000><c> needed</c><00:00:59.280><c> to</c><00:00:59.399><c> be</c>

00:00:59.509 --> 00:00:59.519 align:start position:0%
specifications that needed to be
 

00:00:59.519 --> 00:01:02.029 align:start position:0%
specifications that needed to be
developed<00:01:00.120><c> in</c><00:01:00.199><c> the</c><00:01:00.359><c> industry</c><00:01:01.280><c> and</c><00:01:01.480><c> ethereum</c>

00:01:02.029 --> 00:01:02.039 align:start position:0%
developed in the industry and ethereum
 

00:01:02.039 --> 00:01:03.470 align:start position:0%
developed in the industry and ethereum
actually<00:01:02.280><c> put</c><00:01:02.600><c> together</c><00:01:02.879><c> the</c><00:01:03.039><c> largest</c>

00:01:03.470 --> 00:01:03.480 align:start position:0%
actually put together the largest
 

00:01:03.480 --> 00:01:05.950 align:start position:0%
actually put together the largest
consortiums<00:01:04.159><c> of</c><00:01:04.680><c> uh</c><00:01:04.839><c> companies</c><00:01:05.320><c> to</c><00:01:05.479><c> be</c><00:01:05.680><c> able</c>

00:01:05.950 --> 00:01:05.960 align:start position:0%
consortiums of uh companies to be able
 

00:01:05.960 --> 00:01:09.390 align:start position:0%
consortiums of uh companies to be able
to<00:01:06.720><c> uh</c><00:01:06.880><c> start</c><00:01:07.280><c> acting</c><00:01:07.720><c> on</c><00:01:08.000><c> that</c><00:01:08.240><c> activity</c><00:01:08.799><c> so</c>

00:01:09.390 --> 00:01:09.400 align:start position:0%
to uh start acting on that activity so
 

00:01:09.400 --> 00:01:11.670 align:start position:0%
to uh start acting on that activity so
we<00:01:09.560><c> are</c><00:01:09.680><c> a</c><00:01:09.880><c> nonprofit</c><00:01:10.759><c> membership</c><00:01:11.280><c> based</c>

00:01:11.670 --> 00:01:11.680 align:start position:0%
we are a nonprofit membership based
 

00:01:11.680 --> 00:01:14.550 align:start position:0%
we are a nonprofit membership based
organization<00:01:12.600><c> that</c><00:01:12.720><c> is</c><00:01:13.000><c> advocating</c><00:01:13.680><c> for</c><00:01:14.280><c> the</c>

00:01:14.550 --> 00:01:14.560 align:start position:0%
organization that is advocating for the
 

00:01:14.560 --> 00:01:16.910 align:start position:0%
organization that is advocating for the
adoption<00:01:14.960><c> of</c><00:01:15.119><c> ethereum</c><00:01:15.759><c> in</c><00:01:16.119><c> business</c><00:01:16.720><c> and</c>

00:01:16.910 --> 00:01:16.920 align:start position:0%
adoption of ethereum in business and
 

00:01:16.920 --> 00:01:19.390 align:start position:0%
adoption of ethereum in business and
ultimately<00:01:17.520><c> our</c><00:01:17.759><c> goal</c><00:01:18.479><c> is</c><00:01:18.640><c> to</c><00:01:18.799><c> make</c><00:01:18.960><c> it</c><00:01:19.119><c> so</c>

00:01:19.390 --> 00:01:19.400 align:start position:0%
ultimately our goal is to make it so
 

00:01:19.400 --> 00:01:21.149 align:start position:0%
ultimately our goal is to make it so
clear<00:01:19.640><c> for</c><00:01:19.920><c> business</c><00:01:20.439><c> that</c><00:01:20.600><c> whenever</c><00:01:21.000><c> they</c>

00:01:21.149 --> 00:01:21.159 align:start position:0%
clear for business that whenever they
 

00:01:21.159 --> 00:01:24.190 align:start position:0%
clear for business that whenever they
choose<00:01:21.600><c> to</c><00:01:22.040><c> do</c><00:01:22.320><c> business</c><00:01:22.640><c> in</c><00:01:22.880><c> web</c><00:01:23.159><c> 3</c><00:01:23.560><c> ethereum</c>

00:01:24.190 --> 00:01:24.200 align:start position:0%
choose to do business in web 3 ethereum
 

00:01:24.200 --> 00:01:26.789 align:start position:0%
choose to do business in web 3 ethereum
and<00:01:24.320><c> the</c><00:01:24.400><c> layer</c><00:01:24.680><c> 2</c><00:01:25.040><c> ecosystem</c><00:01:26.040><c> is</c><00:01:26.240><c> the</c><00:01:26.520><c> very</c>

00:01:26.789 --> 00:01:26.799 align:start position:0%
and the layer 2 ecosystem is the very
 

00:01:26.799 --> 00:01:29.190 align:start position:0%
and the layer 2 ecosystem is the very
clear<00:01:27.360><c> choice</c><00:01:27.960><c> that</c><00:01:28.159><c> they</c><00:01:28.360><c> choose</c><00:01:28.640><c> to</c><00:01:28.840><c> go</c><00:01:29.000><c> with</c>

00:01:29.190 --> 00:01:29.200 align:start position:0%
clear choice that they choose to go with
 

00:01:29.200 --> 00:01:31.310 align:start position:0%
clear choice that they choose to go with
for<00:01:29.400><c> where</c><00:01:29.560><c> they'd</c><00:01:29.720><c> like</c><00:01:30.040><c> to</c><00:01:30.200><c> build</c><00:01:30.759><c> uh</c><00:01:30.960><c> invest</c>

00:01:31.310 --> 00:01:31.320 align:start position:0%
for where they'd like to build uh invest
 

00:01:31.320 --> 00:01:35.630 align:start position:0%
for where they'd like to build uh invest
their<00:01:31.560><c> time</c><00:01:31.920><c> use</c><00:01:32.320><c> cases</c><00:01:33.119><c> Etc</c><00:01:34.119><c> so</c><00:01:34.880><c> core</c><00:01:35.280><c> parts</c>

00:01:35.630 --> 00:01:35.640 align:start position:0%
their time use cases Etc so core parts
 

00:01:35.640 --> 00:01:39.469 align:start position:0%
their time use cases Etc so core parts
of<00:01:36.079><c> what</c><00:01:36.240><c> we</c><00:01:36.399><c> do</c><00:01:37.399><c> uh</c><00:01:37.640><c> we</c><00:01:38.159><c> host</c><00:01:38.840><c> uh</c><00:01:39.000><c> events</c>

00:01:39.469 --> 00:01:39.479 align:start position:0%
of what we do uh we host uh events
 

00:01:39.479 --> 00:01:40.990 align:start position:0%
of what we do uh we host uh events
throughout<00:01:39.880><c> the</c><00:01:40.000><c> year</c><00:01:40.240><c> that's</c><00:01:40.439><c> been</c><00:01:40.720><c> one</c>

00:01:40.990 --> 00:01:41.000 align:start position:0%
throughout the year that's been one
 

00:01:41.000 --> 00:01:44.389 align:start position:0%
throughout the year that's been one
thing<00:01:41.600><c> that</c><00:01:42.000><c> has</c><00:01:42.680><c> uh</c><00:01:42.880><c> been</c><00:01:43.159><c> a</c><00:01:43.399><c> a</c><00:01:43.520><c> huge</c><00:01:43.880><c> pickup</c>

00:01:44.389 --> 00:01:44.399 align:start position:0%
thing that has uh been a a huge pickup
 

00:01:44.399 --> 00:01:46.429 align:start position:0%
thing that has uh been a a huge pickup
this<00:01:44.560><c> year</c><00:01:44.960><c> we</c><00:01:45.079><c> want</c><00:01:45.200><c> to</c><00:01:45.360><c> be</c><00:01:45.560><c> right</c><00:01:45.880><c> alongside</c>

00:01:46.429 --> 00:01:46.439 align:start position:0%
this year we want to be right alongside
 

00:01:46.439 --> 00:01:48.310 align:start position:0%
this year we want to be right alongside
the<00:01:46.560><c> ethereum</c><00:01:47.079><c> community</c><00:01:47.640><c> so</c><00:01:47.799><c> you'll</c><00:01:48.000><c> see</c><00:01:48.200><c> us</c>

00:01:48.310 --> 00:01:48.320 align:start position:0%
the ethereum community so you'll see us
 

00:01:48.320 --> 00:01:49.990 align:start position:0%
the ethereum community so you'll see us
out<00:01:48.520><c> at</c><00:01:48.640><c> eth</c><00:01:48.920><c> Denver</c>

00:01:49.990 --> 00:01:50.000 align:start position:0%
out at eth Denver
 

00:01:50.000 --> 00:01:52.749 align:start position:0%
out at eth Denver
ethcc<00:01:51.000><c> uh</c><00:01:51.119><c> we</c><00:01:51.240><c> had</c><00:01:51.360><c> a</c><00:01:51.520><c> major</c><00:01:51.880><c> event</c><00:01:52.240><c> here</c><00:01:52.560><c> this</c>

00:01:52.749 --> 00:01:52.759 align:start position:0%
ethcc uh we had a major event here this
 

00:01:52.759 --> 00:01:55.149 align:start position:0%
ethcc uh we had a major event here this
Monday<00:01:53.280><c> with</c><00:01:53.399><c> our</c><00:01:53.640><c> EA</c><00:01:54.320><c> industry</c><00:01:54.799><c> day</c><00:01:55.040><c> that</c>

00:01:55.149 --> 00:01:55.159 align:start position:0%
Monday with our EA industry day that
 

00:01:55.159 --> 00:01:57.469 align:start position:0%
Monday with our EA industry day that
I'll<00:01:55.320><c> talk</c><00:01:55.520><c> about</c><00:01:55.719><c> a</c><00:01:55.840><c> little</c><00:01:56.039><c> more</c><00:01:56.920><c> uh</c><00:01:57.039><c> token</c>

00:01:57.469 --> 00:01:57.479 align:start position:0%
I'll talk about a little more uh token
 

00:01:57.479 --> 00:02:01.149 align:start position:0%
I'll talk about a little more uh token
2049<00:01:58.479><c> and</c><00:01:58.719><c> off</c><00:01:59.039><c> and</c><00:01:59.159><c> certainly</c><00:01:59.520><c> online</c><00:02:00.320><c> and</c><00:02:00.640><c> on</c>

00:02:01.149 --> 00:02:01.159 align:start position:0%
2049 and off and certainly online and on
 

00:02:01.159 --> 00:02:03.950 align:start position:0%
2049 and off and certainly online and on
uh<00:02:01.320><c> various</c><00:02:01.680><c> digital</c><00:02:02.159><c> communities</c><00:02:02.799><c> as</c><00:02:02.960><c> well</c>

00:02:03.950 --> 00:02:03.960 align:start position:0%
uh various digital communities as well
 

00:02:03.960 --> 00:02:06.550 align:start position:0%
uh various digital communities as well
we<00:02:04.200><c> also</c><00:02:04.560><c> have</c><00:02:04.920><c> technical</c><00:02:05.759><c> specification</c>

00:02:06.550 --> 00:02:06.560 align:start position:0%
we also have technical specification
 

00:02:06.560 --> 00:02:09.469 align:start position:0%
we also have technical specification
groups<00:02:06.880><c> and</c><00:02:07.119><c> interest</c><00:02:07.520><c> groups</c><00:02:08.039><c> so</c><00:02:08.440><c> a</c><00:02:08.800><c> key</c>

00:02:09.469 --> 00:02:09.479 align:start position:0%
groups and interest groups so a key
 

00:02:09.479 --> 00:02:11.750 align:start position:0%
groups and interest groups so a key
group<00:02:09.800><c> that</c><00:02:09.920><c> we</c><00:02:10.080><c> do</c><00:02:10.399><c> have</c><00:02:10.640><c> is</c><00:02:10.759><c> our</c><00:02:10.920><c> defi</c><00:02:11.440><c> risk</c>

00:02:11.750 --> 00:02:11.760 align:start position:0%
group that we do have is our defi risk
 

00:02:11.760 --> 00:02:13.350 align:start position:0%
group that we do have is our defi risk
assessment<00:02:12.319><c> management</c><00:02:12.760><c> and</c><00:02:12.959><c> accounting</c>

00:02:13.350 --> 00:02:13.360 align:start position:0%
assessment management and accounting
 

00:02:13.360 --> 00:02:15.229 align:start position:0%
assessment management and accounting
group<00:02:13.680><c> that</c><00:02:13.920><c> published</c><00:02:14.319><c> a</c><00:02:14.560><c> set</c><00:02:14.720><c> of</c><00:02:14.920><c> risk</c>

00:02:15.229 --> 00:02:15.239 align:start position:0%
group that published a set of risk
 

00:02:15.239 --> 00:02:17.030 align:start position:0%
group that published a set of risk
guidelines<00:02:15.720><c> for</c><00:02:15.959><c> Enterprise</c><00:02:16.599><c> this</c><00:02:16.720><c> year</c>

00:02:17.030 --> 00:02:17.040 align:start position:0%
guidelines for Enterprise this year
 

00:02:17.040 --> 00:02:19.229 align:start position:0%
guidelines for Enterprise this year
that's<00:02:17.640><c> been</c><00:02:17.840><c> looked</c><00:02:18.120><c> at</c><00:02:18.319><c> not</c><00:02:18.519><c> only</c><00:02:18.879><c> by</c>

00:02:19.229 --> 00:02:19.239 align:start position:0%
that's been looked at not only by
 

00:02:19.239 --> 00:02:21.309 align:start position:0%
that's been looked at not only by
Enterprise<00:02:19.879><c> but</c><00:02:20.040><c> also</c><00:02:20.519><c> governments</c><00:02:21.000><c> around</c>

00:02:21.309 --> 00:02:21.319 align:start position:0%
Enterprise but also governments around
 

00:02:21.319 --> 00:02:23.750 align:start position:0%
Enterprise but also governments around
the<00:02:21.440><c> world</c><00:02:21.879><c> and</c><00:02:22.000><c> we</c><00:02:22.160><c> had</c><00:02:22.400><c> over</c><00:02:22.720><c> 15</c><00:02:23.599><c> uh</c>

00:02:23.750 --> 00:02:23.760 align:start position:0%
the world and we had over 15 uh
 

00:02:23.760 --> 00:02:25.670 align:start position:0%
the world and we had over 15 uh
Enterprise<00:02:24.400><c> companies</c><00:02:24.959><c> collaborating</c><00:02:25.519><c> with</c>

00:02:25.670 --> 00:02:25.680 align:start position:0%
Enterprise companies collaborating with
 

00:02:25.680 --> 00:02:28.110 align:start position:0%
Enterprise companies collaborating with
web<00:02:25.920><c> 3</c><00:02:26.200><c> companies</c><00:02:26.680><c> putting</c><00:02:26.959><c> that</c><00:02:27.280><c> together</c><00:02:28.000><c> we</c>

00:02:28.110 --> 00:02:28.120 align:start position:0%
web 3 companies putting that together we
 

00:02:28.120 --> 00:02:30.070 align:start position:0%
web 3 companies putting that together we
have<00:02:28.239><c> our</c><00:02:28.440><c> cross</c><00:02:28.760><c> chain</c><00:02:29.000><c> interoperability</c>

00:02:30.070 --> 00:02:30.080 align:start position:0%
have our cross chain interoperability
 

00:02:30.080 --> 00:02:32.229 align:start position:0%
have our cross chain interoperability
group<00:02:30.519><c> that</c><00:02:30.720><c> also</c><00:02:31.080><c> issued</c><00:02:31.680><c> uh</c><00:02:31.879><c> their</c>

00:02:32.229 --> 00:02:32.239 align:start position:0%
group that also issued uh their
 

00:02:32.239 --> 00:02:35.509 align:start position:0%
group that also issued uh their
specification<00:02:33.239><c> this</c><00:02:33.440><c> year</c><00:02:33.760><c> and</c><00:02:33.959><c> has</c><00:02:34.239><c> had</c><00:02:35.120><c> uh</c>

00:02:35.509 --> 00:02:35.519 align:start position:0%
specification this year and has had uh
 

00:02:35.519 --> 00:02:37.910 align:start position:0%
specification this year and has had uh
implementation<00:02:36.519><c> as</c><00:02:36.760><c> well</c><00:02:37.120><c> among</c><00:02:37.599><c> different</c>

00:02:37.910 --> 00:02:37.920 align:start position:0%
implementation as well among different
 

00:02:37.920 --> 00:02:39.390 align:start position:0%
implementation as well among different
use<00:02:38.239><c> cases</c><00:02:38.480><c> in</c>

00:02:39.390 --> 00:02:39.400 align:start position:0%
use cases in
 

00:02:39.400 --> 00:02:42.630 align:start position:0%
use cases in
Enterprise<00:02:40.400><c> and</c><00:02:41.120><c> to</c><00:02:41.319><c> get</c><00:02:41.480><c> into</c><00:02:41.920><c> a</c><00:02:42.040><c> little</c><00:02:42.239><c> bit</c>

00:02:42.630 --> 00:02:42.640 align:start position:0%
Enterprise and to get into a little bit
 

00:02:42.640 --> 00:02:45.030 align:start position:0%
Enterprise and to get into a little bit
about<00:02:43.000><c> the</c><00:02:43.239><c> renewed</c><00:02:43.720><c> momentum</c><00:02:44.480><c> that</c><00:02:44.599><c> we</c><00:02:44.760><c> have</c>

00:02:45.030 --> 00:02:45.040 align:start position:0%
about the renewed momentum that we have
 

00:02:45.040 --> 00:02:48.830 align:start position:0%
about the renewed momentum that we have
because<00:02:45.159><c> we</c><00:02:45.280><c> started</c><00:02:45.680><c> in</c><00:02:46.480><c> 2017</c><00:02:47.480><c> but</c><00:02:48.040><c> uh</c><00:02:48.400><c> just</c>

00:02:48.830 --> 00:02:48.840 align:start position:0%
because we started in 2017 but uh just
 

00:02:48.840 --> 00:02:50.910 align:start position:0%
because we started in 2017 but uh just
like<00:02:49.000><c> a</c><00:02:49.120><c> lot</c><00:02:49.280><c> of</c><00:02:49.480><c> blockchain</c><00:02:50.080><c> projects</c><00:02:50.560><c> going</c>

00:02:50.910 --> 00:02:50.920 align:start position:0%
like a lot of blockchain projects going
 

00:02:50.920 --> 00:02:53.670 align:start position:0%
like a lot of blockchain projects going
through<00:02:51.879><c> the</c><00:02:52.239><c> trajectory</c><00:02:52.800><c> of</c><00:02:53.000><c> what's</c><00:02:53.239><c> moved</c>

00:02:53.670 --> 00:02:53.680 align:start position:0%
through the trajectory of what's moved
 

00:02:53.680 --> 00:02:55.990 align:start position:0%
through the trajectory of what's moved
from<00:02:54.480><c> uh</c><00:02:54.680><c> different</c><00:02:55.040><c> Technologies</c><00:02:55.640><c> over</c><00:02:55.879><c> the</c>

00:02:55.990 --> 00:02:56.000 align:start position:0%
from uh different Technologies over the
 

00:02:56.000 --> 00:02:58.149 align:start position:0%
from uh different Technologies over the
year<00:02:56.400><c> we</c><00:02:56.959><c> uh</c><00:02:57.080><c> certainly</c><00:02:57.440><c> had</c><00:02:57.560><c> a</c><00:02:57.720><c> lot</c><00:02:57.840><c> of</c>

00:02:58.149 --> 00:02:58.159 align:start position:0%
year we uh certainly had a lot of
 

00:02:58.159 --> 00:03:01.110 align:start position:0%
year we uh certainly had a lot of
interest<00:02:58.840><c> in</c><00:02:59.239><c> private</c><00:02:59.519><c> block</c><00:02:59.959><c> chains</c><00:03:00.239><c> in</c>

00:03:01.110 --> 00:03:01.120 align:start position:0%
interest in private block chains in
 

00:03:01.120 --> 00:03:04.910 align:start position:0%
interest in private block chains in
2017<00:03:02.120><c> now</c><00:03:02.519><c> it</c><00:03:02.640><c> is</c><00:03:02.840><c> a</c><00:03:03.080><c> 100%</c><00:03:03.959><c> public</c><00:03:04.400><c> ethereum</c>

00:03:04.910 --> 00:03:04.920 align:start position:0%
2017 now it is a 100% public ethereum
 

00:03:04.920 --> 00:03:07.350 align:start position:0%
2017 now it is a 100% public ethereum
based<00:03:05.400><c> that</c><00:03:05.519><c> is</c><00:03:05.840><c> our</c><00:03:06.120><c> recommendation</c><00:03:06.879><c> and</c><00:03:07.040><c> our</c>

00:03:07.350 --> 00:03:07.360 align:start position:0%
based that is our recommendation and our
 

00:03:07.360 --> 00:03:09.390 align:start position:0%
based that is our recommendation and our
strong<00:03:07.560><c> point</c><00:03:07.840><c> of</c><00:03:08.000><c> view</c><00:03:08.200><c> to</c><00:03:08.400><c> the</c><00:03:08.560><c> Enterprise</c>

00:03:09.390 --> 00:03:09.400 align:start position:0%
strong point of view to the Enterprise
 

00:03:09.400 --> 00:03:12.350 align:start position:0%
strong point of view to the Enterprise
ecosystem<00:03:10.239><c> is</c><00:03:10.480><c> to</c><00:03:10.760><c> choose</c><00:03:11.200><c> public</c><00:03:11.519><c> ethereum</c>

00:03:12.350 --> 00:03:12.360 align:start position:0%
ecosystem is to choose public ethereum
 

00:03:12.360 --> 00:03:15.190 align:start position:0%
ecosystem is to choose public ethereum
for<00:03:12.599><c> where</c><00:03:12.799><c> you</c><00:03:12.959><c> want</c><00:03:13.159><c> to</c><00:03:13.599><c> build</c><00:03:14.599><c> um</c><00:03:14.840><c> we</c><00:03:15.000><c> had</c>

00:03:15.190 --> 00:03:15.200 align:start position:0%
for where you want to build um we had
 

00:03:15.200 --> 00:03:17.789 align:start position:0%
for where you want to build um we had
new<00:03:15.360><c> leadership</c><00:03:15.959><c> coming</c><00:03:16.599><c> this</c><00:03:16.760><c> year</c><00:03:17.080><c> myself</c>

00:03:17.789 --> 00:03:17.799 align:start position:0%
new leadership coming this year myself
 

00:03:17.799 --> 00:03:20.030 align:start position:0%
new leadership coming this year myself
PA<00:03:18.159><c> Brody</c><00:03:18.599><c> from</c><00:03:18.760><c> ernston</c><00:03:19.280><c> Young</c><00:03:19.560><c> that</c><00:03:19.720><c> works</c>

00:03:20.030 --> 00:03:20.040 align:start position:0%
PA Brody from ernston Young that works
 

00:03:20.040 --> 00:03:21.670 align:start position:0%
PA Brody from ernston Young that works
very<00:03:20.239><c> intimately</c><00:03:20.879><c> with</c><00:03:21.000><c> the</c><00:03:21.159><c> ethereum</c>

00:03:21.670 --> 00:03:21.680 align:start position:0%
very intimately with the ethereum
 

00:03:21.680 --> 00:03:24.149 align:start position:0%
very intimately with the ethereum
community<00:03:22.360><c> on</c><00:03:22.560><c> the</c><00:03:22.720><c> whole</c><00:03:23.080><c> with</c><00:03:23.519><c> the</c><00:03:24.040><c> uh</c>

00:03:24.149 --> 00:03:24.159 align:start position:0%
community on the whole with the uh
 

00:03:24.159 --> 00:03:26.509 align:start position:0%
community on the whole with the uh
Enterprise<00:03:24.799><c> privacy</c><00:03:25.280><c> solutions</c><00:03:25.840><c> that</c><00:03:26.000><c> ey</c><00:03:26.360><c> is</c>

00:03:26.509 --> 00:03:26.519 align:start position:0%
Enterprise privacy solutions that ey is
 

00:03:26.519 --> 00:03:28.309 align:start position:0%
Enterprise privacy solutions that ey is
building<00:03:27.400><c> and</c><00:03:27.519><c> at</c><00:03:27.640><c> the</c><00:03:27.760><c> beginning</c><00:03:28.080><c> of</c><00:03:28.200><c> the</c>

00:03:28.309 --> 00:03:28.319 align:start position:0%
building and at the beginning of the
 

00:03:28.319 --> 00:03:31.350 align:start position:0%
building and at the beginning of the
year<00:03:28.519><c> we</c><00:03:28.640><c> set</c><00:03:28.920><c> out</c><00:03:29.239><c> to</c><00:03:29.799><c> regain</c><00:03:30.239><c> this</c><00:03:30.439><c> momentum</c>

00:03:31.350 --> 00:03:31.360 align:start position:0%
year we set out to regain this momentum
 

00:03:31.360 --> 00:03:35.710 align:start position:0%
year we set out to regain this momentum
that<00:03:31.519><c> we</c><00:03:31.680><c> had</c><00:03:31.840><c> in</c><00:03:32.239><c> 2017</c><00:03:33.239><c> and</c><00:03:33.920><c> at</c><00:03:34.120><c> the</c><00:03:34.799><c> um</c>

00:03:35.710 --> 00:03:35.720 align:start position:0%
that we had in 2017 and at the um
 

00:03:35.720 --> 00:03:37.910 align:start position:0%
that we had in 2017 and at the um
conclusion<00:03:36.200><c> of</c><00:03:36.360><c> this</c><00:03:36.519><c> year</c><00:03:36.680><c> at</c><00:03:36.840><c> this</c><00:03:37.040><c> event</c><00:03:37.480><c> I</c>

00:03:37.910 --> 00:03:37.920 align:start position:0%
conclusion of this year at this event I
 

00:03:37.920 --> 00:03:39.670 align:start position:0%
conclusion of this year at this event I
think<00:03:38.120><c> we've</c><00:03:38.439><c> largely</c><00:03:38.920><c> achieved</c><00:03:39.400><c> what</c><00:03:39.519><c> we've</c>

00:03:39.670 --> 00:03:39.680 align:start position:0%
think we've largely achieved what we've
 

00:03:39.680 --> 00:03:42.869 align:start position:0%
think we've largely achieved what we've
set<00:03:39.879><c> out</c><00:03:40.040><c> to</c><00:03:40.200><c> do</c><00:03:40.480><c> and</c><00:03:41.040><c> uh</c><00:03:41.200><c> include</c><00:03:42.120><c> uh</c><00:03:42.360><c> lots</c><00:03:42.640><c> of</c>

00:03:42.869 --> 00:03:42.879 align:start position:0%
set out to do and uh include uh lots of
 

00:03:42.879 --> 00:03:45.030 align:start position:0%
set out to do and uh include uh lots of
plans<00:03:43.319><c> on</c><00:03:43.599><c> what</c><00:03:43.760><c> to</c><00:03:43.879><c> do</c><00:03:44.040><c> for</c><00:03:44.239><c> the</c><00:03:44.400><c> next</c><00:03:44.599><c> year</c><00:03:44.879><c> as</c>

00:03:45.030 --> 00:03:45.040 align:start position:0%
plans on what to do for the next year as
 

00:03:45.040 --> 00:03:47.229 align:start position:0%
plans on what to do for the next year as
well<00:03:45.799><c> so</c><00:03:46.200><c> I</c><00:03:46.319><c> mentioned</c><00:03:46.680><c> some</c><00:03:46.799><c> of</c><00:03:46.920><c> the</c><00:03:47.040><c> things</c>

00:03:47.229 --> 00:03:47.239 align:start position:0%
well so I mentioned some of the things
 

00:03:47.239 --> 00:03:49.470 align:start position:0%
well so I mentioned some of the things
our<00:03:47.439><c> groups</c><00:03:47.760><c> have</c><00:03:48.200><c> done</c><00:03:48.640><c> the</c><00:03:48.760><c> events</c><00:03:49.159><c> we've</c>

00:03:49.470 --> 00:03:49.480 align:start position:0%
our groups have done the events we've
 

00:03:49.480 --> 00:03:52.949 align:start position:0%
our groups have done the events we've
participated<00:03:50.159><c> in</c><00:03:51.000><c> and</c><00:03:51.680><c> uh</c><00:03:52.000><c> the</c><00:03:52.360><c> number</c><00:03:52.680><c> one</c>

00:03:52.949 --> 00:03:52.959 align:start position:0%
participated in and uh the number one
 

00:03:52.959 --> 00:03:55.710 align:start position:0%
participated in and uh the number one
mission<00:03:53.959><c> that</c><00:03:54.079><c> we</c><00:03:54.239><c> do</c><00:03:54.480><c> have</c><00:03:54.680><c> is</c><00:03:54.879><c> fostering</c>

00:03:55.710 --> 00:03:55.720 align:start position:0%
mission that we do have is fostering
 

00:03:55.720 --> 00:03:57.670 align:start position:0%
mission that we do have is fostering
this<00:03:55.920><c> community</c><00:03:56.439><c> to</c><00:03:56.640><c> improve</c><00:03:57.159><c> ethereum</c>

00:03:57.670 --> 00:03:57.680 align:start position:0%
this community to improve ethereum
 

00:03:57.680 --> 00:04:01.509 align:start position:0%
this community to improve ethereum
adoption<00:03:58.120><c> and</c><00:03:58.319><c> Industry</c><00:03:59.319><c> so</c><00:04:00.159><c> why</c><00:04:00.480><c> would</c><00:04:01.200><c> uh</c>

00:04:01.509 --> 00:04:01.519 align:start position:0%
adoption and Industry so why would uh
 

00:04:01.519 --> 00:04:03.910 align:start position:0%
adoption and Industry so why would uh
organizations<00:04:02.200><c> want</c><00:04:02.360><c> to</c><00:04:02.480><c> be</c><00:04:02.599><c> a</c><00:04:02.760><c> part</c><00:04:03.040><c> of</c><00:04:03.239><c> EA</c>

00:04:03.910 --> 00:04:03.920 align:start position:0%
organizations want to be a part of EA
 

00:04:03.920 --> 00:04:06.229 align:start position:0%
organizations want to be a part of EA
our<00:04:04.120><c> membership</c><00:04:04.640><c> rate</c><00:04:04.920><c> is</c><00:04:05.079><c> increasing</c><00:04:05.560><c> at</c><00:04:05.680><c> a</c>

00:04:06.229 --> 00:04:06.239 align:start position:0%
our membership rate is increasing at a
 

00:04:06.239 --> 00:04:08.350 align:start position:0%
our membership rate is increasing at a
all-time<00:04:06.799><c> high</c><00:04:07.200><c> at</c><00:04:07.360><c> this</c><00:04:07.519><c> point</c><00:04:07.799><c> we</c><00:04:07.920><c> have</c>

00:04:08.350 --> 00:04:08.360 align:start position:0%
all-time high at this point we have
 

00:04:08.360 --> 00:04:11.670 align:start position:0%
all-time high at this point we have
super<00:04:08.720><c> high</c><00:04:08.959><c> quality</c><00:04:09.360><c> members</c><00:04:10.120><c> um</c><00:04:10.360><c> not</c><00:04:10.680><c> only</c>

00:04:11.670 --> 00:04:11.680 align:start position:0%
super high quality members um not only
 

00:04:11.680 --> 00:04:14.710 align:start position:0%
super high quality members um not only
uh<00:04:11.840><c> the</c><00:04:11.959><c> likes</c><00:04:12.200><c> of</c><00:04:12.400><c> Microsoft</c><00:04:13.079><c> ey</c><00:04:13.599><c> JP</c><00:04:13.959><c> Morgan</c><00:04:14.480><c> s</c>

00:04:14.710 --> 00:04:14.720 align:start position:0%
uh the likes of Microsoft ey JP Morgan s
 

00:04:14.720 --> 00:04:16.870 align:start position:0%
uh the likes of Microsoft ey JP Morgan s
Tander<00:04:15.120><c> on</c><00:04:15.200><c> the</c><00:04:15.319><c> web</c><00:04:15.519><c> two</c><00:04:15.840><c> side</c><00:04:16.040><c> but</c><00:04:16.199><c> we</c><00:04:16.359><c> also</c>

00:04:16.870 --> 00:04:16.880 align:start position:0%
Tander on the web two side but we also
 

00:04:16.880 --> 00:04:21.629 align:start position:0%
Tander on the web two side but we also
have<00:04:17.880><c> uh</c><00:04:18.160><c> Circle</c><00:04:18.799><c> carpat</c><00:04:19.359><c> Key</c><00:04:19.880><c> Gateway</c><00:04:20.880><c> uh</c><00:04:21.000><c> ens</c>

00:04:21.629 --> 00:04:21.639 align:start position:0%
have uh Circle carpat Key Gateway uh ens
 

00:04:21.639 --> 00:04:23.950 align:start position:0%
have uh Circle carpat Key Gateway uh ens
also<00:04:21.880><c> joining</c><00:04:22.400><c> as</c><00:04:22.560><c> well</c><00:04:22.759><c> from</c><00:04:22.919><c> the</c><00:04:23.040><c> web</c><00:04:23.280><c> 3</c><00:04:23.639><c> side</c>

00:04:23.950 --> 00:04:23.960 align:start position:0%
also joining as well from the web 3 side
 

00:04:23.960 --> 00:04:25.950 align:start position:0%
also joining as well from the web 3 side
if<00:04:24.040><c> you're</c><00:04:24.280><c> a</c><00:04:24.440><c> web3</c><00:04:24.960><c> engineering</c><00:04:25.520><c> team</c><00:04:25.840><c> that</c>

00:04:25.950 --> 00:04:25.960 align:start position:0%
if you're a web3 engineering team that
 

00:04:25.960 --> 00:04:28.150 align:start position:0%
if you're a web3 engineering team that
wants<00:04:26.320><c> to</c><00:04:26.639><c> come</c><00:04:26.800><c> to</c><00:04:27.040><c> Enterprise</c><00:04:27.639><c> join</c><00:04:27.880><c> us</c>

00:04:28.150 --> 00:04:28.160 align:start position:0%
wants to come to Enterprise join us
 

00:04:28.160 --> 00:04:29.430 align:start position:0%
wants to come to Enterprise join us
because<00:04:28.280><c> we're</c><00:04:28.440><c> going</c><00:04:28.520><c> to</c><00:04:28.680><c> give</c><00:04:28.800><c> you</c><00:04:29.280><c> the</c>

00:04:29.430 --> 00:04:29.440 align:start position:0%
because we're going to give you the
 

00:04:29.440 --> 00:04:31.670 align:start position:0%
because we're going to give you the
large<00:04:30.000><c> Spotlight</c><00:04:30.479><c> possible</c><00:04:30.800><c> to</c><00:04:31.120><c> connect</c><00:04:31.520><c> you</c>

00:04:31.670 --> 00:04:31.680 align:start position:0%
large Spotlight possible to connect you
 

00:04:31.680 --> 00:04:34.550 align:start position:0%
large Spotlight possible to connect you
with<00:04:31.840><c> the</c><00:04:31.960><c> right</c><00:04:32.440><c> people</c><00:04:33.440><c> um</c><00:04:33.680><c> you'll</c><00:04:33.880><c> see</c><00:04:34.360><c> the</c>

00:04:34.550 --> 00:04:34.560 align:start position:0%
with the right people um you'll see the
 

00:04:34.560 --> 00:04:36.670 align:start position:0%
with the right people um you'll see the
pictures<00:04:35.199><c> on</c><00:04:35.360><c> the</c><00:04:35.560><c> side</c><00:04:35.800><c> from</c><00:04:35.960><c> our</c><00:04:36.240><c> industry</c>

00:04:36.670 --> 00:04:36.680 align:start position:0%
pictures on the side from our industry
 

00:04:36.680 --> 00:04:38.790 align:start position:0%
pictures on the side from our industry
Day<00:04:36.919><c> event</c><00:04:37.280><c> this</c><00:04:37.400><c> year</c><00:04:38.080><c> um</c><00:04:38.440><c> which</c><00:04:38.600><c> we</c>

00:04:38.790 --> 00:04:38.800 align:start position:0%
Day event this year um which we
 

00:04:38.800 --> 00:04:40.950 align:start position:0%
Day event this year um which we
highlighted<00:04:39.440><c> a</c><00:04:39.560><c> lot</c><00:04:39.720><c> of</c><00:04:40.039><c> web</c><00:04:40.320><c> 3</c><00:04:40.600><c> companies</c>

00:04:40.950 --> 00:04:40.960 align:start position:0%
highlighted a lot of web 3 companies
 

00:04:40.960 --> 00:04:44.029 align:start position:0%
highlighted a lot of web 3 companies
doing<00:04:41.280><c> work</c><00:04:41.479><c> with</c><00:04:41.680><c> Enterprise</c><00:04:42.400><c> that</c><00:04:43.320><c> um</c><00:04:43.600><c> is</c>

00:04:44.029 --> 00:04:44.039 align:start position:0%
doing work with Enterprise that um is
 

00:04:44.039 --> 00:04:45.749 align:start position:0%
doing work with Enterprise that um is
very<00:04:44.360><c> significant</c><00:04:44.880><c> and</c><00:04:45.000><c> throughout</c><00:04:45.320><c> a</c><00:04:45.400><c> lot</c><00:04:45.560><c> of</c>

00:04:45.749 --> 00:04:45.759 align:start position:0%
very significant and throughout a lot of
 

00:04:45.759 --> 00:04:47.749 align:start position:0%
very significant and throughout a lot of
different<00:04:46.039><c> brand</c><00:04:46.360><c> names</c><00:04:46.680><c> and</c><00:04:46.840><c> you</c><00:04:46.919><c> can</c><00:04:47.080><c> see</c><00:04:47.440><c> we</c>

00:04:47.749 --> 00:04:47.759 align:start position:0%
different brand names and you can see we
 

00:04:47.759 --> 00:04:50.110 align:start position:0%
different brand names and you can see we
brought<00:04:48.000><c> out</c><00:04:48.240><c> 300</c><00:04:48.800><c> people</c><00:04:49.400><c> plus</c><00:04:49.720><c> to</c><00:04:49.919><c> that</c>

00:04:50.110 --> 00:04:50.120 align:start position:0%
brought out 300 people plus to that
 

00:04:50.120 --> 00:04:53.110 align:start position:0%
brought out 300 people plus to that
event<00:04:50.520><c> with</c><00:04:50.759><c> 75</c><00:04:51.560><c> Plus</c><00:04:51.800><c> speakers</c><00:04:52.639><c> so</c><00:04:52.800><c> it</c><00:04:52.880><c> was</c><00:04:53.000><c> a</c>

00:04:53.110 --> 00:04:53.120 align:start position:0%
event with 75 Plus speakers so it was a
 

00:04:53.120 --> 00:04:55.830 align:start position:0%
event with 75 Plus speakers so it was a
very<00:04:53.280><c> well</c><00:04:53.560><c> attended</c><00:04:54.479><c> um</c><00:04:54.800><c> heavy</c><00:04:55.240><c> content</c>

00:04:55.830 --> 00:04:55.840 align:start position:0%
very well attended um heavy content
 

00:04:55.840 --> 00:04:58.430 align:start position:0%
very well attended um heavy content
event<00:04:56.199><c> that</c><00:04:56.320><c> we</c><00:04:56.479><c> plan</c><00:04:56.840><c> to</c><00:04:57.280><c> do</c><00:04:57.680><c> more</c><00:04:57.960><c> of</c><00:04:58.199><c> in</c><00:04:58.320><c> the</c>

00:04:58.430 --> 00:04:58.440 align:start position:0%
event that we plan to do more of in the
 

00:04:58.440 --> 00:05:01.510 align:start position:0%
event that we plan to do more of in the
coming<00:04:58.800><c> years</c><00:04:59.919><c> and</c><00:05:00.720><c> we</c><00:05:00.880><c> have</c><00:05:01.199><c> strongly</c>

00:05:01.510 --> 00:05:01.520 align:start position:0%
coming years and we have strongly
 

00:05:01.520 --> 00:05:04.110 align:start position:0%
coming years and we have strongly
articulated<00:05:02.240><c> points</c><00:05:02.479><c> of</c><00:05:02.680><c> view</c><00:05:03.080><c> we</c><00:05:03.520><c> are</c><00:05:03.880><c> are</c>

00:05:04.110 --> 00:05:04.120 align:start position:0%
articulated points of view we are are
 

00:05:04.120 --> 00:05:07.390 align:start position:0%
articulated points of view we are are
not<00:05:04.880><c> um</c><00:05:05.240><c> coming</c><00:05:05.520><c> in</c><00:05:05.840><c> with</c><00:05:06.080><c> well</c><00:05:06.280><c> maybe</c><00:05:06.600><c> choose</c>

00:05:07.390 --> 00:05:07.400 align:start position:0%
not um coming in with well maybe choose
 

00:05:07.400 --> 00:05:09.909 align:start position:0%
not um coming in with well maybe choose
this<00:05:07.720><c> ecosystem</c><00:05:08.320><c> maybe</c><00:05:08.560><c> choose</c><00:05:08.919><c> that</c><00:05:09.240><c> we</c><00:05:09.400><c> are</c>

00:05:09.909 --> 00:05:09.919 align:start position:0%
this ecosystem maybe choose that we are
 

00:05:09.919 --> 00:05:12.390 align:start position:0%
this ecosystem maybe choose that we are
ethereum<00:05:10.520><c> based</c><00:05:10.960><c> and</c><00:05:11.120><c> want</c><00:05:11.280><c> to</c><00:05:11.479><c> give</c><00:05:11.919><c> Clarity</c>

00:05:12.390 --> 00:05:12.400 align:start position:0%
ethereum based and want to give Clarity
 

00:05:12.400 --> 00:05:14.749 align:start position:0%
ethereum based and want to give Clarity
to<00:05:12.600><c> the</c><00:05:12.759><c> Enterprise</c><00:05:13.320><c> ecosystem</c><00:05:13.919><c> to</c><00:05:14.360><c> join</c><00:05:14.600><c> us</c>

00:05:14.749 --> 00:05:14.759 align:start position:0%
to the Enterprise ecosystem to join us
 

00:05:14.759 --> 00:05:16.710 align:start position:0%
to the Enterprise ecosystem to join us
in<00:05:14.960><c> doing</c><00:05:15.320><c> that</c><00:05:15.880><c> so</c><00:05:16.039><c> if</c><00:05:16.120><c> you</c><00:05:16.240><c> want</c><00:05:16.320><c> to</c><00:05:16.440><c> learn</c>

00:05:16.710 --> 00:05:16.720 align:start position:0%
in doing that so if you want to learn
 

00:05:16.720 --> 00:05:19.309 align:start position:0%
in doing that so if you want to learn
more<00:05:17.680><c> uh</c><00:05:17.800><c> I</c><00:05:17.919><c> have</c><00:05:18.039><c> some</c><00:05:18.240><c> QR</c><00:05:18.600><c> codes</c><00:05:18.880><c> up</c><00:05:19.080><c> here</c>

00:05:19.309 --> 00:05:19.319 align:start position:0%
more uh I have some QR codes up here
 

00:05:19.319 --> 00:05:22.309 align:start position:0%
more uh I have some QR codes up here
about<00:05:19.840><c> our</c><00:05:20.520><c> uh</c><00:05:20.680><c> membership</c><00:05:21.440><c> and</c><00:05:21.680><c> our</c><00:05:22.080><c> our</c>

00:05:22.309 --> 00:05:22.319 align:start position:0%
about our uh membership and our our
 

00:05:22.319 --> 00:05:26.430 align:start position:0%
about our uh membership and our our
website<00:05:23.319><c> um</c><00:05:24.199><c> and</c><00:05:24.479><c> thank</c><00:05:24.639><c> you</c><00:05:24.720><c> for</c><00:05:24.880><c> the</c><00:05:25.039><c> time</c>

00:05:26.430 --> 00:05:26.440 align:start position:0%
website um and thank you for the time
 

00:05:26.440 --> 00:05:30.670 align:start position:0%
website um and thank you for the time
here<00:05:27.440><c> thank</c><00:05:27.600><c> you</c><00:05:27.759><c> very</c><00:05:27.919><c> much</c><00:05:28.120><c> for</c><00:05:28.280><c> your</c><00:05:29.240><c> speech</c>

00:05:30.670 --> 00:05:30.680 align:start position:0%
here thank you very much for your speech
 

00:05:30.680 --> 00:05:33.390 align:start position:0%
here thank you very much for your speech
uh<00:05:30.840><c> we</c><00:05:31.000><c> have</c><00:05:31.240><c> time</c><00:05:31.440><c> for</c><00:05:31.600><c> a</c><00:05:31.720><c> few</c>

00:05:33.390 --> 00:05:33.400 align:start position:0%
uh we have time for a few
 

00:05:33.400 --> 00:05:35.350 align:start position:0%
uh we have time for a few
questions<00:05:34.400><c> raise</c><00:05:34.600><c> your</c><00:05:34.759><c> hand</c><00:05:34.960><c> if</c><00:05:35.080><c> you</c><00:05:35.199><c> have</c>

00:05:35.350 --> 00:05:35.360 align:start position:0%
questions raise your hand if you have
 

00:05:35.360 --> 00:05:37.590 align:start position:0%
questions raise your hand if you have
any

00:05:37.590 --> 00:05:37.600 align:start position:0%
any
 

00:05:37.600 --> 00:05:40.710 align:start position:0%
any
question<00:05:38.600><c> I</c><00:05:38.720><c> can't</c><00:05:38.960><c> see</c><00:05:39.360><c> with</c><00:05:39.520><c> the</c>

00:05:40.710 --> 00:05:40.720 align:start position:0%
question I can't see with the
 

00:05:40.720 --> 00:05:43.990 align:start position:0%
question I can't see with the
lights<00:05:41.720><c> one</c>

00:05:43.990 --> 00:05:44.000 align:start position:0%
lights one
 

00:05:44.000 --> 00:05:48.790 align:start position:0%
lights one
here<00:05:45.160><c> catch</c><00:05:46.160><c> um</c><00:05:46.479><c> thank</c><00:05:46.639><c> you</c><00:05:46.960><c> hello</c><00:05:47.680><c> um</c><00:05:48.520><c> working</c>

00:05:48.790 --> 00:05:48.800 align:start position:0%
here catch um thank you hello um working
 

00:05:48.800 --> 00:05:52.510 align:start position:0%
here catch um thank you hello um working
for<00:05:49.080><c> Microsoft</c><00:05:50.080><c> um</c><00:05:50.680><c> just</c><00:05:51.240><c> um</c><00:05:51.680><c> a</c><00:05:51.880><c> question</c><00:05:52.319><c> I</c>

00:05:52.510 --> 00:05:52.520 align:start position:0%
for Microsoft um just um a question I
 

00:05:52.520 --> 00:05:54.510 align:start position:0%
for Microsoft um just um a question I
have<00:05:52.960><c> is</c><00:05:53.360><c> um</c><00:05:53.520><c> what</c><00:05:53.639><c> do</c><00:05:53.720><c> you</c><00:05:53.880><c> think</c><00:05:54.120><c> their</c>

00:05:54.510 --> 00:05:54.520 align:start position:0%
have is um what do you think their
 

00:05:54.520 --> 00:05:58.909 align:start position:0%
have is um what do you think their
intentions<00:05:55.080><c> are</c><00:05:55.600><c> with</c><00:05:56.080><c> ethereum</c><00:05:57.080><c> we</c><00:05:57.280><c> see</c><00:05:57.919><c> ey</c>

00:05:58.909 --> 00:05:58.919 align:start position:0%
intentions are with ethereum we see ey
 

00:05:58.919 --> 00:06:01.469 align:start position:0%
intentions are with ethereum we see ey
launching<00:05:59.800><c> products</c><00:06:00.560><c> or</c><00:06:00.759><c> trying</c><00:06:01.000><c> to</c><00:06:01.160><c> build</c>

00:06:01.469 --> 00:06:01.479 align:start position:0%
launching products or trying to build
 

00:06:01.479 --> 00:06:04.350 align:start position:0%
launching products or trying to build
products<00:06:02.000><c> in</c><00:06:02.199><c> that</c><00:06:02.440><c> space</c><00:06:03.120><c> what</c><00:06:03.240><c> is</c><00:06:03.800><c> your</c><00:06:04.080><c> take</c>

00:06:04.350 --> 00:06:04.360 align:start position:0%
products in that space what is your take
 

00:06:04.360 --> 00:06:05.350 align:start position:0%
products in that space what is your take
on

00:06:05.350 --> 00:06:05.360 align:start position:0%
on
 

00:06:05.360 --> 00:06:08.029 align:start position:0%
on
Microsoft<00:06:06.360><c> uh</c><00:06:06.520><c> it's</c><00:06:06.720><c> where</c><00:06:06.840><c> we</c><00:06:06.960><c> want</c><00:06:07.080><c> to</c><00:06:07.240><c> build</c>

00:06:08.029 --> 00:06:08.039 align:start position:0%
Microsoft uh it's where we want to build
 

00:06:08.039 --> 00:06:09.710 align:start position:0%
Microsoft uh it's where we want to build
I'll<00:06:08.319><c> I'll</c><00:06:08.520><c> I'll</c><00:06:08.680><c> put</c><00:06:08.800><c> it</c><00:06:09.000><c> that</c><00:06:09.120><c> way</c><00:06:09.280><c> it's</c><00:06:09.440><c> the</c>

00:06:09.710 --> 00:06:09.720 align:start position:0%
I'll I'll I'll put it that way it's the
 

00:06:09.720 --> 00:06:12.070 align:start position:0%
I'll I'll I'll put it that way it's the
strongest<00:06:10.120><c> ecosystem</c><00:06:10.800><c> to</c><00:06:11.000><c> align</c><00:06:11.400><c> with</c><00:06:11.880><c> for</c>

00:06:12.070 --> 00:06:12.080 align:start position:0%
strongest ecosystem to align with for
 

00:06:12.080 --> 00:06:14.710 align:start position:0%
strongest ecosystem to align with for
the<00:06:12.199><c> future</c><00:06:12.520><c> of</c><00:06:12.680><c> the</c><00:06:13.120><c> technology</c><00:06:14.120><c> um</c><00:06:14.360><c> also</c>

00:06:14.710 --> 00:06:14.720 align:start position:0%
the future of the technology um also
 

00:06:14.720 --> 00:06:17.309 align:start position:0%
the future of the technology um also
surrounded<00:06:15.440><c> by</c><00:06:15.680><c> the</c><00:06:15.840><c> largest</c><00:06:16.400><c> ecosystem</c><00:06:17.160><c> as</c>

00:06:17.309 --> 00:06:17.319 align:start position:0%
surrounded by the largest ecosystem as
 

00:06:17.319 --> 00:06:21.469 align:start position:0%
surrounded by the largest ecosystem as
well<00:06:18.319><c> um</c><00:06:18.560><c> so</c><00:06:19.440><c> a</c><00:06:19.880><c> agnostic</c><00:06:20.479><c> of</c><00:06:20.639><c> any</c><00:06:20.919><c> technology</c>

00:06:21.469 --> 00:06:21.479 align:start position:0%
well um so a agnostic of any technology
 

00:06:21.479 --> 00:06:23.950 align:start position:0%
well um so a agnostic of any technology
we<00:06:21.560><c> want</c><00:06:21.680><c> to</c><00:06:21.840><c> be</c><00:06:22.000><c> aligned</c><00:06:22.680><c> in</c><00:06:23.440><c> that</c><00:06:23.720><c> which</c><00:06:23.840><c> is</c>

00:06:23.950 --> 00:06:23.960 align:start position:0%
we want to be aligned in that which is
 

00:06:23.960 --> 00:06:25.909 align:start position:0%
we want to be aligned in that which is
being<00:06:24.240><c> the</c><00:06:24.360><c> most</c><00:06:24.639><c> successful</c><00:06:25.400><c> that</c><00:06:25.599><c> which</c><00:06:25.720><c> is</c>

00:06:25.909 --> 00:06:25.919 align:start position:0%
being the most successful that which is
 

00:06:25.919 --> 00:06:28.390 align:start position:0%
being the most successful that which is
solving<00:06:26.479><c> customer</c><00:06:27.039><c> problems</c><00:06:27.400><c> and</c><00:06:27.560><c> aligned</c>

00:06:28.390 --> 00:06:28.400 align:start position:0%
solving customer problems and aligned
 

00:06:28.400 --> 00:06:32.150 align:start position:0%
solving customer problems and aligned
with<00:06:28.560><c> where</c><00:06:28.720><c> the</c><00:06:28.840><c> future</c><00:06:29.199><c> is</c><00:06:29.680><c> so</c><00:06:30.680><c> um</c><00:06:31.160><c> it</c><00:06:31.400><c> and</c>

00:06:32.150 --> 00:06:32.160 align:start position:0%
with where the future is so um it and
 

00:06:32.160 --> 00:06:33.870 align:start position:0%
with where the future is so um it and
more<00:06:32.680><c> prolifically</c><00:06:33.319><c> if</c><00:06:33.400><c> you</c><00:06:33.520><c> look</c><00:06:33.680><c> at</c>

00:06:33.870 --> 00:06:33.880 align:start position:0%
more prolifically if you look at
 

00:06:33.880 --> 00:06:36.670 align:start position:0%
more prolifically if you look at
Enterprise<00:06:34.840><c> Cloud</c><00:06:35.199><c> environments</c><00:06:35.840><c> ethereum</c>

00:06:36.670 --> 00:06:36.680 align:start position:0%
Enterprise Cloud environments ethereum
 

00:06:36.680 --> 00:06:39.469 align:start position:0%
Enterprise Cloud environments ethereum
has<00:06:36.880><c> always</c><00:06:37.160><c> been</c><00:06:37.400><c> the</c><00:06:37.800><c> the</c><00:06:37.960><c> basis</c><00:06:38.720><c> of</c><00:06:39.240><c> which</c>

00:06:39.469 --> 00:06:39.479 align:start position:0%
has always been the the basis of which
 

00:06:39.479 --> 00:06:41.550 align:start position:0%
has always been the the basis of which
to<00:06:39.680><c> build</c><00:06:40.280><c> there</c><00:06:40.880><c> and</c><00:06:41.039><c> that's</c><00:06:41.280><c> really</c>

00:06:41.550 --> 00:06:41.560 align:start position:0%
to build there and that's really
 

00:06:41.560 --> 00:06:44.390 align:start position:0%
to build there and that's really
significant<00:06:42.319><c> there</c><00:06:42.639><c> there's</c><00:06:42.880><c> not</c><00:06:43.280><c> other</c><00:06:43.599><c> l1s</c>

00:06:44.390 --> 00:06:44.400 align:start position:0%
significant there there's not other l1s
 

00:06:44.400 --> 00:06:46.589 align:start position:0%
significant there there's not other l1s
that<00:06:44.639><c> have</c><00:06:44.919><c> the</c><00:06:45.199><c> oneclick</c><00:06:45.800><c> deployment</c><00:06:46.360><c> for</c>

00:06:46.589 --> 00:06:46.599 align:start position:0%
that have the oneclick deployment for
 

00:06:46.599 --> 00:06:49.830 align:start position:0%
that have the oneclick deployment for
Enterprise<00:06:47.479><c> developers</c><00:06:48.479><c> uh</c><00:06:48.599><c> to</c><00:06:48.759><c> build</c><00:06:49.039><c> on</c><00:06:49.319><c> and</c>

00:06:49.830 --> 00:06:49.840 align:start position:0%
Enterprise developers uh to build on and
 

00:06:49.840 --> 00:06:52.710 align:start position:0%
Enterprise developers uh to build on and
um<00:06:50.479><c> thankfully</c><00:06:51.160><c> ethereum</c><00:06:51.680><c> has</c><00:06:51.919><c> that</c><00:06:52.400><c> uh</c><00:06:52.599><c> we</c>

00:06:52.710 --> 00:06:52.720 align:start position:0%
um thankfully ethereum has that uh we
 

00:06:52.720 --> 00:06:55.589 align:start position:0%
um thankfully ethereum has that uh we
should<00:06:52.919><c> have</c><00:06:53.080><c> a</c><00:06:53.199><c> lot</c><00:06:53.360><c> more</c><00:06:54.240><c> um</c><00:06:54.560><c> the</c><00:06:54.720><c> more</c><00:06:55.080><c> that</c>

00:06:55.589 --> 00:06:55.599 align:start position:0%
should have a lot more um the more that
 

00:06:55.599 --> 00:06:57.110 align:start position:0%
should have a lot more um the more that
you<00:06:55.759><c> can</c><00:06:55.919><c> meet</c><00:06:56.160><c> Enterprises</c><00:06:56.800><c> where</c><00:06:57.000><c> they</c>

00:06:57.110 --> 00:06:57.120 align:start position:0%
you can meet Enterprises where they
 

00:06:57.120 --> 00:07:01.230 align:start position:0%
you can meet Enterprises where they
build<00:06:57.680><c> the</c><00:06:58.160><c> the</c><00:06:58.319><c> better</c>

00:07:01.230 --> 00:07:01.240 align:start position:0%
build the the better
 

00:07:01.240 --> 00:07:02.950 align:start position:0%
build the the better
thank<00:07:01.440><c> you</c><00:07:02.000><c> uh</c><00:07:02.120><c> we</c><00:07:02.240><c> have</c><00:07:02.400><c> another</c><00:07:02.680><c> question</c>

00:07:02.950 --> 00:07:02.960 align:start position:0%
thank you uh we have another question
 

00:07:02.960 --> 00:07:05.270 align:start position:0%
thank you uh we have another question
over<00:07:03.240><c> there</c><00:07:04.000><c> yeah</c><00:07:04.759><c> I</c><00:07:04.840><c> guess</c><00:07:04.960><c> it's</c><00:07:05.120><c> an</c>

00:07:05.270 --> 00:07:05.280 align:start position:0%
over there yeah I guess it's an
 

00:07:05.280 --> 00:07:07.550 align:start position:0%
over there yeah I guess it's an
extension<00:07:05.680><c> of</c><00:07:05.919><c> the</c><00:07:06.160><c> previous</c><00:07:06.560><c> question</c><00:07:07.319><c> um</c>

00:07:07.550 --> 00:07:07.560 align:start position:0%
extension of the previous question um
 

00:07:07.560 --> 00:07:09.110 align:start position:0%
extension of the previous question um
with<00:07:07.840><c> people</c><00:07:08.080><c> like</c><00:07:08.240><c> Microsoft</c><00:07:08.639><c> and</c><00:07:08.759><c> ey</c>

00:07:09.110 --> 00:07:09.120 align:start position:0%
with people like Microsoft and ey
 

00:07:09.120 --> 00:07:11.869 align:start position:0%
with people like Microsoft and ey
building<00:07:09.440><c> components</c><00:07:09.879><c> in</c><00:07:10.039><c> the</c><00:07:10.240><c> space</c><00:07:11.199><c> um</c><00:07:11.720><c> like</c>

00:07:11.869 --> 00:07:11.879 align:start position:0%
building components in the space um like
 

00:07:11.879 --> 00:07:13.909 align:start position:0%
building components in the space um like
Aztec<00:07:12.240><c> is</c><00:07:12.360><c> a</c><00:07:12.639><c> privacy</c><00:07:12.960><c> preserving</c><00:07:13.319><c> layer</c><00:07:13.599><c> too</c>

00:07:13.909 --> 00:07:13.919 align:start position:0%
Aztec is a privacy preserving layer too
 

00:07:13.919 --> 00:07:16.309 align:start position:0%
Aztec is a privacy preserving layer too
and<00:07:14.120><c> I</c><00:07:14.199><c> know</c><00:07:14.400><c> ey</c><00:07:14.720><c> is</c><00:07:14.960><c> doing</c><00:07:15.240><c> privacy</c><00:07:15.639><c> things</c><00:07:15.800><c> on</c>

00:07:16.309 --> 00:07:16.319 align:start position:0%
and I know ey is doing privacy things on
 

00:07:16.319 --> 00:07:19.070 align:start position:0%
and I know ey is doing privacy things on
Main<00:07:16.759><c> ethereum</c><00:07:17.680><c> um</c><00:07:18.400><c> are</c><00:07:18.560><c> they</c><00:07:18.680><c> sort</c><00:07:18.840><c> of</c><00:07:18.919><c> on</c>

00:07:19.070 --> 00:07:19.080 align:start position:0%
Main ethereum um are they sort of on
 

00:07:19.080 --> 00:07:20.790 align:start position:0%
Main ethereum um are they sort of on
equal<00:07:19.319><c> footing</c><00:07:19.639><c> or</c><00:07:19.800><c> is</c><00:07:19.919><c> there</c><00:07:20.080><c> some</c><00:07:20.319><c> advantage</c>

00:07:20.790 --> 00:07:20.800 align:start position:0%
equal footing or is there some advantage
 

00:07:20.800 --> 00:07:23.029 align:start position:0%
equal footing or is there some advantage
to<00:07:20.960><c> say</c><00:07:21.240><c> ey</c><00:07:22.120><c> being</c><00:07:22.319><c> able</c><00:07:22.479><c> to</c><00:07:22.599><c> incorporate</c>

00:07:23.029 --> 00:07:23.039 align:start position:0%
to say ey being able to incorporate
 

00:07:23.039 --> 00:07:24.430 align:start position:0%
to say ey being able to incorporate
things<00:07:23.160><c> a</c><00:07:23.280><c> little</c><00:07:23.440><c> closer</c><00:07:23.759><c> or</c><00:07:23.919><c> recommend</c>

00:07:24.430 --> 00:07:24.440 align:start position:0%
things a little closer or recommend
 

00:07:24.440 --> 00:07:27.670 align:start position:0%
things a little closer or recommend
things<00:07:24.680><c> for</c><00:07:25.360><c> Enterprise</c><00:07:26.360><c> and</c><00:07:27.240><c> I</c><00:07:27.319><c> guess</c><00:07:27.479><c> a</c>

00:07:27.670 --> 00:07:27.680 align:start position:0%
things for Enterprise and I guess a
 

00:07:27.680 --> 00:07:30.150 align:start position:0%
things for Enterprise and I guess a
similar<00:07:28.039><c> follow-up</c><00:07:28.479><c> question</c><00:07:29.160><c> is</c><00:07:29.919><c> uh</c><00:07:30.039><c> when</c>

00:07:30.150 --> 00:07:30.160 align:start position:0%
similar follow-up question is uh when
 

00:07:30.160 --> 00:07:31.710 align:start position:0%
similar follow-up question is uh when
you<00:07:30.280><c> say</c><00:07:30.479><c> ethereum</c><00:07:30.879><c> are</c><00:07:30.960><c> you</c><00:07:31.120><c> talking</c><00:07:31.440><c> like</c>

00:07:31.710 --> 00:07:31.720 align:start position:0%
you say ethereum are you talking like
 

00:07:31.720 --> 00:07:33.189 align:start position:0%
you say ethereum are you talking like
just<00:07:31.960><c> mainnet</c><00:07:32.360><c> ethereum</c><00:07:32.759><c> or</c><00:07:32.879><c> you</c><00:07:32.960><c> talking</c>

00:07:33.189 --> 00:07:33.199 align:start position:0%
just mainnet ethereum or you talking
 

00:07:33.199 --> 00:07:36.230 align:start position:0%
just mainnet ethereum or you talking
ethereum<00:07:33.599><c> including</c><00:07:33.919><c> ler</c><00:07:34.240><c> to</c><00:07:34.560><c> yeah</c><00:07:35.440><c> um</c><00:07:35.879><c> so</c>

00:07:36.230 --> 00:07:36.240 align:start position:0%
ethereum including ler to yeah um so
 

00:07:36.240 --> 00:07:37.990 align:start position:0%
ethereum including ler to yeah um so
first<00:07:36.680><c> tackle</c><00:07:37.000><c> the</c><00:07:37.120><c> second</c><00:07:37.400><c> question</c><00:07:37.759><c> here</c>

00:07:37.990 --> 00:07:38.000 align:start position:0%
first tackle the second question here
 

00:07:38.000 --> 00:07:40.990 align:start position:0%
first tackle the second question here
the<00:07:38.319><c> ethereum</c><00:07:38.759><c> layer</c><00:07:39.039><c> 2</c><00:07:39.400><c> ecosystem</c><00:07:40.240><c> so</c><00:07:40.840><c> we're</c>

00:07:40.990 --> 00:07:41.000 align:start position:0%
the ethereum layer 2 ecosystem so we're
 

00:07:41.000 --> 00:07:43.749 align:start position:0%
the ethereum layer 2 ecosystem so we're
not<00:07:41.680><c> uh</c><00:07:42.280><c> directing</c><00:07:42.759><c> people</c><00:07:42.960><c> to</c><00:07:43.120><c> main</c><00:07:43.400><c> net</c>

00:07:43.749 --> 00:07:43.759 align:start position:0%
not uh directing people to main net
 

00:07:43.759 --> 00:07:46.230 align:start position:0%
not uh directing people to main net
activities<00:07:44.360><c> but</c><00:07:44.520><c> building</c><00:07:44.919><c> in</c><00:07:45.199><c> in</c><00:07:45.319><c> that</c><00:07:45.680><c> which</c>

00:07:46.230 --> 00:07:46.240 align:start position:0%
activities but building in in that which
 

00:07:46.240 --> 00:07:49.029 align:start position:0%
activities but building in in that which
um<00:07:47.240><c> uh</c><00:07:47.639><c> has</c><00:07:47.960><c> ethereum</c><00:07:48.400><c> as</c><00:07:48.520><c> the</c><00:07:48.639><c> settlement</c>

00:07:49.029 --> 00:07:49.039 align:start position:0%
um uh has ethereum as the settlement
 

00:07:49.039 --> 00:07:51.749 align:start position:0%
um uh has ethereum as the settlement
layer<00:07:49.360><c> of</c><00:07:49.720><c> the</c><00:07:50.159><c> internet</c><00:07:51.159><c> uh</c><00:07:51.360><c> and</c><00:07:51.479><c> then</c><00:07:51.599><c> in</c>

00:07:51.749 --> 00:07:51.759 align:start position:0%
layer of the internet uh and then in
 

00:07:51.759 --> 00:07:54.070 align:start position:0%
layer of the internet uh and then in
terms<00:07:52.000><c> of</c><00:07:52.159><c> your</c><00:07:52.360><c> other</c><00:07:52.680><c> question</c><00:07:53.280><c> on</c><00:07:53.800><c> you</c><00:07:53.919><c> know</c>

00:07:54.070 --> 00:07:54.080 align:start position:0%
terms of your other question on you know
 

00:07:54.080 --> 00:07:56.710 align:start position:0%
terms of your other question on you know
how<00:07:54.159><c> do</c><00:07:54.319><c> we</c><00:07:54.520><c> evaluate</c><00:07:55.520><c> uh</c><00:07:55.720><c> which</c><00:07:56.120><c> companies</c><00:07:56.520><c> to</c>

00:07:56.710 --> 00:07:56.720 align:start position:0%
how do we evaluate uh which companies to
 

00:07:56.720 --> 00:08:00.670 align:start position:0%
how do we evaluate uh which companies to
go<00:07:56.919><c> with</c><00:07:57.280><c> a</c><00:07:57.400><c> good</c><00:07:57.680><c> qu</c><00:07:58.240><c> uh</c><00:07:58.720><c> thought</c><00:07:59.240><c> there</c><00:07:59.840><c> is</c><00:08:00.199><c> we</c>

00:08:00.670 --> 00:08:00.680 align:start position:0%
go with a good qu uh thought there is we
 

00:08:00.680 --> 00:08:02.869 align:start position:0%
go with a good qu uh thought there is we
we<00:08:00.800><c> want</c><00:08:00.919><c> to</c><00:08:01.199><c> align</c><00:08:01.560><c> with</c><00:08:01.800><c> projects</c><00:08:02.199><c> that</c><00:08:02.360><c> have</c>

00:08:02.869 --> 00:08:02.879 align:start position:0%
we want to align with projects that have
 

00:08:02.879 --> 00:08:05.430 align:start position:0%
we want to align with projects that have
sustainability<00:08:03.879><c> support</c><00:08:04.479><c> and</c><00:08:04.720><c> a</c><00:08:04.919><c> a</c><00:08:05.080><c> clear</c>

00:08:05.430 --> 00:08:05.440 align:start position:0%
sustainability support and a a clear
 

00:08:05.440 --> 00:08:09.270 align:start position:0%
sustainability support and a a clear
future<00:08:06.080><c> road</c><00:08:06.440><c> map</c><00:08:06.879><c> so</c><00:08:07.879><c> um</c><00:08:08.400><c> that</c><00:08:08.879><c> is</c><00:08:09.039><c> something</c>

00:08:09.270 --> 00:08:09.280 align:start position:0%
future road map so um that is something
 

00:08:09.280 --> 00:08:10.869 align:start position:0%
future road map so um that is something
to<00:08:09.479><c> think</c><00:08:09.639><c> about</c><00:08:09.840><c> for</c><00:08:10.000><c> Enterprise</c><00:08:10.639><c> because</c>

00:08:10.869 --> 00:08:10.879 align:start position:0%
to think about for Enterprise because
 

00:08:10.879 --> 00:08:12.670 align:start position:0%
to think about for Enterprise because
once<00:08:11.120><c> something</c><00:08:11.400><c> gets</c><00:08:11.599><c> in</c><00:08:11.840><c> production</c><00:08:12.479><c> which</c>

00:08:12.670 --> 00:08:12.680 align:start position:0%
once something gets in production which
 

00:08:12.680 --> 00:08:15.469 align:start position:0%
once something gets in production which
not<00:08:13.000><c> a</c><00:08:13.120><c> whole</c><00:08:13.319><c> lot</c><00:08:13.520><c> of</c><00:08:14.199><c> um</c><00:08:14.440><c> Enterprise</c><00:08:15.199><c> proof</c>

00:08:15.469 --> 00:08:15.479 align:start position:0%
not a whole lot of um Enterprise proof
 

00:08:15.479 --> 00:08:18.510 align:start position:0%
not a whole lot of um Enterprise proof
of<00:08:15.680><c> conet</c><00:08:16.280><c> get</c><00:08:16.440><c> to</c><00:08:16.680><c> at</c><00:08:16.919><c> this</c><00:08:17.120><c> point</c><00:08:17.840><c> there's</c><00:08:18.360><c> a</c>

00:08:18.510 --> 00:08:18.520 align:start position:0%
of conet get to at this point there's a
 

00:08:18.520 --> 00:08:20.510 align:start position:0%
of conet get to at this point there's a
a<00:08:18.639><c> release</c><00:08:19.120><c> team</c><00:08:19.479><c> a</c><00:08:19.599><c> maintenance</c><00:08:20.120><c> team</c>

00:08:20.510 --> 00:08:20.520 align:start position:0%
a release team a maintenance team
 

00:08:20.520 --> 00:08:22.430 align:start position:0%
a release team a maintenance team
there's<00:08:20.680><c> a</c><00:08:20.960><c> security</c><00:08:21.440><c> team</c><00:08:21.800><c> that</c><00:08:21.960><c> all</c><00:08:22.159><c> have</c><00:08:22.319><c> to</c>

00:08:22.430 --> 00:08:22.440 align:start position:0%
there's a security team that all have to
 

00:08:22.440 --> 00:08:24.110 align:start position:0%
there's a security team that all have to
be<00:08:22.560><c> in</c><00:08:22.759><c> place</c><00:08:23.000><c> to</c><00:08:23.159><c> make</c><00:08:23.319><c> sure</c><00:08:23.680><c> that</c><00:08:23.840><c> that</c>

00:08:24.110 --> 00:08:24.120 align:start position:0%
be in place to make sure that that
 

00:08:24.120 --> 00:08:26.869 align:start position:0%
be in place to make sure that that
product<00:08:24.560><c> continues</c><00:08:25.039><c> going</c><00:08:25.280><c> for</c><00:08:25.879><c> Enterprise</c>

00:08:26.869 --> 00:08:26.879 align:start position:0%
product continues going for Enterprise
 

00:08:26.879 --> 00:08:28.869 align:start position:0%
product continues going for Enterprise
um<00:08:27.080><c> and</c><00:08:27.199><c> that's</c><00:08:27.400><c> really</c><00:08:27.680><c> significant</c><00:08:28.360><c> so</c><00:08:28.759><c> the</c>

00:08:28.869 --> 00:08:28.879 align:start position:0%
um and that's really significant so the
 

00:08:28.879 --> 00:08:30.029 align:start position:0%
um and that's really significant so the
more<00:08:29.240><c> that</c>

00:08:30.029 --> 00:08:30.039 align:start position:0%
more that
 

00:08:30.039 --> 00:08:33.269 align:start position:0%
more that
um<00:08:30.800><c> ethereum</c><00:08:31.360><c> based</c><00:08:31.919><c> web</c><00:08:32.159><c> 3</c><00:08:32.519><c> ecosystem</c>

00:08:33.269 --> 00:08:33.279 align:start position:0%
um ethereum based web 3 ecosystem
 

00:08:33.279 --> 00:08:35.389 align:start position:0%
um ethereum based web 3 ecosystem
projects<00:08:33.760><c> can</c><00:08:34.000><c> support</c><00:08:34.440><c> that</c><00:08:34.680><c> the</c><00:08:34.839><c> better</c>

00:08:35.389 --> 00:08:35.399 align:start position:0%
projects can support that the better
 

00:08:35.399 --> 00:08:38.790 align:start position:0%
projects can support that the better
because<00:08:35.640><c> a</c><00:08:35.760><c> lot</c><00:08:35.880><c> of</c><00:08:36.080><c> times</c><00:08:37.039><c> um</c><00:08:38.000><c> I</c><00:08:38.080><c> would</c><00:08:38.320><c> say</c>

00:08:38.790 --> 00:08:38.800 align:start position:0%
because a lot of times um I would say
 

00:08:38.800 --> 00:08:41.430 align:start position:0%
because a lot of times um I would say
you<00:08:38.919><c> know</c><00:08:39.599><c> Tech</c><00:08:39.919><c> is</c><00:08:40.360><c> is</c><00:08:40.560><c> very</c><00:08:40.839><c> important</c><00:08:41.320><c> The</c>

00:08:41.430 --> 00:08:41.440 align:start position:0%
you know Tech is is very important The
 

00:08:41.440 --> 00:08:44.029 align:start position:0%
you know Tech is is very important The
Innovation<00:08:42.039><c> behind</c><00:08:42.320><c> it</c><00:08:42.640><c> Etc</c><00:08:43.399><c> but</c><00:08:43.599><c> at</c><00:08:43.800><c> the</c><00:08:43.880><c> end</c>

00:08:44.029 --> 00:08:44.039 align:start position:0%
Innovation behind it Etc but at the end
 

00:08:44.039 --> 00:08:45.550 align:start position:0%
Innovation behind it Etc but at the end
of<00:08:44.120><c> the</c><00:08:44.240><c> day</c><00:08:44.399><c> if</c><00:08:44.519><c> you</c><00:08:44.680><c> can't</c><00:08:44.959><c> support</c><00:08:45.399><c> the</c>

00:08:45.550 --> 00:08:45.560 align:start position:0%
of the day if you can't support the
 

00:08:45.560 --> 00:08:47.670 align:start position:0%
of the day if you can't support the
longevity<00:08:46.120><c> of</c><00:08:46.240><c> a</c><00:08:46.399><c> product</c><00:08:46.720><c> in</c><00:08:46.880><c> an</c><00:08:47.040><c> Enterprise</c>

00:08:47.670 --> 00:08:47.680 align:start position:0%
longevity of a product in an Enterprise
 

00:08:47.680 --> 00:08:49.470 align:start position:0%
longevity of a product in an Enterprise
environment<00:08:48.680><c> um</c><00:08:48.880><c> that's</c><00:08:49.040><c> going</c><00:08:49.120><c> to</c><00:08:49.240><c> be</c><00:08:49.360><c> an</c>

00:08:49.470 --> 00:08:49.480 align:start position:0%
environment um that's going to be an
 

00:08:49.480 --> 00:08:52.870 align:start position:0%
environment um that's going to be an
Achilles<00:08:49.920><c> heel</c>

00:08:52.870 --> 00:08:52.880 align:start position:0%
 
 

00:08:52.880 --> 00:08:55.790 align:start position:0%
 
so<00:08:53.880><c> thank</c><00:08:54.040><c> you</c><00:08:54.880><c> so</c><00:08:55.080><c> we</c><00:08:55.200><c> have</c><00:08:55.399><c> one</c><00:08:55.600><c> last</c>

00:08:55.790 --> 00:08:55.800 align:start position:0%
so thank you so we have one last
 

00:08:55.800 --> 00:09:02.230 align:start position:0%
so thank you so we have one last
question<00:08:56.040><c> over</c><00:08:56.320><c> here</c>

00:09:02.230 --> 00:09:02.240 align:start position:0%
 
 

00:09:02.240 --> 00:09:05.670 align:start position:0%
 
sorry<00:09:02.760><c> um</c><00:09:03.360><c> yeah</c><00:09:03.920><c> uh</c><00:09:04.079><c> I</c><00:09:04.200><c> have</c><00:09:04.360><c> a</c><00:09:04.680><c> controversial</c>

00:09:05.670 --> 00:09:05.680 align:start position:0%
sorry um yeah uh I have a controversial
 

00:09:05.680 --> 00:09:08.350 align:start position:0%
sorry um yeah uh I have a controversial
question<00:09:06.160><c> here</c><00:09:06.760><c> um</c><00:09:07.040><c> so</c><00:09:07.399><c> what</c><00:09:07.600><c> Microsoft</c><00:09:08.120><c> did</c>

00:09:08.350 --> 00:09:08.360 align:start position:0%
question here um so what Microsoft did
 

00:09:08.360 --> 00:09:11.389 align:start position:0%
question here um so what Microsoft did
with<00:09:08.519><c> open</c><00:09:08.839><c> AI</c><00:09:09.800><c> um</c><00:09:10.000><c> taking</c><00:09:10.399><c> open</c><00:09:10.680><c> source</c>

00:09:11.389 --> 00:09:11.399 align:start position:0%
with open AI um taking open source
 

00:09:11.399 --> 00:09:13.949 align:start position:0%
with open AI um taking open source
putting<00:09:11.720><c> into</c><00:09:12.120><c> closed</c><00:09:12.480><c> Source</c><00:09:13.480><c> um</c><00:09:13.720><c> do</c><00:09:13.839><c> you</c>

00:09:13.949 --> 00:09:13.959 align:start position:0%
putting into closed Source um do you
 

00:09:13.959 --> 00:09:16.310 align:start position:0%
putting into closed Source um do you
think<00:09:14.160><c> it</c><00:09:14.279><c> will</c><00:09:14.519><c> align</c><00:09:14.880><c> with</c><00:09:15.120><c> the</c><00:09:15.720><c> open</c><00:09:16.040><c> source</c>

00:09:16.310 --> 00:09:16.320 align:start position:0%
think it will align with the open source
 

00:09:16.320 --> 00:09:20.550 align:start position:0%
think it will align with the open source
ethos<00:09:17.079><c> what</c><00:09:17.320><c> ethereum</c><00:09:17.800><c> is</c><00:09:17.959><c> built</c><00:09:18.279><c> upon</c><00:09:19.279><c> and</c><00:09:20.279><c> do</c>

00:09:20.550 --> 00:09:20.560 align:start position:0%
ethos what ethereum is built upon and do
 

00:09:20.560 --> 00:09:22.069 align:start position:0%
ethos what ethereum is built upon and do
think<00:09:20.800><c> like</c><00:09:21.000><c> they</c><00:09:21.120><c> will</c><00:09:21.279><c> start</c><00:09:21.600><c> acquiring</c>

00:09:22.069 --> 00:09:22.079 align:start position:0%
think like they will start acquiring
 

00:09:22.079 --> 00:09:24.509 align:start position:0%
think like they will start acquiring
startups<00:09:22.839><c> building</c><00:09:23.200><c> Cool</c><00:09:23.560><c> Tech</c><00:09:24.040><c> and</c><00:09:24.200><c> making</c>

00:09:24.509 --> 00:09:24.519 align:start position:0%
startups building Cool Tech and making
 

00:09:24.519 --> 00:09:28.230 align:start position:0%
startups building Cool Tech and making
them<00:09:25.240><c> U</c><00:09:25.440><c> close</c><00:09:26.160><c> Source</c><00:09:27.160><c> well</c><00:09:27.480><c> the</c><00:09:27.640><c> way</c>

00:09:28.230 --> 00:09:28.240 align:start position:0%
them U close Source well the way
 

00:09:28.240 --> 00:09:30.710 align:start position:0%
them U close Source well the way
ethereum<00:09:28.760><c> in</c><00:09:29.079><c> this</c><00:09:29.399><c> Community</c><00:09:29.760><c> is</c><00:09:29.959><c> structured</c>

00:09:30.710 --> 00:09:30.720 align:start position:0%
ethereum in this Community is structured
 

00:09:30.720 --> 00:09:33.030 align:start position:0%
ethereum in this Community is structured
I<00:09:30.839><c> don't</c><00:09:31.079><c> think</c><00:09:31.399><c> we</c><00:09:31.920><c> could</c><00:09:32.120><c> be</c><00:09:32.399><c> successful</c>

00:09:33.030 --> 00:09:33.040 align:start position:0%
I don't think we could be successful
 

00:09:33.040 --> 00:09:36.750 align:start position:0%
I don't think we could be successful
even<00:09:33.240><c> if</c><00:09:33.399><c> we</c><00:09:33.560><c> wanted</c><00:09:34.040><c> to</c><00:09:34.920><c> um</c><00:09:35.880><c> to</c><00:09:36.200><c> to</c><00:09:36.360><c> choose</c><00:09:36.600><c> an</c>

00:09:36.750 --> 00:09:36.760 align:start position:0%
even if we wanted to um to to choose an
 

00:09:36.760 --> 00:09:38.870 align:start position:0%
even if we wanted to um to to choose an
alternative<00:09:37.399><c> Direction</c><00:09:37.920><c> I</c><00:09:38.000><c> think</c><00:09:38.240><c> the</c><00:09:38.440><c> entire</c>

00:09:38.870 --> 00:09:38.880 align:start position:0%
alternative Direction I think the entire
 

00:09:38.880 --> 00:09:42.389 align:start position:0%
alternative Direction I think the entire
success<00:09:39.480><c> of</c><00:09:40.480><c> uh</c><00:09:40.680><c> what</c><00:09:40.880><c> ethereum</c><00:09:41.360><c> is</c><00:09:41.519><c> built</c><00:09:42.040><c> and</c>

00:09:42.389 --> 00:09:42.399 align:start position:0%
success of uh what ethereum is built and
 

00:09:42.399 --> 00:09:44.870 align:start position:0%
success of uh what ethereum is built and
cryptocurrency<00:09:43.160><c> in</c><00:09:43.320><c> general</c><00:09:43.800><c> is</c><00:09:44.000><c> reliant</c><00:09:44.640><c> on</c>

00:09:44.870 --> 00:09:44.880 align:start position:0%
cryptocurrency in general is reliant on
 

00:09:44.880 --> 00:09:48.110 align:start position:0%
cryptocurrency in general is reliant on
a<00:09:45.200><c> open</c><00:09:45.839><c> ecosystem</c><00:09:46.839><c> so</c><00:09:47.279><c> I</c><00:09:47.519><c> I'm</c><00:09:47.680><c> really</c>

00:09:48.110 --> 00:09:48.120 align:start position:0%
a open ecosystem so I I'm really
 

00:09:48.120 --> 00:09:50.150 align:start position:0%
a open ecosystem so I I'm really
encouraged<00:09:48.720><c> by</c><00:09:48.880><c> that</c><00:09:49.079><c> our</c><00:09:49.279><c> open-</c><00:09:49.640><c> source</c>

00:09:50.150 --> 00:09:50.160 align:start position:0%
encouraged by that our open- source
 

00:09:50.160 --> 00:09:53.430 align:start position:0%
encouraged by that our open- source
position<00:09:50.880><c> is</c><00:09:51.480><c> uh</c><00:09:51.920><c> pretty</c><00:09:52.360><c> strong</c><00:09:52.640><c> there's</c><00:09:53.240><c> uh</c>

00:09:53.430 --> 00:09:53.440 align:start position:0%
position is uh pretty strong there's uh
 

00:09:53.440 --> 00:09:56.590 align:start position:0%
position is uh pretty strong there's uh
certainly<00:09:54.079><c> different</c><00:09:54.600><c> business</c><00:09:55.000><c> models</c><00:09:55.600><c> that</c>

00:09:56.590 --> 00:09:56.600 align:start position:0%
certainly different business models that
 

00:09:56.600 --> 00:09:59.430 align:start position:0%
certainly different business models that
uh<00:09:56.800><c> can</c><00:09:56.959><c> be</c><00:09:57.200><c> successful</c><00:09:57.959><c> around</c><00:09:58.320><c> that</c><00:09:58.640><c> and</c><00:09:59.000><c> uh</c>

00:09:59.430 --> 00:09:59.440 align:start position:0%
uh can be successful around that and uh
 

00:09:59.440 --> 00:10:03.480 align:start position:0%
uh can be successful around that and uh
are<00:09:59.600><c> Keen</c><00:09:59.839><c> to</c><00:10:00.040><c> explore</c><00:10:00.480><c> that</c>