WEBVTT Kind: captions Language: en 00:00:03.950 --> 00:00:07.969 align:start position:0% my<00:00:04.950> name<00:00:05.100> is<00:00:05.250> JK<00:00:06.090> I'm<00:00:06.450> the<00:00:07.019> operations<00:00:07.859> manager 00:00:07.969 --> 00:00:07.979 align:start position:0% my name is JK I'm the operations manager 00:00:07.979 --> 00:00:15.169 align:start position:0% my name is JK I'm the operations manager at<00:00:08.550> a<00:00:08.660> steak<00:00:09.660> fish<00:00:12.349> Thank<00:00:13.349> You<00:00:13.820> steak<00:00:14.820> fish<00:00:14.999> is 00:00:15.169 --> 00:00:15.179 align:start position:0% at a steak fish Thank You steak fish is 00:00:15.179 --> 00:00:17.120 align:start position:0% at a steak fish Thank You steak fish is a<00:00:15.209> validator<00:00:15.900> for<00:00:16.289> different<00:00:16.650> Priya<00:00:16.860> West 00:00:17.120 --> 00:00:17.130 align:start position:0% a validator for different Priya West 00:00:17.130 --> 00:00:19.609 align:start position:0% a validator for different Priya West block<00:00:17.340> chains<00:00:17.700> and<00:00:17.970> and<00:00:18.960> no<00:00:19.170> two<00:00:19.230> operators 00:00:19.609 --> 00:00:19.619 align:start position:0% block chains and and no two operators 00:00:19.619 --> 00:00:21.919 align:start position:0% block chains and and no two operators for<00:00:19.920> projects<00:00:20.730> that<00:00:20.760> use<00:00:21.060> staking<00:00:21.449> mechanisms 00:00:21.919 --> 00:00:21.929 align:start position:0% for projects that use staking mechanisms 00:00:21.929 --> 00:00:24.529 align:start position:0% for projects that use staking mechanisms I'll<00:00:22.050> get<00:00:22.230> into<00:00:22.380> that<00:00:22.470> a<00:00:22.590> bit<00:00:22.679> later<00:00:23.160> but<00:00:23.539> you 00:00:24.529 --> 00:00:24.539 align:start position:0% I'll get into that a bit later but you 00:00:24.539 --> 00:00:26.179 align:start position:0% I'll get into that a bit later but you know<00:00:24.630> we're<00:00:24.779> all<00:00:24.869> excited<00:00:25.170> for<00:00:25.349> a<00:00:25.470> dream<00:00:25.710> 2.0 00:00:26.179 --> 00:00:26.189 align:start position:0% know we're all excited for a dream 2.0 00:00:26.189 --> 00:00:29.210 align:start position:0% know we're all excited for a dream 2.0 POS<00:00:27.029> is<00:00:27.179> going<00:00:27.330> to<00:00:27.390> be<00:00:27.480> enabled<00:00:27.949> but<00:00:28.949> you<00:00:29.099> know 00:00:29.210 --> 00:00:29.220 align:start position:0% POS is going to be enabled but you know 00:00:29.220 --> 00:00:31.519 align:start position:0% POS is going to be enabled but you know there<00:00:29.820> have<00:00:30.000> been<00:00:30.029> plenty<00:00:30.539> of<00:00:30.689> other<00:00:30.839> POS 00:00:31.519 --> 00:00:31.529 align:start position:0% there have been plenty of other POS 00:00:31.529 --> 00:00:34.790 align:start position:0% there have been plenty of other POS protocols<00:00:32.120> that<00:00:33.120> have<00:00:33.180> been<00:00:33.900> in<00:00:34.080> operations 00:00:34.790 --> 00:00:34.800 align:start position:0% protocols that have been in operations 00:00:34.800 --> 00:00:37.400 align:start position:0% protocols that have been in operations for<00:00:35.460> a<00:00:35.490> year<00:00:35.789> or<00:00:36.000> even<00:00:36.270> or<00:00:36.780> slightly<00:00:37.079> less<00:00:37.350> than 00:00:37.400 --> 00:00:37.410 align:start position:0% for a year or even or slightly less than 00:00:37.410 --> 00:00:39.680 align:start position:0% for a year or even or slightly less than that<00:00:37.590> and<00:00:38.460> there<00:00:38.640> are<00:00:38.670> already<00:00:39.090> good<00:00:39.450> data 00:00:39.680 --> 00:00:39.690 align:start position:0% that and there are already good data 00:00:39.690 --> 00:00:42.350 align:start position:0% that and there are already good data points<00:00:40.079> to<00:00:40.200> take<00:00:40.559> from<00:00:40.800> there<00:00:41.010> and<00:00:41.360> having 00:00:42.350 --> 00:00:42.360 align:start position:0% points to take from there and having 00:00:42.360 --> 00:00:44.569 align:start position:0% points to take from there and having been<00:00:42.600> in<00:00:42.870> this<00:00:43.050> space<00:00:43.289> for<00:00:43.350> about<00:00:43.860> a<00:00:44.010> year<00:00:44.340> now 00:00:44.569 --> 00:00:44.579 align:start position:0% been in this space for about a year now 00:00:44.579 --> 00:00:47.299 align:start position:0% been in this space for about a year now and<00:00:45.149> a<00:00:45.329> bit<00:00:45.510> over<00:00:45.750> a<00:00:45.809> year<00:00:46.010> there's<00:00:47.010> plenty<00:00:47.280> of 00:00:47.299 --> 00:00:47.309 align:start position:0% and a bit over a year there's plenty of 00:00:47.309 --> 00:00:48.500 align:start position:0% and a bit over a year there's plenty of lessons<00:00:47.550> that<00:00:47.760> we've<00:00:47.969> learned<00:00:48.000> throughout 00:00:48.500 --> 00:00:48.510 align:start position:0% lessons that we've learned throughout 00:00:48.510 --> 00:00:51.380 align:start position:0% lessons that we've learned throughout the<00:00:48.719> way<00:00:48.870> throughout<00:00:49.559> our<00:00:50.010> our<00:00:50.670> operations 00:00:51.380 --> 00:00:51.390 align:start position:0% the way throughout our our operations 00:00:51.390 --> 00:00:53.029 align:start position:0% the way throughout our our operations and<00:00:51.539> we<00:00:51.719> wanted<00:00:52.230> to<00:00:52.320> share<00:00:52.530> a<00:00:52.590> few<00:00:52.859> of<00:00:52.890> those 00:00:53.029 --> 00:00:53.039 align:start position:0% and we wanted to share a few of those 00:00:53.039 --> 00:00:55.310 align:start position:0% and we wanted to share a few of those with<00:00:53.250> you<00:00:53.430> today<00:00:53.460> in<00:00:54.329> the<00:00:54.449> hopes<00:00:54.600> that<00:00:54.719> once 00:00:55.310 --> 00:00:55.320 align:start position:0% with you today in the hopes that once 00:00:55.320 --> 00:00:57.470 align:start position:0% with you today in the hopes that once eternam<00:00:55.920> 2.0<00:00:56.309> launches<00:00:56.730> we<00:00:57.120> don't<00:00:57.269> have 00:00:57.470 --> 00:00:57.480 align:start position:0% eternam 2.0 launches we don't have 00:00:57.480 --> 00:01:00.680 align:start position:0% eternam 2.0 launches we don't have similar<00:00:58.019> problems<00:00:58.559> we've<00:00:58.859> seen<00:00:59.190> on<00:00:59.460> other<00:00:59.789> POS 00:01:00.680 --> 00:01:00.690 align:start position:0% similar problems we've seen on other POS 00:01:00.690 --> 00:01:04.369 align:start position:0% similar problems we've seen on other POS protocols<00:01:02.269> so<00:01:03.269> just<00:01:03.899> a<00:01:03.989> very<00:01:04.019> short 00:01:04.369 --> 00:01:04.379 align:start position:0% protocols so just a very short 00:01:04.379 --> 00:01:06.170 align:start position:0% protocols so just a very short introduction<00:01:04.650> about<00:01:04.949> sake<00:01:05.250> fish<00:01:05.430> steak<00:01:06.030> which 00:01:06.170 --> 00:01:06.180 align:start position:0% introduction about sake fish steak which 00:01:06.180 --> 00:01:08.690 align:start position:0% introduction about sake fish steak which was<00:01:06.330> founded<00:01:06.630> by<00:01:06.780> auction<00:01:07.290> who<00:01:07.799> co-founded<00:01:08.100> f2 00:01:08.690 --> 00:01:08.700 align:start position:0% was founded by auction who co-founded f2 00:01:08.700 --> 00:01:10.780 align:start position:0% was founded by auction who co-founded f2 pool<00:01:08.880> which<00:01:09.720> is<00:01:09.900> one<00:01:10.049> of<00:01:10.140> the<00:01:10.229> of<00:01:10.320> course 00:01:10.780 --> 00:01:10.790 align:start position:0% pool which is one of the of course 00:01:10.790 --> 00:01:12.980 align:start position:0% pool which is one of the of course largest<00:01:11.790> Bitcoin<00:01:12.270> and<00:01:12.390> it<00:01:12.540> dairy<00:01:12.720> mining 00:01:12.980 --> 00:01:12.990 align:start position:0% largest Bitcoin and it dairy mining 00:01:12.990 --> 00:01:14.990 align:start position:0% largest Bitcoin and it dairy mining pools<00:01:13.170> and<00:01:13.460> you<00:01:14.460> know<00:01:14.549> he<00:01:14.700> wanted<00:01:14.939> to 00:01:14.990 --> 00:01:15.000 align:start position:0% pools and you know he wanted to 00:01:15.000 --> 00:01:16.280 align:start position:0% pools and you know he wanted to contribute<00:01:15.420> something<00:01:15.840> similar<00:01:16.140> in<00:01:16.259> the 00:01:16.280 --> 00:01:16.290 align:start position:0% contribute something similar in the 00:01:16.290 --> 00:01:18.080 align:start position:0% contribute something similar in the proof<00:01:16.500> of<00:01:16.619> stake<00:01:16.860> space<00:01:17.130> and<00:01:17.369> of<00:01:17.850> course 00:01:18.080 --> 00:01:18.090 align:start position:0% proof of stake space and of course 00:01:18.090 --> 00:01:19.969 align:start position:0% proof of stake space and of course naturally<00:01:18.509> dye<00:01:18.630> meant<00:01:18.960> creating<00:01:19.200> validators 00:01:19.969 --> 00:01:19.979 align:start position:0% naturally dye meant creating validators 00:01:19.979 --> 00:01:22.270 align:start position:0% naturally dye meant creating validators and<00:01:20.189> staking<00:01:20.430> pools<00:01:20.759> and<00:01:20.970> so<00:01:21.540> so<00:01:21.720> far<00:01:21.750> we<00:01:22.079> have 00:01:22.270 --> 00:01:22.280 align:start position:0% and staking pools and so so far we have 00:01:22.280 --> 00:01:25.670 align:start position:0% and staking pools and so so far we have validators<00:01:23.280> or<00:01:23.520> nodes<00:01:23.790> on<00:01:24.259> various<00:01:25.259> projects 00:01:25.670 --> 00:01:25.680 align:start position:0% validators or nodes on various projects 00:01:25.680 --> 00:01:28.310 align:start position:0% validators or nodes on various projects we<00:01:25.799> have<00:01:25.979> AOS<00:01:26.360> whereof<00:01:27.360> a<00:01:27.450> leader<00:01:27.869> on<00:01:27.990> B<00:01:28.229> owes 00:01:28.310 --> 00:01:28.320 align:start position:0% we have AOS whereof a leader on B owes 00:01:28.320 --> 00:01:31.160 align:start position:0% we have AOS whereof a leader on B owes cosmos<00:01:28.950> Tasos<00:01:29.400> lunette<00:01:29.970> work<00:01:30.150> Irish<00:01:30.810> Network 00:01:31.160 --> 00:01:31.170 align:start position:0% cosmos Tasos lunette work Irish Network 00:01:31.170 --> 00:01:33.649 align:start position:0% cosmos Tasos lunette work Irish Network boss<00:01:31.470> a<00:01:31.920> node<00:01:32.399> operator<00:01:32.790> for<00:01:33.090> a<00:01:33.119> chain<00:01:33.360> link<00:01:33.479> al 00:01:33.649 --> 00:01:33.659 align:start position:0% boss a node operator for a chain link al 00:01:33.659 --> 00:01:36.319 align:start position:0% boss a node operator for a chain link al grant<00:01:33.930> and<00:01:34.110> a<00:01:34.500> storage<00:01:35.250> node<00:01:35.280> provider<00:01:36.090> for 00:01:36.319 --> 00:01:36.329 align:start position:0% grant and a storage node provider for 00:01:36.329 --> 00:01:38.960 align:start position:0% grant and a storage node provider for storage<00:01:36.689> as<00:01:36.780> well<00:01:36.930> and<00:01:37.829> so<00:01:38.130> right<00:01:38.549> now<00:01:38.579> roughly 00:01:38.960 --> 00:01:38.970 align:start position:0% storage as well and so right now roughly 00:01:38.970 --> 00:01:41.179 align:start position:0% storage as well and so right now roughly we're<00:01:39.360> facilitating<00:01:39.720> around<00:01:40.500> 30<00:01:40.799> million 00:01:41.179 --> 00:01:41.189 align:start position:0% we're facilitating around 30 million 00:01:41.189 --> 00:01:47.810 align:start position:0% we're facilitating around 30 million dollars<00:01:41.490> in<00:01:41.790> stay<00:01:42.329> Keable<00:01:42.600> assets<00:01:45.920> so<00:01:46.920> first 00:01:47.810 --> 00:01:47.820 align:start position:0% dollars in stay Keable assets so first 00:01:47.820 --> 00:01:49.819 align:start position:0% dollars in stay Keable assets so first of<00:01:47.939> all<00:01:47.969> just<00:01:48.180> a<00:01:48.240> quick<00:01:48.479> reality<00:01:48.840> check<00:01:49.049> I<00:01:49.469> know 00:01:49.819 --> 00:01:49.829 align:start position:0% of all just a quick reality check I know 00:01:49.829 --> 00:01:52.370 align:start position:0% of all just a quick reality check I know that<00:01:50.219> everyone<00:01:51.030> will<00:01:51.420> be<00:01:51.540> able<00:01:51.719> to<00:01:51.960> run<00:01:52.140> in<00:01:52.290> a 00:01:52.370 --> 00:01:52.380 align:start position:0% that everyone will be able to run in a 00:01:52.380 --> 00:01:55.459 align:start position:0% that everyone will be able to run in a dream<00:01:52.619> 2.0<00:01:53.719> validator<00:01:54.719> known<00:01:54.930> as<00:01:55.170> long<00:01:55.290> as<00:01:55.409> you 00:01:55.459 --> 00:01:55.469 align:start position:0% dream 2.0 validator known as long as you 00:01:55.469 --> 00:01:57.289 align:start position:0% dream 2.0 validator known as long as you have<00:01:55.590> thirty<00:01:55.770> two<00:01:55.950> E's<00:01:56.100> but<00:01:56.369> the<00:01:56.610> reality<00:01:57.270> is 00:01:57.289 --> 00:01:57.299 align:start position:0% have thirty two E's but the reality is 00:01:57.299 --> 00:02:00.950 align:start position:0% have thirty two E's but the reality is not<00:01:57.810> everyone<00:01:58.079> will<00:01:58.530> be<00:01:58.680> able<00:01:58.829> to<00:01:59.869> you<00:02:00.869> know 00:02:00.950 --> 00:02:00.960 align:start position:0% not everyone will be able to you know 00:02:00.960 --> 00:02:02.510 align:start position:0% not everyone will be able to you know either<00:02:01.200> you<00:02:01.439> don't<00:02:01.530> have<00:02:01.799> the<00:02:01.950> equipment<00:02:02.189> we 00:02:02.510 --> 00:02:02.520 align:start position:0% either you don't have the equipment we 00:02:02.520 --> 00:02:03.980 align:start position:0% either you don't have the equipment we can't<00:02:02.880> assume<00:02:03.180> that<00:02:03.240> everyone<00:02:03.659> will<00:02:03.780> have<00:02:03.810> a 00:02:03.980 --> 00:02:03.990 align:start position:0% can't assume that everyone will have a 00:02:03.990 --> 00:02:06.859 align:start position:0% can't assume that everyone will have a PC<00:02:04.320> at<00:02:04.409> their<00:02:04.530> home<00:02:04.680> or<00:02:04.890> even<00:02:04.950> a<00:02:05.219> laptop<00:02:05.640> and<00:02:06.509> we 00:02:06.859 --> 00:02:06.869 align:start position:0% PC at their home or even a laptop and we 00:02:06.869 --> 00:02:08.120 align:start position:0% PC at their home or even a laptop and we can't<00:02:07.110> assume<00:02:07.350> everyone<00:02:07.740> will<00:02:07.860> have<00:02:07.979> the 00:02:08.120 --> 00:02:08.130 align:start position:0% can't assume everyone will have the 00:02:08.130 --> 00:02:10.370 align:start position:0% can't assume everyone will have the technological<00:02:08.660> capabilities<00:02:09.660> of<00:02:09.930> you<00:02:10.289> know 00:02:10.370 --> 00:02:10.380 align:start position:0% technological capabilities of you know 00:02:10.380 --> 00:02:11.930 align:start position:0% technological capabilities of you know parsing<00:02:10.890> through<00:02:11.009> github<00:02:11.160> or<00:02:11.550> even<00:02:11.790> using 00:02:11.930 --> 00:02:11.940 align:start position:0% parsing through github or even using 00:02:11.940 --> 00:02:13.280 align:start position:0% parsing through github or even using command<00:02:12.330> lines<00:02:12.510> to<00:02:12.780> actually<00:02:13.050> run<00:02:13.230> a 00:02:13.280 --> 00:02:13.290 align:start position:0% command lines to actually run a 00:02:13.290 --> 00:02:17.480 align:start position:0% command lines to actually run a validator<00:02:13.800> node<00:02:14.270> and<00:02:15.270> so<00:02:16.200> that's<00:02:16.410> where<00:02:16.650> I 00:02:17.480 --> 00:02:17.490 align:start position:0% validator node and so that's where I 00:02:17.490 --> 00:02:19.900 align:start position:0% validator node and so that's where I Valladares<00:02:18.060> come<00:02:18.330> in<00:02:18.480> we're<00:02:18.660> trying<00:02:19.050> to<00:02:19.170> help 00:02:19.900 --> 00:02:19.910 align:start position:0% Valladares come in we're trying to help 00:02:19.910 --> 00:02:22.700 align:start position:0% Valladares come in we're trying to help lower<00:02:20.910> the<00:02:21.120> barriers<00:02:21.480> to<00:02:21.510> staking<00:02:22.380> even 00:02:22.700 --> 00:02:22.710 align:start position:0% lower the barriers to staking even 00:02:22.710 --> 00:02:25.220 align:start position:0% lower the barriers to staking even further<00:02:22.950> by<00:02:23.910> making<00:02:23.940> seeking<00:02:24.630> easy<00:02:24.870> for 00:02:25.220 --> 00:02:25.230 align:start position:0% further by making seeking easy for 00:02:25.230 --> 00:02:29.180 align:start position:0% further by making seeking easy for retail<00:02:25.800> and<00:02:26.760> so<00:02:27.540> there<00:02:28.350> are<00:02:28.440> two<00:02:28.620> main<00:02:28.830> service 00:02:29.180 --> 00:02:29.190 align:start position:0% retail and so there are two main service 00:02:29.190 --> 00:02:30.950 align:start position:0% retail and so there are two main service offerings<00:02:29.580> that<00:02:29.700> volunteers<00:02:30.210> offer<00:02:30.480> so<00:02:30.930> far 00:02:30.950 --> 00:02:30.960 align:start position:0% offerings that volunteers offer so far 00:02:30.960 --> 00:02:34.280 align:start position:0% offerings that volunteers offer so far one<00:02:31.950> is<00:02:32.100> validated<00:02:32.730> as<00:02:32.850> a<00:02:33.180> service<00:02:33.570> this<00:02:34.170> is 00:02:34.280 --> 00:02:34.290 align:start position:0% one is validated as a service this is 00:02:34.290 --> 00:02:36.500 align:start position:0% one is validated as a service this is where<00:02:34.440> we<00:02:34.770> run<00:02:34.950> a<00:02:35.010> validator<00:02:35.550> and<00:02:35.790> people 00:02:36.500 --> 00:02:36.510 align:start position:0% where we run a validator and people 00:02:36.510 --> 00:02:39.260 align:start position:0% where we run a validator and people delegate<00:02:37.050> their<00:02:37.590> coins<00:02:37.830> to<00:02:38.070> us<00:02:38.190> delegate<00:02:39.090> is 00:02:39.260 --> 00:02:39.270 align:start position:0% delegate their coins to us delegate is 00:02:39.270 --> 00:02:41.240 align:start position:0% delegate their coins to us delegate is where<00:02:39.660> people<00:02:40.440> don't<00:02:40.680> give<00:02:40.950> up<00:02:41.070> their 00:02:41.240 --> 00:02:41.250 align:start position:0% where people don't give up their 00:02:41.250 --> 00:02:43.310 align:start position:0% where people don't give up their ownership<00:02:41.520> but<00:02:41.820> rather<00:02:41.970> they<00:02:42.240> provide<00:02:43.140> the 00:02:43.310 --> 00:02:43.320 align:start position:0% ownership but rather they provide the 00:02:43.320 --> 00:02:46.610 align:start position:0% ownership but rather they provide the power<00:02:44.010> and<00:02:45.000> end<00:02:45.330> of<00:02:45.900> the<00:02:46.050> coins<00:02:46.290> to<00:02:46.590> a 00:02:46.610 --> 00:02:46.620 align:start position:0% power and end of the coins to a 00:02:46.620 --> 00:02:48.830 align:start position:0% power and end of the coins to a validator<00:02:47.610> so<00:02:47.880> it's<00:02:48.000> a<00:02:48.060> pretty<00:02:48.240> special<00:02:48.570> type 00:02:48.830 --> 00:02:48.840 align:start position:0% validator so it's a pretty special type 00:02:48.840 --> 00:02:51.350 align:start position:0% validator so it's a pretty special type of<00:02:48.870> transaction<00:02:49.530> and<00:02:49.740> so<00:02:50.010> therefore<00:02:50.700> we're 00:02:51.350 --> 00:02:51.360 align:start position:0% of transaction and so therefore we're 00:02:51.360 --> 00:02:52.640 align:start position:0% of transaction and so therefore we're able<00:02:51.450> to<00:02:51.690> run<00:02:51.780> a<00:02:51.840> validator<00:02:52.230> but<00:02:52.380> we<00:02:52.470> don't 00:02:52.640 --> 00:02:52.650 align:start position:0% able to run a validator but we don't 00:02:52.650 --> 00:02:55.010 align:start position:0% able to run a validator but we don't have<00:02:53.310> custody<00:02:53.820> over<00:02:54.330> the<00:02:54.450> coins<00:02:54.720> that<00:02:54.810> are 00:02:55.010 --> 00:02:55.020 align:start position:0% have custody over the coins that are 00:02:55.020 --> 00:02:58.070 align:start position:0% have custody over the coins that are stake<00:02:55.230> with<00:02:55.410> us<00:02:55.970> also<00:02:56.970> there's<00:02:57.600> a<00:02:57.660> fair<00:02:57.990> amount 00:02:58.070 --> 00:02:58.080 align:start position:0% stake with us also there's a fair amount 00:02:58.080 --> 00:03:00.500 align:start position:0% stake with us also there's a fair amount of<00:02:58.320> Valladares<00:02:58.890> that<00:02:59.130> run<00:03:00.030> a<00:03:00.060> note<00:03:00.330> as<00:03:00.480> a 00:03:00.500 --> 00:03:00.510 align:start position:0% of Valladares that run a note as a 00:03:00.510 --> 00:03:02.900 align:start position:0% of Valladares that run a note as a service<00:03:00.870> this<00:03:01.200> is<00:03:01.410> where<00:03:01.650> you<00:03:02.250> imagine<00:03:02.760> like 00:03:02.900 --> 00:03:02.910 align:start position:0% service this is where you imagine like 00:03:02.910 --> 00:03:05.060 align:start position:0% service this is where you imagine like AWS<00:03:03.360> right<00:03:03.630> you're<00:03:04.020> trying<00:03:04.260> to<00:03:04.320> spin<00:03:04.530> up<00:03:04.650> an<00:03:04.890> O 00:03:05.060 --> 00:03:05.070 align:start position:0% AWS right you're trying to spin up an O 00:03:05.070 --> 00:03:06.860 align:start position:0% AWS right you're trying to spin up an O Valley<00:03:05.400> general<00:03:05.760> for<00:03:05.970> any<00:03:06.240> customer<00:03:06.600> that 00:03:06.860 --> 00:03:06.870 align:start position:0% Valley general for any customer that 00:03:06.870 --> 00:03:10.610 align:start position:0% Valley general for any customer that wants<00:03:07.170> to<00:03:07.380> stake<00:03:07.910> and<00:03:08.910> you<00:03:09.840> know<00:03:09.960> there<00:03:10.470> are<00:03:10.500> I 00:03:10.610 --> 00:03:10.620 align:start position:0% wants to stake and you know there are I 00:03:10.620 --> 00:03:12.740 align:start position:0% wants to stake and you know there are I think<00:03:10.770> in<00:03:11.250> the<00:03:11.460> US<00:03:11.670> are<00:03:11.850> two<00:03:12.030> big<00:03:12.300> players<00:03:12.540> in 00:03:12.740 --> 00:03:12.750 align:start position:0% think in the US are two big players in 00:03:12.750 --> 00:03:14.180 align:start position:0% think in the US are two big players in the<00:03:12.840> space<00:03:12.990> there's<00:03:13.230> block<00:03:13.470> Damon<00:03:13.770> and<00:03:13.890> bison 00:03:14.180 --> 00:03:14.190 align:start position:0% the space there's block Damon and bison 00:03:14.190 --> 00:03:17.900 align:start position:0% the space there's block Damon and bison trails<00:03:14.460> and<00:03:15.030> you<00:03:15.900> know<00:03:16.280> largely<00:03:17.280> loaded<00:03:17.790> as<00:03:17.880> a 00:03:17.900 --> 00:03:17.910 align:start position:0% trails and you know largely loaded as a 00:03:17.910 --> 00:03:19.310 align:start position:0% trails and you know largely loaded as a service<00:03:18.270> you<00:03:18.300> can<00:03:18.510> really<00:03:18.720> imagine<00:03:18.900> it<00:03:19.140> to 00:03:19.310 --> 00:03:19.320 align:start position:0% service you can really imagine it to 00:03:19.320 --> 00:03:24.470 align:start position:0% service you can really imagine it to look<00:03:19.530> similar<00:03:19.770> to<00:03:19.970> just<00:03:20.970> an<00:03:21.270> AWS<00:03:23.390> but<00:03:24.390> of 00:03:24.470 --> 00:03:24.480 align:start position:0% look similar to just an AWS but of 00:03:24.480 --> 00:03:28.670 align:start position:0% look similar to just an AWS but of course<00:03:25.130> with<00:03:26.130> the<00:03:26.160> 2.0<00:03:26.870> Razak<00:03:27.870> there's<00:03:28.560> no 00:03:28.670 --> 00:03:28.680 align:start position:0% course with the 2.0 Razak there's no 00:03:28.680 --> 00:03:31.130 align:start position:0% course with the 2.0 Razak there's no such<00:03:29.160> thing<00:03:29.430> as<00:03:29.580> delegation<00:03:30.420> you're<00:03:31.020> not 00:03:31.130 --> 00:03:31.140 align:start position:0% such thing as delegation you're not 00:03:31.140 --> 00:03:32.990 align:start position:0% such thing as delegation you're not gonna<00:03:31.290> be<00:03:31.410> able<00:03:31.470> to<00:03:31.680> delegate<00:03:31.980> your<00:03:32.040> coins<00:03:32.400> so 00:03:32.990 --> 00:03:33.000 align:start position:0% gonna be able to delegate your coins so 00:03:33.000 --> 00:03:35.620 align:start position:0% gonna be able to delegate your coins so unless<00:03:33.540> you<00:03:33.750> have<00:03:33.960> custody<00:03:34.620> of<00:03:34.950> the<00:03:35.130> funds 00:03:35.620 --> 00:03:35.630 align:start position:0% unless you have custody of the funds 00:03:35.630 --> 00:03:37.850 align:start position:0% unless you have custody of the funds Valladares<00:03:36.630> a<00:03:36.690> service<00:03:37.170> is<00:03:37.350> probably<00:03:37.590> not 00:03:37.850 --> 00:03:37.860 align:start position:0% Valladares a service is probably not 00:03:37.860 --> 00:03:41.000 align:start position:0% Valladares a service is probably not going<00:03:38.040> to<00:03:38.100> be<00:03:38.160> a<00:03:38.220> viable<00:03:38.490> business<00:03:39.050> for<00:03:40.050> for 00:03:41.000 --> 00:03:41.010 align:start position:0% going to be a viable business for for 00:03:41.010 --> 00:03:43.640 align:start position:0% going to be a viable business for for volunteers<00:03:41.460> so<00:03:41.580> I<00:03:42.510> won't<00:03:42.870> go<00:03:43.080> too<00:03:43.140> much<00:03:43.380> into 00:03:43.640 --> 00:03:43.650 align:start position:0% volunteers so I won't go too much into 00:03:43.650 --> 00:03:46.220 align:start position:0% volunteers so I won't go too much into detail<00:03:44.040> because<00:03:44.190> of<00:03:44.610> time<00:03:45.570> constraints<00:03:46.140> of 00:03:46.220 --> 00:03:46.230 align:start position:0% detail because of time constraints of 00:03:46.230 --> 00:03:48.800 align:start position:0% detail because of time constraints of over<00:03:46.650> what<00:03:47.220> validators<00:03:47.790> are<00:03:47.910> considering<00:03:48.600> on 00:03:48.800 --> 00:03:48.810 align:start position:0% over what validators are considering on 00:03:48.810 --> 00:03:50.750 align:start position:0% over what validators are considering on what<00:03:49.410> are<00:03:49.530> their<00:03:49.680> businesses<00:03:50.370> that<00:03:50.490> could<00:03:50.670> be 00:03:50.750 --> 00:03:50.760 align:start position:0% what are their businesses that could be 00:03:50.760 --> 00:03:53.000 align:start position:0% what are their businesses that could be provided<00:03:51.210> but<00:03:51.990> you<00:03:52.260> know<00:03:52.350> rest<00:03:52.590> assured<00:03:52.860> and 00:03:53.000 --> 00:03:53.010 align:start position:0% provided but you know rest assured and 00:03:53.010 --> 00:03:54.890 align:start position:0% provided but you know rest assured and node<00:03:53.250> as<00:03:53.400> a<00:03:53.430> service<00:03:53.820> will<00:03:54.030> probably<00:03:54.480> be<00:03:54.600> one 00:03:54.890 --> 00:03:54.900 align:start position:0% node as a service will probably be one 00:03:54.900 --> 00:03:56.750 align:start position:0% node as a service will probably be one of<00:03:54.990> the<00:03:55.110> more<00:03:55.350> strong<00:03:55.650> business<00:03:56.310> lines<00:03:56.520> that 00:03:56.750 --> 00:03:56.760 align:start position:0% of the more strong business lines that 00:03:56.760 --> 00:04:00.590 align:start position:0% of the more strong business lines that validators<00:03:57.360> will<00:03:57.570> pursue<00:03:58.110> for<00:03:58.590> East<00:03:58.740> 2.0<00:03:59.600> but 00:04:00.590 --> 00:04:00.600 align:start position:0% validators will pursue for East 2.0 but 00:04:00.600 --> 00:04:02.780 align:start position:0% validators will pursue for East 2.0 but of<00:04:00.690> course<00:04:00.890> personally<00:04:01.890> and<00:04:02.040> there's<00:04:02.430> there's 00:04:02.780 --> 00:04:02.790 align:start position:0% of course personally and there's there's 00:04:02.790 --> 00:04:05.360 align:start position:0% of course personally and there's there's other<00:04:02.910> avenues<00:04:03.780> that<00:04:04.140> are<00:04:04.290> exciting<00:04:04.680> such<00:04:05.220> as 00:04:05.360 --> 00:04:05.370 align:start position:0% other avenues that are exciting such as 00:04:05.370 --> 00:04:07.100 align:start position:0% other avenues that are exciting such as some<00:04:05.550> giving<00:04:05.820> a<00:04:05.940> shout-out<00:04:06.390> to<00:04:06.570> Crockett<00:04:06.990> pull 00:04:07.100 --> 00:04:07.110 align:start position:0% some giving a shout-out to Crockett pull 00:04:07.110 --> 00:04:08.480 align:start position:0% some giving a shout-out to Crockett pull of<00:04:07.200> course<00:04:07.410> which<00:04:07.560> I'm<00:04:07.890> really<00:04:08.220> looking 00:04:08.480 --> 00:04:08.490 align:start position:0% of course which I'm really looking 00:04:08.490 --> 00:04:13.880 align:start position:0% of course which I'm really looking forward<00:04:08.670> to<00:04:09.110> for<00:04:10.110> e<00:04:10.170> 2.0<00:04:11.810> but<00:04:12.810> you<00:04:12.990> know<00:04:13.110> so<00:04:13.530> you 00:04:13.880 --> 00:04:13.890 align:start position:0% forward to for e 2.0 but you know so you 00:04:13.890 --> 00:04:16.310 align:start position:0% forward to for e 2.0 but you know so you know<00:04:13.920> the<00:04:14.640> valleys<00:04:14.910> are<00:04:15.150> losing<00:04:15.510> probably 00:04:16.310 --> 00:04:16.320 align:start position:0% know the valleys are losing probably 00:04:16.320 --> 00:04:18.080 align:start position:0% know the valleys are losing probably like<00:04:16.709> one<00:04:16.890> of<00:04:17.010> their<00:04:17.160> main<00:04:17.549> business<00:04:17.730> lines 00:04:18.080 --> 00:04:18.090 align:start position:0% like one of their main business lines 00:04:18.090 --> 00:04:20.240 align:start position:0% like one of their main business lines and<00:04:18.450> note<00:04:18.870> as<00:04:18.989> a<00:04:19.020> service<00:04:19.380> seems<00:04:19.590> to<00:04:19.830> be<00:04:19.920> one<00:04:20.160> of 00:04:20.240 --> 00:04:20.250 align:start position:0% and note as a service seems to be one of 00:04:20.250 --> 00:04:22.250 align:start position:0% and note as a service seems to be one of the<00:04:20.370> more<00:04:20.580> viable<00:04:21.270> options<00:04:21.570> but<00:04:21.750> like<00:04:21.989> why<00:04:22.200> are 00:04:22.250 --> 00:04:22.260 align:start position:0% the more viable options but like why are 00:04:22.260 --> 00:04:24.860 align:start position:0% the more viable options but like why are valid<00:04:22.890> ears<00:04:23.070> and<00:04:23.310> here<00:04:23.940> at<00:04:24.120> all<00:04:24.270> in<00:04:24.540> this<00:04:24.630> space 00:04:24.860 --> 00:04:24.870 align:start position:0% valid ears and here at all in this space 00:04:24.870 --> 00:04:26.930 align:start position:0% valid ears and here at all in this space right<00:04:25.110> now<00:04:25.890> there's<00:04:26.130> around<00:04:26.340> about<00:04:26.520> five 00:04:26.930 --> 00:04:26.940 align:start position:0% right now there's around about five 00:04:26.940 --> 00:04:30.110 align:start position:0% right now there's around about five billion<00:04:27.240> dollars<00:04:27.630> of<00:04:28.640> stackable<00:04:29.640> assets<00:04:29.940> in 00:04:30.110 --> 00:04:30.120 align:start position:0% billion dollars of stackable assets in 00:04:30.120 --> 00:04:30.900 align:start position:0% billion dollars of stackable assets in the<00:04:30.210> market 00:04:30.900 --> 00:04:30.910 align:start position:0% the market 00:04:30.910 --> 00:04:35.010 align:start position:0% the market so<00:04:31.540> it's<00:04:31.900> a<00:04:32.260> fair<00:04:32.470> amount<00:04:32.590> and<00:04:33.210> I<00:04:34.210> estimated 00:04:35.010 --> 00:04:35.020 align:start position:0% so it's a fair amount and I estimated 00:04:35.020 --> 00:04:36.990 align:start position:0% so it's a fair amount and I estimated roughly<00:04:35.560> that<00:04:35.740> in<00:04:35.950> a<00:04:36.070> year<00:04:36.340> or<00:04:36.490> so<00:04:36.670> there<00:04:36.880> is 00:04:36.990 --> 00:04:37.000 align:start position:0% roughly that in a year or so there is 00:04:37.000 --> 00:04:39.180 align:start position:0% roughly that in a year or so there is gonna<00:04:37.150> be<00:04:37.300> this<00:04:37.600> number<00:04:38.410> is<00:04:38.500> gonna<00:04:38.620> balloon<00:04:39.010> to 00:04:39.180 --> 00:04:39.190 align:start position:0% gonna be this number is gonna balloon to 00:04:39.190 --> 00:04:40.860 align:start position:0% gonna be this number is gonna balloon to 30<00:04:39.400> billion<00:04:39.730> dollars<00:04:39.790> and<00:04:40.210> of<00:04:40.510> course<00:04:40.750> it 00:04:40.860 --> 00:04:40.870 align:start position:0% 30 billion dollars and of course it 00:04:40.870 --> 00:04:42.780 align:start position:0% 30 billion dollars and of course it Durham<00:04:41.110> 2.0<00:04:41.500> is<00:04:41.710> gonna<00:04:42.010> be<00:04:42.160> the<00:04:42.370> majority<00:04:42.730> of 00:04:42.780 --> 00:04:42.790 align:start position:0% Durham 2.0 is gonna be the majority of 00:04:42.790 --> 00:04:45.900 align:start position:0% Durham 2.0 is gonna be the majority of that<00:04:42.970> with<00:04:43.180> 8<00:04:43.450> billion<00:04:43.660> dollars<00:04:44.070> and<00:04:45.070> so<00:04:45.340> not 00:04:45.900 --> 00:04:45.910 align:start position:0% that with 8 billion dollars and so not 00:04:45.910 --> 00:04:47.430 align:start position:0% that with 8 billion dollars and so not to<00:04:46.060> say<00:04:46.210> that<00:04:46.390> this<00:04:46.630> is<00:04:46.810> the<00:04:46.960> exact<00:04:47.260> like 00:04:47.430 --> 00:04:47.440 align:start position:0% to say that this is the exact like 00:04:47.440 --> 00:04:49.890 align:start position:0% to say that this is the exact like revenue<00:04:47.800> opportunity<00:04:48.640> but<00:04:48.790> this<00:04:48.940> is<00:04:49.090> the<00:04:49.300> the 00:04:49.890 --> 00:04:49.900 align:start position:0% revenue opportunity but this is the the 00:04:49.900 --> 00:04:51.720 align:start position:0% revenue opportunity but this is the the size<00:04:50.170> of<00:04:50.380> the<00:04:50.530> market<00:04:50.680> and<00:04:51.040> so<00:04:51.340> therefore 00:04:51.720 --> 00:04:51.730 align:start position:0% size of the market and so therefore 00:04:51.730 --> 00:04:53.400 align:start position:0% size of the market and so therefore there's<00:04:51.910> a<00:04:51.970> reason<00:04:52.270> why<00:04:52.360> do<00:04:52.420> validators<00:04:53.170> are 00:04:53.400 --> 00:04:53.410 align:start position:0% there's a reason why do validators are 00:04:53.410 --> 00:04:56.070 align:start position:0% there's a reason why do validators are here<00:04:53.950> they<00:04:54.130> want<00:04:54.400> to<00:04:54.700> either<00:04:55.270> facilitate 00:04:56.070 --> 00:04:56.080 align:start position:0% here they want to either facilitate 00:04:56.080 --> 00:04:57.690 align:start position:0% here they want to either facilitate something<00:04:56.380> here<00:04:56.650> they<00:04:56.800> want<00:04:56.980> to<00:04:57.130> do<00:04:57.280> something 00:04:57.690 --> 00:04:57.700 align:start position:0% something here they want to do something 00:04:57.700 --> 00:04:58.020 align:start position:0% something here they want to do something here 00:04:58.020 --> 00:04:58.030 align:start position:0% here 00:04:58.030 --> 00:05:00.570 align:start position:0% here they<00:04:58.480> want<00:04:58.690> to<00:04:58.780> help<00:04:59.110> facilitate<00:04:59.500> staking<00:05:00.400> of 00:05:00.570 --> 00:05:00.580 align:start position:0% they want to help facilitate staking of 00:05:00.580 --> 00:05:03.210 align:start position:0% they want to help facilitate staking of 8<00:05:01.030> billion<00:05:01.330> dollars<00:05:01.480> and<00:05:01.960> when<00:05:02.560> eise<00:05:02.740> 2.0 00:05:03.210 --> 00:05:03.220 align:start position:0% 8 billion dollars and when eise 2.0 00:05:03.220 --> 00:05:09.150 align:start position:0% 8 billion dollars and when eise 2.0 launches<00:05:06.420> and<00:05:07.420> so<00:05:07.690> that's<00:05:08.560> sort<00:05:08.680> of<00:05:08.830> a<00:05:08.890> short 00:05:09.150 --> 00:05:09.160 align:start position:0% launches and so that's sort of a short 00:05:09.160 --> 00:05:12.240 align:start position:0% launches and so that's sort of a short intro<00:05:09.430> on<00:05:09.580> like<00:05:09.810> who<00:05:10.810> validators<00:05:11.770> are<00:05:11.950> how 00:05:12.240 --> 00:05:12.250 align:start position:0% intro on like who validators are how 00:05:12.250 --> 00:05:13.620 align:start position:0% intro on like who validators are how they're<00:05:12.400> trying<00:05:12.700> to<00:05:12.760> they're<00:05:12.940> approaching 00:05:13.620 --> 00:05:13.630 align:start position:0% they're trying to they're approaching 00:05:13.630 --> 00:05:16.590 align:start position:0% they're trying to they're approaching eath<00:05:13.750> 2.0<00:05:14.230> but<00:05:14.410> let's<00:05:15.100> go<00:05:15.280> into<00:05:15.640> like<00:05:15.880> the 00:05:16.590 --> 00:05:16.600 align:start position:0% eath 2.0 but let's go into like the 00:05:16.600 --> 00:05:18.210 align:start position:0% eath 2.0 but let's go into like the reason<00:05:16.900> why<00:05:16.990> i'm<00:05:17.110> here<00:05:17.320> today<00:05:17.470> to<00:05:17.710> talk<00:05:18.160> about 00:05:18.210 --> 00:05:18.220 align:start position:0% reason why i'm here today to talk about 00:05:18.220 --> 00:05:20.940 align:start position:0% reason why i'm here today to talk about some<00:05:18.760> of<00:05:18.790> the<00:05:18.910> lessons<00:05:19.260> the<00:05:20.260> key<00:05:20.530> lessons 00:05:20.940 --> 00:05:20.950 align:start position:0% some of the lessons the key lessons 00:05:20.950 --> 00:05:25.380 align:start position:0% some of the lessons the key lessons we've<00:05:21.640> learned<00:05:22.620> by<00:05:23.620> validating<00:05:24.070> on<00:05:24.520> other<00:05:24.820> POS 00:05:25.380 --> 00:05:25.390 align:start position:0% we've learned by validating on other POS 00:05:25.390 --> 00:05:27.900 align:start position:0% we've learned by validating on other POS protocols<00:05:25.960> and<00:05:26.770> I've<00:05:26.950> really<00:05:27.340> summarizes<00:05:27.730> it 00:05:27.900 --> 00:05:27.910 align:start position:0% protocols and I've really summarizes it 00:05:27.910 --> 00:05:29.940 align:start position:0% protocols and I've really summarizes it down<00:05:28.060> to<00:05:28.210> five<00:05:28.360> Garf<00:05:28.750> are<00:05:28.960> many<00:05:29.200> but<00:05:29.500> these<00:05:29.830> are 00:05:29.940 --> 00:05:29.950 align:start position:0% down to five Garf are many but these are 00:05:29.950 --> 00:05:33.030 align:start position:0% down to five Garf are many but these are the<00:05:30.040> five<00:05:30.280> key<00:05:30.640> ones<00:05:30.850> that<00:05:30.970> I<00:05:31.150> believe<00:05:32.040> this 00:05:33.030 --> 00:05:33.040 align:start position:0% the five key ones that I believe this 00:05:33.040 --> 00:05:37.740 align:start position:0% the five key ones that I believe this Durham<00:05:34.000> community<00:05:34.900> needs<00:05:35.380> to<00:05:35.470> focus<00:05:35.680> on<00:05:36.420> so<00:05:37.420> I 00:05:37.740 --> 00:05:37.750 align:start position:0% Durham community needs to focus on so I 00:05:37.750 --> 00:05:39.240 align:start position:0% Durham community needs to focus on so I don't<00:05:38.110> know<00:05:38.260> if<00:05:38.410> any<00:05:38.620> of<00:05:38.710> you<00:05:38.860> were<00:05:39.070> at<00:05:39.220> the 00:05:39.240 --> 00:05:39.250 align:start position:0% don't know if any of you were at the 00:05:39.250 --> 00:05:42.060 align:start position:0% don't know if any of you were at the first<00:05:39.810> speaker<00:05:40.810> panel<00:05:40.990> session<00:05:41.710> for<00:05:41.950> today 00:05:42.060 --> 00:05:42.070 align:start position:0% first speaker panel session for today 00:05:42.070 --> 00:05:44.310 align:start position:0% first speaker panel session for today life<00:05:42.640> Adam<00:05:43.300> from<00:05:43.450> life<00:05:43.600> here<00:05:43.870> actually<00:05:44.140> gave<00:05:44.290> a 00:05:44.310 --> 00:05:44.320 align:start position:0% life Adam from life here actually gave a 00:05:44.320 --> 00:05:46.470 align:start position:0% life Adam from life here actually gave a pretty<00:05:44.590> good<00:05:44.710> presentation<00:05:45.370> on<00:05:45.520> the<00:05:46.030> one<00:05:46.450> of 00:05:46.470 --> 00:05:46.480 align:start position:0% pretty good presentation on the one of 00:05:46.480 --> 00:05:48.510 align:start position:0% pretty good presentation on the one of the<00:05:46.660> key<00:05:47.080> bottlenecks<00:05:47.590> of<00:05:47.800> staking<00:05:48.250> right<00:05:48.400> now 00:05:48.510 --> 00:05:48.520 align:start position:0% the key bottlenecks of staking right now 00:05:48.520 --> 00:05:52.440 align:start position:0% the key bottlenecks of staking right now and<00:05:48.700> it's<00:05:49.120> a<00:05:49.320> it's<00:05:50.320> the<00:05:50.500> user<00:05:50.920> interface<00:05:51.450> right 00:05:52.440 --> 00:05:52.450 align:start position:0% and it's a it's the user interface right 00:05:52.450 --> 00:05:56.160 align:start position:0% and it's a it's the user interface right now<00:05:52.600> staking<00:05:53.110> is<00:05:53.320> insanely<00:05:54.190> hard<00:05:54.400> even<00:05:55.060> on<00:05:55.420> you 00:05:56.160 --> 00:05:56.170 align:start position:0% now staking is insanely hard even on you 00:05:56.170 --> 00:05:58.230 align:start position:0% now staking is insanely hard even on you know<00:05:56.260> even<00:05:56.770> for<00:05:56.920> like<00:05:57.220> a<00:05:57.400> network<00:05:57.700> like<00:05:57.850> tezo's 00:05:58.230 --> 00:05:58.240 align:start position:0% know even for like a network like tezo's 00:05:58.240 --> 00:06:00.510 align:start position:0% know even for like a network like tezo's for<00:05:58.840> example<00:05:59.200> it's<00:05:59.800> very<00:05:59.860> difficult<00:06:00.370> to 00:06:00.510 --> 00:06:00.520 align:start position:0% for example it's very difficult to 00:06:00.520 --> 00:06:02.010 align:start position:0% for example it's very difficult to understand<00:06:01.000> like<00:06:01.120> where<00:06:01.330> I<00:06:01.360> need<00:06:01.570> to<00:06:01.690> go<00:06:01.780> if<00:06:01.900> I 00:06:02.010 --> 00:06:02.020 align:start position:0% understand like where I need to go if I 00:06:02.020 --> 00:06:04.500 align:start position:0% understand like where I need to go if I have<00:06:02.050> two<00:06:02.530> Z's<00:06:02.710> in<00:06:02.890> my<00:06:03.040> ledger<00:06:03.280> is<00:06:04.150> there<00:06:04.390> an 00:06:04.500 --> 00:06:04.510 align:start position:0% have two Z's in my ledger is there an 00:06:04.510 --> 00:06:06.480 align:start position:0% have two Z's in my ledger is there an interface<00:06:04.870> I<00:06:05.050> could<00:06:05.230> use<00:06:05.410> to<00:06:05.620> stake<00:06:05.860> it's<00:06:06.160> very 00:06:06.480 --> 00:06:06.490 align:start position:0% interface I could use to stake it's very 00:06:06.490 --> 00:06:08.130 align:start position:0% interface I could use to stake it's very hard<00:06:06.790> to<00:06:06.850> find<00:06:07.150> out<00:06:07.300> I<00:06:07.330> recommend<00:06:07.570> you<00:06:07.870> trying 00:06:08.130 --> 00:06:08.140 align:start position:0% hard to find out I recommend you trying 00:06:08.140 --> 00:06:10.140 align:start position:0% hard to find out I recommend you trying to<00:06:08.170> google<00:06:08.530> it<00:06:08.650> you'll<00:06:09.370> you'll<00:06:09.820> come<00:06:10.030> up<00:06:10.060> with 00:06:10.140 --> 00:06:10.150 align:start position:0% to google it you'll you'll come up with 00:06:10.150 --> 00:06:12.930 align:start position:0% to google it you'll you'll come up with very<00:06:10.780> different<00:06:11.230> you<00:06:11.770> know<00:06:11.860> explanations<00:06:12.820> on 00:06:12.930 --> 00:06:12.940 align:start position:0% very different you know explanations on 00:06:12.940 --> 00:06:14.580 align:start position:0% very different you know explanations on where<00:06:13.060> you<00:06:13.150> could<00:06:13.300> go<00:06:13.450> it's<00:06:14.020> not<00:06:14.200> really<00:06:14.440> clear 00:06:14.580 --> 00:06:14.590 align:start position:0% where you could go it's not really clear 00:06:14.590 --> 00:06:18.630 align:start position:0% where you could go it's not really clear on<00:06:15.330> cosmos<00:06:16.410> similarly<00:06:17.410> so<00:06:17.620> when<00:06:18.160> cosmos 00:06:18.630 --> 00:06:18.640 align:start position:0% on cosmos similarly so when cosmos 00:06:18.640 --> 00:06:20.730 align:start position:0% on cosmos similarly so when cosmos launched<00:06:19.090> there<00:06:19.720> was<00:06:19.840> only<00:06:19.930> one<00:06:20.320> mobile 00:06:20.730 --> 00:06:20.740 align:start position:0% launched there was only one mobile 00:06:20.740 --> 00:06:23.160 align:start position:0% launched there was only one mobile wallet<00:06:21.070> available<00:06:21.490> and<00:06:21.670> what<00:06:22.120> one<00:06:22.540> web<00:06:22.810> wallet 00:06:23.160 --> 00:06:23.170 align:start position:0% wallet available and what one web wallet 00:06:23.170 --> 00:06:25.500 align:start position:0% wallet available and what one web wallet available<00:06:23.620> and<00:06:23.970> obviously<00:06:24.970> people<00:06:25.270> were 00:06:25.500 --> 00:06:25.510 align:start position:0% available and obviously people were 00:06:25.510 --> 00:06:27.480 align:start position:0% available and obviously people were confused<00:06:25.960> whether<00:06:26.620> that<00:06:26.860> was<00:06:27.010> the<00:06:27.040> only<00:06:27.340> ones 00:06:27.480 --> 00:06:27.490 align:start position:0% confused whether that was the only ones 00:06:27.490 --> 00:06:31.140 align:start position:0% confused whether that was the only ones they<00:06:28.300> could<00:06:28.360> use<00:06:29.010> but<00:06:30.010> you<00:06:30.190> know<00:06:30.310> but<00:06:30.820> the<00:06:30.970> most 00:06:31.140 --> 00:06:31.150 align:start position:0% they could use but you know but the most 00:06:31.150 --> 00:06:32.820 align:start position:0% they could use but you know but the most safe<00:06:31.420> one<00:06:31.660> was<00:06:31.870> actually<00:06:32.050> using<00:06:32.350> the<00:06:32.530> command 00:06:32.820 --> 00:06:32.830 align:start position:0% safe one was actually using the command 00:06:32.830 --> 00:06:34.860 align:start position:0% safe one was actually using the command line<00:06:32.980> and<00:06:33.190> so<00:06:33.640> people<00:06:33.970> about<00:06:34.480> some<00:06:34.690> of<00:06:34.810> the 00:06:34.860 --> 00:06:34.870 align:start position:0% line and so people about some of the 00:06:34.870 --> 00:06:36.690 align:start position:0% line and so people about some of the validators<00:06:35.260> started<00:06:35.620> telling<00:06:36.190> people<00:06:36.220> to<00:06:36.430> use 00:06:36.690 --> 00:06:36.700 align:start position:0% validators started telling people to use 00:06:36.700 --> 00:06:39.240 align:start position:0% validators started telling people to use the<00:06:36.940> command<00:06:37.210> line<00:06:37.360> and<00:06:37.540> obviously<00:06:38.070> as<00:06:39.070> I 00:06:39.240 --> 00:06:39.250 align:start position:0% the command line and obviously as I 00:06:39.250 --> 00:06:41.610 align:start position:0% the command line and obviously as I mentioned<00:06:39.730> when<00:06:39.970> I<00:06:40.000> first<00:06:40.780> began<00:06:40.930> to<00:06:41.169> stop<00:06:41.380> we 00:06:41.610 --> 00:06:41.620 align:start position:0% mentioned when I first began to stop we 00:06:41.620 --> 00:06:43.409 align:start position:0% mentioned when I first began to stop we can't<00:06:41.890> expect<00:06:42.190> everyone<00:06:42.520> to<00:06:42.730> understand<00:06:43.330> how 00:06:43.409 --> 00:06:43.419 align:start position:0% can't expect everyone to understand how 00:06:43.419 --> 00:06:44.850 align:start position:0% can't expect everyone to understand how to<00:06:43.450> use<00:06:43.780> the<00:06:43.900> command<00:06:44.110> lines 00:06:44.850 --> 00:06:44.860 align:start position:0% to use the command lines 00:06:44.860 --> 00:06:46.200 align:start position:0% to use the command lines therefore<00:06:45.460> there<00:06:45.580> was<00:06:45.670> a<00:06:45.730> lot<00:06:45.910> of<00:06:45.940> confusion 00:06:46.200 --> 00:06:46.210 align:start position:0% therefore there was a lot of confusion 00:06:46.210 --> 00:06:49.200 align:start position:0% therefore there was a lot of confusion so<00:06:46.720> it's<00:06:47.470> important<00:06:47.890> that<00:06:47.920> some<00:06:48.760> form<00:06:49.120> of 00:06:49.200 --> 00:06:49.210 align:start position:0% so it's important that some form of 00:06:49.210 --> 00:06:51.180 align:start position:0% so it's important that some form of staking<00:06:49.570> interfaces<00:06:50.050> or<00:06:50.200> multiple<00:06:50.830> staking 00:06:51.180 --> 00:06:51.190 align:start position:0% staking interfaces or multiple staking 00:06:51.190 --> 00:06:53.160 align:start position:0% staking interfaces or multiple staking interfaces<00:06:51.670> are<00:06:51.880> available<00:06:52.390> 1<00:06:52.510> 2<00:06:52.630> e<00:06:52.660> 2.0 00:06:53.160 --> 00:06:53.170 align:start position:0% interfaces are available 1 2 e 2.0 00:06:53.170 --> 00:06:55.590 align:start position:0% interfaces are available 1 2 e 2.0 launches<00:06:53.560> if<00:06:53.710> not<00:06:54.430> it's<00:06:54.670> gonna<00:06:54.790> cause<00:06:55.300> a<00:06:55.330> lot 00:06:55.590 --> 00:06:55.600 align:start position:0% launches if not it's gonna cause a lot 00:06:55.600 --> 00:06:57.660 align:start position:0% launches if not it's gonna cause a lot of<00:06:55.630> confusion<00:06:56.200> and<00:06:56.350> you're<00:06:56.530> just<00:06:57.340> basically 00:06:57.660 --> 00:06:57.670 align:start position:0% of confusion and you're just basically 00:06:57.670 --> 00:07:00.480 align:start position:0% of confusion and you're just basically limiting<00:06:58.390> the<00:06:58.630> opportunity<00:06:59.560> to<00:06:59.710> stake<00:07:00.010> it's<00:07:00.430> a 00:07:00.480 --> 00:07:00.490 align:start position:0% limiting the opportunity to stake it's a 00:07:00.490 --> 00:07:03.390 align:start position:0% limiting the opportunity to stake it's a very<00:07:00.700> limited<00:07:01.150> set<00:07:01.600> of<00:07:01.630> people<00:07:02.200> of<00:07:02.920> community 00:07:03.390 --> 00:07:03.400 align:start position:0% very limited set of people of community 00:07:03.400 --> 00:07:08.390 align:start position:0% very limited set of people of community members<00:07:04.950> now<00:07:06.240> another<00:07:07.240> important<00:07:07.750> part<00:07:07.930> is 00:07:08.390 --> 00:07:08.400 align:start position:0% members now another important part is 00:07:08.400 --> 00:07:13.590 align:start position:0% members now another important part is the<00:07:09.400> making<00:07:10.270> staking<00:07:10.810> trackable<00:07:11.500> uh<00:07:11.650> and<00:07:12.600> you 00:07:13.590 --> 00:07:13.600 align:start position:0% the making staking trackable uh and you 00:07:13.600 --> 00:07:15.060 align:start position:0% the making staking trackable uh and you know<00:07:13.630> of<00:07:13.930> course<00:07:14.140> you<00:07:14.380> want<00:07:14.560> it<00:07:14.830> for 00:07:15.060 --> 00:07:15.070 align:start position:0% know of course you want it for 00:07:15.070 --> 00:07:16.410 align:start position:0% know of course you want it for bookkeeping<00:07:15.610> you<00:07:15.760> want<00:07:15.910> to<00:07:15.970> see<00:07:16.120> how<00:07:16.270> much 00:07:16.410 --> 00:07:16.420 align:start position:0% bookkeeping you want to see how much 00:07:16.420 --> 00:07:18.780 align:start position:0% bookkeeping you want to see how much income<00:07:16.870> you're<00:07:17.050> you<00:07:17.560> have<00:07:17.590> how<00:07:18.070> much<00:07:18.250> how<00:07:18.700> much 00:07:18.780 --> 00:07:18.790 align:start position:0% income you're you have how much how much 00:07:18.790 --> 00:07:20.670 align:start position:0% income you're you have how much how much you<00:07:18.970> have<00:07:19.090> stake<00:07:19.360> but<00:07:19.600> more<00:07:20.230> importantly 00:07:20.670 --> 00:07:20.680 align:start position:0% you have stake but more importantly 00:07:20.680 --> 00:07:24.840 align:start position:0% you have stake but more importantly there<00:07:21.460> are<00:07:21.610> tax<00:07:22.150> reasons<00:07:22.930> for<00:07:23.110> this<00:07:23.760> there's<00:07:24.760> a 00:07:24.840 --> 00:07:24.850 align:start position:0% there are tax reasons for this there's a 00:07:24.850 --> 00:07:27.030 align:start position:0% there are tax reasons for this there's a lot<00:07:25.090> of<00:07:25.240> regulatory<00:07:25.900> unclarity<00:07:26.590> on<00:07:26.830> how 00:07:27.030 --> 00:07:27.040 align:start position:0% lot of regulatory unclarity on how 00:07:27.040 --> 00:07:30.060 align:start position:0% lot of regulatory unclarity on how staking<00:07:27.760> should<00:07:28.060> be<00:07:28.210> considered<00:07:28.920> tax<00:07:29.920> wise 00:07:30.060 --> 00:07:30.070 align:start position:0% staking should be considered tax wise 00:07:30.070 --> 00:07:32.640 align:start position:0% staking should be considered tax wise but<00:07:30.450> eventually<00:07:31.450> you<00:07:31.840> know<00:07:31.960> people<00:07:32.350> will<00:07:32.470> need 00:07:32.640 --> 00:07:32.650 align:start position:0% but eventually you know people will need 00:07:32.650 --> 00:07:34.740 align:start position:0% but eventually you know people will need to<00:07:32.770> be<00:07:32.890> paid<00:07:33.220> our<00:07:33.340> taxes<00:07:33.730> on<00:07:33.850> problem<00:07:34.240> most 00:07:34.740 --> 00:07:34.750 align:start position:0% to be paid our taxes on problem most 00:07:34.750 --> 00:07:36.450 align:start position:0% to be paid our taxes on problem most likely<00:07:35.050> on<00:07:35.170> staking<00:07:35.530> Awards<00:07:35.800> and<00:07:35.950> the<00:07:36.310> only 00:07:36.450 --> 00:07:36.460 align:start position:0% likely on staking Awards and the only 00:07:36.460 --> 00:07:37.950 align:start position:0% likely on staking Awards and the only way<00:07:36.670> they'll<00:07:36.850> be<00:07:36.880> able<00:07:37.060> to<00:07:37.210> do<00:07:37.390> that<00:07:37.540> is<00:07:37.750> if 00:07:37.950 --> 00:07:37.960 align:start position:0% way they'll be able to do that is if 00:07:37.960 --> 00:07:39.720 align:start position:0% way they'll be able to do that is if they're<00:07:38.110> able<00:07:38.290> to<00:07:38.440> track<00:07:38.830> how<00:07:39.040> much<00:07:39.190> rewards 00:07:39.720 --> 00:07:39.730 align:start position:0% they're able to track how much rewards 00:07:39.730 --> 00:07:42.090 align:start position:0% they're able to track how much rewards even<00:07:40.030> receiving<00:07:40.360> how<00:07:40.600> much<00:07:40.750> assets<00:07:41.710> Amiens 00:07:42.090 --> 00:07:42.100 align:start position:0% even receiving how much assets Amiens 00:07:42.100 --> 00:07:43.650 align:start position:0% even receiving how much assets Amiens taking<00:07:42.460> so<00:07:42.610> far 00:07:43.650 --> 00:07:43.660 align:start position:0% taking so far 00:07:43.660 --> 00:07:45.720 align:start position:0% taking so far there<00:07:43.990> aren't<00:07:44.350> that<00:07:44.500> many<00:07:44.560> of<00:07:45.430> such 00:07:45.720 --> 00:07:45.730 align:start position:0% there aren't that many of such 00:07:45.730 --> 00:07:47.820 align:start position:0% there aren't that many of such dashboards<00:07:46.570> many<00:07:46.990> of<00:07:47.080> them<00:07:47.200> are<00:07:47.320> launching 00:07:47.820 --> 00:07:47.830 align:start position:0% dashboards many of them are launching 00:07:47.830 --> 00:07:50.600 align:start position:0% dashboards many of them are launching right<00:07:48.010> now<00:07:48.250> but<00:07:48.700> this<00:07:49.570> is<00:07:49.630> another<00:07:50.020> of<00:07:50.140> another 00:07:50.600 --> 00:07:50.610 align:start position:0% right now but this is another of another 00:07:50.610 --> 00:07:53.190 align:start position:0% right now but this is another of another another<00:07:51.610> key<00:07:52.030> tool<00:07:52.330> that<00:07:52.360> needs<00:07:52.750> to<00:07:52.870> be<00:07:52.900> pride 00:07:53.190 --> 00:07:53.200 align:start position:0% another key tool that needs to be pride 00:07:53.200 --> 00:07:56.970 align:start position:0% another key tool that needs to be pride that<00:07:53.380> when<00:07:53.500> ES<00:07:53.650> 2.0<00:07:54.070> becomes<00:07:54.430> available<00:07:55.980> so 00:07:56.970 --> 00:07:56.980 align:start position:0% that when ES 2.0 becomes available so 00:07:56.980 --> 00:08:00.180 align:start position:0% that when ES 2.0 becomes available so yeah<00:07:57.310> so<00:07:57.730> number<00:07:58.240> one<00:07:58.390> key<00:07:58.630> theme<00:07:58.840> here<00:07:59.080> is<00:07:59.230> try 00:08:00.180 --> 00:08:00.190 align:start position:0% yeah so number one key theme here is try 00:08:00.190 --> 00:08:03.060 align:start position:0% yeah so number one key theme here is try to<00:08:00.250> make<00:08:00.460> you<00:08:01.210> know<00:08:01.350> interfaces<00:08:02.350> for<00:08:02.650> users 00:08:03.060 --> 00:08:03.070 align:start position:0% to make you know interfaces for users 00:08:03.070 --> 00:08:05.240 align:start position:0% to make you know interfaces for users for<00:08:03.340> retail<00:08:03.700> such<00:08:03.880> that<00:08:04.120> they're<00:08:04.630> able<00:08:04.870> to 00:08:05.240 --> 00:08:05.250 align:start position:0% for retail such that they're able to 00:08:05.250 --> 00:08:09.600 align:start position:0% for retail such that they're able to stay<00:08:06.250> easily<00:08:06.670> and<00:08:07.060> also<00:08:07.360> to<00:08:07.420> track<00:08:07.780> how<00:08:08.740> their 00:08:09.600 --> 00:08:09.610 align:start position:0% stay easily and also to track how their 00:08:09.610 --> 00:08:14.250 align:start position:0% stay easily and also to track how their state<00:08:09.880> assets<00:08:10.300> easily<00:08:12.660> number<00:08:13.660> two<00:08:13.810> is<00:08:13.960> so 00:08:14.250 --> 00:08:14.260 align:start position:0% state assets easily number two is so 00:08:14.260 --> 00:08:17.700 align:start position:0% state assets easily number two is so slashing<00:08:14.740> has<00:08:14.890> occurred<00:08:15.810> on<00:08:16.810> Kosmos 00:08:17.700 --> 00:08:17.710 align:start position:0% slashing has occurred on Kosmos 00:08:17.710 --> 00:08:20.640 align:start position:0% slashing has occurred on Kosmos especially<00:08:18.610> recently<00:08:19.330> not<00:08:20.110> recently<00:08:20.140> I<00:08:20.500> guess 00:08:20.640 --> 00:08:20.650 align:start position:0% especially recently not recently I guess 00:08:20.650 --> 00:08:24.090 align:start position:0% especially recently not recently I guess in<00:08:20.800> June<00:08:21.070> July<00:08:22.050> someone<00:08:23.050> uh<00:08:23.080> one<00:08:23.920> of<00:08:24.010> the 00:08:24.090 --> 00:08:24.100 align:start position:0% in June July someone uh one of the 00:08:24.100 --> 00:08:27.390 align:start position:0% in June July someone uh one of the Valladares<00:08:24.630> had<00:08:25.630> their<00:08:26.590> value<00:08:26.890> here<00:08:27.010> was<00:08:27.190> down 00:08:27.390 --> 00:08:27.400 align:start position:0% Valladares had their value here was down 00:08:27.400 --> 00:08:28.860 align:start position:0% Valladares had their value here was down for<00:08:27.580> a<00:08:27.640> while<00:08:27.820> and<00:08:28.000> they<00:08:28.120> tried<00:08:28.480> to<00:08:28.570> bring<00:08:28.750> it 00:08:28.860 --> 00:08:28.870 align:start position:0% for a while and they tried to bring it 00:08:28.870 --> 00:08:30.420 align:start position:0% for a while and they tried to bring it back<00:08:29.020> up<00:08:29.050> and<00:08:29.380> accidentally<00:08:29.950> they're<00:08:30.220> back<00:08:30.400> up 00:08:30.420 --> 00:08:30.430 align:start position:0% back up and accidentally they're back up 00:08:30.430 --> 00:08:33.060 align:start position:0% back up and accidentally they're back up note<00:08:30.730> and<00:08:30.940> our<00:08:31.210> main<00:08:31.480> balladeer<00:08:32.050> node<00:08:32.260> came 00:08:33.060 --> 00:08:33.070 align:start position:0% note and our main balladeer node came 00:08:33.070 --> 00:08:34.710 align:start position:0% note and our main balladeer node came back<00:08:33.280> up<00:08:33.460> at<00:08:33.640> the<00:08:33.730> same<00:08:33.910> time<00:08:34.150> causing<00:08:34.630> a 00:08:34.710 --> 00:08:34.720 align:start position:0% back up at the same time causing a 00:08:34.720 --> 00:08:38.490 align:start position:0% back up at the same time causing a double<00:08:34.990> double<00:08:35.770> signing<00:08:36.070> so<00:08:37.020> when<00:08:38.020> as<00:08:38.440> a 00:08:38.490 --> 00:08:38.500 align:start position:0% double double signing so when as a 00:08:38.500 --> 00:08:40.380 align:start position:0% double double signing so when as a validator<00:08:38.950> when<00:08:39.070> I<00:08:39.100> talk<00:08:39.400> with<00:08:39.430> retail<00:08:40.150> or 00:08:40.380 --> 00:08:40.390 align:start position:0% validator when I talk with retail or 00:08:40.390 --> 00:08:42.720 align:start position:0% validator when I talk with retail or other<00:08:40.900> funds<00:08:41.230> the<00:08:41.920> number<00:08:42.160> one<00:08:42.310> question<00:08:42.640> they 00:08:42.720 --> 00:08:42.730 align:start position:0% other funds the number one question they 00:08:42.730 --> 00:08:45.090 align:start position:0% other funds the number one question they always<00:08:42.760> ask<00:08:43.210> us<00:08:43.510> ask<00:08:43.810> us<00:08:44.140> is<00:08:44.320> how<00:08:44.860> are<00:08:44.980> you 00:08:45.090 --> 00:08:45.100 align:start position:0% always ask us ask us is how are you 00:08:45.100 --> 00:08:47.760 align:start position:0% always ask us ask us is how are you gonna<00:08:45.220> insure<00:08:45.670> me<00:08:45.820> that<00:08:46.030> you<00:08:46.690> know<00:08:46.810> how<00:08:47.650> are 00:08:47.760 --> 00:08:47.770 align:start position:0% gonna insure me that you know how are 00:08:47.770 --> 00:08:49.440 align:start position:0% gonna insure me that you know how are you<00:08:47.860> gonna<00:08:47.980> intervene<00:08:48.400> in<00:08:48.550> terms<00:08:48.790> of<00:08:48.910> slashing 00:08:49.440 --> 00:08:49.450 align:start position:0% you gonna intervene in terms of slashing 00:08:49.450 --> 00:08:51.750 align:start position:0% you gonna intervene in terms of slashing risk<00:08:49.660> it's<00:08:50.080> all<00:08:50.260> in<00:08:50.440> their<00:08:50.590> minds<00:08:50.830> but<00:08:51.190> with 00:08:51.750 --> 00:08:51.760 align:start position:0% risk it's all in their minds but with 00:08:51.760 --> 00:08:54.570 align:start position:0% risk it's all in their minds but with this<00:08:52.000> with<00:08:52.960> this<00:08:53.140> double<00:08:53.470> signing<00:08:53.770> event<00:08:54.070> it's 00:08:54.570 --> 00:08:54.580 align:start position:0% this with this double signing event it's 00:08:54.580 --> 00:08:58.440 align:start position:0% this with this double signing event it's becoming<00:08:55.000> much<00:08:55.720> more<00:08:56.250> this<00:08:57.250> risk<00:08:57.730> is<00:08:57.880> becoming 00:08:58.440 --> 00:08:58.450 align:start position:0% becoming much more this risk is becoming 00:08:58.450 --> 00:09:00.990 align:start position:0% becoming much more this risk is becoming in<00:08:58.600> their<00:08:58.720> minds<00:08:58.930> and<00:08:59.260> it's<00:09:00.070> become<00:09:00.730> a<00:09:00.760> key 00:09:00.990 --> 00:09:01.000 align:start position:0% in their minds and it's become a key 00:09:01.000 --> 00:09:02.970 align:start position:0% in their minds and it's become a key theme<00:09:01.180> that<00:09:01.870> they<00:09:02.200> constantly<00:09:02.500> asked<00:09:02.829> for 00:09:02.970 --> 00:09:02.980 align:start position:0% theme that they constantly asked for 00:09:02.980 --> 00:09:05.610 align:start position:0% theme that they constantly asked for insurance<00:09:03.370> or<00:09:03.579> some<00:09:03.850> way<00:09:04.000> that<00:09:04.320> some<00:09:05.320> social 00:09:05.610 --> 00:09:05.620 align:start position:0% insurance or some way that some social 00:09:05.620 --> 00:09:07.650 align:start position:0% insurance or some way that some social conscious<00:09:06.220> I'm<00:09:06.459> option<00:09:06.910> contrary<00:09:07.300> could<00:09:07.510> sign 00:09:07.650 --> 00:09:07.660 align:start position:0% conscious I'm option contrary could sign 00:09:07.660 --> 00:09:10.139 align:start position:0% conscious I'm option contrary could sign such<00:09:07.839> that<00:09:08.079> they're<00:09:08.649> able<00:09:08.829> to<00:09:09.010> then<00:09:09.190> somehow 00:09:10.139 --> 00:09:10.149 align:start position:0% such that they're able to then somehow 00:09:10.149 --> 00:09:15.120 align:start position:0% such that they're able to then somehow recoup<00:09:10.779> the<00:09:11.470> /<00:09:11.740> amount<00:09:12.660> and<00:09:13.660> so<00:09:14.130> therefore 00:09:15.120 --> 00:09:15.130 align:start position:0% recoup the / amount and so therefore 00:09:15.130 --> 00:09:16.889 align:start position:0% recoup the / amount and so therefore this<00:09:15.399> is<00:09:15.550> definitely<00:09:16.000> another<00:09:16.180> pain<00:09:16.660> point 00:09:16.889 --> 00:09:16.899 align:start position:0% this is definitely another pain point 00:09:16.899 --> 00:09:19.530 align:start position:0% this is definitely another pain point and<00:09:17.110> there<00:09:17.529> needs<00:09:17.740> to<00:09:17.829> be<00:09:17.889> some<00:09:18.190> method<00:09:18.490> to<00:09:19.060> let 00:09:19.530 --> 00:09:19.540 align:start position:0% and there needs to be some method to let 00:09:19.540 --> 00:09:22.980 align:start position:0% and there needs to be some method to let you<00:09:20.529> know<00:09:20.649> people<00:09:21.120> hedge<00:09:22.120> their<00:09:22.600> slashing 00:09:22.980 --> 00:09:22.990 align:start position:0% you know people hedge their slashing 00:09:22.990 --> 00:09:25.170 align:start position:0% you know people hedge their slashing risk<00:09:23.199> and<00:09:23.440> most<00:09:24.040> likely<00:09:24.220> I<00:09:24.430> believe<00:09:24.760> this<00:09:24.940> will 00:09:25.170 --> 00:09:25.180 align:start position:0% risk and most likely I believe this will 00:09:25.180 --> 00:09:28.079 align:start position:0% risk and most likely I believe this will come<00:09:25.570> in<00:09:25.750> the<00:09:25.839> form<00:09:26.019> of<00:09:26.199> defy<00:09:26.589> in<00:09:27.430> terms<00:09:28.000> of 00:09:28.079 --> 00:09:28.089 align:start position:0% come in the form of defy in terms of 00:09:28.089 --> 00:09:30.750 align:start position:0% come in the form of defy in terms of like<00:09:28.240> insurance<00:09:28.990> markets<00:09:29.320> most<00:09:29.500> likely<00:09:29.829> and 00:09:30.750 --> 00:09:30.760 align:start position:0% like insurance markets most likely and 00:09:30.760 --> 00:09:35.129 align:start position:0% like insurance markets most likely and so<00:09:31.769> these<00:09:32.769> sort<00:09:32.980> of<00:09:33.690> these<00:09:34.690> sort<00:09:34.870> of<00:09:34.899> defy 00:09:35.129 --> 00:09:35.139 align:start position:0% so these sort of these sort of defy 00:09:35.139 --> 00:09:36.420 align:start position:0% so these sort of these sort of defy products<00:09:35.500> needs<00:09:35.709> to<00:09:35.829> be<00:09:35.920> thought<00:09:36.100> of<00:09:36.160> in 00:09:36.420 --> 00:09:36.430 align:start position:0% products needs to be thought of in 00:09:36.430 --> 00:09:40.170 align:start position:0% products needs to be thought of in advance<00:09:36.639> and<00:09:37.089> created<00:09:37.959> not<00:09:38.829> not<00:09:39.550> after<00:09:39.760> East 00:09:40.170 --> 00:09:40.180 align:start position:0% advance and created not not after East 00:09:40.180 --> 00:09:43.230 align:start position:0% advance and created not not after East 2.0<00:09:40.720> has<00:09:40.870> launched<00:09:41.110> really<00:09:41.760> also<00:09:42.760> another 00:09:43.230 --> 00:09:43.240 align:start position:0% 2.0 has launched really also another 00:09:43.240 --> 00:09:45.300 align:start position:0% 2.0 has launched really also another thing<00:09:43.480> is<00:09:43.720> another<00:09:44.380> way<00:09:44.620> of<00:09:44.860> actually 00:09:45.300 --> 00:09:45.310 align:start position:0% thing is another way of actually 00:09:45.310 --> 00:09:47.129 align:start position:0% thing is another way of actually reducing<00:09:45.850> slashing<00:09:46.449> risk<00:09:46.660> is<00:09:46.839> by 00:09:47.129 --> 00:09:47.139 align:start position:0% reducing slashing risk is by 00:09:47.139 --> 00:09:49.560 align:start position:0% reducing slashing risk is by diversifying<00:09:47.829> who<00:09:48.279> you<00:09:48.430> stake<00:09:48.730> to<00:09:48.910> for 00:09:49.560 --> 00:09:49.570 align:start position:0% diversifying who you stake to for 00:09:49.570 --> 00:09:52.290 align:start position:0% diversifying who you stake to for example<00:09:49.660> if<00:09:50.110> I'm<00:09:50.350> trying<00:09:50.920> to<00:09:51.010> stake<00:09:51.279> on<00:09:51.550> cosmos 00:09:52.290 --> 00:09:52.300 align:start position:0% example if I'm trying to stake on cosmos 00:09:52.300 --> 00:09:54.509 align:start position:0% example if I'm trying to stake on cosmos random<00:09:52.839> valid<00:09:53.230> any<00:09:53.380> rather<00:09:53.889> is<00:09:54.040> taking<00:09:54.399> with 00:09:54.509 --> 00:09:54.519 align:start position:0% random valid any rather is taking with 00:09:54.519 --> 00:09:56.430 align:start position:0% random valid any rather is taking with one<00:09:54.820> valid<00:09:55.269> ear<00:09:55.389> it's<00:09:55.570> better<00:09:55.810> to<00:09:56.019> spread<00:09:56.260> out 00:09:56.430 --> 00:09:56.440 align:start position:0% one valid ear it's better to spread out 00:09:56.440 --> 00:09:58.620 align:start position:0% one valid ear it's better to spread out your<00:09:56.560> risk<00:09:56.769> and<00:09:57.010> valid<00:09:57.339> just<00:09:58.060> similar<00:09:58.269> to<00:09:58.510> how 00:09:58.620 --> 00:09:58.630 align:start position:0% your risk and valid just similar to how 00:09:58.630 --> 00:10:00.780 align:start position:0% your risk and valid just similar to how you<00:09:58.690> diversify<00:09:59.230> your<00:09:59.500> portfolio 00:10:00.780 --> 00:10:00.790 align:start position:0% you diversify your portfolio 00:10:00.790 --> 00:10:03.050 align:start position:0% you diversify your portfolio this<00:10:01.120> concept<00:10:01.540> is<00:10:01.690> sort<00:10:02.260> of<00:10:02.320> not<00:10:02.769> really 00:10:03.050 --> 00:10:03.060 align:start position:0% this concept is sort of not really 00:10:03.060 --> 00:10:05.939 align:start position:0% this concept is sort of not really considered<00:10:04.060> too<00:10:04.180> much<00:10:04.329> we<00:10:05.110> see<00:10:05.290> way<00:10:05.500> too<00:10:05.560> many 00:10:05.939 --> 00:10:05.949 align:start position:0% considered too much we see way too many 00:10:05.949 --> 00:10:09.540 align:start position:0% considered too much we see way too many just<00:10:06.670> all<00:10:06.850> in<00:10:07.149> staking<00:10:08.050> going<00:10:08.320> on<00:10:08.470> in<00:10:08.709> various 00:10:09.540 --> 00:10:09.550 align:start position:0% just all in staking going on in various 00:10:09.550 --> 00:10:12.870 align:start position:0% just all in staking going on in various protocols<00:10:09.850> so<00:10:10.649> but<00:10:11.649> the<00:10:12.100> probably<00:10:12.579> the<00:10:12.670> main 00:10:12.870 --> 00:10:12.880 align:start position:0% protocols so but the probably the main 00:10:12.880 --> 00:10:14.250 align:start position:0% protocols so but the probably the main reason<00:10:13.149> why<00:10:13.240> that's<00:10:13.390> occurring<00:10:13.600> is<00:10:13.930> because 00:10:14.250 --> 00:10:14.260 align:start position:0% reason why that's occurring is because 00:10:14.260 --> 00:10:17.009 align:start position:0% reason why that's occurring is because it's<00:10:14.440> very<00:10:14.649> inconvenient<00:10:14.949> to<00:10:15.690> diversify<00:10:16.690> your 00:10:17.009 --> 00:10:17.019 align:start position:0% it's very inconvenient to diversify your 00:10:17.019 --> 00:10:20.699 align:start position:0% it's very inconvenient to diversify your stake<00:10:17.760> when<00:10:18.760> you're<00:10:18.880> staking<00:10:19.089> so<00:10:19.779> providing 00:10:20.699 --> 00:10:20.709 align:start position:0% stake when you're staking so providing 00:10:20.709 --> 00:10:24.480 align:start position:0% stake when you're staking so providing an<00:10:20.920> automated<00:10:21.810> option<00:10:22.810> or<00:10:22.990> service<00:10:23.560> such<00:10:24.310> that 00:10:24.480 --> 00:10:24.490 align:start position:0% an automated option or service such that 00:10:24.490 --> 00:10:26.509 align:start position:0% an automated option or service such that people<00:10:24.850> could<00:10:25.000> automatically<00:10:25.480> diversify<00:10:26.199> the 00:10:26.509 --> 00:10:26.519 align:start position:0% people could automatically diversify the 00:10:26.519 --> 00:10:28.680 align:start position:0% people could automatically diversify the validators<00:10:27.519> that<00:10:27.670> they're<00:10:27.820> using<00:10:28.180> is<00:10:28.329> also<00:10:28.660> a 00:10:28.680 --> 00:10:28.690 align:start position:0% validators that they're using is also a 00:10:28.690 --> 00:10:31.710 align:start position:0% validators that they're using is also a pretty<00:10:29.110> important<00:10:30.029> method<00:10:31.029> of<00:10:31.180> hedging 00:10:31.710 --> 00:10:31.720 align:start position:0% pretty important method of hedging 00:10:31.720 --> 00:10:33.389 align:start position:0% pretty important method of hedging they're<00:10:32.290> slashing<00:10:32.529> risk<00:10:32.829> and<00:10:33.040> probably<00:10:33.339> a 00:10:33.389 --> 00:10:33.399 align:start position:0% they're slashing risk and probably a 00:10:33.399 --> 00:10:34.740 align:start position:0% they're slashing risk and probably a very<00:10:33.730> important<00:10:34.120> product<00:10:34.269> that<00:10:34.449> will<00:10:34.720> be 00:10:34.740 --> 00:10:34.750 align:start position:0% very important product that will be 00:10:34.750 --> 00:10:38.400 align:start position:0% very important product that will be needed<00:10:35.550> you<00:10:36.550> know<00:10:36.670> close<00:10:37.180> to<00:10:37.209> when<00:10:37.779> East<00:10:37.959> 2.0 00:10:38.400 --> 00:10:38.410 align:start position:0% needed you know close to when East 2.0 00:10:38.410 --> 00:10:44.490 align:start position:0% needed you know close to when East 2.0 launches<00:10:41.550> another<00:10:42.550> key<00:10:43.540> thing<00:10:43.990> that<00:10:44.019> we've 00:10:44.490 --> 00:10:44.500 align:start position:0% launches another key thing that we've 00:10:44.500 --> 00:10:46.439 align:start position:0% launches another key thing that we've seen<00:10:44.529> constantly<00:10:45.279> come<00:10:45.370> up<00:10:45.399> in<00:10:45.880> other<00:10:46.000> POS 00:10:46.439 --> 00:10:46.449 align:start position:0% seen constantly come up in other POS 00:10:46.449 --> 00:10:50.840 align:start position:0% seen constantly come up in other POS protocols<00:10:46.899> is<00:10:47.339> centralization<00:10:48.339> debate<00:10:49.440> it's 00:10:50.840 --> 00:10:50.850 align:start position:0% protocols is centralization debate it's 00:10:50.850 --> 00:10:53.430 align:start position:0% protocols is centralization debate it's so<00:10:51.850> on<00:10:52.089> the<00:10:52.209> left<00:10:52.540> here<00:10:52.810> you<00:10:52.839> could<00:10:53.050> see<00:10:53.230> sort 00:10:53.430 --> 00:10:53.440 align:start position:0% so on the left here you could see sort 00:10:53.440 --> 00:10:55.740 align:start position:0% so on the left here you could see sort of<00:10:53.470> the<00:10:53.589> graph<00:10:53.829> of<00:10:54.069> the<00:10:54.910> state<00:10:55.540> power 00:10:55.740 --> 00:10:55.750 align:start position:0% of the graph of the state power 00:10:55.750 --> 00:11:00.420 align:start position:0% of the graph of the state power basically<00:10:56.740> distribution<00:10:57.540> and<00:10:58.540> and<00:10:59.370> this<00:11:00.370> is 00:11:00.420 --> 00:11:00.430 align:start position:0% basically distribution and and this is 00:11:00.430 --> 00:11:04.829 align:start position:0% basically distribution and and this is uh<00:11:00.550> this<00:11:00.940> is<00:11:01.000> in<00:11:01.300> cosmos<00:11:01.720> by<00:11:01.839> doing<00:11:02.819> so<00:11:03.839> for 00:11:04.829 --> 00:11:04.839 align:start position:0% uh this is in cosmos by doing so for 00:11:04.839 --> 00:11:06.750 align:start position:0% uh this is in cosmos by doing so for ether<00:11:05.139> a.m.<00:11:05.350> there's<00:11:05.649> no<00:11:05.800> delegation<00:11:06.459> so<00:11:06.670> you 00:11:06.750 --> 00:11:06.760 align:start position:0% ether a.m. there's no delegation so you 00:11:06.760 --> 00:11:11.130 align:start position:0% ether a.m. there's no delegation so you won't<00:11:07.120> see<00:11:07.360> this<00:11:08.069> this<00:11:09.069> dark<00:11:09.399> of<00:11:09.579> of<00:11:10.329> a<00:11:10.870> grant 00:11:11.130 --> 00:11:11.140 align:start position:0% won't see this this dark of of a grant 00:11:11.140 --> 00:11:12.350 align:start position:0% won't see this this dark of of a grant distribution<00:11:11.800> graph 00:11:12.350 --> 00:11:12.360 align:start position:0% distribution graph 00:11:12.360 --> 00:11:14.780 align:start position:0% distribution graph you<00:11:12.480> know<00:11:12.600> and<00:11:13.230> e<00:11:13.440> 2.0<00:11:13.920> how<00:11:14.040> this<00:11:14.220> is<00:11:14.460> relevant 00:11:14.780 --> 00:11:14.790 align:start position:0% you know and e 2.0 how this is relevant 00:11:14.790 --> 00:11:17.360 align:start position:0% you know and e 2.0 how this is relevant is<00:11:15.060> in<00:11:15.210> two<00:11:15.330> ways<00:11:15.540> so<00:11:16.320> exchanges<00:11:16.950> definitely 00:11:17.360 --> 00:11:17.370 align:start position:0% is in two ways so exchanges definitely 00:11:17.370 --> 00:11:19.760 align:start position:0% is in two ways so exchanges definitely will<00:11:18.270> have<00:11:18.480> so<00:11:18.780> much<00:11:18.930> in<00:11:19.080> their<00:11:19.200> custody<00:11:19.500> so 00:11:19.760 --> 00:11:19.770 align:start position:0% will have so much in their custody so 00:11:19.770 --> 00:11:21.320 align:start position:0% will have so much in their custody so they're<00:11:20.100> gonna<00:11:20.220> be<00:11:20.370> big<00:11:20.550> players<00:11:20.790> so<00:11:21.060> there 00:11:21.320 --> 00:11:21.330 align:start position:0% they're gonna be big players so there 00:11:21.330 --> 00:11:25.490 align:start position:0% they're gonna be big players so there will<00:11:21.390> be<00:11:21.450> some<00:11:22.250> some<00:11:23.300> debate<00:11:24.300> over<00:11:24.510> their<00:11:25.080> role 00:11:25.490 --> 00:11:25.500 align:start position:0% will be some some debate over their role 00:11:25.500 --> 00:11:28.160 align:start position:0% will be some some debate over their role in<00:11:25.860> the<00:11:26.580> staking<00:11:26.940> economy<00:11:27.390> in<00:11:27.450> the<00:11:27.540> East<00:11:27.750> 2.0 00:11:28.160 --> 00:11:28.170 align:start position:0% in the staking economy in the East 2.0 00:11:28.170 --> 00:11:29.990 align:start position:0% in the staking economy in the East 2.0 but<00:11:28.710> second<00:11:29.070> of<00:11:29.100> all<00:11:29.220> remember<00:11:29.640> I<00:11:29.670> said<00:11:29.970> that 00:11:29.990 --> 00:11:30.000 align:start position:0% but second of all remember I said that 00:11:30.000 --> 00:11:32.030 align:start position:0% but second of all remember I said that validators<00:11:30.780> will<00:11:30.960> probably<00:11:31.320> enter<00:11:31.590> into<00:11:31.740> easy 00:11:32.030 --> 00:11:32.040 align:start position:0% validators will probably enter into easy 00:11:32.040 --> 00:11:35.120 align:start position:0% validators will probably enter into easy 2.0<00:11:32.550> as<00:11:32.700> note<00:11:32.940> as<00:11:33.090> a<00:11:33.120> service<00:11:33.510> well<00:11:34.230> imagine<00:11:34.530> if 00:11:35.120 --> 00:11:35.130 align:start position:0% 2.0 as note as a service well imagine if 00:11:35.130 --> 00:11:37.700 align:start position:0% 2.0 as note as a service well imagine if any<00:11:35.610> of<00:11:35.760> these<00:11:35.880> note<00:11:36.120> as<00:11:36.270> a<00:11:36.300> service<00:11:36.720> providers 00:11:37.700 --> 00:11:37.710 align:start position:0% any of these note as a service providers 00:11:37.710 --> 00:11:40.370 align:start position:0% any of these note as a service providers become<00:11:38.520> big<00:11:38.700> like<00:11:39.090> they<00:11:39.210> control<00:11:39.540> like<00:11:39.720> 50<00:11:40.230> 60 00:11:40.370 --> 00:11:40.380 align:start position:0% become big like they control like 50 60 00:11:40.380 --> 00:11:43.760 align:start position:0% become big like they control like 50 60 percent<00:11:40.860> of<00:11:40.920> the<00:11:41.040> market<00:11:42.290> imagine<00:11:43.290> that<00:11:43.470> they 00:11:43.760 --> 00:11:43.770 align:start position:0% percent of the market imagine that they 00:11:43.770 --> 00:11:46.130 align:start position:0% percent of the market imagine that they find<00:11:44.280> a<00:11:44.550> very<00:11:44.790> critical<00:11:45.150> bug<00:11:45.540> in<00:11:45.840> their 00:11:46.130 --> 00:11:46.140 align:start position:0% find a very critical bug in their 00:11:46.140 --> 00:11:48.380 align:start position:0% find a very critical bug in their infrastructure<00:11:46.740> what<00:11:47.340> that<00:11:47.490> means<00:11:47.730> is<00:11:47.940> then 00:11:48.380 --> 00:11:48.390 align:start position:0% infrastructure what that means is then 00:11:48.390 --> 00:11:51.830 align:start position:0% infrastructure what that means is then every<00:11:49.140> single<00:11:49.470> user<00:11:50.190> staking<00:11:51.000> using<00:11:51.570> their 00:11:51.830 --> 00:11:51.840 align:start position:0% every single user staking using their 00:11:51.840 --> 00:11:53.870 align:start position:0% every single user staking using their node<00:11:52.200> as<00:11:52.380> a<00:11:52.410> service<00:11:52.860> are<00:11:53.250> probably<00:11:53.580> likely 00:11:53.870 --> 00:11:53.880 align:start position:0% node as a service are probably likely 00:11:53.880 --> 00:11:55.730 align:start position:0% node as a service are probably likely going<00:11:54.180> to<00:11:54.240> be<00:11:54.300> compromised<00:11:54.840> so<00:11:55.320> it's<00:11:55.440> another 00:11:55.730 --> 00:11:55.740 align:start position:0% going to be compromised so it's another 00:11:55.740 --> 00:11:59.600 align:start position:0% going to be compromised so it's another point<00:11:56.160> of<00:11:56.310> failure<00:11:56.780> in<00:11:57.780> that<00:11:58.020> case<00:11:58.290> so<00:11:59.070> that's 00:11:59.600 --> 00:11:59.610 align:start position:0% point of failure in that case so that's 00:11:59.610 --> 00:12:02.390 align:start position:0% point of failure in that case so that's also<00:11:59.880> so<00:12:00.690> that's<00:12:01.110> somewhat<00:12:01.410> like<00:12:01.710> not<00:12:02.190> gonna 00:12:02.390 --> 00:12:02.400 align:start position:0% also so that's somewhat like not gonna 00:12:02.400 --> 00:12:05.210 align:start position:0% also so that's somewhat like not gonna be<00:12:02.550> as<00:12:03.020> forefront<00:12:04.020> as<00:12:04.170> you<00:12:04.680> know<00:12:04.770> seeing<00:12:05.070> an 00:12:05.210 --> 00:12:05.220 align:start position:0% be as forefront as you know seeing an 00:12:05.220 --> 00:12:07.730 align:start position:0% be as forefront as you know seeing an exchange<00:12:05.670> gain<00:12:06.090> like<00:12:06.330> five<00:12:06.630> six<00:12:07.080> percent<00:12:07.470> of<00:12:07.620> a 00:12:07.730 --> 00:12:07.740 align:start position:0% exchange gain like five six percent of a 00:12:07.740 --> 00:12:10.160 align:start position:0% exchange gain like five six percent of a networks<00:12:08.070> power<00:12:08.310> but<00:12:09.060> this<00:12:09.390> is<00:12:09.570> also<00:12:09.870> going<00:12:10.110> to 00:12:10.160 --> 00:12:10.170 align:start position:0% networks power but this is also going to 00:12:10.170 --> 00:12:13.010 align:start position:0% networks power but this is also going to be<00:12:10.230> a<00:12:10.290> very<00:12:10.530> crucial<00:12:11.300> centralization<00:12:12.300> failure 00:12:13.010 --> 00:12:13.020 align:start position:0% be a very crucial centralization failure 00:12:13.020 --> 00:12:15.200 align:start position:0% be a very crucial centralization failure point<00:12:13.260> that<00:12:13.680> will<00:12:13.890> be<00:12:14.160> neat<00:12:14.460> will<00:12:14.850> need<00:12:14.970> to<00:12:15.120> be 00:12:15.200 --> 00:12:15.210 align:start position:0% point that will be neat will need to be 00:12:15.210 --> 00:12:21.350 align:start position:0% point that will be neat will need to be vigilant<00:12:15.390> about<00:12:18.200> so<00:12:19.200> I<00:12:19.530> actually<00:12:20.210> took<00:12:21.210> this 00:12:21.350 --> 00:12:21.360 align:start position:0% vigilant about so I actually took this 00:12:21.360 --> 00:12:24.910 align:start position:0% vigilant about so I actually took this out<00:12:22.280> I've<00:12:23.280> put<00:12:23.790> it<00:12:23.910> as<00:12:24.030> a<00:12:24.060> separate<00:12:24.600> point 00:12:24.910 --> 00:12:24.920 align:start position:0% out I've put it as a separate point 00:12:24.920 --> 00:12:27.650 align:start position:0% out I've put it as a separate point because<00:12:25.920> this<00:12:26.280> is<00:12:26.460> very<00:12:27.180> crucial 00:12:27.650 --> 00:12:27.660 align:start position:0% because this is very crucial 00:12:27.660 --> 00:12:29.810 align:start position:0% because this is very crucial so<00:12:28.440> exchanges<00:12:28.950> are<00:12:29.220> finally<00:12:29.760> entering 00:12:29.810 --> 00:12:29.820 align:start position:0% so exchanges are finally entering 00:12:29.820 --> 00:12:32.150 align:start position:0% so exchanges are finally entering staking<00:12:30.720> you<00:12:30.960> know<00:12:31.080> I'm<00:12:31.500> quite<00:12:31.770> sure<00:12:31.860> many<00:12:32.010> of 00:12:32.150 --> 00:12:32.160 align:start position:0% staking you know I'm quite sure many of 00:12:32.160 --> 00:12:33.800 align:start position:0% staking you know I'm quite sure many of you<00:12:32.250> have<00:12:32.460> seen<00:12:32.670> how<00:12:32.850> by<00:12:33.060> Nance<00:12:33.300> announced 00:12:33.800 --> 00:12:33.810 align:start position:0% you have seen how by Nance announced 00:12:33.810 --> 00:12:34.880 align:start position:0% you have seen how by Nance announced that<00:12:33.900> they're<00:12:34.110> providing<00:12:34.530> staking 00:12:34.880 --> 00:12:34.890 align:start position:0% that they're providing staking 00:12:34.890 --> 00:12:38.630 align:start position:0% that they're providing staking operations<00:12:35.510> and<00:12:36.560> the<00:12:37.560> reason<00:12:37.800> why<00:12:37.890> staking<00:12:38.460> is 00:12:38.630 --> 00:12:38.640 align:start position:0% operations and the reason why staking is 00:12:38.640 --> 00:12:43.280 align:start position:0% operations and the reason why staking is so<00:12:40.910> exchanges<00:12:41.910> are<00:12:42.030> so<00:12:42.180> entering<00:12:42.870> two<00:12:42.990> staking 00:12:43.280 --> 00:12:43.290 align:start position:0% so exchanges are so entering two staking 00:12:43.290 --> 00:12:45.290 align:start position:0% so exchanges are so entering two staking is<00:12:43.380> crucial<00:12:43.680> is<00:12:43.770> because<00:12:44.040> they're<00:12:44.910> able<00:12:45.030> to 00:12:45.290 --> 00:12:45.300 align:start position:0% is crucial is because they're able to 00:12:45.300 --> 00:12:47.300 align:start position:0% is crucial is because they're able to provide<00:12:45.540> instant<00:12:46.110> liquidity<00:12:46.560> and<00:12:46.770> they 00:12:47.300 --> 00:12:47.310 align:start position:0% provide instant liquidity and they 00:12:47.310 --> 00:12:49.640 align:start position:0% provide instant liquidity and they actually<00:12:48.030> bypass<00:12:48.540> any<00:12:48.780> on<00:12:48.930> bonding<00:12:49.260> periods 00:12:49.640 --> 00:12:49.650 align:start position:0% actually bypass any on bonding periods 00:12:49.650 --> 00:12:52.280 align:start position:0% actually bypass any on bonding periods and<00:12:49.890> you<00:12:50.700> know<00:12:50.820> imagine<00:12:51.540> that<00:12:51.810> you<00:12:51.990> know<00:12:52.080> like 00:12:52.280 --> 00:12:52.290 align:start position:0% and you know imagine that you know like 00:12:52.290 --> 00:12:54.380 align:start position:0% and you know imagine that you know like if<00:12:52.710> you're<00:12:52.920> trying<00:12:53.160> to<00:12:53.190> stake<00:12:53.460> on<00:12:53.610> a<00:12:53.640> ES<00:12:53.910> 2.0 00:12:54.380 --> 00:12:54.390 align:start position:0% if you're trying to stake on a ES 2.0 00:12:54.390 --> 00:12:56.120 align:start position:0% if you're trying to stake on a ES 2.0 and<00:12:54.600> you<00:12:54.780> don't<00:12:54.960> need<00:12:55.110> to<00:12:55.170> lock<00:12:55.470> up<00:12:55.680> your<00:12:55.860> ease 00:12:56.120 --> 00:12:56.130 align:start position:0% and you don't need to lock up your ease 00:12:56.130 --> 00:12:58.340 align:start position:0% and you don't need to lock up your ease you<00:12:56.670> just<00:12:56.820> keep<00:12:57.030> it<00:12:57.210> on<00:12:57.360> a<00:12:57.390> low<00:12:57.990> exchange 00:12:58.340 --> 00:12:58.350 align:start position:0% you just keep it on a low exchange 00:12:58.350 --> 00:13:00.440 align:start position:0% you just keep it on a low exchange wallet<00:12:58.800> and<00:12:58.920> you<00:12:59.010> instantly<00:12:59.460> get<00:12:59.790> each<00:13:00.030> drop 00:13:00.440 --> 00:13:00.450 align:start position:0% wallet and you instantly get each drop 00:13:00.450 --> 00:13:02.210 align:start position:0% wallet and you instantly get each drop to<00:13:00.600> your<00:13:00.720> wallet<00:13:00.960> like<00:13:01.350> how<00:13:01.560> convenient<00:13:02.100> is 00:13:02.210 --> 00:13:02.220 align:start position:0% to your wallet like how convenient is 00:13:02.220 --> 00:13:02.420 align:start position:0% to your wallet like how convenient is that 00:13:02.420 --> 00:13:02.430 align:start position:0% that 00:13:02.430 --> 00:13:06.560 align:start position:0% that and<00:13:02.960> so<00:13:03.960> therefore<00:13:04.640> this<00:13:05.640> is<00:13:05.820> this<00:13:06.360> is<00:13:06.540> a 00:13:06.560 --> 00:13:06.570 align:start position:0% and so therefore this is this is a 00:13:06.570 --> 00:13:08.600 align:start position:0% and so therefore this is this is a really<00:13:07.140> problematic<00:13:07.320> especially<00:13:07.950> for 00:13:08.600 --> 00:13:08.610 align:start position:0% really problematic especially for 00:13:08.610 --> 00:13:10.700 align:start position:0% really problematic especially for independent<00:13:09.210> validators<00:13:09.660> like<00:13:09.840> us<00:13:10.050> because 00:13:10.700 --> 00:13:10.710 align:start position:0% independent validators like us because 00:13:10.710 --> 00:13:12.320 align:start position:0% independent validators like us because we're<00:13:10.980> not<00:13:11.070> really<00:13:11.400> able<00:13:11.730> to<00:13:11.820> compete<00:13:12.150> with 00:13:12.320 --> 00:13:12.330 align:start position:0% we're not really able to compete with 00:13:12.330 --> 00:13:14.000 align:start position:0% we're not really able to compete with these<00:13:12.570> exchanges<00:13:13.110> that<00:13:13.230> are<00:13:13.380> able<00:13:13.650> to<00:13:13.770> bypass 00:13:14.000 --> 00:13:14.010 align:start position:0% these exchanges that are able to bypass 00:13:14.010 --> 00:13:17.510 align:start position:0% these exchanges that are able to bypass these<00:13:14.790> liquidity<00:13:15.420> issues<00:13:15.870> oh<00:13:16.310> yeah<00:13:17.310> and 00:13:17.510 --> 00:13:17.520 align:start position:0% these liquidity issues oh yeah and 00:13:17.520 --> 00:13:19.130 align:start position:0% these liquidity issues oh yeah and there's<00:13:17.700> like<00:13:17.880> your<00:13:18.420> street<00:13:18.660> points<00:13:18.870> on<00:13:18.960> how 00:13:19.130 --> 00:13:19.140 align:start position:0% there's like your street points on how 00:13:19.140 --> 00:13:23.180 align:start position:0% there's like your street points on how exchanges<00:13:19.680> are<00:13:19.770> entering<00:13:20.610> I'll<00:13:21.980> please<00:13:22.980> come 00:13:23.180 --> 00:13:23.190 align:start position:0% exchanges are entering I'll please come 00:13:23.190 --> 00:13:24.440 align:start position:0% exchanges are entering I'll please come up<00:13:23.310> to<00:13:23.400> me<00:13:23.490> if<00:13:23.580> you<00:13:23.670> want<00:13:23.850> to<00:13:23.910> understand<00:13:24.330> more 00:13:24.440 --> 00:13:24.450 align:start position:0% up to me if you want to understand more 00:13:24.450 --> 00:13:25.879 align:start position:0% up to me if you want to understand more about<00:13:24.510> how<00:13:24.780> exchanges<00:13:25.320> are<00:13:25.440> entering 00:13:25.879 --> 00:13:25.889 align:start position:0% about how exchanges are entering 00:13:25.889 --> 00:13:29.329 align:start position:0% about how exchanges are entering right<00:13:26.069> now<00:13:26.209> so<00:13:27.209> as<00:13:28.109> I<00:13:28.290> mentioned<00:13:28.649> the<00:13:28.920> the 00:13:29.329 --> 00:13:29.339 align:start position:0% right now so as I mentioned the the 00:13:29.339 --> 00:13:31.910 align:start position:0% right now so as I mentioned the the important<00:13:29.939> part<00:13:30.089> for<00:13:30.290> the<00:13:31.290> poor<00:13:31.559> part<00:13:31.769> about 00:13:31.910 --> 00:13:31.920 align:start position:0% important part for the poor part about 00:13:31.920 --> 00:13:34.099 align:start position:0% important part for the poor part about like<00:13:32.129> of<00:13:32.879> tackling<00:13:33.480> this<00:13:33.629> is<00:13:33.899> that 00:13:34.099 --> 00:13:34.109 align:start position:0% like of tackling this is that 00:13:34.109 --> 00:13:36.410 align:start position:0% like of tackling this is that independent<00:13:35.040> validators<00:13:35.730> like<00:13:35.879> us<00:13:36.089> need<00:13:36.389> to 00:13:36.410 --> 00:13:36.420 align:start position:0% independent validators like us need to 00:13:36.420 --> 00:13:37.970 align:start position:0% independent validators like us need to be<00:13:36.600> able<00:13:36.689> to<00:13:36.899> compete<00:13:37.199> with<00:13:37.379> these<00:13:37.529> guys<00:13:37.739> and 00:13:37.970 --> 00:13:37.980 align:start position:0% be able to compete with these guys and 00:13:37.980 --> 00:13:39.439 align:start position:0% be able to compete with these guys and the<00:13:38.100> only<00:13:38.309> way<00:13:38.549> we<00:13:38.730> could<00:13:38.850> do<00:13:38.999> that<00:13:39.149> is<00:13:39.420> if 00:13:39.439 --> 00:13:39.449 align:start position:0% the only way we could do that is if 00:13:39.449 --> 00:13:41.210 align:start position:0% the only way we could do that is if there's<00:13:39.959> a<00:13:40.019> way<00:13:40.199> where<00:13:40.499> we<00:13:40.829> could<00:13:40.980> offer 00:13:41.210 --> 00:13:41.220 align:start position:0% there's a way where we could offer 00:13:41.220 --> 00:13:43.460 align:start position:0% there's a way where we could offer people<00:13:41.970> who<00:13:42.059> delegate<00:13:42.569> to<00:13:42.749> us<00:13:42.899> who<00:13:43.049> stake<00:13:43.290> with 00:13:43.460 --> 00:13:43.470 align:start position:0% people who delegate to us who stake with 00:13:43.470 --> 00:13:47.179 align:start position:0% people who delegate to us who stake with us<00:13:43.939> have<00:13:44.939> similar<00:13:45.629> liquidity<00:13:46.379> you<00:13:47.069> know 00:13:47.179 --> 00:13:47.189 align:start position:0% us have similar liquidity you know 00:13:47.189 --> 00:13:48.949 align:start position:0% us have similar liquidity you know liquidity<00:13:47.939> wonder<00:13:48.299> when<00:13:48.569> they're<00:13:48.720> staking 00:13:48.949 --> 00:13:48.959 align:start position:0% liquidity wonder when they're staking 00:13:48.959 --> 00:13:51.139 align:start position:0% liquidity wonder when they're staking and<00:13:49.259> so<00:13:49.619> therefore<00:13:49.799> I<00:13:49.949> see<00:13:50.309> staking 00:13:51.139 --> 00:13:51.149 align:start position:0% and so therefore I see staking 00:13:51.149 --> 00:13:54.379 align:start position:0% and so therefore I see staking derivatives<00:13:51.600> again<00:13:52.199> defy<00:13:53.069> playing<00:13:54.059> a<00:13:54.149> key 00:13:54.379 --> 00:13:54.389 align:start position:0% derivatives again defy playing a key 00:13:54.389 --> 00:13:56.090 align:start position:0% derivatives again defy playing a key role<00:13:54.419> here<00:13:54.839> there<00:13:55.049> are<00:13:55.139> a<00:13:55.169> few<00:13:55.589> players<00:13:55.859> right 00:13:56.090 --> 00:13:56.100 align:start position:0% role here there are a few players right 00:13:56.100 --> 00:13:59.179 align:start position:0% role here there are a few players right now<00:13:56.249> trying<00:13:56.609> to<00:13:56.790> tackle<00:13:57.089> this<00:13:57.329> and<00:13:58.169> so<00:13:58.439> once 00:13:59.179 --> 00:13:59.189 align:start position:0% now trying to tackle this and so once 00:13:59.189 --> 00:14:01.069 align:start position:0% now trying to tackle this and so once staking<00:14:00.149> derivatives<00:14:00.540> are<00:14:00.629> alive 00:14:01.069 --> 00:14:01.079 align:start position:0% staking derivatives are alive 00:14:01.079 --> 00:14:03.139 align:start position:0% staking derivatives are alive that<00:14:01.350> will<00:14:01.499> then<00:14:01.529> help<00:14:01.709> us<00:14:02.220> Valladares 00:14:03.139 --> 00:14:03.149 align:start position:0% that will then help us Valladares 00:14:03.149 --> 00:14:05.419 align:start position:0% that will then help us Valladares actually<00:14:03.749> compete<00:14:04.529> with<00:14:04.709> exchanges<00:14:05.279> and 00:14:05.419 --> 00:14:05.429 align:start position:0% actually compete with exchanges and 00:14:05.429 --> 00:14:08.030 align:start position:0% actually compete with exchanges and that's<00:14:05.639> what<00:14:05.970> that's<00:14:06.239> key<00:14:06.509> here<00:14:06.809> I<00:14:07.259> think<00:14:07.889> that 00:14:08.030 --> 00:14:08.040 align:start position:0% that's what that's key here I think that 00:14:08.040 --> 00:14:11.150 align:start position:0% that's what that's key here I think that that's<00:14:08.369> how<00:14:08.730> I<00:14:09.449> don't<00:14:10.049> expect<00:14:10.410> Valladares<00:14:10.980> to 00:14:11.150 --> 00:14:11.160 align:start position:0% that's how I don't expect Valladares to 00:14:11.160 --> 00:14:13.609 align:start position:0% that's how I don't expect Valladares to be<00:14:11.249> treated<00:14:11.669> more<00:14:11.850> favorably<00:14:12.209> in<00:14:12.600> compared<00:14:13.559> to 00:14:13.609 --> 00:14:13.619 align:start position:0% be treated more favorably in compared to 00:14:13.619 --> 00:14:15.379 align:start position:0% be treated more favorably in compared to exchanges<00:14:14.309> but<00:14:14.429> at<00:14:14.579> the<00:14:14.669> very<00:14:14.790> least<00:14:15.029> we<00:14:15.239> could 00:14:15.379 --> 00:14:15.389 align:start position:0% exchanges but at the very least we could 00:14:15.389 --> 00:14:18.169 align:start position:0% exchanges but at the very least we could level<00:14:15.749> the<00:14:15.959> playing<00:14:16.230> field<00:14:16.699> by<00:14:17.699> providing 00:14:18.169 --> 00:14:18.179 align:start position:0% level the playing field by providing 00:14:18.179 --> 00:14:22.009 align:start position:0% level the playing field by providing staking<00:14:18.600> derivatives<00:14:19.049> and<00:14:20.009> so<00:14:20.629> this<00:14:21.629> is<00:14:21.839> just 00:14:22.009 --> 00:14:22.019 align:start position:0% staking derivatives and so this is just 00:14:22.019 --> 00:14:24.259 align:start position:0% staking derivatives and so this is just one<00:14:22.350> a<00:14:22.619> way<00:14:22.949> of<00:14:23.189> sort<00:14:23.519> of<00:14:23.609> tackling<00:14:24.089> the 00:14:24.259 --> 00:14:24.269 align:start position:0% one a way of sort of tackling the 00:14:24.269 --> 00:14:27.049 align:start position:0% one a way of sort of tackling the exchange<00:14:25.489> centralization<00:14:26.489> issue<00:14:26.669> of 00:14:27.049 --> 00:14:27.059 align:start position:0% exchange centralization issue of 00:14:27.059 --> 00:14:29.389 align:start position:0% exchange centralization issue of regarding<00:14:27.449> staking<00:14:27.809> but<00:14:28.019> I<00:14:28.290> welcome<00:14:29.100> anyone 00:14:29.389 --> 00:14:29.399 align:start position:0% regarding staking but I welcome anyone 00:14:29.399 --> 00:14:31.569 align:start position:0% regarding staking but I welcome anyone to<00:14:29.579> think<00:14:29.609> of<00:14:29.939> any<00:14:30.480> alternatives<00:14:31.139> to<00:14:31.259> try<00:14:31.499> to 00:14:31.569 --> 00:14:31.579 align:start position:0% to think of any alternatives to try to 00:14:31.579 --> 00:14:34.850 align:start position:0% to think of any alternatives to try to see<00:14:32.579> where<00:14:32.819> we<00:14:33.509> could<00:14:33.779> compete<00:14:34.230> better<00:14:34.679> with 00:14:34.850 --> 00:14:34.860 align:start position:0% see where we could compete better with 00:14:34.860 --> 00:14:38.720 align:start position:0% see where we could compete better with exchanges<00:14:35.819> when<00:14:36.029> it<00:14:36.179> comes<00:14:36.360> to<00:14:36.509> staking<00:14:37.730> so 00:14:38.720 --> 00:14:38.730 align:start position:0% exchanges when it comes to staking so 00:14:38.730 --> 00:14:42.319 align:start position:0% exchanges when it comes to staking so finally<00:14:39.470> this<00:14:40.470> is<00:14:40.529> a<00:14:41.279> topic<00:14:41.730> that<00:14:41.759> no<00:14:42.209> one 00:14:42.319 --> 00:14:42.329 align:start position:0% finally this is a topic that no one 00:14:42.329 --> 00:14:44.869 align:start position:0% finally this is a topic that no one likes<00:14:42.540> to<00:14:42.720> talk<00:14:42.899> about<00:14:43.079> but<00:14:43.499> that<00:14:44.249> we 00:14:44.869 --> 00:14:44.879 align:start position:0% likes to talk about but that we 00:14:44.879 --> 00:14:47.809 align:start position:0% likes to talk about but that we seriously<00:14:45.329> need<00:14:45.540> to<00:14:46.369> there<00:14:47.369> needs<00:14:47.579> to<00:14:47.669> be<00:14:47.730> a 00:14:47.809 --> 00:14:47.819 align:start position:0% seriously need to there needs to be a 00:14:47.819 --> 00:14:49.220 align:start position:0% seriously need to there needs to be a working<00:14:48.119> group<00:14:48.179> around<00:14:48.509> this<00:14:48.660> it's 00:14:49.220 --> 00:14:49.230 align:start position:0% working group around this it's 00:14:49.230 --> 00:14:51.499 align:start position:0% working group around this it's regulation<00:14:49.860> and<00:14:50.009> Taxation<00:14:50.519> proof-of-work 00:14:51.499 --> 00:14:51.509 align:start position:0% regulation and Taxation proof-of-work 00:14:51.509 --> 00:14:53.600 align:start position:0% regulation and Taxation proof-of-work mining<00:14:52.139> has<00:14:52.290> been<00:14:52.439> around<00:14:52.679> so<00:14:52.980> there<00:14:53.429> has<00:14:53.579> been 00:14:53.600 --> 00:14:53.610 align:start position:0% mining has been around so there has been 00:14:53.610 --> 00:14:57.079 align:start position:0% mining has been around so there has been some<00:14:53.790> framework<00:14:55.069> constructed<00:14:56.069> around<00:14:56.279> how 00:14:57.079 --> 00:14:57.089 align:start position:0% some framework constructed around how 00:14:57.089 --> 00:14:59.269 align:start position:0% some framework constructed around how mining<00:14:57.569> and<00:14:57.809> mining<00:14:58.199> words<00:14:58.739> should<00:14:59.249> be 00:14:59.269 --> 00:14:59.279 align:start position:0% mining and mining words should be 00:14:59.279 --> 00:15:03.019 align:start position:0% mining and mining words should be considered<00:15:00.149> but<00:15:00.739> you<00:15:01.739> know<00:15:01.860> we<00:15:02.279> can't<00:15:02.579> assume 00:15:03.019 --> 00:15:03.029 align:start position:0% considered but you know we can't assume 00:15:03.029 --> 00:15:05.989 align:start position:0% considered but you know we can't assume that<00:15:03.089> proof<00:15:03.749> of<00:15:03.869> stake<00:15:04.309> staking<00:15:05.309> and<00:15:05.489> staking 00:15:05.989 --> 00:15:05.999 align:start position:0% that proof of stake staking and staking 00:15:05.999 --> 00:15:07.989 align:start position:0% that proof of stake staking and staking Wars<00:15:06.360> will<00:15:06.509> be<00:15:06.540> considered<00:15:07.019> the<00:15:07.139> same<00:15:07.319> way 00:15:07.989 --> 00:15:07.999 align:start position:0% Wars will be considered the same way 00:15:07.999 --> 00:15:10.699 align:start position:0% Wars will be considered the same way like<00:15:08.999> as<00:15:09.149> an<00:15:09.299> example<00:15:09.600> like<00:15:09.959> let's<00:15:10.529> say<00:15:10.679> a 00:15:10.699 --> 00:15:10.709 align:start position:0% like as an example like let's say a 00:15:10.709 --> 00:15:12.229 align:start position:0% like as an example like let's say a proof<00:15:11.009> of<00:15:11.160> stake<00:15:11.339> staking<00:15:11.850> words<00:15:11.999> will 00:15:12.229 --> 00:15:12.239 align:start position:0% proof of stake staking words will 00:15:12.239 --> 00:15:14.629 align:start position:0% proof of stake staking words will eventually<00:15:12.660> be<00:15:12.779> taxed<00:15:13.230> will<00:15:13.949> it<00:15:14.100> be<00:15:14.220> taxed 00:15:14.629 --> 00:15:14.639 align:start position:0% eventually be taxed will it be taxed 00:15:14.639 --> 00:15:16.460 align:start position:0% eventually be taxed will it be taxed once<00:15:14.850> I<00:15:15.119> get<00:15:15.449> to<00:15:15.600> staking<00:15:15.959> Awards<00:15:16.199> in<00:15:16.319> my 00:15:16.460 --> 00:15:16.470 align:start position:0% once I get to staking Awards in my 00:15:16.470 --> 00:15:18.439 align:start position:0% once I get to staking Awards in my wallet<00:15:16.769> or<00:15:16.919> will<00:15:17.429> it<00:15:17.549> be<00:15:17.610> taxed<00:15:18.119> once<00:15:18.299> I 00:15:18.439 --> 00:15:18.449 align:start position:0% wallet or will it be taxed once I 00:15:18.449 --> 00:15:20.179 align:start position:0% wallet or will it be taxed once I liquidate<00:15:18.689> it<00:15:19.049> into<00:15:19.379> like<00:15:19.589> a<00:15:19.619> nerd<00:15:19.860> a<00:15:19.949> coin 00:15:20.179 --> 00:15:20.189 align:start position:0% liquidate it into like a nerd a coin 00:15:20.189 --> 00:15:22.909 align:start position:0% liquidate it into like a nerd a coin like<00:15:20.489> these<00:15:20.819> are<00:15:20.939> questions<00:15:21.179> that<00:15:21.480> are<00:15:22.410> still 00:15:22.909 --> 00:15:22.919 align:start position:0% like these are questions that are still 00:15:22.919 --> 00:15:24.229 align:start position:0% like these are questions that are still up<00:15:23.069> in<00:15:23.189> the<00:15:23.249> air<00:15:23.369> and<00:15:23.609> no<00:15:23.759> one<00:15:23.910> knows<00:15:24.059> the 00:15:24.229 --> 00:15:24.239 align:start position:0% up in the air and no one knows the 00:15:24.239 --> 00:15:28.519 align:start position:0% up in the air and no one knows the answers<00:15:24.539> to<00:15:25.160> so<00:15:26.160> there<00:15:26.910> is<00:15:27.149> a<00:15:27.179> POS<00:15:27.899> Alliance 00:15:28.519 --> 00:15:28.529 align:start position:0% answers to so there is a POS Alliance 00:15:28.529 --> 00:15:30.349 align:start position:0% answers to so there is a POS Alliance proof<00:15:28.709> of<00:15:28.829> stake<00:15:29.009> Alliance<00:15:29.429> has<00:15:29.730> been<00:15:29.910> created 00:15:30.349 --> 00:15:30.359 align:start position:0% proof of stake Alliance has been created 00:15:30.359 --> 00:15:33.049 align:start position:0% proof of stake Alliance has been created with<00:15:30.539> a<00:15:30.779> few<00:15:31.139> key<00:15:31.679> players<00:15:32.249> in<00:15:32.489> the<00:15:32.609> staking 00:15:33.049 --> 00:15:33.059 align:start position:0% with a few key players in the staking 00:15:33.059 --> 00:15:37.039 align:start position:0% with a few key players in the staking staking<00:15:33.839> world<00:15:34.019> I<00:15:34.829> also<00:15:35.579> do<00:15:35.819> encourage<00:15:36.209> the 00:15:37.039 --> 00:15:37.049 align:start position:0% staking world I also do encourage the 00:15:37.049 --> 00:15:39.229 align:start position:0% staking world I also do encourage the Durham<00:15:37.350> community<00:15:37.499> to<00:15:37.829> think<00:15:37.980> about<00:15:38.309> how<00:15:38.549> we 00:15:39.229 --> 00:15:39.239 align:start position:0% Durham community to think about how we 00:15:39.239 --> 00:15:39.500 align:start position:0% Durham community to think about how we could 00:15:39.500 --> 00:15:39.510 align:start position:0% could 00:15:39.510 --> 00:15:43.940 align:start position:0% could engage<00:15:40.610> policymakers<00:15:41.610> and<00:15:42.470> and<00:15:43.470> regulators 00:15:43.940 --> 00:15:43.950 align:start position:0% engage policymakers and and regulators 00:15:43.950 --> 00:15:46.210 align:start position:0% engage policymakers and and regulators around<00:15:44.340> house<00:15:44.550> taking<00:15:45.120> should<00:15:45.300> be<00:15:45.420> considered 00:15:46.210 --> 00:15:46.220 align:start position:0% around house taking should be considered 00:15:46.220 --> 00:15:49.460 align:start position:0% around house taking should be considered because<00:15:47.220> if<00:15:47.580> this<00:15:48.060> stack<00:15:48.600> is<00:15:48.780> not<00:15:48.810> figured<00:15:49.350> out 00:15:49.460 --> 00:15:49.470 align:start position:0% because if this stack is not figured out 00:15:49.470 --> 00:15:53.090 align:start position:0% because if this stack is not figured out like<00:15:50.240> you<00:15:51.240> know<00:15:51.270> Valladares<00:15:52.140> takers<00:15:52.590> everyone 00:15:53.090 --> 00:15:53.100 align:start position:0% like you know Valladares takers everyone 00:15:53.100 --> 00:15:54.610 align:start position:0% like you know Valladares takers everyone alike<00:15:53.370> is<00:15:53.610> gonna<00:15:53.820> be<00:15:53.940> in<00:15:54.000> a<00:15:54.090> heap<00:15:54.300> of 00:15:54.610 --> 00:15:54.620 align:start position:0% alike is gonna be in a heap of 00:15:54.620 --> 00:15:58.790 align:start position:0% alike is gonna be in a heap of regulatory<00:15:55.620> issues<00:15:56.780> so<00:15:57.780> I<00:15:58.110> think<00:15:58.500> it's 00:15:58.790 --> 00:15:58.800 align:start position:0% regulatory issues so I think it's 00:15:58.800 --> 00:16:04.280 align:start position:0% regulatory issues so I think it's important<00:15:59.370> that<00:15:59.400> we<00:15:59.610> we<00:16:01.340> we<00:16:02.340> actually<00:16:02.610> take<00:16:03.290> we 00:16:04.280 --> 00:16:04.290 align:start position:0% important that we we we actually take we 00:16:04.290 --> 00:16:06.410 align:start position:0% important that we we we actually take we take<00:16:04.470> a<00:16:04.500> proactive<00:16:04.770> approach<00:16:05.220> I<00:16:05.700> try<00:16:06.120> to<00:16:06.180> talk 00:16:06.410 --> 00:16:06.420 align:start position:0% take a proactive approach I try to talk 00:16:06.420 --> 00:16:07.760 align:start position:0% take a proactive approach I try to talk with<00:16:06.660> policymakers<00:16:07.320> on<00:16:07.440> what<00:16:07.620> they're 00:16:07.760 --> 00:16:07.770 align:start position:0% with policymakers on what they're 00:16:07.770 --> 00:16:09.230 align:start position:0% with policymakers on what they're thinking<00:16:07.920> and<00:16:08.250> how<00:16:08.400> we<00:16:08.460> could<00:16:08.790> make<00:16:09.030> it 00:16:09.230 --> 00:16:09.240 align:start position:0% thinking and how we could make it 00:16:09.240 --> 00:16:12.230 align:start position:0% thinking and how we could make it comfortable<00:16:09.870> such<00:16:10.230> that<00:16:10.470> they<00:16:10.830> make<00:16:11.240> reasoned 00:16:12.230 --> 00:16:12.240 align:start position:0% comfortable such that they make reasoned 00:16:12.240 --> 00:16:15.650 align:start position:0% comfortable such that they make reasoned and<00:16:12.420> logical<00:16:13.050> decisions<00:16:13.560> on<00:16:13.740> how<00:16:14.660> staking 00:16:15.650 --> 00:16:15.660 align:start position:0% and logical decisions on how staking 00:16:15.660 --> 00:16:17.240 align:start position:0% and logical decisions on how staking should<00:16:15.840> be<00:16:15.930> taxed<00:16:16.350> how<00:16:16.530> staking<00:16:17.010> should<00:16:17.160> be 00:16:17.240 --> 00:16:17.250 align:start position:0% should be taxed how staking should be 00:16:17.250 --> 00:16:21.440 align:start position:0% should be taxed how staking should be regulated<00:16:18.110> so<00:16:19.220> yeah<00:16:20.220> so<00:16:20.760> those<00:16:21.060> are<00:16:21.210> sort<00:16:21.330> of 00:16:21.440 --> 00:16:21.450 align:start position:0% regulated so yeah so those are sort of 00:16:21.450 --> 00:16:23.090 align:start position:0% regulated so yeah so those are sort of the<00:16:21.630> five<00:16:21.930> key<00:16:22.170> lessons<00:16:22.470> I<00:16:22.560> wanted<00:16:22.800> to<00:16:22.890> share 00:16:23.090 --> 00:16:23.100 align:start position:0% the five key lessons I wanted to share 00:16:23.100 --> 00:16:25.040 align:start position:0% the five key lessons I wanted to share with<00:16:23.280> you<00:16:23.430> guys<00:16:23.490> and<00:16:23.790> hopefully<00:16:23.970> that<00:16:24.330> one 00:16:25.040 --> 00:16:25.050 align:start position:0% with you guys and hopefully that one 00:16:25.050 --> 00:16:27.260 align:start position:0% with you guys and hopefully that one sees<00:16:25.290> 2.0<00:16:25.770> launches<00:16:26.130> we<00:16:26.280> have<00:16:26.460> some<00:16:27.030> answers 00:16:27.260 --> 00:16:27.270 align:start position:0% sees 2.0 launches we have some answers 00:16:27.270 --> 00:16:29.390 align:start position:0% sees 2.0 launches we have some answers to<00:16:27.660> we<00:16:28.110> might<00:16:28.230> not<00:16:28.380> have<00:16:28.620> answers<00:16:28.890> to<00:16:28.950> all<00:16:29.190> but 00:16:29.390 --> 00:16:29.400 align:start position:0% to we might not have answers to all but 00:16:29.400 --> 00:16:32.060 align:start position:0% to we might not have answers to all but hopefully<00:16:29.760> most<00:16:30.150> of<00:16:30.270> them<00:16:30.420> I<00:16:31.200> loves<00:16:31.680> talking 00:16:32.060 --> 00:16:32.070 align:start position:0% hopefully most of them I loves talking 00:16:32.070 --> 00:16:33.830 align:start position:0% hopefully most of them I loves talking about<00:16:32.220> staking<00:16:32.700> I'm<00:16:32.880> happy<00:16:33.330> to<00:16:33.450> share<00:16:33.630> any 00:16:33.830 --> 00:16:33.840 align:start position:0% about staking I'm happy to share any 00:16:33.840 --> 00:16:36.740 align:start position:0% about staking I'm happy to share any knowledge<00:16:34.020> insight<00:16:34.710> on<00:16:35.090> what<00:16:36.090> we've<00:16:36.300> how 00:16:36.740 --> 00:16:36.750 align:start position:0% knowledge insight on what we've how 00:16:36.750 --> 00:16:38.600 align:start position:0% knowledge insight on what we've how we've<00:16:36.900> operated<00:16:37.170> so<00:16:37.500> far<00:16:37.710> so<00:16:37.890> please<00:16:38.400> feel 00:16:38.600 --> 00:16:38.610 align:start position:0% we've operated so far so please feel 00:16:38.610 --> 00:16:42.320 align:start position:0% we've operated so far so please feel free<00:16:38.640> to<00:16:38.880> reach<00:16:39.090> out<00:16:39.270> to<00:16:39.330> me<00:16:39.600> on<00:16:40.110> Twitter<00:16:40.320> on<00:16:41.330> by 00:16:42.320 --> 00:16:42.330 align:start position:0% free to reach out to me on Twitter on by 00:16:42.330 --> 00:16:45.950 align:start position:0% free to reach out to me on Twitter on by email<00:16:42.690> or<00:16:42.740> or<00:16:43.740> yeah<00:16:43.860> I<00:16:44.120> think<00:16:45.120> that's<00:16:45.390> it<00:16:45.510> I 00:16:45.950 --> 00:16:45.960 align:start position:0% email or or yeah I think that's it I 00:16:45.960 --> 00:16:47.720 align:start position:0% email or or yeah I think that's it I guess<00:16:46.290> I'll<00:16:46.500> take<00:16:46.740> questions<00:16:46.980> if<00:16:47.520> there<00:16:47.700> are 00:16:47.720 --> 00:16:47.730 align:start position:0% guess I'll take questions if there are 00:16:47.730 --> 00:16:58.650 align:start position:0% guess I'll take questions if there are any 00:16:58.650 --> 00:16:58.660 align:start position:0% 00:16:58.660 --> 00:17:00.720 align:start position:0% you