WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:13.150 align:start position:0% [Music] 00:00:13.150 --> 00:00:13.160 align:start position:0% 00:00:13.160 --> 00:00:17.070 align:start position:0% hello<00:00:13.879> everyone<00:00:14.879> thank<00:00:15.120> you<00:00:15.519> for<00:00:15.839> coming<00:00:16.440> to 00:00:17.070 --> 00:00:17.080 align:start position:0% hello everyone thank you for coming to 00:00:17.080 --> 00:00:21.109 align:start position:0% hello everyone thank you for coming to our<00:00:17.400> talk<00:00:17.840> on<00:00:18.680> how<00:00:18.920> crypto<00:00:19.359> goes<00:00:20.119> mainstream 00:00:21.109 --> 00:00:21.119 align:start position:0% our talk on how crypto goes mainstream 00:00:21.119 --> 00:00:23.790 align:start position:0% our talk on how crypto goes mainstream it's<00:00:21.439> a<00:00:21.680> topic<00:00:22.080> that's<00:00:22.480> very<00:00:23.000> near<00:00:23.279> and<00:00:23.480> dear 00:00:23.790 --> 00:00:23.800 align:start position:0% it's a topic that's very near and dear 00:00:23.800 --> 00:00:24.910 align:start position:0% it's a topic that's very near and dear to<00:00:24.080> our 00:00:24.910 --> 00:00:24.920 align:start position:0% to our 00:00:24.920 --> 00:00:30.029 align:start position:0% to our heart<00:00:25.920> I<00:00:26.039> work<00:00:26.480> at<00:00:27.199> privy<00:00:28.160> and<00:00:28.320> privy<00:00:29.039> is<00:00:29.519> an<00:00:29.720> e 00:00:30.029 --> 00:00:30.039 align:start position:0% heart I work at privy and privy is an e 00:00:30.039 --> 00:00:32.229 align:start position:0% heart I work at privy and privy is an e easy<00:00:30.359> and<00:00:30.599> Powerful<00:00:31.160> way<00:00:31.519> for<00:00:31.759> crypto 00:00:32.229 --> 00:00:32.239 align:start position:0% easy and Powerful way for crypto 00:00:32.239 --> 00:00:34.790 align:start position:0% easy and Powerful way for crypto products<00:00:32.599> to<00:00:32.719> onboard<00:00:33.160> their<00:00:33.600> users<00:00:34.600> and 00:00:34.790 --> 00:00:34.800 align:start position:0% products to onboard their users and 00:00:34.800 --> 00:00:37.590 align:start position:0% products to onboard their users and privy<00:00:35.280> Powers<00:00:36.040> many<00:00:36.399> of<00:00:36.559> the<00:00:36.719> most<00:00:37.040> popular 00:00:37.590 --> 00:00:37.600 align:start position:0% privy Powers many of the most popular 00:00:37.600 --> 00:00:41.190 align:start position:0% privy Powers many of the most popular crypto<00:00:38.200> apps<00:00:39.200> from<00:00:39.719> Trading<00:00:40.200> apps<00:00:40.680> like<00:00:40.840> hyper 00:00:41.190 --> 00:00:41.200 align:start position:0% crypto apps from Trading apps like hyper 00:00:41.200 --> 00:00:43.910 align:start position:0% crypto apps from Trading apps like hyper liquid<00:00:41.520> and<00:00:41.680> pump.<00:00:42.200> fun<00:00:43.160> to<00:00:43.399> restaurant 00:00:43.910 --> 00:00:43.920 align:start position:0% liquid and pump. fun to restaurant 00:00:43.920 --> 00:00:46.670 align:start position:0% liquid and pump. fun to restaurant loyalty<00:00:44.559> projects<00:00:45.039> like<00:00:45.480> Blackbird<00:00:46.480> to 00:00:46.670 --> 00:00:46.680 align:start position:0% loyalty projects like Blackbird to 00:00:46.680 --> 00:00:49.510 align:start position:0% loyalty projects like Blackbird to social<00:00:47.079> apps<00:00:47.399> like<00:00:47.559> Zora<00:00:48.079> and<00:00:48.360> friendtech<00:00:49.360> and 00:00:49.510 --> 00:00:49.520 align:start position:0% social apps like Zora and friendtech and 00:00:49.520 --> 00:00:52.950 align:start position:0% social apps like Zora and friendtech and so<00:00:50.280> from<00:00:50.640> supporting<00:00:51.239> many<00:00:51.760> of<00:00:52.399> the<00:00:52.640> most 00:00:52.950 --> 00:00:52.960 align:start position:0% so from supporting many of the most 00:00:52.960 --> 00:00:55.189 align:start position:0% so from supporting many of the most popular<00:00:53.359> consumer<00:00:53.760> teams<00:00:54.600> we've<00:00:54.800> gotten<00:00:55.000> a 00:00:55.189 --> 00:00:55.199 align:start position:0% popular consumer teams we've gotten a 00:00:55.199 --> 00:00:58.830 align:start position:0% popular consumer teams we've gotten a really<00:00:55.440> good<00:00:55.680> lens<00:00:56.320> into<00:00:57.160> what<00:00:57.440> makes<00:00:57.840> a<00:00:58.079> great 00:00:58.830 --> 00:00:58.840 align:start position:0% really good lens into what makes a great 00:00:58.840 --> 00:01:00.990 align:start position:0% really good lens into what makes a great consumer<00:00:59.480> crypto 00:01:00.990 --> 00:01:01.000 align:start position:0% consumer crypto 00:01:01.000 --> 00:01:04.750 align:start position:0% consumer crypto product<00:01:02.000> and<00:01:02.199> it's<00:01:02.440> really<00:01:02.760> exciting<00:01:03.680> at<00:01:04.400> this 00:01:04.750 --> 00:01:04.760 align:start position:0% product and it's really exciting at this 00:01:04.760 --> 00:01:07.390 align:start position:0% product and it's really exciting at this Devcon<00:01:05.760> to<00:01:05.960> hear<00:01:06.240> how<00:01:06.360> many<00:01:06.680> people<00:01:07.159> are 00:01:07.390 --> 00:01:07.400 align:start position:0% Devcon to hear how many people are 00:01:07.400 --> 00:01:11.030 align:start position:0% Devcon to hear how many people are talking<00:01:08.320> about<00:01:08.680> consumers<00:01:09.680> and<00:01:09.960> and<00:01:10.280> apps<00:01:10.759> and 00:01:11.030 --> 00:01:11.040 align:start position:0% talking about consumers and and apps and 00:01:11.040 --> 00:01:12.630 align:start position:0% talking about consumers and and apps and you<00:01:11.119> know<00:01:11.280> one<00:01:11.400> of<00:01:11.560> the<00:01:11.759> things<00:01:12.119> I've<00:01:12.240> seen<00:01:12.479> a 00:01:12.630 --> 00:01:12.640 align:start position:0% you know one of the things I've seen a 00:01:12.640 --> 00:01:15.350 align:start position:0% you know one of the things I've seen a lot<00:01:13.320> on<00:01:13.479> Twitter<00:01:13.799> is<00:01:13.960> people<00:01:14.240> saying<00:01:15.159> where 00:01:15.350 --> 00:01:15.360 align:start position:0% lot on Twitter is people saying where 00:01:15.360 --> 00:01:17.070 align:start position:0% lot on Twitter is people saying where are<00:01:15.600> the<00:01:15.799> apps<00:01:16.159> and<00:01:16.320> how<00:01:16.439> are<00:01:16.560> we<00:01:16.680> going<00:01:16.759> to<00:01:16.920> get 00:01:17.070 --> 00:01:17.080 align:start position:0% are the apps and how are we going to get 00:01:17.080 --> 00:01:19.830 align:start position:0% are the apps and how are we going to get more<00:01:17.400> users<00:01:17.759> on<00:01:18.280> chain<00:01:19.280> and<00:01:19.439> this<00:01:19.520> is<00:01:19.640> a 00:01:19.830 --> 00:01:19.840 align:start position:0% more users on chain and this is a 00:01:19.840 --> 00:01:22.390 align:start position:0% more users on chain and this is a problem<00:01:20.360> we<00:01:20.520> think<00:01:20.759> about<00:01:21.320> a 00:01:22.390 --> 00:01:22.400 align:start position:0% problem we think about a 00:01:22.400 --> 00:01:24.749 align:start position:0% problem we think about a ton<00:01:23.400> and<00:01:23.520> at 00:01:24.749 --> 00:01:24.759 align:start position:0% ton and at 00:01:24.759 --> 00:01:26.590 align:start position:0% ton and at privy 00:01:26.590 --> 00:01:26.600 align:start position:0% privy 00:01:26.600 --> 00:01:29.910 align:start position:0% privy we<00:01:27.600> we<00:01:28.040> um<00:01:28.759> actually<00:01:29.159> I'll<00:01:29.320> tell<00:01:29.439> you<00:01:29.640> a<00:01:29.720> little 00:01:29.910 --> 00:01:29.920 align:start position:0% we we um actually I'll tell you a little 00:01:29.920 --> 00:01:30.749 align:start position:0% we we um actually I'll tell you a little a little<00:01:30.040> bit<00:01:30.159> about<00:01:30.320> what<00:01:30.400> we're<00:01:30.520> going<00:01:30.640> to 00:01:30.749 --> 00:01:30.759 align:start position:0% a little bit about what we're going to 00:01:30.759 --> 00:01:31.950 align:start position:0% a little bit about what we're going to talk<00:01:30.920> about<00:01:31.159> first<00:01:31.400> and<00:01:31.479> then<00:01:31.560> we'll<00:01:31.720> dive 00:01:31.950 --> 00:01:31.960 align:start position:0% talk about first and then we'll dive 00:01:31.960 --> 00:01:34.149 align:start position:0% talk about first and then we'll dive into<00:01:32.159> it<00:01:32.560> so<00:01:32.680> we're<00:01:32.799> going<00:01:32.880> to<00:01:33.000> talk<00:01:33.200> about<00:01:34.000> the 00:01:34.149 --> 00:01:34.159 align:start position:0% into it so we're going to talk about the 00:01:34.159 --> 00:01:36.149 align:start position:0% into it so we're going to talk about the changes<00:01:34.520> in<00:01:34.640> our<00:01:34.840> market<00:01:35.240> like<00:01:35.479> why<00:01:35.840> as<00:01:35.960> an 00:01:36.149 --> 00:01:36.159 align:start position:0% changes in our market like why as an 00:01:36.159 --> 00:01:38.789 align:start position:0% changes in our market like why as an industry<00:01:36.640> we've<00:01:36.920> gone<00:01:37.360> from<00:01:38.119> you<00:01:38.240> know<00:01:38.439> not 00:01:38.789 --> 00:01:38.799 align:start position:0% industry we've gone from you know not 00:01:38.799 --> 00:01:41.870 align:start position:0% industry we've gone from you know not not<00:01:39.159> giving<00:01:39.560> much<00:01:40.200> airtime<00:01:40.799> to<00:01:41.079> Consumer<00:01:41.600> to 00:01:41.870 --> 00:01:41.880 align:start position:0% not giving much airtime to Consumer to 00:01:41.880 --> 00:01:44.109 align:start position:0% not giving much airtime to Consumer to it<00:01:42.079> being<00:01:42.399> something<00:01:42.799> that<00:01:43.320> everyone<00:01:43.759> is<00:01:43.960> is 00:01:44.109 --> 00:01:44.119 align:start position:0% it being something that everyone is is 00:01:44.119 --> 00:01:46.510 align:start position:0% it being something that everyone is is referencing<00:01:44.560> and<00:01:44.719> talking<00:01:45.360> about<00:01:46.360> we're 00:01:46.510 --> 00:01:46.520 align:start position:0% referencing and talking about we're 00:01:46.520 --> 00:01:47.830 align:start position:0% referencing and talking about we're going<00:01:46.600> to<00:01:46.719> talk<00:01:46.840> about<00:01:47.000> the<00:01:47.119> crossroads<00:01:47.680> we're 00:01:47.830 --> 00:01:47.840 align:start position:0% going to talk about the crossroads we're 00:01:47.840 --> 00:01:50.149 align:start position:0% going to talk about the crossroads we're in<00:01:48.399> and<00:01:48.799> why<00:01:48.920> we're<00:01:49.079> starting<00:01:49.399> to<00:01:49.560> see<00:01:50.000> a 00:01:50.149 --> 00:01:50.159 align:start position:0% in and why we're starting to see a 00:01:50.159 --> 00:01:52.749 align:start position:0% in and why we're starting to see a really<00:01:50.399> exciting<00:01:51.119> acceleration<00:01:52.119> in<00:01:52.600> the 00:01:52.749 --> 00:01:52.759 align:start position:0% really exciting acceleration in the 00:01:52.759 --> 00:01:55.109 align:start position:0% really exciting acceleration in the crypto<00:01:53.240> Market<00:01:54.240> we're<00:01:54.399> going<00:01:54.479> to<00:01:54.640> talk<00:01:54.840> about 00:01:55.109 --> 00:01:55.119 align:start position:0% crypto Market we're going to talk about 00:01:55.119 --> 00:01:57.709 align:start position:0% crypto Market we're going to talk about what<00:01:55.320> great<00:01:55.600> looks<00:01:55.880> like<00:01:56.039> in<00:01:56.439> consumer<00:01:57.439> so 00:01:57.709 --> 00:01:57.719 align:start position:0% what great looks like in consumer so 00:01:57.719 --> 00:01:59.230 align:start position:0% what great looks like in consumer so what<00:01:57.880> some<00:01:58.000> of<00:01:58.119> the<00:01:58.240> qualities<00:01:58.600> of<00:01:58.759> the<00:01:58.920> most 00:01:59.230 --> 00:01:59.240 align:start position:0% what some of the qualities of the most 00:01:59.240 --> 00:02:00.870 align:start position:0% what some of the qualities of the most popular<00:01:59.560> cons<00:01:59.880> consumer<00:02:00.200> apps<00:02:00.479> will<00:02:00.640> look 00:02:00.870 --> 00:02:00.880 align:start position:0% popular cons consumer apps will look 00:02:00.880 --> 00:02:02.350 align:start position:0% popular cons consumer apps will look like<00:02:01.439> we're<00:02:01.560> going<00:02:01.640> to<00:02:01.719> talk<00:02:01.880> about<00:02:02.079> where<00:02:02.200> we 00:02:02.350 --> 00:02:02.360 align:start position:0% like we're going to talk about where we 00:02:02.360 --> 00:02:04.830 align:start position:0% like we're going to talk about where we go<00:02:02.560> from<00:02:02.799> here<00:02:03.159> how<00:02:03.600> we're<00:02:03.799> going<00:02:03.880> to<00:02:04.079> get 00:02:04.830 --> 00:02:04.840 align:start position:0% go from here how we're going to get 00:02:04.840 --> 00:02:09.109 align:start position:0% go from here how we're going to get every<00:02:05.119> consumer<00:02:05.640> product<00:02:05.920> on<00:02:06.119> chain<00:02:06.640> over 00:02:09.109 --> 00:02:09.119 align:start position:0% 00:02:09.119 --> 00:02:12.309 align:start position:0% time<00:02:10.119> at<00:02:10.280> priview<00:02:10.720> we<00:02:10.959> we<00:02:11.120> we<00:02:11.239> talked<00:02:11.560> a<00:02:11.720> lot 00:02:12.309 --> 00:02:12.319 align:start position:0% time at priview we we we talked a lot 00:02:12.319 --> 00:02:15.949 align:start position:0% time at priview we we we talked a lot about<00:02:13.319> you<00:02:13.840> know<00:02:14.840> what<00:02:15.200> what<00:02:15.319> will<00:02:15.480> it<00:02:15.680> take 00:02:15.949 --> 00:02:15.959 align:start position:0% about you know what what will it take 00:02:15.959 --> 00:02:19.630 align:start position:0% about you know what what will it take for<00:02:16.120> a<00:02:16.239> consumer<00:02:16.720> product<00:02:17.080> to<00:02:17.560> break<00:02:18.160> out<00:02:19.160> and 00:02:19.630 --> 00:02:19.640 align:start position:0% for a consumer product to break out and 00:02:19.640 --> 00:02:22.790 align:start position:0% for a consumer product to break out and new<00:02:20.200> tech<00:02:21.200> often<00:02:21.640> needs<00:02:21.920> to<00:02:22.120> power 00:02:22.790 --> 00:02:22.800 align:start position:0% new tech often needs to power 00:02:22.800 --> 00:02:24.750 align:start position:0% new tech often needs to power experiences<00:02:23.480> that<00:02:23.599> are<00:02:23.760> orders<00:02:24.080> of<00:02:24.239> magnitude 00:02:24.750 --> 00:02:24.760 align:start position:0% experiences that are orders of magnitude 00:02:24.760 --> 00:02:26.949 align:start position:0% experiences that are orders of magnitude better<00:02:25.400> than<00:02:25.560> the<00:02:25.720> status<00:02:26.080> quo<00:02:26.480> and<00:02:26.599> so<00:02:26.720> to<00:02:26.840> use 00:02:26.949 --> 00:02:26.959 align:start position:0% better than the status quo and so to use 00:02:26.959 --> 00:02:28.470 align:start position:0% better than the status quo and so to use an<00:02:27.120> internet<00:02:27.480> analogy<00:02:28.040> like<00:02:28.160> if<00:02:28.239> you<00:02:28.319> were 00:02:28.470 --> 00:02:28.480 align:start position:0% an internet analogy like if you were 00:02:28.480 --> 00:02:30.470 align:start position:0% an internet analogy like if you were building<00:02:28.840> a<00:02:28.959> new<00:02:29.239> internet 00:02:30.470 --> 00:02:30.480 align:start position:0% building a new internet 00:02:30.480 --> 00:02:31.710 align:start position:0% building a new internet if<00:02:30.599> you<00:02:30.720> build<00:02:31.000> something<00:02:31.280> that's<00:02:31.480> better 00:02:31.710 --> 00:02:31.720 align:start position:0% if you build something that's better 00:02:31.720 --> 00:02:33.670 align:start position:0% if you build something that's better than<00:02:31.879> dialup<00:02:32.879> you<00:02:33.000> know<00:02:33.160> that's<00:02:33.319> not<00:02:33.480> going<00:02:33.560> to 00:02:33.670 --> 00:02:33.680 align:start position:0% than dialup you know that's not going to 00:02:33.680 --> 00:02:36.589 align:start position:0% than dialup you know that's not going to cut<00:02:33.840> it<00:02:34.040> because<00:02:34.200> now<00:02:34.360> we<00:02:34.560> have<00:02:35.360> fiber<00:02:36.360> and<00:02:36.440> so 00:02:36.589 --> 00:02:36.599 align:start position:0% cut it because now we have fiber and so 00:02:36.599 --> 00:02:38.550 align:start position:0% cut it because now we have fiber and so with<00:02:36.800> consumer<00:02:37.480> you<00:02:37.599> know<00:02:37.920> we<00:02:38.040> need<00:02:38.160> to<00:02:38.280> build 00:02:38.550 --> 00:02:38.560 align:start position:0% with consumer you know we need to build 00:02:38.560 --> 00:02:40.430 align:start position:0% with consumer you know we need to build something<00:02:39.239> that's<00:02:39.680> you<00:02:39.800> know<00:02:39.959> a<00:02:40.080> better 00:02:40.430 --> 00:02:40.440 align:start position:0% something that's you know a better 00:02:40.440 --> 00:02:41.869 align:start position:0% something that's you know a better experience<00:02:40.840> a<00:02:40.959> more<00:02:41.080> compelling<00:02:41.519> experience 00:02:41.869 --> 00:02:41.879 align:start position:0% experience a more compelling experience 00:02:41.879 --> 00:02:44.190 align:start position:0% experience a more compelling experience than<00:02:42.040> something<00:02:42.280> like<00:02:42.480> Uber<00:02:42.920> or<00:02:43.159> Facebook<00:02:44.000> or 00:02:44.190 --> 00:02:44.200 align:start position:0% than something like Uber or Facebook or 00:02:44.200 --> 00:02:46.110 align:start position:0% than something like Uber or Facebook or Tik<00:02:44.440> Tok<00:02:44.680> in<00:02:44.760> order<00:02:45.000> to<00:02:45.239> get<00:02:45.680> you<00:02:45.800> know 00:02:46.110 --> 00:02:46.120 align:start position:0% Tik Tok in order to get you know 00:02:46.120 --> 00:02:49.229 align:start position:0% Tik Tok in order to get you know everyone<00:02:46.519> to<00:02:46.720> start<00:02:46.959> using<00:02:47.720> it<00:02:48.720> and<00:02:48.840> to<00:02:49.000> us 00:02:49.229 --> 00:02:49.239 align:start position:0% everyone to start using it and to us 00:02:49.239 --> 00:02:51.030 align:start position:0% everyone to start using it and to us there<00:02:49.519> there<00:02:49.599> are<00:02:49.800> three<00:02:50.080> things<00:02:50.519> that<00:02:50.640> we<00:02:50.840> get 00:02:51.030 --> 00:02:51.040 align:start position:0% there there are three things that we get 00:02:51.040 --> 00:02:54.229 align:start position:0% there there are three things that we get from<00:02:51.239> building<00:02:51.599> on<00:02:51.840> crypto<00:02:52.200> rails<00:02:53.200> that<00:02:54.120> you 00:02:54.229 --> 00:02:54.239 align:start position:0% from building on crypto rails that you 00:02:54.239 --> 00:02:55.830 align:start position:0% from building on crypto rails that you know<00:02:54.400> aren't<00:02:54.879> possible<00:02:55.239> if<00:02:55.360> you're<00:02:55.519> building 00:02:55.830 --> 00:02:55.840 align:start position:0% know aren't possible if you're building 00:02:55.840 --> 00:02:58.550 align:start position:0% know aren't possible if you're building offchain<00:02:56.840> the<00:02:57.000> first<00:02:57.400> is<00:02:57.840> you<00:02:57.920> know<00:02:58.080> this<00:02:58.280> idea 00:02:58.550 --> 00:02:58.560 align:start position:0% offchain the first is you know this idea 00:02:58.560 --> 00:03:01.030 align:start position:0% offchain the first is you know this idea of<00:02:58.680> ownership<00:02:59.640> the<00:03:00.080> assets<00:03:00.519> that<00:03:00.640> you're 00:03:01.030 --> 00:03:01.040 align:start position:0% of ownership the assets that you're 00:03:01.040 --> 00:03:03.390 align:start position:0% of ownership the assets that you're accumulating<00:03:01.720> in<00:03:01.840> your<00:03:02.000> app<00:03:02.200> are<00:03:02.400> yours<00:03:02.959> you 00:03:03.390 --> 00:03:03.400 align:start position:0% accumulating in your app are yours you 00:03:03.400 --> 00:03:05.110 align:start position:0% accumulating in your app are yours you you<00:03:03.560> can<00:03:03.760> get<00:03:04.000> kind<00:03:04.120> of<00:03:04.239> shut<00:03:04.519> off<00:03:04.760> from<00:03:04.959> the 00:03:05.110 --> 00:03:05.120 align:start position:0% you can get kind of shut off from the 00:03:05.120 --> 00:03:07.270 align:start position:0% you can get kind of shut off from the app<00:03:05.440> but<00:03:05.560> you<00:03:05.799> still<00:03:06.280> have<00:03:06.560> the<00:03:06.760> assets<00:03:07.159> that 00:03:07.270 --> 00:03:07.280 align:start position:0% app but you still have the assets that 00:03:07.280 --> 00:03:08.670 align:start position:0% app but you still have the assets that you've<00:03:07.440> earned<00:03:07.760> and<00:03:07.879> you<00:03:07.959> can<00:03:08.120> take<00:03:08.319> them<00:03:08.519> with 00:03:08.670 --> 00:03:08.680 align:start position:0% you've earned and you can take them with 00:03:08.680 --> 00:03:10.949 align:start position:0% you've earned and you can take them with you<00:03:09.560> which<00:03:09.680> is<00:03:09.799> related<00:03:10.080> to<00:03:10.239> the<00:03:10.360> second<00:03:10.640> Point 00:03:10.949 --> 00:03:10.959 align:start position:0% you which is related to the second Point 00:03:10.959 --> 00:03:13.550 align:start position:0% you which is related to the second Point around<00:03:11.400> interoperability<00:03:12.400> by<00:03:12.560> building<00:03:12.920> on<00:03:13.040> a 00:03:13.550 --> 00:03:13.560 align:start position:0% around interoperability by building on a 00:03:13.560 --> 00:03:15.949 align:start position:0% around interoperability by building on a blockchain<00:03:14.560> you<00:03:14.720> can<00:03:15.000> take<00:03:15.239> your<00:03:15.480> assets 00:03:15.949 --> 00:03:15.959 align:start position:0% blockchain you can take your assets 00:03:15.959 --> 00:03:17.630 align:start position:0% blockchain you can take your assets experiences<00:03:16.560> with<00:03:16.680> you<00:03:16.840> from<00:03:17.000> app<00:03:17.200> to<00:03:17.360> app<00:03:17.560> so 00:03:17.630 --> 00:03:17.640 align:start position:0% experiences with you from app to app so 00:03:17.640 --> 00:03:19.869 align:start position:0% experiences with you from app to app so you<00:03:17.720> can<00:03:17.879> mint<00:03:18.159> an<00:03:18.319> nft<00:03:18.799> on<00:03:18.959> Zora<00:03:19.400> and<00:03:19.519> then<00:03:19.680> go 00:03:19.869 --> 00:03:19.879 align:start position:0% you can mint an nft on Zora and then go 00:03:19.879 --> 00:03:22.869 align:start position:0% you can mint an nft on Zora and then go sell<00:03:20.120> it<00:03:20.280> on<00:03:20.640> openc<00:03:21.640> or<00:03:21.840> any<00:03:22.040> other<00:03:22.200> nft 00:03:22.869 --> 00:03:22.879 align:start position:0% sell it on openc or any other nft 00:03:22.879 --> 00:03:24.789 align:start position:0% sell it on openc or any other nft Marketplace<00:03:23.879> and<00:03:24.000> the<00:03:24.080> third<00:03:24.319> is<00:03:24.440> around 00:03:24.789 --> 00:03:24.799 align:start position:0% Marketplace and the third is around 00:03:24.799 --> 00:03:28.670 align:start position:0% Marketplace and the third is around payments<00:03:25.720> so<00:03:26.720> crypto<00:03:27.200> offers<00:03:27.760> a<00:03:28.280> digital 00:03:28.670 --> 00:03:28.680 align:start position:0% payments so crypto offers a digital 00:03:28.680 --> 00:03:31.390 align:start position:0% payments so crypto offers a digital first<00:03:29.159> instant<00:03:29.799> payment<00:03:30.120> layer<00:03:30.599> which<00:03:30.720> is<00:03:31.159> a 00:03:31.390 --> 00:03:31.400 align:start position:0% first instant payment layer which is a 00:03:31.400 --> 00:03:34.070 align:start position:0% first instant payment layer which is a really<00:03:31.840> exciting<00:03:32.480> new<00:03:32.720> capability<00:03:33.400> that's 00:03:34.070 --> 00:03:34.080 align:start position:0% really exciting new capability that's 00:03:34.080 --> 00:03:35.390 align:start position:0% really exciting new capability that's not<00:03:34.360> possible 00:03:35.390 --> 00:03:35.400 align:start position:0% not possible 00:03:35.400 --> 00:03:37.550 align:start position:0% not possible offchain<00:03:36.400> historically 00:03:37.550 --> 00:03:37.560 align:start position:0% offchain historically 00:03:37.560 --> 00:03:40.869 align:start position:0% offchain historically getting<00:03:38.560> that<00:03:39.319> combination<00:03:39.879> of<00:03:40.120> attributes 00:03:40.869 --> 00:03:40.879 align:start position:0% getting that combination of attributes 00:03:40.879 --> 00:03:44.229 align:start position:0% getting that combination of attributes in<00:03:41.159> a<00:03:41.439> product<00:03:41.959> required<00:03:42.439> using<00:03:43.360> something 00:03:44.229 --> 00:03:44.239 align:start position:0% in a product required using something 00:03:44.239 --> 00:03:47.190 align:start position:0% in a product required using something like<00:03:44.760> this<00:03:45.000> metamask<00:03:45.920> it<00:03:46.080> accomplished<00:03:47.080> you 00:03:47.190 --> 00:03:47.200 align:start position:0% like this metamask it accomplished you 00:03:47.200 --> 00:03:49.309 align:start position:0% like this metamask it accomplished you know<00:03:47.519> everything<00:03:48.200> that<00:03:48.400> crypto<00:03:48.760> enables 00:03:49.309 --> 00:03:49.319 align:start position:0% know everything that crypto enables 00:03:49.319 --> 00:03:52.509 align:start position:0% know everything that crypto enables really<00:03:49.640> well<00:03:50.560> but<00:03:50.680> it<00:03:50.879> requires<00:03:51.360> you<00:03:51.599> to<00:03:52.079> to<00:03:52.239> be 00:03:52.509 --> 00:03:52.519 align:start position:0% really well but it requires you to to be 00:03:52.519 --> 00:03:56.030 align:start position:0% really well but it requires you to to be very<00:03:52.799> familiar<00:03:53.519> with<00:03:54.159> crypto<00:03:55.159> and<00:03:55.599> if<00:03:55.920> you 00:03:56.030 --> 00:03:56.040 align:start position:0% very familiar with crypto and if you 00:03:56.040 --> 00:03:57.869 align:start position:0% very familiar with crypto and if you know<00:03:56.200> you<00:03:56.280> don't<00:03:56.799> care<00:03:57.040> about<00:03:57.319> crypto<00:03:57.760> or 00:03:57.869 --> 00:03:57.879 align:start position:0% know you don't care about crypto or 00:03:57.879 --> 00:03:58.990 align:start position:0% know you don't care about crypto or you're<00:03:58.040> not<00:03:58.200> willing<00:03:58.439> to<00:03:58.560> go<00:03:58.720> through<00:03:58.879> the 00:03:58.990 --> 00:03:59.000 align:start position:0% you're not willing to go through the 00:03:59.000 --> 00:04:01.949 align:start position:0% you're not willing to go through the Hoops<00:03:59.319> to<00:03:59.959> set<00:04:00.239> up<00:04:00.879> you<00:04:01.040> know<00:04:01.280> your<00:04:01.480> crypto 00:04:01.949 --> 00:04:01.959 align:start position:0% Hoops to set up you know your crypto 00:04:01.959 --> 00:04:05.309 align:start position:0% Hoops to set up you know your crypto life<00:04:02.599> this<00:04:02.720> might<00:04:02.920> be<00:04:03.079> too<00:04:03.319> daunting<00:04:03.760> to<00:04:04.159> you 00:04:05.309 --> 00:04:05.319 align:start position:0% life this might be too daunting to you 00:04:05.319 --> 00:04:09.190 align:start position:0% life this might be too daunting to you and<00:04:06.319> it's<00:04:07.280> you<00:04:07.439> know<00:04:07.799> been<00:04:08.040> a<00:04:08.200> big<00:04:08.439> reason<00:04:09.000> why 00:04:09.190 --> 00:04:09.200 align:start position:0% and it's you know been a big reason why 00:04:09.200 --> 00:04:11.509 align:start position:0% and it's you know been a big reason why many<00:04:09.760> crypto<00:04:10.120> apps<00:04:10.400> haven't<00:04:11.159> you<00:04:11.280> know<00:04:11.400> been 00:04:11.509 --> 00:04:11.519 align:start position:0% many crypto apps haven't you know been 00:04:11.519 --> 00:04:13.190 align:start position:0% many crypto apps haven't you know been able<00:04:11.720> to<00:04:11.879> cater<00:04:12.159> to<00:04:12.319> people<00:04:12.519> who<00:04:12.680> don't<00:04:12.959> know 00:04:13.190 --> 00:04:13.200 align:start position:0% able to cater to people who don't know 00:04:13.200 --> 00:04:15.949 align:start position:0% able to cater to people who don't know much<00:04:13.400> about<00:04:13.640> crypto<00:04:14.319> and<00:04:14.439> a<00:04:14.560> lot<00:04:14.680> of<00:04:14.799> the<00:04:15.000> first 00:04:15.949 --> 00:04:15.959 align:start position:0% much about crypto and a lot of the first 00:04:15.959 --> 00:04:19.150 align:start position:0% much about crypto and a lot of the first popular<00:04:16.359> crypto<00:04:16.759> app<00:04:17.600> experiences<00:04:18.600> powered 00:04:19.150 --> 00:04:19.160 align:start position:0% popular crypto app experiences powered 00:04:19.160 --> 00:04:23.230 align:start position:0% popular crypto app experiences powered by<00:04:19.959> you<00:04:20.079> know<00:04:20.280> these<00:04:20.560> external<00:04:21.520> wallets<00:04:22.520> they 00:04:23.230 --> 00:04:23.240 align:start position:0% by you know these external wallets they 00:04:23.240 --> 00:04:27.030 align:start position:0% by you know these external wallets they looked<00:04:23.560> like<00:04:23.919> this<00:04:24.600> um<00:04:25.199> they<00:04:25.280> were<00:04:25.639> great<00:04:26.040> for 00:04:27.030 --> 00:04:27.040 align:start position:0% looked like this um they were great for 00:04:27.040 --> 00:04:28.150 align:start position:0% looked like this um they were great for discreet 00:04:28.150 --> 00:04:28.160 align:start position:0% discreet 00:04:28.160 --> 00:04:32.150 align:start position:0% discreet onetime<00:04:29.160> user<00:04:29.800> experiences<00:04:30.600> come<00:04:30.840> in<00:04:31.800> do<00:04:32.000> a 00:04:32.150 --> 00:04:32.160 align:start position:0% onetime user experiences come in do a 00:04:32.160 --> 00:04:34.950 align:start position:0% onetime user experiences come in do a financial<00:04:32.680> transaction<00:04:33.680> get<00:04:33.840> what<00:04:33.960> you<00:04:34.160> need 00:04:34.950 --> 00:04:34.960 align:start position:0% financial transaction get what you need 00:04:34.960 --> 00:04:36.550 align:start position:0% financial transaction get what you need leave<00:04:35.440> and<00:04:35.600> then<00:04:35.800> you<00:04:35.919> know<00:04:36.080> come<00:04:36.280> back<00:04:36.440> when 00:04:36.550 --> 00:04:36.560 align:start position:0% leave and then you know come back when 00:04:36.560 --> 00:04:38.749 align:start position:0% leave and then you know come back when you<00:04:36.639> need<00:04:36.800> to<00:04:36.919> do<00:04:37.240> your<00:04:37.400> next<00:04:37.880> financial 00:04:38.749 --> 00:04:38.759 align:start position:0% you need to do your next financial 00:04:38.759 --> 00:04:41.070 align:start position:0% you need to do your next financial transaction<00:04:39.759> but<00:04:39.880> they<00:04:40.000> weren't<00:04:41.000> they 00:04:41.070 --> 00:04:41.080 align:start position:0% transaction but they weren't they 00:04:41.080 --> 00:04:44.150 align:start position:0% transaction but they weren't they weren't<00:04:41.479> well<00:04:41.720> set<00:04:42.000> up<00:04:42.240> for<00:04:43.160> multi-session 00:04:44.150 --> 00:04:44.160 align:start position:0% weren't well set up for multi-session 00:04:44.160 --> 00:04:46.070 align:start position:0% weren't well set up for multi-session user 00:04:46.070 --> 00:04:46.080 align:start position:0% user 00:04:46.080 --> 00:04:49.950 align:start position:0% user Journeys<00:04:47.080> and<00:04:47.680> the<00:04:47.840> teex<00:04:48.199> stack<00:04:48.600> has<00:04:48.800> come<00:04:49.800> a 00:04:49.950 --> 00:04:49.960 align:start position:0% Journeys and the teex stack has come a 00:04:49.960 --> 00:04:52.830 align:start position:0% Journeys and the teex stack has come a very<00:04:50.240> long<00:04:50.520> way<00:04:50.759> to<00:04:51.000> enable<00:04:51.919> these<00:04:52.199> richer 00:04:52.830 --> 00:04:52.840 align:start position:0% very long way to enable these richer 00:04:52.840 --> 00:04:55.909 align:start position:0% very long way to enable these richer consumer<00:04:53.400> experiences<00:04:54.400> so<00:04:55.400> you<00:04:55.520> know<00:04:55.680> a<00:04:55.800> lot 00:04:55.909 --> 00:04:55.919 align:start position:0% consumer experiences so you know a lot 00:04:55.919 --> 00:04:57.990 align:start position:0% consumer experiences so you know a lot of<00:04:56.240> time<00:04:56.919> a<00:04:57.000> lot<00:04:57.120> of<00:04:57.240> the<00:04:57.360> time<00:04:57.520> we<00:04:57.639> talk<00:04:57.800> about 00:04:57.990 --> 00:04:58.000 align:start position:0% of time a lot of the time we talk about 00:04:58.000 --> 00:05:00.390 align:start position:0% of time a lot of the time we talk about like<00:04:58.160> what<00:04:58.240> are<00:04:58.360> the<00:04:58.479> barriers<00:04:59.000> to 00:05:00.390 --> 00:05:00.400 align:start position:0% like what are the barriers to 00:05:00.400 --> 00:05:02.150 align:start position:0% like what are the barriers to consumer<00:05:00.960> products<00:05:01.320> really<00:05:01.479> breaking<00:05:01.800> out<00:05:02.000> at 00:05:02.150 --> 00:05:02.160 align:start position:0% consumer products really breaking out at 00:05:02.160 --> 00:05:05.070 align:start position:0% consumer products really breaking out at C<00:05:02.600> you<00:05:02.680> know<00:05:02.960> on<00:05:03.160> on<00:05:03.360> crypto<00:05:03.680> rails<00:05:04.160> and 00:05:05.070 --> 00:05:05.080 align:start position:0% C you know on on crypto rails and 00:05:05.080 --> 00:05:07.909 align:start position:0% C you know on on crypto rails and there's<00:05:06.000> sort<00:05:06.240> of<00:05:06.440> like<00:05:06.560> a<00:05:06.639> lot<00:05:06.759> of<00:05:06.960> the<00:05:07.120> ux 00:05:07.909 --> 00:05:07.919 align:start position:0% there's sort of like a lot of the ux 00:05:07.919 --> 00:05:11.029 align:start position:0% there's sort of like a lot of the ux around<00:05:08.600> making<00:05:08.919> crypto<00:05:09.280> apps<00:05:09.560> easy<00:05:09.759> to<00:05:10.039> use 00:05:11.029 --> 00:05:11.039 align:start position:0% around making crypto apps easy to use 00:05:11.039 --> 00:05:13.830 align:start position:0% around making crypto apps easy to use there's<00:05:11.320> scalability<00:05:12.320> cheap<00:05:13.160> you<00:05:13.280> know<00:05:13.560> fast 00:05:13.830 --> 00:05:13.840 align:start position:0% there's scalability cheap you know fast 00:05:13.840 --> 00:05:15.110 align:start position:0% there's scalability cheap you know fast reliable 00:05:15.110 --> 00:05:15.120 align:start position:0% reliable 00:05:15.120 --> 00:05:17.550 align:start position:0% reliable blockchains<00:05:16.120> and<00:05:16.280> then<00:05:16.759> there<00:05:16.880> are<00:05:17.280> kind<00:05:17.400> of 00:05:17.550 --> 00:05:17.560 align:start position:0% blockchains and then there are kind of 00:05:17.560 --> 00:05:18.870 align:start position:0% blockchains and then there are kind of elements<00:05:17.919> around<00:05:18.160> the<00:05:18.319> transaction 00:05:18.870 --> 00:05:18.880 align:start position:0% elements around the transaction 00:05:18.880 --> 00:05:21.550 align:start position:0% elements around the transaction experience<00:05:19.319> and<00:05:19.520> making<00:05:19.880> that<00:05:20.479> easier<00:05:21.440> and 00:05:21.550 --> 00:05:21.560 align:start position:0% experience and making that easier and 00:05:21.560 --> 00:05:23.909 align:start position:0% experience and making that easier and for<00:05:21.720> the<00:05:21.840> first<00:05:22.080> time<00:05:22.319> we<00:05:22.600> have<00:05:22.919> a<00:05:23.080> Tex<00:05:23.440> stack 00:05:23.909 --> 00:05:23.919 align:start position:0% for the first time we have a Tex stack 00:05:23.919 --> 00:05:25.990 align:start position:0% for the first time we have a Tex stack that<00:05:24.479> kind<00:05:24.600> of<00:05:24.759> combining<00:05:25.479> all<00:05:25.600> of<00:05:25.759> these 00:05:25.990 --> 00:05:26.000 align:start position:0% that kind of combining all of these 00:05:26.000 --> 00:05:28.830 align:start position:0% that kind of combining all of these attributes<00:05:26.720> allows<00:05:27.080> us<00:05:27.280> to<00:05:27.560> build<00:05:28.560> great 00:05:28.830 --> 00:05:28.840 align:start position:0% attributes allows us to build great 00:05:28.840 --> 00:05:31.670 align:start position:0% attributes allows us to build great consumer 00:05:31.670 --> 00:05:31.680 align:start position:0% 00:05:31.680 --> 00:05:33.749 align:start position:0% experiences<00:05:32.680> and<00:05:32.960> as<00:05:33.039> a<00:05:33.199> result<00:05:33.440> we've<00:05:33.600> seen 00:05:33.749 --> 00:05:33.759 align:start position:0% experiences and as a result we've seen 00:05:33.759 --> 00:05:35.909 align:start position:0% experiences and as a result we've seen the<00:05:33.840> market<00:05:34.120> evolve<00:05:34.520> quite<00:05:34.680> a<00:05:34.840> bit<00:05:35.240> so<00:05:35.680> we've 00:05:35.909 --> 00:05:35.919 align:start position:0% the market evolve quite a bit so we've 00:05:35.919 --> 00:05:37.830 align:start position:0% the market evolve quite a bit so we've gone<00:05:36.360> from<00:05:37.120> you<00:05:37.240> know<00:05:37.400> here<00:05:37.560> we're 00:05:37.830 --> 00:05:37.840 align:start position:0% gone from you know here we're 00:05:37.840 --> 00:05:39.550 align:start position:0% gone from you know here we're highlighting<00:05:38.600> you<00:05:38.680> know<00:05:38.880> what<00:05:39.000> we<00:05:39.160> see<00:05:39.400> as 00:05:39.550 --> 00:05:39.560 align:start position:0% highlighting you know what we see as 00:05:39.560 --> 00:05:41.309 align:start position:0% highlighting you know what we see as like<00:05:39.759> kind<00:05:39.880> of<00:05:40.039> the<00:05:40.400> most<00:05:40.720> popular<00:05:41.120> most 00:05:41.309 --> 00:05:41.319 align:start position:0% like kind of the most popular most 00:05:41.319 --> 00:05:43.870 align:start position:0% like kind of the most popular most visible<00:05:41.840> consumer<00:05:42.400> products<00:05:43.039> consumer 00:05:43.870 --> 00:05:43.880 align:start position:0% visible consumer products consumer 00:05:43.880 --> 00:05:46.749 align:start position:0% visible consumer products consumer crypto<00:05:44.319> products<00:05:44.680> of<00:05:44.800> the<00:05:45.000> year<00:05:45.840> um<00:05:46.039> starting 00:05:46.749 --> 00:05:46.759 align:start position:0% crypto products of the year um starting 00:05:46.759 --> 00:05:50.510 align:start position:0% crypto products of the year um starting with<00:05:47.759> you<00:05:47.880> know<00:05:48.560> Financial<00:05:49.560> one-time<00:05:50.039> defi 00:05:50.510 --> 00:05:50.520 align:start position:0% with you know Financial one-time defi 00:05:50.520 --> 00:05:53.270 align:start position:0% with you know Financial one-time defi use<00:05:50.919> cases<00:05:51.319> to<00:05:51.600> much<00:05:52.199> kind<00:05:52.319> of<00:05:52.479> broader<00:05:52.840> defi 00:05:53.270 --> 00:05:53.280 align:start position:0% use cases to much kind of broader defi 00:05:53.280 --> 00:05:56.150 align:start position:0% use cases to much kind of broader defi use<00:05:53.560> cases<00:05:54.160> to<00:05:54.319> Bringing<00:05:55.080> art<00:05:55.319> and<00:05:55.520> culture<00:05:55.880> on 00:05:56.150 --> 00:05:56.160 align:start position:0% use cases to Bringing art and culture on 00:05:56.160 --> 00:05:59.909 align:start position:0% use cases to Bringing art and culture on chain<00:05:56.720> to<00:05:57.319> gaming<00:05:58.319> um<00:05:58.759> to<00:05:59.360> social<00:05:59.639> social 00:05:59.909 --> 00:05:59.919 align:start position:0% chain to gaming um to social social 00:05:59.919 --> 00:06:01.990 align:start position:0% chain to gaming um to social social interactions<00:06:00.560> and<00:06:00.720> now<00:06:00.919> having<00:06:01.560> a<00:06:01.720> full 00:06:01.990 --> 00:06:02.000 align:start position:0% interactions and now having a full 00:06:02.000 --> 00:06:03.230 align:start position:0% interactions and now having a full social 00:06:03.230 --> 00:06:03.240 align:start position:0% social 00:06:03.240 --> 00:06:06.469 align:start position:0% social layer<00:06:04.240> and<00:06:04.520> you<00:06:04.680> know<00:06:05.199> now<00:06:05.360> we're<00:06:05.560> starting<00:06:05.919> to 00:06:06.469 --> 00:06:06.479 align:start position:0% layer and you know now we're starting to 00:06:06.479 --> 00:06:11.110 align:start position:0% layer and you know now we're starting to see<00:06:07.479> these<00:06:08.440> more<00:06:09.319> kind<00:06:09.440> of<00:06:09.759> Rich<00:06:10.520> consumer 00:06:11.110 --> 00:06:11.120 align:start position:0% see these more kind of Rich consumer 00:06:11.120 --> 00:06:13.270 align:start position:0% see these more kind of Rich consumer product 00:06:13.270 --> 00:06:13.280 align:start position:0% product 00:06:13.280 --> 00:06:15.950 align:start position:0% product experiences<00:06:14.280> but<00:06:14.400> we're<00:06:14.560> at<00:06:14.720> a<00:06:14.880> crossroad<00:06:15.440> so 00:06:15.950 --> 00:06:15.960 align:start position:0% experiences but we're at a crossroad so 00:06:15.960 --> 00:06:18.029 align:start position:0% experiences but we're at a crossroad so we<00:06:16.199> have<00:06:16.720> kind<00:06:16.840> of<00:06:17.120> everything<00:06:17.440> we<00:06:17.560> need<00:06:17.840> to 00:06:18.029 --> 00:06:18.039 align:start position:0% we have kind of everything we need to 00:06:18.039 --> 00:06:22.110 align:start position:0% we have kind of everything we need to build<00:06:18.919> a<00:06:19.160> great<00:06:19.560> consumer<00:06:20.520> experience<00:06:21.520> um<00:06:21.960> but 00:06:22.110 --> 00:06:22.120 align:start position:0% build a great consumer experience um but 00:06:22.120 --> 00:06:23.990 align:start position:0% build a great consumer experience um but we're<00:06:22.280> not<00:06:22.440> at<00:06:22.599> the<00:06:22.759> point<00:06:23.039> where<00:06:23.599> every<00:06:23.840> app 00:06:23.990 --> 00:06:24.000 align:start position:0% we're not at the point where every app 00:06:24.000 --> 00:06:26.150 align:start position:0% we're not at the point where every app we're<00:06:24.160> using<00:06:24.479> is<00:06:24.599> on<00:06:24.759> crypto<00:06:25.120> rails<00:06:25.919> and<00:06:26.000> so 00:06:26.150 --> 00:06:26.160 align:start position:0% we're using is on crypto rails and so 00:06:26.160 --> 00:06:28.230 align:start position:0% we're using is on crypto rails and so the<00:06:26.319> question<00:06:26.919> we<00:06:27.199> ask<00:06:27.400> a<00:06:27.479> lot<00:06:27.639> at<00:06:27.759> privy<00:06:28.080> is 00:06:28.230 --> 00:06:28.240 align:start position:0% the question we ask a lot at privy is 00:06:28.240 --> 00:06:30.270 align:start position:0% the question we ask a lot at privy is What<00:06:28.400> will<00:06:28.680> what<00:06:28.800> will<00:06:28.919> it<00:06:29.080> take<00:06:29.280> for<00:06:29.720> that<00:06:29.880> to 00:06:30.270 --> 00:06:30.280 align:start position:0% What will what will it take for that to 00:06:30.280 --> 00:06:33.309 align:start position:0% What will what will it take for that to happen<00:06:31.280> and<00:06:31.400> we<00:06:31.520> see<00:06:31.759> two<00:06:32.039> trends<00:06:33.000> that<00:06:33.120> are 00:06:33.309 --> 00:06:33.319 align:start position:0% happen and we see two trends that are 00:06:33.319 --> 00:06:35.670 align:start position:0% happen and we see two trends that are both<00:06:33.919> very<00:06:34.319> exciting<00:06:35.199> that<00:06:35.319> are<00:06:35.479> both 00:06:35.670 --> 00:06:35.680 align:start position:0% both very exciting that are both 00:06:35.680 --> 00:06:38.150 align:start position:0% both very exciting that are both accelerating<00:06:36.240> a<00:06:36.360> ton<00:06:36.759> right<00:06:37.000> now<00:06:37.800> that<00:06:37.960> we 00:06:38.150 --> 00:06:38.160 align:start position:0% accelerating a ton right now that we 00:06:38.160 --> 00:06:39.189 align:start position:0% accelerating a ton right now that we think 00:06:39.189 --> 00:06:39.199 align:start position:0% think 00:06:39.199 --> 00:06:42.950 align:start position:0% think will<00:06:40.199> unlock<00:06:40.919> the<00:06:41.120> next<00:06:41.440> wave<00:06:42.080> of<00:06:42.479> crypto 00:06:42.950 --> 00:06:42.960 align:start position:0% will unlock the next wave of crypto 00:06:42.960 --> 00:06:47.070 align:start position:0% will unlock the next wave of crypto products<00:06:43.800> for<00:06:44.319> consumers<00:06:45.319> the<00:06:45.560> first<00:06:45.800> trend 00:06:47.070 --> 00:06:47.080 align:start position:0% products for consumers the first trend 00:06:47.080 --> 00:06:50.469 align:start position:0% products for consumers the first trend is<00:06:48.080> crypto<00:06:48.560> native<00:06:48.919> app<00:06:49.240> so<00:06:49.800> products<00:06:50.280> that 00:06:50.469 --> 00:06:50.479 align:start position:0% is crypto native app so products that 00:06:50.479 --> 00:06:53.550 align:start position:0% is crypto native app so products that are<00:06:51.240> built<00:06:51.960> on<00:06:52.280> crypto<00:06:52.680> rails<00:06:53.039> the<00:06:53.160> crypto 00:06:53.550 --> 00:06:53.560 align:start position:0% are built on crypto rails the crypto 00:06:53.560 --> 00:06:57.749 align:start position:0% are built on crypto rails the crypto infrastructure<00:06:54.199> is<00:06:54.479> very<00:06:54.759> much<00:06:55.599> core<00:06:56.639> to<00:06:57.639> you 00:06:57.749 --> 00:06:57.759 align:start position:0% infrastructure is very much core to you 00:06:57.759 --> 00:06:59.950 align:start position:0% infrastructure is very much core to you know<00:06:57.919> the<00:06:58.120> product<00:06:58.599> experience<00:06:59.680> that<00:06:59.800> are 00:06:59.950 --> 00:06:59.960 align:start position:0% know the product experience that are 00:06:59.960 --> 00:07:02.430 align:start position:0% know the product experience that are going<00:07:00.280> after<00:07:00.560> a<00:07:00.759> mainstream<00:07:01.759> audience<00:07:02.319> that 00:07:02.430 --> 00:07:02.440 align:start position:0% going after a mainstream audience that 00:07:02.440 --> 00:07:05.230 align:start position:0% going after a mainstream audience that are<00:07:02.599> trying<00:07:02.919> to<00:07:03.479> really<00:07:03.879> hide<00:07:04.440> abstract<00:07:05.000> a<00:07:05.080> lot 00:07:05.230 --> 00:07:05.240 align:start position:0% are trying to really hide abstract a lot 00:07:05.240 --> 00:07:08.350 align:start position:0% are trying to really hide abstract a lot of<00:07:05.440> the<00:07:06.000> crypto<00:07:06.400> mechanics<00:07:06.879> away<00:07:07.120> from<00:07:07.360> users 00:07:08.350 --> 00:07:08.360 align:start position:0% of the crypto mechanics away from users 00:07:08.360 --> 00:07:09.990 align:start position:0% of the crypto mechanics away from users but<00:07:08.520> crypto<00:07:08.879> is<00:07:09.039> like<00:07:09.199> fundamental<00:07:09.680> to<00:07:09.840> the 00:07:09.990 --> 00:07:10.000 align:start position:0% but crypto is like fundamental to the 00:07:10.000 --> 00:07:12.469 align:start position:0% but crypto is like fundamental to the product<00:07:10.280> from<00:07:10.440> the<00:07:10.560> outset<00:07:11.479> so<00:07:11.639> one<00:07:11.759> of<00:07:11.960> the 00:07:12.469 --> 00:07:12.479 align:start position:0% product from the outset so one of the 00:07:12.479 --> 00:07:14.150 align:start position:0% product from the outset so one of the you<00:07:12.599> know<00:07:12.720> most<00:07:12.919> visible<00:07:13.360> examples<00:07:13.759> of<00:07:13.960> this 00:07:14.150 --> 00:07:14.160 align:start position:0% you know most visible examples of this 00:07:14.160 --> 00:07:16.589 align:start position:0% you know most visible examples of this right<00:07:14.319> now<00:07:14.479> is<00:07:14.680> poly<00:07:15.199> Market<00:07:16.199> which<00:07:16.319> is<00:07:16.440> a 00:07:16.589 --> 00:07:16.599 align:start position:0% right now is poly Market which is a 00:07:16.599 --> 00:07:18.869 align:start position:0% right now is poly Market which is a product<00:07:16.840> built<00:07:17.039> on<00:07:17.199> crypto<00:07:17.560> rails<00:07:18.160> but<00:07:18.759> you 00:07:18.869 --> 00:07:18.879 align:start position:0% product built on crypto rails but you 00:07:18.879 --> 00:07:20.309 align:start position:0% product built on crypto rails but you know<00:07:19.120> has 00:07:20.309 --> 00:07:20.319 align:start position:0% know has 00:07:20.319 --> 00:07:23.110 align:start position:0% know has attracted<00:07:21.319> orders<00:07:21.680> of<00:07:21.879> magnitude<00:07:22.319> more<00:07:22.560> users 00:07:23.110 --> 00:07:23.120 align:start position:0% attracted orders of magnitude more users 00:07:23.120 --> 00:07:26.469 align:start position:0% attracted orders of magnitude more users than<00:07:23.360> the<00:07:23.639> kind<00:07:23.720> of<00:07:23.840> core<00:07:24.160> crypto<00:07:24.919> native 00:07:26.469 --> 00:07:26.479 align:start position:0% than the kind of core crypto native 00:07:26.479 --> 00:07:28.909 align:start position:0% than the kind of core crypto native population<00:07:27.479> and<00:07:27.840> you<00:07:27.960> know<00:07:28.120> openc 00:07:28.909 --> 00:07:28.919 align:start position:0% population and you know openc 00:07:28.919 --> 00:07:30.270 align:start position:0% population and you know openc accomplished<00:07:29.400> this<00:07:29.560> this<00:07:29.759> Blackbird<00:07:30.160> the 00:07:30.270 --> 00:07:30.280 align:start position:0% accomplished this this Blackbird the 00:07:30.280 --> 00:07:32.670 align:start position:0% accomplished this this Blackbird the restaurant<00:07:30.720> loyalty<00:07:31.680> app<00:07:31.919> is<00:07:32.120> accomplishing 00:07:32.670 --> 00:07:32.680 align:start position:0% restaurant loyalty app is accomplishing 00:07:32.680 --> 00:07:34.469 align:start position:0% restaurant loyalty app is accomplishing this<00:07:32.879> pump.<00:07:33.319> fun<00:07:33.520> is<00:07:33.680> accomplishing<00:07:34.199> this<00:07:34.360> and 00:07:34.469 --> 00:07:34.479 align:start position:0% this pump. fun is accomplishing this and 00:07:34.479 --> 00:07:36.629 align:start position:0% this pump. fun is accomplishing this and the<00:07:34.599> number<00:07:34.879> of<00:07:35.120> crypto<00:07:35.599> products<00:07:36.440> you<00:07:36.520> know 00:07:36.629 --> 00:07:36.639 align:start position:0% the number of crypto products you know 00:07:36.639 --> 00:07:38.510 align:start position:0% the number of crypto products you know that<00:07:36.759> are<00:07:36.879> Crypton<00:07:37.240> native<00:07:37.879> crypto<00:07:38.240> from<00:07:38.400> the 00:07:38.510 --> 00:07:38.520 align:start position:0% that are Crypton native crypto from the 00:07:38.520 --> 00:07:42.390 align:start position:0% that are Crypton native crypto from the outset<00:07:39.440> that<00:07:39.520> are<00:07:39.720> catering<00:07:40.240> to<00:07:41.160> a<00:07:41.319> broader 00:07:42.390 --> 00:07:42.400 align:start position:0% outset that are catering to a broader 00:07:42.400 --> 00:07:45.869 align:start position:0% outset that are catering to a broader audience<00:07:43.400> is<00:07:43.800> accelerating<00:07:44.440> a<00:07:44.639> lot<00:07:45.639> and<00:07:45.800> this 00:07:45.869 --> 00:07:45.879 align:start position:0% audience is accelerating a lot and this 00:07:45.879 --> 00:07:47.469 align:start position:0% audience is accelerating a lot and this is<00:07:46.080> one<00:07:46.319> Trend<00:07:46.680> that<00:07:46.800> we<00:07:46.919> think<00:07:47.080> is<00:07:47.199> going<00:07:47.319> to 00:07:47.469 --> 00:07:47.479 align:start position:0% is one Trend that we think is going to 00:07:47.479 --> 00:07:48.550 align:start position:0% is one Trend that we think is going to continue 00:07:48.550 --> 00:07:48.560 align:start position:0% continue 00:07:48.560 --> 00:07:51.710 align:start position:0% continue accelerating<00:07:49.560> and<00:07:50.120> we<00:07:50.280> break<00:07:50.639> down<00:07:51.479> kind<00:07:51.599> of 00:07:51.710 --> 00:07:51.720 align:start position:0% accelerating and we break down kind of 00:07:51.720 --> 00:07:53.390 align:start position:0% accelerating and we break down kind of like<00:07:51.840> there<00:07:51.960> are<00:07:52.120> four<00:07:52.560> four<00:07:52.960> common 00:07:53.390 --> 00:07:53.400 align:start position:0% like there are four four common 00:07:53.400 --> 00:07:55.070 align:start position:0% like there are four four common attributes<00:07:53.960> a<00:07:54.080> lot<00:07:54.199> of<00:07:54.479> a<00:07:54.560> lot<00:07:54.720> of<00:07:54.840> these 00:07:55.070 --> 00:07:55.080 align:start position:0% attributes a lot of a lot of these 00:07:55.080 --> 00:07:56.390 align:start position:0% attributes a lot of a lot of these experiences 00:07:56.390 --> 00:07:56.400 align:start position:0% experiences 00:07:56.400 --> 00:08:00.230 align:start position:0% experiences have<00:07:57.400> the<00:07:57.560> first<00:07:57.960> is<00:07:58.360> that<00:07:58.759> they<00:07:59.639> engaging 00:08:00.230 --> 00:08:00.240 align:start position:0% have the first is that they engaging 00:08:00.240 --> 00:08:02.430 align:start position:0% have the first is that they engaging like<00:08:00.400> they're<00:08:00.840> experiences<00:08:01.560> that<00:08:01.800> people 00:08:02.430 --> 00:08:02.440 align:start position:0% like they're experiences that people 00:08:02.440 --> 00:08:05.510 align:start position:0% like they're experiences that people want<00:08:03.039> to<00:08:04.039> use<00:08:04.479> and<00:08:04.639> come<00:08:04.879> back<00:08:05.039> to<00:08:05.319> and 00:08:05.510 --> 00:08:05.520 align:start position:0% want to use and come back to and 00:08:05.520 --> 00:08:09.029 align:start position:0% want to use and come back to and participate<00:08:06.199> in<00:08:07.199> so<00:08:07.599> whether<00:08:07.960> that<00:08:08.319> is<00:08:08.919> you 00:08:09.029 --> 00:08:09.039 align:start position:0% participate in so whether that is you 00:08:09.039 --> 00:08:11.189 align:start position:0% participate in so whether that is you know<00:08:09.199> something<00:08:09.520> like<00:08:09.720> Zora<00:08:10.400> where<00:08:10.599> you<00:08:10.800> can 00:08:11.189 --> 00:08:11.199 align:start position:0% know something like Zora where you can 00:08:11.199 --> 00:08:13.710 align:start position:0% know something like Zora where you can consume<00:08:11.759> content<00:08:12.360> you<00:08:12.479> can<00:08:12.800> like<00:08:13.159> content<00:08:13.599> as 00:08:13.710 --> 00:08:13.720 align:start position:0% consume content you can like content as 00:08:13.720 --> 00:08:15.869 align:start position:0% consume content you can like content as a<00:08:13.879> Creator<00:08:14.319> you<00:08:14.440> get<00:08:14.639> rewarded<00:08:15.120> for<00:08:15.360> posting 00:08:15.869 --> 00:08:15.879 align:start position:0% a Creator you get rewarded for posting 00:08:15.879 --> 00:08:19.830 align:start position:0% a Creator you get rewarded for posting content<00:08:16.680> to<00:08:17.120> games<00:08:17.479> like<00:08:17.639> friend<00:08:18.080> pet<00:08:19.080> to 00:08:19.830 --> 00:08:19.840 align:start position:0% content to games like friend pet to 00:08:19.840 --> 00:08:22.670 align:start position:0% content to games like friend pet to receipts<00:08:20.479> which<00:08:20.639> is<00:08:21.000> a<00:08:21.639> fun<00:08:22.080> competitive 00:08:22.670 --> 00:08:22.680 align:start position:0% receipts which is a fun competitive 00:08:22.680 --> 00:08:25.869 align:start position:0% receipts which is a fun competitive fitness<00:08:23.159> app<00:08:23.800> on<00:08:24.120> chain<00:08:25.120> you<00:08:25.199> know<00:08:25.360> we're 00:08:25.869 --> 00:08:25.879 align:start position:0% fitness app on chain you know we're 00:08:25.879 --> 00:08:28.950 align:start position:0% fitness app on chain you know we're seeing<00:08:26.879> you<00:08:27.280> the<00:08:27.560> Baseline<00:08:28.080> of<00:08:28.319> just<00:08:28.479> a<00:08:28.639> fun 00:08:28.950 --> 00:08:28.960 align:start position:0% seeing you the Baseline of just a fun 00:08:28.960 --> 00:08:31.350 align:start position:0% seeing you the Baseline of just a fun experience<00:08:29.720> that<00:08:29.840> people<00:08:30.120> want<00:08:30.440> to<00:08:30.919> engage 00:08:31.350 --> 00:08:31.360 align:start position:0% experience that people want to engage 00:08:31.360 --> 00:08:34.190 align:start position:0% experience that people want to engage with<00:08:31.599> again<00:08:31.759> and<00:08:32.000> again<00:08:32.880> as<00:08:33.399> the<00:08:33.599> most<00:08:33.839> common 00:08:34.190 --> 00:08:34.200 align:start position:0% with again and again as the most common 00:08:34.200 --> 00:08:36.990 align:start position:0% with again and again as the most common attribute<00:08:34.919> for<00:08:35.919> crypto<00:08:36.279> native<00:08:36.680> products 00:08:36.990 --> 00:08:37.000 align:start position:0% attribute for crypto native products 00:08:37.000 --> 00:08:39.990 align:start position:0% attribute for crypto native products that<00:08:37.120> are<00:08:37.240> breaking<00:08:37.640> out<00:08:38.039> into<00:08:38.320> a<00:08:38.440> broader 00:08:39.990 --> 00:08:40.000 align:start position:0% that are breaking out into a broader 00:08:40.000 --> 00:08:42.990 align:start position:0% that are breaking out into a broader audience<00:08:41.000> the<00:08:41.159> second<00:08:41.640> and<00:08:41.760> one<00:08:41.959> that's<00:08:42.240> very 00:08:42.990 --> 00:08:43.000 align:start position:0% audience the second and one that's very 00:08:43.000 --> 00:08:45.150 align:start position:0% audience the second and one that's very kind<00:08:43.120> of<00:08:43.279> close<00:08:43.519> to<00:08:43.839> home<00:08:44.039> for<00:08:44.240> us<00:08:44.399> at<00:08:44.560> privy<00:08:44.920> is 00:08:45.150 --> 00:08:45.160 align:start position:0% kind of close to home for us at privy is 00:08:45.160 --> 00:08:48.030 align:start position:0% kind of close to home for us at privy is uxx<00:08:45.640> for<00:08:45.880> everyone<00:08:46.680> so<00:08:46.959> even<00:08:47.160> though<00:08:47.320> it<00:08:47.440> is<00:08:47.560> a 00:08:48.030 --> 00:08:48.040 align:start position:0% uxx for everyone so even though it is a 00:08:48.040 --> 00:08:52.269 align:start position:0% uxx for everyone so even though it is a crypto<00:08:49.040> experience<00:08:49.560> at<00:08:49.720> its<00:08:50.240> core<00:08:51.240> it<00:08:51.480> is 00:08:52.269 --> 00:08:52.279 align:start position:0% crypto experience at its core it is 00:08:52.279 --> 00:08:54.310 align:start position:0% crypto experience at its core it is friendly<00:08:52.720> and<00:08:52.959> familiar<00:08:53.480> to<00:08:53.600> people<00:08:53.800> who<00:08:53.959> know 00:08:54.310 --> 00:08:54.320 align:start position:0% friendly and familiar to people who know 00:08:54.320 --> 00:08:56.670 align:start position:0% friendly and familiar to people who know absolutely<00:08:54.839> nothing<00:08:55.200> about<00:08:55.480> crypto<00:08:56.440> so 00:08:56.670 --> 00:08:56.680 align:start position:0% absolutely nothing about crypto so 00:08:56.680 --> 00:08:58.230 align:start position:0% absolutely nothing about crypto so whether<00:08:57.000> it's<00:08:57.360> you<00:08:57.480> know<00:08:57.640> what<00:08:57.760> we<00:08:57.920> have<00:08:58.079> on 00:08:58.230 --> 00:08:58.240 align:start position:0% whether it's you know what we have on 00:08:58.240 --> 00:09:00.030 align:start position:0% whether it's you know what we have on the<00:08:58.440> left<00:08:59.079> with 00:09:00.030 --> 00:09:00.040 align:start position:0% the left with 00:09:00.040 --> 00:09:01.790 align:start position:0% the left with pirate<00:09:00.399> nation<00:09:00.839> which<00:09:00.959> is<00:09:01.079> one<00:09:01.160> of<00:09:01.360> the<00:09:01.560> most 00:09:01.790 --> 00:09:01.800 align:start position:0% pirate nation which is one of the most 00:09:01.800 --> 00:09:04.350 align:start position:0% pirate nation which is one of the most popular<00:09:02.200> crypto<00:09:02.640> games<00:09:03.519> which<00:09:03.680> allows<00:09:04.000> users 00:09:04.350 --> 00:09:04.360 align:start position:0% popular crypto games which allows users 00:09:04.360 --> 00:09:07.750 align:start position:0% popular crypto games which allows users to<00:09:04.560> sign<00:09:04.800> in<00:09:05.040> with<00:09:05.800> Google<00:09:06.160> login<00:09:06.880> or<00:09:07.240> Discord 00:09:07.750 --> 00:09:07.760 align:start position:0% to sign in with Google login or Discord 00:09:07.760 --> 00:09:09.990 align:start position:0% to sign in with Google login or Discord and<00:09:07.959> get<00:09:08.240> a<00:09:08.480> fully<00:09:08.800> self-<00:09:09.120> custodial<00:09:09.640> powerful 00:09:09.990 --> 00:09:10.000 align:start position:0% and get a fully self- custodial powerful 00:09:10.000 --> 00:09:11.310 align:start position:0% and get a fully self- custodial powerful wallet<00:09:10.320> under<00:09:10.519> the<00:09:10.640> hood<00:09:10.880> that<00:09:11.000> could<00:09:11.120> do 00:09:11.310 --> 00:09:11.320 align:start position:0% wallet under the hood that could do 00:09:11.320 --> 00:09:14.750 align:start position:0% wallet under the hood that could do anything<00:09:12.040> you<00:09:12.160> need<00:09:12.399> it<00:09:12.519> to<00:09:12.720> on<00:09:12.920> chain<00:09:13.880> to 00:09:14.750 --> 00:09:14.760 align:start position:0% anything you need it to on chain to 00:09:14.760 --> 00:09:20.470 align:start position:0% anything you need it to on chain to anime<00:09:15.760> um<00:09:16.120> which<00:09:16.320> is<00:09:16.880> a<00:09:18.200> fun<00:09:19.200> ecosystem<00:09:20.040> of 00:09:20.470 --> 00:09:20.480 align:start position:0% anime um which is a fun ecosystem of 00:09:20.480 --> 00:09:23.150 align:start position:0% anime um which is a fun ecosystem of experiences<00:09:21.360> centered<00:09:21.800> around<00:09:22.160> anime<00:09:22.760> where 00:09:23.150 --> 00:09:23.160 align:start position:0% experiences centered around anime where 00:09:23.160 --> 00:09:25.389 align:start position:0% experiences centered around anime where you<00:09:23.279> know<00:09:23.519> you<00:09:23.640> could<00:09:23.839> sign<00:09:24.120> up<00:09:24.440> and<00:09:25.079> start 00:09:25.389 --> 00:09:25.399 align:start position:0% you know you could sign up and start 00:09:25.399 --> 00:09:27.190 align:start position:0% you know you could sign up and start collecting<00:09:25.800> onchain<00:09:26.360> assets<00:09:26.800> but<00:09:26.920> you<00:09:27.040> have 00:09:27.190 --> 00:09:27.200 align:start position:0% collecting onchain assets but you have 00:09:27.200 --> 00:09:29.430 align:start position:0% collecting onchain assets but you have no<00:09:27.399> idea<00:09:28.360> that<00:09:28.680> you<00:09:28.800> know<00:09:28.959> anything 00:09:29.430 --> 00:09:29.440 align:start position:0% no idea that you know anything 00:09:29.440 --> 00:09:30.829 align:start position:0% no idea that you know anything interacting<00:09:29.959> with<00:09:30.079> is 00:09:30.829 --> 00:09:30.839 align:start position:0% interacting with is 00:09:30.839 --> 00:09:34.750 align:start position:0% interacting with is crypto<00:09:31.839> to<00:09:32.240> B3<00:09:33.040> who<00:09:33.519> implemented<00:09:34.519> an 00:09:34.750 --> 00:09:34.760 align:start position:0% crypto to B3 who implemented an 00:09:34.760 --> 00:09:37.509 align:start position:0% crypto to B3 who implemented an experience<00:09:35.560> uh<00:09:35.680> we<00:09:35.839> call<00:09:36.160> guest<00:09:36.440> mode<00:09:37.000> where 00:09:37.509 --> 00:09:37.519 align:start position:0% experience uh we call guest mode where 00:09:37.519 --> 00:09:39.470 align:start position:0% experience uh we call guest mode where you<00:09:37.640> can<00:09:37.839> get<00:09:38.000> a<00:09:38.160> wallet<00:09:38.760> without<00:09:39.079> actually 00:09:39.470 --> 00:09:39.480 align:start position:0% you can get a wallet without actually 00:09:39.480 --> 00:09:41.310 align:start position:0% you can get a wallet without actually creating<00:09:39.839> an<00:09:40.079> account<00:09:40.839> uh<00:09:40.959> which<00:09:41.040> is<00:09:41.160> an 00:09:41.310 --> 00:09:41.320 align:start position:0% creating an account uh which is an 00:09:41.320 --> 00:09:43.030 align:start position:0% creating an account uh which is an experience<00:09:41.720> that's<00:09:41.959> familiar<00:09:42.399> to<00:09:42.600> people<00:09:42.839> who 00:09:43.030 --> 00:09:43.040 align:start position:0% experience that's familiar to people who 00:09:43.040 --> 00:09:45.030 align:start position:0% experience that's familiar to people who shop<00:09:43.320> online<00:09:43.760> for<00:09:43.959> example<00:09:44.399> and<00:09:44.680> aren't<00:09:44.959> going 00:09:45.030 --> 00:09:45.040 align:start position:0% shop online for example and aren't going 00:09:45.040 --> 00:09:46.350 align:start position:0% shop online for example and aren't going to<00:09:45.160> create<00:09:45.440> an<00:09:45.600> account<00:09:45.880> in<00:09:45.959> order<00:09:46.200> to 00:09:46.350 --> 00:09:46.360 align:start position:0% to create an account in order to 00:09:46.360 --> 00:09:49.030 align:start position:0% to create an account in order to purchase<00:09:46.920> something<00:09:47.920> you<00:09:48.040> know<00:09:48.279> a<00:09:48.399> lot<00:09:48.560> of<00:09:48.920> a 00:09:49.030 --> 00:09:49.040 align:start position:0% purchase something you know a lot of a 00:09:49.040 --> 00:09:51.750 align:start position:0% purchase something you know a lot of a lot<00:09:49.160> of<00:09:49.440> the<00:09:49.839> ux<00:09:50.320> elements<00:09:50.720> of<00:09:50.920> these<00:09:51.160> apps<00:09:51.399> are 00:09:51.750 --> 00:09:51.760 align:start position:0% lot of the ux elements of these apps are 00:09:51.760 --> 00:09:53.630 align:start position:0% lot of the ux elements of these apps are accessible<00:09:52.279> for<00:09:52.600> people<00:09:52.800> who<00:09:52.959> don't<00:09:53.399> know 00:09:53.630 --> 00:09:53.640 align:start position:0% accessible for people who don't know 00:09:53.640 --> 00:09:54.910 align:start position:0% accessible for people who don't know anything<00:09:53.920> about 00:09:54.910 --> 00:09:54.920 align:start position:0% anything about 00:09:54.920 --> 00:09:58.710 align:start position:0% anything about crypto<00:09:55.920> the<00:09:56.120> next<00:09:56.440> is<00:09:56.959> uh<00:09:57.160> real<00:09:57.480> world<00:09:57.800> tie-in 00:09:58.710 --> 00:09:58.720 align:start position:0% crypto the next is uh real world tie-in 00:09:58.720 --> 00:10:01.829 align:start position:0% crypto the next is uh real world tie-in so<00:09:58.920> a<00:09:59.000> lot<00:09:59.120> of<00:09:59.440> the<00:09:59.560> most<00:09:59.800> popular<00:10:00.360> apps<00:10:00.680> we<00:10:00.839> see 00:10:01.829 --> 00:10:01.839 align:start position:0% so a lot of the most popular apps we see 00:10:01.839 --> 00:10:04.069 align:start position:0% so a lot of the most popular apps we see are<00:10:02.079> manifesting<00:10:03.000> in<00:10:03.120> the<00:10:03.279> real<00:10:03.519> world<00:10:03.880> in 00:10:04.069 --> 00:10:04.079 align:start position:0% are manifesting in the real world in 00:10:04.079 --> 00:10:06.190 align:start position:0% are manifesting in the real world in different<00:10:04.399> ways<00:10:05.200> so<00:10:05.440> whether<00:10:05.720> that's<00:10:06.079> you 00:10:06.190 --> 00:10:06.200 align:start position:0% different ways so whether that's you 00:10:06.200 --> 00:10:09.030 align:start position:0% different ways so whether that's you know<00:10:06.399> Blackbird<00:10:07.000> who<00:10:07.240> has<00:10:08.240> many<00:10:08.480> of<00:10:08.600> the<00:10:08.760> most 00:10:09.030 --> 00:10:09.040 align:start position:0% know Blackbird who has many of the most 00:10:09.040 --> 00:10:12.110 align:start position:0% know Blackbird who has many of the most popular<00:10:09.440> restaurants<00:10:10.160> in<00:10:10.360> New<00:10:11.000> York<00:10:12.000> there 00:10:12.110 --> 00:10:12.120 align:start position:0% popular restaurants in New York there 00:10:12.120 --> 00:10:14.190 align:start position:0% popular restaurants in New York there are<00:10:12.360> physical<00:10:12.800> pucks<00:10:13.200> at<00:10:13.320> the<00:10:13.519> restaurant 00:10:14.190 --> 00:10:14.200 align:start position:0% are physical pucks at the restaurant 00:10:14.200 --> 00:10:16.470 align:start position:0% are physical pucks at the restaurant that<00:10:14.320> you<00:10:14.399> can<00:10:14.600> tap<00:10:14.800> your<00:10:14.920> phone<00:10:15.160> to<00:10:15.560> to<00:10:16.120> earn 00:10:16.470 --> 00:10:16.480 align:start position:0% that you can tap your phone to to earn 00:10:16.480 --> 00:10:18.710 align:start position:0% that you can tap your phone to to earn rewards<00:10:16.920> points<00:10:17.279> that<00:10:17.360> you<00:10:17.440> could<00:10:17.600> redeem<00:10:18.079> to 00:10:18.710 --> 00:10:18.720 align:start position:0% rewards points that you could redeem to 00:10:18.720 --> 00:10:21.670 align:start position:0% rewards points that you could redeem to either<00:10:19.000> pay<00:10:19.160> your<00:10:19.320> bill<00:10:19.959> or 00:10:21.670 --> 00:10:21.680 align:start position:0% either pay your bill or 00:10:21.680 --> 00:10:24.790 align:start position:0% either pay your bill or um<00:10:22.680> get<00:10:22.800> a<00:10:22.920> free<00:10:23.120> drink<00:10:23.399> at<00:10:23.519> the<00:10:23.640> restaurant<00:10:24.240> to 00:10:24.790 --> 00:10:24.800 align:start position:0% um get a free drink at the restaurant to 00:10:24.800 --> 00:10:28.269 align:start position:0% um get a free drink at the restaurant to you<00:10:24.920> know<00:10:25.360> seeing<00:10:26.360> onchain<00:10:27.279> Assets<00:10:28.079> in 00:10:28.269 --> 00:10:28.279 align:start position:0% you know seeing onchain Assets in 00:10:28.279 --> 00:10:30.350 align:start position:0% you know seeing onchain Assets in Walmart<00:10:28.720> and<00:10:28.880> Target<00:10:29.519> as<00:10:29.800> as<00:10:29.920> the<00:10:30.040> pudgy 00:10:30.350 --> 00:10:30.360 align:start position:0% Walmart and Target as as the pudgy 00:10:30.360 --> 00:10:33.550 align:start position:0% Walmart and Target as as the pudgy Penguins<00:10:30.800> team<00:10:31.120> is<00:10:31.720> accomplishing<00:10:32.720> you<00:10:32.839> know 00:10:33.550 --> 00:10:33.560 align:start position:0% Penguins team is accomplishing you know 00:10:33.560 --> 00:10:36.110 align:start position:0% Penguins team is accomplishing you know showing<00:10:34.560> onchain<00:10:35.120> Assets<00:10:35.399> in<00:10:35.480> the<00:10:35.600> real<00:10:35.839> world 00:10:36.110 --> 00:10:36.120 align:start position:0% showing onchain Assets in the real world 00:10:36.120 --> 00:10:39.509 align:start position:0% showing onchain Assets in the real world is<00:10:36.519> another<00:10:37.279> very<00:10:37.560> common<00:10:37.880> element<00:10:38.800> for<00:10:39.240> apps 00:10:39.509 --> 00:10:39.519 align:start position:0% is another very common element for apps 00:10:39.519 --> 00:10:42.430 align:start position:0% is another very common element for apps that<00:10:39.600> are<00:10:39.720> breaking<00:10:40.240> out<00:10:41.240> and<00:10:41.320> then<00:10:41.480> the<00:10:41.720> last 00:10:42.430 --> 00:10:42.440 align:start position:0% that are breaking out and then the last 00:10:42.440 --> 00:10:44.310 align:start position:0% that are breaking out and then the last piece<00:10:42.680> is<00:10:42.920> around<00:10:43.440> account<00:10:43.720> funding<00:10:44.160> and 00:10:44.310 --> 00:10:44.320 align:start position:0% piece is around account funding and 00:10:44.320 --> 00:10:47.110 align:start position:0% piece is around account funding and getting<00:10:44.600> people<00:10:44.800> to<00:10:44.959> transact<00:10:45.560> on<00:10:45.920> chain 00:10:47.110 --> 00:10:47.120 align:start position:0% getting people to transact on chain 00:10:47.120 --> 00:10:49.389 align:start position:0% getting people to transact on chain without<00:10:48.120> taking<00:10:48.440> them<00:10:48.720> through<00:10:49.040> the<00:10:49.320> the 00:10:49.389 --> 00:10:49.399 align:start position:0% without taking them through the the 00:10:49.399 --> 00:10:51.150 align:start position:0% without taking them through the the multi-step<00:10:50.000> journey<00:10:50.320> of<00:10:50.440> getting<00:10:50.720> crypto 00:10:51.150 --> 00:10:51.160 align:start position:0% multi-step journey of getting crypto 00:10:51.160 --> 00:10:53.509 align:start position:0% multi-step journey of getting crypto assets<00:10:51.600> so<00:10:52.040> we<00:10:52.160> have<00:10:52.279> a<00:10:52.440> video<00:10:52.839> here<00:10:53.040> of<00:10:53.279> one<00:10:53.399> of 00:10:53.509 --> 00:10:53.519 align:start position:0% assets so we have a video here of one of 00:10:53.519 --> 00:10:55.389 align:start position:0% assets so we have a video here of one of our<00:10:53.639> customers<00:10:54.120> Rodeo<00:10:54.600> who<00:10:54.800> has<00:10:54.880> a<00:10:55.120> really 00:10:55.389 --> 00:10:55.399 align:start position:0% our customers Rodeo who has a really 00:10:55.399 --> 00:10:57.870 align:start position:0% our customers Rodeo who has a really nice<00:10:56.120> Apple<00:10:56.440> pay<00:10:56.680> funding<00:10:57.040> flow<00:10:57.480> where<00:10:57.680> you 00:10:57.870 --> 00:10:57.880 align:start position:0% nice Apple pay funding flow where you 00:10:57.880 --> 00:11:00.110 align:start position:0% nice Apple pay funding flow where you can<00:10:58.600> you<00:10:58.680> know<00:10:58.880> purchase 00:11:00.110 --> 00:11:00.120 align:start position:0% can you know purchase 00:11:00.120 --> 00:11:03.030 align:start position:0% can you know purchase uh<00:11:00.360> balance<00:11:01.000> that<00:11:01.120> allows<00:11:01.440> you<00:11:01.600> to<00:11:01.920> Mint<00:11:02.240> nfts 00:11:03.030 --> 00:11:03.040 align:start position:0% uh balance that allows you to Mint nfts 00:11:03.040 --> 00:11:06.389 align:start position:0% uh balance that allows you to Mint nfts in<00:11:03.120> the<00:11:03.240> rodeo<00:11:03.680> app<00:11:03.880> using<00:11:04.200> Apple<00:11:04.680> pay<00:11:05.680> and<00:11:06.279> you 00:11:06.389 --> 00:11:06.399 align:start position:0% in the rodeo app using Apple pay and you 00:11:06.399 --> 00:11:08.590 align:start position:0% in the rodeo app using Apple pay and you know<00:11:06.600> once<00:11:06.839> you<00:11:07.200> once<00:11:07.399> you<00:11:07.639> have<00:11:07.959> your<00:11:08.200> credits 00:11:08.590 --> 00:11:08.600 align:start position:0% know once you once you have your credits 00:11:08.600 --> 00:11:09.990 align:start position:0% know once you once you have your credits as<00:11:08.760> they're<00:11:08.920> framing<00:11:09.320> it<00:11:09.519> here<00:11:09.720> you<00:11:09.839> could 00:11:09.990 --> 00:11:10.000 align:start position:0% as they're framing it here you could 00:11:10.000 --> 00:11:13.670 align:start position:0% as they're framing it here you could just<00:11:10.200> go<00:11:10.440> and<00:11:11.320> collect<00:11:12.240> the<00:11:12.680> asset<00:11:13.240> and<00:11:13.560> it 00:11:13.670 --> 00:11:13.680 align:start position:0% just go and collect the asset and it 00:11:13.680 --> 00:11:17.030 align:start position:0% just go and collect the asset and it feels<00:11:14.200> familiar<00:11:14.920> and<00:11:15.760> leverages<00:11:16.760> you<00:11:16.880> know 00:11:17.030 --> 00:11:17.040 align:start position:0% feels familiar and leverages you know 00:11:17.040 --> 00:11:19.190 align:start position:0% feels familiar and leverages you know payment<00:11:17.320> methods<00:11:17.639> you're<00:11:17.800> already<00:11:18.040> familiar 00:11:19.190 --> 00:11:19.200 align:start position:0% payment methods you're already familiar 00:11:19.200 --> 00:11:21.509 align:start position:0% payment methods you're already familiar with<00:11:20.200> so<00:11:20.360> those<00:11:20.480> are<00:11:20.600> some<00:11:20.720> of<00:11:20.839> the<00:11:21.000> attributes 00:11:21.509 --> 00:11:21.519 align:start position:0% with so those are some of the attributes 00:11:21.519 --> 00:11:24.069 align:start position:0% with so those are some of the attributes of<00:11:21.880> these<00:11:22.079> Crypton<00:11:22.519> native<00:11:23.279> experiences<00:11:23.959> that 00:11:24.069 --> 00:11:24.079 align:start position:0% of these Crypton native experiences that 00:11:24.079 --> 00:11:26.629 align:start position:0% of these Crypton native experiences that are<00:11:24.200> targeting<00:11:24.600> mainstream<00:11:25.399> users<00:11:26.399> and<00:11:26.480> then 00:11:26.629 --> 00:11:26.639 align:start position:0% are targeting mainstream users and then 00:11:26.639 --> 00:11:29.750 align:start position:0% are targeting mainstream users and then there's<00:11:26.880> this<00:11:27.079> parallel<00:11:27.600> trend<00:11:28.360> of 00:11:29.750 --> 00:11:29.760 align:start position:0% there's this parallel trend of 00:11:29.760 --> 00:11:32.870 align:start position:0% there's this parallel trend of products<00:11:30.360> that<00:11:31.000> were<00:11:31.320> built<00:11:32.320> you<00:11:32.480> know 00:11:32.870 --> 00:11:32.880 align:start position:0% products that were built you know 00:11:32.880 --> 00:11:35.949 align:start position:0% products that were built you know without<00:11:33.519> crypto<00:11:34.160> in<00:11:34.639> mind<00:11:35.639> that<00:11:35.760> are 00:11:35.949 --> 00:11:35.959 align:start position:0% without crypto in mind that are 00:11:35.959 --> 00:11:39.430 align:start position:0% without crypto in mind that are leveraging<00:11:37.079> crypto<00:11:38.079> infra<00:11:38.760> to<00:11:39.000> accomplish 00:11:39.430 --> 00:11:39.440 align:start position:0% leveraging crypto infra to accomplish 00:11:39.440 --> 00:11:40.710 align:start position:0% leveraging crypto infra to accomplish things<00:11:39.639> that<00:11:39.720> wouldn't<00:11:39.920> have<00:11:40.079> been<00:11:40.279> possible 00:11:40.710 --> 00:11:40.720 align:start position:0% things that wouldn't have been possible 00:11:40.720 --> 00:11:43.190 align:start position:0% things that wouldn't have been possible without<00:11:41.000> it<00:11:42.000> and<00:11:42.320> this<00:11:42.440> is<00:11:42.600> one<00:11:42.720> of<00:11:42.800> the<00:11:42.959> most 00:11:43.190 --> 00:11:43.200 align:start position:0% without it and this is one of the most 00:11:43.200 --> 00:11:45.590 align:start position:0% without it and this is one of the most exciting<00:11:43.720> things<00:11:44.279> we're<00:11:44.519> seeing<00:11:44.880> at<00:11:45.079> privy 00:11:45.590 --> 00:11:45.600 align:start position:0% exciting things we're seeing at privy 00:11:45.600 --> 00:11:49.310 align:start position:0% exciting things we're seeing at privy right<00:11:45.920> now<00:11:46.920> and<00:11:47.240> it's<00:11:47.519> accelerating<00:11:48.160> a<00:11:48.360> ton 00:11:49.310 --> 00:11:49.320 align:start position:0% right now and it's accelerating a ton 00:11:49.320 --> 00:11:51.470 align:start position:0% right now and it's accelerating a ton where<00:11:49.839> many<00:11:50.480> many 00:11:51.470 --> 00:11:51.480 align:start position:0% where many many 00:11:51.480 --> 00:11:54.230 align:start position:0% where many many fintechs<00:11:52.480> in<00:11:52.680> particular<00:11:53.560> are<00:11:53.720> starting<00:11:54.040> to 00:11:54.230 --> 00:11:54.240 align:start position:0% fintechs in particular are starting to 00:11:54.240 --> 00:11:56.870 align:start position:0% fintechs in particular are starting to leverage<00:11:54.839> crypto<00:11:55.720> for<00:11:56.040> payment<00:11:56.360> rail 00:11:56.870 --> 00:11:56.880 align:start position:0% leverage crypto for payment rail 00:11:56.880 --> 00:11:58.949 align:start position:0% leverage crypto for payment rail benefits<00:11:57.880> and<00:11:58.079> and<00:11:58.160> we'll<00:11:58.320> get<00:11:58.480> into<00:11:58.680> some<00:11:58.800> of 00:11:58.949 --> 00:11:58.959 align:start position:0% benefits and and we'll get into some of 00:11:58.959 --> 00:12:02.710 align:start position:0% benefits and and we'll get into some of the<00:11:59.040> other<00:11:59.519> attributes<00:12:00.519> um<00:12:01.279> but<00:12:02.160> this<00:12:02.320> is<00:12:02.600> this 00:12:02.710 --> 00:12:02.720 align:start position:0% the other attributes um but this is this 00:12:02.720 --> 00:12:05.110 align:start position:0% the other attributes um but this is this is<00:12:02.920> this<00:12:03.120> parallel<00:12:03.600> Trend<00:12:04.360> where<00:12:04.880> these 00:12:05.110 --> 00:12:05.120 align:start position:0% is this parallel Trend where these 00:12:05.120 --> 00:12:07.430 align:start position:0% is this parallel Trend where these products<00:12:05.519> already<00:12:06.079> have<00:12:06.480> a<00:12:06.600> ton<00:12:06.800> of<00:12:06.959> reach 00:12:07.430 --> 00:12:07.440 align:start position:0% products already have a ton of reach 00:12:07.440 --> 00:12:10.550 align:start position:0% products already have a ton of reach they<00:12:07.839> have<00:12:08.839> tens<00:12:09.399> hundreds<00:12:09.760> of<00:12:09.880> millions<00:12:10.200> of 00:12:10.550 --> 00:12:10.560 align:start position:0% they have tens hundreds of millions of 00:12:10.560 --> 00:12:13.110 align:start position:0% they have tens hundreds of millions of users<00:12:11.560> and<00:12:11.680> they're<00:12:11.880> giving<00:12:12.120> them<00:12:12.360> access<00:12:12.720> to 00:12:13.110 --> 00:12:13.120 align:start position:0% users and they're giving them access to 00:12:13.120 --> 00:12:16.269 align:start position:0% users and they're giving them access to crypto<00:12:13.920> rails<00:12:14.920> and<00:12:15.199> the<00:12:15.399> attributes<00:12:16.000> that<00:12:16.160> a 00:12:16.269 --> 00:12:16.279 align:start position:0% crypto rails and the attributes that a 00:12:16.279 --> 00:12:18.990 align:start position:0% crypto rails and the attributes that a lot<00:12:16.440> of<00:12:16.639> these<00:12:16.839> projects<00:12:17.199> have<00:12:17.320> in<00:12:17.480> common<00:12:17.720> are 00:12:18.990 --> 00:12:19.000 align:start position:0% lot of these projects have in common are 00:12:19.000 --> 00:12:21.910 align:start position:0% lot of these projects have in common are one<00:12:20.000> they're<00:12:20.440> looking<00:12:20.760> to<00:12:20.920> use<00:12:21.160> crypto<00:12:21.519> rails 00:12:21.910 --> 00:12:21.920 align:start position:0% one they're looking to use crypto rails 00:12:21.920 --> 00:12:25.910 align:start position:0% one they're looking to use crypto rails to<00:12:22.079> give<00:12:22.240> users<00:12:22.920> access<00:12:23.480> to<00:12:23.880> USD<00:12:24.680> balance<00:12:25.680> so 00:12:25.910 --> 00:12:25.920 align:start position:0% to give users access to USD balance so 00:12:25.920 --> 00:12:28.750 align:start position:0% to give users access to USD balance so this<00:12:26.160> this<00:12:26.240> is<00:12:26.320> a<00:12:26.519> product<00:12:27.000> do<00:12:28.000> they're<00:12:28.519> uh<00:12:28.639> one 00:12:28.750 --> 00:12:28.760 align:start position:0% this this is a product do they're uh one 00:12:28.760 --> 00:12:31.670 align:start position:0% this this is a product do they're uh one of<00:12:28.839> the<00:12:28.920> most<00:12:29.320> popular<00:12:30.199> Neo<00:12:30.600> banks<00:12:30.880> in<00:12:31.040> Latin 00:12:31.670 --> 00:12:31.680 align:start position:0% of the most popular Neo banks in Latin 00:12:31.680 --> 00:12:34.550 align:start position:0% of the most popular Neo banks in Latin America<00:12:32.680> and<00:12:32.839> they're<00:12:33.040> using<00:12:33.399> crypto<00:12:33.800> infra 00:12:34.550 --> 00:12:34.560 align:start position:0% America and they're using crypto infra 00:12:34.560 --> 00:12:37.870 align:start position:0% America and they're using crypto infra to<00:12:34.880> give<00:12:35.760> people<00:12:36.000> in<00:12:36.160> Mexico<00:12:36.880> and<00:12:37.160> Argentina 00:12:37.870 --> 00:12:37.880 align:start position:0% to give people in Mexico and Argentina 00:12:37.880 --> 00:12:40.829 align:start position:0% to give people in Mexico and Argentina access<00:12:38.240> to<00:12:38.519> USD<00:12:39.240> balance<00:12:40.240> um<00:12:40.480> but<00:12:40.560> you<00:12:40.639> would 00:12:40.829 --> 00:12:40.839 align:start position:0% access to USD balance um but you would 00:12:40.839 --> 00:12:42.670 align:start position:0% access to USD balance um but you would never<00:12:41.199> you<00:12:41.279> would<00:12:41.480> never<00:12:41.720> know<00:12:42.199> there's<00:12:42.519> a 00:12:42.670 --> 00:12:42.680 align:start position:0% never you would never know there's a 00:12:42.680 --> 00:12:45.829 align:start position:0% never you would never know there's a trace<00:12:42.959> of<00:12:43.160> crypto<00:12:43.519> infra<00:12:44.000> in<00:12:44.160> the<00:12:44.360> app<00:12:45.360> it<00:12:45.680> just 00:12:45.829 --> 00:12:45.839 align:start position:0% trace of crypto infra in the app it just 00:12:45.839 --> 00:12:47.829 align:start position:0% trace of crypto infra in the app it just feels<00:12:46.160> like<00:12:46.279> you<00:12:46.399> have<00:12:46.519> a<00:12:46.639> dollar<00:12:46.959> balance<00:12:47.680> you 00:12:47.829 --> 00:12:47.839 align:start position:0% feels like you have a dollar balance you 00:12:47.839 --> 00:12:51.629 align:start position:0% feels like you have a dollar balance you can<00:12:48.560> you<00:12:48.680> know<00:12:48.839> earn<00:12:49.079> your<00:12:49.320> paycheck<00:12:50.040> in<00:12:50.639> USD 00:12:51.629 --> 00:12:51.639 align:start position:0% can you know earn your paycheck in USD 00:12:51.639 --> 00:12:53.269 align:start position:0% can you know earn your paycheck in USD which<00:12:51.760> is<00:12:51.880> a<00:12:51.959> great<00:12:52.160> store<00:12:52.360> of<00:12:52.519> value<00:12:52.920> and<00:12:53.040> then 00:12:53.269 --> 00:12:53.279 align:start position:0% which is a great store of value and then 00:12:53.279 --> 00:12:54.949 align:start position:0% which is a great store of value and then spend<00:12:53.560> it<00:12:53.920> you<00:12:54.000> know<00:12:54.120> with<00:12:54.240> a<00:12:54.360> card<00:12:54.639> attached 00:12:54.949 --> 00:12:54.959 align:start position:0% spend it you know with a card attached 00:12:54.959 --> 00:12:57.509 align:start position:0% spend it you know with a card attached to<00:12:55.160> the<00:12:55.360> account<00:12:56.360> anywhere<00:12:57.240> you<00:12:57.360> know 00:12:57.509 --> 00:12:57.519 align:start position:0% to the account anywhere you know 00:12:57.519 --> 00:12:59.710 align:start position:0% to the account anywhere you know merchants<00:12:57.959> accept<00:12:58.240> card 00:12:59.710 --> 00:12:59.720 align:start position:0% merchants accept card 00:12:59.720 --> 00:13:01.069 align:start position:0% merchants accept card so<00:12:59.880> that's<00:13:00.000> a<00:13:00.279> really<00:13:00.440> cool<00:13:00.639> Trend<00:13:00.920> we're 00:13:01.069 --> 00:13:01.079 align:start position:0% so that's a really cool Trend we're 00:13:01.079 --> 00:13:04.829 align:start position:0% so that's a really cool Trend we're seeing<00:13:01.920> another<00:13:02.560> is<00:13:03.560> that<00:13:03.800> mainstream<00:13:04.519> apps 00:13:04.829 --> 00:13:04.839 align:start position:0% seeing another is that mainstream apps 00:13:04.839 --> 00:13:07.750 align:start position:0% seeing another is that mainstream apps are<00:13:05.320> are<00:13:05.440> starting<00:13:05.760> to<00:13:05.959> use<00:13:06.279> crypto<00:13:07.000> as<00:13:07.519> just<00:13:07.639> a 00:13:07.750 --> 00:13:07.760 align:start position:0% are are starting to use crypto as just a 00:13:07.760 --> 00:13:10.150 align:start position:0% are are starting to use crypto as just a more<00:13:08.079> efficient<00:13:08.639> payment<00:13:08.959> and<00:13:09.160> rail<00:13:09.880> so<00:13:10.040> this 00:13:10.150 --> 00:13:10.160 align:start position:0% more efficient payment and rail so this 00:13:10.160 --> 00:13:12.389 align:start position:0% more efficient payment and rail so this is<00:13:10.279> an<00:13:10.480> announcement<00:13:11.000> from<00:13:11.160> deal<00:13:11.680> the<00:13:11.880> payroll 00:13:12.389 --> 00:13:12.399 align:start position:0% is an announcement from deal the payroll 00:13:12.399 --> 00:13:15.069 align:start position:0% is an announcement from deal the payroll company<00:13:13.240> which<00:13:13.399> allows<00:13:14.120> any<00:13:14.360> contractor<00:13:14.880> on 00:13:15.069 --> 00:13:15.079 align:start position:0% company which allows any contractor on 00:13:15.079 --> 00:13:19.790 align:start position:0% company which allows any contractor on the<00:13:15.480> platform<00:13:15.920> to<00:13:16.160> accept<00:13:16.440> their<00:13:16.920> payroll<00:13:18.120> in 00:13:19.790 --> 00:13:19.800 align:start position:0% the platform to accept their payroll in 00:13:19.800 --> 00:13:25.230 align:start position:0% the platform to accept their payroll in usdc<00:13:20.880> and<00:13:21.880> so<00:13:22.880> not<00:13:23.320> only<00:13:23.959> are<00:13:24.680> you<00:13:24.800> know 00:13:25.230 --> 00:13:25.240 align:start position:0% usdc and so not only are you know 00:13:25.240 --> 00:13:27.310 align:start position:0% usdc and so not only are you know contractors<00:13:25.880> getting<00:13:26.320> faster<00:13:26.760> access<00:13:27.000> to<00:13:27.160> the 00:13:27.310 --> 00:13:27.320 align:start position:0% contractors getting faster access to the 00:13:27.320 --> 00:13:29.310 align:start position:0% contractors getting faster access to the payment<00:13:27.800> but<00:13:28.199> they're<00:13:28.399> not<00:13:28.560> dealing<00:13:28.920> with<00:13:29.199> a 00:13:29.310 --> 00:13:29.320 align:start position:0% payment but they're not dealing with a 00:13:29.320 --> 00:13:32.189 align:start position:0% payment but they're not dealing with a lot<00:13:29.440> of<00:13:29.639> the<00:13:30.040> kind<00:13:30.160> of<00:13:30.320> big<00:13:30.519> FX<00:13:31.040> hits<00:13:31.560> you<00:13:31.800> take 00:13:32.189 --> 00:13:32.199 align:start position:0% lot of the kind of big FX hits you take 00:13:32.199 --> 00:13:35.230 align:start position:0% lot of the kind of big FX hits you take on<00:13:32.480> both<00:13:32.720> sides<00:13:32.920> of<00:13:33.079> the<00:13:33.639> transaction<00:13:34.639> uh<00:13:34.839> if 00:13:35.230 --> 00:13:35.240 align:start position:0% on both sides of the transaction uh if 00:13:35.240 --> 00:13:38.150 align:start position:0% on both sides of the transaction uh if you<00:13:35.360> know<00:13:35.519> you<00:13:35.600> were<00:13:36.000> converting<00:13:36.959> from<00:13:37.959> uh 00:13:38.150 --> 00:13:38.160 align:start position:0% you know you were converting from uh 00:13:38.160 --> 00:13:41.670 align:start position:0% you know you were converting from uh payment<00:13:38.480> in<00:13:38.720> USD<00:13:39.760> to<00:13:40.760> you<00:13:40.880> know<00:13:41.199> a<00:13:41.320> foreign 00:13:41.670 --> 00:13:41.680 align:start position:0% payment in USD to you know a foreign 00:13:41.680 --> 00:13:45.189 align:start position:0% payment in USD to you know a foreign currency<00:13:42.240> and<00:13:43.000> the<00:13:43.160> bank<00:13:43.839> would<00:13:44.839> you<00:13:45.000> know 00:13:45.189 --> 00:13:45.199 align:start position:0% currency and the bank would you know 00:13:45.199 --> 00:13:47.189 align:start position:0% currency and the bank would you know take<00:13:45.360> a<00:13:45.480> pretty<00:13:45.680> big<00:13:45.839> fee<00:13:46.079> on<00:13:46.199> the<00:13:46.279> FX 00:13:47.189 --> 00:13:47.199 align:start position:0% take a pretty big fee on the FX 00:13:47.199 --> 00:13:49.590 align:start position:0% take a pretty big fee on the FX conversion<00:13:48.199> so<00:13:48.360> that's<00:13:48.519> a<00:13:48.680> really<00:13:49.160> exciting 00:13:49.590 --> 00:13:49.600 align:start position:0% conversion so that's a really exciting 00:13:49.600 --> 00:13:51.949 align:start position:0% conversion so that's a really exciting Trend<00:13:49.920> as<00:13:50.040> well<00:13:50.800> and<00:13:50.920> then<00:13:51.079> the<00:13:51.240> last<00:13:51.480> Trend 00:13:51.949 --> 00:13:51.959 align:start position:0% Trend as well and then the last Trend 00:13:51.959 --> 00:13:55.389 align:start position:0% Trend as well and then the last Trend we're<00:13:52.480> seeing<00:13:53.480> with<00:13:54.040> mainstream<00:13:55.000> products 00:13:55.389 --> 00:13:55.399 align:start position:0% we're seeing with mainstream products 00:13:55.399 --> 00:13:57.749 align:start position:0% we're seeing with mainstream products and<00:13:55.639> experiences<00:13:56.480> building<00:13:56.800> on<00:13:56.959> crypto<00:13:57.320> rails 00:13:57.749 --> 00:13:57.759 align:start position:0% and experiences building on crypto rails 00:13:57.759 --> 00:13:59.990 align:start position:0% and experiences building on crypto rails is<00:13:58.240> some<00:13:58.360> of<00:13:58.480> the<00:13:58.560> inter<00:13:59.240> ability<00:13:59.600> you 00:13:59.990 --> 00:14:00.000 align:start position:0% is some of the inter ability you 00:14:00.000 --> 00:14:02.350 align:start position:0% is some of the inter ability you benefits<00:14:00.440> you<00:14:00.639> get<00:14:00.839> from<00:14:01.000> building<00:14:01.320> on<00:14:01.519> chain 00:14:02.350 --> 00:14:02.360 align:start position:0% benefits you get from building on chain 00:14:02.360 --> 00:14:03.990 align:start position:0% benefits you get from building on chain so<00:14:02.560> earlier<00:14:02.959> this<00:14:03.079> year<00:14:03.279> at 00:14:03.990 --> 00:14:04.000 align:start position:0% so earlier this year at 00:14:04.000 --> 00:14:07.150 align:start position:0% so earlier this year at Coachella<00:14:05.000> users<00:14:05.399> who<00:14:05.680> had<00:14:06.160> specific<00:14:06.759> assets 00:14:07.150 --> 00:14:07.160 align:start position:0% Coachella users who had specific assets 00:14:07.160 --> 00:14:09.710 align:start position:0% Coachella users who had specific assets that<00:14:07.320> they<00:14:07.440> bought<00:14:07.759> on<00:14:08.199> openc<00:14:09.199> could<00:14:09.360> then<00:14:09.560> go 00:14:09.710 --> 00:14:09.720 align:start position:0% that they bought on openc could then go 00:14:09.720 --> 00:14:14.189 align:start position:0% that they bought on openc could then go on<00:14:09.880> to<00:14:10.040> the<00:14:10.160> Coachella<00:14:10.880> website<00:14:12.240> and<00:14:13.240> Link<00:14:14.000> um 00:14:14.189 --> 00:14:14.199 align:start position:0% on to the Coachella website and Link um 00:14:14.199 --> 00:14:16.550 align:start position:0% on to the Coachella website and Link um link<00:14:14.480> the<00:14:14.639> same<00:14:14.920> wallet<00:14:15.320> they<00:14:15.480> used<00:14:15.800> to 00:14:16.550 --> 00:14:16.560 align:start position:0% link the same wallet they used to 00:14:16.560 --> 00:14:20.710 align:start position:0% link the same wallet they used to buy<00:14:17.560> the<00:14:17.920> assets<00:14:18.240> on<00:14:18.440> openc<00:14:19.399> and<00:14:19.800> unlock<00:14:20.240> VIP 00:14:20.710 --> 00:14:20.720 align:start position:0% buy the assets on openc and unlock VIP 00:14:20.720 --> 00:14:22.629 align:start position:0% buy the assets on openc and unlock VIP passes<00:14:21.079> and<00:14:21.199> there<00:14:21.320> was<00:14:21.440> a<00:14:21.600> special<00:14:22.360> kind<00:14:22.480> of 00:14:22.629 --> 00:14:22.639 align:start position:0% passes and there was a special kind of 00:14:22.639 --> 00:14:25.389 align:start position:0% passes and there was a special kind of section<00:14:23.279> of<00:14:23.519> the<00:14:23.759> Coachella<00:14:24.360> venue<00:14:25.079> where 00:14:25.389 --> 00:14:25.399 align:start position:0% section of the Coachella venue where 00:14:25.399 --> 00:14:27.590 align:start position:0% section of the Coachella venue where users<00:14:25.759> could<00:14:26.000> go<00:14:26.240> and<00:14:26.800> you<00:14:26.920> know<00:14:27.079> get<00:14:27.320> access 00:14:27.590 --> 00:14:27.600 align:start position:0% users could go and you know get access 00:14:27.600 --> 00:14:30.189 align:start position:0% users could go and you know get access if<00:14:27.759> they<00:14:27.959> had<00:14:28.600> this<00:14:28.759> NF<00:14:29.399> in<00:14:29.560> their<00:14:29.839> in<00:14:29.959> their 00:14:30.189 --> 00:14:30.199 align:start position:0% if they had this NF in their in their 00:14:30.199 --> 00:14:32.910 align:start position:0% if they had this NF in their in their wallet<00:14:31.199> and<00:14:31.320> this<00:14:31.399> is<00:14:31.600> like<00:14:31.720> a<00:14:31.880> very<00:14:32.199> early 00:14:32.910 --> 00:14:32.920 align:start position:0% wallet and this is like a very early 00:14:32.920 --> 00:14:35.829 align:start position:0% wallet and this is like a very early example<00:14:33.720> of<00:14:33.959> some<00:14:34.120> of<00:14:34.360> the<00:14:35.040> Cross<00:14:35.480> app 00:14:35.829 --> 00:14:35.839 align:start position:0% example of some of the Cross app 00:14:35.839 --> 00:14:40.230 align:start position:0% example of some of the Cross app experiences<00:14:36.800> where<00:14:37.639> users<00:14:38.160> can<00:14:39.040> users<00:14:39.440> can 00:14:40.230 --> 00:14:40.240 align:start position:0% experiences where users can users can 00:14:40.240 --> 00:14:42.710 align:start position:0% experiences where users can users can take<00:14:41.079> history<00:14:41.560> or<00:14:41.759> purchases<00:14:42.240> they've<00:14:42.440> made 00:14:42.710 --> 00:14:42.720 align:start position:0% take history or purchases they've made 00:14:42.720 --> 00:14:45.150 align:start position:0% take history or purchases they've made in<00:14:42.959> in<00:14:43.120> one<00:14:43.440> crypto<00:14:44.240> app<00:14:44.440> or<00:14:44.639> one<00:14:44.759> thing<00:14:44.920> on 00:14:45.150 --> 00:14:45.160 align:start position:0% in in one crypto app or one thing on 00:14:45.160 --> 00:14:49.509 align:start position:0% in in one crypto app or one thing on chain<00:14:45.639> and<00:14:46.360> unlock<00:14:46.880> things<00:14:47.600> completely 00:14:49.509 --> 00:14:49.519 align:start position:0% chain and unlock things completely 00:14:49.519 --> 00:14:52.069 align:start position:0% chain and unlock things completely elsewhere<00:14:50.519> so<00:14:50.680> the<00:14:50.800> two<00:14:51.040> trends<00:14:51.519> that<00:14:51.639> we're 00:14:52.069 --> 00:14:52.079 align:start position:0% elsewhere so the two trends that we're 00:14:52.079 --> 00:14:53.670 align:start position:0% elsewhere so the two trends that we're really<00:14:52.399> excited<00:14:52.800> about<00:14:53.079> that<00:14:53.199> we<00:14:53.320> think<00:14:53.480> will 00:14:53.670 --> 00:14:53.680 align:start position:0% really excited about that we think will 00:14:53.680 --> 00:14:57.150 align:start position:0% really excited about that we think will unlock<00:14:54.480> the<00:14:54.680> next<00:14:54.959> wave<00:14:55.279> of<00:14:55.519> crypto<00:14:55.880> usage<00:14:56.480> are 00:14:57.150 --> 00:14:57.160 align:start position:0% unlock the next wave of crypto usage are 00:14:57.160 --> 00:15:01.470 align:start position:0% unlock the next wave of crypto usage are one<00:14:58.160> you<00:14:58.320> know<00:14:58.519> these<00:14:59.279> very<00:14:59.920> kind<00:15:00.040> of<00:15:00.199> crypto 00:15:01.470 --> 00:15:01.480 align:start position:0% one you know these very kind of crypto 00:15:01.480 --> 00:15:05.269 align:start position:0% one you know these very kind of crypto deliberate<00:15:02.519> products<00:15:03.519> that<00:15:03.839> are<00:15:04.839> finding 00:15:05.269 --> 00:15:05.279 align:start position:0% deliberate products that are finding 00:15:05.279 --> 00:15:08.670 align:start position:0% deliberate products that are finding ways<00:15:05.720> to<00:15:06.480> attract<00:15:07.440> uh<00:15:07.600> mainstream<00:15:08.079> user<00:15:08.360> base 00:15:08.670 --> 00:15:08.680 align:start position:0% ways to attract uh mainstream user base 00:15:08.680 --> 00:15:10.670 align:start position:0% ways to attract uh mainstream user base with<00:15:08.839> poly<00:15:09.160> Market<00:15:09.480> as<00:15:09.600> like<00:15:09.720> a<00:15:09.880> great<00:15:10.120> example 00:15:10.670 --> 00:15:10.680 align:start position:0% with poly Market as like a great example 00:15:10.680 --> 00:15:12.350 align:start position:0% with poly Market as like a great example of<00:15:10.920> this<00:15:11.639> we<00:15:11.759> think<00:15:11.920> that's<00:15:12.120> going<00:15:12.199> to 00:15:12.350 --> 00:15:12.360 align:start position:0% of this we think that's going to 00:15:12.360 --> 00:15:14.710 align:start position:0% of this we think that's going to continue<00:15:13.240> accelerating<00:15:14.240> and<00:15:14.320> then<00:15:14.480> on<00:15:14.600> the 00:15:14.710 --> 00:15:14.720 align:start position:0% continue accelerating and then on the 00:15:14.720 --> 00:15:16.590 align:start position:0% continue accelerating and then on the other<00:15:14.920> hand<00:15:15.240> you<00:15:15.480> have<00:15:15.959> all<00:15:16.120> of<00:15:16.320> these 00:15:16.590 --> 00:15:16.600 align:start position:0% other hand you have all of these 00:15:16.600 --> 00:15:20.069 align:start position:0% other hand you have all of these products<00:15:17.560> fintech<00:15:18.199> and<00:15:18.519> and<00:15:19.040> largely<00:15:19.440> fintech 00:15:20.069 --> 00:15:20.079 align:start position:0% products fintech and and largely fintech 00:15:20.079 --> 00:15:22.790 align:start position:0% products fintech and and largely fintech but<00:15:20.680> over<00:15:20.959> time<00:15:21.160> we<00:15:21.320> expect<00:15:21.639> many<00:15:21.880> more<00:15:22.680> that 00:15:22.790 --> 00:15:22.800 align:start position:0% but over time we expect many more that 00:15:22.800 --> 00:15:25.990 align:start position:0% but over time we expect many more that are<00:15:23.519> looking<00:15:23.759> to<00:15:24.000> build<00:15:24.480> on<00:15:24.880> crypto<00:15:25.279> rails<00:15:25.759> to 00:15:25.990 --> 00:15:26.000 align:start position:0% are looking to build on crypto rails to 00:15:26.000 --> 00:15:28.350 align:start position:0% are looking to build on crypto rails to unlock<00:15:27.000> some<00:15:27.160> of<00:15:27.279> the<00:15:27.399> interoperability<00:15:28.199> and 00:15:28.350 --> 00:15:28.360 align:start position:0% unlock some of the interoperability and 00:15:28.360 --> 00:15:31.790 align:start position:0% unlock some of the interoperability and payment<00:15:28.680> benefit<00:15:29.279> you<00:15:29.880> get<00:15:30.880> and<00:15:31.000> in<00:15:31.160> our<00:15:31.360> view 00:15:31.790 --> 00:15:31.800 align:start position:0% payment benefit you get and in our view 00:15:31.800 --> 00:15:35.069 align:start position:0% payment benefit you get and in our view these<00:15:32.680> are<00:15:33.079> Moment<00:15:33.360> In<00:15:33.639> Time 00:15:35.069 --> 00:15:35.079 align:start position:0% these are Moment In Time 00:15:35.079 --> 00:15:37.870 align:start position:0% these are Moment In Time distinctions<00:15:36.240> eventually<00:15:37.240> you<00:15:37.399> know<00:15:37.680> we're 00:15:37.870 --> 00:15:37.880 align:start position:0% distinctions eventually you know we're 00:15:37.880 --> 00:15:39.590 align:start position:0% distinctions eventually you know we're just<00:15:38.040> going<00:15:38.160> to<00:15:38.360> talk<00:15:38.519> about<00:15:38.800> crypto<00:15:39.240> as<00:15:39.440> an 00:15:39.590 --> 00:15:39.600 align:start position:0% just going to talk about crypto as an 00:15:39.600 --> 00:15:42.350 align:start position:0% just going to talk about crypto as an enabling<00:15:40.360> technology<00:15:41.160> that<00:15:41.399> products<00:15:41.759> build 00:15:42.350 --> 00:15:42.360 align:start position:0% enabling technology that products build 00:15:42.360 --> 00:15:45.230 align:start position:0% enabling technology that products build on<00:15:43.360> and<00:15:43.480> so<00:15:43.800> this<00:15:44.079> you<00:15:44.199> know<00:15:44.360> Crypton<00:15:44.720> native 00:15:45.230 --> 00:15:45.240 align:start position:0% on and so this you know Crypton native 00:15:45.240 --> 00:15:47.870 align:start position:0% on and so this you know Crypton native vers<00:15:45.839> mainstream<00:15:46.680> product<00:15:47.040> is<00:15:47.160> a<00:15:47.279> very<00:15:47.519> moment 00:15:47.870 --> 00:15:47.880 align:start position:0% vers mainstream product is a very moment 00:15:47.880 --> 00:15:49.790 align:start position:0% vers mainstream product is a very moment in<00:15:48.160> time<00:15:48.560> distinction<00:15:49.120> we<00:15:49.240> think<00:15:49.560> you<00:15:49.639> know 00:15:49.790 --> 00:15:49.800 align:start position:0% in time distinction we think you know 00:15:49.800 --> 00:15:52.030 align:start position:0% in time distinction we think you know these<00:15:49.959> two<00:15:50.120> Trends<00:15:50.480> will<00:15:51.240> converge<00:15:51.800> and 00:15:52.030 --> 00:15:52.040 align:start position:0% these two Trends will converge and 00:15:52.040 --> 00:15:54.230 align:start position:0% these two Trends will converge and everyone<00:15:52.560> will<00:15:53.120> start<00:15:53.399> building<00:15:53.720> on<00:15:53.880> crypto 00:15:54.230 --> 00:15:54.240 align:start position:0% everyone will start building on crypto 00:15:54.240 --> 00:15:57.350 align:start position:0% everyone will start building on crypto rails<00:15:54.720> in<00:15:54.839> order<00:15:55.120> to<00:15:55.800> access<00:15:56.560> the<00:15:56.720> things<00:15:57.160> you 00:15:57.350 --> 00:15:57.360 align:start position:0% rails in order to access the things you 00:15:57.360 --> 00:16:00.550 align:start position:0% rails in order to access the things you get<00:15:57.560> that<00:15:57.680> make<00:15:57.839> crypto<00:15:58.279> special 00:16:00.550 --> 00:16:00.560 align:start position:0% get that make crypto special 00:16:00.560 --> 00:16:02.670 align:start position:0% get that make crypto special we<00:16:00.759> think<00:16:01.079> kind<00:16:01.199> of<00:16:01.440> as<00:16:01.639> that<00:16:01.839> plays<00:16:02.120> out<00:16:02.480> it's 00:16:02.670 --> 00:16:02.680 align:start position:0% we think kind of as that plays out it's 00:16:02.680 --> 00:16:04.150 align:start position:0% we think kind of as that plays out it's important 00:16:04.150 --> 00:16:04.160 align:start position:0% important 00:16:04.160 --> 00:16:07.749 align:start position:0% important to<00:16:05.160> keep<00:16:05.399> your<00:16:05.880> keep<00:16:06.040> your<00:16:06.240> focus<00:16:06.639> on<00:16:07.639> the 00:16:07.749 --> 00:16:07.759 align:start position:0% to keep your keep your focus on the 00:16:07.759 --> 00:16:09.710 align:start position:0% to keep your keep your focus on the things<00:16:08.000> we<00:16:08.199> get<00:16:08.360> from<00:16:08.600> crypto<00:16:09.160> and<00:16:09.440> what<00:16:09.560> we're 00:16:09.710 --> 00:16:09.720 align:start position:0% things we get from crypto and what we're 00:16:09.720 --> 00:16:11.550 align:start position:0% things we get from crypto and what we're all<00:16:09.880> building<00:16:10.279> toward<00:16:10.680> and 00:16:11.550 --> 00:16:11.560 align:start position:0% all building toward and 00:16:11.560 --> 00:16:14.150 align:start position:0% all building toward and not<00:16:12.560> you<00:16:12.639> know<00:16:12.800> concern<00:16:13.240> ourselves<00:16:13.680> with<00:16:14.000> okay 00:16:14.150 --> 00:16:14.160 align:start position:0% not you know concern ourselves with okay 00:16:14.160 --> 00:16:17.110 align:start position:0% not you know concern ourselves with okay I<00:16:14.279> believe<00:16:14.600> crypto<00:16:14.959> needs<00:16:15.160> to<00:16:15.399> evolve<00:16:16.000> in<00:16:17.000> you 00:16:17.110 --> 00:16:17.120 align:start position:0% I believe crypto needs to evolve in you 00:16:17.120 --> 00:16:19.749 align:start position:0% I believe crypto needs to evolve in you know<00:16:17.319> whether<00:16:17.600> it's<00:16:17.959> this<00:16:18.160> chain<00:16:18.720> or<00:16:19.600> this 00:16:19.749 --> 00:16:19.759 align:start position:0% know whether it's this chain or this 00:16:19.759 --> 00:16:22.030 align:start position:0% know whether it's this chain or this user<00:16:20.079> base<00:16:20.440> or<00:16:20.639> that<00:16:20.839> user<00:16:21.120> base<00:16:21.480> and<00:16:21.800> just 00:16:22.030 --> 00:16:22.040 align:start position:0% user base or that user base and just 00:16:22.040 --> 00:16:24.430 align:start position:0% user base or that user base and just really<00:16:22.319> focus<00:16:22.800> on<00:16:23.800> what<00:16:23.880> are<00:16:24.040> the<00:16:24.160> unique 00:16:24.430 --> 00:16:24.440 align:start position:0% really focus on what are the unique 00:16:24.440 --> 00:16:26.870 align:start position:0% really focus on what are the unique benefits<00:16:24.880> we<00:16:25.000> get<00:16:25.160> from<00:16:25.319> building<00:16:25.560> on<00:16:25.759> crypto 00:16:26.870 --> 00:16:26.880 align:start position:0% benefits we get from building on crypto 00:16:26.880 --> 00:16:29.189 align:start position:0% benefits we get from building on crypto rails<00:16:27.880> and<00:16:28.199> you<00:16:28.279> know<00:16:28.440> the<00:16:28.560> last<00:16:28.720> thing 00:16:29.189 --> 00:16:29.199 align:start position:0% rails and you know the last thing 00:16:29.199 --> 00:16:31.749 align:start position:0% rails and you know the last thing will'll<00:16:29.800> leave<00:16:30.160> with<00:16:30.480> is<00:16:31.160> you<00:16:31.399> we<00:16:31.560> really 00:16:31.749 --> 00:16:31.759 align:start position:0% will'll leave with is you we really 00:16:31.759 --> 00:16:34.030 align:start position:0% will'll leave with is you we really believe<00:16:32.040> there's<00:16:32.319> never<00:16:32.839> been<00:16:33.240> a<00:16:33.399> better<00:16:33.720> time 00:16:34.030 --> 00:16:34.040 align:start position:0% believe there's never been a better time 00:16:34.040 --> 00:16:36.350 align:start position:0% believe there's never been a better time to<00:16:34.160> be<00:16:34.319> building<00:16:34.839> products<00:16:35.120> on<00:16:35.319> chain<00:16:36.199> you 00:16:36.350 --> 00:16:36.360 align:start position:0% to be building products on chain you 00:16:36.360 --> 00:16:38.790 align:start position:0% to be building products on chain you have<00:16:36.519> all<00:16:36.800> the<00:16:37.160> infrastructure<00:16:37.839> coming 00:16:38.790 --> 00:16:38.800 align:start position:0% have all the infrastructure coming 00:16:38.800 --> 00:16:41.749 align:start position:0% have all the infrastructure coming together<00:16:39.800> you<00:16:40.000> have<00:16:40.759> all<00:16:40.920> of<00:16:41.040> the<00:16:41.199> energy 00:16:41.749 --> 00:16:41.759 align:start position:0% together you have all of the energy 00:16:41.759 --> 00:16:43.430 align:start position:0% together you have all of the energy behind<00:16:42.079> crypto<00:16:42.519> the<00:16:42.639> visibility<00:16:43.279> we're 00:16:43.430 --> 00:16:43.440 align:start position:0% behind crypto the visibility we're 00:16:43.440 --> 00:16:46.069 align:start position:0% behind crypto the visibility we're getting<00:16:43.720> as<00:16:43.839> a<00:16:44.240> market<00:16:45.240> and<00:16:45.600> we're<00:16:45.839> really 00:16:46.069 --> 00:16:46.079 align:start position:0% getting as a market and we're really 00:16:46.079 --> 00:16:48.269 align:start position:0% getting as a market and we're really excited<00:16:46.440> to<00:16:46.560> see<00:16:47.079> the<00:16:47.240> next<00:16:47.440> wave<00:16:47.639> of<00:16:47.839> products 00:16:48.269 --> 00:16:48.279 align:start position:0% excited to see the next wave of products 00:16:48.279 --> 00:16:50.590 align:start position:0% excited to see the next wave of products that<00:16:48.519> that<00:16:48.720> come<00:16:49.600> so<00:16:49.800> thank<00:16:49.920> you<00:16:50.120> all<00:16:50.399> very 00:16:50.590 --> 00:16:50.600 align:start position:0% that that come so thank you all very 00:16:50.600 --> 00:16:53.829 align:start position:0% that that come so thank you all very much<00:16:50.920> for<00:16:51.440> the<00:16:51.880> time<00:16:52.880> and<00:16:53.240> if<00:16:53.360> there<00:16:53.480> are<00:16:53.639> any 00:16:53.829 --> 00:16:53.839 align:start position:0% much for the time and if there are any 00:16:53.839 --> 00:16:58.949 align:start position:0% much for the time and if there are any questions<00:16:54.319> happy<00:16:54.720> to<00:16:54.920> take<00:16:55.160> them 00:16:58.949 --> 00:16:58.959 align:start position:0% 00:16:58.959 --> 00:17:00.790 align:start position:0% Thanks<00:16:59.240> Max<00:16:59.600> I<00:16:59.720> hope<00:16:59.959> everyone<00:17:00.319> took<00:17:00.600> some 00:17:00.790 --> 00:17:00.800 align:start position:0% Thanks Max I hope everyone took some 00:17:00.800 --> 00:17:04.270 align:start position:0% Thanks Max I hope everyone took some notes<00:17:01.399> on<00:17:01.600> how<00:17:01.720> to<00:17:01.839> build<00:17:02.120> a<00:17:02.720> popular<00:17:03.280> product 00:17:04.270 --> 00:17:04.280 align:start position:0% notes on how to build a popular product 00:17:04.280 --> 00:17:06.429 align:start position:0% notes on how to build a popular product so<00:17:04.679> without<00:17:04.919> further<00:17:05.240> Ado<00:17:05.520> let's<00:17:05.880> go<00:17:06.199> talk 00:17:06.429 --> 00:17:06.439 align:start position:0% so without further Ado let's go talk 00:17:06.439 --> 00:17:07.789 align:start position:0% so without further Ado let's go talk about<00:17:06.600> some<00:17:06.760> of<00:17:06.919> the<00:17:07.079> questions<00:17:07.439> so<00:17:07.559> we<00:17:07.679> can 00:17:07.789 --> 00:17:07.799 align:start position:0% about some of the questions so we can 00:17:07.799 --> 00:17:09.510 align:start position:0% about some of the questions so we can look<00:17:08.000> right<00:17:08.160> here<00:17:08.400> the<00:17:08.520> first<00:17:08.720> one<00:17:09.000> is<00:17:09.240> what<00:17:09.400> is 00:17:09.510 --> 00:17:09.520 align:start position:0% look right here the first one is what is 00:17:09.520 --> 00:17:11.590 align:start position:0% look right here the first one is what is an<00:17:09.839> example<00:17:10.439> of<00:17:10.559> a<00:17:10.760> popular<00:17:11.120> feature<00:17:11.480> that 00:17:11.590 --> 00:17:11.600 align:start position:0% an example of a popular feature that 00:17:11.600 --> 00:17:15.029 align:start position:0% an example of a popular feature that drove<00:17:12.000> massive<00:17:12.439> adoption<00:17:12.919> for<00:17:13.120> a 00:17:15.029 --> 00:17:15.039 align:start position:0% drove massive adoption for a 00:17:15.039 --> 00:17:17.029 align:start position:0% drove massive adoption for a project 00:17:17.029 --> 00:17:17.039 align:start position:0% project 00:17:17.039 --> 00:17:22.110 align:start position:0% project yeah<00:17:18.039> one<00:17:18.640> of<00:17:19.640> the<00:17:20.280> most<00:17:21.280> kind<00:17:21.400> of<00:17:21.600> Novel 00:17:22.110 --> 00:17:22.120 align:start position:0% yeah one of the most kind of Novel 00:17:22.120 --> 00:17:24.990 align:start position:0% yeah one of the most kind of Novel things<00:17:22.679> we<00:17:23.000> saw<00:17:23.640> in<00:17:24.120> a 00:17:24.990 --> 00:17:25.000 align:start position:0% things we saw in a 00:17:25.000 --> 00:17:28.870 align:start position:0% things we saw in a product<00:17:26.000> since<00:17:26.280> starting<00:17:26.640> privy<00:17:27.400> was<00:17:28.000> how 00:17:28.870 --> 00:17:28.880 align:start position:0% product since starting privy was how 00:17:28.880 --> 00:17:31.510 align:start position:0% product since starting privy was how friendch<00:17:29.480> really<00:17:29.720> leaned<00:17:30.160> into<00:17:30.919> an<00:17:31.120> existing 00:17:31.510 --> 00:17:31.520 align:start position:0% friendch really leaned into an existing 00:17:31.520 --> 00:17:35.590 align:start position:0% friendch really leaned into an existing social<00:17:32.000> graph<00:17:32.400> to<00:17:32.600> make<00:17:33.480> the<00:17:33.679> first<00:17:34.039> time<00:17:34.559> user 00:17:35.590 --> 00:17:35.600 align:start position:0% social graph to make the first time user 00:17:35.600 --> 00:17:38.870 align:start position:0% social graph to make the first time user experience<00:17:36.600> a<00:17:36.880> much<00:17:37.200> richer<00:17:37.720> experience<00:17:38.720> um 00:17:38.870 --> 00:17:38.880 align:start position:0% experience a much richer experience um 00:17:38.880 --> 00:17:42.270 align:start position:0% experience a much richer experience um you<00:17:39.000> had<00:17:39.120> a<00:17:39.280> bootstrapped<00:17:40.280> so<00:17:41.160> to<00:17:41.400> to<00:17:41.840> rewind 00:17:42.270 --> 00:17:42.280 align:start position:0% you had a bootstrapped so to to rewind 00:17:42.280 --> 00:17:45.630 align:start position:0% you had a bootstrapped so to to rewind for<00:17:42.440> a<00:17:42.600> second<00:17:43.440> frch<00:17:44.320> when<00:17:44.480> you<00:17:44.600> signed<00:17:45.039> up 00:17:45.630 --> 00:17:45.640 align:start position:0% for a second frch when you signed up 00:17:45.640 --> 00:17:47.909 align:start position:0% for a second frch when you signed up asked<00:17:46.000> users<00:17:46.440> to<00:17:46.720> link<00:17:47.000> their<00:17:47.160> Twitter 00:17:47.909 --> 00:17:47.919 align:start position:0% asked users to link their Twitter 00:17:47.919 --> 00:17:50.750 align:start position:0% asked users to link their Twitter accounts<00:17:48.919> and<00:17:49.000> then<00:17:49.160> there<00:17:49.240> was<00:17:49.360> a<00:17:49.760> populated 00:17:50.750 --> 00:17:50.760 align:start position:0% accounts and then there was a populated 00:17:50.760 --> 00:17:53.470 align:start position:0% accounts and then there was a populated social<00:17:51.200> graph<00:17:51.960> and<00:17:52.520> you<00:17:52.640> know<00:17:52.880> users<00:17:53.320> that<00:17:53.400> you 00:17:53.470 --> 00:17:53.480 align:start position:0% social graph and you know users that you 00:17:53.480 --> 00:17:57.190 align:start position:0% social graph and you know users that you were<00:17:53.720> familiar<00:17:54.480> with<00:17:55.480> and<00:17:56.159> that<00:17:56.880> kind<00:17:57.000> of 00:17:57.190 --> 00:17:57.200 align:start position:0% were familiar with and that kind of 00:17:57.200 --> 00:17:59.870 align:start position:0% were familiar with and that kind of immediately<00:17:57.880> gave<00:17:58.440> the<00:17:58.600> app<00:17:59.080> experience<00:17:59.679> some 00:17:59.870 --> 00:17:59.880 align:start position:0% immediately gave the app experience some 00:17:59.880 --> 00:18:02.350 align:start position:0% immediately gave the app experience some more<00:18:00.400> life<00:18:00.760> you<00:18:01.000> had<00:18:01.600> kind<00:18:01.720> of<00:18:01.840> friends<00:18:02.159> and 00:18:02.350 --> 00:18:02.360 align:start position:0% more life you had kind of friends and 00:18:02.360 --> 00:18:05.909 align:start position:0% more life you had kind of friends and recognizable<00:18:03.000> faces<00:18:03.400> on<00:18:03.559> the<00:18:03.960> app<00:18:04.960> and<00:18:05.799> I 00:18:05.909 --> 00:18:05.919 align:start position:0% recognizable faces on the app and I 00:18:05.919 --> 00:18:08.990 align:start position:0% recognizable faces on the app and I think<00:18:06.200> that<00:18:06.320> is<00:18:06.480> one<00:18:06.640> of<00:18:07.120> the<00:18:08.120> patterns<00:18:08.760> that 00:18:08.990 --> 00:18:09.000 align:start position:0% think that is one of the patterns that 00:18:09.000 --> 00:18:10.990 align:start position:0% think that is one of the patterns that that<00:18:09.159> team<00:18:09.440> introduced<00:18:10.159> that<00:18:10.559> you<00:18:10.679> know<00:18:10.840> we 00:18:10.990 --> 00:18:11.000 align:start position:0% that team introduced that you know we 00:18:11.000 --> 00:18:15.029 align:start position:0% that team introduced that you know we still<00:18:11.200> see<00:18:11.760> everywhere<00:18:12.440> today<00:18:13.440> that<00:18:14.440> made<00:18:14.840> for 00:18:15.029 --> 00:18:15.039 align:start position:0% still see everywhere today that made for 00:18:15.039 --> 00:18:18.230 align:start position:0% still see everywhere today that made for a<00:18:15.200> much<00:18:15.400> richer<00:18:16.000> experience<00:18:17.000> agreed<00:18:17.880> so<00:18:18.120> the 00:18:18.230 --> 00:18:18.240 align:start position:0% a much richer experience agreed so the 00:18:18.240 --> 00:18:20.510 align:start position:0% a much richer experience agreed so the next<00:18:18.440> one<00:18:18.640> would<00:18:18.799> be<00:18:19.200> why<00:18:19.480> is<00:18:19.760> most<00:18:20.080> web<00:18:20.320> tree 00:18:20.510 --> 00:18:20.520 align:start position:0% next one would be why is most web tree 00:18:20.520 --> 00:18:22.549 align:start position:0% next one would be why is most web tree adoption<00:18:20.960> focused<00:18:21.320> on<00:18:21.559> speculative<00:18:22.159> platform 00:18:22.549 --> 00:18:22.559 align:start position:0% adoption focused on speculative platform 00:18:22.559 --> 00:18:24.510 align:start position:0% adoption focused on speculative platform like<00:18:22.799> poly<00:18:23.080> markets<00:18:23.400> or<00:18:23.520> mcoin<00:18:24.039> is<00:18:24.159> the<00:18:24.280> trend 00:18:24.510 --> 00:18:24.520 align:start position:0% like poly markets or mcoin is the trend 00:18:24.520 --> 00:18:26.430 align:start position:0% like poly markets or mcoin is the trend overshadowed<00:18:25.520> the<00:18:25.679> development<00:18:26.080> of<00:18:26.200> real 00:18:26.430 --> 00:18:26.440 align:start position:0% overshadowed the development of real 00:18:26.440 --> 00:18:29.789 align:start position:0% overshadowed the development of real world<00:18:26.679> utility<00:18:27.120> in<00:18:27.240> the<00:18:27.360> web<00:18:27.559> tree<00:18:27.880> space 00:18:29.789 --> 00:18:29.799 align:start position:0% world utility in the web tree space 00:18:29.799 --> 00:18:32.029 align:start position:0% world utility in the web tree space yeah<00:18:30.720> well 00:18:32.029 --> 00:18:32.039 align:start position:0% yeah well 00:18:32.039 --> 00:18:37.630 align:start position:0% yeah well because<00:18:33.039> the<00:18:33.320> crypto<00:18:33.720> rails<00:18:34.679> make<00:18:35.159> for<00:18:36.640> easy 00:18:37.630 --> 00:18:37.640 align:start position:0% because the crypto rails make for easy 00:18:37.640 --> 00:18:39.510 align:start position:0% because the crypto rails make for easy transaction 00:18:39.510 --> 00:18:39.520 align:start position:0% transaction 00:18:39.520 --> 00:18:42.029 align:start position:0% transaction experiences<00:18:40.520> you<00:18:40.640> know<00:18:41.080> facilitating 00:18:42.029 --> 00:18:42.039 align:start position:0% experiences you know facilitating 00:18:42.039 --> 00:18:44.870 align:start position:0% experiences you know facilitating whether<00:18:42.320> it's<00:18:42.640> trades<00:18:43.320> or<00:18:43.520> or<00:18:43.679> bets<00:18:44.080> is<00:18:44.320> like<00:18:44.480> a 00:18:44.870 --> 00:18:44.880 align:start position:0% whether it's trades or or bets is like a 00:18:44.880 --> 00:18:48.510 align:start position:0% whether it's trades or or bets is like a very<00:18:45.880> kind<00:18:46.039> of<00:18:46.200> easy<00:18:46.480> to<00:18:46.679> stand<00:18:46.960> up<00:18:47.159> use<00:18:47.520> case 00:18:48.510 --> 00:18:48.520 align:start position:0% very kind of easy to stand up use case 00:18:48.520 --> 00:18:52.470 align:start position:0% very kind of easy to stand up use case we<00:18:48.720> we<00:18:48.880> have<00:18:49.159> a<00:18:50.120> we<00:18:50.240> have<00:18:50.360> a<00:18:50.480> framing<00:18:51.280> at<00:18:51.520> privy 00:18:52.470 --> 00:18:52.480 align:start position:0% we we have a we have a framing at privy 00:18:52.480 --> 00:18:55.669 align:start position:0% we we have a we have a framing at privy uh<00:18:52.919> where<00:18:53.919> there's<00:18:54.200> sort<00:18:54.400> of<00:18:55.159> we<00:18:55.320> we<00:18:55.440> call<00:18:55.559> it 00:18:55.669 --> 00:18:55.679 align:start position:0% uh where there's sort of we we call it 00:18:55.679 --> 00:19:00.390 align:start position:0% uh where there's sort of we we call it the<00:18:55.799> carrot<00:18:56.120> in<00:18:56.280> the<00:18:56.679> stick<00:18:57.679> and<00:18:59.039> up<00:18:59.400> until 00:19:00.390 --> 00:19:00.400 align:start position:0% the carrot in the stick and up until 00:19:00.400 --> 00:19:01.549 align:start position:0% the carrot in the stick and up until very 00:19:01.549 --> 00:19:01.559 align:start position:0% very 00:19:01.559 --> 00:19:03.110 align:start position:0% very recently 00:19:03.110 --> 00:19:03.120 align:start position:0% recently 00:19:03.120 --> 00:19:06.789 align:start position:0% recently because<00:19:04.120> the<00:19:04.559> ux<00:19:05.120> around<00:19:05.440> crypto<00:19:05.880> experiences 00:19:06.789 --> 00:19:06.799 align:start position:0% because the ux around crypto experiences 00:19:06.799 --> 00:19:09.630 align:start position:0% because the ux around crypto experiences was<00:19:07.720> a<00:19:07.840> bit<00:19:08.039> tougher<00:19:08.440> it<00:19:08.520> was<00:19:08.640> a<00:19:08.799> bit<00:19:09.280> kind<00:19:09.400> of 00:19:09.630 --> 00:19:09.640 align:start position:0% was a bit tougher it was a bit kind of 00:19:09.640 --> 00:19:12.870 align:start position:0% was a bit tougher it was a bit kind of more<00:19:10.400> Hoops<00:19:10.799> to<00:19:10.919> jump<00:19:11.240> through<00:19:11.600> to<00:19:11.880> get<00:19:12.559> up<00:19:12.720> and 00:19:12.870 --> 00:19:12.880 align:start position:0% more Hoops to jump through to get up and 00:19:12.880 --> 00:19:14.270 align:start position:0% more Hoops to jump through to get up and running<00:19:13.200> in<00:19:13.360> the 00:19:14.270 --> 00:19:14.280 align:start position:0% running in the 00:19:14.280 --> 00:19:17.909 align:start position:0% running in the app<00:19:15.280> apps<00:19:15.520> needed<00:19:15.840> to<00:19:16.559> incentivize<00:19:17.559> you<00:19:17.679> know 00:19:17.909 --> 00:19:17.919 align:start position:0% app apps needed to incentivize you know 00:19:17.919 --> 00:19:19.470 align:start position:0% app apps needed to incentivize you know why<00:19:18.039> should<00:19:18.240> I<00:19:18.400> use<00:19:18.640> this<00:19:18.840> app<00:19:19.039> with<00:19:19.120> a<00:19:19.280> little 00:19:19.470 --> 00:19:19.480 align:start position:0% why should I use this app with a little 00:19:19.480 --> 00:19:21.190 align:start position:0% why should I use this app with a little bit<00:19:19.640> more<00:19:19.840> of<00:19:19.960> a<00:19:20.120> carrot<00:19:20.559> whether<00:19:20.760> that's<00:19:21.000> like 00:19:21.190 --> 00:19:21.200 align:start position:0% bit more of a carrot whether that's like 00:19:21.200 --> 00:19:24.590 align:start position:0% bit more of a carrot whether that's like speculation<00:19:22.159> or<00:19:22.640> or<00:19:22.919> yield<00:19:23.600> to<00:19:24.080> get<00:19:24.240> the<00:19:24.360> user 00:19:24.590 --> 00:19:24.600 align:start position:0% speculation or or yield to get the user 00:19:24.600 --> 00:19:28.390 align:start position:0% speculation or or yield to get the user to<00:19:24.760> drump<00:19:25.080> through<00:19:25.880> the<00:19:26.600> the<00:19:26.919> hoops<00:19:27.919> and<00:19:28.240> we 00:19:28.390 --> 00:19:28.400 align:start position:0% to drump through the the hoops and we 00:19:28.400 --> 00:19:32.070 align:start position:0% to drump through the the hoops and we think<00:19:28.960> kind<00:19:29.080> of<00:19:29.280> as<00:19:29.440> the<00:19:29.600> ux<00:19:30.440> improves<00:19:31.440> you<00:19:31.679> can 00:19:32.070 --> 00:19:32.080 align:start position:0% think kind of as the ux improves you can 00:19:32.080 --> 00:19:34.830 align:start position:0% think kind of as the ux improves you can have<00:19:32.880> less<00:19:33.200> speculative<00:19:33.720> use<00:19:34.080> cases<00:19:34.559> because 00:19:34.830 --> 00:19:34.840 align:start position:0% have less speculative use cases because 00:19:34.840 --> 00:19:36.549 align:start position:0% have less speculative use cases because it's<00:19:35.360> you<00:19:35.480> know<00:19:35.760> the<00:19:35.880> same<00:19:36.080> reason<00:19:36.360> why<00:19:36.480> I 00:19:36.549 --> 00:19:36.559 align:start position:0% it's you know the same reason why I 00:19:36.559 --> 00:19:39.909 align:start position:0% it's you know the same reason why I would<00:19:37.000> get<00:19:37.159> up<00:19:37.320> and<00:19:37.480> start<00:19:38.039> using<00:19:38.440> any<00:19:38.760> product 00:19:39.909 --> 00:19:39.919 align:start position:0% would get up and start using any product 00:19:39.919 --> 00:19:42.710 align:start position:0% would get up and start using any product um<00:19:40.919> I<00:19:41.039> can<00:19:41.280> just<00:19:41.720> kind<00:19:41.840> of<00:19:41.960> use<00:19:42.159> the<00:19:42.320> crypto 00:19:42.710 --> 00:19:42.720 align:start position:0% um I can just kind of use the crypto 00:19:42.720 --> 00:19:45.149 align:start position:0% um I can just kind of use the crypto product<00:19:43.080> and<00:19:43.760> enjoy<00:19:44.600> whatever<00:19:44.880> the<00:19:44.960> real 00:19:45.149 --> 00:19:45.159 align:start position:0% product and enjoy whatever the real 00:19:45.159 --> 00:19:47.230 align:start position:0% product and enjoy whatever the real world<00:19:45.440> experience<00:19:45.880> is<00:19:46.120> behind 00:19:47.230 --> 00:19:47.240 align:start position:0% world experience is behind 00:19:47.240 --> 00:19:50.350 align:start position:0% world experience is behind it<00:19:48.240> okay<00:19:48.720> so<00:19:48.919> the<00:19:49.080> next<00:19:49.280> one<00:19:49.440> is<00:19:49.600> the<00:19:49.760> tradeoffs 00:19:50.350 --> 00:19:50.360 align:start position:0% it okay so the next one is the tradeoffs 00:19:50.360 --> 00:19:52.870 align:start position:0% it okay so the next one is the tradeoffs required<00:19:50.760> to<00:19:50.919> enable<00:19:51.320> ux<00:19:51.799> things<00:19:52.159> like<00:19:52.400> Google 00:19:52.870 --> 00:19:52.880 align:start position:0% required to enable ux things like Google 00:19:52.880 --> 00:19:54.830 align:start position:0% required to enable ux things like Google login<00:19:53.240> wallet<00:19:53.600> seems<00:19:53.799> to<00:19:53.960> stretch<00:19:54.400> Definition 00:19:54.830 --> 00:19:54.840 align:start position:0% login wallet seems to stretch Definition 00:19:54.840 --> 00:19:56.750 align:start position:0% login wallet seems to stretch Definition of<00:19:55.039> non-custodial<00:19:55.720> is<00:19:56.440> it<00:19:56.600> really 00:19:56.750 --> 00:19:56.760 align:start position:0% of non-custodial is it really 00:19:56.760 --> 00:19:59.029 align:start position:0% of non-custodial is it really non-custodial<00:19:57.360> if<00:19:57.640> I<00:19:57.760> need<00:19:57.960> to<00:19:58.080> log<00:19:58.360> through<00:19:58.799> a 00:19:59.029 --> 00:19:59.039 align:start position:0% non-custodial if I need to log through a 00:19:59.039 --> 00:20:02.350 align:start position:0% non-custodial if I need to log through a specific<00:19:59.919> provider<00:20:00.919> yeah<00:20:01.440> so<00:20:01.760> this<00:20:01.840> one<00:20:02.039> gets 00:20:02.350 --> 00:20:02.360 align:start position:0% specific provider yeah so this one gets 00:20:02.360 --> 00:20:03.909 align:start position:0% specific provider yeah so this one gets a<00:20:02.440> little<00:20:02.640> bit<00:20:02.799> into<00:20:03.120> like<00:20:03.240> the<00:20:03.360> mechanics<00:20:03.760> of 00:20:03.909 --> 00:20:03.919 align:start position:0% a little bit into like the mechanics of 00:20:03.919 --> 00:20:08.110 align:start position:0% a little bit into like the mechanics of how<00:20:04.080> privy<00:20:04.480> works<00:20:04.960> but<00:20:05.960> when<00:20:06.440> a<00:20:06.679> user<00:20:07.640> creates 00:20:08.110 --> 00:20:08.120 align:start position:0% how privy works but when a user creates 00:20:08.120 --> 00:20:11.909 align:start position:0% how privy works but when a user creates a<00:20:08.280> wallet<00:20:08.720> with<00:20:09.120> privy<00:20:10.120> we<00:20:10.320> split<00:20:10.960> the<00:20:11.400> user's 00:20:11.909 --> 00:20:11.919 align:start position:0% a wallet with privy we split the user's 00:20:11.919 --> 00:20:14.230 align:start position:0% a wallet with privy we split the user's private<00:20:12.280> key<00:20:12.679> into<00:20:13.400> different 00:20:14.230 --> 00:20:14.240 align:start position:0% private key into different 00:20:14.240 --> 00:20:17.430 align:start position:0% private key into different shares<00:20:15.240> and<00:20:16.000> they're<00:20:16.360> assembled<00:20:16.799> in<00:20:16.919> a<00:20:17.080> way 00:20:17.430 --> 00:20:17.440 align:start position:0% shares and they're assembled in a way 00:20:17.440 --> 00:20:22.029 align:start position:0% shares and they're assembled in a way that<00:20:18.200> you<00:20:18.320> know<00:20:18.640> neither<00:20:19.400> privy<00:20:20.760> nor<00:20:21.760> the 00:20:22.029 --> 00:20:22.039 align:start position:0% that you know neither privy nor the 00:20:22.039 --> 00:20:24.029 align:start position:0% that you know neither privy nor the customer<00:20:22.440> we<00:20:22.679> working<00:20:23.000> with<00:20:23.240> has<00:20:23.400> the<00:20:23.559> ability 00:20:24.029 --> 00:20:24.039 align:start position:0% customer we working with has the ability 00:20:24.039 --> 00:20:26.470 align:start position:0% customer we working with has the ability to<00:20:24.600> access<00:20:24.919> the<00:20:25.039> user's<00:20:25.480> private<00:20:25.799> key<00:20:26.360> the 00:20:26.470 --> 00:20:26.480 align:start position:0% to access the user's private key the 00:20:26.480 --> 00:20:29.950 align:start position:0% to access the user's private key the user<00:20:26.760> is<00:20:26.919> the<00:20:27.039> only<00:20:27.360> party<00:20:27.840> that<00:20:28.440> can<00:20:28.720> and 00:20:29.950 --> 00:20:29.960 align:start position:0% user is the only party that can and 00:20:29.960 --> 00:20:32.510 align:start position:0% user is the only party that can and actually<00:20:30.960> you<00:20:31.080> know<00:20:31.400> assemble<00:20:31.840> the<00:20:32.000> key<00:20:32.320> on 00:20:32.510 --> 00:20:32.520 align:start position:0% actually you know assemble the key on 00:20:32.520 --> 00:20:34.870 align:start position:0% actually you know assemble the key on their<00:20:32.760> device<00:20:33.159> and<00:20:33.440> control<00:20:33.840> the<00:20:34.000> wallet<00:20:34.799> and 00:20:34.870 --> 00:20:34.880 align:start position:0% their device and control the wallet and 00:20:34.880 --> 00:20:36.630 align:start position:0% their device and control the wallet and so<00:20:35.080> even<00:20:35.320> though<00:20:35.720> you<00:20:35.799> know<00:20:36.000> Google<00:20:36.320> is<00:20:36.480> the 00:20:36.630 --> 00:20:36.640 align:start position:0% so even though you know Google is the 00:20:36.640 --> 00:20:39.830 align:start position:0% so even though you know Google is the signin<00:20:37.080> method<00:20:37.919> that's<00:20:38.120> only<00:20:38.440> one<00:20:39.000> the<00:20:39.320> the 00:20:39.830 --> 00:20:39.840 align:start position:0% signin method that's only one the the 00:20:39.840 --> 00:20:44.070 align:start position:0% signin method that's only one the the kind<00:20:39.960> of<00:20:40.240> oth<00:20:41.159> link<00:20:41.720> is<00:20:41.880> only<00:20:42.200> one<00:20:42.559> out<00:20:42.720> of<00:20:43.280> the 00:20:44.070 --> 00:20:44.080 align:start position:0% kind of oth link is only one out of the 00:20:44.080 --> 00:20:46.789 align:start position:0% kind of oth link is only one out of the three<00:20:44.280> shares<00:20:44.840> that<00:20:44.960> we<00:20:45.080> split<00:20:45.360> the<00:20:45.480> key<00:20:45.799> into 00:20:46.789 --> 00:20:46.799 align:start position:0% three shares that we split the key into 00:20:46.799 --> 00:20:49.669 align:start position:0% three shares that we split the key into and<00:20:47.039> so<00:20:47.720> you<00:20:47.840> know<00:20:48.039> that<00:20:48.200> doesn't<00:20:48.960> kind<00:20:49.080> of 00:20:49.669 --> 00:20:49.679 align:start position:0% and so you know that doesn't kind of 00:20:49.679 --> 00:20:52.549 align:start position:0% and so you know that doesn't kind of make<00:20:49.960> the<00:20:50.200> wallet<00:20:50.919> experience 00:20:52.549 --> 00:20:52.559 align:start position:0% make the wallet experience 00:20:52.559 --> 00:20:54.830 align:start position:0% make the wallet experience custodial<00:20:53.559> okay<00:20:53.880> so<00:20:54.039> we<00:20:54.159> have<00:20:54.320> time<00:20:54.440> for<00:20:54.640> one 00:20:54.830 --> 00:20:54.840 align:start position:0% custodial okay so we have time for one 00:20:54.840 --> 00:20:56.310 align:start position:0% custodial okay so we have time for one last<00:20:55.080> question<00:20:55.520> this<00:20:55.760> pretty<00:20:55.960> interesting 00:20:56.310 --> 00:20:56.320 align:start position:0% last question this pretty interesting 00:20:56.320 --> 00:20:58.270 align:start position:0% last question this pretty interesting one<00:20:56.520> as<00:20:56.679> well<00:20:57.200> what's<00:20:57.480> the<00:20:57.640> industry<00:20:58.039> that<00:20:58.159> you 00:20:58.270 --> 00:20:58.280 align:start position:0% one as well what's the industry that you 00:20:58.280 --> 00:21:00.149 align:start position:0% one as well what's the industry that you think<00:20:58.640> will<00:20:58.760> on<00:20:58.960> board<00:20:59.159> the<00:20:59.280> most<00:20:59.520> users<00:20:59.919> on 00:21:00.149 --> 00:21:00.159 align:start position:0% think will on board the most users on 00:21:00.159 --> 00:21:02.870 align:start position:0% think will on board the most users on chain<00:21:00.440> in<00:21:00.559> the<00:21:00.720> next<00:21:00.960> 5<00:21:01.200> years<00:21:02.080> yeah<00:21:02.640> we're 00:21:02.870 --> 00:21:02.880 align:start position:0% chain in the next 5 years yeah we're 00:21:02.880 --> 00:21:04.909 align:start position:0% chain in the next 5 years yeah we're really<00:21:03.200> excited<00:21:03.600> about<00:21:03.840> what<00:21:03.960> we're<00:21:04.200> seeing 00:21:04.909 --> 00:21:04.919 align:start position:0% really excited about what we're seeing 00:21:04.919 --> 00:21:08.870 align:start position:0% really excited about what we're seeing in<00:21:05.600> the<00:21:06.240> finch<00:21:06.799> and<00:21:07.000> payments<00:21:07.480> market<00:21:08.360> so 00:21:08.870 --> 00:21:08.880 align:start position:0% in the finch and payments market so 00:21:08.880 --> 00:21:11.549 align:start position:0% in the finch and payments market so seeing<00:21:09.799> you<00:21:09.919> know<00:21:10.159> all<00:21:10.360> of<00:21:10.520> these<00:21:10.720> Neo<00:21:11.120> Banks 00:21:11.549 --> 00:21:11.559 align:start position:0% seeing you know all of these Neo Banks 00:21:11.559 --> 00:21:14.070 align:start position:0% seeing you know all of these Neo Banks really<00:21:11.840> starting<00:21:12.279> to<00:21:12.919> lean<00:21:13.240> into<00:21:13.559> crypto 00:21:14.070 --> 00:21:14.080 align:start position:0% really starting to lean into crypto 00:21:14.080 --> 00:21:17.430 align:start position:0% really starting to lean into crypto payment<00:21:14.360> rails<00:21:15.000> to<00:21:15.279> give<00:21:15.799> users<00:21:16.799> access<00:21:17.080> to 00:21:17.430 --> 00:21:17.440 align:start position:0% payment rails to give users access to 00:21:17.440 --> 00:21:21.310 align:start position:0% payment rails to give users access to USD<00:21:18.440> faster<00:21:18.880> cheaper<00:21:19.640> payments<00:21:20.640> you<00:21:20.760> know 00:21:21.310 --> 00:21:21.320 align:start position:0% USD faster cheaper payments you know 00:21:21.320 --> 00:21:22.950 align:start position:0% USD faster cheaper payments you know potentially<00:21:21.760> better<00:21:22.039> Financial<00:21:22.559> products 00:21:22.950 --> 00:21:22.960 align:start position:0% potentially better Financial products 00:21:22.960 --> 00:21:25.430 align:start position:0% potentially better Financial products over<00:21:23.240> time<00:21:24.240> we<00:21:24.360> think<00:21:24.520> that's<00:21:24.679> a<00:21:24.960> really 00:21:25.430 --> 00:21:25.440 align:start position:0% over time we think that's a really 00:21:25.440 --> 00:21:29.190 align:start position:0% over time we think that's a really powerful<00:21:25.919> driver<00:21:26.600> of<00:21:27.240> adoption<00:21:28.240> and<00:21:28.840> you<00:21:28.960> know 00:21:29.190 --> 00:21:29.200 align:start position:0% powerful driver of adoption and you know 00:21:29.200 --> 00:21:31.710 align:start position:0% powerful driver of adoption and you know if<00:21:29.880> every<00:21:30.159> banking<00:21:30.640> product<00:21:31.000> over<00:21:31.200> the<00:21:31.360> next 00:21:31.710 --> 00:21:31.720 align:start position:0% if every banking product over the next 00:21:31.720 --> 00:21:34.510 align:start position:0% if every banking product over the next five<00:21:31.960> years<00:21:32.400> somehow<00:21:33.159> incorporates<00:21:33.840> a<00:21:34.120> crypto 00:21:34.510 --> 00:21:34.520 align:start position:0% five years somehow incorporates a crypto 00:21:34.520 --> 00:21:36.029 align:start position:0% five years somehow incorporates a crypto payment<00:21:34.760> Rail<00:21:35.120> and<00:21:35.279> gets<00:21:35.480> their<00:21:35.640> users 00:21:36.029 --> 00:21:36.039 align:start position:0% payment Rail and gets their users 00:21:36.039 --> 00:21:39.350 align:start position:0% payment Rail and gets their users wallets<00:21:36.559> that's<00:21:37.520> a<00:21:37.840> really<00:21:38.559> massive<00:21:38.919> Tailwind 00:21:39.350 --> 00:21:39.360 align:start position:0% wallets that's a really massive Tailwind 00:21:39.360 --> 00:21:40.750 align:start position:0% wallets that's a really massive Tailwind for<00:21:39.520> usage<00:21:39.840> in<00:21:39.960> the 00:21:40.750 --> 00:21:40.760 align:start position:0% for usage in the 00:21:40.760 --> 00:21:42.909 align:start position:0% for usage in the market<00:21:41.760> Thanks<00:21:42.039> Max<00:21:42.360> can<00:21:42.440> we<00:21:42.600> give<00:21:42.720> him<00:21:42.840> a 00:21:42.909 --> 00:21:42.919 align:start position:0% market Thanks Max can we give him a 00:21:42.919 --> 00:21:44.230 align:start position:0% market Thanks Max can we give him a round<00:21:43.120> of<00:21:43.240> applause<00:21:43.520> for<00:21:43.679> an<00:21:43.799> insightful 00:21:44.230 --> 00:21:44.240 align:start position:0% round of applause for an insightful 00:21:44.240 --> 00:21:45.750 align:start position:0% round of applause for an insightful conversation<00:21:44.760> they 00:21:45.750 --> 00:21:45.760 align:start position:0% conversation they 00:21:45.760 --> 00:21:48.789 align:start position:0% conversation they had<00:21:46.760> stay<00:21:47.000> tuned<00:21:47.279> we'll<00:21:47.440> be<00:21:47.640> right<00:21:47.840> back<00:21:48.120> at<00:21:48.400> 3 00:21:48.789 --> 00:21:48.799 align:start position:0% had stay tuned we'll be right back at 3 00:21:48.799 --> 00:21:51.630 align:start position:0% had stay tuned we'll be right back at 3 p.m.<00:21:49.440> with<00:21:49.679> the<00:21:49.840> next<00:21:50.320> session<00:21:51.320> all<00:21:51.440> right 00:21:51.630 --> 00:21:51.640 align:start position:0% p.m. with the next session all right 00:21:51.640 --> 00:21:54.480 align:start position:0% p.m. with the next session all right thank<00:21:51.840> you