WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:03.629 align:start position:0% [Music] 00:00:03.629 --> 00:00:03.639 align:start position:0% [Music] 00:00:03.639 --> 00:00:08.950 align:start position:0% [Music] Austin 00:00:08.950 --> 00:00:08.960 align:start position:0% 00:00:08.960 --> 00:00:14.350 align:start position:0% kibble<00:00:09.960> Rahul 00:00:14.350 --> 00:00:14.360 align:start position:0% 00:00:14.360 --> 00:00:17.940 align:start position:0% rumala<00:00:15.360> and<00:00:16.000> Romina 00:00:17.940 --> 00:00:17.950 align:start position:0% rumala and Romina 00:00:17.950 --> 00:00:20.710 align:start position:0% rumala and Romina [Applause] 00:00:20.710 --> 00:00:20.720 align:start position:0% [Applause] 00:00:20.720 --> 00:00:23.589 align:start position:0% [Applause] buo<00:00:21.720> thank<00:00:21.840> you<00:00:21.960> so<00:00:22.119> much<00:00:22.359> everyone<00:00:22.800> please<00:00:23.320> go 00:00:23.589 --> 00:00:23.599 align:start position:0% buo thank you so much everyone please go 00:00:23.599 --> 00:00:26.150 align:start position:0% buo thank you so much everyone please go ahead<00:00:24.320> and<00:00:24.840> thank<00:00:25.000> you<00:00:25.160> everyone<00:00:25.480> for<00:00:25.720> staying 00:00:26.150 --> 00:00:26.160 align:start position:0% ahead and thank you everyone for staying 00:00:26.160 --> 00:00:31.109 align:start position:0% ahead and thank you everyone for staying here<00:00:27.119> all<00:00:27.840> this<00:00:28.240> session 00:00:31.109 --> 00:00:31.119 align:start position:0% here all this session 00:00:31.119 --> 00:00:35.110 align:start position:0% here all this session okay<00:00:31.400> check<00:00:31.960> can<00:00:32.079> you<00:00:32.239> guys<00:00:32.399> hear<00:00:32.760> me<00:00:33.760> okay<00:00:34.559> sa 00:00:35.110 --> 00:00:35.120 align:start position:0% okay check can you guys hear me okay sa 00:00:35.120 --> 00:00:39.830 align:start position:0% okay check can you guys hear me okay sa C<00:00:35.480> Bangkok<00:00:36.480> Welcome<00:00:36.840> to<00:00:37.559> our<00:00:38.200> talk<00:00:38.520> or<00:00:38.840> panel 00:00:39.830 --> 00:00:39.840 align:start position:0% C Bangkok Welcome to our talk or panel 00:00:39.840 --> 00:00:41.389 align:start position:0% C Bangkok Welcome to our talk or panel uh<00:00:40.000> super<00:00:40.280> excited<00:00:40.640> to<00:00:40.719> be<00:00:40.879> here<00:00:41.120> thank<00:00:41.280> you 00:00:41.389 --> 00:00:41.399 align:start position:0% uh super excited to be here thank you 00:00:41.399 --> 00:00:43.790 align:start position:0% uh super excited to be here thank you for<00:00:41.840> uh<00:00:42.000> thank<00:00:42.160> you<00:00:42.239> to<00:00:42.879> ethereum<00:00:43.320> Foundation 00:00:43.790 --> 00:00:43.800 align:start position:0% for uh thank you to ethereum Foundation 00:00:43.800 --> 00:00:46.950 align:start position:0% for uh thank you to ethereum Foundation Devcon<00:00:44.360> for<00:00:44.719> having<00:00:45.000> us<00:00:45.559> first<00:00:45.760> of<00:00:45.879> all<00:00:46.120> so<00:00:46.559> we 00:00:46.950 --> 00:00:46.960 align:start position:0% Devcon for having us first of all so we 00:00:46.960 --> 00:00:50.350 align:start position:0% Devcon for having us first of all so we are<00:00:47.399> going<00:00:47.520> to<00:00:47.719> take<00:00:48.039> the<00:00:48.239> next<00:00:48.920> 45<00:00:49.520> minutes<00:00:49.920> to 00:00:50.350 --> 00:00:50.360 align:start position:0% are going to take the next 45 minutes to 00:00:50.360 --> 00:00:52.110 align:start position:0% are going to take the next 45 minutes to uh<00:00:50.480> talk<00:00:50.719> about<00:00:51.039> some<00:00:51.360> some<00:00:51.480> of<00:00:51.600> the<00:00:51.760> topics 00:00:52.110 --> 00:00:52.120 align:start position:0% uh talk about some some of the topics 00:00:52.120 --> 00:00:53.750 align:start position:0% uh talk about some some of the topics that<00:00:52.280> we<00:00:52.440> feel<00:00:52.760> super<00:00:53.079> passionate<00:00:53.480> about 00:00:53.750 --> 00:00:53.760 align:start position:0% that we feel super passionate about 00:00:53.760 --> 00:00:56.709 align:start position:0% that we feel super passionate about which<00:00:53.920> is<00:00:54.520> data<00:00:54.960> privacy<00:00:55.480> user<00:00:55.920> privacy<00:00:56.520> just 00:00:56.709 --> 00:00:56.719 align:start position:0% which is data privacy user privacy just 00:00:56.719 --> 00:01:00.229 align:start position:0% which is data privacy user privacy just users<00:00:57.399> and<00:00:57.800> product<00:00:58.719> in<00:00:58.879> general<00:00:59.600> so<00:01:00.039> with 00:01:00.229 --> 00:01:00.239 align:start position:0% users and product in general so with 00:01:00.239 --> 00:01:02.270 align:start position:0% users and product in general so with that<00:01:00.640> uh<00:01:00.760> I<00:01:00.840> just<00:01:00.960> want<00:01:01.079> to<00:01:01.199> introduce<00:01:01.680> myself 00:01:02.270 --> 00:01:02.280 align:start position:0% that uh I just want to introduce myself 00:01:02.280 --> 00:01:04.710 align:start position:0% that uh I just want to introduce myself my<00:01:02.480> name<00:01:02.680> is<00:01:02.920> Rahul<00:01:03.760> uh<00:01:03.879> I've<00:01:04.040> been<00:01:04.199> in<00:01:04.360> crypto 00:01:04.710 --> 00:01:04.720 align:start position:0% my name is Rahul uh I've been in crypto 00:01:04.720 --> 00:01:08.270 align:start position:0% my name is Rahul uh I've been in crypto for<00:01:04.879> a<00:01:05.040> while<00:01:05.439> I'm<00:01:05.720> at<00:01:05.880> currently<00:01:06.840> VP<00:01:07.240> at<00:01:07.520> safe 00:01:08.270 --> 00:01:08.280 align:start position:0% for a while I'm at currently VP at safe 00:01:08.280 --> 00:01:11.469 align:start position:0% for a while I'm at currently VP at safe uh<00:01:08.520> leading<00:01:09.000> product<00:01:09.320> engineering<00:01:10.320> and<00:01:10.880> uh 00:01:11.469 --> 00:01:11.479 align:start position:0% uh leading product engineering and uh 00:01:11.479 --> 00:01:14.630 align:start position:0% uh leading product engineering and uh today<00:01:12.240> we<00:01:12.960> are<00:01:13.680> essentially<00:01:14.159> with<00:01:14.400> these 00:01:14.630 --> 00:01:14.640 align:start position:0% today we are essentially with these 00:01:14.640 --> 00:01:16.830 align:start position:0% today we are essentially with these three<00:01:15.040> talented<00:01:15.560> individuals<00:01:16.360> which<00:01:16.560> I<00:01:16.640> will 00:01:16.830 --> 00:01:16.840 align:start position:0% three talented individuals which I will 00:01:16.840 --> 00:01:19.590 align:start position:0% three talented individuals which I will let<00:01:17.119> them<00:01:17.640> introduce<00:01:18.280> themselves<00:01:18.920> so<00:01:19.159> first 00:01:19.590 --> 00:01:19.600 align:start position:0% let them introduce themselves so first 00:01:19.600 --> 00:01:22.109 align:start position:0% let them introduce themselves so first uh<00:01:19.720> I<00:01:19.840> hand<00:01:20.000> it<00:01:20.119> off<00:01:20.320> to<00:01:20.759> Romina<00:01:21.759> yeah<00:01:21.920> hi 00:01:22.109 --> 00:01:22.119 align:start position:0% uh I hand it off to Romina yeah hi 00:01:22.119 --> 00:01:24.429 align:start position:0% uh I hand it off to Romina yeah hi Romina<00:01:22.640> bad<00:01:23.079> is<00:01:23.200> my<00:01:23.360> name<00:01:23.640> I'm<00:01:23.799> founder<00:01:24.240> of 00:01:24.429 --> 00:01:24.439 align:start position:0% Romina bad is my name I'm founder of 00:01:24.439 --> 00:01:27.670 align:start position:0% Romina bad is my name I'm founder of capital<00:01:25.479> we<00:01:25.600> are<00:01:25.799> an<00:01:26.320> onchain<00:01:26.960> risk<00:01:27.320> and 00:01:27.670 --> 00:01:27.680 align:start position:0% capital we are an onchain risk and 00:01:27.680 --> 00:01:31.190 align:start position:0% capital we are an onchain risk and investment<00:01:28.200> management<00:01:28.840> firm<00:01:29.759> um<00:01:30.000> um<00:01:30.920> yeah 00:01:31.190 --> 00:01:31.200 align:start position:0% investment management firm um um yeah 00:01:31.200 --> 00:01:33.710 align:start position:0% investment management firm um um yeah I've<00:01:31.320> been<00:01:31.479> in<00:01:31.640> the<00:01:31.799> space<00:01:32.040> since<00:01:32.520> 2017<00:01:33.520> and 00:01:33.710 --> 00:01:33.720 align:start position:0% I've been in the space since 2017 and 00:01:33.720 --> 00:01:35.749 align:start position:0% I've been in the space since 2017 and mostly<00:01:34.119> building<00:01:34.600> on<00:01:34.720> the<00:01:34.880> capital<00:01:35.280> market 00:01:35.749 --> 00:01:35.759 align:start position:0% mostly building on the capital market 00:01:35.759 --> 00:01:37.870 align:start position:0% mostly building on the capital market and<00:01:36.040> institutional 00:01:37.870 --> 00:01:37.880 align:start position:0% and institutional 00:01:37.880 --> 00:01:40.789 align:start position:0% and institutional side<00:01:38.880> all<00:01:39.000> right<00:01:39.200> hi<00:01:39.360> everyone<00:01:39.680> I'm<00:01:39.840> Austin<00:01:40.600> uh 00:01:40.789 --> 00:01:40.799 align:start position:0% side all right hi everyone I'm Austin uh 00:01:40.799 --> 00:01:43.590 align:start position:0% side all right hi everyone I'm Austin uh designer<00:01:41.159> at<00:01:41.439> Dune<00:01:42.439> um<00:01:43.119> we<00:01:43.240> have<00:01:43.360> another 00:01:43.590 --> 00:01:43.600 align:start position:0% designer at Dune um we have another 00:01:43.600 --> 00:01:45.429 align:start position:0% designer at Dune um we have another designer<00:01:43.920> in<00:01:44.040> the<00:01:44.119> audience<00:01:44.479> here<00:01:44.600> at<00:01:44.719> Dune<00:01:45.320> uh 00:01:45.429 --> 00:01:45.439 align:start position:0% designer in the audience here at Dune uh 00:01:45.439 --> 00:01:47.789 align:start position:0% designer in the audience here at Dune uh thank<00:01:45.600> you<00:01:45.680> for<00:01:45.960> joining<00:01:46.960> um<00:01:47.439> been<00:01:47.560> in<00:01:47.640> the 00:01:47.789 --> 00:01:47.799 align:start position:0% thank you for joining um been in the 00:01:47.799 --> 00:01:49.429 align:start position:0% thank you for joining um been in the space<00:01:48.000> for<00:01:48.079> a<00:01:48.159> while<00:01:48.439> been<00:01:48.560> designing<00:01:49.280> uh<00:01:49.360> in 00:01:49.429 --> 00:01:49.439 align:start position:0% space for a while been designing uh in 00:01:49.439 --> 00:01:51.830 align:start position:0% space for a while been designing uh in the<00:01:49.600> space<00:01:49.840> since<00:01:50.079> around<00:01:50.399> 2020<00:01:51.399> um<00:01:51.680> and 00:01:51.830 --> 00:01:51.840 align:start position:0% the space since around 2020 um and 00:01:51.840 --> 00:01:54.310 align:start position:0% the space since around 2020 um and hanging<00:01:52.119> out<00:01:52.360> as<00:01:52.439> a<00:01:52.600> participant<00:01:53.119> before<00:01:53.399> that 00:01:54.310 --> 00:01:54.320 align:start position:0% hanging out as a participant before that 00:01:54.320 --> 00:01:58.310 align:start position:0% hanging out as a participant before that so<00:01:55.320> and<00:01:55.640> hi<00:01:56.159> um<00:01:56.399> I'm<00:01:56.600> Alice<00:01:57.280> I'm<00:01:57.680> a<00:01:58.000> data 00:01:58.310 --> 00:01:58.320 align:start position:0% so and hi um I'm Alice I'm a data 00:01:58.320 --> 00:02:00.670 align:start position:0% so and hi um I'm Alice I'm a data analyst<00:01:58.759> at<00:01:59.000> safe<00:01:59.520> I<00:01:59.920> work<00:02:00.119> with<00:02:00.240> the<00:02:00.360> product 00:02:00.670 --> 00:02:00.680 align:start position:0% analyst at safe I work with the product 00:02:00.680 --> 00:02:02.749 align:start position:0% analyst at safe I work with the product team<00:02:00.960> to<00:02:01.119> help<00:02:01.360> them<00:02:01.840> understand<00:02:02.000> their<00:02:02.200> users 00:02:02.749 --> 00:02:02.759 align:start position:0% team to help them understand their users 00:02:02.759 --> 00:02:04.469 align:start position:0% team to help them understand their users build<00:02:03.079> features<00:02:03.560> that<00:02:03.759> respond<00:02:04.079> to<00:02:04.200> user 00:02:04.469 --> 00:02:04.479 align:start position:0% build features that respond to user 00:02:04.479 --> 00:02:07.190 align:start position:0% build features that respond to user needs<00:02:05.399> and<00:02:05.719> evaluate<00:02:06.200> the<00:02:06.360> impact<00:02:06.680> of<00:02:06.960> new 00:02:07.190 --> 00:02:07.200 align:start position:0% needs and evaluate the impact of new 00:02:07.200 --> 00:02:08.869 align:start position:0% needs and evaluate the impact of new features<00:02:07.600> that<00:02:07.759> we 00:02:08.869 --> 00:02:08.879 align:start position:0% features that we 00:02:08.879 --> 00:02:11.630 align:start position:0% features that we launch<00:02:09.879> um<00:02:10.599> and<00:02:10.840> I've<00:02:10.959> been<00:02:11.080> in<00:02:11.200> this<00:02:11.400> space 00:02:11.630 --> 00:02:11.640 align:start position:0% launch um and I've been in this space 00:02:11.640 --> 00:02:13.830 align:start position:0% launch um and I've been in this space for<00:02:11.840> about<00:02:12.360> a<00:02:12.520> couple<00:02:12.879> years<00:02:13.239> and<00:02:13.400> before<00:02:13.640> that 00:02:13.830 --> 00:02:13.840 align:start position:0% for about a couple years and before that 00:02:13.840 --> 00:02:17.470 align:start position:0% for about a couple years and before that I<00:02:13.959> was<00:02:14.400> working<00:02:15.400> um<00:02:15.959> for<00:02:16.160> the<00:02:16.319> UK<00:02:16.680> government 00:02:17.470 --> 00:02:17.480 align:start position:0% I was working um for the UK government 00:02:17.480 --> 00:02:20.270 align:start position:0% I was working um for the UK government with<00:02:17.840> policy<00:02:18.400> designers<00:02:19.120> and<00:02:19.319> also<00:02:19.680> product 00:02:20.270 --> 00:02:20.280 align:start position:0% with policy designers and also product 00:02:20.280 --> 00:02:22.070 align:start position:0% with policy designers and also product designers<00:02:20.800> to<00:02:20.959> do<00:02:21.160> exactly<00:02:21.560> the<00:02:21.680> same<00:02:21.879> thing 00:02:22.070 --> 00:02:22.080 align:start position:0% designers to do exactly the same thing 00:02:22.080 --> 00:02:24.150 align:start position:0% designers to do exactly the same thing building<00:02:22.440> for<00:02:22.640> users<00:02:22.959> and 00:02:24.150 --> 00:02:24.160 align:start position:0% building for users and 00:02:24.160 --> 00:02:26.750 align:start position:0% building for users and citizens<00:02:25.160> so<00:02:25.560> are<00:02:25.680> you<00:02:25.800> all<00:02:26.000> ready<00:02:26.200> to<00:02:26.519> talk 00:02:26.750 --> 00:02:26.760 align:start position:0% citizens so are you all ready to talk 00:02:26.760 --> 00:02:29.110 align:start position:0% citizens so are you all ready to talk about<00:02:27.160> users<00:02:27.640> and<00:02:27.879> data<00:02:28.160> and<00:02:28.360> privacy<00:02:28.760> and<00:02:28.920> all 00:02:29.110 --> 00:02:29.120 align:start position:0% about users and data and privacy and all 00:02:29.120 --> 00:02:32.110 align:start position:0% about users and data and privacy and all that<00:02:29.560> should<00:02:30.040> bang<00:02:31.040> let's<00:02:31.280> go<00:02:31.480> let's<00:02:31.680> go<00:02:31.879> let's 00:02:32.110 --> 00:02:32.120 align:start position:0% that should bang let's go let's go let's 00:02:32.120 --> 00:02:34.589 align:start position:0% that should bang let's go let's go let's go<00:02:32.360> all<00:02:32.560> right<00:02:33.480> so<00:02:33.680> firstly<00:02:34.120> I<00:02:34.200> just<00:02:34.319> want<00:02:34.440> to 00:02:34.589 --> 00:02:34.599 align:start position:0% go all right so firstly I just want to 00:02:34.599 --> 00:02:38.750 align:start position:0% go all right so firstly I just want to set<00:02:34.840> some<00:02:35.160> context<00:02:35.840> right<00:02:36.360> um<00:02:37.319> uh<00:02:37.480> so<00:02:38.200> product 00:02:38.750 --> 00:02:38.760 align:start position:0% set some context right um uh so product 00:02:38.760 --> 00:02:40.869 align:start position:0% set some context right um uh so product Discovery<00:02:39.319> we<00:02:39.519> call<00:02:39.760> this<00:02:40.040> a<00:02:40.319> process<00:02:40.760> you 00:02:40.869 --> 00:02:40.879 align:start position:0% Discovery we call this a process you 00:02:40.879 --> 00:02:43.309 align:start position:0% Discovery we call this a process you know<00:02:41.000> to<00:02:41.480> understand<00:02:41.640> users<00:02:42.159> problems<00:02:43.159> and 00:02:43.309 --> 00:02:43.319 align:start position:0% know to understand users problems and 00:02:43.319 --> 00:02:45.670 align:start position:0% know to understand users problems and using<00:02:43.680> that<00:02:43.840> knowledge<00:02:44.159> to<00:02:44.319> build<00:02:45.120> uh<00:02:45.400> the 00:02:45.670 --> 00:02:45.680 align:start position:0% using that knowledge to build uh the 00:02:45.680 --> 00:02:48.910 align:start position:0% using that knowledge to build uh the product<00:02:46.519> so<00:02:46.720> in<00:02:46.840> the<00:02:47.000> world<00:02:47.280> of<00:02:47.480> web<00:02:47.720> 3<00:02:48.319> where 00:02:48.910 --> 00:02:48.920 align:start position:0% product so in the world of web 3 where 00:02:48.920 --> 00:02:50.910 align:start position:0% product so in the world of web 3 where things<00:02:49.239> like<00:02:49.560> anonymity<00:02:50.200> and<00:02:50.440> privacy 00:02:50.910 --> 00:02:50.920 align:start position:0% things like anonymity and privacy 00:02:50.920 --> 00:02:53.270 align:start position:0% things like anonymity and privacy Prevail<00:02:51.800> the<00:02:51.959> question<00:02:52.280> is<00:02:52.599> that<00:02:53.000> how<00:02:53.120> can 00:02:53.270 --> 00:02:53.280 align:start position:0% Prevail the question is that how can 00:02:53.280 --> 00:02:55.509 align:start position:0% Prevail the question is that how can teams<00:02:53.760> identify<00:02:54.360> user<00:02:54.760> problems<00:02:55.200> user 00:02:55.509 --> 00:02:55.519 align:start position:0% teams identify user problems user 00:02:55.519 --> 00:02:57.949 align:start position:0% teams identify user problems user segments<00:02:56.319> and<00:02:56.519> collect<00:02:56.920> the<00:02:57.080> right<00:02:57.360> data<00:02:57.720> so 00:02:57.949 --> 00:02:57.959 align:start position:0% segments and collect the right data so 00:02:57.959 --> 00:03:01.270 align:start position:0% segments and collect the right data so to<00:02:58.400> understand<00:02:58.599> their<00:02:58.840> behaviors<00:03:00.000> so<00:03:00.519> as<00:03:00.760> we<00:03:01.200> I 00:03:01.270 --> 00:03:01.280 align:start position:0% to understand their behaviors so as we I 00:03:01.280 --> 00:03:03.470 align:start position:0% to understand their behaviors so as we I mean<00:03:01.440> we<00:03:01.560> heard<00:03:01.879> this<00:03:02.080> a<00:03:02.239> lot<00:03:02.480> today<00:03:02.879> as<00:03:03.000> we<00:03:03.159> aim 00:03:03.470 --> 00:03:03.480 align:start position:0% mean we heard this a lot today as we aim 00:03:03.480 --> 00:03:06.869 align:start position:0% mean we heard this a lot today as we aim to<00:03:04.000> uh<00:03:04.120> onboard<00:03:04.560> the<00:03:04.720> next<00:03:05.239> billion<00:03:06.239> uh<00:03:06.400> web3 00:03:06.869 --> 00:03:06.879 align:start position:0% to uh onboard the next billion uh web3 00:03:06.879 --> 00:03:09.789 align:start position:0% to uh onboard the next billion uh web3 users<00:03:07.519> so<00:03:08.280> the<00:03:08.519> question<00:03:08.920> really<00:03:09.239> becomes<00:03:09.680> how 00:03:09.789 --> 00:03:09.799 align:start position:0% users so the question really becomes how 00:03:09.799 --> 00:03:11.910 align:start position:0% users so the question really becomes how should<00:03:10.000> we<00:03:10.159> balance<00:03:10.599> building<00:03:11.080> user<00:03:11.480> Centric 00:03:11.910 --> 00:03:11.920 align:start position:0% should we balance building user Centric 00:03:11.920 --> 00:03:15.149 align:start position:0% should we balance building user Centric products<00:03:12.319> in<00:03:12.440> a<00:03:12.680> privacy<00:03:13.159> Centric<00:03:14.159> ecosystem 00:03:15.149 --> 00:03:15.159 align:start position:0% products in a privacy Centric ecosystem 00:03:15.159 --> 00:03:17.270 align:start position:0% products in a privacy Centric ecosystem and<00:03:15.599> with<00:03:15.879> this<00:03:16.120> panel<00:03:16.640> we<00:03:16.840> hope<00:03:17.040> to 00:03:17.270 --> 00:03:17.280 align:start position:0% and with this panel we hope to 00:03:17.280 --> 00:03:19.750 align:start position:0% and with this panel we hope to accomplish<00:03:17.840> touching<00:03:18.200> on<00:03:18.400> some<00:03:18.560> of<00:03:18.760> those<00:03:19.239> uh 00:03:19.750 --> 00:03:19.760 align:start position:0% accomplish touching on some of those uh 00:03:19.760 --> 00:03:23.550 align:start position:0% accomplish touching on some of those uh points<00:03:20.360> so<00:03:21.080> to<00:03:21.360> set<00:03:21.640> the<00:03:21.840> first<00:03:22.159> question<00:03:23.040> uh<00:03:23.480> I 00:03:23.550 --> 00:03:23.560 align:start position:0% points so to set the first question uh I 00:03:23.560 --> 00:03:25.789 align:start position:0% points so to set the first question uh I want<00:03:23.720> to<00:03:23.920> set<00:03:24.480> another<00:03:24.799> context<00:03:25.319> here<00:03:25.599> it's 00:03:25.789 --> 00:03:25.799 align:start position:0% want to set another context here it's 00:03:25.799 --> 00:03:30.030 align:start position:0% want to set another context here it's been<00:03:26.360> uh<00:03:26.879> 10<00:03:27.200> years<00:03:28.080> uh<00:03:28.439> since<00:03:28.879> uh<00:03:29.000> Devcon<00:03:29.480> zero 00:03:30.030 --> 00:03:30.040 align:start position:0% been uh 10 years uh since uh Devcon zero 00:03:30.040 --> 00:03:33.309 align:start position:0% been uh 10 years uh since uh Devcon zero which<00:03:30.159> started<00:03:30.560> in<00:03:30.920> uh<00:03:31.200> qub<00:03:31.799> Berlin<00:03:32.680> uh<00:03:32.959> right 00:03:33.309 --> 00:03:33.319 align:start position:0% which started in uh qub Berlin uh right 00:03:33.319 --> 00:03:35.990 align:start position:0% which started in uh qub Berlin uh right where<00:03:33.599> Romina<00:03:34.000> and<00:03:34.159> I<00:03:34.280> are<00:03:34.439> from<00:03:34.680> for<00:03:35.000> example 00:03:35.990 --> 00:03:36.000 align:start position:0% where Romina and I are from for example 00:03:36.000 --> 00:03:38.350 align:start position:0% where Romina and I are from for example uh<00:03:36.159> lot<00:03:36.400> has<00:03:36.560> changed<00:03:37.400> uh<00:03:37.760> lot<00:03:37.959> of<00:03:38.080> new 00:03:38.350 --> 00:03:38.360 align:start position:0% uh lot has changed uh lot of new 00:03:38.360 --> 00:03:40.589 align:start position:0% uh lot has changed uh lot of new products<00:03:38.879> lot<00:03:39.040> of<00:03:39.159> new<00:03:39.439> problems<00:03:40.000> lot<00:03:40.200> of<00:03:40.360> new 00:03:40.589 --> 00:03:40.599 align:start position:0% products lot of new problems lot of new 00:03:40.599 --> 00:03:44.509 align:start position:0% products lot of new problems lot of new users<00:03:41.319> and<00:03:41.879> uh<00:03:42.319> opportunities<00:03:43.040> as<00:03:43.200> well<00:03:44.000> and 00:03:44.509 --> 00:03:44.519 align:start position:0% users and uh opportunities as well and 00:03:44.519 --> 00:03:47.390 align:start position:0% users and uh opportunities as well and uh<00:03:44.760> so<00:03:45.480> it's<00:03:45.760> it's<00:03:45.959> super<00:03:46.239> nice<00:03:46.480> to<00:03:46.599> see<00:03:46.959> how 00:03:47.390 --> 00:03:47.400 align:start position:0% uh so it's it's super nice to see how 00:03:47.400 --> 00:03:48.869 align:start position:0% uh so it's it's super nice to see how things<00:03:47.599> have<00:03:47.760> changed<00:03:48.120> and<00:03:48.239> put<00:03:48.439> that<00:03:48.599> into 00:03:48.869 --> 00:03:48.879 align:start position:0% things have changed and put that into 00:03:48.879 --> 00:03:50.949 align:start position:0% things have changed and put that into context<00:03:49.439> right<00:03:49.959> so<00:03:50.159> kind<00:03:50.280> of<00:03:50.439> like<00:03:50.640> let's<00:03:50.840> have 00:03:50.949 --> 00:03:50.959 align:start position:0% context right so kind of like let's have 00:03:50.959 --> 00:03:52.949 align:start position:0% context right so kind of like let's have a<00:03:51.080> little<00:03:51.239> bit<00:03:51.360> of<00:03:51.480> an<00:03:51.640> ice<00:03:51.879> breaker<00:03:52.680> uh<00:03:52.840> just 00:03:52.949 --> 00:03:52.959 align:start position:0% a little bit of an ice breaker uh just 00:03:52.959 --> 00:03:54.750 align:start position:0% a little bit of an ice breaker uh just to<00:03:53.120> kind<00:03:53.239> of<00:03:53.360> get<00:03:53.519> the<00:03:53.760> discussions<00:03:54.319> going 00:03:54.750 --> 00:03:54.760 align:start position:0% to kind of get the discussions going 00:03:54.760 --> 00:03:57.149 align:start position:0% to kind of get the discussions going right<00:03:55.480> uh<00:03:55.599> so<00:03:55.799> this<00:03:55.920> is<00:03:56.000> a<00:03:56.159> question<00:03:56.480> for<00:03:57.000> all 00:03:57.149 --> 00:03:57.159 align:start position:0% right uh so this is a question for all 00:03:57.159 --> 00:04:00.710 align:start position:0% right uh so this is a question for all of<00:03:57.319> you<00:03:57.439> all<00:03:58.079> uh<00:03:58.680> what<00:03:58.879> type<00:03:59.120> of<00:03:59.239> a<00:03:59.400> crypto<00:04:00.040> user 00:04:00.710 --> 00:04:00.720 align:start position:0% of you all uh what type of a crypto user 00:04:00.720 --> 00:04:03.229 align:start position:0% of you all uh what type of a crypto user are<00:04:00.959> you<00:04:01.680> and<00:04:02.439> what<00:04:02.560> is<00:04:02.680> your<00:04:02.879> current 00:04:03.229 --> 00:04:03.239 align:start position:0% are you and what is your current 00:04:03.239 --> 00:04:06.509 align:start position:0% are you and what is your current relationship<00:04:03.879> with 00:04:06.509 --> 00:04:06.519 align:start position:0% 00:04:06.519 --> 00:04:09.589 align:start position:0% privacy<00:04:07.519> okay<00:04:07.959> I<00:04:08.079> can<00:04:08.280> start<00:04:08.680> so<00:04:09.159> I<00:04:09.239> think<00:04:09.439> I 00:04:09.589 --> 00:04:09.599 align:start position:0% privacy okay I can start so I think I 00:04:09.599 --> 00:04:12.509 align:start position:0% privacy okay I can start so I think I come<00:04:09.959> from<00:04:10.439> more<00:04:10.760> like<00:04:10.959> from<00:04:11.120> the<00:04:11.280> defi<00:04:11.959> side 00:04:12.509 --> 00:04:12.519 align:start position:0% come from more like from the defi side 00:04:12.519 --> 00:04:15.990 align:start position:0% come from more like from the defi side um<00:04:12.840> also<00:04:13.239> for<00:04:13.680> my<00:04:13.959> personal<00:04:14.599> uses<00:04:15.480> so<00:04:15.680> I'm<00:04:15.840> not 00:04:15.990 --> 00:04:16.000 align:start position:0% um also for my personal uses so I'm not 00:04:16.000 --> 00:04:20.990 align:start position:0% um also for my personal uses so I'm not so<00:04:16.239> much<00:04:16.880> um<00:04:17.519> using<00:04:18.160> the<00:04:18.680> social<00:04:19.519> aspect<00:04:20.199> of<00:04:20.799> uh 00:04:20.990 --> 00:04:21.000 align:start position:0% so much um using the social aspect of uh 00:04:21.000 --> 00:04:24.230 align:start position:0% so much um using the social aspect of uh the<00:04:21.199> projects<00:04:21.919> uh<00:04:22.040> that<00:04:22.240> have<00:04:22.400> been<00:04:22.639> built<00:04:23.600> but 00:04:24.230 --> 00:04:24.240 align:start position:0% the projects uh that have been built but 00:04:24.240 --> 00:04:27.830 align:start position:0% the projects uh that have been built but I<00:04:24.720> for<00:04:25.040> example<00:04:25.880> organize<00:04:26.400> my<00:04:26.600> wallets<00:04:27.240> like<00:04:27.600> I 00:04:27.830 --> 00:04:27.840 align:start position:0% I for example organize my wallets like I 00:04:27.840 --> 00:04:30.629 align:start position:0% I for example organize my wallets like I have<00:04:28.080> one<00:04:28.880> hot<00:04:29.120> wallet<00:04:29.440> that<00:04:29.560> is<00:04:29.880> basically<00:04:30.360> my 00:04:30.629 --> 00:04:30.639 align:start position:0% have one hot wallet that is basically my 00:04:30.639 --> 00:04:33.870 align:start position:0% have one hot wallet that is basically my avatar<00:04:31.400> or<00:04:31.560> it's<00:04:31.759> connected<00:04:32.320> to<00:04:32.840> my<00:04:33.160> Twitter 00:04:33.870 --> 00:04:33.880 align:start position:0% avatar or it's connected to my Twitter 00:04:33.880 --> 00:04:37.950 align:start position:0% avatar or it's connected to my Twitter handle.<00:04:34.880> e<00:04:35.600> and<00:04:36.440> uh<00:04:36.560> this<00:04:36.680> is<00:04:36.919> basically<00:04:37.600> where 00:04:37.950 --> 00:04:37.960 align:start position:0% handle. e and uh this is basically where 00:04:37.960 --> 00:04:41.110 align:start position:0% handle. e and uh this is basically where I<00:04:38.120> hold<00:04:38.840> just<00:04:39.160> like<00:04:39.440> some<00:04:39.800> assets<00:04:40.240> so<00:04:40.479> I<00:04:40.600> can 00:04:41.110 --> 00:04:41.120 align:start position:0% I hold just like some assets so I can 00:04:41.120 --> 00:04:43.629 align:start position:0% I hold just like some assets so I can pay<00:04:41.520> with<00:04:41.759> Dy<00:04:42.199> or<00:04:42.440> Stables<00:04:43.160> just<00:04:43.320> like<00:04:43.479> I 00:04:43.629 --> 00:04:43.639 align:start position:0% pay with Dy or Stables just like I 00:04:43.639 --> 00:04:45.950 align:start position:0% pay with Dy or Stables just like I always<00:04:43.880> have<00:04:44.160> like<00:04:44.360> a<00:04:44.520> 100<00:04:44.840> or2<00:04:45.199> 200<00:04:45.440> years<00:04:45.800> and 00:04:45.950 --> 00:04:45.960 align:start position:0% always have like a 100 or2 200 years and 00:04:45.960 --> 00:04:48.629 align:start position:0% always have like a 100 or2 200 years and some<00:04:46.120> stable<00:04:46.520> coins<00:04:47.199> have<00:04:47.360> some<00:04:47.560> nfts<00:04:48.400> and 00:04:48.629 --> 00:04:48.639 align:start position:0% some stable coins have some nfts and 00:04:48.639 --> 00:04:52.270 align:start position:0% some stable coins have some nfts and maybe<00:04:49.039> also<00:04:49.840> some<00:04:50.520> um<00:04:50.720> additional<00:04:51.440> eth<00:04:51.919> for 00:04:52.270 --> 00:04:52.280 align:start position:0% maybe also some um additional eth for 00:04:52.280 --> 00:04:56.029 align:start position:0% maybe also some um additional eth for for<00:04:52.560> gas<00:04:53.120> fees<00:04:54.120> um<00:04:54.440> so<00:04:54.800> this<00:04:54.919> is<00:04:55.199> the<00:04:55.560> the<00:04:55.680> one 00:04:56.029 --> 00:04:56.039 align:start position:0% for gas fees um so this is the the one 00:04:56.039 --> 00:04:58.950 align:start position:0% for gas fees um so this is the the one that<00:04:56.360> I<00:04:56.800> want<00:04:57.039> to<00:04:57.280> use<00:04:57.560> for<00:04:57.960> non-sensitive 00:04:58.950 --> 00:04:58.960 align:start position:0% that I want to use for non-sensitive 00:04:58.960 --> 00:05:01.390 align:start position:0% that I want to use for non-sensitive interactions<00:04:59.800> it's<00:05:00.000> also<00:05:00.560> public<00:05:01.039> right<00:05:01.240> like 00:05:01.390 --> 00:05:01.400 align:start position:0% interactions it's also public right like 00:05:01.400 --> 00:05:02.870 align:start position:0% interactions it's also public right like people<00:05:01.560> that<00:05:01.720> know<00:05:01.880> my<00:05:02.240> Twitter<00:05:02.560> name<00:05:02.759> they 00:05:02.870 --> 00:05:02.880 align:start position:0% people that know my Twitter name they 00:05:02.880 --> 00:05:05.230 align:start position:0% people that know my Twitter name they can<00:05:03.000> look<00:05:03.160> it<00:05:03.320> up<00:05:03.840> so<00:05:04.039> I'm<00:05:04.199> aware<00:05:04.479> about<00:05:04.800> that 00:05:05.230 --> 00:05:05.240 align:start position:0% can look it up so I'm aware about that 00:05:05.240 --> 00:05:08.670 align:start position:0% can look it up so I'm aware about that so<00:05:05.680> for<00:05:06.680> um<00:05:07.000> my<00:05:07.280> business<00:05:07.759> activities<00:05:08.360> I<00:05:08.479> then 00:05:08.670 --> 00:05:08.680 align:start position:0% so for um my business activities I then 00:05:08.680 --> 00:05:12.310 align:start position:0% so for um my business activities I then have<00:05:08.800> a<00:05:09.000> signer<00:05:10.000> just<00:05:10.240> to<00:05:10.639> sign<00:05:11.440> transactions 00:05:12.310 --> 00:05:12.320 align:start position:0% have a signer just to sign transactions 00:05:12.320 --> 00:05:13.909 align:start position:0% have a signer just to sign transactions in<00:05:12.479> the<00:05:12.680> companies<00:05:13.160> for<00:05:13.320> example<00:05:13.720> with<00:05:13.840> the 00:05:13.909 --> 00:05:13.919 align:start position:0% in the companies for example with the 00:05:13.919 --> 00:05:16.749 align:start position:0% in the companies for example with the multi<00:05:14.560> setup<00:05:15.039> so<00:05:15.280> it<00:05:15.440> always<00:05:15.759> has<00:05:16.039> like<00:05:16.280> a 00:05:16.749 --> 00:05:16.759 align:start position:0% multi setup so it always has like a 00:05:16.759 --> 00:05:20.110 align:start position:0% multi setup so it always has like a signature<00:05:17.600> deficit<00:05:18.600> um<00:05:18.800> it<00:05:19.039> manages<00:05:19.600> a<00:05:19.759> lot<00:05:19.919> of 00:05:20.110 --> 00:05:20.120 align:start position:0% signature deficit um it manages a lot of 00:05:20.120 --> 00:05:23.990 align:start position:0% signature deficit um it manages a lot of transactions<00:05:21.080> they<00:05:21.199> are<00:05:21.600> sensitive<00:05:22.600> um<00:05:23.560> but 00:05:23.990 --> 00:05:24.000 align:start position:0% transactions they are sensitive um but 00:05:24.000 --> 00:05:26.469 align:start position:0% transactions they are sensitive um but there's<00:05:24.360> there<00:05:24.479> are<00:05:24.600> no<00:05:24.919> assets<00:05:25.319> held<00:05:25.600> on<00:05:25.880> this 00:05:26.469 --> 00:05:26.479 align:start position:0% there's there are no assets held on this 00:05:26.479 --> 00:05:29.749 align:start position:0% there's there are no assets held on this um<00:05:26.800> it's<00:05:27.000> also<00:05:27.639> nice<00:05:27.880> for<00:05:28.080> me<00:05:28.280> to<00:05:28.680> keep<00:05:28.960> my<00:05:29.240> tax 00:05:29.749 --> 00:05:29.759 align:start position:0% um it's also nice for me to keep my tax 00:05:29.759 --> 00:05:31.710 align:start position:0% um it's also nice for me to keep my tax accounting<00:05:30.240> overhead<00:05:30.759> low<00:05:31.160> because<00:05:31.400> I<00:05:31.520> can 00:05:31.710 --> 00:05:31.720 align:start position:0% accounting overhead low because I can 00:05:31.720 --> 00:05:34.029 align:start position:0% accounting overhead low because I can basically<00:05:32.080> do<00:05:32.360> my<00:05:32.680> tax<00:05:32.960> filings<00:05:33.520> just<00:05:33.800> like 00:05:34.029 --> 00:05:34.039 align:start position:0% basically do my tax filings just like 00:05:34.039 --> 00:05:36.870 align:start position:0% basically do my tax filings just like with<00:05:34.199> one<00:05:34.440> C3<00:05:35.080> download<00:05:35.600> and<00:05:35.759> then<00:05:36.479> it's<00:05:36.639> more 00:05:36.870 --> 00:05:36.880 align:start position:0% with one C3 download and then it's more 00:05:36.880 --> 00:05:38.990 align:start position:0% with one C3 download and then it's more convenient<00:05:37.319> for<00:05:37.479> me<00:05:37.880> and<00:05:38.000> then<00:05:38.199> for<00:05:38.639> all<00:05:38.800> the 00:05:38.990 --> 00:05:39.000 align:start position:0% convenient for me and then for all the 00:05:39.000 --> 00:05:41.629 align:start position:0% convenient for me and then for all the other<00:05:39.560> assets<00:05:40.080> or<00:05:40.319> my<00:05:40.479> portfolio<00:05:41.000> composition 00:05:41.629 --> 00:05:41.639 align:start position:0% other assets or my portfolio composition 00:05:41.639 --> 00:05:44.070 align:start position:0% other assets or my portfolio composition and<00:05:41.759> I<00:05:41.919> have<00:05:42.160> like<00:05:42.319> a<00:05:42.479> dedicated<00:05:43.000> e<00:05:43.319> wallet<00:05:43.919> or 00:05:44.070 --> 00:05:44.080 align:start position:0% and I have like a dedicated e wallet or 00:05:44.080 --> 00:05:46.550 align:start position:0% and I have like a dedicated e wallet or I<00:05:44.160> have<00:05:44.319> a<00:05:44.440> wallet<00:05:44.720> on<00:05:44.960> another<00:05:45.319> chain<00:05:45.840> and<00:05:46.120> I 00:05:46.550 --> 00:05:46.560 align:start position:0% I have a wallet on another chain and I 00:05:46.560 --> 00:05:48.870 align:start position:0% I have a wallet on another chain and I yeah<00:05:46.960> basically<00:05:47.720> have<00:05:47.840> a<00:05:47.960> little<00:05:48.160> Excel<00:05:48.600> list 00:05:48.870 --> 00:05:48.880 align:start position:0% yeah basically have a little Excel list 00:05:48.880 --> 00:05:52.270 align:start position:0% yeah basically have a little Excel list to<00:05:49.080> keep<00:05:49.720> keep<00:05:49.919> an<00:05:50.080> overview<00:05:50.720> of<00:05:51.280> uh<00:05:51.880> my 00:05:52.270 --> 00:05:52.280 align:start position:0% to keep keep an overview of uh my 00:05:52.280 --> 00:05:54.390 align:start position:0% to keep keep an overview of uh my wallets<00:05:52.680> that<00:05:52.840> are<00:05:53.000> also<00:05:53.280> segregated<00:05:54.240> and 00:05:54.390 --> 00:05:54.400 align:start position:0% wallets that are also segregated and 00:05:54.400 --> 00:05:57.110 align:start position:0% wallets that are also segregated and they<00:05:54.520> are<00:05:54.720> also<00:05:54.960> funded<00:05:55.759> sometimes<00:05:56.199> from 00:05:57.110 --> 00:05:57.120 align:start position:0% they are also funded sometimes from 00:05:57.120 --> 00:05:58.950 align:start position:0% they are also funded sometimes from accounts<00:05:57.479> that<00:05:57.600> are<00:05:57.759> not<00:05:58.000> directly<00:05:58.520> connected 00:05:58.950 --> 00:05:58.960 align:start position:0% accounts that are not directly connected 00:05:58.960 --> 00:06:01.550 align:start position:0% accounts that are not directly connected to<00:05:59.120> my<00:05:59.280> other<00:05:59.720> to<00:05:59.919> address<00:06:00.319> so<00:06:00.680> there<00:06:00.880> is<00:06:01.160> like 00:06:01.550 --> 00:06:01.560 align:start position:0% to my other to address so there is like 00:06:01.560 --> 00:06:04.309 align:start position:0% to my other to address so there is like my<00:06:01.840> personal<00:06:02.400> privacy<00:06:03.400> approach<00:06:04.039> but<00:06:04.160> it's 00:06:04.309 --> 00:06:04.319 align:start position:0% my personal privacy approach but it's 00:06:04.319 --> 00:06:07.270 align:start position:0% my personal privacy approach but it's not<00:06:04.479> a<00:06:04.680> technical 00:06:07.270 --> 00:06:07.280 align:start position:0% 00:06:07.280 --> 00:06:09.189 align:start position:0% solution<00:06:08.280> all<00:06:08.400> right<00:06:08.560> so<00:06:08.720> I<00:06:08.800> think<00:06:08.960> that 00:06:09.189 --> 00:06:09.199 align:start position:0% solution all right so I think that 00:06:09.199 --> 00:06:11.870 align:start position:0% solution all right so I think that there's<00:06:09.840> different<00:06:10.199> buckets<00:06:11.199> uh<00:06:11.520> in<00:06:11.680> the 00:06:11.870 --> 00:06:11.880 align:start position:0% there's different buckets uh in the 00:06:11.880 --> 00:06:13.309 align:start position:0% there's different buckets uh in the space<00:06:12.160> I<00:06:12.240> mean<00:06:12.360> you<00:06:12.479> have<00:06:12.639> your<00:06:12.880> privacy 00:06:13.309 --> 00:06:13.319 align:start position:0% space I mean you have your privacy 00:06:13.319 --> 00:06:15.830 align:start position:0% space I mean you have your privacy purist<00:06:14.319> maybe<00:06:14.560> your<00:06:14.800> wallet<00:06:15.160> Wanderers<00:06:15.720> who 00:06:15.830 --> 00:06:15.840 align:start position:0% purist maybe your wallet Wanderers who 00:06:15.840 --> 00:06:17.629 align:start position:0% purist maybe your wallet Wanderers who are<00:06:15.960> willing<00:06:16.199> to<00:06:16.479> just<00:06:16.680> connect<00:06:17.160> willy-nilly 00:06:17.629 --> 00:06:17.639 align:start position:0% are willing to just connect willy-nilly 00:06:17.639 --> 00:06:20.469 align:start position:0% are willing to just connect willy-nilly um<00:06:18.639> and<00:06:18.720> then<00:06:18.880> maybe<00:06:19.080> in<00:06:19.160> the<00:06:19.280> midd<00:06:19.639> middle<00:06:20.319> uh 00:06:20.469 --> 00:06:20.479 align:start position:0% um and then maybe in the midd middle uh 00:06:20.479 --> 00:06:22.390 align:start position:0% um and then maybe in the midd middle uh utility<00:06:20.919> Seekers<00:06:21.360> I<00:06:21.440> think<00:06:21.639> I'm<00:06:21.840> a<00:06:22.000> utility 00:06:22.390 --> 00:06:22.400 align:start position:0% utility Seekers I think I'm a utility 00:06:22.400 --> 00:06:24.510 align:start position:0% utility Seekers I think I'm a utility Seeker<00:06:22.759> so<00:06:22.960> if<00:06:23.039> I<00:06:23.160> see<00:06:23.880> that<00:06:24.000> I<00:06:24.120> can<00:06:24.240> get<00:06:24.360> some 00:06:24.510 --> 00:06:24.520 align:start position:0% Seeker so if I see that I can get some 00:06:24.520 --> 00:06:26.070 align:start position:0% Seeker so if I see that I can get some clear<00:06:24.800> value<00:06:25.080> from<00:06:25.280> something<00:06:25.680> I'm<00:06:25.880> like 00:06:26.070 --> 00:06:26.080 align:start position:0% clear value from something I'm like 00:06:26.080 --> 00:06:28.670 align:start position:0% clear value from something I'm like happy<00:06:26.319> to<00:06:26.639> to<00:06:26.800> connect<00:06:27.120> and<00:06:27.280> share<00:06:28.240> and<00:06:28.520> in 00:06:28.670 --> 00:06:28.680 align:start position:0% happy to to connect and share and in 00:06:28.680 --> 00:06:31.589 align:start position:0% happy to to connect and share and in general<00:06:29.199> just<00:06:29.960> in<00:06:30.160> general<00:06:30.919> uh<00:06:31.199> you<00:06:31.319> know<00:06:31.520> I 00:06:31.589 --> 00:06:31.599 align:start position:0% general just in general uh you know I 00:06:31.599 --> 00:06:35.510 align:start position:0% general just in general uh you know I think<00:06:32.199> um<00:06:32.520> I'm<00:06:32.840> I'm<00:06:33.000> Pro<00:06:33.880> transparency<00:06:34.880> um<00:06:35.319> but 00:06:35.510 --> 00:06:35.520 align:start position:0% think um I'm I'm Pro transparency um but 00:06:35.520 --> 00:06:37.110 align:start position:0% think um I'm I'm Pro transparency um but also<00:06:35.759> when<00:06:35.840> it<00:06:36.000> comes<00:06:36.199> to<00:06:36.440> kind<00:06:36.560> of<00:06:36.680> financial 00:06:37.110 --> 00:06:37.120 align:start position:0% also when it comes to kind of financial 00:06:37.120 --> 00:06:38.950 align:start position:0% also when it comes to kind of financial activity<00:06:37.759> I<00:06:37.880> guess<00:06:38.080> I<00:06:38.160> was<00:06:38.319> brought<00:06:38.520> up<00:06:38.680> not<00:06:38.800> to 00:06:38.950 --> 00:06:38.960 align:start position:0% activity I guess I was brought up not to 00:06:38.960 --> 00:06:40.629 align:start position:0% activity I guess I was brought up not to really<00:06:39.160> talk<00:06:39.360> about<00:06:39.560> money<00:06:39.919> so<00:06:40.080> it's<00:06:40.240> strange 00:06:40.629 --> 00:06:40.639 align:start position:0% really talk about money so it's strange 00:06:40.639 --> 00:06:43.270 align:start position:0% really talk about money so it's strange to<00:06:41.400> initiate<00:06:41.880> a<00:06:42.039> digital<00:06:42.440> conversation<00:06:43.120> with 00:06:43.270 --> 00:06:43.280 align:start position:0% to initiate a digital conversation with 00:06:43.280 --> 00:06:45.550 align:start position:0% to initiate a digital conversation with your<00:06:43.639> like<00:06:44.000> uh<00:06:44.599> I<00:06:44.720> guess<00:06:44.919> like<00:06:45.080> Financial 00:06:45.550 --> 00:06:45.560 align:start position:0% your like uh I guess like Financial 00:06:45.560 --> 00:06:48.550 align:start position:0% your like uh I guess like Financial history<00:06:46.319> uh<00:06:46.400> so<00:06:46.599> maybe<00:06:47.160> uh<00:06:47.479> yeah<00:06:47.639> what<00:06:47.800> Romina 00:06:48.550 --> 00:06:48.560 align:start position:0% history uh so maybe uh yeah what Romina 00:06:48.560 --> 00:06:51.070 align:start position:0% history uh so maybe uh yeah what Romina mentions<00:06:49.039> kind<00:06:49.160> of<00:06:49.280> resonates<00:06:49.680> on<00:06:49.840> that<00:06:50.080> front 00:06:51.070 --> 00:06:51.080 align:start position:0% mentions kind of resonates on that front 00:06:51.080 --> 00:06:53.710 align:start position:0% mentions kind of resonates on that front um<00:06:51.800> but<00:06:52.199> uh<00:06:52.560> but<00:06:52.800> yeah<00:06:52.960> I<00:06:53.039> think<00:06:53.240> what<00:06:53.360> really 00:06:53.710 --> 00:06:53.720 align:start position:0% um but uh but yeah I think what really 00:06:53.720 --> 00:06:55.589 align:start position:0% um but uh but yeah I think what really inspired<00:06:54.120> me<00:06:54.240> to<00:06:54.400> get<00:06:54.560> into<00:06:54.800> the<00:06:55.000> space<00:06:55.319> was 00:06:55.589 --> 00:06:55.599 align:start position:0% inspired me to get into the space was 00:06:55.599 --> 00:06:57.710 align:start position:0% inspired me to get into the space was ownership<00:06:56.160> in<00:06:56.240> the<00:06:56.360> end<00:06:57.120> um<00:06:57.280> I<00:06:57.360> saw<00:06:57.560> that 00:06:57.710 --> 00:06:57.720 align:start position:0% ownership in the end um I saw that 00:06:57.720 --> 00:06:59.790 align:start position:0% ownership in the end um I saw that creative<00:06:58.120> people<00:06:58.479> could<00:06:58.919> uh<00:06:59.080> to<00:06:59.319> have<00:06:59.639> could 00:06:59.790 --> 00:06:59.800 align:start position:0% creative people could uh to have could 00:06:59.800 --> 00:07:01.390 align:start position:0% creative people could uh to have could have<00:06:59.960> ownership<00:07:00.759> you<00:07:00.879> could<00:07:01.039> have<00:07:01.199> more 00:07:01.390 --> 00:07:01.400 align:start position:0% have ownership you could have more 00:07:01.400 --> 00:07:03.110 align:start position:0% have ownership you could have more people<00:07:01.599> on<00:07:01.840> cap<00:07:02.080> tables<00:07:02.440> actually<00:07:02.680> owning 00:07:03.110 --> 00:07:03.120 align:start position:0% people on cap tables actually owning 00:07:03.120 --> 00:07:05.150 align:start position:0% people on cap tables actually owning parts<00:07:03.360> of<00:07:03.560> projects<00:07:03.919> and<00:07:04.120> businesses<00:07:05.000> so 00:07:05.150 --> 00:07:05.160 align:start position:0% parts of projects and businesses so 00:07:05.160 --> 00:07:06.390 align:start position:0% parts of projects and businesses so that's<00:07:05.319> what<00:07:05.479> inspired<00:07:05.840> me<00:07:05.919> to<00:07:06.000> get<00:07:06.120> into<00:07:06.280> the 00:07:06.390 --> 00:07:06.400 align:start position:0% that's what inspired me to get into the 00:07:06.400 --> 00:07:07.629 align:start position:0% that's what inspired me to get into the space<00:07:06.639> but<00:07:06.759> I<00:07:06.840> think<00:07:06.960> there<00:07:07.080> has<00:07:07.199> to<00:07:07.319> be<00:07:07.440> that 00:07:07.629 --> 00:07:07.639 align:start position:0% space but I think there has to be that 00:07:07.639 --> 00:07:09.070 align:start position:0% space but I think there has to be that value<00:07:07.919> exchange<00:07:08.240> so<00:07:08.360> I'd<00:07:08.520> say<00:07:08.680> I'm<00:07:08.800> a<00:07:08.960> a 00:07:09.070 --> 00:07:09.080 align:start position:0% value exchange so I'd say I'm a a 00:07:09.080 --> 00:07:11.390 align:start position:0% value exchange so I'd say I'm a a utility<00:07:09.440> Seeker<00:07:09.840> I'm<00:07:09.919> willing<00:07:10.199> to<00:07:11.080> uh<00:07:11.240> that's 00:07:11.390 --> 00:07:11.400 align:start position:0% utility Seeker I'm willing to uh that's 00:07:11.400 --> 00:07:13.150 align:start position:0% utility Seeker I'm willing to uh that's kind<00:07:11.479> of<00:07:11.599> my<00:07:11.720> take<00:07:11.840> on<00:07:12.080> privacy<00:07:12.440> I'm<00:07:12.599> happy<00:07:12.800> to 00:07:13.150 --> 00:07:13.160 align:start position:0% kind of my take on privacy I'm happy to 00:07:13.160 --> 00:07:15.909 align:start position:0% kind of my take on privacy I'm happy to to<00:07:13.400> commit<00:07:13.759> information<00:07:14.240> if<00:07:14.360> I<00:07:14.479> feel<00:07:14.800> if<00:07:14.919> I 00:07:15.909 --> 00:07:15.919 align:start position:0% to commit information if I feel if I 00:07:15.919 --> 00:07:18.510 align:start position:0% to commit information if I feel if I understand<00:07:16.160> the<00:07:16.280> value<00:07:16.560> exchange<00:07:17.039> there 00:07:18.510 --> 00:07:18.520 align:start position:0% understand the value exchange there 00:07:18.520 --> 00:07:21.110 align:start position:0% understand the value exchange there so<00:07:19.520> that<00:07:19.840> that's<00:07:20.039> quite<00:07:20.199> well<00:07:20.479> put<00:07:20.800> I'd<00:07:20.960> say 00:07:21.110 --> 00:07:21.120 align:start position:0% so that that's quite well put I'd say 00:07:21.120 --> 00:07:24.070 align:start position:0% so that that's quite well put I'd say I'm<00:07:21.280> a<00:07:21.440> utility<00:07:21.879> Seeker<00:07:22.240> on<00:07:22.400> that<00:07:22.560> point<00:07:23.280> um<00:07:23.960> as 00:07:24.070 --> 00:07:24.080 align:start position:0% I'm a utility Seeker on that point um as 00:07:24.080 --> 00:07:26.390 align:start position:0% I'm a utility Seeker on that point um as a<00:07:24.280> crypto<00:07:24.680> user<00:07:25.000> I'm<00:07:25.199> probably<00:07:25.479> one<00:07:25.599> of<00:07:25.759> your 00:07:26.390 --> 00:07:26.400 align:start position:0% a crypto user I'm probably one of your 00:07:26.400 --> 00:07:28.909 align:start position:0% a crypto user I'm probably one of your inactive<00:07:26.960> users<00:07:27.840> uh<00:07:28.000> I'm<00:07:28.160> one<00:07:28.360> that<00:07:28.639> puts 00:07:28.909 --> 00:07:28.919 align:start position:0% inactive users uh I'm one that puts 00:07:28.919 --> 00:07:30.869 align:start position:0% inactive users uh I'm one that puts money<00:07:29.199> in<00:07:29.560> but<00:07:29.720> never<00:07:29.919> takes<00:07:30.160> money<00:07:30.440> out<00:07:30.720> or 00:07:30.869 --> 00:07:30.879 align:start position:0% money in but never takes money out or 00:07:30.879 --> 00:07:32.430 align:start position:0% money in but never takes money out or doesn't<00:07:31.240> actually<00:07:31.560> really<00:07:31.800> engage<00:07:32.160> with<00:07:32.319> all 00:07:32.430 --> 00:07:32.440 align:start position:0% doesn't actually really engage with all 00:07:32.440 --> 00:07:34.510 align:start position:0% doesn't actually really engage with all the<00:07:32.560> products<00:07:32.879> that<00:07:33.000> we<00:07:33.160> have<00:07:33.319> out<00:07:33.520> there<00:07:34.280> just 00:07:34.510 --> 00:07:34.520 align:start position:0% the products that we have out there just 00:07:34.520 --> 00:07:36.469 align:start position:0% the products that we have out there just because<00:07:35.080> I<00:07:35.240> still<00:07:35.479> feel<00:07:35.800> like<00:07:35.960> the<00:07:36.080> learning 00:07:36.469 --> 00:07:36.479 align:start position:0% because I still feel like the learning 00:07:36.479 --> 00:07:38.629 align:start position:0% because I still feel like the learning curve<00:07:36.800> is<00:07:37.000> too<00:07:37.319> big<00:07:37.599> to<00:07:37.840> invest<00:07:38.160> and<00:07:38.319> I<00:07:38.440> don't 00:07:38.629 --> 00:07:38.639 align:start position:0% curve is too big to invest and I don't 00:07:38.639 --> 00:07:41.150 align:start position:0% curve is too big to invest and I don't have<00:07:38.759> the<00:07:38.960> patience<00:07:39.639> so<00:07:40.160> I<00:07:40.280> put<00:07:40.479> money<00:07:40.759> in<00:07:41.080> I 00:07:41.150 --> 00:07:41.160 align:start position:0% have the patience so I put money in I 00:07:41.160 --> 00:07:43.950 align:start position:0% have the patience so I put money in I don't<00:07:41.360> take<00:07:41.560> it<00:07:41.680> out<00:07:42.199> um<00:07:42.400> I<00:07:42.479> don't<00:07:42.879> really<00:07:43.199> do 00:07:43.950 --> 00:07:43.960 align:start position:0% don't take it out um I don't really do 00:07:43.960 --> 00:07:47.629 align:start position:0% don't take it out um I don't really do transactions<00:07:44.960> um<00:07:45.960> from<00:07:46.120> a<00:07:46.400> privacy<00:07:47.280> point<00:07:47.479> of 00:07:47.629 --> 00:07:47.639 align:start position:0% transactions um from a privacy point of 00:07:47.639 --> 00:07:50.390 align:start position:0% transactions um from a privacy point of view<00:07:48.520> my<00:07:48.759> personal<00:07:49.240> privacy<00:07:49.720> I<00:07:49.840> feel<00:07:50.039> like 00:07:50.390 --> 00:07:50.400 align:start position:0% view my personal privacy I feel like 00:07:50.400 --> 00:07:52.990 align:start position:0% view my personal privacy I feel like I've<00:07:51.400> not<00:07:51.639> really<00:07:51.919> thought<00:07:52.240> about<00:07:52.639> I<00:07:52.720> feel 00:07:52.990 --> 00:07:53.000 align:start position:0% I've not really thought about I feel 00:07:53.000 --> 00:07:55.110 align:start position:0% I've not really thought about I feel like<00:07:53.159> I<00:07:53.280> was<00:07:53.520> born<00:07:53.879> in<00:07:54.039> the<00:07:54.199> internet<00:07:54.639> age<00:07:54.960> and 00:07:55.110 --> 00:07:55.120 align:start position:0% like I was born in the internet age and 00:07:55.120 --> 00:07:58.189 align:start position:0% like I was born in the internet age and I<00:07:55.240> don't<00:07:55.479> really<00:07:56.080> care<00:07:56.479> how<00:07:56.720> people<00:07:57.000> use<00:07:57.960> my 00:07:58.189 --> 00:07:58.199 align:start position:0% I don't really care how people use my 00:07:58.199 --> 00:08:00.270 align:start position:0% I don't really care how people use my data<00:07:58.560> I<00:07:58.720> just<00:07:58.919> say 00:08:00.270 --> 00:08:00.280 align:start position:0% data I just say 00:08:00.280 --> 00:08:02.189 align:start position:0% data I just say that's<00:08:00.440> the<00:08:00.960> world<00:08:01.240> we<00:08:01.400> live<00:08:01.560> in<00:08:01.720> and<00:08:01.919> I've 00:08:02.189 --> 00:08:02.199 align:start position:0% that's the world we live in and I've 00:08:02.199 --> 00:08:03.869 align:start position:0% that's the world we live in and I've I've<00:08:02.360> got<00:08:02.520> to<00:08:02.800> that's<00:08:02.960> the<00:08:03.080> trade-off<00:08:03.520> I<00:08:03.639> make 00:08:03.869 --> 00:08:03.879 align:start position:0% I've got to that's the trade-off I make 00:08:03.879 --> 00:08:06.950 align:start position:0% I've got to that's the trade-off I make for<00:08:04.560> the<00:08:04.720> convenience<00:08:05.240> that<00:08:05.360> I<00:08:05.560> get<00:08:06.479> but<00:08:06.680> as<00:08:06.759> a 00:08:06.950 --> 00:08:06.960 align:start position:0% for the convenience that I get but as a 00:08:06.960 --> 00:08:08.670 align:start position:0% for the convenience that I get but as a data<00:08:07.199> analyst<00:08:07.720> especially<00:08:08.159> coming<00:08:08.400> from 00:08:08.670 --> 00:08:08.680 align:start position:0% data analyst especially coming from 00:08:08.680 --> 00:08:12.589 align:start position:0% data analyst especially coming from government<00:08:09.280> I<00:08:09.400> care<00:08:09.800> very<00:08:10.120> much<00:08:10.560> about<00:08:11.599> how 00:08:12.589 --> 00:08:12.599 align:start position:0% government I care very much about how 00:08:12.599 --> 00:08:15.070 align:start position:0% government I care very much about how the<00:08:12.759> company<00:08:13.240> that<00:08:13.360> I<00:08:13.520> work<00:08:13.840> with<00:08:14.479> leverages 00:08:15.070 --> 00:08:15.080 align:start position:0% the company that I work with leverages 00:08:15.080 --> 00:08:17.629 align:start position:0% the company that I work with leverages the<00:08:15.240> data<00:08:15.520> of<00:08:15.639> our<00:08:15.800> users<00:08:16.360> so<00:08:16.639> I'm<00:08:16.919> very 00:08:17.629 --> 00:08:17.639 align:start position:0% the data of our users so I'm very 00:08:17.639 --> 00:08:20.390 align:start position:0% the data of our users so I'm very privacy<00:08:18.120> focused<00:08:18.599> when<00:08:18.720> it<00:08:18.840> comes<00:08:19.159> to<00:08:20.159> our 00:08:20.390 --> 00:08:20.400 align:start position:0% privacy focused when it comes to our 00:08:20.400 --> 00:08:23.230 align:start position:0% privacy focused when it comes to our users<00:08:21.360> um<00:08:21.879> not<00:08:22.039> so<00:08:22.199> much<00:08:22.440> my 00:08:23.230 --> 00:08:23.240 align:start position:0% users um not so much my 00:08:23.240 --> 00:08:25.270 align:start position:0% users um not so much my data<00:08:24.240> yeah<00:08:24.400> that's<00:08:24.599> already<00:08:25.000> super 00:08:25.270 --> 00:08:25.280 align:start position:0% data yeah that's already super 00:08:25.280 --> 00:08:27.149 align:start position:0% data yeah that's already super interesting<00:08:25.800> because<00:08:26.039> we<00:08:26.199> have<00:08:26.440> like<00:08:26.720> very 00:08:27.149 --> 00:08:27.159 align:start position:0% interesting because we have like very 00:08:27.159 --> 00:08:30.350 align:start position:0% interesting because we have like very different<00:08:27.560> personas<00:08:28.400> of<00:08:28.720> how<00:08:29.560> we<00:08:29.759> use<00:08:30.159> and 00:08:30.350 --> 00:08:30.360 align:start position:0% different personas of how we use and 00:08:30.360 --> 00:08:32.029 align:start position:0% different personas of how we use and what<00:08:30.520> type<00:08:30.680> of<00:08:30.840> user<00:08:31.159> you<00:08:31.280> are<00:08:31.560> so<00:08:31.800> I<00:08:31.879> think 00:08:32.029 --> 00:08:32.039 align:start position:0% what type of user you are so I think 00:08:32.039 --> 00:08:34.269 align:start position:0% what type of user you are so I think it's<00:08:32.360> kind<00:08:32.479> of<00:08:32.640> like<00:08:32.760> a<00:08:33.080> excellent<00:08:33.599> stage<00:08:34.039> for 00:08:34.269 --> 00:08:34.279 align:start position:0% it's kind of like a excellent stage for 00:08:34.279 --> 00:08:36.670 align:start position:0% it's kind of like a excellent stage for the<00:08:34.479> next<00:08:34.760> question<00:08:35.279> which<00:08:35.440> I<00:08:35.560> want<00:08:35.680> to<00:08:35.919> ask 00:08:36.670 --> 00:08:36.680 align:start position:0% the next question which I want to ask 00:08:36.680 --> 00:08:39.110 align:start position:0% the next question which I want to ask Romina<00:08:37.680> uh<00:08:38.000> as<00:08:38.159> someone<00:08:38.440> who's<00:08:38.640> been<00:08:38.839> in<00:08:38.959> the 00:08:39.110 --> 00:08:39.120 align:start position:0% Romina uh as someone who's been in the 00:08:39.120 --> 00:08:42.509 align:start position:0% Romina uh as someone who's been in the industry<00:08:39.640> for<00:08:40.640> uh<00:08:41.080> quite<00:08:41.479> quite<00:08:41.640> a<00:08:41.760> long<00:08:42.000> time 00:08:42.509 --> 00:08:42.519 align:start position:0% industry for uh quite quite a long time 00:08:42.519 --> 00:08:45.110 align:start position:0% industry for uh quite quite a long time how<00:08:42.640> do<00:08:42.800> you<00:08:42.919> feel<00:08:43.360> like<00:08:43.560> the<00:08:43.719> users<00:08:44.200> of<00:08:44.959> our 00:08:45.110 --> 00:08:45.120 align:start position:0% how do you feel like the users of our 00:08:45.120 --> 00:08:47.310 align:start position:0% how do you feel like the users of our industry<00:08:45.600> has<00:08:45.720> changed<00:08:46.080> over<00:08:46.279> the<00:08:46.640> years<00:08:47.160> and 00:08:47.310 --> 00:08:47.320 align:start position:0% industry has changed over the years and 00:08:47.320 --> 00:08:49.990 align:start position:0% industry has changed over the years and how<00:08:47.519> has<00:08:47.760> this<00:08:48.399> affected<00:08:49.399> uh<00:08:49.720> the<00:08:49.920> the 00:08:49.990 --> 00:08:50.000 align:start position:0% how has this affected uh the the 00:08:50.000 --> 00:08:52.110 align:start position:0% how has this affected uh the the industry<00:08:50.360> in<00:08:50.560> general<00:08:51.560> yeah<00:08:51.680> so<00:08:51.880> at<00:08:51.959> the 00:08:52.110 --> 00:08:52.120 align:start position:0% industry in general yeah so at the 00:08:52.120 --> 00:08:54.350 align:start position:0% industry in general yeah so at the beginning<00:08:52.640> there<00:08:52.760> was<00:08:52.959> obviously<00:08:53.320> many 00:08:54.350 --> 00:08:54.360 align:start position:0% beginning there was obviously many 00:08:54.360 --> 00:08:57.670 align:start position:0% beginning there was obviously many infrastructure<00:08:55.360> um<00:08:55.720> or<00:08:56.519> um<00:08:56.760> tech<00:08:57.320> for 00:08:57.670 --> 00:08:57.680 align:start position:0% infrastructure um or um tech for 00:08:57.680 --> 00:08:59.910 align:start position:0% infrastructure um or um tech for managing<00:08:58.120> our<00:08:58.399> interactions<00:08:59.079> missing<00:08:59.640> so<00:08:59.800> at 00:08:59.910 --> 00:08:59.920 align:start position:0% managing our interactions missing so at 00:08:59.920 --> 00:09:01.470 align:start position:0% managing our interactions missing so at the<00:09:00.040> beginning<00:09:00.399> there<00:09:00.519> was<00:09:00.839> safe<00:09:01.160> wasn't 00:09:01.470 --> 00:09:01.480 align:start position:0% the beginning there was safe wasn't 00:09:01.480 --> 00:09:04.150 align:start position:0% the beginning there was safe wasn't around<00:09:02.000> yet<00:09:02.440> right<00:09:03.040> there<00:09:03.200> was<00:09:03.560> multi6 00:09:04.150 --> 00:09:04.160 align:start position:0% around yet right there was multi6 00:09:04.160 --> 00:09:06.790 align:start position:0% around yet right there was multi6 Solutions<00:09:04.680> have<00:09:04.920> just<00:09:05.120> started<00:09:05.920> to<00:09:06.120> be<00:09:06.360> built 00:09:06.790 --> 00:09:06.800 align:start position:0% Solutions have just started to be built 00:09:06.800 --> 00:09:10.509 align:start position:0% Solutions have just started to be built so<00:09:07.680> uh<00:09:07.800> my<00:09:07.920> first<00:09:08.200> wallet<00:09:08.600> was<00:09:08.880> uh<00:09:09.240> my<00:09:09.480> ether 00:09:10.509 --> 00:09:10.519 align:start position:0% so uh my first wallet was uh my ether 00:09:10.519 --> 00:09:15.670 align:start position:0% so uh my first wallet was uh my ether wallet<00:09:11.560> um<00:09:12.640> and<00:09:13.640> um<00:09:14.279> yeah<00:09:14.480> it<00:09:14.640> was<00:09:15.320> very 00:09:15.670 --> 00:09:15.680 align:start position:0% wallet um and um yeah it was very 00:09:15.680 --> 00:09:17.310 align:start position:0% wallet um and um yeah it was very cumbersome<00:09:16.240> you<00:09:16.360> had<00:09:16.519> to<00:09:16.680> basically<00:09:17.079> write 00:09:17.310 --> 00:09:17.320 align:start position:0% cumbersome you had to basically write 00:09:17.320 --> 00:09:19.750 align:start position:0% cumbersome you had to basically write down<00:09:17.640> every<00:09:18.240> every<00:09:18.560> step<00:09:18.959> of<00:09:19.200> how<00:09:19.360> you<00:09:19.480> would 00:09:19.750 --> 00:09:19.760 align:start position:0% down every every step of how you would 00:09:19.760 --> 00:09:22.990 align:start position:0% down every every step of how you would interact<00:09:20.399> or<00:09:20.600> to<00:09:20.800> to<00:09:20.959> keep<00:09:21.120> an<00:09:21.320> overview<00:09:22.079> so<00:09:22.680> do 00:09:22.990 --> 00:09:23.000 align:start position:0% interact or to to keep an overview so do 00:09:23.000 --> 00:09:27.550 align:start position:0% interact or to to keep an overview so do you<00:09:23.399> X<00:09:24.000> um<00:09:24.360> has<00:09:24.720> been<00:09:25.560> um<00:09:25.920> massively<00:09:26.800> upgraded 00:09:27.550 --> 00:09:27.560 align:start position:0% you X um has been um massively upgraded 00:09:27.560 --> 00:09:29.430 align:start position:0% you X um has been um massively upgraded I<00:09:27.680> think<00:09:27.880> we<00:09:28.120> actually<00:09:28.440> also<00:09:28.959> sometimes<00:09:29.200> have 00:09:29.430 --> 00:09:29.440 align:start position:0% I think we actually also sometimes have 00:09:29.440 --> 00:09:33.590 align:start position:0% I think we actually also sometimes have have<00:09:29.640> better<00:09:30.640> ux<00:09:31.240> for<00:09:31.640> certain<00:09:32.240> aspects<00:09:32.880> when 00:09:33.590 --> 00:09:33.600 align:start position:0% have better ux for certain aspects when 00:09:33.600 --> 00:09:35.949 align:start position:0% have better ux for certain aspects when we<00:09:33.800> think<00:09:34.040> about<00:09:34.360> our<00:09:34.760> websites<00:09:35.519> or<00:09:35.680> you<00:09:35.760> know 00:09:35.949 --> 00:09:35.959 align:start position:0% we think about our websites or you know 00:09:35.959 --> 00:09:38.430 align:start position:0% we think about our websites or you know like<00:09:36.240> the<00:09:36.640> the<00:09:37.000> when<00:09:37.120> we<00:09:37.360> connect<00:09:37.680> our<00:09:37.959> wallets 00:09:38.430 --> 00:09:38.440 align:start position:0% like the the when we connect our wallets 00:09:38.440 --> 00:09:42.829 align:start position:0% like the the when we connect our wallets all<00:09:38.720> that<00:09:39.000> part<00:09:39.279> I<00:09:39.360> find<00:09:39.600> this<00:09:40.040> great<00:09:41.040> but<00:09:41.839> um 00:09:42.829 --> 00:09:42.839 align:start position:0% all that part I find this great but um 00:09:42.839 --> 00:09:45.030 align:start position:0% all that part I find this great but um yeah<00:09:43.240> so<00:09:43.519> we<00:09:43.600> saw<00:09:43.880> the<00:09:44.000> shift<00:09:44.279> from<00:09:44.440> a<00:09:44.680> rather 00:09:45.030 --> 00:09:45.040 align:start position:0% yeah so we saw the shift from a rather 00:09:45.040 --> 00:09:48.110 align:start position:0% yeah so we saw the shift from a rather developer<00:09:45.720> focused<00:09:46.240> ux<00:09:46.720> or<00:09:46.920> also<00:09:47.320> the<00:09:47.560> design 00:09:48.110 --> 00:09:48.120 align:start position:0% developer focused ux or also the design 00:09:48.120 --> 00:09:50.470 align:start position:0% developer focused ux or also the design Styles<00:09:48.600> so<00:09:48.800> some<00:09:49.120> projects<00:09:49.519> you<00:09:49.720> still<00:09:50.000> see 00:09:50.470 --> 00:09:50.480 align:start position:0% Styles so some projects you still see 00:09:50.480 --> 00:09:53.350 align:start position:0% Styles so some projects you still see that<00:09:50.839> they<00:09:51.040> use<00:09:51.320> Font<00:09:51.760> Styles<00:09:52.320> like<00:09:52.839> you<00:09:53.000> would 00:09:53.350 --> 00:09:53.360 align:start position:0% that they use Font Styles like you would 00:09:53.360 --> 00:09:57.470 align:start position:0% that they use Font Styles like you would have<00:09:53.600> in<00:09:53.720> a<00:09:53.959> coding<00:09:54.640> terminal<00:09:55.640> or<00:09:56.360> just<00:09:56.640> like 00:09:57.470 --> 00:09:57.480 align:start position:0% have in a coding terminal or just like 00:09:57.480 --> 00:09:59.670 align:start position:0% have in a coding terminal or just like they<00:09:57.720> also<00:09:58.000> design<00:09:58.360> their<00:09:58.640> products<00:09:59.160> how<00:09:59.560> a 00:09:59.670 --> 00:09:59.680 align:start position:0% they also design their products how a 00:09:59.680 --> 00:10:02.350 align:start position:0% they also design their products how a terminal<00:10:00.200> is<00:10:00.360> structured<00:10:00.959> for<00:10:01.200> example<00:10:01.920> but 00:10:02.350 --> 00:10:02.360 align:start position:0% terminal is structured for example but 00:10:02.360 --> 00:10:04.670 align:start position:0% terminal is structured for example but you<00:10:02.480> see<00:10:02.720> that<00:10:02.959> less<00:10:03.160> and<00:10:03.399> less<00:10:03.800> and<00:10:04.000> projects 00:10:04.670 --> 00:10:04.680 align:start position:0% you see that less and less and projects 00:10:04.680 --> 00:10:08.030 align:start position:0% you see that less and less and projects sometimes<00:10:05.360> uh<00:10:05.760> pivot<00:10:06.120> a<00:10:06.240> bit<00:10:06.519> there<00:10:07.120> um<00:10:07.480> ux 00:10:08.030 --> 00:10:08.040 align:start position:0% sometimes uh pivot a bit there um ux 00:10:08.040 --> 00:10:11.269 align:start position:0% sometimes uh pivot a bit there um ux designs<00:10:08.600> or<00:10:08.800> the<00:10:08.959> flows<00:10:09.920> tailored<00:10:10.519> to<00:10:11.079> their 00:10:11.269 --> 00:10:11.279 align:start position:0% designs or the flows tailored to their 00:10:11.279 --> 00:10:15.069 align:start position:0% designs or the flows tailored to their users<00:10:12.160> when<00:10:12.519> they<00:10:13.480> got<00:10:13.880> learned<00:10:14.440> more<00:10:14.800> about 00:10:15.069 --> 00:10:15.079 align:start position:0% users when they got learned more about 00:10:15.079 --> 00:10:17.470 align:start position:0% users when they got learned more about them<00:10:15.360> over<00:10:15.519> the<00:10:15.640> course<00:10:15.880> of<00:10:16.040> the<00:10:16.240> time<00:10:17.120> but 00:10:17.470 --> 00:10:17.480 align:start position:0% them over the course of the time but 00:10:17.480 --> 00:10:19.829 align:start position:0% them over the course of the time but some<00:10:17.800> projects<00:10:18.160> are<00:10:18.320> also<00:10:18.680> kind<00:10:18.920> of<00:10:19.160> dogmatic 00:10:19.829 --> 00:10:19.839 align:start position:0% some projects are also kind of dogmatic 00:10:19.839 --> 00:10:22.990 align:start position:0% some projects are also kind of dogmatic and<00:10:20.000> stick<00:10:20.360> to<00:10:21.120> a<00:10:21.360> rather<00:10:21.640> cumbersome 00:10:22.990 --> 00:10:23.000 align:start position:0% and stick to a rather cumbersome 00:10:23.000 --> 00:10:27.310 align:start position:0% and stick to a rather cumbersome ux<00:10:24.000> uh<00:10:24.160> one<00:10:24.440> that<00:10:25.000> was<00:10:26.000> um<00:10:26.240> keeping<00:10:26.720> quite 00:10:27.310 --> 00:10:27.320 align:start position:0% ux uh one that was um keeping quite 00:10:27.320 --> 00:10:32.470 align:start position:0% ux uh one that was um keeping quite attached<00:10:28.320> uh<00:10:28.440> to<00:10:28.839> their<00:10:29.360> terrible<00:10:30.240> um<00:10:31.000> '90s<00:10:31.480> ux 00:10:32.470 --> 00:10:32.480 align:start position:0% attached uh to their terrible um '90s ux 00:10:32.480 --> 00:10:35.230 align:start position:0% attached uh to their terrible um '90s ux was<00:10:32.760> cury<00:10:33.560> at<00:10:33.680> the<00:10:33.880> beginning<00:10:34.600> um<00:10:34.880> I<00:10:35.000> guess 00:10:35.230 --> 00:10:35.240 align:start position:0% was cury at the beginning um I guess 00:10:35.240 --> 00:10:37.710 align:start position:0% was cury at the beginning um I guess many<00:10:35.440> of<00:10:35.600> you<00:10:35.920> remember<00:10:36.920> basically<00:10:37.399> looked 00:10:37.710 --> 00:10:37.720 align:start position:0% many of you remember basically looked 00:10:37.720 --> 00:10:39.790 align:start position:0% many of you remember basically looked like<00:10:37.959> Windows<00:10:38.680> uh 00:10:39.790 --> 00:10:39.800 align:start position:0% like Windows uh 00:10:39.800 --> 00:10:43.230 align:start position:0% like Windows uh 95<00:10:40.800> um<00:10:41.560> yeah<00:10:42.440> but<00:10:42.560> then<00:10:42.720> there<00:10:42.839> were<00:10:43.000> for 00:10:43.230 --> 00:10:43.240 align:start position:0% 95 um yeah but then there were for 00:10:43.240 --> 00:10:46.350 align:start position:0% 95 um yeah but then there were for example<00:10:43.760> nft<00:10:44.320> mint<00:10:44.560> and<00:10:44.760> cream<00:10:45.360> experiences 00:10:46.350 --> 00:10:46.360 align:start position:0% example nft mint and cream experiences 00:10:46.360 --> 00:10:48.110 align:start position:0% example nft mint and cream experiences where<00:10:46.560> you<00:10:46.760> could<00:10:47.240> like<00:10:47.440> with<00:10:47.600> a<00:10:47.720> mini 00:10:48.110 --> 00:10:48.120 align:start position:0% where you could like with a mini 00:10:48.120 --> 00:10:50.350 align:start position:0% where you could like with a mini computer<00:10:48.720> set<00:10:49.200> like<00:10:49.399> the<00:10:49.519> features<00:10:50.000> of<00:10:50.240> the 00:10:50.350 --> 00:10:50.360 align:start position:0% computer set like the features of the 00:10:50.360 --> 00:10:52.829 align:start position:0% computer set like the features of the nft<00:10:50.920> or<00:10:51.079> the<00:10:51.240> Avatar<00:10:51.680> you<00:10:51.760> wanted<00:10:52.040> to<00:10:52.240> M<00:10:52.519> so<00:10:52.720> you 00:10:52.829 --> 00:10:52.839 align:start position:0% nft or the Avatar you wanted to M so you 00:10:52.839 --> 00:10:55.269 align:start position:0% nft or the Avatar you wanted to M so you could<00:10:53.079> basically<00:10:53.959> set<00:10:54.279> the<00:10:54.440> metadata 00:10:55.269 --> 00:10:55.279 align:start position:0% could basically set the metadata 00:10:55.279 --> 00:10:57.590 align:start position:0% could basically set the metadata function<00:10:56.040> and<00:10:56.160> then<00:10:56.360> the<00:10:56.519> metadata<00:10:57.200> was<00:10:57.399> then 00:10:57.590 --> 00:10:57.600 align:start position:0% function and then the metadata was then 00:10:57.600 --> 00:11:00.430 align:start position:0% function and then the metadata was then giving<00:10:57.920> you<00:10:58.200> for<00:10:58.480> example<00:10:59.360> a<00:10:59.480> feature<00:10:59.920> card<00:11:00.279> of 00:11:00.430 --> 00:11:00.440 align:start position:0% giving you for example a feature card of 00:11:00.440 --> 00:11:02.350 align:start position:0% giving you for example a feature card of the<00:11:00.639> Avatar<00:11:01.079> or<00:11:01.200> the<00:11:01.320> Persona<00:11:01.880> that<00:11:02.000> you<00:11:02.160> have 00:11:02.350 --> 00:11:02.360 align:start position:0% the Avatar or the Persona that you have 00:11:02.360 --> 00:11:05.150 align:start position:0% the Avatar or the Persona that you have been<00:11:02.519> minted<00:11:02.959> and<00:11:03.120> that<00:11:03.279> was<00:11:04.040> amazing<00:11:04.920> so 00:11:05.150 --> 00:11:05.160 align:start position:0% been minted and that was amazing so 00:11:05.160 --> 00:11:07.190 align:start position:0% been minted and that was amazing so there<00:11:05.320> have<00:11:05.519> been<00:11:05.720> some<00:11:06.200> great<00:11:06.519> Solutions 00:11:07.190 --> 00:11:07.200 align:start position:0% there have been some great Solutions 00:11:07.200 --> 00:11:09.710 align:start position:0% there have been some great Solutions pioneered<00:11:08.079> now<00:11:08.279> we<00:11:08.440> just<00:11:08.639> need<00:11:08.880> them<00:11:09.040> to<00:11:09.200> be 00:11:09.710 --> 00:11:09.720 align:start position:0% pioneered now we just need them to be 00:11:09.720 --> 00:11:14.150 align:start position:0% pioneered now we just need them to be adopted<00:11:10.440> in<00:11:10.680> the<00:11:10.880> big<00:11:11.279> apps<00:11:11.880> or<00:11:12.880> um<00:11:13.480> yeah 00:11:14.150 --> 00:11:14.160 align:start position:0% adopted in the big apps or um yeah 00:11:14.160 --> 00:11:17.710 align:start position:0% adopted in the big apps or um yeah chains<00:11:14.600> that<00:11:14.760> we<00:11:14.880> are<00:11:15.120> using<00:11:16.120> yeah<00:11:17.120> so<00:11:17.399> I<00:11:17.480> think 00:11:17.710 --> 00:11:17.720 align:start position:0% chains that we are using yeah so I think 00:11:17.720 --> 00:11:20.389 align:start position:0% chains that we are using yeah so I think that's<00:11:18.160> that's<00:11:18.399> interesting<00:11:19.000> and<00:11:19.399> uh<00:11:19.959> also 00:11:20.389 --> 00:11:20.399 align:start position:0% that's that's interesting and uh also 00:11:20.399 --> 00:11:23.430 align:start position:0% that's that's interesting and uh also like<00:11:20.720> I<00:11:20.880> remember<00:11:21.680> uh<00:11:21.839> the<00:11:22.040> last<00:11:22.320> time<00:11:23.000> uh<00:11:23.360> I 00:11:23.430 --> 00:11:23.440 align:start position:0% like I remember uh the last time uh I 00:11:23.440 --> 00:11:25.990 align:start position:0% like I remember uh the last time uh I was<00:11:23.680> in<00:11:24.160> Devcon<00:11:24.760> Prague<00:11:25.160> for<00:11:25.399> example<00:11:25.800> I<00:11:25.880> was 00:11:25.990 --> 00:11:26.000 align:start position:0% was in Devcon Prague for example I was 00:11:26.000 --> 00:11:28.069 align:start position:0% was in Devcon Prague for example I was building<00:11:26.360> my<00:11:26.519> first<00:11:26.839> company<00:11:27.720> and<00:11:27.839> I<00:11:27.920> was 00:11:28.069 --> 00:11:28.079 align:start position:0% building my first company and I was 00:11:28.079 --> 00:11:30.790 align:start position:0% building my first company and I was talking<00:11:28.360> to<00:11:28.959> the<00:11:29.320> users<00:11:29.760> there<00:11:30.040> you<00:11:30.160> know<00:11:30.440> like 00:11:30.790 --> 00:11:30.800 align:start position:0% talking to the users there you know like 00:11:30.800 --> 00:11:32.750 align:start position:0% talking to the users there you know like just<00:11:31.000> asking<00:11:31.360> how<00:11:31.519> should<00:11:31.680> we<00:11:31.839> build<00:11:32.160> this<00:11:32.440> and 00:11:32.750 --> 00:11:32.760 align:start position:0% just asking how should we build this and 00:11:32.760 --> 00:11:34.710 align:start position:0% just asking how should we build this and uh<00:11:33.079> one<00:11:33.240> of<00:11:33.360> the<00:11:33.480> feedbacks<00:11:34.000> I<00:11:34.079> have<00:11:34.440> received 00:11:34.710 --> 00:11:34.720 align:start position:0% uh one of the feedbacks I have received 00:11:34.720 --> 00:11:36.870 align:start position:0% uh one of the feedbacks I have received is<00:11:35.120> uh<00:11:35.320> that<00:11:35.959> uh<00:11:36.079> if<00:11:36.160> you're<00:11:36.360> building<00:11:36.680> in 00:11:36.870 --> 00:11:36.880 align:start position:0% is uh that uh if you're building in 00:11:36.880 --> 00:11:39.150 align:start position:0% is uh that uh if you're building in crypto<00:11:37.720> you<00:11:37.839> should<00:11:38.079> be<00:11:38.240> building<00:11:38.560> for<00:11:38.760> crypto 00:11:39.150 --> 00:11:39.160 align:start position:0% crypto you should be building for crypto 00:11:39.160 --> 00:11:40.470 align:start position:0% crypto you should be building for crypto users 00:11:40.470 --> 00:11:40.480 align:start position:0% users 00:11:40.480 --> 00:11:42.990 align:start position:0% users first<00:11:41.480> so<00:11:41.680> let<00:11:41.839> that<00:11:41.959> sink<00:11:42.240> in<00:11:42.480> right<00:11:42.720> like 00:11:42.990 --> 00:11:43.000 align:start position:0% first so let that sink in right like 00:11:43.000 --> 00:11:45.629 align:start position:0% first so let that sink in right like that<00:11:43.160> was<00:11:43.440> the<00:11:43.800> a<00:11:44.040> very<00:11:44.360> maximalist<00:11:45.079> belief 00:11:45.629 --> 00:11:45.639 align:start position:0% that was the a very maximalist belief 00:11:45.639 --> 00:11:48.230 align:start position:0% that was the a very maximalist belief back<00:11:46.000> maybe<00:11:46.200> in<00:11:46.360> 2016<00:11:47.000> 2017<00:11:47.839> I<00:11:47.920> wouldn't<00:11:48.120> say 00:11:48.230 --> 00:11:48.240 align:start position:0% back maybe in 2016 2017 I wouldn't say 00:11:48.240 --> 00:11:50.190 align:start position:0% back maybe in 2016 2017 I wouldn't say it's<00:11:48.399> probably<00:11:48.720> like<00:11:48.920> widespread<00:11:49.440> but<00:11:49.560> it<00:11:49.680> was 00:11:50.190 --> 00:11:50.200 align:start position:0% it's probably like widespread but it was 00:11:50.200 --> 00:11:53.110 align:start position:0% it's probably like widespread but it was a<00:11:50.360> very<00:11:50.720> strong<00:11:50.959> belief<00:11:51.320> so<00:11:51.519> maybe<00:11:51.920> like<00:11:52.200> Alice 00:11:53.110 --> 00:11:53.120 align:start position:0% a very strong belief so maybe like Alice 00:11:53.120 --> 00:11:54.870 align:start position:0% a very strong belief so maybe like Alice tin<00:11:53.560> you<00:11:53.680> all<00:11:53.920> have<00:11:54.079> been<00:11:54.240> in<00:11:54.360> the<00:11:54.480> industry 00:11:54.870 --> 00:11:54.880 align:start position:0% tin you all have been in the industry 00:11:54.880 --> 00:11:58.190 align:start position:0% tin you all have been in the industry maybe<00:11:55.279> for<00:11:56.240> 3<00:11:56.519> four<00:11:56.800> years<00:11:57.120> I<00:11:57.200> would<00:11:57.399> say<00:11:57.959> as<00:11:58.040> a 00:11:58.190 --> 00:11:58.200 align:start position:0% maybe for 3 four years I would say as a 00:11:58.200 --> 00:12:00.110 align:start position:0% maybe for 3 four years I would say as a user<00:11:58.760> how<00:11:58.880> does<00:11:59.040> that<00:11:59.399> perspective<00:11:59.839> make<00:12:00.000> you 00:12:00.110 --> 00:12:00.120 align:start position:0% user how does that perspective make you 00:12:00.120 --> 00:12:02.269 align:start position:0% user how does that perspective make you all<00:12:00.279> feel<00:12:00.519> like<00:12:00.720> how<00:12:00.880> did<00:12:01.000> you<00:12:01.120> all<00:12:01.360> experience 00:12:02.269 --> 00:12:02.279 align:start position:0% all feel like how did you all experience 00:12:02.279 --> 00:12:03.990 align:start position:0% all feel like how did you all experience the<00:12:02.440> same<00:12:02.800> or<00:12:02.959> was<00:12:03.079> it<00:12:03.240> still<00:12:03.480> the<00:12:03.600> same<00:12:03.839> when 00:12:03.990 --> 00:12:04.000 align:start position:0% the same or was it still the same when 00:12:04.000 --> 00:12:07.670 align:start position:0% the same or was it still the same when you<00:12:04.200> entered<00:12:04.800> and<00:12:05.000> has<00:12:05.160> that 00:12:07.670 --> 00:12:07.680 align:start position:0% 00:12:07.680 --> 00:12:10.350 align:start position:0% changed<00:12:08.680> yeah<00:12:08.800> sure 00:12:10.350 --> 00:12:10.360 align:start position:0% changed yeah sure 00:12:10.360 --> 00:12:13.189 align:start position:0% changed yeah sure um<00:12:11.360> I<00:12:11.519> would<00:12:11.839> totally<00:12:12.279> agree<00:12:12.560> with<00:12:12.760> this<00:12:13.079> I 00:12:13.189 --> 00:12:13.199 align:start position:0% um I would totally agree with this I 00:12:13.199 --> 00:12:17.470 align:start position:0% um I would totally agree with this I think<00:12:13.600> if<00:12:13.760> you're<00:12:14.680> building<00:12:15.680> for<00:12:16.399> crypto<00:12:17.399> and 00:12:17.470 --> 00:12:17.480 align:start position:0% think if you're building for crypto and 00:12:17.480 --> 00:12:19.389 align:start position:0% think if you're building for crypto and you<00:12:17.600> want<00:12:17.720> to<00:12:17.880> gain<00:12:18.120> user<00:12:18.600> adoption<00:12:19.240> then 00:12:19.389 --> 00:12:19.399 align:start position:0% you want to gain user adoption then 00:12:19.399 --> 00:12:20.949 align:start position:0% you want to gain user adoption then you've<00:12:19.600> got<00:12:19.720> to<00:12:19.880> build<00:12:20.279> things<00:12:20.639> that<00:12:20.760> are 00:12:20.949 --> 00:12:20.959 align:start position:0% you've got to build things that are 00:12:20.959 --> 00:12:23.990 align:start position:0% you've got to build things that are built<00:12:21.519> on<00:12:21.920> say<00:12:22.600> account<00:12:23.000> abstraction<00:12:23.560> but 00:12:23.990 --> 00:12:24.000 align:start position:0% built on say account abstraction but 00:12:24.000 --> 00:12:26.230 align:start position:0% built on say account abstraction but without<00:12:25.000> using<00:12:25.360> that<00:12:25.560> term<00:12:25.839> you<00:12:25.920> know<00:12:26.120> if 00:12:26.230 --> 00:12:26.240 align:start position:0% without using that term you know if 00:12:26.240 --> 00:12:27.430 align:start position:0% without using that term you know if you're<00:12:26.560> if<00:12:26.639> you're<00:12:26.800> doing<00:12:27.040> a<00:12:27.160> account 00:12:27.430 --> 00:12:27.440 align:start position:0% you're if you're doing a account 00:12:27.440 --> 00:12:29.269 align:start position:0% you're if you're doing a account abstraction<00:12:27.920> the<00:12:28.079> right<00:12:28.320> way<00:12:28.680> the<00:12:28.800> truth<00:12:29.000> is 00:12:29.269 --> 00:12:29.279 align:start position:0% abstraction the right way the truth is 00:12:29.279 --> 00:12:31.030 align:start position:0% abstraction the right way the truth is your<00:12:29.440> user<00:12:29.760> won't<00:12:30.040> know<00:12:30.320> that<00:12:30.440> it's<00:12:30.600> built<00:12:30.839> on 00:12:31.030 --> 00:12:31.040 align:start position:0% your user won't know that it's built on 00:12:31.040 --> 00:12:32.670 align:start position:0% your user won't know that it's built on account<00:12:31.320> abstraction<00:12:31.839> they<00:12:31.959> won't<00:12:32.199> even<00:12:32.399> know 00:12:32.670 --> 00:12:32.680 align:start position:0% account abstraction they won't even know 00:12:32.680 --> 00:12:34.389 align:start position:0% account abstraction they won't even know that<00:12:32.839> it's<00:12:33.000> built<00:12:33.240> on<00:12:33.399> web<00:12:33.639> 3<00:12:33.959> they<00:12:34.040> might<00:12:34.240> not 00:12:34.389 --> 00:12:34.399 align:start position:0% that it's built on web 3 they might not 00:12:34.399 --> 00:12:36.110 align:start position:0% that it's built on web 3 they might not even<00:12:34.560> know<00:12:34.760> there's<00:12:35.079> digital<00:12:35.720> assets 00:12:36.110 --> 00:12:36.120 align:start position:0% even know there's digital assets 00:12:36.120 --> 00:12:38.230 align:start position:0% even know there's digital assets powering<00:12:36.519> it<00:12:37.040> and<00:12:37.199> we're<00:12:37.360> seeing<00:12:37.639> this<00:12:37.920> with 00:12:38.230 --> 00:12:38.240 align:start position:0% powering it and we're seeing this with 00:12:38.240 --> 00:12:41.430 align:start position:0% powering it and we're seeing this with things<00:12:38.639> like<00:12:39.440> poly<00:12:39.880> Market<00:12:40.399> or<00:12:40.600> worldcoin 00:12:41.430 --> 00:12:41.440 align:start position:0% things like poly Market or worldcoin 00:12:41.440 --> 00:12:43.389 align:start position:0% things like poly Market or worldcoin those<00:12:41.560> are<00:12:41.760> the<00:12:41.920> real<00:12:42.320> apps<00:12:42.639> that<00:12:42.760> are<00:12:42.920> gaining 00:12:43.389 --> 00:12:43.399 align:start position:0% those are the real apps that are gaining 00:12:43.399 --> 00:12:44.990 align:start position:0% those are the real apps that are gaining traction<00:12:43.920> and<00:12:44.120> that<00:12:44.320> are<00:12:44.560> actually<00:12:44.800> on 00:12:44.990 --> 00:12:45.000 align:start position:0% traction and that are actually on 00:12:45.000 --> 00:12:49.550 align:start position:0% traction and that are actually on boarding<00:12:45.440> users<00:12:46.040> today<00:12:47.040> um<00:12:47.440> but 00:12:49.550 --> 00:12:49.560 align:start position:0% boarding users today um but 00:12:49.560 --> 00:12:52.430 align:start position:0% boarding users today um but without<00:12:50.560> being<00:12:51.399> you<00:12:51.519> wouldn't<00:12:52.000> they<00:12:52.120> wouldn't 00:12:52.430 --> 00:12:52.440 align:start position:0% without being you wouldn't they wouldn't 00:12:52.440 --> 00:12:54.509 align:start position:0% without being you wouldn't they wouldn't call<00:12:52.800> themselves<00:12:53.160> crypto<00:12:53.560> users<00:12:53.880> or<00:12:54.079> web3 00:12:54.509 --> 00:12:54.519 align:start position:0% call themselves crypto users or web3 00:12:54.519 --> 00:12:56.310 align:start position:0% call themselves crypto users or web3 users<00:12:55.000> necessarily<00:12:55.720> and<00:12:55.839> it's<00:12:55.959> just<00:12:56.120> un 00:12:56.310 --> 00:12:56.320 align:start position:0% users necessarily and it's just un 00:12:56.320 --> 00:12:58.350 align:start position:0% users necessarily and it's just un blocking<00:12:56.639> a<00:12:56.760> lot<00:12:56.880> of<00:12:57.440> use<00:12:57.839> cases<00:12:58.160> that<00:12:58.279> you 00:12:58.350 --> 00:12:58.360 align:start position:0% blocking a lot of use cases that you 00:12:58.360 --> 00:13:00.470 align:start position:0% blocking a lot of use cases that you don't<00:12:58.560> see<00:12:58.920> any<00:12:59.160> anywhere 00:13:00.470 --> 00:13:00.480 align:start position:0% don't see any anywhere 00:13:00.480 --> 00:13:03.590 align:start position:0% don't see any anywhere else<00:13:01.480> yeah<00:13:01.639> to<00:13:01.760> follow<00:13:02.000> up<00:13:02.160> on<00:13:02.399> that<00:13:02.800> um<00:13:03.519> I 00:13:03.590 --> 00:13:03.600 align:start position:0% else yeah to follow up on that um I 00:13:03.600 --> 00:13:05.230 align:start position:0% else yeah to follow up on that um I think<00:13:03.800> at<00:13:03.920> the<00:13:04.079> beginning<00:13:04.440> so<00:13:04.680> I've<00:13:04.800> been<00:13:05.040> a 00:13:05.230 --> 00:13:05.240 align:start position:0% think at the beginning so I've been a 00:13:05.240 --> 00:13:07.470 align:start position:0% think at the beginning so I've been a participant<00:13:06.000> in<00:13:06.120> the<00:13:06.279> space<00:13:06.560> I<00:13:06.680> guess<00:13:07.199> for 00:13:07.470 --> 00:13:07.480 align:start position:0% participant in the space I guess for 00:13:07.480 --> 00:13:08.910 align:start position:0% participant in the space I guess for maybe<00:13:07.720> seven<00:13:08.000> years<00:13:08.279> something<00:13:08.560> like<00:13:08.720> that 00:13:08.910 --> 00:13:08.920 align:start position:0% maybe seven years something like that 00:13:08.920 --> 00:13:10.150 align:start position:0% maybe seven years something like that and<00:13:09.040> then<00:13:09.199> just<00:13:09.360> designing<00:13:09.720> for<00:13:09.880> the<00:13:10.000> past 00:13:10.150 --> 00:13:10.160 align:start position:0% and then just designing for the past 00:13:10.160 --> 00:13:12.430 align:start position:0% and then just designing for the past three<00:13:10.320> or<00:13:10.519> four<00:13:11.519> um<00:13:11.760> so<00:13:11.880> I've<00:13:12.000> seen<00:13:12.160> a<00:13:12.279> little 00:13:12.430 --> 00:13:12.440 align:start position:0% three or four um so I've seen a little 00:13:12.440 --> 00:13:14.389 align:start position:0% three or four um so I've seen a little bit<00:13:12.560> of<00:13:12.680> the<00:13:12.800> evolution<00:13:13.279> not<00:13:13.480> like<00:13:13.639> super<00:13:13.920> OG 00:13:14.389 --> 00:13:14.399 align:start position:0% bit of the evolution not like super OG 00:13:14.399 --> 00:13:16.150 align:start position:0% bit of the evolution not like super OG but<00:13:14.600> I<00:13:14.680> think<00:13:14.800> at<00:13:14.959> first<00:13:15.279> it<00:13:15.399> was<00:13:15.560> the<00:13:15.760> secret 00:13:16.150 --> 00:13:16.160 align:start position:0% but I think at first it was the secret 00:13:16.160 --> 00:13:18.949 align:start position:0% but I think at first it was the secret club<00:13:17.079> and<00:13:17.320> the<00:13:17.519> language<00:13:17.920> that<00:13:18.040> we<00:13:18.160> use<00:13:18.519> I<00:13:18.720> I 00:13:18.949 --> 00:13:18.959 align:start position:0% club and the language that we use I I 00:13:18.959 --> 00:13:20.829 align:start position:0% club and the language that we use I I appreciate<00:13:19.360> Romina<00:13:19.839> talking<00:13:20.160> about<00:13:20.560> like 00:13:20.829 --> 00:13:20.839 align:start position:0% appreciate Romina talking about like 00:13:20.839 --> 00:13:24.150 align:start position:0% appreciate Romina talking about like even<00:13:21.079> the<00:13:21.199> design<00:13:21.519> and<00:13:21.680> the<00:13:22.000> aesthetic<00:13:23.000> um<00:13:23.920> uh 00:13:24.150 --> 00:13:24.160 align:start position:0% even the design and the aesthetic um uh 00:13:24.160 --> 00:13:25.470 align:start position:0% even the design and the aesthetic um uh but<00:13:24.320> the<00:13:24.440> language<00:13:24.760> that<00:13:24.880> we<00:13:24.959> used<00:13:25.240> both<00:13:25.399> the 00:13:25.470 --> 00:13:25.480 align:start position:0% but the language that we used both the 00:13:25.480 --> 00:13:28.230 align:start position:0% but the language that we used both the visual<00:13:25.839> language<00:13:26.480> and<00:13:26.720> the<00:13:26.880> written<00:13:27.240> language 00:13:28.230 --> 00:13:28.240 align:start position:0% visual language and the written language 00:13:28.240 --> 00:13:30.230 align:start position:0% visual language and the written language um<00:13:28.480> was<00:13:28.720> kind<00:13:28.880> of<00:13:29.240> exclusive<00:13:29.720> like<00:13:29.839> we<00:13:29.959> wanted 00:13:30.230 --> 00:13:30.240 align:start position:0% um was kind of exclusive like we wanted 00:13:30.240 --> 00:13:32.470 align:start position:0% um was kind of exclusive like we wanted it<00:13:30.360> to<00:13:30.560> be<00:13:30.760> this<00:13:30.920> secret<00:13:31.279> handshake<00:13:31.760> Club<00:13:32.240> I<00:13:32.399> I 00:13:32.470 --> 00:13:32.480 align:start position:0% it to be this secret handshake Club I I 00:13:32.480 --> 00:13:34.470 align:start position:0% it to be this secret handshake Club I I think<00:13:32.639> that's<00:13:32.880> actually<00:13:33.199> fine<00:13:33.760> early<00:13:34.040> on<00:13:34.279> so 00:13:34.470 --> 00:13:34.480 align:start position:0% think that's actually fine early on so 00:13:34.480 --> 00:13:37.350 align:start position:0% think that's actually fine early on so when<00:13:34.600> you<00:13:34.839> heard<00:13:35.160> this<00:13:35.519> comment<00:13:36.440> I<00:13:36.600> think<00:13:37.000> uh 00:13:37.350 --> 00:13:37.360 align:start position:0% when you heard this comment I think uh 00:13:37.360 --> 00:13:38.829 align:start position:0% when you heard this comment I think uh it<00:13:37.519> might<00:13:37.680> have<00:13:37.839> been<00:13:38.320> that<00:13:38.440> might<00:13:38.600> have<00:13:38.680> been 00:13:38.829 --> 00:13:38.839 align:start position:0% it might have been that might have been 00:13:38.839 --> 00:13:40.949 align:start position:0% it might have been that might have been fine<00:13:39.000> for<00:13:39.160> the<00:13:39.360> time<00:13:39.880> you<00:13:40.000> know<00:13:40.240> you<00:13:40.440> you<00:13:40.519> were 00:13:40.949 --> 00:13:40.959 align:start position:0% fine for the time you know you you were 00:13:40.959 --> 00:13:43.629 align:start position:0% fine for the time you know you you were solving<00:13:41.399> super<00:13:41.680> hard<00:13:42.120> problems<00:13:43.120> um<00:13:43.320> around 00:13:43.629 --> 00:13:43.639 align:start position:0% solving super hard problems um around 00:13:43.639 --> 00:13:46.550 align:start position:0% solving super hard problems um around like<00:13:43.880> decentralization<00:13:44.880> and<00:13:45.160> privacy<00:13:45.760> and 00:13:46.550 --> 00:13:46.560 align:start position:0% like decentralization and privacy and 00:13:46.560 --> 00:13:48.550 align:start position:0% like decentralization and privacy and cryptography<00:13:47.560> and<00:13:47.680> now<00:13:47.839> a<00:13:47.920> lot<00:13:48.079> of<00:13:48.240> that<00:13:48.360> is 00:13:48.550 --> 00:13:48.560 align:start position:0% cryptography and now a lot of that is 00:13:48.560 --> 00:13:50.550 align:start position:0% cryptography and now a lot of that is table<00:13:48.839> stakes<00:13:49.199> and<00:13:49.360> it's<00:13:49.560> time<00:13:49.800> to<00:13:50.079> to<00:13:50.279> grow 00:13:50.550 --> 00:13:50.560 align:start position:0% table stakes and it's time to to grow 00:13:50.560 --> 00:13:52.430 align:start position:0% table stakes and it's time to to grow and<00:13:50.720> to<00:13:51.240> like<00:13:51.399> communicate<00:13:52.040> not<00:13:52.199> only 00:13:52.430 --> 00:13:52.440 align:start position:0% and to like communicate not only 00:13:52.440 --> 00:13:55.310 align:start position:0% and to like communicate not only internally<00:13:52.959> but<00:13:53.160> like<00:13:53.639> externally<00:13:54.639> um<00:13:55.160> and 00:13:55.310 --> 00:13:55.320 align:start position:0% internally but like externally um and 00:13:55.320 --> 00:13:57.310 align:start position:0% internally but like externally um and the<00:13:55.440> good<00:13:55.600> news<00:13:55.959> I<00:13:56.360> I<00:13:56.440> mean<00:13:56.800> I<00:13:56.920> have<00:13:57.000> a<00:13:57.079> lot<00:13:57.199> of 00:13:57.310 --> 00:13:57.320 align:start position:0% the good news I I mean I have a lot of 00:13:57.320 --> 00:13:58.629 align:start position:0% the good news I I mean I have a lot of critiques<00:13:57.720> maybe<00:13:57.920> we're<00:13:58.079> not<00:13:58.199> doing<00:13:58.440> this 00:13:58.629 --> 00:13:58.639 align:start position:0% critiques maybe we're not doing this 00:13:58.639 --> 00:13:59.590 align:start position:0% critiques maybe we're not doing this enough 00:13:59.590 --> 00:13:59.600 align:start position:0% enough 00:13:59.600 --> 00:14:02.110 align:start position:0% enough um<00:13:59.759> but<00:13:59.880> we<00:14:00.000> are<00:14:00.160> seeing<00:14:00.560> like<00:14:00.720> real<00:14:01.279> use<00:14:01.680> cases 00:14:02.110 --> 00:14:02.120 align:start position:0% um but we are seeing like real use cases 00:14:02.120 --> 00:14:05.829 align:start position:0% um but we are seeing like real use cases like<00:14:02.320> my<00:14:02.519> in-law<00:14:02.959> family<00:14:03.279> in<00:14:03.880> Argentina<00:14:04.880> um<00:14:05.759> I 00:14:05.829 --> 00:14:05.839 align:start position:0% like my in-law family in Argentina um I 00:14:05.839 --> 00:14:07.710 align:start position:0% like my in-law family in Argentina um I mean<00:14:06.000> they're<00:14:06.199> all<00:14:06.360> over<00:14:06.680> like<00:14:06.839> stable<00:14:07.240> coins 00:14:07.710 --> 00:14:07.720 align:start position:0% mean they're all over like stable coins 00:14:07.720 --> 00:14:10.389 align:start position:0% mean they're all over like stable coins and<00:14:07.839> it's<00:14:08.079> very<00:14:08.279> common<00:14:08.600> practice<00:14:09.000> I<00:14:09.120> just<00:14:09.399> had 00:14:10.389 --> 00:14:10.399 align:start position:0% and it's very common practice I just had 00:14:10.399 --> 00:14:13.110 align:start position:0% and it's very common practice I just had um<00:14:11.160> uh<00:14:11.480> a<00:14:11.600> friend<00:14:11.839> from<00:14:12.040> Argentina<00:14:12.639> like<00:14:12.880> put 00:14:13.110 --> 00:14:13.120 align:start position:0% um uh a friend from Argentina like put 00:14:13.120 --> 00:14:15.470 align:start position:0% um uh a friend from Argentina like put put<00:14:13.240> a<00:14:13.360> down<00:14:13.600> payment<00:14:13.839> on<00:14:13.959> a<00:14:14.120> house<00:14:14.759> uh<00:14:14.880> using 00:14:15.470 --> 00:14:15.480 align:start position:0% put a down payment on a house uh using 00:14:15.480 --> 00:14:17.389 align:start position:0% put a down payment on a house uh using you<00:14:15.560> know<00:14:15.759> crypto<00:14:16.519> um<00:14:16.680> and<00:14:16.800> they're<00:14:17.000> like<00:14:17.240> how 00:14:17.389 --> 00:14:17.399 align:start position:0% you know crypto um and they're like how 00:14:17.399 --> 00:14:19.910 align:start position:0% you know crypto um and they're like how you<00:14:17.519> know<00:14:17.839> like<00:14:18.480> uh<00:14:18.920> current<00:14:19.240> like<00:14:19.399> Exchange 00:14:19.910 --> 00:14:19.920 align:start position:0% you know like uh current like Exchange 00:14:19.920 --> 00:14:21.470 align:start position:0% you know like uh current like Exchange locations<00:14:20.639> you<00:14:20.759> know<00:14:21.000> because<00:14:21.120> you<00:14:21.199> need<00:14:21.360> to 00:14:21.470 --> 00:14:21.480 align:start position:0% locations you know because you need to 00:14:21.480 --> 00:14:22.629 align:start position:0% locations you know because you need to put<00:14:21.600> all<00:14:21.720> the<00:14:21.800> money<00:14:22.000> up<00:14:22.160> front<00:14:22.440> because<00:14:22.560> you 00:14:22.629 --> 00:14:22.639 align:start position:0% put all the money up front because you 00:14:22.639 --> 00:14:24.590 align:start position:0% put all the money up front because you don't<00:14:22.839> have<00:14:23.160> like<00:14:23.519> sophisticated<00:14:24.120> financing 00:14:24.590 --> 00:14:24.600 align:start position:0% don't have like sophisticated financing 00:14:24.600 --> 00:14:27.590 align:start position:0% don't have like sophisticated financing options<00:14:24.920> a<00:14:25.040> lot<00:14:25.160> of<00:14:25.320> times<00:14:25.600> so<00:14:26.199> it's<00:14:26.519> you<00:14:26.680> know 00:14:27.590 --> 00:14:27.600 align:start position:0% options a lot of times so it's you know 00:14:27.600 --> 00:14:29.990 align:start position:0% options a lot of times so it's you know I<00:14:27.720> think<00:14:27.880> that<00:14:28.000> we<00:14:28.120> are<00:14:28.279> like<00:14:28.399> solving<00:14:28.759> very 00:14:29.990 --> 00:14:30.000 align:start position:0% I think that we are like solving very 00:14:30.000 --> 00:14:31.590 align:start position:0% I think that we are like solving very at<00:14:30.160> first<00:14:30.360> it<00:14:30.440> was<00:14:30.600> very<00:14:30.800> abstract<00:14:31.279> but<00:14:31.399> now<00:14:31.560> I 00:14:31.590 --> 00:14:31.600 align:start position:0% at first it was very abstract but now I 00:14:31.600 --> 00:14:33.310 align:start position:0% at first it was very abstract but now I think<00:14:31.720> we're<00:14:31.880> solving<00:14:32.199> very<00:14:32.399> core<00:14:32.720> like<00:14:32.920> human 00:14:33.310 --> 00:14:33.320 align:start position:0% think we're solving very core like human 00:14:33.320 --> 00:14:35.430 align:start position:0% think we're solving very core like human problems<00:14:33.759> so<00:14:34.079> stability<00:14:34.720> for<00:14:34.920> example<00:14:35.320> like 00:14:35.430 --> 00:14:35.440 align:start position:0% problems so stability for example like 00:14:35.440 --> 00:14:37.710 align:start position:0% problems so stability for example like why<00:14:35.560> do<00:14:35.759> people<00:14:36.519> want<00:14:36.759> stable<00:14:37.160> coins<00:14:37.480> well 00:14:37.710 --> 00:14:37.720 align:start position:0% why do people want stable coins well 00:14:37.720 --> 00:14:39.949 align:start position:0% why do people want stable coins well like<00:14:37.959> Argentina<00:14:38.519> experienced<00:14:39.000> over<00:14:39.360> 200% 00:14:39.949 --> 00:14:39.959 align:start position:0% like Argentina experienced over 200% 00:14:39.959 --> 00:14:42.150 align:start position:0% like Argentina experienced over 200% inflation<00:14:40.959> you<00:14:41.079> can't<00:14:41.279> plan<00:14:41.480> for<00:14:41.639> the<00:14:41.759> future 00:14:42.150 --> 00:14:42.160 align:start position:0% inflation you can't plan for the future 00:14:42.160 --> 00:14:44.430 align:start position:0% inflation you can't plan for the future you<00:14:42.360> can't<00:14:42.600> save<00:14:43.079> you<00:14:43.240> can't<00:14:43.639> you<00:14:43.759> know<00:14:44.199> make 00:14:44.430 --> 00:14:44.440 align:start position:0% you can't save you can't you know make 00:14:44.440 --> 00:14:46.790 align:start position:0% you can't save you can't you know make plans<00:14:44.680> for<00:14:44.800> your<00:14:44.959> family<00:14:45.440> and<00:14:45.600> so<00:14:46.440> and<00:14:46.639> it's 00:14:46.790 --> 00:14:46.800 align:start position:0% plans for your family and so and it's 00:14:46.800 --> 00:14:48.430 align:start position:0% plans for your family and so and it's not<00:14:47.000> about<00:14:47.320> making<00:14:47.600> money<00:14:47.880> it's<00:14:48.040> just<00:14:48.240> like 00:14:48.430 --> 00:14:48.440 align:start position:0% not about making money it's just like 00:14:48.440 --> 00:14:50.790 align:start position:0% not about making money it's just like keeping<00:14:48.759> money<00:14:49.320> right<00:14:49.720> and<00:14:50.120> so<00:14:50.480> I<00:14:50.560> think 00:14:50.790 --> 00:14:50.800 align:start position:0% keeping money right and so I think 00:14:50.800 --> 00:14:52.350 align:start position:0% keeping money right and so I think that's<00:14:51.079> why<00:14:51.720> some<00:14:51.839> of<00:14:51.959> the<00:14:52.040> stuff<00:14:52.240> we're 00:14:52.350 --> 00:14:52.360 align:start position:0% that's why some of the stuff we're 00:14:52.360 --> 00:14:54.550 align:start position:0% that's why some of the stuff we're making<00:14:52.600> is<00:14:52.720> really<00:14:52.920> taking<00:14:53.279> off<00:14:53.759> and<00:14:54.120> um<00:14:54.399> it's 00:14:54.550 --> 00:14:54.560 align:start position:0% making is really taking off and um it's 00:14:54.560 --> 00:14:56.749 align:start position:0% making is really taking off and um it's a<00:14:54.759> testament<00:14:55.199> to<00:14:55.959> some<00:14:56.120> of<00:14:56.279> these<00:14:56.440> secret 00:14:56.749 --> 00:14:56.759 align:start position:0% a testament to some of these secret 00:14:56.759 --> 00:14:58.430 align:start position:0% a testament to some of these secret handshakes<00:14:57.320> early<00:14:57.560> on<00:14:57.880> you<00:14:58.000> know<00:14:58.199> like<00:14:58.320> some 00:14:58.430 --> 00:14:58.440 align:start position:0% handshakes early on you know like some 00:14:58.440 --> 00:15:00.550 align:start position:0% handshakes early on you know like some of<00:14:58.600> this<00:14:58.720> like<00:14:59.040> secret<00:14:59.320> club<00:14:59.800> stuff<00:15:00.160> like<00:15:00.399> they 00:15:00.550 --> 00:15:00.560 align:start position:0% of this like secret club stuff like they 00:15:00.560 --> 00:15:01.829 align:start position:0% of this like secret club stuff like they you<00:15:00.639> know<00:15:00.880> solving<00:15:01.240> really<00:15:01.600> difficult 00:15:01.829 --> 00:15:01.839 align:start position:0% you know solving really difficult 00:15:01.839 --> 00:15:03.749 align:start position:0% you know solving really difficult problems<00:15:02.199> and<00:15:02.360> now<00:15:03.079> I<00:15:03.160> think<00:15:03.320> we<00:15:03.440> can<00:15:03.560> have 00:15:03.749 --> 00:15:03.759 align:start position:0% problems and now I think we can have 00:15:03.759 --> 00:15:05.710 align:start position:0% problems and now I think we can have more<00:15:03.920> Nuance<00:15:04.320> takes<00:15:04.560> on<00:15:04.759> privacy<00:15:05.199> for<00:15:05.360> example 00:15:05.710 --> 00:15:05.720 align:start position:0% more Nuance takes on privacy for example 00:15:05.720 --> 00:15:08.509 align:start position:0% more Nuance takes on privacy for example with<00:15:05.839> zero<00:15:06.120> knowledge<00:15:06.440> proofs<00:15:07.399> and<00:15:08.040> um<00:15:08.360> you 00:15:08.509 --> 00:15:08.519 align:start position:0% with zero knowledge proofs and um you 00:15:08.519 --> 00:15:10.389 align:start position:0% with zero knowledge proofs and um you know<00:15:08.800> but<00:15:09.160> I<00:15:09.240> think<00:15:09.399> it<00:15:09.480> is<00:15:09.720> time<00:15:09.920> to<00:15:10.199> to 00:15:10.389 --> 00:15:10.399 align:start position:0% know but I think it is time to to 00:15:10.399 --> 00:15:14.829 align:start position:0% know but I think it is time to to develop<00:15:10.839> like<00:15:11.160> a<00:15:12.160> a<00:15:12.320> more<00:15:13.000> I<00:15:13.519> guess<00:15:14.519> I<00:15:14.639> guess 00:15:14.829 --> 00:15:14.839 align:start position:0% develop like a a more I guess I guess 00:15:14.839 --> 00:15:17.150 align:start position:0% develop like a a more I guess I guess like<00:15:15.120> a<00:15:15.399> just<00:15:15.560> a<00:15:16.079> I<00:15:16.279> just<00:15:16.600> just<00:15:16.720> to<00:15:16.880> talk<00:15:17.040> to 00:15:17.150 --> 00:15:17.160 align:start position:0% like a just a I just just to talk to 00:15:17.160 --> 00:15:19.710 align:start position:0% like a just a I just just to talk to more<00:15:17.399> people<00:15:17.959> and<00:15:18.759> um<00:15:19.000> that<00:15:19.120> is<00:15:19.279> one<00:15:19.480> thing 00:15:19.710 --> 00:15:19.720 align:start position:0% more people and um that is one thing 00:15:19.720 --> 00:15:21.949 align:start position:0% more people and um that is one thing that<00:15:20.320> I<00:15:20.440> haven't<00:15:20.720> been<00:15:21.279> doing<00:15:21.519> for<00:15:21.680> that<00:15:21.839> long 00:15:21.949 --> 00:15:21.959 align:start position:0% that I haven't been doing for that long 00:15:21.959 --> 00:15:23.389 align:start position:0% that I haven't been doing for that long so<00:15:22.120> I<00:15:22.199> can't<00:15:22.360> take<00:15:22.560> credit<00:15:22.800> for<00:15:22.920> the<00:15:23.079> design 00:15:23.389 --> 00:15:23.399 align:start position:0% so I can't take credit for the design 00:15:23.399 --> 00:15:24.990 align:start position:0% so I can't take credit for the design but<00:15:23.519> I<00:15:23.639> like<00:15:23.880> that<00:15:24.160> I<00:15:24.240> feel<00:15:24.480> like<00:15:24.720> they<00:15:24.880> they're 00:15:24.990 --> 00:15:25.000 align:start position:0% but I like that I feel like they they're 00:15:25.000 --> 00:15:26.949 align:start position:0% but I like that I feel like they they're trying<00:15:25.199> to<00:15:25.360> speak<00:15:25.560> to<00:15:25.680> more<00:15:25.880> people<00:15:26.759> um<00:15:26.880> and 00:15:26.949 --> 00:15:26.959 align:start position:0% trying to speak to more people um and 00:15:26.959 --> 00:15:28.189 align:start position:0% trying to speak to more people um and there's<00:15:27.120> some<00:15:27.279> other<00:15:27.480> really<00:15:27.639> great<00:15:27.880> projects 00:15:28.189 --> 00:15:28.199 align:start position:0% there's some other really great projects 00:15:28.199 --> 00:15:30.670 align:start position:0% there's some other really great projects out<00:15:28.360> there<00:15:28.519> too<00:15:29.279> if<00:15:29.399> I<00:15:29.560> can<00:15:30.040> connect<00:15:30.360> to<00:15:30.560> what 00:15:30.670 --> 00:15:30.680 align:start position:0% out there too if I can connect to what 00:15:30.680 --> 00:15:34.990 align:start position:0% out there too if I can connect to what you<00:15:30.839> just<00:15:31.079> said<00:15:31.560> you<00:15:31.839> mentioned<00:15:32.800> um<00:15:33.600> the<00:15:34.600> the 00:15:34.990 --> 00:15:35.000 align:start position:0% you just said you mentioned um the the 00:15:35.000 --> 00:15:37.030 align:start position:0% you just said you mentioned um the the users<00:15:35.440> in<00:15:35.639> countries<00:15:35.959> like<00:15:36.160> Argentina<00:15:36.759> for 00:15:37.030 --> 00:15:37.040 align:start position:0% users in countries like Argentina for 00:15:37.040 --> 00:15:40.389 align:start position:0% users in countries like Argentina for example<00:15:37.399> in<00:15:37.560> stable<00:15:37.920> coin<00:15:38.399> interactions<00:15:39.399> um 00:15:40.389 --> 00:15:40.399 align:start position:0% example in stable coin interactions um 00:15:40.399 --> 00:15:43.230 align:start position:0% example in stable coin interactions um so<00:15:40.920> here<00:15:41.480> when<00:15:41.639> we<00:15:41.959> think<00:15:42.199> about<00:15:42.519> yeah<00:15:43.000> should 00:15:43.230 --> 00:15:43.240 align:start position:0% so here when we think about yeah should 00:15:43.240 --> 00:15:45.790 align:start position:0% so here when we think about yeah should you<00:15:43.440> cater<00:15:43.959> this<00:15:44.199> dogmatism<00:15:45.079> about<00:15:45.639> yeah 00:15:45.790 --> 00:15:45.800 align:start position:0% you cater this dogmatism about yeah 00:15:45.800 --> 00:15:47.749 align:start position:0% you cater this dogmatism about yeah should<00:15:45.959> you<00:15:46.160> cater<00:15:46.480> to<00:15:46.639> crypto<00:15:47.000> native<00:15:47.279> users 00:15:47.749 --> 00:15:47.759 align:start position:0% should you cater to crypto native users 00:15:47.759 --> 00:15:50.870 align:start position:0% should you cater to crypto native users first<00:15:48.279> and<00:15:48.440> then<00:15:49.240> yeah<00:15:49.839> they<00:15:50.120> there<00:15:50.319> you<00:15:50.560> have 00:15:50.870 --> 00:15:50.880 align:start position:0% first and then yeah they there you have 00:15:50.880 --> 00:15:54.230 align:start position:0% first and then yeah they there you have like<00:15:51.160> these<00:15:51.600> certain<00:15:52.199> ux<00:15:53.079> designs<00:15:53.759> that<00:15:54.040> are 00:15:54.230 --> 00:15:54.240 align:start position:0% like these certain ux designs that are 00:15:54.240 --> 00:15:56.189 align:start position:0% like these certain ux designs that are maybe<00:15:54.480> a<00:15:54.560> bit<00:15:54.759> crypto<00:15:55.079> Anarchist<00:15:55.600> inspired 00:15:56.189 --> 00:15:56.199 align:start position:0% maybe a bit crypto Anarchist inspired 00:15:56.199 --> 00:15:58.629 align:start position:0% maybe a bit crypto Anarchist inspired and<00:15:56.399> it<00:15:56.600> was<00:15:56.959> it's<00:15:57.199> actually<00:15:57.639> intentional 00:15:58.629 --> 00:15:58.639 align:start position:0% and it was it's actually intentional 00:15:58.639 --> 00:16:00.069 align:start position:0% and it was it's actually intentional right 00:16:00.069 --> 00:16:00.079 align:start position:0% right 00:16:00.079 --> 00:16:03.670 align:start position:0% right um<00:16:01.079> and<00:16:01.600> those<00:16:02.040> approaches<00:16:02.639> like<00:16:03.079> cater<00:16:03.440> to 00:16:03.670 --> 00:16:03.680 align:start position:0% um and those approaches like cater to 00:16:03.680 --> 00:16:06.150 align:start position:0% um and those approaches like cater to Crypton<00:16:04.040> native<00:16:04.399> maybe<00:16:04.759> first<00:16:05.440> was<00:16:05.680> true<00:16:05.920> for 00:16:06.150 --> 00:16:06.160 align:start position:0% Crypton native maybe first was true for 00:16:06.160 --> 00:16:08.389 align:start position:0% Crypton native maybe first was true for projects<00:16:06.680> like<00:16:06.959> safe<00:16:07.600> right<00:16:07.759> for<00:16:07.959> example 00:16:08.389 --> 00:16:08.399 align:start position:0% projects like safe right for example 00:16:08.399 --> 00:16:11.150 align:start position:0% projects like safe right for example safe<00:16:08.800> has<00:16:08.959> grown<00:16:09.399> and<00:16:09.600> has<00:16:09.800> adopted<00:16:10.440> by<00:16:10.639> now<00:16:10.920> we 00:16:11.150 --> 00:16:11.160 align:start position:0% safe has grown and has adopted by now we 00:16:11.160 --> 00:16:14.990 align:start position:0% safe has grown and has adopted by now we have<00:16:11.560> like<00:16:12.199> swap<00:16:13.040> um<00:16:13.360> Solutions<00:16:14.199> natively 00:16:14.990 --> 00:16:15.000 align:start position:0% have like swap um Solutions natively 00:16:15.000 --> 00:16:17.189 align:start position:0% have like swap um Solutions natively integrated<00:16:15.680> the<00:16:15.800> user<00:16:16.079> doesn't<00:16:16.440> even<00:16:16.800> have<00:16:16.959> to 00:16:17.189 --> 00:16:17.199 align:start position:0% integrated the user doesn't even have to 00:16:17.199 --> 00:16:19.870 align:start position:0% integrated the user doesn't even have to know<00:16:17.600> that<00:16:18.160> um<00:16:18.480> he<00:16:18.680> has<00:16:18.839> to<00:16:19.000> look<00:16:19.160> it<00:16:19.319> up<00:16:19.519> on<00:16:19.680> the 00:16:19.870 --> 00:16:19.880 align:start position:0% know that um he has to look it up on the 00:16:19.880 --> 00:16:22.389 align:start position:0% know that um he has to look it up on the web<00:16:20.519> on<00:16:20.759> Google<00:16:21.120> for<00:16:21.360> example<00:16:21.759> if<00:16:21.880> he<00:16:22.000> wants<00:16:22.240> to 00:16:22.389 --> 00:16:22.399 align:start position:0% web on Google for example if he wants to 00:16:22.399 --> 00:16:25.189 align:start position:0% web on Google for example if he wants to trade<00:16:22.639> on<00:16:22.959> cwap<00:16:23.519> he<00:16:23.639> will<00:16:23.800> get<00:16:23.959> it<00:16:24.160> selected<00:16:25.000> or 00:16:25.189 --> 00:16:25.199 align:start position:0% trade on cwap he will get it selected or 00:16:25.199 --> 00:16:27.550 align:start position:0% trade on cwap he will get it selected or in<00:16:25.319> an<00:16:25.560> interface<00:16:26.240> nicely<00:16:26.720> presented<00:16:27.199> and 00:16:27.550 --> 00:16:27.560 align:start position:0% in an interface nicely presented and 00:16:27.560 --> 00:16:30.829 align:start position:0% in an interface nicely presented and safe<00:16:28.560> um<00:16:28.800> but<00:16:28.920> but<00:16:29.040> there<00:16:29.160> are<00:16:29.399> also<00:16:29.880> use<00:16:30.319> cases 00:16:30.829 --> 00:16:30.839 align:start position:0% safe um but but there are also use cases 00:16:30.839 --> 00:16:32.670 align:start position:0% safe um but but there are also use cases like<00:16:31.160> when<00:16:31.319> we<00:16:31.399> want<00:16:31.560> to<00:16:31.759> cater<00:16:32.079> to<00:16:32.360> these 00:16:32.670 --> 00:16:32.680 align:start position:0% like when we want to cater to these 00:16:32.680 --> 00:16:34.790 align:start position:0% like when we want to cater to these people<00:16:32.959> in<00:16:33.160> Emerging<00:16:33.600> Markets<00:16:34.240> where<00:16:34.519> some 00:16:34.790 --> 00:16:34.800 align:start position:0% people in Emerging Markets where some 00:16:34.800 --> 00:16:37.790 align:start position:0% people in Emerging Markets where some solutions<00:16:35.440> didn't<00:16:35.800> work<00:16:36.199> and<00:16:36.440> now<00:16:36.880> CeeLo<00:16:37.360> for 00:16:37.790 --> 00:16:37.800 align:start position:0% solutions didn't work and now CeeLo for 00:16:37.800 --> 00:16:42.509 align:start position:0% solutions didn't work and now CeeLo for example<00:16:38.800> has<00:16:39.319> um<00:16:40.120> great<00:16:40.560> traction<00:16:41.399> with<00:16:41.800> um 00:16:42.509 --> 00:16:42.519 align:start position:0% example has um great traction with um 00:16:42.519 --> 00:16:46.110 align:start position:0% example has um great traction with um catering<00:16:43.519> crypto<00:16:44.040> users<00:16:44.800> and<00:16:45.240> um<00:16:45.720> these<00:16:45.880> are 00:16:46.110 --> 00:16:46.120 align:start position:0% catering crypto users and um these are 00:16:46.120 --> 00:16:48.389 align:start position:0% catering crypto users and um these are basically<00:16:46.880> telephone<00:16:47.440> or<00:16:47.639> mobile<00:16:48.040> phone 00:16:48.389 --> 00:16:48.399 align:start position:0% basically telephone or mobile phone 00:16:48.399 --> 00:16:51.389 align:start position:0% basically telephone or mobile phone users<00:16:48.920> that<00:16:49.079> get<00:16:49.279> a<00:16:49.639> crypto<00:16:50.079> wallet<00:16:50.440> spun<00:16:50.839> up 00:16:51.389 --> 00:16:51.399 align:start position:0% users that get a crypto wallet spun up 00:16:51.399 --> 00:16:53.870 align:start position:0% users that get a crypto wallet spun up um<00:16:51.839> connected<00:16:52.240> to<00:16:52.440> their<00:16:52.639> telep<00:16:53.000> phone<00:16:53.720> that 00:16:53.870 --> 00:16:53.880 align:start position:0% um connected to their telep phone that 00:16:53.880 --> 00:16:56.269 align:start position:0% um connected to their telep phone that they<00:16:54.079> have<00:16:54.240> or<00:16:54.440> their<00:16:54.600> mobile<00:16:55.040> device<00:16:56.040> um<00:16:56.160> and 00:16:56.269 --> 00:16:56.279 align:start position:0% they have or their mobile device um and 00:16:56.279 --> 00:16:57.749 align:start position:0% they have or their mobile device um and they're<00:16:56.440> not<00:16:56.639> even<00:16:56.959> aware<00:16:57.399> that<00:16:57.560> they're 00:16:57.749 --> 00:16:57.759 align:start position:0% they're not even aware that they're 00:16:57.759 --> 00:17:00.150 align:start position:0% they're not even aware that they're using<00:16:58.279> the<00:16:58.440> blockchain<00:16:58.959> chain<00:16:59.440> um<00:16:59.560> so<00:16:59.920> there's 00:17:00.150 --> 00:17:00.160 align:start position:0% using the blockchain chain um so there's 00:17:00.160 --> 00:17:02.069 align:start position:0% using the blockchain chain um so there's this<00:17:00.399> partnership<00:17:00.920> mini<00:17:01.279> pay<00:17:01.639> together<00:17:01.880> with 00:17:02.069 --> 00:17:02.079 align:start position:0% this partnership mini pay together with 00:17:02.079 --> 00:17:03.910 align:start position:0% this partnership mini pay together with Oprah<00:17:02.600> and<00:17:02.720> I<00:17:02.800> think<00:17:02.959> these<00:17:03.120> are<00:17:03.319> great 00:17:03.910 --> 00:17:03.920 align:start position:0% Oprah and I think these are great 00:17:03.920 --> 00:17:05.909 align:start position:0% Oprah and I think these are great designs<00:17:04.439> so<00:17:04.679> it's<00:17:04.839> a<00:17:05.079> very<00:17:05.400> different 00:17:05.909 --> 00:17:05.919 align:start position:0% designs so it's a very different 00:17:05.919 --> 00:17:08.510 align:start position:0% designs so it's a very different approach<00:17:06.360> than<00:17:06.959> catering<00:17:07.400> to<00:17:07.600> crypto<00:17:08.160> native 00:17:08.510 --> 00:17:08.520 align:start position:0% approach than catering to crypto native 00:17:08.520 --> 00:17:11.429 align:start position:0% approach than catering to crypto native users<00:17:09.079> first<00:17:09.480> and<00:17:09.640> then<00:17:09.799> learn<00:17:10.120> and<00:17:10.360> adopt<00:17:11.079> so 00:17:11.429 --> 00:17:11.439 align:start position:0% users first and then learn and adopt so 00:17:11.439 --> 00:17:14.990 align:start position:0% users first and then learn and adopt so depending<00:17:11.799> on<00:17:11.959> what<00:17:12.120> your<00:17:12.360> use<00:17:12.760> case<00:17:13.760> is<00:17:14.679> your 00:17:14.990 --> 00:17:15.000 align:start position:0% depending on what your use case is your 00:17:15.000 --> 00:17:17.189 align:start position:0% depending on what your use case is your approach<00:17:15.360> could<00:17:15.600> look<00:17:16.039> very<00:17:16.360> different<00:17:16.839> so 00:17:17.189 --> 00:17:17.199 align:start position:0% approach could look very different so 00:17:17.199 --> 00:17:20.029 align:start position:0% approach could look very different so knowing<00:17:17.559> your<00:17:17.760> user<00:17:18.280> well<00:17:18.959> or<00:17:19.439> like<00:17:19.760> where 00:17:20.029 --> 00:17:20.039 align:start position:0% knowing your user well or like where 00:17:20.039 --> 00:17:22.390 align:start position:0% knowing your user well or like where your<00:17:20.280> solution<00:17:20.760> has<00:17:20.959> the<00:17:21.160> high<00:17:21.679> impact<00:17:22.319> I 00:17:22.390 --> 00:17:22.400 align:start position:0% your solution has the high impact I 00:17:22.400 --> 00:17:25.870 align:start position:0% your solution has the high impact I think<00:17:22.959> should<00:17:23.959> um<00:17:24.880> yeah<00:17:25.400> give<00:17:25.600> you<00:17:25.720> the 00:17:25.870 --> 00:17:25.880 align:start position:0% think should um yeah give you the 00:17:25.880 --> 00:17:29.630 align:start position:0% think should um yeah give you the orientation<00:17:26.720> on<00:17:27.039> which<00:17:27.319> approach<00:17:27.640> you<00:17:27.839> follow 00:17:29.630 --> 00:17:29.640 align:start position:0% orientation on which approach you follow 00:17:29.640 --> 00:17:31.310 align:start position:0% orientation on which approach you follow I<00:17:29.720> thought<00:17:29.919> the<00:17:30.080> quote<00:17:30.320> said<00:17:30.559> the<00:17:30.720> opposite<00:17:31.240> I 00:17:31.310 --> 00:17:31.320 align:start position:0% I thought the quote said the opposite I 00:17:31.320 --> 00:17:33.029 align:start position:0% I thought the quote said the opposite I thought<00:17:31.520> you<00:17:31.720> said<00:17:32.280> if<00:17:32.400> you<00:17:32.520> want<00:17:32.679> to<00:17:32.799> build 00:17:33.029 --> 00:17:33.039 align:start position:0% thought you said if you want to build 00:17:33.039 --> 00:17:35.590 align:start position:0% thought you said if you want to build for<00:17:33.280> crypto<00:17:33.960> you<00:17:34.080> should<00:17:34.880> not<00:17:35.120> build<00:17:35.400> for 00:17:35.590 --> 00:17:35.600 align:start position:0% for crypto you should not build for 00:17:35.600 --> 00:17:38.230 align:start position:0% for crypto you should not build for crypto<00:17:35.960> users<00:17:36.880> which<00:17:37.039> is<00:17:37.640> what<00:17:37.840> what<00:17:38.039> I 00:17:38.230 --> 00:17:38.240 align:start position:0% crypto users which is what what I 00:17:38.240 --> 00:17:41.150 align:start position:0% crypto users which is what what I believe<00:17:38.799> is<00:17:39.039> what<00:17:39.200> we<00:17:39.320> should<00:17:39.520> do<00:17:40.200> um<00:17:40.960> that's 00:17:41.150 --> 00:17:41.160 align:start position:0% believe is what we should do um that's 00:17:41.160 --> 00:17:42.830 align:start position:0% believe is what we should do um that's true<00:17:41.520> so<00:17:41.720> I<00:17:41.840> think<00:17:41.960> it's<00:17:42.120> about<00:17:42.320> knowing<00:17:42.640> your 00:17:42.830 --> 00:17:42.840 align:start position:0% true so I think it's about knowing your 00:17:42.840 --> 00:17:44.789 align:start position:0% true so I think it's about knowing your users<00:17:43.360> but<00:17:43.480> it's<00:17:43.679> also<00:17:43.960> about<00:17:44.240> knowing<00:17:44.559> your 00:17:44.789 --> 00:17:44.799 align:start position:0% users but it's also about knowing your 00:17:44.799 --> 00:17:48.190 align:start position:0% users but it's also about knowing your potential<00:17:45.280> users<00:17:45.880> right<00:17:46.480> because<00:17:46.760> if<00:17:46.919> we<00:17:47.240> just 00:17:48.190 --> 00:17:48.200 align:start position:0% potential users right because if we just 00:17:48.200 --> 00:17:50.430 align:start position:0% potential users right because if we just rehash<00:17:49.080> what<00:17:49.280> do<00:17:49.400> we<00:17:49.559> know<00:17:49.799> about<00:17:49.960> our<00:17:50.200> web 00:17:50.430 --> 00:17:50.440 align:start position:0% rehash what do we know about our web 00:17:50.440 --> 00:17:52.070 align:start position:0% rehash what do we know about our web three<00:17:50.640> users<00:17:51.039> today<00:17:51.440> and<00:17:51.600> what<00:17:51.720> are<00:17:51.919> they 00:17:52.070 --> 00:17:52.080 align:start position:0% three users today and what are they 00:17:52.080 --> 00:17:53.750 align:start position:0% three users today and what are they doing<00:17:52.400> and<00:17:52.559> how<00:17:52.720> are<00:17:52.919> they<00:17:53.080> interacting<00:17:53.600> on 00:17:53.750 --> 00:17:53.760 align:start position:0% doing and how are they interacting on 00:17:53.760 --> 00:17:56.830 align:start position:0% doing and how are they interacting on chain<00:17:54.760> we're<00:17:54.960> missing<00:17:55.400> all<00:17:55.720> the<00:17:55.880> other<00:17:56.480> aspect 00:17:56.830 --> 00:17:56.840 align:start position:0% chain we're missing all the other aspect 00:17:56.840 --> 00:17:58.549 align:start position:0% chain we're missing all the other aspect and<00:17:57.039> then<00:17:57.440> you<00:17:57.520> know<00:17:57.720> not<00:17:57.880> even<00:17:58.200> thinking 00:17:58.549 --> 00:17:58.559 align:start position:0% and then you know not even thinking 00:17:58.559 --> 00:18:00.789 align:start position:0% and then you know not even thinking about<00:17:58.880> about<00:17:59.280> what<00:17:59.440> are<00:17:59.919> the<00:18:00.039> users<00:18:00.520> that<00:18:00.640> are 00:18:00.789 --> 00:18:00.799 align:start position:0% about about what are the users that are 00:18:00.799 --> 00:18:03.230 align:start position:0% about about what are the users that are not<00:18:01.039> currently<00:18:01.400> on<00:18:01.559> chain<00:18:02.280> doing<00:18:02.679> and<00:18:02.919> what<00:18:03.120> is 00:18:03.230 --> 00:18:03.240 align:start position:0% not currently on chain doing and what is 00:18:03.240 --> 00:18:05.750 align:start position:0% not currently on chain doing and what is the<00:18:03.440> purpose<00:18:04.360> for<00:18:04.559> bringing<00:18:04.919> them<00:18:05.080> on<00:18:05.240> chain 00:18:05.750 --> 00:18:05.760 align:start position:0% the purpose for bringing them on chain 00:18:05.760 --> 00:18:07.830 align:start position:0% the purpose for bringing them on chain so<00:18:05.919> so<00:18:06.080> that's<00:18:06.200> an<00:18:06.440> interesting<00:18:07.000> segue<00:18:07.600> right 00:18:07.830 --> 00:18:07.840 align:start position:0% so so that's an interesting segue right 00:18:07.840 --> 00:18:11.430 align:start position:0% so so that's an interesting segue right like<00:18:08.159> uh<00:18:08.520> knowing<00:18:09.520> uh<00:18:09.679> the<00:18:09.799> users<00:18:10.280> and<00:18:10.480> knowing 00:18:11.430 --> 00:18:11.440 align:start position:0% like uh knowing uh the users and knowing 00:18:11.440 --> 00:18:13.630 align:start position:0% like uh knowing uh the users and knowing what<00:18:11.640> the<00:18:11.760> users<00:18:12.360> want<00:18:12.840> like<00:18:13.000> if<00:18:13.120> I<00:18:13.240> can<00:18:13.400> throw 00:18:13.630 --> 00:18:13.640 align:start position:0% what the users want like if I can throw 00:18:13.640 --> 00:18:17.149 align:start position:0% what the users want like if I can throw in<00:18:13.880> this<00:18:14.120> very<00:18:14.440> age<00:18:14.880> old<00:18:15.440> adage<00:18:16.440> by<00:18:16.880> uh 00:18:17.149 --> 00:18:17.159 align:start position:0% in this very age old adage by uh 00:18:17.159 --> 00:18:19.630 align:start position:0% in this very age old adage by uh apparently<00:18:17.760> by<00:18:17.960> Henry<00:18:18.280> Ford<00:18:18.679> you<00:18:18.799> know<00:18:19.000> if<00:18:19.200> I 00:18:19.630 --> 00:18:19.640 align:start position:0% apparently by Henry Ford you know if I 00:18:19.640 --> 00:18:21.390 align:start position:0% apparently by Henry Ford you know if I asked<00:18:19.919> my<00:18:20.120> customers<00:18:20.720> what<00:18:20.919> they<00:18:21.039> want<00:18:21.320> they 00:18:21.390 --> 00:18:21.400 align:start position:0% asked my customers what they want they 00:18:21.400 --> 00:18:24.710 align:start position:0% asked my customers what they want they would<00:18:21.559> have<00:18:21.720> asked<00:18:22.000> for<00:18:22.520> Faster<00:18:23.120> Horses<00:18:24.120> right 00:18:24.710 --> 00:18:24.720 align:start position:0% would have asked for Faster Horses right 00:18:24.720 --> 00:18:28.789 align:start position:0% would have asked for Faster Horses right uh<00:18:24.960> so<00:18:25.440> I<00:18:25.559> think<00:18:25.799> in<00:18:26.280> we're<00:18:27.280> in<00:18:27.520> this<00:18:28.120> uh 00:18:28.789 --> 00:18:28.799 align:start position:0% uh so I think in we're in this uh 00:18:28.799 --> 00:18:31.230 align:start position:0% uh so I think in we're in this uh industry<00:18:29.440> where<00:18:29.840> the<00:18:30.000> user<00:18:30.360> is<00:18:30.480> a<00:18:30.600> wallet 00:18:31.230 --> 00:18:31.240 align:start position:0% industry where the user is a wallet 00:18:31.240 --> 00:18:33.830 align:start position:0% industry where the user is a wallet wallet<00:18:31.600> is<00:18:31.799> almost<00:18:32.080> an<00:18:32.280> identity<00:18:33.120> and<00:18:33.640> that 00:18:33.830 --> 00:18:33.840 align:start position:0% wallet is almost an identity and that 00:18:33.840 --> 00:18:35.909 align:start position:0% wallet is almost an identity and that identity<00:18:34.320> does<00:18:34.520> not<00:18:34.919> have<00:18:35.480> like<00:18:35.640> something 00:18:35.909 --> 00:18:35.919 align:start position:0% identity does not have like something 00:18:35.919 --> 00:18:39.029 align:start position:0% identity does not have like something like<00:18:36.039> an<00:18:36.200> email<00:18:36.840> or<00:18:37.120> a<00:18:37.320> persona<00:18:37.960> for<00:18:38.200> example 00:18:39.029 --> 00:18:39.039 align:start position:0% like an email or a persona for example 00:18:39.039 --> 00:18:41.630 align:start position:0% like an email or a persona for example so<00:18:39.520> I<00:18:39.600> think<00:18:39.799> when<00:18:40.000> building<00:18:40.360> for<00:18:40.559> this<00:18:40.799> user 00:18:41.630 --> 00:18:41.640 align:start position:0% so I think when building for this user 00:18:41.640 --> 00:18:44.029 align:start position:0% so I think when building for this user what<00:18:42.159> H<00:18:42.440> how<00:18:42.640> can<00:18:43.000> we<00:18:43.200> as<00:18:43.360> Builders 00:18:44.029 --> 00:18:44.039 align:start position:0% what H how can we as Builders 00:18:44.039 --> 00:18:46.789 align:start position:0% what H how can we as Builders effectively<00:18:44.760> collect<00:18:45.760> data<00:18:46.159> or<00:18:46.400> what 00:18:46.789 --> 00:18:46.799 align:start position:0% effectively collect data or what 00:18:46.799 --> 00:18:49.070 align:start position:0% effectively collect data or what patterns<00:18:47.240> we<00:18:47.360> can<00:18:47.559> observe<00:18:48.000> to<00:18:48.280> actually<00:18:48.960> uh 00:18:49.070 --> 00:18:49.080 align:start position:0% patterns we can observe to actually uh 00:18:49.080 --> 00:18:50.789 align:start position:0% patterns we can observe to actually uh solve<00:18:49.440> problems<00:18:49.840> like<00:18:49.960> what<00:18:50.080> are<00:18:50.200> the<00:18:50.360> actual 00:18:50.789 --> 00:18:50.799 align:start position:0% solve problems like what are the actual 00:18:50.799 --> 00:18:53.070 align:start position:0% solve problems like what are the actual problems<00:18:51.360> rather<00:18:51.640> than<00:18:52.480> shipping<00:18:52.880> out 00:18:53.070 --> 00:18:53.080 align:start position:0% problems rather than shipping out 00:18:53.080 --> 00:18:55.110 align:start position:0% problems rather than shipping out features<00:18:53.600> left<00:18:53.760> and<00:18:53.960> right<00:18:54.320> right<00:18:54.600> and<00:18:55.039> I 00:18:55.110 --> 00:18:55.120 align:start position:0% features left and right right and I 00:18:55.120 --> 00:18:56.909 align:start position:0% features left and right right and I think<00:18:55.280> I<00:18:55.360> would<00:18:55.640> start<00:18:55.960> with<00:18:56.200> Austin<00:18:56.679> here 00:18:56.909 --> 00:18:56.919 align:start position:0% think I would start with Austin here 00:18:56.919 --> 00:18:59.270 align:start position:0% think I would start with Austin here kind<00:18:57.080> of<00:18:57.200> like<00:18:57.400> cuz<00:18:57.600> you<00:18:58.280> spend<00:18:58.760> a<00:18:58.840> lot<00:18:59.000> of<00:18:59.120> time 00:18:59.270 --> 00:18:59.280 align:start position:0% kind of like cuz you spend a lot of time 00:18:59.280 --> 00:19:01.669 align:start position:0% kind of like cuz you spend a lot of time of<00:18:59.440> your<00:18:59.600> day<00:19:00.240> building<00:19:00.960> talking<00:19:01.200> to<00:19:01.360> users 00:19:01.669 --> 00:19:01.679 align:start position:0% of your day building talking to users 00:19:01.679 --> 00:19:03.430 align:start position:0% of your day building talking to users and<00:19:01.799> building<00:19:02.080> for<00:19:02.400> users<00:19:02.760> so<00:19:02.960> how<00:19:03.120> how<00:19:03.200> do<00:19:03.320> you 00:19:03.430 --> 00:19:03.440 align:start position:0% and building for users so how how do you 00:19:03.440 --> 00:19:04.710 align:start position:0% and building for users so how how do you go<00:19:03.600> about<00:19:03.799> it 00:19:04.710 --> 00:19:04.720 align:start position:0% go about it 00:19:04.720 --> 00:19:07.590 align:start position:0% go about it then<00:19:05.720> yeah<00:19:05.919> just<00:19:06.320> to<00:19:06.520> start<00:19:06.919> I<00:19:07.000> think<00:19:07.159> the<00:19:07.240> Ford 00:19:07.590 --> 00:19:07.600 align:start position:0% then yeah just to start I think the Ford 00:19:07.600 --> 00:19:10.390 align:start position:0% then yeah just to start I think the Ford Foundation<00:19:08.120> can't<00:19:08.400> confirm<00:19:08.840> this<00:19:09.200> quote<00:19:10.200> uh 00:19:10.390 --> 00:19:10.400 align:start position:0% Foundation can't confirm this quote uh 00:19:10.400 --> 00:19:12.070 align:start position:0% Foundation can't confirm this quote uh but<00:19:10.559> I<00:19:10.640> think<00:19:10.840> they<00:19:10.960> said<00:19:11.280> something<00:19:11.679> like 00:19:12.070 --> 00:19:12.080 align:start position:0% but I think they said something like 00:19:12.080 --> 00:19:14.510 align:start position:0% but I think they said something like that's<00:19:12.600> something<00:19:12.960> like<00:19:13.159> he<00:19:13.360> would<00:19:13.600> have<00:19:13.799> said 00:19:14.510 --> 00:19:14.520 align:start position:0% that's something like he would have said 00:19:14.520 --> 00:19:16.190 align:start position:0% that's something like he would have said uh<00:19:14.640> so<00:19:14.840> we<00:19:14.919> can<00:19:15.039> all<00:19:15.200> make<00:19:15.320> a<00:19:15.440> tcid<00:19:15.840> agreement 00:19:16.190 --> 00:19:16.200 align:start position:0% uh so we can all make a tcid agreement 00:19:16.200 --> 00:19:19.750 align:start position:0% uh so we can all make a tcid agreement that<00:19:16.840> said<00:19:17.000> it<00:19:17.760> um<00:19:18.400> and<00:19:18.600> I<00:19:18.679> think<00:19:18.840> in<00:19:19.000> this<00:19:19.200> case 00:19:19.750 --> 00:19:19.760 align:start position:0% that said it um and I think in this case 00:19:19.760 --> 00:19:22.950 align:start position:0% that said it um and I think in this case the<00:19:19.919> key<00:19:20.200> is<00:19:20.799> um<00:19:21.640> to<00:19:22.200> to<00:19:22.360> try<00:19:22.520> to<00:19:22.600> find<00:19:22.840> the 00:19:22.950 --> 00:19:22.960 align:start position:0% the key is um to to try to find the 00:19:22.960 --> 00:19:24.789 align:start position:0% the key is um to to try to find the subtext<00:19:23.720> you<00:19:23.840> know<00:19:23.960> when<00:19:24.120> someone<00:19:24.360> tells<00:19:24.559> you 00:19:24.789 --> 00:19:24.799 align:start position:0% subtext you know when someone tells you 00:19:24.799 --> 00:19:26.029 align:start position:0% subtext you know when someone tells you they're<00:19:25.000> having<00:19:25.159> a<00:19:25.280> problem<00:19:25.480> or<00:19:25.600> they<00:19:25.720> want<00:19:25.840> a 00:19:26.029 --> 00:19:26.039 align:start position:0% they're having a problem or they want a 00:19:26.039 --> 00:19:28.549 align:start position:0% they're having a problem or they want a product<00:19:26.320> or<00:19:26.520> a<00:19:26.640> feature<00:19:27.080> request<00:19:28.080> um<00:19:28.280> in<00:19:28.440> this 00:19:28.549 --> 00:19:28.559 align:start position:0% product or a feature request um in this 00:19:28.559 --> 00:19:29.750 align:start position:0% product or a feature request um in this case<00:19:28.760> case<00:19:28.919> it<00:19:29.000> would<00:19:29.120> be<00:19:29.240> like<00:19:29.440> they<00:19:29.559> want<00:19:29.640> to 00:19:29.750 --> 00:19:29.760 align:start position:0% case case it would be like they want to 00:19:29.760 --> 00:19:32.669 align:start position:0% case case it would be like they want to go<00:19:30.000> faster<00:19:30.679> right<00:19:31.480> um<00:19:31.840> people<00:19:32.039> are<00:19:32.200> experts<00:19:32.559> in 00:19:32.669 --> 00:19:32.679 align:start position:0% go faster right um people are experts in 00:19:32.679 --> 00:19:34.149 align:start position:0% go faster right um people are experts in their<00:19:32.880> problems<00:19:33.320> and<00:19:33.520> and<00:19:33.640> the<00:19:33.720> challenges 00:19:34.149 --> 00:19:34.159 align:start position:0% their problems and and the challenges 00:19:34.159 --> 00:19:35.870 align:start position:0% their problems and and the challenges they<00:19:34.320> face<00:19:34.559> but<00:19:34.679> not<00:19:34.799> necessarily<00:19:35.400> in<00:19:35.640> how<00:19:35.720> to 00:19:35.870 --> 00:19:35.880 align:start position:0% they face but not necessarily in how to 00:19:35.880 --> 00:19:40.230 align:start position:0% they face but not necessarily in how to solve<00:19:36.200> them<00:19:36.720> um<00:19:37.640> and<00:19:38.039> so<00:19:39.039> uh<00:19:39.600> yeah<00:19:39.840> I<00:19:40.000> I<00:19:40.080> think 00:19:40.230 --> 00:19:40.240 align:start position:0% solve them um and so uh yeah I I think 00:19:40.240 --> 00:19:42.310 align:start position:0% solve them um and so uh yeah I I think that<00:19:40.360> it's<00:19:40.520> uncovering<00:19:41.520> uh<00:19:41.640> the<00:19:41.760> fundamental 00:19:42.310 --> 00:19:42.320 align:start position:0% that it's uncovering uh the fundamental 00:19:42.320 --> 00:19:45.070 align:start position:0% that it's uncovering uh the fundamental human<00:19:42.600> need<00:19:43.520> um<00:19:43.720> and<00:19:43.840> there<00:19:43.960> aren't<00:19:44.320> actually 00:19:45.070 --> 00:19:45.080 align:start position:0% human need um and there aren't actually 00:19:45.080 --> 00:19:47.590 align:start position:0% human need um and there aren't actually that<00:19:45.240> many<00:19:45.919> um<00:19:46.200> you<00:19:46.320> know<00:19:47.120> as<00:19:47.200> I<00:19:47.320> mentioned 00:19:47.590 --> 00:19:47.600 align:start position:0% that many um you know as I mentioned 00:19:47.600 --> 00:19:49.070 align:start position:0% that many um you know as I mentioned earlier<00:19:47.840> I<00:19:47.919> think<00:19:48.159> sometimes<00:19:48.400> people<00:19:48.600> want 00:19:49.070 --> 00:19:49.080 align:start position:0% earlier I think sometimes people want 00:19:49.080 --> 00:19:51.510 align:start position:0% earlier I think sometimes people want stability<00:19:50.080> um<00:19:50.360> they<00:19:50.480> want<00:19:50.640> their<00:19:50.840> time<00:19:51.120> back 00:19:51.510 --> 00:19:51.520 align:start position:0% stability um they want their time back 00:19:51.520 --> 00:19:54.029 align:start position:0% stability um they want their time back they<00:19:51.640> want<00:19:51.880> money<00:19:52.400> they<00:19:52.520> want<00:19:53.240> rewards<00:19:53.720> of<00:19:53.880> the 00:19:54.029 --> 00:19:54.039 align:start position:0% they want money they want rewards of the 00:19:54.039 --> 00:19:55.870 align:start position:0% they want money they want rewards of the tribe<00:19:54.400> so<00:19:54.760> you<00:19:54.880> know<00:19:55.039> social<00:19:55.400> affirmation 00:19:55.870 --> 00:19:55.880 align:start position:0% tribe so you know social affirmation 00:19:55.880 --> 00:19:58.270 align:start position:0% tribe so you know social affirmation from<00:19:56.080> the<00:19:56.200> people<00:19:56.480> around<00:19:56.840> them<00:19:57.760> um<00:19:58.120> they 00:19:58.270 --> 00:19:58.280 align:start position:0% from the people around them um they 00:19:58.280 --> 00:20:00.669 align:start position:0% from the people around them um they might<00:19:58.720> enjoy<00:19:59.039> the<00:19:59.159> reward<00:19:59.520> of<00:19:59.640> the<00:19:59.799> hunt<00:20:00.559> you 00:20:00.669 --> 00:20:00.679 align:start position:0% might enjoy the reward of the hunt you 00:20:00.679 --> 00:20:02.669 align:start position:0% might enjoy the reward of the hunt you know<00:20:01.240> um<00:20:01.520> like<00:20:01.679> for<00:20:01.840> example<00:20:02.120> I<00:20:02.240> know<00:20:02.480> like<00:20:02.600> the 00:20:02.669 --> 00:20:02.679 align:start position:0% know um like for example I know like the 00:20:02.679 --> 00:20:04.710 align:start position:0% know um like for example I know like the analyst<00:20:03.039> on<00:20:03.240> duner<00:20:03.679> I<00:20:03.760> think<00:20:03.919> enjoy<00:20:04.280> the<00:20:04.360> hunt 00:20:04.710 --> 00:20:04.720 align:start position:0% analyst on duner I think enjoy the hunt 00:20:04.720 --> 00:20:06.789 align:start position:0% analyst on duner I think enjoy the hunt I<00:20:04.799> think<00:20:04.919> they<00:20:05.039> want<00:20:05.159> to<00:20:05.360> find<00:20:05.640> that<00:20:05.840> insight 00:20:06.789 --> 00:20:06.799 align:start position:0% I think they want to find that insight 00:20:06.799 --> 00:20:08.350 align:start position:0% I think they want to find that insight and<00:20:07.039> there's<00:20:07.240> also<00:20:07.400> an<00:20:07.559> element<00:20:07.919> of<00:20:08.240> uh 00:20:08.350 --> 00:20:08.360 align:start position:0% and there's also an element of uh 00:20:08.360 --> 00:20:10.190 align:start position:0% and there's also an element of uh self-mastery<00:20:08.960> you<00:20:09.400> know<00:20:09.679> like<00:20:09.880> let's<00:20:10.039> see 00:20:10.190 --> 00:20:10.200 align:start position:0% self-mastery you know like let's see 00:20:10.200 --> 00:20:12.590 align:start position:0% self-mastery you know like let's see what<00:20:10.360> I<00:20:10.440> can<00:20:10.679> create<00:20:11.679> um<00:20:11.840> but<00:20:11.960> it's<00:20:12.200> really 00:20:12.590 --> 00:20:12.600 align:start position:0% what I can create um but it's really 00:20:12.600 --> 00:20:14.190 align:start position:0% what I can create um but it's really there<00:20:12.919> I<00:20:13.000> don't<00:20:13.159> think<00:20:13.320> there<00:20:13.400> are<00:20:13.640> that<00:20:13.840> many 00:20:14.190 --> 00:20:14.200 align:start position:0% there I don't think there are that many 00:20:14.200 --> 00:20:16.350 align:start position:0% there I don't think there are that many fundamental<00:20:14.760> human<00:20:14.960> needs<00:20:15.280> so<00:20:15.440> I<00:20:15.520> think<00:20:15.720> it's 00:20:16.350 --> 00:20:16.360 align:start position:0% fundamental human needs so I think it's 00:20:16.360 --> 00:20:19.870 align:start position:0% fundamental human needs so I think it's uh<00:20:16.640> trying<00:20:16.960> to<00:20:17.159> be<00:20:17.679> clear<00:20:18.679> um<00:20:19.440> you<00:20:19.559> know<00:20:19.720> not 00:20:19.870 --> 00:20:19.880 align:start position:0% uh trying to be clear um you know not 00:20:19.880 --> 00:20:21.990 align:start position:0% uh trying to be clear um you know not talk<00:20:20.080> about<00:20:20.280> the<00:20:20.400> features<00:20:21.200> uh<00:20:21.360> necessarily 00:20:21.990 --> 00:20:22.000 align:start position:0% talk about the features uh necessarily 00:20:22.000 --> 00:20:23.510 align:start position:0% talk about the features uh necessarily that<00:20:22.120> we're<00:20:22.440> that<00:20:22.559> we're<00:20:22.720> shipping<00:20:23.159> all<00:20:23.320> the 00:20:23.510 --> 00:20:23.520 align:start position:0% that we're that we're shipping all the 00:20:23.520 --> 00:20:26.149 align:start position:0% that we're that we're shipping all the time<00:20:24.080> and<00:20:24.360> we<00:20:24.520> could<00:20:25.080> as<00:20:25.240> designers<00:20:25.720> I<00:20:25.960> like<00:20:26.080> I 00:20:26.149 --> 00:20:26.159 align:start position:0% time and we could as designers I like I 00:20:26.159 --> 00:20:28.950 align:start position:0% time and we could as designers I like I could<00:20:26.280> get<00:20:26.440> better<00:20:26.640> at<00:20:26.799> this<00:20:26.960> and<00:20:27.640> I<00:20:27.919> most 00:20:28.950 --> 00:20:28.960 align:start position:0% could get better at this and I most 00:20:28.960 --> 00:20:30.110 align:start position:0% could get better at this and I most everyone<00:20:29.200> could<00:20:29.360> get<00:20:29.480> better<00:20:29.679> at<00:20:29.840> this<00:20:30.000> just 00:20:30.110 --> 00:20:30.120 align:start position:0% everyone could get better at this just 00:20:30.120 --> 00:20:31.950 align:start position:0% everyone could get better at this just like<00:20:30.280> tying<00:20:30.559> this<00:20:30.640> to<00:20:30.799> like<00:20:30.880> a<00:20:31.039> really<00:20:31.240> core 00:20:31.950 --> 00:20:31.960 align:start position:0% like tying this to like a really core 00:20:31.960 --> 00:20:33.230 align:start position:0% like tying this to like a really core fundamental<00:20:32.440> need<00:20:32.679> I<00:20:32.760> think<00:20:32.880> we<00:20:33.000> don't 00:20:33.230 --> 00:20:33.240 align:start position:0% fundamental need I think we don't 00:20:33.240 --> 00:20:36.630 align:start position:0% fundamental need I think we don't because<00:20:33.440> it<00:20:33.559> sounds<00:20:33.840> too<00:20:34.240> simple<00:20:35.240> um<00:20:36.200> but<00:20:36.480> uh 00:20:36.630 --> 00:20:36.640 align:start position:0% because it sounds too simple um but uh 00:20:36.640 --> 00:20:38.549 align:start position:0% because it sounds too simple um but uh but<00:20:36.799> I<00:20:36.880> think<00:20:37.280> sometimes<00:20:37.559> there's<00:20:37.919> a 00:20:38.549 --> 00:20:38.559 align:start position:0% but I think sometimes there's a 00:20:38.559 --> 00:20:42.630 align:start position:0% but I think sometimes there's a sophistication<00:20:39.480> in<00:20:39.720> simple<00:20:40.919> um 00:20:42.630 --> 00:20:42.640 align:start position:0% sophistication in simple um 00:20:42.640 --> 00:20:44.750 align:start position:0% sophistication in simple um yeah<00:20:43.640> there's<00:20:43.840> a<00:20:44.000> bunch<00:20:44.159> of<00:20:44.320> different<00:20:44.559> things 00:20:44.750 --> 00:20:44.760 align:start position:0% yeah there's a bunch of different things 00:20:44.760 --> 00:20:46.070 align:start position:0% yeah there's a bunch of different things you<00:20:44.840> could<00:20:45.000> do 00:20:46.070 --> 00:20:46.080 align:start position:0% you could do 00:20:46.080 --> 00:20:49.310 align:start position:0% you could do so<00:20:47.080> one<00:20:47.440> thing<00:20:47.799> with<00:20:47.960> the<00:20:48.120> data<00:20:48.559> is<00:20:48.840> always<00:20:49.120> to 00:20:49.310 --> 00:20:49.320 align:start position:0% so one thing with the data is always to 00:20:49.320 --> 00:20:51.430 align:start position:0% so one thing with the data is always to marry<00:20:49.760> quantitative<00:20:50.400> with<00:20:50.600> qualitative<00:20:51.240> so<00:20:51.360> I 00:20:51.430 --> 00:20:51.440 align:start position:0% marry quantitative with qualitative so I 00:20:51.440 --> 00:20:53.070 align:start position:0% marry quantitative with qualitative so I do<00:20:51.600> a<00:20:51.679> lot<00:20:51.799> of<00:20:51.919> the<00:20:52.039> Quant<00:20:52.360> stuff<00:20:52.720> I've<00:20:52.880> done 00:20:53.070 --> 00:20:53.080 align:start position:0% do a lot of the Quant stuff I've done 00:20:53.080 --> 00:20:54.789 align:start position:0% do a lot of the Quant stuff I've done qual<00:20:53.480> stuff<00:20:53.679> in<00:20:53.840> the<00:20:54.039> past<00:20:54.320> but<00:20:54.440> we've<00:20:54.600> got 00:20:54.789 --> 00:20:54.799 align:start position:0% qual stuff in the past but we've got 00:20:54.799 --> 00:20:56.750 align:start position:0% qual stuff in the past but we've got some<00:20:55.280> lovely<00:20:55.640> people<00:20:55.880> at<00:20:56.080> safe<00:20:56.320> who<00:20:56.440> do<00:20:56.559> it 00:20:56.750 --> 00:20:56.760 align:start position:0% some lovely people at safe who do it 00:20:56.760 --> 00:20:58.870 align:start position:0% some lovely people at safe who do it very<00:20:56.960> well<00:20:57.760> uh<00:20:57.919> but<00:20:58.080> it's<00:20:58.280> under 00:20:58.870 --> 00:20:58.880 align:start position:0% very well uh but it's under 00:20:58.880 --> 00:21:01.430 align:start position:0% very well uh but it's under understanding<00:20:59.760> how<00:21:00.000> people<00:21:00.240> are<00:21:00.480> using<00:21:01.200> your 00:21:01.430 --> 00:21:01.440 align:start position:0% understanding how people are using your 00:21:01.440 --> 00:21:03.510 align:start position:0% understanding how people are using your tool<00:21:01.799> from<00:21:02.000> the<00:21:02.240> data<00:21:02.640> but<00:21:02.799> then<00:21:03.000> going<00:21:03.320> and 00:21:03.510 --> 00:21:03.520 align:start position:0% tool from the data but then going and 00:21:03.520 --> 00:21:04.830 align:start position:0% tool from the data but then going and asking<00:21:03.919> them<00:21:04.200> and<00:21:04.280> there's<00:21:04.440> a<00:21:04.559> lot<00:21:04.679> of 00:21:04.830 --> 00:21:04.840 align:start position:0% asking them and there's a lot of 00:21:04.840 --> 00:21:07.149 align:start position:0% asking them and there's a lot of techniques<00:21:05.240> you<00:21:05.320> can<00:21:05.480> use<00:21:05.720> you<00:21:05.840> know<00:21:06.400> why<00:21:06.880> you 00:21:07.149 --> 00:21:07.159 align:start position:0% techniques you can use you know why you 00:21:07.159 --> 00:21:09.350 align:start position:0% techniques you can use you know why you ask<00:21:07.440> five<00:21:07.640> times<00:21:07.960> why<00:21:08.240> so<00:21:08.520> you<00:21:08.640> say<00:21:08.919> you<00:21:09.039> need 00:21:09.350 --> 00:21:09.360 align:start position:0% ask five times why so you say you need 00:21:09.360 --> 00:21:11.070 align:start position:0% ask five times why so you say you need this<00:21:09.679> why<00:21:09.840> do<00:21:09.960> you<00:21:10.080> need<00:21:10.320> it<00:21:10.559> and<00:21:10.640> then<00:21:10.760> you<00:21:10.880> ask 00:21:11.070 --> 00:21:11.080 align:start position:0% this why do you need it and then you ask 00:21:11.080 --> 00:21:12.630 align:start position:0% this why do you need it and then you ask that<00:21:11.279> five<00:21:11.480> times<00:21:11.720> and<00:21:11.880> you'll<00:21:12.080> realize<00:21:12.480> that 00:21:12.630 --> 00:21:12.640 align:start position:0% that five times and you'll realize that 00:21:12.640 --> 00:21:14.909 align:start position:0% that five times and you'll realize that the<00:21:12.799> fifth<00:21:13.159> answer<00:21:13.919> is<00:21:14.080> so<00:21:14.400> completely 00:21:14.909 --> 00:21:14.919 align:start position:0% the fifth answer is so completely 00:21:14.919 --> 00:21:16.510 align:start position:0% the fifth answer is so completely different<00:21:15.200> to<00:21:15.360> what<00:21:15.520> they<00:21:15.640> said<00:21:15.960> initially 00:21:16.510 --> 00:21:16.520 align:start position:0% different to what they said initially 00:21:16.520 --> 00:21:19.990 align:start position:0% different to what they said initially because<00:21:17.200> people<00:21:17.480> tend<00:21:17.679> to<00:21:18.279> think<00:21:19.279> I<00:21:19.440> want<00:21:19.799> this 00:21:19.990 --> 00:21:20.000 align:start position:0% because people tend to think I want this 00:21:20.000 --> 00:21:21.909 align:start position:0% because people tend to think I want this and<00:21:20.159> they<00:21:20.320> tend<00:21:20.520> to<00:21:20.720> think<00:21:21.200> about<00:21:21.400> the<00:21:21.520> feature 00:21:21.909 --> 00:21:21.919 align:start position:0% and they tend to think about the feature 00:21:21.919 --> 00:21:23.909 align:start position:0% and they tend to think about the feature that<00:21:22.080> they<00:21:22.200> want<00:21:22.559> rather<00:21:22.799> than<00:21:23.520> the<00:21:23.679> problem 00:21:23.909 --> 00:21:23.919 align:start position:0% that they want rather than the problem 00:21:23.919 --> 00:21:25.230 align:start position:0% that they want rather than the problem they're<00:21:24.120> trying<00:21:24.320> to<00:21:24.480> solve<00:21:24.760> with<00:21:25.000> that 00:21:25.230 --> 00:21:25.240 align:start position:0% they're trying to solve with that 00:21:25.240 --> 00:21:27.190 align:start position:0% they're trying to solve with that feature<00:21:25.840> and<00:21:26.000> you<00:21:26.240> as<00:21:26.360> the<00:21:26.480> engineer<00:21:26.960> as<00:21:27.080> the 00:21:27.190 --> 00:21:27.200 align:start position:0% feature and you as the engineer as the 00:21:27.200 --> 00:21:28.669 align:start position:0% feature and you as the engineer as the dev<00:21:27.440> you're<00:21:27.640> better<00:21:27.880> place<00:21:28.120> to<00:21:28.400> understand 00:21:28.669 --> 00:21:28.679 align:start position:0% dev you're better place to understand 00:21:28.679 --> 00:21:31.070 align:start position:0% dev you're better place to understand understand<00:21:29.120> kind<00:21:29.279> of<00:21:29.520> how<00:21:29.919> to 00:21:31.070 --> 00:21:31.080 align:start position:0% understand kind of how to 00:21:31.080 --> 00:21:33.990 align:start position:0% understand kind of how to technically<00:21:32.080> answer<00:21:32.559> that<00:21:32.720> need<00:21:33.559> um<00:21:33.840> that 00:21:33.990 --> 00:21:34.000 align:start position:0% technically answer that need um that 00:21:34.000 --> 00:21:35.750 align:start position:0% technically answer that need um that someone<00:21:34.360> without<00:21:34.640> the<00:21:34.799> context<00:21:35.200> of<00:21:35.360> how<00:21:35.520> your 00:21:35.750 --> 00:21:35.760 align:start position:0% someone without the context of how your 00:21:35.760 --> 00:21:38.549 align:start position:0% someone without the context of how your product<00:21:36.039> is<00:21:36.200> built<00:21:36.840> can<00:21:37.799> um<00:21:38.000> but<00:21:38.120> I<00:21:38.240> face<00:21:38.440> the 00:21:38.549 --> 00:21:38.559 align:start position:0% product is built can um but I face the 00:21:38.559 --> 00:21:40.110 align:start position:0% product is built can um but I face the same<00:21:38.760> thing<00:21:38.880> with<00:21:39.080> data<00:21:39.400> you<00:21:39.520> know<00:21:39.960> I'm 00:21:40.110 --> 00:21:40.120 align:start position:0% same thing with data you know I'm 00:21:40.120 --> 00:21:42.909 align:start position:0% same thing with data you know I'm surrounded<00:21:40.600> by<00:21:40.760> people<00:21:41.000> who<00:21:41.159> say<00:21:42.039> I<00:21:42.159> want<00:21:42.679> this 00:21:42.909 --> 00:21:42.919 align:start position:0% surrounded by people who say I want this 00:21:42.919 --> 00:21:45.190 align:start position:0% surrounded by people who say I want this metric<00:21:43.760> and<00:21:44.159> if<00:21:44.279> you<00:21:44.440> ask<00:21:44.679> them<00:21:44.880> why<00:21:45.000> do<00:21:45.120> you 00:21:45.190 --> 00:21:45.200 align:start position:0% metric and if you ask them why do you 00:21:45.200 --> 00:21:46.710 align:start position:0% metric and if you ask them why do you want<00:21:45.400> this<00:21:45.559> metric<00:21:46.000> it's<00:21:46.120> to<00:21:46.279> measure<00:21:46.559> an 00:21:46.710 --> 00:21:46.720 align:start position:0% want this metric it's to measure an 00:21:46.720 --> 00:21:48.470 align:start position:0% want this metric it's to measure an outcome<00:21:47.320> and<00:21:47.440> I<00:21:47.520> realized<00:21:47.919> that<00:21:48.039> the<00:21:48.120> metric 00:21:48.470 --> 00:21:48.480 align:start position:0% outcome and I realized that the metric 00:21:48.480 --> 00:21:50.190 align:start position:0% outcome and I realized that the metric they<00:21:48.679> actually<00:21:48.919> want<00:21:49.240> doesn't<00:21:49.640> quite<00:21:49.919> match 00:21:50.190 --> 00:21:50.200 align:start position:0% they actually want doesn't quite match 00:21:50.200 --> 00:21:52.149 align:start position:0% they actually want doesn't quite match the<00:21:50.360> outcome<00:21:50.840> it's<00:21:51.000> about<00:21:51.679> well<00:21:51.840> if<00:21:51.919> you<00:21:52.000> want 00:21:52.149 --> 00:21:52.159 align:start position:0% the outcome it's about well if you want 00:21:52.159 --> 00:21:53.950 align:start position:0% the outcome it's about well if you want to<00:21:52.279> measure<00:21:52.600> that<00:21:52.799> outcome<00:21:53.240> I<00:21:53.360> suggest<00:21:53.799> we 00:21:53.950 --> 00:21:53.960 align:start position:0% to measure that outcome I suggest we 00:21:53.960 --> 00:21:56.909 align:start position:0% to measure that outcome I suggest we track<00:21:54.720> this<00:21:54.840> or<00:21:55.080> that<00:21:55.240> metric<00:21:55.840> and<00:21:56.640> it's 00:21:56.909 --> 00:21:56.919 align:start position:0% track this or that metric and it's 00:21:56.919 --> 00:21:59.750 align:start position:0% track this or that metric and it's always<00:21:57.320> coming<00:21:57.679> back<00:21:57.919> to<00:21:58.600> as<00:21:58.720> an<00:21:58.919> expert<00:21:59.520> it's 00:21:59.750 --> 00:21:59.760 align:start position:0% always coming back to as an expert it's 00:21:59.760 --> 00:22:02.269 align:start position:0% always coming back to as an expert it's about<00:22:00.760> being<00:22:01.080> able<00:22:01.360> to<00:22:01.520> realize<00:22:01.919> you're<00:22:02.120> the 00:22:02.269 --> 00:22:02.279 align:start position:0% about being able to realize you're the 00:22:02.279 --> 00:22:05.390 align:start position:0% about being able to realize you're the expert<00:22:02.600> in<00:22:02.720> the<00:22:02.880> room<00:22:03.360> and<00:22:04.240> um<00:22:04.559> trying<00:22:04.840> to 00:22:05.390 --> 00:22:05.400 align:start position:0% expert in the room and um trying to 00:22:05.400 --> 00:22:07.430 align:start position:0% expert in the room and um trying to understand<00:22:06.039> from<00:22:06.279> your<00:22:06.559> users<00:22:07.159> what<00:22:07.279> they 00:22:07.430 --> 00:22:07.440 align:start position:0% understand from your users what they 00:22:07.440 --> 00:22:09.990 align:start position:0% understand from your users what they really<00:22:07.640> need<00:22:08.000> and<00:22:08.799> I<00:22:08.919> have<00:22:09.039> to<00:22:09.200> say<00:22:09.480> like<00:22:09.799> in 00:22:09.990 --> 00:22:10.000 align:start position:0% really need and I have to say like in 00:22:10.000 --> 00:22:13.149 align:start position:0% really need and I have to say like in web<00:22:10.240> 3<00:22:10.520> we're<00:22:10.720> still<00:22:11.240> such<00:22:11.480> a<00:22:11.720> small<00:22:12.559> space 00:22:13.149 --> 00:22:13.159 align:start position:0% web 3 we're still such a small space 00:22:13.159 --> 00:22:16.549 align:start position:0% web 3 we're still such a small space that<00:22:13.360> we<00:22:13.559> can<00:22:14.159> go<00:22:14.360> out<00:22:14.640> to<00:22:14.799> users<00:22:15.679> users<00:22:16.200> want 00:22:16.549 --> 00:22:16.559 align:start position:0% that we can go out to users users want 00:22:16.559 --> 00:22:18.190 align:start position:0% that we can go out to users users want our<00:22:16.760> products<00:22:17.120> to<00:22:17.240> grow<00:22:17.679> they're<00:22:17.919> they've 00:22:18.190 --> 00:22:18.200 align:start position:0% our products to grow they're they've 00:22:18.200 --> 00:22:19.870 align:start position:0% our products to grow they're they've adopted<00:22:18.600> our<00:22:18.840> products<00:22:19.200> and<00:22:19.360> they<00:22:19.480> want<00:22:19.640> to 00:22:19.870 --> 00:22:19.880 align:start position:0% adopted our products and they want to 00:22:19.880 --> 00:22:22.310 align:start position:0% adopted our products and they want to keep<00:22:20.120> them<00:22:20.840> you<00:22:21.000> know<00:22:21.279> evolving<00:22:21.919> and<00:22:22.159> we 00:22:22.310 --> 00:22:22.320 align:start position:0% keep them you know evolving and we 00:22:22.320 --> 00:22:24.110 align:start position:0% keep them you know evolving and we should<00:22:22.679> leverage<00:22:23.159> that<00:22:23.320> relationship<00:22:23.960> that 00:22:24.110 --> 00:22:24.120 align:start position:0% should leverage that relationship that 00:22:24.120 --> 00:22:26.950 align:start position:0% should leverage that relationship that we<00:22:24.279> have<00:22:24.559> that<00:22:25.120> in<00:22:25.279> web<00:22:25.720> two<00:22:25.960> it's<00:22:26.159> really<00:22:26.400> hard 00:22:26.950 --> 00:22:26.960 align:start position:0% we have that in web two it's really hard 00:22:26.960 --> 00:22:29.390 align:start position:0% we have that in web two it's really hard to<00:22:27.159> do<00:22:27.400> you<00:22:27.520> know<00:22:27.799> here<00:22:28.159> here<00:22:28.559> people<00:22:28.919> want<00:22:29.159> to 00:22:29.390 --> 00:22:29.400 align:start position:0% to do you know here here people want to 00:22:29.400 --> 00:22:31.350 align:start position:0% to do you know here here people want to help<00:22:29.640> you<00:22:29.799> out<00:22:30.080> you<00:22:30.159> know<00:22:30.360> and<00:22:30.520> they<00:22:30.640> want<00:22:30.799> to 00:22:31.350 --> 00:22:31.360 align:start position:0% help you out you know and they want to 00:22:31.360 --> 00:22:33.750 align:start position:0% help you out you know and they want to see<00:22:32.360> have<00:22:32.480> a<00:22:32.640> better<00:22:32.880> experience<00:22:33.240> using<00:22:33.559> your 00:22:33.750 --> 00:22:33.760 align:start position:0% see have a better experience using your 00:22:33.760 --> 00:22:35.710 align:start position:0% see have a better experience using your product<00:22:34.039> going<00:22:34.240> forward<00:22:34.760> so<00:22:35.000> let's<00:22:35.240> leverage 00:22:35.710 --> 00:22:35.720 align:start position:0% product going forward so let's leverage 00:22:35.720 --> 00:22:37.149 align:start position:0% product going forward so let's leverage that<00:22:35.960> as 00:22:37.149 --> 00:22:37.159 align:start position:0% that as 00:22:37.159 --> 00:22:39.909 align:start position:0% that as well<00:22:38.159> yeah<00:22:38.360> please<00:22:39.039> yeah<00:22:39.240> to<00:22:39.480> that<00:22:39.600> point<00:22:39.880> I 00:22:39.909 --> 00:22:39.919 align:start position:0% well yeah please yeah to that point I 00:22:39.919 --> 00:22:42.310 align:start position:0% well yeah please yeah to that point I mean<00:22:40.200> we<00:22:40.960> I<00:22:41.159> I<00:22:41.320> I<00:22:41.400> completely<00:22:41.760> agree<00:22:42.000> I<00:22:42.080> think<00:22:42.200> a 00:22:42.310 --> 00:22:42.320 align:start position:0% mean we I I I completely agree I think a 00:22:42.320 --> 00:22:44.070 align:start position:0% mean we I I I completely agree I think a lot<00:22:42.440> of<00:22:42.559> times<00:22:42.840> in<00:22:43.080> in<00:22:43.200> the<00:22:43.320> research<00:22:43.760> space 00:22:44.070 --> 00:22:44.080 align:start position:0% lot of times in in the research space 00:22:44.080 --> 00:22:46.310 align:start position:0% lot of times in in the research space there's<00:22:44.320> this<00:22:44.559> battle<00:22:45.039> between<00:22:46.039> uh<00:22:46.159> the 00:22:46.310 --> 00:22:46.320 align:start position:0% there's this battle between uh the 00:22:46.320 --> 00:22:48.029 align:start position:0% there's this battle between uh the qualitative<00:22:47.000> feedback<00:22:47.480> people<00:22:47.760> and<00:22:47.919> the 00:22:48.029 --> 00:22:48.039 align:start position:0% qualitative feedback people and the 00:22:48.039 --> 00:22:50.390 align:start position:0% qualitative feedback people and the quantitative<00:22:48.559> feedback<00:22:49.080> people<00:22:49.919> um<00:22:50.159> either 00:22:50.390 --> 00:22:50.400 align:start position:0% quantitative feedback people um either 00:22:50.400 --> 00:22:51.789 align:start position:0% quantitative feedback people um either they're<00:22:50.640> wired<00:22:51.000> that<00:22:51.120> way<00:22:51.320> or<00:22:51.520> that's<00:22:51.640> where 00:22:51.789 --> 00:22:51.799 align:start position:0% they're wired that way or that's where 00:22:51.799 --> 00:22:54.789 align:start position:0% they're wired that way or that's where their<00:22:51.960> skill<00:22:52.279> set<00:22:52.480> is<00:22:53.279> um<00:22:53.559> but<00:22:53.919> I<00:22:54.000> think<00:22:54.279> that 00:22:54.789 --> 00:22:54.799 align:start position:0% their skill set is um but I think that 00:22:54.799 --> 00:22:57.470 align:start position:0% their skill set is um but I think that they<00:22:55.080> tell<00:22:55.440> different<00:22:56.080> parts<00:22:56.279> of<00:22:56.440> the<00:22:56.600> story 00:22:57.470 --> 00:22:57.480 align:start position:0% they tell different parts of the story 00:22:57.480 --> 00:23:00.149 align:start position:0% they tell different parts of the story um<00:22:57.840> so<00:22:58.760> you<00:22:58.880> know<00:22:59.039> you<00:22:59.240> have<00:22:59.799> I<00:22:59.880> think<00:23:00.039> the 00:23:00.149 --> 00:23:00.159 align:start position:0% um so you know you have I think the 00:23:00.159 --> 00:23:01.390 align:start position:0% um so you know you have I think the quantitative<00:23:00.679> is<00:23:00.799> really<00:23:00.960> good<00:23:01.080> at<00:23:01.159> telling 00:23:01.390 --> 00:23:01.400 align:start position:0% quantitative is really good at telling 00:23:01.400 --> 00:23:03.630 align:start position:0% quantitative is really good at telling you<00:23:01.520> what's<00:23:01.760> happening<00:23:02.600> um<00:23:03.000> and<00:23:03.440> you<00:23:03.520> know 00:23:03.630 --> 00:23:03.640 align:start position:0% you what's happening um and you know 00:23:03.640 --> 00:23:05.190 align:start position:0% you what's happening um and you know observing<00:23:04.080> actual<00:23:04.440> Behavior<00:23:04.880> because<00:23:05.000> a<00:23:05.080> lot 00:23:05.190 --> 00:23:05.200 align:start position:0% observing actual Behavior because a lot 00:23:05.200 --> 00:23:07.710 align:start position:0% observing actual Behavior because a lot of<00:23:05.320> times<00:23:05.559> people<00:23:05.799> don't<00:23:06.039> tell<00:23:06.240> you<00:23:07.240> um<00:23:07.559> or 00:23:07.710 --> 00:23:07.720 align:start position:0% of times people don't tell you um or 00:23:07.720 --> 00:23:09.230 align:start position:0% of times people don't tell you um or they're<00:23:07.880> not<00:23:08.039> even<00:23:08.240> aware<00:23:08.640> of<00:23:08.880> their<00:23:09.080> their 00:23:09.230 --> 00:23:09.240 align:start position:0% they're not even aware of their their 00:23:09.240 --> 00:23:10.789 align:start position:0% they're not even aware of their their actual<00:23:09.559> Behavior<00:23:10.039> but<00:23:10.159> then<00:23:10.279> you<00:23:10.360> can<00:23:10.480> follow 00:23:10.789 --> 00:23:10.799 align:start position:0% actual Behavior but then you can follow 00:23:10.799 --> 00:23:12.789 align:start position:0% actual Behavior but then you can follow that<00:23:10.919> up<00:23:11.159> with<00:23:11.559> you<00:23:11.679> know<00:23:11.880> conversations<00:23:12.600> or 00:23:12.789 --> 00:23:12.799 align:start position:0% that up with you know conversations or 00:23:12.799 --> 00:23:14.110 align:start position:0% that up with you know conversations or observing<00:23:13.159> the<00:23:13.320> space<00:23:13.600> and<00:23:13.720> this<00:23:13.840> doesn't 00:23:14.110 --> 00:23:14.120 align:start position:0% observing the space and this doesn't 00:23:14.120 --> 00:23:16.549 align:start position:0% observing the space and this doesn't always<00:23:14.360> have<00:23:14.520> to<00:23:14.679> be<00:23:15.320> like<00:23:15.520> formal<00:23:16.000> long<00:23:16.279> form 00:23:16.549 --> 00:23:16.559 align:start position:0% always have to be like formal long form 00:23:16.559 --> 00:23:19.029 align:start position:0% always have to be like formal long form interviews<00:23:17.480> um<00:23:18.200> I<00:23:18.279> think<00:23:18.400> we<00:23:18.520> do<00:23:18.679> a<00:23:18.840> pretty 00:23:19.029 --> 00:23:19.039 align:start position:0% interviews um I think we do a pretty 00:23:19.039 --> 00:23:22.549 align:start position:0% interviews um I think we do a pretty good<00:23:19.240> job<00:23:19.480> right<00:23:19.640> now<00:23:20.320> just<00:23:20.720> uh<00:23:20.880> by<00:23:21.240> you<00:23:21.559> know 00:23:22.549 --> 00:23:22.559 align:start position:0% good job right now just uh by you know 00:23:22.559 --> 00:23:24.549 align:start position:0% good job right now just uh by you know I'm<00:23:22.679> trying<00:23:22.840> to<00:23:22.960> do<00:23:23.159> this<00:23:23.320> more<00:23:23.840> uh<00:23:24.000> engage<00:23:24.360> on 00:23:24.549 --> 00:23:24.559 align:start position:0% I'm trying to do this more uh engage on 00:23:24.559 --> 00:23:27.269 align:start position:0% I'm trying to do this more uh engage on Twitter<00:23:25.000> or<00:23:25.159> in<00:23:25.320> telegram<00:23:25.760> groups<00:23:26.400> and<00:23:26.640> get 00:23:27.269 --> 00:23:27.279 align:start position:0% Twitter or in telegram groups and get 00:23:27.279 --> 00:23:29.149 align:start position:0% Twitter or in telegram groups and get it's<00:23:27.520> it's<00:23:27.679> not<00:23:27.840> just<00:23:28.000> one<00:23:28.679> ation<00:23:28.919> it's<00:23:29.039> kind 00:23:29.149 --> 00:23:29.159 align:start position:0% it's it's not just one ation it's kind 00:23:29.159 --> 00:23:31.110 align:start position:0% it's it's not just one ation it's kind of<00:23:29.240> a<00:23:29.400> relationship<00:23:30.279> and<00:23:30.360> you<00:23:30.480> can<00:23:30.720> get<00:23:30.960> that 00:23:31.110 --> 00:23:31.120 align:start position:0% of a relationship and you can get that 00:23:31.120 --> 00:23:33.350 align:start position:0% of a relationship and you can get that kind<00:23:31.279> of<00:23:31.520> like<00:23:31.720> ambient<00:23:32.120> signal<00:23:32.919> and<00:23:33.039> then<00:23:33.159> see 00:23:33.350 --> 00:23:33.360 align:start position:0% kind of like ambient signal and then see 00:23:33.360 --> 00:23:34.950 align:start position:0% kind of like ambient signal and then see is<00:23:33.440> there<00:23:33.600> any<00:23:33.799> discrepancy<00:23:34.400> between<00:23:34.720> that 00:23:34.950 --> 00:23:34.960 align:start position:0% is there any discrepancy between that 00:23:34.960 --> 00:23:37.430 align:start position:0% is there any discrepancy between that and<00:23:35.200> like<00:23:35.400> the<00:23:35.559> actual<00:23:35.919> Behavior<00:23:36.480> or<00:23:36.640> the<00:23:36.799> data 00:23:37.430 --> 00:23:37.440 align:start position:0% and like the actual Behavior or the data 00:23:37.440 --> 00:23:38.470 align:start position:0% and like the actual Behavior or the data and<00:23:37.559> maybe<00:23:37.799> there's<00:23:38.039> like<00:23:38.159> something 00:23:38.470 --> 00:23:38.480 align:start position:0% and maybe there's like something 00:23:38.480 --> 00:23:39.710 align:start position:0% and maybe there's like something interesting<00:23:38.880> there<00:23:39.120> like<00:23:39.240> something<00:23:39.480> that's 00:23:39.710 --> 00:23:39.720 align:start position:0% interesting there like something that's 00:23:39.720 --> 00:23:42.510 align:start position:0% interesting there like something that's worth<00:23:40.440> worth<00:23:40.720> exploring<00:23:41.480> um<00:23:41.760> so 00:23:42.510 --> 00:23:42.520 align:start position:0% worth worth exploring um so 00:23:42.520 --> 00:23:45.789 align:start position:0% worth worth exploring um so yeah<00:23:43.520> yeah<00:23:43.640> I<00:23:43.720> think<00:23:43.919> what<00:23:44.039> you<00:23:44.240> described<00:23:44.960> um 00:23:45.789 --> 00:23:45.799 align:start position:0% yeah yeah I think what you described um 00:23:45.799 --> 00:23:49.990 align:start position:0% yeah yeah I think what you described um how<00:23:46.080> you<00:23:46.640> approach<00:23:47.240> like<00:23:47.919> um<00:23:48.799> pulling<00:23:49.279> data 00:23:49.990 --> 00:23:50.000 align:start position:0% how you approach like um pulling data 00:23:50.000 --> 00:23:51.549 align:start position:0% how you approach like um pulling data and<00:23:50.279> getting<00:23:50.559> like<00:23:50.720> an<00:23:50.880> overview<00:23:51.320> of 00:23:51.549 --> 00:23:51.559 align:start position:0% and getting like an overview of 00:23:51.559 --> 00:23:54.149 align:start position:0% and getting like an overview of different<00:23:52.320> um<00:23:52.640> crypto<00:23:53.120> interactions<00:23:53.760> is<00:23:53.960> what 00:23:54.149 --> 00:23:54.159 align:start position:0% different um crypto interactions is what 00:23:54.159 --> 00:23:56.430 align:start position:0% different um crypto interactions is what we<00:23:54.400> can<00:23:54.640> already<00:23:55.000> track<00:23:55.360> about<00:23:55.640> them<00:23:55.840> on<00:23:56.039> chain 00:23:56.430 --> 00:23:56.440 align:start position:0% we can already track about them on chain 00:23:56.440 --> 00:23:59.710 align:start position:0% we can already track about them on chain but<00:23:56.600> there<00:23:56.720> are<00:23:57.000> also<00:23:57.520> some<00:23:57.880> parts<00:23:58.240> of<00:23:58.480> of<00:23:59.080> the 00:23:59.710 --> 00:23:59.720 align:start position:0% but there are also some parts of of the 00:23:59.720 --> 00:24:03.549 align:start position:0% but there are also some parts of of the user<00:24:00.720> um<00:24:01.000> flow<00:24:01.720> or<00:24:02.000> flow<00:24:02.279> of<00:24:02.440> funds<00:24:03.039> that<00:24:03.240> we 00:24:03.549 --> 00:24:03.559 align:start position:0% user um flow or flow of funds that we 00:24:03.559 --> 00:24:05.909 align:start position:0% user um flow or flow of funds that we might<00:24:03.799> not<00:24:04.039> see<00:24:04.440> yet<00:24:04.679> so<00:24:05.120> from<00:24:05.480> when<00:24:05.640> we<00:24:05.799> look 00:24:05.909 --> 00:24:05.919 align:start position:0% might not see yet so from when we look 00:24:05.919 --> 00:24:07.630 align:start position:0% might not see yet so from when we look at<00:24:06.039> the<00:24:06.200> capital<00:24:06.559> markets<00:24:07.000> industry<00:24:07.480> it's 00:24:07.630 --> 00:24:07.640 align:start position:0% at the capital markets industry it's 00:24:07.640 --> 00:24:10.390 align:start position:0% at the capital markets industry it's very<00:24:08.159> um<00:24:08.320> common<00:24:08.799> that<00:24:09.000> for<00:24:09.360> very<00:24:09.679> big<00:24:09.960> trades 00:24:10.390 --> 00:24:10.400 align:start position:0% very um common that for very big trades 00:24:10.400 --> 00:24:13.029 align:start position:0% very um common that for very big trades when<00:24:10.520> we<00:24:10.679> think<00:24:10.880> about<00:24:11.120> ETFs<00:24:11.600> or<00:24:11.760> large<00:24:12.039> funds 00:24:13.029 --> 00:24:13.039 align:start position:0% when we think about ETFs or large funds 00:24:13.039 --> 00:24:16.269 align:start position:0% when we think about ETFs or large funds when<00:24:13.360> a<00:24:13.679> rebalancing<00:24:14.679> happens<00:24:15.159> or<00:24:15.360> someone 00:24:16.269 --> 00:24:16.279 align:start position:0% when a rebalancing happens or someone 00:24:16.279 --> 00:24:19.310 align:start position:0% when a rebalancing happens or someone basically<00:24:17.120> dissolves<00:24:17.640> a<00:24:17.880> position<00:24:18.880> those 00:24:19.310 --> 00:24:19.320 align:start position:0% basically dissolves a position those 00:24:19.320 --> 00:24:21.190 align:start position:0% basically dissolves a position those trades<00:24:19.679> are<00:24:19.840> not<00:24:20.039> made<00:24:20.320> like<00:24:20.520> in<00:24:20.640> the<00:24:20.840> public 00:24:21.190 --> 00:24:21.200 align:start position:0% trades are not made like in the public 00:24:21.200 --> 00:24:23.830 align:start position:0% trades are not made like in the public market<00:24:22.080> um<00:24:22.720> but<00:24:23.080> because<00:24:23.360> they<00:24:23.520> have<00:24:23.679> the 00:24:23.830 --> 00:24:23.840 align:start position:0% market um but because they have the 00:24:23.840 --> 00:24:26.029 align:start position:0% market um but because they have the potential<00:24:24.200> to<00:24:24.320> move<00:24:24.559> the<00:24:24.720> market<00:24:25.120> so<00:24:25.480> they<00:24:25.600> are 00:24:26.029 --> 00:24:26.039 align:start position:0% potential to move the market so they are 00:24:26.039 --> 00:24:28.389 align:start position:0% potential to move the market so they are then<00:24:26.240> fractionalized<00:24:27.120> and<00:24:27.279> traded<00:24:27.720> away<00:24:28.080> in 00:24:28.389 --> 00:24:28.399 align:start position:0% then fractionalized and traded away in 00:24:28.399 --> 00:24:30.310 align:start position:0% then fractionalized and traded away in for<00:24:28.559> example<00:24:28.960> dark<00:24:29.279> pools<00:24:29.840> where<00:24:30.039> there's 00:24:30.310 --> 00:24:30.320 align:start position:0% for example dark pools where there's 00:24:30.320 --> 00:24:33.590 align:start position:0% for example dark pools where there's like<00:24:30.440> an<00:24:30.600> OTC<00:24:31.440> so<00:24:31.760> an<00:24:31.919> offchain<00:24:32.600> matching 00:24:33.590 --> 00:24:33.600 align:start position:0% like an OTC so an offchain matching 00:24:33.600 --> 00:24:36.149 align:start position:0% like an OTC so an offchain matching about<00:24:34.080> like<00:24:34.399> um<00:24:34.640> where<00:24:35.039> the<00:24:35.559> the<00:24:35.679> buy<00:24:35.919> and<00:24:36.039> the 00:24:36.149 --> 00:24:36.159 align:start position:0% about like um where the the buy and the 00:24:36.159 --> 00:24:38.549 align:start position:0% about like um where the the buy and the sell<00:24:36.520> side<00:24:36.720> agree<00:24:37.039> on<00:24:37.240> a<00:24:37.480> price<00:24:37.919> and<00:24:38.080> then<00:24:38.360> it 00:24:38.549 --> 00:24:38.559 align:start position:0% sell side agree on a price and then it 00:24:38.559 --> 00:24:42.029 align:start position:0% sell side agree on a price and then it gets<00:24:39.440> basically<00:24:40.440> cleared<00:24:41.000> and<00:24:41.279> traded<00:24:41.840> and 00:24:42.029 --> 00:24:42.039 align:start position:0% gets basically cleared and traded and 00:24:42.039 --> 00:24:46.350 align:start position:0% gets basically cleared and traded and settled<00:24:42.640> and<00:24:42.760> so<00:24:43.000> on<00:24:43.760> so<00:24:44.440> um<00:24:44.760> those<00:24:45.159> type<00:24:45.679> of<00:24:46.039> in 00:24:46.350 --> 00:24:46.360 align:start position:0% settled and so on so um those type of in 00:24:46.360 --> 00:24:48.389 align:start position:0% settled and so on so um those type of in more<00:24:46.559> institutional<00:24:47.200> use<00:24:47.600> cases<00:24:48.200> and<00:24:48.320> they 00:24:48.389 --> 00:24:48.399 align:start position:0% more institutional use cases and they 00:24:48.399 --> 00:24:51.029 align:start position:0% more institutional use cases and they are<00:24:48.600> still<00:24:48.880> done<00:24:49.320> in<00:24:49.520> the<00:24:50.159> centralized 00:24:51.029 --> 00:24:51.039 align:start position:0% are still done in the centralized 00:24:51.039 --> 00:24:54.310 align:start position:0% are still done in the centralized exchange<00:24:51.720> context<00:24:52.720> um<00:24:53.200> because<00:24:53.520> here<00:24:53.760> we<00:24:53.960> have 00:24:54.310 --> 00:24:54.320 align:start position:0% exchange context um because here we have 00:24:54.320 --> 00:24:56.549 align:start position:0% exchange context um because here we have rather<00:24:54.640> a<00:24:54.840> logic<00:24:55.240> like<00:24:55.480> we<00:24:55.640> know<00:24:55.840> them<00:24:56.159> from 00:24:56.549 --> 00:24:56.559 align:start position:0% rather a logic like we know them from 00:24:56.559 --> 00:25:00.190 align:start position:0% rather a logic like we know them from stock<00:24:56.960> markets<00:24:57.760> and<00:24:58.080> bond<00:24:58.520> markets<00:24:59.039> and<00:24:59.200> so<00:24:59.440> on 00:25:00.190 --> 00:25:00.200 align:start position:0% stock markets and bond markets and so on 00:25:00.200 --> 00:25:03.470 align:start position:0% stock markets and bond markets and so on so<00:25:00.720> there<00:25:00.840> are<00:25:01.039> some<00:25:01.360> data<00:25:01.720> points<00:25:02.399> that<00:25:03.200> yeah 00:25:03.470 --> 00:25:03.480 align:start position:0% so there are some data points that yeah 00:25:03.480 --> 00:25:06.029 align:start position:0% so there are some data points that yeah we<00:25:03.600> don't<00:25:03.880> see<00:25:04.279> yet<00:25:04.799> so<00:25:05.120> it's<00:25:05.360> really 00:25:06.029 --> 00:25:06.039 align:start position:0% we don't see yet so it's really 00:25:06.039 --> 00:25:09.590 align:start position:0% we don't see yet so it's really important<00:25:06.840> to<00:25:07.279> yeah<00:25:07.760> know<00:25:08.120> the<00:25:08.480> user<00:25:09.039> and<00:25:09.399> the 00:25:09.590 --> 00:25:09.600 align:start position:0% important to yeah know the user and the 00:25:09.600 --> 00:25:11.750 align:start position:0% important to yeah know the user and the ultimate<00:25:10.080> goal<00:25:10.360> where<00:25:10.520> he<00:25:10.640> wants<00:25:10.919> to<00:25:11.360> but 00:25:11.750 --> 00:25:11.760 align:start position:0% ultimate goal where he wants to but 00:25:11.760 --> 00:25:13.470 align:start position:0% ultimate goal where he wants to but sometimes<00:25:12.000> our<00:25:12.279> technology<00:25:12.880> also<00:25:13.200> has 00:25:13.470 --> 00:25:13.480 align:start position:0% sometimes our technology also has 00:25:13.480 --> 00:25:15.909 align:start position:0% sometimes our technology also has advantages<00:25:14.480> where<00:25:14.679> the<00:25:14.840> user<00:25:15.120> doesn't<00:25:15.520> know 00:25:15.909 --> 00:25:15.919 align:start position:0% advantages where the user doesn't know 00:25:15.919 --> 00:25:18.190 align:start position:0% advantages where the user doesn't know what<00:25:16.120> feature<00:25:16.520> he<00:25:16.720> wants<00:25:17.320> because<00:25:17.799> he<00:25:17.919> doesn't 00:25:18.190 --> 00:25:18.200 align:start position:0% what feature he wants because he doesn't 00:25:18.200 --> 00:25:19.669 align:start position:0% what feature he wants because he doesn't really<00:25:18.440> know<00:25:18.679> that<00:25:18.880> this<00:25:19.000> is<00:25:19.120> a<00:25:19.360> problem 00:25:19.669 --> 00:25:19.679 align:start position:0% really know that this is a problem 00:25:19.679 --> 00:25:21.510 align:start position:0% really know that this is a problem that's<00:25:19.880> already<00:25:20.279> solvable<00:25:20.880> and<00:25:21.000> you<00:25:21.159> have<00:25:21.279> to 00:25:21.510 --> 00:25:21.520 align:start position:0% that's already solvable and you have to 00:25:21.520 --> 00:25:24.430 align:start position:0% that's already solvable and you have to Pioneer<00:25:22.039> the<00:25:22.279> technology<00:25:23.120> so<00:25:23.840> this<00:25:24.000> is<00:25:24.200> where 00:25:24.430 --> 00:25:24.440 align:start position:0% Pioneer the technology so this is where 00:25:24.440 --> 00:25:26.630 align:start position:0% Pioneer the technology so this is where we<00:25:24.600> still<00:25:24.880> have<00:25:25.039> some<00:25:25.240> frictions<00:25:26.000> and<00:25:26.480> it 00:25:26.630 --> 00:25:26.640 align:start position:0% we still have some frictions and it 00:25:26.640 --> 00:25:29.230 align:start position:0% we still have some frictions and it makes<00:25:26.919> sense<00:25:27.200> to<00:25:27.440> pay<00:25:27.640> attention<00:25:28.520> have<00:25:28.799> like 00:25:29.230 --> 00:25:29.240 align:start position:0% makes sense to pay attention have like 00:25:29.240 --> 00:25:31.870 align:start position:0% makes sense to pay attention have like user<00:25:29.720> interviews<00:25:30.720> often<00:25:31.080> and<00:25:31.240> not<00:25:31.399> only<00:25:31.679> do 00:25:31.870 --> 00:25:31.880 align:start position:0% user interviews often and not only do 00:25:31.880 --> 00:25:34.990 align:start position:0% user interviews often and not only do the<00:25:32.320> data<00:25:32.640> analytics<00:25:33.480> so<00:25:33.960> I<00:25:34.039> have<00:25:34.159> a<00:25:34.440> question 00:25:34.990 --> 00:25:35.000 align:start position:0% the data analytics so I have a question 00:25:35.000 --> 00:25:38.750 align:start position:0% the data analytics so I have a question on<00:25:35.399> the<00:25:35.960> you<00:25:36.039> mentioned<00:25:36.559> like<00:25:36.960> uh<00:25:37.720> use<00:25:38.120> case<00:25:38.320> of 00:25:38.750 --> 00:25:38.760 align:start position:0% on the you mentioned like uh use case of 00:25:38.760 --> 00:25:42.750 align:start position:0% on the you mentioned like uh use case of uh<00:25:39.039> rebalancing<00:25:40.039> portfolios<00:25:40.960> right<00:25:41.720> so<00:25:42.000> if<00:25:42.200> I 00:25:42.750 --> 00:25:42.760 align:start position:0% uh rebalancing portfolios right so if I 00:25:42.760 --> 00:25:44.950 align:start position:0% uh rebalancing portfolios right so if I remember<00:25:43.200> correctly<00:25:43.679> this<00:25:43.799> is<00:25:44.120> like<00:25:44.880> there 00:25:44.950 --> 00:25:44.960 align:start position:0% remember correctly this is like there 00:25:44.960 --> 00:25:48.070 align:start position:0% remember correctly this is like there are<00:25:46.039> programmable<00:25:47.039> uh<00:25:47.240> Solutions<00:25:47.720> out<00:25:47.919> there 00:25:48.070 --> 00:25:48.080 align:start position:0% are programmable uh Solutions out there 00:25:48.080 --> 00:25:49.710 align:start position:0% are programmable uh Solutions out there that'll<00:25:48.320> automate<00:25:48.919> rebalancing<00:25:49.520> of 00:25:49.710 --> 00:25:49.720 align:start position:0% that'll automate rebalancing of 00:25:49.720 --> 00:25:51.630 align:start position:0% that'll automate rebalancing of portfolios<00:25:50.399> right<00:25:50.720> so<00:25:50.919> essentially<00:25:51.440> these 00:25:51.630 --> 00:25:51.640 align:start position:0% portfolios right so essentially these 00:25:51.640 --> 00:25:54.750 align:start position:0% portfolios right so essentially these are<00:25:52.600> I<00:25:52.720> guess<00:25:52.880> you<00:25:52.960> can<00:25:53.159> call<00:25:53.320> them<00:25:53.640> Bots<00:25:54.640> you 00:25:54.750 --> 00:25:54.760 align:start position:0% are I guess you can call them Bots you 00:25:54.760 --> 00:25:56.389 align:start position:0% are I guess you can call them Bots you know<00:25:55.039> and<00:25:55.200> when<00:25:55.320> you<00:25:55.559> look<00:25:55.720> at<00:25:56.000> like<00:25:56.120> from<00:25:56.240> a 00:25:56.389 --> 00:25:56.399 align:start position:0% know and when you look at like from a 00:25:56.399 --> 00:25:58.830 align:start position:0% know and when you look at like from a data<00:25:56.679> angle<00:25:57.200> when<00:25:57.320> you<00:25:57.480> look<00:25:57.640> at<00:25:58.279> AC<00:25:58.480> ity 00:25:58.830 --> 00:25:58.840 align:start position:0% data angle when you look at AC ity 00:25:58.840 --> 00:26:01.230 align:start position:0% data angle when you look at AC ity onchain<00:25:59.840> uh<00:25:59.960> transactional 00:26:01.230 --> 00:26:01.240 align:start position:0% onchain uh transactional 00:26:01.240 --> 00:26:04.630 align:start position:0% onchain uh transactional activity<00:26:02.240> are<00:26:02.399> we<00:26:02.600> seeing<00:26:03.279> essentially<00:26:04.240> Bots 00:26:04.630 --> 00:26:04.640 align:start position:0% activity are we seeing essentially Bots 00:26:04.640 --> 00:26:07.350 align:start position:0% activity are we seeing essentially Bots as<00:26:04.840> real<00:26:05.399> users<00:26:06.399> are<00:26:06.520> we<00:26:06.640> an<00:26:06.760> industry<00:26:07.159> where 00:26:07.350 --> 00:26:07.360 align:start position:0% as real users are we an industry where 00:26:07.360 --> 00:26:10.830 align:start position:0% as real users are we an industry where Bots<00:26:07.640> are<00:26:07.880> legitimate<00:26:08.679> users<00:26:09.679> it<00:26:09.840> depends<00:26:10.640> my 00:26:10.830 --> 00:26:10.840 align:start position:0% Bots are legitimate users it depends my 00:26:10.840 --> 00:26:12.430 align:start position:0% Bots are legitimate users it depends my my<00:26:11.000> answer<00:26:11.279> is<00:26:11.440> always<00:26:11.799> it<00:26:11.960> depends<00:26:12.320> it 00:26:12.430 --> 00:26:12.440 align:start position:0% my answer is always it depends it 00:26:12.440 --> 00:26:14.110 align:start position:0% my answer is always it depends it depends<00:26:12.720> on<00:26:12.880> what<00:26:13.000> you're<00:26:13.159> trying<00:26:13.399> to<00:26:13.640> measure 00:26:14.110 --> 00:26:14.120 align:start position:0% depends on what you're trying to measure 00:26:14.120 --> 00:26:16.830 align:start position:0% depends on what you're trying to measure right<00:26:14.840> so<00:26:15.480> I<00:26:15.600> read<00:26:15.799> a<00:26:15.960> stat<00:26:16.240> the<00:26:16.360> other<00:26:16.559> day<00:26:16.760> I 00:26:16.830 --> 00:26:16.840 align:start position:0% right so I read a stat the other day I 00:26:16.840 --> 00:26:19.070 align:start position:0% right so I read a stat the other day I think<00:26:17.000> Chad<00:26:17.200> GPT<00:26:17.559> gave<00:26:17.720> me<00:26:17.880> that<00:26:18.000> stat<00:26:18.279> but<00:26:18.440> 50% 00:26:19.070 --> 00:26:19.080 align:start position:0% think Chad GPT gave me that stat but 50% 00:26:19.080 --> 00:26:21.789 align:start position:0% think Chad GPT gave me that stat but 50% of<00:26:19.240> internet<00:26:19.760> activity<00:26:20.200> is<00:26:20.360> bots<00:26:21.360> so<00:26:21.520> I<00:26:21.640> think 00:26:21.789 --> 00:26:21.799 align:start position:0% of internet activity is bots so I think 00:26:21.799 --> 00:26:24.190 align:start position:0% of internet activity is bots so I think it's<00:26:22.000> no<00:26:22.360> lower<00:26:22.760> in<00:26:23.200> crypto<00:26:23.600> it's<00:26:23.760> probably 00:26:24.190 --> 00:26:24.200 align:start position:0% it's no lower in crypto it's probably 00:26:24.200 --> 00:26:27.310 align:start position:0% it's no lower in crypto it's probably higher<00:26:25.200> um<00:26:25.600> if<00:26:25.720> they're<00:26:25.960> airdrop<00:26:26.440> farmers<00:26:27.240> and 00:26:27.310 --> 00:26:27.320 align:start position:0% higher um if they're airdrop farmers and 00:26:27.320 --> 00:26:29.070 align:start position:0% higher um if they're airdrop farmers and you're<00:26:27.520> trying<00:26:27.720> to<00:26:27.919> measure<00:26:28.399> real<00:26:28.640> adoption 00:26:29.070 --> 00:26:29.080 align:start position:0% you're trying to measure real adoption 00:26:29.080 --> 00:26:31.029 align:start position:0% you're trying to measure real adoption of<00:26:29.200> your<00:26:29.399> chain<00:26:30.120> and<00:26:30.240> they're<00:26:30.440> just<00:26:30.600> farming 00:26:31.029 --> 00:26:31.039 align:start position:0% of your chain and they're just farming 00:26:31.039 --> 00:26:33.310 align:start position:0% of your chain and they're just farming for<00:26:31.320> your<00:26:31.480> Chain's<00:26:32.000> airdrop<00:26:33.000> then<00:26:33.120> you 00:26:33.310 --> 00:26:33.320 align:start position:0% for your Chain's airdrop then you 00:26:33.320 --> 00:26:34.870 align:start position:0% for your Chain's airdrop then you probably<00:26:33.600> don't<00:26:33.799> want<00:26:33.919> to<00:26:34.080> see<00:26:34.279> them<00:26:34.480> as<00:26:34.640> real 00:26:34.870 --> 00:26:34.880 align:start position:0% probably don't want to see them as real 00:26:34.880 --> 00:26:38.389 align:start position:0% probably don't want to see them as real users<00:26:35.880> but<00:26:36.039> if<00:26:36.159> they're<00:26:36.600> active<00:26:37.240> traders<00:26:38.240> who 00:26:38.389 --> 00:26:38.399 align:start position:0% users but if they're active traders who 00:26:38.399 --> 00:26:41.029 align:start position:0% users but if they're active traders who are<00:26:38.720> actively<00:26:39.159> using<00:26:39.520> your<00:26:39.679> D5<00:26:40.200> protocol<00:26:40.919> and 00:26:41.029 --> 00:26:41.039 align:start position:0% are actively using your D5 protocol and 00:26:41.039 --> 00:26:43.630 align:start position:0% are actively using your D5 protocol and are<00:26:41.200> making<00:26:41.600> 60%<00:26:42.240> of<00:26:42.360> the 00:26:43.630 --> 00:26:43.640 align:start position:0% are making 60% of the 00:26:43.640 --> 00:26:46.110 align:start position:0% are making 60% of the volume<00:26:44.640> I'd<00:26:44.840> say<00:26:45.159> they<00:26:45.320> probably<00:26:45.600> are<00:26:45.840> active 00:26:46.110 --> 00:26:46.120 align:start position:0% volume I'd say they probably are active 00:26:46.120 --> 00:26:48.950 align:start position:0% volume I'd say they probably are active users<00:26:46.520> they're<00:26:46.760> generating<00:26:47.320> the<00:26:47.480> volume<00:26:47.960> that 00:26:48.950 --> 00:26:48.960 align:start position:0% users they're generating the volume that 00:26:48.960 --> 00:26:51.590 align:start position:0% users they're generating the volume that you're<00:26:49.240> getting<00:26:49.720> fees<00:26:50.159> from<00:26:50.600> or<00:26:50.840> that<00:26:51.000> you're 00:26:51.590 --> 00:26:51.600 align:start position:0% you're getting fees from or that you're 00:26:51.600 --> 00:26:53.350 align:start position:0% you're getting fees from or that you're you<00:26:51.760> know<00:26:51.960> they<00:26:52.080> are<00:26:52.399> generating<00:26:52.960> real 00:26:53.350 --> 00:26:53.360 align:start position:0% you know they are generating real 00:26:53.360 --> 00:26:55.269 align:start position:0% you know they are generating real activity<00:26:53.840> they<00:26:53.960> are<00:26:54.159> powered<00:26:54.520> by<00:26:54.720> humans<00:26:55.159> at 00:26:55.269 --> 00:26:55.279 align:start position:0% activity they are powered by humans at 00:26:55.279 --> 00:26:57.710 align:start position:0% activity they are powered by humans at the<00:26:55.399> end<00:26:55.520> of<00:26:55.679> the<00:26:55.840> day<00:26:56.679> who<00:26:56.880> are<00:26:57.120> using<00:26:57.480> your 00:26:57.710 --> 00:26:57.720 align:start position:0% the end of the day who are using your 00:26:57.720 --> 00:26:59.630 align:start position:0% the end of the day who are using your protocol<00:26:58.399> actively<00:26:58.799> in<00:26:58.919> comparison<00:26:59.440> to 00:26:59.630 --> 00:26:59.640 align:start position:0% protocol actively in comparison to 00:26:59.640 --> 00:27:04.350 align:start position:0% protocol actively in comparison to another<00:27:00.159> dii<00:27:00.720> protocol<00:27:01.880> to<00:27:02.880> to<00:27:03.039> make<00:27:03.360> money 00:27:04.350 --> 00:27:04.360 align:start position:0% another dii protocol to to make money 00:27:04.360 --> 00:27:07.029 align:start position:0% another dii protocol to to make money could<00:27:04.799> could<00:27:05.799> you<00:27:05.960> want<00:27:06.080> to<00:27:06.600> yeah<00:27:06.720> maybe 00:27:07.029 --> 00:27:07.039 align:start position:0% could could you want to yeah maybe 00:27:07.039 --> 00:27:08.510 align:start position:0% could could you want to yeah maybe connecting<00:27:07.480> to<00:27:07.679> what<00:27:07.799> you<00:27:07.960> said<00:27:08.279> with<00:27:08.399> the 00:27:08.510 --> 00:27:08.520 align:start position:0% connecting to what you said with the 00:27:08.520 --> 00:27:10.870 align:start position:0% connecting to what you said with the Bots<00:27:08.880> and<00:27:09.120> that<00:27:09.320> they<00:27:09.679> are<00:27:10.080> probably<00:27:10.480> also<00:27:10.720> a 00:27:10.870 --> 00:27:10.880 align:start position:0% Bots and that they are probably also a 00:27:10.880 --> 00:27:12.789 align:start position:0% Bots and that they are probably also a higher<00:27:11.200> amount<00:27:11.520> in<00:27:11.679> our<00:27:11.960> industry<00:27:12.480> and<00:27:12.640> when 00:27:12.789 --> 00:27:12.799 align:start position:0% higher amount in our industry and when 00:27:12.799 --> 00:27:15.909 align:start position:0% higher amount in our industry and when we<00:27:13.399> think<00:27:13.720> about<00:27:14.080> air<00:27:14.360> trop<00:27:14.600> farming<00:27:15.320> also 00:27:15.909 --> 00:27:15.919 align:start position:0% we think about air trop farming also 00:27:15.919 --> 00:27:18.269 align:start position:0% we think about air trop farming also hamster<00:27:16.720> like<00:27:17.240> maybe<00:27:17.480> some<00:27:17.640> of<00:27:17.760> you<00:27:17.880> saw<00:27:18.080> the 00:27:18.269 --> 00:27:18.279 align:start position:0% hamster like maybe some of you saw the 00:27:18.279 --> 00:27:20.950 align:start position:0% hamster like maybe some of you saw the presentation<00:27:18.880> earlier<00:27:19.520> ton<00:27:19.840> I<00:27:19.919> mean<00:27:20.559> like<00:27:20.720> the 00:27:20.950 --> 00:27:20.960 align:start position:0% presentation earlier ton I mean like the 00:27:20.960 --> 00:27:22.510 align:start position:0% presentation earlier ton I mean like the technical<00:27:21.399> approach<00:27:21.720> to<00:27:21.840> it<00:27:22.000> is<00:27:22.240> really 00:27:22.510 --> 00:27:22.520 align:start position:0% technical approach to it is really 00:27:22.520 --> 00:27:24.830 align:start position:0% technical approach to it is really powerful<00:27:23.039> I<00:27:23.159> think<00:27:23.520> and<00:27:23.799> abstracting<00:27:24.559> gas 00:27:24.830 --> 00:27:24.840 align:start position:0% powerful I think and abstracting gas 00:27:24.840 --> 00:27:27.470 align:start position:0% powerful I think and abstracting gas fees<00:27:25.240> or<00:27:25.559> have<00:27:25.840> payment<00:27:26.159> Master<00:27:26.720> accounts 00:27:27.470 --> 00:27:27.480 align:start position:0% fees or have payment Master accounts 00:27:27.480 --> 00:27:30.789 align:start position:0% fees or have payment Master accounts like<00:27:27.799> has<00:27:27.919> a<00:27:28.200> great<00:27:28.480> potential<00:27:29.200> for<00:27:30.200> um<00:27:30.559> more 00:27:30.789 --> 00:27:30.799 align:start position:0% like has a great potential for um more 00:27:30.799 --> 00:27:32.789 align:start position:0% like has a great potential for um more the<00:27:31.000> average<00:27:31.399> users<00:27:32.000> but<00:27:32.120> in<00:27:32.240> the<00:27:32.399> trading 00:27:32.789 --> 00:27:32.799 align:start position:0% the average users but in the trading 00:27:32.799 --> 00:27:37.870 align:start position:0% the average users but in the trading space<00:27:33.200> for<00:27:33.720> example<00:27:34.720> um<00:27:35.480> here<00:27:35.840> we<00:27:36.440> have<00:27:37.000> also 00:27:37.870 --> 00:27:37.880 align:start position:0% space for example um here we have also 00:27:37.880 --> 00:27:41.470 align:start position:0% space for example um here we have also like<00:27:38.120> some<00:27:39.080> very<00:27:39.440> granular<00:27:40.440> um<00:27:40.720> differences 00:27:41.470 --> 00:27:41.480 align:start position:0% like some very granular um differences 00:27:41.480 --> 00:27:43.950 align:start position:0% like some very granular um differences when<00:27:41.880> we<00:27:42.279> for<00:27:42.519> example<00:27:42.919> look<00:27:43.080> at<00:27:43.240> the<00:27:43.640> amount 00:27:43.950 --> 00:27:43.960 align:start position:0% when we for example look at the amount 00:27:43.960 --> 00:27:46.830 align:start position:0% when we for example look at the amount of<00:27:44.320> accounts<00:27:44.919> right<00:27:45.360> um<00:27:45.519> ton<00:27:45.880> showed<00:27:46.200> us<00:27:46.440> these 00:27:46.830 --> 00:27:46.840 align:start position:0% of accounts right um ton showed us these 00:27:46.840 --> 00:27:49.909 align:start position:0% of accounts right um ton showed us these accounts<00:27:47.760> numbers<00:27:48.760> but<00:27:48.919> or<00:27:49.080> wallet<00:27:49.440> numbers 00:27:49.909 --> 00:27:49.919 align:start position:0% accounts numbers but or wallet numbers 00:27:49.919 --> 00:27:52.750 align:start position:0% accounts numbers but or wallet numbers that<00:27:50.120> have<00:27:50.279> been<00:27:50.440> spin<00:27:50.840> up<00:27:51.519> um<00:27:51.679> in<00:27:51.960> telegram 00:27:52.750 --> 00:27:52.760 align:start position:0% that have been spin up um in telegram 00:27:52.760 --> 00:27:56.029 align:start position:0% that have been spin up um in telegram but<00:27:53.039> actually<00:27:53.480> like<00:27:53.640> I<00:27:53.799> use<00:27:54.120> this<00:27:54.799> um<00:27:55.080> to<00:27:55.600> to 00:27:56.029 --> 00:27:56.039 align:start position:0% but actually like I use this um to to 00:27:56.039 --> 00:27:59.750 align:start position:0% but actually like I use this um to to air<00:27:56.360> to<00:27:56.600> farm<00:27:57.000> or<00:27:57.320> hamster<00:27:58.240> the<00:27:58.360> air<00:27:58.559> drop<00:27:59.440> or<00:27:59.640> I 00:27:59.750 --> 00:27:59.760 align:start position:0% air to farm or hamster the air drop or I 00:27:59.760 --> 00:28:01.190 align:start position:0% air to farm or hamster the air drop or I gave<00:27:59.919> it<00:28:00.000> to<00:28:00.159> my<00:28:00.279> daughter<00:28:00.559> when<00:28:00.720> she<00:28:00.880> had<00:28:01.080> like 00:28:01.190 --> 00:28:01.200 align:start position:0% gave it to my daughter when she had like 00:28:01.200 --> 00:28:03.789 align:start position:0% gave it to my daughter when she had like too<00:28:01.360> much<00:28:01.600> energy<00:28:02.600> um<00:28:02.799> but<00:28:02.960> then<00:28:03.200> after<00:28:03.440> 3<00:28:03.640> days 00:28:03.789 --> 00:28:03.799 align:start position:0% too much energy um but then after 3 days 00:28:03.799 --> 00:28:05.630 align:start position:0% too much energy um but then after 3 days we<00:28:04.000> forgot<00:28:04.360> about<00:28:04.559> it<00:28:04.760> and<00:28:04.919> since<00:28:05.240> then<00:28:05.440> it's 00:28:05.630 --> 00:28:05.640 align:start position:0% we forgot about it and since then it's 00:28:05.640 --> 00:28:07.909 align:start position:0% we forgot about it and since then it's like<00:28:05.760> a<00:28:05.919> d<00:28:06.279> account<00:28:06.919> um<00:28:07.080> so<00:28:07.360> I<00:28:07.480> think<00:28:07.679> that's 00:28:07.909 --> 00:28:07.919 align:start position:0% like a d account um so I think that's 00:28:07.919 --> 00:28:11.669 align:start position:0% like a d account um so I think that's still<00:28:08.360> like<00:28:08.760> part<00:28:09.039> of<00:28:09.279> that<00:28:10.120> um<00:28:10.600> but<00:28:11.279> there<00:28:11.440> are 00:28:11.669 --> 00:28:11.679 align:start position:0% still like part of that um but there are 00:28:11.679 --> 00:28:15.190 align:start position:0% still like part of that um but there are also<00:28:12.159> some<00:28:12.880> bot<00:28:13.200> or<00:28:13.440> trading<00:28:13.880> activity<00:28:14.760> that 00:28:15.190 --> 00:28:15.200 align:start position:0% also some bot or trading activity that 00:28:15.200 --> 00:28:18.310 align:start position:0% also some bot or trading activity that has<00:28:15.480> like<00:28:15.720> very<00:28:16.000> different<00:28:16.840> logic<00:28:17.840> um<00:28:18.120> and 00:28:18.310 --> 00:28:18.320 align:start position:0% has like very different logic um and 00:28:18.320 --> 00:28:20.509 align:start position:0% has like very different logic um and where<00:28:18.519> it's<00:28:18.799> powerful<00:28:19.320> for<00:28:19.559> example<00:28:20.080> like<00:28:20.320> in 00:28:20.509 --> 00:28:20.519 align:start position:0% where it's powerful for example like in 00:28:20.519 --> 00:28:23.630 align:start position:0% where it's powerful for example like in from<00:28:20.919> the<00:28:21.080> trading<00:28:21.600> side<00:28:22.360> um<00:28:22.519> and<00:28:22.640> I<00:28:22.760> think<00:28:23.480> the 00:28:23.630 --> 00:28:23.640 align:start position:0% from the trading side um and I think the 00:28:23.640 --> 00:28:25.830 align:start position:0% from the trading side um and I think the financial<00:28:24.120> side<00:28:24.360> is<00:28:24.640> still<00:28:24.960> like<00:28:25.159> one<00:28:25.440> of<00:28:25.640> the 00:28:25.830 --> 00:28:25.840 align:start position:0% financial side is still like one of the 00:28:25.840 --> 00:28:28.269 align:start position:0% financial side is still like one of the most<00:28:26.640> um<00:28:27.240> relevant<00:28:27.720> when<00:28:27.840> we<00:28:27.960> think<00:28:28.120> think 00:28:28.269 --> 00:28:28.279 align:start position:0% most um relevant when we think think 00:28:28.279 --> 00:28:30.549 align:start position:0% most um relevant when we think think about<00:28:28.480> the<00:28:29.080> blockchain<00:28:30.039> like<00:28:30.159> the<00:28:30.279> impact 00:28:30.549 --> 00:28:30.559 align:start position:0% about the blockchain like the impact 00:28:30.559 --> 00:28:33.590 align:start position:0% about the blockchain like the impact that<00:28:30.760> blockchain<00:28:31.200> can<00:28:31.480> have<00:28:31.840> for<00:28:32.279> the<00:28:32.600> users 00:28:33.590 --> 00:28:33.600 align:start position:0% that blockchain can have for the users 00:28:33.600 --> 00:28:36.350 align:start position:0% that blockchain can have for the users uh<00:28:33.720> that<00:28:33.880> don't<00:28:34.120> have<00:28:34.559> access<00:28:35.039> yet<00:28:35.519> so<00:28:36.080> yeah<00:28:36.200> I 00:28:36.350 --> 00:28:36.360 align:start position:0% uh that don't have access yet so yeah I 00:28:36.360 --> 00:28:38.909 align:start position:0% uh that don't have access yet so yeah I can<00:28:36.679> also<00:28:37.679> talk<00:28:37.919> more<00:28:38.080> and<00:28:38.240> more<00:28:38.480> but<00:28:38.600> I<00:28:38.760> want 00:28:38.909 --> 00:28:38.919 align:start position:0% can also talk more and more but I want 00:28:38.919 --> 00:28:41.350 align:start position:0% can also talk more and more but I want don't<00:28:39.080> want<00:28:39.200> to<00:28:39.440> take<00:28:39.600> up<00:28:40.000> more<00:28:40.279> space<00:28:41.240> the 00:28:41.350 --> 00:28:41.360 align:start position:0% don't want to take up more space the 00:28:41.360 --> 00:28:43.509 align:start position:0% don't want to take up more space the question<00:28:41.600> is<00:28:41.799> really<00:28:42.120> how<00:28:43.000> what<00:28:43.159> what's<00:28:43.360> the 00:28:43.509 --> 00:28:43.519 align:start position:0% question is really how what what's the 00:28:43.519 --> 00:28:45.110 align:start position:0% question is really how what what's the quality<00:28:43.919> of<00:28:44.120> that<00:28:44.279> user<00:28:44.640> whether<00:28:44.840> it's<00:28:44.960> a 00:28:45.110 --> 00:28:45.120 align:start position:0% quality of that user whether it's a 00:28:45.120 --> 00:28:46.990 align:start position:0% quality of that user whether it's a human<00:28:45.399> or<00:28:45.640> bot<00:28:45.960> it<00:28:46.080> doesn't<00:28:46.360> really<00:28:46.559> matter 00:28:46.990 --> 00:28:47.000 align:start position:0% human or bot it doesn't really matter 00:28:47.000 --> 00:28:48.830 align:start position:0% human or bot it doesn't really matter what's<00:28:47.320> what's<00:28:47.480> the<00:28:47.640> quality<00:28:48.039> and<00:28:48.200> what's<00:28:48.440> the 00:28:48.830 --> 00:28:48.840 align:start position:0% what's what's the quality and what's the 00:28:48.840 --> 00:28:51.190 align:start position:0% what's what's the quality and what's the kind<00:28:49.000> of<00:28:49.200> long-term<00:28:49.799> quality<00:28:50.640> of<00:28:50.880> of<00:28:51.039> that 00:28:51.190 --> 00:28:51.200 align:start position:0% kind of long-term quality of of that 00:28:51.200 --> 00:28:53.830 align:start position:0% kind of long-term quality of of that user<00:28:52.120> you<00:28:52.240> mentioned<00:28:52.679> I<00:28:52.760> mean<00:28:53.320> it's<00:28:53.679> it's 00:28:53.830 --> 00:28:53.840 align:start position:0% user you mentioned I mean it's it's 00:28:53.840 --> 00:28:55.029 align:start position:0% user you mentioned I mean it's it's interesting<00:28:54.240> actually<00:28:54.440> it's<00:28:54.640> kind<00:28:54.720> of<00:28:54.840> going 00:28:55.029 --> 00:28:55.039 align:start position:0% interesting actually it's kind of going 00:28:55.039 --> 00:28:57.070 align:start position:0% interesting actually it's kind of going to<00:28:55.240> the<00:28:55.440> topic<00:28:55.840> what<00:28:56.120> I<00:28:56.200> wanted<00:28:56.480> to<00:28:56.760> also 00:28:57.070 --> 00:28:57.080 align:start position:0% to the topic what I wanted to also 00:28:57.080 --> 00:28:58.750 align:start position:0% to the topic what I wanted to also highlight<00:28:57.559> which<00:28:57.720> is 00:28:58.750 --> 00:28:58.760 align:start position:0% highlight which is 00:28:58.760 --> 00:29:03.190 align:start position:0% highlight which is uh<00:28:59.200> definition<00:28:59.919> of<00:29:00.159> a<00:29:00.640> active<00:29:01.120> user<00:29:02.080> in<00:29:02.440> web<00:29:02.720> 3 00:29:03.190 --> 00:29:03.200 align:start position:0% uh definition of a active user in web 3 00:29:03.200 --> 00:29:05.669 align:start position:0% uh definition of a active user in web 3 where<00:29:03.640> you<00:29:03.760> know<00:29:04.080> identity<00:29:04.600> is<00:29:04.760> so<00:29:05.039> fragmented 00:29:05.669 --> 00:29:05.679 align:start position:0% where you know identity is so fragmented 00:29:05.679 --> 00:29:08.750 align:start position:0% where you know identity is so fragmented in<00:29:05.799> our<00:29:06.120> space<00:29:07.120> uh<00:29:07.240> we<00:29:07.360> use<00:29:07.679> accounts<00:29:08.200> like<00:29:08.600> uh 00:29:08.750 --> 00:29:08.760 align:start position:0% in our space uh we use accounts like uh 00:29:08.760 --> 00:29:11.630 align:start position:0% in our space uh we use accounts like uh almost<00:29:09.080> like<00:29:09.320> avatars<00:29:10.240> uh<00:29:10.480> right<00:29:10.919> so<00:29:11.320> so<00:29:11.519> what 00:29:11.630 --> 00:29:11.640 align:start position:0% almost like avatars uh right so so what 00:29:11.640 --> 00:29:14.549 align:start position:0% almost like avatars uh right so so what is<00:29:11.919> what<00:29:12.039> is<00:29:12.559> uh<00:29:12.960> the<00:29:13.399> the<00:29:13.559> current<00:29:14.000> definition 00:29:14.549 --> 00:29:14.559 align:start position:0% is what is uh the the current definition 00:29:14.559 --> 00:29:17.509 align:start position:0% is what is uh the the current definition of<00:29:14.760> a<00:29:15.279> an<00:29:15.519> active<00:29:15.919> user<00:29:16.799> uh<00:29:16.960> and<00:29:17.080> I'm<00:29:17.240> kind<00:29:17.360> of 00:29:17.509 --> 00:29:17.519 align:start position:0% of a an active user uh and I'm kind of 00:29:17.519 --> 00:29:20.070 align:start position:0% of a an active user uh and I'm kind of curious<00:29:18.000> how<00:29:18.559> from<00:29:18.720> a<00:29:18.880> quantitative<00:29:19.600> side<00:29:19.919> how 00:29:20.070 --> 00:29:20.080 align:start position:0% curious how from a quantitative side how 00:29:20.080 --> 00:29:21.830 align:start position:0% curious how from a quantitative side how you<00:29:20.279> look<00:29:20.480> at<00:29:20.600> it<00:29:20.799> and<00:29:20.960> from<00:29:21.080> a<00:29:21.240> qualitative 00:29:21.830 --> 00:29:21.840 align:start position:0% you look at it and from a qualitative 00:29:21.840 --> 00:29:24.149 align:start position:0% you look at it and from a qualitative side<00:29:22.519> how<00:29:22.720> Austin<00:29:23.399> would<00:29:23.640> probably<00:29:23.880> look<00:29:24.039> at 00:29:24.149 --> 00:29:24.159 align:start position:0% side how Austin would probably look at 00:29:24.159 --> 00:29:26.190 align:start position:0% side how Austin would probably look at it<00:29:24.360> and<00:29:24.559> as<00:29:24.679> a<00:29:24.840> user<00:29:25.360> perhaps<00:29:25.720> you<00:29:25.799> know<00:29:25.960> how 00:29:26.190 --> 00:29:26.200 align:start position:0% it and as a user perhaps you know how 00:29:26.200 --> 00:29:29.870 align:start position:0% it and as a user perhaps you know how Romina<00:29:26.760> would<00:29:27.240> have<00:29:27.440> that<00:29:27.640> perspective<00:29:28.279> of 00:29:29.870 --> 00:29:29.880 align:start position:0% Romina would have that perspective of 00:29:29.880 --> 00:29:31.909 align:start position:0% Romina would have that perspective of categorization<00:29:30.880> your<00:29:31.080> opening<00:29:31.440> a<00:29:31.600> can<00:29:31.799> of 00:29:31.909 --> 00:29:31.919 align:start position:0% categorization your opening a can of 00:29:31.919 --> 00:29:34.509 align:start position:0% categorization your opening a can of warms<00:29:32.559> um<00:29:33.240> I<00:29:33.320> don't<00:29:33.480> know<00:29:33.600> who<00:29:33.760> was<00:29:33.880> at<00:29:34.039> dun<00:29:34.360> con 00:29:34.509 --> 00:29:34.519 align:start position:0% warms um I don't know who was at dun con 00:29:34.519 --> 00:29:36.269 align:start position:0% warms um I don't know who was at dun con yesterday<00:29:35.000> but<00:29:35.159> I<00:29:35.240> think<00:29:35.480> every<00:29:35.679> other<00:29:35.919> talk 00:29:36.269 --> 00:29:36.279 align:start position:0% yesterday but I think every other talk 00:29:36.279 --> 00:29:38.830 align:start position:0% yesterday but I think every other talk was<00:29:36.440> talking<00:29:36.799> about<00:29:37.159> how<00:29:38.039> it's<00:29:38.320> very 00:29:38.830 --> 00:29:38.840 align:start position:0% was talking about how it's very 00:29:38.840 --> 00:29:40.750 align:start position:0% was talking about how it's very difficult<00:29:39.000> to<00:29:39.159> measure<00:29:39.559> active<00:29:39.919> users<00:29:40.519> how 00:29:40.750 --> 00:29:40.760 align:start position:0% difficult to measure active users how 00:29:40.760 --> 00:29:43.870 align:start position:0% difficult to measure active users how this<00:29:40.919> measure<00:29:41.360> is<00:29:41.559> explored 00:29:43.870 --> 00:29:43.880 align:start position:0% this measure is explored 00:29:43.880 --> 00:29:46.990 align:start position:0% this measure is explored Etc<00:29:44.880> I<00:29:45.000> think<00:29:45.919> again<00:29:46.159> it<00:29:46.320> depends<00:29:46.600> on<00:29:46.760> your 00:29:46.990 --> 00:29:47.000 align:start position:0% Etc I think again it depends on your 00:29:47.000 --> 00:29:48.990 align:start position:0% Etc I think again it depends on your project<00:29:47.440> so<00:29:47.760> we're<00:29:47.919> not<00:29:48.200> just<00:29:48.440> measuring 00:29:48.990 --> 00:29:49.000 align:start position:0% project so we're not just measuring 00:29:49.000 --> 00:29:51.070 align:start position:0% project so we're not just measuring things<00:29:49.320> we're<00:29:49.519> trying<00:29:49.799> to<00:29:50.640> understand 00:29:51.070 --> 00:29:51.080 align:start position:0% things we're trying to understand 00:29:51.080 --> 00:29:53.310 align:start position:0% things we're trying to understand measure<00:29:51.519> outcomes<00:29:52.159> to<00:29:52.279> measure<00:29:52.720> the<00:29:52.919> success 00:29:53.310 --> 00:29:53.320 align:start position:0% measure outcomes to measure the success 00:29:53.320 --> 00:29:55.669 align:start position:0% measure outcomes to measure the success of<00:29:53.480> a<00:29:54.000> particular<00:29:54.480> product<00:29:54.799> of<00:29:54.919> a<00:29:55.120> particular 00:29:55.669 --> 00:29:55.679 align:start position:0% of a particular product of a particular 00:29:55.679 --> 00:29:59.070 align:start position:0% of a particular product of a particular feature<00:29:56.159> so<00:29:56.880> an<00:29:57.080> active<00:29:57.399> user<00:29:58.360> can<00:29:58.519> mean<00:29:58.799> very 00:29:59.070 --> 00:29:59.080 align:start position:0% feature so an active user can mean very 00:29:59.080 --> 00:30:00.950 align:start position:0% feature so an active user can mean very different<00:29:59.399> things<00:29:59.640> for<00:29:59.880> different<00:30:00.200> protocols 00:30:00.950 --> 00:30:00.960 align:start position:0% different things for different protocols 00:30:00.960 --> 00:30:04.789 align:start position:0% different things for different protocols you<00:30:01.080> know<00:30:01.600> so<00:30:02.240> safe<00:30:03.240> started<00:30:03.720> off<00:30:03.919> for<00:30:04.120> example 00:30:04.789 --> 00:30:04.799 align:start position:0% you know so safe started off for example 00:30:04.799 --> 00:30:08.350 align:start position:0% you know so safe started off for example as<00:30:05.399> a<00:30:05.679> self<00:30:06.200> custody<00:30:06.679> multi-i<00:30:07.399> solution<00:30:08.159> it's 00:30:08.350 --> 00:30:08.360 align:start position:0% as a self custody multi-i solution it's 00:30:08.360 --> 00:30:10.350 align:start position:0% as a self custody multi-i solution it's the<00:30:08.559> safest<00:30:08.960> smart<00:30:09.279> contract<00:30:09.760> out<00:30:10.039> there<00:30:10.200> to 00:30:10.350 --> 00:30:10.360 align:start position:0% the safest smart contract out there to 00:30:10.360 --> 00:30:11.950 align:start position:0% the safest smart contract out there to save<00:30:10.640> your<00:30:10.880> to<00:30:11.000> keep<00:30:11.200> your 00:30:11.950 --> 00:30:11.960 align:start position:0% save your to keep your 00:30:11.960 --> 00:30:14.230 align:start position:0% save your to keep your funds<00:30:12.960> the<00:30:13.120> way<00:30:13.360> we<00:30:13.480> could<00:30:13.640> have<00:30:13.799> measured 00:30:14.230 --> 00:30:14.240 align:start position:0% funds the way we could have measured 00:30:14.240 --> 00:30:17.230 align:start position:0% funds the way we could have measured active<00:30:14.559> users<00:30:15.240> four<00:30:15.519> or<00:30:15.679> five<00:30:15.919> years<00:30:16.159> ago<00:30:16.600> was 00:30:17.230 --> 00:30:17.240 align:start position:0% active users four or five years ago was 00:30:17.240 --> 00:30:19.389 align:start position:0% active users four or five years ago was how<00:30:17.360> many<00:30:17.600> users<00:30:17.919> are<00:30:18.200> depositing<00:30:18.919> funds 00:30:19.389 --> 00:30:19.399 align:start position:0% how many users are depositing funds 00:30:19.399 --> 00:30:22.350 align:start position:0% how many users are depositing funds storing<00:30:20.000> value<00:30:20.399> in<00:30:20.640> saves<00:30:21.200> you<00:30:21.320> know<00:30:22.120> now 00:30:22.350 --> 00:30:22.360 align:start position:0% storing value in saves you know now 00:30:22.360 --> 00:30:24.430 align:start position:0% storing value in saves you know now we're<00:30:22.559> trying<00:30:22.840> to<00:30:23.120> get<00:30:23.559> with<00:30:24.000> the<00:30:24.120> world 00:30:24.430 --> 00:30:24.440 align:start position:0% we're trying to get with the world 00:30:24.440 --> 00:30:26.830 align:start position:0% we're trying to get with the world evolving<00:30:24.919> and<00:30:25.080> smart<00:30:25.440> accounts<00:30:25.919> becoming<00:30:26.720> uh 00:30:26.830 --> 00:30:26.840 align:start position:0% evolving and smart accounts becoming uh 00:30:26.840 --> 00:30:29.350 align:start position:0% evolving and smart accounts becoming uh more<00:30:27.120> prominent<00:30:27.600> we're<00:30:27.760> try<00:30:28.000> trying<00:30:28.200> to<00:30:28.760> bring 00:30:29.350 --> 00:30:29.360 align:start position:0% more prominent we're try trying to bring 00:30:29.360 --> 00:30:31.909 align:start position:0% more prominent we're try trying to bring activity<00:30:30.360> led<00:30:30.720> by<00:30:30.880> smart<00:30:31.240> accounts<00:30:31.559> and<00:30:31.720> not 00:30:31.909 --> 00:30:31.919 align:start position:0% activity led by smart accounts and not 00:30:31.919 --> 00:30:34.310 align:start position:0% activity led by smart accounts and not just<00:30:32.159> EA<00:30:32.720> so<00:30:32.919> what's<00:30:33.159> important<00:30:33.600> to<00:30:33.799> us<00:30:34.000> is<00:30:34.159> how 00:30:34.310 --> 00:30:34.320 align:start position:0% just EA so what's important to us is how 00:30:34.320 --> 00:30:36.789 align:start position:0% just EA so what's important to us is how many<00:30:34.840> users<00:30:35.240> are<00:30:35.480> actually<00:30:36.080> using<00:30:36.600> those 00:30:36.789 --> 00:30:36.799 align:start position:0% many users are actually using those 00:30:36.799 --> 00:30:38.590 align:start position:0% many users are actually using those funds<00:30:37.120> that<00:30:37.279> they<00:30:37.440> deposited<00:30:37.919> on<00:30:38.080> safe<00:30:38.399> so 00:30:38.590 --> 00:30:38.600 align:start position:0% funds that they deposited on safe so 00:30:38.600 --> 00:30:40.669 align:start position:0% funds that they deposited on safe so while<00:30:38.840> back<00:30:39.159> so<00:30:39.600> an<00:30:39.799> active<00:30:40.080> user<00:30:40.440> that<00:30:40.559> could 00:30:40.669 --> 00:30:40.679 align:start position:0% while back so an active user that could 00:30:40.679 --> 00:30:42.669 align:start position:0% while back so an active user that could have<00:30:40.799> been<00:30:41.000> just<00:30:41.240> a<00:30:41.360> user<00:30:41.720> depositing<00:30:42.240> fund 00:30:42.669 --> 00:30:42.679 align:start position:0% have been just a user depositing fund 00:30:42.679 --> 00:30:45.070 align:start position:0% have been just a user depositing fund now<00:30:42.919> becomes<00:30:43.240> an<00:30:44.000> user<00:30:44.440> that<00:30:44.559> is<00:30:44.760> actually 00:30:45.070 --> 00:30:45.080 align:start position:0% now becomes an user that is actually 00:30:45.080 --> 00:30:47.269 align:start position:0% now becomes an user that is actually using<00:30:45.559> those<00:30:45.760> funds<00:30:46.039> and<00:30:46.240> trans<00:30:46.640> transacting 00:30:47.269 --> 00:30:47.279 align:start position:0% using those funds and trans transacting 00:30:47.279 --> 00:30:50.190 align:start position:0% using those funds and trans transacting volume<00:30:47.960> right<00:30:48.159> so<00:30:49.159> it<00:30:49.320> really<00:30:49.640> depends<00:30:50.000> on 00:30:50.190 --> 00:30:50.200 align:start position:0% volume right so it really depends on 00:30:50.200 --> 00:30:52.870 align:start position:0% volume right so it really depends on your<00:30:50.519> product<00:30:51.080> and<00:30:51.200> you<00:30:51.360> have<00:30:51.480> to<00:30:51.679> think<00:30:52.039> about 00:30:52.870 --> 00:30:52.880 align:start position:0% your product and you have to think about 00:30:52.880 --> 00:30:55.509 align:start position:0% your product and you have to think about what<00:30:53.120> definition<00:30:53.559> makes<00:30:53.840> sense<00:30:54.200> in<00:30:54.799> in<00:30:54.960> that 00:30:55.509 --> 00:30:55.519 align:start position:0% what definition makes sense in in that 00:30:55.519 --> 00:30:58.029 align:start position:0% what definition makes sense in in that context<00:30:56.519> yeah<00:30:56.679> I<00:30:56.840> also<00:30:57.120> have<00:30:57.320> like<00:30:57.440> a<00:30:57.559> bunch<00:30:57.760> of 00:30:58.029 --> 00:30:58.039 align:start position:0% context yeah I also have like a bunch of 00:30:58.039 --> 00:31:00.470 align:start position:0% context yeah I also have like a bunch of user<00:30:58.399> groups<00:30:58.760> in<00:30:58.919> mind<00:30:59.320> or<00:30:59.559> how<00:30:59.760> I<00:30:59.960> break<00:31:00.240> them 00:31:00.470 --> 00:31:00.480 align:start position:0% user groups in mind or how I break them 00:31:00.480 --> 00:31:02.310 align:start position:0% user groups in mind or how I break them down<00:31:00.840> so<00:31:01.200> I<00:31:01.279> think<00:31:01.440> when<00:31:01.600> we<00:31:01.679> start<00:31:02.000> with<00:31:02.120> the 00:31:02.310 --> 00:31:02.320 align:start position:0% down so I think when we start with the 00:31:02.320 --> 00:31:04.350 align:start position:0% down so I think when we start with the crypto<00:31:02.679> natives<00:31:03.120> we<00:31:03.240> would<00:31:03.440> have<00:31:03.639> the<00:31:03.799> Wales 00:31:04.350 --> 00:31:04.360 align:start position:0% crypto natives we would have the Wales 00:31:04.360 --> 00:31:07.149 align:start position:0% crypto natives we would have the Wales or<00:31:04.559> we<00:31:05.000> would<00:31:05.200> have<00:31:05.399> the<00:31:05.519> dents<00:31:06.120> that<00:31:06.360> ape<00:31:07.039> we 00:31:07.149 --> 00:31:07.159 align:start position:0% or we would have the dents that ape we 00:31:07.159 --> 00:31:09.830 align:start position:0% or we would have the dents that ape we would<00:31:07.360> have<00:31:07.559> the<00:31:07.919> crypto<00:31:08.360> curious<00:31:09.120> that<00:31:09.679> um 00:31:09.830 --> 00:31:09.840 align:start position:0% would have the crypto curious that um 00:31:09.840 --> 00:31:11.590 align:start position:0% would have the crypto curious that um take<00:31:10.039> the<00:31:10.240> time<00:31:10.440> and<00:31:10.600> get<00:31:10.840> involved<00:31:11.320> but<00:31:11.480> it's 00:31:11.590 --> 00:31:11.600 align:start position:0% take the time and get involved but it's 00:31:11.600 --> 00:31:13.789 align:start position:0% take the time and get involved but it's not<00:31:11.799> like<00:31:11.960> they're<00:31:12.120> doing<00:31:12.440> a<00:31:12.679> lot<00:31:13.159> or<00:31:13.559> have 00:31:13.789 --> 00:31:13.799 align:start position:0% not like they're doing a lot or have 00:31:13.799 --> 00:31:15.430 align:start position:0% not like they're doing a lot or have like<00:31:14.039> a<00:31:14.200> lot<00:31:14.320> of<00:31:14.480> funds<00:31:14.919> that<00:31:15.080> they<00:31:15.200> are 00:31:15.430 --> 00:31:15.440 align:start position:0% like a lot of funds that they are 00:31:15.440 --> 00:31:18.149 align:start position:0% like a lot of funds that they are gambling<00:31:15.960> around<00:31:16.399> with<00:31:17.200> and<00:31:17.320> then<00:31:17.519> we<00:31:17.760> have 00:31:18.149 --> 00:31:18.159 align:start position:0% gambling around with and then we have 00:31:18.159 --> 00:31:20.149 align:start position:0% gambling around with and then we have like<00:31:18.440> the<00:31:18.760> for<00:31:18.960> example<00:31:19.279> the<00:31:19.440> emerg<00:31:19.840> market 00:31:20.149 --> 00:31:20.159 align:start position:0% like the for example the emerg market 00:31:20.159 --> 00:31:22.870 align:start position:0% like the for example the emerg market user<00:31:20.559> that<00:31:20.760> does<00:31:21.200> uh<00:31:21.360> that<00:31:21.480> uses<00:31:22.159> um<00:31:22.320> it<00:31:22.519> for 00:31:22.870 --> 00:31:22.880 align:start position:0% user that does uh that uses um it for 00:31:22.880 --> 00:31:26.430 align:start position:0% user that does uh that uses um it for remittance<00:31:23.639> or<00:31:24.399> also<00:31:24.919> for<00:31:25.840> um<00:31:25.960> a<00:31:26.080> wealth 00:31:26.430 --> 00:31:26.440 align:start position:0% remittance or also for um a wealth 00:31:26.440 --> 00:31:29.310 align:start position:0% remittance or also for um a wealth creating<00:31:27.000> product<00:31:27.760> um<00:31:28.159> so<00:31:28.480> here<00:31:28.760> just<00:31:29.039> like 00:31:29.310 --> 00:31:29.320 align:start position:0% creating product um so here just like 00:31:29.320 --> 00:31:32.070 align:start position:0% creating product um so here just like stable<00:31:29.760> coin<00:31:30.039> adoption<00:31:30.440> or<00:31:30.639> whatever<00:31:31.120> so<00:31:31.720> yes 00:31:32.070 --> 00:31:32.080 align:start position:0% stable coin adoption or whatever so yes 00:31:32.080 --> 00:31:34.350 align:start position:0% stable coin adoption or whatever so yes these<00:31:32.279> are<00:31:32.519> probably<00:31:32.919> also<00:31:33.279> single<00:31:33.679> wallets 00:31:34.350 --> 00:31:34.360 align:start position:0% these are probably also single wallets 00:31:34.360 --> 00:31:36.750 align:start position:0% these are probably also single wallets or<00:31:34.720> here<00:31:35.000> we<00:31:35.240> we<00:31:35.360> can<00:31:35.600> trace<00:31:36.159> like<00:31:36.360> wallet 00:31:36.750 --> 00:31:36.760 align:start position:0% or here we we can trace like wallet 00:31:36.760 --> 00:31:39.830 align:start position:0% or here we we can trace like wallet interactions<00:31:37.720> but<00:31:38.240> when<00:31:38.399> we<00:31:38.960> um<00:31:39.200> think<00:31:39.440> about 00:31:39.830 --> 00:31:39.840 align:start position:0% interactions but when we um think about 00:31:39.840 --> 00:31:42.470 align:start position:0% interactions but when we um think about like<00:31:40.080> Capital<00:31:40.480> markets<00:31:41.120> then<00:31:41.440> a<00:31:41.639> wallet<00:31:42.200> is 00:31:42.470 --> 00:31:42.480 align:start position:0% like Capital markets then a wallet is 00:31:42.480 --> 00:31:45.190 align:start position:0% like Capital markets then a wallet is not<00:31:42.720> a<00:31:42.919> user<00:31:43.600> so<00:31:44.039> I<00:31:44.159> would<00:31:44.360> be<00:31:44.519> careful<00:31:44.880> to 00:31:45.190 --> 00:31:45.200 align:start position:0% not a user so I would be careful to 00:31:45.200 --> 00:31:47.789 align:start position:0% not a user so I would be careful to always<00:31:45.720> for<00:31:46.000> to<00:31:46.200> generalize<00:31:46.840> that<00:31:46.960> a<00:31:47.200> wall 00:31:47.789 --> 00:31:47.799 align:start position:0% always for to generalize that a wall 00:31:47.799 --> 00:31:50.950 align:start position:0% always for to generalize that a wall wallet<00:31:48.120> is<00:31:48.360> always<00:31:49.000> equivalent<00:31:49.639> to<00:31:49.880> a<00:31:50.080> user 00:31:50.950 --> 00:31:50.960 align:start position:0% wallet is always equivalent to a user 00:31:50.960 --> 00:31:53.590 align:start position:0% wallet is always equivalent to a user because<00:31:51.240> we<00:31:51.399> have<00:31:51.880> sub<00:31:52.240> account<00:31:52.519> Logics<00:31:53.200> right 00:31:53.590 --> 00:31:53.600 align:start position:0% because we have sub account Logics right 00:31:53.600 --> 00:31:56.389 align:start position:0% because we have sub account Logics right where<00:31:54.159> like<00:31:54.480> accounts<00:31:55.159> execute<00:31:55.919> certain 00:31:56.389 --> 00:31:56.399 align:start position:0% where like accounts execute certain 00:31:56.399 --> 00:31:59.029 align:start position:0% where like accounts execute certain strategies<00:31:57.039> or<00:31:57.240> it's<00:31:57.360> a<00:31:57.559> wall<00:31:58.200> or<00:31:58.519> whatever 00:31:59.029 --> 00:31:59.039 align:start position:0% strategies or it's a wall or whatever 00:31:59.039 --> 00:32:02.549 align:start position:0% strategies or it's a wall or whatever and<00:31:59.159> the<00:31:59.399> user<00:31:59.840> is<00:32:00.000> not<00:32:00.840> the<00:32:01.000> wallet<00:32:01.519> but<00:32:02.360> it's 00:32:02.549 --> 00:32:02.559 align:start position:0% and the user is not the wallet but it's 00:32:02.559 --> 00:32:04.750 align:start position:0% and the user is not the wallet but it's like<00:32:02.679> on<00:32:02.799> a<00:32:02.960> very<00:32:03.200> different<00:32:03.559> aggregation 00:32:04.750 --> 00:32:04.760 align:start position:0% like on a very different aggregation 00:32:04.760 --> 00:32:08.830 align:start position:0% like on a very different aggregation level<00:32:06.200> um<00:32:07.200> and<00:32:07.799> yeah<00:32:07.960> I<00:32:08.039> think<00:32:08.320> like<00:32:08.519> when<00:32:08.679> we 00:32:08.830 --> 00:32:08.840 align:start position:0% level um and yeah I think like when we 00:32:08.840 --> 00:32:11.190 align:start position:0% level um and yeah I think like when we think<00:32:09.120> about<00:32:09.480> in<00:32:09.639> the<00:32:09.799> numbers<00:32:10.320> of<00:32:11.000> for 00:32:11.190 --> 00:32:11.200 align:start position:0% think about in the numbers of for 00:32:11.200 --> 00:32:13.310 align:start position:0% think about in the numbers of for example<00:32:11.559> the<00:32:11.760> speed<00:32:12.039> of<00:32:12.279> transaction<00:32:13.120> right 00:32:13.310 --> 00:32:13.320 align:start position:0% example the speed of transaction right 00:32:13.320 --> 00:32:16.590 align:start position:0% example the speed of transaction right like<00:32:13.559> which<00:32:14.000> infrastru<00:32:14.880> structure<00:32:15.760> or<00:32:16.320> um 00:32:16.590 --> 00:32:16.600 align:start position:0% like which infrastru structure or um 00:32:16.600 --> 00:32:18.750 align:start position:0% like which infrastru structure or um route<00:32:16.919> are<00:32:17.120> they<00:32:17.320> taking<00:32:17.799> through<00:32:18.320> like<00:32:18.559> the 00:32:18.750 --> 00:32:18.760 align:start position:0% route are they taking through like the 00:32:18.760 --> 00:32:21.029 align:start position:0% route are they taking through like the trades<00:32:19.200> it's<00:32:19.440> very<00:32:19.760> different<00:32:20.399> for<00:32:20.600> example 00:32:21.029 --> 00:32:21.039 align:start position:0% trades it's very different for example 00:32:21.039 --> 00:32:23.629 align:start position:0% trades it's very different for example high<00:32:21.240> frequency<00:32:21.880> trading<00:32:22.760> would<00:32:23.200> would<00:32:23.399> also 00:32:23.629 --> 00:32:23.639 align:start position:0% high frequency trading would would also 00:32:23.639 --> 00:32:26.389 align:start position:0% high frequency trading would would also need<00:32:23.840> to<00:32:24.039> use<00:32:24.440> very<00:32:24.760> different<00:32:25.639> combinations 00:32:26.389 --> 00:32:26.399 align:start position:0% need to use very different combinations 00:32:26.399 --> 00:32:29.350 align:start position:0% need to use very different combinations of<00:32:26.639> chain<00:32:27.080> or<00:32:27.279> would<00:32:27.559> have<00:32:28.039> also<00:32:28.799> um<00:32:29.039> cross 00:32:29.350 --> 00:32:29.360 align:start position:0% of chain or would have also um cross 00:32:29.360 --> 00:32:31.190 align:start position:0% of chain or would have also um cross chain<00:32:29.600> or<00:32:29.760> multi-chain 00:32:31.190 --> 00:32:31.200 align:start position:0% chain or multi-chain 00:32:31.200 --> 00:32:34.070 align:start position:0% chain or multi-chain complexities<00:32:32.200> um<00:32:32.440> they<00:32:32.519> are<00:32:32.720> much<00:32:33.000> easier<00:32:33.880> um 00:32:34.070 --> 00:32:34.080 align:start position:0% complexities um they are much easier um 00:32:34.080 --> 00:32:36.909 align:start position:0% complexities um they are much easier um for<00:32:34.600> like<00:32:34.880> let's<00:32:35.120> say<00:32:35.559> investors<00:32:36.519> value 00:32:36.909 --> 00:32:36.919 align:start position:0% for like let's say investors value 00:32:36.919 --> 00:32:39.470 align:start position:0% for like let's say investors value investors<00:32:37.480> that<00:32:37.679> hold<00:32:38.000> positions<00:32:38.559> and<00:32:38.840> have 00:32:39.470 --> 00:32:39.480 align:start position:0% investors that hold positions and have 00:32:39.480 --> 00:32:44.110 align:start position:0% investors that hold positions and have sometimes<00:32:40.200> um<00:32:40.799> like<00:32:41.080> a<00:32:41.360> trade<00:32:42.200> and<00:32:42.519> here<00:32:43.120> it's 00:32:44.110 --> 00:32:44.120 align:start position:0% sometimes um like a trade and here it's 00:32:44.120 --> 00:32:47.389 align:start position:0% sometimes um like a trade and here it's yeah<00:32:45.080> more<00:32:45.440> about<00:32:45.840> abstracting<00:32:46.639> probably 00:32:47.389 --> 00:32:47.399 align:start position:0% yeah more about abstracting probably 00:32:47.399 --> 00:32:49.590 align:start position:0% yeah more about abstracting probably like<00:32:47.559> the<00:32:47.760> general<00:32:48.279> Key<00:32:48.600> Management<00:32:49.440> the 00:32:49.590 --> 00:32:49.600 align:start position:0% like the general Key Management the 00:32:49.600 --> 00:32:54.590 align:start position:0% like the general Key Management the chain<00:32:50.320> management<00:32:51.320> and<00:32:52.279> yeah<00:32:52.559> so<00:32:53.480> I<00:32:53.559> see<00:32:53.960> like 00:32:54.590 --> 00:32:54.600 align:start position:0% chain management and yeah so I see like 00:32:54.600 --> 00:32:57.870 align:start position:0% chain management and yeah so I see like very<00:32:55.039> different<00:32:56.080> angles<00:32:57.080> a<00:32:57.240> lot<00:32:57.360> of<00:32:57.559> what<00:32:57.679> you 00:32:57.870 --> 00:32:57.880 align:start position:0% very different angles a lot of what you 00:32:57.880 --> 00:33:01.669 align:start position:0% very different angles a lot of what you you<00:32:58.399> actually<00:32:59.399> shared<00:32:59.919> as<00:33:00.000> a<00:33:00.200> user<00:33:01.200> uh<00:33:01.480> these 00:33:01.669 --> 00:33:01.679 align:start position:0% you actually shared as a user uh these 00:33:01.679 --> 00:33:04.669 align:start position:0% you actually shared as a user uh these tend<00:33:01.919> to<00:33:02.080> be<00:33:02.279> like<00:33:02.880> offchain<00:33:03.880> uh<00:33:04.000> interactions 00:33:04.669 --> 00:33:04.679 align:start position:0% tend to be like offchain uh interactions 00:33:04.679 --> 00:33:07.750 align:start position:0% tend to be like offchain uh interactions or<00:33:05.039> workflows<00:33:06.039> this<00:33:06.120> is<00:33:06.320> actually<00:33:07.320> some<00:33:07.559> can 00:33:07.750 --> 00:33:07.760 align:start position:0% or workflows this is actually some can 00:33:07.760 --> 00:33:09.590 align:start position:0% or workflows this is actually some can be<00:33:07.919> on<00:33:08.120> chain<00:33:08.399> as<00:33:08.559> well<00:33:08.720> but<00:33:08.919> like<00:33:09.039> I<00:33:09.200> guess<00:33:09.440> a 00:33:09.590 --> 00:33:09.600 align:start position:0% be on chain as well but like I guess a 00:33:09.600 --> 00:33:12.430 align:start position:0% be on chain as well but like I guess a lot<00:33:09.799> of<00:33:10.159> I<00:33:10.320> just<00:33:10.480> want<00:33:11.000> on<00:33:11.200> chain<00:33:11.519> examples<00:33:12.120> I 00:33:12.430 --> 00:33:12.440 align:start position:0% lot of I just want on chain examples I 00:33:12.440 --> 00:33:15.629 align:start position:0% lot of I just want on chain examples I try<00:33:12.720> to<00:33:12.960> give<00:33:13.240> yeah<00:33:13.960> but<00:33:14.120> did<00:33:14.320> they<00:33:14.559> like<00:33:15.000> uh<00:33:15.399> or 00:33:15.629 --> 00:33:15.639 align:start position:0% try to give yeah but did they like uh or 00:33:15.639 --> 00:33:18.070 align:start position:0% try to give yeah but did they like uh or not<00:33:15.799> financial<00:33:16.240> institutions<00:33:16.799> I<00:33:16.919> didn't<00:33:17.559> um 00:33:18.070 --> 00:33:18.080 align:start position:0% not financial institutions I didn't um 00:33:18.080 --> 00:33:20.149 align:start position:0% not financial institutions I didn't um explicitly<00:33:18.720> describe<00:33:19.240> that<00:33:19.600> because<00:33:19.960> they 00:33:20.149 --> 00:33:20.159 align:start position:0% explicitly describe that because they 00:33:20.159 --> 00:33:23.549 align:start position:0% explicitly describe that because they also<00:33:20.720> have<00:33:21.000> wallets<00:33:21.600> and<00:33:22.360> need<00:33:22.639> certain<00:33:22.960> user 00:33:23.549 --> 00:33:23.559 align:start position:0% also have wallets and need certain user 00:33:23.559 --> 00:33:25.629 align:start position:0% also have wallets and need certain user functionalities<00:33:24.559> and<00:33:24.760> here<00:33:24.919> we<00:33:25.039> have<00:33:25.159> a<00:33:25.320> big 00:33:25.629 --> 00:33:25.639 align:start position:0% functionalities and here we have a big 00:33:25.639 --> 00:33:28.669 align:start position:0% functionalities and here we have a big impact<00:33:26.639> for<00:33:26.799> for<00:33:27.039> safe<00:33:27.600> uh<00:33:27.919> for 00:33:28.669 --> 00:33:28.679 align:start position:0% impact for for safe uh for 00:33:28.679 --> 00:33:31.430 align:start position:0% impact for for safe uh for example<00:33:29.679> uh<00:33:29.919> there's<00:33:30.080> a<00:33:30.200> lot<00:33:30.360> of<00:33:30.559> offchain 00:33:31.430 --> 00:33:31.440 align:start position:0% example uh there's a lot of offchain 00:33:31.440 --> 00:33:33.909 align:start position:0% example uh there's a lot of offchain activity<00:33:31.880> of<00:33:32.039> like<00:33:32.200> collecting<00:33:32.720> approving 00:33:33.909 --> 00:33:33.919 align:start position:0% activity of like collecting approving 00:33:33.919 --> 00:33:37.870 align:start position:0% activity of like collecting approving signatures<00:33:34.919> uh<00:33:35.320> which<00:33:36.240> which<00:33:36.600> which<00:33:37.039> uh<00:33:37.480> means 00:33:37.870 --> 00:33:37.880 align:start position:0% signatures uh which which which uh means 00:33:37.880 --> 00:33:40.509 align:start position:0% signatures uh which which which uh means that<00:33:38.120> the<00:33:38.240> users<00:33:38.720> are<00:33:39.120> actually<00:33:39.639> interacting 00:33:40.509 --> 00:33:40.519 align:start position:0% that the users are actually interacting 00:33:40.519 --> 00:33:43.310 align:start position:0% that the users are actually interacting with<00:33:40.679> your<00:33:40.960> app<00:33:41.960> uh<00:33:42.200> and<00:33:42.360> there<00:33:42.679> is<00:33:42.840> just<00:33:43.039> one 00:33:43.310 --> 00:33:43.320 align:start position:0% with your app uh and there is just one 00:33:43.320 --> 00:33:46.310 align:start position:0% with your app uh and there is just one simple<00:33:43.760> use<00:33:44.120> case<00:33:44.480> right<00:33:45.240> and<00:33:45.559> when<00:33:45.720> we<00:33:45.880> spoke 00:33:46.310 --> 00:33:46.320 align:start position:0% simple use case right and when we spoke 00:33:46.320 --> 00:33:48.909 align:start position:0% simple use case right and when we spoke about<00:33:46.760> quantitative<00:33:47.399> data<00:33:47.720> qualitative<00:33:48.399> data 00:33:48.909 --> 00:33:48.919 align:start position:0% about quantitative data qualitative data 00:33:48.919 --> 00:33:52.669 align:start position:0% about quantitative data qualitative data a<00:33:49.080> lot<00:33:49.279> of<00:33:49.559> the<00:33:49.880> uh<00:33:50.080> industry<00:33:50.559> reports<00:33:51.120> tend<00:33:51.679> to 00:33:52.669 --> 00:33:52.679 align:start position:0% a lot of the uh industry reports tend to 00:33:52.679 --> 00:33:55.509 align:start position:0% a lot of the uh industry reports tend to focus<00:33:53.240> or<00:33:53.480> overly<00:33:53.919> focus<00:33:54.279> on<00:33:54.519> like<00:33:54.840> onchain 00:33:55.509 --> 00:33:55.519 align:start position:0% focus or overly focus on like onchain 00:33:55.519 --> 00:33:58.350 align:start position:0% focus or overly focus on like onchain activity<00:33:56.159> as<00:33:56.360> like<00:33:57.039> does<00:33:57.200> a<00:33:57.399> work<00:33:57.799> flows<00:33:58.159> yeah 00:33:58.350 --> 00:33:58.360 align:start position:0% activity as like does a work flows yeah 00:33:58.360 --> 00:34:01.070 align:start position:0% activity as like does a work flows yeah in<00:33:58.679> organizations<00:33:59.679> where<00:34:00.039> like<00:34:00.519> um<00:34:00.760> wallets 00:34:01.070 --> 00:34:01.080 align:start position:0% in organizations where like um wallets 00:34:01.080 --> 00:34:03.590 align:start position:0% in organizations where like um wallets are<00:34:01.279> already<00:34:01.840> used<00:34:02.320> so<00:34:02.559> I<00:34:02.679> think<00:34:02.880> like<00:34:03.080> they're 00:34:03.590 --> 00:34:03.600 align:start position:0% are already used so I think like they're 00:34:03.600 --> 00:34:05.509 align:start position:0% are already used so I think like they're so<00:34:03.840> safe<00:34:04.120> is<00:34:04.279> one<00:34:04.559> approach<00:34:05.000> right<00:34:05.200> just<00:34:05.399> like 00:34:05.509 --> 00:34:05.519 align:start position:0% so safe is one approach right just like 00:34:05.519 --> 00:34:07.990 align:start position:0% so safe is one approach right just like a<00:34:05.679> multi-c<00:34:06.440> approach<00:34:06.840> and<00:34:07.039> there<00:34:07.240> it<00:34:07.440> already 00:34:07.990 --> 00:34:08.000 align:start position:0% a multi-c approach and there it already 00:34:08.000 --> 00:34:09.790 align:start position:0% a multi-c approach and there it already has<00:34:08.240> like<00:34:08.440> the<00:34:08.599> permission<00:34:09.040> management<00:34:09.679> but 00:34:09.790 --> 00:34:09.800 align:start position:0% has like the permission management but 00:34:09.800 --> 00:34:13.750 align:start position:0% has like the permission management but then<00:34:10.000> there's<00:34:10.320> also<00:34:10.639> other<00:34:11.119> wallets<00:34:12.119> um<00:34:12.760> or 00:34:13.750 --> 00:34:13.760 align:start position:0% then there's also other wallets um or 00:34:13.760 --> 00:34:17.230 align:start position:0% then there's also other wallets um or yeah<00:34:14.159> basically<00:34:15.119> signature<00:34:16.079> tools<00:34:16.599> like<00:34:16.839> fire 00:34:17.230 --> 00:34:17.240 align:start position:0% yeah basically signature tools like fire 00:34:17.240 --> 00:34:19.190 align:start position:0% yeah basically signature tools like fire blocks<00:34:17.800> right<00:34:17.960> we<00:34:18.119> have<00:34:18.280> like<00:34:18.480> MPC<00:34:19.000> and 00:34:19.190 --> 00:34:19.200 align:start position:0% blocks right we have like MPC and 00:34:19.200 --> 00:34:22.470 align:start position:0% blocks right we have like MPC and privacy<00:34:19.679> technology<00:34:20.280> here<00:34:20.520> also<00:34:21.079> security<00:34:21.960> um 00:34:22.470 --> 00:34:22.480 align:start position:0% privacy technology here also security um 00:34:22.480 --> 00:34:26.909 align:start position:0% privacy technology here also security um technology<00:34:23.399> that<00:34:23.720> helps<00:34:24.560> to<00:34:25.440> um<00:34:25.839> abstract<00:34:26.760> uh 00:34:26.909 --> 00:34:26.919 align:start position:0% technology that helps to um abstract uh 00:34:26.919 --> 00:34:28.230 align:start position:0% technology that helps to um abstract uh Key<00:34:27.200> Management 00:34:28.230 --> 00:34:28.240 align:start position:0% Key Management 00:34:28.240 --> 00:34:31.230 align:start position:0% Key Management but<00:34:28.560> also<00:34:29.399> allows<00:34:29.879> for<00:34:30.440> like<00:34:30.599> building<00:34:30.960> an 00:34:31.230 --> 00:34:31.240 align:start position:0% but also allows for like building an 00:34:31.240 --> 00:34:32.950 align:start position:0% but also allows for like building an interface<00:34:31.960> and<00:34:32.079> then<00:34:32.280> you<00:34:32.480> have<00:34:32.760> like 00:34:32.950 --> 00:34:32.960 align:start position:0% interface and then you have like 00:34:32.960 --> 00:34:34.750 align:start position:0% interface and then you have like different<00:34:33.320> permissions<00:34:33.800> for<00:34:34.119> depending<00:34:34.520> on 00:34:34.750 --> 00:34:34.760 align:start position:0% different permissions for depending on 00:34:34.760 --> 00:34:37.710 align:start position:0% different permissions for depending on which<00:34:34.960> user<00:34:35.520> or<00:34:35.960> what<00:34:36.079> they<00:34:36.240> can<00:34:36.520> see<00:34:37.399> you<00:34:37.520> know 00:34:37.710 --> 00:34:37.720 align:start position:0% which user or what they can see you know 00:34:37.720 --> 00:34:39.869 align:start position:0% which user or what they can see you know that<00:34:37.879> they<00:34:38.000> don't<00:34:38.200> see<00:34:38.560> all<00:34:38.760> the<00:34:38.960> data<00:34:39.359> or<00:34:39.599> not 00:34:39.869 --> 00:34:39.879 align:start position:0% that they don't see all the data or not 00:34:39.879 --> 00:34:42.149 align:start position:0% that they don't see all the data or not or<00:34:40.040> you<00:34:40.159> can<00:34:40.399> have<00:34:40.679> randomizers<00:34:41.560> over<00:34:41.839> certain 00:34:42.149 --> 00:34:42.159 align:start position:0% or you can have randomizers over certain 00:34:42.159 --> 00:34:44.829 align:start position:0% or you can have randomizers over certain wallets<00:34:42.760> so<00:34:43.079> that<00:34:43.359> like<00:34:43.520> if<00:34:43.720> an<00:34:44.000> exchange<00:34:44.679> in 00:34:44.829 --> 00:34:44.839 align:start position:0% wallets so that like if an exchange in 00:34:44.839 --> 00:34:46.710 align:start position:0% wallets so that like if an exchange in the<00:34:44.960> category<00:34:45.359> of<00:34:45.480> a<00:34:45.639> financial<00:34:46.079> institution 00:34:46.710 --> 00:34:46.720 align:start position:0% the category of a financial institution 00:34:46.720 --> 00:34:49.550 align:start position:0% the category of a financial institution for<00:34:47.079> example<00:34:48.079> that<00:34:48.599> um<00:34:48.760> people<00:34:49.040> that<00:34:49.200> send 00:34:49.550 --> 00:34:49.560 align:start position:0% for example that um people that send 00:34:49.560 --> 00:34:52.790 align:start position:0% for example that um people that send funds<00:34:50.359> to<00:34:50.919> a<00:34:51.079> wallet<00:34:51.720> that<00:34:51.879> is<00:34:52.000> owned<00:34:52.359> by<00:34:52.599> a 00:34:52.790 --> 00:34:52.800 align:start position:0% funds to a wallet that is owned by a 00:34:52.800 --> 00:34:54.990 align:start position:0% funds to a wallet that is owned by a centralized<00:34:53.520> exchange<00:34:54.480> they<00:34:54.599> wouldn't<00:34:54.839> be 00:34:54.990 --> 00:34:55.000 align:start position:0% centralized exchange they wouldn't be 00:34:55.000 --> 00:34:57.710 align:start position:0% centralized exchange they wouldn't be able<00:34:55.200> to<00:34:55.440> trace<00:34:56.040> like<00:34:56.320> all<00:34:56.520> the<00:34:56.720> other<00:34:57.160> wallets 00:34:57.710 --> 00:34:57.720 align:start position:0% able to trace like all the other wallets 00:34:57.720 --> 00:35:00.950 align:start position:0% able to trace like all the other wallets of<00:34:57.880> a<00:34:58.000> centralized<00:34:58.640> exchange<00:34:59.280> right 00:35:00.950 --> 00:35:00.960 align:start position:0% of a centralized exchange right 00:35:00.960 --> 00:35:04.630 align:start position:0% of a centralized exchange right so<00:35:02.079> yeah<00:35:03.079> and<00:35:03.200> I<00:35:03.320> think<00:35:03.720> uh<00:35:03.920> I<00:35:04.000> want<00:35:04.160> to<00:35:04.400> like 00:35:04.630 --> 00:35:04.640 align:start position:0% so yeah and I think uh I want to like 00:35:04.640 --> 00:35:07.750 align:start position:0% so yeah and I think uh I want to like get<00:35:04.880> some<00:35:05.079> of<00:35:05.480> uh<00:35:05.720> Austin's<00:35:06.599> uh<00:35:06.880> perspective 00:35:07.750 --> 00:35:07.760 align:start position:0% get some of uh Austin's uh perspective 00:35:07.760 --> 00:35:09.750 align:start position:0% get some of uh Austin's uh perspective so<00:35:07.920> I<00:35:08.040> just<00:35:08.119> want<00:35:08.240> to<00:35:08.320> shift<00:35:08.680> Focus<00:35:09.280> uh<00:35:09.560> a 00:35:09.750 --> 00:35:09.760 align:start position:0% so I just want to shift Focus uh a 00:35:09.760 --> 00:35:13.310 align:start position:0% so I just want to shift Focus uh a little<00:35:10.200> bit<00:35:11.200> um<00:35:11.680> just<00:35:11.960> compared<00:35:12.359> to<00:35:12.800> web<00:35:13.040> 2 00:35:13.310 --> 00:35:13.320 align:start position:0% little bit um just compared to web 2 00:35:13.320 --> 00:35:14.790 align:start position:0% little bit um just compared to web 2 right<00:35:13.480> like<00:35:13.599> we're<00:35:13.839> talking<00:35:14.079> about<00:35:14.320> offchain 00:35:14.790 --> 00:35:14.800 align:start position:0% right like we're talking about offchain 00:35:14.800 --> 00:35:17.430 align:start position:0% right like we're talking about offchain onchain<00:35:15.480> like<00:35:15.920> what<00:35:16.040> are<00:35:16.280> some<00:35:17.240> like 00:35:17.430 --> 00:35:17.440 align:start position:0% onchain like what are some like 00:35:17.440 --> 00:35:19.790 align:start position:0% onchain like what are some like tradeoffs<00:35:18.119> that<00:35:18.280> you<00:35:18.440> feel<00:35:18.800> like<00:35:19.000> we<00:35:19.200> make<00:35:19.440> in 00:35:19.790 --> 00:35:19.800 align:start position:0% tradeoffs that you feel like we make in 00:35:19.800 --> 00:35:22.950 align:start position:0% tradeoffs that you feel like we make in web<00:35:20.040> 3<00:35:20.440> that<00:35:20.800> differ<00:35:21.520> uh<00:35:21.680> from<00:35:21.920> web<00:35:22.119> 2<00:35:22.599> in<00:35:22.720> terms 00:35:22.950 --> 00:35:22.960 align:start position:0% web 3 that differ uh from web 2 in terms 00:35:22.960 --> 00:35:24.750 align:start position:0% web 3 that differ uh from web 2 in terms of<00:35:23.160> like<00:35:23.359> General 00:35:24.750 --> 00:35:24.760 align:start position:0% of like General 00:35:24.760 --> 00:35:26.750 align:start position:0% of like General practices<00:35:25.760> oh<00:35:25.960> man<00:35:26.119> I<00:35:26.200> had<00:35:26.280> a<00:35:26.400> really<00:35:26.560> good 00:35:26.750 --> 00:35:26.760 align:start position:0% practices oh man I had a really good 00:35:26.760 --> 00:35:27.950 align:start position:0% practices oh man I had a really good answer<00:35:26.960> to<00:35:27.079> the<00:35:27.240> last<00:35:27.400> question<00:35:27.720> and<00:35:27.839> you'll 00:35:27.950 --> 00:35:27.960 align:start position:0% answer to the last question and you'll 00:35:27.960 --> 00:35:31.750 align:start position:0% answer to the last question and you'll have<00:35:28.079> to<00:35:28.160> come<00:35:28.280> to<00:35:28.440> my<00:35:28.599> next<00:35:28.880> panel<00:35:29.839> um<00:35:30.839> but<00:35:31.079> uh 00:35:31.750 --> 00:35:31.760 align:start position:0% have to come to my next panel um but uh 00:35:31.760 --> 00:35:34.670 align:start position:0% have to come to my next panel um but uh uh<00:35:31.880> so<00:35:32.079> some<00:35:32.280> trade-offs<00:35:33.119> um<00:35:33.520> I<00:35:33.640> think<00:35:34.440> as<00:35:34.560> I 00:35:34.670 --> 00:35:34.680 align:start position:0% uh so some trade-offs um I think as I 00:35:34.680 --> 00:35:37.310 align:start position:0% uh so some trade-offs um I think as I mentioned<00:35:34.960> earlier<00:35:35.320> we've<00:35:35.520> been<00:35:36.320> um<00:35:37.119> we've 00:35:37.310 --> 00:35:37.320 align:start position:0% mentioned earlier we've been um we've 00:35:37.320 --> 00:35:39.230 align:start position:0% mentioned earlier we've been um we've been<00:35:37.520> optimizing<00:35:38.240> for<00:35:38.520> like<00:35:38.680> solving<00:35:39.040> very 00:35:39.230 --> 00:35:39.240 align:start position:0% been optimizing for like solving very 00:35:39.240 --> 00:35:41.430 align:start position:0% been optimizing for like solving very fundamental<00:35:39.760> problems<00:35:40.040> around<00:35:40.359> like 00:35:41.430 --> 00:35:41.440 align:start position:0% fundamental problems around like 00:35:41.440 --> 00:35:44.390 align:start position:0% fundamental problems around like decentralization<00:35:42.440> um<00:35:43.119> and<00:35:43.320> autonomy<00:35:44.079> and<00:35:44.280> you 00:35:44.390 --> 00:35:44.400 align:start position:0% decentralization um and autonomy and you 00:35:44.400 --> 00:35:45.710 align:start position:0% decentralization um and autonomy and you know<00:35:44.560> like<00:35:44.680> I<00:35:44.760> said<00:35:44.920> I<00:35:45.000> think<00:35:45.160> those<00:35:45.280> are<00:35:45.440> table 00:35:45.710 --> 00:35:45.720 align:start position:0% know like I said I think those are table 00:35:45.720 --> 00:35:49.069 align:start position:0% know like I said I think those are table Stakes<00:35:46.160> now<00:35:47.119> um<00:35:47.640> and<00:35:48.240> we<00:35:48.440> have<00:35:48.599> to<00:35:48.800> start 00:35:49.069 --> 00:35:49.079 align:start position:0% Stakes now um and we have to start 00:35:49.079 --> 00:35:51.230 align:start position:0% Stakes now um and we have to start thinking<00:35:49.359> about<00:35:49.680> maybe<00:35:49.960> until 00:35:51.230 --> 00:35:51.240 align:start position:0% thinking about maybe until 00:35:51.240 --> 00:35:54.790 align:start position:0% thinking about maybe until we<00:35:52.240> until<00:35:52.599> we<00:35:52.960> really<00:35:53.680> uh<00:35:53.880> improve<00:35:54.520> the<00:35:54.640> kind 00:35:54.790 --> 00:35:54.800 align:start position:0% we until we really uh improve the kind 00:35:54.800 --> 00:35:56.910 align:start position:0% we until we really uh improve the kind of<00:35:54.920> web<00:35:55.119> 3<00:35:55.359> experience<00:35:55.800> till<00:35:56.240> exceeds<00:35:56.640> the<00:35:56.760> web 00:35:56.910 --> 00:35:56.920 align:start position:0% of web 3 experience till exceeds the web 00:35:56.920 --> 00:35:59.030 align:start position:0% of web 3 experience till exceeds the web two<00:35:57.079> experience<00:35:57.359> we<00:35:57.440> have<00:35:57.560> to<00:35:57.680> to<00:35:57.800> think<00:35:58.040> about 00:35:59.030 --> 00:35:59.040 align:start position:0% two experience we have to to think about 00:35:59.040 --> 00:36:00.990 align:start position:0% two experience we have to to think about um<00:35:59.440> how<00:35:59.599> we<00:35:59.680> can<00:35:59.880> use<00:36:00.119> those<00:36:00.319> moments<00:36:00.680> so<00:36:00.839> for 00:36:00.990 --> 00:36:01.000 align:start position:0% um how we can use those moments so for 00:36:01.000 --> 00:36:04.150 align:start position:0% um how we can use those moments so for example<00:36:01.800> like<00:36:02.800> uh<00:36:03.400> you<00:36:03.520> know<00:36:03.760> how<00:36:03.920> can<00:36:04.040> we 00:36:04.150 --> 00:36:04.160 align:start position:0% example like uh you know how can we 00:36:04.160 --> 00:36:05.790 align:start position:0% example like uh you know how can we alter<00:36:04.440> our<00:36:04.640> language<00:36:05.079> to<00:36:05.200> speak<00:36:05.400> to<00:36:05.599> people 00:36:05.790 --> 00:36:05.800 align:start position:0% alter our language to speak to people 00:36:05.800 --> 00:36:07.750 align:start position:0% alter our language to speak to people more<00:36:06.040> clearly<00:36:06.680> how<00:36:06.800> can<00:36:06.960> we<00:36:07.079> communicate<00:36:07.680> you 00:36:07.750 --> 00:36:07.760 align:start position:0% more clearly how can we communicate you 00:36:07.760 --> 00:36:09.710 align:start position:0% more clearly how can we communicate you know<00:36:07.880> we<00:36:08.000> talked<00:36:08.240> about<00:36:08.960> are<00:36:09.079> you<00:36:09.240> a<00:36:09.359> privacy 00:36:09.710 --> 00:36:09.720 align:start position:0% know we talked about are you a privacy 00:36:09.720 --> 00:36:13.829 align:start position:0% know we talked about are you a privacy purist<00:36:10.280> or<00:36:11.240> um<00:36:12.000> or<00:36:12.280> kind<00:36:12.400> of<00:36:12.599> you<00:36:12.720> know<00:36:12.880> a<00:36:13.079> data 00:36:13.829 --> 00:36:13.839 align:start position:0% purist or um or kind of you know a data 00:36:13.839 --> 00:36:15.589 align:start position:0% purist or um or kind of you know a data a<00:36:13.920> wallet<00:36:14.200> Wanderer<00:36:14.720> or<00:36:14.839> more<00:36:15.000> of<00:36:15.079> a<00:36:15.200> utility 00:36:15.589 --> 00:36:15.599 align:start position:0% a wallet Wanderer or more of a utility 00:36:15.599 --> 00:36:18.710 align:start position:0% a wallet Wanderer or more of a utility Seeker<00:36:16.079> I<00:36:16.359> think<00:36:17.359> uh<00:36:17.839> copy<00:36:18.240> is<00:36:18.440> actually 00:36:18.710 --> 00:36:18.720 align:start position:0% Seeker I think uh copy is actually 00:36:18.720 --> 00:36:20.550 align:start position:0% Seeker I think uh copy is actually really<00:36:18.920> important<00:36:19.640> like<00:36:19.760> to<00:36:20.000> communicate<00:36:20.440> the 00:36:20.550 --> 00:36:20.560 align:start position:0% really important like to communicate the 00:36:20.560 --> 00:36:22.349 align:start position:0% really important like to communicate the message<00:36:20.880> I<00:36:20.960> think<00:36:21.079> a<00:36:21.160> lot<00:36:21.280> of<00:36:21.359> times<00:36:21.599> we<00:36:21.800> put 00:36:22.349 --> 00:36:22.359 align:start position:0% message I think a lot of times we put 00:36:22.359 --> 00:36:23.950 align:start position:0% message I think a lot of times we put tons<00:36:22.599> of<00:36:22.800> information<00:36:23.160> in<00:36:23.280> the 00:36:23.950 --> 00:36:23.960 align:start position:0% tons of information in the 00:36:23.960 --> 00:36:26.910 align:start position:0% tons of information in the documentation<00:36:24.960> um<00:36:25.400> or<00:36:25.599> in<00:36:25.720> the<00:36:25.800> t's<00:36:26.040> and<00:36:26.200> C's 00:36:26.910 --> 00:36:26.920 align:start position:0% documentation um or in the t's and C's 00:36:26.920 --> 00:36:28.190 align:start position:0% documentation um or in the t's and C's and<00:36:27.240> uh<00:36:27.359> this<00:36:27.560> this<00:36:27.640> is<00:36:27.720> something<00:36:27.960> a<00:36:28.040> lot<00:36:28.119> of 00:36:28.190 --> 00:36:28.200 align:start position:0% and uh this this is something a lot of 00:36:28.200 --> 00:36:30.589 align:start position:0% and uh this this is something a lot of times<00:36:28.480> teams<00:36:28.720> don't<00:36:28.920> have<00:36:29.440> copywriters<00:36:30.440> and 00:36:30.589 --> 00:36:30.599 align:start position:0% times teams don't have copywriters and 00:36:30.599 --> 00:36:32.190 align:start position:0% times teams don't have copywriters and it's<00:36:30.760> something<00:36:31.160> that<00:36:31.640> I<00:36:31.720> think<00:36:31.839> a<00:36:31.960> lot<00:36:32.079> of 00:36:32.190 --> 00:36:32.200 align:start position:0% it's something that I think a lot of 00:36:32.200 --> 00:36:35.069 align:start position:0% it's something that I think a lot of designers<00:36:33.200> reluctantly<00:36:33.760> do<00:36:34.599> um<00:36:34.760> but<00:36:34.880> it's 00:36:35.069 --> 00:36:35.079 align:start position:0% designers reluctantly do um but it's 00:36:35.079 --> 00:36:37.710 align:start position:0% designers reluctantly do um but it's worth<00:36:35.960> taking<00:36:36.319> the<00:36:36.520> time<00:36:36.960> and<00:36:37.079> this<00:36:37.160> is<00:36:37.280> a<00:36:37.400> pain 00:36:37.710 --> 00:36:37.720 align:start position:0% worth taking the time and this is a pain 00:36:37.720 --> 00:36:40.270 align:start position:0% worth taking the time and this is a pain point<00:36:38.040> you<00:36:38.160> know<00:36:38.319> for<00:36:38.520> me<00:36:39.480> uh<00:36:39.640> to<00:36:40.000> really 00:36:40.270 --> 00:36:40.280 align:start position:0% point you know for me uh to really 00:36:40.280 --> 00:36:42.710 align:start position:0% point you know for me uh to really communicate<00:36:40.880> clearly<00:36:41.520> the<00:36:41.800> The<00:36:42.000> Exchange 00:36:42.710 --> 00:36:42.720 align:start position:0% communicate clearly the The Exchange 00:36:42.720 --> 00:36:44.030 align:start position:0% communicate clearly the The Exchange like<00:36:42.880> what<00:36:43.000> are<00:36:43.079> you<00:36:43.240> getting<00:36:43.720> and<00:36:43.839> what<00:36:43.960> are 00:36:44.030 --> 00:36:44.040 align:start position:0% like what are you getting and what are 00:36:44.040 --> 00:36:46.309 align:start position:0% like what are you getting and what are you<00:36:44.240> giving<00:36:45.240> um<00:36:45.480> especially<00:36:45.800> if<00:36:45.920> you<00:36:46.040> want<00:36:46.200> to 00:36:46.309 --> 00:36:46.319 align:start position:0% you giving um especially if you want to 00:36:46.319 --> 00:36:48.270 align:start position:0% you giving um especially if you want to onboard<00:36:46.720> more<00:36:46.960> people<00:36:47.640> um<00:36:47.839> I<00:36:47.920> think<00:36:48.079> that's 00:36:48.270 --> 00:36:48.280 align:start position:0% onboard more people um I think that's 00:36:48.280 --> 00:36:50.349 align:start position:0% onboard more people um I think that's super<00:36:48.560> important<00:36:49.400> and<00:36:49.520> then<00:36:49.720> just<00:36:50.040> things 00:36:50.349 --> 00:36:50.359 align:start position:0% super important and then just things 00:36:50.359 --> 00:36:54.030 align:start position:0% super important and then just things like<00:36:50.839> you<00:36:50.960> know<00:36:51.240> fix<00:36:52.240> you<00:36:52.319> know<00:36:52.680> transa<00:36:53.680> like 00:36:54.030 --> 00:36:54.040 align:start position:0% like you know fix you know transa like 00:36:54.040 --> 00:36:56.710 align:start position:0% like you know fix you know transa like uh<00:36:54.240> transactions<00:36:54.839> taking<00:36:55.079> a<00:36:55.200> lot<00:36:55.319> of<00:36:55.480> time<00:36:56.160> um 00:36:56.710 --> 00:36:56.720 align:start position:0% uh transactions taking a lot of time um 00:36:56.720 --> 00:36:58.230 align:start position:0% uh transactions taking a lot of time um you<00:36:56.839> know<00:36:57.000> these<00:36:57.160> sorts<00:36:57.319> of<00:36:57.640> things<00:36:57.920> like 00:36:58.230 --> 00:36:58.240 align:start position:0% you know these sorts of things like 00:36:58.240 --> 00:36:59.870 align:start position:0% you know these sorts of things like until<00:36:58.520> we<00:36:58.680> fix<00:36:58.960> that<00:36:59.119> we<00:36:59.200> have<00:36:59.319> to<00:36:59.440> think<00:36:59.599> about 00:36:59.870 --> 00:36:59.880 align:start position:0% until we fix that we have to think about 00:36:59.880 --> 00:37:02.349 align:start position:0% until we fix that we have to think about those<00:37:00.079> as<00:37:00.480> opportunities<00:37:01.200> to<00:37:02.000> you<00:37:02.079> know 00:37:02.349 --> 00:37:02.359 align:start position:0% those as opportunities to you know 00:37:02.359 --> 00:37:05.349 align:start position:0% those as opportunities to you know educate<00:37:02.920> or<00:37:03.160> entertain<00:37:03.839> or<00:37:04.079> engage<00:37:05.000> um<00:37:05.079> so 00:37:05.349 --> 00:37:05.359 align:start position:0% educate or entertain or engage um so 00:37:05.359 --> 00:37:06.470 align:start position:0% educate or entertain or engage um so that<00:37:05.560> there<00:37:05.599> are<00:37:05.680> lots<00:37:05.839> of<00:37:05.920> little<00:37:06.119> moments 00:37:06.470 --> 00:37:06.480 align:start position:0% that there are lots of little moments 00:37:06.480 --> 00:37:07.829 align:start position:0% that there are lots of little moments like<00:37:06.640> that<00:37:06.800> that<00:37:06.920> are<00:37:07.079> slightly<00:37:07.440> different<00:37:07.680> in 00:37:07.829 --> 00:37:07.839 align:start position:0% like that that are slightly different in 00:37:07.839 --> 00:37:10.190 align:start position:0% like that that are slightly different in web<00:37:08.040> 3<00:37:08.319> but<00:37:08.520> ideally<00:37:09.079> we<00:37:09.280> just<00:37:09.520> we<00:37:09.680> just<00:37:09.800> solved 00:37:10.190 --> 00:37:10.200 align:start position:0% web 3 but ideally we just we just solved 00:37:10.200 --> 00:37:12.710 align:start position:0% web 3 but ideally we just we just solved that<00:37:10.680> yeah<00:37:11.040> and<00:37:11.240> and<00:37:11.440> we<00:37:11.680> we<00:37:11.800> can<00:37:12.280> we<00:37:12.400> can<00:37:12.520> move 00:37:12.710 --> 00:37:12.720 align:start position:0% that yeah and and we we can we can move 00:37:12.720 --> 00:37:15.109 align:start position:0% that yeah and and we we can we can move on<00:37:12.920> to<00:37:13.599> you<00:37:13.720> know<00:37:14.200> creating<00:37:14.599> Next<00:37:14.839> Level 00:37:15.109 --> 00:37:15.119 align:start position:0% on to you know creating Next Level 00:37:15.119 --> 00:37:16.589 align:start position:0% on to you know creating Next Level experiences<00:37:15.599> and<00:37:15.720> we're<00:37:15.880> not<00:37:16.040> trying<00:37:16.280> to<00:37:16.480> like 00:37:16.589 --> 00:37:16.599 align:start position:0% experiences and we're not trying to like 00:37:16.599 --> 00:37:20.349 align:start position:0% experiences and we're not trying to like fill<00:37:16.880> these<00:37:17.079> moments<00:37:17.520> with<00:37:18.119> uh<00:37:18.280> with 00:37:20.349 --> 00:37:20.359 align:start position:0% fill these moments with uh with 00:37:20.359 --> 00:37:23.470 align:start position:0% fill these moments with uh with fixes<00:37:21.359> um<00:37:21.839> I<00:37:21.960> think<00:37:22.119> I<00:37:22.240> just<00:37:22.359> want<00:37:22.480> to<00:37:22.720> like<00:37:23.359> as 00:37:23.470 --> 00:37:23.480 align:start position:0% fixes um I think I just want to like as 00:37:23.480 --> 00:37:24.990 align:start position:0% fixes um I think I just want to like as we're<00:37:23.680> nearing<00:37:24.119> probably<00:37:24.400> like<00:37:24.520> we<00:37:24.640> got<00:37:24.839> like 00:37:24.990 --> 00:37:25.000 align:start position:0% we're nearing probably like we got like 00:37:25.000 --> 00:37:26.910 align:start position:0% we're nearing probably like we got like eight<00:37:25.240> minutes<00:37:25.680> left<00:37:26.240> and<00:37:26.359> I<00:37:26.480> wanted<00:37:26.680> to<00:37:26.800> kind 00:37:26.910 --> 00:37:26.920 align:start position:0% eight minutes left and I wanted to kind 00:37:26.920 --> 00:37:28.910 align:start position:0% eight minutes left and I wanted to kind of<00:37:27.000> shift<00:37:27.240> Focus<00:37:27.640> is<00:37:27.760> maybe<00:37:28.079> like<00:37:28.240> the<00:37:28.359> future 00:37:28.910 --> 00:37:28.920 align:start position:0% of shift Focus is maybe like the future 00:37:28.920 --> 00:37:32.550 align:start position:0% of shift Focus is maybe like the future outlook<00:37:29.480> of<00:37:29.640> our<00:37:30.599> industry<00:37:31.599> uh<00:37:31.920> so<00:37:32.400> the 00:37:32.550 --> 00:37:32.560 align:start position:0% outlook of our industry uh so the 00:37:32.560 --> 00:37:35.309 align:start position:0% outlook of our industry uh so the question<00:37:33.240> to<00:37:33.400> all<00:37:33.560> of<00:37:33.720> you<00:37:33.839> all<00:37:34.400> uh<00:37:34.800> preferably 00:37:35.309 --> 00:37:35.319 align:start position:0% question to all of you all uh preferably 00:37:35.319 --> 00:37:38.150 align:start position:0% question to all of you all uh preferably is<00:37:35.760> looking<00:37:36.079> ahead<00:37:36.800> like<00:37:37.040> how<00:37:37.200> can<00:37:37.520> the<00:37:38.040> the 00:37:38.150 --> 00:37:38.160 align:start position:0% is looking ahead like how can the the 00:37:38.160 --> 00:37:40.069 align:start position:0% is looking ahead like how can the the web<00:37:38.400> three<00:37:38.640> industry<00:37:39.040> onboard<00:37:39.680> like<00:37:39.880> a 00:37:40.069 --> 00:37:40.079 align:start position:0% web three industry onboard like a 00:37:40.079 --> 00:37:42.750 align:start position:0% web three industry onboard like a diverse<00:37:40.560> user<00:37:40.880> base<00:37:41.359> without<00:37:41.800> compromising 00:37:42.750 --> 00:37:42.760 align:start position:0% diverse user base without compromising 00:37:42.760 --> 00:37:45.829 align:start position:0% diverse user base without compromising user<00:37:43.119> privacy<00:37:44.000> are<00:37:44.319> there<00:37:44.640> emerging<00:37:45.160> tools<00:37:45.560> or 00:37:45.829 --> 00:37:45.839 align:start position:0% user privacy are there emerging tools or 00:37:45.839 --> 00:37:48.309 align:start position:0% user privacy are there emerging tools or practices<00:37:46.520> Frameworks<00:37:47.240> that<00:37:47.560> you<00:37:47.720> feel<00:37:48.160> like 00:37:48.309 --> 00:37:48.319 align:start position:0% practices Frameworks that you feel like 00:37:48.319 --> 00:37:50.829 align:start position:0% practices Frameworks that you feel like you're<00:37:48.560> excited 00:37:50.829 --> 00:37:50.839 align:start position:0% you're excited 00:37:50.839 --> 00:37:54.069 align:start position:0% you're excited about<00:37:51.839> yeah<00:37:52.079> maybe<00:37:52.319> I<00:37:52.440> can<00:37:53.079> um<00:37:53.280> connect<00:37:53.640> to<00:37:53.920> one 00:37:54.069 --> 00:37:54.079 align:start position:0% about yeah maybe I can um connect to one 00:37:54.079 --> 00:37:56.470 align:start position:0% about yeah maybe I can um connect to one of<00:37:54.200> the<00:37:54.400> examples<00:37:54.960> I<00:37:55.280> gave<00:37:55.520> earlier<00:37:56.160> that<00:37:56.319> was 00:37:56.470 --> 00:37:56.480 align:start position:0% of the examples I gave earlier that was 00:37:56.480 --> 00:37:58.790 align:start position:0% of the examples I gave earlier that was around<00:37:56.800> signature<00:37:57.560> signature<00:37:58.000> management<00:37:58.520> so 00:37:58.790 --> 00:37:58.800 align:start position:0% around signature signature management so 00:37:58.800 --> 00:38:01.710 align:start position:0% around signature signature management so Solutions<00:37:59.319> like<00:37:59.560> fire<00:37:59.960> blocks<00:38:00.720> um<00:38:00.960> MPC 00:38:01.710 --> 00:38:01.720 align:start position:0% Solutions like fire blocks um MPC 00:38:01.720 --> 00:38:06.710 align:start position:0% Solutions like fire blocks um MPC technology<00:38:02.599> or<00:38:03.520> um<00:38:03.920> CK<00:38:04.599> kyc<00:38:05.599> um<00:38:05.960> like<00:38:06.200> Mina 00:38:06.710 --> 00:38:06.720 align:start position:0% technology or um CK kyc um like Mina 00:38:06.720 --> 00:38:08.670 align:start position:0% technology or um CK kyc um like Mina protocol<00:38:07.280> or<00:38:07.440> a<00:38:07.560> few<00:38:07.880> other<00:38:08.160> projects<00:38:08.480> are 00:38:08.670 --> 00:38:08.680 align:start position:0% protocol or a few other projects are 00:38:08.680 --> 00:38:12.710 align:start position:0% protocol or a few other projects are working<00:38:09.119> on<00:38:10.119> um<00:38:10.839> yeah<00:38:11.119> basically<00:38:11.920> verifying 00:38:12.710 --> 00:38:12.720 align:start position:0% working on um yeah basically verifying 00:38:12.720 --> 00:38:16.430 align:start position:0% working on um yeah basically verifying that<00:38:12.920> you're<00:38:13.560> like<00:38:14.160> for<00:38:14.400> example<00:38:15.440> allowed 00:38:16.430 --> 00:38:16.440 align:start position:0% that you're like for example allowed 00:38:16.440 --> 00:38:18.190 align:start position:0% that you're like for example allowed you're<00:38:16.599> on<00:38:16.800> the<00:38:16.920> allowed<00:38:17.400> list<00:38:17.640> to<00:38:17.800> use<00:38:18.000> a 00:38:18.190 --> 00:38:18.200 align:start position:0% you're on the allowed list to use a 00:38:18.200 --> 00:38:21.829 align:start position:0% you're on the allowed list to use a certain<00:38:19.119> um<00:38:19.920> service<00:38:20.640> without<00:38:21.079> sharing<00:38:21.640> your 00:38:21.829 --> 00:38:21.839 align:start position:0% certain um service without sharing your 00:38:21.839 --> 00:38:24.390 align:start position:0% certain um service without sharing your private<00:38:22.200> data<00:38:22.680> that<00:38:22.880> can<00:38:23.079> be<00:38:23.480> like<00:38:23.760> yes<00:38:24.079> from 00:38:24.390 --> 00:38:24.400 align:start position:0% private data that can be like yes from 00:38:24.400 --> 00:38:25.950 align:start position:0% private data that can be like yes from exams<00:38:24.760> from<00:38:24.880> the<00:38:25.000> financial<00:38:25.400> world<00:38:25.760> but<00:38:25.839> it 00:38:25.950 --> 00:38:25.960 align:start position:0% exams from the financial world but it 00:38:25.960 --> 00:38:28.510 align:start position:0% exams from the financial world but it could<00:38:26.160> also<00:38:26.440> be<00:38:26.800> related<00:38:27.119> to<00:38:27.520> Health<00:38:27.839> Data<00:38:28.359> and 00:38:28.510 --> 00:38:28.520 align:start position:0% could also be related to Health Data and 00:38:28.520 --> 00:38:30.790 align:start position:0% could also be related to Health Data and so<00:38:28.720> on<00:38:29.000> where<00:38:29.280> it's<00:38:29.480> really<00:38:29.880> sensitive<00:38:30.440> data 00:38:30.790 --> 00:38:30.800 align:start position:0% so on where it's really sensitive data 00:38:30.800 --> 00:38:34.030 align:start position:0% so on where it's really sensitive data that<00:38:30.960> should<00:38:31.160> not<00:38:31.480> get<00:38:32.040> access<00:38:33.040> um<00:38:33.200> to<00:38:33.720> other 00:38:34.030 --> 00:38:34.040 align:start position:0% that should not get access um to other 00:38:34.040 --> 00:38:36.589 align:start position:0% that should not get access um to other people<00:38:34.359> so<00:38:34.640> with<00:38:34.880> MPC<00:38:35.520> you<00:38:35.640> would<00:38:35.839> for<00:38:36.040> example 00:38:36.589 --> 00:38:36.599 align:start position:0% people so with MPC you would for example 00:38:36.599 --> 00:38:40.670 align:start position:0% people so with MPC you would for example expose<00:38:37.119> that<00:38:37.480> data<00:38:38.480> um<00:38:38.839> but<00:38:39.440> uh<00:38:39.960> you<00:38:40.040> would<00:38:40.240> not 00:38:40.670 --> 00:38:40.680 align:start position:0% expose that data um but uh you would not 00:38:40.680 --> 00:38:43.030 align:start position:0% expose that data um but uh you would not um<00:38:41.240> um<00:38:41.680> expose<00:38:42.000> that<00:38:42.119> data<00:38:42.319> you<00:38:42.400> would<00:38:42.599> conceal 00:38:43.030 --> 00:38:43.040 align:start position:0% um um expose that data you would conceal 00:38:43.040 --> 00:38:45.270 align:start position:0% um um expose that data you would conceal that<00:38:43.240> data<00:38:43.680> but<00:38:43.839> for<00:38:44.119> example 00:38:45.270 --> 00:38:45.280 align:start position:0% that data but for example 00:38:45.280 --> 00:38:49.470 align:start position:0% that data but for example MPCs<00:38:46.280> uh<00:38:46.440> you<00:38:46.599> would<00:38:46.960> always<00:38:47.400> have<00:38:47.760> like<00:38:48.280> um<00:38:49.000> um 00:38:49.470 --> 00:38:49.480 align:start position:0% MPCs uh you would always have like um um 00:38:49.480 --> 00:38:51.790 align:start position:0% MPCs uh you would always have like um um yeah<00:38:49.800> part<00:38:50.000> of<00:38:50.160> the<00:38:50.319> secret<00:38:50.800> would<00:38:51.000> always<00:38:51.520> be 00:38:51.790 --> 00:38:51.800 align:start position:0% yeah part of the secret would always be 00:38:51.800 --> 00:38:55.349 align:start position:0% yeah part of the secret would always be held<00:38:52.200> by<00:38:52.400> the<00:38:52.720> um<00:38:52.839> NPC<00:38:53.520> technology<00:38:54.359> provider 00:38:55.349 --> 00:38:55.359 align:start position:0% held by the um NPC technology provider 00:38:55.359 --> 00:38:58.309 align:start position:0% held by the um NPC technology provider um<00:38:55.599> but<00:38:55.800> fhe<00:38:56.400> for<00:38:56.599> example<00:38:56.960> fully<00:38:57.640> homomorphic 00:38:58.309 --> 00:38:58.319 align:start position:0% um but fhe for example fully homomorphic 00:38:58.319 --> 00:39:01.270 align:start position:0% um but fhe for example fully homomorphic encryption<00:38:59.319> uh<00:38:59.599> yeah<00:38:59.800> is<00:39:00.079> basically<00:39:01.040> yeah 00:39:01.270 --> 00:39:01.280 align:start position:0% encryption uh yeah is basically yeah 00:39:01.280 --> 00:39:04.670 align:start position:0% encryption uh yeah is basically yeah where<00:39:01.520> you<00:39:01.720> can<00:39:02.319> see<00:39:02.760> or<00:39:03.440> the<00:39:03.640> data<00:39:03.920> and 00:39:04.670 --> 00:39:04.680 align:start position:0% where you can see or the data and 00:39:04.680 --> 00:39:08.870 align:start position:0% where you can see or the data and also<00:39:05.680> um<00:39:06.359> yeah<00:39:06.960> verify<00:39:07.560> it<00:39:07.920> in 00:39:08.870 --> 00:39:08.880 align:start position:0% also um yeah verify it in 00:39:08.880 --> 00:39:12.990 align:start position:0% also um yeah verify it in a<00:39:09.880> in<00:39:10.000> a<00:39:10.280> bit<00:39:10.440> more<00:39:10.880> complex<00:39:11.359> technical<00:39:11.920> way<00:39:12.760> I 00:39:12.990 --> 00:39:13.000 align:start position:0% a in a bit more complex technical way I 00:39:13.000 --> 00:39:14.910 align:start position:0% a in a bit more complex technical way I I'd<00:39:13.200> probably<00:39:13.560> challenge<00:39:14.040> this<00:39:14.200> a<00:39:14.319> little<00:39:14.520> bit 00:39:14.910 --> 00:39:14.920 align:start position:0% I'd probably challenge this a little bit 00:39:14.920 --> 00:39:16.990 align:start position:0% I'd probably challenge this a little bit I<00:39:15.160> I<00:39:15.240> don't<00:39:15.480> think<00:39:15.720> the<00:39:15.920> way<00:39:16.079> to<00:39:16.280> get<00:39:16.480> towards 00:39:16.990 --> 00:39:17.000 align:start position:0% I I don't think the way to get towards 00:39:17.000 --> 00:39:21.190 align:start position:0% I I don't think the way to get towards privacy<00:39:17.640> is<00:39:17.839> to<00:39:18.760> give<00:39:19.119> a<00:39:19.359> third<00:39:19.800> party<00:39:20.800> exactly 00:39:21.190 --> 00:39:21.200 align:start position:0% privacy is to give a third party exactly 00:39:21.200 --> 00:39:24.390 align:start position:0% privacy is to give a third party exactly access<00:39:22.000> that's<00:39:22.240> why<00:39:22.520> you<00:39:22.760> have<00:39:22.960> to<00:39:23.960> choose 00:39:24.390 --> 00:39:24.400 align:start position:0% access that's why you have to choose 00:39:24.400 --> 00:39:26.589 align:start position:0% access that's why you have to choose different<00:39:24.839> types<00:39:25.119> of<00:39:25.359> privacy<00:39:25.880> Technologies 00:39:26.589 --> 00:39:26.599 align:start position:0% different types of privacy Technologies 00:39:26.599 --> 00:39:28.430 align:start position:0% different types of privacy Technologies depending<00:39:26.960> on<00:39:27.079> the<00:39:27.640> case<00:39:27.800> that's<00:39:28.000> what<00:39:28.119> I<00:39:28.240> was 00:39:28.430 --> 00:39:28.440 align:start position:0% depending on the case that's what I was 00:39:28.440 --> 00:39:32.910 align:start position:0% depending on the case that's what I was trying<00:39:28.720> to<00:39:29.760> to<00:39:30.760> to<00:39:31.000> highlight<00:39:31.480> here<00:39:32.079> um<00:39:32.640> and<00:39:32.800> I 00:39:32.910 --> 00:39:32.920 align:start position:0% trying to to to highlight here um and I 00:39:32.920 --> 00:39:34.990 align:start position:0% trying to to to highlight here um and I think<00:39:33.079> like<00:39:33.319> there's<00:39:33.920> there's<00:39:34.240> this<00:39:34.480> part<00:39:34.760> of 00:39:34.990 --> 00:39:35.000 align:start position:0% think like there's there's this part of 00:39:35.000 --> 00:39:37.750 align:start position:0% think like there's there's this part of what<00:39:35.200> type<00:39:35.480> of<00:39:35.680> data<00:39:36.200> is<00:39:36.520> interacted<00:39:37.400> and<00:39:37.599> what 00:39:37.750 --> 00:39:37.760 align:start position:0% what type of data is interacted and what 00:39:37.760 --> 00:39:41.790 align:start position:0% what type of data is interacted and what is<00:39:37.880> the<00:39:38.160> right<00:39:38.440> approach<00:39:38.920> to<00:39:39.520> secure<00:39:40.800> privacy 00:39:41.790 --> 00:39:41.800 align:start position:0% is the right approach to secure privacy 00:39:41.800 --> 00:39:43.750 align:start position:0% is the right approach to secure privacy um<00:39:42.000> and<00:39:42.119> it<00:39:42.280> could<00:39:42.400> be<00:39:42.560> for<00:39:42.800> example<00:39:43.400> we<00:39:43.560> don't 00:39:43.750 --> 00:39:43.760 align:start position:0% um and it could be for example we don't 00:39:43.760 --> 00:39:47.069 align:start position:0% um and it could be for example we don't want<00:39:43.960> to<00:39:44.400> interact<00:39:45.000> with<00:39:45.560> um<00:39:46.079> criminals<00:39:46.720> or<00:39:46.880> to 00:39:47.069 --> 00:39:47.079 align:start position:0% want to interact with um criminals or to 00:39:47.079 --> 00:39:49.270 align:start position:0% want to interact with um criminals or to have<00:39:47.280> exposure<00:39:47.720> to<00:39:47.920> T<00:39:48.319> funds<00:39:48.720> or<00:39:48.920> that<00:39:49.079> for 00:39:49.270 --> 00:39:49.280 align:start position:0% have exposure to T funds or that for 00:39:49.280 --> 00:39:52.710 align:start position:0% have exposure to T funds or that for example<00:39:49.680> our<00:39:50.000> insurances<00:39:50.880> would<00:39:51.119> know<00:39:51.800> like 00:39:52.710 --> 00:39:52.720 align:start position:0% example our insurances would know like 00:39:52.720 --> 00:39:56.109 align:start position:0% example our insurances would know like um<00:39:53.240> what<00:39:53.480> we<00:39:53.760> have<00:39:54.240> genetic 00:39:56.109 --> 00:39:56.119 align:start position:0% um what we have genetic 00:39:56.119 --> 00:39:58.750 align:start position:0% um what we have genetic um<00:39:57.119> yeah<00:39:57.400> how<00:39:57.560> you<00:39:57.680> say<00:39:57.920> like<00:39:58.040> more<00:39:58.280> likelihood 00:39:58.750 --> 00:39:58.760 align:start position:0% um yeah how you say like more likelihood 00:39:58.760 --> 00:40:03.270 align:start position:0% um yeah how you say like more likelihood that<00:39:58.920> we<00:39:59.040> get<00:39:59.240> like<00:39:59.400> a<00:39:59.560> certain<00:40:00.520> um<00:40:01.000> deathly<00:40:02.280> um 00:40:03.270 --> 00:40:03.280 align:start position:0% that we get like a certain um deathly um 00:40:03.280 --> 00:40:06.750 align:start position:0% that we get like a certain um deathly um uh<00:40:03.760> disease<00:40:04.760> but<00:40:05.160> there's<00:40:05.599> also<00:40:06.240> more<00:40:06.560> like 00:40:06.750 --> 00:40:06.760 align:start position:0% uh disease but there's also more like 00:40:06.760 --> 00:40:09.309 align:start position:0% uh disease but there's also more like the<00:40:06.960> surveillance<00:40:07.760> St<00:40:08.119> type<00:40:08.480> of<00:40:08.760> data<00:40:09.160> that 00:40:09.309 --> 00:40:09.319 align:start position:0% the surveillance St type of data that 00:40:09.319 --> 00:40:13.150 align:start position:0% the surveillance St type of data that many<00:40:09.640> people<00:40:09.960> have<00:40:10.160> in<00:40:10.319> mind<00:40:10.760> so<00:40:11.599> um<00:40:12.280> yeah<00:40:12.680> yeah 00:40:13.150 --> 00:40:13.160 align:start position:0% many people have in mind so um yeah yeah 00:40:13.160 --> 00:40:14.829 align:start position:0% many people have in mind so um yeah yeah I<00:40:13.240> think<00:40:13.440> we<00:40:13.599> operate<00:40:13.960> in<00:40:14.079> a<00:40:14.240> little<00:40:14.440> bit<00:40:14.599> of<00:40:14.720> a 00:40:14.829 --> 00:40:14.839 align:start position:0% I think we operate in a little bit of a 00:40:14.839 --> 00:40:17.309 align:start position:0% I think we operate in a little bit of a tricky<00:40:15.240> place<00:40:15.640> because<00:40:15.920> we<00:40:16.079> started<00:40:16.760> well 00:40:17.309 --> 00:40:17.319 align:start position:0% tricky place because we started well 00:40:17.319 --> 00:40:19.470 align:start position:0% tricky place because we started well blockchain<00:40:17.960> ethos<00:40:18.359> kind<00:40:18.480> of<00:40:18.599> started<00:40:18.960> as 00:40:19.470 --> 00:40:19.480 align:start position:0% blockchain ethos kind of started as 00:40:19.480 --> 00:40:22.150 align:start position:0% blockchain ethos kind of started as privacy<00:40:19.960> preserving<00:40:20.920> um<00:40:21.440> that<00:40:21.599> quickly<00:40:21.920> went 00:40:22.150 --> 00:40:22.160 align:start position:0% privacy preserving um that quickly went 00:40:22.160 --> 00:40:27.390 align:start position:0% privacy preserving um that quickly went away<00:40:22.560> when<00:40:22.760> you<00:40:22.960> know<00:40:23.960> uh<00:40:24.920> you<00:40:25.200> had<00:40:26.000> um<00:40:27.000> all<00:40:27.200> the 00:40:27.390 --> 00:40:27.400 align:start position:0% away when you know uh you had um all the 00:40:27.400 --> 00:40:28.990 align:start position:0% away when you know uh you had um all the these<00:40:27.520> tools<00:40:27.839> that<00:40:27.960> are<00:40:28.119> coming<00:40:28.440> in<00:40:28.720> where<00:40:28.839> you 00:40:28.990 --> 00:40:29.000 align:start position:0% these tools that are coming in where you 00:40:29.000 --> 00:40:31.150 align:start position:0% these tools that are coming in where you can<00:40:29.359> follow<00:40:29.720> the<00:40:29.920> history<00:40:30.400> of<00:40:30.599> all<00:40:31.040> the 00:40:31.150 --> 00:40:31.160 align:start position:0% can follow the history of all the 00:40:31.160 --> 00:40:32.710 align:start position:0% can follow the history of all the different<00:40:31.480> wallets<00:40:31.920> and<00:40:32.079> what<00:40:32.240> they<00:40:32.359> do<00:40:32.560> on 00:40:32.710 --> 00:40:32.720 align:start position:0% different wallets and what they do on 00:40:32.720 --> 00:40:35.030 align:start position:0% different wallets and what they do on chain<00:40:33.200> and<00:40:33.599> how<00:40:33.760> they<00:40:33.920> connect<00:40:34.240> to<00:40:34.440> each<00:40:34.640> other 00:40:35.030 --> 00:40:35.040 align:start position:0% chain and how they connect to each other 00:40:35.040 --> 00:40:37.550 align:start position:0% chain and how they connect to each other and<00:40:35.280> you've<00:40:35.480> seen<00:40:35.800> you<00:40:35.920> know<00:40:36.640> um<00:40:36.880> authorities 00:40:37.550 --> 00:40:37.560 align:start position:0% and you've seen you know um authorities 00:40:37.560 --> 00:40:40.309 align:start position:0% and you've seen you know um authorities get<00:40:37.760> using<00:40:38.200> that<00:40:38.440> data<00:40:38.880> to<00:40:39.319> to<00:40:39.520> ban<00:40:39.880> certain 00:40:40.309 --> 00:40:40.319 align:start position:0% get using that data to to ban certain 00:40:40.319 --> 00:40:42.270 align:start position:0% get using that data to to ban certain activity<00:40:40.760> or<00:40:40.920> to<00:40:41.040> ban<00:40:41.319> certain<00:40:41.680> wallets<00:40:42.160> I'm 00:40:42.270 --> 00:40:42.280 align:start position:0% activity or to ban certain wallets I'm 00:40:42.280 --> 00:40:43.589 align:start position:0% activity or to ban certain wallets I'm not<00:40:42.400> saying<00:40:42.640> that's<00:40:42.760> a<00:40:42.880> bad<00:40:43.079> thing<00:40:43.319> I'm<00:40:43.480> just 00:40:43.589 --> 00:40:43.599 align:start position:0% not saying that's a bad thing I'm just 00:40:43.599 --> 00:40:45.430 align:start position:0% not saying that's a bad thing I'm just saying<00:40:44.280> the<00:40:44.440> truth<00:40:44.720> is<00:40:44.920> everything's<00:40:45.280> on 00:40:45.430 --> 00:40:45.440 align:start position:0% saying the truth is everything's on 00:40:45.440 --> 00:40:47.870 align:start position:0% saying the truth is everything's on chain<00:40:45.920> everything<00:40:46.400> is<00:40:46.680> available<00:40:47.319> and<00:40:47.480> tools 00:40:47.870 --> 00:40:47.880 align:start position:0% chain everything is available and tools 00:40:47.880 --> 00:40:51.109 align:start position:0% chain everything is available and tools like<00:40:48.079> Dune<00:40:48.560> are<00:40:48.960> making<00:40:49.319> that<00:40:49.520> data<00:40:49.880> even<00:40:50.200> more 00:40:51.109 --> 00:40:51.119 align:start position:0% like Dune are making that data even more 00:40:51.119 --> 00:40:54.510 align:start position:0% like Dune are making that data even more digestible<00:40:52.119> um<00:40:52.359> so<00:40:52.560> we<00:40:52.800> have<00:40:52.960> to<00:40:53.240> think 00:40:54.510 --> 00:40:54.520 align:start position:0% digestible um so we have to think 00:40:54.520 --> 00:40:56.790 align:start position:0% digestible um so we have to think about<00:40:55.520> I<00:40:55.640> think<00:40:55.760> we're<00:40:55.920> at<00:40:56.119> Crossroads<00:40:56.680> we 00:40:56.790 --> 00:40:56.800 align:start position:0% about I think we're at Crossroads we 00:40:56.800 --> 00:40:59.150 align:start position:0% about I think we're at Crossroads we have<00:40:56.880> to<00:40:57.000> think<00:40:57.359> about<00:40:57.560> how<00:40:57.720> we<00:40:57.880> use<00:40:58.240> data<00:40:58.880> and 00:40:59.150 --> 00:40:59.160 align:start position:0% have to think about how we use data and 00:40:59.160 --> 00:41:01.910 align:start position:0% have to think about how we use data and how<00:41:00.160> because<00:41:00.400> the<00:41:00.560> truth<00:41:00.839> is<00:41:01.400> companies 00:41:01.910 --> 00:41:01.920 align:start position:0% how because the truth is companies 00:41:01.920 --> 00:41:04.309 align:start position:0% how because the truth is companies organizations<00:41:02.599> are<00:41:02.880> always<00:41:03.560> want<00:41:03.960> going<00:41:04.160> to 00:41:04.309 --> 00:41:04.319 align:start position:0% organizations are always want going to 00:41:04.319 --> 00:41:05.790 align:start position:0% organizations are always want going to want<00:41:04.480> to<00:41:04.599> know<00:41:04.800> more<00:41:05.000> about<00:41:05.200> their<00:41:05.400> users 00:41:05.790 --> 00:41:05.800 align:start position:0% want to know more about their users 00:41:05.800 --> 00:41:06.950 align:start position:0% want to know more about their users because<00:41:06.000> they<00:41:06.119> want<00:41:06.200> to<00:41:06.359> grow<00:41:06.680> because<00:41:06.880> they 00:41:06.950 --> 00:41:06.960 align:start position:0% because they want to grow because they 00:41:06.960 --> 00:41:09.270 align:start position:0% because they want to grow because they want<00:41:07.079> to<00:41:07.280> maximize<00:41:07.960> profits<00:41:08.599> because 00:41:09.270 --> 00:41:09.280 align:start position:0% want to maximize profits because 00:41:09.280 --> 00:41:11.430 align:start position:0% want to maximize profits because whatever<00:41:09.680> reason<00:41:10.040> it<00:41:10.200> is<00:41:10.680> they<00:41:10.800> are<00:41:11.040> going<00:41:11.240> to 00:41:11.430 --> 00:41:11.440 align:start position:0% whatever reason it is they are going to 00:41:11.440 --> 00:41:13.390 align:start position:0% whatever reason it is they are going to want<00:41:11.640> to<00:41:12.200> know<00:41:12.480> more<00:41:12.760> and<00:41:12.880> they're<00:41:13.040> going<00:41:13.280> to 00:41:13.390 --> 00:41:13.400 align:start position:0% want to know more and they're going to 00:41:13.400 --> 00:41:15.510 align:start position:0% want to know more and they're going to leverage<00:41:13.680> this<00:41:13.839> onchain<00:41:14.280> data<00:41:14.640> is<00:41:14.720> it<00:41:15.040> okay<00:41:15.400> is 00:41:15.510 --> 00:41:15.520 align:start position:0% leverage this onchain data is it okay is 00:41:15.520 --> 00:41:18.430 align:start position:0% leverage this onchain data is it okay is it<00:41:15.800> okay<00:41:16.160> that<00:41:16.720> we're<00:41:17.000> able<00:41:17.280> to<00:41:17.760> track<00:41:18.040> a<00:41:18.200> whole 00:41:18.430 --> 00:41:18.440 align:start position:0% it okay that we're able to track a whole 00:41:18.440 --> 00:41:21.109 align:start position:0% it okay that we're able to track a whole transaction<00:41:19.079> history<00:41:19.720> and<00:41:19.920> base<00:41:20.200> our<00:41:20.440> product 00:41:21.109 --> 00:41:21.119 align:start position:0% transaction history and base our product 00:41:21.119 --> 00:41:23.150 align:start position:0% transaction history and base our product on<00:41:21.440> this<00:41:21.680> is<00:41:21.760> it<00:41:22.000> okay<00:41:22.160> that<00:41:22.280> we're<00:41:22.480> able<00:41:22.720> to 00:41:23.150 --> 00:41:23.160 align:start position:0% on this is it okay that we're able to 00:41:23.160 --> 00:41:25.069 align:start position:0% on this is it okay that we're able to connect<00:41:23.480> a<00:41:23.640> wallet<00:41:23.920> to<00:41:24.040> an<00:41:24.200> identity<00:41:24.839> because 00:41:25.069 --> 00:41:25.079 align:start position:0% connect a wallet to an identity because 00:41:25.079 --> 00:41:26.829 align:start position:0% connect a wallet to an identity because someone's<00:41:25.480> doxed<00:41:25.880> it<00:41:26.000> or<00:41:26.200> put<00:41:26.440> that 00:41:26.829 --> 00:41:26.839 align:start position:0% someone's doxed it or put that 00:41:26.839 --> 00:41:31.550 align:start position:0% someone's doxed it or put that information<00:41:27.560> on<00:41:27.760> chain<00:41:28.240> online<00:41:28.839> sorry<00:41:30.079> um<00:41:31.079> and 00:41:31.550 --> 00:41:31.560 align:start position:0% information on chain online sorry um and 00:41:31.560 --> 00:41:33.870 align:start position:0% information on chain online sorry um and is<00:41:31.680> it<00:41:31.920> also<00:41:32.680> you<00:41:32.800> know<00:41:33.119> what<00:41:33.359> what<00:41:33.560> kind<00:41:33.680> of 00:41:33.870 --> 00:41:33.880 align:start position:0% is it also you know what what kind of 00:41:33.880 --> 00:41:35.950 align:start position:0% is it also you know what what kind of product<00:41:34.200> tracking<00:41:34.520> are<00:41:34.680> we<00:41:34.800> putting<00:41:35.480> in<00:41:35.680> place 00:41:35.950 --> 00:41:35.960 align:start position:0% product tracking are we putting in place 00:41:35.960 --> 00:41:37.390 align:start position:0% product tracking are we putting in place that's<00:41:36.160> not<00:41:36.280> on<00:41:36.480> chain<00:41:36.880> that's<00:41:37.160> like 00:41:37.390 --> 00:41:37.400 align:start position:0% that's not on chain that's like 00:41:37.400 --> 00:41:39.589 align:start position:0% that's not on chain that's like proprietary<00:41:38.119> data<00:41:38.839> and<00:41:38.920> we<00:41:39.040> need<00:41:39.240> to<00:41:39.400> think 00:41:39.589 --> 00:41:39.599 align:start position:0% proprietary data and we need to think 00:41:39.599 --> 00:41:42.349 align:start position:0% proprietary data and we need to think about<00:41:39.880> how<00:41:40.000> we<00:41:40.160> do<00:41:40.400> that<00:41:40.640> as<00:41:40.800> well<00:41:41.319> um<00:41:41.800> are<00:41:41.960> we 00:41:42.349 --> 00:41:42.359 align:start position:0% about how we do that as well um are we 00:41:42.359 --> 00:41:44.950 align:start position:0% about how we do that as well um are we always<00:41:42.760> gdpr<00:41:43.480> compliant<00:41:44.160> you<00:41:44.280> know<00:41:44.560> are<00:41:44.720> we 00:41:44.950 --> 00:41:44.960 align:start position:0% always gdpr compliant you know are we 00:41:44.960 --> 00:41:47.230 align:start position:0% always gdpr compliant you know are we when<00:41:45.160> we<00:41:45.480> match<00:41:46.040> the<00:41:46.200> data<00:41:46.480> we<00:41:46.599> collect 00:41:47.230 --> 00:41:47.240 align:start position:0% when we match the data we collect 00:41:47.240 --> 00:41:49.150 align:start position:0% when we match the data we collect offchain<00:41:47.839> to<00:41:48.079> some<00:41:48.440> data<00:41:48.720> that<00:41:48.880> we<00:41:49.000> might 00:41:49.150 --> 00:41:49.160 align:start position:0% offchain to some data that we might 00:41:49.160 --> 00:41:51.270 align:start position:0% offchain to some data that we might collect<00:41:49.480> onchain<00:41:50.000> are<00:41:50.119> we<00:41:50.319> doing<00:41:50.560> it<00:41:50.720> in<00:41:50.839> a<00:41:51.000> way 00:41:51.270 --> 00:41:51.280 align:start position:0% collect onchain are we doing it in a way 00:41:51.280 --> 00:41:53.870 align:start position:0% collect onchain are we doing it in a way that<00:41:51.839> is<00:41:52.280> um<00:41:52.599> privacy<00:41:53.079> preserving<00:41:53.520> for<00:41:53.720> our 00:41:53.870 --> 00:41:53.880 align:start position:0% that is um privacy preserving for our 00:41:53.880 --> 00:41:57.550 align:start position:0% that is um privacy preserving for our users<00:41:54.480> and<00:41:54.680> most<00:41:54.960> importantly<00:41:55.800> are<00:41:56.040> our<00:41:56.319> users 00:41:57.550 --> 00:41:57.560 align:start position:0% users and most importantly are our users 00:41:57.560 --> 00:42:00.230 align:start position:0% users and most importantly are our users totally<00:41:58.079> aware<00:41:58.720> of<00:41:59.040> what<00:41:59.400> you<00:41:59.520> know<00:41:59.839> they're 00:42:00.230 --> 00:42:00.240 align:start position:0% totally aware of what you know they're 00:42:00.240 --> 00:42:02.190 align:start position:0% totally aware of what you know they're they're<00:42:00.440> signing<00:42:00.880> in<00:42:01.040> the<00:42:01.200> tnc's<00:42:01.880> it's<00:42:02.079> what 00:42:02.190 --> 00:42:02.200 align:start position:0% they're signing in the tnc's it's what 00:42:02.200 --> 00:42:05.430 align:start position:0% they're signing in the tnc's it's what you<00:42:02.319> were<00:42:02.480> saying<00:42:02.880> earlier<00:42:03.880> um<00:42:04.480> and<00:42:05.200> and<00:42:05.319> what 00:42:05.430 --> 00:42:05.440 align:start position:0% you were saying earlier um and and what 00:42:05.440 --> 00:42:07.589 align:start position:0% you were saying earlier um and and what they're<00:42:05.599> giving<00:42:05.880> away<00:42:06.280> for<00:42:06.880> for<00:42:07.119> the 00:42:07.589 --> 00:42:07.599 align:start position:0% they're giving away for for the 00:42:07.599 --> 00:42:09.670 align:start position:0% they're giving away for for the usability<00:42:08.400> of<00:42:08.640> of<00:42:08.760> the<00:42:08.920> product<00:42:09.359> I<00:42:09.440> think<00:42:09.560> that 00:42:09.670 --> 00:42:09.680 align:start position:0% usability of of the product I think that 00:42:09.680 --> 00:42:12.510 align:start position:0% usability of of the product I think that would<00:42:09.839> be<00:42:10.359> relevant<00:42:10.880> in<00:42:11.119> permission<00:42:11.680> setups 00:42:12.510 --> 00:42:12.520 align:start position:0% would be relevant in permission setups 00:42:12.520 --> 00:42:13.950 align:start position:0% would be relevant in permission setups right<00:42:12.680> but<00:42:12.800> if<00:42:12.880> you<00:42:13.040> have<00:42:13.280> permission<00:42:13.680> less 00:42:13.950 --> 00:42:13.960 align:start position:0% right but if you have permission less 00:42:13.960 --> 00:42:16.470 align:start position:0% right but if you have permission less setups<00:42:14.440> maybe<00:42:14.960> like<00:42:15.480> um<00:42:16.000> yeah<00:42:16.240> being 00:42:16.470 --> 00:42:16.480 align:start position:0% setups maybe like um yeah being 00:42:16.480 --> 00:42:19.430 align:start position:0% setups maybe like um yeah being compliant<00:42:17.119> to<00:42:17.480> a<00:42:17.680> current<00:42:18.240> already<00:42:18.640> outdated 00:42:19.430 --> 00:42:19.440 align:start position:0% compliant to a current already outdated 00:42:19.440 --> 00:42:23.230 align:start position:0% compliant to a current already outdated gdpr<00:42:20.440> um<00:42:20.720> directive<00:42:21.480> is<00:42:21.760> maybe<00:42:22.680> maybe<00:42:22.960> not 00:42:23.230 --> 00:42:23.240 align:start position:0% gdpr um directive is maybe maybe not 00:42:23.240 --> 00:42:25.710 align:start position:0% gdpr um directive is maybe maybe not like<00:42:23.520> what<00:42:23.640> you<00:42:23.960> should<00:42:24.520> orientate<00:42:25.520> um 00:42:25.710 --> 00:42:25.720 align:start position:0% like what you should orientate um 00:42:25.720 --> 00:42:27.710 align:start position:0% like what you should orientate um yourself<00:42:26.200> about<00:42:26.599> so<00:42:26.880> let 00:42:27.710 --> 00:42:27.720 align:start position:0% yourself about so let 00:42:27.720 --> 00:42:29.589 align:start position:0% yourself about so let think<00:42:27.920> about<00:42:28.119> a<00:42:28.280> second<00:42:28.720> example<00:42:29.240> that<00:42:29.400> would 00:42:29.589 --> 00:42:29.599 align:start position:0% think about a second example that would 00:42:29.599 --> 00:42:34.030 align:start position:0% think about a second example that would be<00:42:30.599> um<00:42:31.200> the<00:42:32.160> uh<00:42:32.520> transfer<00:42:33.200> rules<00:42:33.760> for 00:42:34.030 --> 00:42:34.040 align:start position:0% be um the uh transfer rules for 00:42:34.040 --> 00:42:35.670 align:start position:0% be um the uh transfer rules for financial<00:42:34.520> institutions<00:42:35.160> where<00:42:35.319> basically 00:42:35.670 --> 00:42:35.680 align:start position:0% financial institutions where basically 00:42:35.680 --> 00:42:37.750 align:start position:0% financial institutions where basically for<00:42:36.000> every<00:42:36.319> crypto<00:42:36.800> transactions<00:42:37.520> and<00:42:37.640> we 00:42:37.750 --> 00:42:37.760 align:start position:0% for every crypto transactions and we 00:42:37.760 --> 00:42:40.230 align:start position:0% for every crypto transactions and we don't<00:42:38.000> have<00:42:38.200> that<00:42:38.359> in<00:42:38.480> the<00:42:38.640> Fiat<00:42:39.160> system<00:42:40.000> a 00:42:40.230 --> 00:42:40.240 align:start position:0% don't have that in the Fiat system a 00:42:40.240 --> 00:42:42.349 align:start position:0% don't have that in the Fiat system a financial<00:42:40.760> institution<00:42:41.520> would<00:42:41.839> have<00:42:42.040> to 00:42:42.349 --> 00:42:42.359 align:start position:0% financial institution would have to 00:42:42.359 --> 00:42:45.109 align:start position:0% financial institution would have to store<00:42:42.880> like<00:42:43.240> the<00:42:43.400> or<00:42:43.599> collect<00:42:44.000> the<00:42:44.200> data<00:42:44.640> of 00:42:45.109 --> 00:42:45.119 align:start position:0% store like the or collect the data of 00:42:45.119 --> 00:42:47.549 align:start position:0% store like the or collect the data of the<00:42:45.280> sender<00:42:45.760> the<00:42:46.000> recipients<00:42:46.960> their 00:42:47.549 --> 00:42:47.559 align:start position:0% the sender the recipients their 00:42:47.559 --> 00:42:50.109 align:start position:0% the sender the recipients their identification<00:42:48.559> the<00:42:48.839> source<00:42:49.160> of<00:42:49.359> funds<00:42:49.760> or 00:42:50.109 --> 00:42:50.119 align:start position:0% identification the source of funds or 00:42:50.119 --> 00:42:54.750 align:start position:0% identification the source of funds or whatsoever<00:42:50.760> it's<00:42:50.960> like<00:42:51.839> like<00:42:52.839> a<00:42:53.200> very<00:42:53.760> poor 00:42:54.750 --> 00:42:54.760 align:start position:0% whatsoever it's like like a very poor 00:42:54.760 --> 00:42:57.950 align:start position:0% whatsoever it's like like a very poor requirement<00:42:55.480> and<00:42:55.800> technologies<00:42:56.800> that<00:42:57.359> they 00:42:57.950 --> 00:42:57.960 align:start position:0% requirement and technologies that they 00:42:57.960 --> 00:43:00.790 align:start position:0% requirement and technologies that they um<00:42:58.319> have<00:42:58.559> been<00:42:59.359> um<00:42:59.599> adopting<00:43:00.319> where<00:43:00.599> we 00:43:00.790 --> 00:43:00.800 align:start position:0% um have been um adopting where we 00:43:00.800 --> 00:43:03.030 align:start position:0% um have been um adopting where we already<00:43:01.240> have<00:43:01.559> like<00:43:01.880> really<00:43:02.400> impactful 00:43:03.030 --> 00:43:03.040 align:start position:0% already have like really impactful 00:43:03.040 --> 00:43:05.990 align:start position:0% already have like really impactful Solutions<00:43:03.720> in<00:43:03.960> the<00:43:04.119> crypto<00:43:04.520> space<00:43:05.280> that<00:43:05.480> could 00:43:05.990 --> 00:43:06.000 align:start position:0% Solutions in the crypto space that could 00:43:06.000 --> 00:43:09.829 align:start position:0% Solutions in the crypto space that could protect<00:43:06.480> also<00:43:07.119> users<00:43:08.040> um<00:43:08.599> that<00:43:09.200> haven't<00:43:09.520> been 00:43:09.829 --> 00:43:09.839 align:start position:0% protect also users um that haven't been 00:43:09.839 --> 00:43:12.870 align:start position:0% protect also users um that haven't been anticipated<00:43:10.640> yet<00:43:10.839> or<00:43:11.040> Technologies<00:43:11.640> in<00:43:11.880> gdpr 00:43:12.870 --> 00:43:12.880 align:start position:0% anticipated yet or Technologies in gdpr 00:43:12.880 --> 00:43:16.470 align:start position:0% anticipated yet or Technologies in gdpr and<00:43:13.800> um 00:43:16.470 --> 00:43:16.480 align:start position:0% and um 00:43:16.480 --> 00:43:19.510 align:start position:0% and um yeah 00:43:19.510 --> 00:43:19.520 align:start position:0% 00:43:19.520 --> 00:43:21.470 align:start position:0% awesome<00:43:20.520> let's<00:43:20.720> see 00:43:21.470 --> 00:43:21.480 align:start position:0% awesome let's see 00:43:21.480 --> 00:43:24.109 align:start position:0% awesome let's see so<00:43:22.480> I<00:43:22.559> think<00:43:22.720> that<00:43:22.920> web<00:43:23.119> 2<00:43:23.599> has<00:43:23.880> and<00:43:24.000> the 00:43:24.109 --> 00:43:24.119 align:start position:0% so I think that web 2 has and the 00:43:24.119 --> 00:43:25.390 align:start position:0% so I think that web 2 has and the internet<00:43:24.400> in<00:43:24.480> general<00:43:24.800> has<00:43:24.960> proven<00:43:25.280> that 00:43:25.390 --> 00:43:25.400 align:start position:0% internet in general has proven that 00:43:25.400 --> 00:43:26.750 align:start position:0% internet in general has proven that people<00:43:25.599> are<00:43:25.800> not<00:43:26.079> that<00:43:26.240> concerned<00:43:26.640> about 00:43:26.750 --> 00:43:26.760 align:start position:0% people are not that concerned about 00:43:26.760 --> 00:43:29.430 align:start position:0% people are not that concerned about their<00:43:26.920> PR<00:43:27.280> privacy<00:43:28.280> um<00:43:28.640> For<00:43:28.800> Better<00:43:29.000> or<00:43:29.119> Worse 00:43:29.430 --> 00:43:29.440 align:start position:0% their PR privacy um For Better or Worse 00:43:29.440 --> 00:43:33.069 align:start position:0% their PR privacy um For Better or Worse that<00:43:29.760> but<00:43:29.920> I<00:43:30.040> do<00:43:30.280> think<00:43:30.839> counter<00:43:31.200> to<00:43:31.440> that<00:43:32.200> uh 00:43:33.069 --> 00:43:33.079 align:start position:0% that but I do think counter to that uh 00:43:33.079 --> 00:43:35.030 align:start position:0% that but I do think counter to that uh we're<00:43:33.359> given<00:43:33.599> a<00:43:33.720> lot<00:43:33.839> of<00:43:34.000> data<00:43:34.400> and<00:43:34.520> a<00:43:34.640> lot<00:43:34.760> of 00:43:35.030 --> 00:43:35.040 align:start position:0% we're given a lot of data and a lot of 00:43:35.040 --> 00:43:37.549 align:start position:0% we're given a lot of data and a lot of information<00:43:36.040> um<00:43:36.359> sometimes<00:43:36.559> it<00:43:36.680> feels<00:43:36.960> like 00:43:37.549 --> 00:43:37.559 align:start position:0% information um sometimes it feels like 00:43:37.559 --> 00:43:39.670 align:start position:0% information um sometimes it feels like uh<00:43:38.520> you<00:43:38.640> know<00:43:38.760> it<00:43:38.880> can<00:43:39.000> be<00:43:39.119> a<00:43:39.200> blessing<00:43:39.440> or<00:43:39.559> a 00:43:39.670 --> 00:43:39.680 align:start position:0% uh you know it can be a blessing or a 00:43:39.680 --> 00:43:41.030 align:start position:0% uh you know it can be a blessing or a curse<00:43:39.960> I<00:43:40.040> think<00:43:40.319> sometimes<00:43:40.520> we<00:43:40.640> have<00:43:40.720> a<00:43:40.839> hard 00:43:41.030 --> 00:43:41.040 align:start position:0% curse I think sometimes we have a hard 00:43:41.040 --> 00:43:43.910 align:start position:0% curse I think sometimes we have a hard time<00:43:41.200> finding<00:43:41.480> the<00:43:41.640> signal<00:43:42.200> in<00:43:42.359> that<00:43:42.559> data<00:43:43.280> um 00:43:43.910 --> 00:43:43.920 align:start position:0% time finding the signal in that data um 00:43:43.920 --> 00:43:45.230 align:start position:0% time finding the signal in that data um which<00:43:44.040> can<00:43:44.160> be<00:43:44.280> a<00:43:44.359> real<00:43:44.520> challenge<00:43:45.000> something 00:43:45.230 --> 00:43:45.240 align:start position:0% which can be a real challenge something 00:43:45.240 --> 00:43:50.750 align:start position:0% which can be a real challenge something we're<00:43:45.400> working<00:43:45.760> on<00:43:46.880> um<00:43:48.280> but<00:43:49.280> I<00:43:49.400> think<00:43:50.240> it's<00:43:50.520> not 00:43:50.750 --> 00:43:50.760 align:start position:0% we're working on um but I think it's not 00:43:50.760 --> 00:43:52.710 align:start position:0% we're working on um but I think it's not so<00:43:51.720> I<00:43:51.800> don't<00:43:51.920> think<00:43:52.079> we<00:43:52.160> need<00:43:52.319> to<00:43:52.480> make 00:43:52.710 --> 00:43:52.720 align:start position:0% so I don't think we need to make 00:43:52.720 --> 00:43:54.470 align:start position:0% so I don't think we need to make decisions<00:43:53.200> for<00:43:53.520> people<00:43:53.960> I<00:43:54.079> just<00:43:54.240> think<00:43:54.359> we 00:43:54.470 --> 00:43:54.480 align:start position:0% decisions for people I just think we 00:43:54.480 --> 00:43:56.670 align:start position:0% decisions for people I just think we need<00:43:54.640> to<00:43:54.880> communicate<00:43:55.559> clearly<00:43:56.280> you<00:43:56.400> know 00:43:56.670 --> 00:43:56.680 align:start position:0% need to communicate clearly you know 00:43:56.680 --> 00:43:58.990 align:start position:0% need to communicate clearly you know what<00:43:57.160> is<00:43:57.280> it<00:43:57.480> that<00:43:57.599> you're<00:43:57.839> giving<00:43:58.480> what<00:43:58.640> is<00:43:58.760> it 00:43:58.990 --> 00:43:59.000 align:start position:0% what is it that you're giving what is it 00:43:59.000 --> 00:44:01.309 align:start position:0% what is it that you're giving what is it that<00:43:59.119> you're<00:43:59.480> getting<00:44:00.480> um<00:44:00.599> for<00:44:00.800> example<00:44:01.160> you 00:44:01.309 --> 00:44:01.319 align:start position:0% that you're getting um for example you 00:44:01.319 --> 00:44:05.190 align:start position:0% that you're getting um for example you know<00:44:01.920> like<00:44:02.920> uh<00:44:03.839> I'm<00:44:03.960> not<00:44:04.160> transactional<00:44:05.079> when 00:44:05.190 --> 00:44:05.200 align:start position:0% know like uh I'm not transactional when 00:44:05.200 --> 00:44:07.630 align:start position:0% know like uh I'm not transactional when it<00:44:05.319> comes<00:44:05.559> to<00:44:06.280> my<00:44:06.440> friends<00:44:06.800> or<00:44:07.000> my<00:44:07.160> family<00:44:07.480> or 00:44:07.630 --> 00:44:07.640 align:start position:0% it comes to my friends or my family or 00:44:07.640 --> 00:44:10.270 align:start position:0% it comes to my friends or my family or my<00:44:07.800> community<00:44:08.760> but<00:44:08.920> if<00:44:09.079> I'm<00:44:09.240> engaging<00:44:09.839> with 00:44:10.270 --> 00:44:10.280 align:start position:0% my community but if I'm engaging with 00:44:10.280 --> 00:44:12.309 align:start position:0% my community but if I'm engaging with you<00:44:10.400> know<00:44:11.119> a<00:44:11.319> government<00:44:11.800> if<00:44:11.920> I'm<00:44:12.079> paying 00:44:12.309 --> 00:44:12.319 align:start position:0% you know a government if I'm paying 00:44:12.319 --> 00:44:14.030 align:start position:0% you know a government if I'm paying taxes<00:44:12.760> or<00:44:12.880> if<00:44:13.000> I'm<00:44:13.319> you<00:44:13.440> know<00:44:13.640> getting<00:44:13.920> a 00:44:14.030 --> 00:44:14.040 align:start position:0% taxes or if I'm you know getting a 00:44:14.040 --> 00:44:15.870 align:start position:0% taxes or if I'm you know getting a subscription<00:44:14.520> with<00:44:14.680> a<00:44:14.839> company<00:44:15.319> like<00:44:15.680> I<00:44:15.760> want 00:44:15.870 --> 00:44:15.880 align:start position:0% subscription with a company like I want 00:44:15.880 --> 00:44:17.430 align:start position:0% subscription with a company like I want to<00:44:16.040> know<00:44:16.280> like<00:44:16.480> what<00:44:16.599> am<00:44:16.720> I<00:44:16.880> giving<00:44:17.160> and<00:44:17.280> what 00:44:17.430 --> 00:44:17.440 align:start position:0% to know like what am I giving and what 00:44:17.440 --> 00:44:20.710 align:start position:0% to know like what am I giving and what am<00:44:17.520> I<00:44:17.680> getting<00:44:18.400> and<00:44:18.559> I<00:44:18.680> think<00:44:18.880> we<00:44:19.119> just<00:44:19.640> we<00:44:20.559> be 00:44:20.710 --> 00:44:20.720 align:start position:0% am I getting and I think we just we be 00:44:20.720 --> 00:44:22.470 align:start position:0% am I getting and I think we just we be as<00:44:20.839> clear<00:44:21.119> as<00:44:21.319> possible<00:44:21.640> about<00:44:21.960> that<00:44:22.200> and<00:44:22.319> the 00:44:22.470 --> 00:44:22.480 align:start position:0% as clear as possible about that and the 00:44:22.480 --> 00:44:23.950 align:start position:0% as clear as possible about that and the design<00:44:22.760> and<00:44:22.880> the<00:44:23.079> product<00:44:23.359> and<00:44:23.520> let<00:44:23.680> people 00:44:23.950 --> 00:44:23.960 align:start position:0% design and the product and let people 00:44:23.960 --> 00:44:25.230 align:start position:0% design and the product and let people make<00:44:24.160> decisions<00:44:24.520> for<00:44:24.800> themselves<00:44:25.079> and 00:44:25.230 --> 00:44:25.240 align:start position:0% make decisions for themselves and 00:44:25.240 --> 00:44:27.230 align:start position:0% make decisions for themselves and obviously<00:44:25.520> there<00:44:25.599> will<00:44:25.720> be<00:44:25.839> a<00:44:25.960> parallel<00:44:27.160> you 00:44:27.230 --> 00:44:27.240 align:start position:0% obviously there will be a parallel you 00:44:27.240 --> 00:44:29.470 align:start position:0% obviously there will be a parallel you know<00:44:27.400> government<00:44:28.240> uh<00:44:28.559> conversation<00:44:29.119> I<00:44:29.240> assume 00:44:29.470 --> 00:44:29.480 align:start position:0% know government uh conversation I assume 00:44:29.480 --> 00:44:30.870 align:start position:0% know government uh conversation I assume someone's<00:44:29.800> handling<00:44:30.319> uh<00:44:30.599> you<00:44:30.720> know 00:44:30.870 --> 00:44:30.880 align:start position:0% someone's handling uh you know 00:44:30.880 --> 00:44:33.069 align:start position:0% someone's handling uh you know compliance<00:44:31.599> uh<00:44:31.760> that's<00:44:32.559> you<00:44:32.640> know<00:44:32.880> they 00:44:33.069 --> 00:44:33.079 align:start position:0% compliance uh that's you know they 00:44:33.079 --> 00:44:34.270 align:start position:0% compliance uh that's you know they usually<00:44:33.480> tell 00:44:34.270 --> 00:44:34.280 align:start position:0% usually tell 00:44:34.280 --> 00:44:38.390 align:start position:0% usually tell us<00:44:35.280> so<00:44:35.760> yeah<00:44:36.240> so<00:44:36.800> I<00:44:36.960> I<00:44:37.040> want<00:44:37.119> to<00:44:37.359> have<00:44:37.720> uh<00:44:38.000> one 00:44:38.390 --> 00:44:38.400 align:start position:0% us so yeah so I I want to have uh one 00:44:38.400 --> 00:44:40.549 align:start position:0% us so yeah so I I want to have uh one last<00:44:38.800> round<00:44:39.079> of<00:44:39.280> like<00:44:39.440> a<00:44:39.599> lightning<00:44:40.119> round<00:44:40.319> of 00:44:40.549 --> 00:44:40.559 align:start position:0% last round of like a lightning round of 00:44:40.559 --> 00:44:43.990 align:start position:0% last round of like a lightning round of questions<00:44:41.400> so<00:44:41.640> if<00:44:41.760> you<00:44:42.000> had<00:44:42.160> a<00:44:42.400> magic<00:44:42.760> W<00:44:43.680> and 00:44:43.990 --> 00:44:44.000 align:start position:0% questions so if you had a magic W and 00:44:44.000 --> 00:44:46.670 align:start position:0% questions so if you had a magic W and you<00:44:44.119> could<00:44:44.400> ask<00:44:44.640> for<00:44:44.920> any<00:44:45.160> feature<00:44:45.839> as<00:44:45.960> a<00:44:46.119> user 00:44:46.670 --> 00:44:46.680 align:start position:0% you could ask for any feature as a user 00:44:46.680 --> 00:44:51.670 align:start position:0% you could ask for any feature as a user in<00:44:47.040> web<00:44:47.280> 3<00:44:47.640> what<00:44:47.760> would<00:44:47.960> that 00:44:51.670 --> 00:44:51.680 align:start position:0% 00:44:51.680 --> 00:44:55.829 align:start position:0% be<00:44:52.800> okay<00:44:53.800> connecting<00:44:54.200> to<00:44:54.400> my<00:44:55.000> most<00:44:55.319> recent 00:44:55.829 --> 00:44:55.839 align:start position:0% be okay connecting to my most recent 00:44:55.839 --> 00:44:58.349 align:start position:0% be okay connecting to my most recent painful<00:44:56.520> experience<00:44:57.200> I<00:44:57.280> would<00:44:57.440> like<00:44:57.599> to<00:44:57.920> have 00:44:58.349 --> 00:44:58.359 align:start position:0% painful experience I would like to have 00:44:58.359 --> 00:45:02.230 align:start position:0% painful experience I would like to have like<00:44:59.240> um<00:44:59.640> an<00:44:59.880> account<00:45:00.599> that<00:45:01.200> um<00:45:01.520> abstract<00:45:02.040> the 00:45:02.230 --> 00:45:02.240 align:start position:0% like um an account that um abstract the 00:45:02.240 --> 00:45:04.990 align:start position:0% like um an account that um abstract the gas<00:45:02.480> fees<00:45:02.839> and<00:45:03.040> allows<00:45:03.440> me<00:45:03.680> for<00:45:04.160> multi-chain 00:45:04.990 --> 00:45:05.000 align:start position:0% gas fees and allows me for multi-chain 00:45:05.000 --> 00:45:07.150 align:start position:0% gas fees and allows me for multi-chain interactions<00:45:05.760> when<00:45:05.920> I<00:45:06.079> for<00:45:06.280> example<00:45:06.720> want<00:45:06.960> to 00:45:07.150 --> 00:45:07.160 align:start position:0% interactions when I for example want to 00:45:07.160 --> 00:45:10.630 align:start position:0% interactions when I for example want to do<00:45:07.400> a<00:45:07.720> multi-chain<00:45:08.720> um<00:45:09.200> briding<00:45:09.760> of<00:45:09.960> funds<00:45:10.400> and 00:45:10.630 --> 00:45:10.640 align:start position:0% do a multi-chain um briding of funds and 00:45:10.640 --> 00:45:16.030 align:start position:0% do a multi-chain um briding of funds and trades<00:45:11.200> or<00:45:12.240> yeah<00:45:13.240> um<00:45:14.000> having<00:45:15.000> pool<00:45:15.680> assets 00:45:16.030 --> 00:45:16.040 align:start position:0% trades or yeah um having pool assets 00:45:16.040 --> 00:45:17.589 align:start position:0% trades or yeah um having pool assets from<00:45:16.319> different<00:45:16.599> chains<00:45:17.000> for<00:45:17.200> example 00:45:17.589 --> 00:45:17.599 align:start position:0% from different chains for example 00:45:17.599 --> 00:45:19.430 align:start position:0% from different chains for example something<00:45:17.880> from<00:45:18.040> the<00:45:18.160> poka<00:45:18.800> environment 00:45:19.430 --> 00:45:19.440 align:start position:0% something from the poka environment 00:45:19.440 --> 00:45:21.309 align:start position:0% something from the poka environment where<00:45:19.720> this<00:45:19.920> is<00:45:20.119> not<00:45:20.599> uh<00:45:20.839> where<00:45:21.000> it's<00:45:21.119> even 00:45:21.309 --> 00:45:21.319 align:start position:0% where this is not uh where it's even 00:45:21.319 --> 00:45:22.630 align:start position:0% where this is not uh where it's even more<00:45:21.480> painful<00:45:21.839> than 00:45:22.630 --> 00:45:22.640 align:start position:0% more painful than 00:45:22.640 --> 00:45:27.470 align:start position:0% more painful than ethereum<00:45:23.640> watch<00:45:23.880> it 00:45:27.470 --> 00:45:27.480 align:start position:0% 00:45:27.480 --> 00:45:30.990 align:start position:0% uh<00:45:27.640> so<00:45:27.960> at<00:45:28.079> the<00:45:28.200> moment<00:45:29.040> um<00:45:29.880> we're<00:45:30.079> working<00:45:30.440> on 00:45:30.990 --> 00:45:31.000 align:start position:0% uh so at the moment um we're working on 00:45:31.000 --> 00:45:33.349 align:start position:0% uh so at the moment um we're working on uh<00:45:31.119> integrating<00:45:31.640> AI<00:45:32.000> more<00:45:32.200> into<00:45:32.640> kind<00:45:32.760> of<00:45:33.079> the 00:45:33.349 --> 00:45:33.359 align:start position:0% uh integrating AI more into kind of the 00:45:33.359 --> 00:45:36.109 align:start position:0% uh integrating AI more into kind of the data<00:45:33.680> analyst<00:45:34.079> workflow<00:45:34.680> at<00:45:34.880> Dune<00:45:35.520> and<00:45:36.000> uh 00:45:36.109 --> 00:45:36.119 align:start position:0% data analyst workflow at Dune and uh 00:45:36.119 --> 00:45:37.589 align:start position:0% data analyst workflow at Dune and uh unexpectedly<00:45:36.800> I<00:45:36.920> found<00:45:37.119> that<00:45:37.280> really 00:45:37.589 --> 00:45:37.599 align:start position:0% unexpectedly I found that really 00:45:37.599 --> 00:45:40.109 align:start position:0% unexpectedly I found that really powerful<00:45:38.200> personally<00:45:39.200> um<00:45:39.520> I'm<00:45:39.680> relatively 00:45:40.109 --> 00:45:40.119 align:start position:0% powerful personally um I'm relatively 00:45:40.119 --> 00:45:41.630 align:start position:0% powerful personally um I'm relatively new<00:45:40.280> to<00:45:40.440> the<00:45:40.599> space<00:45:40.920> you<00:45:41.000> know<00:45:41.200> trying<00:45:41.480> to 00:45:41.630 --> 00:45:41.640 align:start position:0% new to the space you know trying to 00:45:41.640 --> 00:45:44.030 align:start position:0% new to the space you know trying to learn<00:45:41.839> SQL<00:45:42.800> um<00:45:42.960> but<00:45:43.079> being<00:45:43.280> able<00:45:43.520> to<00:45:43.720> kind<00:45:43.839> of 00:45:44.030 --> 00:45:44.040 align:start position:0% learn SQL um but being able to kind of 00:45:44.040 --> 00:45:46.390 align:start position:0% learn SQL um but being able to kind of have<00:45:44.319> this<00:45:44.839> conversation<00:45:45.839> uh<00:45:46.000> it's<00:45:46.160> really 00:45:46.390 --> 00:45:46.400 align:start position:0% have this conversation uh it's really 00:45:46.400 --> 00:45:48.230 align:start position:0% have this conversation uh it's really like<00:45:46.520> an<00:45:46.680> education<00:45:47.200> you<00:45:47.280> can<00:45:47.400> see<00:45:47.599> the<00:45:47.720> div<00:45:48.079> on 00:45:48.230 --> 00:45:48.240 align:start position:0% like an education you can see the div on 00:45:48.240 --> 00:45:50.390 align:start position:0% like an education you can see the div on the<00:45:48.400> on<00:45:48.520> the<00:45:48.640> left<00:45:48.800> and<00:45:48.920> the<00:45:49.119> right<00:45:49.920> um<00:45:50.119> and<00:45:50.200> so 00:45:50.390 --> 00:45:50.400 align:start position:0% the on the left and the right um and so 00:45:50.400 --> 00:45:52.910 align:start position:0% the on the left and the right um and so I<00:45:50.480> think<00:45:50.680> I<00:45:50.760> think<00:45:50.960> more<00:45:51.079> of<00:45:51.240> that<00:45:51.839> um<00:45:52.520> uh<00:45:52.760> right 00:45:52.910 --> 00:45:52.920 align:start position:0% I think I think more of that um uh right 00:45:52.920 --> 00:45:56.670 align:start position:0% I think I think more of that um uh right now<00:45:53.079> we<00:45:53.240> had<00:45:53.440> this<00:45:53.599> kind<00:45:53.720> of<00:45:54.319> past<00:45:54.599> year<00:45:55.000> of<00:45:56.000> um 00:45:56.670 --> 00:45:56.680 align:start position:0% now we had this kind of past year of um 00:45:56.680 --> 00:45:58.430 align:start position:0% now we had this kind of past year of um you<00:45:57.040> know<00:45:57.280> an<00:45:57.400> explosion<00:45:57.760> of<00:45:57.880> AI<00:45:58.160> but<00:45:58.319> like 00:45:58.430 --> 00:45:58.440 align:start position:0% you know an explosion of AI but like 00:45:58.440 --> 00:46:01.030 align:start position:0% you know an explosion of AI but like using<00:45:58.760> it<00:45:59.400> uh<00:45:59.920> like<00:46:00.079> intelligently<00:46:00.920> like 00:46:01.030 --> 00:46:01.040 align:start position:0% using it uh like intelligently like 00:46:01.040 --> 00:46:03.790 align:start position:0% using it uh like intelligently like where<00:46:01.240> people<00:46:01.480> already<00:46:01.760> are<00:46:02.480> I<00:46:02.559> think<00:46:02.720> is<00:46:03.119> uh 00:46:03.790 --> 00:46:03.800 align:start position:0% where people already are I think is uh 00:46:03.800 --> 00:46:07.390 align:start position:0% where people already are I think is uh could<00:46:03.960> be<00:46:04.040> a<00:46:04.119> lot<00:46:04.240> of<00:46:04.319> fun<00:46:04.640> could<00:46:04.760> be<00:46:04.880> really 00:46:07.390 --> 00:46:07.400 align:start position:0% 00:46:07.400 --> 00:46:10.910 align:start position:0% useful<00:46:08.440> um<00:46:09.440> probably<00:46:09.760> wishful<00:46:10.319> thinking<00:46:10.760> but 00:46:10.910 --> 00:46:10.920 align:start position:0% useful um probably wishful thinking but 00:46:10.920 --> 00:46:13.670 align:start position:0% useful um probably wishful thinking but I<00:46:11.079> like<00:46:11.480> one<00:46:11.880> place<00:46:12.240> where<00:46:12.400> I<00:46:12.480> can<00:46:12.680> interact 00:46:13.670 --> 00:46:13.680 align:start position:0% I like one place where I can interact 00:46:13.680 --> 00:46:19.549 align:start position:0% I like one place where I can interact with<00:46:14.680> all<00:46:15.280> crypto<00:46:16.280> web<00:46:16.559> 3<00:46:17.400> stuff<00:46:18.160> like<00:46:19.160> all<00:46:19.359> my 00:46:19.549 --> 00:46:19.559 align:start position:0% with all crypto web 3 stuff like all my 00:46:19.559 --> 00:46:22.309 align:start position:0% with all crypto web 3 stuff like all my balances<00:46:20.079> in<00:46:20.280> one<00:46:20.599> place<00:46:21.359> being<00:46:21.680> able<00:46:21.960> to<00:46:22.119> use 00:46:22.309 --> 00:46:22.319 align:start position:0% balances in one place being able to use 00:46:22.319 --> 00:46:25.069 align:start position:0% balances in one place being able to use all<00:46:22.559> my<00:46:22.760> funds<00:46:23.760> and<00:46:23.960> and<00:46:24.280> one<00:46:24.480> place<00:46:24.680> that<00:46:24.839> I 00:46:25.069 --> 00:46:25.079 align:start position:0% all my funds and and one place that I 00:46:25.079 --> 00:46:28.589 align:start position:0% all my funds and and one place that I trust<00:46:26.079> and<00:46:26.319> I<00:46:26.520> I<00:46:26.599> can<00:46:26.920> self<00:46:27.200> custody<00:46:27.640> my<00:46:28.240> funds 00:46:28.589 --> 00:46:28.599 align:start position:0% trust and I I can self custody my funds 00:46:28.599 --> 00:46:30.390 align:start position:0% trust and I I can self custody my funds in<00:46:28.720> a<00:46:28.880> secure 00:46:30.390 --> 00:46:30.400 align:start position:0% in a secure 00:46:30.400 --> 00:46:32.829 align:start position:0% in a secure way<00:46:31.400> I<00:46:31.520> I<00:46:31.640> agree<00:46:31.920> as<00:46:32.040> well<00:46:32.240> I<00:46:32.319> think<00:46:32.520> as<00:46:32.640> we 00:46:32.829 --> 00:46:32.839 align:start position:0% way I I agree as well I think as we 00:46:32.839 --> 00:46:34.950 align:start position:0% way I I agree as well I think as we mature<00:46:33.240> as<00:46:33.359> a<00:46:33.480> user<00:46:33.760> and<00:46:33.920> Industry<00:46:34.359> I<00:46:34.440> think<00:46:34.680> we 00:46:34.950 --> 00:46:34.960 align:start position:0% mature as a user and Industry I think we 00:46:34.960 --> 00:46:38.589 align:start position:0% mature as a user and Industry I think we converge<00:46:35.480> to<00:46:36.359> having<00:46:36.800> Simplicity<00:46:37.800> uh 00:46:38.589 --> 00:46:38.599 align:start position:0% converge to having Simplicity uh 00:46:38.599 --> 00:46:41.190 align:start position:0% converge to having Simplicity uh essentially<00:46:39.599> um<00:46:39.920> with<00:46:40.119> that<00:46:40.240> we<00:46:40.359> are<00:46:40.640> a<00:46:40.800> minute 00:46:41.190 --> 00:46:41.200 align:start position:0% essentially um with that we are a minute 00:46:41.200 --> 00:46:45.109 align:start position:0% essentially um with that we are a minute over<00:46:41.599> time<00:46:42.000> that<00:46:42.240> concludes<00:46:42.880> our<00:46:43.520> panel<00:46:44.520> uh 00:46:45.109 --> 00:46:45.119 align:start position:0% over time that concludes our panel uh 00:46:45.119 --> 00:46:48.750 align:start position:0% over time that concludes our panel uh thank<00:46:45.319> you<00:46:45.599> to<00:46:46.200> Romina<00:46:46.760> Austin<00:46:47.280> and<00:46:47.480> Alice<00:46:48.280> uh 00:46:48.750 --> 00:46:48.760 align:start position:0% thank you to Romina Austin and Alice uh 00:46:48.760 --> 00:46:50.829 align:start position:0% thank you to Romina Austin and Alice uh thanks<00:46:48.920> for<00:46:49.079> sharing<00:46:49.400> all<00:46:49.520> the<00:46:49.680> information 00:46:50.829 --> 00:46:50.839 align:start position:0% thanks for sharing all the information 00:46:50.839 --> 00:46:52.910 align:start position:0% thanks for sharing all the information really<00:46:51.839> thanks 00:46:52.910 --> 00:46:52.920 align:start position:0% really thanks 00:46:52.920 --> 00:46:57.430 align:start position:0% really thanks everyone<00:46:54.240> thanks<00:46:55.240> we<00:46:55.440> have<00:46:55.800> Q&A<00:46:56.280> I<00:46:56.440> think 00:46:57.430 --> 00:46:57.440 align:start position:0% everyone thanks we have Q&A I think 00:46:57.440 --> 00:47:00.589 align:start position:0% everyone thanks we have Q&A I think yeah<00:46:57.839> that<00:46:57.960> was 00:47:00.589 --> 00:47:00.599 align:start position:0% 00:47:00.599 --> 00:47:03.710 align:start position:0% an<00:47:01.599> that<00:47:01.800> was<00:47:01.920> an<00:47:02.119> amazing<00:47:02.640> panel<00:47:03.280> thank<00:47:03.480> you 00:47:03.710 --> 00:47:03.720 align:start position:0% an that was an amazing panel thank you 00:47:03.720 --> 00:47:07.470 align:start position:0% an that was an amazing panel thank you everyone<00:47:04.440> please<00:47:05.079> don't<00:47:05.359> forget<00:47:06.160> to<00:47:06.920> scan<00:47:07.280> the 00:47:07.470 --> 00:47:07.480 align:start position:0% everyone please don't forget to scan the 00:47:07.480 --> 00:47:11.430 align:start position:0% everyone please don't forget to scan the QR<00:47:07.920> code<00:47:08.640> so<00:47:08.880> you<00:47:09.040> can<00:47:09.280> write<00:47:09.640> your<00:47:10.440> questions 00:47:11.430 --> 00:47:11.440 align:start position:0% QR code so you can write your questions 00:47:11.440 --> 00:47:14.670 align:start position:0% QR code so you can write your questions uh<00:47:11.640> in<00:47:11.839> the<00:47:12.040> in<00:47:12.200> the<00:47:12.400> app<00:47:13.200> so<00:47:13.440> we<00:47:13.599> can<00:47:14.079> follow<00:47:14.400> up 00:47:14.670 --> 00:47:14.680 align:start position:0% uh in the in the app so we can follow up 00:47:14.680 --> 00:47:17.870 align:start position:0% uh in the in the app so we can follow up with<00:47:14.880> with<00:47:15.040> some<00:47:15.359> questions<00:47:16.040> for<00:47:17.040> uh<00:47:17.520> the 00:47:17.870 --> 00:47:17.880 align:start position:0% with with some questions for uh the 00:47:17.880 --> 00:47:19.910 align:start position:0% with with some questions for uh the panel<00:47:18.400> here<00:47:18.760> so<00:47:19.000> please<00:47:19.240> we<00:47:19.440> have<00:47:19.720> we<00:47:19.839> are 00:47:19.910 --> 00:47:19.920 align:start position:0% panel here so please we have we are 00:47:19.920 --> 00:47:21.990 align:start position:0% panel here so please we have we are going<00:47:20.079> to<00:47:20.200> have<00:47:20.319> a<00:47:20.440> minute<00:47:21.079> to<00:47:21.319> have<00:47:21.559> that<00:47:21.720> so 00:47:21.990 --> 00:47:22.000 align:start position:0% going to have a minute to have that so 00:47:22.000 --> 00:47:24.910 align:start position:0% going to have a minute to have that so please<00:47:22.720> because<00:47:23.000> we<00:47:23.160> ran<00:47:23.520> out<00:47:23.720> of<00:47:24.040> microphones 00:47:24.910 --> 00:47:24.920 align:start position:0% please because we ran out of microphones 00:47:24.920 --> 00:47:27.829 align:start position:0% please because we ran out of microphones so<00:47:25.400> we<00:47:25.599> need<00:47:25.839> to<00:47:26.040> do<00:47:26.240> it<00:47:26.599> from<00:47:26.920> from<00:47:27.240> here<00:47:27.640> so 00:47:27.829 --> 00:47:27.839 align:start position:0% so we need to do it from from here so 00:47:27.839 --> 00:47:36.630 align:start position:0% so we need to do it from from here so please<00:47:28.160> please<00:47:28.440> go 00:47:36.630 --> 00:47:36.640 align:start position:0% 00:47:36.640 --> 00:47:39.309 align:start position:0% ahead<00:47:37.640> we<00:47:37.880> have<00:47:38.280> plenty<00:47:38.599> of<00:47:38.800> time<00:47:39.040> for 00:47:39.309 --> 00:47:39.319 align:start position:0% ahead we have plenty of time for 00:47:39.319 --> 00:47:42.230 align:start position:0% ahead we have plenty of time for questions<00:47:40.000> so<00:47:40.319> please<00:47:41.000> go<00:47:41.240> ahead<00:47:41.520> with<00:47:41.680> a<00:47:41.839> QR 00:47:42.230 --> 00:47:42.240 align:start position:0% questions so please go ahead with a QR 00:47:42.240 --> 00:48:01.430 align:start position:0% questions so please go ahead with a QR code 00:48:01.430 --> 00:48:01.440 align:start position:0% 00:48:01.440 --> 00:48:04.069 align:start position:0% it's<00:48:01.599> see<00:48:02.000> awkward<00:48:02.440> silence<00:48:03.400> uh<00:48:03.640> no<00:48:03.839> I<00:48:03.920> think 00:48:04.069 --> 00:48:04.079 align:start position:0% it's see awkward silence uh no I think 00:48:04.079 --> 00:48:06.030 align:start position:0% it's see awkward silence uh no I think there<00:48:04.200> are<00:48:04.400> no<00:48:04.640> questions<00:48:05.520> people<00:48:05.800> have 00:48:06.030 --> 00:48:06.040 align:start position:0% there are no questions people have 00:48:06.040 --> 00:48:08.109 align:start position:0% there are no questions people have already<00:48:06.359> left<00:48:06.640> and<00:48:06.800> theidea<00:48:07.440> next<00:48:07.680> ones<00:48:07.920> are 00:48:08.109 --> 00:48:08.119 align:start position:0% already left and theidea next ones are 00:48:08.119 --> 00:48:10.230 align:start position:0% already left and theidea next ones are waiting<00:48:08.520> for<00:48:09.040> do<00:48:09.200> do<00:48:09.280> we<00:48:09.440> have<00:48:09.599> one<00:48:09.880> question 00:48:10.230 --> 00:48:10.240 align:start position:0% waiting for do do we have one question 00:48:10.240 --> 00:48:12.190 align:start position:0% waiting for do do we have one question is<00:48:10.359> it<00:48:10.760> yeah<00:48:10.880> there<00:48:11.000> is<00:48:11.119> a 00:48:12.190 --> 00:48:12.200 align:start position:0% is it yeah there is a 00:48:12.200 --> 00:48:14.750 align:start position:0% is it yeah there is a question<00:48:13.200> maybe<00:48:13.440> we<00:48:13.559> can<00:48:13.760> pass<00:48:14.079> microphone 00:48:14.750 --> 00:48:14.760 align:start position:0% question maybe we can pass microphone 00:48:14.760 --> 00:48:17.910 align:start position:0% question maybe we can pass microphone that's<00:48:15.040> more<00:48:15.480> user<00:48:16.240> friendly<00:48:17.240> it<00:48:17.440> has<00:48:17.599> to<00:48:17.720> be 00:48:17.910 --> 00:48:17.920 align:start position:0% that's more user friendly it has to be 00:48:17.920 --> 00:48:18.870 align:start position:0% that's more user friendly it has to be through 00:48:18.870 --> 00:48:18.880 align:start position:0% through 00:48:18.880 --> 00:48:22.309 align:start position:0% through technology<00:48:20.280> okay<00:48:21.280> maybe<00:48:21.599> we<00:48:21.720> have<00:48:21.839> to<00:48:22.000> go<00:48:22.119> to 00:48:22.309 --> 00:48:22.319 align:start position:0% technology okay maybe we have to go to 00:48:22.319 --> 00:48:24.030 align:start position:0% technology okay maybe we have to go to that<00:48:22.520> person<00:48:22.839> with 00:48:24.030 --> 00:48:24.040 align:start position:0% that person with 00:48:24.040 --> 00:48:26.829 align:start position:0% that person with mhone<00:48:25.040> you<00:48:25.160> can<00:48:25.359> come<00:48:25.599> ask<00:48:25.800> your<00:48:25.960> question<00:48:26.200> on 00:48:26.829 --> 00:48:26.839 align:start position:0% mhone you can come ask your question on 00:48:26.839 --> 00:48:34.790 align:start position:0% mhone you can come ask your question on on<00:48:27.160> stage<00:48:27.880> you<00:48:28.000> want<00:48:28.079> to<00:48:28.200> yell<00:48:28.400> out<00:48:28.599> your 00:48:34.790 --> 00:48:34.800 align:start position:0% 00:48:34.800 --> 00:48:37.710 align:start position:0% question<00:48:35.800> thanks 00:48:37.710 --> 00:48:37.720 align:start position:0% question thanks 00:48:37.720 --> 00:48:42.549 align:start position:0% question thanks for<00:48:38.720> okay<00:48:38.920> thank<00:48:39.119> you<00:48:39.680> so<00:48:40.640> um<00:48:41.640> I<00:48:41.760> want<00:48:41.960> to<00:48:42.200> ask 00:48:42.549 --> 00:48:42.559 align:start position:0% for okay thank you so um I want to ask 00:48:42.559 --> 00:48:47.030 align:start position:0% for okay thank you so um I want to ask about<00:48:43.559> that<00:48:44.359> uh<00:48:45.359> U<00:48:45.520> you<00:48:45.720> state<00:48:46.119> that<00:48:46.559> um 00:48:47.030 --> 00:48:47.040 align:start position:0% about that uh U you state that um 00:48:47.040 --> 00:48:52.390 align:start position:0% about that uh U you state that um sometime<00:48:47.920> we<00:48:48.280> uh<00:48:48.400> when<00:48:48.559> we<00:48:48.760> talk<00:48:49.079> to<00:48:50.160> user<00:48:51.400> um 00:48:52.390 --> 00:48:52.400 align:start position:0% sometime we uh when we talk to user um 00:48:52.400 --> 00:48:55.549 align:start position:0% sometime we uh when we talk to user um we<00:48:52.559> should<00:48:53.160> Define<00:48:54.160> the<00:48:54.400> thing<00:48:54.640> that<00:48:54.839> user 00:48:55.549 --> 00:48:55.559 align:start position:0% we should Define the thing that user 00:48:55.559 --> 00:48:59.230 align:start position:0% we should Define the thing that user does<00:48:55.839> not<00:48:56.280> know<00:48:56.520> what<00:48:56.839> he<00:48:57.040> really<00:48:57.440> want<00:48:58.119> for<00:48:58.680> so 00:48:59.230 --> 00:48:59.240 align:start position:0% does not know what he really want for so 00:48:59.240 --> 00:49:03.030 align:start position:0% does not know what he really want for so how<00:48:59.400> to<00:48:59.799> track<00:49:00.480> uh<00:49:00.640> the<00:49:00.799> thing<00:49:01.200> that<00:49:01.599> uh<00:49:02.559> uh<00:49:02.839> the 00:49:03.030 --> 00:49:03.040 align:start position:0% how to track uh the thing that uh uh the 00:49:03.040 --> 00:49:06.150 align:start position:0% how to track uh the thing that uh uh the user<00:49:03.880> does<00:49:04.160> not<00:49:04.760> really<00:49:05.079> know 00:49:06.150 --> 00:49:06.160 align:start position:0% user does not really know 00:49:06.160 --> 00:49:09.990 align:start position:0% user does not really know about<00:49:07.160> uh<00:49:07.280> when<00:49:07.520> you<00:49:08.000> develop<00:49:08.480> a<00:49:08.799> product<00:49:09.720> and 00:49:09.990 --> 00:49:10.000 align:start position:0% about uh when you develop a product and 00:49:10.000 --> 00:49:13.270 align:start position:0% about uh when you develop a product and uh<00:49:10.359> I<00:49:10.520> have<00:49:10.799> another<00:49:11.640> question<00:49:12.640> uh<00:49:12.920> that<00:49:13.160> is 00:49:13.270 --> 00:49:13.280 align:start position:0% uh I have another question uh that is 00:49:13.280 --> 00:49:16.190 align:start position:0% uh I have another question uh that is that<00:49:13.520> true<00:49:14.000> that<00:49:14.520> um<00:49:14.960> the<00:49:15.160> first<00:49:15.480> step<00:49:15.920> when 00:49:16.190 --> 00:49:16.200 align:start position:0% that true that um the first step when 00:49:16.200 --> 00:49:20.109 align:start position:0% that true that um the first step when you<00:49:16.599> uh<00:49:16.720> develop<00:49:17.160> your<00:49:17.440> product<00:49:17.920> is<00:49:18.160> to<00:49:18.799> uh<00:49:19.680> uh 00:49:20.109 --> 00:49:20.119 align:start position:0% you uh develop your product is to uh uh 00:49:20.119 --> 00:49:24.630 align:start position:0% you uh develop your product is to uh uh to<00:49:20.440> ask<00:49:20.839> your<00:49:21.599> customer<00:49:22.200> or<00:49:22.520> we<00:49:22.680> need<00:49:22.880> to<00:49:23.640> find 00:49:24.630 --> 00:49:24.640 align:start position:0% to ask your customer or we need to find 00:49:24.640 --> 00:49:29.230 align:start position:0% to ask your customer or we need to find uh<00:49:24.880> some<00:49:25.720> prior<00:49:26.799> step<00:49:27.280> for<00:49:28.000> maybe<00:49:28.520> for<00:49:28.720> example 00:49:29.230 --> 00:49:29.240 align:start position:0% uh some prior step for maybe for example 00:49:29.240 --> 00:49:32.670 align:start position:0% uh some prior step for maybe for example to<00:49:29.799> uh<00:49:30.480> uh<00:49:30.640> analyzing<00:49:31.440> the<00:49:31.599> market<00:49:32.359> or 00:49:32.670 --> 00:49:32.680 align:start position:0% to uh uh analyzing the market or 00:49:32.680 --> 00:49:35.109 align:start position:0% to uh uh analyzing the market or something<00:49:33.480> something<00:49:33.799> like<00:49:34.040> that<00:49:34.480> so<00:49:34.839> that's 00:49:35.109 --> 00:49:35.119 align:start position:0% something something like that so that's 00:49:35.119 --> 00:49:40.710 align:start position:0% something something like that so that's own<00:49:35.480> of<00:49:36.359> my<00:49:36.640> uh<00:49:36.760> two 00:49:40.710 --> 00:49:40.720 align:start position:0% 00:49:40.720 --> 00:49:42.829 align:start position:0% question<00:49:41.720> I<00:49:41.920> I<00:49:42.000> think<00:49:42.240> the<00:49:42.440> the<00:49:42.599> first 00:49:42.829 --> 00:49:42.839 align:start position:0% question I I think the the first 00:49:42.839 --> 00:49:44.630 align:start position:0% question I I think the the first question<00:49:43.200> summary<00:49:43.760> if<00:49:44.000> correct<00:49:44.280> me<00:49:44.359> if<00:49:44.480> I'm 00:49:44.630 --> 00:49:44.640 align:start position:0% question summary if correct me if I'm 00:49:44.640 --> 00:49:46.109 align:start position:0% question summary if correct me if I'm wrong<00:49:44.839> it's<00:49:45.040> more<00:49:45.240> about<00:49:45.520> like<00:49:45.680> how<00:49:45.799> do<00:49:45.920> we 00:49:46.109 --> 00:49:46.119 align:start position:0% wrong it's more about like how do we 00:49:46.119 --> 00:49:49.870 align:start position:0% wrong it's more about like how do we know<00:49:46.400> what<00:49:46.559> the<00:49:47.200> user<00:49:47.760> actually<00:49:48.760> know<00:49:49.280> uh<00:49:49.480> says 00:49:49.870 --> 00:49:49.880 align:start position:0% know what the user actually know uh says 00:49:49.880 --> 00:49:51.549 align:start position:0% know what the user actually know uh says what<00:49:50.040> they<00:49:50.160> want<00:49:50.440> versus<00:49:50.920> what<00:49:51.079> they<00:49:51.240> actually 00:49:51.549 --> 00:49:51.559 align:start position:0% what they want versus what they actually 00:49:51.559 --> 00:49:54.510 align:start position:0% what they want versus what they actually need<00:49:52.240> right<00:49:52.400> how<00:49:52.520> do<00:49:52.640> we<00:49:52.799> get<00:49:52.920> to<00:49:53.160> the<00:49:53.839> the<00:49:54.000> need 00:49:54.510 --> 00:49:54.520 align:start position:0% need right how do we get to the the need 00:49:54.520 --> 00:49:56.390 align:start position:0% need right how do we get to the the need verus<00:49:54.960> the<00:49:55.119> rather<00:49:55.400> than<00:49:55.799> what<00:49:56.160> they<00:49:56.280> are 00:49:56.390 --> 00:49:56.400 align:start position:0% verus the rather than what they are 00:49:56.400 --> 00:49:58.309 align:start position:0% verus the rather than what they are asking<00:49:56.680> asking<00:49:56.960> for<00:49:57.240> essentially<00:49:58.000> if<00:49:58.160> I'm 00:49:58.309 --> 00:49:58.319 align:start position:0% asking asking for essentially if I'm 00:49:58.319 --> 00:50:00.470 align:start position:0% asking asking for essentially if I'm corre<00:49:58.839> if<00:49:59.119> if<00:49:59.280> it's<00:49:59.559> yeah<00:50:00.000> yeah<00:50:00.200> the<00:50:00.359> the 00:50:00.470 --> 00:50:00.480 align:start position:0% corre if if it's yeah yeah the the 00:50:00.480 --> 00:50:02.230 align:start position:0% corre if if it's yeah yeah the the unhelpful<00:50:01.040> answer<00:50:01.280> is<00:50:01.400> it<00:50:01.559> depends<00:50:02.000> but<00:50:02.160> I 00:50:02.230 --> 00:50:02.240 align:start position:0% unhelpful answer is it depends but I 00:50:02.240 --> 00:50:03.630 align:start position:0% unhelpful answer is it depends but I think<00:50:02.440> if<00:50:02.640> if<00:50:02.760> you<00:50:02.920> have<00:50:03.040> to<00:50:03.160> pick<00:50:03.400> like<00:50:03.480> a 00:50:03.630 --> 00:50:03.640 align:start position:0% think if if you have to pick like a 00:50:03.640 --> 00:50:05.829 align:start position:0% think if if you have to pick like a particular<00:50:04.160> Playbook<00:50:05.160> um<00:50:05.400> you<00:50:05.480> know<00:50:05.640> start 00:50:05.829 --> 00:50:05.839 align:start position:0% particular Playbook um you know start 00:50:05.839 --> 00:50:07.510 align:start position:0% particular Playbook um you know start with<00:50:06.000> a<00:50:06.160> hypothesis<00:50:06.760> or<00:50:06.920> a<00:50:07.040> particular 00:50:07.510 --> 00:50:07.520 align:start position:0% with a hypothesis or a particular 00:50:07.520 --> 00:50:10.270 align:start position:0% with a hypothesis or a particular question<00:50:08.000> that<00:50:08.119> you<00:50:08.240> want<00:50:08.400> to<00:50:08.720> answer<00:50:09.720> um<00:50:10.040> dig 00:50:10.270 --> 00:50:10.280 align:start position:0% question that you want to answer um dig 00:50:10.280 --> 00:50:12.150 align:start position:0% question that you want to answer um dig into<00:50:10.640> the<00:50:10.799> quantitative<00:50:11.440> data<00:50:11.720> if<00:50:11.839> you<00:50:12.000> have 00:50:12.150 --> 00:50:12.160 align:start position:0% into the quantitative data if you have 00:50:12.160 --> 00:50:13.829 align:start position:0% into the quantitative data if you have it<00:50:12.440> and<00:50:12.720> even<00:50:12.920> if<00:50:13.040> you<00:50:13.119> haven't<00:50:13.359> started<00:50:13.640> a 00:50:13.829 --> 00:50:13.839 align:start position:0% it and even if you haven't started a 00:50:13.839 --> 00:50:15.589 align:start position:0% it and even if you haven't started a project<00:50:14.200> yet<00:50:14.440> you<00:50:14.559> know<00:50:14.680> it's<00:50:14.839> a<00:50:15.000> lot<00:50:15.119> of<00:50:15.359> data 00:50:15.589 --> 00:50:15.599 align:start position:0% project yet you know it's a lot of data 00:50:15.599 --> 00:50:17.390 align:start position:0% project yet you know it's a lot of data onchain<00:50:16.280> like<00:50:16.400> you<00:50:16.520> can<00:50:16.799> probably<00:50:17.119> go<00:50:17.280> out 00:50:17.390 --> 00:50:17.400 align:start position:0% onchain like you can probably go out 00:50:17.400 --> 00:50:20.829 align:start position:0% onchain like you can probably go out there<00:50:17.520> and<00:50:17.640> find<00:50:17.839> some<00:50:18.160> signal<00:50:19.160> um<00:50:20.040> and<00:50:20.240> then 00:50:20.829 --> 00:50:20.839 align:start position:0% there and find some signal um and then 00:50:20.839 --> 00:50:22.109 align:start position:0% there and find some signal um and then uh<00:50:20.960> try<00:50:21.119> to<00:50:21.480> understand<00:50:21.640> what's<00:50:21.799> happening 00:50:22.109 --> 00:50:22.119 align:start position:0% uh try to understand what's happening 00:50:22.119 --> 00:50:24.270 align:start position:0% uh try to understand what's happening and<00:50:22.200> then<00:50:22.359> follow<00:50:22.680> up<00:50:23.240> you<00:50:23.400> know<00:50:23.839> with<00:50:24.040> maybe 00:50:24.270 --> 00:50:24.280 align:start position:0% and then follow up you know with maybe 00:50:24.280 --> 00:50:26.150 align:start position:0% and then follow up you know with maybe build<00:50:24.520> something<00:50:24.799> and<00:50:24.920> get<00:50:25.079> some<00:50:25.240> feedback<00:50:26.040> or 00:50:26.150 --> 00:50:26.160 align:start position:0% build something and get some feedback or 00:50:26.160 --> 00:50:27.510 align:start position:0% build something and get some feedback or if<00:50:26.240> you<00:50:26.359> feel<00:50:26.520> like<00:50:26.760> you<00:50:26.880> really<00:50:27.000> need<00:50:27.160> to 00:50:27.510 --> 00:50:27.520 align:start position:0% if you feel like you really need to 00:50:27.520 --> 00:50:28.990 align:start position:0% if you feel like you really need to discover<00:50:27.920> you<00:50:28.000> know<00:50:28.160> you<00:50:28.280> can<00:50:28.520> go<00:50:28.760> you<00:50:28.839> can 00:50:28.990 --> 00:50:29.000 align:start position:0% discover you know you can go you can 00:50:29.000 --> 00:50:30.549 align:start position:0% discover you know you can go you can follow<00:50:29.240> up<00:50:29.400> and<00:50:29.520> go<00:50:29.680> talk<00:50:29.799> to<00:50:30.000> people<00:50:30.240> and<00:50:30.440> and 00:50:30.549 --> 00:50:30.559 align:start position:0% follow up and go talk to people and and 00:50:30.559 --> 00:50:32.109 align:start position:0% follow up and go talk to people and and try<00:50:30.720> to<00:50:30.839> follow<00:50:31.400> answer<00:50:31.680> that<00:50:31.839> question 00:50:32.109 --> 00:50:32.119 align:start position:0% try to follow answer that question 00:50:32.119 --> 00:50:34.870 align:start position:0% try to follow answer that question essentially<00:50:32.599> but<00:50:32.720> you<00:50:32.920> you<00:50:33.040> might<00:50:33.240> have<00:50:33.880> some 00:50:34.870 --> 00:50:34.880 align:start position:0% essentially but you you might have some 00:50:34.880 --> 00:50:38.069 align:start position:0% essentially but you you might have some um<00:50:35.480> no<00:50:35.680> that's<00:50:35.799> a<00:50:36.000> good<00:50:36.680> good<00:50:36.839> point<00:50:37.160> I<00:50:37.359> I<00:50:37.760> maybe 00:50:38.069 --> 00:50:38.079 align:start position:0% um no that's a good good point I I maybe 00:50:38.079 --> 00:50:39.829 align:start position:0% um no that's a good good point I I maybe just<00:50:38.240> adding<00:50:38.520> on<00:50:38.760> this<00:50:39.040> if<00:50:39.160> you<00:50:39.280> are<00:50:39.559> actually 00:50:39.829 --> 00:50:39.839 align:start position:0% just adding on this if you are actually 00:50:39.839 --> 00:50:42.190 align:start position:0% just adding on this if you are actually talking<00:50:40.160> to<00:50:40.319> a<00:50:40.440> user<00:50:41.319> if<00:50:41.480> they<00:50:41.599> are<00:50:41.799> making<00:50:42.079> a 00:50:42.190 --> 00:50:42.200 align:start position:0% talking to a user if they are making a 00:50:42.200 --> 00:50:44.030 align:start position:0% talking to a user if they are making a feature<00:50:42.680> request<00:50:43.319> then<00:50:43.480> that's<00:50:43.680> probably<00:50:43.920> a 00:50:44.030 --> 00:50:44.040 align:start position:0% feature request then that's probably a 00:50:44.040 --> 00:50:46.549 align:start position:0% feature request then that's probably a signal<00:50:44.440> that<00:50:44.599> that's<00:50:45.000> already<00:50:45.559> too<00:50:45.880> narrow 00:50:46.549 --> 00:50:46.559 align:start position:0% signal that that's already too narrow 00:50:46.559 --> 00:50:48.789 align:start position:0% signal that that's already too narrow and<00:50:46.760> too<00:50:47.040> precise<00:50:47.599> like<00:50:47.760> try<00:50:47.920> to<00:50:48.359> understand 00:50:48.789 --> 00:50:48.799 align:start position:0% and too precise like try to understand 00:50:48.799 --> 00:50:50.990 align:start position:0% and too precise like try to understand why<00:50:48.960> do<00:50:49.160> they<00:50:49.319> need<00:50:49.559> that<00:50:49.720> feature<00:50:50.720> and<00:50:50.839> then 00:50:50.990 --> 00:50:51.000 align:start position:0% why do they need that feature and then 00:50:51.000 --> 00:50:52.870 align:start position:0% why do they need that feature and then you<00:50:51.119> might<00:50:51.760> agree<00:50:52.119> that<00:50:52.280> that<00:50:52.400> feature<00:50:52.720> is 00:50:52.870 --> 00:50:52.880 align:start position:0% you might agree that that feature is 00:50:52.880 --> 00:50:54.549 align:start position:0% you might agree that that feature is indeed<00:50:53.319> what<00:50:53.520> responds<00:50:53.880> to<00:50:54.000> their<00:50:54.160> need<00:50:54.400> or 00:50:54.549 --> 00:50:54.559 align:start position:0% indeed what responds to their need or 00:50:54.559 --> 00:50:56.630 align:start position:0% indeed what responds to their need or you<00:50:54.720> might<00:50:55.160> disagree<00:50:55.599> and<00:50:55.760> think<00:50:56.000> that 00:50:56.630 --> 00:50:56.640 align:start position:0% you might disagree and think that 00:50:56.640 --> 00:50:58.910 align:start position:0% you might disagree and think that another<00:50:56.880> feature<00:50:57.240> or<00:50:57.440> a<00:50:57.799> different<00:50:58.799> the 00:50:58.910 --> 00:50:58.920 align:start position:0% another feature or a different the 00:50:58.920 --> 00:51:00.430 align:start position:0% another feature or a different the feature<00:50:59.200> built<00:50:59.480> in<00:50:59.599> a<00:50:59.720> slightly<00:51:00.119> different 00:51:00.430 --> 00:51:00.440 align:start position:0% feature built in a slightly different 00:51:00.440 --> 00:51:02.309 align:start position:0% feature built in a slightly different way<00:51:00.680> might<00:51:00.880> respond<00:51:01.200> to<00:51:01.319> their<00:51:01.440> need 00:51:02.309 --> 00:51:02.319 align:start position:0% way might respond to their need 00:51:02.319 --> 00:51:06.309 align:start position:0% way might respond to their need better<00:51:03.760> yeah<00:51:04.760> yeah<00:51:04.880> maybe<00:51:05.119> to<00:51:05.319> make<00:51:05.480> it<00:51:05.640> more 00:51:06.309 --> 00:51:06.319 align:start position:0% better yeah yeah maybe to make it more 00:51:06.319 --> 00:51:10.950 align:start position:0% better yeah yeah maybe to make it more um<00:51:07.119> yeah<00:51:07.880> clear<00:51:08.680> with<00:51:08.799> a<00:51:09.079> specific<00:51:09.559> example<00:51:10.160> so 00:51:10.950 --> 00:51:10.960 align:start position:0% um yeah clear with a specific example so 00:51:10.960 --> 00:51:14.910 align:start position:0% um yeah clear with a specific example so um<00:51:11.520> this<00:51:12.240> multi-chain<00:51:13.240> um<00:51:13.920> feature<00:51:14.680> um 00:51:14.910 --> 00:51:14.920 align:start position:0% um this multi-chain um feature um 00:51:14.920 --> 00:51:17.150 align:start position:0% um this multi-chain um feature um multichain<00:51:15.559> trading<00:51:16.079> right<00:51:16.359> like<00:51:16.680> I<00:51:16.839> had<00:51:17.000> to 00:51:17.150 --> 00:51:17.160 align:start position:0% multichain trading right like I had to 00:51:17.160 --> 00:51:20.109 align:start position:0% multichain trading right like I had to write<00:51:17.400> for<00:51:17.640> every<00:51:17.920> step<00:51:18.280> of<00:51:18.520> my<00:51:19.119> trade<00:51:19.760> it<00:51:19.880> was 00:51:20.109 --> 00:51:20.119 align:start position:0% write for every step of my trade it was 00:51:20.119 --> 00:51:22.430 align:start position:0% write for every step of my trade it was just<00:51:20.640> actually<00:51:21.040> just<00:51:21.280> wanted<00:51:21.640> to<00:51:22.000> leave<00:51:22.240> a 00:51:22.430 --> 00:51:22.440 align:start position:0% just actually just wanted to leave a 00:51:22.440 --> 00:51:25.349 align:start position:0% just actually just wanted to leave a position<00:51:22.839> it<00:51:23.000> was<00:51:23.200> Stables<00:51:23.760> versus<00:51:24.359> like<00:51:24.760> a 00:51:25.349 --> 00:51:25.359 align:start position:0% position it was Stables versus like a 00:51:25.359 --> 00:51:28.230 align:start position:0% position it was Stables versus like a certain<00:51:25.760> token<00:51:26.680> and<00:51:26.799> for<00:51:27.079> every<00:51:27.640> little<00:51:27.960> step 00:51:28.230 --> 00:51:28.240 align:start position:0% certain token and for every little step 00:51:28.240 --> 00:51:30.150 align:start position:0% certain token and for every little step of<00:51:28.400> onchain<00:51:28.839> interaction<00:51:29.400> I<00:51:29.559> had<00:51:29.680> to<00:51:29.799> write<00:51:30.000> a 00:51:30.150 --> 00:51:30.160 align:start position:0% of onchain interaction I had to write a 00:51:30.160 --> 00:51:32.910 align:start position:0% of onchain interaction I had to write a support<00:51:30.599> request<00:51:31.160> but<00:51:31.319> my<00:51:31.559> actual<00:51:32.040> go<00:51:32.559> goal 00:51:32.910 --> 00:51:32.920 align:start position:0% support request but my actual go goal 00:51:32.920 --> 00:51:36.309 align:start position:0% support request but my actual go goal was<00:51:33.200> to<00:51:33.520> just<00:51:33.960> like<00:51:34.280> Swap<00:51:35.119> usdc<00:51:35.760> and<00:51:35.920> a<00:51:36.040> token 00:51:36.309 --> 00:51:36.319 align:start position:0% was to just like Swap usdc and a token 00:51:36.319 --> 00:51:38.349 align:start position:0% was to just like Swap usdc and a token from<00:51:36.480> a<00:51:36.599> different<00:51:36.880> chain<00:51:37.599> and<00:51:37.720> it<00:51:37.960> had<00:51:38.160> like 00:51:38.349 --> 00:51:38.359 align:start position:0% from a different chain and it had like 00:51:38.359 --> 00:51:40.430 align:start position:0% from a different chain and it had like 10<00:51:38.599> steps<00:51:39.040> involved<00:51:39.839> that<00:51:40.040> I<00:51:40.119> couldn't 00:51:40.430 --> 00:51:40.440 align:start position:0% 10 steps involved that I couldn't 00:51:40.440 --> 00:51:42.630 align:start position:0% 10 steps involved that I couldn't navigate<00:51:40.920> through<00:51:41.319> because<00:51:41.599> there<00:51:41.720> was<00:51:41.880> no 00:51:42.630 --> 00:51:42.640 align:start position:0% navigate through because there was no 00:51:42.640 --> 00:51:45.630 align:start position:0% navigate through because there was no help<00:51:42.960> text<00:51:43.280> also<00:51:43.760> on<00:51:44.200> on<00:51:44.400> that 00:51:45.630 --> 00:51:45.640 align:start position:0% help text also on on that 00:51:45.640 --> 00:51:48.069 align:start position:0% help text also on on that website<00:51:46.640> yeah<00:51:46.760> I<00:51:46.880> think<00:51:47.000> it's<00:51:47.160> just<00:51:47.680> nailing 00:51:48.069 --> 00:51:48.079 align:start position:0% website yeah I think it's just nailing 00:51:48.079 --> 00:51:50.630 align:start position:0% website yeah I think it's just nailing down<00:51:48.240> on<00:51:48.440> that<00:51:48.599> is<00:51:49.040> uh<00:51:49.280> getting<00:51:49.520> to<00:51:49.680> the<00:51:50.240> root 00:51:50.630 --> 00:51:50.640 align:start position:0% down on that is uh getting to the root 00:51:50.640 --> 00:51:52.670 align:start position:0% down on that is uh getting to the root cause<00:51:50.880> and<00:51:51.079> not<00:51:51.280> focusing<00:51:51.720> on<00:51:51.839> the<00:51:52.000> symptom<00:51:52.480> is 00:51:52.670 --> 00:51:52.680 align:start position:0% cause and not focusing on the symptom is 00:51:52.680 --> 00:51:55.270 align:start position:0% cause and not focusing on the symptom is like<00:51:53.079> why<00:51:53.240> are<00:51:53.480> they<00:51:53.640> trying<00:51:53.920> to<00:51:54.040> do<00:51:54.280> something 00:51:55.270 --> 00:51:55.280 align:start position:0% like why are they trying to do something 00:51:55.280 --> 00:51:57.390 align:start position:0% like why are they trying to do something and<00:51:55.799> uh<00:51:56.119> you<00:51:56.240> know<00:51:56.599> really<00:51:56.720> drill<00:51:57.040> them<00:51:57.160> to<00:51:57.280> the 00:51:57.390 --> 00:51:57.400 align:start position:0% and uh you know really drill them to the 00:51:57.400 --> 00:51:59.349 align:start position:0% and uh you know really drill them to the point<00:51:57.680> that<00:51:57.880> they<00:51:58.040> actually<00:51:58.400> disclose<00:51:58.960> the 00:51:59.349 --> 00:51:59.359 align:start position:0% point that they actually disclose the 00:51:59.359 --> 00:52:01.270 align:start position:0% point that they actually disclose the problem<00:51:59.720> they're<00:51:59.880> trying<00:52:00.079> to<00:52:00.200> solve<00:52:00.559> not<00:52:01.160> the 00:52:01.270 --> 00:52:01.280 align:start position:0% problem they're trying to solve not the 00:52:01.280 --> 00:52:04.710 align:start position:0% problem they're trying to solve not the feature<00:52:01.680> that<00:52:01.799> they're<00:52:02.000> trying<00:52:02.280> to<00:52:02.599> use 00:52:04.710 --> 00:52:04.720 align:start position:0% feature that they're trying to use 00:52:04.720 --> 00:52:07.270 align:start position:0% feature that they're trying to use essentially<00:52:05.720> uh<00:52:05.839> I<00:52:05.920> didn't<00:52:06.480> quite<00:52:06.799> catch<00:52:07.000> your 00:52:07.270 --> 00:52:07.280 align:start position:0% essentially uh I didn't quite catch your 00:52:07.280 --> 00:52:09.589 align:start position:0% essentially uh I didn't quite catch your second<00:52:07.599> question<00:52:07.960> but<00:52:08.160> perhaps<00:52:08.480> we<00:52:08.599> can<00:52:09.079> uh 00:52:09.589 --> 00:52:09.599 align:start position:0% second question but perhaps we can uh 00:52:09.599 --> 00:52:13.670 align:start position:0% second question but perhaps we can uh catch<00:52:10.240> uh<00:52:10.720> after<00:52:11.319> and<00:52:11.720> maybe<00:52:12.000> discuss<00:52:12.720> that 00:52:13.670 --> 00:52:13.680 align:start position:0% catch uh after and maybe discuss that 00:52:13.680 --> 00:52:17.030 align:start position:0% catch uh after and maybe discuss that all<00:52:13.839> right<00:52:14.680> there's<00:52:14.880> one<00:52:15.040> for<00:52:15.240> you<00:52:15.880> Austin<00:52:16.880> we 00:52:17.030 --> 00:52:17.040 align:start position:0% all right there's one for you Austin we 00:52:17.040 --> 00:52:19.309 align:start position:0% all right there's one for you Austin we have<00:52:17.400> we<00:52:17.520> have<00:52:17.640> one<00:52:17.920> question<00:52:18.920> we<00:52:19.040> have 00:52:19.309 --> 00:52:19.319 align:start position:0% have we have one question we have 00:52:19.319 --> 00:52:21.589 align:start position:0% have we have one question we have someone<00:52:19.680> with<00:52:19.799> the<00:52:20.000> microphone<00:52:20.760> wait<00:52:21.160> waiting 00:52:21.589 --> 00:52:21.599 align:start position:0% someone with the microphone wait waiting 00:52:21.599 --> 00:52:23.670 align:start position:0% someone with the microphone wait waiting and<00:52:21.839> after<00:52:22.240> your<00:52:22.559> question<00:52:22.960> we'll<00:52:23.280> go<00:52:23.520> with 00:52:23.670 --> 00:52:23.680 align:start position:0% and after your question we'll go with 00:52:23.680 --> 00:52:26.829 align:start position:0% and after your question we'll go with the<00:52:23.880> questions<00:52:24.319> here<00:52:24.680> in<00:52:24.839> the<00:52:25.280> screen<00:52:26.280> uh<00:52:26.599> well 00:52:26.829 --> 00:52:26.839 align:start position:0% the questions here in the screen uh well 00:52:26.839 --> 00:52:29.430 align:start position:0% the questions here in the screen uh well actually<00:52:27.400> my<00:52:27.880> uh<00:52:28.200> it's<00:52:28.559> not<00:52:28.799> that<00:52:28.920> I<00:52:29.079> had<00:52:29.200> a 00:52:29.430 --> 00:52:29.440 align:start position:0% actually my uh it's not that I had a 00:52:29.440 --> 00:52:32.470 align:start position:0% actually my uh it's not that I had a question<00:52:29.839> and<00:52:30.520> I<00:52:30.760> lost<00:52:31.160> the<00:52:31.319> momentum<00:52:32.000> but<00:52:32.359> I 00:52:32.470 --> 00:52:32.480 align:start position:0% question and I lost the momentum but I 00:52:32.480 --> 00:52:35.870 align:start position:0% question and I lost the momentum but I had<00:52:32.599> a<00:52:32.760> comment<00:52:33.680> about<00:52:34.000> the<00:52:34.200> pause<00:52:35.200> uh<00:52:35.359> between 00:52:35.870 --> 00:52:35.880 align:start position:0% had a comment about the pause uh between 00:52:35.880 --> 00:52:38.589 align:start position:0% had a comment about the pause uh between you<00:52:36.160> asking<00:52:36.440> us<00:52:36.599> for<00:52:36.760> a<00:52:36.920> question<00:52:37.319> and<00:52:37.799> silence 00:52:38.589 --> 00:52:38.599 align:start position:0% you asking us for a question and silence 00:52:38.599 --> 00:52:42.190 align:start position:0% you asking us for a question and silence so<00:52:38.920> I<00:52:39.079> scann<00:52:39.520> this<00:52:39.720> code<00:52:40.720> it<00:52:40.920> asked<00:52:41.240> me<00:52:41.400> to<00:52:42.079> uh 00:52:42.190 --> 00:52:42.200 align:start position:0% so I scann this code it asked me to uh 00:52:42.200 --> 00:52:44.510 align:start position:0% so I scann this code it asked me to uh enter<00:52:42.640> some<00:52:42.880> wallet<00:52:43.240> I<00:52:43.359> click<00:52:43.680> the<00:52:43.839> button<00:52:44.200> it 00:52:44.510 --> 00:52:44.520 align:start position:0% enter some wallet I click the button it 00:52:44.520 --> 00:52:46.109 align:start position:0% enter some wallet I click the button it asked<00:52:44.760> me<00:52:44.839> to<00:52:44.960> do<00:52:45.119> something<00:52:45.440> I'm<00:52:45.640> like<00:52:45.839> no<00:52:46.000> I'm 00:52:46.109 --> 00:52:46.119 align:start position:0% asked me to do something I'm like no I'm 00:52:46.119 --> 00:52:49.270 align:start position:0% asked me to do something I'm like no I'm not<00:52:46.319> that<00:52:46.440> interested<00:52:46.839> in<00:52:47.000> this<00:52:47.160> one<00:52:48.079> so<00:52:49.079> uh 00:52:49.270 --> 00:52:49.280 align:start position:0% not that interested in this one so uh 00:52:49.280 --> 00:52:52.750 align:start position:0% not that interested in this one so uh yeah<00:52:49.559> and<00:52:50.319> uh<00:52:50.640> actually<00:52:51.640> I<00:52:51.760> have<00:52:52.040> answer<00:52:52.559> to 00:52:52.750 --> 00:52:52.760 align:start position:0% yeah and uh actually I have answer to 00:52:52.760 --> 00:52:55.750 align:start position:0% yeah and uh actually I have answer to the<00:52:53.200> question<00:52:53.720> that<00:52:53.920> was<00:52:54.440> asked<00:52:54.960> because<00:52:55.440> I 00:52:55.750 --> 00:52:55.760 align:start position:0% the question that was asked because I 00:52:55.760 --> 00:52:58.069 align:start position:0% the question that was asked because I I'm<00:52:56.000> always<00:52:56.680> triggered<00:52:57.440> as<00:52:57.559> a<00:52:57.720> person 00:52:58.069 --> 00:52:58.079 align:start position:0% I'm always triggered as a person 00:52:58.079 --> 00:53:00.670 align:start position:0% I'm always triggered as a person responsible<00:52:58.559> for<00:52:58.720> a<00:52:58.920> product<00:52:59.880> I'm<00:53:00.160> always 00:53:00.670 --> 00:53:00.680 align:start position:0% responsible for a product I'm always 00:53:00.680 --> 00:53:04.030 align:start position:0% responsible for a product I'm always triggered<00:53:01.599> with<00:53:01.799> the<00:53:02.040> quote<00:53:02.520> from<00:53:03.000> Henry<00:53:03.359> Ford 00:53:04.030 --> 00:53:04.040 align:start position:0% triggered with the quote from Henry Ford 00:53:04.040 --> 00:53:07.870 align:start position:0% triggered with the quote from Henry Ford about<00:53:05.040> if<00:53:05.839> I<00:53:06.040> asked<00:53:06.520> people<00:53:07.400> uh<00:53:07.520> what<00:53:07.720> they 00:53:07.870 --> 00:53:07.880 align:start position:0% about if I asked people uh what they 00:53:07.880 --> 00:53:09.950 align:start position:0% about if I asked people uh what they need<00:53:08.200> they<00:53:08.319> will<00:53:08.640> tell<00:53:08.880> me<00:53:09.440> uh<00:53:09.559> they<00:53:09.680> need<00:53:09.839> a 00:53:09.950 --> 00:53:09.960 align:start position:0% need they will tell me uh they need a 00:53:09.960 --> 00:53:12.750 align:start position:0% need they will tell me uh they need a faster<00:53:10.480> horse<00:53:11.480> uh<00:53:11.640> the<00:53:11.839> answer<00:53:12.119> to<00:53:12.319> this<00:53:12.559> one 00:53:12.750 --> 00:53:12.760 align:start position:0% faster horse uh the answer to this one 00:53:12.760 --> 00:53:15.309 align:start position:0% faster horse uh the answer to this one is<00:53:12.960> simple<00:53:13.319> you<00:53:13.440> do<00:53:13.599> not<00:53:13.960> ask<00:53:14.520> people<00:53:15.079> what 00:53:15.309 --> 00:53:15.319 align:start position:0% is simple you do not ask people what 00:53:15.319 --> 00:53:18.750 align:start position:0% is simple you do not ask people what they<00:53:15.599> want<00:53:16.599> you<00:53:16.880> ask<00:53:17.240> people<00:53:17.839> what<00:53:18.280> problems 00:53:18.750 --> 00:53:18.760 align:start position:0% they want you ask people what problems 00:53:18.760 --> 00:53:21.470 align:start position:0% they want you ask people what problems they<00:53:19.000> have<00:53:19.400> what<00:53:19.760> what<00:53:19.960> they<00:53:20.200> do<00:53:20.520> on<00:53:20.960> daily 00:53:21.470 --> 00:53:21.480 align:start position:0% they have what what they do on daily 00:53:21.480 --> 00:53:24.390 align:start position:0% they have what what they do on daily basis<00:53:22.480> and<00:53:22.640> then<00:53:22.799> it's<00:53:23.000> your<00:53:23.280> job<00:53:23.839> to<00:53:24.040> figure 00:53:24.390 --> 00:53:24.400 align:start position:0% basis and then it's your job to figure 00:53:24.400 --> 00:53:28.510 align:start position:0% basis and then it's your job to figure out<00:53:25.040> the<00:53:25.280> way<00:53:25.760> to<00:53:26.520> for<00:53:26.960> them<00:53:27.960> uh<00:53:28.079> to<00:53:28.240> solve 00:53:28.510 --> 00:53:28.520 align:start position:0% out the way to for them uh to solve 00:53:28.520 --> 00:53:30.510 align:start position:0% out the way to for them uh to solve their<00:53:28.760> problems<00:53:29.119> and<00:53:29.280> then<00:53:29.400> you<00:53:29.760> present<00:53:30.160> some 00:53:30.510 --> 00:53:30.520 align:start position:0% their problems and then you present some 00:53:30.520 --> 00:53:33.230 align:start position:0% their problems and then you present some prototype<00:53:31.040> to<00:53:31.200> them<00:53:31.440> if<00:53:31.599> it<00:53:31.880> sticks<00:53:32.880> you<00:53:33.040> did 00:53:33.230 --> 00:53:33.240 align:start position:0% prototype to them if it sticks you did 00:53:33.240 --> 00:53:37.430 align:start position:0% prototype to them if it sticks you did your<00:53:33.400> job<00:53:33.680> well<00:53:33.960> so<00:53:34.880> yeah<00:53:35.599> thank<00:53:36.119> you<00:53:37.119> okay 00:53:37.430 --> 00:53:37.440 align:start position:0% your job well so yeah thank you okay 00:53:37.440 --> 00:53:38.230 align:start position:0% your job well so yeah thank you okay thank 00:53:38.230 --> 00:53:38.240 align:start position:0% thank 00:53:38.240 --> 00:53:42.750 align:start position:0% thank you<00:53:39.240> thank<00:53:39.680> you<00:53:40.680> thank 00:53:42.750 --> 00:53:42.760 align:start position:0% you thank you thank 00:53:42.760 --> 00:53:45.870 align:start position:0% you thank you thank you<00:53:43.760> so<00:53:43.960> we<00:53:44.079> have<00:53:44.359> three<00:53:44.640> questions<00:53:45.119> here<00:53:45.440> so 00:53:45.870 --> 00:53:45.880 align:start position:0% you so we have three questions here so 00:53:45.880 --> 00:53:48.789 align:start position:0% you so we have three questions here so to<00:53:46.160> what<00:53:46.480> extent<00:53:46.960> will<00:53:47.359> AI<00:53:47.839> impact<00:53:48.280> the<00:53:48.440> role 00:53:48.789 --> 00:53:48.799 align:start position:0% to what extent will AI impact the role 00:53:48.799 --> 00:53:50.430 align:start position:0% to what extent will AI impact the role of<00:53:49.000> designers<00:53:49.599> in<00:53:49.760> the 00:53:50.430 --> 00:53:50.440 align:start position:0% of designers in the 00:53:50.440 --> 00:53:54.630 align:start position:0% of designers in the future<00:53:51.440> oh<00:53:51.680> Hot<00:53:52.119> Topic<00:53:53.319> um<00:53:54.319> I<00:53:54.400> mean<00:53:54.520> I'm 00:53:54.630 --> 00:53:54.640 align:start position:0% future oh Hot Topic um I mean I'm 00:53:54.640 --> 00:53:56.109 align:start position:0% future oh Hot Topic um I mean I'm personally<00:53:55.000> excited<00:53:55.359> about<00:53:55.520> it<00:53:55.720> I<00:53:55.760> mean<00:53:55.920> we're 00:53:56.109 --> 00:53:56.119 align:start position:0% personally excited about it I mean we're 00:53:56.119 --> 00:53:58.109 align:start position:0% personally excited about it I mean we're we're<00:53:56.240> on<00:53:56.440> on<00:53:56.559> this<00:53:56.760> ride<00:53:57.440> uh<00:53:57.599> so<00:53:57.880> like<00:53:58.000> you 00:53:58.109 --> 00:53:58.119 align:start position:0% we're on on this ride uh so like you 00:53:58.119 --> 00:54:00.470 align:start position:0% we're on on this ride uh so like you might<00:53:58.280> as<00:53:58.400> well<00:53:58.559> enjoy<00:53:58.839> the<00:53:59.000> ride 00:54:00.470 --> 00:54:00.480 align:start position:0% might as well enjoy the ride 00:54:00.480 --> 00:54:04.630 align:start position:0% might as well enjoy the ride um<00:54:01.480> and<00:54:01.880> you<00:54:02.000> know<00:54:02.200> anecdotally<00:54:02.880> i'<00:54:03.119> I've<00:54:03.640> um 00:54:04.630 --> 00:54:04.640 align:start position:0% um and you know anecdotally i' I've um 00:54:04.640 --> 00:54:07.750 align:start position:0% um and you know anecdotally i' I've um I've<00:54:05.400> seen<00:54:05.720> it<00:54:05.920> be<00:54:06.160> really<00:54:06.400> powerful<00:54:07.119> like 00:54:07.750 --> 00:54:07.760 align:start position:0% I've seen it be really powerful like 00:54:07.760 --> 00:54:09.670 align:start position:0% I've seen it be really powerful like there's<00:54:07.920> a<00:54:08.079> ton<00:54:08.280> of<00:54:08.440> things<00:54:08.799> that<00:54:09.160> we're<00:54:09.400> doing 00:54:09.670 --> 00:54:09.680 align:start position:0% there's a ton of things that we're doing 00:54:09.680 --> 00:54:13.549 align:start position:0% there's a ton of things that we're doing as<00:54:09.880> designers<00:54:10.480> which<00:54:10.599> is<00:54:10.880> really<00:54:11.760> um<00:54:12.559> tedious 00:54:13.549 --> 00:54:13.559 align:start position:0% as designers which is really um tedious 00:54:13.559 --> 00:54:16.670 align:start position:0% as designers which is really um tedious and<00:54:13.960> and<00:54:14.559> you<00:54:14.680> know<00:54:15.000> Annoying<00:54:16.000> um<00:54:16.319> and<00:54:16.480> and<00:54:16.599> I 00:54:16.670 --> 00:54:16.680 align:start position:0% and and you know Annoying um and and I 00:54:16.680 --> 00:54:20.390 align:start position:0% and and you know Annoying um and and I think<00:54:16.799> in<00:54:16.920> the<00:54:17.040> short<00:54:17.280> term<00:54:18.079> um<00:54:18.720> you<00:54:18.839> know<00:54:19.400> like 00:54:20.390 --> 00:54:20.400 align:start position:0% think in the short term um you know like 00:54:20.400 --> 00:54:22.589 align:start position:0% think in the short term um you know like if<00:54:20.559> it's<00:54:20.760> integrated<00:54:21.240> into<00:54:21.559> workflows 00:54:22.589 --> 00:54:22.599 align:start position:0% if it's integrated into workflows 00:54:22.599 --> 00:54:25.630 align:start position:0% if it's integrated into workflows intelligently<00:54:23.599> um<00:54:24.079> I<00:54:24.200> haven't<00:54:24.480> seen<00:54:24.839> this<00:54:25.359> in 00:54:25.630 --> 00:54:25.640 align:start position:0% intelligently um I haven't seen this in 00:54:25.640 --> 00:54:27.150 align:start position:0% intelligently um I haven't seen this in design<00:54:26.119> yet 00:54:27.150 --> 00:54:27.160 align:start position:0% design yet 00:54:27.160 --> 00:54:29.109 align:start position:0% design yet uh<00:54:27.799> very<00:54:28.040> effectively<00:54:28.520> you<00:54:28.640> know<00:54:28.760> figma 00:54:29.109 --> 00:54:29.119 align:start position:0% uh very effectively you know figma 00:54:29.119 --> 00:54:32.109 align:start position:0% uh very effectively you know figma launched<00:54:29.440> a<00:54:29.599> bunch<00:54:29.799> of<00:54:30.240> AI<00:54:30.559> features<00:54:31.119> recently 00:54:32.109 --> 00:54:32.119 align:start position:0% launched a bunch of AI features recently 00:54:32.119 --> 00:54:34.030 align:start position:0% launched a bunch of AI features recently and<00:54:32.280> it<00:54:32.480> hasn't<00:54:33.000> really<00:54:33.240> been<00:54:33.440> sticky<00:54:33.799> in<00:54:33.920> my 00:54:34.030 --> 00:54:34.040 align:start position:0% and it hasn't really been sticky in my 00:54:34.040 --> 00:54:35.910 align:start position:0% and it hasn't really been sticky in my workflow<00:54:34.599> like<00:54:34.799> maybe<00:54:35.040> I<00:54:35.160> need<00:54:35.319> to<00:54:35.520> be<00:54:35.680> more 00:54:35.910 --> 00:54:35.920 align:start position:0% workflow like maybe I need to be more 00:54:35.920 --> 00:54:37.630 align:start position:0% workflow like maybe I need to be more aggressive<00:54:36.359> about<00:54:36.799> you<00:54:36.920> know<00:54:37.040> changing<00:54:37.440> my 00:54:37.630 --> 00:54:37.640 align:start position:0% aggressive about you know changing my 00:54:37.640 --> 00:54:39.430 align:start position:0% aggressive about you know changing my habits<00:54:38.240> just<00:54:38.400> like<00:54:38.559> learning<00:54:38.839> shortcuts<00:54:39.319> you 00:54:39.430 --> 00:54:39.440 align:start position:0% habits just like learning shortcuts you 00:54:39.440 --> 00:54:41.109 align:start position:0% habits just like learning shortcuts you kind<00:54:39.520> of<00:54:39.640> have<00:54:39.720> to<00:54:39.799> brute<00:54:40.160> force<00:54:40.799> your<00:54:40.960> way 00:54:41.109 --> 00:54:41.119 align:start position:0% kind of have to brute force your way 00:54:41.119 --> 00:54:42.510 align:start position:0% kind of have to brute force your way into<00:54:41.359> like<00:54:41.480> new<00:54:41.640> habits<00:54:41.960> when<00:54:42.079> it<00:54:42.160> comes<00:54:42.359> to 00:54:42.510 --> 00:54:42.520 align:start position:0% into like new habits when it comes to 00:54:42.520 --> 00:54:45.390 align:start position:0% into like new habits when it comes to something<00:54:42.760> you<00:54:42.880> do<00:54:43.160> you<00:54:43.280> know<00:54:43.799> 10<00:54:44.040> hours<00:54:44.280> a<00:54:44.440> day 00:54:45.390 --> 00:54:45.400 align:start position:0% something you do you know 10 hours a day 00:54:45.400 --> 00:54:46.990 align:start position:0% something you do you know 10 hours a day um<00:54:45.799> but<00:54:46.000> yeah<00:54:46.119> so<00:54:46.319> far<00:54:46.520> it's<00:54:46.760> it's<00:54:46.839> a 00:54:46.990 --> 00:54:47.000 align:start position:0% um but yeah so far it's it's a 00:54:47.000 --> 00:54:50.230 align:start position:0% um but yeah so far it's it's a playground<00:54:47.880> uh<00:54:48.240> I<00:54:48.319> see<00:54:48.559> it<00:54:48.680> as<00:54:48.799> an<00:54:49.240> opportunity 00:54:50.230 --> 00:54:50.240 align:start position:0% playground uh I see it as an opportunity 00:54:50.240 --> 00:54:52.710 align:start position:0% playground uh I see it as an opportunity um<00:54:50.760> I<00:54:51.000> haven't<00:54:51.799> aside<00:54:52.119> from<00:54:52.359> you<00:54:52.440> know<00:54:52.599> the 00:54:52.710 --> 00:54:52.720 align:start position:0% um I haven't aside from you know the 00:54:52.720 --> 00:54:54.390 align:start position:0% um I haven't aside from you know the classic<00:54:53.040> just<00:54:53.240> chat<00:54:53.640> chat<00:54:53.839> GPD<00:54:54.240> a 00:54:54.390 --> 00:54:54.400 align:start position:0% classic just chat chat GPD a 00:54:54.400 --> 00:54:55.950 align:start position:0% classic just chat chat GPD a conversation<00:54:54.880> partner<00:54:55.200> to<00:54:55.440> to<00:54:55.599> explore 00:54:55.950 --> 00:54:55.960 align:start position:0% conversation partner to to explore 00:54:55.960 --> 00:54:58.630 align:start position:0% conversation partner to to explore topics<00:54:56.440> and<00:54:56.960> ideas<00:54:57.880> um<00:54:58.079> actually<00:54:58.280> that's<00:54:58.480> been 00:54:58.630 --> 00:54:58.640 align:start position:0% topics and ideas um actually that's been 00:54:58.640 --> 00:55:00.710 align:start position:0% topics and ideas um actually that's been really<00:54:58.839> powerful<00:54:59.400> just<00:54:59.520> to<00:54:59.720> be<00:54:59.960> like<00:55:00.440> hey<00:55:00.640> I 00:55:00.710 --> 00:55:00.720 align:start position:0% really powerful just to be like hey I 00:55:00.720 --> 00:55:02.549 align:start position:0% really powerful just to be like hey I need<00:55:00.880> an<00:55:01.079> icon<00:55:01.440> for<00:55:01.680> this<00:55:01.920> like<00:55:02.079> give<00:55:02.160> me<00:55:02.319> 10 00:55:02.549 --> 00:55:02.559 align:start position:0% need an icon for this like give me 10 00:55:02.559 --> 00:55:05.309 align:start position:0% need an icon for this like give me 10 ideas<00:55:03.559> you<00:55:03.680> know<00:55:04.000> like<00:55:04.520> because<00:55:05.000> a<00:55:05.079> lot<00:55:05.200> of 00:55:05.309 --> 00:55:05.319 align:start position:0% ideas you know like because a lot of 00:55:05.319 --> 00:55:06.710 align:start position:0% ideas you know like because a lot of times<00:55:05.480> you<00:55:05.599> have<00:55:05.680> to<00:55:05.839> create<00:55:06.119> choices<00:55:06.559> before 00:55:06.710 --> 00:55:06.720 align:start position:0% times you have to create choices before 00:55:06.720 --> 00:55:08.630 align:start position:0% times you have to create choices before you<00:55:06.880> make<00:55:07.079> choices<00:55:07.480> as<00:55:07.559> a<00:55:07.760> designer<00:55:08.280> but 00:55:08.630 --> 00:55:08.640 align:start position:0% you make choices as a designer but 00:55:08.640 --> 00:55:10.309 align:start position:0% you make choices as a designer but unfortunately<00:55:09.480> often<00:55:09.760> it's<00:55:09.960> just<00:55:10.160> you 00:55:10.309 --> 00:55:10.319 align:start position:0% unfortunately often it's just you 00:55:10.319 --> 00:55:12.910 align:start position:0% unfortunately often it's just you staring<00:55:10.680> at<00:55:10.799> your<00:55:11.040> screen<00:55:12.040> um<00:55:12.200> and<00:55:12.359> so<00:55:12.520> to<00:55:12.680> have 00:55:12.910 --> 00:55:12.920 align:start position:0% staring at your screen um and so to have 00:55:12.920 --> 00:55:14.549 align:start position:0% staring at your screen um and so to have like<00:55:13.079> that<00:55:13.240> brainstorming<00:55:13.799> partner<00:55:14.200> at<00:55:14.319> least 00:55:14.549 --> 00:55:14.559 align:start position:0% like that brainstorming partner at least 00:55:14.559 --> 00:55:15.670 align:start position:0% like that brainstorming partner at least at<00:55:14.680> the<00:55:14.799> moment<00:55:15.119> I<00:55:15.200> mean<00:55:15.319> that's<00:55:15.480> been<00:55:15.599> the 00:55:15.670 --> 00:55:15.680 align:start position:0% at the moment I mean that's been the 00:55:15.680 --> 00:55:17.150 align:start position:0% at the moment I mean that's been the main<00:55:15.880> way<00:55:16.000> it's<00:55:16.160> affecting<00:55:16.480> my<00:55:16.559> workflow<00:55:17.000> for 00:55:17.150 --> 00:55:17.160 align:start position:0% main way it's affecting my workflow for 00:55:17.160 --> 00:55:20.390 align:start position:0% main way it's affecting my workflow for now<00:55:18.160> um<00:55:18.599> in<00:55:18.720> a<00:55:18.920> positive<00:55:19.280> way<00:55:19.720> and<00:55:20.040> yeah<00:55:20.200> I'd 00:55:20.390 --> 00:55:20.400 align:start position:0% now um in a positive way and yeah I'd 00:55:20.400 --> 00:55:22.470 align:start position:0% now um in a positive way and yeah I'd say<00:55:20.720> like<00:55:20.920> it's<00:55:21.119> happening<00:55:21.920> we're<00:55:22.160> long<00:55:22.319> for 00:55:22.470 --> 00:55:22.480 align:start position:0% say like it's happening we're long for 00:55:22.480 --> 00:55:25.430 align:start position:0% say like it's happening we're long for the<00:55:22.599> ride<00:55:22.960> I<00:55:23.160> I'm<00:55:23.559> I'm<00:55:23.880> generally<00:55:24.880> optimistic 00:55:25.430 --> 00:55:25.440 align:start position:0% the ride I I'm I'm generally optimistic 00:55:25.440 --> 00:55:28.950 align:start position:0% the ride I I'm I'm generally optimistic about<00:55:25.640> it 00:55:28.950 --> 00:55:28.960 align:start position:0% 00:55:28.960 --> 00:55:31.309 align:start position:0% awesome<00:55:29.720> we<00:55:29.960> have<00:55:30.240> time<00:55:30.440> for<00:55:30.799> one<00:55:31.000> more 00:55:31.309 --> 00:55:31.319 align:start position:0% awesome we have time for one more 00:55:31.319 --> 00:55:33.630 align:start position:0% awesome we have time for one more question<00:55:31.760> from<00:55:32.440> what<00:55:32.559> is<00:55:32.720> written<00:55:33.119> here<00:55:33.480> I'm 00:55:33.630 --> 00:55:33.640 align:start position:0% question from what is written here I'm 00:55:33.640 --> 00:55:35.990 align:start position:0% question from what is written here I'm trying<00:55:33.920> to<00:55:34.280> choose<00:55:34.599> the<00:55:34.839> right<00:55:35.079> one<00:55:35.680> and<00:55:35.839> we 00:55:35.990 --> 00:55:36.000 align:start position:0% trying to choose the right one and we 00:55:36.000 --> 00:55:38.589 align:start position:0% trying to choose the right one and we have<00:55:36.160> one<00:55:36.359> more 00:55:38.589 --> 00:55:38.599 align:start position:0% have one more 00:55:38.599 --> 00:55:42.309 align:start position:0% have one more here<00:55:39.599> okay<00:55:39.960> sorry<00:55:40.520> uh<00:55:41.039> I<00:55:41.119> was<00:55:41.440> trying<00:55:41.720> to<00:55:41.880> put<00:55:42.079> a 00:55:42.309 --> 00:55:42.319 align:start position:0% here okay sorry uh I was trying to put a 00:55:42.319 --> 00:55:44.630 align:start position:0% here okay sorry uh I was trying to put a new<00:55:42.559> line<00:55:42.799> and<00:55:43.000> it<00:55:43.200> actually<00:55:43.520> posted<00:55:44.039> the 00:55:44.630 --> 00:55:44.640 align:start position:0% new line and it actually posted the 00:55:44.640 --> 00:55:47.670 align:start position:0% new line and it actually posted the question<00:55:45.640> uh<00:55:46.359> uh<00:55:46.640> my<00:55:46.839> question<00:55:47.160> is<00:55:47.359> like<00:55:47.559> when 00:55:47.670 --> 00:55:47.680 align:start position:0% question uh uh my question is like when 00:55:47.680 --> 00:55:50.069 align:start position:0% question uh uh my question is like when you<00:55:47.799> are<00:55:47.960> trying<00:55:48.200> to<00:55:48.440> develop<00:55:48.880> a<00:55:49.400> B2B 00:55:50.069 --> 00:55:50.079 align:start position:0% you are trying to develop a B2B 00:55:50.079 --> 00:55:52.670 align:start position:0% you are trying to develop a B2B application<00:55:50.680> and<00:55:50.920> other<00:55:51.480> uh<00:55:51.880> uh<00:55:52.039> the<00:55:52.160> party 00:55:52.670 --> 00:55:52.680 align:start position:0% application and other uh uh the party 00:55:52.680 --> 00:55:55.470 align:start position:0% application and other uh uh the party the<00:55:53.319> business<00:55:54.000> is<00:55:54.200> not<00:55:54.480> working<00:55:54.920> in<00:55:55.039> a<00:55:55.240> web 00:55:55.470 --> 00:55:55.480 align:start position:0% the business is not working in a web 00:55:55.480 --> 00:55:58.390 align:start position:0% the business is not working in a web three<00:55:55.799> space<00:55:56.480> uh<00:55:56.920> how<00:55:57.480> what<00:55:57.599> is<00:55:57.760> the<00:55:57.960> best<00:55:58.200> way 00:55:58.390 --> 00:55:58.400 align:start position:0% three space uh how what is the best way 00:55:58.400 --> 00:56:01.710 align:start position:0% three space uh how what is the best way to<00:55:58.599> onboard<00:55:59.160> such<00:55:59.720> uh<00:55:59.880> business<00:56:00.400> users<00:56:01.400> so 00:56:01.710 --> 00:56:01.720 align:start position:0% to onboard such uh business users so 00:56:01.720 --> 00:56:04.950 align:start position:0% to onboard such uh business users so maybe<00:56:01.960> I<00:56:02.079> can<00:56:02.240> give<00:56:02.480> an<00:56:02.760> example<00:56:03.359> where<00:56:03.960> um<00:56:04.799> the 00:56:04.950 --> 00:56:04.960 align:start position:0% maybe I can give an example where um the 00:56:04.960 --> 00:56:07.270 align:start position:0% maybe I can give an example where um the solution<00:56:05.440> would<00:56:05.720> basically<00:56:06.200> combine<00:56:06.839> two 00:56:07.270 --> 00:56:07.280 align:start position:0% solution would basically combine two 00:56:07.280 --> 00:56:10.029 align:start position:0% solution would basically combine two different<00:56:07.920> chains<00:56:08.799> um<00:56:09.000> so<00:56:09.440> for<00:56:09.640> example 00:56:10.029 --> 00:56:10.039 align:start position:0% different chains um so for example 00:56:10.039 --> 00:56:12.710 align:start position:0% different chains um so for example friend<00:56:10.240> of<00:56:10.400> mine<00:56:10.720> has<00:56:10.920> developed<00:56:11.599> um<00:56:11.880> AI 00:56:12.710 --> 00:56:12.720 align:start position:0% friend of mine has developed um AI 00:56:12.720 --> 00:56:17.029 align:start position:0% friend of mine has developed um AI agents<00:56:13.760> for<00:56:14.760> uh<00:56:15.119> web<00:56:15.319> to<00:56:15.640> users<00:56:16.200> or<00:56:16.640> you<00:56:16.760> know 00:56:17.029 --> 00:56:17.039 align:start position:0% agents for uh web to users or you know 00:56:17.039 --> 00:56:19.390 align:start position:0% agents for uh web to users or you know like<00:56:17.200> from<00:56:17.480> that<00:56:17.760> World<00:56:18.520> um<00:56:18.799> and<00:56:19.039> basically 00:56:19.390 --> 00:56:19.400 align:start position:0% like from that World um and basically 00:56:19.400 --> 00:56:22.630 align:start position:0% like from that World um and basically the<00:56:19.559> approach<00:56:19.920> was<00:56:20.280> to<00:56:20.720> combine<00:56:21.559> um<00:56:21.839> a<00:56:22.039> near 00:56:22.630 --> 00:56:22.640 align:start position:0% the approach was to combine um a near 00:56:22.640 --> 00:56:24.870 align:start position:0% the approach was to combine um a near based<00:56:23.160> approach<00:56:23.559> so<00:56:23.839> where<00:56:24.119> it's<00:56:24.440> basically 00:56:24.870 --> 00:56:24.880 align:start position:0% based approach so where it's basically 00:56:24.880 --> 00:56:27.029 align:start position:0% based approach so where it's basically abstracting<00:56:25.400> a<00:56:25.559> bit<00:56:25.760> Orit<00:56:26.000> more 00:56:27.029 --> 00:56:27.039 align:start position:0% abstracting a bit Orit more 00:56:27.039 --> 00:56:29.430 align:start position:0% abstracting a bit Orit more designed<00:56:27.480> for<00:56:27.760> web<00:56:28.000> 2<00:56:28.240> users<00:56:28.640> in<00:56:28.839> mind<00:56:29.280> and 00:56:29.430 --> 00:56:29.440 align:start position:0% designed for web 2 users in mind and 00:56:29.440 --> 00:56:31.950 align:start position:0% designed for web 2 users in mind and then<00:56:29.799> basically<00:56:30.319> there<00:56:30.480> was<00:56:30.839> like<00:56:31.240> a<00:56:31.480> bridge 00:56:31.950 --> 00:56:31.960 align:start position:0% then basically there was like a bridge 00:56:31.960 --> 00:56:34.190 align:start position:0% then basically there was like a bridge in<00:56:32.280> or<00:56:32.880> basically<00:56:33.359> interactions<00:56:33.960> with 00:56:34.190 --> 00:56:34.200 align:start position:0% in or basically interactions with 00:56:34.200 --> 00:56:37.710 align:start position:0% in or basically interactions with ethereum<00:56:34.760> or<00:56:35.000> evm<00:56:35.520> compatibility<00:56:36.520> so<00:56:37.480> um 00:56:37.710 --> 00:56:37.720 align:start position:0% ethereum or evm compatibility so um 00:56:37.720 --> 00:56:40.270 align:start position:0% ethereum or evm compatibility so um navigating<00:56:38.359> ethereum<00:56:39.079> was<00:56:39.400> actually<00:56:39.760> not<00:56:39.960> so 00:56:40.270 --> 00:56:40.280 align:start position:0% navigating ethereum was actually not so 00:56:40.280 --> 00:56:43.549 align:start position:0% navigating ethereum was actually not so relevant<00:56:41.240> everything<00:56:41.640> that<00:56:41.839> this<00:56:42.119> B2<00:56:42.520> be<00:56:43.280> web 00:56:43.549 --> 00:56:43.559 align:start position:0% relevant everything that this B2 be web 00:56:43.559 --> 00:56:47.349 align:start position:0% relevant everything that this B2 be web 2<00:56:43.880> user<00:56:44.480> was<00:56:45.200> um<00:56:45.799> experiences<00:56:46.680> was 00:56:47.349 --> 00:56:47.359 align:start position:0% 2 user was um experiences was 00:56:47.359 --> 00:56:49.670 align:start position:0% 2 user was um experiences was experiencing<00:56:48.039> was<00:56:48.920> pretty<00:56:49.160> much<00:56:49.400> like<00:56:49.559> the 00:56:49.670 --> 00:56:49.680 align:start position:0% experiencing was pretty much like the 00:56:49.680 --> 00:56:52.069 align:start position:0% experiencing was pretty much like the same<00:56:49.920> ux<00:56:50.400> as<00:56:50.520> you<00:56:50.680> would<00:56:50.880> have<00:56:51.039> in<00:56:51.160> the<00:56:51.319> web<00:56:51.480> 2 00:56:52.069 --> 00:56:52.079 align:start position:0% same ux as you would have in the web 2 00:56:52.079 --> 00:56:56.670 align:start position:0% same ux as you would have in the web 2 logic<00:56:53.079> so<00:56:53.440> there<00:56:53.559> are<00:56:54.160> many<00:56:54.799> solutions<00:56:55.400> to 00:56:56.670 --> 00:56:56.680 align:start position:0% logic so there are many solutions to 00:56:56.680 --> 00:56:58.510 align:start position:0% logic so there are many solutions to different 00:56:58.510 --> 00:56:58.520 align:start position:0% different 00:56:58.520 --> 00:57:00.750 align:start position:0% different problems<00:56:59.520> awesome<00:57:00.000> thank<00:57:00.160> you<00:57:00.280> so<00:57:00.480> much 00:57:00.750 --> 00:57:00.760 align:start position:0% problems awesome thank you so much 00:57:00.760 --> 00:57:02.990 align:start position:0% problems awesome thank you so much please<00:57:01.039> give<00:57:01.200> a<00:57:01.680> great<00:57:01.960> Applause<00:57:02.400> to<00:57:02.680> this 00:57:02.990 --> 00:57:03.000 align:start position:0% please give a great Applause to this 00:57:03.000 --> 00:57:04.829 align:start position:0% please give a great Applause to this panel 00:57:04.829 --> 00:57:04.839 align:start position:0% panel 00:57:04.839 --> 00:57:09.400 align:start position:0% panel today<00:57:05.839> appreciate<00:57:06.400> it