WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:09.669 align:start position:0% [Music] 00:00:09.669 --> 00:00:09.679 align:start position:0% [Music] 00:00:09.679 --> 00:00:11.669 align:start position:0% [Music] hello<00:00:09.920> everyone<00:00:10.599> my<00:00:10.759> name<00:00:10.880> is<00:00:11.000> Gregory<00:00:11.320> Roco 00:00:11.669 --> 00:00:11.679 align:start position:0% hello everyone my name is Gregory Roco 00:00:11.679 --> 00:00:13.990 align:start position:0% hello everyone my name is Gregory Roco as<00:00:11.799> mentioned<00:00:12.519> and<00:00:12.880> um<00:00:13.320> I<00:00:13.440> tried<00:00:13.679> to<00:00:13.759> figure 00:00:13.990 --> 00:00:14.000 align:start position:0% as mentioned and um I tried to figure 00:00:14.000 --> 00:00:15.390 align:start position:0% as mentioned and um I tried to figure out<00:00:14.280> what<00:00:14.400> I<00:00:14.480> could<00:00:14.639> do<00:00:14.759> in<00:00:14.839> a<00:00:14.920> short<00:00:15.120> amount<00:00:15.280> of 00:00:15.390 --> 00:00:15.400 align:start position:0% out what I could do in a short amount of 00:00:15.400 --> 00:00:17.310 align:start position:0% out what I could do in a short amount of time<00:00:15.519> for<00:00:15.639> a<00:00:15.719> lightning<00:00:16.080> talk<00:00:16.840> I<00:00:16.960> felt<00:00:17.119> like 00:00:17.310 --> 00:00:17.320 align:start position:0% time for a lightning talk I felt like 00:00:17.320 --> 00:00:18.550 align:start position:0% time for a lightning talk I felt like you'd<00:00:17.560> have<00:00:17.640> a<00:00:17.720> lot<00:00:17.800> of<00:00:17.920> Highly<00:00:18.199> specific 00:00:18.550 --> 00:00:18.560 align:start position:0% you'd have a lot of Highly specific 00:00:18.560 --> 00:00:20.230 align:start position:0% you'd have a lot of Highly specific technical<00:00:19.000> talks<00:00:19.279> so<00:00:19.400> I<00:00:19.480> figured<00:00:19.800> I'd<00:00:20.000> give 00:00:20.230 --> 00:00:20.240 align:start position:0% technical talks so I figured I'd give 00:00:20.240 --> 00:00:21.990 align:start position:0% technical talks so I figured I'd give product<00:00:20.720> a<00:00:20.880> go<00:00:21.080> when<00:00:21.160> it<00:00:21.279> comes<00:00:21.439> to<00:00:21.640> giving<00:00:21.880> one 00:00:21.990 --> 00:00:22.000 align:start position:0% product a go when it comes to giving one 00:00:22.000 --> 00:00:24.150 align:start position:0% product a go when it comes to giving one of<00:00:22.199> these<00:00:22.880> so<00:00:23.160> the<00:00:23.279> title<00:00:23.560> itself<00:00:23.800> is<00:00:23.920> product 00:00:24.150 --> 00:00:24.160 align:start position:0% of these so the title itself is product 00:00:24.160 --> 00:00:25.630 align:start position:0% of these so the title itself is product Le<00:00:24.359> blockchain<00:00:24.720> development<00:00:25.240> so<00:00:25.359> it's<00:00:25.519> kind 00:00:25.630 --> 00:00:25.640 align:start position:0% Le blockchain development so it's kind 00:00:25.640 --> 00:00:27.550 align:start position:0% Le blockchain development so it's kind of<00:00:25.800> covering<00:00:26.199> the<00:00:26.359> whole<00:00:26.599> lineage<00:00:27.199> of<00:00:27.320> going 00:00:27.550 --> 00:00:27.560 align:start position:0% of covering the whole lineage of going 00:00:27.560 --> 00:00:30.109 align:start position:0% of covering the whole lineage of going from<00:00:27.720> product<00:00:28.000> Le<00:00:28.199> growth<00:00:28.439> for<00:00:28.640> startups<00:00:29.519> to 00:00:30.109 --> 00:00:30.119 align:start position:0% from product Le growth for startups to 00:00:30.119 --> 00:00:31.630 align:start position:0% from product Le growth for startups to uh<00:00:30.279> product<00:00:30.560> Le<00:00:30.759> protocol<00:00:31.119> development<00:00:31.519> which 00:00:31.630 --> 00:00:31.640 align:start position:0% uh product Le protocol development which 00:00:31.640 --> 00:00:33.549 align:start position:0% uh product Le protocol development which was<00:00:32.079> originally<00:00:32.480> coined<00:00:32.800> by<00:00:32.920> Dan<00:00:33.079> Romero<00:00:33.480> a 00:00:33.549 --> 00:00:33.559 align:start position:0% was originally coined by Dan Romero a 00:00:33.559 --> 00:00:34.790 align:start position:0% was originally coined by Dan Romero a couple<00:00:33.800> years<00:00:34.000> ago<00:00:34.239> and<00:00:34.399> thinking<00:00:34.600> about 00:00:34.790 --> 00:00:34.800 align:start position:0% couple years ago and thinking about 00:00:34.800 --> 00:00:36.790 align:start position:0% couple years ago and thinking about forecaster<00:00:35.719> and<00:00:35.840> then<00:00:36.000> finally<00:00:36.320> product<00:00:36.600> Le 00:00:36.790 --> 00:00:36.800 align:start position:0% forecaster and then finally product Le 00:00:36.800 --> 00:00:38.190 align:start position:0% forecaster and then finally product Le blockchain<00:00:37.120> development<00:00:37.480> which<00:00:37.600> is<00:00:37.719> this<00:00:37.960> new 00:00:38.190 --> 00:00:38.200 align:start position:0% blockchain development which is this new 00:00:38.200 --> 00:00:40.750 align:start position:0% blockchain development which is this new era<00:00:38.680> of<00:00:38.879> everyone<00:00:39.800> uh<00:00:39.960> seemingly<00:00:40.399> wanting 00:00:40.750 --> 00:00:40.760 align:start position:0% era of everyone uh seemingly wanting 00:00:40.760 --> 00:00:42.869 align:start position:0% era of everyone uh seemingly wanting their<00:00:40.920> own<00:00:41.200> block<00:00:41.520> space<00:00:41.800> for<00:00:42.120> some<00:00:42.520> strange 00:00:42.869 --> 00:00:42.879 align:start position:0% their own block space for some strange 00:00:42.879 --> 00:00:44.790 align:start position:0% their own block space for some strange reason<00:00:43.239> but<00:00:43.360> we'll<00:00:43.719> we'll<00:00:43.879> figure<00:00:44.120> it<00:00:44.239> out 00:00:44.790 --> 00:00:44.800 align:start position:0% reason but we'll we'll figure it out 00:00:44.800 --> 00:00:47.270 align:start position:0% reason but we'll we'll figure it out eventually<00:00:45.800> um<00:00:46.239> but<00:00:46.480> the<00:00:46.640> subtitle<00:00:47.079> here<00:00:47.160> is 00:00:47.270 --> 00:00:47.280 align:start position:0% eventually um but the subtitle here is 00:00:47.280 --> 00:00:48.510 align:start position:0% eventually um but the subtitle here is why<00:00:47.399> you're<00:00:47.520> wrong<00:00:47.680> and<00:00:47.800> the<00:00:47.879> market<00:00:48.120> is<00:00:48.320> Right 00:00:48.510 --> 00:00:48.520 align:start position:0% why you're wrong and the market is Right 00:00:48.520 --> 00:00:50.110 align:start position:0% why you're wrong and the market is Right deals<00:00:48.840> specifically<00:00:49.320> with<00:00:49.480> making<00:00:49.760> sure<00:00:50.000> that 00:00:50.110 --> 00:00:50.120 align:start position:0% deals specifically with making sure that 00:00:50.120 --> 00:00:52.430 align:start position:0% deals specifically with making sure that whenever<00:00:50.680> you<00:00:50.879> think<00:00:51.120> about<00:00:52.000> uh<00:00:52.160> product 00:00:52.430 --> 00:00:52.440 align:start position:0% whenever you think about uh product 00:00:52.440 --> 00:00:53.709 align:start position:0% whenever you think about uh product development<00:00:52.800> protocol<00:00:53.160> development<00:00:53.480> or<00:00:53.559> even 00:00:53.709 --> 00:00:53.719 align:start position:0% development protocol development or even 00:00:53.719 --> 00:00:55.349 align:start position:0% development protocol development or even blockchain<00:00:54.199> development<00:00:54.960> that<00:00:55.079> you<00:00:55.160> are 00:00:55.349 --> 00:00:55.359 align:start position:0% blockchain development that you are 00:00:55.359 --> 00:00:57.470 align:start position:0% blockchain development that you are serving<00:00:55.800> some<00:00:56.039> customer<00:00:56.399> need<00:00:56.800> and<00:00:57.000> not<00:00:57.320> your 00:00:57.470 --> 00:00:57.480 align:start position:0% serving some customer need and not your 00:00:57.480 --> 00:00:59.509 align:start position:0% serving some customer need and not your own<00:00:57.960> interests<00:00:58.719> to<00:00:58.879> a<00:00:58.960> certain<00:00:59.199> degree<00:00:59.440> you 00:00:59.509 --> 00:00:59.519 align:start position:0% own interests to a certain degree you 00:00:59.519 --> 00:01:00.830 align:start position:0% own interests to a certain degree you have<00:00:59.600> to<00:00:59.640> be<00:01:00.160> in<00:01:00.239> what<00:01:00.320> you're<00:01:00.399> doing<00:01:00.640> but<00:01:00.719> at 00:01:00.830 --> 00:01:00.840 align:start position:0% have to be in what you're doing but at 00:01:00.840 --> 00:01:02.910 align:start position:0% have to be in what you're doing but at the<00:01:00.920> same<00:01:01.120> time<00:01:01.239> you<00:01:01.320> have<00:01:01.399> to<00:01:01.480> serve<00:01:01.719> a<00:01:01.920> market 00:01:02.910 --> 00:01:02.920 align:start position:0% the same time you have to serve a market 00:01:02.920 --> 00:01:05.310 align:start position:0% the same time you have to serve a market um<00:01:03.760> and<00:01:03.920> a<00:01:04.040> disclaimer<00:01:04.519> to<00:01:04.720> this<00:01:04.920> talk<00:01:05.080> is<00:01:05.199> that 00:01:05.310 --> 00:01:05.320 align:start position:0% um and a disclaimer to this talk is that 00:01:05.320 --> 00:01:06.630 align:start position:0% um and a disclaimer to this talk is that I<00:01:05.400> was<00:01:05.519> a<00:01:05.600> founder<00:01:05.880> and<00:01:05.960> I<00:01:06.040> was<00:01:06.200> wrong<00:01:06.400> plenty 00:01:06.630 --> 00:01:06.640 align:start position:0% I was a founder and I was wrong plenty 00:01:06.640 --> 00:01:08.630 align:start position:0% I was a founder and I was wrong plenty of<00:01:06.799> times<00:01:07.439> I<00:01:07.640> specifically<00:01:08.080> started<00:01:08.479> my 00:01:08.630 --> 00:01:08.640 align:start position:0% of times I specifically started my 00:01:08.640 --> 00:01:11.350 align:start position:0% of times I specifically started my career<00:01:09.119> in<00:01:09.640> uh<00:01:10.080> this<00:01:10.280> space<00:01:10.479> in<00:01:10.680> decentralized 00:01:11.350 --> 00:01:11.360 align:start position:0% career in uh this space in decentralized 00:01:11.360 --> 00:01:13.310 align:start position:0% career in uh this space in decentralized identity<00:01:11.920> which<00:01:12.159> namely<00:01:12.479> is<00:01:12.600> a<00:01:12.720> hard<00:01:12.960> space<00:01:13.200> to 00:01:13.310 --> 00:01:13.320 align:start position:0% identity which namely is a hard space to 00:01:13.320 --> 00:01:14.429 align:start position:0% identity which namely is a hard space to crack<00:01:13.600> when<00:01:13.720> it<00:01:13.799> comes<00:01:14.000> to<00:01:14.159> product 00:01:14.429 --> 00:01:14.439 align:start position:0% crack when it comes to product 00:01:14.439 --> 00:01:16.510 align:start position:0% crack when it comes to product development<00:01:15.280> and<00:01:15.520> probably<00:01:15.960> there<00:01:16.080> are<00:01:16.240> just 00:01:16.510 --> 00:01:16.520 align:start position:0% development and probably there are just 00:01:16.520 --> 00:01:19.030 align:start position:0% development and probably there are just very<00:01:16.920> few<00:01:17.920> uh<00:01:18.080> companies<00:01:18.400> and<00:01:18.560> protocols<00:01:18.960> that 00:01:19.030 --> 00:01:19.040 align:start position:0% very few uh companies and protocols that 00:01:19.040 --> 00:01:20.630 align:start position:0% very few uh companies and protocols that have<00:01:19.159> done<00:01:19.280> it<00:01:19.400> maybe<00:01:19.560> ens<00:01:19.960> is<00:01:20.079> the<00:01:20.200> closest<00:01:20.479> to 00:01:20.630 --> 00:01:20.640 align:start position:0% have done it maybe ens is the closest to 00:01:20.640 --> 00:01:21.990 align:start position:0% have done it maybe ens is the closest to product<00:01:20.920> Market<00:01:21.200> Market<00:01:21.439> fit<00:01:21.640> when<00:01:21.759> it<00:01:21.840> comes 00:01:21.990 --> 00:01:22.000 align:start position:0% product Market Market fit when it comes 00:01:22.000 --> 00:01:24.030 align:start position:0% product Market Market fit when it comes to<00:01:22.200> Identity<00:01:23.200> um<00:01:23.320> but<00:01:23.400> user<00:01:23.680> Control 00:01:24.030 --> 00:01:24.040 align:start position:0% to Identity um but user Control 00:01:24.040 --> 00:01:26.069 align:start position:0% to Identity um but user Control credentials<00:01:24.479> generally<00:01:24.799> were<00:01:25.000> quite<00:01:25.200> tough 00:01:26.069 --> 00:01:26.079 align:start position:0% credentials generally were quite tough 00:01:26.079 --> 00:01:28.469 align:start position:0% credentials generally were quite tough um<00:01:26.280> going<00:01:26.600> back<00:01:26.759> into<00:01:27.400> the<00:01:27.720> core<00:01:28.000> basics<00:01:28.320> of 00:01:28.469 --> 00:01:28.479 align:start position:0% um going back into the core basics of 00:01:28.479 --> 00:01:30.149 align:start position:0% um going back into the core basics of product<00:01:28.720> development<00:01:29.280> one<00:01:29.400> of<00:01:29.520> the<00:01:29.920> kind<00:01:30.040> of 00:01:30.149 --> 00:01:30.159 align:start position:0% product development one of the kind of 00:01:30.159 --> 00:01:32.950 align:start position:0% product development one of the kind of core<00:01:30.400> pillars<00:01:30.920> there<00:01:31.280> is<00:01:31.759> product<00:01:32.079> L<00:01:32.280> growth 00:01:32.950 --> 00:01:32.960 align:start position:0% core pillars there is product L growth 00:01:32.960 --> 00:01:34.590 align:start position:0% core pillars there is product L growth namely<00:01:33.320> that's<00:01:33.520> whenever<00:01:33.799> you<00:01:34.000> build<00:01:34.360> a 00:01:34.590 --> 00:01:34.600 align:start position:0% namely that's whenever you build a 00:01:34.600 --> 00:01:36.310 align:start position:0% namely that's whenever you build a product<00:01:34.960> you<00:01:35.240> specifically<00:01:35.799> have<00:01:35.920> to<00:01:36.119> make 00:01:36.310 --> 00:01:36.320 align:start position:0% product you specifically have to make 00:01:36.320 --> 00:01:38.510 align:start position:0% product you specifically have to make sure<00:01:37.040> that<00:01:37.240> customer<00:01:37.600> needs<00:01:37.960> and<00:01:38.119> customer 00:01:38.510 --> 00:01:38.520 align:start position:0% sure that customer needs and customer 00:01:38.520 --> 00:01:40.190 align:start position:0% sure that customer needs and customer experience<00:01:38.960> are<00:01:39.079> at<00:01:39.200> the<00:01:39.320> Forefront 00:01:40.190 --> 00:01:40.200 align:start position:0% experience are at the Forefront 00:01:40.200 --> 00:01:42.069 align:start position:0% experience are at the Forefront dictating<00:01:40.920> everything<00:01:41.280> that<00:01:41.399> you<00:01:41.520> do<00:01:41.880> and 00:01:42.069 --> 00:01:42.079 align:start position:0% dictating everything that you do and 00:01:42.079 --> 00:01:44.469 align:start position:0% dictating everything that you do and become<00:01:42.600> the<00:01:43.159> full<00:01:43.520> kind<00:01:43.720> of<00:01:43.880> motion<00:01:44.159> for<00:01:44.360> what 00:01:44.469 --> 00:01:44.479 align:start position:0% become the full kind of motion for what 00:01:44.479 --> 00:01:46.910 align:start position:0% become the full kind of motion for what you<00:01:44.640> do<00:01:45.159> so<00:01:45.360> feedback<00:01:45.880> comes<00:01:46.079> in<00:01:46.560> you<00:01:46.759> then 00:01:46.910 --> 00:01:46.920 align:start position:0% you do so feedback comes in you then 00:01:46.920 --> 00:01:48.270 align:start position:0% you do so feedback comes in you then take<00:01:47.119> that<00:01:47.280> feedback<00:01:47.759> as<00:01:47.880> a<00:01:48.000> product 00:01:48.270 --> 00:01:48.280 align:start position:0% take that feedback as a product 00:01:48.280 --> 00:01:50.149 align:start position:0% take that feedback as a product developer<00:01:49.000> and<00:01:49.119> that's<00:01:49.280> what<00:01:49.439> influences 00:01:50.149 --> 00:01:50.159 align:start position:0% developer and that's what influences 00:01:50.159 --> 00:01:52.590 align:start position:0% developer and that's what influences engineering<00:01:51.079> design<00:01:51.840> messaging<00:01:52.399> and 00:01:52.590 --> 00:01:52.600 align:start position:0% engineering design messaging and 00:01:52.600 --> 00:01:54.270 align:start position:0% engineering design messaging and everything<00:01:52.840> in<00:01:53.000> between<00:01:53.640> it<00:01:53.880> shouldn't<00:01:54.079> come 00:01:54.270 --> 00:01:54.280 align:start position:0% everything in between it shouldn't come 00:01:54.280 --> 00:01:56.270 align:start position:0% everything in between it shouldn't come from<00:01:54.600> oh<00:01:55.200> just<00:01:55.399> one<00:01:55.520> more<00:01:55.719> feature<00:01:56.039> and<00:01:56.159> all 00:01:56.270 --> 00:01:56.280 align:start position:0% from oh just one more feature and all 00:01:56.280 --> 00:01:57.950 align:start position:0% from oh just one more feature and all these<00:01:56.439> users<00:01:56.719> are<00:01:56.840> going<00:01:56.920> to<00:01:57.079> use<00:01:57.240> it<00:01:57.560> it<00:01:57.719> never 00:01:57.950 --> 00:01:57.960 align:start position:0% these users are going to use it it never 00:01:57.960 --> 00:02:00.069 align:start position:0% these users are going to use it it never works<00:01:58.200> out<00:01:58.439> that<00:01:58.600> way<00:01:59.039> it's<00:01:59.280> specifically<00:01:59.960> the 00:02:00.069 --> 00:02:00.079 align:start position:0% works out that way it's specifically the 00:02:00.079 --> 00:02:01.350 align:start position:0% works out that way it's specifically the case<00:02:00.240> of<00:02:00.320> someone<00:02:00.600> requesting<00:02:00.960> a<00:02:01.079> feature 00:02:01.350 --> 00:02:01.360 align:start position:0% case of someone requesting a feature 00:02:01.360 --> 00:02:02.870 align:start position:0% case of someone requesting a feature from<00:02:01.520> what<00:02:01.600> you<00:02:01.719> build<00:02:02.240> you<00:02:02.399> bring<00:02:02.640> something 00:02:02.870 --> 00:02:02.880 align:start position:0% from what you build you bring something 00:02:02.880 --> 00:02:04.310 align:start position:0% from what you build you bring something to<00:02:03.079> Market<00:02:03.399> you<00:02:03.520> get<00:02:03.640> your<00:02:03.759> initial<00:02:04.039> set<00:02:04.200> of 00:02:04.310 --> 00:02:04.320 align:start position:0% to Market you get your initial set of 00:02:04.320 --> 00:02:05.990 align:start position:0% to Market you get your initial set of users<00:02:04.640> and<00:02:04.759> you're<00:02:04.960> constantly<00:02:05.439> using<00:02:05.799> that 00:02:05.990 --> 00:02:06.000 align:start position:0% users and you're constantly using that 00:02:06.000 --> 00:02:07.990 align:start position:0% users and you're constantly using that messaging<00:02:06.759> to<00:02:07.000> inform<00:02:07.479> what<00:02:07.600> you're<00:02:07.759> going<00:02:07.880> to 00:02:07.990 --> 00:02:08.000 align:start position:0% messaging to inform what you're going to 00:02:08.000 --> 00:02:09.389 align:start position:0% messaging to inform what you're going to do<00:02:08.160> and<00:02:08.360> all<00:02:08.479> the<00:02:08.640> decisions<00:02:09.039> you're<00:02:09.160> going<00:02:09.280> to 00:02:09.389 --> 00:02:09.399 align:start position:0% do and all the decisions you're going to 00:02:09.399 --> 00:02:10.589 align:start position:0% do and all the decisions you're going to make<00:02:09.560> when<00:02:09.800> thinking<00:02:10.080> about<00:02:10.319> product 00:02:10.589 --> 00:02:10.599 align:start position:0% make when thinking about product 00:02:10.599 --> 00:02:12.510 align:start position:0% make when thinking about product development<00:02:11.560> this<00:02:11.680> was<00:02:11.800> the<00:02:11.920> framework<00:02:12.280> for<00:02:12.400> a 00:02:12.510 --> 00:02:12.520 align:start position:0% development this was the framework for a 00:02:12.520 --> 00:02:14.229 align:start position:0% development this was the framework for a long<00:02:12.760> time<00:02:12.920> when<00:02:13.040> it<00:02:13.120> came<00:02:13.280> to<00:02:13.400> startups<00:02:14.080> it's 00:02:14.229 --> 00:02:14.239 align:start position:0% long time when it came to startups it's 00:02:14.239 --> 00:02:15.589 align:start position:0% long time when it came to startups it's what<00:02:14.400> I<00:02:14.480> was<00:02:14.640> indoctrinated<00:02:15.280> with<00:02:15.400> when<00:02:15.519> I 00:02:15.589 --> 00:02:15.599 align:start position:0% what I was indoctrinated with when I 00:02:15.599 --> 00:02:17.990 align:start position:0% what I was indoctrinated with when I went<00:02:15.720> through<00:02:16.160> Y<00:02:16.360> combinator<00:02:17.239> and<00:02:17.400> then<00:02:17.760> later 00:02:17.990 --> 00:02:18.000 align:start position:0% went through Y combinator and then later 00:02:18.000 --> 00:02:20.070 align:start position:0% went through Y combinator and then later in<00:02:18.120> the<00:02:18.280> space<00:02:19.280> since<00:02:19.480> we're<00:02:19.680> all<00:02:19.840> kind<00:02:19.959> of 00:02:20.070 --> 00:02:20.080 align:start position:0% in the space since we're all kind of 00:02:20.080 --> 00:02:22.070 align:start position:0% in the space since we're all kind of building<00:02:20.519> these<00:02:20.680> emerging<00:02:21.120> protocols<00:02:21.720> and 00:02:22.070 --> 00:02:22.080 align:start position:0% building these emerging protocols and 00:02:22.080 --> 00:02:24.070 align:start position:0% building these emerging protocols and blockchains<00:02:23.080> uh<00:02:23.200> the<00:02:23.319> framework<00:02:23.720> had<00:02:23.879> to<00:02:23.959> be 00:02:24.070 --> 00:02:24.080 align:start position:0% blockchains uh the framework had to be 00:02:24.080 --> 00:02:25.670 align:start position:0% blockchains uh the framework had to be changed<00:02:24.480> a<00:02:24.560> little<00:02:24.760> bit<00:02:25.200> because<00:02:25.360> it<00:02:25.480> was<00:02:25.599> a 00:02:25.670 --> 00:02:25.680 align:start position:0% changed a little bit because it was a 00:02:25.680 --> 00:02:27.350 align:start position:0% changed a little bit because it was a bit<00:02:25.800> of<00:02:26.000> like<00:02:26.080> a<00:02:26.200> blue<00:02:26.440> ocean<00:02:26.840> space<00:02:27.160> when<00:02:27.239> it 00:02:27.350 --> 00:02:27.360 align:start position:0% bit of like a blue ocean space when it 00:02:27.360 --> 00:02:30.030 align:start position:0% bit of like a blue ocean space when it came<00:02:27.519> to<00:02:27.680> protocol<00:02:28.280> development<00:02:29.280> uh<00:02:29.599> kind<00:02:29.720> of 00:02:30.030 --> 00:02:30.040 align:start position:0% came to protocol development uh kind of 00:02:30.040 --> 00:02:33.670 align:start position:0% came to protocol development uh kind of fast<00:02:30.280> forward<00:02:30.800> a<00:02:30.920> little<00:02:31.080> bit<00:02:31.480> later<00:02:32.480> and<00:02:33.480> you 00:02:33.670 --> 00:02:33.680 align:start position:0% fast forward a little bit later and you 00:02:33.680 --> 00:02:35.150 align:start position:0% fast forward a little bit later and you have<00:02:33.800> the<00:02:33.959> situations<00:02:34.440> where<00:02:34.560> developers<00:02:34.959> do 00:02:35.150 --> 00:02:35.160 align:start position:0% have the situations where developers do 00:02:35.160 --> 00:02:37.509 align:start position:0% have the situations where developers do developer<00:02:35.720> things<00:02:36.560> where<00:02:37.000> the<00:02:37.120> developer 00:02:37.509 --> 00:02:37.519 align:start position:0% developer things where the developer 00:02:37.519 --> 00:02:39.589 align:start position:0% developer things where the developer might<00:02:37.680> have<00:02:37.920> an<00:02:38.120> interesting<00:02:38.599> idea<00:02:39.319> and<00:02:39.440> might 00:02:39.589 --> 00:02:39.599 align:start position:0% might have an interesting idea and might 00:02:39.599 --> 00:02:41.350 align:start position:0% might have an interesting idea and might have<00:02:39.760> some<00:02:39.959> problems<00:02:40.319> bringing<00:02:40.640> it<00:02:40.720> to<00:02:40.879> Market 00:02:41.350 --> 00:02:41.360 align:start position:0% have some problems bringing it to Market 00:02:41.360 --> 00:02:42.509 align:start position:0% have some problems bringing it to Market specifically<00:02:41.879> because<00:02:42.080> they're<00:02:42.280> just<00:02:42.400> kind 00:02:42.509 --> 00:02:42.519 align:start position:0% specifically because they're just kind 00:02:42.519 --> 00:02:43.949 align:start position:0% specifically because they're just kind of<00:02:42.640> handing<00:02:42.920> a<00:02:43.040> protocol<00:02:43.440> over<00:02:43.599> to<00:02:43.760> someone 00:02:43.949 --> 00:02:43.959 align:start position:0% of handing a protocol over to someone 00:02:43.959 --> 00:02:46.030 align:start position:0% of handing a protocol over to someone and<00:02:44.080> saying<00:02:44.440> here<00:02:44.680> build<00:02:44.920> on<00:02:45.159> this<00:02:45.599> build<00:02:45.920> all 00:02:46.030 --> 00:02:46.040 align:start position:0% and saying here build on this build all 00:02:46.040 --> 00:02:47.509 align:start position:0% and saying here build on this build all these<00:02:46.159> great<00:02:46.360> ideas<00:02:46.680> on<00:02:46.800> my<00:02:46.959> protocol<00:02:47.360> it'll 00:02:47.509 --> 00:02:47.519 align:start position:0% these great ideas on my protocol it'll 00:02:47.519 --> 00:02:49.550 align:start position:0% these great ideas on my protocol it'll be<00:02:47.720> great<00:02:48.360> but<00:02:48.560> the<00:02:48.760> problem<00:02:49.040> is<00:02:49.200> it's<00:02:49.360> not 00:02:49.550 --> 00:02:49.560 align:start position:0% be great but the problem is it's not 00:02:49.560 --> 00:02:51.110 align:start position:0% be great but the problem is it's not taking<00:02:49.879> those<00:02:50.040> first<00:02:50.360> principles<00:02:50.840> into 00:02:51.110 --> 00:02:51.120 align:start position:0% taking those first principles into 00:02:51.120 --> 00:02:53.030 align:start position:0% taking those first principles into account<00:02:51.800> and<00:02:51.920> a<00:02:52.000> couple<00:02:52.200> of<00:02:52.319> years<00:02:52.519> ago<00:02:52.800> Dan 00:02:53.030 --> 00:02:53.040 align:start position:0% account and a couple of years ago Dan 00:02:53.040 --> 00:02:55.030 align:start position:0% account and a couple of years ago Dan Romero<00:02:53.440> from<00:02:53.560> forcaster<00:02:54.159> put<00:02:54.280> out<00:02:54.400> a<00:02:54.560> post 00:02:55.030 --> 00:02:55.040 align:start position:0% Romero from forcaster put out a post 00:02:55.040 --> 00:02:57.790 align:start position:0% Romero from forcaster put out a post post<00:02:55.560> post<00:02:56.560> called<00:02:56.879> Product<00:02:57.159> Le<00:02:57.440> protocol 00:02:57.790 --> 00:02:57.800 align:start position:0% post post called Product Le protocol 00:02:57.800 --> 00:02:59.589 align:start position:0% post post called Product Le protocol development<00:02:58.599> and<00:02:58.680> it's<00:02:58.879> specifically<00:02:59.360> dealt 00:02:59.589 --> 00:02:59.599 align:start position:0% development and it's specifically dealt 00:02:59.599 --> 00:03:02.149 align:start position:0% development and it's specifically dealt with<00:02:59.680> the<00:02:59.840> the<00:03:00.000> idea<00:03:00.840> that<00:03:01.360> as<00:03:01.519> a<00:03:01.720> protocol 00:03:02.149 --> 00:03:02.159 align:start position:0% with the the idea that as a protocol 00:03:02.159 --> 00:03:04.149 align:start position:0% with the the idea that as a protocol developer<00:03:02.879> you're<00:03:03.080> building<00:03:03.440> the<00:03:03.560> first<00:03:03.879> apps 00:03:04.149 --> 00:03:04.159 align:start position:0% developer you're building the first apps 00:03:04.159 --> 00:03:05.830 align:start position:0% developer you're building the first apps and<00:03:04.360> clients<00:03:04.760> that<00:03:04.920> leverage<00:03:05.319> your<00:03:05.519> own 00:03:05.830 --> 00:03:05.840 align:start position:0% and clients that leverage your own 00:03:05.840 --> 00:03:07.550 align:start position:0% and clients that leverage your own protocol<00:03:06.720> and<00:03:06.840> are<00:03:07.000> then<00:03:07.159> taking<00:03:07.440> the 00:03:07.550 --> 00:03:07.560 align:start position:0% protocol and are then taking the 00:03:07.560 --> 00:03:10.070 align:start position:0% protocol and are then taking the feedback<00:03:08.080> from<00:03:08.360> those<00:03:08.720> to<00:03:08.959> inform<00:03:09.599> protocol 00:03:10.070 --> 00:03:10.080 align:start position:0% feedback from those to inform protocol 00:03:10.080 --> 00:03:13.030 align:start position:0% feedback from those to inform protocol development<00:03:11.040> namely<00:03:11.360> in<00:03:11.599> his<00:03:11.840> case<00:03:12.720> there<00:03:12.840> are 00:03:13.030 --> 00:03:13.040 align:start position:0% development namely in his case there are 00:03:13.040 --> 00:03:14.589 align:start position:0% development namely in his case there are three<00:03:13.239> core<00:03:13.480> tenants<00:03:13.920> of<00:03:14.080> product<00:03:14.360> lied 00:03:14.589 --> 00:03:14.599 align:start position:0% three core tenants of product lied 00:03:14.599 --> 00:03:17.270 align:start position:0% three core tenants of product lied protocol<00:03:14.959> development<00:03:15.959> the<00:03:16.120> first<00:03:16.440> is<00:03:16.760> that 00:03:17.270 --> 00:03:17.280 align:start position:0% protocol development the first is that 00:03:17.280 --> 00:03:19.470 align:start position:0% protocol development the first is that users<00:03:17.760> use<00:03:18.120> apps<00:03:18.360> and<00:03:18.599> clients<00:03:19.159> they<00:03:19.280> don't 00:03:19.470 --> 00:03:19.480 align:start position:0% users use apps and clients they don't 00:03:19.480 --> 00:03:22.149 align:start position:0% users use apps and clients they don't use<00:03:19.720> protocols<00:03:20.680> so<00:03:20.879> in<00:03:21.159> let's<00:03:21.319> use<00:03:21.519> foraster 00:03:22.149 --> 00:03:22.159 align:start position:0% use protocols so in let's use foraster 00:03:22.159 --> 00:03:24.030 align:start position:0% use protocols so in let's use foraster for<00:03:22.280> the<00:03:22.400> sake<00:03:22.599> of<00:03:22.760> the<00:03:22.959> example<00:03:23.560> users<00:03:23.959> are 00:03:24.030 --> 00:03:24.040 align:start position:0% for the sake of the example users are 00:03:24.040 --> 00:03:26.110 align:start position:0% for the sake of the example users are using<00:03:24.280> warp<00:03:24.599> cast<00:03:25.159> they're<00:03:25.480> kind<00:03:25.599> of<00:03:25.760> making 00:03:26.110 --> 00:03:26.120 align:start position:0% using warp cast they're kind of making 00:03:26.120 --> 00:03:27.509 align:start position:0% using warp cast they're kind of making posts<00:03:26.519> they're<00:03:26.720> interacting<00:03:27.200> with<00:03:27.319> the 00:03:27.509 --> 00:03:27.519 align:start position:0% posts they're interacting with the 00:03:27.519 --> 00:03:29.350 align:start position:0% posts they're interacting with the application<00:03:28.519> and<00:03:28.720> on<00:03:28.799> the<00:03:28.959> back<00:03:29.080> end<00:03:29.239> it's 00:03:29.350 --> 00:03:29.360 align:start position:0% application and on the back end it's 00:03:29.360 --> 00:03:31.670 align:start position:0% application and on the back end it's forast<00:03:30.000> the<00:03:30.120> protocol<00:03:30.519> that's<00:03:30.720> kind<00:03:30.840> of 00:03:31.670 --> 00:03:31.680 align:start position:0% forast the protocol that's kind of 00:03:31.680 --> 00:03:33.670 align:start position:0% forast the protocol that's kind of informing<00:03:32.120> all<00:03:32.360> these<00:03:32.519> interactions<00:03:33.519> the 00:03:33.670 --> 00:03:33.680 align:start position:0% informing all these interactions the 00:03:33.680 --> 00:03:35.990 align:start position:0% informing all these interactions the second<00:03:34.000> thing<00:03:34.480> is<00:03:34.760> that<00:03:35.159> a<00:03:35.319> developer<00:03:35.720> worth 00:03:35.990 --> 00:03:36.000 align:start position:0% second thing is that a developer worth 00:03:36.000 --> 00:03:38.750 align:start position:0% second thing is that a developer worth their<00:03:36.159> salt<00:03:36.840> will<00:03:37.080> make<00:03:37.280> sure<00:03:38.280> that<00:03:38.480> they<00:03:38.560> are 00:03:38.750 --> 00:03:38.760 align:start position:0% their salt will make sure that they are 00:03:38.760 --> 00:03:41.429 align:start position:0% their salt will make sure that they are concerned<00:03:39.319> with<00:03:40.159> meaningful<00:03:40.760> daily<00:03:41.120> active 00:03:41.429 --> 00:03:41.439 align:start position:0% concerned with meaningful daily active 00:03:41.439 --> 00:03:43.830 align:start position:0% concerned with meaningful daily active users<00:03:42.360> instead<00:03:42.640> of<00:03:42.760> the<00:03:42.879> coolest<00:03:43.360> technology 00:03:43.830 --> 00:03:43.840 align:start position:0% users instead of the coolest technology 00:03:43.840 --> 00:03:45.910 align:start position:0% users instead of the coolest technology that<00:03:44.000> they<00:03:44.080> want<00:03:44.200> to<00:03:44.400> use<00:03:45.159> a<00:03:45.280> developer<00:03:45.760> that's 00:03:45.910 --> 00:03:45.920 align:start position:0% that they want to use a developer that's 00:03:45.920 --> 00:03:47.670 align:start position:0% that they want to use a developer that's building<00:03:46.200> for<00:03:46.519> an<00:03:46.680> audience<00:03:47.159> specifically 00:03:47.670 --> 00:03:47.680 align:start position:0% building for an audience specifically 00:03:47.680 --> 00:03:49.990 align:start position:0% building for an audience specifically and<00:03:47.840> not<00:03:48.360> experimenting<00:03:49.360> and<00:03:49.480> the<00:03:49.599> third<00:03:49.799> and 00:03:49.990 --> 00:03:50.000 align:start position:0% and not experimenting and the third and 00:03:50.000 --> 00:03:52.229 align:start position:0% and not experimenting and the third and final<00:03:50.319> part<00:03:50.480> of<00:03:50.599> it<00:03:50.840> is<00:03:51.120> that<00:03:51.519> Protocols<00:03:52.000> are 00:03:52.229 --> 00:03:52.239 align:start position:0% final part of it is that Protocols are 00:03:52.239 --> 00:03:53.750 align:start position:0% final part of it is that Protocols are valued<00:03:52.640> based<00:03:52.840> on<00:03:52.920> the<00:03:53.040> clients<00:03:53.360> and<00:03:53.519> app 00:03:53.750 --> 00:03:53.760 align:start position:0% valued based on the clients and app 00:03:53.760 --> 00:03:55.630 align:start position:0% valued based on the clients and app success<00:03:54.079> that<00:03:54.200> build<00:03:54.400> on<00:03:54.640> set<00:03:54.840> protocol<00:03:55.480> so 00:03:55.630 --> 00:03:55.640 align:start position:0% success that build on set protocol so 00:03:55.640 --> 00:03:57.630 align:start position:0% success that build on set protocol so it's<00:03:55.920> always<00:03:56.200> making<00:03:56.480> sure<00:03:56.760> that<00:03:57.000> apps<00:03:57.439> and 00:03:57.630 --> 00:03:57.640 align:start position:0% it's always making sure that apps and 00:03:57.640 --> 00:03:59.309 align:start position:0% it's always making sure that apps and clients<00:03:58.079> are<00:03:58.280> at<00:03:58.360> the<00:03:58.480> center<00:03:58.879> here<00:03:59.120> and<00:03:59.200> then 00:03:59.309 --> 00:03:59.319 align:start position:0% clients are at the center here and then 00:03:59.319 --> 00:04:00.990 align:start position:0% clients are at the center here and then if<00:03:59.400> you're<00:03:59.480> building<00:03:59.920> a<00:04:00.040> protocol<00:04:00.640> you<00:04:00.760> are 00:04:00.990 --> 00:04:01.000 align:start position:0% if you're building a protocol you are 00:04:01.000 --> 00:04:02.630 align:start position:0% if you're building a protocol you are defining<00:04:01.400> the<00:04:01.519> blueprint<00:04:02.079> for<00:04:02.319> how<00:04:02.480> that 00:04:02.630 --> 00:04:02.640 align:start position:0% defining the blueprint for how that 00:04:02.640 --> 00:04:04.429 align:start position:0% defining the blueprint for how that protocol<00:04:03.040> should<00:04:03.200> be<00:04:03.400> used<00:04:04.040> by<00:04:04.200> being 00:04:04.429 --> 00:04:04.439 align:start position:0% protocol should be used by being 00:04:04.439 --> 00:04:05.750 align:start position:0% protocol should be used by being informed<00:04:04.760> of<00:04:04.959> what's<00:04:05.159> happening<00:04:05.439> on<00:04:05.599> these 00:04:05.750 --> 00:04:05.760 align:start position:0% informed of what's happening on these 00:04:05.760 --> 00:04:07.589 align:start position:0% informed of what's happening on these apps<00:04:06.000> and<00:04:06.200> clients<00:04:06.680> that<00:04:07.200> people<00:04:07.439> are 00:04:07.589 --> 00:04:07.599 align:start position:0% apps and clients that people are 00:04:07.599 --> 00:04:09.990 align:start position:0% apps and clients that people are actually<00:04:08.040> using<00:04:09.040> and<00:04:09.120> then<00:04:09.319> finally<00:04:09.599> to<00:04:09.799> round 00:04:09.990 --> 00:04:10.000 align:start position:0% actually using and then finally to round 00:04:10.000 --> 00:04:12.589 align:start position:0% actually using and then finally to round it<00:04:10.200> out<00:04:11.200> complication<00:04:11.879> requires<00:04:12.280> a<00:04:12.360> bit<00:04:12.480> of 00:04:12.589 --> 00:04:12.599 align:start position:0% it out complication requires a bit of 00:04:12.599 --> 00:04:14.470 align:start position:0% it out complication requires a bit of order<00:04:13.280> recently<00:04:13.680> in<00:04:13.799> the<00:04:14.000> space<00:04:14.239> we're 00:04:14.470 --> 00:04:14.480 align:start position:0% order recently in the space we're 00:04:14.480 --> 00:04:16.509 align:start position:0% order recently in the space we're finding<00:04:15.000> protocols<00:04:15.519> wanting<00:04:15.920> to<00:04:16.239> have<00:04:16.400> their 00:04:16.509 --> 00:04:16.519 align:start position:0% finding protocols wanting to have their 00:04:16.519 --> 00:04:18.710 align:start position:0% finding protocols wanting to have their own<00:04:16.759> block<00:04:17.040> space<00:04:17.680> building<00:04:18.079> app<00:04:18.359> specific 00:04:18.710 --> 00:04:18.720 align:start position:0% own block space building app specific 00:04:18.720 --> 00:04:21.030 align:start position:0% own block space building app specific rollups<00:04:19.600> and<00:04:19.759> I<00:04:19.880> think<00:04:20.199> just<00:04:20.400> the<00:04:20.560> bottom<00:04:20.840> line 00:04:21.030 --> 00:04:21.040 align:start position:0% rollups and I think just the bottom line 00:04:21.040 --> 00:04:22.629 align:start position:0% rollups and I think just the bottom line of<00:04:21.160> all<00:04:21.320> this<00:04:21.479> is<00:04:21.639> just<00:04:21.799> making<00:04:22.079> sure<00:04:22.360> that<00:04:22.560> if 00:04:22.629 --> 00:04:22.639 align:start position:0% of all this is just making sure that if 00:04:22.639 --> 00:04:25.510 align:start position:0% of all this is just making sure that if you<00:04:22.880> kind<00:04:23.000> of<00:04:23.160> go<00:04:23.320> down<00:04:23.560> this<00:04:23.800> route<00:04:24.520> that<00:04:24.800> you 00:04:25.510 --> 00:04:25.520 align:start position:0% you kind of go down this route that you 00:04:25.520 --> 00:04:27.150 align:start position:0% you kind of go down this route that you have<00:04:25.680> to<00:04:25.800> be<00:04:26.080> the<00:04:26.240> block<00:04:26.520> space<00:04:26.800> you<00:04:26.919> want<00:04:27.040> to 00:04:27.150 --> 00:04:27.160 align:start position:0% have to be the block space you want to 00:04:27.160 --> 00:04:28.749 align:start position:0% have to be the block space you want to see<00:04:27.360> in<00:04:27.479> the<00:04:27.600> world<00:04:27.960> you<00:04:28.120> have<00:04:28.199> to<00:04:28.360> make<00:04:28.520> sure 00:04:28.749 --> 00:04:28.759 align:start position:0% see in the world you have to make sure 00:04:28.759 --> 00:04:30.390 align:start position:0% see in the world you have to make sure that<00:04:28.919> when<00:04:29.000> you're<00:04:29.160> building<00:04:29.479> this<00:04:30.039> you<00:04:30.199> are 00:04:30.390 --> 00:04:30.400 align:start position:0% that when you're building this you are 00:04:30.400 --> 00:04:32.590 align:start position:0% that when you're building this you are building<00:04:30.759> the<00:04:30.919> killer<00:04:31.320> app<00:04:31.880> leveraging<00:04:32.440> this 00:04:32.590 --> 00:04:32.600 align:start position:0% building the killer app leveraging this 00:04:32.600 --> 00:04:34.350 align:start position:0% building the killer app leveraging this block<00:04:32.919> space<00:04:33.520> that<00:04:33.639> you're<00:04:33.759> not<00:04:33.960> going<00:04:34.199> the 00:04:34.350 --> 00:04:34.360 align:start position:0% block space that you're not going the 00:04:34.360 --> 00:04:35.990 align:start position:0% block space that you're not going the usual<00:04:34.759> route<00:04:35.080> of<00:04:35.240> building<00:04:35.600> this<00:04:35.759> thing<00:04:35.880> and 00:04:35.990 --> 00:04:36.000 align:start position:0% usual route of building this thing and 00:04:36.000 --> 00:04:37.990 align:start position:0% usual route of building this thing and saying<00:04:36.360> hey<00:04:36.560> everyone<00:04:37.320> we're<00:04:37.479> going<00:04:37.560> to<00:04:37.720> get<00:04:37.840> a 00:04:37.990 --> 00:04:38.000 align:start position:0% saying hey everyone we're going to get a 00:04:38.000 --> 00:04:39.590 align:start position:0% saying hey everyone we're going to get a growth<00:04:38.280> marketer<00:04:38.720> to<00:04:38.880> bring<00:04:39.080> a<00:04:39.240> million 00:04:39.590 --> 00:04:39.600 align:start position:0% growth marketer to bring a million 00:04:39.600 --> 00:04:40.790 align:start position:0% growth marketer to bring a million developers<00:04:40.039> through<00:04:40.280> the<00:04:40.400> door<00:04:40.600> and<00:04:40.720> then 00:04:40.790 --> 00:04:40.800 align:start position:0% developers through the door and then 00:04:40.800 --> 00:04:41.909 align:start position:0% developers through the door and then they're<00:04:40.919> going<00:04:41.000> to<00:04:41.120> build<00:04:41.320> a<00:04:41.440> whole<00:04:41.600> bunch<00:04:41.800> of 00:04:41.909 --> 00:04:41.919 align:start position:0% they're going to build a whole bunch of 00:04:41.919 --> 00:04:43.469 align:start position:0% they're going to build a whole bunch of stuff<00:04:42.120> on<00:04:42.280> our<00:04:42.440> new<00:04:42.600> protocol<00:04:43.000> and<00:04:43.120> it's<00:04:43.400> going 00:04:43.469 --> 00:04:43.479 align:start position:0% stuff on our new protocol and it's going 00:04:43.479 --> 00:04:45.150 align:start position:0% stuff on our new protocol and it's going to<00:04:43.600> be<00:04:43.759> great<00:04:44.320> it's<00:04:44.440> like<00:04:44.639> no<00:04:44.840> you're<00:04:44.960> going<00:04:45.080> to 00:04:45.150 --> 00:04:45.160 align:start position:0% to be great it's like no you're going to 00:04:45.160 --> 00:04:46.790 align:start position:0% to be great it's like no you're going to be<00:04:45.280> building<00:04:45.680> the<00:04:45.840> app<00:04:46.080> that<00:04:46.280> specifically 00:04:46.790 --> 00:04:46.800 align:start position:0% be building the app that specifically 00:04:46.800 --> 00:04:48.950 align:start position:0% be building the app that specifically leverages<00:04:47.520> this<00:04:47.720> for<00:04:47.960> what<00:04:48.080> you<00:04:48.280> designed<00:04:48.720> it 00:04:48.950 --> 00:04:48.960 align:start position:0% leverages this for what you designed it 00:04:48.960 --> 00:04:51.430 align:start position:0% leverages this for what you designed it to<00:04:49.199> do<00:04:49.840> and<00:04:49.960> if<00:04:50.039> it<00:04:50.160> doesn't<00:04:50.400> work<00:04:50.560> out<00:04:50.800> well 00:04:51.430 --> 00:04:51.440 align:start position:0% to do and if it doesn't work out well 00:04:51.440 --> 00:04:52.550 align:start position:0% to do and if it doesn't work out well then<00:04:51.560> you<00:04:51.639> might<00:04:51.800> need<00:04:51.919> to<00:04:52.039> hit<00:04:52.199> the<00:04:52.280> drawing 00:04:52.550 --> 00:04:52.560 align:start position:0% then you might need to hit the drawing 00:04:52.560 --> 00:04:54.670 align:start position:0% then you might need to hit the drawing board<00:04:52.880> again<00:04:53.440> but<00:04:53.560> it's<00:04:53.800> all<00:04:54.120> specifically 00:04:54.670 --> 00:04:54.680 align:start position:0% board again but it's all specifically 00:04:54.680 --> 00:04:56.510 align:start position:0% board again but it's all specifically going<00:04:54.960> back<00:04:55.120> to<00:04:55.320> this<00:04:55.560> core<00:04:55.880> idea<00:04:56.120> of<00:04:56.240> product 00:04:56.510 --> 00:04:56.520 align:start position:0% going back to this core idea of product 00:04:56.520 --> 00:04:58.670 align:start position:0% going back to this core idea of product Le<00:04:56.759> growth<00:04:57.440> where<00:04:57.759> you<00:04:57.919> are<00:04:58.199> presenting 00:04:58.670 --> 00:04:58.680 align:start position:0% Le growth where you are presenting 00:04:58.680 --> 00:04:59.990 align:start position:0% Le growth where you are presenting something<00:04:58.919> to<00:04:59.080> the<00:04:59.199> market<00:04:59.800> you're 00:04:59.990 --> 00:05:00.000 align:start position:0% something to the market you're 00:05:00.000 --> 00:05:01.749 align:start position:0% something to the market you're presenting<00:05:00.400> the<00:05:00.560> end<00:05:00.840> users<00:05:01.360> with<00:05:01.520> something 00:05:01.749 --> 00:05:01.759 align:start position:0% presenting the end users with something 00:05:01.759 --> 00:05:04.110 align:start position:0% presenting the end users with something to<00:05:02.000> use<00:05:02.720> they<00:05:02.840> are<00:05:03.039> then<00:05:03.240> informing<00:05:03.919> what 00:05:04.110 --> 00:05:04.120 align:start position:0% to use they are then informing what 00:05:04.120 --> 00:05:05.670 align:start position:0% to use they are then informing what happens<00:05:04.479> with<00:05:04.680> that<00:05:05.080> and<00:05:05.240> everything<00:05:05.560> in 00:05:05.670 --> 00:05:05.680 align:start position:0% happens with that and everything in 00:05:05.680 --> 00:05:07.790 align:start position:0% happens with that and everything in between<00:05:06.360> so<00:05:06.600> kind<00:05:06.720> of<00:05:06.919> returning<00:05:07.280> to<00:05:07.440> First 00:05:07.790 --> 00:05:07.800 align:start position:0% between so kind of returning to First 00:05:07.800 --> 00:05:10.430 align:start position:0% between so kind of returning to First principles<00:05:08.759> I<00:05:08.880> encourage<00:05:09.440> experimentation 00:05:10.430 --> 00:05:10.440 align:start position:0% principles I encourage experimentation 00:05:10.440 --> 00:05:11.909 align:start position:0% principles I encourage experimentation but<00:05:10.560> at<00:05:10.680> the<00:05:10.759> end<00:05:10.919> of<00:05:11.000> the<00:05:11.160> experimentation<00:05:11.800> if 00:05:11.909 --> 00:05:11.919 align:start position:0% but at the end of the experimentation if 00:05:11.919 --> 00:05:13.590 align:start position:0% but at the end of the experimentation if you<00:05:12.039> do<00:05:12.199> wish<00:05:12.320> to<00:05:12.440> bring<00:05:12.600> something<00:05:12.840> to<00:05:13.000> Market 00:05:13.590 --> 00:05:13.600 align:start position:0% you do wish to bring something to Market 00:05:13.600 --> 00:05:14.870 align:start position:0% you do wish to bring something to Market please<00:05:13.840> keep<00:05:14.000> designing<00:05:14.360> and<00:05:14.479> developing 00:05:14.870 --> 00:05:14.880 align:start position:0% please keep designing and developing 00:05:14.880 --> 00:05:16.430 align:start position:0% please keep designing and developing with<00:05:15.000> users<00:05:15.280> in<00:05:15.400> mind<00:05:15.639> and<00:05:15.759> making<00:05:16.000> sure<00:05:16.240> those 00:05:16.430 --> 00:05:16.440 align:start position:0% with users in mind and making sure those 00:05:16.440 --> 00:05:18.189 align:start position:0% with users in mind and making sure those users<00:05:16.840> are<00:05:17.000> able<00:05:17.199> to<00:05:17.360> give<00:05:17.479> you<00:05:17.639> feedback<00:05:18.039> to 00:05:18.189 --> 00:05:18.199 align:start position:0% users are able to give you feedback to 00:05:18.199 --> 00:05:19.550 align:start position:0% users are able to give you feedback to inform<00:05:18.520> the<00:05:18.639> next<00:05:18.840> stages<00:05:19.160> of<00:05:19.280> what<00:05:19.400> you're 00:05:19.550 --> 00:05:19.560 align:start position:0% inform the next stages of what you're 00:05:19.560 --> 00:05:25.510 align:start position:0% inform the next stages of what you're building<00:05:20.800> so 00:05:25.510 --> 00:05:25.520 align:start position:0% 00:05:25.520 --> 00:05:28.670 align:start position:0% thanks<00:05:26.520> thanks<00:05:26.720> a<00:05:26.840> lot<00:05:27.080> Gregory<00:05:28.080> and<00:05:28.360> now<00:05:28.520> we 00:05:28.670 --> 00:05:28.680 align:start position:0% thanks thanks a lot Gregory and now we 00:05:28.680 --> 00:05:30.150 align:start position:0% thanks thanks a lot Gregory and now we have<00:05:28.880> a<00:05:28.960> little<00:05:29.080> bit<00:05:29.199> of<00:05:29.319> time<00:05:29.400> for<00:05:29.720> questions 00:05:30.150 --> 00:05:30.160 align:start position:0% have a little bit of time for questions 00:05:30.160 --> 00:05:32.749 align:start position:0% have a little bit of time for questions wow<00:05:30.360> someone's<00:05:30.759> ready<00:05:31.240> I<00:05:31.360> can<00:05:31.639> I<00:05:31.720> can<00:05:31.840> see<00:05:32.199> that 00:05:32.749 --> 00:05:32.759 align:start position:0% wow someone's ready I can I can see that 00:05:32.759 --> 00:05:35.670 align:start position:0% wow someone's ready I can I can see that all<00:05:32.880> right<00:05:33.080> let<00:05:33.199> me<00:05:33.440> get<00:05:33.759> this<00:05:34.120> box<00:05:34.360> to<00:05:34.680> you 00:05:35.670 --> 00:05:35.680 align:start position:0% all right let me get this box to you 00:05:35.680 --> 00:05:38.670 align:start position:0% all right let me get this box to you ready<00:05:36.479> and 00:05:38.670 --> 00:05:38.680 align:start position:0% ready and 00:05:38.680 --> 00:05:41.469 align:start position:0% ready and go<00:05:39.680> hello<00:05:40.039> thank<00:05:40.240> you<00:05:40.560> don't<00:05:40.919> I'm<00:05:41.120> I'm<00:05:41.240> curious 00:05:41.469 --> 00:05:41.479 align:start position:0% go hello thank you don't I'm I'm curious 00:05:41.479 --> 00:05:43.749 align:start position:0% go hello thank you don't I'm I'm curious to<00:05:41.639> have<00:05:41.800> your<00:05:41.919> opinion<00:05:42.280> about<00:05:42.520> the<00:05:42.720> fact<00:05:43.039> like 00:05:43.749 --> 00:05:43.759 align:start position:0% to have your opinion about the fact like 00:05:43.759 --> 00:05:45.350 align:start position:0% to have your opinion about the fact like don't<00:05:43.960> you<00:05:44.120> think<00:05:44.360> like<00:05:44.520> the<00:05:44.680> space<00:05:45.000> is<00:05:45.160> even 00:05:45.350 --> 00:05:45.360 align:start position:0% don't you think like the space is even 00:05:45.360 --> 00:05:47.990 align:start position:0% don't you think like the space is even design<00:05:45.880> to<00:05:46.240> not<00:05:46.560> incentivize<00:05:47.400> like 00:05:47.990 --> 00:05:48.000 align:start position:0% design to not incentivize like 00:05:48.000 --> 00:05:49.950 align:start position:0% design to not incentivize like competition<00:05:48.600> between<00:05:48.880> different<00:05:49.160> rollups 00:05:49.950 --> 00:05:49.960 align:start position:0% competition between different rollups 00:05:49.960 --> 00:05:51.550 align:start position:0% competition between different rollups because<00:05:50.240> they're<00:05:50.440> all<00:05:50.639> looking<00:05:50.960> to<00:05:51.240> attract 00:05:51.550 --> 00:05:51.560 align:start position:0% because they're all looking to attract 00:05:51.560 --> 00:05:54.270 align:start position:0% because they're all looking to attract liquidity<00:05:52.160> attract<00:05:52.560> user<00:05:53.240> and<00:05:53.360> just<00:05:53.720> grow 00:05:54.270 --> 00:05:54.280 align:start position:0% liquidity attract user and just grow 00:05:54.280 --> 00:05:57.270 align:start position:0% liquidity attract user and just grow like<00:05:54.880> individually<00:05:55.720> and<00:05:55.880> so<00:05:56.440> this<00:05:56.680> doesn't<00:05:57.039> go 00:05:57.270 --> 00:05:57.280 align:start position:0% like individually and so this doesn't go 00:05:57.280 --> 00:05:59.350 align:start position:0% like individually and so this doesn't go in<00:05:57.520> pair<00:05:57.800> with<00:05:58.039> like<00:05:58.199> taking<00:05:58.479> care<00:05:58.639> of<00:05:58.800> re<00:05:59.080> user 00:05:59.350 --> 00:05:59.360 align:start position:0% in pair with like taking care of re user 00:05:59.360 --> 00:06:00.790 align:start position:0% in pair with like taking care of re user because<00:05:59.720> they<00:05:59.840> compete<00:06:00.120> for<00:06:00.280> user<00:06:00.639> they 00:06:00.790 --> 00:06:00.800 align:start position:0% because they compete for user they 00:06:00.800 --> 00:06:02.390 align:start position:0% because they compete for user they compete<00:06:01.080> for<00:06:01.280> liquidity<00:06:01.800> and<00:06:01.960> there<00:06:02.080> is<00:06:02.280> like 00:06:02.390 --> 00:06:02.400 align:start position:0% compete for liquidity and there is like 00:06:02.400 --> 00:06:05.189 align:start position:0% compete for liquidity and there is like a<00:06:02.600> lack<00:06:02.800> of<00:06:03.440> interoperability<00:06:04.440> really<00:06:05.039> so 00:06:05.189 --> 00:06:05.199 align:start position:0% a lack of interoperability really so 00:06:05.199 --> 00:06:06.909 align:start position:0% a lack of interoperability really so what<00:06:05.319> are<00:06:05.479> your<00:06:05.680> thoughts<00:06:05.880> on<00:06:06.080> this<00:06:06.560> so<00:06:06.720> in<00:06:06.800> the 00:06:06.909 --> 00:06:06.919 align:start position:0% what are your thoughts on this so in the 00:06:06.919 --> 00:06:08.909 align:start position:0% what are your thoughts on this so in the case<00:06:07.080> of<00:06:07.199> like<00:06:07.319> very<00:06:07.599> app<00:06:07.840> specific<00:06:08.280> case 00:06:08.909 --> 00:06:08.919 align:start position:0% case of like very app specific case 00:06:08.919 --> 00:06:10.589 align:start position:0% case of like very app specific case you're<00:06:09.199> then<00:06:09.360> competing<00:06:09.680> with<00:06:09.840> others<00:06:10.479> like 00:06:10.589 --> 00:06:10.599 align:start position:0% you're then competing with others like 00:06:10.599 --> 00:06:12.790 align:start position:0% you're then competing with others like we<00:06:10.720> don't<00:06:10.880> need<00:06:11.360> all<00:06:11.599> those<00:06:11.800> rollups<00:06:12.599> no<00:06:12.680> we 00:06:12.790 --> 00:06:12.800 align:start position:0% we don't need all those rollups no we 00:06:12.800 --> 00:06:15.270 align:start position:0% we don't need all those rollups no we don't<00:06:13.000> like<00:06:13.120> it's<00:06:13.360> it's<00:06:13.599> it's<00:06:14.120> unnecessary 00:06:15.270 --> 00:06:15.280 align:start position:0% don't like it's it's it's unnecessary 00:06:15.280 --> 00:06:17.390 align:start position:0% don't like it's it's it's unnecessary like<00:06:16.280> I<00:06:16.360> think<00:06:16.479> I'm<00:06:16.599> an<00:06:16.720> agreement<00:06:16.960> with<00:06:17.120> you 00:06:17.390 --> 00:06:17.400 align:start position:0% like I think I'm an agreement with you 00:06:17.400 --> 00:06:19.309 align:start position:0% like I think I'm an agreement with you we<00:06:17.680> we<00:06:17.800> don't<00:06:18.080> to<00:06:18.199> a<00:06:18.319> certain<00:06:18.599> extent<00:06:19.160> but 00:06:19.309 --> 00:06:19.319 align:start position:0% we we don't to a certain extent but 00:06:19.319 --> 00:06:20.550 align:start position:0% we we don't to a certain extent but making<00:06:19.520> sure<00:06:19.759> that<00:06:19.880> if<00:06:19.960> you<00:06:20.080> were<00:06:20.240> building 00:06:20.550 --> 00:06:20.560 align:start position:0% making sure that if you were building 00:06:20.560 --> 00:06:22.430 align:start position:0% making sure that if you were building something<00:06:20.800> to<00:06:21.080> then<00:06:21.240> build<00:06:21.479> in<00:06:21.840> in<00:06:22.000> those<00:06:22.160> use 00:06:22.430 --> 00:06:22.440 align:start position:0% something to then build in in those use 00:06:22.440 --> 00:06:25.589 align:start position:0% something to then build in in those use cases<00:06:22.720> at<00:06:22.840> the<00:06:22.960> same<00:06:23.479> time<00:06:24.479> um<00:06:24.759> or<00:06:25.240> I<00:06:25.319> might<00:06:25.479> not 00:06:25.589 --> 00:06:25.599 align:start position:0% cases at the same time um or I might not 00:06:25.599 --> 00:06:27.469 align:start position:0% cases at the same time um or I might not be<00:06:25.880> understanding<00:06:26.080> the<00:06:26.199> question<00:06:26.479> correctly 00:06:27.469 --> 00:06:27.479 align:start position:0% be understanding the question correctly 00:06:27.479 --> 00:06:29.830 align:start position:0% be understanding the question correctly well<00:06:27.639> I<00:06:27.800> think<00:06:28.120> like<00:06:28.440> the<00:06:28.919> the<00:06:29.080> the<00:06:29.240> space<00:06:29.720> is 00:06:29.830 --> 00:06:29.840 align:start position:0% well I think like the the the space is 00:06:29.840 --> 00:06:31.510 align:start position:0% well I think like the the the space is designed<00:06:30.120> in<00:06:30.240> a<00:06:30.400> way<00:06:30.639> like<00:06:30.880> everyone<00:06:31.199> want<00:06:31.400> to 00:06:31.510 --> 00:06:31.520 align:start position:0% designed in a way like everyone want to 00:06:31.520 --> 00:06:34.909 align:start position:0% designed in a way like everyone want to talk<00:06:31.919> own<00:06:32.120> rollup<00:06:33.080> get<00:06:33.319> users<00:06:34.199> get<00:06:34.400> liquidity 00:06:34.909 --> 00:06:34.919 align:start position:0% talk own rollup get users get liquidity 00:06:34.919 --> 00:06:36.510 align:start position:0% talk own rollup get users get liquidity but<00:06:35.080> at<00:06:35.199> the<00:06:35.319> end<00:06:35.560> like<00:06:35.680> we're<00:06:35.840> not<00:06:36.080> building 00:06:36.510 --> 00:06:36.520 align:start position:0% but at the end like we're not building 00:06:36.520 --> 00:06:38.430 align:start position:0% but at the end like we're not building something<00:06:36.919> that<00:06:37.120> actually<00:06:37.440> can<00:06:37.880> be<00:06:38.080> useful 00:06:38.430 --> 00:06:38.440 align:start position:0% something that actually can be useful 00:06:38.440 --> 00:06:40.270 align:start position:0% something that actually can be useful for<00:06:38.680> people<00:06:39.039> like<00:06:39.160> and<00:06:39.319> it's<00:06:39.599> also<00:06:40.000> sometimes 00:06:40.270 --> 00:06:40.280 align:start position:0% for people like and it's also sometimes 00:06:40.280 --> 00:06:42.790 align:start position:0% for people like and it's also sometimes just<00:06:40.520> Ser<00:06:40.800> serving<00:06:41.280> like<00:06:41.440> the<00:06:41.680> ecosystem<00:06:42.680> but 00:06:42.790 --> 00:06:42.800 align:start position:0% just Ser serving like the ecosystem but 00:06:42.800 --> 00:06:44.670 align:start position:0% just Ser serving like the ecosystem but to<00:06:42.919> an<00:06:43.039> extent<00:06:43.319> so<00:06:43.479> if<00:06:43.599> there<00:06:43.720> is<00:06:43.840> a<00:06:44.080> dominant 00:06:44.670 --> 00:06:44.680 align:start position:0% to an extent so if there is a dominant 00:06:44.680 --> 00:06:46.589 align:start position:0% to an extent so if there is a dominant use<00:06:45.039> case<00:06:45.240> that's<00:06:45.400> an<00:06:45.560> app<00:06:45.720> specific<00:06:46.039> rollup 00:06:46.589 --> 00:06:46.599 align:start position:0% use case that's an app specific rollup 00:06:46.599 --> 00:06:48.029 align:start position:0% use case that's an app specific rollup then<00:06:46.759> good<00:06:46.880> for<00:06:47.080> that<00:06:47.240> my<00:06:47.360> hope<00:06:47.520> it<00:06:47.599> it<00:06:47.720> masses 00:06:48.029 --> 00:06:48.039 align:start position:0% then good for that my hope it it masses 00:06:48.039 --> 00:06:49.629 align:start position:0% then good for that my hope it it masses the<00:06:48.120> most<00:06:48.319> amount<00:06:48.479> of<00:06:48.599> liquidity<00:06:49.199> in<00:06:49.400> in<00:06:49.520> that 00:06:49.629 --> 00:06:49.639 align:start position:0% the most amount of liquidity in in that 00:06:49.639 --> 00:06:51.150 align:start position:0% the most amount of liquidity in in that only<00:06:49.840> way<00:06:50.000> and<00:06:50.120> dominates<00:06:50.639> that<00:06:50.759> space<00:06:51.000> if 00:06:51.150 --> 00:06:51.160 align:start position:0% only way and dominates that space if 00:06:51.160 --> 00:06:52.469 align:start position:0% only way and dominates that space if it's<00:06:51.360> providing<00:06:51.840> a<00:06:51.919> good<00:06:52.080> enough<00:06:52.280> of 00:06:52.469 --> 00:06:52.479 align:start position:0% it's providing a good enough of 00:06:52.479 --> 00:06:55.430 align:start position:0% it's providing a good enough of experience<00:06:53.440> like<00:06:53.639> I'm<00:06:54.240> I<00:06:54.599> I<00:06:54.680> want<00:06:54.840> to<00:06:55.039> allow 00:06:55.430 --> 00:06:55.440 align:start position:0% experience like I'm I I want to allow 00:06:55.440 --> 00:06:56.710 align:start position:0% experience like I'm I I want to allow the<00:06:55.599> ability<00:06:55.879> for<00:06:56.039> anyone<00:06:56.280> to<00:06:56.400> create<00:06:56.599> that 00:06:56.710 --> 00:06:56.720 align:start position:0% the ability for anyone to create that 00:06:56.720 --> 00:06:58.469 align:start position:0% the ability for anyone to create that app<00:06:56.919> specific<00:06:57.240> rollup<00:06:57.759> but<00:06:57.879> at<00:06:58.000> the<00:06:58.080> same<00:06:58.280> time 00:06:58.469 --> 00:06:58.479 align:start position:0% app specific rollup but at the same time 00:06:58.479 --> 00:07:00.070 align:start position:0% app specific rollup but at the same time I<00:06:58.560> want<00:06:58.680> to<00:06:58.840> very<00:06:59.120> like<00:06:59.240> I<00:06:59.319> want<00:06:59.720> someone<00:06:59.960> to 00:07:00.070 --> 00:07:00.080 align:start position:0% I want to very like I want someone to 00:07:00.080 --> 00:07:01.710 align:start position:0% I want to very like I want someone to win<00:07:00.680> and<00:07:00.840> that's<00:07:01.080> okay<00:07:01.280> because<00:07:01.440> it<00:07:01.520> means 00:07:01.710 --> 00:07:01.720 align:start position:0% win and that's okay because it means 00:07:01.720 --> 00:07:03.749 align:start position:0% win and that's okay because it means user<00:07:02.039> getting<00:07:02.240> the<00:07:02.400> value<00:07:03.000> and<00:07:03.160> if<00:07:03.440> if<00:07:03.599> that 00:07:03.749 --> 00:07:03.759 align:start position:0% user getting the value and if if that 00:07:03.759 --> 00:07:05.390 align:start position:0% user getting the value and if if that app<00:07:03.960> specific<00:07:04.319> roll<00:07:04.599> turns<00:07:04.840> around<00:07:05.039> and<00:07:05.199> does 00:07:05.390 --> 00:07:05.400 align:start position:0% app specific roll turns around and does 00:07:05.400 --> 00:07:07.469 align:start position:0% app specific roll turns around and does something<00:07:05.879> against<00:07:06.240> user<00:07:06.560> wants<00:07:07.240> there's 00:07:07.469 --> 00:07:07.479 align:start position:0% something against user wants there's 00:07:07.479 --> 00:07:08.790 align:start position:0% something against user wants there's another<00:07:07.720> app<00:07:07.919> specific<00:07:08.199> roll<00:07:08.400> up<00:07:08.560> kind<00:07:08.680> of 00:07:08.790 --> 00:07:08.800 align:start position:0% another app specific roll up kind of 00:07:08.800 --> 00:07:10.430 align:start position:0% another app specific roll up kind of waiting<00:07:09.000> for<00:07:09.240> that<00:07:09.840> or<00:07:10.000> waiting<00:07:10.199> for<00:07:10.319> that 00:07:10.430 --> 00:07:10.440 align:start position:0% waiting for that or waiting for that 00:07:10.440 --> 00:07:11.510 align:start position:0% waiting for that or waiting for that user 00:07:11.510 --> 00:07:11.520 align:start position:0% user 00:07:11.520 --> 00:07:14.189 align:start position:0% user base<00:07:12.520> okay<00:07:12.720> thank<00:07:12.879> you<00:07:13.560> is<00:07:13.680> there<00:07:13.840> another 00:07:14.189 --> 00:07:14.199 align:start position:0% base okay thank you is there another 00:07:14.199 --> 00:07:15.869 align:start position:0% base okay thank you is there another question<00:07:14.520> because<00:07:14.759> otherwise<00:07:15.080> I<00:07:15.400> another<00:07:15.639> one 00:07:15.869 --> 00:07:15.879 align:start position:0% question because otherwise I another one 00:07:15.879 --> 00:07:19.390 align:start position:0% question because otherwise I another one here<00:07:16.560> yes<00:07:16.759> there<00:07:16.840> are<00:07:17.000> others 00:07:19.390 --> 00:07:19.400 align:start position:0% here yes there are others 00:07:19.400 --> 00:07:23.230 align:start position:0% here yes there are others so<00:07:20.400> um<00:07:21.160> so<00:07:22.160> you<00:07:22.319> essentially<00:07:22.680> mentioned<00:07:23.039> that 00:07:23.230 --> 00:07:23.240 align:start position:0% so um so you essentially mentioned that 00:07:23.240 --> 00:07:25.629 align:start position:0% so um so you essentially mentioned that you<00:07:24.199> developers<00:07:24.680> should<00:07:24.919> focus<00:07:25.199> on<00:07:25.360> building 00:07:25.629 --> 00:07:25.639 align:start position:0% you developers should focus on building 00:07:25.639 --> 00:07:28.550 align:start position:0% you developers should focus on building a<00:07:25.800> product<00:07:26.120> that<00:07:26.280> the<00:07:26.400> market<00:07:26.720> wants<00:07:27.520> um<00:07:28.319> what 00:07:28.550 --> 00:07:28.560 align:start position:0% a product that the market wants um what 00:07:28.560 --> 00:07:31.629 align:start position:0% a product that the market wants um what makes<00:07:28.840> it<00:07:29.560> and<00:07:29.680> we<00:07:29.800> see<00:07:30.160> that<00:07:30.720> most<00:07:31.039> companies 00:07:31.629 --> 00:07:31.639 align:start position:0% makes it and we see that most companies 00:07:31.639 --> 00:07:33.710 align:start position:0% makes it and we see that most companies actually<00:07:32.639> have<00:07:32.840> are<00:07:33.000> having<00:07:33.199> a<00:07:33.360> hard<00:07:33.560> time 00:07:33.710 --> 00:07:33.720 align:start position:0% actually have are having a hard time 00:07:33.720 --> 00:07:36.990 align:start position:0% actually have are having a hard time doing<00:07:34.039> this<00:07:34.319> what<00:07:34.400> do<00:07:34.520> you<00:07:34.680> think<00:07:35.680> makes<00:07:35.960> it<00:07:36.400> so 00:07:36.990 --> 00:07:37.000 align:start position:0% doing this what do you think makes it so 00:07:37.000 --> 00:07:40.589 align:start position:0% doing this what do you think makes it so difficult<00:07:37.800> to<00:07:38.800> apply<00:07:39.319> that<00:07:39.599> very<00:07:40.160> easy 00:07:40.589 --> 00:07:40.599 align:start position:0% difficult to apply that very easy 00:07:40.599 --> 00:07:42.749 align:start position:0% difficult to apply that very easy fundamental<00:07:41.160> first<00:07:41.479> principle<00:07:41.960> thinking<00:07:42.639> I 00:07:42.749 --> 00:07:42.759 align:start position:0% fundamental first principle thinking I 00:07:42.759 --> 00:07:44.550 align:start position:0% fundamental first principle thinking I think<00:07:43.440> being<00:07:43.720> the<00:07:43.840> space<00:07:44.039> for<00:07:44.159> a<00:07:44.240> number<00:07:44.440> of 00:07:44.550 --> 00:07:44.560 align:start position:0% think being the space for a number of 00:07:44.560 --> 00:07:45.990 align:start position:0% think being the space for a number of years 00:07:45.990 --> 00:07:46.000 align:start position:0% years 00:07:46.000 --> 00:07:48.749 align:start position:0% years um<00:07:47.080> everyone<00:07:48.080> there's<00:07:48.280> there's<00:07:48.400> a<00:07:48.520> lot<00:07:48.639> of 00:07:48.749 --> 00:07:48.759 align:start position:0% um everyone there's there's a lot of 00:07:48.759 --> 00:07:50.990 align:start position:0% um everyone there's there's a lot of cases<00:07:49.080> where<00:07:49.240> people<00:07:49.440> aren't<00:07:49.879> working<00:07:50.879> uh 00:07:50.990 --> 00:07:51.000 align:start position:0% cases where people aren't working uh 00:07:51.000 --> 00:07:52.550 align:start position:0% cases where people aren't working uh deeply<00:07:51.400> enough<00:07:51.560> or<00:07:51.720> pinpoint<00:07:52.159> enough<00:07:52.319> on<00:07:52.440> a 00:07:52.550 --> 00:07:52.560 align:start position:0% deeply enough or pinpoint enough on a 00:07:52.560 --> 00:07:56.270 align:start position:0% deeply enough or pinpoint enough on a very<00:07:52.840> specific<00:07:53.639> issue<00:07:54.639> um<00:07:55.080> namely<00:07:55.599> that<00:07:56.080> good 00:07:56.270 --> 00:07:56.280 align:start position:0% very specific issue um namely that good 00:07:56.280 --> 00:07:57.350 align:start position:0% very specific issue um namely that good good<00:07:56.400> example<00:07:56.720> like<00:07:56.840> let's<00:07:57.000> let's<00:07:57.120> use<00:07:57.240> a 00:07:57.350 --> 00:07:57.360 align:start position:0% good example like let's let's use a 00:07:57.360 --> 00:07:59.029 align:start position:0% good example like let's let's use a hypothetical<00:07:57.800> of<00:07:57.919> like<00:07:58.000> social<00:07:58.280> protocols<00:07:58.879> or 00:07:59.029 --> 00:07:59.039 align:start position:0% hypothetical of like social protocols or 00:07:59.039 --> 00:08:00.270 align:start position:0% hypothetical of like social protocols or like<00:07:59.120> a<00:07:59.199> someone<00:07:59.560> building<00:07:59.759> a<00:07:59.840> chain<00:08:00.000> for<00:08:00.159> like 00:08:00.270 --> 00:08:00.280 align:start position:0% like a someone building a chain for like 00:08:00.280 --> 00:08:01.950 align:start position:0% like a someone building a chain for like all<00:08:00.400> the<00:08:00.479> social<00:08:00.800> protocols<00:08:01.639> they're 00:08:01.950 --> 00:08:01.960 align:start position:0% all the social protocols they're 00:08:01.960 --> 00:08:04.670 align:start position:0% all the social protocols they're thinking<00:08:02.400> mostly<00:08:03.120> about<00:08:04.120> this<00:08:04.199> is<00:08:04.400> again<00:08:04.560> a 00:08:04.670 --> 00:08:04.680 align:start position:0% thinking mostly about this is again a 00:08:04.680 --> 00:08:06.230 align:start position:0% thinking mostly about this is again a hypothetical<00:08:05.319> but<00:08:05.520> like<00:08:05.879> we're<00:08:06.000> going<00:08:06.120> to 00:08:06.230 --> 00:08:06.240 align:start position:0% hypothetical but like we're going to 00:08:06.240 --> 00:08:07.469 align:start position:0% hypothetical but like we're going to amass<00:08:06.560> all<00:08:06.680> the<00:08:06.759> social<00:08:07.000> protocols<00:08:07.360> they're 00:08:07.469 --> 00:08:07.479 align:start position:0% amass all the social protocols they're 00:08:07.479 --> 00:08:08.629 align:start position:0% amass all the social protocols they're going<00:08:07.599> to<00:08:07.639> be<00:08:07.720> using<00:08:07.919> our<00:08:08.080> chain<00:08:08.440> they 00:08:08.629 --> 00:08:08.639 align:start position:0% going to be using our chain they 00:08:08.639 --> 00:08:10.309 align:start position:0% going to be using our chain they different<00:08:08.879> clients<00:08:09.159> and<00:08:09.319> all<00:08:09.520> that<00:08:10.000> without 00:08:10.309 --> 00:08:10.319 align:start position:0% different clients and all that without 00:08:10.319 --> 00:08:12.189 align:start position:0% different clients and all that without building<00:08:10.720> the<00:08:10.919> very<00:08:11.199> specific<00:08:11.680> client 00:08:12.189 --> 00:08:12.199 align:start position:0% building the very specific client 00:08:12.199 --> 00:08:13.629 align:start position:0% building the very specific client themselves<00:08:12.520> and<00:08:12.680> saying<00:08:12.919> we're<00:08:13.039> going<00:08:13.120> to<00:08:13.280> be 00:08:13.629 --> 00:08:13.639 align:start position:0% themselves and saying we're going to be 00:08:13.639 --> 00:08:15.230 align:start position:0% themselves and saying we're going to be offering<00:08:14.039> this<00:08:14.240> experience<00:08:14.759> first<00:08:15.039> as<00:08:15.120> a 00:08:15.230 --> 00:08:15.240 align:start position:0% offering this experience first as a 00:08:15.240 --> 00:08:17.309 align:start position:0% offering this experience first as a first<00:08:15.520> class<00:08:15.800> citizen<00:08:16.560> they're<00:08:16.759> thinking<00:08:17.080> too 00:08:17.309 --> 00:08:17.319 align:start position:0% first class citizen they're thinking too 00:08:17.319 --> 00:08:19.749 align:start position:0% first class citizen they're thinking too much<00:08:17.560> about<00:08:18.199> offer<00:08:18.440> it<00:08:18.599> to<00:08:18.759> everyone<00:08:19.240> before 00:08:19.749 --> 00:08:19.759 align:start position:0% much about offer it to everyone before 00:08:19.759 --> 00:08:21.149 align:start position:0% much about offer it to everyone before let's<00:08:19.960> get<00:08:20.120> the<00:08:20.280> experience<00:08:20.800> right<00:08:21.000> and 00:08:21.149 --> 00:08:21.159 align:start position:0% let's get the experience right and 00:08:21.159 --> 00:08:23.670 align:start position:0% let's get the experience right and figure<00:08:21.479> out<00:08:21.840> how<00:08:21.919> to<00:08:22.080> then<00:08:22.240> open<00:08:22.479> it<00:08:22.680> up<00:08:23.479> and<00:08:23.599> I 00:08:23.670 --> 00:08:23.680 align:start position:0% figure out how to then open it up and I 00:08:23.680 --> 00:08:24.909 align:start position:0% figure out how to then open it up and I think<00:08:23.840> that's<00:08:24.120> been<00:08:24.280> a<00:08:24.400> part<00:08:24.520> of<00:08:24.639> the<00:08:24.720> thinking 00:08:24.909 --> 00:08:24.919 align:start position:0% think that's been a part of the thinking 00:08:24.919 --> 00:08:26.350 align:start position:0% think that's been a part of the thinking or<00:08:25.039> an<00:08:25.159> issue<00:08:25.360> with<00:08:25.479> the<00:08:25.560> thinking<00:08:25.800> for<00:08:25.960> a<00:08:26.080> long 00:08:26.350 --> 00:08:26.360 align:start position:0% or an issue with the thinking for a long 00:08:26.360 --> 00:08:28.430 align:start position:0% or an issue with the thinking for a long time<00:08:26.800> it's<00:08:27.000> ambitious<00:08:27.599> and<00:08:27.720> it's<00:08:27.919> very<00:08:28.199> like<00:08:28.319> a 00:08:28.430 --> 00:08:28.440 align:start position:0% time it's ambitious and it's very like a 00:08:28.440 --> 00:08:30.390 align:start position:0% time it's ambitious and it's very like a good<00:08:28.599> thing<00:08:28.879> overall<00:08:29.680> but<00:08:29.800> at<00:08:29.919> the<00:08:30.039> same<00:08:30.240> time 00:08:30.390 --> 00:08:30.400 align:start position:0% good thing overall but at the same time 00:08:30.400 --> 00:08:31.909 align:start position:0% good thing overall but at the same time it<00:08:30.520> becomes<00:08:31.080> difficult<00:08:31.199> to<00:08:31.440> provide<00:08:31.759> that 00:08:31.909 --> 00:08:31.919 align:start position:0% it becomes difficult to provide that 00:08:31.919 --> 00:08:33.509 align:start position:0% it becomes difficult to provide that very<00:08:32.120> narrow<00:08:32.519> experience<00:08:32.919> or<00:08:33.080> solve<00:08:33.360> that 00:08:33.509 --> 00:08:33.519 align:start position:0% very narrow experience or solve that 00:08:33.519 --> 00:08:35.230 align:start position:0% very narrow experience or solve that very<00:08:33.760> specific<00:08:34.240> problem<00:08:34.599> before<00:08:34.880> thinking 00:08:35.230 --> 00:08:35.240 align:start position:0% very specific problem before thinking 00:08:35.240 --> 00:08:36.670 align:start position:0% very specific problem before thinking too<00:08:35.479> widely<00:08:36.039> and<00:08:36.159> I<00:08:36.240> think<00:08:36.320> you<00:08:36.440> have<00:08:36.519> to 00:08:36.670 --> 00:08:36.680 align:start position:0% too widely and I think you have to 00:08:36.680 --> 00:08:38.469 align:start position:0% too widely and I think you have to balance<00:08:37.039> both<00:08:37.200> of<00:08:37.360> that<00:08:37.959> when<00:08:38.240> When 00:08:38.469 --> 00:08:38.479 align:start position:0% balance both of that when When 00:08:38.479 --> 00:08:41.800 align:start position:0% balance both of that when When developing<00:08:38.880> and<00:08:39.039> designing