WEBVTT
Kind: captions
Language: en

00:00:00.000 --> 00:00:04.350 align:start position:0%
 
foreign

00:00:04.350 --> 00:00:04.360 align:start position:0%
 
 

00:00:04.360 --> 00:00:13.330 align:start position:0%
 
[Music]

00:00:13.330 --> 00:00:13.340 align:start position:0%
 
 

00:00:13.340 --> 00:00:15.709 align:start position:0%
 
good<00:00:14.340><c> afternoon</c><00:00:14.460><c> everyone</c><00:00:15.000><c> my</c><00:00:15.540><c> name</c><00:00:15.660><c> is</c>

00:00:15.709 --> 00:00:15.719 align:start position:0%
good afternoon everyone my name is
 

00:00:15.719 --> 00:00:18.710 align:start position:0%
good afternoon everyone my name is
koshal<00:00:16.320><c> I</c><00:00:17.100><c> am</c>

00:00:18.710 --> 00:00:18.720 align:start position:0%
koshal I am
 

00:00:18.720 --> 00:00:21.349 align:start position:0%
koshal I am
from<00:00:19.140><c> the</c><00:00:19.260><c> Nimbus</c><00:00:19.619><c> client</c><00:00:19.980><c> team</c><00:00:20.359><c> hopefully</c>

00:00:21.349 --> 00:00:21.359 align:start position:0%
from the Nimbus client team hopefully
 

00:00:21.359 --> 00:00:22.970 align:start position:0%
from the Nimbus client team hopefully
you'll<00:00:21.600><c> know</c><00:00:21.779><c> what</c><00:00:22.020><c> members</c><00:00:22.380><c> client</c><00:00:22.619><c> team</c><00:00:22.800><c> is</c>

00:00:22.970 --> 00:00:22.980 align:start position:0%
you'll know what members client team is
 

00:00:22.980 --> 00:00:25.790 align:start position:0%
you'll know what members client team is
but<00:00:23.220><c> if</c><00:00:23.580><c> not</c><00:00:23.699><c> I'll</c><00:00:23.939><c> talk</c><00:00:24.119><c> to</c><00:00:24.240><c> you</c><00:00:24.359><c> about</c><00:00:24.600><c> that</c><00:00:24.840><c> I</c>

00:00:25.790 --> 00:00:25.800 align:start position:0%
but if not I'll talk to you about that I
 

00:00:25.800 --> 00:00:27.650 align:start position:0%
but if not I'll talk to you about that I
support<00:00:26.100><c> Nimbus</c><00:00:26.699><c> client</c><00:00:27.119><c> team</c><00:00:27.300><c> with</c><00:00:27.539><c> their</c>

00:00:27.650 --> 00:00:27.660 align:start position:0%
support Nimbus client team with their
 

00:00:27.660 --> 00:00:29.450 align:start position:0%
support Nimbus client team with their
ecosystem<00:00:28.080><c> development</c><00:00:28.619><c> efforts</c><00:00:29.099><c> which</c>

00:00:29.450 --> 00:00:29.460 align:start position:0%
ecosystem development efforts which
 

00:00:29.460 --> 00:00:31.790 align:start position:0%
ecosystem development efforts which
means<00:00:29.760><c> I</c><00:00:29.939><c> get</c><00:00:30.060><c> to</c><00:00:30.240><c> go</c><00:00:30.359><c> out</c><00:00:30.480><c> and</c><00:00:30.660><c> talk</c><00:00:30.900><c> to</c><00:00:31.080><c> end</c>

00:00:31.790 --> 00:00:31.800 align:start position:0%
means I get to go out and talk to end
 

00:00:31.800 --> 00:00:34.790 align:start position:0%
means I get to go out and talk to end
users<00:00:32.220><c> who</c><00:00:32.700><c> use</c><00:00:32.940><c> the</c><00:00:33.180><c> Nimbus</c><00:00:33.540><c> clients</c><00:00:34.020><c> or</c>

00:00:34.790 --> 00:00:34.800 align:start position:0%
users who use the Nimbus clients or
 

00:00:34.800 --> 00:00:36.889 align:start position:0%
users who use the Nimbus clients or
other<00:00:35.040><c> clients</c><00:00:35.399><c> for</c><00:00:35.579><c> that</c><00:00:35.760><c> matter</c><00:00:35.940><c> and</c>

00:00:36.889 --> 00:00:36.899 align:start position:0%
other clients for that matter and
 

00:00:36.899 --> 00:00:38.870 align:start position:0%
other clients for that matter and
understand<00:00:37.620><c> what</c><00:00:38.040><c> their</c><00:00:38.219><c> experience</c><00:00:38.579><c> is</c>

00:00:38.870 --> 00:00:38.880 align:start position:0%
understand what their experience is
 

00:00:38.880 --> 00:00:41.150 align:start position:0%
understand what their experience is
today<00:00:39.660><c> and</c><00:00:39.960><c> what</c><00:00:40.140><c> their</c><00:00:40.260><c> expectations</c><00:00:40.680><c> are</c><00:00:40.980><c> of</c>

00:00:41.150 --> 00:00:41.160 align:start position:0%
today and what their expectations are of
 

00:00:41.160 --> 00:00:44.869 align:start position:0%
today and what their expectations are of
the<00:00:41.340><c> future</c><00:00:41.660><c> so</c><00:00:42.660><c> in</c><00:00:43.079><c> this</c><00:00:43.200><c> talk</c><00:00:43.379><c> today</c><00:00:43.879><c> I</c>

00:00:44.869 --> 00:00:44.879 align:start position:0%
the future so in this talk today I
 

00:00:44.879 --> 00:00:46.250 align:start position:0%
the future so in this talk today I
should<00:00:45.000><c> start</c><00:00:45.239><c> to</c><00:00:45.360><c> use</c><00:00:45.480><c> the</c><00:00:45.660><c> clicker</c><00:00:46.020><c> as</c><00:00:46.140><c> well</c>

00:00:46.250 --> 00:00:46.260 align:start position:0%
should start to use the clicker as well
 

00:00:46.260 --> 00:00:49.430 align:start position:0%
should start to use the clicker as well
actually

00:00:49.430 --> 00:00:49.440 align:start position:0%
 
 

00:00:49.440 --> 00:00:50.569 align:start position:0%
 
foreign

00:00:50.569 --> 00:00:50.579 align:start position:0%
foreign
 

00:00:50.579 --> 00:00:53.330 align:start position:0%
foreign
there<00:00:51.480><c> we</c><00:00:51.660><c> go</c><00:00:51.719><c> yeah</c><00:00:52.559><c> so</c><00:00:52.739><c> I</c><00:00:52.920><c> just</c><00:00:52.980><c> wanted</c><00:00:53.160><c> to</c>

00:00:53.330 --> 00:00:53.340 align:start position:0%
there we go yeah so I just wanted to
 

00:00:53.340 --> 00:00:54.889 align:start position:0%
there we go yeah so I just wanted to
share<00:00:53.579><c> some</c><00:00:53.820><c> of</c><00:00:53.940><c> my</c><00:00:54.120><c> thoughts</c><00:00:54.360><c> and</c><00:00:54.480><c> experience</c>

00:00:54.889 --> 00:00:54.899 align:start position:0%
share some of my thoughts and experience
 

00:00:54.899 --> 00:00:57.830 align:start position:0%
share some of my thoughts and experience
talking<00:00:55.440><c> to</c><00:00:55.680><c> a</c><00:00:55.800><c> lot</c><00:00:55.920><c> of</c><00:00:56.100><c> the</c><00:00:56.480><c> validators</c><00:00:57.480><c> right</c>

00:00:57.830 --> 00:00:57.840 align:start position:0%
talking to a lot of the validators right
 

00:00:57.840 --> 00:01:00.290 align:start position:0%
talking to a lot of the validators right
whether<00:00:58.260><c> they</c><00:00:58.500><c> are</c><00:00:58.680><c> centralized</c><00:00:59.579><c> exchanges</c>

00:01:00.290 --> 00:01:00.300 align:start position:0%
whether they are centralized exchanges
 

00:01:00.300 --> 00:01:01.670 align:start position:0%
whether they are centralized exchanges
whether<00:01:00.660><c> they</c><00:01:00.840><c> are</c><00:01:01.020><c> the</c><00:01:01.140><c> professional</c><00:01:01.440><c> node</c>

00:01:01.670 --> 00:01:01.680 align:start position:0%
whether they are the professional node
 

00:01:01.680 --> 00:01:05.030 align:start position:0%
whether they are the professional node
operators<00:01:02.300><c> or</c><00:01:03.300><c> individual</c><00:01:03.840><c> users</c><00:01:04.320><c> I</c><00:01:04.920><c> just</c>

00:01:05.030 --> 00:01:05.040 align:start position:0%
operators or individual users I just
 

00:01:05.040 --> 00:01:07.910 align:start position:0%
operators or individual users I just
want<00:01:05.159><c> to</c><00:01:05.339><c> share</c><00:01:05.519><c> the</c><00:01:06.180><c> feedback</c><00:01:07.140><c> that</c><00:01:07.680><c> you</c><00:01:07.799><c> get</c>

00:01:07.910 --> 00:01:07.920 align:start position:0%
want to share the feedback that you get
 

00:01:07.920 --> 00:01:10.070 align:start position:0%
want to share the feedback that you get
when<00:01:08.159><c> you</c><00:01:08.340><c> talk</c><00:01:08.460><c> to</c><00:01:08.640><c> these</c><00:01:09.060><c> validators</c><00:01:09.780><c> about</c>

00:01:10.070 --> 00:01:10.080 align:start position:0%
when you talk to these validators about
 

00:01:10.080 --> 00:01:12.590 align:start position:0%
when you talk to these validators about
what's<00:01:10.500><c> the</c><00:01:10.740><c> future</c><00:01:11.060><c> of</c><00:01:12.060><c> the</c><00:01:12.299><c> client</c>

00:01:12.590 --> 00:01:12.600 align:start position:0%
what's the future of the client
 

00:01:12.600 --> 00:01:14.090 align:start position:0%
what's the future of the client
experience<00:01:13.080><c> like</c><00:01:13.380><c> what</c><00:01:13.619><c> does</c><00:01:13.799><c> the</c><00:01:13.920><c> client</c>

00:01:14.090 --> 00:01:14.100 align:start position:0%
experience like what does the client
 

00:01:14.100 --> 00:01:15.530 align:start position:0%
experience like what does the client
experience<00:01:14.460><c> need</c><00:01:14.760><c> to</c><00:01:14.880><c> look</c><00:01:15.000><c> like</c><00:01:15.180><c> in</c><00:01:15.420><c> the</c>

00:01:15.530 --> 00:01:15.540 align:start position:0%
experience need to look like in the
 

00:01:15.540 --> 00:01:16.690 align:start position:0%
experience need to look like in the
future

00:01:16.690 --> 00:01:16.700 align:start position:0%
future
 

00:01:16.700 --> 00:01:19.730 align:start position:0%
future
as<00:01:17.700><c> you</c><00:01:17.820><c> can</c><00:01:17.939><c> see</c><00:01:18.060><c> I</c><00:01:18.420><c> named</c><00:01:18.840><c> I</c><00:01:19.020><c> titled</c><00:01:19.380><c> my</c><00:01:19.619><c> talk</c>

00:01:19.730 --> 00:01:19.740 align:start position:0%
as you can see I named I titled my talk
 

00:01:19.740 --> 00:01:22.789 align:start position:0%
as you can see I named I titled my talk
validating<00:01:20.280><c> Made</c><00:01:20.580><c> Simple</c><00:01:20.939><c> light</c><00:01:21.720><c> and</c><00:01:21.960><c> simple</c>

00:01:22.789 --> 00:01:22.799 align:start position:0%
validating Made Simple light and simple
 

00:01:22.799 --> 00:01:24.830 align:start position:0%
validating Made Simple light and simple
it<00:01:23.340><c> may</c><00:01:23.580><c> be</c><00:01:23.700><c> light</c><00:01:23.880><c> but</c><00:01:24.119><c> it's</c><00:01:24.240><c> definitely</c><00:01:24.540><c> not</c>

00:01:24.830 --> 00:01:24.840 align:start position:0%
it may be light but it's definitely not
 

00:01:24.840 --> 00:01:26.870 align:start position:0%
it may be light but it's definitely not
simple<00:01:25.020><c> right</c><00:01:25.439><c> now</c><00:01:25.619><c> so</c><00:01:26.159><c> that's</c><00:01:26.700><c> something</c>

00:01:26.870 --> 00:01:26.880 align:start position:0%
simple right now so that's something
 

00:01:26.880 --> 00:01:29.090 align:start position:0%
simple right now so that's something
that<00:01:27.119><c> we</c><00:01:27.360><c> definitely</c><00:01:27.659><c> want</c><00:01:27.840><c> to</c><00:01:28.020><c> fix</c><00:01:28.200><c> in</c><00:01:28.979><c> the</c>

00:01:29.090 --> 00:01:29.100 align:start position:0%
that we definitely want to fix in the
 

00:01:29.100 --> 00:01:29.990 align:start position:0%
that we definitely want to fix in the
future

00:01:29.990 --> 00:01:30.000 align:start position:0%
future
 

00:01:30.000 --> 00:01:32.330 align:start position:0%
future
let's<00:01:30.479><c> talk</c><00:01:30.659><c> about</c><00:01:30.900><c> Nimbus</c><00:01:31.799><c> a</c><00:01:31.979><c> little</c><00:01:32.040><c> bit</c><00:01:32.220><c> so</c>

00:01:32.330 --> 00:01:32.340 align:start position:0%
let's talk about Nimbus a little bit so
 

00:01:32.340 --> 00:01:35.569 align:start position:0%
let's talk about Nimbus a little bit so
Nimbus<00:01:32.759><c> is</c><00:01:33.060><c> a</c><00:01:33.979><c> ethereum</c><00:01:34.979><c> client</c><00:01:35.280><c> it's</c><00:01:35.460><c> a</c>

00:01:35.569 --> 00:01:35.579 align:start position:0%
Nimbus is a ethereum client it's a
 

00:01:35.579 --> 00:01:37.069 align:start position:0%
Nimbus is a ethereum client it's a
consensus<00:01:35.939><c> client</c><00:01:36.240><c> that</c><00:01:36.479><c> you</c><00:01:36.540><c> can</c><00:01:36.659><c> use</c><00:01:36.780><c> right</c>

00:01:37.069 --> 00:01:37.079 align:start position:0%
consensus client that you can use right
 

00:01:37.079 --> 00:01:40.969 align:start position:0%
consensus client that you can use right
now<00:01:37.259><c> it's</c><00:01:38.159><c> an</c><00:01:38.400><c> easy</c><00:01:38.640><c> efficient</c><00:01:39.320><c> uh</c><00:01:40.320><c> low</c>

00:01:40.969 --> 00:01:40.979 align:start position:0%
now it's an easy efficient uh low
 

00:01:40.979 --> 00:01:42.950 align:start position:0%
now it's an easy efficient uh low
resource<00:01:41.340><c> intensive</c><00:01:41.820><c> or</c><00:01:42.060><c> less</c><00:01:42.360><c> very</c>

00:01:42.950 --> 00:01:42.960 align:start position:0%
resource intensive or less very
 

00:01:42.960 --> 00:01:44.929 align:start position:0%
resource intensive or less very
efficient<00:01:43.320><c> essentially</c>

00:01:44.929 --> 00:01:44.939 align:start position:0%
efficient essentially
 

00:01:44.939 --> 00:01:47.690 align:start position:0%
efficient essentially
um<00:01:45.540><c> stable</c><00:01:46.079><c> consensus</c><00:01:46.920><c> client</c><00:01:47.220><c> so</c><00:01:47.460><c> you</c><00:01:47.579><c> can</c>

00:01:47.690 --> 00:01:47.700 align:start position:0%
um stable consensus client so you can
 

00:01:47.700 --> 00:01:49.730 align:start position:0%
um stable consensus client so you can
use<00:01:47.939><c> the</c><00:01:48.299><c> Nimbus</c><00:01:48.840><c> client</c><00:01:49.140><c> with</c><00:01:49.320><c> any</c><00:01:49.500><c> other</c>

00:01:49.730 --> 00:01:49.740 align:start position:0%
use the Nimbus client with any other
 

00:01:49.740 --> 00:01:51.649 align:start position:0%
use the Nimbus client with any other
execution<00:01:50.579><c> client</c><00:01:50.939><c> if</c><00:01:51.119><c> you're</c><00:01:51.240><c> running</c><00:01:51.420><c> an</c>

00:01:51.649 --> 00:01:51.659 align:start position:0%
execution client if you're running an
 

00:01:51.659 --> 00:01:53.690 align:start position:0%
execution client if you're running an
ethereum<00:01:52.079><c> node</c>

00:01:53.690 --> 00:01:53.700 align:start position:0%
ethereum node
 

00:01:53.700 --> 00:01:56.569 align:start position:0%
ethereum node
um<00:01:54.240><c> the</c><00:01:55.079><c> story</c><00:01:55.380><c> behind</c><00:01:55.740><c> Embassy</c><00:01:56.159><c> is</c><00:01:56.280><c> obviously</c>

00:01:56.569 --> 00:01:56.579 align:start position:0%
um the story behind Embassy is obviously
 

00:01:56.579 --> 00:01:58.850 align:start position:0%
um the story behind Embassy is obviously
around<00:01:56.820><c> lowering</c><00:01:57.659><c> the</c><00:01:57.899><c> barriers</c>

00:01:58.850 --> 00:01:58.860 align:start position:0%
around lowering the barriers
 

00:01:58.860 --> 00:02:01.370 align:start position:0%
around lowering the barriers
to<00:01:59.460><c> enable</c><00:01:59.759><c> participation</c><00:02:00.540><c> in</c><00:02:00.840><c> the</c><00:02:01.020><c> ethereum</c>

00:02:01.370 --> 00:02:01.380 align:start position:0%
to enable participation in the ethereum
 

00:02:01.380 --> 00:02:03.469 align:start position:0%
to enable participation in the ethereum
network<00:02:01.680><c> and</c><00:02:02.520><c> we</c><00:02:02.640><c> are</c><00:02:02.759><c> very</c><00:02:02.880><c> specific</c><00:02:03.180><c> about</c>

00:02:03.469 --> 00:02:03.479 align:start position:0%
network and we are very specific about
 

00:02:03.479 --> 00:02:06.050 align:start position:0%
network and we are very specific about
the<00:02:03.960><c> words</c><00:02:04.079><c> it's</c><00:02:04.439><c> it's</c><00:02:04.560><c> the</c><00:02:05.340><c> ethereum</c><00:02:05.759><c> network</c>

00:02:06.050 --> 00:02:06.060 align:start position:0%
the words it's it's the ethereum network
 

00:02:06.060 --> 00:02:08.510 align:start position:0%
the words it's it's the ethereum network
not<00:02:06.719><c> ethereum</c><00:02:07.200><c> in</c><00:02:07.380><c> general</c><00:02:07.500><c> you</c><00:02:08.099><c> want</c><00:02:08.340><c> more</c>

00:02:08.510 --> 00:02:08.520 align:start position:0%
not ethereum in general you want more
 

00:02:08.520 --> 00:02:10.010 align:start position:0%
not ethereum in general you want more
participation<00:02:09.060><c> in</c><00:02:09.300><c> the</c><00:02:09.420><c> ethereum</c><00:02:09.780><c> network</c>

00:02:10.010 --> 00:02:10.020 align:start position:0%
participation in the ethereum network
 

00:02:10.020 --> 00:02:12.949 align:start position:0%
participation in the ethereum network
truly<00:02:10.920><c> see</c><00:02:11.099><c> it</c><00:02:11.280><c> decentralized</c><00:02:12.000><c> further</c><00:02:12.300><c> the</c>

00:02:12.949 --> 00:02:12.959 align:start position:0%
truly see it decentralized further the
 

00:02:12.959 --> 00:02:15.050 align:start position:0%
truly see it decentralized further the
reason<00:02:13.080><c> behind</c><00:02:13.500><c> that</c><00:02:13.680><c> is</c><00:02:13.920><c> also</c><00:02:14.280><c> the</c><00:02:14.940><c> next</c>

00:02:15.050 --> 00:02:15.060 align:start position:0%
reason behind that is also the next
 

00:02:15.060 --> 00:02:17.330 align:start position:0%
reason behind that is also the next
slide<00:02:15.480><c> which</c><00:02:15.720><c> is</c><00:02:15.900><c> it's</c><00:02:16.500><c> part</c><00:02:16.800><c> of</c><00:02:16.980><c> the</c><00:02:17.160><c> status</c>

00:02:17.330 --> 00:02:17.340 align:start position:0%
slide which is it's part of the status
 

00:02:17.340 --> 00:02:20.869 align:start position:0%
slide which is it's part of the status
Network<00:02:17.760><c> portfolio</c><00:02:18.480><c> of</c><00:02:18.660><c> projects</c><00:02:19.700><c> you</c><00:02:20.700><c> will</c>

00:02:20.869 --> 00:02:20.879 align:start position:0%
Network portfolio of projects you will
 

00:02:20.879 --> 00:02:22.729 align:start position:0%
Network portfolio of projects you will
many<00:02:21.180><c> of</c><00:02:21.360><c> you</c><00:02:21.480><c> will</c><00:02:21.720><c> recognize</c><00:02:22.200><c> the</c><00:02:22.560><c> status</c>

00:02:22.729 --> 00:02:22.739 align:start position:0%
many of you will recognize the status
 

00:02:22.739 --> 00:02:25.430 align:start position:0%
many of you will recognize the status
Network<00:02:23.580><c> project</c><00:02:23.940><c> or</c><00:02:24.300><c> the</c><00:02:24.480><c> status</c><00:02:24.660><c> app</c><00:02:25.020><c> for</c>

00:02:25.430 --> 00:02:25.440 align:start position:0%
Network project or the status app for
 

00:02:25.440 --> 00:02:27.589 align:start position:0%
Network project or the status app for
example<00:02:25.680><c> many</c><00:02:26.400><c> of</c><00:02:26.580><c> you</c><00:02:26.640><c> will</c><00:02:26.879><c> have</c><00:02:27.060><c> that</c><00:02:27.300><c> on</c>

00:02:27.589 --> 00:02:27.599 align:start position:0%
example many of you will have that on
 

00:02:27.599 --> 00:02:29.570 align:start position:0%
example many of you will have that on
your<00:02:27.720><c> app</c><00:02:27.959><c> on</c><00:02:28.260><c> your</c><00:02:28.620><c> phones</c><00:02:28.860><c> as</c><00:02:29.040><c> well</c><00:02:29.220><c> and</c>

00:02:29.570 --> 00:02:29.580 align:start position:0%
your app on your phones as well and
 

00:02:29.580 --> 00:02:32.210 align:start position:0%
your app on your phones as well and
hopefully<00:02:29.879><c> you're</c><00:02:30.000><c> using</c><00:02:30.300><c> it</c><00:02:30.920><c> but</c><00:02:31.920><c> the</c><00:02:32.099><c> story</c>

00:02:32.210 --> 00:02:32.220 align:start position:0%
hopefully you're using it but the story
 

00:02:32.220 --> 00:02:35.510 align:start position:0%
hopefully you're using it but the story
is<00:02:32.640><c> status</c><00:02:33.480><c> started</c><00:02:34.140><c> back</c><00:02:34.379><c> in</c><00:02:34.560><c> 2017</c><00:02:34.920><c> with</c><00:02:35.280><c> a</c>

00:02:35.510 --> 00:02:35.520 align:start position:0%
is status started back in 2017 with a
 

00:02:35.520 --> 00:02:37.070 align:start position:0%
is status started back in 2017 with a
decent<00:02:35.879><c> with</c><00:02:36.180><c> the</c><00:02:36.300><c> mission</c><00:02:36.420><c> to</c><00:02:36.660><c> create</c><00:02:36.780><c> a</c>

00:02:37.070 --> 00:02:37.080 align:start position:0%
decent with the mission to create a
 

00:02:37.080 --> 00:02:39.290 align:start position:0%
decent with the mission to create a
decentralized<00:02:37.620><c> peer-to-peer</c><00:02:38.520><c> censorship</c>

00:02:39.290 --> 00:02:39.300 align:start position:0%
decentralized peer-to-peer censorship
 

00:02:39.300 --> 00:02:41.809 align:start position:0%
decentralized peer-to-peer censorship
resistant<00:02:39.900><c> chat</c><00:02:40.260><c> application</c><00:02:40.739><c> but</c><00:02:41.519><c> as</c><00:02:41.700><c> we</c>

00:02:41.809 --> 00:02:41.819 align:start position:0%
resistant chat application but as we
 

00:02:41.819 --> 00:02:43.130 align:start position:0%
resistant chat application but as we
started<00:02:42.180><c> building</c><00:02:42.360><c> it</c><00:02:42.599><c> we</c><00:02:42.780><c> realized</c><00:02:43.080><c> that</c>

00:02:43.130 --> 00:02:43.140 align:start position:0%
started building it we realized that
 

00:02:43.140 --> 00:02:44.150 align:start position:0%
started building it we realized that
there<00:02:43.319><c> is</c><00:02:43.440><c> a</c><00:02:43.500><c> lot</c><00:02:43.620><c> of</c><00:02:43.680><c> work</c><00:02:43.860><c> on</c><00:02:44.040><c> the</c>

00:02:44.150 --> 00:02:44.160 align:start position:0%
there is a lot of work on the
 

00:02:44.160 --> 00:02:45.410 align:start position:0%
there is a lot of work on the
infrastructure<00:02:44.580><c> side</c><00:02:44.760><c> that</c><00:02:45.060><c> needs</c><00:02:45.239><c> to</c><00:02:45.300><c> be</c>

00:02:45.410 --> 00:02:45.420 align:start position:0%
infrastructure side that needs to be
 

00:02:45.420 --> 00:02:47.869 align:start position:0%
infrastructure side that needs to be
done<00:02:45.599><c> and</c><00:02:46.379><c> that</c><00:02:46.560><c> includes</c><00:02:46.980><c> building</c><00:02:47.640><c> the</c>

00:02:47.869 --> 00:02:47.879 align:start position:0%
done and that includes building the
 

00:02:47.879 --> 00:02:50.210 align:start position:0%
done and that includes building the
infrastructure<00:02:48.360><c> for</c><00:02:48.599><c> enabling</c><00:02:49.080><c> a</c><00:02:49.860><c> completely</c>

00:02:50.210 --> 00:02:50.220 align:start position:0%
infrastructure for enabling a completely
 

00:02:50.220 --> 00:02:51.830 align:start position:0%
infrastructure for enabling a completely
decentralized<00:02:50.760><c> peer-to-peer</c><00:02:51.360><c> messaging</c>

00:02:51.830 --> 00:02:51.840 align:start position:0%
decentralized peer-to-peer messaging
 

00:02:51.840 --> 00:02:54.589 align:start position:0%
decentralized peer-to-peer messaging
storage<00:02:52.620><c> and</c><00:02:53.280><c> compute</c><00:02:53.819><c> and</c><00:02:54.180><c> that</c><00:02:54.360><c> is</c><00:02:54.420><c> where</c>

00:02:54.589 --> 00:02:54.599 align:start position:0%
storage and compute and that is where
 

00:02:54.599 --> 00:02:56.110 align:start position:0%
storage and compute and that is where
some<00:02:54.840><c> of</c><00:02:54.900><c> these</c><00:02:55.140><c> projects</c><00:02:55.500><c> actually</c><00:02:55.680><c> fit</c><00:02:55.980><c> in</c>

00:02:56.110 --> 00:02:56.120 align:start position:0%
some of these projects actually fit in
 

00:02:56.120 --> 00:02:58.369 align:start position:0%
some of these projects actually fit in
if<00:02:57.120><c> you</c><00:02:57.239><c> want</c><00:02:57.360><c> to</c><00:02:57.540><c> know</c><00:02:57.660><c> more</c><00:02:57.840><c> about</c><00:02:58.080><c> some</c><00:02:58.319><c> of</c>

00:02:58.369 --> 00:02:58.379 align:start position:0%
if you want to know more about some of
 

00:02:58.379 --> 00:03:01.610 align:start position:0%
if you want to know more about some of
these<00:02:58.560><c> projects</c><00:02:58.800><c> please</c><00:02:59.640><c> pop</c><00:02:59.819><c> by</c><00:03:00.180><c> the</c><00:03:00.620><c> Nimbus</c>

00:03:01.610 --> 00:03:01.620 align:start position:0%
these projects please pop by the Nimbus
 

00:03:01.620 --> 00:03:04.729 align:start position:0%
these projects please pop by the Nimbus
booth<00:03:01.980><c> on</c><00:03:02.519><c> the</c><00:03:02.760><c> on</c><00:03:02.940><c> Level</c><00:03:03.239><c> 3</c><00:03:03.480><c> and</c><00:03:04.260><c> we'll</c><00:03:04.560><c> be</c>

00:03:04.729 --> 00:03:04.739 align:start position:0%
booth on the on Level 3 and we'll be
 

00:03:04.739 --> 00:03:06.949 align:start position:0%
booth on the on Level 3 and we'll be
happy<00:03:04.920><c> to</c><00:03:05.099><c> talk</c><00:03:05.340><c> through</c><00:03:05.879><c> the</c><00:03:06.540><c> details</c><00:03:06.900><c> of</c>

00:03:06.949 --> 00:03:06.959 align:start position:0%
happy to talk through the details of
 

00:03:06.959 --> 00:03:08.509 align:start position:0%
happy to talk through the details of
each<00:03:07.140><c> of</c><00:03:07.260><c> these</c><00:03:07.440><c> projects</c>

00:03:08.509 --> 00:03:08.519 align:start position:0%
each of these projects
 

00:03:08.519 --> 00:03:10.190 align:start position:0%
each of these projects
but<00:03:08.940><c> there</c><00:03:09.060><c> is</c><00:03:09.180><c> a</c><00:03:09.300><c> Common</c><00:03:09.420><c> Thread</c><00:03:09.780><c> that</c><00:03:09.959><c> runs</c>

00:03:10.190 --> 00:03:10.200 align:start position:0%
but there is a Common Thread that runs
 

00:03:10.200 --> 00:03:11.750 align:start position:0%
but there is a Common Thread that runs
across<00:03:10.500><c> all</c><00:03:10.680><c> these</c><00:03:10.860><c> projects</c><00:03:11.159><c> and</c><00:03:11.340><c> that</c><00:03:11.459><c> is</c><00:03:11.640><c> to</c>

00:03:11.750 --> 00:03:11.760 align:start position:0%
across all these projects and that is to
 

00:03:11.760 --> 00:03:13.850 align:start position:0%
across all these projects and that is to
enable<00:03:12.000><c> true</c><00:03:12.360><c> true</c><00:03:12.659><c> decentralization</c><00:03:13.440><c> right</c>

00:03:13.850 --> 00:03:13.860 align:start position:0%
enable true true decentralization right
 

00:03:13.860 --> 00:03:16.790 align:start position:0%
enable true true decentralization right
and<00:03:14.700><c> the</c><00:03:15.239><c> focus</c><00:03:15.480><c> on</c><00:03:15.659><c> privacy</c><00:03:16.019><c> and</c><00:03:16.319><c> censorship</c>

00:03:16.790 --> 00:03:16.800 align:start position:0%
and the focus on privacy and censorship
 

00:03:16.800 --> 00:03:17.990 align:start position:0%
and the focus on privacy and censorship
resistance

00:03:17.990 --> 00:03:18.000 align:start position:0%
resistance
 

00:03:18.000 --> 00:03:20.630 align:start position:0%
resistance
and<00:03:18.480><c> that</c><00:03:18.659><c> sort</c><00:03:18.840><c> of</c><00:03:18.959><c> theme</c><00:03:19.140><c> flows</c><00:03:19.680><c> through</c><00:03:19.980><c> to</c>

00:03:20.630 --> 00:03:20.640 align:start position:0%
and that sort of theme flows through to
 

00:03:20.640 --> 00:03:23.350 align:start position:0%
and that sort of theme flows through to
Nimbus<00:03:21.180><c> as</c><00:03:21.420><c> well</c><00:03:21.599><c> so</c>

00:03:23.350 --> 00:03:23.360 align:start position:0%
Nimbus as well so
 

00:03:23.360 --> 00:03:25.910 align:start position:0%
Nimbus as well so
when<00:03:24.360><c> we</c><00:03:24.540><c> talk</c><00:03:24.659><c> about</c><00:03:24.780><c> the</c><00:03:25.200><c> future</c><00:03:25.379><c> client</c>

00:03:25.910 --> 00:03:25.920 align:start position:0%
when we talk about the future client
 

00:03:25.920 --> 00:03:29.270 align:start position:0%
when we talk about the future client
experience<00:03:26.459><c> right</c><00:03:27.500><c> it</c><00:03:28.500><c> needs</c><00:03:28.739><c> to</c><00:03:28.800><c> be</c><00:03:28.920><c> in</c><00:03:29.159><c> the</c>

00:03:29.270 --> 00:03:29.280 align:start position:0%
experience right it needs to be in the
 

00:03:29.280 --> 00:03:32.809 align:start position:0%
experience right it needs to be in the
context<00:03:29.640><c> of</c><00:03:30.120><c> who</c><00:03:30.540><c> the</c><00:03:30.720><c> users</c><00:03:31.019><c> are</c><00:03:31.739><c> and</c><00:03:32.459><c> both</c>

00:03:32.809 --> 00:03:32.819 align:start position:0%
context of who the users are and both
 

00:03:32.819 --> 00:03:35.030 align:start position:0%
context of who the users are and both
the<00:03:33.000><c> current</c><00:03:33.120><c> users</c><00:03:33.659><c> as</c><00:03:34.140><c> well</c><00:03:34.260><c> as</c><00:03:34.379><c> what</c><00:03:34.680><c> we</c><00:03:34.860><c> see</c>

00:03:35.030 --> 00:03:35.040 align:start position:0%
the current users as well as what we see
 

00:03:35.040 --> 00:03:37.850 align:start position:0%
the current users as well as what we see
the<00:03:35.640><c> composition</c><00:03:36.060><c> of</c><00:03:36.599><c> the</c><00:03:36.959><c> you</c><00:03:37.500><c> know</c><00:03:37.560><c> valid</c>

00:03:37.850 --> 00:03:37.860 align:start position:0%
the composition of the you know valid
 

00:03:37.860 --> 00:03:40.789 align:start position:0%
the composition of the you know valid
data<00:03:38.220><c> set</c><00:03:38.280><c> to</c><00:03:38.580><c> to</c><00:03:38.760><c> look</c><00:03:39.060><c> like</c><00:03:39.239><c> maybe</c><00:03:40.080><c> a</c><00:03:40.379><c> year</c><00:03:40.620><c> or</c>

00:03:40.789 --> 00:03:40.799 align:start position:0%
data set to to look like maybe a year or
 

00:03:40.799 --> 00:03:42.530 align:start position:0%
data set to to look like maybe a year or
two<00:03:40.920><c> down</c><00:03:41.099><c> the</c><00:03:41.280><c> line</c><00:03:41.400><c> or</c><00:03:41.640><c> future</c><00:03:41.819><c> in</c><00:03:42.120><c> future</c><00:03:42.299><c> in</c>

00:03:42.530 --> 00:03:42.540 align:start position:0%
two down the line or future in future in
 

00:03:42.540 --> 00:03:44.990 align:start position:0%
two down the line or future in future in
general<00:03:42.659><c> right</c><00:03:43.019><c> and</c><00:03:43.980><c> who</c><00:03:44.459><c> are</c><00:03:44.640><c> our</c><00:03:44.819><c> current</c>

00:03:44.990 --> 00:03:45.000 align:start position:0%
general right and who are our current
 

00:03:45.000 --> 00:03:47.630 align:start position:0%
general right and who are our current
and<00:03:45.239><c> future</c><00:03:45.420><c> users</c><00:03:45.900><c> so</c>

00:03:47.630 --> 00:03:47.640 align:start position:0%
and future users so
 

00:03:47.640 --> 00:03:49.610 align:start position:0%
and future users so
our<00:03:48.120><c> current</c><00:03:48.360><c> and</c><00:03:48.540><c> future</c><00:03:48.720><c> users</c><00:03:49.200><c> can</c><00:03:49.379><c> be</c>

00:03:49.610 --> 00:03:49.620 align:start position:0%
our current and future users can be
 

00:03:49.620 --> 00:03:52.490 align:start position:0%
our current and future users can be
broadly<00:03:50.099><c> classified</c><00:03:50.580><c> into</c><00:03:51.120><c> categories</c><00:03:51.720><c> it's</c>

00:03:52.490 --> 00:03:52.500 align:start position:0%
broadly classified into categories it's
 

00:03:52.500 --> 00:03:54.410 align:start position:0%
broadly classified into categories it's
the<00:03:52.739><c> individuals</c><00:03:53.340><c> or</c><00:03:53.640><c> you</c><00:03:53.819><c> can</c><00:03:53.940><c> call</c><00:03:54.060><c> them</c><00:03:54.180><c> the</c>

00:03:54.410 --> 00:03:54.420 align:start position:0%
the individuals or you can call them the
 

00:03:54.420 --> 00:03:57.289 align:start position:0%
the individuals or you can call them the
solo<00:03:54.720><c> stakers</c><00:03:55.140><c> right</c><00:03:55.700><c> and</c><00:03:56.700><c> the</c><00:03:56.879><c> professional</c>

00:03:57.289 --> 00:03:57.299 align:start position:0%
solo stakers right and the professional
 

00:03:57.299 --> 00:03:59.830 align:start position:0%
solo stakers right and the professional
node<00:03:57.599><c> operators</c><00:03:58.080><c> now</c><00:03:58.860><c> there</c><00:03:59.159><c> are</c><00:03:59.280><c> some</c><00:03:59.519><c> other</c>

00:03:59.830 --> 00:03:59.840 align:start position:0%
node operators now there are some other
 

00:03:59.840 --> 00:04:02.210 align:start position:0%
node operators now there are some other
you<00:04:00.840><c> know</c><00:04:00.900><c> you</c><00:04:01.080><c> might</c><00:04:01.260><c> call</c><00:04:01.440><c> them</c><00:04:01.680><c> customers</c>

00:04:02.210 --> 00:04:02.220 align:start position:0%
you know you might call them customers
 

00:04:02.220 --> 00:04:03.949 align:start position:0%
you know you might call them customers
or<00:04:02.400><c> segments</c><00:04:02.879><c> that</c><00:04:03.120><c> are</c><00:04:03.239><c> in</c><00:04:03.420><c> between</c><00:04:03.540><c> but</c>

00:04:03.949 --> 00:04:03.959 align:start position:0%
or segments that are in between but
 

00:04:03.959 --> 00:04:05.570 align:start position:0%
or segments that are in between but
broadly<00:04:04.379><c> speaking</c><00:04:04.739><c> you</c><00:04:04.920><c> can</c><00:04:05.040><c> put</c><00:04:05.220><c> them</c><00:04:05.400><c> in</c>

00:04:05.570 --> 00:04:05.580 align:start position:0%
broadly speaking you can put them in
 

00:04:05.580 --> 00:04:06.949 align:start position:0%
broadly speaking you can put them in
these<00:04:05.760><c> two</c><00:04:05.879><c> one</c><00:04:06.120><c> of</c><00:04:06.239><c> these</c><00:04:06.360><c> two</c><00:04:06.480><c> categories</c>

00:04:06.949 --> 00:04:06.959 align:start position:0%
these two one of these two categories
 

00:04:06.959 --> 00:04:09.170 align:start position:0%
these two one of these two categories
and<00:04:07.500><c> we</c><00:04:07.739><c> can</c><00:04:07.920><c> work</c><00:04:08.099><c> through</c><00:04:08.280><c> the</c><00:04:08.640><c> details</c><00:04:09.000><c> as</c>

00:04:09.170 --> 00:04:09.180 align:start position:0%
and we can work through the details as
 

00:04:09.180 --> 00:04:11.390 align:start position:0%
and we can work through the details as
we<00:04:09.360><c> walk</c><00:04:09.540><c> through</c><00:04:09.720><c> the</c><00:04:09.900><c> presentation</c>

00:04:11.390 --> 00:04:11.400 align:start position:0%
we walk through the presentation
 

00:04:11.400 --> 00:04:14.990 align:start position:0%
we walk through the presentation
so<00:04:12.120><c> let's</c><00:04:12.540><c> talk</c><00:04:12.720><c> about</c><00:04:12.900><c> each</c><00:04:13.200><c> one</c><00:04:13.379><c> of</c><00:04:13.500><c> them</c><00:04:14.000><c> we</c>

00:04:14.990 --> 00:04:15.000 align:start position:0%
so let's talk about each one of them we
 

00:04:15.000 --> 00:04:16.250 align:start position:0%
so let's talk about each one of them we
will<00:04:15.180><c> talk</c><00:04:15.299><c> about</c><00:04:15.420><c> the</c><00:04:15.659><c> professional</c><00:04:16.019><c> node</c>

00:04:16.250 --> 00:04:16.260 align:start position:0%
will talk about the professional node
 

00:04:16.260 --> 00:04:18.050 align:start position:0%
will talk about the professional node
operators<00:04:16.739><c> first</c><00:04:17.040><c> and</c><00:04:17.519><c> then</c><00:04:17.639><c> we</c><00:04:17.760><c> will</c><00:04:17.880><c> talk</c>

00:04:18.050 --> 00:04:18.060 align:start position:0%
operators first and then we will talk
 

00:04:18.060 --> 00:04:20.750 align:start position:0%
operators first and then we will talk
about<00:04:18.239><c> the</c><00:04:18.540><c> individual</c><00:04:18.900><c> of</c><00:04:19.139><c> individual</c><00:04:19.760><c> users</c>

00:04:20.750 --> 00:04:20.760 align:start position:0%
about the individual of individual users
 

00:04:20.760 --> 00:04:22.850 align:start position:0%
about the individual of individual users
and<00:04:21.120><c> we'll</c><00:04:21.239><c> see</c><00:04:21.479><c> what</c><00:04:21.720><c> the</c><00:04:21.900><c> similarities</c><00:04:22.620><c> and</c>

00:04:22.850 --> 00:04:22.860 align:start position:0%
and we'll see what the similarities and
 

00:04:22.860 --> 00:04:24.770 align:start position:0%
and we'll see what the similarities and
differences<00:04:23.280><c> are</c><00:04:23.520><c> in</c><00:04:24.240><c> terms</c><00:04:24.419><c> of</c><00:04:24.600><c> their</c>

00:04:24.770 --> 00:04:24.780 align:start position:0%
differences are in terms of their
 

00:04:24.780 --> 00:04:28.490 align:start position:0%
differences are in terms of their
expectations<00:04:25.460><c> of</c><00:04:26.460><c> the</c><00:04:26.880><c> of</c><00:04:27.419><c> using</c><00:04:27.780><c> a</c><00:04:27.960><c> client</c><00:04:28.139><c> to</c>

00:04:28.490 --> 00:04:28.500 align:start position:0%
expectations of the of using a client to
 

00:04:28.500 --> 00:04:31.310 align:start position:0%
expectations of the of using a client to
run<00:04:28.620><c> a</c><00:04:28.800><c> valid</c><00:04:29.100><c> data</c>

00:04:31.310 --> 00:04:31.320 align:start position:0%
run a valid data
 

00:04:31.320 --> 00:04:33.350 align:start position:0%
run a valid data
so<00:04:31.740><c> professional</c><00:04:32.220><c> node</c><00:04:32.580><c> operators</c><00:04:33.000><c> like</c><00:04:33.180><c> who</c>

00:04:33.350 --> 00:04:33.360 align:start position:0%
so professional node operators like who
 

00:04:33.360 --> 00:04:35.930 align:start position:0%
so professional node operators like who
are<00:04:33.540><c> these</c><00:04:33.840><c> let's</c><00:04:34.560><c> do</c><00:04:34.800><c> a</c><00:04:34.979><c> quick</c><00:04:35.100><c> show</c><00:04:35.280><c> of</c><00:04:35.520><c> hands</c>

00:04:35.930 --> 00:04:35.940 align:start position:0%
are these let's do a quick show of hands
 

00:04:35.940 --> 00:04:39.469 align:start position:0%
are these let's do a quick show of hands
for<00:04:36.479><c> people</c><00:04:37.080><c> who</c><00:04:37.440><c> have</c><00:04:37.680><c> staked</c><00:04:38.220><c> their</c><00:04:38.580><c> eats</c>

00:04:39.469 --> 00:04:39.479 align:start position:0%
for people who have staked their eats
 

00:04:39.479 --> 00:04:42.890 align:start position:0%
for people who have staked their eats
with<00:04:40.380><c> let's</c><00:04:40.740><c> say</c><00:04:40.979><c> a</c><00:04:41.639><c> centralized</c><00:04:42.180><c> exchange</c><00:04:42.540><c> or</c>

00:04:42.890 --> 00:04:42.900 align:start position:0%
with let's say a centralized exchange or
 

00:04:42.900 --> 00:04:45.650 align:start position:0%
with let's say a centralized exchange or
Lido<00:04:43.440><c> or</c><00:04:43.800><c> rocket</c><00:04:44.280><c> not</c><00:04:44.699><c> rocket</c><00:04:45.180><c> pool</c><00:04:45.300><c> but</c><00:04:45.540><c> any</c>

00:04:45.650 --> 00:04:45.660 align:start position:0%
Lido or rocket not rocket pool but any
 

00:04:45.660 --> 00:04:47.570 align:start position:0%
Lido or rocket not rocket pool but any
of<00:04:45.840><c> the</c><00:04:45.900><c> Lido</c><00:04:46.320><c> or</c><00:04:46.500><c> centralized</c><00:04:46.979><c> exchanges</c><00:04:47.400><c> for</c>

00:04:47.570 --> 00:04:47.580 align:start position:0%
of the Lido or centralized exchanges for
 

00:04:47.580 --> 00:04:49.550 align:start position:0%
of the Lido or centralized exchanges for
example

00:04:49.550 --> 00:04:49.560 align:start position:0%
example
 

00:04:49.560 --> 00:04:51.650 align:start position:0%
example
all<00:04:50.160><c> right</c><00:04:50.340><c> a</c><00:04:50.580><c> few</c><00:04:50.759><c> few</c><00:04:50.940><c> hands</c><00:04:51.300><c> here</c><00:04:51.419><c> that's</c>

00:04:51.650 --> 00:04:51.660 align:start position:0%
all right a few few hands here that's
 

00:04:51.660 --> 00:04:53.930 align:start position:0%
all right a few few hands here that's
good<00:04:51.900><c> that's</c><00:04:52.199><c> good</c><00:04:52.380><c> uh</c><00:04:53.160><c> we'd</c><00:04:53.520><c> hopefully</c><00:04:53.820><c> see</c>

00:04:53.930 --> 00:04:53.940 align:start position:0%
good that's good uh we'd hopefully see
 

00:04:53.940 --> 00:04:55.129 align:start position:0%
good that's good uh we'd hopefully see
more<00:04:54.120><c> hands</c><00:04:54.479><c> when</c><00:04:54.540><c> we</c><00:04:54.720><c> come</c><00:04:54.840><c> to</c><00:04:54.960><c> the</c>

00:04:55.129 --> 00:04:55.139 align:start position:0%
more hands when we come to the
 

00:04:55.139 --> 00:04:56.050 align:start position:0%
more hands when we come to the
individual

00:04:56.050 --> 00:04:56.060 align:start position:0%
individual
 

00:04:56.060 --> 00:04:59.090 align:start position:0%
individual
sex<00:04:57.060><c> segment</c><00:04:57.479><c> but</c><00:04:58.440><c> professional</c><00:04:58.860><c> node</c>

00:04:59.090 --> 00:04:59.100 align:start position:0%
sex segment but professional node
 

00:04:59.100 --> 00:05:01.010 align:start position:0%
sex segment but professional node
operators<00:04:59.520><c> are</c><00:04:59.880><c> an</c><00:05:00.060><c> important</c><00:05:00.360><c> part</c><00:05:00.600><c> of</c><00:05:00.780><c> the</c>

00:05:01.010 --> 00:05:01.020 align:start position:0%
operators are an important part of the
 

00:05:01.020 --> 00:05:03.469 align:start position:0%
operators are an important part of the
part<00:05:01.800><c> of</c><00:05:01.919><c> the</c><00:05:02.040><c> network</c><00:05:02.160><c> right</c><00:05:02.580><c> now</c><00:05:02.759><c> like</c><00:05:03.300><c> it's</c>

00:05:03.469 --> 00:05:03.479 align:start position:0%
part of the network right now like it's
 

00:05:03.479 --> 00:05:05.210 align:start position:0%
part of the network right now like it's
not<00:05:03.660><c> a</c><00:05:03.780><c> segment</c><00:05:04.020><c> we</c><00:05:04.259><c> can</c><00:05:04.380><c> ignore</c><00:05:04.800><c> right</c>

00:05:05.210 --> 00:05:05.220 align:start position:0%
not a segment we can ignore right
 

00:05:05.220 --> 00:05:07.030 align:start position:0%
not a segment we can ignore right
whether<00:05:05.580><c> we</c><00:05:05.820><c> like</c><00:05:05.940><c> it</c><00:05:06.060><c> or</c><00:05:06.240><c> not</c><00:05:06.360><c> they</c><00:05:06.600><c> are</c><00:05:06.780><c> here</c>

00:05:07.030 --> 00:05:07.040 align:start position:0%
whether we like it or not they are here
 

00:05:07.040 --> 00:05:10.010 align:start position:0%
whether we like it or not they are here
they<00:05:08.040><c> do</c><00:05:08.280><c> offer</c><00:05:08.699><c> an</c><00:05:08.940><c> important</c><00:05:09.419><c> service</c><00:05:09.660><c> right</c>

00:05:10.010 --> 00:05:10.020 align:start position:0%
they do offer an important service right
 

00:05:10.020 --> 00:05:12.590 align:start position:0%
they do offer an important service right
now<00:05:10.199><c> and</c><00:05:10.860><c> they</c><00:05:11.100><c> are</c><00:05:11.280><c> a</c><00:05:11.520><c> large</c><00:05:11.759><c> part</c><00:05:12.240><c> of</c><00:05:12.419><c> the</c>

00:05:12.590 --> 00:05:12.600 align:start position:0%
now and they are a large part of the
 

00:05:12.600 --> 00:05:15.110 align:start position:0%
now and they are a large part of the
network<00:05:12.720><c> that</c><00:05:13.199><c> is</c><00:05:13.380><c> that</c><00:05:13.800><c> needs</c><00:05:14.220><c> to</c><00:05:14.280><c> be</c><00:05:14.520><c> taken</c>

00:05:15.110 --> 00:05:15.120 align:start position:0%
network that is that needs to be taken
 

00:05:15.120 --> 00:05:16.670 align:start position:0%
network that is that needs to be taken
seriously<00:05:15.479><c> in</c><00:05:15.660><c> terms</c><00:05:15.840><c> of</c><00:05:15.960><c> their</c><00:05:16.259><c> expectations</c>

00:05:16.670 --> 00:05:16.680 align:start position:0%
seriously in terms of their expectations
 

00:05:16.680 --> 00:05:20.270 align:start position:0%
seriously in terms of their expectations
as<00:05:17.040><c> well</c><00:05:17.699><c> so</c><00:05:18.660><c> in</c><00:05:19.320><c> my</c><00:05:19.440><c> role</c><00:05:19.620><c> I</c><00:05:19.800><c> have</c><00:05:19.919><c> had</c><00:05:20.100><c> the</c>

00:05:20.270 --> 00:05:20.280 align:start position:0%
as well so in my role I have had the
 

00:05:20.280 --> 00:05:22.010 align:start position:0%
as well so in my role I have had the
opportunity<00:05:20.580><c> to</c><00:05:20.820><c> speak</c><00:05:21.000><c> with</c><00:05:21.180><c> about</c><00:05:21.360><c> 12</c><00:05:21.660><c> to</c><00:05:21.840><c> 15</c>

00:05:22.010 --> 00:05:22.020 align:start position:0%
opportunity to speak with about 12 to 15
 

00:05:22.020 --> 00:05:24.290 align:start position:0%
opportunity to speak with about 12 to 15
node<00:05:22.440><c> operators</c><00:05:22.860><c> in</c><00:05:23.580><c> the</c><00:05:23.699><c> last</c><00:05:23.759><c> six</c><00:05:23.940><c> to</c><00:05:24.120><c> eight</c>

00:05:24.290 --> 00:05:24.300 align:start position:0%
node operators in the last six to eight
 

00:05:24.300 --> 00:05:25.550 align:start position:0%
node operators in the last six to eight
months

00:05:25.550 --> 00:05:25.560 align:start position:0%
months
 

00:05:25.560 --> 00:05:27.830 align:start position:0%
months
and<00:05:26.220><c> it's</c><00:05:26.639><c> really</c><00:05:26.820><c> interesting</c><00:05:27.180><c> when</c><00:05:27.479><c> we</c><00:05:27.600><c> talk</c>

00:05:27.830 --> 00:05:27.840 align:start position:0%
and it's really interesting when we talk
 

00:05:27.840 --> 00:05:30.290 align:start position:0%
and it's really interesting when we talk
to<00:05:28.020><c> them</c><00:05:28.199><c> about</c><00:05:28.440><c> their</c><00:05:29.220><c> setup</c><00:05:29.639><c> the</c><00:05:29.820><c> history</c><00:05:30.000><c> as</c>

00:05:30.290 --> 00:05:30.300 align:start position:0%
to them about their setup the history as
 

00:05:30.300 --> 00:05:33.050 align:start position:0%
to them about their setup the history as
to<00:05:30.479><c> why</c><00:05:30.660><c> and</c><00:05:30.900><c> how</c><00:05:31.280><c> they</c><00:05:32.280><c> have</c><00:05:32.460><c> set</c><00:05:32.639><c> up</c><00:05:32.759><c> the</c><00:05:32.880><c> node</c>

00:05:33.050 --> 00:05:33.060 align:start position:0%
to why and how they have set up the node
 

00:05:33.060 --> 00:05:35.330 align:start position:0%
to why and how they have set up the node
operations<00:05:33.539><c> that</c><00:05:34.320><c> we</c><00:05:34.500><c> understand</c><00:05:34.680><c> you</c><00:05:35.280><c> know</c>

00:05:35.330 --> 00:05:35.340 align:start position:0%
operations that we understand you know
 

00:05:35.340 --> 00:05:36.950 align:start position:0%
operations that we understand you know
why<00:05:35.580><c> they've</c><00:05:35.820><c> chosen</c><00:05:36.180><c> certain</c><00:05:36.419><c> clients</c><00:05:36.780><c> and</c>

00:05:36.950 --> 00:05:36.960 align:start position:0%
why they've chosen certain clients and
 

00:05:36.960 --> 00:05:38.270 align:start position:0%
why they've chosen certain clients and
why<00:05:37.139><c> they've</c><00:05:37.380><c> chosen</c><00:05:37.620><c> to</c><00:05:37.740><c> work</c><00:05:37.860><c> with</c><00:05:38.100><c> certain</c>

00:05:38.270 --> 00:05:38.280 align:start position:0%
why they've chosen to work with certain
 

00:05:38.280 --> 00:05:41.689 align:start position:0%
why they've chosen to work with certain
clients<00:05:38.759><c> and</c><00:05:39.720><c> in</c><00:05:40.380><c> that</c><00:05:40.620><c> process</c><00:05:40.919><c> we</c><00:05:41.280><c> learned</c><00:05:41.580><c> a</c>

00:05:41.689 --> 00:05:41.699 align:start position:0%
clients and in that process we learned a
 

00:05:41.699 --> 00:05:43.010 align:start position:0%
clients and in that process we learned a
few<00:05:41.820><c> things</c><00:05:42.000><c> which</c><00:05:42.300><c> is</c><00:05:42.419><c> which</c><00:05:42.720><c> is</c><00:05:42.840><c> really</c>

00:05:43.010 --> 00:05:43.020 align:start position:0%
few things which is which is really
 

00:05:43.020 --> 00:05:44.210 align:start position:0%
few things which is which is really
interesting

00:05:44.210 --> 00:05:44.220 align:start position:0%
interesting
 

00:05:44.220 --> 00:05:45.950 align:start position:0%
interesting
some<00:05:44.639><c> of</c><00:05:44.820><c> these</c><00:05:44.940><c> node</c><00:05:45.180><c> operators</c><00:05:45.539><c> in</c><00:05:45.840><c> fact</c>

00:05:45.950 --> 00:05:45.960 align:start position:0%
some of these node operators in fact
 

00:05:45.960 --> 00:05:47.510 align:start position:0%
some of these node operators in fact
most<00:05:46.199><c> of</c><00:05:46.320><c> these</c><00:05:46.440><c> node</c><00:05:46.620><c> operators</c><00:05:47.100><c> are</c><00:05:47.340><c> quite</c>

00:05:47.510 --> 00:05:47.520 align:start position:0%
most of these node operators are quite
 

00:05:47.520 --> 00:05:50.930 align:start position:0%
most of these node operators are quite
large<00:05:47.699><c> right</c><00:05:48.360><c> by</c><00:05:49.199><c> ordinary</c><00:05:50.100><c> means</c><00:05:50.400><c> I</c><00:05:50.520><c> mean</c><00:05:50.699><c> in</c>

00:05:50.930 --> 00:05:50.940 align:start position:0%
large right by ordinary means I mean in
 

00:05:50.940 --> 00:05:52.670 align:start position:0%
large right by ordinary means I mean in
terms<00:05:51.180><c> of</c><00:05:51.240><c> comparison</c><00:05:51.660><c> they</c><00:05:52.020><c> run</c><00:05:52.199><c> anything</c>

00:05:52.670 --> 00:05:52.680 align:start position:0%
terms of comparison they run anything
 

00:05:52.680 --> 00:05:54.529 align:start position:0%
terms of comparison they run anything
between<00:05:53.039><c> two</c><00:05:53.400><c> and</c><00:05:53.580><c> a</c><00:05:53.699><c> half</c>

00:05:54.529 --> 00:05:54.539 align:start position:0%
between two and a half
 

00:05:54.539 --> 00:05:57.170 align:start position:0%
between two and a half
two<00:05:55.080><c> seven</c><00:05:55.320><c> eight</c><00:05:55.500><c> thousand</c><00:05:55.800><c> validators</c><00:05:56.400><c> that</c>

00:05:57.170 --> 00:05:57.180 align:start position:0%
two seven eight thousand validators that
 

00:05:57.180 --> 00:05:59.510 align:start position:0%
two seven eight thousand validators that
is<00:05:57.300><c> a</c><00:05:57.419><c> lot</c><00:05:57.539><c> of</c><00:05:57.660><c> validators</c><00:05:58.139><c> right</c><00:05:58.440><c> and</c><00:05:59.340><c> these</c>

00:05:59.510 --> 00:05:59.520 align:start position:0%
is a lot of validators right and these
 

00:05:59.520 --> 00:06:01.129 align:start position:0%
is a lot of validators right and these
These<00:05:59.880><c> are</c><00:06:00.000><c> individual</c><00:06:00.360><c> node</c><00:06:00.660><c> operators</c>

00:06:01.129 --> 00:06:01.139 align:start position:0%
These are individual node operators
 

00:06:01.139 --> 00:06:03.350 align:start position:0%
These are individual node operators
maybe<00:06:01.440><c> 20</c><00:06:01.740><c> 30</c><00:06:02.039><c> of</c><00:06:02.280><c> them</c><00:06:02.460><c> I</c><00:06:02.880><c> don't</c><00:06:03.060><c> have</c><00:06:03.180><c> the</c>

00:06:03.350 --> 00:06:03.360 align:start position:0%
maybe 20 30 of them I don't have the
 

00:06:03.360 --> 00:06:04.969 align:start position:0%
maybe 20 30 of them I don't have the
exact<00:06:03.600><c> count</c><00:06:03.780><c> but</c><00:06:04.199><c> I</c><00:06:04.440><c> suppose</c><00:06:04.680><c> that's</c>

00:06:04.969 --> 00:06:04.979 align:start position:0%
exact count but I suppose that's
 

00:06:04.979 --> 00:06:06.830 align:start position:0%
exact count but I suppose that's
somewhere<00:06:05.340><c> close</c><00:06:05.520><c> to</c><00:06:05.699><c> 30</c><00:06:05.820><c> 35</c><00:06:06.060><c> node</c><00:06:06.479><c> operators</c>

00:06:06.830 --> 00:06:06.840 align:start position:0%
somewhere close to 30 35 node operators
 

00:06:06.840 --> 00:06:09.110 align:start position:0%
somewhere close to 30 35 node operators
total<00:06:07.340><c> across</c><00:06:08.340><c> some</c><00:06:08.520><c> of</c><00:06:08.639><c> these</c><00:06:08.759><c> liquids</c>

00:06:09.110 --> 00:06:09.120 align:start position:0%
total across some of these liquids
 

00:06:09.120 --> 00:06:11.990 align:start position:0%
total across some of these liquids
taking<00:06:09.300><c> protocols</c><00:06:09.960><c> in</c><00:06:10.080><c> general</c>

00:06:11.990 --> 00:06:12.000 align:start position:0%
taking protocols in general
 

00:06:12.000 --> 00:06:13.670 align:start position:0%
taking protocols in general
um<00:06:12.060><c> they</c><00:06:12.360><c> tend</c><00:06:12.539><c> to</c><00:06:12.660><c> operate</c><00:06:13.020><c> from</c><00:06:13.320><c> specific</c>

00:06:13.670 --> 00:06:13.680 align:start position:0%
um they tend to operate from specific
 

00:06:13.680 --> 00:06:16.310 align:start position:0%
um they tend to operate from specific
regions<00:06:14.160><c> they</c><00:06:14.639><c> generally</c><00:06:15.000><c> are</c><00:06:15.539><c> a</c><00:06:15.900><c> registered</c>

00:06:16.310 --> 00:06:16.320 align:start position:0%
regions they generally are a registered
 

00:06:16.320 --> 00:06:18.409 align:start position:0%
regions they generally are a registered
entity<00:06:16.680><c> in</c><00:06:16.919><c> these</c><00:06:17.160><c> regions</c><00:06:17.460><c> which</c><00:06:17.759><c> means</c><00:06:18.060><c> they</c>

00:06:18.409 --> 00:06:18.419 align:start position:0%
entity in these regions which means they
 

00:06:18.419 --> 00:06:20.150 align:start position:0%
entity in these regions which means they
are<00:06:18.600><c> governed</c><00:06:19.259><c> by</c><00:06:19.440><c> the</c><00:06:19.620><c> law</c><00:06:19.800><c> of</c><00:06:19.979><c> those</c>

00:06:20.150 --> 00:06:20.160 align:start position:0%
are governed by the law of those
 

00:06:20.160 --> 00:06:23.450 align:start position:0%
are governed by the law of those
jurisdictions<00:06:20.699><c> and</c><00:06:21.660><c> they're</c><00:06:22.620><c> likely</c><00:06:23.100><c> that</c>

00:06:23.450 --> 00:06:23.460 align:start position:0%
jurisdictions and they're likely that
 

00:06:23.460 --> 00:06:25.629 align:start position:0%
jurisdictions and they're likely that
they're<00:06:23.699><c> trying</c><00:06:23.880><c> to</c><00:06:24.000><c> obviously</c>

00:06:25.629 --> 00:06:25.639 align:start position:0%
they're trying to obviously
 

00:06:25.639 --> 00:06:27.950 align:start position:0%
they're trying to obviously
scale<00:06:26.639><c> up</c><00:06:26.819><c> through</c><00:06:27.060><c> the</c><00:06:27.300><c> liquid</c><00:06:27.539><c> striking</c>

00:06:27.950 --> 00:06:27.960 align:start position:0%
scale up through the liquid striking
 

00:06:27.960 --> 00:06:31.129 align:start position:0%
scale up through the liquid striking
protocols<00:06:28.500><c> but</c><00:06:29.220><c> also</c><00:06:29.639><c> directly</c><00:06:30.180><c> trying</c><00:06:30.900><c> to</c>

00:06:31.129 --> 00:06:31.139 align:start position:0%
protocols but also directly trying to
 

00:06:31.139 --> 00:06:32.629 align:start position:0%
protocols but also directly trying to
find<00:06:31.319><c> customers</c><00:06:31.860><c> who</c><00:06:32.100><c> would</c><00:06:32.220><c> like</c><00:06:32.400><c> to</c><00:06:32.520><c> stick</c>

00:06:32.629 --> 00:06:32.639 align:start position:0%
find customers who would like to stick
 

00:06:32.639 --> 00:06:35.210 align:start position:0%
find customers who would like to stick
with<00:06:32.940><c> them</c><00:06:33.120><c> right</c><00:06:33.539><c> and</c><00:06:34.500><c> the</c><00:06:34.680><c> other</c><00:06:34.800><c> aspect</c>

00:06:35.210 --> 00:06:35.220 align:start position:0%
with them right and the other aspect
 

00:06:35.220 --> 00:06:36.590 align:start position:0%
with them right and the other aspect
that<00:06:35.460><c> is</c><00:06:35.580><c> really</c><00:06:35.759><c> interesting</c><00:06:36.120><c> is</c><00:06:36.360><c> that</c>

00:06:36.590 --> 00:06:36.600 align:start position:0%
that is really interesting is that
 

00:06:36.600 --> 00:06:38.390 align:start position:0%
that is really interesting is that
they're<00:06:36.720><c> trying</c><00:06:37.080><c> to</c><00:06:37.319><c> also</c><00:06:37.560><c> serve</c><00:06:37.919><c> the</c><00:06:38.100><c> needs</c>

00:06:38.390 --> 00:06:38.400 align:start position:0%
they're trying to also serve the needs
 

00:06:38.400 --> 00:06:41.090 align:start position:0%
they're trying to also serve the needs
of<00:06:38.639><c> Institutions</c><00:06:39.380><c> operating</c><00:06:40.380><c> from</c><00:06:40.800><c> the</c><00:06:40.979><c> same</c>

00:06:41.090 --> 00:06:41.100 align:start position:0%
of Institutions operating from the same
 

00:06:41.100 --> 00:06:43.249 align:start position:0%
of Institutions operating from the same
jurisdictions<00:06:41.759><c> why</c><00:06:42.720><c> because</c><00:06:42.960><c> they</c>

00:06:43.249 --> 00:06:43.259 align:start position:0%
jurisdictions why because they
 

00:06:43.259 --> 00:06:44.570 align:start position:0%
jurisdictions why because they
understand<00:06:43.440><c> the</c><00:06:43.919><c> jurisdiction</c><00:06:44.340><c> they</c>

00:06:44.570 --> 00:06:44.580 align:start position:0%
understand the jurisdiction they
 

00:06:44.580 --> 00:06:46.370 align:start position:0%
understand the jurisdiction they
understand<00:06:44.759><c> the</c><00:06:45.240><c> regulatory</c><00:06:45.720><c> aspects</c><00:06:46.199><c> and</c>

00:06:46.370 --> 00:06:46.380 align:start position:0%
understand the regulatory aspects and
 

00:06:46.380 --> 00:06:48.950 align:start position:0%
understand the regulatory aspects and
the<00:06:46.680><c> and</c><00:06:47.400><c> the</c><00:06:47.699><c> nature</c><00:06:48.120><c> of</c><00:06:48.240><c> business</c><00:06:48.360><c> in</c><00:06:48.780><c> that</c>

00:06:48.950 --> 00:06:48.960 align:start position:0%
the and the nature of business in that
 

00:06:48.960 --> 00:06:51.050 align:start position:0%
the and the nature of business in that
in<00:06:49.259><c> that</c><00:06:49.500><c> jurisdiction</c><00:06:50.160><c> and</c><00:06:50.880><c> the</c>

00:06:51.050 --> 00:06:51.060 align:start position:0%
in that jurisdiction and the
 

00:06:51.060 --> 00:06:52.730 align:start position:0%
in that jurisdiction and the
institutions<00:06:51.419><c> in</c><00:06:51.660><c> those</c><00:06:51.840><c> jurisdictions</c><00:06:52.319><c> seem</c>

00:06:52.730 --> 00:06:52.740 align:start position:0%
institutions in those jurisdictions seem
 

00:06:52.740 --> 00:06:55.850 align:start position:0%
institutions in those jurisdictions seem
to<00:06:52.860><c> have</c><00:06:53.100><c> a</c><00:06:53.400><c> a</c><00:06:54.180><c> inclination</c><00:06:54.840><c> to</c><00:06:55.139><c> use</c><00:06:55.319><c> and</c><00:06:55.620><c> you</c>

00:06:55.850 --> 00:06:55.860 align:start position:0%
to have a a inclination to use and you
 

00:06:55.860 --> 00:06:57.529 align:start position:0%
to have a a inclination to use and you
know<00:06:55.979><c> work</c><00:06:56.280><c> with</c><00:06:56.460><c> node</c><00:06:56.759><c> operators</c><00:06:57.120><c> from</c><00:06:57.360><c> that</c>

00:06:57.529 --> 00:06:57.539 align:start position:0%
know work with node operators from that
 

00:06:57.539 --> 00:06:59.990 align:start position:0%
know work with node operators from that
region<00:06:57.840><c> right</c><00:06:58.139><c> so</c><00:06:59.039><c> it</c><00:06:59.400><c> kind</c><00:06:59.580><c> of</c><00:06:59.699><c> makes</c><00:06:59.819><c> sense</c>

00:06:59.990 --> 00:07:00.000 align:start position:0%
region right so it kind of makes sense
 

00:07:00.000 --> 00:07:02.210 align:start position:0%
region right so it kind of makes sense
that<00:07:00.240><c> they</c><00:07:00.479><c> are</c><00:07:00.660><c> sort</c><00:07:00.840><c> of</c><00:07:00.960><c> becoming</c><00:07:01.380><c> a</c><00:07:01.860><c> channel</c>

00:07:02.210 --> 00:07:02.220 align:start position:0%
that they are sort of becoming a channel
 

00:07:02.220 --> 00:07:05.450 align:start position:0%
that they are sort of becoming a channel
for<00:07:02.639><c> the</c><00:07:02.759><c> institutions</c><00:07:03.120><c> to</c><00:07:03.360><c> come</c><00:07:03.479><c> on</c><00:07:03.660><c> board</c>

00:07:05.450 --> 00:07:05.460 align:start position:0%
for the institutions to come on board
 

00:07:05.460 --> 00:07:07.610 align:start position:0%
for the institutions to come on board
so<00:07:06.120><c> that's</c><00:07:06.360><c> another</c><00:07:06.600><c> Point</c><00:07:06.960><c> another</c><00:07:07.199><c> reason</c>

00:07:07.610 --> 00:07:07.620 align:start position:0%
so that's another Point another reason
 

00:07:07.620 --> 00:07:10.010 align:start position:0%
so that's another Point another reason
why<00:07:08.039><c> node</c><00:07:08.699><c> operations</c><00:07:09.120><c> and</c><00:07:09.419><c> node</c><00:07:09.600><c> operators</c>

00:07:10.010 --> 00:07:10.020 align:start position:0%
why node operations and node operators
 

00:07:10.020 --> 00:07:11.870 align:start position:0%
why node operations and node operators
in<00:07:10.259><c> general</c><00:07:10.380><c> as</c><00:07:10.620><c> a</c><00:07:10.800><c> segment</c><00:07:11.039><c> are</c><00:07:11.340><c> an</c><00:07:11.520><c> important</c>

00:07:11.870 --> 00:07:11.880 align:start position:0%
in general as a segment are an important
 

00:07:11.880 --> 00:07:13.790 align:start position:0%
in general as a segment are an important
segment<00:07:12.300><c> of</c><00:07:12.600><c> the</c><00:07:12.840><c> network</c><00:07:12.960><c> and</c><00:07:13.380><c> they</c><00:07:13.560><c> need</c><00:07:13.740><c> to</c>

00:07:13.790 --> 00:07:13.800 align:start position:0%
segment of the network and they need to
 

00:07:13.800 --> 00:07:16.790 align:start position:0%
segment of the network and they need to
be<00:07:13.919><c> looked</c><00:07:14.220><c> at</c><00:07:14.280><c> in</c><00:07:14.699><c> in</c><00:07:14.819><c> that</c><00:07:15.060><c> regard</c>

00:07:16.790 --> 00:07:16.800 align:start position:0%
be looked at in in that regard
 

00:07:16.800 --> 00:07:17.570 align:start position:0%
be looked at in in that regard
um

00:07:17.570 --> 00:07:17.580 align:start position:0%
um
 

00:07:17.580 --> 00:07:20.330 align:start position:0%
um
let's<00:07:18.060><c> look</c><00:07:18.240><c> at</c><00:07:18.560><c> what</c><00:07:19.560><c> the</c><00:07:19.680><c> node</c><00:07:19.860><c> operators</c>

00:07:20.330 --> 00:07:20.340 align:start position:0%
let's look at what the node operators
 

00:07:20.340 --> 00:07:22.850 align:start position:0%
let's look at what the node operators
actually<00:07:20.639><c> look</c><00:07:20.940><c> at</c><00:07:21.120><c> in</c><00:07:21.660><c> terms</c><00:07:21.900><c> of</c><00:07:22.199><c> performance</c>

00:07:22.850 --> 00:07:22.860 align:start position:0%
actually look at in terms of performance
 

00:07:22.860 --> 00:07:24.710 align:start position:0%
actually look at in terms of performance
or<00:07:23.340><c> what</c><00:07:23.580><c> they</c><00:07:23.699><c> prioritize</c><00:07:24.240><c> as</c><00:07:24.479><c> the</c>

00:07:24.710 --> 00:07:24.720 align:start position:0%
or what they prioritize as the
 

00:07:24.720 --> 00:07:27.290 align:start position:0%
or what they prioritize as the
characteristics<00:07:25.259><c> that</c><00:07:26.160><c> are</c><00:07:26.280><c> important</c>

00:07:27.290 --> 00:07:27.300 align:start position:0%
characteristics that are important
 

00:07:27.300 --> 00:07:30.469 align:start position:0%
characteristics that are important
the<00:07:27.780><c> first</c><00:07:27.900><c> is</c><00:07:28.080><c> the</c><00:07:28.259><c> uptime</c><00:07:28.620><c> right</c><00:07:28.919><c> now</c><00:07:29.819><c> when</c>

00:07:30.469 --> 00:07:30.479 align:start position:0%
the first is the uptime right now when
 

00:07:30.479 --> 00:07:32.330 align:start position:0%
the first is the uptime right now when
you're<00:07:30.599><c> running</c><00:07:30.720><c> 7000</c><00:07:31.380><c> or</c><00:07:31.500><c> 8000</c><00:07:31.860><c> validators</c>

00:07:32.330 --> 00:07:32.340 align:start position:0%
you're running 7000 or 8000 validators
 

00:07:32.340 --> 00:07:34.790 align:start position:0%
you're running 7000 or 8000 validators
uptime<00:07:33.000><c> is</c><00:07:33.240><c> really</c><00:07:33.479><c> important</c><00:07:33.900><c> you</c><00:07:34.500><c> can't</c><00:07:34.620><c> be</c>

00:07:34.790 --> 00:07:34.800 align:start position:0%
uptime is really important you can't be
 

00:07:34.800 --> 00:07:37.490 align:start position:0%
uptime is really important you can't be
down<00:07:35.039><c> for</c><00:07:35.280><c> hours</c><00:07:35.520><c> it</c><00:07:36.240><c> needs</c><00:07:36.479><c> to</c><00:07:36.599><c> be</c><00:07:36.840><c> up</c><00:07:37.380><c> and</c>

00:07:37.490 --> 00:07:37.500 align:start position:0%
down for hours it needs to be up and
 

00:07:37.500 --> 00:07:39.110 align:start position:0%
down for hours it needs to be up and
running<00:07:37.680><c> there</c><00:07:37.979><c> needs</c><00:07:38.220><c> to</c><00:07:38.280><c> be</c><00:07:38.400><c> fair</c><00:07:38.639><c> degree</c><00:07:38.940><c> of</c>

00:07:39.110 --> 00:07:39.120 align:start position:0%
running there needs to be fair degree of
 

00:07:39.120 --> 00:07:42.290 align:start position:0%
running there needs to be fair degree of
failover<00:07:39.479><c> redundancy</c><00:07:40.199><c> in</c><00:07:40.860><c> the</c><00:07:41.039><c> system</c><00:07:41.300><c> it's</c>

00:07:42.290 --> 00:07:42.300 align:start position:0%
failover redundancy in the system it's
 

00:07:42.300 --> 00:07:44.629 align:start position:0%
failover redundancy in the system it's
like<00:07:42.599><c> a</c><00:07:42.960><c> it's</c><00:07:43.440><c> a</c><00:07:43.620><c> it's</c><00:07:43.919><c> a</c><00:07:44.039><c> significantly</c>

00:07:44.629 --> 00:07:44.639 align:start position:0%
like a it's a it's a significantly
 

00:07:44.639 --> 00:07:47.029 align:start position:0%
like a it's a it's a significantly
professional<00:07:45.599><c> or</c><00:07:45.900><c> sophisticated</c><00:07:46.440><c> operation</c>

00:07:47.029 --> 00:07:47.039 align:start position:0%
professional or sophisticated operation
 

00:07:47.039 --> 00:07:49.430 align:start position:0%
professional or sophisticated operation
that<00:07:47.520><c> the</c><00:07:47.699><c> node</c><00:07:47.880><c> operators</c><00:07:48.240><c> actually</c><00:07:48.479><c> run</c>

00:07:49.430 --> 00:07:49.440 align:start position:0%
that the node operators actually run
 

00:07:49.440 --> 00:07:51.170 align:start position:0%
that the node operators actually run
the<00:07:49.919><c> second</c><00:07:50.099><c> being</c><00:07:50.280><c> reward</c><00:07:50.699><c> performance</c>

00:07:51.170 --> 00:07:51.180 align:start position:0%
the second being reward performance
 

00:07:51.180 --> 00:07:53.029 align:start position:0%
the second being reward performance
which<00:07:51.840><c> is</c><00:07:51.960><c> extremely</c><00:07:52.319><c> important</c><00:07:52.680><c> so</c><00:07:52.860><c> the</c>

00:07:53.029 --> 00:07:53.039 align:start position:0%
which is extremely important so the
 

00:07:53.039 --> 00:07:55.309 align:start position:0%
which is extremely important so the
choice<00:07:53.160><c> of</c><00:07:53.400><c> client</c><00:07:53.639><c> is</c><00:07:53.880><c> also</c><00:07:54.120><c> based</c><00:07:54.539><c> on</c><00:07:54.599><c> you</c>

00:07:55.309 --> 00:07:55.319 align:start position:0%
choice of client is also based on you
 

00:07:55.319 --> 00:07:56.570 align:start position:0%
choice of client is also based on you
know<00:07:55.380><c> is</c><00:07:55.560><c> the</c><00:07:55.740><c> reward</c><00:07:55.979><c> performance</c><00:07:56.400><c> good</c>

00:07:56.570 --> 00:07:56.580 align:start position:0%
know is the reward performance good
 

00:07:56.580 --> 00:07:57.890 align:start position:0%
know is the reward performance good
enough

00:07:57.890 --> 00:07:57.900 align:start position:0%
enough
 

00:07:57.900 --> 00:08:00.350 align:start position:0%
enough
um<00:07:57.960><c> and</c><00:07:58.560><c> finally</c><00:07:58.800><c> operating</c><00:07:59.220><c> efficiency</c><00:07:59.819><c> like</c>

00:08:00.350 --> 00:08:00.360 align:start position:0%
um and finally operating efficiency like
 

00:08:00.360 --> 00:08:02.450 align:start position:0%
um and finally operating efficiency like
you<00:08:01.139><c> don't</c><00:08:01.259><c> want</c><00:08:01.440><c> to</c><00:08:01.620><c> hire</c><00:08:01.800><c> too</c><00:08:02.099><c> many</c><00:08:02.280><c> people</c>

00:08:02.450 --> 00:08:02.460 align:start position:0%
you don't want to hire too many people
 

00:08:02.460 --> 00:08:04.309 align:start position:0%
you don't want to hire too many people
to<00:08:02.699><c> run</c><00:08:02.880><c> the</c><00:08:03.120><c> operations</c><00:08:03.780><c> as</c><00:08:04.020><c> well</c><00:08:04.139><c> because</c>

00:08:04.309 --> 00:08:04.319 align:start position:0%
to run the operations as well because
 

00:08:04.319 --> 00:08:06.170 align:start position:0%
to run the operations as well because
that<00:08:04.620><c> impacts</c><00:08:05.039><c> the</c><00:08:05.160><c> profitability</c><00:08:05.639><c> of</c><00:08:06.000><c> their</c>

00:08:06.170 --> 00:08:06.180 align:start position:0%
that impacts the profitability of their
 

00:08:06.180 --> 00:08:08.150 align:start position:0%
that impacts the profitability of their
of<00:08:06.419><c> their</c><00:08:06.660><c> operation</c><00:08:06.960><c> in</c><00:08:07.199><c> a</c><00:08:07.319><c> way</c><00:08:07.440><c> so</c><00:08:07.919><c> these</c><00:08:08.099><c> are</c>

00:08:08.150 --> 00:08:08.160 align:start position:0%
of their operation in a way so these are
 

00:08:08.160 --> 00:08:10.249 align:start position:0%
of their operation in a way so these are
some<00:08:08.340><c> other</c><00:08:08.460><c> the</c><00:08:08.759><c> fact</c>

00:08:10.249 --> 00:08:10.259 align:start position:0%
some other the fact
 

00:08:10.259 --> 00:08:11.870 align:start position:0%
some other the fact
the fact<00:08:10.440><c> node</c><00:08:10.800><c> operators</c><00:08:11.160><c> think</c><00:08:11.460><c> about</c><00:08:11.580><c> when</c>

00:08:11.870 --> 00:08:11.880 align:start position:0%
the fact node operators think about when
 

00:08:11.880 --> 00:08:14.089 align:start position:0%
the fact node operators think about when
they<00:08:12.120><c> think</c><00:08:12.240><c> about</c><00:08:12.419><c> their</c><00:08:12.960><c> business</c><00:08:13.380><c> in</c><00:08:13.860><c> a</c><00:08:13.979><c> way</c>

00:08:14.089 --> 00:08:14.099 align:start position:0%
they think about their business in a way
 

00:08:14.099 --> 00:08:16.670 align:start position:0%
they think about their business in a way
and<00:08:14.940><c> this</c><00:08:15.240><c> is</c><00:08:15.419><c> important</c><00:08:15.780><c> because</c><00:08:16.020><c> this</c><00:08:16.380><c> feeds</c>

00:08:16.670 --> 00:08:16.680 align:start position:0%
and this is important because this feeds
 

00:08:16.680 --> 00:08:19.309 align:start position:0%
and this is important because this feeds
down<00:08:16.860><c> to</c><00:08:17.220><c> what</c><00:08:17.520><c> they</c><00:08:17.699><c> look</c><00:08:17.880><c> as</c><00:08:18.060><c> in</c><00:08:18.960><c> the</c><00:08:19.080><c> client</c>

00:08:19.309 --> 00:08:19.319 align:start position:0%
down to what they look as in the client
 

00:08:19.319 --> 00:08:21.050 align:start position:0%
down to what they look as in the client
when<00:08:19.560><c> they</c><00:08:19.740><c> select</c><00:08:19.979><c> a</c><00:08:20.099><c> client</c>

00:08:21.050 --> 00:08:21.060 align:start position:0%
when they select a client
 

00:08:21.060 --> 00:08:23.330 align:start position:0%
when they select a client
right<00:08:21.720><c> so</c>

00:08:23.330 --> 00:08:23.340 align:start position:0%
right so
 

00:08:23.340 --> 00:08:25.610 align:start position:0%
right so
things<00:08:23.879><c> like</c><00:08:24.060><c> stability</c><00:08:24.599><c> of</c><00:08:25.080><c> the</c><00:08:25.199><c> client</c><00:08:25.440><c> is</c>

00:08:25.610 --> 00:08:25.620 align:start position:0%
things like stability of the client is
 

00:08:25.620 --> 00:08:28.790 align:start position:0%
things like stability of the client is
extremely<00:08:25.979><c> important</c><00:08:26.720><c> things</c><00:08:27.720><c> like</c><00:08:28.080><c> reward</c>

00:08:28.790 --> 00:08:28.800 align:start position:0%
extremely important things like reward
 

00:08:28.800 --> 00:08:30.469 align:start position:0%
extremely important things like reward
performance<00:08:29.340><c> how</c><00:08:29.940><c> does</c><00:08:30.120><c> the</c><00:08:30.240><c> reward</c>

00:08:30.469 --> 00:08:30.479 align:start position:0%
performance how does the reward
 

00:08:30.479 --> 00:08:32.570 align:start position:0%
performance how does the reward
performance<00:08:30.900><c> of</c><00:08:31.020><c> a</c><00:08:31.259><c> client</c><00:08:31.620><c> a</c><00:08:32.099><c> compare</c><00:08:32.459><c> to</c>

00:08:32.570 --> 00:08:32.580 align:start position:0%
performance of a client a compare to
 

00:08:32.580 --> 00:08:34.250 align:start position:0%
performance of a client a compare to
client<00:08:32.820><c> B</c><00:08:33.000><c> these</c><00:08:33.539><c> are</c><00:08:33.599><c> factors</c><00:08:33.959><c> that</c><00:08:34.140><c> are</c>

00:08:34.250 --> 00:08:34.260 align:start position:0%
client B these are factors that are
 

00:08:34.260 --> 00:08:36.610 align:start position:0%
client B these are factors that are
extremely<00:08:34.620><c> important</c><00:08:35.039><c> uh</c><00:08:35.760><c> to</c><00:08:35.940><c> node</c><00:08:36.180><c> operators</c>

00:08:36.610 --> 00:08:36.620 align:start position:0%
extremely important uh to node operators
 

00:08:36.620 --> 00:08:39.829 align:start position:0%
extremely important uh to node operators
factors<00:08:37.620><c> like</c><00:08:38.039><c> fit</c><00:08:38.580><c> with</c><00:08:39.000><c> the</c><00:08:39.180><c> current</c><00:08:39.360><c> setup</c>

00:08:39.829 --> 00:08:39.839 align:start position:0%
factors like fit with the current setup
 

00:08:39.839 --> 00:08:41.810 align:start position:0%
factors like fit with the current setup
this<00:08:40.620><c> is</c><00:08:40.740><c> something</c><00:08:40.919><c> that</c><00:08:41.219><c> is</c><00:08:41.399><c> extremely</c>

00:08:41.810 --> 00:08:41.820 align:start position:0%
this is something that is extremely
 

00:08:41.820 --> 00:08:44.990 align:start position:0%
this is something that is extremely
important<00:08:42.300><c> why</c><00:08:43.020><c> because</c><00:08:43.520><c> each</c><00:08:44.520><c> client</c><00:08:44.820><c> is</c>

00:08:44.990 --> 00:08:45.000 align:start position:0%
important why because each client is
 

00:08:45.000 --> 00:08:46.910 align:start position:0%
important why because each client is
slightly<00:08:45.420><c> different</c><00:08:45.600><c> and</c><00:08:46.080><c> this</c><00:08:46.260><c> goes</c><00:08:46.500><c> back</c><00:08:46.620><c> to</c>

00:08:46.910 --> 00:08:46.920 align:start position:0%
slightly different and this goes back to
 

00:08:46.920 --> 00:08:48.710 align:start position:0%
slightly different and this goes back to
Danny<00:08:47.339><c> Ryan's</c><00:08:47.760><c> presentation</c><00:08:48.060><c> on</c><00:08:48.360><c> day</c><00:08:48.540><c> one</c>

00:08:48.710 --> 00:08:48.720 align:start position:0%
Danny Ryan's presentation on day one
 

00:08:48.720 --> 00:08:50.630 align:start position:0%
Danny Ryan's presentation on day one
where<00:08:48.959><c> he</c><00:08:49.140><c> talked</c><00:08:49.380><c> about</c><00:08:49.459><c> diversity</c><00:08:50.459><c> of</c>

00:08:50.630 --> 00:08:50.640 align:start position:0%
where he talked about diversity of
 

00:08:50.640 --> 00:08:52.850 align:start position:0%
where he talked about diversity of
perspectives<00:08:51.060><c> and</c><00:08:51.899><c> each</c><00:08:52.080><c> client</c><00:08:52.320><c> team</c><00:08:52.500><c> takes</c>

00:08:52.850 --> 00:08:52.860 align:start position:0%
perspectives and each client team takes
 

00:08:52.860 --> 00:08:55.009 align:start position:0%
perspectives and each client team takes
a<00:08:53.100><c> slightly</c><00:08:53.820><c> different</c><00:08:54.000><c> perspective</c><00:08:54.540><c> on</c><00:08:54.779><c> how</c>

00:08:55.009 --> 00:08:55.019 align:start position:0%
a slightly different perspective on how
 

00:08:55.019 --> 00:08:56.870 align:start position:0%
a slightly different perspective on how
they<00:08:55.200><c> would</c><00:08:55.320><c> like</c><00:08:55.440><c> to</c><00:08:55.620><c> architect</c><00:08:55.980><c> the</c><00:08:56.100><c> client</c>

00:08:56.870 --> 00:08:56.880 align:start position:0%
they would like to architect the client
 

00:08:56.880 --> 00:08:58.730 align:start position:0%
they would like to architect the client
now<00:08:57.480><c> when</c><00:08:57.720><c> it</c><00:08:57.839><c> comes</c><00:08:58.019><c> to</c><00:08:58.140><c> node</c><00:08:58.320><c> operations</c>

00:08:58.730 --> 00:08:58.740 align:start position:0%
now when it comes to node operations
 

00:08:58.740 --> 00:09:00.590 align:start position:0%
now when it comes to node operations
node<00:08:59.160><c> operations</c><00:08:59.519><c> like</c><00:08:59.940><c> similarity</c>

00:09:00.590 --> 00:09:00.600 align:start position:0%
node operations like similarity
 

00:09:00.600 --> 00:09:03.350 align:start position:0%
node operations like similarity
homogeneity<00:09:01.320><c> in</c><00:09:02.040><c> the</c><00:09:02.220><c> client</c><00:09:02.459><c> architecture</c>

00:09:03.350 --> 00:09:03.360 align:start position:0%
homogeneity in the client architecture
 

00:09:03.360 --> 00:09:05.810 align:start position:0%
homogeneity in the client architecture
so<00:09:03.660><c> that</c><00:09:03.779><c> it</c><00:09:03.959><c> fits</c><00:09:04.320><c> with</c><00:09:04.620><c> the</c><00:09:05.160><c> way</c><00:09:05.339><c> they</c><00:09:05.640><c> have</c>

00:09:05.810 --> 00:09:05.820 align:start position:0%
so that it fits with the way they have
 

00:09:05.820 --> 00:09:09.290 align:start position:0%
so that it fits with the way they have
started<00:09:06.779><c> to</c><00:09:06.899><c> operate</c><00:09:07.260><c> right</c><00:09:07.940><c> so</c><00:09:08.940><c> it's</c><00:09:09.060><c> really</c>

00:09:09.290 --> 00:09:09.300 align:start position:0%
started to operate right so it's really
 

00:09:09.300 --> 00:09:12.230 align:start position:0%
started to operate right so it's really
interesting<00:09:09.720><c> that</c><00:09:10.160><c> the</c><00:09:11.160><c> uh</c><00:09:11.640><c> there's</c><00:09:11.880><c> a</c><00:09:12.000><c> huge</c>

00:09:12.230 --> 00:09:12.240 align:start position:0%
interesting that the uh there's a huge
 

00:09:12.240 --> 00:09:14.449 align:start position:0%
interesting that the uh there's a huge
push<00:09:12.480><c> to</c><00:09:12.779><c> try</c><00:09:13.140><c> and</c><00:09:13.320><c> figure</c><00:09:13.500><c> out</c><00:09:13.740><c> how</c><00:09:14.100><c> to</c><00:09:14.279><c> make</c>

00:09:14.449 --> 00:09:14.459 align:start position:0%
push to try and figure out how to make
 

00:09:14.459 --> 00:09:16.550 align:start position:0%
push to try and figure out how to make
the<00:09:14.700><c> clients</c><00:09:15.000><c> actually</c><00:09:15.180><c> fit</c><00:09:15.660><c> and</c><00:09:16.019><c> work</c><00:09:16.200><c> with</c>

00:09:16.550 --> 00:09:16.560 align:start position:0%
the clients actually fit and work with
 

00:09:16.560 --> 00:09:20.449 align:start position:0%
the clients actually fit and work with
the<00:09:16.800><c> with</c><00:09:17.399><c> the</c><00:09:17.820><c> current</c><00:09:18.440><c> architecture</c><00:09:19.440><c> of</c><00:09:20.220><c> the</c>

00:09:20.449 --> 00:09:20.459 align:start position:0%
the with the current architecture of the
 

00:09:20.459 --> 00:09:22.610 align:start position:0%
the with the current architecture of the
node<00:09:20.580><c> operator</c><00:09:21.000><c> and</c><00:09:21.540><c> the</c><00:09:21.779><c> future</c><00:09:21.899><c> and</c><00:09:22.260><c> in</c><00:09:22.440><c> the</c>

00:09:22.610 --> 00:09:22.620 align:start position:0%
node operator and the future and in the
 

00:09:22.620 --> 00:09:24.590 align:start position:0%
node operator and the future and in the
direction<00:09:22.740><c> that</c><00:09:23.339><c> the</c><00:09:23.760><c> direction</c><00:09:24.120><c> in</c><00:09:24.480><c> which</c>

00:09:24.590 --> 00:09:24.600 align:start position:0%
direction that the direction in which
 

00:09:24.600 --> 00:09:28.030 align:start position:0%
direction that the direction in which
this<00:09:24.899><c> architecture</c><00:09:25.320><c> is</c><00:09:25.500><c> actually</c><00:09:25.680><c> evolving</c>

00:09:28.030 --> 00:09:28.040 align:start position:0%
this architecture is actually evolving
 

00:09:28.040 --> 00:09:30.590 align:start position:0%
this architecture is actually evolving
other<00:09:29.040><c> factors</c><00:09:29.459><c> are</c><00:09:29.760><c> are</c><00:09:30.000><c> really</c><00:09:30.240><c> important</c>

00:09:30.590 --> 00:09:30.600 align:start position:0%
other factors are are really important
 

00:09:30.600 --> 00:09:32.329 align:start position:0%
other factors are are really important
such<00:09:30.839><c> as</c><00:09:30.959><c> release</c><00:09:31.200><c> communication</c><00:09:31.860><c> and</c><00:09:32.160><c> the</c>

00:09:32.329 --> 00:09:32.339 align:start position:0%
such as release communication and the
 

00:09:32.339 --> 00:09:34.790 align:start position:0%
such as release communication and the
Rhythm<00:09:32.640><c> so</c><00:09:33.300><c> how</c><00:09:33.779><c> good</c><00:09:33.959><c> can</c><00:09:34.260><c> the</c><00:09:34.380><c> quality</c><00:09:34.620><c> of</c>

00:09:34.790 --> 00:09:34.800 align:start position:0%
Rhythm so how good can the quality of
 

00:09:34.800 --> 00:09:36.410 align:start position:0%
Rhythm so how good can the quality of
release<00:09:34.980><c> communication</c><00:09:35.640><c> the</c><00:09:35.880><c> rhythm</c><00:09:36.180><c> of</c><00:09:36.300><c> the</c>

00:09:36.410 --> 00:09:36.420 align:start position:0%
release communication the rhythm of the
 

00:09:36.420 --> 00:09:38.930 align:start position:0%
release communication the rhythm of the
release<00:09:36.540><c> communication</c><00:09:37.200><c> and</c><00:09:38.160><c> the</c><00:09:38.339><c> ability</c><00:09:38.580><c> to</c>

00:09:38.930 --> 00:09:38.940 align:start position:0%
release communication and the ability to
 

00:09:38.940 --> 00:09:40.430 align:start position:0%
release communication and the ability to
contact<00:09:39.060><c> the</c><00:09:39.420><c> team</c><00:09:39.540><c> the</c><00:09:39.839><c> ability</c><00:09:40.080><c> for</c><00:09:40.260><c> the</c>

00:09:40.430 --> 00:09:40.440 align:start position:0%
contact the team the ability for the
 

00:09:40.440 --> 00:09:41.990 align:start position:0%
contact the team the ability for the
team<00:09:40.560><c> to</c><00:09:40.740><c> turn</c><00:09:40.860><c> around</c><00:09:41.100><c> when</c><00:09:41.700><c> there</c><00:09:41.880><c> are</c>

00:09:41.990 --> 00:09:42.000 align:start position:0%
team to turn around when there are
 

00:09:42.000 --> 00:09:44.389 align:start position:0%
team to turn around when there are
issues<00:09:42.240><c> and</c><00:09:42.420><c> challenges</c><00:09:42.920><c> and</c><00:09:43.920><c> of</c><00:09:44.100><c> course</c><00:09:44.160><c> the</c>

00:09:44.389 --> 00:09:44.399 align:start position:0%
issues and challenges and of course the
 

00:09:44.399 --> 00:09:46.670 align:start position:0%
issues and challenges and of course the
testing<00:09:44.700><c> rigor</c><00:09:45.120><c> and</c><00:09:45.480><c> the</c><00:09:45.660><c> variety</c><00:09:46.140><c> of</c><00:09:46.320><c> testing</c>

00:09:46.670 --> 00:09:46.680 align:start position:0%
testing rigor and the variety of testing
 

00:09:46.680 --> 00:09:48.350 align:start position:0%
testing rigor and the variety of testing
that<00:09:46.980><c> the</c><00:09:47.160><c> team</c><00:09:47.459><c> actually</c><00:09:47.700><c> conducts</c><00:09:48.180><c> before</c>

00:09:48.350 --> 00:09:48.360 align:start position:0%
that the team actually conducts before
 

00:09:48.360 --> 00:09:49.850 align:start position:0%
that the team actually conducts before
the<00:09:48.540><c> release</c><00:09:48.660><c> scores</c><00:09:48.959><c> are</c>

00:09:49.850 --> 00:09:49.860 align:start position:0%
the release scores are
 

00:09:49.860 --> 00:09:51.650 align:start position:0%
the release scores are
so<00:09:50.279><c> these</c><00:09:50.519><c> are</c><00:09:50.640><c> all</c><00:09:50.760><c> very</c><00:09:50.940><c> important</c><00:09:51.300><c> factors</c>

00:09:51.650 --> 00:09:51.660 align:start position:0%
so these are all very important factors
 

00:09:51.660 --> 00:09:53.449 align:start position:0%
so these are all very important factors
from<00:09:51.899><c> a</c><00:09:52.019><c> node</c><00:09:52.140><c> operator</c><00:09:52.500><c> point</c><00:09:52.740><c> of</c><00:09:52.920><c> view</c><00:09:53.040><c> right</c>

00:09:53.449 --> 00:09:53.459 align:start position:0%
from a node operator point of view right
 

00:09:53.459 --> 00:09:56.389 align:start position:0%
from a node operator point of view right
and<00:09:53.940><c> as</c><00:09:54.120><c> a</c><00:09:54.300><c> client</c><00:09:54.480><c> team</c><00:09:55.260><c> we</c><00:09:55.920><c> have</c><00:09:56.040><c> to</c><00:09:56.220><c> take</c>

00:09:56.389 --> 00:09:56.399 align:start position:0%
and as a client team we have to take
 

00:09:56.399 --> 00:09:58.910 align:start position:0%
and as a client team we have to take
these<00:09:56.640><c> into</c><00:09:56.820><c> account</c><00:09:57.060><c> as</c><00:09:57.480><c> expectations</c><00:09:58.080><c> of</c><00:09:58.620><c> a</c>

00:09:58.910 --> 00:09:58.920 align:start position:0%
these into account as expectations of a
 

00:09:58.920 --> 00:10:01.610 align:start position:0%
these into account as expectations of a
potential<00:09:59.339><c> large</c><00:10:00.300><c> set</c><00:10:00.600><c> of</c><00:10:00.779><c> customers</c><00:10:01.380><c> right</c>

00:10:01.610 --> 00:10:01.620 align:start position:0%
potential large set of customers right
 

00:10:01.620 --> 00:10:04.430 align:start position:0%
potential large set of customers right
who<00:10:02.100><c> use</c><00:10:02.279><c> these</c><00:10:02.640><c> clients</c><00:10:02.940><c> essentially</c>

00:10:04.430 --> 00:10:04.440 align:start position:0%
who use these clients essentially
 

00:10:04.440 --> 00:10:06.710 align:start position:0%
who use these clients essentially
now<00:10:04.860><c> what</c><00:10:05.279><c> does</c><00:10:05.459><c> desired</c><00:10:06.060><c> client</c><00:10:06.360><c> Evolution</c>

00:10:06.710 --> 00:10:06.720 align:start position:0%
now what does desired client Evolution
 

00:10:06.720 --> 00:10:09.530 align:start position:0%
now what does desired client Evolution
look<00:10:07.080><c> like</c><00:10:07.260><c> for</c><00:10:08.220><c> from</c><00:10:08.580><c> a</c><00:10:08.760><c> node</c><00:10:08.940><c> operator</c><00:10:09.300><c> point</c>

00:10:09.530 --> 00:10:09.540 align:start position:0%
look like for from a node operator point
 

00:10:09.540 --> 00:10:10.550 align:start position:0%
look like for from a node operator point
of<00:10:09.720><c> view</c>

00:10:10.550 --> 00:10:10.560 align:start position:0%
of view
 

00:10:10.560 --> 00:10:13.730 align:start position:0%
of view
it's<00:10:11.100><c> basically</c><00:10:11.580><c> much</c><00:10:12.240><c> more</c><00:10:12.420><c> flexibility</c><00:10:13.080><c> in</c>

00:10:13.730 --> 00:10:13.740 align:start position:0%
it's basically much more flexibility in
 

00:10:13.740 --> 00:10:15.470 align:start position:0%
it's basically much more flexibility in
how<00:10:13.980><c> they</c><00:10:14.160><c> would</c><00:10:14.279><c> want</c><00:10:14.459><c> to</c><00:10:14.640><c> use</c><00:10:14.760><c> the</c><00:10:15.000><c> client</c><00:10:15.240><c> to</c>

00:10:15.470 --> 00:10:15.480 align:start position:0%
how they would want to use the client to
 

00:10:15.480 --> 00:10:17.449 align:start position:0%
how they would want to use the client to
make<00:10:15.600><c> it</c><00:10:15.779><c> work</c><00:10:15.959><c> with</c><00:10:16.320><c> their</c><00:10:16.440><c> current</c><00:10:16.620><c> setup</c>

00:10:17.449 --> 00:10:17.459 align:start position:0%
make it work with their current setup
 

00:10:17.459 --> 00:10:21.430 align:start position:0%
make it work with their current setup
and<00:10:18.420><c> much</c><00:10:19.140><c> more</c><00:10:19.380><c> interoperability</c>

00:10:21.430 --> 00:10:21.440 align:start position:0%
and much more interoperability
 

00:10:21.440 --> 00:10:24.110 align:start position:0%
and much more interoperability
interoperability<00:10:22.440><c> because</c><00:10:22.860><c> it's</c><00:10:23.760><c> not</c><00:10:24.000><c> just</c>

00:10:24.110 --> 00:10:24.120 align:start position:0%
interoperability because it's not just
 

00:10:24.120 --> 00:10:26.210 align:start position:0%
interoperability because it's not just
the<00:10:24.360><c> client</c><00:10:24.600><c> software</c><00:10:25.260><c> that</c><00:10:25.560><c> is</c><00:10:25.680><c> used</c><00:10:25.860><c> there</c>

00:10:26.210 --> 00:10:26.220 align:start position:0%
the client software that is used there
 

00:10:26.220 --> 00:10:27.949 align:start position:0%
the client software that is used there
are<00:10:26.339><c> other</c><00:10:26.519><c> other</c><00:10:26.820><c> pieces</c><00:10:27.180><c> of</c><00:10:27.360><c> components</c><00:10:27.839><c> of</c>

00:10:27.949 --> 00:10:27.959 align:start position:0%
are other other pieces of components of
 

00:10:27.959 --> 00:10:30.230 align:start position:0%
are other other pieces of components of
software<00:10:28.320><c> that</c><00:10:28.560><c> are</c><00:10:28.680><c> actually</c><00:10:28.800><c> used</c><00:10:29.240><c> in</c>

00:10:30.230 --> 00:10:30.240 align:start position:0%
software that are actually used in
 

00:10:30.240 --> 00:10:31.790 align:start position:0%
software that are actually used in
running<00:10:30.420><c> a</c><00:10:30.660><c> sophisticated</c><00:10:31.080><c> node</c><00:10:31.440><c> operation</c>

00:10:31.790 --> 00:10:31.800 align:start position:0%
running a sophisticated node operation
 

00:10:31.800 --> 00:10:33.889 align:start position:0%
running a sophisticated node operation
right<00:10:32.040><c> so</c><00:10:32.640><c> interoperability</c><00:10:33.240><c> with</c><00:10:33.600><c> all</c><00:10:33.779><c> of</c>

00:10:33.889 --> 00:10:33.899 align:start position:0%
right so interoperability with all of
 

00:10:33.899 --> 00:10:35.150 align:start position:0%
right so interoperability with all of
these<00:10:34.140><c> components</c><00:10:34.500><c> becomes</c><00:10:34.920><c> really</c>

00:10:35.150 --> 00:10:35.160 align:start position:0%
these components becomes really
 

00:10:35.160 --> 00:10:37.009 align:start position:0%
these components becomes really
important<00:10:35.580><c> when</c><00:10:36.060><c> it</c><00:10:36.180><c> comes</c><00:10:36.360><c> to</c><00:10:36.480><c> selecting</c><00:10:36.899><c> a</c>

00:10:37.009 --> 00:10:37.019 align:start position:0%
important when it comes to selecting a
 

00:10:37.019 --> 00:10:38.750 align:start position:0%
important when it comes to selecting a
client<00:10:37.200><c> and</c><00:10:37.380><c> working</c><00:10:37.560><c> with</c><00:10:37.800><c> a</c><00:10:37.920><c> client</c>

00:10:38.750 --> 00:10:38.760 align:start position:0%
client and working with a client
 

00:10:38.760 --> 00:10:40.430 align:start position:0%
client and working with a client
all<00:10:39.240><c> of</c><00:10:39.300><c> these</c><00:10:39.540><c> factors</c><00:10:39.839><c> on</c><00:10:40.080><c> all</c><00:10:40.260><c> these</c>

00:10:40.430 --> 00:10:40.440 align:start position:0%
all of these factors on all these
 

00:10:40.440 --> 00:10:41.810 align:start position:0%
all of these factors on all these
discussions<00:10:40.800><c> are</c><00:10:41.040><c> really</c><00:10:41.220><c> important</c><00:10:41.580><c> because</c>

00:10:41.810 --> 00:10:41.820 align:start position:0%
discussions are really important because
 

00:10:41.820 --> 00:10:43.730 align:start position:0%
discussions are really important because
if<00:10:42.120><c> we</c><00:10:42.300><c> want</c><00:10:42.540><c> client</c><00:10:42.959><c> diversity</c><00:10:43.440><c> in</c><00:10:43.620><c> the</c>

00:10:43.730 --> 00:10:43.740 align:start position:0%
if we want client diversity in the
 

00:10:43.740 --> 00:10:45.470 align:start position:0%
if we want client diversity in the
network<00:10:43.860><c> then</c><00:10:44.279><c> we</c><00:10:44.459><c> have</c><00:10:44.579><c> to</c><00:10:44.760><c> somehow</c><00:10:45.120><c> make</c>

00:10:45.470 --> 00:10:45.480 align:start position:0%
network then we have to somehow make
 

00:10:45.480 --> 00:10:47.269 align:start position:0%
network then we have to somehow make
sure<00:10:45.600><c> that</c><00:10:45.839><c> we</c><00:10:46.019><c> meet</c><00:10:46.200><c> these</c><00:10:46.560><c> requirements</c><00:10:47.040><c> we</c>

00:10:47.269 --> 00:10:47.279 align:start position:0%
sure that we meet these requirements we
 

00:10:47.279 --> 00:10:49.790 align:start position:0%
sure that we meet these requirements we
meet<00:10:47.459><c> these</c><00:10:47.760><c> challenges</c><00:10:48.200><c> so</c><00:10:49.200><c> that</c><00:10:49.320><c> we</c><00:10:49.500><c> can</c><00:10:49.620><c> see</c>

00:10:49.790 --> 00:10:49.800 align:start position:0%
meet these challenges so that we can see
 

00:10:49.800 --> 00:10:53.930 align:start position:0%
meet these challenges so that we can see
greater<00:10:50.220><c> diversity</c><00:10:50.720><c> in</c><00:10:51.720><c> this</c><00:10:52.019><c> segment</c><00:10:52.380><c> of</c><00:10:53.279><c> of</c>

00:10:53.930 --> 00:10:53.940 align:start position:0%
greater diversity in this segment of of
 

00:10:53.940 --> 00:10:56.090 align:start position:0%
greater diversity in this segment of of
validators<00:10:54.600><c> which</c><00:10:55.019><c> is</c><00:10:55.200><c> primarily</c><00:10:55.740><c> the</c><00:10:55.920><c> node</c>

00:10:56.090 --> 00:10:56.100 align:start position:0%
validators which is primarily the node
 

00:10:56.100 --> 00:10:57.230 align:start position:0%
validators which is primarily the node
operators<00:10:56.519><c> which</c><00:10:56.760><c> we</c><00:10:56.880><c> are</c><00:10:57.000><c> talking</c><00:10:57.120><c> about</c>

00:10:57.230 --> 00:10:57.240 align:start position:0%
operators which we are talking about
 

00:10:57.240 --> 00:10:59.030 align:start position:0%
operators which we are talking about
here

00:10:59.030 --> 00:10:59.040 align:start position:0%
here
 

00:10:59.040 --> 00:11:01.250 align:start position:0%
here
so<00:10:59.700><c> a</c><00:10:59.880><c> little</c><00:10:59.940><c> bit</c><00:11:00.180><c> about</c><00:11:00.360><c> what</c><00:11:00.720><c> Nimbus</c><00:11:01.079><c> is</c>

00:11:01.250 --> 00:11:01.260 align:start position:0%
so a little bit about what Nimbus is
 

00:11:01.260 --> 00:11:02.630 align:start position:0%
so a little bit about what Nimbus is
trying<00:11:01.440><c> to</c><00:11:01.560><c> do</c><00:11:01.680><c> to</c><00:11:01.860><c> address</c><00:11:01.980><c> these</c><00:11:02.399><c> issues</c>

00:11:02.630 --> 00:11:02.640 align:start position:0%
trying to do to address these issues
 

00:11:02.640 --> 00:11:05.509 align:start position:0%
trying to do to address these issues
right<00:11:02.940><c> so</c><00:11:03.360><c> nimba</c><00:11:04.200><c> started</c><00:11:04.500><c> when</c><00:11:05.040><c> it</c><00:11:05.220><c> went</c><00:11:05.399><c> into</c>

00:11:05.509 --> 00:11:05.519 align:start position:0%
right so nimba started when it went into
 

00:11:05.519 --> 00:11:07.370 align:start position:0%
right so nimba started when it went into
production<00:11:05.880><c> in</c><00:11:06.120><c> 2021</c><00:11:06.660><c> it's</c><00:11:06.959><c> it</c><00:11:07.200><c> was</c>

00:11:07.370 --> 00:11:07.380 align:start position:0%
production in 2021 it's it was
 

00:11:07.380 --> 00:11:09.350 align:start position:0%
production in 2021 it's it was
constructed<00:11:07.800><c> as</c><00:11:07.980><c> a</c><00:11:08.220><c> very</c><00:11:08.339><c> simple</c><00:11:08.579><c> easy</c><00:11:08.940><c> client</c>

00:11:09.350 --> 00:11:09.360 align:start position:0%
constructed as a very simple easy client
 

00:11:09.360 --> 00:11:10.430 align:start position:0%
constructed as a very simple easy client
to<00:11:09.540><c> use</c>

00:11:10.430 --> 00:11:10.440 align:start position:0%
to use
 

00:11:10.440 --> 00:11:12.829 align:start position:0%
to use
it<00:11:11.100><c> had</c><00:11:11.279><c> a</c><00:11:11.459><c> single</c><00:11:11.760><c> process</c><00:11:12.060><c> a</c><00:11:12.300><c> beacon</c><00:11:12.600><c> node</c>

00:11:12.829 --> 00:11:12.839 align:start position:0%
it had a single process a beacon node
 

00:11:12.839 --> 00:11:15.170 align:start position:0%
it had a single process a beacon node
setup<00:11:13.560><c> it</c><00:11:13.920><c> had</c><00:11:14.040><c> validated</c><00:11:14.399><c> duties</c><00:11:14.880><c> that</c><00:11:15.060><c> are</c>

00:11:15.170 --> 00:11:15.180 align:start position:0%
setup it had validated duties that are
 

00:11:15.180 --> 00:11:16.670 align:start position:0%
setup it had validated duties that are
performed<00:11:15.600><c> by</c><00:11:15.720><c> the</c><00:11:15.839><c> beacon</c><00:11:16.140><c> mode</c><00:11:16.320><c> itself</c>

00:11:16.670 --> 00:11:16.680 align:start position:0%
performed by the beacon mode itself
 

00:11:16.680 --> 00:11:18.410 align:start position:0%
performed by the beacon mode itself
which<00:11:16.920><c> means</c><00:11:17.100><c> you</c><00:11:17.220><c> don't</c><00:11:17.399><c> need</c><00:11:17.579><c> to</c><00:11:17.700><c> go</c><00:11:17.940><c> and</c><00:11:18.240><c> set</c>

00:11:18.410 --> 00:11:18.420 align:start position:0%
which means you don't need to go and set
 

00:11:18.420 --> 00:11:20.449 align:start position:0%
which means you don't need to go and set
up<00:11:18.540><c> a</c><00:11:18.660><c> separate</c><00:11:18.839><c> validator</c><00:11:19.260><c> client</c><00:11:19.620><c> so</c><00:11:20.160><c> this</c>

00:11:20.449 --> 00:11:20.459 align:start position:0%
up a separate validator client so this
 

00:11:20.459 --> 00:11:22.850 align:start position:0%
up a separate validator client so this
is<00:11:20.579><c> really</c><00:11:20.820><c> easy</c><00:11:21.060><c> for</c><00:11:21.420><c> anybody</c><00:11:21.779><c> sticking</c><00:11:22.680><c> from</c>

00:11:22.850 --> 00:11:22.860 align:start position:0%
is really easy for anybody sticking from
 

00:11:22.860 --> 00:11:23.870 align:start position:0%
is really easy for anybody sticking from
home

00:11:23.870 --> 00:11:23.880 align:start position:0%
home
 

00:11:23.880 --> 00:11:25.790 align:start position:0%
home
however<00:11:24.540><c> as</c><00:11:24.959><c> we've</c><00:11:25.260><c> talked</c><00:11:25.440><c> about</c><00:11:25.500><c> it</c>

00:11:25.790 --> 00:11:25.800 align:start position:0%
however as we've talked about it
 

00:11:25.800 --> 00:11:28.550 align:start position:0%
however as we've talked about it
previously<00:11:26.720><c> a</c><00:11:27.720><c> lot</c><00:11:27.779><c> of</c><00:11:27.839><c> node</c><00:11:28.079><c> operators</c>

00:11:28.550 --> 00:11:28.560 align:start position:0%
previously a lot of node operators
 

00:11:28.560 --> 00:11:30.170 align:start position:0%
previously a lot of node operators
actually<00:11:28.860><c> started</c><00:11:29.279><c> using</c><00:11:29.579><c> some</c><00:11:29.820><c> of</c><00:11:29.880><c> the</c><00:11:30.000><c> other</c>

00:11:30.170 --> 00:11:30.180 align:start position:0%
actually started using some of the other
 

00:11:30.180 --> 00:11:32.630 align:start position:0%
actually started using some of the other
clients<00:11:30.600><c> which</c><00:11:30.959><c> are</c><00:11:31.279><c> architected</c><00:11:32.279><c> slightly</c>

00:11:32.630 --> 00:11:32.640 align:start position:0%
clients which are architected slightly
 

00:11:32.640 --> 00:11:34.130 align:start position:0%
clients which are architected slightly
differently<00:11:33.060><c> which</c><00:11:33.480><c> means</c><00:11:33.720><c> a</c><00:11:33.899><c> separate</c>

00:11:34.130 --> 00:11:34.140 align:start position:0%
differently which means a separate
 

00:11:34.140 --> 00:11:36.230 align:start position:0%
differently which means a separate
Beacon<00:11:34.500><c> node</c><00:11:34.860><c> separate</c><00:11:35.339><c> validated</c><00:11:35.820><c> process</c>

00:11:36.230 --> 00:11:36.240 align:start position:0%
Beacon node separate validated process
 

00:11:36.240 --> 00:11:38.509 align:start position:0%
Beacon node separate validated process
and<00:11:37.200><c> the</c><00:11:37.380><c> ability</c><00:11:37.620><c> to</c><00:11:37.800><c> mix</c><00:11:37.980><c> and</c><00:11:38.160><c> match</c><00:11:38.339><c> between</c>

00:11:38.509 --> 00:11:38.519 align:start position:0%
and the ability to mix and match between
 

00:11:38.519 --> 00:11:41.269 align:start position:0%
and the ability to mix and match between
these<00:11:39.000><c> components</c><00:11:40.019><c> so</c><00:11:40.440><c> it</c><00:11:40.620><c> is</c><00:11:40.740><c> an</c><00:11:40.860><c> expectation</c>

00:11:41.269 --> 00:11:41.279 align:start position:0%
these components so it is an expectation
 

00:11:41.279 --> 00:11:42.710 align:start position:0%
these components so it is an expectation
that<00:11:41.579><c> Nimbus</c><00:11:41.940><c> also</c><00:11:42.120><c> offers</c><00:11:42.480><c> something</c>

00:11:42.710 --> 00:11:42.720 align:start position:0%
that Nimbus also offers something
 

00:11:42.720 --> 00:11:46.130 align:start position:0%
that Nimbus also offers something
similar<00:11:43.140><c> if</c><00:11:43.500><c> if</c><00:11:43.860><c> Nimbus</c><00:11:44.459><c> is</c><00:11:44.579><c> to</c><00:11:44.760><c> be</c><00:11:44.880><c> used</c>

00:11:46.130 --> 00:11:46.140 align:start position:0%
similar if if Nimbus is to be used
 

00:11:46.140 --> 00:11:48.290 align:start position:0%
similar if if Nimbus is to be used
um<00:11:46.200><c> equally</c><00:11:46.920><c> well</c><00:11:47.160><c> in</c><00:11:47.459><c> this</c><00:11:47.579><c> segment</c><00:11:47.880><c> of</c>

00:11:48.290 --> 00:11:48.300 align:start position:0%
um equally well in this segment of
 

00:11:48.300 --> 00:11:50.090 align:start position:0%
um equally well in this segment of
validators<00:11:48.959><c> in</c><00:11:49.200><c> this</c><00:11:49.380><c> segment</c><00:11:49.560><c> of</c><00:11:49.740><c> customers</c>

00:11:50.090 --> 00:11:50.100 align:start position:0%
validators in this segment of customers
 

00:11:50.100 --> 00:11:50.930 align:start position:0%
validators in this segment of customers
right

00:11:50.930 --> 00:11:50.940 align:start position:0%
right
 

00:11:50.940 --> 00:11:52.730 align:start position:0%
right
so<00:11:51.420><c> there</c><00:11:51.779><c> are</c><00:11:51.899><c> a</c><00:11:51.959><c> few</c><00:11:52.019><c> things</c><00:11:52.140><c> that</c><00:11:52.320><c> Nimbus</c>

00:11:52.730 --> 00:11:52.740 align:start position:0%
so there are a few things that Nimbus
 

00:11:52.740 --> 00:11:54.590 align:start position:0%
so there are a few things that Nimbus
has<00:11:52.860><c> done</c><00:11:53.040><c> over</c><00:11:53.220><c> the</c><00:11:53.399><c> last</c><00:11:53.519><c> I'd</c><00:11:54.180><c> say</c><00:11:54.300><c> six</c><00:11:54.480><c> to</c>

00:11:54.590 --> 00:11:54.600 align:start position:0%
has done over the last I'd say six to
 

00:11:54.600 --> 00:11:57.829 align:start position:0%
has done over the last I'd say six to
eight<00:11:54.720><c> months</c><00:11:55.019><c> things</c><00:11:55.380><c> like</c><00:11:55.880><c> supporting</c><00:11:56.880><c> the</c>

00:11:57.829 --> 00:11:57.839 align:start position:0%
eight months things like supporting the
 

00:11:57.839 --> 00:12:00.170 align:start position:0%
eight months things like supporting the
Nimbus<00:11:58.260><c> Beacon</c><00:11:58.560><c> node</c><00:11:58.860><c> with</c><00:11:59.220><c> support</c><00:11:59.880><c> for</c>

00:12:00.170 --> 00:12:00.180 align:start position:0%
Nimbus Beacon node with support for
 

00:12:00.180 --> 00:12:03.170 align:start position:0%
Nimbus Beacon node with support for
Welch<00:12:00.540><c> and</c><00:12:00.839><c> the</c><00:12:01.019><c> lighthouse</c><00:12:01.440><c> client</c><00:12:02.000><c> which</c><00:12:03.000><c> we</c>

00:12:03.170 --> 00:12:03.180 align:start position:0%
Welch and the lighthouse client which we
 

00:12:03.180 --> 00:12:06.590 align:start position:0%
Welch and the lighthouse client which we
have<00:12:03.360><c> now</c><00:12:03.600><c> in</c><00:12:03.779><c> place</c><00:12:03.959><c> and</c><00:12:04.740><c> the</c><00:12:04.980><c> Nimbus</c><00:12:05.600><c> web3</c>

00:12:06.590 --> 00:12:06.600 align:start position:0%
have now in place and the Nimbus web3
 

00:12:06.600 --> 00:12:08.449 align:start position:0%
have now in place and the Nimbus web3
sign<00:12:06.899><c> or</c><00:12:07.140><c> remote</c><00:12:07.260><c> interface</c><00:12:07.740><c> remote</c><00:12:07.920><c> standard</c>

00:12:08.449 --> 00:12:08.459 align:start position:0%
sign or remote interface remote standard
 

00:12:08.459 --> 00:12:10.430 align:start position:0%
sign or remote interface remote standard
interface<00:12:08.760><c> as</c><00:12:08.940><c> well</c><00:12:09.120><c> which</c><00:12:09.360><c> is</c><00:12:09.480><c> in</c><00:12:09.660><c> place</c><00:12:09.839><c> so</c>

00:12:10.430 --> 00:12:10.440 align:start position:0%
interface as well which is in place so
 

00:12:10.440 --> 00:12:11.509 align:start position:0%
interface as well which is in place so
these<00:12:10.680><c> are</c><00:12:10.740><c> things</c><00:12:10.920><c> that</c><00:12:11.160><c> are</c><00:12:11.339><c> really</c>

00:12:11.509 --> 00:12:11.519 align:start position:0%
these are things that are really
 

00:12:11.519 --> 00:12:14.569 align:start position:0%
these are things that are really
important<00:12:11.880><c> for</c><00:12:12.240><c> node</c><00:12:12.540><c> operators</c><00:12:13.220><c> not</c><00:12:14.220><c> as</c><00:12:14.399><c> much</c>

00:12:14.569 --> 00:12:14.579 align:start position:0%
important for node operators not as much
 

00:12:14.579 --> 00:12:16.130 align:start position:0%
important for node operators not as much
for<00:12:14.820><c> somebody</c><00:12:15.000><c> who</c><00:12:15.240><c> runs</c><00:12:15.480><c> let's</c><00:12:15.600><c> say</c><00:12:15.779><c> a</c><00:12:15.899><c> single</c>

00:12:16.130 --> 00:12:16.140 align:start position:0%
for somebody who runs let's say a single
 

00:12:16.140 --> 00:12:18.530 align:start position:0%
for somebody who runs let's say a single
validator<00:12:16.500><c> from</c><00:12:16.740><c> the</c><00:12:16.920><c> home</c><00:12:17.240><c> but</c><00:12:18.240><c> these</c><00:12:18.480><c> are</c>

00:12:18.530 --> 00:12:18.540 align:start position:0%
validator from the home but these are
 

00:12:18.540 --> 00:12:20.329 align:start position:0%
validator from the home but these are
expectations<00:12:19.019><c> from</c><00:12:19.440><c> from</c><00:12:19.620><c> a</c><00:12:19.800><c> node</c><00:12:19.980><c> operator</c>

00:12:20.329 --> 00:12:20.339 align:start position:0%
expectations from from a node operator
 

00:12:20.339 --> 00:12:22.970 align:start position:0%
expectations from from a node operator
perspective<00:12:20.820><c> the</c><00:12:21.779><c> one</c><00:12:21.959><c> big</c><00:12:22.200><c> requirement</c><00:12:22.740><c> that</c>

00:12:22.970 --> 00:12:22.980 align:start position:0%
perspective the one big requirement that
 

00:12:22.980 --> 00:12:24.650 align:start position:0%
perspective the one big requirement that
was<00:12:23.160><c> missing</c><00:12:23.399><c> the</c><00:12:23.640><c> missing</c><00:12:23.940><c> piece</c><00:12:24.180><c> I</c><00:12:24.360><c> suppose</c>

00:12:24.650 --> 00:12:24.660 align:start position:0%
was missing the missing piece I suppose
 

00:12:24.660 --> 00:12:28.130 align:start position:0%
was missing the missing piece I suppose
was<00:12:25.200><c> the</c><00:12:25.680><c> Nimbus</c><00:12:26.459><c> validator</c><00:12:27.000><c> client</c><00:12:27.360><c> or</c><00:12:27.899><c> the</c>

00:12:28.130 --> 00:12:28.140 align:start position:0%
was the Nimbus validator client or the
 

00:12:28.140 --> 00:12:30.290 align:start position:0%
was the Nimbus validator client or the
ability<00:12:28.380><c> to</c><00:12:28.680><c> split</c><00:12:28.980><c> the</c><00:12:29.100><c> client</c><00:12:29.399><c> so</c><00:12:30.060><c> having</c>

00:12:30.290 --> 00:12:30.300 align:start position:0%
ability to split the client so having
 

00:12:30.300 --> 00:12:32.329 align:start position:0%
ability to split the client so having
the<00:12:30.839><c> ability</c><00:12:31.019><c> to</c><00:12:31.320><c> use</c><00:12:31.440><c> a</c><00:12:31.680><c> separate</c><00:12:31.920><c> Beacon</c>

00:12:32.329 --> 00:12:32.339 align:start position:0%
the ability to use a separate Beacon
 

00:12:32.339 --> 00:12:34.910 align:start position:0%
the ability to use a separate Beacon
node<00:12:32.640><c> and</c><00:12:33.180><c> the</c><00:12:33.300><c> validators</c><00:12:33.839><c> separately</c><00:12:34.260><c> and</c>

00:12:34.910 --> 00:12:34.920 align:start position:0%
node and the validators separately and
 

00:12:34.920 --> 00:12:37.190 align:start position:0%
node and the validators separately and
use<00:12:35.040><c> them</c><00:12:35.279><c> into</c><00:12:35.459><c> you</c><00:12:35.820><c> know</c><00:12:35.940><c> use</c><00:12:36.120><c> them</c><00:12:36.420><c> with</c>

00:12:37.190 --> 00:12:37.200 align:start position:0%
use them into you know use them with
 

00:12:37.200 --> 00:12:38.750 align:start position:0%
use them into you know use them with
other<00:12:37.440><c> mix</c><00:12:37.740><c> mixing</c><00:12:38.160><c> and</c><00:12:38.220><c> matching</c><00:12:38.519><c> it</c><00:12:38.640><c> with</c>

00:12:38.750 --> 00:12:38.760 align:start position:0%
other mix mixing and matching it with
 

00:12:38.760 --> 00:12:41.269 align:start position:0%
other mix mixing and matching it with
other<00:12:38.880><c> client</c><00:12:39.380><c> components</c><00:12:40.380><c> essentially</c>

00:12:41.269 --> 00:12:41.279 align:start position:0%
other client components essentially
 

00:12:41.279 --> 00:12:43.850 align:start position:0%
other client components essentially
Nimbus<00:12:42.000><c> did</c><00:12:42.240><c> not</c><00:12:42.420><c> have</c><00:12:42.600><c> that</c><00:12:42.839><c> so</c><00:12:43.079><c> far</c><00:12:43.260><c> but</c><00:12:43.620><c> we</c>

00:12:43.850 --> 00:12:43.860 align:start position:0%
Nimbus did not have that so far but we
 

00:12:43.860 --> 00:12:45.769 align:start position:0%
Nimbus did not have that so far but we
have<00:12:44.040><c> it</c><00:12:44.160><c> now</c><00:12:44.339><c> and</c><00:12:44.639><c> it's</c><00:12:44.820><c> available</c><00:12:45.060><c> in</c><00:12:45.360><c> beta</c>

00:12:45.769 --> 00:12:45.779 align:start position:0%
have it now and it's available in beta
 

00:12:45.779 --> 00:12:47.150 align:start position:0%
have it now and it's available in beta
it's<00:12:45.959><c> going</c><00:12:46.139><c> out</c><00:12:46.320><c> of</c><00:12:46.440><c> beta</c><00:12:46.740><c> into</c><00:12:46.860><c> production</c>

00:12:47.150 --> 00:12:47.160 align:start position:0%
it's going out of beta into production
 

00:12:47.160 --> 00:12:50.210 align:start position:0%
it's going out of beta into production
into<00:12:47.519><c> and</c><00:12:48.240><c> ready</c><00:12:48.480><c> for</c><00:12:48.600><c> mainnet</c><00:12:49.019><c> very</c><00:12:49.260><c> soon</c><00:12:49.440><c> so</c>

00:12:50.210 --> 00:12:50.220 align:start position:0%
into and ready for mainnet very soon so
 

00:12:50.220 --> 00:12:52.250 align:start position:0%
into and ready for mainnet very soon so
these<00:12:50.459><c> are</c><00:12:50.579><c> all</c><00:12:50.820><c> the</c><00:12:51.060><c> all</c><00:12:51.420><c> the</c><00:12:51.660><c> components</c>

00:12:52.250 --> 00:12:52.260 align:start position:0%
these are all the all the components
 

00:12:52.260 --> 00:12:54.050 align:start position:0%
these are all the all the components
that<00:12:52.440><c> have</c><00:12:52.620><c> been</c><00:12:52.860><c> built</c><00:12:53.220><c> over</c><00:12:53.399><c> the</c><00:12:53.639><c> last</c><00:12:53.820><c> few</c>

00:12:54.050 --> 00:12:54.060 align:start position:0%
that have been built over the last few
 

00:12:54.060 --> 00:12:56.269 align:start position:0%
that have been built over the last few
months<00:12:54.360><c> last</c><00:12:54.660><c> few</c><00:12:54.959><c> last</c><00:12:55.380><c> six</c><00:12:55.620><c> to</c><00:12:55.800><c> eight</c><00:12:55.980><c> months</c>

00:12:56.269 --> 00:12:56.279 align:start position:0%
months last few last six to eight months
 

00:12:56.279 --> 00:12:58.790 align:start position:0%
months last few last six to eight months
to<00:12:57.060><c> enable</c><00:12:57.360><c> nimbers</c><00:12:57.899><c> to</c><00:12:58.019><c> be</c><00:12:58.139><c> better</c><00:12:58.380><c> suited</c>

00:12:58.790 --> 00:12:58.800 align:start position:0%
to enable nimbers to be better suited
 

00:12:58.800 --> 00:13:01.250 align:start position:0%
to enable nimbers to be better suited
for<00:12:59.160><c> this</c><00:12:59.399><c> large</c><00:12:59.579><c> segment</c><00:13:00.000><c> which</c><00:13:00.899><c> is</c><00:13:01.019><c> the</c><00:13:01.079><c> node</c>

00:13:01.250 --> 00:13:01.260 align:start position:0%
for this large segment which is the node
 

00:13:01.260 --> 00:13:03.829 align:start position:0%
for this large segment which is the node
operator<00:13:01.620><c> segment</c>

00:13:03.829 --> 00:13:03.839 align:start position:0%
operator segment
 

00:13:03.839 --> 00:13:04.670 align:start position:0%
operator segment
um

00:13:04.670 --> 00:13:04.680 align:start position:0%
um
 

00:13:04.680 --> 00:13:06.590 align:start position:0%
um
that<00:13:05.040><c> is</c><00:13:05.160><c> not</c><00:13:05.279><c> it</c><00:13:05.459><c> though</c><00:13:05.940><c> there</c><00:13:06.360><c> are</c><00:13:06.420><c> some</c>

00:13:06.590 --> 00:13:06.600 align:start position:0%
that is not it though there are some
 

00:13:06.600 --> 00:13:08.389 align:start position:0%
that is not it though there are some
Advanced<00:13:06.959><c> features</c><00:13:07.380><c> which</c><00:13:07.680><c> are</c><00:13:07.800><c> which</c><00:13:08.040><c> Nimbus</c>

00:13:08.389 --> 00:13:08.399 align:start position:0%
Advanced features which are which Nimbus
 

00:13:08.399 --> 00:13:09.710 align:start position:0%
Advanced features which are which Nimbus
is<00:13:08.519><c> working</c><00:13:08.700><c> on</c><00:13:08.940><c> some</c><00:13:09.180><c> of</c><00:13:09.300><c> the</c><00:13:09.360><c> validator</c>

00:13:09.710 --> 00:13:09.720 align:start position:0%
is working on some of the validator
 

00:13:09.720 --> 00:13:11.090 align:start position:0%
is working on some of the validator
client<00:13:10.139><c> features</c><00:13:10.560><c> that</c><00:13:10.740><c> are</c><00:13:10.920><c> really</c>

00:13:11.090 --> 00:13:11.100 align:start position:0%
client features that are really
 

00:13:11.100 --> 00:13:14.389 align:start position:0%
client features that are really
interesting<00:13:11.519><c> for</c><00:13:11.820><c> node</c><00:13:12.120><c> operators</c><00:13:13.079><c> and</c><00:13:13.920><c> I'm</c>

00:13:14.389 --> 00:13:14.399 align:start position:0%
interesting for node operators and I'm
 

00:13:14.399 --> 00:13:16.009 align:start position:0%
interesting for node operators and I'm
talking<00:13:14.639><c> about</c><00:13:14.820><c> these</c><00:13:15.240><c> because</c><00:13:15.420><c> these</c><00:13:15.959><c> are</c>

00:13:16.009 --> 00:13:16.019 align:start position:0%
talking about these because these are
 

00:13:16.019 --> 00:13:17.389 align:start position:0%
talking about these because these are
factors<00:13:16.440><c> that</c><00:13:16.620><c> are</c><00:13:16.740><c> important</c><00:13:17.100><c> to</c><00:13:17.160><c> node</c>

00:13:17.389 --> 00:13:17.399 align:start position:0%
factors that are important to node
 

00:13:17.399 --> 00:13:19.430 align:start position:0%
factors that are important to node
operator<00:13:17.700><c> segment</c><00:13:18.120><c> which</c><00:13:18.779><c> need</c><00:13:18.959><c> to</c><00:13:19.079><c> be</c><00:13:19.139><c> taken</c>

00:13:19.430 --> 00:13:19.440 align:start position:0%
operator segment which need to be taken
 

00:13:19.440 --> 00:13:21.170 align:start position:0%
operator segment which need to be taken
into<00:13:19.560><c> account</c><00:13:19.800><c> when</c><00:13:20.339><c> we</c><00:13:20.519><c> think</c><00:13:20.700><c> about</c><00:13:20.820><c> the</c>

00:13:21.170 --> 00:13:21.180 align:start position:0%
into account when we think about the
 

00:13:21.180 --> 00:13:23.810 align:start position:0%
into account when we think about the
future<00:13:21.300><c> client</c><00:13:21.660><c> experience</c><00:13:22.279><c> as</c><00:13:23.279><c> it</c><00:13:23.459><c> evolves</c>

00:13:23.810 --> 00:13:23.820 align:start position:0%
future client experience as it evolves
 

00:13:23.820 --> 00:13:25.490 align:start position:0%
future client experience as it evolves
because<00:13:24.180><c> the</c><00:13:24.480><c> client</c><00:13:24.660><c> is</c><00:13:24.839><c> the</c><00:13:25.019><c> one</c><00:13:25.139><c> client</c>

00:13:25.490 --> 00:13:25.500 align:start position:0%
because the client is the one client
 

00:13:25.500 --> 00:13:28.250 align:start position:0%
because the client is the one client
that<00:13:26.100><c> is</c><00:13:26.279><c> used</c><00:13:26.399><c> by</c><00:13:26.639><c> both</c><00:13:26.820><c> individual</c><00:13:27.360><c> users</c>

00:13:28.250 --> 00:13:28.260 align:start position:0%
that is used by both individual users
 

00:13:28.260 --> 00:13:30.530 align:start position:0%
that is used by both individual users
and<00:13:28.980><c> the</c><00:13:29.160><c> node</c><00:13:29.339><c> operators</c><00:13:29.760><c> at</c><00:13:30.060><c> a</c><00:13:30.180><c> professional</c>

00:13:30.530 --> 00:13:30.540 align:start position:0%
and the node operators at a professional
 

00:13:30.540 --> 00:13:31.550 align:start position:0%
and the node operators at a professional
level

00:13:31.550 --> 00:13:31.560 align:start position:0%
level
 

00:13:31.560 --> 00:13:32.930 align:start position:0%
level
so

00:13:32.930 --> 00:13:32.940 align:start position:0%
so
 

00:13:32.940 --> 00:13:35.389 align:start position:0%
so
the<00:13:33.779><c> advanced</c><00:13:34.320><c> validator</c><00:13:34.800><c> features</c><00:13:35.220><c> are</c>

00:13:35.389 --> 00:13:35.399 align:start position:0%
the advanced validator features are
 

00:13:35.399 --> 00:13:37.190 align:start position:0%
the advanced validator features are
things<00:13:35.639><c> like</c><00:13:35.940><c> they</c><00:13:36.240><c> are</c><00:13:36.420><c> inspired</c><00:13:36.779><c> by</c><00:13:36.959><c> the</c>

00:13:37.190 --> 00:13:37.200 align:start position:0%
things like they are inspired by the
 

00:13:37.200 --> 00:13:39.650 align:start position:0%
things like they are inspired by the
secret<00:13:37.519><c> shared</c><00:13:38.519><c> secret</c><00:13:38.639><c> validator</c><00:13:39.240><c> research</c>

00:13:39.650 --> 00:13:39.660 align:start position:0%
secret shared secret validator research
 

00:13:39.660 --> 00:13:42.710 align:start position:0%
secret shared secret validator research
and<00:13:40.380><c> IT</c><00:13:41.100><c> addresses</c><00:13:41.519><c> risks</c><00:13:42.000><c> like</c><00:13:42.240><c> Rogue</c>

00:13:42.710 --> 00:13:42.720 align:start position:0%
and IT addresses risks like Rogue
 

00:13:42.720 --> 00:13:45.829 align:start position:0%
and IT addresses risks like Rogue
employees<00:13:43.399><c> malicious</c><00:13:44.399><c> actors</c><00:13:45.360><c> or</c>

00:13:45.829 --> 00:13:45.839 align:start position:0%
employees malicious actors or
 

00:13:45.839 --> 00:13:47.509 align:start position:0%
employees malicious actors or
infrastructure<00:13:46.440><c> failures</c>

00:13:47.509 --> 00:13:47.519 align:start position:0%
infrastructure failures
 

00:13:47.519 --> 00:13:51.110 align:start position:0%
infrastructure failures
even<00:13:48.120><c> in</c><00:13:48.420><c> the</c><00:13:48.540><c> current</c><00:13:48.660><c> setup</c><00:13:49.139><c> where</c><00:13:49.860><c> you</c><00:13:50.160><c> have</c>

00:13:51.110 --> 00:13:51.120 align:start position:0%
even in the current setup where you have
 

00:13:51.120 --> 00:13:53.410 align:start position:0%
even in the current setup where you have
validators<00:13:52.019><c> running</c><00:13:52.320><c> through</c><00:13:52.560><c> web</c>

00:13:53.410 --> 00:13:53.420 align:start position:0%
validators running through web
 

00:13:53.420 --> 00:13:56.449 align:start position:0%
validators running through web
remote<00:13:54.420><c> signers</c><00:13:55.100><c> infrastructure</c><00:13:56.100><c> failures</c>

00:13:56.449 --> 00:13:56.459 align:start position:0%
remote signers infrastructure failures
 

00:13:56.459 --> 00:13:58.190 align:start position:0%
remote signers infrastructure failures
can<00:13:56.700><c> still</c><00:13:56.880><c> bring</c><00:13:57.120><c> down</c><00:13:57.300><c> the</c><00:13:57.540><c> operation</c><00:13:57.839><c> in</c><00:13:58.079><c> a</c>

00:13:58.190 --> 00:13:58.200 align:start position:0%
can still bring down the operation in a
 

00:13:58.200 --> 00:14:01.910 align:start position:0%
can still bring down the operation in a
way<00:13:58.320><c> so</c><00:13:59.120><c> that</c><00:14:00.120><c> is</c><00:14:00.240><c> one</c><00:14:00.540><c> area</c><00:14:01.139><c> of</c><00:14:01.380><c> or</c><00:14:01.620><c> risk</c>

00:14:01.910 --> 00:14:01.920 align:start position:0%
way so that is one area of or risk
 

00:14:01.920 --> 00:14:03.650 align:start position:0%
way so that is one area of or risk
potential<00:14:02.279><c> risk</c><00:14:02.639><c> that</c><00:14:02.820><c> the</c><00:14:03.180><c> the</c><00:14:03.360><c> node</c>

00:14:03.650 --> 00:14:03.660 align:start position:0%
potential risk that the the node
 

00:14:03.660 --> 00:14:05.569 align:start position:0%
potential risk that the the node
operators<00:14:04.079><c> are</c><00:14:04.260><c> still</c><00:14:04.440><c> exposed</c><00:14:04.860><c> to</c>

00:14:05.569 --> 00:14:05.579 align:start position:0%
operators are still exposed to
 

00:14:05.579 --> 00:14:07.430 align:start position:0%
operators are still exposed to
there's<00:14:06.360><c> always</c><00:14:06.540><c> the</c><00:14:06.779><c> risk</c><00:14:07.019><c> of</c><00:14:07.139><c> Rogue</c>

00:14:07.430 --> 00:14:07.440 align:start position:0%
there's always the risk of Rogue
 

00:14:07.440 --> 00:14:09.230 align:start position:0%
there's always the risk of Rogue
employees<00:14:07.860><c> because</c><00:14:08.100><c> if</c><00:14:08.459><c> an</c><00:14:08.639><c> employee</c><00:14:09.000><c> has</c>

00:14:09.230 --> 00:14:09.240 align:start position:0%
employees because if an employee has
 

00:14:09.240 --> 00:14:11.810 align:start position:0%
employees because if an employee has
access<00:14:09.420><c> to</c><00:14:09.660><c> all</c><00:14:09.839><c> the</c><00:14:10.079><c> key</c><00:14:10.279><c> keys</c><00:14:11.279><c> they</c><00:14:11.639><c> can</c>

00:14:11.810 --> 00:14:11.820 align:start position:0%
access to all the key keys they can
 

00:14:11.820 --> 00:14:13.310 align:start position:0%
access to all the key keys they can
actually<00:14:12.060><c> you</c><00:14:12.420><c> know</c><00:14:12.540><c> hold</c><00:14:12.779><c> the</c><00:14:12.959><c> company</c><00:14:13.079><c> to</c>

00:14:13.310 --> 00:14:13.320 align:start position:0%
actually you know hold the company to
 

00:14:13.320 --> 00:14:15.410 align:start position:0%
actually you know hold the company to
Ransom<00:14:13.740><c> right</c><00:14:14.220><c> and</c><00:14:14.760><c> you</c><00:14:14.880><c> don't</c><00:14:15.060><c> want</c><00:14:15.240><c> that</c>

00:14:15.410 --> 00:14:15.420 align:start position:0%
Ransom right and you don't want that
 

00:14:15.420 --> 00:14:17.569 align:start position:0%
Ransom right and you don't want that
when<00:14:15.540><c> you're</c><00:14:15.779><c> running</c><00:14:16.019><c> 7000</c><00:14:16.500><c> validators</c><00:14:17.040><c> so</c>

00:14:17.569 --> 00:14:17.579 align:start position:0%
when you're running 7000 validators so
 

00:14:17.579 --> 00:14:18.889 align:start position:0%
when you're running 7000 validators so
these<00:14:17.820><c> are</c><00:14:17.880><c> some</c><00:14:18.060><c> of</c><00:14:18.120><c> the</c><00:14:18.240><c> factors</c><00:14:18.540><c> that</c><00:14:18.779><c> are</c>

00:14:18.889 --> 00:14:18.899 align:start position:0%
these are some of the factors that are
 

00:14:18.899 --> 00:14:22.670 align:start position:0%
these are some of the factors that are
really<00:14:19.079><c> important</c><00:14:19.760><c> for</c><00:14:20.760><c> for</c><00:14:21.120><c> to</c><00:14:22.079><c> address</c><00:14:22.260><c> from</c>

00:14:22.670 --> 00:14:22.680 align:start position:0%
really important for for to address from
 

00:14:22.680 --> 00:14:24.769 align:start position:0%
really important for for to address from
a<00:14:22.800><c> risk</c><00:14:23.040><c> management</c><00:14:23.160><c> point</c><00:14:23.579><c> of</c><00:14:23.760><c> view</c>

00:14:24.769 --> 00:14:24.779 align:start position:0%
a risk management point of view
 

00:14:24.779 --> 00:14:27.530 align:start position:0%
a risk management point of view
there<00:14:25.380><c> are</c><00:14:25.500><c> some</c><00:14:25.680><c> features</c><00:14:26.040><c> that</c><00:14:26.519><c> Nimbus</c><00:14:27.360><c> is</c>

00:14:27.530 --> 00:14:27.540 align:start position:0%
there are some features that Nimbus is
 

00:14:27.540 --> 00:14:29.930 align:start position:0%
there are some features that Nimbus is
working<00:14:27.779><c> on</c><00:14:28.019><c> in</c><00:14:28.620><c> terms</c><00:14:28.920><c> of</c><00:14:29.040><c> what</c><00:14:29.459><c> the</c><00:14:29.579><c> advanced</c>

00:14:29.930 --> 00:14:29.940 align:start position:0%
working on in terms of what the advanced
 

00:14:29.940 --> 00:14:31.250 align:start position:0%
working on in terms of what the advanced
validator<00:14:30.300><c> feature</c><00:14:30.720><c> set</c><00:14:30.779><c> would</c><00:14:31.019><c> look</c><00:14:31.139><c> like</c>

00:14:31.250 --> 00:14:31.260 align:start position:0%
validator feature set would look like
 

00:14:31.260 --> 00:14:33.170 align:start position:0%
validator feature set would look like
that<00:14:31.620><c> would</c><00:14:31.740><c> address</c><00:14:31.920><c> some</c><00:14:32.220><c> of</c><00:14:32.339><c> these</c><00:14:32.639><c> some</c><00:14:33.000><c> of</c>

00:14:33.170 --> 00:14:33.180 align:start position:0%
that would address some of these some of
 

00:14:33.180 --> 00:14:35.870 align:start position:0%
that would address some of these some of
these<00:14:33.300><c> issues</c><00:14:33.740><c> and</c><00:14:34.740><c> part</c><00:14:35.220><c> of</c><00:14:35.339><c> this</c><00:14:35.519><c> is</c><00:14:35.700><c> about</c>

00:14:35.870 --> 00:14:35.880 align:start position:0%
these issues and part of this is about
 

00:14:35.880 --> 00:14:37.790 align:start position:0%
these issues and part of this is about
splitting<00:14:36.480><c> the</c><00:14:36.839><c> sysadmin</c><00:14:37.500><c> teams</c><00:14:37.680><c> into</c>

00:14:37.790 --> 00:14:37.800 align:start position:0%
splitting the sysadmin teams into
 

00:14:37.800 --> 00:14:40.490 align:start position:0%
splitting the sysadmin teams into
multiple<00:14:38.279><c> teams</c><00:14:39.120><c> that</c><00:14:39.300><c> have</c><00:14:39.480><c> only</c><00:14:39.720><c> access</c><00:14:40.139><c> to</c>

00:14:40.490 --> 00:14:40.500 align:start position:0%
multiple teams that have only access to
 

00:14:40.500 --> 00:14:42.710 align:start position:0%
multiple teams that have only access to
part<00:14:40.860><c> of</c><00:14:41.100><c> the</c><00:14:41.339><c> keys</c><00:14:41.639><c> like</c><00:14:41.880><c> no</c><00:14:42.120><c> but</c><00:14:42.300><c> no</c><00:14:42.540><c> one</c>

00:14:42.710 --> 00:14:42.720 align:start position:0%
part of the keys like no but no one
 

00:14:42.720 --> 00:14:44.449 align:start position:0%
part of the keys like no but no one
person<00:14:42.899><c> has</c><00:14:43.199><c> access</c><00:14:43.380><c> to</c><00:14:43.620><c> all</c><00:14:43.800><c> of</c><00:14:43.980><c> the</c><00:14:44.220><c> the</c>

00:14:44.449 --> 00:14:44.459 align:start position:0%
person has access to all of the the
 

00:14:44.459 --> 00:14:46.189 align:start position:0%
person has access to all of the the
entire<00:14:44.760><c> key</c><00:14:45.000><c> set</c><00:14:45.180><c> I</c><00:14:45.360><c> suppose</c>

00:14:46.189 --> 00:14:46.199 align:start position:0%
entire key set I suppose
 

00:14:46.199 --> 00:14:48.590 align:start position:0%
entire key set I suppose
and<00:14:46.980><c> distributing</c><00:14:47.579><c> that</c><00:14:47.820><c> the</c><00:14:48.120><c> portions</c><00:14:48.420><c> of</c>

00:14:48.590 --> 00:14:48.600 align:start position:0%
and distributing that the portions of
 

00:14:48.600 --> 00:14:51.610 align:start position:0%
and distributing that the portions of
those<00:14:48.779><c> keys</c><00:14:49.199><c> across</c><00:14:49.920><c> several</c><00:14:50.279><c> different</c>

00:14:51.610 --> 00:14:51.620 align:start position:0%
those keys across several different
 

00:14:51.620 --> 00:14:54.290 align:start position:0%
those keys across several different
infrastructure<00:14:52.620><c> providers</c><00:14:53.160><c> potentially</c>

00:14:54.290 --> 00:14:54.300 align:start position:0%
infrastructure providers potentially
 

00:14:54.300 --> 00:14:57.650 align:start position:0%
infrastructure providers potentially
the<00:14:54.779><c> challenge</c><00:14:55.019><c> also</c><00:14:55.500><c> here</c><00:14:55.740><c> is</c><00:14:56.160><c> that</c><00:14:56.519><c> this</c><00:14:57.420><c> is</c>

00:14:57.650 --> 00:14:57.660 align:start position:0%
the challenge also here is that this is
 

00:14:57.660 --> 00:14:59.810 align:start position:0%
the challenge also here is that this is
extremely<00:14:58.139><c> complex</c><00:14:58.560><c> I</c><00:14:59.160><c> mean</c><00:14:59.279><c> node</c><00:14:59.519><c> operations</c>

00:14:59.810 --> 00:14:59.820 align:start position:0%
extremely complex I mean node operations
 

00:14:59.820 --> 00:15:01.550 align:start position:0%
extremely complex I mean node operations
itself<00:15:00.240><c> is</c><00:15:00.420><c> complex</c><00:15:00.720><c> and</c><00:15:00.959><c> then</c><00:15:01.079><c> on</c><00:15:01.260><c> top</c><00:15:01.380><c> of</c>

00:15:01.550 --> 00:15:01.560 align:start position:0%
itself is complex and then on top of
 

00:15:01.560 --> 00:15:02.810 align:start position:0%
itself is complex and then on top of
that<00:15:01.680><c> we</c><00:15:01.920><c> are</c><00:15:02.100><c> we</c><00:15:02.279><c> are</c><00:15:02.399><c> overlaying</c>

00:15:02.810 --> 00:15:02.820 align:start position:0%
that we are we are overlaying
 

00:15:02.820 --> 00:15:04.250 align:start position:0%
that we are we are overlaying
organizational<00:15:03.300><c> changes</c><00:15:03.779><c> that</c><00:15:03.959><c> you</c><00:15:04.079><c> need</c><00:15:04.139><c> to</c>

00:15:04.250 --> 00:15:04.260 align:start position:0%
organizational changes that you need to
 

00:15:04.260 --> 00:15:05.210 align:start position:0%
organizational changes that you need to
bring<00:15:04.380><c> about</c>

00:15:05.210 --> 00:15:05.220 align:start position:0%
bring about
 

00:15:05.220 --> 00:15:07.430 align:start position:0%
bring about
so<00:15:05.940><c> this</c><00:15:06.420><c> creates</c><00:15:06.720><c> an</c><00:15:06.839><c> additional</c><00:15:07.079><c> layer</c><00:15:07.380><c> of</c>

00:15:07.430 --> 00:15:07.440 align:start position:0%
so this creates an additional layer of
 

00:15:07.440 --> 00:15:09.769 align:start position:0%
so this creates an additional layer of
complexity<00:15:07.920><c> but</c><00:15:08.699><c> it's</c><00:15:08.820><c> a</c><00:15:09.000><c> trade-off</c><00:15:09.360><c> right</c>

00:15:09.769 --> 00:15:09.779 align:start position:0%
complexity but it's a trade-off right
 

00:15:09.779 --> 00:15:11.990 align:start position:0%
complexity but it's a trade-off right
it's<00:15:10.079><c> a</c><00:15:10.260><c> trade-off</c><00:15:10.620><c> around</c><00:15:10.860><c> do</c><00:15:11.399><c> we</c><00:15:11.579><c> want</c><00:15:11.820><c> to</c>

00:15:11.990 --> 00:15:12.000 align:start position:0%
it's a trade-off around do we want to
 

00:15:12.000 --> 00:15:14.210 align:start position:0%
it's a trade-off around do we want to
actively<00:15:12.300><c> manage</c><00:15:12.600><c> that</c><00:15:12.779><c> risk</c><00:15:13.139><c> versus</c>

00:15:14.210 --> 00:15:14.220 align:start position:0%
actively manage that risk versus
 

00:15:14.220 --> 00:15:16.610 align:start position:0%
actively manage that risk versus
sort<00:15:14.699><c> of</c><00:15:14.820><c> live</c><00:15:15.000><c> with</c><00:15:15.180><c> this</c><00:15:15.360><c> risk</c><00:15:15.720><c> as</c><00:15:16.320><c> a</c><00:15:16.440><c> node</c>

00:15:16.610 --> 00:15:16.620 align:start position:0%
sort of live with this risk as a node
 

00:15:16.620 --> 00:15:17.509 align:start position:0%
sort of live with this risk as a node
operator

00:15:17.509 --> 00:15:17.519 align:start position:0%
operator
 

00:15:17.519 --> 00:15:20.569 align:start position:0%
operator
and<00:15:18.180><c> in</c><00:15:19.019><c> this</c><00:15:19.139><c> regard</c><00:15:19.560><c> the</c><00:15:19.860><c> there</c><00:15:20.220><c> are</c><00:15:20.399><c> a</c><00:15:20.459><c> few</c>

00:15:20.569 --> 00:15:20.579 align:start position:0%
and in this regard the there are a few
 

00:15:20.579 --> 00:15:22.250 align:start position:0%
and in this regard the there are a few
possible<00:15:20.880><c> solutions</c><00:15:21.360><c> that</c><00:15:21.660><c> Nimbus</c><00:15:22.079><c> is</c>

00:15:22.250 --> 00:15:22.260 align:start position:0%
possible solutions that Nimbus is
 

00:15:22.260 --> 00:15:24.829 align:start position:0%
possible solutions that Nimbus is
exploring<00:15:22.680><c> including</c><00:15:23.220><c> kind</c><00:15:24.120><c> of</c><00:15:24.240><c> a</c><00:15:24.360><c> new</c><00:15:24.540><c> remote</c>

00:15:24.829 --> 00:15:24.839 align:start position:0%
exploring including kind of a new remote
 

00:15:24.839 --> 00:15:26.750 align:start position:0%
exploring including kind of a new remote
key<00:15:25.139><c> store</c><00:15:25.380><c> where</c><00:15:25.740><c> you</c><00:15:25.980><c> know</c><00:15:26.100><c> each</c><00:15:26.339><c> item</c><00:15:26.579><c> is</c>

00:15:26.750 --> 00:15:26.760 align:start position:0%
key store where you know each item is
 

00:15:26.760 --> 00:15:29.210 align:start position:0%
key store where you know each item is
sent<00:15:26.940><c> to</c><00:15:27.240><c> multiple</c><00:15:28.019><c> web3</c><00:15:28.380><c> signer</c><00:15:28.860><c> instances</c>

00:15:29.210 --> 00:15:29.220 align:start position:0%
sent to multiple web3 signer instances
 

00:15:29.220 --> 00:15:31.310 align:start position:0%
sent to multiple web3 signer instances
instead<00:15:29.699><c> of</c><00:15:29.760><c> just</c><00:15:29.880><c> one</c><00:15:30.120><c> so</c><00:15:30.839><c> there</c><00:15:30.959><c> are</c><00:15:31.079><c> some</c><00:15:31.260><c> of</c>

00:15:31.310 --> 00:15:31.320 align:start position:0%
instead of just one so there are some of
 

00:15:31.320 --> 00:15:32.810 align:start position:0%
instead of just one so there are some of
these<00:15:31.560><c> things</c><00:15:31.680><c> that</c><00:15:31.920><c> Nimbus</c><00:15:32.279><c> is</c><00:15:32.459><c> exploring</c>

00:15:32.810 --> 00:15:32.820 align:start position:0%
these things that Nimbus is exploring
 

00:15:32.820 --> 00:15:36.470 align:start position:0%
these things that Nimbus is exploring
which<00:15:33.060><c> will</c><00:15:33.300><c> add</c><00:15:34.199><c> much</c><00:15:35.040><c> more</c><00:15:35.220><c> capability</c>

00:15:36.470 --> 00:15:36.480 align:start position:0%
which will add much more capability
 

00:15:36.480 --> 00:15:38.629 align:start position:0%
which will add much more capability
to<00:15:36.959><c> the</c><00:15:37.139><c> validator</c><00:15:37.500><c> client</c><00:15:37.920><c> which</c><00:15:38.220><c> is</c><00:15:38.339><c> what</c>

00:15:38.629 --> 00:15:38.639 align:start position:0%
to the validator client which is what
 

00:15:38.639 --> 00:15:40.550 align:start position:0%
to the validator client which is what
the<00:15:39.000><c> node</c><00:15:39.480><c> operators</c><00:15:39.839><c> have</c><00:15:40.019><c> been</c><00:15:40.199><c> looking</c><00:15:40.320><c> for</c>

00:15:40.550 --> 00:15:40.560 align:start position:0%
the node operators have been looking for
 

00:15:40.560 --> 00:15:43.129 align:start position:0%
the node operators have been looking for
for<00:15:40.920><c> a</c><00:15:41.100><c> long</c><00:15:41.220><c> time</c>

00:15:43.129 --> 00:15:43.139 align:start position:0%
for a long time
 

00:15:43.139 --> 00:15:45.410 align:start position:0%
for a long time
all<00:15:43.500><c> you</c><00:15:43.980><c> can</c><00:15:44.100><c> see</c><00:15:44.279><c> where</c><00:15:44.639><c> the</c><00:15:45.000><c> expectations</c>

00:15:45.410 --> 00:15:45.420 align:start position:0%
all you can see where the expectations
 

00:15:45.420 --> 00:15:46.970 align:start position:0%
all you can see where the expectations
of<00:15:45.660><c> node</c><00:15:45.899><c> operators</c>

00:15:46.970 --> 00:15:46.980 align:start position:0%
of node operators
 

00:15:46.980 --> 00:15:48.530 align:start position:0%
of node operators
have<00:15:47.339><c> the</c><00:15:47.519><c> expectations</c><00:15:47.820><c> of</c><00:15:47.940><c> node</c><00:15:48.240><c> operators</c>

00:15:48.530 --> 00:15:48.540 align:start position:0%
have the expectations of node operators
 

00:15:48.540 --> 00:15:50.210 align:start position:0%
have the expectations of node operators
are<00:15:48.660><c> changing</c><00:15:48.959><c> with</c><00:15:49.139><c> regards</c><00:15:49.560><c> to</c><00:15:49.620><c> the</c><00:15:49.920><c> use</c><00:15:50.040><c> of</c>

00:15:50.210 --> 00:15:50.220 align:start position:0%
are changing with regards to the use of
 

00:15:50.220 --> 00:15:53.050 align:start position:0%
are changing with regards to the use of
the<00:15:50.339><c> client</c><00:15:50.579><c> right</c><00:15:51.060><c> and</c><00:15:51.660><c> how</c><00:15:52.079><c> they</c><00:15:52.320><c> see</c>

00:15:53.050 --> 00:15:53.060 align:start position:0%
the client right and how they see
 

00:15:53.060 --> 00:15:55.370 align:start position:0%
the client right and how they see
the<00:15:54.060><c> evolution</c><00:15:54.300><c> of</c><00:15:54.600><c> the</c><00:15:54.720><c> client</c><00:15:54.899><c> experience</c>

00:15:55.370 --> 00:15:55.380 align:start position:0%
the evolution of the client experience
 

00:15:55.380 --> 00:15:57.769 align:start position:0%
the evolution of the client experience
now<00:15:55.680><c> this</c><00:15:55.980><c> is</c><00:15:56.160><c> definitely</c><00:15:56.519><c> not</c><00:15:56.880><c> what</c>

00:15:57.769 --> 00:15:57.779 align:start position:0%
now this is definitely not what
 

00:15:57.779 --> 00:15:59.509 align:start position:0%
now this is definitely not what
individual<00:15:58.260><c> customers</c><00:15:58.680><c> want</c><00:15:58.860><c> right</c><00:15:59.100><c> like</c><00:15:59.339><c> as</c>

00:15:59.509 --> 00:15:59.519 align:start position:0%
individual customers want right like as
 

00:15:59.519 --> 00:16:00.829 align:start position:0%
individual customers want right like as
an<00:15:59.699><c> individual</c><00:16:00.060><c> if</c><00:16:00.240><c> you</c><00:16:00.360><c> want</c><00:16:00.480><c> to</c><00:16:00.600><c> run</c><00:16:00.660><c> the</c>

00:16:00.829 --> 00:16:00.839 align:start position:0%
an individual if you want to run the
 

00:16:00.839 --> 00:16:03.530 align:start position:0%
an individual if you want to run the
node<00:16:01.079><c> you're</c><00:16:01.800><c> looking</c><00:16:01.980><c> for</c><00:16:02.279><c> Simplicity</c><00:16:02.760><c> and</c>

00:16:03.530 --> 00:16:03.540 align:start position:0%
node you're looking for Simplicity and
 

00:16:03.540 --> 00:16:07.250 align:start position:0%
node you're looking for Simplicity and
so<00:16:03.839><c> it's</c><00:16:04.560><c> almost</c><00:16:04.800><c> like</c><00:16:05.279><c> pulling</c><00:16:05.880><c> the</c>

00:16:07.250 --> 00:16:07.260 align:start position:0%
so it's almost like pulling the
 

00:16:07.260 --> 00:16:09.650 align:start position:0%
so it's almost like pulling the
um<00:16:07.740><c> pulling</c><00:16:08.459><c> the</c><00:16:08.639><c> direction</c><00:16:08.880><c> in</c><00:16:09.240><c> which</c><00:16:09.420><c> the</c>

00:16:09.650 --> 00:16:09.660 align:start position:0%
um pulling the direction in which the
 

00:16:09.660 --> 00:16:11.269 align:start position:0%
um pulling the direction in which the
client<00:16:09.899><c> should</c><00:16:10.440><c> evolve</c><00:16:10.860><c> in</c><00:16:11.100><c> a</c><00:16:11.160><c> different</c>

00:16:11.269 --> 00:16:11.279 align:start position:0%
client should evolve in a different
 

00:16:11.279 --> 00:16:12.829 align:start position:0%
client should evolve in a different
direction<00:16:11.519><c> totally</c><00:16:12.060><c> right</c><00:16:12.360><c> compared</c><00:16:12.779><c> to</c>

00:16:12.829 --> 00:16:12.839 align:start position:0%
direction totally right compared to
 

00:16:12.839 --> 00:16:14.810 align:start position:0%
direction totally right compared to
where<00:16:13.079><c> the</c><00:16:13.199><c> node</c><00:16:13.320><c> operators</c><00:16:13.740><c> are</c><00:16:13.920><c> seeking</c><00:16:14.339><c> for</c>

00:16:14.810 --> 00:16:14.820 align:start position:0%
where the node operators are seeking for
 

00:16:14.820 --> 00:16:18.110 align:start position:0%
where the node operators are seeking for
the<00:16:14.940><c> client</c><00:16:15.180><c> to</c><00:16:15.360><c> evolve</c>

00:16:18.110 --> 00:16:18.120 align:start position:0%
 
 

00:16:18.120 --> 00:16:19.730 align:start position:0%
 
question<00:16:18.360><c> before</c><00:16:18.720><c> I</c><00:16:19.019><c> I</c><00:16:19.199><c> can't</c><00:16:19.440><c> go</c><00:16:19.620><c> back</c>

00:16:19.730 --> 00:16:19.740 align:start position:0%
question before I I can't go back
 

00:16:19.740 --> 00:16:21.650 align:start position:0%
question before I I can't go back
unfortunately<00:16:20.220><c> but</c><00:16:20.519><c> I</c><00:16:20.699><c> I</c><00:16:20.880><c> just</c><00:16:21.120><c> quick</c><00:16:21.240><c> show</c><00:16:21.480><c> of</c>

00:16:21.650 --> 00:16:21.660 align:start position:0%
unfortunately but I I just quick show of
 

00:16:21.660 --> 00:16:23.210 align:start position:0%
unfortunately but I I just quick show of
hands<00:16:22.079><c> for</c><00:16:22.320><c> those</c><00:16:22.500><c> who</c><00:16:22.620><c> are</c><00:16:22.740><c> running</c><00:16:22.860><c> a</c><00:16:23.040><c> note</c>

00:16:23.210 --> 00:16:23.220 align:start position:0%
hands for those who are running a note
 

00:16:23.220 --> 00:16:25.129 align:start position:0%
hands for those who are running a note
from<00:16:23.459><c> their</c><00:16:23.579><c> own</c><00:16:23.760><c> homes</c>

00:16:25.129 --> 00:16:25.139 align:start position:0%
from their own homes
 

00:16:25.139 --> 00:16:26.990 align:start position:0%
from their own homes
wow<00:16:25.620><c> that's</c><00:16:25.860><c> that's</c><00:16:26.160><c> definitely</c><00:16:26.579><c> more</c><00:16:26.820><c> than</c>

00:16:26.990 --> 00:16:27.000 align:start position:0%
wow that's that's definitely more than
 

00:16:27.000 --> 00:16:29.030 align:start position:0%
wow that's that's definitely more than
people<00:16:27.240><c> who</c><00:16:27.420><c> are</c><00:16:27.540><c> staking</c><00:16:27.779><c> through</c><00:16:28.079><c> liquids</c>

00:16:29.030 --> 00:16:29.040 align:start position:0%
people who are staking through liquids
 

00:16:29.040 --> 00:16:30.949 align:start position:0%
people who are staking through liquids
taking<00:16:29.220><c> protocols</c><00:16:29.820><c> or</c><00:16:30.060><c> or</c><00:16:30.240><c> exchanges</c><00:16:30.839><c> so</c>

00:16:30.949 --> 00:16:30.959 align:start position:0%
taking protocols or or exchanges so
 

00:16:30.959 --> 00:16:33.110 align:start position:0%
taking protocols or or exchanges so
that's<00:16:31.139><c> that's</c><00:16:31.380><c> really</c><00:16:31.620><c> good</c><00:16:31.860><c> to</c><00:16:32.040><c> see</c>

00:16:33.110 --> 00:16:33.120 align:start position:0%
that's that's really good to see
 

00:16:33.120 --> 00:16:34.490 align:start position:0%
that's that's really good to see
um

00:16:34.490 --> 00:16:34.500 align:start position:0%
um
 

00:16:34.500 --> 00:16:37.550 align:start position:0%
um
Hester<00:16:35.399><c> and</c><00:16:36.060><c> Kiel</c><00:16:36.540><c> from</c><00:16:36.779><c> the</c><00:16:36.839><c> team</c><00:16:37.019><c> ran</c><00:16:37.380><c> some</c>

00:16:37.550 --> 00:16:37.560 align:start position:0%
Hester and Kiel from the team ran some
 

00:16:37.560 --> 00:16:39.590 align:start position:0%
Hester and Kiel from the team ran some
research<00:16:37.860><c> very</c><00:16:38.100><c> recently</c><00:16:38.519><c> and</c><00:16:39.120><c> the</c><00:16:39.300><c> feedback</c>

00:16:39.590 --> 00:16:39.600 align:start position:0%
research very recently and the feedback
 

00:16:39.600 --> 00:16:43.189 align:start position:0%
research very recently and the feedback
is<00:16:40.139><c> quite</c><00:16:40.380><c> interesting</c><00:16:40.800><c> from</c><00:16:41.160><c> individuals</c>

00:16:43.189 --> 00:16:43.199 align:start position:0%
is quite interesting from individuals
 

00:16:43.199 --> 00:16:44.930 align:start position:0%
is quite interesting from individuals
there's<00:16:43.680><c> a</c><00:16:43.920><c> lot</c><00:16:43.980><c> of</c><00:16:44.100><c> potential</c><00:16:44.459><c> there's</c><00:16:44.639><c> a</c><00:16:44.820><c> lot</c>

00:16:44.930 --> 00:16:44.940 align:start position:0%
there's a lot of potential there's a lot
 

00:16:44.940 --> 00:16:47.449 align:start position:0%
there's a lot of potential there's a lot
of<00:16:45.000><c> interest</c><00:16:45.180><c> but</c><00:16:45.600><c> they're</c><00:16:45.779><c> all</c><00:16:45.959><c> held</c><00:16:46.320><c> back</c><00:16:46.440><c> by</c>

00:16:47.449 --> 00:16:47.459 align:start position:0%
of interest but they're all held back by
 

00:16:47.459 --> 00:16:50.030 align:start position:0%
of interest but they're all held back by
a<00:16:47.880><c> number</c><00:16:48.120><c> of</c><00:16:48.300><c> challenges</c><00:16:49.040><c> particularly</c>

00:16:50.030 --> 00:16:50.040 align:start position:0%
a number of challenges particularly
 

00:16:50.040 --> 00:16:50.990 align:start position:0%
a number of challenges particularly
around

00:16:50.990 --> 00:16:51.000 align:start position:0%
around
 

00:16:51.000 --> 00:16:53.150 align:start position:0%
around
lack<00:16:51.660><c> of</c><00:16:51.779><c> easy</c><00:16:52.079><c> access</c><00:16:52.380><c> to</c><00:16:52.680><c> documentation</c>

00:16:53.150 --> 00:16:53.160 align:start position:0%
lack of easy access to documentation
 

00:16:53.160 --> 00:16:55.629 align:start position:0%
lack of easy access to documentation
lack<00:16:53.639><c> of</c><00:16:53.820><c> you</c><00:16:54.120><c> know</c><00:16:54.180><c> uniform</c><00:16:54.839><c> documentation</c>

00:16:55.629 --> 00:16:55.639 align:start position:0%
lack of you know uniform documentation
 

00:16:55.639 --> 00:16:57.889 align:start position:0%
lack of you know uniform documentation
multiple<00:16:56.639><c> clients</c><00:16:57.000><c> have</c><00:16:57.180><c> multiple</c><00:16:57.540><c> guides</c>

00:16:57.889 --> 00:16:57.899 align:start position:0%
multiple clients have multiple guides
 

00:16:57.899 --> 00:16:59.509 align:start position:0%
multiple clients have multiple guides
you<00:16:58.139><c> need</c><00:16:58.320><c> to</c><00:16:58.440><c> shuffle</c><00:16:58.620><c> across</c><00:16:59.100><c> these</c><00:16:59.399><c> things</c>

00:16:59.509 --> 00:16:59.519 align:start position:0%
you need to shuffle across these things
 

00:16:59.519 --> 00:17:02.150 align:start position:0%
you need to shuffle across these things
it<00:17:00.360><c> is</c><00:17:00.480><c> not</c><00:17:00.600><c> easy</c><00:17:00.839><c> multiple</c><00:17:01.380><c> Discord</c><00:17:01.740><c> channels</c>

00:17:02.150 --> 00:17:02.160 align:start position:0%
it is not easy multiple Discord channels
 

00:17:02.160 --> 00:17:03.290 align:start position:0%
it is not easy multiple Discord channels
for<00:17:02.399><c> example</c>

00:17:03.290 --> 00:17:03.300 align:start position:0%
for example
 

00:17:03.300 --> 00:17:04.730 align:start position:0%
for example
so

00:17:04.730 --> 00:17:04.740 align:start position:0%
so
 

00:17:04.740 --> 00:17:06.710 align:start position:0%
so
there<00:17:05.220><c> are</c><00:17:05.339><c> a</c><00:17:05.459><c> few</c><00:17:05.579><c> requests</c><00:17:06.059><c> that</c><00:17:06.240><c> came</c><00:17:06.540><c> out</c>

00:17:06.710 --> 00:17:06.720 align:start position:0%
there are a few requests that came out
 

00:17:06.720 --> 00:17:09.530 align:start position:0%
there are a few requests that came out
when<00:17:07.199><c> when</c><00:17:07.679><c> there</c><00:17:07.980><c> are</c><00:17:08.220><c> in</c><00:17:08.339><c> this</c><00:17:08.540><c> this</c>

00:17:09.530 --> 00:17:09.540 align:start position:0%
when when there are in this this
 

00:17:09.540 --> 00:17:11.510 align:start position:0%
when when there are in this this
research<00:17:10.140><c> right</c><00:17:10.380><c> one</c><00:17:10.679><c> of</c><00:17:10.799><c> the</c><00:17:10.919><c> first</c><00:17:11.040><c> is</c><00:17:11.220><c> is</c>

00:17:11.510 --> 00:17:11.520 align:start position:0%
research right one of the first is is
 

00:17:11.520 --> 00:17:13.490 align:start position:0%
research right one of the first is is
there<00:17:11.760><c> a</c><00:17:11.939><c> no</c><00:17:12.179><c> command</c><00:17:12.600><c> line</c><00:17:12.780><c> option</c><00:17:13.199><c> please</c>

00:17:13.490 --> 00:17:13.500 align:start position:0%
there a no command line option please
 

00:17:13.500 --> 00:17:17.030 align:start position:0%
there a no command line option please
setting<00:17:14.280><c> up</c><00:17:14.459><c> a</c><00:17:15.059><c> valid</c><00:17:15.419><c> data</c><00:17:15.720><c> right</c>

00:17:17.030 --> 00:17:17.040 align:start position:0%
setting up a valid data right
 

00:17:17.040 --> 00:17:18.829 align:start position:0%
setting up a valid data right
believe<00:17:17.640><c> it</c><00:17:17.819><c> or</c><00:17:17.939><c> not</c><00:17:18.059><c> they</c><00:17:18.419><c> all</c><00:17:18.720><c> the</c>

00:17:18.829 --> 00:17:18.839 align:start position:0%
believe it or not they all the
 

00:17:18.839 --> 00:17:20.929 align:start position:0%
believe it or not they all the
validators<00:17:19.199><c> you</c><00:17:19.439><c> set</c><00:17:19.559><c> up</c><00:17:19.740><c> right</c><00:17:19.919><c> now</c><00:17:20.100><c> no</c>

00:17:20.929 --> 00:17:20.939 align:start position:0%
validators you set up right now no
 

00:17:20.939 --> 00:17:22.429 align:start position:0%
validators you set up right now no
matter<00:17:21.059><c> which</c><00:17:21.299><c> client</c><00:17:21.540><c> it</c><00:17:21.720><c> is</c><00:17:21.839><c> it's</c><00:17:22.020><c> all</c><00:17:22.260><c> still</c>

00:17:22.429 --> 00:17:22.439 align:start position:0%
matter which client it is it's all still
 

00:17:22.439 --> 00:17:24.350 align:start position:0%
matter which client it is it's all still
command<00:17:22.799><c> line</c><00:17:22.919><c> right</c><00:17:23.220><c> so</c>

00:17:24.350 --> 00:17:24.360 align:start position:0%
command line right so
 

00:17:24.360 --> 00:17:26.390 align:start position:0%
command line right so
a<00:17:24.900><c> lot</c><00:17:25.020><c> of</c><00:17:25.199><c> users</c><00:17:25.620><c> end</c><00:17:25.799><c> users</c><00:17:26.100><c> who</c><00:17:26.280><c> are</c>

00:17:26.390 --> 00:17:26.400 align:start position:0%
a lot of users end users who are
 

00:17:26.400 --> 00:17:27.710 align:start position:0%
a lot of users end users who are
interested<00:17:26.640><c> in</c><00:17:26.760><c> running</c><00:17:26.880><c> validators</c><00:17:27.480><c> were</c>

00:17:27.710 --> 00:17:27.720 align:start position:0%
interested in running validators were
 

00:17:27.720 --> 00:17:29.270 align:start position:0%
interested in running validators were
not<00:17:27.900><c> very</c><00:17:28.079><c> tech</c><00:17:28.260><c> savvy</c><00:17:28.679><c> are</c><00:17:28.919><c> still</c><00:17:29.100><c> looking</c>

00:17:29.270 --> 00:17:29.280 align:start position:0%
not very tech savvy are still looking
 

00:17:29.280 --> 00:17:32.150 align:start position:0%
not very tech savvy are still looking
for<00:17:29.520><c> a</c><00:17:29.640><c> non-command</c><00:17:30.240><c> line</c><00:17:30.799><c> interface</c><00:17:31.799><c> to</c><00:17:32.040><c> set</c>

00:17:32.150 --> 00:17:32.160 align:start position:0%
for a non-command line interface to set
 

00:17:32.160 --> 00:17:35.510 align:start position:0%
for a non-command line interface to set
up<00:17:32.280><c> the</c><00:17:32.460><c> validators</c><00:17:32.940><c> a</c><00:17:33.419><c> fair</c><00:17:33.660><c> ask</c><00:17:33.900><c> right</c>

00:17:35.510 --> 00:17:35.520 align:start position:0%
up the validators a fair ask right
 

00:17:35.520 --> 00:17:37.250 align:start position:0%
up the validators a fair ask right
um<00:17:35.640><c> the</c><00:17:36.120><c> Second</c><00:17:36.240><c> Challenge</c><00:17:36.539><c> obviously</c><00:17:37.020><c> is</c>

00:17:37.250 --> 00:17:37.260 align:start position:0%
um the Second Challenge obviously is
 

00:17:37.260 --> 00:17:39.350 align:start position:0%
um the Second Challenge obviously is
don't<00:17:37.500><c> have</c><00:17:37.740><c> the</c><00:17:37.919><c> 32</c><00:17:38.220><c> or</c><00:17:38.400><c> 16</c><00:17:38.520><c> age</c><00:17:38.880><c> so</c><00:17:39.059><c> how</c><00:17:39.179><c> do</c><00:17:39.299><c> I</c>

00:17:39.350 --> 00:17:39.360 align:start position:0%
don't have the 32 or 16 age so how do I
 

00:17:39.360 --> 00:17:40.610 align:start position:0%
don't have the 32 or 16 age so how do I
participate

00:17:40.610 --> 00:17:40.620 align:start position:0%
participate
 

00:17:40.620 --> 00:17:43.990 align:start position:0%
participate
right<00:17:41.100><c> so</c><00:17:41.700><c> this</c><00:17:42.240><c> is</c><00:17:42.419><c> huge</c>

00:17:43.990 --> 00:17:44.000 align:start position:0%
right so this is huge
 

00:17:44.000 --> 00:17:46.610 align:start position:0%
right so this is huge
idea<00:17:45.000><c> in</c><00:17:45.360><c> the</c><00:17:45.480><c> in</c><00:17:45.600><c> the</c><00:17:45.840><c> in</c><00:17:46.020><c> the</c><00:17:46.200><c> in</c><00:17:46.380><c> this</c>

00:17:46.610 --> 00:17:46.620 align:start position:0%
idea in the in the in the in this
 

00:17:46.620 --> 00:17:48.350 align:start position:0%
idea in the in the in the in this
segment<00:17:46.919><c> of</c><00:17:47.160><c> individual</c><00:17:47.580><c> users</c><00:17:48.000><c> which</c><00:17:48.240><c> is</c>

00:17:48.350 --> 00:17:48.360 align:start position:0%
segment of individual users which is
 

00:17:48.360 --> 00:17:49.190 align:start position:0%
segment of individual users which is
around

00:17:49.190 --> 00:17:49.200 align:start position:0%
around
 

00:17:49.200 --> 00:17:51.650 align:start position:0%
around
that<00:17:49.919><c> you</c><00:17:50.100><c> need</c><00:17:50.340><c> 16</c><00:17:50.520><c> to</c><00:17:50.820><c> 32</c><00:17:51.120><c> weeks</c><00:17:51.360><c> to</c>

00:17:51.650 --> 00:17:51.660 align:start position:0%
that you need 16 to 32 weeks to
 

00:17:51.660 --> 00:17:53.390 align:start position:0%
that you need 16 to 32 weeks to
participate<00:17:52.140><c> in</c><00:17:52.320><c> the</c><00:17:52.440><c> network</c><00:17:52.559><c> but</c><00:17:53.220><c> there</c>

00:17:53.390 --> 00:17:53.400 align:start position:0%
participate in the network but there
 

00:17:53.400 --> 00:17:54.890 align:start position:0%
participate in the network but there
could<00:17:53.580><c> be</c><00:17:53.640><c> other</c><00:17:53.820><c> ways</c><00:17:54.179><c> to</c><00:17:54.299><c> participate</c><00:17:54.720><c> in</c>

00:17:54.890 --> 00:17:54.900 align:start position:0%
could be other ways to participate in
 

00:17:54.900 --> 00:17:56.330 align:start position:0%
could be other ways to participate in
the<00:17:55.020><c> network</c><00:17:55.200><c> when</c><00:17:55.559><c> you're</c><00:17:55.740><c> not</c><00:17:55.919><c> validating</c>

00:17:56.330 --> 00:17:56.340 align:start position:0%
the network when you're not validating
 

00:17:56.340 --> 00:17:57.970 align:start position:0%
the network when you're not validating
and<00:17:56.700><c> we'd</c><00:17:56.880><c> like</c><00:17:57.000><c> to</c><00:17:57.120><c> explore</c><00:17:57.360><c> a</c><00:17:57.539><c> few</c><00:17:57.660><c> of</c><00:17:57.780><c> those</c>

00:17:57.970 --> 00:17:57.980 align:start position:0%
and we'd like to explore a few of those
 

00:17:57.980 --> 00:18:00.289 align:start position:0%
and we'd like to explore a few of those
in<00:17:58.980><c> this</c><00:17:59.160><c> talk</c><00:17:59.340><c> as</c><00:17:59.520><c> well</c>

00:18:00.289 --> 00:18:00.299 align:start position:0%
in this talk as well
 

00:18:00.299 --> 00:18:02.450 align:start position:0%
in this talk as well
and<00:18:00.780><c> finally</c><00:18:01.080><c> as</c><00:18:01.679><c> I</c><00:18:01.799><c> said</c><00:18:01.919><c> earlier</c><00:18:02.220><c> the</c>

00:18:02.450 --> 00:18:02.460 align:start position:0%
and finally as I said earlier the
 

00:18:02.460 --> 00:18:04.070 align:start position:0%
and finally as I said earlier the
information<00:18:02.580><c> is</c><00:18:02.940><c> scattered</c><00:18:03.299><c> across</c><00:18:03.660><c> forums</c>

00:18:04.070 --> 00:18:04.080 align:start position:0%
information is scattered across forums
 

00:18:04.080 --> 00:18:06.950 align:start position:0%
information is scattered across forums
across<00:18:04.620><c> across</c><00:18:05.039><c> different</c><00:18:05.220><c> guides</c><00:18:05.960><c> across</c>

00:18:06.950 --> 00:18:06.960 align:start position:0%
across across different guides across
 

00:18:06.960 --> 00:18:09.470 align:start position:0%
across across different guides across
guides<00:18:07.860><c> that</c><00:18:07.980><c> are</c><00:18:08.100><c> created</c><00:18:08.400><c> by</c><00:18:08.820><c> champions</c><00:18:09.299><c> in</c>

00:18:09.470 --> 00:18:09.480 align:start position:0%
guides that are created by champions in
 

00:18:09.480 --> 00:18:11.630 align:start position:0%
guides that are created by champions in
the<00:18:09.600><c> community</c><00:18:09.780><c> and</c><00:18:10.620><c> then</c><00:18:10.740><c> Discord</c><00:18:11.160><c> channels</c>

00:18:11.630 --> 00:18:11.640 align:start position:0%
the community and then Discord channels
 

00:18:11.640 --> 00:18:14.750 align:start position:0%
the community and then Discord channels
so<00:18:12.000><c> it</c><00:18:12.600><c> becomes</c><00:18:12.960><c> difficult</c><00:18:13.320><c> if</c><00:18:14.160><c> not</c><00:18:14.340><c> you</c><00:18:14.640><c> know</c>

00:18:14.750 --> 00:18:14.760 align:start position:0%
so it becomes difficult if not you know
 

00:18:14.760 --> 00:18:17.510 align:start position:0%
so it becomes difficult if not you know
impossible<00:18:15.380><c> to</c><00:18:16.380><c> coordinate</c><00:18:17.039><c> and</c><00:18:17.220><c> to</c><00:18:17.400><c> be</c>

00:18:17.510 --> 00:18:17.520 align:start position:0%
impossible to coordinate and to be
 

00:18:17.520 --> 00:18:19.549 align:start position:0%
impossible to coordinate and to be
across<00:18:17.880><c> all</c><00:18:18.179><c> of</c><00:18:18.360><c> this</c><00:18:18.660><c> especially</c><00:18:19.140><c> when</c><00:18:19.380><c> there</c>

00:18:19.549 --> 00:18:19.559 align:start position:0%
across all of this especially when there
 

00:18:19.559 --> 00:18:21.289 align:start position:0%
across all of this especially when there
are<00:18:19.679><c> multiple</c><00:18:19.980><c> releases</c><00:18:20.460><c> going</c><00:18:20.640><c> out</c><00:18:20.820><c> for</c><00:18:21.120><c> the</c>

00:18:21.289 --> 00:18:21.299 align:start position:0%
are multiple releases going out for the
 

00:18:21.299 --> 00:18:22.850 align:start position:0%
are multiple releases going out for the
client

00:18:22.850 --> 00:18:22.860 align:start position:0%
client
 

00:18:22.860 --> 00:18:25.250 align:start position:0%
client
um<00:18:23.000><c> professional</c><00:18:24.000><c> node</c><00:18:24.299><c> operators</c><00:18:24.720><c> have</c><00:18:25.080><c> the</c>

00:18:25.250 --> 00:18:25.260 align:start position:0%
um professional node operators have the
 

00:18:25.260 --> 00:18:27.110 align:start position:0%
um professional node operators have the
bandwidth<00:18:25.740><c> the</c><00:18:25.860><c> capacity</c><00:18:26.280><c> to</c><00:18:26.700><c> be</c><00:18:26.820><c> able</c><00:18:26.940><c> to</c>

00:18:27.110 --> 00:18:27.120 align:start position:0%
bandwidth the capacity to be able to
 

00:18:27.120 --> 00:18:29.510 align:start position:0%
bandwidth the capacity to be able to
deal<00:18:27.240><c> with</c><00:18:27.480><c> this</c><00:18:27.919><c> individuals</c><00:18:28.919><c> don't</c><00:18:29.100><c> right</c>

00:18:29.510 --> 00:18:29.520 align:start position:0%
deal with this individuals don't right
 

00:18:29.520 --> 00:18:32.570 align:start position:0%
deal with this individuals don't right
so<00:18:30.179><c> there's</c><00:18:30.539><c> an</c><00:18:30.840><c> absolute</c><00:18:31.200><c> need</c><00:18:31.500><c> and</c><00:18:32.340><c> I</c><00:18:32.460><c> know</c>

00:18:32.570 --> 00:18:32.580 align:start position:0%
so there's an absolute need and I know
 

00:18:32.580 --> 00:18:35.210 align:start position:0%
so there's an absolute need and I know
the<00:18:32.820><c> community</c><00:18:32.940><c> has</c><00:18:33.419><c> been</c><00:18:33.919><c> asking</c><00:18:34.919><c> for</c>

00:18:35.210 --> 00:18:35.220 align:start position:0%
the community has been asking for
 

00:18:35.220 --> 00:18:37.669 align:start position:0%
the community has been asking for
individuals<00:18:35.700><c> to</c><00:18:35.880><c> step</c><00:18:36.059><c> up</c><00:18:36.240><c> and</c><00:18:36.480><c> take</c><00:18:36.660><c> on</c><00:18:36.900><c> uh</c>

00:18:37.669 --> 00:18:37.679 align:start position:0%
individuals to step up and take on uh
 

00:18:37.679 --> 00:18:40.070 align:start position:0%
individuals to step up and take on uh
the<00:18:37.860><c> responsibility</c><00:18:38.340><c> to</c><00:18:38.640><c> run</c><00:18:38.820><c> more</c><00:18:39.000><c> nodes</c><00:18:39.299><c> run</c>

00:18:40.070 --> 00:18:40.080 align:start position:0%
the responsibility to run more nodes run
 

00:18:40.080 --> 00:18:41.450 align:start position:0%
the responsibility to run more nodes run
it<00:18:40.260><c> run</c><00:18:40.440><c> them</c><00:18:40.620><c> at</c><00:18:40.799><c> home</c>

00:18:41.450 --> 00:18:41.460 align:start position:0%
it run them at home
 

00:18:41.460 --> 00:18:43.310 align:start position:0%
it run them at home
but<00:18:41.880><c> there</c><00:18:42.059><c> are</c><00:18:42.179><c> real</c><00:18:42.360><c> challenges</c><00:18:42.840><c> and</c><00:18:43.140><c> we</c>

00:18:43.310 --> 00:18:43.320 align:start position:0%
but there are real challenges and we
 

00:18:43.320 --> 00:18:44.870 align:start position:0%
but there are real challenges and we
from<00:18:43.679><c> a</c><00:18:43.799><c> client</c><00:18:43.980><c> team</c><00:18:44.160><c> perspective</c><00:18:44.580><c> we</c>

00:18:44.870 --> 00:18:44.880 align:start position:0%
from a client team perspective we
 

00:18:44.880 --> 00:18:46.130 align:start position:0%
from a client team perspective we
definitely<00:18:45.179><c> acknowledge</c><00:18:45.600><c> that</c><00:18:45.780><c> these</c><00:18:46.020><c> are</c>

00:18:46.130 --> 00:18:46.140 align:start position:0%
definitely acknowledge that these are
 

00:18:46.140 --> 00:18:48.770 align:start position:0%
definitely acknowledge that these are
challenges<00:18:46.440><c> that</c><00:18:46.620><c> need</c><00:18:46.740><c> to</c><00:18:46.860><c> be</c><00:18:46.980><c> addressed</c>

00:18:48.770 --> 00:18:48.780 align:start position:0%
challenges that need to be addressed
 

00:18:48.780 --> 00:18:51.350 align:start position:0%
challenges that need to be addressed
like<00:18:49.559><c> let's</c><00:18:49.980><c> give</c><00:18:50.460><c> credit</c><00:18:50.640><c> where</c><00:18:50.940><c> it's</c><00:18:51.120><c> due</c>

00:18:51.350 --> 00:18:51.360 align:start position:0%
like let's give credit where it's due
 

00:18:51.360 --> 00:18:55.310 align:start position:0%
like let's give credit where it's due
right<00:18:51.780><c> so</c><00:18:52.260><c> credit</c><00:18:53.160><c> to</c><00:18:53.400><c> Rocket</c><00:18:53.760><c> pool</c><00:18:53.940><c> to</c><00:18:54.480><c> uh</c><00:18:55.020><c> to</c>

00:18:55.310 --> 00:18:55.320 align:start position:0%
right so credit to Rocket pool to uh to
 

00:18:55.320 --> 00:18:58.190 align:start position:0%
right so credit to Rocket pool to uh to
uh<00:18:55.500><c> stereium</c><00:18:56.039><c> to</c><00:18:56.520><c> DAP</c><00:18:56.760><c> node</c><00:18:57.059><c> who</c><00:18:57.780><c> have</c><00:18:57.960><c> all</c>

00:18:58.190 --> 00:18:58.200 align:start position:0%
uh stereium to DAP node who have all
 

00:18:58.200 --> 00:18:59.930 align:start position:0%
uh stereium to DAP node who have all
stepped<00:18:58.559><c> up</c><00:18:58.620><c> in</c><00:18:58.860><c> a</c><00:18:58.919><c> way</c><00:18:59.039><c> to</c><00:18:59.460><c> offer</c><00:18:59.760><c> some</c>

00:18:59.930 --> 00:18:59.940 align:start position:0%
stepped up in a way to offer some
 

00:18:59.940 --> 00:19:02.029 align:start position:0%
stepped up in a way to offer some
solutions<00:19:00.360><c> while</c><00:19:00.720><c> there</c><00:19:00.900><c> is</c><00:19:01.020><c> a</c><00:19:01.140><c> gap</c>

00:19:02.029 --> 00:19:02.039 align:start position:0%
solutions while there is a gap
 

00:19:02.039 --> 00:19:05.090 align:start position:0%
solutions while there is a gap
tap<00:19:02.640><c> node</c><00:19:03.059><c> Stadium</c><00:19:03.419><c> offer</c><00:19:04.380><c> ability</c><00:19:04.740><c> for</c><00:19:05.039><c> you</c>

00:19:05.090 --> 00:19:05.100 align:start position:0%
tap node Stadium offer ability for you
 

00:19:05.100 --> 00:19:07.190 align:start position:0%
tap node Stadium offer ability for you
to<00:19:05.280><c> spin</c><00:19:05.460><c> up</c><00:19:05.580><c> your</c><00:19:05.760><c> own</c><00:19:05.880><c> nodes</c><00:19:06.120><c> right</c><00:19:06.780><c> on</c><00:19:07.080><c> your</c>

00:19:07.190 --> 00:19:07.200 align:start position:0%
to spin up your own nodes right on your
 

00:19:07.200 --> 00:19:08.230 align:start position:0%
to spin up your own nodes right on your
own<00:19:07.320><c> Hardware</c>

00:19:08.230 --> 00:19:08.240 align:start position:0%
own Hardware
 

00:19:08.240 --> 00:19:11.810 align:start position:0%
own Hardware
with<00:19:09.240><c> a</c><00:19:09.419><c> UI</c><00:19:09.799><c> so</c><00:19:10.799><c> you</c><00:19:11.039><c> know</c><00:19:11.160><c> you</c><00:19:11.280><c> don't</c><00:19:11.400><c> don't</c>

00:19:11.810 --> 00:19:11.820 align:start position:0%
with a UI so you know you don't don't
 

00:19:11.820 --> 00:19:13.310 align:start position:0%
with a UI so you know you don't don't
need<00:19:12.059><c> to</c><00:19:12.179><c> necessarily</c><00:19:12.600><c> use</c><00:19:12.780><c> a</c><00:19:12.960><c> command</c><00:19:13.200><c> line</c>

00:19:13.310 --> 00:19:13.320 align:start position:0%
need to necessarily use a command line
 

00:19:13.320 --> 00:19:14.930 align:start position:0%
need to necessarily use a command line
interface<00:19:13.679><c> so</c><00:19:13.860><c> these</c><00:19:14.160><c> are</c><00:19:14.280><c> these</c><00:19:14.880><c> are</c>

00:19:14.930 --> 00:19:14.940 align:start position:0%
interface so these are these are
 

00:19:14.940 --> 00:19:17.630 align:start position:0%
interface so these are these are
absolutely<00:19:15.299><c> positives</c><00:19:15.840><c> and</c><00:19:16.799><c> there's</c><00:19:17.460><c> an</c>

00:19:17.630 --> 00:19:17.640 align:start position:0%
absolutely positives and there's an
 

00:19:17.640 --> 00:19:20.270 align:start position:0%
absolutely positives and there's an
option<00:19:17.880><c> to</c><00:19:18.059><c> use</c><00:19:18.179><c> Nimbus</c><00:19:18.600><c> across</c><00:19:19.020><c> all</c><00:19:19.799><c> of</c><00:19:19.919><c> these</c>

00:19:20.270 --> 00:19:20.280 align:start position:0%
option to use Nimbus across all of these
 

00:19:20.280 --> 00:19:23.090 align:start position:0%
option to use Nimbus across all of these
uh<00:19:20.580><c> all</c><00:19:20.880><c> of</c><00:19:20.940><c> these</c><00:19:21.179><c> operators</c><00:19:21.679><c> rocket</c><00:19:22.679><c> pool</c><00:19:22.799><c> of</c>

00:19:23.090 --> 00:19:23.100 align:start position:0%
uh all of these operators rocket pool of
 

00:19:23.100 --> 00:19:25.250 align:start position:0%
uh all of these operators rocket pool of
course<00:19:23.220><c> very</c><00:19:23.700><c> popular</c><00:19:23.880><c> amongst</c><00:19:24.539><c> people</c><00:19:25.020><c> who</c>

00:19:25.250 --> 00:19:25.260 align:start position:0%
course very popular amongst people who
 

00:19:25.260 --> 00:19:26.630 align:start position:0%
course very popular amongst people who
want<00:19:25.380><c> to</c><00:19:25.500><c> run</c><00:19:25.620><c> a</c><00:19:25.799><c> node</c><00:19:25.980><c> from</c><00:19:26.160><c> their</c><00:19:26.280><c> own</c><00:19:26.460><c> homes</c>

00:19:26.630 --> 00:19:26.640 align:start position:0%
want to run a node from their own homes
 

00:19:26.640 --> 00:19:28.250 align:start position:0%
want to run a node from their own homes
whether<00:19:27.299><c> that's</c><00:19:27.539><c> a</c><00:19:27.720><c> full</c><00:19:27.780><c> node</c><00:19:28.080><c> whether</c>

00:19:28.250 --> 00:19:28.260 align:start position:0%
whether that's a full node whether
 

00:19:28.260 --> 00:19:31.250 align:start position:0%
whether that's a full node whether
that's<00:19:28.500><c> a</c><00:19:28.740><c> mini</c><00:19:28.799><c> pool</c><00:19:29.480><c> and</c><00:19:30.480><c> again</c><00:19:30.600><c> Nimbus</c><00:19:31.080><c> is</c>

00:19:31.250 --> 00:19:31.260 align:start position:0%
that's a mini pool and again Nimbus is
 

00:19:31.260 --> 00:19:33.230 align:start position:0%
that's a mini pool and again Nimbus is
extremely<00:19:31.620><c> popular</c><00:19:31.799><c> as</c><00:19:32.460><c> a</c><00:19:32.580><c> client</c><00:19:32.760><c> of</c><00:19:33.000><c> choice</c>

00:19:33.230 --> 00:19:33.240 align:start position:0%
extremely popular as a client of choice
 

00:19:33.240 --> 00:19:37.310 align:start position:0%
extremely popular as a client of choice
in<00:19:34.140><c> amongst</c><00:19:34.740><c> the</c><00:19:34.799><c> rocket</c><00:19:35.100><c> pool</c><00:19:35.220><c> users</c>

00:19:37.310 --> 00:19:37.320 align:start position:0%
in amongst the rocket pool users
 

00:19:37.320 --> 00:19:39.529 align:start position:0%
in amongst the rocket pool users
uh<00:19:37.980><c> limbus</c><00:19:38.400><c> is</c><00:19:38.580><c> doing</c><00:19:38.700><c> its</c><00:19:39.059><c> own</c><00:19:39.120><c> bit</c><00:19:39.299><c> to</c>

00:19:39.529 --> 00:19:39.539 align:start position:0%
uh limbus is doing its own bit to
 

00:19:39.539 --> 00:19:41.990 align:start position:0%
uh limbus is doing its own bit to
contribute<00:19:40.140><c> to</c><00:19:40.380><c> this</c><00:19:40.500><c> effort</c><00:19:40.799><c> right</c><00:19:41.100><c> so</c><00:19:41.640><c> we</c>

00:19:41.990 --> 00:19:42.000 align:start position:0%
contribute to this effort right so we
 

00:19:42.000 --> 00:19:43.250 align:start position:0%
contribute to this effort right so we
completely<00:19:42.480><c> acknowledge</c><00:19:42.840><c> that</c><00:19:43.020><c> our</c>

00:19:43.250 --> 00:19:43.260 align:start position:0%
completely acknowledge that our
 

00:19:43.260 --> 00:19:44.630 align:start position:0%
completely acknowledge that our
challenges<00:19:43.620><c> here</c><00:19:43.860><c> that</c><00:19:44.280><c> need</c><00:19:44.400><c> to</c><00:19:44.520><c> be</c>

00:19:44.630 --> 00:19:44.640 align:start position:0%
challenges here that need to be
 

00:19:44.640 --> 00:19:47.690 align:start position:0%
challenges here that need to be
addressed<00:19:45.059><c> and</c><00:19:45.840><c> we</c><00:19:46.200><c> have</c><00:19:46.380><c> some</c><00:19:46.740><c> views</c><00:19:47.340><c> on</c><00:19:47.460><c> how</c>

00:19:47.690 --> 00:19:47.700 align:start position:0%
addressed and we have some views on how
 

00:19:47.700 --> 00:19:49.250 align:start position:0%
addressed and we have some views on how
this<00:19:47.940><c> can</c><00:19:48.059><c> be</c><00:19:48.179><c> addressed</c>

00:19:49.250 --> 00:19:49.260 align:start position:0%
this can be addressed
 

00:19:49.260 --> 00:19:50.990 align:start position:0%
this can be addressed
the<00:19:49.799><c> first</c><00:19:49.919><c> thing</c><00:19:50.100><c> is</c><00:19:50.280><c> abstracting</c><00:19:50.820><c> the</c>

00:19:50.990 --> 00:19:51.000 align:start position:0%
the first thing is abstracting the
 

00:19:51.000 --> 00:19:53.470 align:start position:0%
the first thing is abstracting the
complexity<00:19:51.360><c> away</c><00:19:51.600><c> from</c><00:19:51.960><c> the</c><00:19:52.140><c> end</c><00:19:52.200><c> user</c><00:19:52.679><c> Right</c>

00:19:53.470 --> 00:19:53.480 align:start position:0%
complexity away from the end user Right
 

00:19:53.480 --> 00:19:57.049 align:start position:0%
complexity away from the end user Right
End<00:19:54.480><c> users</c><00:19:54.840><c> like</c><00:19:55.140><c> to</c><00:19:55.799><c> be</c><00:19:56.039><c> taken</c><00:19:56.520><c> on</c><00:19:56.700><c> a</c><00:19:56.820><c> journey</c>

00:19:57.049 --> 00:19:57.059 align:start position:0%
End users like to be taken on a journey
 

00:19:57.059 --> 00:19:59.210 align:start position:0%
End users like to be taken on a journey
if<00:19:57.539><c> you</c><00:19:57.660><c> can</c><00:19:57.720><c> give</c><00:19:57.900><c> them</c><00:19:58.080><c> a</c><00:19:58.260><c> wizard</c><00:19:58.620><c> and</c><00:19:59.039><c> follow</c>

00:19:59.210 --> 00:19:59.220 align:start position:0%
if you can give them a wizard and follow
 

00:19:59.220 --> 00:20:01.130 align:start position:0%
if you can give them a wizard and follow
the<00:19:59.460><c> journey</c><00:19:59.700><c> follow</c><00:19:59.940><c> the</c><00:20:00.179><c> wizard</c><00:20:00.480><c> to</c><00:20:00.660><c> get</c><00:20:00.840><c> to</c>

00:20:01.130 --> 00:20:01.140 align:start position:0%
the journey follow the wizard to get to
 

00:20:01.140 --> 00:20:04.190 align:start position:0%
the journey follow the wizard to get to
set<00:20:01.799><c> up</c><00:20:01.980><c> a</c><00:20:02.220><c> validator</c><00:20:02.940><c> successfully</c><00:20:03.720><c> easily</c>

00:20:04.190 --> 00:20:04.200 align:start position:0%
set up a validator successfully easily
 

00:20:04.200 --> 00:20:06.169 align:start position:0%
set up a validator successfully easily
and<00:20:04.740><c> be</c><00:20:04.919><c> able</c><00:20:05.100><c> to</c><00:20:05.220><c> monitor</c><00:20:05.640><c> that</c><00:20:05.820><c> in</c><00:20:06.120><c> a</c>

00:20:06.169 --> 00:20:06.179 align:start position:0%
and be able to monitor that in a
 

00:20:06.179 --> 00:20:08.690 align:start position:0%
and be able to monitor that in a
simplistic<00:20:06.539><c> fashion</c><00:20:07.020><c> then</c><00:20:07.799><c> that</c><00:20:08.039><c> is</c><00:20:08.220><c> what</c><00:20:08.580><c> the</c>

00:20:08.690 --> 00:20:08.700 align:start position:0%
simplistic fashion then that is what the
 

00:20:08.700 --> 00:20:11.630 align:start position:0%
simplistic fashion then that is what the
end<00:20:08.820><c> user</c><00:20:09.120><c> would</c><00:20:09.240><c> like</c><00:20:09.419><c> as</c><00:20:09.840><c> an</c><00:20:10.020><c> individual</c><00:20:10.440><c> so</c>

00:20:11.630 --> 00:20:11.640 align:start position:0%
end user would like as an individual so
 

00:20:11.640 --> 00:20:15.409 align:start position:0%
end user would like as an individual so
one<00:20:12.240><c> of</c><00:20:12.419><c> the</c><00:20:12.600><c> key</c><00:20:12.960><c> tenets</c><00:20:13.500><c> here</c><00:20:13.740><c> from</c><00:20:14.340><c> a</c><00:20:14.700><c> client</c>

00:20:15.409 --> 00:20:15.419 align:start position:0%
one of the key tenets here from a client
 

00:20:15.419 --> 00:20:17.510 align:start position:0%
one of the key tenets here from a client
Evolution<00:20:15.720><c> point</c><00:20:16.080><c> of</c><00:20:16.260><c> view</c><00:20:16.380><c> for</c><00:20:16.980><c> individuals</c>

00:20:17.510 --> 00:20:17.520 align:start position:0%
Evolution point of view for individuals
 

00:20:17.520 --> 00:20:20.090 align:start position:0%
Evolution point of view for individuals
is<00:20:18.000><c> abstracting</c><00:20:18.600><c> complexity</c><00:20:19.140><c> away</c><00:20:19.380><c> from</c><00:20:19.919><c> the</c>

00:20:20.090 --> 00:20:20.100 align:start position:0%
is abstracting complexity away from the
 

00:20:20.100 --> 00:20:21.169 align:start position:0%
is abstracting complexity away from the
individual

00:20:21.169 --> 00:20:21.179 align:start position:0%
individual
 

00:20:21.179 --> 00:20:23.510 align:start position:0%
individual
and<00:20:21.780><c> this</c><00:20:22.140><c> takes</c><00:20:22.320><c> the</c><00:20:22.559><c> form</c><00:20:22.679><c> as</c><00:20:23.039><c> far</c><00:20:23.220><c> as</c><00:20:23.340><c> status</c>

00:20:23.510 --> 00:20:23.520 align:start position:0%
and this takes the form as far as status
 

00:20:23.520 --> 00:20:25.970 align:start position:0%
and this takes the form as far as status
is<00:20:23.820><c> concerned</c><00:20:24.299><c> we've</c><00:20:25.200><c> talked</c><00:20:25.440><c> about</c><00:20:25.500><c> let's</c>

00:20:25.970 --> 00:20:25.980 align:start position:0%
is concerned we've talked about let's
 

00:20:25.980 --> 00:20:28.310 align:start position:0%
is concerned we've talked about let's
say<00:20:26.160><c> theorem</c><00:20:26.760><c> and</c><00:20:27.000><c> death</c><00:20:27.120><c> node</c><00:20:27.480><c> but</c><00:20:27.780><c> status</c><00:20:27.960><c> is</c>

00:20:28.310 --> 00:20:28.320 align:start position:0%
say theorem and death node but status is
 

00:20:28.320 --> 00:20:30.250 align:start position:0%
say theorem and death node but status is
heading<00:20:28.679><c> in</c><00:20:29.039><c> the</c><00:20:29.160><c> similar</c><00:20:29.520><c> Direction</c>

00:20:30.250 --> 00:20:30.260 align:start position:0%
heading in the similar Direction
 

00:20:30.260 --> 00:20:32.570 align:start position:0%
heading in the similar Direction
the<00:20:31.260><c> status</c><00:20:31.440><c> Network</c><00:20:31.860><c> team</c><00:20:32.220><c> is</c><00:20:32.460><c> actually</c>

00:20:32.570 --> 00:20:32.580 align:start position:0%
the status Network team is actually
 

00:20:32.580 --> 00:20:34.430 align:start position:0%
the status Network team is actually
planning<00:20:33.000><c> to</c><00:20:33.120><c> integrate</c><00:20:33.480><c> the</c><00:20:33.720><c> Nimbus</c><00:20:34.080><c> client</c>

00:20:34.430 --> 00:20:34.440 align:start position:0%
planning to integrate the Nimbus client
 

00:20:34.440 --> 00:20:37.250 align:start position:0%
planning to integrate the Nimbus client
inside<00:20:35.220><c> the</c><00:20:35.580><c> status</c><00:20:35.760><c> desktop</c><00:20:36.299><c> which</c><00:20:37.020><c> will</c>

00:20:37.250 --> 00:20:37.260 align:start position:0%
inside the status desktop which will
 

00:20:37.260 --> 00:20:41.150 align:start position:0%
inside the status desktop which will
give<00:20:37.620><c> users</c><00:20:38.580><c> the</c><00:20:39.059><c> ability</c><00:20:39.299><c> to</c><00:20:39.960><c> spin</c><00:20:40.620><c> up</c><00:20:40.740><c> a</c><00:20:40.919><c> node</c>

00:20:41.150 --> 00:20:41.160 align:start position:0%
give users the ability to spin up a node
 

00:20:41.160 --> 00:20:43.070 align:start position:0%
give users the ability to spin up a node
manage<00:20:41.760><c> it</c><00:20:41.940><c> through</c><00:20:42.299><c> the</c><00:20:42.480><c> status</c><00:20:42.600><c> desktop</c>

00:20:43.070 --> 00:20:43.080 align:start position:0%
manage it through the status desktop
 

00:20:43.080 --> 00:20:45.950 align:start position:0%
manage it through the status desktop
application<00:20:44.100><c> so</c><00:20:44.760><c> this</c><00:20:45.120><c> is</c><00:20:45.299><c> one</c><00:20:45.539><c> of</c><00:20:45.660><c> the</c><00:20:45.720><c> things</c>

00:20:45.950 --> 00:20:45.960 align:start position:0%
application so this is one of the things
 

00:20:45.960 --> 00:20:47.750 align:start position:0%
application so this is one of the things
that<00:20:46.200><c> Nimbus</c><00:20:46.620><c> and</c><00:20:46.860><c> the</c><00:20:47.160><c> status</c><00:20:47.280><c> team</c><00:20:47.580><c> are</c>

00:20:47.750 --> 00:20:47.760 align:start position:0%
that Nimbus and the status team are
 

00:20:47.760 --> 00:20:50.330 align:start position:0%
that Nimbus and the status team are
working<00:20:48.000><c> on</c><00:20:48.299><c> to</c><00:20:48.900><c> address</c>

00:20:50.330 --> 00:20:50.340 align:start position:0%
working on to address
 

00:20:50.340 --> 00:20:52.610 align:start position:0%
working on to address
second<00:20:50.820><c> one</c><00:20:51.179><c> let's</c><00:20:51.660><c> talk</c><00:20:51.900><c> about</c><00:20:52.020><c> the</c><00:20:52.320><c> elephant</c>

00:20:52.610 --> 00:20:52.620 align:start position:0%
second one let's talk about the elephant
 

00:20:52.620 --> 00:20:55.250 align:start position:0%
second one let's talk about the elephant
in<00:20:52.799><c> the</c><00:20:52.919><c> room</c><00:20:53.039><c> who's</c><00:20:54.000><c> recently</c><00:20:54.600><c> set</c><00:20:54.780><c> up</c><00:20:54.960><c> a</c><00:20:55.080><c> note</c>

00:20:55.250 --> 00:20:55.260 align:start position:0%
in the room who's recently set up a note
 

00:20:55.260 --> 00:20:56.810 align:start position:0%
in the room who's recently set up a note
quick<00:20:55.679><c> show</c><00:20:55.919><c> of</c><00:20:56.100><c> hand</c>

00:20:56.810 --> 00:20:56.820 align:start position:0%
quick show of hand
 

00:20:56.820 --> 00:20:58.730 align:start position:0%
quick show of hand
all<00:20:57.179><c> right</c>

00:20:58.730 --> 00:20:58.740 align:start position:0%
all right
 

00:20:58.740 --> 00:21:00.529 align:start position:0%
all right
um You<00:20:59.400><c> had</c><00:20:59.520><c> to</c><00:20:59.640><c> set</c><00:20:59.760><c> up</c><00:20:59.880><c> one</c><00:21:00.120><c> execution</c>

00:21:00.529 --> 00:21:00.539 align:start position:0%
um You had to set up one execution
 

00:21:00.539 --> 00:21:01.549 align:start position:0%
um You had to set up one execution
client

00:21:01.549 --> 00:21:01.559 align:start position:0%
client
 

00:21:01.559 --> 00:21:03.289 align:start position:0%
client
consensus<00:21:02.280><c> client</c>

00:21:03.289 --> 00:21:03.299 align:start position:0%
consensus client
 

00:21:03.299 --> 00:21:05.330 align:start position:0%
consensus client
or<00:21:03.960><c> probably</c><00:21:04.260><c> even</c><00:21:04.500><c> Beacon</c><00:21:04.860><c> node</c><00:21:05.100><c> and</c><00:21:05.220><c> a</c>

00:21:05.330 --> 00:21:05.340 align:start position:0%
or probably even Beacon node and a
 

00:21:05.340 --> 00:21:06.590 align:start position:0%
or probably even Beacon node and a
validator<00:21:05.580><c> client</c><00:21:05.880><c> let's</c><00:21:06.120><c> talk</c><00:21:06.240><c> about</c><00:21:06.360><c> the</c>

00:21:06.590 --> 00:21:06.600 align:start position:0%
validator client let's talk about the
 

00:21:06.600 --> 00:21:08.510 align:start position:0%
validator client let's talk about the
two<00:21:06.720><c> components</c><00:21:07.200><c> individually</c><00:21:07.620><c> and</c><00:21:08.400><c> then</c>

00:21:08.510 --> 00:21:08.520 align:start position:0%
two components individually and then
 

00:21:08.520 --> 00:21:10.730 align:start position:0%
two components individually and then
possibly<00:21:08.880><c> an</c><00:21:09.120><c> Mev</c><00:21:09.539><c> setup</c><00:21:09.840><c> right</c>

00:21:10.730 --> 00:21:10.740 align:start position:0%
possibly an Mev setup right
 

00:21:10.740 --> 00:21:13.370 align:start position:0%
possibly an Mev setup right
that<00:21:11.280><c> is</c><00:21:11.400><c> like</c><00:21:11.640><c> four</c><00:21:11.880><c> steps</c>

00:21:13.370 --> 00:21:13.380 align:start position:0%
that is like four steps
 

00:21:13.380 --> 00:21:15.830 align:start position:0%
that is like four steps
it's<00:21:13.559><c> too</c><00:21:13.860><c> complex</c><00:21:14.220><c> right</c><00:21:14.580><c> for</c><00:21:15.240><c> individuals</c>

00:21:15.830 --> 00:21:15.840 align:start position:0%
it's too complex right for individuals
 

00:21:15.840 --> 00:21:17.270 align:start position:0%
it's too complex right for individuals
when<00:21:16.020><c> we're</c><00:21:16.200><c> talking</c><00:21:16.380><c> about</c><00:21:16.559><c> no</c><00:21:16.799><c> command</c><00:21:17.160><c> line</c>

00:21:17.270 --> 00:21:17.280 align:start position:0%
when we're talking about no command line
 

00:21:17.280 --> 00:21:20.630 align:start position:0%
when we're talking about no command line
options<00:21:17.760><c> and</c><00:21:18.480><c> presenting</c><00:21:18.960><c> a</c><00:21:19.080><c> simpler</c><00:21:19.440><c> UI</c>

00:21:20.630 --> 00:21:20.640 align:start position:0%
options and presenting a simpler UI
 

00:21:20.640 --> 00:21:22.430 align:start position:0%
options and presenting a simpler UI
walking<00:21:21.299><c> through</c><00:21:21.600><c> setting</c><00:21:22.140><c> up</c><00:21:22.260><c> four</c>

00:21:22.430 --> 00:21:22.440 align:start position:0%
walking through setting up four
 

00:21:22.440 --> 00:21:24.230 align:start position:0%
walking through setting up four
different<00:21:22.740><c> clients</c><00:21:23.580><c> with</c><00:21:23.880><c> four</c><00:21:24.000><c> different</c>

00:21:24.230 --> 00:21:24.240 align:start position:0%
different clients with four different
 

00:21:24.240 --> 00:21:26.510 align:start position:0%
different clients with four different
guides<00:21:24.660><c> but</c><00:21:25.020><c> potentially</c><00:21:25.500><c> all</c><00:21:25.860><c> components</c><00:21:26.460><c> at</c>

00:21:26.510 --> 00:21:26.520 align:start position:0%
guides but potentially all components at
 

00:21:26.520 --> 00:21:28.490 align:start position:0%
guides but potentially all components at
least<00:21:26.700><c> is</c><00:21:27.360><c> complex</c>

00:21:28.490 --> 00:21:28.500 align:start position:0%
least is complex
 

00:21:28.500 --> 00:21:30.529 align:start position:0%
least is complex
and<00:21:28.980><c> this</c><00:21:29.159><c> could</c><00:21:29.340><c> get</c><00:21:29.580><c> even</c><00:21:29.760><c> more</c><00:21:30.000><c> complex</c><00:21:30.299><c> if</c>

00:21:30.529 --> 00:21:30.539 align:start position:0%
and this could get even more complex if
 

00:21:30.539 --> 00:21:33.289 align:start position:0%
and this could get even more complex if
it's<00:21:30.720><c> not</c><00:21:30.960><c> checked</c><00:21:31.380><c> right</c><00:21:31.500><c> now</c><00:21:31.740><c> so</c><00:21:32.460><c> we</c><00:21:33.120><c> need</c><00:21:33.179><c> to</c>

00:21:33.289 --> 00:21:33.299 align:start position:0%
it's not checked right now so we need to
 

00:21:33.299 --> 00:21:35.210 align:start position:0%
it's not checked right now so we need to
do<00:21:33.480><c> something</c><00:21:33.659><c> about</c><00:21:33.900><c> this</c><00:21:34.200><c> and</c><00:21:34.679><c> from</c><00:21:35.100><c> a</c>

00:21:35.210 --> 00:21:35.220 align:start position:0%
do something about this and from a
 

00:21:35.220 --> 00:21:37.190 align:start position:0%
do something about this and from a
nimbus<00:21:35.580><c> point</c><00:21:35.820><c> of</c><00:21:36.000><c> view</c><00:21:36.179><c> one</c><00:21:36.900><c> of</c><00:21:36.960><c> the</c><00:21:37.080><c> things</c>

00:21:37.190 --> 00:21:37.200 align:start position:0%
nimbus point of view one of the things
 

00:21:37.200 --> 00:21:39.409 align:start position:0%
nimbus point of view one of the things
we<00:21:37.380><c> would</c><00:21:37.500><c> like</c><00:21:37.679><c> to</c><00:21:37.799><c> do</c><00:21:37.980><c> and</c><00:21:38.340><c> we</c><00:21:38.580><c> are</c>

00:21:39.409 --> 00:21:39.419 align:start position:0%
we would like to do and we are
 

00:21:39.419 --> 00:21:43.909 align:start position:0%
we would like to do and we are
working<00:21:39.900><c> on</c><00:21:40.200><c> is</c><00:21:40.860><c> a</c><00:21:41.400><c> unified</c><00:21:42.620><c> execution</c><00:21:43.620><c> plus</c>

00:21:43.909 --> 00:21:43.919 align:start position:0%
working on is a unified execution plus
 

00:21:43.919 --> 00:21:46.070 align:start position:0%
working on is a unified execution plus
consensus<00:21:44.520><c> client</c><00:21:45.059><c> or</c>

00:21:46.070 --> 00:21:46.080 align:start position:0%
consensus client or
 

00:21:46.080 --> 00:21:48.470 align:start position:0%
consensus client or
actually<00:21:46.740><c> an</c><00:21:47.220><c> execution</c><00:21:47.580><c> client</c><00:21:47.940><c> that</c><00:21:48.240><c> works</c>

00:21:48.470 --> 00:21:48.480 align:start position:0%
actually an execution client that works
 

00:21:48.480 --> 00:21:49.850 align:start position:0%
actually an execution client that works
really<00:21:48.600><c> well</c><00:21:48.840><c> with</c><00:21:49.020><c> the</c><00:21:49.140><c> consensus</c><00:21:49.559><c> client</c>

00:21:49.850 --> 00:21:49.860 align:start position:0%
really well with the consensus client
 

00:21:49.860 --> 00:21:52.669 align:start position:0%
really well with the consensus client
from<00:21:50.580><c> Nimbus</c><00:21:51.059><c> so</c><00:21:51.539><c> a</c><00:21:51.659><c> nimbus</c><00:21:52.020><c> execution</c><00:21:52.380><c> client</c>

00:21:52.669 --> 00:21:52.679 align:start position:0%
from Nimbus so a nimbus execution client
 

00:21:52.679 --> 00:21:56.029 align:start position:0%
from Nimbus so a nimbus execution client
and<00:21:52.860><c> a</c><00:21:52.980><c> numbers</c><00:21:53.100><c> consensus</c><00:21:53.640><c> client</c><00:21:53.940><c> together</c>

00:21:56.029 --> 00:21:56.039 align:start position:0%
and a numbers consensus client together
 

00:21:56.039 --> 00:21:58.370 align:start position:0%
and a numbers consensus client together
um<00:21:56.520><c> there</c><00:21:57.059><c> will</c><00:21:57.179><c> be</c><00:21:57.299><c> ability</c><00:21:57.539><c> to</c><00:21:57.840><c> use</c><00:21:58.020><c> these</c>

00:21:58.370 --> 00:21:58.380 align:start position:0%
um there will be ability to use these
 

00:21:58.380 --> 00:21:59.990 align:start position:0%
um there will be ability to use these
clients<00:21:58.679><c> independently</c><00:21:59.280><c> and</c>

00:21:59.990 --> 00:22:00.000 align:start position:0%
clients independently and
 

00:22:00.000 --> 00:22:02.149 align:start position:0%
clients independently and
interchangeably<00:22:00.659><c> with</c><00:22:00.960><c> other</c><00:22:01.140><c> clients</c><00:22:01.919><c> as</c>

00:22:02.149 --> 00:22:02.159 align:start position:0%
interchangeably with other clients as
 

00:22:02.159 --> 00:22:05.029 align:start position:0%
interchangeably with other clients as
well<00:22:02.340><c> but</c><00:22:02.960><c> I</c><00:22:03.960><c> think</c><00:22:04.080><c> there</c><00:22:04.200><c> is</c><00:22:04.380><c> real</c><00:22:04.559><c> benefits</c>

00:22:05.029 --> 00:22:05.039 align:start position:0%
well but I think there is real benefits
 

00:22:05.039 --> 00:22:07.669 align:start position:0%
well but I think there is real benefits
if<00:22:05.340><c> we</c><00:22:05.460><c> can</c><00:22:05.640><c> simplify</c><00:22:06.059><c> the</c><00:22:06.360><c> setup</c><00:22:06.659><c> of</c><00:22:06.840><c> our</c><00:22:07.080><c> of</c><00:22:07.500><c> a</c>

00:22:07.669 --> 00:22:07.679 align:start position:0%
if we can simplify the setup of our of a
 

00:22:07.679 --> 00:22:09.770 align:start position:0%
if we can simplify the setup of our of a
validator<00:22:08.100><c> and</c><00:22:08.700><c> take</c><00:22:08.820><c> the</c><00:22:09.000><c> user</c><00:22:09.240><c> on</c><00:22:09.419><c> a</c><00:22:09.539><c> journey</c>

00:22:09.770 --> 00:22:09.780 align:start position:0%
validator and take the user on a journey
 

00:22:09.780 --> 00:22:11.330 align:start position:0%
validator and take the user on a journey
where<00:22:10.080><c> you</c><00:22:10.200><c> set</c><00:22:10.380><c> up</c><00:22:10.500><c> your</c><00:22:10.679><c> execution</c><00:22:11.039><c> client</c>

00:22:11.330 --> 00:22:11.340 align:start position:0%
where you set up your execution client
 

00:22:11.340 --> 00:22:13.490 align:start position:0%
where you set up your execution client
and<00:22:11.520><c> consensus</c><00:22:11.940><c> client</c><00:22:12.299><c> simply</c><00:22:13.080><c> in</c><00:22:13.200><c> the</c><00:22:13.380><c> same</c>

00:22:13.490 --> 00:22:13.500 align:start position:0%
and consensus client simply in the same
 

00:22:13.500 --> 00:22:15.230 align:start position:0%
and consensus client simply in the same
process<00:22:13.799><c> rather</c><00:22:14.280><c> having</c><00:22:14.460><c> to</c><00:22:14.640><c> switch</c><00:22:14.820><c> between</c>

00:22:15.230 --> 00:22:15.240 align:start position:0%
process rather having to switch between
 

00:22:15.240 --> 00:22:17.390 align:start position:0%
process rather having to switch between
things

00:22:17.390 --> 00:22:17.400 align:start position:0%
things
 

00:22:17.400 --> 00:22:19.070 align:start position:0%
things
there<00:22:17.760><c> are</c><00:22:17.880><c> other</c><00:22:18.000><c> ways</c><00:22:18.299><c> to</c><00:22:18.419><c> participate</c><00:22:18.900><c> in</c>

00:22:19.070 --> 00:22:19.080 align:start position:0%
there are other ways to participate in
 

00:22:19.080 --> 00:22:21.529 align:start position:0%
there are other ways to participate in
the<00:22:19.260><c> network</c><00:22:19.440><c> so</c>

00:22:21.529 --> 00:22:21.539 align:start position:0%
the network so
 

00:22:21.539 --> 00:22:23.810 align:start position:0%
the network so
the<00:22:22.320><c> light</c><00:22:22.500><c> proxy</c><00:22:23.039><c> this</c><00:22:23.280><c> is</c><00:22:23.340><c> something</c><00:22:23.520><c> I</c><00:22:23.700><c> want</c>

00:22:23.810 --> 00:22:23.820 align:start position:0%
the light proxy this is something I want
 

00:22:23.820 --> 00:22:25.130 align:start position:0%
the light proxy this is something I want
to<00:22:23.940><c> spend</c><00:22:24.120><c> a</c><00:22:24.240><c> bit</c><00:22:24.360><c> of</c><00:22:24.480><c> time</c><00:22:24.539><c> on</c><00:22:24.720><c> and</c><00:22:24.900><c> I</c><00:22:25.020><c> think</c>

00:22:25.130 --> 00:22:25.140 align:start position:0%
to spend a bit of time on and I think
 

00:22:25.140 --> 00:22:26.270 align:start position:0%
to spend a bit of time on and I think
I'm<00:22:25.260><c> running</c><00:22:25.380><c> out</c><00:22:25.620><c> of</c><00:22:25.740><c> time</c><00:22:25.860><c> but</c><00:22:26.039><c> I</c><00:22:26.220><c> have</c>

00:22:26.270 --> 00:22:26.280 align:start position:0%
I'm running out of time but I have
 

00:22:26.280 --> 00:22:28.490 align:start position:0%
I'm running out of time but I have
enough<00:22:26.460><c> time</c><00:22:26.700><c> to</c><00:22:26.820><c> cover</c><00:22:26.940><c> this</c><00:22:27.179><c> as</c><00:22:27.419><c> well</c>

00:22:28.490 --> 00:22:28.500 align:start position:0%
enough time to cover this as well
 

00:22:28.500 --> 00:22:30.649 align:start position:0%
enough time to cover this as well
so<00:22:29.039><c> the</c><00:22:29.280><c> light</c><00:22:29.400><c> web</c><00:22:29.640><c> proxy</c><00:22:30.059><c> is</c><00:22:30.240><c> something</c><00:22:30.360><c> that</c>

00:22:30.649 --> 00:22:30.659 align:start position:0%
so the light web proxy is something that
 

00:22:30.659 --> 00:22:34.310 align:start position:0%
so the light web proxy is something that
Nimbus<00:22:31.080><c> has</c><00:22:31.500><c> recently</c><00:22:31.919><c> released</c><00:22:32.340><c> and</c><00:22:33.260><c> this</c><00:22:34.260><c> is</c>

00:22:34.310 --> 00:22:34.320 align:start position:0%
Nimbus has recently released and this is
 

00:22:34.320 --> 00:22:36.110 align:start position:0%
Nimbus has recently released and this is
another<00:22:34.559><c> way</c><00:22:34.919><c> to</c><00:22:35.280><c> participate</c><00:22:35.760><c> in</c><00:22:35.940><c> the</c>

00:22:36.110 --> 00:22:36.120 align:start position:0%
another way to participate in the
 

00:22:36.120 --> 00:22:37.490 align:start position:0%
another way to participate in the
network

00:22:37.490 --> 00:22:37.500 align:start position:0%
network
 

00:22:37.500 --> 00:22:39.049 align:start position:0%
network
um

00:22:39.049 --> 00:22:39.059 align:start position:0%
um
 

00:22:39.059 --> 00:22:40.549 align:start position:0%
um
participating<00:22:39.780><c> in</c><00:22:40.020><c> the</c><00:22:40.140><c> network</c><00:22:40.200><c> doesn't</c>

00:22:40.549 --> 00:22:40.559 align:start position:0%
participating in the network doesn't
 

00:22:40.559 --> 00:22:42.590 align:start position:0%
participating in the network doesn't
only<00:22:40.860><c> mean</c><00:22:41.159><c> a</c><00:22:41.460><c> testing</c><00:22:41.760><c> and</c><00:22:41.880><c> validating</c><00:22:42.299><c> and</c>

00:22:42.590 --> 00:22:42.600 align:start position:0%
only mean a testing and validating and
 

00:22:42.600 --> 00:22:45.289 align:start position:0%
only mean a testing and validating and
creating<00:22:42.900><c> blocks</c><00:22:43.440><c> right</c><00:22:44.120><c> participating</c><00:22:45.120><c> in</c>

00:22:45.289 --> 00:22:45.299 align:start position:0%
creating blocks right participating in
 

00:22:45.299 --> 00:22:46.490 align:start position:0%
creating blocks right participating in
the<00:22:45.419><c> network</c><00:22:45.600><c> also</c><00:22:46.080><c> means</c><00:22:46.380><c> taking</c>

00:22:46.490 --> 00:22:46.500 align:start position:0%
the network also means taking
 

00:22:46.500 --> 00:22:49.130 align:start position:0%
the network also means taking
responsibility<00:22:47.220><c> and</c><00:22:47.580><c> checking</c><00:22:48.140><c> verifying</c>

00:22:49.130 --> 00:22:49.140 align:start position:0%
responsibility and checking verifying
 

00:22:49.140 --> 00:22:50.750 align:start position:0%
responsibility and checking verifying
you<00:22:49.679><c> know</c><00:22:49.740><c> where</c><00:22:49.980><c> you're</c><00:22:50.100><c> getting</c><00:22:50.280><c> your</c><00:22:50.460><c> data</c>

00:22:50.750 --> 00:22:50.760 align:start position:0%
you know where you're getting your data
 

00:22:50.760 --> 00:22:53.450 align:start position:0%
you know where you're getting your data
from<00:22:50.940><c> can</c><00:22:51.659><c> you</c><00:22:51.780><c> trust</c><00:22:52.020><c> that</c><00:22:52.200><c> data</c><00:22:52.620><c> should</c><00:22:53.280><c> you</c>

00:22:53.450 --> 00:22:53.460 align:start position:0%
from can you trust that data should you
 

00:22:53.460 --> 00:22:55.669 align:start position:0%
from can you trust that data should you
trust<00:22:53.700><c> that</c><00:22:53.880><c> data</c><00:22:54.179><c> if</c><00:22:54.659><c> if</c><00:22:54.840><c> you</c><00:22:55.020><c> should</c><00:22:55.200><c> if</c><00:22:55.559><c> you</c>

00:22:55.669 --> 00:22:55.679 align:start position:0%
trust that data if if you should if you
 

00:22:55.679 --> 00:22:56.990 align:start position:0%
trust that data if if you should if you
should<00:22:55.740><c> not</c><00:22:55.919><c> trust</c><00:22:56.100><c> the</c><00:22:56.280><c> data</c><00:22:56.520><c> you</c><00:22:56.640><c> should</c><00:22:56.760><c> at</c>

00:22:56.990 --> 00:22:57.000 align:start position:0%
should not trust the data you should at
 

00:22:57.000 --> 00:22:59.390 align:start position:0%
should not trust the data you should at
least<00:22:57.120><c> verify</c><00:22:57.600><c> it</c><00:22:57.720><c> right</c><00:22:58.080><c> and</c><00:22:58.799><c> so</c><00:22:58.919><c> lightweb</c>

00:22:59.390 --> 00:22:59.400 align:start position:0%
least verify it right and so lightweb
 

00:22:59.400 --> 00:23:01.130 align:start position:0%
least verify it right and so lightweb
proxy<00:22:59.700><c> gives</c><00:22:59.880><c> you</c><00:23:00.000><c> the</c><00:23:00.179><c> ability</c><00:23:00.419><c> to</c><00:23:00.780><c> do</c><00:23:00.900><c> that</c>

00:23:01.130 --> 00:23:01.140 align:start position:0%
proxy gives you the ability to do that
 

00:23:01.140 --> 00:23:04.549 align:start position:0%
proxy gives you the ability to do that
it's<00:23:01.980><c> a</c><00:23:02.640><c> it's</c><00:23:03.179><c> a</c><00:23:03.299><c> lot</c><00:23:03.480><c> it's</c><00:23:03.659><c> a</c>

00:23:04.549 --> 00:23:04.559 align:start position:0%
it's a it's a lot it's a
 

00:23:04.559 --> 00:23:06.409 align:start position:0%
it's a it's a lot it's a
you<00:23:05.039><c> can</c><00:23:05.220><c> basically</c><00:23:05.520><c> set</c><00:23:05.700><c> up</c><00:23:05.880><c> the</c><00:23:06.000><c> lightweight</c>

00:23:06.409 --> 00:23:06.419 align:start position:0%
you can basically set up the lightweight
 

00:23:06.419 --> 00:23:09.529 align:start position:0%
you can basically set up the lightweight
proxy<00:23:06.720><c> on</c><00:23:06.900><c> your</c><00:23:07.020><c> phone</c><00:23:07.260><c> right</c><00:23:07.980><c> and</c><00:23:08.940><c> instead</c><00:23:09.419><c> of</c>

00:23:09.529 --> 00:23:09.539 align:start position:0%
proxy on your phone right and instead of
 

00:23:09.539 --> 00:23:11.990 align:start position:0%
proxy on your phone right and instead of
trusting<00:23:10.020><c> the</c><00:23:10.200><c> endpoint</c><00:23:10.559><c> that</c><00:23:11.400><c> let's</c><00:23:11.640><c> say</c><00:23:11.820><c> the</c>

00:23:11.990 --> 00:23:12.000 align:start position:0%
trusting the endpoint that let's say the
 

00:23:12.000 --> 00:23:14.390 align:start position:0%
trusting the endpoint that let's say the
wallet<00:23:12.360><c> trusts</c><00:23:13.080><c> the</c><00:23:13.559><c> endpoint</c><00:23:13.860><c> that's</c><00:23:14.100><c> set</c><00:23:14.280><c> up</c>

00:23:14.390 --> 00:23:14.400 align:start position:0%
wallet trusts the endpoint that's set up
 

00:23:14.400 --> 00:23:16.490 align:start position:0%
wallet trusts the endpoint that's set up
for<00:23:14.520><c> the</c><00:23:14.640><c> wallet</c><00:23:14.940><c> instead</c><00:23:15.780><c> of</c><00:23:15.840><c> trusting</c><00:23:16.320><c> the</c>

00:23:16.490 --> 00:23:16.500 align:start position:0%
for the wallet instead of trusting the
 

00:23:16.500 --> 00:23:19.070 align:start position:0%
for the wallet instead of trusting the
data<00:23:16.860><c> that's</c><00:23:17.039><c> provided</c><00:23:17.460><c> by</c><00:23:17.640><c> the</c><00:23:17.820><c> endpoint</c><00:23:18.179><c> the</c>

00:23:19.070 --> 00:23:19.080 align:start position:0%
data that's provided by the endpoint the
 

00:23:19.080 --> 00:23:20.630 align:start position:0%
data that's provided by the endpoint the
light<00:23:19.200><c> web</c><00:23:19.440><c> proxy</c><00:23:19.860><c> can</c><00:23:19.980><c> actually</c><00:23:20.159><c> intercept</c>

00:23:20.630 --> 00:23:20.640 align:start position:0%
light web proxy can actually intercept
 

00:23:20.640 --> 00:23:23.090 align:start position:0%
light web proxy can actually intercept
that<00:23:20.940><c> call</c><00:23:21.120><c> to</c><00:23:21.900><c> give</c><00:23:22.020><c> you</c><00:23:22.140><c> an</c><00:23:22.260><c> example</c><00:23:22.559><c> if</c><00:23:22.919><c> you</c>

00:23:23.090 --> 00:23:23.100 align:start position:0%
that call to give you an example if you
 

00:23:23.100 --> 00:23:24.649 align:start position:0%
that call to give you an example if you
make<00:23:23.520><c> a</c><00:23:23.700><c> call</c><00:23:23.820><c> you</c><00:23:24.059><c> want</c><00:23:24.240><c> to</c><00:23:24.360><c> check</c><00:23:24.480><c> your</c>

00:23:24.649 --> 00:23:24.659 align:start position:0%
make a call you want to check your
 

00:23:24.659 --> 00:23:27.049 align:start position:0%
make a call you want to check your
balance<00:23:24.960><c> on</c><00:23:25.200><c> the</c><00:23:25.320><c> on</c><00:23:25.500><c> the</c><00:23:25.620><c> wallet</c><00:23:26.400><c> the</c><00:23:26.760><c> wallet</c>

00:23:27.049 --> 00:23:27.059 align:start position:0%
balance on the on the wallet the wallet
 

00:23:27.059 --> 00:23:28.909 align:start position:0%
balance on the on the wallet the wallet
makes<00:23:27.240><c> a</c><00:23:27.419><c> call</c><00:23:27.600><c> you</c><00:23:28.080><c> know</c><00:23:28.200><c> get</c><00:23:28.380><c> balanced</c><00:23:28.799><c> get</c>

00:23:28.909 --> 00:23:28.919 align:start position:0%
makes a call you know get balanced get
 

00:23:28.919 --> 00:23:31.070 align:start position:0%
makes a call you know get balanced get
it<00:23:29.100><c> balanced</c><00:23:29.520><c> the</c><00:23:30.179><c> lightweight</c><00:23:30.600><c> proxy</c><00:23:30.900><c> can</c>

00:23:31.070 --> 00:23:31.080 align:start position:0%
it balanced the lightweight proxy can
 

00:23:31.080 --> 00:23:32.750 align:start position:0%
it balanced the lightweight proxy can
actually<00:23:31.200><c> intercept</c><00:23:31.679><c> that</c><00:23:31.980><c> and</c><00:23:32.520><c> the</c><00:23:32.640><c> light</c>

00:23:32.750 --> 00:23:32.760 align:start position:0%
actually intercept that and the light
 

00:23:32.760 --> 00:23:35.270 align:start position:0%
actually intercept that and the light
web<00:23:32.940><c> proxy</c><00:23:33.480><c> connects</c><00:23:34.260><c> to</c><00:23:34.440><c> the</c><00:23:34.679><c> light</c><00:23:34.860><c> client</c>

00:23:35.270 --> 00:23:35.280 align:start position:0%
web proxy connects to the light client
 

00:23:35.280 --> 00:23:39.110 align:start position:0%
web proxy connects to the light client
Network<00:23:35.640><c> to</c><00:23:36.179><c> keep</c><00:23:36.419><c> track</c><00:23:37.080><c> of</c><00:23:37.440><c> the</c><00:23:37.679><c> head</c><00:23:37.799><c> of</c><00:23:38.400><c> the</c>

00:23:39.110 --> 00:23:39.120 align:start position:0%
Network to keep track of the head of the
 

00:23:39.120 --> 00:23:42.169 align:start position:0%
Network to keep track of the head of the
chained<00:23:39.900><c> right</c><00:23:40.020><c> now</c><00:23:40.200><c> or</c><00:23:40.559><c> the</c><00:23:40.740><c> state</c><00:23:40.919><c> right</c><00:23:41.460><c> and</c>

00:23:42.169 --> 00:23:42.179 align:start position:0%
chained right now or the state right and
 

00:23:42.179 --> 00:23:44.330 align:start position:0%
chained right now or the state right and
then<00:23:42.299><c> it</c><00:23:42.480><c> and</c><00:23:42.960><c> then</c><00:23:43.200><c> then</c><00:23:43.380><c> it</c><00:23:43.620><c> requests</c><00:23:43.980><c> a</c><00:23:44.100><c> get</c>

00:23:44.330 --> 00:23:44.340 align:start position:0%
then it and then then it requests a get
 

00:23:44.340 --> 00:23:47.330 align:start position:0%
then it and then then it requests a get
proof<00:23:44.760><c> separately</c><00:23:45.419><c> from</c><00:23:46.320><c> any</c><00:23:46.559><c> of</c><00:23:46.740><c> your</c><00:23:46.860><c> not</c>

00:23:47.330 --> 00:23:47.340 align:start position:0%
proof separately from any of your not
 

00:23:47.340 --> 00:23:49.330 align:start position:0%
proof separately from any of your not
providers<00:23:47.760><c> API</c><00:23:48.299><c> providers</c>

00:23:49.330 --> 00:23:49.340 align:start position:0%
providers API providers
 

00:23:49.340 --> 00:23:51.890 align:start position:0%
providers API providers
to<00:23:50.340><c> check</c><00:23:50.520><c> the</c><00:23:50.760><c> state</c><00:23:50.880><c> route</c><00:23:51.179><c> against</c><00:23:51.600><c> the</c>

00:23:51.890 --> 00:23:51.900 align:start position:0%
to check the state route against the
 

00:23:51.900 --> 00:23:55.310 align:start position:0%
to check the state route against the
balance<00:23:52.140><c> that</c><00:23:52.320><c> is</c><00:23:52.440><c> supplied</c><00:23:52.799><c> so</c><00:23:53.640><c> now</c><00:23:54.080><c> if</c><00:23:55.080><c> let's</c>

00:23:55.310 --> 00:23:55.320 align:start position:0%
balance that is supplied so now if let's
 

00:23:55.320 --> 00:23:58.010 align:start position:0%
balance that is supplied so now if let's
say<00:23:55.500><c> infuria</c><00:23:56.340><c> you</c><00:23:56.580><c> use</c><00:23:56.760><c> metamask</c><00:23:57.179><c> within</c><00:23:57.600><c> fura</c>

00:23:58.010 --> 00:23:58.020 align:start position:0%
say infuria you use metamask within fura
 

00:23:58.020 --> 00:23:59.750 align:start position:0%
say infuria you use metamask within fura
and<00:23:58.440><c> if</c><00:23:58.559><c> inferior</c><00:23:59.039><c> comes</c><00:23:59.340><c> back</c><00:23:59.400><c> with</c><00:23:59.640><c> a</c>

00:23:59.750 --> 00:23:59.760 align:start position:0%
and if inferior comes back with a
 

00:23:59.760 --> 00:24:01.610 align:start position:0%
and if inferior comes back with a
balance<00:24:00.120><c> your</c><00:24:00.659><c> light</c><00:24:00.900><c> web</c><00:24:01.140><c> proxy</c><00:24:01.500><c> can</c>

00:24:01.610 --> 00:24:01.620 align:start position:0%
balance your light web proxy can
 

00:24:01.620 --> 00:24:03.409 align:start position:0%
balance your light web proxy can
actually<00:24:01.799><c> verify</c><00:24:02.280><c> whether</c><00:24:02.640><c> it</c><00:24:02.820><c> is</c><00:24:03.000><c> true</c><00:24:03.179><c> or</c>

00:24:03.409 --> 00:24:03.419 align:start position:0%
actually verify whether it is true or
 

00:24:03.419 --> 00:24:05.510 align:start position:0%
actually verify whether it is true or
not<00:24:03.539><c> whether</c><00:24:04.020><c> whether</c><00:24:04.559><c> that</c><00:24:05.039><c> balance</c><00:24:05.400><c> is</c>

00:24:05.510 --> 00:24:05.520 align:start position:0%
not whether whether that balance is
 

00:24:05.520 --> 00:24:07.669 align:start position:0%
not whether whether that balance is
correct<00:24:05.820><c> or</c><00:24:05.940><c> not</c><00:24:06.539><c> so</c><00:24:06.960><c> there</c><00:24:07.140><c> are</c><00:24:07.260><c> all</c><00:24:07.500><c> these</c>

00:24:07.669 --> 00:24:07.679 align:start position:0%
correct or not so there are all these
 

00:24:07.679 --> 00:24:09.529 align:start position:0%
correct or not so there are all these
things<00:24:07.919><c> that</c><00:24:08.220><c> that</c><00:24:08.400><c> can</c><00:24:08.640><c> be</c><00:24:08.760><c> done</c><00:24:08.940><c> to</c><00:24:09.179><c> improve</c>

00:24:09.529 --> 00:24:09.539 align:start position:0%
things that that can be done to improve
 

00:24:09.539 --> 00:24:10.850 align:start position:0%
things that that can be done to improve
the<00:24:09.659><c> security</c><00:24:09.840><c> and</c><00:24:10.200><c> health</c><00:24:10.380><c> of</c><00:24:10.559><c> the</c><00:24:10.679><c> network</c>

00:24:10.850 --> 00:24:10.860 align:start position:0%
the security and health of the network
 

00:24:10.860 --> 00:24:13.850 align:start position:0%
the security and health of the network
that<00:24:11.220><c> don't</c><00:24:11.460><c> only</c><00:24:11.940><c> mean</c><00:24:12.620><c> validating</c><00:24:13.620><c> and</c>

00:24:13.850 --> 00:24:13.860 align:start position:0%
that don't only mean validating and
 

00:24:13.860 --> 00:24:14.990 align:start position:0%
that don't only mean validating and
staking<00:24:14.100><c> there</c><00:24:14.400><c> are</c><00:24:14.520><c> things</c><00:24:14.700><c> that</c>

00:24:14.990 --> 00:24:15.000 align:start position:0%
staking there are things that
 

00:24:15.000 --> 00:24:17.570 align:start position:0%
staking there are things that
individuals<00:24:15.480><c> can</c><00:24:15.780><c> do</c><00:24:15.960><c> on</c><00:24:16.559><c> their</c><00:24:16.740><c> own</c><00:24:16.860><c> to</c>

00:24:17.570 --> 00:24:17.580 align:start position:0%
individuals can do on their own to
 

00:24:17.580 --> 00:24:18.950 align:start position:0%
individuals can do on their own to
improve<00:24:17.880><c> the</c><00:24:18.059><c> the</c><00:24:18.299><c> secure</c><00:24:18.659><c> their</c><00:24:18.840><c> own</c>

00:24:18.950 --> 00:24:18.960 align:start position:0%
improve the the secure their own
 

00:24:18.960 --> 00:24:21.710 align:start position:0%
improve the the secure their own
security<00:24:19.200><c> the</c><00:24:19.799><c> security</c><00:24:20.039><c> and</c><00:24:20.580><c> and</c><00:24:20.760><c> Trust</c><00:24:21.120><c> in</c>

00:24:21.710 --> 00:24:21.720 align:start position:0%
security the security and and Trust in
 

00:24:21.720 --> 00:24:24.350 align:start position:0%
security the security and and Trust in
the<00:24:21.840><c> in</c><00:24:22.080><c> the</c><00:24:22.559><c> balance</c><00:24:22.860><c> that</c><00:24:23.100><c> they</c><00:24:23.280><c> see</c><00:24:23.460><c> in</c><00:24:24.240><c> the</c>

00:24:24.350 --> 00:24:24.360 align:start position:0%
the in the balance that they see in the
 

00:24:24.360 --> 00:24:26.510 align:start position:0%
the in the balance that they see in the
metamask<00:24:24.720><c> wallet</c><00:24:25.200><c> and</c><00:24:26.039><c> these</c><00:24:26.220><c> are</c><00:24:26.340><c> things</c>

00:24:26.510 --> 00:24:26.520 align:start position:0%
metamask wallet and these are things
 

00:24:26.520 --> 00:24:30.169 align:start position:0%
metamask wallet and these are things
that<00:24:26.700><c> are</c><00:24:26.880><c> possible</c><00:24:27.179><c> now</c><00:24:27.419><c> right</c><00:24:27.900><c> now</c><00:24:28.140><c> so</c><00:24:29.179><c> on</c>

00:24:30.169 --> 00:24:30.179 align:start position:0%
that are possible now right now so on
 

00:24:30.179 --> 00:24:32.510 align:start position:0%
that are possible now right now so on
that<00:24:30.299><c> note</c><00:24:30.480><c> I</c><00:24:30.960><c> would</c><00:24:31.080><c> also</c><00:24:31.260><c> like</c><00:24:31.380><c> to</c><00:24:31.559><c> say</c><00:24:31.860><c> my</c>

00:24:32.510 --> 00:24:32.520 align:start position:0%
that note I would also like to say my
 

00:24:32.520 --> 00:24:33.950 align:start position:0%
that note I would also like to say my
colleague<00:24:32.760><c> Eaton</c><00:24:33.179><c> is</c><00:24:33.419><c> going</c><00:24:33.539><c> to</c><00:24:33.720><c> present</c>

00:24:33.950 --> 00:24:33.960 align:start position:0%
colleague Eaton is going to present
 

00:24:33.960 --> 00:24:35.810 align:start position:0%
colleague Eaton is going to present
about<00:24:34.140><c> the</c><00:24:34.440><c> like</c><00:24:34.559><c> Clans</c><00:24:34.919><c> tomorrow</c><00:24:35.159><c> so</c><00:24:35.580><c> if</c><00:24:35.700><c> you</c>

00:24:35.810 --> 00:24:35.820 align:start position:0%
about the like Clans tomorrow so if you
 

00:24:35.820 --> 00:24:37.730 align:start position:0%
about the like Clans tomorrow so if you
are<00:24:35.880><c> interested</c><00:24:36.299><c> in</c><00:24:36.720><c> in</c><00:24:36.900><c> the</c><00:24:37.080><c> like</c><00:24:37.200><c> client</c><00:24:37.559><c> and</c>

00:24:37.730 --> 00:24:37.740 align:start position:0%
are interested in in the like client and
 

00:24:37.740 --> 00:24:40.549 align:start position:0%
are interested in in the like client and
the<00:24:37.860><c> like</c><00:24:37.980><c> client</c><00:24:38.340><c> proxy</c><00:24:38.880><c> please</c><00:24:39.780><c> do</c><00:24:40.080><c> make</c>

00:24:40.549 --> 00:24:40.559 align:start position:0%
the like client proxy please do make
 

00:24:40.559 --> 00:24:43.070 align:start position:0%
the like client proxy please do make
sure<00:24:40.740><c> you</c><00:24:40.980><c> you</c><00:24:41.159><c> attend</c><00:24:41.460><c> his</c><00:24:41.640><c> talk</c><00:24:41.880><c> it's</c><00:24:42.840><c> quite</c>

00:24:43.070 --> 00:24:43.080 align:start position:0%
sure you you attend his talk it's quite
 

00:24:43.080 --> 00:24:45.310 align:start position:0%
sure you you attend his talk it's quite
fascinating<00:24:43.500><c> to</c><00:24:43.860><c> see</c><00:24:43.980><c> the</c><00:24:44.280><c> actual</c>

00:24:45.310 --> 00:24:45.320 align:start position:0%
fascinating to see the actual
 

00:24:45.320 --> 00:24:47.930 align:start position:0%
fascinating to see the actual
demo<00:24:46.320><c> as</c><00:24:46.440><c> well</c><00:24:46.559><c> if</c><00:24:46.740><c> you</c><00:24:46.860><c> can</c><00:24:46.980><c> show</c><00:24:47.159><c> that</c>

00:24:47.930 --> 00:24:47.940 align:start position:0%
demo as well if you can show that
 

00:24:47.940 --> 00:24:51.950 align:start position:0%
demo as well if you can show that
and<00:24:48.720><c> finally</c><00:24:49.020><c> in</c><00:24:49.380><c> conclusion</c><00:24:49.799><c> I'd</c><00:24:50.400><c> say</c><00:24:50.960><c> the</c>

00:24:51.950 --> 00:24:51.960 align:start position:0%
and finally in conclusion I'd say the
 

00:24:51.960 --> 00:24:53.630 align:start position:0%
and finally in conclusion I'd say the
client<00:24:52.260><c> experience</c><00:24:52.679><c> or</c><00:24:52.919><c> evolution</c><00:24:53.220><c> of</c><00:24:53.460><c> the</c>

00:24:53.630 --> 00:24:53.640 align:start position:0%
client experience or evolution of the
 

00:24:53.640 --> 00:24:55.070 align:start position:0%
client experience or evolution of the
client<00:24:53.820><c> experience</c><00:24:54.240><c> is</c><00:24:54.419><c> being</c><00:24:54.659><c> pulled</c><00:24:54.960><c> in</c>

00:24:55.070 --> 00:24:55.080 align:start position:0%
client experience is being pulled in
 

00:24:55.080 --> 00:24:57.350 align:start position:0%
client experience is being pulled in
different<00:24:55.320><c> directions</c><00:24:55.580><c> right</c><00:24:56.580><c> more</c>

00:24:57.350 --> 00:24:57.360 align:start position:0%
different directions right more
 

00:24:57.360 --> 00:24:59.090 align:start position:0%
different directions right more
modularity<00:24:58.080><c> when</c><00:24:58.440><c> it</c><00:24:58.559><c> comes</c><00:24:58.740><c> to</c><00:24:58.919><c> node</c>

00:24:59.090 --> 00:24:59.100 align:start position:0%
modularity when it comes to node
 

00:24:59.100 --> 00:25:01.250 align:start position:0%
modularity when it comes to node
operators<00:24:59.580><c> and</c><00:24:59.820><c> simplicity</c><00:25:00.299><c> when</c><00:25:00.960><c> it</c><00:25:01.140><c> comes</c>

00:25:01.250 --> 00:25:01.260 align:start position:0%
operators and simplicity when it comes
 

00:25:01.260 --> 00:25:03.230 align:start position:0%
operators and simplicity when it comes
to<00:25:01.440><c> individuals</c><00:25:01.919><c> so</c><00:25:02.159><c> it's</c><00:25:02.340><c> the</c><00:25:02.820><c> task</c><00:25:02.940><c> for</c>

00:25:03.230 --> 00:25:03.240 align:start position:0%
to individuals so it's the task for
 

00:25:03.240 --> 00:25:05.630 align:start position:0%
to individuals so it's the task for
client<00:25:03.480><c> teams</c><00:25:03.840><c> in</c><00:25:04.020><c> general</c><00:25:04.140><c> isn't</c><00:25:04.679><c> easy</c><00:25:04.919><c> to</c>

00:25:05.630 --> 00:25:05.640 align:start position:0%
client teams in general isn't easy to
 

00:25:05.640 --> 00:25:09.169 align:start position:0%
client teams in general isn't easy to
balance<00:25:06.120><c> these</c><00:25:06.480><c> priorities</c><00:25:06.840><c> but</c><00:25:07.679><c> I</c><00:25:07.860><c> think</c><00:25:08.179><c> I</c>

00:25:09.169 --> 00:25:09.179 align:start position:0%
balance these priorities but I think I
 

00:25:09.179 --> 00:25:10.789 align:start position:0%
balance these priorities but I think I
can<00:25:09.299><c> speak</c><00:25:09.419><c> on</c><00:25:09.600><c> behalf</c><00:25:09.900><c> of</c><00:25:10.020><c> nimbus</c><00:25:10.440><c> that</c><00:25:10.620><c> I</c>

00:25:10.789 --> 00:25:10.799 align:start position:0%
can speak on behalf of nimbus that I
 

00:25:10.799 --> 00:25:12.110 align:start position:0%
can speak on behalf of nimbus that I
think<00:25:10.919><c> for</c><00:25:11.039><c> from</c><00:25:11.220><c> a</c><00:25:11.400><c> nimbus</c><00:25:11.700><c> point</c><00:25:11.880><c> of</c><00:25:12.000><c> view</c>

00:25:12.110 --> 00:25:12.120 align:start position:0%
think for from a nimbus point of view
 

00:25:12.120 --> 00:25:13.789 align:start position:0%
think for from a nimbus point of view
there<00:25:12.780><c> are</c><00:25:12.900><c> certain</c><00:25:13.020><c> things</c><00:25:13.260><c> that</c><00:25:13.500><c> we</c><00:25:13.620><c> have</c>

00:25:13.789 --> 00:25:13.799 align:start position:0%
there are certain things that we have
 

00:25:13.799 --> 00:25:16.549 align:start position:0%
there are certain things that we have
planned<00:25:14.220><c> which</c><00:25:14.640><c> should</c><00:25:15.179><c> hopefully</c><00:25:15.600><c> address</c><00:25:15.840><c> a</c>

00:25:16.549 --> 00:25:16.559 align:start position:0%
planned which should hopefully address a
 

00:25:16.559 --> 00:25:18.710 align:start position:0%
planned which should hopefully address a
number<00:25:16.799><c> of</c><00:25:16.980><c> these</c><00:25:17.340><c> things</c><00:25:17.520><c> for</c><00:25:18.179><c> both</c><00:25:18.360><c> these</c>

00:25:18.710 --> 00:25:18.720 align:start position:0%
number of these things for both these
 

00:25:18.720 --> 00:25:21.409 align:start position:0%
number of these things for both these
major<00:25:18.840><c> segments</c><00:25:19.440><c> of</c><00:25:20.100><c> validators</c><00:25:20.640><c> because</c>

00:25:21.409 --> 00:25:21.419 align:start position:0%
major segments of validators because
 

00:25:21.419 --> 00:25:23.090 align:start position:0%
major segments of validators because
both<00:25:21.720><c> of</c><00:25:21.840><c> them</c><00:25:21.960><c> are</c><00:25:22.260><c> equally</c><00:25:22.500><c> important</c><00:25:22.919><c> at</c>

00:25:23.090 --> 00:25:23.100 align:start position:0%
both of them are equally important at
 

00:25:23.100 --> 00:25:24.769 align:start position:0%
both of them are equally important at
this<00:25:23.280><c> stage</c>

00:25:24.769 --> 00:25:24.779 align:start position:0%
this stage
 

00:25:24.779 --> 00:25:27.529 align:start position:0%
this stage
on<00:25:25.320><c> that</c><00:25:25.500><c> note</c><00:25:25.620><c> I'll</c><00:25:25.860><c> conclude</c><00:25:26.279><c> I'm</c><00:25:27.000><c> happy</c><00:25:27.360><c> to</c>

00:25:27.529 --> 00:25:27.539 align:start position:0%
on that note I'll conclude I'm happy to
 

00:25:27.539 --> 00:25:30.289 align:start position:0%
on that note I'll conclude I'm happy to
stay<00:25:27.779><c> in</c><00:25:27.900><c> touch</c><00:25:28.080><c> my</c><00:25:28.980><c> Twitter</c><00:25:29.279><c> is</c><00:25:29.640><c> lift</c><00:25:30.000><c> lines</c>

00:25:30.289 --> 00:25:30.299 align:start position:0%
stay in touch my Twitter is lift lines
 

00:25:30.299 --> 00:25:33.310 align:start position:0%
stay in touch my Twitter is lift lines
and<00:25:31.020><c> you</c><00:25:31.200><c> can</c><00:25:31.320><c> also</c><00:25:31.679><c> reach</c><00:25:31.980><c> out</c><00:25:32.039><c> to</c><00:25:32.220><c> me</c>

00:25:33.310 --> 00:25:33.320 align:start position:0%
and you can also reach out to me
 

00:25:33.320 --> 00:25:36.230 align:start position:0%
and you can also reach out to me
via<00:25:34.320><c> Telegram</c><00:25:34.740><c> and</c><00:25:34.980><c> other</c><00:25:35.159><c> other</c><00:25:35.520><c> channels</c>

00:25:36.230 --> 00:25:36.240 align:start position:0%
via Telegram and other other channels
 

00:25:36.240 --> 00:25:38.670 align:start position:0%
via Telegram and other other channels
using<00:25:36.659><c> the</c><00:25:36.720><c> same</c><00:25:36.840><c> handle</c><00:25:37.260><c> thank</c><00:25:37.860><c> you</c>

00:25:38.670 --> 00:25:38.680 align:start position:0%
using the same handle thank you
 

00:25:38.680 --> 00:25:45.529 align:start position:0%
using the same handle thank you
[Applause]

00:25:45.529 --> 00:25:45.539 align:start position:0%
[Applause]
 

00:25:45.539 --> 00:25:52.130 align:start position:0%
[Applause]
any<00:25:45.960><c> questions</c>

00:25:52.130 --> 00:25:52.140 align:start position:0%
 
 

00:25:52.140 --> 00:26:08.690 align:start position:0%
 
second<00:25:53.039><c> row</c><00:25:53.340><c> oh</c>

00:26:08.690 --> 00:26:08.700 align:start position:0%
 
 

00:26:08.700 --> 00:26:13.490 align:start position:0%
 
today

00:26:13.490 --> 00:26:13.500 align:start position:0%
 
 

00:26:13.500 --> 00:26:14.870 align:start position:0%
 
you<00:26:13.980><c> know</c><00:26:14.039><c> you're</c><00:26:14.159><c> close</c><00:26:14.400><c> enough</c><00:26:14.520><c> you</c><00:26:14.760><c> could</c>

00:26:14.870 --> 00:26:14.880 align:start position:0%
you know you're close enough you could
 

00:26:14.880 --> 00:26:16.310 align:start position:0%
you know you're close enough you could
probably<00:26:15.059><c> yell</c><00:26:15.299><c> if</c><00:26:15.480><c> you</c><00:26:15.600><c> want</c><00:26:15.720><c> hello</c><00:26:16.320><c> hello</c>

00:26:16.310 --> 00:26:16.320 align:start position:0%
probably yell if you want hello hello
 

00:26:16.320 --> 00:26:18.350 align:start position:0%
probably yell if you want hello hello
thanks<00:26:16.919><c> for</c><00:26:17.159><c> the</c><00:26:17.279><c> sharing</c>

00:26:18.350 --> 00:26:18.360 align:start position:0%
thanks for the sharing
 

00:26:18.360 --> 00:26:20.289 align:start position:0%
thanks for the sharing
um<00:26:18.419><c> I'm</c><00:26:18.720><c> just</c><00:26:18.900><c> curious</c><00:26:19.740><c> um</c>

00:26:20.289 --> 00:26:20.299 align:start position:0%
um I'm just curious um
 

00:26:20.299 --> 00:26:24.110 align:start position:0%
um I'm just curious um
for<00:26:21.299><c> the</c><00:26:21.480><c> better</c><00:26:21.720><c> user</c><00:26:22.440><c> experience</c><00:26:22.940><c> were</c><00:26:23.940><c> you</c>

00:26:24.110 --> 00:26:24.120 align:start position:0%
for the better user experience were you
 

00:26:24.120 --> 00:26:26.210 align:start position:0%
for the better user experience were you
like<00:26:24.539><c> thinking</c><00:26:25.020><c> about</c>

00:26:26.210 --> 00:26:26.220 align:start position:0%
like thinking about
 

00:26:26.220 --> 00:26:29.330 align:start position:0%
like thinking about
provide<00:26:27.120><c> infrastructure</c><00:26:27.779><c> skull</c><00:26:28.440><c> to</c><00:26:28.860><c> set</c><00:26:29.100><c> up</c>

00:26:29.330 --> 00:26:29.340 align:start position:0%
provide infrastructure skull to set up
 

00:26:29.340 --> 00:26:30.409 align:start position:0%
provide infrastructure skull to set up
the

00:26:30.409 --> 00:26:30.419 align:start position:0%
the
 

00:26:30.419 --> 00:26:34.029 align:start position:0%
the
the<00:26:30.900><c> infra</c><00:26:31.500><c> like</c><00:26:31.980><c> telephone</c><00:26:32.700><c> or</c>

00:26:34.029 --> 00:26:34.039 align:start position:0%
the infra like telephone or
 

00:26:34.039 --> 00:26:38.510 align:start position:0%
the infra like telephone or
Hampshire<00:26:35.039><c> this</c><00:26:35.640><c> kind</c><00:26:35.760><c> of</c><00:26:35.880><c> thing</c>

00:26:38.510 --> 00:26:38.520 align:start position:0%
 
 

00:26:38.520 --> 00:26:40.310 align:start position:0%
 
so<00:26:39.000><c> if</c><00:26:39.179><c> I</c><00:26:39.360><c> understand</c><00:26:39.480><c> correctly</c><00:26:39.960><c> I</c><00:26:40.080><c> think</c><00:26:40.200><c> are</c>

00:26:40.310 --> 00:26:40.320 align:start position:0%
so if I understand correctly I think are
 

00:26:40.320 --> 00:26:42.710 align:start position:0%
so if I understand correctly I think are
you<00:26:40.440><c> asking</c><00:26:40.740><c> whether</c><00:26:41.100><c> or</c><00:26:41.340><c> not</c>

00:26:42.710 --> 00:26:42.720 align:start position:0%
you asking whether or not
 

00:26:42.720 --> 00:26:43.970 align:start position:0%
you asking whether or not
um

00:26:43.970 --> 00:26:43.980 align:start position:0%
um
 

00:26:43.980 --> 00:26:45.950 align:start position:0%
um
numbers<00:26:44.400><c> would</c><00:26:44.760><c> Supply</c><00:26:45.000><c> infrastructure</c><00:26:45.779><c> is</c>

00:26:45.950 --> 00:26:45.960 align:start position:0%
numbers would Supply infrastructure is
 

00:26:45.960 --> 00:26:49.130 align:start position:0%
numbers would Supply infrastructure is
that<00:26:46.140><c> is</c><00:26:46.320><c> that</c><00:26:46.500><c> what</c><00:26:46.620><c> you're</c><00:26:46.740><c> asking</c><00:26:46.860><c> sorry</c>

00:26:49.130 --> 00:26:49.140 align:start position:0%
that is that what you're asking sorry
 

00:26:49.140 --> 00:26:52.010 align:start position:0%
that is that what you're asking sorry
infrastructure<00:26:49.980><c> is</c><00:26:50.580><c> code</c>

00:26:52.010 --> 00:26:52.020 align:start position:0%
infrastructure is code
 

00:26:52.020 --> 00:26:54.950 align:start position:0%
infrastructure is code
right<00:26:52.580><c> I</c><00:26:53.580><c> think</c>

00:26:54.950 --> 00:26:54.960 align:start position:0%
right I think
 

00:26:54.960 --> 00:26:57.710 align:start position:0%
right I think
the<00:26:55.679><c> primary</c><00:26:56.039><c> goal</c><00:26:56.400><c> for</c><00:26:56.580><c> us</c><00:26:56.700><c> at</c><00:26:57.000><c> the</c><00:26:57.120><c> moment</c><00:26:57.240><c> is</c>

00:26:57.710 --> 00:26:57.720 align:start position:0%
the primary goal for us at the moment is
 

00:26:57.720 --> 00:26:59.510 align:start position:0%
the primary goal for us at the moment is
to<00:26:57.960><c> make</c><00:26:58.200><c> sure</c><00:26:58.320><c> that</c><00:26:58.559><c> we</c><00:26:58.740><c> can</c><00:26:58.860><c> take</c><00:26:58.980><c> the</c><00:26:59.220><c> boxes</c>

00:26:59.510 --> 00:26:59.520 align:start position:0%
to make sure that we can take the boxes
 

00:26:59.520 --> 00:27:00.950 align:start position:0%
to make sure that we can take the boxes
that<00:26:59.760><c> we</c><00:26:59.880><c> have</c><00:27:00.000><c> planned</c><00:27:00.299><c> on</c><00:27:00.480><c> the</c><00:27:00.600><c> roadmap</c>

00:27:00.950 --> 00:27:00.960 align:start position:0%
that we have planned on the roadmap
 

00:27:00.960 --> 00:27:03.769 align:start position:0%
that we have planned on the roadmap
right<00:27:01.380><c> so</c><00:27:01.980><c> these</c><00:27:02.700><c> are</c><00:27:02.820><c> these</c><00:27:03.240><c> are</c><00:27:03.299><c> things</c><00:27:03.539><c> that</c>

00:27:03.769 --> 00:27:03.779 align:start position:0%
right so these are these are things that
 

00:27:03.779 --> 00:27:05.630 align:start position:0%
right so these are these are things that
we<00:27:03.900><c> must</c><00:27:04.140><c> address</c><00:27:04.380><c> over</c><00:27:04.799><c> the</c><00:27:05.039><c> next</c><00:27:05.159><c> six</c><00:27:05.460><c> to</c>

00:27:05.630 --> 00:27:05.640 align:start position:0%
we must address over the next six to
 

00:27:05.640 --> 00:27:06.710 align:start position:0%
we must address over the next six to
eight<00:27:05.820><c> months</c>

00:27:06.710 --> 00:27:06.720 align:start position:0%
eight months
 

00:27:06.720 --> 00:27:08.269 align:start position:0%
eight months
um

00:27:08.269 --> 00:27:08.279 align:start position:0%
um
 

00:27:08.279 --> 00:27:10.010 align:start position:0%
um
um<00:27:08.340><c> it</c><00:27:08.940><c> could</c><00:27:09.240><c> be</c><00:27:09.360><c> one</c><00:27:09.539><c> of</c><00:27:09.659><c> the</c><00:27:09.720><c> things</c><00:27:09.840><c> we</c>

00:27:10.010 --> 00:27:10.020 align:start position:0%
um it could be one of the things we
 

00:27:10.020 --> 00:27:13.190 align:start position:0%
um it could be one of the things we
could<00:27:10.200><c> consider</c><00:27:10.620><c> absolutely</c><00:27:11.460><c> but</c><00:27:12.000><c> uh</c><00:27:12.900><c> yeah</c><00:27:13.080><c> I</c>

00:27:13.190 --> 00:27:13.200 align:start position:0%
could consider absolutely but uh yeah I
 

00:27:13.200 --> 00:27:15.110 align:start position:0%
could consider absolutely but uh yeah I
wouldn't<00:27:13.380><c> say</c><00:27:13.620><c> more</c><00:27:13.799><c> about</c><00:27:14.039><c> that</c><00:27:14.340><c> than</c><00:27:14.880><c> that</c>

00:27:15.110 --> 00:27:15.120 align:start position:0%
wouldn't say more about that than that
 

00:27:15.120 --> 00:27:17.690 align:start position:0%
wouldn't say more about that than that
at<00:27:15.360><c> the</c><00:27:15.480><c> moment</c><00:27:15.659><c> I</c><00:27:16.440><c> think</c><00:27:16.620><c> for</c><00:27:17.279><c> us</c><00:27:17.400><c> it's</c>

00:27:17.690 --> 00:27:17.700 align:start position:0%
at the moment I think for us it's
 

00:27:17.700 --> 00:27:20.450 align:start position:0%
at the moment I think for us it's
important<00:27:18.059><c> that</c><00:27:18.960><c> um</c>

00:27:20.450 --> 00:27:20.460 align:start position:0%
important that um
 

00:27:20.460 --> 00:27:23.269 align:start position:0%
important that um
the<00:27:21.419><c> users</c><00:27:21.960><c> who</c><00:27:22.260><c> end</c><00:27:22.500><c> up</c><00:27:22.620><c> using</c><00:27:22.919><c> Nimbus</c>

00:27:23.269 --> 00:27:23.279 align:start position:0%
the users who end up using Nimbus
 

00:27:23.279 --> 00:27:25.610 align:start position:0%
the users who end up using Nimbus
whether<00:27:23.580><c> that's</c><00:27:23.880><c> directly</c><00:27:24.240><c> using</c><00:27:24.720><c> Nimbus</c><00:27:25.260><c> as</c>

00:27:25.610 --> 00:27:25.620 align:start position:0%
whether that's directly using Nimbus as
 

00:27:25.620 --> 00:27:27.649 align:start position:0%
whether that's directly using Nimbus as
a<00:27:25.740><c> validator</c><00:27:26.159><c> that</c><00:27:26.640><c> they</c><00:27:26.820><c> set</c><00:27:27.000><c> up</c><00:27:27.179><c> on</c><00:27:27.480><c> their</c>

00:27:27.649 --> 00:27:27.659 align:start position:0%
a validator that they set up on their
 

00:27:27.659 --> 00:27:29.690 align:start position:0%
a validator that they set up on their
own<00:27:27.779><c> home</c><00:27:28.020><c> environment</c><00:27:28.679><c> whatever</c><00:27:29.100><c> that</c><00:27:29.400><c> looks</c>

00:27:29.690 --> 00:27:29.700 align:start position:0%
own home environment whatever that looks
 

00:27:29.700 --> 00:27:34.070 align:start position:0%
own home environment whatever that looks
like<00:27:29.840><c> or</c><00:27:30.840><c> use</c><00:27:31.140><c> rocket</c><00:27:32.100><c> pool</c><00:27:32.279><c> Stadium</c><00:27:32.880><c> dap</c><00:27:33.840><c> node</c>

00:27:34.070 --> 00:27:34.080 align:start position:0%
like or use rocket pool Stadium dap node
 

00:27:34.080 --> 00:27:36.769 align:start position:0%
like or use rocket pool Stadium dap node
or<00:27:34.200><c> any</c><00:27:34.380><c> other</c><00:27:34.559><c> Hardware</c><00:27:34.860><c> providers</c><00:27:35.700><c> to</c><00:27:36.240><c> set</c>

00:27:36.769 --> 00:27:36.779 align:start position:0%
or any other Hardware providers to set
 

00:27:36.779 --> 00:27:39.830 align:start position:0%
or any other Hardware providers to set
up<00:27:36.900><c> the</c><00:27:37.080><c> client</c><00:27:37.400><c> or</c><00:27:38.400><c> have</c>

00:27:39.830 --> 00:27:39.840 align:start position:0%
up the client or have
 

00:27:39.840 --> 00:27:42.049 align:start position:0%
up the client or have
you<00:27:40.500><c> know</c><00:27:40.679><c> all</c><00:27:41.279><c> used</c><00:27:41.520><c> as</c><00:27:41.700><c> part</c><00:27:41.940><c> of</c>

00:27:42.049 --> 00:27:42.059 align:start position:0%
you know all used as part of
 

00:27:42.059 --> 00:27:43.970 align:start position:0%
you know all used as part of
professional<00:27:42.480><c> node</c><00:27:42.840><c> operations</c><00:27:43.140><c> at</c><00:27:43.679><c> scale</c>

00:27:43.970 --> 00:27:43.980 align:start position:0%
professional node operations at scale
 

00:27:43.980 --> 00:27:46.010 align:start position:0%
professional node operations at scale
that<00:27:44.640><c> they</c><00:27:44.760><c> have</c><00:27:44.880><c> the</c><00:27:45.059><c> flexibility</c><00:27:45.419><c> to</c><00:27:45.720><c> run</c><00:27:45.840><c> it</c>

00:27:46.010 --> 00:27:46.020 align:start position:0%
that they have the flexibility to run it
 

00:27:46.020 --> 00:27:48.470 align:start position:0%
that they have the flexibility to run it
the<00:27:46.200><c> way</c><00:27:46.380><c> they</c><00:27:46.559><c> like</c><00:27:46.679><c> it</c><00:27:46.919><c> right</c><00:27:47.279><c> so</c><00:27:47.760><c> I</c><00:27:48.360><c> don't</c>

00:27:48.470 --> 00:27:48.480 align:start position:0%
the way they like it right so I don't
 

00:27:48.480 --> 00:27:49.970 align:start position:0%
the way they like it right so I don't
think<00:27:48.600><c> we'd</c><00:27:48.840><c> like</c><00:27:48.960><c> to</c><00:27:49.080><c> mandate</c><00:27:49.440><c> anything</c><00:27:49.679><c> in</c>

00:27:49.970 --> 00:27:49.980 align:start position:0%
think we'd like to mandate anything in
 

00:27:49.980 --> 00:27:52.490 align:start position:0%
think we'd like to mandate anything in
particular<00:27:50.539><c> but</c><00:27:51.539><c> the</c><00:27:51.659><c> guide</c><00:27:52.080><c> does</c><00:27:52.320><c> cover</c>

00:27:52.490 --> 00:27:52.500 align:start position:0%
particular but the guide does cover
 

00:27:52.500 --> 00:27:54.529 align:start position:0%
particular but the guide does cover
different<00:27:52.799><c> scenarios</c>

00:27:54.529 --> 00:27:54.539 align:start position:0%
different scenarios
 

00:27:54.539 --> 00:27:56.510 align:start position:0%
different scenarios
um<00:27:54.659><c> depending</c><00:27:55.140><c> on</c><00:27:55.260><c> who</c><00:27:55.440><c> who</c><00:27:55.500><c> wants</c><00:27:55.980><c> to</c><00:27:56.100><c> set</c><00:27:56.340><c> up</c>

00:27:56.510 --> 00:27:56.520 align:start position:0%
um depending on who who wants to set up
 

00:27:56.520 --> 00:27:58.909 align:start position:0%
um depending on who who wants to set up
in<00:27:57.179><c> different</c><00:27:57.299><c> ways</c>

00:27:58.909 --> 00:27:58.919 align:start position:0%
in different ways
 

00:27:58.919 --> 00:28:02.520 align:start position:0%
in different ways
great<00:27:59.400><c> thank</c><00:27:59.820><c> you</c><00:27:59.940><c> let's</c><00:28:00.600><c> uh</c>

00:28:02.520 --> 00:28:02.530 align:start position:0%
great thank you let's uh
 

00:28:02.530 --> 00:28:07.000 align:start position:0%
great thank you let's uh
[Applause]