WEBVTT Kind: captions Language: en 00:00:03.850 --> 00:00:07.150 align:start position:0% thank<00:00:04.850> you<00:00:04.970> everyone<00:00:05.210> for<00:00:05.330> for<00:00:05.899> joining<00:00:06.160> today 00:00:07.150 --> 00:00:07.160 align:start position:0% thank you everyone for for joining today 00:00:07.160 --> 00:00:09.100 align:start position:0% thank you everyone for for joining today we're<00:00:07.310> gonna<00:00:07.430> talk<00:00:07.670> about<00:00:07.879> how<00:00:08.780> to<00:00:08.840> onboard 00:00:09.100 --> 00:00:09.110 align:start position:0% we're gonna talk about how to onboard 00:00:09.110 --> 00:00:13.449 align:start position:0% we're gonna talk about how to onboard ace<00:00:09.740> taking<00:00:10.280> user<00:00:10.490> in<00:00:10.850> under<00:00:11.389> five<00:00:11.869> minutes 00:00:13.449 --> 00:00:13.459 align:start position:0% ace taking user in under five minutes 00:00:13.459 --> 00:00:15.820 align:start position:0% ace taking user in under five minutes but<00:00:13.730> first<00:00:13.879> a<00:00:14.000> quick<00:00:14.209> introduction<00:00:14.650> my<00:00:15.650> name 00:00:15.820 --> 00:00:15.830 align:start position:0% but first a quick introduction my name 00:00:15.830 --> 00:00:18.160 align:start position:0% but first a quick introduction my name is<00:00:15.980> Adam<00:00:16.369> I<00:00:16.609> grew<00:00:17.570> up<00:00:17.630> in<00:00:17.810> New<00:00:17.960> Haven 00:00:18.160 --> 00:00:18.170 align:start position:0% is Adam I grew up in New Haven 00:00:18.170 --> 00:00:20.470 align:start position:0% is Adam I grew up in New Haven Connecticut<00:00:18.529> I<00:00:19.190> currently<00:00:19.759> live<00:00:20.029> in<00:00:20.150> Brooklyn 00:00:20.470 --> 00:00:20.480 align:start position:0% Connecticut I currently live in Brooklyn 00:00:20.480 --> 00:00:23.109 align:start position:0% Connecticut I currently live in Brooklyn I<00:00:20.810> got<00:00:21.529> involved<00:00:21.769> in<00:00:22.009> live<00:00:22.220> pier<00:00:22.669> pretty<00:00:22.999> early 00:00:23.109 --> 00:00:23.119 align:start position:0% I got involved in live pier pretty early 00:00:23.119 --> 00:00:25.689 align:start position:0% I got involved in live pier pretty early on<00:00:23.320> building<00:00:24.320> products<00:00:24.980> and<00:00:25.099> tools<00:00:25.249> for<00:00:25.580> the 00:00:25.689 --> 00:00:25.699 align:start position:0% on building products and tools for the 00:00:25.699 --> 00:00:28.710 align:start position:0% on building products and tools for the community<00:00:26.210> and<00:00:26.710> these<00:00:27.710> days<00:00:27.980> I'm<00:00:28.279> doing 00:00:28.710 --> 00:00:28.720 align:start position:0% community and these days I'm doing 00:00:28.720 --> 00:00:31.239 align:start position:0% community and these days I'm doing product<00:00:29.720> engineering<00:00:30.499> and<00:00:30.740> design<00:00:30.980> with<00:00:31.220> a 00:00:31.239 --> 00:00:31.249 align:start position:0% product engineering and design with a 00:00:31.249 --> 00:00:33.280 align:start position:0% product engineering and design with a real<00:00:31.909> focus<00:00:32.119> on<00:00:32.480> the<00:00:32.660> token<00:00:33.050> holder 00:00:33.280 --> 00:00:33.290 align:start position:0% real focus on the token holder 00:00:33.290 --> 00:00:34.770 align:start position:0% real focus on the token holder experience 00:00:34.770 --> 00:00:34.780 align:start position:0% experience 00:00:34.780 --> 00:00:39.010 align:start position:0% experience hi<00:00:35.780> I'm<00:00:36.110> Swan<00:00:36.500> I<00:00:37.090> was<00:00:38.090> born<00:00:38.300> in<00:00:38.390> China<00:00:38.600> I<00:00:38.810> grew 00:00:39.010 --> 00:00:39.020 align:start position:0% hi I'm Swan I was born in China I grew 00:00:39.020 --> 00:00:41.500 align:start position:0% hi I'm Swan I was born in China I grew up<00:00:39.080> in<00:00:39.230> Texas<00:00:39.470> and<00:00:39.980> now<00:00:40.520> I'm<00:00:40.670> in<00:00:40.820> San<00:00:40.940> Francisco 00:00:41.500 --> 00:00:41.510 align:start position:0% up in Texas and now I'm in San Francisco 00:00:41.510 --> 00:00:43.000 align:start position:0% up in Texas and now I'm in San Francisco and<00:00:41.720> how<00:00:42.290> I<00:00:42.320> heard<00:00:42.530> about<00:00:42.620> the<00:00:42.800> blockchain 00:00:43.000 --> 00:00:43.010 align:start position:0% and how I heard about the blockchain 00:00:43.010 --> 00:00:45.880 align:start position:0% and how I heard about the blockchain world<00:00:43.370> was<00:00:43.610> at<00:00:43.880> the<00:00:44.030> end<00:00:44.330> of<00:00:44.420> last<00:00:44.630> year<00:00:44.960> and<00:00:45.200> I 00:00:45.880 --> 00:00:45.890 align:start position:0% world was at the end of last year and I 00:00:45.890 --> 00:00:47.950 align:start position:0% world was at the end of last year and I really<00:00:46.160> got<00:00:46.340> involved<00:00:46.760> in<00:00:47.060> life<00:00:47.210> here<00:00:47.540> earlier 00:00:47.950 --> 00:00:47.960 align:start position:0% really got involved in life here earlier 00:00:47.960 --> 00:00:49.810 align:start position:0% really got involved in life here earlier this<00:00:48.170> year<00:00:48.230> and<00:00:48.650> just<00:00:48.890> never<00:00:49.100> looked<00:00:49.370> back 00:00:49.810 --> 00:00:49.820 align:start position:0% this year and just never looked back 00:00:49.820 --> 00:00:51.640 align:start position:0% this year and just never looked back so<00:00:50.180> now<00:00:50.300> I'm<00:00:50.420> working<00:00:50.630> on<00:00:50.870> a<00:00:51.200> life<00:00:51.440> here 00:00:51.640 --> 00:00:51.650 align:start position:0% so now I'm working on a life here 00:00:51.650 --> 00:00:53.800 align:start position:0% so now I'm working on a life here research<00:00:52.190> and<00:00:52.430> design<00:00:52.790> under<00:00:53.360> the<00:00:53.480> community 00:00:53.800 --> 00:00:53.810 align:start position:0% research and design under the community 00:00:53.810 --> 00:00:57.250 align:start position:0% research and design under the community grant<00:00:54.640> actually<00:00:55.640> license<00:00:56.150> mine<00:00:56.300> so<00:00:56.990> we<00:00:57.080> got<00:00:57.230> a 00:00:57.250 --> 00:00:57.260 align:start position:0% grant actually license mine so we got a 00:00:57.260 --> 00:00:59.050 align:start position:0% grant actually license mine so we got a couple<00:00:57.500> really<00:00:57.590> exciting<00:00:58.460> things<00:00:58.700> on<00:00:58.940> the 00:00:59.050 --> 00:00:59.060 align:start position:0% couple really exciting things on the 00:00:59.060 --> 00:01:01.120 align:start position:0% couple really exciting things on the agenda<00:00:59.090> for<00:00:59.570> you<00:00:59.630> today<00:00:59.890> first<00:01:00.890> we're<00:01:01.070> gonna 00:01:01.120 --> 00:01:01.130 align:start position:0% agenda for you today first we're gonna 00:01:01.130 --> 00:01:02.740 align:start position:0% agenda for you today first we're gonna delve<00:01:01.400> into<00:01:01.700> what<00:01:02.270> are<00:01:02.360> some<00:01:02.600> of<00:01:02.660> the 00:01:02.740 --> 00:01:02.750 align:start position:0% delve into what are some of the 00:01:02.750 --> 00:01:04.660 align:start position:0% delve into what are some of the onboarding<00:01:03.170> problems<00:01:03.590> across<00:01:03.920> the<00:01:04.040> entire 00:01:04.660 --> 00:01:04.670 align:start position:0% onboarding problems across the entire 00:01:04.670 --> 00:01:06.340 align:start position:0% onboarding problems across the entire ecosystem<00:01:04.939> because<00:01:05.600> this<00:01:05.750> is<00:01:05.840> really<00:01:06.020> not<00:01:06.200> an 00:01:06.340 --> 00:01:06.350 align:start position:0% ecosystem because this is really not an 00:01:06.350 --> 00:01:08.709 align:start position:0% ecosystem because this is really not an isolated<00:01:06.770> incident<00:01:06.979> and<00:01:07.549> then<00:01:08.299> secondly 00:01:08.709 --> 00:01:08.719 align:start position:0% isolated incident and then secondly 00:01:08.719 --> 00:01:10.330 align:start position:0% isolated incident and then secondly we're<00:01:08.899> gonna<00:01:08.990> be<00:01:09.649> really<00:01:09.859> excited<00:01:10.189> to<00:01:10.249> share 00:01:10.330 --> 00:01:10.340 align:start position:0% we're gonna be really excited to share 00:01:10.340 --> 00:01:12.160 align:start position:0% we're gonna be really excited to share with<00:01:10.460> you<00:01:10.549> how<00:01:10.880> life<00:01:11.299> here<00:01:11.509> really<00:01:11.689> imagined 00:01:12.160 --> 00:01:12.170 align:start position:0% with you how life here really imagined 00:01:12.170 --> 00:01:17.200 align:start position:0% with you how life here really imagined its<00:01:12.380> own<00:01:12.590> sneaking<00:01:13.399> out<00:01:13.490> redesign<00:01:15.340> cool<00:01:16.340> so 00:01:17.200 --> 00:01:17.210 align:start position:0% its own sneaking out redesign cool so 00:01:17.210 --> 00:01:18.999 align:start position:0% its own sneaking out redesign cool so there's<00:01:17.630> a<00:01:17.780> pretty<00:01:18.140> decent<00:01:18.590> amount<00:01:18.710> of<00:01:18.890> you 00:01:18.999 --> 00:01:19.009 align:start position:0% there's a pretty decent amount of you 00:01:19.009 --> 00:01:21.700 align:start position:0% there's a pretty decent amount of you here<00:01:19.369> quick<00:01:20.179> show<00:01:20.329> of<00:01:20.450> hands<00:01:20.659> who<00:01:20.929> here<00:01:20.960> runs<00:01:21.530> a 00:01:21.700 --> 00:01:21.710 align:start position:0% here quick show of hands who here runs a 00:01:21.710 --> 00:01:28.450 align:start position:0% here quick show of hands who here runs a mining<00:01:22.159> operation<00:01:23.829> okay<00:01:24.999> and<00:01:26.380> who<00:01:27.380> here<00:01:28.039> has 00:01:28.450 --> 00:01:28.460 align:start position:0% mining operation okay and who here has 00:01:28.460 --> 00:01:30.880 align:start position:0% mining operation okay and who here has recently<00:01:28.729> staked<00:01:29.270> token<00:01:29.689> on<00:01:29.840> a<00:01:29.869> prove<00:01:30.590> mistake 00:01:30.880 --> 00:01:30.890 align:start position:0% recently staked token on a prove mistake 00:01:30.890 --> 00:01:34.090 align:start position:0% recently staked token on a prove mistake Network<00:01:31.249> okay<00:01:32.210> so<00:01:32.869> a<00:01:32.899> lot<00:01:33.079> more<00:01:33.350> hands<00:01:33.619> I<00:01:33.829> think 00:01:34.090 --> 00:01:34.100 align:start position:0% Network okay so a lot more hands I think 00:01:34.100 --> 00:01:39.270 align:start position:0% Network okay so a lot more hands I think I<00:01:34.819> think<00:01:35.210> is<00:01:35.299> perfectly<00:01:35.630> illustrates 00:01:39.270 --> 00:01:39.280 align:start position:0% 00:01:39.280 --> 00:01:43.059 align:start position:0% basically<00:01:40.689> how<00:01:41.689> much<00:01:42.170> brute<00:01:42.590> mistake<00:01:42.889> has 00:01:43.059 --> 00:01:43.069 align:start position:0% basically how much brute mistake has 00:01:43.069 --> 00:01:44.679 align:start position:0% basically how much brute mistake has really<00:01:43.369> lowered<00:01:43.700> the<00:01:43.819> barrier<00:01:44.119> to<00:01:44.179> entry<00:01:44.270> to 00:01:44.679 --> 00:01:44.689 align:start position:0% really lowered the barrier to entry to 00:01:44.689 --> 00:01:46.510 align:start position:0% really lowered the barrier to entry to participate<00:01:45.530> in<00:01:45.679> these<00:01:45.829> these<00:01:46.159> open 00:01:46.510 --> 00:01:46.520 align:start position:0% participate in these these open 00:01:46.520 --> 00:01:48.609 align:start position:0% participate in these these open decentralized<00:01:47.179> networks<00:01:47.630> so<00:01:48.200> in<00:01:48.259> the<00:01:48.319> case<00:01:48.469> of 00:01:48.609 --> 00:01:48.619 align:start position:0% decentralized networks so in the case of 00:01:48.619 --> 00:01:52.029 align:start position:0% decentralized networks so in the case of live<00:01:48.799> peer<00:01:49.659> that's<00:01:50.659> a<00:01:50.899> video<00:01:51.319> infrastructure 00:01:52.029 --> 00:01:52.039 align:start position:0% live peer that's a video infrastructure 00:01:52.039 --> 00:01:54.639 align:start position:0% live peer that's a video infrastructure network<00:01:52.340> but<00:01:52.579> there's<00:01:52.759> lots<00:01:53.030> of<00:01:53.649> really 00:01:54.639 --> 00:01:54.649 align:start position:0% network but there's lots of really 00:01:54.649 --> 00:01:56.399 align:start position:0% network but there's lots of really exciting<00:01:55.159> proof<00:01:55.340> of<00:01:55.459> stake<00:01:55.700> networks<00:01:55.999> being 00:01:56.399 --> 00:01:56.409 align:start position:0% exciting proof of stake networks being 00:01:56.409 --> 00:01:59.050 align:start position:0% exciting proof of stake networks being being<00:01:57.409> built<00:01:57.619> out<00:01:57.770> today<00:01:58.100> that<00:01:58.130> we<00:01:58.670> think<00:01:58.909> will 00:01:59.050 --> 00:01:59.060 align:start position:0% being built out today that we think will 00:01:59.060 --> 00:02:01.719 align:start position:0% being built out today that we think will be<00:01:59.090> really<00:01:59.929> integral<00:02:00.619> to<00:02:00.829> our<00:02:00.859> everyday<00:02:01.399> lives 00:02:01.719 --> 00:02:01.729 align:start position:0% be really integral to our everyday lives 00:02:01.729 --> 00:02:04.949 align:start position:0% be really integral to our everyday lives as<00:02:02.029> really<00:02:02.560> citizens<00:02:03.560> of<00:02:03.740> the<00:02:03.859> internet<00:02:04.189> so 00:02:04.949 --> 00:02:04.959 align:start position:0% as really citizens of the internet so 00:02:04.959 --> 00:02:08.290 align:start position:0% as really citizens of the internet so here's<00:02:05.959> a<00:02:06.020> short<00:02:06.649> list<00:02:06.759> this<00:02:07.759> is<00:02:07.880> really<00:02:08.119> just 00:02:08.290 --> 00:02:08.300 align:start position:0% here's a short list this is really just 00:02:08.300 --> 00:02:09.820 align:start position:0% here's a short list this is really just the<00:02:08.390> tip<00:02:08.539> of<00:02:08.569> the<00:02:08.690> iceberg<00:02:09.110> but<00:02:09.289> there's<00:02:09.740> a 00:02:09.820 --> 00:02:09.830 align:start position:0% the tip of the iceberg but there's a 00:02:09.830 --> 00:02:12.160 align:start position:0% the tip of the iceberg but there's a public<00:02:10.280> proof<00:02:10.490> of<00:02:10.610> stake<00:02:10.880> network<00:02:11.300> for<00:02:11.689> smart 00:02:12.160 --> 00:02:12.170 align:start position:0% public proof of stake network for smart 00:02:12.170 --> 00:02:14.860 align:start position:0% public proof of stake network for smart contract<00:02:12.620> platforms<00:02:13.280> for<00:02:13.580> value<00:02:14.360> exchange 00:02:14.860 --> 00:02:14.870 align:start position:0% contract platforms for value exchange 00:02:14.870 --> 00:02:17.490 align:start position:0% contract platforms for value exchange for<00:02:15.379> data<00:02:16.099> query<00:02:16.610> processing 00:02:17.490 --> 00:02:17.500 align:start position:0% for data query processing 00:02:17.500 --> 00:02:21.720 align:start position:0% for data query processing for<00:02:17.800> blockchain<00:02:18.760> interoperability<00:02:20.580> so<00:02:21.580> yeah 00:02:21.720 --> 00:02:21.730 align:start position:0% for blockchain interoperability so yeah 00:02:21.730 --> 00:02:24.600 align:start position:0% for blockchain interoperability so yeah we<00:02:22.180> think<00:02:22.390> staking<00:02:23.350> is<00:02:23.440> here<00:02:23.620> to<00:02:23.680> stay<00:02:23.890> and<00:02:24.100> we 00:02:24.600 --> 00:02:24.610 align:start position:0% we think staking is here to stay and we 00:02:24.610 --> 00:02:28.050 align:start position:0% we think staking is here to stay and we believe<00:02:24.820> strongly<00:02:25.120> it's<00:02:26.640> yeah<00:02:27.640> it's<00:02:27.850> here<00:02:27.970> to 00:02:28.050 --> 00:02:28.060 align:start position:0% believe strongly it's yeah it's here to 00:02:28.060 --> 00:02:29.370 align:start position:0% believe strongly it's yeah it's here to stay<00:02:28.120> we<00:02:28.390> think<00:02:28.510> it's<00:02:28.600> pretty<00:02:28.690> cool<00:02:28.900> and<00:02:29.140> we're 00:02:29.370 --> 00:02:29.380 align:start position:0% stay we think it's pretty cool and we're 00:02:29.380 --> 00:02:30.450 align:start position:0% stay we think it's pretty cool and we're looking<00:02:29.560> forward<00:02:29.740> to<00:02:29.890> seeing<00:02:30.070> the<00:02:30.190> first 00:02:30.450 --> 00:02:30.460 align:start position:0% looking forward to seeing the first 00:02:30.460 --> 00:02:32.550 align:start position:0% looking forward to seeing the first million<00:02:30.940> users<00:02:31.270> on<00:02:31.510> boarded<00:02:32.440> and 00:02:32.550 --> 00:02:32.560 align:start position:0% million users on boarded and 00:02:32.560 --> 00:02:36.240 align:start position:0% million users on boarded and participating<00:02:33.400> in<00:02:33.580> these<00:02:34.420> networks<00:02:35.250> but 00:02:36.240 --> 00:02:36.250 align:start position:0% participating in these networks but 00:02:36.250 --> 00:02:39.240 align:start position:0% participating in these networks but there's<00:02:37.180> a<00:02:37.390> problem 00:02:39.240 --> 00:02:39.250 align:start position:0% there's a problem 00:02:39.250 --> 00:02:42.420 align:start position:0% there's a problem staking<00:02:39.670> user<00:02:40.450> interfaces<00:02:41.110> so<00:02:41.860> the<00:02:41.980> gateway 00:02:42.420 --> 00:02:42.430 align:start position:0% staking user interfaces so the gateway 00:02:42.430 --> 00:02:44.730 align:start position:0% staking user interfaces so the gateway to<00:02:42.460> to<00:02:43.330> participate<00:02:43.780> in<00:02:44.170> securing<00:02:44.620> these 00:02:44.730 --> 00:02:44.740 align:start position:0% to to participate in securing these 00:02:44.740 --> 00:02:47.250 align:start position:0% to to participate in securing these networks<00:02:45.240> kind<00:02:46.240> of<00:02:46.390> sucked<00:02:46.660> for<00:02:46.870> the<00:02:46.990> for<00:02:47.200> the 00:02:47.250 --> 00:02:47.260 align:start position:0% networks kind of sucked for the for the 00:02:47.260 --> 00:02:50.460 align:start position:0% networks kind of sucked for the for the most<00:02:47.410> part<00:02:48.780> and<00:02:49.780> that<00:02:49.870> makes<00:02:50.080> onboarding 00:02:50.460 --> 00:02:50.470 align:start position:0% most part and that makes onboarding 00:02:50.470 --> 00:02:53.790 align:start position:0% most part and that makes onboarding really<00:02:50.709> hard<00:02:52.020> so<00:02:53.020> studies<00:02:53.350> have<00:02:53.530> shown<00:02:53.770> that 00:02:53.790 --> 00:02:53.800 align:start position:0% really hard so studies have shown that 00:02:53.800 --> 00:02:56.250 align:start position:0% really hard so studies have shown that if<00:02:54.340> it<00:02:54.459> takes<00:02:54.700> more<00:02:54.880> than<00:02:54.940> five<00:02:55.330> minutes<00:02:55.630> to 00:02:56.250 --> 00:02:56.260 align:start position:0% if it takes more than five minutes to 00:02:56.260 --> 00:02:59.640 align:start position:0% if it takes more than five minutes to onboard<00:02:56.740> a<00:02:57.070> user<00:02:57.360> they'll<00:02:58.360> most<00:02:58.570> likely<00:02:58.660> the 00:02:59.640 --> 00:02:59.650 align:start position:0% onboard a user they'll most likely the 00:02:59.650 --> 00:03:01.650 align:start position:0% onboard a user they'll most likely the most<00:02:59.830> likely<00:03:00.070> drop<00:03:00.310> off<00:03:00.490> or<00:03:00.670> give<00:03:00.850> up<00:03:01.030> so<00:03:01.240> we're 00:03:01.650 --> 00:03:01.660 align:start position:0% most likely drop off or give up so we're 00:03:01.660 --> 00:03:03.360 align:start position:0% most likely drop off or give up so we're gonna<00:03:01.720> have<00:03:01.870> a<00:03:01.900> real<00:03:02.050> hard<00:03:02.290> time<00:03:02.370> onboarding 00:03:03.360 --> 00:03:03.370 align:start position:0% gonna have a real hard time onboarding 00:03:03.370 --> 00:03:05.940 align:start position:0% gonna have a real hard time onboarding the<00:03:03.490> first<00:03:03.730> you<00:03:04.120> know<00:03:04.240> million<00:03:04.750> staking<00:03:05.650> users 00:03:05.940 --> 00:03:05.950 align:start position:0% the first you know million staking users 00:03:05.950 --> 00:03:08.460 align:start position:0% the first you know million staking users if<00:03:06.160> it<00:03:06.280> takes<00:03:06.490> more<00:03:06.940> than<00:03:07.000> five<00:03:07.390> minutes<00:03:07.660> to<00:03:07.959> to 00:03:08.460 --> 00:03:08.470 align:start position:0% if it takes more than five minutes to to 00:03:08.470 --> 00:03:12.180 align:start position:0% if it takes more than five minutes to to stake<00:03:09.750> so<00:03:10.750> so<00:03:11.050> why<00:03:11.170> do<00:03:11.230> who's<00:03:11.530> taking<00:03:11.890> apps 00:03:12.180 --> 00:03:12.190 align:start position:0% stake so so why do who's taking apps 00:03:12.190 --> 00:03:15.660 align:start position:0% stake so so why do who's taking apps suck<00:03:13.230> we<00:03:14.230> surveyed<00:03:14.650> this<00:03:14.830> sort<00:03:15.250> of<00:03:15.280> burgeoning 00:03:15.660 --> 00:03:15.670 align:start position:0% suck we surveyed this sort of burgeoning 00:03:15.670 --> 00:03:18.150 align:start position:0% suck we surveyed this sort of burgeoning landscape<00:03:16.270> of<00:03:16.480> staking<00:03:17.410> apps<00:03:17.709> and<00:03:17.980> we 00:03:18.150 --> 00:03:18.160 align:start position:0% landscape of staking apps and we 00:03:18.160 --> 00:03:22.590 align:start position:0% landscape of staking apps and we surfaced<00:03:18.580> really<00:03:19.080> four<00:03:20.080> main<00:03:21.510> problems<00:03:22.510> that 00:03:22.590 --> 00:03:22.600 align:start position:0% surfaced really four main problems that 00:03:22.600 --> 00:03:24.900 align:start position:0% surfaced really four main problems that have<00:03:22.810> really<00:03:23.320> been<00:03:23.440> impeding<00:03:24.220> the<00:03:24.370> onboarding 00:03:24.900 --> 00:03:24.910 align:start position:0% have really been impeding the onboarding 00:03:24.910 --> 00:03:27.540 align:start position:0% have really been impeding the onboarding process<00:03:24.940> and<00:03:25.720> for<00:03:26.230> users<00:03:26.380> and<00:03:26.650> nearly<00:03:27.250> all<00:03:27.400> of 00:03:27.540 --> 00:03:27.550 align:start position:0% process and for users and nearly all of 00:03:27.550 --> 00:03:31.199 align:start position:0% process and for users and nearly all of them<00:03:27.750> so<00:03:28.750> problem<00:03:29.110> number<00:03:29.140> one<00:03:29.820> is<00:03:30.820> a<00:03:30.880> really 00:03:31.199 --> 00:03:31.209 align:start position:0% them so problem number one is a really 00:03:31.209 --> 00:03:33.979 align:start position:0% them so problem number one is a really verbose<00:03:31.750> and<00:03:32.019> inconsistent<00:03:32.650> language<00:03:33.459> system 00:03:33.979 --> 00:03:33.989 align:start position:0% verbose and inconsistent language system 00:03:33.989 --> 00:03:38.370 align:start position:0% verbose and inconsistent language system being<00:03:34.989> used<00:03:35.200> so<00:03:35.500> staking<00:03:36.489> bonding<00:03:37.150> on<00:03:37.480> bonds 00:03:38.370 --> 00:03:38.380 align:start position:0% being used so staking bonding on bonds 00:03:38.380 --> 00:03:41.640 align:start position:0% being used so staking bonding on bonds on<00:03:38.500> stake<00:03:38.890> baking<00:03:39.700> cycle<00:03:40.150> around<00:03:40.360> era<00:03:40.780> epoch 00:03:41.640 --> 00:03:41.650 align:start position:0% on stake baking cycle around era epoch 00:03:41.650 --> 00:03:44.310 align:start position:0% on stake baking cycle around era epoch delegator<00:03:42.160> there's<00:03:42.670> a<00:03:42.820> lot<00:03:43.000> of<00:03:43.120> jargon<00:03:43.330> and<00:03:44.200> I 00:03:44.310 --> 00:03:44.320 align:start position:0% delegator there's a lot of jargon and I 00:03:44.320 --> 00:03:45.990 align:start position:0% delegator there's a lot of jargon and I think<00:03:44.530> like<00:03:44.800> these<00:03:45.280> words<00:03:45.489> are<00:03:45.580> great<00:03:45.700> but 00:03:45.990 --> 00:03:46.000 align:start position:0% think like these words are great but 00:03:46.000 --> 00:03:48.449 align:start position:0% think like these words are great but they're<00:03:46.780> pretty<00:03:46.900> reverse<00:03:47.290> verbose<00:03:47.980> and<00:03:48.160> often 00:03:48.449 --> 00:03:48.459 align:start position:0% they're pretty reverse verbose and often 00:03:48.459 --> 00:03:50.759 align:start position:0% they're pretty reverse verbose and often redundant<00:03:48.940> like<00:03:49.150> stake<00:03:49.750> and<00:03:49.930> bond<00:03:50.110> really 00:03:50.759 --> 00:03:50.769 align:start position:0% redundant like stake and bond really 00:03:50.769 --> 00:03:52.470 align:start position:0% redundant like stake and bond really mean<00:03:50.920> the<00:03:51.010> same<00:03:51.160> thing<00:03:51.400> and<00:03:52.269> they're<00:03:52.390> not 00:03:52.470 --> 00:03:52.480 align:start position:0% mean the same thing and they're not 00:03:52.480 --> 00:03:54.030 align:start position:0% mean the same thing and they're not being<00:03:52.690> employed<00:03:52.930> consistently<00:03:53.650> and<00:03:53.739> this<00:03:53.890> is 00:03:54.030 --> 00:03:54.040 align:start position:0% being employed consistently and this is 00:03:54.040 --> 00:03:58.050 align:start position:0% being employed consistently and this is leaving<00:03:54.340> users<00:03:54.610> pretty<00:03:54.910> confused<00:03:56.850> number<00:03:57.850> two 00:03:58.050 --> 00:03:58.060 align:start position:0% leaving users pretty confused number two 00:03:58.060 --> 00:04:00.690 align:start position:0% leaving users pretty confused number two it's<00:03:58.840> really<00:03:59.200> hard<00:03:59.440> to<00:03:59.620> evaluate<00:03:59.890> delegates 00:04:00.690 --> 00:04:00.700 align:start position:0% it's really hard to evaluate delegates 00:04:00.700 --> 00:04:03.620 align:start position:0% it's really hard to evaluate delegates so<00:04:01.000> in<00:04:01.390> most<00:04:02.080> proof<00:04:02.470> of<00:04:02.650> stakes<00:04:02.890> systems<00:04:03.340> a 00:04:03.620 --> 00:04:03.630 align:start position:0% so in most proof of stakes systems a 00:04:03.630 --> 00:04:06.690 align:start position:0% so in most proof of stakes systems a delegate<00:04:04.630> is<00:04:04.750> represented<00:04:05.410> by<00:04:05.440> their<00:04:06.250> very 00:04:06.690 --> 00:04:06.700 align:start position:0% delegate is represented by their very 00:04:06.700 --> 00:04:08.190 align:start position:0% delegate is represented by their very dress<00:04:06.970> so<00:04:07.239> this<00:04:07.390> is<00:04:07.510> just<00:04:07.630> a<00:04:07.810> randomly 00:04:08.190 --> 00:04:08.200 align:start position:0% dress so this is just a randomly 00:04:08.200 --> 00:04:12.240 align:start position:0% dress so this is just a randomly generated<00:04:08.700> string<00:04:10.260> and<00:04:11.260> so<00:04:11.380> the<00:04:11.470> absence<00:04:11.950> of<00:04:12.100> a 00:04:12.240 --> 00:04:12.250 align:start position:0% generated string and so the absence of a 00:04:12.250 --> 00:04:15.390 align:start position:0% generated string and so the absence of a social<00:04:12.670> identity<00:04:12.760> layer<00:04:13.690> for<00:04:14.019> example<00:04:14.410> a<00:04:14.680> name 00:04:15.390 --> 00:04:15.400 align:start position:0% social identity layer for example a name 00:04:15.400 --> 00:04:18.360 align:start position:0% social identity layer for example a name a<00:04:15.430> bio<00:04:15.970> or<00:04:16.479> an<00:04:16.570> avatar<00:04:17.019> or<00:04:17.049> URL<00:04:17.590> makes<00:04:18.250> it 00:04:18.360 --> 00:04:18.370 align:start position:0% a bio or an avatar or URL makes it 00:04:18.370 --> 00:04:20.849 align:start position:0% a bio or an avatar or URL makes it really<00:04:18.549> difficult<00:04:18.900> for<00:04:19.900> users<00:04:20.019> to<00:04:20.290> evaluate 00:04:20.849 --> 00:04:20.859 align:start position:0% really difficult for users to evaluate 00:04:20.859 --> 00:04:22.830 align:start position:0% really difficult for users to evaluate who<00:04:21.040> to<00:04:21.160> stake<00:04:21.400> towards<00:04:21.760> and<00:04:21.970> this<00:04:22.479> is<00:04:22.660> like 00:04:22.830 --> 00:04:22.840 align:start position:0% who to stake towards and this is like 00:04:22.840 --> 00:04:25.620 align:start position:0% who to stake towards and this is like you<00:04:23.560> know<00:04:23.650> web<00:04:23.860> 2.0<00:04:24.370> this<00:04:24.520> is<00:04:24.760> like<00:04:25.060> a<00:04:25.240> given 00:04:25.620 --> 00:04:25.630 align:start position:0% you know web 2.0 this is like a given 00:04:25.630 --> 00:04:27.719 align:start position:0% you know web 2.0 this is like a given but<00:04:25.840> it's<00:04:25.960> in<00:04:26.710> a<00:04:26.890> lot<00:04:27.039> of<00:04:27.070> these<00:04:27.220> apps<00:04:27.430> we<00:04:27.580> saw 00:04:27.719 --> 00:04:27.729 align:start position:0% but it's in a lot of these apps we saw 00:04:27.729 --> 00:04:30.250 align:start position:0% but it's in a lot of these apps we saw there<00:04:28.000> it's<00:04:28.510> not<00:04:28.690> available 00:04:30.250 --> 00:04:30.260 align:start position:0% there it's not available 00:04:30.260 --> 00:04:32.240 align:start position:0% there it's not available problem<00:04:31.260> number<00:04:31.380> three<00:04:31.740> it's<00:04:31.980> really 00:04:32.240 --> 00:04:32.250 align:start position:0% problem number three it's really 00:04:32.250 --> 00:04:34.640 align:start position:0% problem number three it's really difficult<00:04:32.460> to<00:04:32.790> evaluate<00:04:33.120> the<00:04:33.840> benefits<00:04:34.080> of 00:04:34.640 --> 00:04:34.650 align:start position:0% difficult to evaluate the benefits of 00:04:34.650 --> 00:04:36.710 align:start position:0% difficult to evaluate the benefits of staking<00:04:35.040> so<00:04:35.850> staking<00:04:36.300> apps<00:04:36.450> are<00:04:36.570> not 00:04:36.710 --> 00:04:36.720 align:start position:0% staking so staking apps are not 00:04:36.720 --> 00:04:39.320 align:start position:0% staking so staking apps are not effectively<00:04:37.470> showing<00:04:38.040> users<00:04:38.760> what<00:04:39.180> they 00:04:39.320 --> 00:04:39.330 align:start position:0% effectively showing users what they 00:04:39.330 --> 00:04:43.280 align:start position:0% effectively showing users what they stand<00:04:39.570> to<00:04:39.750> gain<00:04:40.250> by<00:04:41.250> staking<00:04:42.290> staking 00:04:43.280 --> 00:04:43.290 align:start position:0% stand to gain by staking staking 00:04:43.290 --> 00:04:45.020 align:start position:0% stand to gain by staking staking represents<00:04:43.680> an<00:04:43.770> opportunity<00:04:43.860> to<00:04:44.430> own<00:04:44.580> equity 00:04:45.020 --> 00:04:45.030 align:start position:0% represents an opportunity to own equity 00:04:45.030 --> 00:04:47.420 align:start position:0% represents an opportunity to own equity and<00:04:45.660> voting<00:04:46.320> influence<00:04:46.710> in<00:04:46.800> public<00:04:47.130> networks 00:04:47.420 --> 00:04:47.430 align:start position:0% and voting influence in public networks 00:04:47.430 --> 00:04:49.310 align:start position:0% and voting influence in public networks that<00:04:47.670> you<00:04:48.210> know<00:04:48.270> we<00:04:48.420> think<00:04:48.930> we<00:04:49.290> believe 00:04:49.310 --> 00:04:49.320 align:start position:0% that you know we think we believe 00:04:49.320 --> 00:04:52.040 align:start position:0% that you know we think we believe strongly<00:04:49.880> our<00:04:50.880> society<00:04:51.300> will<00:04:51.450> will<00:04:51.750> run<00:04:51.930> on 00:04:52.040 --> 00:04:52.050 align:start position:0% strongly our society will will run on 00:04:52.050 --> 00:04:53.780 align:start position:0% strongly our society will will run on one<00:04:52.230> day<00:04:52.380> and<00:04:52.710> it<00:04:53.040> also<00:04:53.190> represents<00:04:53.370> an 00:04:53.780 --> 00:04:53.790 align:start position:0% one day and it also represents an 00:04:53.790 --> 00:04:56.360 align:start position:0% one day and it also represents an opportunity<00:04:53.910> to<00:04:54.420> do<00:04:55.170> work<00:04:55.350> and<00:04:55.770> potentially 00:04:56.360 --> 00:04:56.370 align:start position:0% opportunity to do work and potentially 00:04:56.370 --> 00:04:57.940 align:start position:0% opportunity to do work and potentially even<00:04:56.400> earn<00:04:56.640> a<00:04:56.670> living<00:04:57.030> on<00:04:57.150> these<00:04:57.300> networks 00:04:57.940 --> 00:04:57.950 align:start position:0% even earn a living on these networks 00:04:57.950 --> 00:05:00.050 align:start position:0% even earn a living on these networks whether<00:04:58.950> that's<00:04:59.100> validating<00:04:59.490> blockchain 00:05:00.050 --> 00:05:00.060 align:start position:0% whether that's validating blockchain 00:05:00.060 --> 00:05:02.770 align:start position:0% whether that's validating blockchain transactions<00:05:00.750> or<00:05:01.050> in<00:05:01.890> the<00:05:01.950> case<00:05:02.100> of<00:05:02.220> live<00:05:02.340> peer 00:05:02.770 --> 00:05:02.780 align:start position:0% transactions or in the case of live peer 00:05:02.780 --> 00:05:05.420 align:start position:0% transactions or in the case of live peer transcoding<00:05:03.780> and<00:05:03.990> distributing<00:05:04.560> video<00:05:04.680> so 00:05:05.420 --> 00:05:05.430 align:start position:0% transcoding and distributing video so 00:05:05.430 --> 00:05:07.880 align:start position:0% transcoding and distributing video so these<00:05:05.520> are<00:05:05.670> awesome<00:05:05.820> opportunities<00:05:06.890> but 00:05:07.880 --> 00:05:07.890 align:start position:0% these are awesome opportunities but 00:05:07.890 --> 00:05:09.260 align:start position:0% these are awesome opportunities but staking<00:05:08.400> apps<00:05:08.520> are<00:05:08.640> not<00:05:08.760> doing<00:05:09.060> a<00:05:09.090> good<00:05:09.210> job 00:05:09.260 --> 00:05:09.270 align:start position:0% staking apps are not doing a good job 00:05:09.270 --> 00:05:11.300 align:start position:0% staking apps are not doing a good job communicating<00:05:09.660> them<00:05:10.290> before<00:05:10.650> user<00:05:10.830> users 00:05:11.300 --> 00:05:11.310 align:start position:0% communicating them before user users 00:05:11.310 --> 00:05:14.300 align:start position:0% communicating them before user users actually<00:05:11.700> stake<00:05:11.960> and<00:05:12.960> finally<00:05:13.950> we<00:05:14.070> notice<00:05:14.280> a 00:05:14.300 --> 00:05:14.310 align:start position:0% actually stake and finally we notice a 00:05:14.310 --> 00:05:16.400 align:start position:0% actually stake and finally we notice a really<00:05:14.520> disconnected<00:05:15.060> onboarding<00:05:15.600> funnel<00:05:15.900> so 00:05:16.400 --> 00:05:16.410 align:start position:0% really disconnected onboarding funnel so 00:05:16.410 --> 00:05:18.500 align:start position:0% really disconnected onboarding funnel so most<00:05:16.650> staking<00:05:17.070> apps<00:05:17.220> suffer<00:05:18.060> from<00:05:18.210> non 00:05:18.500 --> 00:05:18.510 align:start position:0% most staking apps suffer from non 00:05:18.510 --> 00:05:20.720 align:start position:0% most staking apps suffer from non integrated<00:05:19.230> complex<00:05:19.980> onboarding<00:05:20.490> or<00:05:20.580> no 00:05:20.720 --> 00:05:20.730 align:start position:0% integrated complex onboarding or no 00:05:20.730 --> 00:05:22.790 align:start position:0% integrated complex onboarding or no onboarding<00:05:21.240> at<00:05:21.360> all<00:05:21.510> so<00:05:22.260> there's<00:05:22.560> a<00:05:22.590> lot<00:05:22.680> of 00:05:22.790 --> 00:05:22.800 align:start position:0% onboarding at all so there's a lot of 00:05:22.800 --> 00:05:24.260 align:start position:0% onboarding at all so there's a lot of steps<00:05:22.980> connecting<00:05:23.460> your<00:05:23.580> wallet<00:05:23.880> acquiring 00:05:24.260 --> 00:05:24.270 align:start position:0% steps connecting your wallet acquiring 00:05:24.270 --> 00:05:26.420 align:start position:0% steps connecting your wallet acquiring tokens<00:05:24.690> staking<00:05:25.680> apps<00:05:25.830> you<00:05:25.920> really<00:05:26.160> need<00:05:26.280> to 00:05:26.420 --> 00:05:26.430 align:start position:0% tokens staking apps you really need to 00:05:26.430 --> 00:05:27.920 align:start position:0% tokens staking apps you really need to lead<00:05:26.610> users<00:05:27.030> through<00:05:27.300> these<00:05:27.450> steps<00:05:27.660> in 00:05:27.920 --> 00:05:27.930 align:start position:0% lead users through these steps in 00:05:27.930 --> 00:05:29.780 align:start position:0% lead users through these steps in applica<00:05:28.440> like<00:05:28.740> a<00:05:28.770> good<00:05:28.980> salsa<00:05:29.400> dancing 00:05:29.780 --> 00:05:29.790 align:start position:0% applica like a good salsa dancing 00:05:29.790 --> 00:05:33.410 align:start position:0% applica like a good salsa dancing partner<00:05:31.010> so<00:05:32.010> this<00:05:32.190> is<00:05:32.340> an<00:05:32.910> actual 00:05:33.410 --> 00:05:33.420 align:start position:0% partner so this is an actual 00:05:33.420 --> 00:05:36.020 align:start position:0% partner so this is an actual conversation<00:05:34.170> I<00:05:34.380> had<00:05:35.340> with<00:05:35.370> a<00:05:35.550> friend<00:05:35.640> of<00:05:35.880> mine 00:05:36.020 --> 00:05:36.030 align:start position:0% conversation I had with a friend of mine 00:05:36.030 --> 00:05:39.340 align:start position:0% conversation I had with a friend of mine he<00:05:36.570> asked<00:05:36.840> me<00:05:37.040> how<00:05:38.040> to<00:05:38.100> stake<00:05:38.370> on<00:05:38.550> live<00:05:38.730> here 00:05:39.340 --> 00:05:39.350 align:start position:0% he asked me how to stake on live here 00:05:39.350 --> 00:05:42.050 align:start position:0% he asked me how to stake on live here and<00:05:40.350> I<00:05:41.010> didn't<00:05:41.190> feel<00:05:41.280> really<00:05:41.520> confident<00:05:41.880> in 00:05:42.050 --> 00:05:42.060 align:start position:0% and I didn't feel really confident in 00:05:42.060 --> 00:05:43.910 align:start position:0% and I didn't feel really confident in the<00:05:42.360> the<00:05:42.570> onboarding<00:05:42.960> tutorial<00:05:43.410> on<00:05:43.680> the 00:05:43.910 --> 00:05:43.920 align:start position:0% the the onboarding tutorial on the 00:05:43.920 --> 00:05:46.100 align:start position:0% the the onboarding tutorial on the staking<00:05:44.280> app<00:05:44.400> so<00:05:44.610> I<00:05:44.640> just<00:05:44.850> sent<00:05:45.510> him<00:05:45.660> step<00:05:45.930> by 00:05:46.100 --> 00:05:46.110 align:start position:0% staking app so I just sent him step by 00:05:46.110 --> 00:05:48.350 align:start position:0% staking app so I just sent him step by step<00:05:46.410> instructions<00:05:47.400> and<00:05:47.550> I'm<00:05:47.610> sure<00:05:47.790> many<00:05:48.210> of 00:05:48.350 --> 00:05:48.360 align:start position:0% step instructions and I'm sure many of 00:05:48.360 --> 00:05:50.810 align:start position:0% step instructions and I'm sure many of you<00:05:48.480> have<00:05:48.510> gone<00:05:48.750> through<00:05:49.020> this<00:05:49.110> process<00:05:49.830> you 00:05:50.810 --> 00:05:50.820 align:start position:0% you have gone through this process you 00:05:50.820 --> 00:05:52.820 align:start position:0% you have gone through this process you know<00:05:50.910> step<00:05:51.120> one<00:05:51.330> get<00:05:51.720> a<00:05:51.780> wallet<00:05:51.990> step<00:05:52.290> two<00:05:52.500> from 00:05:52.820 --> 00:05:52.830 align:start position:0% know step one get a wallet step two from 00:05:52.830 --> 00:05:54.620 align:start position:0% know step one get a wallet step two from the<00:05:52.950> wallet<00:05:53.130> step<00:05:53.520> three<00:05:53.790> acquire<00:05:54.180> a<00:05:54.210> token 00:05:54.620 --> 00:05:54.630 align:start position:0% the wallet step three acquire a token 00:05:54.630 --> 00:05:57.050 align:start position:0% the wallet step three acquire a token step<00:05:54.960> four<00:05:55.200> the<00:05:55.800> proof<00:05:56.010> tokens<00:05:56.400> for<00:05:56.580> staking 00:05:57.050 --> 00:05:57.060 align:start position:0% step four the proof tokens for staking 00:05:57.060 --> 00:05:58.520 align:start position:0% step four the proof tokens for staking step<00:05:57.930> 5 00:05:58.520 --> 00:05:58.530 align:start position:0% step 5 00:05:58.530 --> 00:06:02.150 align:start position:0% step 5 evaluate<00:05:59.220> your<00:05:59.250> your<00:06:00.000> delegate<00:06:00.680> step<00:06:01.680> 6 00:06:02.150 --> 00:06:02.160 align:start position:0% evaluate your your delegate step 6 00:06:02.160 --> 00:06:04.160 align:start position:0% evaluate your your delegate step 6 make<00:06:02.910> sure<00:06:03.030> to<00:06:03.120> manage<00:06:03.420> your<00:06:03.510> awards<00:06:03.960> you<00:06:04.050> know 00:06:04.160 --> 00:06:04.170 align:start position:0% make sure to manage your awards you know 00:06:04.170 --> 00:06:14.090 align:start position:0% make sure to manage your awards you know sign<00:06:04.350> up<00:06:04.470> for<00:06:04.590> notifications<00:06:11.000> so<00:06:12.860> my<00:06:13.860> friend 00:06:14.090 --> 00:06:14.100 align:start position:0% sign up for notifications so my friend 00:06:14.100 --> 00:06:15.560 align:start position:0% sign up for notifications so my friend he<00:06:14.220> did<00:06:14.310> give<00:06:14.520> up<00:06:14.670> and<00:06:14.880> like<00:06:15.090> I<00:06:15.270> don't<00:06:15.330> blame 00:06:15.560 --> 00:06:15.570 align:start position:0% he did give up and like I don't blame 00:06:15.570 --> 00:06:18.230 align:start position:0% he did give up and like I don't blame him<00:06:15.750> it's<00:06:15.960> like<00:06:16.310> come<00:06:17.310> on<00:06:17.430> that's<00:06:17.670> a<00:06:18.060> lot<00:06:18.210> of 00:06:18.230 --> 00:06:18.240 align:start position:0% him it's like come on that's a lot of 00:06:18.240 --> 00:06:20.930 align:start position:0% him it's like come on that's a lot of steps<00:06:18.540> so<00:06:19.220> yeah<00:06:20.220> I<00:06:20.250> think<00:06:20.490> the<00:06:20.550> stakes<00:06:20.730> are<00:06:20.910> too 00:06:20.930 --> 00:06:20.940 align:start position:0% steps so yeah I think the stakes are too 00:06:20.940 --> 00:06:21.230 align:start position:0% steps so yeah I think the stakes are too high 00:06:21.230 --> 00:06:21.240 align:start position:0% high 00:06:21.240 --> 00:06:23.000 align:start position:0% high no<00:06:21.540> pun<00:06:21.690> intended<00:06:21.780> the<00:06:22.440> stakes<00:06:22.710> are<00:06:22.860> too<00:06:22.890> high 00:06:23.000 --> 00:06:23.010 align:start position:0% no pun intended the stakes are too high 00:06:23.010 --> 00:06:25.790 align:start position:0% no pun intended the stakes are too high for<00:06:23.490> to<00:06:24.030> allow<00:06:24.180> users<00:06:24.540> to<00:06:24.570> drop<00:06:24.930> off<00:06:25.140> like<00:06:25.590> this 00:06:25.790 --> 00:06:25.800 align:start position:0% for to allow users to drop off like this 00:06:25.800 --> 00:06:29.150 align:start position:0% for to allow users to drop off like this so<00:06:26.660> you<00:06:27.660> know<00:06:27.780> how<00:06:28.230> can<00:06:28.470> we<00:06:28.590> help<00:06:28.740> how<00:06:28.920> can<00:06:28.950> we 00:06:29.150 --> 00:06:29.160 align:start position:0% so you know how can we help how can we 00:06:29.160 --> 00:06:30.470 align:start position:0% so you know how can we help how can we design<00:06:29.310> for<00:06:29.490> these<00:06:29.760> problems<00:06:29.940> how<00:06:30.180> can<00:06:30.210> we 00:06:30.470 --> 00:06:30.480 align:start position:0% design for these problems how can we 00:06:30.480 --> 00:06:32.810 align:start position:0% design for these problems how can we help<00:06:30.960> onboard<00:06:31.500> new<00:06:31.680> staking<00:06:32.130> users<00:06:32.400> in<00:06:32.580> under 00:06:32.810 --> 00:06:32.820 align:start position:0% help onboard new staking users in under 00:06:32.820 --> 00:06:33.820 align:start position:0% help onboard new staking users in under five<00:06:33.000> minutes 00:06:33.820 --> 00:06:33.830 align:start position:0% five minutes 00:06:33.830 --> 00:06:36.410 align:start position:0% five minutes I'm<00:06:34.830> so<00:06:35.160> glad<00:06:35.340> you<00:06:35.520> asked<00:06:35.820> Adam<00:06:36.120> because 00:06:36.410 --> 00:06:36.420 align:start position:0% I'm so glad you asked Adam because 00:06:36.420 --> 00:06:38.860 align:start position:0% I'm so glad you asked Adam because that's<00:06:36.750> exactly<00:06:37.020> what<00:06:37.770> we<00:06:37.890> set<00:06:38.100> out<00:06:38.220> to<00:06:38.250> do<00:06:38.490> in 00:06:38.860 --> 00:06:38.870 align:start position:0% that's exactly what we set out to do in 00:06:38.870 --> 00:06:42.500 align:start position:0% that's exactly what we set out to do in reimagining<00:06:39.870> the<00:06:40.080> life<00:06:40.440> he's<00:06:40.680> sticking<00:06:41.070> up 00:06:42.500 --> 00:06:42.510 align:start position:0% reimagining the life he's sticking up 00:06:42.510 --> 00:06:43.940 align:start position:0% reimagining the life he's sticking up yes<00:06:42.870> and<00:06:43.140> we're<00:06:43.260> super<00:06:43.500> excited<00:06:43.530> to<00:06:43.860> share 00:06:43.940 --> 00:06:43.950 align:start position:0% yes and we're super excited to share 00:06:43.950 --> 00:06:46.400 align:start position:0% yes and we're super excited to share with<00:06:44.070> you<00:06:44.130> also<00:06:44.280> our<00:06:44.550> results<00:06:45.110> so<00:06:46.110> maybe 00:06:46.400 --> 00:06:46.410 align:start position:0% with you also our results so maybe 00:06:46.410 --> 00:06:48.500 align:start position:0% with you also our results so maybe before<00:06:46.800> we<00:06:46.890> get<00:06:47.010> into<00:06:47.250> that<00:06:47.280> what<00:06:48.120> is<00:06:48.210> life 00:06:48.500 --> 00:06:48.510 align:start position:0% before we get into that what is life 00:06:48.510 --> 00:06:50.570 align:start position:0% before we get into that what is life here<00:06:48.780> anyway<00:06:49.200> and<00:06:49.470> for<00:06:50.130> those<00:06:50.250> of<00:06:50.400> you<00:06:50.460> who 00:06:50.570 --> 00:06:50.580 align:start position:0% here anyway and for those of you who 00:06:50.580 --> 00:06:52.580 align:start position:0% here anyway and for those of you who don't<00:06:50.760> know<00:06:51.000> life<00:06:51.360> here<00:06:51.570> is<00:06:51.630> peer<00:06:52.320> to<00:06:52.350> peer 00:06:52.580 --> 00:06:52.590 align:start position:0% don't know life here is peer to peer 00:06:52.590 --> 00:06:54.830 align:start position:0% don't know life here is peer to peer live<00:06:52.890> video<00:06:53.190> encoding<00:06:53.640> and<00:06:53.820> what<00:06:54.540> that<00:06:54.630> means 00:06:54.830 --> 00:06:54.840 align:start position:0% live video encoding and what that means 00:06:54.840 --> 00:06:57.740 align:start position:0% live video encoding and what that means is<00:06:55.080> we<00:06:55.680> are<00:06:55.830> a<00:06:56.100> protocol<00:06:57.030> and<00:06:57.210> open<00:06:57.510> source 00:06:57.740 --> 00:06:57.750 align:start position:0% is we are a protocol and open source 00:06:57.750 --> 00:07:00.140 align:start position:0% is we are a protocol and open source protocol<00:06:58.140> that<00:06:58.320> any<00:06:58.590> video<00:06:59.160> developer<00:06:59.850> in<00:07:00.030> the 00:07:00.140 --> 00:07:00.150 align:start position:0% protocol that any video developer in the 00:07:00.150 --> 00:07:02.030 align:start position:0% protocol that any video developer in the world<00:07:00.390> can<00:07:00.660> use<00:07:00.900> to<00:07:01.110> incorporate<00:07:01.260> live<00:07:01.740> video 00:07:02.030 --> 00:07:02.040 align:start position:0% world can use to incorporate live video 00:07:02.040 --> 00:07:05.720 align:start position:0% world can use to incorporate live video into<00:07:02.400> their<00:07:02.520> project<00:07:03.000> or<00:07:03.120> app<00:07:04.370> now<00:07:05.370> how<00:07:05.670> does 00:07:05.720 --> 00:07:05.730 align:start position:0% into their project or app now how does 00:07:05.730 --> 00:07:07.700 align:start position:0% into their project or app now how does staking<00:07:06.360> play<00:07:06.540> a<00:07:06.570> role<00:07:06.780> in<00:07:06.900> life<00:07:06.990> here<00:07:07.230> to 00:07:07.700 --> 00:07:07.710 align:start position:0% staking play a role in life here to 00:07:07.710 --> 00:07:09.170 align:start position:0% staking play a role in life here to understand<00:07:08.160> that<00:07:08.340> let's<00:07:08.640> just<00:07:08.880> go<00:07:09.000> through<00:07:09.030> a 00:07:09.170 --> 00:07:09.180 align:start position:0% understand that let's just go through a 00:07:09.180 --> 00:07:09.770 align:start position:0% understand that let's just go through a scenario 00:07:09.770 --> 00:07:09.780 align:start position:0% scenario 00:07:09.780 --> 00:07:12.170 align:start position:0% scenario pretend<00:07:10.530> you're<00:07:10.770> watching<00:07:11.280> a<00:07:11.520> streaming 00:07:12.170 --> 00:07:12.180 align:start position:0% pretend you're watching a streaming 00:07:12.180 --> 00:07:14.570 align:start position:0% pretend you're watching a streaming version<00:07:12.480> of<00:07:12.900> the<00:07:13.110> World<00:07:13.350> Cup<00:07:13.620> in<00:07:13.800> 2020<00:07:14.370> or 00:07:14.570 --> 00:07:14.580 align:start position:0% version of the World Cup in 2020 or 00:07:14.580 --> 00:07:17.180 align:start position:0% version of the World Cup in 2020 or traveling<00:07:15.210> time<00:07:16.110> you<00:07:16.650> know<00:07:16.740> traveling<00:07:17.070> into 00:07:17.180 --> 00:07:17.190 align:start position:0% traveling time you know traveling into 00:07:17.190 --> 00:07:20.120 align:start position:0% traveling time you know traveling into the<00:07:17.220> future<00:07:17.310> and<00:07:18.080> between<00:07:19.080> the<00:07:19.530> camera<00:07:19.920> and 00:07:20.120 --> 00:07:20.130 align:start position:0% the future and between the camera and 00:07:20.130 --> 00:07:22.220 align:start position:0% the future and between the camera and Qatar<00:07:20.490> that's<00:07:21.060> on<00:07:21.270> the<00:07:21.420> football<00:07:21.720> field<00:07:21.960> and 00:07:22.220 --> 00:07:22.230 align:start position:0% Qatar that's on the football field and 00:07:22.230 --> 00:07:24.290 align:start position:0% Qatar that's on the football field and streaming<00:07:23.160> that<00:07:23.250> live<00:07:23.430> to<00:07:23.610> you<00:07:23.730> your<00:07:24.000> device 00:07:24.290 --> 00:07:24.300 align:start position:0% streaming that live to you your device 00:07:24.300 --> 00:07:27.050 align:start position:0% streaming that live to you your device there's<00:07:25.050> this<00:07:25.460> multi-billion<00:07:26.460> dollar<00:07:26.880> market 00:07:27.050 --> 00:07:27.060 align:start position:0% there's this multi-billion dollar market 00:07:27.060 --> 00:07:30.470 align:start position:0% there's this multi-billion dollar market in<00:07:27.600> ensuring<00:07:28.380> this<00:07:28.680> quality<00:07:29.160> video<00:07:29.480> streaming 00:07:30.470 --> 00:07:30.480 align:start position:0% in ensuring this quality video streaming 00:07:30.480 --> 00:07:32.660 align:start position:0% in ensuring this quality video streaming experience<00:07:30.630> for<00:07:31.080> you<00:07:31.200> and<00:07:31.380> now<00:07:32.370> how<00:07:32.640> that 00:07:32.660 --> 00:07:32.670 align:start position:0% experience for you and now how that 00:07:32.670 --> 00:07:35.290 align:start position:0% experience for you and now how that happens<00:07:33.150> is<00:07:33.360> there's<00:07:33.780> a<00:07:34.020> footage<00:07:34.560> of<00:07:34.740> the<00:07:34.830> vo 00:07:35.290 --> 00:07:35.300 align:start position:0% happens is there's a footage of the vo 00:07:35.300 --> 00:07:38.600 align:start position:0% happens is there's a footage of the vo football<00:07:36.300> game<00:07:36.900> playing<00:07:37.260> out<00:07:37.620> there<00:07:37.890> and<00:07:38.070> it 00:07:38.600 --> 00:07:38.610 align:start position:0% football game playing out there and it 00:07:38.610 --> 00:07:40.520 align:start position:0% football game playing out there and it has<00:07:38.730> to<00:07:38.760> be<00:07:38.910> reformatted<00:07:39.750> in<00:07:39.930> order<00:07:40.290> for<00:07:40.440> it<00:07:40.500> to 00:07:40.520 --> 00:07:40.530 align:start position:0% has to be reformatted in order for it to 00:07:40.530 --> 00:07:42.470 align:start position:0% has to be reformatted in order for it to work<00:07:40.650> on<00:07:40.830> all<00:07:40.980> these<00:07:41.220> different<00:07:41.700> devices<00:07:41.820> and 00:07:42.470 --> 00:07:42.480 align:start position:0% work on all these different devices and 00:07:42.480 --> 00:07:45.560 align:start position:0% work on all these different devices and that's<00:07:43.170> called<00:07:43.560> encoding<00:07:44.270> the<00:07:45.270> current 00:07:45.560 --> 00:07:45.570 align:start position:0% that's called encoding the current 00:07:45.570 --> 00:07:47.150 align:start position:0% that's called encoding the current services<00:07:45.990> that<00:07:46.230> are<00:07:46.320> centralized<00:07:46.770> make<00:07:47.040> this 00:07:47.150 --> 00:07:47.160 align:start position:0% services that are centralized make this 00:07:47.160 --> 00:07:49.730 align:start position:0% services that are centralized make this insanely<00:07:47.730> expensive<00:07:48.090> now<00:07:49.020> what<00:07:49.380> life<00:07:49.560> here 00:07:49.730 --> 00:07:49.740 align:start position:0% insanely expensive now what life here 00:07:49.740 --> 00:07:52.670 align:start position:0% insanely expensive now what life here does<00:07:49.920> is<00:07:50.130> take<00:07:50.760> unused<00:07:51.680> infrastructure 00:07:52.670 --> 00:07:52.680 align:start position:0% does is take unused infrastructure 00:07:52.680 --> 00:07:54.530 align:start position:0% does is take unused infrastructure that's<00:07:52.860> out<00:07:53.040> there<00:07:53.220> and<00:07:53.510> make<00:07:54.510> the 00:07:54.530 --> 00:07:54.540 align:start position:0% that's out there and make the 00:07:54.540 --> 00:07:56.690 align:start position:0% that's out there and make the computation<00:07:55.230> so<00:07:55.830> cheap<00:07:56.100> that<00:07:56.130> it's<00:07:56.460> just<00:07:56.640> a 00:07:56.690 --> 00:07:56.700 align:start position:0% computation so cheap that it's just a 00:07:56.700 --> 00:07:58.220 align:start position:0% computation so cheap that it's just a fraction<00:07:57.030> of<00:07:57.120> the<00:07:57.180> cost<00:07:57.420> of<00:07:57.720> what<00:07:57.810> it<00:07:57.900> is<00:07:58.080> today 00:07:58.220 --> 00:07:58.230 align:start position:0% fraction of the cost of what it is today 00:07:58.230 --> 00:08:01.550 align:start position:0% fraction of the cost of what it is today and<00:07:59.000> we<00:08:00.000> use<00:08:00.180> a<00:08:00.210> delegated<00:08:00.900> proof<00:08:01.200> of<00:08:01.350> stake 00:08:01.550 --> 00:08:01.560 align:start position:0% and we use a delegated proof of stake 00:08:01.560 --> 00:08:04.070 align:start position:0% and we use a delegated proof of stake system<00:08:02.190> so<00:08:02.670> when<00:08:02.880> you<00:08:03.030> stake<00:08:03.300> like<00:08:03.510> your<00:08:03.720> token 00:08:04.070 --> 00:08:04.080 align:start position:0% system so when you stake like your token 00:08:04.080 --> 00:08:06.410 align:start position:0% system so when you stake like your token you<00:08:04.590> ensure<00:08:04.950> the<00:08:05.250> quality<00:08:05.550> of<00:08:05.880> the<00:08:06.030> service 00:08:06.410 --> 00:08:06.420 align:start position:0% you ensure the quality of the service 00:08:06.420 --> 00:08:10.010 align:start position:0% you ensure the quality of the service and<00:08:06.630> you<00:08:06.780> secure<00:08:07.080> the<00:08:07.230> network<00:08:08.300> okay<00:08:09.300> so<00:08:09.600> let's 00:08:10.010 --> 00:08:10.020 align:start position:0% and you secure the network okay so let's 00:08:10.020 --> 00:08:11.120 align:start position:0% and you secure the network okay so let's take<00:08:10.080> a<00:08:10.140> look<00:08:10.290> at<00:08:10.410> the<00:08:10.560> current<00:08:10.860> seeking 00:08:11.120 --> 00:08:11.130 align:start position:0% take a look at the current seeking 00:08:11.130 --> 00:08:13.580 align:start position:0% take a look at the current seeking experience<00:08:11.490> this<00:08:12.150> here<00:08:12.360> is<00:08:12.510> a<00:08:12.590> previous 00:08:13.580 --> 00:08:13.590 align:start position:0% experience this here is a previous 00:08:13.590 --> 00:08:17.030 align:start position:0% experience this here is a previous Explorer<00:08:14.010> and<00:08:14.900> what<00:08:15.900> you<00:08:16.050> do<00:08:16.260> here<00:08:16.290> is<00:08:16.800> you 00:08:17.030 --> 00:08:17.040 align:start position:0% Explorer and what you do here is you 00:08:17.040 --> 00:08:20.120 align:start position:0% Explorer and what you do here is you stick<00:08:17.310> token<00:08:17.640> you<00:08:18.270> manage<00:08:19.050> your<00:08:19.200> rewards<00:08:19.710> etc 00:08:20.120 --> 00:08:20.130 align:start position:0% stick token you manage your rewards etc 00:08:20.130 --> 00:08:22.970 align:start position:0% stick token you manage your rewards etc etc<00:08:20.190> and<00:08:20.700> there<00:08:21.450> are<00:08:21.510> over<00:08:21.810> 2,600<00:08:22.710> token 00:08:22.970 --> 00:08:22.980 align:start position:0% etc and there are over 2,600 token 00:08:22.980 --> 00:08:24.740 align:start position:0% etc and there are over 2,600 token holders<00:08:23.280> currently<00:08:23.820> participating<00:08:24.270> in<00:08:24.450> every 00:08:24.740 --> 00:08:24.750 align:start position:0% holders currently participating in every 00:08:24.750 --> 00:08:26.690 align:start position:0% holders currently participating in every day<00:08:24.870> there<00:08:24.990> are<00:08:25.050> more<00:08:25.200> people<00:08:25.410> but<00:08:26.190> there<00:08:26.520> are 00:08:26.690 --> 00:08:26.700 align:start position:0% day there are more people but there are 00:08:26.700 --> 00:08:28.700 align:start position:0% day there are more people but there are still<00:08:27.060> a<00:08:27.120> lot<00:08:27.390> of<00:08:27.510> problems<00:08:27.840> with<00:08:28.200> the<00:08:28.440> sinking 00:08:28.700 --> 00:08:28.710 align:start position:0% still a lot of problems with the sinking 00:08:28.710 --> 00:08:31.220 align:start position:0% still a lot of problems with the sinking Explorer<00:08:28.980> and<00:08:29.910> as<00:08:30.120> I<00:08:30.300> mentioned<00:08:30.870> we<00:08:31.020> don't 00:08:31.220 --> 00:08:31.230 align:start position:0% Explorer and as I mentioned we don't 00:08:31.230 --> 00:08:32.990 align:start position:0% Explorer and as I mentioned we don't really<00:08:31.560> are<00:08:31.980> we're<00:08:32.250> not<00:08:32.280> really<00:08:32.490> exempt<00:08:32.880> from 00:08:32.990 --> 00:08:33.000 align:start position:0% really are we're not really exempt from 00:08:33.000 --> 00:08:35.930 align:start position:0% really are we're not really exempt from all<00:08:33.240> of<00:08:33.390> the<00:08:33.570> you<00:08:34.020> know<00:08:34.340> same<00:08:35.340> the<00:08:35.550> problems 00:08:35.930 --> 00:08:35.940 align:start position:0% all of the you know same the problems 00:08:35.940 --> 00:08:38.290 align:start position:0% all of the you know same the problems that<00:08:36.180> are<00:08:36.330> going<00:08:36.720> on<00:08:36.900> in<00:08:36.990> the<00:08:37.080> ecosystem<00:08:37.620> so 00:08:38.290 --> 00:08:38.300 align:start position:0% that are going on in the ecosystem so 00:08:38.300 --> 00:08:41.480 align:start position:0% that are going on in the ecosystem so currently<00:08:39.300> more<00:08:39.960> than<00:08:40.140> 70%<00:08:40.860> of<00:08:40.979> the<00:08:41.040> users 00:08:41.480 --> 00:08:41.490 align:start position:0% currently more than 70% of the users 00:08:41.490 --> 00:08:43.820 align:start position:0% currently more than 70% of the users don't<00:08:42.270> make<00:08:42.450> it<00:08:42.540> past<00:08:42.690> the<00:08:42.840> first<00:08:42.990> page<00:08:43.260> so<00:08:43.680> we 00:08:43.820 --> 00:08:43.830 align:start position:0% don't make it past the first page so we 00:08:43.830 --> 00:08:46.190 align:start position:0% don't make it past the first page so we know<00:08:43.919> this<00:08:44.099> from<00:08:44.280> our<00:08:44.400> analytics<00:08:44.940> and<00:08:45.240> more 00:08:46.190 --> 00:08:46.200 align:start position:0% know this from our analytics and more 00:08:46.200 --> 00:08:48.710 align:start position:0% know this from our analytics and more than<00:08:46.350> 90%<00:08:46.680> the<00:08:47.070> users<00:08:47.340> who<00:08:47.520> are<00:08:47.550> staking<00:08:48.180> had 00:08:48.710 --> 00:08:48.720 align:start position:0% than 90% the users who are staking had 00:08:48.720 --> 00:08:51.050 align:start position:0% than 90% the users who are staking had to<00:08:48.930> rely<00:08:49.170> on<00:08:49.200> the<00:08:49.440> community<00:08:49.650> and<00:08:50.190> some<00:08:50.550> human 00:08:51.050 --> 00:08:51.060 align:start position:0% to rely on the community and some human 00:08:51.060 --> 00:08:52.370 align:start position:0% to rely on the community and some human input<00:08:51.330> to<00:08:51.510> even<00:08:51.840> just<00:08:51.990> get<00:08:52.110> through<00:08:52.290> the 00:08:52.370 --> 00:08:52.380 align:start position:0% input to even just get through the 00:08:52.380 --> 00:08:54.590 align:start position:0% input to even just get through the staking<00:08:52.650> first<00:08:52.950> experience<00:08:53.600> probably 00:08:54.590 --> 00:08:54.600 align:start position:0% staking first experience probably 00:08:54.600 --> 00:08:56.120 align:start position:0% staking first experience probably something<00:08:54.960> else<00:08:55.080> is<00:08:55.200> more<00:08:55.320> shocking<00:08:55.620> is 00:08:56.120 --> 00:08:56.130 align:start position:0% something else is more shocking is 00:08:56.130 --> 00:08:58.430 align:start position:0% something else is more shocking is the<00:08:56.850> first<00:08:57.180> steak<00:08:57.660> experience<00:08:58.140> can<00:08:58.290> take 00:08:58.430 --> 00:08:58.440 align:start position:0% the first steak experience can take 00:08:58.440 --> 00:09:00.740 align:start position:0% the first steak experience can take anywhere<00:08:58.770> between<00:08:58.950> 30<00:08:59.670> minutes<00:08:59.760> to<00:09:00.330> upwards 00:09:00.740 --> 00:09:00.750 align:start position:0% anywhere between 30 minutes to upwards 00:09:00.750 --> 00:09:03.170 align:start position:0% anywhere between 30 minutes to upwards of<00:09:00.900> three<00:09:01.200> days<00:09:01.380> for<00:09:02.070> some<00:09:02.280> unfortunate<00:09:02.700> users 00:09:03.170 --> 00:09:03.180 align:start position:0% of three days for some unfortunate users 00:09:03.180 --> 00:09:05.930 align:start position:0% of three days for some unfortunate users who<00:09:03.360> are<00:09:03.630> truly<00:09:03.990> lost<00:09:04.520> so<00:09:05.520> that's<00:09:05.700> not 00:09:05.930 --> 00:09:05.940 align:start position:0% who are truly lost so that's not 00:09:05.940 --> 00:09:08.270 align:start position:0% who are truly lost so that's not acceptable<00:09:06.240> and<00:09:06.720> that<00:09:06.750> led<00:09:07.680> us<00:09:07.710> to<00:09:07.830> formulate 00:09:08.270 --> 00:09:08.280 align:start position:0% acceptable and that led us to formulate 00:09:08.280 --> 00:09:11.360 align:start position:0% acceptable and that led us to formulate these<00:09:09.000> two<00:09:09.390> North<00:09:09.810> Stars<00:09:10.170> for<00:09:10.560> where<00:09:11.040> we<00:09:11.160> want 00:09:11.360 --> 00:09:11.370 align:start position:0% these two North Stars for where we want 00:09:11.370 --> 00:09:14.390 align:start position:0% these two North Stars for where we want to<00:09:11.430> be<00:09:11.720> so<00:09:12.720> the<00:09:12.960> two<00:09:13.140> key<00:09:13.380> targets<00:09:13.800> for<00:09:13.980> us<00:09:14.130> in 00:09:14.390 --> 00:09:14.400 align:start position:0% to be so the two key targets for us in 00:09:14.400 --> 00:09:17.810 align:start position:0% to be so the two key targets for us in our<00:09:14.700> staking<00:09:15.360> a<00:09:15.530> design<00:09:16.530> would<00:09:16.920> be<00:09:16.980> we<00:09:17.610> want 00:09:17.810 --> 00:09:17.820 align:start position:0% our staking a design would be we want 00:09:17.820 --> 00:09:19.730 align:start position:0% our staking a design would be we want all<00:09:18.030> of<00:09:18.090> the<00:09:18.450> users<00:09:18.780> or<00:09:19.050> sorry<00:09:19.380> eight<00:09:19.590> out<00:09:19.710> of 00:09:19.730 --> 00:09:19.740 align:start position:0% all of the users or sorry eight out of 00:09:19.740 --> 00:09:21.560 align:start position:0% all of the users or sorry eight out of ten<00:09:20.010> users<00:09:20.190> to<00:09:20.550> be<00:09:20.640> able<00:09:20.730> to<00:09:20.880> complete<00:09:21.210> staking 00:09:21.560 --> 00:09:21.570 align:start position:0% ten users to be able to complete staking 00:09:21.570 --> 00:09:23.720 align:start position:0% ten users to be able to complete staking autonomously<00:09:22.200> supported<00:09:23.100> by<00:09:23.220> the<00:09:23.280> interface 00:09:23.720 --> 00:09:23.730 align:start position:0% autonomously supported by the interface 00:09:23.730 --> 00:09:25.430 align:start position:0% autonomously supported by the interface alone<00:09:24.060> and<00:09:24.300> that<00:09:24.630> means<00:09:24.810> no<00:09:25.140> human 00:09:25.430 --> 00:09:25.440 align:start position:0% alone and that means no human 00:09:25.440 --> 00:09:27.860 align:start position:0% alone and that means no human intervention<00:09:25.650> they<00:09:26.340> just<00:09:26.580> figure<00:09:26.910> it<00:09:26.970> out<00:09:27.030> the 00:09:27.860 --> 00:09:27.870 align:start position:0% intervention they just figure it out the 00:09:27.870 --> 00:09:29.630 align:start position:0% intervention they just figure it out the second<00:09:28.230> thing<00:09:28.380> is<00:09:28.620> that<00:09:28.650> we<00:09:28.950> want<00:09:29.160> more<00:09:29.460> than 00:09:29.630 --> 00:09:29.640 align:start position:0% second thing is that we want more than 00:09:29.640 --> 00:09:31.400 align:start position:0% second thing is that we want more than 50%<00:09:29.940> of<00:09:30.240> the<00:09:30.330> users<00:09:30.600> to<00:09:30.750> be<00:09:30.840> able<00:09:30.990> to<00:09:31.080> stick<00:09:31.290> in 00:09:31.400 --> 00:09:31.410 align:start position:0% 50% of the users to be able to stick in 00:09:31.410 --> 00:09:34.310 align:start position:0% 50% of the users to be able to stick in under<00:09:31.740> five<00:09:31.950> minutes<00:09:31.980> and<00:09:32.580> as<00:09:32.910> we<00:09:33.120> said<00:09:33.900> this 00:09:34.310 --> 00:09:34.320 align:start position:0% under five minutes and as we said this 00:09:34.320 --> 00:09:37.880 align:start position:0% under five minutes and as we said this is<00:09:34.500> a<00:09:34.650> really<00:09:35.040> key<00:09:35.250> thing<00:09:35.460> for<00:09:35.490> us<00:09:36.680> so<00:09:37.680> how<00:09:37.830> do 00:09:37.880 --> 00:09:37.890 align:start position:0% is a really key thing for us so how do 00:09:37.890 --> 00:09:39.830 align:start position:0% is a really key thing for us so how do we<00:09:38.040> go<00:09:38.400> about<00:09:38.520> accomplishing<00:09:39.030> this<00:09:39.600> right 00:09:39.830 --> 00:09:39.840 align:start position:0% we go about accomplishing this right 00:09:39.840 --> 00:09:43.250 align:start position:0% we go about accomplishing this right these<00:09:40.470> two<00:09:40.680> goals<00:09:40.910> well<00:09:41.910> as<00:09:42.090> a<00:09:42.480> good<00:09:42.870> human 00:09:43.250 --> 00:09:43.260 align:start position:0% these two goals well as a good human 00:09:43.260 --> 00:09:46.070 align:start position:0% these two goals well as a good human centered<00:09:43.590> designer<00:09:44.370> we<00:09:45.090> asked<00:09:45.360> the<00:09:45.420> first 00:09:46.070 --> 00:09:46.080 align:start position:0% centered designer we asked the first 00:09:46.080 --> 00:09:47.870 align:start position:0% centered designer we asked the first question<00:09:46.260> first<00:09:46.650> which<00:09:46.980> is<00:09:47.160> for<00:09:47.490> whom<00:09:47.670> are<00:09:47.820> we 00:09:47.870 --> 00:09:47.880 align:start position:0% question first which is for whom are we 00:09:47.880 --> 00:09:48.830 align:start position:0% question first which is for whom are we designing<00:09:48.300> anyway 00:09:48.830 --> 00:09:48.840 align:start position:0% designing anyway 00:09:48.840 --> 00:09:52.880 align:start position:0% designing anyway and<00:09:49.820> we<00:09:50.820> went<00:09:51.000> to<00:09:51.210> our<00:09:51.240> community<00:09:51.900> for<00:09:52.080> that<00:09:52.170> we 00:09:52.880 --> 00:09:52.890 align:start position:0% and we went to our community for that we 00:09:52.890 --> 00:09:55.250 align:start position:0% and we went to our community for that we did<00:09:53.700> generative<00:09:54.270> research<00:09:54.600> with<00:09:54.930> 30 00:09:55.250 --> 00:09:55.260 align:start position:0% did generative research with 30 00:09:55.260 --> 00:09:56.510 align:start position:0% did generative research with 30 community<00:09:55.770> members<00:09:56.100> who<00:09:56.280> are<00:09:56.340> currently 00:09:56.510 --> 00:09:56.520 align:start position:0% community members who are currently 00:09:56.520 --> 00:09:58.280 align:start position:0% community members who are currently stickers<00:09:57.180> and<00:09:57.450> figured<00:09:57.990> out<00:09:58.080> that<00:09:58.230> our 00:09:58.280 --> 00:09:58.290 align:start position:0% stickers and figured out that our 00:09:58.290 --> 00:09:59.840 align:start position:0% stickers and figured out that our audience<00:09:58.440> really<00:09:58.950> has<00:09:59.130> this<00:09:59.280> investor 00:09:59.840 --> 00:09:59.850 align:start position:0% audience really has this investor 00:09:59.850 --> 00:10:02.390 align:start position:0% audience really has this investor mindset<00:10:00.090> and<00:10:00.600> we<00:10:01.230> further<00:10:01.470> sub<00:10:01.890> segmented 00:10:02.390 --> 00:10:02.400 align:start position:0% mindset and we further sub segmented 00:10:02.400 --> 00:10:03.860 align:start position:0% mindset and we further sub segmented them<00:10:02.490> and<00:10:02.730> figured<00:10:03.270> out<00:10:03.360> who<00:10:03.510> our<00:10:03.540> early 00:10:03.860 --> 00:10:03.870 align:start position:0% them and figured out who our early 00:10:03.870 --> 00:10:05.920 align:start position:0% them and figured out who our early adopters<00:10:03.960> are<00:10:04.440> in<00:10:04.650> the<00:10:05.340> community<00:10:05.700> and 00:10:05.920 --> 00:10:05.930 align:start position:0% adopters are in the community and 00:10:05.930 --> 00:10:08.540 align:start position:0% adopters are in the community and another<00:10:06.930> way<00:10:07.110> to<00:10:07.170> resent<00:10:07.800> this<00:10:07.920> audience<00:10:08.250> is 00:10:08.540 --> 00:10:08.550 align:start position:0% another way to resent this audience is 00:10:08.550 --> 00:10:10.250 align:start position:0% another way to resent this audience is to<00:10:08.760> look<00:10:08.970> at<00:10:09.090> their<00:10:09.210> experience<00:10:09.570> with<00:10:09.870> staking 00:10:10.250 --> 00:10:10.260 align:start position:0% to look at their experience with staking 00:10:10.260 --> 00:10:12.320 align:start position:0% to look at their experience with staking in<00:10:10.350> general<00:10:10.680> because<00:10:11.250> we<00:10:11.400> want<00:10:11.580> to<00:10:11.700> design<00:10:11.850> for 00:10:12.320 --> 00:10:12.330 align:start position:0% in general because we want to design for 00:10:12.330 --> 00:10:14.870 align:start position:0% in general because we want to design for multiple<00:10:13.170> levels<00:10:13.740> of<00:10:13.830> experience<00:10:14.100> so<00:10:14.670> we<00:10:14.790> have 00:10:14.870 --> 00:10:14.880 align:start position:0% multiple levels of experience so we have 00:10:14.880 --> 00:10:16.820 align:start position:0% multiple levels of experience so we have new<00:10:15.060> users<00:10:15.390> and<00:10:15.420> experienced<00:10:15.930> users<00:10:16.200> which 00:10:16.820 --> 00:10:16.830 align:start position:0% new users and experienced users which 00:10:16.830 --> 00:10:18.590 align:start position:0% new users and experienced users which we'll<00:10:16.980> share<00:10:17.190> with<00:10:17.490> you<00:10:17.610> how<00:10:17.790> we<00:10:17.820> factor<00:10:18.510> that 00:10:18.590 --> 00:10:18.600 align:start position:0% we'll share with you how we factor that 00:10:18.600 --> 00:10:21.500 align:start position:0% we'll share with you how we factor that into<00:10:18.750> the<00:10:18.900> hoenn<00:10:19.020> boarding<00:10:19.820> ok<00:10:20.820> a<00:10:21.000> second 00:10:21.500 --> 00:10:21.510 align:start position:0% into the hoenn boarding ok a second 00:10:21.510 --> 00:10:22.910 align:start position:0% into the hoenn boarding ok a second category<00:10:21.750> of<00:10:22.080> information<00:10:22.200> that<00:10:22.650> we<00:10:22.740> looked 00:10:22.910 --> 00:10:22.920 align:start position:0% category of information that we looked 00:10:22.920 --> 00:10:24.980 align:start position:0% category of information that we looked at<00:10:23.070> is<00:10:23.310> what<00:10:23.790> are<00:10:23.820> all<00:10:24.090> of<00:10:24.150> the<00:10:24.420> other<00:10:24.660> apps 00:10:24.980 --> 00:10:24.990 align:start position:0% at is what are all of the other apps 00:10:24.990 --> 00:10:26.480 align:start position:0% at is what are all of the other apps doing<00:10:25.440> right<00:10:25.710> because<00:10:26.070> we<00:10:26.220> don't<00:10:26.340> want<00:10:26.460> to 00:10:26.480 --> 00:10:26.490 align:start position:0% doing right because we don't want to 00:10:26.490 --> 00:10:28.040 align:start position:0% doing right because we don't want to reinvent<00:10:26.850> the<00:10:26.910> wheel<00:10:26.970> want<00:10:27.660> to<00:10:27.720> take<00:10:27.870> what's 00:10:28.040 --> 00:10:28.050 align:start position:0% reinvent the wheel want to take what's 00:10:28.050 --> 00:10:30.530 align:start position:0% reinvent the wheel want to take what's good<00:10:28.820> some<00:10:29.820> of<00:10:29.850> the<00:10:29.940> apps<00:10:30.090> that<00:10:30.240> we<00:10:30.300> looked<00:10:30.330> at 00:10:30.530 --> 00:10:30.540 align:start position:0% good some of the apps that we looked at 00:10:30.540 --> 00:10:32.360 align:start position:0% good some of the apps that we looked at our<00:10:30.690> cosmos<00:10:31.200> Tazo<00:10:31.830> some<00:10:32.040> of<00:10:32.130> the<00:10:32.190> bigger 00:10:32.360 --> 00:10:32.370 align:start position:0% our cosmos Tazo some of the bigger 00:10:32.370 --> 00:10:34.370 align:start position:0% our cosmos Tazo some of the bigger sticking<00:10:32.970> apps<00:10:33.090> that<00:10:33.240> we<00:10:33.330> know<00:10:33.480> but<00:10:34.050> we<00:10:34.170> also 00:10:34.370 --> 00:10:34.380 align:start position:0% sticking apps that we know but we also 00:10:34.380 --> 00:10:36.020 align:start position:0% sticking apps that we know but we also looked<00:10:34.800> at<00:10:34.890> investment<00:10:35.490> apps<00:10:35.640> which<00:10:35.910> are 00:10:36.020 --> 00:10:36.030 align:start position:0% looked at investment apps which are 00:10:36.030 --> 00:10:37.910 align:start position:0% looked at investment apps which are relevant<00:10:36.300> to<00:10:36.660> what<00:10:37.110> our<00:10:37.260> users<00:10:37.680> are<00:10:37.830> already 00:10:37.910 --> 00:10:37.920 align:start position:0% relevant to what our users are already 00:10:37.920 --> 00:10:40.160 align:start position:0% relevant to what our users are already familiar<00:10:38.130> with<00:10:38.400> we<00:10:39.090> looked<00:10:39.270> at<00:10:39.390> the<00:10:39.450> UI<00:10:39.600> relate 00:10:40.160 --> 00:10:40.170 align:start position:0% familiar with we looked at the UI relate 00:10:40.170 --> 00:10:41.960 align:start position:0% familiar with we looked at the UI relate to<00:10:40.260> the<00:10:40.380> onboarding<00:10:40.890> flow<00:10:41.070> we<00:10:41.520> looked<00:10:41.700> at<00:10:41.850> the 00:10:41.960 --> 00:10:41.970 align:start position:0% to the onboarding flow we looked at the 00:10:41.970 --> 00:10:43.640 align:start position:0% to the onboarding flow we looked at the information<00:10:42.180> architecture<00:10:42.570> and<00:10:43.230> also<00:10:43.410> the 00:10:43.640 --> 00:10:43.650 align:start position:0% information architecture and also the 00:10:43.650 --> 00:10:47.510 align:start position:0% information architecture and also the sticking<00:10:43.980> interactions<00:10:44.510> and<00:10:46.190> thirdly<00:10:47.190> and 00:10:47.510 --> 00:10:47.520 align:start position:0% sticking interactions and thirdly and 00:10:47.520 --> 00:10:49.550 align:start position:0% sticking interactions and thirdly and most<00:10:47.790> importantly<00:10:48.180> we<00:10:48.960> really<00:10:49.290> wanted<00:10:49.470> to 00:10:49.550 --> 00:10:49.560 align:start position:0% most importantly we really wanted to 00:10:49.560 --> 00:10:50.900 align:start position:0% most importantly we really wanted to figure<00:10:49.650> out<00:10:49.800> what<00:10:49.950> are<00:10:50.040> the<00:10:50.130> user<00:10:50.310> pain<00:10:50.580> points 00:10:50.900 --> 00:10:50.910 align:start position:0% figure out what are the user pain points 00:10:50.910 --> 00:10:52.820 align:start position:0% figure out what are the user pain points and<00:10:51.000> that's<00:10:51.120> key<00:10:51.630> to<00:10:51.660> all<00:10:52.080> of<00:10:52.410> the<00:10:52.530> designs 00:10:52.820 --> 00:10:52.830 align:start position:0% and that's key to all of the designs 00:10:52.830 --> 00:10:55.520 align:start position:0% and that's key to all of the designs decisions<00:10:53.310> that<00:10:53.490> we<00:10:53.580> made<00:10:53.840> so<00:10:54.840> we<00:10:55.230> went<00:10:55.410> about 00:10:55.520 --> 00:10:55.530 align:start position:0% decisions that we made so we went about 00:10:55.530 --> 00:10:56.960 align:start position:0% decisions that we made so we went about constructing<00:10:56.130> the<00:10:56.220> user<00:10:56.400> during<00:10:56.640> from 00:10:56.960 --> 00:10:56.970 align:start position:0% constructing the user during from 00:10:56.970 --> 00:10:58.790 align:start position:0% constructing the user during from beginning<00:10:57.300> to<00:10:57.540> end<00:10:57.570> and<00:10:58.050> that<00:10:58.290> means<00:10:58.470> when 00:10:58.790 --> 00:10:58.800 align:start position:0% beginning to end and that means when 00:10:58.800 --> 00:11:00.860 align:start position:0% beginning to end and that means when they<00:10:59.070> first<00:10:59.400> got<00:10:59.670> involved<00:11:00.060> and<00:11:00.390> engaged<00:11:00.510> with 00:11:00.860 --> 00:11:00.870 align:start position:0% they first got involved and engaged with 00:11:00.870 --> 00:11:03.380 align:start position:0% they first got involved and engaged with life<00:11:01.110> here<00:11:01.290> as<00:11:01.440> a<00:11:01.530> brand<00:11:01.890> all<00:11:02.310> the<00:11:02.670> way<00:11:02.790> to<00:11:02.850> the 00:11:03.380 --> 00:11:03.390 align:start position:0% life here as a brand all the way to the 00:11:03.390 --> 00:11:06.050 align:start position:0% life here as a brand all the way to the end<00:11:03.570> when<00:11:03.870> they<00:11:03.960> State<00:11:04.470> took<00:11:04.800> it<00:11:04.950> and<00:11:05.130> some<00:11:06.000> of 00:11:06.050 --> 00:11:06.060 align:start position:0% end when they State took it and some of 00:11:06.060 --> 00:11:07.790 align:start position:0% end when they State took it and some of the<00:11:06.150> problems<00:11:06.810> we<00:11:06.870> surfaced<00:11:07.230> are<00:11:07.410> pretty 00:11:07.790 --> 00:11:07.800 align:start position:0% the problems we surfaced are pretty 00:11:07.800 --> 00:11:09.040 align:start position:0% the problems we surfaced are pretty similar<00:11:08.160> to<00:11:08.190> what's<00:11:08.460> going<00:11:08.730> on 00:11:09.040 --> 00:11:09.050 align:start position:0% similar to what's going on 00:11:09.050 --> 00:11:10.780 align:start position:0% similar to what's going on out<00:11:09.140> there<00:11:09.410> on<00:11:09.680> all<00:11:09.980> the<00:11:10.160> other<00:11:10.310> sticking<00:11:10.640> apps 00:11:10.780 --> 00:11:10.790 align:start position:0% out there on all the other sticking apps 00:11:10.790 --> 00:11:12.910 align:start position:0% out there on all the other sticking apps people<00:11:11.630> don't<00:11:11.810> understand<00:11:12.170> the<00:11:12.290> ROI<00:11:12.620> like 00:11:12.910 --> 00:11:12.920 align:start position:0% people don't understand the ROI like 00:11:12.920 --> 00:11:14.560 align:start position:0% people don't understand the ROI like what<00:11:13.279> am<00:11:13.370> I<00:11:13.459> even<00:11:13.490> getting<00:11:14.000> out<00:11:14.120> of<00:11:14.240> the<00:11:14.330> stick 00:11:14.560 --> 00:11:14.570 align:start position:0% what am I even getting out of the stick 00:11:14.570 --> 00:11:16.810 align:start position:0% what am I even getting out of the stick and<00:11:14.870> they<00:11:15.860> don't<00:11:16.070> understand<00:11:16.580> how<00:11:16.760> to 00:11:16.810 --> 00:11:16.820 align:start position:0% and they don't understand how to 00:11:16.820 --> 00:11:18.720 align:start position:0% and they don't understand how to evaluate<00:11:17.089> who<00:11:17.540> to<00:11:17.660> stick<00:11:17.810> towards<00:11:18.080> anyway 00:11:18.720 --> 00:11:18.730 align:start position:0% evaluate who to stick towards anyway 00:11:18.730 --> 00:11:21.850 align:start position:0% evaluate who to stick towards anyway they<00:11:19.730> don't<00:11:19.910> really<00:11:20.209> they<00:11:20.779> can't<00:11:21.350> finish<00:11:21.620> the 00:11:21.850 --> 00:11:21.860 align:start position:0% they don't really they can't finish the 00:11:21.860 --> 00:11:23.259 align:start position:0% they don't really they can't finish the first<00:11:22.070> sticking<00:11:22.370> experience<00:11:22.760> which<00:11:22.940> is<00:11:23.089> a 00:11:23.259 --> 00:11:23.269 align:start position:0% first sticking experience which is a 00:11:23.269 --> 00:11:25.750 align:start position:0% first sticking experience which is a huge<00:11:23.720> problem<00:11:23.899> and<00:11:24.170> lastly<00:11:24.920> the<00:11:25.250> confusing 00:11:25.750 --> 00:11:25.760 align:start position:0% huge problem and lastly the confusing 00:11:25.760 --> 00:11:27.400 align:start position:0% huge problem and lastly the confusing terminology<00:11:25.940> detracted<00:11:26.810> greatly<00:11:27.140> from<00:11:27.290> the 00:11:27.400 --> 00:11:27.410 align:start position:0% terminology detracted greatly from the 00:11:27.410 --> 00:11:34.389 align:start position:0% terminology detracted greatly from the experience<00:11:30.730> awesome<00:11:31.760> so<00:11:33.130> based<00:11:34.130> on<00:11:34.279> these 00:11:34.389 --> 00:11:34.399 align:start position:0% experience awesome so based on these 00:11:34.399 --> 00:11:36.550 align:start position:0% experience awesome so based on these these<00:11:34.970> user<00:11:35.360> pain<00:11:35.630> points<00:11:35.899> that<00:11:36.050> show<00:11:36.200> on<00:11:36.320> just 00:11:36.550 --> 00:11:36.560 align:start position:0% these user pain points that show on just 00:11:36.560 --> 00:11:39.040 align:start position:0% these user pain points that show on just described<00:11:37.010> we<00:11:37.880> identified<00:11:38.390> really<00:11:38.779> five 00:11:39.040 --> 00:11:39.050 align:start position:0% described we identified really five 00:11:39.050 --> 00:11:41.400 align:start position:0% described we identified really five areas<00:11:39.500> that<00:11:39.740> we<00:11:39.860> felt<00:11:40.100> we<00:11:40.700> could<00:11:40.730> really 00:11:41.400 --> 00:11:41.410 align:start position:0% areas that we felt we could really 00:11:41.410 --> 00:11:43.509 align:start position:0% areas that we felt we could really improve<00:11:42.410> the<00:11:42.560> onboarding<00:11:42.890> experience<00:11:43.010> for 00:11:43.509 --> 00:11:43.519 align:start position:0% improve the onboarding experience for 00:11:43.519 --> 00:11:47.259 align:start position:0% improve the onboarding experience for this<00:11:43.610> this<00:11:43.850> new<00:11:44.000> staking<00:11:44.420> app<00:11:45.850> so<00:11:46.850> I'll<00:11:47.180> go 00:11:47.259 --> 00:11:47.269 align:start position:0% this this new staking app so I'll go 00:11:47.269 --> 00:11:49.840 align:start position:0% this this new staking app so I'll go through<00:11:47.450> them<00:11:47.600> so<00:11:48.350> number<00:11:49.190> one<00:11:49.339> we<00:11:49.519> introduced 00:11:49.840 --> 00:11:49.850 align:start position:0% through them so number one we introduced 00:11:49.850 --> 00:11:51.880 align:start position:0% through them so number one we introduced a<00:11:49.970> more<00:11:50.180> intuitive<00:11:50.890> information 00:11:51.880 --> 00:11:51.890 align:start position:0% a more intuitive information 00:11:51.890 --> 00:11:53.710 align:start position:0% a more intuitive information architecture<00:11:52.700> that<00:11:52.820> really<00:11:52.970> Shepard's<00:11:53.420> users 00:11:53.710 --> 00:11:53.720 align:start position:0% architecture that really Shepard's users 00:11:53.720 --> 00:11:56.440 align:start position:0% architecture that really Shepard's users to<00:11:53.899> where<00:11:54.019> they<00:11:54.140> need<00:11:54.290> to<00:11:54.320> go<00:11:55.180> so<00:11:56.180> they're<00:11:56.300> over 00:11:56.440 --> 00:11:56.450 align:start position:0% to where they need to go so they're over 00:11:56.450 --> 00:11:58.690 align:start position:0% to where they need to go so they're over like<00:11:56.720> 14<00:11:57.290> views<00:11:57.800> but<00:11:58.010> if<00:11:58.100> you<00:11:58.190> really<00:11:58.339> boil<00:11:58.550> it 00:11:58.690 --> 00:11:58.700 align:start position:0% like 14 views but if you really boil it 00:11:58.700 --> 00:12:01.329 align:start position:0% like 14 views but if you really boil it down<00:11:58.730> there's<00:11:59.120> like<00:11:59.300> three<00:11:59.720> high-level<00:12:00.380> views 00:12:01.329 --> 00:12:01.339 align:start position:0% down there's like three high-level views 00:12:01.339 --> 00:12:04.060 align:start position:0% down there's like three high-level views so<00:12:02.329> there's<00:12:02.600> the<00:12:02.750> orchestrator<00:12:03.290> is<00:12:03.500> list<00:12:03.860> view 00:12:04.060 --> 00:12:04.070 align:start position:0% so there's the orchestrator is list view 00:12:04.070 --> 00:12:05.769 align:start position:0% so there's the orchestrator is list view which<00:12:04.250> orchestrators<00:12:05.060> in<00:12:05.300> the<00:12:05.420> live<00:12:05.540> peer 00:12:05.769 --> 00:12:05.779 align:start position:0% which orchestrators in the live peer 00:12:05.779 --> 00:12:09.040 align:start position:0% which orchestrators in the live peer protocol<00:12:06.170> are<00:12:06.290> the<00:12:06.649> delegates<00:12:07.839> there's<00:12:08.839> the 00:12:09.040 --> 00:12:09.050 align:start position:0% protocol are the delegates there's the 00:12:09.050 --> 00:12:12.250 align:start position:0% protocol are the delegates there's the orchestrator<00:12:09.500> profile<00:12:09.980> and<00:12:10.899> the<00:12:11.899> token 00:12:12.250 --> 00:12:12.260 align:start position:0% orchestrator profile and the token 00:12:12.260 --> 00:12:14.590 align:start position:0% orchestrator profile and the token holder<00:12:12.500> profile<00:12:12.890> a<00:12:13.130> key<00:12:13.970> takeaway<00:12:14.149> here<00:12:14.420> is 00:12:14.590 --> 00:12:14.600 align:start position:0% holder profile a key takeaway here is 00:12:14.600 --> 00:12:16.360 align:start position:0% holder profile a key takeaway here is that<00:12:14.690> you'll<00:12:15.620> notice<00:12:15.860> there's<00:12:16.010> a<00:12:16.070> call<00:12:16.250> to 00:12:16.360 --> 00:12:16.370 align:start position:0% that you'll notice there's a call to 00:12:16.370 --> 00:12:19.360 align:start position:0% that you'll notice there's a call to action<00:12:16.490> to<00:12:16.730> steak<00:12:17.180> or<00:12:17.540> on<00:12:18.079> steak<00:12:18.350> on<00:12:18.950> each<00:12:19.160> one 00:12:19.360 --> 00:12:19.370 align:start position:0% action to steak or on steak on each one 00:12:19.370 --> 00:12:20.500 align:start position:0% action to steak or on steak on each one of<00:12:19.490> these<00:12:19.579> views<00:12:19.880> so<00:12:20.149> whether<00:12:20.329> you're 00:12:20.500 --> 00:12:20.510 align:start position:0% of these views so whether you're 00:12:20.510 --> 00:12:22.900 align:start position:0% of these views so whether you're evaluating<00:12:21.110> transcoders<00:12:21.740> or<00:12:21.950> managing<00:12:22.790> your 00:12:22.900 --> 00:12:22.910 align:start position:0% evaluating transcoders or managing your 00:12:22.910 --> 00:12:25.000 align:start position:0% evaluating transcoders or managing your your<00:12:23.690> existing<00:12:24.140> steak<00:12:24.440> that<00:12:24.770> core<00:12:24.980> value 00:12:25.000 --> 00:12:25.010 align:start position:0% your existing steak that core value 00:12:25.010 --> 00:12:27.639 align:start position:0% your existing steak that core value proposition<00:12:25.820> is<00:12:25.940> always<00:12:26.320> available<00:12:27.320> and 00:12:27.639 --> 00:12:27.649 align:start position:0% proposition is always available and 00:12:27.649 --> 00:12:30.310 align:start position:0% proposition is always available and highly<00:12:27.890> visible<00:12:28.720> so<00:12:29.720> this<00:12:29.839> was<00:12:29.959> just<00:12:29.990> an 00:12:30.310 --> 00:12:30.320 align:start position:0% highly visible so this was just an 00:12:30.320 --> 00:12:31.810 align:start position:0% highly visible so this was just an important<00:12:30.649> design<00:12:30.860> consideration<00:12:31.010> in 00:12:31.810 --> 00:12:31.820 align:start position:0% important design consideration in 00:12:31.820 --> 00:12:33.819 align:start position:0% important design consideration in getting<00:12:32.420> users<00:12:32.690> staked<00:12:32.959> in<00:12:33.079> under<00:12:33.320> five 00:12:33.819 --> 00:12:33.829 align:start position:0% getting users staked in under five 00:12:33.829 --> 00:12:34.800 align:start position:0% getting users staked in under five minutes 00:12:34.800 --> 00:12:34.810 align:start position:0% minutes 00:12:34.810 --> 00:12:39.010 align:start position:0% minutes we<00:12:35.810> established<00:12:35.930> a<00:12:36.380> language<00:12:37.100> system<00:12:37.459> so<00:12:38.020> this 00:12:39.010 --> 00:12:39.020 align:start position:0% we established a language system so this 00:12:39.020 --> 00:12:42.579 align:start position:0% we established a language system so this was<00:12:39.230> I<00:12:39.440> mean<00:12:39.680> it's<00:12:40.339> small<00:12:40.520> but<00:12:41.410> important<00:12:42.410> so 00:12:42.579 --> 00:12:42.589 align:start position:0% was I mean it's small but important so 00:12:42.589 --> 00:12:43.720 align:start position:0% was I mean it's small but important so this<00:12:42.680> was<00:12:42.829> really<00:12:43.070> just<00:12:43.160> an<00:12:43.310> exercise<00:12:43.579> in 00:12:43.720 --> 00:12:43.730 align:start position:0% this was really just an exercise in 00:12:43.730 --> 00:12:47.100 align:start position:0% this was really just an exercise in reaching<00:12:44.240> consensus<00:12:44.810> with<00:12:45.740> the<00:12:45.770> team<00:12:46.070> on<00:12:46.310> on 00:12:47.100 --> 00:12:47.110 align:start position:0% reaching consensus with the team on on 00:12:47.110 --> 00:12:50.440 align:start position:0% reaching consensus with the team on on you<00:12:48.110> know<00:12:48.200> vernacular<00:12:48.560> so<00:12:49.310> removing<00:12:50.089> certain 00:12:50.440 --> 00:12:50.450 align:start position:0% you know vernacular so removing certain 00:12:50.450 --> 00:12:56.199 align:start position:0% you know vernacular so removing certain words<00:12:51.410> and<00:12:51.770> renaming<00:12:52.250> others<00:12:54.760> we<00:12:55.760> introduced 00:12:56.199 --> 00:12:56.209 align:start position:0% words and renaming others we introduced 00:12:56.209 --> 00:12:59.470 align:start position:0% words and renaming others we introduced opt-in<00:12:56.720> identity<00:12:57.230> using<00:12:58.000> using<00:12:59.000> a<00:12:59.180> project 00:12:59.470 --> 00:12:59.480 align:start position:0% opt-in identity using using a project 00:12:59.480 --> 00:13:00.400 align:start position:0% opt-in identity using using a project called<00:12:59.779> three<00:13:00.020> bucks 00:13:00.400 --> 00:13:00.410 align:start position:0% called three bucks 00:13:00.410 --> 00:13:02.019 align:start position:0% called three bucks so<00:13:00.980> this<00:13:01.160> accomplishes<00:13:01.640> really<00:13:01.850> two<00:13:02.000> things 00:13:02.019 --> 00:13:02.029 align:start position:0% so this accomplishes really two things 00:13:02.029 --> 00:13:05.130 align:start position:0% so this accomplishes really two things so<00:13:02.660> number<00:13:02.899> one<00:13:03.079> it<00:13:03.199> helps<00:13:03.440> users<00:13:03.620> evaluate 00:13:05.130 --> 00:13:05.140 align:start position:0% so number one it helps users evaluate 00:13:05.140 --> 00:13:07.360 align:start position:0% so number one it helps users evaluate who<00:13:06.140> to<00:13:06.320> stake<00:13:06.529> to<00:13:06.709> and<00:13:06.920> then<00:13:07.130> it<00:13:07.250> gives 00:13:07.360 --> 00:13:07.370 align:start position:0% who to stake to and then it gives 00:13:07.370 --> 00:13:09.910 align:start position:0% who to stake to and then it gives orchestrators<00:13:08.149> campaigns<00:13:08.920> greater 00:13:09.910 --> 00:13:09.920 align:start position:0% orchestrators campaigns greater 00:13:09.920 --> 00:13:11.590 align:start position:0% orchestrators campaigns greater visibility<00:13:10.220> into<00:13:10.760> the<00:13:10.970> app<00:13:11.089> so<00:13:11.329> they<00:13:11.420> don't 00:13:11.590 --> 00:13:11.600 align:start position:0% visibility into the app so they don't 00:13:11.600 --> 00:13:16.210 align:start position:0% visibility into the app so they don't have<00:13:11.720> to<00:13:11.930> go<00:13:12.529> digging<00:13:12.769> off<00:13:13.040> app<00:13:14.829> we<00:13:15.829> introduced 00:13:16.210 --> 00:13:16.220 align:start position:0% have to go digging off app we introduced 00:13:16.220 --> 00:13:17.910 align:start position:0% have to go digging off app we introduced what<00:13:16.339> we're<00:13:16.430> calling<00:13:16.579> a<00:13:16.760> staking<00:13:17.180> widget<00:13:17.480> so 00:13:17.910 --> 00:13:17.920 align:start position:0% what we're calling a staking widget so 00:13:17.920 --> 00:13:20.439 align:start position:0% what we're calling a staking widget so this<00:13:18.920> really<00:13:19.130> accomplishes<00:13:19.790> three<00:13:20.120> things 00:13:20.439 --> 00:13:20.449 align:start position:0% this really accomplishes three things 00:13:20.449 --> 00:13:21.860 align:start position:0% this really accomplishes three things number<00:13:20.690> one<00:13:20.930> it 00:13:21.860 --> 00:13:21.870 align:start position:0% number one it 00:13:21.870 --> 00:13:23.329 align:start position:0% number one it it<00:13:22.139> allows<00:13:22.350> you<00:13:22.499> to<00:13:22.529> connect<00:13:22.860> your<00:13:22.980> wallets 00:13:23.329 --> 00:13:23.339 align:start position:0% it allows you to connect your wallets 00:13:23.339 --> 00:13:26.210 align:start position:0% it allows you to connect your wallets number<00:13:23.819> to<00:13:23.999> it<00:13:24.209> it<00:13:24.990> it<00:13:25.290> helps<00:13:25.680> you<00:13:25.769> understand 00:13:26.210 --> 00:13:26.220 align:start position:0% number to it it it helps you understand 00:13:26.220 --> 00:13:28.429 align:start position:0% number to it it it helps you understand what<00:13:26.519> you're<00:13:26.670> getting<00:13:26.939> from<00:13:27.779> staking<00:13:28.139> before 00:13:28.429 --> 00:13:28.439 align:start position:0% what you're getting from staking before 00:13:28.439 --> 00:13:29.929 align:start position:0% what you're getting from staking before you<00:13:28.529> actually<00:13:28.709> stake<00:13:29.249> so<00:13:29.610> in<00:13:29.699> the<00:13:29.759> case<00:13:29.910> of 00:13:29.929 --> 00:13:29.939 align:start position:0% you actually stake so in the case of 00:13:29.939 --> 00:13:32.420 align:start position:0% you actually stake so in the case of life<00:13:30.329> here<00:13:30.689> that's<00:13:30.899> projected<00:13:31.430> rewards 00:13:32.420 --> 00:13:32.430 align:start position:0% life here that's projected rewards 00:13:32.430 --> 00:13:37.460 align:start position:0% life here that's projected rewards projected<00:13:32.999> earned<00:13:33.149> fees<00:13:34.490> voting<00:13:35.490> power<00:13:36.470> and 00:13:37.460 --> 00:13:37.470 align:start position:0% projected earned fees voting power and 00:13:37.470 --> 00:13:40.429 align:start position:0% projected earned fees voting power and then<00:13:37.730> thirdly<00:13:38.730> it<00:13:39.180> leads<00:13:39.509> directly<00:13:39.689> into<00:13:40.139> the 00:13:40.429 --> 00:13:40.439 align:start position:0% then thirdly it leads directly into the 00:13:40.439 --> 00:13:42.829 align:start position:0% then thirdly it leads directly into the staking<00:13:40.920> interaction<00:13:41.670> so<00:13:41.939> this<00:13:42.540> is<00:13:42.629> kind<00:13:42.809> of 00:13:42.829 --> 00:13:42.839 align:start position:0% staking interaction so this is kind of 00:13:42.839 --> 00:13:44.480 align:start position:0% staking interaction so this is kind of like<00:13:42.959> a<00:13:43.019> mini<00:13:43.199> app<00:13:43.379> in<00:13:43.559> and<00:13:43.680> of<00:13:43.769> itself<00:13:44.040> and<00:13:44.339> we 00:13:44.480 --> 00:13:44.490 align:start position:0% like a mini app in and of itself and we 00:13:44.490 --> 00:13:46.309 align:start position:0% like a mini app in and of itself and we really<00:13:44.759> like<00:13:44.879> it<00:13:45.059> because<00:13:45.120> it<00:13:45.389> it<00:13:45.899> I<00:13:46.079> think 00:13:46.309 --> 00:13:46.319 align:start position:0% really like it because it it I think 00:13:46.319 --> 00:13:49.429 align:start position:0% really like it because it it I think lends<00:13:46.589> itself<00:13:46.949> to<00:13:48.170> embedding<00:13:49.170> in<00:13:49.290> other 00:13:49.429 --> 00:13:49.439 align:start position:0% lends itself to embedding in other 00:13:49.439 --> 00:13:50.869 align:start position:0% lends itself to embedding in other applications<00:13:49.800> so<00:13:50.370> if<00:13:50.490> you're<00:13:50.670> an 00:13:50.869 --> 00:13:50.879 align:start position:0% applications so if you're an 00:13:50.879 --> 00:13:53.119 align:start position:0% applications so if you're an Orchestrator<00:13:51.809> running<00:13:52.559> a<00:13:52.620> note<00:13:52.769> in<00:13:52.920> a<00:13:52.980> live 00:13:53.119 --> 00:13:53.129 align:start position:0% Orchestrator running a note in a live 00:13:53.129 --> 00:13:55.819 align:start position:0% Orchestrator running a note in a live care<00:13:53.370> network<00:13:53.839> we<00:13:54.839> can<00:13:54.870> see<00:13:55.170> you<00:13:55.379> you<00:13:55.740> know 00:13:55.819 --> 00:13:55.829 align:start position:0% care network we can see you you know 00:13:55.829 --> 00:13:57.290 align:start position:0% care network we can see you you know embedding<00:13:56.220> this<00:13:56.339> on<00:13:56.490> your<00:13:56.639> own<00:13:56.670> site<00:13:57.059> to 00:13:57.290 --> 00:13:57.300 align:start position:0% embedding this on your own site to 00:13:57.300 --> 00:14:03.079 align:start position:0% embedding this on your own site to campaign<00:13:57.870> for<00:13:58.589> for<00:13:59.069> a<00:13:59.100> token<00:13:59.309> holders<00:14:02.089> now 00:14:03.079 --> 00:14:03.089 align:start position:0% campaign for for a token holders now 00:14:03.089 --> 00:14:04.999 align:start position:0% campaign for for a token holders now that<00:14:03.300> we've<00:14:03.449> seen<00:14:03.720> how<00:14:03.779> the<00:14:04.559> information 00:14:04.999 --> 00:14:05.009 align:start position:0% that we've seen how the information 00:14:05.009 --> 00:14:07.280 align:start position:0% that we've seen how the information architecture<00:14:05.209> have<00:14:06.209> been<00:14:06.449> reorganized<00:14:07.019> and 00:14:07.280 --> 00:14:07.290 align:start position:0% architecture have been reorganized and 00:14:07.290 --> 00:14:09.230 align:start position:0% architecture have been reorganized and how<00:14:07.649> the<00:14:07.709> UI<00:14:07.980> elements<00:14:08.490> have<00:14:08.579> been<00:14:08.610> really 00:14:09.230 --> 00:14:09.240 align:start position:0% how the UI elements have been really 00:14:09.240 --> 00:14:11.059 align:start position:0% how the UI elements have been really designed<00:14:09.899> to<00:14:10.050> support<00:14:10.410> onboarding<00:14:10.860> and 00:14:11.059 --> 00:14:11.069 align:start position:0% designed to support onboarding and 00:14:11.069 --> 00:14:12.860 align:start position:0% designed to support onboarding and understanding<00:14:11.639> let's<00:14:12.120> see<00:14:12.300> how<00:14:12.420> all<00:14:12.629> those 00:14:12.860 --> 00:14:12.870 align:start position:0% understanding let's see how all those 00:14:12.870 --> 00:14:14.389 align:start position:0% understanding let's see how all those elements<00:14:13.110> kind<00:14:13.470> of<00:14:13.589> pulled<00:14:13.740> together<00:14:13.860> into<00:14:14.309> a 00:14:14.389 --> 00:14:14.399 align:start position:0% elements kind of pulled together into a 00:14:14.399 --> 00:14:16.970 align:start position:0% elements kind of pulled together into a cohesive<00:14:14.819> onboarding<00:14:15.449> experience<00:14:15.509> and<00:14:16.199> what 00:14:16.970 --> 00:14:16.980 align:start position:0% cohesive onboarding experience and what 00:14:16.980 --> 00:14:18.319 align:start position:0% cohesive onboarding experience and what we<00:14:17.069> did<00:14:17.220> here<00:14:17.249> was<00:14:17.579> creating<00:14:17.970> an<00:14:18.059> onboarding 00:14:18.319 --> 00:14:18.329 align:start position:0% we did here was creating an onboarding 00:14:18.329 --> 00:14:20.629 align:start position:0% we did here was creating an onboarding tutorial<00:14:18.779> and<00:14:18.990> as<00:14:19.439> Adam<00:14:19.800> mentioned<00:14:19.829> we<00:14:20.220> always 00:14:20.629 --> 00:14:20.639 align:start position:0% tutorial and as Adam mentioned we always 00:14:20.639 --> 00:14:22.519 align:start position:0% tutorial and as Adam mentioned we always have<00:14:20.819> just<00:14:20.939> one<00:14:21.300> call<00:14:21.509> to<00:14:21.629> action<00:14:21.990> there's<00:14:22.350> no 00:14:22.519 --> 00:14:22.529 align:start position:0% have just one call to action there's no 00:14:22.529 --> 00:14:24.829 align:start position:0% have just one call to action there's no distraction<00:14:23.040> but<00:14:23.550> for<00:14:23.999> the<00:14:24.089> onboarding<00:14:24.629> we 00:14:24.829 --> 00:14:24.839 align:start position:0% distraction but for the onboarding we 00:14:24.839 --> 00:14:26.990 align:start position:0% distraction but for the onboarding we give<00:14:25.019> people<00:14:25.170> a<00:14:25.379> place<00:14:25.559> to<00:14:25.769> start<00:14:26.009> and<00:14:26.279> that<00:14:26.850> is 00:14:26.990 --> 00:14:27.000 align:start position:0% give people a place to start and that is 00:14:27.000 --> 00:14:29.210 align:start position:0% give people a place to start and that is over<00:14:27.240> there<00:14:27.470> so<00:14:28.470> once<00:14:28.680> you've<00:14:28.800> launched<00:14:29.040> this 00:14:29.210 --> 00:14:29.220 align:start position:0% over there so once you've launched this 00:14:29.220 --> 00:14:31.429 align:start position:0% over there so once you've launched this tutorial<00:14:29.790> we<00:14:30.509> kind<00:14:30.720> of<00:14:30.779> learned<00:14:31.019> this<00:14:31.230> key 00:14:31.429 --> 00:14:31.439 align:start position:0% tutorial we kind of learned this key 00:14:31.439 --> 00:14:33.079 align:start position:0% tutorial we kind of learned this key lesson<00:14:31.829> which<00:14:32.160> is<00:14:32.189> you<00:14:32.459> can't<00:14:32.670> have<00:14:32.879> the<00:14:33.059> same 00:14:33.079 --> 00:14:33.089 align:start position:0% lesson which is you can't have the same 00:14:33.089 --> 00:14:35.329 align:start position:0% lesson which is you can't have the same onboarding<00:14:33.660> experience<00:14:33.990> for<00:14:34.170> everyone 00:14:35.329 --> 00:14:35.339 align:start position:0% onboarding experience for everyone 00:14:35.339 --> 00:14:37.759 align:start position:0% onboarding experience for everyone so<00:14:35.550> as<00:14:35.790> we<00:14:36.509> remember<00:14:36.930> we<00:14:37.110> had<00:14:37.230> two<00:14:37.500> key 00:14:37.759 --> 00:14:37.769 align:start position:0% so as we remember we had two key 00:14:37.769 --> 00:14:39.980 align:start position:0% so as we remember we had two key audiences<00:14:38.449> experience<00:14:39.449> levels<00:14:39.779> that<00:14:39.899> we 00:14:39.980 --> 00:14:39.990 align:start position:0% audiences experience levels that we 00:14:39.990 --> 00:14:41.990 align:start position:0% audiences experience levels that we wanted<00:14:40.199> to<00:14:40.259> sign<00:14:40.439> for<00:14:40.620> and<00:14:40.860> that<00:14:41.279> is<00:14:41.399> new<00:14:41.639> users 00:14:41.990 --> 00:14:42.000 align:start position:0% wanted to sign for and that is new users 00:14:42.000 --> 00:14:44.749 align:start position:0% wanted to sign for and that is new users and<00:14:42.029> experienced<00:14:42.930> users<00:14:43.259> new<00:14:43.920> users<00:14:44.309> really 00:14:44.749 --> 00:14:44.759 align:start position:0% and experienced users new users really 00:14:44.759 --> 00:14:46.189 align:start position:0% and experienced users new users really can't<00:14:45.059> do<00:14:45.209> without<00:14:45.360> a<00:14:45.509> lot<00:14:45.870> of<00:14:45.990> hand-holding 00:14:46.189 --> 00:14:46.199 align:start position:0% can't do without a lot of hand-holding 00:14:46.199 --> 00:14:48.619 align:start position:0% can't do without a lot of hand-holding but<00:14:46.889> experienced<00:14:47.430> users<00:14:47.699> are<00:14:47.939> boggled<00:14:48.480> down 00:14:48.619 --> 00:14:48.629 align:start position:0% but experienced users are boggled down 00:14:48.629 --> 00:14:50.869 align:start position:0% but experienced users are boggled down by<00:14:48.930> all<00:14:49.259> the<00:14:49.319> explanations<00:14:50.129> that<00:14:50.309> they<00:14:50.699> don't 00:14:50.869 --> 00:14:50.879 align:start position:0% by all the explanations that they don't 00:14:50.879 --> 00:14:52.549 align:start position:0% by all the explanations that they don't need<00:14:51.000> so<00:14:51.600> here's<00:14:51.959> how<00:14:52.079> we<00:14:52.139> solve<00:14:52.410> for<00:14:52.439> that 00:14:52.549 --> 00:14:52.559 align:start position:0% need so here's how we solve for that 00:14:52.559 --> 00:14:54.710 align:start position:0% need so here's how we solve for that problem<00:14:52.889> once<00:14:53.610> you<00:14:53.699> launch<00:14:53.970> the<00:14:54.240> tutorial 00:14:54.710 --> 00:14:54.720 align:start position:0% problem once you launch the tutorial 00:14:54.720 --> 00:14:57.230 align:start position:0% problem once you launch the tutorial which<00:14:54.959> is<00:14:54.990> for<00:14:55.529> everyone<00:14:55.889> then<00:14:56.790> you<00:14:56.879> get<00:14:57.089> a 00:14:57.230 --> 00:14:57.240 align:start position:0% which is for everyone then you get a 00:14:57.240 --> 00:14:59.689 align:start position:0% which is for everyone then you get a choose-your-own-adventure<00:14:57.920> so<00:14:58.920> for<00:14:59.430> the 00:14:59.689 --> 00:14:59.699 align:start position:0% choose-your-own-adventure so for the 00:14:59.699 --> 00:15:01.280 align:start position:0% choose-your-own-adventure so for the experienced<00:15:00.240> users<00:15:00.509> they<00:15:00.720> get<00:15:00.839> a<00:15:00.870> quick<00:15:01.110> guide 00:15:01.280 --> 00:15:01.290 align:start position:0% experienced users they get a quick guide 00:15:01.290 --> 00:15:03.230 align:start position:0% experienced users they get a quick guide really<00:15:02.009> really<00:15:02.220> quick<00:15:02.430> out<00:15:02.579> of<00:15:02.730> glance<00:15:02.910> you 00:15:03.230 --> 00:15:03.240 align:start position:0% really really quick out of glance you 00:15:03.240 --> 00:15:04.759 align:start position:0% really really quick out of glance you know<00:15:03.360> for<00:15:03.629> what<00:15:04.050> the<00:15:04.170> four<00:15:04.350> steps<00:15:04.620> are 00:15:04.759 --> 00:15:04.769 align:start position:0% know for what the four steps are 00:15:04.769 --> 00:15:07.669 align:start position:0% know for what the four steps are onboarding<00:15:05.279> and<00:15:05.459> then<00:15:06.120> for<00:15:06.449> the<00:15:06.629> new<00:15:07.319> users 00:15:07.669 --> 00:15:07.679 align:start position:0% onboarding and then for the new users 00:15:07.679 --> 00:15:09.379 align:start position:0% onboarding and then for the new users who<00:15:07.889> really<00:15:08.160> need<00:15:08.309> a<00:15:08.339> lot<00:15:08.550> more<00:15:08.579> support<00:15:08.819> they 00:15:09.379 --> 00:15:09.389 align:start position:0% who really need a lot more support they 00:15:09.389 --> 00:15:11.059 align:start position:0% who really need a lot more support they get<00:15:09.540> a<00:15:09.569> step-by-step<00:15:10.079> walkthrough<00:15:10.470> to<00:15:10.920> help 00:15:11.059 --> 00:15:11.069 align:start position:0% get a step-by-step walkthrough to help 00:15:11.069 --> 00:15:12.410 align:start position:0% get a step-by-step walkthrough to help them<00:15:11.189> completes<00:15:11.550> taking<00:15:11.850> interaction<00:15:12.300> for 00:15:12.410 --> 00:15:12.420 align:start position:0% them completes taking interaction for 00:15:12.420 --> 00:15:14.179 align:start position:0% them completes taking interaction for the<00:15:12.449> first<00:15:12.660> time<00:15:12.809> so<00:15:13.559> let's<00:15:13.769> take<00:15:13.889> a<00:15:13.920> look<00:15:14.040> at 00:15:14.179 --> 00:15:14.189 align:start position:0% the first time so let's take a look at 00:15:14.189 --> 00:15:17.600 align:start position:0% the first time so let's take a look at how<00:15:14.339> that<00:15:14.399> works<00:15:14.699> so<00:15:15.600> this<00:15:15.839> is<00:15:15.990> the<00:15:16.410> first<00:15:17.370> step 00:15:17.600 --> 00:15:17.610 align:start position:0% how that works so this is the first step 00:15:17.610 --> 00:15:18.860 align:start position:0% how that works so this is the first step we'll<00:15:17.759> just<00:15:17.910> enter<00:15:18.209> the<00:15:18.389> amount<00:15:18.689> that<00:15:18.749> you 00:15:18.860 --> 00:15:18.870 align:start position:0% we'll just enter the amount that you 00:15:18.870 --> 00:15:20.299 align:start position:0% we'll just enter the amount that you want<00:15:19.019> to<00:15:19.110> stick<00:15:19.290> in<00:15:19.410> the<00:15:19.499> sticking<00:15:19.829> widget<00:15:20.160> and 00:15:20.299 --> 00:15:20.309 align:start position:0% want to stick in the sticking widget and 00:15:20.309 --> 00:15:23.119 align:start position:0% want to stick in the sticking widget and also<00:15:20.730> figure<00:15:21.149> out<00:15:21.269> what<00:15:21.449> the<00:15:21.540> ROI<00:15:21.749> is<00:15:22.009> for<00:15:23.009> the 00:15:23.119 --> 00:15:23.129 align:start position:0% also figure out what the ROI is for the 00:15:23.129 --> 00:15:25.040 align:start position:0% also figure out what the ROI is for the experienced<00:15:23.850> user<00:15:24.089> it's<00:15:24.329> a<00:15:24.389> very<00:15:24.569> simple 00:15:25.040 --> 00:15:25.050 align:start position:0% experienced user it's a very simple 00:15:25.050 --> 00:15:26.989 align:start position:0% experienced user it's a very simple suggestion<00:15:25.559> and<00:15:25.800> showing<00:15:26.100> you<00:15:26.189> where<00:15:26.399> to<00:15:26.730> you 00:15:26.989 --> 00:15:26.999 align:start position:0% suggestion and showing you where to you 00:15:26.999 --> 00:15:29.840 align:start position:0% suggestion and showing you where to you know<00:15:27.089> input<00:15:27.360> that<00:15:27.449> information<00:15:27.929> for<00:15:28.769> the<00:15:29.160> new 00:15:29.840 --> 00:15:29.850 align:start position:0% know input that information for the new 00:15:29.850 --> 00:15:31.429 align:start position:0% know input that information for the new user<00:15:30.120> would<00:15:30.420> give<00:15:30.509> a<00:15:30.629> lot<00:15:30.929> more<00:15:31.139> in-depth 00:15:31.429 --> 00:15:31.439 align:start position:0% user would give a lot more in-depth 00:15:31.439 --> 00:15:33.860 align:start position:0% user would give a lot more in-depth explanation<00:15:32.160> so<00:15:32.459> this<00:15:33.059> way<00:15:33.240> they<00:15:33.480> understand 00:15:33.860 --> 00:15:33.870 align:start position:0% explanation so this way they understand 00:15:33.870 --> 00:15:34.300 align:start position:0% explanation so this way they understand what<00:15:33.990> they're<00:15:34.110> due 00:15:34.300 --> 00:15:34.310 align:start position:0% what they're due 00:15:34.310 --> 00:15:38.290 align:start position:0% what they're due okay<00:15:35.240> step<00:15:35.510> two<00:15:36.460> we<00:15:37.460> want<00:15:37.700> to<00:15:37.880> choose<00:15:38.150> an 00:15:38.290 --> 00:15:38.300 align:start position:0% okay step two we want to choose an 00:15:38.300 --> 00:15:40.780 align:start position:0% okay step two we want to choose an Orchestrator<00:15:38.840> from<00:15:38.990> the<00:15:39.050> list<00:15:39.320> so<00:15:39.980> we<00:15:40.100> explain 00:15:40.780 --> 00:15:40.790 align:start position:0% Orchestrator from the list so we explain 00:15:40.790 --> 00:15:42.430 align:start position:0% Orchestrator from the list so we explain how<00:15:41.060> to<00:15:41.120> choose<00:15:41.390> the<00:15:41.510> orchestrator<00:15:41.930> and<00:15:42.200> that 00:15:42.430 --> 00:15:42.440 align:start position:0% how to choose the orchestrator and that 00:15:42.440 --> 00:15:44.560 align:start position:0% how to choose the orchestrator and that you<00:15:42.590> can<00:15:42.710> also<00:15:42.830> click<00:15:43.250> here<00:15:43.580> to<00:15:43.970> go<00:15:44.090> into<00:15:44.120> the 00:15:44.560 --> 00:15:44.570 align:start position:0% you can also click here to go into the 00:15:44.570 --> 00:15:48.840 align:start position:0% you can also click here to go into the detail<00:15:44.900> view<00:15:44.930> and<00:15:45.350> further<00:15:46.250> evaluate<00:15:47.590> yes 00:15:48.840 --> 00:15:48.850 align:start position:0% detail view and further evaluate yes 00:15:48.850 --> 00:15:51.340 align:start position:0% detail view and further evaluate yes further<00:15:49.850> evaluate<00:15:50.450> the<00:15:50.570> orchestrator<00:15:51.020> and 00:15:51.340 --> 00:15:51.350 align:start position:0% further evaluate the orchestrator and 00:15:51.350 --> 00:15:52.900 align:start position:0% further evaluate the orchestrator and all<00:15:51.560> of<00:15:51.740> their<00:15:51.860> activities<00:15:52.310> to<00:15:52.520> see<00:15:52.790> their 00:15:52.900 --> 00:15:52.910 align:start position:0% all of their activities to see their 00:15:52.910 --> 00:15:55.210 align:start position:0% all of their activities to see their campaigns<00:15:53.300> there<00:15:53.540> because<00:15:53.750> the<00:15:53.960> identity<00:15:54.440> and 00:15:55.210 --> 00:15:55.220 align:start position:0% campaigns there because the identity and 00:15:55.220 --> 00:15:56.380 align:start position:0% campaigns there because the identity and this<00:15:55.370> just<00:15:55.580> like<00:15:55.700> really<00:15:56.000> helps<00:15:56.270> you 00:15:56.380 --> 00:15:56.390 align:start position:0% this just like really helps you 00:15:56.390 --> 00:15:59.620 align:start position:0% this just like really helps you contextualize<00:15:56.810> who<00:15:57.260> you're<00:15:57.470> evaluating<00:15:58.630> so 00:15:59.620 --> 00:15:59.630 align:start position:0% contextualize who you're evaluating so 00:15:59.630 --> 00:16:01.420 align:start position:0% contextualize who you're evaluating so the<00:15:59.720> third<00:15:59.900> step<00:16:00.140> is<00:16:00.350> a<00:16:00.680> really<00:16:01.100> important 00:16:01.420 --> 00:16:01.430 align:start position:0% the third step is a really important 00:16:01.430 --> 00:16:04.269 align:start position:0% the third step is a really important step<00:16:01.610> which<00:16:02.120> is<00:16:02.180> we<00:16:02.540> tell<00:16:02.900> them<00:16:03.050> explicitly<00:16:03.860> to 00:16:04.269 --> 00:16:04.279 align:start position:0% step which is we tell them explicitly to 00:16:04.279 --> 00:16:05.740 align:start position:0% step which is we tell them explicitly to go<00:16:04.400> ahead<00:16:04.580> and<00:16:04.670> stick<00:16:04.880> the<00:16:05.060> orchestrator<00:16:05.540> that 00:16:05.740 --> 00:16:05.750 align:start position:0% go ahead and stick the orchestrator that 00:16:05.750 --> 00:16:09.040 align:start position:0% go ahead and stick the orchestrator that they<00:16:05.900> chose<00:16:06.279> and<00:16:07.279> after<00:16:07.970> this<00:16:08.150> step<00:16:08.360> is<00:16:08.570> where 00:16:09.040 --> 00:16:09.050 align:start position:0% they chose and after this step is where 00:16:09.050 --> 00:16:11.890 align:start position:0% they chose and after this step is where all<00:16:09.260> the<00:16:09.350> fun<00:16:09.500> happens<00:16:09.529> we<00:16:10.460> get<00:16:10.640> this<00:16:10.760> huge<00:16:11.600> yay 00:16:11.890 --> 00:16:11.900 align:start position:0% all the fun happens we get this huge yay 00:16:11.900 --> 00:16:14.350 align:start position:0% all the fun happens we get this huge yay you<00:16:11.960> have<00:16:12.620> completed<00:16:13.010> staking<00:16:13.490> lots<00:16:14.270> of 00:16:14.350 --> 00:16:14.360 align:start position:0% you have completed staking lots of 00:16:14.360 --> 00:16:16.210 align:start position:0% you have completed staking lots of confetti<00:16:14.660> user<00:16:15.020> delight<00:16:15.380> so<00:16:15.740> people<00:16:16.070> love 00:16:16.210 --> 00:16:16.220 align:start position:0% confetti user delight so people love 00:16:16.220 --> 00:16:18.490 align:start position:0% confetti user delight so people love this<00:16:16.430> and<00:16:16.670> voila<00:16:17.510> we<00:16:17.750> have<00:16:17.960> now<00:16:18.080> completed 00:16:18.490 --> 00:16:18.500 align:start position:0% this and voila we have now completed 00:16:18.500 --> 00:16:21.550 align:start position:0% this and voila we have now completed staking<00:16:18.890> for<00:16:19.070> a<00:16:19.130> new<00:16:19.279> user<00:16:19.460> and<00:16:19.930> then<00:16:20.930> lastly 00:16:21.550 --> 00:16:21.560 align:start position:0% staking for a new user and then lastly 00:16:21.560 --> 00:16:23.829 align:start position:0% staking for a new user and then lastly but<00:16:22.130> not<00:16:22.190> least<00:16:22.490> we<00:16:23.150> finished<00:16:23.450> strong<00:16:23.660> by 00:16:23.829 --> 00:16:23.839 align:start position:0% but not least we finished strong by 00:16:23.839 --> 00:16:25.570 align:start position:0% but not least we finished strong by helping<00:16:24.290> people<00:16:24.500> understand<00:16:24.920> that<00:16:25.100> the 00:16:25.570 --> 00:16:25.580 align:start position:0% helping people understand that the 00:16:25.580 --> 00:16:28.660 align:start position:0% helping people understand that the staking<00:16:26.210> fund<00:16:26.480> continues<00:16:26.960> on<00:16:27.529> you<00:16:28.160> still<00:16:28.430> have 00:16:28.660 --> 00:16:28.670 align:start position:0% staking fund continues on you still have 00:16:28.670 --> 00:16:31.840 align:start position:0% staking fund continues on you still have a<00:16:28.930> management<00:16:29.930> app<00:16:30.680> basically<00:16:31.160> where<00:16:31.610> you<00:16:31.700> can 00:16:31.840 --> 00:16:31.850 align:start position:0% a management app basically where you can 00:16:31.850 --> 00:16:33.370 align:start position:0% a management app basically where you can see<00:16:32.029> you're<00:16:32.270> seeking<00:16:32.480> activities<00:16:32.960> how<00:16:33.260> did 00:16:33.370 --> 00:16:33.380 align:start position:0% see you're seeking activities how did 00:16:33.380 --> 00:16:35.320 align:start position:0% see you're seeking activities how did that<00:16:33.470> change<00:16:34.130> over<00:16:34.279> time<00:16:34.550> this<00:16:34.940> anything 00:16:35.320 --> 00:16:35.330 align:start position:0% that change over time this anything 00:16:35.330 --> 00:16:37.870 align:start position:0% that change over time this anything change<00:16:35.660> what<00:16:36.410> your<00:16:36.529> rewards<00:16:37.130> are<00:16:37.339> over<00:16:37.700> time 00:16:37.870 --> 00:16:37.880 align:start position:0% change what your rewards are over time 00:16:37.880 --> 00:16:40.600 align:start position:0% change what your rewards are over time etc<00:16:38.570> so<00:16:39.170> that<00:16:39.500> concludes<00:16:39.710> our<00:16:40.100> onboarding 00:16:40.600 --> 00:16:40.610 align:start position:0% etc so that concludes our onboarding 00:16:40.610 --> 00:16:47.189 align:start position:0% etc so that concludes our onboarding tutorial 00:16:47.189 --> 00:16:47.199 align:start position:0% 00:16:47.199 --> 00:16:49.530 align:start position:0% thank<00:16:48.199> you 00:16:49.530 --> 00:16:49.540 align:start position:0% thank you 00:16:49.540 --> 00:16:55.449 align:start position:0% thank you so<00:16:50.540> yeah<00:16:50.990> results<00:16:51.819> really<00:16:52.819> quickly<00:16:54.310> we<00:16:55.310> did 00:16:55.449 --> 00:16:55.459 align:start position:0% so yeah results really quickly we did 00:16:55.459 --> 00:16:58.059 align:start position:0% so yeah results really quickly we did find<00:16:55.670> in<00:16:55.790> our<00:16:55.910> early<00:16:56.660> usability<00:16:57.170> testing<00:16:57.500> that 00:16:58.059 --> 00:16:58.069 align:start position:0% find in our early usability testing that 00:16:58.069 --> 00:17:00.460 align:start position:0% find in our early usability testing that 8<00:16:58.519> out<00:16:58.790> of<00:16:58.819> 10<00:16:59.000> users<00:16:59.209> were<00:16:59.449> able<00:16:59.779> to<00:16:59.810> complete 00:17:00.460 --> 00:17:00.470 align:start position:0% 8 out of 10 users were able to complete 00:17:00.470 --> 00:17:03.220 align:start position:0% 8 out of 10 users were able to complete staking<00:17:00.980> autonomously<00:17:01.870> so<00:17:02.870> that<00:17:03.019> means<00:17:03.170> just 00:17:03.220 --> 00:17:03.230 align:start position:0% staking autonomously so that means just 00:17:03.230 --> 00:17:06.329 align:start position:0% staking autonomously so that means just really<00:17:03.620> without<00:17:03.860> asking<00:17:04.339> any<00:17:04.490> questions<00:17:04.880> and 00:17:06.329 --> 00:17:06.339 align:start position:0% really without asking any questions and 00:17:06.339 --> 00:17:09.579 align:start position:0% really without asking any questions and he<00:17:07.339> was<00:17:07.459> old<00:17:07.579> number<00:17:07.760> to<00:17:07.880> 60%<00:17:08.449> over<00:17:09.049> 60%<00:17:09.350> of 00:17:09.579 --> 00:17:09.589 align:start position:0% he was old number to 60% over 60% of 00:17:09.589 --> 00:17:11.799 align:start position:0% he was old number to 60% over 60% of users<00:17:10.309> were<00:17:10.400> able<00:17:10.459> to<00:17:10.699> completes<00:17:11.179> taking<00:17:11.659> in 00:17:11.799 --> 00:17:11.809 align:start position:0% users were able to completes taking in 00:17:11.809 --> 00:17:13.169 align:start position:0% users were able to completes taking in under<00:17:12.409> five<00:17:12.589> minutes 00:17:13.169 --> 00:17:13.179 align:start position:0% under five minutes 00:17:13.179 --> 00:17:15.579 align:start position:0% under five minutes and<00:17:14.179> this<00:17:14.449> particular<00:17:14.809> stay<00:17:15.289> car<00:17:15.470> actually 00:17:15.579 --> 00:17:15.589 align:start position:0% and this particular stay car actually 00:17:15.589 --> 00:17:23.829 align:start position:0% and this particular stay car actually completed<00:17:16.130> in<00:17:16.280> under<00:17:16.339> one<00:17:16.640> minute<00:17:22.750> so<00:17:23.750> you 00:17:23.829 --> 00:17:23.839 align:start position:0% completed in under one minute so you 00:17:23.839 --> 00:17:27.789 align:start position:0% completed in under one minute so you have<00:17:23.929> future<00:17:24.289> challenges<00:17:26.740> you<00:17:27.740> know 00:17:27.789 --> 00:17:27.799 align:start position:0% have future challenges you know 00:17:27.799 --> 00:17:29.230 align:start position:0% have future challenges you know obviously<00:17:28.309> onboarding<00:17:28.669> is<00:17:28.760> just<00:17:28.940> one<00:17:29.090> piece 00:17:29.230 --> 00:17:29.240 align:start position:0% obviously onboarding is just one piece 00:17:29.240 --> 00:17:32.080 align:start position:0% obviously onboarding is just one piece of<00:17:29.299> the<00:17:29.539> puzzle<00:17:30.280> how<00:17:31.280> do<00:17:31.340> you<00:17:31.520> help<00:17:31.669> retain 00:17:32.080 --> 00:17:32.090 align:start position:0% of the puzzle how do you help retain 00:17:32.090 --> 00:17:34.480 align:start position:0% of the puzzle how do you help retain users<00:17:32.539> after<00:17:32.929> they've<00:17:33.679> staked<00:17:33.980> and<00:17:34.220> and 00:17:34.480 --> 00:17:34.490 align:start position:0% users after they've staked and and 00:17:34.490 --> 00:17:36.600 align:start position:0% users after they've staked and and really<00:17:34.730> encourage<00:17:35.030> active<00:17:35.390> participation 00:17:36.600 --> 00:17:36.610 align:start position:0% really encourage active participation 00:17:36.610 --> 00:17:39.580 align:start position:0% really encourage active participation staking<00:17:37.610> is<00:17:37.700> not<00:17:37.850> a<00:17:37.880> passive<00:17:38.360> activity<00:17:38.929> you 00:17:39.580 --> 00:17:39.590 align:start position:0% staking is not a passive activity you 00:17:39.590 --> 00:17:41.470 align:start position:0% staking is not a passive activity you have<00:17:39.710> to<00:17:39.830> be<00:17:39.919> really<00:17:40.159> vigilant<00:17:40.309> and<00:17:40.730> you<00:17:41.390> know 00:17:41.470 --> 00:17:41.480 align:start position:0% have to be really vigilant and you know 00:17:41.480 --> 00:17:43.750 align:start position:0% have to be really vigilant and you know make<00:17:41.659> sure<00:17:41.690> your<00:17:41.990> delegate<00:17:42.559> is<00:17:42.740> performing<00:17:43.700> up 00:17:43.750 --> 00:17:43.760 align:start position:0% make sure your delegate is performing up 00:17:43.760 --> 00:17:45.430 align:start position:0% make sure your delegate is performing up to<00:17:43.909> par<00:17:44.090> and<00:17:44.330> playing<00:17:45.020> by<00:17:45.140> the<00:17:45.200> rules 00:17:45.430 --> 00:17:45.440 align:start position:0% to par and playing by the rules 00:17:45.440 --> 00:17:48.669 align:start position:0% to par and playing by the rules otherwise<00:17:46.299> you<00:17:47.299> like<00:17:47.510> them<00:17:47.720> risk<00:17:47.990> losing<00:17:48.380> some 00:17:48.669 --> 00:17:48.679 align:start position:0% otherwise you like them risk losing some 00:17:48.679 --> 00:17:54.010 align:start position:0% otherwise you like them risk losing some of<00:17:48.740> your<00:17:48.860> stake<00:17:52.539> designing<00:17:53.539> for<00:17:53.659> governance 00:17:54.010 --> 00:17:54.020 align:start position:0% of your stake designing for governance 00:17:54.020 --> 00:17:56.049 align:start position:0% of your stake designing for governance interactions<00:17:54.530> so<00:17:54.710> in<00:17:54.919> life<00:17:55.400> here<00:17:55.669> and<00:17:55.760> in<00:17:55.880> most 00:17:56.049 --> 00:17:56.059 align:start position:0% interactions so in life here and in most 00:17:56.059 --> 00:17:58.270 align:start position:0% interactions so in life here and in most pre<00:17:56.630> Pacific<00:17:56.929> protocols<00:17:57.350> your<00:17:57.559> stake<00:17:57.980> also 00:17:58.270 --> 00:17:58.280 align:start position:0% pre Pacific protocols your stake also 00:17:58.280 --> 00:18:01.120 align:start position:0% pre Pacific protocols your stake also represents<00:17:58.669> your<00:17:58.760> voting<00:17:59.120> power<00:17:59.809> so<00:18:00.260> you<00:18:00.500> know 00:18:01.120 --> 00:18:01.130 align:start position:0% represents your voting power so you know 00:18:01.130 --> 00:18:03.279 align:start position:0% represents your voting power so you know for<00:18:01.340> future<00:18:01.460> governance<00:18:02.179> proposals<00:18:02.720> how<00:18:03.110> can 00:18:03.279 --> 00:18:03.289 align:start position:0% for future governance proposals how can 00:18:03.289 --> 00:18:05.260 align:start position:0% for future governance proposals how can we<00:18:03.409> design<00:18:03.559> to<00:18:03.890> encourage<00:18:04.340> this<00:18:05.000> type<00:18:05.059> of 00:18:05.260 --> 00:18:05.270 align:start position:0% we design to encourage this type of 00:18:05.270 --> 00:18:08.399 align:start position:0% we design to encourage this type of participation<00:18:05.539> in<00:18:06.169> the<00:18:06.230> network<00:18:06.530> and<00:18:07.390> finally 00:18:08.399 --> 00:18:08.409 align:start position:0% participation in the network and finally 00:18:08.409 --> 00:18:10.240 align:start position:0% participation in the network and finally you<00:18:09.409> know<00:18:09.500> in<00:18:09.559> a<00:18:09.620> world<00:18:09.770> where<00:18:10.070> there's 00:18:10.240 --> 00:18:10.250 align:start position:0% you know in a world where there's 00:18:10.250 --> 00:18:11.950 align:start position:0% you know in a world where there's hundreds<00:18:10.700> of<00:18:10.820> staking<00:18:11.179> protocols<00:18:11.690> it's<00:18:11.840> going 00:18:11.950 --> 00:18:11.960 align:start position:0% hundreds of staking protocols it's going 00:18:11.960 --> 00:18:14.230 align:start position:0% hundreds of staking protocols it's going to<00:18:12.020> be<00:18:12.140> increasingly<00:18:12.650> important<00:18:13.130> to<00:18:13.280> make<00:18:14.150> it 00:18:14.230 --> 00:18:14.240 align:start position:0% to be increasingly important to make it 00:18:14.240 --> 00:18:16.029 align:start position:0% to be increasingly important to make it as<00:18:14.360> easy<00:18:14.630> as<00:18:14.809> possible<00:18:14.929> for<00:18:15.470> users<00:18:15.559> to<00:18:15.830> really 00:18:16.029 --> 00:18:16.039 align:start position:0% as easy as possible for users to really 00:18:16.039 --> 00:18:18.640 align:start position:0% as easy as possible for users to really jump<00:18:16.460> from<00:18:16.700> one<00:18:17.240> staking<00:18:17.750> app<00:18:17.870> to<00:18:18.049> another<00:18:18.350> and 00:18:18.640 --> 00:18:18.650 align:start position:0% jump from one staking app to another and 00:18:18.650 --> 00:18:21.430 align:start position:0% jump from one staking app to another and still<00:18:19.130> feel<00:18:19.429> at<00:18:19.610> home<00:18:19.640> if<00:18:20.000> you<00:18:20.200> have<00:18:21.200> it<00:18:21.320> feel 00:18:21.430 --> 00:18:21.440 align:start position:0% still feel at home if you have it feel 00:18:21.440 --> 00:18:22.510 align:start position:0% still feel at home if you have it feel familiar<00:18:21.650> so<00:18:22.039> this<00:18:22.159> is<00:18:22.250> gonna<00:18:22.340> require 00:18:22.510 --> 00:18:22.520 align:start position:0% familiar so this is gonna require 00:18:22.520 --> 00:18:24.460 align:start position:0% familiar so this is gonna require reaching<00:18:23.120> consensus<00:18:23.630> with<00:18:23.780> other<00:18:23.990> staking 00:18:24.460 --> 00:18:24.470 align:start position:0% reaching consensus with other staking 00:18:24.470 --> 00:18:26.380 align:start position:0% reaching consensus with other staking protocols<00:18:24.890> and<00:18:24.980> other<00:18:25.159> projects<00:18:25.640> and<00:18:26.150> really 00:18:26.380 --> 00:18:26.390 align:start position:0% protocols and other projects and really 00:18:26.390 --> 00:18:28.720 align:start position:0% protocols and other projects and really coalesced<00:18:26.840> around<00:18:27.010> proven<00:18:28.010> design<00:18:28.280> patterns 00:18:28.720 --> 00:18:28.730 align:start position:0% coalesced around proven design patterns 00:18:28.730 --> 00:18:30.640 align:start position:0% coalesced around proven design patterns and<00:18:28.909> a<00:18:29.240> shared<00:18:29.510> language<00:18:29.690> and<00:18:30.049> we're<00:18:30.440> really 00:18:30.640 --> 00:18:30.650 align:start position:0% and a shared language and we're really 00:18:30.650 --> 00:18:33.039 align:start position:0% and a shared language and we're really looking<00:18:30.860> forward<00:18:31.370> to<00:18:31.490> to<00:18:32.480> working<00:18:32.780> with<00:18:32.900> you 00:18:33.039 --> 00:18:33.049 align:start position:0% looking forward to to working with you 00:18:33.049 --> 00:18:34.659 align:start position:0% looking forward to to working with you guys<00:18:33.110> and<00:18:33.559> and<00:18:33.830> other<00:18:33.950> teams<00:18:34.220> in<00:18:34.370> the<00:18:34.400> space 00:18:34.659 --> 00:18:34.669 align:start position:0% guys and and other teams in the space 00:18:34.669 --> 00:18:36.850 align:start position:0% guys and and other teams in the space and<00:18:34.909> to<00:18:35.210> make<00:18:35.360> this<00:18:35.510> a<00:18:35.750> reality<00:18:36.320> and<00:18:36.710> help 00:18:36.850 --> 00:18:36.860 align:start position:0% and to make this a reality and help 00:18:36.860 --> 00:18:38.590 align:start position:0% and to make this a reality and help onboard<00:18:37.250> you<00:18:37.760> know<00:18:37.850> the<00:18:38.120> first<00:18:38.330> million 00:18:38.590 --> 00:18:38.600 align:start position:0% onboard you know the first million 00:18:38.600 --> 00:18:44.500 align:start position:0% onboard you know the first million staking<00:18:39.200> users<00:18:42.730> huge<00:18:43.730> thanks<00:18:44.120> to<00:18:44.150> the<00:18:44.330> live 00:18:44.500 --> 00:18:44.510 align:start position:0% staking users huge thanks to the live 00:18:44.510 --> 00:18:46.510 align:start position:0% staking users huge thanks to the live pure<00:18:44.690> team<00:18:44.929> and<00:18:45.200> community<00:18:45.409> without<00:18:46.340> whom 00:18:46.510 --> 00:18:46.520 align:start position:0% pure team and community without whom 00:18:46.520 --> 00:18:47.770 align:start position:0% pure team and community without whom this<00:18:46.700> talk<00:18:46.909> would<00:18:47.090> not<00:18:47.270> have<00:18:47.480> been<00:18:47.600> possible 00:18:47.770 --> 00:18:47.780 align:start position:0% this talk would not have been possible 00:18:47.780 --> 00:18:51.310 align:start position:0% this talk would not have been possible and<00:18:48.289> also<00:18:49.159> a<00:18:49.190> huge<00:18:49.730> huge<00:18:50.030> thanks<00:18:50.390> to<00:18:50.450> you<00:18:51.080> the 00:18:51.310 --> 00:18:51.320 align:start position:0% and also a huge huge thanks to you the 00:18:51.320 --> 00:18:53.140 align:start position:0% and also a huge huge thanks to you the audience<00:18:51.500> members<00:18:52.070> and<00:18:52.309> as<00:18:52.700> Adam<00:18:53.120> mentioned 00:18:53.140 --> 00:18:53.150 align:start position:0% audience members and as Adam mentioned 00:18:53.150 --> 00:18:55.210 align:start position:0% audience members and as Adam mentioned we<00:18:53.809> really<00:18:54.110> want<00:18:54.320> to<00:18:54.470> collaborate<00:18:54.860> with<00:18:55.039> you 00:18:55.210 --> 00:18:55.220 align:start position:0% we really want to collaborate with you 00:18:55.220 --> 00:18:57.260 align:start position:0% we really want to collaborate with you to<00:18:55.580> make<00:18:55.700> staking<00:18:56.120> better<00:18:56.330> for<00:18:56.570> everyone 00:18:57.260 --> 00:18:57.270 align:start position:0% to make staking better for everyone 00:18:57.270 --> 00:18:59.810 align:start position:0% to make staking better for everyone so<00:18:57.480> if<00:18:58.080> you<00:18:58.290> want<00:18:58.470> to<00:18:58.560> take<00:18:58.710> our<00:18:58.860> challenge<00:18:59.370> we 00:18:59.810 --> 00:18:59.820 align:start position:0% so if you want to take our challenge we 00:18:59.820 --> 00:19:01.850 align:start position:0% so if you want to take our challenge we have<00:19:00.060> this<00:19:00.690> challenge<00:19:01.050> out<00:19:01.170> for<00:19:01.380> everyone<00:19:01.650> at 00:19:01.850 --> 00:19:01.860 align:start position:0% have this challenge out for everyone at 00:19:01.860 --> 00:19:02.240 align:start position:0% have this challenge out for everyone at Def<00:19:02.040> Con 00:19:02.240 --> 00:19:02.250 align:start position:0% Def Con 00:19:02.250 --> 00:19:04.220 align:start position:0% Def Con to<00:19:02.700> stick<00:19:03.000> like<00:19:03.210> your<00:19:03.360> token<00:19:03.660> in<00:19:03.750> under<00:19:04.020> one 00:19:04.220 --> 00:19:04.230 align:start position:0% to stick like your token in under one 00:19:04.230 --> 00:19:05.990 align:start position:0% to stick like your token in under one minute<00:19:04.260> so<00:19:04.740> if<00:19:04.980> you're<00:19:05.370> curious<00:19:05.520> about<00:19:05.760> that 00:19:05.990 --> 00:19:06.000 align:start position:0% minute so if you're curious about that 00:19:06.000 --> 00:19:08.540 align:start position:0% minute so if you're curious about that come<00:19:06.300> find<00:19:06.540> us<00:19:06.660> afterwards<00:19:07.250> thank<00:19:08.250> you<00:19:08.370> so 00:19:08.540 --> 00:19:08.550 align:start position:0% come find us afterwards thank you so 00:19:08.550 --> 00:19:10.940 align:start position:0% come find us afterwards thank you so much<00:19:08.700> come<00:19:09.060> find<00:19:09.300> us<00:19:09.450> on<00:19:09.720> Twitter<00:19:10.050> and<00:19:10.320> yes 00:19:10.940 --> 00:19:10.950 align:start position:0% much come find us on Twitter and yes 00:19:10.950 --> 00:19:21.690 align:start position:0% much come find us on Twitter and yes hurrah 00:19:21.690 --> 00:19:21.700 align:start position:0% 00:19:21.700 --> 00:19:23.760 align:start position:0% you